credentials query - unable to discover devices

[musademirel]

hi there

I am trying to add a few devices into CPCA. v9. Its stating that credentials to Call manager servers are incorrect even though we type this in correctly.  When I go through and perform  a  "verify", it fails each time. We have our fw ports opened up between the servers. I can also successfully ssh/telnet via port 80/443 via the cli. SNMP authentication passes however HTTP authentication fails.

Any ideas on what else to check?

Thanks

MD

[prchandr · Accepted solution]

Hi Musa

Let me check and get back on this by tomorrow. Can you try restarting the assurance app

by logging in via ssh as admin . you need to use port 26 for ssh for assurance server

Then run the commain

application stop cpcm

After it stops

then start it with

application start cpcm

YOu will need to wait around 15 mts or so before logging into ui and trying again.

In the meantime i will check from our side as well as what could be the issue or what logs to check

thx
Prem

[prchandr · Accepted solution]

Can you check the follwong to make sure the username you give in credentials for hte CUCM in Prme Collab has the right permissions and also the ports are open in FW. I know you have mentioned the fw is open but wanted to check if all the required ports below are allowed

i

The required ports for CUCM is documented here: http://docwiki.cisco.com/wiki/Required_Ports_for_Prime_Collaboration.  In addition, the CUCM app user should also be configured properly in CUCM:http://docwiki.cisco.com/wiki/Setting_up_Devices_for_Prime_Collaboration_Assurance#Cisco_Unified_Communications_Manager.  

thx
Prem

[musademirel]

Thanks Prem, yes  thats the ports i have opened up on the firewalls. I would like to know if there is a way to do the packet capture from the server.

I know the credentails are correct as I am using the main admin password for CUCM which has full access. With regards to other products like meeting place it seems to detect only one of the two identical nodes i have on the same subnet. The second node is not liked - "state unsupported" even though its identical in hardware and software. Weird right?

[musademirel]

ok seem to get to the bottom of this. Removed all credentials and deleted all historical/discovered devices. restarted services. Re-added all credentials back in - seems to resolve issue. Its weird as I can telnet to some of the devices and not others via the server cli , but still get discovery completed.

Nevertheless thanks for the help.