670
C
HAPTER
47: PIM C
ONFIGURATION
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.
■
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.
■
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.
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.
5
Check that the same PIM mode is enabled on related interfaces. Use the
display
pim interface verbose
command to check whether the same PIM mode is
enabled on the RPF interface and the corresponding interface of the RPF neighbor
router.
6
Check that the same PIM mode is enabled on all the routers in the entire network.
Make sure that the same PIM mode is enabled on all the routers: PIM-SM on all
routers, or PIM-DM on all routers. In the case of PIM-SM, also check that the BSR
and RP configurations are correct.
Multicast Data
Abnormally Terminated
on an Intermediate
Router
Symptom
An intermediate router can receive multicast data successfully, but the data cannot
reach the last hop router. An interface on the intermediate router receives data but
no corresponding (S, G) entry is created in the PIM routing table.
Analysis
■
If a multicast forwarding boundary has been configured through the
multicast
boundary
command, any multicast packet will be kept from crossing the
boundary, and therefore no routing entry can be created in the PIM routing
table.
■
In addition, the
source-policy
command is used to filter received multicast
packets. If the multicast data fails to pass the ACL rule defined in this
command, PIM cannot create the route entry, either.
Summary of Contents for 4800G Series
Page 26: ...26 CHAPTER NETWORKING APPLICATIONS ...
Page 30: ...30 CHAPTER 1 LOGGING IN TO AN ETHERNET SWITCH ...
Page 62: ...62 CHAPTER 3 LOGGING IN THROUGH TELNET ...
Page 70: ...70 CHAPTER 5 LOGGING IN THROUGH WEB BASED NETWORK MANAGEMENT SYSTEM ...
Page 72: ...72 CHAPTER 6 LOGGING IN THROUGH NMS ...
Page 82: ...82 CHAPTER 8 CONTROLLING LOGIN USERS ...
Page 98: ...98 CHAPTER 9 VLAN CONFIGURATION ...
Page 108: ...108 CHAPTER 10 VOICE VLAN CONFIGURATION ...
Page 119: ...GVRP Configuration Examples 119 DeviceB display vlan dynamic No dynamic vlans exist ...
Page 120: ...120 CHAPTER 11 GVRP CONFIGURATION ...
Page 160: ...160 CHAPTER 17 PORT ISOLATION CONFIGURATION ...
Page 172: ...172 CHAPTER 19 LINK AGGREGATION CONFIGURATION ...
Page 196: ...196 CHAPTER 22 DLDP CONFIGURATION ...
Page 240: ...240 CHAPTER 23 MSTP CONFIGURATION ...
Page 272: ...272 CHAPTER 27 RIP CONFIGURATION ...
Page 364: ...364 CHAPTER 29 IS IS CONFIGURATION ...
Page 426: ...426 CHAPTER 31 ROUTING POLICY CONFIGURATION ...
Page 442: ...442 CHAPTER 33 IPV6 RIPNG CONFIGURATION ...
Page 466: ...466 CHAPTER 35 IPV6 IS IS CONFIGURATION ...
Page 488: ...488 CHAPTER 36 IPV6 BGP CONFIGURATION ...
Page 498: ...498 CHAPTER 37 ROUTING POLICY CONFIGURATION ...
Page 540: ...540 CHAPTER 40 TUNNELING CONFIGURATION ...
Page 552: ...552 CHAPTER 41 MULTICAST OVERVIEW ...
Page 604: ...604 CHAPTER 43 MLD SNOOPING CONFIGURATION ...
Page 628: ...628 CHAPTER 46 IGMP CONFIGURATION ...
Page 700: ...700 CHAPTER 48 MSDP CONFIGURATION ...
Page 812: ...812 CHAPTER 57 DHCP SERVER CONFIGURATION ...
Page 822: ...822 CHAPTER 58 DHCP RELAY AGENT CONFIGURATION ...
Page 834: ...834 CHAPTER 61 BOOTP CLIENT CONFIGURATION ...
Page 850: ...850 CHAPTER 63 IPV4 ACL CONFIGURATION ...
Page 856: ...856 CHAPTER 64 IPV6 ACL CONFIGURATION ...
Page 860: ...860 CHAPTER 65 QOS OVERVIEW ...
Page 868: ...868 CHAPTER 66 TRAFFIC CLASSIFICATION TP AND LR CONFIGURATION ...
Page 888: ...888 CHAPTER 69 PRIORITY MAPPING ...
Page 894: ...894 CHAPTER 71 TRAFFIC MIRRORING CONFIGURATION ...
Page 904: ...904 CHAPTER 72 PORT MIRRORING CONFIGURATION ...
Page 930: ...930 CHAPTER 74 UDP HELPER CONFIGURATION ...
Page 990: ...990 CHAPTER 79 FILE SYSTEM MANAGEMENT CONFIGURATION ...
Page 1000: ...1000 CHAPTER 80 FTP CONFIGURATION ...
Page 1020: ...1020 CHAPTER 82 INFORMATION CENTER CONFIGURATION ...
Page 1038: ...1038 CHAPTER 84 SYSTEM MAINTAINING AND DEBUGGING ...
Page 1046: ...1046 CHAPTER 85 DEVICE MANAGEMENT ...
Page 1129: ...SSH Client Configuration Examples 1129 SwitchB ...
Page 1130: ...1130 CHAPTER 88 SSH CONFIGURATION ...
Page 1160: ...1160 CHAPTER 90 RRPP CONFIGURATION ...
Page 1180: ...1180 CHAPTER 91 PORT SECURITY CONFIGURATION ...
Page 1192: ...1192 CHAPTER 92 LLDP CONFIGURATION ...
Page 1202: ...1202 CHAPTER 93 POE CONFIGURATION ...
Page 1218: ...1218 CHAPTER 96 HTTPS CONFIGURATION ...