Turn on suggestions
![]() Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
|
01-30-2014 12:19 AM
I have DCX with (1) FCOE10-24 Blade, (1) FC8-16, and (1) FC8-48 running Firmware v6.4.3d.
When I installed Firmware v7.0.2d to avoid disruptive upgrade, it triggered "Faulting blade in slot 10" followed by "Slot 10 set to faulty, rc=20015." then "Firmwaredownload timed out in slot 10."
After the upgrade I saw only FCOE10-24 stayed firmware v6.4.3d and offline.
All network configuraitons were gone. Everything worked with marginal health state except FCOE10-24.
I reinstalled v6.4.3d and FCOE10-24 came back with all the configuration in tact.
Now it's back to Healthy state.
I checked v7.0.2d documentation but I have no clue what I did wrong.
Do I need to use Network Advisor to upgrade DCX with FCOE10-24 blade?
Thanks in advance for any assistance you can provide.
01-30-2014 12:50 AM
can you please provide to post "firmwareshow" and "slotshow -m" output ?
BNA is not required to upgrade the FOS
01-30-2014 02:05 AM
--->>>When I installed Firmware v7.0.2d to avoid disruptive upgrade.....
see follow Note:
Note: Upgrading from FOS v6.4.1_fcoe or FOS v6.4.x releases other than v6.4.1_fcoe1 to FOS v7.0.2d will be disruptive to FCoE traffic going through FCOE10-24 blades in DCX/DCX-4S.
continue
Upgrading firmware on a DCX or DCX-4S with one or more FCOE10-24 blades from FOS v6.3.x, v6.4.x, and v6.4.1_fcoe to FOS v7.0 or later will be disruptive to any traffic through the FCOE10-24 blades.
in such case, FC Traffic is non-disruptive, but the traffic going trough FCOE Blade is disruptive.
The error "rc=20015" refer in most case to Ethernet traffic, now i assume the firmwaredownload is failed due a mismatch FCoE config.
01-30-2014 08:43 AM
Thank you for the quick responses.
Now I understand that I missed "other than" part.
Here is the result of the 2 commands:
Slot Name Appl Primary/Secondary Versions Status
--------------------------------------------------------------------------
6 CP0 FOS v6.4.3d STANDBY
v6.4.3d
7 CP1 FOS v6.4.3d ACTIVE *
v6.4.3d
10 FCOE10-24 FOS v6.4.3d
v6.4.3d
Slot Blade Type ID Model Name Status
--------------------------------------------------
1 SW BLADE 55 FC8-32 ENABLED
2 SW BLADE 51 FC8-48 ENABLED
3 UNKNOWN VACANT
4 UNKNOWN VACANT
5 CORE BLADE 52 CORE8 ENABLED
6 CP BLADE 50 CP8 ENABLED
7 CP BLADE 50 CP8 ENABLED
8 CORE BLADE 52 CORE8 ENABLED
9 UNKNOWN VACANT
10 AP BLADE 74 FCOE10-24 ENABLED
11 UNKNOWN VACANT
12 UNKNOWN VACAN
I also found this:
2014/01/29-23:56:50, [FCOE-1046], 6520, SLOT 6 | CHASSIS, INFO, demodcx, fcoed.conf file is truncated. Please reconfigure FCoE ports.
2014/01/29-23:57:51, [SSMD-1300], 6526, SLOT 6 | FID 128, INFO, demodcx, CEE Map default is created with precedence 1.
2014/01/29-23:57:51, [SSMD-1303], 6527, SLOT 6 | FID 128, INFO, demodcx, CEE Map default priority group 1 with weight 40 is created with PFC enabled.
2014/01/29-23:57:51, [SSMD-1303], 6528, SLOT 6 | FID 128, INFO, demodcx, CEE Map default priority group 2 with weight 60 is created with PFC disabled.
2014/01/29-23:57:51, [SSMD-1302], 6529, SLOT 6 | FID 128, INFO, demodcx, CEE Map default priority table 2,2,2,1,2,2,2,2, are created.
2014/01/29-23:57:51, [CCFG-1003], 6530, SLOT 6 | FID 128, INFO, demodcx, System is ready to accept CEE user commands.
2014/01/29-23:57:53, [EM-1051], 6531, SLOT 6 | CHASSIS, INFO, Brocade_DCX, Slot 10: Inconsistency detected, FRU reinitialized.
2014/01/29-23:59:28, [BL-1003], 6541, SLOT 6 | FFDC | CHASSIS, CRITICAL, Brocade_DCX, Faulting blade in slot 10.
2014/01/29-23:59:28, [EM-1034], 6543, SLOT 6 | CHASSIS, ERROR, Brocade_DCX, Slot 10 set to faulty, rc=20015.
2014/01/29-23:59:32, [FW-1434], 6544, SLOT 6 | FID 128, WARNING, demodcx, Switch status change contributing factor Blade: 1 blade failures (10).
Looks like I need to use dcf.conf file to coy configuration over.
I will check Chapter 5 of the FOS v7.0.0 Converged Enhanced Ethernet Administrator’s Guide.
Thanks again.
01-30-2014 09:39 AM
FW-1434 stay indicated for Severity error.
Indicates that the switch is not in a healthy state. This occurred because the number of blade failures is
greater than or equal to the policy set by the switchStatusPolicySet command.
If the error persist, would suggest that you open a call with Brocad eor they OEM Supplier to procede for Blade replacement.