VI3 Command Line Changes Jeremy van Doorn Systems Engineer Danny Claproth Channel Systems Engineer

Agenda Major differences compared to ESX2 Commands & configuration file changes Network changes Proc filesystem Security Troubleshooting

Major differences compared to ESX2 Service console I/O more like a virtual machine –Virtual I/O devices for the service console –All storage and network devices dedicated to the VMkernel –Easier install: no more dividing physical devices between virtual machines and the service console

Major differences compared to ESX2 Red Hat Enterprise Linux 3 Follow security updates from Red Hat Better compatibility with 3 rd party agents and software Service console resource needs independent of the number of virtual machines Most vmx processes moved from service console to VMkernel Service Console not a scalability bottleneck More accurate virtual machine resource accounting ESX host management vmware-serverd has disappeared vmware-hostd now does all the work together with vmware-vpxa

New Command-line utilities esxcfg-initPerform initialization steps in the initrd. NOT TO BE RUN MANUALLY! esxcfg-authAuthentication configuration esxcfg-advcfgSets advanced VMkernel options esxcfg-mpathMultipathing configuration esxcfg-resgrpCreate, delete and list resource groups esxcfg-rescanRescan LUNs on SCSI device esxcfg-vswitchCreate and configure virtual switches and port groups esxcfg-vswifCreate and configure vswifs for the COS esxcfg-vmknicCreate and configure VMkernel nics esxcfg-routeChange default gateway for vmknics esxcfg-nasAdd, delete or manage NAS file systems esxcfg-dumppartSet, activate, deactivate, list potential and current VMkernel dump partitions esxcfg-bootConfigure boot, including PCI allocation esxcfg-firewallConfigure Firewalling options.

Demo Screen some esxcfg commands

Configuration files changes The /etc/vmware/esx.conf file is the new master configuration file for ESX Server Old FileNew fileNotes hwconfigesx.conf devnames.confNo longer necessary, was duplicated in hwconfig now in esx.conf vmkmodule.confesx.confKeys start with /vmkmodule netmap.confesx.confSee the prettyName entry for each portgroup vmkconfigesx.confKeys start with /adv Use the esxcfg-* tools, Virtual Center, or Virtual Infrastructure Client to configure ESX!

Demo Screen /etc/vmware/esx.conf

Commands Changes Removed or replaced scripts vmkpcidivy vmkbootcfg  esxcfg-boot vmsnap.pl  vcbMounter Vmsnap_all  vcbSnapAll vmware-cmd –Added multiple snapshots

Networking Only the new ESX style networking is available. –All networking (COS vswifs, VM virtual nics, VMkernel networking clients) will connect to the system through port groups on a virtual switch –Physical network devices will still get names in the form vmnicN, these names will no longer appear in VM configuration files (.vmx files). Instead, virtual nics are currently connected to the port group's ID –Virtual switches are connected to the pNics –Bond devices no longer exist. Nic teaming/bonding is accomplished by attaching multiple pNics to a single virtual switch –esxcfg-* programs are used for persistent command-line configuration esxcfg-vswitch esxcfg-vswif

Demo Screen esxcfg-vswitch esxcfg-vswif esxcfg-vmknic

/proc /proc/vmware –Still here, but with some changes /proc/vmware/net /proc/vmware/swap /proc/vmware/vm

Demo Screen /proc

Security Service Console Security Level –High, medium, and low # esxcfg-firewall –q incoming # esxcfg-firewall –q outgoing Use esxcfg-firewall to set level of security LOW  # esxcfg-firewall --allowIncoming –-allowOutgoing MEDIUM  # esxcfg-firewall –-blockIncoming --allowOutgoing HIGH  # esxcfg-firewall --blockIncoming –blockOutgoing SSH –SSH root login not permitted by default

Demo Screen esxcfg-firewall

Troubleshouting Logfiles /var/log/messages VMkernel log Use the esxcfg-* tools /proc filesystem Alt-f12 Have a good look at the output of vm-support ESX3 still has Service Console only mode –Can’t use esxcfg-* tools in this mode

Demo Screen vmkernel logfile

Questions?