Best is to involve nutanix support, they can help you out.
Hello! Just wanted to follow up on this to see if you found a resolution to your issue? I have run across a similar situation with my recent install of CE 2.0.
hello,
i have the same problem after to reboot the server.
do you have any solution?
thanks
best regards
Emanuel
Hello
can anybody help me..
[root@XXX~]# virsh list --all | grep CVM
1 NTNX-XXX-CVM running
groot@XXX~]# ping 192.168.5.254
PING 192.168.5.254 (192.168.5.254) 56(84) bytes of data.
From 192.168.5.1 icmp_seq=1 Destination Host Unreachable
^C
--- 192.168.5.254 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3081ms
pipe 4
4root@XXX ~]# ssh nutanix@192.168.5.2
FIPS mode initialized
ssh: connect to host 192.168.5.2 port 22: No route to host
how to repair cvm ?
seems like its CE , have you tried to add manual routes
Hello
can anybody help me..
[root@XXX~]# virsh list --all | grep CVM
1 NTNX-XXX-CVM running
PING 192.168.5.254 (192.168.5.254) 56(84) bytes of data.
From 192.168.5.1 icmp_seq=1 Destination Host Unreachable
^C
--- 192.168.5.254 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3081ms
pipe 4
FIPS mode initialized
ssh: connect to host 192.168.5.2 port 22: No route to host
how to repair cvm ?
seems like its CE , have you tried to add manual routes
the routes are correct,
at the and i reinstall the CE
Try restarting the network using the “sudo systemctl restart network.service” command.
Check your AHV network configuration “cat /etc/sysconfig/network-scripts/ifcfg-br0” - check if correct NIC is in use, GW, mask, etc. Make sure DHCP is not set. Check if you can ssh to the CVM from outside your AHV, by its primary IP. 192.168.5.254 is only internal IP accessible from AHV if network is setup correctly. As suggested above sometimes network service restart helps (for AHV I would rather use “service network restart”), or try AHV node reboot.
i had a similar issue and it was the vlan tags weren’t set.. might want to check that if all else fails
Try restarting the network using the “sudo systemctl restart network.service” command.
Restarting the network service on Single Cluster Node helped to reset the communication with CVM node.
I soon as you get the answer, please let us now. had similar situaion.
thank you in advance