CISCO-UNIFIED-COMPUTING-DUPE-MIB

Description: MIB for duplicate managed-object detection and resolution on Cisco UCS, tracking scope, operation status, and class identifiers for objects flagged as duplicates within the UCS domain

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 Managed Information Model package MIB tracks duplicate managed-object detection within the UCS domain, exposing scope, operation, and class identifier data for objects that the UCS management framework has flagged as duplicates. It is largely an internal consistency-checking module rather than a hardware telemetry one, surfacing software-level state about the UCS object database itself. Monitoring use is niche: administrators or UCS support engineers would check cucsDupeScopeTable entries to identify which managed objects (by class ID and distinguished name) triggered duplicate detection, which can indicate configuration synchronization problems or corrupted management-information-tree state after a fabric interconnect failover. It depends on the umbrella CISCO-UNIFIED-COMPUTING-MIB and the internal UCS managed-object database/DME mechanisms. It is used exclusively within Cisco UCS Manager/UCS Central deployments for troubleshooting management-plane consistency issues. Engineers can download the CISCO-UNIFIED-COMPUTING-DUPE-MIB file directly to load it into their MIB browser.

An administrator troubleshooting a UCS management sync issue would poll cucsDupeScopeTable / cucsDupeScopeEntry, examining cucsDupeScopeMoClassId, cucsDupeScopeSourceMoDn, and cucsDupeScopeClientMoDn to identify which specific managed object was duplicated and in what scope. The cucsDupeScopeOperCode would indicate what operation triggered the detection, helping pinpoint whether a failover or config-sync event caused the conflict. This is a low-level diagnostic table rather than a typical performance-monitoring one.

MIB representation of Cisco Unified Computing System DUPE management information model package.