Loading...
Loading...
Specific to: Catalyst 9400X-SUP-2, 9500 High Performance or 9600-SUP-1 Series switches reporting the following: %FED_CCK_ERRMSG-4-INCONSISTENCY_FOUND: Chassis 2 F0/0: fed: Consistency Checker(CCK) detected inconsistency for l3m_entry. AND 9500H#show consistency-checker run-id (run-id) detail Process: IOSD Process: FMAN-RP Process: FMAN-FP (Active) Process: FED (Active) Object-Type:l3m_entry Start-time:2023/02/22 15:18:43 Status:Completed State:Inconsistent <<<<<<<<< Key/data Reason (table_id:0x0, (*,239.1.1.1)) Hw inconsistency <<<<<<<< Entry Flags: C Total entries: 3 Obj_id/IfName: 0xf80004e1/L2LISP0 Obj_flags: F <<<<< Obj_id/IfName: 0xf8000461/Port-channel2 Obj_flags: A Obj_id/IfName: 0xf80004d1/L2LISP0 Obj_flags: F <<<<< Hardware Inconsistencies: HW_CHECK_TYPE:**rep-ri info** ErrorType :inconsistent Val :asic:0, ri(refcnt):0x16802(2), port_id:88() <<<<<< - 2 counted Exp Val:asic:0, ri(refcnt):0x16802(1), port_id:88() <<<<<< - 1 expected Where there is an additional entry for rep-ri info than expected by consistency checker.
As of today, this is only observed in the field when the following LISP configuration is used. But other scenarios and technologies (multicast, possibly) could see the same result in certain configurations. Have the following: Broadcast-underlay configured with LISP instance-ids using same multicast group on two or more instance-ids instance-id 100 service ethernet eid-table vlan 10 broadcast-underlay 239.1.1.1 <<<< database-mapping mac locator-set LAB-KL exit-service-ethernet ! exit-instance-id ! instance-id 101 service ethernet eid-table vlan 11 broadcast-underlay 239.1.1.1 database-mapping mac locator-set LAB-KL exit-service-ethernet 9500H#show ip mroute (*, 239.1.1.1), 00:31:46/stopped, RP 192.168.1.1, flags: SJC Incoming interface: Port-channel2, RPF nbr 10.2.3.2 Outgoing interface list: L2LISP0.100, Forward/Sparse-Dense, 00:31:46/00:01:43, flags: L2LISP0.101, Forward/Sparse-Dense, 00:31:46/00:01:43, flags: Must be a UADP 3.0 based switch for this defect to apply Must have "Exp Val" for (refcnt) to be 1 Must have "Val" for (refcnt) to be 2
Issue is not operationally impacting beyond the log message. Consistency checker is reporting the error due to the mismatch in counted vs expected values, but the mismatch is an issue with the checker logic and not the real entry programming. To filter the logs, a logging discriminator can be configured: logging discriminator filter-cck msg-body drops l3m_entry logging buffered discriminator filter-cck
Other models of catalyst switch not listed in the symptom are not impacted. This only affects models with the UADP 3.0 forwarding ASIC. If you see similar symptoms on another switch model, this defect will not address the issue. If you see the same error message have rep-ri info discrepancies that do not align exactly to these conditions, this defect may not apply The error message indicates the automatic consistency checker has detected a possible inconsistency between software programming layers, or software and hardware programming. In this case, the detection is incorrect and there is no issue beyond the checker itself not handling this scenario properly. If a consistency checker failure is seen for something outside the specific list of symptoms in this defect, another issue may be hit and other defects should be reviewed or a case opened with Cisco TAC.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.