F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices Network Management Configuration Guide-6PW100

817
(if any), to filter updates to the BGP speaker, reducing the number of exchanged update messages and
saving network resources.
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 further determines 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
2994HTable 72.
To enable the BGP ORF capability:
Ste
p
Command Remarks
1305. Enter system view.
system-view
N/A
1306. Enter BGP view.
bgp as-number N/A
1307. Enter IPv6 address
family view.
ipv6-family N/A
1308. Enable BGP route
refresh for a peer or peer
group.
peer { group-name | ipv6-address }
capability-advertise route-refresh
Enabled by default.
1309. Enable the
non-standard ORF capability
for a BGP peer or 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.
1310. Enable the ORF IP prefix
negotiation capability for a
BGP peer or peer group.
peer { group-name | ip-address |
ipv6-address } capability-advertise orf
ipv6-prefix { both | receive | send }
Not supported by default.
Table 72 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.
950BEnabling 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.