CISCO-SIBU-FLASH-MIB :: csfUpgradeFlashSize

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-SIBU-FLASH-MIB › csfUpgradeFlashSize

csfUpgradeFlashSize

Module: CISCO-SIBU-FLASH-MIB

OID (symbolic): CISCO-SIBU-FLASH-MIB::csfUpgradeFlashSize

OID (numeric): 1.3.6.1.4.1.9.10.45.1.1.2

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: The size of available FLASH memory in the system, in kilobytes. For example: 128 equals 131072 bytes (128 bytes times 1024).

What is csfUpgradeFlashSize?

Reports the total size, in kilobytes, of the flash memory available on the device for storing firmware images.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.45.1.1.2
snmpwalk -v2c -c public <target> CISCO-SIBU-FLASH-MIB::csfUpgradeFlashSize

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.45.1.1.2.1
snmpget -v2c -c public <target> CISCO-SIBU-FLASH-MIB::csfUpgradeFlashSize.1

Start monitoring Cisco SIBU/SMB switches (e.g. Catalyst 1900 series, legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-SIBU-FLASH-MIB::csfUpgradeFlashSize OID value, configure state conditions and alerts, and monitor any Cisco SIBU/SMB switches (e.g. Catalyst 1900 series, legacy) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco SIBU/SMB switch (e.g. Catalyst 1900 series, legacy) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type csfUpgradeFlashSize into the Find box to locate it in the OID tree, then select it and click OK. The size of available FLASH memory in the system, in kilobytes. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the value drifts significantly from its normal baseline, since an unexpected change often points to a real underlying issue. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 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.10ciscoExperimentCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.10.45ciscoSibuFlashMIBCISCO-SIBU-FLASH-MIB
1.3.6.1.4.1.9.10.45.1ciscoSibuFlashMIBObjectsCISCO-SIBU-FLASH-MIB
1.3.6.1.4.1.9.10.45.1.1csfUpgradeCISCO-SIBU-FLASH-MIB
1.3.6.1.4.1.9.10.45.1.1.2csfUpgradeFlashSizeCISCO-SIBU-FLASH-MIB