Good morning,
I would like to see if someone alreadfy ran into a similar problem,
We had a new F2e running in a 7k, no port configured or assigned that experienced the following issue :
2014 Mar 26 16:50:14 xxxxxxxxxxxxxx %MODULE-4-MOD_WARNING: Module 4 (Serial number: JAF1750ARMN) reported warning due to EOBC heartbeat failure in device DEV_EOBC_MAC (device error 0xc0a0614f)
2014 Mar 26 16:50:15 xxxxxxxxxxxxxx %MODULE-2-MOD_SOMEPORTS_FAILED: Module 4 (Serial number: JAF1750ARMN) reported failure on ports Ethernet4/21-24 (Ethernet) due to error in device DEV_CLP_XBAR (device error 0xca7056d7)
2014 Mar 26 16:50:15 xxxxxxxxxxxxxx %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on vsh.17810
2014 Mar 26 16:50:15 xxxxxxxxxxxxxx %MODULE-2-MOD_SOMEPORTS_FAILED: Module 4 (Serial number: JAF1750ARMN) reported failure on ports Ethernet4/21-24 (Ethernet) due to error in device DEV_CLP_XBAR (device error 0xca7056d7)
2014 Mar 26 16:50:15 xxxxxxxxxxxxxx %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on vsh.17815
2014 Mar 26 16:50:42 xxxxxxxxxxxxxx %PLATFORM-4-MOD_TEMPFAIL: Module-4 temperature sensor 9 failed
2014 Mar 26 16:54:06 xxxxxxxxxx %MODULE-2-MOD_SOMEPORTS_FAILED: Module 4 (Serial number: JAF1750ARMN) reported failure on ports Ethernet4/21-24 (Ethernet) due to error in device DEV_CLP_FWD (device error 0xca805600)
We had L2 issue for server when the traffic was going over that chassis, but in VDC, that should not have been impacted.
The problem was gone when we powered down the module.
I will update this discussion with the info I get from the tac as well.
Regards,
