johncosentino
asked on
Solaris Network issue
A sun solaris machine lost network connectvity, I discoved an error message saying that my machine had found a duplicate ip on the network an that it was shutting down its network interface (see below).
WARNING: node 00:15:17:d1:6c:27 is using our IP address
192.168.153.239 on hme0
WARNING: node 00:15:17:d1:6c:27 is using our IP address
192.168.153.239 on hme0
WARNING: node 00:15:17:c9:ff:dd is using our IP address
192.168.153.239 on hme0
WARNING: hme0 has duplicate address 192.168.153.239 (claimed
by 00:15:17:c9:ff:dd); disabled
After changing the ip to a dummy IP, then changing it back to its original ip (seen above....192.168.153.239) this error message ceased. But now very few network related commands work properly. Most hang the computer. Ping, even to localhost hangs, arp commands hang, most netstat commands hang.
I noticed the following line when running svcs -a |grep network
offline* 11:52:12 svc:/network/service:defau
I'm not at all experience with solaris os network troubleshooting. any help would be greatly appreciated.
Thanks
WARNING: node 00:15:17:d1:6c:27 is using our IP address
192.168.153.239 on hme0
WARNING: node 00:15:17:d1:6c:27 is using our IP address
192.168.153.239 on hme0
WARNING: node 00:15:17:c9:ff:dd is using our IP address
192.168.153.239 on hme0
WARNING: hme0 has duplicate address 192.168.153.239 (claimed
by 00:15:17:c9:ff:dd); disabled
After changing the ip to a dummy IP, then changing it back to its original ip (seen above....192.168.153.239) this error message ceased. But now very few network related commands work properly. Most hang the computer. Ping, even to localhost hangs, arp commands hang, most netstat commands hang.
I noticed the following line when running svcs -a |grep network
offline* 11:52:12 svc:/network/service:defau
I'm not at all experience with solaris os network troubleshooting. any help would be greatly appreciated.
Thanks
ASKER
Thanks for the response. Since I posted my first question I've reset the ipaddress on the machine. That is, I set the ip address to something else, then set it back to the original address. This seems to have stopped the error message regarding the duplicate ip addresses.
However the machine is still not pingable. I noticed that a service that appears to be a critical service is stuck in the offline state and I can get it to become active.
offline* Mar_04 svc:/network/service:defau
Could you walk me through the process of how you would reactivate this service?
However the machine is still not pingable. I noticed that a service that appears to be a critical service is stuck in the offline state and I can get it to become active.
offline* Mar_04 svc:/network/service:defau
Could you walk me through the process of how you would reactivate this service?
svcadm is the tool to manage the services.
changing the IP and reverting back is not a good process.
However the other system got the IP has to be addressed and resolved.
How did you change the IP? There are different configuration files that have to be changed/adjusted.
changing the IP and reverting back is not a good process.
However the other system got the IP has to be addressed and resolved.
How did you change the IP? There are different configuration files that have to be changed/adjusted.
ASKER
I changed the ip by running ifconfig hme0 inet 192.168.153.218 (then running the same with ip address 192.168.153.239)... this stopped the duplicate ip error message.
Like I said in my prior post, very few of the network related commands work on the host (ifconfig works, but that's about it). That's why I posted that piece about the service that is in an offline state.
Wht would all these commands (ie arp, netstat, etc) hang? What service are they dependent on?
Like I said in my prior post, very few of the network related commands work on the host (ifconfig works, but that's about it). That's why I posted that piece about the service that is in an offline state.
Wht would all these commands (ie arp, netstat, etc) hang? What service are they dependent on?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are you trying to BOND two of the network interfaces on the system to appear as one, but did not trunc/bond the network switch and did not subordinate the hme0/1 under a bond0 ??
If you have a managed switch you could use it to locate where the other system is.
Check your DHCP server to make sure that you are not alocating the 192.168.153.239 IP even though you have one system configured with this IP as static.