KB.15.15

IGMP-related problems

IP multicast (IGMP) traffic that is directed by IGMP does not reach IGMP hosts or a multicast router

connected to a port

IGMP must be enabled on the switch and the affected port must be configured for "Auto" or

"Forward" operation.

IP multicast traffic floods out all ports; IGMP does not appear to filter traffic

The IGMP feature does not operate if the switch or VLAN does not have an IP address configured

manually or obtained through DHCP/Bootp. To verify whether an IP address is configured for the

switch or VLAN, do one of the following:

• Try using the WebAgent: If you can access the WebAgent, then an IP address is configured.

• Try to telnet to the switch console: If you can Telnet to the switch, an IP address is configured.

• Use the switch console interface: From the Main Menu, check the Management Address

Information screen by clicking on:

1. Status and Counters

2. Switch Management Address Information

LACP-related problems

Unable to enable LACP on a port with the interface port-number lacp command. In

this case, the switch displays the following message

Operation is not allowed for a trunked port.

You cannot enable LACP on a port while it is configured as a static Trunk port. To enable LACP

on a static-trunked port:

1. Use the no trunk port-number command to disable the static trunk assignment.

2. Execute interface port-number lacp.

CAUTION: Removing a port from a trunk without first disabling the port can create a traffic loop

that can slow down or halt your network. Before removing a port from a trunk, HP recommends

that you either disable the port or disconnect it from the LAN.

Mesh-related problems

Traffic on a dynamic VLAN does not get through the switch mesh

GVRP enables dynamic VLANs. Ensure that all switches in the mesh have GVRP enabled.

Port-based access control (802.1X)-related problems

NOTE: To list the 802.1X port-access Event Log messages stored on the switch, use show log

802.

See also “Radius-related problems” (page 376).

The switch does not receive a response to RADIUS authentication requests

In this case, the switch attempts authentication using the secondary method configured for the type

of access you are using (console, Telnet, or SSH.)

374 Troubleshooting