Re: SG550x issue (fatal error)

Sebastian Helmer · ‎10-04-2018

Hello,

we have two stacks (2x2) running on different location with almost the same issue and the same config. Sometimes it seems to crash somewehre inside or so and after a few minutes/seconds the switch is back fine. Also the network is down in that moment.

From the techsupport file I would like to outline this:

***** FATAL ERROR *****
Reporting Task: HCWT.
Software Version: 2.4.0.94 (date May 31 2018 time 02:37:28)
ros(HOSTG_fatal_error+0x14) [0x2e62a4]
ros(OSSYSG_fatal_error+0x134) [0x8752ec] ros() [0x693ec0]
ros() [0xbc3c80]
/lib/libp2linux.so.1(+0x3aa4) [0xb6edbaa4]
/lib/libpthread.so.0(+0x6e64) [0xb6eb6e64]

***** END OF FATAL ERROR *****

05-Oct-2018 04:46:14 :%STCK SYSL-W-UNITTRP: UNIT ID 1,Trap:%Box-W-I2C-FAILURE-WRITE: I2C failed to write information to device at address 0x40 on bus 1 offset 0x33, component CPLD

05-Oct-2018 04:46:08 :%STCK SYSL-W-UNITTRP: UNIT ID 1,Trap:%Box-W-I2C-FAILURE-WRITE: I2C failed to write information to device at address 0x40 on bus 1 offset 0x33, component CPLD

05-Oct-2018 04:46:02 :%STCK SYSL-W-UNITTRP: UNIT ID 1,Trap:%Box-W-I2C-FAILURE-WRITE: I2C failed to write information to device at address 0x40 on bus 1 offset 0x33, component CPLD

05-Oct-2018 04:45:56 :%STCK SYSL-W-UNITTRP: UNIT ID 1,Trap:%Box-W-I2C-FAILURE-WRITE: I2C failed to write information to device at address 0x40 on bus 1 offset 0x33, component CPLD

05-Oct-2018 04:45:50 :%STCK SYSL-W-UNITTRP: UNIT ID 1,Trap:%Box-W-I2C-FAILURE-WRITE: I2C failed to write information to device at address 0x40 on bus 1 offset 0x33, component CPLD

05-Oct-2018 04:45:44 :%STCK SYSL-W-UNITTRP: UNIT ID 1,Trap:%Box-W-I2C-FAILURE-READ: I2C failed to read information from device at address 0x1B on bus 0 offset 0x05, component TC654E Fan Speed Controllers with Fan Fault Detection

05-Oct-2018 04:45:44 :%STCK SYSL-W-UNITTRP: UNIT ID 1,Trap:%Box-W-I2C-FAILURE-WRITE: I2C failed to write information to device at address 0x40 on bus 1 offset 0x33, component CPLD

05-Oct-2018 04:45:38 :%STCK SYSL-W-UNITTRP: UNIT ID 1,Trap:%Box-W-I2C-FAILURE-READ: I2C failed to read information from device at address 0x40 on bus 1 offset 0x10, component CPLD

05-Oct-2018 04:45:32 :%STCK SYSL-W-UNITTRP: UNIT ID 1,Trap:%Box-W-I2C-FAILURE-READ: I2C failed to read information from device at address 0x40 on bus 1 offset 0x30, component CPLD

05-Oct-2018 04:45:26 :%STCK SYSL-W-UNITTRP: UNIT ID 1,Trap:%Box-W-I2C-FAILURE-READ: I2C failed to read information from device at address 0x40 on bus 1 offset 0x20, component CPLD

I hope you have an idea..

Sujoy Paria · ‎10-05-2018

Hi Sebastian,

Thank you for your post. Similar error log has been reported earlier for the mentioned Switch series with older firmware version however I’m able to see there is little bit difference on the ‘Reporting Task: HCWT’ in your case and firmware version is upgraded.

We may need to process the replacement and gather more details for that Switch, such as…

How long the switch was running before failure
What was connected (especially PoE devices),

So it will be better if you can raise a service request with us by contacting our support centre based on your region. Contact numbers are available on the following link…

https://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html

Sebastian Helmer · ‎10-05-2018

Thank you for your reply.

I'm not 100% sure I guess the system runs just a few hours maybe about 12 or so..after that it seems to come up the problem.

We didn't saw the issue during the first day's because we used it just in a lab environment first.

I will open a case with my vendor or by myself.

PoE devices are not installed on the ports.

I disabled already cdp due to some research and smartports as well as green ethernet.