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. 125
Chapter 9 Managing vSphere Networking
Addanewuplinkadaptertoavirtualswitch.
vicfg-vswitch <conn_options> --link vmnic15 vSwitch0
Removeanuplinkadapterfromavirtualswitch.
vicfg-vswitch <conn_options> --unlink vmnic15 vSwitch0
Adding and Modifying VMkernel Network Interfaces
VMkernelnetworkinterfacesareusedprimarilyformanagementtraffic,whichcanincludevMotion,IP
Storage,andothermanagementtrafficontheESXisystem.YoucanalsobindanewlycreatedVMkernel
networkinterfaceforusebysoftwareanddependenthardwareiSCSIbyusingtheesxcli iscsicommands.
TheVMkernelnetworkinterfaceis
separatefromthevirtualmachinenetwork.Theguestoperatingsystem
andapplicationprogramscommunicatewithaVMkernelnetworkinterfacethroughacommonlyavailable
devicedriveroraVMwaredevicedriveroptimizedforthevirtualenvironment.Ineithercase,communication
intheguestoperatingsystemoccursasitwouldwitha
physicaldevice.Virtualmachinescanalso
communicatewithaVMkernelnetworkinterfaceifbothusethesamevirtualswitch.
EachVMkernelnetworkinterfacehasitsownMACaddressandoneormoreIPaddresses,andrespondsto
thestandardEthernetprotocolaswouldaphysicalNIC.TheVMkernelnetworkinterfaceis
createdwithTCP
SegmentationOffload(TSO)enabled.
YoucanmanageVMkernelNICswithESXCLI(see“ManagingVMkernelNetworkInterfaceswithESXCLI”
onpage 125)andwithvicfg-vmknic(see“ManagingVMkernelNetworkInterfaceswithvicfg‐vmknic”on
page 126).
Managing VMkernel Network Interfaces with ESXCLI
YoucanconfiguretheVMkernelnetworkinterfaceforIPv4(see“ToaddandconfigureanIPv4VMkernel
NetworkInterfaceforIPv4”onpage 125)orforIPv6(see“ToaddandconfigureaVMkernelNetwork
InterfaceforIPv6”onpage 126)withESXCLI.Incontrasttovicfg-vmknic,ESXCLIdoesnotsupport
enabling
vMotion.
YoucanaddandconfigureanIPv4VMkernelNICwithESXCLI.Specifyoneoftheoptionslistedin
“ConnectionOptionsforvCLIHostManagementCommands”onpage 18inplaceof<conn_options>.
To add and configure an IPv4 VMkernel Network Interface for IPv4
1AddanewVMkernelnetworkinterface.
esxcli <conn_options> network ip interface add --interface-name=vmk<x>
--portgroup-name=<my_portgroup>
YoucanspecifytheMTUsettingafteryouhaveaddedthenetworkinterfacebyusingesxcli network
ip interface set --mtu.
2ConfiguretheinterfaceasanIPv4interface.YoumustspecifytheIPaddressusing--ip,thenetmask,and
thename.Forthefollowingexamples,assumethatVMSF‐VMK‐363isaportgroup
towhichyouwantto
addaVMkernelnetworkinterface.
esxcli <conn_options> network ip interface ipv4 set --ipv4=<ip_address>
--netmask=255.255.255.0 --interface-name=vmk<X>
Youcansettheaddressasfollows.
<X.X.X.X>–StaticIPv4address.
DHCP–UseIPv4DHCP.
TheVMkernelsupportsDHCPonlyforESXi4.0andlater.
Whenthecommandfinishessuccessfully,thenewlyaddedVMkernelnetworkinterfaceisenabled.
3ListinformationaboutallVMkernelnetworkinterfacesonthesystem.
esxcli <conn_options> network ip interface list