Daniel Micanek virtual Blog – Like normal Dan, but virtual.
Historically, SD cards or USB devices have been chosen to free up device bays and lower the cost of installing ESXi hosts. Such devices, however, have lower endurance and exhibit reliability and issues over time. SD cards and USB drives may also exhibit performance issues and may not tolerate […]
Colbert will shape the technology vision for the company and drive foundational technologies for the company’s next stage of growth
Well here we are again – another VMworld has come around. As most of you will know, VMworld 2021 is going to be fully virtual event. Here are My Top 10 Sessions:
Curious how Project Monterey and SmartNICs will redefine the data center for VMware ESXi hosts and bare-metal systems?
Reducing the amount of time required to update and upgrade your systems is imperative as the number of systems and environments grow
Is app modernization top of mind for your business? You’re not alone, but many are struggling to begin
Got VEBA? The VMware Event Broker Appliance has come a long way since its release 3 years ago
Ever experience application migration paralysis? Fear not!
Legacy network operations & management solutions have been primarily reactive. Enter the self-healing network
Apps are the lifeblood of the business in today’s digital economy. Can you envision seamless connectivity between your apps & networking technologies?
Managing Kubernetes clusters across teams and clouds can be difficult. Not with Tanzu Mission Control.
Questions on how VMware Tanzu Kubernetes Grid works? Our experts are here for you!
With the expansion of VMware’s security portfolio, you may be wondering how all of the pieces fit together into a cohesive multi-cloud enterprise design
what better way to celebrate innovation than by updating our ESXi-Arm Fling? NVIDIA Xavier, Altra, bug fixes and perf improvements.
We can see annual incidence of uncorrectable errors is rissing. Here is one possibility – How to solved it with FRM.
Some systems have reliable memory, which is a part of memory that is less likely to have hardware memory errors than other parts of the memory in the system. If the hardware exposes information about the different levels of reliability, ESXi might be able to achieve higher system reliability.
Configuration is in BIOS policy / Advanced / RAS Memory
8GB Could be enough for ESXi hypervisor …
This forces the Hypervisor and some core kernel processes to be mirrored between DIMMs so ESXi itself can survive the complete and total failure of a memory DIMM.
# esxcli hardware memory get Physical Memory: 540800864256 Bytes Reliable Memory: 8589934592 Bytes NUMA Node Count: 2
# esxcli system settings kernel list | grep useReliableMem useReliableMem Bool TRUE TRUE TRUE System is aware of reliable memory.
I can decided to configure more Reliable Memory for VM – not only 8GB for hypervisor.
To turn on the feature per VM:
sched.mem.reliable = "True"Memory Errors and Dell EMC PowerEdge YX4X Server Memory RAS Features
After you finish the prerequisites for upgrading, your next step is to update the upgrade coordinator to initiate the upgrade process.
Trending support issues in VMware NSX (2131154) – This article provides information regarding trending issues and important Knowledge Base articles regarding VMware NSX Data Center for vSphere 6.x and VMware NSX-T Data Center 3.x.
The upgrade coordinator runs in the NSX Manager. It is a self-contained web application that orchestrates the upgrade process of hosts, NSX Edge cluster, NSX Controller cluster, and Management plane.
After the upgrade coordinator has been upgraded, based on your input, the upgrade coordinator updates the NSX Edge cluster, hosts, and the Management plane. Edge upgrade unit groups consist of NSX Edge nodes that are part of the same NSX Edge cluster. You can reorder Edge upgrade unit groups and enable or disable an Edge upgrade unit group from the upgrade sequence.
You can upgrade your hosts using the upgrade coordinator.
The upgrade sequence upgrades the Management Plane at the end. When the Management Plane upgrade is in progress, avoid any configuration changes from any of the nodes.
| Task | Instructions |
|---|---|
| Review the known upgrade problems and workaround documented in the NSX-T Data Center release notes. | See the NSX-T Data Center Release Notes. |
| Follow the system configuration requirements and prepare your infrastructure. | See the system requirements section of the NSX-T Data Center Installation Guide. |
| Evaluate the operational impact of the upgrade. | See Operational Impact of the NSX-T Data Center Upgrade. |
| Upgrade your supported hypervisor. | See Upgrading Your Host OS. |
| If you have an earlier version of NSX Intelligence installed, upgrade the NSX Intelligence appliance first. | See the Installing and Upgrading VMware NSX Intelligence documentation at https://docs.vmware.com/en/VMware-NSX-Intelligence/index.html for more information. |
| Complete the Pre-Upgrade Tasks. | See Pre-Upgrade Tasks. |
| Verify that the NSX-T Data Center environment is in a healthy state. | See Verify the Current State of NSX-T Data Center. |
| Download the latest NSX-T Data Center upgrade bundle. | See Download the NSX-T Data Center Upgrade Bundle. |
| If you are using NSX Cloud for your public cloud workload VMs, upgrade NSX Cloud components. | See Upgrading NSX Cloud Components. |
| Upgrade your upgrade coordinator. | See Upgrade the Upgrade Coordinator. |
| Upgrade the NSX Edge cluster. | See Upgrade NSX Edge Cluster. |
| Upgrade the hosts. | See Configuring and Upgrading Hosts . |
| Upgrade the Management plane. | See Upgrade Management Plane. |
| Post-upgrade tasks. | See Verify the Upgrade. |
| Troubleshoot upgrade errors. | See Troubleshooting Upgrade Failures. |
Verify that the upgrade bundle is available. See Download the NSX-T Data Center Upgrade Bundle.
tanzu-nsx> get service install-upgrad
Wed May 19 2021 UTC 18:58:00.174
Service name: install-upgrade
Service state: running
Enabled on: 10.254.201.169
The NSX Edge nodes are upgraded in serial mode so that when the upgrading node is down, the other nodes in the NSX Edge cluster remain active to continuously forward traffic.
| Option | Description |
|---|---|
| Serial | Upgrade all the Edge upgrade unit groups consecutively. |
| Parallel | Upgrade all the Edge upgrade unit groups simultaneously. |
| When an upgrade unit fails to upgrade | You can fix an error on the Edge node and continue the upgrade. You cannot deselect this setting. |
| After each group completes | Select to pause the upgrade process after each Edge upgrade unit group finishes upgrading. |
get upgrade progress-statusIN_PROGRESS:
tanzu-nsx-edge> get upgrade progress-status ********************************************************************* Node Upgrade has been started. Please do not make any changes, until the upgrade operation is complete. Run "get upgrade progress-status" to show the progress of last upgrade step. ********************************************************************* Tue May 18 2021 UTC 21:51:51.235 Upgrade info: From-version: 3.1.1.0.0.17483065 To-version: 3.1.2.0.0.17883603 Upgrade steps: 11-preinstall-enter_maintenance_mode [2021-05-18 21:45:34 - 2021-05-18 21:46:45] SUCCESS download_os [2021-05-18 21:47:34 - 2021-05-18 21:49:01] SUCCESS install_os [2021-05-18 21:49:02 - ] IN_PROGRESS
SUCCESS / Upgrade is not in progress:
tanzu-nsx-edge> get upgrade progress-status Node Upgrade has been started. Please do not make any changes, until the upgrade operation is complete. Run "get upgrade progress-status" to show the progress of last upgrade step. Tue May 18 2021 UTC 21:55:55.278 Upgrade info: From-version: 3.1.1.0.0.17483065 To-version: 3.1.2.0.0.17883603 Upgrade steps: 11-preinstall-enter_maintenance_mode [2021-05-18 21:45:34 - 2021-05-18 21:46:45] SUCCESS download_os [2021-05-18 21:47:34 - 2021-05-18 21:49:01] SUCCESS install_os [2021-05-18 21:49:02 - 2021-05-18 21:51:58] SUCCESS switch_os [2021-05-18 21:52:01 - 2021-05-18 21:52:24] SUCCESS reboot [2021-05-18 21:52:28 - 2021-05-18 21:53:53] SUCCESS migrate_users [2021-05-18 21:55:26 - 2021-05-18 21:55:31] SUCCESS tanzu-nsx-edge> get upgrade progress-status Tue May 18 2021 UTC 21:59:41.501 Upgrade is not in progress
You can customize the upgrade sequence of the hosts, disable certain hosts from the upgrade, or pause the upgrade at various stages of the upgrade process.
| Option | Description |
|---|---|
| Serial | Upgrade all the host upgrade unit groups consecutively. This selection is useful to maintain the step-by-step upgrade of the host components. . |
| Parallel | Upgrade all the host upgrade unit groups simultaneously. You can upgrade up to five hosts simultaneously. |
| When an upgrade unit fails to upgrade | Select to pause the upgrade process if any host upgrade fails. |
| After each group completes | Select to pause the upgrade process after each host upgrade unit group finishes upgrading. |
Hosts in a ESXi cluster appear in one host upgrade unit group in the upgrade coordinator. You can move these hosts from one host upgrade unit group to another host upgrade unit group.
esxcli software vib list | grep nsx nsx-adf 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-cfgagent 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-context-mux 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-cpp-libs 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-esx-datapath 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-exporter 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-host 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-ids 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-monitoring 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-mpa 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-nestdb 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-netopa 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-opsagent 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-platform-client 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-proto2-libs 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-proxy 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-python-gevent 1.1.0-15366959 VMware VMwareCertified nsx-python-greenlet 0.4.14-16723199 VMware VMwareCertified nsx-python-logging 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-python-protobuf 2.6.1-16723197 VMware VMwareCertified nsx-python-utils 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-sfhc 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-shared-libs 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsx-vdpi 3.1.1.0.0-7.0.17483060 VMware VMwareCertified nsxcli 3.1.1.0.0-7.0.17483060 VMware VMwareCertified
esxcli software vib list | grep nsx nsx-adf 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-cfgagent 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-context-mux 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-cpp-libs 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-esx-datapath 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-exporter 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-host 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-ids 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-monitoring 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-mpa 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-nestdb 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-netopa 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-opsagent 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-platform-client 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-proto2-libs 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-proxy 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-python-gevent 1.1.0-15366959 VMware VMwareCertified nsx-python-greenlet 0.4.14-16723199 VMware VMwareCertified nsx-python-logging 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-python-protobuf 2.6.1-16723197 VMware VMwareCertified nsx-python-utils 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-sfhc 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-shared-libs 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsx-vdpi 3.1.2.0.0-7.0.17883598 VMware VMwareCertified nsxcli 3.1.2.0.0-7.0.17883598 VMware VMwareCertified
More info in the NSX-T Data Center Administration Guide.
tanzu-nsx> get upgrade progress-status
Node Upgrade has been started. Please do not make any changes, until
the upgrade operation is complete. Run "get upgrade progress-status"
to show the progress of last upgrade step.
Tue May 18 2021 UTC 22:38:49.533
Upgrade info:
From-version: 3.1.1.0.0.17483186
To-version: 3.1.2.0.0.17883600
Upgrade steps:
download_os [2021-05-18 22:35:57 - 2021-05-18 22:38:04] SUCCESS
shutdown_manager [2021-05-18 22:38:15 - ] IN_PROGRESS
Status: cloud-init status command returned output active.
Some appliance components are not functioning properly.
Component health: MANAGER:UNKNOWN, POLICY:UNKNOWN, SEARCH:UNKNOWN, NODE_MGMT:UP, UI:UP.
Error code: 101
tanzu-nsx> get upgrade progress-status Node Upgrade has been started. Please do not make any changes, until the upgrade operation is complete. Run "get upgrade progress-status" to show the progress of last upgrade step. Tue May 18 2021 UTC 23:09:58.930 Upgrade info: From-version: 3.1.1.0.0.17483186 To-version: 3.1.2.0.0.17883600 Upgrade steps: download_os [2021-05-18 22:35:57 - 2021-05-18 22:38:04] SUCCESS shutdown_manager [2021-05-18 22:38:15 - 2021-05-18 22:56:22] SUCCESS install_os [2021-05-18 22:56:22 - 2021-05-18 22:58:34] SUCCESS migrate_manager_config [2021-05-18 22:58:34 - 2021-05-18 22:58:44] SUCCESS switch_os [2021-05-18 22:58:44 - 2021-05-18 22:59:06] SUCCESS reboot [2021-05-18 22:59:06 - 2021-05-18 23:00:04] SUCCESS run_migration_tool [2021-05-18 23:03:11 - 2021-05-18 23:03:16] SUCCESS start_manager [2021-05-18 23:03:16 - ] IN_PROGRESS
tanzu-nsx> get upgrade progress-status Tue May 18 2021 UTC 23:21:33.659 Upgrade is not in progress
