WO2019019991A1 - 聚合组的创建 - Google Patents

聚合组的创建 Download PDF

Info

Publication number
WO2019019991A1
WO2019019991A1 PCT/CN2018/096754 CN2018096754W WO2019019991A1 WO 2019019991 A1 WO2019019991 A1 WO 2019019991A1 CN 2018096754 W CN2018096754 W CN 2018096754W WO 2019019991 A1 WO2019019991 A1 WO 2019019991A1
Authority
WO
WIPO (PCT)
Prior art keywords
aggregation group
port
identifier
unique identifier
packet
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2018/096754
Other languages
English (en)
French (fr)
Inventor
徐志辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Technologies Co Ltd
Original Assignee
New H3C Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Priority to US16/633,564 priority Critical patent/US11050661B2/en
Priority to JP2020503807A priority patent/JP6842599B2/ja
Publication of WO2019019991A1 publication Critical patent/WO2019019991A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
    • 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
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • 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/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5069—Address allocation for group communication, multicast communication or broadcast communication
    • 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
    • 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

  • IRF Intelligent Resilient Framework
  • CB Controlling Bridge
  • the CB device To improve the link stability between the CB device and the PE device, you can connect multiple links between the CB device and the PE device.
  • the multiple links form an aggregation link and transmit packets through the aggregation link.
  • you need to manually create an aggregation group and manually add ports to the aggregation group the workload is large, especially when the CB device is connected to a large number of PE devices.
  • FIG. 1 is a schematic diagram of an application scenario in an implementation manner of the present application.
  • FIG. 2 is a flowchart of a method for creating an aggregation group in an embodiment of the present application.
  • 2A is a schematic flowchart of a method for creating an aggregation group in an implementation manner of the present application.
  • FIG. 3 is a structural diagram of an apparatus for creating an aggregation group in an embodiment of the present application.
  • FIG. 4 is a hardware structural diagram of a CB device in an embodiment of the present application.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present application.
  • second information may also be referred to as the first information.
  • word “if” may be interpreted to mean “at time” or "when” or "in response to determination.”
  • the embodiment of the present application provides a method for creating an aggregation group, which can be applied to a system including a CB device and a PE device.
  • two or more links may be connected between the CB device and the PE device.
  • two links will be taken as an example for description.
  • FIG. 1 the application scenario of the embodiment of the present application is shown.
  • the CB device 10 and the PE device 11 are connected by two links, and the CB device 10 and the PE device 12 are also connected by two links.
  • the port 101 of the CB device 10 is connected to the port 111 of the PE device 11, the port 103 of the CB device 10 is connected to the port 112 of the PE device 11, the port 102 of the CB device 10 is connected to the port 121 of the PE device 12, and the CB device 10 is connected.
  • the port 104 is connected to the port 122 of the PE device 12.
  • FIG. 2 is a flowchart of a method for creating an aggregation group according to an embodiment of the present application. The method may be applied to a CB device, and the method may include the following steps:
  • Step 201 The CB device receives the packet sent by the PE device through the first port, and parses the unique identifier of the PE device from the packet.
  • the packet may include, but is not limited to, an LLDP (Link Layer Discovery Protocol) packet.
  • the CB device when receiving a packet through the first port, can parse the device type field from the packet.
  • the device type field is a preset value
  • the CB device can determine that the packet received by the first port is a packet sent by the PE device, so that the subsequent steps can be performed.
  • the CB device may determine that the packet received through the first port is not a packet sent by the PE device, so that the processing procedure may be ended.
  • the LLDP packet can carry the device type field and the unique identifier field.
  • the LLDP packet can also carry other fields.
  • the other content carried in the LLDP packet is not limited.
  • the PE device can send an LLDP packet to the CB device.
  • the device type field carried in the LLDP packet is a preset value
  • the type of the device that sends the LLDP packet is a PE device.
  • the unique identifier field carried in the LLDP packet is a unique identifier of the PE device.
  • the CB device can also send LLDP packets to the PE device. In this case, the device type field carried in the LLDP packet will not be the preset value.
  • the value that is not the preset value may be referred to as a first value, where the first value indicates that the device type is a CB device, and the unique identifier field carried by the LLDP packet is the CB device. Uniquely identifies.
  • the device type field may be a CPP (Cascade Port Priority) field.
  • the value of the CPP field may range from 0 to 255.
  • one or more values of 0-255 may be used as a preset value to indicate that the device type is a PE device, and the preset value is not included.
  • the other values are the first values to indicate that the device type is a CB device. For example, 255 can be used as the preset value, and 0-254 is used as the first value.
  • the CB device when the CB device receives the LLDP packet through the first port, if the device type field of the LLDP packet is 255, the LLDP packet is sent by the PE device, that is, the CB device passes the first The port receives the LLDP packet sent by the PE. If the device type field of the LLDP packet is any value in the range of 0 to 254, the LLDP packet is sent by the CB device. That is, the CB device receives the LLDP packet sent by the other CB device through the first port. .
  • the unique identifier field may be an Address field, and is used to carry a unique identifier of the device, and the unique identifier may include, but is not limited to, a MAC (Media Access Control) address of the device. Based on this, when the CB device receives the LLDP packet sent by the PE device through the first port, the CB device can parse the MAC address of the PE device from the unique identifier field.
  • MAC Media Access Control
  • Step 202 If the first port is not in the aggregation group, the CB device queries the array table. If the unique identifier of the PE device exists in the array table, step 203 may be performed; if the unique identifier of the PE device does not exist in the array table, step 204 may be performed.
  • the CB device can create an array table for recording the correspondence between the aggregation group identifier and the unique identifier of the PE device.
  • Table 1 shows an example of an array table. As shown in Table 1, the initial state of the array table is empty. In the subsequent process, the CB device adds the aggregation group identifier and the unique identifier of the PE device to the array table.
  • Aggregation group ID Unique identifier of the PE device ... ...
  • the CB device parses the unique identifier of the PE device from the packet, and then determines whether the first port is in the aggregation group. If the first port is in the aggregation group (referred to as the second aggregation group), the second aggregation group identifier of the second aggregation group is used to query the array table; if the PE device corresponding to the second aggregation group identifier is recorded in the array table.
  • the unique identifier of the PE device that is parsed out from the packet is different from the unique identifier of the PE device that is parsed from the packet, and the unique identifier of the PE device corresponding to the second aggregation group identifier is updated in the array table to be the unique identifier of the PE device that is parsed from the packet.
  • the processing flow can be ended; if the unique identifier of the PE device corresponding to the second aggregation group identifier recorded in the array table is the same as the unique identifier of the PE device parsed from the packet, the processing flow can be ended. If the first port is not in the aggregation group, the array table may be queried by using the unique identifier of the PE device parsed from the packet.
  • Step 203 If the unique identifier of the PE device exists in the array table, the CB device obtains the aggregation group identifier corresponding to the unique identifier of the PE device from the array table (recorded as the third aggregation group identifier), and adds the first port. Go to the third aggregation group corresponding to the third aggregation group identifier. In this way, the first port can be successfully added to the aggregation group.
  • the array table is used to record the correspondence between the identifier of the aggregation group and the unique identifier of the PE device. Therefore, when the unique identifier of the PE device exists in the array table, the CB device can obtain the unique identifier from the array table.
  • the aggregation group ID and add the first port to the aggregation group corresponding to the aggregation group ID.
  • Step 204 If the unique identifier of the PE device does not exist in the array table, the CB device selects an idle (that is, not used) aggregation group identifier (recorded as the first aggregation group identifier), and creates a corresponding identifier corresponding to the first aggregation group identifier.
  • the first aggregation group is added to the created first aggregation group, and the correspondence between the first aggregation group identifier and the unique identifier of the PE device parsed in step 202 is recorded in the array table. .
  • the CB device may also select an idle (ie, unused) PE number and assign the selected PE number to the PE device.
  • the PE number is used as the frame number of the PE device, and is the identifier of the PE device managed by the CB device. Then, the CB device can also record the correspondence between the selected PE number and the first aggregation group identifier.
  • first aggregation group, the first aggregation group identifier, the second aggregation group, the second aggregation group identifier, the third aggregation group, and the third aggregation group identifier are only distinguished for convenience of description.
  • the first aggregation group, the second aggregation group, and the third aggregation group may be the same aggregation group or different aggregation groups.
  • the CB device can create an aggregation group for each PE device, including: creating an aggregation group for the PE device, assigning an aggregation group identifier to the aggregation group, adding a port to the aggregation group, and corresponding to the aggregation group.
  • the PE device assigns a PE number.
  • an aggregation group ID to an aggregation group
  • the aggregation group identifier is marked as a non-idle aggregation group identifier, and the aggregation group identifier is no longer assigned to other aggregation groups.
  • PE number 100-PE number 128 You can configure multiple PE numbers on the CB device, such as PE number 100-PE number 128. In the initial state, these PE numbers are idle. When a PE number is assigned to a PE device, the PE number is marked as a non-idle PE number, and the PE number is no longer assigned to other PE devices.
  • Step a1 When the CB device receives the packet (LLDP packet) through the first port, the device class field is parsed from the packet.
  • step a2 When the device type field is a preset value, step a2 is performed; when the device type field is not a preset value, it is determined that the packet sent by the non-PE device is received through the first port, and the process ends.
  • the CB device determines that the packet sent by the PE device is received by the first port, and the unique identifier of the PE device, such as the MAC address of the PE device, is parsed from the unique identifier field of the packet.
  • Step a3 The CB device determines whether the first port is in an aggregation group.
  • step a4 can be performed, and if not, step a6 can be performed.
  • Step a4 The CB device queries the array table by using the aggregation group identifier of the aggregation group, and determines whether the unique identifier of the PE device corresponding to the array table in the array table is the same as the unique identifier of the PE device carried in the packet. If yes, the process can be ended, and if not, step a5 can be performed.
  • Step a5 The CB device updates the unique identifier of the PE device corresponding to the aggregation group identifier in the array table to the unique identifier of the PE device carried in the packet. After step a5, the flow can be ended.
  • Step a6 The CB device queries the array table by using the unique identifier of the PE device, and determines whether the unique identifier exists in the array table. If yes, go to step a7; if no, go to step a8.
  • Step a7 The CB device obtains the aggregation group identifier corresponding to the unique identifier of the PE device from the array table, and adds the first port to the aggregation group corresponding to the aggregation group identifier, and then ends the process.
  • Step a8 The CB device selects an idle aggregation group identifier, creates an aggregation group corresponding to the selected aggregation group identifier, and adds the first port to the created aggregation group. Then, step a9 is performed.
  • step a9 the CB device records the correspondence between the aggregation group identifier and the unique identifier in the array table.
  • Step a10 The CB device selects an idle PE number and assigns the PE number to the PE device.
  • Step a11 The CB device records the correspondence between the PE number and the aggregation group identifier, and ends the process.
  • the CB device can automatically create an aggregation group, assign an idle aggregation group identifier to the aggregation group, and add the port connected to the PE device to the aggregation group instead of manually creating an aggregation group.
  • the port is manually added to the aggregation group. Therefore, the workload of the manual configuration can be reduced. In particular, when the CB device is connected to a large number of PE devices, the workload of the user can be significantly reduced.
  • the CB device can quickly create an aggregation group. To achieve automatic deployment of PE devices.
  • the PE device can also automatically assign a PE number to the PE device, so that the PE device can automatically go online.
  • the PE device 11 sends an LLDP packet through the port 111.
  • the LLDP packet carries the MAC address A of the PE device 11.
  • the CB device 10 queries the array table by the MAC address A. Since the MAC address A does not exist in the array table, the CB device 10 selects an idle aggregation group identifier, such as the aggregation group identifier 1, and creates an aggregation group corresponding to the aggregation group identifier 1 (hereinafter referred to as aggregation group 1).
  • the CB device 10 adds the port 101 to the aggregation group 1, and records the correspondence between the aggregation group identifier 1 and the MAC address A in the array table, as shown in Table 2. Then, the CB device 10 selects the free PE number, such as the PE number 100, and assigns the PE number 100 to the PE device 11, and records the correspondence between the PE number 100 and the aggregation group identifier 1.
  • Aggregation group identifier Unique identifier of the PE device Aggregation group ID 1 MAC address A ... ...
  • the PE device 11 sends an LLDP packet through the port 112.
  • the LLDP packet carries the MAC address A of the PE device 11.
  • the CB device 10 queries the array table by the MAC address A. Since the MAC address A exists in the array table, the CB device 10 obtains the aggregation group identifier 1 corresponding to the MAC address A from the array table, and adds the port 103 to the aggregation group 1 corresponding to the aggregation group identifier 1.
  • the CB device 10 automatically completes the aggregation of the port 101 and the port 103.
  • the CB device 10 creates the aggregation group 1, assigns the aggregation group identifier 1 to the aggregation group 1, adds the port 101 and port 103 to the aggregation group 1, and adds the PE number. 100 is assigned to the PE device 11 corresponding to the aggregation group 1.
  • the CB device 10 After the CB device 10 receives the new LLDP packet through the port 101 or the port 103 again, the CB device 10 will not start to create the new LLDP packet because the port 101/port 103 is already in the aggregation group. Update the operation of the aggregation group.
  • the CB device 10 can create the aggregation group 2, assign the aggregation group identifier 2 to the aggregation group 2, add the port 102 and the port 104 to the aggregation group 2, and assign the PE number 101 to the PE corresponding to the aggregation group 2.
  • the embodiment of the present application further provides an apparatus for creating an aggregation group, which is applied to a CB device.
  • a CB device As shown in FIG. 3, which is a structural diagram of the device, the device includes the following modules.
  • the receiving module 301 is configured to receive, by using the first port, a packet sent by the PE device.
  • the parsing module 302 is configured to parse the unique identifier of the PE device from the packet.
  • the querying module 303 is configured to query an array table when the first port is not in an aggregation group
  • the processing module 304 is configured to: when the unique identifier of the PE device does not exist in the array table, select an idle first aggregation group identifier, and create a first aggregation group corresponding to the first aggregation group identifier, where The first port is added to the first aggregation group, and the corresponding relationship between the first aggregation group identifier and the unique identifier of the PE device is recorded in an array table.
  • the receiving module 301 is specifically configured to: when receiving a packet by using the first port, parsing the device type field from the packet, and determining that the device type field is a preset value
  • the packet received by the port is a packet sent by the PE device.
  • the query module 303 is further configured to query the array table when the first port is in the second aggregation group.
  • the processing module 304 is further configured to: when the second aggregation group identifier of the second aggregation group recorded in the array table, the unique identifier of the PE device and the parsing from the packet When the unique identifiers of the PE devices are different, the unique identifier of the PE device corresponding to the second aggregation group identifier is updated in the array table to be the unique identifier of the PE device parsed from the packet.
  • the processing module 304 is further configured to: if the unique identifier of the PE device exists in the array table, obtain a third aggregation corresponding to the unique identifier of the PE device from the array table. And the first port is added to the third aggregation group corresponding to the third aggregation group identifier.
  • the processing module 304 is further configured to: after creating the first aggregation group, select an idle PE number, assign the PE number to the PE device, and record the PE number and Corresponding relationship of the first aggregation group identifier.
  • the packet includes an LLDP packet, and the unique identifier includes a MAC address of the PE device.
  • FIG. 4 For the CB device provided in the embodiment of the present application, a hardware architecture diagram can be specifically shown in FIG. 4 .
  • a machine readable storage medium 410 and a processor 420 are included, wherein:
  • Machine-readable storage medium 410 stores instruction code.
  • the processor 420 communicates with the machine readable storage medium 410, reads and executes the instruction code stored in the machine readable storage medium 410, and implements the creation operation of the aggregation group disclosed in the above example of the present application.
  • machine-readable storage medium 410 can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and so forth.
  • a machine-readable storage medium can be a volatile memory, a non-volatile memory, or similar storage medium.
  • the machine-readable storage medium 410 may be a RAM (Radom Access Memory), a flash memory, a storage drive (such as a hard disk drive), a solid state drive, any type of storage disk (such as a compact disc, a DVD, etc.) or The combination.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, and a game control.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the application can take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware.
  • embodiments of the present application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • these computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the instruction means implements the functions specified in one or more blocks of the flowchart or in a flow or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

CB设备在通过第一端口接收PE设备发送的报文时，从所述报文解析出所述PE设备的唯一标识。若所述第一端口没有在聚合组中，则查询数组表。若所述数组表中不存在所述PE设备的唯一标识，则选取空闲的第一聚合组标识，创建与所述第一聚合组标识对应的第一聚合组，将所述第一端口添加到所述第一聚合组中，并在所述数组表中记录所述第一聚合组标识与所述PE设备的唯一标识的对应关系。

Description

聚合组的创建
相关申请的交叉引用
本专利申请要求于2017年7月24日提交的、申请号为201710607814.5、发明名称为“一种聚合组的创建方法和装置”的中国专利申请的优先权，该申请的全文以引用的方式并入本文中。
背景技术
IRF(Intelligent Resilient Framework，智能弹性架构)是一种纵向网络整合虚拟化技术，可以用于集合多台设备的硬件资源和软件处理能力，以实现多台设备的协同工作、统一管理和不间断维护。IRF可以将多个PE(Port Extender，端口扩展器)设备连接到CB(Controlling Bridge，控制桥)设备，并将每个PE设备虚拟化成CB设备的一块远程业务板，以由CB设备统一管理所述多个PE设备。
为了提高CB设备和PE设备之间的链路稳定性，可以在CB设备和PE设备之间连接多条链路，这多条链路组成聚合链路，通过聚合链路传输报文。为了实现对聚合链路的管理，用户需要在CB设备上，手工为PE设备创建聚合组，并将与这个PE设备连接的端口添加到该聚合组。但是，由于需要用户手工创建聚合组，并手工在该聚合组中添加端口，工作量较大，尤其是当CB设备与大量PE设备连接时。
附图说明
图1是本申请一种实施方式中的应用场景示意图。
图2是本申请一种实施方式中的聚合组的创建方法的流程图。
图2A是本申请一种实施方式中的聚合组的创建方法的示意性流程图。
图3是本申请一种实施方式中的聚合组的创建装置的结构图。
图4是本申请一种实施方式中的CB设备的硬件结构图。
具体实施方式
在本申请实施例使用的术语仅仅是出于描述特定实施例的目的，而非限制本申请。 本申请和权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其它含义。还应当理解，本文中使用的术语“和/或”是指包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，此外，所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
本申请实施例提出一种聚合组的创建方法，可以应用于包括CB设备和PE设备的系统。为了提高CB设备和PE设备之间的链路稳定性，可以在CB设备和PE设备之间连接两个或者两个以上的链路。以下，为了方便描述，以两个链路为例进行说明。如图1所示，为本申请实施例的应用场景示意图，CB设备10和PE设备11之间通过两个链路连接，CB设备10和PE设备12之间也通过两个链路连接。其中，CB设备10的端口101与PE设备11的端口111连接，CB设备10的端口103与PE设备11的端口112连接，CB设备10的端口102与PE设备12的端口121连接，CB设备10的端口104与PE设备12的端口122连接。
图2为本申请实施例中提出的聚合组的创建方法的流程图，该方法可以应用于CB设备，该方法可以包括以下步骤：
步骤201，CB设备通过第一端口接收PE设备发送的报文，从所述报文中解析出所述PE设备的唯一标识。其中，该报文可以包括但不限于：LLDP(Link Layer Discovery Protocol，链路层发现协议)报文。
在一个例子中，CB设备在通过第一端口接收到报文时，可以从该报文中解析出设备类型字段。当该设备类型字段为预设数值时，CB设备可确定通过该第一端口接收到的报文是PE设备发送的报文，从而可以执行后续步骤。并且，当该设备类型字段不是预设数值时，CB设备可确定通过该第一端口接收到的报文不是PE设备发送的报文，从而可以结束处理流程。
以下结合LLDP报文对上述过程进行说明。在LLDP报文中，可以携带设备类型字段、唯一标识字段，当然，LLDP报文也可以携带其它字段。在本发明实施例中，对LLDP报文携带的其他内容不做限制。
例如，当PE设备和CB设备连接时，则PE设备可以向CB设备发送LLDP报文。假设，该LLDP报文携带的设备类型字段为预设数值，则表示发送该LLDP报文的设备的类型是PE设备。并且，该LLDP报文携带的唯一标识字段为该PE设备的唯一标识。此外，CB设备也可以向PE设备发送LLDP报文。在这种情况下，该LLDP报文携带的设备类型字段将不是上述预设数值。为了与上述预设数值进行区分，可以将该不是上述预设数值的数值称为第一数值，该第一数值表示设备类型是CB设备，该LLDP报文携带的唯一标识字段为该CB设备的唯一标识。
其中，上述设备类型字段可以为CPP(Cascade Port Priority，级联端口优先级)字段。在一示例中，该CPP字段的取值范围可以是0-255。为了通过CPP字段区分出报文的发送设备是PE设备还是CB设备，可以将0-255中的一个或者多个数值作为预设数值，以表示设备类型是PE设备，而预设数值之外的其它数值均为第一数值，以表示设备类型是CB设备。例如，可以将255作为预设数值，而将0-254均作为第一数值。
基于此，CB设备在通过第一端口接收到LLDP报文时，若该LLDP报文的设备类型字段为255，则说明这个LLDP报文是PE设备发送的，也就是说，CB设备通过第一端口接收到PE设备发送的LLDP报文。若该LLDP报文的设备类型字段为0-254中的任意数值，则说明这个LLDP报文是CB设备发送的，也就是说，CB设备通过第一端口接收到其它CB设备发送的LLDP报文。
其中，唯一标识字段可以为Address(地址)字段，用于携带设备的唯一标识，该唯一标识可以包括但不限于设备的MAC(Media Access Control，介质访问控制)地址。基于此，CB设备在通过第一端口接收到PE设备发送的LLDP报文时，可以从唯一标识字段解析出PE设备的MAC地址。
步骤202，若该第一端口没有在聚合组中，则CB设备查询数组表。若该数组表中存在所述PE设备的唯一标识，则可以执行步骤203；若该数组表中不存在所述PE设备的唯一标识，则可以执行步骤204。
在一个例子中，CB设备可以建立数组表，该数组表用于记录聚合组标识与PE设备的唯一标识之间的对应关系。表1所示为数组表的示例。如表1所示，数组表的初始状态为空。后续过程中，CB设备会将聚合组标识与PE设备的唯一标识添加到数组表中。
表1
聚合组标识 PE设备的唯一标识
... ...
在一个例子中，CB设备在通过第一端口接收到PE设备发送的报文后，从报文中解析出PE设备的唯一标识，然后判断第一端口是否在聚合组中。若该第一端口在聚合组(记为第二聚合组)中，则通过第二聚合组的第二聚合组标识查询数组表；若数组表中记录的与第二聚合组标识对应的PE设备的唯一标识与从报文解析出的PE设备的唯一标识不同，则在数组表中将与第二聚合组标识对应的PE设备的唯一标识更新为从该报文解析出的PE设备的唯一标识，并可以结束处理流程；若该数组表中记录的与第二聚合组标识对应的PE设备的唯一标识与从报文解析出的PE设备的唯一标识相同，则可以结束处理流程。若该第一端口没有在聚合组中，则可以通过从报文解析出的PE设备的唯一标识查询数组表。
步骤203，若该数组表中存在PE设备的唯一标识，则CB设备从数组表中获取PE设备的唯一标识对应的聚合组标识(记为第三聚合组标识)，并将该第一端口添加到该第三聚合组标识对应的第三聚合组中。这样，可以成功将第一端口添加到聚合组。
其中，由于数组表用于记录聚合组标识与PE设备的唯一标识之间的对应关系，因此，在数组表中存在PE设备的唯一标识时，CB设备可以从数组表中获取到该唯一标识对应的聚合组标识，并将该第一端口添加到该聚合组标识对应的聚合组中。
步骤204，若该数组表中不存在PE设备的唯一标识，则CB设备选取空闲(即未被使用)的聚合组标识(记为第一聚合组标识)，并创建与第一聚合组标识对应的第一聚合组，并将该第一端口添加到创建的第一聚合组中，在数组表中记录该第一聚合组标识与步骤202中解析出的PE设备的唯一标识之间的对应关系。
在一个例子中，在创建第一聚合组之后，CB设备还可以选取空闲(即未被使用)的PE编号，并将该选取的PE编号分配给该PE设备。其中，该PE编号作为PE设备的框槽号，是CB设备管理这个PE设备的标识。然后，CB设备还可以记录该选取的PE编号与该第一聚合组标识之间的对应关系。
需要说明的是，上述记载的第一聚合组、第一聚合组标识、第二聚合组、第二聚合 组标识、第三聚合组、第三聚合组标识，仅仅是为了描述方便所作的区分，并非指示为不同的聚合组，实际上，第一聚合组、第二聚合组、第三聚合组可以为相同的聚合组也可以为不同的聚合组。
在一个例子中，CB设备可以为每个PE设备创建聚合组，包括：为PE设备创建聚合组，为该聚合组分配聚合组标识，在该聚合组中添加端口，并为该聚合组对应的PE设备分配PE编号。
为了实现“为聚合组分配聚合组标识”，可以在CB设备配置多个聚合组标识，如聚合组标识1-聚合组标识1024，在初始状态下，这些聚合组标识都是空闲的聚合组标识，当某个聚合组标识被分配给聚合组时，将该聚合组标识标记为非空闲的聚合组标识，且这个聚合组标识不再分配给其它聚合组。
为了实现“选取空闲的PE编号，并将该PE编号分配给PE设备”，可以在CB设备配置多个PE编号，如PE编号100-PE编号128，在初始状态下，这些PE编号都是空闲的PE编号，当某个PE编号被分配给PE设备时，将该PE编号标记为非空闲的PE编号，且这个PE编号不再分配给其它PE设备。
以下结合一个具体的实施例，对上述聚合组的创建方法进行详细说明。聚合组的创建过程可如图2A所示包括：
步骤a1、CB设备通过第一端口接收到报文(LLDP报文)时，从报文中解析出设备类型字段。设备类型字段为预设数值时，执行步骤a2；设备类型字段不是预设数值时，确定通过第一端口接收到非PE设备发送的报文，结束流程。
步骤a2、CB设备确定通过该第一端口接收到PE设备发送的报文，并从该报文的唯一标识字段解析出PE设备的唯一标识，如PE设备的MAC地址。
步骤a3、CB设备判断该第一端口是否在聚合组中。
如果是，则可以执行步骤a4，如果否，则可以执行步骤a6。
步骤a4、CB设备通过该聚合组的聚合组标识查询数组表，并判断该聚合组标识在数组表对应的PE设备的唯一标识与该报文携带的PE设备的唯一标识是否相同。如果是，则可以结束流程，如果否，则可以执行步骤a5。
步骤a5、CB设备将该聚合组标识在数组表对应的PE设备的唯一标识更新为该报文携带的PE设备的唯一标识。在步骤a5之后，可以结束流程。
步骤a6、CB设备通过PE设备的唯一标识查询数组表，并判断该数组表是否存在该唯一标识。如果是，则执行步骤a7；如果否，则执行步骤a8。
步骤a7、CB设备从数组表中获取该PE设备的唯一标识对应的聚合组标识，并将该第一端口添加到该聚合组标识对应的聚合组中，然后结束流程。
步骤a8、CB设备选取空闲的聚合组标识，并创建与选取的聚合组标识对应的聚合组，并将该第一端口添加到创建的聚合组中，然后，执行步骤a9。
步骤a9、CB设备在数组表中记录该聚合组标识与该唯一标识的对应关系。
步骤a10、CB设备选取空闲的PE编号，并将该PE编号分配给该PE设备。
步骤a11、CB设备记录该PE编号与该聚合组标识的对应关系，结束流程。
基于上述技术方案，本申请实施例中，CB设备可以自动创建聚合组，为聚合组分配空闲的聚合组标识，并将与PE设备连接的端口添加到聚合组中，而不用用户手工创建聚合组，并手工在聚合组中添加端口，因此可以减少用户手动配置的工作量，尤其是，当CB设备与大量PE设备连接时，可以显著减少用户的大量工作量，CB设备可以快速的创建聚合组，实现PE设备的自动部署。CB设备还可以自动为PE设备分配PE编号，使得PE设备能够自动上线。
以下结合图1所示的应用场景，对上述聚合组的创建方法进行详细说明。
假设，PE设备11通过端口111发送LLDP报文，该LLDP报文携带PE设备11的MAC地址A，CB设备10在通过端口101接收到该LLDP报文后，由于端口101没有在聚合组中，因此，CB设备10通过MAC地址A查询数组表。由于数组表中不存在MAC地址A，因此CB设备10选取空闲的聚合组标识、如聚合组标识1，并创建与聚合组标识1对应的聚合组(后续将其称为聚合组1)。然后，CB设备10将端口101添加到聚合组1中，并在数组表中记录聚合组标识1与MAC地址A之间的对应关系，如表2所示。然后，CB设备10选取空闲的PE编号、如PE编号100，将PE编号100分配给PE设备11，并记录PE编号100与聚合组标识1之间的对应关系。
表2
聚合组标识 PE设备的唯一标识
聚合组标识1 MAC地址A
... ...
接着，PE设备11通过端口112发送LLDP报文，该LLDP报文携带PE设备11的MAC地址A，CB设备10在通过端口103接收到该LLDP报文后，由于端口103没有在聚合组中，因此，CB设备10通过MAC地址A查询数组表。由于数组表中存在该MAC地址A，因此，CB设备10从数组表中获取MAC地址A对应的聚合组标识1，并将端口103添加到聚合组标识1对应的聚合组1中。
至此，CB设备10自动完成了端口101和端口103的聚合，CB设备10创建聚合组1，为聚合组1分配聚合组标识1，将端口101和端口103添加到聚合组1，并将PE编号100分配给聚合组1对应的PE设备11。此后，若CB设备10再次通过端口101或端口103接收到新的LLDP报文后，由于端口101/端口103已在聚合组中，则CB设备10将不启动基于该新的LLDP报文创建、更新聚合组的操作。
同理，CB设备10在通过端口102/端口104接收到LLDP报文时，其处理流程与上述处理过程类似，在此不再赘述。最终，CB设备10可以创建聚合组2，为聚合组2分配聚合组标识2，并将端口102和端口104添加到该聚合组2中，并将PE编号101分配给该聚合组2对应的PE设备12。
基于与上述方法同样的申请构思，本申请实施例还提出一种聚合组的创建装置，应用于CB设备。如图3所示，为所述装置的结构图，所述装置包括如下模块。
接收模块301，用于通过第一端口接收PE设备发送的报文；
解析模块302，用于从所述报文中解析出所述PE设备的唯一标识；
查询模块303，用于当所述第一端口没有在聚合组时，查询数组表；
处理模块304，用于当所述数组表中不存在所述PE设备的唯一标识时，则选取空闲的第一聚合组标识，创建与所述第一聚合组标识对应的第一聚合组，将所述第一端口添加到所述第一聚合组中，并在数组表中记录所述第一聚合组标识与所述PE设备的唯一标识的对应关系。
所述接收模块301，具体用于：在通过第一端口接收到报文时，从所述报文中解析出设备类型字段，并在所述设备类型字段为预设数值的情况下确定通过第一端口接收到的所述报文为PE设备发送的报文。
所述查询模块303，还用于：当所述第一端口在第二聚合组时查询所述数组表。在这种情况下，所述处理模块304，还用于：当所述数组表中记录的所述第二聚合组的第二聚合组标识对应的PE设备的唯一标识与从所述报文解析出的PE设备的唯一标识不 同时，在所述数组表中将该第二聚合组标识对应的PE设备的唯一标识更新为从所述报文解析出的PE设备的唯一标识。
在一个例子中，所述处理模块304还用于：若所述数组表中存在所述PE设备的唯一标识，则从所述数组表中获取与所述PE设备的唯一标识对应的第三聚合组标识，并将所述第一端口添加到所述第三聚合组标识对应的第三聚合组中。
在一个例子中，所述处理模块304，还用于：在创建所述第一聚合组后，选取空闲的PE编号，将所述PE编号分配给所述PE设备，并记录所述PE编号与所述第一聚合组标识的对应关系。
所述报文包括LLDP报文，所述唯一标识包括所述PE设备的MAC地址。
本申请实施例中提供的CB设备，从硬件层面而言，硬件架构示意图具体可以参见图4所示。包括：机器可读存储介质410和处理器420，其中：
机器可读存储介质410：存储指令代码。
处理器420：与机器可读存储介质410通信，读取和执行机器可读存储介质410中存储的所述指令代码，实现本申请上述示例公开的聚合组的创建操作。
这里，机器可读存储介质410可以是任何电子、磁性、光学或其它物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，机器可读存储介质可以是易失存储器、非易失性存储器或者类似的存储介质。具体地，机器可读存储介质410可以是RAM(Radom Access Memory，随机存取存储器)、闪存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、DVD等)或者它们的组合。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本申请时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面 的实施例的形式。而且，本申请实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可以由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其它可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其它可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
而且，这些计算机程序指令也可以存储在能引导计算机或其它可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或者多个流程和/或方框图一个方框或者多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其它可编程数据处理设备上，使得在计算机或者其它可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其它可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (13)

  1. 一种聚合组的创建方法，包括：
    控制桥CB设备通过第一端口接收端口扩展器PE设备发送的报文；
    所述CB设备从所述报文中解析出所述PE设备的唯一标识；
    若所述第一端口没有在聚合组中，所述CB设备查询数组表；
    若所述数组表中不存在所述PE设备的唯一标识，则所述CB设备选取空闲的第一聚合组标识；
    所述CB设备创建与所述第一聚合组标识对应的第一聚合组，将所述第一端口添加到所述第一聚合组中，并在所述数组表中记录所述第一聚合组标识与所述PE设备的唯一标识的对应关系。
  2. 根据权利要求1所述的方法，其特征在于，所述通过第一端口接收PE设备发送的报文，包括：
    所述CB设备通过所述第一端口接收报文；
    所述CB设备从所述报文中解析出设备类型字段；
    所述设备类型字段为预设数值时，所述CB设备确定通过所述第一端口接收到的所述报文发送自PE设备。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    若所述第一端口在第二聚合组中，则所述CB设备查询所述数组表；
    若所述数组表中记录的所述第二聚合组的第二聚合组标识对应的PE设备的唯一标识与从所述报文解析出的PE设备的唯一标识不同，则所述CB设备在所述数组表中将所述第二聚合组标识对应的PE设备的唯一标识更新为从所述报文解析出的PE设备的唯一标识。
  4. 根据权利要求1所述的方法，其特征在于，该方法还包括：
    若所述数组表中存在所述PE设备的唯一标识，则所述CB设备从所述数组表中获取与所述PE设备的唯一标识对应的第三聚合组标识；
    所述CB设备将所述第一端口添加到所述第三聚合组标识对应的第三聚合组中。
  5. 根据权利要求1所述的方法，其特征在于，
    所述创建与所述第一聚合组标识对应的所述第一聚合组之后，所述方法还包括：
    选取空闲的PE编号，并将所述PE编号分配给所述PE设备；
    记录所述PE编号与所述第一聚合组标识的对应关系。
  6. 根据权利要求1所述的方法，其特征在于，
    所述报文包括链路层发现协议LLDP报文，
    所述唯一标识包括所述PE设备的媒体接入控制MAC地址。
  7. 一种聚合组的创建装置，应用于控制桥CB设备，该装置包括：
    接收模块，用于通过所述CB设备的第一端口接收端口扩展器PE设备发送的报文；
    解析模块，用于从所述报文中解析出所述PE设备的唯一标识；
    查询模块，用于若所述第一端口没有在聚合组中，则查询数组表；
    处理模块，用于若所述数组表中不存在所述PE设备的唯一标识时，则选取空闲的第一聚合组标识，创建与所述第一聚合组标识对应的第一聚合组，将所述第一端口添加到所述第一聚合组中，并在所述数组表中记录所述第一聚合组标识与所述PE设备的唯一标识的对应关系。
  8. 根据权利要求7所述的装置，其特征在于，所述接收模块，具体用于
    通过所述第一端口接收到报文；
    从所述报文中解析出设备类型字段；
    所述设备类型字段为预设数值时，确定通过所述第一端口接收到的所述报文为PE设备发送的报文。
  9. 根据权利要求8所述的装置，其特征在于，
    所述查询模块，还用于：若所述第一端口在第二聚合组中，则查询所述数组表；
    所述处理模块，还用于：若所述数组表中记录的所述第二聚合组的第二聚合组标识对应的PE设备的唯一标识与从所述报文解析出的PE设备的唯一标识不同，则在所述数组表中该将所述第二聚合组标识对应的PE设备的唯一标识更新为从所述报文解析出的PE设备的唯一标识。
  10. 根据权利要求7所述的装置，其特征在于，所述处理模块还用于：
    若所述数组表中存在所述PE设备的唯一标识，则从所述数组表中获取与所述PE设备的唯一标识对应的第三聚合组标识；
    将所述第一端口添加到所述第三聚合组标识对应的第三聚合组中。
  11. 根据权利要求7所述的装置，其特征在于，所述处理模块，还用于
    在创建与所述第一聚合组标识对应的所述第一聚合组之后，选取空闲的PE编号，并将所述PE编号分配给所述PE设备；
    记录所述PE编号与所述第一聚合组标识的对应关系。
  12. 根据权利要求7所述的装置，其特征在于，
    所述报文包括链路层发现协议LLDP报文，
    所述唯一标识包括所述PE设备的MAC地址。
  13. 一种聚合组的创建装置，应用于控制桥CB设备，包括：
    非暂时性机器可读存储介质，存储有机器可执行指令；
    处理器，用于执行所述机器可执行指令，以
    通过所述CB设备的第一端口接收端口扩展器PE设备发送的报文；
    从所述报文中解析出所述PE设备的唯一标识；
    若所述第一端口没有在聚合组中，则查询数组表；
    若所述数组表中不存在所述PE设备的唯一标识，则选取空闲的第一聚合组标识；
    创建与所述第一聚合组标识对应的第一聚合组，将所述第一端口添加到所述第一聚合组中，并在所述数组表中记录所述第一聚合组标识与所述PE设备的唯一标识的对应关系
PCT/CN2018/096754 2017-07-24 2018-07-24 聚合组的创建 Ceased WO2019019991A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/633,564 US11050661B2 (en) 2017-07-24 2018-07-24 Creating an aggregation group
JP2020503807A JP6842599B2 (ja) 2017-07-24 2018-07-24 集約グループの作成

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710607814.5 2017-07-24
CN201710607814.5A CN108418752B (zh) 2017-07-24 2017-07-24 一种聚合组的创建方法和装置

Publications (1)

Publication Number Publication Date
WO2019019991A1 true WO2019019991A1 (zh) 2019-01-31

Family

ID=63125447

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/096754 Ceased WO2019019991A1 (zh) 2017-07-24 2018-07-24 聚合组的创建

Country Status (4)

Country Link
US (1) US11050661B2 (zh)
JP (1) JP6842599B2 (zh)
CN (1) CN108418752B (zh)
WO (1) WO2019019991A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114827016A (zh) * 2022-04-12 2022-07-29 珠海星云智联科技有限公司 切换链路聚合方案的方法、装置、设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111030859B (zh) * 2019-12-10 2022-07-26 苏州浪潮智能科技有限公司 一种端口汇聚的配置方法及装置
CN111614555B (zh) * 2020-04-20 2022-05-03 北京百卓网络技术有限公司 一种业务通道建立方法、装置及设备
US11303504B2 (en) * 2020-06-09 2022-04-12 T-Mobile Usa, Inc. Data link error feedback signaling

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103780480A (zh) * 2012-10-17 2014-05-07 杭州华三通信技术有限公司 报文转发方法和设备
US20160205019A1 (en) * 2013-03-12 2016-07-14 Dell Products, L.P. Port extender
CN105847107A (zh) * 2016-03-31 2016-08-10 杭州华三通信技术有限公司 一种系统以及设置链路聚合组方法和装置
CN105991445A (zh) * 2016-03-31 2016-10-05 杭州华三通信技术有限公司 链路聚合组的设置方法和装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006095508A1 (ja) * 2005-03-08 2006-09-14 Nippon Telegraph And Telephone Corporation フラッディング抑制方法
CN101447872B (zh) 2007-11-27 2011-09-28 阿里巴巴集团控股有限公司 一种用户身份验证方法、系统及验证码生成维护子系统
EP2696538B1 (en) * 2011-05-06 2019-05-29 ZTE Corporation Method, system and controlling bridge for obtaining port extension topology information
US20120287930A1 (en) * 2011-05-13 2012-11-15 Cisco Technology, Inc. Local switching at a fabric extender
US9077650B2 (en) * 2012-05-31 2015-07-07 Broadcom Corporation Multi-homing in an extended bridge
CN103166874B (zh) * 2013-03-25 2016-03-02 杭州华三通信技术有限公司 一种报文转发方法及设备
US10412012B2 (en) 2015-09-22 2019-09-10 Arris Enterprises Llc Intelligent, load adaptive, and self optimizing master node selection in an extended bridge
US10148595B2 (en) 2015-10-16 2018-12-04 Arris Enterprises Llc Handling dynamic port/LAG changes without breaking communication in an extended bridge
EP3439248B1 (en) * 2016-03-31 2020-09-16 New H3C Technologies Co., Ltd. Configuration of link aggregation group
US10250527B2 (en) * 2016-09-01 2019-04-02 Arris Enterprises Llc Port extender ID assignment in an extended bridge

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103780480A (zh) * 2012-10-17 2014-05-07 杭州华三通信技术有限公司 报文转发方法和设备
US20160205019A1 (en) * 2013-03-12 2016-07-14 Dell Products, L.P. Port extender
CN105847107A (zh) * 2016-03-31 2016-08-10 杭州华三通信技术有限公司 一种系统以及设置链路聚合组方法和装置
CN105991445A (zh) * 2016-03-31 2016-10-05 杭州华三通信技术有限公司 链路聚合组的设置方法和装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114827016A (zh) * 2022-04-12 2022-07-29 珠海星云智联科技有限公司 切换链路聚合方案的方法、装置、设备及存储介质
CN114827016B (zh) * 2022-04-12 2023-03-24 珠海星云智联科技有限公司 切换链路聚合方案的方法、装置、设备及存储介质

Also Published As

Publication number Publication date
JP6842599B2 (ja) 2021-03-17
US11050661B2 (en) 2021-06-29
CN108418752B (zh) 2019-11-08
US20200162368A1 (en) 2020-05-21
CN108418752A (zh) 2018-08-17
JP2020528241A (ja) 2020-09-17

Similar Documents

Publication Publication Date Title
US10797988B2 (en) Method and apparatus for controlling and managing a field device using an industry internet operating system
US11546228B2 (en) Zero-touch configuration of network devices using hardware metadata
US8862865B2 (en) Rebooting infiniband clusters
CN110635987B (zh) 一种报文传输方法、装置、设备及机器可读存储介质
WO2019019991A1 (zh) 聚合组的创建
CN107104824B (zh) 一种网络拓扑确定方法和装置
CN109800270B (zh) 一种数据存储和查询的方法及物联网系统
WO2019001480A1 (zh) 虚拟机管理
WO2017186159A1 (zh) 报文传输
WO2020001514A1 (zh) 业务处理
CN114710549A (zh) 一种容器平台中网卡的动态管理方法、系统及业务节点
WO2019037664A1 (zh) 地址分配
CN103563304A (zh) 基于虚拟组网的交换机配置方法及集群管理设备
CN109525621B (zh) 一种基于ZigBee绑定的数据同步方法、设备及系统
CN104777754A (zh) 一种虚拟设备创建方法及装置
CN110708275B (zh) 一种协议报文的处理方法和装置
CN107370818A (zh) 一种分布式会话对象管理方法及系统
US10833990B2 (en) Transmitting packet
CN107547382B (zh) 一种邻居关系发现方法和装置
CN115633013B (zh) 一种地址配置方法、装置、设备及机器可读存储介质
EP3573303B1 (en) Forwarder network-access recognition method, sdn controller, and forwarder
US20120311115A1 (en) Assignment of agent identifier to cloned device
WO2023092504A1 (zh) 订阅控制方法、装置、计算机设备及存储介质
WO2023201587A1 (zh) 设备控制方法、装置、设备及存储介质
CN106028303A (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: 18839127

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020503807

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18839127

Country of ref document: EP

Kind code of ref document: A1