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

Troubleshooting MSDP, MSDP peers stay in down state, Symptom, Analysis, Solution

Get HP 6125G PDF manuals and user guides View all HP 6125G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 195 highlights

Troubleshooting MSDP MSDP peers stay in down state Symptom The configured MSDP peers stay in the down state. Analysis • A TCP connection-based MSDP peering relationship is established between the local interface address and the MSDP peer after the configuration. • The TCP connection setup will fail if the local interface address is not consistent with the MSDP peer address configured on the peer router. • If no route is available between the MSDP peers, the TCP connection setup will fail. Solution 1. Verify that a route is available between the routers. Use the display ip routing-table command to determine whether the unicast route between the routers is correct. 2. Verify that a unicast route is available between the two routers that will become MSDP peers to each other. 3. Verify the interface address consistency between the MSDP peers. Use the display current-configuration command to verify that the local interface address and the MSDP peer address of the remote router are the same. No SA entries in the switch's SA cache Symptom MSDP fails to send (S, G) entries through SA messages. Analysis • The import-source command controls sending (S, G) entries through SA messages to MSDP peers. If this command is executed without the acl-number argument, all the (S, G) entries are filtered out. That is, no (S, G) entries of the local domain is advertised. • If the import-source command is not executed, the system will advertise all the (S, G) entries of the local domain. If MSDP fails to send (S, G) entries through SA messages, verify that the import-source command has been correctly configured. Solution 1. Use the display ip routing-table command to verify that the unicast route between the routers is correct. 2. Verify that a unicast route is available between the two routers that will become MSDP peers to each other. 3. Verify the configuration of the import-source command and its acl-number argument and be sure that ACL rule can filter appropriate (S, G) entries. 184

  • 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
184
Troubleshooting MSDP
MSDP peers stay in down state
Symptom
The configured MSDP peers stay in the down state.
Analysis
•
A TCP connection–based MSDP peering relationship is established between the local interface
address and the MSDP peer after the configuration.
•
The TCP connection setup will fail if the local interface address is not consistent with the MSDP peer
address configured on the peer router.
•
If no route is available between the MSDP peers, the TCP connection setup will fail.
Solution
1.
Verify that a route is available between the routers. Use the
display ip routing-table
command to
determine whether the unicast route between the routers is correct.
2.
Verify that a unicast route is available between the two routers that will become MSDP peers to
each other.
3.
Verify the interface address consistency between the MSDP peers. Use the
display
current-configuration
command to verify that the local interface address and the MSDP peer
address of the remote router are the same.
No SA entries in the switch’s SA cache
Symptom
MSDP fails to send (S, G) entries through SA messages.
Analysis
•
The
import-source
command controls sending (S, G) entries through SA messages to MSDP peers.
If this command is executed without the
acl-number
argument, all the (S, G) entries are filtered out.
That is, no (S, G) entries of the local domain is advertised.
•
If the
import-source
command is not executed, the system will advertise all the (S, G) entries of the
local domain. If MSDP fails to send (S, G) entries through SA messages, verify that the
import-source
command has been correctly configured.
Solution
1.
Use the
display ip routing-table
command to verify that the unicast route between the routers is
correct.
2.
Verify that a unicast route is available between the two routers that will become MSDP peers to
each other.
3.
Verify the configuration of the
import-source
command and its
acl-number
argument and be sure
that ACL rule can filter appropriate (S, G) entries.