Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual
Brocade access gateway administrator's guide v6.2.0 (53-1001189-01, april 2009)
Hide thumbs
Also See for A7533A - Brocade 4Gb SAN Switch Base:
- Reference manual (1240 pages) ,
- Command reference manual (894 pages) ,
- Reference (550 pages)
Related Manuals for Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base
Summary of Contents for Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base
-
Page 1: Access Gateway
53-1001189-01 November 24, 2008 Access Gateway Administrator’s Guide Supporting Fabric OS 6.2.0... - Page 2 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.
- Page 3 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...
- Page 4 Access Gateway Administrator’s Guide 53-1001189-01...
-
Page 5: Table Of Contents
Contents About This Document How this document is organized ......xiii Supported hardware and software ......xiii What’s new in this document . - Page 6 Advanced Device Security policy ......10 Enabling the Advanced Device Security policy....10 Disabling the Advanced Device Security policy .
- Page 7 Connectivity to Cisco Fabrics ....... 35 Access Gateway routing requirements with Cisco fabrics..36 Enabling NPIV on a Cisco switch.
- Page 8 viii Access Gateway Administrator’s Guide 53-1001189-01...
- Page 9 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 .
- Page 10 Access Gateway Administrator’s Guide 53-1001189-01...
- Page 11 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 .
- Page 12 Access Gateway Administrator’s Guide 53-1001189-01...
-
Page 13: About This Document
About This Document • How this document is organized ........xiii •... -
Page 14: 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: • 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 •... -
Page 15: Notes, Cautions, And Warnings
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. -
Page 16: Notice To The Reader
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. -
Page 17: Brocade Resources
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... -
Page 18: Document Feedback
• 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. -
Page 19: Chapter 1 Getting Started
Chapter Getting Started In this chapter • Brocade Access Gateway ......... 1 •... -
Page 20: Fabric Os Features In Access Gateway Mode
Fabric OS features in Access Gateway mode 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. -
Page 21: Table 1 Fabric Os Components Supported On Access Gateway
Fabric OS features in Access Gateway mode TABLE 1 Fabric OS components supported on Access Gateway Feature Support Access Control Yes (limited roles) Audit Beaconing Config Download/Upload DHCP Environmental Monitor Error Event Management Extended Fabrics Fabric Device Management Interface (FDMI) Yes* Fabric Manager Yes** Fabric Watch... -
Page 22: Access Gateway Port Types
Access Gateway port types 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). -
Page 23: How Access Gateway Maps Ports
How Access Gateway maps ports Table 2 shows a comparison of port configurations with AG to a standard fabric switch. TABLE 2 Port configurations Port Type Access Gateway Fabric switch F_Port Connects hosts and targets to Connects devices, such as hosts, HBAs, Access Gateway. -
Page 24: Access Gateway Limitations
Access Gateway limitations TABLE 3 Description of F_Port-to-N_Port mapping Access Gateway Fabric F_Port N_Port Edge switch F_Port F_1, F_2 Switch_A F_A1 F_3, F_4 Switch_A F_A2 F_5, F_6 Switch_B F_B1 F_7, F_8 Switch_B F_B2 Access Gateway limitations The limitations of Access Gateway are as follows: •... -
Page 25: Advance Device Security Policy
Upgrade and downgrade considerations for switches in AG mode Note the following upgrade and downgrade considerations when the Brocade policies are enabled. Advance Device Security policy If you upgrade from v5.2.1/v5.3.x to v6.2.0, the ADS policy is disabled. Downgrading to v6.0 or earlier is permitted, but you must disable ADS. - Page 26 Upgrade and downgrade considerations for switches in AG mode Access Gateway Administrator’s Guide 53-1001189-01...
-
Page 27: In This Chapter
Chapter Enabling Policies on Switches in Access Gateway Mode In this chapter • Access Gateway policies ......... . 9 •... -
Page 28: Advanced Device Security Policy
Advanced Device Security policy Advanced Device Security policy The Advanced Device Security (ADS) policy is supported on AG F_Ports. Fabric OS v6.2.0 extends the DCC policy to switches in AG mode to provide an additional level of security. It does this by extending the DCC policy to the physical F_Ports and the NPIV logins on F_Ports. -
Page 29: Setting Which Devices Cannot Log In If Ads Policy Is Enabled
Advanced Device Security policy • The same Allow List can be specified for more than one F_Port. This example show how to set the list of allowed devices for ports 1, 10, and 13 to all access: 1. Connect to the switch and log in as admin. 2. -
Page 30: Displaying The List Of Devices On The Switch
Automatic Port Configuration policy 1. Connect to the switch and log in as admin. 2. Enter the ag --adsadd "3;9" "20:03:08:00:88:35:a0:12;21:00:00:e0:8b:88:01:8b" command. switch:admin> ag --adsadd "3;9" "20:03:08:00:88:35:a0:12;21:00:00:e0:8b:88:01:8b" WWNs added successfully to Allow Lists of the F_Port[s] Displaying the list of devices on the switch 1. -
Page 31: Enabling The Automatic Port Configuration Policy
Automatic Port Configuration policy NOTE When in Access Gateway mode, the Automatic Port Configuration policy may not work when attached to M-EOS switches. M-EOS ports should be set to G_Port to prevent problems with port type discovery. Ports 16-47 on the FC8-48 blade may not be used for AG F_Port Trunking connections. Enabling the Automatic Port Configuration policy 1. -
Page 32: Failover Policy
Failover policy Failover policy Access Gateway Failover and Failback policies ensure maximum uptime for the servers. 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. -
Page 33: Enabling The Failover Policy
Failover policy • Next the F_A2 port goes offline, as shown in Figure 4 on page 15 Example 2 (right), causing the corresponding Access Gateway N_2 port to be disabled. 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. -
Page 34: Disabling The Failover Policy
Failback policy Disabling the Failover policy 1. Connect to the switch and log in as admin. 2. Enter the ag command with the failovershow <n_portnumber> operand to display the failover setting. switch:admin> ag --failovershow 13 Failover on N_Port 13 is supported 3. -
Page 35: Enabling The Failback Policy
Failback policy Example 3 Fabric Access Gateway Hosts Edge Switch Host_1 (Switch_A) F_A1 NPIV Host_2 enabled F_A2 NPIV Host_3 enabled Edge Switch (Switch_B) Host_4 F_B1 NPIV enabled Host_5 F_B2 NPIV enabled Host_6 Host_7 Legend Physical connection Mapped online Failover route online Host_8 Original mapped route (offline) -
Page 36: Cold Failover Policy
Cold Failover policy Failback policy is disabled for port 13 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. -
Page 37: Figure 7 Port Grouping Behavior
Port Grouping policy Figure 7 shows that if you create port groups and when an N_Port goes offline, the F_Ports being routed through that port will fail over to any of the N_Ports that are part of that port group and are currently active. -
Page 38: Creating A Port Group
Port Grouping policy 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. -
Page 39: Removing A Port Group
Port Grouping policy 3. Enter the command ag --pgshow to verify the N_Port was deleted from the specified port group. switch:admin> ag --pgshow PG_ID N_Ports PG_Name ----------------------------------------------------------------------------- 13;15 12;14 Test ----------------------------------------------------------------------------- Removing a port group 1. Connect to the switch and log in as admin. 2. -
Page 40: Access Gateway Policy Enforcement Matrix
Access Gateway policy enforcement matrix Auto Port Configuration auto Disabled Advance Device Security Disabled ---------------------------------------------------------- Access Gateway policy enforcement matrix The following table shows which combinations of policies can co-exist with each other. TABLE 5 Policy enforcement matrix Policies Auto Port Configuration Port Grouping N_Port Trunking ADS Policy... -
Page 41: Access Gateway Trunking Considerations For The Edge Switch
Access Gateway trunking Trunking prevents reassignments of the Port ID (also referred to as the Address Identifier as described in Table 7 on page 26) when N_Ports go offline. You must install the Brocade ISL license on both the Edge switch and the module running in AG mode and you must ensure that both modules running Fabric OS v6.1.0 or later. - Page 42 Access Gateway trunking TABLE 6 Access Gateway trunking considerations for the Edge switch Category Description PWWN The entire Trunk Area trunk group share the same Port WWN within the trunk group. The PWWN is the same across the F_Port trunk that will have 0x2f or 0x25 as the first byte of the PWWN. The TA is part of the PWWN in the format listed in Table 7 page 26.
- Page 43 Access Gateway trunking TABLE 6 Access Gateway trunking considerations for the Edge switch Category Description PID format F_Port masterless trunking is only supported in CORE PID format. Long Distance Long distance is not allowed on F_Port trunks, which means a Trunk Area is not allowed on long distance ports;...
-
Page 44: Trunk Group Creation
Access Gateway trunking The following table describes the PWWN format for F_Port and N_Port trunk ports. TABLE 7 PWWN format for F_Port and N_Port trunk ports NAA = 2 2f:xx:nn:nn:nn:nn:nn:nn Port WWNs for: The valid range of xx is [0 - FF], for maximum of 256. -
Page 45: Assigning A Trunk Area
Access Gateway trunking Assigning a Trunk Area You must enable trunking on all ports to be included in a Trunk Area before you can create a Trunk Area. Use the portCfgTrunkPort or switchCfgTrunk command to enable trunking on a port or on all ports of a switch. -
Page 46: Enabling The Dcc Policy On Trunk
Configuration management for trunk areas Enabling the DCC policy on trunk 1. After you assign a Trunk Area, the porttrunkarea CLI checks whether there are any active DCC policies on the port with the index TA, and then issues a warning to add all the device WWNs to the existing DCC policy with index as TA. - Page 47 Configuration management for trunk areas switchType: 66.1 switchState: Online switchMode: Native switchRole: Principal switchDomain: switchId: fffc02 switchWwn: 10:00:00:05:1e:41:22:80 zoning: switchBeacon: FC Router: FC Router BB Fabric ID: 100 Area Port Media Speed State Proto ===================================== No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module...
-
Page 48: Disabling F_Port Trunking
Access Gateway Cascading Port Type State Master ------------------------------------- Disabling F_Port trunking 1. Connect to the switch and log in as admin. 2. Enter the porttrunkarea --disable command switch:admin> porttrunkarea --disable 36-39 ERROR: port 36 has to be disabled Disable each port prior to removing ports from the TA. Then reissue the command: switch:admin>... -
Page 49: Figure 9 Access Gateway Cascading
Access Gateway Cascading FIGURE 9 Access Gateway cascading Ports are connected between the two AG switches, which are connected to each other. AG cascading connections between devices increase the network use because cascading provides higher over-subscription while allowing you to consolidate the number of ports going to the main fabric. - Page 50 Access Gateway Cascading Access Gateway Administrator’s Guide 53-1001189-01...
-
Page 51: Connecting Devices Using Access Gateway
Chapter Connecting Devices Using Access Gateway In this chapter • Connectivity of multiple devices overview ......33 •... -
Page 52: Verifying The Switch Mode
Fabric and Edge switch configuration • Allow multiple logins. The recommended fabric login setting is the maximum allowed per port and per switch. • Use only WWN zoning throughout the fabric. Access Gateway does not support domain ID and other types of zoning schemes. •... -
Page 53: Setting The Fabric Os Switch To Native Mode
Connectivity to Cisco Fabrics No_Module Online E-Port segmented,(zone conflict)(Trunk master) Online E-Port (Trunk port, master is Port 21 ) Online E-Port (Trunk port, master is Port 21 ) Table 10 on page 41 for a description of the port state. If the switch is in Native mode, you can enable AG mode;... -
Page 54: Access Gateway Routing Requirements With Cisco Fabrics
Connectivity to Cisco Fabrics In this case, you must configure the Cisco switch using the Cisco provided procedures to ensure interoperability with Access Gateway. If you are using Emulex HBAs or any other HBAs that are not based on QLogic FC ASIC technology, ensure that N_Port ID Virtualization (NPIV) is enabled on the Cisco switch and that the switch is running SAN-OS 3.0 (1) or SAN-OS 3.1 (1) or later. -
Page 55: Workaround For Qlogic-Based Devices
Connectivity to Cisco Fabrics 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. -
Page 56: Adding Or Deleting An Oui From The Company Id List
Connectivity to Cisco Fabrics <- Explicitly deleted entry (from the original default list) 00:E0:8B * 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. -
Page 57: Enabling Flat Fcid Mode If No Fc Target Devices On Switch
Connectivity to Cisco Fabrics 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. -
Page 58: Access Gateway Mode
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. -
Page 59: Port States
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.2 switchState: Online switchMode: Access Gateway Mode switchWwn: 10:00:00:05:1e:03:4b:e7 switchBeacon: Area Port Media Speed State Proto ===================================== No_Module Online F-Port... -
Page 60: Disabling Access Gateway Mode
Access Gateway mode TABLE 10 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. -
Page 61: Rejoining Switches To A Fabric
Rejoining switches to a fabric Rejoining 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: •... - Page 62 Rejoining switches to a fabric Access Gateway Administrator’s Guide 53-1001189-01...
-
Page 63: Chapter 4 Configuring Ports In Access Gateway Mode
Chapter Configuring Ports in Access Gateway mode In this chapter • Port Initialization in Access Gateway mode ......45 •... -
Page 64: N_Ports
N_Ports FIGURE 10 Initialized ports in Access Gateway You can expand your fabric by configuring the F_Ports to connect to the fabric as N_Ports, which increases the number of device ports you can connect to a single fabric port. You can connect AG to more than one fabric. -
Page 65: Unlocking N_Ports
N_Ports Figure 11 shows a host connected to an embedded switch’s external F_Port when Access Gateway is enabled. The configured F_Port is mapped to an N_Port. FIGURE 11 Example of adding an external F_Port (F9) on an embedded switch Unlocking N_Ports Unlocking the N_Port configuration automatically changes the port to an F_Port. -
Page 66: Displaying N_Port Configurations
N_Ports 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. It does not support other types of ports, such as ISL (interswitch link) ports. The port types on a fabric switch are not locked. -
Page 67: Displaying N_Port Mapping
N_Ports Displaying N_Port mapping 1. Connect to the switch and log in as admin. 2. Enter the ag mapshow command and specify the port number. The N_Port failover and failback policies and the mapped F_Ports displays. switch:admin> ag --mapshow N_Port Configured_F_Ports Current_F_Ports Failover Failback PG_ID PG_Name ---------------------------------------------------------------------------- SecondFabric 7;8;9... -
Page 68: Port Configurations
Port configurations Port configurations The following mapping updates and adding and removing of ports are only applicable to the Port Grouping policy. Adding F_Ports to an N_Port When you update the mapping, only the F_Ports added or removed are affected. Adding an F_Port to an N_Port routes that traffic to and from the fabric through the specified N_Port. -
Page 69: Removing F_Ports From An N_Port
Port configurations Online N-Port 10:00:00:05:1e:35:10:1e 0x5a0a00 Online N-Port 10:00:00:05:1e:35:10:1e 0x5a0900 Online N-Port 10:00:00:05:1e:35:10:1e 0x5a0800 4. Enter the ag command with the mapadd <n_portnumber> “<f_port1;f_port2;...> operand to add the list of F_Ports to the N_Port. The f_portlist can contain multiple F_Port numbers separated by semicolons, for example “17;18”. -
Page 70: Adding A Preferred Secondary N_Port
Port configurations 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. You add the F_Ports to a preferred secondary N_Port using the prefset command, which sets the preferred N_Port for one or more F_Ports. -
Page 71: Table 11 Access Gateway Default F_Port-To-N_Port Mapping
Port configurations 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. TABLE 11 Access Gateway default F_Port-to-N_Port mapping Brocade... - Page 72 Port configurations TABLE 11 Access Gateway default F_Port-to-N_Port mapping Brocade Total Ports F_Ports N_Ports Default F_ to N_Port Mapping Model 4424 17-20 0, 17-23 as N_Port with failover enabled, failback enabled 1, 2 mapped to 17 3, 4 mapped to 18 5, 6 mapped to 19 7, 8 mapped to 20 9, 10 mapped to 21...
- Page 73 Port configurations TABLE 11 Access Gateway default F_Port-to-N_Port mapping Brocade Total Ports F_Ports N_Ports Default F_ to N_Port Mapping Model 5100 32-39 0-31 32-39 as N_Port with failover enabled, failback enabled 0, 1, 2, 3 mapped to 32 4, 5, 6, 7 mapped to 33 8, 9, 10, 11 mapped to 34 12, 13, 14, 15 mapped to 35 16, 17, 18, 19 mapped to 36...
- Page 74 Port configurations Access Gateway Administrator’s Guide 53-1001189-01...
-
Page 75: Appendix A Troubleshooting
Appendix Troubleshooting This appendix provides troubleshooting instructions. TABLE 12 Troubleshooting Problem Cause Solution Switch is not in Access Switch is in Native switch mode Disable switch using the switchDisable command. Gateway mode Enable Access Gateway mode using the ag modeenable command. Answer yes when prompted;... - Page 76 Troubleshooting TABLE 12 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 <port_number> operand. Enter the ag failbackShow command with the <port_number> operand.
- Page 77 Index Access Gateway behavior, failover policy cascading comparison to standard switches compatible fabrics connecting devices connecting two AGs Cisco switch description adding OUIs displaying information AG routing requirements features Company ID list mapping description deleting OUIs port mapping displaying FCID port types editing Company ID list Access Gateway mode...
- Page 78 commands ag --failbackDisable Edge switch ag --failbackEnable FLOGI ag --failbackShow long distance mode setting ag --failoverDisable NPIV ag --failoverEnable settings ag --failoverShow external port, N_Port ag --mapAdd ag --mapDel ag --mapShow ag --modeDisable ag --modeEnable F_Port ag --modeShow adding external port on embedded switch cfgSave Address Identifier configDownload...
- Page 79 non disruptive NPIV Edge switch ICL ports, limitations enable with portcfgnpivport command inband queries enabling on Cisco switch internal port, F_Port enabling on M-EOS switch support join fabric optional features xvii long distance mode, Edge switch Policies Access Gateway Advance Device Security enabling DCC policy management server enforcement matrix...
- Page 80 preferred secondary N_Port trunk area cold failover activate DCC policy definition assign deleting F_Ports configuration management failover policy disabling forming groups remove ports not online standby CP online using the porttrunkarea command PWWN trunk groups, create format trunk master, limitation sharing TA trunk group trunking enabling...