HP 6125G HP 6125G & 6125G/XG Blade Switches Layer 3 - IP Routing Comma - Page 201

peer public-as-only (BGP/BGP-VPN instance view

Get HP 6125G PDF manuals and user guides View all HP 6125G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 201 highlights

If you both reference a routing policy and use the peer { group-name | ip-address } preferred-value value command to set a preferred value for routes from a peer, the routing policy sets the specified preferred value for routes matching it. Other routes not matching the routing policy uses the value set with the command. If the preferred value specified in the routing policy is zero, the routes matching it will also use the value set with the peer { group-name | ip-address } preferred-value value command. For information about using a routing policy to set a preferred value, see the command peer { group-name | ip-address } route-policy route-policy-name { export | import } in this document, and the command apply preferred-value preferred-value in "Routing policy configuration commands." Examples # In BGP view, configure the preferred value as 50 for routes from peer 131.108.1.1. system-view [Sysname] bgp 100 [Sysname-bgp] peer 131.108.1.1 preferred-value 50 # In BGP-VPN instance view, configure the preferred value as 50 for routes from peer 131.108.1.1. (The VPN has been created.) system-view [Sysname] bgp 100 [Sysname-bgp] ipv4-family vpn-instance vpn1 [Sysname-bgp-ipv4-vpn1] peer 131.108.1.1 preferred-value 50 peer public-as-only (BGP/BGP-VPN instance view) Syntax peer { group-name | ip-address } public-as-only View undo peer { group-name | ip-address } public-as-only BGP view, BGP-VPN instance view Default level 2: System level Parameters group-name: Name of a peer group, a string of 1 to 47 characters. ip-address: IP address of a peer. Description Use peer public-as-only to not keep private AS numbers in BGP updates sent to a peer/peer group. Use undo peer public-as-only to keep private AS numbers in BGP updates sent to a peer/peer group. By default, BGP updates carry private AS numbers. The command does not take effect if the BGP update has both public and private AS numbers. The range of private AS number is from 64512 to 65535. Examples # In BGP view, carry no private AS number in BGP updates sent to the peer group test. system-view [Sysname] bgp 100 [Sysname-bgp] peer test public-as-only 190

  • 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
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
190
If you both reference a routing policy and use the
peer
{
group-name
|
ip-address
}
preferred-value
value
command to set a preferred value for routes from a peer, the routing policy sets the specified preferred
value for routes matching it. Other routes not matching the routing policy uses the value set with the
command. If the preferred value specified in the routing policy is zero, the routes matching it will also use
the value set with the
peer
{
group-name
|
ip-address
}
preferred-value
value
command. For information
about using a routing policy to set a preferred value, see the command
peer
{
group-name
|
ip-address
}
route-policy
route-policy-name
{
export
|
import
} in this document, and the command
apply
preferred-value
preferred-value
in "Routing policy configuration commands."
Examples
# In BGP view, configure the preferred value as 50 for routes from peer 131.108.1.1.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp] peer 131.108.1.1 preferred-value 50
# In BGP-VPN instance view, configure the preferred value as 50 for routes from peer 131.108.1.1. (The
VPN has been created.)
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp] ipv4-family vpn-instance vpn1
[Sysname-bgp-ipv4-vpn1] peer 131.108.1.1 preferred-value 50
peer public-as-only (BGP/BGP-VPN instance view)
Syntax
peer
{
group-name
|
ip-address
}
public-as-only
undo
peer
{
group-name
|
ip-address
}
public-as-only
View
BGP view, BGP-VPN instance view
Default level
2: System level
Parameters
group-name
: Name of a peer group, a string of 1 to 47 characters.
ip-address
: IP address of a peer.
Description
Use
peer
public-as-only
to not keep private AS numbers in BGP updates sent to a peer/peer group.
Use
undo peer public-as-only
to keep private AS numbers in BGP updates sent to a peer/peer group.
By default, BGP updates carry private AS numbers.
The command does not take effect if the BGP update has both public and private AS numbers. The range
of private AS number is from 64512 to 65535.
Examples
# In BGP view, carry no private AS number in BGP updates sent to the peer group
test
.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp] peer test public-as-only