Brocade BCFA 16 Gbps Training PDF

CFA 200
Brocade Certified
Fabric Administrator
(BCFA) 16 Gbps
Training
Lab Guide
Brocade University
Revision 0512
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
2012 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 0512
Contents
Remote Lab Access Instructions
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Record Remote Lab Access Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Login information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Connecting to the ITTM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Enrolling in the Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Connecting to the Brocade RSL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Module 2: Fibre Channel Theory

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Fibre Channel Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Classes of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Frame Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Node and Port World-Wide Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Port Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Well-Known Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
24-bit Device Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Module 4: Director FRU Identification

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
DCX Feature Hunt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
DCX Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
DCX non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
DCX-4S Feature Hunt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
DCX-4S Port Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
DCX-4S non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Director Feature Hunt Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
DCX Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
DCX non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
DCX-4S Port Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
DCX-4S non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Module 5: Installing and Configuring Switches

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configure and Verify Basic Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Setting the Command Line Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuring and Verifying Basic Settings on the B300. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring and Verifying Basic Settings on the B5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
View Time for the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuring an NTP Server for the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Change the Time Zone for Each Switch in the Fabric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Setting a Message of the Day and a Login Banner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
CFA 200 Revision 0512 iii

Verify Licensed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
View the Switch Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
View the Chassis Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Turn on Enhanced Change Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Specify a Syslog Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Determining Switch Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Verifying Switch Uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Checking Switch Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Looking at Sensor Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Looking at Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Looking at the Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Examine Fabric Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Verify Device Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Verify that Devices have Successfully Logged into the Fabric. . . . . . . . . . . . . . . . . . . . . . . . . 55
Discovering the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Configuration Backup Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Configuration Save (Backup) and Restore Using Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . 63
Module 6: Firmware
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Upgrading Firmware from the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Upgrading Firmware Using Brocade Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Setting Up the Firmware Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Updating Switch Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Module 7: Zoning
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Configuring Zoning in Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Setting the Default Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Creating and Activating a Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Verifying Device Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Using Network Advisor to verify Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Using HCM and Disk Management to Verify Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Module 8: Routing and Trunking

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Student Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Lab Pairing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Using the CLI to Evaluate Basic Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
iv Revision 0512 CFA 200

Using Brocade Network Advisor to Configure Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Use CLI to Evaluate the Current Trunking Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Restore the Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Evaluate the Current B6510 Routing over Trunks Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Module 9: Long Distance

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Student Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Lab Pairing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Configure Trunking Over Distance . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Restore the Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Module 10: Troubleshooting

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Lab Station Pairing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Run D_Port Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Capturing Technical Support Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Brocade Network Advisor Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Troubleshooting Switch Merge Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Downloading the B300 Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Downloading the B5100 Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Troubleshooting Switch Merge Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Appendix A: Cheat Sheet

Module 2: Fibre Channel Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Module 10: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
B300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
B5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Lab Setup
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
List of Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Lab Environment: Two Stations (Odd and Even) Configuration. . . . . . . . . . . . . . . . . . . . . . 149
Individual Lab Station Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
CFA 200 Revision 0512 v

vi Revision 0512 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 preconnected.
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 0512 CFP 300 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:
Circle one: ITTM RSL.Brocade.com
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.
4. If you are assigned an ITTM pod continue to Connecting to the ITTM Environment on page3.
5. If you are assigned an RSL station skip to Connecting to the Brocade RSL Environment on
page10.
2 Revision 0512 CFP 300

Connecting to the ITTM Environment

These steps are for connecting to a lab for a class that is using the ITTM lab environment. If you are
using the Brocade RSL environment skip to the Connect to the Brocade RSL Environment section.
6. Connect to the remote lab environment using the URL: http://brocade.netsysenterprise.com/
7. From the login page:
a. If this is the first time you have used the remote lab system, click on the register here link
below the Log In button.
b. If you have already registered, enter your credentials select the Log In button. Skip to the next
section.
FIGURE 1 ITTM login screen

8. Enter the required information, agree to the terms of service, and click the Register button.
9. On the login page, enter your credentials select the Log In button.
Enrolling in the Class

Enrolling in the class requires a registration code and a student number. Your instructor will provide
the registration code and assign you a student number. Document your information in the space
provided.
Registration Code: __________________
Student Number: ___________________

10. To enroll, from your home page, select Training > Enroll in a Class.
11. Enter your registration code and student number and click Enroll Now.
12. In the Class Training section of your home page you will see a list of classes you are registered
for, including the one you just enrolled in.

13. Click the Begin Class button.

14. Your class page provides details on the availibilty of the lab station assigned to you, other
classmates enrolled and instructor contact information. To access your lab station, click the
Access <lab station> Now button.
15. If prompted, provide your login credentials.

16. From your equipment session, select the station tab that was assigned to you.
17. Click the server image.

18. Click the Begin Session button.
19. A warning will appear. Click Connect to launch a Remote Desktop session.
20. You are now connected to your remote lab station.
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.
NOTE
You are now connected to the lab environment. You may skip the Connect to the Brocade
RSL Environment section below.

Connecting to the Brocade RSL Environment

21. Using Internet Explorer, connect to the RSL website: rsl.brocade.com.
22. 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.
23. 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.
24. The Secure Application Manager used to control access to the RSL launches.

25. A link to your RSL station will be provided (shown below). Click the link to access your RSL
workstation.
26. The Remote Desktop Connection window will display, click Connect.
27. 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.

28. Select the username assigned by the instructor.
29. Enter the password assigned by the instructor.
30. 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

31. 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.
32. From the remote desktop, select Start > Log off Administrator and click OK. Please do not
choose Shutdown.
33. Click on Sign Out in the upper right corner.
34. 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 switches, you should see the following:
- 4 switches: B300 and B5100
- Zoning should is off/disabled
Credentials to access switches:

- User credentials for the B300 and B5100:
The login gives you access to the B300 and B5100 where you will see connectivity to a third
switch, B6510, that you will not access in this class.
Username: admin
Password: password
Revision 0512 CFA 200 15

Lab Environment
FIGURE 2 Lab Topology
16 Revision 0512 CFA 200

Fibre Channel Levels

35. 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
36. 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
37. 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
38. 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. 10:00:00:05:1e:02:a5:49=(Node) WWN; 20:07:00:05:1e:02:a5:49=Port WWN

Port Types
39. 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.
40. Login into the B300 using the following credentials:

Username: admin
Password: password
41. Type the portshow 8 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 8
portIndex: 8
portName: port8
portHealth: OFFLINE
Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x1 PRESENT U_PORT
LocalSwcFlags: 0x0
portType: 18.0
5.1=F_Port, 2=U_Port, 3=E_Port, 4=FL_Port, 5=F_Port

POD Port: Port is licensed

portState: 2 Offline
Protocol: FC
portPhys: 2 No_Module portScn: 0
port generation number: 0
state transition count: 0
portId: 010800
portIfId: 4302000f
portWwn: 20:08:00:05:1e:0a:83:6d
portWwn of device(s) connected:
Distance: normal
portSpeed: N8Gbps
LE domain: 0
FC Fastwrite: OFF
Interrupts: 0 Link_failure: 0 Frjt: 0
Unknown: 0 Loss_of_sync: 0 Fbsy: 0
Lli: 0 Loss_of_sig: 1
Proc_rqrd: 0 Protocol_err: 0
Timed_out: 0 Invalid_word: 0
Rx_flushed: 0 Invalid_crc: 0
Tx_unavail: 0 Delim_err: 0
Free_buffer: 0 Address_err: 0
Overrun: 0 Lr_in: 0
Suspended: 0 Lr_out: 0
Parity_err: 0 Ols_in: 0
2_parity_err: 0 Ols_out: 0
CMI_bus_err: 0
Port part of other ADs: No

42. Log into the B5100 using the following credentials:
Username: admin
Password: password
43. Type the portshow 8 command and review the output.
portIndex: 8
portName: port8
portHealth: OFFLINE
EX_Port Mode: Enabled

Fabric ID: 20
Front Phantom: state = Not OK Pref Dom ID: 160
Fabric params: R_A_TOV: 0 E_D_TOV: 0 PID fmt: auto
Authentication Type: None

Hash Algorithm: N/A

DH Group: N/A
Edge fabric's primary wwn: N/A
Edge fabric's version stamp: N/A
portDisableReason: Fabric ID oversubscribed

portCFlags: 0x0
portFlags: 0x4021 PRESENT U_PORT EX_PORT DISABLED LED
LocalSwcFlags: 0x0
portType: 17.0
portState: 2 Offline
Protocol: FC
portPhys: 6 In_Sync portScn: 2 Offline
portId: 020800
portIfId: 43020007
portWwn: 20:08:00:05:1e:7f:06:9c
Distance: normal
portSpeed: N8Gbps
LE domain: 0
FC Fastwrite: OFF
Overrun: 0 Lr_in: 9
CMI_bus_err: 0

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

45. The switch is using standard 24-bit addressing. Translate the hexadecimal area to decimal:7
010400
171700
011A00
1F241F
113F00
46. 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
2 Nx_Ports in the Fabric }
DEV2-ST01-B300:admin>
____________________________________________________________________
____________________________________________________________________
47. 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
____________________________________________________________________
____________________________________________________________________
48. From the B5100, type the nscamshow command. List the field that appears after the Permanent
Port Name field.10
49.
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
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.

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
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
Switch entry for 4

No entry is found!
____________________________________________________________________
50. From the B5100, type the nscamshow -t command. List the field that appears after the
Permanent Port Name field.
51.
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
Switch entry for 4

No entry is found!
ST01-B5100:admin>
____________________________________________________________________
- 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 chassis
Identify components of the DCX-4S chassis
DCX Feature Hunt

Use the diagrams below to identify the components in a DCX 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 Hardware Reference Manual.

DCX Port Side
1.
2.
3.

DCX non-Port Side

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

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.



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

- 4 switches: B300, B5100, and B6510
The B6510 has two logical switches, LS1 and LS2. Review Figure3 on page36 for lab
topology. You will not access the B6510 in the Module 5: Installing and Configuring
Switches lab.
- All ISLs should be up and running.
- Zoning should be off/disabled.
Credentials to access switches and RSL station:
- User credentials for Remote Desktop:
Username: Administrator (click Administrator icon)
Password: brcd
Username: admin
Password: password
- User credentials for Brocade Network Advisor:
Username: Administrator
Password: password

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:
# timeout 0
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
50:00:51:e7:f0:69:ce:0a "fcr_fd_5" (downstream)(Trunk mas
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.0.0a
Made on: Wed Jun 1 16:04:18 2011
Flash: Wed Nov 16 11:39:43 2011
BootProm: 1.0.9
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.0.0 or later

10. Enter the fabricshow command; how many domains are in the fabric?
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
>"DEV2-ST01-B300"
5: fffc05 50:00:51:e7:f0:69:ce:0a 0.0.0.0 0.0.0.0
"fcr_fd_5"
The Fabric has 2 switches
11. __________________6
Configuring and Verifying Basic Settings on the B5100

12. From the desktop open the Putty application and select the B5100, select Load, click Open.
13. Log in using the following credentials:
Username: admin
Password: password
14. 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. 2 (B300 and B5100)

15. Enter the switchshow command. Review the command output, and fill in the following
parameters:
DEV2-ST01-B5100:admin> switchshow
switchName: DEV2-ST01-B5100
switchType: 66.1
switchState: Online
switchMode: Native
switchDomain: 2
switchId: fffc02
switchWwn: 10:00:00:05:1e:7f:06:9c
zoning: OFF
switchBeacon: OFF
FC Router: ON
FC Router BB Fabric ID: 100
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 In_Sync FC Disabled (Fabric ID
oversubscribed)
9 9 020900 id N4 In_Sync FC Disabled
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 EX-Port
10:00:00:05:1e:0a:83:6d "DEV2-ST01-B300" (fabric id = 10 )(Trunk
master)
15 15 020f00 id N8 Online FC EX-Port (Trunk port,
master is Port 14 )
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
16. Entering the version command. What version is currently installed on your B5100?
Fabric OS: ____________________11
View Time for the Fabric

17. Continuing on the Telnet session of the B5100 switch, enter the date command to view the
current date and time.
18. 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
19. Record the current clock server setting on the B5100:
tsclockserver: ____________________
20. 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.0.0a 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

21. 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 that they both have the date of Tue Apr 10 11:15:37 Localtime 2012.
22. Set the fabric to synchronize to an external NTP server using the tsclockserver command on
the B300.
# tsclockserver 10.255.252.11
DEV2-ST01-B300:admin> tsclockserver 10.255.252.11

Updating Clock Server configuration...done.
Updated with the NTP servers
Although the command may be run on any switch in a fabric, enter this command on the B300
only.
23. 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: ____________________
24. 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: ____________________
25. 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.

26. 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.
# tstimezone -5
System Time Zone change will take effect at next reboot.
# 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.
27. 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.
28. From the B300, type the following command to restore the configuration back to default:
# 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.
29. Continuing with the Telnet session of your B300 and enter the following:
> motd --set "Unauthorized access is prohibited. Unauthorized users
must log off."
30. Type the following:
> bannerset You have successfully logged into the switch.
31. Type login to terminate your current session. Once you log in to the switch the new MOTD and
login banner are displayed.
32. To turn off MOTD, type motd --set "" at the command prompt.
33. 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.
34. 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

35. To view the licensed features on this switch, enter the licenseshow command.
DEV2-ST01-B5100:admin> licenseshow
c9SdQeRedATeRK:
Fabric license
bRyRc9RRzbci3Sd6:
Full Ports on Demand license - additional 16 port upgrade license
PWrGHFKXFHQ4EAMSPWNJFXXSfEYKY7C9BJ9MH:
Enhanced Group Management license
RR3rEXQKTXHHmR3gLYRgF3ttSXS7KM9rBJtSK:
8 Gig FC license
QDQfZS3QWaPmrSDHfrMRGXYFrffr3F9LB7tYN:
Extended Fabric license
Fabric Watch license
Performance Monitor license
Trunking license
Integrated Routing license
Adaptive Networking license
7aACCMPLDAfrRrFJXHZEGHS3FfLf9HAtB7LTA:
Server Application Optimization license
36. Record one or two licensed features here:
____________________________________________________________________
____________________________________________________________________
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.
37. 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.
____________________________________________________________________

38.
39. 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.
40. 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
41. 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:
# chassisname R01-ST02#-B300
DEV2-ST01-B5100:admin> chassisname R01-ST02-B300
b. Use the chassisname command on the B5100 switch and replace the name as follows:
# chassisname R01-ST02-B5100
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
Turn on Enhanced Change Tracking

Enhanced change tracking may be turned on to increase ability to audit and track changes within the
fabric.

42. Return to the open Telnet session of your B5100 and issue the errclear command to clear out
any existing messages in the error log.
DEV2-ST01-B5100:admin> errclear
43. Use the trackchangesshow command to verify the track changes status.
DEV2-ST01-B5100:admin> trackchangesshow
Track changes status: OFF
Track changes generate SNMP-TRAP: NO
44. Use the trackchangesset 1 command.
DEV2-ST01-B5100:admin> trackchangesset 1
Committing configuration...done.
45. Use the errshow -r command and look for informational TRCK messages.
DEV2-ST01-B5100:admin> errshow -r
Fabric OS: v7.0.0a
2012/04/16-06:28:39, [TRCK-1005], 2, FID 128, INFO, DEV2-ST01-B5100,

Track-changes on
Type <CR> to continue, Q<CR> to stop:
2012/04/16-06:27:27, [LOG-1003], 1, CHASSIS, INFO, DEV2-ST01-B5100,

The log has been cleared.
Type <CR> to continue, Q<CR> to stop:
Note
The errdump command is mostly used for scripts and supportshow output while the
errshow command is commonly used from the CLI as it paginates the output.
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.
46. Ensure that the Brocade Network Advisor services have been stopped:
a. On the desktop click Start > Programs > Network Advisor 11.1.0 > 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.
47. Follow these steps to start the syslog server (we are using Kiwi Syslog Daemon):

a. On the desktop launch the Kiwi Syslog Daemon program.

48. 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.
49. Determine the IP address of your RSL host server:
a. Click Start > Run
b. Type cmd and press ENTER.
c. From the command window run ipconfig and note the IP address:
____________________________________________________________________
Note
You can forward syslogd messages to up to six servers.
50. Return to the Telnet session of your B5100 and issue the syslogdipadd <IP address>
command. Use the IP address you obtained from Step49, Stepc. It is the IP address of your RSL
host.
51. 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.
52. Examine the entries in the Kiwi syslog daemon window.
53. 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.
54. Leave this configuration active through the remainder of this lab in order to observe the log
message that are created.
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
Checking switch status
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.
55. 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
56. Record the amount of time the switch has been operational. ____________________
57. 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
Checking Switch Status

You will display the overall status of the switch, look at policy settings, and look at temperature, fan,
and power supply status.
58. Return to the Telnet session of your B300 and issue the switchstatusshow command.
DEV2-ST01-B300:admin> switchstatusshow
Switch Health Report Report time: 04/16/2012
06:47:57 AM
Switch Name: DEV2-ST01-B300
IP address: 10.255.224.34
SwitchState: HEALTHY
Duration: 140:12
Power supplies monitor HEALTHY

Temperatures monitor HEALTHY
Fans monitor HEALTHY
Flash monitor HEALTHY
Marginal ports monitor HEALTHY

Faulty ports monitor HEALTHY

Missing SFPs monitor HEALTHY
Error ports monitor HEALTHY
All ports are healthy
59. Record the switch status here:
a. SwitchState ____________________
b. Power supplies monitor____________________
c. Temperatures monitor ____________________
d. Fans monitor ____________________
e. Flash monitor____________________
f. Marginal ports monitor ____________________
g. Faulty ports monitor ____________________
h. Missing SFPs monitor ____________________
60. Issue the switchstatuspolicyshow command to determine the percentage and the number
of ports needed to fault before the switch is reported as marginal and record that value:
DEV2-ST01-B300:admin> switchstatuspolicyshow
The current overall switch status policy parameters:
Down Marginal
----------------------------------
PowerSupplies 1 1
Temperatures 2 1
Fans 2 1
Flash 0 1
MarginalPorts 25.00%[6] 10.00%[2]
FaultyPorts 25.00%[6] 10.00%[2]
MissingSFPs 0.00%[0] 0.00%[0]
ErrorPorts 0.00%[0] 0.00%[0]
Number of ports: 24
_____________________________________________________________________13
61. Record the number/percentages of other out-of-spec measurements required to put the switch
into marginal status.14
a. PowerSupplies____________________
b. Temperatures ____________________
13.The marginal ports are 25% and down ports are 10%.
14. A setting of 0 indicates that Fabric OS will not monitor this component. For example having a setting of 0 for
MissingSFPs indicates that the switch will not complain if you remove SFPs. If you wish to have the switch
track this condition or others, use the switchstatuspolicyset command. Since output is user-configurable
it could vary.

c. Fans ____________________
d. Flash ____________________
e. MarginalPorts ____________________
f. MissingSFPs ____________________
Looking at Sensor Readings

You can display the current operational status of all switch sensors.
62. 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
63. 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.
64. From the Telnet session of your B300, issue the portshow 1 command.
portIndex: 1
portName: port1
portHealth: HEALTHY
portDisableReason: None
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

65. Review the output and record the following parameters15:

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.
66. From the Telnet session of your B300, issue the portcfgshow |more command.
67. 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.
# 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.
68. 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
15. B300 portshow outputs should display as follows portHealth: HEALTHY; portState: Online;
Distance: normal; portSpeed: N8Gbps; the other parameters will vary.

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.class.2:2
fabric.ops.vc.config:0xc0
fabric.ops.vc.linkCtrl:0
fabric.ops.vc.multicast:7
fabric.ops.wan_tov:0
69. Return to the Telnet session of your B5100 and issue the same command:
# configshow -pattern fabric.ops to look at the fabric.ops parameters.
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

70. Compare the fabric.ops parameters on both switches. Do any of the parameters differ?
______________________________________________________________________16
Check Point: You have learned to quickly assess general switch status. Fabric troubleshooting builds on
these introductory steps.
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.
71. Return to the open Telnet session of your B300 and issue the nsshow t -r command.
72. 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
Port Index: 0
Share Area: No
Redirect: No
Partial: No
16.The switches should be successfully merged into a single fabric so the fabric.ops parameters should be the
same.

N 010100; 3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00;
0x01000003
FC4s: FCP
Port Index: 1
Share Area: No
Redirect: No
Partial: No
WWPN ____________ Device Type _____________________ State Change Registration (Y/N) ___
73. Return to the open Telnet session of your B300 and issue the nsshow t -r command.
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
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
Port Index: 1
Share Area: No
Redirect: No
Partial: No
74. Verify that the storage devices are properly registered with the name server and fabric controller.
Record the last three octets of the Port WWN of the storage ports. Example: 52:3a:72.

75. 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
Switch entry for 4

No entry is found!
ST01-B5100:admin>
76. 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?17
____________________________________________________________________
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

77. Ensure that the Brocade Network Advisor services are running:
a. On the desktop click Start > Programs > Network Advisor 11.1.0 > Server Management
Console.
78. On the Services tab click the Start button
79. From the desktop open Brocade Network Advisor 11.1.0 application by double-clicking on the icon
80. Log in using the default credentials:
- Username: administrator
- Password: password
81. Select the SAN tab.
17.The nscamshow output does not have an SCR column, otherwise they are the same.

82. Click Discover > Fabrics
83. Click Add.
84. 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.

85. 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.

86. Click OK. This launches the discovery Add Operation.
87. Repeat Step83 through Step86 for the B300 and B6510.
- Did you have to go through the discovery process for the B300 or the B6510? Yes or No. If No,
why not?18
____________________________________________________________________
____________________________________________________________________
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.
88. Return to the Telnet session of your B300.
89. Issue the switchshow command, what is the switchWwn?19
ST01-B300:admin> switchshow
switchName: ST01-B300
switchType: 71.2
switchState: Online
switchMode: Native
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:05:1e:0a:83:6d
zoning: OFF
switchBeacon: OFF.......
____________________________________________________________________
18. No. Once the seed switch was discovered, any switch connected to the seed is discovered automatically.
19.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
90. Issue the command portshow 1, what is the portWwn and portWwn of device(s)
connected?20
...portId: 010100
portIfId: 43020015
portWwn: 20:01:00:05:1e:0a:83:6d
20:00:00:11:0d:0f:84:00...
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
Configuration Backup Using the CLI

91. 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.
20.This information is different for each switch and device connection.

Configuration Save (Backup) and Restore Using Network Advisor

92. From Brocade Network Advisor 11.1.0 application select the SAN tab.
93. Select the B5100 in the Switch Group.
94. Right-click, select Configuration > Save.
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.
95.
96. Select the B5100.

97. Click the right arrow to put the selected switch in the Selected Switches pane.
98. Click OK.
This initiates the save configuration process.
99. On the Network Advisor Message, click OK

100.In the Switch Group, select the B5100 .
101.Right-click on the B5100, select Configuration > Configuration Repository.

102.In the Switch Configurations Repository, select the backup file by clicking on the line, but do not
click on the Keep checkbox.
Note
Do not select the checkbox 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.

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

104.From the Saved Sessions, select B5100 - Console.
105.Click Load.
106.Click Open.
107.Hit Enter to activate the console.
108.Login in using the following credentials:
Username: admin
Password: password
109.Leave the B5100 Console session open to watch the progress on the B5100.
110.In Network Advisor, on the Switch Configuration Repository, click Restore.
111.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.
Configupload 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.
112.Click OK on the Network Advisor Message.

113.On the Switch Configuration Repository, click OK to close.
114.Close Brocade Network Advisor.
115.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

- 4 switches: B300, B5100, and B6510
topology.
- Zoning should be off/disabled
Username: admin
Password: password

Module 6: Firmware
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.0.0a
v7.0.0a
____________________________________________________________________
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.0.0a
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.0.0a
Made on: Wed Jun 1 16:04:18 2011
Flash: Wed Nov 16 10:39:43 2011
BootProm: 1.0.9
1.Wed Jun 1 22:04:18 2011

Module 6: Firmware
DEV2-ST01-B300:admin> firmwareshow
Appl Primary/Secondary Versions
------------------------------------------
FOS v7.0.0a
v7.0.0a
____________________________________________________________________
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 Documents\Firmware directory and select the v7.0.0a.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\Firmware directory and select the
v7.0.0a_releasenotes_v3.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.0.0a. 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.0.0a
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.
Important
When selecting the B6510 be sure to only select the one from your station.
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.0.0a.
29. Check the Overwrite current firmware check box

Module 6: Firmware
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.0.0a.
30. Verify that the Status column reports Ready for all switches.
31. Click the Download button.

Module 6: Firmware
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

____________________________________________________________________
35. Wait for about a minute, the Message column will change to show the current firmware download
status.
36. Move and resize the Firmware Management window so you can watch the Master Log on the main
Network Advisor window behind.
37. You can 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
____________________________________________________________________
38. After the firmware download completes on all switches, right-click one of the switches in the
Selected Switches list and click Show Detailed Message.
Note
This can be done at any time during the firmware download process to view the output of the
firmwaredownloadstatus command from the switch.
6.In Progress
7.User Action Event

Module 6: Firmware
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.

Module 6: Firmware

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)

- 4 switches: B300, B5100, and B6510
topology.
- Ensure that zoning is off/disabled
Username: admin
Password: password

Module 7: Zoning
Lab Environment

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 WWN, right-click 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. 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 that is connected to the B6510 and
the storage port is connected to the B300.
Note
You can switch back to the main Network Advisor screen and use the fabric map to deter-
mine which port WWN is connected to each switch.
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. Click Activate, the Activate Zone Configuration window displays.

25. After reviewing the zoning configuration for accuracy click OK, a Network Advisor Message window
displays.

Module 7: Zoning
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 Configure > FC Troubleshooting >
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 workdstation 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.

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

- 4 switches: B300, B5100, and B6510
topology.
- All ISLs should be up and running.
- Zoning should be on/enabled.
- Trunks should be up and running
Username: admin
Password: password
Username: administrator
Password: password
Password: brcd
Important
Your login credentials from the Lab Pairing Overview on page95 automatically gives you access to
the correct Logical Switch (LS).

Student Information
FIGURE 6 Lab topology
Important

Lab Pairing Overview

When you are asked to log into R#-ST#-B6510-LS1, R# refers to your RSL number, and ST# refers to
your station number. Use the following username and password associated with your station number.
- Odd numbered stations:
Username: adminOdd
Password: password
- Even numbered stations:
Username: adminEven
Password: password
This lab refers to R#-ST#-B6510-LS1 and R#-ST#-B6510-LS2. If you refer to the lab diagram, notice
that there is an even numbered station associated with an odd numbered station.
- If you are asked to log into R#-ST#-B6510-LS1, determine the number (#) for your RSL and
determine whether you have an odd or even station number. Then one of the following
applies:
Odd numbered stations: If you are asked to log into R#-ST#-B6510-LS2 then ST# is the
even numbered pair (i.e. R13-ST02-B6510-LS2)
Even numbered stations: If you are asked to log into R#-ST#-B6510-LS2 then ST# is the
odd numbered pair (i.e. R13-ST01-B6510-LS2)
RSL stations are divided into the following pairs:
- 01 and 02
- 03 and 04
- 05 and 06
- 07 and 08
Table 1 lists the station number, associated username and password, and the stations you can log
into.
TABLE 1 Station Information
Station Number Username Password Associated Stations
01 adminOdd password R#-ST01-B6510-LS1

R#-ST02-B6510-LS2
02 adminEven password R#-ST02-B6510-LS1
R#-ST01-B6510-LS2
R#-ST04-B6510-LS2
R#-ST03-B6510-LS2
R#-ST06-B6510-LS2
R#-ST05-B6510-LS2



R#-ST08-B6510-LS2
R#-ST07-B6510-LS2
Getting Started
This lab exercise verifies that the switches are using the default exchange-base routing.
1. Open Telnet sessions to the B5100 and R#-ST#-B6510-LS1 switches using Putty.
2. Ensure that Trunking and Extended Fabric licenses are installed on the B5100 and R#-ST#-
B6510-LS1 switches using the licenseshow command. Contact the instructor if this licenses
is missing from either switch.
ST01-B5100:admin> licenseshow
c9SdQeRedATeRK:
Fabric license
bRyRc9RRzbci:
PWrGHFKXFHQ4EAMSPWNJFXXSfEY:
RR3rEXQKTXHHmR3gLYRgF3ttSXS:
8 Gig FC license
QDQfZS3QWaPmrSDHfrMRGXYFrff:
Trunking license
7aACCMPLDAfrRrFJXHZEGHS3FfL:
ST01-B6510-LS1:FID1:admin> licenseshow
byeQeSczRdez:
byeQeSczRdgz:
byeQeSczRdkz:
Trunking license
byeQeSczRdcz:
SdScQQbyeyTe:
byeQeSczRdc1:
FICON_CUP license
byeQeSczRdcF:

gaaM7Ra3CREYNP9CEKg7HCJfWR:
B7BLSt4DYHLF7BGtGSW794DmSH:
3. Type the aptpolicy command on both the R#-ST#-B6510-LS1 and B5100 to verify this; the
output should display: Current Policy: 3.
ST01-B5100:admin> aptpolicy
Current Policy: 3 0(ap)
3 0(ap) : Default Policy

1: Port Based Routing Policy
3: Exchange Based Routing Policy
0: AP Shared Link Policy
1: AP Dedicated Link Policy
ST01-B6510-LS1:FID1:admin> aptpolicy
Current Policy: 3
3 : Default Policy
1: Port Based Routing Policy
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:
R13-ST07-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 R#-ST#-B6510-LS1
and R#-ST#-B6510-LS2 switches.
5. Type the portcfgshow command on both the R#-ST#B6510-LS1 and R#-ST#-B6510-LS2
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>
ST02-B6510-LS2:FID1:adminOdd> portcfgshow
1. Trunk Ports should display ON.

Ports of Slot 0 24 25 26 27 28 29 30 31
----------------------+---+---+---+---+-----+---+---+---
Octet Speed Combo 1 1 1 1 1 1 1 1
Speed AN AN AN AN AN AN AN AN
AL_PA Offset 13 .. .. .. .. .. .. .. ..
Trunk Port ON ON ON ON ON ON ON ON
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
7. Type the switchshow command from the R#-ST#-B6510-LS1 and use the output to answer
the following questions:
ST01-B6510-LS1:FID1:admin> switchshow
switchName:ST01-B6510-LS1
switchType:109.1
switchState:Online
switchMode:Native
switchRole:Subordinate
switchDomain:3
switchId:fffc03
switchWwn:10:00:00:05:33:93:69:40
zoning:ON (ConfigA)
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF
LS Attributes:[FID: 1, Base Switch: No, Default Switch: No, 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 Online FC E-Port 10:00:00:05:33:92:ea:67 "ST02-B6510-LS2"
(downstream)(Trunk master)
7 7 030700 id 4G Online FC E-Port 10:00:00:05:33:92:ea:67 "ST02-B6510-LS2"
(Trunk master)
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
<output truncated>
a. How many trunks exist?

_______________________________________________________________3
8. How can you determine which Trunk Master is the Principal ISL?
_______________________________________________________________4
2. The switchcfgtrunk 1 command will turn trunking ON for all switch ports.
3. There should be 2 trunks with 2 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.

9. List the criteria that needs to be met in order for ports to form a trunk:
_______________________________________________________________5
10. 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-LS1 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
11. Since some of the lab stations have differences, use the example islshow output below to
answer the following question. What do the 8 > 8 and 6 > 24 values tell you?
_______________________________________________________________7
ST01-B6510-LS1:FID1:adminOdd> islshow
1: 6-> 24 10:00:00:05:33:92:ea:67 4 ST02-B6510-LS2 sp: 16.000G bw: 32.000G TRUNK QOS
CR_RECOV FEC
2: 8-> 8 10:00:00:05:1e:7f:06:9c 2 ST01-B5100 sp: 8.000G bw: 16.000G TRUNK QOS
12. From the R#-ST#-B6510-LS1, type the trunkshow command and evaluate the deskew values.
ST01-B6510-LS1:FID1:adminOdd> trunkshow
1: 6-> 24 10:00:00:05:33:92:ea:67 4 deskew 51 MASTER
7-> 25 10:00:00:05:33:92:ea:67 4 deskew 15
2: 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: ___________________

13. What is greatest deskew difference in the following example trunkshow output?
_______________________________________________________________8
ST01-B5100:admin> trunkshow
1: 8-> 8 10:00:00:05:33:93:69:40 3 deskew 15 MASTER
9-> 9 10:00:00:05:33:93:69:40 3 deskew 15
2: 15-> 15 10:00:00:05:1e:0a:83:6d 1 deskew 15 MASTER

14-> 14 10:00:00:05:1e:0a:83:6d 1 deskew 15
14. 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?
_______________________________________________________________9
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.
8. The greatest deskew difference in the example shown is 0.
9. A deskew of 30 or more could cause additional latency.

CHECK POINT
You established that there are two 16 Gbps per port ISL trunks between the two B6510_St01 and St02
switches in your fabric.
15. Verify that port 6 is the trunk master. If it is not, issue the following commands:
portdisable 6
portdisable 7
portenable 6
portenable 7
Using Brocade Network Advisor to Configure Trunking

16. Open Brocade Network Advisor.
17. Logon as requested.
18. In the left-hand pane, select R#-ST#-B6510-LS1.
19. Right-click and go to Element Manager > Ports
20. Verify that there is at least one trunk group between the B300 and the B5100 (ports 14 and 15),
the B5100 and the B6510 (ports 8 and 9), and between two logical switches (B6510s; LS1
ports 6 and 7; LS2 ports 24 and 25) switches in your fabric.
The trunk groups should be between the following switches:
- B300 and the B5100 (ports 14 and 15)
- B5100 and the B6510 (ports 8 and 9)
- Between two logical switches (B6510s; LS1 ports 6 and 7; LS2 ports 24 and 25)
This lab focuses on the trunk between the two logical switches (LS1 and LS2)

Helpful Hint
The Network Advisor SAN tab has a Connectivity Toolbar located in the right pane of the SAN
tab which displays the trunk groups between the switches. You can mouse over a link which
is bolded when selected, right-click the link and select Properties to view the connection
properties.
21. Verify that the Trunk Master port in one of the Trunk Groups is port 6. This is used later.
Use the following steps to change the trunking configuration on the R#-ST#-B6510-LS1 using
Brocade Network Advisor:
a. Select port 7.
b. Click Edit Configuration.
c. A Confirmation dialog box will pop up, click Yes.
d. FC Port Configuration wizard: Click Next to get to step 2.
e. Specify FC Parameters: Use the Speed drop-down to change the speed of port 7 from Auto to 4G.

f. Click Next.
g. Click Save.
h. Click Close.
22. Re-evaluate the trunk configuration by clicking Refresh, located in the top right-hand corner of
the Port Administration window. If it refreshes too slowly, you can close and re-open the Port
Administration window.
CHECK POINT
The view of your switches should now have three trunk groups.
Use CLI to Evaluate the Current Trunking Configuration

23. Return to your open CLI session to your R#-ST#-B6510-LS1 (or re-open) and type the following:
ST01-B6510-LS1:adminOdd> trunkdebug 6 7
port 6 and port 7 speeds are not the same
24. Type trunkshow to verify that there are now 3 trunk groups.
1: 6-> 24 10:00:00:05:33:92:ea:67 4 deskew 15 MASTER

2: 7-> 25 10:00:00:05:33:92:ea:67 4 deskew 15 MASTER

9-> 9 10:00:00:05:1e:7f:06:9c 2 deskew 15
Why?
____________________________________________________________________10
25. Before completing the exercise port 7 should be set back to the default speed of 16 Gbps.
CHECK POINT
You created two trunk groups from one by changing the speed of 1 ISL in the trunk group. This created
two trunk groups with different speeds in the same ASIC port group. You used the trunkdebug com-
mand to analyze the message associated with why two trunks formed.
Restore the Trunk Configuration

Perform these steps on the following switches:
26. On the R#-ST#-B6510-LS1 run the following commands:
portcfgdefault 6
portcfgdefault 7
portcfgdefault 24
portcfgdefault 25
28. Type trunkshow and switchshow on both R#-ST#-B6510-LS1 and R#-ST#B6510-LS2 and to
verify that there is only one trunk group with no long distance parameters.
ST01-B6510-LS1:FID1:admin> switchshow
switchType:109.1
switchState:Online
switchMode:Native
switchDomain:3
switchId:fffc03
switchWwn:10:00:00:05:33:93:69:40
zoning:ON (ConfigA)
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF

==============================================
1 1 030100 -- N16 No_Module FC
10. Because the speed on ports 6 and 7 are not the same therefore they cannot form a trunk group.

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
10 10 030a00 -- N16 No_Module FC
<output truncated>
ST02-B6510-LS2:FID1:adminOdd> switchshow
switchType:109.1
switchState:Online
switchMode:Native
switchDomain:4
switchId:fffc04
switchWwn:10:00:00:05:33:92:ea:67
zoning:ON (ConfigA)
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF

==============================================
24 24 040000 id N16 Online FC E-Port 10:00:00:05:33:93:69:40 "ST01-B6510-LS1"
26 26 040200 -- N16 No_Module FC
<output truncated>
Helpful Hint
The portcfgdefault command was used to put the ports back into the original trunk
configuration (two 16 Gbps trunk groups with aggregate 32 Gbps bandwidths each).
Evaluate the Current B6510 Routing over Trunks Status

29. 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.)
30. Enter the following credentials:
Username: admin
Password: password
31. Click OK on the Seurity Banner dialog window to proceed to Web Tools.
32. From the Logical Switch drop-down menu located on the right-hand side, select Logical Switch 1.

33.
34. Under Manage in the left pane, click on Switch Admin.

35. Click Show Advanced Mode located in the upper right-hand corner, if necessary.
36. Click the Trunking tab and note the Trunk Master port for the 16 Gbps trunk.
a. ____11
37. Click the Routing tab and verify the two routes,(Out Ports), and reference the Trunk Master
noted above.
38. Also, note the In-ports are configured to use both available Trunk group routes. Explain why?
__________________________________________________________12
11. Master port should be 6..

12. Exchange-Based Routing provides this feature to use its load sharing mechanism.

NOTE
Note the configuration options that are available from the Web Tools Routing view.
39. Click Off located under the Dynamic Load Sharing (DLS) section.
40. Click Apply.
41. Click Yes on the Routing: Confirm Action dialog box. Why can this option not be turned
Off?_________________________________________________________________ 13
42. Is there an option in the Web Tools Routing view to change from the default exchange-based
routing to port-based routing?
_____________________________________________________________________14
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.
13. Exchange-Based Routing is turned on.

14. 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.

- 4 switches: B300, B5100, and B6510
topology.
- All ISLs should be online.
- Zoning should be on/enabled.
Username: admin
Password: password
Password: password
Password: brcd
This lab exercise covers tasks related to long distance parameters in Brocade fabrics.
- R#-ST#-B6510 where R# refers to your RSL station and ST# refers to the numbered station
(odd or even)
When logging into the switches, you need to use the following username and password associated
with your station number.
Odd numbered stations:
- Username: adminOdd
Even numbered stations:
- Username: adminEven

Student Information
Important

Lab Pairing Overview

Username: adminOdd
Password: password
Username: adminEven
Password: password
determine whether you have an odd or even station number. Then one of the following
applies:
- 01 and 02
- 03 and 04
- 05 and 06
- 07 and 08
into.

R#-ST02-B6510-LS2
R#-ST01-B6510-LS2
R#-ST04-B6510-LS2
R#-ST03-B6510-LS2
R#-ST06-B6510-LS2
R#-ST05-B6510-LS2



R#-ST08-B6510-LS2
R#-ST07-B6510-LS2
Getting Started
1. Open Telnet sessions to R#-ST#-B6510-LS1 and LS2 using Putty.
2. Type the licenseshow command and verify that both license keys are installed.
Verify that Trunking and Extended Fabric licenses are installed on your both of these switches.
Contact the instructor if either of these licenses are missing from either switch.
3. The first step is to verify that both switches are configured with default distance settings.
a. Type the portcfgshow command on both the R#-ST#-B6510-LS1 and R#-ST#-B6510-LS2
numbered stations. Verify that the Long Distance row display .. for all ports
indicating that long distance is disabled.
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 from
R#-ST#-B6510-LS1.
ST01-B6510-LS1:FID1:adminOdd> portbuffershow
User Port Lx Max/Resv Buffer Needed Link Remaining
Port Type Mode Buffers Usage Buffers Distance Buffers
---- ---- ---- ------- ------ ------- --------- ----------
0 F - 8 8 - -
1 - 8 0 - -
2 - 8 0 - -
3 - 8 0 - -
4 - 8 0 - -
5 - 8 0 - -
6 E - 8 34 34 <2km
7 E - 8 34 34 <2km
8 E - 8 34 34 <2km
9 E - 8 34 34 <2km 7556
<output truncated>

5. To enable LD mode on port 6 of the R#-ST#-B6510 with a desired distance of 25 km, issue the
following CLI command:
ST01-B6510-LS1:FID1:adminOdd> portcfglongdistance 6 ld 1 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 6.
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 R#-ST#-B6510-LS1, issue the switchshow command and answer these questions.
switchType:109.1
switchState:Online
switchMode:Native
switchDomain:3
switchId:fffc03
switchWwn:10:00:00:05:33:93:69:40
zoning:ON (ConfigA)
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF


==============================================
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 Online FC LD E-Port segmented,("No class F frames, Long
distance fabric or LD mode" incompatible)
10 10 030a00 -- N16 No_Module FC
<output truncated>
a. What is the status of port 6?
____________________________________________________________________1
b. What is the reason given for the status?
____________________________________________________________________2
8. From R#-ST#-B6510-LS2, issue the following command:
estimated.
Helpful Hint
You may need to disable/enable the port for the connection to come online, use the com-
mands portdisable and portenable.
9. From the R#-ST#-B6510-LS1, issue the switchshow command.

switchType:109.1
switchState:Online
switchMode:Native
switchDomain:3
switchId:fffc03
switchWwn:10:00:00:05:33:93:69:40
zoning:ON (ConfigA)
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF
1.Segmented
2. VC Link Init incompat


==============================================
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 Online FC LD E-Port 10:00:00:05:33:92:ea:67 "ST02-B6510-
LS2" (Trunk master)
10 10 030a00 -- N16 No_Module FC
<output truncated>
What is the status of port 6?

_______________________________________________________________3
10. From the R#-ST#-B6510-LS1, issue a trunkshow command.
1: 6-> 24 10:00:00:05:33:92:ea:67 4 deskew 15 MASTER
2: 7-> 25 10:00:00:05:33:92:ea:67 4 deskew 15 MASTER

9-> 9 10:00:00:05:1e:7f:06:9c 2 deskew 15
How many trunks are there? ____ 4

Why?
____________________________________________________________________ 5
11. From the R#-ST#-B6510-LS1, issue the following command:
estimated.
12. From the R#-ST#-B6510-LS2, issue the following command:
estimated.
13. From the R#-ST#-B6510-LS1, issue a trunkshow command.
1: 6-> 24 10:00:00:05:33:92:ea:67 4 deskew 50 MASTER
3. Online and operating normally

4. 3
5. The long distance settings at both ends of the link are the same

7-> 25 10:00:00:05:33:92:ea:67 4 deskew 15

9-> 9 10:00:00:05:1e:7f:06:9c 2 deskew 15
How many trunks are there? ____6

why?
____________________________________________________________________7
14. From the R#-ST#-B6510-LS1, issue the portbuffershow command.
---- ---- ---- ------- ------ ------- --------- ----------
0 F - 8 8 - -
1 - 8 0 - -
2 - 8 0 - -
3 - 8 0 - -
4 - 8 0 - -
5 - 8 0 - -
6 E LD 206 86 86 <2km
7 E LD 206 86 86 <2km
8 E - 8 34 34 <2km
9 E - 8 34 34 <2km
10 - 8 0 - -
11 - 8 0 - -
12 - 8 0 - -
13 - 8 0 - -
14 - 8 0 - -
15 - 8 0 - -
16 - 8 0 - -
17 - 8 0 - -
18 - 8 0 - -
19 - 8 0 - -
20 - 8 0 - -
21 - 8 0 - -
22 - 8 0 - -
23 - 8 0 - - 7212
15. Compare the portbuffershow output from Step14 with what was displayed in Step4.
a. How do ports 6 and 7 differ between the two outputs?
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________8
6. 2
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.

16. When you have finished this part of the lab perform the following actions:
a. R#-ST#-B6510-LS1: Type the portcfgdefault command on ports 6 and 7.
b. R#-ST#-B6510-LS2: Type the portcfgdefault command on port 24 and 25.
Configure Trunking Over Distance

Now that we have created trunks and long distance, lets put these two together to create a long
distance trunk. Follow these steps to create a long distance trunk over a pair of 16 Gbps ISLs.
17. From the R#-ST#-B6510-LS1, type the islshow command to identify the two ISL trunk groups.
Output from this command displays the following information:
ST01-B6510-LS1:FID1:adminOdd> islshow
1: 6-> 24 10:00:00:05:33:92:ea:67 4 ST02-B6510-LS2 sp: 16.000G bw: 32.000G TRUNK QOS
CR_RECOV FEC
2: 8-> 8 10:00:00:05:1e:7f:06:9c 2 ST01-B5100 sp: 8.000G bw: 16.000G TRUNK QOS
18. From the R#-ST#-B6510-LS1, type the trunkshow command to identify the ports associated
with this trunk group. This expected example output shows that ports 6 and 7 are associated
with trunk 1:
1: 6-> 24 10:00:00:05:33:92:ea:67 4 deskew 50 MASTER
7-> 25 10:00:00:05:33:92:ea:67 4 deskew 15

9-> 9 10:00:00:05:1e:7f:06:9c 2 deskew 15
19. Use CLI to configure one long distance trunk group on the R#-ST#-B6510-LS1.
a. Type portcfglongdistance 6 LS 1 25; you will receive a warning message:
Warning: Port may be reserving more credits depending on port
speed.
This is a reminder that each switch has specific amount of buffer credits associated with its
ASIC type. The following configuration will not exceed these limits if all steps are strictly
followed.
This will enable LS mode on port 6 and automatically turn VC Translation Link Init on.
20. On LS1, type the portcfgshow 6 command to verify configuration; below is an example
output:
ST01-B6510-LS1:FID1:adminOdd> portcfgshow 6
Area Number: 6
Octet Speed Combo: 1(16G|8G|4G|2G)
Speed Level: AUTO(SW)
AL_PA Offset 13: OFF
Trunk Port ON
Long Distance LS
VC Link Init ON
Desired Distance 25 Km
Reserved Buffers 206

Locked L_Port OFF

Locked G_Port OFF
Disabled E_Port OFF
Locked E_Port OFF
ISL R_RDY Mode OFF
RSCN Suppressed OFF
Persistent Disable OFF
LOS TOV enable OFF
NPIV capability ON
QOS E_Port OFF
Port Auto Disable: OFF
Rate Limit OFF

EX Port OFF
Mirror Port OFF
Credit Recovery ON
F_Port Buffers OFF
Fault Delay: 0(R_A_TOV)
NPIV PP Limit: 126
CSCTL mode: OFF
D-Port mode: OFF
Compression: OFF
Encryption: OFF
FEC: ON
21. On R#-ST#-B6510-LS1 type the following command to complete the long distance trunk group
configuration.:
ST01-B6510-LS1:FID1:adminOdd> portcfglongdistance 7 ls 1 25
Warning: port (7) may be reserving more credits depending on port
speed.
22. On R#-ST#-B6510-LS2 using port 24 and 25, type the following command to complete the long
distance trunk group at the other end of the link:
speed.
speed.
This enables LS mode on specified ports. Notice the switch response.
NOTE
There is segmentation due to the change on the other switch.
23. On R#-ST#-B6510-LS2 type switchshow and notice that the trunk group is now up and
running.

switchType:109.1
switchState:Online
switchMode:Native
switchDomain:4 (unconfirmed)
switchId:fffc04
switchWwn:10:00:00:05:33:92:ea:67
zoning:ON (ConfigA)
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF

==============================================
24 24 040000 id N16 Online FC LS E-Port (Trunk port, master is Port 25 )
25 25 040100 id N16 Online FC LS E-Port 10:00:00:05:33:93:69:40 ""
26 26 040200 -- N16 No_Module FC
<truncated output>
24. On R#-ST#-B6510-LS2, type portbuffershow to see the buffer credit allocation.
---- ---- ---- ------- ------ ------- --------- ----------
24 E LS 206 206 206 25km
25 E LS 206 206 206 25km
26 - 8 0 - -
<truncated output>
46 - 8 0 - -
47 - 8 0 - - 7212
25. Notice port 6 and 7 Needed Buffers and Buffer Usage columns show 206 buffers.
Why does the Max/Resv Buffers column show 206?
_____________________________________________________________________9
CHECK POINT
You used the CLI to configure two ports on each of the B6510s to long distance level LS. This allowed
you to create a 25 KM ISL trunk.
Restore the Trunk Configuration

Perform these steps on the B6510_St01 and St02 switches:
portcfgdefault 6
9. Max/Resv Buffers represents max number of credits needed to extend 25Km at full speed. Remember
the ports are running at 16 Gbps.

portcfgdefault 7
portcfgdefault 24
portcfgdefault 25
28. Type trunkshow and switchshow to verify that the trunk groups have no long distance
parameters.
R#-ST#-B6510-LS1
switchType:109.1
switchState:Online
switchMode:Native
switchDomain:3
switchId:fffc03
switchWwn:10:00:00:05:33:93:69:40
zoning:ON (ConfigA)
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF

==============================================
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
10 10 030a00 -- N16 No_Module FC
<output truncated>
1: 6-> 24 10:00:00:05:33:92:ea:67 4 deskew 50 MASTER
7-> 25 10:00:00:05:33:92:ea:67 4 deskew 15

9-> 9 10:00:00:05:1e:7f:06:9c 2 deskew 15
R#-ST#-B6510-LS2
switchType:109.1
switchState:Online
switchMode:Native
switchDomain:4
switchId:fffc04

switchWwn:10:00:00:05:33:92:ea:67
zoning:ON (ConfigA)
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF

==============================================
24 24 040000 id N16 Online FC E-Port 10:00:00:05:33:93:69:40 "ST01-B6510-LS1"
26 26 040200 -- N16 No_Module FC
<output truncated>
1: 24-> 6 10:00:00:05:33:93:69:40 3 deskew 51 MASTER
25-> 7 10:00:00:05:33:93:69:40 3 deskew 15
Helpful Hint
The portcfgdefault command was used to put the ports back into the original trunk
configuration (two 16 Gbps trunk groups with aggregate 32 Gbps bandwidths 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

- 4 switches: B300, B5100, and B6510
topology.
- All ISLs should be functional
- Server should be discovered
Username: admin
Password: password
Password: password
Password: brcd

Lab Environment

Lab Station Pairing Overview

NOTE
In this example, you will need access to two Brocade 6510 switches as shown in Lab Environment on
page124. The information below describes how two sets of students would complete this lab exercise.
The important point is you need access to two Brocade 6510 switches which are connected via an ISL.
NOTE
You must create user ids for both virtual fabrics. To create user IDs for the even and odd stations as
show in this lab guide, use these commands:
userconfig --add adminOdd -r admin -l 1 -h 1 -c user

username: adminOdd
admin role in FID 1
home FID 1
user role at Chassis level
userconfig --add adminEven -r admin -l 2 -h 2 -c user

username: adminEven
admin role in FID 2
home FID 2
user role at Chassis level
Username: adminOdd
Password: password
Username: adminEven
Password: password
determine whether you have an odd or even station number. Then one of the following applies:
- 01 and 02

into.

R#-ST02-B6510-LS2
R#-ST01-B6510-LS2
Run D_Port Test

In this section you use Brocade Network Advisor to test an ISL connection between the two B6510
switches.
1. On the desktop double-click the Network Advisor 11.1.0 icon to open.
b. Click on the Login button
Login: Administrator
Password: password
c. In the Network Advisor Login Banner, click OK.
d. In the Brocade Network Advisor application, select the SAN tab.
The fabric should already be discovered and fully functional.
2. From Network Advisor tool bar, select Configure > FC Troubleshooting > Diagnostic Port Test
a. Expand the B6510_LS1.
b. Click on port 6. (See screen shot below)
c. Click on the right arrow to add the port to the Selected Ports list.
d. Click Start.

e. A Diagnostic Port Test window opens, click OK to start the test once it is no longer grayed out.

The test takes about 2 minutes to run. The Diagnostic Port Test window displays the progress
of the test. Looking at the Status Details section provides details of the progress of the test.
When the test is completed the Status should be Success. See example below:
f. Based on the information in the status window, what is this port ready to be used for?
____________________________________________________________________1
g. Click Close to close the Diagnostic Port Test window.
Note
Because one of ISLs went offline for the D_Port test the connectivity map may display an
issue with the ISL connections between the two switches. See example screen shot below.
This issue will be resolved as the port will revert back from a D_Port to an E_Port.
1. A new ISL or a member of a trunk.

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.
3. 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.

4. 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. (See example below.)
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:
5. View the supportsave repository: From the Brocade Network Advisor main window click on
Monitor > Technical Support > View Repository
a. You should see four files:
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
See example below:
b. These logs can be E-mailed, FTPd, Saved to disk or Deleted.

Brocade Network Advisor Reports

In this section of the lab you will use Brocade Network Advisor to run report on the SAN.
6. 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? ____________2

d. How many ports are on B6510 Logical Switch 1? ____________3
e. Take a minute and review this report.
f. Expand out all the reports By time and click on the Fabric Ports Report_Administrator.
Report; this will open up the Fabric Ports Report.
g. Looking at the Switch Utilization, what is the "Number of Ports connected"? _____________4
h. Looking at the Switch Utilization, what is the "Number of Ports Free"? _____________5
2. 112
3. 24
4. 15
5. 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

7. On the desk double click on the PuTTY ICON.
8. Select the B300 and then click Open.
Login: admin
Password: password
9. Disable the switch using the switchdisable command.
R13-ST01-B300:admin> switchdisable
10. 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
11. Enable the switch using the switchenable command.
Downloading the B5100 Configuration File

12. On the desk double click on the PuTTY icon.
13. Select the B5100 and then click Open.
Login: admin
Password: password
14. Disable the switch using the switchdisable command.
R13-ST01-B5100:admin> switchdisable
15. 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
16. 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.


Although answers are supplied at the bottom of each page in the lab book, below are some helpful
work arounds and the answers to labs that require a bit more work.

If the nscamshow command does not display output use the following instructions to boot your HBA:
1. Open up your host. Refer to your Student Information Sheet for the IP address of your stations
host.
2. Click on the Administrator icon.
3. Login using the following credentials
Password: brcd
4. Open up Host Connectivity Manager
5. If you are prompted to login, use the following credentials:
Password: password
6. In the left pane you may see red triangles. You need to disable and re-enable the HBA to remove
the red triangels.
7. Right-click the Adapter.
8. Uncheck Enable Adapter .
9. Right-click Adapter.
10. Check Enable Adapter.


The following information provides answers to the Module 10: Troubleshooting.
B300
If you want to reset the B300 download the config_good_b300 which is a good config file and will
correct the switch behavior.
TABLE 1 B300 Problems and Solutions

Port Number Problem Solution
Switch wide Zoning zoneshow; defzone --show

Displays the contents of the zone
configuration and its member. To fix
a segmented fabric, you can either
make the zones the same by adding
and deleting members or disable
zoning, remove the effective zone
configuration, delete the defined
and then enable zoning letting the
zones propagate.
B5100
If you want to reset the B5100 download the config_good_b5100 which is a good config file and
will correct the switch behavior. If you have already downloaded the bad config file, you will need to
change the defzone access before downloading the good config file.
TABLE 2 B5100 Problems and Solutions
Switch wide Zoning zoneshow; defzone --show

Displays the contents of the zone
configuration and its member. To fix
a segmented fabric, you can either
make the zones the same by adding
and deleting members or disable
zoning, remove the effective zone
configuration, delete the defined
and then enable zoning letting the
zones propagate.
8 Speed portcfgspeed 8 0
This sets the specified ports speed
to autosensing.
Use switchshow and
portcfgshow to view the port
configurations.

TABLE 2 B5100 Problems and Solutions (Continued)

9 L_Port portcfglport 9 0
This changes a locked L_Port to
unlocked on the specified port.
Use switchshow and
configurations.
14 Disabled E_Port portcfgeport 14 1
This enables the E_Port capability
on the specified port.
Use switchshow and
configurations.


Lab Setup
This section covers the requirements for you to setup your own lab environment. In order for the labs
to work you will need to set up for an odd station and an even station; each odd and even station
makes one paired station.
NOTE
If you do not have access to an environment that matches what is described below, you will not be able to
complete all of the labs. Command line interface output is provided as well as screen captures of applications
like Brocade Network Advisor. You can use this lab guide as a reference and if you have access to compatible
lab environment, for performing the tasks listed in this lab guide.
Objectives
This section describes what is required to setup your own lab environment
List of Required Equipment

Your lab station has the following components:
A server with a Brocade 825 adapter installed for a standard network. You will need Brocade Host
Connectivity Manager, version 3.0 installed as well on the server.
Two Brocade 300s (or other supported FCR) switch (used as a backbone router)
- Required firmware: Fabric OS v7.0.0a
- Domain ID: 1
- Required licenses:
Second Ports on Demand license - additional 8 port upgrade license
Fabric license
Trunking license
First Ports on Demand license - additional 8 port upgrade license
8 Gig FC license
Two Brocade 5100s (or other supported FCR) switch

Lab Setup
- Domain ID: 2
Fabric license
8 Gig FC license
Trunking license
Two Brocade 6510s switches
Trunking license
Virtual Fabric Configuration
- Default switch
FID 128
No ports assigned
Insistent Domain ID is set
Domain ID 5
- Divide odd station B6510 into two separate logical switches
First logical switch: Ports 0-23; FID 1; Domain ID 3; Credentials: adminOdd/password
with access only to FID1
Second logical switch: Ports 24-47; FID 2; Domain ID 4; Credentials: adminOdd/
password access only to FID2
- Divide even station B6510 into two separate logical switches
First logical switch: Ports 0-23; FID 2: Domain ID 4; Credentials: adminOdd/password

Lab Setup
access only to FID2

Second logical switch: Ports 24-47; FID 1; Domain ID 3; Credentials: adminOdd/
password with access only to FID1
One FC storage device (we use SANBlaze but any FC storage device will work)
Two hosts (each with an Brocade 825 HBA)
Requires enterprise license to create distributed switches
Brocade Network Advisor 11.1.0 must be installed on the host server. For some lab tasks, the
Brocade Network Advisor, version 11.1.0 is required. If you do not have access to Brocade Network
Advisor, contact Brocade for a trial version. Screen captures are provided for the tasks which require
Brocade Network Advisor.
Optics
6 x 16 GbE
20 x 8 Gbps FC
Cables: 12 Optic cables

Lab Setup
Lab Port Map

Below are the port numbers connections.
TABLE 1 Port Mapping

From Device Port To Device Port
Host 0 B300 0
Host 1 B6510 0
B300 14 B5100 14
B300 15 B5100 15
B300 1 Storage
B5100 8 B6510 8
B5100 9 B6510 9
B6510 Station Odd 6 B6510 Station Even 24
B6510 Station Odd 7 B6510 Station Even 25
NOTE
The BNA Server is the host server where Brocade Network Advisor is installed. The Brocade 825
adapter is also installed on the host server. For some lab tasks, the Brocade Network Advisor, version
11.1.0 is required. If you do not have access to Brocade Network Advisor, contact Brocade for a trial
version. Screen captures are provided for the tasks which require Brocade Network Advisor.

Lab Setup
Lab Environment: Two Stations (Odd and Even) Configuration
FIGURE 1 Lab Environment with Both Stations

Lab Setup
Individual Lab Station Configuration
BNA
16Gbps
<16Gbps
Station1
BNAP1To
B6510P0 B6510_St2
BNAP0To
B300P0
LS2
B300 B5100
P14,15 P8,9 LS1 6510St1
to B5100 to
B300 B5100 P6,7
6510St1
P14,15 B6510_St1 to
P8,9
6510St2
P24,25
SANBlazeP0To
B300St1P1
SANBlaze
FIGURE 2 Individual Lab Station Configuration

Brocade BCFA 16 Gbps Training PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Brocade BCFA 16 Gbps Training PDF

Enviado por

Direitos autorais:

Formatos disponíveis

CFA 200

European Headquarters - Geneva, Switzerland

Asia Pacific Headquarters - Singapore

2012 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 0512 iii

Module 8: Routing and Trunking

iv Revision 0512 CFA 200

Module 9: Long Distance

Module 10: Troubleshooting

Appendix A: Cheat Sheet

CFA 200 Revision 0512 v

Revision 0512 CFP 300 1

Record Remote Lab Access Information

2 Revision 0512 CFP 300

Connecting to the ITTM Environment

FIGURE 1 ITTM login screen

Revision 0512 CFP 300 3

Enrolling in the Class

4 Revision 0512 CFP 300

Revision 0512 CFP 300 5

13. Click the Begin Class button.

6 Revision 0512 CFP 300

15. If prompted, provide your login credentials.

Revision 0512 CFP 300 7

17. Click the server image.

8 Revision 0512 CFP 300

18. Click the Begin Session button.

20. You are now connected to your remote lab station.

Revision 0512 CFP 300 9

Connecting to the Brocade RSL Environment

10 Revision 0512 CFP 300

Revision 0512 CFP 300 11

28. Select the username assigned by the instructor.

29. Enter the password assigned by the instructor.

12 Revision 0512 CFP 300

Close Open Sessions and Exit Remote Connection

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

34. Close the browser.

This ends the Remote Lab Access Instructions lab exercise.

Revision 0512 CFP 300 13

14 Revision 0512 CFP 300

Expected Start State

Credentials to access switches:

Revision 0512 CFA 200 15

FIGURE 2 Lab Topology

16 Revision 0512 CFA 200

Fibre Channel Levels

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

Revision 0512 CFA 200 17

Node and Port World-Wide Names

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

18 Revision 0512 CFA 200

40. Login into the B300 using the following credentials:

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

Revision 0512 CFA 200 19

POD Port: Port is licensed

Port part of other ADs: No

EX_Port Mode: Enabled

Authentication Type: None

20 Revision 0512 CFA 200