Sie sind auf Seite 1von 3
TECHNICAL SUPPORT BULLETIN May 6, 2010 TSB 2010-080-A SEVERITY: High - Operational PRODUCTS AFFECTED: Brocade

TECHNICAL SUPPORT BULLETIN

May 6, 2010

TSB 2010-080-A

SEVERITY: High - Operational

PRODUCTS AFFECTED:

Brocade 200E, 4012, 4016, 4018, 4020, 4024, 4424, 4100, 4900, 7500, 7600 and 48000

POTENTIAL PROBLEM AVOIDANCE:

This bulletin contains information on avoiding a potential problem when performing a firmware upgrade on any of the Brocade products listed above if their configuration is invalid.

BULLETIN OVERVIEW

A Brocade 200E, 4012, 4016, 4018, 4020, 4024, 4424, 4100, 4900, 7500 or 7600 switch or the standby CP within a Brocade 48000 director may remain in a perpetual reboot state when upgrading from Fabric OS version v6.1.x to Fabric OS version v6.2.x or later.

Brocade produces and publishes Technical Support Bulletins to OEMs, partners and customers that have a direct, entitled, support relationship in place with Brocade.

Please contact your primary service provider for further information regarding this topic and applicability for your environment

PROBLEM STATEMENT

Any one of the Brocade switches listed above or the standby CP within a Brocade 48000 director may remain in a perpetual reboot state when upgrading from Fabric OS version v6.1.x to Fabric OS version v6.2.x or later. Traffic is not disrupted when this occurs on the 48000 director. Traffic will eventually be disrupted if this occurs on any of the Brocade switches listed above.

This issue occurs if the director or switch is configured without a valid SSL certificate and HTTP is not enabled. This is an invalid configuration. On bootup, Fabric OS v6.2.x and later checks the configuration. If this invalid configuration is detected a critical management daemon fails to start. Since, the OS is unable to start the daemon it gets stuck in a perpetual reboot loop.

© 2010 Brocade Communications Systems, Inc. All Rights Reserved.

TSB 2010-080-A

RISK ASSESSMENT

If the invalid configuration, referenced above, exists at the time of upgrade from Fabric OS v6.1.x to Fabric OS v6.2.x or later, the CP being upgraded may get stuck in a reboot loop. Traffic is not disrupted when this occurs on the 48000 director. Traffic will eventually be disrupted if this occurs on any of the Brocade switches listed above. For these reasons, Brocade recommends that the user verify that HTTP is enabled prior to upgrading the OS. Detailed instructions are provided in the Corrective Action section of this document.

SYMPTOMS

Brocade 48000 Symptom

If the failure occurs while upgrading a Brocade 48000 director from Fabric OS v6.1.x to Fabric OS v6.2.x or later the following firmwaredownload failure message is reported by the active CP.

SUS_PEER_FS_CHECK: HA is not in sync

Active and Standby CPs failed to gain HA synchronization within 10 minutes.

Switch Symptom

If the failure occurs while upgrading one of the Brocade switches listed above from Fabric OS v6.1.x to Fabric OS v6.2.x or later the following type of message is reported by the switch.

2010/04/19-19:27:57, [HAM-1008], 549435, FFDC | CHASSIS, CRITICAL, engh-4100e2-g1, Rebooting the system for recovery - auto-reboot is enabled.

WORKAROUND

If the standby CP or switch appears to be stuck in a reboot loop, recovery is possible by logging in as root, via the serial console port, and executing the commands listed below. You will have approximately three minutes to execute the commands before the next reboot cycle occurs. Perform a cut and paste of these commands and execute them via the console port. After entering these commands, allow the switch or CP to complete the current reboot cycle.

sed ‘s/http.enabled:0/http.enabled:1/g’ < /etc/fabos/fabos.0.conf > tmp

cp tmp /etc/fabos/fabos.0.conf

cp tmp /mnt/etc/fabos/fabos.0.conf

rm tmp

CORRECTIVE ACTION

Before upgrading the firmware from Fabric OS v6.1.x to Fabric OS v6.2.x or later, execute the following steps. This ensures that HTTP is enabled.

StepStepStepStep 1:1:1:1: OnOnOnOn thethethethe activeactiveactiveactive CPCPCPCP ofofofof aaaa BrocadeBrocadeBrocadeBrocade 48000480004800048000 directodirectodirectodirectorrrr orororor thethethethe CPCPCPCP ofofofof aaaa BrocadeBrocadeBrocadeBrocade switchswitch:switchswitch:::

Login as admin

Execute the following command

admin> configshow http.enable

http.enabled:1

A value of ‘1’ should be observed. If so, skip to STEPSTEPSTEPSTEP 3333 for the Brocade 48000 director or STEPSTEPSTEPSTEP 4444 for a Brocade switch

StepStepStepStep 2:2:2:2:

Login as root

Execute the command shown below. If the highlighted parameter “HTTP enabled” is [no], you must change it ‘yes’. Depress the return key to review the remaining configuration items.

sw0:root> /fabos/libexec/webdconfigure/fabos/libexec/webdconfigure/fabos/libexec/webdconfigure/fabos/libexec/webdconfigure http attributes (yes, y, no, n): [no] y

enter y enter yes to change this parameter

HTTP Enabled

(yes, y, no, n): [no] yes

ErrorLog Enabled (yes, y, no, n): [no] AccessLog Enabled (yes, y, no, n): [no] SSLLog Enabled (yes, y, no, n): [no]

HTTP Port: (1

60000)

[80]

Secure HTTP Port: (1

60000)

[443]

HTTP IsAlive Check Enabled (yes, y, no, n): [yes]

HTTP Max HeapSize: (256

1024) [256]

After completing this step, the following type message may be seen in the error log. This message is purely informational; stating that someone has changed the HTTP enabled parameter.

“2010/04/11-15:05:16, [WEBD-1004], 60,, INFO, DCX_190, HTTP server will be restarted due to configuration change”

For switches, go to STEPSTEPSTEPSTEP 4.4.4.4.

StepStepStepStep 3333 (Standby(Standby(Standby(Standby CPCPCPCP inininin 48000480004800048000 onlyonly):onlyonly):):):

Login as admin

Execute the following command

admin> configshow http.enable

http.enabled:1

A value of ‘1’ should be observed. If so, skip ahead to STEPSTEPSTEPSTEP 44.44

Otherwise, execute the following commands.

Login as root

Execute the following command (this command must be on one single line).

StepStepStepStep 4:4:4:4:

sed ‘s/http.enabled:0/http.enabled:1/g’ < /etc/fabos/fabos.0.conf > tmp

Execute the following three commands

cp tmp /etc/fabos/fabos.0.conf

cp tmp /mnt/etc/fabos/fabos.0.conf

rm tmp

Upgrade to Fabric OS v6.2.x using the defined upgrade process for the target switch.