Maintaining BGP4+

Maintaining BGP4+ involves resetting BGP4+ connections, clearing BGP4+ statistics, and debugging BGP4+.

Resetting BGP4+ Connections: Resetting BGP4+ connections interrupts peer relationships.

Clearing BGP4+ Statistics: Clearing BGP4+ statistics involves clearing route flapping statistics and route dampening statistics.

Configuring a Mode in Which BGP4+ Path Attributes Are Processed: To enhance reliability, you can configure a special mode in which BGP4+ path attributes are processed.

Setting a Priority That Determines the Disconnection Order of a BGP4+ Peer Relationship If Memory Overload Occurs: You can set a priority that determines the disconnection order of a BGP4+ peer relationship upon memory overload. If the system memory usage exceeds the alarm threshold and the BGP4+ memory usage is excessively high, such configurations allow BGP4+ peer relationships to be disconnected in order of priority. This prevents BGP4+ from exhausting the memory.

Enabling BGP4+ to Discard New Routes in the Case of a Memory Exception: After BGP4+ is enabled to discard new routes in the case of a memory exception, BGP4+ will discard the new routes received from peers in the case of a memory exception.

Configuring Whitelist Session-CAR for BGP4+: You can configure whitelist session-CAR for BGP4+ to isolate bandwidth resources by session for BGP4+ messages. This configuration prevents bandwidth preemption among BGP4+ sessions in the case of a traffic burst.