InstallationGetting Started

Expand all | Collapse all

Add multiple devices that have the same IP

  • 1.  Add multiple devices that have the same IP

    Posted 05-20-2019 01:41 PM

    Some background:
    Our Oracle DB's all have a DNS alias that points to the server IP where the DB runs.
    When a DB moves to another server, the DNS alias is changed, and all applications connect again to the DB without reconfiguration.

    We want to monitor these DB's with Zenoss.
    Adding the first DB works fine (ip is resolved )
    Adding a second DB that runs on the same host doesn't work, Zenoss give a message telling the DB already exists in Zenoss.
    But this is not the case, the IP where it runs is already used in Zenoss.

    How can I solve this issue.. so adding multiple devices that share the same IP... and keeping the flexibility that when the DB moves (and the DNS alias changes), that Zenoss monitoring moves along.

    Any idea how to resolve this?



  • 2.  RE: Add multiple devices that have the same IP

    Posted 05-23-2019 09:34 AM
    Well, you cannot have more than one device sharing the same manage IP (Unless you are using MultiRealm ZP).

    Are you adding these "Oracle DB's" as individual devices in Zenoss? Are they actually individual devices? Are you using a special ZenPack to monitor or what device class are you using?

    Does the DNS alias change IPs or are you saying the name of the alias changes? becomes or switches from to


  • 3.  RE: Add multiple devices that have the same IP

    Posted 05-23-2019 01:23 PM
    Hi Jay,

    With our previous monitoring product, the IP was not the unique key in th system to manage devices.
    Because of that we expected Zenoss to work in the same way.
    Luckily we found a way arround it.

    We use the Oracle Database Zenpack. This we can configure to connect to a DB and monitor it.
    Now, I made the fault to use the DB alias as the device (old habbit).
    But, for Zenoss I have to take the linux server where the database runs to be the device (we are not really interested in the OS monitoring for these servers).

    From the documentation of the zenpack it was not clear to me that the zenpack could monitor multiple DB's.
    The configuration property zConnectionStrings alows to add multiple connection strings (hence the 's' at the end).
    I overlooked this, making me think that the zenpack was only be able to monitor 1 DB.

    Now, some automation using the api will help us in case a DB moves to another server.

    Thanks for thinking with me.
    As a remark... maybe the zenpack documentation can explain it better that the zConnectionStrings can contain multiple connectionstring.
    Don't know yet how much DB's we can monitor with it, but we will find out soon :-)