Configuration Warnings And Event Log Messages - HP ProCurve 6120G/XG Configuration Manual

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
link-keepalive 6 Possible configuration
problem detected on port
6. UDLD VLAN configuration
does not match the port's
VLAN configuration.
link-keepalive 7 Possible configuration
vlan 4 problem detected on port
7. UDLD VLAN configuration
does not match the port's
VLAN configuration.
no vlan 22 tagged Possible configuration
20 problem detected on port
18. UDLD VLAN
configuration does not
match the port's VLAN
configuration.
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
I 01/01/06 04:25:05 ports: port 4 is
deactivated due to link failure.
I 01/01/06 06:00:43 ports: port 4 is
up, link status is good.
Uni-Directional Link Detection (UDLD)
Possible Problem
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.
Event
A UDLD-enabled port has been blocked due to part of the link
having failed.
A failed link has been repaired and the UDLD-enabled port is no
longer blocked.
Port Status and Configuration
10-37