ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

No Memory utilization on Bluecoats SG400 & SG500 in CA Performance Management

book

Article ID: 186584

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

We have a few Bluecoat devices for which we are not getting any memory utilization in PM.


 

 

Cause

Here is the Vendor Certification (VC) for Blue Coat Proxy Server Memory:

<?xml version="1.0" encoding="UTF-8"?>
<!--Auto-generated by the type catalog local manager.-->
<DataModel namespace="http://im.ca.com/certifications/snmp" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="SNMPCertificationFacet.xsd">
    <Author>CA</Author>
    <Version>1.1</Version>
    <FacetType name="BlueCoatProxyServerMemoryMib" descriptorClass="com.ca.im.core.datamodel.certs.CertificationFacetDescriptorImpl">
        <Documentation>Support for Blue Coat Proxy Server Memory.</Documentation>
        <FacetOf namespace="http://im.ca.com/core" name="Item" />
        <AttributeGroup name="BlueCoatProxyServerMemoryGroup" external="true" list="true">
            <Documentation />
            <Attribute name="Index" type="ObjectID">
                <Documentation />
                <IsKey>true</IsKey>
                <IsIndex>true</IsIndex>
                <Source>1.3.6.1.4.1.3417.2.4.1.1.1.4</Source>
            </Attribute>
            <Attribute name="deviceUsagePercent" type="Double">
                <Documentation />
                <IsKey>false</IsKey>
                <NeedsDelta>false</NeedsDelta>
                <Source>1.3.6.1.4.1.3417.2.4.1.1.1.4</Source>
            </Attribute>
            <Attribute name="deviceUsageName" type="OctetString">
                <Documentation />
                <IsKey>false</IsKey>
                <Source>1.3.6.1.4.1.3417.2.4.1.1.1.3</Source>
            </Attribute>
        </AttributeGroup>
        <DisplayName>Blue Coat Proxy Server Memory</DisplayName>
        <Protocol>SNMP</Protocol>
        <MIB>BLUE-COAT-PROXY-SERVER-MEMORY-MIB</MIB>
        <Expressions>
            <ExpressionGroup name="BlueCoatProxyServerMemoryDS" destCert="{http://im.ca.com/normalizer}NormalizedMemoryInfo">
                <Filter>(deviceUsageName.toString().toLowerCase() contains "mem")</Filter>
                <Expression destAttr="Indexes">Index</Expression>
                <Expression destAttr="Names">"Blue-Coat-Proxy-Server-"+deviceUsageName</Expression>
                <Expression destAttr="Descriptions">"Blue-Coat-Proxy-Server-"+deviceUsageName</Expression>
                <Expression destAttr="Utilization">deviceUsagePercent</Expression>
            </ExpressionGroup>
        </Expressions>
    </FacetType>
</DataModel>

THat can be found at the follwong url:

http://<DA>:8581/typecatalog/certifications/snmp/BlueCoatProxyServerMemoryMib

If you have a Fault Tolerant DA setup, use the proxy instead of the DA.

The Metric Family (MF) and VC are showing as supported because the isKey OID (1.3.6.1.4.1.3417.2.4.1.1.1.4) is returned by the device:

         <Attribute name="Index" type="ObjectID">
                <Documentation />
                <IsKey>true</IsKey>
                <IsIndex>true</IsIndex>
                <Source>1.3.6.1.4.1.3417.2.4.1.1.1.4</Source>
            </Attribute>
  
All isKey OIDs must be present for the VC to apply.

But later on there is a filter based on 1.3.6.1.4.1.3417.2.4.1.1.1.3 that looks for mem:

                <Filter>(deviceUsageName.toString().toLowerCase() contains "mem")</Filter>

To make sure that we are only creating the components for memory.

The devices are not showing anything that matches the filter:
 
Example:

SG500
1.3.6.1.4.1.3417.2.4.1.1.1.4.1, Integer     , 20 <----- The isKey oid os present so the MF/VC show as supported
1.3.6.1.4.1.3417.2.4.1.1.1.4.2, Integer     , 42


1.3.6.1.4.1.3417.2.4.1.1.1.3.1, OctetString , CPU    <--- No memory entry, only CPU and Disk so nothing passes the filter
1.3.6.1.4.1.3417.2.4.1.1.1.3.2, OctetString , Disk


SG400:

1.3.6.1.4.1.3417.2.4.1.1.1.4.1, Integer     , 23    <----- The isKey oid os present so the MF/VC show as supported
1.3.6.1.4.1.3417.2.4.1.1.1.4.2, Integer     , 12

1.3.6.1.4.1.3417.2.4.1.1.1.3.1, OctetString , CPU   <--- No memory entry, only CPU an disk, so nothing passes the filter
1.3.6.1.4.1.3417.2.4.1.1.1.3.2, OctetString , Disk

So as there is no entry for Memory on these devices in the MIB, no Memory components are created.

Environment

Release : 3.7

Component : IM Reporting / Admin / Configuration

Resolution

Consult the device vendor on why the OIDs are not present.