Enabling Quick Ebgp Session Reestablishment - 3Com S7906E Configuration Manual

policies (if any), to filter updates to the BGP speaker, thus 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 (that is, determine whether to carry ORF information in messages;
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, refer to
Follow these steps to enable the BGP ORF capability:
To do...
Enter system view
Enter BGP view
Enable BGP route refresh for a
peer/peer group
Enable the non-standard ORF
capability for a BGP peer/peer
group
Enable the ORF capability for a
BGP peer/peer group
Table 1-2 Description of the both, send, and receive parameters and the negotiation result
Local parameter
send
receive
both

Enabling Quick eBGP Session Reestablishment

If the router receives no keepalive messages from a BGP peer within the holdtime, it disconnects from
the peer.
With quick eBGP connection reestablishment enabled, the router, when the link to a directly connected
eBGP peer is down, will reestablish a session to the eBGP peer immediately.
Use the command...
system-view
bgp as-number
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
The ORF sending capability is enabled locally and
the ORF receiving capability is enabled on the peer.
both
send
The ORF receiving capability is enabled locally and
the ORF sending capability is enabled on the peer.
both
Both the ORF sending and receiving capabilities are
both
enabled locally and on the peer, respectively.
1-35
Table
Remarks
—
—
Required
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.
Required
Disabled by default.
Negotiation result
1-2.