Perform the following steps to verify the connectivity between source and target cluster.
- Open a terminal in the Dell Telecom Infrastructure Automation Foundation source cluster. Run the following command on the Dell Telecom Infrastructure Automation Foundation Global Controller (CP1) node to fetch its IP address.
kubectl get node -l nodetype=primary -o=jsonpath='{.items[0].status.addresses[?(@.type=="InternalIP")].address}'
Optionally, you can view the mcloud_config.yaml file in the Dell Telecom Infrastructure Automation Foundation bundle to get the IP address of the Global Controller (CP1). The mcloud_config.yaml is used for Dell Telecom Infrastructure Automation Foundation installation.
- Identify the IP address of the Bare Metal Orchestrator Global Controller (CP1) node.
You can view the hosts.ini file in the Bare Metal Orchestrator bundle to get the IP address of the Global Controller (CP1).
- Open a terminal in the target cluster. Run the following command.
ping <DTIAF 1.1 CP1 IP>
Where <DTIAF 1.1 CP1 IP> is the IP address of the Dell Telecom Infrastructure Automation Foundation Global Controller (CP1) node.
The ping command sends packets to the Global Controller (CP1) node, requesting a response. If there is a successful connectivity, a message similar to the following appears to mention no lost packets.
PING 192.168.1.10 (192.168.1.10): 56 data bytes
64 bytes from 192.168.2.20: icmp_seq=0 ttl=64 time=1.011 ms
64 bytes from 192.168.2.20: icmp_seq=1 ttl=64 time=0.987 ms
64 bytes from 192.168.2.20: icmp_seq=2 ttl=64 time=1.003 ms
64 bytes from 192.168.2.20: icmp_seq=3 ttl=64 time=0.998 ms
--- 192.168.1.10 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.987/0.999/1.011/0.012 ms - Open a terminal in the target cluster. Run the following command.
ping <BMO 2.3.0 CP1 IP>
Where <BMO 2.3.0 CP1 IP> is the IP address of the Bare Metal Orchestrator Global Controller (CP1) node.
The ping command sends packets to the Global Controller (CP1) node, requesting a response. If there is a successful connectivity, a message similar to the following appears to mention no lost packets.
PING 192.168.2.20 (192.168.2.20): 56 data bytes
64 bytes from 192.168.2.20: icmp_seq=0 ttl=64 time=1.011 ms
64 bytes from 192.168.2.20: icmp_seq=1 ttl=64 time=0.987 ms
64 bytes from 192.168.2.20: icmp_seq=2 ttl=64 time=1.003 ms
64 bytes from 192.168.2.20: icmp_seq=3 ttl=64 time=0.998 ms
--- 192.168.2.20 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.987/0.999/1.011/0.012 ms