- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Distributed Trunking - what is now mutual exclusiv...
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-17-2013 07:26 AM
07-17-2013 07:26 AM
Distributed Trunking - what is now mutual exclusive?
Hi there,
we are going to revisit our network. Currently we have
core1: 5406
core2: 2910al
(connected with 10GbE)
At the moment they "only" serve our virtualization environment via balance-tlb (one host is connected to both switches) for xen-traffic, data and iSCSI.
All downlinks to the edge switches are only connected to core1 (via LACP) at the moment.
On my recherche through the web I stumbled accross distributed trunking which seems to be the jack of all trades for our virt-cluster (I know that the 2910 is not capable of DT, but we would go for a new redundancy-core then).
But I stumbled about some downsides and on some contradictory announcements:
* A lot of sources state that IP routing is not possible with DT enabled - other source state that this should be possible with never firmware
* official 5400 page on HP ProCurve ( 1. ) state that DT is possible to servers AND switches - all other sources I found state that only connection to servers is possible
* All source I found state that IGMP is not supported with DT
Ideal scenario would be to use DT-LACP for the servers and the downlinks to the edge switches to achieve redundancy and the full LACP performance. But we need routing and IGMP support.
Any ideas and suggestions? Any answers to these three points?
Thanks a lot in advance,
phix
ressources:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2013 03:54 PM
07-17-2013 03:54 PM
Re: Distributed Trunking - what is now mutual exclusive?
My understanding was that it does not apply to switch-switch links, only switch-server.
A couple of years ago my colleague set this up and proved it worked, but we never brought it into any production environment as we preferred the option of moving to A-series or Juniper switches and using IRF instead.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2013 02:26 PM
07-18-2013 02:26 PM
Re: Distributed Trunking - what is now mutual exclusive?
Hi,
DT trunking do work with switches, I advise you to use DT-LACP and LACP as these prevents possible loops. As soon as you create a dt it disables STP in those links.
If you really need to use IGMP maybe you should just use redundant links with MSTP enabled. This way you can have redundancy with the other requirements you chose, the only problem is that the redundancy is not as fast as with DT.
Kind regards,
Aarón
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2013 04:03 PM
07-18-2013 04:03 PM
Re: Distributed Trunking - what is now mutual exclusive?
OK, DT-LACP for downstream devices was changed to include servers at some stage in K15 maybe?:
This allows third party devices such as switches, servers, or
any other networking device that supports trunking to interoperate with the distributed trunking
switches (DTSs) seamlessly.
Features not supported include:
• SVLANs in mixed mode on DT or ISC links
• Meshing
• CDP
• GVRP
• Multicast routing
• IPv6 routing
• MLD/MLD snooping on DT VLAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2013 04:28 AM
07-19-2013 04:28 AM
Re: Distributed Trunking - what is now mutual exclusive?
Thanks for your answers! Really appreciate it (and gave Kudos ;-) )
That PDF only states that Multicast Routing is not possible. Do you think/know if normal IGMP snooping support is possible (ip igmp)?
Because then everything would be possible for us and I do the Multicast Routing on an external device and reingest them into the few VLANs where we need em.
Phix
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2013 04:58 AM
07-19-2013 04:58 AM
Re: Distributed Trunking - what is now mutual exclusive?
Hi,
from the Management and configuration guide K.15.09:
Configuring Distributed Trunking
The following parameters must be configured identically on the peer devices or undesirable behavior in traffic flow may occur:
■ The ISC link must have a VLAN interface configured for the same VLAN on both DT switches.
■ VLAN membership for all DT trunk ports should be the same on both DT switches in a DT pair.
■ IGMP-snooping or DHCP-snooping configuration on a DT VLAN should be the same on both DT switches. For example, for a DT, if IGMP-snooping or DHCP-snooping is enabled on a VLANthat has a DT port as a member port of the VLAN, the same must be configured on the peer DT on the same VLAN.
■ Loop-protection configuration on a DT VLAN should be the same for both DT switches.
It seems it should work but I have not tried it.
Aarón
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2013 05:21 AM
07-23-2013 05:21 AM
Re: Distributed Trunking - what is now mutual exclusive?
Thanks for all your help guys, really appreciate it.
phix