- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- MC Service Guard 11.18 - Single Node Cluster - Lan...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2011 09:10 AM
10-28-2011 09:10 AM
MC Service Guard 11.18 - Single Node Cluster - Lan recovery after dual failure
Hi,
I was testing our configuration of MC/SG 11.18 (on B.11.31) and have a question about the expected behavior of one scenario.
We have a single node cluster made by an rx2800 node, with a subnet supporting the package and using two interfaces (lan1 Primary and lan0 Standby)
Test was performed with both interfaces connected to the same switch.
Single failure (tested unplugging one of the cables) worked fine, with local IP switch as expected, with Primary taking the IP when possible and switching to Standby when needed.
Question refers to the dual failure scenario, once we unplugged both cables. Package went down as expected and being a single node stayed down. I was surprised when re-connecting one of the cables nothing happened, the syslog did not report the interface as available and cmvewcl was showing BOTH interfaces as DOWN.
After plugging in the second cable the situation went to normal.
After making some more tests we saw that after two cables are disconnected, and only one is connected back you have two scenarios
a) If the fist cable to be re-connected did not host the IP once the two cables were disconnected, the LAN is not identified as available
b) If the first cable to be reconnected hosted the IP then the interface is identified as available, BUTonly after attempting an IP conncetion (either a PING or a telnet/SSH) to it.
I understand when both interfaces are up one is identified as poller and start sending to the other some packets to ensure the other is healthy. Once a driver error is reported for an interface, that interface is marked as bad, and appropriate action is taken depending on the configuration.
But what happens after both available Lan interfaces are down and then one (only one) is brought up?
This way the polling won't help since the far end won't respond, but still we would have the connectivity available.
Am I missing anything obvious?
Thanks as usual!
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2011 06:46 AM
11-09-2011 06:46 AM
Re: MC Service Guard 11.18 - Single Node Cluster - Lan recovery after dual failure
You are not missing anything. Unfortunately this is a double failure that the product is not designed to protect you from. The product does not handle the situation where all interfaces on a single bridged net in the cluster go down. If there are no pollers left, polling stops and does not start again without external influences. You should find that if you use linkloop to manually induce traffic the lans will recover. You will need to send several messages over a few seconds for the increase in statistics to be enough to recover the lan.
You really need to configure the cluster such that there is no single point of failure which allows both lan interfaces to fail at the same time or risk this scenario.