CN109495285B - Network equipment configuration method and network equipment - Google Patents

Network equipment configuration method and network equipment Download PDF

Info

Publication number
CN109495285B
CN109495285B CN201710822403.8A CN201710822403A CN109495285B CN 109495285 B CN109495285 B CN 109495285B CN 201710822403 A CN201710822403 A CN 201710822403A CN 109495285 B CN109495285 B CN 109495285B
Authority
CN
China
Prior art keywords
network
network device
configuration file
packet
profile
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.)
Active
Application number
CN201710822403.8A
Other languages
Chinese (zh)
Other versions
CN109495285A (en
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201710822403.8A priority Critical patent/CN109495285B/en
Publication of CN109495285A publication Critical patent/CN109495285A/en
Application granted granted Critical
Publication of CN109495285B publication Critical patent/CN109495285B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/30Profiles

Abstract

The application provides a configuration method of network equipment and the network equipment, wherein a first configuration file packet acquired by first network equipment comprises configuration files of all network equipment in a network branch taking the first network equipment as a root node, so that the first network equipment can obtain a configuration file of the first network equipment from the first configuration file packet to realize self configuration. The second configuration file packet comprises configuration files of all network devices in the network branch which takes the second network device as a root node, so that the second network device can also obtain the configuration file of the second network device from the second configuration file packet to realize the configuration of the second network device; and the second network device can extract the configuration files of all the network devices in the network branch taking the network device connected with the second network device as the root node from the second configuration file packet, and send the configuration files to the network devices connected with the second network device, so that the configuration of the network devices connected with the second network device is realized.

Description

Network equipment configuration method and network equipment
Technical Field
The present application relates to the field of network technologies, and in particular, to a configuration technology for a network device.
Background
The network construction can be divided into two stages of network design and opening.
In the opening stage, the network equipment needs to be installed at a designated position, the connection of network cables among the network equipment is completed, and then each network equipment is configured to complete the network construction. Therefore, it is desirable to provide a solution that enables configuring a network device.
Disclosure of Invention
The application provides a configuration method of network equipment and the network equipment, so as to realize the configuration of the network equipment.
In order to achieve the above object, the following solutions are proposed:
a first aspect of the present application provides a method for configuring a network device, including: a first network device acquires a first configuration file packet, extracts a second configuration file packet from the first configuration file packet, and sends the second configuration file packet to a second network device; the first configuration file packet comprises configuration files of all network devices in a network branch which takes the first network device as a root node; the second configuration file packet comprises configuration files of all network devices in a network branch taking the second network device as a root node; the second network equipment is connected with the first network equipment; the first network device.
From the above process, it can be seen that: the first configuration file packet acquired by the first network device includes configuration files of all network devices in a network branch using the first network device as a root node, so that the first network device can obtain its own configuration file from the first configuration file packet to implement its own configuration. And the first network device extracts the second configuration file packet from the first configuration file packet, and the second configuration file packet includes the configuration files of all the network devices in the network branch taking the second network device as the root node, so that after the first network device sends the second configuration file packet to the second network device, the second network device can also obtain its own configuration file from the second configuration file packet, thereby implementing its own configuration. Furthermore, the second configuration file packet sent by the first network device to the second network device is not the configuration file of the second network device, but includes the configuration files of all network devices in the network branch taking the second network device as the root node, so that the second network device can extract the configuration files of all network devices in the network branch taking the network device connected to the second network device as the root node from the second configuration file packet and send the configuration files to the network device connected to the second network device, thereby realizing the configuration of the network device connected to the second network device.
In one implementation, before sending the second profile package, the method further comprises: and the first network equipment receives a message which comes from the second network equipment and is used for requesting the configuration file of the second network equipment. From this process it can be seen that: the first network equipment identifies the network equipment requiring the configuration file through the message for requesting the configuration file of the second network equipment, and then sends the second configuration file packet to the first network equipment, so that the accuracy of the second configuration file packet sent by the first network equipment is ensured.
In one implementation, the method further comprises: the first network equipment acquires the topology of a network branch taking the first network equipment as a root node; the extracting a second profile package from the first profile package comprises: and the first network equipment extracts the second configuration file packet from the first configuration file packet according to the topology of the network branch taking the first network equipment as a root node.
In one implementation, the second network device is connected to the first network device via at least two links, and before sending the second profile packet, the method further includes: receiving at least two messages from the second network device via the at least two links; the sending, by the first network device, the second profile packet to the second network device includes: transmitting the second profile packet via only one of the at least two links. From this process it can be seen that: the first network device receives at least two messages from the second network device through at least two links, and can determine a connection port between the first network device and the second network device from the links of the received messages, so that the first network device is ensured to transmit the second configuration file packet by using the port connected with the second network device. And the first network equipment adopts a link to send the second configuration file packet, so that the message communication between the first network equipment and the second network equipment is simply and conveniently completed.
In one implementation, the sending, by the first network device, the second profile packet to the second network device includes: and the first network equipment sends the second configuration file packet fragmented based on message length limitation to the second network equipment. From this process it can be seen that: the first network equipment sends the second configuration file packet which is fragmented based on the message length limitation, so that the problem that the second configuration file packet file is too long and cannot meet the message protocol requirement can be avoided.
In one implementation, before sending the second profile packet, the first network device further sends, to the second network device, a packet indicating that the first network device can provide a profile. From this process it can be seen that: the second network device may determine a connection port between the second network device and the first network device according to the packet, and receive a second configuration file packet sent by the first network device from the connection port.
A second aspect of the present application provides a network device, which is a first network device, and the first network device includes: a first obtaining unit, configured to obtain a first configuration file packet, where the first configuration file packet includes configuration files of all network devices in a network branch using the first network device as a root node; an extracting unit, configured to extract a second configuration file packet from the first configuration file packet, where the second configuration file packet includes configuration files of all network devices in a network branch using the second network device as a root node, and the second network device is connected to the first network device; a sending unit, configured to send the second profile packet to the second network device.
A third aspect of the present application provides a network device, where the network device is a first network device, and the first network device includes: a processor and a communication port; the processor is configured to: acquiring a first configuration file packet, extracting a second configuration file packet from the first configuration file packet, and sending the second configuration file packet to second network equipment by using the communication port; the first configuration file packet comprises configuration files of all network devices in a network branch which takes the first network device as a root node; the second configuration file packet comprises configuration files of all network devices in a network branch taking the second network device as a root node; the second network device is connected to the first network device.
In one implementation, before the processor sends the second profile packet through the communication port, the processor is further configured to receive, through the communication port, a message from the second network device and requesting a profile of the second network device.
In one implementation, the processor is further configured to obtain a topology of a network leg with the first network device as a root node; when the processor executes the extraction of the second configuration file package from the first configuration file package, the processor is specifically configured to: and extracting the second configuration file packet from the first configuration file packet according to the topology of the network branch taking the first network equipment as a root node.
In one implementation, the second network device establishes at least two links with at least two communication ports of the first network device, and the processor is further configured to receive at least two packets from the second network device using the at least two links before sending the second profile packet using the communication ports; wherein, when the processor executes the sending of the second profile packet to the second network device by using the communication port, the processor is specifically configured to: sending, by one of the at least two links, the second profile packet to the second network device.
In one implementation, when the processor executes the sending of the second profile packet to the second network device by using the communication port, the processor is specifically configured to: and sending the second configuration file packet fragmented based on message length limitation to the second network equipment by using the communication port. In one implementation, before the processor sends the second profile packet through the communication port, the processor is further configured to send, through the communication port, a message indicating that the first network device is capable of providing a profile to the second network device.
A fourth aspect of the present application provides a method for configuring a network device, including: the method comprises the steps that a first network device obtains a whole network configuration file packet, extracts a configuration file of a second network device from the whole network configuration file packet, and sends the configuration file of the second network device to a third network device; the whole network configuration file package comprises configuration files of all network devices in a network; the second network device comprises any network device in the network except the first network device; the third network device is located between the second network device and the first network device and is connected with the first network device.
From the above process, it can be seen that: the configuration file package of the whole network obtained by the first network device includes the configuration files of all the network devices in the network, so that the first network device can obtain the configuration file of itself from the configuration file package of the whole network to realize the configuration of itself. And the first network device extracts the configuration file of the second network device from the whole network configuration file packet and sends the configuration file to the third network device, if the third network device and the second network device are one device, the third network device receives the configuration file of the second network device, the configuration of the third network device is realized, if the third network device and the second network device are not the same device, the first network device sends the configuration file of the second network device to the third network device, and the third network device can also send the configuration file of the second network device to the second network device.
In one implementation, before sending the profile of the second network device, the method further includes: and the first network equipment receives a message which comes from the third network equipment and is used for requesting the configuration file of the second network equipment. From this process it can be seen that: the first network equipment identifies the network equipment requiring the configuration file through the message for requesting the configuration file of the second network equipment, and then sends the second configuration file packet to the first network equipment, so that the accuracy of the second configuration file packet sent by the first network equipment is ensured.
In one implementation, the third network device is connected to the first network device via at least two links, and before sending the configuration file of the second network device, the method further includes: receiving at least two messages from the third network device via the at least two links; the first network device sending the configuration file of the second network device to a third network device comprises: transmitting the configuration file of the second network device via only one of the at least two links. From this process it can be seen that: the first network device receives at least two messages from the third network device via at least two links, and can determine a connection port between the first network device and the third network device from the links of the received messages, so as to ensure that the first network device transmits the second configuration file packet by using the port connected with the third network device. And the first network equipment adopts a link to send the configuration file of the second network equipment, thus realizing the simple and convenient completion of the message communication between the first network equipment and the third network equipment.
In one implementation, the sending, by the first network device, the configuration file of the second network device to the third network device includes: and the first network equipment sends the configuration file of the second network equipment which is fragmented based on message length limitation to the third network equipment. From this process it can be seen that: the first network equipment sends the configuration file of the second network equipment which is fragmented based on the message length limitation, so that the problem that the configuration file of the second network equipment is too long and cannot meet the requirement of a message protocol can be avoided.
In one implementation, before sending the profile of the second network device, the method further includes: and the first network equipment sends a message indicating that the first network equipment can provide the configuration file of the second network equipment to the third network equipment. From this process it can be seen that: the third network device may determine a connection port between the third network device and the first network device according to the packet, and receive a configuration file of the second network device sent by the first network device from the connection port.
A fifth aspect of the present application provides a network device, where the network device is a first network device, and the first network device includes: the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a whole network configuration file packet which comprises configuration files of all network devices in a network; an extracting unit, configured to extract a configuration file of a second network device from the whole network configuration file packet, where the second network device includes any network device in the network except the first network device; a sending unit, configured to send the configuration file of the second network device to a third network device, where the third network device is located between the second network device and the first network device and is connected to the first network device.
In one implementation, the first network device further includes: a first receiving unit, configured to receive, before the sending unit sends the configuration file of the second network device, a packet from the third network device and used for requesting the configuration file of the second network device.
In one implementation, the third network device is connected to the first network device via at least two links, and the first network device further includes: a second receiving unit, configured to receive at least two packets from the third network device via the at least two links before the sending unit sends the configuration file of the second network device; when the sending unit executes sending of the configuration file of the second network device to a third network device, the sending unit is specifically configured to: transmitting the configuration file of the second network device via only one of the at least two links.
In an implementation manner, when the sending unit executes sending of the configuration file of the second network device to a third network device, the sending unit is specifically configured to: and sending the configuration file of the second network equipment which is fragmented based on message length limitation to the third network equipment.
In one implementation, before sending the configuration file of the second network device, the sending unit is further configured to:
and sending a message indicating that the first network equipment can provide the configuration file of the second network equipment to the third network equipment.
A sixth aspect of the present application provides a network device, comprising: the network device is a first network device, and the first network device includes: a processor and a communication port; wherein the processor is configured to: acquiring a whole network configuration file packet, extracting a configuration file of second network equipment from the whole network configuration file packet, and sending the configuration file of the second network equipment to third network equipment through the communication port; the whole network configuration file package comprises configuration files of all network devices in a network; the second network device comprises any network device in the network except the first network device; the third network device is located between the second network device and the first network device and is connected with the first network device.
In one implementation, before the processor sends the configuration file of the second network device through the communication port, the processor is further configured to receive, through the communication port, a packet from the third network device and requesting the configuration file of the second network device.
In one implementation, the third network device establishes at least two links with at least two communication ports of the first network device, and the processor is further configured to receive at least two packets from the third network device using the at least two links before sending the configuration file of the second network device using the communication ports; wherein, when the processor executes the sending of the configuration file of the second network device to the third network device by using the communication port, the processor is specifically configured to: sending, by one of the at least two links, a configuration file of the second network device to the third network device.
In one implementation, when the processor executes sending the configuration file of the second network device to the third network device through the communication port, the processor is specifically configured to: and sending the configuration file of the second network equipment which is fragmented based on message length limitation to the third network equipment by using the communication port.
In one implementation, before the processor sends the configuration file of the second network device through the communication port, the processor is further configured to: and sending a message indicating that the first network equipment can provide the configuration file of the second network equipment to the third network equipment by using the communication port.
A seventh aspect of the present application provides a computer program product for performing the method performed by the first network device described above when the computer program product is executed.
The eighth aspect of the present application further provides a computer-readable storage medium, which stores instructions for executing the method performed by the first network device described above.
Drawings
Fig. 1 is a system structure diagram for configuring a network device in a network according to an embodiment of the present disclosure;
fig. 2 is a timing diagram of a method for configuring a top-layer device and a second network device according to an embodiment of the present disclosure;
FIG. 3 is a diagram illustrating a network configuration package according to an embodiment of the present disclosure;
FIG. 4 is a diagram illustrating a second package of profiles disclosed in an embodiment of the present application;
fig. 5 is a timing diagram of a method for packet interaction between a top-layer device and a primary device disclosed in the embodiment of the present application;
FIG. 6 is a diagram illustrating another package of configuration files for a whole network according to an embodiment of the present disclosure;
fig. 7 is a system structure diagram for configuring a network device in a network according to an embodiment of the present disclosure;
fig. 8 is a timing diagram of a method for configuring a secondary device and a second network device according to an embodiment of the present disclosure;
fig. 9 is a timing diagram of a method for configuring a logical root device and a third network device according to an embodiment of the present disclosure;
fig. 10 is a timing diagram illustrating a method for packet interaction among the top device, the primary device, and the secondary device according to an embodiment of the present disclosure;
fig. 11 is a schematic structural diagram of a network device disclosed in an embodiment of the present application;
fig. 12 is a schematic structural diagram of a network device disclosed in an embodiment of the present application;
fig. 13 is a block diagram of a network device disclosed in an embodiment of the present application.
Detailed Description
In the embodiment of the application, a network device in the network for accessing an external network is referred to as a top-level device, optionally, the top-level device in the network is one, a network device directly connected to the top-level device is referred to as a primary device, a network device directly connected to the primary device and other than the top-level device is referred to as a secondary device, and so on until a network device at a terminal in the network.
The following describes configurations of network devices disclosed in the embodiments of the present application, by taking a top-level device and a non-top-level network device as examples. The top-level device, which may also be referred to as a first network device, is configured to obtain a first configuration file package; the first configuration file packet comprises configuration files of all network devices in a network branch which takes the first network device as a root node. Optionally, the top-level device may obtain the first profile package from the cloud management controller, and of course, may also obtain the first profile package in other manners, for example: the Universal Serial Bus (USB) flash disk is connected to a USB interface of the top-level device, and the top-level device reads a first configuration file package stored in the USB flash disk. The other network devices in the network all obtain the configuration file from the network device at the upper level connected to the network device, and the network device directly connected to the top-level device may be referred to as a second network device.
The following describes a scheme for the top-level device to obtain the first profile package from the cloud management controller in a specific embodiment. Referring to fig. 1 and fig. 2, in this embodiment, a method for configuring a top-level device includes:
s201, the terminal 106 obtains the login parameters of the cloud management controller 107.
The terminal 106 may obtain the login parameters of the cloud management controller 107 input by the user or sent by the third-party device, and further load software with the whole network deployment function, and after receiving the login parameters of the cloud management controller 107, execute the configuration method of the network device according to the login parameters of the cloud management controller 107. If the login user name and password of the cloud management controller 107 are authenticated, the login parameters of the cloud management controller 107 include the user name and the password.
The cloud management controller 107 is deployed on a public network and may be used to generate configuration files for network devices in the network. Among them, the cloud management controller 107 stores therein: a geographic location, a network identification, a network topology, and a profile of a plurality of network devices included in the network for each of the plurality of networks; wherein, the network topology includes: the network device comprises network devices in a network, and a device serial number of each network device, wherein the device serial number is used for uniquely identifying the network devices and a connection relationship between the network devices, and the connection relationship can be a logical connection relationship or a physical connection relationship.
S202, the terminal 106 establishes connection with the top-level device 101.
Wherein, the terminal 106 establishes a connection with the top-level device 101 to trigger the configuration of the whole network. The terminal 106 may establish a connection with the top-level device 101 through a Universal Serial Bus (USB), and both the terminal 106 and the top-level device 101 are provided with USB interfaces, and the two USB interfaces are connected through a USB connection line. In addition, the terminal 106 and the top-level device 101 can also establish connection through bluetooth, bluetooth modules are arranged in the terminal 106 and the top-level device 101, and the bluetooth module in the terminal 106 and the bluetooth module in the top-level device 101 establish connection based on a bluetooth protocol. In addition, the terminal 106 and the top device 101 may also establish connection through a USB interface to network port line, the terminal 106 is connected to a USB interface end of the USB interface to network port line, and the top device 101 is connected to a network port end of the USB interface to network port line.
S203, the terminal 106 logs in the cloud management controller 107 according to the login parameter of the cloud management controller 107, and requests the cloud management controller 107 to send the configuration file.
The request message of the configuration file sent by the terminal 106 is used for requesting the configuration file from the cloud management controller 107. The request message sent by the terminal 106 may carry the device serial number of the top-layer device 101, and is used as a credential for the cloud management controller 107 to generate the whole network profile packet. Moreover, if the request message needs to carry the device serial number of the top-level device 101, the terminal 106 needs to establish a connection with the top-level device 101, and then obtain the device serial number of the top-level device 101. The request message sent by the terminal 106 may also carry a network identifier or a geographic location of the network where the top-layer device 101 is located, and also serve as a credential for the cloud management controller 107 to generate the whole network profile packet. In addition, the network identifier of the network where the top-level device 101 is located may be input by a human-computer interaction module of the user at the terminal, and the geographic information of the network where the top-level device 101 is located may also be input by the user, or may be the geographic location of the terminal 106 where the terminal is located.
S204, the cloud management controller 107 generates a first configuration file package; the first configuration file package includes configuration files of all network devices in a network branch using the top device 101 as a root node.
Since the top-level device 101 is a network device for accessing an external network in the network, a network branch using the top-level device 101 as a root node includes: all network legs in the network where the top-level device 101 is located, the first profile package includes: profiles of all network devices in the network.
After receiving the request message of the configuration file sent by the terminal 106, the cloud management controller 107 finds the network where the network device connected to the terminal 106 is located, that is, the network where the top-level device 101 is located, according to the request message of the configuration file, and packages the configuration files of all the network devices included in the network to obtain a first configuration file package.
If the request message of the configuration file sent by the terminal 106 carries the network identifier or the geographic position of the network where the top-level device 101 is located, the cloud management controller 107 reads the network identifier or the geographic position of the network where the top-level device 101 is located, and searches for the network where the top-level device 101 is located according to the network identifier or the geographic position of the network where the top-level device 101 is located. If the device serial number of the top-level device 101 is in the request message of the configuration file sent by the terminal 106, the cloud management controller 107 searches for the network topology to which the top-level device 101 belongs according to the device serial number of the top-level device 101, and then obtains the network corresponding to the network topology to which the top-level device 101 belongs.
Optionally, the generating of the first profile packet by the cloud management controller 107 may further include, in addition to the profiles of all network devices included in the network: the network topology of the network branch with the top device 101 as the root node includes each network device included in the network and the connection relationship between the network devices. Optionally, the network topology may also include a device serial number for each network device.
The network topology of the network branch using the top-level device 101 as a root node is the network topology of the entire network. In addition, the cloud management controller 107 may be configured to separately transmit the network topology of the entire network to the terminal 106, in addition to packaging the network topology of the entire network into the first profile packet and transmitting the first profile packet to the terminal 106.
S205, the cloud management controller 107 sends the first profile package to the terminal 106.
S206, the terminal 106 transmits the first configuration file package to the top-level device 101.
S207, the top-level device 101 extracts the configuration file of the top-level device 101 from the first configuration file package, and activates the configuration file of the top-level device 101.
In the first configuration file package, the configuration files of each network device included in the network are stored, and therefore, the top-level device 101 needs to unpack the first configuration file package and analyze out the configuration files belonging to itself. After extracting the configuration file belonging to the top-level device 101, activating the configuration file completes the configuration of the top-level device. In general, profile activation is divided into two steps: setting the configuration file as a configuration file used in the next starting; and (6) restarting. After the network device is restarted, the configuration in the configuration file is executed one by one, and after the execution is completed, the configuration file is activated.
The manner in which the top-level device 101 parses its own configuration file from the first configuration file package may be to derive the position of the top-level device 101 according to the topology of the entire network, and correspondingly determine the configuration file of the position, that is, the configuration file of the top-level device 101. In addition, the top-level device 101 may also parse its own configuration file from the first configuration file packet according to its own device serial number.
In this embodiment, step S203 and steps S205 to S206 are executed when the top-level device 101 cannot route to the cloud management controller 107. If the top-level device 101 can route the cloud management controller 107 to be reachable, in order to save traffic of the terminal 106, after the top-level device 101 performs step S202, the top-level device does not need to perform step S203, but directly obtains the login parameter of the cloud management controller 107 from the terminal 106, logs in the cloud management controller 107 according to the login parameter, and requests the configuration file from the cloud management controller 107. After the top-level device 101 finishes executing step S204, it is not necessary to execute steps S205 to S206, but the cloud management controller 107 receives the entire network profile package and then executes step S207.
And, if the top-level device 101 can be reachable by the cloud management controller 107, the parameters of the top-level device 101 for accessing the external network, for example: a Point-to-Point Protocol Over Ethernet (PPPoE), a static Internet Protocol Address (IP) Address or a dynamic IP Address on the Ethernet may be transmitted to the top device 101 by the terminal 106 after the terminal 106 and the top device 101 establish a connection, so that the top device 101 may access the external network by using the parameters for accessing the external network, thereby implementing communication with the cloud management controller 107. The parameters for accessing the external network, which are transmitted by the terminal 106 to the top-level device 101, may be input by a user in a human-computer interaction module of the terminal 106, or acquired from the cloud management controller 107 after the terminal 106 logs in the cloud management controller 107 according to the login parameters of the cloud management controller 107.
In this embodiment, the scheme for the top-level device 101 to obtain the first configuration file package in the scenario that the top-level device can route to the cloud management controller 107 or in the scenario that the top-level device cannot route to the cloud management controller 107 is a specific implementation manner for obtaining the first configuration file package from the cloud management controller, and if the top-level device 101 obtains the first configuration file package in another manner, steps S201 to S206 are optional contents.
After step S206, the overlay device 101 may perform the following steps in addition to step S207:
s208, the top-level device 101 extracts a second configuration file package from the first configuration file package.
The second configuration file packet includes configuration files of all network devices in a network branch using the second network device as a root node, and the second network device is connected to the top-level device 101. The network branch is a tree topology including a certain root node, and all network devices in the tree topology are network devices in the network branch.
As can be seen from fig. 1, the second network device includes the primary device 102 and the primary device 103, and therefore, after the top-level device 101 obtains the first profile package, the second profile package that can be extracted from the first profile package includes: the configuration files of all network devices in the network branch using the primary device 102 as the root node, and the configuration files of all network devices in the network branch using the primary device 103 as the root node. The network devices in the network branch using the primary device 102 as a root node include the primary device 102, the secondary device 104, and the secondary device 105; the network devices in the network leg having primary device 103 as the root node include primary device 103.
Optionally, the top-level device 101 obtains a network topology of the entire network, determines a network branch using the second network device as a root node according to the network topology of the entire network, and extracts configuration files of all network devices in the network branch using the second network device as the root node from the first configuration file packet.
The connection relationship between network devices in the network topology of the whole network may be a logical connection or a physical connection, and the difference between the logical connection and the physical connection is as follows:
logical connection Physical connection
Connection information Comprises that Comprises that
Connected port Does not comprise Comprises that
If the connection relationship between the network devices in the network topology is physical connection, the top-level device 101 may extract the second configuration file packet from the first configuration file packet according to the connection information between the network devices, or may extract the second configuration file packet from the first configuration file packet according to the connected ports. If the connection relationship between the network devices in the network topology is a logical connection, the top-level device 101 can extract the second profile packet from the first profile packet only according to the connection information between the network devices.
The description will be given by taking an example of extracting configuration files of all network devices in a network branch having the primary device 102 as a root node. Referring to fig. 3, the connection relationship between the network devices in the network topology is a logical connection, and the network topology further includes the device serial number of each network device. The top-level device 101 finds a network branch using the first-level device 102 as a root node in the network topology according to the connection information between the network devices in the network topology, finds configuration files of the network devices included in the network branch, and packages the configuration files of all the network devices in the network branch using the first-level device 102 as the root node to form a second configuration file packet, and optionally, the second configuration file packet may further include a topology of the network branch using the first-level device 102 as the root node, as shown in fig. 4.
S209, the top-level device 101 sends the second profile packet to the second network device.
The second configuration file packet sent by the top-level device 101 to the second network device may be the second configuration file packet itself, or may be the second configuration file packet fragmented based on the packet length limitation under the condition that the second configuration file packet is long. Of course, the overlay device 101 may transmit the second profile package itself using the very long frame even in the case where the second profile package is long.
Moreover, the second profile packet extracted by the top-level device 101 may directly send the second profile packet itself to the second network device, or send the second profile packet fragmented based on the packet length limitation. Optionally, it may also be: after receiving the message from the second network device and requesting the profile of the second network device, the top-level device 101 sends a second profile packet to the second network device, or the second profile packet is fragmented based on the message length limitation. Correspondingly, the message for requesting the profile of the second network device includes: a message for requesting a profile of the second network device, and a message for requesting a fragment of the profile of the second network device.
The following describes a specific embodiment of a scheme in which the top-level device 101 sends a second profile packet to a second network device after receiving a packet from the second network device and requesting a profile of the second network device, or the second profile packet is fragmented based on a packet length limit.
Referring to fig. 1 and fig. 5, in this embodiment, taking the primary device 102 as an example, a process of the primary device 102 obtaining a configuration file of the primary device 102 through interaction with the top-level device 101 is described. Specifically, the interaction process includes:
s501, the primary device 102 sends a plurality of first layer two protocol packets through a plurality of ports.
The primary device 102 sends a first layer two protocol packet through a port, and the first layer two protocol packet is used for requesting configuration.
After the primary device 102 is started, it finds that it is in an empty configuration state, and if the empty configuration state is a state in which the network device is not configured, it needs to acquire a configuration file to complete configuration.
Also, the primary device 102 has a plurality of ports for connecting to the top level device 101, the secondary device 104, and the secondary device 105, respectively. The primary device 102 is started in the null configuration state, and does not know which port is connected to the top-level device 101, so that the primary device 102 respectively sends the first layer two protocol packet by using each connected port. In fig. 1, there are two connection lines between the top device 101 and the primary device 102, which illustrates that the primary device 102 uses two ports to establish a connection with the top device 101. The primary device 102 also uses the two connection ports to respectively send the first layer two protocol packets.
Since non-top-level devices such as the first-level device 102 are all configured devices without any layer, and three-layer communication cannot be performed, only two-layer protocols can be used for message interaction, specifically, protocols based on ethernet frame formats and extensible are used, for example: link Layer Discovery Protocol (LLDP), Cisco Discovery Protocol (CDP), Protocol based on Bridge Protocol Data Unit (BPDU) encapsulation.
The null configuration device performs message interaction by adopting an ethernet frame format-based and extensible protocol, that is, for each protocol, fields in the frame format need to be extended. Taking the LLDP protocol as an example, in the protocol, the LLDP protocol can be extended by a Type-Length-Value (TLV) with a specific Type of 127.
The format of the TLV with a specific Type of 127 is as follows:
Type Length OUI Subtype Information string
7bits 9bits 24bits 8bits 0-507octets
type: type of TLV. Type is 127.
Length: length of TLV.
OUI: organization unique identifier (English: organization unique identifier) is a unique identifier for attributing to a specific organization, such as 00-E0-FC.
Subtype: type defined in this TLV.
Information string: value of the present TLV.
subtype is defined as shown in the following table:
Subtype means of Frame direction information
1 Request configuration Request device>Deployed device Device serial number
2 Presence profile Deployed equipment>Requesting device
The Subtype of the first layer two protocol packet sent by the primary device 102 is 1. Optionally, the first layer two protocol message sent by the primary device 102 may also carry a device serial number of the primary device 102.
Optionally, in step S208 of the above embodiment, the top-layer device 101 extracts the second configuration file packet from the first configuration file packet, which may be executed after the top-layer device 101 receives the first layer-two protocol packet.
If the top-level device 101 receives the first two-layer protocol packet sent by the first-level device 102, the top-level device 101 may extract the second configuration file packet from the first configuration file packet according to the connected port. Referring to fig. 6, the top-level device 101 may calculate, from a receiving port of a first layer two protocol packet, for example, a port GE0/0/1 in the figure, and by combining connection information in the network topology, that the packet is sent by the first-level device 102, then find, in the network topology, a topology of a network branch using the first-level device 102 as a root node, and find a configuration file of a network device included in the network branch, repackage the topology of the network branch using the first-level device 102 as the root node and the configuration file of the network device included in the network branch to form a second configuration file packet, and in the second configuration file packet, the topology of the network branch using the first-level device 102 as the root node is optional.
S502, the top-level device 101 sends a second layer protocol packet to the primary device 102.
If the top-level device 101 stores the second configuration file packet, the top-level device 101 sends a second layer protocol packet to the primary device 102, where the second packet is used to indicate that the top-level device can provide the configuration file. Moreover, the top-level device 101 sends the second layer protocol packet in the following manner: a port receiving the first layer two protocol packet is used to send a second layer two protocol packet to the primary device 102.
And, if the first-level device 102 is connected to the top-level device 101 via at least two links, for example, there are two connecting lines between the top-level device 101 and the first-level device 102 in fig. 1, and the first-level device 102 uses two connecting ports to respectively send the first two-layer protocol packet, then the top-level device 101 receives the first two-layer protocol packet, and then uses the port that receives the first two-layer protocol packet to respectively send the second two-layer protocol packet.
As with the first layer two protocol packet sent by the primary device 102, the protocol based on the ethernet frame format and expandable for sending the second layer two protocol packet sent by the top layer device 101 is adopted, and if the second layer two protocol packet is sent by the LLDP protocol, its subtype is 2. The protocol used by the first-level device 102 to send the second layer protocol packet is generally the same as the protocol used by the top-level device 101 to send the first layer protocol packet, but different protocols may be used.
S503, the primary device 102 determines a connection port between the primary device 102 and the top device 101 according to the receiving port of the second layer protocol packet.
The port of the first-level device 102 that sends the first layer protocol packet and the port that receives the second layer protocol packet indicate that the ports are the ports through which the first-level device 102 and the top-level device 101 are connected if the ports are the same port. After determining the connection port between the primary device 102 and the top device 101, the primary device 102 requests and receives the second profile packet from the top device 101 through the connection port.
The disclosure of steps S501 and S503 is an embodiment for determining the connection ports of the primary device 102 and the top device 101, and certainly, there may be other embodiments for determining the connection ports of the primary device 102 and the top device 101, for example: information for explaining the connection form of the port is stored in the primary device 102 in advance, and in this case, the contents of steps S501 to S503 are optional contents.
Optionally, after determining the connection ports of the primary device 102 and the top device 101 by using other embodiments and obtaining the second configuration file packet by the top device 101, the second layer protocol packet may also be sent to the primary device 102, so as to indicate that the top device 101 can provide the configuration file.
S504, the first device 102 sends a third layer protocol packet to the top device 101 through the connection ports of the first device 102 and the top device 101, where the third layer protocol packet is used to request a length value of the second configuration file packet.
In this embodiment, the communication process of requesting and receiving the second configuration file packet by the primary device 102 is preferably completed based on a protocol encapsulated by the BPDU, because the BPDU reserves a longer space for the user-defined information. In addition, the direct extension BPDU frame is adopted, the existing protocol based on BPDU encapsulation is not used, the conflict with the transmission frequency of the existing protocol is prevented, and the existing protocol is not influenced as much as possible.
Furthermore, the BPDU specifies a set of special destination physical address (MAC) addresses, called BPDU-MAC, which is characterized by not broadcasting and not learning the source MAC, and therefore, it is a function of extending subsequent fields of the BPDU-MAC to carry the distribution of the second configuration file packet.
The frame format of the extended BPDU is as follows:
Figure GDA0002576859580000111
Figure GDA0002576859580000121
the meaning of each field is as follows:
BPDU-MAC: a multicast address;
SMAC: a source MAC;
EthType: a frame type;
VLAN-ID: this field is not used;
BPDU-Type: a BPDU type;
protocol-version: a protocol version;
magic: magic words;
encryption: and (4) an encryption mark, wherein 0 is unencrypted and 1 is encrypted by an OpenSSL certificate. If necessary, encrypting the content with the range behind length;
length: indicates the length from Reserved to the end of TLVs;
reserved: reserving a field;
serial-number: sending serial number, adding 1 to each message sent;
TLVs: TLV encapsulated data is the subject of data interaction.
The format of the TLV is defined as follows:
type (Type) Length (Length) Value (Value)
2octets 2octets 0–1400octets
The detailed Type is defined as follows:
Figure GDA0002576859580000122
in the third layer two protocol packet sent by the primary device 102, its type is 1. Optionally, the third layer two protocol message sent by the primary device 102 may also carry a device serial number of the primary device 102.
And S505, the top-layer device 101 calculates a length value of the second configuration file package according to the second configuration file package.
When generating the second profile package, a description file is created, where the description file is used to describe the offset and the length of the profile of all network devices included in the network leg in the package file. And when the second configuration file package is generated by packaging, the description file is placed at the starting position of the file. Therefore, the length of the second profile package mentioned above refers to: the total length of the description file and the file lengths of all the configuration files added together. If the second configuration file packet further includes the topology of the network leg, the length of the second configuration file packet refers to: the total length of the profile, the topology of the network legs and the file length of all the profiles added up.
S506, the top device 101 sends a fourth layer protocol packet to the first device 102, where the fourth layer protocol packet carries a length value of the second configuration file packet.
The fourth layer protocol packet sent by the top-level device 101 is the same as the third layer protocol packet sent by the first-level device 102, and when a protocol based on BPDU encapsulation is adopted, the type of the fourth layer protocol packet is 2.
S507, the primary device 102 determines whether the length value in the fourth layer protocol message exceeds a preset maximum length value.
The maximum length value can be set according to the maximum length value allowed by the TLV specified in the protocol, for example, in the BPDU-based protocol, the maximum length allowed by the TLV is 1400 octets.
If the length value is judged to exceed the preset maximum length value, executing the steps S508 to S509, otherwise executing the steps S510 to S511.
Before the first-level device 102 receives the second configuration file packet, the length value of the second configuration file packet is determined, so that the problem that the length value of the second configuration file packet exceeds the maximum value, which causes the requirement of the protocol not to be met, can be avoided. And if the length value in the fourth layer-two protocol message is judged to exceed the preset maximum length value, which indicates that the length value of the second configuration file packet exceeds the maximum value required by the protocol, steps S510 to S511 are executed, that is, the second configuration file packet is requested and received in a fragmentation manner, so that the length value of each fragment can be ensured not to exceed the maximum value required by the protocol.
S508, the primary device 102 sends a fifth layer protocol packet to the top-layer device 101.
The fifth layer two protocol packet is used to request a fragment of the second profile packet, and has a type of 3, and carries an offset and a length value, that is, an initial value of a certain fragment of the second profile packet and a length value of the fragment.
The primary device 102 calculates the number of fragments according to the length value in the fourth layer protocol message, generates a fifth layer protocol message corresponding to the number of fragments according to the calculation result, and sequentially sends the fifth layer protocol message to the top layer device 101.
For example: the second profile package is 3000octets in length:
3000octets
since 3000octets exceeds the maximum length allowed once, it can be sent in the following way:
1400octets 1400octets 200octets
in the above example, in the message sent by the primary device 102 and used for requesting the first fragment of the second profile packet, the offset is 0, and the length value is 1400 octets; in the message for requesting the second fragment, the offset is 1401, and the length value is 1400 octets; in the message requesting the second slice, the offset is 2801 and the length is 200 octets.
S509, the top-level device 101 sends the fragments of the second profile package to the primary device 102.
The first-level device 102 sends a message for requesting a fragment of the second configuration file packet once, the top-level device 101 returns the fragment of the request information corresponding to the fragment to the first-level device 102, the first-level device 102 receives the fragment and stores the fragment, and then sends the message for requesting the fragment of the second configuration file packet once again, and the first-level device 102 can obtain the complete branched configuration file packet after interaction for several times.
As can be seen from the BPDU-based protocol, the type of the second profile packet transmitted by the top-level device 101 is 4.
S510, the primary device 102 sends a sixth layer two protocol packet to the top-layer device 101.
The sixth layer two protocol message is used for requesting a second configuration file packet, the type is also 3, and the carried length value is the length value in the fourth layer two protocol message.
S511, the top-level device 101 sends the second profile packet to the primary device 102.
After step S509 and step S511, step S512 may be executed.
The solutions disclosed in steps S509 to S511 are an implementation manner for the top-level device 101 to send the second configuration file package fragmented based on the message length limitation to the primary device 102, or the second configuration file package itself. In another embodiment, the top-level device 101 may fragment the second configuration file packet by using a specified message length, and send the fragmented second configuration file packet to the primary device 102. In another embodiment, the manner in which the top-level device 101 sends the second profile package fragmented based on the packet length limitation, or the second profile package itself, to the primary device 102 includes:
s504', the first device 102 sends a seventh layer protocol packet to the top device 101 through the connection ports of the first device 102 and the top device 101, where the seventh layer protocol packet carries a maximum length value allowed to be used by the first device 102.
The maximum length value that the primary device 102 is allowed to use is the maximum length value specified in the protocol used by the primary device 102 to send the seventh layer protocol packet.
S505' the top-layer device 101 calculates a length value of the second configuration file package according to the second configuration file package, and determines whether the length value of the second configuration file package exceeds a maximum length value allowed to be used by the primary device 102.
If the length value of the second configuration file packet is judged to exceed the maximum length value allowed to be used by the primary device 102, executing the steps S506' to S507', otherwise executing the step S508 '.
S506', the top device 101 calculates the number of fragments according to the maximum length value allowed to be used by the primary device 102.
S507', the top device 101 sequentially sends the fragments of the second profile package to the primary device 102.
The top-level device 101 sequentially sends the fragments of each second profile package to the primary device 102, and the primary device 102 receives and combines the received fragments of the second profile package into a second profile package. The top-level device 101 may also send one fragment of the second profile packet at a time, after the primary device 102 receives the fragment of the second profile packet, send a message to the top-level device 101 to request the next fragment, and the top-level device 101 sends the next fragment of the second profile packet to the primary device 102 again, and this is repeated until the top-level device 101 finishes sending all the fragments of the second profile packet.
S508', the top-level device 101 sends the second profile package to the primary device 102.
After steps S507 'and S508', S512 is performed.
If the first-level device 102 and the top-level device 101 are connected via at least two links, in order to simply complete communication between the network devices, the first-level device 102 uses the same link to receive the second configuration file packet sent by the top-level device 101, and optionally, the second configuration file packet is a fragment of the second configuration file packet or the second configuration file packet itself. Even in steps S504 to S511, and S504 'to S508', the message communication process between the primary device 102 and the top device 101 can be performed based on the same link.
After the first device 102 obtains the second configuration file packet, the configuration file packet may be extracted from the second configuration file packet, where the configuration file packet includes configuration files of all network devices in a network branch using the network device connected to the first device 102 as a root node, and the extracted configuration file packet is sent to the network device connected to the first device 102, and the network device connected to the first device 102 performs the steps of extracting and sending the configuration file packet, and so on until each network device in the network receives its own configuration file.
Optionally, before extracting the second configuration file packet from the first configuration file packet, each network device in the network may further obtain a topology of a network branch taking itself as a root node, and extract the second configuration file packet from the first configuration file packet according to the topology, and the specific manner of extraction may refer to the content of step S208.
S512, the primary device 102 extracts the configuration file of the primary device 102 from the second configuration file package, and activates the configuration file of the primary device 102.
The primary device 102 may derive a location of the primary device 102 according to a topology of the network branch, determine its own configuration file corresponding to the location, and may also find its own configuration file according to its own device serial number.
After the primary device 102 completes the configuration of its own configuration file, it may also record and store the uplink port, i.e. the port connected to the top-level device 101, to ensure that the communication process with the top-level device 101 is completed with this port later.
In another embodiment of the present application, the network device connected to the terminal 707 is not the top-level device 701, but another network device, such as the secondary device 704 in fig. 7. Based on this, in the configuration method of the network device disclosed in this embodiment, the configuration method of the network device (specifically, taking the secondary device 704 as an example for explanation) of the connection terminal 707, with reference to fig. 8, includes: steps S801 to S809.
The specific implementation process of steps S801 to S803 can refer to the content of the embodiment corresponding to fig. 2, and the difference is that the device connected to the terminal 707 is changed from the top-level device 701 to the secondary device 704.
In this embodiment, in a specific implementation manner of step S803, although the secondary device 704 is not a top-level device in the network, the first profile packet generated for the secondary device by the cloud management controller 107 should also include profiles of all network devices in the network. Therefore, when the network device that acquires the configuration file from the cloud management control is a non-top-level device, the network branch that takes the secondary device 704 as the root node in the first configuration file packet generated by the cloud management controller 107 refers to: setting a secondary device 704 as a logical top-level device to form a logical network, wherein the network branch takes the secondary device 704 as a root node; the logic top-level device is not a real top-level device in the network, and the logic top-level device does not have the functions of the real top-level device but is a supposed top-level device.
In a specific implementation manner of step S807, if the secondary device 704 parses its own configuration file from the first configuration file packet according to its own device serial number, an implementation process thereof is the same as that of the embodiment corresponding to fig. 2. If the secondary device 704 analyzes its own configuration file according to the network topology, the secondary device 704 needs to receive the location identifier of the secondary device 704 sent by the terminal 707, and the secondary device 704 determines the configuration file of the secondary device 704 according to the location identifier of the secondary device 704 in the first configuration file packet.
The user specifies the network device connected to the terminal 707 in the terminal 707, and the terminal 707 receives the user's specification information and transmits the location identifier of the network device connected to the terminal 707.
In a specific implementation manner of step S808, the second network device, that is, the network device connected to the secondary device 704 may be a previous device of the secondary device 704, such as the primary device 702 in fig. 7, or may be a next device of the secondary device 704, such as the tertiary device 706 in fig. 7. In addition, the secondary device 704 may determine whether the second network device is the upper-level network device or the lower-level network device of the secondary device 704 by comparing the device serial number of the second network device with the receiving port of the first layer two protocol packet in the network topology of the entire network.
For the case that the second network device is a superior device, the network branch in the second profile packet with the second network device as the root node refers to: and setting the second network equipment as a logic top-level equipment to form a logic network, wherein the network branch takes the second network equipment as a root node.
And, the network leg with the second network device as the root node may include: in a logical network formed by setting top-level devices in the network as second network devices, all network branches using the second network devices as root nodes are basically all network branches in the original network. The method can also comprise the following steps: in all network branches included in the logical network formed by setting the second network device as the logical top-level device, and taking the second network device as the root node, the network branches that are left by taking the secondary device 704 as the network branch in the root node are removed, such as the network branch including the primary device 702, the top-level device 701, and the primary device 703, and the network branch including the primary device 702 and the secondary device 705 in fig. 7.
For the case that the second network device is the next-level device, what the network branch in the second configuration file packet with the second network device as the root node refers to is: and all network branches in the original network taking the second network equipment as a root node.
In a specific implementation manner of step S809, if the secondary device 704 sends the second configuration file packet to the second network device, the method is as follows: after receiving the message from the second network device and requesting the profile of the second network device, and then sending the second profile packet to the second network device, the message interaction process between the secondary device 704 and the second network device may refer to the content of the embodiment corresponding to fig. 5, which is different in that: the configured device is changed from the top-level device to a secondary device 704, the requesting device is changed to a tertiary device 706 or a primary device 702, and the configuration files included in the second configuration file package are adjusted according to the level of the second network device.
Another embodiment of the present application further discloses a configuration method of a network device. In this embodiment, the configured device may be divided into two roles: a logical root device and a proxy device; the network device which acquires the whole network configuration file package in the cloud management controller becomes a logic root device after activating the self configuration file, and the logic root device stores the whole network configuration file package. The proxy device only stores its own configuration file, and is used for proxying the message for requesting configuration sent by the request device to the logical root device, and proxying the message for response sent by the logical root device to the request device.
Based on this, in the configuration method of the network device disclosed in this embodiment, referring to fig. 9, the configuration method of the logical root device includes: steps S901 to S909.
The logic root device is a top-level device or a non-top-level device, and the specific implementation processes of steps S901 to S903 may all refer to the contents corresponding to the embodiment of fig. 2.
In a specific implementation manner of step S904, the cloud management controller generates a whole network configuration file packet including configuration files of all network devices in the network for the request packet of the configuration file, regardless of whether the logical root device is the top-level device.
In a specific implementation manner of step S908, after receiving the entire network configuration file packet, the logic root device extracts the configuration file of the second network device from the entire network configuration file packet, where the second network device includes any network device in the network except the logic root device.
Because the logical root device can only send the configuration file to the network devices connected to the logical root device, if the second network device is a network device connected to the logical root device, that is, the second network device is one of the third network devices, the configuration file of the second network device sent by the logical root device to the third network device includes: and the logic root device sends the configuration file of the third network device to the third network device.
If the second network device is not a network device connected to the logical root device, but any network device in a network branch using a third network device as a root node in the network, it indicates that the third network device is a proxy device, and the configuration file of the second network device sent by the logical root device to the third network device includes:
the logic root device sends the derived configuration file of the second network device to the third network device;
the difference between the derived configuration file of the second network device and the configuration file of the second network device is that the Type value includes a value meaning the proxy in addition to a value meaning the response configuration in the derived configuration file of the second network device.
In a specific implementation manner of step S909, the logic root device sends the configuration file of the second network device to the third network device, may send the configuration file of the second network device to the third network device directly after extracting the configuration file of the second network device, or may send the configuration file of the second network device to the third network device after receiving a message from the third network device and requesting the configuration file of the second network device.
A specific embodiment of the following describes a scheme in which, after receiving a packet from a third network device and requesting a profile of the second network device, a logical root device sends the profile of the second network device to the third network device, and in this scheme, the second network device is not a network device connected to the logical root device, but any network device in a network branch in which the third network device is a root node in a network.
Referring to fig. 1 and fig. 10, in this embodiment, taking a third network device as a secondary device 104 as an example, a process of the secondary device 104 obtaining a configuration file from a logical root device, namely a top-level device 101, through a proxy device, namely a primary device 102, is described. Specifically, the method comprises the following steps:
s1001 and the secondary device 104 send a plurality of first layer two protocol packets through a plurality of ports.
The secondary device 104 sends a first layer two protocol packet through a port, and the first layer two protocol packet is used for requesting configuration. The secondary device 104 is a request device, and its ports are connected to other network devices, and it is necessary to sequentially send the first layer two protocol packets by using the ports in the connection state, so as to determine the port connected to the primary device 102. In addition, for a specific implementation process of the secondary device 104 sending the first layer two protocol packet, reference may be made to the content of step S501 in the embodiment corresponding to fig. 5, which is not described herein again.
S1002, the primary device 102 generates a first derived two-layer protocol packet according to the first two-layer protocol packet.
The first layer two protocol message sent by the secondary device 104 may carry a device serial number of the secondary device 104. The primary device 102 receives the first layer two protocol packet, and determines that it does not store the configuration file of the secondary device 104 according to the device serial number of the secondary device 104 carried in the first layer two protocol packet or the port of the first layer two protocol packet sent by the secondary device 104, and if it indicates that it is a proxy device, it generates a first derived layer two protocol packet.
For the first two-layer protocol packet generated by using the LLDP protocol, the primary device 102 receives the first two-layer protocol packet, and reassembles the packet to have a value of Subtype with a meaning of proxy, that is, adds Subtype with a meaning of 3 (the meaning of Subtype3 is set as proxy information), to form a first derived two-layer protocol packet, that is, the value of Subtype of the first derived two-layer protocol packet is Subtype1 and Subtype 3. Moreover, the first derived layer two protocol packet may also carry the device serial number of the secondary device 104.
In addition, if another two-layer protocol is adopted, for example, based on the BPDU encapsulation protocol, in the uplink or downlink derived message, the specific value of Type is also added to the value of proxy.
S1003, the primary device 102 sends a first derived two-layer protocol packet to the top-layer device 101.
After the primary device 102 requests the configuration file of the top device 101, the connection port between the primary device and the top device 101 is recorded, and after the primary device 102 receives the first two-layer protocol message sent by the secondary device 104 and generates the first derived two-layer protocol message, the recorded connection port between the primary device 102 and the top device 101 is used for sending the first derived two-layer protocol message.
In the following steps, which reflect the interaction between the primary device 102 and the top-level device 101, the port is used, and therefore, the description is not necessarily given.
Alternatively, the process of the top-level device 101 extracting the profile of the secondary device 104 from the whole network profile package may be performed after the top-level device 101 receives the first derived layer two protocol packet.
The top-level device 101 stores a whole network configuration file package, and according to the device serial number of the secondary device 104, the configuration file of the secondary device 104 can be determined, and if the top-level device 101 also stores the network topology of the network, the configuration file can also be determined by using the device account and the connection relationship of the network device directly connected with the requesting device.
The primary device 102 carries its own device account and its port number connected to the secondary device 104 to the first derived two-layer protocol message, and sends the message to the top-layer device 101. The top-level device 101 receives the first derived two-layer protocol packet, determines the location of the primary device 102 in the network topology according to the account of the primary device 102, determines the true requesting device (i.e., the secondary device 104) according to the port number of the connection between the primary device 102 and the secondary device 104, and obtains the configuration file of the secondary device 104. In this scheme, the network topology obtained by the top-level device 101 further includes an account of each network device in the network.
S1004, the top-level device 101 sends a second derived two-layer protocol packet to the primary device 102.
If the top-level device 101 receives the first derived two-level protocol packet, it generates a second derived two-level protocol packet for responding to the first derived two-level protocol packet. If the LLDP protocol is used, in the second derived two-layer protocol message, the values of Subtype are Subtype2 and Subtype 3.
S1005, the primary device 102 sends the second derived two-layer protocol packet to the secondary device 104.
S1006, the secondary device 104 determines a connection port between the secondary device 104 and the primary device 102 according to the receiving port of the second derived two-layer protocol packet.
The specific process of this step may refer to the content of step S503 in the embodiment corresponding to fig. 3, and is not described herein again.
S1007, the secondary device 104 sends a third layer protocol packet to the primary device 102 by using the connection port between the secondary device 104 and the primary device 102, where the third layer protocol packet is used to request a length value of the configuration file of the secondary device 104.
S1008, the primary device 102 generates a third derived two-layer protocol packet according to the third two-layer protocol packet.
If a protocol based on BPDU encapsulation is adopted, the value of Type in the third derived two-layer protocol message is 1 and 5 (the meaning of Type5 is set as proxy information). In the derived protocol messages mentioned in the following steps, the Type value is combined with Type5 on the basis of the Type value of the original information.
S1009, the primary device 102 sends the third derived two-layer protocol packet to the top-level device 101.
The secondary device 104 does not know that it is several levels of network devices away from the logical root device, and the secondary device 104 only knows that the protocol packet can be sent or obtained through the port connected to the primary device 102. Therefore, the secondary device 104 generates a third layer protocol packet and then sends the third layer protocol packet to the primary device 102 through the connection port of the primary device 102. After receiving the protocol packet, the primary device 102 parses the protocol packet, determines that the protocol packet is to be sent to the logical root device, generates a third derived two-layer protocol packet, and sends the third derived two-layer protocol packet to the network device connected to the primary device.
If there are other intermediate-layer network devices, that is, other proxy devices, between the proxy device, such as the primary device 102, and the logical root device, the proxy devices receive the third layer protocol derivative packet sent by the proxy device directly connected to the proxy device, analyze the third layer protocol derivative packet, determine that the information is to be sent to the logical root device, and all use the communication port to send the information to the connected network devices.
S1010, the top-level device 101 calculates a length value of the configuration file of the secondary device 104 according to the configuration file of the secondary device 104.
S1011, the top-level device 101 sends a fourth derived two-layer protocol packet to the primary device 102, where the fourth derived two-layer protocol packet carries a length value of the configuration file of the secondary device 104.
S1012, the primary device 102 sends a fourth derived two-layer protocol packet to the secondary device 104.
S1013, the secondary device 104 determines whether the length value of the configuration file of the secondary device 104 carried in the fourth derived layer-two protocol message exceeds a preset maximum length value.
If the length value is judged to exceed the preset maximum length value, executing the steps S1014 to S1018, otherwise executing the steps S1019 to S1023.
S1014, the secondary device 104 sends a fifth layer protocol message to the primary device 102; wherein, the fifth layer protocol packet is used to request the fragment of the configuration file of the secondary device 104.
S1015, the primary device 102 generates a fifth derivative second-layer protocol packet according to the fifth second-layer protocol packet.
S1016, the primary device 102 sends the fifth derivative layer two protocol packet to the top device 101.
S1017, the top-level device 101 sends the fragment of the derived configuration file of the secondary device 104 to the primary device 102.
The difference between the values in the fragment of the derived profile of the secondary device 104 and the values in the profile of the secondary device 104 is that the Type value in the fragment of the derived profile of the secondary device 104 includes a value meaning the proxy in addition to a value meaning the response configuration.
S1018, the primary device 102 sends the secondary device 104 the fragment of the derived configuration file of the secondary device 104.
S1019, the secondary device 104 sends a sixth layer protocol packet to the primary device 102, where the sixth layer protocol packet is used to request a configuration file of the secondary device 104.
S1020, the primary device 102 generates a sixth derived two-layer protocol packet according to the sixth two-layer protocol packet.
S1021, the primary device 102 sends a sixth derived two-layer protocol packet to the top-layer device 101.
S1022, the top-level device 101 sends the derived configuration file of the secondary device 104 to the primary device 102.
Wherein, as in step S1017, the Type value of the derived profile of the secondary device 104 further includes 5.
S1023, the primary device 102 sends the derived configuration file of the secondary device 104 to the secondary device 104.
S1024, the secondary device 104 activates the derived configuration file of the secondary device 104.
The specific implementation processes of steps S1007 to S1024 may all refer to the contents of the embodiment corresponding to fig. 5, and the difference from the contents of the embodiment corresponding to fig. 5 is that the primary device 102 generates a derived protocol packet according to the protocol packet sent by the secondary device 104, and sends the derived packet sent by the top device 101 to the primary device 102.
Another embodiment of the present application further discloses a network device, as a first network device, with reference to fig. 11, the first network device includes:
the first obtaining unit 1101 is configured to obtain a first profile package according to the implementation disclosed in steps S201 to S206 in the embodiment of fig. 2 or the implementation disclosed in steps S801 to S806 in the embodiment of fig. 8, where the first profile package includes profiles of all network devices in a network branch using the first network device as a root node.
An extracting unit 1102, configured to extract, according to an implementation disclosed in step S208 in the embodiment of fig. 2 or an implementation disclosed in step S808 in the embodiment of fig. 8, a second configuration file packet from the first configuration file packet, where the second configuration file packet includes configuration files of all network devices in a network branch using the second network device as a root node, where the second network device is connected to the first network device.
Optionally, in an embodiment, still referring to fig. 11, the first network device further includes: a second obtaining unit 1103, configured to obtain a topology of a network branch using the first network device as a root node. Furthermore, the extracting unit 1102 extracts the second configuration file packet from the first configuration file packet according to the topology of the network branch using the first network device as the root node according to the optional implementation manner disclosed in step S208 in the embodiment of fig. 2.
A sending unit 1104, configured to send a second profile package to the second network device according to the embodiment disclosed in step S209 in the embodiment of fig. 2; or is configured to send, according to the embodiment disclosed in steps S501 to S511 in the embodiment corresponding to fig. 5 or step S809 in the embodiment corresponding to fig. 8, a second profile packet fragmented based on packet length limitation to the second network device, and send, before sending the second profile packet, a packet indicating that the first network device can provide a profile to the second network device.
Optionally, in an embodiment, still referring to fig. 11, the first network device further includes: the first receiving unit 1105 is configured to receive, according to an implementation disclosed in step S510 in the embodiment of fig. 5, a message that is from the second network device and is used for requesting the profile of the second network device, before the sending unit 1104 sends the second profile packet.
Optionally, in an embodiment, the second network device is connected to the first network device via at least two links, and the first network device further includes: a second receiving unit 1106, configured to receive at least two packets from the second network device via at least two links before the sending unit 1104 sends the second profile packet according to the embodiment disclosed in step S501 in the embodiment of fig. 5. Furthermore, the transmitting unit 1104 is configured to transmit the second profile package via only one link of the at least two links according to an embodiment disclosed in step S511 in the embodiment of fig. 5.
Another embodiment of the present application further discloses a network device, as a first network device, with reference to fig. 12, the first network device includes:
an obtaining unit 1201, configured to obtain a whole network configuration file package according to the embodiment disclosed in steps S901 to S906 in the embodiment corresponding to fig. 9, where the whole network configuration file package includes configuration files of all network devices in a network;
an extracting unit 1202, configured to extract a configuration file of a second network device from the whole network configuration file packet according to an implementation disclosed in step S908 in the embodiment corresponding to fig. 9, where the second network device includes any network device in the network except the first network device;
a sending unit 1203, configured to send a configuration file of a second network device to a third network device according to an implementation manner disclosed in step S909 in the embodiment of fig. 9, where the third network device is located between the second network device and the first network device and is connected to the first network device; or, the method is configured to send, to the third network device, the profile of the second network device fragmented based on the packet length limitation according to the implementation disclosed in steps S1001 to S1023 in the embodiment corresponding to fig. 10, and send, to the third network device, a packet indicating that the first network device is capable of providing the profile of the second network device before sending the profile of the second network device.
Optionally, in an embodiment, still referring to fig. 12, the first network device further includes: the first receiving unit 1204 is configured to receive, before the sending unit 1203 sends the configuration file of the second network device, a message from the third network device and requesting the configuration file of the second network device according to the embodiments disclosed in steps S1014 to S1016 or steps S1019 to S1021 in the embodiment corresponding to fig. 10.
Optionally, in an implementation, the third network device is connected to the first network device via at least two links, still referring to fig. 12, the first network device further includes a second receiving unit 1205, configured to receive at least two messages from the third network device via at least two links according to the implementation disclosed in steps S1001 to S1003 in the embodiment of fig. 10 before the sending unit 1203 sends the configuration file of the second network device. Further, the transmitting unit 1203 transmits the configuration file of the second network device via only one link of the at least two links according to the embodiment disclosed in steps S1004 to S1005 of the embodiment of fig. 10.
Another embodiment of the present application further discloses a network device, as shown in fig. 13, including:
the number of the processors 1301 (in which one or more processors 1301 are included in the first network device 1300 (e.g., a switch, a router, a firewall, etc.). one or more processors are illustrated in fig. 13), and the hardware structures include an optional memory 1302, an optional forwarding chip 1303, a communication port 1304, a power supply, an operating system installed on hardware, and the like, which are not specifically illustrated in fig. 13 one by one, but are not limited to the network device in the embodiment of the present application. In some embodiments of the present application, the processor 1301, the memory 1302, and the forwarding chip 1303 may be connected by a bus or other methods, which are not limited herein. In fig. 13, an example is illustrated in which the processor 1301 and the memory 1302 are connected via a bus, and the forwarding chip 1303 is connected to the processor 1301.
Processor 1301 is configured to control the operation of first network apparatus 1300, and processor 1301 may also be referred to as a Central Processing Unit (CPU). In a particular application, the various components of the first network device 1300 are coupled together by a bus system that may include a power bus, a control bus, a status signal bus, etc., in addition to a data bus, although for clarity of illustration the various buses are referred to in FIG. 13 as the bus system.
The memory 1302 may include read-only memory (ROM) and Random Access Memory (RAM), and may also be other memories or storage media and provides instructions and data to the processor 1301. A portion of memory 1302 may also include non-volatile random access memory (NVRAM). The memory 1302 stores an operating system and operating instructions, executable modules or data structures, or a subset or an expanded set thereof, wherein the operating instructions may include various operating instructions for performing various operations. The operating system may include various system programs for implementing various basic services and for handling hardware-based tasks. The memory 1302 also stores data, programs, and the like according to the embodiments of the present application. The processor 1301 is configured to execute the program in the memory 1302 to perform the method performed by the first network device 1300 in each of the above embodiments.
Processor 1301 may be an integrated circuit chip having signal processing capabilities. In the implementation process of the embodiment of the present application, the steps performed by the first network device 1300 in the embodiment of the present application may be implemented by an integrated logic circuit of hardware in the processor 1301 or instructions in the form of software. The processor 1301 may be a general-purpose processor, a Digital Signal Processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 1302 or the processor 1301, and the processor 1301 reads information in the memory 1302 or itself, and completes the steps of the configuration method of the network device according to the embodiment in combination with hardware thereof.
The forwarding chip 1303 may be used to forward ethernet and other protocols such as Transmission Control Protocol/Internet Protocol (TCP/IP).
The communication port 1304 may be used to receive or transmit information/data.
In the above-described embodiments of the present application, the implementation may be wholly or partially realized by software, hardware, or a combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application are all or partially generated when the computer program instructions are loaded and executed on a computer, which may be through a computer, a special purpose computer, a computer network, or other editable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, such as: the computer instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center by wire (e.g., coaxial cable, twisted pair, fiber optics) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy disks, hard disks, magnetic tape), an optical medium (e.g., compact disks), or a semiconductor medium (e.g., Solid State Disks (SSDs)), among others.

Claims (21)

1. A method for configuring a network device, comprising:
the method comprises the steps that first network equipment obtains a first configuration file packet so that the first network equipment can analyze a configuration file of the first network equipment from the first configuration file packet, and configuration of the first network equipment is completed according to the configuration file obtained through analysis; the first configuration file packet comprises configuration files of all network devices in a network branch taking the first network device as a root node; the first network equipment extracts a second configuration file packet from the first configuration file packet, wherein the second configuration file packet comprises configuration files of all network equipment in a network branch taking the second network equipment as a root node, and the second network equipment is connected with the first network equipment;
the first network device sends the second profile packet to the second network device.
2. The method of claim 1, wherein prior to sending the second profile package, the method further comprises:
and the first network equipment receives a message which comes from the second network equipment and is used for requesting the configuration file of the second network equipment.
3. The method according to claim 1 or 2, further comprising the first network device obtaining a topology of a network leg having the first network device as a root node;
the extracting a second profile package from the first profile package comprises:
and the first network equipment extracts the second configuration file packet from the first configuration file packet according to the topology of the network branch taking the first network equipment as a root node.
4. The method of claim 1 or 2, wherein the second network device is connected to the first network device via at least two links, and wherein before sending the second profile packet, the method further comprises:
receiving at least two messages from the second network device via the at least two links;
the sending, by the first network device, the second profile packet to the second network device includes:
transmitting the second profile packet via only one of the at least two links.
5. The method of claim 1 or 2, wherein sending, by the first network device, the second profile packet to the second network device comprises:
and the first network equipment sends the second configuration file packet fragmented based on message length limitation to the second network equipment.
6. The method of claim 1 or 2, wherein prior to sending the second profile package, the method further comprises:
and the first network equipment sends a message indicating that the first network equipment can provide the configuration file to the second network equipment.
7. A network device, wherein the network device is a first network device, and wherein the first network device comprises:
the first obtaining unit is used for obtaining a first configuration file packet so that the first network equipment can analyze the configuration file of the first network equipment from the first configuration file packet and complete the configuration of the first network equipment according to the configuration file obtained by analysis; the first configuration file packet comprises configuration files of all network devices in a network branch taking the first network device as a root node;
an extracting unit, configured to extract a second configuration file packet from the first configuration file packet, where the second configuration file packet includes configuration files of all network devices in a network branch using a second network device as a root node, and the second network device is connected to the first network device;
a sending unit, configured to send the second profile packet to the second network device.
8. The network device of claim 7, further comprising:
a first receiving unit, configured to receive, before the sending unit sends the second profile packet, a message from the second network device and used for requesting the profile of the second network device.
9. The network device of claim 7 or 8, further comprising:
a second obtaining unit, configured to obtain a topology of a network branch using the first network device as a root node;
when the extracting unit is used for extracting the second configuration file package from the first configuration file package, the extracting unit is specifically configured to: and extracting the second configuration file packet from the first configuration file packet according to the topology of the network branch taking the first network equipment as a root node.
10. The network device of claim 7 or 8, wherein the second network device is connected to the first network device via at least two links, and wherein the first network device further comprises:
a second receiving unit, configured to receive at least two packets from the second network device via the at least two links before the sending unit sends the second profile packet;
when the sending unit executes sending of the second profile packet to the second network device, the sending unit is specifically configured to: transmitting the second profile packet via only one of the at least two links.
11. The network device according to claim 7 or 8, wherein the sending unit, when executing sending the second profile packet to the second network device, is specifically configured to: and sending the second configuration file packet fragmented based on message length limitation to the second network equipment.
12. The network device according to claim 7 or 8, wherein the sending unit is further configured to, before sending the second profile packet: and sending a message indicating that the first network equipment can provide the configuration file to the second network equipment.
13. A network device, wherein the network device is a first network device, and wherein the first network device comprises: a processor and a communication port; wherein the content of the first and second substances,
the processor is configured to: acquiring a first configuration file packet so as to analyze a configuration file of a first configuration file packet from the first configuration file packet, and completing configuration of the first network equipment according to the configuration file obtained by analysis; extracting a second profile packet from the first profile packet and sending the second profile packet to a second network device using the communication port;
the first configuration file packet comprises configuration files of all network devices in a network branch which takes the first network device as a root node; the second configuration file packet comprises configuration files of all network devices in a network branch taking the second network device as a root node; the second network device is connected to the first network device.
14. The network device of claim 13, wherein the processor is further configured to receive a message from the second network device requesting the profile of the second network device via the communication port before sending the second profile packet via the communication port.
15. The network device according to claim 13 or 14, wherein the processor is further configured to obtain a topology of a network leg having the first network device as a root node;
when the processor executes the extraction of the second configuration file package from the first configuration file package, the processor is specifically configured to: and extracting the second configuration file packet from the first configuration file packet according to the topology of the network branch taking the first network equipment as a root node.
16. The network device according to claim 13 or 14, wherein the second network device establishes at least two links with at least two communication ports of the first network device, and the processor is further configured to receive at least two packets from the second network device via the at least two links before sending the second profile packet via the communication ports;
wherein, when the processor executes the sending of the second profile packet to the second network device by using the communication port, the processor is specifically configured to: sending, by one of the at least two links, the second profile packet to the second network device.
17. The network device according to claim 13 or 14, wherein the processor, when executing sending the second profile packet to the second network device using the communication port, is specifically configured to:
and sending the second configuration file packet fragmented based on message length limitation to the second network equipment by using the communication port.
18. The network device of claim 13 or 14, wherein the processor is further configured to send a message to the second network device using the communication port indicating that the first network device is capable of providing a profile before sending the second profile packet using the communication port.
19. A method for configuring a network device, comprising:
the method comprises the steps that a first network device obtains a whole network configuration file packet so that the first network device can analyze a configuration file of the first network device from the whole network configuration file packet, and the configuration of the first network device is completed according to the configuration file obtained through analysis; the whole network configuration file packet comprises configuration files of all network devices in a network;
the first network equipment extracts a configuration file of second network equipment from the whole network configuration file packet, wherein the second network equipment comprises any network equipment except the first network equipment in the network;
the first network device sends the configuration file of the second network device to a third network device, and the third network device is located between the second network device and the first network device and connected with the first network device.
20. A network device, wherein the network device is a first network device, and wherein the first network device comprises:
the acquisition unit is used for acquiring a whole network configuration file packet so that the first network equipment can analyze a configuration file of the first network equipment from the whole network configuration file packet and complete the configuration of the first network equipment according to the configuration file obtained by analysis; the whole network configuration file packet comprises configuration files of all network devices in a network;
an extracting unit, configured to extract a configuration file of a second network device from the whole network configuration file packet, where the second network device includes any network device in the network except the first network device;
a sending unit, configured to send the configuration file of the second network device to a third network device, where the third network device is located between the second network device and the first network device and is connected to the first network device.
21. A network device, comprising: the network device is a first network device, and the first network device includes: a processor and a communication port; wherein the content of the first and second substances,
the processor is configured to: acquiring a whole network configuration file package so as to analyze a configuration file of the whole network configuration file package, and completing configuration of the first network equipment according to the configuration file obtained by analysis; extracting a configuration file of second network equipment from the whole network configuration file packet, and sending the configuration file of the second network equipment to third network equipment through the communication port;
the whole network configuration file package comprises configuration files of all network devices in a network; the second network device comprises any network device in the network except the first network device; the third network device is located between the second network device and the first network device and is connected with the first network device.
CN201710822403.8A 2017-09-13 2017-09-13 Network equipment configuration method and network equipment Active CN109495285B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710822403.8A CN109495285B (en) 2017-09-13 2017-09-13 Network equipment configuration method and network equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710822403.8A CN109495285B (en) 2017-09-13 2017-09-13 Network equipment configuration method and network equipment

Publications (2)

Publication Number Publication Date
CN109495285A CN109495285A (en) 2019-03-19
CN109495285B true CN109495285B (en) 2020-12-15

Family

ID=65687378

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710822403.8A Active CN109495285B (en) 2017-09-13 2017-09-13 Network equipment configuration method and network equipment

Country Status (1)

Country Link
CN (1) CN109495285B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103095495A (en) * 2013-01-06 2013-05-08 华为技术有限公司 Network implementation configuration method, device and system
CN104301141A (en) * 2014-10-10 2015-01-21 华为技术有限公司 Method, device and system for storing configuration information
CN104639348A (en) * 2013-11-07 2015-05-20 华为技术有限公司 Network device and configuration method thereof

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012106883A1 (en) * 2011-07-12 2012-08-16 华为技术有限公司 Method, apparatus and system for initial deployment of layer 2 network device
US10285058B2 (en) * 2015-01-09 2019-05-07 Comcast Cable Communications, Llc Providing secure Wi-Fi in an open Wi-Fi environment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103095495A (en) * 2013-01-06 2013-05-08 华为技术有限公司 Network implementation configuration method, device and system
CN104639348A (en) * 2013-11-07 2015-05-20 华为技术有限公司 Network device and configuration method thereof
CN104301141A (en) * 2014-10-10 2015-01-21 华为技术有限公司 Method, device and system for storing configuration information

Also Published As

Publication number Publication date
CN109495285A (en) 2019-03-19

Similar Documents

Publication Publication Date Title
CN107800602B (en) Message processing method, device and system
EP3195566B1 (en) Service layer interworking using mqtt protocol
US10439931B2 (en) Data packet processing method, service node, and delivery node
US20160285820A1 (en) Method for processing address resolution protocol message, switch, and controller
CN111490893B (en) Method, device and system for establishing network forwarding model
WO2014101394A1 (en) Method, device and system for transmitting message in virtual extensible local area network
WO2016112869A1 (en) Access point management
EP3651040A1 (en) Apparatus and method for remotely managing devices, and program therefor
EP3007389A1 (en) Gre tunnel implementation method, access point and gateway
CN110235417B (en) SDN and message forwarding method and device thereof
CN109495285B (en) Network equipment configuration method and network equipment
Do et al. SDN/NFV based Internet of Things for multi-tenant networks
EP3220584A1 (en) Wifi sharing method and system, home gateway and wireless local area network gateway
KR102503257B1 (en) Apparatus and method for bluetooth communication
WO2022048430A1 (en) Method for uploading configuration file, method for downloading configuration file, and apparatus
US10298454B2 (en) Communication path switching apparatus, method for controlling communication path switching apparatus, and computer program product
CN112995007B (en) Cloud private line connection method and system
WO2020119824A1 (en) Device control method and apparatus, control node, network device, and data center
WO2016189884A1 (en) Packet relay apparatus and packet relay method
WO2016184025A1 (en) Device management method and apparatus
EP3726789A1 (en) Load sharing method, device, and system and computer readable storage medium
TWI608749B (en) Method for controlling a client device to access a network device, and associated control apparatus
KR102385707B1 (en) SDN network system by a host abstraction and implemented method therefor
CN111510511A (en) Data reporting network creating method, data reporting method and related equipment
CN109672593B (en) PPPoE message processing method and device and broadband remote access server

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant