WO2014176975A1 - Drni中同一端内系统之间交互信息的方法和系统 - Google Patents
Drni中同一端内系统之间交互信息的方法和系统 Download PDFInfo
- Publication number
- WO2014176975A1 WO2014176975A1 PCT/CN2014/075462 CN2014075462W WO2014176975A1 WO 2014176975 A1 WO2014176975 A1 WO 2014176975A1 CN 2014075462 W CN2014075462 W CN 2014075462W WO 2014176975 A1 WO2014176975 A1 WO 2014176975A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- neighboring
- key value
- session
- operation key
- state machine
- Prior art date
Links
Classifications
-
- 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/12—Discovery or management of network topologies
-
- 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/24—Multipath
- H04L45/245—Link aggregation, e.g. trunking
-
- 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
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/41—Flow control; Congestion control by acting on aggregated flows or links
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/14—Multichannel or multilink protocols
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Definitions
- the present invention relates to a network communication protection technology, and more particularly to a method and system for interacting information between systems in the same end in a DRNK Distributed Resilient Network Interconnected (Distributed Resilient Network Interconnected).
- the protection can be implemented by using port aggregation.
- the common method can be port aggregation or loop protection.
- link aggregation currently supports port aggregation on a node, so it can only be used for link protection. Nodes on the network edge interface are protected.
- the link aggregation group DRNI is used to implement the dual-redundant network interconnection protection requirement of the link and the node, that is, the endpoint of the aggregation group is composed of multiple nodes, and the aggregation links of the multiple nodes form a link aggregation group ( Link Aggregation Group, LAG for short.
- the two endpoints (Ports) A and B of the link aggregation group are composed of two and three systems: Endpoint A contains System 1 and System 2, and Endpoint B contains System 3, System 4 and System 5, the multiple links of the five systems are aggregated together to form a distributed LAG. Through this distributed LAG, double protection of links and nodes can be achieved.
- DRNI interconnects more than two systems through Distributed Relay (DR), where each system runs link aggregation to form a Portal.
- DR Distributed Relay
- the peer system For the peer system connected to the Portal, the peer system considers itself to be an analog system.
- each system in a portal needs to negotiate with each other through distributed relays to achieve uniformity of parameters between the systems, and advertise the LACP protocol to interact with the other end of the link aggregation group.
- the function of the DR is to send the packet (UP packet) received from the aggregation interface to the gateway or discard it, and send the packet (DOWN packet) received from the gateway interface to the aggregator or discard it.
- the DR determines whether to forward the packet or discard the packet according to the session to which the received packet belongs.
- the configuration of the gateway algorithm and the port algorithm is also performed according to the session.
- Each session traffic is assigned a maximum of one gateway link, and each session traffic also corresponds to at most one aggregate interface.
- the present invention provides a method for exchanging information between systems in the same end of a distributed elastic network interconnection, which is applied to each of the end points of the link aggregation group, including: sending distribution through the internal link interface a relay control protocol (DRCP) protocol message, at least carrying system information of the system;
- DRCP relay control protocol
- the operation key value of the system is determined.
- the method further includes: After determining the operating key value of the system, a distributed relay channel is established in the system.
- the method further includes: after determining an operation key value of the system, negotiating a unified session distribution manner with the neighboring system.
- the determining that the system and the neighboring system can form the same endpoint includes: matching system information of the neighboring system carried in the received DRCP protocol packet with system information of the system If the matching check passes, it is determined that the system and the adjacent system can form the same endpoint.
- the matching check is performed on the system information of the neighboring system carried in the received DRCP protocol packet and the system information of the system, including:
- the matching check includes: the system is the same as the endpoint identifier of the neighboring system, and/or the system is the same as the virtual system identifier of the neighboring system.
- the performing the matching check on the system information of the neighboring system carried in the received DRCP protocol packet and the system information of the system further includes:
- the matching check includes: the system is the same as the endpoint identifier and/or the virtual system identifier of the neighboring system, and the system does not conflict with the system number of the neighboring system.
- the method further includes: if the matching check is passed, saving system information of the neighboring system carried in the DRCP protocol packet.
- the sending the DRCP protocol text includes:
- the method further includes:
- a timer is started; if the DRCP protocol packet sent by the neighboring system is not received when the timer expires, Or if the DRCP protocol packet sent by the neighboring system is received before the timer expires, but the matching check fails, it is determined that the system and the neighboring system cannot form an endpoint of the distributed elastic network interconnection. .
- the sending the DRCP protocol text includes:
- the DRCP protocol text is sent.
- the determining the operation key value of the system includes:
- the operation key value of the system is the same as the operation key value of the adjacent system, the operation key value of the system is maintained unchanged.
- the determining the operation key value of the system includes:
- the operation key value of the system is different from the operation key value of the adjacent system, the operation key value of the system is modified according to the policy, or the operation key value of the system is maintained.
- the determining the operation key value of the system includes:
- the operation key value of the system is calculated.
- the method further includes:
- the operation key value of the system is sent to the opposite end of the distributed elastic network interconnection through the Link Aggregation Control Protocol (LACP) message.
- LACP Link Aggregation Control Protocol
- the method for negotiating a unified session with the neighboring system includes: negotiating a session splitting manner carried in the DRCP protocol packet sent by the neighboring system with a session distribution manner of the system, Configure the distributed distribution traffic distribution mode in the system according to the negotiated session distribution mode;
- the session distribution mode includes any one or any combination of the following two parameters: gateway system selection and aggregator/aggregation port selection.
- the session division method carried in the DRCP protocol packet sent by the neighboring system is negotiated with the session distribution mode of the system, and the method includes: sending the DRCP protocol packet sent by the neighboring system
- the session distribution mode carried in the session is compared with the session distribution mode of the system.
- the distributed relay is distributed in a consistent manner.
- the distribution of the session traffic is performed.
- the establishing a distributed relay channel in the system includes:
- the distributed relay is configured for session distribution on the gateway and the aggregator/aggregation port. After the configuration, the distributed relay forwards session traffic between the gateway and the aggregator/aggregation port on the system.
- the method further includes: closing a data traffic forwarding function of the inner link link with the neighboring system;
- the distribution algorithm is unified, and the data traffic forwarding function of the inner chain link is started.
- the method further includes:
- the system and the neighboring system can no longer form an endpoint of the distributed elastic network interconnection, determine whether the system information of the system needs to be modified according to the policy; if it needs to be modified, at least part of the LACP of the system information of the system The parameters are modified, and the LACP parameters of the modified LACP system are at least not the same as the LACP parameters of the adjacent system.
- the modifying at least part of the LACP parameters in the system information of the system includes: modifying an operation key value and/or a system identifier of the system, or restoring the operation key value to a management key value.
- the distributed relay is restored to the configuration of the pre-negotiation session distribution mode.
- the DRCP protocol packet sent by the internal link interface further carries system information and/or a session distribution manner of other adjacent systems connected to the system.
- the present invention also provides a system for implementing distributed relay control in a distributed elastic network interconnection, including:
- the sending state machine is set to: send a distributed relay control protocol (DRCP) protocol text when other state machines of the system indicate that they need to send or need to send periodically;
- DRCP distributed relay control protocol
- the receiving state machine is set to: receive a DRCP protocol packet sent by the neighboring system, Performing a matching check on the system information of the adjacent system, and recording the result after the matching check is passed
- the information in the DRCP protocol message is started by the timer to determine whether the DRCP protocol sent by the neighboring system is received periodically;
- the negotiation state machine is set to: determine the operation key value of the system, and ensure that the operation key value of the adjacent system is consistent;
- the synchronization state machine is set to: establish a forwarding channel between the aggregator/aggregation port and the gateway, negotiate a unified session distribution manner with the neighboring system as needed, and configure a session distribution mode of the distributed relay; the periodic transmission state machine is set to : Determining that the sending state machine periodically sends a DRCP protocol message.
- the receiving state machine is configured to perform a matching check on the system information of the system and the adjacent system, including:
- the receiving state machine determines whether the endpoint identifier of the system is consistent with the endpoint identifier of the neighboring system; and/or determines whether the virtual system identifier of the system is consistent with the virtual system identifier of the neighboring system;
- the matching check includes: the system is the same as the endpoint identifier of the neighboring system, and/or the system is the same as the virtual system identifier of the neighboring system.
- the receiving state machine is configured to perform a matching check on system information of the system and the adjacent system, and further includes:
- the receiving state machine determines whether a system number of the system conflicts with a system number of the neighboring system
- the matching check includes: the system identifier is the same as the endpoint identifier and/or the virtual system identifier of the neighboring system, and the system number of the neighboring system is legal, or the system number of the system and the neighboring system is Do not conflict.
- the negotiation state machine is configured to: determine an operation key value of the system, and ensure that the operation key value of the adjacent system is consistent, including:
- the negotiation state machine determines the operation key value of the system and the operation of the adjacent system
- the negotiation state machine is configured to: determine an operation key value of the system, and ensure that the operation key value of the neighboring system is consistent, and the method includes: the negotiation state machine according to the management key value of the system and the received location The management key value of the adjacent system is calculated, and the operation key value of the system is calculated.
- the negotiation state machine is further configured to: after determining the operation key value of the system, send the operation key value of the system to the distributed elastic network interconnection pair through a Link Aggregation Control Protocol (LACP) message. end.
- LACP Link Aggregation Control Protocol
- the synchronization state machine is configured to: the session distribution manner that is negotiated with the neighboring system, and the method includes: a session division method and a method carried in the DRCP protocol packet sent by the neighboring system
- the session distribution mode of the system is negotiated, and the distributed distribution of traffic in the system is configured according to the negotiated session distribution mode.
- the synchronization state machine is configured to: negotiate a session division manner carried in the DRCP protocol packet sent by the neighboring system with a session distribution manner of the system, where: the synchronization state machine will The session distribution mode carried in the DRCP protocol packet sent by the adjacency system is compared with the session distribution mode of the system. For the session in which the session distribution mode is consistent, the session traffic is performed in a consistent session distribution manner. Distributing, for distribution in a session, preferably, the session distribution mode includes any one or any combination of the following two parameters: gateway system selection and aggregator/aggregation port selection.
- the synchronization state machine is further configured to: before negotiating the unified session distribution mode with the neighboring system, shutting down the data traffic forwarding function of the inner link link with the adjacent system; when unified with the adjacency system After the session is distributed, the negotiation is complete.
- the distribution algorithm is unified.
- the data forwarding function of the internal link is enabled.
- the receiving state machine is further configured to: if the DRCP protocol message sent by the neighboring system is not received, or the received DRCP protocol message sent by the neighboring system fails to pass the matching check.
- it is determined whether the system information of the system needs to be modified; if it needs to be modified, at least part of the LACP parameters of the system information of the system are modified, wherein the LACP parameters of the system and the LACP parameters of the adjacent system are modified. At least not exactly the same.
- the receiving state machine is set to: at least part of system information of the system
- the LACP parameter is modified, including: the receiving state machine modifies the operation key value and/or the system identifier of the system, or restores the operation key value to the management key value.
- the synchronization state machine is further configured to: restore the distributed relay to a pre-negotiation session when an internal link between the adjacent system fails or the inner link is unavailable Configuration of the distribution method.
- the DRCP protocol sent by the sending state machine through the inner chain interface further carries system information and/or a session distribution manner of other adjacent systems connected to the system.
- control communication between multiple systems in one end of the distributed link aggregation group is implemented, and the multiple systems can be effectively aggregated into one aggregation group to implement protection on the interconnection interface. It is protection on the link and implements node level protection.
- FIG. 1 is a schematic diagram of a network interconnection node connection in the related art
- FIG. 2 is a schematic diagram of a process flow of a distributed relay control protocol state event according to an embodiment of the present invention
- FIG. 3 is a schematic diagram of parameter transmission of a distributed relay control protocol according to an embodiment of the present invention
- FIG. 4 is a schematic diagram of a processing flow of a receiving state machine in an embodiment of the present invention.
- Figure 5 is a flow chart of the Check function in the embodiment of the present invention.
- FIG. 6 is a schematic diagram of a processing flow of a negotiation state machine in an embodiment of the present invention.
- FIG. 7 is a schematic diagram of a processing flow of a synchronization state machine in an embodiment of the present invention.
- FIG. 8 is a schematic diagram of another processing flow of a synchronous state machine in an embodiment of the present invention.
- Figure 9 is a flow chart of the NeedtoCoordination function in the embodiment of the present invention. Preferred embodiment of the invention
- the distributed relay control protocol (DRCP) in the system mainly includes: a receiving state machine, a synchronization state machine, and a sending state machine, and may further include: a negotiation state machine and a periodic sending state. machine.
- DRCP distributed relay control protocol
- the receiving state machine is mainly used to receive DRCP protocol packets sent by the neighboring system.
- the received DRCP protocol packet includes system information (Actor_Info) of the neighboring system that sends the packet, and may also include a system of other systems connected to the neighboring system saved by the neighboring system that sends the packet.
- Information Partner_Info.
- the main tasks of the receiving state machine are:
- a timer is started every time a DRCP protocol packet is sent from the neighboring system. If the timer expires (Expire), the DRCP protocol packet sent by the neighboring system is not received. The adjacent system loses contact and enters the lost contact state;
- the Actor-Info carried in the received DRCP protocol message is saved, if the DRCP protocol message carries the Partner- Info is also saved.
- the following steps are used to determine whether the system and the adjacent system can form an endpoint of the distributed elastic network interconnection, including:
- Step 1 Compare whether the Portal ID carried in the received DRCP protocol is the same as the Portal ID of the endpoint to which the system belongs. If the two are consistent, the two parties are indeed in the same endpoint. If the packets are inconsistent, the DRCP protocol packet is discarded.
- Step 2 Compare whether the virtual system ID (Emulated System ID) carried in the DRCP protocol is consistent with the value of the Emulated System ID of the system. If the two are consistent, go to Step 3. If the two are inconsistent, discard the The value of the System ID field carried in the message is the value of the Emulated System ID of the system when the system sends the LACP packet.
- virtual system ID Emulated System ID
- Step 3 Check whether the System Number of the system that sends the DRCP protocol packet in the DRCP protocol conflicts with the System Number of the system, that is, whether the two are the same. If the two are different, it means that the two systems already have the condition of being aggregated into one DRNI interface, that is, the two systems can form a logical system, that is, the portal.
- the system number of the system is legal and does not conflict with the system number of the system, it indicates that the matching check is passed.
- step c) If the DRCP protocol packet sent by another system that has been aggregated with the system is not received before the timer expires, or the DRCP protocol packet received before the timer expires does not pass the match in step c) Sex check (that is, it does not receive the qualified DRCP protocol message sent by the other system), indicating that the system and the other system have lost contact, and the two systems cannot be re-aggregated. Take the relevant actions to de-aggregate and separate the two systems.
- the synchronous state machine is mainly used to establish DR channels, perform data forwarding on the DRNI interface, and distribute traffic between systems. mainly includes:
- the two systems need to negotiate a unified session distribution mode to determine which packets of the specific session are from the system.
- the link on the DRNI interface is forwarded.
- the data distribution process here may need to be implemented by the internal chain link to participate in data forwarding.
- the DR channel can distribute traffic on different systems
- data traffic may need to be transmitted on the internal link.
- the inbound link of the port on the inner link should be opened to transmit data traffic. Enables data traffic to be forwarded through the inner link in systems within the same portal.
- the inbound and outbound traffic on the ports on the inner link is configured to ensure that different session traffic can go to a specific system and a specific aggregation port. Since then, the DR channel on each system will distribute traffic according to the negotiated session distribution method.
- DRCP.state Synchronization
- IPL Intra-Portal Link
- the distribution mode that is, the data packets received by the system are also forwarded from the system, and are not distributed through the internal link.
- the sending state machine is configured to send a DRCP protocol message through the internal link interface, where the DRCP protocol message may be triggered by a command sent by another state machine, or may be triggered by a periodic sending state machine.
- the DRCP protocol message may be triggered by a command sent by another state machine, or may be triggered by a periodic sending state machine.
- the periodic transmit state machine is used to determine when the system sends DRCP protocol messages to convey relevant information and maintain connectivity with other systems.
- the periodic transmission state machine has a timer inside. Whenever the timer expires, an NTT (Need to transmit) is generated, and the sending state machine is triggered to send the DRCP protocol message.
- NTT Need to transmit
- the distributed relay control protocol needs to transfer some information in these state machines during the state switching. As shown in Figure 3, it includes: 1.
- the receiving state machine receives the system information sent by the other party system through the DRCP protocol message and saves it as its own Partner information;
- the operation key (Actor_OperKey) value of the system and the operation key (Partner_OperKey) value of the system that sends the DRCP protocol message are judged and processed in the negotiation state machine. If the Actor-OperKey and Partner-OperKey are inconsistent, it is necessary to determine whether to tamper with the Actor of the system-OperKey according to the policy, and then trigger the sending state machine to send the Actor_OperKey and Partner-OperKey to the other system. Only if the operation key values of the two systems are consistent, can the two systems be further aggregated into one aggregation group;
- the synchronization state machine may need to negotiate a unified session distribution method. If required, after receiving the DRCP protocol packet, the receiving state machine selects the parameters of the session distribution mode of the adjacent system carried in, that is, the gateway system selects (Actor_GW & Partner-GW, which gateway should be used for a certain session traffic) The link and the aggregator system selection ( Actor — Agg & Partner — Agg, which aggregation port/aggregator a session traffic should go to) are judged and processed. In the synchronous state machine, the last negotiated session distribution mode is used to determine and configure the session distribution mode in the system, and the ports of the internal link are configured accordingly, and the session is forwarded according to the configured session distribution mode.
- System 1 considers itself to be an Actor and considers System 2 to be a Partner.
- System 2 considers itself to be an Actor and considers System 1 to be a Partner.
- System 1 receives the Actor information sent from System 2 and saves the Actor information as its own Partner information.
- the timeout flag Expire is set to False, indicating that there is no timeout yet;
- the record initial value function RecordDefault ( ) is used to set some LACP system parameters of system 1 to the LACP system parameters considered by system 1 as system 2, namely:
- the setting needs to send the identifier NTT to False, ie:
- DRCP.state Uncontact, indicating that the two parties are not currently connected, that is:
- the processing state is entered.
- DRCP DU Digital Unit
- the received protocol message RecordPDU ( ) is recorded, and the Actor information in the DRCPDU sent by the system 2 is recorded as the Partner information of the system 1.
- the function of Check ( Actor, Partner ) is mainly to check the matching of multiple parameters, as shown in Figure 5, including:
- the system ID of the logical system is the consistent Emulated System ID of the two systems.
- step 502 If the two parameters of system 1 and system 2 are consistent after the comparison in step 1), continue to compare whether the System Number parameters of system 1 and system 2 conflict.
- the system 1 If the DRCP DU sent by the system 2 is not received again when the timer expires, or if the matching check fails in the Check function, the system 1 considers that the Split Brain error has occurred and enters the abnormality. status. In the abnormal state, the two systems can no longer be aggregated into one logical node, and the distributed relay control protocol status needs to be set to Uncontact again, namely:
- System 1 can modify its own Operational Key to the Administration Key set before negotiation, or modify its own System ID to the system ID of the system instead of the Emulated System. ID.
- the foregoing policy may be that the system 1 and the system 2 are respectively modified, or the system 1 remains unchanged, the system 2 is modified, and vice versa, thereby ensuring that the system 1 and the system 2 have the system parameters of the LACP. The differences are at least not identical.
- the distributed relay control protocol If the distributed relay control protocol is found to be disabled DRCP_Disabled after initialization, it enters an unavailable state. Set the status of the distributed relay control protocol to Uncontact, namely:
- the Operational Key values of System 1 and System 2 may be different, and they are each equal to the Administration Key of the two systems, so if the system 1 is compared The Operational Key and the Operational Key of System 2 have different values.
- the relevant policy for example, according to the System Priority parameter, if the System Priority of System 2 is higher than the System Priority of System 1.
- System 1 will modify its Operational Key to the Operational Key of System 2; when the policy is modified according to the management key value, System 1 can follow the management key of the system and the received Management Key value of System 2, according to A certain algorithm calculates the corresponding Operational Key, and takes the value as the Operational Key of the system.
- the algorithm can be set according to the specific situation, as long as the interactive dual-issue (in this embodiment, System 1 and System 2) is guaranteed. The selected algorithm is the same.
- ModifyKey :
- ModifyKey Actor. OperKey, Partner. OperKey .
- the triggering sending state machine sends the modified Operational Key to System 2 to notify System 2.
- the LACP is started, and the LACP protocol packet is sent to the other end of the DRNI, and the parameters carried in the LACP protocol are parameters negotiated and determined by the DRCP protocol, including:
- the processing flow of the synchronization state machine in System 1, as shown in Figure 7, includes:
- trigger NTT Tme to notify system 2 that the DR of this system has not been established yet.
- DR established.
- DRCP. State is set to Synchronization, that is, the synchronization state machine detects DRCP.
- State Synchronization
- system 1 has completed aggregation with endpoint B through LACP.
- the configuration principle here is that the packets received by the system are forwarded in the system, that is, the data is not distributed through the internal link.
- the determination method is related to the specific implementation of the device:
- the DR can already be used for data forwarding.
- DRNI is already working.
- This function establishes the connection between the forwarding and aggregation group interfaces, thus ensuring that the DRNI interface can receive and send data packets.
- the NTT transmission can be triggered to notify the system 2.
- a distributed link aggregation group is established, and data traffic can be normal.
- DRNI technology can better meet the requirements of load balancing and protection.
- the DRCP control protocol may further need to further enhance the distribution of data traffic, that is, in system 1 and system. 2 to forward traffic between the two, which requires IPL to transmit data packets, but this requires System 1 and System 2 to agree on the choice of gateway and aggregator for the data flow, otherwise there will be confusion, even loop network storms, etc. Serious Problem.
- System 1 then begins with System 2 in DR for negotiation of traffic distribution:
- the traffic distribution of the DR is configured according to the previous negotiation result.
- the data traffic here is allocated by the session ID of the traffic.
- the current gateway selection is system 1
- IPL.Converstation[200] Discard).
- the data stream can be forwarded between System 1 and System 2 according to the configuration.
- the synchronization state machine in system 1 can also be processed as follows, as shown in Figure 8:
- trigger NTT Tme to notify system 2 that the DR of this system has not been established yet.
- the IPL data forwarding function is turned off, that is, the data cannot be diverted between the system 1 and the system 2 through the IPL:
- the configuration principle here is that the packet received by the system is forwarded in the system, that is,
- the DR can already be used for data forwarding.
- DRNI is already working.
- the traffic distribution to the DR is configured according to the previous negotiation result, namely:
- the data traffic here is assigned by the session ID of the traffic.
- the distribution manner of the DR on the system 1 is modified as shown in Table 1 above.
- the current gateway selection is system 1
- IPL.Converstation[200] Discard).
- the DR can formally distribute the traffic according to the previously distributed distribution configuration method.
- the control protocol can be in the forwarding state, and the DR distributes the traffic according to the distribution mode after the system 1 and the system 2 negotiate.
- the NeedtoCoordination ( ) function is used to unify the distribution of traffic between System 1 and System 2.
- DRNI has data traffic in two directions, one is data traffic sent from other network ports to the aggregation port, and the other is data traffic sent to the other network ports received by the aggregation port.
- the traffic in the first direction needs to be selected from the aggregator of system 1 to the aggregation port or from the aggregator of system 2 to the aggregation port.
- the traffic distribution at this time is determined by Actor_Info.Agg.
- the traffic in the second direction needs to be selected from the system 1 to other network ports, or sent to the system 2 via the inner link, and then sent to other network ports.
- the traffic is distributed by Actor_Info. GW to decide.
- the NeedtoCoordination ( ) function fc is used for Actor - Info.Agg and Partner - Info.Agg, and Actor - Info.GW and Partner - Info.GW to prevent conflicts.
- ⁇ 1 is processed as follows:
- the established strategies here include, but are not limited to, the following two types:
- System 1 fully accepts the information selected by the system 2 in the gateway selection and aggregator, that is, after interactive modification, System 1 and System 2 are completely identical in gateway selection and aggregator selection;
- System 1 and System 2 only select the parts they are consistent with, and only distribute the agreed session traffic, and discard the session traffic that has conflicts in gateway selection and aggregator selection. It is also possible to report alarms on conflicting session traffic and make adjustments by higher layer protocols or network administrators. Once the original conflicting session traffic is adjusted to be consistent, the distribution of these session traffic can be resumed.
- the embodiment of the present invention implements control communication between multiple systems at one end in a distributed link aggregation group, and can effectively implement protection on an interconnection interface after a plurality of systems are aggregated into one aggregation group, not only Protection on the link and node level protection.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
- Communication Control (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14791616.7A EP2981026B1 (en) | 2013-04-28 | 2014-04-16 | Method and system for information interaction among systems in the same portal in drni |
US14/787,596 US9749186B2 (en) | 2013-04-28 | 2014-04-16 | Method and system for information interaction among systems in the same end in DRNI |
JP2016510922A JP6105155B2 (ja) | 2013-04-28 | 2014-04-16 | Drniにおける同一端内システムの間で情報を交換する方法及びシステム |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310155668.9 | 2013-04-28 | ||
CN201310155668.9A CN104125088B (zh) | 2013-04-28 | 2013-04-28 | Drni中同一端内系统之间交互信息的方法和系统 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014176975A1 true WO2014176975A1 (zh) | 2014-11-06 |
Family
ID=51770360
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/075462 WO2014176975A1 (zh) | 2013-04-28 | 2014-04-16 | Drni中同一端内系统之间交互信息的方法和系统 |
Country Status (5)
Country | Link |
---|---|
US (1) | US9749186B2 (zh) |
EP (1) | EP2981026B1 (zh) |
JP (1) | JP6105155B2 (zh) |
CN (1) | CN104125088B (zh) |
WO (1) | WO2014176975A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114172690A (zh) * | 2021-11-11 | 2022-03-11 | 新华三大数据技术有限公司 | 一种终端认证方法及装置 |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9497074B2 (en) | 2013-04-23 | 2016-11-15 | Telefonaktiebolaget L M Ericsson (Publ) | Packet data unit (PDU) structure for supporting distributed relay control protocol (DRCP) |
US9497132B2 (en) | 2013-04-23 | 2016-11-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system of implementing conversation-sensitive collection for a link aggregation group |
CN104243259B (zh) * | 2013-06-20 | 2019-07-30 | 中兴通讯股份有限公司 | 分布式弹性网络互连系统中协作方法和系统 |
CN106878164B (zh) * | 2016-12-13 | 2020-04-03 | 新华三技术有限公司 | 一种报文传输方法和装置 |
CN107547398B (zh) * | 2017-05-23 | 2020-04-17 | 新华三技术有限公司 | 报文转发方法、装置和设备 |
CN108259348B (zh) * | 2017-05-24 | 2020-05-12 | 新华三技术有限公司 | 一种报文传输方法和装置 |
CN107249047B (zh) * | 2017-06-09 | 2020-11-17 | 区动(上海)网络科技有限公司 | 基于网络协议的数据传送方法、装置及计算机处理设备 |
US11039488B2 (en) | 2018-04-05 | 2021-06-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Adaptation layer setup and configuration in integrated access backhauled networks |
CN108737189B (zh) * | 2018-05-25 | 2021-11-05 | 新华三技术有限公司 | Dr设备角色更新方法及装置 |
CN109194521B (zh) * | 2018-09-29 | 2021-12-07 | 新华三技术有限公司 | 一种流量转发方法及设备 |
CN110708275B (zh) | 2018-12-18 | 2020-11-06 | 新华三技术有限公司 | 一种协议报文的处理方法和装置 |
CN113746763B (zh) * | 2020-05-29 | 2022-11-11 | 华为技术有限公司 | 一种数据处理的方法、装置和设备 |
CN111835560B (zh) * | 2020-06-29 | 2024-02-09 | 新华三信息安全技术有限公司 | 一种分布式弹性网络互连系统及其部署方法 |
CN112929417B (zh) * | 2021-01-22 | 2022-05-27 | 新华三信息安全技术有限公司 | 报文处理方法及装置 |
CN115333974B (zh) * | 2022-08-10 | 2023-08-11 | 杭州云合智网技术有限公司 | Drni网络中基于vsi的环路检测方法及装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102014019A (zh) * | 2010-11-04 | 2011-04-13 | 中兴通讯股份有限公司 | 聚合链路切换方法及装置 |
CN102316039A (zh) * | 2011-09-09 | 2012-01-11 | 中兴通讯股份有限公司 | 基于聚合体优先级策略的聚合体逻辑选择的方法及系统 |
CN102752187A (zh) * | 2011-04-21 | 2012-10-24 | 中兴通讯股份有限公司 | 弹性网络接口的实现方法和系统 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6910149B2 (en) * | 2001-09-24 | 2005-06-21 | Intel Corporation | Multi-device link aggregation |
CN101252459B (zh) * | 2008-03-24 | 2010-12-08 | 中兴通讯股份有限公司 | 一种设置链路端口的协议状态的方法及其监控方法 |
US8213296B2 (en) * | 2009-05-14 | 2012-07-03 | Verizon Patent And Licensing Inc. | Link aggregation protection |
US8913489B2 (en) * | 2010-08-04 | 2014-12-16 | Alcatel Lucent | System and method for virtual fabric link failure recovery |
EP2850787B1 (en) * | 2012-05-15 | 2019-02-13 | Telefonaktiebolaget LM Ericsson (publ) | Methods and apparatus for detecting and handling split brain issues in a link aggregation group |
US9497074B2 (en) * | 2013-04-23 | 2016-11-15 | Telefonaktiebolaget L M Ericsson (Publ) | Packet data unit (PDU) structure for supporting distributed relay control protocol (DRCP) |
-
2013
- 2013-04-28 CN CN201310155668.9A patent/CN104125088B/zh active Active
-
2014
- 2014-04-16 EP EP14791616.7A patent/EP2981026B1/en active Active
- 2014-04-16 US US14/787,596 patent/US9749186B2/en active Active
- 2014-04-16 JP JP2016510922A patent/JP6105155B2/ja active Active
- 2014-04-16 WO PCT/CN2014/075462 patent/WO2014176975A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102014019A (zh) * | 2010-11-04 | 2011-04-13 | 中兴通讯股份有限公司 | 聚合链路切换方法及装置 |
CN102752187A (zh) * | 2011-04-21 | 2012-10-24 | 中兴通讯股份有限公司 | 弹性网络接口的实现方法和系统 |
CN102316039A (zh) * | 2011-09-09 | 2012-01-11 | 中兴通讯股份有限公司 | 基于聚合体优先级策略的聚合体逻辑选择的方法及系统 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114172690A (zh) * | 2021-11-11 | 2022-03-11 | 新华三大数据技术有限公司 | 一种终端认证方法及装置 |
CN114172690B (zh) * | 2021-11-11 | 2023-12-26 | 新华三大数据技术有限公司 | 一种终端认证方法及装置 |
Also Published As
Publication number | Publication date |
---|---|
CN104125088B (zh) | 2019-05-10 |
CN104125088A (zh) | 2014-10-29 |
US20160105324A1 (en) | 2016-04-14 |
JP2016517252A (ja) | 2016-06-09 |
EP2981026A1 (en) | 2016-02-03 |
US9749186B2 (en) | 2017-08-29 |
EP2981026B1 (en) | 2019-11-27 |
JP6105155B2 (ja) | 2017-03-29 |
EP2981026A4 (en) | 2016-09-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2014176975A1 (zh) | Drni中同一端内系统之间交互信息的方法和系统 | |
RU2635288C2 (ru) | Способ и система для поддержки операций по протоколу управления распределенным ретранслятором (drcp) при сбое связи | |
EP1982447B1 (en) | System and method for detecting and recovering from virtual switch link failures | |
US7983173B2 (en) | System and method for detecting link failures | |
US8817594B2 (en) | Technique establishing a forwarding path in a network system | |
US7197660B1 (en) | High availability network security systems | |
JP4527447B2 (ja) | ネットワーク中継装置及びその制御方法 | |
WO2015101168A1 (zh) | 故障恢复的方法及控制器 | |
EP2911355B1 (en) | Method and device for flow path negotiation in link aggregation group | |
JP2013519268A (ja) | データ転送方法、データ転送装置及びデータ転送システム | |
US11128663B2 (en) | Synchronizing link and event detection mechanisms with a secure session associated with the link | |
WO2012058895A1 (zh) | 聚合链路切换方法及装置 | |
WO2015070383A1 (zh) | 一种链路聚合的方法、装置和系统 | |
US8711681B2 (en) | Switch redundancy in systems with dual-star backplanes | |
EP1803259B1 (en) | Carrier class resilience solution for switched ethernet local area networks (lans) | |
WO2014201903A1 (zh) | 分布式弹性网络互连系统中协作方法和系统 | |
CN112995002B (zh) | 一种交换机环网的设计方法、交换机及存储介质 | |
WO2014075594A1 (zh) | 基于多环结构网络相交环的业务的传输保护方法及装置 | |
WO2013004124A1 (zh) | 一种分布式链路聚合系统中业务流转发方法及节点 | |
CN116962284A (zh) | 针对受控不可用事件的mclag的高效业务重定向 | |
WO2014044088A1 (zh) | L2tp网络的保护方法、装置及系统 | |
KR102376484B1 (ko) | 이중화 회선 자동 절체를 위한 장치 및 방법 | |
US20220321268A1 (en) | Review and retry for minimum speed port channel | |
CN108430039A (zh) | 一种组播优化方法、组播设备及系统 | |
JP2001148714A (ja) | 通信ネットワーク装置および簡易ルーティング方法 |
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: 14791616 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016510922 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14787596 Country of ref document: US Ref document number: 2014791616 Country of ref document: EP |