Enabling 4-Byte As Number Suppression - HP 3600 v2 series Configuration Manual

After you enable the BGP ORF capability, the local BGP router negotiates the ORF capability with the
BGP peer through Open messages. The local BGP router determines whether to carry ORF information
in messages. If yes, it will further determine 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
Follow these steps to enable the BGP ORF capability:
To do...
Enter system view
Enter BGP view
Enter IPv6 address family view
Enable BGP route refresh for a
peer or peer group
Enable the non-standard ORF
capability for a BGP peer or peer
group
Enable the ORF IP prefix
negotiation capability for a BGP
peer or peer group
Table 6 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.
Follow these steps to enable 4-byte AS number suppression:
Use the command...
system-view
bgp as-number
ipv6-family
peer { group-name |
ipv6-address } capability-advertise
route-refresh
peer { group-name |
ipv6-address } capability-advertise
orf non-standard
peer { group-name | ip-address |
ipv6-address } capability-advertise
orf ip-prefix { both | receive |
send }
Peer parameter
receive
both
send
both
both
340
Remarks
—
Required
—
Required
Enabled by default
Optional
By default, standard BGP ORF
capability defined in RFC 5291
and RFC 5292 is supported.
Required
Not supported 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, respectively.
Table 6.