Brocade BCFA 16 Gbps Training

8/18/2019 Brocade BCFA 16 Gbps Training

1/156

CFA 200

Brocade Certified

Fabric Administrator(BCFA) 16 Gbps

Training

Lab Guide

Brocade University

Revision 0512


2/156

Corporate Headquarters - San Jose, CA USA

T: (408) 333-8000

[email protected]

European Headquarters - Geneva, SwitzerlandT: +41 22 799 56 40

[email protected]

Asia Pacific Headquarters - Singapore

T: +65-6538-4700

[email protected]

© 2012 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, the Brocade B-weave logo, Fabric OS, File Lifecycle Manager, MyView, Secure Fabric OS, SilkWorm,

and StorageX are registered trademarks and the Brocade B-wing symbol and Tapestry are trademarks of

Brocade Communications Systems, Inc., in the United States and/or in other countries. FICON is a registered

trademark of IBM Corporation in the U.S. and other countries. All other brands, products, or service names are

or may be trademarks or service marks of, and are used to identify, products or services of their respective

owners.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or

implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade.

Brocade reserves the right to make changes to this document at any time, without notice, and assumes no

responsibility for its use. This informational document describes features that may not be currently available.

Contact a Brocade sales office for information on feature and product availability. Export of technical data

contained in this document may require an export license from the United States government.

Revision 0512


3/156

CFA 200 Revision 0512 iii

ont nts

Remote Lab Access Instructions

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Record Remote Lab Access Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Login information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Connecting to the ITTM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Enrolling in the Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Connecting to the Brocade RSL Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Module 2: Fibre Channel Theory

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Fibre Channel Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Classes of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Frame Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Node and Port World-Wide Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Port Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Well-Known Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

24-bit Device Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Module 4: Director FRU Identification

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

DCX Feature Hunt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

DCX Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

DCX non-Port Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

DCX-4S Feature Hunt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

DCX-4S Port Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

DCX-4S non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Director Feature Hunt Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

DCX Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

DCX non-Port Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

DCX-4S Port Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

DCX-4S non-Port Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Module 5: Installing and Configuring Switches

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configure and Verify Basic Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Setting the Command Line Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring and Verifying Basic Settings on the B300. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Configuring and Verifying Basic Settings on the B5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

View Time for the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Configuring an NTP Server for the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Change the Time Zone for Each Switch in the Fabric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Setting a Message of the Day and a Login Banner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44


4/156

iv Revision 0512 CFA 200

Verify Licensed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

View the Switch Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

View the Chassis Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Turn on Enhanced Change Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Specify a Syslog Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Determining Switch Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Verifying Switch Uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Checking Switch Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Looking at Sensor Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Looking at Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Looking at the Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Examine Fabric Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Verify Device Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Verify that Devices have Successfully Logged into the Fabric. . . . . . . . . . . . . . . . . . . . . . . . . 55

Discovering the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Configuration Backup Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Configuration Save (Backup) and Restore Using Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . 63

Module 6: Firmware

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Upgrading Firmware from the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Upgrading Firmware Using Brocade Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Setting Up the Firmware Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Updating Switch Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Module 7: Zoning

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79


Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Configuring Zoning in Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Setting the Default Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Creating and Activating a Zone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Verifying Device Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Using Network Advisor to verify Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Using HCM and Disk Management to Verify Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Module 8: Routing and Trunking

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93


Student Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Lab Pairing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Using the CLI to Evaluate Basic Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97


5/156

CFA 200 Revision 0512 v

Using Brocade Network Advisor to Configure Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Use CLI to Evaluate the Current Trunking Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Restore the Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Evaluate the Current B6510 Routing over Trunks Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Module 9: Long Distance

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Student Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Lab Pairing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Configure Trunking Over Distance . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Restore the Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Module 10: Troubleshooting

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Lab Station Pairing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Run D_Port Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Capturing Technical Support Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Brocade Network Advisor Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Troubleshooting Switch Merge Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Downloading the B300 Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Downloading the B5100 Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Troubleshooting Switch Merge Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Appendix A: Cheat Sheet

Module 2: Fibre Channel Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Module 10: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

B300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

B5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Lab Setup

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

List of Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Lab Environment: Two Stations (Odd and Even) Configuration. . . . . . . . . . . . . . . . . . . . . . 149

Individual Lab Station Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150


6/156

vi Revision 0512 CFA 200


7/156

Revision 0512 CFP 300 1


Time Allocated: 10 Minutes

You will need to use these steps to access a remote workstation when doing lab exercises using the

Remote Solutions Lab (RSL). All lab exercises start at the remote workstation. All devices in the RSL

are preconnected.

Objectives

In this lab exercise, you will perform tasks related to connecting and then disconnecting from the

Brocade Remote Solutions Lab. This lab is divided into the following sections:

• Record remote lab access information

• Connect to the Brocade RSL environment

• Cleanly disconnect from the remote lab station


8/156


9/156



Connecting to the ITTM Environment

These steps are for connecting to a lab for a class that is using the ITTM lab environment. If you are

using the Brocade RSL environment skip to the Connect to the Brocade RSL Environment section.

6. Connect to the remote lab environment using the URL: http://brocade.netsysenterprise.com/

7. From the login page:

a. If this is the first time you have used the remote lab system, click on the register here link

below the Log In button.

b. If you have already registered, enter your credentials select the Log In button. Skip to the next

section.

FIGURE 1 ITTM login screen


10/156


4 Revision 0512 CFP 300

8. Enter the required information, agree to the terms of service, and click the Register button.

9. On the login page, enter your credentials select the Log In button.

Enrolling in the Class

Enrolling in the class requires a registration code and a student number. Your instructor will provide

the registration code and assign you a student number. Document your information in the space

provided.

Registration Code: __________________

Student Number: ___________________


11/156



10. To enroll, from your home page, select Training > Enroll in a Class.

11. Enter your registration code and student number and click Enroll Now.

12. In the Class Training section of your home page you will see a list of classes you are registered

for, including the one you just enrolled in.


12/156



13. Click the Begin Class button.


13/156



14. Your class page provides details on the availibilty of the lab station assigned to you, other

classmates enrolled and instructor contact information. To access your lab station, click the

Access Now button.

15. If prompted, provide your login credentials.


14/156



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

17. Click the server image.


15/156



18. Click the Begin Session button.

19. A warning will appear. Click Connect to launch a Remote Desktop session.

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

Important

Once you are connected please do not alter any of the partitions on the C drive.

If you are unable to sign on to your station, notify the instructor immediately.

NOTE

You are now connected to the lab environment. You may skip the Connect to the Brocade

RSL Environment section below.


16/156



Connecting to the Brocade RSL Environment

21. Using Internet Explorer, connect to the RSL website: rsl.brocade.com .

22. Depending on the version of your browser:

a. You may be prompted to accept a security certificate through a Security Alert dialog, click

Yes to accept the certificate from the RSL;

b. Otherwise you may see a page stating that there is a ‘problem with this website’s security certificate’.

Choose ‘Continue to this website (not recommended).

• You will then be prompted by a Security Warning. Click the Yes button.

23. Log into the RSL using the Username and Password credentials provided by your instructor.

NOTE

If this is your first time connecting to the RSL, you will be prompted to download the Secure Application

Manager. The Secure Application Manager is used to control access to the RSL.

24. The Secure Application Manager used to control access to the RSL launches.


17/156



25. A link to your RSL station will be provided (shown below). Click the link to access your RSL

workstation.

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

27. A web browser window to the Windows server in your RSL workstation opens. You may first be

prompted with a dialog (shown below) that warns you about displaying the web browser in full-

screen mode. Review the information then click OK.

NOTE

You can press Ctrl+Alt+Pause to toggle between a window view and a full-screen view.


18/156



28. Select the username assigned by the instructor.

29. Enter the password assigned by the instructor.

30. You have successfully connected to the Windows server in your RSL workstation. In your display,

you will see the tab controls shown below. Remember, typing CTRL-ALT-PAUSE will togglebetween full screen and windowed mode.

Important

Once you are connected please do not alter any of the partitions on the C drive.

If you are unable to sign on to your station, notify the instructor immediately.


19/156



Close Open Sessions and Exit Remote Connection

31. If you are not doing another lab at this time then please close all the GUI and CLI sessions that

you have open in your workstation.

32. From the remote desktop, select Start > Log off Administrator and click OK. Please do not

choose Shutdown.

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

34. Close the browser.

This ends the Remote Lab Access Instructions lab exercise.


20/156




21/156

Revision 0512 CFA 200 15


Time Allocated: 30 minutes

This lab will reinforce the Fibre Channel theory concepts that you learned in class.

Objectives In this laboratory exercise, you will perform tasks related to the various elements of the Fibre Channel

protocol and theory:

• List Fibre Channel Levels

• Describe Classes of Service

• Discuss Fibre Channel frame format

• Differentiate between node and port world-wide names

• Discovering fabrics using Brocade Network Advisor

• List various port types

• Differentiate between the well-known addresses

• Decode 24-bit device addressing

Expected Start State

When accessing the switches, you should see the following:

- 4 switches: B300 and B5100

- Zoning should is off/disabled

Credentials to access switches:

- User credentials for the B300 and B5100:

The login gives you access to the B300 and B5100 where you will see connectivity to a third

switch, B6510, that you will not access in this class.

• Username: admin

• Password: password


22/156


16 Revision 0512 CFA 200

Lab Environment

FIGURE 2 Lab Topology


23/156



Fibre Channel Levels

35. Match the Fibre Channel level on the left with its description on the right.1

Classes of Service

36. The column on the left is a description of the Brocade supported Classes of Service. The two

columns on the right are the types of Fibre Channel Classes of Service. Match the description with

its Class of Service.2

Frame Format

37. Identify the fields within a Fibre Channel frame, the length (in bytes) of each and the maximum

frame size.3

Field Length

1. _____________________________________ ______

2. _____________________________________ ______

3. _____________________________________ ______ (maximum)

4. _____________________________________ ______

5. _____________________________________ ______

Maximum frame size: ______

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

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

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

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


24/156



Node and Port World-Wide Names

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

• 10:00:00:05:1e:02:a5:49 __________

• 20:07:00:05:1e:02:a5:49 __________

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


25/156



Port Types

39. Using the above diagram, identify the port types below (U_Port, F_Port, FL_Port, G_Port, E_Port).

The first one has been filled in for you:5

40. Login into the B300 using the following credentials:

• Username: admin


41. Type the portshow 8 command to see the transitory port types that are used during portinitialization.

Note

The flags are shown in reverse order, with the most recent port state on the left.

DEV2-ST01-B300:admin> portshow 8portIndex: 8portName: port8portHealth: OFFLINE

Authentication: NoneportDisableReason: NoneportCFlags: 0x1portFlags: 0x1 PRESENT U_PORTLocalSwcFlags: 0x0portType: 18.0

1. F_Port

2.

3.

4.

5.

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


26/156



POD Port: Port is licensedportState: 2 OfflineProtocol: FCportPhys: 2 No_Module portScn: 0port generation number: 0state transition count: 0

portId: 010800portIfId: 4302000fportWwn: 20:08:00:05:1e:0a:83:6dportWwn of device(s) connected:

Distance: normalportSpeed: N8Gbps

LE domain: 0FC Fastwrite: OFFInterrupts: 0 Link_failure: 0 Frjt: 0Unknown: 0 Loss_of_sync: 0 Fbsy: 0

Lli: 0 Loss_of_sig: 1Proc_rqrd: 0 Protocol_err: 0Timed_out: 0 Invalid_word: 0Rx_flushed: 0 Invalid_crc: 0Tx_unavail: 0 Delim_err: 0Free_buffer: 0 Address_err: 0Overrun: 0 Lr_in: 0Suspended: 0 Lr_out: 0Parity_err: 0 Ols_in: 02_parity_err: 0 Ols_out: 0CMI_bus_err: 0

Port part of other ADs: No

42. Log into the B5100 using the following credentials:

• Username: admin


43. Type the portshow 8 command and review the output.

DEV2-ST01-B5100:admin> portshow 8portIndex: 8portName: port8portHealth: OFFLINE

Authentication: None

EX_Port Mode: EnabledFabric ID: 20Front Phantom: state = Not OK Pref Dom ID: 160Fabric params: R_A_TOV: 0 E_D_TOV: 0 PID fmt: auto

Authentication Type: NoneHash Algorithm: N/A


27/156



DH Group: N/AEdge fabric's primary wwn: N/AEdge fabric's version stamp: N/A

portDisableReason: Fabric ID oversubscribedportCFlags: 0x0portFlags: 0x4021 PRESENT U_PORT EX_PORT DISABLED LED

LocalSwcFlags: 0x0portType: 17.0POD Port: Port is licensedportState: 2 OfflineProtocol: FCportPhys: 6 In_Sync portScn: 2 Offlineport generation number: 40state transition count: 10

portId: 020800portIfId: 43020007portWwn: 20:08:00:05:1e:7f:06:9c

portWwn of device(s) connected:

Distance: normalportSpeed: N8Gbps

LE domain: 0FC Fastwrite: OFFInterrupts: 0 Link_failure: 0 Frjt: 0Unknown: 0 Loss_of_sync: 5 Fbsy: 0Lli: 80 Loss_of_sig: 10Proc_rqrd: 9938 Protocol_err: 0Timed_out: 0 Invalid_word: 6161Rx_flushed: 0 Invalid_crc: 0Tx_unavail: 0 Delim_err: 0Free_buffer: 0 Address_err: 8Overrun: 0 Lr_in: 9Suspended: 0 Lr_out: 5Parity_err: 0 Ols_in: 02_parity_err: 0 Ols_out: 5CMI_bus_err: 0



28/156



Well-Known Addresses

44. Identify the above Well-Known Addresses below:6

24-bit Device Addressing

45. The switch is using standard 24-bit addressing. Translate the hexadecimal area to decimal:7

46. From the B300, type the nsallshow command to display a list of every PID logged into thefabric.

DEV2-ST01-B300:admin> nsallshow{

010000 0101002 Nx_Ports in the Fabric }DEV2-ST01-B300:admin>____________________________________________________________________

____________________________________________________________________

47. From the B300 type the nsshow command. What type of information can you see?8

EV2-ST01-B300:admin> nsshow{ Type Pid COS PortName NodeNameTTL(sec)

N 010000; 3;10:00:00:05:1e:56:c8:2a;20:00:00:05:1e:56:c8:2a;na FC4s: FCP PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST01-HBA | WindowsServer (R) 2008 Standard | Service Pack 1" Fabric Port Name: 20:00:00:05:1e:0a:83:6d

• FFFFFA

• FFFFFB

•

FFFFFC

• FFFFFD

• FFFFFE

• FFFFFF

6.1=Management Server, 2=Time Server, 3=Name Server, 4=Fabric Controller, 5=Fabric Login, 6=Broadcast Server

010400

171700

011A00

1F241F

113F00

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.


29/156



Permanent Port Name: 10:00:00:05:1e:56:c8:2a Port Index: 0 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No N 010100; 3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00;

na FC4s: FCP PortSymb: [36] "Brocade University Virtual FC Target" Fabric Port Name: 20:01:00:05:1e:0a:83:6d Permanent Port Name: 20:00:00:11:0d:0f:84:00 Port Index: 1 Share Area: No Device Shared in Other AD: No Redirect: No Partial: NoThe Local Name Server has 2 entries }____________________________________________________________________

____________________________________________________________________

____________________________________________________________________

- What is the main difference between the nsallshow and the nsshow commands?9

____________________________________________________________________

____________________________________________________________________

48. From the B5100, type the nscamshow command. List the field that appears after the PermanentPort Name field.10

49.

ST01-B5100:admin> nscamshownscam show for remote switches:Switch entry for 1 state rev owner cap_available known v700 0xfffc02 1 Device list: count 1 Type Pid COS PortName NodeName N 010100;3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00; FC4s: FCP PortSymb: [36] "Brocade University Virtual FC Target" Fabric Port Name: 20:01:00:05:1e:0a:83:6d

Permanent Port Name: 20:00:00:11:0d:0f:84:00 Port Index: 1 Share Area: No Device Shared in Other AD: No Redirect: No

9.The nsshow command displays the local NS database. The nsallshow command displays the fabric addresses for

the fabric.

10.If nscamshow does not display output, refer to Appendix A.


30/156



Partial: No

Switch entry for 3 state rev owner cap_available known v700 0xfffc02 1 Device list: count 1 Type Pid COS PortName NodeName

N 030000;3;10:00:00:05:1e:56:c8:2b;20:00:00:05:1e:56:c8:2b; FC4s: FCP PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST01-HBA |Windows Server (R) 2008 Standard | Service Pack 1" Fabric Port Name: 20:00:00:05:33:93:69:40 Permanent Port Name: 10:00:00:05:1e:56:c8:2b Port Index: 0 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No

Switch entry for 4 state rev owner cap_available known v700 0xfffc02 1 Device list: count 0 No entry is found!____________________________________________________________________

50. From the B5100, type the nscamshow -t command. List the field that appears after thePermanent Port Name field.

51.

ST01-B5100:admin> nscamshow -tnscam show for remote switches:Switch entry for 1 state rev owner cap_available known v700 0xfffc02 1 Device list: count 1 Type Pid COS PortName NodeName N 010100;3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00; FC4s: FCP PortSymb: [36] "Brocade University Virtual FC Target" Fabric Port Name: 20:01:00:05:1e:0a:83:6d

Permanent Port Name: 20:00:00:11:0d:0f:84:00 Device type: Physical Target Port Index: 1 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No

Switch entry for 3


31/156



state rev owner cap_available known v700 0xfffc02 1 Device list: count 1 Type Pid COS PortName NodeName N 030000;3;10:00:00:05:1e:56:c8:2b;20:00:00:05:1e:56:c8:2b; FC4s: FCP

PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST01-HBA |Windows Server (R) 2008 Standard | Service Pack 1" Fabric Port Name: 20:00:00:05:33:93:69:40 Permanent Port Name: 10:00:00:05:1e:56:c8:2b Device type: Physical Initiator Port Index: 0 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No

Switch entry for 4

state rev owner cap_available known v700 0xfffc02 1 Device list: count 0 No entry is found!

ST01-B5100:admin>

____________________________________________________________________

- What is the main difference between the nscamshow and nscamshow -t commands?11

____________________________________________________________________

This ends Module 2: Fibre Channel Theory.

11.The nscamshow -t displays the device type.


32/156




33/156




In this lab you will label the major components of the DCX, DCX-4S, and 48000 chassis. A diagram is

provided for both the port side and non-port side of each chassis.

Objectives

In this laboratory exercise, you will perform tasks related to identifying the major components of the

Brocade directors:

• Identify components of the DCX chassis

• Identify components of the DCX-4S chassis

DCX Feature Hunt

Use the diagrams below to identify the components in a DCX chassis. Two diagrams are provided, one

for the port side and one for the non-port side. Use the answer lines below each diagram to write in

the component names. Answers are found at the end of the module, you can also find the answers in

the DCX Hardware Reference Manual.


34/156



DCX Port Side

1.

3.

2.


35/156



DCX non-Port Side

.

.

.


36/156



DCX-4S Feature Hunt

Use the diagrams below to identify the components in a DCX-4S chassis. Two diagrams are provided,

one for the port side and one for the non-port side. Use the answer lines below each diagram to write

in the component names. Answers are found at the end of the module, you can also find the answers

in the DCX-4S Hardware Reference Manual.

DCX-4S Port Side

.

.

.


37/156



DCX-4S non-Port Side

1.

3.

2.


38/156



Director Feature Hunt Answers

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

corrections.

DCX Port Side

1. 48-port FC blade / slot 1

2. CR8 Core Routing blade

3. CP8 Control Processor blade

DCX non-Port Side

1. Power supply

2. WWN cards / logo plate

3. Blower assembly

DCX-4S Port Side

1. 48-port FC blade / slot 8

2. CR4S-8 Core Routing blade

3. CP8 Control Processor blade

DCX-4S non-Port Side

1. Power supply

2. WWN cards / logo plate

3. Blower assembly

This ends Module 4: Director FRU Identification.


39/156




40/156




41/156




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

Expected Start State

When accessing the switches, you should see the following:

- 4 switches: B300, B5100, and B6510

• The B6510 has two logical switches, LS1 and LS2. Review Figure 3 on page 36 for lab

topology. You will not access the B6510 in the Module 5: Installing and Configuring

Switches lab.

-

All ISLs should be up and running.- Zoning should be off/disabled.

Credentials to access switches and RSL station:

- User credentials for Remote Desktop:

• Username: Administrator (click Administrator icon)

• Password: brcd

- User credentials for the B300 and B5100:

The login gives you access to the B300 and B5100 where you will see connectivity to a third

switch, B6510, that you will not access in this class.

•

Username: admin• Password: password

- User credentials for Brocade Network Advisor:

• Username: Administrator



42/156


43/156



• Verify licensed features

• View the switch name

• Turn on enhanced change tracking

• Specify a syslog server

Setting the Command Line Session Timeout The timeout value for a command line session determines how long the session can be idle for before

it is automatically terminated by the switch. This can be set between 1 and 99,999 minutes, or 0 to

disable the timeout value. As you are going through these labs you may wish to change the timeout

value on the switch to prevent being disconnected.

1. From the desktop open the Putty application and select the B300, select Load, click Open.

2. Log in using the following credentials:

• Username: admin


3. Use the timeout command to determine the current value.

DEV2-ST01-B300:admin> timeoutCurrent IDLE Timeout is 5 minutesDEV2-ST01-B300:admin>

4. Use the timeout command to set the timeout value to 0 minutes. This prevents your sessionfrom closing when you are idle:

# timeout 0

DEV2-ST01-B300:admin> timeout 0IDLE Timeout Changed to 0 minutesThe modified IDLE Timeout will be in effect after NEXT loginDEV2-ST01-B300:admin>

DEV2-ST01-B300 login: adminPassword:Place Security Banner Here-----------------------------------------------------------------DEV2-ST01-B300:admin> timeoutCurrent IDLE Timeout is 0 minutes

DEV2-ST01-B300:admin>

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.


44/156



Configuring and Verifying Basic Settings on the B300

6. Display the current Ethernet settings using the ifmodeshow eth0 command. Record theresults here:

DEV2-ST01-B300:admin> ifmodeshow eth0Link mode: negotiated 100baseTx-FD, link ok

MAC Address: 00:05:1E:0A:83:6DDEV2-ST01-B300:admin>

Link mode: ____________________

7. Display the current IP address settings using the ipaddrshow command. Record the settingshere:

DEV2-ST01-B300:admin> ipaddrshow

SWITCHEthernet IP Address: 10.255.224.34Ethernet Subnetmask: 255.255.255.192Gateway IP Address: 10.255.224.62DHCP: OffDEV2-ST01-B300:admin>

Ethernet IP Address:____________________

Ethernet Subnetmask:____________________

Gateway IP Address:____________________

DHCP:____________________

8. Enter the switchshow command. You can use the pipe (|) operand to direct the output to the more command, e.g. switchshow | more. Review the command output, and fill in the

following parameters:

DEV2-ST01-B300:admin> switchshowswitchName: DEV2-ST01-B300switchType: 71.2switchState: OnlineswitchMode: NativeswitchRole: PrincipalswitchDomain: 1switchId: fffc01switchWwn: 10:00:00:05:1e:0a:83:6dzoning: OFFswitchBeacon: OFF

Index Port Address Media Speed State Proto============================================== 0 0 010000 id N4 Online FC F-Port10:00:00:05:1e:56:c8:2a


45/156



1 1 010100 id N8 Online FC F-Port20:00:00:11:0d:0f:84:00 2 2 010200 -- N8 No_Module FC 3 3 010300 -- N8 No_Module FC 4 4 010400 -- N8 No_Module FC 5 5 010500 -- N8 No_Module FC 6 6 010600 -- N8 No_Module FC

7 7 010700 -- N8 No_Module FC 8 8 010800 -- N8 No_Module FC 9 9 010900 -- N8 No_Module FC 10 10 010a00 -- N8 No_Module FC 11 11 010b00 -- N8 No_Module FC 12 12 010c00 -- N8 No_Module FC 13 13 010d00 -- N8 No_Module FC 14 14 010e00 id N8 Online FC E-Port50:00:51:e7:f0:69:ce:0a "fcr_fd_5" (downstream)(Trunk mas 15 15 010f00 id N8 Online FC E-Port (Trunk port,master is Port 14 ) 16 16 011000 -- N8 No_Module FC

17 17 011100 -- N8 No_Module FC 18 18 011200 -- N8 No_Module FC 19 19 011300 -- N8 No_Module FC 20 20 011400 -- N8 No_Module FC 21 21 011500 -- N8 No_Module FC 22 22 011600 -- N8 No_Module FC 23 23 011700 -- N8 No_Module FC

switchName:____________________

switchType:____________________ 1

switchRole:____________________2

switchDomain:__________________3

zoning: ____________________4

9. Enter the version command; what is the FOS version running on the switch?

DEV2-ST01-B300:admin> versionKernel: 2.6.14.2Fabric OS: v7.0.0aMade on: Wed Jun 1 16:04:18 2011Flash: Wed Nov 16 11:39:43 2011BootProm: 1.0.9DEV2-ST01-B300:admin>

Fabric OS: __________________5

1. Switch type for B300 is 71.x

2. Principal or Subordinate

3. 1

4. Zoning should be OFF

5. Fabric OS v7.0.0 or later


46/156



10. Enter the fabricshow command; how many domains are in the fabric?

DEV2-ST01-B300:admin> fabricshowSwitch ID Worldwide Name Enet IP Addr FC IP AddrName------------------------------------------------------------------------- 1: fffc01 10:00:00:05:1e:0a:83:6d 10.255.224.34 0.0.0.0>"DEV2-ST01-B300" 5: fffc05 50:00:51:e7:f0:69:ce:0a 0.0.0.0 0.0.0.0"fcr_fd_5"

The Fabric has 2 switches


11. __________________6

Configuring and Verifying Basic Settings on the B510012. From the desktop open the Putty application and select the B5100, select Load, click Open.

13. Log in using the following credentials:

• Username: admin


14. From the Telnet session of your B5100, display the current IP address settings using the

ipaddrshow command. Record the settings here:

DEV2-ST01-B5100:admin> ipaddrshow

SWITCHEthernet IP Address: 10.255.224.35Ethernet Subnetmask: 255.255.255.192Gateway IP Address: 10.255.224.62DHCP: OffDEV2-ST01-B5100:admin>

Ethernet IP Address:____________________

Ethernet Subnetmask:____________________

Gateway IP Address:____________________

DHCP: ____________________

6. 2 (B300 and B5100)


47/156



15. Enter the switchshow command. Review the command output, and fill in the followingparameters:

DEV2-ST01-B5100:admin> switchshowswitchName: DEV2-ST01-B5100switchType: 66.1switchState: OnlineswitchMode: NativeswitchRole: PrincipalswitchDomain: 2switchId: fffc02switchWwn: 10:00:00:05:1e:7f:06:9czoning: OFFswitchBeacon: OFFFC Router: ONFC Router BB Fabric ID: 100Address Mode: 0

Index Port Address Media Speed State Proto

============================================== 0 0 020000 -- N8 No_Module FC 1 1 020100 -- N8 No_Module FC 2 2 020200 -- N8 No_Module FC 3 3 020300 -- N8 No_Module FC 4 4 020400 -- N8 No_Module FC 5 5 020500 -- N8 No_Module FC 6 6 020600 -- N8 No_Module FC 7 7 020700 -- N8 No_Module FC 8 8 020800 id N8 In_Sync FC Disabled (Fabric IDoversubscribed) 9 9 020900 id N4 In_Sync FC Disabled

10 10 020a00 -- N8 No_Module FC 11 11 020b00 -- N8 No_Module FC 12 12 020c00 -- N8 No_Module FC 13 13 020d00 -- N8 No_Module FC 14 14 020e00 id N8 Online FC EX-Port10:00:00:05:1e:0a:83:6d "DEV2-ST01-B300" (fabric id = 10 )(Trunkmaster) 15 15 020f00 id N8 Online FC EX-Port (Trunk port,master is Port 14 ) 16 16 021000 -- N8 No_Module FC 17 17 021100 -- N8 No_Module FC 18 18 021200 -- N8 No_Module FC

19 19 021300 -- N8 No_Module FC 20 20 021400 -- N8 No_Module FC 21 21 021500 -- N8 No_Module FC 22 22 021600 -- N8 No_Module FC 23 23 021700 -- N8 No_Module FC 24 24 021800 -- N8 No_Module FC 25 25 021900 -- N8 No_Module FC 26 26 021a00 -- N8 No_Module FC 27 27 021b00 -- N8 No_Module FC


48/156



28 28 021c00 -- N8 No_Module FC 29 29 021d00 -- N8 No_Module FC 30 30 021e00 -- N8 No_Module FC 31 31 021f00 -- N8 No_Module FC 32 32 022000 -- N8 No_Module FC 33 33 022100 -- N8 No_Module FC 34 34 022200 -- N8 No_Module FC

35 35 022300 -- N8 No_Module FC 36 36 022400 -- N8 No_Module FC 37 37 022500 -- N8 No_Module FC 38 38 022600 -- N8 No_Module FC 39 39 022700 -- N8 No_Module FCDEV2-ST01-B5100:admin>

switchName:____________________

switchType:____________________ 7

switchRole:____________________8

switchDomain:____________________

9

zoning: ____________________10

16. Entering the version command. What version is currently installed on your B5100?

Fabric OS: ____________________11

View Time for the Fabric

17. Continuing on the Telnet session of the B5100 switch, enter the date command to view thecurrent date and time.

18. Enter tsclockserver to determine the current source of date and time synchronization.12

DEV2-ST01-B5100:admin> tsclockserverActive NTP Server 10.255.252.50Configured NTP Server List 10.255.252.50DEV2-ST01-B5100:admin>

19. Record the current clock server setting on the B5100:

tsclockserver: ____________________

20. Change the tsclockserver setting to LOCL, if it is not already, by running the tsclockserverLOCL command.

7. Switch type of B5100 is 66.x

8. Principal or Subordinate

9. 2

10. Zoning should be OFF

11. v7.0.0a or later

12. If the clock server is specified as LOCL then the date and time that has been manually set on the fabric Principal

is used fabric wide. If an NTP server has been specified, the IP address of that server is displayed.


49/156



Configuring an NTP Server for the Fabric

21. From the B300, run the date 0227123003 command to change the date and time.

a. Issue the date command from both the B300 and the B5100.

b. Verify that they both have the date of Tue Apr 10 11:15:37 Localtime 2012.

22. Set the fabric to synchronize to an external NTP server using thetsclockserver

command on

the B300.

# tsclockserver 10.255.252.11

DEV2-ST01-B300:admin> tsclockserver 10.255.252.11

Updating Clock Server configuration...done.

Updated with the NTP servers


Although the command may be run on any switch in a fabric, enter this command on the B300 only.

23. Record the new clock server and date settings on the B300:

DEV2-ST01-B300:admin> dateTue Apr 10 11:15:37 Localtime 2012DEV2-ST01-B300:admin>

tsclockserver: ____________________

date: ____________________

24. Record the new clock server and date settings on the B5100:

DEV2-ST01-B5100:admin> date

Tue Apr 10 11:14:34 Localtime 2012


tsclockserver: ____________________

date: ____________________

25. Verify that the time is in sync (both dates should match).

It may take up to two minutes for the time to synchronize.

Change the Time Zone for Each Switch in the Fabric

Switches participating in a fabric may be in different time zones. For logging and reporting, it may be

advantageous to leave all switches in the default UTC time zone, however it is possible to have

switches report events in their local time with the tstimezone command.

For example, the Eastern time zone in the United States is offset from GMT by -5 hours, so the

tstimezone -5 command would correctly set the time zone for a switch in the Eastern UnitedStates. You can also run the tstimezone --interactive command to choose the correct timezone from a menu.


50/156



26. Use the tstimezone command to set the time zone of your B300 to the Eastern time zone inthe United States (GMT -5) and verify same.

# tstimezone -5System Time Zone change will take effect at next reboot.# tstimezoneTime Zone Hour Offset: -5Time Zone Minute Offset: 0

Note

If the tstimezone command does not work, use the tstimezone --old 0 commandand then use the tstimezone -5 command. This may require a reboot.

27. Type the date command on each switch to verify that the date on the B300 is 5 hours earlierthan the date on B5100.

If the dates do not differ by 2 hours then type fastboot on the B300, log in and check the datesagain.

28. From the B300, type the following command to restore the configuration back to default:

# tstimezone -7System Time Zone change will take effect at next reboot.

Setting a Message of the Day and a Login Banner

A Message Of The Day (MOTD) and login banner may be displayed at each login. If an MOTD is set, it is

displayed at initial command line access login and a Web Tools session. Once you have logged in, the

login banner is displayed.

29. Continuing with the Telnet session of your B300 and enter the following:

> motd --set "Unauthorized access is prohibited. Unauthorized users must log off."

30. Type the following:

> bannerset “You have successfully logged into the switch.”

31. Type login to terminate your current session. Once you log in to the switch the new MOTD andlogin banner are displayed.

32. To turn off MOTD, type motd --set "" at the command prompt.

33. To turn off the login banner, type bannerset "" at the command prompt.

Verify Licensed Features

In addition to basic switch functionality, each switch may have optional licensed features enabled.

34. Return to the Telnet session of your B5100 and type licenseidshow. Switch license keys aregenerated for a specific switch WWN.

DEV2-ST01-B5100:admin> licenseidshow10:00:00:05:1e:7f:06:9cDEV2-ST01-B5100:admin>


51/156



35. To view the licensed features on this switch, enter thelicenseshow command.

DEV2-ST01-B5100:admin> licenseshowc9SdQeRedATeRK: Fabric licensebRyRc9RRzbci3Sd6: Full Ports on Demand license - additional 16 port upgrade licensePWrGHFKXFHQ4EAMSPWNJFXXSfEYKY7C9BJ9MH: Enhanced Group Management licenseRR3rEXQKTXHHmR3gLYRgF3ttSXS7KM9rBJtSK: 8 Gig FC licenseQDQfZS3QWaPmrSDHfrMRGXYFrffr3F9LB7tYN: Extended Fabric license Fabric Watch license Performance Monitor license Trunking license Integrated Routing license Adaptive Networking license7aACCMPLDAfrRrFJXHZEGHS3FfLf9HAtB7LTA:

Server Application Optimization licenseDEV2-ST01-B5100:admin>

36. Record one or two licensed features here:

____________________________________________________________________

____________________________________________________________________

Note

Notice that one or more features may be activated with a single license key.

View the Switch Name

Verify that each switch has a unique and meaningful name that matches the lab topology diagrams.

Having a switch naming convention is helpful during administration and troubleshooting.

37. Return to the Telnet session of your B300 and issue the switchname command. Verify that theswitch name matches the topology diagram associated with your station.

DEV2-ST01-B300:admin> switchnameDEV2-ST01-B300DEV2-ST01-B300:admin>

a. Record the switch name here.

____________________________________________________________________


52/156



38.

39. Return to the Telnet session of your B5100 and use the switchname command. Verify that theswitch 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 thechassis name when naming files, because of this it is important that your switches have unique

chassis names as well. In most cases the chassis name can be set to the switch name.

40. Return to the Telnet session and use the chassisname command on both switches (B300 andB5100) to verify the current chassis name is correct.

DEV2-ST01-B300:admin> chassisnameDEV2-ST01-B300


DEV2-ST01-B5100:admin> chassisnameDEV2-ST01-B5100DEV2-ST01-B5100:admin>

41. If you want to change the chassisname, use the following steps to rename:

a. Use the chassisname command on the B300 switch and replace the name as follows:

# chassisname R01-ST02#-B300DEV2-ST01-B5100:admin> chassisname R01-ST02-B300

b. Use the chassisname command on the B5100 switch and replace the name as follows:

# chassisname R01-ST02-B5100DEV2-ST01-B5100:admin> chassisname R01-ST02-B5100

c. Use the chassisname command on both switches to verify the new chassis name.

DEV2-ST01-B300:admin> chassisnameR01-ST02-B300

DEV2-ST01-B5100:admin> chassisname

R01-ST02-B5100

Turn on Enhanced Change Tracking

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

fabric.


53/156



42. Return to the open Telnet session of your B5100 and issue the errclear command to clear outany existing messages in the error log.

DEV2-ST01-B5100:admin> errclearDEV2-ST01-B5100:admin>

43. Use the trackchangesshow command to verify the track changes status.

DEV2-ST01-B5100:admin> trackchangesshowTrack changes status: OFFTrack changes generate SNMP-TRAP: NODEV2-ST01-B5100:admin>

44. Use the trackchangesset 1 command.

DEV2-ST01-B5100:admin> trackchangesset 1Committing configuration...done.DEV2-ST01-B5100:admin>

45. Use the errshow -r command and look for informational TRCK messages.

DEV2-ST01-B5100:admin> errshow -rFabric OS: v7.0.0a

2012/04/16-06:28:39, [TRCK-1005], 2, FID 128, INFO, DEV2-ST01-B5100,Track-changes on

Type to continue, Q to stop:

2012/04/16-06:27:27, [LOG-1003], 1, CHASSIS, INFO, DEV2-ST01-B5100,The log has been cleared.

Type to continue, Q to stop:

Note

The errdump command is mostly used for scripts and supportshow output while theerrshow command is commonly used from the CLI as it paginates the output.

Specify a Syslog Server

Error and change tracking logs are stored in switch memory; older entries in this log will be flushed out

to make room for newer log entries. A syslog server may be used to persistently store log files, and has

the added benefit of centralizing switch logs from all switches.

46. Ensure that the Brocade Network Advisor services have been stopped:

a. On the desktop click Start > Programs> Network Advisor 11.1.0> Server Management

Console.

b. On the Services tab click the Stop button

c. At the Confirmation window click Yes and wait for the Network Advisor services to shut down.

d. When the Network Advisor services are stopped close the window and return to the desktop.

47. Follow these steps to start the syslog server (we are using Kiwi Syslog Daemon):


54/156



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

48. Setup a log file to capture events:

a. Click File > Setup

b. In the navigation pane on the left expand Rules > Default > Actions and click Log to file.

c. In the Path and file name of log file field enter c:\captures\cfa200_logs.txt.

d. In the navigation pane on the left click Inputs > UDP

e. Ensure the Listen for UDP Syslog messages box is checked

f. Ensure the UDP Port field is set to 514.

g. Click OK.

49. Determine the IP address of your RSL host server:

a. Click Start > Run

b. Type cmd and press ENTER.

c. From the command window run ipconfig and note the IP address:

____________________________________________________________________

Note

You can forward syslogd messages to up to six servers.

50. Return to the Telnet session of your B5100 and issue the syslogdipadd command. Use the IP address you obtained from Step 49, Step c. It is the IP address of your RSL

host.

51. Generate switch log messages on the B5100. Type login to terminate your current session andlog in as admin. An entry should appear in the syslog server list.

52. Examine the entries in the Kiwi syslog daemon window.

53. Check to see if the messages were recorded in the syslog file; to do this do the following:

a. Click Start > Run

b. Type c:\captures and press ENTER.

c. Open the cfa200_logs.txt file and verify the syslog entries are there.

NOTE

If the messages did not get recorded in the syslog file or the Kiwi syslog daemon window check the fol-lowing:

On the switch run command: syslogdipshow and verify the IP address is set correctly.

Verify that the Network Advisor services are not running.

54. Leave this configuration active through the remainder of this lab in order to observe the log

message that are created.

Check Point: You have configured and verified basic settings on the switches in your fabric. Some of

these steps are not required for essential switch operation; however these basic steps will make SAN

administration easier and more consistent as your fabric grows.


55/156



Determining Switch Status

It is important to have the ability to quickly determine the overall status of the switch, and the status

of particular components.

This section of the lab has the following parts:

• Verifying switch uptime

• Checking switch status

• Looking at sensor readings

• Looking at port status

• Looking at port configuration

• Verifying fabric parameters

Verifying Switch Uptime

Display the amount of time the switch has been operational.

55. Return to the Telnet session of your B5100 and issue the switchuptime command.

DEV2-ST01-B5100:admin> switchuptime 6:46am: up for 5 days 20 hrs 13 minsDEV2-ST01-B5100:admin>

56. Record the amount of time the switch has been operational. ____________________

57. Issue the uptime command. Notice that the uptime reported by both commands is the same.

DEV2-ST01-B5100:admin> uptime 06:46:36 up 5 days, 20:14, 1 user, load average: 0.02, 0.03, 0.00DEV2-ST01-B5100:admin>

Checking Switch Status

You will display the overall status of the switch, look at policy settings, and look at temperature, fan,

and power supply status.

58. Return to the Telnet session of your B300 and issue the switchstatusshow command.

DEV2-ST01-B300:admin> switchstatusshowSwitch Health Report Report time: 04/16/201206:47:57 AMSwitch Name: DEV2-ST01-B300IP address: 10.255.224.34SwitchState: HEALTHYDuration: 140:12

Power supplies monitor HEALTHYTemperatures monitor HEALTHYFans monitor HEALTHYFlash monitor HEALTHYMarginal ports monitor HEALTHY


56/156



Faulty ports monitor HEALTHYMissing SFPs monitor HEALTHYError ports monitor HEALTHY

All ports are healthy


59. Record the switch status here:

a. SwitchState ____________________

b. Power supplies monitor____________________

c. Temperatures monitor ____________________

d. Fans monitor ____________________

e. Flash monitor____________________

f. Marginal ports monitor ____________________

g. Faulty ports monitor ____________________

h. Missing SFPs monitor ____________________

60. Issue theswitchstatuspolicyshow command to determine the percentage and the numberof ports needed to fault before the switch is reported as marginal and record that value:

DEV2-ST01-B300:admin> switchstatuspolicyshowThe current overall switch status policy parameters: Down Marginal ---------------------------------- PowerSupplies 1 1 Temperatures 2 1

Fans 2 1 Flash 0 1 MarginalPorts 25.00%[6] 10.00%[2] FaultyPorts 25.00%[6] 10.00%[2] MissingSFPs 0.00%[0] 0.00%[0] ErrorPorts 0.00%[0] 0.00%[0]Number of ports: 24DEV2-ST01-B300:admin>

_____________________________________________________________________ 13

61. Record the number/percentages of other out-of-spec measurements required to put the switch

into marginal status.14

a. PowerSupplies____________________

b. Temperatures ____________________

13.The marginal ports are 25% and down ports are 10%.

14. A setting of 0 indicates that Fabric OS will not monitor this component. For example having a setting of 0 for

MissingSFPs indicates that the switch will not complain if you remove SFPs. If you wish to have the switch

track this condition or others, use the switchstatuspolicyset command. Since output is user-configurableit could vary.


57/156



c. Fans ____________________

d. Flash ____________________

e. MarginalPorts ____________________

f. MissingSFPs ____________________

Looking at Sensor Readings You can display the current operational status of all switch sensors.

62. From the Telnet session of your B300, issue the sensorshow command.

DEV2-ST01-B300:admin> sensorshowsensor 1: (Temperature) is Ok, value is 28 Csensor 2: (Temperature) is Ok, value is 27 Csensor 3: (Temperature) is Ok, value is 28 Csensor 4: (Fan ) is Ok,speed is 6250 RPMsensor 5: (Fan ) is Ok,speed is 6250 RPMsensor 6: (Fan ) is Ok,speed is 6250 RPM

sensor 7: (Power Supply) is OkDEV2-ST01-B300:admin>

63. Verify that the sensors all display an OK status.

Alternatively, the tempshow, fanshow, and psshow commands will display the status of individualcomponents. The output of these commands is shown below:

DEV2-ST01-B300:admin> tempshow

Sensor State Centigrade Fahrenheit

ID

=================================================

1 Ok 28 82

2 Ok 27 80

3 Ok 28 82


DEV2-ST01-B300:admin> fanshow

Fan 1 is Ok, speed is 6250 RPM




DEV2-ST01-B300:admin> psshow

Power Supply #1 is OK


58/156




Looking at Port Status

We will now observe the status of ports on the switch.

64. From the Telnet session of your B300, issue the portshow 1 command.

DEV2-ST01-B300:admin> portshow 1portIndex: 1portName: port1portHealth: HEALTHY

Authentication: NoneportDisableReason: NoneportCFlags: 0x1portFlags: 0x24b03 PRESENT ACTIVE F_PORT G_PORT U_PORTLOGICAL_ONLINE LOGIN NOELP LED ACCEPT FLOGILocalSwcFlags: 0x0

portType: 18.0POD Port: Port is licensedportState: 1 OnlineProtocol: FCportPhys: 6 In_Sync portScn: 32 F_Portport generation number: 50state transition count: 25

portId: 010100portIfId: 43020015portWwn: 20:01:00:05:1e:0a:83:6dportWwn of device(s) connected:

20:00:00:11:0d:0f:84:00Distance: normalportSpeed: N8Gbps

LE domain: 0FC Fastwrite: OFFInterrupts: 0 Link_failure: 11 Frjt: 0Unknown: 0 Loss_of_sync: 3 Fbsy: 0Lli: 91 Loss_of_sig: 6Proc_rqrd: 167 Protocol_err: 0Timed_out: 0 Invalid_word: 3342501Rx_flushed: 0 Invalid_crc: 0Tx_unavail: 0 Delim_err: 0Free_buffer: 0 Address_err: 0Overrun: 0 Lr_in: 15Suspended: 0 Lr_out: 1Parity_err: 0 Ols_in: 12_parity_err: 0 Ols_out: 15CMI_bus_err: 0



59/156




65. Review the output and record the following parameters15:

a. portHealth ____________________

b. portState ____________________

c. Distance ____________________d. portSpeed ____________________

e. Link_failure____________________

f. Loss_of_sync ____________________

g. Loss_of_sig ____________________

NOTE

It is not unusual to observe Link_failure, Loss_of_sync and related errors. These errors are commonlygenerated as devices are plugged into switch ports. However, you may have a marginal link if you

notice that these errors are increasing over time on a port in a stable fabric.

Looking at the Port Configuration

We will now observe the current port configuration.

66. From the Telnet session of your B300, issue the portcfgshow |more command.

67. Review the output. All ports should be enabled and, since the Trunking license is installed,

trunking also should be enabled by default on all ports.

# portcfgshow |morePorts of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15-----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+--

Trunk Port ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON

Persistent Disable.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..

Examine Fabric Parameters

Fabric parameters must be consistent within a fabric. If fabric parameters (fabric.ops) are notconsistent, a fabric merge will fail until the parameters are set to common values.

68. From the Telnet session of your B300, issue the configshow -pattern fabric.ops command and look at the fabric.ops parameters.

DEV2-ST01-B300:admin> configshow -pattern fabric.opsfabric.ops.BBCredit:16fabric.ops.E_D_TOV:2000fabric.ops.R_A_TOV:10000

15. B300 portshow outputs should display as follows – portHealth: HEALTHY; portState: Online;

Distance: normal; portSpeed: N8Gbps; the other parameters will vary.


60/156



fabric.ops.bladeFault_on_hwErrlevel:0fabric.ops.dataFieldSize:2112fabric.ops.max_hops:7fabric.ops.mode.fcpProbeDisable:0fabric.ops.mode.isolate:0fabric.ops.mode.longDistance:0fabric.ops.mode.noClassF:0

fabric.ops.mode.pidFormat:1fabric.ops.mode.tachyonCompat:0fabric.ops.mode.unicastOnly:0fabric.ops.mode.useCsCtl:0fabric.ops.vc.class.2:2fabric.ops.vc.class.3:3fabric.ops.vc.config:0xc0fabric.ops.vc.linkCtrl:0fabric.ops.vc.multicast:7fabric.ops.wan_tov:0DEV2-ST01-B300:admin>

69. Return to the Telnet session of your B5100 and issue the same command:# configshow -pattern fabric.ops to look at the fabric.ops parameters.

DEV2-ST01-B5100:admin> configshow -pattern fabric.ops

fabric.ops.BBCredit:16

fabric.ops.E_D_TOV:2000

fabric.ops.R_A_TOV:10000

fabric.ops.bladeFault_on_hwErrlevel:0

fabric.ops.dataFieldSize:2112

fabric.ops.max_hops:7fabric.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.class.3:3

fabric.ops.vc.config:0xc0

fabric.ops.vc.linkCtrl:0

fabric.ops.vc.multicast:7

fabric.ops.wan_tov:0


61/156




70. Compare the fabric.ops parameters on both switches. Do any of the parameters differ?

______________________________________________________________________ 16

Check Point: You have learned to quickly assess general switch status. Fabric troubleshooting builds on

these introductory steps.

Verify Device Connection

This section of the lab will have you verify that a host, storage, or tape device has successfully logged

into the fabric.

Verify that Devices have Successfully Logged into the Fabric

As new devices are added to a fabric configuration, it is important to have the ability to gather basicinformation and status regarding the newly-added devices.

71. Return to the open Telnet session of your B300 and issue the nsshow –t -r command.

72. Verify that the host bus adapter is properly registered with the name server and fabric controller.

Record the last three octets of the port WWN of the devices. Example: 50:4c:7d.

Note

The number of devices on your SAN may vary depending on the RSL environment. At a mini-mum you should have at least one host and one storage device.

ST01-B300:admin> nsshow -t -r{ Type Pid COS PortName NodeNameSCR N 010000; 3;10:00:00:05:1e:56:c8:2a;20:00:00:05:1e:56:c8:2a;0x01000003 FC4s: FCP PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST01-HBA | WindowsServer (R) 2008 Standard | Service Pack 1" Fabric Port Name: 20:00:00:05:1e:0a:83:6d Permanent Port Name: 10:00:00:05:1e:56:c8:2a Device type: Physical Initiator Port Index: 0 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No

16.The switches should be successfully merged into a single fabric so the fabric.ops parameters should be the

same.


62/156



N 010100; 3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00;0x01000003 FC4s: FCP PortSymb: [36] "Brocade University Virtual FC Target" Fabric Port Name: 20:01:00:05:1e:0a:83:6d Permanent Port Name: 20:00:00:11:0d:0f:84:00 Device type: Physical Target

Port Index: 1 Share Area: No Device Shared in Other AD: No Redirect: No Partial: NoThe Local Name Server has 2 entries }

WWPN ____________ Device Type _____________________ State Change Registration (Y/N) ___


73. Return to the open Telnet session of your B300 and issue the nsshow –t -r command.

ST01-B300:admin> nsshow -t -r{ Type Pid COS PortName NodeNameSCR N 010000; 3;10:00:00:05:1e:56:c8:2a;20:00:00:05:1e:56:c8:2a;0x01000003 FC4s: FCP PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST01-HBA | WindowsServer (R) 2008 Standard | Service Pack 1" Fabric Port Name: 20:00:00:05:1e:0a:83:6d Permanent Port Name: 10:00:00:05:1e:56:c8:2a Device type: Physical Initiator

Port Index: 0 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No N 010100; 3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00;0x01000003 FC4s: FCP PortSymb: [36] "Brocade University Virtual FC Target" Fabric Port Name: 20:01:00:05:1e:0a:83:6d Permanent Port Name: 20:00:00:11:0d:0f:84:00 Device type: Physical Target

Port Index: 1 Share Area: No Device Shared in Other AD: No Redirect: No Partial: NoThe Local Name Server has 2 entries }

74. Verify that the storage devices are properly registered with the name server and fabric controller.

Record the last three octets of the Port WWN of the storage ports. Example: 52:3a:72.


63/156







75. From open B5100 Telnet session issue the nscamshow command to see detailed information

about the devices on your B300 switch.

ST01-B5100:admin> nscamshownscam show for remote switches:Switch entry for 1 state rev owner cap_available known v700 0xfffc02 1 Device list: count 2 Type Pid COS PortName NodeName N 010000;3;10:00:00:05:1e:56:c8:2a;20:00:00:05:1e:56:c8:2a; FC4s: FCP

PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST01-HBA |Windows Server (R) 2008 Standard | Service Pack 1" Fabric Port Name: 20:00:00:05:1e:0a:83:6d Permanent Port Name: 10:00:00:05:1e:56:c8:2a Port Index: 0 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No N 010100;3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00; FC4s: FCP

PortSymb: [36] "Brocade University Virtual FC Target" Fabric Port Name: 20:01:00:05:1e:0a:83:6d Permanent Port Name: 20:00:00:11:0d:0f:84:00 Port Index: 1 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No

Switch entry for 3 state rev owner cap_available known v700 0xfffc02 1

Device list: count 1 Type Pid COS PortName NodeName N 030000;3;10:00:00:05:1e:56:c8:2b;20:00:00:05:1e:56:c8:2b; FC4s: FCP PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST01-HBA |Windows Server (R) 2008 Standard | Service Pack 1" Fabric Port Name: 20:00:00:05:33:93:69:40 Permanent Port Name: 10:00:00:05:1e:56:c8:2b


64/156



Port Index: 0 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No

Switch entry for 4

state rev owner cap_available known v700 0xfffc02 1 Device list: count 0 No entry is found!

ST01-B5100:admin>

76. Compare the last three octets of the Port WWN of two device outputs gathered from the B5100

nscamshow output with the B300 nsshow output values gathered earlier. Are they the same?17

____________________________________________________________________

Check Point: You have learned how to determine if a SAN attached device, such as host, storage, ortape device, has successfully logged into the fabric.

Discovering the Fabric

77. Ensure that the Brocade Network Advisor services are running:

a. On the desktop click Start > Programs> Network Advisor 11.1.0> Server Management

Console.

78. On the Services tab click the Start button79. From the desktop open Brocade Network Advisor 11.1.0 application by double-clicking on the icon

80. Log in using the default credentials:

- Username: administrator

- Password: password

81. Select the SAN tab.

17.The nscamshow output does not have an SCR column, otherwise they are the same.


65/156



82. Click Discover > Fabrics

83. Click Add.

84. In the Fabric Name field, enter Fabric XX, where XX is your workstation.

The Fabric Name is used in to differentiate fabrics in Network Advisor. Each fabric you discover

should have a different fabric name.


66/156



85. Using the Student Information Sheet (SIS), enter the IP address for the B5100 in the IP Address

field.

NOTE

If default credentials are used you do not need to enter anything in the User ID or Password fields.


67/156



86. Click OK. This launches the discovery Add Operation.

87. Repeat Step 83 through Step 86 for the B300 and B6510.

- Did you have to go through the discovery process for the B300 or the B6510? Yes or No. If No,

why not?18

____________________________________________________________________

____________________________________________________________________

You can use the switchshow command to display the Node WWN of a switch and the portshow command to display Port WWN of any ports.

88. Return to the Telnet session of your B300.

89. Issue the switchshow command, what is the switchWwn?19

ST01-B300:admin> switchshowswitchName: ST01-B300switchType: 71.2switchState: OnlineswitchMode: NativeswitchRole: Principal

switchDomain: 1switchId: fffc01switchWwn: 10:00:00:05:1e:0a:83:6dzoning: OFFswitchBeacon: OFF.......____________________________________________________________________

18. No. Once the seed switch was discovered, any switch connected to the seed is discovered automatically.

19.The switch WWN is different for each switch, but it should start with 10:00:00:05:1e:xx:xx:xx

http://-/?-http://-/?-http://-/?-http://-/?-


68/156



Helpful Hint

Using the switchshow | more command can be used to page through the output. Beloware some more helpful hints: space - advance one pageenter - advance one lineb — go back one page / — search forward? — search backwards

90. Issue the command portshow 1, what is the portWwn and portWwn of device(s)connected?20

...portId: 010100portIfId: 43020015portWwn: 20:01:00:05:1e:0a:83:6dportWwn of device(s) connected: 20:00:00:11:0d:0f:84:00...

____________________________________________________________________

____________________________________________________________________

____________________________________________________________________

Configuration Backup Using the CLI

91. On the B5100, type the configupload command. Use FTP and the file name should be thename of the switch:

R14-ST08-B5100:admin> configupload Protocol (scp, ftp, sftp, local) [ftp]: ftpServer Name or IP Address [host]: 10.255.252.50User Name [user]: cfaPath/Filename [/config.txt]: R13STxxB5100.txtSection (all|chassis|switch [all]): allPassword: cfa

configUpload complete: All selected config parameters are uploaded

Note

The configupload command was performed using the -all option specified in the inter-action Section.

20.This information is different for each switch and device connection.


69/156



Configuration Save

Documents

Brocade BCFA 16 Gbps Training