CISCO-UNIFIED-COMPUTING-CONFIG-MIB :: cucsConfigManagedEpImpactResponseAppConnectorId

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-UNIFIED-COMPUTING-CONFIG-MIB › cucsConfigManagedEpImpactResponseAppConnectorId

cucsConfigManagedEpImpactResponseAppConnectorId

Module: CISCO-UNIFIED-COMPUTING-CONFIG-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-CONFIG-MIB::cucsConfigManagedEpImpactResponseAppConnectorId

OID (numeric): 1.3.6.1.4.1.9.9.719.1.61.3.1.5

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

Description: Cisco UCS config:ManagedEpImpactResponse:appConnectorId managed object property

What is cucsConfigManagedEpImpactResponseAppConnectorId?

This Gauge32 'appConnectorId' identifies the specific application connector (the integration link between the managing endpoint and this managed UCS domain) used to gather this impact response. This is mainly relevant to UCS Central's own internal bookkeeping, letting it correlate a response back to the exact connector session that retrieved it, rather than something an admin queries directly. A domain connected via a particular registered connector session might report appConnectorId as `7`.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.61.3.1.5
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-CONFIG-MIB::cucsConfigManagedEpImpactResponseAppConnectorId

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.61.3.1.5.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-CONFIG-MIB::cucsConfigManagedEpImpactResponseAppConnectorId.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-CONFIG-MIB::cucsConfigManagedEpImpactResponseAppConnectorId 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.61cucsConfigObjectsCISCO-UNIFIED-COMPUTING-CONFIG-MIB
1.3.6.1.4.1.9.9.719.1.61.3cucsConfigManagedEpImpactResponseTableCISCO-UNIFIED-COMPUTING-CONFIG-MIB
1.3.6.1.4.1.9.9.719.1.61.3.1cucsConfigManagedEpImpactResponseEntryCISCO-UNIFIED-COMPUTING-CONFIG-MIB
1.3.6.1.4.1.9.9.719.1.61.3.1.5cucsConfigManagedEpImpactResponseAppConnectorIdCISCO-UNIFIED-COMPUTING-CONFIG-MIB