Book Image

VMware Performance and Capacity Management, Second Edition - Second Edition

By : Sunny Dua
Book Image

VMware Performance and Capacity Management, Second Edition - Second Edition

By: Sunny Dua

Overview of this book

Performance management and capacity management are the two top-most issues faced by enterprise IT when doing virtualization. Until the first edition of the book, there was no in-depth coverage on the topic to tackle the issues systematically. The second edition expands the first edition, with added information and reorganizing the book into three logical parts. The first part provides the technical foundation of SDDC Management. It explains the difference between a software-defined data center and a classic physical data center, and how it impacts both architecture and operations. From this strategic view, it zooms into the most common challenges—performance management and capacity management. It introduces a new concept called Performance SLA and also a new way of doing capacity management. The next part provides the actual solution that you can implement in your environment. It puts the theories together and provides real-life examples created together with customers. It provides the reasons behind each dashboard, so that you get the understanding on why it is required and what problem it solves. The last part acts as a reference section. It provides a complete reference to vSphere and vRealize Operations counters, explaining their dependencies and providing practical guidance on the values you should expect in a healthy environment.
Table of Contents (28 chapters)
VMware Performance and Capacity Management Second Edition
Credits
Foreword
Foreword
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Part 1
Part 2
Part 3
Index

Network


Let's recap what we need to produce in order to monitor network capacity:

  • A line chart showing the maximum network dropped packets at the physical data center level. We use a physical data center and not vSphere cluster, as they eventually share the same core switches.

  • A line chart showing the maximum and average ESXi vmnic at the same level as per the previous point. This will tell you whether any of your vmnics are saturated.

In the first line chart, notice it only has the maximum line. We're not tracking the average dropped packets. The reason is that we're not expecting any packet loss, so the average is irrelevant.

We covered the first line chart in the performance chapter. So we just need to add the utilization line chart.

Dropped packets are much easier to track, as you expect 0 everywhere. Utilization is harder. If your ESXi has mixed 10 GE and 1 GE vmnics, you would expect the 10 GE vmnic to dominate the data. This is where consistent design and standards matter. Without it,...