HP StorageWorks 8/40 HP StorageWorks Fabric OS 5.2.x administrator guide (5697 - Page 146
Admin Domains, zones, and zone databases, Admin Domain interaction with Fabric OS features
View all HP StorageWorks 8/40 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 146 highlights
Table 41 Admin Domain interaction with Fabric OS features (continued) Fabric OS feature Admin Domain interaction FCR FDMI FICON iSCSI Management applications Port-Swapping and PID formats RSCN You can create LSAN zones as a physical fabric administrator or as an individual AD administrator. The LSAN zone can be part of the root zone database or the AD zone database. • FCR collects the LSAN zones from all ADs. If both edge fabrics have matching LSAN zones and both devices are online, FCR triggers a device import. • LSAN zone enforcement in the local fabric occurs only if the AD member list contains both of the devices (local and imported device) specified in the LSAN zone. To support legacy applications, WWNs are reported based on the AD context using NAA=5. As a result, you cannot use the NAA=5 field alone in the WWN to detect an FC Router. FDMI operations are allowed only in AD0 and AD255. Admin Domains support FICON. However, you must perform additional steps because FICON management (CUP) requires additional physical control of the ports. You must set up the switch as a physical member of the FICON AD. DCC and SCC policies are supported only in AD0 and AD255, since ACL configurations are supported only in AD0 and AD255. iSCSI operations are supported only in AD0. Management interfaces that access the fabric without a user's credentials continue to get the physical fabric view. Examples include: SNMPV1, Web Tools, Fabric Manager; http access, unzoned management server query, FAL in-band CT requests from FAL Proxy to FAL Target, and FC-CT based management applications (such as Tivoli). Access from applications or hosts using Management Server calls can be controlled using the Management Server ACL support provided by the msConfigure command. Note that this is a switch-specific setting and not a fabric-wide setting. Admin Domain port members are specified in (domain, port) format. Based on the PID format, a (domain, port) member indicates a slot/port in the switch. The (domain, port) member is effectively a member of that AD. If the PID format changes, all (domain, port) AD members with a port index of less than 128 are automatically converted to meet the new PID format. Port swapping has no effect on AD support as port swapping swaps only the area numbers of two ports and Admin Domains are specified using (domain, port) member. For detailed information about configuring the PID format, see "Configuring the PID format" on page 381. Admin Domains do not introduce any RSCN changes to devices or hosts. Refer to the Fabric OS Command Reference Manual for detailed information about the commands. The following sections describe Admin Domain interactions with zones, zone databases, and LSAN zones. Admin Domains, zones, and zone databases Each Admin Domain has its own zone database, with both defined and effective zone configurations and all related zone objects (zones, zone aliases, and zone members). Within an Admin Domain, you can configure zoning only with the devices that are present in that Admin Domain. With a hierarchical zoning model, the name space for each Admin Domain and the root zones are separate; configurations are supported with the same zone object name appearing in the root zone database and different ADs (for example, the same zoneset name in AD1 and AD2). 146 Managing administrative domains