Enabling 4-Byte As Number Suppression - HPE FlexNetwork HSR6800 Configuration Manual

Layer 3-ip routing configuration guide
Hide thumbs Also See for FlexNetwork HSR6800:
Table of Contents

Advertisement

Step
Enter BGP view or
2.
BGP-VPN instance view.
Enable BGP route refresh for
3.
a peer or peer group.
Enable the non-standard
4.
ORF capability for a BGP
peer or peer group.
Enable the ORF capability
5.
for a BGP peer or peer
group.
Table 7 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 device that supports 4-byte AS numbers sends an Open message for session 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 session 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 session 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:
Step
Enter system view.
1.
Command
Enter BGP view:
bgp as-number
Enter BGP-VPN instance
view:
a. bgp as-number
b. ipv4-family
vpn-instance
vpn-instance-name
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
Command
system-view
221
Remarks
Use either method.
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 local end can only send ORF information, and the
peer end can only receive ORF information.
The local end can only receive ORF information, and the
peer end can only send ORF information.
Both the local and peer ends can send and receive ORF
information.
Remarks
N/A

Advertisement

Table of Contents
loading

Table of Contents