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

Troubleshooting IPv6 multicast policy configuration, Abnormal termination of IPv6 multicast data

Page 268 highlights

Task Clear routing entries from the IPv6 multicast routing table. Command Remarks reset multicast ipv6 routing-table { { ipv6-source-address [ prefix-length ] | ipv6-group-address [ prefix-length ] | incoming-interface { interface-type interface-number | register } } * | all } Available in user view. When a routing entry is deleted from the IPv6 multicast routing table, the corresponding forwarding entry is also deleted from the IPv6 multicast forwarding table. Troubleshooting IPv6 multicast policy configuration Abnormal termination of IPv6 multicast data Symptom • • Analysis • • Solution 1. 2. A host sends an MLD report announcing its joining an IPv6 multicast group (G). However, no member information about the IPv6 multicast group (G) exists on the intermediate router. The intermediate router can receive IPv6 multicast packets successfully, but the packets cannot reach the stub network. The interface of the intermediate router receives the IPv6 multicast packets, but no corresponding (S, G) entry exists in the IPv6 PIM routing table. The multicast ipv6 boundary command filters IPv6 multicast packets received on an interface. If an IPv6 multicast packet fails to match the IPv6 ACL rule of this command, IPv6 PIM will create no routing entry. In addition, the source-policy command in IPv6 PIM filters received IPv6 multicast packets. If an IPv6 multicast packet fails to match the IPv6 ACL rule of this command, IPv6 PIM will not create a routing entry, either. Use the display current-configuration command to display the IPv6 ACL rule configured on the multicast forwarding boundary. Change the IPv6 ACL rule used in the multicast ipv6 boundary command so that the source IP address of the IPv6 multicast packets and the IPv6 multicast group address can both match the IPv6 ACL rule. View the configuration of the multicast filter. Use the display current-configuration command to display the configuration of the IPv6 multicast filter. Change the IPv6 ACL rule used in the source-policy command so that the source IP address of the IPv6 multicast packets and the IPv6 multicast group address can both match the IPv6 ACL rule. 257

  • 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

257
Task
Command
Remarks
Clear routing entries from the IPv6
multicast routing table.
reset multicast ipv6 routing-table
{ {
ipv6-source-address
[
prefix-length
]
|
ipv6-group-address
[
prefix-length
] |
incoming-interface
{
interface-type
interface-number
|
register
} } * |
all
}
Available in user view.
When a routing entry is
deleted from the IPv6
multicast routing table, the
corresponding
forwarding entry is also
deleted from the IPv6
multicast forwarding
table.
Troubleshooting IPv6 multicast policy configuration
Abnormal termination of IPv6 multicast data
Symptom
A host sends an MLD report announcing its joining an IPv6 multicast group (G). However, no
member information about the IPv6 multicast group (G) exists on the intermediate router. The
intermediate router can receive IPv6 multicast packets successfully, but the packets cannot reach the
stub network.
The interface of the intermediate router receives the IPv6 multicast packets, but no corresponding (S,
G) entry exists in the IPv6 PIM routing table.
Analysis
The
multicast ipv6 boundary
command filters IPv6 multicast packets received on an interface. If an
IPv6 multicast packet fails to match the IPv6 ACL rule of this command, IPv6 PIM will create no
routing entry.
In addition, the
source-policy
command in IPv6 PIM filters received IPv6 multicast packets. If an IPv6
multicast packet fails to match the IPv6 ACL rule of this command, IPv6 PIM will not create a routing
entry, either.
Solution
1.
Use the
display current-configuration
command to display the IPv6 ACL rule configured on the
multicast forwarding boundary. Change the IPv6 ACL rule used in the
multicast ipv6 boundary
command so that the source IP address of the IPv6 multicast packets and the IPv6 multicast group
address can both match the IPv6 ACL rule.
2.
View the configuration of the multicast filter. Use the
display current-configuration
command to
display the configuration of the IPv6 multicast filter. Change the IPv6 ACL rule used in the
source-policy
command so that the source IP address of the IPv6 multicast packets and the IPv6
multicast group address can both match the IPv6 ACL rule.