HP 1606 Access Gateway Administrator's Guide (53-1001760-01, June 2010)
HP 1606 Manual
View all HP 1606 manuals
Add to My Manuals
Save this manual to your list of manuals |
HP 1606 manual content summary:
- HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 1
53-1001760-01 ® 30 March 2010 Access Gateway Administrator's Guide Supporting Fabric OS v6.4.0 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 2
or service offered or to be offered by Brocade. Brocade license from the United States government. The authors and Brocade brocade.com/support/oscd. Brocade Communications Systems, Incorporated Corporate and Latin American Headquarters Brocade Communications Systems, Inc. 1745 Technology Drive San - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 3
-04 Access Gateway Administrator's Guide Access Gateway Administrator's Guide Access Gateway Administrator's Guide 53-1001189-01 53-1001345-01 53-1001760-01 Summary of Changes Publication Date First version January 2007 Added support for the 200E June 2007 Added support for new policies and - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 4
iv Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 5
of Access Gateway ports to standard switch ports. 4 Access Gateway hardware considerations 5 Chapter 2 Configuring Ports in Access Gateway mode In this chapter 7 Enabling and disabling Access Gateway mode 7 Port state description 9 Access Gateway mapping 10 Port-based mapping 10 Device - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 6
policy considerations 39 Upgrade and downgrade considerations for the Port Grouping policy 40 Device Load Balancing Policy 40 Enabling WWN Load Balancing 40 Disabling Device Load Balancing 40 Device Load Balancing considerations 41 vi Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 7
on Access Gateway 58 Upgrade and downgrade considerations with Adaptive Networking in AG mode enabled 59 Adaptive Networking on Access Gateway considerations . . . . . 59 Per Port NPIV login limit 60 Setting the login limit 60 Considerations for the Brocade 8000 60 SAN Configuration with Access - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 8
65 Verifying the switch mode 65 Enabling NPIV on M-EOS switches 66 Connectivity to Cisco Fabrics 67 Enabling NPIV on a Cisco switch 67 Rejoining Fabric OS switches to a fabric 67 Reverting to a previous configuration 67 Troubleshooting viii Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 9
in Access Gateway mode 2 Port usage comparison 5 Example port-based mapping 11 Example of device mapping to N_Port groups 17 Example device mapping to an N_Port 18 Example of adding an external F_Port (F9) on an embedded switch 24 Port grouping behavior 34 Port group 1 (pg1) setup 34 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 10
x Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 11
Description of port mapping 11 Access Gateway default port mapping 12 Policy enforcement matrix 28 Address identifier 52 Access Gateway trunking considerations for the Edge switch 54 PWWN format for F_Port and N_Port trunk ports 57 Troubleshooting 69 Access Gateway Administrator's Guide xi - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 12
xii Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 13
" provides symptoms and troubleshooting tips to resolve issues. 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 exactly which switches are supported and which are not - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 14
Cisco switches with SAN OS must be running 3.0 (1) and 3.1 (1) or later. Fabric OS v6.4.0 supports the following Brocade hardware platforms for Access Gateway: • Brocade 300 • Brocade 5100 • Brocade M5424 • Brocade 5450 • Brocade 5460 • Brocade 5470 • Brocade 5480 • Brocade VA40-FC • Brocade 8000 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 15
the narrative portions of this guide are presented in mixed lettercase: for example, switchShow. In actual examples, command lettercase is often all lowercase. Command syntax conventions Command syntax in this manual follows these conventions: command --option, option -argument, arg [ ] variable - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 16
to you or cause damage to hardware, firmware, software, or data. DANGER A Danger Brocade and Fibre Channel, see the Brocade Glossary. The following terms are used in this manual to describe Access Gateway mode and its components. Access Gateway (AG) Fabric OS mode for switches that reduces SAN - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 17
user ID and password. For additional Brocade documentation, visit the Brocade SAN Info Center and click the Resource Library location: http://www.brocade.com Release notes are available on the My Brocade website (http://my.brocade.com) and are also bundled with the Fabric OS firmware. Other industry - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 18
: http://www.fibrechannel.org Optional Brocade features For a list of optional Brocade features and descriptions, see the Fabric OS Administrator's Guide. Getting technical help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 19
command because the switch is inoperable, you can get the WWN from the same place as the serial number, except for the Brocade DCX. For the Brocade DCX, access the numbers on the WWN cards by removing the Brocade at Brocade and we your feedback to: [email protected] Provide the title and - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 20
xx Access Gateway Administrator's Guide 553-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 21
3 •Access Gateway port types 4 •Access Gateway hardware considerations 5 Brocade Access Gateway overview Brocade Access Gateway (AG) -based fabrics v3.0 (1) or later and v3.1 (1) and later. Enabling and disabling AG mode and configuring AG features on a switch can be performed from the command - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 22
1 Brocade Access Gateway overview FIGURE 1 Switch function in Native mode FIGURE 2 Switch function in Access Gateway mode 2 Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 23
components that are supported on a switch when AG mode is enabled. "No" indicates Brocade fabric, the feature may not be available. TABLE 1 Feature Fabric OS components supported on Access Gateway Support Interoperability Mode License Hot Code only, no APM support) Yes Port Mirroring QuickLoop, - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 24
, time should be updated by the server management utility. 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 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 25
platforms and embedded switch platforms listed in "Supported hardware and software" on page xiii. • Loop devices are not supported. • Direct connections to SAN target devices are only supported if the AG-enabled module is connected to a fabric. Access Gateway Administrator's Guide 5 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 26
1 Access Gateway hardware considerations 6 Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 27
mode using a factory default port mapping. For more information on AG default port mapping, see Table 5 on page 12. 6. Enter the ag --modeshow command to verify that AG mode is enabled. switch:admin> ag --modeshow Access Gateway mode is enabled. Access Gateway Administrator's Guide 7 53-1001760 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 28
on Access Gateway. 7. Enter the ag --mapshow command to display all the mapped ports. The ag --mapshow command shows all the N_Ports (with the portcfgnport value of 1) even if those N_Ports are not connected. switch:admin> ag --mapshow N_Port Configured_F_Ports Current_F_Ports Failover Failback - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 29
> ag --modedisable 11. Enter the ag --modeshow command to verify that AG mode is disabled. switch:admin> ag --modeshow Access Gateway mode is NOT enabled Port state description The following table describes the possible port states. TABLE 3 Port state description State Description No _Card No - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 30
port maps. Port mapping must exist at all times. Port-based mapping An F_Port needs to be mapped to an N_Port before the F_Port can come online. When you first enable a switch to AG mode, by default, the F_Ports are mapped to a set of predefined N_Ports. For default port mapping on supported - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 31
F_4 N_3 F_5 N_4 F_6 Edge Switch (Switch_A) F_A1 NPIV enabled F_A2 NPIV enabled Edge Switch (Switch_B) F_B1 NPIV enabled F_B2 NPIV enabled Fabric Host_7 F_7 Host_8 F_8 FIGURE 4 Example port-based mapping Table 4 provides a description of the port mapping in Figure 4. TABLE 4 Description of - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 32
policies are enabled on all N_Ports. NOTE All POD licenses must be present to use Access Gateway on the Brocade 5100 and 300. .TABLE 5 Brocade Model VA40-FC Access Gateway default port mapping Total Ports F_Ports N_Ports 40 0-31 32-39 300 24 0-15 16 -23 Default Port Mapping 0-3 mapped - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 33
Brocade Model 5100 Access Gateway default port mapping (Continued) Total Ports F_Ports N_Ports 40 0-31 32-39 5424 24 1-16 0, 17-23 5450 26 6-25 0, 19-25 Not all ports may be present. Default Port 11, 12 mapped to 24 13, 14 mapped to to 3 10, 14, 20, and 24 mapped to 4 11, 15, 21, - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 34
2 Access Gateway mapping TABLE 5 Brocade Model 5480 Access Gateway default port mapping (Continued) Total Ports F_Ports N_Ports 24 1-16 0, 17-23 8000 32 8-31 0-7 FCoE ports mapped as F_Ports. Default Port Mapping 1, 2 mapped to 17 9, 10 mapped to 18 3, 4 mapped to 19 11, 12 mapped to - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 35
page 46 for instructions. 3. Enter the ag --mapdel N_Port command with the "[fprot;[fport]" option to remove the F_Port from the N_Port. The f_portlist can contain multiple F_Port numbers separated by semicolons, for example "17;18". switch:admin> ag --mapdel 17;18 F-Port to N-Port mapping has been - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 36
mapping NOTE Port Grouping Policy is not supported when both Automatic Login Balancing and Device Load Balancing are enabled. Device-based mapping does not affect or replace the traditional port mapping. Device mapping is an optional mapping that will exist on top of existing port mapping. In - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 37
. 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 17 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 38
and restored with Fabric OS configUpload and configDownload commands. • Automatic WWN load balancing, if enabled, is considered dynamic. These mappings exist only more information on port groups, refer to "Port Grouping policy" on page 33. 18 Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 39
group. 1. Connect to the switch and log in using an port group 3. ag --delwwnpgmapping 3 --all 4. 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. Access Gateway Administrator's Guide - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 40
command with the --all option. The following command changes all the existing device mappings to use port enable this at a later time without reconfiguring your original mapping. To enable disabled mapping, refer to "Enabling device mapping" on page 21. 1. Connect to the switch Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 41
, that is one who's mapping is not disabled, will be enabled by default. Disabled mappings can be modified with out automatically enabling them. The following command enables all previously disabled device mappings. switch:admin> ag --wwnmappingenable --all Display device mapping information Use the - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 42
using Fabric OS commands for device mapping. You could map several devices to a new port group then create 3.5 at following link: http://www.brocade.com/downloads/documents/brocade_vmware_technical_briefs/Brocade_NP IV_ESX3. avoid potential problems when both port-based and device-based mapping are - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 43
failover policy, the devices will be enabled on other N_Ports. • Similar to Port-based mappings, device-based mappings are affected by changes to underlying to further reduce this condition. • Device mapping is not supported when firmware is downgraded to Fabric OS 6.3.x or lower. You must - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 44
2 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 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 45
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 (inter switch link) ports. By default, on fabric switches the port types are not locked. Fabric OS Native mode dynamically assigns the port type based - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 46
2 N_Port configurations 26 Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 47
policies are enabled. switch:admin> ag --policyshow Policy_Description Policy_Name State Port Grouping pg Enabled Auto Port Configuration auto Disabled Advanced Device Security ads Enabled WWN Based Load Balancing wwnloadbalance Disabled Access Gateway Administrator's Guide 27 53 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 48
supported when using Device mapping. 2. Device Load Balancing and Automatic Login Balancing cannot be enabled for the same port SAN. How the ADS policy works When you enable this policy, it applies to all F_Ports on the AG-enabled module. By default, all devices have access to the fabric on all ports - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 49
3 Enabling and disabling the Advanced Device Security 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 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 50
the specified WWNs from all the F_Ports' allow lists. The ADS policy must be enabled for this command to succeed. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag --adsdel command to remove one or more devices from the list of allowed devices. Use the - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 51
the AG module that directly connects to the servers. • ADS policy can be enabled or disabled independent of status of other AG policies. • The ADS policy is not currently supported with device-based mapping. Upgrade and downgrade considerations for the ADS policy Downgrading to Fabric OS v6.3.0 or - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 52
[no] y Access Gateway configuration has been restored to factory default 6. Enter the switchenable command to enable the switch. Automatic Port Configuration policy considerations Following are the considerations for the Automatic Port Configuration policy: • The APC and the PG policies cannot be - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 53
and the port-based mapping revert back to the default factory configurations for that platform. It is recommended that before you either disable or enable APC policy to save the current configuration file using the configupload command in case you might need this configuration again. Upgrade and - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 54
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 N_Ports, you must separate them with a semicolon. switch:admin> ag --pgadd 3 14 N_Port[s] are added to the port group 3 34 Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 55
policy The Port Grouping (PG) policy is enabled by default for Access Gateway. To disable this policy, use the following steps. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ag --policydisable command. switch:admin> ag --policydisable pg. Access - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 56
default and managed mode, the system queries the fabric name once every 120 seconds to detect inconsistencies such as a port command is blocked on a Brocade 8000 during and after creation of a port group. Creating a port group and enabling Automatic Login Balancing mode 1. Connect to the switch - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 57
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 Disabled 1 Disabled - - This command also displays the automatic login redistribution settings for N_Ports and - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 58
admin role. 2. Enter the ag --pgsetmodes command with appropriate operands to enable MFNM mode. In the following example, MFNM mode is enabled for port group 3. switch:admin> ag --pgsetmodes 3 "mfnm" Managed Fabric Name Monitoring mode has been enabled for Port Group 3 Disabling Managed Fabric Name - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 59
value to 100 seconds. NOTE The pgfnmtov command is blocked on a Brocade 8000. Port Grouping policy considerations Following are the considerations for the Port Grouping policy: • A port cannot be a member of more than one port group. • The PG policy is enabled by default in Fabric OS 6.0 and higher - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 60
the configuration file using the configupload command in case you might need this configuration again. • If you upgrade from Fabric OS 5.3.0 to 6.0 or higher, you will not see any change in device behavior where the Port Grouping policy is enabled by default. Device Load Balancing Policy When Device - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 61
. • This policy is not supported on the Brocade 8000 switch for Fabric OS v6.4.0. This is because MFNM is enabled on the default port group and any created port groups on the Brocade 8000. As a result, the pgsetmodes, pgdelmodes, and pgcreate commands are blocked for the -m option, and Automatic - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 62
switch and log in using an account assigned to the admin role. 2. Enter the ag --persistentalpaenable command to enable persistent ALPA in flexible or stringent mode. switch can remove some of the entries to make space using instructions under "Removing device data from the database" next. Removing - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 63
ports of 48-port Director blades • CISCO fabrics. Enable Persistent FCID mode on the connecting Cisco switch to achieve the same functionality. • Persistent ALPA configuration will not change to the default when the configdefault command is used, but will retain the previous configuration. Upgrade - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 64
configured as an N_Port, failover is enabled by default and is enforced during power-up. Failover allows hosts and targets to automatically remap to another online N_Port if the primary N-Port goes offline. NOTE For port-based mapping, the Failover policy must be enabled on an N_Port for failover to - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 65
: switch:admin> ag --prefset "3;9" 4 Preferred N_Port is set successfully for the F_Port[s] NOTE Preferred mapping is not allowed when automatic login balancing mode is enabled for a port group. All N_Ports are the same when automatic login balancing is enabled. Access Gateway Administrator's Guide - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 66
Failover or Failback policies for N_Ports have no effect on device-based mapping. A device will always fail over to an online N_Port in the port group, regardless of whether Failback is enabled for an N_Port or not. Whereas, with port-based mapping, if you disable the Failover or Failback policy on - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 67
Failover on N_Port 13 is not supported 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 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 68
pgid command to disable failover. switch:admin> ag --failoverdisable -pg 3 Failover policy is disabled for port group 3 Upgrade and downgrade considerations for Failover Consider the following when upgrading or downgrading Fabric OS versions. • Downgrading to Fabric OS v6.3.0 or earlier is supported - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 69
13 Failback on N_Port 13 is not supported 3. Use the following commands to enable or disable Failback: • 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 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 70
switch:admin> ag --failbackdisable -pg 3 Failback policy is disabled for port group 3 Upgrade and downgrade considerations for Failback • Downgrading to Fabric OS v6.3.0 or earlier is supported. • Upgrading from Fabric OS v6.3.0 is supported. Trunking in Access Gateway mode Brocade's hardware-based - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 71
that both modules (Edge switch and the switch running in AG mode) have the trunking licenses enabled. 3. Ensure that the ports have trunking enabled by issuing the portcfgshow command. If Trunking is not enabled, issue the portcfgttrunkport port 1 command. 4. Ensure that ports within a trunk have - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 72
a Trunk Area. Use the portCfgTrunkPort or switchCfgTrunk command to enable trunking on a port or on all ports of a switch. Issue the porttrunkarea command to assign a static TA on a port or port trunk group, to remove a TA from a port or group of ports in a trunk, and to display masterless trunking - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 73
DCC policy on the trunk ports. 4. 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. Connect to the switch and log in using - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 74
that port displays the authentication details when you issue the portshow command. Management Server Note: Switches in Access Gateway mode do not perform authentication. Registered Node ID (RNID), Link Incident Record Registration (LIRR), and (QSA) Query Security Attributes ELSs are not supported - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 75
on those ports; if a port is fast write enabled, the port cannot be assigned a Trunk Area. FICON is not supported on F_Port trunk ports. However, FICON can still run on ports that are not F_Port trunked within the same switch. F_Port Trunking does not support shared area ports on the Brocade FC8-48 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 76
command to assign a Trunk Area on those ports. You must first enable Trunking on the port before the port can have a Trunk Area assigned to it. F_Port masterless trunking is only supported in CORE PID format. Long distance is not allowed when AG is enabled on a switch. This means you cannot enable - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 77
(1) Port WWNs for: switch's FX_Ports command to determine the devices using a particular trunk. Upgrade and downgrade considerations for Trunking in Access Gateway mode Upgrading and downgrading from Fabric OS v6.4.0 to Fabric OS v6.3.0 and earlier is supported. Access Gateway Administrator's Guide - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 78
must be installed to extend QoS features to supported HBAs. To determine if these licenses are installed on the connected switch, issue the Fabric OS licenseshow command. Refer to the Fabric OS Administrator's Guide for detailed information about QoS. You can configure the ingress rate limiting - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 79
on the edge switch also tries to come up as a master. To avoid this issue, simply persistently enable the slave F_Port on the switch. • QoS takes precedence over ingress rate limiting • Ingress rate limiting is not enforced on trunked ports. Access Gateway Administrator's Guide 59 53-1001760 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 80
reboots and firmware upgrades. • This feature supports virtual switches, so each port can have a specific NPIV login limit value in each logical switch. • The login limit default is 126. This value will be set for a port when the portCfgDefault command is used to reset port default values. • Before - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 81
Port Configuration Policy • Persistent ALPA • Device Load Balancing Fabric OS commands This section describes differences in using Fabric OS commands on the Brocade 8000 in AG mode. • The following commands are not supported on the Brocade Access Gateway Administrator's Guide 61 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 82
for Trunking due to the function of QoS. Automatic Login Balancing MFNM is enabled by default on all port groups and cannot be disabled on the Brocade 8000. Because of this, the pgsetmodes, pgdelmodes, and pgcreate commands are blocked for the -m option, and Automatic Login Balancing cannot be - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 83
with the following firmware versions: • M-EOSc v9.6.2 or later and M-EOSn v9.6 or later. • Cisco MDS Switches with SAN OS v3.0(1). • Loop devices and FICON channels/control unit connectivity are not supported. • When a switch is in AG mode, it can be connected to NPIV-enabled HBAs, or F_Ports - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 84
use cascading to further increase the ratio of hosts to fabric ports beyond what a single switch model in AG mode can support. Access Gateway cascading lets you connect two Access Gateway (AG) switches linking them back to back. The AG switch that is directly connected to the fabric is referred to - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 85
switch and the fabric is supported. • It is recommended that you enable Advanced Security Policy (ADS) on all AG F_Ports that are directly connected to devices. • APC policy is not supported when cascading. • Loopbacks (Core AG N_Port to Edge AG F_Port) are not allowed. • The agshow command issued - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 86
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. Connect to the switch and log in as admin on the M-EOS switch. 2. Enable the MS services by entering the following commands - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 87
1. Log in as admin on the Cisco MDS switch. 2. Enter the show version command to determine that you are using the correct SAN-OS version and to see if NPIV is enabled on the switch. 3. Enter the following commands to enable NPIV: conf t enable npiv 4. Press Ctrl-Z to exit. 5. Enter the following - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 88
4 Rejoining Fabric OS switches to a fabric The switch automatically joins the fabric. 68 Access Gateway Administrator's Guide 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 89
instructions. TABLE 10 Problem Troubleshooting Cause Solution Switch is not in Access Gateway mode NPIV disabled on Edge switch ports Need to reconfigure N_Port and F_Ports LUNs are not visible Switch is in Native switch mode Disable switch using the switchDisable command. Enable - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 90
TABLE 10 Problem Troubleshooting (Continued) 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 operand. Enter the ag --failbackShow command with the - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 91
31 enabling, 29 removing devices, 30 APC Policy disabling, 33 rebalancing F_Ports, 37 support for port groups, 36 area assignment, 54 authentication, limitations, 54 B behavior, failover policy, 49 Access Gateway Administrator's Guide 53-1001760-01 Brocade 8000 AG considerations, 60 default mapping - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 92
, 67 re-joining switch to fabric, 67 saving, 67 using configdownload command, 67 D daisy chaining, 63 DCC policy adding WWN, 53 enabling, 53 limitation creating TA, 56 default area, removing ports, 55 72 device load balancing, 36 device load balancing policy, 40 APC policy, 41 Brocade 8000, 41 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 93
mapping Brocade 8000 differences, 12 considerations, 22 default mapping for Brocade 8000, 12 device, 10 device to port groups, 18 devices to ports, 20 example, 11 port, 10 ports, 10 mapping priority, 10 masterless trunking, 56 M-EOS switch, enabling NPIV, 66 N N_Port configurations, 24 description - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 94
, 25 native switchMode, 66 non disruptive, 55 NPIV Edge switch, 65 enabling on Cisco switch, 67 enabling on M-EOS switch, 66 login limit, 60 support, 63 O optional features, xviii P per port NPIV login limit, 60 Persistent ALPA support, 41 persistent ALPA clearing ALPA values, 43 considerations, 43 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 95
, 51 considerations in AG module, 57 considerations on edge switch, 54 disabling, 54 enabling, 53, 56 license, 50 monitoring, 54 U unlock N_Port, 25 upgrading, 55 V VMware configuration for device mapping, 22 Z zoning schemes, 65 setting, 67 Access Gateway Administrator's Guide 75 53-1001760-01 - HP 1606 | Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 96
76 Access Gateway Administrator's Guide 53-1001760-01
53-1001760-01
30 March 2010
®
Access Gateway
Administrator’s Guide
Supporting Fabric OS v6.4.0