HP Systems Insight Manager 5.2 Update 2 Technical Reference Guide

NOTE: Any additional changes to the system collection do not affect the system group or authorizations
unless updated by one of the following options.
The content of the system group is updated with the current contents of the collection when:
• Another authorization is created using the collection
• An authorization using the system group is updated
• Using mxngroup from the CLI
In the first two cases, the current contents of the collection are displayed for verification.
When deleting authorizations, a system group no longer used in any authorization is deleted.
Managing system groups from the CLI using mxngroup
System groups can be created directly using the mxngroup command. When system groups are created
using the CLI, a top-level collection is created and named after the system collection with three digits appended,
usually 001. The collection contains the systems in the system group only when the system group is first
added. Later modifications are not reflected in the collection.
NOTE: Any additional changes to the system group or collection do not affect the other, unless updated
by one of the following options or by using the GUI as previously described. This means that changes to the
collection do not affect authorizations, and changes to the system group do not affect the collection view
unless specifically updated.
The contents of the system group can be updated with the current contents of the collection by using the -u
parameter for mxngroup:
mxngroup –m –g <groupname> -u
CAUTION: This command does not display the systems in the collection. To display the updated contents
of the system group, use mxngroup –lm –g <groupname>.
CAUTION: Setting up a periodic task to dynamically update a system group is not recommended. A
collection based on system attributes can be compromised, adversely affecting authorizations in HP Systems
Insight Manager (HP SIM) if those attributes are based on a nonsecure protocol (such as SNMP) or are
maintained by a user with user rights. Additionally, the collection itself can be modified by a user with user
rights, which also adversely affects authorizations.
When deleting authorizations, a system group no longer used in any authorizations is deleted.
Related procedures
• Creating new authorizations
• Updating authorizations
Related procedures
▲ Users and authorizations
156 Users and authorizations