I asked about a problem getting the netmask to set correctly on reboot in Solaris 10. Thanks to all that replied. I believe that I made a false assumption of what the netmask *should* be, based on another server that turns out not to be on the same network. Thus, it appears to be my mistake. However, I rec'd a number of good suggestions. Most people said this hadn't changed from Solaris 9 to Solaris 10. It was also noted that I should have included examples - apologies, had trouble sanitizing info and hoped this was an easy and obvious change in Solaris 10. Comments included: * "I had the same problem and I fixed it by adding the netmask on the /etc/hostname.hme0 file. Here is an example: 10.10.10.10 netmask + broadcast + up" * Check the links from /etc/netmasks to /etc/inet/netmasks, and /etc/hosts to /etc/inet/hosts, and double-check syntax in files * Check the network number in /etc/netmasks * Make sure you have the same entries as /etc/hosts (sym link to /etc/inet/hosts) in /etc/inet/ipnodes. "Used to be for IPV6 only. Compulsory on Solaris 10 for IPV4, too, nowadays." * "I notice that Solaris 10 is very strict about network definition, e.g., we had an old definition like 10.241.132.0 255.255.255.0 ...which had worked before, but Sol10 rejected it because 10.241.132 isn't (strictly speaking) a network." Regards, and thanks, _______________________________ Judith Reed This e-mail is the property of NaviSite, Inc. It is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. Distribution or copying of this e-mail, or the information contained herein, to anyone other than the intended recipient is prohibited. _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Tue Jan 30 11:23:35 2007
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:04 EST