Connectrix B-Series Procedure

Departmental Model Fabric OS 6.4.1a Upgrade

INFORMATION ABOUT THIS PROCEDURE:
This document steps you through the completion of a Connectrix management activity that can be
completed without the involvement of Remote Technical Support. If you have any concerns, questions, or
need assistance with an implementation, regarding your environment or this procedure, please contact
EMC Customer Support.
As part of the effort to continuously improve and enhance the performance and capabilities of the
Connectrix product line, EMC periodically releases new versions of its hardware and software, or qualifies
various systems interoperability with the Connectrix product family. Therefore, some functions described
in this procedure may not be supported by all revisions of the software or hardware you have currently in
use. For the most up-to-date information on specific requirements concerning your environment, refer to
the Fabric OS Release Notes for your version and the E-Lab Interoperability Navigator on PowerLink.
Site Ac tivity a nd Event Rec ord :
For your own change management practices, you may need to document this task activity. You may note
critical information in the log area below:
Ac tivity Event Tim e:
Date/Time:
Ta sk Ac tivity or Event:
Task being executed:
Performed by:
Switc h Inform a tion:
Switch Serial Number:
Switch Model:
Switch Name:
Switch IP:

Revision (1.0)

February 4, 2011
-1-

Contents
Introduction.................................................................................................................................................... 3
Known issues, Limitations and Restrictions .............................................................................................. 3
Assumptions .............................................................................................................................................. 4
Preparation Tasks ..................................................................................................................................... 6
Task 1: Reading and understanding the procedure before you begin ................................................ 6
Task 2: Obtaining software.................................................................................................................. 6
Task 3: Setting up the working environment ....................................................................................... 6
Verify Connectivity ......................................................................................................................................... 6
Open a HyperTerminal or Telnet session ..................................................................................................... 7
Task 4: Record and verify configuration .............................................................................................. 8
Upgrade Tasks .......................................................................................................................................... 9
Task 1: Back up and save the current switch configuration ................................................................ 9
Task 2: Firmware upgrade and final steps ........................................................................................ 10
Upgrade firmware ........................................................................................................................................ 10
Final changes, verification, and backup ...................................................................................................... 11

Revision (1.0)

February 4, 2011
-2-

Introduction
This procedure explains how upgrade a Department Model B-Series switch to Fabric OS version 6.4.1a
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 Guide or the EMC
Connectrix Manager Data Center Edition Users Guide for more information.
Topics for this upgrade include:
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 is only applicable to the following departmental class models:
DS-300B
DS-4100B
DS-4900B
DS-5000B
DS-5100B
DS-5300B
MP-7500B
AP-7600B
DS-5832B
MP-7800B
MP-8000B
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.
The MP- 8000B does not support non-disruptive hot code loads (HCL). Upgrading the MP-8000B from
FOS v6.3.2b or higher to FOS v6.4.1a or from FOS 6.4.1a to a later FOS version will be disruptive to
the IO through the switch.
If Bottleneck detection feature is currently enabled on the switch running FOS v6.3.x, you must disable
it before upgrading to FOS v6.4.1a; otherwise, frame drops may occur due to increased Hot Code Load
(HCL) time.
The MP-7800B platform must be power cycled after upgrading from FOS v6.3 to FOS v6.4.1a. This is
necessary to load the new FPGA image that enables IPv6 capability for FCIP links to MP-7800B. This
step is mandatory even if IPv6 will not be used on the FCIP ports. Not performing this step will result in
unpredictable behaviors on the FCIP links.

Revision (1.0)

February 4, 2011
-3-

Always refer to the current version of the Fabric OS Release Notes, the E-Lab Interoperability Navigator
on PowerLink , and EMCs Knowledgebase (Primus) for up to date information. Solution emc234016 is a
good starting place to find some important ETAs and known issues. Known issues, restrictions, and
limiations listed here are only for departmental 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.1a for Departmental Switches

Migrating from FOS v6.2.x
For switches currently running FOS 6.2.x it is recommended to use FOS v6.3.2b prior to migrating to FOS
v6.4.1a.

Migrating from FOS v6.3.x

For switches currently running FOS 6.3.x, there are no special steps required to migrate to FOS v6.4.1a.

Assumptions
This upgrade procedure assumes the following:
Before beginning the upgrade procedure, the switch must be IP accessable for establishing a Telnet
(or HyperTerminal session), and for the firmwaredownload to establish an FTP connection to the
FTP server.
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: The procedure takes approximately 20-25 minutes to complete. Please plan
accordingly.

Connectrix B Series departmental switches under Premium Support include installation of firmware
upgrades by EMC or our Partners. Customers with switches on Enhanced Support are required to
download and install their own firmware upgrades.

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
Customer Support before you begin the upgrade.

Revision (1.0)

February 4, 2011
-4-

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

Revision (1.0)

February 4, 2011
-5-

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
the documentation for your ftp server or the instructions in the included 3CDaemon zip file for
configuration instructions.

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:
Windows hosts: c:\temp\brocade
Unix host: /tmp/brocade

3. ( ) Download firmware file BRCDFOS6_4_1a.zip from the appropriate location. EMC personnel
download it from the Customer Service Web Site here while EMC Partners use the EMC Partners
site. Customers with Enhanced switch support download the firmware from Powerlink.
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.
4. ( ) Unzip the file BRCDFOS6_4_1a.zip that you downloaded in Step 3. ( ) to the directory you
created in Step 2. ( ). 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.
5. ( ) Unzip the file named v6.4.1a.zip that was just extracted to the directory you created in
2. ( ). Again, if using WinZip, ensure that Use folder names is checked.

Task 3:

Step

Setting up the working environment

Verify Connectivity
6. ( ) Open a command prompt on the host machine you will be using for the procedure and ping the IP
address of the switch to verify connectivity.
7. ( ) 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
Revision (1.0)

February 4, 2011
-6-

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 ifmodeshow command for the Ethernet interfaces (CP). Verify
that the connections from the CP 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 switchs
IP connections.
Example:
#switch:admin> ifmodeshow eth0
Link mode: negotiated 100baseTx-HD, link ok

{indicates 100Mbs connection at Half Duplex}

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

8. ( ) If your FTP server is on a different machine, open a command prompt on it and ping the 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 the BlackICE service (or reset the startup type) 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

9. ( ) Launch HyperTerminal or the Telnet application of your choice and establish a session to the IP
address of the switch being upgraded.
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 to Upgrade Tasks, 5. ( ).
Example:
# telnet {IP address of switch}
Fabric OS (name of switch)
Fabos Version 6.3.2b
FC_Switch login: admin
Password:

Revision (1.0)

February 4, 2011
-7-

Task 4:

Record and verify configuration

10. ( ) Execute the ipaddrshow command on the switch and verify that you are connected to the switch
the customer intends to be upgraded.

11. ( ) Execute the firmwareshow command to verify the version of Fabric OS currently running on the
switch.
Example:
FC_Switch:admin> firmwareshow
Appl
Primary/Secondary Versions
-----------------------------------------FOS
v6.3.2b
v6.3.2b

12. ( ) 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.
Hostname ____________________________________________________________________
FTP Server IP _________________________________________________________________
FTP username _________________________________________________________________
FTP password _________________________________________________________________
Switch IP address ______________________________________________________________
Switch username _______________________________________________________________
Switch password _______________________________________________________________

Revision (1.0)

February 4, 2011
-8-

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 cfgsave command in order to ensure that the zoning information in the switchs flash
is preserved following the reboot.
Example:
FC_Switch:admin> cfgsave
Updating Flash...

NOTE: If nothing has changed since the most recent cfgsave, you will receive the message: Nothing
changed: nothing to save, returning
2. ( ) Execute the configupload command in order to get a good backup of the current configuration
file contained on the switch. EMC strongly recommends that you make a backup 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.
NOTE: When typing in the path for the commands, you must use the UNIX forward / even on
Windows machines.
Example:
FC_Switch:admin> configUpload
Protocol (scp or ftp) [ftp]: ftp
Server Name or IP Address [host]: {IP address of your host}
User Name [user]: {Your login ID on the host}
File Name [config.txt]: {Path to the file} i.e./temp/brocade/origconfig.txt
Password: {your password on the FTP server}
upload complete

The /temp/brocade directory was created in Preparation Tasks, 2. ( ). The origconfig.txt file 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:

Revision (1.0)

February 4, 2011
-9-

Task 2:

Firmware upgrade and final steps

Upgrade firmware

The examples used below, 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. The path that you
specify is in relation to the folder that was created when you unzipped the file in Step 5. ( ) of
the Preparation Tasks section. Refer to the documentation for your ftp server or the
instructions in the included 3CDaemon zip file for configuration instructions.
3. ( ) Execute the firmwareDownload command to download the new firmware file onto the switch. If
this procedure is being done from a Windows based system, make sure an FTP service 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 the
firmware download process times out. If a timeout occurs on a switch, the firmware download
process synchronizes the two partitions on the switch by starting a firmware commit operation.
Wait at least 15 minutes for the commit operation to complete then use the firmwareShow
command to verify the partitions are synchronized. Only if the versions are synchronized can you
then reissue the firmwareDownload command to upgrade the system.

Example:
FC_Switch:admin> firmwaredownload
Server Name or IP Address: <host IP address>
User Name: <FTP Server User Name>
File Name: temp/brocade/v6.4.1a
Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]:
Password: *****
Checking system settings for firmwaredownload...
Server IP: 10.1.1.10, Protocol IPv4
System settings check passed.
You can run firmwaredownloadstatus to get the status of this command.
This command will cause a warm/non-disruptive boot on the switch,
but will require that existing telnet, secure telnet or SSH sessions
be restarted.
Do you want to continue [Y]: y
Firmware is being downloaded to the switch. This step may take up to 30 minutes.
Preparing for firmwaredownload...
Start to install packages...
dir
##################################################
ldconfig
##################################################
glibc
##################################################
~
awk
##################################################
Removing unneeded files, please wait ...
Finished removing unneeded files.
All packages have been downloaded successfully.
Firmware has been downloaded to the secondary partition of the switch.
HA Rebooting ...

Revision (1.0)

February 4, 2011
-10-

Final changes, verification, and backup

4. ( ) Wait approximately 5 minutes after you see the above statement about the HA Rebooting and
start another Telnet session to the switch you just rebooted (your original connection may have hung).
After logging in as admin you may see a message asking you to change the passwords.
Example:
# telnet {IP address of switch}
Fabric OS (name of switch)
Fabos Version 6.4.1a
FC_Switch login: admin
Password:
Please change your passwords now. Type <Ctrl-C> to abort.
For username - root
New password:

5. ( ) You may be asked to change the passwords for the factory, root, admin and user IDs 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 admin and user IDs as long as they are a minimum of 8 characters. The root and
factory passwords 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
root to reset the passwords. Be sure to enter them exactly as shown on the next screen shot. Failure
to do so will affect Global Services ability to resolve any future problems.
Example:
login: admin
Password:
Please change your passwords now. Type <Ctrl-C> to abort.
For username - root
New password: Serv4EMC
Re-enter new password: Serv4EMC
For username - factory
New password: Fact4EMC
Re-enter new password: Fact4EMC
For username - admin
New password: customers choice {EMC default is password}
Re-enter new password:
For username - user
New password: customers choice {EMC default is password}
Re-enter new password:
Saving passwd...done.

6. ( ) Execute the firmwareshow command to verify that the new version of Fabric OS is running on
the switch.
Example:
FC_Switch:admin> firmwareshow
Appl
Primary/Secondary Versions
-----------------------------------------FOS
v6.4.1a
v6.4.1a

Revision (1.0)

February 4, 2011
-11-

7. ( ) Execute the switchstatuspolicyshow command 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 of
power supplies, fans, etc. If you want to keep your current settings, skip to Step 10. ( ). If not,
continue with the next step.
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.
Example:
FC_Switch:admin> switchStatusPolicyShow
The current overall switch status policy parameters:
Down
Marginal
---------------------------------PowerSupplies 2
1
Temperatures 2
1
Fans 3
1
Down = Error
Flash 0
1
Marginal = Warning
MarginalPorts 2
1
FaultyPorts 1
0
MissingSFPs 0
0

8. ( ) Execute the switchStatusPolicySet command to change the policy settings on the switch.
Example:
FC_Switch:admin> switchStatusPolicySet
The current overall switch status policy parameters:
The current overall switch status policy parameters:
Down
Marginal
---------------------------------PowerSupplies 2
1
Temperatures 2
1
Fans 3
1
Flash 0
1
MarginalPorts 2
1
FaultyPorts 1
0
MissingSFPs 0
0
Note that the value, 0, for a parameter, means that it is NOT used in the
calculation.
** In addition, if the range of settable values in the prompt is (0..0),
** the policy parameter is NOT applicable to the switch.
** Simply hit the Return key.
The minimum number of
Bad PowerSupplies contributing to DOWN status: (0..2) [2]
Bad PowerSupplies contributing to MARGINAL status: (0..2) [1]
Bad Temperatures contributing to DOWN status: (0..3) [2]
Bad Temperatures contributing to MARGINAL status: (0..3) [1]
Bad Fans contributing to DOWN status: (0..4) [3]
Bad Fans contributing to MARGINAL status: (0..4) [1]
Out of range Flash contributing to DOWN status: (0..1) [0]
Out of range Flash contributing to MARGINAL status: (0..1) [1]
MarginalPorts contributing to DOWN status: (0..16) [2]
MarginalPorts contributing to MARGINAL status: (0..16) [1]
FaultyPorts contributing to DOWN status: (0..16) [1]
FaultyPorts contributing to MARGINAL status: (0..16) [0]
MissingSFPs contributing to DOWN status: (0..16) [0]
MissingSFPs contributing to MARGINAL status: (0..16) [0]
No Change

Revision (1.0)

February 4, 2011
-12-

9. ( ) Execute the switchstatuspolicyshow command again (as shown in Step 7. ( )) to verify that the
policy settings on the switch are now correct.
10. ( ) Execute the cfgsave command to ensure that the updated configuration is saved to flash, so it is
available after a switch reboot or total power failure.
Example:
FC_Switch:admin> cfgsave
Updating flash ...
FC_Switch:admin>

11. ( ) Execute the configUpload command in order to get a good backup of the current configuration,
per Step 2. ( ) . Be sure not to overwrite the previously saved configuration files by using different
filenames.

Location of switch post upgrade configuration backup:

For more information on any of the commands used in this procedure, refer to the Brocade Fabric OS
Adminstrators Guide, which contains detailed information on commands, and command syntax.

Revision (1.0)

February 4, 2011
-13-