Hi,
I have 2 solaris 9 (192.168.0.201 and 192.168.0.202) and installed vcs
in both. The virtual ip in cluster is 192.168.0.200. when I ftp to
somewhere, I found the source ip was 192.168.0.201. Is it possible to
make the ftp connection from 192.168.0.200 instead of 192.168.0.201?
Thanks

BL a �crit :
> Hi,
> I have 2 solaris 9 (192.168.0.201 and 192.168.0.202) and installed vcs
> in both. The virtual ip in cluster is 192.168.0.200. when I ftp to
> somewhere, I found the source ip was 192.168.0.201. Is it possible to
> make the ftp connection from 192.168.0.200 instead of 192.168.0.201?
> Thanks
Maybe configuring IPMP with one interface and the virtual interface on 
..201 ?

In article <2857a2f6-7b3c-4869-ac79-4921242428ad@i29g2000prf.googlegroups.com>,
BL  <c50342182003@gmail.com> wrote:
>Hi,
>I have 2 solaris 9 (192.168.0.201 and 192.168.0.202) and installed vcs
>in both. The virtual ip in cluster is 192.168.0.200. when I ftp to
>somewhere, I found the source ip was 192.168.0.201. Is it possible to
>make the ftp connection from 192.168.0.200 instead of 192.168.0.201?

The problem is with the way that Solaris does IP aliasing. Because you've 
assigned 192.168.0.201 to node0's base interface (and 192.168.0.202 to 
node1's base interface) first, any traffic exiting the pysical NIC will 
appear to come from the first IP address configured on that interface. This 
will be true, even if the inbound packet was addressed to the IP alias of 
192.168.0.200 (or any other subsequent IP in that logical network you 
configure). If you want to force it to go out the next configured IP 
address, you would need to deprecate each node's base interface. Please 
note, I am not recommending this, I'm just saying that "this is what you 
would need to do if you wanted to force traffic to appear to come from 
192.168.0.200, regardless of which node 192.168.0.200 was active on".
-- 

"You can only be -so- accurate with a claw-hammer."  --me

BL wrote:
> Hi,
> I have 2 solaris 9 (192.168.0.201 and 192.168.0.202) and installed vcs
> in both. The virtual ip in cluster is 192.168.0.200. when I ftp to
> somewhere, I found the source ip was 192.168.0.201. Is it possible to
> make the ftp connection from 192.168.0.200 instead of 192.168.0.201?
> Thanks

You can use ipf to rewrite egress packets to come from a different source ip 
address.  You can do this per protocol.

Neal