You are on page 1of 4

This is a simple six step process for trouble-shooting terrestrial multicast issues. Step 1.

Check to see what PIM neighbor relationships have been formed between the router and the Provider edge router
( How it should look) Router#sho ip pim nei PIM Neighbor Table Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, S - State Refresh Capable Neighbor Interface Uptime/Expires Ver DR Address Prio/Mode x.x.x.x Serial0/0/0 11w0d/00:01:44 v2 1 / S (How a problem store might look if no relationship with the provider is seen) Router#sho ip pim nei PIM Neighbor Table Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, S - State Refresh Capable Neighbor Interface Uptime/Expires Ver DR Address Prio/Mode Note that we see no WAN IP between router and provider edge router This could be due to the LEC not having multicast enabled on their end or it may not be enabled on our end.

Step 2. Verify router is configured for IP multicasting


R1#sho ip multicast Multicast Routing: enabled ----------------------------Multicast on router config is enabled Multicast Multipath: disabled Multicast Route limit: No limit Multicast Triggered RPF check: enabled Multicast Fallback group mode: Sparse Multicast DVMRP Interoperability: disabled

If multicast Routing shows disabled, we must enable it by going into Global Config T mode and using the command
Router(config)# ip multicast-routing

Step 3.

Check to see if an ip pim mode (either sparse, dense or sparse-dense) has been enabled on our routers serial interface (This enables multicast routing on the serial interface)
Router#sh run interface ethernet0/0
interface ethernet0/0 description XO MPLS ip address x.x.x.x x.x.x.x ip nbar protocol-discovery ip flow ingress ip virtual-reassembly encapsulation ppp load-interval 30 no fair-queue service-module t1 timeslots 1-24 max-reserved-bandwidth 100 end

(Note, we do not see an ip pim mode configured) In addition we will also see multicast routing on the serial interface disabled if an ip pim mode has not been configured. R1#show ip multicast interface ethernet0/0
Example if multicast disabled. Router#show ip multicast interface ethernet0/0 Ethernet0/0 is up, line protocol is up Internet address is x.x.x.x/20 Multicast routing: disabled ------------------------------------------ Multicast shows disabled Multicast packets in/out: 0/0 Multicast TTL threshold: 0 Multicast Tagswitching: disabled

To enable an ip pim mode on the interface to be sparse-mode, go into global config t mode and type this command
Router(config-if)# ip pim sparse-mode We now can rerun the show ip multicast interface

ethernet0/0 and should now see multicast routing enabled as well as see the sparse-mode setting on the running config for the serial interface.

Router#conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)#interface ethernet0/0/0 Router(config-if)#ip pim sparse-mode Router(config-if)#end Router#show ip multicast interface ethernet0/0 Ethernet0/0/0 is up, line protocol is up Internet address is x.x.x.x/30 Multicast routing: enabled ----------------------------------Now enabled Multicast switching: fast Multicast packets in/out: 0/0 Multicast TTL threshold: 0 Multicast Tagswitching: disabled Router#show run interface ethernet0/0 interface Ethernet0/0 description ip address x.x.x.x x.x.x.x ip nbar protocol-discovery ip flow ingress ip pim sparse-mode -------------------------------Now set for pim sparse-mode ip virtual-reassembly encapsulation ppp load-interval 30 no fair-queue service-module t1 timeslots 1-24 max-reserved-bandwidth 100 end

Step 4.
Verify we have configured a Rendevous Point (RP) IP Address, this must also be set by the provider and be the same RP IP address we are using. To check if we have an RP set, you can use either of the below commands (Note, that nothing appears in the next line, indicating no RP is set in the running config)
Router#sh run | i ip pim rp ip pim rp-address x.x.x.x 20 Router#sho ip pim rp mapping PIM Group-to-RP Mappings Acl: 20, Static RP: x.x.x.x (?)

To set the RP IP Address, use this command


Router(config)# ip pim rp-address rp-address [access-list #]

For our example store, we would then type


Router(config)#ip pim rp-address x.x.x.x 20

To verify the rp-address has been set, retype


Router#sh run | i ip pim rp ip pim rp-address x.x.x.x 20 --------------------------------Note, we now see an rp-address

Step 5.
Verify we have set the appropriate access list (in this case access-list 20) into the running config
Router#show ip access-lists 20 Standard IP access list 30 10 permit x.x.x.0 wildcard bits 0.0.0.255 (# matches)

If it has not been set, we will see this


Router#show ip access-lists 20 Router#

To set access-list 20, type this command


Router#access-list 20 permit x.x.x.0 0.0.0.255

Step 6.
Finally, check the IP PIM neighbors again and see what relationships have now been established. You should now see an IP between the router and the providers edge router (WAN IP). If you do not, you will need to contact the provider to verify they have multicasting enabled on their side, and verify the rp-address they are using, as it must match your own.
Router#sho ip pim nei PIM Neighbor Table Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, S - State Refresh Capable Neighbor Interface Uptime/Expires Ver DR Address Prio/Mode x.x.x.x Ethernet0/0 11w0d/00:01:32 v2 1 / S ----------------------------Router to provider edge router

You might also like