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.
The function of whitelist session-CAR for BGP4+ sets an independent CAR channel for each BGP4+ session to ensure that the bandwidth of each BGP4+ session is not preempted by other traffic (including traffic from other sessions of the same protocol and traffic from other protocols). When BGP4+ messages suffer a traffic burst, you can adjust the default parameters of whitelist session-CAR for BGP4+ if they do not meet service requirements. This ensures that BGP4+ messages can be sent properly.
In normal cases, you are advised to enable whitelist session-CAR for BGP4+. If this function becomes abnormal or adversely affects other services, you can run the whitelist session-car bgp disable command to disable this function.
The system view is displayed.
Parameters of whitelist session-CAR for BGP4+ are configured.
In normal cases, you are advised to use the default values of these parameters.
The configuration is committed.
Run the following command to check the previous configuration:
To check the statistics within a specific period of time, run the reset cpu-defend whitelist session-car bgpv6 statistics slot slot-id command to clear the existing statistics about whitelist session-CAR for BGP4+ on the specified interface board; after a certain period of time, run the display cpu-defend whitelist-v6 session-car bgpv6 statistics slot slot-id command.
The statistics about whitelist session-CAR for BGP4+ on a specified interface board cannot be restored after being cleared. Therefore, exercise caution when clearing the statistics.