Troubleshooting Web in Ar 60

Introduction to Troubleshooting Webinar
vSphere 6.0
2015 VMware Inc. All rights reserved
Webinar Overview
This Webinar will discuss:
Use of the VMware vSphere Web Client, the command line, and log
files to diagnose and correct problems in vSphere
Troubleshooting networking issues
Troubleshooting storage issues
Troubleshooting VMware vCenter Server issues
Troubleshooting VMware ESXi host issues
Troubleshooting vSphere HA cluster issues
Troubleshooting VMware vSphere vMotion issues
VMware vSphere: Troubleshooting Webinar 6.0
2
2015 Vmware Inc. All rights reserved
Webinar Scope
This Webinar covers portions of the Troubleshooting Workshop:
For more information, go to http://vmware.com/education
3
Troubleshooting Overview
4
Definition of a System Problem

A system problem is a fault in a system, or one of its components,
that negatively affects the services needed for normal production.
Problems can arise from numerous sources, which include:
Configuration issues
Resource contention
Network attacks
Software bugs
Hardware failures
This webinar addresses problems caused by configuration and

operational issues.
5
Effect of a System Problem

These problems can affect certain aspects of a system:
Usability
Accuracy
Reliability
Performance
These perceived effects, or symptoms, are what is generally exposed
and reported.
Although performance is a predominant symptom in reported
problems, this webinar does not focus on problems that cause
performance issues.
Performance troubleshooting is covered in the VMware vSphere:

Optimize and Scale course.
6
Troubleshooting Process
Troubleshooting involves the systematic approach to identifying the
problem (root cause) from the reported symptom.
The troubleshooting process consists of the following tasks:
Defining the problem
Identifying symptoms
Gathering information
Identifying the cause of the problem
Identifying possible causes

Determining the root cause
Resolving the problem
Identifying possible solutions

Implementing the best solution
7
Gathering Information About the Problem

Reproduce the problem.
This provides a repeatable means to verify the problem as well as a
way to validate that the problem was resolved.
Identify the scope of the problem:
Does the problem affect only one object, or multiple objects?
Gather additional information:
Was the task working before?
If so, what changed in your environment or configuration?
Consult references, such as product release notes, to determine

whether the problem is a known problem.
Use your existing knowledge of your systems configuration to help

you determine the cause of the problem.
8
Viewing and Interpreting Diagnostic Information

View diagnostic
messages
displayed in the
GUI or written to
log files.
Example: Error powering on a virtual machine
Interpret the
diagnostic
messages to
focus your
troubleshooting
efforts.
9
Identifying Possible Causes

A structured approach to troubleshooting enables you to determine
the root cause quickly and effectively.
Based on the problems
characteristics, take one
of the following
troubleshooting
approaches:
Investigate cause top-down
Investigate cause bottom-up
top-down
application/
guest OS
virtual
machine
Approach cause by halves
Approach
the cause by
halves.
ESXi
host
hardware
(CPU, memory,
network, storage)
bottom-up
10
Resolving the Problem

After identifying the root cause, assess the impact of the problem on
operations:
High impact Resolve immediately
Medium impact Resolve when possible
Low impact Resolve during next maintenance window
Identify possible solutions to resolve the problem.
Short-term solution Workaround
Long-term solution Reconfiguration
Impact analysis Assess the impact of the solution on operations.
Implement the solution.
11
Example: Defining the Problem
VMware vSphere vMotion migration fails with an error.
Scenario:
You attempt to migrate the virtual machine named VM01 from the host
named esxi01 to the host named esxi02. After waiting a couple of
minutes, the vSphere vMotion migration fails with an error.
Is this a vSphere vMotion problem or a symptom of an underlying
problem?
The error message is the starting point.
12
Example: Gathering Information

Error messages can help determine the problem.
13
Example: Identifying Possible Causes

Use the information you gathered to identify possible causes:
Based on error messages, the vSphere vMotion migration failed
because esxi01 and esxi02 failed to connect over the network named
vMotion.
This error points you to a possible
misconfiguration on the ESXi
application or
host.
guest OS
Possible Causes
virtual
machine
vMotion is misconfigured.
Network connectivity is down
ESXi
host
on one of the ESXi hosts.
vMotion VMkernel interface connectivity

is down on one of the ESXi hosts.
hardware
(CPU, memory,
network, storage)
14
Example: Determining the Root Cause

Start here:
ping esxi02
ping 172.20.13.52
Yes
Success?
Success?
No
Test next
possible
cause.
No
Fix network configuration

to get a successful ping.
Fix VMkernel configuration

to get a successful ping.
Perform vMotion
migration.
Perform vMotion
migration.
No
Success?
Success?
Yes
Further
investigation
necessary.
Yes
Root cause
identified.
No
Yes
15
Example: Resolving the Problem

In this example, suppose that the root cause was an incorrect IP
address for the vSphere vMotion VMkernel interface on esxi02.
Assess the impact of the problem on operations.
Probably high impact
The problem affects any virtual machine that is migrated to esxi02.

The problem also affects the proper operation of VMware vSphere
Distributed Resource Scheduler.
Identify possible solutions to resolve the problem.

Short-term accommodation Do not migrate virtual machines to
esxi02.
Long-term solution Fix the IP address of esxi02s vMotion VMkernel
interface.
Implementing the solution should not require downtime.
16
Commandline Troubleshooting Tools
17
Commandline Troubleshooting Tools

Ways to obtain command-line access on a VMware ESXi host:
VMware vSphere ESXi Shell, which includes:
ESXCLI commands
A set of esxcfg-* commands
A set of commands for troubleshooting
vSphere Management Assistant
Includes the VMware vSphere Command-Line Interface (vCLI) package
18
vSphere ESXi Shell

vSphere ESXi Shell can be accessed:
Locally, from the direct console user interface (DCUI)
Remotely, from an SSH session
To access the local vSphere ESXi Shell:
Enable the local vSphere ESXi Shell from the DCUI or from the
VMware vSphere Web Client.
Access vSphere ESXi Shell from the main DCUI screen by pressing
Alt+F1 to open a console window to the host.
To access the remote vSphere ESXi Shell:

Enable the vSphere ESXi Shell and SSH services.
Use an SSH client, such as PuTTY, to access vSphere ESXi Shell.
Disable the SSH service when you are no longer using it.
19
vSphere Management Assistant

vSphere Management Assistant is a virtual appliance that includes
the following:
vCLI command set
vi-fastpass authentication component
Enables you to run system administration commands to manage ESXi

hosts, such as:
Requires credential connection options to a server
Automates authentication to VMware vCenter Server system or ESXi
host targets
Prevents the user from having to continually add login credentials to every
command being executed
Reference:
https://www.vmware.com/support/developer/vcli/vcli60/vsp6_60_vcli_rel
notes.html
20
ESXCLI Command
The esxcli command offers the following namespaces, as well as
many new esxcli commands added in the vSphere 6.0 release.
21
Example: Viewing vSphere Network Information

esxcli network
Physical and virtual network information can be displayed by using

esxcli network commands.
22
Example: Viewing Standard Switch Information

esxcli network vswitch standard
Standard switches can be created by using the esxcli network

vswitch standard command structure.
23
vicfg-* Commands
vicfg-*
Commands with the vicfg- prefix enable you to manage your

storage, network, and host configuration.
For example, to display IP information of your VMkernel interfaces:
vicfg-vmknic -l
24
vmware-cmd Command
vmware-cmd
The vmware-cmd command is exclusively used for virtual machines.
25
Example: Viewing Virtual Machine Information

vmware-cmd -l
Lists the virtual machines that are located on the target host. Lists
virtual machines by path to the .vmx file.
26
Useful ESXi Host Logs for Troubleshooting

ESXi hosts write to multiple log files, depending on which action is
being performed.
Log file
Purpose
hostd.log
Host Management service logs
syslog.log
Management service initialization, watchdogs,

scheduled tasks, and DCUI use
vmkernel.log
Core VMkernel logs, including device discovery,

storage and networking device and driver events,
and virtual machine startups
vmkwarning.log
A summary of warning and alert log messages

excerpted from the VMKernel logs
vmksummary.log
A summary of ESXi host startup and shutdown, and

an hourly heartbeat with uptime, number of virtual
machines running, and service resource
consumption
27
Viewing Log Files by Using the vSphere Web Client

The vSphere Web Client can be used to view and search log files on
vCenter Server systems and ESXi hosts.
28
Improved Audit Trail of ESXi Administrative Tasks

In vSphere 5, ESXi hosts log actions by named VMware vCenter
Server users as vpxuser.
In vSphere 6, ESXi hosts log actions by named vCenter Server users

as the correct user name.
29
Viewing Log Files by Using the DCUI

The Direct Console User Interface (DCUI) can be used if vCenter
Server is not available.
With the DCUI, only the log files for a single ESXi host can be viewed.
30
Collecting Diagnostic Data for VMware Technical Support

Methods for collecting diagnostic information to send to VMware
Technical Support include the following:
Use the GUI to export files to a log bundle.
vSphere Client or vSphere Web Client
Use the vm-support command to collect information from an

individual ESXi host.
31
Network Troubleshooting
32
Networking Overview
In vSphere, networking problems can occur with various types of
connectivity:
Virtual switch connectivity
Standard switches
Distributed switches
Virtual machine network connectivity

VMware ESXi host management network connectivity
33
Example: Network Issue

The ESXi host has intermittent or no network connectivity to other
systems.
Initial check:
From the ESXi local console, ping a system that is known to be up and
accessible by the ESXi host.
command
prompt at
the DCUI
34

If you know that your hardware is functioning correctly, take the topdown approach to troubleshooting, starting with the ESXi host
configuration.
Possible Causes
The ESXi host network configuration is incorrect.
The VLAN ID of the port group is incorrect.
ESXi
host
The speed and duplex of the network links are not

consistent.
The network link is down.
NIC teaming is not configured properly.
hardware
(network, server)
The network adapter or server hardware is not supported.

The physical hardware is faulty or misconfigured.
Network performance is slow.
35
Host Networking Rollback

Rollback enables you to roll back to a previous valid configuration.
One type of rollback is the host networking rollback.
Triggered when a network configuration change is made that

disconnects the host
Examples of events that might trigger a host networking rollback:

Updating DNS and routing settings
Updating the speed or duplex of a physical NIC
Changing the IP settings of a management VMkernel network adapter
Updating teaming and failover policies to a port group that contains the
management VMkernel network adapter
If a network disconnects for any of these reasons, the task fails and
the host reverts to the last valid configuration.
36
Distributed Switch Rollback

The other type of rollback is the distributed switch rollback.
Triggered when invalid updates are made to distributed switch-related
objects
Examples of events that might trigger a distributed switch rollback:
Changing the MTU of a distributed switch
Changing the following settings in the distributed port group of the
management VMkernel network adapter:
NIC teaming and failover

VLAN
Traffic shaping
If an invalid configuration occurs, one or more hosts might be out of

synchronization with the distributed switch.
37
Recovering from a Distributed Switch Misconfiguration

Always back up your distributed switch after you make a change to
its configuration.
If your distributed switch loses network connectivity because of a
misconfiguration, you can restore from your latest backup.
The vSphere Web Client provides you with the following features:
Export Back up your distributed switch configuration.
Restore Reset the configuration of an existing distributed switch from
an exported configuration file.
Import Create a new distributed switch from an exported configuration
file.
The export, restore, and import functions are available with the
vSphere Web Client.
38
Backing Up a Distributed Switch Configuration

You can back up a distributed switch configuration by exporting the
configuration to a file.
Exporting enables you to do the following tasks:
Make a backup of your distributed switch configuration.
Create a template of a distributed switch configuration.

Create a revision control system for your distributed switch
configuration.
39
Restoring and Importing a Distributed Switch Configuration

After you export a distributed switch configuration, you can perform
the following functions:
Restore resets the configuration of an existing distributed switch from
an exported configuration file.
Import creates a new distributed switch from an exported configuration
file.
You can use restore to reset a distributed switch configuration that
has become corrupted.
You can use import to create a new distributed switch, for example,
on a different vCenter Server system.
40
Storage Troubleshooting
41
Example: Storage Issue

IP storage is not reachable by an ESXi host.
Initial checks:
Verify that the ESXi host can see the LUN.
esxcli storage core path list
Check whether a rescan restores visibility to the LUNs.
esxcli storage core adapter rescan A <vmhba##>
42

If the ESXi host accessed IP storage in the past, and no recent
changes have been made to the host configuration, you might take a
bottom-up approach to troubleshooting.
Possible Causes
The VMkernel interface for IP storage is misconfigured.
IP storage is not configured correctly on the ESXi host.
ESXi
host
iSCSI TCP port 3260 is unreachable.

A firewall is interfering with iSCSI traffic.
NFS storage is not configured correctly.

VMFS datastore metadata is inconsistent.
The iSCSI storage array is not supported.
hardware:
storage network,
storage array
The LUN is not presented to the ESXi host.
The physical hardware is not functioning correctly.

Poor iSCSI storage performance is observed.
43
Example: Storage Issue
One or more paths to a LUN are lost.

Initial checks:
Find detailed information regarding LUN paths:
esxcli storage core path list
List LUN multipathing information:
esxcli storage nmp device list
Check whether a rescan restores visibility to the LUNs.
esxcli storage core adapter rescan A <vmhba##>
44

If you see errors in /var/log/vmkernel.log that refer to a
permanent device loss (PDL) or all paths down (APD) condition, then
take a bottom-up approach to troubleshooting.
Possible Causes
ESXi
host
hardware:
storage network,
storage array
For iSCSI storage, NIC teaming is misconfigured.

The path selection policy for a storage device is
misconfigured.
A PDL condition has occurred.
An APD condition has occurred.
45
Retrieving SMART Data

vSphere 6 includes the esxcli storage core device smart get
d device_name command to retrieve data about a specified SSD
device.
46
Possible Cause: NFS Misconfiguration

If your virtual machines reside on NFS datastores, verify that your
NFS configuration is correct.
directory to share
with the ESXi host
over the network
NFS server name or

IP address
mount permission
(read/write or read
only) and ACLs
ESXi host with NIC

mapped to virtual
switch
VMkernel port
configured with
IP address
47
NFS Version Compatibility

Compatibility with other vSphere technologies
vSphere Technologies
NFS v3
NFS v4.1
vSphere vMotion/vSphere Storage vMotion
Yes
Yes
vSphere HA
Yes
Yes
vSphere Fault Tolerance
Yes
Yes
vSphere DRS/vSphere DPM
Yes
Yes
Stateless ESXi/Host Profiles
Yes
Yes
vSphere Storage DRS/vSphere Storage I/O

Control
Yes
No
Site Recovery Manager
Yes
No
Virtual Volumes
Yes
No
48
NFS Dual Stack Not Supported

NFS v3 and v4.1 use different locking semantics:
NFS v3 uses proprietary client-side cooperative locking. NFS v4.1 uses
server-side locking
Best practice:
Configure an NFS array to allow only one NFS protocol.
Use either NFS v3 or NFS v4.1 to mount the same NFS share across
all VMware ESXi hosts.
Data corruption can occur if hosts attempt to access the same NFS share
using different NFS client versions.
49
Reviewing Session Information

The esxcli storage nfs41 list command is used to list and
view the volume name, IP address, and other information for the
export.
50
Cluster Troubleshooting
51
vSphere HA
A reliable network connection between the hosts and VMware
vCenter Server is essential for enabling vSphere HA.
Heartbeat
datastores
FDM
vpxa
FDM
FDM
hostd
ESXi host (slave)
vpxa
hostd
ESXi host (slave)
vpxa
hostd
ESXi host (master)

management
network
vCenter
Server
vpxd
52
Example: vSphere HA Issue

The vCenter Server displays the following error:
Insufficient failover capacity in a vSphere HA cluster.
The issue might also occur if you attempt to power-on a virtual
machine that is part of a vSphere HA cluster with insufficient failover
resources.
53

Excessive virtual machine reservations or insufficient resources in
the cluster can cause insufficient failover capacity for vSphere HA.
Possible Causes
vSphere HA
vSphere HA admission control policy is not configured

correctly.
virtual
machine
One or more of the virtual machines have excessive

reservations.
ESXi
host
The cluster has insufficient physical resources.
54
vSphere HA
When a host failure or isolation occurs, vSphere HA powers on a
virtual machine on another host in the cluster with respect to the
bandwidth reservation and teaming policy:
Failover:
vSphere HA respects the virtual machines reservation.
vSphere HA failure:
If a virtual machine cannot start because the bandwidth reservation cannot

be met, information about the failure is available in the UI and log files.
NIOCES.etherswitch: NIOCES_UpdateNIOCVnicInfo: Fail to

reserve bandwidth for the port
55
vSphere HA and VMCP

vSphere 5.x is unable to detect ADP conditions and remediate PDL
conditions.
(Inactive)
(Inaccessible)
In vSphere 6, vSphere HA includes Virtual Machine Component

Protection (VMCP):
VMCP provides enhanced protection from APD and PDL conditions.
Can automatically restart impacted virtual machines on non-impacted
hosts.
56
Review of vSphere vMotion

A vSphere vMotion migration occurs over a network that is enabled
for vSphere vMotion.
VMkernel port
enabled for
vMotion
ESXi
ESXi
VMkernel port
enabled for
vMotion
migration of VMs execution state

vMotion
network
57
vSphere vMotion TCP/IP Stacks

In vSphere 6, each host has a second TCP/IP stack dedicated to
vSphere vMotion.
userworld
hostd
PING
DHCP
User
VMkernel
vSphere FT Virtual SAN
NFS
vSphere vMotion
VMKTCP-API
Default TCP IP
Default TCP IP
Separate Memory Heap
Separate Memory Heap
ARP Tables
ARP Tables
Routing Table
Routing Table
Default Gateway
Default Gateway
58
Example: vSphere vMotion Issue
vSphere vMotion fails at 15% or less, or times out completely.
Initial checks:
If vSphere vMotion was previously working, perform a check:
Restart the management agents on the ESXi host at the command prompt.
/etc/init.d/hostd restart
/etc/init.d/vpxa restart
Or restart the management agents on the ESXi host by using the DCUI.
59

The most probable causes of this issue can be attributed to the ESXi
host. Therefore, use a bottom-up approach to troubleshooting this
problem.
Possible Causes
VMkernel network connectivity is lost.
VMkernel network configuration is invalid.
ESXi
host
Name resolution is not valid on the host.

Time is not synchronized across the environment.
The required disk space is not available.

VM reservation requirements are not met on the target host.
60
Resetting Migrate.Enabled
If vSphere vMotion fails at 10% with the error, A general system
error occurred: Migration failed while copying data, Broken Pipe,
take the following action.
1. Try resetting the advanced setting, Migrate.Enabled.
a. Change the value to 0 and save the setting.
b. Change the value back to 1 and save the setting.
61
Possible Cause: DRS Configuration

DRS might have valid reasons for not performing vSphere vMotion
migrations.
DRS Never Migrates
DRS Seldom Migrates
DRS Often Migrates
The automation level is set to

manual mode.
Virtual machine loads are

fairly consistent.
Virtual machine loads are very

erratic in their resource
requirements.
The automation level is fully

automated mode and the
migration threshold is set to
apply priority 1
recommendations.

apply priority 1, 2, and 3
recommendations.

apply all recommendations.
62
vCenter and ESXi Host Troubleshooting
63
Example: vCenter Server Issue
Symptom: vCenter Server is slow to start.

Problem:
The vCenter Server database is not healthy.
Initial checks:
Validate that the basic configuration of the vCenter Server database
meets these requirements.
Adequate disk space available

Microsoft SQL Server: Healthy transaction logs, backed up regularly
Oracle: Adequate space available for tablespace growth
Ability to connect to the database repository through SQL Server or Oracle
Valid authentication to vCenter Server database
64
Example: ESXi Issue
The ESXi host crashes and displays a purple diagnostic screen.

A host crash produces a purple diagnostic screen.
Typical causes of a purple screen crash are the following:

CPU exception
Driver or module panic
Machine check exception (MCE)
Hardware fault
Genuine software defect
65
Recovering from a Purple Screen Crash

Record the state of the system.
Take a screenshot or photograph of the purple diagnostic screen.
Note any relevant environmental issues or conditions.
Restart the host.
Get the virtual machines up and running.
Collect a vm-support log bundle from the affected host.
Contact VMware technical support.

If technical support determines that the issue is a hardware problem,
you must contact your hardware vendor.
66
Example: ESXi Host Issue
Symptom: ESXi Host is inaccessible using SSH.

Problem:
Unable to access ESXi Host using remote SSH.
Initial checks:
Management network interface configuration
Lockdown Mode settings
67
Lockdown Mode and the DCUI

In vSphere 6.0, you can select normal lockdown mode or strict
lockdown mode:
Normal lockdown mode:
The DCUI service is not stopped.
Strict lockdown mode:
The DCUI service is stopped.
Accounts on the Exception User list and users in the DCUI.Access

list can access the DCUI:
DCUI.Access list:
A list of users that can disable lockdown

mode
Exception User list:
Users do not lose their privileges when

the host enters lockdown mode
68
VMware Education Services: Recommended Next Steps:

vSphere Training
Training
vSphere: Optimize and Scale3
Certification (vSphere 6)
VMware Certified Professional 6 - Data
Center Virtualization (VCP6-DCV)
vSphere: Install, Configure, Manage [V6]

vSphere: Whats New [V5.5 to V6]
If you have questions, contact a Learning Specialist!

1 (877) 735-1355
For complete options visit:
www.vmware.com/education
www.vmware.com/go/vsphere6training
69
VMware Learning Zone

Continuous learning beyond the
classroom
Subscription service with 12 months
of continuous, 24/7 access

Flexible training option where you
set the schedule

Scenarios and issues based on most
common VMware customer requests

Superb search functionality
Mobile Access
www.vmware.com/go/learningzone
70
Next FREE Webinar Save the Date!

A Technical Overview of Virtual Volumes
Learn how Virtual Volumes simplify Storage Operations,

Delivery and Resource Utilization.
Date: July 15, 2015
Instructor: Joe Cooper
Registration details will be in your follow-up email
71
Thank You!

Troubleshooting Web in Ar 60

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Troubleshooting Web in Ar 60

Hochgeladen von

Copyright:

Verfügbare Formate

Introduction to Troubleshooting Webinar

2015 VMware Inc. All rights reserved

VMware vSphere: Troubleshooting Webinar 6.0

VMware vSphere: Troubleshooting Webinar 6.0

VMware vSphere: Troubleshooting Webinar 6.0

Definition of a System Problem

This webinar addresses problems caused by configuration and

VMware vSphere: Troubleshooting Webinar 6.0

Effect of a System Problem

Performance troubleshooting is covered in the VMware vSphere:

VMware vSphere: Troubleshooting Webinar 6.0

Identifying the cause of the problem

Identifying possible causes

Resolving the problem

Identifying possible solutions

VMware vSphere: Troubleshooting Webinar 6.0

Gathering Information About the Problem

If so, what changed in your environment or configuration?

Consult references, such as product release notes, to determine

Use your existing knowledge of your systems configuration to help

VMware vSphere: Troubleshooting Webinar 6.0

Viewing and Interpreting Diagnostic Information

Example: Error powering on a virtual machine

VMware vSphere: Troubleshooting Webinar 6.0

Identifying Possible Causes

Approach cause by halves

VMware vSphere: Troubleshooting Webinar 6.0

Resolving the Problem

VMware vSphere: Troubleshooting Webinar 6.0

Example: Defining the Problem

VMware vSphere vMotion migration fails with an error.

VMware vSphere: Troubleshooting Webinar 6.0

Example: Gathering Information

VMware vSphere: Troubleshooting Webinar 6.0

Example: Identifying Possible Causes

Network connectivity is down

on one of the ESXi hosts.

vMotion VMkernel interface connectivity

VMware vSphere: Troubleshooting Webinar 6.0

Example: Determining the Root Cause

Fix network configuration

Fix VMkernel configuration

VMware vSphere: Troubleshooting Webinar 6.0

Example: Resolving the Problem

The problem affects any virtual machine that is migrated to esxi02.

Identify possible solutions to resolve the problem.

VMware vSphere: Troubleshooting Webinar 6.0

Commandline Troubleshooting Tools

VMware vSphere: Troubleshooting Webinar 6.0

Commandline Troubleshooting Tools

vSphere Management Assistant

Includes the VMware vSphere Command-Line Interface (vCLI) package

VMware vSphere: Troubleshooting Webinar 6.0

vSphere ESXi Shell

To access the remote vSphere ESXi Shell:

VMware vSphere: Troubleshooting Webinar 6.0

vSphere Management Assistant

vi-fastpass authentication component

Enables you to run system administration commands to manage ESXi

VMware vSphere: Troubleshooting Webinar 6.0

VMware vSphere: Troubleshooting Webinar 6.0

Example: Viewing vSphere Network Information

Physical and virtual network information can be displayed by using

VMware vSphere: Troubleshooting Webinar 6.0