Dell PowerConnect Brocade M6505 Brocade 7.1.0 Access Gateway Administrator's G - Page 35

Access Gateway mapping

Get Dell PowerConnect Brocade M6505 PDF manuals and user guides View all Dell PowerConnect Brocade M6505 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 35 highlights

Access Gateway mapping 2 TABLE 5 State Lock_Ref Testing Offline Online Port state description (Continued) Description Locking to the reference signal Running diagnostics Connection not established (only for virtual ports) Port is up and running Access Gateway mapping When operating in AG mode, you must specify pre-provisioned routes that AG will use to direct traffic from the devices (hosts or targets) on its F_Ports to the ports connected to the fabric using its N_Ports. This is unlike Native switch mode where the switch itself determines the best path between its F_Ports. This process of pre-provisioning routes in AG mode is called "mapping." During mapping, device World Wide Names (WWNs) or F_Ports are assigned to N_Ports and N_Port groups on the switch running in AG mode. Mapping ensures that a device logging in to the switch will always connect to the fabric through a specific N_Port or N_Port group. Two types of mapping are available: • Port mapping A specific 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 specific N_Ports. Device mapping allows a virtual port to access its destination device regardless of the F_Port where the device resides. Device mapping also allows multiple virtual ports on a single physical machine to access multiple destinations residing in different fabrics. Device mapping is optional and should be added on top of existing port maps. Port mapping must exist at all times. Access Gateway Administrator's Guide 15 53-1002743-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
Access Gateway Administrator’s Guide
15
53-1002743-01
Access Gateway mapping
2
Access Gateway mapping
When operating in AG mode, you must specify pre-provisioned routes that AG will use to direct
traffic from the devices (hosts or targets) on its F_Ports to the ports connected to the fabric using
its N_Ports. This is unlike Native switch mode where the switch itself determines the best path
between its F_Ports. This process of pre-provisioning routes in AG mode is called “mapping.”
During mapping, device World Wide Names (WWNs) or F_Ports are assigned to N_Ports and N_Port
groups on the switch running in AG mode. Mapping ensures that a device logging in to the switch
will always connect to the fabric through a specific N_Port or N_Port group. Two types of mapping
are available:
•
Port mapping
A specific 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 specific N_Ports.
Device mapping allows a virtual port to access its destination device regardless of the F_Port
where the device resides. Device mapping also allows multiple virtual ports on a single
physical machine to access multiple destinations residing in different fabrics.
Device mapping is optional and should be added on top of existing port maps. Port mapping must
exist at all times.
Lock_Ref
Locking to the reference signal
Testing
Running diagnostics
Offline
Connection not established (only for virtual ports)
Online
Port is up and running
TABLE 5
Port state description (Continued)
State
Description