IM&P configuration validation with CUCM fails

[Djeten]

Hello,

I am setting up a new voice cluster. I have 2 CUCM's installed  and I want to add a IM&P server.

I have added the new server to the server list in CUCM

During the install of IM&P I get the error that the configuration validation failed.

I'm sure that the hostname and password is entered correctly. I have tried it multiple times already. 

Any ideas how I can troubleshoot this more?

[b.winter]

Is the IMP able to resolve the hostname / FQDN of the pub? And also the reverse pointer?

[Djeten]

I'm doing this on ip address and not on fqdn

[Roger Kallberg]

Even though you’re using IPs in the server list you still need to have both a A and a PTR record, or a host record that combines both, for each of the servers in your server list.

Also a question, why are you masking part of the private IPs?

[b.winter]

But you still define the hostname for every machine during the installation. And as far as I remember, you also define the hostname of the pub during the clustering.
And every machine checks the DNS and reverse record during installation.

[Djeten]

I have added the DNS record and the reverse record, but I still get the same error...

[b.winter]

Maybe the security password is just incorrect. Maybe the one you got is wrong.
You can check it by trying to reset the password via CLI "set password user security"

It asks you for the old one and also to set the new one.
It then verifies, if they are correct and then prompts you to confirm the change. So, you can still cancel the password change.
If the verification is not successful, then you probably have a wrong security password.

[Djeten]

I do have the right security password. I used it already to add the CUCM subscriber...

[Djeten]

Some more info:

In the Unified Reporting I can see this:

In RTMT I see this error:

At Fri Nov 24 11:30:23 CET 2023 on node 192.168.x.x; the following SyslogSeverityMatchFound events generated: SeverityMatch : Alert MatchedEvent : Nov 24 11:29:30 EBOSLBE1-CUCM01 local7 1 : 182: EBOSLBE1-CUCM01.domain.com: Nov 24 2023 10:29:30.516 UTC : %UC_CLUSTERMANAGER-1-CLM_MsgIntChkError: %[NodeIP=192.168.x.x][AppID=Cisco Cluster Manager][ClusterID=][NodeID=EBOSLBE1-CUCM01]: ClusterMgr message integrity check error. AppID : Cisco Syslog Agent ClusterID : NodeID : EBOSLBE1-CUCM01 TimeStamp : Fri Nov 24 11:29:30 CET 2023

[Carlo Poggiarelli]

As correctly mentioned by @b.winter and @Roger Kallberg fqdn validation is always performed during the installation of both first node and subsequent nodes of the cluster.

To verify that before rebooting the failing node go on the first node and do a show network cluster and see if the node you are installing is authenticated or not 

Please let us know.  

Regards

Carlo

[Djeten]

[Djeten]

I don't know why but now the configuration validation was succesfull and the installation is now installing the database...

I can now also see this in the provisioned servers:

So I changed nothing, but suddenly the installation does continue... Thanks for the assistance anyway.

[Carlo Poggiarelli]

Glad to know your problem is fixed for now but I would check if all the DNS you configured on all nodes are able to resolve both A and PTR record of all nodes.

Cheers

Regards

Carlo