5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Got it. Thanks for your information.
Hi Nupur: The ping_all.INFO only include the latency between the CVM and the gateway, does not include response times between CVMs and CVM-Host like before. as the example information of ping_all.INFO#TIMESTAMP 1656297510 : 06/27/2022 02:38:30 AM IP : latency (threshold = 0.5 ms, payload = 1472 bytes) gw-192.168.30.254 : 5.55 ms#TIMESTAMP 1656297525 : 06/27/2022 02:38:45 AM IP : latency (threshold = 0.5 ms, payload = 1472 bytes) gw-192.168.30.254 : 5.56 ms#TIMESTAMP 1656297540 : 06/27/2022 02:39:00 AM IP : latency (threshold = 0.5 ms, payload = 1472 bytes) gw-192.168.30.254 : 3.05 ms
I have got the some ideas for this problem. Seems it is time issue that caused this problem. If I installed xray on the ESXi platform, therre is no this issue in most of time. But if I installed xray on VMware workstation of the laptop which has different timezone with UTC, then this problem will happen sometimes.
@Sergei Ivanov It is worked after tested in the enviroment. Thanks for your solution.
Hi Segei Thanks for your information, I also noted the file of /srv/salt/security/CVM/Network/hosts.allow description. So l will change the file and check whether it can be worked and update the result. Thanks Sergei.
Hi @JeremyJ I have checked the portal martrix link. If I selected ESXi 6.5 U3 Vendor,and AOS for 5.10.10, there is no hardware model display to meet the version. But AOS 5.10.10 is released recently, I think it will be compatible. If I select ESXi 6.5 U3, and AOS for 5.5.9.5, there are some NX series hardware model can meet it. So my understanding is that maybe OEM partner just did not test some versions. Another concern is that AOS has compatible with ESXi in VMware HCL. And the Hardware also has compatible with VMware. Hardware also has compatible with AOS. This is a triangle. How to treat it rightly?
Hi AntonioG It is very clear and I got it. Thanks for your information.
Hi @Mutahir My another concern is unplanned node remove I have ever meet a real environment, the node has already broken, and the data resilience is already restored. the user reinstall the node with phoenix after replace the satadom, but mistakenly install the node by the install and configure Hypervisor and CVM(wipe data), So the node is initialized and need to be removed from the cluster and add it back. Accordingly, the data has already rebuild in the cluster and the remove process will be very quickly, but finally the remove process last about 20 hours and finished. Do you know why it last so long time? Is it need to do a same process of planned node removal? Regards
@Alona Thanks for your information. What is my meaning is When a node is failure/CVM failure, the data will migrated to other node and the data will be kept the status of RF=2/RF=3. This process will last not long time(serveral minutes or less than a hour), then the data resilience will be restore to OK. But after that, I think the data will kept RF=2/RF=3 status, at this time I want to remove the node from the cluster(prism-hardware-diagram--remove node), accoding to the data resilience status, the cluster is restored and the remove process should be very short. But from the real enviroment operation, The remove process will last serveral hours. What is my concern is the data has already migrated by stargare in the node/cvm failure process. Why I remove the node will last so long time? does any other data will be additional be removed?
Hi [user=77695]Shridhar[/user] Thanks for you information, But I also have questions: [list=1] [*]If mode implies speed, how about the speed imply? [*]In my environment of the snapshot, you can see, 25Gb speed display 10000 mode. actually, its speed is 25Gb. [/list]
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.