6.0
Table Of Contents
- vSphere Command-Line Interface Concepts and Examples
- Contents
- About This Book
- vSphere CLI Command Overviews
- Introduction
- List of Available Host Management Commands
- Targets and Protocols for vCLI Host Management Commands
- Supported Platforms for vCLI Commands
- Commands with an esxcfg Prefix
- ESXCLI Overview
- Connection Options for vCLI Host Management Commands
- Connection Options for DCLI Commands
- vCLI Host Management Commands and Lockdown Mode
- Managing Hosts
- Managing Files
- Managing Storage
- Introduction to Storage
- Examining LUNs
- Detaching Devices and Removing a LUN
- Working with Permanent Device Loss
- Managing Paths
- Managing Path Policies
- Scheduling Queues for Virtual Machine I/O
- Managing NFS/NAS Datastores
- Monitoring and Managing SAN Storage
- Monitoring and Managing Virtual SAN Storage
- Monitoring vSphere Flash Read Cache
- Monitoring and Managing Virtual Volumes
- Migrating Virtual Machines with svmotion
- Configuring FCoE Adapters
- Scanning Storage Adapters
- Retrieving SMART Information
- Managing iSCSI Storage
- iSCSI Storage Overview
- Protecting an iSCSI SAN
- Command Syntax for esxcli iscsi and vicfg-iscsi
- iSCSI Storage Setup with ESXCLI
- iSCSI Storage Setup with vicfg-iscsi
- Listing and Setting iSCSI Options
- Listing and Setting iSCSI Parameters
- Enabling iSCSI Authentication
- Setting Up Ports for iSCSI Multipathing
- Managing iSCSI Sessions
- Managing Third-Party Storage Arrays
- Managing NMP with esxcli storage nmp
- Path Claiming with esxcli storage core claiming
- Managing Claim Rules
- Managing Users
- Managing Virtual Machines
- vmware-cmd Overview
- Listing and Registering Virtual Machines
- Retrieving Virtual Machine Attributes
- Managing Virtual Machine Snapshots with vmware-cmd
- Powering Virtual Machines On and Off
- Connecting and Disconnecting Virtual Devices
- Working with the AnswerVM API
- Forcibly Stopping Virtual Machines with EXCLI
- Managing vSphere Networking
- Introduction to vSphere Networking
- Retrieving Basic Networking Information
- Network Troubleshooting
- Setting Up vSphere Networking with vSphere Standard Switches
- Setting Up Virtual Switches and Associating a Switch with a Network Interface
- Retrieving Information About Virtual Switches
- Adding and Deleting Virtual Switches
- Checking, Adding, and Removing Port Groups
- Managing Uplinks and Port Groups
- Setting the Port Group VLAN ID
- Managing Uplink Adapters
- Adding and Modifying VMkernel Network Interfaces
- Setting Up vSphere Networking with vSphere Distributed Switch
- Managing Standard Networking Services in the vSphere Environment
- Setting the DNS Configuration
- Adding and Starting an NTP Server
- Managing the IP Gateway
- Setting Up IPsec
- Managing the ESXi Firewall
- Monitoring VXLAN
- Monitoring ESXi Hosts
- Index
VMware, Inc. 57
Chapter 4 Managing Storage
Running svmotion in Noninteractive Mode
Innoninteractivemode,thesvmotioncommandusesthefollowingsyntax:
svmotion [standard vCLI options] --datacenter=<datacenter_name>
--vm <VM config datastore path>:<new datastore>
[--disks <virtual disk datastore path>:<new datastore>,
<virtual disk datastore path>:<new datastore>]
Squarebracketsindicateoptionalelements,notdatastores.
The--vmoptionspecifiesthevirtualmachineanditsdestination.Bydefault,allvirtualdisksarerelocatedto
thesamedatastoreasthevirtualmachine.Thisoptionrequiresthecurrentvirtualmachineconfigurationfile
location.See“Todeterminethepathtothevirtualmachineconfigurationfileanddiskfile”onpage 57.
The
--disksoptionrelocatesindividualvirtualdiskstodifferentdatastores.The--disksoptionrequiresthe
currentvirtualdiskdatastorepathasanoption.See“Todeterminethepathtothevirtualmachine
configurationfileanddiskfile”onpage 57.
To determine the path to the virtual machine configuration file and disk file
1Runvmware-cmd -ltolistallvirtualmachineconfigurationfiles(VMXfiles).
vmware-cmd -H <vc_server> -U <login_user> -P <login_password> -h <esx_host> -l
2 ChoosetheVMXfileforthevirtualmachineofinterest.
Bydefault,thevirtualdiskfilehasthesamenameastheVMXfilebuthasa.vmdkextension.
3 (Optional)UsevifstoverifythatyouareusingthecorrectVMDKfile.
To relocate a virtual machine’s storage (including disks)
1 Determinethepathtothevirtualmachineconfigurationfile.
2Runsvmotion:
svmotion
--url=https://myvc.mycorp.com/sdk --datacenter=DC1
--vm=”[storage1] myvm/myvm.vmx:new_datastore”
TheexampleisforWindows.UsesinglequotesonLinux.
To relocate a virtual machine’s configuration file, but leave virtual disks
1 Determinethepathtothevirtualdiskfilesandthevirtualmachineconfigurationfile.
2Runsvmotion,forexample:
svmotion
<conn_options>
--datacenter='My DC'
--vm='[old_datastore] myvm/myvm.vmx:new_datastore'
--disks='[old_datastore] myvm/myvm_1.vmdk:old_datastore, [old_datastore] myvm/myvm_2.vmdk:
old_datastore'
Thiscommandrelocatesthevirtualmachineʹsconfigurationfiletonew_datastore,butleavesthetwodisks
(myvm_1.vmdkandmyvm_2.vmdk)inold_datastore.TheexampleisforLinux.Usedoublequoteson
Windows.Thesquarebracketssurroundthedatastorenameanddonotindicateanoptionalelement.
Configuring FCoE Adapters
ESXicanuseFibreChanneloverEthernet(FCoE)adapterstoaccessFibreChannelstorage.
TheFCoEprotocolencapsulatesFibreChannelframesintoEthernetframes.Asaresult,yourhostdoesnot
needspecialFibreChannellinkstoconnecttoFibreChannelstorage,butcanuse10GbitlosslessEthernetto
deliver
FibreChanneltraffic.
I
MPORTANTWhenyourunsvmotion,--servermustpointtoavCenterServersystem.