Director Models 640b Upgrade

8/11/2019 Director Models 640b Upgrade

1/14

Revision (1.0) September 13, 2010-Page 1-

Connectrix B-Series Procedure

Director Model Fabric OS 6.4.0b Upgrade

INFORMATION ABOUT THIS PROCEDURE

This document steps you through the completion of a Connectrix management activity that can becompleted without the involvement of Remote Technical Support. If you have any concerns, questions, orneed assistance with an implementation, regarding your environment or this procedure, please contactEMC Customer Support.

As part of the effort to continuously improve and enhance the performance and capabilities of theConnectrix product line, EMC periodically releases new versions of its hardware and software, or qualifiesvarious systems interoperability with the Connectrix product family. Therefore, some functions describedin this procedure may not be supported by all revisions of the software or hardware you have currently inuse. For the most up-to-date information on specific requirements concerning your environment, refer tothe Fabric OS Release Notesfor your version and the E-Lab Interoperability Navigator onPowerLink.

Site Ac tivity and Event Rec ord

For your own change management practices, you may need to document this task activity. You may notecritical information in the log area below:

Ac tivity Event Tme

Date/Time:

Task Ac tivity or Event

Task being executed:Performed by:

Switc h Information

Switch Serial Number:

Switch Model:

Switch Name:

Switch Chassis IP:

Switch CP0 IP:

Switch CP1 IP:
http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/


2/14


Contents

Introduction .................................................................................................................................................... 3

Known issues, Limitations and Restrictions .............................................................................................. 3Assumptions .............................................................................................................................................. 4

Preparation Tasks ..................................................................................................................................... 5

Task 1: Reading and understanding the procedure before you begin ................................................ 5Task 2: Obtaining software .................................................................................................................. 5Task 3: Setting up the working environment ....................................................................................... 6

Verify Connectivity ......................................................................................................................................... 6

Open a HyperTerminal or Telnet session ..................................................................................................... 6

Task 4: Record and verify configuration .............................................................................................. 7Upgrade Tasks .......................................................................................................................................... 9

Task 1: Back up and save the current switch configuration ................................................................ 9Task 2: Firmware upgrade and final steps ........................................................................................ 10

Upgrade firmware ........................................................................................................................................ 10

Final changes, verification, and backup ...................................................................................................... 11


3/14


Introduction

This procedure explains how upgrade a Director Model B-Series switch to Fabric OS (FOS) version 6.4.0b

using the Fabric OS command line interface. You may also use the Web Tools or Connectrix Manager

Data Center Edition applications. Please refer to the Web Tools Administrators Guideor the EMC

Connectrix Manager Data Center Edition Users Guidefor more information.

Overview

Preparation tasks

Upgrade tasks

Known issues, Limitations and Restrictions

The switch must be running a minimum version of FOS 6.3.0b in order to upgrade.

This firmware upgrade documentation is only applicable to the following director class models:

ED-48000B

ED-DCX-B

ED-DCX-4S-B

FOS does not support concurrent FC Routing (EX_Ports) and TopTalkers features. If there are

multiple node EGs (encryption groups) in a fabric, please complete firmwaredownload on one node at

a time before downloading on another node.

A code load of ED-DCXB or ED-DCX-4S-B with one or more PB-DCX-24FCOE blades from FOS6.4.0b to another version will disrupt traffic through the blade.

Disable the ports in DCX Logical Switches that use 10 bit addressing mode that have 8 bit areas in therange 0x70-0x8F before upgrading to FOS v6.4.0b. Otherwise firmware upgrade will fail with an error

message. This step is necessary even if users do not plan to use PB-DCX-64P-8G blades afterperforming firmware upgrade to FOS v6.4.0b. However, if areas 0x70-0x8F are not in use this step isnot necessary. Please use portAddress CLI to find out the areas in use within a Logical Switch.

If Bottleneck detection feature is currently enabled on the switch running FOS v6.3.x, you must disableit before upgrading to FOS v6.4.0b; otherwise, frame drops may occur due to increased Hot Code Load(HCL) time.

The PB-DCX-FX8-24 blade must be power cycled after upgrading from FOS v6.3 to FOS v6.4.0b. Thisis necessary to load the new FPGA image that enables IPv6 capability for FCIP links to PB-DCX-FX8-24 blade. This step is mandatory even if IPv6 will not be used on the FCIP ports. Not performing thisstep will result in unpredictable behaviors on the FCIP links. Please note that in the case of PB-DCX-FX8-24, only the PB-DCX-FX8-24 blade needs to be power cycled and not the entire DCX/DCX-4S

chassis.

If a switch with FOS v6.2 in FIPS (Federal Information Processing Standards) mode with only LDAPauthentication support is upgraded to v6.4.0b, login will fail. A switch with v6.2 in FIPS mode must haveboth LDAP and local authentication configured before upgrading to v6.4.0b. Once the switch is fullyoperational the user can login to the switch and import the certificate again. If the switch is not in FIPSmode, users can login to the switch with LDAP after upgrading to v6.4.0b and then import thecertificate.


4/14


Always refer to the current version of the Fabric OS Release Notes, the E-Lab Interoperability Navigator

onPowerLink, and EMCs Knowledgebase (Primus) for up to date information. Solutionemc234016is a

good starting place to find some important ETAs and known issues. Known issues, restrictions, and

limiations listed here are onlyfor director switches. You must consult the departmental upgrade

instructions for any known issues, restrictions, and limitations if you are also upgrading them.

Recommended Migration Paths to FOS v6.4.0b for Director Switches

Migrating from FOS v6 2 x

For switches currently running FOS 6.2.x the following are the recommended upgrade paths; FOS 6.3.1ais the recommended stepping version except for ED-DCX-B's or ED-DCX-4S-B with the PB-DCX-FX8-24FCiP blades the recommended 6.3.x stepping code is FOS 6.3.1b.

Note: Since FOS 6.3.1b is not an ESM listed release it should only be used on an interim basis as

a stepping code from FOS 6.2.x to 6.4.0b. Please contact your local EMC support representativeto initiate the process to have this non EMC GA release installed (RPQ).

Migrating from FOS v6 3 x

For switches currently running FOS 6.3.x the following are the recommended upgrade paths:

Any EMC Support Matrix listed 6.3.x version is suitable to upgrade from 6.3.x to FOS 6.4.0b withthe exception of ED-DCX-B's or ED-DCX-4S-B's with PB-DCX-FX8-24 FCiP blades.For ED-DCX-B's or ED-DCX-4S-B's, the recommended 6.3.x version to upgrade from is FOS6.3.1b.

Notesince FOS 6.3.1b is not an ESM listed release it should only be used on an interim basis asa stepping code from FOS 6.2.x to 6.4.0b. Please contact your local EMC support representativeto initiate the process to have this non EMC GA release installed.

Assumptions

This upgrade procedure assumes the following:

Before beginning the upgrade procedure, both of the switchs CP (control processors) must be IP

accessable for establishing a Telnet (or HyperTerminal session), and for the firmwaredownload to

establish an FTP connection to the FTP server. A cross over cable connection to one of the CPs will

NOT work.

Working knowledge of the Connectrix B Series switch product family.

If these assumptions are not true, please contact EMC Customer Support for advice before continuing.

WARNING: This procedure takes approximately 45 minutes to complete. Please plan accordingly.

To further help you understand what is involved, the table that follows lists the high-level tasks required for

this upgrade. Take a moment to become familiar with these tasks. If you have any questions, contact
http://powerlink.emc.com/http://powerlink.emc.com/http://powerlink.emc.com/http://csexplorer.isus.emc.com/eservice/iviewcs/ui/eserver.asp?id=emc234016http://csexplorer.isus.emc.com/eservice/iviewcs/ui/eserver.asp?id=emc234016http://csexplorer.isus.emc.com/eservice/iviewcs/ui/eserver.asp?id=emc234016http://csexplorer.isus.emc.com/eservice/iviewcs/ui/eserver.asp?id=emc234016http://powerlink.emc.com/


5/14


Customer Support before you begin the upgrade.

Preparation Tasks

Task 1: Reading and understanding the procedure before you begin

Task 2: Obtaining software

Task 3: Setting up the working environment

Task 4: Record and verify configuration

Upgrade Tasks

Task 1: Back up and save the current switch configuration

Task 2: Firmware upgrade and final steps

Preparation Tasks

Before you start the actual upgrade, prepare by performing the tasks in this section.

CAUTION: The examples used in this document, including the paths used in the command lines,

are relative to ftproot, and assume the ftp server was configured to use C:\ as its ftproot. Refer to thedocumentation for your ftp server or the instructions in the included 3CDaemon zip file for configurationinstructions.

Task 1: Reading and understanding the procedure before you begin

1. ( ) To prevent errors, save time, and to minimize customer downtime, please read through the entire

upgrade procedure at least once. If you do not understand the upgrade procedure steps, contact

Customer Support before you begin the upgrade.

Task 2: Obtaining software

2. ( ) Create a download directory on the FTP server host machine that you will be using for your

upgrade.

Example:Wi ndows host s: c: \ t emp\ brocadeUni x host : / t mp/ br ocade

1. ( ) Download firmware file BRCDFOS6_4_0b.zipfrom the appropriate location. EMC personnel

download it from the Customer Service Web Siteherewhile EMC Partners use the EMCPartners

site.

This file consists of the following:

Firmware zip file

Release Notes

Upgrade Document

3CDaemon FTP Utility

NOTE:The FTP utility is included for your convenience in the event you (or your customer) do not

have access to an FTP server.

3. ( ) Unzip the file BRCDFOS6_4_0b.zipthat you downloaded in Step1. ( ) to the directory you

created in Step2. ( ). If using WinZip, ensure that Use folder names is checked so that files are

placed in their appropriate locations. If using another utility make sure folders are created during the

unzip process.
http://www.cs.isus.emc.com/csweb2/esn/esnhome.htmhttp://www.cs.isus.emc.com/csweb2/esn/esnhome.htmhttp://www.cs.isus.emc.com/csweb2/esn/esnhome.htmhttp://www.emc.com/partners/index.htmhttp://www.emc.com/partners/index.htmhttp://www.emc.com/partners/index.htmhttp://www.emc.com/partners/index.htmhttp://www.emc.com/partners/index.htmhttp://www.emc.com/partners/index.htmhttp://www.cs.isus.emc.com/csweb2/esn/esnhome.htm


6/14


4. ( ) Unzip the file named v6.4.0b.zip that was just extracted to the directory you created in Step2. ( ).

Again, if using Winzip, ensure that Use folder names is checked.

Task 3: Setting up the work ing environment

Verify Connectivity

5. ( ) Open a command prompt on the host machine you will be using for the procedure and pingthe IP

addresses of the switch to verify connectivity. Director class switches have multiple IP addresses

assigned to them. You must verify connectivity (ping) to both CPs in addition to the chassis IP

address. (ipaddrshowis the Brocade command to display the different IP addresses of the switch.)

6. ( ) Firmwaredownloads are hardcoded that they must complete in 30 minutes after being started.

This time restriction therefore mandates there to be adequate bandwidth in the IP network for the

firmware to download to the switch within the 30 minute time window. Slow connections may cause

the firmwaredownload to time out. To check the type of connection to the CPs open a command

prompt on the switch and issue the ifmodeshowcommand for each of the Ethernet interfaces (CPs).

Verify that the connections from the CPs to the IP network will allow for adequate bandwidth to

download the firmware. For some configurations half duplex connections will not provide adequate

bandwidth for firmwaredownload to complete. If firmwaredownloads time out you may need to

change the CPs IP connections.

Example:

#swi t ch: admi n> ifmodeshow eth0

Link mode: negotiated 100baseTx-HD, link ok {indicates 100Mbs connection at Half Duplex}

MAC Address: 00:60:69:D0:24:40

7. ( ) If your FTP server is on a different machine, open a command prompt on it and pingthe IP

address of the switch to verify connectivity. If you are unable to ping the switch from the FTP host,

there may be a firewall or other connectivity issue involved.

CAUTION: EMC Supplied Field Laptops and some Customer Sites

The firewall service or other services such as Antivirus software may be required to be stopped prior

to the firmware upgrade. For example, to stop the firewall BlackICE:

1. Go into services (under Administrative Tools in Windows).

2. Right click and select the process BlackICE and select stop.

----- If the service will not stop, you must change the startup type to manual and reboot.

----- Right click under services, select properties, and change the startup type to Manual.

3. Complete the firmware upgrade procedure.

4. Restart / Reset the BlackICE service if necessary when the upgrade is complete.

If you have McAfee 8.x VirusScan installed, you may need to reconfigure it. To reconfigure it, go to

the McAfee VirusScan Console, select Access Protection, and deselect FTP inbound

Open a HyperTerminal or Telnet session

8. ( ) Launch HyperTerminal or the Telnet application of your choice and establish a session to either


7/14


the chassis or active CP IP address of the switch being upgraded. If you are not sure of this address,

discuss it with the customer (ipaddrshowcommand displays the switches IP addresses).

By default, the login username is admin, and the password is password. If these are incorrect, please

see the customer for the correct information. Upon login, you may be asked to change the default

passwords. If so, refer toUpgrade Tasks,Step5. ( ).

Example:# t el net {I P addr ess of swi t ch}Fabr i c OS ( name of swi t ch)Fabos Vers i on 6. 3. 0c

FC_Swi t ch l ogi n: admi nPassword:

Task 4: Record and verify configuration

9. ( ) Execute the ipaddrshowcommand and verify that you are connected to the switch that the

customer intends to be upgraded. Record the pertinent information in the table in Step13. ( ).

10. ( ) Execute the firmwareshow command to verify the version of Fabric OS currently running on the

switch.

Example:FC_Swi t ch: admi n> f i r mwar eshowSl ot Name Appl Pri mary/ Secondar y Versi ons St atus- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

4 FR4- 18i FOS v6. 3. 0cv6. 3. 0c

6 CP0 FOS v6. 3. 0c STANDBYv6. 3. 0c

7 CP1 FOS v6. 3. 0c ACTI VE *v6. 3. 0c

11. ( ) Execute the hashowcommand to verify the state of the CPs.Example:FC_Swi t ch: admi n> hashowLocal CP ( Sl ot 6, CP0) : Act i ve, Warm RecoveredRemote CP (Sl ot 7, CP1) : St andby, Heal t hyHA enabl ed, Hear t beat Up, HA St ate synchr oni zed

12. ( ) Execute the slotshowcommand to verify the state of all blades.

FC_Swi t ch: admi n> s l ot show

Sl ot Bl ade Type I D St atus- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1 SW BLADE 37 ENABLED2 UNKNOWN VACANT3 SW BLADE 55 ENABLED

4 AP BLADE 24 ENABLED5 CORE BLADE 52 ENABLED6 CP BLADE 50 ENABLED7 CP BLADE 50 ENABLED8 CORE BLADE 52 ENABLED9 UNKNOWN VACANT

10 SW BLADE 51 ENABLED11 UNKNOWN VACANT12 UNKNOWN VACANT


8/14


CAUTION: You should see that HA is enabled, the Heartbeat is up, the state is synchronized and

the CP Blades are ENABLED. If not, do not continue with the upgrade, and contact Customer

Service.

13. ( ) Record and verify the following configuration information before you begin the upgrade. You will

need to enter some or all of this information during the upgrade procedure. Use the ipaddrshow

command to note the logical (chassis) IP address. It is recommended that the logical (chassis) IP

address be used for the upgrade.

Hostname ____________________________________________________________________

FTP Server IP _________________________________________________________________

FTP username _________________________________________________________________

FTP password _________________________________________________________________

Switch username _______________________________________________________________

Switch password _______________________________________________________________

Logical Switch 0 / Chassis IP address ______________________________________________


9/14


Upgrade Tasks

Before you begin the upgrade procedure, make sure you have completed all of the tasks described under

Preparation Tasks.

Follow the next steps to back up the switch information and complete the upgrade of the switch firmware.

Task 1: Back up and save the current switch configuration

1. ( ) Execute the cfgsavecommand in order to ensure that the zoning information in the switchs flash

is preserved following the reboot.

Example:FC_Swi t ch: admi n> cf gsaveUpdat i ng Fl ash. . .

NOTE:If nothing has changed since the most recent cfgsave, you will receive the message: Nothing

changed: nothing to save, returning

2. ( ) Execute the configuploadcommandin order to get a good backup of the current configuration

file contained on the switch. EMC strong ly recommends

NOTE:When typing in the path for the commands, you must use the UNIX forward /even on

Windows machines.

that you make a backup of this file anytime

you have changed the configuration of the switch. This includes zoning changes. This file can be

downloaded to the switch if the configuration ever becomes corrupted or the switch itself is replaced.

Example:FC_Swi t ch: admi n> conf i gUpl oadProt ocol ( scp or f t p) [ f t p] : f tpServer Name or I P Addr ess [ host ] : {IP address of your host}User Name [ user] : {Your l ogi n I D on t he host }

Fi l e Name [ conf i g. t xt ] : {Pat h t o t he f i l e} i . e./ t emp/ brocade/ or i gconf i g. t xtPassword: {your password on the FTP server}

Upl oad compl et e

The /temp/brocadedirectory was created inPreparation Tasks, 2. ( ). The origconfig.txtfile will

get created automatically when the upload takes place. You can name the file anything you prefer.

Make note of where the backup was saved below.

Location of switch pre upgrade configuration backup: .


10/14


Task 2: Firmware upgrade and final steps

Upgrade firmware

The examples used below, includ ing the paths used in the command lines, are relative to

ftproot, and assume the ftp server was configu red to use C:\ as its ftproot . The path that you

specify is in relation to the folder that was created when you unzipped the file in Step4. ( ) of

the Preparation Tasks section. Refer to the documentation for your ftp server or the

instructions in the i ncluded 3CDaemon zip file for configuration instructions.

3. ( ) Execute the firmwareDownloadcommand to download the new firmware file onto the switch. If

this procedure is being done from a Windowsbased system, make sure an FTP service (i.e.

3CDaemon) has been started prior to starting the download procedure. Brackets below indicate

user supplied information. Do NOT include the in your commands.

NOTE: If the firmwaredownload takes more than 30 minutes to download firmware on a switch, or oneach CP in a director, the firmware download process times out. If a timeout occurs on a switch, thefirmware download process synchronizes the two partitions on the switch by starting a firmwarecommit operation. If a timeout occurs in a director, the firmware download process synchronizes thefirmware on the two partitions on the CP blades by starting a firmware commit operation on each CP.Wait at least 15 minutesfor the commit operation to complete then use the firmwareShow command to verify the partitions are synchronized. Only if the versions are synchronized can you thenreissue the firmwareDownload command to upgrade the system.

NOTE: Take note of some of the features pertaining to the intelligent blades. In particular, the fact

that FCIP traffic over the GbE ports will be disrupted during the code load to the blade. These areas

are highlighted in red .

Example:FC_Swi t ch: admi n> firmwaredownloadSer ver Name or I P Addr ess: User Name: Fi l e Name: t emp/ br ocade/ v6 4 0bNet wor k Pr ot ocol ( 1- aut o- sel ect , 2- FTP, 3- SCP) [ 1] :Password: *** **Checki ng systemsett i ngs f or f i r mwaredownl oad. . .

Ser ver I P: 10. 1. 1. 10, Pr ot ocol I Pv4Systemsett i ngs check passed.

The f ol l owi ng AP bl ades are i nst al l ed i n t he sys t em.

Sl ot Name Versi ons Traf f i c Di sr upt ed- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

4 FR4- 18i v6. 3. 0c Gi gE/ FC Fast - wr i t e

Thi s command wi l l upgrade t he f i r mware on both CPs and al l AP bl ade above.I f you want t o upgr ade f i r mware on a si ngl e CP onl y, pl ease use - s opt i on.

You may r un f i r mwar edownl oadst at us t o get t he st at us of t hi s


11/14


command.

Thi s command wi l l cause a war m/ non- di sr upt i ve boot on t he act i ve CP,but wi l l r equi r e t hat exi st i ng t el net , secur e t el net or SSH sessi ons be r est ar t ed.

Do you want t o cont i nue [ Y] : y

Fi r mware i s bei ng downl oaded to st andby CP. Thi s st ep may t ake up t o 30 mi nut es.Fi r mware i s bei ng downl oaded t o St andby CP. Pl ease wai t . . .Compl eted downl oad of xxx/ yyyy packages ( 100%) . Pl ease wai t . . .

Standby CP i s goi ng t o reboot wi t h new f i r mware.Standby CP boot ed successf ul l y wi t h new f i r mware.

Final changes, verif ication, and backup

4. ( ) Wait approximately 5 minutes after you see the above statement that the standby CP has booted

successfully and start another Telnet session to the switch as your first session to the switch will be

hung.

Example:# t el net {I P addr ess of swi t ch}Fabr i c OS ( name of swi t ch)

Fabos Vers i on 6. 4. 0bFC_Swi t ch l ogi n: admi nPassword:

Pl ease change your passwords now. Type t o abor t . )For user name - r ootNew passwor d:

5. ( ) You may be asked to change the passwords for the factory, root, admin and userIDs the first

time you login after the upgrade. This will happen for new switches or for switches that are being

upgraded and have not had the passwords changed before. The customer can use any password that

they want for the adminand userIDs as long as they are a minimum of 8 characters. The rootand

factorypasswords should not be changed from the defaults. If the customer looses or somehow

corrupts the admin or user passwords, EMC Global Services personnel need the ability to login as

rootto reset the passwords. Be sure to enter them exactly as shown on the next screen shot. Failureto do so will

Example:

affect Global Services ability to resolve any future problems.

l ogi n: adminPassword:

Pl ease change your passwords now. Type t o abort .For user name - r ootNew passwor d: Serv4EMCRe- ent er new password: Ser v4EMCFor username - f actoryNew passwor d: Fac t 4EMCRe- ent er new password: Fac t 4EMCFor user name - admi nNew passwor d: cust omer s choi ce {EMC def aul t i s pass wor d}Re- ent er new password:For username - userNew passwor d: cust omer s choi ce {EMC def aul t i s pass wor d}Re- ent er new password:Savi ng passwd. . . done.

6. ( ) Execute the firmwaredownloadstatus command to verify the state of the download operation.

Continue to issue this command until you see the output shown below, specifically message# 9 (for

the AP Blades)and#18 for the CPs. Note this can take over 30 minutes to complete.

FC_Swi t ch: admi n> f i r mwar edownl oadst at us

[ 1] : Mon Oct 9 15: 07: 28 2009


12/14


Sl ot 6 (CP0, act i ve) : Fi r mware i s bei ng downl oaded t o st andby CP. Thi s st ep mayt ake up t o 30 mi nut es.

[ 2] : Mon Oct 9 15: 14: 12 2009Sl ot 6 (CP0, act i ve) : Fi r mware has been downl oaded successf ul l y t o St andby CP.

[ 3] : Mon Oct 9 15: 14: 17 2009

Sl ot 6 (CP0, act i ve) : St andby CP i s goi ng to reboot wi t h new f i r mware.

[ 4] : Mon Oct 9 15: 17: 08 2009Sl ot 6 (CP0, act i ve) : St andby CP boot ed successf ul l y wi t h new f i r mware.

[ 5] : Mon Oct 9 15: 17: 17 2009Sl ot 4 (FR4- 18i ) : Fi r mware i s bei ng downl oaded t o t he bl ade. Thi s st ep may t ake upt o 10 mi nut es.

[ 6] : Mon Oct 9 15: 18: 04 2009Sl ot 7 (CP1, act i ve) : For ced f ai l over succeeded. New Act i ve CP i s r unni ng newf i r mware

[ 7] : Mon Oct 9 15: 19: 01 2009Sl ot 4 (FR4- 18i ) : Fi r mware has been downl oaded successf ul l y. Bl ade i s r eboot i ngwi t h t he new f i r mware.

[ 8] : Mon Oct 9 15: 21: 43 2009Sl ot 4 ( FR4- 18i ) : Fi r mware commi t has st ar t ed on t he bl ade. Thi s may t ake up t o 15mi nut es.

[ 9] : Mon Oct 9 15: 22: 32 2009Sl ot 4 (FR4- 18i ) : The commi t operat i on has compl eted successf ul l y.

[ 10] : Mon Oct 9 15: 23: 09 2009Sl ot 7 (CP1, act i ve) : Fi r mware i s bei ng downl oaded t o st andby CP. Thi s st ep mayt ake up t o 30 mi nut es.

[ 11] : Mon Oct 9 15: 27: 50 2009Sl ot 7 (CP1, act i ve) : Fi r mware has been downl oaded successf ul l y on St andby CP.

[ 12] : Mon Oct 9 15: 27: 55 2009Sl ot 7 ( CP1, act i ve) : St andby CP reboot s.

[ 13] : Mon Oct 9 15: 29: 25 2009Sl ot 7 (CP1, act i ve) : St andby CP boot ed successf ul l y wi t h new f i r mware.

[ 14] : Mon Oct 9 15: 29: 28 2009Sl ot 7 ( CP1, act i ve) : Fi r mware commi t operat i on has st art ed on both act i ve andst andby CPs.

[ 15] : Mon Oct 9 15: 29: 28 2009Sl ot 7 ( CP1, act i ve) : The f i r mware commi t operat i on has st art ed. Thi s may t ake upt o 10 mi nut es.

[ 16] : Mon Oct 9 15: 32: 19 2009Sl ot 7 (CP1, act i ve) : The commi t oper ati on has compl eted successf ul l y.

[ 17] : Mon Oct 9 15: 32: 19 2009Sl ot 7 ( CP1, act i ve) : Fi r mware commi t operat i on has compl eted successf ul l y on bothCPs.

[ 18] : Mon Oct 9 15: 32: 20 2009Sl ot 7 (CP1, act i ve) : Fi r mwaredownl oad command has compl eted successf ul l y. Usef i r mwareshow t o veri f y t he f i r mware ver si ons.

7. ( ) Execute the firmwareshow command to verify that the new version of Fabric OS is running on

the switch.

Note:This could take about 15 minutes to complete the write to all four partitions.

Example:


13/14


FC_Swi t ch: admi n> firmwareshowSl ot Name Appl Pri mary/ Secondar y Versi ons St atus- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

4 FR4- 18i FOS v6. 4. 0bv6. 4. 0b

6 CP0 FOS v6. 4. 0b STANDBYv6. 4. 0b

7 CP1 FOS v6. 4. 0b ACTI VE *v6. 4. 0b

8. ( ) Execute the hashowcommand again to verify the state of the CPs. You should see that HA is

enabled, the Heartbeat is up, the state is synchronized.

Example:FC_Swi t ch: admi n> hashowLocal CP ( Sl ot 6, CP0) : Act i ve, Warm RecoveredRemote CP (Sl ot 7, CP1) : St andby, Heal t hyHA enabl ed, Hear t beat Up, HA St ate synchr oni zed

9. ( ) Execute the slotshowcommand once again to verify the state of all blades.

FC_Swi t ch: admi n> s l ot show

Sl ot Bl ade Type I D St atus- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1 SW BLADE 37 ENABLED2 UNKNOWN VACANT3 SW BLADE 55 ENABLED4 AP BLADE 24 ENABLED5 CORE BLADE 52 ENABLED6 CP BLADE 50 ENABLED7 CP BLADE 50 ENABLED8 CORE BLADE 52 ENABLED9 UNKNOWN VACANT

10 SW BLADE 51 ENABLED11 UNKNOWN VACANT12 UNKNOWN VACANT

10. ( ) Execute the switchstatuspolicyshowcommand to verify that the policy settings on the switch

are correct. Your switch model determines what options are present in the output, such as number ofpower supplies, fans, etc. If you want to keep your current settings, skip to Step13. ( )

NOTE:This is an example of the settings, but based on the customer's specific switch configuration

and model,some items may change to more adequately reflect the hardware environment.

.If not,

continue with the next step.

Example:FC_Swi t ch: admi n> swi t chSt at usPol i cyShowThe cur r ent overal l swi t ch st at us pol i cy paramet er s:

Down Mar gi nal- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

PowerSuppl i es 2 1Temperat ures 2 1

Fans 2 1WWN 0 1CP 0 1 Down Er r or

Bl ade 0 1 Margi nal Warni ngFl ash 0 1

Margi nal Por t s 2 1Faul t yPort s 1 0Mi ssi ngSFPs 0 0

11. ( ) Execute the switchStatusPolicySetcommand to change the policy settings on the switch.

Example:FC_Swi t ch: admi n> swi t chSt at usPol i cySet


14/14


The cur r ent overal l swi t ch st at us pol i cy paramet er s:Down Mar gi nal

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -PowerSuppl i es 2 1Temperat ures 2 1

Fans 2 1WWN 0 1

CP 0 1Bl ade 0 1Fl ash 0 1

Margi nal Por t s 2 1Faul t yPort s 1 0Mi ssi ngSFPs 0 0

Note that t he val ue, 0, f or a parameter, means t hat i t i s NOT used i n t hecal cul at i on.** I n addi t i on, i f t he range of set t abl e val ues i n t he pr ompt i s ( 0. . 0) ,** t he pol i cy par ameter i s NOT appl i cabl e to the swi t ch.** Si mpl y hi t t he Return key.

The mi ni mum number ofBad PowerSuppl i es cont r i but i ng t o DOWN st atus: ( 0. . 4) [ 2]Bad PowerSuppl i es cont r i but i ng t o MARGI NAL st atus: ( 0. . 4) [ 1]Bad Temperat ur es cont r i but i ng to DOWN st atus: ( 0. . 10) [ 2]

Bad Temperat ur es cont r i but i ng t o MARGI NAL st atus: ( 0. . 10) [ 1]Bad Fans cont r i but i ng t o DOWN st atus: ( 0. . 3) [ 2]Bad Fans cont r i but i ng to MARGI NAL st atus: ( 0. . 3) [ 1]Down WWN contr i but i ng t o DOWN st at us: ( 0. . 2) [ 0]Down WWN cont r i but i ng t o MARGI NAL st atus: ( 0. . 2) [ 1]Down CP cont r i but i ng to DOWN st atus: ( 0. . 2) [ 0]Down CP cont r i but i ng t o MARGI NAL st atus: ( 0. . 2) [ 1]Down Bl ade cont r i but i ng to DOWN st atus: ( 0. . 4) [ 0]Down Bl ade cont r i but i ng t o MARGI NAL st atus: ( 0. . 4) [ 1]Out of r ange Fl ash cont r i but i ng t o DOWN st atus: ( 0. . 1) [ 0]Out of r ange Fl ash cont r i but i ng t o MARGI NAL st atus: ( 0. . 1) [ 1]Mar gi nal Por t s cont r i but i ng t o DOWN st atus: ( 0. . 64) [ 2]Mar gi nal Por t s cont r i but i ng t o MARGI NAL status: ( 0. . 64) [ 1]Faul t yPort s cont r i but i ng t o DOWN st at us: ( 0. . 64 [ 1]Faul t yPort s cont r i but i ng t o MARGI NAL stat us: ( 0. . 642) [ 0]Mi ssi ngSFPs cont r i but i ng to DOWN st at us: ( 0. . 64) [ 0]Mi ssi ngSFPs cont r i but i ng t o MARGI NAL st at us: ( 0. . 64) [ 0]

No Change

12. ( ) Execute the switchstatuspolicyshowcommand again (as shown in Step10. ( ))to verify that

the policy settings on the switch are now correct.

13. ( ) Execute the cfgsavecommand to ensure that the updated configuration is saved to flash, so it is

available after a switch reboot or total power failure.

Example:FC_Swi t ch: admi n> cfgsaveUpdat i ng f l ash . . .FC_Swi t ch: admi n>

14. ( ) Execute the configUpload command in order to get a good backup of the current configuration,

per Step2. ( ) . Be sure not to overwrite the previously saved configuration files by using differentfilenames.

Location of switch post upgrade configuration backup:

.

For more information on any of the commands used in this procedure, refer to Brocades Fabric OS

Administrators Guide, which contains detailed information on commands, and command syntax.

Documents

Director Models 640b Upgrade