Limitations for Consistency Checker
The Consistency Checker has the following limitations:
-
Consistency Checkers are CPU intensive. It is not recommended to run the checkers at very short intervals.
-
Consistency Checkers do not have support for snapshot. So, the previous runs cannot be displayed.
-
There is no command to stop/abort the already running Consistency Checkers.
-
Forwarding Engine hardware entry validations are partially implemented. Only programming failures can be detected and reported.
-
Layer2 MAC Consistency Checker can validate the MAC address in hardware with software copy.
-
Consistency checker is designed to reduce false positives in all cases. However, there could be rare cases of reporting a false positive in the following scenarios:
-
Large table state changes (i.e clear, relearn etc).
-
Under very high CPU usage due to any other feature while a consistency checker running. The consistency checker may report inconsistency in processes where CPU usage is high.
-
-
Forwarding engine hardware (FED) check is not entirely supported in Layer3 Multicast Consistency Checker. You can only detect and report on programming failures.
-
Forwarding Manager-RP software entry is not supported in Layer3 Multicast Consistency Checker.