HP 6125G HP 6125G & 6125G/XG Blade Switches Layer 3 - IP Routing Confi - Page 159

Configuring automatic soft-reset, Enabling the BGP ORF capability

Page 159 highlights

Configuring automatic soft-reset After route refresh is enabled for peers and a policy is modified, the router advertises a route-refresh message to the peers, which then resend their routing information to the router. After receiving the routing information, the router performs dynamic route update by using the new policy. To enable BGP route refresh for a peer or peer group: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enable BGP route refresh for a peer or peer { group-name | ip-address } Optional. peer group. capability-advertise route-refresh Enabled by default. Configuring manual soft-reset If a BGP peer does not support route-refresh, you must save updates from the peer on the local router by using the peer keep-all-routes command, and use the refresh bgp command to refresh the BGP routing table. If the BGP peer does not support route-refresh and the peer keep-all-routes command is not configured for it, you need to decide whether to manually disconnect the peer to learn routes again according to the impact of the new policy. Following these steps to save all route updates from a peer or peer group: Step 1. Enter system view. 2. Enter BGP view. 3. Disable BGP route-refresh and multi-protocol extension capability for a peer or peer group. 4. Save all routes from a peer or peer group. 5. Return to user view. Command Remarks system-view N/A bgp as-number N/A peer { group-name | ip-address } capability-advertise Enabled by default. conventional peer { group-name | ip-address } keep-all-routes Not saved by default. return N/A 6. Perform manual soft reset on BGP connections. refresh bgp { all | ip-address | group group-name | external | internal } { export | import } N/A Enabling the BGP ORF capability The BGP Outbound Route Filtering (ORF) feature allows a BGP speaker to send its BGP peer a set of ORFs through route-refresh messages. The peer then applies the ORFs, in addition to its local routing policies (if any), to filter updates to the BGP speaker, reducing the number of exchanged 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 (determines whether to carry ORF information in messages, and if yes, 149

  • 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

149
Configuring automatic soft-reset
After route refresh is enabled for peers and a policy is modified, the router advertises a route-refresh
message to the peers, which then resend their routing information to the router. After receiving the routing
information, the router performs dynamic route update by using the new policy.
To enable BGP route refresh for a peer or peer group:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enable BGP route refresh for a peer or
peer group.
peer
{
group-name
|
ip-address
}
capability-advertise
route-refresh
Optional.
Enabled by default.
Configuring manual soft-reset
If a BGP peer does not support route-refresh, you must save updates from the peer on the local router by
using the
peer keep-all-routes
command, and use the
refresh bgp
command to refresh the BGP routing
table.
If the BGP peer does not support route-refresh and the
peer keep-all-routes
command is not configured
for it, you need to decide whether to manually disconnect the peer to learn routes again according to the
impact of the new policy.
Following these steps to save all route updates from a peer or peer group:
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
multi-protocol extension capability for
a peer or peer group.
peer
{
group-name
|
ip-address
}
capability-advertise
conventional
Enabled by default.
4.
Save all routes from a peer or peer
group.
peer
{
group-name
|
ip-address
}
keep-all-routes
Not saved by default.
5.
Return to user view.
return
N/A
6.
Perform manual soft reset on BGP
connections.
refresh bgp
{
all
|
ip-address
|
group
group-name
|
external
|
internal
} {
export
|
import
}
N/A
Enabling the BGP ORF capability
The BGP Outbound Route Filtering (ORF) feature allows a BGP speaker to send its BGP peer a set of ORFs
through route-refresh messages. The peer then applies the ORFs, in addition to its local routing policies
(if any), to filter updates to the BGP speaker, reducing the number of exchanged 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 (determines whether to carry ORF information in messages, and if yes,