5.6 Post Installation Procedure

MySQL VM

Perform the following procedure to modify properties for mysqld service:

1. Log in to MySQL VM (Virtual Machine) through SSH.
2. Run the following command:

   sudo restorecon -v /etc/my.cnf

3. To create the swap file, run the following commands in the same sequence:

   
   sudo fallocate -l 12G /swapfile
   sudo chmod 600 /swapfile
   sudo mkswap /swapfile
   sudo swapon /swapfile
   echo '/swapfile swap swap defaults 0 0' | sudo tee -a /etc/fstab

4. Edit the mysqld service:
   1. Run the following command to edit mysqld service:

      systemctl edit mysqld

   2. Paste the below content in the edit window:

      
      [Service]
      MemoryMax=11G

   3. To save the service configuration, press escape key and type wq.
5. Run the following command to restart the MySQL service:

   systemctl restart mysqld

NF-Config Service Configuration To Fetch MO Data From DSR

Perform the following steps to fetch MO data from DSR:

1. Log in to Service VM.
   1. Go to Service VM and navigate to /opt folder and open cnidih_VM.yaml file.
   2. Navigate to Nf-Config section.
   3. In place of NFCONFIG_PLUGIN_DSR_HOST=<Replace with SOAM VIP> provide DSR SOAM VIP.

      Note:

      The Service Operations, Administration, and Maintenance (SOAM) VIP to be replaced in the angular brackets. Example: NFCONFIG_PLUGIN_DSR_HOST=127.0.0.1
   4. Navigate to Protrace section, and modify the following property NFCONFIG_CLIENT_ENABLED to true.

Modifying advertised.listeners in Kafka (This is required only if DSR and IDIH are deployed using different networks )

Perform the following steps to modify advertised.listeners in kafka:

1. Log in to Kafka VM.
2. Go to /opt/kafka/config directory.

   cd /opt/kafka/config

3. Perform the following command to open broker.properties:

   vi broker.properties

4. Following are the steps to modify advertised.listeners property:
   1. There are two instances of advertised.listeners in broker.properties file, comment the one which has ens5(XSI) IP for external listener.
   2. Uncomment the other instance which has kafka_xmi for external listener and replace the kafka_xmi with the ens3(XMI) ip address of Kafka VM.
   3. Save the broker.properties file.
5. Perform the following command to restart the Kafka service:

   systemctl restart kafka

SSL Certificate Creation for IDIH

Kafka VM

1. Certificates are required in KeyStore and TrustStore format (PKCS or JKS).
2. Private key which is part of KeyStore must be encrypted.
3. One KeyStore and TrustStore file is required.

DSR (it acts as client for Kafka)

1. Certificates are required in pem format here.
2. Required files are: certificate, privatekey, CA file.

   Privatekey should be encrypted with password.

3. To upload the above files on DSR SOAM: from the Main Menu, go to Diameter, and Troubleshooting with IDIH, and then Configuration.

   Note:

   Same CA file must be used for Kafka and DSR Certificates.

Service VM

1. Certificates are required in KeyStore and TrustStore format (PKCS).
2. One KeyStore file and TrustStore file is required.
3. Same CA file can be used which is used while creating certificates for Kafka or different CA file also can be used.
4. Private key which is part of KeyStore must not be encrypted.
5. Certificate should contain the following fqdn's as SAN's (Subject Alternative Names).
   1. idih.tekelec.com
   2. .tekelec.com
   3. cnidih-portal
   4. usermanagement
   5. protraceprocessor
   6. ttrdecoder
   7. logauditmanager
   8. alarmmanagement