- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Problem: ProCurve switches acting like hubs
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
02-15-2007 01:52 AM
02-15-2007 01:52 AM
Problem: ProCurve switches acting like hubs
I found a strange problem on two 4108gl and two 4000M connected as depicted below
A_4108gl ============= B_4108gl
   ||    |            2-ports trunk
   ||    |                (C1+C2)
   ||    |
   ||    D_HP4000m via single link (VLAN 1 only)
   ||
   ||  (C3+C4)
   ||
   C_HP4000m via 2-ports trunk
If I connect a Network Analyzer to every switch I can see all the traffic, not only broadcasts and multicasts as I expected.
I've not configured the "mirror-port XX" command and the "monitor" keyword into any of the existing interfaces.
Here 802.1w is enabled even in no loops can occur..
Same problem after a reboot on the four switches...
Any ideas ?
Thanks in advance
Luigi
Attached the 4108gl configs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2007 12:56 AM
02-16-2007 12:56 AM
Re: Problem: ProCurve switches acting like hubs
sh spanning-tree was not reporting the
TC's that were happening downstream.. If I did a sh span detail and looked at the TC's I was getting tons of them. What this caused was everytime one happend it caused the switch to fast flush the mac table. Since the switch no longer knew where the mac's were they flooded the traffic out all the ports...
Took me weeks to figure out that sh spanning-tree is just a small part of the picture.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2007 07:22 PM
02-16-2007 07:22 PM
Re: Problem: ProCurve switches acting like hubs
command to see if I have topology changes..
I'll keep informed. Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2007 10:43 PM
02-20-2007 10:43 PM
Re: Problem: ProCurve switches acting like hubs
Do I'm missing something ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2007 08:52 PM
02-21-2007 08:52 PM
Re: Problem: ProCurve switches acting like hubs
I found also a strange problem: if I try to re-enable the "mirror-port" I see that always appear the previous configuration (using the port F20 as mirror port and the Trk3 as monitored trunk) and I can't change the configuration.
Via Telnet I got:
W02DBSVR-SW4108(config)# sh monitor
Network Monitoring Port
Mirror Port: F20
Monitoring sources
------------------
Trk3
W02DBSVR-SW4108(config)# no mirror-port F20
mirror-port: Invalid value.
W02DBSVR-SW4108(config)#
W02DBSVR-SW4108(config)# no mirror-port
mirror-port: Invalid value.
W02DBSVR-SW4108(config)#
W02DBSVR-SW4108(config)# mirror-port F2
mirror-port: Invalid value.
W02DBSVR-SW4108(config)#
Even from the menu the switch will always prompt that the monitoring in enabled using port F20:
===========================- TELNET - MANAGER MODE -============================
Switch Configuration - Network Monitoring Port
Monitoring Enabled [No] : Yes
Monitoring Port : F20
Monitor : Ports
Port Type Action | Port Type Action
---- --------- + ------- | ---- --------- + -------
E21 10/100TX | | H17 1000T |
E22 10/100TX | | H18 1000T |
E23 10/100TX | | H19 1000T |
E24 10/100TX | | H20 1000T |
F1 1000T | | H21 1000SX |
F2 1000T | | H22 1000SX |
F3 1000T | | Trk1 Trunk |
F4 1000T | | Trk2 Trunk |
Actions-> Cancel Edit Save Help
we have not the Trk3 configured....
Even if we try to disabled the function and
save, when you exit and reenter we found the oldest configuration
W02DBSVR-SW4108 22-Feb-2007 9:40:55
===========================- TELNET - MANAGER MODE -============================
Switch Configuration - Network Monitoring Port
Monitoring Enabled [No] : No
Actions-> Save
W02DBSVR-SW4108 22-Feb-2007 10:50:58
===========================- TELNET - MANAGER MODE -============================
Switch Configuration - Network Monitoring Port
Monitoring Enabled [No] : Yes
Monitoring Port : F20
Monitor : Ports
Any ideas ?
Thanks in advance
Luigi