BLUECOAT-SG-WCCP-MIB :: deviceWccpPacketsRedir

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BLUECOAT-SG-WCCP-MIB › deviceWccpPacketsRedir

deviceWccpPacketsRedir

Module: BLUECOAT-SG-WCCP-MIB

OID (symbolic): BLUECOAT-SG-WCCP-MIB::deviceWccpPacketsRedir

OID (numeric): 1.3.6.1.4.1.3417.2.5.2.1.1.1.5

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: This variable indicates how many WCCP packets have been redirected.

What is deviceWccpPacketsRedir?

Tracks the total number of WCCP (Web Cache Communication Protocol) packets that the Blue Coat SG device has redirected. This counter helps monitor the volume of web traffic being intercepted and forwarded via WCCP.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3417.2.5.2.1.1.1.5
snmpwalk -v2c -c public <target> BLUECOAT-SG-WCCP-MIB::deviceWccpPacketsRedir

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3417.2.5.2.1.1.1.5.1
snmpget -v2c -c public <target> BLUECOAT-SG-WCCP-MIB::deviceWccpPacketsRedir.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-WCCP-MIB::deviceWccpPacketsRedir 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 deviceWccpPacketsRedir into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This variable indicates how many WCCP packets have been redirected. 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.5deviceWccpMIBBLUECOAT-SG-WCCP-MIB
1.3.6.1.4.1.3417.2.5.2deviceWccpMIBObjectsBLUECOAT-SG-WCCP-MIB
1.3.6.1.4.1.3417.2.5.2.1deviceWccpValuesBLUECOAT-SG-WCCP-MIB
1.3.6.1.4.1.3417.2.5.2.1.1deviceWccpValueTableBLUECOAT-SG-WCCP-MIB
1.3.6.1.4.1.3417.2.5.2.1.1.1deviceWccpValueEntryBLUECOAT-SG-WCCP-MIB
1.3.6.1.4.1.3417.2.5.2.1.1.1.5deviceWccpPacketsRedirBLUECOAT-SG-WCCP-MIB