JP5075856B2 - User specific device and program - Google Patents

Description

  The present invention relates to a user specifying device and a program.

  A technique for simultaneously monitoring an IP-VPN user and an MPLS path has been proposed (see, for example, Patent Document 1). In recent years, multicast VPN (see Patent Document 2) has attracted attention and is applied to IP-TV and video conferencing.

K. Kumaki, I. Nakagawa, K. Nagami, T. Ogishi and S. Ano, “A Hierarchical Management System for MPLS Network Services”, IEICE, Vol. E90-B, No. 10, October 2007. E. Rosen and R. Aggarwal, “Multicast in MPLS / BGP IP VPNs”, IETF Internet-Drafts, draft-ietf-l3vpn-2547bis-mcast, July 2008. D. Awduche, L. Berger, D. Gan, T. Li, V. Srinivasan and G. Swallow, “RSVP-TE: Extensions to RSVP for LSP Tunnels”, IETF RFC3209, December 2001. R. Aggarwal, D. Papadimitriou and S. Yasukawa, “Extensions to Resource Reservation Protocol-Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)”, IETF RFC4875, May 2007.

  However, since the technique disclosed in Non-Patent Document 1 is based on a network composed of P2P (Point-to-Point) IP-VPN and P2P MPLS path (see Patent Document 3), P2MP (Point -to-Multipoint) cannot be applied to simultaneous monitoring of a multicast VPN user and a P2MP MPLS path in a network composed of a multicast IP-VPN and a P2MP MPLS path (see Patent Document 4). Therefore, when a failure occurs in the P2MP MPLS path, the affected multicast VPN user cannot be instantly specified.

  The present invention has been made in view of the above-described problems, and it is an object of the present invention to provide a technique for instantaneously identifying an affected multicast VPN user when a failure occurs in a P2MP MPLS path. To do.

  In order to solve the above problem, a user identification device according to one aspect of the present invention identifies a failure-affected user who is affected by a failure when a failure occurs in a network to which P2MP MPLS configured by a plurality of paths is applied. A path management information storage unit that stores path information indicating each device in the path as path management information in association with path identification information for identifying each path of the P2MP MPLS, and a path identification information Correspondingly, a route table management information storage unit for storing information indicating a combination of route tables held by devices at both ends of the path as route table management information, and a failure notification for notifying a link related to the occurrence of a failure are acquired from the outside. Path management information and route table management information when a fault notification is acquired by the fault notification acquisition unit Each of the routes constituting the combination of the route tables indicated by the information indicating the combination of the route tables, by extracting information indicating the combination of the route tables held by the devices at both ends of the path including the link relating to the failure And a user identification unit that identifies the user to which the table is assigned as the failure-affected user.

  The user identification device includes a device management information storage unit that stores information indicating a combination of devices at both ends as device management information in association with information indicating a combination of route tables held by devices at both ends of the path, and a path A route table management information generation unit that generates the route table management information with reference to the management information and the device management information may be further provided.

  In order to solve the above problem, a user identification device according to another aspect of the present invention identifies a failure-affected user affected by a failure when a failure occurs in a network to which P2MP MPLS configured by a plurality of paths is applied. A combination of a path management information storage unit that stores path information indicating each device in each path of the P2MP MPLS, and a path table held by devices at both ends of the path. A device management information storage unit that stores information indicating a combination of the devices at both ends in association with the information as device management information, a failure notification acquisition unit that acquires a failure notification that notifies a link related to the occurrence of a failure, and a failure notification When a failure notification is acquired by the acquisition unit, the path management information and device management information are referred to and both paths including the link related to the failure occurrence are referred to. The information indicating the combination of the route tables held by the device is extracted, and the user who assigns the route tables constituting the combination of the route tables indicated by the information indicating the combination of the route tables is specified as the failure-affected user. And a user identification unit.

  In order to solve the above problem, a program according to another aspect of the present invention is a user specifying a failure-affected user who is affected by a failure when a failure occurs in a network to which P2MP MPLS configured by a plurality of paths is applied. When a failure notification is acquired by a failure notification acquisition step for acquiring a failure notification for notifying a link related to the occurrence of a failure from the outside, and the failure notification acquisition step, each path of the MPLS of P2MP is identified. A path table in which path identification information is associated with path information indicating each device in the path, and path identification information is associated with information indicating a combination of path tables held by devices at both ends of the path. Refer to the management information, and combine the route tables held by the devices at both ends of the path including the link related to the failure occurrence. And a user specifying step for specifying a user who is assigned to each of the route tables constituting the combination of the route tables indicated by the information indicating the combination of the route tables as the failure-affected user. And

  According to the present invention, when a failure occurs in the MPLS path of P2MP, an affected multicast VPN user can be identified instantaneously.

It is a block diagram of user specific device 10 of a 1st embodiment. 1 is a schematic diagram of a network 1. FIG. It is an example of various information. It is a block diagram of the user specific device 20 of 2nd Embodiment. It is an example of various information. 4 is a flowchart showing the operation of the user specifying device 20. It is a block diagram of the user specific device 30 of 3rd Embodiment. This is an architecture of a monitoring device 90 which is an application example of the user specifying device 20.

(First embodiment)
Hereinafter, a user specifying device 10 according to a first embodiment of the present invention will be described in detail with reference to the drawings. The user specifying device 10 specifies a user affected by a failure (hereinafter referred to as “failure affected user”) when a failure occurs in the network 1 to which P2MP MPLS configured by a plurality of paths is applied. As shown in FIG. 1, the user specifying device 10 includes a path management information storage unit 100, a route table management information storage unit 110, a failure notification acquisition unit 120, and a user specification unit 130.

  The path management information storage unit 100 stores path information indicating each device in each path as path management information in association with path identification information for identifying each path of P2MP MPLS. Specifically, when the network 1 has the configuration shown in FIG. 2, the path management information storage unit 100 stores, for example, the path management information shown in FIG. In FIG. 3A, the item “Sub_LSP_ID” corresponds to path identification information, and the item “Path” corresponds to path information. Also, the item “Sub_LSP original_ID” in FIG. 3A is device identification information for identifying the device at the start point (transmission source) of each path, and the item “Sub_LSP Destination_ID” is the device for identifying the device at the end point (destination) of each path. The identification information item “P2MP_ID / tunnel_ID” is information for identifying the MPLS of each P2MP. The item “Sub_LSP original_ID” and the item “Sub_LSP Destination_ID” are extracted from the item “Path” (path information).

  In FIG. 2A, RE (ID: A) to RE (ID: I) are devices (for example, routers) in the network 1, and symbols in parentheses are device identification information. A straight line is a link between devices. FIG. 2B is a detailed view of FIG. In FIG. 2B, vrf is a route table held by each device, and User is a user who assigns the route table (a user who uses the route table). When the configuration of the network 1 is updated, a path management information generation unit (not shown in FIG. 1) updates the path management information stored in the path management information storage unit 100 to reflect the updated contents. The same applies to the second and third embodiments.

  The route table management information storage unit 110 stores information indicating a combination of route tables held by devices at both ends of the path as route table management information in association with the path identification information. Specifically, the route table management information storage unit 110 stores, for example, the route table management information shown in FIG. 3B when the network 1 has the configuration shown in FIG. In FIG. 3B, the item “Sub_LSP_ID” corresponds to path identification information, and the item “VRF (root)” and the item “VRF (leaf)” correspond to information indicating a combination of route tables.

  The failure notification acquisition unit 120 acquires a failure notification for notifying a link related to the occurrence of a failure from the outside (each device). For example, the failure notification acquisition unit 120 acquires a failure notification from the outside as a trap by SNTP (Simple Network Management Protocol). The failure notification acquisition unit 120 supplies a failure notification acquired from the outside to the user identification unit 130.

  The user identification unit 130 acquires a failure notification from the failure notification acquisition unit 120. When acquiring the failure notification, the user specifying unit 130 refers to the path management information stored in the path management information storage unit 100 and the route table management information stored in the route table management information storage unit 110, and a failure has occurred. Information indicating a combination of route tables held by devices at both ends of the path including the link is extracted. For example, when the network 1 has the configuration shown in FIG. 2, when the user identifying unit 130 obtains a failure notification for notifying a link failure between RE (ID: F) and RE (ID: I), Then, from the path management information stored in the path management information storage unit 100, the Sub_LSP_ID (path identification information) “30004” of the path including the link “FI” related to the failure occurrence is specified. Next, the user specifying unit 130 determines, based on the route table management information stored in the route table management information storage unit 110, the VRF (root) / VRF (leaf) (route) corresponding to Sub_LSP_ID (path identification information) “30004”. Information indicating a combination of tables) “vrf2 / vrf7” is extracted.

  The user specifying unit 130 that has extracted the information indicating the combination of the route tables specifies, as the failure-affected user, the user to whom each of the route tables constituting the combination of the route tables indicated by the information indicating the combination of the route tables is assigned. For example, when the user specifying unit 130 extracts VRF (root) / VRF (leaf) (information indicating a combination of route tables) “vrf2 / vrf7”, it is stored in a user information storage unit (not shown in FIG. 1). Referring to the user management information shown in FIG. 3C, a route table “vrf2” constituting Vvr (root) / VRF (leaf) (information indicating a combination of route tables) “vrf2 / vrf7” is assigned. The user “C (branch 1)” is identified as the failure-affected user, and the user “C (branch 4)” to which the route table “vrf7” is assigned is identified as the failure-affected user (that is, the user “C” is identified). . In the user management information shown in FIG. 3C, the item “VRF” is device identification information, and the item “User (branch1)” is user identification information (user name, base).

(Second Embodiment)
Hereinafter, a user identification device 20 according to a second embodiment of the present invention will be described with reference to the drawings. The user identification device 20 identifies a failure-affected user when a failure occurs in the network 1 to which P2MP MPLS configured by a plurality of paths is applied. As shown in FIG. 4, the user specifying device 20 includes a path management information storage unit 200, a route table management information storage unit 210, a failure notification acquisition unit 220, a user specification unit 230, a device management information storage unit 240, and a route table management information. A generation unit 250 is provided. The path management information storage unit 200, the route table management information storage unit 210, the failure notification acquisition unit 220, and the user identification unit 230 are the path management information storage unit 100, the path table management of the user identification device 10 according to the first embodiment. Since it is the same as the information storage unit 110, the failure notification acquisition unit 120, and the user identification unit 130, description thereof is omitted.

  The device management information storage unit 240 stores information indicating a combination of devices at both ends as device management information in association with information indicating a combination of route tables held by devices at both ends of the P2MP MPLS path. Specifically, when the network 1 has the configuration shown in FIG. 2, the device management information storage unit 240 stores, for example, the device management information shown in FIG. In FIG. 5, item “VRF (root)” and item “VRF (leaf)” correspond to information indicating a combination of route tables, and item “RE (root)” and item “RE (leaf)” are the devices of both ends. This corresponds to information indicating a combination. When the configuration of the network 1 is updated, a device management information generation unit (not shown in FIG. 4) updates the device management information stored in the device management information storage unit 240 to reflect the updated contents. The same applies to the third embodiment.

  The route table management information generation unit 250 refers to the path management information stored in the path management information storage unit 100 and the device management information stored in the device management information storage unit 240, and generates the route table management information. For example, the path table management information generation unit 250 stores the path management information shown in FIG. 3A in the path management information storage unit 100 and the device management information shown in FIG. 4 in the device management information storage unit 240. First, the route table management information generating unit 250 first obtains VRF (root) / VRF (leaf) (information indicating a combination of route tables) “vrf1 /” from the device management information stored in the device management information storage unit 240. vrf3 ”and RE (root) / RE (leaf) (information indicating a combination of devices at both ends)“ A / G ”are extracted, and the extracted value“ A ”is extracted from the path management information stored in the path management information storage unit 100. Sub_LSP_ID (path identification information) “30000” corresponding to “/ G” is specified. Then, the route table management information generation unit 250 generates the route table management information (first line) shown in FIG. 3B from the specific value “30000” and the extracted value “vrf1 / vrf3”. Next, the routing table management information generation unit 250 similarly extracts VRF (root) / VRF (leaf) “vrf1 / vrf5” and RE (root) / RE (leaf) “A / H” from the device management information. Then, the Sub_LSP_ID (path identification information) “30001” corresponding to the extracted value “A / H” is specified from the path management information. Then, the route table management information generation unit 250 generates the route table management information (third line) shown in FIG. 3B from the specific value “30001” and the extracted value “vrf1 / vrf5”. The route table management information generation unit 250 repeats the same operation and generates the route table management information shown in FIG. The route table management information generation unit 250 reflects the updated contents when the path management information stored in the path management information storage unit 200 or the device management information stored in the device management information storage unit 240 is updated. Therefore, the routing table management information stored in the routing table management information storage unit 210 is updated.

  Next, the operation of the user identification device 20 will be described with reference to FIG. FIG. 6A is a flowchart showing the operation when generating the routing table management information, and FIG. 6B is a flowchart showing the operation when specifying the user. The flowchart illustrated in FIG. 6A starts when the path management information stored in the path management information storage unit 200 or the device management information stored in the device management information storage unit 240 is updated. Also, the flowchart illustrated in FIG. 6B starts when the user identification unit 230 acquires a failure notification from the failure notification acquisition unit 220.

  In FIG. 6A, the route table management information generation unit 250 displays one line of device management information stored in the device management information storage unit 240 (information indicating a combination of route tables and information indicating a combination of devices at both ends). Is extracted (read out) (step S100).

  The route table management information generation unit 250 identifies path identification information corresponding to information indicating the combination of the devices at both ends extracted in step S100 from the path management information stored in the path management information storage unit 100 (step S110). ).

  The route table management information generation unit 250 generates a line of route table management information from the path identification information identified in step S110 and the information indicating the combination of route tables extracted in step S100 (step S120).

  The route table management information generation unit 250 determines whether all device management information stored in the device management information storage unit 240 has been extracted (step S130).

  When the route table management information generation unit 250 determines that all the device management information stored in the device management information storage unit 240 has been extracted (step S130: Yes), this flowchart ends. On the other hand, when the route table management information generation unit 250 determines that all the device management information stored in the device management information storage unit 240 has not been extracted (step S130: No), the process returns to step S100.

  In FIG. 6B, the user specifying unit 230 that has acquired the failure notification from the failure notification acquisition unit 220 uses the path management information stored in the path management information storage unit 100 to determine the path of the path including the link relating to the failure occurrence. Identification information is specified (step S200).

  The user specifying unit 130 extracts information indicating a combination of route tables corresponding to the path identification information specified in step S200 from the route table management information stored in the route table management information storage unit 110 (step S210).

  The user identifying unit 230 that has extracted the information indicating the combination of the route tables identifies the user who has assigned each of the route tables constituting the combination of the route tables indicated by the information indicating the combination of the route tables extracted in step S210 as the failure-affected user. (Step S220). And this flowchart is complete | finished.

(Third embodiment)
Hereinafter, a user identification device 30 according to a third embodiment of the present invention will be described with reference to the drawings. The user specifying device 30 specifies a failure-affected user when a failure occurs in the network 1 to which P2MP MPLS configured by a plurality of paths is applied. As shown in FIG. 7, the user specifying device 30 includes a path management information storage unit 300, a failure notification acquisition unit 320, a user specification unit 330, and a device management information storage unit 340. Note that the path management information storage unit 300 and the failure notification acquisition unit 320 are the same as the path management information storage unit 100 and the failure notification acquisition unit 120 of the user identification device 10 of the first embodiment, and thus description thereof is omitted. The device management information storage unit 340 is the same as the device management information storage unit 240 of the user identification device 20 according to the second embodiment, and thus the description thereof is omitted.

  The user identification unit 330 acquires a failure notification from the failure notification acquisition unit 320. When acquiring the failure notification, the user specifying unit 330 refers to the path management information stored in the path management information storage unit 300 and the device management information stored in the device management information storage unit 340 and relates to the occurrence of the failure. Information indicating a combination of route tables held by devices at both ends of the path including the link is extracted. For example, when the network 1 has the configuration shown in FIG. 2, the user identification unit 330 first obtains a failure notification that notifies a link failure between RE (ID: F) and RE (ID: I). From the path management information stored in the path management information storage unit 300, the Sub_LSP original_ID (device identification information for identifying the starting device) “B” and the Sub_LSP Destination_ID of the path including the link “FI” related to the failure occurrence (Device identification information for identifying the terminal device) “I” is specified. Next, the user identification unit 330 changes the device management information stored in the device management information storage unit 340 to RE (root) / RE (leaf) (information indicating a combination of devices at both ends) “B / I”. Corresponding VRF (root) / VRF (leaf) (information indicating a combination of route tables) “vrf2 / vrf7” is extracted.

  The user specifying unit 330 that has extracted the information indicating the combination of the route tables uses, for example, the same method as the user specifying device 10 of the first embodiment to combine the combination of the route tables indicated by the information indicating the combination of the route tables. A user who assigns each route table to be configured is specified as a failure-affected user.

  Note that the path management information stored in the path management information storage unit 100 (200) of the user specifying device 10 (20) of the first (2) embodiment has the item “Sub_LSP_ID” (path identification information). The path management information stored in the path management information storage unit 300 may not include the item “Sub_LSP_ID” (path identification information).

  In the following, supplementary explanation will be given using specific examples. As shown in FIG. 8, the monitoring device 90, which is an application example of the user specifying device 20, includes service management including multicast VPN (Service management) and path management including P2MP / MPLS path (Path management in the diagram). Element management including router devices and interfaces (Element management in the figure), and correlation management including coordination between multicast VPN and P2MP / MPLS path (Correlation in the figure).

  As shown in FIG. 8, the service management holds information corresponding to the user management information shown in FIG. 3C and the device management information shown in FIG. The path management holds information corresponding to the path management information shown in FIG. Correlation management holds information corresponding to the routing table management information shown in FIG. The element management realizes a function for acquiring a fault notification (a function of the fault notification acquiring unit 220). Further, other functions (functions of the user specifying unit 230 and the route table management information generating unit 250) are realized by any one management unit or a plurality of management units. For example, the correlation management may independently realize the function of the route table management information generation unit 250, and the path management, the correlation management, and the service management may cooperate to realize the function of the user specifying unit 230.

  An operation in which the monitoring device 90 identifies a user who has an influence on a failure will be briefly described. When the network 1 has the configuration shown in FIG. 2 and the link between the router F and the router I has a failure, the monitoring device 90 receives a trap (S2L sub-LSP originator ID, S2L sub-LSP) from the router B. Destination ID, P2MP ID or Tunnel ID) = (B, I, P2MP LSP2) is received (element management). The monitoring device 90 identifies S2L_Sub_LSP_ID = 30004 from the value included in the trap (path management). The monitoring device 90 identifies root vrf = vrf2 and leaf vrf = vrf7 using S2L_Sub_LSP_ID = 5 (correlation management), and finally identifies the failure-affected user (service management).

  As described above, according to the user specifying devices 10, 20, and 30, when a failure occurs in the P2MP MPLS path, an affected multicast VPN user can be specified instantaneously.

  Note that a program for executing each process of the user specifying devices 10, 20, and 30 according to each embodiment of the present invention is recorded on a computer-readable recording medium, and the program recorded on the recording medium is stored in a computer system. By reading and executing, the above-described various processes related to the user specifying devices 10, 20, and 30 according to an embodiment of the present invention may be performed. Here, the “computer system” may include an OS and hardware such as peripheral devices. Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used. The “computer-readable recording medium” means a flexible disk, a magneto-optical disk, a ROM, a writable nonvolatile memory such as a flash memory, a portable medium such as a CD-ROM, a hard disk built in a computer system, etc. This is a storage device.

  Further, the “computer-readable recording medium” means a volatile memory (for example, DRAM (Dynamic DRAM) in a computer system that becomes a server or a client when a program is transmitted through a network such as the Internet or a communication line such as a telephone line. Random Access Memory)), etc., which hold programs for a certain period of time. The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes designs and the like that do not depart from the gist of the present invention.

  DESCRIPTION OF SYMBOLS 1 Network 10, 20, 30 User specific apparatus 90 Monitoring apparatus 100 Path management information storage part 110 Path table management information storage part 120 Failure notification acquisition part 130 User specification part 200 Path management information storage part 210 Path table management information storage part 220 Fault Notification acquisition unit 230 User identification unit 240 Device management information storage unit 250 Route table management information generation unit 300 Path management information storage unit 320 Fault notification acquisition unit 330 User identification unit 340 Device management information storage unit

Claims (4)

A user identification device that identifies a failure-affected user affected by a failure when a failure occurs in a network to which a P2MP MPLS configured by a plurality of paths is applied,
A path management information storage unit that stores path information indicating each device in the path as path management information in association with path identification information that identifies each path of the MPLS of the P2MP;
A path table management information storage unit that stores information indicating a combination of path tables held by devices at both ends of the path as path table management information in association with the path identification information;
A failure notification acquisition unit for acquiring a failure notification for notifying a link relating to a failure occurrence from the outside;
When the failure notification is acquired by the failure notification acquisition unit, the path management information and the route table management information are referred to, and the path table held by the devices at both ends of the path including the link related to the failure occurrence A user specifying unit that extracts information indicating a combination and specifies a user who is assigned to each of the route tables constituting the combination of the route tables indicated by the information indicating the combination of the route tables as the failure-affected user. Feature user-specific device. A device management information storage unit that stores information indicating a combination of devices at both ends as device management information in association with information indicating a combination of route tables held by devices at both ends of the path;
A path table management information generating unit that generates the path table management information with reference to the path management information and the device management information;
The user specifying device according to claim 1, further comprising: A user identification device that identifies a failure-affected user affected by a failure when a failure occurs in a network to which a P2MP MPLS configured by a plurality of paths is applied,
A path management information storage unit for storing path information indicating each device in each path of the P2MP MPLS as path management information;
A device management information storage unit that stores information indicating a combination of devices at both ends as device management information in association with information indicating a combination of route tables held by devices at both ends of the path;
A failure notification acquisition unit for acquiring a failure notification for notifying a link relating to a failure occurrence;
When the failure notification is acquired by the failure notification acquisition unit, the path management information and the device management information are referred to, and a combination of route tables held by the devices at both ends of the path including the link related to the failure occurrence And a user specifying unit that specifies a user who is assigned to each of the route tables constituting the combination of route tables indicated by the information indicating the combination of the route tables as the failure-affected user. User specific device. When a failure occurs in a network to which a P2MP MPLS configured by a plurality of paths is applied, a failure is affected by the failure.
A failure notification acquisition step for acquiring a failure notification for notifying a link related to a failure occurrence from the outside,
Path management information in which path identification information for identifying each path of the P2MP MPLS is associated with path information indicating each device in the path when the fault notification is acquired by the fault notification acquisition step; and , Referring to route table management information in which the path identification information is associated with information indicating a combination of route tables held by devices at both ends of the path, and devices at both ends of the path including the link relating to the occurrence of the failure User specifying step of extracting information indicating a combination of route tables to be held and specifying a user who has assigned each route table constituting a combination of route tables indicated by the information indicating the combination of the route tables as the failure-affected user A program characterized by causing

Images