Post Installation Task
Validating the Deployment
Once the deployment of IBM Sterling Control Center Monitor is finished, validate the installation to ensure that all components are functioning as expected.
$ oc describe svc -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 running pod, and the port numbers will correspond to those specified in the ConfigMap.
$ oc get pods -n ibm-sccm -o wide
NAME READ STATUS RESTARTS AGE IP NODE NOMINATED NODE
ibm-sccm-statefulset-0 1/1 Running 0 16h 10.36.0.1 ccrdock-01 <none> <none>
With the verification of service and pod connectivity complete, the next step is to confirm access to the Control Center application.
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, the IP address 111.22.333.444 will be used to access the control center
application. 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
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/
$ 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
Here, IP address is 111.22.333.444 which will be matched with the hostname.
Once the service and pod connectivity have been verified, proceed by logging into the Web Console using the default user credentials and their 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.
- Navigate to Control Center Monitor Web Console.
- Go to .
- Enter the Server Name, choose the Server Type as Connect:Direct, and provide other necessary details.
- Verify the addition of the server in the Server List.
Troubleshooting
- Generic Checks
- To check container logs see, CCStartup.log in log directory.
- To check Engine logs, see nohup.out.
- View Logs
- Invoke the following command to log into the
container:
$ oc exec -it pod_name -n ibm-sccm -- /bin/bash
- Invoke stopEngine.sh to stop Control Center Monitor Engine
- 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
- To start control center engine, first login inside container and then call runEngine.sh in bin folder.
- Invoke the following command to log into the
container: