Brocade, the Brocade B weave logo, Fabric OS, File Lifecycle Manager, MyView, Secure Fabric OS, SilkWorm, and StorageX are
registered trademarks and Tapestry is a trademark 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.
FICON, IBM BladeCenter are registered trademarks of IBM Corporation in the U.S. and other countries.
Notice: The information in this document is provided “AS IS,” without warranty of any kind, including, without limitation, any
implied warranty of merchantability, noninfringement or fitness for a particular purpose. Disclosure of information in this material
in no way grants a recipient any rights under Brocade's patents, copyrights, trade secrets or other intellectual property rights.
Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its
use.
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.
Notice: 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.
Export of technical data contained in this document may require an export license from the United States Government.
Brocade Communications Systems, Incorporated
Corporate Headquarters
Brocade Communications Systems, Inc.
1745 Technology Drive
San Jose, CA 95110
Tel: 1-408-333-8000
Fax: 1-408-333-8101
E-mail: info@brocade.com
European and Latin American Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour A - 2ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: +41 22 799 56 40
Fax: +41 22 799 56 41
Email: emea-info@brocade.com
This document is specific to Fabric OS v5.3.0 or higher running on the Brocade 200E switch and
the Brocade 4012, 4016, 4020, and 4024 embedded switches.
When procedures or parts of procedures documented here apply to some switches but not to
others, this guide identifies which switches are supported and which are not.
This document sometimes mentions other Fabric OS releases to highlight the changes in the latest
release or to point out interoperability issues with other Brocade models. It also specifies when
procedures or steps of procedures apply only to specific Brocade models.
Although many different software and hardware configurations are tested and supported by
Brocade Communications Systems, Inc. for this Brocade Fabric OS release, documenting all
possible configurations and scenarios is beyond the scope of this document.
How this document is organized
The document contains the following topics:
• Chapter 1, “Introduction to the Brocade Access Gateway” describes the Access Gateway
operation.
• Chapter 2, “Configuring Access Gateway” provides the initial setup procedures and fabric
• Chapter 4, “Managing Ports in Access Gateway mode” provides instructions on changing
N_Ports to F_Ports, mapping F_Ports to N_Ports, and changing failover and failback policies.
• Chapter 4, “Managing Ports in Access Gateway mode” provides instructions on changing
N_Ports to F_Ports, mapping F_Ports to N_Ports, and changing failover and failback policies.
• Appendix A, “Default Port Mapping” provides the default N_Port mappings for the different
switches while in Access Gateway mode.
• Appendix B, “Compatibility” provides compatibility information between different devices while
running a switch in Access Gateway mode.
• Appendix C, “Troubleshooting” provides symptoms and troubleshooting tips to resolve issues.
• Appendix D, “Access Gateway Commands” provides the commands for Access Gateway.
The appendices provide the default mappings, compatibility guidelines, and troubleshooting
assistance.
What’s new in this document
The following changes have been made since this document was last released:
Information that was added:
• Support for the following platform:
-Brocade 200E switch
• Enhancements to the failback policy
• Enhancements for compatibility
Information that was removed:
• System messages were moved to the Fabric OS System Message Reference
• All references to using Web Tools was moved to the Web Tool Administrator’s Guide
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 textIdentifies command names
italic textProvides emphasis
viAccess Gateway Administrator’s Guide
Identifies the names of user-manipulated GUI elements
Identifies keywords and operands
Identifies text to enter at the GUI or CLI
Identifies variables
Identifies paths and Internet addresses
Identifies document titles
53-1000633-01
NOTE
CAUTION
WARNING
code textIdentifies 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.
NOTES, CAUTIONS, AND WARNINGS
The following notices appear in this document.
A note provides a tip, emphasizes important information, or provides a reference to related
information.
A caution alerts you to potential damage to hardware, firmware, software, or data.
Key terms
A warning alerts you to potential danger to personnel.
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.
Access Gateway (AG) Fabric OS mode for embedded switches that reduces SAN (storage area
network) deployment complexity by leveraging NPIV (N_Port ID virtualization).
Edge switchFabric switch that connects host, storage, or other devices, such as Brocade
Access Gateway, to the fabric.
NPIVN_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.
E_PortAn ISL (Interswitch link) port. A switch port that connects switches together to
form a fabric.
F_PortA 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 only.
N_PortA 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.
NOTE
mappingOn Brocade Access Gateway, the configuration of F_Port to N_Port routes.
Additional information
This section lists additional Brocade and industry-specific documentation that you might find
helpful.
BROCADE RESOURCES
The most recent version of documentation is provided on the Brocade Web site, through Brocade
Connect.
Go to http://www.brocade.com and CLIck Brocade Connect to register at no cost for a user ID and
password.
The following documentation is available for Fabric OS:
• Fabric OS Administrator’s Guide
• Fabric OS Command Reference
• Fabric OS MIB Reference
• Fabric OS Message Reference
• Web Tools Administrator’s Guide
• Brocade Glossary
The following documentation is available for Brocade switches:
• Brocade 200E Hardware Reference Manual
• Brocade 200E QuickStart Guide
• Brocade 4016 Hardware Reference Manual
• Brocade 4016 QuickStart Guide
• Brocade 4020 Hardware Reference Manual
• Brocade 4020 QuickStart Guide
For practical discussions about SAN design, implementation, and maintenance, you can obtain
Building SANs with Brocade Fabric Switches through:
http://www.amazon.com
For information about how to use Fabric OS features in a SAN solution, refer to the Principles of
SAN Design (ISBN 0-7414-2824-5), available from the SAN Administrator’s Bookshelf. You can
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.
viiiAccess Gateway Administrator’s Guide
53-1000633-01
OTHER INDUSTRY RESOURCES
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, as well as 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
For information about the iSCSI (internet small computer systems interface) standards, visit the
following Web site:
http://www.ietf.org/rfc/rfc3720.txt
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
-Detailed description of the problem and specific questions
-Description of any troubleshooting steps already performed and 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 illustrated below.
:
*FT00X0054E9*
FT00X0054E9
The serial number label is located as follows:
-Brocade 3014—On the top of the chassis, under the insertion arm
-Brocade 3016 and 4012—On the bottom of the switch module
4024, 4100, 4900, 5000, and 7500 switches and Brocade 24000, and 48000 directors:
Provide the license ID. Use the licenseIdShow command to display the license ID.
-SilkWorm Multiprotocol Router Model AP7420: Provide the switch WWN. Use the
switchShow command to display the switch WWN.
-All other Brocade switches: Provide the switch WWN. Use the wwn command to display the
switch WWN.
Document feedback
Because quality is our first concern at Brocade, 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:
documentation@brocade.com
Provide the title and version number and as much detail as possible about your issue, including the
topic heading and page number and your suggestions for improvement.
xAccess Gateway Administrator’s Guide
53-1000633-01
Chapter
Introduction to the Brocade Access Gateway
This chapter describes the functions of Brocade Access Gateway. The Brocade 200E switch and the
Brocade 4012, 4016, 4020, and 4024 embedded switches running Fabric OS 5.3.0 or higher
support Access Gateway (AG).
Brocade Access Gateway allows multiple host bus adapters (HBAs) to access the fabric using fewer
physical ports. Access Gateway mode transforms the 200E or an embedded switch into a device
management tool that is compatible with different types of fabrics, including Brocade-, Brocade
Enterprise OS (EOS), and Cisco- based fabrics. Refer to the matrix in Appendix B, “Compatibility” for
more details.
When a switch is in Access Gateway mode, it is logically transparent to the host and the fabric.
Brocade Access Gateway mode allows hosts to access the fabric without increasing the number of
switches and simplifies configuration and management in a large fabric by reducing the number of
domain IDs and ports.
Brocade Access Gateway is a device management tool and provides only a subset of Fabric OS
commands. It does not consume critical fabric elements that could inhibit scalability. For example,
a fabric that uses Access Gateways to connect hosts requires fewer domain IDs.
Figure 1 compares a configuration that connects eight hosts to the fabric using Brocade Access
Gateway to the same configuration with standard fabric switches.
FIGURE 1Access Gateway and fabric switch comparison
The difference between the fabric switch (Fabric OS native mode) and Brocade Access Gateway is
as follows:
• The Fabric OS switch is a part of the fabric; it requires two to four times as many physical ports,
consumes fabric resources, and can connect to a Brocade-based fabric only.
• Brocade Access Gateway is outside the fabric; it reduces the number of switches in the fabric
and the number of required physical ports. You can connect Brocade Access Gateway to either
a Brocade-, Brocade EOS-, or Cisco-based fabric.
BROCADE FEATURES IN ACCESS GATEWAY MODE
When using a Brocade switch in Access Gateway mode, most features are no longer applicable.
These features include Admin Domains, Advanced Performance Monitoring, direct connection to
SAN target devices, Fibre Channel Arbitrated Loop support, Fabric Manager, FICON, IP over FC, ISL
trunking, extended fabrics, management platform services, name services (SNS), port mirroring,
Secure Fabric OS, SMI-S, and zoning. These switch features are available in the default switch
mode of operation.
Access Gateway does not support any Secure Fabric OS features. All the security enforcement is
done in the enterprise fabric. DCC policy in the enterprise fabric should include N_Port WWN and
port WWNs of all F_Ports on Access Gateway mapped to that N_Port. In case of DCC policy
violation, the port in the enterprise fabric to which N_Port is connected will be disabled. This will
bring down the corresponding N_Port and F_Ports mapped to it on Access Gateway.
2Access Gateway Administrator’s Guide
53-1000633-01
N_Port
F_Port
N_Port
F_Port
N_Port
F_Port
Hosts
Access Gateway
Edge Switch
Fabric
enabled
NPIV
N_Port
F_Port
E_Port
E_Port
N_Port
F_Port
Hosts
Edge Switch
Fabric Switch
E_Port
E_Port
Fabric
Access Gateway Ports
Fabric Switch Ports
Access Gateway port types
Brocade Access Gateway differs from a typical fabric switch because it connects to the fabric using
node ports (N_Ports). Typically fabric switches connect to the enterprise fabric using ISL
(InterSwitch Link) ports, such as an E_Port.
The following defines the Fibre Channel (FC) port terms used in this manual:
-F_Port, fabric port. A switch port that connects a host, HBA, or storage device to the SAN.
-N_Port, node port. A host, HBA, or storage device port that connects to the F_Port of the
fabric switch.
COMPARING FC PORT CONFIGURATIONS
Brocade Access Gateway multiplexes host connections to the fabric. It presents an F_Port to the
host and an N_Port to an edge fabric switch. Using N_Port ID virtualization (NPIV), Brocade Access
Gateway allows multiple FC initiators to access the SAN on the same physical port. This reduces the
hardware requirements and management overhead of hosts to the SAN connections.
A fabric switch presents F_Ports (or FL_Ports) to the host and storage devices and presents
E_Ports, TE_Ports, or EX_Ports to other switches in the fabric. A fabric switch consumes SAN
resources, such as domain IDs, and participates in fabric management and zoning distribution. A
fabric switch requires more physical ports than Brocade Access Gateway to connect the same
number of hosts.
Access Gateway port types
1
Figure 2 compares the types of ports used by the Access Gateway to those used by a typical fabric
Tab le 1 Compares port configuration between Access Gateway with a typical fabric switch.
TABLE 1Port Configurations
Port TypeAccess GatewayFabric switch
1.The switch is logically transparent to the fabric, therefore it does not participate in the SAN as a fabric switch.
Port mapping
Brocade Access Gateway uses mapping—that is, pre-provisioned routes—to direct traffic from the
hosts to the fabric. When you first enable Access Gateway mode, the F_Ports are mapped to a set
of predefined N_Ports, see Appendix A, “Default Port Mapping”. After the initial setup, you can
manually change the mapping if required.
Figure 3 shows a mapping with eight F_Ports evenly mapped to four N_Ports on Brocade Access
Gateway. The N_Ports connect to the same fabric via different edge switches. This example is also
used to explain mapping, failover, and failback polices.
F_PortYesConnects hosts to Brocade Access
Gateway.
N_PortYesConnects Access Gateway to a fabric
switch.
E_Port
NAISL is not supported.
1
YesConnects devices, such as hosts, HBAs,
and storage to the fabric.
NAN_Ports are not supported.
YesConnects the switch to other switches to
form a fabric.
FIGURE 3Example F_Port to N_Port mapping
4Access Gateway Administrator’s Guide
53-1000633-01
Tab le 2 describes the mapping and fabric connection shown in Figure 3.
TABLE 2Example port mapping
Access GatewayFabric
N_PortF_PortEdge switchF_Port
N_1F_1, F_2Switch_AF_A1
N_2F_3, F_4Switch_AF_A2
N_3F_5, F_6Switch_BF_B1
N_4F_7, F_8Switch_BF_B2
Port initialization
To ensure that all hosts are brought online when Brocade Access Gateway starts up, the ports are
initialized in the following manner:
1. All N_Ports are initialized. During N_Port initialization all the F_Ports are disabled (kept
OFFLINE).
Port initialization
1
The ports are enabled or disabled as follows:
-Enabled (online) if the port receives a fabric login event and is connected to an F_Port of
an edge switch that supports NPIV (N_Port ID virtualization).
-Disabled (offline) if the port is not connected to a fabric or is connected to a fabric port
that does not support NPIV.
2. All F_Ports mapped to online N_Ports are enabled. F_Ports that are inactive or that have no
hosts are disabled.
3. F_Ports mapped to an offline N_Port with the failover policy enabled fail over to an online
N_Port.
4. The host logs in to the fabric as follows:
a. The host sends a FLOGI (fabric login) request.
b. Access Gateway converts the FLOGI request into an FDISC request to the fabric with the
same parameters as the host.
c.The fabric processes the request and sends an FDISC response.
d. Access Gateway converts the FDISC ACC response to the host as an FLOGI ACC using the
same parameters as the fabric.
e. The host receives the response from the fabric.