Owner's Manual

• The summary includes the number of impacted devices, number of impacted groups, and number of impacted

policies.

• All subgroups under the specified group path are counted in the summary whether they will be deleted from

OMPC or not. (It is possible that a subgroup could be removed from the specified group path, but not be deleted

from OMPC due to a reference from another parent group.)

• All devices and subgroups are counted in the summary (not only the direct children of a specified group).

• Any policies that you added to the impacted devices are not counted in the summary, because the device will

not be deleted from OMPC, and these policies will remain on these devices.

Example Summary:

– Number of impacted devices: 5

– Number of impacted subgroups: 10

– Number of impacted policies: 3

You can delete a chassis as a group with the delete_group command. In this case, after successful removal, the

chassis will be kept on the Devices page as a device, but will no longer appear as a group if there is no other group

containing this chassis (if there is no connection between the chassis and the blades inside it).

update_group

Usage:

ompc_cli update_group [-description <description>] [-group_type <DC|ROOM|AISLE|

CUSTOM >] [-capacity <capacity>] [-total_power_capacity <power_capacity>]

GROUP_PATH [new_group_name]

The update_group command updates the properties of an existing group identified by GROUP_PATH. The –capacity

and –total_power_capacity options are valid only when the group to be updated is a rack. The –group_type

of a rack cannot be updated, and no other type of group can be updated to be a rack.

If new_group_name is provided, the CLI updates the name of the group to the new name. The group can belong to

another group. If this is the case, the rename operation may fail because of the name confliction.

The chassis can be regarded as group, so the CLI allows updates to the properties of the chassis through the

update_group command. You can only update the chassis’ description and name through the update_group command.

You cannot update other types of groups to be a chassis.

The name must be unique across devices and groups under the same parent group.

You cannot use “/” as GROUP_PATH in the update_group command.

add_device_to_group

Usage:

ompc_cli add_device_to_group [-slot <slot_num>] [-service_tag <stag>]

[<device_name >] GROUP_PATH

The add_device_to_group command adds a device to a group. If a device is added to a rack, the slot_num option is

used to specify into which slot the device will be added. If the value of the slot is -1, the system will choose a slot

automatically. When adding PDU/UPS, if you do not provide a slot option, the PDU/UPS will be attached to the rack. For

adding a server or chassis to rack,

-slot is allowed (when not provided, the system will choose a slot automatically). If

adding a server or chassis to other groups, -slot is not allowed (an error will display).

Slots start from 1 (0 is an invalid slot number).