presentation title goes here - ibmlinux windows/ linux monitoring a traditional vmware environment...

26
监控您的 SmartCloud 刘鹤 IBM 软件部

Upload: others

Post on 26-Jul-2020

12 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

监控您的 SmartCloud

刘鹤IBM软件部

Page 2: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Agenda• Why is SmartCloud Monitoring Important

• Best Practices for SmartCloud Monitoring of VMware– Operational Health Dashboard– Deployment Considerations– Historical Collection

• Integration Scenarios

• Capacity Planning– Trends– Cloud management– Smart Cloud Monitoring– Planning capability

Page 3: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

SmartCloud Monitoring: Why is it important

Page 4: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Monitoring the VMware environment with IBM SmartCloud Monitoring - Why it is important?

• VCenter – provides monitoring of hypervisor; static alarms & events that can be sent to an event management system. Which is fine if your infrastructure is static and you only care if performance exceeds a certain capacity or performance limit

• SmartCloud Monitoring provides in ONE tool:– Dynamic thresholding– Predictive Analytics– Capacity planning– Storage and Network monitoring– Reporting for performance trends– OS Monitoring– Monitoring across servers, storage – phys & virt view– Integrated monitoring for Virtualization, Applications, Middleware, and

more.– Easy Integration into other parts of the Tivoli portfolio

Page 5: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Operational HealthDashboard

Page 6: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

SmartCloud Monitoring Health Summary Dashboard: Great tool for Operations team

Page 7: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Health Dashboard Dashboards with holistic view of health of whole environment

Out of the box contextual views of health (availability, performance and capacity) in the complete context of the virtual environment to include physical and virtual server, storage and network resources.

Integrates across our tool set to merge physical & virtual data – Storage, Network, ITM, TADDM & VMware

Views with performance and capacity reports for assessment of environment and long term trend analysis.

Page 8: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Best Practices for SmartCloud Monitoring of VMware

Page 9: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Windows/Linux

Windows/Linux

Monitoring a Traditional VMware Environment• ESX/ESXi servers managed by

vCenter• Best Practice Deployment is to

deploy 1 Agent per vCenter• VMotion between similar

hardware• IBM Tivoli Monitoring with vCenter

Server:– An Agent is installed on

Windows or Linux– The VMware VI Agent is

configured to monitor remotely through vCenter

– Multi-Instance Agent

Agent-lessOS Monitors

Windows/Linux

HUBTEMS

RemoteTEMS

RemoteTEMS

OS Agents

VI Agent

ESX/ESXiESX/E

SXiESX/ESXiESX/E

SXiESX/ESXiESX/E

SXiESX/ESXi

ESX/ESXiESX/E

SXiESX/ESXiESX/E

SXiESX/ESXiESX/E

SXiESX/ESXi

vCenterServer

vCenterServer

TEPS

VI Agent

Windows/Linux

Spare Remote

TEMS

OS Agents

OS Agents

OS Agents

Page 10: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Deployment Scalability/Sizing• Virtual Center/vCenter

– For Virtual Center 2.5 the maximums are 200 ESX hosts or 2000 virtual machines.

– For VCenter 4.1 & 5.0 the maximums are 1000 ESX hosts or 10,000 virtual machines.

– If vCenter has capacity, Agent can be run on vCenter– Disk Space…200 Meg for Agent– Short Term History Data:

• 85 Meg for 10 ESX servers• 415 Meg for 50 ESX servers• 1.6 Gig for 200 ESX servers• 4 Gig for 500 ESX servers

Page 11: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Deployment Scalability/Sizing

• Unless vCenter environments are small, recommend 1 vCenter per Agent instance

• Multiple Vmware VI Agent instances may run on a server• Vcenter Failover:

– Agent installed on VCenter- automatically will monitor the VCenter as it fails over.

– Agent installed on another machine - Install 2 VMWare VI Agent instances and then create situations and automation to stop the instance that is monitoring the inactive VCenter and start the other VMware VI instance.

Page 12: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Monitoring Recommendations• Out-of-the-box Best Practice Situation to monitor

– Resource Pool CPU and Memory utilization– Disk and Network I/O– ESX/ESXi utilization– VM utilization including CPU Ready– Data Store utilization– Cluster Utilization (CPU, Effective CPU, Memory, and Effective Memory)

• Clone the out-of-the-box Situations• In addition to the out-of the box Situations, monitor:

– Monitor to ensure VM Tools are installed and up to date– Use TCR Reports or OMNIbus to monitor high VMotion rates for specific servers

and clusters

• Key workspaces include Top 5/Bottom 5 report shown

Page 13: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Top 5 / Bottom 5 Clusters

Links provided for drilldown

Top 5/Bottom 5 Cluster for CPU and Memory

Page 14: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Link from VMware Agent to OS Agent

Link from VMware Agent to OS Agent

Page 15: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

TCR Report: Balanced ClustersUnbalanced

Can’t move workload to this cluster because it’s almost out of datastore space

On one screen, I can check all of the key resources to see if my workload is balanced

Page 16: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Other Monitoring Considerations• Other Key Attributes:

– Percent Ready…should never be above 10%. Recommend WARNING at 5% and CRITICAL at 10% sustained utilization

• Hyper-threading CPUs can drive Percent Ready higher…can be disabled in BIOS.

– Disk Latency including queue, device, and kernel latency– Balloon Usage…should be low. In order to use Balloon memory, you must have

VMtools installed.– Guest Swap Used should be zero or performance will degrade – Resource Pool CPU Usage…Percentage takes into account reservation– Resource Pool Memory…Percentage takes into account reservation– Percent Effective CPU and Memory Utilization for Clusters

Page 17: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Historical Collection Filtering

Filter out Removable Storage

Page 18: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Additional Integrations

Page 19: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Additional Integrations• NetApp Storage Agent:

– Provides Monitoring data in ITM– Integrates into Health Dashboard

• TADDM Integration– TADDM DLA discovers the vCenter

environment/topology– TADDM provides change data to VMware Health

Dashboard

• IBM Director Integration– ITM Agent provides integration with the Director

Server– Allows for Management of VMware resources– Historical Collection of HW data

• Tivoli Storage Productivity Center:– Agent provides storage metrics in TEP– Integrates into Health Dashboard– Warehouse storage metrics for reporting and

analysis

• Network Monitoring Agent– Monitor switches used by Vmware– Integrate Network Events into Dashboard

ITM

ESX/ESXi

ESX/ESXi

ESX/ESXi

ESX/ESXi

ESX/ESXi

ESX/ESXi

ESX/ESXi

vCenterServer

NetApp

NetApp Agent

DFM

TADDMDLA

Health Dashboard

TPC

IBM Storage

Hitachi

EMC

NetApp

NetworkSwitches

NetworkSwitches

VI Agent

Page 20: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Capacity PlanningIBM SmartCloud Monitoring – A Deeper Look at Capacity Analytics

Page 21: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Why is Capacity Management Important? Helps consolidate and reduce costs

oReduces HW and labor costsoReduces number of physical servers required to run workloadsoReduce number of required licenseso Increase VM density and increase Cloud ROIoPredict how many more customers / VMs can be serviced

Helps ensure application availability and reduce riskoAre any resources overloaded? When will physical resources reach their limits?oHave there been any significant changes in my environment between two weeks?o Identify trends to predict bottlenecks or free space and balance workloadso Ensure supply can meet demando Ensure technical and business policies are met to reduce risk

Helps optimize resource utilizationoRight size virtual machines and allocate based on usage, over-commit within known

risk limitsoPack VMs on the infrastructure to optimize resources

Page 22: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Planning Analytics

…Platforms

Storage Network

HypervisorsServers

Workload Characterization- Establish patterns using historical data- Capture workload attributes to enable optimization policies

Capacity Planning Database

Optimization Engine to size and place VMs

PlanRecommendation

(minimize systems, license, balance)

Business and Technical policies

Copy, Federate

Custom Tagsenhance Config Profiles and

workload relationships

Benchmarking data

Usage profiles, workload relationships

Page 23: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Planning Scenarios1. An IT Admin wants to consolidate an

existing environment and optimize the use of physical resources

1. A Capacity Planner performs what-if analysis to accommodate future VM requests

2. A Capacity Planner applies business and technical best practices to create a plan

Page 24: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Planning Scenarios1. An IT Admin wants to consolidate an

existing environment and optimize the use of physical resources

1. A Capacity Planner performs what-if analysis to accommodate future VM requests

1. A Capacity Planner applies business and technical best practices to create a plan

Page 25: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

Planning Scenarios1. An IT Admin wants to consolidate an

existing environment and optimize the use of physical resources

2. A Capacity Planner performs what-if analysis to accommodate future VM requests

1. A Capacity Planner applies business and technical best practices to create a plan

Page 26: Presentation Title Goes Here - IBMLinux Windows/ Linux Monitoring a Traditional VMware Environment • ESX/ESXi servers managed by vCenter • Best Practice Deployment is to deploy

http://www-142.ibm.com/software/products/cn/zh/tivomoniforvirtenvi