sudo rm -rf /var/lib/kubelet/* /var/lib/icp/* /var/lib/calico echo done sudo rm -rf {{ .icpInstallDir }}/cluster/cfc-certs {{ .icpInstallDir }}/cluster/cfc-components {{ .icpInstallDir }}/cluster/cfc-keys {{ .icpInstallDir }}/cluster/.addon {{ .icpInstallDir }}/cluster/.misc ; echo done 

## 8.2 Network configuration errors 

After completing the previous steps, perform the installation again. 

This section describes how to troubleshoot the IBM Cloud Private networking components, such as Calico and IPsec. 

## 8.2.1 Calico troubleshooting 

Calico network issues might show up during or after an IBM Cloud Private installation. During the installation, the installer runs checks to ensure seamless pod-to-pod connectivity in the cluster. However, if there are issues, the following information might help to identify the possible causes and resolve the issues. 

## Problems during the installation 

To avoid Calico network issues during the installation, ensure that the following settings are correctly configured. 

The calico_ipip_enabled  parameter must be set to true  if all the nodes in the cluster do not belong to the same subnet. This parameter must be set to true if the nodes are deployed in a cloud environment such as OpenStack, where source and destination checks prevent the IP traffic from unknown IP ranges, even if all the nodes belong to the same subnet. This configuration enables encapsulation of pod to pod traffic over the underlying network infrastructure. 

The calico_ip_autodetection_method  parameter must be set, so that Calico uses the correct interface on the node. If there are multiple interfaces, aliases, logical interfaces, bridge interfaces, or any other type of interfaces on the nodes, use either the following settings to ensure that the auto-detect mechanism chooses the correct interface. 

GLYPH<SM590000> calico_ip_autodetection_method: can-reach= (This is the default setting.) 

GLYPH<SM590000> calico_ip_autodetection_method: interface= 

GLYPH<SM590000> The calico_tunnel_mtu  parameter must be set based on the MTU of the interface that is configured to be used by Calico. 

GLYPH<SM590000> If the calico_ipip_enabled  parameter is set to true , 20 bytes are used for IP-IP tunnel header. It is required to set the calico_tunnel_mtu  parameter to be at least 20 bytes less than the actual MTU of the interface. 

GLYPH<SM590000> If IPsec is enabled, 40 bytes are needed for the IPsec packet header. Because when you enable IPsec, calico_ipip_enabled to true  is set, you also need the 20 bytes for the IP-IP tunnel header. Therefore, you must set the calico_tunnel_mtu  parameter to be at least 60 bytes less than the actual MTU of the interface. 

GLYPH<SM590000> The network CIDR (Classless Inter-Domain Routing), existing host network, and the service cluster IP range must not be in conflict with each other. 

