WO2017211162A1 - 一种纵向堆叠环境接口扩展设备自动连接方法和装置 - Google Patents

一种纵向堆叠环境接口扩展设备自动连接方法和装置 Download PDF

Info

Publication number
WO2017211162A1
WO2017211162A1 PCT/CN2017/084298 CN2017084298W WO2017211162A1 WO 2017211162 A1 WO2017211162 A1 WO 2017211162A1 CN 2017084298 W CN2017084298 W CN 2017084298W WO 2017211162 A1 WO2017211162 A1 WO 2017211162A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
module
configuration information
packet
information
Prior art date
Application number
PCT/CN2017/084298
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 中兴通讯股份有限公司
Publication of WO2017211162A1 publication Critical patent/WO2017211162A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/20—Support for services
    • H04L49/201—Multicast operation; Broadcast operation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for automatically connecting a vertical stack environment interface expansion device.
  • the 802.1BR standard defines the operation, interaction protocols, management objects, and algorithms of the extension bridge:
  • An expansion bridge system including a control bridge and one or more interface expansion devices;
  • CB device Control Bridge
  • PE interface extension devices
  • a CB device Under the virtual bridge interface extension standard vertical stacking environment (hereinafter referred to as vertical stacking), a CB device may need to be connected to many PE devices, but only manual configuration is required on the CB device. However, if manual configuration is adopted, it takes a huge amount of time. Human and material resources have no practical significance. Therefore, in order to facilitate the management of PE devices, zero deployment of PE devices is required. The core of the zero-distribution of the PE device is the plug-and-play of the PE. In the vertical stacking environment, the PE device does not need to be configured through any command line interface or the NMS to implement self-starting and normal service operations.
  • the traditional zero-deployment method generally pre-creates a fixed configuration file on the server according to the fixed networking, and then the switch downloads the configuration file to the server through FTP (File Transfer Protocol).
  • FTP File Transfer Protocol
  • the link between the CB device and the PE device is not fixed.
  • the PE device needs dynamic discovery to detect the link and dynamically load the link configuration. Therefore, the traditional zero deployment method cannot be used.
  • PE equipment In order to achieve zero deployment of PE equipment, PE equipment needs to be automatically configured without any special configuration at the factory. Do not stack environments vertically, and PE devices can dynamically sense configuration information for automatic updates or automatic connections.
  • An automatic connection method for an interface expansion device in a vertical stacking environment is provided by the embodiment of the present disclosure.
  • the main technical problem is that the interface expansion device cannot implement zero deployment in a vertical stack environment.
  • an embodiment of the present disclosure provides a method for automatically connecting an interface expansion device in a vertical stacking environment, including:
  • the link takes effect.
  • the embodiment of the present disclosure further provides an automatic operation method of an interface expansion device in a vertical stacking environment, including:
  • the link is in communication with the interface extension device, the communication including a timed broadcast message and a response to the interface extension device request.
  • the embodiment of the present disclosure further provides a vertical stack environment interface expansion device, including:
  • a receiving module configured to receive a message that controls a bridge broadcast
  • a parsing module configured to parse the packet to obtain parsed content
  • a determining module configured to determine whether the parsed content is consistent with local information
  • connection module configured to make the link take effect when the determination result is consistent
  • a communication module configured to communicate with the control bridge.
  • the embodiment of the present disclosure further provides an automatic control bridge for the vertical stack environment interface expansion device, including:
  • a generating module configured to generate a packet, where the packet includes interface extension device configuration information and link information;
  • a sending module configured to periodically send the packet.
  • a communication module configured to communicate with the interface expansion device.
  • An embodiment of the present disclosure further provides an apparatus for automatically operating an interface expansion device in a vertical stacking environment, the apparatus comprising: a processor; a memory storing instructions executable by the processor; wherein the processor is configured to execute as The method of any of the preceding claims.
  • Embodiments of the present disclosure also provide a storage medium storing a computer program that, when executed by a processor of a computer, causes the computer to perform the method of any of the above.
  • the interface expansion device can automatically update the device configuration and dynamically load the link by comparing the configuration information sent by the control bridge with the local configuration information. Implement zero deployment of interface expansion devices.
  • FIG. 1 is a flowchart of a method for automatically connecting a PE device in a vertical stacking environment according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a method for automatically connecting PE devices in a vertical stacking environment according to Embodiment 2 of the present disclosure
  • FIG. 3 is a schematic diagram of a device of a PE device according to Embodiment 3 of the present disclosure.
  • FIG. 4 is a schematic diagram of a device of a fourth CB device according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of a PE device automatic connection system in a vertical stacking environment according to Embodiment 5 of the present disclosure
  • FIG. 6 is a schematic diagram of a basic format of an LLDP TLV packet according to Embodiment 1 of the present disclosure
  • FIG. 7 is a schematic diagram of a basic format of a LLDP nearest bridge PDU TLV packet according to Embodiment 1 of the present disclosure.
  • FIG. 8 is a schematic diagram of a format of a private TLV Value value according to Embodiment 2 of the present disclosure.
  • FIG. 9 is a schematic diagram of exemplary information of a private TLV Value value in Embodiment 2 of the present disclosure.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • This embodiment is a method for automatically connecting PE devices in a vertical stacking environment. See Figure 1, including:
  • Step 101 The CB device generates a packet.
  • the packet contains configuration information or version information or other information of the PE device, and may also be a combination of multiple types of information. If there are multiple PE devices, the message is generated by connecting multiple PE device information.
  • Step 102 The CB device periodically broadcasts the packet.
  • the CB device sends all the connected devices to the set interface to send packets at a certain frequency, but only the PE device can recognize the received packets.
  • a port is a port on a CB device that connects devices and devices.
  • Step 103 The PE device receives the packet.
  • the PE device can recognize that the PE device has identified the vertical stacking environment.
  • Step 104 The PE device parses the packet.
  • the PE device analyzes the packet and extracts information about the device.
  • Step 105 it is determined whether the parsed content and the device local information are consistent, if they are consistent, then go to step 106, if not, then go to step 107;
  • the PE device compares the information in the packet with the local information.
  • Step 106 Make the link take effect
  • the link takes effect.
  • the PE device determines the LACP (Link Dynamic Convergence Protocol) uplink port and loads the port configuration.
  • the link between the CB device and the PE device is the uplink of the PE device.
  • the uplink in this embodiment is exemplified by the link that the PE device connects to the CB device under the LACP protocol.
  • Step 107 Send a request to the CB device.
  • the purpose of sending a request to the CB device is to reacquire the latest PE device configuration information content.
  • Step 108 The CB device sends new configuration information of the device to the PE device.
  • the CB device sends the latest configuration information to the PE device in response to the request of the PE device.
  • Step 109 The PE device generates a new configuration file.
  • the PE device writes the obtained configuration information to the configuration file to generate a new configuration file.
  • Step 110 The PE device restarts the device to update the configuration.
  • the PE device has updated the configuration at this time, and then parses the received packet with the local information. If they are consistent, the link can take effect.
  • the packet in the embodiment of the present disclosure adopts the LLDP nearest bridge PDU (data layer link discovery protocol nearest bridge proxy protocol data unit) TLV (type/length/value, type/length/value) basic format
  • FIG. 6 is the LLDP TLV report.
  • TLV header TLV header
  • TLV type TLV type
  • TLV information string TLV information string
  • TLV information string length The length of the TLV information string.
  • FIG. 7 is a schematic diagram of a basic format of adding a private content to an LLDP nearest bridge PDU TLV packet (hereinafter referred to as a private TLV) in a vertical stacking environment, and the private content is configuration information about the PE device that is set to implement the solution of the embodiment of the present disclosure. among them:
  • OUI Organizationally unique identifier
  • Subtype subtype
  • the above link is a link under the link dynamic convergence protocol
  • the private TLV is a message under the data layer link discovery protocol. If the solution of the embodiment of the present disclosure is applied to another scenario or another protocol, other settings for the link or corresponding changes to the form and content of the message should also be considered as belonging to the protection scope of the present disclosure. .
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the CB device can encrypt the packets. After receiving the packets, the PE device performs the decryption check before parsing the packets. To determine that the message was sent by the CB device.
  • the encryption operation uses a HASH (Hash) encryption algorithm. See Figure 2 for an exemplary process, including:
  • Step 201 The CB device generates a private TLV.
  • Step 202 The CB device encrypts the private TLV.
  • the CB device encrypts the content of the private TLV.
  • the PE device type and the version compiling time are encrypted by using a first hash algorithm to form a first hash value and a first random number.
  • the first random number and the first hash value perform a first operation to obtain a calculated value.
  • the CB device then populates the private according to the set message format. TLV, and carry the calculated value obtained by encryption.
  • Step 203 The CB device periodically broadcasts an encrypted private TLV.
  • Step 204 the PE device receives the encrypted private TLV
  • Step 205 the PE device decrypts and verifies the private TLV
  • the PE device performs the decryption check on the content of the private TLV.
  • the PE device extracts the calculated value from the private TLV, and uses the inverse operation of the previous operation to obtain the first hash value and the first random number. Then extracting the PE device type and version compiling time in the private TLV, encrypting by using the first hash algorithm, obtaining the second hash value and the second random number; comparing the second hash value with the second random number and the first hash The hash value and the first random number.
  • Step 206 Determine whether the verification is performed by decryption
  • step 207 If the comparison results are inconsistent, the decryption check is not passed, and the process proceeds to step 207. If the comparison results are consistent, the decryption check is performed, and the process proceeds to step 208.
  • Step 207 discarding the private TLV
  • Step 208 parsing the private TLV
  • Step 209 it is determined whether the parsed content is consistent with the device local information; if they are consistent, go to step 210; if not, go to step 211;
  • Step 210 Enable the uplink to take effect
  • Step 211 Send a request to the CB device.
  • Step 212 The CB device sends new configuration information of the device to the PE device.
  • Step 213 The PE device generates a new configuration file.
  • step 214 the PE device restarts the device to update the configuration; go to step 204.
  • FIG. 8 is a schematic diagram of a format of a private TLV Value value in the embodiment, where:
  • TYPE type; in different embodiments, it may also be a device ID (identity);
  • FLAG tag, used by the CB device to mark whether the version number of the PE device is changed.
  • VERINFO version information; in this embodiment, the version compiling time, version number, and version name of the PE device may be other information of the PE device in different embodiments;
  • RADOM Shield, used to separate TLVs from different devices.
  • FIG. 9 is a schematic diagram of exemplary information of a private TLV Value value in the embodiment, where:
  • 0x01 the PE device type
  • 0x00 indicates that the version number of the PE device has not changed.
  • Hash the value obtained by hashing the encryption
  • 20151110957, V3.02.20B13, and MSXP.SET are the version compile time, version number, and version name of the PE device, respectively.
  • the hash algorithm used by the CB device and the PE device for encryption is consistent.
  • the hash algorithm and the first operation and the inverse operation thereof can be set by the technician to increase the difficulty of the encryption method. , reducing the possibility of being attacked.
  • the encryption methods used include, but are not limited to, hash encryption.
  • the method for automatically connecting a PE device in a vertical stacking environment is provided by the embodiment of the present disclosure.
  • the PE device After the CB device encrypts the private TLV and then broadcasts, the PE device decrypts and checks each received private TLV. After the decryption check is passed, the private TLV is verified. The private TLV is parsed by the CB device to avoid forged similar packet attacks and improve security.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • FIG. 3 A schematic diagram of a PE device that automatically operates in a vertical stacking environment PE device is described in conjunction with FIG. 3, and further descriptions of each module and function are provided below, including:
  • the receiving module 301 is configured to receive a message broadcast by the CB device.
  • the decryption check module 302 is configured to decrypt the check and encrypt the message when the received message is an encrypted message, and verify the identity of the sender of the message;
  • the parsing module 303 is configured to parse the packet to obtain the parsed content, and parse the decrypted packet when the packet is the encrypted packet.
  • the determining module 304 is configured to determine whether the parsed content is consistent with the local information
  • the configuration module 305 is configured to regenerate the configuration file when the judgment result is inconsistent, and restart the device to update the configuration.
  • connection module 306 is configured to make the link take effect when the determination result is consistent
  • the communication module 307 is configured to communicate with the CB device; and includes sending a request to the CB device.
  • the modules in the above embodiments of the present disclosure may be increased or decreased according to actual application conditions.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • FIG. 4 A schematic diagram of a CB device device that automatically operates in a vertical stacking environment PE device will be described with reference to FIG. 4, and further descriptions of each module and function are provided below, including:
  • the generating module 401 is configured to generate a packet, where the packet includes configuration information and link information of the interface extension device.
  • the cryptographic module 402 is configured to extract the content of the packet and encrypt the packet to form an encrypted packet, where the content of the packet includes configuration information of the PE device.
  • the sending module 403 is configured to send a packet periodically; when the packet is an encrypted packet, the encrypted packet is periodically sent;
  • the communication module 404 is configured to communicate with the PE device; and includes responding to the PE device request.
  • the modules in the above embodiments of the present disclosure may be increased or decreased according to actual application conditions.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • FIG. 5 is a schematic diagram of a system configuration of an expansion bridge system, and is also a schematic diagram of an automatic operation system of a PE device in a vertical stacking environment, including a CB device and one or more PE devices.
  • the PE device device adopts the device described in the third embodiment
  • the CB device device adopts the device described in the fourth embodiment, and adopts the automatic operation method in the second embodiment of the present disclosure, and the PE device automatically runs in the vertical stacking environment to realize the zero deployment of the PE device. .
  • An embodiment of the present disclosure further provides an apparatus for automatically operating an interface expansion device in a vertical stacking environment, the apparatus comprising: a processor; a memory storing instructions executable by the processor; wherein the processor is configured to execute as The method of any of the preceding claims.
  • Embodiments of the present disclosure also provide a storage medium storing a computer program that, when executed by a processor of a computer, causes the computer to perform the method of any of the above.
  • the automatic connection method and device for the interface expansion device in the vertical stacking environment provided by the embodiment of the present disclosure can be used in the CB device or the PE device.
  • the PE device can automatically compare the configuration information sent by the CB device with the local configuration information. Update the device configuration, dynamically load the link, and implement zero deployment of the PE device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开实施例提供一种纵向堆叠环境接口扩展设备自动连接方法和装置，接口扩展设备通过比较控制网桥发送的配置信息和自身本地的配置信息，可自动更新设备配置，动态加载链路，实现接口扩展设备零部署。

Description

一种纵向堆叠环境接口扩展设备自动连接方法和装置 技术领域
本公开涉及通信技术领域，尤其是一种纵向堆叠环境接口扩展设备自动连接方法和装置。
背景技术
当前数据中心的快速发展，虚拟化通过提高处理器的使用效率，进一步降低成本。而随着云计算的发展，虚拟机的猛增，企业的数据中心产生了一些管理的难题，网络技术及管理的发展必须适应新的虚拟化技术趋势。因此IEEE组织针对数据中心虚拟机迁移等新技术提出了一系列新的802.1标准，包括802.1Qau(拥塞通告)、802.1Qaz(增强型传输选择)、802.1Qbb(基于优先级的流控)、802.1Qbg(边缘虚拟桥)、802.1BR(虚拟桥接口扩展)等。
802.1BR标准定义了扩展桥的操作、交互协议、管理对象和算法：
1)定义了一个tag(标签)，支持E-C ID(虚拟通道标识)以实现扩展桥上接口间的流量区分和隔离；
2)建立了一个扩展桥系统，包括控制网桥和一个或多个接口扩展设备；
3)定义了接口扩展设备的附属对桥构成元素和系统的要求；
4)将桥接口的MAC(介质访问控制)服务扩展延伸到桥接口扩展设备，并支持用户VLAN(虚拟局域网)；
5)定义了接口扩展设备CSP(客户端服务器)协议，通过控制网桥配置、监控桥接口扩展设备；
6)定义了桥管理的需求、管理对象和管理操作，建立了一个扩展桥系统，包括控制网桥(Control Bridge,下文简称CB设备)和一个或多个接口扩展设备(Port Extender,下文简称PE设备)。
在虚拟桥接口扩展标准纵向堆叠环境(下文简称纵向堆叠)下，一台CB设备可能需要挂接很多PE设备，而只有在CB设备上才有手工配置，但是若采用手工配置，需要耗费巨大的人力物力资源，没有实际意义。所以为了便于管理PE设备，需要实现PE设备的零部署。PE设备零部署的核心是PE的即插即用，即纵向堆叠环境中，PE设备不需要通过任何命令行界面或网管去配置，就可实现自启动和业务正常运行的目的。传统零部署的方法，一般是先在服务器上根据固定组网预创建固定的配置文件，然后交换机通过FTP(文件传输协议)等方式到服务器下载配置文件。但是对于纵向堆叠场景，CB设备和PE设备之间的链路不固定，PE设备需要动态发现才能感知链路，动态加载链路配置，因此无法使用传统的零部署方法。
为了实现PE设备零部署，需要PE设备在出厂时不做任何特殊配置，就能够自动识 别纵向堆叠环境，并且PE设备能够动态感知配置信息以实现自动更新或自动连接。
发明内容
本公开实施例提供的一种纵向堆叠环境下接口扩展设备自动连接方法，主要解决的技术问题是在纵向堆叠环境下，接口扩展设备无法实现零部署。
为解决上述技术问题，本公开实施例提供一种在纵向堆叠环境下接口扩展设备自动连接方法，包括：
接收控制网桥广播的报文，所述报文包括接口扩展设备配置信息和链路信息；
解析所述报文；
若所述解析的扩展设备配置信息与本地信息一致，则使链路生效。
本公开实施例还提供一种纵向堆叠环境下接口扩展设备自动运行方法，包括：
定时向所有连接设备广播报文，所述报文包括接口扩展设备配置信息和链路信息；
在所述链路与所述接口扩展设备通信，所述通信包括定时广播报文和响应所述接口扩展设备请求。
本公开实施例还提供一种纵向堆叠环境接口扩展设备，包括：
接收模块，用于接收控制网桥广播的报文；
解析模块，用于解析所述报文，获得解析内容；
判断模块，用于判断所述解析内容与本地信息是否一致；
连接模块，用于在所述判断结果一致时使链路生效；
通信模块，用于与所述控制网桥通信。
本公开实施例还提供一种纵向堆叠环境接口扩展设备自动的控制网桥，包括：
生成模块，用于生成报文，所述报文包括接口扩展设备配置信息和链路信息；
发送模块，用于定时发送所述报文。
通信模块，用于与所述接口扩展设备进行通信。
本公开实施例还提供一种纵向堆叠环境下接口扩展设备自动运行装置，所述装置包括：处理器；存储器，存储有可由所述处理器执行的指令；其中所述处理器被配置为执行如上任一项所述的方法。
本公开实施例还提供一种存储有计算机程序的存储介质，所述计算机程序在由计算机的处理器运行时，使所述计算机执行如上任一项所述的方法。
本公开的有益效果是：
根据本公开实施例提供的纵向堆叠环境下接口扩展设备自动连接方法和装置，接口扩展设备通过比较控制网桥发送的配置信息和自身本地的配置信息，可自动更新设备配置，动态加载链路，实现接口扩展设备零部署。
附图说明
图1为本公开实施例一纵向堆叠环境下PE设备自动连接方法的流程图；
图2为本公开实施例二纵向堆叠环境下PE设备自动连接方法的流程图；
图3为本公开实施例三PE设备装置示意图；
图4为本公开实施例四CB设备装置示意图；
图5为本公开实施例五纵向堆叠环境下PE设备自动连接系统示意图；
图6为本公开实施例一中LLDP TLV报文基本格式示意图；
图7为本公开实施例一中LLDP nearest bridge PDU TLV报文基本格式示意图；
图8为本公开实施例二中私有TLV Value值的格式示意图；
图9为本公开实施例二中私有TLV Value值的示例性信息示意图。
具体实施方式
下面通过具体实施方式结合附图对本公开实施例作进一步详细说明。
实施例一：
为了实现PE设备零部署，需要PE设备自动识别纵向堆叠环境，并且PE设备能够动态感知配置信息以实现自动更新和自动连接，本实施例为纵向堆叠环境下PE设备自动连接方法，示例性流程请参见图1，包括：
步骤101，CB设备生成报文；
报文中包含PE设备的配置信息或者版本信息或者其他信息，也可以是多种信息的组合。若PE设备是多个，那么这个报文是多个PE设备信息连接起来生成的。
步骤102，CB设备定时广播报文；
CB设备给集连口所有连接的设备以一定频率发送报文，但只有PE设备可以识别接收报文。集连口指CB设备上连接设备、装置的端口。
步骤103，PE设备接收报文；
PE设备接收报文即可认为PE设备已识别纵向堆叠环境。
步骤104，PE设备解析报文；
PE设备分析报文，从中提取涉及本设备的信息。
步骤105，判断解析的内容与设备本地信息是否一致，若一致，则转至步骤106，若不一致，则转至步骤107；
PE设备将报文中的信息和本地信息作比较。
步骤106，使链路生效；
链路生效指PE设备确定LACP(链路动态汇聚协议)上行链路端口，并加载端口配置。CB设备与PE设备的链路即为PE设备的上行链路。本实施例中上行链路示例性为PE设备在LACP协议下连接CB设备的链路。
步骤107，向CB设备发送请求；
向CB设备发送请求的目的是为了重新获取最新PE设备配置信息内容。
步骤108，CB设备向PE设备发送该设备新的配置信息；
CB设备响应PE设备的请求，将最新配置信息发送给该PE设备。
步骤109，PE设备生成新的配置文件；
PE设备将获取的配置信息写入配置文件，生成新的配置文件。
步骤110，PE设备重启设备以更新配置；
然后转至步骤103；
PE设备此时已经更新了配置，再解析接收到的报文与本地信息比较，若一致，就可以使链路生效。
本公开实施例中的报文采用LLDP nearest bridge PDU(数据层链路发现协议最近桥代理协议数据单元)TLV(type/length/value,类型/长度/值)基本格式，图6为LLDP TLV报文基本格式示意图。其中：
TLV header：TLV标头；
TLV type：TLV类型；
TLV information string：TLV信息字符串；
TLV information string length：TLV信息字符串长度。
图7是纵向堆叠环境下，LLDP nearest bridge PDU TLV报文(下文简称私有TLV)添加私有内容的基本格式示意图，私有内容为实现本公开实施例方案而设置的有关PE设备的配置信息。其中：
OUI(Organizationally unique identifier)：组织唯一标识符；
Subtype：子类型；
Value：值。
显然，本领域的技术人员应该明白，上述链路是在链路动态汇聚协议下的链路，上述私有TLV是在数据层链路发现协议下的报文。若将本公开实施例的方案应用于别的场景或别的协议下时，对链路有其他设定或对报文的形式和内容进行相应改变，也都应当视为属于本公开的保护范围。
实施例二：
为了防止伪造的报文对PE设备形成攻击，影响正常使用和运行，CB设备可以对报文进行加密操作，相应的，PE设备接收到报文后、在解析报文内容前要进行解密校验，以确定该报文是CB设备发送的。本实施例中，加密操作采用HASH(哈希)加密算法。示例性流程请参见图2，包括：
步骤201，CB设备生成私有TLV；
步骤202，CB设备加密私有TLV；
CB设备将私有TLV的内容进行加密，在本实施例中示例性为将PE设备类型、版本编译时间采用第一哈希算法进行加密，形成第一哈希值和第一随机数，将所述第一随机数与第一哈希值进行第一运算得到计算值。然后CB设备按照设定的报文格式填充私有 TLV，并携带加密得出的计算值。
步骤203，CB设备定时广播加密私有TLV；
步骤204，PE设备接收加密私有TLV；
步骤205，PE设备解密校验私有TLV；
PE设备将私有TLV的内容进行解密校验，在本实施例中示例性为PE设备从私有TLV中提取出计算值，采用之前第一运算的逆运算得到第一哈希值和第一随机数；然后提取私有TLV中PE设备类型、版本编译时间，采用第一哈希算法进行加密，得到第二哈希值和第二随机数；比较第二哈希值与第二随机数与第一哈希值及第一随机数。
步骤206，判断是否通过解密校验；
若比较结果不一致，则未通过解密校验，转至步骤207；若比较结果一致，则通过所述解密校验，转至步骤208。
步骤207，丢弃该私有TLV；
步骤208，解析该私有TLV；
步骤209，判断解析的内容与设备本地信息是否一致；若一致，则转至步骤210；若不一致，则转至步骤211；
步骤210，使上行链路生效；
步骤211，向CB设备发送请求；
步骤212，CB设备向PE设备发送该设备的新的配置信息；
步骤213，PE设备生成新的配置文件；
步骤214，PE设备重启设备以更新配置；转至步骤204。
图8为本实施例中的私有TLV Value值的格式示意图，其中：
TYPE：类型；在不同的实施例中，也可以是设备ID(身份标识)；
FLAG：标记，CB设备用来标记这个PE设备的版本号是否改变；
VERINFO：版本信息；在本实施例中为该PE设备的版本编译时间、版本号、版本名称，在不同的实施例中，也可以是PE设备的其他信息；
RADOM：屏蔽，用于分隔不同设备的TLV。
图9为本实施例中的私有TLV Value值的示例性信息示意图，其中：
0x01：该PE设备类型；
0x00：表示该PE设备的版本号没有改变；
hash：哈希加密得到的值；
20151110957、V3.02.20B13、MSXP.SET分别为该PE设备的版本编译时间、版本号、版本名称。
本公开实施例中CB设备和PE设备进行加密时候使用的哈希算法是一致的，这里的哈希算法和第一运算及其逆运算可以由技术人员自行设定规则，增大加密方法破解难度，降低受到攻击的可能。同时，使用的加密方法包括但是不局限于哈希加密。
本公开实施例提供的纵向堆叠环境下PE设备自动连接方法，CB设备加密私有TLV后再广播，PE设备解密校验每一次接收到的私有TLV，解密校验通过后，验证这个私有TLV是由CB设备发送的，再解析这个私有TLV，避免伪造的相似报文攻击，提高安全性。
显然，本领域的技术人员应该明白，上述本公开实施例为了验证私有TLV报文是否由CB设备发送的而进行的加密过程和解密校验是相对应的。为此所采用的加密及解密方法都应当视为属于本公开的保护范围。
实施例三：
结合图3说明在纵向堆叠环境PE设备自动运行的PE设备装置示意图，下面对各模块及功能进行进一步说明，包括：
接收模块301，用于接收CB设备广播的报文；
解密校验模块302，用于在接收的报文为加密报文时，解密校验加密报文，验证报文发送方身份；
解析模块303，用于解析报文，获得解析内容；当报文为加密报文时，解析解密校验后的报文；
判断模块304，用于判断解析内容与本地信息是否一致；
配置模块305，用于在判断结果为不一致时，重新生成配置文件，重启设备以更新配置；
连接模块306，用于在判断结果一致时使链路生效；
通信模块307，用于与CB设备通信；包括向CB设备发送请求。
上述本公开实施例中的各模块可以根据实际应用情况进行增加或减少。
实施例四：
结合图4说明在纵向堆叠环境PE设备自动运行的CB设备装置示意图，下面对各模块及功能进行进一步说明，包括：
生成模块401，用于生成报文，报文包括接口扩展设备的配置信息和链路信息；
加密模块402，用于提取报文内容进行加密形成加密报文，报文内容包括PE设备配置信息；
发送模块403，用于定时发送报文；当报文为加密报文时，定时发送加密报文；
通信模块404，用于与PE设备进行通信；包括响应PE设备请求。
上述本公开实施例中的各模块可以根据实际应用情况进行增加或减少。
实施例五：
结合图5说明一个扩展桥系统的系统组成，同时也是本公开实施例在纵向堆叠环境PE设备自动运行系统的示意图，包括CB设备和一个或多个PE设备。PE设备装置采用实施例三描述的装置，CB设备装置采用实施例四描述的装置，采用本公开实施例二中的自动运行方法，PE设备在纵向堆叠环境下的自动运行，实现PE设备零部署。
本公开实施例还提供一种纵向堆叠环境下接口扩展设备自动运行装置，所述装置包括：处理器；存储器，存储有可由所述处理器执行的指令；其中所述处理器被配置为执行如上任一项所述的方法。
本公开实施例还提供一种存储有计算机程序的存储介质，所述计算机程序在由计算机的处理器运行时，使所述计算机执行如上任一项所述的方法。
以上内容是结合具体的实施方式对本公开实施例所作的进一步详细说明，不能认定本公开的具体实施只局限于这些说明。对于本公开所属技术领域的普通技术人员来说，在不脱离本公开构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本公开的保护范围。
工业实用性
本公开实施例提供的纵向堆叠环境下接口扩展设备自动连接方法和装置，可相应的用于CB设备或PE设备中，PE设备通过比较CB设备发送的配置信息和自身本地的配置信息，可自动更新设备配置，动态加载链路，实现PE设备零部署。

Claims (12)

  1. 一种纵向堆叠环境接口扩展设备自动运行方法，包括：
    接收控制网桥广播的报文，所述报文包括接口扩展设备配置信息和链路信息；
    解析所述报文；
    若所述解析的扩展设备配置信息与本地信息一致，则使链路生效。
  2. 如权利要求1所述的纵向堆叠环境接口扩展设备自动运行方法，其中：
    若所述解析的扩展设备配置信息与本地信息不一致，则向控制网桥发送请求，重新获取配置信息；
    将所述配置信息写入配置文件；
    重启设备以更新配置。
  3. 如权利要求1所述的纵向堆叠环境接口扩展设备自动运行方法，其中，当所述报文为加密报文时，接口扩展设备对所述加密报文进行解密验证并解析。
  4. 一种纵向堆叠环境接口扩展设备自动运行方法，包括：
    定时向所有连接设备广播报文，所述报文包括接口扩展设备配置信息和链路信息；
    在所述链路与所述接口扩展设备通信，所述通信包括定时广播报文和响应所述接口扩展设备请求。
  5. 如权利要求4所述的纵向堆叠环境接口扩展设备自动运行方法，其中，提取所述报文内容进行加密形成加密报文并广播，所述报文内容包括所述接口扩展设备配置信息。
  6. 一种纵向堆叠环境接口扩展设备，包括：
    接收模块，设置为接收控制网桥广播的报文；
    解析模块，设置为解析所述报文，获得解析内容；
    判断模块，设置为判断所述解析内容与本地信息是否一致；
    连接模块，设置为在所述判断结果一致时使链路生效；
    通信模块，设置为与所述控制网桥通信。
  7. 如权利要求6所述的纵向堆叠环境接口扩展设备自动运行装置，其中，还包括：
    配置模块，设置为在所述判断结果不一致时，重新生成配置文件，重启设备以更新配置。
  8. 如权利要求6所述的纵向堆叠环境接口扩展设备自动运行装置，其中，还包括：
    解密校验模块，设置为在所述报文为加密报文时，解密校验所述加密报文，验证所述报文发送方身份。
  9. 一种纵向堆叠环境接口扩展设备自动运行的控制网桥，包括：
    生成模块，设置为生成报文，所述报文包括接口扩展设备配置信息和链路信息；
    发送模块，设置为定时发送所述报文。
    通信模块，设置为与所述接口扩展设备进行通信。
  10. 如权利要求9所述的控制网桥，其中，还包括：
    加密模块，设置为提取所述报文内容进行加密形成加密报文，所述报文内容包括所述接口扩展设备配置信息；
    所述发送模块，设置为定时发送所述加密报文。
  11. 一种纵向堆叠环境接口扩展设备自动运行装置，包括：
    处理器；
    存储器，存储有可由所述处理器执行的指令；
    其中所述处理器被配置为执行如权利要求1-5任一项所述的方法。
  12. 一种存储有计算机程序的存储介质，所述计算机程序在由计算机的处理器运行时，使所述计算机执行如权利要求1-5任一项所述的方法。
PCT/CN2017/084298 2016-06-07 2017-05-15 一种纵向堆叠环境接口扩展设备自动连接方法和装置 WO2017211162A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610404026.1A CN107483366B (zh) 2016-06-07 2016-06-07 一种纵向堆叠环境接口扩展设备自动连接方法和装置
CN201610404026.1 2016-06-07

Publications (1)

Publication Number Publication Date
WO2017211162A1 true WO2017211162A1 (zh) 2017-12-14

Family

ID=60578353

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/084298 WO2017211162A1 (zh) 2016-06-07 2017-05-15 一种纵向堆叠环境接口扩展设备自动连接方法和装置

Country Status (2)

Country Link
CN (1) CN107483366B (zh)
WO (1) WO2017211162A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112532756B (zh) * 2019-09-17 2023-10-24 华为技术有限公司 接口扩展方法、装置和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102769558A (zh) * 2011-05-06 2012-11-07 中兴通讯股份有限公司 获知端口扩展拓扑信息的方法、系统和控制桥
US20140269710A1 (en) * 2013-03-12 2014-09-18 Dell Products L.P. Port extender
CN104427012A (zh) * 2013-09-04 2015-03-18 杭州华三通信技术有限公司 端口协商方法和设备
CN104683130A (zh) * 2013-11-28 2015-06-03 华为技术有限公司 一种配置堆叠端口的方法和设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100466659C (zh) * 2004-07-13 2009-03-04 华为技术有限公司 一种自动配置终端设备的方法
CN101232409B (zh) * 2008-02-20 2014-04-30 中兴通讯股份有限公司 不对称数字用户线路终端设备的配置方法
CN101888573B (zh) * 2009-05-15 2013-03-20 中兴通讯股份有限公司 一种自动发现相邻节点间资源状态的方法和系统
CN102387042B (zh) * 2011-11-22 2014-03-12 华为技术有限公司 自动配置的方法和系统以及网络节点
CN103220373B (zh) * 2012-01-19 2018-05-04 中兴通讯股份有限公司 一种分布式逻辑地址与物理地址互换方法、装置及设备
CN104618147B (zh) * 2015-01-06 2018-04-06 新华三技术有限公司 一种纵向堆叠系统管理方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102769558A (zh) * 2011-05-06 2012-11-07 中兴通讯股份有限公司 获知端口扩展拓扑信息的方法、系统和控制桥
US20140269710A1 (en) * 2013-03-12 2014-09-18 Dell Products L.P. Port extender
CN104427012A (zh) * 2013-09-04 2015-03-18 杭州华三通信技术有限公司 端口协商方法和设备
CN104683130A (zh) * 2013-11-28 2015-06-03 华为技术有限公司 一种配置堆叠端口的方法和设备

Also Published As

Publication number Publication date
CN107483366A (zh) 2017-12-15
CN107483366B (zh) 2021-11-05

Similar Documents

Publication Publication Date Title
CN110996318B (zh) 一种变电站智能巡检机器人安全通信接入系统
US9917845B2 (en) Link discovery method and apparatus
CN107005569B (zh) 端对端服务层认证
CN104811444B (zh) 一种安全的云端控制方法
US9516061B2 (en) Smart virtual private network
CN104780069B (zh) 一种面向sdn网络的控制层与数据层通信通道自配置方法及其系统
US20140189357A1 (en) Encryption and authentication based network management method and apparatus
US10554689B2 (en) Secure communication session resumption in a service function chain
WO2011032321A1 (zh) 一种数据转发方法、数据处理方法、系统以及相关设备
Whitehurst et al. Exploring security in ZigBee networks
CN106209401B (zh) 一种传输方法及装置
WO2019237576A1 (zh) 校验虚拟机通信性能的方法及装置
US20210168614A1 (en) Data Transmission Method and Device
US10243741B2 (en) Key exchange and mutual authentication in low performance devices
CN113037684B (zh) VxLan隧道认证方法、装置和系统及网关
WO2017211162A1 (zh) 一种纵向堆叠环境接口扩展设备自动连接方法和装置
US11831622B2 (en) Security for distributed networking
CN101388796B (zh) 信息发送处理方法、通信设备与通信系统
CN102970134A (zh) 将硬件密码设备的算法用于pkcs#7数据封装的方法及系统
CN115499177A (zh) 云桌面访问方法、零信任网关、云桌面客户端和服务端
Gu et al. Enhancing Security and Scalability in Software Defined LTE Core Networks
CN107295015B (zh) 一种交通信号机通信方法
Song et al. Name-signature lookup system: A security enhancement to named data networking
WO2023071712A1 (zh) 一种安全通信方法和相关设备
WO2023024540A1 (zh) 处理报文、获取sa信息的方法、装置、系统及介质

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17809601

Country of ref document: EP

Kind code of ref document: A1