WO2014056367A1 - 聚合端口id分配方法及装置 - Google Patents

聚合端口id分配方法及装置 Download PDF

Info

Publication number
WO2014056367A1
WO2014056367A1 PCT/CN2013/082699 CN2013082699W WO2014056367A1 WO 2014056367 A1 WO2014056367 A1 WO 2014056367A1 CN 2013082699 W CN2013082699 W CN 2013082699W WO 2014056367 A1 WO2014056367 A1 WO 2014056367A1
Authority
WO
WIPO (PCT)
Prior art keywords
port
aggregation
aggregated
aggregation port
terminal
Prior art date
Application number
PCT/CN2013/082699
Other languages
English (en)
French (fr)
Inventor
郭锥
喻敬海
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP13844911.1A priority Critical patent/EP2908486B1/en
Publication of WO2014056367A1 publication Critical patent/WO2014056367A1/zh

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
    • 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
    • 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

  • LACP Link Aggregation Control Protocol
  • Link Aggregation Control Protocol is a protocol that implements dynamic link aggregation and de-aggregation based on the IEEE802.3ad standard.
  • LACP uses Link Aggregation to control protocol data units (Link Aggregation).
  • Link Aggregation The Control Protocol Data Unit (LACPDU) is used to exchange information with the peer.
  • FIG. 1 is a partial format of a LACPDU packet according to the related art.
  • the port identifier (Port Identifier) is composed of an aggregate port priority (Actor_Port_Priority) and an aggregate port number (Actor_Port).
  • the upper two bytes are aggregate ports. Priority, the lower two bytes are the aggregate port number.
  • IEEE standard 802.1A link aggregation can protect multiple links, but only supports port aggregation on a system, so it can only be used for link protection, but on the network edge interface. In-end system protection cannot be achieved by using current link aggregation technology.
  • the IEEE802.1 working group has established a distributed link aggregation technology, that is, one or more end systems form a logical end system for link aggregation, which will be more on multiple end systems.
  • Strip links are aggregated into one aggregation group, thus achieving dual redundant network interconnection protection for links and end systems.
  • link aggregation technology a key technical factor is the allocation of the aggregation port ID.
  • the aggregation port ID is used to negotiate the local end system and the peer system. The size of the ID to determine the state of the ports on both ends.
  • the aggregation port ID is uniformly assigned by the system, and each physical port has an ID that is uniquely not duplicated with other aggregation ports.
  • Embodiments of the present invention provide a method and an apparatus for allocating an aggregated port ID to solve at least the above problems.
  • a method for allocating an aggregated port ID including: an in-terminal primary system at one end of an aggregated link group assigning an aggregated port ID to an aggregated port of the primary system in the end, and according to the The aggregation port allocation request from the system in the end of the aggregation link group is the aggregation port ID assigned to the corresponding aggregation port of the system in the end.
  • the method further includes: checking, by the system, whether the allocated aggregation port ID is valid, and notifying the verification result The end internal system.
  • the method further includes: negotiating multiple end systems at one end of the aggregation link group Determining the in-terminal primary system and the in-end secondary system; or determining an in-terminal primary system and an in-end secondary system at one end of the aggregated link group according to a pre-configuration.
  • the allocating the aggregated port ID to the corresponding aggregate port of the system in the end according to the aggregate port allocation request of the intra-terminal slave system includes: the intra-terminal master system receiving the aggregate port of the slave system in the end Allocating a request; the in-terminal primary system assigns an aggregated port ID to a corresponding aggregated port of the slave system according to the aggregated port assignment request; the in-terminal primary system sends the assigned aggregated port ID to the End from the system.
  • the in-terminal primary system sends the allocated aggregated port ID to the
  • the in-end slave system includes: establishing a correspondence between the aggregated port ID and the local aggregated port ID; and sending the aggregated port ID and the corresponding relationship to the in-end slave system.
  • the method further includes: the main system and the end in the end If the Intra-Portal Link (IPL) is disconnected from the system, if the in-band slave system is isolated, the in-band system in the aggregate state retains the aggregate port ID of the aggregation port.
  • IPL Intra-Portal Link
  • the method further includes: the main system and the end in the end Internal slave system
  • the intra-terminal secondary system re-negotiates an end-end primary system to re-allocate the aggregated port ID for the in-band system in the aggregated state.
  • the method further includes: receiving, by the intra-terminal master system, the intra-end slave a port removal request sent by the system, where the port removal request carries an aggregation port ID to be removed; the end main system recovers the aggregation port ID to be removed according to the port removal request .
  • a method for allocating an aggregation port ID including: an intra-end system at one end of an aggregation link group is an aggregation port of the intra-terminal system according to an in-end system ID and an aggregation port number thereof. Assign the aggregate port ID.
  • the intra-end system at one end of the aggregation link group allocates an aggregation port ID for the aggregation port of the intra-terminal system according to the in-terminal system ID and the aggregation port number, and includes: an intra-end system at one end of the aggregation link group according to the port priority.
  • the in-end system ID and the aggregation port number are the aggregation port IDs of the aggregation ports of the in-end system.
  • the method further includes: the intra-system system The assigned aggregated port ID notifies other end-end systems at one end of the aggregated link group.
  • an aggregation port ID allocation apparatus including an allocation module, configured to allocate an aggregation port ID to an aggregation port of an in-terminal primary system at one end of an aggregation link group, and according to the aggregation An aggregation port assignment request from the system in the end of one end of the link group allocates an aggregation port ID for the corresponding aggregation port of the system in the end.
  • the device further includes: a processing module, configured to check whether the aggregated port ID allocated by the in-terminal main system is valid, and notify the end main system of the verification result.
  • the processing module is further configured to: if the in-terminal main system receives the port removal request sent by the system from the system, the aggregation to be removed according to the port removal request
  • the port ID is reclaimed, wherein the port removal request carries an aggregation port ID to be removed.
  • an aggregation port ID allocation apparatus including a port ID allocation module, configured to be an aggregation port of an intra-end system at one end of an aggregation link group according to an intra-system ID and an aggregation port number. Assign the aggregate port ID.
  • the port ID assignment module is further configured to allocate an aggregate port ID to the aggregate port of the end system according to the aggregate port priority, the in-end system ID, and the aggregate port number.
  • the apparatus further includes: a notification module, configured to notify the other end-end system in one end of the aggregation link group of the allocated aggregation port ID.
  • FIG. 1 is a partial format of a LACPDU message according to the related art
  • FIG. 2 is a flowchart of a method for allocating an aggregated port ID according to an embodiment of the present invention
  • FIG. 3 is an aggregation port according to an embodiment of the present invention.
  • FIG. 4 is a block diagram showing the structure of an aggregation port ID allocation apparatus according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a method for allocating an aggregation port ID according to a preferred embodiment of the present invention
  • 6 is a second flowchart of a method for aggregating port ID allocation according to a preferred embodiment of the present invention
  • FIG. 7a is a system block diagram of a multi-end intra-system aggregation link group according to an embodiment of the present invention
  • FIG. 7b is a preferred embodiment of the present invention
  • FIG. 8 is a fourth flowchart of a method for allocating an aggregated port ID according to a preferred embodiment of the present invention.
  • FIG. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
  • Embodiment 1 The embodiment of the present invention provides a method for allocating an aggregation port ID.
  • FIG. 1 The embodiment of the present invention provides a method for allocating an aggregation port ID.
  • Step S202 the primary system at the end of the aggregation link group allocates an aggregation port to the aggregation port of the primary system in the end.
  • Step S204 Assign an aggregation port ID to the corresponding aggregation port of the system according to the aggregation port allocation request of the system in the end of the aggregation link group.
  • the aggregation port ID is uniformly allocated by the in-band primary system at one end of the aggregation link group, and the aggregation port ID is uniformly allocated, thereby ensuring the uniqueness of the aggregation port ID.
  • the in-band slave system can verify whether the received aggregated port ID is valid, and notify the in-end primary system of the check result. .
  • the in-end slave system verifies the aggregated port ID, which avoids the situation that the aggregated port ID of the aggregated port is unavailable when the assigned aggregated port ID is invalid.
  • the in-terminal primary system and the in-end secondary system can negotiate to determine the internal primary system and the internal secondary secondary system, or according to pre-configuration.
  • the in-end primary system and the in-end slave system at one end of the aggregation link group can be determined.
  • the in-end primary system can directly assign aggregated port IDs to all end-end systems, and can also receive aggregated ports.
  • the aggregated port ID is assigned to the system from the end that sent the request.
  • the aggregated port ID is allocated to the aggregated port of the system according to the aggregated port ID allocation request, and then the allocated aggregated port ID is sent to the End from the system.
  • the in-end slave system can request to allocate the aggregated port ID if the aggregated port ID is required, so as to avoid wasting the aggregated port ID resource.
  • the in-terminal primary system receives the aggregated port ID allocation request from the system in the end, preferably, the aggregated port ID allocation request may carry the local aggregated port ID assigned by the system to the aggregated port of the system, and Preferably, the correspondence between the aggregation port ID and the local aggregation port ID may be established, and the aggregation port ID and the corresponding relationship are sent to the intra-slave slave system.
  • the intra-terminal primary system establishes an association between the aggregation port ID and the aggregation port of the intra-system slave system.
  • the intra-end subsystem can be based on the above.
  • the corresponding relationship sends the received aggregated port ID to the corresponding aggregation port.
  • the primary system in the end allocates the aggregation port ID for the in-terminal primary system and the intra-terminal aggregation port of the system respectively, if the primary system in the end is disconnected from the intermediate link IPL of the system, then the primary system and the end are in the end.
  • the following two methods may be included: In the first mode, if the in-band slave system is isolated, the master system in the aggregation state retains the aggregation port ID of the aggregation port, and the slave system in the aggregation state retains the aggregation port ID.
  • Manner 2 If the in-end primary system is isolated, the intra-terminal primary system is renegotiated from the system and the aggregated port ID is re-allocated for the aggregation port of the intra-system.
  • the system in the end can process correspondingly according to different situations, thereby saving link resources.
  • the intra-terminal main system allocates the aggregation port IDs to the aggregation ports of the plurality of intra-end systems respectively, preferably, after the intra-terminal main system receives the port removal request sent from the system in the end, the main system in the end will The aggregation port ID to be removed is reclaimed, and the port removal request carries the aggregation port ID to be removed.
  • the second embodiment of the present invention further provides a method for allocating an aggregated port ID. Specifically, an in-end system at one end of an aggregated link group allocates an aggregated port according to an in-terminal system ID and an aggregated port number. ID.
  • the in-end system at one end of the aggregation link group allocates the aggregation port ID according to the in-terminal system ID and the aggregation port number of the intra-system aggregation port, including: the intra-end system at one end of the aggregation link group according to the port priority and the end
  • the internal system ID and the aggregated port number are the aggregated port IDs of the aggregated ports of the in-end system.
  • the method further includes: the intra-system system allocates the allocated aggregation port ID Notify other end-end systems at one end of the aggregated link group.
  • Embodiment 3 The embodiment of the present invention further provides an aggregation port ID allocation device, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again.
  • the term "module" may implement a combination of software and/or hardware of a predetermined function.
  • FIG. 3 is a structural block diagram of an aggregation port ID allocation apparatus according to an embodiment of the present invention.
  • the apparatus includes an allocation module 302.
  • the allocating module 302 is configured to allocate an aggregation port ID to the aggregation port of the primary system in the end of the aggregation link group, and according to the aggregation port allocation request of the system from the end of the aggregation link group, the corresponding The aggregation port assigns an aggregated port ID.
  • the device further includes: a processing module 304, configured to check whether the aggregated port ID allocated by the primary system in the terminal is valid, and notify the end main system of the verification result.
  • the processing module 304 is further configured to: when the in-terminal primary system receives the port removal request sent from the system in the end, recover the aggregated port ID to be removed according to the port removal request, where the port is removed The request carries the aggregated port ID to be removed.
  • the components in the device can be combined with each other to complete the corresponding functions according to the method described in the first embodiment, and have the same beneficial effects. .
  • Embodiment 4 The embodiment of the present invention further provides an aggregation port ID allocation device.
  • the device includes a port ID assignment. Module 402.
  • the port ID assignment module 402 is configured to allocate an aggregated port ID according to an in-terminal system ID and an aggregated port number as an aggregated port of the in-end system.
  • the port ID assignment module 402 is further configured to allocate an aggregated port ID to the aggregated port of the in-end system according to the aggregated port priority, the in-end system ID, and the aggregated port number.
  • the apparatus further includes a notification module 404 configured to notify the other end systems in one of the aggregated link groups of the assigned aggregated port ID.
  • FIG. 5 is a flowchart of a method for allocating an aggregated port ID according to a preferred embodiment of the present invention. As shown in FIG. 5, the flow includes the following steps: Step S502, determining an in-end primary system and an in-end secondary system. Each end-end system in one end of the aggregation link group performs system negotiation in the master-slave system to determine the internal system in the end and the slave system in the end. The specific method for negotiating from the system in the primary end is the prior art, and details are not described herein again.
  • Step S504 the in-end main system receives the aggregate port ID allocation request sent from the system in the end.
  • the aggregated port ID is uniformly assigned by the in-terminal master system.
  • the system sends an aggregation port ID allocation request to the primary system.
  • the request packet carries the local aggregation port ID assigned by the system to the aggregation port.
  • the advertising protocol between the in-end systems can implement information exchange through a specific protocol, which may be a Distributed Relay Control Protocol (DRCP) protocol.
  • DRCP Distributed Relay Control Protocol
  • Step S506 the in-end main system allocates an aggregation port ID to the in-end slave system.
  • the in-end primary system After receiving the aggregation port ID allocation request, the in-end primary system allocates an aggregation port ID to the inbound end system, and saves the correspondence between the local aggregation port ID and the assigned aggregation port ID carried in the request. If the request carries multiple local aggregation port IDs, it indicates that multiple aggregation ports in the system need to allocate aggregation port IDs. Therefore, the primary system in the end should allocate multiple aggregation port IDs to the local end based on the local aggregation port ID. system.
  • Step S508 the in-end main system sends the allocated aggregate port ID to the in-band slave system.
  • Step S512 the processing intermediate link is disconnected.
  • FIG. 6 is a second flowchart of a method for allocating an aggregated port ID according to a preferred embodiment of the present invention. As shown in FIG.
  • Step S602 Each end-end system separately allocates an aggregation port thereof.
  • Aggregate port ID is composed of an aggregation port priority (Actor_Port_Priority) and an aggregation port number (Actor_Port).
  • the upper two bytes are the aggregation port priority, and the lower two bytes are the aggregation port number.
  • the uniqueness of the port number is ensured by including the in-end system ID in the aggregation port number.
  • the system ID in the end is represented by 3 bits, and can be configured by the administrator or generated by other identifiers of the system.
  • the upper bit of the aggregation port number is used to store the ID of the system in the end where the aggregation port is located, and the lower one of the aggregation port number is used to store the aggregation port number, so that the aggregation port allocated by the system in each end is configured.
  • the number is limited to a range, which ensures that there is no duplication of port numbers assigned by the systems in each end of the aggregated link group.
  • Step S604 notifying other end systems.
  • the generated aggregated port ID is notified to other end systems in one end of the aggregated link group. When the end system loses contact with other end systems, the aggregate port ID is restored to the default state.
  • FIG. 7a is a block diagram of a system structure of a multi-end intra-system aggregation link group according to an embodiment of the present invention. As shown in FIG. 7a, one end of an aggregation link group is composed of two intra-end system As and an intra-end system B. The intermediate link IPL is connected to form one end of the distributed aggregation link group. Similarly, the two end systems C and D form the other end of the aggregated link group. In-end system A is connected through port PortA and in-terminal system C.
  • FIG. 7a is a third flowchart of a method for allocating an aggregated port ID according to a preferred embodiment of the present invention. As shown in FIG.
  • Step S702 The primary system in the end allocates an aggregation port ID to the port, and the primary system A in the end allocates an aggregation port ID to the port A of the local system that joins the aggregation group.
  • the saved port information is as follows:
  • Step S704 the in-end main system receives the aggregate port ID allocation request of the slave system in the end.
  • the port B of the system is added to the aggregation link group, and the end of the system initiates an aggregation port ID allocation request from the system to the internal system.
  • the type length value in the following figure is TLV format:
  • the primary system When the inbound end of the system has multiple aggregation port requests, the primary system allocates an aggregation port ID.
  • the request packet carries an aggregation port ID of 0 and multiple local aggregation port IDs.
  • Step S706 After receiving the aggregated port ID allocation request from the primary system in the end of the system, the primary system performs the aggregation port ID allocation check. If the primary system in the terminal checks that no aggregated port ID is allocated, it returns a response packet. The included aggregation port ID is identified as 0; otherwise, the in-end system is assigned an available aggregation port ID.
  • Step S708 the in-end primary system sends an aggregation port assignment response message to the in-end slave system. Assume that the port number assigned by the primary system in the terminal is 2, and the format of the message sent by the primary system to the slave system in the terminal is as follows:
  • the response packet carries a combination of multiple aggregation port IDs and local aggregation port IDs.
  • the in-end primary system saves the port information:
  • Step S710 the end is checked from the system.
  • the terminal After receiving the response packet from the system, the terminal obtains the assigned aggregation port ID and performs validity check. If the newly assigned aggregated port ID in the response packet is duplicated with the aggregated port ID of other ports currently stored in the system, the allocation is invalid; otherwise, it is valid.
  • Step S712 the end result is sent from the system to the end main system. If the in-end slave system checks that the aggregation port ID assignment is valid, it sends an acknowledgement packet to the in-terminal primary system and saves the port assignment information:
  • the device If the system checks that the aggregation port ID is invalid, the device sends an error indication packet to the primary system.
  • the packet carries all the aggregation port information with duplicate IDs.
  • the detailed format is as follows -
  • the primary system in the terminal After receiving the error indication message, the primary system in the terminal re-allocates the aggregation port ID, and performs steps S706 to S714 to process the intermediate link disconnection.
  • the primary system in the end When the primary system in the end is disconnected from the intermediate link IPL between the systems, if the internal slave system is isolated, the primary system in the aggregated state retains the aggregated port ID of the aggregated port, and at the same time, the end The internal primary system deletes the corresponding relationship between the local aggregation port ID and the aggregation port ID. If the internal system is isolated, the internal system in the end renegotiates the internal system and is the in-band system in the aggregation state.
  • the system block diagram of this implementation is shown in Figure 7a.
  • the logical end system at one end of the aggregation link group is composed of two end systems A and B.
  • the end system A and the end system B have no master-slave distinction, and the end
  • the in-end system IDs of the inner system A and the in-end system B have been pre-allocated or negotiated. It is assumed here that the in-end system ID of the system A in the end is 0, and the in-end system ID of the system B in the end is 1.
  • the in-end system A and the in-end system B are connected through the intermediate link IPL to form one end of the distributed aggregation link group.
  • FIG. 8 is a fourth flowchart of a method for allocating an aggregation port ID according to a preferred embodiment of the present invention. As shown in FIG. 8, the process includes the following steps: Step S802: In-end system A allocates an aggregation port ID for its aggregation port. In-end system A assigns the aggregation port ID to Port A of the aggregation group in the local end. The information about the aggregation port ID is as follows:
  • the aggregation port ID is composed of an aggregation port priority, an in-end system ID, and an aggregation port number.
  • the upper 3 bits of the original aggregation port number are the in-end system ID, that is, 0 in the table, and the lower 13 bits are the aggregation port number, that is, Port A in the table.
  • the system A in the end announces the allocation information to the other end systems.
  • In-end system A advertises the aggregation port ID allocation information to system B in the end, such as the TLV format in the following figure: When the in-end system A simultaneously advertises multiple aggregation port IDs to other end systems, it can carry multiple aggregation port IDs in the packet at the same time.
  • Step S806 the system B in the end allocates an aggregation port ID to the system in the end.
  • the system B assigns the aggregation port ID to the port B of the aggregation group in the local end.
  • the information about the aggregation port ID is as follows:
  • step S808 the in-end system B notifies the in-end system A of the allocation information.
  • step S808 advertises the aggregation port allocation information to system A in the end, and notifies the TLV format of the message as shown below:
  • Step S810 the process of disconnecting the intermediate link.
  • the intra-terminal system A and the intra-system B intermediate link IPL are disconnected, the intra-end system that is still in the aggregation state retains its own intra-end system ID, and the intra-end system that is isolated from the aggregation link group changes the system.
  • the in-end system ID is the default value of 0, and the port ID is reassigned to the aggregated port on the system within its end.
  • the two ends are consistent. Internal system instance processing flow. From the above description, it can be seen that the present invention achieves the following technical effects:
  • the unified allocation of the aggregation port is implemented by the intra-terminal system negotiation mode or the intra-system fixed allocation policy, and the unique aggregation port ID is ensured. Sex.
  • the above modules or steps of the embodiments of the present invention can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in multiple computing devices.
  • embodiments of the invention are not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种聚合端口ID分配方法及装置，该方法包括聚合链路组一端的端内主***为所述端内主***的聚合端口分配聚合端口ID，并根据所述聚合链路组一端的端内从***的聚合端口分配请求为所述端内从***的相应的聚合端口分配聚合端口ID。本发明解决了相关技术中聚合链路组一端中的多个端内***的聚合端口ID分配存在的问题，具有能够实现统一分配聚合端口ID保证聚合端口ID唯一性的有益效果。

Description

聚合端口 ID分配方法及装置 技术领域 本发明涉及通信领域， 具体而言， 涉及一种聚合端口 ID分配方法及装置。 背景技术 以太网链路聚合简称链路聚合， 它通过将多条以太网物理链路捆绑在一起成为一 条逻辑链路， 从而实现增加链路带宽的目的。 同时， 这些捆绑在一起的链路通过相互 间的动态备份， 可以有效地提高链路的可靠性。 链路聚合控制协议 （Link Aggregation Control Protocol, 简称 LACP) 是一种基于 IEEE802.3ad标准的、 能够实现链路动态聚合与解聚合的协议， 通常 LACP协议通过 链路聚合控制协议数据单元 （Link Aggregation Control Protocol Data Unit, 简称 LACPDU) 与对端进行信息交互。 图 1是根据相关技术的 LACPDU报文的部分格式，聚合端口标识（Port Identifier, 简称为 Port ID) 由聚合端口优先级 （Actor_Port_Priority) 和聚合端口号 （Actor_Port) 组成， 高两字节是聚合端口优先级， 低两字节是聚合端口号。 目前 IEEE现有标准 802.1A 链路聚合能够实现多条链路的保护， 但仅限于支持 的是一个***上的端口聚合， 因此仅能用于链路保护上， 但是在网络边缘接口上若要 对端内***保护在采用当前的链路聚合技术中就无法实现。 因此 IEEE802.1工作组对 一种分布式的链路聚合技术进行了立项， 即由一个或多个端内***组成一个逻辑端内 ***来进行链路聚合， 将多个端内***上的多条链路聚合为一个聚合组中， 从而实现 了链路和端内***的双冗余的网络互连保护。 在链路聚合技术中， 关键的一个技术因素是聚合端口 ID的分配， 聚合端口 ID的 作用在于本端***和对端***进行协商时， 根据两端***中设备 ID 较优的一端的聚 合端口 ID的大小， 来决定两端端口的状态。 在 LACP***中， 聚合端口 ID由***统 一分配， 每个物理端口有一个唯一不与其他聚合端口重复的 ID， 而在分布式链路聚合 ***中， 由于在一个***中可以存在两个或多个端内***，为了保证聚合端口 ID分配 的统一性， 需要一种方法能够实现端口的统一分配， 保证聚合端口 ID的唯一性， 并需 要和 LACP协议相互兼容。 针对相关技术中聚合端口 ID分配存在的问题， 目前尚未提出有效的解决方案。 发明内容 本发明实施例提供了一种聚合端口 ID分配方法及装置， 以至少解决上述问题。 根据本发明实施例的一个方面， 提供了一种聚合端口 ID分配方法， 包括： 聚合链 路组一端的端内主***为所述端内主***的聚合端口分配聚合端口 ID，并根据所述聚 合链路组一端的端内从***的聚合端口分配请求为所述端内从***的相应的聚合端口 分配聚合端口 ID。 优选地， 为所述端内从***的相应的聚合端口分配聚合端口 ID之后，所述方法还 包括：所述端内从***校验所分配的聚合端口 ID是否有效，并将校验结果通知所述端 内主***。 优选地， 聚合链路组一端的端内主***为所述端内主***的聚合端口分配聚合端 口 ID之前，所述方法还包括：所述聚合链路组一端的多个端内***进行协商确定所述 端内主***和所述端内从***； 或根据预先配置确定所述聚合链路组一端的端内主系 统和端内从***。 优选地， 根据所述端内从***的聚合端口分配请求为所述端内从***的相应的聚 合端口分配聚合端口 ID包括:所述端内主***接收到所述端内从***的聚合端口分配 请求； 所述端内主***根据所述聚合端口分配请求为所述端内从***的相应的聚合端 口分配聚合端口 ID;所述端内主***将所分配的聚合端口 ID发送给所述端内从***。 优选地， 在所述聚合端口分配请求中携带有所述端内从***为其聚合端口分配的 局部聚合端口 ID的情况下， 所述端内主***将所分配的聚合端口 ID发送给所述端内 从***包括： 建立所述聚合端口 ID与所述局部聚合端口 ID的对应关系； 将所述聚合 端口 ID及所述对应关系发送给所述端内从***。 优选地， 根据所述端内从***的聚合端口分配请求为所述端内从***的相应的聚 合端口分配聚合端口 ID之后，所述方法还包括：在所述端内主***和所述端内从*** 的中间链路 （Intra-Portal Link ， 简称 IPL) 断开的情况下， 如果隔离出去的是端内从 ***， 则处于聚合状态的端内***保留其聚合端口的聚合端口 ID。 优选地， 根据所述端内从***的聚合端口分配请求为所述端内从***的相应的聚 合端口分配聚合端口 ID之后，所述方法还包括：在所述端内主***和所述端内从*** 的中间链路 IPL断开的情况下， 如果隔离出去的是端内主***， 则端内从***重新协 商出一个端内主***为处于聚合状态的端内***重新分配聚合端口 ID。 优选地， 根据端内从***的聚合端口分配请求为所述端内从***的相应的聚合端 口分配聚合端口 ID之后，所述方法还包括：所述端内主***接收到所述端内从***发 送的端口移除请求， 其中， 所述端口移除请求中携带有待移除的聚合端口 ID; 所述端 内主***根据所述端口移除请求将所述待移除的聚合端口 ID回收。 根据本发明实施例的另一方面， 提供了一种聚合端口 ID分配方法， 包括： 聚合链 路组一端的端内***根据其端内*** ID 和聚合端口号为所述端内***的聚合端口分 配聚合端口 ID。 优选地，聚合链路组一端的端内***根据其端内*** ID和聚合端口号为所述端内 ***的聚合端口分配聚合端口 ID包括： 聚合链路组一端的端内***根据端口优先级、 端内*** ID和聚合端口号为所述端内***的聚合端口分配聚合端口 ID。 优选地，聚合链路组一端的端内***根据其端内*** ID和聚合端口号为所述端内 ***的聚合端口分配聚合端口 ID之后，所述方法还包括：所述端内***将所分配的聚 合端口 ID通知所述聚合链路组一端的其他端内***。 根据本发明实施例的另一方面，提供了一种聚合端口 ID分配装置，包括分配模块， 设置为为聚合链路组一端的端内主***的聚合端口分配聚合端口 ID，并根据所述聚合 链路组一端的端内从***的聚合端口分配请求为所述端内从***的相应的聚合端口分 配聚合端口 ID。 优选地， 所述装置还包括： 处理模块， 设置为校验所述端内主***所分配的聚合 端口 ID是否有效， 并将校验结果通知所述端内主***。 优选地， 所述处理模块还设置为在所述端内主***接收到所述端内从***发送的 端口移除请求的情况下，根据所述端口移除请求将所述待移除的聚合端口 ID回收，其 中， 所述端口移除请求中携带有待移除的聚合端口 ID。 根据本发明实施例的另一方面， 提供了一种聚合端口 ID分配装置， 包括端口 ID 分配模块，设置为根据端内*** ID和聚合端口号为聚合链路组一端的端内***的聚合 端口分配聚合端口 ID。 优选地， 所述端口 ID分配模块还设置为根据聚合端口优先级、 端内*** ID和聚 合端口号为所述端内***的聚合端口分配聚合端口 ID。 优选地， 所述装置还包括： 通知模块， 设置为将所分配的聚合端口 ID通知所述聚 合链路组一端中的其他端内***。 通过本发明实施例， 解决了相关技术中聚合链路组中分配聚合端口 ID 存在的问 题， 进而达到了能够实现统一分配保证聚合端口 ID的唯一性的效果。 附图说明 此处所说明的附图用来提供对本发明实施例的进一步理解，构成本申请的一部分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的不当限定。 在 附图中- 图 1是根据相关技术的 LACPDU报文的部分格式； 图 2是根据本发明实施例的聚合端口 ID分配方法的流程图之一； 图 3是根据本发明实施例的聚合端口 ID分配装置的结构框图之一； 图 4是根据本发明实施例的聚合端口 ID分配装置的结构框图之二； 图 5是根据本发明优选实施例的聚合端口 ID分配方法的流程图之一； 图 6是根据本发明优选实施例的聚合端口 ID分配的方法的流程图之二； 图 7a是根据本发明实施例的多端内***聚合链路组的***结构框图； 图 7b是根据本发明优选实施例的聚合端口 ID分配方法的流程图之三； 图 8是本发明优选实施例提供的聚合端口 ID分配方法的流程图之四。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在不冲突的 情况下， 本申请中的实施例及实施例中的特征可以相互组合。 实施例一 本发明实施例提供了一种聚合端口 ID分配方法，图 2是根据本发明实施例的聚合 端口 ID分配方法的流程图之一， 如图 2所示， 该流程包括以下步骤： 步骤 S202，聚合链路组一端的端内主***为端内主***的聚合端口分配聚合端口
ID; 步骤 S204，根据聚合链路组一端的端内从***的聚合端口分配请求为端内从*** 的相应的聚合端口分配聚合端口 ID。 通过上述步骤， 实现由聚合链路组一端的端内主***统一分配聚合端口 ID， 实现 了对聚合端口 ID的统一分配， 进而保证了聚合端口 ID的唯一性。 在端内主***将所分配的聚合端口 ID发送给端内从***之后，优选地，端内从系 统可以校验所接收到的聚合端口 ID是否有效，并将校验结果通知端内主***。通过上 述步骤， 端内从***对聚合端口 ID进行校验， 避免了所分配的聚合端口 ID无效时该 聚合端口无聚合端口 ID可用以致无法通信的情况。 端内主***和端内从***的确定方式有很多种， 优选地， 可以是聚合链路组一端 的多个端内***进行协商确定端内主***和端内从***， 或者根据预先配置确定聚合 链路组一端的端内主***和端内从***。 通过上述步骤， 可以确定端内主***和端内 从***。 端内主***可以直接给所有端内***分配聚合端口 ID，也可以在接收到聚合端口
ID 分配请求之后， 给发送请求的端内从***分配聚合端口 ID。 优选地， 可以在接收 到端内从***的聚合端口 ID分配请求之后， 根据该聚合端口 ID分配请求为端内从系 统的聚合端口分配聚合端口 ID， 然后将所分配的聚合端口 ID发送给该端内从***。 这样， 端内从***可以在需要聚合端口 ID的情况下， 请求分配聚合端口 ID， 以避免 浪费聚合端口 ID资源。 在端内主***接收到端内从***的聚合端口 ID分配请求的情况下，优选地，该聚 合端口 ID分配请求中可以携带有端内从***为其聚合端口分配的局部聚合端口 ID， 并且， 优选地， 可以建立聚合端口 ID与局部聚合端口 ID的对应关系， 并将所述聚合 端口 ID及所述对应关系发送给所述端内从***。通过上述步骤，端内主***建立了聚 合端口 ID和端内从***的聚合端口之间的关联，在端内从***有多个聚合端口需要聚 合端口 ID的情况下， 端内子***可以根据上述对应关系将接收到的聚合端口 ID发送 给相应的聚合端口。 在端内主***分别为端内主***和端内从***的聚合端口分配聚合端口 ID之后， 如果端内主***和端内从***的中间链路 IPL断开， 那么端内主***和端内从***有 很多种处理方式。 优选地， 可以包括以下两种方式： 方式一， 如果隔离出去的是端内从***， 则处于聚合状态的端内主***保留其聚 合端口的聚合端口 ID， 处于聚合状态的端内从***也保留其聚合端口 ID。 方式二， 如果隔离出去的是端内主***， 则端内从***重新协商出一个端内主系 统并为端内***的聚合端口重新分配聚合端口 ID。 通过上述步骤， 在遇到中间链路断开的情况下， 端内***可以根据不同的情况进 行相应地处理， 进而节省了链路资源。 在端内主***分别为多个端内***的聚合端口分配聚合端口 ID之后，优选地，该 端内主***接收到端内从***发送的端口移除请求后， 端内主***将所述待移除的聚 合端口 ID回收， 其中端口移除请求中携带有待移除的聚合端口 ID。 通过上述步骤， 可以达到有效利用有限的聚合端口 ID的效果。 实施例二 本发明实施例还提供了一种聚合端口 ID分配方法，具体为：聚合链路组一端的端 内***根据其端内*** ID和聚合端口号为端内***的聚合端口分配聚合端口 ID。 优选地，聚合链路组一端的端内***根据其端内*** ID和聚合端口号为端内*** 的聚合端口分配聚合端口 ID包括：聚合链路组一端的端内***根据端口优先级、端内 *** ID和聚合端口号为端内***的聚合端口分配聚合端口 ID。 优选地，聚合链路组一端的端内***根据其端内*** ID和聚合端口号为端内*** 的聚合端口分配聚合端口 ID之后， 该方法还包括： 端内***将所分配的聚合端口 ID 通知聚合链路组一端的其他端内***。 实施例三 本发明实施例还提供了一种聚合端口 ID分配装置，该装置用于实现上述实施例及 优选实施方式， 已经进行过说明的不再赘述。 如以下所使用的， 术语"模块"可以实现 预定功能的软件和 /或硬件的组合。 尽管以下实施例所描述的装置较佳地以软件来实 现， 但是硬件， 或者软件和硬件的组合的实现也是可能并被构想的。 图 3是根据本发明实施例的聚合端口 ID分配装置的结构框图之一， 如图 3所示， 该装置包括分配模块 302。 分配模块 302， 设置为为聚合链路组一端的端内主***的聚合端口分配聚合端口 ID, 并根据聚合链路组一端的端内从***的聚合端口分配请求为端内从***的相应的 聚合端口分配聚合端口 ID。 优选地， 该装置还包括： 处理模块 304， 设置为校验端内主***所分配的聚合端 口 ID是否有效， 并将校验结果通知端内主***。 优选地， 处理模块 304还设置为在端内主***接收到端内从***发送的端口移除 请求的情况下， 根据端口移除请求将待移除的聚合端口 ID回收， 其中， 端口移除请求 中携带有待移除的聚合端口 ID。 在本发明实施例的优选实施方式中， 该装置中的各个组成部分可以按照上述实施 例一所述的方法相互组合完成相应的功能， 并具有相同的有益效果， 具体本发明实施 例不再赘述。 实施例四 本发明实施例还提供了一种聚合端口 ID分配装置，图 4是根据本发明实施例的聚 合端口 ID分配装置的结构框图之二， 如图 4所示， 该装置包括端口 ID分配模块 402。 端口 ID分配模块 402， 设置为根据其端内*** ID和聚合端口号为端内***的聚 合端口分配聚合端口 ID。 优选地， 端口 ID分配模块 402还设置为根据聚合端口优先级、 端内*** ID和聚 合端口号为端内***的聚合端口分配聚合端口 ID。 优选地， 所述装置还包括通知模块 404， 设置为将所分配的聚合端口 ID通知聚合 链路组一端中的其他端内***。 在本发明实施例的优选实施方式中， 该装置中的各个组成部分可以按照上述实施 例二所述的方法相互组合完成相应的功能， 并具有相同的有益效果， 具体本发明实施 例不再赘述。 实施例五 图 5是根据本发明优选实施例的聚合端口 ID分配方法的流程图之一，如图 5所示， 该流程包括以下步骤： 步骤 S502， 确定端内主***和端内从***。 聚合链路组一端内各个端内***进行主从端内***协商， 确定端内主***和端内 从***。 具体的主端内从***协商的方法是现有技术， 此处不再赘述。 步骤 S504， 端内主***接收到端内从***发送的聚合端口 ID分配请求。 在确定端内***的主从之后，聚合端口 ID统一由端内主***分配。端内从***发 现聚合端口后， 向端内主***发送聚合端口 ID分配请求，在该请求报文中携带该端内 从***为该聚合端口分配的局部聚合端口 ID。端内***之间的通告协议可以通过特定 的协议来实现信息的交互， 该协议可以是分布式中继控制协议 （Distributed Relay Control Protocol, 简称 DRCP)协议。端内***及其所连接的其他端内***情况的信息 可以通过该协议报文携带在协议中。 步骤 S506， 端内主***为端内从***分配聚合端口 ID。 端内主***接收到聚合端口 ID分配请求后， 为端内从***分配聚合端口 ID， 并 保存该请求中携带的局部聚合端口 ID和所分配的聚合端口 ID的对应关系。 如果请求 中携带多个局部聚合端口 ID， 表示该端内从***有多个聚合端口需要分配聚合端口 ID,因此端内主***应当根据局部聚合端口 ID分配多个聚合端口 ID给该端内从***。 步骤 S508， 端内主***将所分配的聚合端口 ID发送给端内从***。 端内主***通过聚合端口 ID分配应答报文返回聚合端口 ID给端内从***， 从而 使端内从***的聚合端口获取到聚合端口 ID。 步骤 S510， 端内主***处理端口移除请求。 当端内从***上的聚合端口从聚合链路组中删除时， 端内从***需要通告端内主 ***端口移除信息。 端内主***接收到端内从***发送的端口移除请求后， 由端内主 ***回收该聚合端口 ID， 该回收的聚合端口 ID可以选择为该端口保留而不会分配其 他端口， 也可以选择分配给其他端口。 如果选择保留， 则之前移除的聚合端口重新加 入该聚合链路组时端内主***重新分配聚合端口 ID 仍然可以是之前分配该端口使用 过的聚合端口 ID。 步骤 S512， 处理中间链路断开。 在端内主***和端内从***的中间链路断开的情况下， 如果隔离出去的是端内从 ***则处于聚合状态的端内主***保留其聚合端口的聚合端口 ID， 同时， 端内主*** 删除局部聚合端口 ID和聚合端口 ID的对应关系； 如果隔离出去的是端内主***， 则 端内从***重新协商出一个端内主***并为处于聚合状态的端内***的聚合端口重新 分配聚合端口 ID。 实施例六 图 6是根据本发明优选实施例的聚合端口 ID分配的方法的流程图之二， 如图 6 所示， 该流程包括以下步骤： 步骤 S602， 各端内***各自为其聚合端口分配聚合端口 ID。 相关技术中， 聚合端口 ID (Port ID) 由聚合端口优先级 （Actor_Port_Priority) 和 聚合端口号（Actor—Port)组成， 高两字节是聚合端口优先级，低两字节是聚合端口号。 本实施例中，采用在聚合端口号中包含端内*** ID的方式保证端口号的唯一性。其中 该端内*** ID是用 3位 bit表示， 可以由管理员配置， 也可以有***其它标识生成。 具体地说， 用聚合端口号中的高位用来存放该聚合端口所在的端内***的 ID， 该聚合 端口号中的低位用来存放聚合端口号， 这样把每个端内***分配的聚合端口号限定在 一个范围内， 保证了聚合链路组内各个端内***分配的端口号不会存在重复。 步骤 S604， 通知其他端内***。 将所生成的聚合端口 ID通知聚合链路组一端中的其他端内***。 当端内***与其他端内***失去联系时，聚合端口 ID恢复成默认状态。如果需要 对聚合端口 ID进行一定的排序，可以通过改变端口优先级实现端口的排序，也可以通 过优先合理分配端内*** ID实现。 实施例七 图 7a是根据本发明实施例的多端内***聚合链路组的***结构框图， 如图 7a所 示， 聚合链路组一端由两个端内*** A和端内*** B组成， 他们通过中间链路 IPL进 行连接， 从而形成分布式聚合链路组的一端， 同理， 两个端内*** C和 D构成聚合链 路组的另一端。 端内*** A通过端口 PortA和端内*** C连接， 端内*** 、 C之间 的链路是链路 1 ; 端内*** B通过端口 Port B和端内*** D连接， 端内*** B和 D 之间的链路是链路 2。假定，在图 7a中，通过配置或协商完成端内从***的主从协商， 其中端内*** A为端内主***， 端内*** B为端内从***。 图 7b是根据本发明优选实施例的聚合端口 ID分配方法的流程图之三， 如图 7b 所示， 该流程包括以下步骤： 步骤 S702， 端内主***为其端口分配聚合端口 ID 端内主*** A给本端内***加入聚合组的端口 Port A分配一个聚合端口 ID。 该 实例中假定聚合端口号为 1， 则保存的端口信息如下：
Figure imgf000011_0001
步骤 S704， 端内主***接收到端内从***的聚合端口 ID分配请求。 端内从***的端口 Port B加入聚合链路组， 端内从***向端内主***发起聚合端 口 ID分配请求， 例如下图的类型长度值 TLV格式：
Figure imgf000011_0002
当该端内从***同时有多个聚合端口请求端内主***分配聚合端口 ID时，可以在 请求报文中携带一个值为 0的聚合端口 ID和多个局部聚合端口 ID 步骤 S706， 端内主***为端内从***分配聚合端口 ID 端内主***接收到聚合端口 ID分配请求后， 进行聚合端口 ID分配检查， 若端内 主***检查无可用聚合端口 ID分配，则返回应答报文中包含的聚合端口 ID标识为 0; 否则， 给该端内***分配可用聚合端口 ID 步骤 S708， 端内主***向端内从***发送聚合端口分配应答报文。 假定端内主***分配的端口号为 2， 端内主***发送应答报文给端内从***的报 文的格式如下：
Figure imgf000011_0003
如果同时分配多个聚合端口 ID给该端内从***，则可以在应答报文中携带多个 聚合端口 ID和局部聚合端口 ID的组合。 成功分配聚合端口 ID后， 端内主***保 存该端口信息：
端内***
ID 聚合端口 ID 局部聚合端口 ID"
优 先 级 优 先 级 口
A Priority 1 Priority Port A 优 先 级 优 先 级 口
B Priority 2 Priority Port B
步骤 S710， 端内从***进行校验。 端内从***接收到应答报文后，获取分配的聚合端口 ID并进行有效性校验。如果 应答报文中新分配的聚合端口 ID和该端内从***现有保存的其他端口的聚合端口 ID 有重复， 则为无效分配； 否则为有效分配。 步骤 S712， 端内从***向端内主***发送校验结果。 端内从***检查聚合端口 ID分配有效，则向端内主***发送确认报文，并保存端 口分配信息：
Figure imgf000012_0001
端内从***检查聚合端口 ID无效的情况下，则重新向端内主***发送错误指示报 文， 报文需要携带所有存在重复 ID的聚合端口信息， 具体格式如下-
Figure imgf000012_0002
端内主***收到错误指示报文后， 重新分配聚合端口 ID， 执行步骤 S706 步骤 S714， 处理中间链路断开。 当端内主***和端内从***之间的中间链路 IPL断开， 如果隔离出去的是端内从 ***则处于聚合状态的端内主***保留其聚合端口的聚合端口 ID， 同时， 端内主*** 删除相应的局部聚合端口 ID和聚合端口 ID的对应关系； 如果隔离出去的是端内主系 统， 则端内从***重新协商出一个端内主***并为处于聚合状态的端内***的聚合端 口重新分配聚合端口 ID 实施例八 本实施的***结构框图如图 7a所示，聚合链路组一端的逻辑端内***是由两个端 内*** A和 B组成， 端内*** A和端内*** B无主从区分， 且端内*** A和端内系 统 B的端内*** ID已经预先分配或协商。 这里假设端内*** A的端内*** ID是 0， 端内*** B的端内*** ID是 1。 端内*** A和端内*** B通过中间链路 IPL进行连 接， 从而形成分布式聚合链路组的一端， 同理， 两个端内*** C和 D构成聚合链路组 的另一端。 端内*** A通过端口 PortA和端内*** C连接， 端内***八、 C之间的链 路是链路 1 ; 端内*** B通过端口 Port B和端内*** D连接， 端内*** B和 D之间 的链路是链路 2。 图 8是本发明优选实施例提供的聚合端口 ID分配方法的流程图之四，如图 8所示， 该流程包括以下步骤： 步骤 S802， 端内*** A为其聚合端口分配聚合端口 ID。 端内*** A给本端内***加入聚合组的 Port A分配聚合端口 ID， 分配聚合端口 ID信息如下：
Figure imgf000013_0001
其中， 聚合端口 ID由聚合端口优先级、 端内*** ID和聚合端口号组成。 其中， 原聚合端口号的高 3位为端内*** ID， 即表中的 0， 低 13位为聚合端口号， 即表中的 Port A。 步骤 S804， 端内*** A向其他端内***通告分配信息。 端内*** A向端内*** B通告聚合端口 ID分配信息， 例如下图的 TLV格式:
Figure imgf000013_0002
当端内*** A同时向其他端内***通告多个聚合端口 ID时， 可以在报文中同时 携带多个聚合端口 ID。 步骤 S806， 端内*** B为本端内***分配聚合端口 ID。 端内*** B给本端内***加入聚合组的 Port B分配聚合端口 ID， 分配聚合端口 ID信息如下：
聚合端口 ID 2字节 3位 13位
优先级 Priority 0 端 P Port B 聚合端口 ID的具体组成同步骤 S802， 此处不再赘述。 步骤 S808， 端内*** B向端内*** A通知分配信息。 端内*** B向端内*** A通告聚合端口分配信息， 通知报文如下图的 TLV格式:
Figure imgf000014_0001
当该端内***同时向其他端内***通告多个聚合端口 ID时，可以在报文中同时携 带多个聚合端口 ID。 步骤 S810， 中间链路断开的处理。 当端内*** A和端内*** B中间链路 IPL断开，则仍处于聚合状态的端内***保 留自己的端内*** ID不变， 从聚合链路组中隔离出去的端内***改变本端内*** ID 为默认值 0， 并为其端内***上的聚合端口重新分配端口 ID。 以上两个实施实例列举了一个聚合链路组内两个端内***的聚合端口 ID 分配处 理流程， 对于三端内***及以上多端内***的处理流程和两端内***一致， 可以参考 两端内***实例处理流程。 从以上的描述中， 可以看出， 本发明实现了如下技术效果： 本发明实施例通过端 内***协商方式或端内***固定分配策略实现对聚合端口的统一分配， 保证了聚合端 口 ID的唯一性。 显然， 本领域的技术人员应该明白， 上述的本发明实施例的各模块或各步骤可以 用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算 装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 并且在某些情况下， 可以以不同于 此处的顺序执行所示出或描述的步骤， 或者将它们分别制作成各个集成电路模块， 或 者将它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样， 本发明实施例 不限制于任何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域的技 术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内， 所作的 任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。 工业实用性 本发明实施例提供的技术方案可以应用于以太网链路聚合领域， 解决了聚合端口 ID分配存在的问题，通过端内***协商方式或端内***固定分配策略实现对聚合端口 的统一分配， 保证了聚合端口 ID的唯一性。

Claims

权 利 要 求 书
1. 一种聚合端口 ID分配方法， 包括： 聚合链路组一端的端内主***为所述端内主***的聚合端口分配聚合端口 ID, 并根据所述聚合链路组一端的端内从***的聚合端口分配请求为所述端内 从***的相应的聚合端口分配聚合端口 ID。
2. 根据权利要求 1所述的方法， 其中， 为所述端内从***的相应的聚合端口分配 聚合端口 ID之后， 所述方法还包括：
所述端内从***校验所分配的聚合端口 ID 是否有效， 并将校验结果通知 所述端内主***。
3. 根据权利要求 1或 2所述的方法， 其中， 聚合链路组一端的端内主***为所述 端内主***的聚合端口分配聚合端口 ID之前， 所述方法还包括：
所述聚合链路组一端的多个端内***进行协商确定所述端内主***和所述 端内从***； 或
根据预先配置确定所述聚合链路组一端的端内主***和端内从***。
4. 根据权利要求 1所述的方法， 其中， 根据所述端内从***的聚合端口分配请求 为所述端内从***的相应的聚合端口分配聚合端口 ID包括：
所述端内主***接收到所述端内从***的聚合端口分配请求； 所述端内主***根据所述聚合端口分配请求为所述端内从***的相应的聚 合端口分配聚合端口 ID;
所述端内主***将所分配的聚合端口 ID发送给所述端内从***。
5. 根据权利要求 4所述的方法， 其中， 在所述聚合端口分配请求中携带有所述端 内从***为其聚合端口分配的局部聚合端口 ID 的情况下， 所述端内主***将 所分配的聚合端口 ID发送给所述端内从***包括：
建立所述聚合端口 ID与所述局部聚合端口 ID的对应关系； 将所述聚合端口 ID及所述对应关系发送给所述端内从***。
6. 根据权利要求 1至 5中任一项所述的方法， 其中， 根据所述端内从***的聚合 端口分配请求为所述端内从***的相应的聚合端口分配聚合端口 ID 之后， 所 述方法还包括：
在所述端内主***和所述端内从***的中间链路 IPL断开的情况下， 如果 隔离出去的是端内从***， 则处于聚合状态的端内***保留其聚合端口的聚合 端口 ID。
7. 据权利要求 1至 5中任一项所述的方法， 根据所述端内从***的聚合端口分配 请求为所述端内从***的相应的聚合端口分配聚合端口 ID 之后， 所述方法还 包括：
在所述端内主***和所述端内从***的中间链路 IPL断开的情况下， 如果 隔离出去的是端内主***， 则端内从***重新协商出一个端内主***为处于聚 合状态的端内***重新分配聚合端口 ID。
8. 根据权利要求 1至 7中任一项所述的方法， 其中， 根据端内从***的聚合端口 分配请求为所述端内从***的相应的聚合端口分配聚合端口 ID 之后， 所述方 法还包括：
所述端内主***接收到所述端内从***发送的端口移除请求， 其中， 所述 端口移除请求中携带有待移除的聚合端口 ID;
所述端内主***根据所述端口移除请求将所述待移除的聚合端口 ID回收。
9. 一种聚合端口 ID分配方法， 包括：
聚合链路组一端的端内***根据其端内*** ID和聚合端口号为所述端内 ***的聚合端口分配聚合端口 ID。
10. 根据权利要求 9所述的方法， 其中， 聚合链路组一端的端内***根据其端内系 统 ID和聚合端口号为所述端内***的聚合端口分配聚合端口 ID包括：
聚合链路组一端的端内***根据端口优先级、 端内*** ID和聚合端口号 为所述端内***的聚合端口分配聚合端口 ID。
11. 根据权利要求 9或 10所述的方法，其中，聚合链路组一端的端内***根据其端 内*** ID和聚合端口号为所述端内***的聚合端口分配聚合端口 ID之后， 所 述方法还包括： 所述端内***将所分配的聚合端口 ID通知所述聚合链路组一端的其他端 内***。
12. 一种聚合端口 ID分配装置， 包括： 分配模块， 设置为为聚合链路组一端的端内主***的聚合端口分配聚合端 口 ID，并根据所述聚合链路组一端的端内从***的聚合端口分配请求为所述端 内从***的相应的聚合端口分配聚合端口 ID。
13. 根据权利要求 12所述的装置， 其中， 所述装置还包括：
处理模块， 设置为校验所述端内主***所分配的聚合端口 ID 是否有效， 并将校验结果通知所述端内主***。
14. 根据权利要求 12或 13所述的装置， 其中， 所述处理模块还设置为在所述端内 主***接收到所述端内从***发送的端口移除请求的情况下， 根据所述端口移 除请求将所述待移除的聚合端口 ID 回收， 其中， 所述端口移除请求中携带有 待移除的聚合端口 ID。
15. 一种聚合端口 ID分配装置， 包括：
端口 ID分配模块， 设置为根据端内*** ID和聚合端口号为聚合链路组一 端的端内***的聚合端口分配聚合端口 ID。
16. 根据权利要求 15所述的装置， 其中， 所述端口 ID分配模块还设置为根据聚合 端口优先级、 端内*** ID 和聚合端口号为所述端内***的聚合端口分配聚合 端口 ID。
17. 根据权利要求 15或 16所述的装置， 其中， 所述装置还包括：
通知模块， 设置为将所分配的聚合端口 ID通知所述聚合链路组一端中的 其他端内***。
PCT/CN2013/082699 2012-10-12 2013-08-30 聚合端口id分配方法及装置 WO2014056367A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP13844911.1A EP2908486B1 (en) 2012-10-12 2013-08-30 Aggregation port id allocation method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210387281.1A CN103731286A (zh) 2012-10-12 2012-10-12 聚合端口id分配方法及装置
CN201210387281.1 2012-10-12

Publications (1)

Publication Number Publication Date
WO2014056367A1 true WO2014056367A1 (zh) 2014-04-17

Family

ID=50455221

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/082699 WO2014056367A1 (zh) 2012-10-12 2013-08-30 聚合端口id分配方法及装置

Country Status (3)

Country Link
EP (1) EP2908486B1 (zh)
CN (1) CN103731286A (zh)
WO (1) WO2014056367A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108259348A (zh) * 2017-05-24 2018-07-06 新华三技术有限公司 一种报文传输方法和装置
CN111181866A (zh) * 2019-12-21 2020-05-19 武汉迈威通信股份有限公司 一种基于端口隔离的端口汇聚方法及***

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107547384B (zh) * 2017-08-21 2021-07-06 新华三技术有限公司 一种接口链路标识分配方法以及装置
CN108737189B (zh) * 2018-05-25 2021-11-05 新华三技术有限公司 Dr设备角色更新方法及装置
CN109088819A (zh) * 2018-07-25 2018-12-25 新华三技术有限公司合肥分公司 一种报文转发方法、交换机及计算机可读存储介质
CN109618015B (zh) * 2018-11-19 2022-01-11 锐捷网络股份有限公司 基于数据中心的去堆叠实现方法及装置
CN109728972B (zh) * 2018-12-14 2021-07-23 新华三技术有限公司 网络连接检测方法和装置
CN112087378B (zh) * 2020-08-18 2022-03-22 浪潮思科网络科技有限公司 一种LACP forceup功能的实现方法、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008009160A1 (fr) * 2006-06-30 2008-01-24 Zte Corporation Procédé de configuration d'accès pour l'ajout de liens et systèmes d'ajout de liens
CN102404102A (zh) * 2011-11-16 2012-04-04 中兴通讯股份有限公司 一种同步以太网的方法和设备
CN102428679A (zh) * 2009-05-18 2012-04-25 思科技术公司 在虚拟端口通道环境中实现机架间活动链路数目大体相等

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101252459B (zh) * 2008-03-24 2010-12-08 中兴通讯股份有限公司 一种设置链路端口的协议状态的方法及其监控方法
US8059638B2 (en) * 2009-06-30 2011-11-15 Alcatel Lucent Inter-node link aggregation system and method
JP5422844B2 (ja) * 2009-12-17 2014-02-19 日立金属株式会社 スイッチングハブ、ラインカード、及びフレーム中継方法
US8488608B2 (en) * 2010-08-04 2013-07-16 Alcatel Lucent System and method for traffic distribution in a multi-chassis link aggregation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008009160A1 (fr) * 2006-06-30 2008-01-24 Zte Corporation Procédé de configuration d'accès pour l'ajout de liens et systèmes d'ajout de liens
CN102428679A (zh) * 2009-05-18 2012-04-25 思科技术公司 在虚拟端口通道环境中实现机架间活动链路数目大体相等
CN102404102A (zh) * 2011-11-16 2012-04-04 中兴通讯股份有限公司 一种同步以太网的方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2908486A4 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108259348A (zh) * 2017-05-24 2018-07-06 新华三技术有限公司 一种报文传输方法和装置
WO2018214652A1 (zh) * 2017-05-24 2018-11-29 新华三技术有限公司 一种报文传输方法和装置
CN108259348B (zh) * 2017-05-24 2020-05-12 新华三技术有限公司 一种报文传输方法和装置
US11233735B2 (en) 2017-05-24 2022-01-25 New H3C Technologies Co., Ltd. Method and apparatus for message transmission
CN111181866A (zh) * 2019-12-21 2020-05-19 武汉迈威通信股份有限公司 一种基于端口隔离的端口汇聚方法及***
CN111181866B (zh) * 2019-12-21 2023-06-30 武汉迈威通信股份有限公司 一种基于端口隔离的端口汇聚方法及***

Also Published As

Publication number Publication date
EP2908486B1 (en) 2018-05-02
EP2908486A1 (en) 2015-08-19
EP2908486A4 (en) 2015-11-04
CN103731286A (zh) 2014-04-16

Similar Documents

Publication Publication Date Title
WO2014056367A1 (zh) 聚合端口id分配方法及装置
US10938710B2 (en) Protection switching method and system, and network device
US8285875B2 (en) Synchronizing resource bindings within computer network
US8880935B2 (en) Redundancy and load balancing in remote direct memory access communications
CN102067533B (zh) 与虚拟接口相关联的端口分组
US11398956B2 (en) Multi-Edge EtherChannel (MEEC) creation and management
US10404773B2 (en) Distributed cluster processing system and packet processing method thereof
US9998366B2 (en) System, method and device for forwarding packet
US20110310729A1 (en) Maintaining balance of active links across network devices in a double-sided virtual port-channel environment
WO2019042124A1 (zh) 一种通信方法、设备及存储介质
WO2004084496A1 (fr) Procede de mise en oeuvre de la distribution de la charge dynamique par les passerelles
WO2014190791A1 (zh) 一种网关设备身份设置的方法及管理网关设备
JP5107339B2 (ja) アクティブ地理的冗長性のためのシステムおよび方法
WO2017114363A1 (zh) 报文处理方法、bng及bng集群***
WO2014059867A1 (zh) 链路聚合组中流量路径的协商方法及装置
CN105490937B (zh) 以太虚拟网络网关切换方法和服务商边缘节点设备
WO2012100671A1 (zh) 一种绑定物理网口的方法、网卡及通信***
CN104734930B (zh) Vlan接入vf网络的实现方法及装置、fcf
WO2022052496A1 (zh) 地址预留的方法、网络设备和***
WO2016000186A1 (zh) 一种链路聚合方法及设备
WO2014015715A1 (zh) 逻辑通道的建立方法及***、边缘虚拟桥接站点及网桥
WO2014059873A1 (zh) 链路聚合组中流量路径的协商方法及装置
CN111131224B (zh) 一种维护连接的方法及存储设备
US10367681B2 (en) Maintenance of data forwarder connection state information
WO2022057487A1 (zh) 路径标识的分配方法、***、装置、设备以及存储介质

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: 13844911

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2013844911

Country of ref document: EP