Im not quite sure i understand what your asking.
Why would Control-M be monitoring your SolarWinds Server?
Or, are you saying that you send your Control-M traps to SolarWinds which then alerts?
We would need to know your environment setup for SolarWinds to get an understanding of what you have and what i can advise on.
Yes, my question is "Or, are you saying that you send your Control-M traps to SolarWinds which then alerts?"
So whenever we reboot the Solarwinds server( on which control alerts are mapped, ) for patching or any activities. We have to monitor the manually Control M Jobs. Please suggest me how to create a redundancy for Solarwinds servers.
In my environment we do the same thing, i tend to reboot my SolarWinds server for patching etc during the day as we have a team of operators that work with and monitor Control-M from 7am-10pm.
A reboot of SW if its virtual like mine doesn't take any longer than a couple of minutes or so. When SolarWinds is rebooting its just something we live with for a few minutes which isn't an issue for us.
You can use SolarWinds HA functionality if you so wish to create a failover SolarWinds node
Although i believe there are additional license costs for this.
Let me explain, what process we are using for control m alerts.:
Control M sends TRAP messages if there are any job failures or if Jobs are delayed. Production-related Trap messages are sent to the SolarWinds Poller XYZ SERVER and the Test Related Trap Messages are sent to Poller ABCD SERVER. Destination of the Trap messages is set at ControlM application level by Control M team. If there are any issues with any of these pollers then the tickets will not be created. In case of permanent failure of these Polling servers, then Control M team need to send the trap message to different Poller, which requires application bounce from their end. SolarWinds Control M scripts are designed to work from any of the NUMBERS OF Pollers, so even if ControlM team changes the server, we don’t need to change any configuration at SolarWinds level. To avoid this issue we setup the VIP for all pollers as swpollers.hersheys.com, but the messages from this VIP was delayed and sometimes it was missing out sending the required information due to this delay, hence the VIP was not used.
But here the problem is that we don't want any outage while performing any kind of activity either patching or server down due to any reason, we want a backup so that if any issues happen on the poller, an alert should be bounce automatically through different poller. Please let me know how can we create a backup or do we have solutions for the same.
Im also using Control-M here where i work, we are using Control-M 9 and the latest version of SolarWinds SAM.
One of the core functionalities that the SolarWinds system is missing is being able to alert based on incoming SNMP traps using the alert manager and i have raised this with them plenty of times.
You'll also see lots of feature requests for this which have been ongoing for years but the functionality has never been added to SolarWinds
We ended up developing our own alerting, we have a custom database in which we pull certain information into from SolarWinds via PowerShell using the SolarWinds and BMC Control-M API, do a bunch of magic and that then utilizes our SMS gateway for out of hours SMS alerting.
This isn't the best way or the easiest thing to keep up to date but unfortunately SolarWinds doesn't offer the functionality that we need so we just built our own mechanism.
stevenwhunt Maybe you can shed some light on the SNMP trap alerting via alert manager feature? i know people have been crying out for it for a long time including myself when i met you at the VMUG in Birmingham last year.