0

I have created a Single Node Cluster for Nutanix on VMWare ESXi 7 with configuration of 16 CPU, 64gb RAM, 64GB Hypervisor disk, 200 GB CVM disk and 1.4TB Data Disk with one CVM. I have successfully deployed hypervisor and able to access prism UI. I'm using Nutanix version 6.8.1 CE.

Now I am trying to deploy Nutanix Files on Hypervisor where I have one unmanaged network which I have used for both client and storage network, since this is a test environment. My CVM, AD and File Server all exists in same subnet range and pingable among each other. Now when I start to deploy the file server the progress gets stuck at 50% and fails with the error - "Failed to reach FileServerVm NTNX-vmname-1 from Nutanix Controller Vm Please Check Network Configuration from Contrl".

I have checked minerva_cvm.log where the client network IP was unable to reach from CVM and failed with the following errors

2025-03-12 19:58:19,062Z INFO 44700128 infra_uvm.py:106 No route to host found.

2025-03-12 19:58:24,069Z INFO 44700128 file_server.py:3195 Waiting for FSVM NTNX-nutnxfiles-1 to be up and running.

2025-03-12 19:58:32,140Z WARNING 44700128 genesis_client.py:86 Failed to reach genesis on any of the svm_ips: ['172.24.147.87']

and cassandra,out has thrown the following error

I20250313 11:10:38.000743Z 40947(0x7f3e7c53f400) zookeeper_init:994] Initiating client connection, host=zk1:9876 sessionTimeout=12000 watcher=0x7f3e8693d6c0 sessionId=0 sessionPasswd= context=0x558d6f471e40 flags=0 I20250313 11:10:38.000745Z 40947(0x7f3e7b8f4700) zookeeper_interest:1950] Connecting to server 172.24.147.96:9876 I20250313 11:10:38.000745Z 40947(0x7f3e7b8f4700) zookeeper_interest:1987] Zookeeper handle state changed to ZOO_CONNECTING_STATE for socket [172.24.147.96:9876] I20250313 11:10:38.000745Z 40947(0x7f3e7b8f4700) check_events:2196] initiated connection to server [172.24.147.96:9876] I20250313 11:10:38.000748Z 40947(0x7f3e7b8f4700) check_events:2244] session establishment complete on server [172.24.147.96:9876], sessionId=0x1958f30c8f50021, negotiated timeout=12000 kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] E20250313 11:10:41.363291Z 41532 tcp_client.cc:315] Connection to 127.0.0.1:2049 failed with socket error 111 E20250313 11:10:41.363566Z 41520 counters_vdisk_store.cc:166] Mounting stats container failed with rpc status 2 E20250313 11:10:41.363584Z 41520 counters_backend.cc:171] Failed to initialize counters store with error 1 E20250313 11:10:41.363595Z 41520 counters_backend.cc:182] Failed to mount container

Warning: The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /home/nutanix/data/cassandra/conf/cassandra_keystore.jks -destkeystore /home/nutanix/data/cassandra/conf/cassandra_keystore.jks -deststoretype pkcs12".

Warning: The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /home/nutanix/data/cassandra/conf/cassandra_keystore.jks -destkeystore /home/nutanix/data/cassandra/conf/cassandra_keystore.jks -deststoretype pkcs12". Signature ok subject=C = US, O = nutanix, OU = nutanix, CN = cassandra_node Getting CA Private Key Certificate was added to keystore

Warning: The input uses the SHA1withRSA signature algorithm which is considered a security risk and is disabled. The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /home/nutanix/data/cassandra/conf/cassandra_keystore.jks -destkeystore /home/nutanix/data/cassandra/conf/cassandra_keystore.jks -deststoretype pkcs12". Certificate reply was installed in keystore

Warning: The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /home/nutanix/data/cassandra/conf/cassandra_keystore.jks -destkeystore /home/nutanix/data/cassandra/conf/cassandra_keystore.jks -deststoretype pkcs12". E20250313 11:10:43.014400Z 40947 cassandra_monitor.cc:10656] to_ret= cassandra_ring_state: 172.24.147.96,00000000dBhKHoScQrqW2jxn1yjkukjmnLH1uhDzDosb9nOBv0kyHmBNOnUF,kNormal\n E20250313 11:10:43.148834Z 41781 rpc_client_v2.cc:2773] Connection was refused E20250313 11:10:43.186491Z 41781 tcp_client.cc:315] Connection to 172.24.147.96:9161 failed with socket error 111 E20250313 11:10:43.186651Z 41781 rpc_client_v2.cc:2773] Connection was refused E20250313 11:10:43.224460Z 41781 rpc_client_v2.cc:2773] Connection was refused E20250313 11:10:43.224884Z 41781 tcp_client.cc:315] Connection to 172.24.147.96:9161 failed with socket error 111 E20250313 11:10:43.261292Z 41781 rpc_client_v2.cc:2773] Connection was refused

I was unable to figure out if this was ISO level error or my network configuration error. Since from my CVM I was able to ping the client network IP address. Any help on this...

0 Answers0