Configuring VIP versus servers for MTS

Highlighted
05 Base Camper

Configuring VIP versus servers for MTS

We have Pulse configured and working for a single server within a AIX cluster; however, looking for examples to utilize a VIP instead of server IP address so that switching within the cluster works automatically.  Any feedback appreciated.

1 REPLY 1
Highlighted
Community Manager

Re: Configuring VIP versus servers for MTS

Hi There,

 

I imagine your deployment is like the diagram in this help article, espec, Prognosis is installed on the MTS unix box:

https://help.prognosis.com/prognosis/117/deploying-prognosis-for-aci-mts-28089294.html

 

So it is the prognosis managing node - to - prognosis monitoring node connection that would be affected by a VIP type network setup. This Online Help article describes the relevant configuration.

https://help.prognosis.com/prognosis/117/configure-the-prognosis-network-connections-28091082.html

 

This Prognosis-to-Prognosis is a pretty standard TCP connection, default port 1960, that should be able to connect between network segments/subnets, with NAT or port forwarding etc so it should just be a matter of specifying the VIP address into the managing node NETWORK config:

MANAGED-NODES (<VIP Address Of MTS Host Here>:<port 1960 usually>)

 

HTH

Webinar: Top Ten Predictions in Retail Payments for 2020

Join IR, Celent and your peers as we discuss the top ten predictions for retail payments in 2020 and how evolving your payment solutions will help you stay ahead of your customers’ expectations ...

Join Webinar
Top Liked Members