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

Configuring MSDP peer description, Configuring an MSDP mesh group

Page 174 highlights

Configuring MSDP peer description With the MSDP peer description information, the administrator can easily distinguish different MSDP peers to better manage MSDP peers. To configure description for an MSDP peer: Step 1. Enter system view. 2. Enter MSDP view. 3. Configure description for an MSDP peer. Command system-view msdp peer peer-address description text Remarks N/A N/A No description is configured for an MSDP peer by default. Configuring an MSDP mesh group An AS can contain multiple MSDP peers. You can use the MSDP mesh group mechanism to avoid SA message flooding among these MSDP peers and optimize the multicast traffic. An MSDP peer in an MSDP mesh group forwards SA messages (that have passed the RPF check) from outside the mesh group to the other members in the mesh group. A mesh group member accepts SA messages from inside the group without performing an RPF check, and does not forward the message within the mesh group. This mechanism not only avoids SA flooding but also simplifies the RPF check mechanism because you do not need to run BGP or MBGP between these MSDP peers. By configuring the same mesh group name for multiple MSDP peers, you can create a mesh group that contains these MSDP peers. IMPORTANT: Before grouping multiple routers into an MSDP mesh group, make sure that these routers are interconnected with one another. To create an MSDP mesh group: Step 1. Enter system view. 2. Enter MSDP view. Command system-view msdp 3. Create an MSDP mesh group and assign an MSDP peer to peer peer-address mesh-group that mesh group. name Remarks N/A N/A An MSDP peer does not belong to any mesh group by default. If you assign an MSDP peer to multiple mesh groups, only the last configuration is effective. Configuring MSDP peer connection control MSDP peers are interconnected over TCP (port number 639). You can flexibly control sessions between MSDP peers by manually deactivating and reactivating the MSDP peering connections. When the connection between two MSDP peers is deactivated, SA messages will no longer be delivered between 163

  • 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

163
Configuring MSDP peer description
With the MSDP peer description information, the administrator can easily distinguish different MSDP
peers to better manage MSDP peers.
To configure description for an MSDP peer:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter MSDP view.
msdp
N/A
3.
Configure description for an
MSDP peer.
peer
peer-address
description
text
No description is configured for an
MSDP peer by default.
Configuring an MSDP mesh group
An AS can contain multiple MSDP peers. You can use the MSDP mesh group mechanism to avoid SA
message flooding among these MSDP peers and optimize the multicast traffic.
An MSDP peer in an MSDP mesh group forwards SA messages (that have passed the RPF check) from
outside the mesh group to the other members in the mesh group. A mesh group member accepts SA
messages from inside the group without performing an RPF check, and does not forward the message
within the mesh group. This mechanism not only avoids SA flooding but also simplifies the RPF check
mechanism because you do not need to run BGP or MBGP between these MSDP peers.
By configuring the same mesh group name for multiple MSDP peers, you can create a mesh group that
contains these MSDP peers.
IMPORTANT:
Before grouping multiple routers into an MSDP mesh group, make sure that these routers are
interconnected with one another.
To create an MSDP mesh group:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter MSDP view.
msdp
N/A
3.
Create an MSDP mesh group
and assign an MSDP peer to
that mesh group.
peer
peer-address
mesh-group
name
An MSDP peer does not belong to
any mesh group by default.
If you assign an MSDP peer to
multiple mesh groups, only the last
configuration is effective.
Configuring MSDP peer connection control
MSDP peers are interconnected over TCP (port number 639). You can flexibly control sessions between
MSDP peers by manually deactivating and reactivating the MSDP peering connections. When the
connection between two MSDP peers is deactivated, SA messages will no longer be delivered between