Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- BladeSystem
- >
- BladeSystem - General
- >
- VC/Red Hat Nic Teaming
BladeSystem - General
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
08-14-2007 09:20 AM
08-14-2007 09:20 AM
VC/Red Hat Nic Teaming
Hi All –
I am having a hard time determining what my configuration should to have redundant network paths. I have a c7000 enclosure with several BL 460c Red Hat Servers and I am using a Virtual Connect Module to get to the external mission network.
The first question is:
In order to have redundant paths do I have to set up nic teaming/bonding internal to Red Hat, set it the external uplink ports in a failover connection mode OR both?
The second question is:
I want 6 of my servers to communicate internally through the chassis so I don’t have to run more connections to the switch. Using the Virtual Connect Manager I assigned one of my connections with no uplink ports because I want the comms to stay internal. Then I assigned my servers using server profile to that connection. I can’t communicate between them so obviously I did something wrong. Does this work or are there more configurations to do or is it even possible to do this without getting some runs to the switch?
Thanks in advance for any help!
I am having a hard time determining what my configuration should to have redundant network paths. I have a c7000 enclosure with several BL 460c Red Hat Servers and I am using a Virtual Connect Module to get to the external mission network.
The first question is:
In order to have redundant paths do I have to set up nic teaming/bonding internal to Red Hat, set it the external uplink ports in a failover connection mode OR both?
The second question is:
I want 6 of my servers to communicate internally through the chassis so I don’t have to run more connections to the switch. Using the Virtual Connect Manager I assigned one of my connections with no uplink ports because I want the comms to stay internal. Then I assigned my servers using server profile to that connection. I can’t communicate between them so obviously I did something wrong. Does this work or are there more configurations to do or is it even possible to do this without getting some runs to the switch?
Thanks in advance for any help!
He who walks through airport turnstile sideways is going to Bangkok
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