JP4678778B2 - Multi-layer network operation management system and computer program - Google Patents

Description

  The present invention relates to a multi-layer network operation management system and a computer program, and more particularly, to a multi-layer network operation management system and a computer program that can accurately grasp the operation status of an MPLS / GMPLS network system.

  In an MPLS / GMPLS network system in which an MPLS (Multi Protocol Label Switching) network and a GMPLS (Generalized Multi Protocol Label Switching) network coexist, the network path (label switch path, hereinafter simply referred to as a path) of the requested bandwidth is end- In order to set the end-to-end, each network node (hereinafter simply referred to as a node) has a link (TE (Traffic Engineering) link) information (bandwidth, link attributes, reachability, etc.) and path between nodes used for the path. Control signals for setting are exchanged. This exchange of control information is performed on a transmission line through which actual data traffic flows using a dedicated control protocol or on a dedicated control signal network provided outside.

  The node holds only the information (path information) of the path passing through its own node, and this path information has a hierarchical structure in which the upper layer path is set on the lower layer path.

  Patent Document 1 collects and stores path information from a plurality of routers that are components of the network in order to appropriately grasp the path setting status in the MPLS network, and selectively stores path information according to designation from the user. A network monitoring device that reads out and graphically displays a path route according to the path information is described.

  In this network monitoring device, information on the traffic flowing through the path is selectively displayed in correspondence with the graphic display of the path route, and if there is a vertically related path, the path route is correlated. It is also possible to display graphics.

  Conventionally, when managing an MPLS / GMPLS network system in which an MPLS network and a GMPLS network are mixed, a different management system is installed for each layer, and each management system manages the layer individually.

  FIG. 24 shows a conventional management system of an MPLS / GMPLS network system. The MPLS / GMPLS network 40 has a configuration in which an MPLS network 60, a GMPLS network 70, and an MPLS network 80 are sequentially connected. The MPLS network 60, the GMPLS network 70, and the MPLS network 80 are individually managed.

That is, the MPLS network 60, the GMPLS network 70, and the MPLS network 80 are respectively managed by the router monitoring device 130, the WDM monitoring device 140, the transmission node monitoring device 150, and the router monitoring device 160 through the management planes (management networks) 100 and 110120. .
JP 2005-286818 A

  The network monitoring device described in Patent Document 1 monitors a network path using MPLS in particular. When managing an MPLS / GMPLS network system in which an MPLS network and a GMPLS network are mixed, as shown in FIG. 24, it is conceivable to install and manage different management systems for each layer. Since it is managed individually, the operation status in the entire network could not be accurately grasped.

  For this reason, even if a failure occurs in the TE link or node, it is difficult for the operator to grasp the identification of the failure point on different layers on the system side. In addition, when a failure occurs, a large number of alarm information is notified from the node, and it is necessary to analyze the large number of alarm information to identify the location of the failure, requiring a lot of labor and time.

  An object of the present invention is to provide a multi-layer network operation management system and a computer program capable of accurately grasping the operation status of an MPLS / GMPLS network system.

In order to solve the above problems, the present invention comprises a management server and a database, and the management server detects node existing in an MPLS / GMPLS network in which an MPLS network and a GMPLS network are mixed, and the node TE link between node information identification registration means for identifying node attributes detected by the detection means to obtain node attribute information, registering node information including the node attribute information in the database, and nodes of the MPLS / GMPLS network TE link information acquisition means for acquiring information, TE link information registration means for registering TE link information acquired by the TE link information acquisition means in the database, and path information of paths set in the MPLS / GMPLS network. Path information acquisition means to acquire, and analysis of path information acquired by the path information acquisition means , An analysis unit that obtains inclusion relation information that associates a hierarchical relation between an MPLS path and a GMPLS path, and a path that registers path information acquired by the path information acquisition unit and inclusion relation information obtained by the analysis unit in the database. Information / inclusion relation information registration means, and display control means for displaying a map of MPLS / GMPLS network objects based on node information, TE link information , path information and inclusion relation information registered in the database It is characterized by.

  Further, the present invention is characterized in that the node detection means, the TE link information acquisition means, and the path information acquisition means respectively perform node detection, TE link information acquisition, and path information acquisition through a management network.

  Further, the present invention is characterized in that the map display is performed by at least one of the management server and an external server.

  Further, the present invention is characterized in that when the object is selected on the map display, the display control means displays detailed information of the object. In the present invention, the management server further includes a failure management means for identifying a failure location by linking failure information transmitted from a node when a failure of a node, link or path occurs and information registered in the database The display control means displays the fault location specified by the fault management means on a map display or as a list.

  The present invention also provides failure recovery management means for identifying failure recovery by the management server linking failure recovery information sent from a node with failure recovery by path switching and information registered in the database; A path information acquisition unit for recovery that acquires at least path information after path switching out of path information before and after path switching, and the display control unit performs the recovery when the fault recovery is specified by the fault recovery management unit The route information acquired by the hour path information acquisition means is displayed on a map display or as a list.

  The present invention can also be realized as a computer program mounted on a management server that manages the operation of an MPLS / GMPLS network system.

  In the present invention, nodes existing in the MPLS / GMPLS network are detected, node information including node attribute information is generated, and TE link information and path information are acquired. For the path, the acquired path information is analyzed, and inclusion relation information representing the inclusion relation between the MPLS path and the GMPLS path is generated.

  Based on the node information, TE link information, and path information / inclusion relation information, the objects that exist in the MPLS / GMPLS network are displayed as a map, so the operation status of the MPLS / GMPLS network can be accurately grasped and the network map can be created. It can be displayed. In particular, it is possible to associate hierarchical relationships with the inclusion relationship information between MPLS paths and GMPLS paths, making it easier to understand the dependency relationships between layers on the MPLS / GMPLS network, and for network reconfiguration and trouble. It is possible to provide effective information for relocation.

  In addition, by configuring the management server to detect nodes through the management network and acquire node information, the node attributes of each node can be automatically collected and identified, allowing dynamic topology information acquisition It becomes.

  In addition, by configuring the map display so that the detailed information is displayed when an object is selected, it is possible to display the network map without disturbing the visibility of the network map, and the detailed information is displayed when necessary. It is possible to display only.

  In addition, it is possible to identify the location of failure on the network and the cause of failure by configuring so that a large number of failure information sent from a node when a failure of a node, link or path occurs is associated with information registered in the database. . Furthermore, failure recovery and path switching can be specified. As a result, it is possible to appropriately notify the operator of the occurrence or failure recovery of the failure.

  The present invention will be described below with reference to the drawings. FIG. 1 is a configuration diagram showing an embodiment of a multi-layer network operation management system according to the present invention. This multi-layer network operation management system includes a management server 10, a database 20, and a management client 30, and manages the operation of the MPLS / GMPLS network 40. The MPLS / GMPLS network 40 has a configuration in which an MPLS network 60, a GMPLS network 70, and an MPLS network 80 are sequentially connected.

  The management server 10 has a multi-layer topology management function. In the inter-multilayer topology management function, first, nodes existing in the MPLS / GMPLS network 40 are detected through the management plane (management network) 50, and node information is collected from each detected node. Furthermore, topology information such as TE link information and path information is also collected.

  By collecting information through the management network 50, there is no need to monitor control signals in the dedicated control network or actual traffic transmission path, so node information, TE link information, path information in real time without affecting the network. Topology information such as can be collected.

Further, the management server 10 recognizes the topology of the MPLS / GMPLS network 40 based on the collected topology information, and displays the network map and its detailed information.
The database 20 holds information collected and processed by the management server 10.
The management client 30 has a function of acquiring various information from the management server 10 and the database 20 and displaying a network map equivalent to the management server 10 and its detailed information.

  The GMPL network 70 that constitutes the MPLS / GMPLS network 40 includes GMPLS nodes 71 to 73 that are GMPLS path start points, end points, and via nodes corresponding to the GMPLS protocol, and WDM nodes that are compatible with the GMPLS protocol and become GMPLS path via nodes. 74,75. In general, WDM nodes are also arranged between the GMPLS nodes 71 and 73 and between the GMPLS nodes 72 and 73, but they are not shown. The GMPLS nodes 71 to 73 are configured by OXC.

  The MPLS networks 60 and 80 include MPLS nodes 61 to 63 and 81 to 83 that correspond to the MPLS protocol and serve as start points, end points, and transit nodes of the MPLS path.

  At the boundary between the MPLS networks 60 and 80 and the GMPL network 70, both the MPLS protocol and the GMPLS protocol are supported, and the GMPLS path start point, end point, and transit node become the MPLS path start point, end point, and transit node. Functional MPLS / GMPLS nodes 76 and 77 are arranged.

  In addition to the above functions, one of the MPLS / GMPLS nodes 76 and 77, for example, the MPLS / GMPLS node 76, generally uses the TE link information between the nodes in the MPLS / GMPLS network 40 in the management server 10 for network management. It functions as a master MPLS / GMPLS node that can be provided using SNMP (Simple Network Management Protocol), which is a standard protocol, or XML (eXtensible Markup Language), which is a general-purpose data description language. A plurality of TE links exist on the transmission path between the nodes.

  The management network (management plane) 50 exchanges information between MPLS nodes 61 to 63, 81 to 83, MPLS / GMPLS nodes 76 and 77, GMPLS nodes 71 to 73, the management server 10, the management client 30, and the database 20. Used for.

For example, as shown in FIG. 2, the management server 10 has a multi-layer topology management function that performs topology discovery in the MPLS / GMPLS network 40 by the following processes S1 to S6, and performs topology recognition and MAP display. It is.
S1: Node detection / information (node attribute information) registration process
S2: Data link information registration process
S3: TE link information registration process
S4: GMPLS path information registration process
S5: MPLS path information registration process
S6: MAP display processing

Hereinafter, the six processes S1 to S6 will be described in order. Node detection / information registration process (S1)
In the node detection / information registration process (S1), a node in the MPLS / GMPLS network 40 is detected and a node including node attribute information indicating whether each detected node is a GMPLS node, a WDM node, an MPLS / GMPLS node, or an MPLS node. Register the information in the database 20.

  FIG. 3 is a flowchart showing a specific example of the node detection / information registration process (S1). The management server 10 first detects a node in the MPLS / GMPLS network 40 (S31). This can be realized by sequentially checking responses using SNMP Ping for the nodes in the MPLS / GMPLS network 40 described in the discovery configuration file.

  When there is a response from the node to SNMP Ping, SNMP information such as sysOID is collected from the response (S32). The sysOID is determined and registered in advance for each node device.

  Next, the sysOID collected from each node is examined to determine whether sysOID = GMPLS node, sysOID = WDM node, sysOID = MPLS node, MPLS / GMPLS node, and others (S33).

  If it is determined in S33 that sysOID = GMPLS node (S34), the node is registered as a GMPLS node in the database 20 (S35). If it is determined that sysOID = WDM node (S36), the node is WDM Register as a node in the database 20 (S37). This registration is performed in correspondence with the ID (Node-ID) of each node.

  If it is determined in S33 that sysOID = MPLS node, MPLS / GMPLS node, etc., it is further determined whether the node is an MPLS / GMPLS node based on the collected SNMP information ( S38). If the node is an MPLS / GMPLS node, there will be a GMPLS-TE MIB (Management Information Base) or GMPLS-LSR MIB response from that node, so check whether there is a GMPLS-TE MIB or GMPLS-LSR MIB response. Can determine MPLS / GMPLS nodes. If it is determined that the node is an MPLS / GMPLS node, the node is registered in the database 20 as an MPLS / GMPLS node (S39).

  If it is determined in S38 that the node is not an MPLS / GMPLS node, it is further determined whether or not the node is an MPLS node (S40). When the node is an MPLS node, there is a response of MPLS-TE MIB or MPLS-LSR MIB from the node. Therefore, the MPLS node can be determined by checking whether or not there is a response of MPLS-TE MIB or MPLS-LSR MIB. If it is determined that the node is an MPLS node, the node is registered as an MPLS node in the database 20 (S41). If it is determined in S40 that the node is not an MPLS node, the node is not registered in the database 20 because it is not a managed node.

  As described above, in the node detection / information registration process (S1), for GMPLS nodes and WDM nodes that can be determined from sysOID, each node is determined using sysOID, and for MPLS nodes, MPLS / GMPLS nodes, and other nodes Provides a discrimination criterion so that nodes other than the MPLS node and the MPLS / GMPLS node are not detected, and the MPLS node and the MPLS / GMPLS node are discriminated by detecting only those that match the discrimination criterion.

  In the MPLS / GMPLS network 40 of FIG. 1, nodes 71 to 73 are determined as GMPLS nodes, nodes 74 and 75 are determined as WDM nodes, nodes 61 to 63, 81 to 83 are determined as MPLS nodes, and nodes 76, 77 is determined to be an MPLS / GMPLS node. As a result, node attribute information indicating whether the node is a GMPLS node, a WDM node, an MPLS / GMPLS node, or an MPLS node is registered in the database 20.

2. Data link information registration process (S2)
WDM nodes 74 and 75 exist between the GMPLS nodes 71 and 72 in the GMPLS network 70 of FIG. In this case, as shown in FIG. 4, there are two types of TE links: a TE link between a GMPLS node and a GMPLS node and a TE link between a GMPLS node and a WDM node.

  In operation management, the management server 10 side is required to manage the TE link between the GMPLS node and the GMPLS node and the TE link between the GMPLS node and the WDM node as the same TE link. In the data link information registration process (S2), as pre-processing of the TE link information registration process (S3), data link information that exists between the GMPLS node and the WDM node is acquired, and matching of two types of TE links is performed. Register in the database 20 as a key.

  FIG. 5 is a flowchart showing a specific example of the data link information registration process (S2). The management server 10 first determines whether there is a WDM node (S51). The WDM node has already been determined in S36 of FIG. If it is determined in S51 that there is no WDM node, the two types of TE links do not exist, and the data link information registration process is terminated.

  If it is determined in S51 that a WDM node exists, the data link information is acquired from the LMP-MIB (RFC4327) sent from the WDM node according to SNMP (RFC4327), and further the LMP-MIB sent from the GMPLS node Data link information is acquired from (RFC4327) (S53). The acquired data link information is registered in the database 20 (S54).

3. TE link information registration process (S3)
In the TE link information registration process (S3), TE link information between nodes in the MPLS / GMPLS network 40 is acquired and registered in the database 20. Therefore, the management server 10 uses a TE link that conforms to the OSPF-TE GMPLS extension information from a master MPLS / GMPLS node that can provide TE link information between nodes in the MPLS / GMPLS network 40, for example, the MPLS / GMPLS node 76. Information (RFC3630, RFC4203) is acquired and registered in the database 20.

  TE link information can be obtained from MIB (draft-otani-ccamp-gmpls-ospf-mib-01.txt), which is an extension of the existing OSPF-MIB sent according to SNMP, to OSPF-TE. It can also be obtained using other data description languages. The master MPLS / GMPLS node and the slave MPLS / GMPLS node are assumed to be registered in advance. If the master MPLS / GMPLS node does not exist on the MPLS / GMPLS network 40, the master MPLS / GMPLS node and the slave MPLS / GMPLS node are similar. Get TE link information by processing.

  If a WDM node exists, two types of TE links are matched and merged according to the above-described request, and are registered in the database 20 as the same TE link. The TE link information between the GMPLS node and the WDM node is not advertised to each node in the GMPLS network, so it cannot be obtained from the master MPLS / GMPLS node or slave MPLS / GMPLS node, but is sent from the GMPLS node and WDM node. It can be obtained from TE-LINK-MIB (draft-ietf-mpls-telink-mib-07).

  FIG. 6 is a flowchart showing a specific example of the TE link information registration process (S3). The management server 10 first determines whether there is a master MPLS / GMPLS node on the MPLS / GMPLS network 40 (S61), and if it is determined that there is no master MPLS / GMPLS node, the slave MPLS / GMPLS node is determined. It is determined whether a GMPLS node exists (S62).

  If it is determined that neither a master MPLS / GMPLS node nor a slave MPLS / GMPLS node exists, the TE link information registration process (S3) is terminated. If it is determined that a master MPLS / GMPLS node exists, Obtain TE link information from an MPLS / GMPLS node, and if it is determined that there is no master MPLS / GMPLS node and there is a slave MPLS / GMPLS node, obtain TE link information from the slave MPLS / GMPLS node ( S63).

  Since TE link information between GMPLS node and GMPLS node is advertised to each node existing in the GMPLS network using OSPF, this TE link information can be acquired from the master MPLS / GMPLS node or slave MPLS / GMPLS node. .

  When the WDM node exists, TE link information between the GMPLS node and the WDM node is acquired from the GMPLS node and the TE-LINK-MIB (draft-ietf-mpls-telink-mib-07) from the WDM node.

  Of the TE link information acquired in this way, TE link information other than information on the TE link between the GMPLS node and the WDM node is registered in the database 20 (S64).

  Next, it is determined whether or not a WDM node exists (S65). Here, when it is determined that there is no WDM node, the TE link information registration process (S3) ends. In this case, only the TE link information registered in S64 exists in the database 20.

  If it is determined in S65 that a WDM node exists, TE link information is collected from the WDM node (S66), and TE link information is collected from a neighboring GMPLS node (S67), and the GMPLS node-WDM node The TE link information is registered in the database 20 (S68).

  Next, the two types of TE links shown in FIG. 4 are matched and merged from the TE link information registered in S64 and S68 (S69). The merged two types of TE links are registered in the database 20 as the same TE link (S70).

4). GMPLS path information registration process (S4)
In the GMPLS path information registration process (S4), GMPLS path information is acquired, and settings on the start node side and the end node side are associated with each other and then registered in the database 20.

  FIG. 7 is a flowchart showing a specific example of the GMPLS path information registration process (S4). The management server 10 receives SNMP information (MPLS-TE-MIB, MPLS-LSR MIB, GMPLS-TE-MIB, GMPLS) from the nodes registered as MPLS / GMPLS nodes or GMPLS nodes in the node detection / information registration process (S1). -GMPLS path information is acquired from (LSR MIB) (S71).

  In the GMPLS path, there is bidirectionality between the start point / end point MPLS / GMPLS nodes, and on the management server 10 side, it is necessary to associate the settings on the start point node side and the end point node side. In the GMPLS path identification process (S72), this association is performed using the GMPLS path information acquired in S71. In the GMPLS path identification process (S72), by performing this association process based on the GMPLS path information, the setting of the start point node and the end point node can be discriminated from the setting of the same path. The GMPLS path information identified in the GMPLS path identification process (S72) is registered in the database 20 (S73).

  FIG. 8 is an explanatory diagram of GMPLS path information acquisition and identification processing (S71, S72) procedures. Here, it is assumed that a GMPLS path is set between the MPLS / GMPLS node 76 and the MPLS / GMPLSS node 77, and an MPLS path is set between the MPLS node 61 and the MPLS node 81. GMPLS nodes 71 and 72 exist between the MPLS / GMPLS node 76 and the MPLS / GMPLS node 77.

In (1) to (8) of FIG. 8, the following processes (1) to (8) are performed.
(1) Read MPLS-TE-MIB and RFC1213-MIB from MPLS / GMPLS node 76.
(2) The index (41.79.842150471.842150472) of the entry whose second index (mplsTunnelInstance) is not 0 is read from the entries whose mplsTunnelRole is head (1) in the MPLS-TE-MIB. This entry contains an index into the tunnel route table. An entry whose mplsTunnelRole is head (1) is a GMPLS path.
(3) Read the value (84) of mplsTunnelARHopTableIndex having the read index (41.79.842150471.842150472).
(4) From the mplsTunnelARHopIpAddr, all the entries whose first index (mplsTunnelARHopListIndex) is the same as the value (84) read in (3) are read and stored as the path of the GMPLS path.
(5) An index ipAdEntIfIndex (200.200.200.200) having a value matching the value (12) of mplsTunnelIfIndex is obtained from RFC1213-MIB, and the index is set as IngressTunnelID. Also, use ipAdEntNetMask to determine the subnetwork address. In this case, the subnetwork address is 200.200.200.0.
(6) Egress (termination) MPLS / GMPLS node (64 64 01 06) is obtained from the GMPLS path route obtained in (4). (64 64 01 06) is expressed in hexadecimal, which indicates the MPLS / GMPLS node 77. (64 64 01 02) and (64 64 01 04) indicate GMPLS nodes 71 and 72, respectively. Thus, it can be seen that the route of the GMPLS path passes through the MPLS / GMPLS node 76-GMPLS node 71-GMPLS node 72, and the termination is the MPLS / GMPLS node 77.
(7) Read MPLS-TE-MIB and RFC1213-MIB from the MPLS / GMPLS node 77 at the egress (termination) obtained in (6), and ipAdEntIfIndex (200.200) of the same subnetwork as the subnetwork of IngressTunnelID obtained in (5) .200.201).
(8) The mplsTunnelIfIndex that matches the value (13) of ipAdEntIfIndex obtained in (7) is obtained from the MPLS-TE-MIB. The mplsTunnelDescr (GSR SUITA t42) having the index (42.0.842150472.842150471) of the mplsTunnelIfIndex obtained in this way is set as ReverseTunnel and is associated with IngressTunne.
(9) Only the last entry in the route that is in the local IpAddress or remoteIpAddress of the TE link is added to the route.

5. MPLS path information registration process (S5)
In the MPLS path information registration process (S5), the MPLS path information is acquired, the inclusion relation with the GMPLS path is analyzed, and the MPLS path information including the inclusion relation information obtained thereby is registered in the database 20.

  FIG. 9 is a flowchart showing a specific example of the MPLS path information registration process (S5). The management server 10 acquires MPLS path information from SNMP information (MPLS-TE MIB, MPLS-LSR MIB) from the nodes registered as MPLS nodes in the node detection / information registration process (S1) (S91).

  Next, the inclusion relationship between the GMPLS path and the MPLS path is analyzed using the path information of the MPLS path and the tunnel address of the GMPLS path information registered in the GMPLS path information registration process (S4) as keys. Inclusion relation information is obtained by this analysis, and MPLS path information including this inclusion relation information is registered in the database 20.

  Specifically, it is determined whether the MPLS path route information ID and the Tunnel ID of the GMPLS path match (S92). If they match, the MPLS path is included in the GMPLS path. And the inclusion relation information between the paths together with the MPLS path information is registered in the database 20 (S93). If the MPLS path route information ID and the GMPLS path Tunnel ID do not match, only the MPLS path information is registered in the database 20 (S94).

FIG. 10 is an explanatory diagram of the MPLS path information acquisition and inclusion relation analysis processing procedure. In the drawings (1) to (5), the following processes (1) to (5) are performed, respectively.
(1) Read MPLS-TE-MIB from MPLS node 61.
(2) Read the index (22.2881.842150401.842150402) of the entry whose second index (mplsTunnelInstance) is not 0 from the entries whose mplsTunnelRole is head (1). An entry whose mplsTunnelRole is head (1) is an MPLS path.
(3) Read the value (1426353688) of mplsTunnelARHopTableIndex having the read index (22.2881.842150401.842150402).
(4) From the mplsTunnelARHopIpv4Addr, read all the entries whose first index (mplsTunnelARHopListIndex) is the same as the value read in (3) and store it as the MPLS path route.
(5) An ipAdEntIfIndex having a value matching the value (13) of mplsTunnelIfIndex is obtained, and the index (150.150.150.150) is set as ingressTunnelID.
(6) A GMPLS path having the same EgressTunnel ID or IngressTunnel ID as the IP address (200.200.200.201) of the second GMPLS node 85 in the path of the MPLS path is registered as a parent GMPLS path, that is, a GMPLS path including the MPLS path.

6). MAP display processing (S6)
In the MAP display process, node information, TE link information, MPLS path information, and GMPLS path information registered in the database 20 are read, and a network map including the node, TE link, MPLS path, and GMPLS path is displayed (MAP display). The MAP display can be performed on the management server 10, but can also be performed on the management client 30 in response to a request from the management client 30.

  FIG. 11 is an ER (Entity Relation) diagram showing the relationship between objects (nodes, TE links, GMPLS paths, MPLS paths) managed by the management server 10. FIG. 11 shows the inter-object relevance in the case where there are 0 to N TE links for nodes 2 and 0 to N GMPLS paths for 2 TE links. Since the management server 10 has the relevant object information in this way, operation management between multiple layers becomes possible.

  In the MAP display, in order to improve visibility and facilitate operation management, it is preferable to display objects existing between the same nodes as objects representing them. For example, when there are a plurality of TE links, MPLS paths, and GMPLS paths between any two nodes, they are displayed as one representative line. When there is an MPLS path segment included in a GMPLS path segment between any two nodes, the MPLS path segment is not displayed and only the GMPLS path segment is displayed.

  Detailed attribute information of each object on the network map can be displayed, for example, in a separate window by selecting the object displayed in the MAP (clicking operation at the object position). In addition, by selecting an object of a certain segment, a plurality of TE links and paths passing through the segment can be displayed in a list form. Further, by selecting an arbitrary GMPLS path on the GMPLS path list display, a list of MPLS paths included in the GMPLS path can be displayed.

  FIG. 12 is a diagram showing a display form of the TE link and path. In this display form, the TE link, the MPLS path, and the GMPLS path are displayed in different colors by a thin line, a middle thick line, and a thick line, respectively. The MPLS path is set between the MPLS node 61 and the MPLS node 81, and the GMPLS path is set by the path of the MPLS / GMPLS node 76-GMPLS node 71-GMPLS node 73, 72-MPLS / GMPLS node 77.

  Since the MPLS path is included in the GMPLS path between the MPLS / GMPLS node 76 and the MPLS / GMPLS node 77, the MPLS path between them is not displayed. In addition, the Node-ID (Router ID) of each of the nodes 61, 71 to 73, 76, 77, 81 serving as routers is displayed in parentheses, and the address of each TE link is displayed.

  For example, the TE link between GMPLS node 71 (10.10.10.1) and MPLS / GMPLS node 76 (10.10.10.4) has a link ID (LinkID) of 1, the start router ID (10.10.10.1), and the end router ID (10.10.10.4), the start point TE link address is (1.1.2.2), and the end point TE link address is (1.1.2.1). The name of the TE link is given as (10.10.10.1_1.1.2.2_1_10.10.10.4_1.1.2.2), for example, according to (starting router ID_starting TE link address_LinkID_endpoint router ID_endpoint TE link address) .

  By clicking the TE link display portion on the MAP display of FIG. 12, the detailed information of the TE link is displayed in a list form. FIG. 13 shows a list of detailed information of the TE link. For example, when the display part of the TE link between the GMPLS node 71 and the MPLS / GMPLS node 76 is clicked, the information in the upper part of FIG. 13 is displayed in another window. As indicated by the circled numbers, the middle information in FIG. 13 is detailed information of the TE link between the GMPLS node 71 and the GMPLS node 73, and the lower information is the MPLS / GMPLS node 76-MPLS node. It is the detailed information of the TE link between 61. When any one TE link line is clicked, detailed information of all TE links may be displayed. In that case, the correspondence between the TE link and the detailed information is understood.

  FIG. 14 is a diagram showing a display form in which a GMPLS path is displayed in addition to the display of FIG. Here, the detailed information of the GMPLS path is displayed in a list by clicking the display part of the GMPLS path. FIG. 15 shows a list of GMPLS path detailed information. Further, by clicking a path item in the list display, detailed information of MPLS paths included in the GMPLS path is displayed in a list form.

  FIG. 16 is a diagram showing a display form in which the inclusion relationship between the MPLS path and the GMPLS path is displayed in addition to the display of FIG. Here, by clicking on the display part of the MPLS path included in the GMPLS path, the detailed information of the MPLS path is displayed in a list form. FIG. 17 shows a list of MPLS path detailed information.

  Although the multi-layer topology management function of the management server 10 has been described above, the management server 10 can be further provided with a fault management function.

  When a failure occurs, the management server 10 links the failure information (alarm) notified from the node with the information held by the database 20 (node information, TE link information, GMPLS path information, MPLS path information). Identify the fault location in more detail.

  FIG. 18 is a conceptual diagram showing fault management (according to fault occurrence) according to the present invention. The management server 10 centrally manages the nodes, TE links, GMPLS paths, and MPLS paths of the entire MPLS / GMPLS network 40, and functions as a multilayer monitoring apparatus.

For example, as shown in FIG. 19, the fault management function (according to the occurrence of a fault) executes processes S191 to S194 to display the fault location of the MPLS / GMPLS network 40 on the map.
S191: Alarm filter processing
S192: Alarm analysis processing (correlation processing)
S193: Event process processing
S194: Map display processing

The above four processes S7 to S10 will be described in detail. Alarm filter processing (S191)
In alarm filter processing, when an alarm arrives from a node, alarms that are not managed are sorted. An alarm filter policy (filter processing rule) is set in advance. There are many nodes in the MPLS / GMPLS network 40, and various types of information are sent from the nodes, but nodes and information that are not managed or not required are excluded from management by alarm filtering. Thus, the processing load of alarm analysis can be reduced.

2. Alarm analysis processing (S192)
In the alarm analysis processing, failure analysis is performed based on the alarm distributed in the alarm filter processing and the information in the database 20 (node information, TE link information, GMPLS path information, MPLS path information), and the failure location is identified. The failure analysis rule is set in advance. In addition, when a failure location is specified only by alarm filter processing, failure analysis is unnecessary.

  For example, in the MPLS / GMPLS network 40 shown in FIG. 20, when an optical interruption failure occurs between WDM nodes, an alarm (TRAP: trap) is sent from each node. The management server 10 receives these alarms and analyzes the cause of the failure according to the failure analysis rule.

  FIG. 21 is a conceptual diagram of an example of a failure analysis rule. This failure analysis rule is set so that failure analysis is performed with priority given in the order of data link, TE link, and path. When a high priority alarm is received, the alarm is fundamental. Identified from the faulty location.

3. Event process processing (S193)
In the event process process, event information is created based on the alarm of the fault location identified by the alarm analysis process.

4). Map display processing (S194)
In the map display process, the fault location is displayed on the map or in a list format based on the event information from the event process process. This display can be performed on the management server 10 or the management client 30 (FIG. 1).

  The failure management in the management server 10 can be provided with a function to display not only a function for identifying and displaying a failure location when a failure occurs, but also a route information before and after path switching due to failure recovery.

  FIG. 22 is a conceptual diagram showing failure management (according to failure recovery) according to the present invention. When the GMPLS path is restored by the restoration or protection function (recovery operation between nodes), failure recovery information (recovery alarm) is sent immediately from the starting node of the GMPLS path. Based on the recovery alarm, the management server 10 executes processes S231 to S236, for example, as shown in FIG.

  First, in the alarm filter process (S231), when a recovery alarm arrives from a node, a recovery alarm that is not a management target is assigned according to the filter processing rule. In the alarm analysis process (S232), based on the recovery alarm distributed in the alarm filter process and the database 20 information (node information, TE link information, GMPLS path information, MPLS path information), failure recovery analysis is performed according to the analysis processing rules. To identify failure recovery by path switching. In event process processing (S233), event information for failure recovery is created.

  In the management server 10, it is necessary to search for a new route of the restored GMPLS path. Therefore, synchronization processing (TE link, GMPLS and MPLS path synchronization processing) is performed on each node in various information synchronization processing (S234), and the path information of the latest (after recovery) path is acquired. In the DB update and the previous path storage (S235), the information in the database 20 is updated to the latest path path information, and the path information before path switching is stored as a history.

  In the display process (S236), the latest path information and the path information before path switching are displayed together with the event information from the event process. Only the latest path route information may be displayed, but by displaying the route information before path switching, the management server 10 or the management client 30 can display not only the latest path route information but also before path switching. You can also check the route information on the map or list (log).

Although the multi-layer network operation management system has been described above, the present invention can also be realized as a computer program mounted on a management server that performs operation management of the MPLS / GMPLS network system. In this case, the following functions (1) to (9) may be executed by the computer in the management server.
(1) A function for detecting a node existing in the MPLS / GMPLS network 40.
(2) A function for obtaining node information including node attribute information by identifying whether the detected node is a GMPLS node, a WDM node, an MPLS / GMPLS node, or an MPLS node.
(3) A function of acquiring TE link information between nodes of the MPLS / GMPLS network 40 from the master MPLS / GMPLS node.
(4) A function for acquiring the path information of the MPLS path and the GMPLS path set in the MPLS / GMPLS network 40.
(5) A function for analyzing path information and obtaining inclusion relation information for associating hierarchical relations between MPLS paths and GMPLS path paths.
(6) A function of registering node information, TE link information, and path information / inclusion relation information in the database 20.
(7) A function of generating map display information by integrating node information, TE link information, and path information / inclusion relationship information registered in the database 20, and displaying objects on the MPLS / GMPLS network 40 as a map.

Furthermore, the following functions (10) to (12) can be added.
(10) A function for displaying detailed information of an object when an object is selected on the map display.
(11) Obtain an alarm sent from a node when a node, link or path failure occurs, analyze the node information, TE link information and path information / inclusion relationship information registered in the database 20 and the failure location. A function of identifying and generating fault information and reflecting the fault information on the map display. Furthermore, it is a function that identifies failure recovery and reflects it on the map display.
(12) A function of providing the management client 30 with the information of the network map and the database 20 in response to a request from the management client 30.

  Although the embodiment has been described above, the present invention is not limited to the above embodiment. For example, the management server 10 can have a GMPLS provisioning function. This function can be realized by installing interfaces such as CLI (Telnet) and XML (CORBA, Telnet).

It is a block diagram which shows embodiment of the multilayer network operation management system which concerns on this invention. It is a flowchart which shows the process in the multi-layer topology management function. It is a flowchart which shows the specific example of a node detection / information registration process. It is explanatory drawing of TE link when a WDM node exists. It is a flowchart which shows the specific example of a data link information registration process. It is a flowchart which shows the specific example of a TE link information registration process. It is a flowchart which shows the specific example of a GMPLS path information registration process. It is explanatory drawing of a GMPLS path information acquisition and identification processing procedure. It is a flowchart which shows the specific example of a MPLS path information registration process. It is explanatory drawing of a MPLS path information acquisition and inclusion relation analysis processing procedure. It is an ER diagram which shows the relationship between the managed objects. It is a figure which shows the display form of TE link and a path | pass. It is a figure which shows the list of the detailed information of TE link. It is a figure which shows the other display form of TE link and a path | pass. It is a figure which shows the list of GMPLS path detailed information. It is a figure which shows the other display form of TE link and a path | pass. It is a figure which shows the list | wrist of MPLS path detailed information. It is a conceptual diagram which shows the fault management by the present invention (according to the occurrence of a fault). It is a flowchart which shows the process in the fault management function (with fault occurrence) by this invention. It is explanatory drawing of the failure management at the time of failure occurrence. It is a conceptual diagram of an example of a failure analysis rule. It is a conceptual diagram which shows the failure management (according to failure recovery) by this invention. It is a flowchart which shows the process in the fault management function (according to fault recovery) by this invention. 1 is a configuration diagram showing a conventional management system of an MPLS / GMPLS network system.

Explanation of symbols

10 ... Management server, 20 ... Database, 30 ... Management client, 40,50 ... MPLS / GMPLS network, 100,110,120 ... Management plane (management network), 60,80 ... MPLS network 61-63, 81-83 ... MPLS node, 70 ... GMPLS network, 71-73 ... GMPLS node, 74,75 ... WDM node, 76,77 ... MPLS / GMPLS node, 130,160 ... Router monitoring device, 140 ... WDM monitoring device, 150 ... Transmission node monitoring device

Claims (10)

It has a management server and database,
The management server
Node detection means for detecting a node existing in an MPLS / GMPLS network in which an MPLS network and a GMPLS network are mixed ;
Node information identification registration means for identifying node attributes detected by the node detection means to obtain node attribute information, and registering node information including the node attribute information in the database;
TE link information acquisition means for acquiring TE link information between nodes of an MPLS / GMPLS network;
TE link information registration means for registering the TE link information acquired by the TE link information acquisition means in the database;
Path information acquisition means for acquiring path information of paths set in the MPLS / GMPLS network;
Analyzing the path information acquired by the path information acquisition means, and analyzing means for obtaining inclusion relation information that correlates the hierarchical relation between the MPLS path and the GMPLS path;
Path information / inclusion relation information registration means for registering path information acquired by the path information acquisition means and inclusion relation information obtained by the analysis means in the database;
Multi-layer network operation management comprising display control means for displaying a map of an MPLS / GMPLS network object based on node information, TE link information , path information and inclusion relation information registered in the database system.   The multi-layer network according to claim 1, wherein the node detection unit, the TE link information acquisition unit, and the path information acquisition unit respectively perform node detection, TE link information acquisition, and path information acquisition through a management network. Operation management system.   The multilayer network operation management system according to claim 1, wherein the map display is performed by at least one of the management server and an external server.   The multi-layer network operation management system according to claim 1, wherein the display control means displays detailed information of an object when an object is selected on the map display.   The management server further comprises failure management means for identifying a failure location by linking failure information sent from a node when a failure of a node, link or path occurs and information registered in the database, and the display control 2. The multi-layer network operation management system according to claim 1, wherein the means displays the failure location specified by the failure management means on a map display or as a list. 3.   The management server includes failure recovery management means for identifying failure recovery by linking failure recovery information sent from a node with failure recovery by path switching and information registered in the database, and paths before and after path switching. A recovery path information acquisition unit that acquires at least path information after path switching in the information, and when the failure recovery management unit specifies failure recovery, the display control unit uses the recovery path information acquisition unit 6. The multilayer network operation management system according to claim 5, wherein the acquired route information is displayed on a map display or as a list. A computer program installed in a management server for managing an operation of an MPLS / GMPLS network system in which an MPLS network and a GMPLS network are mixed ,
The ability to detect nodes present in an MPLS / GMPLS network;
A function of identifying whether a detected node is a GMPLS node, a WDM node, an MPLS / GMPLS node, or an MPLS node and obtaining node information including node attribute information;
The ability to obtain TE link information between nodes in an MPLS / GMPLS network;
A function to obtain the path information of the MPLS path and GMPLS path set in the MPLS / GMPLS network,
It analyzes the path information, and a function of obtaining the inclusion relation information associating a hierarchical relationship between MPLS paths and GMPLS path,
A function for registering node information, TE link information , path information and inclusion relation information in a database;
A computer program that realizes a function of generating map display information by integrating node information, TE link information , path information, and inclusion relation information registered in a database, and displaying an MPLS / GMPLS network object on a map.   The computer program according to claim 7, further realizing a function of displaying detailed information of an object when a certain object is selected on the map display. Further, failure information transmitted from the node when a node, link or path failure occurs is obtained, and the failure information is analyzed by analyzing the failure information and node information, TE link information, path information and inclusion relation information registered in the database. The computer program according to claim 7, wherein a function for generating event information and reflecting a failure occurrence on a map display is realized by the event information.   Furthermore, the failure recovery information sent from the node along with the failure recovery by the path switching is acquired, and the failure recovery is specified by linking the failure recovery information and the information registered in the database, and the route before and after the path switching. The computer program according to claim 9, wherein the computer program realizes a function of acquiring at least route information after path switching out of at least path information after path switching, and reflecting failure recovery and path switching on a map display.

Images