To deploy NCM Reporting successfully, you need to complete the NCM server side configuration.
Procedure
- Login to NCM application server, go to $VOYENCE_HOME/bin and generate lockb.ekey using below command:
./cstdriver -lockbox $VOYENCE_HOME/data/lockb.clb -passphrase <PASSPHRASE> -createKeyFileNote: Use the same lockbox passphrase, which was provided during NCM installation.
- Transfer lockb.ekey file from NCM server to the location from where it can be uploaded to VMware Telco Cloud Service Assurance as mentioned in Add NCM Integration section.
- Login to NCM database server and add VMware Telco Cloud Service Assurance cluster node IPs in NCM database access list, that is in $VOYENCE_HOME/db/controldb/data/pg_hba.conf file:
For example:
host all all 10.x.x.x/32 md5
Note: To get the IP addresses, use any one of the following options:- To get the IP addresses of the nodes where Grafana and ncm-proxy services are running in VMware Telco Cloud Service Assurance cluster, run the following command:
kubectl get pods -o custom-columns=Name:.metadata.name,HostIP:.status.hostIP |egrep '^grafana|ncm-proxy'
The command might return a duplicate IP address due to the same node, you can ignore the duplicate IP address.
- Add the subnet. For example, if your IP address is 10.x.x.x then update as 10.x.x.0/24.
- To get the IP addresses of the nodes where Grafana and ncm-proxy services are running in VMware Telco Cloud Service Assurance cluster, run the following command:
- Restart controldb service using service controldb restart command.