HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.2 administrator guide (5697-0 - Page 388

Displaying EX_Port trunking information 1. Log in as an admin and connect to the switch. 2. Enter the switchShow command to display trunking information for the EX_Ports. fcr_switch:admin_06> switchshow The following is an example of a master EX_Port and a slave EX_Port displayed in switchShow: Index Slot Port Address Media Speed State 16 2 0 ee1000 id N4 No_Light 17 2 1 ee1100 id N4 Online EX_Port 18 2 2 ee1200 id N4 Online EX_Port (fabric id = 2 )(Trunk master) 19 2 3 ee1300 id N4 No_Light 20 2 4 ee1400 id N4 Online EX_Port 21 2 5 ee1500 id N4 Online EX_Port 22 2 6 ee1600 id N4 Online EX_Port 23 2 7 ee1700 id N4 Online EX_Port (fabric id = 2 )(Trunk master) LSAN zone configuration (Trunk port, master is Slot 2 Port 2 ) 10:00:00:05:1e:35:bb:32 "MtOlympus_82" (Trunk port, master is Slot 2 Port 7 ) (Trunk port, master is Slot 2 Port 7 ) (Trunk port, master is Slot 2 Port 7 ) 10:00:00:60:69:80:1d:bc "MtOlympus_72" An LSAN consists of zones in two or more edge or backbone fabrics that contain the same devices. LSANs essentially provide selective device connectivity between fabrics without forcing you to merge those fabrics. FC routers provide multiple mechanisms to manage interfabric device connectivity through extensions to existing switch management interfaces. You can define and manage LSANs using Advanced Zoning. Use of administrative domains with LSAN zones and FCR You can create LSAN zones as a physical fabric administrator or as an individual administrative domain (AD) administrator. The LSAN zone can be part of the root zone database or the AD zone database. FCR harvests the LSAN zones from all administrative domains. If both edge fabrics have the matching LSAN zones and both devices are online, FCR triggers a device import. To support legacy applications, WWNs are reported based on the administrative domain context. As a result, you must not use the network address authority (NAA) field in the WWN to detect an FC Router. LSAN zone enforcement in the local fabric occurs only if the administration domain member list contains both of the devices (local and imported device) specified in the LSAN zone. For more information, see Chapter 7, "Using the FC-FC routing service" on page 367. Zone definition and naming Zones are defined locally on a switch or director. Names and memberships, with the exception of hosts and targets exported from one fabric to another, do not need to be coordinated with other fabrics. For example, in "Edge SANs connected through a backbone fabric" on page 371, when the zones for Edge SAN 1 are defined, you do not need to consider the zones in Edge SAN 2, and vice versa. Zones that contain hosts and targets that are shared between the two fabrics need to be explicitly coordinated. To share devices between any two fabrics, you must create an LSAN zone in both fabrics containing the port WWNs of the devices to be shared. Although an LSAN is managed using the same tools as any other zone on the edge fabric, two behaviors distinguish an LSAN from a conventional zone: • A required naming convention. The name of an LSAN begins with the prefix LSAN_. The LSAN name is case-insensitive; for example, lsan_ is equivalent to LSAN_, Lsan_, and so on. • Members must be identified by their port WWN because port IDs are not necessarily unique across fabrics. The names of the zones need not be explicitly the same, and membership lists of the zones need not be in the same order. NOTE: The LSAN_ prefix must appear at the beginning of the zone name. LSAN zones may not be combined with QoS zones. See "QoS zones" on page 361 for more information about the naming convention for QoS zones. 386 Using the FC-FC routing service