Lab Guide CFP300 Rev0114 LG - L

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

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

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

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Configuring FC-FC Integrated Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Switch Start State and Enabling FC Routing Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Backbone Router Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Backbone-to-Edge Fabric 10 (B300) EX-to-E_Port Connections Using the CLI . . . . . . . . . . . 13
Discovering your Fabrics in Brocade Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring EX_Ports using Brocade Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Identify the Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
LSAN Zone Management with Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Verifying FC-FC Routing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Lab Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Module 5: FCIP
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
FCIP Simulation Lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Module 6a Lab: Configuring Flow Vision on the CLI

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Connect to the RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Configuring the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Configuring Flow Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configuring Flow Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuring Flow Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Viewing Flow Vision Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Module 6b Lab: Flow Vision and Network Advisor

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Creating Flows in Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Graphing Flow Vision Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Lab Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
CFP 300 Revision 0114 iii

Module 7a Lab: Using the MAPS CLI
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Enabling MAPS on a Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring Global MAPS Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Creating and Viewing Logical Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Creating Policies and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Enabling MAPS Policies and Testing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Viewing the MAPS CLI Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Viewing the Port Availability Monitor Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Module 7b Lab: Using MAPS With Network Advisor

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Expected Start State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Configuring the MAPS Network Advisor Dashboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Enabling MAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configuring MAPS Using Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configuring MAPS Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Managing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Creating Policies and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Viewing Port Violations on the Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Lab Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Module 8: Virtual Fabrics

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Enabling Virtual Fabrics Using Network Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Create a New Logical Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Discover the Logical Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Verify the Environment Using CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Managing Virtual Fabrics with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Deleting Logical Switches and Disabling Virtual Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Module 9 Lab: Access Gateway

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Reviewing the Pre-Access Gateway Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Open a Telnet Session to the B300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Enabling Access Gateway Mode on the Brocade B300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Managing the Access Gateway Port Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
iv Revision 0114 CFP 300

Configuring Ports 14, 15, and N_Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Changing the Mapping of Host Port 0 to 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Move to the Open Telnet Session on the B5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Testing Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Test Failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Enabling F_Port Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Testing Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Cleaning Up the Lab Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Disabling Access Gateway Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Close Open Sessions and Exit Remote Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
CFP 300 Revision 0114 v

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

Record Remote Lab Access Information

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

Connecting to the Brocade RSL Environment

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

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

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

Close Open Sessions and Exit Remote Connection

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

Objectives
Verify that the edge and backbone fabrics are ready for FC-FC integrated routing activities
Configure a backbone router for FC-FC integrated routing
Configure and verify zone aliases for backbone and edge fabrics
Configure edge-to-edge FC-FC routing across a B5100-based backbone
Lab Environment
FIGURE 1 Lab station diagram

Getting Started
This lab exercise will configure a backbone and 2 edge fabrics for sharing devices while maintaining
fabric services and fault isolation between the fabrics.
To connect to the environment, follow the instructions in Lab 0. You will need information about logins,
passwords, and switch IP address information found in the Student Information Sheet.
1. Verify that your station includes the devices shown.
All devices should be enabled and form a single FC fabric.
Credentials to access switches and RSL station:
User credentials for Remote Desktop to servers:
- Username: Administrator (click Administrator icon)
- Password: brcd
User credentials for Brocade Network Advisor:
- Username: Administrator
- Password: password
User credentials for the B300, B5100, B6510:
- Username: admin
- Password: password
Configuring FC-FC Integrated Routing

In this section, the B5100 will be configured to enable FC-FC Integrated Routing.
2. Please follow the Student Information Sheet (SIS) to connect to your remote desktop.
3. From the desktop, open the PuTTY application.
4. Follow these instructions to establish a CLI session to the B5100, B300 and B6510 switches:
a. To start a Telnet session, double-click on the B5100 entry in the Saved Sessions section.
b. Login using the login credentials provided in SIS. If prompted to change the switch
passwords, type Ctrl+C.
5. Repeat Step3 and Step4 for the B300 and B6510.
NOTE
Keep the Telnet sessions open until you are instructed to close them.
Switch Start State and Enabling FC Routing Services

In this section of the lab we will verify and set the initial settings on the B5100, which will be used as
the backbone fabric (BB) with the B300 and B6510s will be used as the Edge Fabrics (Edge 10 and
Edge 20).

Initial Settings on the B5100

6. From the Telnet window to your B5100, type the switchshow command.
ST01-B5100:admin> switchshow
switchName: ST01-B5100
switchType: 66.1
switchState: Online
switchMode: Native
switchRole: Subordinate
switchDomain: 2
switchId: fffc02
switchWwn: 10:00:00:05:1e:7f:06:9c
zoning: OFF
switchBeacon: OFF
FC Router: OFF
FC Router BB Fabric ID: 1
Address 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 Online FC E-Port 10:00:00:05:33:93:69:3f "ST01-B6510"
(downstream)(Trunk master)
9 9 020900 id N8 Online FC E-Port (Trunk port, master is Port 8 )
10 10 020a00 -- N8 No_Module FC
11 11 020b00 -- N8 No_Module FC
12 12 020c00 -- N8 No_Module FC
13 13 020d00 -- N8 No_Module FC
14 14 020e00 id N8 Online FC E-Port 10:00:00:05:1e:0a:83:6d "ST01-B300"
(upstream)(Trunk master)
15 15 020f00 id N8 Online FC E-Port (Trunk port, master is Port 14 )
<output truncated>
7. Review the switchshow command output from Step6 and fill in the following parameters:
a. switchDomain: ____________________________________1
b. zoning: ____________________________________2
c. FC Router: ____________________________________3
d. List all E_Ports: ____________________________________4
8. Type the licenseshow command and verify the Integrated Routing license is installed.
ST01-B5100:admin> licenseshow
c9SdQeRedATeRK:
1.2
2. There should be no active zoning configuration (zoning output is OFF).
3. The FC Router output should display OFF.
4. Ports 8, 9, 14, 15

Fabric license
bRyRc9RRzbci3Sd6:
Full Ports on Demand license - additional 16 port upgrade
license
PWrGHFKXFHQ4EAMSPWNJFXXSfEYKY7C9BJ9MH:
Enhanced Group Management license
RR3rEXQKTXHHmR3gLYRgF3ttSXS7KM9rBJtSK:
8 Gig FC license
QDQfZS3QWaPmrSDHfrMRGXYFrffr3F9LB7tYN:
Extended Fabric license
Fabric Watch (Fabric Vision capable) license
Performance Monitor (Fabric Vision capable) license
Trunking license
Integrated Routing license
Adaptive Networking - obsolete license
7aACCMPLDAfrRrFJXHZEGHS3FfLf9HAtB7LTA:
Server Application Optimization - obsolete license
Change the Backbone Fabric ID

9. Disable the switch and use the fcrconfigure --bbfid command to set the backbone
fabric ID to 100, be sure to re-enable the switch when you are finished.
ST01-B5100:admin> switchdisable
ST01-B5100:admin> fcrconfigure --bbfid

Backbone fabric ID parameter set. <cr> to skip this parameter
Please make sure new Backbone Fabric ID does not conflict with any
configured EX-Port's Fabric ID
Backbone fabric ID: (1-128)[1] 100
ST01-B5100:admin> switchenable
10. Use the fosconfig --show command and verify that the FC Routing service is
disabled.
ST01-B5100:admin> fosconfig --show
FC Routing service: disabled
iSCSI service: Service not supported on this Platform
iSNS client service: Service not supported on this Platform
Virtual Fabric: disabled
Ethernet Switch Service: Service not supported on this Platform
If the FC Routing service feature is enabled then disable it using the
fosconfig --disable fcr command.
11. Type the switchshow to verify the switch is enabled and the FC BB Fabric ID is set to 100.
switchName:ST01-B5100
switchType:66.1
switchState:Online
switchMode:Native
switchRole:Principal
switchDomain:2

switchId:fffc02
switchWwn:10:00:00:05:1e:7f:06:9c
zoning:OFF
switchBeacon:OFF
FC Router:OFF
FC Router BB Fabric ID:100
Address Mode:0
12. Type the fosconfig --enable fcr command.
ST01-B5100:admin> fosconfig --enable fcr
FC Routing service is enabled
13. Verify the FC Router feature is enabled using the fosconfig --show command.
ST01-B5100:admin> fosconfig --show
FC Routing service:enabled
iSCSI service:Service not supported on this Platform
iSNS client service:Service not supported on this Platform
Virtual Fabric:disabled
Ethernet Switch Service:Service not supported on this Platform
14. Use the portdisable command to disable all E_Ports connected to the B300 and B6510.
ST01-B5100:admin> portdisable 8-9
15. Verify FC router-related values in backbone fabric:
a. Display the FC router switches in the backbone fabric using the fcrfabricshow
command.
ST01-B5100:admin> fcrfabricshow
FC Router WWN: 10:00:00:05:1e:7f:06:9c, Dom ID: 2,
Info: 10.255.224.35, "ST01-B5100"
EX_Port FIDNeighbor Switch Info (enet IP, WWN, name)
------------------------------------------------------------------------
N/A
How many FC router switches appear? 5
____________________________________________________________________
b. Display the FCR physical devices initially configured in backbone fabric using the
fcrphydevshow command.
ST01-B5100:admin> fcrphydevshow
No device found
How many physical devices are there? 6

____________________________________________________________________
c. Display the proxy devices initially configured in backbone fabric using the
fcrproxydevshow command.
ST01-B5100:admin> fcrproxydevshow
No proxy device found
5. One (domain 2)
6. None.

How many proxy devices are there? 7

____________________________________________________________________
d. Display the LSAN zone information in backbone fabric using the lsanzoneshow -s
command.
ST01-B5100:admin> lsanzoneshow -s
No LSAN Zones found.
How many LSAN zones are currently configured? 8
____________________________________________________________________
Based on your answers to questions a through d, are there any devices currently being
shared between any of the fabrics?
____________________________________________________________________9
Initial Settings on the B300

You will be using the B300 as an edge fabric for Fc-FC routing. Currently this switch has one of the
host connections (the other goes to the B6510) and the connection to the storage. To ensure that the
host is only going to be able to see the storage through the FC-FC routing path you will disable the host
connection on the B300.
16. Persistently disable the switch port connecting to the host using the
portcfgpersistentdisable command
ST01-B300:admin> portcfgpersistentdisable 0
17. You can verify the storage is connected to the switch using the nsshow command, the Brocade
University Virtual FC Target device should be the only device connected to the B300 on port 1.
ST01-B300: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: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
LSAN: No
The Local Name Server has 1 entry }
7. None.
8. None.
9. No devices are being shared.

Initial Settings on the B6510s

18. Using PuTTY, Telnet to your stations B6510s.
19. Use the switchshow and nsshow commands to verify the following:
Port 1 (host) is enabled
Ports 8 and 9 are enabled but show No_Light in the State column
Ports 6, 7, 24, and 25 are persistently disabled (these ports connect to the neighboring
station and should remain persistently disabled)
The only device listed in the nsshow output is the HBA for your stations host
Backbone Router Configuration

In this section of the lab, you will perform tasks related to implementing device sharing without
merging fabrics.
Create and verify EX_Port-to-E_Port connections between the backbone fabric B5100 and edge
fabric 10 B300 using CLI.
Create and verify EX_Port-to-E_Port connections between the backbone fabric B5100 and edge
fabric 20 B6510 using Network Advisor.
Backbone-to-Edge Fabric 10 (B300) EX-to-E_Port Connections Using

the CLI
In this section, you will configure EX_Ports on the backbone fabric B5100 to connect to edge fabric 10
B300.
20. Using your SIS or the diagram at the begining of this lab write down the B5100 ports that
connect to your B300:
____________________________________________________________________10
21. Open a Telnet session to the B5100, if not already open.
22. Use the following commands to configure EX_Ports with a fabric ID value of 10 [-f 10] and a
preferred front domain ID value of 5 [-d 5].
a. Type the portcfgexport 14 -a 1 -f 10 -d 5 command for the first port.
b. Type the portcfgexport 15 -a 1 -f 10 command for the second port.
c. Why dont you have to configure the preferred front domain id for the second port? 11
____________________________________________________________________
d. Now enable both EX_Ports using the portenable command.
ST02-B5100:admin> portenable 14-15
10.Ports 14 and 15.

11. All EX_Ports on a FC router going to the same edge fabric will share the same front domain ID (Front
Domain Consolidation).

Discovering your Fabrics in Brocade Network Advisor

In this section you will discover your three fabrics using Brocade Network Advisor.
23. If Network Advisor is not already open, from the desktop of your stations host, launch the
Network Advisor 12.3.0 application.
24. Login using the credentials supplied in the SIS.
25. You will need to discover your stations switches first.
a. Click the SAN tab.
b. Select Discover > Fabrics.
c. Click Add.
d. Type Lab Fabric BB, where XX is your station number, for the Fabric Name (The BB is short
for Back Bone).
e. Type the IP address of your stations B5100 into the IP address field.
f. Leave the User ID and Password fields blank.
g. Click OK.Lab Fabric
26. Repeat step 25 for your B300 switch and use Lab Fabric Edge10 as the fabric name.
27. Repeat step 25 for your B6510s and use Lab Fabric Edge20 as the fabric name.
28. When you have discovered three fabrics (the backbone B5100, edge B300, and edge B6510)
close the Discover Fabrics window and return to the main Network Advisor window.
Configuring EX_Ports using Web Tools

29. Open a web browser and navigate to the IP address of your B5100 switch.
30. Accept any warnings and login using the switch admin account.

31. From the Web Tools window select the Configure > FCR menu.
32. In the FC Router window that opens, click on the EX-Ports tab.
33. Verify the switch name in the left pane is highlighted and click Actions > New.
34. From the Port Selection List click Port 8.
35. Click Add.
36. Click Next.
37. In the drop down list for Fabric ID, select 20.
38. Review the remaining default FC Parameters and accept them by clicking Next.
39. Confirm the settings, click Save and Close.
40. Repeat this procedure for Port 9.
41. Enable both ports by right-clicking and selecting Port Enable.
Identify the Changes

42. Return to the B5100 Telnet session and type the switchshow | grep -i online
command.
ST02-B5100:admin> switchshow | grep -i online
switchState: Online
8 8 020900 id N8 Online FC EX-Port 10:00:00:05:33:92:ea:65 "ST02-B6510"
(fabric id = 20 )(Trunk master)
9 9 020800 id N8 Online FC EX-Port (Trunk port, master is Port 8 )
14 14 020e00 id N8 Online FC EX-Port 10:00:00:05:33:07:5a:dd "ST02-B300"
(fabric id = 10 )(Trunk master)
15 15 020f00 id N8 Online FC EX-Port (Trunk port, master is Port 14 )
Are the ports now online as trunked EX_Ports? 12

____________________________________________________________________
43. Type the fabricshow command. How many domains are present?
ST01-B5100:admin> fabricshow
Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
-------------------------------------------------------------------------
2: fffc02 10:00:00:05:1e:7f:06:9c 10.255.224.35 0.0.0.0 >"ST01-B5100"
Why? 13
____________________________________________________________________
44. Move to the B300 (edge fabric 10) Telnet session and identify the changes seen from these
commands:
a. Type switchshow | grep -i online.
ST02-B300:admin> switchshow | grep -i online
switchState: Online
12. Yes.
13. No additional switches (domains) were added to the backbone fabric, front domains are not presented
in the backbone, and devices are not being shared with the backbone so no translate domains were
added. Therefore the count of 1 domain did not change.

1 1 010100 id N8 Online FC F-Port 20:01:00:11:0d:0f:85:00

14 14 010e00 id N8 Online FC E-Port 50:00:51:e9:cb:23:3e:0a "fcr_fd_5"
15 15 010f00 id N8 Online FC E-Port (Trunk port, master is Port 14 )
Are the ports now online as trunked E_Ports?14

____________________________________________________________________
b. What switch name is attached to the trunk master port? What does this name mean? 15
____________________________________________________________________
c. Type the fabricshow command.
-------------------------------------------------------------------------
1: fffc01 10:00:00:05:1e:0a:83:6d 10.255.224.34 0.0.0.0 >"ST01-B300"
5: fffc05 50:00:51:e7:f0:69:ce:0a 0.0.0.0 0.0.0.0 "fcr_fd_5"
How many front domains are now present? What do you observe about the domain ID of
the new front domain? 16
____________________________________________________________________
d. Type the topologyshow command.
ST02-B300:admin> topologyshow
2 domain(s) in the fabric; Local Domain ID: 1
Domain: 5
Metric: 500
Name: fcr_fd_5
Path Count: 1
Hops: 1
Out Port: 14
In Ports: 1
Total Bandwidth: 16.000 Gbps
Bandwidth Demand: 50 %
Flags: D
How many hops is it to the new front domain?

____________________________________________________________________17
14. Yes.
15. Domain name fcr_fd_5 represents Fibre Channel Router Front Domain with a domain ID of 5 as
specified earlier when we configured EX_Ports -d 5 on the B5100.
16. There is one front domain, with a domain ID of 5 as configured earlier.
17. One hop to the front domain.

CHECK POINT
There should now be four EX_Ports configured on the B5100; two that are attached to edge fabric 10
B300 and two to edge fabric 20 B6510. These ports should form EX_Port trunks with each respective
edge fabric EX_Port. Your topology window in Network Advisor should look similar to the following:
LSAN Zone Management with Network Advisor

This section you provides instructions to enable device sharing between the edge fabrics across the
backbone though the creation and enabling of LSAN zones using Network Advisor.
Use the LSAN Zone Management tool to create LSAN zones in each edge fabric.
Verify FC-FC routing across the backbone fabric B5100 and edge fabrics.
45. Go to Brocade Network Advisor.
46. Expand the objects in the device tree in the left pane.

47. Highlight Lab Fabric BB backbone fabric.

48. Right-click and select Zoning > LSAN Zoning (Device Sharing).
49. Expand all the objects in the device tree in the pane on the left of the Zoning window.
50. Click New Zone.
51. Rename the new zone to LSAN_StXX, where XX is your station number.
52. Select the Brocade Host Adapter port connected to the B6510 and the storage device attached
the B300 and click the arrow button that points to the right to add it to the new LSAN zone you
created.

53. Click Activate.

This opens the Activate LSAN Zones window which allows you to choose which fabrics to create
and activate the new LSAN zone.
NOTE
If a zone configuration is already effective in a given fabric, then the new LSAN zone will be added to
the existing configuration and it will be activated. If no effective configuration is present, a new auto-
matically generated zone configuration will be created and activated.
54. Verify that both the edge fabrics are listed in the Destination Fabrics column. If any are missing,
select it from the Fabrics pane, and click the arrow pointing to the left to add it as a destination.
55. Click OK.

56. Read the information window that comes up and click Yes.
57. Once the successful message comes up, click OK.
58. Click OK to close the Zoning.
59. Give Network Advisor a few minutes to refresh.
Notice that a new device has been added to both the Edge fabrics. What are these new devices
you see in the edge fabrics?
____________________________________________________________________18

60. In the Connectivity Map, right-click the Edge20 and Edge10 fabrics and select View > Connected
End Devices > Show All.
NOTE
The end devices have a blue arrow pointing away from them indicating that they are being exported out
to another fabric.
61. Looking at the device tree for Edge10 expand Routed Products Group > From Lab Fabric
Edge10, you will see the host being imported from the B6510 Edge20 fabric.
62. Return to the B5100 Telnet session and type the fcrproxydevshow command to verify that
the devices are in the Imported state.
Proxy WWN Proxy Device Physical State
Created PID Exists PID
in Fabric in Fabric
----------------------------------------------------------------------------
10 10:00:00:05:1e:56:c8:2b 02f001 20 030000 Imported
20 20:00:00:11:0d:0f:84:00 01f001 10 010100 Imported
Total devices displayed: 2
63. Type the lsanzoneshow command to verify that the LSAN zones have been created in each of
the respective Fabric IDs.
ST01-B5100:admin> lsanzoneshow
Fabric ID: 10 Zone Name: LSAN_stXX
10:00:00:05:1e:56:c8:2b
20:00:00:11:0d:0f:84:00
Fabric ID: 20 Zone Name: LSAN_stXX
18. These are the Translate Domains created by sharing routed devices to these fabrics.

10:00:00:05:1e:56:c8:2b
20:00:00:11:0d:0f:84:00
Verifying FC-FC Routing Configuration

64. Return to the Telnet window for your B300 (edge fabric) and identify the changes seen from
these commands:
a. Type the fabricshow command.
-------------------------------------------------------------------------
1: fffc01 10:00:00:05:1e:0a:83:6d 10.255.224.34 0.0.0.0 >"ST01-B300"
2: fffc02 50:00:51:e7:f0:6b:cf:02 0.0.0.0 0.0.0.0 "fcr_xd_2_20"
5: fffc05 50:00:51:e7:f0:69:ce:0a 0.0.0.0 0.0.0.0 "fcr_fd_5"
How many domains are now present? ____

What is the name and domain ID of the new translate domain associated with Edge20
Fabric? 19 ____________________________________________________________________
19. Three domains exist. The B300 itself, one translate domain, and one front domain. The name of the new
xlate domain fcr_xd_2_20 indicates a translate domain with a domain ID of 2 connected to a fabric
with a FID of 20 (Edge20 fabric.)

65. Type the cfgshow command.

ST01-B300:admin> cfgshow
Defined configuration:
cfg: LSAN_CFG_20131215
LSAN_stXX
zone: LSAN_stXX
20:01:00:11:0D:0F:85:00; 10:00:00:05:1E:57:7C:B5
Effective configuration:
cfg: LSAN_CFG_20131215
zone: LSAN_stXX
20:01:00:11:0d:0f:85:00
10:00:00:05:1e:57:7c:b5
What zone configuration is effective?
____________________________________________________________________20
a. Still on the B300, identify newly imported device from B5100 backbone fabric (the storage
from B5100 backbone fabric) whose PID has the same domain ID as the new translate
domain seen in the previous step using the nsallshow command, and write it here: 21
____________________________________________________________________
ST01-B300:admin> nsallshow
{
010100 02f001
2 Nx_Ports in the Fabric }
b. Type the topologyshow command.

3 domain(s) in the fabric; Local Domain ID: 1
Domain: 2
Metric: 10500
Name: fcr_xd_2_20
Path Count: 1
Hops: 2
Out Port: 14
In Ports: 1
Flags: D
20. An automatically generated zone configuration is effective with a naming scheme of

LSAN_CFG_YYYYMMDD.
21. The proxy PID is 02f001, where 02 indicates the domain ID of the translate domain used to import the
other edge fabric devices, this translate domain exists in the local B300 fabric.

Domain: 5
Metric: 500
Name: fcr_fd_5
Path Count: 1
Hops: 1
Out Port: 14
In Ports: 1
Flags: D
How many hops to the new translate domain, and what is the metric cost? 22
____________________________________________________________________
c. Type the nsshow command. This shows you the contents of the Name Server entries on
the B300 that includes the physical storage port. Use the output of this command for
Step66.
{
TTL(sec)
N 010100;
3;20:00:00:11:0d:0f:84:00;20:00:00:11:0d:0f:84:00; na
FC4s: FCP
Fabric Port Name: 20:01:00:05:1e:0a:83:6d
Port Index: 1
Share Area: No
Redirect: No
Partial: No
The Local Name Server has 1 entry }
____________________________________________________________________
d. Type the nscamshow command. This shows you the contents of the Name Server entries
on the translate domain that includes the imported host from the Edge 20 fabric.
ST01-B300:admin> nscamshow
nscam show for remote switches:
Switch entry for 2
state rev owner cap_available
known v410 0xfffc01 1
Device list: count 1
N 02f001;
3;10:00:00:05:1e:56:c8:2b;20:00:00:05:1e:56:c8:2b;
FC4s: FCP
22. It is 2 hops to the translate domain. The metric cost for the translate domain is 10500.

PortSymb: [89] "Brocade-825 | 3.0.0.0 | ST01-HBA | Windows

Server (R) 2008 Standard | Service Pack 1"
Fabric Port Name: 50:00:51:e7:f0:6b:ca:04
Permanent Port Name: 10:00:00:05:1e:56:c8:2b
Port Index: na
Share Area: No
Redirect: No
Partial: No
Switch entry for 5

state rev owner cap_available
known v410 0xfffc01 1
Device list: count 0
No entry is found!
66. Verify connectivity between the devices using the fcping command:
At the B300 command prompt, type the following command:
fcping <PWWN of storage> <PWWN of Host>
ST01-B300:admin> fcping 20:00:00:11:0d:0f:84:00 10:00:00:05:1e:56:c8:2b
Source:20:00:00:11:0d:0f:84:00
Destination:10:00:00:05:1e:56:c8:2b
Zone Check:Zoned
Pinging 20:00:00:11:0d:0f:84:00 [0x10100] with 12 bytes of data:

received reply from 20:00:00:11:0d:0f:84:00: 12 bytes time:559 usec
5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout
Round-trip min/avg/max = 521/540/559 usec
Pinging 10:00:00:05:1e:56:c8:2b [0x2f001] with 12 bytes of data:

received reply from 10:00:00:05:1e:56:c8:2b: 12 bytes time:3898 usec
5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout
Round-trip min/avg/max = 3292/3454/3898 usec

67. Return to the Telnet window for the B5100, and identify the changes seen in the backbone
fabric:
a. Use the fcrphydevshow command to display the physical devices being shared through
backbone fabric.
Proxy WWN Proxy Device Physical State
Created PID Exists PID
in Fabric in Fabric
----------------------------------------------------------------------------
10 10:00:00:05:1e:56:c8:2b 02f001 20 030000 Imported
20 20:00:00:11:0d:0f:84:00 01f001 10 010100 Imported
Total devices displayed: 2
How many physical devices is the FC router sharing? By reviewing the Fabric IDs, in
which fabrics do the physical devices reside?23
____________________________________________________________________
b. Use the fcrproxydevshow command to display the proxy devices configured in
backbone fabric.
How many proxy devices are there now in backbone fabric? Do the proxy devices match
the physical devices displayed in the previous step? 24
____________________________________________________________________
c. Use the fcrresourceshow command to display the FCR resources in the backbone
fabric .
ST01-B5100:admin> fcrresourceshow
Daemon Limits:
Max Allowed Currently Used
----------------------------------
LSAN Zones: 3000 2
LSAN Devices: 10000 4
Proxy Device Slots: 10000 2
WWN Pool Size Allocated

----------------------------------
Phantom Node WWN: 8192 2
Phantom Port WWN: 32768 4
Port Limits:
Max proxy devices: 2000
Max NR_Ports: 1000
Currently Used(column 1: proxy, column 2: NR_Ports):
8 | 1 2
9 | 0 2
14 | 1 2
15 | 0 2
23. There are two physical devices, one in the edge fabric (FID = 10) and one in edge fabric (FID = 20).
24. There are two proxy devices, one in the edge fabric (FID = 10) and one in edge fabric (FID = 20). The proxy
devices appear in the opposite fabrics as they appeared in the fcrphydevshow output.

How many LSAN zones have now been allocated? How many LSAN devices? How many
proxy devices have been allocated? 25
____________________________________________________________________
d. Use the lsanzoneshow -s command to display the LSAN zones seen by the backbone
fabric.
ST01-B5100:admin> lsanzoneshow -s
Fabric ID: 10 Zone Name: LSAN_St01
10:00:00:05:1e:56:c8:2b Imported
20:00:00:11:0d:0f:84:00 EXIST
Fabric ID: 20 Zone Name: LSAN_St01
10:00:00:05:1e:56:c8:2b EXIST
20:00:00:11:0d:0f:84:00 Imported
How many LSAN zones have now been allocated in the edge fabric (FID = 10) and
backbone fabric (FID = 100)? Does this match the current zone configurations in the
two fabrics? 26
____________________________________________________________________
Important
This concludes the FC-FC Routing lab. Complete the Lab Cleanup on page26 section to prepare for
the next lab.
Lab Cleanup
NOTE
These cleanup steps are required for the remaining exercises in your lab guide.
68. In the Telnet session for the B5100 disable the switch using the switchdisable command.
69. For each configured EX_Port, type the following command, refer to the Figure1 on page7 if
necessary.
ST01-B5100:admin> portcfgdefault 8
70. On the B300 re-enable port 0.
25. Two LSAN zones have been created, four LSAN devices and 2 proxy devices
26.There is one zone in the edge fabric (FID = 10) and one zone in edge fabric (FID = 20). If everything is
correct it will match the zone configurations in the two fabrics.

71. Disable FC-FC Routing on the B5100 using the fosconfig --disable fcr command,
answer y to the prompt.
ST01-B5100:admin> fosconfig --disable fcr
FC Routing service is disabled
72. Enable the switch using the switchenable command.
73. From the Telnet session of the B5100 Type the switchshow and verify all ISLs between the
B5100, B300 and B6510 are online and not segmented.
74. Type the fabricshow command and verify all four of your switches have joined the fabric.
75. After the fabric has stabilized all four switches in the fabric, remove the zoning information from
the fabric using the following commands on the B5100.
a. cfgdisable, answer y to the prompt
ST01-B5100:admin> cfgdisable
You are about to disable zoning configuration. This
action will disable any previous zoning configuration enabled.
Do you want to disable zoning configuration? (yes, y, no, n):
[no] y
Updating flash ...
b. cfgclear, answer y to the prompt
ST01-B5100:admin> cfgclear
The Clear All action will clear all Aliases, Zones, FA Zones
and configurations in the Defined configuration.
Run cfgSave to commit the transaction or cfgTransAbort to
cancel the transaction.
Do you really want to clear all configurations? (yes, y, no, n):
[no] y
c. cfgsave, answer y to the prompt
ST01-B5100:admin> cfgsave
You are about to save the Defined zoning configuration. This
action will only save the changes on Defined configuration.
Any changes made on the Effective configuration will not
take effect until it is re-enabled. Until the Effective
configuration is re-enabled, merging new switches into the
fabric is not recommended and may cause unpredictable
results with the potential of mismatched Effective Zoning
configurations.
Do you want to save Defined zoning configuration only? (yes, y,
no, n): [no] y
Updating flash ...


choose Shutdown.
This ends Module 3: FC-FC Routing lab.

Module 5: FCIP
In this lab exercise, you will configure FCIP solutions between an FX8-24 and a B7800.
Objectives
Upon completion of this lab, you should be able to:
Configure an FCIP tunnel using CLI
Discover your FCIP tunnel using DCFM
Configure a tunnel using DCFM
Implement QoS over FCIP
Add a second circuit to the tunnel
Simulate failover
FCIP Simulation Lab

1. Locate the FCIP demo on the root of your class USB drive. The demo is a self-extracting
executable.
NOTE
This simulation requires Adobe Flash player, if you try to launch the EXE file and nothing hap-
pens (no error messages) please install Adobe Flash.
2. Double-click the CFP300_FCIP_Demo.exe file to launch the executable.
This ends Module 5: FCIP lab.

Module 5: FCIP

In this exercise you will use Flow Vision to configure and monitor flows across a fabric.
Objectives
In this laboratory exercise, you will perform tasks related to configuring Flow Vision flows:
Configuring flows for Flow Monitor
Configuring flows for Flow Mirror
Creating SIM-Ports
Configuring Flow Generator to generate traffic
Viewing Flow Vision configuration
Expected Start State

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 Environment

Since Flow Vision is used to monitor traffic on a SAN, the first step in these labs is to make sure that
there is active traffic. In this section you will first disable the host port connected to the B300 switch,
this will ensure that all storage traffic goes through the B6510. Additionally you will start a traffic
generation utility to actually create the traffic to the storage device.
1. Connect to your stations B300 and issue a portdisable command on port 0.
2. On your host station launch the Kgen application from the desktop. Kgen will be used to create
traffic from the host onto the SAN.
3. On the Test Options tab make sure the following are configured:
Select Physicaldrive2
Change the file size to 800 MB
4. Click Start to begin the test. You can monitor the data throughput using the Stastics tab.
NOTE
Kgen works by creating a test file and then writing it to a disk device. After the file is written it is then
read back and verified. When looking at the traffic profile keep in mind that you will see 1 GB worth of
writes followed by 1 GB worth of reads and then the test will repeat.

Configuring Flow Monitor

5. Using the PuTTY icon on your stations desktop log into your stations B6510.
6. Create a Flow Monitor flow to look at the throughput between your host on port 0 of the B6510
and the storage array on port 1 of the B300.
B6510:admin> flow --create throughput -feature monitor
-ingrport 0 -srcdev 0x030000 -dstdev 0x010100 -bidir
7. Allow the flow to run for a time and view the output using the flow --show throughput
command.
Are the statistics for this flow calculated unidirectionaly or bidirectionaly? How can you
tell?1
____________________________________________________________________
B6510:admin> flow --show throughput
========================================================================================================================
Name : throughputFeatures: mon(Active)noConfig: Off
Definition: IngrPort(0),SrcDev(0x030000),DstDev(0x010100),BiDir
Flow Monitor (Active):

Monitor time: | Mon Aug 19 07:54:00 UTC 2013 |
---------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------
| Frame Count | Frames Per Sec. | Byte count | Throughput(Bps) |Frame Size(Bytes)|
| Tx / Rx / Total | Tx / Rx / Total | Tx / Rx / Total | Tx / Rx / Total | Tx / Rx |
-------------------------------------------------------------------------------------------------------------------
| 15.67M/ 18.33M/ 34.00M|111.39k/127.83k/239.22k| 30.76G/ 36.33G/ 67.10G|224.00M/259.48M/483.49M| 2108 / 2128 |
-------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------
| I/O Count | I/O Per Sec.(IOPS) | I/O bytes Transferred | I/O bytes Per Sec. |
| Reads / Writes/ Total | Reads / Writes/ Total | Reads / Writes/ Total | Reads / Writes/ Total |
-------------------------------------------------------------------------------------------------
| 19.23k/ 22.59k/ 41.83k| 135 / 156 / 291 | 30.65G/ 36.21G/ 66.87G|221.50M/258.16M/479.66M|
-------------------------------------------------------------------------------------------------
The feature Generator is not attached to the flow.
The feature Mirror is not attached to the flow.

========================================================================================================================
8. Delete the flow using the flow --delete throughput command.

9. Create a new flow and look specifically for a frametype of SCSIRead, this time the flow will be
unidirectional.
B6510:admin> flow --create throughput -feature monitor
-ingrport 0 -srcdev 0x030000 -dstdev 0x010100 -frametype SCSIRead
1.The throughput is shown bidirectionaly. You can tell from the flow definition at the top of the show output.

10. Wait a moment to allow traffic to flow and then check the output with the
flow --show throughput command.
ST01-B6510:FID1:admin> flow --show throughput
========================================================================================================================
Name : throughputFeatures: mon(Active)noConfig: Off
Definition: IngrPort(0),SrcDev(0x030000),DstDev(0x010100),FrameType(srd)

---------------------------------------------------------
----------------------------------------
| Rx Frames Count | Rx Frames per Sec. |
----------------------------------------
| 6.98k | 141 |
----------------------------------------
11. After you have looked at the output remove the flow using the flow --delete throughput
command.

Configuring Flow Mirroring

In this section you will use the same traffic flow, but instead of monitoring for specific conditions you
are going to use the Flow Mirror feature to capture the frames.
12. Create a flow using Flow Mirroring to capture frames from the specified port.
B6510:admin> flow --create throughput -feature mirror
-ingrport 0 -dstdev 0x010100 -bidir
13. Wait a minute and view the flow information using the flow --show throughput
command.
ST01-B6510:FID1:admin> flow --show throughput
========================================================================================================================
Name : throughputFeatures: mir(Active)noConfig: Off
Definition: IngrPort(0),DstDev(0x010100),BiDir
Flow Mirror (Active):

-----------------------------------------------------------------------------------------------
| SID(*) | DID(*) | OXID | RXID | SOF | EOF | Frame_type | LUN(*) | Dir | Time-Stamp |
-----------------------------------------------------------------------------------------------
| 030000 | 010100 | 00b1 | 06b4 | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:22:331 |
| 030000 | 010100 | 012f | 0628 | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:22:331 |
| 030000 | 010100 | 014f | 06e0 | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:22:331 |
| 030000 | 010100 | 00d3 | 06ac | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:22:331 |
| 030000 | 010100 | 012f | 0628 | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:22:331 |
| 030000 | 010100 | 014f | 06e0 | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:22:331 |
| 030000 | 010100 | 018d | 0696 | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:22:331 |
| 030000 | 010100 | 0111 | 06c4 | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:22:331 |
| 030000 | 010100 | 00d3 | 06ac | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:22:331 |
<Truncated Output>
| 030000 | 010100 | 0a9d | 0778 | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:26:341 |
| 030000 | 010100 | 0a15 | 070a | SOFn3 | EOFn | Data | ---- | Rx | Aug 19 08:07:26:341 |
| 010100 | 030000 | 09db | 0018 | SOFn3 | EOFn | Data | ---- | Tx | Aug 19 08:07:26:341 |
--------------------------------------------------------------------------------------------
No of Mirrored Frames : 1280, No of RX Mirrored Frames : 736, No of TX Mirrored Frames : 544
--------------------------------------------------------------------------------------------
The feature Monitor is not attached to the flow.
14. You can also see more information using the verbose option,
flow --show throughput -v.
NOTE
The verbose output includes the first 64 bytes of each frame captured. The output is too wide to be
shown correctly in this lab guide.

Configuring Flow Generator

In this section you will configure SIM-Ports and use the Flow Generator feature to generate traffic.
15. Now you will create a simulated F_Ports for the Flow Generator feature.
B6510:admin> flow --control -simport 1 -enable
------|--------|--------------------------|
Index | PID | PWWN |
------|--------|--------------------------|
1 | 030100 | 20:01:00:05:33:93:69:40 |
------|--------|--------------------------|

------|--------|--------------------------|
------|--------|--------------------------|
2 | 030200 | 20:02:00:05:33:93:69:40 |
------|--------|--------------------------|
16. Use the switchshow command to view the SIM-Ports.
Is there anything that differentiates the SIM-Port from a normal F_Port?2
____________________________________________________________________
17. You can also view SIM-Ports in the nsshow output.
Is there anything in the nsshow output that differentiates the SIM-Port from a normal
F_Port?3
____________________________________________________________________
18. Now create the Flow Generator flow to start generating traffic between the two SIM-Ports.
B6510:admin> flow --create traffic -feature generator
-ingrport 1 -srcdev 0x030100 -dstdev 0x030200
19. Open a PuTTY session to your stations B300 and create a SIM-Port on port 4 of the switch.
------|--------|--------------------------|
------|--------|--------------------------|
4 | 010400 | 20:04:00:05:1e:0a:83:6d |
------|--------|--------------------------|
20. Return to the B6510 and create a new Flow Generator flow between the SIM-Port 0x030200
and the new SIM-Port 0x010400 on the B300. At the same time we will also attach this flow to
the monitor feature so we can view the traffic statistics.
B6510:admin> flow --create traffic2 -feature generator,monitor -
ingrport 2 -srcdev 0x030200 -dstdev 0x010400
2.Although the SIM-Port looks like a normal port, it is called out as a SIM-Port in the last column.
3.There is no port or node symbolic information, however, this is not a clear identifier.

21. When the flow has been created use the flow --show traffic2 command to see the flow details.
Notice how the details are displayed for each feature the flow is attached to.
B6510:admin> flow --show traffic2
========================================================================================================================
Name : traffic2Features: gen(Active),mon(Active)noConfig: Off
Definition: IngrPort(2),SrcDev(0x030200),DstDev(0x010400)
Flow Generator (Active):

-----------------------
| SrcDev | DstDev |
-----------------------
| 0x030200 | 0x010400 |
-----------------------
Number of frames generated from IngrPort : 4.94M

---------------------------------------------------------
-----------------------------------------------------------------------------------------------------
| Rx Frames Count | Rx Frames per Sec. | Rx Bytes Count | Rx Throughput(Bps) | Avg Rx Frm Sz(Bytes)|
-----------------------------------------------------------------------------------------------------
| 2.69M | 449.46k | 5.23G | 893.27M | 2084 |
-----------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------
| 0 / 0 / 0 | 0 / 0 / 0 | 0 / 0 / 0 | 0 / 0 / 0 |
-------------------------------------------------------------------------------------------------
22. You can also see the Flow Generator traffic as it crosses the ISL using the portperfshow
command.
23. Disable the traffic2 flow for the Flow Generator feature.
B6510:admin> flow --deactivate traffic2 -feature generator
24. Use the flow --show traffic2 command, notice that the monitor statistics remain but the flow
generator is no longer running.
ST01-B6510:FID1:admin> flow --show traffic2
========================================================================================================================
Name : traffic2Features: gen(Deactivated),mon(Active)noConfig: Off
Definition: IngrPort(2),SrcDev(0x030200),DstDev(0x010400)
Flow Generator (Deactivated at Aug 19 08:41:48:565, showing data collected at deactivation):

-----------------------
| SrcDev | DstDev |
-----------------------
| 0x000000 | 0x000000 |
-----------------------

---------------------------------------------------------
-----------------------------------------------------------------------------------------------------
| Rx Frames Count | Rx Frames per Sec. | Rx Bytes Count | Rx Throughput(Bps) | Avg Rx Frm Sz(Bytes)|
-----------------------------------------------------------------------------------------------------
| 115.90M | 0 | 224.95G | 0 | 2084 |
-----------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------
| 0 / 0 / 0 | 0 / 0 / 0 | 0 / 0 / 0 | 0 / 0 / 0 |
-------------------------------------------------------------------------------------------------

Viewing Flow Vision Configurations

You can use the Flow Vision show commands to see general configuration information about Flows
enabled on a switch.
25. If you want to view all of the flows created on a switch:
How many flows are present on the switch?4
____________________________________________________________________
Which flows are configured to be bidirectional?5
____________________________________________________________________
Which features are the traffic2 flow active for?6
____________________________________________________________________
B6510:admin> flow --show
---------------------------------------------------------------------------------------------------------------------------
Flow Name | Feature | SrcDev | DstDev |IngrPt|EgrPt |BiDir| LUN | FrameType|
---------------------------------------------------------------------------------------------------------------------------
traffic |gen+ |030100 |030200 |1 |- |no |- |- |
traffic2 |gen,mon+ |030200 |010400 |2 |- |no |- |- |
throughput |mir+ |- |010100 |0 |- |yes |- |- |
---------------------------------------------------------------------------------------------------------------------------
+ Denotes feature is currently activated for the flow
26. To show control and SIM-Port information:

B6510:admin> flow --show -ctrlcfg
Default Values of the control parameters
SimPort Information
------|--------|--------------------------|--------------------|--------------------|
Index | PID | PWWN | SID Frame Count | DID Frame Count |
------|--------|--------------------------|--------------------|--------------------|
1 | 030100 | 20:01:00:05:33:93:69:40 | 697369K | 0K |
2 | 030200 | 20:02:00:05:33:93:69:40 | 113252K | 696374K |
------|--------|--------------------------|--------------------|--------------------|
Addressing mode information

Port Addressing Mode : index
Device Addressing Mode: PID
Flow Generator Information

Size: 2048
Pattern: Random (Default)
Flow mirror Information

enable_wrap
27. Before continuing with the next steps delete the throughput flow:
B6510:admin> flow --delete throughput
4.Three flows: traffic, traffic2, and throughput.

5.The throughput flow is configured as bidirectional.
6.The traffic2 flow is only active for the monitor feature, this is denoted by a + next to the feature name.


29. Click Start > Log off administrator in the client window.
30. In the Log Off Windows window click Log Off.
31. Close the Secure Application Manager on your desktop, it is located in your System Tray.
32. Right-click the Secure Application Manager icon (as shown below) and select Sign Out.
This ends the Module 6a Lab: Configuring Flow Vision on the CLI exercise.


In this lab exercise you will use Network Advisor to configure and view Flow Vision flows.
Objectives
In this laboratory exercise, you will perform tasks related to configuring Flow Vision using Network
Advisor.
Configuring flows for Flow Monitor
Configuring flows for Flow Mirror
Configuring Flow Generator to generate traffic
Viewing Flow Vision configuration information
Viewing Flow Vision flows graphically

Creating Flows in Network Advisor

In this exercise you will create several flows in Network Advisor. These flows will be used later to create
traffic graphs.
1. Launch Network Advisor by double-clicking the Network Advisor icon on your lab stations
desktop. The default credentials are administrator / password.
2. Click on the SAN tab, in the navigation pane expand the Lab Fabric entry and then expand the
B6510 entry. Notice that Network Advisor represents your previously created SIM-Ports with a
blue v icon.
3. Right-click on the B6510 entry and select Fabric Vision > Flow > Add from the menu, the Add
Flow Definition window will be displayed.
a. In the Name field enter bna_host_flow.
b. In the Features section put a check next in the Monitor check box.
c. Select the Source to Destination radio button.
d. Under Basic Options enter 030000 in the Source text box and 010100 in the Destination text box.
e. In the Switch section select the D,I radio button and enter 3,0 in the Ingress text box, this is the host
port for your stations host.
f. Expand the Advanced Options section by clicking on it and click the elipses (...) next to the Frame
Type field, the Frame Types Picker dialog will be displayed.

g. Under Available Frame Types select scsiwrite and click the right arrow to add it to the Selected Frame
Types.
h. Click OK to return to the Add Flow Definition window.
030000 010100
i. Click OK, the flow will be created and the Flow Vision monitoring dialog will be displayed.
4. Click Close to return to the main Network Advisor window.
5. Right-click the B6510 entry again, select Fabric Vision > Flow > Add.

6. Create a new flow with the following options, if an option is not mentioned leave it at default:
Name: bna_generator_flow
Features: Generator
Source: 030100
Destination: 010400
Switch: D,I radio button
Ingress: 3,1
7. Click OK to create the flow, the Flow Vision control dialog will be displayed.

Graphing Flow Vision Flows

In this exercise you will use Network Advisor to graph Flow Vision flow results.
8. In the Flow Definitions section select the bna_host_flow and click the right arrow to add it to the
Flows field.
9. Click the arrow next to the Performance Graph button and select real-Time Graph.
10. On the left side select the bna_host_flow, you can scroll to the right to see the name and other
flow information.
11. Select the Receive Frame Rate (f/s) entry and click the right arrow to add it to the graph. You
should see something similar to the image below.
con

12. Click the Select Flows button, the Flow Vision control dialog will be displayed.
13. Select the bna_generator flow and click the right arrow to add it to the Flows column.
14. In the Feature pull-down on the right side select Generator and click the Graph button.
15. Select the bna_generator flow and the Generator Receive Frame Count (count) entry, click the
right arrow to add it to the graph.
16. Click Close to return to the main Network Advisor window.
Lab Cleanup
17. Stop the running KGen test.
18. In BNA select the B6510, right-click and select Flow Vision> Flow> Monitor
19. Select all flows using ctrl+click, from the Flow pull-down select Delete.
20. Log into the B6510 and disable the SIM Ports:
6510:admin> flow --control -simport 1 -disable
6510:admin> flow --control -simport 2 -disable


This ends the Module 6b Lab: Flow Vision and Network Advisor exercise.


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

Connect to the RSL

Enabling MAPS on a Switch

In this exercise you will go through the process of converting Fabric Watch rules to MAPS and enabling
MAPS with a default policy.
1. Using the PuTTY shortcut on your desktop connect to the B300 in your lab station and log in
using the admin account.
2. Begin by checking the status of MAPS using the mapsconfig --show command.
ST01-B300:admin> mapsconfig --show
MAPS not active. Please migrate to MAPS.
3. Use the mapspolicy --show -summary command to see a summary of currently
configured policies. How many default policies are present?1
____________________________________________________________________
ST01-B300:admin> mapspolicy --show -summary
Policy Name Number of Rules
------------------------------------------------------------
dflt_aggressive_policy : 173
dflt_conservative_policy : 175
dflt_moderate_policy : 175
MAPS is not enabled yet.

4. Convert your Fabric Watch rules to MAPS using the mapsconfig --fwconvert command.
ST01-B300:admin> mapsconfig --fwconvert
1.By default MAPS is pre-configured with three policies.

5. When the conversion is complete check the MAPS policy summary one more time using the
mapspolicy --show -summary command. How many MAPS policies are there now?2
____________________________________________________________________
ST01-B300:admin> mapspolicy --show -summary
Policy Name Number of Rules
------------------------------------------------------------
dflt_aggressive_policy : 173
dflt_conservative_policy : 175
dflt_moderate_policy : 175
fw_default_policy : 107
fw_custom_policy : 107
fw_active_policy : 107
MAPS is not enabled yet.

6. Once the Fabric Watch rules have been converted, enable MAPS on the switch with one of the
default policies using the mapsconfig --enable -policy
dflt_conservative_policy command. Read the warning, when you are finished enter y
to proceed.
ST01-B300:admin> mapsconfig --enable -policy
dflt_conservative_policy
WARNING:
This command enables MAPS and replaces all Fabric Watch
configurations and monitoring. Once MAPS is enabled, the Fabric
Watch configuration can't be converted to MAPS.
If you wish to convert your Fabric Watch configuration into MAPS
policies, select NO to this prompt and first issue the "mapsconfig -
-fwconvert" command. Once the Fabric Watch configuration is
concerted into MAPS policies, you may reissue the "mapsconfig --
enablemaps" command to continue this process. If you do not use
Fabric Watch or need the configuration, then select YES to enable
MAPS now.
Do you want to continue? (yes, y, no, n): [no] y
Enabled dflt_conservative_policy policy.
2.There should be six policies now, the three default policies and the three policies created by the Fabric
Watch conversion.

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.
7. Use the mapsconfig --show command, what actions are enabled by default?3
____________________________________________________________________
Configured Notifications: SW_CRITICAL,SW_MARGINAL,SW_HEALTHY
Mail Recipient: Not Configured
Paused members :
===============
PORT :
CIRCUIT :
SFP :
8. Use the mapsconfig --actions command to enable all of the MAPS actions.
NOTE
The action list given in the mapsconfig --actions command will replace the current action
list, it does not add the action to the list. You will need to put the full list of actions you want to
enable in the command, even if some of the actions are already enabled.
ST01-B300:admin> mapsconfig --actions

RASLOG,FENCE,SW_CRITICAL,SW_MARGINAL,SFP_MARGINAL
9. Use the mapsconfig --show command one more time to verify the actions have been
enabled.
Configured Notifications:
RASLOG,FENCE,SW_CRITICAL,SW_MARGINAL,SW_HEALTHY,SFP_MARGINAL
Mail Recipient: Not Configured
Paused members :
===============
PORT :
CIRCUIT :
SFP :
3.By default the SW_CRITICAL, SW_MARGINAL, and SW_HEALTHY actions are enabled.

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.
10. Before beginning look at the default logical groups using the logicalgroup --show
command.
ST01-B300:admin> logicalgroup --show
---------------------------------------------------------------------------------------------------------
Group Name |Predefined |Type |Member Count |Members
---------------------------------------------------------------------------------------------------------
ALL_PORTS |Yes |Port |24 |0-23
NON_E_F_PORTS |Yes |Port |20 |2-3,5-13,16-23
ALL_E_PORTS |Yes |Port |2 |14-15
ALL_F_PORTS |Yes |Port |2 |0-1
ALL_OTHER_F_PORTS |Yes |Port |0 |4
ALL_HOST_PORTS |Yes |Port |1 |0
ALL_TARGET_PORTS |Yes |Port |1 |1
ALL_TS |Yes |Temperature Sensor|3 |0-2
ALL_FAN |Yes |Fan |3 |1-3
ALL_WWN |Yes |WWN |1 |1
ALL_PS |Yes |Power Supply |1 |1
ALL_SFP |Yes |Sfp |4 |0-1,14-15
ALL_10GSWL_SFP |Yes |Sfp |0 |
ALL_10GLWL_SFP |Yes |Sfp |0 |
ALL_QSFP |Yes |Sfp |0 |
ALL_FLASH |Yes |Flash |1 |0
ALL_CIRCUITS |Yes |Circuit |0 |
SWITCH |Yes | |1 |0
CHASSIS |Yes | |1 |0
11. 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?4
____________________________________________________________________
4.On this switch you will see ports 0-1 in the ALL_F_PORTS group and ports 14-15 in the ALL_E_PORTS
group.

12. Disable ports 0-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?5
____________________________________________________________________
ST01-B300:admin> logicalgroup --show
---------------------------------------------------------------------------------------------------------
-----
Group Name |Predefined |Type |Member Count |Members
---------------------------------------------------------------------------------------------------------
-----
ALL_PORTS |Yes |Port |24 |0-23
NON_E_F_PORTS |Yes |Port |24 |0-23
ALL_E_PORTS |Yes |Port |0 |
ALL_F_PORTS |Yes |Port |0 |
ALL_OTHER_F_PORTS |Yes |Port |0 |
ALL_HOST_PORTS |Yes |Port |0 |
ALL_TARGET_PORTS |Yes |Port |0 |
ALL_TS |Yes |Temperature Sensor|3 |0-2
ALL_FAN |Yes |Fan |3 |1-3
ALL_WWN |Yes |WWN |1 |1
ALL_PS |Yes |Power Supply |1 |1
ALL_SFP |Yes |Sfp |4 |0-1,14-15
ALL_QSFP |Yes |Sfp |0 |
ALL_FLASH |Yes |Flash |1 |0
ALL_CIRCUITS |Yes |Circuit |0 |
SWITCH |Yes | |1 |0
CHASSIS |Yes | |1 |0
13. Re-enable ports 0-1 and 14-15.

14. Create a logical group that contains the two F_Ports (0 and 1) called critical_ports.
ST01-B300:admin> logicalgroup --create critical_ports -type port
-members 0,1
15. You can use the logicalgroup --show critical_ports command verify the group was
created with the correct members.
16. Now add the E_Ports to the same group and verify using the logicalgroup --show
command.
ST01-B300:admin> logicalgroup --addmember critical_ports
-members 14,15
5.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.
17. 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-B300:admin> mapsrule --create port_state_change
-group critical_ports -monitor state_chg -timebase min -op g
-value 1 -action raslog
18. Verify the rule using the mapsrule --show command. Is this rule currently associated with
any policies?6
ST01-B300:admin> mapsrule --show port_state_change
Rule Data:
----------
RuleName: port_state_change
Condition: critical_ports(state_chg/min>1)
Actions: raslog
Associated Policies:
19. Create an empty policy named lab_policy using the mapspolicy --create command
ST01-B300:admin> mapspolicy --create lab_policy
20. Now add the port_state_change rule you created in step 18 to the new policy.
ST01-B300:admin> mapspolicy --addrule lab_policy -rulename
port_state_change
21. Verify the new policy using the mapspolicy --show and mapsrule --show commands.
ST01-B300: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_conservative_policy'.
ST01-B300: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
22. With the current MAPS configuration will this rule be active on the switch? Why?7
____________________________________________________________________
____________________________________________________________________
6.No, this rule is not associated with any policies currently.

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

23. 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-B300:admin> mapsrule --create E_Port_Down -group switch
-monitor EPORT_DOWN -timebase min -op g -value 2 -action RASLOG
-policy lab_policy
24. At this point you can verify the rules in your policy using the mapspolicy --show command.
R14-ST01-B300: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_copnservative_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.
25. Enable the policy you just created using the mapspolicy --enable command.
ST01-B300:admin> mapspolicy --enable lab_policy
26. Test the new policy by disabling and enabling one of the ports in the critical_ports group.
ST01-B300:admin> portdisable 0
ST01-B300:admin> portenable 0
27. Check the RASLog to make sure that a message was generated.
ST01-B300:admin> errshow -r
Fabric OS: v7.2.0a_rc1_bld03
2013/08/09-11:56:29, [MAPS-1003], 907, FID 128, WARNING, R14-ST01-

B300, Port 0, Condition=critical_ports(STATE_CHG/min>1), Current
Value:[STATE_CHG,2], RuleName=port_state_change, Dashboard
Category=Port Health.
28. Check the second rule that you created by disabling one of the E_Ports on the B300. Try
disabling and re-enabling port 14 several times. When you are done check the RASLog, what do
you see?8
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
8.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.

29. Now, disable port 15 and try disabling and re-enabling port 14 a few more times. Does this
trigger the E_Port_Down rule?9
____________________________________________________________________
30. 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.
31. 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?10
____________________________________________________________________
____________________________________________________________________
In section 3.2 Rules Affecting Health, which rules have been triggered?11
____________________________________________________________________
____________________________________________________________________
32. 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?12
____________________________________________________________________
____________________________________________________________________
9.Yes it does.
10.Port Health and Fabric State Changes show an abnormal status for today because of the rules you
created and triggered.
11.The port_state_change and E_Port_Down rules have been triggered.
12.Yes, there should be state change events for ports 0, 14, and 15.

ST01-B300: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) | | | | | |
R14-ST01-B300: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.
33. View the port availability monitor report using the mapssam --show command.
Do any of your switch ports show any downtime?13
____________________________________________________________________
What does the T in the Type column indicate on ports 14 and 15?14 (Hint: use the help
files if needed).
____________________________________________________________________
ST01-B300:admin> mapssam --show
Total Total Down Total

Port Type Up Time Down Time Occurrence Offline Time
(Percent) (Percent) (Times) (Percent)
======================================================================
0 F 98.78 0.00 0 1.22
1 F 100.00 0.00 0 0.00
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 T 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
21 U 0.00 0.00 0 100.00
22 U 0.00 0.00 0 100.00
23 U 0.00 0.00 0 100.00
13.Ports 0, 14, and 15 should show a small percentage of downtime.

14.The T stands for trunk port. MAPS recognizes that ports 14 and 15 are in a valid trunk and not just
individual E_Ports.


This ends the Module 7a 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
Enabling MAPS on a switch 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 B300, 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


Configuring the MAPS Network Advisor Dashboards

In this exercise you will configure the MAPS dashboards for 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.
1. Switch to the Product Status and Traffic tab.
2. Close all of the dashboards by clicking the small x in the top right corner of each one. This is to
reduce clutter for the labs.
3. Click the wrench icon (Customize Dashboard button) on the left side of the control bar, the
Customize Dashboard window will display.
4. In the display column put a check next to the following dashboards:
Out of Range Violations
Port Health Violations
ISL Port Health Violations
Initiator Port Health Violations
Target Port Health Violations
5. With the dashboards setup you can now configure MAPS on one of your other switches.
Enabling MAPS
Network Advisor can enable MAPS on multiple chassis at once. You do not need to manually convert
the Fabric Watch policies either, Network Advisor does this automatically.
6. Return to the SAN tab.
7. In the navigation tree expand the Lab Fabric entry and select the B5100 switch.
8. From the menus choose Monitor > Fabric Vision > MAPS > Enable, the Enable MAPS dialog will
be displayed.
9. The B5100 switch should already be in the Selected Switches column
10. In the Available Switches column select your stations B6510 and click the right arrow.

11. Click OK and read the Network Advisor Message.
12. Click Yes to enable MAPS on the two switches.
13. Return to the SAN tab and look at the Master Log at the bottom of the window. You will see a
number of product events generated from the automatic conversion of Fabric Watch policies
and enabling MAPS on the switches.

Configuring MAPS Using Network Advisor
14. In the navigation tree on the left, right-click the B6510 entry and select
Fabric Vision > MAPS > Configure, the MAPS Configuration dialog will be displayed with the
selected switch information already expanded.
What is the active policy for the B6510 switch?1
____________________________________________________________________
Look at the columns to the right of the switch, be sure to scroll. Which actions are enabled
on the B6510 switch?2
____________________________________________________________________
1.fw_active_policy, this is the policy that Network Advisor enables by default when MAPS is enabled.
2.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.
15. In the MAPS Configuration dialog select the Lab Fabric entry and click the Actions button on the
right.
16. Click Enable All then click OK, the Set Action Status window will be displayed.
17. Verify that the action was successful on all four switches and click Close to return to the MAPS
Configuration dialog.

18. Network Advisor can also be used to configure an individual switch. Select the B5100 switch
and click the Actions button on the right.
19. Un-check the E-mail action and click OK, the Set Action Status dialog will be displayed.
20. Verify the action was successful and click Close to return to the MAPS Configuration dialog.
21. You will now see that the green check is missing from the E-mail column of the B5100.
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.
22. 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?3
____________________________________________________________________
23. In the Available Ports column expand the Products entry to view all your fabric switches.
3.You will see the critical_ports group that was created in the previous lab.

24. Click the Add button in the lower left corner, the Add Group dialog will be displayed.
25. In the Name field enter ISLtoB5100.
26. In the Type pull-down leave the default selection of PORT.
27. Click OK.
28. Create a second group with the name HostPort of type PORT.
29. Select the ISLtoB5100 group.
30. In the Available Ports column expand the B300 and select ports 14 and 15. Click the right arrow
to add those ports to the Selected Ports column.
NOTE
You can select multiple items in a list by using Shift + click or Ctrl + click.
31. Expand the B6510 entry and select ports 8 and 9. Click the right arrow to add those ports to the
Selected Ports column.

32. Use the same procedure to assign the following ports to the HostPort group:
HostPort
B300 port 0
B6510 port 0
33. When you have finished setting up the groups click OK to apply the changes to the switches, the
Manage Groups dialog will be displayed.
34. 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, they can then 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.
35. Expand your B6510 switch and select the dflt_aggressive_policy.
36. Click the Add button on the right, the Add Policy dialog will be displayed. The existing rules for the
policy will be populated automatically.
37. In the Name field enter dflt_clone_policy.
38. 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)4
____________________________________________________________________
What percentage of the flash memory needs to be in use before a rule is triggered?5
____________________________________________________________________
4.A RASLog, SNMP trap, and email are generated.

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

39. Click on the Port tab. Are there any rules which would cause a port to be fenced if triggered?6
____________________________________________________________________
40. Click OK to create the newly cloned policy and return to the MAPS Configuration dialog.
6.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

41. Select the B6510 switch and click Add. The Add Policy dialog will be displayed with an empty
policy.
42. In the Name field enter BNA_Policy.
43. On the Port tab, In the Groups / Rules field select the HostPort group.
44. 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.
45. In the Measure pull-down select State Changes (STATE_CHG).
46. In the Threshold section set the operand drop-down to the greater than or equal symbol >=
and the count to 1.
47. Set the TimeBase drop-down to Min.
48. Under Actions put check marks next to RAS Log Event and Fence.
49. Click the right arrow to add the rule to the policy.
50. Click OK to create the policy on the switch and return to the MAPS Configuration dialog.

Editing an Existing Policy

51. If it is not already select the BNA_Policy you just created.
52. Click the Edit button, the Edit Policy dialog will be displayed.
53. Select the Fabric tab.
54. 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
55. 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.
56. Click OK to finish editing the rule and return to the MAPS Configuration dialog.

Distributing Policies to Other Switches in the Fabric

Network Advisor will allow you to distribute a policy from one switch 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.
these automatically generated logical groups will not be populated however.
57. Select the BNA_Policy you just finished creating and editing.
58. Click the Distribute button, the Distribution Options dialog will be displayed.
59. Leave the radio buttons at their defaults and select OK, a Network Advisor Message dialog will
be displayed.
60. Read the warning and click Yes to finnish the distribution, when the process is finished the
Distribute Policy Status dialog will be displayed.
61. Click Close to return to the MAPS Configuration dialog.
62. 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.
63. Minimize Network Advisor and launch Host Connectivity Manager using the icon on your
stations desktop. The default credentials are administrator / password.
64. Expand the top port (this is port 0 on the HBA) and right-click on the FC Port instance, this will be
the second port down in the tree (see the graphic below for an example).
65. Click the Enable Port entry to remove the check mark and disable the port, an HCM Message
dialog will be displayed.
66. Read the message and click OK to disable the port.
67. Wait a moment and then repeat this process to re-enable the port. This will trigger the
fence_host_ports rule created earlier and will result in port 0 on the B300 being fenced.
68. Use the PuTTY icon on your desktop to log into the B300 in your lab station.

69. Use the switchshow command to verify that the port has been fenced:
switchName: R14-ST01-B300
switchType: 71.2
switchState: Online
switchMode: Native
switchRole: Principal
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:05:1e:0b:55:3f
zoning: OFF
switchBeacon: OFF

==================================================
0 0 010000 id N8 In_Sync FC Disabled (Port State Change threshold exceeded)
<Output Truncated>
70. Return to your Network Advisor window and change to the Product Status and Traffic tab.
Do you see any violations shown in the dashboards?7
____________________________________________________________________
Which dashboards show violations? Why?8
____________________________________________________________________
7.Yes, there are port health violations shown on the Network Advisor dashboards.
8.The following dashboards 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).

71. In the Initiator Port Health Violations dashboard right-click on the port and choose Locate, you
will be taken to the SAN tab and the port will be highlighted.
72. Right-click on the port and select Enable / Disable > Enable to re-enable the port, a Network
Advisor Message dialog will be displayed.
73. Read the message and click Yes to finish enabling the port.
74. 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.
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.
75. 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.


This ends the Module 7b Lab: Using MAPS With Network Advisor exercise.

Objectives
In this lab exercise, you will perform tasks related to FC-FC routing:
Enable Virtual Fabrics on your B5100
Implement routing on the B5100 base switch
Implement TI zones over a routed fabric backbone
Lab Environment

Enabling Virtual Fabrics Using Network Advisor

You will now enable Virtual Fabrics on the B5100. This requires a reboot of the switch and is disruptive
to the traffic flowing on this switch.
81. Locate the B5100 in the Connectivity Map, right-click and select Virtual Fabric > Enable.
82. Review the warning and consider the impacts of enabling VF then click OK.
It is necessary to wait several minutes (3-5 minutes) as the B5100 reboots. The B5100 icon will
change in the Network Advisor window as it goes through this process.
NOTE
When you enable Virtual Fabrics, the chassis is automatically rebooted. When the switch comes up,
only one default logical switch is present, with the default fabric ID (FID) of 128.
Notice there is now a V above the B5100 icon denoting that Virtual Fabrics is enabled.

Create a New Logical Switch

83. When the B5100 is communicating with Network Advisor again (its icon status symbols will
disappear), select Configure > Virtual Fabrics > Logical Switches from the main menu bar.

84. In the Logical Switches dialog box, click New Fabric to create a new fabric template for logical
switches.
85. Replace the value of the Logical Fabric ID with 100.

86. Review the other options available to configure the new fabric template. The fabric template acts
as a container for all of the logical switch attributes created in it. Click OK when finished.
A new fabric template has been created that is called NewFabric. Notice that in the FID column
the value of 100 has been assigned.
87. Select the NewFabric entry in the Existing Logical Switches field.
88. Click New Switch.
89. The same information is displayed that was used to configure the fabric. Uncheck Base Fabric
for Transport.

90. Click Switch and enter B5100_LS100 the name.
91. Click the OK button.

92. Verify the B5100 is selected in the Chassis drop down list.
93. Select the E_Ports connecting to the B300 in the ports list.
94. In Existing Logical Switches, verify the new logical switch is highlighted.
95. Add the selected ports to new logical switch by clicking the right-arrow.

96. Click the OK button.

97. Review the changes to be made. Leave the default settings and click the Start button to commit
the configuration to the fabric.
NOTE
This procedure could take several minutes to complete.When the Status field changes to Success,
review the status window output and then click the Close button to continue.
98. Your Network Advisor topology map will now indicate that you have missing elements in the
fabric with the red circle with a dash icon.

99. Select your fabric name in the device tree pane on the left and right-click it, select Accept
Change(s).
100. Click the Yes button to accept. This will remove the missing devices from that fabrics device
tree and topology map.
Discover the Logical Fabric

101. From the main menu bar select Discover > Fabrics.
102. In the Previously Discovered Addresses pane at the bottom, select the B300 in your station.
Click the Discover button.
103. Type B300 as the fabric name. Click the OK button.
104. Close the Discover Fabrics window.
105. With the current configuration should the host port connected to the B6510 be able to
communicate with the storage port on the B300? __________1
Verify the Environment Using CLI

106. Double-click the PuTTY icon on the desktop of your host.
107. Double-click the B5100 entry in the saved sessions list.
108. Login using the admin/password login credentials.
109. Type the fosconfig --show command. Virtual Fabric should be enabled.
1. No, they now reside in separate fabrics.

ST02-B5100:FID128:admin> fosconfig --show

FC Routing service: disabled
iSCSI service: Service not supported on this Platform
iSNS client service: Service not supported on this Platform
Virtual Fabric: enabled
Ethernet Switch Service:Service not supported on this Platform
110. According the the switch prompt, which FID are you currently logged into? __________2
ST02-B5100:FID128:admin>
111. Type the switchshow command. Why are there some ports missing from the output?
ST02-B5100:FID128:admin> switchshow
switchType:66.1
switchState:Online
switchMode:Native
switchDomain:2
switchId:fffc02
switchWwn:10:00:00:05:1e:9c:b2:33
zoning:OFF
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF
LS Attributes:[FID: 128, Base Switch: No, Default Switch: Yes,
Address Mode 0]

==============================================
0 0 020000 -- N8 No_Module FC
1 1 020100 -- N8 No_Module FC
2 2 020200 -- N8 No_Module FC
3 3 020300 -- N8 No_Module FC
4 4 020400 -- N8 No_Module FC
5 5 020500 -- N8 No_Module FC
6 6 020600 -- N8 No_Module FC
7 7 020700 -- N8 No_Module FC
8 8 020900 id N8 Online FC E-Port (Trunk
port, master is Port 9 )
9 9 020800 id N8 Online FC E-Port
10:00:00:05:33:93:69:7f "R15-ST02-B6510" (downstream)(Trunk master)
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
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
2. 128, this is the default setting for the Default logical switch that is created when Virtual Fabrics is enabled.

____________________________________________________________________3
112. Type the lscfg --show command.
ST02-B5100:FID128:admin> lscfg --show
Created switches FIDs(Domain IDs): 128(ds)(2) 100(2)
Port 0 1 2 3 4 5 6 7 8 9
-------------------------------------------------------------------
FID 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 |
Port 10 11 12 13 14 15 16 17 18 19
-------------------------------------------------------------------
FID 128 | 128 | 128 | 128 | 100 | 100 | 128 | 128 | 128 | 128 |
Port 20 21 22 23 24 25 26 27 28 29
-------------------------------------------------------------------
FID 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 |
Port 30 31 32 33 34 35 36 37 38 39
-------------------------------------------------------------------
FID 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 |
113. Which ports are listed as assigned to FID 100? __________4

114. Type the setcontext 100 command. Notice that your prompt changes to FID 100 context.
ST02-B5100:FID128:admin> setcontext 100
B5100_LS100:FID100:admin>
3. The switchshow command only shows the specific switch information that you are logged into. The missing
ports are assigned to a different logical switch and do not show up here.
4. 14 and 15

115. Type the switchshow command. Only the ports assigned to this logical switch will be shown.
B5100_LS100:FID100:admin> switchshow
switchName:B5100_LS100
switchType:66.1
switchState:Online
switchMode:Native
switchDomain:2
switchId:fffc02
switchWwn:10:00:00:05:1e:9c:b2:34
zoning:OFF
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF
LS Attributes:[FID: 100, Base Switch: No, Default Switch: No, Address Mode 0]

==============================================
15 15 020100 id N8 Online FC E-Port 10:00:00:05:33:07:5a:dd "ST02-B300"
116. What is the status of the Allow XISL Use feature? __________5
Managing Virtual Fabrics with CLI

In this section you will move ports between logical switches and enable the base switch functions in
the FID 128 switch.
117. From LS100, use the port numbers connected to the B300 and move them from FID 100 back
to the default switch FID 128.
B5100_LS100:FID100:admin> lscfg --config 128 -port 14-15
This operation requires that the affected ports be disabled.
Would you like to continue [y/n]?: y
Making this configuration change. Please wait...
Configuration change successful.
Please enable your ports/switch when you are ready to continue.
118. Type the switchshow command. How many ports are listed? __________6
NOTE
Logical switches with no ports assigned can be created as staging areas for preparing the switch for
your environment, including fabric parameters, zoning, security policies and other features.
119. Return to the default logical switch context using the setcontext 128 command.
5. OFF. When the check mark next to Base Fabric for Transport option was removed, it sets this feature to
OFF.
6. 0, zero: No ports found in the system!!!

120. Type the switchshow command. Notice that ports you just moved from the other FIDs are
disabled.
ST02-B5100:FID128:admin> switchshow
switchType:66.1
switchState:Online
switchMode:Native
switchDomain:2
switchId:fffc02
switchWwn:10:00:00:05:1e:9c:b2:33
zoning:OFF
switchBeacon:OFF
FC Router:OFF
Allow XISL Use:OFF
LS Attributes:[FID: 128, Base Switch: No, Default Switch: Yes, Address Mode 0]

==============================================
0 0 020000 -- N8 No_Module FC
<output truncated>
13 13 020d00 -- N8 No_Module FC
14 14 020e00 id N8 In_Sync FC Disabled
15 15 020f00 id N8 In_Sync FC Disabled
16 16 021000 -- N8 No_Module FC
<output truncated>
121. Use the portenable command to enable ports 14 and 15.
Deleting Logical Switches and Disabling Virtual Fabrics

In the CLI, to delete a logical switch, all ports that were assigned to it must be removed. The logical
switch cannot be deleted if any ports are still assigned to it, even if there are no devices attached to
them or if they are disabled.
To disable the Virtual Fabrics service, all logical switches except the default logical switch must first
be deleted.
In Network Advisor, removing ports from logical switches to be deleted and deleting non-default logical
switches when disabling VF is automated. Ports are automatically moved to the default switch
122. Verify that you are in the context of FID 128. Deleting a logical switch also terminates any
management sessions to that switch.
123. Delete FID 100 using the lscfg --delete 100 command.
ST02-B5100:FID128:admin> lscfg --delete 100
Termination of all active login sessions for FID 100 has failed.
Switch successfully deleted.

NOTE
There are no warning messages after you type this command. You may get a Termination of
all active login sessions for FID 100 has failed. message after this completes. This is ok.
124. Type the lscfg --show command to verify that FID 100 has been deleted.
ST02-B5100:FID128:admin> lscfg --show
Created switches: 128(ds) 2
Port 0 1 2 3 4 5 6 7 8 9
-------------------------------------------------------------------
FID 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128
Port 10 11 12 13 14 15 16 17 18 19
-------------------------------------------------------------------
FID 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 |
Port 20 21 22 23 24 25 26 27 28 29
-------------------------------------------------------------------
FID 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 |
Port 30 31 32 33 34 35 36 37 38 39
-------------------------------------------------------------------
FID 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 | 128 |
____________________________________________________________________
125. Return to Network Advisor and expand the Chassis Group in the device tree pane on the left.
126. Right-click the B5100 in the Chassis Group and select Virtual Fabric > Disable.
127. Click the OK button after the consideration timer counts down.


choose Shutdown.
This ends Module 8: Virtual Fabrics.

Objectives
Implement, troubleshoot, and support Access Gateway on a Brocade B300 switch.
Overview
The next page shows the default Access Gateway configuration. On the right is the configuration
performed in this lab. To complete this, you will need to do the following:
Review pre-Access Gateway environment
Enable Access Gateway Mode
Unmap ports 14 and 15
Enable ports 14 and 15 as N_Ports
Map server connected to port 0 to port 14
Test failover/failback
Enable F_Port Trunking
Test failover - verify the host 24-bit address does not change
Disable Access Gateway mode

Connect to the RSL

If you are not already connected, use the instructions in Remote Lab Access InstructionsRemote Lab
Access Instructions of this book and the information on your Student Information Sheet (SIS) to
reconnect to your RSL station.
FIGURE 1 Access Gateway Configuration
Reviewing the Pre-Access Gateway Environment

In this section, you will review the pre-Access Gateway environment on the Brocade B300 and B5100.
Open a Telnet Session to the B300

1. Double click the PuTTY icon on the host desktop.
2. Double click the B300 entry in Saved Sessions.
3. Login using the credentials provided in the SIS.
4. Use the switchshow command to display the switch and port status.
switchType:71.2
switchState:Online
switchMode:Native
switchDomain:1
switchId:fffc01
switchWwn:10:00:00:05:33:07:5a:dd
zoning:OFF
switchBeacon:OFF


==============================================
0 0 011700 id N8 In_Sync FC Disabled (Persistent)
1 1 011500 id N8 Online FC F-Port 20:01:00:11:0d:0f:85:00
<output truncated>
5. Confirm that ports 0, 1, 14, and 15 are enabled. If necessary, enable them using the
portcfgpersistentenable <port#> command for each port number to enable.
ST02-B300:admin> portcfgpersistentenable 0
6. Use the nsshow command to display the local Name Server on the B300.
{
Type Pid COS PortName NodeName TTL(sec)
N 010000; 3;10:00:00:05:1e:57:7c:b4;20:00:00:05:1e:57:7c:b4; na
FC4s: FCP
PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST02-HBA | Windows Server (R)
2008 Standard | Service Pack 1"
Fabric Port Name: 20:00:00:05:33:07:5a:dd
Permanent Port Name: 10:00:00:05:1e:57:7c:b4
Port Index: 0
Share Area: No
Redirect: No
Partial: No
N 010100; 3;20:01:00:11:0d:0f:85:00;20:01:00:11:0d:0f:85:00; na
FC4s: FCP
Fabric Port Name: 20:01:00:05:33:07:5a:dd
Port Index: 1
Share Area: No
Redirect: No
Partial: No
The Local Name Server has 2 entries }
What is the FC address (PID) of the server connected to port 0?
____________________________________________________________________1
Enabling Access Gateway Mode on the Brocade B300

In this section, you will configure the Brocade B300 for Access Gateway. All commands in this section
are executed on the Brocade B300.
7. Return to the B300 Telnet session.
8. Disable the switch with the switchdisable command.
1. The server should have a PID of 010000.

NOTE
The standard process for enabling the Access Gateway feature on the Brocade B300 includes
uploading the switch configuration. This lab does not include this step.
9. Enable Access Gateway mode on the Brocade B300 using the ag --modeenable command.
Review the command output, and at the Do you want to continue? prompt, type y.
ST02-B300:admin> ag --modeenable
WARNING: Access Gateway mode changes the standard behavior of the
switch. Please check Access Gateway Administrator's Guide before
proceeding.
Enabling agmode will remove all the configuration data on the switch
including zoning configuration and security database. Please backup
your
configuration using configupload.
This operation will reboot the switch.
Access Gateway mode was enabled successfully
Switch is being rebooted...
Important
The Brocade B300 switch now reboots.
10. Wait a couple of minutes for the Brocade B300 to reboot, then re-open a CLI session to the
B300.
11. Verify that Access Gateway mode has been enabled with the ag --modeshow command.
ST02-B300:admin> ag --modeshow
Access Gateway mode is enabled.
- Is Access Gateway mode now enabled? ____________________________2

12. Type the switchshow and note switchMode: _______________________________3
switchType:71.2
switchState:Online
switchMode:Access Gateway Mode
switchWwn:10:00:00:05:33:07:5a:dd
switchBeacon:OFF
==============================================
0 0 010000 id N8 In_Sync FC Disabled (N-Port Offline for F-Port)
1 1 010100 id N8 No_Sync FC Disabled (N-Port Offline for F-Port)
2 2 010200 -- N8 No_Module FC
<output truncated>
14 14 010e00 id N8 In_Sync FC Disabled (N-Port Offline for F-Port)

15 15 010f00 id N8 In_Sync FC Disabled (N-Port Offline for F-Port)
<output truncated>
2. The command output should state Access Gateway mode is enabled.

3. Access Gateway Mode

13. Why are some ports disabled?

____________________________________________________________________4
CHECK POINT
You have now enabled Access Gateway mode on the Brocade B300.
Managing the Access Gateway Port Map

In this section, you will review the default Access Gateway port mapping.
14. Continuing with the B300 Telnet session.
15. Use the portcfgnport command to display the default N_Port configuration.
ST02-B300:admin> portcfgnport
Ports 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
--------------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
Locked N_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ON ON ON ON ON ON ON ON
- Which Brocade B300 ports are now configured as N_Ports?

_________________________________________________5
16. Display the default Access Gateway port map with the ag --mapshow command.
ST02-B300:admin> ag --mapshow
N_Port Configured_F_Ports Static_F_Ports Current_F_Ports Failover Failback PG_ID PG_Name
------------------------------------------------------------------------------------------------
16 0;1 None None 1 1 0 pg0
17 2;3 None None 1 1 0 pg0
18 4;5 None None 1 1 0 pg0
19 6;7 None None 1 1 0 pg0
20 8;9 None None 1 1 0 pg0
21 10;11 None None 1 1 0 pg0
22 12;13 None None 1 1 0 pg0
23 14;15 None None 1 1 0 pg0
------------------------------------------------------------------------------------------------
Review the command output.

a. What N_Port is port 0 mapped to:___________.6
b. What N_Port is port 1 mapped to:___________.7
c. What N_Port is port 14 mapped to:___________.8
d. What N_Port is port 15 mapped to:___________.9
4. These are by default configured as F_Ports. F_Ports are disabled until the N_Port they are mapped to is
logged in.
5. Ports 16-23 should now be configured as N_Ports.
6. Port 0 is mapped to N_Port 16

CHECK POINT
The default N_Port configuration and port map has been implemented and verified.
Configuring Ports 14, 15, and N_Ports

In this section, you will change the port map on the Access Gateway so that ports 14 and 15 which
connect to the B5100 are configured as N_Ports.
17. Continuing with the B300 Telnet session, delete the N_Port mapping for ports 0, 14, and 15 by
running the following commands:
ST02-B300:admin> ag --mapdel 16 0
F_Port to N_Port mapping has been updated successfully
18. Now verify that ports 14 and 15 are not mapped using the ag --mapshow command.
------------------------------------------------------------------------------------------------
16 1 None None 1 1 0 pg0
17 2;3 None None 1 1 0 pg0
18 4;5 None None 1 1 0 pg0
19 6;7 None None 1 1 0 pg0
20 8;9 None None 1 1 0 pg0
21 10;11 None None 1 1 0 pg0
22 12;13 None None 1 1 0 pg0
23 None None None 1 1 0 pg0
------------------------------------------------------------------------------------------------
19. Now configure ports 14 and 15 as N_Ports using the portcfgnport 14-15 1 command.
20. Verify ports 14 and 15 are now N_Ports using the portcfgnport command.
ST02-B300:admin> portcfgnport
Ports 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
--------------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
Locked N_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. ON ON ON ON ON ON ON ON ON ON
CHECK POINT
Ports 14 and 15 should be configured as N_Ports.

Confirm Connectivity on the B5100

21. Open a Telnet session to the B5100.
22. Type the switchshow command. Verify that ports 14 and 15 are F_Ports and not E_Ports.
switchType:66.1
switchState:Online
switchMode:Native
switchRole:Subordinate
switchDomain:2
switchId:fffc02
switchWwn:10:00:00:05:1e:9c:b2:33
zoning:ON (LSAN_CFG_20120307)
switchBeacon:OFF
FC Router:OFF
Address Mode:0

==============================================
0 0 020000 -- N8 No_Module FC
1 1 020100 -- N8 No_Module FC
2 2 020200 -- N8 No_Module FC
3 3 020300 -- N8 No_Module FC
4 4 020400 -- N8 No_Module FC
5 5 020500 -- N8 No_Module FC
6 6 020600 -- N8 No_Module FC
7 7 020700 -- N8 No_Module FC
9 9 020800 id N8 Online FC E-Port 10:00:00:05:33:92:ea:66 "ST02-B6510"
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 F-Port 20:0e:00:05:33:07:5a:dd (AoQ)
15 15 020f00 id N8 Online FC F-Port 1 N Port + 1 NPIV public (AoQ)
16 16 021000 -- N8 No_Module FC
<output truncated>
a. How many NPIV public devices are logged into port 14? _______10
b. How many NPIV public devices are logged into port 15? _______11
10.Port 14 should display 1 N Port + 1 NPIV public device

11.Port 15 should display 1 N Port + 1 NPIV public device

Confirm Connectivity on the B300

23. Return to the B300 Telnet window. Now that N_Ports 14 and 15 are online, type the
ag --mapshow command.
------------------------------------------------------------------------------------------------
15 None None 1 1 1 0 pg0
17 2;3 None None 1 1 0 pg0
18 4;5 None None 1 1 0 pg0
19 6;7 None None 1 1 0 pg0
20 8;9 None None 1 1 0 pg0
21 10;11 None None 1 1 0 pg0
22 12;13 None None 1 1 0 pg0
------------------------------------------------------------------------------------------------
a. What ports are the host and storage mapped to? _________________________12
b. Why are these values different than what you recorded in Step16?
____________________________________________________________________13
Changing the Mapping of Host Port 0 to 15

24. Statically map the host connected to port 0 to port 15:
a. ag --staticadd 15 0
ST02-B300:admin> ag --staticadd 15 0
F_Port to N_Port static mapping has been updated successfully
b. ag --mapshow (You should now see port 0 mapped to port 15 as a Static_F_Port)

------------------------------------------------------------------------------------------------
15 None 0 0;1 1 1 0 pg0
17 2;3 None None 1 1 0 pg0
18 4;5 None None 1 1 0 pg0
19 6;7 None None 1 1 0 pg0
20 8;9 None None 1 1 0 pg0
21 10;11 None None 1 1 0 pg0
22 12;13 None None 1 1 0 pg0
------------------------------------------------------------------------------------------------
12.The host port 0 is now mapped to N_Port 14 and the storage port 1 is mapped to N_Port 15.
13.By default, the port grouping policy is enabled that also enables the auto map balancing feature.

c. ag --show
ST02-B300:admin> ag --show
Name : ST02-B300
NodeName : 10:00:00:05:33:07:5a:dd
Number of Ports : 24
IP Address(es) : 10.255.224.39
Firmware Version : v7.0.0a
N_Ports : 2
F_Ports : 2
Policies enabled : pg
Persistent ALPA : Disabled
Static WWN Map : None
Port Group information :
PG_IDPG_MembersPG_NamePG_Mode
----------------------------------------------------------------------------------------
0 14;15;16;17;18; pg0 -
19;20;21;22;23
----------------------------------------------------------------------------------------
Fabric Information :
Attached Fabric NameN_Ports
---------------------------------------------
10:00:00:05:33:92:ea:66 14;15
---------------------------------------------
N_Port information :
Port PortID Attached PWWN FO FB IP_Addr F_Ports
---------------------------------------------------------------------
14 0x020e00 20:0e:00:05:1e:9c:b2:33 1 1 10.255.224.40 None
15 0x020f00 20:0f:00:05:1e:9c:b2:33 1 1 10.255.224.40 0;1;
---------------------------------------------------------------------
F_Port information :
Port PortID Attached PWWNN_Port Preferred N_port Login Exceeded?
------------------------------------------------------------------------------------
0 0x020f02 10:00:00:05:1e:57:7c:b415 None No
1 0x020f01 20:01:00:11:0d:0f:85:0015 None No
------------------------------------------------------------------------------------
Static N-Port to F-Port Mapping :
N-Port F-Port
------------------------------------------------------------------------------------
14 None
15 0;
------------------------------------------------------------------------------------
a. What is the 24 bit address of the host attached to port 0:_____________________?

b. What is the 24 bit address of the storage attached to port 1:_____________________?
c. What is the 24 bit address assigned to port 14:_____________________?
d. What is the 24 bit address assigned to port 15:_____________________?
25. Type switchshow command; verify the address of the devices recorded in the previous steps.
switchType:71.2
switchState:Online
switchWwn:10:00:00:05:33:07:5a:dd
switchBeacon:OFF

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

0 0 010000 id N8 Online FC F-Port 10:00:00:05:1e:57:7c:b4 0x020f02

1 1 010100 id N8 Online FC F-Port 20:01:00:11:0d:0f:85:00 0x020f01
2 2 010200 -- N8 No_Module FC
<output truncated>
14 14 010e00 id N8 Online FC N-Port 10:00:00:05:1e:9c:b2:33 0x020e00 (AoQ)
15 15 010f00 id N8 Online FC N-Port 10:00:00:05:1e:9c:b2:33 0x020f00 (AoQ)
16 16 011000 -- N8 No_Module FC
<output truncated>
Move to the Open Telnet Session on the B5100

26. From the B5100 switch run the switchshow command.
switchType:66.1
switchState:Online
switchMode:Native
switchDomain:2
switchId:fffc02
switchWwn:10:00:00:05:1e:9c:b2:33
switchBeacon:OFF
FC Router:OFF
Address Mode:0

==============================================
0 0 020000 -- N8 No_Module FC
<output truncated>
10 10 020a00 -- N8 No_Module FC
<output truncated>
14 14 020e00 id N8 Online FC F-Port 20:0e:00:05:33:07:5a:dd (AoQ)
15 15 020f00 id N8 Online FC F-Port 1 N Port + 2 NPIV public (AoQ)
16 16 021000 -- N8 No_Module FC
<output truncated>
a. How many NPIV public devices does port 15 show?

____________________________________________________________________14
27. Type the nsshow command.
{
TTL(sec)
N 020e00;
3;20:0e:00:05:33:07:5a:dd;10:00:00:05:33:07:5a:dd; na
Fabric Port Name: 20:0e:00:05:1e:9c:b2:33
Permanent Port Name: 20:0e:00:05:33:07:5a:dd
14. 2

Port Index: 14
Share Area: No
Redirect: No
Partial: No
N 020f00;
3;20:0f:00:05:33:07:5a:dd;10:00:00:05:33:07:5a:dd; na
Fabric Port Name: 20:0f:00:05:1e:9c:b2:33
Permanent Port Name: 20:0f:00:05:33:07:5a:dd
Port Index: 15
Share Area: No
Redirect: No
Partial: No
N 020f01;
3;20:01:00:11:0d:0f:85:00;20:01:00:11:0d:0f:85:00; na
FC4s: FCP
Port Index: 15
Share Area: No
Redirect: No
Partial: No
N 020f02;
3;10:00:00:05:1e:57:7c:b4;20:00:00:05:1e:57:7c:b4; na
FC4s: FCP
PortSymb: [89] "Brocade-825 | 3.0.0.0 | DEV2-ST02-HBA | Windows
Server (R) 2008 Standard | Service Pack 1"
Port Index: 15
Share Area: No
Redirect: No
Partial: No
The Local Name Server has 4 entries }
b. Which devices are displayed?

____________________________________________________________________15
15.The host, storage and each of the N_Ports (14 and 15) of the B300 itself.

Testing Failover
Move to the open Telnet session on the Brocade B300.
28. Type the ag --mapshow command.
ST02-B300:admin> ag--mapshow
------------------------------------------------------------------------------------------------
15 None 0 0;1 1 1 0 pg0
17 2;3 None None 1 1 0 pg0
18 4;5 None None 1 1 0 pg0
19 6;7 None None 1 1 0 pg0
20 8;9 None None 1 1 0 pg0
21 10;11 None None 1 1 0 pg0
22 12;13 None None 1 1 0 pg0
------------------------------------------------------------------------------------------------
a. Are failover and failback are enabled on ports 14 and 15?16

29. Disable port 15 using the portdisable 15 command.
30. Type the ag --mapshow command to look at the new port mapping.
------------------------------------------------------------------------------------------------
15 None 0 None 1 1 0 pg0
17 2;3 None None 1 1 0 pg0
18 4;5 None None 1 1 0 pg0
19 6;7 None None 1 1 0 pg0
20 8;9 None None 1 1 0 pg0
21 10;11 None None 1 1 0 pg0
22 12;13 None None 1 1 0 pg0
------------------------------------------------------------------------------------------------
a. Looking at the current F_Ports; did port 0 failover? ________?17 Port 1?_______?18 Why?
____________________________________________________________________19
31. To change the static mapping to a dynamic mapping, first delete the static map using the
ag --staticdel 15 0 command.
ST02-B300:admin> ag --staticdel 15 0
F_Port to N_Port static mapping has been updated successfully
32. The add the new mapping using the ag --mapadd 15 0 command, enter y when prompted
to continue.
ST02-B300:admin> ag --mapadd 15 0
16.Yes. It is denoted by the 1 (=on) on Failover and Failback columns.

17.No
18.Yes
19.Port 0 was STATICALLY mapped to port 15. Static mapping overrides dynamic mapping.

WARNING: Mapping F_Port(s) to this N_Port may cause the F_Port(s) to

be disabled
------------------------------------------------------------------------------------------------
14 None None 0;1 1 1 0 pg0
17 2;3 None None 1 1 0 pg0
18 4;5 None None 1 1 0 pg0
19 6;7 None None 1 1 0 pg0
20 8;9 None None 1 1 0 pg0
21 10;11 None None 1 1 0 pg0
22 12;13 None None 1 1 0 pg0
------------------------------------------------------------------------------------------------
Looking at the current F_Ports; did port 0 failover? ________?20 Port 1?_______?21
a. Type the switchshow command.
switchType:71.2
switchState:Online
switchWwn:10:00:00:05:33:07:5a:dd
switchBeacon:OFF

==============================================
0 0 010000 id N8 Online FC F-Port 10:00:00:05:1e:57:7c:b4 0x020e02
1 1 010100 id N8 Online FC F-Port 20:01:00:11:0d:0f:85:00 0x020e01
2 2 010200 -- N8 No_Module FC
<output truncated>
14 14 010e00 id N8 Online FC N-Port 10:00:00:05:1e:9c:b2:33 0x020e00 (AoQ)
16 16 011000 -- N8 No_Module FC
<output truncated>
What is the 24-bit address of the device on port 0:________________?

20.No
21.No

Test Failback
34. Now test fail back by running the portenable 15 command.
------------------------------------------------------------------------------------------------
14 None None 1 1 1 0 pg0
15 0 None 0 1 1 0 pg0
17 2;3 None None 1 1 0 pg0
18 4;5 None None 1 1 0 pg0
19 6;7 None None 1 1 0 pg0
20 8;9 None None 1 1 0 pg0
21 10;11 None None 1 1 0 pg0
22 12;13 None None 1 1 0 pg0
------------------------------------------------------------------------------------------------
a. Looking at the current F_Ports; did port 0 failover? ________? Port 1?_______? Why?
____________________________________________________________________22
b. Type the switchshow command.
switchType:71.2
switchState:Online
switchWwn:10:00:00:05:33:07:5a:dd
switchBeacon:OFF

==============================================
0 0 010000 id N8 Online FC F-Port 10:00:00:05:1e:57:7c:b4 0x020f01
2 2 010200 -- N8 No_Module FC
<output truncated>

36. Compare the addresses of the devices throughout the changes in Step33. Notice that the PIDs
change to match the N_Port physical address.
22.Auto Map Balancing balanced the F_Ports across both N_Ports.

CHECK POINT
You have now tested failover and noticed that port 0 changed address (due to the fact that the server
must re-login to the fabric). Now you will enable F_Port Trunking and retest failover; this time however
you will notice that the failover is non-disruptive (server does not have to re-login to the fabric).
Enabling F_Port Trunking

37. To enable F_Port trunking on ports 14 and 15 of the B5100 run the following commands:
a. portdisable 14-15
b. porttrunkarea --enable 14-15 -index 14 (This enables F_Port trunking on
ports 14 and 15.)
ST02-B5100:admin> porttrunkarea --enable 14-15 -index 14
Trunk index 14 enabled for ports 14 and 15.
c. portenable 14-15
ST02-B5100:admin> portenable 14-15
d. switchshow
switchType:66.1
switchState:Online
switchMode:Native
switchDomain:2
switchId:fffc02
switchWwn:10:00:00:05:1e:9c:b2:33
switchBeacon:OFF
FC Router:OFF
Address Mode:0

==============================================
0 0 020000 -- N8 No_Module FC
<output truncated>
10 10 020a00 -- N8 No_Module FC
<output truncated>
13 13 020d00 -- N8 No_Module FC
14 14 020e00 id N8 Online FC F-Port (Trunk port, master is Port 15 )(AoQ)
14 15 020e00 id N8 Online FC F-Port 1 N Port + 1 NPIV public (Trunk master)
(AoQ)
16 16 021000 -- N8 No_Module FC
<output truncated>

38. Verify that ports 14 and 15 are now trunked using the porttrunkarea --show 14-15
command.
ST02-B5100:admin> porttrunkarea --show 14-15
Port Type State Master TI DI
-------------------------------------
14 F-port Slave 15 14 14
15 F-port Master 15 14 15
Are ports 14 and 15 are trunked? How can you tell?
____________________________________________________________________23
CHECK POINT
You have now enabled F_Port Trunking on the B5100 switch. You are now ready to test failover on the
B300.
Testing Failover
39. Type the following commands and answer the questions.
a. Type the switchshow command.
switchType:71.2
switchState:Online
switchWwn:10:00:00:05:33:07:5a:dd
switchBeacon:OFF

==============================================
2 2 010200 -- N8 No_Module FC
<output truncated>
14 14 010e00 id N8 Online FC N-Port 10:00:00:05:1e:9c:b2:33 0x020e00 (Trunk
port, master is Port 15 )(AoQ)
15 15 010f00 id N8 Online FC N-Port 10:00:00:05:1e:9c:b2:33 0x020e00 (Trunk
master) (AoQ)
16 16 011000 -- N8 No_Module FC
<output truncated>
What is the 24-bit address of the host attached to port 0:_____________________?

What is the 24-bit address of the host attached to port 1:_____________________?
What is the 24-bit address assigned to port 14:_____________________?
What is the 24 bit address assigned to port 15:_____________________?
23. In the state column a master and slave are specified. The Master column specifies port 15 as the master
which corresponds to the state of port 14.

b. Enter the switchshow command and write down which port is the master ISL.
c. Disable the master ISL using the portdisable <port#> command where <port#> is
the port number obtained in step b.
d. Type the switchshow command.
switchType:71.2
switchState:Online
switchWwn:10:00:00:05:33:07:5a:dd
switchBeacon:OFF

==============================================
2 2 010200 -- N8 No_Module FC
<output truncated>
14 14 010e00 id N8 Online FC N-Port 10:00:00:05:1e:9c:b2:33 0x020e00 (Trunk
master) (AoQ)
16 16 011000 -- N8 No_Module FC
<output truncated>
Did the 24 bit address of the host or storage change? __________________24

------------------------------------------------------------------------------------------------
14 None None 0;1 1 1 0 pg0
17 2;3 None None 1 1 0 pg0
18 4;5 None None 1 1 0 pg0
19 6;7 None None 1 1 0 pg0
20 8;9 None None 1 1 0 pg0
21 10;11 None None 1 1 0 pg0
22 12;13 None None 1 1 0 pg0
------------------------------------------------------------------------------------------------
Verify that port 0 failed over and is currently mapped to the new trunk master port specified
in the switchshow output from Step39.
41. Use the portenable <port#> command to enable the ISL port, where <port#> is the port
number you disabled in step c.
24.No, because F_Port Trunking is enabled when a port fails over it does not require the complete re-login
process.

CHECK POINT
You have completed the Access Gateway lab but need to run some cleanup commands to prepare the
lab station for the next lab.
Cleaning Up the Lab Environment

42. Type the following commands on B5100:
portdisable 14-15
porttrunkarea --disable 14-15 (Leave these ports disabled until Step45)
ST02-B5100:admin> porttrunkarea --disable 14-15
Trunk index 14 disabled for ports 14 and 15.
Disabling Access Gateway Mode

43. Move to the open Telnet session on the B300. Disable Access Gateway mode to prepare switch
for your next lab:
a. Type the switchdisable command.
b. Disable Access Gateway mode on the Brocade B300 with the ag --modedisable
command.
c. Review the command output, and at the Do you want to continue? prompt, type y.
ST02-B300:admin> ag --modedisable
WARNING 1: Changing from Access Gateway mode to Switch mode will set
zoning to "all access".
WARNING 2: Disabling agmode will remove all the configuration data

on the switch
including N_Port configuration and F_Port to N_Port mapping. Please
backup your
configuration using configupload.
This operation will reboot the switch.

Access Gateway mode was disabled successfully
Switch is being rebooted...
NOTE
This will cause your Telnet session to the B300 to be lost; close that window.
44. Move to the open Telnet session on the B5100.

45. Type the portenable 14-15 command.
46. Before going to the next lab type a switchshow to validate that ports 14 and 15 come back
online as normal trunked E_Ports.


choose Shutdown.
This ends Module 9 Lab: Access Gateway lab.


Lab Guide CFP300 Rev0114 LG - L

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lab Guide CFP300 Rev0114 LG - L

Uploaded by

Copyright:

Available Formats

CFP 300:

European Headquarters - Geneva, Switzerland

Asia Pacific Headquarters - Singapore

2014 Brocade Communications Systems, Inc. All Rights Reserved.

Module 3: FC-FC Routing

Module 6a Lab: Configuring Flow Vision on the CLI

Module 6b Lab: Flow Vision and Network Advisor

CFP 300 Revision 0114 iii

Module 7b Lab: Using MAPS With Network Advisor

Module 8: Virtual Fabrics

Module 9 Lab: Access Gateway

iv Revision 0114 CFP 300

CFP 300 Revision 0114 v

Revision 0114 CFP 300 1

Record Remote Lab Access Information

2 Revision 0114 CFP 300

Connecting to the Brocade RSL Environment

Revision 0114 CFP 300 3

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

4 Revision 0114 CFP 300

11. Select the username assigned by the instructor.

12. Enter the password assigned by the instructor.

Revision 0114 CFP 300 5

Close Open Sessions and Exit Remote Connection

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

17. Close the browser.

This ends the Remote Lab Access Instructions lab exercise.

6 Revision 0114 CFP 300

FIGURE 1 Lab station diagram

Revision 0114 CFP 300 7

Configuring FC-FC Integrated Routing

Switch Start State and Enabling FC Routing Services

8 Revision 0114 CFP 300

Initial Settings on the B5100

Index Port Address Media Speed State Proto

Revision 0114 CFP 300 9

Change the Backbone Fabric ID

ST01-B5100:admin> fcrconfigure --bbfid

10 Revision 0114 CFP 300

How many physical devices are there? 6

Revision 0114 CFP 300 11

How many proxy devices are there? 7

Initial Settings on the B300

12 Revision 0114 CFP 300

Initial Settings on the B6510s

Backbone Router Configuration

Backbone-to-Edge Fabric 10 (B300) EX-to-E_Port Connections Using

10.Ports 14 and 15.

Revision 0114 CFP 300 13

Discovering your Fabrics in Brocade Network Advisor

Configuring EX_Ports using Web Tools

14 Revision 0114 CFP 300

Identify the Changes

Are the ports now online as trunked EX_Ports? 12

Revision 0114 CFP 300 15

1 1 010100 id N8 Online FC F-Port 20:01:00:11:0d:0f:85:00

Are the ports now online as trunked E_Ports?14

2 domain(s) in the fabric; Local Domain ID: 1

How many hops is it to the new front domain?

16 Revision 0114 CFP 300

LSAN Zone Management with Network Advisor

Revision 0114 CFP 300 17

47. Highlight Lab Fabric BB backbone fabric.