Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: UDLD on trunk
Switches, Hubs, and Modems
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
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
- Email to a Friend
- Report Inappropriate Content
10-27-2009 07:42 AM
10-27-2009 07:42 AM
UDLD on trunk
Hi all,
when i try to enable UDLD on a port that is part of a Trunk i get the following warning:
"udld: Possible configuration problem detected on port E1.UDLD VLAN configuration does not match port's VLAN configuration."
But VLAN configuration seem so be OK :
sh trunk
Load Balancing
Port | Name Type | Group Type
---- + -------------------------------- --------- + ----- -----
E1 | 1000LX | Trk1 Trunk
F1 | 1000LX | Trk1 Trunk
sh vlan port Trk1
Status and Counters - VLAN Information - for ports Trk1
VLAN ID Name | Status Voice Jumbo
------- -------------------- + ---------- ----- -----
1 DEFAULT_VLAN | Port-based No No
5 VoIP_VLAN | Port-based Yes No
200 Link200 | Port-based No No
202 Link202 | Port-based No No
206 Link206 | Port-based No No
211 Link211 | Port-based No No
214 Link214 | Port-based No No
sh vlan 1
Status and Counters - VLAN Information - VLAN 1
VLAN ID : 1
Name : DEFAULT_VLAN
Status : Port-based
Voice : No
Jumbo : No
Port Information Mode Unknown VLAN Status
---------------- -------- ------------ ----------
Trk1 Untagged Learn Up
sh link-keepalive
Total link-keepalive enabled ports: 1
Keepalive Retries: 4
Keepalive Interval: 5 sec
Physical Keepalive Adjacent UDLD
Port Enabled Status Status Switch VLAN
----- ------- ---------------- --------- ------------- ----------
E1 Yes up up 0019bb-081400 untagged
The following are the Switch I manage:
Procurve 5406 firmware 13.49
Procurve 8212 firmware 13.45
Regards,
Marco
when i try to enable UDLD on a port that is part of a Trunk i get the following warning:
"udld: Possible configuration problem detected on port E1.UDLD VLAN configuration does not match port's VLAN configuration."
But VLAN configuration seem so be OK :
sh trunk
Load Balancing
Port | Name Type | Group Type
---- + -------------------------------- --------- + ----- -----
E1 | 1000LX | Trk1 Trunk
F1 | 1000LX | Trk1 Trunk
sh vlan port Trk1
Status and Counters - VLAN Information - for ports Trk1
VLAN ID Name | Status Voice Jumbo
------- -------------------- + ---------- ----- -----
1 DEFAULT_VLAN | Port-based No No
5 VoIP_VLAN | Port-based Yes No
200 Link200 | Port-based No No
202 Link202 | Port-based No No
206 Link206 | Port-based No No
211 Link211 | Port-based No No
214 Link214 | Port-based No No
sh vlan 1
Status and Counters - VLAN Information - VLAN 1
VLAN ID : 1
Name : DEFAULT_VLAN
Status : Port-based
Voice : No
Jumbo : No
Port Information Mode Unknown VLAN Status
---------------- -------- ------------ ----------
Trk1 Untagged Learn Up
sh link-keepalive
Total link-keepalive enabled ports: 1
Keepalive Retries: 4
Keepalive Interval: 5 sec
Physical Keepalive Adjacent UDLD
Port Enabled Status Status Switch VLAN
----- ------- ---------------- --------- ------------- ----------
E1 Yes up up 0019bb-081400 untagged
The following are the Switch I manage:
Procurve 5406 firmware 13.49
Procurve 8212 firmware 13.45
Regards,
Marco
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-01-2009 02:47 AM
11-01-2009 02:47 AM
Re: UDLD on trunk
You can check this document
http://cdn.procurve.com/training/Manuals/2900-MCG-Jan08-10-Ports.pdf#27
There you will find the way to configure UDLD on Trunk ports and group.
Regards,
Islam Hassan
http://cdn.procurve.com/training/Manuals/2900-MCG-Jan08-10-Ports.pdf#27
There you will find the way to configure UDLD on Trunk ports and group.
Regards,
Islam Hassan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-02-2009 12:06 AM
11-02-2009 12:06 AM
Re: UDLD on trunk
The configuration was made by following that manual. And according to the same manual, the warning:
"Possible configuration problem detected on port xx. UDLD VLAN configuration does not match the port's VLAN configuration."
has the following mening:
"You have attempted to enable UDLD on a port that is a tagged only port, but did not specify a configuration for tagged UDLD control packets. In this example, the switch will send and receive the UDLD control packets untagged despite issuing this warning"
As you can see on my first post, trunk ports are part of both tagged and untagged ports, then they are not "tagged only ports".
Am I missing something ?
That warning is confusing me........
"Possible configuration problem detected on port xx. UDLD VLAN configuration does not match the port's VLAN configuration."
has the following mening:
"You have attempted to enable UDLD on a port that is a tagged only port, but did not specify a configuration for tagged UDLD control packets. In this example, the switch will send and receive the UDLD control packets untagged despite issuing this warning"
As you can see on my first post, trunk ports are part of both tagged and untagged ports, then they are not "tagged only ports".
Am I missing something ?
That warning is confusing me........
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP