Netgear CSM4532 Software Administration Manual - Page 218

PIM Protocol

Page 218 highlights

Router Alter Option implies a hop by hop option header. MLD 3 types of messages: • General Query: multicast address field is set to 0 (::), is for learning which multicast addresses have listeners on the subnet. • Group-Specific Query: • Group-and-Source-Specific Query 8.1.9.1. Join Mechanism When receiving an IGMP query message, clients will respond with IGMP Join Report for the group it is interested. MLD reports must be sent with a valid IPv6 link-local source address, or, if the outgoing interface has not yet acquired a valid link-local address, the unspecific address(::). Sending reports with the unspecified address is allowed to support the use of IPv6 multicast in the Neighbor Discovery Protocol 8.1.9.2. Leave Mechanism Multicast client can leave multicast group any time by sending MLD Done message or sending the MLD listener report that excludes the group to the link-scope all routers multicast address FF02::2. If multicast clients leave multicast group quietly without sending notification to the multicast router, the multicast router stops forwarding traffic after client response timeout. 8.1.10. PIM Protocol The Protocol Independent Multicast protocol is a simple, protocol-independent multicast routing protocol. PIM uses an existing unicast routing table and a Join/Prune/Graft mechanism to build a tree. PIM switches support two types of PIM: sparse mode (PIM-SM) and dense mode (PIM-DM). PIM-SM is most effective in networks with a sparse population of multicast receivers. In contrast, PIM-DM is most effective in networks with densely populated multicast receivers. In other words, PIM-DM can be used if the majority of network hosts request to receive a multicast stream, while PIM-SM might be a better choice in networks in which a small percentage of network hosts, located throughout the network, wish to receive the multicast stream. Note: The switch supports PIM-SM only. 8.1.10.1. Using PIM-SM as the Multicast Routing Protocol PIM-SM is used to efficiently route multicast traffic to multicast groups that may span wide area networks where bandwidth is a constraint. PIM-SM uses shared trees by default and implements source-based trees for efficiency; it assumes that no hosts want the multicast traffic unless they specifically ask for it. It creates a shared distribution tree centered on a defined rendezvous point (RP) from which source traffic is relayed to the receivers. Senders first send the multicast data to the RP, which in turn sends the data down the shared tree to the receivers. NETGEAR M4500 Series Switches Software Administration Manual 218

  • 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
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251

NETGEAR M4500 Series Switches Software Administration Manual
218
Router Alter Option implies a hop by hop option header. MLD 3 types of messages:
General Query: multicast address field is set to 0 (::), is for learning which multicast addresses have
listeners on the subnet.
Group-Specific Query:
Group-and-Source-Specific Query
8.1.9.1.
Join Mechanism
When receiving an IGMP query message, clients will respond with IGMP Join Report for the group it is
interested. MLD reports must be sent with a valid IPv6 link-local source address, or, if the outgoing interface
has not yet acquired a valid link-local address, the unspecific address(::). Sending reports with the unspecified
address is allowed to support the use of IPv6 multicast in the Neighbor Discovery Protocol
8.1.9.2.
Leave Mechanism
Multicast client can leave multicast group any time by sending MLD Done message or sending the MLD
listener report that excludes the group to the link-scope all routers multicast address FF02::2.
If multicast clients leave multicast group quietly without sending notification to the multicast router, the
multicast router stops forwarding traffic after client response timeout.
8.1.10.
PIM Protocol
The Protocol Independent Multicast protocol is a simple, protocol-independent multicast routing protocol.
PIM uses an existing unicast routing table and a Join/Prune/Graft mechanism to build a tree. PIM switches
support two types of PIM: sparse mode (PIM-SM) and dense mode (PIM-DM).
PIM-SM is most effective in networks with a sparse population of multicast receivers. In contrast, PIM-DM is
most effective in networks with densely populated multicast receivers. In other words, PIM-DM can be used if
the majority of network hosts request to receive a multicast stream, while PIM-SM might be a better choice in
networks in which a small percentage of network hosts, located throughout the network, wish to receive the
multicast stream.
Note:
The switch supports PIM-SM only.
8.1.10.1.
Using PIM-SM as the Multicast Routing Protocol
PIM-SM is used to efficiently route multicast traffic to multicast groups that may span wide area networks
where bandwidth is a constraint.
PIM-SM uses shared trees by default and implements source-based trees for efficiency; it assumes that no
hosts want the multicast traffic unless they specifically ask for it. It creates a shared distribution tree centered
on a defined rendezvous point (RP) from which source traffic is relayed to the receivers. Senders first send the
multicast data to the RP, which in turn sends the data down the shared tree to the receivers.