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

Tuning and optimizing IPv6 BGP networks

Page 249 highlights

Step 1. Enter system view. 2. Enter BGP view. 3. Enter IPv6 address family view. 4. Allow the local AS number to appear in AS_PATH of routes from a peer or peer group and specify the repeat times. Command system-view bgp as-number ipv6-family peer { ipv6-group-name | ipv6-address } allow-as-loop [ number ] 5. Specify a fake AS number for peer { ipv6-group-name | an IPv6 peer or peer group. ipv6-address } fake-as as-number 6. Disable IPv6 BGP from considering the AS_PATH during best route selection. bestroute as-path-neglect 7. Configure to carry only the public AS number in updates peer { ipv6-group-name | sent to a peer or peer group. ipv6-address } public-as-only 8. Substitute the local AS number for the AS number of an IPv6 peer { ipv6-group-name | peer or peer group identified ipv6-address } substitute-as in the AS_PATH attribute. Remarks N/A N/A N/A Optional. Not allowed by default. Optional. Not specified by default. Optional. Enabled by default. Optional. By default, IPv6 BGP updates carry a private AS number. Optional. Not substituted by default. Tuning and optimizing IPv6 BGP networks This section describes configurations of IPv6 BGP timers, IPv6 BGP connection soft reset, and the maximum number of load balanced routes. • IPv6 BGP timers After establishing an IPv6 BGP connection, two routers send keepalive messages periodically to each other to maintain the connection. If a router receives no keepalive message from the peer after the holdtime elapses, it tears down the connection. When establishing an IPv6 BGP connection, the two parties compare their holdtimes, taking the shorter one as the common holdtime. If the holdtime is 0, neither keepalive massage is sent, nor holdtime is checked. • IPv6 BGP connection soft reset After modifying a route selection policy, you must reset IPv6 BGP connections to make the new one take effect. The current IPv6 BGP implementation supports the route-refresh feature that enables dynamic route refresh without needing to disconnect IPv6 BGP links. After this feature is enabled on all IPv6 BGP routers, a router that wants to apply a new route selection policy advertises a route-refresh message to its peers, which then send their routing information to the router. After receiving the routing information, the router can perform dynamic route update by using the new policy without tearing down connections. If a peer not supporting route-refresh exists in the network, you must configure the peer keep-all-routes command to save all routes from the peer. When the routing policy is changed, the system will update the IPv6 BGP routing table and apply the new policy. 239

  • 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

239
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter IPv6 address family
view.
ipv6-family
N/A
4.
Allow the local AS number to
appear in AS_PATH of routes
from a peer or peer group
and specify the repeat times.
peer
{
ipv6-group-name
|
ipv6-address
}
allow-as-loop
[
number
]
Optional.
Not allowed by default.
5.
Specify a fake AS number for
an IPv6 peer or peer group.
peer
{
ipv6-group-name
|
ipv6-address
}
fake-as
as-number
Optional.
Not specified by default.
6.
Disable IPv6 BGP from
considering the AS_PATH
during best route selection.
bestroute as-path-neglect
Optional.
Enabled by default.
7.
Configure to carry only the
public AS number in updates
sent to a peer or peer group.
peer
{
ipv6-group-name
|
ipv6-address
}
public-as-only
Optional.
By default, IPv6 BGP updates carry
a private AS number.
8.
Substitute the local AS number
for the AS number of an IPv6
peer or peer group identified
in the AS_PATH attribute.
peer
{
ipv6-group-name
|
ipv6-address
}
substitute-as
Optional.
Not substituted by default.
Tuning and optimizing IPv6 BGP networks
This section describes configurations of IPv6 BGP timers, IPv6 BGP connection soft reset, and the
maximum number of load balanced routes.
IPv6 BGP timers
After establishing an IPv6 BGP connection, two routers send keepalive messages periodically to
each other to maintain the connection. If a router receives no keepalive message from the peer
after the holdtime elapses, it tears down the connection.
When establishing an IPv6 BGP connection, the two parties compare their holdtimes, taking the
shorter one as the common holdtime. If the holdtime is 0, neither keepalive massage is sent, nor
holdtime is checked.
IPv6 BGP connection soft reset
After modifying a route selection policy, you must reset IPv6 BGP connections to make the new one
take effect. The current IPv6 BGP implementation supports the route-refresh feature that enables
dynamic route refresh without needing to disconnect IPv6 BGP links.
After this feature is enabled on all IPv6 BGP routers, a router that wants to apply a new route
selection policy advertises a route-refresh message to its peers, which then send their routing
information to the router. After receiving the routing information, the router can perform dynamic
route update by using the new policy without tearing down connections.
If a peer not supporting route-refresh exists in the network, you must configure the
peer
keep-all-routes
command to save all routes from the peer. When the routing policy is changed, the
system will update the IPv6 BGP routing table and apply the new policy.