[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
We changed IP addresses recently. Despite following the III directions on
this, we did run into trouble with our IT people. We gave them copies of
the directions multiple times, had multiple meetings with IT, had a
timeline, and still ran into trouble. Our campus installed a new network
and we were also getting a new server from III. We cut over the old machine
to the new network, then found when the new server was installed, we had to
change IPs yet again because the first time the IT people had made a mistake
and put us on the wrong subnet. There were also issues with firewall ports
and DNS (domain name server). Since we changed subnets, different firewall
servers and DNS machines were also involved. Plus there were some issues
with ports on routers in connection with the firewall ports.

1 - Make sure all IT people concerned have copies of III instructions

2 - Do have consultation/planning meetings.

3 - Set up a local timeline with your IT people and check up on everything.
Continue to check up on everything.

4 - Make sure any firewall issues and DNS issues are addressed.

5 - If software such as OCLC uses IP address rather than alias, be prepared
to change the settings on PCs. You will need to change IP in Millennium.

6 - If your alias changes, you have more changes. Try to keep the same
alias.

7 - Follow the steps above for your new server installation also. Copy
documents, meet, follow up, follow up.

8 - Last, be prepared for something to go wrong locally anyway. Make sure
that all your pertinent local IT people are available on the day of the
cutover and also the day of the new server installation.

9 - Be prepared for problems afterwards. Our ftp would not work because of
a firewall issue the local IT had forgotten about. Over the following
weeks, several similar issues came up with parts of the system we did not
use very often. We tried to test every process, but there are a lot of
processes in an III system.



Sandra Card
Library
California State University, Los Angeles
scard at calstatela dot edu
323-343-4894


-----Original Message-----
From: Buzzell, Bonnie Good [mailto:Bonnie_Buzzell at brown dot edu]
Sent: Sunday, January 02, 2005 6:38 AM
To: IUG INNOPAC List
Subject: server ip address change


Finding myself the adminstrator for our innovative system without a systems
background, I'd especially welcome your wisdom and advice regarding changing
our III server's ip address.

We are a turnkey site, with the server housed in the University's IT
department. As part of the preparation for moving to a new server
mid-January, the person responsible for IT security has recommended that we
move to a new subnet.

I have reviewed the FAQ on csdirect, and have found what I can in the
manual. It seems to me that this would require significant planning and
coordination to make sure everything keeps working.

I would like to be able to respond to the ip-change rcommendation knowing
the pro's and con's of doing so, and with a fairly complete idea of
everything that we would have to do to accomplish this.

I'd welcome advice from any/all, and would especially appreciate hearing
from any of you who have changed your ip address.

Thanks,
Bonnie

Ps--Happy new year!

........................................................................
..
Bonnie Buzzell
Web Services Department
Brown University Library, Box A, Providence, RI 02912
401-863-3599 Bonnie_Buzzell at brown dot edu
........................................................................
..



--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies: INNOPAC at innopacusers dot org Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac


--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---