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

Performing soft reset manually, Enabling the MBGP ORF capability

Page 207 highlights

Step Command 3. Enable BGP route refresh for a peer { group-name | ip-address } peer or a peer group. capability-advertise route-refresh Remarks Optional. Enabled by default. Performing soft reset manually If the peer does not support route refresh, you can use the peer keep-all-routes command to save all the route updates from the peer, and then use the refresh bgp ipv4 multicast command to soft-reset MBGP connections to refresh the MBGP routing table and apply the new policy without terminating MBGP connections. To perform a manual soft reset: Step 1. Enter system view. Command system-view 2. Enter BGP view. bgp as-number 3. Disable BGP route refresh and multiprotocol extensions for a peer { group-name | ip-address } peer or a peer group. capability-advertise conventional 4. Enter IPv4 MBGP address family view. ipv4-family multicast 5. Keep all original routes from a peer or a peer group regardless of whether they pass the inbound filtering peer { group-name | ip-address } keep-all-routes policies. 6. Return to user view. return 7. Soft-reset MBGP connections manually. refresh bgp ipv4 multicast { all | ip-address | group group-name | external | internal } { export | import } Remarks N/A N/A Optional. Enabled by default. N/A Not kept by default. N/A Optional. Enabling the MBGP ORF capability The MBGP Outbound Router Filter (ORF) feature enables an MBGP speaker to send a set of ORFs to its MBGP peer through route-refresh messages. The peer then applies the ORFs, in addition to its local routing policies (if any), to filter updates to the MBGP speaker, reducing update messages and saving network resources. After you enable the BGP ORF capability, the local BGP router negotiates the ORF capability with the BGP peer through Open messages. That is, the BGP router determines whether to carry ORF information in messages and, if so, whether to carry nonstandard ORF information in the packets. After completing the negotiation process and establishing the neighboring relationship, the BGP router and its BGP peer can exchange ORF information through specific route-refresh messages. For the parameters configured on both sides for ORF capability negotiation, see Table 7. To enable the MBGP ORF capability: 196

  • 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

196
Step
Command
Remarks
3.
Enable BGP route refresh for a
peer or a peer group.
peer
{
group-name
|
ip-address
}
capability-advertise
route-refresh
Optional.
Enabled by default.
Performing soft reset manually
If the peer does not support route refresh, you can use the
peer keep-all-routes
command to save all the
route updates from the peer, and then use the
refresh bgp ipv4 multicast
command to soft-reset MBGP
connections to refresh the MBGP routing table and apply the new policy without terminating MBGP
connections.
To perform a manual soft reset:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Disable BGP route refresh and
multiprotocol extensions for a
peer or a peer group.
peer
{
group-name
|
ip-address
}
capability-advertise conventional
Optional.
Enabled by default.
4.
Enter IPv4 MBGP address
family view.
ipv4-family multicast
N/A
5.
Keep all original routes from a
peer or a peer group
regardless of whether they
pass the inbound filtering
policies.
peer
{
group-name
|
ip-address
}
keep-all-routes
Not kept by default.
6.
Return to user view.
return
N/A
7.
Soft-reset MBGP connections
manually.
refresh bgp ipv4 multicast
{
all
|
ip-address
|
group
group-name
|
external
|
internal
} {
export
|
import
}
Optional.
Enabling the MBGP ORF capability
The MBGP Outbound Router Filter (ORF) feature enables an MBGP speaker to send a set of ORFs to its
MBGP peer through route-refresh messages. The peer then applies the ORFs, in addition to its local
routing policies (if any), to filter updates to the MBGP speaker, reducing update messages and saving
network resources.
After you enable the BGP ORF capability, the local BGP router negotiates the ORF capability with the
BGP peer through Open messages. That is, the BGP router determines whether to carry ORF information
in messages and, if so, whether to carry nonstandard ORF information in the packets. After completing
the negotiation process and establishing the neighboring relationship, the BGP router and its BGP peer
can exchange ORF information through specific route-refresh messages.
For the parameters configured on both sides for ORF capability negotiation, see
Table 7
.
To enable the MBGP ORF capability: