Lab Guide CFA200 Rev0114 LG - L

CFA 200
Brocade Core Gen 5

SAN Administration
Lab Guide
Brocade University
Revision 0114
Corporate Headquarters - San Jose, CA USA
T: (408) 333-8000
info@brocade.com
European Headquarters - Geneva, Switzerland

T: +41 22 799 56 40
emea-info@brocade.com
Asia Pacific Headquarters - Singapore

T: +65-6538-4700
apac-info@brocade.com
2014 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, the Brocade B-weave logo, Fabric OS, File Lifecycle Manager, MyView, Secure Fabric OS, SilkWorm,
and StorageX are registered trademarks and the Brocade B-wing symbol and Tapestry are trademarks of
Brocade Communications Systems, Inc., in the United States and/or in other countries. FICON is a registered
trademark of IBM Corporation in the U.S. and other countries. All other brands, products, or service names are
or may be trademarks or service marks of, and are used to identify, products or services of their respective
owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or
implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade.
Brocade reserves the right to make changes to this document at any time, without notice, and assumes no
responsibility for its use. This informational document describes features that may not be currently available.
Contact a Brocade sales office for information on feature and product availability. Export of technical data
contained in this document may require an export license from the United States government.
Revision 0114
Contents
Remote Lab Access Instructions
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Record Remote Lab Access Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Login information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Connecting to the Brocade RSL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Module 2: Fibre Channel Theory

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Fibre Channel Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Classes of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Frame Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Node and Port World-Wide Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Port Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Well-Known Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
24-bit Device Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Module 4: Director FRU Identification

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
DCX Feature Hunt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
DCX Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
DCX non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
DCX-4S Feature Hunt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
DCX-4S Port Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
DCX-4S non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Director Feature Hunt Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
DCX Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
DCX non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
DCX-4S Port Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
DCX-4S non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Module 5: Installing and Configuring Switches

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Configure and Verify Basic Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Setting the Command Line Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configuring and Verifying Basic Settings on the B300. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Configuring and Verifying Basic Settings on the B5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
View Time for the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuring an NTP Server for the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Change the Time Zone for Each Switch in the Fabric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Setting a Message of the Day and a Login Banner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Verify Licensed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
View the Switch Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
CFA 200 Revision 0114 iii

View the Chassis Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Specify a Syslog Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Determining Switch Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Verifying Switch Uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Checking Switch Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Looking at Sensor Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Looking at Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Looking at the Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Examine Fabric Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Verify Device Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Verify that Devices have Successfully Logged into the Fabric. . . . . . . . . . . . . . . . . . . . . . . . . 47
Discovering the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuration Backup Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuration Save (Backup) and Restore Using Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . 54
Module 6: Firmware
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Upgrading Firmware from the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Upgrading Firmware Using Brocade Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Setting Up the Firmware Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Updating Switch Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Module 7: Zoning
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Lab Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Configuring Zoning in Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Setting the Default Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating and Activating a Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Verifying Device Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Using Network Advisor to verify Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Using HCM and Disk Management to Verify Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Module 8: Routing and Trunking

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Using the CLI to Evaluate Basic Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Evaluate the Current B6510 Routing over Trunks Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
iv Revision 0114 CFA 200

Module 9: Long Distance
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Student Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Module 10: Troubleshooting

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Capturing Technical Support Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Brocade Network Advisor Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Troubleshooting Switch Merge Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Downloading the B300 Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Downloading the B5100 Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Troubleshooting Switch Merge Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
CFA 200 Revision 0114 v

vi Revision 0114 CFA 200
Time Allocated: 10 Minutes
You will need to use these steps to access a remote workstation when doing lab exercises using the
Remote Solutions Lab (RSL). All lab exercises start at the remote workstation. All devices in the RSL
are pre-connected.
Objectives
In this lab exercise, you will perform tasks related to connecting and then disconnecting from the
Brocade Remote Solutions Lab. This lab is divided into the following sections:
Record remote lab access information
Connect to the Brocade RSL environment
Cleanly disconnect from the remote lab station
Revision 0114 CFA 200 1

Record Remote Lab Access Information

Login information
1. For the purpose of these labs, you will be allocated a remote environment. Please check with
your instructor for the RSL workstation that you are assigned:
2. You will be provided with a Student Information Sheet (SIS). The SIS includes the following
information:
- A diagram of your remote environment
- IP addresses for all switches and hosts in your environment
- User names and passwords for all switches and hosts
- FTP account and server information
3. Write your station name and password information on the SIS sheet provided by your instructor.
2 Revision 0114 CFA 200

Connecting to the Brocade RSL Environment

4. Using Internet Explorer, connect to the RSL website: rsl.brocade.com.
5. Depending on the version of your browser:
a. You may be prompted to accept a security certificate through a Security Alert dialog, click
Yes to accept the certificate from the RSL;
b. Otherwise you may see a page stating that there is a problem with this websites security certificate.
Choose Continue to this website (not recommended).
You will then be prompted by a Security Warning. Click the Yes button.
6. Log into the RSL using the Username and Password credentials provided by your instructor.
NOTE
If this is your first time connecting to the RSL, you will be prompted to download the Secure Application
Manager. The Secure Application Manager is used to control access to the RSL.
7. The Secure Application Manager used to control access to the RSL launches.

8. A link to your RSL station will be provided (shown below). Click the link to access your RSL
workstation.
9. The Remote Desktop Connection window will display, click Connect.
10. A web browser window to the Windows server in your RSL workstation opens. You may first be
prompted with a dialog (shown below) that warns you about displaying the web browser in full-
screen mode. Review the information then click OK.
NOTE
You can press Ctrl+Alt+Pause to toggle between a window view and a full-screen view.

11. Select the username assigned by the instructor.
12. Enter the password assigned by the instructor.
13. You have successfully connected to the Windows server in your RSL workstation. In your display,
you will see the tab controls shown below. Remember, typing CTRL-ALT-PAUSE will toggle
between full screen and windowed mode.
Important
Once you are connected please do not alter any of the partitions on the C drive.
If you are unable to sign on to your station, notify the instructor immediately.

Close Open Sessions and Exit Remote Connection

14. If you are not doing another lab at this time then please close all the GUI and CLI sessions that
you have open in your workstation.
15. From the remote desktop, select Start > Log off Administrator and click OK. Please do not
choose Shutdown.
16. Click on Sign Out in the upper right corner.
17. Close the browser.
This ends the Remote Lab Access Instructions lab exercise.

Time Allocated: 30 minutes
This lab will reinforce the Fibre Channel theory concepts that you learned in class.
Objectives
In this laboratory exercise, you will perform tasks related to the various elements of the Fibre Channel
protocol and theory:
List Fibre Channel Levels
Describe Classes of Service
Discuss Fibre Channel frame format
Differentiate between node and port world-wide names
Discovering fabrics using Brocade Network Advisor
List various port types
Differentiate between the well-known addresses
Decode 24-bit device addressing
Expected Start State

When accessing the environment for the first time your switches should be configured as follows:
B300
Fabric OS: 7.2.0b
Domain ID: 1
Switch/Chassis Name: RSL-STXX-B300
Ports Enabled: 0 1 14 15
Ports Disabled: none
Virtual Fabrics: Disabled
B5100
Fabric OS: 7.2.0b
Domain ID: 2

B6510
Fabric OS: 7.2.0b
Domain ID: 3
Ports Enabled: 0 8 9
Ports Disabled: 6 7 24 25
Fabric Wide
Default Zone: All access
Zoning: Cleared

Lab Environment

Fibre Channel Levels

1. Match the Fibre Channel level on the left with its description on the right.1
FC-4 A. Framing/Flow Control
FC-3 B. Physical Interface
FC-2 C. Upper Level Protocol Mapping
FC-1 D. Encode/Decode
FC-0 E. Common Services
Classes of Service
2. The column on the left is a description of the Brocade supported Classes of Service. The two
columns on the right are the types of Fibre Channel Classes of Service. Match the description with
its Class of Service.2
Switch-to-Switch communication A. Class-1 D. Class-4
Connectionless without ACK B. Class-2 E. Class-6
Connectionless with ACK C. Class-3 F. Class-F
Frame Format
3. Identify the fields within a Fibre Channel frame, the length (in bytes) of each and the maximum
frame size.3
Field Length
1. _____________________________________ ______
2. _____________________________________ ______
3. _____________________________________ ______ (maximum)
4. _____________________________________ ______
5. _____________________________________ ______
Maximum frame size: ______
1. FC-4=C; FC-3=E; FC-2=A; FC-1=D; FC-0=B

2. Switch-to-Switch communication =F, Connectionless without ACK=C, Connectionless with ACK=B
3. 1=SOF, 4 bytes; 2=Header, 24; 3=Payload, 2112; 4=CRC, 4; 5=EOF, 4; Max frame=2148 bytes

Node and Port World-Wide Names
4. Match the Brocade World Wide Name with a type below.4

10:00:00:05:1e:02:a5:49__________
20:07:00:05:1e:02:a5:49__________
4.Node WWN = 10:00:00:05:1e:02:a5:49, Port WWN (port 7) = 20:07:00:05:1e:02:a5:49

Port Types
5. Using the above diagram, identify the port types below (U_Port, F_Port, FL_Port, G_Port, E_Port).
The first one has been filled in for you:5
1. F_Port
2.
3.
4.
5.
6. Log into the B300 using the following credentials:

Username: admin
Password: password
7. Type the portshow 0 command to see the transitory port types that are used during port
initialization.
Note
The flags are shown in reverse order, with the most recent port state on the left.
DEV2-ST01-B300:admin> portshow 0
portIndex: 0
portName: port0
portHealth: HEALTHY
Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x20b03 PRESENT ACTIVE F_PORT G_PORT U_PORT
LOGICAL_ONLINE LOGIN NOELP ACCEPT FLOGI
LocalSwcFlags: 0x0
5.1=F_Port, 2=U_Port, 3=E_Port, 4=FL_Port, 5=F_Port

portType: 18.0
POD Port: Port is licensed
portState: 1 Online
Protocol: FC
portPhys: 6 In_Sync portScn: 32 F_Port
port generation number: 10
state transition count: 3
portId: 010000
portIfId: 43020017
portWwn: 20:00:00:05:1e:0a:83:6d
portWwn of device(s) connected:
10:00:00:05:1e:56:c8:2a
Distance: normal
portSpeed: N8Gbps
Credit Recovery: Inactive

Aoq: Inactive
FAA: Inactive
F_Trunk: Inactive
LE domain: 0
FC Fastwrite: OFF
Interrupts: 0 Link_failure: 0 Frjt: 0
Unknown: 0 Loss_of_sync: 0 Fbsy: 0
Lli: 34 Loss_of_sig: 2
Proc_rqrd: 183 Protocol_err: 0
Timed_out: 0 Invalid_word: 276
Rx_flushed: 0 Invalid_crc: 0
Tx_unavail: 0 Delim_err: 0
Free_buffer: 0 Address_err: 0
Overrun: 0 Lr_in: 5
Suspended: 0 Lr_out: 0
Parity_err: 0 Ols_in: 0
2_parity_err: 0 Ols_out: 5
CMI_bus_err: 0
Port part of other ADs: No
8. Log into the B5100 using the following credentials:

Username: admin
Password: password
9. Type the portshow 8 command and review the output.
portIndex: 8
portName: port8
portHealth: HEALTHY
portCFlags: 0x1

portFlags: 0x1000090b PRESENT ACTIVE E_PORT T_PORT T_MASTER G_PORT

U_PORT LOGICAL_ONLINE LOGIN
LocalSwcFlags: 0x0
portType: 17.0
portState: 1 Online
Protocol: FC
portPhys: 6 In_Sync portScn: 16 E_Port Trunk master
port Flow control mode 4
portId: 020800
portIfId: 43020000
portWwn: 20:08:00:05:1e:7f:06:9c
Distance: normal
portSpeed: N8Gbps
Credit Recovery: Inactive

LE domain: 0
FC Fastwrite: OFF
Overrun: 0 Lr_in: 5
CMI_bus_err: 0

Well-Known Addresses
10. Identify the above Well-Known Addresses below:6
FFFFFA
FFFFFB
FFFFFC
FFFFFD
FFFFFE
FFFFFF
24-bit Device Addressing

11. The switch is using standard 24-bit addressing. Translate the hexadecimal area to decimal:7
010400
171700
011A00
1F241F
113F00
12. From the B300, type the nsallshow command to display a list of every PID logged into the
fabric.
DEV2-ST01-B300:admin> nsallshow
{
010000 010100 030000
2 Nx_Ports in the Fabric }
DEV2-ST01-B300:admin>
____________________________________________________________________
____________________________________________________________________
13. From the B300 type the nsshow command. What type of information can you see?8
EV2-ST01-B300:admin> nsshow
{
Type Pid COS PortName NodeName
TTL(sec)
N 010000; 3;10:00:00:05:1e:56:c8:2a;20:00:00:05:1e:56:c8:2a;
na
FC4s: FCP
PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST01-HBA | Windows
Server (R) 2008 Standard | Service Pack 1"
Fabric Port Name: 20:00:00:05:1e:0a:83:6d
6.1=Management Server, 2=Time Server, 3=Name Server, 4=Fabric Controller, 5=Fabric Login, 6=Broadcast Server
7.1=port 4, 2=port 23, 3=port 26, 4=port 36, 5=port 63
8. Port type, PID, Class of Service, port name, node name, etc.

Permanent Port Name: 10:00:00:05:1e:56:c8:2a

Port Index: 0
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
N 010100; 3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00;
na
FC4s: FCP
PortSymb: [36] "Brocade University Virtual FC Target"
Permanent Port Name: 20:00:00:11:0d:0f:84:00
Port Index: 1
Share Area: No
Redirect: No
Partial: No
The Local Name Server has 2 entries }
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
- What is the main difference between the nsallshow and the nsshow commands?9
____________________________________________________________________
____________________________________________________________________
14. From the B5100, type the nscamshow command. List the field that appears after the Permanent
Port Name field.10
ST01-B5100:admin> nscamshow
nscam show for remote switches:
Switch entry for 1
state rev owner cap_available
known v700 0xfffc02 1
Device list: count 1
N 010100;
3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00;
FC4s: FCP
Port Index: 1
Share Area: No
Redirect: No
Partial: No
9.The nsshow command displays the local NS database. The nsallshow command displays the fabric addresses for
the fabric.
10.If nscamshow does not display output, refer to Appendix A.

Switch entry for 3

N 030000;
3;10:00:00:05:1e:56:c8:2b;20:00:00:05:1e:56:c8:2b;
FC4s: FCP
PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST01-HBA |
Windows Server (R) 2008 Standard | Service Pack 1"
Fabric Port Name: 20:00:00:05:33:93:69:40
Permanent Port Name: 10:00:00:05:1e:56:c8:2b
Port Index: 0
Share Area: No
Redirect: No
Partial: No
____________________________________________________________________
15. From the B5100, type the nscamshow -t command. List the field that appears after the
Permanent Port Name field.
ST01-B5100:admin> nscamshow -t
Switch entry for 1
N 010100;
3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00;
FC4s: FCP
Device type: Physical Target
Port Index: 1
Share Area: No
Redirect: No
Partial: No
Switch entry for 3

N 030000;
3;10:00:00:05:1e:56:c8:2b;20:00:00:05:1e:56:c8:2b;
FC4s: FCP

Fabric Port Name: 20:00:00:05:33:93:69:40

Device type: Physical Initiator
Port Index: 0
Share Area: No
Redirect: No
Partial: No
16. What is the main difference between the nscamshow and nscamshow -t commands?11
____________________________________________________________________
This ends Module 2: Fibre Channel Theory.
11.The nscamshow -t displays the device type.

In this lab you will label the major components of the DCX, DCX-4S, and 48000 chassis. A diagram is
provided for both the port side and non-port side of each chassis.
Objectives
In this laboratory exercise, you will perform tasks related to identifying the major components of the
Brocade directors:
Identify components of the DCX/DCX 8510-8 chassis
Identify components of the DCX-4S/DCX 8510-4 chassis
DCX Feature Hunt

Use the diagrams below to identify the components in a DCX chassis. Two diagrams are provided per
chassis type, one for the port side and one for the non-port side. Use the answer lines below each
diagram to write in the component names. Answers are found at the end of the module, you can also
find the answers in the DCX Hardware Reference Manual.

DCX Port Side
1.
2.
3.

DCX non-Port Side
1.
2.
3.

DCX-4S Feature Hunt

Use the diagrams below to identify the components in a DCX-4S chassis. Two diagrams are provided,
one for the port side and one for the non-port side. Use the answer lines below each diagram to write
in the component names. Answers are found at the end of the module, you can also find the answers
in the DCX-4S Hardware Reference Manual.
DCX-4S Port Side
1.
2.
3.

DCX-4S non-Port Side
1.
2.
3.

Director Feature Hunt Answers

Here are the answers to the above questions. Use this to check your work and make any necessary
corrections.
DCX Port Side

1. 48-port FC blade / slot 1
2. CR8 Core Routing blade
3. CP8 Control Processor blade
DCX non-Port Side

1. Power supply
2. WWN cards / logo plate
3. Blower assembly
DCX-4S Port Side

1. 48-port FC blade / slot 8
2. CR4S-8 Core Routing blade
3. CP8 Control Processor blade
DCX-4S non-Port Side

1. Power supply
2. WWN cards / logo plate
3. Blower assembly
This ends Module 4: Director FRU Identification.



Time Allocated: 60-90 Minutes
In this lab exercise, you will perform tasks related to installing and configuring Brocade fabrics. This
lab includes instructions on configuring and verifying basic parameters, basic security configuration,
determining switch status, and verifying device connections.
Objectives
In this laboratory exercise, the following tasks are performed to install and configure the Fibre Channel
switches:
Discover the fabric using Brocade Network Advisor
Use Telnet or SSH to access a switch
Verify and configure switch IP address and licenses
Configure login banners
Verify end device connections to the fabric

When accessing the switches, you should see the following:
B300
Fabric OS: 7.2.0b
Domain ID: 1
B5100
Fabric OS: 7.2.0b
Domain ID: 2

B6510
Fabric OS: 7.2.0b
Domain ID: 3
Fabric Wide
Zoning: Cleared

Lab Environment
Configure and Verify Basic Parameters

This activity focuses on the initial setup and configuration of a Brocade switch. This activity consists of
the following tasks:
Setting the command line session timeout
Configure and verify basic settings on the B300
Configure and verify basic settings on the B5100
View and set date and time parameters for the Fabric
Set login banner
Verify licensed features
View the switch name
Turn on enhanced change tracking
Specify a syslog server

Setting the Command Line Session Timeout

The timeout value for a command line session determines how long the session can be idle for before
it is automatically terminated by the switch. This can be set between 1 and 99,999 minutes, or 0 to
disable the timeout value. As you are going through these labs you may wish to change the timeout
value on the switch to prevent being disconnected.
1. From the desktop open the Putty application and select the B300, select Load, click Open.
2. Log in using the following credentials:
Username: admin
Password: password
3. Use the timeout command to determine the current value.
DEV2-ST01-B300:admin> timeout
Current IDLE Timeout is 5 minutes
4. Use the timeout command to set the timeout value to 0 minutes. This prevents your session
from closing when you are idle.
DEV2-ST01-B300:admin> timeout 0
IDLE Timeout Changed to 0 minutes
The modified IDLE Timeout will be in effect after NEXT login
DEV2-ST01-B300 login: admin

Password:
Place Security Banner Here
DEV2-ST01-B300:admin> timeout
Current IDLE Timeout is 0 minutes
5. The new timeout value does not get applied to the current session, you need to log in again using
the login command to have the new timeout value apply.

Configuring and Verifying Basic Settings on the B300

6. Display the current Ethernet settings using the ifmodeshow eth0 command. Record the
results here:
DEV2-ST01-B300:admin> ifmodeshow eth0
Link mode: negotiated 100baseTx-FD, link ok
MAC Address: 00:05:1E:0A:83:6D
Link mode: ____________________

7. Display the current IP address settings using the ipaddrshow command. Record the settings
here:
DEV2-ST01-B300:admin> ipaddrshow
SWITCH
Ethernet IP Address: 10.255.224.34
Ethernet Subnetmask: 255.255.255.192
Gateway IP Address: 10.255.224.62
DHCP: Off
Ethernet IP Address:____________________
Ethernet Subnetmask:____________________
Gateway IP Address:____________________
DHCP:____________________
8. Enter the switchshow command. You can use the pipe (|) operand to direct the output to the
more command, e.g. switchshow | more. Review the command output, and fill in the
following parameters:
DEV2-ST01-B300:admin> switchshow
switchName: DEV2-ST01-B300
switchType: 71.2
switchState: Online
switchMode: Native
switchRole: Principal
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:05:1e:0a:83:6d
zoning: OFF
switchBeacon: OFF
Index Port Address Media Speed State Proto

==============================================
0 0 010000 id N4 Online FC F-Port
10:00:00:05:1e:56:c8:2a
1 1 010100 id N8 Online FC F-Port
20:00:00:11:0d:0f:84:00
2 2 010200 -- N8 No_Module FC
3 3 010300 -- N8 No_Module FC
4 4 010400 -- N8 No_Module FC
5 5 010500 -- N8 No_Module FC

6 6 010600 -- N8 No_Module FC
7 7 010700 -- N8 No_Module FC
8 8 010800 -- N8 No_Module FC
9 9 010900 -- N8 No_Module FC
10 10 010a00 -- N8 No_Module FC
11 11 010b00 -- N8 No_Module FC
12 12 010c00 -- N8 No_Module FC
13 13 010d00 -- N8 No_Module FC
14 14 010e00 id N8 Online FC E-Port
10:00:00:05:1e:0b:63:0c "R15-ST02-B5100" (downstream)(Trunk master)
15 15 010f00 id N8 Online FC E-Port (Trunk port,
master is Port 14 )
16 16 011000 -- N8 No_Module FC
17 17 011100 -- N8 No_Module FC
18 18 011200 -- N8 No_Module FC
19 19 011300 -- N8 No_Module FC
20 20 011400 -- N8 No_Module FC
21 21 011500 -- N8 No_Module FC
22 22 011600 -- N8 No_Module FC
23 23 011700 -- N8 No_Module FC
switchName:____________________
switchType:____________________1
switchRole:____________________2
switchDomain:__________________3
zoning: ____________________4
9. Enter the version command; what is the FOS version running on the switch?
DEV2-ST01-B300:admin> version
Kernel: 2.6.14.2
Fabric OS: v7.2.0b
Made on: Sat Oct 19 00:15:12 2013
Flash: Mon Nov 25 06:55:26 2013
BootProm: 1.0.11
Fabric OS: __________________5
1. Switch type for B300 is 71.x

2. Principal or Subordinate
3. 1
4. Zoning should be OFF
5. Fabric OS v7.2.0b or later

10. Enter the fabricshow command; how many domains are in the fabric?6
____________________________________________________________________
DEV2-ST01-B300:admin> fabricshow
Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
-------------------------------------------------------------------------
1: fffc01 10:00:00:05:1e:0a:83:6d 10.255.224.34 0.0.0.0 >"ST01-B300"
2: fffc02 10:00:00:05:1e:7f:06:9c 10.255.224.35 0.0.0.0 "ST01-B5100"
3: fffc03 10:00:00:05:33:93:69:3f 10.255.224.36 0.0.0.0 "ST01-B6510"
The Fabric has 3 switches
Configuring and Verifying Basic Settings on the B5100

11. From the desktop open the Putty application and select the B5100, select Load, click Open.
12. Log in using the following credentials:
Username: admin
Password: password
13. From the Telnet session of your B5100, display the current IP address settings using the
ipaddrshow command. Record the settings here:
DEV2-ST01-B5100:admin> ipaddrshow
SWITCH
Ethernet IP Address: 10.255.224.35
Ethernet Subnetmask: 255.255.255.192
Gateway IP Address: 10.255.224.62
DHCP: Off
Ethernet IP Address:____________________
Ethernet Subnetmask:____________________
Gateway IP Address:____________________
DHCP: ____________________
6. 3 (B300, B5100, and B6510)

14. Enter the switchshow command. Review the command output, and fill in the following
parameters:
DEV2-ST01-B5100:admin> switchshow
switchName: ST01-B5100
switchType: 66.1
switchState: Online
switchMode: Native
switchRole: Subordinate
switchDomain: 2
switchId: fffc02
switchWwn: 10:00:00:05:1e:7f:06:9c
zoning: ON (ConfigA)
switchBeacon: OFF
FC Router: OFF
FC Router BB Fabric ID: 1
Address Mode: 0

==================================================
0 0 020000 -- N8 No_Module FC
1 1 020100 -- N8 No_Module FC
2 2 020200 -- N8 No_Module FC
3 3 020300 -- N8 No_Module FC
4 4 020400 -- N8 No_Module FC
5 5 020500 -- N8 No_Module FC
6 6 020600 -- N8 No_Module FC
7 7 020700 -- N8 No_Module FC
8 8 020800 id N8 Online FC E-Port
10:00:00:05:33:93:69:3f "ST01-B6510" (downstream)(Trunk master)
9 9 020900 id N8 Online FC E-Port (Trunk port,
master is Port 8 )
10 10 020a00 -- N8 No_Module FC
11 11 020b00 -- N8 No_Module FC
12 12 020c00 -- N8 No_Module FC
13 13 020d00 -- N8 No_Module FC
14 14 020e00 id N8 Online FC E-Port (Trunk port,
master is Port 15 )
15 15 020f00 id N8 Online FC E-Port
10:00:00:05:1e:0a:83:6d "ST01-B300" (upstream)(Trunk master)
16 16 021000 -- N8 No_Module FC
17 17 021100 -- N8 No_Module FC
18 18 021200 -- N8 No_Module FC
19 19 021300 -- N8 No_Module FC
20 20 021400 -- N8 No_Module FC
21 21 021500 -- N8 No_Module FC
22 22 021600 -- N8 No_Module FC
23 23 021700 -- N8 No_Module FC
24 24 021800 -- N8 No_Module FC
25 25 021900 -- N8 No_Module FC
26 26 021a00 -- N8 No_Module FC
27 27 021b00 -- N8 No_Module FC

28 28 021c00 -- N8 No_Module FC
29 29 021d00 -- N8 No_Module FC
30 30 021e00 -- N8 No_Module FC
31 31 021f00 -- N8 No_Module FC
32 32 022000 -- N8 No_Module FC
33 33 022100 -- N8 No_Module FC
34 34 022200 -- N8 No_Module FC
35 35 022300 -- N8 No_Module FC
36 36 022400 -- N8 No_Module FC
37 37 022500 -- N8 No_Module FC
38 38 022600 -- N8 No_Module FC
39 39 022700 -- N8 No_Module FC
switchName:____________________
switchType:____________________7
switchRole:____________________8
switchDomain:____________________9
zoning: ____________________10
15. Entering the version command. What version is currently installed on your B5100?
Fabric OS: ____________________11
View Time for the Fabric

16. Continuing on the Telnet session of the B5100 switch, enter the date command to view the
current date and time.
17. Enter tsclockserver to determine the current source of date and time synchronization.12
DEV2-ST01-B5100:admin> tsclockserver
Active NTP Server 10.255.252.50
Configured NTP Server List 10.255.252.50
18. Record the current clock server setting on the B5100:
tsclockserver: ____________________
19. On the B300, change the tsclockserver setting to LOCL, if it is not already, by running the
tsclockserver LOCL command.
7. Switch type of B5100 is 66.x

8. Principal or Subordinate
9. 2
10. Zoning should be OFF
11. v7.2.0b or later
12. If the clock server is specified as LOCL then the date and time that has been manually set on the fabric Principal
is used fabric wide. If an NTP server has been specified, the IP address of that server is displayed.

Configuring an NTP Server for the Fabric

20. From the B300, run the date 0227123003 command to change the date and time.
a. Issue the date command from both the B300 and the B5100.
b. Verify the B300 has the date of Thu Feb 27 12:30 Localtime 2003.
21. Set the fabric to synchronize to an external NTP server using the tsclockserver command on
the B300. Although the command may be run on any switch in a fabric, enter this command on the
B300 only.
DEV2-ST01-B300:admin> tsclockserver 10.255.252.11
Updating Clock Server configuration...done.
Updated with the NTP servers
22. Record the new clock server and date settings on the B300:
DEV2-ST01-B300:admin> date
Tue Apr 10 11:15:37 Localtime 2012
tsclockserver: ____________________
date: ____________________
23. Record the new clock server and date settings on the B5100:
DEV2-ST01-B5100:admin> date
Tue Apr 10 11:14:34 Localtime 2012
tsclockserver: ____________________
date: ____________________
24. Verify that the time is in sync (both dates should match). It may take up to two minutes for the time
to synchronize.
Change the Time Zone for Each Switch in the Fabric

Switches participating in a fabric may be in different time zones. For logging and reporting, it may be
advantageous to leave all switches in the default UTC time zone, however it is possible to have
switches report events in their local time with the tstimezone command.
For example, the Eastern time zone in the United States is offset from GMT by -5 hours, so the
tstimezone -5 command would correctly set the time zone for a switch in the Eastern United
States. You can also run the tstimezone --interactive command to choose the correct time
zone from a menu.
25. Use the tstimezone command to set the time zone of your B300 to the Eastern time zone in
the United States (GMT -5) and verify same.
DEV2-ST01-B300:admin> tstimezone -5
System Time Zone change will take effect at next reboot.
DEV2-ST01-B300:admin> tstimezone
Time Zone Hour Offset: -5
Time Zone Minute Offset: 0

Note
If the tstimezone command does not work, use the tstimezone --old 0 command
and then use the tstimezone -5 command. This may require a reboot.
26. Type the date command on each switch to verify that the date on the B300 is 5 hours earlier
than the date on B5100. If the dates do not differ by 2 hours then type fastboot on the B300,
log in and check the dates again.
27. From the B300, type the following command to restore the configuration back to default:
DEV2-ST01-B300:admin> tstimezone -7
System Time Zone change will take effect at next reboot.
Setting a Message of the Day and a Login Banner

A Message Of The Day (MOTD) and login banner may be displayed at each login. If an MOTD is set, it is
displayed at initial command line access login and a Web Tools session. Once you have logged in, the
login banner is displayed.
28. Continuing with the Telnet session of your B300 and enter the following:
DEV2-ST01-B300:admin> motd --set "Unauthorized access is prohibited.
Unauthorized users must log off."
29. Type the following:
DEV2-ST01-B300:admin> bannerset You have successfully logged into
the switch.
30. Type login to terminate your current session. Once you log in to the switch the new MOTD and
login banner are displayed.
31. To turn off MOTD, type motd --set "" at the command prompt.
32. To turn off the login banner, type bannerset "" at the command prompt.

Verify Licensed Features

In addition to basic switch functionality, each switch may have optional licensed features enabled.
33. Return to the Telnet session of your B5100 and type licenseidshow. Switch license keys are
generated for a specific switch WWN.
DEV2-ST01-B5100:admin> licenseidshow
10:00:00:05:1e:7f:06:9c
34. To view the licensed features on this switch, enter the licenseshow command.
DEV2-ST01-B5100:admin> licenseshow
RzdebzybyQS0efcb:
Fabric license
ezbeeQecRf0gffI:
Second Ports on Demand license - additional 8 port upgrade
license
AQDAMQ4gRQLESTHrMLP7CRZFgEmtYNYFBJfPB:
8 Gig FC license
mB9TtSgRN7HTY77L7N4MW4B74mfWGQZJB7fAB:
Extended Fabric license
Fabric Watch (Fabric Vision capable) license
Performance Monitor (Fabric Vision capable) license
Trunking license
FICON_CUP license
First Ports on Demand license - additional 8 port upgrade license
Integrated Routing license
Adaptive Networking - obsolete license
DataFort Compatibility license
R3Mf9HaHfX4f9CWtAgm3ZRTWT7X7BfHfB79PJ:
Enhanced Group Management license
LZWKR7DmFZ4GNB3TSmJLgAAmWKSDgTgLBASaR:
Server Application Optimization - obsolete license
Note
Notice that one or more features may be activated with a single license key.

View the Switch Name

Verify that each switch has a unique and meaningful name that matches the lab topology diagrams.
Having a switch naming convention is helpful during administration and troubleshooting.
35. Return to the Telnet session of your B300 and issue the switchname command. Verify that the
switch name matches the topology diagram associated with your station.
DEV2-ST01-B300:admin> switchname
DEV2-ST01-B300
a. Record the switch name here.
____________________________________________________________________
36. Return to the Telnet session of your B5100 and use the switchname command. Verify that the
switch name matches the topology diagram associated with your station.
a. Record the switch name here.
____________________________________________________________________
View the Chassis Name

The chassis name is similar to the switch name and is used by Fabric OS to uniquely identify the
chassis when outputting certain commands. In particular, the supportsave command uses the
chassis name when naming files, because of this it is important that your switches have unique
chassis names as well. In most cases the chassis name can be set to the switch name.
37. Return to the Telnet session and use the chassisname command on both switches (B300 and
B5100) to verify the current chassis name is correct.
DEV2-ST01-B300:admin> chassisname
DEV2-ST01-B300
DEV2-ST01-B5100
NOTE
The default chassis names for Brocade switches is the word Brocade followed by the model number.
For example a B300 would have Brocade300 as the chassis name, a B5100 would be
Brocade5100.
38. If you want to change the chassisname, use the following steps to rename:
a. Use the chassisname command on the B300 switch and replace the name as follows:
DEV2-ST01-B300:admin> chassisname R01-ST02-B300
b. Use the chassisname command on the B5100 switch and replace the name as follows:
DEV2-ST01-B5100:admin> chassisname R01-ST02-B5100
c. Use the chassisname command on both switches to verify the new chassis name.
R01-ST02-B300
R01-ST02-B5100

Specify a Syslog Server

Error and change tracking logs are stored in switch memory; older entries in this log will be flushed out
to make room for newer log entries. A syslog server may be used to persistently store log files, and has
the added benefit of centralizing switch logs from all switches.
39. Ensure that the Brocade Network Advisor services have been stopped:
a. On the desktop click Start > Programs > Network Advisor 12.1.3 > Server Management
Console.
b. On the Services tab click the Stop button
c. At the Confirmation window click Yes and wait for the Network Advisor services to shut down.
d. When the Network Advisor services are stopped close the window and return to the desktop.
40. Follow these steps to start the syslog server (we are using Kiwi Syslog Daemon):
a. On the desktop launch the Kiwi Syslog Daemon program.
41. Setup a log file to capture events:
a. Click File > Setup
b. In the navigation pane on the left expand Rules > Default > Actions and click Log to file.
c. In the Path and file name of log file field enter c:\captures\cfa200_logs.txt.
d. In the navigation pane on the left click Inputs > UDP
e. Ensure the Listen for UDP Syslog messages box is checked
f. Ensure the UDP Port field is set to 514.
g. Click OK.
42. Determine the IP address of your RSL host server by referencing your Student Information Sheet.
Note
You can forward syslogd messages to up to six servers.
43. Return to the Telnet session of your B5100 and issue the syslogdipadd <IP address>
command.
44. Generate switch log messages on the B5100. Type login to terminate your current session and
log in as admin. An entry should appear in the syslog server list.
45. Examine the entries in the Kiwi syslog daemon window.

46. Check to see if the messages were recorded in the syslog file; to do this do the following:
a. Click Start > Run
b. Type c:\captures and press ENTER.
c. Open the cfa200_logs.txt file and verify the syslog entries are there.
NOTE
If the messages did not get recorded in the syslog file or the Kiwi syslog daemon window check the fol-
lowing:
On the switch run command: syslogdipshow and verify the IP address is set correctly.
Verify that the Network Advisor services are not running.
47. When you are finished close the Kiwi Syslog server.
Check Point: You have configured and verified basic settings on the switches in your fabric. Some of
these steps are not required for essential switch operation; however these basic steps will make SAN
administration easier and more consistent as your fabric grows.
Determining Switch Status

It is important to have the ability to quickly determine the overall status of the switch, and the status
of particular components.
This section of the lab has the following parts:
Verifying switch uptime
Looking at sensor readings
Looking at port status
Looking at port configuration
Verifying fabric parameters
Verifying Switch Uptime

Display the amount of time the switch has been operational.
48. Return to the Telnet session of your B5100 and issue the switchuptime command.
DEV2-ST01-B5100:admin> switchuptime
6:46am: up for 5 days 20 hrs 13 mins
49. Record the amount of time the switch has been operational. ____________________
50. Issue the uptime command. Notice that the uptime reported by both commands is the same.
DEV2-ST01-B5100:admin> uptime
06:46:36 up 5 days, 20:14, 1 user, load average: 0.02, 0.03, 0.00

Looking at Sensor Readings

You can display the current operational status of all switch sensors.
51. From the Telnet session of your B300, issue the sensorshow command.
DEV2-ST01-B300:admin> sensorshow
sensor 1: (Temperature) is Ok, value is 28 C
sensor 4: (Fan ) is Ok,speed is 6250 RPM
sensor 7: (Power Supply) is Ok
52. Verify that the sensors all display an OK status.
Alternatively, the tempshow, fanshow, and psshow commands will display the status of individual
components. The output of these commands is shown below:
DEV2-ST01-B300:admin> tempshow
Sensor State Centigrade Fahrenheit
ID
=================================================
1 Ok 28 82
2 Ok 27 80
3 Ok 28 82
DEV2-ST01-B300:admin> fanshow
Fan 1 is Ok, speed is 6250 RPM
DEV2-ST01-B300:admin> psshow
Power Supply #1 is OK

Looking at Port Status

We will now observe the status of ports on the switch.
53. From the Telnet session of your B300, issue the portshow 1 command.
portIndex: 1
portName: port1
portHealth: HEALTHY
portCFlags: 0x1
portFlags: 0x24b03 PRESENT ACTIVE F_PORT G_PORT U_PORT
LOGICAL_ONLINE LOGIN NOELP LED ACCEPT FLOGI
LocalSwcFlags: 0x0
portType: 18.0
portState: 1 Online
Protocol: FC
portPhys: 6 In_Sync portScn: 32 F_Port
portId: 010100
portIfId: 43020015
portWwn: 20:01:00:05:1e:0a:83:6d
20:00:00:11:0d:0f:84:00
Distance: normal
portSpeed: N8Gbps
LE domain: 0
FC Fastwrite: OFF
Overrun: 0 Lr_in: 15
CMI_bus_err: 0

54. Review the output and record the following parameters13:

a. portHealth ____________________
b. portState ____________________
c. Distance ____________________
d. portSpeed ____________________
e. Link_failure____________________
f. Loss_of_sync ____________________
g. Loss_of_sig ____________________
NOTE
It is not unusual to observe Link_failure, Loss_of_sync and related errors. These errors are commonly
generated as devices are plugged into switch ports. However, you may have a marginal link if you
notice that these errors are increasing over time on a port in a stable fabric.
Looking at the Port Configuration

We will now observe the current port configuration.
55. From the Telnet session of your B300, issue the portcfgshow |more command.
56. Review the output. All ports should be enabled and, since the Trunking license is installed,
trunking also should be enabled by default on all ports.
DEV2-ST01-B300:admin> portcfgshow |more
Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+--
<truncated output>
Trunk Port ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON
<truncated output>
Persistent Disable.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
<truncated output>
Examine Fabric Parameters

Fabric parameters must be consistent within a fabric. If fabric parameters (fabric.ops) are not
consistent, a fabric merge will fail until the parameters are set to common values.
57. From the Telnet session of your B300, issue the configshow -pattern fabric.ops
command and look at the fabric.ops parameters.
DEV2-ST01-B300:admin> configshow -pattern fabric.ops
fabric.ops.BBCredit:16
fabric.ops.E_D_TOV:2000
fabric.ops.R_A_TOV:10000
fabric.ops.bladeFault_on_hwErrlevel:0
fabric.ops.dataFieldSize:2112
13. B300 portshow outputs should display as follows portHealth: HEALTHY; portState: Online;
Distance: normal; portSpeed: N8Gbps; the other parameters will vary.

fabric.ops.max_hops:7
fabric.ops.mode.fcpProbeDisable:0
fabric.ops.mode.isolate:0
fabric.ops.mode.longDistance:0
fabric.ops.mode.noClassF:0
fabric.ops.mode.pidFormat:1
fabric.ops.mode.tachyonCompat:0
fabric.ops.mode.unicastOnly:0
fabric.ops.mode.useCsCtl:0
fabric.ops.vc.class.2:2
fabric.ops.vc.config:0xc0
fabric.ops.vc.linkCtrl:0
fabric.ops.vc.multicast:7
fabric.ops.wan_tov:0
58. Return to the Telnet session of your B5100 and issue the same command:
DEV2-ST01-B5100:admin> configshow -pattern fabric.ops
fabric.ops.BBCredit:16
fabric.ops.E_D_TOV:2000
fabric.ops.R_A_TOV:10000
fabric.ops.bladeFault_on_hwErrlevel:0
fabric.ops.dataFieldSize:2112
fabric.ops.max_hops:7
fabric.ops.mode.fcpProbeDisable:0
fabric.ops.mode.isolate:0
fabric.ops.mode.longDistance:0
fabric.ops.mode.noClassF:0
fabric.ops.mode.pidFormat:1
fabric.ops.mode.tachyonCompat:0
fabric.ops.mode.unicastOnly:0
fabric.ops.mode.useCsCtl:0
fabric.ops.vc.config:0xc0
fabric.ops.vc.linkCtrl:0
fabric.ops.vc.multicast:7
fabric.ops.wan_tov:0
59. Compare the fabric.ops parameters on both switches. Do any of the parameters differ?
______________________________________________________________________14
Check Point: You have learned to quickly assess general switch status. Fabric troubleshooting builds on
these introductory steps.
14.The switches should be successfully merged into a single fabric so the fabric.ops parameters should be the
same.

Verify Device Connection

This section of the lab will have you verify that a host, storage, or tape device has successfully logged
into the fabric.
Verify that Devices have Successfully Logged into the Fabric

As new devices are added to a fabric configuration, it is important to have the ability to gather basic
information and status regarding the newly-added devices.
60. Return to the open Telnet session of your B300 and issue the nsshow t -r command.
61. Verify that the host bus adapter is properly registered with the name server and fabric controller.
Record the last three octets of the port WWN of the devices. Example: 50:4c:7d.
Note
The number of devices on your SAN may vary depending on the RSL environment. At a mini-
mum you should have at least one host and one storage device.
ST01-B300:admin> nsshow -t -r
{
SCR
N 010000; 3;10:00:00:05:1e:56:c8:2a;20:00:00:05:1e:56:c8:2a;
0x01000003
FC4s: FCP
PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST01-HBA | Windows
Server (R) 2008 Standard | Service Pack 1"
Device type: Physical Initiator
Port Index: 0
Share Area: No
Redirect: No
Partial: No
N 010100; 3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00;
0x01000003
FC4s: FCP
Device type: Physical Target
Port Index: 1
Share Area: No
Redirect: No
Partial: No
The Local Name Server has 2 entries }
WWPN ____________ Device Type _____________________ State Change Registration (Y/N) ___

WWPN ____________ Device Type _____________________ State Change Registration (Y/N) ___
62. From open B5100 Telnet session issue the nscamshow command to see detailed information
about the devices on your B300 switch.
ST01-B5100:admin> nscamshow
Switch entry for 1
N 010000;
3;10:00:00:05:1e:56:c8:2a;20:00:00:05:1e:56:c8:2a;
FC4s: FCP
Port Index: 0
Share Area: No
Redirect: No
Partial: No
N 010100;
3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00;
FC4s: FCP
Port Index: 1
Share Area: No
Redirect: No
Partial: No
Switch entry for 3

N 030000;
3;10:00:00:05:1e:56:c8:2b;20:00:00:05:1e:56:c8:2b;
FC4s: FCP
Fabric Port Name: 20:00:00:05:33:93:69:40
Port Index: 0
Share Area: No
Redirect: No
Partial: No

63. Compare the last three octets of the Port WWN of two device outputs gathered from the B5100
nscamshow output with the B300 nsshow output values gathered earlier. Are they the same?15
____________________________________________________________________
Check Point: You have learned how to determine if a SAN attached device, such as host, storage, or
tape device, has successfully logged into the fabric.
Discovering the Fabric

64. Ensure that the Brocade Network Advisor services are running:
NOTE
You will need to make sure that the Kiwi syslog server is completely shut down before enabling the
Network Advisor services.
a. On the desktop click Start > Programs > Network Advisor 12.1.3 > Server Management
Console.
65. On the Services tab click the Start button
66. From the desktop open Brocade Network Advisor 12.1.3 application by double-clicking on the icon
67. Log in using the default credentials:
- Username: administrator
- Password: password
68. Select the SAN tab.
69. Click Discover > Fabrics
15.The nscamshow output does not have an SCR column, otherwise they are the same.

70. Click Add.
71. In the Fabric Name field, enter Fabric XX, where XX is your workstation.
The Fabric Name is used in to differentiate fabrics in Network Advisor. Each fabric you discover
should have a different fabric name.

72. Using the Student Information Sheet (SIS), enter the IP address for the B5100 in the IP Address
field.
NOTE
If default credentials are used you do not need to enter anything in the User ID or Password fields.

73. Click OK. This launches the discovery Add Operation.
NOTE
You only have to discover one switch in the fabric. This switch is used as a seed switch to find all the
other switches in the same fabric.
You can use the switchshow command to display the Node WWN of a switch and the portshow
command to display Port WWN of any ports.
74. Return to the Telnet session of your B300.
75. Issue the switchshow command, what is the switchWwn?16
ST01-B300:admin> switchshow
switchType: 71.2
switchState: Online
switchMode: Native
switchRole: Principal
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:05:1e:0a:83:6d
zoning: OFF
switchBeacon: OFF.......
____________________________________________________________________
16.The switch WWN is different for each switch, but it should start with 10:00:00:05:1e:xx:xx:xx

Helpful Hint
Using the switchshow | more command can be used to page through the output. Below
are some more helpful hints:
space - advance one page
enter - advance one line
b go back one page
/ search forward
? search backwards
76. Issue the command portshow 1, what is the portWwn and portWwn of device(s)
connected?17
____________________________________________________________________
<truncated output>
portId: 010100
portIfId: 43020015
portWwn: 20:01:00:05:1e:0a:83:6d
20:00:00:11:0d:0f:84:00
<truncated output>
Configuration Backup Using the CLI

77. On the B5100, type the configupload command. Use FTP and the file name should be the
name of the switch:
R14-ST08-B5100:admin> configupload
Protocol (scp, ftp, sftp, local) [ftp]: ftp
Server Name or IP Address [host]: 10.255.252.50
User Name [user]: cfa
Path/Filename [<home dir>/config.txt]: R13STxxB5100.txt
Section (all|chassis|switch [all]): all
Password: cfa
configUpload complete: All selected config parameters are uploaded
Note
The configupload command was performed using the -all option specified in the inter-
action Section.
17.This information is different for each switch and device connection.

Configuration Save (Backup) and Restore Using Network Advisor

78. From Brocade Network Advisor application select the SAN tab.
79. Select the B5100 in the Switch Group.
80. Right-click, select Configuration > Save Now.
This opens the Save Switch Configurations dialog window.
Note
You can Save the configuration file over again and Network Advisor will keep it. Previously
saved configuration files are not overwritten because the date stamp on the configuration
file includes hh:mm:ss.
If you do perform multiple configuration Saves, you will have more than one file as an option
to restore when you perform a restore later in this exercise.
81. Verify that the B5100 is in the Selected Swtiches list on the right side.
82. Click OK, this initiates the save configuration process.
83. On the Network Advisor Message, click OK

84. In the Switch Group, select the B5100 .
85. Right-click on the B5100, select Configuration > Configuration Repository.

86. In the Switch Configurations Repository, select the backup file by clicking on the line, but do not
click on the Keep check box.
Note
Do not select the check box as that is to keep the selected file and delete what has been
highlighted. Checking Keep and then performing the restore will not change the nature of
the restore.

87. On the Desktop, double-click the Putty icon to open.

88. From the Saved Sessions, connect to the B5100 - Console.
89. Hit Enter to activate the console.
90. Login in using the following credentials:
Username: admin
Password: password
91. Leave the B5100 Console session open to watch the progress on the B5100.
92. In Network Advisor, on the Switch Configuration Repository, click Restore. A Network Advisor
Message window will display.
93. Read the message and click Yes.
94. Watch the messages appear in the B5100 Console. You should see messages similar to the
following:
2011/11/17-13:38:37, [MFIC-1003], 1081, FID 128, WARNING, R14-ST08-
B5100, Effective Insistent domain ID for the fabric changed from OFF
to ON
2011/11/17-13:38:41, [FCR-1068], 1082, FID 128, INFO, R14-ST08-
B5100, The FC Routing service is disabled.
2011/11/17-13:38:42, [FW-1424], 1083, FID 128, WARNING, R14-ST08-
B5100, Switch status changed from HEALTHY to MARGINAL.
The following message tells us that the switch has been disabled:
2011/11/17-13:38:43, [FW-1439], 1084, FID 128, WARNING, R14-ST08-
B5100, Switch status change contributing factor Switch offline.
The following message tells us that the configuration restore completed successfully. The
configupload command is to save the switch configuration file and configdownload
restores the switch configuration file.
2011/11/17-13:38:56, [CONF-1000], 1085, FID 128, INFO, R14-ST08-
B5100, configDownload completed successfully for all.
The following message tells us the switch is backup and running.
2011/11/17-13:39:01, [FW-1425], 1086, FID 128, INFO, R14-ST08-
B5100, Switch status changed from MARGINAL to HEALTHY.
95. Once the configuration upload is completed another Network Advisor Message will display. Read
the message and click OK.
96. On the Switch Configuration Repository, click OK to close.
97. Close Brocade Network Advisor.
98. Close all Putty sessions.

This ends Module 5: Installing and Configuring Switches.

Module 6: Firmware
Time Allocated: 30 - 45 Minutes
Firmware upgrades can be done using Brocade Network Advisor (Network Advisor) or from the CLI.
This lab will show you how to use the Network Advisor firmware repository as well as the CLI to perform
firmware upgrades
Objectives
In this laboratory exercise, you will perform tasks related to firmware upgrades:
Upgrading firmware from the CLI
Verifying firmware upgrade status from the CLI
Setting up the Network Advisor firmware repository
Viewing firmware release notes using the Network Advisor Firmware Repository
Using Network Advisor to upgrade to upgrade multiple switches

B300
Fabric OS: 7.2.0b
Domain ID: 1
B5100
Fabric OS: 7.2.0b
Domain ID: 2

Module 6: Firmware
B6510
Fabric OS: 7.2.0b
Domain ID: 3
Fabric Wide
Zoning: Cleared
Lab Environment

Module 6: Firmware
Upgrading Firmware from the CLI

In this section of the lab you will perform a firmware upgrade using the interactive
firmwaredownload command from the CLI.
1. From the workstation desktop open Putty and double-click the B300 entry to open a Telnet
session.
2. Log in using the default credentials: admin/password.
3. Issue the firmwareshow command and make a note of the current firmware version.
DEV2-ST01-B300:admin> firmwareshow
Appl Primary/Secondary Versions
-----------------------------------------
FOS v7.2.0b
v7.2.0b
____________________________________________________________________
4. Issue the firmwaredownload command and follow the prompts to begin the firmware upgrade.
See Step5 for example.
5. Once the firmwaredownload starts logging into the switch, open up a console connection to the
B300 through Putty and use the firmwaredownloadstatus command to monitor the update
process.
Note
The firmwaredownloadstatus output is shown on the next page.
R13-ST03-B300:admin> firmwaredownload
Server Name or IP Address: 10.255.252.50
User Name: cfa
File Name: v7.2.0b
Network Protocol(1-auto-select, 2-FTP, 3-SCP, 4-SFTP) [1]: 1
Password: cfa
Server IP: 10.255.252.50, Protocol IPv4
Checking system settings for firmwaredownload...
System settings check passed.
You can run firmwaredownloadstatus to get the status

of this command.
This command will cause a warm/non-disruptive boot but will

require that existing telnet, secure telnet or SSH sessions
be restarted.
Do you want to continue (Y/N) [Y]: y

Firmware is being downloaded to the switch. This step may take up to
30 minutes.
Preparing for firmwaredownload...
Start to install packages...

Module 6: Firmware
dir
##################################################
ldconfig
##################################################
glibc
##################################################
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 ...
R13-ST03-B300:admin> firmwaredownloadstatus
[1]: Wed Aug 10 20:33:06 2011
Firmware is being downloaded to the switch. This step may take up to
30 minutes.
[2]: Wed Aug 10 20:38:36 2011

Firmware has been downloaded to the secondary partition of the
switch.
[3]: Wed Aug 10 20:40:38 2011

The firmware commit operation has started. This may take up to 10
minutes.
[4]: Wed Aug 10 20:43:09 2011

The commit operation has completed successfully.
[5]: Wed Aug 10 20:43:09 2011

Firmwaredownload command has completed successfully. Use
firmwareshow to verify the firmware versions.
6. Once the firmwaredownloadstatus command shows that the firmware was successfully
update use the version and firmwareshow commands to verify and answer the questions
below.
a. What date was the firmware image created on?1
DEV2-ST01-B300:admin> version
Kernel: 2.6.14.2
Fabric OS: v7.2.0b
Made on: Sat Oct 19 00:15:12 2013
Flash: Mon Nov 25 06:55:26 2013
BootProm: 1.0.11
1.Sat Oct 19 00:15:12 2013

Module 6: Firmware
DEV2-ST01-B300:admin> firmwareshow
Appl Primary/Secondary Versions
------------------------------------------
FOS v7.2.0b
v7.2.0b
b. What is the kernel version used for this version of Fabric OS?2
____________________________________________________________________
7. Issue the errshow -r command to view log messages in reverse order.
a. What message is generated when the firmwaredownload command is started?3
2011/05/26-09:18:32, [SULB-1001], 1078268, CHASSIS, WARNING,

Brocade300, Firmwaredownload command has started.
____________________________________________________________________
b. What message is generated when the firmware commit completes?4
2011/11/16-10:23:51, [SULB-1004], 1078878, CHASSIS, INFO, DEV2-ST01-
B300, Firmwarecommit has completed.
____________________________________________________________________
c. What message is generated when the firmwaredownload command completes?5
2011/11/16-10:42:41, [SULB-1002], 1078891, CHASSIS, INFO, DEV2-ST01-
B300, Firmwaredownload command has completed successfully.
____________________________________________________________________
2.2.6.14.2
3.[SULB-1001], 17507, CHASSIS, WARNING, R11-ST15-B30, Firmwaredownload command has started.
4.[SULB-1004], 17520, CHASSIS, INFO, R11-ST15-B30, Firmwarecommit has completed.
5.[SULB-1002], 17522, CHASSIS, INFO, R11-ST15-B30, Firmwaredownload command has completed successfully.

Module 6: Firmware
Upgrading Firmware Using Brocade Network Advisor

Setting Up the Firmware Repository
To make the most of Network Advisors firmware management features you will first want to setup the
firmware repository.
8. From the main Network Advisor screen, on the SAN tab, click Configure > Firmware Management
to open the Firmware Management window.
9. Click the Repository tab.
10. At the bottom left side of the screen click Import.
11. Click the Browse button next to the Enter the firmware location text field.
12. From the desktop, browse to the c:\firmware directory and select the v7.2.0b.zip file.
13. Click Open.
14. Click Browse located next to the Enter release notes location text field.
15. From the desktop, browse to the Documents directory and select the
v7.2.0b_releasenotes_v1.0.pdf file.
16. Click Open.
17. Click OK.

Module 6: Firmware
18. At the Network Advisor Message dialog click Yes to continue.
Note
Importing the firmware into the repository may take several minutes. You can monitor the
progress using the dialog box that is displayed.
19. When the import process completes a dialog will display, click OK to return to the Firmware
Management window.
20. Select the Show switch types in my resource group.

21. In the Firmware Repository field select firmware versions v7.2.0b. Which switches are displayed in
the lower right?
____________________________________________________________________
____________________________________________________________________
22. Click the Show all supported switch types to view all switches capable of running the v7.2.0b
firmware.

Module 6: Firmware
23. Next to the Release Notes entry click the View button to view the current release notes. When you
are finished close the release notes and continue with the lab.
Updating Switch Firmware

Network Advisor allows you to update the firmware on multiple switches simultaneously. All firmware
events are logged in the master log.
24. On the Firmware Management window click the Download tab.
25. Expand the fabric and the Chassis Group so you can see all the switches.
26. Select the B5100 and the B6510 from your station using CTRL + click.
27. Click the right arrow to add the switches to the Select Switches list.
28. In the Firmware to Download column of all switches select v7.2.0b.
29. Check the Overwrite current firmware check box
Note
The Overwrite current firmware option is only needed if you are flashing a switch with the
same or an earlier version of Fabric OS. It is used in this lab because the switches are pre-
loaded with Fabric OS v7.2.0b.
30. Verify that the Status column reports Ready for all switches.

Module 6: Firmware
31. Click the Download button.
32. Read the Network Advisor Message dialog, click Yes to continue.
33. Another Network Advisor Message dialog will display; read it and click Yes to continue.
34. What is now displayed in the Status column?6
6.In Progress

Module 6: Firmware
____________________________________________________________________
35. Wait for about a minute, the Message column will change to show the current firmware download
status.
36. You can click on any of the switches to see the firmwaredownloadstatus command output
in the Status Details text field at the bottom of the Firmware Management window.
37. Move and resize the Firmware Management window so you can watch the Master Log on the main
Network Advisor window behind.
38. Scroll through the Master Log, located at the bottom of the main Network Advisor window, while
the firmware is updating. Look at some of the events by right-clicking and choosing Properties.
What Value was logged for the Category property when the firmware was imported to the
repository?7
____________________________________________________________________
39. Review the firmware messages and click Close when finished.
40. Click Close to close the Firmware Management window and return to the main Network Advisor
window.
This ends Module 6: Firmware lab.
7.User Action Event

Module 7: Zoning
Time Allocated: 30 - 45 Minutes
Objectives
Configure, verify, administer, and describe Brocade zoning processes and enforcement
methodologies.
Overview
In this lab exercise, you will perform tasks related to zoning a Brocade fabric. This lab is divided into
the following sections:
Changing the default zoning behavior using Brocade Network Advisor
Creating and activating a zoning configuration using Network Advisor
Verifying LUN connectivity using Network Advisor
Verifying LUN connectivity using Host Connectivity Manager (HCM)

B300
Fabric OS: 7.2.0b
Domain ID: 1
B5100
Fabric OS: 7.2.0b
Domain ID: 2

Module 7: Zoning
B6510
Fabric OS: 7.2.0b
Domain ID: 3
Fabric Wide
Zoning: Cleared
Lab Environment
Lab Setup
Prior to starting this lab you will need to disable one of the hosts connections to the fabric. This will
make it easier to determine if the zoning configuration is working properly. Use the portenable and
portdisable commands to set the following:
On the B300 disable port 0
On the B300 enable port 1
On the B6510 enable port 0
This will ensure that the host is only connected to the fabric using port 0 of the B6510.

Module 7: Zoning
Configuring Zoning in Network Advisor

Setting the Default Zone
Default zoning controls device access within a fabric when zoning is not enabled. Default zone
settings are managed with the defzone CLI command and through the Network Advisor Zoning tool.
Default zoning is in effect when a user-specified zone configuration is not enabled and is overridden
when a user-specified zone configuration is enabled.
In this lab exercise you will change the default zoning from all access to no access. This means that
you will have to implicitly zone any storage devices you want your host to have access to.
1. From the main Network Advisor screen, on the SAN tab, select your fabric from the navigation
pane on the left.
2. Highlight the fabric name in the product window, right-click and select View > Connected End
Devices > Show All. This will show the HBA and storage LUNs that are known to Network Advisor
through the fabric.
3. In the navigation pane on the left expand your fabric then expand the Storage Group and Host
Group.
4. Verify that both your storage and your host are visible to the fabric and listed in Network Advisor.
5. Select your fabric and click Configure > Zoning > Fabric to open the Zoning window.
6. Click the Active Zone Configuration tab.

Module 7: Zoning
7. Verify that the default zone is currently set for All Access.
8. Return to the Zone DB tab and click Zoning Policies.
9. Select the Disable (No Access), click OK.

10. The Network Advisor Message window will display, click OK.
11. Click the Active Zone Configuration tab and confirm the new default zone setting, when you are
finished return to the Zone DB tab.
Creating and Activating a Zone Configuration

12. Verify that the Zoning Scope pull-down is set to your fabric and the Zone DB pull-down is set to
Fabric Zone DB.
13. In the Potential Members field, right-click and select Show Connected End Devices.

Module 7: Zoning
14. Underneath the Zones panel click the New Zone.

15. Change the name of the zone to Zone1. Press Enter when you are done typing to save the change
and select the new Zone1.

Module 7: Zoning
16. In the Potential Members pane expand the Host Group and the Storage Group.
17. Using CTRL+Click select the following devices:
the HBA port connected to the B6510
the storage port connected to the B300
Note
You can expand the HBA entries and look at the FC Address column for the ports to deter-
mine which switch domain the HBA ports are connected to. The B300 is domain 1 and the
B6510 is domain 3.
18. Click the right arrow to add the device to Zone1.

19. Click the New Configuration, change the name to ConfigA.

Module 7: Zoning
20. Select Zone1 and click the right arrow to add the zone to the ConfigA.configuration.
21. Click Apply.
22. A Network Advisor Message window will display, click OK to save the configuration and return to
the Zoning window.
23. Has the zoning configuration been enabled?

____________________________________________________________________1
1.No. The zone configuration has been saved to the defined database on the fabric without being activated.

Module 7: Zoning
24. Ensure that ConfigA is highlighted and click Activate, the Activate Zone Configuration window
displays.
25. After reviewing the zoning configuration for accuracy click OK, a Network Advisor Message window
displays.
26. Review the message and click Yes to activate the configuration.
27. Another Network Advisor Message window will display, review the message and click OK to return
to the Zoning window.

Module 7: Zoning
28. In the Zoning window, click the Active Zone Configuration tab to verify the active configuration.
29. Click Cancel to return to the main Network Advisor window.
Note
The configuration has already been saved to the fabric and activated. Clicking cancel does
not undo these actions, it simply closes the window. If there were changes made that were
not saved to the fabric then they would be lost.
Verifying Device Connectivity

Using Network Advisor to verify Connectivity
30. From the main Network Advisor window on the SAN tab click Monitor > Troubleshooting > FC >
Device Connectivity. The Device Connectivity Troubleshooting window displays.
31. Select the Select two device ports.
32. In the Available Device Ports field select the storage device and the host port that was used to
create the above zone.
Note
Be sure to expand the tree to the lowest level and select the port.
33. Click the right arrow to add these two ports to the Selected Device Ports field.

Module 7: Zoning
34. Click OK and wait for the tests to run. The Device Connectivity Troubleshooting Results window will
display.
35. Scroll through the Details field and verify that all the tests were passed.
36. Click the Trace Route and wait for the Trace Route Summary window to display.

Module 7: Zoning
37. Verify the following:

a. Did the ping succeed for both devices?
b. What was the average round trip time for each device?
c. Review the Forward Route, Reverse Route, and FC Ping tabs.
38. When you are finished click close to return to the Device Connectivity Troubleshooting Results
window.
39. Click Close again to return to the main Network Advisor screen.

Module 7: Zoning
Using HCM and Disk Management to Verify Connectivity

40. On the desktop double click the Host Connectivity Manager icon to launch HCM. Log into HCM
using the default credentials, Administrator/password.
41. In the navigation pane on the left expand the tree fully for both ports.
a. Is the LUN displayed for both ports? Why?2
____________________________________________________________________
____________________________________________________________________
b. How would you modify the zoning configuration if you wanted the LUN to be visible on both
ports?3
____________________________________________________________________
____________________________________________________________________
42. Close the HCM window and return to the desktop.

43. Right-click the My Computer icon and select Manage,
44. In the navigation pane on the left, expand Storage and select Disk Management.
45. If you are prompted to initialize the disk verify that Disk 0 is NOT selected and click OK.
46. Verify that the LUN is visible and then close the Server Manager window to return to the desktop.
2.No. The storage device is only zoned with the HBA port connected to the B6510.
3.Create a second overlapping zone that includes the additional HBA port and the storage or add the additional
HBA port to the existing zone.

Module 7: Zoning
This ends Module 7: Zoning lab.

Module 7: Zoning

Objectives
Describe, configure, and validate multi-switch fabric Trunking solutions
Overview
This lab exercise covers tasks related to trunking in Brocade fabrics. This lab is divided into the
following sections:
Trunking with CLI
Routing over trunks

B300
Fabric OS: 7.2.0b
Domain ID: 1
Ports Disabled: 0 (disabled in previous lab)
B5100
Fabric OS: 7.2.0b
Domain ID: 2

B6510
Fabric OS: 7.2.0b
Domain ID: 3
Fabric Wide
Zoning: Cleared
Lab Environment

Getting Started
This lab exercise verifies that the switches are using the default exchange-base routing.
1. Open Telnet sessions to the B5100 and B6510 switches using Putty.
2. Ensure that Trunking and Extended Fabric licenses are installed on the B5100 and B6510
switches using the licenseshow command. Contact the instructor if this licenses is missing
from either switch.
ST01-B5100:admin> licenseshow
c9SdQeRedATeRK:
Fabric license
bRyRc9RRzbci:
Full Ports on Demand license - additional 16 port upgrade license
PWrGHFKXFHQ4EAMSPWNJFXXSfEY:
Enhanced Group Management license
RR3rEXQKTXHHmR3gLYRgF3ttSXS:
8 Gig FC license
QDQfZS3QWaPmrSDHfrMRGXYFrff:
Fabric Watch license
Performance Monitor license
Trunking license
Adaptive Networking license
7aACCMPLDAfrRrFJXHZEGHS3FfL:
Server Application Optimization license
ST01-B6510:admin> licenseshow
byeQeSczRdez:
Fabric Watch license
byeQeSczRdgz:
Performance Monitor license
byeQeSczRdkz:
Trunking license
byeQeSczRdcz:
SdScQQbyeyTe:
byeQeSczRdc1:
FICON_CUP license
byeQeSczRdcF:
Full Ports on Demand license - additional 24 port upgrade license
gaaM7Ra3CREYNP9CEKg7HCJfWR:
Adaptive Networking license
B7BLSt4DYHLF7BGtGSW794DmSH:
Server Application Optimization license

3. Type the aptpolicy command on both the B6510 and B5100 to verify this; the output should
display: Current Policy: 3.
ST01-B5100:admin> aptpolicy
Current Policy: 3
3 : Default Policy
1: Port Based Routing Policy
2: Device Based Routing Policy (FICON support only)
3: Exchange Based Routing Policy
ST01-B6510:admin> aptpolicy
Current Policy: 3
3 : Default Policy
1: Port Based Routing Policy
2: Device Based Routing Policy (FICON support only)
3: Exchange Based Routing Policy
4. If the policy is not exchange based policy then change it to this policy using the syntax modeled
in this example:
ST01-B5100:admin> switchdisable;aptpolicy 3;switchenable
Policy updated successfully.
Using the CLI to Evaluate Basic Trunking

In this part of the lab, CLI sessions will be used to evaluate trunks between the B6510 and B5100
switches.
5. Type the portcfgshow command on both the B6510 and B5100 switches to verify that
trunking is enabled on all the ports on each switch in your fabric.1
ST01-B6510-LS1:FID1:admin> portcfgshow
Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
----------------------+---+---+---+---+-----+---+---+---+-----+---+---+---+-----+---+---+---
Octet Speed Combo 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Speed AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN
AL_PA Offset 13 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
<output truncated>
6. If portcfgshow output does not show Trunk Port ON, use the following command to
ensure that both switches are capable of establishing a trunk: switchcfgtrunk 12
1. Trunk Ports should display ON.

2. The switchcfgtrunk 1 command will turn trunking ON for all switch ports.

7. Type the switchshow command from the B6510 and use the output to answer the following
questions:
switchType: 109.1
switchState: Online
switchMode: Native
switchDomain: 3
switchId: fffc03
switchWwn: 10:00:00:05:33:93:69:3f
switchBeacon: OFF
FC Router: OFF
Address Mode: 0

==================================================
0 0 030000 id N8 Online FC F-Port 10:00:00:05:1e:56:c8:2b
1 1 030100 -- N16 No_Module FC
2 2 030200 -- N16 No_Module FC
3 3 030300 -- N16 No_Module FC
4 4 030400 -- N16 No_Module FC
5 5 030500 -- N16 No_Module FC
6 6 030600 id N16 No_Sync FC Disabled (Persistent)
8 8 030800 id N8 Online FC E-Port 10:00:00:05:1e:7f:06:9c "ST01-B5100"
(upstream)(Trunk master)
9 9 030900 id N8 Online FC E-Port (Trunk port, master is Port 8 )
10 10 030a00 -- N16 No_Module FC
<truncated output>
a. How many trunks exist?

_______________________________________________________________3
b. How can you determine which Trunk Master is the Principal ISL?
_______________________________________________________________4
c. List the criteria that needs to be met in order for ports to form a trunk:
_______________________________________________________________5
8. From the 5100, type the islshow command and answer this questions.
ST01-B5100:admin> islshow
1: 8-> 8 10:00:00:05:33:93:69:40 3 ST01-B6510 sp: 8.000G bw: 16.000G TRUNK QOS
2: 15-> 15 10:00:00:05:1e:0a:83:6d 1 ST01-B300 sp: 8.000G bw: 16.000G TRUNK QOS
a. What is the aggregate bandwidth of each trunk group:

_______________________________________________________________6
9. What do the 8 > 8 and 15 > 15 values tell you?
_______________________________________________________________7
3. There should be 1 trunk with 1 different trunk masters.

4. The principal Trunk Master ISL will either say upstream or downstream. The non-principal ISL/trunk will
not show upstream or downstream.
5. Each end of the link must have a trunking license, common speed and ports must originate and end in an
ASIC port group and portcfgtrunkport must be enabled.
6. The aggregate bandwidth (bw) should be 16G.
7. These are the Master ISLs in each trunk group.

10. From the B6510, type the trunkshow command and evaluate the deskew values.
ST01-B6510:admin> trunkshow
1: 8-> 8 10:00:00:05:1e:7f:06:9c 2 deskew 15 MASTER
9-> 9 10:00:00:05:1e:7f:06:9c 2 deskew 15
Note the greatest deskew difference in your trunk groups: ___________________

11. A deskew of 15 deskew units is used as the baseline for the ISL with the least latency. What
deskew value could cause additional latency?
_______________________________________________________________8
CHECK POINT
You established that there are two 8 Gbps per port ISL trunks between the B6510 and B5100 switches
in your fabric.
Evaluate the Current B6510 Routing over Trunks Status

12. Open Internet Explorer from the desktop and enter the IP address for your stations B6510 to
open a Web Tools session. (Refer to your Student Information Sheet for the IP address.)
13. Enter the following credentials:
Username: admin
Password: password
14. Click OK on the Seurity Banner dialog window to proceed to Web Tools.
15. In the menus click Configure > Switch Admin.
16. Click Show Advanced Mode located in the upper right-hand corner, if necessary.
17. Click the Trunking tab and note the Trunk Master port for the trunk.
8. A deskew of 30 or more could cause additional latency.

18. Click the Routing tab and verify the two routes,(Out Ports), and reference the Trunk Master
noted above.
NOTE
Note the configuration options that are available from the Web Tools Routing view.
19. Click Off located under the Dynamic Load Sharing (DLS) section.
20. Click Apply.
21. Click Yes on the Routing: Confirm Action dialog box. Why can this option not be turned
Off?_________________________________________________________________ 9
22. Is there an option in the Web Tools Routing view to change from the default exchange-based
routing to port-based routing?
_____________________________________________________________________10
CHECK POINT
Web Tools was used to verify that there are two routes from the B6510_St01 to the B6510_St02. These
routes are through Trunk Masters.
9. Exchange-Based Routing is turned on.

10. Yes, the routing policy can be changed from the CLI using the aptpolicy command or WebTools after
the switch is disabled.


choose Shutdown.
This ends Module 8: Routing and Trunking.

Objectives
Describe, configure, and validate Brocade Fabric OS long distance parameters.

B300
Fabric OS: 7.2.0b
Domain ID: 1
B5100
Fabric OS: 7.2.0b
Domain ID: 2

B6510
Fabric OS: 7.2.0b
Domain ID: 3
Fabric Wide
Zoning: Cleared
Student Information

Getting Started
1. Open Telnet sessions to your B6510 and B5100 using Putty.
2. Type the licenseshow command and verify that the Extended Fabric license
3. The first step is to verify that both switches are configured with default distance settings.
a. Type the portcfgshow command on both switches. Verify that the Long Distance row
displays .. for all ports indicating that long distance is disabled.
ST01-B6510:admin> portcfgshow
Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-
Fill Word 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
AL_PA Offset 13 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
<truncated output>
4. To see what the available BB credits are at this point, type the portbuffershow fromyour B6510
ST01-B6510:admin> portbuffershow
User Port Lx Max/Resv Avg Buffer Usage & FrameSize Buffer Needed Link Remaining
Port Type Mode Buffers Tx Rx Usage Buffers Distance Buffers
---- ---- ---- ------- ---------------------------- ------ ------- --------- ----------
0 F - 8 - ( - ) - ( - ) 8 - -
1 F - 48 - ( - ) - ( - ) 48 - -
2 - 8 - ( - ) - ( - ) 0 - -
3 - 8 - ( - ) - ( - ) 0 - -
4 - 8 - ( - ) - ( - ) 0 - -
5 - 8 - ( - ) - ( - ) 0 - -
6 - 8 - ( - ) - ( - ) 0 - -
7 - 8 - ( - ) - ( - ) 0 - -
8 E - 8 - ( - ) - ( - ) 34 34 <2km
9 E - 8 - ( - ) - ( - ) 34 34 <2km 7130
5. To enable LD mode on port 8 of the B6510 with a desired distance of 25 km, issue the following
CLI command:
ST01-B6510:admin> portcfglongdistance 8 ld 1 -distance 25
Reserved Buffers = 206
Warning: port may be buffer limited if cable is longer than
estimated.

6. Issue the portcfgshow command and note the new configuration for port 8.
ST01-B6510-LS1:FID1:adminOdd> portcfgshow
Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
----------------------+---+---+---+---+-----+---+---+---+-----+---+---+---+-----+---+---+---
Octet Speed Combo 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
AL_PA Offset 13 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Long Distance .. .. .. .. .. .. .. .. LD .. .. .. .. .. .. ..
VC Link Init .. .. .. .. .. .. .. .. ON .. .. .. .. .. .. ..
Locked L_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked G_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Disabled E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
ISL R_RDY Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
RSCN Suppressed .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Persistent Disable .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
LOS TOV enable .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
NPIV capability ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON
NPIV PP Limit 126 126 126 126 126 126 126 126 126 126 126 126 126 126 126 126
QOS E_Port AE AE AE AE AE AE .. AE AE AE AE AE AE AE AE AE
EX Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Mirror Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Rate Limit .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Credit Recovery ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON
Fport Buffers .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Port Auto Disable .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
CSCTL mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
D-Port mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Compression .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Encryption .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
FEC ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON
Fault Delay 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
<output truncated>

7. From the B5100, issue the switchshow command and answer these questions.
switchType: 66.1
switchState: Online
switchMode: Native
switchDomain: 2
switchId: fffc02
switchWwn: 10:00:00:05:1e:7f:06:9c
switchBeacon: OFF
FC Router: OFF
Address Mode: 0

==================================================
0 0 020000 -- N8 No_Module FC
1 1 020100 id N8 No_Module FC
2 2 020200 -- N8 No_Module FC
3 3 020300 -- N8 No_Module FC
4 4 020400 -- N8 No_Module FC
5 5 020500 -- N8 No_Module FC
6 6 020600 -- N8 No_Module FC
7 7 020700 -- N8 No_Module FC
8 8 020800 id N8 Online FC E-Port segmented,10:00:00:05:33:93:69:3f ("No class F
frames, Long distance fabric or LD mode" incompatible)
9 9 020900 id N8 Online FC E-Port 10:00:00:05:33:93:69:3f "ST01-B6510"
(downstream)(Trunk master)
10 10 020a00 -- N8 No_Module FC
11 11 020b00 -- N8 No_Module FC
<output truncated>
a. What is the status of port 8?

____________________________________________________________________1
b. What is the reason given for the status?
____________________________________________________________________2
8. From your B5100, issue the following commands. The fill word for the port needs to be changed
in order to be compatible with the B6510 on the other side of the link.
R15-ST02-B5100:admin> portcfgfillword 8 3
R15-ST02-B5100:admin> portcfglongdistance 8 ld 1 -distance 25
estimated.
NOTE
You may need to disable/enable the port for the connection to come online, use the commands
portdisable and portenable.
1.Segmented
2."No class F frames, Long distance fabric or LD mode" incompatible

9. From the B6510, issue the switchshow command.

switchType: 109.1
switchState: Online
switchMode: Native
switchDomain: 3
switchId: fffc03
switchWwn: 10:00:00:05:33:93:69:3f
switchBeacon: OFF
FC Router: OFF
Address Mode: 0

==================================================
0 0 030000 id N8 Online FC F-Port 10:00:00:05:1e:56:c8:2b
1 1 030100 id N16 No_Module FC
2 2 030200 -- N16 No_Module FC
3 3 030300 -- N16 No_Module FC
4 4 030400 -- N16 No_Module FC
5 5 030500 -- N16 No_Module FC
8 8 030800 id N8 Online FC LD E-Port 10:00:00:05:1e:7f:06:9c "ST01-B5100" (Trunk
master)
9 9 030900 id N8 Online FC E-Port 10:00:00:05:1e:7f:06:9c "ST01-B5100"
(upstream)(Trunk master)
10 10 030a00 -- N16 No_Module FC
<output truncated>
What is the status of port 8?

_______________________________________________________________3
10. From the B6510, issue a trunkshow command.
How many trunks are there? ____ 4

Why?
____________________________________________________________________ 5
11. From the B6510, issue the following command:
estimated.
3. Online and operating normally

4. 2
5. The two ISLs in the trunk do not have the same long distance settings

12. From the B5100, issue the following commands:

ST01-B5100:admin> portcfgfillword 9 3
estimated.
13. From the B6510, issue a trunkshow command.
9-> 9 10:00:00:05:1e:7f:06:9c 2 deskew 16
How many trunks are there? ____6

why?
____________________________________________________________________7
14. From the B6510, issue the portbuffershow command.
ST01-B6510:admin> portbuffershow
User Port Lx Max/Resv Avg Buffer Usage & FrameSize Buffer Needed Link Remaining
Port Type Mode Buffers Tx Rx Usage Buffers Distance Buffers
---- ---- ---- ------- ---------------------------- ------ ------- --------- ----------
0 F - 8 - ( - ) - ( - ) 8 - -
1 F - 48 - ( - ) - ( - ) 48 - -
2 - 8 - ( - ) - ( - ) 0 - -
3 - 8 - ( - ) - ( - ) 0 - -
4 - 8 - ( - ) - ( - ) 0 - -
5 - 8 - ( - ) - ( - ) 0 - -
6 - 8 - ( - ) - ( - ) 0 - -
7 - 8 - ( - ) - ( - ) 0 - -
8 E LD 206 - ( - ) - ( - ) 46 46 <2km
9 E LD 206 3( 144) 3( 124) 46 46 <2km
10 - 8 - ( - ) - ( - ) 0 - -
11 - 8 - ( - ) - ( - ) 0 - - 6786
15. Compare the portbuffershow output from Step14 with what was displayed in Step4.
a. How do ports 8 and 9 differ between the two outputs?
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________8
16. When you have finished this part of the lab perform the following actions:
a. B6510: Type the portcfgdefault command on ports 8 and 9.
b. B5100: Type the portcfgdefault command on port 8 and 9.
6. 1
7. The long distance settings at both ends of the link are the same.
8. In the second output, the port modes are listed as LD, and the Max/Resv Buffers are 206 each, instead
of 8 each.


choose Shutdown.
This ends Module 9: Long Distance lab.

The focus of this lab exercise is to use troubleshooting tools and techniques covered in the
Troubleshooting module, as well as information from other portions of the class. You will download a
configuration file into each of the switches in your station. These configuration files contain errors.
Find and correct all the errors. There is a cheat sheet located in Appendix A: Cheat Sheet.
Objectives
Use Brocade Network Advisor to run D_Port tests
Use Brocade Network Advisor to collect switch, host and Brocade Network Advisor application and
client session logs
Use Brocade Network Advisor to run reports on the SAN
Perform a configdownload using files with known bugs
Troubleshoot fabric merge issues using the CLI and Brocade Network Advisor

B300
Fabric OS: 7.2.0b
Domain ID: 1
B5100
Fabric OS: 7.2.0b
Domain ID: 2

B6510
Fabric OS: 7.2.0b
Domain ID: 3
Fabric Wide
Zoning: Cleared
Lab Environment

Capturing Technical Support Data

In this section of the lab you use Brocade Network Advisor to capture switch, host, Network Advisor
application and session logs.
1. From the tool bar click Monitor > Technical Support > Product /Host SuportSave
a. Under SAN Products, select the Name of your fabric.
In the example below the name of the Fabric was St01.
b. Click the right arrow to add all switches in the fabric to the Selected Products and Hosts list.
See example below:
c. Click OK.
This starts the capture of the supportsave data and opens up the Technical SupportSave
Status window. The status of data captures are updated about once a minute. The capture of
the data takes several minutes to complete. See example below:

Note
If the operation fails restart Nework Advisor.
d. Once all data has been captured click Close.

2. Capture logs for Brocade Network Advisor application and client session.
a. From the pull down menu click on Monitor > Technical Support > SupportSave. This opens the
SupportSave window.
b. Keep the defaults (as shown above) and click OK. The supportsave data capture begins and a
Network Advisor Message appears.
c. Once the capture is complete click OK to close the message window. The Master Log contains
an event showing the results. See example below:

3. View the supportsave repository: From the Brocade Network Advisor main window click on
Monitor > Technical Support > View Repository.
a. You should see four files:
NOTE
There may be older files in the repository. Look in the Las Modified column and find the files that match
todays date.
Supportinfo.... This contains the supportsave data for all four switches
DCM-SS.... This contains the supportsave data from the Network Advisor application
DCM-Client.... This contains the supportsave data from the current client session

Brocade Network Advisor Reports

In this section of the lab you will use Brocade Network Advisor to run report on the SAN.
4. From the Brocade Network Advisor pull down menu and click on Reports > Generate, this opens
the Generate Reports window.
a. Under Select Output Template, select Fabric Summary Report and Fabric Ports Report (see
example below).
b. Click OK.

This initiates the generate report process and opens the View Reports window and displays
the Fabric Summary Report when done.
c. How many ports are in the fabric? ____________1

d. Take a minute and review this report.
e. Expand out all the reports By time and click on the Fabric Ports Report_Administrator.
Report; this will open up the Fabric Ports Report.
f. Looking at the Switch Utilization, what is the "Number of Ports connected"? _____________2
g. Looking at the Switch Utilization, what is the "Number of Ports Free"? _____________3
1. 112
2. 15
3. 97

See example report below:

Troubleshooting Switch Merge Issues

In this section you will download a configuration file to both the B300 and B5100. Once the
configuration files are successfully downloaded to both switches enable the switches using the
switchenable command. A number of issues have been introduced into the switch configurations
that will prevent the fabric from merging. Using the skills and commands you have learned in class
troubleshoot the merge issue.
The lab is finished when you have found and resolved all of the issues. When you have completed this
lab you should have a four switch fabric, all ISLs up and running, all devices connected, and a valid
zoning configuration.
Downloading the B300 Configuration File

5. On the desk double click on the PuTTY ICON.
6. Select the B300 and then click Open.
Login: admin
Password: password
7. Disable the switch using the switchdisable command.
R13-ST01-B300:admin> switchdisable
8. Type the configdownload command to download a config file and answer the prompts as
listed below:
R13-ST01-B300:admin> configdownload
Protocol (scp, ftp, sftp, local) [ftp]: ftp
Path/Filename [<home dir>/config.txt]: config_b300
Section (all|chassis|switch [all]):
*** CAUTION ***
This command is used to download a backed-up configuration

for a specific switch. If using a file from a different
switch, this file's configuration settings will override
any current switch settings. Downloading a configuration
file, which was uploaded from a different type of switch,
may cause this switch to fail. A switch reboot might be
required for some parameter changes to take effect.
configDownload operation may take several minutes

to complete for large files.
Do you want to continue [y/n]: y

Password: cfa
duplicate license-key "S9bSdRyQ9bTAgTeG"
duplicate license-key "S9bSdRyQ9bTQcTeS"
duplicate license-key "MW7BKM7PHLtD7GCEXJKWEKrgQ9YRSDrKBADFB"

duplicate license-key "GCDrFTGKZQtWTNgLX3faD7SQK7mAQ49rBAENN"

duplicate license-key "RAQJrgDJaFCPFJSQmf7tKSMSLaC9Nar3BJHQE"
Doing configDownload on switch ...

Activating configDownload: Switch is disabled
configDownload complete: All selected config parameters are
downloaded
Note
If the configdownload command fails change the fabric to defzone --allaccess
and try the download again.
9. Enable the switch using the switchenable command.
Downloading the B5100 Configuration File

10. On the desk double click on the PuTTY icon.
11. Select the B5100 and then click Open.
Login: admin
Password: password
12. Disable the switch using the switchdisable command.
R13-ST01-B5100:admin> switchdisable
13. Download the configuration file using the configdownload command and answer the prompts
as listed below:
R13-ST01-B5100:admin> configdownload
Protocol (scp, ftp, sftp, local) [ftp]:
Path/Filename [<home dir>/config.txt]: config_b5100
Section (all|chassis|switch [all]):
*** CAUTION ***
This command is used to download a backed-up configuration

for a specific switch. If using a file from a different
switch, this file's configuration settings will override
any current switch settings. Downloading a configuration
file, which was uploaded from a different type of switch,
may cause this switch to fail. A switch reboot might be
required for some parameter changes to take effect.
configDownload operation may take several minutes

to complete for large files.
Do you want to continue [y/n]: y

Password: cfa

duplicate license-key "bcze9bbS9zcd0fAp"

duplicate license-key "SbRcSQede9TcWdTj"
duplicate license-key "KGG9RaRra9FJSFNXKD9YFtTXBJm74YNCBAgYR"
duplicate license-key "GHCtNLTPrB4CQM3CHDGt7DNJarWKBmFYBSWtA"
duplicate license-key "ra34HgYfTEYEra4fCQRR9339StKfm9rGBJYaQ"
duplicate license-key "S9X9rZQfSRCFAXTrAF4WMQ9BrFPLCgKSBAHtR"
Doing configDownload on switch ...

Activating configDownload: Switch is disabled
configDownload complete: All selected config parameters are
downloaded
Note
If the configdownload command fails change the fabric to defzone --allaccess
and try the download again.
14. Enable the switch using the switchenable command.

R13-ST01-B5100:admin> switchenable
Troubleshooting Switch Merge Issues

The following commands or applications will be useful in troubleshooting these issues (Note: This is
not a complete list):
switchshow
portcfgshow
cfgshow
zoneshow
defzone --show
Brocade Network Advisor
Use the space provided below to catalogue the issues you find:
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________

____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
This ends Module 10: Troubleshooting lab.

Lab Guide CFA200 Rev0114 LG - L

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lab Guide CFA200 Rev0114 LG - L

Uploaded by

Copyright:

Available Formats

CFA 200

Brocade Core Gen 5

European Headquarters - Geneva, Switzerland

Asia Pacific Headquarters - Singapore

2014 Brocade Communications Systems, Inc. All Rights Reserved.

Module 2: Fibre Channel Theory

Module 4: Director FRU Identification

Module 5: Installing and Configuring Switches

CFA 200 Revision 0114 iii

Module 8: Routing and Trunking

iv Revision 0114 CFA 200

Module 10: Troubleshooting

CFA 200 Revision 0114 v

Revision 0114 CFA 200 1

Record Remote Lab Access Information

2 Revision 0114 CFA 200

Connecting to the Brocade RSL Environment

Revision 0114 CFA 200 3

9. The Remote Desktop Connection window will display, click Connect.

4 Revision 0114 CFA 200

11. Select the username assigned by the instructor.

12. Enter the password assigned by the instructor.

Revision 0114 CFA 200 5

Close Open Sessions and Exit Remote Connection

16. Click on Sign Out in the upper right corner.

17. Close the browser.

This ends the Remote Lab Access Instructions lab exercise.

6 Revision 0114 CFA 200

Expected Start State

Revision 0114 CFA 200 7

8 Revision 0114 CFA 200

Revision 0114 CFA 200 9

Fibre Channel Levels

1. FC-4=C; FC-3=E; FC-2=A; FC-1=D; FC-0=B

10 Revision 0114 CFA 200

Node and Port World-Wide Names

4. Match the Brocade World Wide Name with a type below.4

4.Node WWN = 10:00:00:05:1e:02:a5:49, Port WWN (port 7) = 20:07:00:05:1e:02:a5:49

Revision 0114 CFA 200 11

6. Log into the B300 using the following credentials:

5.1=F_Port, 2=U_Port, 3=E_Port, 4=FL_Port, 5=F_Port

12 Revision 0114 CFA 200

Credit Recovery: Inactive

Port part of other ADs: No

8. Log into the B5100 using the following credentials:

Revision 0114 CFA 200 13

portFlags: 0x1000090b PRESENT ACTIVE E_PORT T_PORT T_MASTER G_PORT

Credit Recovery: Inactive

Port part of other ADs: No

14 Revision 0114 CFA 200

24-bit Device Addressing

Revision 0114 CFA 200 15

Permanent Port Name: 10:00:00:05:1e:56:c8:2a

16 Revision 0114 CFA 200

Switch entry for 3

Switch entry for 3

Revision 0114 CFA 200 17

Fabric Port Name: 20:00:00:05:33:93:69:40

This ends Module 2: Fibre Channel Theory.

11.The nscamshow -t displays the device type.

18 Revision 0114 CFA 200

DCX Feature Hunt

Revision 0114 CFA 200 19