Ad Widget

Collapse

VMWare Hypervisors with multiple interfaces

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tmroberts
    Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Jan 2017
    • 73

    #1

    VMWare Hypervisors with multiple interfaces

    I am trying to set up monitoring on 5 different VMWare clusters. I have the basic out of the box template working, but we need more monitoring than what comes out of the box. The Hypervisors also need to have some Dell Hardware (iDRAC) or UCS monitoring added but it requires an SNMP interface with an expanded hostname (i.e. hostname-drac.domain.name). I have found a handful of posts on the bug fix pages that talk about this but nothing is being done about it. I'm wondering if anyone has successfully implemented something sort of work around like this. Having the hypervisor discovery/creation is awesome. It saves a huge amount of time. But the only way i can see getting ALL of the monitoring we need from them is to create the hypervisors manually and I really don't want to go down that road.
  • LenR
    Senior Member
    • Sep 2009
    • 1005

    #2
    On a windows or linux host running dell openmanage, you can query SNMP on the OS primary IP, the iDRAC address is in mib MIB-Dell-10892::bmcLANInterfaceIPAddress.1.1.1. I don't think VMware enables snmp or openmange in the OS stack. The SNMP interface can be an IP address, the requirement for an expanded host name should like a local standard (and that's not a bad idea).

    Zabbix provided VM monitoring should pick up all the hypervisors after given access to the cluster. With your naming standard, you could write a Zabbix API script to process the hypervisors and if host doesn't the snmp interface host-drac.domain.name, add it and link a template.

    Comment


    • tmroberts
      tmroberts commented
      Editing a comment
      That's the issue.... with a discovered hypervisor (created from a host prototype) I can't add additional interfaces or even link additional templates. I can create the hypervisors as actual hosts all day long, but that defeats the purpose of the discovery process
  • LenR
    Senior Member
    • Sep 2009
    • 1005

    #3
    Maybe create the iDRAC as a separate host with an API script, it's a little messy, but it would be monitored. If the iDRAC are on a dedicated subnet, could you use network discovery?

    Comment


    • tmroberts
      tmroberts commented
      Editing a comment
      we may actually end up doing just that. Thanks for the advice.
Working...