cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Orion Server 2020.2 - High Availability (HA) Standby templates

These templates are designed for SAM 2020.2 deployments that leverage SolarWinds High Availability (HA). Please note that these templates are not part of the standard SAM 2020.2 release that includes fully tested, official templates. See the disclaimer for details. 

Disclaimer: Any custom templates, scripts or other content posted in THWACK are provided as a suggestion or recommendation for your internal use. This is not part of the SolarWinds software purchased from SolarWinds, and the information set forth herein may come from third party customers. Your organization should internally review and assess to what extent, if any, such custom templates or scripts will be incorporated into your environment. Any custom content obtained on THWACK is provided to you “AS IS” without indemnification, support, or warranty of any kind, express or implied. You elect to utilize custom templates or scripts at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Attachments
Comments

Thanks!

As either node in the main pool or the APE pool could be standby or active at any time based on failovers, do these templates account for that?  I ask because the name of the templates sounds as though they would only be applied to the node that is currently in standby which, as previously stated, could be either node in the pool.

@cmazko 

Are you able to answer the question above from last Thursday?  Sorry about forgetting to tag you in that reply.

@kbswcon  The "unofficial" Orion Server 2020.2 templates referenced in this thread have not been formally tested with Orion Platform 2019.4. I checked with one of our top SAM Support reps, who said that those templates should work on earlier versions though, starting with 2017.3.

The SAM Application Engineer (AE) that created those templates said he originally created them in SAM 2019.4, then carried them over to 2020.2. Also, no major database changes occurred between those versions that would impact the templates, which mostly monitor services anyway. 

Hope this is helpful. If you decide to assign them to nodes (or maybe use the Test functionality instead), it would be great if you could post your feedback here. 

@cmazko 

I wasn't asking about 2019.4.  We're running 2020.2.  I was asking about the nature of the "standby" templates when using HA.  As either node in the pool may assume the role of active or standby, if these templates are only for the poller currently serving as standby, that would mean that every time you failover that you'd need to also remove/swap application monitors.  Make sense?

@kbswcon Sorry, I mixed up this thread with your 2019.4 testing question in the other thread, https://thwack.solarwinds.com/t5/SAM-Documents/Orion-Server-2020-2-templates/ta-p/594548. I'll see what I can find out about your active/standby question.

@kbswcon  Here is the input I received from the SAM AE in response to your latest question... 

Apply the Main Polling Engine template to both Main Polling Engine pairs, and then apply the Additional Polling Engine (APE) HA template to the APE HA pairs. It shouldn't matter which one is active or standby. If issues occur, tweak the template accordingly. The only service that might have an issue is the SW Orion Module Engine service -- it should be Up on Standby, if it's included.

The following screenshot shows Orion Server 2020.2 - Main Poller HA Standby. The APE will look similar but with SSL because only the Main Polling Engine has RabbitMQ; APEs don’t need it.


OrionServer2020-2_MainPollerHAStandby.png

 

@cmazko 

Forgive the additional questions, but I want to ensure that I understand this correctly.  Are you saying *not* to use the original Main Poller and Additional Polling Engine 2020.2 templates from the blog post but *instead* use these standby templates on each node in the pools?  If so, are we losing any monitoring as a result?  I ask this question because per your screenshot, the majority of component monitors are disabled and this seems like we're just silencing the alerts versus intelligently handling monitoring based on the current role of the node (active or standby).

@kbswcon  I may need a few days to get back to you. The AE is in a different timezone, plus we're on top of a holiday weekend.

@kbswcon  ...and I just heard back from the AE. 

"You can continue to use the three new Orion Server 2020.2 templates, and then be able to -- additionally -- apply the HA templates to both of the standby nodes so they're being monitored for the HA side.

So we know before any future failure that it should fail over successfully. As in the required minimum services required to handle a failover are working as expected if and when needed.

As for full HA support after failover, thats likely not supported as if now, as in pick Primary Active and aim to have it active as much as possible. If standby occurs should work to keep that minimum before being able to revert to PREFERRED Primary active server in a HA pair." 

 

@cmazko 

Thank you for checking on this.  I appreciate your time and assistance.

Version history
Revision #:
3 of 3
Last update:
3 weeks ago
Updated by: