BASA 200 Brocade Associate SAN Administrator: Lab Guide

BASA 200
Brocade Associate SAN

Administrator
Lab Guide
Brocade University
Revision 0816
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
2016 Brocade Communications Systems, Inc. All Rights Reserved.
ADX, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, HyperEdge, ICX, MLX, MyBrocade,
OpenScript, The Effortless Network, VCS, VDX, Vplane, and Vyatta are registered trademarks, and Fabric
Vision and vADX are trademarks of Brocade Communications Systems, Inc., in the United States and/or in
other countries. Other brands, products, or service names mentioned may be trademarks of others.
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 0816
Contents
Remote Lab Access Instructions
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Record Remote Lab Access Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Connecting to the Brocade RSL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Module 3: Director FRU Identification

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
DCX Feature Hunt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
DCX8510-8 Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
DCX8510-8 non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
X6-4 Feature Hunt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
X6-4 Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
X6-4 non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Director Feature Hunt Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
DCX8510-8 Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
DCX8510-8 non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
X6-4 Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
X6-4 non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Module 4: Fibre Channel Theory

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Fibre Channel Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Classes of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Frame Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Node and Port World-Wide Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Port Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Well-Known Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
24-bit Device Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Module 5: Installing and Configuring Switches

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configure and Verify Basic Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Setting the Command Line Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring and Verifying Basic Settings on the G620_Edge . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuring and Verifying Basic Settings on the 6510_Edge . . . . . . . . . . . . . . . . . . . . . . . . . 29
View Time for the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Configuring an NTP Server for the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Change the Time Zone for Each Switch in the Fabric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Setting a Message of the Day and a Login Banner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Verify Licensed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
View the Switch Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
View the Chassis Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
BASA 200 Revision 0816 iii

Specify a Syslog Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Determining Switch Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Verifying Switch Uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Looking at Sensor Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Looking at Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Looking at the Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Examine Fabric Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Verify Device Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Verify that Devices have Successfully Logged into the Fabric. . . . . . . . . . . . . . . . . . . . . . . . . 42
Discovering the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Configuration Backup Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuration Save (Backup) and Restore Using Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . 49
Module 6: Firmware
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Upgrading Firmware from the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Upgrading Firmware Using Brocade Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Setting Up the Firmware Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
........................................................................... 61
Updating Switch Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Module 7: Zoning
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configuring Zoning in Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Setting the Default Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Creating and Activating a Regular Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Verifying Device Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Using Network Advisor to verify Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Lab Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Using Brocade Network Advisor to create a Peer Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Module 8: Routing and Trunking

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

Module 9: Long Distance
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Student Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Module 10a Lab: Using the MAPS CLI

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Connect to the RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Enabling MAPS on a Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Configuring Global MAPS Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Creating and Viewing Logical Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Creating Policies and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Enabling MAPS Policies and Testing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Viewing the MAPS CLI Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Viewing the Port Availability Monitor Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Module 10b Lab: Using MAPS With Network Advisor

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Connect to the RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Configuring the MAPS Network Advisor Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Configuring MAPS Using Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Configuring MAPS Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Managing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Creating Policies and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Viewing Port Violations on the Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Lab Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Module 11: Troubleshooting

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Capturing Technical Support Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Brocade Network Advisor Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Troubleshooting Switch Merge Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Downloading the 6510_Edge Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Troubleshooting Switch Merge Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Clear Link D_Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
BASA 200 Revision 0816 v

vi Revision 0816 BASA 200
Time Allocated: 10 Minutes
Use these steps to access a remote workstation when doing lab exercises using the remote lab. All lab
exercises start at the remote workstation. All devices in the remote lab are pre-connected.
Objectives
In this lab exercise, you will perform the tasks to connect and disconnect from the Brocade Remote
Solutions Lab (RSL). 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 0816 BASA 200 1

Record Remote Lab Access 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:
Station Number: Password:
2. You will be provided with a Student Information Sheet (SIS). The SIS may include all or some of
the following information:
A diagram of your remote environment
IP addresses for the switches and hosts in your environment
User names and passwords for all switches and hosts
FTP account and server information
3. Write your station number and password information on the SIS sheet provided by your
instructor.
Connecting to the Brocade RSL Environment

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

7. The Secure Application Manager launches. Select Allow.
8. You have successfully connected to your RSL workstation.

If you are unable to sign on to your workstation, notify the instructor immediately.
Close Open Sessions and Exit Remote Connection

9. If you are not doing another lab at this time, please close all open sessions.
a. From the rsl.brocade.com window, select Sign Out in the upper right corner.
10. Close the browser.

This ends the Remote Lab Access Instructions lab exercise.

In this lab you will label the major components of the Brocade Gen5 and Gen6 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 8510-8 chassis
Identify components of the X6-4 chassis
DCX Feature Hunt

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

DCX8510-8 Port Side
1.
2.
3.

DCX8510-8 non-Port Side
1.
2.
3.

X6-4 Feature Hunt

Use the diagrams below to identify the components in a X6-4 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 X6 Hardware Reference Manual.
X6-4 Port Side
1.
2.
3.

X6-4 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.
DCX8510-8 Port Side

1. FC16-48 port blade / slot 1
2. CR16 core routing blade / slot 5
3. CP8 control processor blade / slot 7
DCX8510-8 non-Port Side

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

1. CPX6 control processor blade / slot 1
2. FC32-48 port blade / slot 3
3. CR32-4 core routing blade slot 5
X6-4 non-Port Side

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

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

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

6510_Edge
Fabric OS: 8.0.1
Domain ID: 3
Switch/Chassis Name: RSL-STXX-6510
Fabric Wide
Default Zone: All access
Zoning: Cleared

Lab Environment

Fibre Channel Levels

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

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

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

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

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

Username: admin
Password: password
7. Type the portshow 1 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.
ST01-G620_Edge:FID128:admin> portshow 1
portIndex: 1
portName: port1
portHealth: HEALTHY
Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x20b03 PRESENT ACTIVE F_PORT G_PORT U_PORT
LOGICAL_ONLINE LOGIN NOELP ACCEPT FLOGI
LocalSwcFlags: 0x0
5.1=F_Port, 2=U_Port, 3=E_Port, 4=FL_Port, 5=F_Port

portType: 26.0
POD Port: Port is licensed
portState: 1 Online
Protocol: FC
portPhys: 6 In_Sync portScn: 32 F_Port
port generation number: 12
state transition count: 3
portId: 010100
portIfId: 4302003d
portWwn: 20:01:c4:f5:7c:0e:d4:d8
portWwn of device(s) connected:
20:00:00:11:0d:0f:84:00
Distance: normal
portSpeed: N8Gbps
FEC: Inactive
Credit Recovery: Inactive
Aoq: Inactive
FAA: Inactive
F_Trunk: Inactive
LE domain: 0
Peer beacon: Off
FC Fastwrite: OFF
Interrupts: 0 Link_failure: 0 Frjt: 0
Unknown: 0 Loss_of_sync: 0 Fbsy: 0
Lli: 24 Loss_of_sig: 0
Proc_rqrd: 107 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: 3
Suspended: 0 Lr_out: 0
Parity_err: 0 Ols_in: 0
2_parity_err: 0 Ols_out: 3
CMI_bus_err: 0
Port part of other ADs: No

8. Log into the G620_Core using the following credentials:
Username: admin
Password: password
9. Type the portshow 8 command and review the output.
ST01-G620_Core:FID128:admin> portshow 8
portIndex: 8
portName: G620_Core.E_PORT.8.
portHealth: HEALTHY

portCFlags: 0x1
portFlags: 0x4903 PRESENT ACTIVE E_PORT T_PORT G_PORT U_PORT
LOGICAL_ONLINE LOGIN LED
LocalSwcFlags: 0x0
portType: 26.0
portState: 1 Online
Protocol: FC
portPhys: 6 In_Sync portScn: 128 T_Port Trunk port Flow
control mode 4
portId: 010800
portIfId: 43020035
portWwn: 20:08:c4:f5:7c:0e:c0:7c
Distance: normal
portSpeed: N16Gbps
FEC: Active
Credit Recovery: Active
LE domain: 0
Peer beacon: Off
FC Fastwrite: OFF
Overrun: 0 Lr_in: 0
CMI_bus_err: 0

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

11. The switch is using standard 24-bit addressing. Translate the hexadecimal area to decimal:7
010400
171700
011A00
1F241F
113F00
12. From the G620_Edge, type the nsallshow command to display a list of every PID logged into the
fabric.
ST01-G620_Edge:FID128:admin> nsallshow
{
010100 030000
2 Nx_Ports in the Fabric }
____________________________________________________________________
____________________________________________________________________
13. From the G620_Edge type the nsshow command. What type of information can you see?8
ST01-G620_Edge:FID128:admin> nsshow
{
Type Pid COS PortName NodeName
TTL(sec)
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"
Fabric Port Name: 20:01:c4:f5:7c:0e:d4:d8
Permanent Port Name: 20:00:00:11:0d:0f:84:00
Port Index: 1
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.

Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
LSAN: No
Device link speed: 8G
The Local Name Server has 1 entries }
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
- What is the main difference between the nsallshow and the nsshow commands?9
____________________________________________________________________
____________________________________________________________________
14. From the G620_Core, type the nscamshow command. List the field that appears after the
Permanent Port Name field.10
ST01-G620_Core:FID128: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
Fabric Port Name: 20:01:00:05:1e:0a:83:6d
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
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
9.The nsshow command displays the local NS database. The nsallshow command displays the fabric addresses for
the fabric.
10.Port Index: 1 and Port Index: 0

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

Port Index: 0
Share Area: No
Redirect: No
Partial: No
____________________________________________________________________
15. From the G620_Core, type the nscamshow -t command. List the field that appears after the
Permanent Port Name field.
ST01-G620_Core:FID128:admin> nscamshow -t
Switch entry for 2
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
Device Link speed: 8G
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
Windows Server (R) 2008 Standard | Service Pack
1"
NodeSymb: [40] "Brocade-825 | 3.2.3.0 | DEV2-ST01-HBA | "
Fabric Port Name: 20:00:00:05:33:93:69:3f
Device type: Physical Initiator
Port Index: 0
Share Area: No
Redirect: No
Partial: No

16. What is the main difference between the nscamshow and nscamshow -t commands?11
____________________________________________________________________
This ends Module 4: Fibre Channel Theory.
11.The nscamshow -t displays the device type.

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

When accessing the switches, you should see the following:
G620_Edge
Fabric OS: 8.0.1
Domain ID: 1
Ports Disabled: 0
G620_Core
Fabric OS: 8.0.1
Domain ID: 2

6510_Edge
Fabric OS: 8.0.1
Domain ID: 3
Fabric Wide
Zoning: Cleared

Lab Environment
Configure and Verify Basic Parameters

This activity focuses on the initial setup and configuration of a Brocade switch. This activity consists of
the following tasks:
Setting the command line session timeout
Configure and verify basic settings on the G620_Edge
Configure and verify basic settings on the 6510_Edge
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 G620_Edge, 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.
ST01-G620_Edge:FID128:admin> timeout
Current IDLE Timeout is 10 minutes
4. Use the timeout command to set the timeout value to 0 minutes. This prevents your session
from closing when you are idle. Then you will be prompted to re-login to the switch.
ST01-G620_Edge:FID128:admin> timeout 0
IDLE Timeout Changed to 0 minutes
The modified IDLE Timeout will be in effect after NEXT login
ST01-G620_Edge login: admin

Password:
Place Security Banner Here
ST01-G620_Edge:FID128: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 G620_Edge

6. Display the current Ethernet settings using the ethif --show eth0 command. Record the
results here:
ST01-G620_Edge:FID128:admin> ethif --show eth0
eth0 interface:
Link mode: negotiated 1000baseT-FD, link ok

MAC Address: C4:F5:7C:0E:D4:D8
eth0 Link encap:Ethernet HWaddr C4:F5:7C:0E:D4:D8

inet addr:10.255.224.37 Bcast:10.255.224.63 Mask:255.255.255.192
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:748643 errors:0 dropped:0 overruns:0 frame:0
TX packets:535084 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
Memory:fe4e2000-fe4e2fff
Link mode: ____________________

Number of TX & RX errors: ____________________
7. Display the current IP address settings using the ipaddrshow command. Record the settings
here:
ST01-G620_Edge:FID128: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:
ST01-G620_Edge:FID128:admin> switchshow
switchName: ST01-G620_Edge
switchType: 162
switchState: Online
switchMode: Native
switchRole: Principal
switchDomain: 1

switchId: fffc01
switchWwn: 10:00:c4:f5:7c:0e:c0:7c
zoning: OFF
switchBeacon: OFF
Index Port Address Media Speed State Proto

==============================================
0 0 010000 id N8 No_Sync FC Disabled
(Persistent)
1 1 010100 id N8 Online FC F-Port 20:00:00:11:0d:0f:84:00
2 2 010200 -- N32 No_Module FC (POD license not assigned or reserved yet)
10 10 010a00 -- N32 No_Module FC (POD license not assigned or reserved yet)
11 11 010b00 -- N32 No_Module FC (POD license not assigned or reserved yet)
12 12 010c00 -- N32 No_Module FC (POD license not assigned or reserved yet)
13 13 010d00 -- N32 No_Module FC (POD license not assigned or reserved yet)
14 14 010e00 id N32 Online FC E-Port 10:00:00:05:1e:0b:63:0c "R15-ST02-G620_Core" (downstream)(Trunk
master)
15 15 010f00 id N32 Online FC E-Port(Trunk port, master is Port 14 )
<<truncated output>>
switchName:____________________
switchType:____________________1
switchRole:____________________2
switchDomain:__________________3
zoning: ____________________4
1. Switch type for G620 is 162

2. Principal or Subordinate
3. 1
4. Zoning should be OFF

9. Enter the version command; what is the FOS version running on the switch?
ST01-G620_Edge:FID128:admin> version
Kernel: 2.6.14.2
Fabric OS: v8.0.1
Made on: Sat May 19 00:15:12 2016
Flash: Mon May 25 06:55:26 2016
BootProm: 2.0.25
Fabric OS: __________________5

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

11. From the desktop open the Putty application and select the 6510_Edge, select Load, click Open.
Username: admin
Password: password
13. From the Telnet session of your 6510_Edge, display the current IP address settings using the
ipaddrshow command. Record the settings here:
ST01-6510_Edge:FID128:admin> ipaddrshow
SWITCH
Ethernet IP Address: 10.255.224.36
Ethernet Subnetmask: 255.255.255.192
Gateway IP Address: 10.255.224.62
DHCP: Off
ST01-6510_Edge:admin>
Ethernet IP Address:____________________
Ethernet Subnetmask:____________________
Gateway IP Address:____________________
DHCP: ____________________
5. Fabric OS v8.0.1 or later

6. 3

14. Enter the switchshow command. Review the command output, and fill in the following
parameters:
ST01-6510_Edge:FID128:admin> switchshow
switchName: ST01-6510_Edge
switchType: 109.1
switchState: Online
switchMode: Native
switchRole: Subordinate
switchDomain: 3
switchId: fffc03
switchWwn: 10:00:00:05:1e:7f:06:9c
zoning: OFF
switchBeacon: OFF
FC Router: OFF
HIF Mode: OFF
Allow XISL Use: OFF
LS Attributes: [FID: 128, Base Switch: No, Default Switch: Yes,
Address Mode 0]

==================================================
0 0 030000 -- 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 -- N16 No_Module FC
7 7 030700 -- N16 No_Module FC
8 8 030800 id N16 Online FC E-Port
10:00:00:05:33:93:69:3f "ST01-G620_Core" (downstream)(Trunk master)
9 9 030900 id N16 Online FC E-Port (Trunk port,
master is Port 8 )
10 10 030a00 -- N16 No_Module FC
11 11 030b00 -- N16 No_Module FC
12 12 030c00 -- N16 No_Module FC
13 13 030d00 -- N16 No_Module FC
14 14 030e00 -- N16 No_Module FC
15 15 030f00 -- N16 No_Module FC
17 17 031100 -- N16 No_Module FC
18 18 031200 -- N16 No_Module FC
19 19 031300 -- N16 No_Module FC
20 20 031400 -- N16 No_Module FC
21 21 031500 -- N16 No_Module FC
22 22 031600 -- N16 No_Module FC
23 23 031700 -- N16 No_Module FC
24 24 031800 -- N16 No_Module FC
25 25 031900 -- N16 No_Module FC
26 26 031a00 -- N16 No_Module FC
27 27 031b00 -- N16 No_Module FC

28 28 031c00 -- N16 No_Module FC

29 29 031d00 -- N16 No_Module FC
30 30 031e00 -- N16 No_Module FC
31 31 031f00 -- N16 No_Module FC
32 32 032000 -- N16 No_Module FC
33 33 032100 -- N16 No_Module FC
34 34 032200 -- N16 No_Module FC
35 35 032300 -- N16 No_Module FC
36 36 032400 -- N16 No_Module FC
37 37 032500 -- N16 No_Module FC
38 38 032600 -- N16 No_Module FC
39 39 032700 -- N16 No_Module FC
40 40 032800 -- N16 No_Module FC
41 41 032900 -- N16 No_Module FC
42 42 032a00 -- N16 No_Module FC
43 43 032b00 -- N16 No_Module FC
44 44 032c00 -- N16 No_Module FC
45 45 032d00 -- N16 No_Module FC
46 46 032e00 -- N16 No_Module FC
switchName:____________________
switchType:____________________7
switchRole:____________________8
switchDomain:____________________9
zoning: ____________________10
15. Entering the version command. What version is currently installed on your 6510_Edge?
Fabric OS: ____________________11
7. Switch type of 6510 is 109.1

8. Principal or Subordinate
9. 3
10. Zoning should be OFF
11. v8.0.1 or later

View Time for the Fabric

16. Continuing on the Telnet session of the 6510_Edge switch, enter the date command to view the
current date and time.
17. Enter tsclockserver to determine the current source of date and time synchronization.12
ST01-6510_Edge:FID128:admin> tsclockserver
Active NTP Server 10.255.252.50
Configured NTP Server List 10.255.252.50
ST01-6510_Edge:FID128:admin>
18. Record the current clock server setting on the 6510_Edge:
tsclockserver: ____________________
19. On the G620_Edge, change the tsclockserver setting to LOCL, if it is not already, by running the
tsclockserver LOCL command.
Configuring an NTP Server for the Fabric

20. From the G620_Edge, run the date 0223123016 command to change the date and time.
a. Issue the date command from both the G620_ Edge and the 6510_Edge.
b. Verify the G620_ Edge has the date of Tue Feb 23 12:30 Localtime 2016.
21. Set the fabric to synchronize to an external NTP server using the tsclockserver command on
the G620_ Edge. Although the command may be run on any switch in a fabric, enter this command
on the G620_ Edge only.
ST01-G620_Edge:FID128:admin> tsclockserver 10.255.252.11
Updating Clock Server configuration...done.
Updated with the NTP servers
22. Record the new clock server and date settings on the G620_ Edge
ST01-G620_Edge:FID128:admin> date
Tue Apr 10 11:15:37 Localtime 2016
ST01-G620_Edge:admin>
tsclockserver: ____________________
date: ____________________
23. Record the new clock server and date settings on the 6510_Edge:
ST01-6510_Edge:FID128:admin> date
Tue Apr 10 11:14:34 Localtime 2016
tsclockserver: ____________________
date: ____________________
24. Verify that the time is in sync (both dates should match). It may take up to two minutes for the
time to synchronize.
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.

Change the Time Zone for Each Switch in the Fabric

Switches participating in a fabric may be in different time zones. For logging and reporting, it may be
advantageous to leave all switches in the default UTC time zone, however it is possible to have
switches report events in their local time with the tstimezone command.
For example, the Eastern time zone in the United States is offset from GMT by -5 hours, so the
tstimezone -5 command would correctly set the time zone for a switch in the Eastern United
States. You can also run the tstimezone --interactive command to choose the correct time
zone from a menu.
25. Use the tstimezone command to set the time zone of your G620_Edge to the Eastern time zone
in the United States (GMT -5) and verify same.
ST01-G620_Edge:FID128:admin> tstimezone -5
System Time Zone change will take effect at next reboot.
ST01-B300:FID128:admin> tstimezone
Time Zone Hour Offset: -5
Time Zone Minute Offset: 0
Note
If the tstimezone command does not work, use the tstimezone --old 0 command
and then use the tstimezone -5 command. This may require a reboot.
26. Type the date command on each switch to verify that the date on the G620_Edge is 5 hours
earlier than the date on 6510_Edge. If the dates do not differ by 2 hours then type fastboot on
the G620_Edge log in and check the dates again.
27. From the G620_Edge type the following command to restore the configuration back to default:
ST01-G620_Edge:FID128:admin> tstimezone -7
System Time Zone change will take effect at next reboot.
Setting a Message of the Day and a Login Banner

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

Verify Licensed Features

In addition to basic switch functionality, each switch may have optional licensed features enabled.
33. Return to the Telnet session of your G620_Edge and type licenseidshow. Switch license keys
are generated for a specific switch WWN.
ST01-G620_Edge:FID128:admin> licenseidshow
10:00:c4:f5:7c:0e:be:fc
34. To view the licensed features on this switch, enter the licenseshow command.
DEV2-ST01-_Edge:G620admin> licenseshow
tKfKP73FKHLm4LMYA4AQBG74a9SM97YH4gJMXLEABPFA:
Ports on Demand license
Capacity 24
WKT4JAHt3mHXJKLLHAHLRHEPFLFGDFRRB779N:
Integrated Routing license
4YEGgP9KFKWAStZt3WrCEgWZK4REYXZrZ4LLQLGAGAWA:
Q-Flex Ports on Demand license
Capacity 16
tKfKP7GFKHLmtQLYA4AGDG74a9SM97YCBJLrK:
Extended Fabric license
Trunking license
FICON_CUP license
Fabric Vision and IO Insight licensee
Note
Notice that one or more features may be activated with a single license key.

View the Switch Name

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

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

Specify a Syslog Server

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

46. Check to see if the messages were recorded in the syslog file; to do this do the following:
a. Click Start > Run
b. Type c:\captures and press ENTER.
c. Open the basa200_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: syslogadmin --show -ip and verify the IP address is set
correctly.
Verify that the Network Advisor services are not running.
47. When you are finished close the Kiwi Syslog server.
Check Point: You have configured and verified basic settings on the switches in your fabric. Some of
these steps are not required for essential switch operation; however these basic steps will make SAN
administration easier and more consistent as your fabric grows.
Determining Switch Status

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

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

Looking at Sensor Readings

You can display the current operational status of all switch sensors.
51. From the Telnet session of your G620_Edge, issue the sensorshow command.
ST01-G620_Edge:FID128:admin> sensorshow
sensor 1: (Temperature) is Ok, value is 40 C
sensor 8: (Fan ) is Ok,speed is 8239 RPM
sensor 9: (Fan ) is Ok,speed is 8141 RPM
sensor 10: (Power Supply) is Ok
sensor 11: (Power Supply) is Ok
NOTE
If one of the Power Supplies is reported Faulty this is because it is not connected to a power source.
52. Verify that the sensors all display an OK status.

Alternatively, the tempshow, fanshow, and psshow commands will display the status of individual
components. The output of these commands is shown below:
ST01-G620_Edge:FID128:admin> tempshow
Sensor Sensor State Centigrade Fahrenheit
ID Index
==========================================================
1 0 Ok 40 104
2 1 Ok 50 122
3 2 Ok 45 113
4 3 Ok 43 109
5 4 Ok 43 109
6 5 Ok 39 102
7 6 Ok 65 149
ST01-G620_Edge:FID128:admin> fanshow
Fan 1 is Ok, speed is 8341 RPM
Fan 2 is Ok, speed is 8239 RPM
ST01-G620_Edge:FID128:admin> psshow
Power Supply #1 is faulty
Power Supply #2 is OK

Looking at Port Status

We will now observe the status of ports on the switch.
53. From the Telnet session of your G620_Edge, issue the portshow 1 command.
ST01-G620_Edge:FID128:admin> portshow 1
portIndex: 1
portName: port1
portHealth: HEALTHY
portCFlags: 0x1
portFlags: 0x20b03 PRESENT ACTIVE F_PORT G_PORT U_PORT
LOGICAL_ONLINE LOGIN NOELP ACCEPT
LocalSwcFlags: 0x0
portType: 26.0
portState: 1 Online
Protocol: FC
portPhys: 6 In_Sync portScn: 32 F_Port
portId: 020100
portIfId: 4302003d
20:00:00:11:0d:0f:84:00
Distance: normal
portSpeed: N8Gbps
FEC: Active
Credit Recovery: Inactive
Aoq: Inactive
FAA: Inactive
F_Trunk: Inactive
LE domain: 0
Peer beacon: Off
FC Fastwrite: OFF
Overrun: 0 Lr_in: 0

CMI_bus_err: 0
54. Review the output and record the following parameters13:

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

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

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

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

Verify Device Connection

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

As new devices are added to a fabric configuration, it is important to have the ability to gather basic
information and status regarding the newly-added devices.
60. Return to the open Telnet session of your G620_Edge and issue the nsshow t -r command.
61. Verify that the storage 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: 0f:84:00.
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 storage device.
ST01-G620_Edge:FID128:admin> nsshow -t -r
{
SCR
N 010100; 3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00;
0x01000003
FC4s: FCP
Device type: Physical Target
Port Index: 1
Share Area: No
Redirect: No
Partial: No
LSAN: No
Device link speed: 8G
The Local Name Server has 1 entry }
WWPN ____________ Device Type _____________________ State Change Registration (Y/N) ___
62. From open G620_Core Telnet session issue the nscamshow command to see detailed information
about the devices on your G620_Edge switch and all remote switches.
ST01-G620_Core:FID128:admin> nscamshow
Switch entry for 2


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
Windows Server (R) 2008 Standard | Service Pack
1"
NodeSymb: [40] "Brocade-825 | 3.2.3.0 | DEV2-ST01-HBA | "
Fabric Port Name: 20:00:00:05:33:93:69:3f
Port Index: 0
Share Area: No
Redirect: No
Partial: No
63. Compare the last three octets of the Port WWN of the storage device output gathered from the
G620_Core nscamshow output with the G620_Edge nsshow output values gathered earlier. Are
they the same?15
____________________________________________________________________
Check Point: You have learned how to determine if a SAN attached device, such as host, storage, or
tape device, has successfully logged into the fabric.
15.The nscamshow output does not have an SCR column, otherwise they are the same.

Discovering the Fabric

64. Ensure that the Brocade Network Advisor services are running:
NOTE
You will need to make sure that the Kiwi syslog server is completely shut down before enabling the
Network Advisor services.
a. On the desktop click Start > Programs > Network Advisor 14.0.1> Server Management
Console.
65. On the Services tab click the Start button and confirm that the services have started.
66. From the desktop open Brocade Network Advisor 14.0.1 application by double-clicking on the icon
67. Log in using the default credentials:
- Username: administrator
- Password: password
68. Select the SAN tab.
69. Click Discover > Fabrics

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

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

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

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

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

Configuration Save (Backup) and Restore Using Network Advisor

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

84. In the Switch Group, select the 6510_Edge .
85. Right-click on the 6510_Edge, select Configuration > Configuration File Manager .
86. In the Configuration File Manager and Switch Configuration tab, select the backup file by clicking
on the line, but do not click on the Keep and Baseline check boxes.
Note
The Keep checkbox is selected to keep the configuration max past the defined age limit.
87. On the Desktop, double-click the Putty icon to open.

88. From the Saved Sessions, connect to the 6510_Edge - Console.
89. Hit Enter to activate the console.
90. Login in using the following credentials:

Username: admin
Password: password
91. Leave the 6510_Edge Console session open to watch the progress on the 6510_Edge.
92. In Network Advisor, on the Configuration File Manager click Restore. A Network Advisor Message
window will display.
93. Read the message and click Yes.
94. Watch the messages appear in the 6510_Edge Console. You should see messages similar to the
following:
2011/11/17-13:38:41, [FCR-1068], 1082, FID 128, INFO, R14-ST08-

6510_Edge, The FC Routing service is disabled.
2016/05/25-19:38:30, [SEC-1197], 981, FID 128, INFO, 6510_Edge,

Changed account root.
The following message tells us that MAPS has been enabled with the default policy name
dflt_aggressive_policy. There is one power supply now connected therefore this switchs status
is now reported as MARGINAL
2016/05/25-19:38:44, [FV-1002], 982, FID 128, INFO, 6510_Edge, Flow

Vision Config Replay Completed Successfully.
2016/05/25-19:38:46, [MAPS-1113], 983, FID 128, INFO, 6510_Edge,

Policy dflt_aggressive_policy activated.
2016/05/25-19:38:46, [MAPS-1021], 984, FID 128, WARNING, 6510_Edge,

RuleName=defCHASSISBAD_PWR_MARG, Condition=CHASSIS(BAD_PWR>=1),
Obj:Chassis [ BAD_PWR,1] has contributed to switch status MARGINAL.
2016/05/25-19:38:46, [MAPS-1020], 985, FID 128, WARNING, 6510_Edge,

Switch wide status has changed from HEALTHY to MARGINAL.
The following message tells us that the configuration restore completed successfully. The
configupload command is to save the switch configuration file and configdownload
restores the switch configuration file.
2011/11/17-13:38:56, [CONF-1000], 1085, FID 128, INFO, R14-ST08-
6510_Edge, configDownload completed successfully for all.
95. Once the configuration upload is completed another Network Advisor Message will display. Read
the message and click OK.
96. On the Configuration File Manager click OK to close.
97. Close Brocade Network Advisor.
98. Close all Putty sessions.

This ends Module 5: Installing and Configuring Switches.

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

G620_Edge
Fabric OS: 8.0.1
Domain ID: 1
Ports Disabled: 0
G620_Core
Fabric OS: 8.0.1
Domain ID: 2

Module 6: Firmware
6510_Edge
Fabric OS: 8.0.1
Domain ID: 3
Fabric Wide
Zoning: Cleared
Lab Environment

Module 6: Firmware
Upgrading Firmware from the CLI

In this section of the lab you will perform a firmware upgrade using the interactive
firmwaredownload command from the CLI.
1. From the workstation desktop open Putty and double-click the G620_Edge 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.
ST01-G620_Edge:FID128:admin> firmwareshow
Appl Primary/Secondary Versions
-----------------------------------------
FOS v8.0.1
v8.0.1
ST01-G620_Edge:FID128:admin>
____________________________________________________________________
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
through G620_Edge Putty and use the firmwaredownloadstatus command to monitor the update
process.
Note
The firmwaredownloadstatus output is shown on the next page.
ST01-G620_Edge:FID128:admin> firmwaredownload
Server Name or IP Address: 10.255.252.50
User Name: basa
File Name: v8.0.1
Network Protocol(1-auto-select, 2-FTP, 3-SCP, 4-SFTP) [1]: 1
Password: basa
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 ...
ST01-G620_Edge:FID128:admin> firmwaredownloadstatus
[1]: Thu May 25 20:33:06 2016
Firmware is being downloaded to the switch. This step may take up to
30 minutes.
[2]: Thu May 25 20:38:36 2016

Firmware has been downloaded to the secondary partition of the
switch.
[3]: Thu May 25 20:40:38 2016

The firmware commit operation has started. This may take up to 10
minutes.
[4]: Thu May 25 20:43:09 2016

The commit operation has completed successfully.
[5]: Thu May 25 20:43:09 2016

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
ST01-G620_Edge:FID128:admin> version
Kernel: 2.6.34.6
Fabric OS: v8.0.1
Made on: Thu Apr 21 23:48:31 2016
Flash: Wed May 25 20:43:09 2016
BootProm: 2.0.25
1.Thursday April 21 2016

Module 6: Firmware
ST01-G620_Edge:FID128:admin> firmwareshow
Appl Primary/Secondary Versions
------------------------------------------
FOS v8.0.1
v8.0.1
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
2016/05/25-20:38:32, [SULB-1001], 1078268, CHASSIS, WARNING,

Brocade300, Firmwaredownload command has started.
____________________________________________________________________
b. What message is generated when the firmware commit completes?4
2016/5/25-20:43:09, [SULB-1004], 1078878, CHASSIS, INFO, ST01-
G620_Edge, Firmwarecommit has completed.
____________________________________________________________________
c. What message is generated when the firmwaredownload command completes?5
2016/5/25-20:43:09, [SULB-1002], 1078891, CHASSIS, INFO, ST01-
G620_Edge, Firmwaredownload command has completed successfully.
____________________________________________________________________
2.2.6.34.6
3.[SULB-1001], 17507, CHASSIS, WARNING, ST01-G620_Edge, Firmwaredownload command has started.
4.[SULB-1004], 17520, CHASSIS, INFO, ST01-G620_Edge, Firmwarecommit has completed.
5.[SULB-1002], 17522, CHASSIS, INFO, ST01-G620_Edge, Firmwaredownload command has completed successfully.

Module 6: Firmware
Upgrading Firmware Using Brocade Network Advisor

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

Module 6: Firmware

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 v8.0.1. Which switches are displayed in
the lower right?
____________________________________________________________________
____________________________________________________________________
22. Click the Show all supported switch types to view all switches capable of running the v8.0.1
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.

Module 6: Firmware
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 G620_Core and the 6510_Edge from your station using CTRL + click.
27. Click the right arrow to add the switches to the Select Switches list.
28. In the Firmware to Download column of all switches select v8.0.1
29. Check the Overwrite current firmware check box
Note
The Overwrite current firmware option is only needed if you are flashing a switch with the
same or an earlier version of Fabric OS. It is used in this lab because the switches are pre-
loaded with Fabric OS v8.0.1.
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. You can click on any of the switches to see the firmwaredownloadstatus command output
in the Status Details text field at the bottom of the Firmware Management window.
37. Move and resize the Firmware Management window so you can watch the Master Log on the main
Network Advisor window behind.
38. Scroll through the Master Log, located at the bottom of the main Network Advisor window, while
the firmware is updating. Look at some of the events by right-clicking and choosing Properties.
What Value was logged for the Category property when the firmware was imported to the
repository?7
____________________________________________________________________
39. Review the firmware messages and click Close when finished.
40. Click Close to close the Firmware Management window and return to the main Network Advisor
window.
6.In Progress
7.User Action Event

Module 6: Firmware
This ends Module 6: Firmware lab.

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 regular zoning configuration using Network Advisor
Verifying LUN connectivity using Network Advisor
Creating and activating a peer zoning configuration using Network Advisor

G620_Edge
Fabric OS: 8.0.1
Domain ID: 1
Ports Disabled: 0
G620_Core
Fabric OS: 8.0.1
Domain ID: 2

Module 7: Zoning
6510_Edge
Fabric OS: 8.0.1
Domain ID: 3
Fabric Wide
Zoning: Cleared
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 fabric name in the product window, right-click and select View > Connected End
Devices > Show All. This will show the HBA and storage LUNs that are known to Network Advisor
through the fabric.
3. In the navigation pane on the left expand your fabric then expand the Storage Group and Host
Group.
4. Verify that both your storage and your host are visible to the fabric and listed in Network Advisor.

Module 7: Zoning
5. Select your fabric and click Configure > Zoning > Fabric to open the Zoning window.
6. Click the Active Zone Configuration tab.
7. Verify that the default zone is currently set for All Access.

Module 7: Zoning
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.

Module 7: Zoning
Creating and Activating a Regular 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.
14. Underneath the Zones panel click the New Zone.

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

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

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

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

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

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

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

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

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

Module 7: Zoning
36. Click the Trace Route button at the bottom of the Device Connectivity Troubleshooting Results
window and wait for the Trace Route Summary window to display.
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.
Creating and Activating a Peer Zone Configuration
Lab Setup
Prior to starting this lab you will need to persistently enable a second host connection to the fabric. A
minimum of two hosts are required to create a valid peer zone. You will create 1 peer zone with two
initiator ports and 1 target port in it. This zone will have overlapping definitions as the regular zone
already created but for the lab purposes this will not cause issues because we are not running
production traffic. Use the portcfgpersistent enable command on the following switch:
40. On the G620_Edge enable port 0:
portcfgpersistent enable 0
41. Use the switchshow command to verify the a successful enabling of port 0
.

Module 7: Zoning
Using Brocade Network Advisor to create a Peer Zone

42. Select your fabric and click Configure > Zoning > Fabric to open the Zoning window.
43. In the Potential Members pane expand the Host Group and the Storage Group. This time there
should be 2 hosts and 1 storage device. It may take Brocade Network Advisor some time to pick
up the fabric change and update the potential member list. Watch for the following message and
close out the Zoning window and re-open if necessary.
44. Next to the New Zone drop down select a New Peer Zone as shown below

Module 7: Zoning
45. Select the following three devices and use to the Right arrow to move each device to the right
membership window:
Principle Member: the storage port connected to the G620_Edge
Peer Member: the HBA port connected to the 6510_Edge
Peer Member: the HBA port connected to the G620_Edge
46. Click OK to close out the Add Peer Zone window
47. Select the New Zone and rename to PeerZone

Module 7: Zoning
48. Select PeerZone and click the right arrow to add the zone to the ConfigA. configuration.
49. Click Apply
50. A Network Advisor Message window will display, click OK to save the configuration and return to
the Zoning window.
51. Ensure that ConfigA is highlighted and click Activate, the Activate Zone Configuration window
displays.
52. After reviewing the zoning configuration for accuracy click OK, a Network Advisor Message window
displays.

Module 7: Zoning
53. Review the message and click Yes to activate the configuration.
54. Another Network Advisor Message window will display, review the message and click OK to return
to the Zoning window.

Module 7: Zoning
55. In the Zoning window, click the Active Zone Configuration tab to verify the active configuration.
56. Click Cancel to return to the main Network Advisor window.
Validate the Zoning change using the CLI

57. Use Putty on the desktop to initiate a telnet session to G620_Edge
58. Login and view the zoning configuration using the command: cfgshow
ST01-G620_Edge:FID128:admin> cfgshow
Defined configuration:
cfg: ConfigA Zone1; PeerZone
zone: PeerZone
00:02:00:00:00:03:00:01; 20:00:00:11:0d:0f:84:00;
10:00:00:05:1e:56:c8:2a; 10:00:00:05:1e:56:c8:2b
zone: Zone1 10:00:00:05:1e:56:c8:2b; 20:00:00:11:0d:0f:84:00
Effective configuration:
cfg: ConfigA
zone: PeerZone
00:02:00:00:00:03:00:01
20:00:00:11:0d:0f:84:00
10:00:00:05:1e:56:c8:2a
10:00:00:05:1e:56:c8:2b
zone: Zone1 10:00:00:05:1e:56:c8:2b

20:00:00:11:0d:0f:84:00
59. What is the purpose of the entry in the PeerZone that begins with 00:02?
____________________________________________________________________2
60. Should the two initiators be able to communicate with each other if they are members of the same
peer zone?
____________________________________________________________________3
2.Internal fabric designation identifying this zone as a peer zone: 00:02:00:00:00:03:00:01

3.Not as long as they have been defined as Peer members

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

G620_Edge
Fabric OS: 8.0.1
Domain ID: 1
G620_Core
Fabric OS: 8.0.1
Domain ID: 2

6510_Edge
Fabric OS: 8.0.1
Domain ID: 3
Fabric Wide
Default Zone: No access
Zoning: ConfigA
Lab Environment

Getting Started
This lab exercise verifies that the switches are using the default exchange-base routing.
1. Open Telnet sessions to the G620_Core and 6510_Edge switches using Putty.
2. Ensure that Trunking and Extended Fabric licenses are installed on the G620_Core and
6510_Edge switches using the licenseshow command. Contact the instructor if this licenses
is missing from either switch.
ST01-G620_Core:FID128:admin> licenseshow
7YrHgWm4EACfAJErrm349JtaW3LKRPTFB7T3P:
DgXTP4Zfm77FXmJ9SCCHXFPYEaWgArgANgQGaYEAGKPB:
Ports on Demand license
Capacity 24
4NQLRFZKRDKFQttfPQ4GKKTgYT74aaAgB79rF:
Trunking license
FICON_CUP license
Fabric Vision and IO Insight license
4NQLRFFKRDKFGgrfRQ4QKKTgYT74aaAKDtFCQNHAWLHB:
Q-Flex Ports on Demand license
Capacity 16
ST01-6510_Edge:FID128:admin> licenseshow
byeQeSczRdezfRfm:
Fabric Watch (Fabric Vision capable) license
byeQeSczRdgzfRfo:
Performance Monitor (Fabric Vision capable) license
byeQeSczRdkzfRfs:
Trunking license
byeQeSczRdczhRfm:
byeQeSczRdc1fRfm:
FICON_CUP license
byeQeSczRdcFjRf4:
Full Ports on Demand license - additional 24 port upgrade license
SdScQQbyeyTeTdRo:
gaaM7Ra3CREYNP9CEKg7HCJfWRRMPtrNB7gJK:
Adaptive Networking - obsolete license
B7BLSt4DYHLF7BGtGSW794DmSHgtJLHEBAg4K:
Server Application Optimization - obsolete license

3. Type the aptpolicy command on both the 6510_Edge and G620_Core to verify this; the
output should display: Current Policy: 3.
ST01-G620_Core:FID128:admin> aptpolicy
Current Policy: 3
3 : Default Policy
1: Port Based Routing Policy
2: Device Based Routing Policy (FICON support only)
3: Exchange Based Routing Policy
ST01-6510_Edge:FID128:admin> aptpolicy
Current Policy: 3
3 : Default Policy
1: Port Based Routing Policy
2: Device Based Routing Policy (FICON support only)
3: Exchange Based Routing Policy
4. If the policy is not exchange based policy then change it to this policy using the syntax modeled
in this example:
ST01-G620_Core:FID128: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 6510_Edge and
G620_Core switches.
5. Type the portcfgshow command on both the 6510_Edge and G620_Core switches to verify
that trunking is enabled on all the ports on each switch in your fabric.1
ST01-6510_Edge:FID128:admin> portcfgshow
Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
----------------------+---+---+---+---+-----+---+---+---+-----+---+---+---+-----+---+---+---
Octet Speed Combo 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Speed AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN
AL_PA Offset 13 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
<output truncated>
6. If portcfgshow output does not show Trunk Port ON, use the following command to
ensure that both switches are capable of establishing a trunk: switchcfgtrunk 12
1. Trunk Ports should display ON.

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

7. Type the switchshow command from the 6510_Edge and use the output to answer the
following questions:
switchType: 109.1
switchState: Online
switchMode: Native
switchDomain: 3
switchId: fffc03
switchWwn: 10:00:00:05:33:93:69:3f
zoning: ON (ConfigA)
switchBeacon: OFF
FC Router: OFF
FC Router BB Fabric ID: 1
Address Mode: 0

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

_______________________________________________________________3
b. How can you determine which Trunk Master is the Principal ISL?
_______________________________________________________________4
c. List the criteria that needs to be met in order for ports to form a trunk:
_______________________________________________________________5
8. From the G620_Core, type the islshow command and answer this questions.
ST01-G620_Core:FID128:admin> islshow
1: 8-> 8 10:00:00:05:33:93:69:3f 3 6510_Edge sp:16.000G bw:32.000G TRUNK QOS CR_RECOV FEC
2: 15-> 15 10:00:c4:f5:7c:0e:d4:d8 2 G620_Edg sp:32.000G bw:64.000G TRUNK QOS CR_RECOV FEC
a. What is the aggregate bandwidth of each trunk group:

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

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

10. From the 6510_Edge, type the trunkshow command and evaluate the deskew values.
ST01-6510_Edge:FID128:admin> trunkshow
1: 8-> 8 10:00:c4:f5:7c:0e:c0:7c 1 deskew 15 MASTER
9-> 9 10:00:c4:f5:7c:0e:c0:7c 1 deskew 15
Note the greatest deskew difference in your trunk groups: ___________________

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

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

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

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


23. 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.
24. From the remote desktop, select Start > Log off Administrator and click OK. Please do not
choose Shutdown.
25. Click on Sign Out in the upper right corner.
This ends Module 8: Routing and Trunking.

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

G620_Edge
Fabric OS: 8.0.1
Domain ID: 1
G620_Core
Fabric OS: 8.0.1
Domain ID: 2

6510_Edge
Fabric OS: 8.0.1
Domain ID: 3
Fabric Wide
Zoning: ConfigA
Student Information

Getting Started
1. Open Telnet sessions to your 6510_Edge and G620_Core using Putty.
2. Type the licenseshow command and verify that the Extended Fabric license is installed.
3. The first step is to verify that both switches are configured with default distance settings.
a. Type the portcfgshow command on both switches. Verify that the Long Distance row
displays .. for all ports indicating that long distance is disabled.
ST01-6510_Edge:FID128:admin> portcfgshow | more
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 your
6510_Edge
ST01-6510_Edge:FID128:admin> portbuffershow
User Port Lx Max/Resv Avg Buffer Usage & FrameSize Buffer Needed Link Remaining
Port Type Mode Buffers Tx Rx Usage Buffers Distance Buffers
---- ---- ---- ------- ---------------------------- ------ ------- --------- ----------
0 F - 8 - ( - ) - ( - ) 8 - -
1 - 8 - ( - ) - ( - ) 0 - -
2 - 8 - ( - ) - ( - ) 0 - -
3 - 8 - ( - ) - ( - ) 0 - -
4 - 8 - ( - ) - ( - ) 0 - -
5 - 8 - ( - ) - ( - ) 0 - -
6 - 8 - ( - ) - ( - ) 0 - -
7 - 8 - ( - ) - ( - ) 0 - -
8 E - 8 - ( 80) 1(1864) 34 34 <2km
9 E - 8 1(2024) 1(2000) 34 34 <2km
5. To enable LD mode on port 8 of the 6510_Edge with a desired distance of 25 km, issue the
following CLI command:
ST01-6510_Edge:FID128:admin> portcfglongdistance 8 ld 1 -distance 25
Warning: port may be buffer limited if cable is longer than estimated.

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

7. From the G620_Core, issue the switchshow command and answer these questions.
ST01-G620_Core:admin> switchshow
switchName: G620_Core
switchType: 162.0
switchState: Online
switchMode: Native
switchDomain: 2
switchId: fffc02
switchWwn: 10:00:c4:f5:7c:0e:c0:7c
zoning: OFF
switchBeacon: OFF
FC Router: OFF
HIF Mode: OFF
Allow XISL Use: OFF
LS Attributes: [FID: 128, Base Switch: No, Default Switch: Yes, Address Mode 0]

==================================================
0 0 020000 id N16 No_Light FC
2 2 020200 -- N32 No_Module FC
7 7 020700 -- N32 No_Module FC
8 8 020800 id N16 Online FC E-Port segmented,10:00:00:05:33:93:69:3f ("No class F
frames, Long distance fabric or LD mode" incompatible)
9 9 020900 id N16 Online FC E-Port 10:00:00:05:33:93:69:3f "ST01-6510_Edge"
(upstream)(Trunk master)
<output truncated>
a. What is the status of port 8?

____________________________________________________________________1
b. What is the reason given for the status?
____________________________________________________________________2
8. From your G620_Core, issue the following commands.
ST01-G620_Core:admin> portcfglongdistance 8 ld 1 -distance 25
Warning: port may be buffer limited if cable is longer than
estimated.
NOTE
You may need to disable/enable the port for the connection to come online, use the commands
portdisable and portenable.
1.Segmented
2."No class F frames, Long distance fabric or LD mode" incompatible

9. From the 6510_Edge, issue the switchshow command.

ST01-6510_Edge:admin> switchshow
switchType: 109.1
switchState: Online
switchMode: Native
switchDomain: 3
switchId: fffc03
switchWwn: 10:00:00:05:33:93:69:3f
switchBeacon: OFF
FC Router: OFF
Address Mode: 0

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

_______________________________________________________________3
10. From the 6510_Edge, issue a trunkshow command.
ST01-6510_Edge:admin> trunkshow
1: 8-> 8 10:00:00:05:1e:7f:06:9c 2 deskew 15 MASTER
How many trunks are there? ____ 4

Why?
____________________________________________________________________ 5
11. From the 6510_Edge, issue the following command:
ST01-6510_Edge:admin> portcfglongdistance 9 ld 1 -distance 25
estimated.
3. Online and operating normally

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

12. From the G620_Core, issue the following command:

ST01-G620_Core:admin> portcfglongdistance 9 ld 1 -distance 25
estimated.
13. From the 6510_Edge, issue a trunkshow command.
ST01-6510_Edge:admin> trunkshow
9-> 9 10:00:00:05:1e:7f:06:9c 2 deskew 16
How many trunks are there? ____6

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


18. From the remote desktop, select Start > Log off Administrator and click OK. Please do not
choose Shutdown.
19. Click on Sign Out in the upper right corner.
This ends Module 9: Long Distance lab.

This exercise will concentrate on migrating, configuring, and using the Fabric OS MAPS feature on the
CLI.
Objectives
In this laboratory exercise, you will perform tasks related to configuring MAPS from the CLI:
Configuring custom groups
Creating, modifying, and editing rules and policies

G620_Edge
Fabric OS: 8.0.1
Domain ID: 1
G620_Core
Fabric OS: 8.0.1
Domain ID: 2

6510_Edge
Fabric OS: 8.0.1
Domain ID: 3
Fabric Wide
Zoning: ConfigA

Connect to the RSL

If you are not already connected, use the instructions in Lab 0 of this book and the information on
your Student Information Sheet to reconnect to your RSL station.
Enabling MAPS on a Switch

In this exercise you will go through the process reviewing the MAPS default policy.
1. Using the PuTTY shortcut on your desktop connect to the G620_Edge in your lab station and log
in using the admin account.
2. Check the MAPS policy summary using the mapspolicy --show -summary command. How
many default MAPS policies are there?1
____________________________________________________________________
ST01-G620_Edge:FID128:admin> mapspolicy --show -summary
dflt_aggressive_policy : 216
dflt_moderate_policy : 218
dflt_conservative_policy : 218
dflt_base_policy : 33
Active Policy is 'dflt_conservative_policy'.
3. To view an entire policy use the command syntax mapspolicy --show <<policy
name>>. View the dflt_conservative_policy.
a. Find the latency rules in the command output (Hint, look for LATENCY under the Condition
column. List the names.2
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
b. Which actions are listed for the following IO_FRAME_LOSS rule?3
____________________________________________________________________
ST01-G620_Edge:FID128:admin> mapspolicy --show dflt_conservative_policy
Rule Name |Condition |Actions |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
defALL_PORTSSFP_STATE_OUT |ALL_PORTS(SFP_STATE/NONE==OUT) |RASLOG,SNMP,EMAIL |
defALL_PORTS_IO_FRAME_LOSS | ALL_PORTS(DEV_LATENCY_IMPACT/NONE==IO_FRAME_LOSS) |RASLOG,SNMP,EMAIL,SDDQ,TOGG|
1.There should be four policies with the default active policy being the dflt_conservative_policy.
2. defALL_PORTS_IO_FRAME_LOSS, defALL_PORTS_IO_LATENCY_CLEAR,
defALL_PORTS_IO_PERF_IMPACT
3. RASLOG,SNMP,EMAIL,SDDQ,TOGGLE

Configuring Global MAPS Actions

In this exercise you will take a look at the default actions enabled by MAPS. You will also configure the
default actions available to all MAPS rules. Remember, if a rule has an action listed but that action is
disabled in MAPS the global MAPS configuration will take precedence.
4. Use the mapsconfig --show command, what actions are enabled by default?4
____________________________________________________________________
ST01-G620_Edge:FID128:admin> mapsconfig --show
Configured Notifications: SW_CRITICAL,SW_MARGINAL
Mail Recipient: Not Configured
Paused members :
===============
PORT :
CIRCUIT :
SFP :
5. Use the mapsconfig --actions command to enable some of the MAPS actions.
a. First view your possible --actions options by entering the incomplete command syntax:
mapsconfig --actions
ST01-G620_Edge:FID128:admin> mapsconfig --actions
mapsconfig: option '--actions' requires an argument
Usage:
mapsConfig --config <pause | continue> -type <memberType> -members
<member-string>
mapsConfig --actions <action list>
mapsConfig --emailcfg -address <email address | address list>
mapsConfig --testmail [-subject <subject>] [-message <msg>]
mapsConfig --import <flowName> [-force]
mapsConfig --deimport <flowName>
mapsConfig --purge
mapsConfig --show
mapsConfig --help
Valid format for Action list: <action>[,<action>,..]
-----------------------------
Values for group type: PORT, CIRCUIT, SFP
----------------------
Values for action: RASLOG, SNMP, EMAIL, FENCE,
---------------------- SDDQ, DECOM, TOGGLE, FMS,
SFP_MARGINAL, NONE
4.By default the SW_CRITICAL, SW_MARGINAL actions are enabled.

6. Globally enable a few more of the MAPS action options.

ST01-G620_Edge:FID128:admin> mapsconfig --actions
RASLOG,SNMP,EMAIL,FENCE,TOGGLE
7. Use the mapsconfig --show command one more time to verify the actions have been
enabled.
ST01-G620_Edge:FID128:admin> mapsconfig --show
Configured Notifications:
RASLOG,SNMP,EMAIL,FENCE,SW_CRITICAL,SW_MARGINAL,TOGGLE
Mail Recipient: Not Configured
Paused members :
===============
PORT :
CIRCUIT :
SFP :

Creating and Viewing Logical Groups

Now that our global actions are configured we can move onto creating custom groups. In order for a
MAPS rule to use a custom group the group must exist first. You will use the logicalgroup CLI to
create and manage logical groups in MAPS.
8. Before beginning look at the default logical groups using the logicalgroup --show
command.
ST01-G620_Edge:FID128:admin> logicalgroup --show
---------------------------------------------------------------------------------------------------------
Group Name |Predefined |Type |Member Count |Members
---------------------------------------------------------------------------------------------------------
ALL_PORTS |Yes |Port |64 |0-63
ALL_E_PORTS |Yes |Port |2 |14-15
ALL_F_PORTS |Yes |Port |1 |1
ALL_HOST_PORTS |Yes |Port |0 |
ALL_TARGET_PORTS |Yes |Port |1 |1
ALL_OTHER_F_PORTS |Yes |Port |0 |
NON_E_F_PORTS |Yes |Port |61 |0,2-13,16-63
ALL_D_PORTS |Yes |Port |0 |
ALL_BE_PORTS |Yes |BE Port |0 |
ALL_QUARANTINED_PORTS |Yes |Port |0 |
ALL_TS |Yes |Temperature sensor|7 |0-6
ALL_PS |Yes |Power Supply |2 |1-2
ALL_FAN |Yes |Fan |2 |1-2
ALL_WWN |Yes |WWN |1 |1
ALL_FLASH |Yes |Flash |1 |0
ALL_ASICS |Yes |Asic |1 |0
ALL_CERTS |Yes |Certificate |0 |
ALL_LOCAL_PIDS |Yes |Pid |1 |All Pids monitored
SWITCH |Yes | |1 |0
CHASSIS |Yes | |1 |0
ALL_SFP |Yes |Sfp |4 |0-1,14-15
ALL_10GSWL_SFP |Yes |Sfp |0 |
ALL_10GLWL_SFP |Yes |Sfp |0 |
ALL_16GSWL_SFP |Yes |Sfp |2 |0-1
ALL_25Km_16GLWL_SFP |Yes |Sfp |0 |
ALL_32GSWL_QSFP |Yes |Sfp |0 |
ALL_OTHER_SFP |Yes |Sfp |0 |
ALL_QSFP |Yes |Sfp |0 |
ALL_100M_16GSWL_QSFP |Yes |Sfp |0 |
ALL_CIRCUITS |Yes |Circuit |0 |
9. Look at the ALL_F_PORTS group, which ports are a member of this group by default on the
switch? What about the ALL_E_PORTS group?5
____________________________________________________________________
5.On this switch you will see port 1 in the ALL_F_PORTS group and ports 14-15 in the ALL_E_PORTS group.

10. Disable port 1 and ports 14-15 on the switch. Run the logicalgroup --show command
one more time, are those ports still members of the ALL_F_PORTS and ALL_E_PORTS groups?6
____________________________________________________________________
ST01-G620_Edge:FID128:admin> portdisable 14-15
ST01-G620_Edge:FID128:admin> portdisable 1
ST01-G620_Edge:FID128:admin> logicalgroup --show
---------------------------------------------------------------------------------------------------------
Group Name |Predefined |Type |Member Count |Members
---------------------------------------------------------------------------------------------------------
ALL_PORTS |Yes |Port |64 |0-63
ALL_E_PORTS |Yes |Port |0 |
ALL_F_PORTS |Yes |Port |0 |
ALL_HOST_PORTS |Yes |Port |0 |
ALL_TARGET_PORTS |Yes |Port |0 |
ALL_OTHER_F_PORTS |Yes |Port |0 |
NON_E_F_PORTS |Yes |Port |64 |0-63
ALL_D_PORTS |Yes |Port |0 |
ALL_BE_PORTS |Yes |BE Port |0 |
ALL_QUARANTINED_PORTS |Yes |Port |0 |
ALL_TS |Yes |Temperature sensor|7 |0-6
ALL_PS |Yes |Power Supply |2 |1-2
ALL_FAN |Yes |Fan |2 |1-2
ALL_WWN |Yes |WWN |1 |1
ALL_FLASH |Yes |Flash |1 |0
ALL_ASICS |Yes |Asic |1 |0
ALL_CERTS |Yes |Certificate |0 |
ALL_LOCAL_PIDS |Yes |Pid |1 |All Pids monitored
SWITCH |Yes | |1 |0
CHASSIS |Yes | |1 |0
ALL_SFP |Yes |Sfp |4 |0-1,14-15
ALL_10GSWL_SFP |Yes |Sfp |0 |
ALL_25Km_16GLWL_SFP |Yes |Sfp |0 |
ALL_32GSWL_QSFP |Yes |Sfp |0 |
ALL_OTHER_SFP |Yes |Sfp |0 |
ALL_QSFP |Yes |Sfp |0 |
ALL_100M_16GSWL_QSFP |Yes |Sfp |0 |
ALL_CIRCUITS |Yes |Circuit |0 |
11. Re-enable port 1 and ports 14-15.

12. Create a logical group that contains the Port 1 called critical_ports.
ST01-G620_Edge:FID128:admin> logicalgroup --create critical_ports
-type port -members 1
13. You can use the logicalgroup --show critical_ports command verify the group was
created with the correct members.
14. Now add the E_Ports to the same group and verify using the logicalgroup --show
command.
ST01-G620_Edge:FID128:admin> logicalgroup --addmember
critical_ports -members 14,15
6.Because the ports are disabled (no longer E or F_Ports) they are no longer members of those default
groups.

Creating Policies and Rules

In this exercise you will create a new empty policy and assign some custom rules. Please note that
these rules were designed to be easily tested in a lab environment and are not meant to be put on a
production switch.
15. Create a rule that will monitor the critical_ports group for state changes, the rule will generate a
RASLog message if a state change occurs more than once in a minute.
ST01-G620_Edge:FID128:admin> mapsrule --create port_state_change
-group critical_ports -monitor state_chg -timebase min -op g
-value 1 -action raslog
16. Verify the rule using the mapsrule --show command. Is this rule currently associated with
any policies?7
ST01-G620_Edge:FID128:admin> mapsrule --show port_state_change
Rule Data:
----------
RuleName: port_state_change
Condition: critical_ports(state_chg/min>1)
Actions: raslog
Associated Policies:
17. Create an empty policy named lab_policy using the mapspolicy --create command
ST01-G620_Edge:FID128:admin> mapspolicy --create lab_policy
18. Now add the port_state_change rule you created in step 15 to the new policy.
ST01-G620_Edge:FID128:admin> mapspolicy --addrule lab_policy
-rulename port_state_change
19. Verify the new policy using the mapspolicy --show and mapsrule --show commands.
ST01-G620_Edge:FID128:admin> mapspolicy --show lab_policy
Policy Name: lab_policy
Rule List Action Condition
---------------------------------------------------------------------------------------------------------
port_state_change raslog critical_ports_group(state_chg/min>1)
Active Policy is 'dflt_base_policy'.
ST01-G620_Edge:FID128:admin> mapsrule --show port_state_change

Rule Data:
----------
RuleName: port_state_change
Condition: critical_ports(state_chg/min>1)
Actions: raslog
Associated Policies: lab_policy
20. With the current MAPS configuration will this rule be active on the switch? Why?8
____________________________________________________________________
____________________________________________________________________
7.No, this rule is not associated with any policies currently.

8.No, because the rule is not currently associated with the active policy.

21. Create a second rule to add to your custom policy. This rule will monitor for E_Port down events,
if an E_Port goes down more than twice in a minute a RASLog message will be generated.
ST01-G620_Edge:FID128:admin> mapsrule --create E_Port_Down -group
switch -monitor EPORT_DOWN -timebase min -op g -value 2 -action
RASLOG -policy lab_policy
22. At this point you can verify the rules in your policy using the mapspolicy --show command.
ST01-G620_Edge:FID128:admin> mapspolicy --show lab_policy
Policy Name: lab_policy
Rule List Action Condition

---------------------------------------------------------------------------------------------------------
port_state_change raslog critical_ports(state_chg/min>1)
E_Port_Down RASLOG switch(EPORT_DOWN/min>2)
Active Policy is 'dflt_base_policy'.
Enabling MAPS Policies and Testing Rules

In this lab exercise you will enable the policy created above and test the new rules. Remember that
while multiple MAPS policies can be defined on a switch only one can be active at any time.
23. Enable the policy you just created using the mapspolicy --enable command.
ST01-G620_Edge:FID128:admin> mapspolicy --enable lab_policy
24. Test the new policy by disabling and enabling one of the ports in the critical_ports group.
ST01-G620_Edge:FID128:admin> portenable 1
25. Check the RASLog to make sure that a message was generated.
ST01-G620_Edge:FID128:admin> errshow -r
Fabric OS: v8.1.0
20116/08/05-11:56:29, [MAPS-1003], 907, FID 128, WARNING, ST01-

G620_Edge, Port 1, Condition=critical_ports(STATE_CHG/min>1),
Current Value:[STATE_CHG,2], RuleName=port_state_change, Dashboard
Category=Port Health.
26. Check the second rule that you created by disabling one of the E_Ports on the G620_Edge. Try
disabling and re-enabling port 14 several times. When you are done check the RASLog, what do
you see?9
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
9.You will see a trigger for the port_state_change rule but not for the E_Port_Down rule. This is because ports
14 and 15 form a trunk and disabling a single port does not cause the E_Port to go down, it does however
generate a port state change event.

27. Now, disable port 15 and try disabling and re-enabling port 14 a few more times. Does this
trigger the E_Port_Down rule?10
____________________________________________________________________
28. Re-enable both E_Ports, 14 and 15, and continue with the next lab exercise.
Viewing the MAPS CLI Dashboard

In this exercise you will use the MAPS CLI Dashboard to see what types of events have occurred on a
switch. The dashboard will show rule violations as well as general health and status information for a
switch. The MAPS dashboard has several options for displaying and filtering the dashboard data
based on the date and hour.
NOTE
Because the mapsdb command outputs are fairly long, they have been included on the
following page.
29. To view the MAPS dashboard use the mapsdb --show command.
In section 3.1 Summary Report, which categories show an abnormal status for today?
Why?11
____________________________________________________________________
____________________________________________________________________
In section 3.2 Rules Affecting Health, which rules have been triggered?12
____________________________________________________________________
____________________________________________________________________
30. Detailed history data can also be shown using the mapsdb --show history command.
Take a moment to review the port statistics for your switch. Are there any STATE_CHG
events?13
____________________________________________________________________
____________________________________________________________________
10.Yes it does.
11.Port Health and Fabric State Changes show an abnormal status for today because of the rules you
created and triggered.
12.The port_state_change and E_Port_Down rules have been triggered.
13.Yes, there should be state change events for ports 1, 14, and 15.

ST01-G620_Edge:FID128:admin> mapsdb --show
1 Dashboard Information:
=======================
DB start time: Fri Aug 9 11:55:54 2013

Active policy: lab_policy
Fenced Ports : none
2 Switch Health Report:

=======================
Current Switch Policy Status: HEALTHY
3.1 Summary Report:

===================
Category |Today |Last 7 days |

--------------------------------------------------------------------------------
Port Health |Out of operating range |No Errors |
Fru Health |In operating range |In operating range |
Security Violations |No Errors |No Errors |
Fabric State Changes |Out of operating range |No Errors |
Switch Resource |In operating range |In operating range |
Traffic Performance |In operating range |In operating range |
FCIP Health |Not applicable |Not applicable |
3.2 Rules Affecting Health:

===========================
Category(Rule Count)|RepeatCount|Rule Name |Execution Time |Object |Triggered Value(Units)|

-----------------------------------------------------------------------------------------------------------------------
Port Health(7) |1 |port_state_change |08/09/13 15:15:48|Port 0 |2 |
|5 |port_state_change |08/09/13 12:07:11|Port 14 |4 |
| | | |Port 14 |4 |
| | | |Port 14 |2 |
| | | |Port 14 |4 |
| | | |Port 14 |2 |
|1 |port_state_change |08/09/13 11:56:29|Port 0 |2 |
Fabric State Changes|1 |E_Port_Down |08/09/13 12:06:35|Switch |3 Ports |
(1) | | | | | |
ST01-G620_Edge:FID128:admin> mapsdb --show history
1 History Data:
===============
Stats(Units) Current --/--/-- --/--/-- --/--/-- --/--/-- --/--/-- --/--/--

Port(val)
---------------------------------------------------------------------------------------------
CRC(CRCs) - - - - - - -
ITW(ITWs) 0(>999) - - - - - -
LOSS_SYNC(SyncLoss) - - - - - - -
LF 0(2) - - - - - -
LOSS_SIGNAL(LOS) 0(8) - - - - - -
PE(Errors) - - - - - - -
STATE_CHG 14(16) - - - - - -
0(6) - - - - - -
15(2) - - - - - -
LR 14(16) - - - - - -
0(5) - - - - - -
15(2) - - - - - -
C3TXTO(Timeouts) - - - - - - -
RX(%) - - - - - - -
TX(%) - - - - - - -
UTIL(%) - - - - - - -
BN_SECS(Seconds) - - - - - - -

Viewing the Port Availability Monitor Report

The port availability monitor can be used to check the uptime statistics for every port in a switch. The
mapssam --show command will display every port on the system, the type of port, uptime and
downtime percentages, the number of times the port was marked faulty (this does not include
administratively downing the port using the portdisable command), and the total offline time of
the port.
31. View the port availability monitor report using the mapssam --show command.
Do any of your switch ports show any downtime?14
____________________________________________________________________
What does the DP and T in the Type column indicate on ports 0, 14 and 15?15 (Hint: use
the help files if needed).
____________________________________________________________________
ST01-G620_Edge:FID128:admin> mapssam --show
Total Total Down Total

Port Type Up Time Down Time Occurrence Offline Time
(Percent) (Percent) (Times) (Percent)
======================================================================
0 DP 0.00 0.00 0 100.00
1 F 98.78 0.00 0 1.22
2 U 0.00 0.00 0 100.00
3 U 0.00 0.00 0 100.00
4 U 0.00 0.00 0 100.00
5 U 0.00 0.00 0 100.00
6 U 0.00 0.00 0 100.00
7 U 0.00 0.00 0 100.00
8 U 0.00 0.00 0 100.00
9 U 0.00 0.00 0 100.00
10 U 0.00 0.00 0 100.00
11 U 0.00 0.00 0 100.00
12 U 0.00 0.00 0 100.00
13 U 0.00 0.00 0 100.00
14 E 99.77 0.00 0 0.23
15 T 98.95 0.00 0 1.05
16 U 0.00 0.00 0 100.00
17 U 0.00 0.00 0 100.00
18 U 0.00 0.00 0 100.00
19 U 0.00 0.00 0 100.00
20 U 0.00 0.00 0 100.00
14.Ports 1, 14, and 15 should show a small percentage of downtime.

15.The DP stands for disabled persistently, port 0 is persistently disabled. The T stands for trunk port.
MAPS recognizes that ports 15 is a member of a trunk port. Note, port 14 is also a member of the same
trunk but its the trunk master which displays as E for E_Port.


33. Click Start > Log off administrator in the client window.
34. In the Log Off Windows window click Log Off.
35. Close the Secure Application Manager on your desktop, it is located in your System Tray.
36. Right-click the Secure Application Manager icon (as shown below) and select Sign Out.
This ends the Module 10a Lab: Using the MAPS CLI exercise.


In this lab you will be enabling and configuring MAPS using Brocade Network Advisor. You will also
make use of the new Network Advisor dashboards to track MAPS events.
Objectives
In this laboratory exercise, you will perform tasks related to configuring MAPS using Network Advisor
Configuring MAPS actions using Network Advisor
Configuring custom groups
Creating, modifying, and editing rules and policies
Using the Network Advisor MAPS dashboards

At this point you have enabled MAPS on your stations G620_Edge, enabled actions, created a policy,
and defined rules for that policy. In these next exercises you will use Network Advisor to enable MAPS
on the rest of your switches.
Connect to the RSL

If you are not already connected, use the instructions in Lab 0 of this book and the information on
your Student Information Sheet to reconnect to your RSL station.

Configuring the MAPS Network Advisor Dashboard

In this exercise you will create a dashboard view for Network Advisor.
1. Switch to the Default Dashboard tab (step 1 in example graphic).
2. Create your own My Dashboard (Note, Lab Dashboard already created for illustration purposes).
a. Expand the dashboard view, if not already done, by clicking on left-hand side Dashboards
- vertically written (step 2 in graphic)
b. Select My Dashboard (step 2a) and click Add near the bottom of the page (step 2b)
c. Enter in the Name field: Lab Dashboard and click OK (step 2c)
Double-click the Lab Dashboard to change the view to the newly created dashboard (step 2d)

Now in these steps you will add additional widgets to your dashboard in Network Advisor. For the
purposes of this lab you will be closing the dashboards that we will not be using. Feel free to
experiment with the other dashboards if you have time.
3. Switch to the Dashboard - Lab Dashboard tab.
4. Click the wrench icon (Customize Dashboard button) on the left side of the control bar, the
Customize Dashboard window will display.
5. Under the Status tab choose in the display column put a check next to the following widgets
Out of Range Violations
Port Health Violations
ISL Port Health Violations
Initiator Port Health Violations
Target Port Health Violations
6. With the dashboard setup you can now configure MAPS on one of your other switches.

Configuring MAPS Using Network Advisor
7. Return to the main SAN tab

8. In the navigation tree on the left, right-click the 6510_Edge entry and select
Fabric Vision > MAPS > Configure, the MAPS Configuration dialog will be displayed with the
selected switch information already expanded.
How can you tell which one is the active policy?1
____________________________________________________________________
What is the active policy for the 6510_Edge switch?2
____________________________________________________________________
Look at the columns to the right of the switch, be sure to scroll (left to right). Which actions
are enabled on the 6510_Edge switch?3
____________________________________________________________________
1.The policy will have a green dot next to it.

2.dflt_conservative_policy, this is the policy that Network Advisor enables by default with a Fabric Vision
license
3.Switch Status Marginal and Switch Status Critical

Configuring MAPS Actions

Network Advisor can be used to configure MAPS actions on a switch-by-switch or fabric basis.
9. In the MAPS Configuration dialog select the Lab Fabric entry and click the Actions button on the
right.
10. Click Enable All then click OK, the Set Action Status window will be displayed.
11. Verify that the action was successful on all four switches and click Close to return to the MAPS
Configuration dialog.

12. Network Advisor can also be used to configure an individual switch. Select the G620_Core
switch and click the Actions button on the right.
13. Un-check the E-mail action and click OK, the Set Action Status dialog will be displayed.
14. Verify the action was successful and click Close to return to the MAPS Configuration dialog.
15. You will now see that the green check is missing from the E-mail column of the G620_Core.

Managing Groups
Similar to managing actions, Network Advisor allows you to manage logical groups on a switch-by-
switch or fabric basis. The logical groups created are still unique to each switch in the fabric, but
Network Advisor makes it easy to create groups with the same names across multiple switches
simultaneously.
16. Select the Lab Fabric entry and then click the Manage button on the right beneath the Groups
heading. The Lab Fabric - Manage MAPS Groups window will be displayed. Are there any groups
already present on the switch?4
____________________________________________________________________
17. In the Available Ports column expand the Products entry to view all your fabric switches.
18. Click the Add button in the lower left corner, the Add Group dialog will be displayed.
4.You will see the critical_ports group that was created in the previous lab.

19. In the Name field enter ISLtoG620_Core.

20. In the Type pull-down leave the default selection of PORT.
21. Click OK.
22. Create a second group with the name HostPort of type PORT.
23. Select the ISLtoG620_Core group.
24. In the Available Ports column expand the G620_Edge and select ports 14 and 15. Click the right
arrow to add those ports to the Force Include Product/Group window.
NOTE
You can select multiple items in a list by using Shift + click or Ctrl + click.
25. Expand the 6510_Edge entry and select ports 8 and 9. Click the right arrow to add those ports to
the Force Include Product/Group window

26. Use the same procedure to assign the following port to the HostPort group:
HostPort
6510_Edge port 0
27. When you have finished setting up the groups click OK to apply the changes to the switches, the
Manage Groups dialog will be displayed.
28. Verify all the actions were successful and click Close.

Creating Policies and Rules

Unlike managing actions and logical groups, Network Advisor does not support managing policies on a
fabric-wide basis. Instead policies and rules are created on an individual switch basis, and then they
can be distributed to the rest of the switches in the fabric.
Cloning an Existing Policy

Any existing policy, user created or default, can be cloned into a new policy and modified to suite your
needs.
29. Expand your 6510_Edge switch and select the dflt_aggressive_policy.
30. Click the Add button on the right, the Add Policy dialog will be displayed. The existing rules for the
policy will be populated automatically.
31. In the Name field enter dflt_clone_policy.
32. Click on the Resource tab and answer the following questions.
What actions are taken if the CPU utilization exceeds 80%? (Hint: be sure to scroll)5
____________________________________________________________________
What percentage of the flash memory needs to be in use before a rule is triggered?6
____________________________________________________________________
5.A RASLog, SNMP trap, and email are generated.

6.A rule will be triggered if the flash utilization equals or exceeds 90%.

33. Click on the Port tab. Are there any rules which would cause a port to be fenced if triggered?7
____________________________________________________________________
34. Click OK to create the newly cloned policy and return to the MAPS Configuration dialog.
7.You should see a number of rules where port fencing is an action. Remember that ports will only be fenced
if port fencing is enabled in the Global Allowable Actions list.

Creating a New Policy

35. Select the 6510_Edge switch and click Add. The Add Policy dialog will be displayed with an
empty policy.
36. In the Name field enter BNA_Policy.
37. On the Port tab, In the Groups / Rules field select the HostPort group.
38. In the Add/Edit Rule field in the Rule Name section select the Custom radio button and enter
fence_host_ports for the rule name.
39. In the Measure pull-down, scroll down and select State Changes (STATE_CHG).
40. In the Threshold section set the operand drop-down to the greater than or equal symbol >=
and the count to 1.
41. Set the TimeBase drop-down to Min.
42. Under Actions put check marks next to RAS Log Event and Fence.
43. Click the right arrow to add the rule to the policy. (Make sure the Custom Group: HostPort is
selected)
44. Click OK to create the policy on the switch and return to the MAPS Configuration dialog.

Editing an Existing Policy

45. If not already selected, select the BNA_Policy you just created.
46. Click the Edit button, the Edit Policy dialog will be displayed.
47. Select the Fabric tab.
48. In the Add/Edit Rule column use the following parameters:
Rule Name: (select the Auto radio button)
Measure: E-port down (EPORT_DOWN)
Threshold: > 0 (greater than zero)
TimeBase: Min
Actions: SNMP Trap
49. In the Groups / Rules column select the SWITCH entry, click the right arrow to add the rule to the
group. Make a note of the automatically generated name BNA provides.
50. Click OK to finish editing the rule and return to the MAPS Configuration dialog.

Activate Policy
51. Just because a policy has been created and edited doesnt mean that it will automatically
become the active policy.
a. To enable the policy select the BNA_Policy listed underneath the 6510_Edge switch and
select Activate.

Distributing Policies to Other Switches in the Fabric

Network Advisor will allow you to distribute a policy from one switch (6510_Edge) to other switches in
the same fabric, or even different, fabrics. When policies are distributed all the rules are also
distributed with the policy. Any user defined logical groups will be created on the target switches if
they do not exist. The automatically generated logical groups will not be populated however.
52. Select the BNA_Policy you just finished creating and editing.
53. Click the Distribute button, and move the G620_Core and G620_Edge into the Selected Members
window.
54. Leave the Activation radio button set to: Activate policy on each switch
55. Select OK, a Network Advisor Message dialog will be displayed.
56. Read the warning and click Yes to finish the distribution, when the process is finished the
Distribute Policy Status dialog will be displayed.
57. Click Close to return to the MAPS Configuration dialog.
58. Click Close to return to the main Network Advisor screen.

Viewing Port Violations on the Dashboard

When you created your BNA_Policy in the previous exercise you included a rule that will fence host
ports if the port experiences a state change. Were going to trigger this rule and use the results to see
how port violations are shown on the Network Advisor dashboards.
59. Minimize Network Advisor.
60. Use the PuTTY icon on your desktop to log into the 6510_Edge in your lab station
61. Trigger the BNA_Policy by disabling and enabling one of the ports.
ST01-6510_Edge:FID128:admin> portdisable 0
ST01-6510_Edge:FID128:admin> portenable 0
62. Wait a moment and then repeat this process of disabling and re-enable the port. This will trigger
the fence_host_ports rule created earlier and will result in port 0 on the 6510_Edge being
fenced.
63. Use the switchshow command to verify that the port has been fenced:
switchName: 6510_Edge
switchType: 109.1
switchState: Online
switchMode: Native
switchDomain: 3
switchId: fffc03
switchWwn: 10:00:00:05:33:93:69:3f
switchBeacon: OFF
FC Router: OFF
Address Mode: 0
HIF Mode: OFF

==================================================
0 0 030000 id N16 No_Sync FC Disabled (Port State Change threshold exceeded)
1 1 030100 -- N16 No_Module FC
<Output Truncated>

64. Return to your Network Advisor window and select the Dashboard tab. Double click Lab
Dashboard under My Dashboard.
Do you see any violations shown in the dashboard widgets?8
____________________________________________________________________
Which widgets show violations? Why?9
____________________________________________________________________
65. In the Initiator Port Health Violations widget right-click on the port and choose Locate, you will be
taken to the SAN tab and the port will be highlighted.
66. Right-click on the port and select Enable / Disable > Enable to re-enable the port, a Network
Advisor Message dialog will be displayed.
67. Read the message and click Yes to finish enabling the port.
68. Look in the Master Log for any relevant events. There will be an event showing that the port was
fenced due to a rule violation.
8.Yes, there are port health violations shown on the Network Advisor dashboards.
9.The following widgets show violations: Initiator Port Health, Port Health, and Out of Range. These
dashboards show the violations for this port because the port fits the scope for each one (it is an initiator
port, it is also a port, and the rule trigger creates an out of range violation).

Lab Cleanup
In order to prevent the fence_host_ports rule from causing problems with the remainder of the labs
you are going to adjust the threshold values.
69. Before continuing on with any other labs run the mapsconfig --purge command on all
three of your stations switches. This will remove any MAPS configurations and will prevent ports
from being fenced by mistake.


71. Click Start > Log off administrator in the client window.
72. In the Log Off Windows window click Log Off.
73. Close the Secure Application Manager on your desktop, it is located in your System Tray.
74. Right-click the Secure Application Manager icon (as shown below) and select Sign Out.
This ends the Module 10b Lab: Using MAPS With Network Advisor exercise.

Objectives
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 one of the switches in your station. This configuration file will contain errors.
Find and correct all the errors.
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
Use Brocade Network Advisor to run D_Port tests

G620_Edge
Fabric OS: 8.0.1
Domain ID: 1
G620_Core
Fabric OS: 8.0.1
Domain ID: 2

6510_Edge
Fabric OS: 8.0.1
Domain ID: 3
Fabric Wide
Zoning: ConfigA
Lab Environment

Capturing Technical Support Data

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

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

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

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

Brocade Network Advisor Reports

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

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

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

g. Looking at the Switch Utilization, what is the "Number of Ports Free"? _____________3
See example report below:
3. 165

Troubleshooting Switch Merge Issues

In this section you will download a configuration file to the 6510_Edge switch. Once the configuration
file is successfully downloaded to the switch enable the switch using the switchenable command.
A number of issues have been introduced into the switch configuration 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 6510_Edge Configuration File

5. On the desk double click on the PuTTY icon.
6. Select the 6510_Edge and then click Open.
Login: admin
Password: password
7. Disable the switch using the switchdisable command.
ST01-6510_Edge:FID128:admin> switchdisable
8. Download the configuration file using the configdownload command and answer the prompts
as listed below:
ST01-6510_Edge:FID128:admin> configdownload
Protocol (scp, ftp, sftp, local) [ftp]:
Server Name or IP Address [host]: 10.255.252.50
User Name [user]: basa
Path/Filename [<home dir>/config.txt]: config_6510_Edge
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: basa
duplicate license-key "bcze9bbS9zcd0fAp"
duplicate license-key "SbRcSQede9TcWdTj"
duplicate license-key "KGG9RaRra9FJSFNXKD9YFtTXBJm74YNCBAgYR"
duplicate license-key "GHCtNLTPrB4CQM3CHDGt7DNJarWKBmFYBSWtA"

duplicate license-key "ra34HgYfTEYEra4fCQRR9339StKfm9rGBJYaQ"

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

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

ST01-6510_Edge:FID128: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:
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________

Clear Link D_Port Configuration

In this section you will configure a D_Port test between two switches: G620_Edge and G620_Core. A
port in D_Port mode does not carry any user traffic, and is designed to run only specific diagnostics
tests for identifying link-level faults or failures.
1. From the desktop open the Putty application and select the G620_Edge, select Load, click Open.
Username: admin
Password: password
3. Use the configure command to view the default D_Port mode configuration:
a. Is the Dynamic D-Port functionality enabled by default?
____________________________________________________________________4
ST01-G620_Edge:FID128:admin> configure
Configure...
Fabric parameters (yes, y, no, n): [no]
D-Port parameters (yes, y, no, n): [no] y
Dynamic D-Port (on, off): [on]
On Demand D-Port (on, off): [off]
b. Enter Ctrl + C to exit out of the configure command

4. What type of external requests trigger a Dynamic D_Port?
____________________________________________________________________5
5. From the desktop open the Putty application and select the G620_Core, select Load, click Open.
Username: admin
Password: password
7. Use the command switchshow to view the ISL connections to the G620_Edge.
8. Return to your putty session for the G620_Edge switch and put port 15 into Static D_Port mode.
a. The first step is to disable the port 15 in order to enable D_Port mode.
b. Enable Static D_Port mode on port 15.
ST01-G620_Edge:FID128:admin> portcfgdport --enable 15
c. What console message do you see after enabling D_Port mode?
____________________________________________________________________6
4. Yes
5. The port is automatically set to a D_Port based on an external request from a remote port on the other end of the
connection. Typically, this is setting the other end of the link into a Static D_Port mode to trigger a D_Port test.

9. Remember port 15 is an ISL connection between G620_Edge and G620_Core.

a. Enable port 15.
b. Use the switchshow command and view what the description is for port 15,
____________________________________________________________________7
c. Wait a few minutes and enter the switchshow command again. The following output shows
port 15 after the D_Port test has completed.
.........
10 10 020a00 -- N32 No_Module FC (POD license not assigned or reserved
yet)
11 11 020b00 -- N32 No_Module FC (POD license not assigned or reserved
yet)
12 12 020c00 -- N32 No_Module FC (POD license not assigned or reserved
yet)
13 13 020d00 -- N32 No_Module FC (POD license not assigned or reserved
yet)
14 14 020e00 id N32 Online FC E-Port 10:00:c4:f5:7c:0e:c0:7c
"G620_Core" (upstream)(Trunk master)
15 15 020f00 id N32 Online FC D-Port 10:00:c4:f5:7c:0e:c0:7c
10. Return to the putty session for G620_Core. Use the switchshow command and record what is
listed next to port 15
____________________________________________________________________8
6. Caution:
Gen 5 platforms: D_Port functionality is available with 16Gb/10Gb FC SFPs, 16Gb/8Gb LWL/ELWL FC SFPs and 16Gb Q
SFPs
Gen 6 platforms: D_Port functionality is available with 32Gb/16Gb/10Gb FC SFPs, 32Gb/16Gb LWL/ELWL FC SFPs and
32Gb/16Gb QSFPs.
7. Depending on the timing when the switchshow the description field will change. While the test is running it will
show the current phase of the test.
15 15 020f00 id N32 Online FC D-Port Loopback->Port 15.
8. Dynamic

11. The results of the D_Port test can be viewed from either switch. Us the following command sytax
for port 15: portdporttest --show <slot/port>
a. What is the estimated length of the cable between the switches?
____________________________________________________________________9
ST01-G620_Core:FID128:admin> portdporttest --show 15
D-Port Information:
===================
Port: 15
Remote WWNN: 10:00:c4:f5:7c:0e:d4:d8
Remote port index: 15
Mode: Automatic
No. of test frames: 1 Million
Test frame size: 1024 Bytes
FEC (enabled/option/active): Yes/No/Yes
CR (enabled/option/active): Yes/No/No
Start time: Fri May 27 16:19:08 2016
End time: Fri May 27 16:20:29 2016
Status: PASSED
======================================================================
==
Test Start time Result EST(HH:MM:SS)
Comments
======================================================================
==
Electrical loopback 16:20:13 PASSED -------- -
---------
Optical loopback 16:20:17 PASSED -------- -
---------
Link traffic test 16:20:25 PASSED -------- -
---------
======================================================================
==
Roundtrip link latency: 1056 nano-seconds
Estimated cable distance: 1 meters
Buffers required: 1 (for 2112 byte frames at 32Gbps speed)
Egress power: Tx: -1.4 dBm, Rx: -1.1 dBm, Diff: 0.0
dBm (No Loss)
9. 1 meter

Ingress power: Rx: -3.3 dBm, Tx: -1.7 dBm, Diff: 1.6
dBm (Loss is within tolerable limit)
12. Return to the putty session of the other switch and execute the same command to view the result
of the D_Port test.
a. Does the Roundtrip link latency value match?
____________________________________________________________________10
13. Return to the putty session of the G620_Edge switch.
a. Attempt to remove the D_Port configuration on port 15. Enter the following command:
portcfgdport --disable 15.
b. What was the outcome?
____________________________________________________________________11
14. In order to remove the D_Port mode from port 15 you can use the following sequence of
commands:
ST01-G620_Edge:FID128:admin> portcfgdport --disable 15
15. Are there any commands that need to be executed on G620_Core to remove its port 15 from
Dynamic D_Port mode?
____________________________________________________________________12
16. Return to the putty session of the G620_Core switch and validate that an ISL has reformed on port
15.
This ends Module 11: Troubleshooting lab.
10. Yes they should because they are measuring the same link length
11. Port 15: This operation is not allowed because the port has not been provisioned for
D_Port or port is not disabled. Please use portcfgdport --provision -add command
to provision the port for D_Port or use portdisable to disable the port to proceed
further
12. No. The removal of the static D_Port config on G620_Edge prompts the removal of the D_Port state on port 15 on
G620_Core.

BASA 200 Brocade Associate SAN Administrator: Lab Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BASA 200 Brocade Associate SAN Administrator: Lab Guide

Uploaded by

Copyright:

Available Formats

BASA 200

Brocade Associate SAN

European Headquarters - Geneva, Switzerland

Asia Pacific Headquarters - Singapore

2016 Brocade Communications Systems, Inc. All Rights Reserved.

Module 3: Director FRU Identification

Module 4: Fibre Channel Theory

Module 5: Installing and Configuring Switches

BASA 200 Revision 0816 iii

Module 8: Routing and Trunking

iv Revision 0816 BASA 200

Module 10a Lab: Using the MAPS CLI

Module 10b Lab: Using MAPS With Network Advisor

Module 11: Troubleshooting

BASA 200 Revision 0816 v

Revision 0816 BASA 200 1

Record Remote Lab Access Information

Connecting to the Brocade RSL Environment

2 Revision 0816 BASA 200

7. The Secure Application Manager launches. Select Allow.

8. You have successfully connected to your RSL workstation.

Close Open Sessions and Exit Remote Connection

10. Close the browser.

Revision 0816 BASA 200 3

This ends the Remote Lab Access Instructions lab exercise.

4 Revision 0816 BASA 200

DCX Feature Hunt

Revision 0816 BASA 200 5

DCX8510-8 Port Side

6 Revision 0816 BASA 200

DCX8510-8 non-Port Side

Revision 0816 BASA 200 7

X6-4 Feature Hunt

X6-4 Port Side

8 Revision 0816 BASA 200

X6-4 non-Port Side

Revision 0816 BASA 200 9

Director Feature Hunt Answers

DCX8510-8 Port Side

DCX8510-8 non-Port Side

X6-4 Port Side

X6-4 non-Port Side

This ends Module 3: Director FRU Identification.

10 Revision 0816 BASA 200

Expected Start State

Revision 0816 BASA 200 11

12 Revision 0816 BASA 200

Revision 0816 BASA 200 13

Fibre Channel Levels

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

14 Revision 0816 BASA 200

Node and Port World-Wide Names

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

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

Revision 0816 BASA 200 15

6. Log into the G620_Edge using the following credentials:

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

16 Revision 0816 BASA 200

Port part of other ADs: No

Revision 0816 BASA 200 17

Port part of other ADs: No

18 Revision 0816 BASA 200

24-bit Device Addressing