Blue Coat Supported MIBS

09/17/2001

General Blue Coat SNMP Overview

The Blue Coat Management Information Base (MIB) specifications adhere to RFC1155 (v1-SMI), RFC1902 (v2-SMI), RFC1903 (v2-TC), and 1904 (v2-CONF.)

To load the Blue Coat MIBs on an SNMP network manager, ensure these dependent MIBs are loaded. (Most of the commercial-grade SNMP-based products do load these MIBs as the software starts.)

All Blue Coat products implement RFC1213 (MIB-II) without the EGP Group.

The system OIDs for all Blue Coat products are specified in bluecoat.mib.

Blue Coat products implement a number of private MIBs. Detailed description of the MIB variables and traps can be found at the end of this page.

• bluecoat.mib
• disk.mib
• sensor.mib
• usage.mib
• attack.mib
• wccp.mib

Blue Coat products implement most of the RFC2594 (WWW MIB) and the experimental proxy MIB.

• www.mib: Only the wwwService and wwwProtocolStatistics groups are supported. The only service that's instrumented is http.
• proxy.mib: All but the proxyConfig group and the proxyMedianSvcTable (under the proxyPerf group) are supported.

Additional private MIBs (such as streaming and CDN) will be implemented as the functionality get released with different products. Check the Blue Coat support site for the most updated information. You can download the supported MIB files from the web site as well.

Blue Coat Private MIB Files

sensor.mib

The sensor.mib file monitors the values of the various environmental sensors present on the Security Appliance. To enable or disable the trap, set the deviceSensorTrapEnable variable true/false.

The notification syntax for sensor.mib is

deviceSensorTrap {deviceSensorName, deviceSensorValue, deviceSensorCode}

Parameters that you can monitor with the sensor.mib file include:

• · Bus Temperature
• · CPU Temperature
• · Fan
• · CPU Fan
• · Bus Voltage
• · CPU Voltage
• · Power Supply

The sensor.mib trap variables and their values are described in the table below.

Trap Variable	Description	Value
deviceSensorName	The textual name of the sensor.	---
deviceSensorValue	Reports the most recent measurement seen by the sensor.	---
deviceSensorCode	Interprets the deviceSensor Value.	ok(1) unknown(2) not-installed(3) voltage-low-warning(4) voltage-low-critical(5) no-power(6) voltage-high-warning(7) voltage-high-critical(8) voltage-high-severe(9) temperature-high-warning(10) temperature-high-critical(11) temperature-high-severe(12) fan-slow-warning(13) fan-slow-critical(14) fan-stopped(15)

The error messages produced by the deviceSensorCode are described in the table below.

Message	Status
OK (1)	Normal
voltage-low-critical(5) no-power(6) voltage-high-critical(8) voltage-high-severe(9) temperature-high-critical(11) temperature-high-severe(12) fan-slow-critical(14) fan-stopped(15)	Critical-Immediate attention is required.
unknown(2) not-installed(3)	Minor
voltage-low-warning(4) voltage-high-warning(7) temperature-high-warning(10) fan-slow-warning(13)	Warning

disk.mib

The disk.mib monitors the status of the Security Appliance disks. Enable or disable the disk trap through the deviceDiskTrapEnable variable.

The notification syntax for disk.mib is:

deviceDiskTrap {deviceDiskStatus}

The disk.mib trap variables and their values are described in the table below.

Trap Variable	Description	Value
deviceDiskStatus	Indicates the present operation status of the disk	present(1) initializing(2) inserted(3) offline(4) removed(5) not-present(6) empty(7) bad(8) unknown(9)

The error messages produced by the deviceDiskStatus are described in the table below.

Message	Status
present(1) initializing(2)	Normal
empty (8)	Critical-Immediate attention is required.
nserted(3) offline(4) removed(5) unknown(9)	Warning
voltage-low-warning(4) voltage-high-warning(7) temperature-high-warning(10) fan-slow-warning(13)	Warning

attack.mib

The attack.mib file monitors possible protocol attacks by hackers. The MIB file sends notification at the beginning and ending of an attack. The conditions reported by the attack.mib file include SYN_FLOOD.

The attack.mib notification syntax is:

deviceAttackTrap {deviceAttackName, deviceAttackStatus})

The attack.mib trap variables and their values are described in the table below.

Trap Variable	Description	Value
deviceAttackName	Shows textual name of the attack.	---
deviceAttackStatus	The status of an attack.	no-attack(1): not under attack under-attack(2): attack in progress Default value: no-attack(1)

The error messages produced by the deviceAttackStatus are described in the table below.

Message	Status
no-attack(1)	Normal
under-attack(2)	Critical-Immediate attention is required.

usage.mib

The usage.mib file sends a notification when the percentage of available space that is used exceeds a threshold specified by the deviceUsageHigh variable.

Resources that can be monitored include:

• Disk
• CPU

The usage.mib trap variables and their values are described in the table below.

Trap Variable	Description	Value
deviceUsageName	The textual name of the resource; for example, CPU..	---
deviceUsagePercent	Percentage of the resource that is in use	---
deviceUsageStatus	Comparison of the deviceUsagePercent value with the deviceUsageHigh variable.	ok(1) high(2)

The deviceUsageHigh variable can specify values for each resource, using an SNMP set operation. A notification is sent when the value is reached. For more information on the deviceUsageHigh variable, refer to the usage.mib file.

The error messages produced by the deviceUsageHigh variable are described in the table below.

Message	Status
ok (1)	Normal
high (2)	Warning

wccp.mib

wccp.mib file monitors the some of the statistical information of WCCP (Web Cache Communication Protocol)

Statistics that can be monitored for each service include:

• Service Type
• Service Version
• Packets Redirected
• Bytes Redirected