Gartner Market Guide for IT Infrastructure Monitoring Tools
LIVE WEBINAR: 2/27, 1 p.m. CST
Google and Zenoss will bring contemporary applications of state-of-the-art AI and machine learning technologies to life.
Zenoss is the only enterprise monitoring solution certified Nutanix Ready - Integrated.
Learn. Discuss. Participate.
Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Gartner Market Guide for IT Infrastructure Monitoring Tools
Zenoss Blog
ZenPack SDK
Customers for Life
At Zenoss, our customers are at the core of everything we do.
This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.
The ZenPacks.zenoss.MultiRealmIP ZenPack extends the modeling, monitoring, and event management features of Zenoss platform to accommodate overlapping IP namespaces.
Note: This ZenPack is not installed when Zenoss platform is installed. To download it, visit the Zenoss Support site.
With this ZenPack, Zenoss platform can prefix a realm identifier to the IP addresses of a network, enabling unified monitoring.
There are two primary use cases for using multi-realm IP management.
The essential workflow for creating and using IP Realms is that first you need to create the IP realms and then associate these realms with a collector. The associations between IP Realms and actual devices is made automatically by the device's association with the collector. All devices on a collector are associated with the realm for that collector.
Before setting up multi-realms, you must delete all Zenoss platform networks. (These are automatically recreated.)
Prerequisite | Restriction |
---|---|
Product | Zenoss platform 4.x, 5.x |
Required ZenPacks | ZenPacks.zenoss.DistributedCollector, ZenPacks.zenoss.MultiRealmIP |
The following diagram lays out an example setup. It has a central Zenoss platform server in the 10.10.10.0/24 network. The network local to the server is considered the default network within the system. The default network is treated exactly the same as a Zenoss platform system without this ZenPack installed.
There are two other networks shown (r1 and r2) which are behind a firewall and have the same IP space 192.168.0.0/24. Each realm has a distributed collector located within it. The collector can be accessed from the Zenoss platform server using a IP translation from the firewall to map the address accessible from in front of the firewall to an address behind the firewall. Remote collectors in a multi-realm setup must be accessible from the central server using SSH.
Example IP Realm
Set up Zenoss platform following the example system described previously.
Tip: If you do not have overlapping IP space this example can be created using collectors within the same network. To create the example, add a machine multiple times once per collector, making sure to change the name of the device as it is added. The result is similar to a real realm setup.
Under multi-realm IP networks, device names must be unique even though the IP addresses will overlap.
On certain server configurations, if a distributed collector is configured, a "zenpack command failed" error occurs when installing this ZenPack. If you encounter this error, then run the following grant (as MySQL root):
grant super on *.* to 'zenoss'@'{FQDN_of_Zenoss_host}' identified by 'zenoss';
where the first 'zenoss' is the user account that Zenoss platform uses to access MySQL, and the second 'zenoss' is that account's password.
As another test try searching by IP from the top-level search. Two devices will be returned -- one within each realm.
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.