Dienstag, 12. Oktober 2021
Freitag, 3. September 2021
Nutanix NGT installation failed with cmd.exe /C ""c:\Program Files\Nutanix\Python36\python.exe" -E "c:\Program Files\Nutanix\ssr\ssr_gateway\ssr_gateway_service.py" install"
1. Check the installed softwares and check of NGT was installed before being removed
2. check using powershell if the NGT Infra Component Packages are still present after removing the "old" NGT:
Get-wmiobject -class win32_product -filter "Name = 'Nutanix Guest Tools Infrastructure Components Package 1'"
then remove it:
Get-Package -Name "Nutanix Guest Tools Infrastructure Components Package 1" | Uninstall-Package -Force
3. clean the registry in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and "find" Nutanix - delete the key.
4. Reinstall NGT
Montag, 8. Februar 2021
You will receive the following error message in Prism Element:
System has x aged third-party backup snapshot(s) and they may unnecessarily consume storage space in the cluster.
The problem occurs if snaps are not removed successfully by the backup.
You have to remove the snaps by a script from one of the cvms:
download the latest script:
python backup_snapshots.py --delete_snapshot_older_than 7 admin
Montag, 7. Dezember 2020
To show the Configuration (from any CVM):
hostssh "./ipmitool lan print 1"
apply settings that IPMI does not get locked:
hostssh "./ipmitool lan set 1 bad_pass_tresh 0 0 0 0"
Donnerstag, 26. November 2020
you can use following command to remove the NVIDIA driver from ahv with the following command:
yum remove NVIDIA-vGPU-ahv-2019-440.121.x86_64
please replace the NVIDIA-vGPU-ahv-2019-440.121.x86_64 with your current installed driver
Montag, 30. März 2020
cmsso-util domain-repoint -m execute --src-emb-admin Administrator --replication-partner-fqdn vCenter1.domain.intern --replication-partner-admin Administrator --dest-domain-name vsphere.local
Enter Source embedded vCenter Server Admin Password :
Enter Replication partner Platform Services Controller Admin Password :
The domain-repoint operation will export License, Tags, Authorization data
before repoint and import after repoint.
WARNING: Global Permissions for the source vCenter Server system will be lost. The
administrator for the target domain must add global permissions manually.
Source domain users and groups will be lost after the Repoint operation.
User 'Administrator@vsphere.local' will be assigned administrator role on the
source vCenter Server system.
The default resolution mode for Tags and Authorization conflicts is Copy,
unless overridden in the conflict files generated during pre-check.
Solutions and plugins registered with vCenter Server must be re-registered.
Before running the Repoint operation, you should backupof all nodes
including external databases. You can use file based backups to restore in
case of failure. By using the Repoint tool you agree to take the responsibility
for creating backups, otherwise you should cancel this operation.
Starting with vSphere 6.7, VMware announced a simplified vCenter Single Sign-On
domain architecture by enabling vCenter Enhanced Linked Mode support for
vCenter Server Appliance installations with an embedded Platform Services
Controller. You can use the vCenter Server converge utility to change the
deployment topology from an external Platform Services Controller to an
embedded Platform Services Controller with support for vCenter Enhanced Linked
Mode. As of this release, the external Platform Services Controller
architecture is deprecated and will not be available in future releases. For
more information, see https://kb.vmware.com/s/article/60229
The following license keys are being copied to the target Single Sign-On
domain. VMware recommends using each license key in only a single domain. See
"vCenter Server Domain Repoint License Considerations" in the vCenter Server
Installation and Setup documentation.
Repoint Node Information:
Source embedded vCenter Server:vCenter2.domain.intern
Replication partner Platform Services Controller: vCenter1.domain.intern
All Repoint configuration settings are correct; proceed? [Y|y|N|n]: y
Starting License export ... Done
Starting Authz Data export ... Done
Starting Tagging Data export ... Done
Export Service Data ... Done
Uninstalling Platform Controller Services ... Done
Stopping all services ... Done
Updating registry settings ... Done
Re-installing Platform Controller Services ... Done
Registering Infra services ... Done
Updating Service configurations ... Done
Starting License import ... Done
Starting Authz Data import ... Done
Starting Tagging Data import ... Done
Applying target domain CEIP participation preference ... Done
Starting all services ... Done
root@vCenter2 [ ~ ]#
Donnerstag, 5. Dezember 2019
This will show all users:
[root@esxi]# /ipmitool user list
so mostly user "2" is the default ADMIN user. you can reenable it using following command:
[root@esxi]# /ipmitool user enable 2
Dienstag, 12. November 2019
allssh 'genesis status | grep foundation'
genesis stop foundation
ecli task.list include_completed=false
If there is nothing running, you can do this in Phoenix:
Then the host will boot back to HV, you will have to remove the CVM from maintenance mode:
cluster status (to see, if everything in the Cluster is ok)
ncli host list (to get UUID from the host)
ncli host edit id=<insert uuid here> enable-maintenance-mode='false'
Check the metadataring:
nodetool -h localhost ring
If the Host is AHV, you have to leave Maintenance Mode for AHV, too:
acli host.exit_maintenance_mode <hostname>
Mittwoch, 15. Mai 2019
set max connection per nfs store to 32 by using:
esxcfg-advcfg -s 32 /SunRPC/MaxConnPerIP
or via GUI in advanced settings of the esxi server
Dienstag, 16. April 2019
1. Please shutdown the VM
2. Connect to any of the cvm
3. Update the nic: acli vm.nic_update VMNAME 50:6b:8d:1e:40:50 network=VLAN_150
Please verify that if you configured a proxy server, that you whitelist the PC-IP-Adress at PE Site and the PE-IP-Adress from PC Site. Otherwise Prism tries to connect by using the proxy.
Dienstag, 9. April 2019
you can set the following commands in a nutanix CVM. If you are not using nutanix - you can remove the "hostssh" parameter in front of the command.
1. Set active uplink ports in vSwitch0
hostssh esxcli network vswitch standard policy failover set -a vmnic2,vmnic3 -v vSwitch0
2. Remove unused ports in vSwitch0
hostssh esxcli network vswitch standard uplink remove --uplink-name=vmnic0 --vswitch-name=vSwitch0
3. Create VM portgroup in vSwitch 0
hostssh esxcli network vswitch standard portgroup add -p <VM NETWORK> -v vSwitch0
4. Set vlan ID for the newly created portgroup
hostssh esxcli network vswitch standard portgroup set -p <VM NETWORK> --vlan-id 55
Donnerstag, 14. Februar 2019
Freitag, 1. Februar 2019
connect to a cvm:
ecli task.list include_completed=false
ergon_update_task --task_uuid='UUID' --task_status=succeeded