WO2001095129A1 - Serveur centralise multi-domaine pour gestion de reseaux - Google Patents

Serveur centralise multi-domaine pour gestion de reseaux Download PDF

Info

Publication number
WO2001095129A1
WO2001095129A1 PCT/US2001/017749 US0117749W WO0195129A1 WO 2001095129 A1 WO2001095129 A1 WO 2001095129A1 US 0117749 W US0117749 W US 0117749W WO 0195129 A1 WO0195129 A1 WO 0195129A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
networks
network interface
information
request
Prior art date
Application number
PCT/US2001/017749
Other languages
English (en)
Inventor
Martin G. Vasquez
Frank Lee
James R. Mosier, Iii
Original Assignee
Mci Worldcom, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mci Worldcom, Inc. filed Critical Mci Worldcom, Inc.
Priority to AU2001268134A priority Critical patent/AU2001268134A1/en
Publication of WO2001095129A1 publication Critical patent/WO2001095129A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures

Definitions

  • the present invention relates to networks and. more particularly, to systems and methods for managing a network.
  • IP Internet Protocol
  • the original network manager may have assigned random Internet Protocol (IP) addresses or common network addresses to various servers, since the company was not concerned about IP addressing conflicts with any other networks.
  • IP Internet Protocol
  • the original network manager may have assigned an IP address of " 10.XXX.XXX.XXX" to the main server of the company's network, since network "10" is typically an unregistered address.
  • the network management personnel may also have to physically go to the specific server associated with the particular customer's network in order to perform the management-related services.
  • each server may have different access requirements, such as requiring a unique user identifier (ID) and password in order for the network management personnel to access the particular customer's network information. Learning the nuances associated with locating the appropriate server and providing the appropriate identification information via a number of different servers greatly increases the learning curve associated with new network management personnel managing customer networks.
  • ID unique user identifier
  • a centralized server then interfaces with a number of network interface devices associated with the respective domains.
  • the server interacting with network management personnel, may then transmit/receive network management-related information to/from each of the network interface devices.
  • a method for managing a plurality of networks in a shared network management environment includes a plurality of network interface devices, where each network interface device receives information from at least one of a lurality of networks.
  • the method includes assigning each of the plurality of networks to one of a plurality of respective domains.
  • the method also includes transmitting a request for information to a first one of the plurality of network interface devices where each network interface device is associated with one of the plurality of domains.
  • the method further includes receiving the requested information from the first network interface device and managing the at least one network using the received information.
  • Another aspect of the present invention provides a computer-readable medium that includes stored sequences of instructions that are executed by a processor.
  • the instructions cause the processor to receive, from a user, a request for providing a network management-related program for managing a first one of a plurality of networks.
  • the instructions further cause the processor to determine a network interface device associated with the first network and transmit the network management-related program to the first network interface device.
  • a system for managing a plurality of networks includes at least one network interface device configured to receive network-related information from at least one of the plurality of networks.
  • the system also includes a server configured to receive the network-related information from the at least one network interface device and manage the at least one network using the network-related information.
  • Figure 1 is an exemplary system in which methods and systems consistent with ihe present invention may be implemented.
  • Figure 2 is a block diagram of an exemplary server illustrated in Figure 1 , consistent with the present invention.
  • Figure 3 is a flow diagram, consistent with the present invention, illustrating exemplary processing for assigning a network to a domain.
  • Figure 4 is a flow diagram, consistent with the present invention, illustrating exemplary processing for providing network applications for managing customer networks.
  • Systems and methods consistent with-the present invention provide an efficient mechanism for managing networks in a shared management environment.
  • Customers' networks are assigned to particular domains to ensure that no network addressing conflicts exist.
  • a centralized server stores application programs for managing these customers' networks.
  • Network management personnel via the server, may then transmit these applications programs to network interface devices associated with the respective domains.
  • Providing a centralized location from which to manage the customers' networks greatly simplifies the tasks for network management personnel and reduces the knowledge requirements for such personnel.
  • Figure I is a block diagram of an exemplary system 100 in which methods and
  • the system 100 includes a plurality of network interface devices 110, 120 and 130, a server 140, a plurality of management devices 150, 160 and 170, and a network 180.
  • the network interface devices 110, 120 and 130 may each include any type of computer system, such as one or more servers, a personal computer, a minicomputer system or a mainframe computer with a connection tp server 140.
  • the network interface devices 110, 120 and 130 provide interface points to customer networks (not shown) that are actively being managed by system 100.
  • customer networks may include, for example, frame relay networks for which system 100 performs network management functions, i.e., monitors the status of routers, circuits, etc.
  • these customer networks may include any other type of network for which system 100 performs network management services.
  • each network interface device is associated with a separate
  • domain i.e., a group of customers' networks.
  • network interface devices 110, 120 and 130 are associated with domain 1, domain 2 and domain 3, respectively.
  • Each respective domain consistent with the present invention, may include a plurality of separate customer networks for which no network addressing conflicts exist.
  • the network interface devices 1 10, 120 and 130 may connect directly to server 1 0.
  • the network interface devices 110, 120 and 130 may establish communication with server 140 over a network (not shown) via a wired, wireless, or optical connection.
  • a network may include the Internet, a local area network (LAN), a wide.area network (WAN), an intranet or another type of network.
  • the server 140 may include any type of computer system, such as a mainframe, minicomputer or personal computer, that includes a mechanism for connecting to the network interface devices 110, 120 and 130 to enable server 140 to communicate with these network interface devices.
  • the server 140 may include a mechanism for communicating with the network interfaces devices via a network, such as the Internet, a LAN, a WAN, an intranet or another type of network.
  • the server 140 also includes a mechanism for communicating with management devices 150, 160 and 170 via network 180.
  • the server 140 consistent with the present invention, provides a forum through which network interface devices 110, 120 and 130 communicate customer network information.
  • the server 140 also provides a forum through which management devices 150, 160 and 170 may provide customized applications to particular customer networks, as described in more detail below.
  • the server 140 may also transmit data to these management devices 150, 160 and 170 over network 180 via wired, wireless or optical connections.
  • the management devices 150, 160 and 170 may each include any type of computer system, such as a personal computer, a laptop or a personal digital assistant (PDA), with a connection to network 180.
  • the management devices 150, 160 and 170 may also include dumb terminals with a connection to server 140.
  • the management devices 150, 160 and 170 may be used by personnel, such as a network engineer, for managing a customer's network.
  • management device 150 may be used by a network engineer to download or retrieve information for a network associated with network interface device 110.
  • the management devices 150, 1 0 and 170 may establish communication with server 140 over network 180 via a wired, wireless, or optical connection.
  • the network 180 may include the Internet, a LAN, a WAN, an intranet or another type of network. In alternative implementations, management devices 150, 160 and 170 may connect directly to server 140.
  • system 100 may include more or less network interface devices, management devices and servers thin illustrated in Figure 1.
  • FIG 2 is an exemplary diagram of server 140 of Figure I.
  • the server 140 includes a bus 210, a processor 220, a memory 230, a read only memory (ROM) 240, a storage device 250, an input device 260, an output device 270, and a communication interface 280.
  • the bus 210 permits communication among the components of the server 140.
  • the processor 220 may include any type of conventional processor or microprocessor that interprets and executes instructions.
  • the memory 230 may include a random access memory (RAM) or another dynamic storage device (referred to as main memory) that stores information and instructions for execution by the processor 220.
  • Main memory 230 may also be used to store temporary variables or other intermediate information during execution of instructions by processor 220.
  • ROM 240 may include a conventional ROM device and/or another static storage device that stores static information and instructions for processor 220.
  • the storage device 250 may include a magnetic disk or optical disk and its corresponding drive and/or some other type of magnetic or optical recording medium and its corresponding drive for storing information and instructions.
  • the input device 260 may include any conventional mechanism that permits an operator to input information to the server 140, such as a keyboard, a mouse, a pen, voice recognition and or biometric mechanisms, etc.
  • the output device 270 may include any conventional mechanism mat outputs information to the operator, including a display, a printer, a pair of speakers, etc.
  • the communication interface 280 may include any transceiver-like mechanism that enables the server 140 to communicate with other devices and/or systems, such as the network interface devices 1 10-130 and the management devices 150-170.
  • the communication interface 280 may include a modem or an Ethernet interface to a LAN.
  • communication interface 280 may include other mechanisms for communicating via a network, such as
  • the server 140 provides a forum through which customer networks may be proactively managed in an efficient manner, According to one implementation, the server 140 provides for the management of customer networks in response to processor 220 executing sequences of instructions contained in memory 230. Such instructions may be read into memory 230 from another computer-readable medium, such as a data storage device 250, or from a separate device via communication interface 280. Execution of the sequences of instructions contained in memory 230 causes processor 220 to perform the process steps that will be described hereafter. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the present invention. Thus, the present invention is not limited to any specific combination of hardware circuitry and software.
  • network interface devices 110, 120 and 130 may each be configured similarly to server 140.
  • the network interface devices 1 10, 120 and 130 operate using the same software platform, thereby enabling the server 140 to communicate with each of the network interface devices in a simplified manner.
  • the network interface devices 110, 120 and 130 receive information from the managed networks and transmit the received information to server 140 to facilitate the management of the customer networks.
  • FIG. 3 is an exemplary flow diagram, consistent with the present invention, illustrating processing associated with assigning a customer network to a particular domain.
  • Processing begins when network management personnel, such as a network engineer, receives a request for adding a new network into the shared management environment of server 140 (step 310).
  • the network engineer requests specific network information from the customer (step 320).
  • This information may include detailed information regarding network addressing or the network addressing scheme employed.
  • the network manager may request the IP addressing scheme used by the customer to address the customer's network equipment, such as the routers, switches, etc.
  • the customer supplies the network addressing information to the network engineer in any conventional manner, such as by e-mail, telephone, etc. (step 320).
  • the network engineer determines whether any addressing conflicts exist between the new customer's network and existing customer networks currently being managed by server 140 (step 330). For example, if the new customer is currently using network 10, i.e., an IP address of "10.XXX.XXX.XX," the network engineer determines whether any existing network being managed by server 140 uses that same address. If no addressing conflict exists, the network engineer assigns the new network to any one of the domains (step 340). For example, referring to Figure 1, the network engineer assigns the new network to any one of domains 1, 2 and 3, respectively.
  • the network engineer determines whether all the existing domains have an addressing conflict (step 350). For example, suppose that the new customer uses network "10" as an address and an existing customer in domain 1 uses network "10.” Further assume that neither domain 2 nor domain 3 uses network "10" as an address for any network equipment. In this case, the network engineer assigns the new network to either domain 2 or domain 3 (step 360). However, when the new network has an addressing conflict with existing equipment in each of domains 1, 2 and 3, the network engineer creates a new domain, such as domain 4 and assigns the new network to domain 4 (step 370). The network engineer may also have to provide additional network interface equipment associated with such a domain, similar to the network interface devices 1 10, 120 and 130 in Figure I .
  • the networks managed by server 140 may be separated to prevent addressing conflicts.
  • This use of the domains significantly simplifies the processes involved in transmitting and receiving data from the managed networks. For example, when network interface devices 1 10, 120 and 130 transmit requests for information to a particular customer's network, the possibility of misidentifying the destination network is avoided since no duplicate addressing exists. Similarly, the possibility of misinterpreting the source of information received from the customers' networks is eliminated. This greatly increases the efficiency of system 100, reduces potential errors and simplifies the tasks for network management personnel.
  • FIG. 4 illustrates exemplary processing associated with providing network applications for particular customer networks. Processing begins when a user, e.g., a network engineer, establishes a connection with server 140 in a conventional manner using a management device, such as management device 150 (step 410). For example, the network engineer may enter, via management device 150, a Uniform Resource Locator (URL) associated with server 140 and transmit the information via network 180. The server 140 then transmits a login screen to the management device 150 and the network engineer enters a user ID and password (step 420). The server 140 receives the ID and password and determines whether the network engineer is authorized to access server 140. Assuming that the network engineer is authorized, the server 140 provides an indication that access to server 140 has been granted.
  • a management device such as management device 150
  • URL Uniform Resource Locator
  • the server 140 stores a number of files that facilitate the management of the customers' networks. These files may be stored, for example, on storage device 250 ( Figure 1). Alternatively, these files may be stored on any other computer-readable medium accessible to server 140.
  • the network engineer may now transmit a new application program from his/her management device, such as management device 150, to server 140 via network 180 (step 430).
  • the new application program may be intended for a customer whose network equipment has been upgraded.
  • the application may be a program for a particular customer network that just added a new voice management system.
  • the network engineer identifies the particular customer's network that is to receive the new application program (step 430).
  • the server 140 may provide a list of all the customers' networks currently being managed by the server 140. In this scenario, the network engineer may select the particular customer network from the list.
  • the network engineer then downloads the program to the server 140.
  • the server 140 receives the application program and stores the program in memory, such as on storage device 250 (step 440).
  • the server 140 determines the domain associated with the intended recipient (step 440). More specifically, using the intended customer information provided by the network engineer at step 430, the server 140 determines the domain associated with that particular customer.
  • the server 140 then transmits the new application program to the network interface device associated with that particular domain (step 450). For example, if the server 140 determines that the intended recipient is in domain 1, the server 140 transmits the new application program to network interface device 110.
  • the network interface device receives the new program and executes the program for managing the identified customer's network (step 460). That is, the network interface device manages that customer's network in accordance with the new application program provided via server 140.
  • server 140 is able to provide customized programs to particular customer's networks without having to travel to the particular customer interface device, log in to that device and then load the new program.
  • the network engineer may simply provide the new application program to server 140, identify the particular customer and the server 140 automatically transmits the program to the appropriate network interface device associated with the particular customer.
  • the network interface device then executes the program for monitoring that particular customer's network.
  • the present invention may also use a program stored on server 140 for multiple customers' networks. For example, suppose that one customer adds network equipment similar to the equipment used by another customer network currently being managed by server 140. In this case, the network engineer responsible for managing this customer's network simply identifies the appropriate application program stored on server 140, indicates the intended customer network and provides this information to server 140. Server 140 automatically downloads the program to the appropriate network interface device. The network interface device then executes the program in conjunction with managing the intended customer's network. Advantageously, this saves time associated
  • the present invention may also be used to provide for global changes to the network interface devices. That is, in a situation where the network manager wishes to upgrade or change a network management program that operates across all the network interface devices, a network engineer may indicate to the server 140 that the change is to be a "global change.” The server 140 then transmits the new/upgraded program to each of the network interface devices. The network interface devices then execute the new program in conjunction with managing each of the connected customers' networks. This greatly reduces the time associated with individually changing/updating programs for each customer's network. It should be noted that the ability to implement a global change may be based on the user's access level, which may be based on the user's ID and password (step 420).
  • Server 140 also facilitates receiving information from the customers' networks.
  • the configuration of system 100 enables a network engineer to transmit particular requests for information associated with each of the networks communicating with the network interface devices.
  • the network engineer may wish to receive information, such as a listing of all network devices that were not "backed up" over a weekend.
  • the network engineer may send out a global query requesting such information from each of the network interface devices.
  • the network interface devices then obtain the requested information.
  • the network engineer may request network configuration information, network equipment inventory information, network equipment location information or any other network- related information for any of the customer networks.
  • An advantage of the invention is that network management personnel, interacting with server 140, may transmit customized information, including application programs, to particular customer interface devices without having to know where the network interface device resides and then logging into that interface device. This significantly simplifies the tasks for network management personnel and reduces the knowledge requirements for such personnel.
  • Another advantage of the invention is that network addressing conflicts are avoided by assigning the networks to domains based on the particular customer's addressing scheme.
  • a further advantage of the invention is that each network interface device operates using the same platform, thereby allowing the server 140 to reuse programs for a number of different networks. This also allows the server 140 to transmit global requests and receive information from all of the interface devices in a simplified manner.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un système de gestion de réseaux (100) permettant à un gestionnaire de réseaux de gérer un certain nombre de réseaux dans un environnement de gestion partagé. Le système comprend un serveur centralisé (140) interfaçant un certain nombre de dispositif d'interface de réseau (110, 120, 130). Chaque dispositif d'interface reçoit des informations relatives au réseau à partir des réseaux gérés et les transmet au serveur. Le serveur peut également recevoir des entrées provenant des utilisateurs requérant des informations spécifiques ou mettant en place des programmes spécifiques de gestion de réseaux pour un des réseaux gérés.
PCT/US2001/017749 2000-06-05 2001-06-01 Serveur centralise multi-domaine pour gestion de reseaux WO2001095129A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001268134A AU2001268134A1 (en) 2000-06-05 2001-06-01 Centralized multi-domain server for network management

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US58701500A 2000-06-05 2000-06-05
US09/587,015 2000-06-05

Publications (1)

Publication Number Publication Date
WO2001095129A1 true WO2001095129A1 (fr) 2001-12-13

Family

ID=24347981

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/017749 WO2001095129A1 (fr) 2000-06-05 2001-06-01 Serveur centralise multi-domaine pour gestion de reseaux

Country Status (2)

Country Link
AU (1) AU2001268134A1 (fr)
WO (1) WO2001095129A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3343835A4 (fr) * 2015-08-24 2019-04-03 ZTE Corporation Procédé et système de gestion d'élément de réseau

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5204955A (en) * 1989-12-18 1993-04-20 Hitachi, Ltd. Network management method and system
US5768501A (en) * 1996-05-28 1998-06-16 Cabletron Systems Method and apparatus for inter-domain alarm correlation
US5959985A (en) * 1994-09-19 1999-09-28 Newbridge Networks Corporation Multi-network architecture
US6057757A (en) * 1995-03-29 2000-05-02 Cabletron Systems, Inc. Method and apparatus for policy-based alarm notification in a distributed network management environment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5204955A (en) * 1989-12-18 1993-04-20 Hitachi, Ltd. Network management method and system
US5959985A (en) * 1994-09-19 1999-09-28 Newbridge Networks Corporation Multi-network architecture
US6057757A (en) * 1995-03-29 2000-05-02 Cabletron Systems, Inc. Method and apparatus for policy-based alarm notification in a distributed network management environment
US5768501A (en) * 1996-05-28 1998-06-16 Cabletron Systems Method and apparatus for inter-domain alarm correlation

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CHIU ET AL.STUDYING THE USER APPLICATION BEHAVIOR OF A LARGE NETWORK, IEEE, 1988, pages 14 - 22, XP002944692 *
MODIRI: "An implementation of the common network management information services element interfaces", IEEE, pages 29 - 38, XP002944693 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3343835A4 (fr) * 2015-08-24 2019-04-03 ZTE Corporation Procédé et système de gestion d'élément de réseau

Also Published As

Publication number Publication date
AU2001268134A1 (en) 2001-12-17

Similar Documents

Publication Publication Date Title
US8234639B2 (en) Autonomic auto-configuration using prior installation configuration relationships
US7013462B2 (en) Method to map an inventory management system to a configuration management system
US7065526B2 (en) Scalable database management system
US6058426A (en) System and method for automatically managing computing resources in a distributed computing environment
US7246174B2 (en) Method and system for accessing and managing virtual machines
US6697836B1 (en) Method and apparatus for controlling server
US6412025B1 (en) Apparatus and method for automatic configuration of a personal computer system when reconnected to a network
US6467088B1 (en) Reconfiguration manager for controlling upgrades of electronic devices
US5526492A (en) System having arbitrary master computer for selecting server and switching server to another server when selected processor malfunctions based upon priority order in connection request
US8286157B2 (en) Method, system and program product for managing applications in a shared computer infrastructure
US7444395B2 (en) Method and apparatus for event handling in an enterprise
JP5340610B2 (ja) 複数の構成要素を管理するためのコンピュータ・システム、並びにその方法及びコンピュータ・プログラム
US6111883A (en) Repeater and network system utilizing the same
US20020059471A1 (en) Method and apparatus for handling policies in an enterprise
US6973463B2 (en) Replication architecture for a directory server
US20020082819A1 (en) Data model for automated server configuration
US20080275976A1 (en) Information gathering tool for systems administration
US8086701B2 (en) Platform for managing and configuring network state
US7590618B2 (en) System and method for providing location profile data for network nodes
US7433957B2 (en) Group access privatization in clustered computer system
JP3153129B2 (ja) サーバ選択方式
US7840615B2 (en) Systems and methods for interoperation of directory services
WO2001095129A1 (fr) Serveur centralise multi-domaine pour gestion de reseaux
JPH10301786A (ja) ネットワーク経由によるソフトウェアの自動インストール方式
US20070174077A1 (en) Executing system and executing method of intelligent rule base service

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP