UCCX 8.5 System parameters partially displayed in app admin

[arani]

Hi all
we have a problem with a 2 node UCCX 8.5 deployment.
The System Parameters Configuration page in app addmin displays only a few fields that are not editable. For example we cannot view historical reporting field and others.
Also an error message is shown 
"** -Error while reading the data. Please look into logs for more information."

Regards

[Aaron Harrison]

Hi

Have you tried logging in to the alternate node to  see if the problem shows there as well?

If not, try that. 

If you have, post up your MADM logs covering the time you access the page.

Aaron

[arani]

HI Aron
first of all, thank you.

Same behavior on the alternate node.
To tell the truth, something similar also happens in Cisco Unified Serviceability.

MADM log in attach.

Regards

[Aaron Harrison]

Hi

Is this a new deployment, or in production?

I see a lot of error entries in there suggesting DB connection issues to XFUCCX02.

I would first verify that name resolution is working correctly between the nodes:

• From each node, ping the other by hostname only (e.g. utils network ping xfuccx02)
• From each node, ping the other by FQDN (e.g. xfuccx02.whatever.com)
• From each node, 'utils network host x.x.x.x' where x.x.x.x is the IP of the other node

Also do both nodes show all the services as up?

Regards

Aaron

[arani]

Hi Aaron

• From each node, ping the other by hostname only (e.g. utils network ping xfuccx02)
  OK!
• From each node, ping the other by FQDN (e.g. xfuccx02.whatever.com)
  NOT OK!
• From each node, 'utils network host x.x.x.x' where x.x.x.x is the IP of the other node
  OK!

Both tho nodes have Application Manager and RmCm Subsystem in partial service. All other servrices are ok.

Regards

[Aaron Harrison]

Hi

So for the second test you can't ping by FQDN? If not, you should check your DNS setup - suffixes assigned to the servers, records in the DNS server etc.

On the third test, do you see the proper FQDN returned when you do the host lookup? 

Aaron

[arani]

Hi Aaron

sorry for the delay in my answer
Maybe we have a problem with DNS configuration.

At the moment we are dealing with the resolution of this problem.

Thank you for now.

Kind regards.