Setting a Priority That Determines the Disconnection Order of a BGP Peer Relationship If Memory Overload Occurs

You can set a priority that determines the disconnection order of a BGP peer relationship upon memory overload. If the system memory usage exceeds the alarm threshold and the BGP memory usage is excessively high, such configurations allow BGP peer relationships to be disconnected in order of priority. This prevents BGP from exhausting the memory.

Usage Scenario

If BGP consumes excessive memory resources, a board reset may occur. To prevent this issue, you can set a priority that determines the disconnection order of a BGP peer relationship upon memory overload. Memory overload here means that the system memory usage exceeds the alarm threshold and the BGP memory usage is excessively high. If this occurs, the BGP peer relationships are disconnected in order of priority to release memory. This ensures that the system operates as normal. A lower priority indicates that the associated peer relationship will be disconnected first.

Procedure

Run system-view
The system view is displayed.
Run bgp { as-number-plain | as-number-dot }
BGP is started (with the local AS number specified), and the BGP view is displayed.
Run peer ipv4-address as-number as-number
The IP address of a peer and the number of the AS where the peer resides are specified.
Run ipv4-family unicast
The BGP-IPv4 unicast address family view is displayed.
Run peer peerIpv4Addr memory-priority priority
A priority is set, which determines the disconnection order of the specified BGP peer relationship if memory overload occurs.
Run commit
The configuration is committed.

Verifying the Configuration

Run the display bgp peer verbose command to check the priority that determines the disconnection order of the specified BGP peer relationship if memory overload occurs.