We will be moving the 131.215.113.XXX ip addresses of the martian network over to a 192.168.XXX.YYY scheme.
Computer names (i.e. linux1, scipe25/c1dcuepics) will not change. The domain name martian, will not change (i.e. linux1.martian.). What will change is the underlying IP address associated with the host names. Linux1 will no longer be 220.127.116.11 but something like 192.168.0.20. If everything is done properly, that should be it. There should be no impact or need to change anything in EPICS for example. However, if there are custom scripts with hard coded IP addresses rather than hostnames, those would need to be updated, if they exist.
Each computer and router will need to either be accessed remotely, or directly, and the configuration files controlling the IP address (and/or dns lookup locations) be modified. Then it needs to be rebooted so the configuration changes take effect. I'll be making an updated list of computers this week (tracked down via their physical ethernet cables), and next week, probably on Thursday, and then we simply go down the list one by one.
For a linux machine, this means checking the /etc/hosts file and making sure it doesn't have old information. It should look like:
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
Then change the /etc/sysconfig/network-scripts/ifcfg-eth0 file (or ethX file depending on the ethernet card in question). The IPADDR, NETWORK, and GATEWAY lines will need to be changed. You can change the hostname (although I don't plan on it) by modifying the /etc/sysconfig/network file.
The /etc/resolv.conf file will need to be updated with the new DNS server location (i.e. 18.104.22.168 to 192.168.0.20 for example).
Simlarly to linux, the /etc/hosts file will need to be updated and/or simplified. The /etc/defaultrouter file will need to be updated to the new router ip. /etc/defaultdomain will need to be updated. The /etc/resolv.conf will need to be updated with the new dns server.
Looking at the vxWorks machines, the command bootChange can be used to view or edit the IP configuration.
The following is an example from c1iscey.
'.' = clear field; '-' = go to previous field; ^D = quit
boot device : eeE0
processor number : 0
host name : linux1
file name : /cvs/cds/vw/pIII_7751/vxWorks
inet on ethernet (e) : 22.214.171.124:ffffff00
inet on backplane (b):
host inet (h) : 126.96.36.199
gateway inet (g) :
user (u) : controls
ftp password (pw) (blank = use rsh):
flags (f) : 0x0
target name (tn) : c1iscey
startup script (s) :
other (o) :
value = 0 = 0x0
By updating the the host (name of machine where its mounting /cvs/cds from - i.e. linux1), inet on ethernet (the IP of c1iscey) and host inet (linux1's ip address), we should be able to change all the vxWorks machines.
The DNS server running on linux1 will need to be updated with the new IPs and domain information. The host file on linux1 will also need to be updated for all the new IP addresses as well.
This will need to be handled carefully as the last time I tried getting away without the host file on linux1, it broke NFS mounting from other machines. However, as long as the host on linux1 is kept in sync with the dns server files everything should work.