Error Logs in Cisco ISR4221

y_ananthan · ‎07-03-2017

Hi Experts,

We have purchased a new Cisco ISR4221 with NIM-2BRI-NT/TE= module and we have receiving this error logs from router.

Cisco IOS Software [Everest], ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9_IAS-M), Version 16.5.1b, RELEASE SOFTWARE (fc1)

cisco ISR4221/K9 (1RU) processor with 1632707K/6147K bytes of memory.
Processor board ID XXXXXXXXXXXX
1 Virtual Ethernet interface
6 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
6598655K bytes of flash memory at bootflash:.
0K bytes of WebUI ODM Files at webui:.

%INIT: waited 0 seconds for NVRAM to be available

*Jul 3 08:05:27.936: %SMART_LIC-6-AGENT_READY: Smart Agent for Licensing is initialized
*Jul 3 08:05:28.648: %IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Module name = esg Next reboot level = securityk9 and License = securityk9
*Jul 3 08:05:28.678: %IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Module name = esg Next reboot level = ipbasek9 and License = ipbasek9
*Jul 3 08:05:30.273: %ISR_THROUGHPUT-6-LEVEL: Throughput level has been set to 35000 kbps
*Jul 3 08:05:31.260: %IOSXE_RP_NV-3-NV_ACCESS_FAIL: Initial read of NVRAM contents failed
*Jul 3 08:05:35.961: %NBAR-6-CACHE_SYNC_INFO: Cache synchronization. Initialized.

Press RETURN to get started!

*Jul 3 08:05:37.349: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan
*Jul 3 08:05:37.912: in NSH init

*Jul 3 08:05:38.346: %LINK-3-UPDOWN: Interface Lsmpi0, changed state to up
*Jul 3 08:05:38.347: %LINK-3-UPDOWN: Interface EOBC0, changed state to up
*Jul 3 08:05:38.347: %LINK-3-UPDOWN: Interface LIIN0, changed state to up
*Jul 3 08:03:28.486: %CMCC-5-UNSUPPORTED_MODULE: SIP0: cmcc: Unsupported Module inserted. The module NIM-2BRI-NT/TE on the slot 0 may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.
*Jul 3 08:03:28.592: %IOSXE-3-PLATFORM: SIP0: kernel: dash_c2w_op_done: I2C Master time out: status register - 0x0
*Jul 3 08:03:28.592: %IOSXE-3-PLATFORM: SIP0: kernel: dash_i2c_xfer: I2C Master Error master=13 addr=0x1c status=0x0
*Jul 3 08:03:28.666: %IOSXE-3-PLATFORM: SIP0: kernel: dash_c2w_prep_master: I2C Master Busy - aborting
*Jul 3 08:03:29.946: %IOSXE-3-PLATFORM: SIP0: kernel: dash_c2w_op_done: I2C Master time out: status register - 0x0
*Jul 3 08:03:29.947: %IOSXE-3-PLATFORM: SIP0: kernel: dash_i2c_xfer: I2C Master Error master=13 addr=0x1c status=0x0
*Jul 3 08:03:29.947: %IOSXE-3-PLATFORM: SIP0: kernel: show_reg_output_1 (line 142): read pca9557 register at 01 failed
*Jul 3 08:03:29.947: %IOSXE-3-PLATFORM: SIP0: kernel: dash_c2w_prep_master: I2C Master Busy - aborting
*Jul 3 08:03:29.948: %IOSXE-3-PLATFORM: SIP0: kernel: show_reg_input_0 (line 141): read pca9557 register at 00 failed
*Jul 3 08:03:30.178: %IOSXE-3-PLATFORM: SIP0: kernel: dash_c2w_prep_master: I2C Master Busy - aborting
*Jul 3 08:03:30.178: %IOSXE-3-PLATFORM: SIP0: kernel: show_reg_input_0 (line 141): read pca9557 register at 00 failed
*Jul 3 08:03:31.210: %IOSXE-3-PLATFORM: SIP0: kernel: dash_c2w_prep_master: I2C Master Busy - aborting

Any advise on this ?

Thank you.

Mark Malone · ‎07-03-2017

Reseat the module see if it goes , if not you can follow the below check the coverage make sure its legit, if it stays faulty get them to replace it

%CMCC-5-UNSUPPORTED_MODULE : Unsupported Module inserted. The module [chars] on the slot [dec] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.

Hardware in the specified location could not be identified as a genuine Cisco product.

If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.

Mark Malone · ‎07-03-2017

https://cway.cisco.com/docs/SNChecker/1.6.0/coverage-checker-checking-status/coverage-checker-checking-status.htm