VMWare Monitoring

How to monitor VMWares?

VMWare provides different technologies which can be used to monitor

 CIM(WBEM)
 Web Services
 Power Shell
 SNMP

To monitor through Web Services, we can use Virtual Infrastructure SDK,

which is used in various VI tools.

Virtual Infrastructure SDK is supported for following VMWare versions:

 ESX 3.5
 ESX 3i
 ESX 3.0.x
 VSphere
 Virtual Center 2.5
 Virtual Center Server 2.0.x

VI provides following Management/Monitoring Components:

 Inventory
 Virtual Machine Management
 Performance Monitoring
 Event / Alarms

Virtual Infrastructure SDK provides two types of interfaces to communicate

1. Java API’s (Managed Objects)
2. Web Services (Non-Managed Objects)

Note: Java API’s uses internal web services, but it has been managed and day
to day getting updated.

Inventory Performance
Host Guest Note: Need to verify it gives Guest as
well as Host System performance or
only guest
Bios Info Disk CPU
Cpu Info Guest Family (OS) Disk I/O counters
Cpu Pkg Guest Full Name Storage Utilization
(OS)
Cpu Power GuestID Memory
Management Info
Memory Size Guest State Network
Non-Uniform Guest HostName Heart beat (Guest)
Memory Access
PCI Devices IPAddress Uptime
 System Info NIC
(Dynamic Info)
Screen Resolution

Apart from the above it provides certain performance counters like

• numChangeDS (Data Store)
• numchangeHost (For powered off & suspended)
• numClone
• numCreate
• numDeploy
• numDestroy

Node: The above counters are web services operations which will give the
counts,

Proposed Programming language:

1. Java can be used as it is useful in maintainability compare to C++, If we
use C++ then we have to create our own objects by using WSDL files and GSOAP.
2. C# also supported.

Integration with SapphireIMS:

Data Collector:
We can have Java VMware Monitoring Data Collector which will collect the
Inventory/Performance.

Note: We can also integrate as a Poller by using our generic poller module.

Discovery Integration:
A dll can be provided by using GSOAP, which will give the minimal data,
which is required by Discovery module like
Host System
 Bios
 MAC,
 Gateway etc.
 OS Name (ESX etc)

Guest System
 No of Guest OS
 Status
 OS
 Guest ID

( or )

TCP based communication between Discovery Module and Data Collector /

Poller can be used.