Adding A Resource As A Child Of A Group - Extreme Networks EPICenter Reference Manual

The Grouping Manager
NOTE
You can only destroy resources whose source is "Manual" (except for the predefined groups) and the root groups of
imported resources. You cannot destroy the predefined groups, system-defined resources (devices, device groups, or
ports) whose source is EPICenter, or individual imported resources (where the source is a file, LDAP database, etc.).
If you select a resource you cannot delete, the Destroy button is not available.
To delete a user-defined resource do the following:
1 Select the resource in the Component Tree.
2 Click the Destroy button on the toolbar.
A confirmation dialog is displayed. Click OK to confirm that you want to delete this resource.
If you delete a group, any orphaned children of the group (resources that are not members of any other
group) are also deleted.
If you delete a Host or User, all relationships to other resources are also deleted.
To remove a resource as a child of a group, use the Remove function, see
from a Group,"
not delete the resource from the database.

Adding a Resource as a Child of a Group

NOTE
You cannot add Resources as a Child of a Group for Custom Applications.
A group's children are individual resources or subordinate groups that are manipulated or managed
together. A resource is placed into a group as it is created— either the root-level group, or the group
that was selected when it was created. However, because a resource can be a member of multiple
groups, you may wish to add an existing resource to an additional group, or move it to a different
group. To add a resource to a group, you select the resource from a list of the resources that are
currently defined in the EPICenter database.
You can add individual resources as children of a group, or you can add groups as children. You
cannot add an ancestor group as a child of one of its subordinate groups. You cannot have subordinate
groups of Applications below the Custom Applications group.
When you add a group as a child of another group, all members of the sub-group (its children) are
considered members of the higher level (ancestor) group. As membership in the sub-group changes, so
does the membership in the higher level (ancestor) group. This can have important effects when a
group is used by another EPICenter module. For example, suppose you create group "A" that contains
two groups of hosts "HostsA" and "HostsB", and then use group A in defining access list policies
through the Policy Manager. The Policy Manager generates access list rules for traffic related to all the
hosts in groups HostsA and HostsB. If you subsequently change the membership of HostsB, and auto-
configuration of policies is enabled in the Policy Manager, the QoS rules that define the access lists are
automatically recomputed and reconfigured. (See the
information on this optional applet).
230
on page 232. This just removes the parent-child relationship with the group, but does
"Removing A Child Resource
Chapter 18 "Using the Policy Manager"for more
EPICenter Reference Guide