H3C Technologies H3C S7500E Series Switches - Manual (Page 240)

6-37
if yes, 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 Table 6-2 .
Follow these steps to enable the BGP ORF capability:
To do… Use the command… Remarks
Enter system view system-view —
Enter BGP view bgp as-number —
Enable BGP route refresh for a
peer/peer group
peer { group-name | ip-address }
capability-advertise
route-refresh
Required
Enabled by default.
Enable the non-standard ORF
capability for a BGP peer/peer
group
peer { group-name | ip-address }
capability-advertise orf
non-standard
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.
Enable the ORF capability for a
BGP peer/peer group
peer { group-name | ip-address }
capability-advertise orf ip-prefix
{ both | receive | send }
Required
Disabled by default.
Table 6-2 Description of the both, send, and receive parameters and the negotiation result
Local parameter Peer parameter Negotiation result
receive
send
both
The ORF sending capability is enabled locally and the
ORF receiving capability is enabled on the peer.
send
receive
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 Quick eBGP Session Reestablishment
If the router receives no keepalive messages from a BGP peer within the holdtime, it disconnects from
the peer.