HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- RHEL 2.1 update 5: bonding up but not stable
Operating System - Linux
1831593
Members
2994
Online
110027
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
01-06-2005 09:28 PM
01-06-2005 09:28 PM
RHEL 2.1 update 5: bonding up but not stable
We are using the HP Ethernet bonding driver in RHEL 2.1. There are two bonds on each box, one to the NetApps, one to the rest of the network. Each bond is set to fail over on link failure. But the kernel keeps seeing a link failure when there isn't one (mii checks every 100ms and can't see one) and switching to the other link, flapping roughly every few hours.
I've kludged around it by setting the downdelay to 2000ms (so it waits two seconds before flapping), but it's still trying to flap.
It's happening on two (identical) boxes in two locations, each with two separate bonded links, each of whose two links goes to different switches - I'm confident it's not dodgy hardware.
The boxes are DL580 G2, quad 3GHz, 16 gig memory. The kernel is 2.4.9e49-enterprise. The bonding driver is HP driver 1.0.4q (haven't tried the kernel driver, did 2.4.9 even have it included?). The card driver is HP driver e1000-5.4.11a-1. The switches are Ciscos, not sure what model - they don't see a link failure either.
We have other RHAS2.1 boxes (DL360s) going to the same switches which do not show this behaviour. Those boxes only have one bond each, though - these boxes are the only ones with two bonds.
We tried going to kernel 2.4.9e57, but bonding driver 1.0.4q doesn't say it supports that, and bonding doesn't seem to work. So I can't upgrade the driver (perhaps 1.0.4r will support the current kernel).
Has anyone seen or heard of this behaviour?
I've kludged around it by setting the downdelay to 2000ms (so it waits two seconds before flapping), but it's still trying to flap.
It's happening on two (identical) boxes in two locations, each with two separate bonded links, each of whose two links goes to different switches - I'm confident it's not dodgy hardware.
The boxes are DL580 G2, quad 3GHz, 16 gig memory. The kernel is 2.4.9e49-enterprise. The bonding driver is HP driver 1.0.4q (haven't tried the kernel driver, did 2.4.9 even have it included?). The card driver is HP driver e1000-5.4.11a-1. The switches are Ciscos, not sure what model - they don't see a link failure either.
We have other RHAS2.1 boxes (DL360s) going to the same switches which do not show this behaviour. Those boxes only have one bond each, though - these boxes are the only ones with two bonds.
We tried going to kernel 2.4.9e57, but bonding driver 1.0.4q doesn't say it supports that, and bonding doesn't seem to work. So I can't upgrade the driver (perhaps 1.0.4r will support the current kernel).
Has anyone seen or heard of this behaviour?
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP