Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- NIC Teaming on Linux BL20pG3
ProLiant Servers (ML,DL,SL)
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-12-2005 02:25 AM
11-12-2005 02:25 AM
NIC Teaming on Linux BL20pG3
I'm in research mode at this point, not yet a user, and have the following HA questions:
Q1: I understand that there is support for NIC teaming on Linux but is it true that dual channel NIC teaming is not currently supported (on RH | Suse)?
Q2: If Q1 is true, how can one remove a given switch (A | B) as a single-point-of-failure within the blade enclosure? I'm left with NIC redundancy but not switch redundancy.
For instance, on a given server, I'd like to team (bond) server ports 1 & 3 which connect via the backplane to both switches - if one of the switches dies, the connection is still available via the other switch.
However, if Q1 above is true, I'm able to team only server ports 1 & 2 which connect via the backplane to Switch A - if switch A goes, the connection is severed.
Are my assumptions correct or am I missing something here?
Thanks in advance
JH
Q1: I understand that there is support for NIC teaming on Linux but is it true that dual channel NIC teaming is not currently supported (on RH | Suse)?
Q2: If Q1 is true, how can one remove a given switch (A | B) as a single-point-of-failure within the blade enclosure? I'm left with NIC redundancy but not switch redundancy.
For instance, on a given server, I'd like to team (bond) server ports 1 & 3 which connect via the backplane to both switches - if one of the switches dies, the connection is still available via the other switch.
However, if Q1 above is true, I'm able to team only server ports 1 & 2 which connect via the backplane to Switch A - if switch A goes, the connection is severed.
Are my assumptions correct or am I missing something here?
Thanks in advance
JH
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP