NETANN-L Archives

- NETANN-L - Networkmaine Network Announcement List

NETANN-L@LISTS.MAINE.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Irelann Kerry Anderson <[log in to unmask]>
Reply To:
- NETANN-L - UNET Network Announcement List <[log in to unmask]>
Date:
Sun, 13 Mar 2005 13:44:55 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (48 lines)
I've re-enabled the 130.111.2.1 IP address on the mainframe.   It turns
out an application had the IP address baked in rather than the name of
the mainframe and cannot be entirely fixed for a few days.  Once that is
taken care of we will turn it off again and see if any other problems
show up.

To reiterate a bit of the history of this...

The 130.111.2.1 IP address is on a cisco CIP card in an old router and
is no longer under maintenance.  If it breaks, it is broken, so we need
to move any applications over to the new interface at IP address
130.111.32.53.

We announced this change when we announced the switchover to the new
mainframe but it may not have gotten to everyone it should have.

The DNS (name server) was updated to point to the new IP address on
December 12th when we moved to the new mainframe.  At that time we also
configured TCPIP on the mainframe to use the new interface as the
default interface.  The intent being that we would remove the old
interface some short time thereafter.

We ran into a problem with an application with the old IP address hard
coded and could not use the new interface as the default until it was
fixed and so we changed the default back to 130.111.2.1 while still
leaving DNS entries pointing to the new interface.

This weekend we changed the default to the new interface and turned off
the old interface to see if anything would break.  As mentioned one more
application did break.   The default is now the new interface, but the
old one is still active for a short time longer.

If any of you have anything that might have the IP address 130.111.2.1
hard coded, please change to use the name of the mainframe:
maine.unet.maine.edu (or the alternative maine.maine.edu) or if you
cannot, use the IP address 130.111.32.53.  Note that if you use an IP
address in place of a name, the same problem will probably arise again
at some future date.

My thanks to those who worked on fixing up broken applications and my
apologies to those who unexpectedly found something of theirs broken.

--
Irelann Kerry Anderson          phone:    (207)581-3508
Systems Group                   internet  [log in to unmask]
University Network - UNET
University of Maine System

ATOM RSS1 RSS2