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

Configuring an IPv6 multicast data filter, Configuration guidelines, Configuration procedure,

Page 325 highlights

• Determine the prune message delay (global value/interface level value). • Determine the prune override interval (global value/interface level value). • Determine the prune delay. • Determine the hello interval (global value/interface level value). • Determine the maximum delay between hello message (interface level value). • Determine the assert timeout time (global value/interface value). • Determine the join/prune interval (global value/interface level value). • Determine the join/prune timeout (global value/interface value). • Determine the IPv6 multicast source lifetime. • Determine the maximum size of join/prune messages. • Determine the maximum number of (S, G) entries in a join/prune message. • Determine the DSCP value for IPv6 PIM messages. Configuring an IPv6 multicast data filter In either an IPv6 PIM-DM domain or an IPv6 PIM-SM domain, routers can check passing-by IPv6 multicast data based on the configured filtering rules and determine whether to continue forwarding the IPv6 multicast data. In other words, IPv6 PIM routers can act as IPv6 multicast data filters. These filters can help implement traffic control on one hand, and control the information available to downstream receivers to enhance data security on the other hand. Configuration guidelines • Generally, a smaller distance from the filter to the IPv6 multicast source results in a more remarkable filtering effect. • This filter works not only on independent IPv6 multicast data but also on IPv6 multicast data encapsulated in register messages. Configuration procedure To configure an IPv6 multicast data filter: Step 1. Enter system view. 2. Enter IPv6 PIM view. 3. Configure an IPv6 multicast group filter. Command system-view pim ipv6 source-policy acl6-number Remarks N/A N/A No IPv6 multicast data filter by default Configuring a hello message filter Along with the wide applications of IPv6 PIM, the security requirement for the protocol is becoming increasingly demanding. The establishment of correct IPv6 PIM neighboring relationships is a prerequisite for secure application of IPv6 PIM. To guide against IPv6 PIM message attacks, you can configure a legal source address range for hello messages on interfaces of routers to ensure the correct IPv6 PIM neighboring relationships. To configure a hello message filter: 314

  • 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

314
Determine the prune message delay (global value/interface level value).
Determine the prune override interval (global value/interface level value).
Determine the prune delay.
Determine the hello interval (global value/interface level value).
Determine the maximum delay between hello message (interface level value).
Determine the assert timeout time (global value/interface value).
Determine the join/prune interval (global value/interface level value).
Determine the join/prune timeout (global value/interface value).
Determine the IPv6 multicast source lifetime.
Determine the maximum size of join/prune messages.
Determine the maximum number of (S, G) entries in a join/prune message.
Determine the DSCP value for IPv6 PIM messages.
Configuring an IPv6 multicast data filter
In either an IPv6 PIM-DM domain or an IPv6 PIM-SM domain, routers can check passing-by IPv6 multicast
data based on the configured filtering rules and determine whether to continue forwarding the IPv6
multicast data. In other words, IPv6 PIM routers can act as IPv6 multicast data filters. These filters can help
implement traffic control on one hand, and control the information available to downstream receivers to
enhance data security on the other hand.
Configuration guidelines
Generally, a smaller distance from the filter to the IPv6 multicast source results in a more remarkable
filtering effect.
This filter works not only on independent IPv6 multicast data but also on IPv6 multicast data
encapsulated in register messages.
Configuration procedure
To configure an IPv6 multicast data filter:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter IPv6 PIM view.
pim ipv6
N/A
3.
Configure an IPv6 multicast
group filter.
source-policy
acl6-number
No IPv6 multicast data filter by default
Configuring a hello message filter
Along with the wide applications of IPv6 PIM, the security requirement for the protocol is becoming
increasingly demanding. The establishment of correct IPv6 PIM neighboring relationships is a
prerequisite for secure application of IPv6 PIM. To guide against IPv6 PIM message attacks, you can
configure a legal source address range for hello messages on interfaces of routers to ensure the correct
IPv6 PIM neighboring relationships.
To configure a hello message filter: