You can configure whitelist session-CAR for IS-IS to isolate bandwidth resources by session for IS-IS packets. This configuration prevents bandwidth preemption among IS-IS sessions in the case of a traffic burst.
When IS-IS packets suffer a traffic burst, bandwidth may be preempted among different IS-IS sessions. To resolve this problem, you can configure whitelist session-CAR for IS-IS to isolate bandwidth resources by session. If the default parameters of whitelist session-CAR for IS-IS do not meet service requirements, you can adjust them as required.
The system view is displayed.
Parameters of whitelist session-CAR for IS-IS are configured.
In normal cases, you are advised to use the default values of these parameters.
Whitelist session-CAR for IS-IS is disabled.
By default, whitelist session-CAR for IS-IS is enabled. In normal cases, you are advised to keep this function enabled. Disable it if it becomes abnormal or adversely affects other services.
The configuration is committed.
After configuring whitelist session-CAR for IS-IS, verify the configuration.
Run the display cpu-defend whitelist-l2 session-car isis statistics slot slot-id command to check statistics about whitelist session-CAR for IS-IS on a specified interface board.
If you want to check such statistics within a specific period, first you can run the reset cpu-defend whitelist-l2 session-car isis statistics slot slot-id command to clear statistics about whitelist session-CAR for IS-IS on the specified interface board. After some time, run the display cpu-defend whitelist-l2 session-car isis statistics slot slot-id command again.