![]() ![]() The consistency checker is bound to CPU utilization and can not exceed the configured value while validating the tables acrossįeatures Supported in Consistency Checker (i.e, A Layer 3 Multicast with N outgoing interfaces can be validated for multicast entries along with OIFs programming,Ĭonstant memory usages irrespective of total entries in a table. Records any inconsistent entry with relevant data.Ĭonsistency checker supports the recursive single entry check which can validate the dependent objects along with the actualĮntry. Reports various inconsistencies (entry inconsistent, entry missing, stale entry) and sends a syslog to alert the administrator. Validates the IOS entry to software tables/processes (Forwarding manger-RP, Forwarding manager-FP and FED) for all modules. The last 5 snapshots are available any time for you to check the previous run's result.Į2E consistency checker performs the following functions: Using the runID, its status, summary, details can be viewed. Process entry is not consistent and helps speed up the debugging.Įvery time the consistency checker is started, a runID is provided. The consistency checker can be started for a single entry using the command which helps to isolate the issue at which forwarding Legacy Consistency Checker - supports validating the entry from control plane to the forwarding engine (or hardware copy).Įnd-to-End Consistency Checker - supports validating the software entry from control plane to all processes involved in distributingĪnd handling the entry, as well as the forwarding engine's hardware copy.Įnd-to-End (E2E) Consistency Checker supports full scan and single entry and should be started manually or run via gold diagnostic. There are two types of consistency checker implementation available: Scenarios where inconsistent states between software and hardware tables are causing issues in the network, thereby reducing The consistency checker supplements basic troubleshooting and helps to identify Increased troubleshooting time at a later period. If there is any inconsistency, it flags the issue immediately. The Consistency Checker collects information on various table states within the software and the hardware. Information about Consistency Checker Overview of Consistency Checker You can only detectįorwarding Manager-RP software entry is not supported in Layer3 Multicast Consistency Checker. Inconsistency in processes where CPU usage is high.įorwarding engine hardware (FED) check is not entirely supported in Layer3 Multicast Consistency Checker. Under very high CPU usage due to any other feature while a consistency checker running. Large table state changes (i.e clear, relearn etc). ![]() However, there could be rare cases of reporting aįalse positive in the following scenarios: Layer2 MAC Consistency Checker can validate the MAC address in hardware with software copy.Ĭonsistency checker is designed to reduce false positives in all cases. Only programming failures can be detected and reported. There is no command to stop/abort the already running Consistency Checkers.įorwarding Engine hardware entry validations are partially implemented. So, the previous runs cannot be displayed. Legacy Consistency Checkers do not have support for snapshot. ![]() It is not recommended to run the checkers at very short intervals. The Consistency Checker has the following limitations:Ĭonsistency Checkers are CPU intensive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |