- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- ProLiant DL380 ServiceGuard & bonding problem
Operating System - Linux
1753854
Members
7215
Online
108808
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
Discussions
Discussions
Forums
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
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-23-2004 04:13 PM
тАО06-23-2004 04:13 PM
ProLiant DL380 ServiceGuard & bonding problem
RHEL3.0, kernel 2.4.21-9, bonding driver 1.0.4f-1 (bonding driver from HP)
I have 2-node cluster, four nics on each host. I've created two bonds on both hosts (two nics on one bond, though all nics at same subnet). Bonding is working ok, so when I'm unplugging lan cables, the other nic gets active and so on.
But when I'm trying to query the ServiceGuard cluster with command 'cmquerycl -v -L /my/lock/disk -n host1 -n host2 -C $SGCONF/foo.ascii' , i'm getting the following error:
"Error: Unable to determine network configuration: failed to receive net probe reply from node host1.
Failed to probe network.
Warning: Network interface bond0 on node host2 couldn't talk to itself.
Warning: Network interface bond1 on node host2 couldn't talk to itself."
Exactly same error if I execute that command on host or host2.
I have 2-node cluster, four nics on each host. I've created two bonds on both hosts (two nics on one bond, though all nics at same subnet). Bonding is working ok, so when I'm unplugging lan cables, the other nic gets active and so on.
But when I'm trying to query the ServiceGuard cluster with command 'cmquerycl -v -L /my/lock/disk -n host1 -n host2 -C $SGCONF/foo.ascii' , i'm getting the following error:
"Error: Unable to determine network configuration: failed to receive net probe reply from node host1.
Failed to probe network.
Warning: Network interface bond0 on node host2 couldn't talk to itself.
Warning: Network interface bond1 on node host2 couldn't talk to itself."
Exactly same error if I execute that command on host or host2.
N/A
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-23-2004 07:01 PM
тАО06-23-2004 07:01 PM
Re: ProLiant DL380 ServiceGuard & bonding problem
You need to check if ServiceGuard can handle bonding.
I know it can handle fast failover but it might not be compatible with a bonding configuration.
SEP
I know it can handle fast failover but it might not be compatible with a bonding configuration.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2004 04:54 PM
тАО06-24-2004 04:54 PM
Re: ProLiant DL380 ServiceGuard & bonding problem
SG uses bonding.
The most common problem is using the wrong driver. If you have TG3 - try the BCM5700 driver. Can't remember the appropriate driver for Intel but both are documented in the release notes.
If you need to add the BCM5700 driver and download it - read the install instructions VERY carefully. It is to easy to do it wrong.
Another possible problem (or one to watch out for) is cmclnodelist (and rhosts) not being correctly set up. See section Editing Security Files (chapter 5) in the Users manual.
Happy clustering
The most common problem is using the wrong driver. If you have TG3 - try the BCM5700 driver. Can't remember the appropriate driver for Intel but both are documented in the release notes.
If you need to add the BCM5700 driver and download it - read the install instructions VERY carefully. It is to easy to do it wrong.
Another possible problem (or one to watch out for) is cmclnodelist (and rhosts) not being correctly set up. See section Editing Security Files (chapter 5) in the Users manual.
Happy clustering
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP