5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Witness VM Upgrades are independent of AOS version or PC version and is also independent of the Nutanix Upgrade order. Please refer to the below Document for the Witness VM Upgrade procedure:https://portal.nutanix.com/page/documents/details?targetId=Prism-Element-Data-Protection-Guide-v6_0%3Asto-metro-availability-witness-upgrade-t.html&a=00009bb166c38ca201b932af77e85c6477c8dc705903152ee3f1356309ed7508b9ac8651e7396128
With both PC and PE on 5.17 AOS version and greater, we can now use Playbooks to expand the VM disk size automatically. Check out this video:
Hi @Sebastian Antunez Please check out our Upgrade Path page to determine if you can Upgrade to a particular version. Sorta like compatibility matrix but for AOS Versions to Jump to. The version you specified dont seems to be compatible. Try 5.15.1
Hi @JasonStenack Please check the command below, this should get you started. Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall | Get-ItemProperty | Where-Object {$_.DisplayName -match 'DellPTAgent'} | Select-Object DisplayVersion, DisplayName, InstallDate | ConvertTo-Json If this does not work, I suppose you are hitting an issue we have noticed where LCM fails to populate the ISM and PTAgent versions due to python version being installed automatically is a 32 bit process and the DELL’s PTAgent/ISM is a 64 bit installation when done manually. Read thru KB-8701 Let me know if this help !! Cheers
Here is how I look at it. Dont not get hung up on what vnet is used for? As of today , CVM has 3 ports, eth0, eth1 and eth2. eth0 is the port connected to the external IP address eth1 is connected to the internal linux bridge. eth2 is present incase customer configures backplane. Use of certain scripts can change what vnet0, vnet1 and vnet2 represents. The way to check this is to match the Mac address of eth0, eth1 and eth2 from CVM (ifconfig) to the ifconfig output shown when run from the host and compare the vnet interfaces. Match the mac address to know which interface is actually external and which one is internal. The only thing set in stone is eth0 is always external and eth1 is always connected to internal linux bridge. The naming of the port where it connects to the OVS is interchangeable and is executed and the time of the boot from the CVM config xml. Output from CVM : eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.2.126.26 netmask
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.
