6.5.1

n
Ensure that the physical NIC capacity is large enough to handle the network trac on that virtual
switch. If the capacity is not enough, consider using a high-bandwidth physical NIC (10Gbps) or
moving some virtual machines to a virtual switch with a lighter load or to a new virtual switch.
n
If packets are being dropped at the virtual switch port, increase the virtual network driver ring buers
where applicable.
n
Verify that the reported speed and duplex seings for the physical NIC match the hardware
expectations and that the hardware is congured to run at its maximum capability. For example, verify
that NICs with 1Gbps are not reset to 100Mbps because they are connected to an older switch.
n
Verify that all NICs are running in full duplex mode. Hardware connectivity issues might result in a
NIC reseing itself to a lower speed or half duplex mode.
n
Use vNICs that are TCP Segmentation Ooad (TSO)-capable, and verify that TCP Segmentation
Ooad-Jumbo Frames are enabled where possible.
Empty Performance Charts
No graphics or data are displayed in performance charts.
Problem
When data is missing for a performance chart, the chart appears empty and you see the message No data
available.
Cause
The causes for missing data in performance charts that are described herein are based on the assumption
that the default roll-up conguration for the vCenter Server system has not changed. The causes include but
are not limited to the following scenarios:
n
Metrics introduced in ESXi 5.0 are not available for hosts running earlier versions.
n
Data is deleted when you remove or add objects to vCenter Server.
n
Performance charts data for inventory objects that were moved to a new site by VMware vCenter Site
Recovery Manager is deleted from the old site and not copied to the new site.
n
Performance charts data is deleted when you use VMware vMotion across vCenter Server instances.
n
Real-time statistics are not available for disconnected hosts or powered o virtual machines.
n
Real-time statistics are collected on hosts and aggregated every 5 minutes. After six data points are
collected for approximately 30 minutes, they are rolled up to the vCenter Server database to create the
1-Day statistic. 1-Day statistics might not be available for 30 minutes after the current time, depending
on when the sample period began.
n
The 1-Day statistics are rolled up to create one data point every 30 minutes. If a delay occurs in the roll-
up operation, the 1-Week statistics might not be available for 1 hour after the current time. It takes 30
minutes for the 1-Week collection interval, plus 30 minutes for the 1-Day collection interval.
n
The 1-Week statistics are rolled up to create one data point every two hours. If a delay occurs in the roll-
up operations, the 1-Month statistics might not be available for 3 hours. It takes 2 hours for the 1-Month
collection interval, plus 1 hour for the 1-Week collection interval.
n
The 1-Month statistics are rolled up to create one data point every day. If a delay occurs in the roll-up
operations, the statistics might not be available for 1-day and 3 hours. It takes one day for the past year
collection interval, plus 3 hours for the past month collection interval. During this time, the charts are
empty.
Solution
u
There is no solution available.
vSphere Monitoring and Performance
98 VMware, Inc.