![HP ProCurve 1600M Management And Configuration Manual Download Page 251](http://html.mh-extra.com/html/hp/procurve-1600m/procurve-1600m_management-and-configuration-manual_155305251.webp)
Port Status and Configuration
Uni-Directional Link Detection (UDLD)
Configuration Warnings and Event Log Messages
Warning Messages.
The following table shows the warning messages that
may be issued and their possible causes, when UDLD is configured for tagged
ports.
Table 10-3. Warning Messages caused by configuring UDLD for Tagged Ports
CLI Command Example
Warning Message
Possible Problem
link-keepalive 6 Possible configuration
link-keepalive 7
vlan 4
no vlan 22 tagged
20
problem detected on port
6. UDLD VLAN
configuration does not
match the port's VLAN
configuration.
Possible configuration
problem detected on port
7. UDLD VLAN
configuration does not
match the port's VLAN
configuration.
Possible configuration
problem detected on port
18. UDLD VLAN
configuration does not
match the port's VLAN
configuration.
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.
You have attempted to configure tagged UDLD
packets on a port that does not belong to the specified
VLAN. In this example, if port 7 belongs to VLAN 1 and
22, but the user tries to configure UDLD on port 7 to
send tagged packets in VLAN 4, the configuration will
be accepted. The UDLD control packets will be sent
tagged in VLAN 4, which may result in the port being
blocked by UDLD if the user does not configure VLAN
4 on this port.
You have attempted to remove a VLAN on port that is
configured for tagged UDLD packets on that VLAN. In
this example, if port 18, 19, and 20 are transmitting and
receiving tagged UDLD packets for Vlan 22, but the
user tries to remove Vlan 22 on port 20, the
configuration will be accepted. In this case, the UDLD
packets will still be sent on Vlan 20, which may result
in the port being blocked by UDLD if the users do not
change the UDLD configuration on this port.
Note:
If you are configuring the switch via SNMP with the same problematic VLAN configuration choices, the above
warning messages will also be logged in the switch’s event log.
Event Log Messages.
The following table shows the event log messages that
may be generated once UDLD has been enabled on a port.
Table 10-4. UDLD Event Log Messages
Message
Event
I 01/01/06 04:25:05 ports: port 4 is
A UDLD-enabled port has been blocked due to part of the link
deactivated due to link failure.
having failed.
I 01/01/06 06:00:43 ports: port 4 is
A failed link has been repaired and the UDLD-enabled port is no
up, link status is good.
longer blocked.
10-31
Summary of Contents for ProCurve 1600M
Page 1: ...Management and Configuration Guide 8200zl ProCurve Switches K 12 XX www procurve com ...
Page 2: ......
Page 3: ...ProCurve Series 8200zl Switches September 2007 K 12 xx Management and Configuration Guide ...
Page 68: ...Using the Menu Interface Where To Go From Here 3 16 ...
Page 110: ...Using the ProCurve Web Browser Interface Status Reporting Features 5 26 ...
Page 152: ...Switch Memory and Configuration Multiple Configuration Files 6 42 ...
Page 220: ...Time Protocols SNTP Messages in the Event Log 9 28 ...
Page 252: ...Port Status and Configuration Uni Directional Link Detection UDLD 10 32 ...
Page 282: ...Power Over Ethernet PoE Operation PoE Operating Notes 11 30 ...
Page 472: ...Redundancy Switch 8212zl Event Log Messages 15 48 ...
Page 584: ...Monitoring and Analyzing Switch Operation Locating a Device B 74 ...
Page 652: ...Troubleshooting Restoring a Flash Image C 68 ...
Page 660: ...MAC Address Management Viewing the MAC Addresses of Connected Devices D 8 ...
Page 666: ...Monitoring Resources When Insufficient Resources Are Available E 6 ...
Page 670: ...Daylight Savings Time on ProCurve Switches F 4 ...
Page 688: ...18 Index ...
Page 689: ......