WO2017215446A1

WO2017215446A1 - Configuration information notification method, configuration method and corresponding device for interface expansion apparatus

Info

Publication number: WO2017215446A1
Application number: PCT/CN2017/086721
Authority: WO
Inventors: 黄锦元; 曹淑玲; 王同乐; 郑炎
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-06-13
Filing date: 2017-05-31
Publication date: 2017-12-21
Also published as: CN107493185A; CN107493185B

Abstract

A configuration information notification method, a configuration method and a corresponding device for an interface expansion apparatus. The notification method comprises: by acquiring pre-stored configuration information about an interface expansion apparatus, filling the configuration information and address information about a local end into a private message field of a notification message, and transmitting the notification message to a target interface extension apparatus via a cascade port of a control network bridge apparatus.

Description

Configuration information notification method, configuration method and corresponding device of interface expansion device

Technical field

The present disclosure relates to the field of communications technologies, for example, to a configuration information notification method, a configuration method, and a corresponding device of an interface extension device.

Background technique

With the continuous development of network technology, the amount of data for communication interaction is also increasing, which causes some management problems in the data center of the enterprise. In order to improve the efficiency of the processor through virtualization technology, thereby reducing the management cost, the Institute of Electrical and Electronics Engineers (Institute of Electrical and Electronics Engineers, IEEE) proposed a series of new 802.1 standards for new technologies such as data center virtual machine migration, including: congestion notification 802.1Qau, enhanced transmission selection 802.1Qaz, priority-based flow control 802.1Qbb The edge virtual bridge 802.1Qbg and the virtual bridge interface extend the 802.1BR standard.

The 802.1Qbg standard introduces a Virtual Ethernet Port Aggregator (VEPA). The VEPA device can send all the information to the border bridge, so that the use of the Access Control List (ACL) is no longer used. Depends on where the virtual machine is located. In the 802.1Qbg standard, the VSI Discovery and Configuration Protocol (VDP) can implement the discovery and configuration of the Virtual Switch Interface (VSI); the Channel Discovery and Configuration Protocol (CDCP). Channel discovery and configuration can be achieved; the VEPA protocol can reduce the complexity associated with highly virtualized deployments. The 802.1Qbg standard focuses on the operation between the service equipment and the border bridge, and the physical link channel between the two devices. This method of edge relaying is relatively simple, and there is no need to modify the format of the packet transmitted on the current link, but when multicast or a large amount of information passes through the physical link, each channel will be sent in the 802.1Qbg standard. A copy of the frame results in multiple frames of the same frame in the physical link.

In order to solve the problem that multiple copies of the same frame appear in the 802.1Qbg standard occupy the bandwidth, the 802.1BR standard restricts the channel to only send and copy one frame by adding additional tag information to the message. This reduces the bandwidth usage of multiple identical frame replicas under multicast conditions, which usually requires more hardware resources to support. The 802.1BR standard can deploy a remote switch as a policy-controlled switch in a virtual environment instead of a switch deployed as a neighboring server rack. Through multiple virtual channels, the edge virtual bridge copies the frames to a set of remote ports, using the waterfall. The serial port flexibility allows the network to be designed to more efficiently allocate bandwidth for multicast, broadcast, and unicast frames.

The 802.1BR standard establishes an expansion bridge system, including a Controlling Bridge (CB) and one or more Interface Extenders (PEs). In a vertical stacking environment, a core for zero deployment of PE devices The PE device is plug-and-play, that is, the PE device can be configured directly through the command line interface (CLI) or the NMS. The PE device can be self-starting and normal running. However, because the PE device in the vertical stacking environment is plug-and-play, the connection link between the CB device and the PE device is not fixed. This requires the PE device to dynamically detect the Link Aggregation Control Protocol (LACP). The link member port of the link, and the zero-deployment of the PE device in the vertical stack environment, the PE device needs to know the configuration information of the PE device, such as the storage path of the version file, the compile time and version number of the version. In the related art, the PE device cannot dynamically detect LACP link member ports and PE device configuration information.

Summary of the invention

The disclosure provides a configuration information notification method, a configuration method, and a corresponding device for an interface expansion device, so as to solve the problem that the PE device cannot perceive the configuration information of the PE device in the vertical stack environment, and thus cannot perform zero deployment.

The embodiment provides a method for advertising configuration information of an interface extension device, including:

Acquiring configuration information of the pre-stored interface extension device, where the configuration information includes: a device type, a version number of the device, a version compile time, and a version storage path;

Filling in the private message field of the advertisement message with the configuration information and the address information of the control bridge device;

The advertisement message is sent to the target interface extension device by controlling the cascade port of the bridge device.

The embodiment further provides a method for configuring an interface expansion device, including:

Receiving, by the control bridge device, an advertisement message carrying a private message field, the private message The content of the packet corresponding to the field includes configuration information of the interface extension device and address information of the control bridge device, where the configuration information includes: a device type, a version number of the device, a version compile time, and a version storage path.

And parsing the advertisement packet to obtain configuration information of the interface extension device, and determining whether the interface extension device type in the configuration information is consistent with the device type of the target interface extension device;

If the interface extension device type in the configuration information is consistent with the device type of the target interface extension device, download the version file according to the configuration information and the address information of the control bridge device, and write the configuration information to the target interface extension device. In the configuration file.

The embodiment further provides a configuration information notification device of the interface expansion device, including:

The obtaining module is configured to: obtain configuration information of the pre-stored interface expansion device, where the configuration information includes: a device type, a version number of the device, a version compiling time, and a version storage path;

The processing module is configured to: fill the configuration information and the address information of the control bridge device into the private message field of the advertisement packet;

The sending module is configured to: send the advertisement packet to the target interface extension device by using a cascade port of the control bridge device.

The embodiment further provides an apparatus for configuring an interface expansion device, including:

The receiving module is configured to: receive an advertisement message that is sent by the control bridge device and carries a private message field, where the content of the packet corresponding to the private message field includes configuration information of the interface extension device and an address of the control bridge device. Information, the configuration information includes: a device type, a version number of the device, a version compile time, and a version storage path;

The parsing processing module is configured to: parse the advertisement packet to obtain configuration information of the interface extension device;

a judging module, configured to: disconnect the interface extension device type in the configuration information from the device type of the target interface extension device;

The configuration module is configured to: when the interface extension device type in the configuration information is consistent with the device type of the target interface extension device, download the version file according to the configuration information and the address information of the control bridge device, and write the configuration information. Enter the configuration file of the target interface extension device.

The embodiment further provides a computer readable storage medium, where the computer storage medium stores Computer executable instructions for performing any of the methods described above.

The embodiment also provides an electronic device including one or more processors, a memory, and one or more programs, the one or more programs being stored in the memory when executed by one or more processors When performing any of the above methods.

The embodiment further provides a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer Having the computer perform any of the methods described above.

In this embodiment, the configuration information of the pre-stored interface extension device is obtained, and the configuration information and the address information of the local end are filled in the private packet field of the advertisement packet, and the advertisement packet is sent to the interface extension device through the expansion port. The configuration information of the interface extension device is added to the advertisement packet in the manner of a private packet field, and is sent to the interface extension device, so that the interface extension device can directly parse the corresponding configuration information after receiving the advertisement packet. Thereby, the dynamic awareness of the interface extension device configuration information is realized, thereby achieving zero deployment.

DRAWINGS

1 is a schematic structural diagram of a configuration information notification apparatus of an interface extension device according to a first embodiment;

2 is a schematic flowchart of a method for notifying a configuration information of an interface extension device according to the first embodiment;

3 is a schematic diagram of a basic format of a private message field provided by the first embodiment;

4 is a schematic diagram of a basic format of an LLDP private packet field provided by the first embodiment;

FIG. 5 is a schematic diagram of a LLDP private packet field carrying information format provided by the first embodiment;

FIG. 6 is a schematic diagram of carrying specific information of an LLDP private packet field provided by the first embodiment;

FIG. 7 is a schematic structural diagram of a device for configuring an interface expansion device according to a second embodiment;

FIG. 8 is a schematic flowchart diagram of a method for configuring an interface expansion device according to a second embodiment;

FIG. 9 is a schematic structural diagram of an electronic device according to a second embodiment.

detailed description

The embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which should be understood as described herein. The embodiments are only used to illustrate and explain the present disclosure, and are not intended to limit the present disclosure, and the features of the embodiments and the embodiments of the present disclosure may be combined with each other without conflict.

The configuration information advertisement method, the configuration method, and the corresponding device of the interface extension device provided in this embodiment are filled in the advertisement packet by the CB device, and the private packet field is used. -Iength-value, TLV) adds the configuration information of the PE device, and sends the advertisement packet with the configuration information to the target PE device through the cascade port. After the target PE device receives the advertisement packet, the target PE device The advertisement packet is parsed to obtain the corresponding configuration information, and the PE device type in the configuration information is consistent with the device type of the target PE device. The PE device type in the configuration information is the same as the device type of the target PE device. The target PE device downloads the corresponding version file from the CB device through the File Transfer Protocol (FTP), and writes the parsed configuration information to the configuration file of the target PE device. The problem that the configuration information is dynamically perceived, so that the PE device can be parsed according to the received advertisement packet in the vertical stack environment. Obtaining the configuration information and sensing the member ports of the LACP link, thereby achieving zero deployment. The zero deployment of the PE device can be understood as the PE device detecting the connection link between the PE device and the CB device, and the PE device and the CB device. The corresponding port is used to store the detected port information in the PE device, so that the PE device downloads the version file of the software to be run through the corresponding link. The information about the detected port may include the information of the port that can receive the private TLV message and the port that the CB device sends the private TLV message, and the uplink port of the PE device, that is, the PE device and the CB device. A port that can receive private TLV messages.

First embodiment

Referring to FIG. 1 , FIG. 1 is a schematic structural diagram of a configuration information notification apparatus of an interface expansion device according to an embodiment of the present disclosure. The configuration information notification apparatus may be configured in a CB device. In this embodiment, the configuration information notification apparatus may include: The obtaining module 110, the processing module 120, and the sending module 130, wherein:

The obtaining module 110 is configured to: obtain configuration information of the pre-stored interface extension device, where the configuration information includes: a device type, a version number of the device, a version compile time, and a version storage path.

The processing module 120 is configured to: fill the configuration information and the address information of the control bridge device into the private message field of the advertisement message.

The sending module 130 is configured to: send the advertisement packet to the target interface extension device by using a cascade port of the control bridge device.

The advertisement packet is an advertisement packet carrying the configuration information described above.

Optionally, the processing module 120 is configured to pre-store the configuration information of the interface expansion device in the control bridge device in a configuration file, so that the control bridge device reads the configuration file by Obtaining configuration information of the interface extension device.

In this embodiment, the PE device that receives the advertisement message with the private message field may be referred to as the target PE device. Before the obtaining module 110 obtains the configuration information, the processing module 120 may convert the configuration information of the PE device into the configuration file in advance. And the configuration file is stored on the CB device. When the notification message needs to be sent, the obtaining module 110 obtains the configuration information by reading the configuration file. For example, the processing module 120 stores the configuration information in the flash memory of the CB device. In the flash), the configuration information is converted into a configuration file and stored in the flash. The configuration file may be an Extensible Markup Language (XML) file, and the obtaining module 110 reads the XML corresponding to the configuration file from the flash. The file is parsed, and the configuration of the PE device is obtained, such as the device type of the PE device, the version number of the PE device, the version compile time, and the version storage path.

The version number of the PE device is the version number of the software that the PE device needs to run. The version compile time is the compile time of the software that the PE device needs to run. The version storage path is the directory information that the PE device needs to run to store the software in the CB device. .

Optionally, the processing module 120 is configured to: fill the configuration information and the address information of the control bridge device into the message content corresponding to the private message field of the advertisement packet, and in the private message The header of the text field sets the type of the private message field and the length of the private message field header information.

In this embodiment, after the configuration information is obtained, the processing module 120 is configured to: add a private TLV to the advertisement packet, and the CB device fills the obtained configuration information into the private TLV according to the corresponding format, for example, The processing module 120 fills the configuration information and the address information of the CB device into the content of the packet corresponding to the private TLV of the advertisement packet in a corresponding format, and sets the type and private type of the private message field in the header of the packet field. The length of the header information of the message field.

In this embodiment, the configuration information of each port of the PE device is not fixed. When the configuration information of the PE device is modified, the content corresponding to the configuration file stored in the flash on the CB device may be changed. The obtaining module 110 may obtain the configuration file of the PE device from the flash, and parse the corresponding configuration information from the configuration file, and then re-fill the configuration information into the private TLV of the advertisement packet and send the configuration information to the target PE device. In order to update the configuration information, it is not necessary to change the configuration file on both ends of the PE device and the CB device, so that the content of the configuration file at one end is modified. In this case, the other end automatically performs the corresponding modification of the configuration file according to the sent advertisement packet, thereby realizing the dynamic sensing configuration information of the PE device and implementing zero deployment of the PE device.

For example, if there are multiple PE devices, the user can modify the configuration file of the PE device stored on the CB device, and the CB device can send the notification of the configuration information of the modified PE device. A packet, that is, a private TLV packet, enables the PE device to obtain configuration information of the modified PE device through the configuration of the private TLV packet, and realize zero deployment of multiple PE devices.

On the basis of the configuration information notification device provided in FIG. 1 , the present embodiment further provides a configuration information advertisement method for the interface extension device. As shown in FIG. 2 , the configuration information notification method for the interface extension device is provided in this embodiment. The method can be applied to a CB device and can include steps 202-206.

In step 202, configuration information of the interface expansion device stored in advance is acquired.

The configuration information of the PE device may include information such as the device type, the version number of the device, the version compile time, and the version storage path. The foregoing configuration information may be stored in a specific configuration file, and the advertisement information sent by the configuration information notification device may be an LLDP nearest bridge advertisement packet, and the configuration information of the PE device is added to the packet. And adding configuration information of the PE device to the packet in a private TLV format.

Optionally, the acquiring, by the pre-stored configuration information of the interface expansion device, the configuration information of the interface expansion device is pre-stored in the control bridge device in a configuration file, so that the control bridge device is read by The configuration file acquires configuration information of the interface extension device

In this embodiment, the CB device may convert the configuration information of the PE device into a configuration file in advance, for example, storing the configuration information of the PE device in a configuration file, and storing the configuration file in a memory of the CB device, for example, Store the configuration file in the flash of the CB device. When the configuration file is to be written to the advertisement packet, the CB device reads the configuration file from the flash and parses the configuration file to obtain the device type, the version number of the device, the version compile time, and the version storage path. information.

In step 204, the configuration information and the address information of the control bridge device are filled in the private message field of the advertisement message.

In this step, after obtaining the configuration information, the CB device adds a private TLV to the advertisement packet. As shown in FIG. 3, the basic format of the packet field provided in this embodiment may include the packet. The header of the field and the information content of the message field, wherein the header of the message field further includes a report The type of the field type TLVtype and the length of the header information, the information content of the message field can occupy 0-511 octets.

Optionally, the configuration information and the address information of the control bridge device are filled in the message content corresponding to the private message field of the advertisement packet, and the private message field is set in the header of the private message field. The type and length of the private message field header information.

In this embodiment, the processing module 120 adds the configuration information of the obtained PE device to the advertisement packet. As shown in FIG. 4, the format of the advertisement packet private TLV may be: the header of the packet field includes the packet. The type of the TLV type and the length of the header information. The information content of the packet field includes multiple link identifiers, a private TLV subtype, and a corresponding packet content Value. The content of the TLV type can occupy 7 bits. The length of the header information can be 9 bits, the link identifier OUI can be 00-19-0c, the content of the link identifier can occupy 3 bytes (Byte), and the content of the private TLV subtype can occupy 1 byte.

In this embodiment, after the definition of the private TLV is completed according to the format of FIG. 4, the processing module 120 fills the obtained configuration information into the private TLV, as shown in FIG. 5, the configuration information that the processing module 120 fills in to the private TLV. Including: the ID of the PE device, whether the version number of the PE device is changed, the version compilation information generation hash, the version compile time of the PE device, the version number, and the version name (verinfo) and the random number (random). The information is filled in the location of the private TLV. The ID of the PE device added to the private TLV can occupy 1 byte. The content of the PE device can be changed by 1 byte. The version information of the PE device is compiled. The content that generates the identifier can occupy 4 bytes. The content compilation time, version number, and version name of the PE device can occupy 60 bytes, and the random content can occupy 4 bytes.

The version compilation information generation hash (hash) refers to calculating the compile time, version number, and a random number of the software that the PE device needs to run according to the hash algorithm, obtaining a hash value, and encrypting the private TLV report by using the obtained hash value. The problem is that the PE device receives the error message and the PE device continuously upgrades the software version or restarts continuously.

In this embodiment, as shown in FIG. 5, in order to enable a plurality of PE devices to dynamically sense the configuration information of the corresponding PE device, the processing module 120 may further fill the configuration information of the next PE device into the private TLV, so that A PE device can also learn the corresponding configuration information and implement deployment of multiple PE devices. The format of the configuration information in the private TLV is as shown in FIG. 6. For example, the configuration information of the PE device includes the PE device ID (type) being 0x01, and the identifier of the PE device changing flag is 0x00, and the version is compiled. The information generation identifier is hash, the version time of the PE device is 20151110957, the version number is V3.02.20B13, and the version name is MSXP.SET.

In step 206, the advertisement message is sent to the target interface extension device by controlling the cascade port of the bridge device.

In this embodiment, the private message field is set in step 204, and after the configuration information of the PE device is filled in the advertisement message according to the set private message field, the sending module 130 passes the configuration port of the CB end. The advertisement message of the information is sent to the target PE device, and the target PE device performs the resolution and deployment according to the received packet.

The port of the CB device and the PE device includes two ports, one is a port that can receive private TLV packets, and the other is a port that cannot receive private TLV packets, that is, a common port and an uplink device. A member port is a port that can receive a private TLV packet in a port that is cascaded between a PE device and a CB device. The port that cannot receive the private TLV packet is a common port and does not belong to the PE device uplink device. Member port.

Optionally, the advertisement packet is a link layer discovery protocol LLDP packet.

The configuration information advertisement method and device for the interface extension device provided in this embodiment obtains the configuration information of the interface extension device by using the acquisition module, and fills the configuration information into the advertisement packet, so that the advertisement packet carries the configuration of the PE device. The information is sent to the target PE device. After receiving the advertisement packet, the target PE device can parse the configuration information from the advertisement packet, so that the PE device can sense the member port of the uplink device and obtain the The configuration information is zero-deployed accordingly.

Second embodiment

Referring to FIG. 7, FIG. 7 is a schematic structural diagram of an apparatus for configuring an interface expansion device according to an embodiment. The configuration apparatus may be configured in a PE device. In this embodiment, the configuration apparatus of the interface expansion device may include: Module 710, parsing processing module 720, judging module 730, and configuration module 740, wherein:

The receiving module 710 is configured to: receive an advertisement message that is sent by the control bridge device and that carries the private message field, where the content of the packet corresponding to the private message field includes configuration information of the interface extension device and the device that controls the bridge device. Address information, the configuration information includes: a device type, a version number of the device, a version compile time, and a version storage path.

Optionally, the receiving module 710 receives the LLDP neighbor bridge advertisement packet sent by the CB device.

The parsing processing module 720 is configured to: parse the advertisement packet to obtain configuration information of the interface extension device.

The determining module 730 is configured to: disconnect the interface extension device type in the configuration information from the device type of the target interface extension device.

The configuration module 740 is configured to: when the interface extension device type in the configuration information is consistent with the device type of the target interface extension device, download the version file according to the configuration information and the address information of the control bridge device, and configure the configuration information. Write to the configuration file of the target interface expansion device

The version file downloaded by the PE device according to the configuration information and the address information of the control bridge is a version file of the software that the PE device needs to run.

In this embodiment, the PE device that receives the advertisement packet with the private packet field may be referred to as the target PE device. When receiving the advertisement packet, the configuration device of the interface extension device detects whether the advertisement packet has a private message. The TLV, if yes, parses the advertisement packet by the parsing processing module 720 to obtain the device type, and the judging module 730 determines whether the parsed device type is consistent with the device type of the target PE device, and if they are consistent, the target is determined. The port of the PE device is the member port of the LACP link of the PE device. The current environment is a vertical stack. The device continues to parse the received private TLV packet format and obtain the address information of the CB device, such as the IP address of the VLAN 1 of the CB device. And the version file information of the software that the PE device carried in the private TLV needs to run, wherein the PE device version file information includes information such as a version number, a version compile time, and a version storage path of the PE device.

The target PE device can detect the port that receives the private TLV packet from the cascading port between the PE device and the CB device, and configures the port of the target PE device as a member port of the LACP.

Optionally, the configuration module 740 is configured to: according to the version number, the version compile time, and the version storage path of the device in the configuration information, use the address information of the control bridge device and FTP from the control bridge according to the file transfer protocol. Download the version file from the device.

In this embodiment, after the parsing processing module 720 parses the version storage path of the PE device and the port that sends the advertisement packet, the configuration module 740 downloads the version file corresponding to the version file information from the CB device according to the obtained version storage path. , wherein the target PE device can pass the file transfer protocol FTP is used to download the version file. The port that sends the advertisement packet is the CB device port that sends the private TLV packet.

In this embodiment, the parsing processing module 720, after downloading the version file according to the version file information of the PE device, further includes writing the parsed configuration information into the configuration file of the target PE device, so that the target PE device is deployed next time. You can directly read the corresponding port information and PE device version file information from its own configuration file.

In this embodiment, since the configuration information received by the configuration device of the interface extension device carries the configuration information of the PE device, the connection link between the CB device and the PE device is different, but the PE device can directly The received packet is the corresponding port, that is, the cascading port of the CB device, and the port information of the PE device obtained from the packet is used as the member port of the LACP link of the PE device, and the corresponding version is downloaded from the CB device. The file is implemented, so that the PE device deploys the PE device according to the received packet.

On the basis of the configuration device of the interface expansion device provided in FIG. 7 , the present embodiment further provides a configuration method of the interface expansion device, which can be applied to the PE device, as shown in FIG. The configuration method of the interface expansion device may include steps 802 to 808.

In step 802, the notification message carrying the private message field sent by the control bridge device is received, and the content of the packet corresponding to the private message field includes the configuration information of the interface extension device and the address information of the control bridge device. .

The configuration information may include: a device type, a version number of the device, a version compile time, and a version storage path.

In this example, the PE device that receives the advertisement packet with the private packet field may be referred to as the target PE device, and the configuration information may include: a device type, a version number of the device, a version compile time, and a version storage path, where The advertisement information received by the configuration information notification device may be an LLDP nearest bridge advertisement packet sent by the CB device, and the configuration information of the PE device is added to the packet, and the packet is in the private TLV format. Add configuration information of the PE device.

In step 804, the advertisement packet is parsed to obtain configuration information of the interface extension device.

When the configuration device receives the advertisement packet, it detects whether the advertisement packet carries a private TLV. If the advertisement packet has a private TLV, the resolution processing module 720 parses the advertisement packet to obtain the device type. information.

In step 806, it is determined whether the interface extension device type in the configuration information is consistent with the device type of the target interface extension device.

In step 808, in a case where the interface extension device type in the configuration information is consistent with the device type of the target interface extension device, the version file is downloaded according to the configuration information and the address information of the control bridge device, and the configuration information is written. The target interface is extended in the configuration file of the device.

The judging module 730 determines whether the parsed device type is consistent with the device type of the target PE device. If the parsed device type is consistent with the device type of the target PE device, the port of the target PE device is determined to be the PE device LACP link. Member port, the current environment is a vertical stack environment, and the received private TLV packet format is analyzed. The IP address of the VLAN 1 of the CB device and the version file of the PE device carried in the private TLV are obtained. The file information includes information such as the version number of the device, the version compile time, and the version storage path.

Optionally, the downloading the version file according to the configuration information and the address information of the control bridge device includes: obtaining a version number, a version compiling time, and a version storage path of the device in the configuration information, and using the address information of the control bridge device according to the File Transfer Protocol FTP downloads version files from the control bridge device.

In this embodiment, when it is determined that the device type in the configuration information is consistent with the device type of the target PE device, the configuration device is configured according to the device type, the version number of the device, the version compile time, and the version storage path. The information about the port of the PE device is zero. For example, the port of the PE device is used to find the corresponding communication link, connect to the CB device through the communication link, and use the FTP version of the CB device according to the version number of the device. Download the version file corresponding to the version number and deploy the PE device based on the version file. The port information of the PE device can be understood as the member port of the LACP of the PE device.

Optionally, the configuration device may further write the parsed configuration information into a configuration file of the target PE device, where the configuration file may be an XML file, and the configuration information is written into the XML file and stored in the flash of the PE device. If the PE device needs to be deployed again, the XML file corresponding to the configuration information can be directly read from the flash to obtain the configuration information of the PE device, and the XML file corresponding to the configuration information is directly read from the flash of the PE device. Obtaining the configuration information of the PE device is applicable to the case that the configuration information of the PE device is not modified. If the configuration information is modified, the configuration information needs to be obtained through the foregoing step 802-step 808.

The configuration information notification method, the configuration method, and the corresponding device of the interface extension device provided in this embodiment are configured to fill the configuration information of the obtained PE device into the advertisement packet in the private TLV format by using the processing module. The sending module sends the advertised packet with the private TLV to the target PE device through the cascading port. After receiving the advertised packet with the private TLV, the target PE device parses the advertised packet and obtains the advertised packet. The configuration of the PE device determines whether the device type in the configuration information is the same as the device type of the target PE device. If the device type in the configuration information is the same as the device type of the target PE device, the configuration information and the address of the CB device are used. The information is downloaded from the CB device, so that the PE device can directly obtain the configuration information of the PE device through the received packet, and the communication between the CB device and the PE device can be obtained without manual operation or communication through the gateway device. The link information is obtained, and the member port of the uplink LACP link of the PE device is obtained, and the version file is downloaded from the CB device to perform the PE device deployment according to the configured configuration information, so that the PE device can dynamically sense the configuration information.

The embodiment further provides a computer readable storage medium storing computer executable instructions for performing the method provided by any of the above embodiments.

FIG. 9 is a schematic structural diagram of an electronic device according to the embodiment. As shown in FIG. 9, the electronic device includes: one or more processors 910 and a memory 920. One processor 910 is taken as an example in FIG.

The electronic device may further include an input device 930 and an output device 940.

The processor 910, the memory 920, the input device 930, and the output device 940 in the electronic device may be connected by a bus or other means, as exemplified by a bus connection in FIG.

Input device 930 can receive input numeric or character information, and output device 940 can include a display device such as a display screen.

The memory 920 is a computer readable storage medium that can be used to store software programs, computer executable programs, and modules. The processor 910 performs various functional applications and data processing by executing software programs, instructions, and modules stored in the memory 920 to implement any of the above-described embodiments.

The memory 920 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the electronic device, and the like. In addition, the memory may include volatile memory such as random access memory (RAM), and may also include non-volatile memory such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device.

Memory 920 can be a non-transitory computer storage medium or a transitory computer storage medium. The non-transitory computer storage medium, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 920 can optionally include remotely with respect to processor 910 Set up memory that can be connected to an electronic device over a network. Examples of the above networks may include the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

Input device 930 can be used to receive input digital or character information and to generate key signal inputs related to user settings and function control of the electronic device. Output device 940 can include a display device such as a display screen.

The electronic device of the present embodiment may further include a communication device 950 that transmits and/or receives information over a communication network.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by executing related hardware by a computer program, and the program can be stored in a non-transitory computer readable storage medium. The program, when executed, may include the flow of an embodiment of the method as described above, wherein the non-transitory computer readable storage medium may be a magnetic disk, an optical disk, a read only memory (ROM), or a random access memory (RAM). Wait.

Industrial applicability

The present disclosure provides a configuration information notification method, a configuration method, and a corresponding device of an interface extension device, so that the PE device can obtain configuration information of the PE device through the received packet, and does not need to perform an artificial operation or a communication interaction through the gateway device. The link information between the CB device and the P device is obtained, so that the PE device can dynamically sense the configuration information, and the member ports of the uplink LACP link of the PE device, and download the version file from the CB device according to the configuration information to deploy the PE device. Settings.

Claims

A method for advertising configuration information of an interface extension device includes:

Acquiring configuration information of the pre-stored interface extension device, where the configuration information includes: a device type, a version number of the device, a version compile time, and a version storage path;

Filling in the private message field of the advertisement message with the configuration information and the address information of the control bridge device;

The advertisement message is sent to the target interface extension device by controlling the cascade port of the bridge device.
The method according to claim 1, wherein the obtaining the configuration information of the pre-stored interface extension device comprises: pre-storing the configuration information of the interface extension device in a control file device in a manner of a configuration file, so that the The control bridge device obtains configuration information of the interface extension device by reading the configuration file.
The method according to claim 1 or 2, wherein the filling the configuration information and the address information of the control bridge device into the private message field of the advertisement packet includes:

The configuration information and the address information of the control bridge device are filled in the message content corresponding to the private message field of the advertisement packet, and the type and private type of the private message field are set in the header of the private message field. The length of the header information of the message field.
The method according to claim 1 or 2, wherein the advertisement message is a link layer discovery protocol LLDP message.
A method for configuring an interface extension device includes:

Receiving, by the control network bridge device, an advertisement message carrying a private message field, where the content of the message corresponding to the private message field includes configuration information of the interface extension device and address information of the control bridge device, where the configuration information is Including: device type, device version number, version compile time, and version storage path;

And parsing the advertisement packet to obtain configuration information of the interface extension device, and determining whether the interface extension device type in the configuration information is consistent with the device type of the target interface extension device;

If the interface extension device type in the configuration information is consistent with the device type of the target interface extension device, download the version file according to the configuration information and the address information of the control bridge device, and write the configuration information to the target interface extension device. In the configuration file.
The method of claim 5, wherein said configuring information and controlling a bridge device The address information download version file includes:

Obtain the version number, version compile time, and version storage path of the device in the configuration information, and use the address information of the control bridge device to download the version file from the control bridge device according to the file transfer protocol FTP.
A configuration information notification device for an interface expansion device includes:

The obtaining module is configured to: obtain configuration information of the pre-stored interface expansion device, where the configuration information includes: a device type, a version number of the device, a version compiling time, and a version storage path;

The processing module is configured to: fill the configuration information and the address information of the control bridge device into the private message field of the advertisement packet;

The sending module is configured to: send the advertisement packet to the target interface extension device by using a cascade port of the control bridge device.
The device according to claim 7, wherein the processing module is configured to pre-store configuration information of the interface expansion device in a control network device in a configuration file, so that the control bridge device passes Reading the configuration file to obtain configuration information of the interface extension device.
The device according to claim 7 or 8, wherein the processing module is configured to: fill the configuration information and the address information of the control bridge device into the message content corresponding to the private message field of the advertisement message. And setting the type of the private message field and the length of the private message field header information in the header of the private message field.
An apparatus for configuring an interface extension device, comprising: a receiving module, configured to: receive an advertisement message that is sent by a control bridge device and that carries a private message field, where the content of the packet corresponding to the private message field includes an interface extension The configuration information of the device and the address information of the control bridge device, where the configuration information includes: a device type, a version number of the device, a version compile time, and a version storage path;

The parsing processing module is configured to: parse the advertisement packet to obtain configuration information of the interface extension device;

a judging module, configured to: disconnect the interface extension device type in the configuration information from the device type of the target interface extension device;

The configuration module is configured to: when the interface extension device type in the configuration information is consistent with the device type of the target interface extension device, download the version file according to the configuration information and the address information of the control bridge device, and write the configuration information. Enter the configuration file of the target interface extension device.
The device according to claim 10, wherein the configuration module is configured to: according to the version number, version compile time and version storage path of the device in the configuration information, use the address information of the control bridge device and transmit according to the file Protocol FTP downloads version files from the control bridge device.
A computer readable storage medium storing computer executable instructions for performing the method of any of claims 1-4 and 5-6.