CN108259228B

CN108259228B - Network equipment virtualization system and equipment configuration method and device thereof

Info

Publication number: CN108259228B
Application number: CN201711410323.8A
Authority: CN
Inventors: 朱武杰
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: Hangzhou H3C Technologies Co Ltd
Priority date: 2017-12-22
Filing date: 2017-12-22
Publication date: 2021-06-08
Anticipated expiration: 2037-12-22
Also published as: CN108259228A

Abstract

The embodiment of the application provides a network equipment virtualization system and an equipment configuration method and device thereof. The network equipment virtualization system comprises a CB equipment and more than one PE equipment, wherein the CB equipment is used for connecting and managing the more than one PE equipment. After the PE equipment to be configured is communicated with the cascade port of the CB equipment, the CB equipment transmits a configuration file which is stored by the CB equipment and corresponds to the PE equipment to be configured through the cascade port; the configuration file at least comprises at least one preset basic configuration information for the PE equipment to be configured. And when the PE equipment to be configured receives the configuration file, executing configuration operation according to the configuration information in the configuration file. According to the embodiment of the application, the time for issuing the configuration by the CB equipment can be shortened, and the configuration efficiency is improved.

Description

Network equipment virtualization system and equipment configuration method and device thereof

Technical Field

The present application relates to the field of communications technologies, and in particular, to a network device virtualization system and a device configuration method and apparatus thereof.

Background

With the development of internet technology, the traditional data center faces many challenges, such as poor expandability, slow service deployment, difficult management and control, and the like. In order to improve the network management efficiency, network device virtualization technologies have been developed, and the 802.1BR protocol is one of the virtualization technologies. The cascade connection of all network devices can be realized through the 802.1BR protocol, and all network devices are virtualized into one network device.

Currently, a network system based on the 802.1BR protocol logically includes: CB (control Bridge) devices and PE (Port Extender) devices. The CB device is used for connecting and managing the PE device. The PE equipment operates as a remote service board of the CB equipment, which is equivalent to a service board inserted in a specified slot position of the CB equipment.

Each PE device accessing the CB device can normally operate only by configuring corresponding configuration information, which is usually recorded in the CB device and sent to the corresponding PE device by the CB device in the form of a protocol packet. However, the data volume that each protocol packet can carry is limited, and when the data volume of the configuration information is large, the configuration information can be issued only by sending the protocol packet for many times, which consumes a long time and has low efficiency.

Disclosure of Invention

In view of the above, an object of the present application is to provide a method and an apparatus for configuring a PE, and a CB device, so as to increase the issuing speed of configuration information.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, an embodiment of the present application provides a network device virtualization system, which includes a CB device and one or more PE devices, where the CB device is configured to connect to and manage the one or more PE devices. After the PE equipment to be configured is communicated with the cascade port of the CB equipment, the CB equipment transmits a configuration file which is stored by the CB equipment and corresponds to the PE equipment to be configured through the cascade port; the configuration file at least comprises at least one preset basic configuration information aiming at the PE equipment to be configured; and when the PE equipment to be configured receives the configuration file, executing configuration operation according to the configuration information in the configuration file.

In a second aspect, an embodiment of the present application provides a device configuration method, which is applied to a network device virtualization system including a CB device and one or more PE devices, where the CB device is configured to connect and manage the PE devices, and the method includes:

after the PE equipment to be configured is communicated with the cascade port of the CB equipment, the CB equipment transmits the configuration file which is stored by the CB equipment and corresponds to the PE equipment to be configured through the cascade port; the configuration file at least comprises at least one preset basic configuration information aiming at the PE equipment to be configured; and

and when the PE equipment to be configured receives the configuration file, executing configuration operation according to the configuration information in the configuration file.

In a third aspect, an embodiment of the present application provides an apparatus configuration device, which is applied to a CB device, where the CB device is configured to connect and manage more than one PE device. The device configuration apparatus includes: the configuration module is used for transmitting a configuration file which is stored in the CB device and corresponds to the PE device to be configured through the cascade port after the PE device to be configured is communicated with the cascade port of the CB device; the configuration file at least comprises at least one preset basic configuration information for the PE equipment to be configured.

According to the network device virtualization system and the device configuration method and device thereof provided by the embodiment of the application, after the PE device to be configured is communicated with the cascade port of the CB device, the configuration file corresponding to the PE device to be configured and stored in the CB device is transmitted to the PE device to be configured through the cascade port, the configuration is not required to be issued through a protocol message every time, the time for the CB device to issue the configuration to the PE device to be configured is shortened, the configuration efficiency is improved, and the PE device to be configured can start to operate more quickly.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.

Fig. 1 is a schematic diagram of a network device virtualization system including a CB device and a PE device according to an embodiment of the present disclosure;

fig. 2 is another schematic diagram of a network device virtualization system including a CB device and a PE device according to an embodiment of the present disclosure;

fig. 3 is a schematic block diagram of a CB device according to an embodiment of the present disclosure;

fig. 4 is a functional block diagram of an apparatus configuration device according to an embodiment of the present application;

fig. 5 is a schematic flowchart of a device configuration method according to an embodiment of the present application;

fig. 6 is another schematic flow chart of a device configuration method according to an embodiment of the present application;

fig. 7 is another schematic flow chart of a device configuration method according to an embodiment of the present application.

Icon: 10-a network device virtualization system; 100-CB equipment; 110-a device configuration means; 111-configuration module; 112-a first save module; 113-a second save module; 114-a third save module; 115-a fourth save module; 120-a memory; 130-a processor; 140-an interface unit; 150-a communication unit; 200-PE devices.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.

Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.

The inventor finds that, in the existing device configuration method, the CB device generally sends configuration information to each PE device through a protocol packet, so as to configure each PE device. However, each message has limited data to carry, and when the amount of configuration information data to be sent is large, the protocol message needs to be sent many times to complete sending of the configuration information, which is very tedious. In addition, since the content sent by each packet is limited, when sending a certain configuration information to the PE device, it takes time to split the configuration information, and the PE device also needs to take time to integrate after receiving all the content of the configuration information. Therefore, the issuing speed of the configuration information is slow, so that the PE device is difficult to complete the configuration quickly, and is also difficult to operate quickly.

In order to solve the above problems, the inventor proposes a device configuration method, an apparatus, and a CB device, and stores configuration information required by a PE device in the CB device in the form of a configuration file, and directly sends the configuration file to the PE device to be configured when necessary, thereby avoiding splitting the configuration information into multiple parts and then sending the split configuration information through a message, so as to improve the sending efficiency of the configuration information. As will be explained in detail below.

Fig. 1 and fig. 2 are schematic diagrams of a network device virtualization system 10 including a CB device 100 and a PE device 200 according to an embodiment of the present disclosure.

For example, as shown in fig. 1, in order to implement management of the PE devices 200, a network device virtualization system 10 may be formed by connecting one CB device 100 with one or more PE devices 200, and the CB device 100 implements management of the one or more PE devices 200.

Each PE device 200 is connected to the CB device 100, and provides a port expansion function for the CB device 100. The CB device 100 serves as a management and control party of all the PE devices 200, and is responsible for configuring and managing the PE devices 200. The PE device 200 serves as a remote service board of the CB device 100 and is responsible for transmitting the packet to the CB device 100 for processing.

In this embodiment, the CB device 100 is provided with configuration information required by the PE device 200 to operate, for example, a relevant configuration of an Access Control List (ACL), a relevant configuration of a Virtual Local Area Network (VLAN), a relevant configuration of a multicast routing protocol, a relevant configuration of a quality of service (QoS) policy, a relevant configuration of a port, and the like.

As shown in fig. 2, a plurality of CB devices may be stacked to form a logical CB device 100, so as to manage the PE device 200. Wherein each CB device in the stack is connected with each PE device 200 to form the network device virtualization system 10.

In summary, in the present embodiment, the "CB device 100" may be an independent CB device 100 shown in fig. 1, or may be a logical CB device 100 formed by stacking a plurality of CB devices shown in fig. 2.

Please refer to fig. 3, which is a block diagram of the CB apparatus 100 according to an embodiment of the present disclosure. The CB device 100 may include a device configuration apparatus 110, a memory 120, a processor 130, an interface unit 140, and a communication unit 150.

The components of the memory 120, the processor 130, the interface unit 140 and the communication unit 150 are electrically connected to each other directly or indirectly to realize data interaction. For example, these components may be electrically connected to each other via one or more communication or signal buses. The device configuration means 110 comprises one or more Software functional modules which may be stored in the memory 120 in the form of Software (Software) or Firmware (Firmware) or solidified in an Operating System (OS) of the CB device 100.

The processor 130 is used for executing executable modules stored in the memory 120, such as software functional modules and computer programs included in the device configuration apparatus 110.

The interface unit 140 includes ports for connecting the CB device 100 and the PE device 200, and the communication unit 150 is configured to establish a communication connection between the CB device 100 and an external device (including the PE device 200, etc.), so as to implement data communication and interaction with the external device.

It should be understood that the illustration of fig. 3 is merely for illustrative purposes and that the CB device 100 may have more or fewer components than shown in fig. 3 or may have a completely different configuration than shown in fig. 3. In addition, each component shown in fig. 3 may be implemented by software, hardware, or a combination thereof, and the present embodiment is not limited thereto.

A device configuration method based on the network device virtualization system 10 according to the embodiment of the present application will be described in detail below with reference to the network device virtualization system 10 shown in fig. 1 or fig. 2. In this embodiment, the device configuration method includes the following steps.

After the PE device 200 to be configured is communicated with the cascade port of the CB device 100, the configuration file stored in the CB device 100 and corresponding to the PE device 200 to be configured is transmitted to the PE device 200 to be configured through the cascade port.

The cascade interface of the CB device 100 is a physical interface on the CB device 100.

In one example, after the PE device 200 to be configured accesses the CB device 100, a request message is usually sent to the CB device 100 to request the CB device 100 to allocate a corresponding virtual slot number. The request message carries the MAC address of the PE device 200 to be configured, and the CB device 100 allocates a virtual slot number to the PE device 200 to be configured after receiving the request message, and binds the allocated virtual slot number with the MAC address of the PE device 200 to be configured. The virtual slot number, the MAC address, and the PE device 200 to be configured are in a one-to-one correspondence relationship. In this manner, a communication link between the PE device 200 to be configured and the CB device 100 is established.

In this embodiment, the communication between the PE device 200 to be configured and the cascade interface of the CB device 100 may refer to the successful establishment of a link between the PE device 200 to be configured and the cascade interface of the CB device 100.

In this embodiment, the configuration file at least includes at least one kind of basic configuration information that is preset for the PE device 200 to be configured.

The basic configuration information includes configuration information required to be synchronized to each PE device 200 connected to the CB device 100, such as the above-mentioned configuration related to the ACL, the configuration related to the VLAN, the configuration related to the multicast routing protocol, the configuration related to the QoS policy, and the like. It should be noted that, in the present embodiment, the port configuration information (e.g., port communication rate, etc.) varies with port variation, and thus, the port configuration information does not belong to the basic configuration information.

The inventor finds that the data size of the basic configuration information is usually large, and the basic configuration information sent to each PE device 200 is basically the same, so that if some or all of the basic configuration information is stored in a file in advance, and then the file is sent to the PE device 200 to be configured once when the PE device 200 to be configured is communicated with the cascade port of the CB device 100, the efficiency of sending the configuration information can be greatly improved.

Optionally, in this embodiment, the configuration file may be a basic configuration file including at least one type of basic configuration information. Wherein the base configuration file may be a file including only base configuration information. In general, when the CB device 100 configures a PE Group (PE Group), a basic configuration file including at least one basic configuration information may be first saved in the CB device 100.

In an existing 802.1 BR-based network system, a PE group is generally configured on the CB device 100, and each PE group may be configured to drop multiple PE devices 200. In practical applications, when a user configures a PE group on the CB device 100, it indicates that the user wishes to load the PE devices 200 through the CB device 100 for vertical stacking, and at first, basic information configuration needs to be performed on each PE device 200. Thus, at this time, a basic configuration file including at least one kind of basic configuration information may be saved in the CB device 100.

Moreover, since the basic configuration file is applicable to each PE device 200, only one basic configuration file may be saved, and it is not necessary to save one basic configuration file for each PE device 200, thereby saving storage space.

Optionally, before saving the base profile, a folder for saving the base profile may be created, the folder may be named a specific name (e.g., 1br. cfg), and other related profiles may be saved in the folder. Thus, centralized searching is facilitated when the configuration file needs to be sent.

Alternatively, the folder may be established in Flash of the CB device 100, i.e. the configuration files saved in the CB device 100 may be saved in its Flash. In this way, even if the CB device 100 is restarted, the saved configuration file is not lost.

In this embodiment, the PE device 200 that needs to be configured may have multiple situations, that is, the PE device 200 to be configured may include the PE device 200 in multiple situations, which will be described in detail below.

In one embodiment, the PE device 200 to be configured may be a newly online PE device 200 connected to the CB device 100 for the first time.

Since the port configuration information may be different according to the different ports connected to the PE device 200 to be configured, the connected port is unknown before the newly online PE device 200 is online, and the port configuration information cannot be determined, and cannot be stored in advance.

Therefore, the configuration file corresponding to the newly online PE device 200 may be a basic configuration file, that is, when the newly online PE device 200 is connected to the cascade port of the CB device 100, the CB device 100 sends the basic configuration file to the PE device 200 to be configured (the newly online PE device 200) to perform basic information configuration.

In practical application, the port configuration information of each PE device 200 is usually set by a user in the CB device 100 before or during access of the PE device 200, and then sent to the PE device 200 by the CB device 100 through a protocol packet. In this embodiment, after obtaining the port configuration information of the newly online PE device 200, the CB device 100 may send the port configuration information to the newly online PE device 200 through a protocol message, or may directly save the obtained port configuration information as a configuration file and send the configuration file to the newly online PE device 200 once again. Specifically, what manner is adopted to send the port configuration information to the newly online PE device 200 may be determined according to the size of the port configuration information.

In this embodiment, after receiving the basic configuration file, the PE device 200 to be configured may perform a configuration rollback operation according to the basic configuration file, so as to perform configuration according to the configuration information in the basic configuration file. The configuration rollback operation means that the PE device to be configured performs a configuration operation according to the configuration information in the configuration file, so that the configuration of the PE device returns to the configuration state in the configuration file.

After the PE device 200 to be configured completes the configuration corresponding to the basic configuration file, the configuration feedback signal may be returned to the CB device 100, so that the CB device 100 continues to issue other required configuration information (e.g., port configuration information) to the PE device 200 to be configured.

It should be understood that after a certain PE device 200 first comes online, if relevant information (e.g., correspondence between MAC address and virtual slot number, configuration information, etc.) in the CB device 100 is deleted, the PE device 200 may also be regarded as a newly brought online PE device 200 when the CB device 100 is connected later by the PE device 200.

In the following manner, it can be determined whether a PE device 200 is a newly online PE device 200 that establishes a connection with the CB device 100 for the first time.

For example, when any PE device 200 is connected to the CB device 100, it may be determined whether a virtual slot number corresponding to the MAC address of the PE device 200 is recorded in the CB device 100, and if not, it may be determined that the PE device 200 is a newly online PE device 200. Otherwise, the PE device 200 is not a new PE device 200 online.

In practical applications, when a power outage occurs or the CB device 100 malfunctions, the CB device 100 needs to be restarted. When the CB device 100 is restarted, the PE device 200, which remains connected to the CB device 100, needs to be reconfigured.

Therefore, in another specific embodiment, the PE devices 200 to be configured further include each PE device 200 connected to the CB device 100 after the CB device 100 is restarted.

For this case, before the CB device 100 is restarted, for each PE device 200 connected to the CB device 100, a configuration file corresponding to the PE device 200 is saved in the CB device 100.

The configuration file corresponding to each PE device 200 may include at least one basic configuration information in the basic configuration file. As for the configuration information (e.g., port configuration information) of each PE device 200 that is not globally synchronized may still be issued through the protocol packet, in this case, the configuration file corresponding to the PE device 200 may further include the configuration information that is issued to the PE device 200 by the CB device 100 through the protocol packet.

In this way, after the CB device 100 is restarted, for each PE device 200 connected to the CB device 100, the configuration file corresponding to the PE device 200 stored in the CB device 100 may be issued to the PE device 200, so that the PE device 200 completes the corresponding configuration according to the received configuration file.

It is considered that each PE device 200 connected before the CB device 100 restarts performs at least one configuration, that is, the configuration information of each PE device 200 before the restart includes both the basic configuration information and the non-globally synchronized configuration information. Therefore, the non-globally synchronized configuration information of each PE device 200 may also be saved in the configuration file corresponding to the PE device 200. In the CB device 100, the saved configuration file corresponding to each PE device 200 may be named by using a slot number or other device identifier corresponding to each PE device 200, respectively, so as to distinguish the configuration files corresponding to different PE devices 200. Thus, after the CB device 100 is restarted, the configuration file corresponding to the PE device 200 may be found according to the slot number corresponding to the PE device 200, and rapid configuration may be performed.

Thus, after the CB device 100 is restarted, the configuration file only needs to be sent once through the cascade interface for each connected PE device 200.

Optionally, in this embodiment, before the CB device 100 is restarted, the restart instruction may be executed within a first preset time period. For example, when the restart instruction is generated (e.g., the reset button is pressed), the restart procedure may be executed with a delay of a first preset duration, and the CB device 100 may perform the operation of saving the configuration file within the first preset duration. The preset duration may be flexibly set according to an actual situation, for example, the preset duration may be set according to a data size of the configuration information.

In addition, in practical applications, each PE device 200 may be restarted due to a power failure, a device failure, or a link failure, and after the PE device 200 is restarted, the CB device 100 needs to be reconfigured.

Thus, in another embodiment, the PE device 200 to be configured may further include a restarted PE device 200 connected to the CB device 100.

For this situation, before any PE device 200 connected to the CB device 100 is restarted, a configuration file corresponding to the PE device 200 may be stored in the CB device 100. Accordingly, the configuration file may also be named using the slot number or other device identifier of the corresponding PE device 200 to distinguish it from other configuration files stored in the CB device 100. Thus, after the PE device 200 is restarted, the configuration file corresponding to the PE device 200 can be found according to the slot number or other device identifier corresponding to the PE device 200, and rapid configuration is performed.

In this way, after the PE device 200 is restarted, the CB device 100 may send the stored configuration file corresponding to the PE device 200 through the cascade interface, so that the PE device 200 performs configuration according to the configuration file.

In this embodiment, the configuration file corresponding to the PE device 200 (the restarted PE device 200) includes the at least one piece of basic configuration information in the basic configuration file. Thus, after the PE device 200 receives the configuration file sent by the CB device 100 and performs configuration, at least the basic configuration before the restart can be recovered. As for configuration information that is not globally synchronized, such as port configuration information, the CB device 100 may issue a protocol packet.

The PE device 200 may have been configured at least once before the restart, and thus, the configuration information of the PE device 200 may include the basic configuration information and the non-globally synchronized configuration information. Correspondingly, the configuration file corresponding to the PE device 200 may further include non-globally synchronized configuration information, for example, the configuration information that is issued to the PE device 200 by the CB device 100 through a protocol packet.

Optionally, in this embodiment, before any PE device 200 connected to the CB device 100 is restarted, the time duration may be within a second preset time duration before the PE device 200 executes the restart instruction. For example, when the restart instruction is generated, the PE device 200 may delay the execution of the restart instruction for the second preset time period (e.g., 2 seconds), and execute the saving operation of the configuration file within the second preset time period.

Further, the CB device 100 may store the configuration information sent to each PE device 200 through the protocol packet into the configuration file corresponding to the corresponding PE device 200, so as to ensure that all the current configuration information of each PE device 200 is always recorded in the CB device 100. Therefore, no matter the CB device 100 is restarted or any PE device 200 is restarted, the corresponding configuration file can be issued through the cascade interface in time, so as to quickly recover the service operation.

In order to ensure that other configuration information issued by the CB device 100 through the protocol each time can be timely recorded in the corresponding configuration file, in this embodiment, after the CB device 100 issues the configuration information to any one of the PE devices 200 connected to the CB device 100 through the protocol packet to configure the PE device 200, a configuration file corresponding to the PE device 200 may be stored in the CB device 100, and the configuration file corresponding to the PE device 200 includes the at least one piece of basic configuration information in the basic configuration file and the configuration information issued by the CB device 100 to the PE device 200 through the protocol packet. The configuration file may also be named by a slot number or other device identification information corresponding to the PE device 200 to distinguish it from other configuration files.

Optionally, in this embodiment, the configuration File corresponding to each PE device 200 and the basic configuration File may be text files, and the CB device 100 may transmit the configuration File corresponding to the PE device 200 to be configured through a cascade interface by using a File Transfer protocol such as ftp (File Transfer protocol) or tftp (trivial File Transfer protocol). Therefore, the transmission time can be reduced, and the configuration efficiency can be improved.

Referring to fig. 4, a functional block diagram of an apparatus configuration device 110 according to an embodiment of the present application is shown, where the apparatus configuration device 110 is applied to the CB apparatus 100 shown in fig. 3.

In the present embodiment, the device configuration apparatus 110 includes a configuration module 111.

The configuration module 111 is configured to transmit, after the PE device 200 to be configured is communicated with the cascade port of the CB device 100, the configuration file stored in the CB device 100 and corresponding to the PE device 200 to be configured through the cascade port.

Optionally, the device configuration apparatus 110 may further include a first saving module 112.

The first saving module 112 is configured to save a basic configuration file including at least one basic configuration information in the CB device 100 when the CB device 100 configures a PE Group (PE-Group).

Alternatively, the PE device 200 to be configured may include a newly online PE device 200 that is first connected with the CB device 100. Wherein, the configuration file corresponding to the newly online PE device 200 may be a basic configuration file.

Optionally, in this embodiment, the PE devices 200 to be configured may further include each PE device 200 connected to the CB device 100 after the CB device 100 is restarted. In this case, the device configuration apparatus 110 may further include a second saving module 113.

The second saving module 113 is configured to, before the CB device 100 is restarted, save, in the CB device 100, a configuration file corresponding to the PE device 200 for each PE device 200 connected to the CB device 100.

The configuration file corresponding to the PE device 200 includes at least one basic configuration information in the basic configuration file. Optionally, the configuration file corresponding to the PE device 200 may further include configuration information that is issued by the CB device 100 to the PE device 200 through a protocol packet.

Optionally, in this embodiment, the PE device 200 to be configured may further include a restarted PE device 200 connected to the CB device 100. In this case, the device configuration apparatus 110 may further include a third saving module 114.

The third saving module 114 is configured to save, in the CB device 100, a configuration file corresponding to any PE device 200 connected to the CB device 100 before the PE device 200 is restarted.

The configuration file corresponding to the PE device 200 includes at least one type of configuration information in the basic configuration file. Optionally, the configuration file corresponding to the PE device 200 may further include configuration information that is issued by the CB device 100 to the PE device 200 through a protocol packet.

Optionally, in this embodiment, the device configuration apparatus 110 may further include a fourth saving module 115.

The fourth saving module 115 is configured to save, in the CB device 100, a configuration file corresponding to the PE device 200 after the CB device 100 issues configuration information to any PE device 200 connected to the CB device 100 through a protocol packet to configure the PE device 200.

The configuration file includes at least one of basic configuration information in the basic configuration file and configuration information that the CB device 100 issues to the PE device 200 through a protocol packet.

With reference to fig. 5 to fig. 7, a detailed process of the device configuration method provided in this embodiment of the present application is illustrated for several cases where the PE device 200 needs to be configured and issued with a configuration file.

First, referring to fig. 5, fig. 5 is a detailed flowchart of a device configuration method when the CB device 100 performs PE group configuration on a plurality of PE devices 200.

In step S501, the first storing module 112 stores a basic configuration file including at least one basic configuration information in the CB device 100.

Step S502, after the multiple PE devices 200 in the PE group are communicated with the CB device 100 through the cascade port, the configuration module 111 sends the basic configuration file to each PE device 200 in the PE group through the cascade port, respectively, so as to configure each PE device 200.

In step S503, each PE device 200, upon receiving the basic configuration file, performs configuration rollback on the basic configuration file to complete the configuration.

It should be noted that, in the method shown in fig. 5, each PE device 200 in the PE group may be understood as a new online PE device 200, and accordingly, the configuration file corresponding to each PE device 200 is a basic configuration file.

Secondly, after the CB device 100 completes the PE group configuration of the multiple PE devices 200, and after the newly online PE device 200 is connected to the CB device 100, the basic configuration file may be directly sent to the newly online PE device 200 through the cascade interface, which is not described in detail herein.

Again, referring to fig. 6, fig. 6 is a detailed flowchart of a device configuration method in the case where the CB device 100 needs to be restarted.

In step S601, before the CB device 100 is restarted, for each PE device 200 connected to the CB device 100, the second saving module 113 saves a configuration file corresponding to the corresponding PE device 200 in the CB device 100.

Step S602, after the CB device 100 is restarted, for each PE device 200 connected to the cascade port of the CB device 100, the configuration module 111 sends the corresponding configuration file stored in the CB device 100 to the PE device 200 through the cascade port.

In step S603, after each PE device 200 connected to the cascade port of the CB device 100 receives the corresponding configuration file, it performs configuration rollback to complete configuration.

Further, referring to fig. 7, fig. 7 is a detailed flowchart of a device configuration method in a case where any PE device 200 connected to the CB device 100 needs to be restarted.

In step S701, before any PE device 200 (hereinafter referred to as a target PE device 200) is restarted, the third saving module 114 saves a configuration file corresponding to the target PE device 200 in the CB device 100.

In step S702, after the target PE device 200 is restarted and is connected to the cascade port of the CB device 100, the configuration module 111 sends the configuration file corresponding to the target PE device 200 stored in the CB device 100 to the target PE device 200 through the cascade port.

In step S703, when receiving the corresponding configuration file, the target PE device 200 performs configuration rollback to complete configuration.

To sum up, according to the network device virtualization system 10 and the device configuration method and apparatus provided in the embodiment of the present application, after the PE device 200 to be configured is communicated with the cascade port of the CB device 100, the configuration file stored in the CB device 100 and corresponding to the PE device 200 to be configured is transmitted to the PE device 200 to be configured through the cascade port, so that the time for the CB device 100 to issue the configuration to the PE device 200 to be configured is reduced, thereby improving the configuration efficiency, and enabling the PE device 200 to be configured to start operating more quickly.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which protects one or more executable instructions for implementing the corresponding logical function(s).

It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

Finally, it should be noted that the above-mentioned embodiments illustrate only the preferred embodiments of the present application, and are not intended to limit the present application, and that various modifications and changes can be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A network device virtualization system includes a CB device for connecting and managing one or more PE devices and one or more PE devices,

after the PE equipment to be configured is communicated with the cascade port of the CB equipment, the CB equipment transmits the configuration file which is stored by the CB equipment and corresponds to the PE equipment to be configured through the cascade port; the configuration file at least comprises at least one preset basic configuration information aiming at the PE equipment to be configured;

2. The network device virtualization system of claim 1 wherein the CB device stores a base configuration file comprising the at least one base configuration information therein when the CB device is configuring the PE group.

3. The network device virtualization system of claim 2, wherein the PE device to be configured comprises a new online PE device that is connected to the CB device for the first time, wherein the configuration file corresponding to the new online PE device is the basic configuration file.

4. The network device virtualization system of claim 2, wherein the PE devices to be configured comprise each PE device connected to the CB device in the system after the CB device is restarted; before restarting, the CB device stores, in the CB device, a configuration file corresponding to each PE device connected to the CB device, where the configuration file corresponding to the PE device includes the at least one piece of basic configuration information in the basic configuration file.

5. The network device virtualization system of claim 2 wherein the PE device to be configured comprises a restarted PE device connected to the CB device in the system; before any PE device connected with the CB device is restarted, a configuration file corresponding to the PE device is saved in the CB device, and the configuration file corresponding to the PE device comprises the at least one type of basic configuration information in the basic configuration file.

6. The network device virtualization system according to any one of claims 2 to 5, wherein the CB device issues configuration information to any one of the PE devices connected to the CB device through a protocol packet to configure the PE device, and then stores a configuration file corresponding to the PE device in the CB device, where the configuration file includes the at least one of the basic configuration files and the configuration information that the CB device issues to the PE device through the protocol packet.

7. A device configuration method is applied to a network device virtualization system comprising a CB device and more than one PE device, wherein the CB device is used for connecting and managing the PE devices, and the method comprises the following steps:

8. The device configuration method of claim 7, wherein the method further comprises:

and when the CB equipment configures the PE group, storing a basic configuration file comprising the at least one basic configuration information in the CB equipment.

9. The device configuration method according to claim 8, wherein the PE device to be configured includes a new online PE device that is connected to the CB device for the first time, and wherein the configuration file corresponding to the new online PE device is the basic configuration file.

10. The device configuration method according to claim 8, wherein the PE devices to be configured include each PE device connected to the CB device in the network device virtualization system after the CB device is restarted, the method further comprising: before the CB equipment is restarted, aiming at each PE equipment connected with the CB equipment, storing a configuration file corresponding to the PE equipment in the CB equipment, wherein the configuration file corresponding to the PE equipment comprises the at least one type of basic configuration information in the basic configuration file;

the PE device to be configured further includes a restarted PE device connected to the CB device in the network device virtualization system, and the method further includes: before any PE device connected with the CB device is restarted, a configuration file corresponding to the PE device is saved in the CB device, and the configuration file corresponding to the PE device comprises the at least one type of basic configuration information in the basic configuration file.

11. The device configuration method according to any of claims 8-10, wherein the method further comprises:

after the CB equipment issues configuration information to any PE equipment connected with the CB equipment through a protocol message to configure the PE equipment, a configuration file corresponding to the PE equipment is stored in the CB equipment, wherein the configuration file comprises the at least one basic configuration information in the basic configuration file and the configuration information issued to the PE equipment by the CB equipment through the protocol message.

12. An apparatus configuration device, applied to a CB device, where the CB device is configured to connect and manage more than one PE device, and the apparatus configuration device includes:

the configuration module is used for transmitting a configuration file stored in the CB device and corresponding to the PE device to be configured through a cascade port after the PE device to be configured is communicated with the cascade port of the CB device;

wherein the configuration file at least comprises at least one preset basic configuration information for the PE device to be configured.

13. The device configuration apparatus of claim 12, further comprising:

a first storing module, configured to store, in the CB device, a basic configuration file including the at least one basic configuration information when the CB device configures the PE group;

the PE equipment to be configured comprises newly online PE equipment which is connected with the CB equipment for the first time, wherein the configuration file corresponding to the newly online PE equipment is the basic configuration file.

14. The device configuration apparatus of claim 13, further comprising:

a second saving module, configured to, before the CB device is restarted, save, in the CB device, a configuration file corresponding to the PE device for each PE device connected to the CB device, where the configuration file corresponding to the PE device includes at least one piece of basic configuration information in the basic configuration files; the PE equipment to be configured comprises each PE equipment connected with the CB equipment after the CB equipment is restarted; and

a third storing module, configured to store, in any PE device connected to the CB device, a configuration file corresponding to the PE device before the PE device is restarted, where the configuration file corresponding to the PE device includes the at least one piece of basic configuration information in the basic configuration file; the PE equipment to be configured further comprises restarted PE equipment connected with the CB equipment.

15. The device configuration apparatus according to claim 13 or 14, further comprising:

and a fourth storing module, configured to store, in the CB device, a configuration file corresponding to any PE device connected to the CB device after the CB device issues configuration information to the PE device through a protocol packet to configure the PE device, where the configuration file includes the at least one piece of basic configuration information in the basic configuration file and the configuration information that the CB device issues to the PE device through the protocol packet.