632
C
HAPTER
47: PIM C
ONFIGURATION
Figure 188
Assert mechanism
As shown in Figure 188, after Router A and Router B receive an (S, G) packet from
the upstream node, they both forward the packet to the local subnet. As a result,
the downstream node Router C receives two identical multicast packets, and both
Router A and Router B, on their own local interface, receive a duplicate packet
forwarded by the other. Upon detecting this condition, both routers send an assert
message to all PIM routers (224.0.0.13) through the interface on which the packet
was received. The assert message contains the following information: the
multicast source address (S), the multicast group address (G), and the preference
and metric of the unicast route to the source. By comparing these parameters,
either Router A or Router B becomes the unique forwarder of the subsequent (S,
G) packets on the multi-access subnet. The comparison process is as follows:
1
The router with a higher unicast route preference to the source wins;
2
If both routers have the same unicast route preference to the source, the router
with a smaller metric to the source wins;
3
If there is a tie in route metric to the source, the router with a higher IP address of
the local interface wins.
Introduction to PIM-SM
PIM-DM uses the “flood and prune” principle to build SPTs for multicast data
distribution. Although an SPT has the shortest path, it is built with a low efficiency.
Therefore the PIM-DM mode is not suitable for large- and medium-sized networks.
PIM-SM is a type of sparse mode multicast protocol. It uses the “pull mode” for
multicast forwarding, and is suitable for large- and medium-sized networks with
sparsely and widely distributed multicast group members.
The basic implementation of PIM-SM is as follows:
■
PIM-SM assumes that no hosts need to receive multicast data. In the PIM-SM
mode, routers must specifically request a particular multicast stream before the
data is forwarded to them. The core task for PIM-SM to implement multicast
forwarding is to build and maintain rendezvous point trees (RPTs). An RPT is
rooted at a router in the PIM domain as the common node, or rendezvous
point (RP), through which the multicast data travels along the RPT and reaches
the receivers.
Ethernet
Router A
Router B
Router C
Receiver
Multicast packets
Assert message
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 ...