JP3798584B2 - Network management system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a network management system in a multi-domain network.
[0002]
A management system for managing a network is provided for each network such as ATM, SDH, and IP, and manages resources, paths, and failures in each network.
[0003]
In recent years, it is desired that ATM, SDH, IP, and the like are connected to a server network using an optical network, and each is configured and managed as a client network.
[0004]
[Prior art]
FIG. 16 shows a network system configuration. In the figure, 80 is an ATM (Asynchronous Transfer Mode) network in which cells are asynchronously transmitted using VPI (virtual path identifier) / VCI (virtual channel identifier) by cell, and 81 is various types of synchronously. An SDH (Synchronous Digital Hieralchy) network that transmits data in the form of a virtual container, 82 is an IP (Internet Protocol) network that performs connectionless packet exchange in TCP / IP (Transmission Control Protocol / Internet Protocol). Yes, 83 is an optical network using an optical fiber as a physical medium for actually transmitting signals.
[0005]
The optical network 83 is called a server network because it functions as a server for each of the networks 80 to 82, and each of the networks 80 to 82 is called a client network.
[0006]
Each of the networks 80 to 82 and 83 includes network management systems (NMS) 80a, 81a, 82a, and 83a for managing resources, paths, failures, and the like in the respective networks. Are independent of each other. In this way, each of the networks 80 to 83 forms a different domain (resource management area), and this network system is configured by a plurality of domains.
[0007]
Telecom operators and Internet service providers are planning to introduce point-to-point wavelength division multiplexing communication systems to backbone networks to accommodate the rapidly increasing Internet and data communications traffic. In addition to this, mesh-like optical networks composed of an optical cross-connect system (OXC: Optical Crossconnection) and an optical wavelength division multiplexing system (OADM: Optical Add Drop Multiplex) break down various limitations of existing networks. It is expected to provide a low-cost and large-capacity next-generation communication infrastructure. As for optical networks, in ITU-T (Telecommunication Standardization Sector of the International Telecommunication Union), optical channel (0Ch: 0ptical Channel) layer, optical multiplex section (OMS: Optical Multiplex Section) layer, optical transmission section (OTS: Modeling with three layers of Optical Transmission Section) is under study.
[0008]
[Problems to be solved by the invention]
Each of the network management systems 80a to 83a shown in FIG. 16 operates independently and is not linked to each other. Therefore, the server layer (which means a server hierarchy and represents the optical network 83 that is the server network of FIG. 16). If a failure occurs in (), failure recovery is performed at the server layer. If all failures are not recovered, the failure recovery etc. can be activated in other network management systems simply by notifying the user. Therefore, there was a problem that the recovery was delayed.
[0009]
In addition, in order to speed up failure recovery, it is necessary to prepare a large amount of spares for recovery at the server layer, which increases the cost.
[0010]
An object of the present invention is to provide a network management system capable of performing cooperation between network management systems of a plurality of domain networks.
[0011]
[Means for Solving the Problems]
FIG. 1 shows the principle configuration of the present invention. In the figure, 1 is a coordinator system provided by the present invention, 10 is a management unit, 10a is a network configuration management unit that manages a table (13a to be described later) including configuration information of a server network and a client network, and 10b is terminated at initialization. An access point management unit 10c that constructs resources such as points and performs correspondence management using a table (13b to be described later) including information indicating the correspondence relationship between the termination points to which the server network and the client network are connected. A path management unit that operates to generate a server path from a client or to control connection generation for a client when a server path is generated, and 11 is an NMS (network management system) of the server network and client network via a coordinator A message communication unit between NMSs that controls message communication in the network, 12 is a failure recovery unit that operates in the event of a failure and cooperates in failure recovery between layers, 13 is a database that stores various tables and data, and 13a is a server network. Network configuration information table including client network configuration information, 13b is a correspondence table representing the correspondence and status of access points connecting sub-networks, 13c is a detour route table having access point information, and 2 is an optical network. Server sub-network, 3 and 4 are client sub-networks composed of any one of ATM, SDH, IP, etc., 20 is a server sub-network management system (indicated by server SNMS), and 21 is a server network. Management system (displayed by server NMS), 30 and 40 are client subnetwork management systems (displayed by client SNMS) provided corresponding to each client subnetwork, and 31 is a client network management system for controlling a plurality of client SNMSs (displayed by client SNMS). Client NMS).
[0012]
Although not shown, the optical network (server subnetwork) 2 is composed of an optical cross-connect device (OXC), an optical ADM (Add Drop Multiplex) device, a WDM (Wavelength Division Multiplex) multiplexer, and the like. Subnetworks 3 and 4 are constituted by networks such as ATM, SDH, and IP, and each piece of configuration information is held in the network configuration information table 13a, and an access point and a state connecting the server subnetwork 2 and the client subnetworks 3 and 4 (In operation, unused, etc.) is held in the correspondence table 13b.
[0013]
In order to perform cooperation between the layer of the server subnetwork 2 and the layers of the client subnetworks 3 and 4, the network configuration management unit 10 a of the coordinator system 1 receives an instruction from a terminal operated by an operator (operator) (not shown). The configuration information table 13a of the server subnetwork 2 and the client subnetworks 3 and 4 is registered and updated. In addition, the network management system (NMS) 21 and 31 of each of the server network and each client network manages only the termination point information of its own domain, but the access point management unit 10b of the coordinator system 1 When the correspondence between the end points in each domain is managed using the correspondence table 13b and the path is set at the server layer, the client side sets the client connection between the end points of the client connected to the end point of the server path. Set.
[0014]
When the path setting is performed by the client NMS 31, the path management unit 10c generates a server path if the path of the requested bandwidth cannot be acquired, and sets a corresponding connection on the client side when the path is generated by the server. It also has a function and manages the bandwidth of the client path to be accommodated.
[0015]
When a failure occurs, the failure recovery unit 12 performs failure recovery using the failure recovery mechanism provided in the NMS in the domain (network) where the failure has occurred, but not all failures may be recovered. Recovery is performed by rerouting at the layer (other network).
[0016]
Each of the network management systems 21 and 31 of the server and the client uses the coordinator system 1 to perform processing across the networks such as path setting and cancellation when an operator (user or operator) gives an instruction from an operation terminal (not shown). However, by providing each operator with an access level, access control can be permitted only when the operator has a certain level or higher.
[0017]
DETAILED DESCRIPTION OF THE INVENTION
FIG. 2 shows a configuration example of the table. Is a configuration example of a network consisting of five sub-networks; Is the network configuration information table (corresponding to the sub-network configuration information table 13a in FIG. Is an access point correspondence table (corresponding to the correspondence table 13b in FIG. 1). A. In the example of the network configuration as shown in FIG. As shown in FIG. 4, for each subnetwork ID 1 to 5, the server / client type, the server type (WDM (wavelength division multiplexing), SDH, IP, etc.), and the subnetwork connected to each subnetwork In addition, each information of the access point list (access point list to each connected subnetwork) is set as shown in the figure. In the access point correspondence table, C.I. As shown in FIG. 4, the server access point ID connected to the client access point ID is set, and the status of each access point (in operation, unused, etc.) is registered for each item of each table.
[0018]
B. of FIG. And C.I. Is created in the coordinator system 1 based on notifications from the client NMS and the server NMS when the equipment is newly added.
[0019]
FIG. 3 is an operation explanatory diagram of server path setting. 1 to 4 and 20, 21, 30, 31, and 40 in FIG. 3 are the same as those in FIG. 1 and are not described here.
[0020]
When the operator instructs the server NMS 21 to set the path between 4010 and 5001 from the operation terminal ((1) in FIG. 3), the server NMS 21 sets the path between the end points 4010 and 5001 of the subnetwork 2 (see FIG. 3). (2) of 3). As a result, when the path setting in the sub-network 2 is completed, the server NMS 21 sends a path generation notification having termination point and bandwidth information to the coordinator system 1 ((3) in FIG. 3). In the coordinator system 1, based on the termination point information included in the generation notification, the termination point 3-2003 of the client subnetwork 3, 4 connected to each from the access point correspondence table (C. in FIG. 2). 4-5001 is acquired, and a path setting instruction is given to the client NMS 31 ((4) in FIG. 3). In response to this, the client NMS 31 controls the client SNMS 30 and the client SNMS 40 to set each path between the end points of the subnetwork 3 and the subnetwork 2 and between the end points of the subnetwork 4 and the subnetwork 2 to the operating state. I do. The client path is a path using VPI / VCI for ATM, a fixed bandwidth for SDH, and an IP address for IP. It is possible to include processing for determining whether or not to execute path setting based on the authority (level) held by the operator who has issued the path setting instruction.
[0021]
FIG. 4 is a processing flow of the client NMS at the time of path setting. This process is started by receiving a path generation notification from the server NMS, and searches for a corresponding client access point from the access point relation table (S1 in FIG. 4). In this search, it is determined whether or not an access point exists (S2 in FIG. 4). If it does not exist, the process is terminated, and if it exists, the client subnetwork NMS is instructed to generate a client path (S3).
[0022]
FIG. 5 is an explanatory diagram of the server path release operation. The reference numerals 1 to 4 and 20, 21, 30, 31, and 40 in FIG. 5 are the same as the parts having the same reference numerals in FIGS.
[0023]
When the operator instructs the server NMS 21 to cancel the path between 4010 and 5001 from the operating terminal ((1) in FIG. 5), the server NMS 21 that has received this command operates the path of 4010 to 5001 with respect to the coordinator system 1. A status check request is made ((2) in FIG. 5). The coordinator system 1 is shown in FIG. When the operation status is checked by referring to the access point relation table as shown in (3) in FIG. 5 and the operation check response is notified to the server NMS 21 (4 in FIG. 5) and not in operation. Instructs the client NMS 31 to cancel the path ((5) in FIG. 5), and the client NMS 31 cancels the client path between the corresponding client access points (between 4-5001 and 3-2003) accordingly. To the client SNMSs 30 and 40 ((6) in FIG. 5). When the cancellation is completed, when a cancellation completion notification is sent from the client SNMS 30 or 40 to the coordinator system 1, the coordinator system 1 returns an unused operation check response to the server NMS 21, and the server NMS 21 starts path cancellation.
[0024]
FIG. 6 is a processing flow of the client NMS at the time of path cancellation. This process is started in the client NMS that has received the path release notification from the server NMS. When the notification is received, the corresponding client access point is searched from the access point relation table (S1 in FIG. 6). In this search, it is determined whether an access point exists (S2 in FIG. 6). If it does not exist, the process is terminated. If it exists, it is determined whether the path status is in use (S3). The server NMS is notified that the path is being used (S4). If not, the server NMS is notified that the path can be released (S5). In this case, it is possible to determine whether or not the path release notification can be performed by the authority (level) held by the operator who has generated the path release notification.
[0025]
In the path setting process shown in FIGS. 3 and 4 above, when a new server path and client path are set, transition is made unused, a new path is set on the client side, and a generation notification is notified to the coordinator system. At some point, the state can be changed to the operational state. Also, as shown in FIG. 5 and FIG. 6, in the path cancellation by the client NMS, the cancellation notification is notified to the coordinator system, and the state is made unused when all client paths are released. By not using this, it is possible to prevent double setting.
[0026]
Next, the operation for setting from the client side is shown.
[0027]
FIG. 7 is a diagram for explaining the operation of setting a path between client networks by the client NMS. Reference numerals 1 to 4 in FIG. 7 and reference numerals 20, 21, 30, 31, and 40 correspond to the same reference numerals in FIG. 1, FIG. 3, and FIG.
[0028]
In FIG. 7, when the operator first gives the client NMS 31 an operation terminal or a path setting instruction between 4-6001 and 3-7001 ((1) in FIG. 7), the client NMS 31 has a free path in the designated band. The table is searched for (2) in FIG. If there is no route of the requested bandwidth, the path setting request is notified to the coordinator system 1 ((3) in FIG. 7). Upon receiving this, the coordinator system 1 instructs the search for network configuration information (B in FIG. 2) based on the end point of the client ((4) in FIG. 7), and the subnetwork ID (sub-network in FIG. 7). The network 4 and the subnetwork 3) are obtained, and access points that can connect the subnetworks 4 and 3 are obtained from the access point relation table (C. of FIG. 2) (4010 and 5001 of the subnetwork 2). And the server NMS 20 are instructed to set a path between them (5 in FIG. 7). After completing the path setting, the coordinator system 1 instructs the client NMS 31 to generate a path for the path setting request notification.
[0029]
FIG. 8 is a processing flow of the coordinator system in the operation of FIG. When a path setting request is received from the client NMS, the processing is started, and the subnetwork ID of the client path termination point is searched from the network configuration information table (B in FIG. 2) (S1 in FIG. 8). The server network access point that connects the sub-networks is searched from the access point correspondence table (C in FIG. 2) (S2 in FIG. 8). In this search, it is determined whether there is an unused access point (S3 in FIG. 8). If there is no access point, the client NMS is notified that the server path cannot be set (S4). A path setting instruction is given (S5). Subsequently, the server path setting result is received from the server NMS (S6 in FIG. 8), and it is determined whether or not the contents indicate that the path setting has been performed (S7). If the path setting is not performed, the process returns to S2. If the path setting is performed, the state of the access point correspondence table is set (S8), the client NMS is notified of the completion of the server path setting, and the client The client path is reset by the NMS (S9).
[0030]
Next, FIG. 9 is an operation explanatory diagram when a failure occurs in the server network. Reference numerals 1 to 4 in FIG. 9 and reference numerals 20, 21, 30, 31, and 40 correspond to the same reference numerals in FIGS.
[0031]
In FIG. 9, when a failure occurs in the server network 2, an alarm recovery stop instruction is issued to the client device when an alarm is detected in the server device connected to the client device ((1) in FIG. 9). This instruction is issued in order to preferentially perform the recovery on the server side while suppressing the failure recovery operation on the client device side. When failure recovery fails on the server side ((2) in FIG. 9), a failure recovery start instruction is sent to the client device ((3)), and failure recovery is started on the client side.
[0032]
When failure recovery fails in the server network, the server NMS 21 notifies the coordinator system 1 of failure recovery failure ((5) in FIG. 9). The coordinator system 1 obtains the connected client subnetwork ID based on the termination point of the failed server path, and searches the access point correspondence table for an access point that can connect the client subnetwork and the server network. The server NMS 21 is instructed to search for a path route, recorded in the detour route table (13c in FIG. 1) ((6) in FIG. 9), and the state is being searched. If successful, the coordinator system 1 records the status of the detour route table as having a route.
[0033]
10 to 12 show the processing flow of each unit when a failure occurs, FIG. 10 shows the processing flow of the server SNMS, FIG. 11 shows the processing flow of the server network and server NMS, and FIG. 12 shows the processing flow of the coordinator system. .
[0034]
FIG. 10 shows processing in the server network (server device). When a failure is detected in the server device, a failure recovery suppression message is transmitted to the client network (client device) (S1 in FIG. 10). After that, it is determined whether or not the failure recovery processing is completed (S2 in FIG. 10), and when it is completed, it is determined whether or not the failure is recovered (S3 in the same). A message is transmitted (S4).
[0035]
When a failure is detected in the server device, the processing of FIG. The server NMS notifies the server NMS as shown in FIG. As shown in Fig. 2, the fault notification is sent to the coordinator. The coordinator system executes the processing flow shown in FIG. 11, uses the search function of the path setting operation shown in FIG. 8 to search for a detour route whose access point has been changed, and stores it in the detour route table (13c in FIG. 1). Record.
[0036]
Referring to FIG. 11, when an alarm notification is received by the coordinator system, the subnetwork ID of the client connected to the failed server path termination point is searched from the network configuration information table (S1 in FIG. 11). Next, the server network access point that connects the sub-networks is searched from the access point correspondence table (S2 in FIG. 11), and it is determined whether there is an unused access point (S3). If there is, the server NMS is instructed to search for a path between access points of the server (S4). Thereafter, a server path search result is received from the server NMS (S5 in FIG. 11), and it is determined whether there is a path route based on the result (S6). If not, the process returns to S2. The route is recorded in the detour route table (S7), it is determined whether the detour route of all the fault paths is recorded (S8), and the process ends when the detour routes of all the fault paths are recorded, but all are recorded. If not, return to S2.
[0037]
If failure recovery fails on the client side when the failure of the server device shown in FIG. 10 is detected, the client NMS executes the failure recovery failure processing flow shown in FIG. 13 and notifies the coordinator system of failure recovery failure. Do.
[0038]
FIG. 14 is a processing flow of the coordinator system when a failure recovery failure notification is received. When the client failure recovery failure notification is received, it is determined whether there is a detour route corresponding to the detour route table (S1 in FIG. 14). If there is no detour route table, the processing is terminated. Is instructed to set a path (S2 in FIG. 14). When the path setting result is received in response to this instruction (S3 in FIG. 14), it is determined whether the path setting is successful (S4). If not successful, the process returns to S1, but if successful, the state of the access point correspondence table is set (S5 in FIG. 14), the server path setting is notified to the client NMS, and the client NMS is instructed to reset the client path (S6). ).
[0039]
FIG. 15 is a processing flow when the client side succeeds in the failure recovery in the processing flow of FIG. A. of FIG. Is a process in the client NMS, and when the failure recovery is successful in the client NMS, the failure recovery is notified to the coordinator and the process is terminated. B. of FIG. Is a process in the coordinator. When the coordinator receives the client failure recovery success notification by the above processing, the corresponding detour route table is deleted and the processing is terminated.
[0040]
Finally, the coordinator system gives the access level (weight of job title) to the user (operator) of the server NMS and client NMS in advance and sets the access level when performing access control to other network management systems (NMS). Check to manage access control only when it is above a certain level.
[0041]
【The invention's effect】
According to the present invention, when a client network layer such as ATM, SDH, or IP is connected to a server network layer such as an optical network, path setting and failure recovery are performed by linking paths and failure recovery between layers. In addition to speeding up processing, it is possible to reduce network resources by sharing spare resources, and an efficient system can be constructed.
[Brief description of the drawings]
FIG. 1 is a diagram showing a principle configuration of the present invention.
FIG. 2 is a diagram illustrating a configuration example of a table.
FIG. 3 is an operation explanatory diagram of server path setting.
FIG. 4 is a diagram showing a processing flow of a client NMS at the time of path setting.
FIG. 5 is an explanatory diagram of server path release operation.
FIG. 6 is a diagram showing a processing flow of a client NMS at the time of path cancellation.
FIG. 7 is an explanatory diagram of an operation of setting a path between client networks by a client NMS.
FIG. 8 is a diagram showing a processing flow of the coordinator system in the operation of FIG. 7;
FIG. 9 is an operation explanatory diagram when a failure occurs in the server network.
FIG. 10 is a diagram showing a processing flow of a server SNMS.
FIG. 11 is a diagram showing a processing flow of a server network and a server NMS.
FIG. 12 is a diagram showing a processing flow of the coordinator system.
FIG. 13 is a diagram showing a processing flow when failure recovery is unsuccessful.
FIG. 14 is a diagram showing a processing flow of the coordinator system when a notification of failure recovery failure is received.
15 is a diagram showing a processing flow when failure recovery is successful on the client side in the processing flow of FIG.
FIG. 16 is a diagram showing a system configuration of a network.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 Coordinator system 10 Management part 10a Network configuration management part 10b Access point management part 10c Path management part 11 Inter-NMS message communication part 12 Failure recovery part 13 Database 13a Network configuration information table 13b Correspondence relation table 13c Detour path table 2 Server subnetwork 3 , 4 Client sub-network 20 Server sub-network management system 21 Server network management system 30, 40 Client sub-network management system 31 Client network management system

Claims (9)

In a network management system that manages multiple networks with a management unit for the end point of its own network and a network management system that sets and releases paths.
Configuring multiple client network and server network, management unit for managing such an access point, the coordinator system comprising a database and a failure recovery unit is provided,
The database of the coordinator system includes a network configuration information table including information configuring the server network and the client network, and a correspondence table including a correspondence relationship and a state of access points connecting the server network. Oh ,
The management unit of the coordinator system converts the termination point of the notified server path into the termination point of the client network using the correspondence table in response to a server path generation notification from the network management system of the server network. And a network management system comprising a path management unit that instructs the network management system of the client network to generate a client path . In claim 1,
When the path management unit of the coordinator system receives the client network path release notification before the path release notification from the network management system of the server network , the client determines that the access point status is not in use and can be released. A network management system characterized by instructing a network network management system to cancel a path and permitting the server network network management system to cancel the path . In either claim 1 or 2,
The path management unit of the coordinator system changes the state of the corresponding path in the correspondence table when the path is set to in use, and changes the state of the corresponding path in the correspondence table to unused when the path is released. A featured network management system. In claim 1,
When the path management unit of the coordinator system receives a path setting request from the network management system of the client network, it searches the network configuration information table to identify the network of the client path termination point,
An access point of the identified network is searched from the correspondence table to detect an unused access point, and a path setting instruction is given to the network management system of the server network.
When the result of path setting completion is received from the network management system of the server network, the state of the access point correspondence table is set, and the server path setting is notified to the network management system of the client network system. In claim 1,
In response to the occurrence of a failure in the server network, the failure recovery unit sends an instruction to stop the failure recovery operation to the client network and starts the failure recovery operation in the server network.
A network management system characterized in that when failure recovery fails in a server network, a failure recovery start instruction is sent to the client network to start failure recovery in the client network . In claim 5,
Notifying the network management system of the server network together with the start of the operation of failure recovery in the server network,
The network management system of the server network performs sending the failure notification to the coordinator system, the coordinator system clients network connected to the termination point of the server path by searching the network configuration information table by the path management unit Identify and search the connection table for access points that can be connected between the client and server networks,
A network management system characterized by instructing the network management system of the server network to search for a route through a searched access point and recording and using the searched route in the detour route table . In claim 5,
If failure recovery fails in the client network, the network management system of the client network notifies the coordinator system of failure recovery failure,
2. The network management system according to claim 1, wherein the coordinator system instructs the network management system of the client network to start failure recovery again when the presence of a route is recorded in the bypass route table . In claim 5,
When failure recovery is successful in the server network, the network management system of the client network notifies the coordinator system of failure recovery success,
The coordinator system instructs a network management system of a server network to release a route in a detour route table in which a detour route searched by a path management unit during the failure recovery operation is recorded. system. In any one of Claims 1 thru | or 8 ,
The coordinator system is necessary when an access level is previously assigned to each operator of the network management system of the server network or the network management system of the client network, and mutual access control to the network management system of another network is performed. A network management system for checking whether an access level is provided .

Images