Home » HP Manuals » Storage Devices » HP 8/8 » Manual Viewer

HP 8/8 Brocade Access Gateway Administrator's Guide v6.3.0 (53-1001345-01, Jul - Page 70

Fabric and Edge switch configuration, Fabric

Add to My Manuals
Save this manual to your list of manuals

Page 70 highlights

4 Fabric and Edge switch configuration F_Port N_Port F_ Port Edge AG F_Port N_Port F_ Port F_Port N_Port Core AG F_ Port Fabric FIGURE 11 Access Gateway cascading AG cascading provides higher over-subscription because it allows you to consolidate the number of ports going to the main fabric. There is no license requirement to use this feature. 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 even a higher consolidation ratio. • AG trunking between the Edge and Core AG switches is not supported. Trunking between the Core AG 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 on the fabric will discover only the Core AG switches. If issued as agshow --name AG name, then the F_Ports of both the Core and Edge AG switches will be shown for the Core AG switch. • Due to high subscription ratios that could occur when cascading AGs, ensure there is enough bandwidth for all servers when creating such configurations. The subscription ratio becomes more acute in a virtual environment. Fabric and Edge switch configuration To connect devices to the fabric using Access Gateway, configure the fabric and Edge switches within the fabric that will connect to the AG module using the following parameters. These parameters apply to Fabric OS, M-EOS, and Cisco-based fabrics: • Install and configure the switch as described in the switch's Hardware Reference manual before performing these procedures. • Verify that the interop mode parameter is set to Brocade Native mode. • Configure the F_Ports on the Edge switch to which Access Gateway is connected as follows: • Enable NPIV. 50 Access Gateway Administrator's Guide 53-1001345-01

Section	Page
About This Document	13
How this document is organized	13
Supported hardware and software	13
What’s new in this document	14
Document conventions	15
Text formatting	15
Command syntax conventions	15
Notes, cautions, and warnings	15
Notice to the reader	16
Key terms	16
Additional information	17
Brocade resources	17
Other industry resources	17
Optional Brocade features	18
Getting technical help	18
Document feedback	19
Access Gateway Basic Concepts	21
In this chapter	21
Brocade Access Gateway overview	21
Comparing Native Fabric and Access Gateway modes	21
Fabric OS features in Access Gateway mode	23
Access Gateway port types	24
Comparison of Access Gateway ports to standard switch ports	24
Access Gateway limitations	25
Configuring Ports in Access Gateway mode	27
In this chapter	27
Enabling and disabling Access Gateway mode	27
Port state description	29
Access Gateway mapping	30
Default port mapping	31
Adding F_Ports to an N_Port	33
Removing F_Ports from N_Ports	34
N_Port configurations	35
Displaying N_Port configurations	36
Unlocking N_Ports	36
Managing Policies and Features in Access Gateway Mode	37
In this chapter	37
Access Gateway policies overview	37
Displaying current policies	37
Access Gateway policy enforcement matrix	38
Advanced Device Security policy	38
How the ADS policy works	38
Enabling and disabling the Advanced Device Security policy	39
Setting the list of devices allowed to log in	39
Setting the list of devices not allowed to log in	40
Removing devices from the list of allowed devices	40
Adding new devices to the list of allowed devices	40
Displaying the list of allowed devices on the switch	41
ADS policy considerations	41
Upgrade and downgrade considerations for the ADS policy	41
Automatic Port Configuration policy	41
How the APC policy works	42
Enabling and disabling the APC policy	42
Automatic Port Configuration policy considerations	43
Upgrade and downgrade considerations for the APC policy	43
Port Grouping policy	43
How port groups work	43
Adding an N_Port to a port group	44
Deleting an N_Port from a port group	45
Removing a port group	45
Renaming a port group	45
Disabling the Port Grouping policy	45
Port Grouping policy modes	46
Creating a port group and enabling login balancing mode	46
Rebalancing F_Ports	47
Enabling Managed Fabric Name Monitoring mode	48
Disabling Managed Fabric Name Monitoring mode	48
Displaying the current fabric name monitoring timeout value	48
Setting the current fabric name monitoring timeout value	48
Port Grouping policy considerations	48
Upgrade and downgrade considerations for the Port Grouping policy	49
Persistent ALPA Policy	49
Enabling Persistent ALPA	50
Disabling Persistent ALPA	50
Persistent ALPA device data	50
Removing device data from the database	50
Displaying device data	51
Clearing ALPA values	51
Persistent ALPA policy considerations	51
Upgrade and downgrade considerations for Persistent ALPA	51
Failover	52
Failover configurations in Access Gateway	52
Enabling and disabling Failover on a N_Port	53
Enabling and disabling Failover for a port group	54
Upgrade and downgrade considerations for Failover	54
Adding a preferred secondary N_Port	54
Deleting F_Ports from a preferred secondary N_Port	54
Failback	55
Failback configurations in Access Gateway	55
Enabling and disabling Failback on an N_Port	56
Enabling and disabling Failback for a port group	57
Upgrade and downgrade considerations for Failback	57
Trunking in Access Gateway mode	57
How Trunking works	57
Trunking on the Edge switch in Access Gateway mode	58
Configuration management for trunk areas	59
Enabling Access Gateway trunking	60
Disabling F_Port trunking	62
F_Port Trunking monitoring	62
Trunking considerations for the Edge switch	62
Trunking considerations for Access Gateway mode	66
Upgrade and downgrade considerations for Trunking in Access Gateway mode	66
Adaptive Networking on Access Gateway	66
Upgrade and downgrade considerations with Adaptive Networking in AG mode enabled	67
Adaptive Networking on Access Gateway considerations	67
SAN Configuration with Access Gateway	69
In this chapter	69
Connectivity of multiple devices overview	69
Access Gateway cascading	69
Fabric and Edge switch configuration	70
Verifying the switch mode	71
Enabling NPIV on M-EOS switches	72
Connectivity to Cisco Fabrics	72
Enabling NPIV on a Cisco switch	73
Workaround for certain 4 Gbps QLogic-based devices	73
Editing Company ID List if no FC target devices on switch	73
Adding or deleting an OUI from the Company ID List	74
Enabling Flat FCID mode if no FC target devices on switch	74
Editing Company ID list if target devices on switch	75
Rejoining Fabric OS switches to a fabric	75
Reverting to a previous configuration	76
Troubleshooting	77

Match case Limit results 1 per page

Access Gateway Administrator’s Guide

53-1001345-01

Fabric and Edge switch configuration

FIGURE 11

Access Gateway cascading

AG cascading provides higher over-subscription because it allows you to consolidate the number of

ports going to the main fabric. There is no license requirement to use this feature.

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 even a higher consolidation ratio.

•

AG trunking between the Edge and Core AG switches is not supported. Trunking between the

Core AG 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 on the fabric will discover only the Core AG switches. If issued as

agshow

name

AG name

, then the F_Ports of both the Core and Edge AG switches will be

shown for the Core AG switch.

•

Due to high subscription ratios that could occur when cascading AGs, ensure there is enough

bandwidth for all servers when creating such configurations. The subscription ratio becomes

more acute in a virtual environment.

Fabric and Edge switch configuration

To connect devices to the fabric using Access Gateway, configure the fabric and Edge switches

within the fabric that will connect to the AG module using the following parameters. These

parameters apply to Fabric OS, M-EOS, and Cisco-based fabrics:

•

Install and configure the switch as described in the switch’s Hardware Reference manual

before performing these procedures.

•

Verify that the interop mode parameter is set to Brocade Native mode.

•

Configure the F_Ports on the Edge switch to which Access Gateway is connected as follows:

•

Enable NPIV.

F_Port

F_ Port

Edge

N_Port

F_Port

F_ Port

N_Port

F_Port

N_Port

F_ Port

Fabric

Core