One of our customers have multiple clusters. And being one company, they asked if Alerter can be configured for getting data from multiple clusters?
Is there a way around?
Depending on the amount of elements of interest, it might be a scenario for element replication (in case clusters cannot be unified).
Or perhaps some SNMP forwarding from one DMS to another connected to the alerter?
I believe SLAlerter was designed to run as a single instance tied to one cluster - not sure if this chnages with any more recent version.
But I've done a quick test and where Cube allows to launch more then one instance, this doesn't seem possible for alerter - not the version I've tried in any case:
So the workaround could be running 2 Alerters from two different clients.
SLAlerter used as one instance can connect via the "Edit Account" settings
This section explains how to point Alerter to a different DMA:
https://docs.dataminer.services/dataminer/DataMiner_Tools/DMS_Alerter/Configuring_Alerter/Connecting_Alerter_to_another_DMS.html
yet the operation triggers a re-connect, and I'm receiving info from one DMS only in my test set-up:
HTH
Thanks, but how can I Forward the alarms via SNMP from one Cluster to another.
Lets say Alerter is connected to DMA_X and I want DMA_Z to forward the alarms to DMA_X. so it can show in the alerter?
Are users across the systems the same group with same privileges?