BLUECOAT-SG-PROXY-MIB :: sgProxyStorage

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBLUECOAT-SG-PROXY-MIBsgProxyStorage

sgProxyStorage

Module: BLUECOAT-SG-PROXY-MIB

OID (symbolic): BLUECOAT-SG-PROXY-MIB::sgProxyStorage

OID (numeric): 1.3.6.1.4.1.3417.2.11.2.2.1

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The quantity of storage in use by the proxy in bytes.

What is sgProxyStorage?

Reports the total disk or cache storage currently consumed by the Blue Coat SG proxy, measured in bytes. This helps track how much storage the proxy is using for cached content.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3417.2.11.2.2.1
snmpwalk -v2c -c public <target> BLUECOAT-SG-PROXY-MIB::sgProxyStorage

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3417.2.11.2.2.1.1
snmpget -v2c -c public <target> BLUECOAT-SG-PROXY-MIB::sgProxyStorage.1

Start monitoring Blue Coat (Symantec/Broadcom) SG proxy appliances with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BLUECOAT-SG-PROXY-MIB::sgProxyStorage OID value, configure state conditions and alerts, and monitor any Blue Coat (Symantec/Broadcom) SG proxy appliances from a single console.

How to Use in IPNetwork Monitor

Select a Blue Coat (Symantec/Broadcom) SG proxy appliance 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 sgProxyStorage into the Find box to locate it in the OID tree, then select it and click OK. The quantity of storage in use by the proxy in bytes. 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 a Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. 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.3417blueCoatBLUECOAT-MIB
1.3.6.1.4.1.3417.2blueCoatMgmtBLUECOAT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.3417.2.11bluecoatSGProxyMIBBLUECOAT-SG-PROXY-MIB
1.3.6.1.4.1.3417.2.11.2sgProxySystemBLUECOAT-SG-PROXY-MIB
1.3.6.1.4.1.3417.2.11.2.2sgProxyCacheBLUECOAT-SG-PROXY-MIB
1.3.6.1.4.1.3417.2.11.2.2.1sgProxyStorageBLUECOAT-SG-PROXY-MIB