46 Replies Latest reply on Jun 2, 2010 11:38 PM by Andy Ng

    NPM shows different readings of RAM on server being monitored

    trebor11584

      Hi Guys,

      I don't know if this problem has been posted on this forum before nor if anyone has experienced the same. But, here it goes we are currently doing demo of NPM v10 to our prospective clients via their own net infrastracture, and right now this is still our problem. They have a Silverlake sofware residing on an IBM i520 machine which is being detected by NPM but the thing is it's showing different readings (capacity) on the RAM. I've coordinated this concern with their IT guy to verify the amount of RAM residing on their machine, and as per their IT guy the machine has 16Gig RAM's (4Gig per stick). I was wondering why it is only showing the RAM as 1Gig in capacity or sometimes a different value instead of showing it as fix 4Gig. I've uploaded screenshots for reference since I'm not really good in explaining (sorry). Hope someone could help me here, 'coz this problem has been on going for a long time now. TIA

      1st image shows the space utilize (82%) notice that If you add up value on the space and space used the RAM is equal to 1Gig of memory.

      on the image below, the utilization percentage is now "green" and notice that the value on the space column also change, it is now 1.465Gig which when I add up the value on the space used the total now would be around 2Gig.

      On the 3rd image below, RAM reading on space now reads as 2.603Gig while the space used is 897.504MB, which when added equals to roughy 3Gig.

        • Re: NPM shows different readings of RAM on server being monitored
          Andy Ng

          Hi trebor11584,

          size and space used does not add up get the total size of the volume.

          Instead, size is the total size of the volume.
          The percentage is derived from {spaced used / size}.

          As it is showing as volumes, the HOST-RESOURCE-MIB of the SNMP-agent should have records of it.

          The following is how we get the values that you are seeing:

          size = hrStorageSize x hrStorageAllocationUnits
          used space = hrStorageUsed x hrStorageAllocationUnits

          OIDs:
          hrStorageAllocationUnits = 1.3.6.1.2.1.25.2.3.1.4
          hrStorageSize = 1.3.6.1.2.1.25.2.3.1.5
          hrStorageUsed = 1.3.6.1.2.1.25.2.3.1.6

          Note that Orion NPM "sees" this information via the SNMP-agent, and not direct from the device.
          All that is showing in Orion NPM, are information that are supplied from the SNMP-agent.

          I do suspect that the SNMP-agent is causing this inconsistency.

          To investigate further, you might want to run a MIB walk (snmpwalk, etc.) against the device and check if the values for size is changing.
          MIB walk is available as a component in Engineer's Toolset that is available for evaluation.

          If confirmed that the SNMP-agent is causing the problem, the vendor should be approached.

          HTH.

            • Re: NPM shows different readings of RAM on server being monitored
              trebor11584

              Thanks for the quick response, I appreciate it.

              About your response, I just want to clarify something. Are you saying that what I'm seeing right now is not the physical RAM but rather the RAM on the disk drive? As per your first sentence below

              "size and space used does not add up get the total size of the volume. Instead, size is the total size of the volume."

              Also, I want to add up something on my previous post. As you notice, when the loading bar's value becomes smaller that is the time the size value becomes bigger (as per the image posted on the previous post).

              About the MIB walk, I'm not good on reading it so I really don't know which part of that should I check, so I decided to paste the results that I've got hoping that you could help me out and pin-point which part of it is wrong.

              MIBOIDNameValue
              DPI20-MIB1.3.6.1.4.1.2.2.1.1.0dpiPort.00
              DPI20-MIB1.3.6.1.4.1.2.2.1.1.1.0dpiPortForTCP.00
              DPI20-MIB1.3.6.1.4.1.2.2.1.1.2.0dpiPortForUDP.00
              DPI20-MIB1.3.6.1.4.1.2.2.12.1.0ibmDPI.12.1.05
              DPI20-MIB1.3.6.1.4.1.2.2.12.2.0ibmDPI.12.2.0300
              DPI20-MIB1.3.6.1.4.1.2.2.12.3.0ibmDPI.12.3.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.4.0ibmDPI.12.4.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.5.0ibmDPI.12.5.0228996
              DPI20-MIB1.3.6.1.4.1.2.2.12.6.0ibmDPI.12.6.0228996
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.1.1ibmDPI.12.7.1.1.11
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.2.1ibmDPI.12.7.1.2.11.3.6.1.4.1.2.6.11.2
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.3.1ibmDPI.12.7.1.3.1as400SubagentRouter
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.4.1ibmDPI.12.7.1.4.11
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.5.1ibmDPI.12.7.1.5.141
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.6.1ibmDPI.12.7.1.6.11
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.7.1ibmDPI.12.7.1.7.12
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.8.1ibmDPI.12.7.1.8.10
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.9.1ibmDPI.12.7.1.9.13
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.10.1ibmDPI.12.7.1.10.1øâõô×âáø@@`øäâùâèâ@@@
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.11.1ibmDPI.12.7.1.11.1120
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.12.1ibmDPI.12.7.1.12.10
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.13.1ibmDPI.12.7.1.13.1228996
              DPI20-MIB1.3.6.1.4.1.2.2.12.7.1.14.1ibmDPI.12.7.1.14.1228996
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.1.1.3.6.1.2.1.25.0ibmDPI.12.8.1.1.1.3.6.1.2.1.25.01.3.6.1.2.1.25
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.1.1.3.6.1.4.1.2.6.2.13.0ibmDPI.12.8.1.1.1.3.6.1.4.1.2.6.2.13.01.3.6.1.4.1.2.6.2.13
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.1.1.3.6.1.4.1.2.6.4.5.0ibmDPI.12.8.1.1.1.3.6.1.4.1.2.6.4.5.01.3.6.1.4.1.2.6.4.5
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.1.1.3.6.1.4.1.2.6.11.1.0ibmDPI.12.8.1.1.1.3.6.1.4.1.2.6.11.1.01.3.6.1.4.1.2.6.11.1
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.1.1.3.6.1.4.1.2.6.50.0ibmDPI.12.8.1.1.1.3.6.1.4.1.2.6.50.01.3.6.1.4.1.2.6.50
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.2.1.3.6.1.2.1.25.0ibmDPI.12.8.1.2.1.3.6.1.2.1.25.00
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.2.1.3.6.1.4.1.2.6.2.13.0ibmDPI.12.8.1.2.1.3.6.1.4.1.2.6.2.13.00
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.2.1.3.6.1.4.1.2.6.4.5.0ibmDPI.12.8.1.2.1.3.6.1.4.1.2.6.4.5.00
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.2.1.3.6.1.4.1.2.6.11.1.0ibmDPI.12.8.1.2.1.3.6.1.4.1.2.6.11.1.00
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.2.1.3.6.1.4.1.2.6.50.0ibmDPI.12.8.1.2.1.3.6.1.4.1.2.6.50.00
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.3.1.3.6.1.2.1.25.0ibmDPI.12.8.1.3.1.3.6.1.2.1.25.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.3.1.3.6.1.4.1.2.6.2.13.0ibmDPI.12.8.1.3.1.3.6.1.4.1.2.6.2.13.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.3.1.3.6.1.4.1.2.6.4.5.0ibmDPI.12.8.1.3.1.3.6.1.4.1.2.6.4.5.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.3.1.3.6.1.4.1.2.6.11.1.0ibmDPI.12.8.1.3.1.3.6.1.4.1.2.6.11.1.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.3.1.3.6.1.4.1.2.6.50.0ibmDPI.12.8.1.3.1.3.6.1.4.1.2.6.50.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.4.1.3.6.1.2.1.25.0ibmDPI.12.8.1.4.1.3.6.1.2.1.25.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.4.1.3.6.1.4.1.2.6.2.13.0ibmDPI.12.8.1.4.1.3.6.1.4.1.2.6.2.13.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.4.1.3.6.1.4.1.2.6.4.5.0ibmDPI.12.8.1.4.1.3.6.1.4.1.2.6.4.5.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.4.1.3.6.1.4.1.2.6.11.1.0ibmDPI.12.8.1.4.1.3.6.1.4.1.2.6.11.1.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.4.1.3.6.1.4.1.2.6.50.0ibmDPI.12.8.1.4.1.3.6.1.4.1.2.6.50.01
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.5.1.3.6.1.2.1.25.0ibmDPI.12.8.1.5.1.3.6.1.2.1.25.0120
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.5.1.3.6.1.4.1.2.6.2.13.0ibmDPI.12.8.1.5.1.3.6.1.4.1.2.6.2.13.0120
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.5.1.3.6.1.4.1.2.6.4.5.0ibmDPI.12.8.1.5.1.3.6.1.4.1.2.6.4.5.0120
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.5.1.3.6.1.4.1.2.6.11.1.0ibmDPI.12.8.1.5.1.3.6.1.4.1.2.6.11.1.0120
              DPI20-MIB1.3.6.1.4.1.2.2.12.8.1.5.1.3.6.1.4.1.2.6.50.0ibmDPI.12.8.1.5.1.3.6.1.4.1.2.6.50.0120
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.1.0ibmappnNodeCpName.0APPN.S10FC9FC
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.2.0ibmappnNodeNetid.0APPN
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.3.0ibmappnNodeBlockNum.056
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.4.0ibmappnNodeIdNum.00
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.5.0ibmappnNodeType.02
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.6.0ibmappnNodeUpTime.0282734104
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.7.0ibmappnNodeNegotLs.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.8.0ibmappnNodeSegReasm.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.9.0ibmappnNodeBindReasm.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.10.0ibmappnNodeParallelTg.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.11.0ibmappnNodeService.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.12.0ibmappnNodeAdaptiveBindPacing.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.13.0ibmappnGeneralInfoAndCaps.13.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.14.0ibmappnGeneralInfoAndCaps.14.02
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.1.15.0ibmappnGeneralInfoAndCaps.15.00
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.3.1.0ibmappnNodeEnSegGen.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.3.2.0ibmappnNodeEnModeCosMap.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.3.3.0ibmappnNodeEnLocateCdinit.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.3.4.0ibmappnNodeEnSendRegNames.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.3.5.0ibmappnNodeEnSendRegChar.01
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.3.6.0ibmappnEnUniqueCaps.6.0
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.1.6.81.49.80.76.73.78ibmappnNodePortName.6.81.49.80.76.73.78Q1PLIN
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.1.7.69.84.72.76.73.78.69ibmappnNodePortName.7.69.84.72.76.73.78.69ETHLINE
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.1.7.81.69.83.76.73.78.69ibmappnNodePortName.7.81.69.83.76.73.78.69QESLINE
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.1.7.81.84.73.76.73.78.69ibmappnNodePortName.7.81.84.73.76.73.78.69QTILINE
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.1.8.69.84.72.76.73.78.69.50ibmappnNodePortName.8.69.84.72.76.73.78.69.50ETHLINE2
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.1.8.69.84.72.76.73.78.69.51ibmappnNodePortName.8.69.84.72.76.73.78.69.51ETHLINE3
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.1.8.69.84.72.76.73.78.69.52ibmappnNodePortName.8.69.84.72.76.73.78.69.52ETHLINE4
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.1.8.69.84.72.76.73.78.69.53ibmappnNodePortName.8.69.84.72.76.73.78.69.53ETHLINE5
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.2.6.81.49.80.76.73.78ibmappnNodePortState.6.81.49.80.76.73.781
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.2.7.69.84.72.76.73.78.69ibmappnNodePortState.7.69.84.72.76.73.78.693
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.2.7.81.69.83.76.73.78.69ibmappnNodePortState.7.81.69.83.76.73.78.691
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.2.7.81.84.73.76.73.78.69ibmappnNodePortState.7.81.84.73.76.73.78.691
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.2.8.69.84.72.76.73.78.69.50ibmappnNodePortState.8.69.84.72.76.73.78.69.503
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.2.8.69.84.72.76.73.78.69.51ibmappnNodePortState.8.69.84.72.76.73.78.69.513
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.2.8.69.84.72.76.73.78.69.52ibmappnNodePortState.8.69.84.72.76.73.78.69.521
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.2.8.69.84.72.76.73.78.69.53ibmappnNodePortState.8.69.84.72.76.73.78.69.531
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.3.6.81.49.80.76.73.78ibmappnNodePortDlcType.6.81.49.80.76.73.782
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.3.7.69.84.72.76.73.78.69ibmappnNodePortDlcType.7.69.84.72.76.73.78.695
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.3.7.81.69.83.76.73.78.69ibmappnNodePortDlcType.7.81.69.83.76.73.78.692
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.3.7.81.84.73.76.73.78.69ibmappnNodePortDlcType.7.81.84.73.76.73.78.692
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.3.8.69.84.72.76.73.78.69.50ibmappnNodePortDlcType.8.69.84.72.76.73.78.69.505
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.3.8.69.84.72.76.73.78.69.51ibmappnNodePortDlcType.8.69.84.72.76.73.78.69.515
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.3.8.69.84.72.76.73.78.69.52ibmappnNodePortDlcType.8.69.84.72.76.73.78.69.525
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.3.8.69.84.72.76.73.78.69.53ibmappnNodePortDlcType.8.69.84.72.76.73.78.69.535
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.4.6.81.49.80.76.73.78ibmappnNodePortPortType.6.81.49.80.76.73.782
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.4.7.69.84.72.76.73.78.69ibmappnNodePortPortType.7.69.84.72.76.73.78.693
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.4.7.81.69.83.76.73.78.69ibmappnNodePortPortType.7.81.69.83.76.73.78.692
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.4.7.81.84.73.76.73.78.69ibmappnNodePortPortType.7.81.84.73.76.73.78.692
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.4.8.69.84.72.76.73.78.69.50ibmappnNodePortPortType.8.69.84.72.76.73.78.69.503
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.4.8.69.84.72.76.73.78.69.51ibmappnNodePortPortType.8.69.84.72.76.73.78.69.513
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.4.8.69.84.72.76.73.78.69.52ibmappnNodePortPortType.8.69.84.72.76.73.78.69.523
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.4.8.69.84.72.76.73.78.69.53ibmappnNodePortPortType.8.69.84.72.76.73.78.69.533
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.6.6.81.49.80.76.73.78ibmappnNodePortLsRole.6.81.49.80.76.73.782
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.6.7.69.84.72.76.73.78.69ibmappnNodePortLsRole.7.69.84.72.76.73.78.693
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.6.7.81.69.83.76.73.78.69ibmappnNodePortLsRole.7.81.69.83.76.73.78.692
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.6.7.81.84.73.76.73.78.69ibmappnNodePortLsRole.7.81.84.73.76.73.78.692
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.6.8.69.84.72.76.73.78.69.50ibmappnNodePortLsRole.8.69.84.72.76.73.78.69.503
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.6.8.69.84.72.76.73.78.69.51ibmappnNodePortLsRole.8.69.84.72.76.73.78.69.513
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.6.8.69.84.72.76.73.78.69.52ibmappnNodePortLsRole.8.69.84.72.76.73.78.69.523
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.6.8.69.84.72.76.73.78.69.53ibmappnNodePortLsRole.8.69.84.72.76.73.78.69.533
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.7.6.81.49.80.76.73.78ibmappnNodePortMaxRcvBtuSize.6.81.49.80.76.73.78521
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.7.7.69.84.72.76.73.78.69ibmappnNodePortMaxRcvBtuSize.7.69.84.72.76.73.78.691496
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.7.7.81.69.83.76.73.78.69ibmappnNodePortMaxRcvBtuSize.7.81.69.83.76.73.78.69521
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.7.7.81.84.73.76.73.78.69ibmappnNodePortMaxRcvBtuSize.7.81.84.73.76.73.78.69521
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.7.8.69.84.72.76.73.78.69.50ibmappnNodePortMaxRcvBtuSize.8.69.84.72.76.73.78.69.501496
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.7.8.69.84.72.76.73.78.69.51ibmappnNodePortMaxRcvBtuSize.8.69.84.72.76.73.78.69.511496
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.7.8.69.84.72.76.73.78.69.52ibmappnNodePortMaxRcvBtuSize.8.69.84.72.76.73.78.69.521496
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.4.1.1.7.8.69.84.72.76.73.78.69.53ibmappnNodePortMaxRcvBtuSize.8.69.84.72.76.73.78.69.531496
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.1.8.69.84.72.76.73.78.69.50ibmappnNodeLsName.8.69.84.72.76.73.78.69.50ETHLINE2
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.1.8.69.84.72.76.73.78.69.51ibmappnNodeLsName.8.69.84.72.76.73.78.69.51ETHLINE3
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.1.8.69.84.72.76.73.78.69.52ibmappnNodeLsName.8.69.84.72.76.73.78.69.52ETHLINE4
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.1.8.69.84.72.76.73.78.69.53ibmappnNodeLsName.8.69.84.72.76.73.78.69.53ETHLINE5
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.2.8.69.84.72.76.73.78.69.50ibmappnNodeLsPortName.8.69.84.72.76.73.78.69.50ETHLINE2
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.2.8.69.84.72.76.73.78.69.51ibmappnNodeLsPortName.8.69.84.72.76.73.78.69.51ETHLINE3
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.2.8.69.84.72.76.73.78.69.52ibmappnNodeLsPortName.8.69.84.72.76.73.78.69.52ETHLINE4
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.2.8.69.84.72.76.73.78.69.53ibmappnNodeLsPortName.8.69.84.72.76.73.78.69.53ETHLINE5
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.3.8.69.84.72.76.73.78.69.50ibmappnNodeLsDlcType.8.69.84.72.76.73.78.69.505
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.3.8.69.84.72.76.73.78.69.51ibmappnNodeLsDlcType.8.69.84.72.76.73.78.69.515
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.3.8.69.84.72.76.73.78.69.52ibmappnNodeLsDlcType.8.69.84.72.76.73.78.69.525
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.3.8.69.84.72.76.73.78.69.53ibmappnNodeLsDlcType.8.69.84.72.76.73.78.69.535
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.4.8.69.84.72.76.73.78.69.50ibmappnNodeLsDynamic.8.69.84.72.76.73.78.69.502
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.4.8.69.84.72.76.73.78.69.51ibmappnNodeLsDynamic.8.69.84.72.76.73.78.69.512
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.4.8.69.84.72.76.73.78.69.52ibmappnNodeLsDynamic.8.69.84.72.76.73.78.69.522
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.4.8.69.84.72.76.73.78.69.53ibmappnNodeLsDynamic.8.69.84.72.76.73.78.69.532
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.5.8.69.84.72.76.73.78.69.50ibmappnNodeLsState.8.69.84.72.76.73.78.69.503
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.5.8.69.84.72.76.73.78.69.51ibmappnNodeLsState.8.69.84.72.76.73.78.69.513
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.5.8.69.84.72.76.73.78.69.52ibmappnNodeLsState.8.69.84.72.76.73.78.69.523
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.5.8.69.84.72.76.73.78.69.53ibmappnNodeLsState.8.69.84.72.76.73.78.69.533
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.6.8.69.84.72.76.73.78.69.50ibmappnNodeLsCpName.8.69.84.72.76.73.78.69.50APPN.
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.6.8.69.84.72.76.73.78.69.51ibmappnNodeLsCpName.8.69.84.72.76.73.78.69.51APPN.
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.6.8.69.84.72.76.73.78.69.52ibmappnNodeLsCpName.8.69.84.72.76.73.78.69.52APPN.
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.6.8.69.84.72.76.73.78.69.53ibmappnNodeLsCpName.8.69.84.72.76.73.78.69.53APPN.
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.7.8.69.84.72.76.73.78.69.50ibmappnNodeLsTgNum.8.69.84.72.76.73.78.69.501
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.7.8.69.84.72.76.73.78.69.51ibmappnNodeLsTgNum.8.69.84.72.76.73.78.69.511
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.7.8.69.84.72.76.73.78.69.52ibmappnNodeLsTgNum.8.69.84.72.76.73.78.69.521
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.7.8.69.84.72.76.73.78.69.53ibmappnNodeLsTgNum.8.69.84.72.76.73.78.69.531
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.8.8.69.84.72.76.73.78.69.50ibmappnNodeLsLimResource.8.69.84.72.76.73.78.69.502
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.8.8.69.84.72.76.73.78.69.51ibmappnNodeLsLimResource.8.69.84.72.76.73.78.69.512
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.8.8.69.84.72.76.73.78.69.52ibmappnNodeLsLimResource.8.69.84.72.76.73.78.69.522
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.8.8.69.84.72.76.73.78.69.53ibmappnNodeLsLimResource.8.69.84.72.76.73.78.69.532
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.10.8.69.84.72.76.73.78.69.50ibmappnNodeLsBlockNum.8.69.84.72.76.73.78.69.500
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.10.8.69.84.72.76.73.78.69.51ibmappnNodeLsBlockNum.8.69.84.72.76.73.78.69.510
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.10.8.69.84.72.76.73.78.69.52ibmappnNodeLsBlockNum.8.69.84.72.76.73.78.69.520
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.10.8.69.84.72.76.73.78.69.53ibmappnNodeLsBlockNum.8.69.84.72.76.73.78.69.530
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.11.8.69.84.72.76.73.78.69.50ibmappnNodeLsIdNum.8.69.84.72.76.73.78.69.500
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.11.8.69.84.72.76.73.78.69.51ibmappnNodeLsIdNum.8.69.84.72.76.73.78.69.510
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.11.8.69.84.72.76.73.78.69.52ibmappnNodeLsIdNum.8.69.84.72.76.73.78.69.520
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.11.8.69.84.72.76.73.78.69.53ibmappnNodeLsIdNum.8.69.84.72.76.73.78.69.530
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.12.8.69.84.72.76.73.78.69.50ibmappnNodeLsCpCpSession.8.69.84.72.76.73.78.69.501
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.12.8.69.84.72.76.73.78.69.51ibmappnNodeLsCpCpSession.8.69.84.72.76.73.78.69.511
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.12.8.69.84.72.76.73.78.69.52ibmappnNodeLsCpCpSession.8.69.84.72.76.73.78.69.521
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.12.8.69.84.72.76.73.78.69.53ibmappnNodeLsCpCpSession.8.69.84.72.76.73.78.69.531
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.15.8.69.84.72.76.73.78.69.50ibmappnNodeLsEffCap.8.69.84.72.76.73.78.69.500
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.15.8.69.84.72.76.73.78.69.51ibmappnNodeLsEffCap.8.69.84.72.76.73.78.69.510
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.15.8.69.84.72.76.73.78.69.52ibmappnNodeLsEffCap.8.69.84.72.76.73.78.69.520
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.15.8.69.84.72.76.73.78.69.53ibmappnNodeLsEffCap.8.69.84.72.76.73.78.69.530
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.16.8.69.84.72.76.73.78.69.50ibmappnNodeLsConnCost.8.69.84.72.76.73.78.69.500
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.16.8.69.84.72.76.73.78.69.51ibmappnNodeLsConnCost.8.69.84.72.76.73.78.69.510
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.16.8.69.84.72.76.73.78.69.52ibmappnNodeLsConnCost.8.69.84.72.76.73.78.69.520
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.16.8.69.84.72.76.73.78.69.53ibmappnNodeLsConnCost.8.69.84.72.76.73.78.69.530
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.17.8.69.84.72.76.73.78.69.50ibmappnNodeLsByteCost.8.69.84.72.76.73.78.69.500
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.17.8.69.84.72.76.73.78.69.51ibmappnNodeLsByteCost.8.69.84.72.76.73.78.69.510
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.17.8.69.84.72.76.73.78.69.52ibmappnNodeLsByteCost.8.69.84.72.76.73.78.69.520
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.17.8.69.84.72.76.73.78.69.53ibmappnNodeLsByteCost.8.69.84.72.76.73.78.69.530
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.18.8.69.84.72.76.73.78.69.50ibmappnNodeLsSecurity.8.69.84.72.76.73.78.69.501
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.18.8.69.84.72.76.73.78.69.51ibmappnNodeLsSecurity.8.69.84.72.76.73.78.69.511
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.18.8.69.84.72.76.73.78.69.52ibmappnNodeLsSecurity.8.69.84.72.76.73.78.69.521
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.18.8.69.84.72.76.73.78.69.53ibmappnNodeLsSecurity.8.69.84.72.76.73.78.69.531
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.19.8.69.84.72.76.73.78.69.50ibmappnNodeLsDelay.8.69.84.72.76.73.78.69.50384
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.19.8.69.84.72.76.73.78.69.51ibmappnNodeLsDelay.8.69.84.72.76.73.78.69.51384
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.19.8.69.84.72.76.73.78.69.52ibmappnNodeLsDelay.8.69.84.72.76.73.78.69.52384
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.19.8.69.84.72.76.73.78.69.53ibmappnNodeLsDelay.8.69.84.72.76.73.78.69.53384
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.20.8.69.84.72.76.73.78.69.50ibmappnNodeLsUsr1.8.69.84.72.76.73.78.69.50128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.20.8.69.84.72.76.73.78.69.51ibmappnNodeLsUsr1.8.69.84.72.76.73.78.69.51128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.20.8.69.84.72.76.73.78.69.52ibmappnNodeLsUsr1.8.69.84.72.76.73.78.69.52128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.20.8.69.84.72.76.73.78.69.53ibmappnNodeLsUsr1.8.69.84.72.76.73.78.69.53128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.21.8.69.84.72.76.73.78.69.50ibmappnNodeLsUsr2.8.69.84.72.76.73.78.69.50128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.21.8.69.84.72.76.73.78.69.51ibmappnNodeLsUsr2.8.69.84.72.76.73.78.69.51128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.21.8.69.84.72.76.73.78.69.52ibmappnNodeLsUsr2.8.69.84.72.76.73.78.69.52128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.21.8.69.84.72.76.73.78.69.53ibmappnNodeLsUsr2.8.69.84.72.76.73.78.69.53128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.22.8.69.84.72.76.73.78.69.50ibmappnNodeLsUsr3.8.69.84.72.76.73.78.69.50128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.22.8.69.84.72.76.73.78.69.51ibmappnNodeLsUsr3.8.69.84.72.76.73.78.69.51128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.22.8.69.84.72.76.73.78.69.52ibmappnNodeLsUsr3.8.69.84.72.76.73.78.69.52128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.22.8.69.84.72.76.73.78.69.53ibmappnNodeLsUsr3.8.69.84.72.76.73.78.69.53128
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.43.8.69.84.72.76.73.78.69.50ibmappnNodeLsEntry.43.8.69.84.72.76.73.78.69.501
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.43.8.69.84.72.76.73.78.69.51ibmappnNodeLsEntry.43.8.69.84.72.76.73.78.69.511
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.43.8.69.84.72.76.73.78.69.52ibmappnNodeLsEntry.43.8.69.84.72.76.73.78.69.521
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.43.8.69.84.72.76.73.78.69.53ibmappnNodeLsEntry.43.8.69.84.72.76.73.78.69.531
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.45.8.69.84.72.76.73.78.69.50ibmappnNodeLsEntry.45.8.69.84.72.76.73.78.69.502
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.45.8.69.84.72.76.73.78.69.51ibmappnNodeLsEntry.45.8.69.84.72.76.73.78.69.512
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.45.8.69.84.72.76.73.78.69.52ibmappnNodeLsEntry.45.8.69.84.72.76.73.78.69.522
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.5.1.1.45.8.69.84.72.76.73.78.69.53ibmappnNodeLsEntry.45.8.69.84.72.76.73.78.69.532
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.6.1.0ibmappnSnmpInPkts.0485
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.6.2.0ibmappnSnmpInGetRequests.00
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.6.3.0ibmappnSnmpInGetNexts.0487
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.6.4.0ibmappnSnmpInSetRequests.00
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.6.5.0ibmappnSnmpInTotalVars.0489
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.6.6.0ibmappnSnmpInGetVars.00
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.6.7.0ibmappnSnmpInGetNextVars.0491
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.6.8.0ibmappnSnmpInSetVars.00
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.6.9.0ibmappnSnmpOutNoSuchNames.00
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.1.6.10.0ibmappnSnmpOutGenErrs.00
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.3.1.1.1.0ibmappnLocalNodeName.0APPN.S10FC9FC
              IBM-6611-APPN-MIB1.3.6.1.4.1.2.6.2.13.3.1.1.2.0ibmappnLocalNodeType.02
              NV6000-MIB1.3.6.1.4.1.2.6.4.5.1.0nv6saComputerSystemLoad.03090
              IBM-MIB1.3.6.1.4.1.2.6.11.1.99.1.0as400Agent.1.99.1.00

                • Re: NPM shows different readings of RAM on server being monitored
                  Andy Ng

                  Hi trebor11584,

                  Thanks for the reply! ;)

                  The MIB walk seems incomplete, as it does not hold any information regarding your volume elements.

                  If possible, attach the MIB walk results in CSV file to your reply post.

                  Let's look at the MIB walk results to be able to look at it further.

                   

                  Cheers!

                    • Re: NPM shows different readings of RAM on server being monitored
                      trebor11584

                      Hi,

                      Sorry about that, I used the private one instead of the standard in running MIB. Anyway, here's the attached file. This is not a .csv file since the format gets corrupted when I saved it to that file type. Also, I've changed the extension to .jpg 'coz I can't attached it kindly change it back to .xls.

                      Thanks,

                        • Re: NPM shows different readings of RAM on server being monitored
                          Andy Ng

                          Hi trebor11584,

                          Thanks! But I noticed that the MIB walk results (after renaming to .xls) is showing the HOST-RESOURCES-MIB, but only 4.. and it looks incomplete.

                          Volume elements are once again not showing in the results. Are you able to confirm if the one that you are seeing continues the HOST-RESOURCES-MIB after RFC-1213-MIB? And that you see more than 5 under HOST-RESOURCES-MIB?

                            • Re: NPM shows different readings of RAM on server being monitored
                              trebor11584

                              Hi Andy,


                              I just want to clarify on what you're to say on this "And that you see more than 5 under HOST-RESOURCES-MIB"? 'coz I checked the excel file and it's only showing 4 HOST-RESOURCES-MIB, and all the values are those that I've got from running the Standard mode in MIB walk, I'll try to re-run it again and see if I'll get a different result.

                               

                              Aside from the volume elements, what are the other values that you want to see on the file?

                               

                              TIA.

                                • Re: NPM shows different readings of RAM on server being monitored
                                  Andy Ng

                                  Hi trebor11584,

                                  The information that you boxed in red is actually volume information that is populated by HOST-RESOURCES-MIB. That is the reason I am wanting to see that information to try and see the result I get from manual calculations.

                                  There really isn't anything else that I will need to see except that ;)

                                    • Re: NPM shows different readings of RAM on server being monitored
                                      trebor11584

                                      Hi Andy,

                                      Attached is the .xls file again (.jpg file), I checked it and it is still showing only 4 HOST MIB's. What do you think is causing is this problem? why is the MIB walk only showing 4 HOST MIB's?

                                      On a side note, I checked with their IT guy to verify the information on the said machine since he is using a different NMS (OpManager) ;P to monitor their network and on his side the said machine doesn't show that SNMP is enabled. But, as Orion detects it, it is using SNMP v1.

                                        • Re: NPM shows different readings of RAM on server being monitored
                                          Andy Ng

                                          Hi trebor11584,

                                          Is the NPM monitoring the device on SNMP v1 as well?

                                          Try changing to SNMP v2c on the device to see if that helps.

                                          It might be that the SNMP-agent on the IBM device is not working well. And it increases my suspicion that the SNMP-agent is causing the discrepancies in the Web Console.

                                            • Re: NPM shows different readings of RAM on server being monitored
                                              trebor11584

                                              Hi Andy,

                                              I deleted the element and rediscover it, when I manually added it and chose SNMP v2 a pop-up appeared saying that the device only responds to SNMP v1. So, I chose it and again same result. Does that mean that this is an issue concerning SNMP v1? Is there anyway to fix this? How can I prove to them that the SNMP is culprit?

                                              TIA

                                                • Re: NPM shows different readings of RAM on server being monitored
                                                  Andy Ng

                                                  Hi trebor11584,

                                                  For SNMP v2 to be used for managing the device in NPM, you will have to first ensure that the SNMP-agent on the device is responding to SNMP v2 requests.

                                                  At this point, it seems that you have changed the Node to be managed using SNMP v2, but did not make changes to the SNMP-agent of the device.

                                                  What I will do to ensure that the SNMP is causing the issue are as follows:

                                                  * use SNMP v2 and check if NPM is showing up the discrepancies
                                                  * use MIB walk against the device to ensure that the HOST-RESOURCES-MIB is showing up
                                                  * use other MIB walk equivalent tools (e.g. snmpwalk that comes with Net-SNMP and is almost default on servers with Net-SNMP installed) to confirm that both MIB walk and other snmpwalking utilities are seeing the incomplete results

                                                  * if the results is able to be retrieved, I will do the calculation that I have indicated in my earlier posts, and check it against the NPM.
                                                  And I will monitor to see if the values on the NPM changes again. If it does change, I will once again do a MIB walk against the device and perform the calculation to see if the values there match up.

                                                  If the changes on the NPM matches the calculation that is done with the values that are retrieved from the SNMP-agent, it is obvious that the SNMP-agent does not keep consistent data there, and the problem lies there.

                                                  Hope that clarifies.

                                                    • Re: NPM shows different readings of RAM on server being monitored
                                                      trebor11584

                                                      Hi Andy,

                                                      Yes, that's what I did. I tried to used SNMP v2 on the NPM without setting the device first to SNMP v2 because we don't have the authority to do that now. But, what I want to know is that, is this a SNMP v1 issue? which is causing the problem? and how do I access Net-SNMP?

                                                      On a side note, could you also teach me how to do the alert email escalation on Orion? let's say I want to send an email to the technician first and after an hour or so if he didn't acknowledge it, then it will send an email to the manager/CEO and to the technician again. I've been trying to that but I was not successful at all.

                                                      TIA.

                                                        • Re: NPM shows different readings of RAM on server being monitored
                                                          Andy Ng

                                                          Hi trebor11584,

                                                          I am frankly not sure if it is a SNMP v1 issue.

                                                          But along the tests, if SNMP v2 shows that it has no issues. Then can we say that it is SNMP v1 that is having issues.

                                                          Net-SNMP is typically installed into Linux/UNIX boxes to let them have SNMP capabilities.
                                                          They have a Win32 installer that can work in Windows: http://www.net-snmp.org/download.html

                                                          For the other issue, I have seen a new posting that you have made as well. Let us just keep this post for your SNMP issues and not lump everything together.

                                                            • Re: NPM shows different readings of RAM on server being monitored
                                                              trebor11584

                                                              Hi Andy,

                                                               

                                                              Thanks for the response. I'll try to do this later and post the results later (need to take my lunch first).

                                                               

                                                              regards,

                                                                • Re: NPM shows different readings of RAM on server being monitored
                                                                  Andy Ng

                                                                  Hi trebor11584,

                                                                  Great! Let me know of the results.

                                                                  • Re: NPM shows different readings of RAM on server being monitored
                                                                    trebor11584

                                                                    Hi Andy,

                                                                    Could you teach me how to use Net-SNMP to gather the MIB of the element that I'm having trouble. I tried to read the documentation but the thing is I'm having a difficult time understanding it.

                                                                     

                                                                    TIA.

                                                                      • Re: NPM shows different readings of RAM on server being monitored
                                                                        Andy Ng

                                                                        Hi trebor11584,

                                                                        It is not really that hard.

                                                                        What you will need to do, is to install Net-SNMP on the PC or server that is able to query the SNMP-agent of the device.

                                                                        After installation, the installer should make some changes to your environmental settings to be able to call out the binaries of Net-SNMP.

                                                                        What you need to do next, is to go to command-line: [Start | Run | cmd]

                                                                        And when you hit the command line, you can try entering: snmpwalk

                                                                        You should get one whole heap of commands... but to cut short... the command you will need to enter is:
                                                                        snmpwalk -v [version] -c [community string] [IP]

                                                                        Note that it should give you an output without page breaks.. modifying the command line to:
                                                                        snmpwalk -v [version] -c [community string] [IP] | more

                                                                        Replace those values in [] to the ones that you is being used in your environment... close to the end, you should see HOST-RESOURCES-MIB being responded by the SNMP-agent of the device.

                                                                        HTH.

                                                                          • Re: NPM shows different readings of RAM on server being monitored
                                                                            trebor11584

                                                                            Hi Andy,

                                                                            Thanks for this prompt response. Here's the result of the Net-SNMP's snmpwalk.

                                                                            Kindly check it out for discrepancies.

                                                                            Thanks!

                                                                              • Re: NPM shows different readings of RAM on server being monitored
                                                                                Andy Ng

                                                                                Hi trebor11584,

                                                                                Thanks for the snmpwalk results.

                                                                                It seems that the issue is the same, having only 4 results:

                                                                                =========================================================
                                                                                HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (299684708) 34 days, 16:27:27.08
                                                                                HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2010-5-27,16:56:31.0,+8:0
                                                                                HOST-RESOURCES-MIB::hrSystemInitialLoadDevice.0 = INTEGER: 3
                                                                                HOST-RESOURCES-MIB::hrSystemInitialLoadParameters.0 = STRING: "B"
                                                                                =========================================================

                                                                                And ended with timeout on:
                                                                                Timeout: No Response from 172.19.13.2

                                                                                Seems like the SNMP-agent is having some issues IMO.

                                                                                  • Re: NPM shows different readings of RAM on server being monitored
                                                                                    trebor11584

                                                                                    Hi Andy,

                                                                                    Thanks for looking. :)

                                                                                    About the result, yes I've noticed that as well. I compared the resulst from the MIB walk to the SNMP wal results and they're the same. It seems the SNMP is the culprit. But I still have questions (sorry, I just want this to be clear as a crystal). Hope you are still willing to help. :)

                                                                                    1. Since the SNMP is the culprit, how can I prove and explain to our clients that it is actually the machine's SNMP and not the Orion that is causing the issue?

                                                                                    2. How come that the information the SNMP is sending are incomplete/inconsistent?

                                                                                    3. If SNMP is the issue here, what are those equipment that are currently being shown by Orion base on the screen shots (Disk Volume Usage) on my post?

                                                                                    4. What does the message "And ended with timeout on: Timeout: No Response from 172.19.13.2" meant?

                                                                                    5. What could be the reason/s of the SNMP iconsistency here?

                                                                                    Thanks,

                                                                                      • Re: NPM shows different readings of RAM on server being monitored
                                                                                        Andy Ng

                                                                                        Hi trebor11584,

                                                                                        No worries, the answer to the questions that you have posed are:

                                                                                        1. If you do a snmpwalk or MIB walk against this device, and against other devices (e.g. Windows, Linux boxes, etc) that has Volumes, etc. you should be able to see that HOST-RESOURCES-MIB extend more than 4 values.

                                                                                        2. The following command might be able to debug it: snmpwalk -v [version] -c [community string] [IP]-D ALL

                                                                                        Let the snmpwalk finish up, and see if there are any errors being informed at the end.

                                                                                        3. IMO, pulling the information from the HOST-RESOURCES-MIB might not need to go through the whole SNMP-listings. And that might be the reason why you are able to avoid timeouts?

                                                                                        To test that out, you might want to try doing the following: snmpwalk -v [version] -c [community string] [IP] 1.3.6.1.2.1.25.2.3.1.4

                                                                                        4. Refer to Q2 recommendations.

                                                                                        5. I am unable to tell you offhand, but again, the troubleshooting on Q2 might center on the issue.

                                                                                        I have did some reading, and found there are various reasons why you get that error. If the SNMP-agent has a timeout setting, you might want to pro-long it.

                                                                                          • Re: NPM shows different readings of RAM on server being monitored
                                                                                            trebor11584

                                                                                            Hi Andy,

                                                                                            I did what you've mentioned on you response here's what I've got.

                                                                                            1. About the debugging, I was not successful I'm getting these errors whenever I tried to run it.

                                                                                            Timeout: No Response from 172.19.13.2-D

                                                                                            snmpwalk: Unknown host (172.19.13.2-D) (No such file or directory)

                                                                                            And when I  put a space between the IP add and "-D" here's what I've got.

                                                                                            -D:  (Sub-id not found: (top) -> -D)

                                                                                            Am I doing something wrong here?

                                                                                            2. And about your no. 3 post, here are the results. 

                                                                                            HOST-RESOURCES-MIB::hrStorageAllocationUnits.1 = INTEGER: 4096 Bytes
                                                                                            HOST-RESOURCES-MIB::hrStorageAllocationUnits.2 = INTEGER: 4096 Bytes
                                                                                            HOST-RESOURCES-MIB::hrStorageAllocationUnits.3 = INTEGER: 4096 Bytes
                                                                                            HOST-RESOURCES-MIB::hrStorageAllocationUnits.4 = INTEGER: 4096 Bytes
                                                                                            HOST-RESOURCES-MIB::hrStorageAllocationUnits.5 = INTEGER: 4096 Bytes

                                                                                            What do these results mean? what does the 4Kb pertains to?

                                                                                            TIA.

                                                                                              • Re: NPM shows different readings of RAM on server being monitored
                                                                                                Andy Ng

                                                                                                Hi trebor11584,

                                                                                                Opps. I forgotten a space between the IP and the -D... it should be: snmpwalk -v [version] -c [community string] [IP] -D ALL

                                                                                                And with the posting of hrStorageAllocationUnits, it should be quite clear that the snmpwalk on the whole device will cause timeouts.

                                                                                                If you refer to my earlier post, there are 3 OIDs that you should look at:

                                                                                                hrStorageAllocationUnits = 1.3.6.1.2.1.25.2.3.1.4
                                                                                                hrStorageSize = 1.3.6.1.2.1.25.2.3.1.5
                                                                                                hrStorageUsed = 1.3.6.1.2.1.25.2.3.1.6

                                                                                                size = hrStorageSize x hrStorageAllocationUnits
                                                                                                used space = hrStorageUsed x hrStorageAllocationUnits

                                                                                                hrStorageAllocationUnits is used to multiplied to hrStorageSize, hrStorageUsed to get the value.

                                                                                                You might want to do a snmpwalk / MIB walk on these 3 OIDs.
                                                                                                And in addition to those 3, there is another OID that you might need to walk: .1.3.6.1.2.1.25.2.3.1.3
                                                                                                This OID will hold the name of the volumes that are indicated by the 5 Storage Indexes. (Note that at the end of your snmpwalk results, you see .1, .2, .3, .4, .5. The hrStorageAllocationUnits are actually belonging to 5 different Volumes.

                                                                                                HTH.

                                                                                                  • Re: NPM shows different readings of RAM on server being monitored
                                                                                                    trebor11584

                                                                                                    Hi Andy,

                                                                                                    I've already did that and still no result from the debug, all I've got is the message below.

                                                                                                    -D:  (Sub-id not found: (top) -> -D)

                                                                                                    What value should I put after -D? ALL is not working.

                                                                                                    I did the walk on the .3 and comparing to the screenshots I've posted, the walk result is correct. These are the exact names that are currently showing up on the web console and being monitored by Orion.

                                                                                                    HOST-RESOURCES-MIB::hrStorageDescr.1 = STRING: System ASP
                                                                                                    HOST-RESOURCES-MIB::hrStorageDescr.2 = STRING: RAM
                                                                                                    HOST-RESOURCES-MIB::hrStorageDescr.3 = STRING: RAM
                                                                                                    HOST-RESOURCES-MIB::hrStorageDescr.4 = STRING: RAM
                                                                                                    HOST-RESOURCES-MIB::hrStorageDescr.5 = STRING: RAM

                                                                                                    Now, I'm still trying to solve/find where is the 16Gig RAM on this machine our client is talking about.

                                                                                                      • Re: NPM shows different readings of RAM on server being monitored
                                                                                                        Andy Ng

                                                                                                        Hi trebor11584,

                                                                                                        Let's leave the -D aside first.

                                                                                                        Do snmpwalk for the following:

                                                                                                        hrStorageAllocationUnits = 1.3.6.1.2.1.25.2.3.1.4
                                                                                                        hrStorageSize = 1.3.6.1.2.1.25.2.3.1.5
                                                                                                        hrStorageUsed = 1.3.6.1.2.1.25.2.3.1.6

                                                                                                        And let me know the results.

                                                                                                          • Re: NPM shows different readings of RAM on server being monitored
                                                                                                            trebor11584

                                                                                                            Hi Andy,

                                                                                                            Here are the results of the walk.

                                                                                                            1.3.6.1.2.1.25.2.3.1.4

                                                                                                            HOST-RESOURCES-MIB::hrStorageAllocationUnits.1 = INTEGER: 4096 Bytes
                                                                                                            HOST-RESOURCES-MIB::hrStorageAllocationUnits.2 = INTEGER: 4096 Bytes
                                                                                                            HOST-RESOURCES-MIB::hrStorageAllocationUnits.3 = INTEGER: 4096 Bytes
                                                                                                            HOST-RESOURCES-MIB::hrStorageAllocationUnits.4 = INTEGER: 4096 Bytes
                                                                                                            HOST-RESOURCES-MIB::hrStorageAllocationUnits.5 = INTEGER: 4096 Bytes

                                                                                                            1.3.6.1.2.1.25.2.3.1.5

                                                                                                            HOST-RESOURCES-MIB::hrStorageSize.1 = INTEGER: 429719552
                                                                                                            HOST-RESOURCES-MIB::hrStorageSize.2 = INTEGER: 790087
                                                                                                            HOST-RESOURCES-MIB::hrStorageSize.3 = INTEGER: 1778998
                                                                                                            HOST-RESOURCES-MIB::hrStorageSize.4 = INTEGER: 1376502
                                                                                                            HOST-RESOURCES-MIB::hrStorageSize.5 = INTEGER: 76446

                                                                                                            1.3.6.1.2.1.25.2.3.1.6

                                                                                                            HOST-RESOURCES-MIB::hrStorageUsed.1 = INTEGER: 223810580
                                                                                                            HOST-RESOURCES-MIB::hrStorageUsed.2 = INTEGER: 220884
                                                                                                            HOST-RESOURCES-MIB::hrStorageUsed.3 = INTEGER: 1668810
                                                                                                            HOST-RESOURCES-MIB::hrStorageUsed.4 = INTEGER: 1376501
                                                                                                            HOST-RESOURCES-MIB::hrStorageUsed.5 = INTEGER: 75584

                                                                                                              • Re: NPM shows different readings of RAM on server being monitored
                                                                                                                Andy Ng

                                                                                                                Hi trebor11584,

                                                                                                                Thank you for the information!

                                                                                                                I have calculated .2, .3, .4, .5 (that belongs to RAM) as indicated in your previous update using hrStorageSize x hrStorageAllocationUnits:

                                                                                                                790087 x 4096 = 3,236,196,352 B
                                                                                                                1778998 x 4096 = 7,286,775,808 B
                                                                                                                1376502 x 4096 = 5,638,152,192 B
                                                                                                                76446 x 4096 = 313,122,816 B

                                                                                                                3,236,196,352 B + 7,286,775,808 B + 5,638,152,192 B + 313,122,816 B = 16,474,247,168 B (~16 GB)

                                                                                                                That is the total amount that is reflected by the server via SNMP-agent.

                                                                                                                But I have looked at the screenshot that you have raised on the initial posting, and found that the values are different. Are you able to do a re-discovery on the volumes to see if there are any changes?

                                                                                                                And in regards to the error that was seen in the snmpwalk, that will have to be checked with the vendor as I can just help you to find that there is an error there, but I can't explain much about the error as I am not an SNMP guru *lol*

                                                                                                              • Re: NPM shows different readings of RAM on server being monitored
                                                                                                                Andy Ng

                                                                                                                Hi trebor11584,

                                                                                                                The syntax of the -D that I gave was working in the Linux box, but not in Windows.

                                                                                                                It should be: snmpwalk -v [version] -c [community] -D ALL [IP]

                                                                                                                  • Re: NPM shows different readings of RAM on server being monitored
                                                                                                                    trebor11584

                                                                                                                    Hi Andy,

                                                                                                                    Ok, got it.

                                                                                                                    Here's the debug results.

                                                                                                                    dumpv_recv:            ObjID: RFC1213-MIB::ipRouteIfIndex.192.168.46.31
                                                                                                                    trace:  ..\..\snmplib\snmp_api.c, 4674:
                                                                                                                    dumph_recv:         Value
                                                                                                                    trace:  ..\..\snmplib\snmp_api.c, 5416:
                                                                                                                    sess_process_packet: received message id#0 reqid#26793
                                                                                                                    trace:  ..\..\snmplib\snmp_client.c, 180:
                                                                                                                    snmp_synch: Response (ReqID: 26793 - Cmd 162)
                                                                                                                    Error in packet.
                                                                                                                    Reason: (genError) A general failure occured
                                                                                                                    Failed object: RFC1213-MIB::ipRouteIfIndex.192.168.46.31

                                                                                                                    I just copied the last part, it seems that the error/s can be found on the last part. Now what does that error meant?


                                                                                                                    TIA.