IP space/Network number change

[jerry1]

Has anyone gone through a company wide IP space
domainname change? And what was some of the problems that were incountered as a result of changing all nodes IP addresses. Network number is different also so this is not just an IP address change in the same class network. Domainname is changing also.

For printers I can use hpwebjet to reconfiure or write a script to do telnet to jetdirect and reconfigure.

Desktop systems not a problem. pretty static
unix systems.
I made a scan of the servers and came up with
some lists of files that would need to be changed.
I have the order of servers figured out.
NFS/NIS/DNS servers last.

Anyone had any issues with san/emc?
Will reconfigure brocade switches also.

[Steven E. Protter · Accepted solution]

In general a fiber connection to the SAN shows up as a SCSI device and will not be effected by a change in IP address.

These cards identify themselves to the system and the san by their world wide name.

SEP

[Donny Jekels]

unless you are refering to the management lan port on the brocade switch. yes you must change this ip as well to the new address.

as SEP explained no concern on the FC side. for disks only.

unless you use fiber lan cards.

peace
Donny

[Thomas Bianco]

Unless your using iSCSI or FC/IP you shouldn't need to reconfigure the brocades (excepting the management port ip).

As for other issues: Iâ d be wary of routing changes first. With major routing changes (most of which are manual) it's very easy to overlook one of those entries and create a routing loop.

Most other changes will be minor in nature, especially if most or all of your network infrastructure uses DNS or WINS names.

Oh, make certain you change the DNS and WINS nam