Brocade Communications Systems 53-1003126-02 manual

53-1003126-02 15 August 2014 Access Gateway Administrator's Guide Supporting Fabric OS v7.3.0[...]

© 2014, Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks of Brocade Communications[...]

Contents Preface..................................................................................................................................... 7 Document conventions...................................................................................... 7 Text formatting conventions..............................................................[...]

Access Gateway policies overview............................................................... 51 Displaying current policies ............................................................... 51 Access Gateway policy enforcement matrix .................................... 51 Advanced Device Security policy ...........................................[...]

Disabling F_Port trunking.................................................................... 78 Monitoring trunking ............................................................................. 78 AG trunking considerations for the Edge switch................................. 78 Trunking considerations for Access Gateway mode......................[...]

6 Access Gateway Administrator's Guide 53-1003126-02[...]

Preface ● Document conventions...................................................................................................... 7 ● Brocade resources............................................................................................................ 9 ● Contacting Brocade Technical Support.........................................[...]

Convention Description value In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, for example, --show WWN. [ ] Syntax components displayed within square brackets are optional. Default responses to system prompts are enclosed in square brackets. { x | y | z } A choice of required parameters is encl[...]

Brocade resources Visit the Brocade website to locate related documentation for your product and additional Brocade resources. You can download additional publications supporting your product at www.brocade.com . Select the Brocade Products tab to locate your product, then click the Brocade product name or image to open the individual product page.[...]

• Brocade Supplemental Support augments your existing OEM support contract, providing direct access to Brocade expertise. For more information, contact Brocade or your OEM. • For questions regarding service levels and response times, contact your OEM/Solution Provider. Document feedback To send feedback and report errors in the documentation yo[...]

About This Document ● Supported hardware and software.................................................................................. 11 ● What’s new in this document.......................................................................................... 11 ● Key terms for Access Gateway..................................................[...]

Changes made for Fabric OS 7.3.0a The following content is new or significantly revised from 53-1003126-01 for this release of this document: • Updated Key terms for Access Gateway on page 12. Key terms for Access Gateway For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at: http://www.snia[...]

NPIV N_Port ID Virtualization. This is a Fibre Channel facility allowing multiple N_Port IDs to share a single physical N_Port. This allows multiple Fibre Channel initiators to occupy a single physical port, easing hardware requirements in storage area network design, especially for virtual SANs. Port Grouping (PG) policy Port Grouping (PG) policy [...]

Key terms for Access Gateway 14 Access Gateway Administrator's Guide 53-1003126-02[...]

Access Gateway Basic Concepts ● Brocade Access Gateway overview ............................................................................... 15 ● Fabric OS features in Access Gateway mode................................................................ 17 ● Access Gateway port types...........................................................[...]

FIGURE 1 Switch function in Native mode Access Gateway Basic Concepts 16 Access Gateway Administrator's Guide 53-1003126-02[...]

FIGURE 2 Switch function in Access Gateway mode Fabric OS features in Access Gateway mode In the table below, "Yes" indicates that the feature is supported in Access Gateway mode. "No" indicates that the feature is not provided in AG mode. "NA" indicates the feature is not applicable in Access Gateway mode. A single as[...]

Fabric OS components supported on Access Gateway (Continued) TABLE 1 Feature Support Admin Domains No Audit Yes Beaconing Yes Bottleneck Detection Yes Buffer Credit Recovery (CR) Yes - Refer to Buffer credit recovery support on page 20 . Config Download/Upload Yes Device Authentication Yes Refer to Device authentication support on page 21. DHCP Yes[...]

Fabric OS components supported on Access Gateway (Continued) TABLE 1 Feature Support FICON (includes CUP) No Forward Error Correction (FEC) Yes Refer to Forward error correction support on page 20. High Availability Yes Hot Code Load Yes License Yes** Lightweight Directory Access Protocol (LDAP) Yes Log Tracking Yes Management Server NA Manufacturi[...]

Fabric OS components supported on Access Gateway (Continued) TABLE 1 Feature Support Syslog Daemon Yes Track Changes Yes Trunking Yes** User-Defined Roles Yes Value Line Options (Static POD, DPOD) Yes Virtual Fabrics No Refer to Virtual Fabrics support on page 21 . Web Tools Yes Zoning NA Buffer credit recovery support This Fabric OS feature is sup[...]

• A Fabric OS downgrade requires FEC to be disabled. • Specific switch platforms support this feature either in R_RDY or VC_RDY mode. Virtual Fabrics support Although you cannot enable AG mode on a switch enabled for Virtual Fabrics or enable Virtual Fabrics on an AG switch, you can connect ports on an AG switch to Virtual Fabrics. Device authe[...]

To perform authentication with switch policy, the on and off policy modes are supported on the AG switch. To perform authentication with device policy, the on, off, and passive modes are supported on the AG switch. Behavior of sending AG switch and receiving fabric switch with different policies configured TABLE 2 Fabric switch with device policy m[...]

For more information, refer to the Fabric OS Command Reference . Limitations and considerations • Authentication policy is not supported on cascaded AG switch configurations. • 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 [...]

• VF mode distribution is not applicable to an AG. • The distribute command is not supported in AG mode. Hence, an AG cannot distribute its password database to any of the switches in native mode. FDMI support Starting with Fabric OS 7.3.0, AG can register its N_Port with FDMI devices, and the fdmishow command is supported to display the device[...]

FIGURE 3 Port usage comparison You can convert a Fibre Channel port into a D_Port on AG switch and a connected fabric switch, another AG switch (cascaded configuration), or an HBA 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 [...]

FIGURE 4 Diagnostic port configurations The table below shows a comparison of port configurations between AG and a standard fabric switch. Port configurations TABLE 4 Port type Available on Access Gateway? Available on Fabric switch? F_Port Yes Connects hosts and targets to Access Gateway. Yes Connects devices, such as hosts, HBAs, and storage to t[...]

Configuring Ports in Access Gateway Mode ● Enabling and disabling Access Gateway mode.............................................................. 27 ● Access Gateway mapping............................................................................................... 29 ● N_Port configurations...............................................[...]

9. Enter the switchShow command to display the status and port state of all ports. Refer to the Fabric OS Command Reference for examples of output. For a description of the port state, refer to Table 5 on page 28. When you disable AG mode, the switch automatically reboots and comes back online using the fabric switch configuration; the AG parameter[...]

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. This is unlike Native switch mode where the switch itself determines the best path between its F_Ports. This process o[...]

FIGURE 5 Port mapping example The following table describes the port mapping details for the above example. Description of port mapping TABLE 6 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 Default port mapping When you first enable [...]

NOTE Prior to Fabric OS 7.3.0, all POD licenses must be present to use the Brocade 300, 5100, 6505, and 6510 as an Access Gateway. However, Fabric OS 7.3.0 does not require all POD licenses to run in AG mode. Access Gateway default port mapping TABLE 7 Brocade Model Total Ports F_Ports N_Ports Default port mapping VA-40FC 40 0–31 32–39 0–3 ma[...]

Access Gateway default port mapping (Continued) TABLE 7 Brocade Model Total Ports F_Ports N_Ports Default port mapping M5424 24 1–16 0, 17–23 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 11, 12 mapped to 22 13, 14 mapped to 23 15, 16 mapped to 0 5430 16 1–10 0, 11–15 10 mapped to 0 1, 5 mapped t[...]

Access Gateway default port mapping (Continued) TABLE 7 Brocade Model Total Ports F_Ports N_Ports Default port mapping 5460 26 6–25 0–5 6, 16 mapped to 0 7, 17 mapped to 1 8, 12, 18, and 22 mapped to 2 9, 13, 19, and 23 mapped to 3 10, 14, 20, and 24 mapped to 4 11, 15, 21, and 25 mapped to 5 5470 20 1–14 0, 15–19 1, 2 mapped to 0 3, 4 mapp[...]

Access Gateway default port mapping (Continued) TABLE 7 Brocade Model Total Ports F_Ports N_Ports Default port mapping M6505 24 1–16 0, 17–23 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 11, 12 mapped to 22 13, 14 mapped to 23 15, 16 mapped to 0 6510 48 0–39 40–47 0-4 mapped to 40 5–9 mapped t[...]

Access Gateway default port mapping (Continued) TABLE 7 Brocade Model Total Ports F_Ports N_Ports Default port mapping 6548 28 1–16 0, 17–27 1, 13 mapped to 0 2, 14 mapped to 17 3, 15 mapped to 18 4, 16 mapped to 19 5 mapped to 20 6 mapped to 21 7 mapped to 22 8 mapped to 23 9 mapped to 24 10 mapped to 25 11 mapped to 26 12 mapped to 27 Conside[...]

The F_Port list can contain multiple F_Port numbers separated by semicolons. In the following example, F_Ports 6 and 7 are mapped to N_Port 13. switch:admin> ag --mapadd 13 "6;7" F-Port to N-Port mapping has been updated successfully 3. Enter the ag --mapshow command and specify the port number to display the list of mapped F_Ports. Ve[...]

Considerations for using F_Port Static Mapping with other AG features and policies Consider the following when using F_Port Static Mapping with Access Gateway features and policies: • F_Port Static Mapping functions with cascaded Access Gateway configurations. • Failover, failback, and preferred secondary N_Port settings are disabled for F_Port[...]

• Logins from a device mapped to a specific N_Port or N_Port group (device mapping) always have priority over unmapped devices that log in to an F_Port that has been mapped to the same N_Port or N_Port group (port mapping). • Current device routing (dynamic mapping) may turn out different than your intended mapping (static mapping), depending o[...]

FIGURE 6 Example of device mapping to N_Port groups The figure below 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. Configuring Ports in Access Gateway Mode Access Gateway Administrator's Guide 39 53-1003126-02[...]

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: Static versus dynamic mapping 40 Access Gateway Administrator's Guide 53-1003126-02[...]

• 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. • Automatic Device Load Balancing, if enabled, is considered dynamic. These mappings exist only while a device is logged in. Dynamic mappings c[...]

The following example removes all devices mapped to port group 3. ag --delwwnpgmapping 3 --all 6. Enter the ag --wwnmapshow command to display the list of WWNs mapped to port groups and verify that the correct devices have been mapped to the desired port group. Device mapping to N_Ports Use the following steps to add one or more devices to an N_Por[...]

The following example disables device mapping for two WWNs. switch:admin> ag --wwnmappingdisable "10:00:00:06:2b:0f:71:0c; 10:00:00:05:1e:5e: 2c:11" 3. Enter the ag--wwnmappingdisable command with the --all option to disable mapping for all available WWNs. The --all option will not affect mappings made in the future. Disabled mappings [...]

error. This also applies to using Fabric OS commands for device mapping. You could also map several devices to a new port group and then create the group without error. You can also remove one device, and then remove another device without error. VMware configuration considerations Enabling device mapping for individual virtual machines (VMs) runni[...]

Mapping priority To avoid potential problems when both port and device mapping are implemented, AG uses the following priority system when verifying policies to select the N_Port where a fabric login (FLOGI) is routed. Access Gateway considers all available mappings in the following order until one can be used. NOTE Only NPIV devices can use device[...]

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. Although some ports are loc[...]

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, al[...]

D_Port support The Diagnostic (D_Port) feature is supported on 16-Gbps ports in the following configurations: • An AG switch connected to an AG switch in cascaded configuration (supports only static D_Port). • An AG switch connected to a Brocade fabric switch (supports only static D_Port). • An AG switch connected to a Brocade HBA (supports s[...]

• D__Port must be configured on the AG, fabric switch, cascaded AG switch, or HBA before enabling D_Ports on both sides of the link. Otherwise, the port will be persistently disabled. • After configuring D_Port for an AG switch port, mapping will be not be retained. Static D_Port configuration cannot be made unless mappings are removed from the[...]

Saving port mappings 50 Access Gateway Administrator's Guide 53-1003126-02[...]

Managing Policies and Features in Access Gateway Mode ● Access Gateway policies overview................................................................................. 51 ● Advanced Device Security policy ................................................................................... 52 ● Automatic Port Configuration policy ............[...]

Policy enforcement matrix (Continued) TABLE 8 Policies Auto Port Configuration N_Port Grouping N_Port Trunking Advanced Device Security N_Port Grouping Mutually exclusive N/A Yes Yes N_Port Trunking Yes Yes N/A Yes Advanced Device Security Yes Yes Yes N/A Device Load Balancing No Yes Yes Yes Advanced Device Security policy Advanced Device Security [...]

1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag --policyenable ads command to enable the ADS policy. switch:admin> ag --policyenable ads The policy ADS is enabled 3. Enter the ag - - policydisable ads command to disable the ADS policy. switch:admin> ag --policydisable ads The policy ADS is disa[...]

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. In the following example, ports 11 and 12 are set to "no access." switch:admin [...]

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. Enter the ag --adsshow command. For each F_Port, command output will show access for all devices, a list of device WWNs, or no access. For more details on this command and its output, refer to the Fabric OS Comman[...]

3. Enter the configUpload command to save the switch’s current configuration. 4. Enter the ag --policydisable pg command to disable the Port Grouping (PG) policy. 5. Enter the ag --policyenable auto command to enable the APC policy. 6. At the command prompt, type Y to enable the policy. The switch is ready; a reboot is not required. Disabling the[...]

How port groups work Create port groups using the ag --pgcreate command. This command groups N_Ports together as "port groups." By default, any F_Ports mapped to the N_Ports belonging to a port group will become members of that port group. Port grouping fundamentally restricts failover of F_Ports to the N_Ports that belong to that group. [...]

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. Enter the ag --pgadd command with the appropriate options to add an N_Port to a specific port group. In the following example, N_Port 14 is added to port group 3. Note that if you add more than one [...]

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> ag --pgrename 2 MyEvenFabric Port Group 2 has been renamed as MyEvenFabric [...]

other than 120 seconds using the steps under Setting the current MFNM mode timeout value on page 61. Creating a port group and enabling Automatic Login Balancing mode 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag --pgcreate command with the appropriate options to create a port group. In the followi[...]

• Be aware that modifying Automatic Login Balancing mode default settings using the agautomapbalance command may yield uneven distribution of F_Ports to N_Ports. In such cases, you might consider a manual login distribution that forces a rebalancing of F_Ports to N_Ports. • To control automatic rebalancing to avoid disruptions when the Port Gro[...]

• APC policy and PG policy are mutually exclusive. You cannot enable these policies at the same time. • If an N_Port is added to a port group or deleted from a port group and Automatic Login Balancing mode is enabled or disabled for the port group, the N_Port maintains its original failover or failback setting. If an N_Port is deleted from a po[...]

3. The Port Grouping policy must be enabled to enable Device Load Balancing. Enter the ag -- policyshow command to determine if the Port Grouping policy is enabled. If it is not enabled, enter ag --policyenable pg to enable this policy. 4. Enter the ag --policyenable wwnloadbalance command to enable the Device Load Balancing policy. Because Fibre C[...]

• In "Flexible" mode, the AG logs an event that it did not receive the same (requested) ALPA from the core fabric and brings up the device with the ALPA assigned by the fabric. • In the "Stringent" mode, if the requested ALPA is not available, the server login will be rejected and the server port cannot log in to the fabric.[...]

In the example, PWWN is the port that you want to remove from the database. Displaying device data You can view the ALPA of the host related to any ports you delete from the database. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag --printalpamap command with the appropriate option to display a datab[...]

N_Port goes offline. This occurs regardless of whether the Failover policy is enabled or disabled for the primary N_Port. Failover with port mapping The Failover policy allows F_Ports to automatically remap to an online N_Port if the primary N_Port goes offline. If multiple N_Ports are available for failover, the Failover policy evenly distributes [...]

FIGURE 11 Failover behavior Managing Policies and Features in Access Gateway Mode Access Gateway Administrator's Guide 67 53-1003126-02[...]

Managing Policies and Features in Access Gateway Mode 68 Access Gateway Administrator's Guide 53-1003126-02[...]

Adding a preferred secondary N_Port (optional) F_Ports automatically fail over to any available N_Port. Alternatively, you can specify a preferred secondary N_Port in case the primary N_Port fails. If the primary N_Port goes offline, the F_Ports fail over to the preferred secondary N_Port (if it is online), then re-enable. If the secondary N_Port i[...]

Adding a preferred secondary N_Port for device mapping (optional) Use the following steps to configure 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. To configure an N_Port as a failover port for one or mu[...]

3. Enter the ag --failoverenable N_Port command to enable failover. switch:admin> ag --failoverenable 13 Failover policy is enabled for port 13 4. Enter the ag --failoverdisable N_Port command to disable failover. switch:admin> ag --failoverdisable 13 Failover policy is disabled for port 13 Enabling and disabling the Failover policy for a por[...]

Failback policy configurations in Access Gateway The following sequence describes how a failback event occurs: • When an N_Port comes back online, with the Failback policy enabled, the F_Ports that were originally mapped to it are temporarily disabled. • The F_Port is rerouted to the primary mapped N_Port, and then re-enabled. • The host esta[...]

FIGURE 12 Failback behavior Enabling and disabling the Failback policy on an N_Port Use the following steps to enable or disable the Failback policy on N_Ports. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag --failbackshow n_portnumber command to display the failback setting. switch:admin> ag --f[...]

• Enter the ag --failbackenable n_portnumber command to enable failback. switch:admin> ag --failbackenable 13 Failback policy is enabled for port 13 • Enter the ag --failbackdisable n_portnumber command to disable failback. switch:admin> ag --failbackdisable 13 Failback policy is disabled for port 13 Enabling and disabling the Failback po[...]

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 simplifyi[...]

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[...]

You can remove specified ports from a TA using the porttrunkarea --disable command, however, this command does not unassign a TA if its previously assigned Area_ID is the same address identifier (Area_ID) of the TA unless all the ports in the trunk group are specified to be unassigned. For more information on the porttrunkarea command, enter help p[...]

command forms a trunk group for ports 36-39 with index 37. These will be connected to N_Ports on an AG module. switch:admin> porttrunkarea --enable 36-39 -index 37 Trunk area 37 enabled for ports 36, 37, 38 and 39. 4. Enter the portenable port command for each port in the TA to re-enable the desired ports, such as ports 36-39. 5. Enter the switc[...]

Access Gateway trunking considerations for the Edge switch (Continued) TABLE 10 Category Description Management Server Registered Node ID (RNID), Link Incident Record Registration (LIRR), and Query Security Attributes (QSA) Extended Link Service Requests (ELSs) are not supported on F_Port trunks. Trunk area The port must be disabled before assignin[...]

Access Gateway trunking considerations for the Edge switch (Continued) TABLE 10 Category Description FC8-48 blades F_Port trunking does not support shared area ports on the Brocade FC8-48 blades in a 48000. F_Port trunking is supported on all ports on the Brocade FC8-48 in the DCX and DCX-4S. FC4-32 blade If an FC4-32 blade has the Trunk Area enabl[...]

Access Gateway trunking considerations for the Edge switch (Continued) TABLE 10 Category Description D,I Zoning (D,I) AD (D, I) DCC and (PWWN, I) DCC Creating a Trunk Area may remove the Index ("I") from the switch to be grouped to the Trunk Area. All ports in a Trunk Area share the same "I". This means that Domain,Index (D,I), [...]

Adaptive Networking on Access Gateway Adaptive Networking (AN) services ensure bandwidth for critical servers, virtual servers, or applications in addition to reducing latency and minimizing congestion. Adaptive Networking in Access Gateway works in conjunction with the Quality of Service (QoS) feature on Brocade fabrics. Fabric OS provides a mecha[...]

FIGURE 13 Starting point for QoS Upgrade and downgrade considerations for Adaptive Networking in AG mode Upgrading to Fabric OS v7.1.0 from Fabric OS v6.4.0 is supported. Note the following considerations when upgrading to Fabric OS v7.1.0 from Fabric OS v6.2.X and earlier and downgrading from Fabric OS v7.1.0 to Fabric OS v6.2.X and earlier: • I[...]

• QoS takes precedence over ingress rate limiting • Ingress rate limiting is not enforced on trunked ports. Per-Port NPIV login limit The Per-Port NPIV login limit feature allows you to set a specific maximum NPIV login limit on individual ports. This feature works in both Native and Access Gateway modes. Using this feature, you can use additio[...]

device logged in. The first login takes precedence over the second login request in case of a duplicate entry exit on the F_Port without any NPIV device logged in. You can configure different handling of duplicate PWWNs other than the default operation using the configure command through the F_Port login parameters. For more information on configur[...]

Legacy performance monitoring features Instead of Flow Monitor, you can use the legacy end-to-end and frame monitoring features available through Advanced Performance Monitoring (APM). These legacy features are available on platforms using Fabric OS 7.2 and earlier. The following licenses must be appropriately installed on the AG switch to use the [...]

frame type, for a particular purpose. The frame type can be a standard type (for example, an SCSI read command filter that counts the number of SCSI read commands that have been transmitted by the port) or a frame type that you can customize for a particular use. For a complete list of the standard, pre- defined frame types, see the fmMonitor comma[...]

Considerations for the Brocade 6505 and 6510 The Brocade 6505 and 6510 can function in either Fabric OS Native mode or Brocade Access Gateway mode. These switches are shipped in Fabric OS Native mode. They are also supported in Access Gateway cascaded configurations. All POD licenses must be present to support Access Gateway for all releases prior [...]

SAN Configuration with Access Gateway ● Connectivity of multiple devices overview....................................................................... 89 ● Direct target attachment.................................................................................................. 89 ● Target aggregation........................................[...]

FIGURE 14 Direct target attachment to switch operating in AG mode Although target devices can be connected directly to AG ports, it is recommended that the switch operating in AG mode be connected to the core fabric. Considerations for direct target attachment Consider the following points for direct target attachment: • Direct target attachment [...]

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 the figure below. Target aggregation has many applications. As one exampl[...]

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. [...]

• 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. • Starting with Fabric OS 7.3.0 and later, the registration and de-registration of FDMI devices connected to an AG or casca[...]

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. Connect to the switch and log in as admin on the M-EOS switch. 2. Enable Open Systems Management Server (OSMS) services by entering the following commands. For the Mi10K switch, enter the [...]

Rejoining Fabric OS switches to a fabric When a switch reboots after 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 rejoin a switch to the fabric: • If you saved a Fabric OS configuration before enabling AG mode, do[...]

Reverting to a previous configuration 96 Access Gateway Administrator's Guide 53-1003126-02[...]

Troubleshooting The following table provides troubleshooting information for Fabric OS switches in AG mode. Troubleshooting TABLE 12 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[...]

Troubleshooting (Continued) TABLE 12 Problem Cause Solution Failover is not working Failover disabled on N_Port. Verify that the failover and failback policies are enabled, as follows: Enter the ag --failoverShow command with the port_number option. Enter the ag --failbackShow command with the port_number option. Command returns "Failback (or [...]

Index A Access Gateway cascading 92 comparison to standard switches 24 compatible fabrics 15 connecting devices 89 connecting two AGs 92 description 15 displaying information 94 features 17 limitations 26 mapping description 29 port types 24 Access Gateway mode comparison 15 disabling 27 port types 24 supported firmware versions 89 terms 12 verifyi[...]

enabling switch 95 limitations with configdownload command 78 merging switch with fabric 95 re-joining switch to fabric 95 saving 95 using configdownload command 95 D D_Port description 24 descriptionD_Port configurations supported 48 saving port mappings 49 tests 48 daisy chaining 89 DCC policy adding WWN 77 enabling 77 limitation creating TA 78 d[...]

I ICL ports, limitations 78 inband queries 93 initiator and target port considerations 35 J join fabric 95 L limitations device load balancing 63 direct connections to target devices 26 loop devices not supported 26 login balancing considerations 60 long distance mode, Edge switch 93 M managed fabric name monitoring disabling 61 displaying current [...]

comparison 24 mapping 29 requirements 89 types 24 portcfgpersistentenable command 47 port group add N_Port 58 createport group add N_Port 60 delete N_Port 58 disabling 59 enabling logging balancing mode 60 login balancing mode 59 managed fabric name monitoring mode 59 remove port group 58 rename 59 port grouping policy considerations 61 downgrading[...]

schemes 93 setting 95 Access Gateway Administrator's Guide 103 53-1003126-02[...]

104 Access Gateway Administrator's Guide 53-1003126-02[...]