Smarts IP: There is a known Cisco bug with ciscoMemoryPoolName OID, is there a way to prevent polling? How do I prevent polling ciscoMemoryPoolName OID
search cancel

Smarts IP: There is a known Cisco bug with ciscoMemoryPoolName OID, is there a way to prevent polling? How do I prevent polling ciscoMemoryPoolName OID

book

Article ID: 331964

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:




There is a known Cisco bug (CSCtx43501), that causes high memory utilization on ASA devices when ciscoMemoryPoolName OID is polled.  This article will explain how to prevent Smarts from polling the OID.

Environment

VMware Smart Assurance - SMARTS

Cause

Cisco bug

Resolution

To prevent Smarts IP from  polling this OID you will need to edit the DISCOVERY_CISCO.import.

When editing this file please use the sm_edit function. (ie <base>/bin/sm_edit -s<domain name> ..conf/discovery/DISCOVEY_CISCO.import

GA_Driver::Performance-Cisco-Router-Driver {
ReadsRulesFrom = GA_RuleSet::Performance-Cisco-Router-RS

{ fileName = "discovery/ic-cisco-router-health.asl" }

ReadsInputFrom = SNMP_WalkFE::Performance-Cisco-Router-FE {
rootOIDs = {

  1. cpmCPUTotal5minRev # CPU will be created using cpmCPUTotal5minRev by default
    { 5, ".1.3.6.1.4.1.9.9.109.1.1.1.1.8" }

    ,

  2. cpmCPUTotal5minOID
    { 10, ".1.3.6.1.4.1.9.9.109.1.1.1.1.5"}

    , # CPU will be created using cpmCPUTotal5min when there's no data for cpmCPUTotal5minRev

  3. avgBusy1
    { 15, ".1.3.6.1.4.1.9.2.1.57" }

    , # CPU will be created using avgBusy1 when there's no data for cpmCPUTotal5minRev and cpmCPUTotal5min

  4. ciscoMemoryPoolName
    { 20, ".1.3.6.1.4.1.9.9.48.1.1.1.2" },
    # freeMem
    { 25, ".1.3.6.1.4.1.9.2.1.8" },

    Please comment out the line:  { 20, ".1.3.6.1.4.1.9.9.48.1.1.1.2" }

    This change will require a restart of AMPM domain.



Additional Information

Please not that as this OID is a basic CPU OID smarts will poll this OID in an AM domain as well.  Also please note that this will effect all Cisco Routers that use this OID. If you are concerned with this please contact Cisco to see if there is a resolution to the bug on their side.  This article is simply a workaround until the bug can be resolved.