Professional Documents
Culture Documents
1.What is SvMotion?
Migration of a virtual machine files and disks from one datastore to another with Zero
downtime.
2. What are the use cases of SvMotion ?
Migrating from Old storage to new storage systems or migrating to different vendor
storage without downtime to VM's.
Performing Scheduled activity like storage upgrades on the source Lun.
Converting VM disk type from Thick to Thin and Thin to Thick.
Migrating the critical virtual machines to high performance storage arrays to improve
performance of virtual Machine.
ESX host in which virtual machine is running should have access to source and
destination storage.
ESX host should have configured with the license for svMotion
svMotion copies all the files expect virtual machine disk and create the directory as
same the Virtual Machine name on the destination storage.
It uses Changed Block tracking to track the virtual machine disk. The change block
tracking knows which region disk includes data. This data will be stored in bitmap and
reside either in memory or in a file.
Pre-copies Virtual machine disk and swap file will start from the source to destination
datastore as the first iteration. once it is completed, It only transfers the region which
were modified or written after the first iteration.
ESX performs fast suspend and resume of the virtual Machine. The final changed
regions will be copied to the destination before the virtual Machine is resumed on the
destination datastore.
Virtual Machine will continue running on the destination datastore and source file and
disk will be deleted.
Virtual machines configured with the Raw Device Mapping(RDM) for clustering
features using vMotion
VM cannot be connected to a CD-ROM or floppy drive that is using an ISO or
floppy image stored on a drive that is local to the host server. The device should be
disconnected before initiating the vMotion.
Virtual Machine cannot be migrated with VMotion unless the destination swapfile
location is the same as the source swapfile location. As a best practice, Place the virtual
machine swap files with the virtual machine configuration file.
Virtual Machine affinity must not be set (aka, bound to physical CPUs).
A request has been made that VM-1 should be migrated (or "VMotioned") from ESX A
to ESX B.
VM-1's memory is pre-copied from ESX A to ESX B while ongoing changes are
written to a memory bitmap on ESX A.
VM-1 is quiesced on ESX A and VM-1's memory bitmap is copied to ESX B.
VM-1 is started on ESX B and all access to VM-1 is now directed to the copy running
on ESX B.
The rest of VM-1's memory is copied from ESX A all the while memory is being read
and written from VM-1 on ESX A when applications attempt to access that memory on
VM-1 on ESX B.
If the migration is successful, VM-1 is unregistered on ESX A.
VC agent is an agent installed on ESX server which enables communication between VC and
ESX server. This Agent will be installed on ESX/ESXi will be done when you try to add the
ESx host in Vcenter.
What is the command used to restart SSH, NTP & Vmware Web access?
Service sshd restart
Service ntpd restrat
Service vmware-webaccess restart
What are the types of Ports groups in ESX/ESXi?
There are 3 types of port groups in ESX
1.Service console port group
2.VMkernel Port group
3. Virtual machine port group
There are only 2 types of port group in ESXi
1. Vmkernel Port group
2.Virtual Machine Port group
What is VMKernel ?
VMWare Kernel is a Proprietary kernel of vmwareand is not based on any of the flavors of
Linux operating systems, .VMkernel requires an operating system to boot and manage the
kernel. A service console is being provided when VMWare kernel is booted. Only service
console is based up on Redhat Linux OS not VMkernel.
What is the use of Service Console port ?
Service console port group required to manage the ESX server and it acts as the management
network for the ESX. Vcenter/Vsphere Client uses the service console IP's to communicate
with the ESX server.
What is the use of VMKernel Port ?
Vmkernel port is used by ESX/ESXi for vmotion, ISCSI & NFS communications. ESXi uses
Vmkernel as the management network since it don't have service console built with it.
What is the use of Virtual Machine Port Group?
If the promiscuous mode set to Accept, all the communication is visible to all the virtual
machines, in other words all the packets are sent to all the ports on vSwitch. It can be useful
when you are running virtual machines with network sniffers to capture packet in that network.
Traffic shaping policies are disabled by default. There are 3 different traffic shaping policy
setting
Average Bandwidth
Peak Bandwidth
Burst Size
Route based on the originating virtual switch port ID - Chooses an uplink based on the
virtual port where the traffic entered the virtual switch. The traffic will be always send with
that same uplink until that particular uplink is failed and failed over to another NIC.
Route based on source MAC hash - Choose an uplink based on a hash of the source Ethernet
MAC address.The traffic will be always send with that same uplink until that particular uplink
is failed and failed over to another NIC.
Route based on IP hash - Choose an uplink based on a hash of the source and destination IP
What is the command to check the IP address along with the detailed network cards
assigned to the esx server?
Ifconfig -a
Output appears like this
===================================================================
=====
lo
======
[root@ESXTEST1 etc]# ip addr
1: lo: mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: vmnic0: mtu 1500 qdisc noop qlen 1000
link/ether 00:0c:29:85:0d:76 brd ff:ff:ff:ff:ff:ff
3: vmnic1: mtu 1500 qdisc noop qlen 1000
link/ether 00:0c:29:85:0d:80 brd ff:ff:ff:ff:ff:ff
4: vmnic2: mtu 1500 qdisc noop qlen 1000
link/ether 00:0c:29:85:0d:8a brd ff:ff:ff:ff:ff:ff
5: vmnic3: mtu 1500 qdisc noop qlen 1000
link/ether 00:0c:29:85:0d:94 brd ff:ff:ff:ff:ff:ff
6: vswif0: mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:50:56:4d:69:d1 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.75/24 brd 192.168.0.255 scope global vswif0
7: vswif1: mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:50:56:4f:45:b1 brd ff:ff:ff:ff:ff:ff
9: vswif2: mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:50:56:43:92:be brd ff:ff:ff:ff:ff:ff
inet 192.168.0.96/24 brd 192.168.0.255 scope global vswif2
===================================================================
======
what is the command to check the ESX vswitch details, port group and its ip address?
Esxcfg-vswitch -l
Outuput will appear like this:
===================================================================
======
[root@ESXTEST1 ~]# esxcfg-vswitch -l
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch0
32
4
32
1500 vmnic0
PortGroup Name
VLAN ID Used Ports Uplinks
Service Console 0
1
vmnic0
VMkernel
0
1
vmnic0
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch1
64
3
64
1500 vmnic2,vmnic1
PortGroup Name
VM-10.0.0 subnet
VM-192.168.0 subnet 0
vmnic2,vmnic1
Uplinks
PortGroup Name
VLAN ID Used Ports Uplinks
Service Console 2 0
1
vmnic3
Vmotion
0
1
vmnic3
===================================================================
======
From the above output,
we come to know that we have 3 virtual switches named vSwitch0,vSwitch1 and vSwitch2.
4 uplinks (physical nics in our esx server) Vmnic0,vmnic1,vmnic2,vmnic3.
vswitch0 constains 2 port group (Service Console & VMKernel), vSwitch1 contains 2 virtual
machine port group (VM-10.0.0 subnet & VM-192.168.0 subnet) and Vswitch2 contains 2 port
group (Service Console 2 & Vmotion) port group.
What is command to get the information about Service console ports and its IP address
assigned to it?
esxcfg-vswif -l
Output will appear like this:
===================================================================
======
[root@ESXTEST1 ~]# esxcfg-vswif -l
Name Port Group/DVPort IP Family IP Address
Netmask
Broadcast
Enabled TYPE
vswif0 Service Console IPv4
192.168.0.75
255.255.255.0
192.168.0.255 true
STATIC
vswif1 Service Console 2 IPv4
192.168.0.78
255.255.255.0
192.168.0.255 false STATIC
===================================================================
======
what is the command to get the information about vmkernel ports and its ip address?
esxcfg-vmknic -l
Output will appear like this:
===================================================================
======
[root@ESXTEST1 ~]# esxcfg-vmknic -l
Interface Port Group/DVPort IP Family IP Address
Netmask
Broadcast
MAC Address
MTU TSO MSS Enabled Type
vmk0
VMkernel
IPv4
192.168.0.110
255.255.255.0
192.168.0.255 00:50:56:78:7e:73 1500 65535 true STATIC
vmk1
Vmotion
IPv4
192.168.0.77
255.255.255.0
192.168.0.255 00:50:56:76:42:df 1500 65535 true S
===================================================================
======
what is the command to get the information about physical nics installed on ESX server?
esxcfg-vmknic -l
Output will appear like this:
===================================================================
======
[root@ESXTEST1 sbin]# esxcfg-nics -l
Name PCI
Driver
Link Speed Duplex MAC Address
MTU Description
vmnic0 02:00.00 e1000
Up 1000Mbps Full 00:0c:29:85:0d:76 1500 Intel Corporation
82545EM Gigabit Ethernet Controller (Copper)
vmnic1 02:02.00 e1000
Up 1000Mbps Full 00:0c:29:85:0d:80 1500 Intel Corporation
82545EM Gigabit Ethernet Controller (Copper)
vmnic2 02:03.00 e1000
Up 1000Mbps Full 00:0c:29:85:0d:8a 1500 Intel Corporation
82545EM Gigabit Ethernet Controller (Copper)
vmnic3 02:04.00 e1000
Up 1000Mbps Full 00:0c:29:85:0d:94 1500 Intel Corporation
82545EM Gigabit Ethernet Controller (Copper)
===================================================================
=====
What is command to add the new virtual switch named (vswitch3) to our ESX server?
[root@ESXTEST1 sbin]# esxcfg-vswitch -a vswitch3
Now vswitch3 is created without any port group.
===================================================================
===
Switch Name Num Ports Used Ports Configured Ports MTU
vswitch3
64
1
64
1500
Uplinks
PortGroup Name
VLAN ID Used Ports Uplinks
===================================================================
=====
What is command to add the new port group named (mgmt)to vswitch (vswitch 3) ?
How to add the service console port (vswif2) to our newly created port group "mgmt"
with the ip addr 192.168.0.79 ?
[root@ESXTEST1 sbin]# esxcfg-vswif -a vswif2 -i 192.168.0.79 -n 255.255.255.0 -p "mgmt"
where i is the ip address, n is subnet mask p is to mentione the port group name
===================================================================
======
vswif2 mgmt
IPv4
192.168.0.79
255.255.255.0
192.168.0.255 true
STATIC
===================================================================
======
How to add the vmkernal port (vmk2) to our newly created port group "mgmt" with the
ip addr 192.168.0.83?
[root@ESXTEST1 sbin]# esxcfg-vmknic -a -i 192.168.0.83 -n 255.255.255.0 -p "mgmt"
===================================================================
======
vmk2
mgmt
IPv4
192.168.0.83
255.255.255.0 192.168.0.255
00:50:56:7b:bd:36 1500 65535 true STATIC
===================================================================
======
How to change the ip addresss of the existing service console "vswif2"?
nano /etc/sysconfig/network-scripts/ifcfg-vswif2.
Edit the file with your new id address " 192.168.0.255" then save and exit.
======================================================
DEVICE=vswif2
HOTPLUG=yes
MACADDR=00:50:56:43:92:be
ONBOOT=yes
PORTGROUP=mgmt
BOOTPROTO=static
BROADCAST=192.168.0.255
DHCPV6C=no
IPADDR=192.168.0.96
IPV6INIT=no
IPV6_AUTOCONF=no
NETMASK=255.255.255.0
======================================================
restart the network service for ip change to take effect:
[root@ESXTEST1 sysconfig]# service network restart
Shutting down interface vswif0:
[ OK ]
Shutting down interface vswif2:
[ OK ]
Shutting down loopback interface:
[ OK ]
Bringing up loopback interface:
[ OK ]
Bringing up interface vswif0:
[ OK ]
Another way is to connect to the console of the ESX server and at the shell prompt type in
:esxcfg-vswif -d vswif2
This will delete the existing vswif0 and it will give the message about "nothing to flush".
then type the below command
esxcfg-vswif -a vswif2 -p mgmt -i 192.168.0.97 -n 255.255.255.0
===================================================================
======
[root@ESXTEST1 etc]# esxcfg-vswif -d vswif2
Nothing to flush.
[root@ESXTEST1 etc]# esxcfg-vswif -a vswif2 -p mgmt -i 192.168.0.97 -n 255.255.255.0
[2011-09-17 19:35:46 'Vnic' warning] Generated New MAC address, 00:50:56:43:92:be for
vswif2
Nothing to flush.
===================================================================
======
How to change the ESX host name and default gateway?
How to open the port in firewall (port no 8877, tcp, incoming , name: test3 ?
esxcfg-firewall -o 8877,tcp,in,test3
Power off All the VMs are powered off , when the HA detects that the network isolation
occurs
Shut down All VMs running on that host are shut down with the help of VMware Tools,
when the HA detects that the network isolation occurs.If the shutdown via VMWare tools not
happened within 5 minutes, VM's power off operation will be executed. This behavior can be
changed with the help of HA advanced options. Please refer my Post on HA Advanced
configuration
Leave powered on The VM's state remain powered on or remain unchanged, when the HA
detects that the network isolation occurs.
How to add additional isolation address for redundancy?
By default, VMWare HA use to ping default gateway as the isolation address if it stops
receiving heartbeat.We can add an additional values in case if we are using redundant service
console both belongs to different subnet.Let's say we can add the default gateway of SC1 as
first value and gateway of SC2 as the additional one using the below value
1. Right Click your HA cluster
2. Goto to advanced options of HA
3. Add the line "das.isolationaddress1 = 192.168.0.1"
4. Add the line "das.isolationaddress2 = 192.168.1.1" as the additional isolation address
To know more about the Advanced HA Options
What is HA Admission control?
As per "VMware Availability Guide",
VCenter Server uses admission control to ensure that sufficient resources are available in a
cluster to provide failover protection and to ensure that virtual machine resource reservations
are respected.
What are the 2 types of settings available for admission control?
Select the maximum number of host failures that you can afford for or to guarantee fail over.
Let's take an example, you are performing network maintenance activity on your switches
which connects your one of th ESX host in HA cluster.
what will happen if the switch connected to the ESX host in HA cluster is down?
It will not receive heartbeat and also ping to the isolation address also failed. so, host will think
itself as isolated and HA will initiate the reboot of virtual machines on the host to other hosts in
the cluster. Why do you need this unwanted situation while performing scheduled maintenance
window.
To avoid the above situation when performing scheduled activity which may cause ESX host to
isolate, remove the check box in " Enable Host Monitoring" until you are done with the
network maintenance activity.
How to Manually define the HA Slot size?
By default, HA slot size is determined by the Virtual machine Highest CPU and memory
reservation. If no reservation is specified at the VM level, default slot size of 256 MHZ for
CPU and 0 MB + memory overhead for RAM will be taken as slot size. We can control the HA
slot size manually by using the following values.
There are 4 options we can configure at HA advanced options related to slot size
das.slotMemInMB - Maximum Bound value for HA memory slot size
das.slotCpuInMHz - Maximum Bound value for HA CPU slot Size
das.vmMemoryMinMB - Minimum Bound value for HA memory slot size
das.vmCpuMinMHz - Minimum Bound value for HA CPU slot size
For More HA related Advanced options, Please refer my blog post
How the "Percentage of cluster resources reserved as failover spare capacity" admission
control policy works?
In the Percentage of cluster resources reserved as failover spare capacity admission control
policy, We can define the specific percentage of total cluster resources are reserved for
failover.In contrast to the "Host Failures cluster tolerates admission control policy", It will not
use slots. Instead This policy calculates the in the way below
1.It calculates the Total resource requirement for all Powered-on Virtual Machines in the
cluster and also calculates the total resource available in host for virtual machines.
2.It calculates the current CPU and Memory Failover capacity for the capacity.
3.If the current CPU and Memory Failover capacity for the cluster < configured failover
capacity (ex 25 %)
4.Admission control will not allow to power on the virtual machine which violates the
availability constraints.
How the "Specify a failover host" admission control policy works?
In the Specify a failover host" admission control policy, We can define a specific host as a
dedicated failover host. When isolation response is detected, HA attempts to restart the virtual
machines on the specified failover host.In this Approach, dedicated failover hist will be sitting
idle without actively involving or not participating in DRS load balancing.DRS will not
migrate or power on placement of virtual machines on the defined failover host.
What is VM Monitoring status?
HA will usually monitors ESX hosts and reboot the virtual machine in the failed hosts in the
other host in the cluster in case of host isolation but i need the HA to monitors for Virtual
machine failures also. here the feature called VM monitoring status as part of HA settings.VM
monitoring restarts the virtual machine if the vmware tools heartbeat didn't received with the
specified time using Monitoring sensitivity.
4. Check the ESX networks are properly configured and named exactly as other hosts in the
cluster.
otherwise, you will get the below errors while installing or reconfiguring HA
agent.
5. Check HA related ports are open in firewall to allow for the communication
Incoming port: TCP/UDP 8042-8045
Outgoing port: TCP/UDP 2050-2250
6. Try to restart /stop/start the vmware HA agent on the affected host using the below
commands.
In addition, u can also try to restart vpxa and management agent in the Host.
service vmware-aam restart
service vmware-aam stop
service vmware-aam start
7. Right Click the affected host and click on "Reconfigure for VMWare HA" to re-install the
HA agent that particular host.
Additional Isolation Address: By default, VMWare HA use to ping default gateway as the isolation address if it stops
receiving heartbeat.We can add an additional values in case if we are using redundant service
console both belongs to different subnet.Let's say we can add the default gateway of SC1 as
first value and gateway of SC2 as the additional one using the below value
1. Right Click your HA cluster
2. Goto to advanced options of HA
3. Add the line "das.isolationaddress1 = 192.168.0.1"
4. Add the line "das.isolationaddress1 = 192.168.1.1" as the additional isolation address
Changing Default Isolation Address:By default, VMWare HA uses default gateway as the isolation address incase if its stop
receiving heartbeat. Let's take an example, In your organization, Firewall policy is blocking
the ICMP ping or your gateway address is not pingable. In that case, HA fells itself that host is
isolated. This default isolation address can be changed using the below value.
Configuring vMotion network to use for HA heartbeat usage:To configure the HA heartbeat to utilize the nic which is used for Vmotion network. By this
value configured, HA heartbeat communication will be send via the nic which is used for
vmotion communication.
1. Right Click your HA cluster
2. Goto to advanced options of HA
3. Add the line "das.allowVmotionNetworks = True"
Configuring retries for restart of Virtual Machines:When the ESX host is isolated and HA tries to restart the Virtual machine running on the
isolated ESX host to the non-isolated ESS host in the HA cluster. By default, The retry value is
5. You can reduce the value of reties by using the below value
1. Right Click your HA cluster
Ignore the Network redundant warning:We all may be come across the warnings in our HA cluster that " No redundant network for the
management network incase if we don't have redundant service consoles. To vanish the
warnings to appear due to non-redundant service console in cluster, configure the below value
to TRUE.
1. Right Click your HA cluster
2. Goto to advanced options of HA
3. Add the line "das.bypassNetCompatCheck = TRUE " to vanish the warnings from the HA
Cluster.
Configuring Manual HA Slot Size:By default, HA slot size is determined by the Virtual machine Highest CPU and memory
reservation. If no reservation is specified at the VM level, default slot size of 256 MHZ for
CPU and 0 MB + memory overhead for ram will be taken as slot size. We can control the HA
slot size manually by using the following values.
There are 4 options we can configure at HA advanced options related to slot size
Changing HA heartbeat interval:By default, HA heart beat interval is 1000 milliseconds i.e 1 seconds. primary HA node will
send heartbeat to other primary and secondary and secondary nodes will only send to primary
node every 1 seconds. this value can be changed using the following option.
1. Right Click your HA cluster
2. Goto to advanced options of HA
3
Add the line "das.failuredetectioninterval = 3000" for heart beat to occur every 3 seconds
Changing default VM shutdown timeout:By default, HA waits for 300 seconds for the VM to be shutdown if the isolation response of
the virtual machine is set as "shutdown" before it performs the virtual machine power off. this
value can be changed using the following values.
1. Right Click your HA cluster
8. Remove the affected host from the cluster. Removing ESX host from the cluster will not be
allowed untill that host is put into maintenance mode.
9.Alternative solution for 8 step is, Goto cluster settings and uncheck the vmware HA to
turnoff the HA in that cluster and re-enable the vmware HA to get the agent installed from the
scratch.
10. For further troubleshooting , review the HA logs under /Var/log/vmware/aam directory.
Select the Host which you want it as golden image for your environment
Right Click on the created profile to edit or view the settings captured as part of this host
profile.
We can the see the list of configuration settings for the below items:
Firewall Configuration
Security Configuration
Service Configuration
Advanced configuration information
User configuration
User Group Configuration
Authentication Configuration (AD Domain)
Let's look at each of the configurations policy items one by one.
Memory Reservation Configuration:
This setting captures the service console memory reservation settings of the reference ESX
host and this will not be captured in ESXI host.
Since ESXi host doesn't have a service console and Memory reservation Configuration for
ESXi host in the host profile will contain any captured information.
The Memory Reservation settings of the reference host in the host profile are abstracted from
the memory reservation configuration of the ESX host.Please refer the below snapshot.
Storage configuration
This setting captures the storage (only NFS) configuration of the reference host. It ensures that
NFS configuration of ESX hosts is consistent across the environment by applying this profile.
Compliance Details:
If you have unchecked the "Validate that NFS datastore exists with the following Properties" ,
This particular settings will not be validated as part of compliance check and will not report as
non-complaint when host is not configured with this settings.
The NFS storage settings of the reference host in the host profile are abstracted from the
storage configuration of the ESX host . Please refer the below snapshot.
We can manually define the time zone and NTP servers IP address for the ESX to sync the
time with.
The Date and Time configuration of the reference host in the host profile are abstracted from
the time configuration of the ESX host . Please refer the below snapshot.
Firewall Configuration
This setting captures the firewall configuration of ESX host and ESXi does not include a
firewall because it runs a limited set of well-known services.
Firewall settings contain the rule set configuration which contains the ports or services specific
firewall configuration. So that the destination host will be configured as exactly as same as the
reference host to maintain consistency among the host in your environment.
The firewall settings of the reference host in the host profile are abstracted from the Security
profile Configuration of the ESX host.
Check the Storage I/O Control Enabled check box to enable the Storage I/O Control for that
particular Datastore.
If you want to edit the Congestion Threshold, Click advanced and enter the Value like 10 ms.
Default value is 30 ms
Goto Resources Tab and select Disk. Select the share type (Low, Normal, High & Custom)
which you want to configure for the Virtual machine and click on OK.
Error 1067 unable to start the VMware Virtual center Server Service
Error 1067 unable to start the VMware Virtual center Server Service
I got a call that our Vcenter server is not working. and I felt ohh thats it....let me start the
Vcenter service. I noticed vcenter service was not started and i tried to start the service, it is
throwing the below error.
"Windows Could not start the VMware VirtualCenter service on local computer. Error 1067:
the process terminated unexpectedly"
I wont say the below is the standard to follow to troubleshoot the issue. It was the approach
which i used to resolve the above issue.
Troubleshooting Step 1:
My first place to troubleshoot the Vcenter service failure is "vpxd.log" on the below location
Troubleshooting Step 2:
I have started my investigation into my Vcenter server configuration file "Vpxd.cfg" and the
error messge telling me that Line 33 is culprit so, I started targetting my line towards 30 to 35
in "vpxd.cfg" file.
===========================================================
==============================================================
First, it looks like the culprit is the below line.
Tried to start the service But no luck again failed and the error message in the vpxd log is
different this time
"the Duplicate loop error"
Troubleshhoting Step 3:
Again my target is Vcenter configuration file "Vpxd.cfg"
===========================================================
==============================================================
This time found the issue and the issue is because of the loop # and # appears twice in Vcenter
configuration file.Removed the extra loop and started the service. It started sucessfully and i
am safe.
The issue appeared because of the configuration file of vcenter was edited as part of standard
hardening but edited with the wrong format sometime before and my server was rebooted as
part of patching process.Configuration changes takes effect if you restart the Virtual center
service. After the reboot, My Vcenter server service was not started.
Hey man!!!! wake up.... last friday i was struggled to change the ip address of my collegue's
lab ESX server service console. That struggle leads me to this post. thanks Anil.....
To check the IP address along with the detailed network cards assigned to the esx server:
Ifconfig -a
Output appears like this
===================================================================
=====
lo
Uplinks
PortGroup Name
VLAN ID Used Ports Uplinks
Service Console 2 0
1
vmnic3
Vmotion
0
1
vmnic3
===================================================================
======
From the above output,
we come to know that we have 3 virtual switches named vSwitch0,vSwitch1 and vSwitch2.
4 uplinks (physical nics in our esx server) Vmnic0,vmnic1,vmnic2,vmnic3.
vswitch0 constains 2 port group (Service Console & VMKernel), vSwitch1 contains 2 virtual
machine port group (VM-10.0.0 subnet & VM-192.168.0 subnet) and Vswitch2 contains 2 port
Uplinks
PortGroup Name
VLAN ID Used Ports Uplinks
===================================================================
======
7.To add the new port group named (mgmt)to vswitch (vswitch 3):
[root@ESXTEST1 sbin]# esxcfg-vswitch -A mgmt vswitch3
now port group "mgmt" is added.
===================================================================
======
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vswitch3
64
1
64
1500
PortGroup Name
VLAN ID Used Ports Uplinks
mgmt
0
0
===================================================================
======
8. To add the service console port (vswif2) to our newly created port group "mgmt" with
the ip addr 192.168.0.79
[ OK ]
[ OK ]
[ OK ]
Another way is to conncet to the console of the ESX server and at the shell prompt type in
:esxcfg-vswif -d vswif2
This will delete the existing vswif0 and it will give the message about "nothing to flush".
then type the below command
esxcfg-vswif -a vswif2 -p mgmt -i 192.168.0.97 -n 255.255.255.0
===================================================================
======
[root@ESXTEST1 etc]# esxcfg-vswif -d vswif2
Nothing to flush.
[root@ESXTEST1 etc]# esxcfg-vswif -a vswif2 -p mgmt -i 192.168.0.97 -n 255.255.255.0
[2011-09-17 19:35:46 'Vnic' warning] Generated New MAC address, 00:50:56:43:92:be for
vswif2
Nothing to flush.
===================================================================
======
11. To Edit the hostname and default gateway.
edit the below file:
nano /etc/sysconfig/network
======================================
NETWORKING=yes
HOSTNAME=ESXTEST1.lab.com
GATEWAY=192.168.0.20
GATEWAYDEV=vswif0
IPV6_AUTOCONF=no
NETWORKING_IPV6=no
======================================
restart the network service for ip change to take effect:
[root@ESXTEST1 sysconfig]# service network restart
12.To edit the host file:
nano /etc/hosts