- The bcmDPC is responsible for reporting messages to the shell. Whenever there is a parity error in the L2/L3 table received this process reports this information.
- These errors are continuously coming in therefore overloading the process and possibly causing the issue.
- Unfortunately, we do not have a command to verify the parity error related to process “bcmDPC” is increasing or not.
The below two steps are implemented in order to kill the “bcmDPC” process:
- Rebooting the switch when you have a maintenance window is the simplest way to bring down the high CPU utilization by “bcmDPC” process.
- Clearing the forwarding database seems fixing this issue as well. The command is clear fdb?. The switch will have to re-learn all forwarding information which should be unnoticeable, but may cause short slowdown in traffic (depending on the number of FDB entries).