07-28-2013 07:41 AM
Frequently getting following warning message on DC04 San Director Switch..
2013/07/28-11:54:38, , 577, SLOT 5 | CHASSIS, CRITICAL, Brocade_DCX4S, S2,C1: Internal monitoring has identified suspect hardware, blade may need to be reset or replaced: fau1:0xd5, fau2:0xf0000065 th2:0x
2013/07/28-11:59:38, , 578, SLOT 5 | CHASSIS, WARNING, Brocade_DCX4S, S2,C1: Internal link errors reported, no hardware faults identified, continuing monitoring: fault1:0xd5, fault2:0xf0000000 thresh1:0x
firmwareshow -v :
CURRENT CONTEXT -- 0 , 128
Slot Name Appl Primary/Secondary Versions Status
4 CP0 FOS v7.1.0b STANDBY
5 CP1 FOS v7.1.0b ACTIVE *
07-28-2013 08:24 AM
Odd, you're just stating something.
But according to my tarot cards you are looking for advise what to do next.
The c2-1010 tells you there is something wrong with the blade in slot 2.
If you can powercycle the blade or get it replaced
08-12-2013 05:14 AM
the output of command errdumpall may provide a little bit more of info for that error. As dion posted, powerclycling port blade in slot 2 may fix the issue, but powercycling one of the involved Core blades could also make those errors disappear and it would be less disruptive.
08-12-2013 10:59 AM
to avoid some confusion
--->>>but powercycling one of the involved Core blades......
error message both C2-1006 and 1010 stay indicated a error within S2 = Slot 2
Core Blade are not located in Slot 2
08-13-2013 12:10 AM
You're right TechHelp24, but very often these messages are reported due to errors in the connection between a port blade (in slot 2 in this case) and one of the Core Blades (slot 3 and 6 in this model). By reviewing errdumpall, we can check that out.
08-13-2013 02:24 AM
-->>...but very often these messages are reported due to errors in the connection between a port blade (in slot 2 in this case) and one of the Core Blades (slot 3 and 6 in this model).
I've no intention to discuss a long, but Honestly, I am not sure why you use here this terminology "very often"
As per my opinion that hear to me you want to say, as Brocade had a higher issue/impact with such error message.
And more less, I'm not sure how many DCX you manage.
However I am quite sure, I've a lot of large customer with very critical environments, where I supported more dozen DCX, and never see or have any similarly problem.
In all the years since Brocade launched DCX Family, I had only at one time a Hardware Issue. Here was necessary to replace a Control Processor in a BRAND NEW DCX, caused by manufacturing defect.
08-13-2013 03:10 AM
I did not mean that these events occur very ofter (my bad If I hinted that...), but when they appear, are often preceded by C2-5825's which report errors in the communication between Port Blade and Core Blade.
errdumpall will report more info regarding the cause of the C2-1006 and C2-1010.