Device Mapping - HP StoreFabric SN6500B Administrator's Manual

Use the following steps to remove the static mapping:
1. Connect to the switch and log in using an account assigned to the admin role.
2. Perform one of the following steps to remove mapping:
Considerations for using F_Port Static Mapping with other AG features and
policies
Consider the following when using F_Port Static Mapping with Access Gateway features and
policies:
•
•
•
•
•
•
•
Upgrade and downgrade considerations
•
•
Access Gateway Administrator's Guide
53-1002743-01
Once F_Port Static Mapping is enabled, the F_Port and all attached devices log out of the
previously mapped N_Port and log in to the new N_Port.
-
Map the F_Port to a different N_Port using the ag --staticadd.
-
Enter the following command to remove F_Port mapping entirely:
ag --staticdel "N-Port" "F-Port(s)"
F_Port Static Mapping is not supported on the Brocade 8000 switch.
F_Port Static Mapping functions with cascaded Access Gateway configurations.
Failover, failback, and preferred secondary N_Port settings are disabled for F_Ports that are
statically mapped.
Statically mapped ports are blocked from using the Automatic Port Configuration (APC) and
Advanced Device Security (ADS) policies. You cannot enable the APC policy until all 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 settings that other F_Ports
have when mapped to an N_Port in that port group. To remap to an N_Port with PG policy
attributes, use the ag --staticdel command to remove the static mapping, and then remap to
another N_Port using the ag --mapadd command.
F_Port Static Mapping will not work with Device Load Balancing. Because F_Port Static
Mapping forces the F_Port to stick with a specific N_Port, NPIV devices that log in to the F_Port
cannot redistribute themselves among N_Ports in the port group.
F_Port Static Mapping will not work with port trunking. If an F_Port is statically mapped to an
N_Port and trunking is enabled, the F_Port goes offline. If port trunking is enabled for an
F_Port already, you will be blocked from configuring static mapping for the F_Port.
All static mappings will be maintained when upgrading to the latest Fabric OS version.
When downgrading, you must remove all static mappings or downgrade will not be allowed.
Access Gateway mapping
2
21