16.2.3 IPv4 PIM-SM confirmation of information

The following are the types of information you can check in the IPv4 multicast routing information for the Switch when the PIM-SM functionality is set.

<Structure of this section>

(1) Interface information

Execute the show ip pim interface command and check the following.

Check the interface within Address. If none exists, PIM-SM will not run on the interface. In the configuration, make sure that PIM is enabled on the interface. In addition, check whether a failure has occurred on the interface.

Check the Nbr Count value (number of neighboring PIM routers) for the target interface. If this value is 0, neighboring routers either do not exist, or are not reporting PIM hello messages. Check the neighboring routers.

Figure 16-9: Result of executing show ip pim interface command
> show ip pim interface Date 20XX/08/01 15:20:00 UTC Address Interface Component Vif Nbr Hello DR Count Intvl Address 192.168.10.1 VLAN0001 PIM-SM 1 2 30 192.168.10.5 192.168.20.1 VLAN0002 PIM-SM 2 0 30 This system >

Figure 16-9: Result of executing show ip pim interface command

> show ip pim interface
Date 20XX/08/01 15:20:00 UTC
Address         Interface       Component Vif Nbr   Hello DR
                                              Count Intvl Address
192.168.10.1    VLAN0001        PIM-SM      1     2    30 192.168.10.5
192.168.20.1    VLAN0002        PIM-SM      2     0    30 This system
>

[Figure Data]

(2) Neighbor information

Execute the show ip pim neighbor command to check the presence of neighbors at the IP address for Neighbor Address of the corresponding interface. If a particular neighbor does not exist, the neighboring routers might not be reporting PIM Hello messages. Check the neighboring routers.

Figure 16-10: Result of executing show ip pim neighbor command
> show ip pim neighbor Date 20XX/08/01 15:20:00 UTC Address Interface Neighbor Address Uptime Expires 192.168.10.1 VLAN0001 192.168.10.5 00:10 01:35 192.168.10.3 00:05 01:40 >

(3) Source route information

Execute the show ip rpf command to check sender routing information.

Figure 16-11: Result of executing show ip rpf command
> show ip rpf 192.168.5.100 Date 20XX/08/01 15:20:00 UTC Incoming: VLAN0001(192.168.5.200) Upstream: 192.168.10.1

(4) PIM-SM BSR info

Execute the show ip pim bsr command and check whether the BSR address is displayed. If ---- is displayed, the BSR might not be sending bootstrap messages, or might not exist. Check the BSR. Note that BSRs cannot be used for PIM-SSM.

Figure 16-12: Result of executing show ip pim bsr command
> show ip pim bsr Date 20XX/08/01 15:20:00 UTC Status : Not Candidate Bootstrap Router BSR Address : 192.168.10.10 Priority: 100 Hash mask length: 30 Uptime : 03:00 Bootstrap Timeout : 130 seconds >

(5) PIM-SM rendezvous point data

Execute the show ip pim rp-mapping command to make sure that the C-RP address is displayed for the corresponding IPv4 multicast group address. If it is not displayed, the BSR might not be sending bootstrap messages, or the rendezvous point or BSR might not exist. Check the rendezvous point and BSR. Note that rendezvous points cannot be used for PIM-SSM.

Figure 16-13: Result of executing show ip pim rp-mapping command
> show ip pim rp-mapping Date 20XX/04/20 15:20:00 UTC Status : Not Candidate Rendezvous Point Total: 2 routes, 2 groups, 1 RP Group/Masklen C-RP Address Priority Uptime Expires Flags 224.100.200.0/24 192.168.1.1 100 02:00 02:30 - 224.100.100.0/24 192.168.1.1 100 02:00 02:30 - >

Figure 16-13: Result of executing show ip pim rp-mapping command

> show ip pim rp-mapping
Date 20XX/04/20 15:20:00 UTC
Status : Not Candidate Rendezvous Point
Total: 2 routes, 2 groups, 1 RP 
Group/Masklen       C-RP Address Priority Uptime  Expires  Flags
224.100.200.0/24    192.168.1.1       100 02:00   02:30    -
224.100.100.0/24    192.168.1.1       100 02:00   02:30    -
>

(6) PIM-SM routing info

Execute the show ip mroute command to check whether a path to the corresponding destination address exists. If no (S,G) entry exists, check whether a (*,G) entry exists. If no (*,G) entry exists, and both incoming and outgoing are invalid, check the neighboring router. Note that (*,G) cannot be used for PIM-SSM, since it does not exist.

Figure 16-14: Displaying PIM-SM multicast route information
> show ip mroute Date 20XX/04/20 15:20:00 UTC Total: 5 routes, 4 groups, 2 sources (S,G) 3 routes ----------------------------------------------------------- Group Address Source Address Protocol Flags Uptime Expires Assert 224.100.100.10 192.168.1.1 SM F 02:00 02:30 01:00 incoming: VLAN0001(192.168.1.3) upstream: Direct, reg-sup: 30s outgoing: VLAN0002(192.168.2.3) uptime 02:30, expires 00:40 224.100.100.20 192.168.1.1 SM F 02:00 02:30 01:00 incoming: VLAN0001(192.168.1.3) upstream: Direct outgoing: register <Register to 192.168.5.1> 224.100.100.30 192.1.4.1 SM F 02:00 02:30 01:00 incoming: VLAN0001(192.168.1.3) upstream: 192.168.1.5 outgoing: VLAN0002(192.168.2.3) uptime 02:30, expires 00:40 (*,G) 2 routes ----------------------------------------------------------- Group Address RP Address Protocol Flags Uptime Expires Assert 225.100.100.10 192.168.5.1 SM R 02:00 02:30 01:00 incoming: register upstream: This System outgoing: VLAN0002(192.168.2.3) uptime 02:30, expires 00:40 225.100.100.10 192.168.5.1 SM R 02:00 02:30 01:00 incoming: VLAN0001(192.168.1.3) upstream: 192.168.1.2 outgoing: VLAN0003(192.168.3.3) uptime 02:30, expires 00:40 >

Figure 16-14: Displaying PIM-SM multicast route information

> show ip mroute
Date 20XX/04/20 15:20:00 UTC
Total: 5 routes, 4 groups, 2 sources
 
(S,G) 3 routes  -----------------------------------------------------------
Group Address    Source Address   Protocol Flags  Uptime   Expires  Assert
224.100.100.10   192.168.1.1      SM       F       02:00    02:30    01:00
    incoming: VLAN0001(192.168.1.3)      upstream: Direct, reg-sup: 30s
    outgoing: VLAN0002(192.168.2.3)      uptime 02:30, expires 00:40
 
224.100.100.20   192.168.1.1      SM       F       02:00    02:30    01:00
    incoming: VLAN0001(192.168.1.3)      upstream: Direct 
    outgoing: register <Register to 192.168.5.1>
 
224.100.100.30   192.1.4.1        SM       F       02:00    02:30    01:00
    incoming: VLAN0001(192.168.1.3)      upstream: 192.168.1.5
    outgoing: VLAN0002(192.168.2.3)      uptime 02:30, expires 00:40
 
(*,G) 2 routes  -----------------------------------------------------------
Group Address    RP Address       Protocol Flags  Uptime   Expires  Assert
225.100.100.10   192.168.5.1      SM       R       02:00    02:30    01:00
    incoming: register                   upstream: This System
    outgoing: VLAN0002(192.168.2.3)      uptime 02:30, expires 00:40
 
225.100.100.10   192.168.5.1      SM       R       02:00    02:30    01:00
    incoming: VLAN0001(192.168.1.3)      upstream: 192.168.1.2
    outgoing: VLAN0003(192.168.3.3)      uptime 02:30, expires 00:40
>