CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

Description: MIB for blade server and chassis compute resource management on Cisco UCS, covering server discovery, power states, memory/link aggregation admin states, and blade association lifecycle

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

This Cisco UCS MIB represents the COMPUTE package of the UCS Manager information model, covering blade server and chassis compute-resource management, including server auto-discovery/association policy, power state administration, and memory/link-aggregation admin states. It exposes configuration data (autoconfiguration policy qualifiers, source service-profile template names, policy inheritance level) tied to how newly discovered blades are provisioned. Its monitoring emphasis is on hardware/software lifecycle status: whether a blade has been discovered and correctly associated with a service profile, and its power/administrative state, which is foundational to knowing whether compute hardware in a chassis is usable. It is part of the broader CISCO-UNIFIED-COMPUTING-MIB family and correlates with the FAULT and DIAG MIBs via shared distinguished names for the same physical components. Typical deployment is within UCS blade chassis managed by UCS Manager and Fabric Interconnects. Engineers can download the CISCO-UNIFIED-COMPUTING-COMPUTE-MIB file directly to load it into their MIB browser.

cucsComputeAutoconfigPolicyTable/cucsComputeAutoconfigPolicyEntry rows, keyed by cucsComputeAutoconfigPolicyInstanceId and identified by Dn/Rn, expose cucsComputeAutoconfigPolicyQualifier and cucsComputeAutoconfigPolicySrcTemplName describing which service-profile template a newly discovered blade auto-associates with, plus cucsComputeAutoconfigPolicyPolicyLevel indicating where the policy is inherited from. An admin polling this table after inserting a new blade into a chassis can confirm it discovered correctly and picked up the intended service-profile template rather than remaining unassociated.