D-Link DES-3326SRM Product Manual - Page 216

Reverse Path Multicasting (RPM), Multicast Routing Protocols

Page 216 highlights

D-Link DES-3326S Layer 3 Switch if the packet was received on the shortest path back from the router to the source. If the packet was received on the shortest path back to the source, the packet is forwarded on all links except the link on which the packet was received. If the packet was not received on the shortest link back to the source, the packet is dropped. If a link-state routing protocol is in use, RPB on a local router can determine if the path from the source through the local router to an immediately neighboring router. If it is not, the packet will be dropped at the next router and the packet should not be forwarded. If a distance-vector routing protocol is in use, a neighboring router can either advertise its previous hop for the source as part of its routing update messages. This will 'poison-reverse' the route (or have the local router prune the branch from the multicast source to the neighboring router because the neighboring router has a better route from the source to the next router or subnetwork). Since multicast packets are forwarded through the shortest route between source and destination, RPB is fast. A given router also does not need information about the entire spanning tree, nor does it need a mechanism to stop the forwarding of packets. RPB does not use multicast group membership information in its forwarding decisions. Reverse Path Multicasting (RPM) Reverse Path Multicasting (RPM) introduces an enhancement to RPB - an explicit method to prune branches of the spanning tree that have on active multicast group members for the source. RPM constructs a tree that spans only subnetworks with multicast group member and routers along the shortest path between the source and the destinations. When a multicast router receives a multicast packet, it is forwarded using the RPB constructed spanning tree. Subsequent routers in the tree that have no active path to another router are referred to as leaf routers. If the multicast packet if forwarded to a leaf router that has no active multicast group members for the source, the leaf router will send a prune message to the previous router. This will remove the leaf router's branch from the spanning tree, and no more multicast packets (from that source) will be forwarded to it. Prune messages have a TTL equal to one, so they can be sent only one hop (one router) back toward the source. If the previous router receives prune messages from all of its branch and leaf routers, the previous router will then send it's own prune message back one router toward the multicast source, and the process will repeat. In this way, multicast group membership information can be used to prune the spanning tree between a given multicast source and the corresponding multicast group. Since the membership of any given multicast group can change and the network topology can also change, RPM periodically removes all of the prune information it has gathered from it's memory, and the entire process repeats. This gives all subsequent routers on the network a chance to receive multicast packets from all multicast sources on the network. It also gives all users a chance to join a given multicast group. Multicast Routing Protocols This section contains an overview of two multicast routing protocols - Distance Vector Multicast Routing Protocol (DVMRP), and Protocol Independent Multicast-Dense Mode (PIM-DM). The most commonly used routing protocol (not a multicast routing protocol), the Routing Information Protocol, is discussed in a later section. Distance Vector Multicast Routing Protocol (DVMRP) The Distance Vector Multicast Routing Protocol (DVMRP) was derived from the Routing Information Protocol (RIP) with the introduction of multicast delivery trees constructed from information about the 'distance' from the local router back toward the multicast source. DVMRP uses an RPM algorithm to construct its multicast delivery trees. The first multicast packet received by a multicast router using DVMRP is flooded to all interfaces except the one on which the packet was received. Subsequent prune messages are used to prune branches of the delivery tree that are either not on the shortest path back to the multicast source, or that have no active multicast group members. A 'graft' message is added that allows a previously pruned branch of the multicast delivery tree to be reactivated. This allows for lower latency when a leaf router adds a new member to a multicast membership group. Graft messages are forwarded one hop (one router) back at a time toward a multicast source until they reach a router that is on an active branch of the multicast delivery tree. If there is more than one multicast router on a network, the one that has the shortest path back to the multicast source is elected to forward multicast packets from that source. All other routers will discard multicast packets from that source. If 206

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242

D-Link DES-3326S Layer 3 Switch
if the packet was received on the shortest path back from the router to the source. If the packet was received on the shortest
path back to the source, the packet is forwarded on all links except the link on which the packet was received.
If the packet
was not received on the shortest link back to the source, the packet is dropped.
If a link-state routing protocol is in use, RPB on a local router can determine if the path from the source through the local
router to an immediately neighboring router.
If it is not, the packet will be dropped at the next router and the packet should
not be forwarded.
RPB does not use multicast group membership information in its forwarding decisions.
When a multicast router receives a multicast packet, it is forwarded using the RPB constructed spanning tree.
Subsequent
routers in the tree that have no active path to another router are referred to as leaf routers.
If the multicast packet if
forwarded to a leaf router that has no active multicast group members for the source, the leaf router will send a prune
message to the previous router.
This will remove the leaf router’s branch from the spanning tree, and no more multicast
packets (from that source) will be forwarded to it.
Prune messages have a TTL equal to one, so they can be sent only one
hop (one router) back toward the source.
If the previous router receives prune messages from all of its branch and leaf
routers, the previous router will then send it’s own prune message back one router toward the multicast source, and the
process will repeat.
In this way, multicast group membership information can be used to prune the spanning tree between a
given multicast source and the corresponding multicast group.
This section contains an overview of two multicast routing protocols – Distance Vector Multicast Routing Protocol
(DVMRP), and Protocol Independent Multicast-Dense Mode
Distance Vector Multicast Routing Protocol (DVMRP)
If a distance-vector routing protocol is in use, a neighboring router can either advertise its previous hop for the source as part
of its routing update messages.
This will ‘poison-reverse’ the route (or have the local router prune the branch from the
multicast source to the neighboring router because the neighboring router has a better route from the source to the next router
or subnetwork).
Since multicast packets are forwarded through the shortest route between source and destination, RPB is fast.
A given router
also does not need information about the entire spanning tree, nor does it need a mechanism to stop the forwarding of
packets.
Reverse Path Multicasting (RPM)
Reverse Path Multicasting (RPM) introduces an enhancement to RPB – an explicit method to prune branches of the spanning
tree that have on active multicast group members for the source.
RPM constructs a tree that spans only subnetworks with
multicast group member and routers along the shortest path between the source and the destinations.
Since the membership of any given multicast group can change and the network topology can also change, RPM periodically
removes all of the prune information it has gathered from it’s memory, and the entire process repeats.
This gives all
subsequent routers on the network a chance to receive multicast packets from all multicast sources on the network.
It also
gives all users a chance to join a given multicast group.
Multicast Routing Protocols
(PIM-DM).
The most commonly used routing protocol (not a multicast routing protocol), the Routing Information Protocol,
is discussed in a later section.
The Distance Vector Multicast Routing Protocol (DVMRP) was derived from the Routing Information Protocol (RIP) with
the introduction of multicast delivery trees constructed from information about the ‘distance’ from the local router back
toward the multicast source.
DVMRP uses an RPM algorithm to construct its multicast delivery trees.
The first multicast packet received by a multicast router using DVMRP is flooded to all interfaces except the one on which
the packet was received.
Subsequent prune messages are used to prune branches of the delivery tree that are either not on the
shortest path back to the multicast source, or that have no active multicast group members.
A ‘graft’ message is added that
allows a previously pruned branch of the multicast delivery tree to be reactivated.
This allows for lower latency when a leaf
router adds a new member to a multicast membership group.
Graft messages are forwarded one hop (one router) back at a
time toward a multicast source until they reach a router that is on an active branch of the multicast delivery tree.
If there is more than one multicast router on a network, the one that has the shortest path back to the multicast source is
elected to forward multicast packets from that source.
All other routers will discard multicast packets from that source.
If
206