Configuration of ARSWCpuUsageTest

One of the probable reasons for the poor performance of the target Arista switch is excessive CPU utilization. Administrators should hence continuously track how well the switch utilizes CPU resources, so that abnormal usage patterns can be proactively detected and corrected to ensure peak performance of the switch.

This test helps the administrators to monitor the CPU resource contention in the Arista switch and also helps to sort out the solutions for what caused this contention - resource-hungry user processes, CPU-intensive system processes or low-priority (Nice) jobs?

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify they address of the Arista Switch that is being monitored.

• This test uses SSH commands to pull metrics from the target switch. To run SSH commands, this test first needs to establish an SSH connection with the target switch. To enable the test to establish this connection, specify the port through which SSH connection should be established in the SSH PORT text box.

• This test uses SSH commands to pull out the required metrics. To use these commands, the test first needs to connect to the target storage server via SSH. For running the SSH commands, this test requires the credentials of a user who is authorized to access the target switch via SSH. Specify the login credentials of such a user in the SSH USERNAME and SSH PASSWORD text boxes.

• Confirm the Password by retyping it in the CONFIRM PASSWORD text box.

• Specify the duration (in seconds) for which the SNMP query executed by this test should time out in the TIMEOUT text box. By default, this is set to 10 seconds.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.