Set the cap for the features and enable the Capped-Enforcement feature using the SNMP set command. The SNMP set command is successful only when the cap enforcement count for all the features are greater than or equal to the current usage count. If the usage count for any feature is above the cap count, shutdown those resources and make sure that they are below or equal to the cap limit before issuing the SET command.
Platform, after synchronizing those values with the standby RP, enables the capped enforcement. So if the user tries to increase the usage beyond the CAP values, the resource are blocked and warning messages appear.
During the Return Material Authorization (RMA) of the SUP and when the SUP is moved across chassis, the stored cap numbers and the values configured while enabling cap enforcement are cleared. However, in a system with standby RP, if the standby RP has taken over, when the new RP is plugged in during RMA, the values are synced. In a non-redundant system, reissue the SNMP SET command after an RMA or when an SUP is moved across the chassis.
You cannot enable capped enforcement on Cisco cBR-8, which is already in a configuration lock state. However, a Cisco cBR8 that is cap enabled or not when fails to communicate with the license server for more than 90 days, moves to configuration lock state.
If you do not set the CAP count for a feature, the value is set to the default 0xfff_ffff (268435455).