MTRACE - We do not Receive Audio and Video

If your network appears in mBGP but you are not able to receive any multicast sessions, then there could be a multicast forwarding problem somewhere between your host and the Abilene network. To determine where the problem might be, use the MTRACE command. Because this command polls several routers along the path between the Abilene network and an end station, the process can take a while to complete, especially if there are network problems that prevent certain hosts from responding.

Figure 1 is an MTRACE from the Abilene network to the host ping-dnvr.abilene.ucaid.edu (198.32.10.210). Notice that the last line in the trace is the host, "ping-dnvr", indicating that the trace completed properly and, therefore, "ping-dnvr" should be able to receive multicast traffic.

Figure 2 shows an mtrace to 128.197.8.116 that failed to complete. In this example, the host does not appear on the last line, indicating that multicast traffic may not be reaching this host. The last valid hop is the second one, 192.5.89.9, and that the third hop, 192.5.89.202, didn't respond. Therefore, the problem may lie at the set between these two networks, the Northern Crossroads (192.5.89.9) and Boston University (192.5.89.202).