Performance Guidelines

To ensure the best performance in your N1 System Manager environment, adhere to the following guidelines and recommendations:

• Before you run discovery, tune the N1 System Manager for the number of provisionable servers as described in To Increase the N1 System Manager Performance.

• Ensure that each OS distribution creation job has finished before starting another one. Creating an OS distribution is a very CPU and disk-intensive operation. The provisioning of operating systems, firmware, and OS management agents on large numbers of monitored servers is also very CPU and disk intensive. Limit the number of simultaneous jobs of this type to prevent performance issues.

• Limit the total number of jobs executing on the system to fewer than 11 jobs. You can determine the total number of running jobs by typing the command show job state running at the command-line interface or in the n1sh shell.

• Always run the non-interactive n1sh shell commands in the foreground.

• Maximize the number of servers per group, and run operations against groups instead of against a large number of individual servers. Running operations on a group minimizes the number of groups you need to manage and minimizes the number of jobs you need to submit in order to accomplish a given task.

• Before performing operations targeted at the operating system level such as remote command execution and operating system update installation, ensure that the OS Health of the servers is not Unknown.

• Before performing operations targeted at the service processor (SP) such as a firmware update, ensure that the Hardware Health of the servers is not Unknown.

• Before performing operations on the provisionable servers, ensure that the network connectivity state for the required interface on targeted servers is not Unreachable.

The next section provides the procedure for tuning your N1 System Manager system.