Monitoring CUSP using JConsole

[sathish10608]

Hi,

Need help to monitor Memory utilization of CUSP using JConsole.

The GUI and CLI are showing spiked up values of Memory utilization due to an identified bug. There is no ETA for this Fix.

There is an option to monitor CUSP using JConsole and the port is 9999.

When we try to monitor, we are getting a connection failed message. The Jconsole debug log says it has failed due to Invalid Username or Password.

We are using the superuser password for CUSP where we are able to access both CLI and GUI.

Any suggestions on how to monitor using JConsole?

CUSP Version 10.2

[bill.king1]

Are you sure for a fact that you're having a memory problem? There's a defect in version 10 that outlines it may be false alarm?

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvp65157

[sathish10608]

Yes, we are aware of this Bug.

There is also another Bug around the same topic,

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi81740

We are using a monitoring tool(in-house) and CUSP GUI/CLI, both reports false values.

We had a TAC opened for the same issue earlier, we were advised to increase RAM from 4GB to 8GB to resolve this issue, which we did and it occurred again.

The possible ways to monitor CUSP as of now is using ESXI and JConsole.

In ESXi it is not giving any values and just says 0.6 GB used.

We would need help on how to monitor using JConsole.

We are trying using JConsole and port 9999 as mentioned but getting error message as said above

[sathish10608]

We have managed to find a way to monitor CUSP Memory and CPU using Java Console/JMX.

We would need a monitoring user to be created in CUSP, which is not available/mentioned as part of any CUSP documentation. After creating the monitoring user, we were able to connect using JConsole/JMX and monitor CUSP Memory and CPU and get exact details.

[neerakum]

It's documented already https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cusp/rel10_2/cli_command_ref/cli_commands/cuspfoundcmds.html#94714

[sathish10608]

Thank you, I think this is updated recently, at the time when we were working with TAC, we did not find it online. Hence we requested TAC to update the documentation.