CISCO-UNIFIED-COMPUTING-FAULT-MIB :: cucsFaultPolicyPinningExpirationInterval

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-FAULT-MIBcucsFaultPolicyPinningExpirationInterval

cucsFaultPolicyPinningExpirationInterval

Module: CISCO-UNIFIED-COMPUTING-FAULT-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-FAULT-MIB::cucsFaultPolicyPinningExpirationInterval

OID (numeric): 1.3.6.1.4.1.9.9.719.1.1.3.1.18

Node type: OBJECT-TYPE

Type: TimeIntervalSec

Access: read-only

Description: Cisco UCS fault:Policy:pinningExpirationInterval managed object property

What is cucsFaultPolicyPinningExpirationInterval?

This is the time, in seconds, after which a pinned fault, one being kept visible past its actual resolution as referenced by the fault holder's pinning-cleared field earlier, automatically has its pin released. This controls how long a resolved-but-pinned fault stays artificially visible so an admin has a fair chance to notice it before it's allowed to disappear on its own, balancing visibility against not letting the fault log accumulate resolved noise indefinitely. A pinning expiration interval of 900 seconds, 15 minutes, means a transient fault that's already cleared will still show as pinned for 15 minutes after clearing before that hold is automatically released.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.1.3.1.18
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-FAULT-MIB::cucsFaultPolicyPinningExpirationInterval

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.1.3.1.18.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-FAULT-MIB::cucsFaultPolicyPinningExpirationInterval.1

Start monitoring Cisco UCS blade servers and chassis (fault management) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-FAULT-MIB::cucsFaultPolicyPinningExpirationInterval OID value, configure state conditions and alerts, and monitor any Cisco UCS blade servers and chassis (fault management) 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.1cucsFaultObjectsCISCO-UNIFIED-COMPUTING-FAULT-MIB
1.3.6.1.4.1.9.9.719.1.1.3cucsFaultPolicyTableCISCO-UNIFIED-COMPUTING-FAULT-MIB
1.3.6.1.4.1.9.9.719.1.1.3.1cucsFaultPolicyEntryCISCO-UNIFIED-COMPUTING-FAULT-MIB
1.3.6.1.4.1.9.9.719.1.1.3.1.18cucsFaultPolicyPinningExpirationIntervalCISCO-UNIFIED-COMPUTING-FAULT-MIB