![]() |
![]() |
Subject: | DeviceExistsErrors: Ip %s exists on device |
Author: | Austin Culbertson |
Posted: | 2018-10-10 13:29 |
Subject: | RE: DeviceExistsErrors: Ip %s exists on device |
Author: | Jane Curry |
Posted: | 2018-10-11 06:02 |
Subject: | RE: DeviceExistsErrors: Ip %s exists on device |
Author: | Austin Culbertson |
Posted: | 2018-10-12 11:18 |
My hope was that I could have 3 devices in monitoring:
The Virtual IP of the Cluster
Device A (member #1 of cluster)
Device B (member #2 of cluster)
I have recently changed our zModelerLock zProperty to Lock all processes from deletion, because we ran into many scenarios where a process would be legitimately down and the scheduled remodel would remove the process. Now that these are locked from deletion, however, I have remembered that some processes are (for lack of a better term) 'passed' from one cluster to another. i.e. when it stops on Device A, Device B starts running that process.
I imagine there are a few solutions to this, but the first and 'easiest' I considered clearly isn't viable due to not being able to have duplicate IPs in Zenoss. Is there any simple programmatic solution to this that I might not be aware of? i.e. a ZenPack or other function native to Zenoss?
Subject: | RE: DeviceExistsErrors: Ip %s exists on device |
Author: | Jane Curry |
Posted: | 2018-10-15 10:49 |
Subject: | RE: DeviceExistsErrors: Ip %s exists on device |
Author: | Austin Culbertson |
Posted: | 2018-10-16 15:48 |
Subject: | RE: DeviceExistsErrors: Ip %s exists on device |
Author: | Dennis Stackley |
Posted: | 2018-10-17 12:27 |
< |
Previous Unable to download install-zenoss-hbase-24.0.8.run |
Next zencommand suddenly using high amounts of memory |
> |