Enabling 4-Byte As Number Suppression - HP 6125G Configuration Manual

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
To enable the BGP ORF capability:
Step
1. Enter system view.
2. Enter BGP view.
3. Enable BGP route refresh for a
peer or peer group.
4. Enable the non-standard ORF
capability for a BGP peer or
peer group.
5. Enable the ORF capability for
a BGP peer or peer group.
Table 5 Description of the both, send, and receive parameters and the negotiation result
Local parameter
send
receive
both

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:
Command
system-view
bgp as-number
peer { group-name | ip-address }
capability-advertise route-refresh
peer { group-name | ip-address }
capability-advertise orf
non-standard
peer { group-name | ip-address }
capability-advertise orf ip-prefix
{ both | receive | send }
Peer parameter
•
receive
•
both
•
send
•
both
both
150
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.
Negotiation result
The ORF sending capability is enabled locally and the
ORF receiving capability is enabled on the peer.
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.
Table 5.