
Security Configurator Situations - Access Control Groups (ACG)
Table 18: Access Control Groups Situations
Situation | Resolution |
|
|
|
|
All servers are not displayed. When I run | Make sure all of the systems are connected to the FC network |
the Security Configurator on the Master | and are online when you start the Configurator. Discovery of |
Security Client (MSC), I do not see all of the | the systems is done only once, at startup. Unlike the |
systems in available servers or ACG Servers | HBAnyware utility, there is no Rediscover Devices button. |
lists. When I run the Security Configurator on | Therefore, the Security Configurator must be restarted to |
a | rediscover new systems. |
should see in the ACG Servers list. |
|
|
|
Cannot add or remove a server. The | This is normal. You can modify the ACG for your system only |
Security Configurator shows only a list of the | on the MSC or on a parent client system. |
systems in this system's ACG. I cannot add or |
|
remove systems from the ACG. |
|
|
|
HBAnyware utility shows | The HBAnyware utility discovers unsecured servers as well |
Servers. The HBAnyware utility shows | as servers that are part of its ACG. The servers you see that |
servers that are part of the ACG and that are | are not part of the ACG are unsecured. They will be |
not part of the ACG. | discovered by any system running the HBAnyware utility on |
| the same FC fabric. |
|
|
Security Configuration Situations - Access Sub-Groups (ASG)
Table 19: HBAnyware Security Configurator - Access
Situation | Resolution |
|
|
|
|
ASG Appears to Be | See |
possible from a | for a discussion and a resolution to this situation. |
the MSC) to create an ASG 1 with system A |
|
as the client and systems B, C, D, and E as |
|
servers. Then create an ASG 2 with system E |
|
as the client, but with systems F and G as |
|
servers even though F and G are not part of |
|
ASG 1. This makes the topology non- |
|
hierarchical. |
|
|
|
Cannot add or remove a server. | When all of the systems in an ACG are running on a single |
| fabric, they are all available to be added to any ASG. |
| However, if the client is connected to more than one fabric, |
| it is possible that not all of the servers in the client's ACG |
| are physically accessible by a chosen client for an ASG. In |
| this case, those servers are not available to be added to |
| that ASG. |
| If you add a system to an ASG as a server, and then make |
| the system a client to a child ASG, you cannot remove it |
| from the ACG it belongs to as a server until you delete the |
| ASG to which it is a client. |
| Before you delete a server from an ASG, you must first |
| remove the server from any lower level ASGs to which it |
| belongs. |
|
|
The HBAnyware Utility User Manual | Page 143 |