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

HP 8/80 Access Gateway Administrator's Guide (53-1001760-01, June 2010) - Page 90

Troubleshooting Continued

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

Page 90 highlights

A Troubleshooting 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 port_number operand. Command returns "Failback (or Failover) on N_Port port_number is supported." If it returns, "Failback (or Failover) on N_Port port_number is not supported." See "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 is offline, the F_Ports will disable. Define the preferred secondary N_Ports per F_Port. For example, if two F_Ports are mapped to a primary N_Port 1, you can define a secondary N_Port for one of those F_Ports and not define a secondary N_Port for the other F_Port. F_Ports must have a primary N_Port mapped before a secondary N_Port can be configured." on page 45. Access Gateway is mode Access Gateway must be disabled. not wanted Disable switch using the switchDisable command. Disable Access Gateway mode using the ag --modeDisable command. Answer yes when prompted; the switch reboots. Log in to the switch. Display the switch settings using the switchShow command. Verify that the field switchMode displays Fabric OS Native mode. "Login Rejected by FC stack" messages on console may be seen during F_Port and N_Port disruptions on Brocade 8000 in AG Mode. The CNA host is retrying a log in before the switch has finished precessing a previous fabric logout (LOGO) attempt. Working as designed. After the switch has completed LOGO processing, it will accept another login. NOTE If a Fabric OS switch is in AG mode and is also set to McDATA Fabric mode, when that switch is connected to an M-EOS switch, the Fabric OS switch does not display in the output when you run the agshow command. 70 Access Gateway Administrator's Guide 53-1001760-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 hardware considerations	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
Port-based mapping	30
Device-based mapping	35
Considerations for Access Gateway mapping	42
N_Port configurations	44
Displaying N_Port configurations	45
Unlocking N_Ports	45
Managing Policies and Features in Access Gateway Mode	47
In this chapter	47
Access Gateway policies overview	47
Displaying current policies	47
Access Gateway policy enforcement matrix	48
Advanced Device Security policy	48
How the ADS policy works	48
Enabling and disabling the Advanced Device Security policy	49
Setting the list of devices allowed to log in	49
Setting the list of devices not allowed to log in	50
Removing devices from the list of allowed devices	50
Adding new devices to the list of allowed devices	50
Displaying the list of allowed devices on the switch	51
ADS policy considerations	51
Upgrade and downgrade considerations for the ADS policy	51
Automatic Port Configuration policy	51
How the APC policy works	51
Enabling and disabling the APC policy	52
Automatic Port Configuration policy considerations	52
Upgrade and downgrade considerations for the APC policy	53
Port Grouping policy	53
How port groups work	53
Adding an N_Port to a port group	54
Deleting an N_Port from a port group	55
Removing a port group	55
Renaming a port group	55
Disabling the Port Grouping policy	55
Port Grouping policy modes	56
Creating a port group and enabling Automatic Login Balancing mode	56
Rebalancing F_Ports	57
Enabling Managed Fabric Name Monitoring mode	58
Disabling Managed Fabric Name Monitoring mode	58
Displaying the current fabric name monitoring timeout value	58
Setting the current fabric name monitoring timeout value	59
Port Grouping policy considerations	59
Upgrade and downgrade considerations for the Port Grouping policy	60
Device Load Balancing Policy	60
Enabling WWN Load Balancing	60
Disabling Device Load Balancing	60
Device Load Balancing considerations	61
Persistent ALPA Policy	61
Enabling Persistent ALPA	62
Disabling Persistent ALPA	62
Persistent ALPA device data	62
Removing device data from the database	62
Displaying device data	63
Clearing ALPA values	63
Persistent ALPA policy considerations	63
Upgrade and downgrade considerations for Persistent ALPA	63
Failover	64
Failover with port-based mapping	64
Failover with device-based mapping	66
Enabling and disabling Failover on a N_Port	67
Enabling and disabling Failover for a port group	67
Upgrade and downgrade considerations for Failover	68
Failback	68
Failback configurations in Access Gateway	68
Enabling and disabling Failback on an N_Port	69
Enabling and disabling Failback for a port group	70
Upgrade and downgrade considerations for Failback	70
Trunking in Access Gateway mode	70
How Trunking works	70
Configuring Trunking on the Edge switch	71
Configuration management for trunk areas	72
Enabling trunking	73
Disabling F_Port trunking	74
Trunking monitoring	74
Trunking considerations for the Edge switch	74
Trunking considerations for Access Gateway module	77
Upgrade and downgrade considerations for Trunking in Access Gateway mode	77
Adaptive Networking on Access Gateway	78
Upgrade and downgrade considerations with Adaptive Networking in AG mode enabled	79
Adaptive Networking on Access Gateway considerations	79
Per Port NPIV login limit	80
Setting the login limit	80
Considerations for the Brocade 8000	80
SAN Configuration with Access Gateway	83
In this chapter	83
Connectivity of multiple devices overview	83
Direct target attachment	83
Considerations	83
Target aggregation	84
Access Gateway cascading	84
Fabric and Edge switch configuration	85
Verifying the switch mode	85
Enabling NPIV on M-EOS switches	86
Connectivity to Cisco Fabrics	87
Enabling NPIV on a Cisco switch	87
Rejoining Fabric OS switches to a fabric	87
Reverting to a previous configuration	87
Troubleshooting	89

Match case Limit results 1 per page

Access Gateway Administrator’s Guide

53-1001760-01

Troubleshooting

NOTE

If a Fabric OS switch is in AG mode and is also set to McDATA Fabric mode, when that switch is

connected to an M-EOS switch, the Fabric OS switch does not display in the output when you run the

agshow

command.

Failover is not working

Failover disabled on N_Port.

Verify that the failover and failback policies are enabled, as follows:

Enter the

failoverShow

command with the

port_number

operand.

Enter the

failbackShow

command with the

port_number

operand.

Command returns “Failback (or Failover) on N_Port

port_number

supported.”

If it returns, “Failback (or Failover) on N_Port

port_number

is not

supported.” See

“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 is offline, the F_Ports will

disable. Define the preferred secondary N_Ports per F_Port. For

example, if two F_Ports are mapped to a primary N_Port 1, you can

define a secondary N_Port for one of those F_Ports and not define a

secondary N_Port for the other F_Port. F_Ports must have a primary

N_Port mapped before a secondary N_Port can be configured.”

page 45.

Access Gateway is mode

not wanted

Access Gateway must be disabled.

Disable switch using the

switchDisable

command.

Disable Access Gateway mode using

the

modeDisable

command.

Answer yes when prompted; the switch reboots.

Display the switch settings using the

switchShow

command. Verify

that the field

switchMode

displays Fabric OS Native mode.

“Login Rejected by FC

stack” messages on

console may be seen

during F_Port and N_Port

disruptions on Brocade

8000 in AG Mode.

The CNA host is retrying a log in before

the switch has finished precessing a

previous fabric logout (LOGO) attempt.

Working as designed. After the switch has completed LOGO

processing, it will accept another login.

TABLE 10

Troubleshooting (Continued)

Problem

Cause

Solution