- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- VLAN leakage
Switches, Hubs, and Modems
1823950
Members
3662
Online
109667
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
Forums
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
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
02-16-2007 04:38 AM
02-16-2007 04:38 AM
VLAN leakage
Here is a little warning to you; remember to *not* tag any VLANs on a port that shouldn't have it. The reason is AFAIK as follows: a IP packet sent out on a port (broadcast) is received at its peer. Now, since the VLAN is not configured on the switch, the packet is tossed. However, the switch has seen the MAC address on the port. This is really bad and can cause a 'loop-like' situation.
We saw this because of parallell links with VLANs and Martini tunnels (MPLS). The switch (5304xl) insisted on seeing a given MAC address on the wrong interface, and tried to send traffic out on a port that didn't have the proper connection.
We discovered a similar thing during a broadcast storm. One switch (2626) had big problems, but didn't have the VLAN in question defined. The trick was to remove the VLAN from the interface on core side of the link.
Another thing; defining the VLAN on the switch, and leaving it without any ports tagged or untagged, also worked. This baffles me. Must be some poor design somewhere.
We saw this because of parallell links with VLANs and Martini tunnels (MPLS). The switch (5304xl) insisted on seeing a given MAC address on the wrong interface, and tried to send traffic out on a port that didn't have the proper connection.
We discovered a similar thing during a broadcast storm. One switch (2626) had big problems, but didn't have the VLAN in question defined. The trick was to remove the VLAN from the interface on core side of the link.
Another thing; defining the VLAN on the switch, and leaving it without any ports tagged or untagged, also worked. This baffles me. Must be some poor design somewhere.
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.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP