CISCO-UNIFIED-COMPUTING-FIRMWARE-MIB :: cucsFirmwareHostPackModImpactRebootPolicy

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-FIRMWARE-MIBcucsFirmwareHostPackModImpactRebootPolicy

cucsFirmwareHostPackModImpactRebootPolicy

Module: CISCO-UNIFIED-COMPUTING-FIRMWARE-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-FIRMWARE-MIB::cucsFirmwareHostPackModImpactRebootPolicy

OID (numeric): 1.3.6.1.4.1.9.9.719.1.22.35.1.7

Node type: OBJECT-TYPE

Type: SnmpAdminString

Access: read-only

Description: Cisco UCS firmware:HostPackModImpact:rebootPolicy managed object property

What is cucsFirmwareHostPackModImpactRebootPolicy?

This holds the reboot policy that would apply if this particular firmware package change were carried out on this host -- essentially whether the server will need an immediate reboot, a user-acknowledged reboot, or none at all. This is the single field an admin cares about most when scheduling firmware maintenance, since it tells them directly whether applying this specific change to this specific service profile will cause the server to go down. A value of 'immediate' here for a production service profile is the signal an admin needs to schedule that specific update for an approved maintenance window rather than applying it during business hours.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.22.35.1.7
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-FIRMWARE-MIB::cucsFirmwareHostPackModImpactRebootPolicy

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.22.35.1.7.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-FIRMWARE-MIB::cucsFirmwareHostPackModImpactRebootPolicy.1

Start monitoring Cisco UCS blade server / fabric interconnect / chassis (firmware) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-FIRMWARE-MIB::cucsFirmwareHostPackModImpactRebootPolicy OID value, configure state conditions and alerts, and monitor any Cisco UCS blade server / fabric interconnect / chassis (firmware) 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.22cucsFirmwareObjectsCISCO-UNIFIED-COMPUTING-FIRMWARE-MIB
1.3.6.1.4.1.9.9.719.1.22.35cucsFirmwareHostPackModImpactTableCISCO-UNIFIED-COMPUTING-FIRMWARE-MIB
1.3.6.1.4.1.9.9.719.1.22.35.1cucsFirmwareHostPackModImpactEntryCISCO-UNIFIED-COMPUTING-FIRMWARE-MIB
1.3.6.1.4.1.9.9.719.1.22.35.1.7cucsFirmwareHostPackModImpactRebootPolicyCISCO-UNIFIED-COMPUTING-FIRMWARE-MIB