Dell EMC OpenManage Command Line Interface Guide Version 9.1

PDF

Scripting And Comparing Using CLI

The Server Administrator CLI allows administrators to write batch programs for the operating system. For an enterprise with many systems, an administrator could write a configuration script that specifies the warning thresholds for each major component of a system and also specifies a set of actions that the administrator wants each system to take in case of a warning or failure event. In most critical cases, the administrator could write a script so that the system shuts down to prevent damage. The administrator could then distribute and execute the script to many managed systems at the same time. Such a scenario facilitates configuring any number of new systems acquired by a company and makes implementation of new system administration policies easier across many existing systems that require re-configuration.

A similar scenario is used to populate a large number of newly acquired systems with detailed asset information. Much of the information are the same, such as the manufacturer or lessor of the system, whether support for the system is outsourced, name of the company providing insurance for the system, method of depreciation, and so on. Any variable that is common to all systems is scripted, sent to all managed systems, and executed. Asset information that is unique to a system is scripted as a group and sent to that managed node for execution. For example, a script could specify values for all unique variables such as the owner, primary user phone number, asset tag, and so on. Scripts to populate unique values would set all unique variables at once rather than one by one through the system's command line.

In many cases, the CLI allows a user with a very well-defined task in mind to retrieve information about the system rapidly. If a user wants to review a comprehensive summary of all system components and save that summary information to a file for comparison with later system states, the CLI is ideal.

Using CLI commands, administrators can write batch programs or scripts to execute at specific times. When these programs are executed, they can capture reports on components of interest, such as fan RPMs during periods of highest system usage compared with the same measurements at times of lowest system usage. Command results are routed to a file for later analysis. Reports can help administrators gain information that are used to adjust usage patterns, to justify purchasing new system resources, or to focus on the health of a problem component.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\