- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: UDLD on trunk
Switches, Hubs, and Modems
1753361
Members
5324
Online
108792
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
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
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
тАО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
- 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
- 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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP