Operating System - HP-UX
1834557 Members
3606 Online
110069 Solutions
New Discussion

Service guard ssh & telnet

 
Nair1980
Frequent Advisor

Service guard ssh & telnet

I am having a 2 node service guard cluster with single package running

My application performance monitoring software is connecting to the service guard package using a non-expiring user from some automated script and as per the monitoring system support engineer it is using telnet connection .

Here comes the problem. When ever I am doing a failover of package the monitoring software is stop working.

My observations -: the software is connected to package using package ip through the physical network port of the node the package resides and once it is fail over to other node the software not able to identify this change and stop working.

1  my observation is correct or not ?

2  In this condition any thoughts to solve this problem?

3  And how will be the effect if I am using a ssh connection for the monitoring software user?

Nair
4 REPLIES 4
Ivan Krastev
Honored Contributor

Re: Service guard ssh & telnet

Hi Nair,

You can setup ssh to connect to package, instead of nodes. To do that you need to use the same private/public key for both nodes of the cluster.

Search the forum for previous thread about setting ssh keys for SG cluster.


regards,
ivan
Murat SULUHAN
Honored Contributor

Re: Service guard ssh & telnet

Hi Nair

Did you check your network settings ? especially routing.
Can you ping the package ip when your monitoring app. is not working?

If you cannot solve the problem I think ssh will not work

Best Regards
Murat
Murat Suluhan
Nair1980
Frequent Advisor

Re: Service guard ssh & telnet

Hi Murat

I checked network connection it is working for both SG node from the monitoring software servers
Luis Cardenas Perez
Valued Contributor

Re: Service guard ssh & telnet

Hello Nair,

1. Yes your observations are correct. Since ssh uses tcp connection and establishes a session on the node, when the ip migrates to another node the connection will be broken even if you're using package ip.

2. You can add a line to package start script (/etc/cmcluster/package/package.cntl.sh) to start performance application.


3. I guess it has something to do with first question.


Hope it helps,

Luis