Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Service manual

53-1001189-01
November 24, 2008
Access Gateway
Administrator’s Guide
Supporting Fabric OS 6.2.0

Copyright © 2007-2008 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade B-wing symbol,
DCX, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in 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.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with
respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that
accompany it.
The product described by this document may contain “open source” software covered by the GNU General Public License or other
open source license agreements. To find-out which open source software is included in Brocade products, view the licensing
terms applicable to the open source software, and obtain a copy of the programming source code, please visit
http://www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated
Corporate Headquarters
Brocade Communications Systems, Inc.
1745 Technology Drive
San Jose, CA 95110
Tel: [phone]
Fax: [phone]
Email: [e-mail]
Asia-Pacific Headquarters
Brocade Communications Singapore Pte. Ltd.
30 Cecil Street
#19-01 Prudential Tower
Singapore 049712
Tel: [phone]
Fax: [phone]
Email: [email protected]
European and Latin American Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour B - 4ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: [phone]
Fax: [phone]
Email: [email protected]

Access Gateway Administrator’s Guide iii
53-1001189-01
Document History
The following table lists all versions of the Access Gateway Administrator’s Guide.
Document Title Publication Number Summary of Changes Publication Date
Access Gateway Administrator’s Guide 53-1000430-01 First version January 2007
Access Gateway Administrator’s Guide 53-1000633-01 Added support for the 200E June 2007
Access Gateway Administrator’s Guide 53-1000605-01 Added support for new policies
and changes to N_Port
mappings.
October 2007
Access Gateway Administrator’s Guide 53-1000605-02 Added support for new
platforms:
300 and the 4424.
Added support for new features:
- Masterless Trunking
- Direct Target Connectivity
- Advance Device Security policy
- 16- bit routing
March 2008
Access Gateway Administrator’s Guide 53-1000605-03 Added support for:
- Cascading Access Gateway.
July 2008
Access Gateway Administrator’s Guide 53-1000605-04 Updated to fix the table of
contents
July 2008
Access Gateway Administrator’s Guide 53-1001189-01 Updated for FOS 6.2 November 2008

iv Access Gateway Administrator’s Guide
53-1001189-01

Access Gateway Administrator’s Guide v
53-1001189-01
Contents
About This Document
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
What’s new in this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Key terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Brocade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Other industry resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Optional Brocade features . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Getting technical help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Chapter 1 Getting Started
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Brocade Access Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Fabric OS features in Access Gateway mode . . . . . . . . . . . . . . . . . . . 2
Access Gateway port types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Comparison of Access Gateway ports to standard switch ports. 4
How Access Gateway maps ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Access Gateway limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Upgrade and downgrade considerations for switches in AG mode . . 6
Advance Device Security policy. . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Automatic Port Configuration policy . . . . . . . . . . . . . . . . . . . . . . . 7
Port Grouping policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 2 Enabling Policies on Switches in Access Gateway Mode
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Access Gateway policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Showing current policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

vi Access Gateway Administrator’s Guide
53-1001189-01
Advanced Device Security policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Enabling the Advanced Device Security policy. . . . . . . . . . . . . . 10
Disabling the Advanced Device Security policy . . . . . . . . . . . . . 10
Setting which devices can log in if ADS policy is enabled. . . . . 10
Setting which devices cannot log in if ADS policy is enabled . . 11
Removing devices from the list of devices allowed at login . . . 11
Adding new devices to the list of devices allowed at login . . . . 11
Displaying the list of devices on the switch . . . . . . . . . . . . . . . .12
Automatic Port Configuration policy. . . . . . . . . . . . . . . . . . . . . . . . . .12
Enabling the Automatic Port Configuration policy . . . . . . . . . . .13
Disabling the Automatic Port Configuration policy . . . . . . . . . . 13
Rebalancing F_Ports with APC policy enabled. . . . . . . . . . . . . .13
Failover policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Enabling the Failover policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Disabling the Failover policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Failback policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Enabling the Failback policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Cold Failover policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Port Grouping policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Creating a port group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Adding an N_Port to a port group . . . . . . . . . . . . . . . . . . . . . . . . 20
Deleting an N_Port from a port group . . . . . . . . . . . . . . . . . . . . 20
Removing a port group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Renaming a port group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Disabling the Port Group policy. . . . . . . . . . . . . . . . . . . . . . . . . . 21
Access Gateway policy enforcement matrix . . . . . . . . . . . . . . . . . . .22
Access Gateway trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Access Gateway trunking considerations for the Edge switch .23
Trunk group creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Setting up F_Port trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Assigning a Trunk Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Enabling the DCC policy on trunk . . . . . . . . . . . . . . . . . . . . . . . .28
Configuration management for trunk areas . . . . . . . . . . . . . . . . . . .28
Enabling Access Gateway trunking . . . . . . . . . . . . . . . . . . . . . . . 28
Disabling F_Port trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
F_Port Trunking monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Access Gateway Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chapter 3 Connecting Devices Using Access Gateway
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Connectivity of multiple devices overview . . . . . . . . . . . . . . . . . . . . . 33
Fabric and Edge switch configuration . . . . . . . . . . . . . . . . . . . . . . . . 33
Verifying the switch mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Setting the Fabric OS switch to Native Mode. . . . . . . . . . . . . . .35
Enabling NPIV on the M-EOS switch . . . . . . . . . . . . . . . . . . . . . . 35

Access Gateway Administrator’s Guide vii
53-1001189-01
Connectivity to Cisco Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Access Gateway routing requirements with Cisco fabrics. . . . .36
Enabling NPIV on a Cisco switch. . . . . . . . . . . . . . . . . . . . . . . . .36
Workaround for QLogic-based devices . . . . . . . . . . . . . . . . . . . . 37
Editing Company ID List if no FC target devices on switch . . . . 37
Adding or deleting an OUI from the Company ID List . . . . . . . . 38
Enabling Flat FCID mode if no FC target devices on switch . . .39
Editing Company ID list if target devices on switch . . . . . . . . . .39
Access Gateway mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Enabling Access Gateway mode . . . . . . . . . . . . . . . . . . . . . . . . .40
Port States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Disabling Access Gateway mode . . . . . . . . . . . . . . . . . . . . . . . .42
Saving the Access Gateway configuration . . . . . . . . . . . . . . . . .42
Rejoining switches to a fabric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Reverting to a previous configuration. . . . . . . . . . . . . . . . . . . . .43
Chapter 4 Configuring Ports in Access Gateway mode
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Port Initialization in Access Gateway mode. . . . . . . . . . . . . . . . . . . . 45
N_Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Unlocking N_Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Displaying N_Port configurations . . . . . . . . . . . . . . . . . . . . . . . . 48
Verifying port mapping and status . . . . . . . . . . . . . . . . . . . . . . .48
Displaying N_Port mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Displaying port status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Port configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Adding F_Ports to an N_Port . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Removing F_Ports from an N_Port . . . . . . . . . . . . . . . . . . . . . . . 51
Adding a preferred secondary N_Port . . . . . . . . . . . . . . . . . . . . 52
Deleting F_Ports from a preferred secondary N_Port . . . . . . . .52
Appendix A Troubleshooting
Index

viii Access Gateway Administrator’s Guide
53-1001189-01

Access Gateway Administrator’s Guide ix
53-1001189-01
Figures
Figure 1 Access Gateway and fabric switch comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Figure 2 Port usage comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 3 Example F_Port-to-N_Port mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 4 Example 1 and 2 Failover policy behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 5 Failback policy behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 6 Port Group Zero (pg0) setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 7 Port grouping behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 8 Port Group 1 (pg1) setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 9 Access Gateway cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 10 Initialized ports in Access Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 11 Example of adding an external F_Port (F9) on an embedded switch . . . . . . . . . 47

xAccess Gateway Administrator’s Guide
53-1001189-01

Access Gateway Administrator’s Guide xi
53-1001189-01
Tables
Table 1 Fabric OS components supported on Access Gateway . . . . . . . . . . . . . . . . . . . . . 3
Table 2 Port configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Table 3 Description of F_Port-to-N_Port mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Table 4 Firmware upgrade and downgrade scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Table 5 Policy enforcement matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 6 Access Gateway trunking considerations for the Edge switch . . . . . . . . . . . . . . 23
Table 7 PWWN format for F_Port and N_Port trunk ports. . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 8 Address identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 9 OUI IDs that require special treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 10 Port state description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 11 Access Gateway default F_Port-to-N_Port mapping. . . . . . . . . . . . . . . . . . . . . . . 53
Table 12 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

xii Access Gateway Administrator’s Guide
53-1001189-01

Access Gateway Administrator’s Guide xiii
53-1001189-01
About This Document
•How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
•Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
•What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
•Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
•Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
•Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
•Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
•Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
How this document is organized
This document is a procedural guide to help SAN administrators configure and manage Brocade
Access Gateway.
This preface contains the following components:
•Chapter 1, “Getting Started” describes how to use Access Gateway to create seamless
connectivity to any Storage Area Network (SAN) fabric.
•Chapter 2, “Enabling Policies on Switches in Access Gateway Mode” describes how to enable
policies on a switch in Access Gateway mode.
•Chapter 3, “Connecting Devices Using Access Gateway” describes how to connect multiple
devices using Access Gateway.
•Chapter 4, “Configuring Ports in Access Gateway mode” describes how to configure ports in
Access Gateway mode.
•Appendix A, “Troubleshooting” provides symptoms and troubleshooting tips to resolve issues.
Supported hardware and software
Although many different software and hardware configurations are tested and supported by
Brocade Communications Systems, Inc. For 6.2.0, documenting all possible configurations and
scenarios is beyond the scope of this document. All Fabric OS switches must be running v5.1 or
later; all M-EOS switches must be running M-EOSc 9.1 or later, M-EOSn must be running 9.6.2 or
later, and Cisco switches with SAN OS must be running 3.0 (1) and 3.1 (1) or later. Access Gateway
supports 4 and 8 Gbit bladed servers and blades.

xiv Access Gateway Administrator’s Guide
53-1001189-01
What’s new in this document
The following changes have been made since this document was last released:
Information that was added:
•Supported software
•M-EOSc products: Release 9.1 or later and 9.6 or later
•Cisco Products: SAN-OS 3.0(1) or later and 3.1(1) or later
•Supported platforms
•Brocade 300 (24-port version only), 5100
•Embedded switches: 5410, 5424, 5480
•Supported configurations in cascaded AG
For further information, refer to the release notes.
Document conventions
This section describes text formatting conventions and important notices formats.
Text formatting
The narrative-text formatting conventions that are used in this document are as follows:
bold text Identifies command names
Identifies the names of user-manipulated GUI elements
Identifies keywords and operands
Identifies text to enter at the GUI or CLI
italic text Provides emphasis
Identifies variables
Identifies paths and Internet addresses
Identifies document titles
code text Identifies CLI output
Identifies syntax examples
For readability, command names in the narrative portions of this guide are presented in mixed
lettercase: for example, switchShow. In actual examples, command lettercase is often all
lowercase. Otherwise, this manual specifically notes those cases in which a command is case
sensitive. The ficonCupSet and ficonCupShow commands are an exception to this convention.
Command syntax conventions
Command syntax in this manual follows these conventions:

Access Gateway Administrator’s Guide xv
53-1001189-01
Notes, cautions, and warnings
The following notices appear in this document.
NOTE
A note provides a tip, emphasizes important information, or provides a reference to related
information.
ATTENTION
An Attention statement indicates potential damage to hardware or data.
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you.
DANGER
A Danger statement indicates conditions or situations that can be potentially lethal or extremely
hazardous to you. Safety labels are also attached directly to products to warn of these conditions
or situations.
Key terms
For definitions of SAN-specific terms, visit the Storage Networking Industry Association online
dictionary at: http://www.snia.org/education/dictionary.
For definitions specific to Brocade and Fibre Channel, see the Brocade Glossary.
The following terms are used in this manual to describe Access Gateway mode and its components.
command Commands are printed in bold.
--option, option Command options are printed in bold.
-argument, arg Arguments.
[ ] Optional element.
variable Variables are printed in italics. In the help pages, values are underlined or
enclosed in angled brackets < >.
... Repeat the previous element, for example “member[;member...]”
value Fixed values following arguments are printed in plain font. For example,
--show WWN
| Boolean. Elements are exclusive. Example: --show -mode egress | ingress

xvi Access Gateway Administrator’s Guide
53-1001189-01
Access Gateway (AG)
Fabric OS mode for switches that reduces SAN (storage area network)
deployment complexity by leveraging NPIV (N_Port ID Virtualization).
E_Port An ISL (Interswitch link) port. A switch port that connects switches together to
form a fabric.
Edge switch A fabric switch that connects host, storage, or other devices, such as Brocade
Access Gateway, to the fabric.
F_Port A fabric port. A switch port that connects a host, HBA (host bus adaptor), or
storage device to the SAN. On Brocade Access Gateway, the F_Port connects
to a host or a target.
Mapping On Brocade Access Gateway, the configuration of F_Port to N_Port routes.
N_Port A node port. A Fibre Channel host or storage port in a fabric or point-to-point
connection. On Brocade Access Gateway, the N_Port connects to the Edge
switch.
NPIV N_Port ID Virtualization. Allows a single Fibre Channel port to appear as
multiple, distinct ports providing separate port identification and security
zoning within the fabric for each operating system image as if each operating
system image had its own unique physical port.
Preferred Secondary N_Port
On the Brocade Access Gateway, the preferred secondary N_Port refers to the
secondary path to which an F_Port fails over if the primary N_Port goes
offline.
Notice to the reader
This document may contain references to the trademarks of the following corporations. These
trademarks are the properties of their respective companies and corporations.
These references are made for informational purposes only.
Additional information
This section lists additional Brocade and industry-specific documentation that you might find
helpful.
Corporation Referenced Trademarks and Products
Cisco Systems Cisco
Emulex Corporation Emulex
Qlogic Corporation Qlogic

Access Gateway Administrator’s Guide xvii
53-1001189-01
Brocade resources
To get up-to-the-minute information, join Brocade Connect. It’s free! Go to http://www.brocade.com
and click Brocade Connect to register at no cost for a user ID and password.
For practical discussions about SAN design, implementation, and maintenance, you can obtain
Building SANs with Brocade Fabric Switches through:
http://www.amazon.com
For additional Brocade documentation, visit the Brocade SAN Info Center and click the Resource
Library location:
http://www.brocade.com
Release notes are available on the Brocade Connect Web site and are also bundled with the Fabric
OS firmware.
Other industry resources
•White papers, online demos, and data sheets are available through the Brocade Web site at
http://www.brocade.com/products/software.jhtml.
•Best practice guides, white papers, data sheets, and other documentation is available through
the Brocade Partner Web site.
For additional resource information, visit the Technical Committee T11 Web site. This Web site
provides interface standards for high-performance and mass storage applications for Fibre
Channel, storage management, and other applications:
http://www.t11.org
For information about the Fibre Channel industry, visit the Fibre Channel Industry Association Web
site:
http://www.fibrechannel.org
Optional Brocade features
For a list of optional Brocade features and descriptions, see the Fabric OS Administrator’s Guide.
Getting technical help
Contact your switch support supplier for hardware, firmware, and software support, including
product repairs and part ordering. To expedite your call, have the following information available:
1. General Information
•Technical Support contract number, if applicable
•Switch model
•Switch operating system version
•Error numbers and messages received
•supportSave command output

xviii Access Gateway Administrator’s Guide
53-1001189-01
•Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions
•Description of any troubleshooting steps already performed and the results
•Serial console and Telnet session logs
•Syslog message logs
2. Switch Serial Number
The switch serial number and corresponding bar code are provided on the serial number label,
as shown here.
:
The serial number label is located as follows:
•Brocade 200E—On the nonport side of the chassis
•Brocade 300, 4100, 4900, 5100, 5300, 7500, and Brocade Encryption Switch—On the
switch ID pull-out tab located inside the chassis on the port side on the left
•Brocade 5000—On the switch ID pull-out tab located on the bottom of the port side of the
switch
•Brocade 7600—On the bottom of the chassis
•Brocade 48000—Inside the chassis next to the power supply bays
•Brocade DCX—On the bottom right on the port side of the chassis
•Brocade DCX-4S—On the bottom right on the port side of the chassis, directly above the
cable management comb.
3. World Wide Name (WWN)
Use the wwn command to display the switch WWN.
If you cannot use the wwn command because the switch is inoperable, you can get the WWN
from the same place as the serial number, except for the Brocade DCX. For the Brocade DCX,
access the numbers on the WWN cards by removing the Brocade logo plate at the top of the
nonport side of the chassis.
Document feedback
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a
topic needs further development, we want to hear from you. Forward your feedback to:
[e-mail]
Provide the title and version number of the document and as much detail as possible about your
comment, including the topic heading and page number and your suggestions for improvement.
*FT00X0054E9*
FT00X0054E9

Access Gateway Administrator’s Guide 1
53-1001189-01
Chapter
1
Getting Started
In this chapter
•Brocade Access Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
•Fabric OS features in Access Gateway mode. . . . . . . . . . . . . . . . . . . . . . . . . . 2
•Access Gateway port types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
•How Access Gateway maps ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
•Access Gateway limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Brocade Access Gateway
This chapter describes how to create seamless connectivity to any Storage Area Network (SAN)
fabric using Access Gateway (AG). It provides information on how to set the port types, port
mappings, and the policies to ensure a stable fabric.
AG is compatible with Fabric OS, M-EOSv9.1 or v9.6 and later, and Cisco-based fabrics v3.0(1) or
later and v3.1(1) and later. Enabling and disabling AG mode on a switch can be performed from the
command line interface (CLI) or using Web Tools, Fabric Manager, or DCFM. This document
describes configurations using the CLI commands. Please see the Web Tools Administrator’s
Guide, the Fabric Manager Administrator’s Guide, or the Data Center Fabric Manager User Guide
for more information about AG support in those tools.
Brocade Access Gateway is a Fabric OS feature that lets you configure your Enterprise fabric to
handle additional N_Ports instead of domains. You do this by configuring F_Ports to connect to the
fabric as N_Ports, which increases the number of device ports you can connect to a single fabric.
Multiple AGs can connect to the DCX enterprise-class platform, directors, and switches.
After you set a Fabric OS switch to AG mode, the F_Ports connect to the Enterprise fabric as
N_Ports rather than as E_Ports. They connect as E_Ports if the Fabric OS switch is in its Native
switch mode. Figure 1 shows a comparison of a configuration that connects eight hosts to a fabric
using AG to the same configuration with Fabric OS switches in Native mode.
Switches in AG mode are logically transparent to the host and the fabric. You can increase the
number of hosts that have access to the fabric without increasing the number of switches. This
simplifies configuration and management in a large fabric by reducing the number of domain IDs
and ports.

2Access Gateway Administrator’s Guide
53-1001189-01
Fabric OS features in Access Gateway mode
1
FIGURE 1 Access Gateway and fabric switch comparison
The following points summarize the differences between a Fabric OS switch in Native mode and a
Fabric OS switch in AG mode:
•The Fabric OS switch in Native mode is a part of the fabric; it requires two to four times as
many physical ports, consumes fabric resources, and can connect to a Fabric OS fabric only.
•A switch in AG mode is outside of the fabric; it reduces the number of switches in the fabric
and the number of required physical ports. You can connect an AG switch to either a Fabric OS,
M-EOS, or Cisco-based fabric.
Fabric OS features in Access Gateway mode
When a switch is behaving as an Access Gateway, RBAC features in Fabric OS are available, but
Admin Domains, Advanced Performance Monitoring, direct connection to SAN target devices, Fibre
Channel Arbitrated Loop support, FICON, IP over FC, extended fabrics, management platform
services, name services (SNS), port mirroring, SMI-S, and zoning are not available or no longer
applicable.
Table 1 lists Fabric OS components that are supported on a switch when AG mode is enabled. “No”
indicates that the feature is not provided in AG mode. “NA” indicates this feature is not applicable
in Access Gateway mode of operation. A single asterisk (*) indicates the feature is transparent to
AG, that is AG forwards the request to the Enterprise fabric. Two asterisks (**) indicates that if the
Enterprise fabric is not a Brocade fabric, the feature may not be available.
Security enforcement can be done in either the Enterprise fabric using the DCC policy or in the
Access Gateway module using Advanced Device Security (ADS) policy. The ADS policy secures
virtual and physical connections to the SAN. When you enable the ADS policy, by default, every
F_Port is configured to allow all devices to login or be a part of the Access List. The Allow list
restricts the devices that can log into a specific F_Port. Because all WWNs are a part of the Access
List, you can identify which devices are allowed to log in on a per F_Port basis by specifying the
device’s port WWN(PWWN). See the Fabric Command Reference on using the ag --adsset
command to set the “Allow List” to All Access or No Access. Alternatively the security policy can be
established in the Enterprise fabric. For information on the ADS policy, see “Setting which devices
can log in if ADS policy is enabled” on page 10 or “Setting which devices cannot log in if ADS policy
is enabled” on page 11.