I am stumped. I am trying to perform multicast across two NetVanta 6247 with AOSR10.8.0. Each NetVanta is connected via port eth0/2 with a laptop at eth0/1 running TfGen/Mcast/Mikkle Multicast test tools. Each router is running OSPF advertising their respective networks with ping, telnet, and http working as expected in my closed test network. I believe i have configured the needed commands:

NetVanta 1:

ip multicast-routing

!

interface eth 0/1

ip address 198.162.0.10 255.255.255.248

ip pim sparse-mode

media-gateway ip primary

no shutdown

!

!

interface eth 0/2

description eth0/2

ip address 198.162.0.33 255.255.255.248

ip pim sparse-mode

no awcp

no shutdown

!

!

router ospf

default-information originate

network 198.162.0.8 0.0.0.7 area 0

network 198.162.0.32 0.0.0.7 area 0

redistribute static subnets

redistribute connected subnets

!

router pim-sparse

rp-address 198.162.0.10

!

NetVanta 2:

ip multicast-routing

!

interface eth 0/1

ip address 198.162.0.26 255.255.255.248

ip pim sparse-mode

ip pim-sparse dr-priority 20

media-gateway ip primary

no awcp

no shutdown

!

!

interface eth 0/2

description eth0/2

ip address 198.162.0.34 255.255.255.248

ip pim sparse-mode

no awcp

no shutdown

!

!

router ospf

default-information originate

network 198.162.0.24 0.0.0.7 area 0

network 198.162.0.32 0.0.0.7 area 0

redistribute static subnets

redistribute connected subnets

!

router pim-sparse

rp-address 198.162.0.10

!

We have configured a hardware firewall, CISCO routers and switches passing multicast traffic crossing our switches/routers/firewall between networks. We are looking to place the NetVantas in our test network.

What am i missing here?

I have used the debug utilities for mroute, pim-sparse hello, pim-sparse joinprune, igmp, and pim-sparse packets. It looks line joins are happening and packets are passing.

I have laptop 198.162.0.27 generating packets to group 224.4.4.1 (5000) and looking to join group 224.4.4.2 (5002). Laptop 198.162.0.11 is generating to group 224.4.4.2 (5002) and wanting to join 224.4.4.1 (5000).

Thank you for asking this question in the support community. When you get a chance, will you elaborate on the network design? In this lab application, are the two ADTRAN's connected directly via Ethernet 0/2, or are there routers, switches, and a firewall between the devices? I'm not familiar with the multicast testing devices you used, but one portion of the testing tool that often gets overlooked is the time to live (TTL) value. The TTL value must be greater than (1) when traversing more than one router.

The Configuring Multicast Routing in AOS guide has recommended ways to troubleshoot all configurations of multicast. If an entry is not in the Multicast routing table for a stream that needs to traverse this router, the troubleshooting needs to begin at the destination and work back towards the source. In Multicast networks, the source will usually be streaming constantly, whether or not there is any device listening. This means that the destination will initiate the request, which is why the troubleshooting should begin there.

The first point of failure is the easiest to check out. Ping or connect to the Multicast source in a Unicast manner to ensure that the Unicast route table is operating properly. The second point of failure is in the initial IGMP request from the end device. This will need to be debugged from the Stub router. To start the debug process, issue the following command (from enable mode):

# debug ip igmp

This will show that the router received the join message for Multicast group, forwarded it along to the router connected to the upstream interface. It will also show if it sent out a periodic query on the downstream interface to ensure that the end device is real and is still actively listening.

The next point of failure is in the Multicast routing table of either the stub router of the PIM cloud. You can check each router’s table constantly, or debug all changes to the table as they happen with the following command (from enable mode):

# debug ip mrouting

If at any point along the chain back to the source, the Multicast routing table updates are not received, there is most likely a mis-configuration or line error in the segment leading from the previous link in the chain.

I hope that makes sense, but please do not hesitate to reply to this post with additional debug information, or questions. I will be happy to help in any way I can.

Thanks for the reply. I followed the "Configuration Multicast Routing AOS" guide in setting up and debugging my network. I have used the various multicast "sho ip ..." commands and will provide a copy of the output. However, they seem to show joins and information at both Eth0/1 for prunes and joins, however, no traffic crossing Eth0/2 except RP information.

Both laptops are able to ping each other and both laptops are able to web and telnet into both ADTRAN routers. The laptops are taken directly from the CISCO based network (routers with same IP address and physical setup as ADTRAN network) and plugged into the ADTRAN network. Multicast passes as expected in the controlled CISCO network.

I have included three files. "Router dot 10 Node 1 Multicast CMDs 2 Jan 13.rtf" is router Node 1, "Router dot 10 Node 2 Multicast CMDs 2 Jan 13.rtf" for router node 2, and "Multicast Packet TTL set to 6 2 Jan 13.txt" which is the Wireshark packet capture. The Wireshark capture is just one packet, but it shows the TTL for the multicast packet (> 1). The source for the multicast is 198.162.0.11. The listener/receiver address is the laptop 198.162.0.27.

Thank you for following up. I finished reproducing your setup and testing, and everything worked properly the first time. In the configuration output you pasted in the first post, you specified the RP in both configurations. Were there more than these two routers?