- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Blocking a link on GbE2?
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
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
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
тАО12-19-2006 02:33 AM
тАО12-19-2006 02:33 AM
Re: Blocking a link on GbE2?
In stead of dissabling the trunk, try dissabling the physical uplinks themselves. This will assure no traffic gets through. Being that you had a topology change, I would agree with the others in that the ports probably managed to forward data.
I clipped the following from the CLI Guide.
To temporarily disable a port without changing its stored configuration attributes, enter the following command at any prompt:
Main# /oper/port
Note: Be sure to dissable all 4 trunk members.
Because this configuration sets a temporary state for the port, you do not need to use apply or save. The port state
will revert to its original configuration when the GbE2 Interconnect Switch is reset.
I work for HP, but my posts and replies are my own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2006 04:58 AM
тАО12-19-2006 04:58 AM
Re: Blocking a link on GbE2?
Hi, Dennis.
>In stead of dissabling the trunk, try
>dissabling the physical uplinks
Well, that's what I was trying to avoid.
Two commands vs. eight for the entire operation reduces likelyhood of errors significantly.
>Being that you had a topology change, I
>would agree with the others in that the
>ports probably managed to forward data.
Only RSTP data. No switched data came through from the servers hanging off that switch.
And herein lies the mystery...
Since RSTP kept the ports open, why was there even a TCN? The STP didn't really change.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2006 05:13 AM
тАО12-19-2006 05:13 AM
Re: Blocking a link on GbE2?
You might be able to catch the anomaly with a protocol analyzer?
I'll be interested to see what direction your support ticket leads you.
I work for HP, but my posts and replies are my own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2006 08:49 AM
тАО12-19-2006 08:49 AM
Re: Blocking a link on GbE2?
(I don't recall all details, and that web page is not available just now..)
This teaches me another lesson.
In a discussion here the other day (also with Matt Hobbs), I made the assumption
that a port would only change into a bridge link following a "link up".
Apparently, that was very wrong.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-19-2006 01:18 PM
тАО12-19-2006 01:18 PM
Re: Blocking a link on GbE2?
One of the easiest ways to manually force a particular port (or trunk) to become the root port/trunk is to manually change the STP port cost value.
In your setup, you could have increased the port cost value on Switch A's uplinks, forcing it to start using the interconnect ports (17/18) because they would then have a lower STP port cost. Or, you could have decreased the port cost on the interconnect ports to achieve the same thing.
In regards to TCNs, you'll get TCN's anytime a non-Host port changes it's status (examples: blocking to forwarding, forwarding to blocking, link up, link down, etc.)
regards,
-sean
- « Previous
-
- 1
- 2
- Next »