Post Installation Tasks

Validating the Deployment

After the deployment of IBM Sterling Control Center Monitor is complete, perform validation to ensure that everything is functioning as expected.

Check the service endpoints using this command:
$ oc describe svc ibm-sccm-service -n ibm-sccm
Name:	ibm-sccm-service
Namespace:	ibm-sccm
Labels:	app.kubernetes.io/instance=ibm-sccm 
        app.kubernetes.io/name=ibm-sccm
Selector:	app.kubernetes.io/instance=ibm-sccm,app.kubernetes.io/name=ibm-sccm 
Type:	ClusterIP
IP Family Policy: SingleStack 
IP Families:	IPv4
IP:	10.107.207.207
IPs:	10.107.207.207
Port:	swing-console 58080/TCP
TargetPort:	58080/TCP
Endpoints:	10.36.0.1:58080
Port:	web-console 58082/TCP
TargetPort:	58082/TCP
Endpoints:	10.36.0.1:58082
Port:	web-console-secure 58083/TCP
TargetPort:	58083/TCP
Endpoints:	10.36.0.1:58083
Port:	swing-console-secure 58081/TCP
TargetPort:	58081/TCP
Endpoints:	10.36.0.1:58081 
Session Affinity: ClientIP 
Events:	<none>

The Endpoints will display the IP address of the active pod, with port numbers matching those defined in the ConfigMap.

Retrieve the pod's IP address using the following command:
$ oc get pods -n ibm-sccm -o wide
NAME	READY	STATUS	RESTARTS    AGE	IP	NODE	NOMINATED NODE
ibm-sccm-statefulset-0	1/1	Running	0	16h	10.36.0.1	ccrdock-01	<none>  <none>

Now, validate the access to the Control Center application.

In case you've created a LoadBalancer service, retrieve the IP address to access Control Center with the following command:
Name:                     ibm-sccm-service
Namespace:                ibm-sccm
Labels:                   app.kubernetes.io/instance=ibm-sccm
                          app.kubernetes.io/name=ibm-sccm
Selector:                 app.kubernetes.io/instance=ibm-sccm,app.kubernetes.io/name=ibm-sccm
Type:                     LoadBalancer
IP:                       172.10.100.100
LoadBalancer Ingress:     111.22.333.444 
Port:                     swing-console  58080/TCP
TargetPort:               58080/TCP
NodePort:                 swing-console  30836/TCP
Endpoints:                10.36.0.1:58080
Port:                     web-console  58082/TCP
TargetPort:               58082/TCP
NodePort:                 web-console  31555/TCP
Endpoints:                10.36.0.1:58082
Port:                     web-console-secure  58083/TCP
TargetPort:               58083/TCP
NodePort:                 web-console-secure  31419/TCP
Endpoints:                10.36.0.1:58083
Port:                     swing-console-secure  58081/TCP
TargetPort:               58081/TCP
NodePort:                 swing-console-secure  32268/TCP
Endpoints:                10.36.0.1:58081
Session Affinity:         ClientIP
External Traffic Policy:  Local
HealthCheck NodePort:     31305
Events:                   <none>

Now, you can access the Control Center application using the IP address 111.22.333.444. The URL will be https://<LoadBalancer Ingress>:<port value given in webHttpsPort in ConfigMap>/, i.e., https://111.22.333.444:58083/.

Here, 58083 is the webHttpsPort value given in the ConfigMap. If an Ingress resource has been created, the Control Center service can be accessed using the hostname.

For example: https://<hostname>/

Example: test.sccm.com

https://test.sccm.com/

To access the application using the hostname, ensure that the DNS server is configured. If not, you need to add an entry with the hostname and IP address in the /etc/hosts file. The IP address can be found using the following command:
$ oc get ing -n ibm-sccm
NAME               CLASS   HOSTS         ADDRESS          PORTS   AGE
ibm-sccm-ingress   nginx   test.sccm.com 111.22.333.444   80      2d

The IP address (111.22.333.444) will match with the hostname. Now, proceed by logging into the Web Console using the default user credentials and its corresponding password.

Execute a Sample Business Process

To confirm the proper functioning of fundamental Control Center features, execute an end-to-end sample business process. This may involve actions such as adding a Connect:Direct server or executing a report.

Follow the high-level steps defined below to add a Connect:Direct server:
  1. Navigate to Control Center Monitor Web Console.
  2. Go to Servers > Add Server.
  3. Enter the Server Name, choose the Server Type as Connect:Direct, and provide other necessary details.
  4. Verify the addition of the server in the Server List.

Troubleshooting

When you encounter an issue in your Kubernetes environment, run the following checks to assist you with troubleshooting process.
  • Generic Checks
    1. To check container logs. See, CCStartup.log in log directory.
    2. To check Engine logs, see nohup.out.

View Logs

Run the following commands to check the logs of Control Center.
$ oc logs pod_name -n ibm-sccm

Some basic commands

  1. Invoke the following command to log into the container:
    $ oc exec -it pod_name -n ibm-sccm -- /bin/bash
  2. Invoke ./stopEngine.sh -np to stop Control Center Monitor Engine
  3. Exit the Docker container (enter exit command twice) and invoke the following command to invoke the configCC utility:
    $ oc exec -it pod_name -n ibm-sccm -- /app/CC/bin/configCC.sh
  4. To start control center engine, first login inside container and then call runEngine.sh in bin folder.