VMware:- Cross vCenter Migration

-


Pre-requisites:
1. The source and destination vCenter and ESXi hosts must be running at least vSphere 6.0 or later.

2. Use an Enterprise Plus license. It’s not going to work without it. The cross vCenter Server and long-distance vMotion features require an Enterprise Plus license, so be sure both source and destination environments are licensed properly.
3. Both vCenter Server instances must be in Enhanced Linked Mode and must be in the same vCenter Single Sign-On domain to migrate VMs using the vSphere Web Client. This is because the source vCenter must be able to authenticate to the destination vCenter.
4. Both vCenter Server instances must be time-synchronized with each other for correct vCenter Single Sign-On token verification. Functional NTP is critical for this feature to work! You can check under each host configuration tab.
5. For migration of compute resources only, both vCenter Server instances must be connected to the shared virtual machine storage.
Network Port Requirements
1. 8000 and 902 for vMotion and NFC between ESXi.

2. 902 for NFC on the ESXi host's Management subnet in case of Cross-vCenter vMotion, or cold migration (unless there is a dedicated subnet and vmkernel port).

3. 443 between both vCenter Servers.

4. 443 between vCenter Server and the ESXi server (this is a requirement to have the ESXi host added to vCenter Servers).

Comments

Post a Comment

Popular posts from this blog

VMware:- Esxi Log File Locations

-
Enable SSH and connect the host through CLI tool-  *Authentication- /var/log/auth.log *ESXi host agent log - /var/log/hostd.log *Shell log - /var/log/shell.log *System messages - /var/log/syslog.log *vCenter Server agent log - /var/log/vpxa.log *Virtual machines - The same directory as the affected virtual machine's configuration files, named vmware.log and vmware*.log. For example, /vmfs/volumes/datastore/virtual machine/vmware.log *VMkernel - /var/log/vmkernel.log *VMkernel summary - /var/log/vmksummary.log *VMkernel warnings - /var/log/vmkwarning.log *Quick Boot - /var/log/loadESX.log *Trusted infrastructure agent - /var/run/log/kmxa.log *Key Provider Service - /var/run/log/kmxd.log *Attestation Service - /var/run/log/attestd.log *ESX Token Service - /var/run/log/esxtokend.log *ESX API Forwarder - /var/run/log/esxapiadapter.log
Read more

ESX and vCenter Alarms

-
Image
  Definition An  Alarms  is a   notification  that are activated in response to an event, a set of conditions, or the state of an inventory object. An alarm definition consists of the following elements in the vSphere Client: ·  Name and description - Provides an identifying label and description. ·  Targets - Defines the type of object that is  monitored. -  VM\  DataSore \N\W  etc. ·  Alarm Rules - Defines the event, condition, or state that triggers the alarm and defines the notification severity. It also defines operations that occur in response to triggered alarms. ·  Last modified - The last modified date and time of the defined alarm.   Alarm categories – Alarms have the following severity levels: ·  Normal –  green  -   Status is Good. The health of the object is Normal ·  Warning – yellow  -  Status is Warning – The Object experiencing Some Problem ·  Ale...
Read more

Convert VMware Snapshot into Memory Dump

-
Image
  Convert VMware Snapshot into Memory Dump Background   This document explains about generating a memory dump for a VMWare Virtual Machine when the machine becomes unresponsive. VM becomes unresponsive for various reasons, you may not be able to get into any OS related settings or access any application. Even users may get not be able to access any shares or resources of this machine.   In this type of situation Memory dump would be required to  analyze  the cause. Even if the OS is configured to generate a Memory Dump for System Crashes, it would not be able to generate a Memory Dump for System Unresponsiveness most of the  times. But  with a VMWare VM, you can take a snapshot of the machine when it is unresponsive and then use vmss2core.exe tool to convert the snapshot to a Memory Dump. The target audience for this information is any technician that is responsible for creating and deleting snapshot in the Levi virtualization environment.   Note ...
Read more