Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Problems with distributed-trunks
Switches, Hubs, and Modems
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
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
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-08-2011 01:05 AM
06-08-2011 01:05 AM
Problems with distributed-trunks
I'm having some issues with the following setup.
Two 5400 switches each with latest firmware (K.15.03.0007) connected via switch-interconnect for allowing servers to be connected redundant.
In this example the server (RHEL6) with bonding (802.3ad) eth8/eth9 and tagged vlans (vid 100 and 108) is connected to both switches on port b20 which is configured as trk55 with dt-lacp.
After "failing" switch0 by disabling port b20 only the ip on vlan 108 is reachable. Trying to fail switch1 both vlans are reachable on the server.
I noticed also, that in regular operation only one server interface is used for communication. I'm used to see traffic beeing splitted over all interfaces using all slave interfaces.
What's the mistake?
switch0:
switch-interconnect Trk1
trunk A23-A24,B1-B4 Trk1 LACP
trunk B20 Trk55 dt-lacp
spanning-tree
spanning-tree instance 1 vlan 100-200 301-400
spanning-tree instance 1 priority 0
spanning-tree instance 2 vlan 1-99 201-300
spanning-tree instance 2 priority 1
spanning-tree priority 0
primary-vlan 100
management-vlan 108
switch1:
switch-interconnect Trk1
trunk A23-A24,B1-B4 Trk1 LACP
trunk B20 Trk55 dt-lacp
spanning-tree
spanning-tree instance 1 vlan 100-200 301-400
spanning-tree instance 1 priority 1
spanning-tree instance 2 vlan 1-99 201-300
spanning-tree instance 2 priority 0
spanning-tree priority 1
primary-vlan 100
management-vlan 108
Thanks and best regards
Two 5400 switches each with latest firmware (K.15.03.0007) connected via switch-interconnect for allowing servers to be connected redundant.
In this example the server (RHEL6) with bonding (802.3ad) eth8/eth9 and tagged vlans (vid 100 and 108) is connected to both switches on port b20 which is configured as trk55 with dt-lacp.
After "failing" switch0 by disabling port b20 only the ip on vlan 108 is reachable. Trying to fail switch1 both vlans are reachable on the server.
I noticed also, that in regular operation only one server interface is used for communication. I'm used to see traffic beeing splitted over all interfaces using all slave interfaces.
What's the mistake?
switch0:
switch-interconnect Trk1
trunk A23-A24,B1-B4 Trk1 LACP
trunk B20 Trk55 dt-lacp
spanning-tree
spanning-tree instance 1 vlan 100-200 301-400
spanning-tree instance 1 priority 0
spanning-tree instance 2 vlan 1-99 201-300
spanning-tree instance 2 priority 1
spanning-tree priority 0
primary-vlan 100
management-vlan 108
switch1:
switch-interconnect Trk1
trunk A23-A24,B1-B4 Trk1 LACP
trunk B20 Trk55 dt-lacp
spanning-tree
spanning-tree instance 1 vlan 100-200 301-400
spanning-tree instance 1 priority 1
spanning-tree instance 2 vlan 1-99 201-300
spanning-tree instance 2 priority 0
spanning-tree priority 1
primary-vlan 100
management-vlan 108
Thanks and best regards
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 2021 Hewlett Packard Enterprise Development LP