Routing costs and redundant connections

We have about 20 satellite offices, each with their own Notes server and a highspeed Internet connection.

Currently, all the servers are in the same NNN, so all mail routes instantly between all offices, and we needn’t have more powerful hub servers to route mail through (except our incoming SMTP servers). This is of course not perfect, but it is easy.

We are getting backup Internet lines in our offices, each office will have two lines, each with it’s own IP address. I have the hardware which will bring up these redundant connections when necessary, so all I need is a way of routing the email over these secondary connections when the primary connection fails.

I have two requirements:

  1. Each office should be able to route mail directly to every other office

  2. The secondary address must be used when the server is unresponsive on the primary address.

The problem is, Notes doesn’t seem capable of this. From what I can make out, apart from the large number of connection documents I’d have to keep track of, the router will either never try the backup connection, or it will take it as the primary connection.

For example:

Two servers, A & B

Server A has two connection documents for B, the primary with cost 1 and the secondary with cost 2.

When the primary address fails, the cost will go to 2; then the router must choose between 2 connection documents with the same cost, number of hops and destination server name. So it will probably choose the one which appears first in the directory which I don’t think will be reliable. The same result would happen if I created the two connection documents with equal routing costs.

What is everyone else doing??? Does no one else do mesh routing?