OPERATIONAL DEFECT DATABASE
...
...
An initialization failure is reported by the CPP driver. A "Failed to initialize init device drivers(s)" message appears on the IOS console. Here's an example: *Nov 15 13:10:03.741: %CPPDRV-3-FATAL_INIT_ID: F0: cpp_driver: CPP0: (0x1) Failed to initialize init device drivers(s) - Operation not permitted -Traceback= This is a generic initialization failure message, so the CPP driver tracelog (cpp_driver*) must be checked to see if the following trace is present which points to this ddts: COMP0053/dui/A41C: QFP0.0 - unable to turn on termination for DUI0 Note: The memory configuration on ASR1002-X (Kingpin) is different from all the other ASR1k platforms. On ASR1002-X, the DUI channel can be any of DUI0 through DUI11 since Kingpin uses only x36 atris devices for both resource and packet buffer memory. On all other ASR1k systems, only DUI8 through DUI11 should be impacted, since only the packet buffer memory uses x36 devices. DUI0 thru DUI7 use x18 devices for the resource memory, and should not be impacted by this change. The QFP device number can be QFP0.0 through QFP0.3, since any Yoda ASIC can be impacted.
Router configuration or traffic pattern does not affect this problem. This issue only impacts qfp40 based systems (asr1002-x, asr1001-hx, asr1002-hx, ESP100, ESP200).
None. This is an intermittent issue and the failure only occurs during initialization. If the issue does occur, the system will reload and reinitialize. Once the system initializes successfully, there is no operational impact.
The fix is available in the following releases: XE313 / 15.4(3)S7 XE316 / 15.5(3)S5 16.3.3 16.4.1 16.5.1
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
