Also refer to the section Validate VM Deployment for steps to verify that the CPS installation was successful.
Problem: Diameter Stack in not UP even if the hostname is configured for the Policy Director (LB) VMs and same names are configured in Local End Points under Diameter Stack configuration plug-in in Policy Builder.
Solution:
Update the /etc/hosts in Cluster Manager VM.
Example:
If hostnames configured for lb01/lb02 VMs are lab1-lb01 and lab1-lb02 and same names are configured in Local End Points of Diameter Stack configuration, then update /etc/hosts file:
[root@shiprock-base ~]# cat /etc/hosts | grep lb0 10.10.75.164 lb01 lab1-lb01 10.10.75.165 lb02 lab1-lb02 10.10.90.132 lab2-lb01 lab2-lb01 10.10.90.133 lab2-lb02 lab2-lb02 [root@shiprock-base ~]#
[root@shiprock-base ~]# cat /etc/hosts | grep lb0 10.10.75.164 lab1-lb01 lb01 10.10.75.165 lab1-lb02 lb02 10.10.90.132 lab2-lb01 lab2-lb01 10.10.90.133 lab2-lb02 lab2-lb02 [root@shiprock-base ~]#
Execute the following command to rebuild the /etc/broadhop/license directory from the Cluster Manager VM:
/var/qps/install/current/scripts/build/build_etc.sh
Execute the following commands in Cluster manager VM to copy /etc/hosts file to all deployed VMs.
SSHUSER_PREFERROOT=true copytoall.sh /etc/hosts /etc/hostsLogin to the individual Policy Director (LB) VMs and restart the Policy Server (QNS) service by executing the following commands:
service monit stop
monit stop qns-1...4
monit start qns-1...4
service monit start