Filter
Top Products
Troubleshooting IP Multicast Switching (IPMS) Troubleshooting IPMS in Debug CLI
OmniSwitch Troubleshooting Guide September 2005 page 14-7
Troubleshooting IPMS in Debug CLI
The Debug CLI will allow you to view traffic traversing the switch in many ways. The most useful
command for troubleshooting IP Multicast is:
-> debug ip packet show-multicast on board ni 1 output console
This command turns on debug for IP packets, turns on the ability to show multicast packets, looks only on
blade #1, and outputs to console. The output is:
-> 1 R IPM 00d095206406->(01005e000001) IP 10.10.10.190->224.0.0.1 IGMPv2 MQ
1 S CMM 00d095206406->01005e000001 IP 10.10.10.190->224.0.0.1 IGMPv2 MQ
1 R IPM 00a0c955af3e->(01005e4d0100) IP 10.10.10.51->224.77.1.0 IGMPv2 MR
1 S CMM 00a0c955af3e->01005e4d0100 IP 10.10.10.51->224.77.1.0 IGMPv2 MR
1 R IPM 00c04f0c3b2d->(01005e7ffffe) IP 10.10.10.5->239.255.255.254 IGMPv2 MR
1 S CMM 00c04f0c3b2d->01005e7ffffe IP 10.10.10.5->239.255.255.254 IGMPv2 MR
1 R IPM 00c04f0c3b2d->(01005e7ffffe) IP 10.10.10.5->239.255.255.254 IGMPv2 MR
1 S CMM 00c04f0c3b2d->01005e7ffffe IP 10.10.10.5->239.255.255.254 IGMPv2 MR
1 R IPM 0060971c0c45->(01005e000009) IP 10.10.10.220->224.0.0.9 IGMPv2 MR
1 S CMM 0060971c0c45->01005e000009 IP 10.10.10.220->224.0.0.9 IGMPv2 MR
1 R IPM 0008c709f671->(01005e3796d0) IP 10.10.10.222->229.55.150.208 IGMPv2 MR
1 S CMM 0008c709f671->01005e3796d0 IP 10.10.10.222->229.55.150.208 IGMPv2 MR
1 R IPM 0008c709f671->(01005e3796d0) IP 10.10.10.222->229.55.150.208 IGMPv2 MR
1 S CMM 0008c709f671->01005e3796d0 IP 10.10.10.222->229.55.150.208 IGMPv2 MR
1 R IPM 00d095265480->(01005e000004) IP 10.10.10.34->224.0.0.4 IGMPv1 DV RSP
1 S CMM 00d095265480->01005e000004 IP 10.10.10.34->224.0.0.4 IGMPv1 DV RSP
1 R IPM 00a0c955af3e->(01005e4db6d6) IP 10.10.10.51->224.77.182.214 IGMPv2 MR
1 S CMM 00a0c955af3e->01005e4db6d6 IP 10.10.10.51->224.77.182.214 IGMPv2 MR
1 R IPM 0008c709f671->(01005e000118) IP 10.10.10.222->224.0.1.24 IGMPv2 MR
1 S CMM 0008c709f671->01005e000118 IP 10.10.10.222->224.0.1.24 IGMPv2 MR
1 R IPM 0008c709f671->(01005e000118) IP 10.10.10.222->224.0.1.24 IGMPv2 MR
1 S CMM 0008c709f671->01005e000118 IP 10.10.10.222->224.0.1.24 IGMPv2 MR
1 R IPM 0010a4c59c87->(01005e000116) IP 10.10.10.54->224.0.1.22 IGMPv2 MR
1 S CMM 0010a4c59c87->01005e000116 IP 10.10.10.54->224.0.1.22 IGMPv2 MR
1 R IPM 0010a4c59c87->(01005e000116) IP 10.10.10.54->224.0.1.22 IGMPv2 MR
1 S CMM 0010a4c59c87->01005e000116 IP 10.10.10.54->224.0.1.22 IGMPv2 MR
For this example, Ghost was used to multicast to a client as follows: Ghost server at 10.10.10.222,
connected to an OSR9, which was uplinked to a Falcon 7700 via 10/100 Ethernet on 1/22; the Ghost
multicast client was at 10.10.10.51 on 1/7. From the output, we can see that the client is receiving a stream
with multicast address 224.77.182.214, which matches with the output of the show ip multicast
forwarding command:
-> show ip multicast forwarding
Source Destination
Multicast Group Source IP Type VLAN Slot/Port Type VLAN Slot/Port
-------------------+-------------------+----+----+---------+----+----+---------
224.77.182.214 10.10.10.222 NATV 1 1/22 NATV 1 1/7
Showing the IP address of the source of the actual stream as 10.10.10.222.