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
Enable BGP route refresh for
4.
a peer or peer group.
Enable the non-standard
5.
ORF capability for a BGP
peer or peer group.
Enable the ORF IP prefix
6.
negotiation capability for a
BGP peer or peer group.
Table 9 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 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 IPv6 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:
Step
Enter system view.
1.
Enter BGP view.
2.
Enter IPv6 address
3.
family view or IPv6
BGP-VPN instance
view.
Command
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
ipv6-prefix { both | receive |
send }
Peer parameter
receive
both
send
both
both
Command
system-view
bgp as-number
ipv6-family [ vpn-instance
vpn-instance-name ]
365
Remarks
Enabled by default.
Optional.
By default, standard BGP ORF
capability defined in RFC 5291
and RFC 5292 is supported.
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.
Remarks
N/A
N/A
N/A

Advertisement

Table of Contents
loading

Table of Contents