Create an account on the HP Community to personalize your profile and ask a question
02-02-2012 09:29 AM
We are using a CMA5000 Version 5.5.0.ER19 with the CMAD client version 188.8.131.5216 and we are having some issues with clients dropping out of area assignments. What is happening is that IF the CMAD client logs into the CMA, say every single day, there is no problem and it stays assigned to the area, however should that particular client not login for a few days or a week or whatever then that client drops out of its assigned area and has to be re-assigned to the area once again when it logs in again. On another note, the Real Presence Mobile clients are exhibiting similar issues but just a bit different in that the old RPM client entry in the CMA area never drops out of its area, but once it logs back into the CMA the status shown in the area never changes showing it to be online.
02-02-2012 10:03 AM
This sounds like it is probably the CMAD inactive license reclaimation. This is a configurable value on the CMA Server that will cause CMAD registrations to be deleted after a period of inactivity. It is under Admin --> Server Settings --> Licenses.
The default value is 30 days, but you can set it for anything you like. If you want the CMA to never delete a CMA D entry, just set it to 0 and it will never reclaim the licenses.
02-06-2012 10:49 AM
I suspected that was the cause but I do have another question. Is this setting a Global setting for all CMAD endpoints or can it be set "per Area" or for a specific CMAD client?
Another question I have is regarding the RPM mobile clients showing up with multiple CMA entrys if the same client with the same network ID and login registers with a different IP. Is that normal behavior for the RPM client and is there a way to somehow prevent that multiple entry effect?
Thank you for your time,
02-07-2012 06:12 AM
The license reclaim is a global setting at the moment.
As for the reporting issues with RPM, that is pretty typical on version 5.X CMA. RPM was designed to work with 6.0 CMA, so earlier versions have to use two entries, one for registration and one for provisioning/directory/presence. On 6.0.1 CMA, the RPM registers as a single device.