Transient and punted traffic received on a sub-interface is policed to the previously configured storm control policer rate. To verify the storm control policer is present in hardware, get the NPU, Core and PP port values by running the below command on the affected line card: RP/0/RP0/CPU0:iox#sh controllers npu voq-usage interface all instance all location 0/0/CPU0 ------------------------------------------------------------------- Node ID: 0/1/CPU0 Intf Intf NPU NPU PP Sys VOQ Flow VOQ Port name handle # core Port Port base base port speed (hex) type ---------------------------------------------------------------------- Hu0/0/0/21 230 2 0 9 209 1256 7192 local 100G and execute the following diag shell command passing the PP port and Core numbers as arguments: sh controllers fia diag 2 "diag pp eplcr port=9 core=0" location 0/0/CPU0 If the storm control is configured in hardware, the output will look like this: RP/0/RP0/CPU0:iox#sh controllers fia diag 2 "diag pp eplcr port=9 core=0" location 0/0/CPU0 Node ID: 0/0/CPU0 |--------------------------------------------PORT 9-------------------------------------------------| ^M|-------------------------------------------------------------------------------------------------------------------| ^M| Data Type | Rate(kbps) | Burst(kbps) | Bucket(kbps) | Cir Disable | Color Blind | Packet Mode | Packet Adj | ^M|-------------------------------------------------------------------------------------------------------------------| ^M| UNK_UCAST | 159740 | 3200 | 1638 | FALSE | TRUE | TRUE | FALSE | ^M|- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | ^M| UCAST | 0 | 0 | 33292 | FALSE | TRUE | FALSE | FALSE | ^M|- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | ^M| UNK_MCAST | 159740 | 3200 | 1638 | FALSE | TRUE | TRUE | FALSE | ^M|- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | ^M| MCAST | 159740 | 3200 | 1638 | FALSE | TRUE | TRUE | FALSE | ^M|- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | ^M| BCAST | 159740 | 3200 | 1638 | FALSE | TRUE | TRUE | FALSE | ^M|- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | ^M|-------------------------------------------------------------------------------------------------------------------|
Configure storm control on multiple sub-interfaces of the same physical or bundle interface. Then remove relevant bridge domains from l2vpn configuration.
When removing a bridge domain from the l2vpn configuration and the attachment circuits in the bridge domain have storm control configuration, remove first the storm control configuration from the attachment circuit before removing the bridge domain configuration.
Recap of storm control configuration restrictions on NCS5500: 1) Storm control configuration is supported only at attachment circuit level, not at bridge domain level 2) Storm control is configured at attachment circuit (i.e. sub-interface) level, but it is applied at physical interface level. Consequence of point #2 above: 1) Storm control configuration of the first configured attachment circuit is programmed in hardware. Subsequent storm control configuration on any other sub-interface of the same physical interface is rejected and a syslog error is reported. Example: LC/0/1/CPU0:Mar 30 13:44:24.814 IST: l2fib[120]: %PLATFORM-PLAT_L2FIB_STORM-3-SC_EXIST_ERR_INTF_NAME : storm control config already present for the main interface Bundle-Ether1001 on sub-intf Bundle-Ether1001.2808 LC/0/1/CPU0:Mar 30 13:44:24.815 IST: l2fib[120]: %PLATFORM-PLAT_L2FIB_STORM-3-SC_MODIFY_ERR_INTF_NAME : cant modify storm control on this sub_intf Bundle-Ether1001.2855, Please modify on sub-intf Bundle-Ether1001.2808 to take an effect LC/0/1/CPU0:Mar 30 13:44:24.818 IST: l2fib[120]: %PLATFORM-PLAT_L2FIB_STORM-3-SC_MODIFY_ERR_INTF_NAME : cant modify storm control on this sub_intf Bundle-Ether1001.2855, Please modify on sub-intf Bundle-Ether1001.2808 to take an effect