White Papers
CoPP
Control Plane Policing (CoPP) in Dell EMC Networking OS provides a method for protecting CPU bound control plane packets by policing
packets punted to CPU with a specied rate and from undesired or malicious trac.
CoPP is implemented using:
• Rate shapers in CPU port scheduling nodes for queue based shaping
• Rate limiters in egress ACL for protocol based limiting
• Protocol to queue mapping
• Conguring CPU queue length
The user will need to congure the boot-type to warmboot under the reload-type conguration mode. Warmboot is a system reload
technique where the NPU will not restart. Only the CPU is restarted to bring up the upgraded software. Software upgrade ISSU, is the
typical use case for warmboot. Since BCM chip is already up and running while the software is restarted, there should not be any trac
outage during warmboot. However, since the CPU is restarted during the warmboot process, control plane trac drop will be observed and
the same would resume post warmboot.
Mirroring ow control packets
ISSU for mirroring ow control packets is a graceful implementation . The mirror ACL FP rules and the MTPs would be cleared out when
the box comes up in warmboot during the ISSU audit phase, and the ows are re-programmed again with mirror action when the mirroring
congurations are downloaded. In case of legacy L3 ACL based mirroring , the mirroring actions would be cleared out and re-programmed
while the FP rules are retained.
PFC
This feature has been designed to ensure that there is no trac loss with respect to PFC during warmboot or upgrade to a dierent switch
image.
The user will need to congure the boot-type to warmboot under the reload-type conguration mode. All the supported feature information
gets stored in a persistent storage, and when the switch goes in for a reload, all hardware programmed entries will be saved and trac will
be treated seamlessly, during reload. After the reload is complete, the running-cong and startup-cong will be compared and if there is a
dierence, the device will be programmed based on the startup-cong.
QoS
This feature has been designed to ensure that there is no trac loss with respect to QoS trac during warmboot or upgrade to a dierent
switch image.
The user will need to congure the boot-type to warmboot under the reload-type conguration mode. All the supported feature information
gets stored in a persistent storage, and when the switch goes in for a reload, all hardware programmed entries will be saved and trac will
be treated seamlessly, during reload. After the reload is complete, the running-cong and startup-cong will be compared and if there is a
dierence, the device will be programmed based on the startup-cong.
Tunnel Conguration
This feature has been designed to ensure that there is no trac loss with respect to tunneled trac during warmboot or upgrade to a
dierent switch image.
The user will need to congure the boot-type to warmboot under the reload-type conguration mode. All the supported feature information
gets stored in a persistent storage, and when the switch goes in for a reload, all hardware programmed entries in CAM and FIB will be saved
and trac will be treated seamlessly, during reload. After the reload is complete, the running-cong and startup-cong will be compared
482
In-Service Software Upgrade