Here I am going to give you the difference between the ESX & ESXI points wise based on the clasifications.
Service Console
ESX:- Service Console is a standard Linux environment through which a user has privileged access to the VMware ESX kernel. This Linux-based privileged access allows you to highly customize your environment by installing agents and drivers and executing scripts and other Linux-environment code.
ESXI:-VMware ESXi is designed to make the server a computing appliance. Accordingly, VMware ESXi behaves more like firmware than traditional software. To provide hardware-like security and reliability, VMware ESXi does not support a privileged access environment like the Service Console of VMware ESX. To enable interaction with agents, VMware has provisioned CIM Providers through which monitoring and management tasks – traditionally done through Service Console agents – can be performed. VMware has provisioned RCLI to allow the execution of scripts.
Remote CLI
ESX:- VMware ESX Service Console has a host CLI through which VMware ESX can be configured. ESX 3.5 Update 2 supports RCLI.
ESXI:-VMware ESX Service Console CLI has been ported to a Remote CLI (RCLI) for VMware ESXi. RCLI is a virtual appliance that interacts with VMware ESXi hosts to enable host configuration through scripts or specific commands.
Note:
•RCLI is limited to read-only access for the free version of VMware ESXi. To enable full functionality of RCLI on a VMware ESXi host, the host must be licensed with VI Foundation, VI Standard, or VI Enterprise.
•The VMware Infrastructure toolkit for Windows and the Perl toolkit access ESXi through the same API as RCLI. Similarly, these toolkits are limited to read-only access for the free version of VMware ESXi. When the host is upgraded to VI Foundation, VI Standard, or VI Enterprise, these toolkits have write-access and provide a scriptable method for managing ESXi hosts.
•The following Service Console CLI commands have not been implemented in
RCLI:
◦ESXcfg-info
◦ESXcfg-resgrp
◦ESXcfg-swiscsi
Scriptable Installation
ESX:- VMware ESX supports scriptable installations through utilities like KickStart.
ESXI:- VMware ESXi Installable does not support scriptable installations in the manner ESX does, at this time. VMware ESXi does provide support for post installation configuration script using RCLI-based configuration scripts.
Boot from SAN
ESX:- VMware ESX supports boot from SAN. Booting from SAN requires one dedicated LUN per server.
ESXI:- VMware ESXi may be deployed as an embedded hypervisor or installed on a hard disk.
In most enterprise settings, VMware ESXi is deployed as an embedded hypervisor directly on the server. This operational model does not require any local storage and no SAN booting is required because the hypervisor image is directly on the server.
The installable version of VMware ESXi does not support booting from SAN.
Serial Cable Connectivity
ESX:- VMware ESX supports interaction through direct-attached serial cable to the VMware ESX host.
ESXI:- VMware ESXi does not support interaction through direct-attached serial cable to the VMware ESXi host at this time.
SNMP
ESX:- VMware ESX supports SNMP.
ESXI:- VMware ESXi supports SNMP when licensed to a VI Foundation, VI Standard, or VI Enterprise edition. The free version of VMware ESXi does not support SNMP.
Active Directory Integration
ESX:- VMware ESX supports Active Directory integration through third-party agents installed on the Service Console.
ESXI:- VMware ESXi with a Virtual Infrastructure license and in conjunction with VirtualCenter allows users to be authenticated via Active Directory. In this configuration, users can log in directly to an ESXi host and authenticate using a local username and password.
The free version of VMware ESXi does not support Active Directory integration at this time.
HW Instrumentation
ESX:- Service Console agents provide a range of HW instrumentation on VMware ESX.
ESXI:- VMware ESXi provides HW instrumentation through CIM Providers. Standards-based CIM Providers are distributed with all versions of VMware ESXi. VMware partners may inject their own proprietary CIM Providers in customized versions of VMware ESXi. To obtain a customized version of VMware ESXi, you typically have to purchase a server with embedded VMware ESXi through a server vendor.
At this time, HP also offers its customized VMware ESXi Installable on http://www.vmware.com/. Dell, IBM, and FSC will soon offer their customized version of VMware ESXi on http://www.vmware.com/.
Remote console applications like Dell DRAC, HP iLO, IBM RSA, and FSC iRMC S2 are supported with ESXi.
Note: COS agents have a longer lineage than CIM Providers and are therefore more mature. VMware is actively working with its 250+ partners to close the CIM Provider–Service Console agent gap.
Software Patches and Updates
ESX:- VMware ESX software patches and upgrades behave like traditional Linux based patches and upgrades. The installation of a software patch or upgrade may require multiple system boots as the patch or upgrade may have dependencies on previous patches or upgrades.
ESXI:- VMware ESXi patches and updates behave like firmware patches and updates. Any given patch or update is all-inclusive of previous patches and updates. That is, installing patch version “n” includes all updates included in patch versions n-1, n-2, and so forth.
Licensing
ESX:- VMware ESX hosts can be licensed as part of a VMware Infrastructure 3 Foundation, Standard, or Enterprise suite.
ESXI:- VMware ESXi hosts can be individually licensed (for free) or licensed as part of a VMware Infrastructure 3 Foundation, Standard, or Enterprise suite.
Individually licensed ESXi hosts offer a subset of management capabilities (see SNMP and Remote CLI).
Jumbo Frames
ESX:- iSCSI with Jumbo Frames is not supported.
ESXI:- Jumbo Frames are not supported for VMkernel networking interfaces in ESXi 3.x. In ESXi 3.5, Jumbo Frames are only supported on non-VMkernel network interfaces. For more information, see Enabling Jumbo Frames of the ESXi Server Configuration Guide.
Saturday, March 5, 2011
Friday, March 4, 2011
Freeing disk space on an ESX host
To Free up your ESX server, first you should know what files are stored in different locations.
•The /vmimages folder. This folder is used to store operating system install files such as the VMware Tools or other ISO files.
•The /var/core folder. This folder is used to store crash files for processes on the service console.
•The /var/log folder. This folder stores the majority of the logs for the ESX host.
•Any VMFS volume. These are used to store the virtual machine data.
Run the following command to check which files are using more space on the Disk:
[root@server]# find / -size +10240000c -exec du -h {} \; | less
The following are a list of files that can be deleted from the ESX server
•Old vm-support logs
•Virtual machines that are not being used and are not needed
•ISO files that were copied to the system
•The /vmimages folder. This folder is used to store operating system install files such as the VMware Tools or other ISO files.
•The /var/core folder. This folder is used to store crash files for processes on the service console.
•The /var/log folder. This folder stores the majority of the logs for the ESX host.
•Any VMFS volume. These are used to store the virtual machine data.
Run the following command to check which files are using more space on the Disk:
[root@server]# find / -size +10240000c -exec du -h {} \; | less
The following are a list of files that can be deleted from the ESX server
•Old vm-support logs
•Virtual machines that are not being used and are not needed
•ISO files that were copied to the system
How to Check Disk space usage on the ESX
To check the free space on an ESX service console partitions:
1.Log in to the ESX service console as root from either an SSH session or directly from the console of the host.
2.Type df -h.
The output appears similar to:
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 4.9G 3.0G 1.6G 66% /
/dev/sda1 99M 18M 77M 19% /boot
none 145M 0 145M 0% /dev/shm
/dev/sda7 2.0G 135M 1.7G 8% /var/log
[root@server]#
************************************************************
To check the free space on a VMFS volume of an ESX host:
1.Log in to the ESX service console as root from either an SSH session or directly from the console of the host.
2.Type vdf -h.
The output appears similar to:
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 4.9G 3.0G 1.6G 66% /
/dev/sda1 99M 18M 77M 19% /boot
none 145M 0 145M 0% /dev/shm
/dev/sda7 2.0G 135M 1.7G 8% /var/log
/vmfs/devices 439G 0 439G 0% /vmfs/devices
/vmfs/volumes/458865ba-b31110fd-43d5-00127994e616
68G 47G 20G 69% /vmfs/volumes/San_Storage
/vmfs/volumes/45b5eb1a-808343db-ecab-00114335854b
26G 9.7G 16G 36% /vmfs/volumes/Local_Storage
[root@server]#
************************************************************************
Command to show the largest files with the Directories
[root@server]#du -h --max-depth=1 "dir"
This command lists the directories within a given filesystem that contain the largest files.
1.Log in to the ESX service console as root from either an SSH session or directly from the console of the host.
2.Type df -h.
The output appears similar to:
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 4.9G 3.0G 1.6G 66% /
/dev/sda1 99M 18M 77M 19% /boot
none 145M 0 145M 0% /dev/shm
/dev/sda7 2.0G 135M 1.7G 8% /var/log
[root@server]#
************************************************************
To check the free space on a VMFS volume of an ESX host:
1.Log in to the ESX service console as root from either an SSH session or directly from the console of the host.
2.Type vdf -h.
The output appears similar to:
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 4.9G 3.0G 1.6G 66% /
/dev/sda1 99M 18M 77M 19% /boot
none 145M 0 145M 0% /dev/shm
/dev/sda7 2.0G 135M 1.7G 8% /var/log
/vmfs/devices 439G 0 439G 0% /vmfs/devices
/vmfs/volumes/458865ba-b31110fd-43d5-00127994e616
68G 47G 20G 69% /vmfs/volumes/San_Storage
/vmfs/volumes/45b5eb1a-808343db-ecab-00114335854b
26G 9.7G 16G 36% /vmfs/volumes/Local_Storage
[root@server]#
************************************************************************
Command to show the largest files with the Directories
[root@server]#du -h --max-depth=1 "dir"
This command lists the directories within a given filesystem that contain the largest files.
Subscribe to:
Posts (Atom)