JP2001036587A - Network management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To coordinate network management systems in a plurality of domain networks with respect to a network management system that is provided with a network management system of each network. SOLUTION: The network management system is provided with a coordinator system 1 that has a management section 10 that manages cross-reference of access points between a client network and a server network, a bus management section 10d and a fault recovery section 12. The coordinator system 1 is configured with a sub network configuration information table including information configuring the server network and the client network and a cross-reference table 13b including a cross-reference of access points to connect the sub networks and its state so as to coordinate the networks.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a network management system in a multi-domain network.

[0002] A management system for managing a network includes:
Deployed for each network such as ATM, SDH, IP, etc.
It manages resources, paths, failures, etc. in each network.

In recent years, it has been desired that ATMs, SDHs, IPs, and the like are connected to a server network using an optical network, and each is configured and managed as a client network.

[0004]

2. Description of the Related Art FIG. 16 shows a network system configuration. In the figure, reference numeral 80 denotes VPI (virtual path identifier) and VCI (virtual channel identifier) depending on the cell.
A that performs asynchronous transmission by expressing paths and channels using
TM (Asynchronous Transfer Mode) network,
81 is an SDH (Synchronous Digital Hieralchy) that transmits data synchronously in the form of various virtual containers.
Network 82, TCP / IP (Transmission C
IP (Internet Protocol) that performs connectionless packet exchange in ontrol Protocol / Internet Protocol
The networks 1) and 83 are optical networks using optical fibers as physical media for actually transmitting signals.

The optical network 83 is connected to each network 80
The server network is called a server network because it functions as a server with respect to -82, and each of the networks 80-82 is called a client network.

Each of the networks 80 to 82 and 83 has a network management system (Netw) for managing resources, paths, faults, and the like in each network.
orkManagement System: NMS) 80a, 81a, 82
a and 83a, and each network management system is independent. Thus, each network 80 ~
Reference numerals 83 denote different domains (resource management areas), and this network system is constituted by a plurality of domains.

[0007] Telecommunications carriers and Internet service providers have a point-to-point connection to backbone communications networks to accommodate the rapidly growing Internet and data communications traffic.
Plans to introduce point-division multiplex communication system. In addition, the optical cross connect system (OXC:
Optical networks in the form of a mesh consisting of Optical Crossconnection) and optical wavelength multiplexing / branching systems (OADM: Optical Add Drop Multiplex) overcome the various limitations of existing networks and are low-cost, large-capacity next-generation communication platforms. Is expected to provide. For the optical network, the ITU-T (Telecommunication Standardization Sector of the International Telecommunication Union) provides an optical channel (0Ch:
0ptical Channel) layer, optical multiplex section (OMS: O
ptical Multiplex Section) layer and optical transmission section (OTS) layer
Modeling in layers is being considered.

[0008]

The network management systems 80a to 83a shown in FIG. 16 operate independently of each other and do not cooperate with each other. Therefore, a server layer (means a server hierarchy; FIG. If a failure occurs in the optical network 83 which is a server network), the failure is recovered at the server layer, and if all the failures are not recovered, the user is notified only.
There is a problem that recovery is delayed because other network management systems do not activate failure recovery or the like.

Further, in order to speed up the recovery from a failure, it is necessary to prepare a large number of spares for restoring all at the server layer, and there is a problem that the cost increases.

[0010] It is an object of the present invention to provide a network management system capable of cooperating with each network management system of a multi-domain network.

[0011]

FIG. 1 shows the principle 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. Build resources such as points,
An access point management unit 10c that manages correspondence using a table (13b described later) including information indicating the correspondence between terminal points to which the server network and the client network are connected. A path management unit that generates and controls connection generation for a client when a server path is generated; and 11 is an NMS message that controls message communication between an NMS (network management system) of a server network and a client network via a coordinator. A communication unit 12 operates when a failure occurs, and performs a failure restoration cooperation between layers, and 13
Is a database that stores various tables and data.
3a is a network configuration information table including configuration information of the server network and the client network,
13b is a correspondence table indicating the correspondence and the state of the access points connecting the sub-networks, 13c is a bypass route table having access point information, 2 is a server sub-network composed of an optical network, 3, 4
Is a client sub-network composed of any one of ATM, SDH, IP, etc., 20 is a server sub-network management system (displayed by server SNMS), 21 is a server network management system (displayed by server NMS), 30 , 40 is a client sub-network management system (displayed by client SNMS) provided corresponding to each client sub-network, and 31 is a client network management system (displayed by client NMS) that controls a plurality of client SNMSs.

Although an optical network (server subnetwork) 2 is not shown, an optical cross-connect device (OXC), an optical ADM (Add Drop Multiplex) device, W
Client networks (client sub-networks) 3 and 4 are configured by networks such as ATM, SDH, and IP, and each configuration information is held in a network configuration information table 13a. The access points connecting the server subnetwork 2 and the client subnetworks 3 and 4 and their states (operating, unused, etc.) are held in the correspondence table 13b.

In order to cooperate between the layer of the server subnetwork 2 and the layers of the client subnetwork 3 and 4, the network configuration management unit 10a of the coordinator system 1 is operated from a terminal operated by an operator (not shown). The configuration information table 13a of the server subnetwork 2 and each of the client subnetwork 3 and 4 is registered and updated according to the instruction. The access point management unit 10b manages only the end point information of its own domain in each of the network management systems (NMS) 21 and 31 of the server network and each client network, but the access point management unit 10b of the coordinator system 1 When the correspondence between the terminal points in each domain is managed using the correspondence table 13b and the path is set in the server layer, the client side establishes the connection between the terminal point of the server path and the client between terminal points of the connected clients. Set.

The path management unit 10c is a client NMS 3
If the path is set in step 1 and the path of the requested bandwidth cannot be obtained, a server path is generated, and when the path is generated by the server, the client has a function to set the corresponding connection and accommodates it. Also performs client path bandwidth management.

When a failure occurs, the failure recovery unit 12 performs a failure recovery using a failure recovery mechanism provided in the NMS in the domain (network) where the failure has occurred. However, there are cases where all failures cannot be recovered. Recovers by performing rerouting in another layer (other network).

Each of the network management systems 21 and 31 of the server and the client cooperates with the coordinator for processing such as path setting and canceling between networks when an operator (user or operator) issues an instruction from an operation terminal (not shown). It is performed through the system 1, but by giving each operator an access level, it is possible to permit access control only when the operator has a certain level or more.

[0017]

FIG. 2 shows an example of the structure of a table.
A. Is a configuration example of a network composed of five sub-networks; Is the network configuration information table (corresponding to the sub-network configuration information table 13a in FIG. 1); Is an access point correspondence table (corresponding to the correspondence table 13b in FIG. 1). A. In the example of the network configuration shown in FIG. As shown in each subnetwork ID
For 1 to 5, server / client type, server type (type such as WDM (wavelength division multiplexing), SDH, IP, etc.), ID of subnetwork connected to each subnetwork, and access point list ( Each piece of information in the list of access points to each connected sub-network is set as shown in the figure. The access point correspondence table contains C.I. As shown in (1), the connected server access point ID is set for the client access point ID, and the status (operating, unused, etc.) of each access point is registered for each item of each table.

FIG. And C.I. Is prepared in the coordinator system 1 based on the notification from the client NMS and the server NMS when a new facility is added.

FIG. 3 is a diagram for explaining the operation of setting a server path. The reference numerals 1 to 4 and 20, 21, 30, 31, and 40 in FIG. 3 are the same as those of the same reference numerals in FIG.

The operator operates the server NMS2 from the operation terminal.
When the server NMS 21 instructs a path setting between 4010 and 5001 (FIG. 3), the server NMS 21 sets a path between the terminal points 4010 and 5001 of the subnetwork 2 (FIG. 3). Thus, when the path setting in the sub-network 2 is completed, the server NMS 21 sends a path generation notification having the terminal point and the bandwidth information to the coordinator system 1 (FIG. 3). Coordinator system 1
Then, based on the terminal point information included in the generation notification, based on the access point correspondence table (C in FIG. 2), the terminal points 3-2003 and 4-5001 of the client sub-networks 3 and 4 connected to the respective access point correspondence tables. Is obtained, and a path setting instruction is issued to the client NMS 31 (FIG. 3). In response, the client NMS 31 sends the sub-network 3 and the sub-network 2 to the client SNMS 30 and the client SNMS 40, respectively.
The control is performed to set each path between the terminal points of the sub network 4 and between the terminal points of the sub network 4 and the sub network 2 to the operation state. The client path is VPI for ATM.
Fixed bandwidth for VCI and SDH, I for IP
This is a path based on the P address. Note that a process for determining whether to execute the path setting based on the authority (level) held by the operator who has issued the path setting instruction may be included.

FIG. 4 is a processing flow of the client NMS when setting a path. This processing 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 not, the process is terminated. If the access point does exist, the client is instructed to generate a client path to the NMS of the client subnetwork (S3).

FIG. 5 is an explanatory diagram of the operation of releasing the server path. The reference numerals 1 to 4 and 20, 21, 30, 31, and 40 in FIG. 5 are the same as those in FIG. 1 and FIG.

The operator operates the server NMS2 from the operation terminal.
When the server NMS 21 instructs the coordinator system 1 to check the operation state of the path 4010-5001 (see FIG. 5). ). The coordinator system 1 has a C.I. The operation status is checked with reference to the access point relation table as shown in FIG.
1 (see FIG. 5), and when not operating, instructs the client NMS 31 to release the path (see FIG. 5), and the client NMS 31 responds accordingly to the corresponding client access point (4). -5
The client SNMSs 30 and 40 are instructed to release the client path (between 001 and 3-2003) (FIG. 5).
of). When the release is completed, the client SNMS30,
When the release completion notification is sent from the server 40 to the coordinator system 1, the coordinator system 1
1 returns an unused operation check response to the server NMS.
At 21, pass cancellation is started.

FIG. 6 is a processing flow of the client NMS when releasing the path. This process is started in the client NMS that has received the path release notification from the server NMS, and upon receiving the notification, searches the access point relation table for a corresponding client access point (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 state is in use (S3). The server NMS is notified that the path is being used (S4), and if not, the server NMS is used.
(Step S5). In this case, it is possible to determine whether or not the path release notification can be made based on the authority (level) held by the operator who generated the path release notification.

In the path setting processing shown in FIGS. 3 and 4, when a new server path and a new client path are set, transition is made to the unused path, a new path is set on the client side, and a generation notification is sent to the coordinator system. , The state can be changed to the operation state. Also, as shown in FIGS. 5 and 6, when the client NMS releases the path, a release notification is sent to the coordinator system, and the state becomes unused when all the client paths are released. By making this unused, double setting can be prevented.

Next, the operation for setting from the client side will be described.

FIG. 7 is an explanatory diagram of an operation of setting a path between client networks by the client NMS. Reference numerals 1 to 4 and 20, 21, 30, 31, and 40 in FIG. 7 correspond to the same reference numerals in FIGS. 1, 3, and 5, and a description thereof will be omitted.

In FIG. 7, first, the client NMS
For 31, the operator operates the operation terminal or 4-6001 and 3-
When a path setting instruction between 7001 is given (FIG. 7), the client NMS 31 searches the table for an available route in the designated band (FIG. 7). If there is no route of the requested band, a path setting request is notified to the coordinator system 1 (FIG. 7). Upon receiving this, the coordinator system 1 instructs to search for network configuration information (B. in FIG. 2) based on the terminal point of the client (FIG. 7), and a subnetwork ID (the subnetwork 4 and the subnetwork 4 in FIG. 7). The sub-network 3) is obtained, and the access points to which the sub-networks 4 and 3 can be connected are obtained from the access point relation table (C in FIG. 2) (4010 and 5001 of the sub-network 2). Is instructed to the server NMS 20 (FIG. 7). After the path setting is completed, the coordinator system 1 instructs the client NMS 31 to generate a path for a path setting request notification.

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 process starts, and a subnetwork ID of the client path terminal point is searched from the network configuration information table (B in FIG. 2) (S in FIG. 8).
1). The access point of the server network connecting 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 unused access point, the client NMS is notified that the server path cannot be set (S4). Instruct path setting (S
5). Subsequently, the server path setting result is received from the server NMS (S6 in FIG. 8), and it is determined whether or not the content indicates 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 server path setting completion is notified to the client NMS, and the client NMS is notified. The client path is reset by the NMS (S9).

FIG. 9 is a diagram for explaining the operation when a failure occurs in the server network. 1 to 4 and 2 in FIG.
Reference numerals 0, 21, 30, 31, and 40 correspond to the same reference numerals in FIG. 1, FIG. 3, FIG.

In FIG. 9, when a failure occurs in the server network 2, when an alarm is detected in the server connected to the client, an alarm recovery stop instruction is issued to the client (FIG. 9). This instruction is issued to suppress the failure recovery operation on the client device side and give priority to the recovery on the server side. If the failure recovery on the server side has failed (FIG. 9), a failure recovery start instruction is sent to the client device (same).
Initiate disaster recovery on the client side.

If the failure recovery in the server network fails, the server NMS 21
Is notified of failure recovery failure (FIG. 9). The coordinator system 1 obtains the connected client subnetwork ID based on the terminal 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. , Server NMS
21 is instructed to search for a path route, and a detour route table (FIG. 1)
13c) (FIG. 9), and the state is determined to be searching. If successful, the coordinator system 1 records the state of the bypass route table as having a route.

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 the server NMS, and FIG. 12 shows the processing of the coordinator system It is a flow.

FIG. 10 shows processing in the server network (server device). When a failure is detected in the server device, the client network (client device)
Sends a failure recovery suppression message to the
1). Thereafter, it is determined whether the failure recovery processing has been completed (FIG. 10).
S2), upon termination, it is determined whether the failure has been recovered (S2).
3) If it is recovered, the process is terminated, but if it is not recovered, a failure recovery start message is transmitted to the client device (S4).

When a failure is detected in the server device, FIG.
Are started, and at the same time as the processing of A. As shown in FIG. 12, the server NMS notifies the server NMS. The failure notification is sent to the coordinator as shown in (1). The coordinator system executes the processing flow shown in FIG. 11, uses the search function of the path setting operation shown in FIG. 8 described above, searches for a detour path in which an access point has been changed, and stores it in the detour path table (13c in FIG. 1). Record.

Referring to FIG. 11, when the coordinator system receives an alarm notification, it searches the network configuration information table for the subnetwork ID of the client connected to the failed server path terminal point (S1 in FIG. 11). Next, the access point of the server network connecting the sub-networks is searched from the access point correspondence table (S2 in FIG. 11), and it is determined whether or not there is an unused access point (S3). If there is, the server NMS is instructed to search for a path between the access points of the server (S4). Thereafter, a server path search result is received from the server NMS (S5 in FIG. 11), and based on the result, it is determined whether there is a path route (S6). If not, the process returns to S2. The route is recorded in the detour path table (S7), it is determined whether or not the detour paths of all the failed paths are recorded (S8), and when the detour paths of all the failed paths are recorded, the process is terminated, but all are recorded. If not, the process returns to S2.

When a failure of the server shown in FIG. 10 is detected,
If the failure recovery on the client side fails, the client NMS executes the processing flow for failure recovery failure shown in FIG. 13 and notifies the coordinator system of failure recovery failure.

FIG. 14 is a processing flow of the coordinator system when a notification of failure recovery failure has been received. When the client failure recovery failure notification is received, it is determined whether or not there is a detour path corresponding to the detour path table (S in FIG. 14).
1) If not, the process is terminated, but if there is, a path setting instruction is issued to the server NMS for the route in the bypass route table (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 status 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 instructs the client path resetting (S6). ).

FIG. 15 is a processing flow in the case where the client has succeeded in recovery from a failure in the processing flow of FIG. FIG. Is a process in the client NMS. When the failure recovery in the client NMS succeeds, the coordinator is notified of the failure recovery, and the process ends. B of FIG. Is a process in the coordinator, and A. When the coordinator receives the notification of the success of the client failure recovery by the above processing, the corresponding detour path table is deleted, and the processing ends.

Lastly, the coordinator system gives the users (operators) of the server NMS and the client NMS an access level (weight of position) in advance, and performs access control to another network management system (NMS). The access level is checked, and management is performed so that access control can be performed only when the access level is equal to or higher than a predetermined level.

[0041]

According to the present invention, ATM, SDH, I
When a client network layer such as P is connected, path setting and failure recovery processing are speeded up by coordinating paths and failure recovery between layers, and network resources are reduced by sharing spare resources. It is possible to construct an efficient system.

[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 explanatory diagram of an operation of setting a server path.

FIG. 4 is a diagram showing a processing flow of a client NMS when setting a path.

FIG. 5 is an explanatory diagram of an operation of releasing a server path.

FIG. 6 is a diagram showing a processing flow of a client NMS at the time of releasing a path.

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 a coordinator system.

FIG. 13 is a diagram showing a processing flow when failure recovery is unsuccessful.

FIG. 14 is a diagram illustrating a processing flow of the coordinator system when a notification of failure recovery failure has been received;

FIG. 15 is a diagram showing a processing flow in a case where the client side has successfully recovered from a failure in the processing flow of FIG. 10;

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 Message communication part between NMSs 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

 ──────────────────────────────────────────────────続 き Continued on the front page F term (reference) 5K030 GA12 HD07 KA07 MA01 MD07 5K035 BB04 GG13 5K051 AA03 AA09 CC02 FF01 FF17 GG01 LL00 9A001 CC07 JJ27 LL05 LL09

Claims (10)

[Claims] 1. A network management system for managing a plurality of networks, comprising a network management system for setting and canceling a path, and a correspondence between access points between a client network and a server network. A coordinator system including a management unit for managing the network, a path management unit, and a failure recovery unit. The coordinator system connects a network configuration information table including information configuring the server network and the client network, and connects the subnetwork. A network management system, comprising: a correspondence table including a correspondence relation between access points to be accessed and a state of the access point. 2. The communication system according to claim 1, wherein the path management unit of the coordinator system determines a terminal point of the notified server path as an access point in response to a server path generation notification from a network management system of the server network. A network management system for converting a correspondence table into a terminal point of a client network, and instructing a network management system of the client network to generate a client path. 3. The system according to claim 1, wherein the path management unit of the coordinator system receives the notification of the release of the path of the client network before the notification of the release of the path from the network management system of the server network. A network management system in which a path release is instructed to a management system of a client network when release is possible and a path release is permitted to a network management system of a server network. 4. The method according to claim 2, wherein the state of the corresponding path in the correspondence table is changed to "in use" at the time of setting the path, and the correspondence table is changed at the time of releasing the path. A status of a corresponding path of the network management system is changed to unused. 5. The system according to claim 1, wherein the path management unit of the coordinator system, upon receiving a path setting request from a network management system of the client network, searches the network configuration information table to identify a network at a client path terminal point. The access point of the identified network is searched from the correspondence table to detect an unused access point, a path setting instruction is issued to the server network management system, and a result of the completion of the path setting is reported to the server network. Upon receipt from the network management system, 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. Network management system 6. The server management system according to claim 1, wherein, in response to the occurrence of a failure in the server network, the network management system of the server network sends an instruction to stop the failure recovery operation to the client network and recovers the failure in the server network. A network management system which starts, and when failure recovery in a server network fails, sends a failure recovery start instruction to a client network to start failure recovery in the client network. 7. The server management system according to claim 6, wherein a failure recovery operation in said server network is started and said network management system of said server network is notified, and the network management system of said server network sends a failure notification to a coordinator system. The coordinator system uses a search function of the path management unit according to claim 5 to identify a client network connected to an end point of a server path, and establish a connectable access point between the client and server networks. A network which is searched from the correspondence table, instructs a server network system to search for a route via the searched access point, and records the searched route as recorded in a bypass route table and uses the route. Management system. 8. The method according to claim 6, wherein when the failure recovery in the client network fails, the client network management system notifies the coordinator system of the failure recovery failure, and the coordinator system determines that there is a route in the detour path table. A network management system which, when recorded, instructs a client network management system to start recovery from a fault again. 9. The method according to claim 6, wherein when the failure recovery is successful in the server network, a failure recovery success notification is sent from the client network management system to the coordinator system. A network management system for instructing a server network management system to cancel a route in a route table. 10. The coordinator system according to claim 1, wherein the coordinator system assigns an access level to each operator of the server network management system or the client network management system in advance and mutually sends the network management system to another network management system. A network management system for checking whether a required access level is provided when performing the above access control.