Browse Prior Art Database

Dynamic Alias Binding for Network Management

IP.com Disclosure Number: IPCOM000119125D
Original Publication Date: 1997-Dec-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 2 page(s) / 37K

Publishing Venue

IBM

Related People

Ashida, T: AUTHOR [+3]

Abstract

Disclosed is a network management using dynamic alias binding by which a network administrator can dynamically change an end user's server without a change in configuration. The end user specifies the alias of the server instead of specifying the server's network Identification (ID) directly, and the network administrator can switch the server by changing alias binding to the other server.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 100% of the total text.

Dynamic Alias Binding for Network Management

      Disclosed is a network management using dynamic alias binding
by which a network administrator can dynamically change an end user's
server without a change in configuration.  The end user specifies the
alias of the server instead of specifying the server's network
Identification (ID) directly, and the network administrator can
switch the server by changing alias binding to the other server.

      The Figure shows an example of this system.  There are two
servers.  One has the ID "xxx" (1) and the other has the ID "yyy"
(2).  In addition to these two servers, there is one alias "aaa"
(4).  From the user's (3) view point, this alias looks like there is
one other server which has the ID "aaa" and the user can specify
"aaa" as her server.  In that case, the user's request is passed to
the server bound to the alias (in this example, the server "xxx" is
bound to the alias).  When the administrator of this network would
like to change the user's server to server "yyy", he can do it by
re-binding the alias  to server "yyy" instead of changing the user's
client configuration.

      By using this addressing, the administrator can change the
user's server without the user's configuration changing or server's
shutdown, and this mechanism makes it easier to divide the load
equally among the servers or to switch the server to backup.