Monitoring VMware Virtualization
Using vMA & The Plugin
box293_check_vmware
Troy Lea
tlea@nagios.com
Twitter: @box293
Great Plugin with many
Options and powerful
Stats
- Marvin Holze
Documentation
was
GREAT!
- Kevin Oswald
A qualifi...
Why did I create the plugin?
• Not satisfied with the existing solutions
available
• Existing solutions crippled Nagios...
What is vMA ???
● VMware vSphere Management Assistant (vMA)
– Virtual Appliance
● It's a SUSE VM with the VMware Perl S...
Why use vMA ???
● It offloads the VMware SDK from your Nagios
host
● CPU and Memory Hungry !!!!!!!!
● Deploy vMA in mi...
How does Nagios use vMA?
vCenter or ESX or ESXi
● Plugin works with:
● vCenter
● ESX
● ESXi
● vCenter is not required to use the plugin
HOWEV...
Is it secure / safe?
● vCenter
● Read only credentials are recommended
● Includes ESX(i) hosts connected via vCenter
●...
How do I get vMA up and running?
● Read the manual
● The manual has step by step instructions on
how to get it up and r...
Quick Break
What Can It Monitor?
● Cluster_CPU_Usage
● Cluster_DRS_Status
● Cluster_EVC_Status
● Cluster_HA_Status
● Cluster_Memo...
Common Options - Thresholds
● Thresholds
● warning and/or critical thresholds
● One does not require the other
● Each ...
Common Options – Reporting Units
● --reporting_si
● International System of Unit to use for results
● Argument format: ...
Common Options – Concurrent Checks
● --concurrent_checks
● Maximum amount of concurrent checks that can run at
any one ...
Read The Manual
● There are a lot more options available
● The manual covers them all in detail
● Lets look at all the ...
Quick Break
vCenter / Cluster
● Cluster_CPU_Usage
● Cluster_DRS_Status
● Cluster_EVC_Status
● Cluster_HA_Status
● Cluster_Memory_...
Cluster_CPU_Usage
Report the specified Clusters' CPU Usage
Returned as GHz by default
Required Arguments:
--cluster
O...
Cluster_DRS_Status
Check the specified Distributed Resource Scheduler (DRS) Cluster
Required Arguments:
box293_check_vm...
Cluster_EVC_Status
Check the specified Clusters' Enhanced vMotion Compatibility (EVC) Mode
Required Arguments:
--cluste...
Cluster_HA_Status
box293_check_vmware.pl ­­check
Cluster_HA_Status ­­server
192.168.1.211 ­­cluster
"Empty
Cluster" ­...
Cluster_Memory_Usage
Report the specified Clusters' Memory Usage
Returned as GB by default
Required Arguments:
--clust...
Cluster_Resource_Info
Reports the resources in a cluster such as Hosts, CPU and Memory
OK: Always Cluster returns an OK ...
Cluster_Swapfile_Status
Checks the the Clusters' Swapfile Policy
Required Arguments:
--cluster
Optional Arguments:
--...
Cluster_vMotion_Info
Reports the number of vMotions performed in the Cluster
Always returns an OK state
Useful for gath...
vCenter_License_Status
Reports the specified vCenters' license status along with the license key
If vCenter is in evalua...
vCenter_Name_Version
Report the specified vCenter product Name and Version
Required Arguments:
--server
box293_check_v...
Guests (VMs)
● Guest_CPU_Info
● Guest_CPU_Usage
● Guest_Disk_Performance
● Guest_Disk_Usage
● Guest_Memory_Info
● Gu...
Guest_CPU_Info
box293_check_vmware.pl ­­check
Guest_CPU_Info ­­server
192.168.1.211
­­guest
"vSphere Management Assis...
Guest_CPU_Usage
Report the specified Guests' CPU Usage
Returned as MHz and ms by default
Required Arguments:
--guest
...
Guest_Disk_Performance
Check the Disk Performance of a Guests' virtual disk(s)
Metrics returned are:
Disk Rate (Read an...
Guest_Disk_Usage
Check the Disk Usage of a Guests' virtual disk(s)
Returned as GB by default
Returns overall usage of a...
Guest_Memory_Info
Report Information about the Guests' Memory such as Total, Reservation and Limit
box293_Returned as MB...
Guest_Memory_Usage
Report the specified Guests' Memory Usage
Returned as MB and kBps by default
Memory Swapping is repo...
Guest_NIC_Usage
Check the Guests' Network Interface Card(s) (NIC) usage
Returned as kBps by default
If the guest has mo...
Guest_Snapshot
Check if a guest has snapshots & trigger warning/critical states if snapshot is X days old
If a guest has...
Guest_Status
Check the status of a guest including Power State, Uptime, VMware Tools Version and Status, IP Address,
Hos...
Hosts
● Host_CPU_Info
● Host_CPU_Usage
● Host_License_Status
● Host_Memory_Usage
● Host_OS_Name_Version
● Host_pNIC_...
Datastore_Performance
Check the performance of a specific Datastore
Metrics returned are:
box293_Datastore check_Rate (...
Example Graphs
Datastore_Usage
Check the Usage of a specific Datastore
Returned as GB by default
Required Arguments:
--name
Optional...
Host_CPU_Info
Report Information about the Hosts' CPU such as Model, Cores and Total CPU
Returned as GHz by default
Req...
Host_CPU_Usage
Report the specified Hosts' CPU Usage
Returned as GHz by default
Required Arguments:
--host (if connect...
Host_License_Status
Reports the specified Hosts license status along with the license key
If the host is in evaluation m...
Host_Memory_Usage
Report the specified Hosts' Memory Usage
Returned as GB by default
Required Arguments:
--host (if co...
Host_OS_Name_Version
Report the specified Hosts' product Name and Version
Required Arguments:
--host (if connected via ...
Host_pNIC_Status
Check the Status of the Hosts' Physical Network Interface Card(s) (pNIC)
box293_All pNICs are check_ret...
Host_pNIC_Usage
Check the Hosts' Physical Network Interface Card(s) (pNIC) usage
Returned as kBps by default
All pNICs ...
Example Graphs
Host_Status
Check the overall status of a Host and report any known issues
Required Arguments:
--host (if connected via...
Host_Storage_Adapter_Info
Report Information about the Hosts' Storage Adapter(s) such as Model, Device Name and
Driver N...
Host_Storage_Adapter_Performance
Check the performance of a specific Hosts' Storage Adapter
Metrics returned are:
Rate ...
Example Graphs
Host_Switch_Status
Check the Status of a Hosts' vSwitch or Distributed Switch including all pNICs that are
connected to ...
Host_vNIC_Status
Check the Status of the Hosts' Virtual Network Interface Card(s) (vNIC) and report the role(s)
All vNIC...
BREATHE!
Pause to take a breath
Surely I must be finished
Just one more thing ...
Introducing …
Nagios XI VMware Wizard
● Released Soon
● A Configuation Wizard for Nagios XI
● Queries your VMware Virtualization Infr...
Quick Break
Conclusion
box293_check_vmware is:
• An offloaded plugin for Nagios
• Easy to implement
• Feature Rich
• Wizard for N...
Great Plugin with many
Options and powerful
Stats
- Marvin Holze
Documentation
was
GREAT!
- Kevin Oswald
A qualifi...
The End
Troy Lea
tlea@nagios.com
Twitter: @box293
Nagios Conference 2014 - Troy Lea - Monitoring VMware Virtualization Using vMA
Nagios Conference 2014 - Troy Lea - Monitoring VMware Virtualization Using vMA
of 64

Nagios Conference 2014 - Troy Lea - Monitoring VMware Virtualization Using vMA

Troy Lea's presentation on Monitoring VMware Virtualization Using vMA. The presentation was given during the Nagios World Conference North America held Oct 13th - Oct 16th, 2014 in Saint Paul, MN. For more information on the conference (including photos and videos), visit: http://go.nagios.com/conference
Published on: Mar 3, 2016
Source: www.slideshare.net


Transcripts - Nagios Conference 2014 - Troy Lea - Monitoring VMware Virtualization Using vMA

  • 1. Monitoring VMware Virtualization Using vMA & The Plugin box293_check_vmware Troy Lea tlea@nagios.com Twitter: @box293
  • 2. Great Plugin with many Options and powerful Stats - Marvin Holze Documentation was GREAT! - Kevin Oswald A qualified VMware and Nagios systems administrator will have no issue getting things up and running with relative ease. - John Chivian Thank you for your effort you put into this amazing plugin. We are using this plugin to monitor our vmware infrastructure and it is working great so far. - Seyfidin Hamraoui I’ve been testing your vmware plugin, which has been a big help, many thanks for taking the time to develop it. - Paul Mason I just installed and configured your vMA software and now monitoring our vCenter with it. Manual was really clear and so it was easily done. - Vincent Palmboom I've only used 2 VMware plugins, but Box's is the best of the 2. We recently switched to it and I haven't had any reason to look for another one. - snapon_admin Still by far the best documented plugin I've seen, and works as advertised. - fusfeld
  • 3. Why did I create the plugin? • Not satisfied with the existing solutions available • Existing solutions crippled Nagios when scaled up • I wanted to audit as well as monitor (versions, settings, options)
  • 4. What is vMA ??? ● VMware vSphere Management Assistant (vMA) – Virtual Appliance ● It's a SUSE VM with the VMware Perl SDK install on it with all the prerequisites ● VMware's solution to manage ESXi hosts
  • 5. Why use vMA ??? ● It offloads the VMware SDK from your Nagios host ● CPU and Memory Hungry !!!!!!!! ● Deploy vMA in minutes ● No time wasted with confusing installation per-requisites
  • 6. How does Nagios use vMA?
  • 7. vCenter or ESX or ESXi ● Plugin works with: ● vCenter ● ESX ● ESXi ● vCenter is not required to use the plugin HOWEVER certain checks are only available via vCenter
  • 8. Is it secure / safe? ● vCenter ● Read only credentials are recommended ● Includes ESX(i) hosts connected via vCenter ● ESX(i) – Direct without vCenter ● Current testing done with root account however setting up a read-only account is possible (being added to the manual in the future)
  • 9. How do I get vMA up and running? ● Read the manual ● The manual has step by step instructions on how to get it up and running
  • 10. Quick Break
  • 11. What Can It Monitor? ● Cluster_CPU_Usage ● Cluster_DRS_Status ● Cluster_EVC_Status ● Cluster_HA_Status ● Cluster_Memory_Usage ● Cluster_Resource_Info ● Cluster_Swapfile_Status ● Cluster_vMotion_Info ● Datastore_Performance ● Datastore_Usage ● Guest_CPU_Info ● Guest_CPU_Usage ● Guest_Disk_Performance ● Guest_Disk_Usage ● Guest_Memory_Info ● Guest_Memory_Usage ● Guest_NIC_Usage ● Guest_Snapshot ● Guest_Status ● Host_CPU_Info ● Host_CPU_Usage ● Host_License_Status ● Host_Memory_Usage ● Host_OS_Name_Version ● Host_pNIC_Status ● Host_pNIC_Usage ● Host_Status ● Host_Storage_Adapter_Info ● Host_Storage_Adapter_Performance ● Host_Switch_Status ● Host_vNIC_Status ● vCenter_License_Status ● vCenter_Name_Version
  • 12. Common Options - Thresholds ● Thresholds ● warning and/or critical thresholds ● One does not require the other ● Each threshold is in the format: ● <type>:<value> ● Example: cpu_free:10 ● Multiple thresholds separated with a comma ● Example: disk_rate:150,disk_latency:30
  • 13. Common Options – Reporting Units ● --reporting_si ● International System of Unit to use for results ● Argument format: ● <type>:<SI> ● Example: CPU_Speed:GHz ● Multiple arguments separated with a comma ● Example: Datastore_Rate:kBps,Latency:ms
  • 14. Common Options – Concurrent Checks ● --concurrent_checks ● Maximum amount of concurrent checks that can run at any one time ● Default is 15 ● This option helps prevent the vMA appliance from being overloaded, as the VMware SDK will consume lots of CPU and memory resources ● Increase # concurrent checks to suite your environment
  • 15. Read The Manual ● There are a lot more options available ● The manual covers them all in detail ● Lets look at all the checks and their options
  • 16. Quick Break
  • 17. vCenter / Cluster ● Cluster_CPU_Usage ● Cluster_DRS_Status ● Cluster_EVC_Status ● Cluster_HA_Status ● Cluster_Memory_Usage ● Cluster_Resource_Info ● Cluster_Swapfile_Status ● Cluster_vMotion_Info ● vCenter_License_Status ● vCenter_Name_Version
  • 18. Cluster_CPU_Usage Report the specified Clusters' CPU Usage Returned as GHz by default Required Arguments: --cluster Optional Arguments: --reporting_si CPU_Speed:<Hertz> --warning and --critical cpu_free:<Hertz>, cpu_used:<Hertz> box293_check_vmware.pl --check Cluster_CPU_Usage --server 192.168.1.211 --cluster HA OK: {Cores (Total: 6) (Available: 4)} {CPU (Free: 9.8 GHz) (Used: 0.9 GHz) (Effective: 10.7 GHz) (Total: 22.8 GHz)}|'Cores Total'=6 'Cores Available'=4 'CPU Free'=9.8GHz 'CPU Used'=0.9GHz 'CPU Effective'=10.7GHz 'CPU Total'=22.8GHz
  • 19. Cluster_DRS_Status Check the specified Distributed Resource Scheduler (DRS) Cluster Required Arguments: box293_check_vmware.pl ­­check Cluster_DRS_Status ­­server 192.168.1.211 ­­cluster "Empty Cluster" ­­drs_ automation_level manual ­­drs_ dpm_level on box293_check_vmware.pl ­­check --cluster Cluster_DRS_Status ­­server 192.168.1.211 ­­cluster "Empty Cluster" ­­drs_ automation_level manual ­­drs_ dpm_level on Optional Arguments: --drs_state --drs_automation_level --drs_dpm_level --exclude_issue CRITICAL: DRS: {Enabled} {Automation Level is fullyAutomated but should be manual} {Migration Threshold: 1} {DPM is off but should be on} box293_check_vmware.pl --check Cluster_DRS_Status --server 192.168.1.211 --cluster "Empty Cluster" --drs_automation_level manual --drs_dpm_level on CRITICAL: DRS: {Enabled} {Automation Level is fullyAutomated but should be manual} {Migration Threshold: 1} {DPM is off but should be on} CRITICAL: DRS: {Enabled} {Automation Level is fullyAutomated but should be manual} {Migration Threshold: 1} {DPM is off but should be on} *
  • 20. Cluster_EVC_Status Check the specified Clusters' Enhanced vMotion Compatibility (EVC) Mode Required Arguments: --cluster Optional Arguments: --evc_mode box293_check_vmware.pl --check Cluster_EVC_Status --server 192.168.1.211 --cluster "Empty Cluster" OK: EVC: intel-westmere
  • 21. Cluster_HA_Status box293_check_vmware.pl ­­check Cluster_HA_Status ­­server 192.168.1.211 ­­cluster "Empty Cluster" ­­ha_ admission_control disabled OK: HA: {Enabled} {Host Monitoring: Enabled} {Admission Control: Disabled} {VM Options: Restart Priority: Low, Isolation Response: Shutdown} {VM Monitoring: VM Only} * Check the specified High Availability (HA) Cluster Required Arguments: box293_check_vmware.pl ­­check Cluster_--cluster HA_Status ­­server 192.168.1.211 ­­cluster "Empty Cluster" ­­ha_ admission_control disabled OK: HA: {Enabled} {Host Monitoring: Enabled} {Admission Control: Disabled} {VM Options: Restart Priority: Low, Isolation Response: Shutdown} {VM Monitoring: VM Only} Optional Arguments: --ha_state --ha_host_monitoring --ha_admission_control --exclude_issue box293_check_vmware.pl --check Cluster_HA_Status --server 192.168.1.211 --cluster "Empty Cluster" --ha_admission_control disabled OK: HA: {Enabled} {Host Monitoring: Enabled} {Admission Control: Disabled} {VM Options: Restart Priority: Low, Isolation Response: Shutdown} {VM Monitoring: VM Only}
  • 22. Cluster_Memory_Usage Report the specified Clusters' Memory Usage Returned as GB by default Required Arguments: --cluster Optional Arguments: --reporting_si Memory_Size:<Bytes> --warning and --critical memory_free:<Bytes>, memory_used:<Bytes> box293_check_vmware.pl --check Cluster_Memory_Usage --server 192.168.1.211 --cluster HA --reporting_si Memory_Size:MB --warning memory_free:3000 --critical memory_free:2000 WARNING: Memory {Free: 2,492 MB (WARNING <= 3,000)} {Used: 1,983 MB} {Effective: 4,475 MB} {Total: 12,286.5 MB}|'Memory Free'=2492MB;3000;2000 'Memory Used'=1983MB 'Memory Effective'=4475MB 'Memory Total'=12286.5MB
  • 23. Cluster_Resource_Info Reports the resources in a cluster such as Hosts, CPU and Memory OK: Always Cluster returns an OK 'state HA' [Hosts {Total: 3} {Available: Returned as GHz and 2}] GB by [{default. Cores (Total: 6) (Available: 4)} {CPU (Free: 10.4 GHz) (Used: 0.3 GHz) (Effective: 10.7 GHz) (Total: 22.8 GHz)}] [Memory {Free: 2.4 GB} {Used: 2 GB} {Effective: 4.4 GB} {Total: 12 GB}]|'Hosts Total'=3 'Hosts Available'=2 'Cores Total'=6 'Cores Available'=4 'CPU Free'=10.4GHz 'CPU Used'=0.3GHz 'CPU Effective'=10.7GHz 'CPU Total'=22.8GHz 'Memory Free'=2.4GB 'Memory Used'=2GB 'Memory Effective'=4.4GB 'Memory Total'=12GB Required Arguments: --cluster Optional Arguments: --reporting_si CPU_Speed:<Hertz>, Memory_Size:<Bytes> box293_check_vmware.pl --check Cluster_Resource_Info --server 192.168.1.211 --cluster HA OK: Cluster 'HA' [Hosts {Total: 3} {Available: 2}] [{Cores (Total: 6) (Available: 4)} {CPU (Free: 10.4 GHz) (Used: 0.3 GHz) (Effective: 10.7 GHz) (Total: 22.8 GHz)}] [Memory {Free: 2.4 GB} {Used: 2 GB} {Effective: 4.4 GB} {Total: 12 GB}]|'Hosts Total'=3 'Hosts Available'=2 'Cores Total'=6 'Cores Available'=4 'CPU Free'=10.4GHz 'CPU Used'=0.3GHz 'CPU Effective'=10.7GHz 'CPU Total'=22.8GHz 'Memory Free'=2.4GB 'Memory Used'=2GB 'Memory Effective'=4.4GB 'Memory Total'=12GB * OK: Cluster 'HA' [Hosts {Total: 3} {Available: 2}] [{Cores (Total: 6) (Available: 4)} {CPU (Free: 10.4 GHz) (Used: 0.3 GHz) (Effective: 10.7 GHz) (Total: 22.8 GHz)}] [Memory {Free: 2.4 GB} {Used: 2 GB} {Effective: 4.4 GB} {Total: 12 GB}]|'Hosts Total'=3 'Hosts Available'=2 'Cores Total'=6 'Cores Available'=4 'CPU Free'=10.4GHz 'CPU Used'=0.3GHz 'CPU Effective'=10.7GHz 'CPU Total'=22.8GHz 'Memory Free'=2.4GB 'Memory Used'=2GB 'Memory Effective'=4.4GB 'Memory Total'=12GB
  • 24. Cluster_Swapfile_Status Checks the the Clusters' Swapfile Policy Required Arguments: --cluster Optional Arguments: --swapfile_policy box293_check_vmware.pl --check Cluster_Swapfile_Status --server 192.168.1.211 --cluster HA OK: Swapfile Policy: Store In VM Directory
  • 25. Cluster_vMotion_Info Reports the number of vMotions performed in the Cluster Always returns an OK state Useful for gathering performance data to observe trends over time Required Arguments: --cluster box293_check_vmware.pl --check Cluster_vMotion_Info --server 192.168.1.211 --cluster HA OK: vMotions: 283|'Number of vMotions'=283
  • 26. vCenter_License_Status Reports the specified vCenters' license status along with the license key If vCenter is in evaluation mode and has less than 24 hours remaining a CRITICAL state is returned otherwise a WARNING state is returned When vCenter is queried using an account that has read only privileges, only a portion of the key is displayed Required Arguments: --server Optional Arguments: --hide_key box293_check_vmware.pl --check vCenter_License_Status --server 192.168.1.211 --hide_key OK: Licensed {Version: vCenter Server 5 Standard}
  • 27. vCenter_Name_Version Report the specified vCenter product Name and Version Required Arguments: --server box293_check_vmware.pl --check vCenter_Name_Version --server 192.168.1.211 VMware vCenter Server 5.1.0 build-1123961
  • 28. Guests (VMs) ● Guest_CPU_Info ● Guest_CPU_Usage ● Guest_Disk_Performance ● Guest_Disk_Usage ● Guest_Memory_Info ● Guest_Memory_Usage ● Guest_NIC_Usage ● Guest_Snapshot ● Guest_Status
  • 29. Guest_CPU_Info box293_check_vmware.pl ­­check Guest_CPU_Info ­­server 192.168.1.211 ­­guest "vSphere Management Assistant (vMA)" OK: {CPU (Cores Total: 4) (Cores Per Socket: 2) (Sockets: 2)} {Total MHz: 15,196 MHz} {Reservation MHz: 0 MHz} {Limit MHz: 12,236 MHz}|'Cores Total'=4 'Cores Per Socket'=2 'Sockets'=2 'CPU Total'=15196MHz 'CPU Reservation'=0MHz 'CPU Limit'=12236MHz Report Information about the Guests' CPU such as Cores, Total CPU, Reservation and Limit Returned as MHz by default Performance data can be useful for identifying when changes occurred, like adding CPU's or when a reservation or limit was defined NOTE: cpu_reservation and cpu_limit thresholds are either --warning OR --critical, NOT both Required Arguments: --guest Optional Arguments: --reporting_si CPU_Speed:<Hertz> --warning and --critical cpu_reservation:<Hertz>, cpu_limit:<Hertz> box293_check_vmware.pl --check Guest_CPU_Info --server 192.168.1.211 --guest "vSphere Management Assistant (vMA)" OK: {CPU (Cores Total: 4) (Cores Per Socket: 2) (Sockets: 2)} {Total MHz: 15,196 MHz} {Reservation MHz: 0 MHz} {Limit MHz: 12,236 MHz}|'Cores Total'=4 'Cores Per Socket'=2 'Sockets'=2 'CPU Total'=15196MHz 'CPU Reservation'=0MHz 'CPU Limit'=12236MHz * box293_check_vmware.pl ­­check Guest_CPU_Info ­­server 192.168.1.211 ­­guest "vSphere Management Assistant (vMA)" OK: {CPU (Cores Total: 4) (Cores Per Socket: 2) (Sockets: 2)} {Total MHz: 15,196 MHz} {Reservation MHz: 0 MHz} {Limit MHz: 12,236 MHz}|'Cores Total'=4 'Cores Per Socket'=2 'Sockets'=2 'CPU Total'=15196MHz 'CPU Reservation'=0MHz 'CPU Limit'=12236MHz
  • 30. Guest_CPU_Usage Report the specified Guests' CPU Usage Returned as MHz and ms by default Required Arguments: --guest Optional Arguments: --reporting_si CPU_Speed:<Hertz> Time:<Time> --warning and --critical cpu_free:<Hertz>, cpu_used:<Hertz>, cpu_ready_time:<Time> box293_check_vmware.pl --check Guest_CPU_Usage --server 192.168.1.211 --guest "vSphere Management Assistant (vMA)" OK: {Free: 15,157 MHz} {Usage: (Total: 39 MHz) (CPU 0: 10 MHz) (CPU 1: 3 MHz) (CPU 2: 9 MHz) (CPU 3: 1 MHz)} {Total Available: 15,196 MHz} {Ready Time: (Total: 48 ms) (CPU 0: 14 ms) (CPU 1: 10 ms) (CPU 2: 15 ms) (CPU 3: 10 ms)}|'Total CPU Free'=15157MHz 'Total CPU Usage'=39MHz 'CPU 0: Usage'=10MHz 'CPU 1: Usage'=3MHz 'CPU 2: Usage'=9MHz 'CPU 3: Usage'=1MHz 'Total Available'=15196MHz 'Total Ready Time'=48ms 'CPU 0 Ready Time'=14ms 'CPU 1 Ready Time'=10ms 'CPU 2 Ready Time'=15ms 'CPU 3 Ready Time'=10ms
  • 31. Guest_Disk_Performance Check the Disk Performance of a Guests' virtual disk(s) Metrics returned are: Disk Rate (Read and Write) as kBps Averaged Number of (Reads and Writes) (no thresholds checked) Latency depending on ESX(i) host version Required Arguments: --guest Optional Arguments: --reporting_si Disk_Rate:<Bytes Per Second>, Latency:<Time> --warning and --critical disk_rate:<Bytes Per Second>, disk_latency:<Time> box293_check_vmware.pl --check Guest_Disk_Performance --server 192.168.1.211 --guest "VMware vCenter Server Appliance" OK: [Hard disk 1 (scsi0:0) on 'ESXi 5.1' {Rate (Read:0 kBps / 0%)(Write:36 kBps / 100%)} {Averaged Number of (Reads:0) (Writes:2)} {Latency (Read:0 us) (Write:3,364 us)}], [Hard disk 2 (scsi0:1) on 'ESXi 5.1' {Rate (Read:0 kBps / 0%)(Write:9 kBps / 100%)} {Averaged Number of (Reads:0) (Writes:1)} {Latency (Read:0 us)(Write:407 us)}]|'Hard disk 1 (scsi0:0) Read Rate'=0kBps 'Hard disk 1 (scsi0:0) Write Rate'=36kBps 'Hard disk 1 (scsi0:0) Averaged Number of Reads'=0 'Hard disk 1 (scsi0:0) Averaged Number of Writes'=2 'Hard disk 1 (scsi0:0) Read Latency'=0us 'Hard disk 1 (scsi0:0) Write Latency'=3364us 'Hard disk 2 (scsi0:1) Read Rate'=0kBps 'Hard disk 2 (scsi0:1) Write Rate'=9kBps 'Hard disk 2 (scsi0:1) Averaged Number of Reads'=0 'Hard disk 2 (scsi0:1) Averaged Number of Writes'=1 'Hard disk 2 (scsi0:1) Read Latency'=0us 'Hard disk 2 (scsi0:1) Write Latency'=407us
  • 32. Guest_Disk_Usage Check the Disk Usage of a Guests' virtual disk(s) Returned as GB by default Returns overall usage of all virtual disks and well as individual virtual disk usage Includes provisioning type (Thin, Thick Eager, Thick Lazy), swap files, suspend files and CRITICAL: [Totals: {Disk Usage: 35.3 GB} {CRITICAL: Suspend File: [Totals: 4 GB} {Disk {All Usage: Snapshot 35.3 Space: GB} {Suspend snapshot files 4.1 File: For Thin GB}], provisioned disks, [Hard 4 you can trigger disk GB} thresholds 1 {All on how (scsi0:Snapshot Space: much free disk space 0) there on 'RAID1 4.1 is remaining (<total virtual (1)(3)' GB}], {Provisioning: [Hard disk size> disk - <current size 1 on datastore>) (scsi0:0) on 'RAID1 Disk Total threshold is triggered on the overall total, not each Thin} individual disk {Disk Capacity: (1)(3)' {Provisioning: 80.5 GB} {Size Thin} On Datastore: {Disk 27.2 GB} Capacity: {Free Space: 80.5 GB} 53.3 {Size GB / On 67% Datastore: (CRITICAL 27.2 <= 60)}]|'GB} {Free Total Space: Disk 53.3 Usage'=GB 35.3GB / 67% ('CRITICAL Suspend <= File'=60)}]|'4GB Total 'All Disk Snapshot Usage'=Space'=35.3GB 4.1GB 'Suspend 'Hard disk File'=1 4GB (scsi0:'All 0) Snapshot Capacity'=Space'=80.5GB 4.1GB 'Hard 'Hard disk disk 1 1 ((scsi0:scsi0:0) 0) Size Capacity'=On Datastore'=80.5GB 'Hard 27.2GB 'disk Hard 1 disk (scsi0:1 (scsi0:0) Size 0) On Free Datastore'=27.2GB Space'='Hard disk 53.3GB;;1 (scsi0:60 0) Free * Required Arguments: --guest Optional Arguments: --reporting_si Disk_Size:<Bytes> --warning and --critical disk_free:<Bytes>, disk_total:<Bytes> box293_check_vmware.pl --check Guest_Disk_Usage --server 192.168.1.211 --guest "Windows 8 Development" --critical disk_free:60 CRITICAL: [Totals: {Disk Usage: 35.3 GB} {Suspend File: 4 GB} {All Snapshot Space: 4.1 GB}], [Hard disk 1 (scsi0:0) on 'RAID1 (1)(3)' {Provisioning: Thin} {Disk Capacity: 80.5 GB} {Size On Datastore: 27.2 GB} {Free Space: 53.3 GB / 67% (CRITICAL <= 60)}]|'Total Disk Usage'=35.3GB 'Suspend File'=4GB 'All Snapshot Space'=4.1GB 'Hard disk 1 (scsi0:0) Capacity'=80.5GB 'Hard disk 1 (scsi0:0) Size On Datastore'=27.2GB 'Hard disk 1 (scsi0:0) Free Space'=53.3GB;;60
  • 33. Guest_Memory_Info Report Information about the Guests' Memory such as Total, Reservation and Limit box293_Returned as MB check_by default vmware.pl ­­check Guest_Performance Memory_data can be useful Info for identifying ­­server when changes 192.168.1.211 occurred, like adding ­­guest "Windows 8 Development" ­­warning memory_limit:3096 ­­critical memory_reservation:1024 CRITICAL: {Total: 4,096 MB} {Reservation MB: 0 MB (CRITICAL != 1,024)} {Limit MB: 4,096 MB (WARNING != 3,096)}|'Memory Total'=4096MB 'Memory Reservation'=0MB;;1024 'Memory Limit'=4096MB;3096 box293_check_vmware.pl ­­check Guest_Memory Memory_or when a reservation Info or limit ­­server was defined 192.168.1.211 ­­guest "Windows 8 Development" ­­warning memory_limit:3096 ­­critical memory_reservation:1024 CRITICAL: {Total: 4,096 MB} {Reservation MB: 0 MB (CRITICAL != 1,024)} {Limit MB: 4,096 MB (WARNING != 3,096)}|'Memory Total'=4096MB 'Memory Reservation'=0MB;;1024 'Memory Limit'=4096MB;3096 NOTE: memory_reservation and memory_limit thresholds are either –warning OR --critical, NOT both Required Arguments: --guest Optional Arguments: --reporting_si Memory_Size:<Bytes> --warning and --critical memory_reservation:<Bytes>, memory_limit:<Bytes> box293_check_vmware.pl --check Guest_Memory_Info --server 192.168.1.211 --guest "Windows 8 Development" --warning memory_limit:3096 --critical memory_reservation:1024 CRITICAL: {Total: 4,096 MB} {Reservation MB: 0 MB (CRITICAL != 1,024)} {Limit MB: 4,096 MB (WARNING != 3,096)}|'Memory Total'=4096MB 'Memory Reservation'=0MB;;1024 'Memory Limit'=4096MB;3096 *
  • 34. Guest_Memory_Usage Report the specified Guests' Memory Usage Returned as MB and kBps by default Memory Swapping is reported depending on ESX(i) host version Required Arguments: --guest Optional Arguments: --reporting_si Memory_Size:<Bytes>, Memory_Rate:<Bytes Per Second> --warning and --critical memory_free:<Bytes>, memory_consumed:<Bytes>, memory_ballooned:<Bytes>, memory_swap_rate:<Bytes Per Second>, memory_swapped:<Bytes> box293_check_vmware.pl --check Guest_Memory_Usage --server 192.168.1.211 --guest "vSphere Management Assistant (vMA)" OK: Guest Memory {Free: 3,468.0 MB} {Consumed: 628 MB} {Total: 4,096 MB} {Ballooned: 0 MB} {Overhead: 32.7 MB} {Active: 163.8 MB} {Shared: 0 MB} {Swap Rate (In: 0 kBps)(Out: 0 kBps)}|'Memory Free'=3468.0MB 'Memory Consumed'=628MB 'Memory Total'=4096MB 'Memory Ballooned'=0MB 'Memory Overhead'=32.7MB 'Memory Active'=163.8MB 'Memory Shared'=0MB 'Swapping Rate In'=0kBps 'Swapping Rate Out'=0kBps
  • 35. Guest_NIC_Usage Check the Guests' Network Interface Card(s) (NIC) usage Returned as kBps by default If the guest has more than one NIC then each NIC will be reported on individually Metrics returned are: Rate (Received and Transmitted) as kBps Packets (Received and Transmitted) (no thresholds checked) Required Arguments: --guest Optional Arguments: --reporting_si NIC_Rate:<Bytes Per Second> --warning and --critical nic_rate:<Bytes Per Second> box293_check_vmware.pl --check Guest_NIC_Usage --server 192.168.1.211 --guest "vSphere Management Assistant (vMA)" OK: {Rate (Rx:236 kBps / 96%)(Tx:11 kBps / 4%)} {Packets (Rx:3,669)(Tx:875)}|'Rate Rx'=236kBps 'Rate Tx'=11kBps 'Packets Rx'=3669 'Packets Tx'=875
  • 36. Guest_Snapshot Check if a guest has snapshots & trigger warning/critical states if snapshot is X days old If a guest has multiple snapshots, the oldest snapshot is checked You can target an individual Guest or multiple guests via a Host, Cluster or box293_check_vmware.pl ­­check Guest_Snapshot ­­server 192.168.1.211 ­­datacenter Box293 ­­warning snapshot_age:5 ­­critical snapshot_age:15 CRITICAL: ['nagiosxi' (Notes: Tester) (Age: 2)], ['Windows XP' (Notes: Test) (Age: 15 (CRITICAL >= 15))], ['Windows Server 2003 x86' (Notes: Test) (Age: 20 (CRITICAL >= 15))], ['Debian 7 x86' (Notes: Another Test) (Age: 15 (CRITICAL >= 15))], ['Linux Mint 15' (Notes: asdas) (Age: 13 (WARNING >= 5))], ['vMA' (Notes: before configuring) (Age: 12 (WARNING >= 5))] box293_check_vmware.pl ­­check Guest_Snapshot Datacenter ­­server 192.168.1.211 ­­datacenter Box293 ­­warning snapshot_age:5 ­­critical snapshot_age:15 CRITICAL: ['nagiosxi' (Notes: Tester) (Age: 2)], ['Windows XP' (Notes: Test) (Age: 15 (CRITICAL >= 15))], ['Windows Server 2003 x86' (Notes: Test) (Age: 20 (CRITICAL >= 15))], ['Debian 7 x86' (Notes: Another Test) (Age: 15 (CRITICAL >= 15))], ['Linux Mint 15' (Notes: asdas) (Age: 13 (WARNING >= 5))], ['vMA' (Notes: before configuring) (Age: 12 (WARNING >= 5))] Required Arguments: --guest or --host or --cluster or --datacenter Optional Arguments: --warning and --critical snapshot_age:<Day(s)> box293_check_vmware.pl --check Guest_Snapshot --server 192.168.1.211 --datacenter Box293 --warning snapshot_age:5 --critical snapshot_age:15 CRITICAL: ['nagiosxi' (Notes: Tester) (Age: 2)], ['Windows XP' (Notes: Test) (Age: 15 (CRITICAL >= 15))], ['Windows Server 2003 x86' (Notes: Test) (Age: 20 (CRITICAL >= 15))], ['Debian 7 x86' (Notes: Another Test) (Age: 15 (CRITICAL >= 15))], ['Linux Mint 15' (Notes: asdas) (Age: 13 (WARNING >= 5))], ['vMA' (Notes: before configuring) (Age: 12 (WARNING >= 5))] *
  • 37. Guest_Status Check the status of a guest including Power State, Uptime, VMware Tools Version and Status, IP Address, Hostname, ESX(i) Host Guest Is Running On, Consolidation State and Guest Version Warning or critical states can be triggered for Power State, Uptime, Consolidation State and VMware Tools Status. Required Arguments: --guest Optional Arguments: --warning and --critical guest_uptime:<Day(s)> --guest_consolidation_state --guest_power_state --guest_tools_version_state box293_check_vmware.pl --check Guest_Status --server 192.168.1.211 --guest "vSphere Management Assistant (vMA)" OK: {State: poweredOn} {Uptime: 13 d} {Tools (Version: 2147483647) (Status: guestToolsUnmanaged)} {IP Address: 10.25.6.22} {Guest Hostname: vmademo} {Host: esxi001.box293.local} {Guest Version: vmx-07}
  • 38. Hosts ● Host_CPU_Info ● Host_CPU_Usage ● Host_License_Status ● Host_Memory_Usage ● Host_OS_Name_Version ● Host_pNIC_Status ● Host_pNIC_Usage ● Host_Status ● Host_Storage_Adapter_Info ● Host_Storage_Adapter_Performance ● Host_Switch_Status ● Host_vNIC_Status
  • 39. Datastore_Performance Check the performance of a specific Datastore Metrics returned are: box293_Datastore check_Rate (Read and vmware.Write) as kBps pl ­­check Datastore_Number of (Reads Performance and Writes) (no thresholds ­­server checked) Device Latency (Read and Write) as ms 192.168.1.211 ­­host 192.168.1.210 ­­name "ESXi 5.1" OK: Datastore 'ESXi 5.1' {Rate (Read:32 kBps / 21%) (Write:122 kBps / 79%)} {Number of (Reads:20) (Writes:109)} {Latency (Read:0 ms)(Write:1 ms)}|'Read Rate'=32kBps 'Write Rate'=122kBps 'Number of Reads'=20 'Number of Writes'=109 'Read Latency'=0ms 'Write Latency'=1ms box293_check_vmware.pl ­­check Datastore_Performance ­­server 192.168.1.211 ­­host 192.168.1.210 ­­name "ESXi 5.1" OK: Datastore 'ESXi 5.1' {Rate (Read:32 kBps / 21%) (Write:122 kBps / 79%)} {Number of (Reads:20) (Writes:109)} {Latency (Read:0 ms)(Write:1 ms)}|'Read Rate'=32kBps 'Write Rate'=122kBps 'Number of Reads'=20 'Number of Writes'=109 'Read Latency'=0ms 'Write Latency'=1ms Required Arguments: --name --host (the host that the datastore is connected to) Optional Arguments: --reporting_si Datastore_Rate:<Bytes Per Second>, Latency:<Time> --warning and --critical datastore_rate:<Bytes Per Second>, datastore_latency:<Time> box293_check_vmware.pl --check Datastore_Performance --server 192.168.1.211 --host 192.168.1.210 --name "ESXi 5.1" OK: Datastore 'ESXi 5.1' {Rate (Read:32 kBps / 21%)(Write:122 kBps / 79%)} {Number of (Reads:20) (Writes:109)} {Latency (Read:0 ms)(Write:1 ms)}|'Read Rate'=32kBps 'Write Rate'=122kBps 'Number of Reads'=20 'Number of Writes'=109 'Read Latency'=0ms 'Write Latency'=1ms *
  • 40. Example Graphs
  • 41. Datastore_Usage Check the Usage of a specific Datastore Returned as GB by default Required Arguments: --name Optional Arguments: --reporting_si Datastore_Size:<Bytes> --warning and --critical datastore_free:<Bytes>, datastore_used:<Bytes> box293_check_vmware.pl --check Datastore_Usage --server 192.168.1.211 --name "ESXi 5.1" OK: Datastore 'ESXi 5.1' {Free Space: 67.3 GB} {Used Space: 67.7 GB} {Capacity: 135 GB}|'Free Space'=67.3GB 'Used Space'=67.7GB 'Capacity'=135GB
  • 42. Host_CPU_Info Report Information about the Hosts' CPU such as Model, Cores and Total CPU Returned as GHz by default Required Arguments: --host (if connected via a vCenter server) Optional Arguments: --reporting_si CPU_Speed:<Hertz> box293_check_vmware.pl --check Host_CPU_Info --server 192.168.1.211 --host 192.168.1.210 --reporting_si CPU_Speed:MHz OK: AMD A10-5800K APU with Radeon(tm) HD Graphics, 4 cores @ 3799MHz
  • 43. Host_CPU_Usage Report the specified Hosts' CPU Usage Returned as GHz by default Required Arguments: --host (if connected via a vCenter server) Optional Arguments: --reporting_si CPU_Speed:<Hertz> --warning and --critical cpu_free:<Hertz>, cpu_used:<Hertz> box293_check_vmware.pl --check Host_CPU_Usage --server 192.168.1.211 --host 192.168.1.210 OK: Host CPU {Free: 12.9 GHz} {Used: 2.3 GHz} {Total: 15.2 GHz}|'CPU Free'=12.9GHz 'CPU
  • 44. Host_License_Status Reports the specified Hosts license status along with the license key If the host is in evaluation mode and has less than 24 hours remaining a CRITICAL state is returned otherwise a WARNING state is returned When host is queried using an account that has read only privileges, only a portion of the key is displayed Required Arguments: --host (if connected via a vCenter server) Optional Arguments: --hide_key box293_check_vmware.pl --check Host_License_Status --server 192.168.1.211 --host 192.168.1.210 OK: Licensed {Version: VMware vSphere 5 Enterprise Plus}{Key: ABCDE-#####-#####-#####-VWXYZ}
  • 45. Host_Memory_Usage Report the specified Hosts' Memory Usage Returned as GB by default Required Arguments: --host (if connected via a vCenter server) Optional Arguments: --reporting_si Memory_Size:<Bytes> --warning and --critical memory_free:<Bytes>, memory_used:<Bytes> box293_check_vmware.pl --check Host_Memory_Usage --server 192.168.1.211 --host 192.168.1.210 OK: Host Memory {Free: 9.2 GB} {Used: 22.8 GB} {Total: 32 GB}|'Memory Free'=9.2GB 'Memory Used'=22.8GB 'Memory Total'=32GB
  • 46. Host_OS_Name_Version Report the specified Hosts' product Name and Version Required Arguments: --host (if connected via a vCenter server) box293_check_vmware.pl --check Host_OS_Name_Version --server 192.168.1.211 --host 192.168.1.210 OK: VMware ESXi 5.1.0 build-1065491
  • 47. Host_pNIC_Status Check the Status of the Hosts' Physical Network Interface Card(s) (pNIC) box293_All pNICs are check_returned by vmware.default however pl you ­­check can target specific pNIC(s) Host_If any pNIC pNIC_is disconnected Status it will ­­server trigger a CRITICAL 192.168.1.211 state ­­host 192.168.1.210 CRITICAL: NICs [Total: 3, Connected: 1, Disconnected: 2], [vmnic1 on Local vSwitch 'vSwitch0', Driver: e1000e, NOT Connected], [vmnic0 on Local vSwitch 'vSwitch0', Driver: r8168, NOT Connected], [vmnic2 on Local vSwitch 'vSwitch0', Driver: e1000e, 1,000 MB, Full Duplex] box293_check_vmware.pl ­­check Host_pNIC_Status ­­server 192.168.1.211 ­­host 192.168.1.210 CRITICAL: NICs [Total: 3, Connected: 1, Disconnected: 2], [vmnic1 on Local vSwitch 'vSwitch0', Driver: e1000e, NOT Connected], [vmnic0 on Local vSwitch 'vSwitch0', Driver: r8168, NOT Connected], [vmnic2 on Local vSwitch 'vSwitch0', Driver: e1000e, 1,000 MB, Full Duplex] Required Arguments: --host (if connected via a vCenter server) Optional Arguments: --name --nic_state --nic_speed --nic_duplex box293_check_vmware.pl --check Host_pNIC_Status --server 192.168.1.211 --host 192.168.1.210 CRITICAL: NICs [Total: 3, Connected: 1, Disconnected: 2], [vmnic1 on Local vSwitch 'vSwitch0', Driver: e1000e, NOT Connected], [vmnic0 on Local vSwitch 'vSwitch0', Driver: r8168, NOT Connected], [vmnic2 on Local vSwitch 'vSwitch0', Driver: e1000e, 1,000 MB, Full Duplex] *
  • 48. Host_pNIC_Usage Check the Hosts' Physical Network Interface Card(s) (pNIC) usage Returned as kBps by default All pNICs are returned by default however you can target specific pNIC(s) Metrics returned are: Rate (Received and Transmitted) as kBps Packets (Received and Transmitted) (no thresholds checked) ESX(i) host version 5.0.0 and later reports Packet Errors (Received and Transmitted) Required Arguments: --host (if connected via a vCenter server) Optional Arguments: --name --reporting_si NIC_Rate:<Bytes Per Second> --warning and --critical nic_rate:<Bytes Per Second>, packet_errors:<Number> box293_check_vmware.pl --check Host_pNIC_Usage --server 192.168.1.211 --host 192.168.1.210 --name vmnic2 --reporting_si NIC_Rate:Bps OK: [vmnic2 {Rate (Rx:2,048 Bps / 50%)(Tx:2,048 Bps / 50%)} {Packets (Rx:320)(Tx:283)} {Packet Errors (Rx:0)(Tx:0)}]|'vmnic2 Rate Rx'=2048Bps 'vmnic2 Rate Tx'=2048Bps 'vmnic2 Packets Rx'=320 'vmnic2 Packets Tx'=283 'vmnic2 Packet Errors Rx'=0 'vmnic2 Packet Errors Tx'=0 *
  • 49. Example Graphs
  • 50. Host_Status Check the overall status of a Host and report any known issues Required Arguments: --host (if connected via a vCenter server) Optional Arguments: --exclude_issue box293_check_vmware.pl --check Host_Status --server 192.168.1.211 --host 192.168.1.210 WARNING: Host has a YELLOW status {Local Tech Support Mode ENABLED, Remote Tech Support Mode ENABLED}
  • 51. Host_Storage_Adapter_Info Report Information about the Hosts' Storage Adapter(s) such as Model, Device Name and Driver Name (driver version not available at this point in time) Required Arguments: --host (if connected via a vCenter server) Optional Arguments: --name box293_check_vmware.pl --check Host_Storage_Adapter_Info --server 192.168.1.211 --host 192.168.1.210 OK: [LSI 3ware 9750 (vmhba1) {Driver: 3w-sas}], [AMD Hudson SATA Controller [AHCI Mode] (vmhba0) {Driver: ahci}]
  • 52. Host_Storage_Adapter_Performance Check the performance of a specific Hosts' Storage Adapter Metrics returned are: Rate (Read and Write) as kBps Average Number of (Reads and Writes) (no thresholds checked) Latency Total (Read and Write) as ms Required Arguments: --host (if connected via a vCenter server) --name Optional Arguments: --reporting_si HBA_Rate:<Bytes Per Second>, Latency:<Time> --warning and --critical hba_rate:<Bytes Per Second>, hba_latency:<Time> box293_check_vmware.pl --check Host_Storage_Adapter_Performance --server 192.168.1.211 --host 192.168.1.210 --name vmhba1 OK: [LSI 3ware 9750 (vmhba1) {Rate (Read:493 kBps / 23%)(Write:1,720 kBps / 77%)} {Averaged Number of (Reads:81) (Writes:168)} {Total Latency (Read:2 ms)(Write:0 ms)}]|'vmhba1 Rate Read'=493kBps 'vmhba1 Rate Write'=1720kBps 'vmhba1 Average Number of Reads'=81 'vmhba1 Average Number of Writes'=168 'vmhba1 Latency Total Read'=2ms 'vmhba1 Latency Total Write'=0ms *
  • 53. Example Graphs
  • 54. Host_Switch_Status Check the Status of a Hosts' vSwitch or Distributed Switch including all pNICs that are connected to the switch Required Arguments: box293_check_vmware.pl ­­check Host_Switch_Status ­­server 192.168.1.211 ­­host 192.168.1.22 ­­name dvSwitch ­­mtu 9000 CRITICAL: [dvSwitch {Distributed}, Ports {Total: 256} {Available: 248}, MTU is 1500 but should be 9000, NICs: {Total: 2, Connected: 2} {vmnic0, Driver: e1000, 1,000 MB, Full Duplex} {vmnic1, Driver: e1000, 1,000 MB, Full Duplex}] box293_check_vmware.pl ­­check Host_--host (if connected Switch_via a Status vCenter server) ­­server 192.168.1.211 ­­host 192.168.1.22 ­­name dvSwitch ­­mtu 9000 CRITICAL: [dvSwitch {Distributed}, Ports {Total: 256} {Available: 248}, MTU is 1500 but should be 9000, NICs: {Total: 2, Connected: 2} {vmnic0, Driver: e1000, 1,000 MB, Full Duplex} {vmnic1, Driver: e1000, 1,000 MB, Full Duplex}] Optional Arguments: --mtu --name --nic_state --nic_speed --nic_duplex box293_check_vmware.pl --check Host_Switch_Status --server 192.168.1.211 --host 192.168.1.22 --name dvSwitch --mtu 9000 CRITICAL: [dvSwitch {Distributed}, Ports {Total: 256} {Available: 248}, MTU is 1500 but should be 9000, NICs: {Total: 2, Connected: 2} {vmnic0, Driver: e1000, 1,000 MB, Full Duplex} {vmnic1, Driver: e1000, 1,000 MB, Full Duplex}] *
  • 55. Host_vNIC_Status Check the Status of the Hosts' Virtual Network Interface Card(s) (vNIC) and report the role(s) All vNICs are returned by default however you can target specific vNIC(s) Required Arguments: --host (if connected via a vCenter server) Optional Arguments: --mtu --name box293_check_vmware.pl --check Host_vNIC_Status --server 192.168.1.211 --host 192.168.1.210 OK: [{Management Network (vmk0 on Local vSwitch 'vSwitch0')} {MTU: 1,500} {Roles: Management}], [{VMkernel test (vmk1 on Local vSwitch 'vSwitch1')} {MTU: 1,500} {Roles: vMotion, Management, Fault Tolerance}]
  • 56. BREATHE! Pause to take a breath Surely I must be finished Just one more thing ...
  • 57. Introducing …
  • 58. Nagios XI VMware Wizard ● Released Soon ● A Configuation Wizard for Nagios XI ● Queries your VMware Virtualization Infrastructure ● Presents you with all the objects that you can monitor ● Makes adding objects to XI quick, painless with minimal keyboard interaction!
  • 59. Quick Break
  • 60. Conclusion box293_check_vmware is: • An offloaded plugin for Nagios • Easy to implement • Feature Rich • Wizard for Nagios XI available soon • Well documented, has an easy to understand manual Drs Orders: ● Implement ASAP!
  • 61. Great Plugin with many Options and powerful Stats - Marvin Holze Documentation was GREAT! - Kevin Oswald A qualified VMware and Nagios systems administrator will have no issue getting things up and running with relative ease. - John Chivian Thank you for your effort you put into this amazing plugin. We are using this plugin to monitor our vmware infrastructure and it is working great so far. - Seyfidin Hamraoui I’ve been testing your vmware plugin, which has been a big help, many thanks for taking the time to develop it. - Paul Mason I just installed and configured your vMA software and now monitoring our vCenter with it. Manual was really clear and so it was easily done. - Vincent Palmboom I've only used 2 VMware plugins, but Box's is the best of the 2. We recently switched to it and I haven't had any reason to look for another one. - snapon_admin Still by far the best documented plugin I've seen, and works as advertised. - fusfeld
  • 62. The End Troy Lea tlea@nagios.com Twitter: @box293

Related Documents