WO2006025296A1 - 障害回復方法およびネットワーク装置ならびにプログラム - Google Patents
障害回復方法およびネットワーク装置ならびにプログラム Download PDFInfo
- Publication number
- WO2006025296A1 WO2006025296A1 PCT/JP2005/015620 JP2005015620W WO2006025296A1 WO 2006025296 A1 WO2006025296 A1 WO 2006025296A1 JP 2005015620 W JP2005015620 W JP 2005015620W WO 2006025296 A1 WO2006025296 A1 WO 2006025296A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- path
- unit
- failure
- packet
- routing
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/26—Route discovery packet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
- H04L45/03—Topology update or discovery by updating link state protocols
Definitions
- the present invention relates to a failure recovery method and a network device, and more particularly, to a failure recovery method in a network configured by a network device having a control module group including a routing protocol for exchanging route information and a signaling protocol for route setting. Regarding the law.
- failure recovery in mesh topology can be realized. Failure recovery in the mesh topology is divided into a pre-brand method in which a spare route is calculated in advance for the current route and a dynamic method in which a spare route is calculated after a failure is detected. Each can be divided into link failure recovery, which switches to the backup path at both ends of the link where a failure has occurred on a link basis, and path failure recovery, which switches the entire node from the source node to the destination node on a path basis. Furthermore, there are three types of pre-planned path failure recovery: 1 + 1, 1: 1, and Shared. The three types of pre-planned path failure recovery are as follows.
- both the working path and the protection path are set in advance and a failure occurs in the working path, the path is switched to the protection path only at the end node of the path.
- Preliminary path calculation and bandwidth reservation are performed in advance, but the switch is not set. If a failure occurs in the working path, signaling is performed to set the backup node.
- the LS control unit receives the failure notification, the failure recovery operation using the routing protocol and signaling protocol is started simultaneously.
- the routing protocol transmits a packet to notify other nodes of the status change of the failed link, and the signaling protocol transmits a packet for switching the failed node to the protection path.
- These packets are simultaneously sent to the control plane control channel.
- the routing protocol since the routing protocol sends a large number of packets at once, it does not compete with the signaling protocol packets, resulting in congestion. For this reason, it takes time to process the packet by the signaling protocol, and it takes time to recover from the failure.
- Non-Patent Document 2 describes one solution to such a problem.
- Non-Patent Document 2 mentions that control message storms occur due to failure recovery signaling executed for each path at the time of failure and advertisement by routing of the failure link, resulting in congestion.
- the results of an experimental evaluation of the impact of the amount of signaling and routing information on the routing information) and the control channel bandwidth on the scalability of the GMPLS control plane are shown, which are large enough to reduce failure recovery time. We conclude that a bandwidth control channel is needed.
- Patent Document 1 On the receiving side, packet processing priority is determined according to information such as a source IP address, a destination IP address, a source port number, a destination port number, and a protocol, and scheduling is performed. To avoid congestion. Also, discard processing is performed for low priority packets. Queue packet processing is determined by the scheduling rate.
- packet transmission processing is congested. The data flow to which the transmitted packet belongs is identified in the congested period and the packet is preferentially transmitted according to the data flow communication quality. In the non-congested period, the data is transmitted. Packets are transmitted in the order requested without identifying the packet data flow. During the congested period, the number of transmission waiting packets in the transmission waiting state is large, and it is determined by whether or not the power exceeds the value.
- Patent Document 1 Japanese Patent Laid-Open No. 2001-332440 (Page 3-4)
- Patent Document 2 JP-A-9 126701 (page 3)
- Non-Patent Document 1 G. P. Lang), 2 others, “Earl” S “Bui” P. 'End Ji'em
- Non-Patent Document 2 Toru Nishioka and 2 others, “Scalability Evaluation of GMPLS Control Plane”, 20 2003 IEICE Communication Society Conference, B-7-66, p. 247
- the present invention has been proposed in view of such circumstances, and an object thereof is to provide a novel failure recovery method and network device that can shorten the failure recovery time.
- Another object of the present invention is to provide a failure recovery method and network device that can perform pre-brand failure recovery reliably and at high speed.
- the failure recovery method according to claim 1 is used in a network including a plurality of network devices including a control protocol group including a routing protocol unit for exchanging route information and a signaling protocol unit for setting a route.
- a failure occurs in a link that constitutes a path
- the first network device that performs processing to switch the one or more working paths that have failed to a spare path that has been calculated in advance. Routing that is effective in advertising the failed link by the routing protocol after the signaling message for switching to the protection path by the signaling protocol for all or some of the working paths is completed. It is characterized by starting packet transmission.
- a failure recovery method is the same as the failure recovery method according to claim 1,
- the first network device is characterized in that when the switching to the protection path by the signaling protocol unit is completed, the advertisement of the failed link by the routing protocol unit is started. Switching to the protection path after the signaling message transmission for switching to the protection path by the signaling protocol unit for all or some of the one or more working paths that have failed is completed. If advertisement of the failed link by the routing protocol part is started at the time of completion, packet contention and congestion can be prevented more reliably, and the advertisement of the failed link is not delayed so much.
- the failure recovery method according to claim 3 is the failure recovery method according to claim 2, wherein the first network device performs signaling by the signaling protocol unit that switches the failed working path. When it is confirmed that the message has made one round trip along the failure recovery path, it is judged that the switch to the spare node has been completed.
- a failure recovery method is the failure recovery method according to claim 2 or 3, wherein a network device that detects a failure that has occurred in a link that constitutes a working path includes: The second network device other than the first network device described above performs the process of switching the used working path to the preliminarily calculated spare path. The second network device other than the first network device may include all or a part of the one or more working paths that have failed. In response to the end of switching of the path to the backup path, transmission of a routing packet that is effective for advertisement of a faulty link by the routing protocol unit is started.
- the second network device other than the first network device that switches the working path to the protection path also delays the advertisement of the failure link by the routing protocol unit, thereby transmitting the first network device. It is possible to more reliably avoid the occurrence of congestion due to conflicting signaling messages with routing packets.
- the failure recovery method according to claim 5 is the failure recovery method according to claim 4, wherein the second network device is a routing packet that applies an advertisement of a failure link from the first network device. It is characterized in that it is determined that the switching of all or one of the failed working paths or a part of the failed paths to the backup path has been completed.
- a failure recovery method according to claim 6 is provided in a network composed of a plurality of network devices each including a control protocol group including a routing protocol unit for exchanging route information and a signaling protocol unit for performing route setting. In addition to the first control channel on the communication path that is implemented by Out-of-Band between the network devices to be installed, a second control channel on the communication path that is implemented by In-Band is provided.
- the packet When a failure occurs in the link that constitutes the working path set by the signaling protocol, the packet by the signaling protocol unit and the routing protocol unit for switching one or more of the failed working paths to a backup path.
- the first and second control channels and routing packets that are used to And wherein the transmitted and received between the network device over different that control channel from each other of the panel.
- the packet by the signaling protocol unit for switching one or more working paths that have failed to the backup path, and the advertisement of the failed link by the routing protocol unit Since routing packets that are difficult to handle are transmitted and received between network devices through different control channels, the occurrence of contention between signaling message packets and routing packets is suppressed, and congestion is avoided. Thereby, pre-brand failure recovery is performed reliably and at high speed.
- a network device includes a monitor unit that detects a failure, a failure information notification unit that notifies a failure detected by the monitor unit, a scheduling control unit that controls scheduling such as changing a scheduling algorithm, A network device including a control module group to be scheduled is changed by changing a scheduling algorithm applied to the control module group in response to a failure.
- the network device is a network device including a control protocol group including a routing protocol unit for exchanging route information and a signaling protocol unit for setting a route, and a failure occurs in a link constituting the working path.
- a path setting management unit that detects that the switching to the protection path by the signaling protocol has been completed for all or some of the one or more working paths that have failed, and the node setting Until the detection is performed by the management unit, the routing protocol unit does not transmit a routing packet that is effective in advertising the failed link.
- a network device is a network device including a control protocol group including a routing protocol unit for exchanging route information and a signaling protocol unit for performing route setting.
- the failure information notification unit that simultaneously notifies the routing protocol unit, the first queue that stores the signaling packet of the signaling protocol unit and the Hello packet of the routing protocol unit when the working path fails, and the failure of the working path
- a second queue that stores packets other than Hello packets in the routing protocol section, and a path setting that monitors whether or not switching to all the failed paths has been completed when the working path fails
- the scheduling control unit performs transmission control of packets stored in the first queue until switching to the backup path of the network is completed, and then performs transmission control of packets stored in the second queue. It is characterized by having.
- the network device is a network device comprising a control protocol group including a routing protocol unit for exchanging route information and a signaling protocol unit for performing route setting, wherein the signaling protocol unit Failure information notifying unit to notify to, the queue for storing the signaling packet of the signaling protocol unit and the routing packet of the routing protocol unit, and switching of all failed paths to backup nodes when the working path fails A path that allows the failure of the working path notified to the signaling protocol part to be notified to the routing protocol part if the switching of all the failed paths to the protection path has been completed. Stored in the queue And a scheduling control unit that controls transmission of the transmitted packets.
- a network device provides a network device having a control module group including a routing protocol unit for exchanging route information and a signaling protocol unit for route setting, so that a failure of the working path can be prevented.
- a failure information notifying unit for notifying the signaling protocol unit and the routing protocol unit; a Hello packet by the routing protocol unit when the working path fails; and the signaling protocol unit Packets sent and received by other network devices via the first control channel implemented in IN—Band, and packets other than Hello packets by the routing protocol part are second control channels implemented in Out—of—Band.
- a transmission / reception unit that transmits / receives to / from another network device through the network, and transmits a packet passed from the transmission / reception unit to an adjacent network device using the first control channel, and the adjacent network device power
- a separation unit that sends a packet received through the channel to the transmission / reception unit.
- the dynamic method which is one of the failure recovery methods, calculates a backup route after detecting a failure, if a failure link advertisement by the routing protocol is delayed, the backup route using the failure link is calculated.
- the pre-brand method does not need to calculate the backup route after detecting the failure, so the advertisement of the failure link by the routing protocol may be delayed.
- the failure recovery method according to claim 1 has been made paying attention to this point. By first transmitting a signaling message and then starting to transmit a routing packet, a signaling message packet and a routing packet are transmitted. By preventing the occurrence of congestion and avoiding congestion, pre-brand failure recovery can be performed reliably and quickly!
- Pre-brand failure recovery can be performed reliably and at high speed.
- the reason for this is that in the failure recovery method according to claim 1, signaling messages are transmitted first, and then routing packet transmission is started. Therefore, contention between signaling message packets and routing packets occurs. This is because congestion is prevented and the occurrence of congestion is avoided. Further, in the failure recovery method according to claim 6, since the packet by the signaling protocol unit and the packet by the routing protocol unit are transmitted and received between the network devices through different control channels, both packets are transmitted. This is because the occurrence of contention is suppressed and the occurrence of congestion is avoided.
- the bandwidth of the control channel on the control plane can be designed to be small. The reason for this is that when a failure occurs, the signaling and routing packets are placed in the control channel of the control plane. This is because it is possible to suppress the competition of the network.
- FIG. 1 is an explanatory diagram of a failure recovery operation by a signaling protocol in the first failure recovery method of the present invention.
- FIG. 2 is an explanatory diagram of an operation by a routing protocol in the first failure recovery method of the present invention.
- FIG. 3 is a diagram showing a failure recovery operation by the first failure recovery method of the present invention.
- FIG. 4 is a block diagram of an embodiment of a network control device used in the first failure recovery method of the present invention.
- FIG. 5 is a flowchart showing the operation of the embodiment of the network control device used in the first failure recovery method of the present invention.
- FIG. 6 is a block diagram of another embodiment of a network control device used in the first failure recovery method of the present invention.
- FIG. 7 is a flowchart showing the operation of another embodiment of the network control device used in the first failure recovery method of the present invention.
- FIG. 8 is a diagram showing a failure recovery operation by the second failure recovery method of the present invention.
- FIG. 9 is a block diagram of an embodiment of a network control device used in the second failure recovery method of the present invention. Explanation of symbols
- FIG. 1 is an operation explanatory diagram of a signaling protocol in a GMPLS network that implements the first failure recovery method of the present invention
- FIG. 2 is also an operation explanatory diagram of a routing protocol.
- 1 and 2 ⁇ 1 to ⁇ 5 represent node devices constituting the GMPLS network
- 1 is a link connecting the respective node devices ⁇ 1 to ⁇ 5.
- Link 1 may be any line capable of communication, such as an optical fiber Ethernet (registered trademark) cable.
- N1-N4 as working path P1
- a path configured by N5 that is, a link between the node device Nl and the node device N4 and a link between the node device N4 and the node device N5 is set.
- a node is a virtual connection.
- an LSP Label
- the failure recovery type of this working path P1 is 1: 1 of the pre-planned path failure recovery method, and it is used as a backup path to be used instead of the working path P1 when a failure occurs in the working node P1.
- Nl—N3—N5 is set.
- it is the node device N1 that is the starting node of the path that stores the protection path P1 of the working path P1.
- two or more working paths may be set. In this case, use the shared type pre-planned path failure recovery method, and share the same protection path between two working paths.
- a signaling packet 2 shown in FIG. 1 is a packet for switching a path when a failure occurs, and is transferred from the source node device N1 to the destination node device N5 of the protection path P2.
- the routing packet 3 shown in FIG. 2 is a packet that is advertised to an adjacent node to update the link state because the link state changes due to the failure when a failure occurs.
- Type routing protocol OSPF or a packet based on a routing protocol that extends it to GMPLS.
- the data plane for transferring data packets and the control plane for transferring control packets such as signaling packet 2 and routing packet 3 are logically separated.
- the node device N1 that is the starting node of the working path PI can detect the failure of the link that configures the working path P1, and the working node P1 is detected by the link failure between the node device N4 and the node device N5.
- the node P1 becomes a failure, such a data plane failure is finally notified to the node device N1 that is the origin node of the working path P1.
- One method is a method of notifying by a signaling protocol on the control plane. Specifically, notification is made using the RSVP Notify message. This message includes information indicating which path has failed, and the originating node starts a path switching operation corresponding to this information.
- Another method is to notify on the data plane.
- SONETZSDH Depending on the type of data plane, taking SONETZSDH as an example, it is put into the overhead part of SONETZSDH, which is AIS (Alarm Indication Signal).
- AIS Alarm Indication Signal
- the monitor unit of the switch unit of the originating node Upon receiving this information, raises path failure information to the control plane and starts a corresponding path switching operation on the control plane.
- the node device N1 and the node device N4 that detect the failure each start failure recovery.
- the node device N1 is the starting node of the working path P1
- the node device N4 is not the starting node of the working path P1
- different operations are performed.
- the operations of the node device N1 and the node device N4 will be described.
- the failure recovery operation of the node device N1 that is the starting node of the working path P1 will be described.
- the node device N1 detects a failure in the link between the node devices N4, the node device N1 uses the signaling protocol of the node device N 1 to switch the working path P 1 using the link to the protection path P2.
- a signaling packet 2 called a Path message is transmitted to the node device N 5 which is an end node of the path P2.
- the node device N1 since a failure has occurred in the link with the node device N4, the node device N1 is required to send a routing packet for updating the link state change to other node devices. If it starts at the same time as packet transmission, the failure recovery time is affected by packet contention. In this embodiment, after the path switching by the signaling protocol is completed, routing by the routing protocol is performed. Start sending packets.
- the Path message by the signaling packet 2 requests the node on the failure recovery path of the protection path P2 to set a label given to each link.
- the Path message is transmitted to the node device N5 via the node device N3.
- the node device N3 that has received the Path message sets a switch to use the protection path P2.
- a Pat h message is sent to the node device N5.
- the node device N5 that has received the Path message determines that the packet is addressed to its own node, sets the switch, and then sends the signaling packet 2 called the Resv message to the node device N1 on the reverse path to the Path message. Send to.
- the node device N3 that has received the Resv message changes the label information in the Resv message, and then sends the Resv message to the node device N1.
- the node device N1, which has received the Resv message has completed the setting of the protection path P2, and thereafter transmits the packet transmitted to the working path P1 to the protection path P2. As a result, the failed working path P 1 is switched to the protection path P 2.
- node apparatus N1 since there is only one working path P1 that has a failure path starting from the node apparatus N1, the node apparatus N1 switches the failed working path P1 to the protection path P2. When the replacement is completed, transmission of the routing packet is started. If there are multiple failure nodes with node device N1 as the starting node, node device N1 uses the same method as when switching the failed working path P1 to backup path P2. Switch the failed path to the backup path. Then, the node device N1 confirms that all the failed paths have been switched by confirming the transmitted Path message and the received Resv message, and when all the failed paths are switched, advertisement of the failed link by the routing packet is performed. To start.
- the routing protocol in the node device N1 transmits the routing packet 3 to the node device N2, the node device N3, and the node device N4 in order to update the state change of the failed link.
- the node device N2 that has received the routing packet 3 transmits the routing packet 3 to the node device N3 and the node device N5. Thereafter, the routing packet 3 for updating the state change of the failed link is similarly propagated sequentially.
- Each node device that receives the routing packet 3 performs operations specified in the routing protocol, such as updating the topology database. Topology data for all node devices in the network When the database is updated, the failure recovery operation performed from the occurrence of the failure is terminated.
- the failure recovery operation of the node device N4 that is a relay node of the working path P1 will be described.
- the node device N4 determines that a failure has occurred in the working path P1 that uses the link 1.
- the origin node of the working path P1 is not the own node device N4 and there is no other fault path where the own node device N4 becomes the origin node, the node device N4 has the node device N1 described above.
- the fault recovery operation by the signaling protocol is not performed.
- node device N4 since node device N4 has detected that a failure has occurred in the link with node device N1, it transmits a routing packet for updating the link state change to the other node devices in accordance with the routing protocol. There is a need to. However, if transmission of the routing packet is unconditionally started, the node device N1 that is the starting node of the failure path competes with the signaling packet that is transmitted for switching the failure path, which affects the failure recovery time. Therefore, the node device N4 starts transmitting the routing packet by the routing protocol after the switching of the working node P1 that has failed is completed.
- the node device N1 transmits the routing packet by the advertisement of the fault link to the own node device N4. Whether or not switching of the working path P1 has been completed can be determined by whether or not a routing packet has been received.
- the node device N4 since there is only one working path P1 with the node device N4 as a relay node, the node device N4 switches the failed working path P1 to the protection path P2.
- the node device N4 has switched all the failure paths to backup paths.
- the packet is detected by receiving a routing packet from each origin node, transmission of the routing packet is started.
- the node device N1 that is the starting node of the working path P1 is triggered by the end of the switching of the working path P1 to the protection path P2.
- the signaling message for switching the fault node is the fault recovery path (Nl -N3 -N5)
- the link state announcement by the routing protocol is started, so it is possible to avoid the occurrence of congestion due to contention between the signaling packet and routing packet, Pre-brand failure recovery time can be shortened.
- congestion between routing packets and signaling packets is avoided, the probability of discarding signaling packets is reduced and the reliability of failure recovery can be improved.
- the node device N4 that is not the starting node of the working path P1 determines that the node device N1 that is the starting node of the working path P1 has finished switching the working path P1 to the protection path P2.
- a trigger that is, when a routing packet is received from the node equipment N1 by advertisement of the fault link, the notification of the fault link by the routing protocol is started. It is possible to further avoid the situation.
- the node device N1 finishes switching all the failure paths and notifies the failure link by the force routing protocol.
- the announcement of the fault link by the routing protocol may be started. Specifically, transmission of a routing packet is started when it is confirmed that a signaling message for switching part of the fault paths has made one round trip along the fault recovery path.
- the node device N4 when there are a plurality of failure paths for which the own node device N4 is a relay node, the node device N4 terminates the switching of all the failure paths and announces the failure link by the force routing protocol. When the switching of all of the failed paths is completed, the announcement of the failed link by the routing protocol may be started.
- the node device N1 has a failure due to the routing protocol after switching of all the failure nodes is completed when there is one or more failure paths starting from the node device N1. Force to initiate link announcements for all or some disabilities Then, transmission of the routing packet may be started when transmission of the signaling message for switching the faulty path of the signaling protocol is completed.
- network device 4 also includes GMPLS control unit 5 constituting the control network and switch unit 13 constituting the data plane network.
- the network device 4 shown in FIG. 4 is a node device (nodes shown in FIGS. 1 and 2) in the GMPLS network that implements the first failure recovery method of the present invention described with reference to FIGS. Used as devices N1-N5).
- the GMPLS control unit 5 includes a control module group 21 having a routing protocol unit 6 and a signaling protocol unit 7, a queue A14 and a queue B15, a scheduling control unit 8, a path setting management unit 11, and a failure information notification unit. 9, a switch control unit 12, and a communication path A 18 to the GMPLS control unit 5 of another network device 4.
- the switch unit 13 includes a switch 17 that transfers data packets, a motor unit 10 that detects a link failure and the like, and a communication path B19 to the switch unit 13 of another network device 4. .
- the switch 17 performs a process of transferring a data packet, which has also been transmitted by another network device, to another network device, that is, switching a route.
- the communication path B19 is a communication path for transferring the data packet subjected to the data transfer process in the switch 17 to the transmission destination.
- the monitor unit 10 includes a link on the communication path B19 and other network devices connected by the link.
- the switch control unit 12 controls the switch 17 in the switch unit 13.
- the fault information notification unit 9 receives the fault information notified from the monitor unit 10 in the switch unit 13 and sends the fault information to the routing protocol unit 6, the signaling protocol unit 7, and the scheduling control unit 8. Notice. [0062] When the network is operating normally, the routing protocol unit 6 does not use the queue B 15 but uses only the queue A 14 to exchange the topology with the adjacent node, and creates a routing table and TE Link (Traffic
- EngineeringLink advertisement
- exchange of Hello packets to maintain the relationship with neighboring nodes.
- the routing protocol unit 6 maintains the relationship with the adjacent nodes in the same way as when the link information is updated and the network is operating normally when a failure is notified of the failure information from the failure information notification unit 9.
- the routing protocol unit 6 uses the queue A14 for transmitting the Hello packet, and uses the queue B15 for routing packets for updating link state information other than the Hello packet.
- the signaling protocol unit 7 uses the queue A 14 to perform LSP setting, LSP deletion, LSP setting state management, and the like.
- the signaling protocol unit 7 uses the queue A14 to protect the failure path if it is a failure of the working path starting from its own network device. Switch to the path.
- the signaling device 7 sends the received Path message and the Resv message as a response to the received Path message to the next node on the failure recovery path.
- the power to send to the device Packets for such messages are also stored in queue A14.
- the signaling protocol part 7 does not use the queue B 15 at all in both the normal state and the failure state.
- the queue A14 is used to store a packet transmitted from the routing protocol unit 6 and a packet transmitted from the signaling protocol unit 7, and a failure occurs.
- Time is used to store packets sent from the signaling protocol part 7 and Hello packets sent from the routing protocol part 6.
- Queue B15 is not used when the network is operating normally, and is used to store packets other than Hello packets transmitted from the routing protocol unit 6 when a failure occurs.
- Scheduling control unit 8 determines the packet stored in queue A14 and queue B15. Perform transmission processing. When the network is operating normally, the scheduling control unit 8 performs transmission processing on the packets stored in the queue A14 in the stored order. In addition, when the failure information is notified from the failure information notification unit 9, the scheduling control unit 8 performs transmission processing from the packet in the queue A14, and when the transmission processing of the packet in the queue A14 ends, the path setting management unit 11 is notified that the transmission processing of the packet in queue A14 has been completed, and when it is notified from the path setting management unit 11 that switching of all failed paths has been completed, the transmission processing of the packet in queue B15 is performed. If such notification is not received, it concentrates on the packet transmission process in queue A14.
- the node setting management unit 11 monitors the switching status of the failed path to the protection path by the signaling protocol unit 7, and when detecting that the switching of all the failed paths to the protection path has been completed, Notify the scheduling control unit 8.
- the routing protocol unit 6 exchanges the topology with the adjacent node, and creates a routing table, advertises the TE link, and maintains the relationship with the adjacent node. Packets are sent and received for Hello packet exchange. Packets transmitted from the routing protocol unit 6 are stored in the queue A14.
- the signaling protocol unit 7 transmits and receives packets for LSP setting, LSP deletion, LSP setting state management, and the like. Similarly, packets transmitted from the signaling protocol unit 7 are also stored in the queue A14. In this case, queue B15 is not used.
- queue A14 and queue B15 are of variable length and the same memory area is used, memory is wasted even when the network is operating normally or when a failure occurs. Can be omitted.
- Packets stored in queue A14 are subjected to transmission processing by scheduling control unit 8. Packet transmission processing is performed in the order stored in queue A14. A packet for which transmission processing is completed in the queue A 14 is transferred to the transmission destination using the communication path A18. On the other hand, under the control of the switch control unit 12, the switch 17 of the switch unit 13 transfers the data bucket.
- the failure is detected by monitor unit 10 of network device 4 (step Al in FIG. 5). .
- the monitor unit 10 that has detected the failure notifies the failure information notification unit 9 of the failure information (step A2).
- the failure information notifying unit 9 that has received the failure information transmits the failure information simultaneously to the routing protocol unit 6, the signaling protocol unit 7, and the scheduling control unit 8 (step A3).
- the routing protocol unit 6 that has received the failure information from the failure information notification unit 9 transmits a packet that uses the link state information in order to update the link state (step A4). Packets that are useful for the link state information transmitted from the routing protocol unit 6 are stored in the queue B 15 (step A6). The routing protocol unit 6 periodically sends and receives Hello packets to maintain the relationship with the adjacent nodes. The Hello packet transmitted from the routing protocol unit 6 is stored in the queue A14 (step A9).
- the signaling protocol unit 7 that has received the failure information from the failure information notification unit 9 starts switching the failure path to the protection path (step A7), and transmits a packet for switching to the protection path. (Step A8).
- the packet for switching from the failed path to the protection path transmitted from the signaling protocol unit 7 is stored in the queue A14 (step A9).
- the scheduling control unit 8 Upon receiving the failure information, the scheduling control unit 8 starts monitoring the queue A14 and the queue B15, and when it detects that there is a packet in the queue A14, performs transmission processing of the packet (step A10). When the transmission process for one packet in queue A14 is completed, scheduling control unit 8 determines whether there is a packet in queue A14 (step All), and if it is determined that there is a packet in queue A14, The packet transmission process is performed again. Queue A14 If it is determined that there is no packet, the scheduling control unit 8 notifies the path setting management unit 11 that the processing of the packet in the queue A14 has been completed (step A12).
- the path setting management unit 11 determines whether or not the switching of all the failed paths to the protection path has been completed (step A13).
- the path setting management unit 11 sends a signaling packet related to the Resv message to the signaling packet that works on the Path message transmitted from the signaling protocol unit 7 for all the fault paths from which the network device is the origin node.
- the scheduling control section 8 is notified that the switching to the protection path has been completed (step A14).
- the scheduling control unit 8 confirms again the presence or absence of the packet in the queue A14, and if the existence of the packet is confirmed, performs the transmission process again.
- the path setting management unit 11 notifies the scheduling control unit 8 that the switching of all the paths has been completed (Step A15 ). Receiving the notification that the switching to the protection path has been completed, the scheduling control unit 8 performs transmission processing of the packet in the queue B15 (step A16). When the packet transmission process in the queue B15 is completed, the scheduling control unit 8 determines whether there is a packet in the queue B15 (step A17), and if it determines that there is a packet, performs the packet transmission process again. If it is determined that there is no packet, the failure recovery operation by the routing protocol unit 6 and the signaling protocol unit 7 ends.
- the working path backup is established in the network device (corresponding to node device N1 in the case of Fig. 3) in which the failure of the working path whose own network device is the origin node is detected.
- the network device corresponding to node device N1 in the case of Fig. 3
- public announcements by the routing protocol can be started, competition between signaling packets and routing packets and the occurrence of congestion can be avoided, and pre-brand failure recovery time can be shortened.
- congestion of routing packets and signaling packets is avoided, the probability of discarding signaling packets is reduced, and the reliability of failure recovery can be improved.
- the operation of the network device (corresponding to the node device N4 in the case of FIGS. 1 and 2) in which the own network device detects the failure of the active node serving as a relay node is shown in the block diagram of FIG. 4 and FIG. This will be described with reference to the flowchart of FIG.
- the failure is detected by monitor unit 10 of network device 4 (step Al in FIG. 5).
- the monitor unit 10 that has detected the failure notifies the failure information notification unit 9 of the failure information (step A2).
- the failure information notifying unit 9 that has received the failure information transmits the failure information simultaneously to the routing protocol unit 6, the signaling protocol unit 7, and the scheduling control unit 8 (step A3).
- the routing protocol unit 6 that has received the failure information from the failure information notification unit 9 transmits a packet that uses the link state information in order to update the link state (step A4). Packets that are useful for the link state information transmitted from the routing protocol unit 6 are stored in the queue B 15 (step A6). The routing protocol unit 6 periodically sends and receives Hello packets to maintain the relationship with the adjacent nodes. The Hello packet transmitted from the routing protocol unit 6 is stored in the queue A14 (step A9).
- the signaling protocol unit 7 that has received the failure information from the failure information notification unit 9 does not switch the failed path to the backup path because the own network device is not the origin node of the failed path. That is, steps A7 to A9 in FIG. 5 are skipped.
- the scheduling control unit 8 Upon receiving the failure information, the scheduling control unit 8 starts monitoring the queue A14 and the queue B15. When detecting that there is a packet in the queue A14, the scheduling control unit 8 performs transmission processing of the packet (step A10). When the transmission process for one packet in queue A14 is completed, scheduling control unit 8 determines whether there is a packet in queue A14 (step All), and if it is determined that there is a packet in queue A14, The packet transmission process is performed again. If it is determined that there is no packet in the queue A14, the scheduling control unit 8 notifies the path setting management unit 11 that the processing of the packet in the queue A14 has been completed (step A12).
- path setting management unit 11 determines whether or not the switching of all the failed paths to the backup path has been completed (step A13).
- the path setting management unit 11 uses all the fault paths for which the local network device is a relay node. Network device power as a source node
- the scheduling control unit 8 is notified that the switching to the backup node has not been completed (step A14).
- the scheduling control unit 8 confirms the presence / absence of a packet in the queue A14 again, and performs transmission processing again when the existence of the packet is confirmed.
- the path setting management unit 11 notifies the scheduling control unit 8 that the switching of all the paths has been completed (Step A15). ). Receiving the notification that the switching to the protection path has been completed, the scheduling control unit 8 performs transmission processing of the packet in the queue B15 (step A16). When the packet transmission process in the queue B15 is completed, the scheduling control unit 8 determines whether there is a packet in the queue B15 (step A17), and if it determines that there is a packet, performs the packet transmission process again. If it is determined that there is no packet, the failure recovery operation by the routing protocol unit 6 and the signaling protocol unit 7 ends.
- the network device (corresponding to the node device N4 in the case of FIG. 3) in which the own network device detects a failure of the working path serving as a relay node,
- public announcements by the routing protocol can be started, competition between signaling packets and routing packets and the occurrence of congestion can be avoided, and pre-brand failure recovery time can be shortened.
- congestion of routing packets and signaling packets is avoided, the probability of discarding signaling packets is reduced, and the reliability of failure recovery can be improved.
- the network device 4 that is effective in the present embodiment includes two queues A14 and B15.
- the packet transmitted by the signaling protocol unit 7 and the Hello packet transmitted by the routing protocol unit 6 Are stored in queue A14, and packets other than the Hello packet of routing protocol part 6 are stored in queue B15, and the switching of all fault paths to the backup path is completed.
- packets stored in queue A14 are processed with priority over packets stored in queue B15. That is, only the packet stored in the queue A14 is transmitted to the communication path A18, and then the packet stored in the queue B15 is transmitted to the communication path A18.
- the network device 4 according to another embodiment used in the first failure recovery method of the present invention includes a GMPLS control unit 5 constituting a control network, and a data plane network.
- the switch part 13 and the force that constitutes the power are also constructed.
- the network device 4 shown in FIG. 6 is a node device in the GMPLS network that implements the first failure recovery method of the present invention described with reference to FIGS. 1 to 3 (node device N1 in FIGS. 1 and 2). ⁇ N5) used.
- the GMPLS control unit 5 includes a control module group 21 having a routing protocol unit 6 and a signaling protocol unit 7, a queue A14, a scheduling control unit 8, a path setting management unit 11, a failure information notification unit 9, The switch control unit 12 and a communication path A18 to the GMPLS control unit 5 of the other network device 4 are provided.
- the switch unit 13 includes a switch 17 that transfers data packets, a monitor unit 10 that detects a link failure and the like, and a communication path B19 to the switch unit 13 of another network device 4.
- the main difference from the network device 4 described in Fig. 4 is that the queue B15 is omitted, and the failure information detected by the monitor unit 10 is first notified to the signaling protocol unit 7 and all failures are detected. The failure information is notified to the routing protocol section 6 when the path switching to the protection path is completed.
- Each component of the GMPLS control unit 5 and the switch unit 13 generally has the following functions.
- the switch 17 performs processing for transferring a data packet, which has also been transmitted by another network device, to another network device.
- the communication path B19 is a communication path for transferring the data packet that has undergone the data transfer process in the switch 17 to the transmission destination.
- the monitor unit 10 monitors whether a failure has occurred in the link on the communication path B19 or other network device (node device) connected by the link, and detects a failure in the link or other node device. Then, failure information including information on the location of the failure is sent to the failure information notification unit 9.
- the switch control unit 12 controls the switch 17 in the switch unit 13.
- the failure information notification unit 9 receives the failure information notified from the monitor unit 10 in the switch unit 13 and notifies the signaling protocol unit 7 and the scheduling control unit 8 of the failure information. At this point, failure information is not notified to the routing protocol section 6.
- the routing protocol unit 6 exchanges the topology with the adjacent node, and creates a routing table, advertises the TE link, and maintains the relationship with the adjacent node. Exchanges. In addition, when the failure information detected by the monitoring unit 10 is notified, the routing protocol unit 6 exchanges Hello packets to maintain the relationship with the adjacent nodes as in the case of normal operation of the network. At the same time, transmission of packets for updating link status information is started.
- the signaling protocol unit 7 When the network is operating normally, the signaling protocol unit 7 performs LSP setting, LSP deletion, LSP setting state management, and the like. The signaling protocol unit 7 switches the failed path to the backup path if the failure is notified of the failure information from the failure information notifying unit 9 if the working path has its own network device as a starting node. When the local network device becomes the relay node or the end node of the protection path, the signaling protocol unit 7 sends the received Path message and the Resv message, which is the response, to the next node on the failure recovery path. Sent to the node device.
- the queue A14 is used for storing packets transmitted from the routing protocol unit 6 and packets transmitted from the signaling protocol unit 7.
- the scheduling control unit 8 performs transmission processing of the packet stored in the queue A14.
- the scheduling control unit 8 performs transmission processing on the packets stored in the queue A14 in the stored order. In addition, when the failure information is notified from the failure information notification unit 9 and the scheduling control unit 8 completes the transmission processing of the packet in the queue A14 when the failure information is notified, When the transmission of the packet in queue A14 is notified to the primary management unit 11 and the switching of all the failed paths is notified from the path setting management unit 11, the failure information notification unit 9 Is notified to the routing protocol unit 6 and the packet in the queue A14 is transmitted again. If no such notification is received, the routing protocol unit 6 is notified of the failure information. Then, send the packet in queue A14 again.
- the node setting management unit 11 monitors the switching status of the failed path to the protection path by the signaling protocol unit 7 and detects that the switching of all the failed paths to the protection path has been completed. Notify the scheduling control unit 8.
- the routing protocol unit 6 exchanges the topology with neighboring nodes, and sends and receives packets for creating routing tables, advertising TE links, and exchanging Hello packets to maintain the relationship with neighboring nodes. Packets transmitted from the routing protocol unit 6 are stored in the queue A14.
- the signaling protocol unit 7 transmits and receives packets for LSP setting, LSP deletion, LSP setting state management, and the like. Similarly, packets transmitted from the signaling protocol unit 7 are also stored in the queue A14.
- the packet stored in the queue A14 is subjected to transmission processing by the scheduling control unit 8. Packet transmission processing is performed in the order stored in queue A14. A packet for which transmission processing is completed in the queue A 14 is transferred to the transmission destination using the communication path A18.
- the switch 17 of the switch unit 13 transfers the data bucket.
- the signaling protocol unit 7 Upon receiving the failure information from the failure information notifying unit 9, the signaling protocol unit 7 starts switching the failed path to the protection path (step B4), and transmits a packet for switching to the protection path. (Step B5).
- the packet for switching from the failed path to the protection path transmitted from the signaling protocol unit 7 is stored in the queue A14 (step B6).
- the routing protocol unit 6 has not been notified of the failure information yet, so it does not recognize that the failure has occurred, and the operation is performed when the network is operating normally. The work continues.
- the scheduling control unit 8 Upon receiving the failure information, the scheduling control unit 8 monitors the queue A14 in the same manner as when the network is operating normally. When the scheduling control unit 8 detects that there is a packet in the queue A14, Perform transmission processing (step B7). When the transmission process for one packet in queue A14 is completed, scheduling control unit 8 determines whether there is a packet in queue A14 (step B8). Perform transmission processing. If it is determined that there is no packet in the queue A14, the scheduling control unit 8 notifies the path setting management unit 11 that the processing of the packet in the queue A14 has been completed (step B9).
- the path setting management unit 11 determines whether or not the switching of all the failed paths to the protection path has been completed (step B10).
- the path setting management unit 11 sends a signaling packet related to the Resv message to the signaling packet that works on the Path message transmitted from the signaling protocol unit 7 for all the fault paths from which the network device is the origin node.
- the scheduling control unit 8 is notified that the switching to the protection path has been completed (step Bl 1).
- the scheduling control unit 8 confirms again the presence or absence of the packet in the queue A14, and if the existence of the packet is confirmed, performs the transmission process again.
- the path setting management unit 11 notifies the scheduling control unit 8 that the switching of all the paths has been completed (step B12 ).
- the scheduling control unit 8 that has received the notification that the switching to the standby node has been completed notifies the failure information notified to the routing protocol unit 6 from the failure information notification unit 9 (step B13).
- the failure information is notified to the routing protocol unit 6 from the scheduling control unit 8
- the method of notifying from the path setting management unit 11 and the failure information notification unit 9 and the path setting management unit 11 can switch all paths. It is also possible to employ a method of notifying the signaling protocol unit 7 of the completion and notifying the routing protocol unit 6 of the failure information notified from the failure information notification unit 9 by the signaling protocol unit 7.
- the routing protocol unit 6 that has received the failure information from the failure information notification unit 9 transmits a packet that uses the link state information in order to update the link state (step B14). Packets that are useful for the link state information transmitted from the routing protocol unit 6 are stored in the queue A 14 and processed by the scheduling processing unit 8 (step B15). When the transmission process for one packet in queue A 14 is completed, scheduling control unit 8 determines whether there is a packet in queue A 14 (step B16). If it is determined that there is no packet, the failure recovery operation by the routing protocol unit 6 and the signaling protocol unit 7 ends.
- the working path backup is established in the network device (corresponding to node device N1 in the case of Fig. 3) in which the failure of the working path that is the originating node of the own network device is detected.
- the routing protocol public announcements by the routing protocol can be started, competition between signaling packets and routing packets and the occurrence of congestion can be avoided, and pre-brand failure recovery time can be shortened. It also avoids congestion between routing and signaling packets, The probability that ring packets are discarded is reduced, and the reliability of failure recovery can be improved.
- the failure is detected by monitor unit 10 of network device 4 (step Bl in FIG. 5). .
- the monitor unit 10 that has detected the failure notifies the failure information notification unit 9 of the failure information (step B2).
- the failure information notifying unit 9 that has received the failure information transmits the failure information to the sibling protocol unit 7 and the scheduling control unit 8 (step B3).
- the signaling protocol unit 7 that has received the failure information from the failure information notification unit 9 does not switch the failed path to the backup path because the own network device is not the starting node of the failed path. That is, steps B4 to B6 in FIG. 7 are skipped.
- the scheduling control unit 8 that has received the failure information monitors the queue A14 in the same way as when the network is normal, and if it detects that there is a packet in the queue A14, it performs transmission processing of the packet (step S14). B7). When the transmission process for one packet in queue A14 is completed, scheduling control unit 8 determines whether there is a packet in queue A14 (step B8). Perform transmission processing. If it is determined that there is no packet in the queue A14, the scheduling control unit 8 notifies the path setting management unit 11 that the processing of the packet in the queue A14 has been completed (step B9).
- the path setting management unit 11 determines whether or not the switching of all the failed paths to the protection path has been completed (step B10).
- the path setting management unit 11 receives all packets for the failure of all the failed links for which the own network device is a relay node, and for the power of the network device that is the starting node, for all failed links. Judge that switching to the spare node of the path is complete. If it is determined that switching of all fault paths to the backup path has not been completed, the scheduling control unit 8 is notified that switching to the backup node has been completed (step Bl 1). .
- the scheduling control unit 8 confirms the presence / absence of a packet in the queue A14 again, and performs transmission processing again when the existence of the packet is confirmed.
- the path setting management unit 11 notifies the scheduling control unit 8 that the switching of all the paths has been completed (step B12 ).
- the scheduling control unit 8 that has received the notification that the switching to the standby node has been completed notifies the failure information notified to the routing protocol unit 6 from the failure information notification unit 9 (step B13).
- the failure information is notified to the routing protocol unit 6 from the scheduling control unit 8
- the method of notifying from the path setting management unit 11 and the failure information notification unit 9 and the path setting management unit 11 can switch all paths. It is also possible to employ a method of notifying the signaling protocol unit 7 of the completion and notifying the routing protocol unit 6 of the failure information notified from the failure information notification unit 9 by the signaling protocol unit 7.
- the routing protocol unit 6 that has received the failure information from the failure information notification unit 9 transmits a packet that uses the link state information in order to update the link state (step B14). Packets that are useful for the link state information transmitted from the routing protocol unit 6 are stored in the queue A 14 and processed by the scheduling processing unit 8 (step B15). When the transmission process for one packet in queue A 14 is completed, scheduling control unit 8 determines whether there is a packet in queue A 14 (step B16). If it is determined that there is no packet, the failure recovery operation by the routing protocol unit 6 and the signaling protocol unit 7 ends.
- the network path (corresponding to node apparatus N4 in the case of Fig. 3) in which the local network apparatus detects a failure in the working path that serves as a relay node,
- public announcements by the routing protocol can be started, competition between signaling packets and routing packets and the occurrence of congestion can be avoided, and pre-brand failure recovery time can be shortened.
- congestion of routing packets and signaling packets is avoided, the probability of discarding signaling packets is reduced, and the reliability of failure recovery can be improved.
- the network device 4 first notifies the failure information to the signaling protocol unit 7, and notifies the failure information to the routing protocol unit 6 when the switching of all the failed paths to the reserved path is completed.
- the timing of the notification operation on the failure path by the routing protocol unit 6 and the failure recovery operation by the signaling protocol unit 6 are shifted.
- the contention of packets transmitted from the protocol part 7 is eliminated, and the pre-brand failure recovery time can be shortened.
- the discarding of signaling packets is eliminated, the reliability of failure recovery is improved.
- the timing of notification of failure information is shifted to shift the timing of failure notification operation by the routing protocol unit 6 and failure recovery operation by the signaling protocol unit 6. Notifies the routing protocol unit 6 and the signaling protocol unit 7 at the same timing, and the routing protocol unit 6 does not immediately start the failure notification operation even when the failure information is notified, and all the failed paths are switched to the backup path.
- the same effect can be obtained by starting the failure notification operation when the completed notification is received from the scheduling control unit 9, for example.
- N1 to N5 represent node devices constituting the GMPLS network, and 1 is a link connecting the respective node devices N1 to N5.
- Link 1 can be any wire that can communicate, such as an optical fiber cable (registered trademark).
- N1-N4-N5 is set as the working path P1.
- the failure recovery type of this working path P1 is 1: 1 of the pre-brand 'path failure recovery method', and N1 is used as a backup path to be used instead of the working path P1 when a failure occurs in the working path P1.
- —N3—N5 is set.
- it is the node device N1 that is the starting node of the path that stores the protection path P2 of the working path P1.
- the GMPLS network shown in Fig. 8 has a working path of P1 1 Although only one is set, two or more working paths may be set. In that case, use the Shared type pre-brand 'path failure recovery method and share the same protection path between the two working paths.
- the signaling packet 2 shown in Fig. 8 is a packet for switching the path when a failure occurs, and is transferred from the source node device N1 to the destination node device N5 of the backup path.
- the routing packet 3 shown in FIG. 8 is a packet that is advertised to an adjacent node to update the link state because the link state changes due to the failure when a failure occurs. Routing protocol OSPF or a packet based on a routing protocol extended to GMPLS.
- routing packet 3 and signaling packet 2 are sent out using different communication paths. For example, use physically different channels, or assign different wavelengths on the same physical channel.
- a communication path implemented in In-Band is separated from the first control channel that is implemented in the Out-of-Band communication path between adjacent node devices. If the second control channel generated in the above is installed and the network is operating normally, packets according to the signaling protocol and packets according to the routing protocol are exchanged between the node devices via the first control channel.
- a part of the packets according to these two protocols is exchanged between the node devices via the second control channel. For example, routing protocol Hello packets and signaling protocol packets use the second control channel, and packets other than routing protocol Hello packets use the first control channel.
- the node device N1 and the node device N4 detect the failure.
- the node device Nl and the node device N4 that detect the failure each start failure recovery. In this case, since the node device N1 is the starting node of the working path P1, and the node device N4 is not the starting node of the working path P1, different operations are performed. Hereinafter, the operations of the node device N1 and the node device N4 will be described.
- the failure recovery operation of the node device N1 that is the starting node of the working path P1 will be described.
- the signaling device uses the second control channel to switch the working path P 1 that uses the link to the protection path P 2.
- a signaling packet 2 called a Path message is transmitted to the node device N5 that is the end node of the protection path P2 through the node device N3.
- the node device N1 uses the first control channel to transmit the routing packet 3 for updating the link state change to the other node device. To do.
- the Path message by the signaling packet 2 requests the node on the recovery path of the protection path P2 to set the label given to each link.
- the Path message is transmitted to the node device N5 via the node device N3.
- the node device N3 that has received the Path message sets a switch to use the protection path P2.
- a Pat h message is sent to the node device N5.
- the node device N5 that has received the Path message determines that the packet is addressed to its own node, sets the switch, and then sends the signaling packet 2 called the Resv message to the node device N1 on the reverse path to the Path message. Send to.
- the node device N3 that has received the Resv message changes the label information in the Resv message, and then sends the Resv message to the node device N1.
- the node device N1, which has received the Resv message has completed the setting of the protection path P2, and thereafter transmits the packet transmitted to the working path P1 to the protection path P2.
- the failed working path P1 is switched to the protection path P2.
- there is only one failure path that has node device N1 as the starting node but if there are multiple failure paths that have node device N1 as the starting node, node device N1 All failed paths are switched to backup paths in the same way as when the failed working path P1 is switched to backup path P2.
- the routing protocol in the node device Nl uses the first control channel to update the routing packet 3 to the node device N2, the node device N3, and the node in order to update the state change of the failed link.
- the node device N2 that has received the routing packet 3 transmits the routing packet 3 to the node device N3 and the node device N5 using the first control channel. Thereafter, the routing packet 3 for updating the link state change in the same way is sequentially propagated.
- Each node device that receives routing packet 3 performs operations specified in the routing protocol, such as updating the topology database. When the topology database of all the node devices in the network is updated, the failure recovery operation performed from the occurrence of the failure ends.
- the failure recovery operation of the node device N4 that is a relay node of the working path P1 will be described.
- the node device N4 determines that a failure has occurred in the working path P1 that uses the link 1.
- the node device N4 since there is no other failure path in which the starting node of the working path P1 is the own node device N4 that is not the own node device N4, the node device N4 was performed by the node device N1 described above. No fault recovery operation is performed by such a signaling protocol.
- the routing for updating the link state change using the first control channel according to the routing protocol is performed. Send the packet to the other node equipment.
- network device 4 that is useful in the present embodiment includes GMPLS control unit 5 and switch unit 13 that form a control network.
- the network device 4 shown in FIG. 9 is used as a node device (node devices N1 to N5 in FIG. 8) in the GMPLS network that implements the second failure recovery method of the present invention described with reference to FIG. Used.
- the GMPLS control unit 5 includes a control module group 21 having a routing protocol unit 6 and a signaling protocol unit 7, a transmission / reception unit 20, a failure information notification unit 9, a switch control unit 12, and other network devices 4.
- a communication path A18 to the GMPLS control unit 5 is provided.
- the switch unit 13 includes a switch 17 that transfers data packets, a monitor unit 10 that detects a link failure and the like, an In-Band control channel separation unit 22, and a switch unit 13 of another network device 4. And communication channel B19.
- the switch 17 performs processing for transferring the data packet transmitted from the other network device 4 to the other network device 4.
- the communication path B19 is a communication path for transferring the data packet subjected to the data transfer processing in the switch 17 to the transmission destination.
- the communication path B19 is a communication path for transmitting and receiving the control bucket. Is also used.
- the monitor unit 10 is a link on the communication path B19 and other network devices connected by the link.
- the switch control unit 12 controls the switch 17 in the switch unit 13.
- the failure information notification unit 9 receives the failure information notified from the monitor unit 10 in the switch unit 13, and receives the routing protocol unit 6, the signaling protocol unit 7, and the transmission / reception unit.
- the routing protocol unit 6 uses the transmission / reception unit 20 to perform topology exchange with adjacent nodes to create a routing table.
- the routing protocol unit 6 uses the transmission / reception unit 20 when there is a failure notified of the failure information from the failure information notification unit 9, and updates the link status information and makes it adjacent as if the network is operating normally. Exchange Hello packets to maintain the relationship with the node.
- the signaling protocol unit 7 uses the transmission / reception unit 20 to perform LSP setting, LSP deletion, LSP setting state management, and the like.
- the signaling protocol unit 7 uses the transmission / reception unit 20 to determine the failure path if the failure of the working path starts from its own network device 4. Switch to the backup path.
- the transmission / reception unit 20 transmits / receives packets between the routing protocol unit 6 and the signaling protocol unit 7 between adjacent network devices.
- the transmission / reception unit 20 transmits / receives packets from the routing protocol unit 6 and the signaling protocol unit 7 using the communication path A18.
- the transmission / reception unit 20 transmits and receives the Hello packet by the routing protocol unit 6 and the packet by the signaling protocol unit 7 using the communication path B 19, Packets other than Hello packets sent by the routing protocol section 6 are sent and received using channel A18.
- the SONETZSDH (Synchronous) packet is sent from the signaling protocol unit 7 and the Hello packet that performs liveness confirmation with the neighbor sent from the routing protocol unit 6.
- In—Band control channel separation unit 22 transmits the sirennering packet and Hello packet passed from transmission / reception unit 20 of own network device 4 to adjacent network device 4 using communication path B19.
- the packet received from the adjacent network device 4 through the communication path B19 is separated into a signaling packet, a Hello packet, and other packets, and the former packet is sent to the transmitting / receiving unit 20 of the own network device 4 and the latter packet. Is sent to switch 17 of its own network device 4.
- the routing protocol unit 6 exchanges the topology with the adjacent node, and creates the routing table, advertises the TE link, and maintains the relationship with the adjacent node. Packets are sent and received for Hello packet exchange. Packets transmitted from the routing protocol unit 6 are transmitted / received between the network devices 4 by the transmission / reception unit 20 using the communication path A18.
- the signaling protocol unit 7 transmits and receives packets for LSP setting, LSP deletion, LSP setting state management, and the like. Similarly, a packet transmitted from the signaling protocol unit 7 is also transmitted and received between the network devices 4 by the transmission / reception unit 20 using the communication path A18.
- the switch 17 of the switch unit 13 transfers the data bucket. Data packets are transmitted and received between the network devices 4 through the communication path B 19.
- the monitor unit 10 of the network device 4 detects the failure, and the failure information is displayed in the monitor unit 10 Is notified to the failure information notification unit 9.
- the failure information notification unit 9 that has received the failure information notifies the control module group 21 and the transmission / reception unit 20 of the failure information.
- the control module group 21 that has received the fault information starts fault recovery.
- the signaling protocol unit 7 included in the control module group 21 transmits a packet for switching the failure path, and the routing protocol unit 6 transmits a packet for updating the failure link state change.
- the transmitted bucket is stored in a queue or a buffer (not shown) in the transceiver 20.
- the transmission / reception unit 20 Since the transmission / reception unit 20 receives the failure information, the transmission / reception unit 20 sorts the routing packet, the sibling packet, and the Hello packet that is a part of the routing packet.
- the routing packet uses channel A18, and the signaling packet and Hel The lo packet is sent using communication path B19.
- the DCC Data
- the routing packet transmitted using the communication path A 18 arrives at the adjacent node, it is delivered to the routing protocol unit 6 by the transmission / reception unit 20.
- a packet sent using the communication path B19 arrives at an adjacent node, it is sent to the In—Band control channel separation unit 22 !, and if it is a signaling packet or Hello packet, it is sent to the GMPLS control unit 5. If it is a packet other than, it is sent to switch 17.
- Network device that has detected a failure in the working path whose local network device is the relay node
- the operation of the signaling protocol unit 7 that switches the failed path to the protection path is not performed, but the only difference is that the other operations are The operation is almost the same as that of the network device 4 (corresponding to the node device N1 in the case of FIG. 8) that detects the failure of the working path whose device is the starting node.
- the network device 4 that is effective in this embodiment uses a communication path A 18 in which a packet transmitted from the routing protocol unit 6 is implemented in an out-of-band when a working path fails, and a signaling protocol
- the packet transmitted from part 7 uses part of the communication path B19 implemented in In-Band, so there is no contention in the control channel. This makes it possible to quickly process packets for path switching when a failure occurs, thereby reducing failure recovery time. Furthermore, since packets transmitted from the signaling protocol unit 7 can be processed quickly, packet discard is eliminated. As a result, the reliability of failure recovery can be improved.
- the communication path A18 uses only packets transmitted from the routing protocol unit 6. For this reason, the control channel band can be designed to be small considering only the packet transmitted from the routing protocol unit 6.
- GMPLS has a link management protocol and signaling protocol in addition to the routing protocol and signaling protocol
- the control module group 21 has a link management protocol. It is also possible to run a scheduling algorithm between protocols. When a failure occurs, the link management protocol starts the operation of exchanging control packets (Channel Status message and Channel Status Ack message) for identifying the failure location with neighboring nodes. This Channel
- the network device of the present invention can be realized by a computer and a program as well as by realizing the functions of the network device in the form of software.
- the program is provided by being recorded on a computer-readable recording medium such as a magnetic disk or a semiconductor memory, read by the computer at the time of starting up the computer, etc., and controlling the operation of the computer.
- the network device 4 functions as a routing protocol unit 6, a signaling protocol unit 7, a scheduling control unit 8, a path setting management unit 11, a failure information notification unit 9, a switch control unit, and the like.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/574,380 US20070211623A1 (en) | 2004-08-30 | 2005-08-29 | Failure recovery method, network device, and program |
CN2005800288906A CN101015176B (zh) | 2004-08-31 | 2005-08-29 | 故障恢复方法和网络装置 |
JP2006532651A JP4488248B2 (ja) | 2004-08-31 | 2005-08-29 | 障害回復方法およびネットワーク装置ならびにプログラム |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2004-251872 | 2004-08-30 | ||
JP2004251872 | 2004-08-31 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006025296A1 true WO2006025296A1 (ja) | 2006-03-09 |
Family
ID=35999950
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2005/015620 WO2006025296A1 (ja) | 2004-08-30 | 2005-08-29 | 障害回復方法およびネットワーク装置ならびにプログラム |
Country Status (4)
Country | Link |
---|---|
US (1) | US20070211623A1 (ja) |
JP (1) | JP4488248B2 (ja) |
CN (1) | CN101015176B (ja) |
WO (1) | WO2006025296A1 (ja) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007066442A1 (ja) * | 2005-12-05 | 2007-06-14 | Nippon Telegraph And Telephone Corporation | 故障救済方法およびパケット通信装置 |
JP2007324981A (ja) * | 2006-06-01 | 2007-12-13 | Alaxala Networks Corp | ネットワーク接続装置およびネットワーク接続方法 |
JP2008061139A (ja) * | 2006-09-01 | 2008-03-13 | Kddi Corp | ネットワーク監視装置およびネットワーク監視方法、コンピュータプログラム |
JP2013034080A (ja) * | 2011-08-01 | 2013-02-14 | Nippon Telegr & Teleph Corp <Ntt> | 経路情報更新システム、及び経路情報更新方法 |
Families Citing this family (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4688757B2 (ja) * | 2006-08-23 | 2011-05-25 | 株式会社日立製作所 | 通信路障害回復方式 |
US8166156B2 (en) * | 2006-11-30 | 2012-04-24 | Nokia Corporation | Failure differentiation and recovery in distributed systems |
JP5377845B2 (ja) | 2007-10-25 | 2013-12-25 | 本田技研工業株式会社 | 燃料電池システム及びその掃気方法 |
JP4607254B2 (ja) * | 2008-06-12 | 2011-01-05 | パナソニック株式会社 | ネットワーク監視装置、バスシステム監視装置、方法、およびプログラム |
WO2010084775A1 (ja) * | 2009-01-26 | 2010-07-29 | パナソニック株式会社 | 中継装置、制御方法、およびプログラム |
KR101289890B1 (ko) * | 2009-11-10 | 2013-07-24 | 한국전자통신연구원 | 트래픽 엔지니어링 토폴로지 생성을 위한 장치 및 방법 |
JPWO2011083780A1 (ja) | 2010-01-05 | 2013-05-13 | 日本電気株式会社 | 通信システム、制御装置、処理規則の設定方法、パケットの送信方法およびプログラム |
JP5510000B2 (ja) * | 2010-03-31 | 2014-06-04 | ソニー株式会社 | コンテンツ送信装置、コンテンツ再生システム、コンテンツ送信方法、およびプログラム |
US8929735B2 (en) * | 2010-05-07 | 2015-01-06 | Ciena Corporation | Dynamic trail termination point creation for optical transport networks |
US8670302B2 (en) * | 2010-06-10 | 2014-03-11 | Infinera Corporation | Activation signaling in transport networks |
US8908533B2 (en) | 2010-06-10 | 2014-12-09 | Infinera Corporation | Supporting OAM on protecting connections in shared mesh protection environment |
US8627137B1 (en) | 2010-09-16 | 2014-01-07 | Cisco Technology, Inc. | Graceful handling of critical traffic blackholing faults |
US10250492B2 (en) * | 2010-12-15 | 2019-04-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Segment recovery in connection-oriented network |
WO2012163432A1 (en) * | 2011-05-27 | 2012-12-06 | Telefonaktiebolaget L M Ericsson (Publ) | Setting up precalculated alternate path for circuit following failure in network |
CN102664755B (zh) * | 2012-04-20 | 2014-12-10 | 杭州华三通信技术有限公司 | 控制通道故障确定方法及其装置 |
KR20150088559A (ko) * | 2014-01-24 | 2015-08-03 | 한국전자통신연구원 | 네트워크의 장애를 복구하는 방법 및 장치 |
US9998930B2 (en) | 2015-05-15 | 2018-06-12 | Qualcomm Incorporated | Anchor assisted communication channel hopping |
US10039052B2 (en) | 2015-05-15 | 2018-07-31 | Qualcomm Incorporated | Anchor assisted communication channel hopping |
CN107646170A (zh) * | 2015-05-15 | 2018-01-30 | 高通股份有限公司 | 锚辅助的通信信道跳跃 |
CN105763448B (zh) * | 2016-03-07 | 2019-08-06 | 新华三技术有限公司 | 一种报文传输方法和装置 |
CN111989898B (zh) * | 2018-03-26 | 2022-03-15 | 住友电气工业株式会社 | 车载通信系统、交换机装置、通信控制方法和计算机可读存储介质 |
CN112953785B (zh) * | 2019-12-10 | 2022-03-01 | 烽火通信科技股份有限公司 | 用于多核处理器的通信设备的链路检测方法及系统 |
JP7063926B2 (ja) * | 2020-02-17 | 2022-05-09 | 矢崎総業株式会社 | 通信システム |
US20230030168A1 (en) * | 2021-07-27 | 2023-02-02 | Dell Products L.P. | Protection of i/o paths against network partitioning and component failures in nvme-of environments |
CN116980345A (zh) * | 2022-04-22 | 2023-10-31 | 华为技术有限公司 | 故障处理方法、网络设备、存储介质和芯片系统 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003218912A (ja) * | 2002-01-23 | 2003-07-31 | Nec Corp | パス障害回復方式及び障害復旧後の切戻方式並びにそれらを用いるノード |
JP2003224591A (ja) * | 2002-01-31 | 2003-08-08 | Nec Corp | 光通信ネットワーク及びそれに用いる光通信ネットワーク設計方法 |
JP2004032602A (ja) * | 2002-06-28 | 2004-01-29 | Matsushita Electric Ind Co Ltd | パケット伝送装置及びその方法 |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6226296B1 (en) * | 1997-01-16 | 2001-05-01 | Physical Optics Corporation | Metropolitan area network switching system and method of operation thereof |
US6535480B1 (en) * | 1998-11-20 | 2003-03-18 | At&T Corp. | System and method to provide survivability for broadcast video and interactive IP-based services on cable access networks |
US6535481B1 (en) * | 1999-08-20 | 2003-03-18 | Nortel Networks Limited | Network data routing protection cycles for automatic protection switching |
US6741553B1 (en) * | 1999-12-08 | 2004-05-25 | Nortel Networks Limited | Method and system for protecting virtual traffic in a communications network |
CA2310872A1 (en) * | 1999-12-22 | 2001-06-22 | Nortel Networks Corporation | Automatic protection switching using link-level redundancy supporting multi-protocol label switching |
US7170852B1 (en) * | 2000-09-29 | 2007-01-30 | Cisco Technology, Inc. | Mesh with projection channel access (MPCA) |
US7130264B2 (en) * | 2001-12-26 | 2006-10-31 | Ciena Corporation | Service protection method and apparatus for TDM or WDM communications networks |
-
2005
- 2005-08-29 CN CN2005800288906A patent/CN101015176B/zh not_active Expired - Fee Related
- 2005-08-29 JP JP2006532651A patent/JP4488248B2/ja not_active Expired - Fee Related
- 2005-08-29 WO PCT/JP2005/015620 patent/WO2006025296A1/ja active Application Filing
- 2005-08-29 US US11/574,380 patent/US20070211623A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003218912A (ja) * | 2002-01-23 | 2003-07-31 | Nec Corp | パス障害回復方式及び障害復旧後の切戻方式並びにそれらを用いるノード |
JP2003224591A (ja) * | 2002-01-31 | 2003-08-08 | Nec Corp | 光通信ネットワーク及びそれに用いる光通信ネットワーク設計方法 |
JP2004032602A (ja) * | 2002-06-28 | 2004-01-29 | Matsushita Electric Ind Co Ltd | パケット伝送装置及びその方法 |
Non-Patent Citations (2)
Title |
---|
NISHIOKA I.ET AL: "GMPLS Seigyo Plane no Scalability Hyoka. (Study on Scalability of GMPLS......and Control Traffic)", IEICE COMMUNICATIONS SOCIETY TAIKAI KOEN RONBUNSHU 2., 10 September 2003 (2003-09-10), B-7-66, pages 247, XP002998866 * |
SAGARA K.: "Hikari Contents Haishin Network Muke Hybrid Router no Teian. (Proposal of optical hybrid router for future contents delivery networks)", THE INSTITUTE OF ELECTRONICS, INFORMATION AND COMMUNICATION ENGINEERS., 2 August 2002 (2002-08-02), pages 1 - 4, XP002998867 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007066442A1 (ja) * | 2005-12-05 | 2007-06-14 | Nippon Telegraph And Telephone Corporation | 故障救済方法およびパケット通信装置 |
US8462617B2 (en) | 2005-12-05 | 2013-06-11 | Nippon Telegraph And Telephone Corporation | Method for relieving failure, and packet communication device |
JP2007324981A (ja) * | 2006-06-01 | 2007-12-13 | Alaxala Networks Corp | ネットワーク接続装置およびネットワーク接続方法 |
JP2008061139A (ja) * | 2006-09-01 | 2008-03-13 | Kddi Corp | ネットワーク監視装置およびネットワーク監視方法、コンピュータプログラム |
JP2013034080A (ja) * | 2011-08-01 | 2013-02-14 | Nippon Telegr & Teleph Corp <Ntt> | 経路情報更新システム、及び経路情報更新方法 |
Also Published As
Publication number | Publication date |
---|---|
CN101015176B (zh) | 2011-04-20 |
CN101015176A (zh) | 2007-08-08 |
JPWO2006025296A1 (ja) | 2008-05-08 |
JP4488248B2 (ja) | 2010-06-23 |
US20070211623A1 (en) | 2007-09-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4488248B2 (ja) | 障害回復方法およびネットワーク装置ならびにプログラム | |
US7710860B2 (en) | Data relay apparatus and data relay method | |
US6865149B1 (en) | Dynamically allocated ring protection and restoration technique | |
EP1903725B1 (en) | Packet communication method and packet communication device | |
EP2560326B1 (en) | Ring network protection method, network node and ring network | |
EP1262042B1 (en) | Routing switch for dynamically rerouting traffic due to detection of faulty link | |
WO2009119571A1 (ja) | 通信ネットワークシステム、通信装置、経路設計装置及び障害回復方法 | |
EP2013996B1 (en) | System and method of multi-nodal aps control protocol signalling | |
US20060013127A1 (en) | MPLS network system and node | |
JP2004533142A (ja) | 動的割り当てリングの保護および復元技術における帯域幅確保の再利用 | |
WO2009082923A1 (fr) | Procédé de traitement de défaut de liaison et dispositif de transfert de données | |
GB2471761A (en) | Fault recovery path reconfiguration in ring networks | |
CN102480368B (zh) | 一种聚合链路的保护方法及系统 | |
EP2254289B1 (en) | Method, device, and system for establishing label switching path in fast rerouting switching | |
US10250492B2 (en) | Segment recovery in connection-oriented network | |
EP2658177B1 (en) | Method for detecting tunnel faults and traffic engineering node | |
WO2008119294A1 (fr) | Procédé et matériel de restauration du commerce en réseau | |
WO2011076024A1 (zh) | 传送多协议标签交换网络系统和链路保护方法 | |
WO2003065218A1 (en) | Mesh protection service in a communications network | |
WO2010028560A1 (zh) | 在mesh网络中实现永久环网保护的方法 | |
WO2010121459A1 (zh) | 一种自动交换光网络中实现保护与恢复的方法及系统 | |
KR20150002474A (ko) | 통신 네트워크에서 장애 복구 방법 | |
WO2012097595A1 (zh) | 一种共享网状保护实现方法及系统 | |
WO2010015161A1 (zh) | 业务恢复的方法、系统和设备 | |
JP2006033124A (ja) | トンネル障害通知装置および方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2006532651 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11574380 Country of ref document: US Ref document number: 2007211623 Country of ref document: US Ref document number: 200580028890.6 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWP | Wipo information: published in national office |
Ref document number: 11574380 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |