HP Fabric OS v7.0.1, Administrator'S Manual

Page: 396 / 584

358 Fabric OS Administrator’s Guide
53-1002446-01
SAN management with Admin Domains
17
Validating an Admin Domain member list
You can validate the device and switch member list. You can list non-existing or offline Admin
Domain members. You can also identify misconfigurations of the Admin Domain.
The Admin Domain validation process is not applicable for AD0, because AD0 implicitly contains all
unassigned online switches and their devices.
1. Connect to the switch and log in using an account with admin permissions.
2. Switch to the AD255 context, if you are not already in that context.
ad --select 255
3. Enter the ad
--
validate command.
ad --validate ad_id -m mode
If you do not specify any parameters, the entire AD database (transaction buffer, defined
configuration, and effective configuration) is displayed.
If you do not specify an Admin Domain, information about all existing Admin Domains is
displayed.
The -m mode option can be used with the following values:
•
0 to display the Admin Domain configuration in the current transaction buffer.
•
1 to display the Admin Domain configuration stored in the persistent memory (defined
configuration).
•
2 to display the currently enforced Admin Domain configuration (effective configuration).
Example of validating the member list of Admin Domain 10 in the current transaction buffer
switch:AD255:admin> ad --validate 10 –m 0
Current AD Number: 255 AD Name: AD255
Transaction buffer configuration:
---------------------------------
AD Number: 2
AD Name: ad2 State: Active
Switch port members: 1,1; 1,3; 2,5+; 3,6;
----------------------------
* - Member does not exist
+ - Member is AD Unaware
SAN management with Admin Domains
This section is for both users and administrators and describes how Admin Domains affect
commands and other Fabric OS features. If you are a physical fabric administrator and you want to
create, modify, or otherwise manage Admin Domains, refer to
“Admin Domain management for
physical fabric administrators” on page 346.
The Admin Domain looks like a virtual switch or fabric to a user. However, based on the user role
and type (User_ID), users are presented with only their relevant AD-based views (refer to
Figure 51
on page 338 and Figure 52 on page 338). Any devices and switch ports that are not defined as
part of the Admin Domain are not shown and are not available to that AD user.
Each Admin Domain can also have its own zone configurations (defined and effective) with zones
and aliases under them.