CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB :: cucsSysdebugAutoCoreFileExportTargetHostname

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIBcucsSysdebugAutoCoreFileExportTargetHostname

cucsSysdebugAutoCoreFileExportTargetHostname

Module: CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.47.1.1.16

Node type: OBJECT-TYPE

Type: SnmpAdminString

Access: read-only

Description: Cisco UCS sysdebug:AutoCoreFileExportTarget:hostname managed object property

What is cucsSysdebugAutoCoreFileExportTargetHostname?

This string field holds the hostname or IP address of the remote server that this automatic core-file export target sends its files to. An admin needs this to know exactly where UCS Manager will deliver data the moment this automatic core-file export target runs, so the destination can be checked and confirmed reachable. For example, if transfers from this automatic core-file export target are failing, an admin first confirms this Hostname value points to a server that is actually up and reachable from the fabric interconnect.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.47.1.1.16
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB::cucsSysdebugAutoCoreFileExportTargetHostname

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.47.1.1.16.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB::cucsSysdebugAutoCoreFileExportTargetHostname.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::cucsSysdebugAutoCoreFileExportTargetHostname 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.1cucsSysdebugAutoCoreFileExportTargetTableCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB
1.3.6.1.4.1.9.9.719.1.47.1.1cucsSysdebugAutoCoreFileExportTargetEntryCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB
1.3.6.1.4.1.9.9.719.1.47.1.1.16cucsSysdebugAutoCoreFileExportTargetHostnameCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB