Showing results for 
Search instead for 
Did you mean: 

CUCM Not detected in Prime Collaboration 10.6


Hi All,

while adding the CUCM cluster in Prime Collaboration Assurance 10.6 , one of the subscriber always detected as "NonCisco" server & capabilities are not detected.Multiple deleted & added again byt no luck.

Due to this subscriber couldn't be listed in the cluster view topology. Has any faced this problem earlier ?

Thanks in Advance !!!

2 Replies 2

Deepak Rawat
Cisco Employee
Cisco Employee

Can you make sure that SNMP Master Agent under Control Center - Network Services and Cisco CallManager SNMP Service under Control Center - Feature Services for all the CM servers in the cluster is started.

After this, suspend and delet the subscribers and the publisher from Prime Collaboration and restart the cpcm application.After CPCM comes back, initiated a discovery on the publisher again using default credentials and see if that helps.

Try below steps only if the issue still persists after following the above steps

1.       Login to PCA as globaladmin

2.       Make a note of all IP address for every CUCM node currently listed (including the decommissioned that aren't in DWC)

3.       In DWC, suspend all CUCM nodes and then delete all CUCM nodes

4.       Navigate to the below URL - Copy and paste the below URL to the same browser window after replacing the correct PCA server IP address and CUCM node IP address

a.       https://PCAServerIPAddress/emsam/service/inventory/delete?deviceIP=IPAddressoftheCUCM

b.      Run this command for every CUCM node gathered on step 2 above.

c.       For each delete, you should receive a success confirmation message in the browser. Please ensure you're using a supported browser version. (FF 24 or 31 ESR, IE 10 or 11).

5.       Restart PCA services via admin user in CLI

a.       Stop application cpcm

b.      Show application status cpcm (wait until every service has stopped)

c.       Start application cpcm (you should have a total of 26 services)

6.       Navigate back to DWC and re-discovery only the CUCM publisher for each cluster

a.       Note that under Manage Credentials > Profile Name, your Device Type needs to be CISCO UNIFIED COMMUNICATIONS MANAGER

After 5-15 minutes all nodes should be in a Managed state if they were successfully discovered and the type should be, Communications Manager.



- Rate Helpful Posts -

Hi Deepak,

Thanks for the detailed troubleshooting steps.

Unfortunately , After all these we get in to the same problem for that subscriber.

That subscriber detected as "Type = NonCisco, Model = CiscoUCVirtualMachine".  No capabilities are detected.

What is the next step for troubleshooting ?

Thanks in Advance !!

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers