Admin Domain Interactions With Other Fabric Os Features; Table 67 Admin Domain Interaction With Fabric Os Features - HP StoreFabric SN6500B Administrator's Manual

Example of switching to a different Admin Domain context

Admin Domain interactions with other Fabric OS features

The Admin Domain feature provides interaction with other Fabric OS features and across
third-party applications. You can manage Admin Domains with Web Tools as well as the CLI. If the
current Admin Domain owns the switch, you can perform Fabric Watch operations.
Admin Domain interactions do not extend to user session tunneling across switches. A user logged
in to a switch can control only the local switch ports as specified in the Admin Domain.
When the fabric is in secure mode, the following restrictions apply:
•
•
Table 67
Domains.
TABLE 67
Fabric OS feature
ACLs
Advanced Performance
Monitoring (APM)
Configuration upload
and download
Fabric Watch
FC-FC Routing Service
Fabric OS Administrator's Guide
53-1002745-02
You cannot switch to another Admin Domain context from within the shell created by ad
--select. You must first exit the shell, and then issue the ad --select command again.
The following example switches to the AD12 context and back. Note that the prompt changes
to display the Admin Domain.
switch:admin> ad --select 12
switch:AD12:admin> logout
switch:admin>
There is no support for ACL configuration under each Administrative Domain.
ACL configuration commands are allowed only in AD0 and AD255. None of the policy
configurations are validated with AD membership.
lists some of the Fabric OS features and considerations that apply when using Admin
Admin Domain interaction with Fabric OS features
Admin Domain interaction
If no user-defined Admin Domains exist, you can run ACL configuration commands in only
AD0 and AD255. If any user-defined Admin Domains exist, you can run ACL configuration
commands only in AD255.
You cannot use ACL configuration commands or validate ACL policy configurations
against AD membership under each Admin Domain.
All APM-related filter setup and statistics viewing is allowed only if the local switch is part
of the current Admin Domain.
Refer to
Fabric Watch configuration operations are allowed only if the local switch is part of the
current Admin Domain.
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 devices) 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.
SAN management with Admin Domains
"Configuration upload and download in an AD context"
17
on page 460 for details.
457