Filter
Top Products
Access Gateway default port mapping (Continued)TABLE 7
Brocade Model Total Ports F_Ports N_Ports Default port mapping
6548 28 1–16 0, 17–27 1, 13 mapped to 0
2, 14 mapped to 17
3, 15 mapped to 18
4, 16 mapped to 19
5 mapped to 20
6 mapped to 21
7 mapped to 22
8 mapped to 23
9 mapped to 24
10 mapped to 25
11 mapped to 26
12 mapped to 27
Considerations for initiator and target ports
The following connections are possible for the Fibre Channel Protocol (FCP) initiator (host) and target
ports through AG:
• All F_Ports connect to all initiator ports.
• All F_Ports connect to all target ports.
• Some F_Ports connect to initiator ports and some F_Ports connect to target ports.
For the last case, communication between initiator and target ports is not supported if both are mapped
to the same N_Port. Therefore, follow these recommendations for initiator and target port mapping:
• If connecting a host and target port to the same AG, you should map them to separate N_Ports and
connect those N_Ports to the same fabric.
• Use separate port groups for initiator and target ports.
• When configuring secondary port mapping for failover and failback situations, make sure that initiator
and target F_Ports will not fail over or fail back to the same N_Port.
Adding F_Ports to an N_Port
You can modify the default port mapping by adding F_Ports to an N_Port. Adding an F_Port to an
N_Port routes that traffic to and from the fabric through the specified N_Port.
You can assign an F_Port to only one primary N_Port at a time. If the F_Port is already assigned to an
N_Port, you must first remove it from the N_Port before you can add it to a different N_Port.
Use the following steps to add an F_Port to an N_Port.
1. Connect to the switch and log in using an account assigned to the admin role.
2. Enter the ag command with the --mapadd n_portnumber f_port1;f_port2;... option to add the list of
F_Ports to the N_Port.
Considerations for initiator and target ports
Access Gateway Administrator's Guide 35
53-1003126-02