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

Configuring the NEXT_HOP attribute, Configuring the AS_PATH attribute

Page 364 highlights

Step 3. Enter IPv6 MBGP address family view. Command ipv6-family multicast 4. Configure a default MED value. default med med-value 5. Enable the comparison of the MED for routes from different compare-different-as-med ASs. 6. Enable the comparison of the MED for routes from each AS. bestroute compare-med 7. Enable the comparison of the MED for routes from bestroute med-confederation confederation peers. Remarks N/A Optional. By default, the default med-value is 0. Optional. Not enabled by default. Optional. Disabled by default. Optional. Disabled by default. Configuring the NEXT_HOP attribute You can use the peer next-hop-local command to specify the local router as the next hop of routes sent to an IPv6 multicast IBGP peer or a peer group. If load balancing is configured, the router specifies itself as the next hop of routes sent to the IPv6 multicast IBGP peer or the peer group regardless of whether the peer next-hop-local command is configured. In a third-party next-hop network, that is, the local router has two IPv6 multicast EBGP peers in a broadcast network, the router does not specify itself as the next hop of routes sent to the EBGP peers by default. To specify the router as the next hop of routes sent to a peer or a peer group: Step 1. Enter system view. 2. Enter BGP view. 3. Enter IPv6 MBGP address family view. Command system-view bgp as-number ipv6-family multicast 4. Configure the router as the next hop of routes sent to the peer or the peer group. peer { ipv6-group-name | ipv6-address } next-hop-local Remarks N/A N/A N/A Optional. By default, IPv6 MBGP specifies the local router as the next hop for routes sent to an EBGP peer or a peer group, but not for routes sent to an IBGP peer or a peer group. Configuring the AS_PATH attribute Step 1. Enter system view. 2. Enter BGP view. 3. Enter IPv6 MBGP address family view. Command system-view bgp as-number ipv6-family multicast 353 Remarks N/A N/A N/A

  • 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

353
Step
Command
Remarks
3.
Enter IPv6 MBGP address
family view.
ipv6-family multicast
N/A
4.
Configure a default MED
value.
default med
med-value
Optional.
By default, the default
med-value
is
0.
5.
Enable the comparison of the
MED for routes from different
ASs.
compare-different-as-med
Optional.
Not enabled by default.
6.
Enable the comparison of the
MED for routes from each AS.
bestroute compare-med
Optional.
Disabled by default.
7.
Enable the comparison of the
MED for routes from
confederation peers.
bestroute med-confederation
Optional.
Disabled by default.
Configuring the NEXT_HOP attribute
You can use the
peer next-hop-local
command to specify the local router as the next hop of routes sent
to an IPv6 multicast IBGP peer or a peer group. If load balancing is configured, the router specifies itself
as the next hop of routes sent to the IPv6 multicast IBGP peer or the peer group regardless of whether the
peer next-hop-local
command is configured.
In a third-party next-hop network, that is, the local router has two IPv6 multicast EBGP peers in a
broadcast network, the router does not specify itself as the next hop of routes sent to the EBGP peers by
default.
To specify the router as the next hop of routes sent to a peer or a peer group:
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 the
next hop of routes sent to the
peer or the peer group.
peer
{
ipv6-group-name
|
ipv6-address
}
next-hop-local
Optional.
By default, IPv6 MBGP specifies
the local router as the next hop for
routes sent to an EBGP peer or a
peer group, but not for routes sent
to an IBGP peer or a peer group.
Configuring the AS_PATH attribute
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