Cisco ASR1002-HX is discovered with an incorrect number of CPUs in DX Netops Performance Management

Products

• CA Infrastructure Management
• CA Performance Management
• Network Observability

Issue/Introduction

Cisco ASR1002-HX is discovered with an incorrect number of CPUs in DX Netops Performance Management

Environment

Release : 3.7

Component : IM Reporting / Admin / Configuration

Cause

The MIB is only reporting one CPU

Resolution

Cisco CPU VC

Location:

http://<DAorPROXY:8581/typecatalog/certifications/snmp/CiscoCPUMib

Contents:

<?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.0</Version>
    <FacetType name="CiscoCPUMib" descriptorClass="com.ca.im.core.datamodel.certs.CertificationFacetDescriptorImpl">
        <Documentation>Supports CPUs based on the Cisco CPU table using CPU load average(average number of processes in queue).</Documentation>
        <FacetOf namespace="http://im.ca.com/core" name="Item" />
        <AttributeGroup name="cpmCPUTotalTable" external="true" list="true">
            <Documentation />
            <Attribute name="cpmCPUIndex" type="ObjectID">
                <Documentation />
                <IsKey>true</IsKey>
                <IsIndex>true</IsIndex>
                <Source>1.3.6.1.4.1.9.9.109.1.1.1.1.25</Source>
                <Polled>true</Polled>
            </Attribute>
            <Attribute name="cpmCPULoadAvg1min" type="Long">
                <Documentation />
                <IsKey>false</IsKey>
                <Source>1.3.6.1.4.1.9.9.109.1.1.1.1.24</Source>
            </Attribute>
            <Attribute name="cpmCPULoadAvg5min" type="Long">
                <Documentation />
                <IsKey>true</IsKey>
                <Source>1.3.6.1.4.1.9.9.109.1.1.1.1.25</Source>
            </Attribute>
            <Attribute name="cpmCPULoadAvg15min" type="Long">
                <Documentation />
                <IsKey>false</IsKey>
                <Source>1.3.6.1.4.1.9.9.109.1.1.1.1.26</Source>
            </Attribute>
            <Attribute name="cpmCPUTotal5min" type="Long">
                <Documentation />
                <IsKey>false</IsKey>
                <Source>1.3.6.1.4.1.9.9.109.1.1.1.1.5</Source>
                <Polled>true</Polled>
            </Attribute>
            <Attribute name="cpmCPUTotal5minRev" type="Long">
                <Documentation />
                <IsKey>false</IsKey>
                <Source>1.3.6.1.4.1.9.9.109.1.1.1.1.8</Source>
                <Polled>true</Polled>
            </Attribute>
        </AttributeGroup>
        <Protocol>SNMP</Protocol>
        <MIB>CISCO-PROCESS-MIB</MIB>
        <DisplayName>Cisco CPU</DisplayName>
        <Expressions>
            <ExpressionGroup destCert="{http://im.ca.com/normalizer}NormalizedCPUInfo" name="CiscoNRMCpuDS">
                <Expression destAttr="Indexes">cpmCPUIndex</Expression>
                <Expression destAttr="Names">"CPU " + cpmCPUIndex</Expression>
                <Expression destAttr="Descriptions">"Cisco CPU Statistics " + cpmCPUIndex</Expression>
                <Expression destAttr="Utilization">isdef (cpmCPUTotal5minRev) ? cpmCPUTotal5minRev : cpmCPUTotal5min</Expression>
            </ExpressionGroup>
        </Expressions>
    </FacetType>
</DataModel>

Looking at the Vendor Certification there is one isKey OID (isKey must be present), this is also the OID used for SNMP indexing.

           <Attribute name="cpmCPUIndex" type="ObjectID">
                <Documentation />
                <IsKey>true</IsKey>
                <IsIndex>true</IsIndex>
                <Source>1.3.6.1.4.1.9.9.109.1.1.1.1.25</Source>
                <Polled>true</Polled>
            </Attribute>

     <Attribute name="cpmCPULoadAvg5min" type="Long">
                <Documentation />
                <IsKey>true</IsKey>
                <Source>1.3.6.1.4.1.9.9.109.1.1.1.1.25</Source>
            </Attribute>

So if you walk this OID, each CPU reported by the MIB would have its own index.

If there is only one index, there will be one CPU discovered and so on.