|
Default Parameters for UCSChassisTest
By running periodic health checks on each chassis supported by a Cisco UCS Manager, you can promptly identify the following:
- The chassis that is currently in an abnormal operational state;
- The insufficiently licensed chassis;
- Empty/missing chassis;
- The chassis that is experiencing serious power failures;
- The chassis with fans that are in a critical thermal state;
- The chassis that is handling unusually high input and output power.
This page depicts the default parameters that need to be configured for the UCSChassisTest.
By default, in most environments, Cisco UCS Manager listens on port 80 (if not SSL-enabled) or on port 443 (if SSL-enabled) only. This implies that while monitoring Cisco UCS Manager, the eG agent, by default, connects to port 80 or 443, depending upon the SSL-enabled status of Cisco UCS Manager - i.e., if Cisco UCS Manager is not SSL-enabled (i.e., if the SSL flag above is set to No), then the eG agent connects to Cisco UCS Manager using port 80 by default, and if Cisco UCS Manager is SSL-enabled (i.e., if the SSL flag is set to Yes), then the agent-Cisco UCS Manager communication occurs via port 443 by default. Accordingly, the WEBPORT parameter is set to default by default.
In some environments however, the default ports 80 or 443 might not apply. In such a case, against the WEBPORT parameter, you can specify the exact port at which the Cisco UCS Manager in your environment listens, so that the eG agent communicates with that port for collecting metrics from the Cisco UCS Manager.
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.
|