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

Troubleshooting multicast routing and forwarding, Static multicast route failure, Symptom, Analysis

Page 85 highlights

The output shows that Switch A is the RPF neighbor of Switch C and the multicast data from Switch A is delivered over an IPv4 over IPv4 tunnel to Switch C. Troubleshooting multicast routing and forwarding Static multicast route failure Symptom No dynamic routing protocol is enabled on the routers, and the physical status and link layer status of interfaces are both up, but the static multicast route fails. Analysis • If the static multicast route is not configured or updated correctly to match the current network conditions, the route entry and the configuration information of static multicast route do not exist in the multicast routing table. • If a better route is found, the static multicast route might also fail. Solution 1. Use the display multicast routing-table static command to view the information of static multicast routes to verify that the static multicast route has been correctly configured and that the route entry exists in the multicast routing table. 2. Check the type of the next hop interface of the static multicast route. If the interface is not a point-to-point interface, be sure to specify the next hop address for the outgoing interface when you configure the static multicast route. 3. Check that the static multicast route matches the specified routing protocol. If a protocol was specified in static multicast route configuration, enter the display ip routing-table command to check if an identical route was added by the protocol. 4. Check that the static multicast route matches the specified routing policy. If a routing policy was specified when the static multicast route was configured, enter the display route-policy command to check the configured routing policy. Multicast data fails to reach receivers Symptom The multicast data can reach some routers but fails to reach the last-hop router. Analysis If a multicast forwarding boundary has been configured through the multicast boundary command, any multicast packet will be kept from crossing the boundary. Solution 1. Use the display pim routing-table command to verify that the corresponding (S, G) entries exist on the router. If yes, the router has received the multicast data. Otherwise, the router has not received the data. 2. Use the display multicast boundary command to check the multicast boundary information on the interfaces. Use the multicast boundary command to change the multicast forwarding boundary setting. 74

  • 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

74
The output shows that Switch A is the RPF neighbor of Switch C and the multicast data from Switch A is
delivered over an IPv4 over IPv4 tunnel to Switch C.
Troubleshooting multicast routing and forwarding
Static multicast route failure
Symptom
No dynamic routing protocol is enabled on the routers, and the physical status and link layer status of
interfaces are both up, but the static multicast route fails.
Analysis
If the static multicast route is not configured or updated correctly to match the current network
conditions, the route entry and the configuration information of static multicast route do not exist in
the multicast routing table.
If a better route is found, the static multicast route might also fail.
Solution
1.
Use the
display multicast routing-table static
command to view the information of static multicast
routes to verify that the static multicast route has been correctly configured and that the route entry
exists in the multicast routing table.
2.
Check the type of the next hop interface of the static multicast route. If the interface is not a
point-to-point interface, be sure to specify the next hop address for the outgoing interface when
you configure the static multicast route.
3.
Check that the static multicast route matches the specified routing protocol. If a protocol was
specified in static multicast route configuration, enter the
display ip routing-table
command to
check if an identical route was added by the protocol.
4.
Check that the static multicast route matches the specified routing policy. If a routing policy was
specified when the static multicast route was configured, enter the
display route-policy
command
to check the configured routing policy.
Multicast data fails to reach receivers
Symptom
The multicast data can reach some routers but fails to reach the last-hop router.
Analysis
If a multicast forwarding boundary has been configured through the
multicast boundary
command, any
multicast packet will be kept from crossing the boundary.
Solution
1.
Use the
display pim routing-table
command to verify that the corresponding (S, G) entries exist on
the router. If yes, the router has received the multicast data. Otherwise, the router has not received
the data.
2.
Use the
display multicast boundary
command to check the multicast boundary information on the
interfaces. Use the
multicast boundary
command to change the multicast forwarding boundary
setting.