S-Series with "doI2cAccess: CI2CBus::Access() failed for slave 0x40" errors

FAQ_User — Mon, 02 Dec 2013 22:31:00 GMT

Article ID: 14379

Products
S-Series

Symptoms
Error log ('show support') contains one or more instances of "CI2CBus::Access() failed for slave 0x40" error; for example:
<

code:

Dec 13 09:37:35 10.19.98.17 NIM[2.tBcPoEAccs]doI2cAccess:

code:

CI2CBus::Access() failed for slave 0x40 on NIM 1

Power over Ethernet (PoE) may not be working on a group of ports on the referenced module slot.

Cause
Given that module slots are identified in messages as "[<slot>.<task>]" and that "slave 0x40" refers to the PoE microcontroller , this particular message means that there is an I2C bus issue with the PoE microcontroller on a slot 2 module NIM.

Solution
Ensure that the PoE power header (looks like four parallel pins) is installed so that the NIM's RJ45 ports can physically receive PoE power.
See the "S-Series Option Module Quick Reference" guide, for more about the power header.

Contact the GTAC for assistance, as necessary.

See also: 14197.

topic S-Series with "doI2cAccess: CI2CBus::Access() failed for slave 0x40" errors in FAQs

S-Series with "doI2cAccess: CI2CBus::Access() failed for slave 0x40" errors