Telnet on Relocatable IPs

[Lee Chee Keen]

Hi,

I have configured MCSG Package on two servers db01 and db02.

I have a relocatable package IP 10.1.1.80.

When it is running in db01, I am able to telnet to 10.1.1.80 and login.

But when I halt the package and restart the package in the other node, I am not able to telnet to 10.1.1.80.

But I am able to ping it successfully and also when I use the "netstat -i" command, I am able to see the ip address 10.1.1.80 bind to lan0:1.

Can any one tell me where I am missing out. Why I am not able to telnet to 10.1.1.80 when I run it in the other node?

[A. Clay Stephenson]

First thing to check is if inetd is running on the 2nd node and if so, is telnet enabled in /etc/inetd.conf?

[Lee Chee Keen]

Clay,

Thanks for your reply. Both inetd is very well running and telnet is enabled in inetd.conf.

I can very well telnet to db02 using its physical ip address.

I am not able to telnet to db02 only with the relocatable package ip address 10.1.1.88

Is there any other setting which I am missing our with this relocatable ip?

[freddy_21]

are you copy your package configuration at other node?

is your other node have same subnet with your package ip?
Could you give me your network configurtion ( phisical Ip from both server)

thanks
freddy

[Lee Chee Keen]

I did copy my package configuration file to the other machine.

Yes. Both are in the same Subnet.

My physical ip address of db01 - 10.1.1.83
My physical ip address of db02 - 10.1.1.89

Virtual/Relocatable package IP address - 10.1.1.80

[Ralph Grothe]

Maybe a bit far-fetched,
is there some sort of tcp wrapper active on the failover node?
For instance, is there a file such as /var/adm/inetd.sec which restricts access to inetd services?
Can you access other (maybe non-inetd services) on the VIP when the package has failed over?
Usually one has a stand-alone sshd running to which you could try to connect over the VIP, or you could start some netcat or similar just for testing.

[Jim Keeble]

1) What's the error message or symptom you see when you try to telnet to the package IP?

2) Enable inetd logging with "inetd -l", then check syslog after you have tried again to see if inetd even sees the attempt.

3) "inetd -b" will enable even more debug information if needed.

4) Can you telnet to the package ip in loopback? I mean , can you telnet to the package ip from db02 when teh package is running on db02 ?

[melvyn burnard]

how about another basic test:
1. Halt the package
2. Verify that a ping of the IP returns nothing
3. use ifconfig to add the ip to the second node WITHOUT using SG.
4. Verify the ping now works.
5. Try the telnet command now.
6. If it fails, try ftp.
7. If telnet worked, then you need to review your SG package config, otherwise you have a basic network issue that has nothing to do with SG