HP 6125G HP 6125G & 6125G/XG Blade Switches IP Multicast Configuration - Page 281

Configuring Router-Alert option handling methods globally, Configuring Router-Alert option handling

Page 281 highlights

• For compatibility, the device by default ignores the Router-Alert option and processes all received MLD messages, no matter whether the MLD messages carry the Router-Alert option or not. • To enhance device performance, avoid unnecessary costs, and ensure protocol security, configure the device to discard MLD messages that do not carry the Router-Alert option. Configuring Router-Alert option handling methods globally Step 1. Enter system view. 2. Enter MLD view. 3. Configure the interface to discard any MLD message without the Router-Alert option. 4. Enable the insertion of the Router-Alert option into MLD messages. Command system-view mld require-router-alert send-router-alert Configuring Router-Alert option handling methods on an interface Remarks N/A N/A By default, the device does not check MLD messages for the Router-Alert option. By default, MLD messages carry the Router-Alert option. Step 1. Enter system view. 2. Enter interface view. 3. Configure the interface to discard any MLD message without the Router-Alert option. 4. Enable the insertion of the Router-Alert option into MLD messages. Command system-view interface interface-type interface-number mld require-router-alert mld send-router-alert Remarks N/A N/A By default, the device does not check MLD messages for the Router-Alert option. By default, MLD messages carry the Router-Alert option. Configuring MLD query and response parameters On startup, the MLD querier sends MLD general queries at the startup query interval, which is one-quarter of the MLD query interval. The number of queries, or the startup query count, is user configurable. After startup, the MLD querier periodically sends MLD general queries at the MLD query interval to check for IPv6 multicast group members on the network. You can modify the query interval based on the actual condition of the network. The MLDv1 querier sends MLD multicast-address-specific queries at the MLD last listener query interval when it receives an MLD done message. The MLDv2 querier sends MLD multicast-address-and-source-specific queries at the MLD last listener query interval when it receives a multicast group and multicast source mapping change report. The number of queries, or the last listener query count, equals the robustness variable (the maximum number of packet retransmissions). A multicast listening host starts a timer for each IPv6 multicast group that it has joined when it receives an MLD query (general query, multicast-address-specific query, or multicast-address-and-source-specific 270

  • 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
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379

270
For compatibility, the device by default ignores the Router-Alert option and processes all received
MLD messages, no matter whether the MLD messages carry the Router-Alert option or not.
To enhance device performance, avoid unnecessary costs, and ensure protocol security, configure
the device to discard MLD messages that do not carry the Router-Alert option.
Configuring Router-Alert option handling methods globally
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter MLD view.
mld
N/A
3.
Configure the interface to
discard any MLD message
without the Router-Alert
option.
require-router-alert
By default, the device does not
check MLD messages for the
Router-Alert option.
4.
Enable the insertion of the
Router-Alert option into MLD
messages.
send-router-alert
By default, MLD messages carry
the Router-Alert option.
Configuring Router-Alert option handling methods on an interface
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface
interface-type
interface-number
N/A
3.
Configure the interface to
discard any MLD message
without the Router-Alert
option.
mld require-router-alert
By default, the device does not
check MLD messages for the
Router-Alert option.
4.
Enable the insertion of the
Router-Alert option into MLD
messages.
mld send-router-alert
By default, MLD messages carry
the Router-Alert option.
Configuring MLD query and response parameters
On startup, the MLD querier sends MLD general queries at the startup query interval, which is
one-quarter of the MLD query interval. The number of queries, or the startup query count, is user
configurable.
After startup, the MLD querier periodically sends MLD general queries at the MLD query interval to check
for IPv6 multicast group members on the network. You can modify the query interval based on the actual
condition of the network.
The MLDv1 querier sends MLD multicast-address-specific queries at the MLD last listener query interval
when
it
receives
an
MLD
done
message.
The
MLDv2
querier
sends
MLD
multicast-address-and-source-specific queries at the MLD last listener query interval when it receives a
multicast group and multicast source mapping change report. The number of queries, or the last listener
query count, equals the robustness variable (the maximum number of packet retransmissions).
A multicast listening host starts a timer for each IPv6 multicast group that it has joined when it receives an
MLD query (general query, multicast-address-specific query, or multicast-address-and-source-specific