
Driver for Linux -Troubleshooting Section Page 101
Non-Hierarchical and Hierarchical ASG
It is possible from a higher-level client (such as 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 (see Figure 60).
Figure 60: Non-hierarchical ASG Scenario
System E is part of ASG 1, but has been made a client of ASG 2, and both of the servers in ASG 2 are
not part of ASG 1. You could not create this ASG on system A, but you could on the MSC (or on a parent
client) because it can access systems F and G. Although not shown in the picture, it is also possible to
make system A a server in ASG 2, creating a case where system A and system E are both clients and
servers to/of each other.
While the Security Configurator will allow you to set up ASGs this way, it is best not to create a topology
like this as it can lead to confusion. The best way is to set up the ASG on the MSC (or a higher-level
parent) where the clients and servers do not cross over into other ASGs. Then set up ASGs on clients of
those ASGs in the same manner, keeping the topology hierarchical (see Figure 61)
Kommentare zu diesen Handbüchern