Enabling 4-Byte As Number Suppression; Enabling Quick Reestablishment Of Direct Ebgp Session - HP MSR Series Configuration Manual

Layer 3 - ip routing
Hide thumbs Also See for MSR Series:
Table of Contents

Advertisement

Table 8 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 session 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 session 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 BGP session 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
1.
Enter system view.
2.
Enter BGP view or BGP-VPN
instance view.
3.
Enable 4-byte AS number
suppression.

Enabling quick reestablishment of direct EBGP session

When the link to a directly connected EBGP peer is down, the router, with quick EBGP session
reestablishment enabled, tears down the session to the peer, and then reestablishes a session
immediately. If the function is not enabled, the router does not tear down the session until the holdtime
times out. A route flap does not affect the EBGP session state when the quick EBGP session
reestablishment is disabled.
To enable quick reestablishment of direct EBGP session:
Peer parameter
receive
both
send
both
both
Command
system-view
Enter BGP view:
bgp as-number
Enter BGP-VPN instance view:
a.
bgp as-number
b.
ipv4-family vpn-instance
vpn-instance-name
peer { group-name | ip-address }
capability-advertise
suppress-4-byte-as
204
Negotiation result
The local end can only send ORF information, and the peer
end can only receive ORF information.
The local end can only receive ORF information, and the
peer end can only send ORF information.
Both the local and peer ends can send and receive ORF
information.
Remarks
N/A
Use either method.
Disabled by default.

Advertisement

Table of Contents
loading

Table of Contents