R3721-F3210-F3171-HP High-End Firewalls Network Management Configuration Guide-6PW101

778
Ste
p
Command Remarks
4. Enable the non-standard ORF
capability for a BGP
peer/peer group.
peer { group-name |
ipv6-address } capability-advertise
orf non-standard
Optional.
By default, standard BGP ORF
capability defined in RFC 5291
and RFC 5292 is supported.
5. Enable the ORF IP prefix
negotiation capability for a
BGP peer/peer group.
peer { group-name | ip-address |
ipv6-address } capability-advertise
orf ipv6-prefix { both | receive |
send }
Not supported by default.
Table 87 Description of the both, send, and receive parameters and the negotiation result
Local
p
arameter Peer
p
arameter Ne
g
otiation 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, respectively.
Enabling 4-byte AS number suppression
The device supports 4-byte AS numbers and uses 4-byte AS numbers by default. If the peer devices
support only 2-byte AS numbers, you must enable the 4-byte AS number suppression function on the
device.
To enable 4-byte AS number suppression:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter BGP view.
bgp as-number N/A
3. Enter IPv6 address
family view or IPv6
BGP-VPN instance view.
ipv6-family [ vpn-instance
vpn-instance-name ]
N/A
4. Enable 4-byte AS
number suppression.
peer { group-name | ip-address }
capability-advertise suppress-4-byte-as
Disabled by default.
NOTE:
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.
Configuring the maximum number of load-balanced routes
To configure the maximum number of load balanced routes: