9 Replies Latest reply: Jun 28, 2012 1:37 PM by Kevin Knight RSS

Cisco memory problem

Kevin Knight

I have several Cisco VG224s and Cisco 1900, 2900, and 3900 routers on my network.  When I run a file system report, Blade is giving me the wrong answer.  It is telling me that my device only has Xmb of dram, when in fact it has Ymb.  Does anyone have a solution?  Blade is using the show memory statistics to gather this information...and I am using show version.  I am wondering if you can setup a custom action or modify the action blade is using to take the output in the show version and perform a sum equation on it to provide the total dram installed.  here is a sample of what i am talking about

 

Blade Report:  CISCO2921/K9      nvram 262,136     148,237     113,899

 

Show Version:  Cisco CISCO2921/K9 (revision 1.0) with 466944K/57344Kbytes of memory.

 

Kevin Knight

Network Engineer

  • 1. Cisco memory problem
    Rahul

    Are you using any custom action..? If "Yes", which custom action you are using..?

  • 2. Cisco memory problem
    Kevin Knight

    No...I am just running a device inventory report and including the file system.

  • 3. Cisco memory problem
    Rahul

    Hello Kevin,

     

    You can create one custom action for show version command, take the help of BNA Developrs guide for developing new custom action.

     

    Thanks,

    Rahul

  • 4. Cisco memory problem
    Kevin Knight

    action and when i try to import the adapter, i am getting the following error...

               
                                                                                    Error :                                          Can't find resource for bundle java.util.PropertyResourceBundle, key customAction.get.SystemMemory                                                                       

                    Here is my Adapter...

    <?xml version="1.0" encoding="UTF-8"?>

    <!--

            BBNA Version : 8.1.03.000 b025 u002

            Exported Date : 05/22/12 16:07:58

            Enabled : Yes

            State : Baseline

            Requires Merge : No

            Last Modified :

            Annotation : -->

    <deviceTypeMap>

        <customDeviceCommandDeclaration>

            <!-- Get System Memory -->

            <name key="customAction.get.SystemMemory"/>

            <id>2007</id>

            <guid>7C34F790-C77A-37E1-BBCF-DD5644F70F32</guid>

            <groupName key="customAction.groupName.hardware"/>

            <browserExecutable>true</browserExecutable>

            <inspectionOnly>true</inspectionOnly>

            <classification>1</classification>

            <dynamicField>

                <name>DRAM</name>

                <sourceResult>result.pbid</sourceResult>

            </dynamicField>

            <dynamicField>

                <name>Flash</name>

                <sourceResult>result1.pbid</sourceResult>

            </dynamicField>

        </customDeviceCommandDeclaration>

        <!-- ================================================================== -->

        <deviceType>

            <guid>BE2B2D21-1CAA-53C3-05C3-CBB0A5D151B8</guid>

            <extension>true</extension>

            <deviceCommand>

                <!-- get system memory -->

                <guid>7C34F790-C77A-37E1-BBCF-DD5644F70F32</guid>

                <interaction>

                    <prompt>%prompt%</prompt>

                    <command>show ver</command>

                    <response>%prompt%</response>

                    <error>Invalid input</error>

                    <!-- capture buffer="Cisco\s\d+\s+.+ith\s+(\S+)\s+bytes of memory|(\S+)\s+bytes of\s+.+Flash" ignoreFailure="true"> -->

                    <capture

                        buffer="Cisco\s\d+\s+.+ith\s+(\S+)\s+bytes of memory|(\S+)\s+bytes of\s+.+Flash" ignoreFailure="true">

                        <property name="result.pbid">{1}</property>

                        <property name="result1.pbid">{2}</property>

                    </capture>

                </interaction>

            </deviceCommand>

        </deviceType>

    </deviceTypeMap>   

                 
  • 5. Cisco memory problem
    Kevin Knight

    well...i got the custom action to work...turns out that BNA is telling alot of wrong information when it comes to the ram memory of my cisco devices...at first i thought it was just VGs, then i found it was 1900s, 2900s, and 3900s.  THen i found it was 2800s.  Is there no end to the misinformation?  When doing software upgrades I would have relied heavily on the information BNA provided.  Now i rely on the information from MY custom job.  Millions invested into this product and I have to be the one to fix it.  Not a big BNA fan today.

     

    Anyone using this product should compare what BNA tells you and what the device actually tells you.  You might be surprised.

     

    Kevin

  • 6. Cisco memory problem
    Rahul

    Hey Kevin,

     

    As every customer has their own use cases, so its very difficult to manage every use cases in upcoming versions, and tht's why we have some customization to freeze our own requirements...

     

    Do open a ticket with support, they will take this is as an RFE and will consider the same in upcoming versions.

     

    Thanks,

    Rahul

  • 7. Re: Cisco memory problem
    Kevin Knight

    I am just running a device inventory report and including file systems under the hardware inventory section.

     

    Kevin Knight

    Network Services

    314-694-2817

  • 8. Re: Cisco memory problem
    James Smith

    The issue is the name.

     

     

     

    Then re-try

     

    James Smith "Smitty"

    Technical Support Analyst

    BMC Software, Inc.

    Support: 800-537-1813

    customer_support@bmc.com

  • 9. Re: Cisco memory problem
    Kevin Knight

    Just a FYI....I have opened a support ticket with BMC and they are going to open up a defect for this memory issue.

     

    Kevin