Troubleshooting static multicast route failure, Symptom, Analysis – H3C Technologies H3C SecPath F1000-E User Manual

Page 601

Advertising
background image

576

Source sends multicast data to the multicast group 225.1.1.1 and Receiver can receive the

multicast data after joining the multicast group. You can view the PIM routing table information on
firewalls by using the display pim routing-table command. For example:
# Display the PIM routing table information on SecPath C.

[SecPathC] display pim routing-table

Total 1 (*, G) entry; 1 (S, G) entry

(*, 225.1.1.1)

Protocol: pim-dm, Flag: WC

UpTime: 00:04:25

Upstream interface: NULL

Upstream neighbor: NULL

RPF prime neighbor: NULL

Downstream interface(s) information:

Total number of downstreams: 1

1: GigabitEthernet0/1

Protocol: igmp, UpTime: 00:04:25, Expires: never

(10.1.1.100, 225.1.1.1)

Protocol: pim-dm, Flag: ACT

UpTime: 00:06:14

Upstream interface: Tunnel0

Upstream neighbor: 50.1.1.1

RPF prime neighbor: 50.1.1.1

Downstream interface(s) information:

Total number of downstreams: 1

1: GigabitEthernet0/1

Protocol: pim-dm, UpTime: 00:04:25, Expires: never

The output shows that SecPath A is the RPF neighbor of SecPath C and the multicast data from
SecPath A is delivered over a GRE tunnel to SecPath C.

Troubleshooting static multicast route failure

Symptom

No dynamic routing protocol is enabled on the routers, and the physical status and link layer status of

interfaces are both up, but the static multicast route fails.

Analysis

If the static multicast route is not configured or updated correctly to match the current network

conditions, the route entry and the configuration information of static multicast route do not exist in

the multicast routing table.

If a better route is found, the static multicast route might also fail.

Advertising