Operation Manual – Multicast
H3C S5500-EI Series Ethernet Switches
Chapter 7 PIM Configuration
7-52
II. Analysis
z
When PIM-DM runs on the entire network, multicast data is flooded from the first
hop router connected with the multicast source to the last hop router connected
with the clients along the SPT. When the multicast data is flooded to a router, no
matter which router is, it creates (S, G) entries only if it has a route to the multicast
source. If the router does not have a route to the multicast source, or if PIM-DM is
not enabled on the router’s RPF interface to the multicast source, the router
cannot create (S, G) entries.
z
When PIM-SM runs on the entire network, and when a router is to join the SPT, the
router creates (S, G) entries only if it has a route to the multicast source. If the
router does not have a router to the multicast source, or if PIM-DM is not enabled
on the router’s RPF interface to the multicast source, the router cannot create (S,
G) entries.
z
When a multicast router receives a multicast packet, it searches the existing
unicast routing table for the optimal route to the RPF check object. The outgoing
interface of this route will act as the RPF interface and the next hop will be taken
as the RPF neighbor. The RPF interface completely relies on the existing unicast
route, and is independent of PIM. The RPF interface must be PIM-enabled, and
the RPF neighbor must also be a PIM neighbor. If PIM is not enabled on the router
where the RPF interface or the RPF neighbor resides, the establishment of a
multicast distribution tree will surely fail, causing abnormal multicast forwarding.
z
Because a hello message does not carry the PIM mode information, a router
running PIM is unable to know what PIM mode its PIM neighbor is running. If
different PIM modes are enabled on the RPF interface and on the corresponding
interface of the RPF neighbor router, the establishment of a multicast distribution
tree will surely fail, causing abnormal multicast forwarding.
z
The same PIM mode must run on the entire network. Otherwise, the establishment
of a multicast distribution tree will surely fail, causing abnormal multicast
forwarding.
III. Solution
1) Check unicast routes. Use the
display ip routing-table
command to check
whether a unicast route exists from the receiver host to the multicast source.
2)
Check that PIM is enabled on the interfaces, especially on the RPF interface. Use
the
display pim interface
command to view the PIM information on each
interface. If PIM is not enabled on the interface, use the
pim dm
or
pim sm
command to enable PIM-DM or PIM-SM.
3) Check that the RPF neighbor is a PIM neighbor. Use the
display pim neighbor
command to view the PIM neighbor information.
4)
Check that PIM and IGMP are enabled on the interfaces directly connecting to the
multicast source and to the receivers.