How to control outbound traffic?

[Jared]

Hi all,

We are setting up a test environment. Part of that test environment
includes four Oracle instances on a single machine (running Solaris
8). There is a quad ethernet NIC in the machine, which is set to four
different addresses. The main client to this machine is an AIX server
running a piece of middleware, using a plain vanilla SQL*Net client.

It is, of course, trivial to set tnsnames.ora to access each instance
by a particular IP address. What we are trying to figure out is how
to make the instance reply via the given address. We can see from
netstat that the connection is made via the proper address; but does
that automatically mean the SQL*Net session will use the given IP for
outbound traffic?

TIA -

Kind regards,

jh

[Tony Dare]

Jared wrote:

> Hi all,
>
> We are setting up a test environment. Part of that test environment
> includes four Oracle instances on a single machine (running Solaris
> 8). There is a quad ethernet NIC in the machine, which is set to four
> different addresses. The main client to this machine is an AIX server
> running a piece of middleware, using a plain vanilla SQL*Net client.
>
> It is, of course, trivial to set tnsnames.ora to access each instance
> by a particular IP address. What we are trying to figure out is how
> to make the instance reply via the given address. We can see from
> netstat that the connection is made via the proper address; but does
> that automatically mean the SQL*Net session will use the given IP for
> outbound traffic?
>
> TIA -
>
> Kind regards,
>
> jh

Jared -

Traffic outbound from the database goes out the same socket the
connection was established on and so goes out the same interface/address
the socket was created on (or so I've read - testing it would say for
sure). The listener only does *port* redirection - when on the same
server as the database. It accomplishes this by directly handing off
its socket "handle" to the server process it spawns. The game changes
under RAC, when you're using a remote listener (in the case of
server-side load balancing). The listener in this case sends a
"redirect" packet to the client, which then disconnects and reconnects
to the address and port specified in the packet.

HTH,

TD

[Jared]

Thank you, Tony. That makes a lot of sense from a Unix standpoint.

Tony Dare <tonydare@yahoo.com> wrote in message news:<oItDc.7$X01.476@news.oracle.com>...

> Traffic outbound from the database goes out the same socket the
> connection was established on and so goes out the same interface/address
> the socket was created on (or so I've read - testing it would say for
> sure). The listener only does *port* redirection - when on the same
> server as the database. It accomplishes this by directly handing off
> its socket "handle" to the server process it spawns. The game changes
> under RAC, when you're using a remote listener (in the case of
> server-side load balancing). The listener in this case sends a
> "redirect" packet to the client, which then disconnects and reconnects
> to the address and port specified in the packet.