WO2009089726A1 - Procédé, système et appareil pour synchroniser des chemins de protocole bgp - Google Patents

Procédé, système et appareil pour synchroniser des chemins de protocole bgp Download PDF

Info

Publication number
WO2009089726A1
WO2009089726A1 PCT/CN2008/073723 CN2008073723W WO2009089726A1 WO 2009089726 A1 WO2009089726 A1 WO 2009089726A1 CN 2008073723 W CN2008073723 W CN 2008073723W WO 2009089726 A1 WO2009089726 A1 WO 2009089726A1
Authority
WO
WIPO (PCT)
Prior art keywords
routing information
notification message
information
module
received
Prior art date
Application number
PCT/CN2008/073723
Other languages
English (en)
Chinese (zh)
Inventor
Shunwan Zhuang
Hui Ni
Qing Zeng
Shuanglong Chen
Xin Zhang
Hongjie Yang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2009089726A1 publication Critical patent/WO2009089726A1/fr

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/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • 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/033—Topology update or discovery by updating distance vector protocols

Definitions

  • the present invention relates to a Border Gateway Protocol (BGP), and more particularly to a method, system and apparatus for route synchronization of a border gateway protocol.
  • Border Gateway Protocol BGP
  • NSF Network Stop Leave Forwarding
  • the related network protocols are required to support the Graceful Restart (GR) technology, so that the data can be forwarded normally during the synchronization of the routing protocol and the re-synchronization of the route to ensure that the key services are not interrupted.
  • GR technology has been widely used in active and standby switching and system upgrades.
  • the GR technology can only be triggered when the router re-initiates the establishment of a Transmission Control Protocol (TCP) session, the BGP is continuously re-established (ie, without disconnecting the communication link with the BGP neighbor).
  • TCP Transmission Control Protocol
  • BGP peer group inter-group switching There are two important application scenarios in the BGP continuous re-establishment scenario: BGP peer group inter-group switching and TCP hot backup. The following describes how to perform BGP route synchronization in these two scenarios.
  • BGP BGP peers with the same egress policy are configured in the same address family to form a BGP peer-group (BGP Update-group). Therefore, only one update (UPDATE) is encapsulated to avoid each BGP.
  • the neighbors send the repeated processing of the encapsulated UPDATE packets, which greatly simplifies the processing of encapsulated packets, enabling BGP to achieve faster convergence.
  • BGP peer-to-peer group There are multiple BGP peers in a BGP peer-to-peer group. After a BGP peer in a BGP peer group changes the egress policy, the system changes the egress policy based on the BGP peer. Re-discover another BGP peer-packing group (which can be called a destination group) for the BGP peer. After the BGP peer ends working in the current group, you can switch to the destination group. The handover process may be referred to as an inter-group handover procedure. After the BGP peers complete the switchover, they need to synchronize the BGP routes with their peers to ensure that the next hop of the route is reachable.
  • Another router establishes a BGP connection between RouterB.
  • Router A there are two BGP peer-to-peer groups, namely Group A (Group A) and Group B (Group B); Group A includes a peer K Peerl ), and Peerl corresponds to the peer on Router B.
  • Group A includes a peer K Peerl
  • Peerl corresponds to the peer on Router B.
  • All BGP routes in Router A can form a set, called RouteSet; and all the BGP routes that conform to the GroupA egress policy can be called RouteSetA, and all meet the GroupB export policy.
  • the set of BGP routes can be called RouteSetB. Therefore, RouteSetA and RouteSetB are respectively a subset of RouteSet. RouteSetA and RouteSetB have intersections, that is, some BGP routes may belong to both RouteSetA and RouteSetB, but under normal circumstances, RouteSetA and RouteSetB will not be identical.
  • the Peer1 sends the information of the added route to the peer Peer2.
  • Peer1 If the current route to be processed does not comply with the egress policy of GroupB, Peer1 sends the information of the revocation route to the peer Peer2.
  • the BGP peer needs to traverse the entire BGP route set to update the route after the inter-group handover occurs, and the traversal speed is slow and the efficiency is low; After the switchover, the BGP peers make the BGP peers in the process of inter-group switchover to ensure that the routes at both ends of the peer switch are synchronized.
  • the peer corresponding to the body receives some repeated information about the added route and the information of the redundant route.
  • TCP hot backup is introduced.
  • a router with a main control board and a standby main control board is used. Two boards work at the same time, but only the main control board outputs an effective control signal, and the control signal output by the standby main control board
  • the system switches to the standby main control board, and the standby main control board takes over the original main control board.
  • the above process is called active/standby switchover.
  • the active/standby switchover Before performing the above-mentioned active/standby switchover, you need to back up the TCP session information between the main control board and the standby main control board.
  • the active/standby switchover the upper layer protocol of the TCP hot backup can be used to interrupt the BGP neighbor relationship. In the case of a connection, a smooth transition of all services related to the upper layer protocol of the TCP hot backup is completed.
  • the inventor has found that at least the following problems exist in the prior art solution: Since the router does not disconnect from the BGP neighbor in the TCP hot backup, there is no connection process for re-initiating the establishment of the TCP session, so Apply GR technology to TCP hot backup technology. Therefore, in the above-mentioned active/standby switchover process, the TCP hot backup processes the upper layer protocol data in the following manner: Maintaining the state of the TCP session unchanged, completely backing up the upper layer data, and then backing up the backup data after the active/standby switchover is completed. It is sent to the upper layer to complete the route synchronization.
  • the upper layer protocol temporarily suspends reading the TCP data, so that the TCP data is accumulated in the TCP buffer of the standby main control board; therefore, the standby main control board in the router will give A backpressure information of the peer end of the router causes the peer end to delay sending data, which causes the TCP data stream of the peer end to be sent slowly, which affects the data forwarding of the peer end.
  • Embodiments of the present invention provide a method, system, and apparatus for routing gateway protocol routing synchronization, so as to implement efficient and high-speed BGP route synchronization between nodes without interruption of BGP sessions between nodes.
  • a method for route synchronization of a border gateway protocol comprising:
  • the aging identification information is added to the routing information, where the routing information is the routing information that has been received before the start notification message is received, and the routing information is sent by the start notification.
  • the node of the message is sent;
  • the aging identification information in the routing information with the aging identification information is removed; the received routing information and the routing information with the aging identification information If not, the received routing information is received. After receiving the ending notification packet, the routing information with the aging identification information is deleted.
  • a system for routing synchronization of a border gateway protocol is further provided, where the system includes: a first node and a second node;
  • the first node sends a start notification message, the obtained routing information, and an end notification message to the second node;
  • the second node adds aging identification information to all routing information sent by the first node before receiving the start notification message; receiving routing information, when receiving routing information When the routing information with the aging identification information is the same, the aging identification information in the routing information with the aging identification information is removed. When the received routing information is different from the routing information with the aging identification information, the received routing information is stored. Receiving the end notification message, and deleting the routing information with the aging identification information after receiving the end notification message.
  • the device of the present invention further provides a device for routing synchronization of a border gateway protocol, and the device includes: an indication module, a collection module, and a sending module;
  • the indication module is configured to output a start instruction to the sending module and the collecting module when the routing synchronization starts; output an ending instruction to the sending module according to the output completion message sent by the collecting module;
  • the collecting module is configured to receive the device Routing information sent by the connected node; outputting the received routing information to the sending module according to the start instruction; and returning the output completion message to the indicating module after all the routing information is output to the sending module;
  • the sending module is configured to output a start notification message according to the start instruction, output routing information sent by the collection module, and output an end notification message according to the end instruction.
  • the device of the present invention further provides a device for routing synchronization of a border gateway protocol, and the device includes: a receiving module and a synchronization module;
  • the receiving module is configured to send the received start notification message, routing information, and end notification message to the synchronization module;
  • the synchronization module is configured to add aging identification information to the routing information when the start notification message is received, where the routing information is routing information that has been received before receiving the start notification message, and the routing The information is sent by the node that sends the start notification message; when the received routing information is the same as the routing information with the aging identification information, the aging identification information in the routing information with the aging identification information is removed; when the received route is received When the information is different from the routing information with the aging identification information, the received routing information is stored. After receiving the ending notification message, the routing information with the aging identification information is deleted.
  • an embodiment of the present invention provides a method, system, and apparatus for routing gateway protocol routing synchronization.
  • the on-demand aging capability provided in the foregoing method, only the aging identification information is added to the routing information stored by the node, and the aging identification information on the original routing information is removed according to the updated routing information, and finally all If the routing information with the aging identification information is deleted, the BGP routing between the nodes can be synchronized without interrupting the BGP session between the nodes.
  • the traversal speed in the route synchronization process is greatly improved, and the operation process is simplified.
  • the BGP route synchronization method can also be applied to the application scenario of the TCP hot backup.
  • FIG. 2 is a flowchart of a method for BGP route synchronization in an embodiment of the present invention.
  • FIG. 4 is a topological structural diagram of BGP route synchronization in TCP hot backup according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a method for synchronizing BGP routes in TCP hot backup according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a BGP route synchronization system according to an embodiment of the present invention.
  • Start notification 4 for example, StartAgingRoute
  • End notification for example, EndAgingRoute
  • the start notification message is used to notify the peer end to start the on-demand aging process
  • the end notification message is used to notify the peer end to end the on-demand aging process.
  • the foregoing end notification message may also be a routing information base end point (End-Of-Rib) message frequently used in the GR technology.
  • both nodes that need to perform BGP route synchronization can support The ability to use the aging capability is successful, and the negotiation is successful in the BGP negotiation and establishment process.
  • two nodes supporting on-demand aging capability are used: The first node and the second node are used as an example to describe the method of BGP route synchronization using the on-demand aging capability.
  • FIG. 2 is a flowchart of a method for BGP route synchronization according to an embodiment of the present invention. As shown in FIG. 2, the method for synchronizing BGP routes in the embodiment of the present invention includes the following steps:
  • Step 201 The first node sends a start notification message to the peer second node.
  • the first node sends a start notification message to the second node at a predetermined time in the case that the first node keeps the connection with the neighboring node, and notifies the peer to start the on-demand aging process.
  • the first node that sends the start notification message may be referred to as an active node, and the second node that receives the start notification message is referred to as a passive speaker.
  • Step 202 The second node starts the on-demand aging process according to the start notification message.
  • the second node after receiving the start notification message sent by the first node, the second node adds aging identification information to all BGP routing information sent by the first node before receiving the start notification message, and simultaneously Start a timer.
  • the routing information with the aging identification information remains in the active state.
  • Step 203 The first node sends the collected valid routing information to the second node.
  • the first node first collects valid BGP routing information, and sends the collected valid routing information to the second node. After the routing information is sent, an end notification message is sent to the second node.
  • the end notification message may be an EndAgingRoute message or an End-Of-Rib message commonly used in the GR technology.
  • Step 204 The second node performs route synchronization according to the routing information sent by the first node.
  • the second node compares the routing information sent by the first node with the routing information that has the aging identification information, if the received routing information sent by the first node is related to one of the second nodes. If the routing information of the aging identification information is the same, the aging label is added. The aging identification information of the routing information of the information is removed and becomes the normal routing information. If the routing information of the aging identification information plus the routing information sent by the first node is not stored in the second node, The second node stores the routing information received by the strip.
  • the second node When the second node receives the end notification message (for example, an EndAgingRoute message or an End-Of-Rib message) sent by the first node, or when the timer of the second node expires, the second node will have all The routing information of the aging identification information is deleted, so that BGP route synchronization is implemented. In addition, when the second node receives the end notification message sent by the first node, the timer is turned off.
  • the end notification message for example, an EndAgingRoute message or an End-Of-Rib message
  • the second node needs to actively send a routing update message to the first node, and informs the first node to resend the routing information currently stored by the first node to the second node.
  • Embodiment 1 The method for synchronizing BGP routes after the inter-group handover process of a BGP peer.
  • the method for synchronizing the BGP routes is used after the inter-group handover process of the BGP peers, so that BGP routes are synchronized after the BGP peers switch between groups.
  • the topology structure shown in FIG. 1 is taken as an example to introduce the BGP route synchronization method after inter-group switching in this embodiment.
  • Peerl when Peerl is switched from GroupA to GroupB, the egress policy used by Peerl is changed from the egress policy of GroupA to the egress policy of GroupB. Therefore, Peerl needs to reroute with Peer2. Synchronize. In this embodiment, Peerl only needs to traverse RouteSetB to complete the route synchronization with the peer Peer2.
  • the method for synchronizing BGP routes after group switching in this embodiment includes the following steps:
  • Step 301 supporting Peerl and Peer2 of the on-demand aging capability, during the BGP negotiation establishment process Negotiation is completed for the on-demand aging capability.
  • Peerl completes the inter-group handover, and sends a start notification to Peer2 (for example, StartAgingRoute).
  • Step 303 Peer2 starts the on-demand aging process according to the start notification message.
  • the on-demand aging process is: adding aging identification information to all BGP routes sent by Peerl before receiving the start notification message, and starting a routing information timer. The route with the aging identification information continues to remain active.
  • Step 304 Peerl traverses RouteSetB and sends the route in RouteSetB to Peer2.
  • Peerl does not need to consider the impact of any egress policy, and does not need to consider the route sending status of GroupA. Instead, it directly sends the information about the added routes corresponding to all the routes in RouteSetB to Peer2. After the sending is complete, it sends to Peer2.
  • An end notification message (for example, EndAgingRoute message or End-Of-Rib message, etc.).
  • Step 305 Peer2 processes the route sent by Peerl.
  • the process is as follows: If the route with the aging identification information is received and the same route is received, the aging identification information of the route is removed and becomes a normal route; if there is no storage and received by Peer2 in Peer2 If the route with the same aging information is sent, Peer2 stores the route received by the packet.
  • Peer2 receives the end notification packet sent by Peerl (for example, EndAgingRoute packet or End-Of-Rib packet)
  • the timer of the Peer2 expires, the routes with the aging identification information are deleted, so that the BGP routes of the Peerl and Peer2 are synchronized.
  • Peer2 receives the end notification message sent by Peer1, it will close the above timer.
  • the end notification message may take a long time to be sent to Peer2. It may also be that Peerl does not send the end notification message for some reason, so Peer2 can also be used in the above.
  • the timer expires, delete the routes that still have the aging identification information to ensure that the BGP route synchronization can be completed in time.
  • the duration of the above timer can be adjusted to ensure that a complete copy can be received from the peer within the duration of the timer.
  • Peer2 performing the aging operation needs to send a route update message to Peerl, and notify Peerl to resend the current stored route of Peerl to Peer2.
  • steps 304 and 305 are performed simultaneously on Peerl and Peer2, respectively, and thus there is no order of execution.
  • Peerl and Peer2 can synchronize the BGP routes in the case that the BGP session is continuously re-established. Moreover, compared with the BGP route synchronization method after the inter-group handover in the prior art, the Peer1 does not need to traverse the set RouteSet of all the BGP routes on the RouterA in the method of the BGP route synchronization after the inter-group handover in the embodiment. You only need to traverse the set RouteSetB of the BGP route that meets the GroupB export policy. When a router has multiple peer groups, RouteSetB may be only a small subset of the RouteSet. Therefore, the BGP in this embodiment is used.
  • the routing synchronization method requires a large amount of traversal routing, which can greatly improve the traversal speed of Peerl.
  • Peerl does not have to consider which routes have been sent before the handover is completed, and only needs to send information of all routes in RouteSetB to The peer end can be used to process each route in RouteSetB one by one, so that the route differentiation process that needs to be completed by Peerl is converted into a simple route update and deletion process in Peer2, thereby greatly simplifying the processing process of Peerl. And do not need to lock the BGP peer to which the Peerl switch belongs.
  • Peer2 will not receive repeated information about adding routes, nor will it receive information about the revocation routes of routes that do not exist in Peer2, thus avoiding pinning. Success and other situations have emerged.
  • Embodiment 2 A method for synchronizing BGP routes in a TCP hot backup process.
  • the BGP route synchronization method may be used in the TCP hot backup process, so that the BGP route synchronization of each router after the active/standby switchover is quickly implemented in the application scenario of the TCP hot backup. And does not affect the data forwarding of BGP neighbors.
  • FIG. 4 is a topological structural diagram of BGP route synchronization in TCP hot backup according to an embodiment of the present invention.
  • the three routers RTA, RTB, and RTC that need to perform BGP route synchronization are supported.
  • an external BGP (EBGP) connection is established between the three routers as shown in Figure 4, where the RTA is connected to the network side and receives a certain amount from the network side.
  • the received routes are forwarded to the RTB, and then the RTB forwards the routes to the RTC.
  • the BGP route synchronization method after TCP hot backup is introduced by taking the BGP route synchronization with the RTC after the active/standby switchover of the RTB in the topology shown in FIG. .
  • FIG. 5 is a flowchart of a method for synchronizing BGP routes in TCP hot backup according to an embodiment of the present invention. As shown in FIG. 5, the BGP route synchronization method in TCP hot backup in the embodiment of the present invention includes the following steps:
  • Step 501 The RTB and the RTC that need to perform route synchronization support the on-demand aging capability, and the negotiation of the aging capability on the aging negotiation process is successful.
  • Step 502 The RTB completes the active/standby switchover, and sends a route update (Refresh) message to the RTA and the RTC to collect routes.
  • a route update Refresh
  • the received routing information is processed as follows: No need to back up the received routing information, but simply maintain the TCP session state unchanged, that is, when When the RTB receives the routing information, the RTB sends an acknowledgement message (ACK) to the peer that sends the routing information to confirm that the routing information has been received, but the RTB does not add the routing information included in the received routing information. And the information of the revocation route is processed, but the received routing information is directly discarded, and all of the discarded routing information can be recovered in the subsequent processing.
  • ACK acknowledgement message
  • the RTB can send the Refresh message to the RTA and the RTC respectively.
  • the RTA and the RTC send the latest route to the RTB according to the received Refresh message.
  • Step 503 After collecting the route, the RTB sends a start notification message to the RTC (for example, StartAgingRoute).
  • a start notification message for example, StartAgingRoute.
  • Step 504 The RTC starts the on-demand aging process according to the start notification message.
  • the on-demand aging process is: sending the start notification message to the RTB.
  • the BGP route adds the aging identification information and starts a timer. The route with the aging identification information continues to remain active.
  • Step 505 The RTB sends a valid route to the RTC.
  • the valid route refers to the effective route that the RTB processes according to the route collected from the RTA and the RTB in step 502 and finally determines. For example, when the active/standby switchover occurs on the RTB, if the route between the RTA and the network side changes, and the network side cancels a route in the route originally sent to the RTA, the RTA will receive the RTB. After the routing update message is sent, the information about the revoked route corresponding to the revoked route is sent to the RTB, and the RTB learns that the revoked route is no longer a valid route according to the information of the revoked route, so the RTB will not The route of this route is sent to the RTC.
  • the RTB After the RTB sends the valid route, it sends an end notification message to the RTC (for example, EndAgingRoute message or End-Of-Rib message, etc.).
  • an end notification message for example, EndAgingRoute message or End-Of-Rib message, etc.
  • Step 506 The RTC processes the valid route sent from the RTB.
  • the processing is: RTC compares the valid route sent by the RTB with the route with the aging identification information, if the received valid route sent by the RTB and an aging identifier are added to an RTC If the route of the information is the same, the aging identification information of the route with the aging identification information is removed and becomes a normal route. If the received route received by the RTB is not stored in the RTC, the aging identification information is added. The route, then the RTC stores the route received by the strip. When the RTC receives the end notification message (for example, the EndAgingRoute message or the End-Of-Rib message) sent by the RTB, or when the RTC timer expires, the route that still has the aging identification information is deleted.
  • the BGP routes of RTB and RTC are synchronized.
  • Peer2 receives the end notification message sent by Peer1, it will close the timer.
  • the end notification message may take a long time to be sent to the RTC, and the RTB may not send the end notification message for some reason, so the RTC may also be in the above.
  • the timer expires, delete the routes that still have the aging identification information to ensure that the BGP route synchronization can be completed in time.
  • the above can be adjusted
  • the duration of the timer is such that a complete route can be received from the peer within the timer duration.
  • the RTC that performs the aging operation needs to send a route update. 4 ⁇ The message is sent to the RTB, and the RTB is notified to resend the current stored route of the RTB to the RTC.
  • steps 505 and 506 are performed simultaneously on the RTB and the RTC, respectively, and thus there is no order of execution.
  • the BGP route synchronization method of the TCP hot backup can be used in the scenario of the TCP hot backup.
  • the BGP neighbor relationship is not required to be disconnected from the BGP neighbor relationship. That is, the router can synchronize the BGP routes with the BGP neighbors connected to it after the active/standby switchover. At the same time, the router that performs the active/standby switchover can continuously receive the routes sent by the BGP peers connected to it, so it does not affect the data forwarding of the BGP neighbors connected to it.
  • the router that performs the active/standby switch does not need to save the route that it has sent, but only needs to notify the peer end of the effective route after the active/standby switchover. The synchronization of the BGP routes on the peer end makes the operation process simpler and faster.
  • FIG. 6 is a schematic diagram of a BGP route synchronization system according to an embodiment of the present invention.
  • the BGP route synchronization system in the embodiment of the present invention includes: node A and node B;
  • the node A is connected to the node B, and sends the start notification message, the obtained routing information, and the end notification message to the node B;
  • the Node B adds aging identification information to all routing information sent by the node A before receiving the start notification message; receiving routing information, and receiving the routing information and having the aging identifier When the routing information of the information is the same, the aging identification information in the routing information with the aging identification information is removed; when the received routing information is different from the routing information having the aging identification information, the received routing information is stored; After receiving the end notification message, the packet deletes the routing information with the aging identification information.
  • the node A includes: an indication module 11, a collection module 12, and a sending module 13;
  • the indication module 11 is configured to output to the sending module and the collecting module when the routing synchronization starts a start instruction; outputting an end instruction to the sending module according to the output completion message sent by the collecting module; the collecting module 12, configured to receive routing information sent by a node connected to the device; and output to the sending module according to the start instruction The received routing information; after all routing information is output to the sending module, returning an output completion message to the indicating module;
  • the sending module 13 is configured to output a start notification message according to the start instruction, output routing information sent by the collection module, and output an end notification message according to the end instruction.
  • the node B includes: a receiving module 21 and a synchronization module 22;
  • the receiving module 21 is configured to output the received start notification message, routing information, and end notification message to the synchronization module.
  • the synchronization module 22 is configured to: when receiving the start notification message, add aging identification information to the routing information, where the routing information is routing information that has been received before receiving the start notification message, and the The routing information is sent by the node that sends the start notification message; when the received routing information is the same as the routing information with the aging identification information, the aging identification information in the routing information with the aging identification information is removed; When the routing information is different from the routing information with the aging identification information, the received routing information is stored. After receiving the ending notification message, the routing information with the aging identification information is deleted.
  • the Node B may further include: a timer module 23, a first sending module 24, and a second sending module 25.
  • the first sending module 24 is configured to send the start notification message received by the receiving module 21 to the timer module 23.
  • the timer module 23 includes a timer, and the timer is used to start timing according to the received start notification message; when the timer expires, the timer module 23 sends an update message to the synchronization module 22; The timing of the timer is stopped according to the stop message sent by the synchronization module 22.
  • the synchronization module 22 is configured to delete all the routing information with the aging identification information according to the received update message, and output an update instruction to the second sending module 25; according to the received end notification message, to the timer module 23 Send a stop message.
  • the second sending module 25 is configured to send a routing update message to the indication module in the first node according to the received update instruction.
  • the indication module in the node A outputs a start instruction to the sending module 13 and the collecting module 12 according to the received routing update message; and restarts the process of routing synchronization.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Abstract

L'invention concerne un procédé pour synchroniser des chemins de protocole 'border gateway protocol' (BGP). Ce procédé consiste : après réception d'un message de notification de démarrage, à ajouter des informations d'identification de dégradation aux informations d'acheminement qui ont été reçues avant réception du message de notification de démarrage, les informations d'acheminement étant envoyées par le noeud qui envoie le message de notification de démarrage; à recevoir des informations d'acheminement, lorsque les informations d'acheminement reçues sont identiques à celles qui comportent les informations d'identification de dégradation, à éliminer les informations d'identification de dégradation des informations d'acheminement comportant lesdites informations d'identification de dégradation; lorsque les informations d'acheminement reçues sont différentes des informations d'acheminement comportant les informations d'identification de dégradation, à stocker les informations d'acheminement reçues; après réception d'un message de notification de fin, à effacer les informations d'acheminement comportant les informations d'identification de dégradation. L'invention concerne également un système et un appareil pour synchroniser les chemins de protocole BGP. L'application desdits procédé, système et appareil permet une synchronisation de chemins entre des noeuds lorsqu'une session BGP entre des noeuds est ininterrompue.
PCT/CN2008/073723 2007-12-28 2008-12-25 Procédé, système et appareil pour synchroniser des chemins de protocole bgp WO2009089726A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200710306961 2007-12-28
CN200710306961.5 2007-12-28
CN200810126989.5 2008-06-20
CN2008101269895A CN101471940B (zh) 2007-12-28 2008-06-20 一种边界网关协议路由同步的方法、系统及装置

Publications (1)

Publication Number Publication Date
WO2009089726A1 true WO2009089726A1 (fr) 2009-07-23

Family

ID=40829065

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073723 WO2009089726A1 (fr) 2007-12-28 2008-12-25 Procédé, système et appareil pour synchroniser des chemins de protocole bgp

Country Status (2)

Country Link
CN (1) CN101471940B (fr)
WO (1) WO2009089726A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108123876A (zh) * 2017-12-14 2018-06-05 新华三技术有限公司 边界网关协议bgp路由信息处理方法及装置
WO2022218132A1 (fr) * 2021-04-15 2022-10-20 华为技术有限公司 Procédé, appareil et système de mise à jour d'itinéraire
CN116170367A (zh) * 2023-02-09 2023-05-26 浪潮思科网络科技有限公司 一种bgp链路路由收敛方法、装置、设备及介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014205832A1 (fr) * 2013-06-29 2014-12-31 华为技术有限公司 Procédé, passerelle frontière, et dispositif de plan de commande pour une émission de données
CN106712997B (zh) * 2015-11-16 2020-04-14 华为技术有限公司 表项恢复的方法、设备及系统
CN105763477B (zh) * 2016-02-03 2019-09-06 新华三技术有限公司 一种流量控制策略处理方法及装置
CN106411728B (zh) * 2016-09-29 2019-10-11 新华三技术有限公司 路由处理方法和装置
US10531412B2 (en) 2017-11-06 2020-01-07 Sony Corporation On demand route synchronization and beamforming in wireless networks
CN108390822B (zh) * 2018-03-13 2021-01-26 新华三技术有限公司 路由发布方法和装置
CN109905325B (zh) * 2019-03-13 2022-09-30 厦门网宿有限公司 一种流量引导方法及流量识别设备
CN110932970B (zh) * 2019-12-04 2022-03-18 锐捷网络股份有限公司 传输控制协议tcp会话的处理方法及装置
EP4333405A1 (fr) * 2021-10-28 2024-03-06 New H3C Technologies Co., Ltd. Procédé et appareil de synchronisation d'informations entre des commutateurs

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1536866A (zh) * 2003-04-11 2004-10-13 华为技术有限公司 一种ip电话路由的备份及恢复方法
CN1711729A (zh) * 2002-11-12 2005-12-21 思科技术公司 用于同步的路由系统与方法
WO2006081138A1 (fr) * 2005-01-27 2006-08-03 Cisco Technology, Inc. Procede et appareil permettant d'effectuer des mises a jour d'indicatifs centrees sur le contexte dans un protocole bgp
US20070086461A1 (en) * 2005-10-17 2007-04-19 Ward David D Method for recovery of a controlled failover of a border gateway protocol speaker

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1711729A (zh) * 2002-11-12 2005-12-21 思科技术公司 用于同步的路由系统与方法
CN1536866A (zh) * 2003-04-11 2004-10-13 华为技术有限公司 一种ip电话路由的备份及恢复方法
WO2006081138A1 (fr) * 2005-01-27 2006-08-03 Cisco Technology, Inc. Procede et appareil permettant d'effectuer des mises a jour d'indicatifs centrees sur le contexte dans un protocole bgp
US20070086461A1 (en) * 2005-10-17 2007-04-19 Ward David D Method for recovery of a controlled failover of a border gateway protocol speaker

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108123876A (zh) * 2017-12-14 2018-06-05 新华三技术有限公司 边界网关协议bgp路由信息处理方法及装置
WO2022218132A1 (fr) * 2021-04-15 2022-10-20 华为技术有限公司 Procédé, appareil et système de mise à jour d'itinéraire
CN116170367A (zh) * 2023-02-09 2023-05-26 浪潮思科网络科技有限公司 一种bgp链路路由收敛方法、装置、设备及介质
CN116170367B (zh) * 2023-02-09 2024-04-16 浪潮思科网络科技有限公司 一种bgp链路路由收敛方法、装置、设备及介质

Also Published As

Publication number Publication date
CN101471940B (zh) 2012-09-05
CN101471940A (zh) 2009-07-01

Similar Documents

Publication Publication Date Title
WO2009089726A1 (fr) Procédé, système et appareil pour synchroniser des chemins de protocole bgp
WO2009067865A2 (fr) Procédé, routeur, carte de ligne et carte maîtresse active permettant d'effectuer la synchronisation d'une base de données d'états de liaison
KR101260233B1 (ko) 소프트라우터 프로토콜 장애 극복들
US9634846B2 (en) Running link state routing protocol in CLOS networks
EP2222023B1 (fr) Procédé de traitement de défaut de liaison et dispositif de transfert de données
JP4755786B2 (ja) トポロジ状態ルーティングプロトコルを有する通信ネットワークにおけるトポロジデータベースの再同期化のための方法および装置
WO2008031334A1 (fr) Procédé et système de mise à jour de chemin, et routage
TW201134151A (en) RSVP-TE graceful restart under fast re-route conditions
JP2006135970A (ja) ＳｏｆｔＲｏｕｔｅｒ動的バインディング・プロトコル
WO2007062559A1 (fr) Procede et passerelle de restitution de service au moment de la permutation entre passerelles pilote et asservie
WO2008141567A1 (fr) Procédé de commutation de flux d'un réseau de commutation multiprotocole par étiquette et équipement
JP2014519737A (ja) アクティブｔｃｐアプリケーションからスタンバイｔｃｐアプリケーションへのヒットレススイッチオーバ
EP2773070A1 (fr) Procédé et appareil de gestion de multicast (multidiffusion)
WO2007036103A1 (fr) Procede de reparation de trajet de reacheminement de service et systeme associe
WO2008014696A1 (fr) Méthode et dispositif pour effectuer un transfert de communications
WO2014090083A1 (fr) Procédé et appareil de support de services pendant l'interconnexion de réseau résiliente distribuée
JP2012529805A (ja) 二台のコンピュータによるホットスタンバイの方法、機器およびシステム
WO2012062069A1 (fr) Procédé et dispositif pour envoyer un message de détection de réacheminement bidirectionnel
US8238309B1 (en) Stateful home agent recovery protocol (SHARP)
EP2571211A2 (fr) Routage ininterrompu OSPF avec synchronisation voisine retardée
WO2014101125A1 (fr) Procédé, dispositif et système de négociation de liaison d'un groupe d'agrégation
EP2575304B1 (fr) Réduction de synchronisation du routage ininterrompu OSPF
EP2575306B1 (fr) Synchronisation sans acquittement du routage ininterrompu ospf
WO2012088909A1 (fr) Procédé et dispositif de mise à jour de routage vpn
WO2009155799A1 (fr) Procédé de récupération d’informations sur la base d’un redémarrage en douceur et routeur associé

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08870749

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08870749

Country of ref document: EP

Kind code of ref document: A1