This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.
Requires PythonCollector ZenPack, ZenPackLib ZenPackCompatible with Zenoss Resource Manager 6.5.0, 6.6.0, and Zenoss Cloud
This ZenPack provides support for monitoring VMware NSX-T. Modeling and monitoring of devices placed in the /VMware/NSX device class is performed using the NSX-T API by executing queries and parsing the output.
The NSX ZenPack provides:
The following entities will be automatically discovered. The attributes and collections will be updated on Zenoss's normal remodeling interval which defaults to every 12 hours.
NSX-T Virtual Switches Attributes: ID of the virtual switch in compute manager, Discovered Nodes, Description, ID of the compute manager, Portgroup UUID, Tags, Uplink Port Names, Uplink portgroup Relations: NSX-T Compute Manager
The installation of this ZenPack will create the device class /VMware/NSX. This new device class will provide five new zProperties zNSXUsername, zNSXPassword, zNSXPort, zNSXSSL, and zNSXConcurrentHTTP
The following procedure assumes that credentials have been set.
Enter the following information in the dialog:
Monitoring plugin collects System Events from NSX-T Manager and shows them as Zenoss Events with the same time and severity.
Once the event is sent, it will not be sent again. If the user clears the event, it will not reappear again. There’s no automatic mechanism to clear system events, as they can not be cleared from NSX manager and do not have expire date, therefore the user is to close new events manually from Zenoss UI.
Installing this ZenPack will add the following items to your Zenoss system.
Note: disk_space_total and disk_space_used values may be different from the values in NSX UI. Zenoss takes these values from the NSX API, but NSX UI doesn't. NSX UI iterates though file_systems field and sums the total_space of each file system with some inaccuracy (NSX UI uses 1000 as base, not 1024, for converting kbytes to other units)