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

Enabling 4-byte AS number suppression, Command, Remarks, Local parameter, Peer parameter

Page 160 highlights

whether to carry non-standard 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 5. To enable the BGP ORF capability: Step Command 1. Enter system view. system-view 2. Enter BGP view. bgp as-number 3. Enable BGP route refresh for a peer { group-name | ip-address } peer or peer group. capability-advertise route-refresh 4. Enable the non-standard ORF peer { group-name | ip-address } capability for a BGP peer or capability-advertise orf peer group. non-standard 5. Enable the ORF capability for peer { group-name | ip-address } a BGP peer or peer group. capability-advertise orf ip-prefix { both | receive | send } Remarks N/A N/A Enabled by default. Optional. By default, standard BGP ORF capability defined in RFC 5291 and RFC 5292 is supported. If the peer supports only non-standard ORF, you need to configure this command. Disabled by default. Table 5 Description of the both, send, and receive parameters and the negotiation result Local parameter send Peer parameter • receive • both Negotiation result The ORF sending capability is enabled locally and the ORF receiving capability is enabled on the peer. receive both • send • both both The ORF receiving capability is enabled locally and the ORF sending capability is enabled on the peer. Both the ORF sending and receiving capabilities are enabled locally and on the peer. Enabling 4-byte AS number suppression When a switch that supports 4-byte AS numbers sends an Open message for peer relationship establishment, the Optional parameters field of the message indicates that the AS number occupies four bytes-in the range of 1 to 4294967295. If the peer device does not support 4-byte AS numbers (for examples, it supports only 2-byte AS numbers), the peer relationship cannot be established. After you enable the 4-byte AS number suppression function, the peer device can then process the Open message even though it does not support 4-byte AS numbers, and the BGP peer relationship can be established. If the peer device supports 4-byte AS numbers, do not enable the 4-byte AS number suppression function; otherwise, the BGP peer relationship cannot be established. To enable 4-byte AS number suppression: 150

  • 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

150
whether to carry non-standard 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 5
.
To enable the BGP ORF capability:
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
Enabled by default.
4.
Enable the non-standard ORF
capability for a BGP peer or
peer group.
peer
{
group-name
|
ip-address
}
capability-advertise orf
non-standard
Optional.
By default, standard BGP ORF
capability defined in RFC 5291
and RFC 5292 is supported.
If the peer supports only
non-standard ORF, you need to
configure this command.
5.
Enable the ORF capability for
a BGP peer or peer group.
peer
{
group-name
|
ip-address
}
capability-advertise orf ip-prefix
{
both
|
receive
|
send
}
Disabled by default.
Table 5
Description of the both, send, and receive parameters and the negotiation result
Local parameter
Peer parameter
Negotiation result
send
receive
both
The ORF sending capability is enabled locally and the
ORF receiving capability is enabled on the peer.
receive
send
both
The ORF receiving capability is enabled locally and the
ORF sending capability is enabled on the peer.
both
both
Both the ORF sending and receiving capabilities are
enabled locally and on the peer.
Enabling 4-byte AS number suppression
When a switch that supports 4-byte AS numbers sends an Open message for peer relationship
establishment, the Optional parameters field of the message indicates that the AS number occupies four
bytes—in the range of 1 to 4294967295. If the peer device does not support 4-byte AS numbers (for
examples, it supports only 2-byte AS numbers), the peer relationship cannot be established.
After you enable the 4-byte AS number suppression function, the peer device can then process the Open
message even though it does not support 4-byte AS numbers, and the BGP peer relationship can be
established.
If the peer device supports 4-byte AS numbers, do not enable the 4-byte AS number suppression
function;
otherwise, the BGP peer relationship cannot be established.
To enable 4-byte AS number suppression: