Missing Memory Items and Data from Blue Coat SG200 Proxy in Performance Management
search cancel

Missing Memory Items and Data from Blue Coat SG200 Proxy in Performance Management

book

Article ID: 206593

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

We have Blue Coat SG200 Proxy devices that we need to monitor and alert for cpu and memory utilization.

I'm not able to see Memory graphs in DX NetOps Performance Management even though it says it is supported.

The Blue Coat Proxy Server Memory Vendor Certification shows as Supported but has no Items.

Blue Coat SG200 Proxy devices have no Memory data.

Environment

All supported DX NetOps Performance Management releases

Cause

The deviceUsageName MIB OID at 1.3.6.1.4.1.3417.2.4.1.1.1.3 contains numeric values.

Resolution

The Blue Coat Proxy Server Memory Vendor Certification requires the deviceUsageName OID values to create Items for Polling.

The deviceUsageName MIB OID is defined as:

deviceUsageName OBJECT-TYPE
 SYNTAX  DisplayString
 MAX-ACCESS read-only
 STATUS  current
 DESCRIPTION: "The textual name of the resource i.e. Disk."
 ::= { deviceUsageEntry 3  }

The Names and Filter Expressions from the Vendor Certification are:

  • Names: <Expression destAttr="Names">"Blue-Coat-Proxy-Server-"+deviceUsageName</Expression>
  • Filter: <Filter>(deviceUsageName.toString().toLowerCase() contains "mem")</Filter>

This means we take the value from deviceUsageName, make it lower case and verify it contains "mem".

In this case we see the device returning the following numeric values for that OID when textual ones are expected.

SnmpResponseVariable [oid=1.3.6.1.4.1.3417.2.4.1.1.1.3, type=OCTET_STRING, value={{67,80,85},{68,105,115,107}}, isDelta=false, isList=true, error=SUCCESS, isDynamicIndex=false, indexList=[1, 2]]

Values returned from a working device would contain something like this, where we'd see CPU and Disk items created, but no Memory items without an index containing "mem" in the deviceUsageName OID values.

1.3.6.1.4.1.3417.2.4.1.1.1.3.1, OctetString , RO , fixed(CPU)
1.3.6.1.4.1.3417.2.4.1.1.1.3.2, OctetString , RO , fixed(Disk)

Resolve the issue with the non-textual values set on the deviceUsageName OID and the items should be discovered and polled.