Measures reported by UCSCsServerTest
Blade servers are the core components of the Cisco UCS system. Unavailable/inoperable blade servers can hence bring the entire system to a standstill. Using this test, you can continuously monitor the overall health, operability, and availability of each blade server in a chassis, and be alerted to anomalies as soon as they occur, so that you can take the required corrective actions before your mission-critical services begin to suffer. In addition, the test also captures critical power and thermal failures experienced by the blade servers, and takes stock of the hardware (such as processors, cores, NICs, etc.) supporting the operations of the blade server.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement
Unit |
Interpretation |
| OperState |
Indicates the overall status of the blade servers loaded in the chassis.
|
|
This measure reports the status of the blade servers and their numeric equivalents as shown in the table:
| Numeric Value |
State |
| 0 |
Indeterminate |
| 1 |
Unassociated |
| 10 |
Ok |
| 11 |
Discovery |
| 12 |
Config |
| 13 |
Unconfig |
| 14 |
Power-off |
| 15 |
Restart |
| 20 |
Maintenance |
| 21 |
Test |
| 29 |
Compute-mismatch |
| 30 |
Compute-failed |
| 31 |
Degraded |
| 32 |
Discovery-failed |
| 33 |
Config-failure |
| 34 |
Unconfig-failed |
| 35 |
Test-failed |
| 36 |
Maintenance-failed |
| 40 |
Removed |
| 41 |
Disabled |
| 50 |
Inaccessible |
| 60 |
Thermal-problem |
| 61 |
Power-problem |
| 62 |
Voltage-problem |
| 63 |
Inoperable |
| 101 |
Decomissioning |
| 201 |
Bios-restore |
| 202 |
Cmos-reset |
| 203 |
Diagnostics |
| 204 |
Diagnostics-failed |
Note:By default, this measure reports the above-mentioned States while indicating the status of the blade servers in the chassis. However, the graph of this measure will be represented using the corresponding numeric equivalents of the states as mentioned in the table above.
The detailed diagnosis of this measure provides the Time, Slot ID, chassis ID, PID, Revision, Serial Number, Vendor, Name, UUID, Service Profile and Original UUID attributes for this blade server. |
| AdminState |
Indicates the administrative state of the blade servers loaded in the chassis.
|
|
This measure reports either In-service or Out-of-service as the adminstrative state of the blade servers. The numeric equivalents corresponding to these states are shown in the table below:
| Numeric Value |
State |
1 |
In-service |
| 2 |
Out-of-service |
Note:By default, this measure reports the above-mentioned States while indicating the administrative state of the blade servers. However, the graph of this measure will be represented using the corresponding numeric equivalents of the states i.e., 1 or 2. |
| AssociateState |
Indicates the associative state of the blade servers loaded in this chassis i.e., indicates whether the blade servers are associated with the service profile that is preconfigured in the Cisco UCS Manager.
|
|
A service profile represents a logical view of a single blade server, without needing to know exactly which blade you are talking about. The profile object contains the server personality (identity and network information). The profile can then be associated with a single blade at a time.Cisco UCS Manager uses service profiles to provision the blade servers and their I/O properties. The Cisco Unified Computing System has a form factor-neutral architecture, allowing administrators to centrally manage Cisco UCS blade servers or rack-mount servers, or incorporate both within a single management domain.
Service profiles are created by server, network, and storage administrators and are stored in the Cisco UCS Fabric Interconnects. Infrastructure policies needed to deploy applications, such as power and cooling, security, identity, hardware health, and Ethernet and storage networking, are encapsulated in the service profile. The policies coordinate and automate element management at every layer of the hardware stack, including RAID levels, BIOS settings, firmware revisions and settings, adapter identities
and settings, VLAN and VSAN network settings, network quality of service (QoS), and data center connectivity. Cisco UCS Manager provides granular Cisco Unified Computing System visibility for higher-level management tools from BMC, CA, HP, IBM, and others, providing exceptional alignment of infrastructure management with OS and application requirements.
Service profile templates are used to simplify the creation of service profiles, helping ensure consistent policies within the system for a given service or application. This approach makes it just as easy to configure one server or hundreds of servers with thousands of virtual machines, decoupling scale from complexity. This automation reduces the number of manual steps needed, helping reduce the chance for human error, improving consistency, and reducing server and network deployment times.
This measure reports the associative state of the blade servers and their numeric equivalents as shown in the table:
| Numeric Value |
State |
0 |
None |
| 1 |
Associated |
| 2 |
Removing |
| 3 |
Failed |
Note:By default, this measure reports the above-mentioned States while indicating the associative state of the blade servers loaded in the chassis. However, the graph of this measure will be represented using the corresponding numeric equivalents of the states i.e., 0 to 3. |
| AvailState |
Indicates the availability status of the blade servers loaded in each chassis.
|
|
This measure reports the either Available or Unavailable as the availability status of the blade servers. The states and their corresponding numeric equivalents are shown in the table below:
| Numeric Value |
State |
0 |
Unavailable |
| 1 |
Available |
Note:By default, this measure reports the above-mentioned States while indicating the availability status of the blade servers. However, the graph of this measure will be represented using the corresponding numeric equivalents of the states i.e., 0 or 1. |
| CheckpointState |
Indicates the checkpoint status of the blade servers loaded in this chassis.
|
|
This measure reports the checkpoint status of the blade servers and their numeric equivalents as shown in the table:
| Numeric Value |
State |
0 |
Unknown |
| 1 |
Removing |
2 |
Shallow-checkpoint |
| 3 |
Deep-checkpoint |
| 4 |
Discovered |
Note:By default, this measure reports the above-mentioned States while indicating the checkpoint status of the blade servers. However, the graph of this measure will be represented using the corresponding numeric equivalents of the states i.e., 0 to 4. |
| DiscoveryState |
Indicates the discovery status of the blade servers loaded in this chassis.
|
|
This measure reports the discovery status of the blade servers and their numeric equivalents as shown in the table:
| Numeric Value |
State |
0 |
Undiscovered |
| 1 |
In-progress |
2 |
Malformed-fru-ino |
| 3 |
Fru-not-ready |
| 4 |
Insufficiently-equipped |
| 8 |
Failed |
| 16 |
Complete |
| 32 |
Retry |
| 64 |
Throttled |
| 128 |
Illegal-fru |
| 129 |
Fru-identity-indeterminate |
| 130 |
Fru-state-indeterminate |
| 131 |
Diagnostics-in-progress |
| 132 |
Efidiagnostics-in-progress |
| 133 |
Diagnostics-failed |
| 134 |
Diagnostics-complete |
Note:By default, this measure reports the above-mentioned States while indicating the discovery status of the blade servers loaded in this chassis. However, the graph of this measure will be represented using the corresponding numeric equivalents of the states as mentioned in the table above. |
| Operability |
Indicates the operating state of the blade servers loaded in this chassis.
|
|
This measure reports the operating state of the blade servers and their numeric equivalents as shown in the table:
| Numeric Value |
State |
| 0 |
Unknown |
| 1 |
Operable |
| 2 |
Inoperable |
| 3 |
Degraded |
| 4 |
Powered-off |
| 5 |
Power-problem |
| 6 |
Removed |
| 7 |
Voltage-problem |
| 8 |
Thermal-problem |
| 9 |
Performance-problem |
| 10 |
Accessibility-problem |
| 11 |
Identity-unestablishable |
| 12 |
Bios-post-timeout |
| 13 |
Disabled |
| 51 |
Fabric-conn-problem |
| 52 |
Fabric-unsupported-conn |
| 81 |
Config |
| 82 |
Equipment-problem |
| 83 |
Decommissioning |
| 84 |
Chassis-limit-exceeded |
| 101 |
Discovery |
| 102 |
Discovery-failed |
| 103 |
Identify |
| 104 |
Post-failure |
| 105 |
Upgrade-problem |
| 106 |
Peer-comm-problem |
| 107 |
Auto-upgrade |
Note:By default, this measure reports the above-mentioned States while indicating the operating state of the blade servers loaded in this chassis. However, the graph of this measure will be represented using the corresponding numeric equivalents of the states as mentioned in the table above. |
| Power |
Indicates the power status of the blade servers loaded in this chassis.
|
|
This measure reports the power status of the blade servers and their numeric equivalents as shown in the table:
| Numeric Value |
State |
| 0 |
Unknown |
| 1 |
On |
| 2 |
Test |
| 3 |
Off |
| 4 |
Online |
| 5 |
Offline |
| 6 |
Offduty |
| 7 |
Degraded |
| 8 |
Power-save |
| 9 |
Error |
Note:By default, this measure reports the above-mentioned States while indicating the power status of the blade servers loaded in this chassis. However, the graph of this measure will be represented using the corresponding numeric equivalents of the states i.e., 0 to 10. |
| SlotState |
Indicates the slot status of the blade servers loaded in this chassis.
|
|
This measure reports the slot status of the blade servers and their numeric equivalents as shown in the table:
| Numeric Value |
State |
| 0 |
Unknown |
| 1 |
Empty |
| 10 |
Equipped |
| 11 |
Missing |
| 12 |
Mismatch |
| 13 |
Equipped-not-primary |
| 20 |
Equipped-identity-unestablishable |
| 21 |
Mismatch-identity-unestablishable |
| 30 |
Inaccessible |
| 40 |
Unauthorized |
Note:By default, this measure reports the above-mentioned States while indicating the slot status of the blade servers loaded in this chassis. However, the graph of this measure will be represented using the corresponding numeric equivalents of the states as mentioned in the table above. |
| EffectiveMem |
Indicates the amount of memory that can be effectively used by the blade servers present in this chassis.
|
MB |
Ideally, the value of this measure should be high.
|
| TotalMem |
Indicates the total memory available in the blade servers present in this chassis.
|
MB |
|
| Cpus |
Indicates the number of Central Processor Units available in the blade servers present in this Cisco UCS chassis.
|
Number |
|
| Cores |
Indicates the total number of cores available on all the CPS that are installed in the blade servers.
|
Number |
|
| CoresEnabled |
Indicates the number of core processors that are enabled in this blade server.
|
Number |
|
| Threads |
Indicates the number of processes that can run simultaneously on this blade server.
|
Number |
This measure is equal to either the number of cores or twice the number of cores if the operating system supports hyperthreading. |
| Adapters |
Indicates the number of adapters available in the blade servers.
|
Number |
|
| Nics |
Indicates the number of physical ethernet network interface cards (NICs) available in the blade servers.
|
Number |
|
| Hbas |
Indicates the number of physical host bus adapters (HBAs) available in the blade servers.
|
Number |
|
|