tkevans@cs.umd.edu (06/11/90)
When our vendor installed our Sun equipment (3/50's and 3/60's, but this
is not--I don't think--important to this question), he used the example IP
addresses in the Sun manuals to set up the machines. At that time, we had
no plans to connect to the outside world, so these arbitrary addresses
worked ok within our network.
Now, however, we have a shiny new domain name and Class B IP address. As
a result, I need to change all the IP addresses we have been using. When
I made changes in the /etc/hosts file on the server machines, everything
went ok, but the clients could not find the server to boot up. They were
able to get their (new) IP address from the server, but couldn't boot.
There doesn't seem to be anything in TFM about how to _change_ an existing
client's IP address. Lots of stuff about installing and deleting clients,
but nothing about changing an existing one. I hate to have to back the
client up, then delete it, then reinstall it, just to change its IP
address.
From TFM, it appears the client looks for a file /tftpboot named with the
hex equivalent of its IP address, a file which is symbolically linked to
/tftpboot/boot.sun3. Could I just rename this file to the hex equivalent
of its new IP address? Will the client boot? If so, are there any other
fixes needed to properly implement this workaround? Thanks.
cc:Mail Tim K. Evans at ~OSS
UUCP ...!{rutgers|ames|uunet}!mimsy!woodb!tkevans
INTERNET tkevans%woodb@mimsy.umd.edu PHONE: (301) 965-3286
US MAIL 6401 Security Blvd, 2-Q-2 Operations, Baltimore, MD 21235merlyn@iwarp.intel.com (Randal Schwartz) (06/12/90)
In article <8715@brazos.Rice.edu>, woodb!tkevans@cs writes: | | Now, however, we have a shiny new domain name and Class B IP address. As | a result, I need to change all the IP addresses we have been using. When | I made changes in the /etc/hosts file on the server machines, everything | went ok, but the clients could not find the server to boot up. They were | able to get their (new) IP address from the server, but couldn't boot. | | There doesn't seem to be anything in TFM about how to _change_ an existing | client's IP address... Yeah, I just went through renaming 14 uVaxen and 50 Suns (Sun 3, Sparc, Sun-386, with about 30 diskless clients) from our old class C to our new class B net number. Here's what I had to do: 1. Disable the three YP slave servers, because they would have the old hosts entries, and there's no way to force an update in sync with the world. This required deleting /var/yp/`domain-name` on each slave and editing the 'ypservers' map on the master. 2. Halt all the clients. 3. Unmount all the NFS disks from the YP master. 4. Halt all machines except the YP master. 5. Edit /etc/hosts, /etc/netmasks, /etc/networks on the YP master. (Don't forget to cd /var/yp && make.) 6. Reboot the YP master. (slow, because it tried to mount all those disks...) 7. Reboot everything but the clients. 8. Rename all /tftpboot/AABBCC12 files on all boot servers to /tftpboot/DDEEFF12, where AABBCC was the old net number in hex, and DDEEFF was the new net number. 9. Boot the clients. 10. Add the three slave YP servers back. Took me a good long day. Step 8 was the hardest... I couldn't figure out why the clients weren't booting. I sp'ose it's documented down in the bowels somewhere, but I didn't have it in front of me. Just another (tired) sysadmin, Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn
richard@chook.ua.oz.au (Richard Siggs) (07/02/90)
In article <8715@brazos.Rice.edu>, woodb!tkevans@cs.umd.edu writes: [stuff deleted] |> |>Now, however, we have a shiny new domain name and Class B IP address. As |>a result, I need to change all the IP addresses we have been using. |> |>From TFM, it appears the client looks for a file /tftpboot named with the |>hex equivalent of its IP address, a file which is symbolically linked to |>/tftpboot/boot.sun3. Could I just rename this file to the hex equivalent |>of its new IP address? Will the client boot? If so, are there any other |>fixes needed to properly implement this workaround? Thanks. As far as I know (I've done it many times), you can just rename the file in tftpboot to the new IP address in hex, however, be careful about permissions on files in /tftpboot, as tftp is pretty dumb. I've also found that the client needs its server's IP number in its /etc/hosts file (even if it's YP served, as YP comes up after such things as mounting root disks...) Richard Siggs | "As the joys of Heaven are enjoyed by men, Computer Science Dept., | so shall the pains of Hell be suffered. Adelaide University, | For they will be men still, South Australia. | so they will act and feel as men." ACSnet: richard@cs.ua.oz.au | - quote from the film "Bliss".