I need to know how to monitor JVM memory on CVP/VXML Server using SNMP

[bschmitt7]

I need to know how to Monitor JVM memory on CVP/VXML Server using SNMP

I am looking to monitor JVM memory statistics with SNMP.  The CVP only has the CISCO-CVP-MIB.my file in Cisco\CVP\Conf directory.  I want to use the JVM-MANAGEMENT-MIB to look at more statistics using the same SNMP community strings we have configured.   Is it possible to use multiple MIBs?  If so, where would I put the JVM MIB?

[Gergely Szabo]

Hi,

it depends on your monitoring tool. SNMP as such won't place any limitations on the number of MIB's used.

Actually, JVM memory monitoring may be a bit tricky as the OS does not really see what's going on within the one large memory block reserved by the JVM (heap/non-heap). You'll have to set up JMX within the application server.

G.

[bschmitt7]

We use Solarwinds for SNMP.  I have used snmptranslate to look at the OIDs in the JVM-MANAGEMENT-MIB which include some statistics like:

c:\NETSNMP\bin>snmptranslate.exe -m +JVM-MANAGEMENT-MIB -IR -On jvmMemPoolCommitted
.1.3.6.1.4.1.42.2.145.3.163.1.1.2.110.1.12

I also found this one below on the Cacti forums that listed this OID in the same JVM MIB. I did not find this object when I checked with snmptranslate ( "Unknown Object Identifier" )

id="jPermGenUsed" oid="1.3.6.1.4.1.42.2.145.3.163.1.1.2.110.1.12.5" 

Since there is no limitations to how many MIBs I want to use, where would I put them on the Cisco CVP/VXML server?  Cisco CVP installer disables the default Windows SNMP service and uses their own Cisco CVP SNMP management service which listens on port 161.   I don't have a default MIBs folder anywhere on the server other than where the CISCO-CVP-MIB.my file is located (\Cisco\CVP\conf\) directory.  Putting my MIBs in this directory does not work.

For JVM-MANAGEMENT-MIB to work, I also need to add SNMPv2-CONF, SNMPv2-SMI, and SNMPv2-TC because those 3 are referenced in JVM-MANAGEMENT-MIB.

I don't know how to set up JMX.  I only want the ability to do snmpwalks on additional OIDs that are not included in the default installation.