You are here

Cisco UCS - Chassis

Requires Opsview Cloud

This Host Template is part of the Cisco Ucs Monitoring Opspack

check_circle
Opsview Supported

Host Template: Infrastructure - Cisco UCS - Chassis

Monitor your Cisco UCS Chassis with metrics for overall health, usage information and a detailed summary of faults.

This Host Template includes the following Service Checks:

Service Check Name Description Default Thresholds (Warning, Critical) UOM
UCS - Chassis - Admin State Admin state of the Chassis N/A N/A
UCS - Chassis - Availability Availability of the Chassis N/A N/A
UCS - Chassis - Blades Information on the Blade Servers connected to this Chassis N/A N/A
UCS - Chassis - Config State Config state of the Chassis N/A N/A
UCS - Chassis - Connection Path Connection path of the Chassis N/A N/A
UCS - Chassis - Connection State Connection state of the Chassis N/A N/A
UCS - Chassis - Faults Fault information for the Chassis chassis_critical_faults=,0
chassis_major_faults=,0
chassis_minor_faults=0,
chassis_warning_faults=0,
chassis_info_faults=,
chassis_cleared_faults=,
N/A
UCS - Chassis - IO Cards Information on the IO Cards on this Chassis N/A N/A
UCS - Chassis - Managing Instance Managing Instance of the Chassis N/A N/A
UCS - Chassis - Operability Operability of the Chassis N/A N/A
UCS - Chassis - Overall State Overall state of the Chassis N/A N/A
UCS - Chassis - Power State Power state of the Chassis N/A N/A
UCS - Chassis - Presence Presence of the Chassis N/A N/A
UCS - Chassis - PSUs PSU stats for the Chassis N/A N/A
UCS - Chassis - Redundancy Qualifier Redundancy qualifier of the Chassis N/A N/A
UCS - Chassis - Redundancy State Redundancy state of the Chassis N/A N/A
UCS - Chassis - Revision Revision number of the Chassis N/A N/A
UCS - Chassis - Thermal State Thermal state of the Chassis N/A N/A

Usage Instructions

Step 1: Add this Host Template

Add the Infrastructure - Cisco UCS - Chassis Host Template to your Opsview Monitor host. If the resource you're monitoring has no hostname or public IP, then open the Advanced settings pane and change Host Check Command to Always assumed to be UP.

For more information, refer to Opsview Knowledge Center - Adding Host Templates to Hosts.

Step 2: Add and configure variables required for this Host Template

The Service Checks in this Host Template use the following variables, and they will be added to your Opsview Monitor instance when you import the Opspack:

UCS_CREDENTIALS

The Value is not used and therefore can be set to anything. Override the arguments with your credentials.

Parameter Position in Variable Name Description
--api-server-url Arg1 UCS API Server URL The server URL for your Cisco UCS Manager or CIMC Supervisor
--username Arg2 UCS Username The username for your Cisco UCS user
--password Arg3 UCS Password The password for your Cisco UCS user

UCS_CHASSIS_NAME

Parameter Position in Variable Name Description
--chassis-name Value UCS Chassis Name Name of the Chassis to monitor

UCS_FAULT_SETTINGS

The Value is not used and therefore can be set to anything. Override the arguments with your settings. The fault severity must be one of; 'critical', 'major', 'minor', 'warning', 'info', 'cleared' (default: 'major'). The fault limit, limits the number of faults displayed (default: '10'). Leave this blank to display all faults.

Parameter Position in Variable Name Description
--fault-severity Arg1 UCS Fault Severity The minimum severity level of faults to display
--fault-limit Arg2 UCS Fault Limit The maximum number of faults to display

For more information, refer to Opsview Knowledge Center - Adding Variables to Hosts.

For mode-specific help, run the plugin with the -h -m <mode> flags. This will list the required and optional Variable Arguments for that mode. The appropriate mode for each Service Check is listed here:

Service Check Name Mode
UCS - Chassis - Admin State UCS.Chassis.Admin
UCS - Chassis - Availability UCS.Chassis.Availability
UCS - Chassis - Blades UCS.Chassis.Blades
UCS - Chassis - Config State UCS.Chassis.Config
UCS - Chassis - Connection Path UCS.Chassis.Conn.Path
UCS - Chassis - Connection State UCS.Chassis.Conn.State
UCS - Chassis - Faults UCS.Chassis.Faults
UCS - Chassis - IO Cards UCS.Chassis.IO.Cards
UCS - Chassis - Managing Instance UCS.Chassis.Managing.Inst
UCS - Chassis - Operability UCS.Chassis.Operability
UCS - Chassis - Overall State UCS.Chassis.Overall
UCS - Chassis - Power State UCS.Chassis.Power
UCS - Chassis - Presence UCS.Chassis.Presence
UCS - Chassis - PSUs UCS.Chassis.PSUs
UCS - Chassis - Redundancy Qualifier UCS.Chassis.Redundancy.Qual
UCS - Chassis - Redundancy State UCS.Chassis.Redundancy.State
UCS - Chassis - Revision UCS.Chassis.Revision
UCS - Chassis - Thermal State UCS.Chassis.Thermal

SSL Certificates

Additionally, if ssl verification is required, you can use the following variable to pass in your SSL certificates for use when connecting to the service provider to gather metrics:

UCS_CERTIFICATES

The Value is not used and therefore can be set to anything. Override the arguments with your certificates.

Parameter Position in Variable Name Description
--ca-path Arg1 CA Certificate Path Path to the CA Certificate. Optional, only required if server verification is needed
--client-cert Arg2 Client Certificate Path Path to the Client Certificate. Optional, only required if client verification is needed
--client-key Arg3 Client Key Path Path to the Client Key. Optional, only required if client verification is needed

Step 3: Apply changes and the system will now be monitored

Cisco UCS Chassis Output