- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Alletra 6000 peer persistance and MC-LAG
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
Forums
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
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
Monday - last edited Monday by support_s
Monday - last edited Monday by support_s
Alletra 6000 peer persistance and MC-LAG
Hi,
we have 2 DC's both with an Alletra 6000. both DC's have 4 esxi hosts per DC and datacenters are interconnected based on juniper switches (QFX).
In DC1 we have two peer switches configured for MC-LAG
In DC2 we have two peer switches configured for MC-LAG
so basically each datacenter has its own MC-LAG setup for connecting switches and servers that are able to use LACP. ESXi hosts and alletra is configured based on trunk and access ports.
Peer switch 1 of DC1 is connected via a high bandwidth port to peer switch 1 of DC2
Peer switch 2 of DC1 is connected via a high badnwidth port to peer switch 2 of DC2
On both DCs a MC-LAG is congfigured for both high bandwidth ports for iSCSI and replication traffic that is trunked on this MC-LAG ae100 configuration.
I can't verify if this configuration is supported, or that we should use dedicated intra datacenter connections between peer switches, so for example iSCSI1 runs on peer 1 over both DC's and iSCSI2 runs on peer 2 over both DC's. regarding the available bandwidth we may combine iSCSI and replication traffic over these two inter datacenter connections.
- Tags:
- Port
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Monday
Re: Alletra 6000 peer persistance and MC-LAG
Hi Convergo,
In some cases, combining iSCSI traffic and replication traffic on a shared MC-LAG may be a viable option.
Dedicated connections for iSCSI traffic across DCs (using peer 1 and peer 2) would be a safer choice, especially for workloads that are latency sensitive.
As an alternative, QoS can be implemented on the MC-LAG in order to prioritize iSCSI traffic if the bandwidth is sufficient.
Make sure the configuration is compatible with HPE and Juniper before proceeding.
Hope this helps.
Regards,
Satish
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Monday
Query: Alletra 6000 peer persistance and MC-LAG
System recommended content:
Please click on "Thumbs Up/Kudo" icon to give a "Kudo".
Thank you for being a HPE valuable community member.