IBM RackSwitch G8000, Инструкция по применению

Страница: 228 / 362

226
RackSwitch G8000: Application Guide
Troubleshooting
This section provides the steps to resolve common IGMP Snooping configuration
issues. The topology described in Figure 20 is used as an example.
Multicast traffic from non-member groups reaches the host or Mrouter
• Check if traffic is unregistered. For unregistered traffic, an IGMP entry is not
displayed in the IGMP groups table.
• Ensure IPMC flooding is disabled and CPU is enabled.
• Check the egress port’s VLAN membership. The ports to which the hosts and
Mrouter are connected must be used only for VLAN 2 and VLAN 3.
Note: To avoid such a scenario, disable IPMC flooding for all VLANs enabled on
the switches (if this is an acceptable configuration).
• Check IGMP Reports on switches B and C for information about the IGMP
groups.
If the non-member IGMP groups are displayed in the table, close the application
that may be sending the IGMP Reports for these groups.
Identify the traffic source by using a sniffer on the hosts and reading the source
IP/MAC address. If the source IP/MAC address is unknown, check the port
statistics to find the ingress port.
• Ensure no static multicast MACs, static multicast groups, or static Mrouters are
configured.
• Ensure IGMP Relay and PIM are not configured.
Not all multicast traffic reaches the appropriate receivers.
• Ensure hosts are sending IGMP Reports for all the groups. Check the VLAN on
which the groups are learned.
If some of the groups are not displayed, ensure the multicast application is
running on the host device and the generated IGMP Reports are correct.
RS G8000#
show ip igmp groups
RS G8000(config)#
vlan
<vlan id>
RS G8000(config-vlan)#
no flood
RS G8000(config-vlan)#
cpu
RS G8000#
show vlan
RS G8000#
show ip igmp groups
RS G8000#
show interface port
<port id>
interface-counters
RS G8000#
show ip igmp groups