## Problems after the installation of IBM Cloud Private 

After the cluster is installed, it could present IP connectivity issues across the pods. Service name resolution issues are a symptom of pods not being able to reach the DNS service. These problems are not always related to Calico networks. 

In these situations, gather the following information from the cluster for support: 

1. Get the node list: 

kubectl get nodes -o wide 

2. Get the logs: 

Collect logs from the calico-node-* pod running on the node which is experiencing the mesh problem. Example 8-6 shows how to get the logs from calico-node-*  running on node 10.10.25.71 . 

# kubectl get pods -o wide | grep calico-node calico-node-amd64-2cbjh 2/2 Running 0 7h 10.10.25.70 10.10.25.70 calico-node-amd64-48lf9 2/2 Running 0 7h 10.10.25.71 10.10.25.71 calico-node-amd64-75667 2/2 Running 0 7h 10.10.25.7 10.10.25.7 

3. Retrieve the logs from the calico-node  container in the pod: 

# kubectl logs calico-node-amd64-48lf9 -c calico-node-amd64 

4. Get the routing table and interface details to complete this. Run the commands on master node(s) + nodes on which pods are experiencing the connectivity issues. 

route -n ifconfig -a 

5. Get Calico node list running the command on the master node: 

calicoctl get nodes 

6. Get all the pods and endpoints on Calico mesh by running the command on the IBM Cloud Private master node: 

calicoctl get workload endpoints 

7. Get calico node status and diagnostics. Run the commands on the IBM Cloud Private master node and the nodes on which pods are experiencing connectivity problem: 

calicoctl node status calicoctl node diags 

8. Provide config.yaml  and host files from boot node. 

## Configuring calicoctl 

Perform the following steps: 

1. Log in to the node. Find the calico-ctl  docker image and copy the calicoctl  to node as shown in Example 8-7. 

# docker images | grep "icp-inception" ibmcom-amd64/icp-inception 3.1.0-ee c816bd4546f9 2 days ago 746MB 

