- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- LACP Active/Active with VC connected directly to N...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
07-13-2012 03:11 AM
07-13-2012 03:11 AM
LACP Active/Active with VC connected directly to NetApp filer
Hi, twice now (for two seperate customers) I have experienced the same issue
We have two, stacked, VC modules in the back of a C7000 enclosure
We have two, failover, NetApp filers in a cluster
We connect, using a crossed configuration - 4 X Fibre Ethernet cables between the VC modules and the filers
Expected outcome:
Active/Active/Active/Active - in two seperate LACP trunks; one LACP trunk per filer
Actual outcome:
Active/passive/passive/passive
This means that we can only communicate with one filer at a time with this configuration
In both instances I have had to work around this issue by creating two seperate networks, one for each filer in seperate broadcast domains. This eliminates any possibility for a redundant configuration
I suspect that if I was to install a 10GbE switch between the VC and the NetApp filers that the negotiation would work properly and I could have a fully active and redundant configuration
My question is, is it a supported configuration to have a VC module connected directly into a NetApp filer and expect two full active LACP trunks within the same broadbast domain? If so, how is this acheived?
I have attached two very simple diagrams to show what I want and what I get. Only a single switch is drawn because the switch is supposed to be stacked
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2012 08:05 AM
07-13-2012 08:05 AM
Re: LACP Active/Active with VC connected directly to NetApp filer
As far as I've heard that is not a support configuration, as the VC is technically a Layer-2 device and not a switch. To get LACP you need a swtich to manage/create that connection; keep in mind you wouldn't need an external switch, it could be another interconnect.
The only supported direct attached FC storage is 3Par.