- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 5406 Multiple Trunks
Switches, Hubs, and Modems
1753518
Members
5007
Online
108795
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
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
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
тАО11-15-2008 09:45 AM
тАО11-15-2008 09:45 AM
5406 Multiple Trunks
I have 2 5406's connected to each other via a 4gb trunk called Trk1. This trunk is tagged on all my VLANs.
I have an ISCSI storage array and that traffic is init's own VLAN (VLAN5). It's been suggested by my storage vendor that the storage vlan should be using it's own trunk and not Trk1. I've created a new 8gb Trunk (Trk3) and have tagged it on VLAN5 and also removed Trk1 from VLAN5. I've tested pinging from 1 core to the other, but is not working.
Is this a supported configuration? If yes any suggestions on what may be wrong?
I have an ISCSI storage array and that traffic is init's own VLAN (VLAN5). It's been suggested by my storage vendor that the storage vlan should be using it's own trunk and not Trk1. I've created a new 8gb Trunk (Trk3) and have tagged it on VLAN5 and also removed Trk1 from VLAN5. I've tested pinging from 1 core to the other, but is not working.
Is this a supported configuration? If yes any suggestions on what may be wrong?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2008 10:54 AM
тАО11-15-2008 10:54 AM
Re: 5406 Multiple Trunks
you can do this, but need to have mstp. with stp or rstp one of the trunks is in blocking.
ben
ben
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2008 08:09 AM
тАО11-16-2008 08:09 AM
Re: 5406 Multiple Trunks
thanks ben. how can i confirm what spanning tree method i'm using? i ran show spanning-tree config and this is what i rec'd...
Multiple Spanning Tree (MST) Configuration Information
STP Enabled [No] : Yes
Force Version [MSTP-operation] : MSTP-operation
Default Path Costs [802.1t] : 802.1t
MST Configuration Name : 001560f7ea00
MST Configuration Revision : 0 Switch Priority : 0
Forward Delay [15] : 15 Hello Time [2] : 2
Max Age [20] : 20 Max Hops [20] : 20
Multiple Spanning Tree (MST) Configuration Information
STP Enabled [No] : Yes
Force Version [MSTP-operation] : MSTP-operation
Default Path Costs [802.1t] : 802.1t
MST Configuration Name : 001560f7ea00
MST Configuration Revision : 0 Switch Priority : 0
Forward Delay [15] : 15 Hello Time [2] : 2
Max Age [20] : 20 Max Hops [20] : 20
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