hit counter script
HP StoreFabric SN6500B Administrator's Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. StoreFabric SN6500B
  6. Administrator's manual
HP StoreFabric SN6500B Administrator's Manual

HP StoreFabric SN6500B Administrator's Manual

Brocade access gateway administrator's guide v7.1.0 (53-1002743-01, march 2013)
Hide thumbs Also See for StoreFabric SN6500B:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Administrator's Manual
53-1002743-01
®
14 December 2012

Access Gateway

Administrator's Guide
Supporting Fabric OS v7.1.0

Advertisement

Table of Contents
loading

Related Manuals for HP StoreFabric SN6500B

Summary of Contents for HP StoreFabric SN6500B

  • Page 1: Access Gateway

    53-1002743-01 ® 14 December 2012 Access Gateway Administrator’s Guide Supporting Fabric OS v7.1.0...
  • Page 2 Copyright © 2007-2012 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, NetIron, SAN Health, ServerIron, and TurboIron are registered trademarks, and AnyIO, Brocade Assurance, Brocade NET Health, Brocade One, CloudPlex, MLX, VCS, VDX, and When the Mission Is Critical, the Network Is Brocade are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
  • Page 3 Document History 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 October 2007 and changes to N_Port mappings.
  • Page 4 Access Gateway Administrator’s Guide 53-1002743-01...

  • Page 5: Table Of Contents

    Contents About This Document How this document is organized ......xiii Supported hardware and software ......xiv What’s new in this document .
  • Page 6 Access Gateway mapping ........15 Port mapping ........16 F_Port Static Mapping .
  • Page 7 Persistent ALPA policy........48 Enabling the Persistent ALPA policy .
  • Page 8 Chapter 4 SAN Configuration with Access Gateway Connectivity of multiple devices overview ..... 73 Considerations for connecting multiple devices ... . 73 Direct target attachment .
  • Page 9 Figures Figure 1 Switch function in Native mode ........2 Figure 2 Switch function in Access Gateway mode .
  • Page 10 Access Gateway Administrator’s Guide 53-1002743-01...
  • Page 11 Tables Table 1 Fabric OS components supported on Access Gateway ..... 3 Table 2 Behavior of sending AG switch and receiving fabric switch with different policies configured .
  • Page 12 Access Gateway Administrator’s Guide 53-1002743-01...

  • Page 13: About This Document

    About This Document • How this document is organized ........xiii •...

  • Page 14: Supported Hardware And Software

    Supported hardware and software In those instances in which 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. Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc., for Fabric OS v7.1.0, documenting all possible configurations and scenarios is beyond the scope of this document.

  • Page 15: Document Conventions

    • Chapter 2 Added port mapping details for the Brocade 5430 switch to “Access Gateway default port mapping” on page 17. Table 5, Added “D_Port support” on page 32. • Chapter 3 Added notes to “Failover policy” on page 50 and “Failback policy”...

  • Page 16: Notes, Cautions, And Warnings

    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.

  • Page 17: Key Terms For Access Gateway

    Corporation Referenced trademarks and products Emulex Corporation Emulex QLogic Corporation QLogic Key terms for Access Gateway 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.

  • Page 18: Additional Information

    Additional information This section lists additional Brocade and industry-specific documentation that you might find helpful. Brocade resources To get up-to-the-minute information, go to http://my.brocade.com to register at no cost for a user ID and password. White papers, online demonstrations, and data sheets are available through the Brocade website http://www.brocade.com/products-solutions/products/index.page For additional Brocade documentation, visit the Brocade website: http://www.brocade.com...

  • Page 19: Document Feedback

    • Switch model • Switch operating system version • Error numbers and messages received • supportSave command output • 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 •...
  • Page 20 Access Gateway Administrator’s Guide 53-1002743-01...

  • Page 21: Chapter 1 Access Gateway Basic Concepts

    Chapter Access Gateway Basic Concepts • Brocade Access Gateway overview........1 •...

  • Page 22: Figure 1 Switch Function In Native Mode

    Brocade Access Gateway overview FIGURE 1 Switch function in Native mode Access Gateway Administrator’s Guide 53-1002743-01...

  • Page 23: Fabric Os Features In Access Gateway Mode

    Fabric OS features in Access Gateway mode FIGURE 2 Switch function in Access Gateway mode Fabric OS features in Access Gateway mode Table 1 lists Fabric OS components that are supported on a switch when AG mode is enabled. “Yes” indicates that the feature is supported in Access Gateway mode. “No” indicates that the feature is not provided in AG mode.
  • Page 24 Fabric OS features in Access Gateway mode TABLE 1 Fabric OS components supported on Access Gateway (Continued) Feature Support Buffer Credit Recovery (CR) Yes - Refer to “Buffer credit recovery support” page 5. Config Download/Upload Device Authentication Refer to “Device authentication support” page 6.

  • Page 25: Buffer Credit Recovery Support

    Fabric OS features in Access Gateway mode TABLE 1 Fabric OS components supported on Access Gateway (Continued) Feature Support Name Server Native Interoperability Mode Network Time Protocol (NTP) No (no relevance from fabric perspective) Open E_Port Performance Monitor Persistent ALPA Port Decommission Port Mirroring QuickLoop, QuickLoop Fabric...

  • Page 26: Forward Error Correction Support

    Fabric OS features in Access Gateway mode It is highly recommended that you disable this feature on the AG switch before connecting to a switch running Fabric OS less than 7.1. Enable and disable CR using the portcfgcreditrecovery command. Refer to the Fabric OS Command Reference for more information on this command. Specific switch platforms support this feature either in R_RDY or VC_RDY mode.
  • Page 27 Fabric OS features in Access Gateway mode For details on installing FCAP certificates and creating DHCAP secrets on the switch in AG or native mode, refer to the Fabric OS Administrator’s Guide or Fabric OS Command Reference. For general information on authentication, refer to the section on authentication policy for fabric elements in the Configuring Security Policies chapter of the Fabric OS Administrator’s Guide.

  • Page 28: Table 2 Behavior Of Sending Ag Switch And Receiving Fabric Switch With Different Policies Configured

    Fabric OS features in Access Gateway mode TABLE 2 Behavior of sending AG switch and receiving fabric switch with different policies configured Fabric switch with device Fabric switch with device Fabric switch with device policy mode ON policy mode PASSIVE policy mode OFF AG switch with switch Authorization negotiation -...

  • Page 29: Access Gateway Port Types

    Access Gateway port types • Authentication is not supported between an AG switch running Fabric OS v7.1.0 or later and a fabric running Fabric OS earlier than v7.1.0. If the AG switch is connected to fabric switch running Fabric OS earlier than v7.1.0, the AG switch N_Ports will disable if authentication is enabled on both switches.

  • Page 30: Figure 3 Port Usage Comparison

    Access Gateway port types Access Gateway Ports Switch in AG mode Fabric Hosts Edge Switch N_Port F_Port F_Port N_Port NPIV enabled N_Port F_Port Fabric Switch Ports Fabric Switch in Native Hosts Fabric mode Fabric Switch E_Port E_Port N_Port F_Port E_Port F_Port N_Port E_Port...

  • Page 31: Access Gateway Hardware Considerations

    Access Gateway hardware considerations TABLE 4 Port configurations Port type Available on Access Gateway? Available on Fabric switch? F_Port Connects hosts and targets to Connects devices, such as hosts, HBAs, Access Gateway. and storage to the fabric. N_Port Connects Access Gateway to a fabric N_Ports are not supported.
  • Page 32 Access Gateway hardware considerations Access Gateway Administrator’s Guide 53-1002743-01...

  • Page 33: Chapter 2 Configuring Ports In Access Gateway Mode

    Chapter Configuring Ports in Access Gateway Mode • Enabling and disabling Access Gateway mode ..... . . 13 • Access Gateway mapping ........15 •...

  • Page 34: Port State Description

    Enabling and disabling Access Gateway mode Enter the ag modeshow command to verify that AG mode is enabled. switch:admin> ag --modeshow Access Gateway mode is enabled. You can display the port mappings and status of the host connections to the fabric on Access Gateway.

  • Page 35: Access Gateway Mapping

    Access Gateway mapping TABLE 5 Port state description (Continued) State Description Lock_Ref Locking to the reference signal Testing Running diagnostics Offline Connection not established (only for virtual ports) Online Port is up and running Access Gateway mapping When operating in AG mode, you must specify pre-provisioned routes that AG will use to direct traffic from the devices (hosts or targets) on its F_Ports to the ports connected to the fabric using its N_Ports.

  • Page 36: Port Mapping

    Access Gateway mapping Port mapping F_Ports must be mapped to N_Ports before the F_Ports can come online. Figure 5 on page 16 shows an example in which eight F_Ports are mapped evenly to four N_Ports on a switch in AG mode.

  • Page 37: Table 7 Access Gateway Default Port Mapping

    Access Gateway mapping NOTE All Ports On Demand (POD) licenses must be present to use Access Gateway on the Brocade 300, 5100, 6505, and 6510. TABLE 7 Access Gateway default port mapping Brocade Total ports F_Ports N_Ports Default port mapping Model VA-40FC 0-31...
  • Page 38 Access Gateway mapping TABLE 7 Access Gateway default port mapping (Continued) Brocade Total ports F_Ports N_Ports Default port mapping Model 5430 1-10 0, 11-15 1, 5 mapped to 11 2, 6 mapped to 12 3, 7 mapped to 13 4, 8 mapped to 14 9 mapped to 15 10 mapped to 0 5450...
  • Page 39 Access Gateway mapping TABLE 7 Access Gateway default port mapping (Continued) Brocade Total ports F_Ports N_Ports Default port mapping Model 6510 0-39 40-47 0-4 mapped to 40 5-9 mapped to 41 10-14 mapped to 42 15-19 mapped to 43 20-24 mapped to 44 25-29 mapped to 45 30-34 mapped to 46 35-39 mapped to 47...

  • Page 40: F_Port Static Mapping

    Access Gateway mapping Adding F_Ports to an N_Port You can modify the default port mapping by adding F_Ports to an N_Port. Adding an F_Port to an N_Port routes that traffic to and from the fabric through the specified N_Port. You can assign an F_Port to only one primary N_Port at a time. If the F_Port is already assigned to an N_Port, you must first remove it from the N_Port before you can add it to a different N_Port.

  • Page 41: Device Mapping

    Access Gateway mapping Once F_Port Static Mapping is enabled, the F_Port and all attached devices log out of the previously mapped N_Port and log in to the new N_Port. Use the following steps to remove the static mapping: 1. Connect to the switch and log in using an account assigned to the admin role. 2.
  • Page 42 Access Gateway mapping Device mapping Device mapping allows you to map individual N_Port ID Virtualization (NPIV) devices to N_Ports. By mapping device WWNs directly to an N_Port group (recommended) or specific N_Ports, traffic from the device will always go to the same N_Port or N_Port group, regardless of the F_Port where the device logs in.

  • Page 43: Figure 6 Example Of Device Mapping To N_Port Groups

    Access Gateway mapping Hosts/Targets Access Gateway WWN1 WWN2 WWN3 WWN4 WWN5 FIGURE 6 Example of device mapping to N_Port groups Figure 7 shows an example of device mapping to specific N_Ports. Note that you can map one or multiple WWNs to one N_Port to allow multiple devices to log in through one N_Port. Access Gateway Administrator’s Guide 53-1002743-01...

  • Page 44: Figure 7 Example Device Mapping To An N_Port

    Access Gateway mapping Hosts/Targets Access Gateway WWN1 WWN2 WWN3 WWN4 WWN5 WWN6 WWN7 WWN8 FIGURE 7 Example device mapping to an N_Port Static versus dynamic mapping Device mapping can be classified as either “static” or “dynamic” as follows: • Device mapping to an N_Port and to an N_Port group are considered static. Static mappings persists across reboots and can be saved and restored with Fabric OS configUpload and configDownload commands.
  • Page 45 Access Gateway mapping Use the following steps to map one or more devices to an N_Port group or remove device mapping from an N_Port group. 1. Connect to the switch and log in using an account assigned to the admin role. 2.
  • Page 46 Access Gateway mapping 3. To change all current device mappings to a different N_Port, enter the ag --addwwnmapping N_Port command with the --all option. The following command changes all the existing device mappings to use port 17. ag --addwwnmapping 17 --all 4.
  • Page 47 Access Gateway mapping The following example enables two device WWNs. switch:admin> ag --wwnmappingenable “10:00:00:06:2b:0f:71:0c; 10:00:00:05:1e:5e:2c:11” 3. Enter the ag wwnmappingenable command with the --all option to enable mapping for all currently available WWNs. The --all option will not affect mappings made in the future. Any mapping added for a new device (a device for which mapping is not disabled) will be enabled by default.

  • Page 48: Considerations For Access Gateway Mapping

    Access Gateway mapping When this behavior occurs, the VM’s WWN will be properly logged in to the fabric. The WWN appears in the output of ag --show and ag --wwnmapshow, as well as on the switch. The output from the portperfshow command displays all traffic on the port to which the ESX server port is mapped (base PID).
  • Page 49 Access Gateway mapping 1. Static device mapping to N_Port (if defined) 2. Device mapping to N_Port group (if defined) For more information, refer to “Port Grouping policy” on page 41. 3. Automatic Device Load Balancing within a port group (if enabled) For more information, refer to “Port Grouping policy”...

  • Page 50: N_Port Configurations

    N_Port configurations N_Port configurations By default, on embedded switches, only the internal ports of Access Gateway are configured as F_Ports. All external ports are configured (locked) as N_Ports. On standalone switches with AG support, a preset number of ports are locked as N_Ports, and the rest of the ports operate as standard F_Ports.

  • Page 51: Displaying N_Port Configurations

    N_Port configurations Displaying N_Port configurations Use the following steps to determine which ports on a switch are locked as N_Ports. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the portcfgnport command. Command output will display “ON” for locked N_Ports. Unlocking N_Ports By default, on embedded switches, all external ports are configured in N_Port lock mode when you enable Access Gateway.

  • Page 52: D_Port Support

    D_Port support D_Port support You can convert a Fibre Channel port into a D_Port on an AG switch and connected fabric switch or another AG switch (cascaded configuration) to test the link between the ports. When you configure the ports on each end of the link as D_Ports, diagnostic tests automatically initiate on the link when the D_Ports go online.

  • Page 53: Saving Port Mappings

    D_Port support Saving port mappings Before configuring D_Ports, you must remove all mappings between the subject ports and device as they will not be retained. This includes port (N_Port to F_Port), device (WWN), static, and dynamic mapping. You can save N_Port mappings using Fabric OS commands. Once you save the mappings, you can display them so that you can manually reconfigure them after the D_Port is disabled.
  • Page 54 D_Port support Access Gateway Administrator’s Guide 53-1002743-01...

  • Page 55: Managing Policies And Features In Access Gateway Mode

    Chapter Managing Policies and Features in Access Gateway Mode • Access Gateway policies overview ....... . . 35 •...

  • Page 56: Access Gateway Policy Enforcement Matrix

    Advanced Device Security policy Access Gateway policy enforcement matrix Table 8 shows which policies can be enabled at the same time. For example, in the Auto Port Configuration policy row, only N_Port Trunking and Advanced Device Security can be enabled with this policy.

  • Page 57: Enabling And Disabling The Ads Policy

    Advanced Device Security policy Enabling and disabling the ADS policy By default, the ADS policy is disabled. When you manually disable the ADS policy, all of the allow lists (global and per-port) are cleared. Before disabling the ADS policy, you should save the configuration using the configUpload command in case you need this configuration again.
  • Page 58 Advanced Device Security policy Setting the list of devices not allowed to log in 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag --adsset command with the appropriate options to set the list of devices not allowed to log in to specific ports.

  • Page 59: Ads Policy Considerations

    Automatic Port Configuration policy 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 allowed devices on the switch 1. Connect to the switch and log in using an account assigned to the admin role. 2.

  • Page 60: Enabling And Disabling The Apc Policy

    Automatic Port Configuration policy Enabling and disabling the APC policy Use the following steps to enable and disable Automatic Port Configuration policy. This policy is disabled by default in Access Gateway. Enabling the APC policy 1. Connect to the switch and log in using an account assigned to the admin role. 2.

  • Page 61: Port Grouping Policy

    Port Grouping policy Port Grouping policy Use the Port Grouping (PG) policy to partition the fabric, host, or target ports within an AG-enabled module into independently operated groups. Use the PG policy in the following situations: • When connecting the AG module to multiple physical or virtual fabrics. •...

  • Page 62: Adding An N_Port To A Port Group

    Port Grouping policy F_Port1 N_Port1 Fabric-1 Storage Array F_Port2 F_Port3 N_Port2 Fabric-2 F_Port4 FIGURE 10 Port group 1 (PG1) setup Adding an N_Port to a port group 1. Connect to the switch and log in using an account assigned to the admin role. 2.

  • Page 63: Renaming A Port Group

    Port Grouping policy Renaming a port group 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag --pgrename command with the appropriate options to rename a port group. In the following example, port group 2 is renamed to MyEvenFabric. switch:admin>...

  • Page 64: Creating A Port Group And Enabling Automatic Login Balancing Mode

    Port Grouping policy Managed Fabric Name Monitoring mode When enabled, Managed Fabric Name Monitoring (MFNM) mode queries the fabric name at a specific time period. If it detects an inconsistency, for example all the N_Ports within a port group are not physically connected to the same physical or virtual fabric, it generates a RASLOG message. In “default”...

  • Page 65: Enabling Mfnm Mode

    Port Grouping policy 5. Enter the agautomapbalance --show command to display the automatic login redistribution settings for port groups. In the following example, there are two port groups, 0 and 1. switch:admin> agautomapbalance --show AG Policy: pg -------------------------------------------- PG_ID LB mode nport fport -------------------------------------------- 0 Enabled Enabled...

  • Page 66: Displaying The Current Mfnm Mode Timeout Value

    Port Grouping policy Displaying the current MFNM mode timeout value 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag --pgfnmtov command to display the current MFNM timeout value. switch:admin> ag --pgfnmtov Fabric Name Monitoring TOV: 120 seconds Setting the current MFNM mode timeout value 1.

  • Page 67: Upgrade And Downgrade Considerations For The Port Grouping Policy

    Device Load Balancing policy Upgrade and downgrade considerations for the Port Grouping policy Downgrading to Fabric OS v6.4.0 or earlier is supported. Note the following considerations when upgrading to Fabric OS 7.1.0: • When upgrading to Fabric OS v7.1.0 from v6.4.0, the PG policy that was enforced in Fabric OS v6.4.0 continues to be enforced in Fabric OS v7.1.0 and the port groups are retained.

  • Page 68: Device Load Balancing Policy Considerations

    Persistent ALPA policy Device Load Balancing policy considerations • The Device Load Balancing policy should be enabled on the edge AG of a cascaded AG configuration. • The Device Load Balancing policy is not applicable on a port group when the APC policy or Automatic Login Balancing are enabled.

  • Page 69: Disabling The Persistent Alpa Policy

    Persistent ALPA policy 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag persistentalpaenable command to enable persistent ALPA in flexible (-f) or stringent (-s) mode. The following example shows enabling the policy in flexible mode. switch:admin>...

  • Page 70: Persistent Alpa Policy Considerations

    Failover policy 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag clearalpamap command with the appropriate option to remove the PWW-to-ALPA mapping for a specific port. In the following example, the mapping for port 2 is cleared from the database.
  • Page 71 Failover policy Failover configurations in Access Gateway The following sequence describes how a failover event occurs: • An N_Port goes offline. • All F_Ports mapped to that N_Port are temporarily disabled. • If the Failover policy is enabled on an offline N_Port, the F_Ports mapped to it will be distributed among available online N_Ports.

  • Page 72: Figure 11 Failover Behavior

    Failover policy Example 2 Example 1 Access Gateway Access Gateway Hosts Hosts Host_1 Host_1 Fabric Fabric Edge Switch Edge Switch (Switch_A) (Switch_A) Host_2 Host_2 F_A1 F_A1 Host_3 Host_3 F_A2 F_A2 Host_4 Host_4 Edge Switch Edge Switch (Switch_B) (Switch_B) Host_5 F_B1 Host_5 F_B1 Host_6...

  • Page 73: Failover With Device Mapping

    Failover policy Deleting F_Ports from a preferred secondary N_Port 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag --prefdel command with the “F_Port1;F_Port2;...” N_Port options to delete F_Ports from an N_Port. The list of F_Ports must be enclosed in quotation marks.

  • Page 74: Enabling And Disabling The Failover Policy On An N_Port

    Failover policy Deleting a preferred secondary N-Port for device mapping (optional) Use the following steps to remove a secondary N_Port where devices will connect if their first or primary N_Port, if defined, is unavailable. 1. Connect to the switch and log in using an account assigned to the admin role. 2.

  • Page 75: Upgrade And Downgrade Considerations For The Failover

    Failback policy 3. Enter the ag failoverdisable -pg pgid command to disable failover. switch:admin> ag --failoverdisable -pg 3 Failover policy is disabled for port group 3 Upgrade and downgrade considerations for the Failover policy Consider the following when upgrading or downgrading Fabric OS versions: •...

  • Page 76: Enabling And Disabling The Failback Policy On An N_Port

    Failback policy Ports F_1 and F_2 are mapped to N_1 and continue routing to N_3. Ports F_3 and F_4, which were originally mapped to N_2, are disabled and rerouted to N_2, and then enabled. Example 3 Fabric Access Gateway Hosts Edge Switch Host_1 (Switch_A)

  • Page 77: Enabling And Disabling The Failback Policy For A Port Group

    Failback policy Enabling and disabling the Failback policy for a port group Use the following steps to enable or disable the Failback policy on all the N_Ports belonging to the same port group. 1. Connect to the switch and log in using an account assigned to the admin role. 2.

  • Page 78: Trunking In Access Gateway Mode

    Trunking in Access Gateway mode Trunking in Access Gateway mode The hardware-based Port Trunking feature enhances management, performance, and reliability of Access Gateway N_Ports when they are connected to Brocade fabrics. Port trunking combines multiple links between the switch and AG module to form a single, logical port. This enables fewer individual links, thereby simplifying management.

  • Page 79: Configuration Management For Trunk Areas

    Trunking in Access Gateway mode Trunk group creation 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.

  • Page 80: Table 9 Address Identifier

    Trunking in Access Gateway mode 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 81: Enabling Trunking

    Trunking in Access Gateway mode 3. Turn on the trunk ports. Trunk ports should be turned on after issuing the secpolicyactivate command to prevent the ports from becoming disabled in the case where there is a DCC security policy violation. Enabling trunking 1.

  • Page 82: Ag Trunking Considerations For The Edge Switch

    Trunking in Access Gateway mode AG trunking considerations for the Edge switch Table 10 describes the Access Gateway trunking considerations for the Edge switch. TABLE 10 Access Gateway trunking considerations for the Edge switch Category Description Area assignment You statically assign the area within the trunk group on the Edge switch.
  • Page 83 Trunking in Access Gateway mode TABLE 10 Access Gateway trunking considerations for the Edge switch (Continued) Category Description Default Area Port X is a port that has its Default Area the same as its Trunk Area. The only time you can remove port X from the trunk group is if the entire trunk group has the Trunk Area disabled.

  • Page 84: Table 10 Access Gateway Trunking Considerations For The Edge Switch

    Trunking in Access Gateway mode TABLE 10 Access Gateway trunking considerations for the Edge switch (Continued) Category Description configDownload and configUpload If you issue the configdownload command for a port configuration that is not compatible with F_Port trunking, and the port is Trunk-Area-enabled, then the port will be persistently disabled.

  • Page 85: Trunking Considerations For Access Gateway Mode

    Adaptive Networking on Access Gateway Table 11 describes the PWWN format for F_Port and N_Port trunk ports. TABLE 11 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 86: Qos: Ingress Rate Limiting

    Adaptive Networking on Access Gateway QoS: Ingress rate limiting Ingress rate limiting restricts the speed of traffic from a particular device to the switch port. On switches in AG mode, you must configure ingress rate limiting on F_Ports. For more information and procedures for configuring this feature, refer to “Ingress Limiting” in the Fabric OS Administrator’s Guide.

  • Page 87: Adaptive Networking On Access Gateway Considerations

    Per-Port NPIV login limit Adaptive Networking on Access Gateway considerations • QoS is configured in the fabric, as normal, and not on the AG module.. • QoS on Access Gateway is only supported on Fabric OS v6.3 and later. • You should disable HBA QoS if connected to a Fabric OS v6.2 AG switch.

  • Page 88: Advanced Performance Monitoring

    Advanced Performance Monitoring Advanced Performance Monitoring Advanced Performance Monitoring (APM) is a licensed feature that allows you to monitor traffic on a specific port. This feature supports end to end and frame monitors. The following licenses must be appropriately installed on the AG switch to use end-to-end and frame monitors: •...

  • Page 89: Frame Monitors

    Advanced Performance Monitoring • Deleting a monitor Frame monitors Frame monitors count the number of times a frame with a particular pattern is transmitted by a port and generate alerts when thresholds are crossed. Frame monitoring is achieved by defining a filter, or frame type, for a particular purpose.

  • Page 90: Limitations For Using Apm

    Considerations for the Brocade 8000 Limitations for using APM The following limitations apply to using APM on an AG switch: • The Top Talker and ISL monitoring features used for APM in switch mode are not supported on an AG switch. •...

  • Page 91: Fabric Os Command Support

    Considerations for the Brocade 8000 Port trunking and QoS features Because the Brocade 8000 has limited available buffers and port trunking and QoS require more buffers than normal, consider the following points: • Do not enable QoS by itself on more than six Fibre Channel ports at a time. If you attempt to enable QoS on more than six ports, the Brocade 8000 may enter buffer-limited mode.

  • Page 92: Considerations For The Brocade 6505 And 6510

    Considerations for the Brocade 6505 and 6510 • The following commands have restricted usage, mostly because the Brocade 8000 contains only eight Fibre Channel ports and does not support the Automatic Port Configuration policy: ag --pgcreate ag --policyenable ag --policydisable portcfgdefault •...

  • Page 93: Connectivity Of Multiple Devices Overview

    Chapter SAN Configuration with Access Gateway • Connectivity of multiple devices overview ......73 •...

  • Page 94: Direct Target Attachment

    Direct target attachment Direct target attachment FCP targets can directly connect to an AG module instead of through a fabric connection, as illustrated in Figure Fabric-Attached Target Direct-Attached Target Servers Servers Switch in Switch in AG Mode AG Mode FCP Target Fabric Fabric FCP Target...

  • Page 95: Target Aggregation

    Target aggregation • Hosts and targets should be in separate port groups. • Direct target attachment configurations are not enforced. Target aggregation Access Gateway mode is normally used as host aggregation. In other words, a switch in AG mode aggregates traffic from a number of host systems onto a single uplink N_Port. Similarly, many targets can be aggregated onto to a single uplink N_Port, as shown in Figure 15.

  • Page 96: Access Gateway Cascading

    Access Gateway cascading Access Gateway cascading Access Gateway cascading is an advanced configuration supported in Access Gateway mode. Access Gateway cascading allows you to further increase the ratio of hosts to fabric ports to beyond what a single switch in AG mode can support. Access Gateway cascading allows you to link two Access Gateway (AG) switches back to back.

  • Page 97: Fabric And Edge Switch Configuration

    Fabric and Edge switch configuration • Due to high subscription ratios that could occur when cascading AGs, ensure there is enough bandwidth for all servers when creating such configurations. The subscription ratio becomes more acute in a virtual environment. Fabric and Edge switch configuration To connect devices to the fabric using Access Gateway, configure the fabric and Edge switches within the fabric that will connect to the AG module using the following parameters.

  • Page 98: Enabling Npiv On M-Eos Switches

    Connectivity to Cisco fabrics Table 5 on page 14 for a description of the port state. If the switch is in Native mode, you can enable AG mode; otherwise, set the switch to Native mode, and then reboot the switch. Enabling NPIV on M-EOS switches 1.

  • Page 99: Rejoining Fabric Os Switches To A Fabric

    Rejoining Fabric OS switches to a fabric 5. Enter the following commands to save the MDS switch connection: copy start Your Cisco switch is now ready to connect to a switch in Access Gateway mode. Rejoining Fabric OS switches to a fabric When a switch reboots after AG mode is disabled, the Default zone is set to no access.
  • Page 100 Rejoining Fabric OS switches to a fabric Access Gateway Administrator’s Guide 53-1002743-01...

  • Page 101: Appendix A Troubleshooting

    Appendix Troubleshooting Table 12 provides troubleshooting instructions for Access Gateway. 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.
  • Page 102 Troubleshooting TABLE 12 Troubleshooting (Continued) Problem Cause Solution Access Gateway is mode Access Gateway must be disabled. Disable switch using the switchDisable command. not wanted Disable Access Gateway mode using the ag modeDisable command. Answer yes when prompted; the switch reboots. Log in to the switch.
  • Page 103 Index authentication considerations device Access Gateway limitations cascading policy modes comparison to standard switches related commands compatible fabrics support connecting devices authentication, limitations connecting two AGs description displaying information features limitations mapping description behavior, failover policy port types Brocade 6505 and 6510, AG considerations Access Gateway mode Brocade 8000 comparison...
  • Page 104 commands DCC policy ag --addwwnfailovermapping adding WWN ag --addwwnpgmapping enabling ag --delwwnfailovermapping limitation creating TA ag --delwwnpgmapping default area, removing ports ag --failbackEnable device load balancing ag --failbackShow device load balancing policy ag --failoverDisable APC policy ag --failoverEnable considerations ag --failoverShow disabling ag --mapAdd enabling...
  • Page 105 F_Port join fabric adding external port on embedded switch description mapping, example maximum number mapped to N_Port settings, Edge switch limitations shared area ports device load balancing trunking setup direct connections to target devices fabric loop devices not supported compatibility login balancing considerations inband queries long distance mode, Edge switch...
  • Page 106 persisting port online state policies advance device security N_Port enabling DCC policy configurations enforcement matrix description port grouping displaying configurations showing current policies failover in a PG using policyshow command mapping example port masterless trunking comparison maximum number supported mapping multiple trunk groups requirements trunk groups...
  • Page 107 unlock N_Port firmware downgrade upgrading ingress rate limiting SID/DID traffic prioritization VMware configuration for device mapping removing devices from switch removing trunk ports requirements, ports zoning schemes setting settings FLOGI inband queries management server platform zone, no access static vs. dynamic mapping supported hardware and software switch mode, verify terms...
  • Page 108 Access Gateway Administrator’s Guide 53-1002743-01...

This manual is also suitable for:

Access gateway

Table of Contents