Configuration of CtxSDXXenCPUTest

This test reports the number of CPU cores the SDX appliance supports and the average CPU usage of the appliance across all the cores. In the process, the test warns administrators of a probable CPU contention on the appliance and prompts speedy action, so that performance does not suffer.

The default parameters associated with this test are as follows:

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

• In the HOST text box, the host for which the test is to be configured has to be specified.

• To monitor a NetScaler SDX device, the eG agent should be configured with the credentials of a user with read-only privileges to the target device. Specify the credentials of such a user in the SDX USERNAME and SDX PASSWORD text boxes.

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

• The eG agent collects performance metrics by invoking NITRO (NetScaler Interface Through Restful interfaces and Objects) APIs on the target NetScaler SDX device. Typically, the NITRO APIs can be invoked through the HTTP or the HTTPS mode. By default, the eG agent invokes the NITRO APIs using the HTTPS mode. This is why, the SSL flag is set to Yes by default. If the target NetScaler SDX device is not SSL-enabled, then the NITRO APIs can be accessed through the HTTP mode only. In this case, set the SSL flag to No.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box 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 default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.