From: Naylor, Jim (Jnaylor@Schnucks.com)
Date: Tue Sep 27 2005 - 09:01:47 EDT
Thanks to Craig Kennedy, Stephane Lachapelle, Rita Workman, and Jay Duncan for their response. It appears that this is normal operation. It was suggested that if I had waited a little while after changing the Primary connection and allow everything to stabilize before changing the Alternate that it may have failed back over to the primary without incident. Unfortunately I am not able to test that theory. It was also suggested that this is the way I had it set up in my configuration file for the package. Once again, thanks for the replies.
Thanks,
Jim Naylor
Unix/Storage Systems Administrator
Schnuck Markets, Inc.
* Direct (314) 994-4784
))( Cell (314) 691-0186
Fax (314) 994-4684
* E-Mail jnaylor@schnucks.com
-----Original Message-----
From: hpux-admin-owner@DutchWorks.nl
[mailto:hpux-admin-owner@DutchWorks.nl]On Behalf Of Naylor, Jim
Sent: Tuesday, September 20, 2005 9:03 AM
To: Hpux-Admin@Dutchworks. Nl (E-mail)
Subject: [HPADM] MC/ServiceGuard NIC faliover
Good Day All,
I have a question on Service Guard NIC failover. We had a situation where we were moving our HP900 network connections to a new switch. This particular HP had Service Guard running on it. I halted the only package on this system and moved the cable to the new switch. Every thing went fine with moving to the new switch and I restarted the package which is running an oracle database. We later noticed that the NIC card settings in SAM had changed from Autonegociate OFF, 100Mb, Full Duplex to Autonegociate ON, 100Mb, Half Duplex. In SAM I changed the Primary NIC back to Autonegociate OFF, 100Mb, Full duplex and noticed that the IP information failed over to the Alternate NIC. No problem so far. Then I checked the Alternate settings and notice that they had also changed to Autonegociate ON, 100Mb, Half Duplex. Once again via SAM I changed the settings back to Autonegociate OFF, 100Mb, Full Duplex. As expected the IP information failed back over to the Primary NIC but a !
few minutes later all jobs accessing the database of this package started failing. What I found was the database/SG package was shutting down which needless to say cause some major problems. During the process of changing the NIC settings we never lost network communications to the system.
My question is:
1- Is this what SG is supposed to do if your primary NIC appears to fail and a few minutes later the Alternate NIC appears to fail
even though the IP information failed back over to the Primary NIC?
2- Is SG assuming that all network connections have failed and shuts down the package?
3- Other than shutting down the package again, would there have been a better way of handling the NIC setting changes?
Any thoughts on this would be greatly appreciated.
Thanks,
Jim Naylor
Unix/Storage Systems Administrator
Schnuck Markets, Inc.
* Direct (314) 994-4784
))( Cell (314) 691-0186
Fax (314) 994-4684
* E-Mail jnaylor@schnucks.com
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:50 EDT