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

Configuring an IPv6 MBGP route reflector

Page 369 highlights

Step Command 1. Enter system view. system-view 2. Enter BGP view. 3. Enter IPv6 MBGP address family view. 4. Advertise the COMMUNITY attribute to an IPv6 MBGP peer or a peer group. bgp as-number ipv6-family multicast peer { ipv6-group-name | ipv6-address } advertise-community 5. Advertise the extended peer { ipv6-group-name | community attribute to an IPv6 ipv6-address } MBGP peer or a peer group. advertise-ext-community 6. Apply a routing policy to routes sent to an IPv6 MBGP peer or a peer group. peer { ipv6-group-name | ipv6-address } route-policy route-policy-name export Remarks N/A N/A N/A By default, no COMMUNITY attribute is advertised to any peer group/peer. By default, no extended community attribute is advertised to any peer or peer group. Not configured by default. NOTE: You must configure a routing policy to define the COMMUNITY attribute, and apply the policy to outgoing routes. Configuring an IPv6 MBGP route reflector To guarantee connectivity between IPv6 multicast IBGP peers, you must make them fully meshed. However, this becomes unpractical when too many IPv6 multicast IBGP peers exist. Using route reflectors can solve the problem. The clients of a route reflector should not be fully meshed, and the route reflector reflects the routes of a client to the other clients. If the clients are fully meshed, you must disable route reflection between clients to reduce routing costs. If a cluster has multiple route reflectors, you must specify the same cluster ID for these route reflectors to avoid routing loops. To configure an IPv6 BGP route reflector: Step Command 1. Enter system view. system-view 2. Enter BGP view. bgp as-number 3. Enter IPv6 MBGP address family view. ipv6-family multicast 4. Configure the router as a route reflector and specify an IPv6 peer { ipv6-group-name | MBGP peer or a peer group ipv6-address } reflect-client as its client. 5. Enable route reflection between clients. reflect between-clients 6. Configure the cluster ID of the route reflector. reflector cluster-id cluster-id Remarks N/A N/A N/A Not configured by default. Optional. Enabled by default. Optional. By default, a route reflector uses its router ID as the cluster ID. 358

  • 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

358
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter IPv6 MBGP address
family view.
ipv6-family multicast
N/A
4.
Advertise the COMMUNITY
attribute to an IPv6 MBGP
peer or a peer group.
peer
{
ipv6-group-name
|
ipv6-address
}
advertise-community
By default, no COMMUNITY
attribute is advertised to any peer
group/peer.
5.
Advertise the extended
community attribute to an IPv6
MBGP peer or a peer group.
peer
{
ipv6-group-name
|
ipv6-address
}
advertise-ext-community
By default, no extended community
attribute is advertised to any peer
or peer group.
6.
Apply a routing policy to
routes sent to an IPv6 MBGP
peer or a peer group.
peer
{
ipv6-group-name
|
ipv6-address
}
route-policy
route-policy-name
export
Not configured by default.
NOTE:
You must configure a routing policy to define the COMMUNITY attribute, and apply the policy to outgoing
routes.
Configuring an IPv6 MBGP route reflector
To guarantee connectivity between IPv6 multicast IBGP peers, you must make them fully meshed.
However, this becomes unpractical when too many IPv6 multicast IBGP peers exist. Using route reflectors
can solve the problem.
The clients of a route reflector should not be fully meshed, and the route reflector reflects the routes of a
client to the other clients. If the clients are fully meshed, you must disable route reflection between clients
to reduce routing costs.
If a cluster has multiple route reflectors, you must specify the same cluster ID for these route reflectors to
avoid routing loops.
To configure an IPv6 BGP route reflector:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter IPv6 MBGP address
family view.
ipv6-family multicast
N/A
4.
Configure the router as a route
reflector and specify an IPv6
MBGP peer or a peer group
as its client.
peer
{
ipv6-group-name
|
ipv6-address
}
reflect-client
Not configured by default.
5.
Enable route reflection
between clients.
reflect between-clients
Optional.
Enabled by default.
6.
Configure the cluster ID of the
route reflector.
reflector cluster-id
cluster-id
Optional.
By default, a route reflector uses its
router ID as the cluster ID.