Emulex 3.3 Frozen Dessert Maker User Manual


 
The HBAnyware Utility User Manual Page 92
Reserved Indices - Examples
A particular security installation can support the creation of several hundred access groups (ACGs and
ASGs). When you create each new access group, you allocate some number of 'indices' to the client
system of the new ASG. This number reflects the number of subsequent 'child' ASGs that you can
subsequently create at the new client's system.
If zero indices are reserved, you cannot create any lower-level ASG under the client of the new
ASG. Thus, if you want to implement a multi-tiered security architecture consisting of many
ASGs, and you want to create them all from the Master Security Client (MSC), zero indices
would be allocated to each of the new ASGs client platforms when they are created.
If you create an ASG, and you reserve 25 indices for the new ASG client platform, a child ASG
created by this platform will have a maximum of only 24 indices available to be reserved (one is
taken by the creation of the child ASG itself). This continues down the ASG hierarchy as each
lower level ASG is created.
When you create an ASG from the MSC, a maximum of 50 indices (or less if fewer are available)
can be reserved. For all other clients, the maximum depends on how many indices were
reserved to that client when its ASG was created, and on how many it has subsequently
allocated to its ASGs.
Adding a Server to an ASG
To add a server to an ASG:
1. Click the Access Sub-Group tab (see Figure 45 on page 91).
2. The name of the ASG appears in the Access Sub-Groups tree. From the Available Servers list,
select the servers to add to the ASG.
3. Click the left arrow to move the servers to the Access Sub-Group Servers list.
4. Click OK (or Apply) to update servers, adding them to the ASG. The new client can remotely
manage the HBAs on those servers using the HBAnyware utility.
Deleting an ASG
Only a leaf node ASG may be deleted (i.e. not ASGs underneath it in the tree). If an ASG has at least
one child ASG, you must delete those child ASGs first.
To delete an ASG:
1. From the Access Sub-Group tree, select the leaf node ASG you wish to delete.
2. Click the Delete button. A dialog box appears warning you that if you continue the access sub-
group will be deleted.
3. Click Yes. This operation is immediate. There is no need to click OK (or Apply).
Note: TCP/IP accessed servers will appear in the Available Servers list even though the
ASG client system may not have discovered them yet. These servers can still be
added to the Access Sub-Group Servers list.