- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- multiple VLAN traffic flooding, 5406zl core switch...
Switches, Hubs, and Modems
1753792
Members
7304
Online
108799
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
11-13-2008 06:28 AM
11-13-2008 06:28 AM
multiple VLAN traffic flooding, 5406zl core switch?
This is a shot in the dark, as my other resources have turned up nothing and we've got nothing to lose.
We had a company-wide network outage yesterday which we traced back to a failing VoIP phone spewing gibberish packets. Our VoIP network is physically separated from the data network, as well as having a different VLAN ID. We also have a remote datacenter connected via metro ethernet, also with a separate VLAN ID. The only place all three networks come together, both physically and virtually, is in our 5406zl core switch. This switch does the inter-VLAN routing, as well as sends traffic out our public gateway.
The babbling phone effectively shut down all three VLANs. None of the switches (all procurve) showed any alerts about excessive traffic. We had to find the defective device by looking at link lights. As soon as we disconnected the phone, network response was back to normal.
All the VoIP phones do is boot off of a phone server on their own VLAN, download their configuration, and pass voice traffic. They have no need to contact the other VLANs. Does it make any sense that the core switch, which has fault detection set to high, should've been forwarding this traffic? Shouldn't the downstream switch (a 2626PWR) have blocked this port? Since we can't retroactively apply a packet sniffer, what else can we trace?
Like I said, a shot in the dark, but any thoughts would be appreciated.
We had a company-wide network outage yesterday which we traced back to a failing VoIP phone spewing gibberish packets. Our VoIP network is physically separated from the data network, as well as having a different VLAN ID. We also have a remote datacenter connected via metro ethernet, also with a separate VLAN ID. The only place all three networks come together, both physically and virtually, is in our 5406zl core switch. This switch does the inter-VLAN routing, as well as sends traffic out our public gateway.
The babbling phone effectively shut down all three VLANs. None of the switches (all procurve) showed any alerts about excessive traffic. We had to find the defective device by looking at link lights. As soon as we disconnected the phone, network response was back to normal.
All the VoIP phones do is boot off of a phone server on their own VLAN, download their configuration, and pass voice traffic. They have no need to contact the other VLANs. Does it make any sense that the core switch, which has fault detection set to high, should've been forwarding this traffic? Shouldn't the downstream switch (a 2626PWR) have blocked this port? Since we can't retroactively apply a packet sniffer, what else can we trace?
Like I said, a shot in the dark, but any thoughts would be appreciated.
White water rafting on a river of acid
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