53-1000605-02 12 Mar 2008 Access Gateway Administrator’s Guide Supporting Fabric OS v6.1.
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.
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 Email: info@brocade.com Asia-Pacific Headquarters Brocade Communications Singapore Pte. Ltd. 9 Raffles Place #59-02 Republic Plaza 1 Singapore 048619 Tel: +65-6538-4700 Fax: +65-6538-0302 Email: apac-info@brocade.
iv Access Gateway Administrator’s Guide 53-1000605-02
Contents About This Document How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . vii What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access Gateway policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Showing current policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Advance Device Security policy. . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Enabling the Advance Device Security policy. . . . . . . . . . . . . . . . 9 Disabling the Advance Device Security policy . . . . . . . . . . . . . . . 9 Setting which devices can log in if ADS policy is enabled. . . . . .
Connectivity to Cisco Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Access Gateway routing requirements with Cisco fabrics. . . . . 34 Enabling NPIV on a Cisco switch. . . . . . . . . . . . . . . . . . . . . . . . . 34 Workaround for QLogic-based devices . . . . . . . . . . . . . . . . . . . . 35 Editing Company ID List if no FC target devices on switch . . . . 35 Adding or deleting an OUI from the Company ID List . . . . . . . .
vi Access Gateway Administrator’s Guide 53-1000605-02
About This Document This document is a procedural guide to help SAN administrators configure and manage Brocade Access Gateway. This preface contains the following sections: • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What’s new in this document The following changes have been made since this document was last released: Information that was added • Platforms • Brocade 300 and 4424 • 16-bit routing (8 Gbps platforms only) • Performance • Access Gateway masterless trunking • Seamless failover • Configuration • Direct Target Attach • Security • Advance Device Security policy • Enhanced routing For further information, refer to the release notes.
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.
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 that and F_Port failovers to if the primary N_Port goes offline.
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.
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: documentation@brocade.com 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.
Chapter 1 Getting Started 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-EOS, and Cisco-based fabrics. Enabling and disabling AG mode on a switch can be performed from the command line interface (CLI) or using Web Tools, Fabric Manager (5.3) or EFCM (9.6).
1 Brocade Access Gateway 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.
Access Gateway port types 1 Access Gateway port types Access Gateway differs from a typical fabric switch because it is not a switch; instead, it is a mode that you enable on a switch using the ag command. After a switch is set in ag mode, it can connect to the fabric using node ports (N_Ports). Typically fabric switches connect to the Enterprise fabric using ISL (InterSwitch Link) ports, such as E_Ports.
1 How Access Gateway maps ports Table 1 shows a comparison of port configurations with AG to a standard fabric switch. TABLE 1 Port configurations Port Type Access Gateway Fabric switch F_Port Yes Connects hosts and targets to Access Gateway. Yes Connects devices, such as hosts, HBAs, and storage to the fabric. N_Port Yes Connects Access Gateway to a fabric switch. NA N_Ports are not supported. E_Port NA ISL is not supported.1 Yes Connects the switch to other switches to form a fabric.
Upgrade and downgrade considerations TABLE 2 1 Description of F_Port-to-N_Port mapping Access Gateway Fabric F_Port N_Port Edge switch F_Port F_1, F_2 N_1 Switch_A F_A1 F_3, F_4 N_2 Switch_A F_A2 F_5, F_6 N_3 Switch_B F_B1 F_7, F_8 N_4 Switch_B F_B2 Upgrade and downgrade considerations Downgrading to Fabric OS v6.0.0 or earlier is supported; however, you must first disable the switch from AG mode. Note the following considerations when upgrading and downgrading from Fabric OS v6.1.
1 6 Upgrade and downgrade considerations Access Gateway Administrator’s Guide 53-1000605-02
Chapter Enabling Policies on Switches in Access Gateway Mode 2 This chapter provides information and procedures for enabling policies on switches in Access Gateway mode. In this chapter • Access Gateway policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 • Showing current policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 • Advance Device Security policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Access Gateway policies • Access Gateway trunking considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . • Trunk group creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Setting up F_Port trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Assigning a Trunk Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Enabling Access Gateway trunking. . . . . . . . . . . . . .
Access Gateway policies 2 Enabling the Advance Device Security policy 1. Connect to the switch and log in as admin. 2. Enter the ag --policyenable ads command. switch:admin> ag --policyenable ads The policy ADS is enabled Disabling the Advance Device Security policy 1. Connect to the switch and log in as admin. 2. Enter the ag --policydisable ads command.
2 Access Gateway policies Setting which devices cannot log in if ADS policy is enabled For example, to set the list of allowed devices for ports 11 and 12 to no access: 1. Connect to the switch and log in as admin. 2. Enter the ag --adsset “11;12 ““ command.
Access Gateway policies 2 Displaying the list of devices on the switch 1. Connect to the switch and log in as admin. 2. Enter the ag --adsshow command.
2 Access Gateway policies Enabling the Automatic Port Configuration policy 1. Connect to the switch and log in as admin. 2. Ensure that the switch is disabled, enter the switchdisable command 3. Enter the ag --policyenable auto command to enable the APC policy. switch:admin> ag --policyenable auto All Port related Access Gateway configurations will be lost. Please save the current configuration using configupload. Do you want to continue? (yes, y, no, n): [no] y 4.
Access Gateway policies 2 Failover Policy When a port is configured as an N_Port and if by default, the Failover policy is enabled, F_Ports are not disabled if its N_Port goes off line. If you specify a Preferred Secondary N_Port for any of the F_Ports, and if the N_Port goes offline, the F_Ports will fail over to the Preferred Secondary N_Port and then re-enable. The specified Preferred Secondary N_Port must be online; otherwise, not the F_Ports will become disabled.
2 Access Gateway policies The ports mapped to N_2 (F_1, F_3, and F_4) fail over to N_3 and N_4. Note that the F_Ports are evenly distributed to the remaining online N_Ports and that the F_2 port did not participate in the failover event.
Access Gateway policies 2 Disabling the Failover policy 1. Connect to the switch and log in as admin. 2. Enter the ag command with the --failovershow operand to display the failover setting. switch:admin> ag --failovershow 13 Failover on N_Port 13 is supported 3. Enter the ag --failoverdisable operand to disable failover.
2 Access Gateway policies Example 3 Host_1 Fabric Access Gateway Hosts Edge Switch (Switch_A) F_1 F_A1 N_1 Host_2 F_2 NPIV enabled F_A2 Host_3 Host_4 F_3 N_2 NPIV enabled Edge Switch (Switch_B) F_4 F_B1 N_3 Host_5 NPIV enabled F_5 F_B2 N_4 Host_6 F_6 Host_7 F_7 Host_8 FIGURE 5 F_8 NPIV enabled Legend Physical connection Mapped online Failover route online Original mapped route (offline) Failback policy behavior Enabling the Failback policy 1.
Access Gateway policies 2 Cold Failover policy All F_Ports for an N_Port that goes offline are failed over to other N_Ports. However, if the N_Port fails to come online after the switch comes online, it triggers cold failover of its F_Ports. If any of these F_Ports have a Preferred Secondary N_Port set, and if the Preferred Secondary N_Port is online, those F_Ports fail over to the Preferred Secondary N_Port during cold failover. If the Preferred Secondary N_Port is not online, those F_Ports are disabled.
2 Access Gateway policies FIGURE 6 Port grouping behavior When a dual redundant fabric configuration is used, F_Ports connected to a switch in AG mode can access the same target devices from both of the fabrics. In this case, you must group the N_Ports connected to the redundant fabric into a single port group. It is recommended to have paths fail over to the redundant fabric when the primary fabric goes down.
Access Gateway policies FIGURE 8 2 pg0 default setup You can create new port groups and add N_Ports to those groups. However, all N_Ports that are not part of any user-created port group are part of the default port group pg0. Because port groups cannot be overlapped, if you specify an N_Port as a Preferred Secondary N_Port and it already belongs to another port group, the Port Group creation fails.
2 Access Gateway policies Adding an N_Port to a port group 1. Connect to the switch and log in as admin. 2. Enter the command ag --pgadd with the “ operands. If you add more than one N_Port you must separate them with a semicolon. switch:admin> ag --pgadd 3 14 N_Port[s] are added to the port group 3 3. Enter the command ag --pgshow to verify the N_Port was added to the specified port group.
Access Gateway policies 2 Renaming a port group 1. Connect to the switch and log in as admin. 2. Enter the command ag --pgrename with the operands, for example, to rename port group with pgid 2 to "MyEvenFabric": switch:admin> ag --pgrename 2 MyEvenFabric Port Group 2 has been renamed as MyEvenFabric successfully 3. Enter the command ag --pgshow to verify the port group has been renamed.
2 Access Gateway N_Port trunking Access Gateway N_Port trunking On switches running in Access Gateway mode, the masterless trunking feature trunks N_Ports because only the external port or the N_Port can connect to a switch in AG mode. After you map or assign F_Ports to an N_Port, the N_Port distributes frames across a set of available path links on the switch in AG mode to an adjacent edge switch. To use Access Gateway masterless trunking, all trunking must be configured on the edge switch.
Access Gateway N_Port trunking 2 Access Gateway trunking considerations TABLE 4 Access Gateway trunking considerations Category Description Area assignment You statically assign the area within the trunk group on the edge switch. That group is the N_Port masterless trunk. The static trunk area you assign must fall within the F_Port trunk group starting from port 0 on a edge switch or blade. The static trunk area you assign must be one of the port’s default areas of the trunk group.
2 Access Gateway N_Port trunking TABLE 4 Access Gateway trunking considerations Category Description portCfgTrunkPort , 0 portCfgTrunkPort , 0 will fail if a Trunk Area is enabled on a port. The port must be Trunk Area disabled first. switchCfgTrunk 0 switchCfgTrunk 0 will fail if a port has TA enabled. All ports on a switch must be TA disabled first.
Access Gateway N_Port trunking TABLE 4 2 Access Gateway trunking considerations Category Description DCC Policy DCC policy enforcement for the F_Port trunk is based on the Trunk Area; the FDISC requests to a trunk port is accepted only if the WWN of the attached device is part of the DCC policy against the TA. The PWWN of the FLOGI sent from the AG will be dynamic for the F_Port trunk master.
2 Access Gateway N_Port trunking Setting up F_Port trunking F_Port trunking is enabled between two separate Fabric OS switches that support trunking and where all the ports on each switch reside in the same quad and are running the same speed. Trunk groups form when you connect two or more cables on one Fabric OS switch to another Fabric OS switch with ports in the same port group or quad. A port group or a quad is a set of sequential ports, for example ports 0-3 in the figure shown below.
2 Access Gateway N_Port trunking The following table shows an example of the Address Identifier. TABLE 6 23 22 Address identifier 21 20 19 18 17 16 15 14 13 Domain ID 12 11 10 9 Area_ID 8 7 6 5 4 3 2 1 0 Port ID Address Identifier 1. Connect to the switch and log in as admin. 2. Disable the ports to be included in the TA. 3.
2 Access Gateway N_Port trunking Configuration management for trunk areas Ports from different ADs are not allowed to join the same Trunk Area group. The porttrunkarea command prevents the different AD's from joining the TA group. When you assign a TA, the ports within the TA group will have the same Index. The Index that was assigned to the ports is no longer part of the switch.
Access Gateway N_Port trunking 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 -id -----------------------id id id id id id id id N8 N4 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N4 N4 N4 N4 N4 N4 N4 N4 No_Module Online No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Modu
2 Access Gateway N_Port trunking F_Port Trunking monitoring For F_Port masterless trunking, you must install Filter, EE or TT monitors on the F_Port trunk port. Whenever the master port changes, it is required to move the monitor to the new master port. For example, if a master port goes down, a new master is selected from the remaining slave ports. APM must delete the monitor from the old master and install the monitor on new master port.
Chapter 3 Connecting Devices Using Access Gateway This chapter describes how to connect multiple devices to a switch in Access Gateway (AG) mode, discusses edge switch compatibility, port requirements, NPIV HBA, and interoperability. Access Gateway supports Direct Target Attach, which allows you to directly attach a target device to a switch in AG mode if the AG switch is connected to an external fabric. AG does not support daisy chaining when two AG devices are connected to each other.
3 Configuring the fabric and edge switch Configuring the fabric and edge switch To connect hosts to the fabric using Access Gateway, configure the fabric using the following parameters. These parameters apply to Fabric OS, M- EOS, and Cisco-based fabrics: • Install and configure the switch as described in the switch’s Hardware Reference Manual before performing these procedures. • Verify that the interop mode parameter is set to 0, Brocade Native mode, or the switch mode is in Native mode.
Configuring the fabric and edge switch 5 5 6 6 7 7 8 8 9 9 10 10 11 11 12 12 13 13 14 14 15 15 16 16 17 17 18 18 19 19 20 20 21 21 master) 22 22 23 23 3 cu cu cu cu cu cu cu cu cu cu cu cu ----id N4 N4 AN AN AN AN AN AN AN AN AN AN N4 N4 N4 N4 N4 Online Online No_Sync No_Sync No_Sync No_Sync No_Sync No_Sync No_Sync No_Sync No_Sync No_Sync No_Module No_Module No_Module No_Module Online F-Port 50:06:0b:00:00:3c:b4:3e F-Port 10:00:00:00:c9:35:43:f3 Disabled (Persistent) E-Port segmented,(zone conflict)
3 Connectivity to Cisco Fabrics Connectivity to Cisco Fabrics When connecting a switch in Access Gateway mode to a Cisco fabric where certain QLogic-based devices are present behind the switch in AG mode, some QLogic FC ASIC-based Host Bus Adapters (HBA)s are not compatible with the routing mechanism used by switches in AG mode. In this case, you must configure the Cisco switch using the Cisco provided procedures to ensure interoperability with Access Gateway.
Connectivity to Cisco Fabrics 3 Workaround for QLogic-based devices If there are QLogic-based devices behind a switch in AG mode, you must use the Cisco provided procedures to connect to a Fabric OS switch in AG mode to a Cisco fabric. Cisco software maintains a list of QLogic-based HBAs. Each HBA is identified by its company ID (also know as Organizational Unit Identifier, or OUI) used in the PWWN during a fabric log in. You can modify the Cisco Company ID entries using the CLI.
3 Connectivity to Cisco Fabrics 00:E0:8B * <- Explicitly deleted entry (from the original default list) Total company ids 6 + - Additional user configured company ids * -Explicitly deleted company ids from default list. Adding or deleting an OUI from the Company ID List The following example shows how to add or delete an OUI (0x112233) from the Company ID List. 1. Enter the following command: config t 2.
Connectivity to Cisco Fabrics 3 Enabling Flat FCID mode if no FC target devices on switch 1. Alternatively, you can place the Cisco switch FCID allocation mode into FLAT mode by entering the following commands: config t fcinterop fcid-allocation flat 2. Enter the following command to enable VSAN mode: vsan database 3. Enter the following two commands to enable the Flat FCID mode: vsan suspend no vsan suspend 4. Press Ctrl-Z to exit. 5.
3 Access Gateway mode Access Gateway mode Before enabling a switch to AG mode, you must save the switch configuration because after you enable AG mode, some fabric information is erased, such as the zone and security databases. For information on backing up and restoring the configuration file, refer to the Fabric OS Administrator’s Guide. Enabling AG mode is disruptive; the switch is disabled and rebooted. You must verify that the switch is set to Native mode or interopmode 0.
3 Access Gateway mode 4. Enter the switchShow command without any options to display the status of all ports. switch:admin> switchshow switchName: switch switchType: 43.
3 Access Gateway mode TABLE 8 Port state description State Description Diag_Flt Port failed diagnostics Lock_Ref locking to the reference signal Testing running diagnostics Offline Connection not established (only for virtual ports) Online The port is up and running Disabling Access Gateway mode Before you disable a switch in AG mode, you should always back up the current configuration. Disabling AG mode clears the F_Port-to-N_Port mapping.
Re-joining switches to a fabric 3 Re-joining switches to a fabric After a switch reboots and AG mode is disabled, the Default zone is set to no access. Therefore, the switch does not immediately join the fabric to which it is connected. Use one of the following methods to re-join a switch to the fabric: • If you saved a Fabric OS configuration before enabling AG mode, download the configuration using the configDownload command.
3 42 Re-joining switches to a fabric Access Gateway Administrator’s Guide 53-1000605-02
Chapter 4 Configuring Ports in Access Gateway mode This chapter explains how to configure ports in Access Gateway mode and how to implement Access Gateway masterless trunking. In this chapter • Port Initialization in Access Gateway mode . . . . . . . . . . . . . . . . . . . . . . . . . . • N_Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Unlocking N_Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 N_Ports 4. The host logs into 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 Accept link service reply (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.
N_Ports 4 The enabled N_Port will automatically come online if it is connected to an Enterprise fabric switch that supports NPIV. NPIV capability should be enabled on the ports connected to the Access Gateway. Use the portcfgnpivport command to enable NPIV capability on the specific port. By default, NPIV is enabled on 8 Gbps switches. NOTE A switch in Access Gateway mode must have at least one port configured as an N_Port.
4 N_Ports Locked N_Port .. .. .. .. .. .. .. .. .. .. ON ON ON ON ON ON 3. Enter the portcfgnport command with 0 operand to unlock N_Port mode. switch:admin> portcfgnport 10 0 Alternatively, to lock a port in N_Port mode, enter the portcfgnport 1 command. switch:admin> portcfgnport 10 1 By default, on embedded switches, all external ports are configured as N_Port lock mode when you enable Access Gateway. Access Gateway connects only FCP initiators and targets to the fabric.
4 N_Ports Current F_Ports Failover and Failback PG_ID and PG_Name Shows the F_Ports that are currently connected to the fabric on the corresponding N_Port. In the case of failover, the current F_Ports and configured F_Ports differ. Indicates whether the N_Port policy is enabled (1) or disabled (0). Indicates whether the Port Grouping policy is enabled (1) or disabled (0). Displaying N_Port mapping 1. Connect to the switch and log in as admin. 2.
4 Port configurations 16 17 18 19 20 21 22 23 16 17 18 19 20 21 22 23 cu --id -id id id AN N4 N4 N4 N4 N4 N4 N4 No_Sync No_Module No_Module No_Light No_Module Online Online Online Disabled (Persistent) N-Port N-Port N-Port 10:00:00:05:1e:35:10:1e 0x5a0200 10:00:00:05:1e:35:10:1e 0x5a0100 10:00:00:05:1e:35:10:1e 0x5a0000 NOTE For a description of the port state, see Table 8 on page 39.
Port configurations ===================================== 0 0 cu AN No_Sync 1 1 cu AN No_Sync 2 2 cu AN No_Sync 3 3 cu AN No_Sync 4 4 cu AN No_Sync 5 5 cu AN No_Sync 6 6 cu AN No_Sync 7 7 cu AN No_Sync 8 8 cu AN No_Sync 9 9 cu AN No_Sync 10 10 -N4 No_Module 11 11 -N4 No_Module 12 12 -N4 No_Module 13 13 id N4 Online 14 14 id N4 Online 15 15 id N4 Online Disabled Disabled Disabled Disabled Disabled Disabled N-Port N-Port N-Port (N-Port Offline (N-Port Offline (N-Port Offline (N-Port Offline (N-Port Offlin
4 Port configurations Failover(1=enabled/0=disabled) Failback(1=enabled/0=disabled) Current F_Ports Configured F_Ports PG_ID : : : : : 1 1 None 7 0 PG_Name : pg0 Adding a preferred secondary N_Port Preferred mapping is optional. Adding a preferred N_Port provides an alternate N_Port for F_Ports to fail over to. The F_Ports must have a primary N_Port mapping before a secondary N_Port can be configured.
Port configurations 4 The following table shows the default F_Port-to-N_Port mapping that is automatically configured when Access Gateway mode is enabled. All N_Ports have failover and failback enabled. All ports must have the POD license active to use Access Gateway on the Brocade 300 and 200E. .
4 Port configurations TABLE 9 52 Access Gateway default F_Port-to-N_Port mapping Brocade Model Total Ports F_Ports N_Ports Default F_ to N_Port Mapping 4024 24 1–16 0, 17–23 1, 2 mapped to 17 9, 10 mapped to 18 3, 4 mapped to 19 11, 12 mapped to 20 5, 6 mapped to 21 13, 14 mapped to 22 7, 8 mapped to 23 15, 16 mapped to 0 4424 24 17-20 1-8 17-20 as N_Port with failover enabled, failback enabled 0, 21-23 as N_Port with failover enabled, failback enabled 1, 2 mapped to 17 3, 4 mapped to 19
Appendix A Troubleshooting This appendix provides troubleshooting instructions. TABLE 10 Troubleshooting Problem Cause Solution Switch is not in Access Gateway mode Switch is in Native switch mode Disable switch using the switchDisable command. Enable Access Gateway mode using the ag --modeenable command. Answer yes when prompted; the switch reboots. Log in to the switch. Display the switch settings using the switchShow command. Verify that the field switchMode displays Access Gateway Mode.
A Troubleshooting TABLE 10 Troubleshooting (Continued) Problem Cause Solution Failover is not working Failover disabled on N_Port. Verify that failover and failback policies are enabled, as follows: Enter the ag --failoverShow command with the operand. Enter the ag --failbackShow command with the operand. Command returns “Failback (or Failover) on N_Port is supported.” If it returns, “Failback (or Failover) on N_Port is not supported.
Index A B Access Gateway comparison to standard switches, 3 compatible fabrics, 2 connecting devices, 31 description, 1 features, 2 mapping description, 5 port mapping, 4 port types, 3 Access Gateway mode comparison, 2 direct target attach, 31 disabling, 40 enabling, 38 port initialization, 43 port types, 3 saving configuration, 40 supported firmware versions, 31 terms, ix ACL policies settings, 32 adding devices to fabric, 10 Address Identifier, 27 Admin domain, 24 ADS Policy adding devices, 10 disablin
portCfgNport, 45, 46, 53 portCfgShow, 53 switchDisable, 33, 40, 41, 53, 54 switchEnable, 41 switchMode, 53, 54 switchShow, 32, 39, 47, 48, 53, 54 compatibility fabric, 32 configuration show, 46 configurations limitations with configdownload command, 24 re-joining switch to fabric, 41 saving AG configuration, 40 using configdownload command, 40 using configupload command, 40 D daisy chaining, 31 DCC policy adding WWN, 27 enabling, 27 limitation creating TA, 25 default area removing ports, 23 devices attachi
internal port F_Port, 48 J NPIV edge switch, 32 enable with portcfgnpivport command, 45 enabling on Cisco switch, 34 enabling on M-EOS swtich, 33 support, 31 join fabric, 41 L O optional features, xi long distance mode, edge switch, 32 M management server, 23 mapping example, 4 ports, 4 show, 46 masterless trunking blades not supported, 24 PID format, 24 M-EOS switch enabling NPIV, 33 N N_Port AG configurations, 44 displaying configurations, 46 displaying status, 47 external port, 48 F_Port, remove,
port types limitations, 23 Preferred, 13 preferred secondary N_Port cold failover, 17 definition, x deleting F_Ports, 50 failover policy, 13 forming groups, 17 not online, 13 online, 13 PWWN format, 25 sharing TA trunk group, 23 Q QLogic-based devices workaround, 35 R removing devices from switch, 10 removing trunk ports, 23 requirements ports, 31 S settings ACL policies, 32 FLOGI, 32 inband queries, 32 Management Server Platform, 32 zone, no access, 41 supported hardware and software, vii switch mode ve
