Nimsoft Monitor cisco ucs...
Transcript of Nimsoft Monitor cisco ucs...
cisco_ucs Guide v1.5 series
Nimsoft® Monitor™
Legal Notices Copyright © 2012, CA. All rights reserved.
Warranty
The material contained in this document is provided "as is," and is subject to being changed, without notice, in future editions. Further, to the maximum extent permitted by applicable law, Nimsoft LLC disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Nimsoft LLC shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein. Should Nimsoft LLC and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control.
Technology Licenses
The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license.
No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Nimsoft LLC as governed by United States and international copyright laws.
Restricted Rights Legend
If software is for use in the performance of a U.S. Government prime contract or subcontract, Software is delivered and licensed as "Commercial computer software" as defined in DFAR 252.227-7014 (June 1995), or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in FAR 52.227-19 (June 1987) or any equivalent agency regulation or contract clause. Use, duplication or disclosure of Software is subject to Nimsoft LLC’s standard commercial license terms, and non-DOD Departments and Agencies of the U.S. Government will receive no greater than Restricted Rights as defined in FAR 52.227-19(c)(1-2) (June 1987). U.S. Government users will receive no greater than Limited Rights as defined in FAR 52.227-14 (June 1987) or DFAR 252.227-7015 (b)(2) (November 1995), as applicable in any technical data.
Trademarks
Nimsoft is a trademark of CA.
Adobe®, Acrobat®, Acrobat Reader®, and Acrobat Exchange® are registered trademarks of Adobe Systems Incorporated.
Intel® and Pentium® are U.S. registered trademarks of Intel Corporation.
Java(TM) is a U.S. trademark of Sun Microsystems, Inc.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Netscape(TM) is a U.S. trademark of Netscape Communications Corporation.
Oracle® is a U.S. registered trademark of Oracle Corporation, Redwood City, California.
UNIX® is a registered trademark of the Open Group.
ITIL® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.
All other trademarks, trade names, service marks and logos referenced herein belong to their respective companies.
Contact Nimsoft
For your convenience, Nimsoft provides a single site where you can access information about Nimsoft products.
At http://support.nimsoft.com/, you can access the following:
■ Online and telephone contact information for technical assistance and customer services
■ Information about user communities and forums
■ Product and documentation downloads
■ Nimsoft Support policies and guidelines
■ Other helpful resources appropriate for your product
Provide Feedback
If you have comments or questions about Nimsoft product documentation, you can send a message to [email protected].
Contents 5
Contents
Chapter 1: cisco_ucs 1.5 7
cisco_ucs Overview ...................................................................................................................................................... 7
Requirements ............................................................................................................................................................... 8
Installation Notes ......................................................................................................................................................... 8
Chapter 2: cisco_ucs configuration 9
General tab ................................................................................................................................................................... 9
Advanced tab ............................................................................................................................................................. 10
Creating a New Group ................................................................................................................................................ 12
Creating a Host Profile ............................................................................................................................................... 13
Appendix A: Mapping the Fault Severity 17
Working with Monitors .............................................................................................................................................. 17
Editing Monitor Properties ................................................................................................................................. 18
Equipment .................................................................................................................................................................. 21
Chassis Interface Card ......................................................................................................................................... 21
Fabric Interconnects............................................................................................................................................ 23
Rack Mounts ....................................................................................................................................................... 24
Viewing History .......................................................................................................................................................... 25
Faults .......................................................................................................................................................................... 26
Pools ........................................................................................................................................................................... 27
UCS Service Profiles .................................................................................................................................................... 28
Importing the threshold policies into template ......................................................................................................... 30
Configuring Alarms and QoS ...................................................................................................................................... 31
Configuring a QoS................................................................................................................................................ 32
cisco_ucs QoS Metrics ......................................................................................................................................... 32
Using Templates ......................................................................................................................................................... 33
Adding monitors to a template ........................................................................................................................... 34
Wildcard or Fixed monitor templates ................................................................................................................ 35
AutoConfiguration ............................................................................................................................................... 36
Message Pool ............................................................................................................................................................. 39
Create new message ........................................................................................................................................... 40
Chapter 3: cisco_ucs Metrics 41
Chapter 1: cisco_ucs 1.5 7
Chapter 1: cisco_ucs 1.5
This description applies to cisco_ucs probe version 1.4.
This section contains the following topics:
cisco_ucs Overview (see page 7) Documentation Changes (see page 8) Requirements (see page 8) Installation Notes (see page 8)
cisco_ucs Overview
The Nimsoft cisco_ucs probe is a tool for managing the health and performance of your Unified Computing System (UCS).
The Cisco Unified Computing System is a next-generation data center platform that unites computing, networking, storage access, and virtualization into a cohesive system designed to reduce total cost of ownership (TCO) and increase business agility.
Requirements
8 cisco_ucs Guide
Documentation Changes
This table describes the version history for this document.
Version Date What's New?
1.5 September 2012
Added support for UCS Manager 2.0; Added Status and Count Indicators for monitors; added predefined QoS for several monitors.
1.4 September 2011
Updated the Advanced tab section and added theWorking with Monitors section.
1.3 June 2011 Added support for rack mounted units; added metrics for Interface Cards; and added support for multiple selection of thresholds.
Related Documentation
Documentation for other versions of the cisco_ucs probe
Getting Started with Nimsoft® Probes
Nimsoft® Probes Reference
Requirements
Platform: Windows, Linux, Solaris
Software: Cisco Unified Computing System Manager (Cisco UCSM) v1.3 and later
Installation Notes
The cisco_ucs probe is capable of monitoring the state of VMWare ESX Hypervisors and VMs installed on the UCS blade servers.
This requires a secure communication set up between VMWare vCenter and Cisco UCS Manager (using the vCenter extension files).
Chapter 2: cisco_ucs configuration 9
Chapter 2: cisco_ucs configuration
The probe is configured by double-clicking the probe in the Infrastructure Manager, which brings up the GUI.
This section contains the following topics:
General tab (see page 9) Advanced tab (see page 10) Creating a New Group (see page 12) Creating a Host Profile (see page 13) Working with Monitors (see page 17) Equipment (see page 21) Viewing History (see page 25) Faults (see page 26) Pools (see page 27) UCS Service Profiles (see page 28) Importing the threshold policies into template (see page 30) Configuring Alarms and QoS (see page 31) Using Templates (see page 33) Message Pool (see page 39)
General tab
The General tab enables you to set the depth to which log details should be maintained. Move the slider to set the desired log level.
Advanced tab
10 cisco_ucs Guide
Advanced tab
The Advanced tab allows you to set advanced parameters for the probe. You can customize these values according to your monitoring requirements and the available system setup.
Advanced tab
Chapter 2: cisco_ucs configuration 11
The Advanced tab enables you to configure the following parameters:
Profile Check Interval
Click the time interval when the probe must poll the UCS for the profile information.
Max. number of threads
Move the slider to set the maximum number of profiles that the probe must monitor simultaneously.
UCSM XML API timeout
Enter the time duration when the probe must wait for a response from the UCS XML API.
UCSM ping timeout
Enter the time duration when the probe must wait for the UCS Manager to respond.
The probe starts a profile check with a ping to the UCS Manager. The probe does not check anything further if there is no response from the UCS Manager, or a timeout.
Note: You can disable the ping by setting this threshold to 0. The probe will query the UCS XML API and wait for a timeout there instead.
Logsize
Enter the size of the probe log file to which the probe must add internal log messages.
If the size of the log file reaches this value, the probe clears the contents of the log file.
Disable usage metering QoS
Select this check box to disable the probe from sending the usage metering QoS.
Creating a New Group
12 cisco_ucs Guide
Creating a New Group
By default, the probe contains a group, called the Default Group, for creating the host profiles. However, you can create more groups by clicking the Create a new group folder button.
The new group folder is added to the tree-view with a default name. You can edit the name, create sub-groups under a group, create a host profile under the group or delete the group by right-clicking on the New Group name and selecting the respective menu option in the context menu.
Creating a Host Profile
Chapter 2: cisco_ucs configuration 13
Creating a Host Profile
To create a host profile, click the Create new host profile button on the toolbar.
The Profile dialog opens.
Creating a Host Profile
14 cisco_ucs Guide
The fields are:
Hostname or IP address
Enter the machine name or IP address of the UCS Manager
Port
Enter the port number to connect to the UCS Manager. Usually, the port number is 443 or 80
Active
Select this checkbox to activate the profile
Group
Select the group under which the new profile is to be created
Alarm Message
Choose an alarm message from the drop-down. For more details about alarm messages, please refer to the Message Pool section.
Description
Enter a brief description for the profile.
Send UCS Faults as Nimsoft Alarms
Select this checkbox if you wish to convert the UCS Faults into Nimsoft Alarms
The severity of the Fault is converted to the corresponding Nimsoft Alarm severity. The severity "mapping" might be changed using raw-configure. For more details, see the Mapping the Fault Severity section.
User Name and Password
Provide a valid user name and password.
Important! If Cisco UCS has been set up for LDAP Authentication the login will require a domain name in addition to the user name. The convention for this username is: ucs-<domain-name>\<username>.
Example:
If the username is nimsoft and the domain is LOCAL, the username to enter for LDAP authentication is: ucs-LOCAL\nimsoft
Authentication Message
Select an alarm message from the drop-down
Alarm
Select a source for the alarm from the drop-down. Two options are available:
■ Host address: Choose this option to set the IP address of the agent profile as the source for the alarm
■ Profile name: Choose this option to set the name of the agent profile as the source for the alarm
Creating a Host Profile
Chapter 2: cisco_ucs configuration 15
QoS
Select a source for the QoS from the drop-down. Two options are available:
■ Host address: Choose this option to set the IP address of the agent profile as the source for the QoS
■ Profile name: Choose this option to set the name of the agent profile as the source for the QoS
After entering all the necessary details, click the Start Query button to generate the profile. The generated profile is displayed in the probe GUI.
Once the profile has been successfully created, you can drill down into the UCS and activate Alarms or QoS on the provided checkpoints.
The probe delivers QoS for state metrics as well. The states are translated into integer values based on the /Constants section in the probe .cfg file.
The probe can raise an alarm if a state is equal or not equal to the threshold.
Appendix A: Mapping the Fault Severity 17
Appendix A: Mapping the Fault Severity
Right-click on the cisco_ucs probe in the Infrastructure Manager while holding down the SHIFT key. Select Raw Configure option from the context menu.
From the tree-view in left frame, select FaultSeverity.
Select a Key value and click Edit Key to change the value.
Working with Monitors
The cisco_ucs probe retrieves the tree structure of the nodes, and the monitors within the nodes, from the UCS.
You can navigate through the tree structure of the nodes within the host profile, and select a node to view its monitors on the right pane.
Working with Monitors
18 cisco_ucs Guide
Editing Monitor Properties
You can edit monitor properties in one of the following ways:
■ Right click a monitor and select Edit.
■ Double click a monitor name.
The Monitor Properties window appears.
Working with Monitors
Appendix A: Mapping the Fault Severity 19
The fields are:
Name
The probe provides a default name for the monitor.
You can edit the name of the monitor.
Monitoring Object
The probe provides a short description of the object being monitored and its location from UCS.
You cannot edit the Monitoring Object or its location.
Description
Enter a description for the monitor.
Value definition
Click a predefined value that the probe must use to compare with the threshold value.
This option is inactive if the value is either a character or a string.
You can use one of the following options to define the value:
■ The current value – Click this option to use the current value measured.
■ The delta value – Click this option to use the delta value, which is current value – previous value.
■ Delta per second – Click this option to use the average of two values collected within a second, which is (current + previous)/2.
Note: When you set the value definition to The delta value or Delta per Second, the calculated value appears in the probe interface along with the actual value.
Working with Monitors
20 cisco_ucs Guide
Using Ratio
Select this check box and enter a scaling factor to display the value in the UMP graphs.
If the value is a character or a string, this check box appears dimmed.
Enable Monitoring
Select this check box to start using this monitor.
Click the appropriate mathematical operator, and specify the Threshold, Unit, and Message token.
Publish Quality of Service (QoS)
Select this check box to publish QoS messages.
In the drop down list box for QoS name, a default QoS will typically be chosen for you.
Equipment
Appendix A: Mapping the Fault Severity 21
If you see <Default> in the drop down list box it is recommended that you create your own QoS by selecting the down arrow and selecting <Add New QoS Definition>. The QoS Definition screen appears.
See the Configuring a QoS (see page 32) section for details.
Equipment
Chassis Interface Card
The server blade interface cards provide the traffic metric states.
Equipment
22 cisco_ucs Guide
If configured, the NICs on the server blade interface cards also provide traffic metrics (number of packets sent, packets dropped, errors, etc.).
The information of the disks attached to the server blades is available at Equipment > Chassis/Rack Mounts > Servers. The metrics collect the disk status values.
Equipment
Appendix A: Mapping the Fault Severity 23
Fabric Interconnects
The ports in the Fixed Module / Expansion Module(s) are grouped into the following categories, based on the "ifRole" property in the Cisco UCS Manager.
■ Appliance Ports
■ FCoE Storage Ports
■ Monitoring Ethernet Ports
■ Monitoring FC Ports
■ Server Ports
■ Unconfigured Ports
■ Uplink Ethernet Ports
■ Uplink FC Ports
The NIC nodes display an aggregated view of bandwidth (the bandwidth available for the Chassis, for Uplink to VSANs etc.).
Equipment
24 cisco_ucs Guide
Rack Mounts
Rack Mounts class is available in the Equipment node. The children nodes of this class are FEX and Servers. Rack Mounts have many similarities with the equipmentChassis class. The cisco_ucs probe should automatically detect if any RackUnits are managed by the UCS Manager.
Viewing History
Appendix A: Mapping the Fault Severity 25
Viewing History
The UCS provides a history buffer for counters.
Note: History does not apply to "states".
To view the history for items that support history, right click a counter from the grid, and from the context menu, select History option.
The following screenshot shows the history for the Speed of fan.
Faults
26 cisco_ucs Guide
Faults
The Faults item displays the various faults and the relevant details such as severity, fault code, ID, the affected object, cause for the faults, last transition date and time, and a brief description of the fault.
Pools
Appendix A: Mapping the Fault Severity 27
Pools
The Cisco UCS contains a number of ‘pools’ such as a MAC Pool (list of available MAC addresses), WWNN pool, WWPN pools, etc. It is useful for the system administrators to be aware of how many of these pools are empty, how many are assigned, and so on.
The cisco_ucs probe supports the following pools. They are displayed in the tree view of the probe GUI.
■ MAC Pools
■ Server Pools
■ UUID Pools
■ WWNN Pools
■ WWPN Pools
UCS Service Profiles
28 cisco_ucs Guide
UCS Service Profiles
The service profiles created in the Cisco UCSM are displayed in the tree view of cisco_ucs probe GUI under the UCS Service Profiles node.
UCS Service Profiles
Appendix A: Mapping the Fault Severity 29
Right-clicking a service profile from the tree view opens a context-menu.
■ Choose Refresh option to update the service profile with latest changes.
■ Choose Information to view additional details as provided by UCS.
Note: For any monitor, right-click and choose information to view additional details as provided by UCS.
Importing the threshold policies into template
30 cisco_ucs Guide
Importing the threshold policies into template
The threshold policies created in UCSM are displayed under the UCS Threshold Policies node in the treeview of cisco_ucs probe GUI.
You can import one or more existing threshold policies in to a template.
Right click one or more threshold policies and select "Add to template" context-menu. A dialog appears allowing you to select the template into which you wish to import the threshold policies.
Configuring Alarms and QoS
Appendix A: Mapping the Fault Severity 31
Select the required template from the drop-down and click OK.
The selected threshold policies are imported into the template.
It is a good idea to to add the templates based on thresholds-policies in autoconfiguration, so that after each interval the probe will try to detect if there are any classnames ( for example, processorErrorStats) available on any of the processors.
Configuring Alarms and QoS
To select the threshold values of a metric, Double-click the metric from the interface to open the Monitor Properties window.
Note: You can select multiple values to compare a Status value to in order to determine if a threshold has been exceeded.
Configuring Alarms and QoS
32 cisco_ucs Guide
Configuring a QoS
The QoS node displays the configured QoS for the system.
To create a QoS, right click on the QoS node and from the context menu, select New. The QoS Definition dialog appears.
Enter the required details such as the name for QoS, group, a brief description, QoS unit and its abbreviation. Also, select a flag to specify if the QoS is Boolean or has a maximum value.
Click OK. The new QoS is added to the tree view.
cisco_ucs QoS Metrics
Quality of Service (QoS) metrics for the cisco_ucs probe.
Name Units Description
QOS_UCS_CURRENT Ampere (A) Current
QOS_UCS_FAN_SPEED RPM Fan Speed
QOS_UCS_POWER Watt (W) Power
QOS_UCS_TEMPERATURE Celsius (C) Temperature
QOS_UCS_VOLTAGE Volt (V) Voltage
Using Templates
Appendix A: Mapping the Fault Severity 33
Using Templates
You can create templates for monitors using the Templates node. From the tree view, right-click on the Templates node and from the context menu, select New.
The Template Properties dialog appears. Enter a name for the template and brief description for it.
Click OK. The new template is added to the tree-view.
You can edit or delete a template by right clicking it in the tree view and choosing the appropriate option from the context menu.
To apply a template, you can simply drag and drop the template onto new profiles.
More Information
Adding monitors to a template Wildcard or Fixed monitor templates Auto Configuration
Using Templates
34 cisco_ucs Guide
Adding monitors to a template
To add monitors to templates, first configure a set of monitors on an existing profile.
Right-click one or more of the configured monitors and from the context menu, select Add to template.
The Select Template dialog appears. From the Name drop-down, select the template to which you wish to add the monitor(s). Click OK.
Note: Alternatively, you can also simply drag and drop the configured monitors onto a template item in the tree-view.
Using Templates
Appendix A: Mapping the Fault Severity 35
Wildcard or Fixed monitor templates
When you drag monitors on to a template, you can choose whether to create a wildcard template monitor or fixed template monitor.
If you create a wildcard, then on template deployment, monitors for all current instances of the specified class will be created.
A good place to start is to create a wildcard template for one of the fan-modules, and then deploy it to confirm whether monitors are created for all available fan-modules in every chassis.
After performing any of the above action, the selected monitors will be assigned to the selected template as shown in the figure below.
Using Templates
36 cisco_ucs Guide
AutoConfiguration
To create automonitors, drag and drop a metric (e.g. a fan-module metric) on to the AutoConfiguration node.
Apply and restart the probe. The icons indicate that monitors for all available metrics are created.
If a new fan-module has been added, the probe will pick it up and apply monitor. Furthermore, if a new chassis is inserted, the probe will automatically create monitors for the fan-modules inside that new chassis.
Using Templates
Appendix A: Mapping the Fault Severity 37
Static monitors and automonitors:
■ Static monitors override automonitors.
■ You can convert automonitor instances to static monitors if you want to treat a particular instance separately (e.g. set a different threshold or disable alarming). Then once you delete the static, automonitors will be created.
When you double-click an automonitor, the following message appears.
When you click Yes, the Monitor properties dialog appears.
Using Templates
38 cisco_ucs Guide
Configure the require settings as shown and click OK.
The selected automonitor now becomes a static monitor, as indicated by its icon.
Difference between wildcard templates and automonitors:
When wildcard templates are deployed, static monitors are created for the current available instances (So if you e.g. insert a new chassis, you will have to deploy the template once more in order for monitors to be created).
If you create automonitors, then the probe automatically detect new instances, and applies the configured automonitors.
Note: You may drag templates on to the AutoConfigurations node. If any fixed monitors are part of the template, then they are no longer fixed to that particular instance. This implies that from the AutoConfiguration point of view, it does not matter if you have a fixed or wildcard template monitor. All instances will automatically be monitored.
Message Pool
Appendix A: Mapping the Fault Severity 39
Message Pool
You can create alarm messages by using the Message Pool dialog.
From the toolbar, click the Message Pool Manager button.
The Message Pool window appears, displaying the currently configured alarm messages.
More Information
Create new message
Message Pool
40 cisco_ucs Guide
Create new message
To create a new alarm message, click the Add Message button from the Message Pool window.
Message Properties dialog appears.
Enter the necessary details such as identification name for the alarm message, message token, text for the alarm message, text to be displayed on clearing the alarm, severity (if applicable) and the subsystem string or ID.
Click OK to save the alarm message. The new alarm message is listed in the Message Pool.
Chapter 3: cisco_ucs Metrics 41
Chapter 3: cisco_ucs Metrics
The following table describes the checkpoint metrics that can be configured using the cisco_ucs probe.
Monitor Name Units Description
Application.Cisco_UCS
Status Indicates if the UCS Manager responds to ping.
Authentication Indicate if the cisco_ucs probe has the proper credentials (username/password) to communicate with the UCS Manager.
Fault UCS faults translated into Nimsoft Alarms.
Application.Cisco_UCS.Chassis
Administrative State Type: equipmentChassisAdminState
The potential values can be:
■ acknowledged = 1
■ re-acknowledge = 2
■ decommission = 3
■ remove = 4
Config State Type: equipmentChassisConfigState
The potential values can be:
■ uninitialized = 0
■ unacknowledged = 1
■ unsupported-connectivity = 2
■ ok = 3
■ removing = 4
Input Power Watt (W)
Message Pool
42 cisco_ucs Guide
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Output Power Watt (W)
Message Pool
Chapter 3: cisco_ucs Metrics 43
Monitor Name Units Description
Overall Status Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
44 cisco_ucs Guide
Monitor Name Units Description
Power Type: equipmentChassisPowerOperState
The potential values can be:
■ unknown = 0
■ ok = 1
■ failed = 2
■ input-failed = 3
■ input-degraded = 4
■ output-failed = 5
■ output-degraded = 6
■ redundancy-failed = 7
■ redundancy-degraded = 8
Presence Type: equipmentPresence
Indicates whether the component exists in the system, regardless of its operational state.
The potential values can be:
■ unknown = 0
■ empty = 1
■ equipped = 10
■ missing = 11
■ mismatch = 12
■ equipped-not-primary = 13
■ equipped-identity-unestablishable = 20
■ mismatch-identity-unestablishable = 21
■ inaccessible = 30
■ unauthorized = 40
■ not-supported = 100
Message Pool
Chapter 3: cisco_ucs Metrics 45
Monitor Name Units Description
Thermal Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Application.Cisco_UCS.Chassis.FanModule
Message Pool
46 cisco_ucs Guide
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
Chapter 3: cisco_ucs Metrics 47
Monitor Name Units Description
Overall Status Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
48 cisco_ucs Guide
Monitor Name Units Description
Performance Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Power Type: equipmentPowerState
The potential values can be:
■ unknown = 0
■ on = 1
■ test = 2
■ off = 3
■ online = 4
■ offline = 5
■ offduty = 6
■ degraded = 7
■ power-save = 8
■ error = 9
■ not-supported = 100
Message Pool
Chapter 3: cisco_ucs Metrics 49
Monitor Name Units Description
Presence Type: equipmentPresence
Indicates whether the component exists in the system, regardless of its operational state.
The potential values can be:
■ unknown = 0
■ empty = 1
■ equipped = 10
■ missing = 11
■ mismatch = 12
■ equipped-not-primary = 13
■ equipped-identity-unestablishable = 20
■ mismatch-identity-unestablishable = 21
■ inaccessible = 30
■ unauthorized = 40
■ not-supported = 100
Thermal Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Message Pool
50 cisco_ucs Guide
Monitor Name Units Description
Voltage Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Application.Cisco_UCS.Chassis.FanModule.Fan
Speed RPM The fan speed in revolutions per minute
Message Pool
Chapter 3: cisco_ucs Metrics 51
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
52 cisco_ucs Guide
Monitor Name Units Description
Overall Status Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
Chapter 3: cisco_ucs Metrics 53
Monitor Name Units Description
Performance Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Power Type: equipmentPowerState
The potential values can be:
■ unknown = 0
■ on = 1
■ test = 2
■ off = 3
■ online = 4
■ offline = 5
■ offduty = 6
■ degraded = 7
■ power-save = 8
■ error = 9
■ not-supported = 100
Message Pool
54 cisco_ucs Guide
Monitor Name Units Description
Presence Type: equipmentPresence
Indicates whether the component exists in the system, regardless of its operational state.
The potential values can be:
■ unknown = 0
■ empty = 1
■ equipped = 10
■ missing = 11
■ mismatch = 12
■ equipped-not-primary = 13
■ equipped-identity-unestablishable = 20
■ mismatch-identity-unestablishable = 21
■ inaccessible = 30
■ unauthorized = 40
■ not-supported = 100
Thermal Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Message Pool
Chapter 3: cisco_ucs Metrics 55
Monitor Name Units Description
Voltage Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Application.Cisco_UCS.Chassis.PSU
Input 210v Volt (V) Type: counter
The actual 210V input voltage
Internal Temperature Celsius (C) Type: counter
The internal PSU temperature
Message Pool
56 cisco_ucs Guide
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Output 12v Volt (V) Type: counter
The actual 12V output voltage
Message Pool
Chapter 3: cisco_ucs Metrics 57
Monitor Name Units Description
Output 3v3 Volt (V) Type: counter
The actual 3.3V output voltage
Output Current Amperes (A) Type: counter
The output current
Output Power Watts (W) Type: counter
The output power
Message Pool
58 cisco_ucs Guide
Monitor Name Units Description
Overall Status Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
Chapter 3: cisco_ucs Metrics 59
Monitor Name Units Description
Performance Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Power Type: equipmentPowerState
The potential values can be:
■ unknown = 0
■ on = 1
■ test = 2
■ off = 3
■ online = 4
■ offline = 5
■ offduty = 6
■ degraded = 7
■ power-save = 8
■ error = 9
■ not-supported = 100
Message Pool
60 cisco_ucs Guide
Monitor Name Units Description
Presence Type: equipmentPresence
Indicates whether the component exists in the system, regardless of its operational state.
The potential values can be:
■ unknown = 0
■ empty = 1
■ equipped = 10
■ missing = 11
■ mismatch = 12
■ equipped-not-primary = 13
■ equipped-identity-unestablishable = 20
■ mismatch-identity-unestablishable = 21
■ inaccessible = 30
■ unauthorized = 40
■ not-supported = 100
Thermal Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Message Pool
Chapter 3: cisco_ucs Metrics 61
Monitor Name Units Description
Voltage Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Application.Cisco_UCS.Chassis.IOModule
Ambient Temperature Celsius (C) Type: counter
The surrounding temperature
ASIC Temperature Celsius (C) The temperature on the ASIC (Application Specific Integrated Circuit).
Message Pool
62 cisco_ucs Guide
Monitor Name Units Description
Overall Status Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
Chapter 3: cisco_ucs Metrics 63
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Application.Cisco_UCS.Chassis.IOModule.BackplanePort
Message Pool
64 cisco_ucs Guide
Monitor Name Units Description
Administrative State Type: fabricAdminState
The potential values can be:
■ enabled = 0
■ disabled = 1
Overall Status Type: networkPortOperState
The potential values can be:
■ indeterminate = 0
■ up = 1
■ admin-down = 2
■ link-down = 3
■ failed = 4
■ no-license = 5
■ link-up = 6
■ hardware-failure = 7
■ software-failure = 8
■ error-disabled = 9
■ sfp-not-present = 10
Application.Cisco_UCS.Chassis.IOModule.FabricPort
Acknowledged Type: equipmentChassisConfigState
The potential values can be:
■ un-initialized = 0
■ un-acknowledged = 1
■ unsupported-connectivity = 2
■ ok = 3
■ removing = 4
Administrative State Type: fabricAdminState
The potential values can be:
■ enabled = 0
■ disabled = 1
Message Pool
Chapter 3: cisco_ucs Metrics 65
Monitor Name Units Description
Discovery Type: etherSatelliteConnectionDisc
The potential values can be:
■ absent = 0
■ present = 1
■ mis-connect = 2
Overall Status Type: networkPortOperState
The potential values can be:
■ indeterminate = 0
■ up = 1
■ admin-down = 2
■ link-down = 3
■ failed = 4
■ no-license = 5
■ link-up = 6
■ hardware-failure = 7
■ software-failure = 8
■ error-disabled = 9
■ sfp-not-present = 10
Application.Cisco_UCS.Chassis.BladeServer
Administrative State Type: computeAdminState
The potential values can be:
■ in-service = 1
■ out-of-service = 2
Availability Type: computeAvailability
The potential values can be:
■ unavailable = 0
■ available = 1
Consumed Power Watt (W) Type: counter
Front Temperature Celsius (C) Type: counter
Input Current Ampere (A) Type: counter
Input Voltage Voltage (V) Type: counter
Message Pool
66 cisco_ucs Guide
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
Chapter 3: cisco_ucs Metrics 67
Monitor Name Units Description
Overall Status Type: IsOperState
The potential values can be:
■ indeterminate = 0
■ unassociated = 1
■ ok = 10
■ discovery = 11
■ config = 12
■ unconfig = 13
■ power-off = 14
■ restart = 15
■ maintenance = 20
■ test = 21
■ compute-mismatch = 29
■ compute-failed = 30
■ degraded = 31
■ discovery-failed = 32
■ config-failure = 33
■ unconfig-failed = 34
■ test-failed = 35
■ maintenance-failed = 36
■ removed = 40
■ disabled = 41
■ inaccessible = 50
■ thermal-problem = 60
■ power-problem = 61
■ voltage-problem = 62
■ inoperable = 63
■ decommissioning = 101
■ bios-restore = 201
■ cmos-reset = 202
■ diagnostics = 203
■ diagnostics-failed = 204
Message Pool
68 cisco_ucs Guide
Monitor Name Units Description
Power Type: equipmentPowerState
The potential values can be:
■ unknown = 0
■ on = 1
■ test = 2
■ off = 3
■ online = 4
■ offline = 5
■ offduty = 6
■ degraded = 7
■ power-save = 8
■ error = 9
■ not-supported = 100
Presence Type: equipmentPresence
Indicates whether the component exists in the system, regardless of its operational state.
The potential values can be:
■ unknown = 0
■ empty = 1
■ equipped = 10
■ missing = 11
■ mismatch = 12
■ equipped-not-primary = 13
■ equipped-identity-unestablishable = 20
■ mismatch-identity-unestablishable = 21
■ inaccessible = 30
■ unauthorized = 40
■ not-supported = 100
Rear Temperature Celsius (C) Type: counter
Application.Cisco_UCS.Chassis.BladeServer.AdaptorUnit
NA NA NA
Application.Cisco_UCS.Chassis.BladeServer.AdaptorUnit.DCE
Message Pool
Chapter 3: cisco_ucs Metrics 69
Monitor Name Units Description
Administrative State Type: scalarEnum8
The potential values can be:
■ enabled = 0
■ reset-connectivity-active = 44
■ reset-connectivity-passive = 45
■ reset-connectivity = 46
Overall Status Type: networkPortOperState
The potential values can be:
■ indeterminate = 0
■ up = 1
■ admin-down = 2
■ link-down = 3
■ failed = 4
■ no-license = 5
■ link-up = 6
■ hardware-failure = 7
■ software-failure = 8
■ error-disabled = 9
■ sfp-not-present = 10
Application.Cisco_UCS.Chassis.BladeServer.AdaptorUnit.HBA
Administrative State Type: scalarEnum8
The potential values can be:
■ enabled = 0
■ reset-connectivity-active = 44
■ reset-connectivity-passive = 45
■ reset-connectivity = 46
Message Pool
70 cisco_ucs Guide
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
Chapter 3: cisco_ucs Metrics 71
Monitor Name Units Description
Overall Status Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
72 cisco_ucs Guide
Monitor Name Units Description
Performance Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Power Type: equipmentPowerState
The potential values can be:
■ unknown = 0
■ on = 1
■ test = 2
■ off = 3
■ online = 4
■ offline = 5
■ offduty = 6
■ degraded = 7
■ power-save = 8
■ error = 9
■ not-supported = 100
Message Pool
Chapter 3: cisco_ucs Metrics 73
Monitor Name Units Description
Presence Type: equipmentPresence
Indicates whether the component exists in the system, regardless of its operational state.
The potential values can be:
■ unknown = 0
■ empty = 1
■ equipped = 10
■ missing = 11
■ mismatch = 12
■ equipped-not-primary = 13
■ equipped-identity-unestablishable = 20
■ mismatch-identity-unestablishable = 21
■ inaccessible = 30
■ unauthorized = 40
■ not-supported = 100
Thermal Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Message Pool
74 cisco_ucs Guide
Monitor Name Units Description
Voltage Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Application.Cisco_UCS.Chassis.BladeServer.AdaptorUnit.NIC
Administrative State Type: scalarEnum8
The potential values can be:
■ enabled = 0
■ reset-connectivity-active = 44
■ reset-connectivity-passive = 45
■ reset-connectivity = 46
Message Pool
Chapter 3: cisco_ucs Metrics 75
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
76 cisco_ucs Guide
Monitor Name Units Description
Overall Status Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
Chapter 3: cisco_ucs Metrics 77
Monitor Name Units Description
Performance Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Power Type: equipmentPowerState
The potential values can be:
■ unknown = 0
■ on = 1
■ test = 2
■ off = 3
■ online = 4
■ offline = 5
■ offduty = 6
■ degraded = 7
■ power-save = 8
■ error = 9
■ not-supported = 100
Message Pool
78 cisco_ucs Guide
Monitor Name Units Description
Presence Type: equipmentPresence
Indicates whether the component exists in the system, regardless of its operational state.
The potential values can be:
■ unknown = 0
■ empty = 1
■ equipped = 10
■ missing = 11
■ mismatch = 12
■ equipped-not-primary = 13
■ equipped-identity-unestablishable = 20
■ mismatch-identity-unestablishable = 21
■ inaccessible = 30
■ unauthorized = 40
■ not-supported = 100
Thermal Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Message Pool
Chapter 3: cisco_ucs Metrics 79
Monitor Name Units Description
Voltage Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Application.Cisco_UCS.Chassis.BladeServer.MemArray
Current Capacity MB Type: counter
Max Capacity MB
Application.Cisco_UCS.Chassis.BladeServer.MemArray.Memory
Temperature Celsius (C) Type: counter
Application.Cisco_UCS.Chassis.BladeServer.Processor
CPU Temperature Celsius (C) Type: counter
Input Current Ampere (A)
Application.Cisco_UCS.FabricInterconnect
Available Memory MB
Cached Memory MB
fanCtrlrlnlet1 Celsius (C)
fanCtrlrlnlet2 Celsius (C)
fanCtrlrlnlet3 Celsius (C)
fanCtrlrlnlet4 Celsius (C)
Load Percent (%) CPU Utilization: Load (%) of last 1 minute
mainBoardOutlet1 Celsius (C)
mainBoardOutlet2 Celsius (C)
Message Pool
80 cisco_ucs Guide
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
psuCtrlrlnlet1 Celsius (C)
psuCtrlrlnlet2 Celsius (C)
Message Pool
Chapter 3: cisco_ucs Metrics 81
Monitor Name Units Description
Application.Cisco_UCS.FabricInterconnect.Fan
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
82 cisco_ucs Guide
Monitor Name Units Description
Overall Status Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
Chapter 3: cisco_ucs Metrics 83
Monitor Name Units Description
Performance Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Power Type: equipmentPowerState
The potential values can be:
■ unknown = 0
■ on = 1
■ test = 2
■ off = 3
■ online = 4
■ offline = 5
■ offduty = 6
■ degraded = 7
■ power-save = 8
■ error = 9
■ not-supported = 100
Message Pool
84 cisco_ucs Guide
Monitor Name Units Description
Presence Type: equipmentPresence
Indicates whether the component exists in the system, regardless of its operational state.
The potential values can be:
■ unknown = 0
■ empty = 1
■ equipped = 10
■ missing = 11
■ mismatch = 12
■ equipped-not-primary = 13
■ equipped-identity-unestablishable = 20
■ mismatch-identity-unestablishable = 21
■ inaccessible = 30
■ unauthorized = 40
■ not-supported = 100
Thermal Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Message Pool
Chapter 3: cisco_ucs Metrics 85
Monitor Name Units Description
Voltage Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Application.Cisco_UCS.FabricInterconnect.PSU
Message Pool
86 cisco_ucs Guide
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
Chapter 3: cisco_ucs Metrics 87
Monitor Name Units Description
Overall Status Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
88 cisco_ucs Guide
Monitor Name Units Description
Performance Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Power Type: equipmentPowerState
The potential values can be:
■ unknown = 0
■ on = 1
■ test = 2
■ off = 3
■ online = 4
■ offline = 5
■ offduty = 6
■ degraded = 7
■ power-save = 8
■ error = 9
■ not-supported = 100
Message Pool
Chapter 3: cisco_ucs Metrics 89
Monitor Name Units Description
Presence Type: equipmentPresence
Indicates whether the component exists in the system, regardless of its operational state.
The potential values can be:
■ unknown = 0
■ empty = 1
■ equipped = 10
■ missing = 11
■ mismatch = 12
■ equipped-not-primary = 13
■ equipped-identity-unestablishable = 20
■ mismatch-identity-unestablishable = 21
■ inaccessible = 30
■ unauthorized = 40
■ not-supported = 100
Thermal Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Message Pool
90 cisco_ucs Guide
Monitor Name Units Description
Voltage Type: equipmentSensorThresholdStatus
The potential values can be:
■ unknown = 0
■ ok = 1
■ upper-non-recoverable = 2
■ upper-critical = 3
■ upper-non-critical = 4
■ lower-non-critical = 5
■ lower-critical = 6
■ lower-non-recoverable = 7
■ not-supported = 100
Input Current Ampere (A)
Input Power Watt (W)
Input Voltage Volt (V)
Application.Cisco_UCS.FabricInterconnect.IOModule
Message Pool
Chapter 3: cisco_ucs Metrics 91
Monitor Name Units Description
Operability Type: equipmentOperability
The potential values can be:
■ unknown = 0
■ operable = 1
■ inoperable = 2
■ degraded = 3
■ powered-off = 4
■ power-problem = 5
■ removed = 6
■ voltage-problem = 7
■ thermal-problem = 8
■ performance-problem = 9
■ accessibility-problem = 10
■ identity-unestablishable = 11
■ bios-post-timeout = 12
■ disabled = 13
■ fabric-conn-problem = 51
■ fabric-unsupported-conn = 52
■ config = 81
■ equipment-problem = 82
■ decomissioning = 83
■ chassis-limit-exceeded = 84
■ not-supported = 100
■ discovery = 101
■ discovery-failed = 102
■ identify = 103
■ post-failure = 104
■ upgrade-problem = 105
■ peer-comm-problem = 106
■ auto-upgrade = 107
Message Pool
92 cisco_ucs Guide
Monitor Name Units Description
State Type: equipmentPowerState
The potential values can be:
■ unknown = 0
■ on = 1
■ test = 2
■ off = 3
■ online = 4
■ offline = 5
■ offduty = 6
■ degraded = 7
■ power-save = 8
■ error = 9
■ not-supported = 100
Application.Cisco_UCS.FabricInterconnect.IOModule.EtherPort
Administrative State Type: fabricAdminState
The potential values can be:
■ enabled = 0
■ disabled = 1
Align errors
BroadcastPackets(Rx) packets
BroadcastPackets(Tx) packets
Carrier Sense errors
Deferred Tx errors
Excess Collision errors
Fcs errors
Giants errors
Int Mac Rx errors
Int Mac Tx errors
Jumbo Packets (Rx) packets
Jumbo Packets (Tx) packets
Late Collision errors
Message Pool
Chapter 3: cisco_ucs Metrics 93
Monitor Name Units Description
Multi Collision errors
Multicast Packets(Rx) packets
Multicast Packets(Tx) packets
Out Discard errors
Overall Status Type: networkPortOperState
The potential values can be:
■ indeterminate = 0
■ up = 1
■ admin-down = 2
■ link-down = 3
■ failed = 4
■ no-license = 5
■ link-up = 6
■ hardware-failure = 7
■ software-failure = 8
■ error-disabled = 9
■ sfp-not-present = 10
Rcv errors
Recv Pause pause
Resets resets
Single Collision errors
SQETest errors
Symbol errors
Total Bytes(Rx) Bytes
Total Bytes(Tx) Bytes
Total Packets (Rx) packets
Total Packets (Tx) packets
Under Size errors
Unicast Packets (Rx) packets
Unicast Packets (Tx) packets
Xmit errors
Message Pool
94 cisco_ucs Guide
Monitor Name Units Description
Xmit Pause pause
Application.Cisco_UCS.FabricInterconnect.IOModule.FCPort
Administrative State Type: fabricAdminState
The potential values can be:
■ enabled = 0
■ disabled = 1
Bytes Rx Bytes
Bytes Tx Bytes
CRC Rx errors
Discard Rx errors
Discard Tx errors
Link Failures errors
Overall Status Type: networkPortOperState
The potential values can be:
■ indeterminate = 0
■ up = 1
■ admin-down = 2
■ link-down = 3
■ failed = 4
■ no-license = 5
■ link-up = 6
■ hardware-failure = 7
■ software-failure = 8
■ error-disabled = 9
■ sfp-not-present = 10
Packets Rx Packets
Packets Tx Packets
Rx errors
Signal Losses errors
Sync Losses errors
Too Long Rx errors
Message Pool
Chapter 3: cisco_ucs Metrics 95
Monitor Name Units Description
Too Short Rx errors
Tx errors
Application.Cisco_UCS.FabricInterconnect.LocalStorage
bootflash(size) MB
bootflash(used) MB
opt(size) MB
opt(used) MB
workspace(size) MB
workspace(used) MB
Note: In the case of Application.Cisco_UCS.FabricInterconnect.LocalStorage, the names of the storage-partitions may vary as per the hardware; however bootflash, opt and workspace are the ones most commonly found.
Application.Cisco_UCS.Hypervisor
status Type: vmStatus
The potential values can be:
■ unknown = 0
■ online = 1
■ offline = 2
Application.Cisco_UCS.VirtualMachines
status Type: vmStatus
The potential values can be:
■ unknown = 0
■ online = 1
■ offline = 2