630
C
HAPTER
47: PIM C
ONFIGURATION
■
PIM-DM assumes that at least one multicast group member exists on each
subnet of a network, and therefore multicast data is flooded to all nodes on
the network. Then, branches without multicast forwarding are pruned from
the forwarding tree, leaving only those branches that contain receivers. This
“flood and prune” process takes place periodically, that is, pruned branches
resume multicast forwarding when the pruned state times out and then data is
re-flooded down these branches, and then are pruned again.
■
When a new receiver on a previously pruned branch joins a multicast group, to
reduce the join latency, PIM-DM uses a graft mechanism to resume data
forwarding to that branch.
Generally speaking, the multicast forwarding path is a source tree, namely a
forwarding tree with the multicast source as its “root” and multicast group
members as its “leaves”. Because the source tree is the shortest path from the
multicast source to the receivers, it is also called shortest path tree (SPT).
How PIM-DM Works
The working mechanism of PIM-DM is summarized as follows:
■
Neighbor discovery
■
SPT building
■
Graft
■
Assert
Neighbor discovery
In a PIM domain, a PIM router discovers PIM neighbors, maintains PIM neighboring
relationships with other routers, and builds and maintains SPTs by periodically
multicasting hello messages to all other PIM routers (224.0.0.13).
n
Every activated interface on a router sends hello messages periodically, and thus
learns the PIM neighboring information pertinent to the interface.
SPT establishment
The process of building an SPT is the process of “flood and prune”.
1
In a PIM-DM domain, when a multicast source S sends multicast data to a
multicast group G, the multicast packet is first flooded throughout the domain:
The router first performs RPF check on the multicast packet. If the packet passes
the RPF check, the router creates an (S, G) entry and forwards the data to all
downstream nodes in the network. In the flooding process, an (S, G) entry is
created on all the routers in the PIM-DM domain.
2
Then, nodes without receivers downstream are pruned: A router having no
receivers downstream sends a prune message to the upstream node to “tell” the
upstream node to delete the corresponding interface from the outgoing interface
list in the (S, G) entry and stop forwarding subsequent packets addressed to that
multicast group down to this node.
n
■
An (S, G) entry contains the multicast source address S, multicast group
address G, outgoing interface list, and incoming interface.
■
For a given multicast stream, the interface that receives the multicast stream is
referred to as “upstream”, and the interfaces that forward the multicast stream
are referred to as “downstream”.
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 ...