Configuring interfaces files for multiple networks

You can concatenate the original server name and the network name. For example, if your server is named PRODUCTION, you could choose the names PRODUCTION_network1 and PRODUCTION_network2.

2Do one of the following:

For PC clients, use sqledit to create multiple sql.ini file entries for the server, one for each network. In the following example, you create one entry for PRODUCTION_network 1 and one for PRODUCTION_network2. For more information, see the Open Client documentation for your client platform.

For UNIX clients, you can edit the interfaces files with an ASCII text editor. From the server’s interfaces files, copy the server name line and the “master” line for each network into the client interfaces file. Add the appropriate server name for each entry, and change “master” to “query.”

Clients on each network must use the DSQUERY value that corresponds to the network the client is on. In the following example, either PRODUCTION_network1 or PRODUCTION_network2 can be used.

#Client entry for PRODUCTION on network1

PRODUCTION_network1<tab>3<tab>3<newline> <tab>query tcp ether serv_corpnet 4559

#Client entry for PRODUCTION on network2 PRODUCTION_network2<tab>3<tab>3<newline> <tab>query tcp ether serv_engnet 5479

Configuring for query port backup

Another use for multiple network interfaces is to provide a backup in case of network failure. If a client is connected to a server via two networks, the client can establish a connection via the second network if the first one goes down.

To configure Adaptive Server for query port backup:

1Install multiple “master” and “query” lines in a server entry in the interfaces file.

2Adaptive Server listens for connections at both ports. Clients looking for a host name and a port number for a connection to an Adaptive Server try the port on each “query” line in order, until they establish a connection.

62

Adaptive Server Enterprise

Page 78
Image 78
Sybase DC35823-01-1500-04 manual Configuring for query port backup