Stationary ip not return

[gigiz]

Hallo,
After a switch of clusters package,
i have a problem when invoking r-command (such as rlogin remsh )to other node from a clusters node.It fails whith "permission denied".
I suppose the problem is that the secondary IP of the package switched to overshadow the primary ip, why the secondary ip address are used as source ip address. A work around might be to insert also all package ip in the /.rhosts but i want know why not return my primary ip address

[Steven E. Protter]

check the .rhosts file on boht machines.

If the ip address is hard coded and SG failed the ip over, there may be a contention issue.

See if you can ping the ip.

SEP

[Elmar P. Kolkman]

It shouldn't do that. First make sure how your route's and resolving looks like. Perhaps it uses another route, for instance over the backup lan instead of the userlan.
Traceroute might be of some help, just like nslookup.
Also make sure the .rhost files are indeed containing the (and all) node names, and not any package names.

[gigiz]

I think that a focal problem is on the routin table that was modified by last virtual ip assigned ...
but this is wrong how do resolve this problem.....?

[melvyn burnard]

I am not quite sure I follow you here, but if your package has failed over, it will move the floating or relocatable ip address to the new node. That node retains it's stationary or permanent ip address, and the relocatable address should have no effect.
I suggest you verify your .rhosts file on all nodes, and also verify your hostname to ip lookups give you the results you ar eexpecting, using nslookup.
Serviceguard does NOT use the relocatable address as the source address, although for an application you can compile the app to bind to this relocatable address, but this will not affect system commands such as rlogin etc.

[gigiz]

the solution is on the routing table ...