manualshive.com logo in svg

HP StoreFabric SN6500B, Руководство администратора

Поделиться
Скачать
HP StoreFabric SN6500B Скачать руководство пользователя страница 86

66

Access Gateway Administrator’s Guide

53-1002743-01

Adaptive Networking on Access Gateway

3

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

.

QoS: SID/DID traffic prioritization 

SID/DID traffic prioritization allows you to categorize the traffic flow between a given host and 
target as having a high or low priority; the default is medium. For example, you can assign online 
transaction processing (OLTP) to a high priority and the backup traffic to a low priority. 

For detailed information on this feature, refer to “QoS: SID/DID traffic prioritization” in the 

Fabric 

OS Administrator’s Guide.

Figure 13

 shows the starting point for QoS in various Brocade and non-Brocade configurations.

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:

•

If any of the AG QoS-enabled ports are active and you attempt a firmware downgrade, the 
downgrade is prevented. You must disable the QoS-enabled ports before performing a 
firmware downgrade. 

•

Upgrades from earlier versions to Fabric OS v7.1.0 are allowed, but AG QoS-enabled ports do 
not become effective until the ports are disabled or enabled so that QoS mode can be 
negotiated on the ISLs.

Содержание StoreFabric SN6500B

Страница 1: ...53 1002743 01 14 December 2012 Access Gateway Administrator s Guide Supporting Fabric OS v7 1 0 ...

Страница 2: ...ponsibility to any person or entity with respect to any loss cost liability or damages arising from the information contained in this book or the computer programs that accompany it The product described by this document may contain open source software covered by the GNU General Public License or other open source license agreements To find out which open source software is included in Brocade pr...

Страница 3: ...ance Device Security policy 16 bit routing March 2008 Access Gateway Administrator s Guide 53 1000605 03 Added support for Cascading Access Gateway July 2008 Access Gateway Administrator s Guide 53 1000605 04 Updated to fix the table of contents July 2008 Access Gateway Administrator s Guide 53 1001189 01 Updated for Fabric OS v6 2 0 November 2008 Access Gateway Administrator s Guide 53 1001345 01...

Страница 4: ...iv Access Gateway Administrator s Guide 53 1002743 01 ...

Страница 5: ...i Optional Brocade features xviii Getting technical help xviii Document feedback xix Chapter 1 Access Gateway Basic Concepts Brocade Access Gateway overview 1 Comparing Native Fabric and Access Gateway modes 1 Fabric OS features in Access Gateway mode 3 Buffer credit recovery support 5 Forward error correction support 6 Virtual Fabrics support 6 Device authentication support 6 Access Gateway port ...

Страница 6: ...e ADS policy 39 Automatic Port Configuration policy 39 How the APC policy works 39 Enabling and disabling the APC policy 40 APC policy considerations 40 Upgrade and downgrade considerations for the APC policy 40 Port Grouping policy 41 How port groups work 41 Adding an N_Port to a port group 42 Deleting an N_Port from a port group 42 Removing a port group 42 Renaming a port group 43 Disabling the ...

Страница 7: ...bled on unreliable links N_Port monitoring 57 Trunking in Access Gateway mode 58 How trunking works 58 Configuring trunking on the Edge switch 58 Configuration management for trunk areas 59 Enabling trunking 61 Disabling F_Port trunking 61 Monitoring trunking 61 AG trunking considerations for the Edge switch 62 Trunking considerations for Access Gateway mode 65 Upgrade and downgrade considerations...

Страница 8: ...Considerations for direct target attachment 74 Target aggregation 75 Access Gateway cascading 76 Access Gateway cascading considerations 76 Fabric and Edge switch configuration 77 Verifying the switch mode 77 Enabling NPIV on M EOS switches 78 Connectivity to Cisco fabrics 78 Enabling NPIV on a Cisco switch 78 Rejoining Fabric OS switches to a fabric 79 Reverting to a previous configuration 79 App...

Страница 9: ...Example of device mapping to N_Port groups 23 Figure 7 Example device mapping to an N_Port 24 Figure 8 Example of adding an external F_Port F9 on an embedded switch 30 Figure 9 Port grouping behavior 41 Figure 10 Port group 1 PG1 setup 42 Figure 11 Failover behavior 52 Figure 12 Failback behavior 56 Figure 13 Starting point for QoS 66 Figure 14 Direct target attachment to switch operating in AG mo...

Страница 10: ...x Access Gateway Administrator s Guide 53 1002743 01 ...

Страница 11: ...ng device HBA and receiving AG switch with different policies configured 8 Table 4 Port configurations 11 Table 5 Port state description 14 Table 6 Description of port mapping 16 Table 7 Access Gateway default port mapping 17 Table 8 Policy enforcement matrix 36 Table 9 Address identifier 60 Table 10 Access Gateway trunking considerations for the Edge switch 62 Table 11 PWWN format for F_Port and ...

Страница 12: ...xii Access Gateway Administrator s Guide 53 1002743 01 ...

Страница 13: ... following components Chapter 1 Access Gateway Basic Concepts describes the Brocade Access Gateway and provides an overview of its key features Chapter 2 Configuring Ports in Access Gateway Mode describes how to configure ports in Access Gateway mode Chapter 3 Managing Policies and Features in Access Gateway Mode describes how to enable policies on a switch in Access Gateway mode It also provides ...

Страница 14: ... or later and Cisco switches with SAN OS must be running 3 0 1 and 3 1 1 or later Fabric OS v7 1 0 supports the following Brocade hardware platforms for Access Gateway Brocade 300 Brocade 5100 Brocade M5424 Brocade 5430 Brocade 5450 Brocade 5460 Brocade 5470 Brocade 5480 Brocade 6505 Brocade 6510 Brocade 8000 NC 4380 Brocade VA 40FC What s new in this document The following information has been ad...

Страница 15: ...ribes text formatting conventions and important notices formats Text formatting The narrative text formatting conventions that are used in this document are as follows bold text Identifies command names Identifies the names of user manipulated GUI elements Identifies keywords and operands Identifies text to enter at the GUI or CLI italic text Provides emphasis Identifies variables Identifies paths...

Страница 16: ...directly to products to warn of these conditions or situations Notice to the reader This document may contain references to the trademarks of the following corporations These trademarks are the properties of their respective companies and corporations These references are made for informational purposes only variable Variables are printed in italics In the help pages values are underlined or enclo...

Страница 17: ...itch link ISL port A switch port that connects switches together to form a fabric Edge switch A fabric switch that connects host storage or other devices such as Brocade Access Gateway to the fabric F_Port A fabric port A switch port that connects a host host bus adapter HBA or storage device to the SAN On Brocade Access Gateway the F_Port connects to a host or a target Mapping In Access Gateway m...

Страница 18: ...ebsite athttp www brocade com products solutions products index page Best practice guides white papers data sheets and other documentation are available through the Brocade Partner website For additional resource information visit the Technical Committee T11 website This website provides interface standards for high performance and mass storage applications for Fibre Channel storage management and...

Страница 19: ...located inside the chassis on the port side on the left Brocade M5424 5450 5460 5470 5480 Serial number label attached to the module 3 World Wide Name WWN Use the licenseIdShow command to display the WWN of the chassis If you cannot use the licenseIdShow command because the switch is inoperable you can get the WWN from the same place as the serial number Document feedback Quality is our first conc...

Страница 20: ...xx Access Gateway Administrator s Guide 53 1002743 01 ...

Страница 21: ...out AG support in those tools After you set a Fabric OS switch to AG mode the F_Ports connect to the Enterprise fabric as N_Ports rather than as E_Ports Figure 1 shows a comparison of a configuration that connects eight hosts to a fabric using AG to the same configuration with Fabric OS switches in Native mode Switches in AG mode are logically transparent to the host and the fabric Therefore you c...

Страница 22: ...2 Access Gateway Administrator s Guide 53 1002743 01 Brocade Access Gateway overview 1 FIGURE 1 Switch function in Native mode ...

Страница 23: ... indicates the feature is not applicable in Access Gateway mode A single asterisk indicates the feature is transparent to AG that is AG forwards the request to the Enterprise fabric Two asterisks indicates that the feature may not be available if the Enterprise fabric is not a Brocade fabric For more information on these features refer to the Fabric OS Administrator s Guide and Fabric OS Command R...

Страница 24: ...No Fabric Assigned PWWN FA PWWN Yes Fabric Device Management Interface FDMI Yes Fabric Manager Yes Fabric Provisioning No Fabric Services No Fabric Watch Yes Refer to the Fabric Watch Administrator s Guide for applicable support details Fibre Channel Routing FCR services No FICON includes CUP No Forward Error Correction FEC Yes Refer to Forward error correction support on page 6 High Availability ...

Страница 25: ... Open E_Port NA Performance Monitor Yes Persistent ALPA Yes Port Decommission No Port Mirroring No QuickLoop QuickLoop Fabric Assist No Remote Authentication Dial In User Service RADIUS Yes Resource Monitor Yes Security Yes ADS DCC Policy SNMP Yes Speed Negotiation Yes Syslog Daemon Yes Track Changes Yes Trunking Yes User Defined Roles Yes ValueLineOptions Static POD DPOD Yes Virtual Fabrics No Re...

Страница 26: ...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 authentication support Devices use authentication as a mechanism to log in into switches only after exchanging DH_CHAP authorization keys This prevents any unauthorized device from logging into switch an...

Страница 27: ...licy mode set to off should not be connected to an AG switch with policy mode set to on since the on policy is strict This will disable the port if any switch rejects the authentication You must configure DH CHAP shared secrets or install FCAP certificates on the AG and connected fabric switch before switching from a policy off mode to policy on mode Off is the default mode for both switch and dev...

Страница 28: ...IVE Fabric switch with device policy mode OFF AG switch with switch policy mode on Authorization negotiation accept DH CHAP FCAP Success N_Port Failure disable Authorization negotiation accept DH CHAP FCAP Success N_Port Failure disable Authorization negotiation reject N_Port without authentication AG switch with switch policy off No negotiation No light No Negotiation N_Port without authencticati...

Страница 29: ...c port that connects a host HBA or storage device to a switch in AG mode N_Port Node port that connects a switch in AG mode to the F_Port of the fabric switch D_Port Port configured in diagnostic mode so that various tests can run between it and connected D_Port on another switch across a link NOTE Initiate the portcfgpersisentenable command on all external or outward facing ports to ensure that t...

Страница 30: ...g or after testing Once in D_Port mode the port does not participate in fabric operations login to a remote device or run data traffic Figure 4 on page 10 illustrates the supported D_Port configurations FIGURE 4 Diagnostic port configurations Table 4 shows a comparison of port configurations between AG and a standard fabric switch N_Port F_Port N_Port F_Port N_Port F_Port Hosts Switch in AG mode E...

Страница 31: ...a fabric TABLE 4 Port configurations 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 the fabric N_Port Yes Connects Access Gateway to a fabric switch NA N_Ports are not supported E_Port NA ISL is not supported 1 1 The switch is logically transparent to the fabric therefor...

Страница 32: ...12 Access Gateway Administrator s Guide 53 1002743 01 Access Gateway hardware considerations 1 ...

Страница 33: ...ion again 3 Ensure that no zoning or Admin Domain AD transaction buffers are active If any transaction buffer is active enabling AG mode will fail with the error Failed to clear Zoning Admin Domain configuration 4 Verify that the switch is set to Native mode a Issue the switchShow command to verify the switch mode b If the switch mode is anything other than 0 issue the interopmode 0 command to set...

Страница 34: ...ters such as port mapping and Failover and Failback are automatically removed When the switch reboots it starts in Fabric OS Native mode To rejoin the switch to the core fabric refer to Rejoining Fabric OS switches to a fabric on page 79 10 Enter the switchDisable command to disable the switch switch admin switchdisable 11 Enter the ag command with the modedisable option to disable AG mode switch ...

Страница 35: ... F_Port is mapped to a specific N_Port This ensures that all traffic from a specific F_Port always goes through the same N_Port To map an F_Port to an N_Port group simply map the port to an N_Port that belongs to that port group All F_Ports mapped to that N_Port will be part of that N_Port group Device mapping optional A specific device WWN is mapped to N_Port groups preferred method or to specifi...

Страница 36: ...able 7 on page 17 describes the default port mapping for all supported hardware platforms By default Failover and Failback policies are enabled on all N_Ports If you want to change the default mapping refer to Adding F_Ports to an N_Port on page 20 Note that all F_Ports must be mapped to an N_Port before the F_Port can come online TABLE 6 Description of port mapping Access Gateway Fabric F_Port N_...

Страница 37: ...6 0 17 23 1 2 mapped to 17 9 10 mapped to 18 3 4 mapped to 19 11 12 mapped to 20 15 16 mapped to 0 5 6 mapped to 21 13 14 mapped to 22 7 8 mapped to 23 300 24 0 15 16 23 0 1 mapped to 16 2 3 mapped to 17 4 5 mapped to 18 6 7 mapped to 19 8 9 mapped to 20 10 11 mapped to 21 12 13 mapped to 22 14 15 mapped to 23 5100 40 0 31 32 39 0 1 2 3 mapped to 32 4 5 6 7 mapped to 33 8 9 10 11 mapped to 34 12 1...

Страница 38: ...apped 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 mapped to 15 5 6 7 mapped to 16 8 9 mapped to 17 10 11 mapped to 18 12 13 14 mapped to 19 5480 24 1 16 0 17 23 1 2 mapped to 17 9 10 mapped to 18 3 4 mapped to 19 11 12 mapped to 20 15 16 mapped to 0 5 6 mapped to 21 13 14 mapped to 22 7 8 mapped to 23 6505 24 0 15...

Страница 39: ...oE ports and 8 external Fibre Channel ports In Access Gateway mode the internal FCoE ports are configured logically as F_Ports while the external Fibre Channel ports are configured as N_Ports The FCoE ports are divided into six groups or trunks consisting of four ports each All four ports in a group are mapped to one N_Port Although you can change the default port mapping for these groups refer to...

Страница 40: ...account assigned to the admin role 2 Remove any preferred secondary N_Port settings for the F_Port Refer to Deleting F_Ports from a preferred secondary N_Port on page 53 for instructions 3 Enter the ag mapdel N_Port command with the f_port1 f_port option to remove F_Ports from an N_Port The F_Port list can contain multiple F_Port numbers separated by semicolons In the following example F_Ports 17 ...

Страница 41: ... static mappings are deleted using the ag staticdel command F_Port Static Mapping works with the Port Grouping PG policy with some modifications to policy behavior If static mapping is applied to an F_Port already mapped to an N_Port the F_Port will lose its mapping to the N_Port applied through the Port Grouping policy Therefore the F_Port will not have the failover failback or preferred N_Port s...

Страница 42: ...n a port group This ensures maximum device up time especially during failover conditions and system power up This is especially true when a reasonably large number of devices must connect to the same fabric through a single port group The following aspects of device mapping are important to note Logins from a device mapped to a specific N_Port or N_Port group device mapping always have priority ov...

Страница 43: ...apping 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 Hosts Targets Access Gateway F_3 F_2 F_1 N_4 WWN1 WWN2 WWN3 F_4 WWN4 WWN5 N_5 F_6 N_6 F_5 N_2 N_1 N_3 PG2 PG1 ...

Страница 44: ... If a device is mapped to an N_Port group then all mapping is dynamic NOTE Static and dynamic mapping only applies to NPIV devices and cannot redirect devices that are directly attached to Access Gateway because physically attached devices use the port maps to connect to the fabric Device mapping to port groups recommended Mapping NPIV devices to a port group is an ideal choice when a reasonably s...

Страница 45: ...wo devices from port group 3 ag delwwnpgmapping 3 10 00 00 06 2b 0f 71 0c 10 00 00 05 1e 5e 2c 11 5 To remove all devices mapped to an N_Port group enter the command with the all option instead of listing all WWNs All of the devices will cease automatic use of the least loaded port in the port group when they log in The all option is a shortcut for specifying all of the devices that are already ma...

Страница 46: ...mapped or removed from the desired N_Ports Disabling device mapping Use the following procedures to disable device mapping for all or only specific devices These procedures are useful when you want to temporarily disable device mapping and then enable this at a later time without reconfiguring your original mapping To enable device mapping refer to Enabling device mapping on page 26 1 Connect to t...

Страница 47: ... in to the switch To display device mapping information enter the ag wwnmapshow command Pre provisioning You can use Fabric OS commands Web Tools and Fabric Manager to map devices that do not yet exist This allows applicable management programs to push configuration changes without worrying about the order in which they are received For example if system administrators need to push a set of port g...

Страница 48: ... documents brocade_vmware_technical_briefs Brocade_NP IV_ESX3 5_WP pdf Failover and failback considerations When using device mapping with VMware the base device initiates PLOGI and PRLI to the target and then discovers the LUN The virtual device also initiates a PLOGI and PRLI to the target but LUN discovery does not occur Therefore when the device mapped port is toggled and failover or failback ...

Страница 49: ...atically rebalanced to another N_Port if an additional N_Port comes online There can be cases where two NPIV devices logging in through the same F_Port are mapped to two different N_Ports that are connected to two different fabrics In this case both NPIV devices may be allocated the same PID by their respective fabrics Once Access Gateway detects this condition it will disable that F_Port and the ...

Страница 50: ...Port to an F_Port first remove all the F_Ports that are mapped to that N_Port then unlock the port from N_Port state Finally define a map for the port It is highly recommended that all F_Ports mapped to the N_Port first be remapped to other N_Ports before converting the N_Port to an F_Port Also note that if the Automatic Port Configuration APC policy is enabled the port conversion is done automati...

Страница 51: ...min role 2 Enter the portcfgnport command to display which ports on the switch are locked as N_Ports Command output will display ON for locked N_Ports NOTE The portcfgnport command only works when the Port Grouping policy is enabled 3 Enter the portcfgnport command and specify the port number and 0 zero to unlock N_Port mode switch admin portcfgnport 10 0 Alternatively to lock a port in N_Port mod...

Страница 52: ...tch The following tests automatically run on the link between configured D_Ports Electrical loopback Optical loopback Link traffic Link latency and distance measurement NOTE For details on configuring D_Ports using D_Ports and D_Port limitations and considerations refer to the Fabric OS Troubleshooting and Diagnostics Guide For details on D_Port related commands refer to the Fabric OS Command Refe...

Страница 53: ...ppings The following are available backup mapping commands For more details refer to the Fabric OS Command Reference To save configured N_Port mappings enter the following command ag backupmappingsave N_Port To display saved N__Port mappings so that you can reconfigure them on the switch enter the following command ag backupmappingshow N_Port Following is an example of command output sw0 root ag b...

Страница 54: ...34 Access Gateway Administrator s Guide 53 1002743 01 D_Port support 2 ...

Страница 55: ...t NPIV login limit 67 Advanced Performance Monitoring 68 Considerations for the Brocade 8000 70 Considerations for the Brocade 6505 and 6510 72 Access Gateway policies overview This chapter provides detailed information on all Access Gateway policies These policies can be used to control various advanced features such as failover failback and trunking when used in Access Gateway mode Displaying cu...

Страница 56: ...rough an F_Port You can view the devices with active connections to an F_Port using the ag show command NOTE The ag show command only displays F_Ports on Core AGs such as the AGs that are directly connected to fabric Use the agshow name command on the fabric switch to display the F_Ports of both the Core and Edge AGs Alternatively the security policy can be established in the Enterprise fabric usi...

Страница 57: ...e separated by semicolons The maximum number of entries in the allowed device list is twice the per port maximum login count Use an asterisk instead of port numbers in the F_Port list to add the specified WWNs to all the F_Ports allow lists Use an asterisk instead of WWNs to indicate access to all devices from the specified F_Port list A blank WWN list indicates no access NOTE Use an asterisk encl...

Страница 58: ... 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 In the following example two devices are removed from the list of allowed devices ports 3 and 9 switch admin ag adsdel 3 9 22 03 08 00 88 35 a0 12 22 00 00 e0 8b 88 01 8b WWNs removed successfully from Allow Lists of the F_Port s Viewing F_...

Страница 59: ... ADS policy is not supported with device mapping Upgrade and downgrade considerations for the ADS policy Downgrading to Fabric OS v6 4 0 or earlier is supported Downgrading from Fabric OS v7 1 0 to v6 4 0 or upgrading from Fabric OS v6 4 0 to v7 1 0 will not change the ADS policy settings Automatic Port Configuration policy The Automatic Port Configuration APC provides the ability to automatically...

Страница 60: ... the switchEnable command to enable the switch APC policy considerations Following are the considerations for the Automatic Port Configuration APC policy The APC and the PG policies cannot be enabled at the same time You can still benefit from the automatic port mapping feature of the APC policy when the Port Grouping policy is enabled by enabling the auto distribution feature for each port group ...

Страница 61: ...ort groups Figure 9 shows that if you have created port groups and then an N_Port goes offline the F_Ports being routed through that port will fail over to any of the N_Ports that are part of that port group and are currently online For example if N_Port 4 goes offline then F_Ports 7 and 8 are routed through to N_Port 3 as long as N_Port 3 is online because both N_Ports 3 and 4 belong to the same ...

Страница 62: ...ort should be remapped before the N_Port is deleted from a port group 1 Connect to the switch and log in using an account assigned to the admin role 2 Enter the ag pgdel command with the appropriate options to delete an N_Port from a specific port group In the following example N_Port 13 is removed from port group 3 switch admin ag pgdel 3 13 N_Port s are deleted from port group 3 3 Enter the ag p...

Страница 63: ...and an F_Port goes offline logins in the port group are redistributed among the remaining F_Ports Similarly if an N_Port comes online port logins in the port group are redistributed to maintain a balanced N_Port to F_Port ratio Consider the following notes about Automatic Login Balancing mode Automatic Login Balancing mode is disruptive However you can minimize disruption by disabling or enabling ...

Страница 64: ...des N_Ports 1 and 3 and has Automatic Login Balancing lb enabled switch admin ag pgcreate 3 1 3 n FirstFabric1 m lb Port Group 3 created successfully 3 Enter the ag pgshow command to verify the port group was created A table containing a port group with ID 3 and ports 1 and 3 should display Rebalancing F_Ports To minimize disruption that could occur once F_Ports go offline or when additional N_Por...

Страница 65: ... to N_Ports To control automatic rebalancing to avoid disruptions when the Port Grouping policy is enabled refer to Rebalancing F_Ports on page 44 Enabling MFNM mode 1 Connect to the switch and log in using an account assigned to the admin role 2 Enter the ag pgsetmodes command with the appropriate options to enable MFNM mode This command changes the monitoring mode from default to managed In the ...

Страница 66: ...tains its original failover or failback setting If an N_Port is deleted from a port group it automatically gets added to port group 0 When specifying a preferred secondary N_Port for a port group the N_Port must be from the same group If you specify an N_Port as a preferred secondary N_Port and it already belongs to another port group the operation fails Therefore it is recommended to form groups ...

Страница 67: ...ou can enable Device Load Balancing Manually created mappings from devices to N_Ports take precedence over automatically created mappings Refer to Mapping priority on page 28 for details on connection priority for AG port mapping For more information on device mapping refer to Device mapping on page 21 Enabling the Device Load Balancing policy Use the following steps to enable Device Load Balancin...

Страница 68: ... of and into the same F_Port Because the Arbitrated Port Loop Address ALPA field makes up a portion of the PID the PID may change across switch or server power cycles This policy if enabled helps reduce the chances of a different PID being issued for the same host The benefit of this policy is that it ensures that a host has the same ALPA on the F_Ports through the host power cycle You can also ac...

Страница 69: ...sistent ALPA device data Access Gateway uses a table to maintain a list of available and used ALPAs When the number of entries in this table is exhausted the host receives an error message You can remove some of the entries to make space using the instructions in Removing device data from the database Removing device data from the database Use the following steps to remove device data from the dat...

Страница 70: ... Failover policy is enabled by default and is enforced during power up The Failover policy allows hosts and targets to automatically remap to another online N_Port if the primary N Port goes offline NOTE For port mapping the Failover policy must be enabled on an N_Port for failover to occur For device mapping if a device is mapped to an N_Port in a port group the device will always reconnect to th...

Страница 71: ..._Port Failover example The following example shows the failover sequence of events in a scenario where two fabric ports go offline one after the other Note that this example assumes that no preferred secondary N_Port is set for any of the F_Ports First the Edge switch F_A1 port goes offline as shown in Figure 11 on page 52 Example 1 left causing the corresponding Access Gateway N_1 port to be disa...

Страница 72: ...to the admin role 2 Enter the ag prefset command with the F_Port1 F_Port2 N_Port options to add the preferred secondary F_Ports to the specified N_Port The F_Ports must be enclosed in quotation marks and the port numbers must be separated by a semicolon as shown in the following example switch admin ag prefset 3 9 4 Preferred N_Port is set successfully for the F_Port s NOTE Preferred mapping is no...

Страница 73: ...r or Failback policy on an N_Port the F_Port will not fail over or fail back to other N_Ports Failover behavior is different if a device is mapped to a specific N_Port instead of to an N_Port group If mapping a device to a specific N_Port you can define a secondary N_Port that will be used if the primary N_Port is offline To maximize the device uptime it is recommended to map the device to a port ...

Страница 74: ...with the all option The following command removes N_Port 32 as the secondary N_Port for all available devices ag delwwnfailovermapping 32 all Enabling and disabling the Failover policy on an N_Port Use the following steps to enable or disable the Failover policy on a specific N_Port 1 Connect to the switch and log in using an account assigned to the admin role 2 Enter the ag failovershow N_Port co...

Страница 75: ...mapping the Failback policy must be enabled on an N_Port for failback to occur For device mapping the Failback policy has no effect If a device is mapped to a port group it will always fail over to an online N_Port in the port group or secondary N_Port if configured and will remain connected to this failover N_Port when the original N_Port comes back online NOTE If failover and failback policy are...

Страница 76: ...e failback setting switch admin ag failbackshow 13 Failback on N_Port 13 is not supported 3 Use the following commands to enable or disable the Failback policy 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 failbackdisab...

Страница 77: ...ks from all N_Ports are monitored for the number of online and offline static change notifications SCNs that occur during a set time period 5 minutes If the number of SCNs on a link exceeds a set threshold the link is considered unreliable and failback is disabled for that N_Port Failover continues for the port as needed Once the number of SCNs drops below the set threshold the port is deemed reli...

Страница 78: ...eep the same license NOTE N_Port trunking is not supported to HBAs connected to switches running in Access Gateway mode N_Port trunking is only supported for HBAs connected to switches running in Native mode How trunking works Trunking in Access Gateway mode provides a trunk group between N_Ports on the AG module and F_Ports on the Edge switch module With trunking any link within a trunk group can...

Страница 79: ...rts within an ASIC trunk group are used to group the ports as part of a trunk on the Edge switch or on an AG 6 Ensure that both modules are running the same Fabric OS versions Configuration management for trunk areas The porttrunkarea command does not allow ports from different admin domains ADs and ports from different logical switches to join the same trunk area TA group When you assign a TA the...

Страница 80: ...r the appropriate ports The following example enables a TA for ports 13 and 14 on slot 10 with port index of 125 switch admin porttrunkarea enable 10 13 14 index 125 4 Display the TA port configuration ports still disabled using the porttrunkarea show enabled command 5 Enable the ports specified in step 3 using the portenable command switch admin portenable 10 13 switch admin portenable 10 14 6 Sh...

Страница 81: ...o re enable the desired ports such as ports 36 39 5 Enter the switchhow command to display the switch or port information including created trunks Disabling F_Port trunking Use the following steps to disable F_Port trunking 1 Connect to the switch and log in using an account assigned to the admin role 2 Enter the porttrunkarea disable command switch admin porttrunkarea disable 36 39 ERROR port 36 ...

Страница 82: ...istration 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 assigning a Trunk Area on the Edge switch to the port or removing a Trunk Area from a trunk group You cannot assign a Trunk Area to ports if the standby CP is running a firmware version earlier than Fabric OS v6 2 0 PWWN The entire Trun...

Страница 83: ...runk Area FICON 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 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 enabled o...

Страница 84: ... for the F_Port trunk is based on the Trunk Area the FDISC request to a trunk port is accepted only if the WWN of the attached device is part of the DCC policy against the TA The PWWN of the FLOGI sent from the AG will be dynamic for the F_Port trunk master Because you do not know ahead of time what PWWN AG will use the PWWN of the FLOGI will not go through DCC policy check on an F_Port trunk mast...

Страница 85: ...owngrade considerations for trunking in Access Gateway mode Upgrading to Fabric OS v7 1 0 and downgrading to Fabric OS v6 4 0 and earlier is supported 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 conj...

Страница 86: ... detailed information on this feature refer to QoS SID DID traffic prioritization in the Fabric OS Administrator s Guide Figure 13 shows the starting point for QoS in various Brocade and non Brocade configurations 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 followi...

Страница 87: ...use additional tools to design and implement a virtual infrastructure In Access Gateway mode this feature allows smaller login limits for F_Ports and larger limits for N_Ports Note that N_Ports are restricted by the NPIV login limit of the connecting port on the Edge switch Note the following aspects of this feature Upgrading between Fabric OS v6 4 0 and v7 1 0 will retain the NPIV settings The va...

Страница 88: ...s End to end monitors End to end monitors measure the traffic between a host and target pair by counting the number of words in Fibre Channel frames for a specified Source ID SID and Destination ID DID pair An end to end performance monitor includes these counts RX_COUNT Words in frames received at the port TX_COUNT Words in frames transmitted from the port To enable end to end performance monitor...

Страница 89: ... be monitored Add a set of ports for which a specific frame type can be monitored Save a set of ports on which the specified frame type can be monitored Show different frame types configured on the switch as well as frame counters Change properties for a particular frame type such as thresholds and bit pattern Clear a set of ports on which the specified frame type is monitored to the persistent co...

Страница 90: ...Brocade 8000 This section provides information on differences in operation Fabric OS command function and features on the Brocade 8000 when operating in Access Gateway mode Port mapping The Brocade 8000 contains FCoE and Fibre Channel ports In Access Gateway mode the FCoE ports are configured logically as F_Ports while the Fibre Channel ports are configured as N_Ports For details on how this affec...

Страница 91: ...be available for trunking due to the function of QoS Managed Fabric Name Monitoring mode Managed Fabric Name Monitoring MFNM mode is enabled by default on the Brocade 8000 However you can disable or enable this policy at any time Enabling or disabling MFNM on one port group enables or disables it for the entire switch RASLOG messages are generated only if MFNM is enabled on the entire switch and m...

Страница 92: ...FCoE ports use fcoe enable and fcoe disable instead of portdisable and portenable The portcfgdefault command resets the degraded state and NPIV PerPort and clears the BufferLimitedMode on a port For other AG platforms this command restores the port configuration to factory default values Considerations for the Brocade 6505 and 6510 The Brocade 6505 and 6510 can function in either Fabric OS Native ...

Страница 93: ...on direct target attachment port requirements NPIV HBA and interoperability Switches in AG mode can connect to third party fabrics 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 Considerations for connecting multiple devices Consider the following points when connecting multiple devices to a switch in AG mode AG does not s...

Страница 94: ...ect target attachment Consider the following points for direct target attachment Direct target attachment to AG is only supported if the AG module is also connected to a core fabric A switch module running in AG mode does not provide Name Services on its own and routing to the target devices must be established by the core fabric Hosts and targets cannot be mapped to the same N_Port Redundant conf...

Страница 95: ...t 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 Target aggregation has many applications As one example you can consolidate targets with various lower Fibre Channel speeds such as 1 2 or 4 Gbps onto a single high speed uplink port to the core fabric This reduces the number of core fabric ports used by target device...

Страница 96: ...o the main fabric There is no license requirement to use this feature Access Gateway cascading considerations Note the following configuration considerations when cascading Access Gateways Only one level of cascading is supported Note that several Edge AGs can connect into a single Core AG to support an even higher consolidation ratio AG trunking between the Edge and Core AG switches is not suppor...

Страница 97: ...nly WWN zoning for devices behind AG If DCC security is being used on Edge switches that directly connect to AG make sure to include the Access Gateway WWN or the port WWN of the N_Ports Also include the HBA WWNs that will be connected to AG F_Ports in the switch s Access Control List ACL It is recommended to use AG ADS policy instead of the DCC policy on the Edge switch Allow inband queries for f...

Страница 98: ...nality on the Edge fabric ports so that multiple logins are allowed for each port Enter the following command on the M EOS switch to enable NPIV on the specified ports config NPIV Your M EOS switch is now ready to connect NOTE You can run the agshow command to display Access Gateway information registered with the fabric When an Access Gateway is exclusively connected to non Fabric OS based switch...

Страница 99: ...using the fabric configuration use the following procedure To rejoin the Fabric OS switch to a fabric perform the following steps 1 Connect to the switch and log in using an account assigned to the admin role 2 Enter the switchDisable command to disable the switch 3 Enter the defZone allAccess command to allow the switch to merge with the fabric 4 Enter the cfgSave command to commit the Default zo...

Страница 100: ...80 Access Gateway Administrator s Guide 53 1002743 01 Rejoining Fabric OS switches to a fabric 4 ...

Страница 101: ...nt Enter the portCfgShow command For each port that is to be activated as an N_Port enter the portCfgNport port_number command with the 1 option All other ports remain as F_Ports To reset the port to an F_Port enter the portCfgNpivPort port_number command with the disable option LUNs are not visible Zoning on fabric switch is incorrect Port mapping on Access Gateway mode switch is incorrect Cablin...

Страница 102: ...uring F_Port and N_Port disruptions on Brocade 8000 in Access Gateway mode The CNA host is retrying a login before the switch has finished precessing a previous fabric logout LOGO attempt Messages display as designed After the switch has completed LOGO processing it will accept another login Login Rejected by FC stack messages on console may be seen during F_Port and N_Port disruptions on Brocade ...

Страница 103: ... upgrade and downgrade considerations 66 adding devices to fabric 38 address Identifier 60 admin domain 64 ADS Policy adding devices 38 displaying devices 38 39 enabling 37 removing devices 38 advanced performance monitoring 68 APC Policy disabling 40 rebalancing F_Ports 44 support for port groups 43 area assignment 62 authentication considerations 8 device 6 limitations 8 policy modes 7 related c...

Страница 104: ...mand 64 merging switch with fabric 79 re joining switch to fabric 79 saving 79 using configdownload command 79 D D_Port configurations supported 32 description 9 10 32 saving port mappings 33 tests 32 daisy chaining 73 DCC policy adding WWN 60 enabling 60 limitation creating TA 64 default area removing ports 63 device load balancing 44 device load balancing policy 47 APC policy 48 considerations 4...

Страница 105: ...rt mapping 51 enabling 54 example 52 56 port mapping 50 fast write limitation 63 FICON F_Port trunk ports 63 frame monitors 69 H HA sync TA present 62 I ICL ports limitations 64 inband queries 77 initiator and target port considerations 19 J join fabric 79 L limitations device load balancing 48 direct connections to target devices 11 loop devices not supported 11 login balancing considerations 45 ...

Страница 106: ... advance device security 36 enabling DCC policy 60 enforcement matrix 36 port grouping 41 showing current policies 35 using policyshow command 35 port comparison 9 mapping 15 requirements 73 types 9 port group add N_Port 42 44 create 44 delete N_Port 42 disabling 43 enabling logging balancing mode 44 login balancing mode 43 managed fabric name monitoring mode 44 remove port group 42 rename 43 Port...

Страница 107: ...dynamic mapping 24 supported hardware and software xiv switch mode verify 77 T terms xvii trunk area assign 60 configuration management 59 disabling 63 remove ports 60 standby CP 62 using the porttrunkarea command 63 trunk groups create 59 trunk master limitation 63 trunking 58 configuring on edge switch 58 considerations in AG module 65 considerations on edge switch 62 disabling 61 enabling 61 63...

Страница 108: ...88 Access Gateway Administrator s Guide 53 1002743 01 ...

Отзывы:

Нет отзывов

Бренды по названию

Популярные бренды

Загрузить еще бренды