- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Problems with distributed-trunks
Switches, Hubs, and Modems
1752786
Members
5979
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
- 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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP