HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Network architecture for the M/C service guard
Operating System - HP-UX
1825643
Members
3641
Online
109685
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
06-18-2001 10:50 AM
06-18-2001 10:50 AM
Network architecture for the M/C service guard
I am implementing cluster setup for 2 HP L class server . The server has tree lan cards
one as primary , standby and heartbeat . Primary cards for the both the servers is attaced to a switch and standby cards to another switch . The switch has back to back connectivity so they should act as a bridge in case of lancard failure .
This setup seems to be not working .
The linkloop command gives FAILED status when I try to check connectivity from primary to standby network interface . Am I missing somthing ?
one as primary , standby and heartbeat . Primary cards for the both the servers is attaced to a switch and standby cards to another switch . The switch has back to back connectivity so they should act as a bridge in case of lancard failure .
This setup seems to be not working .
The linkloop command gives FAILED status when I try to check connectivity from primary to standby network interface . Am I missing somthing ?
vaibhav
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2001 11:33 AM
06-18-2001 11:33 AM
Re: Network architecture for the M/C service guard
Your setup sounds good, you probably need to check your switch configuration. linkloop between primary and standby lans must be possible for local lan failover to function (i.e. primary and standby lan must be on the same bridged network).
You might want to refer to the somewhat outdated paper
http://docs.hp.com/hpux/onlinedocs/ha/wpnetwork.pdf
for reference and you will find your setup on page 5 (figure 6).
Carsten
You might want to refer to the somewhat outdated paper
http://docs.hp.com/hpux/onlinedocs/ha/wpnetwork.pdf
for reference and you will find your setup on page 5 (figure 6).
Carsten
-------------------------------------------------------------------------------------------------
In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. -- HhGttG
In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. -- HhGttG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2001 11:31 PM
06-18-2001 11:31 PM
Re: Network architecture for the M/C service guard
I would hazard a guess that the switch-2-switch connection may not be correct.
You need to do as Carsten says, and check all the configutrations on the switches.
It may be a worthwhile test to first check all the lan connections by connecting them all to just one switch to prove at least the cables are ok.
You need to do as Carsten says, and check all the configutrations on the switches.
It may be a worthwhile test to first check all the lan connections by connecting them all to just one switch to prove at least the cables are ok.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2001 12:12 AM
07-17-2001 12:12 AM
Re: Network architecture for the M/C service guard
When the linkloop command fails it can be two things:
1) physical problem: cable, NIC switch port etc.
2) logical problem: when the primary and standby lans are not in the same Vlan (subnet) on the switch linkloop will fail.
1) physical problem: cable, NIC switch port etc.
2) logical problem: when the primary and standby lans are not in the same Vlan (subnet) on the switch linkloop will fail.
The surest sign that life exists elsewhere in the universe is that none of it has tried to contact us
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP