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

Removing private AS numbers from updates to a peer or peer group

Page 157 highlights

Removing private AS numbers from updates to 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. Configure BGP to remove private AS numbers from the AS_PATH attribute of peer { group-name | ip-address } By default, BGP updates updates to a peer or peer group. public-as-only carry private AS numbers. Ignoring the first AS number of EBGP route updates Typically, BGP checks the AS_PATH attribute of a route update received from a peer. If the first AS number is not that of the BGP peer, the BGP router discards the route update. To ignore the first AS number of EBGP route updates: Step 1. Enter system view. 2. Enter BGP view. 3. Configure BGP to ignore the first AS number of EBGP route updates. Command system-view bgp as-number ignore-first-as Remarks N/A N/A By default, BGP checks the first AS number of EBGP route updates. Tuning and optimizing BGP networks Configuration prerequisites BGP connections must be created. Configuring the BGP keepalive interval and holdtime After establishing a BGP connection, two routers send keepalive messages periodically to each other to keep the connection. If a router receives no keepalive or update message from the peer within the holdtime, it tears down the connection. You can configure the keepalive interval and holdtime globally or for a specific peer or peer group. The actual keepalive interval and holdtime depend on the following cases: • If the holdtime settings on the local and peer routers are different, the smaller one is used. The holdtime is no less than three seconds unless it is set to 0. • If the keepalive interval is 0 and the negotiated holdtime is not 0, the actual keepalive interval equals one-third of the holdtime. The maximum keepalive interval must be one third of the holdtime and no less than one second. • If the keepalive interval is not 0, the actual keepalive interval is the smaller one between one third of the holdtime and the keepalive interval. Follow these guidelines when you configure BGP keepalive interval and holdtime: • The intervals set with the peer timer command are preferred to those set with the timer command. 147

  • 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

147
Removing private AS numbers from updates to 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.
Configure BGP to remove private AS
numbers from the AS_PATH attribute of
updates to a peer or peer group.
peer
{
group-name
|
ip-address
}
public-as-only
By default, BGP updates
carry private AS numbers.
Ignoring the first AS number of EBGP route updates
Typically, BGP checks the AS_PATH attribute of a route update received from a peer. If the first AS number
is not that of the BGP peer, the BGP router discards the route update.
To ignore the first AS number of EBGP route updates:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Configure BGP to ignore the first AS
number of EBGP route updates.
ignore-first-as
By default, BGP checks the
first AS number of EBGP
route updates.
Tuning and optimizing BGP networks
Configuration prerequisites
BGP connections must be created.
Configuring the BGP keepalive interval and holdtime
After establishing a BGP connection, two routers send keepalive messages periodically to each other to
keep the connection. If a router receives no keepalive or update message from the peer within the
holdtime, it tears down the connection.
You can configure the keepalive interval and holdtime globally or for a specific peer or peer group. The
actual keepalive interval and holdtime depend on the following cases:
If the holdtime settings on the local and peer routers are different, the smaller one is used. The
holdtime is no less than three seconds unless it is set to 0.
If the keepalive interval is 0 and the negotiated holdtime is not 0, the actual keepalive interval
equals one-third of the holdtime. The maximum keepalive interval must be one third of the holdtime
and no less than one second.
If the keepalive interval is not 0, the actual keepalive interval is the smaller one between one third
of the holdtime and the keepalive interval.
Follow these guidelines when you configure BGP keepalive interval and holdtime:
The intervals set with the
peer timer
command are preferred to those set with the
timer
command.