CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB :: cucsSysdebugManualCoreFileExportTargetDn

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIBcucsSysdebugManualCoreFileExportTargetDn

cucsSysdebugManualCoreFileExportTargetDn

Module: CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB::cucsSysdebugManualCoreFileExportTargetDn

OID (numeric): 1.3.6.1.4.1.9.9.719.1.47.15.1.2

Node type: OBJECT-TYPE

Type: CucsManagedObjectDn

Access: read-only

Description: Cisco UCS sysdebug:ManualCoreFileExportTarget:dn managed object property

What is cucsSysdebugManualCoreFileExportTargetDn?

This is the Distinguished Name (DN) of an admin-defined destination (server, protocol, and path) for manually pushing a captured core (crash) file off the fabric interconnect, the full hierarchical path in the UCS management tree that uniquely addresses this one instance. UCS Manager returns a DN like this so that an administrator or a script can pinpoint exactly which managed object a given SNMP row refers to, rather than a bare index number. For example, an admin sending a process crash dump to an external server so Cisco TAC can analyze it, and the DN is the string that tells them precisely which object in the tree they are looking at.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.47.15.1.2
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB::cucsSysdebugManualCoreFileExportTargetDn

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.47.15.1.2.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB::cucsSysdebugManualCoreFileExportTargetDn.1

Start monitoring Cisco UCS Manager-managed blade/rack servers and fabric interconnects with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB::cucsSysdebugManualCoreFileExportTargetDn OID value, configure state conditions and alerts, and monitor any Cisco UCS Manager-managed blade/rack servers and fabric interconnects from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
1.3.6.1.4.1.9.9.719ciscoUnifiedComputingMIBCISCO-UNIFIED-COMPUTING-MIB
1.3.6.1.4.1.9.9.719.1ciscoUnifiedComputingMIBObjectsCISCO-UNIFIED-COMPUTING-MIB
Numeric OIDNameModule
1.3.6.1.4.1.9.9.719.1.47cucsSysdebugObjectsCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB
1.3.6.1.4.1.9.9.719.1.47.15cucsSysdebugManualCoreFileExportTargetTableCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB
1.3.6.1.4.1.9.9.719.1.47.15.1cucsSysdebugManualCoreFileExportTargetEntryCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB
1.3.6.1.4.1.9.9.719.1.47.15.1.2cucsSysdebugManualCoreFileExportTargetDnCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB