Browse Prior Art Database

Automatically Generate Multiple Independent Static Routing Paths to Same IP Network Segment at Startup of Windows 2000 Server

IP.com Disclosure Number: IPCOM000033271D
Original Publication Date: 2004-Dec-03
Included in the Prior Art Database: 2004-Dec-03
Document File: 3 page(s) / 84K

Publishing Venue

IBM

Abstract

This invention provides a mechanism for a Windows 2000 Server* to automatically configure multiple independent static network routing paths to the same TCPIP network segment at system startup. By default, Windows 2000 will choose one adapter to be the gateway to that network segment at system startup. The command used to create persistent static routes does not allow the gateways to be specified, therefore, typical persistent static routes cannot be used.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 3

Automatically Generate Multiple Independent Static Routing Paths to Same IP Network Segment at Startup of Windows 2000 Server

Disclosed is a software-based mechanism to allow Windows 2000 Servers to automatically configure static network routing paths to the same TCPIP network segment using multiple physical network adapters. At startup, if left to perform this task by default Windows 2000 will choose one adapter to be the gateway to that segment. Gateways can only be specified when creating non-persistent routes. This disclosure describes a mechanism to overcome this default behavior.

The requirement for using multiple physical network adapters is to be able to closely bind multiple instances of an application running on the server each to its own physical adapter. This ensures that the outbound traffic from each application instance is routed over the corresponding physical adapter, in a symmetric fashion, rather than one adapter bearing all of the outbound traffic load.

It is possible to accomplish the desired configuration manually; a pair of static routes (non-persistent) can be created using the route command so long as each individual adapter reference is contained in each command, forcing Windows to accept multiple routes to the same segment with the multiple gateway adapter references.

Since each application is bound to a specific adapter, it sends network traffic to the TCPIP segment using the specifically bound adapter as the chosen route, and thus the outbound traffic load is more balanced.

The problem with the manual approach is that the adapter reference used in the command line arguments changes each time the adapter is stopped/started or the server is initialized. While the ...