Device Stacking Method, Apparatus and Border Device

Abstract

The embodiment of the present application relates to a device stacking method, apparatus and boundary device. The method includes: receiving a stacking request sent by a second device; comparing the role type information of a first device with the role type information of the second device, and comparing the identification information corresponding to the first device with the identification information corresponding to the second device; when it is determined that the role type information of the first device is the same as the role type information of the second device, and the identification information corresponding to the first device is the same as the identification information corresponding to the second device, perform a stacking operation with the second device. In this way, it can be identified whether a certain boundary device and the adjacent boundary device belong to the same physical connection domain. And for stacking, only devices of the same role type can perform the stacking operation. Therefore, it is also necessary to determine whether the two devices are of the same role type. Only when both conditions are met can the stacking operation be performed to achieve the expected stacking effect.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies, and in particular, to a device stacking method, apparatus, and border device. Background Art

[0002] Automatically deploying the Underlay function, also known as Zero Touch Provisioning (ZTP), refers to the function of automatically loading version files (including system software, template configuration information, and license files) when a newly manufactured or empty-configured device is powered on and started. In the traditional deployment mode, after the hardware installation of a newly manufactured or empty-configured device is completed, an administrator needs to manually configure each device, which not only affects the deployment efficiency but also requires a high labor cost.

[0003] In the current Software Defined Network (SDN) networking, the SDN controller already supports automatic deployment. However, in a multi-Fabric / DC (Fabric is a virtual physical connectivity domain, and DC, i.e., DataCenter, represents a data center, which is uniformly managed by an SDN controller cluster and can include one or more Fabrics) networking, border devices are expected to stack with adjacent border devices in the same Fabric. However, in actual situations, the border devices adjacent to a certain border device may include devices in other Fabrics in addition to the devices in the same Fabric as it. It is precisely because a certain border device cannot well distinguish whether the adjacent border devices belong to the same Fabric as itself that the expected stacking effect cannot be achieved finally. Summary of the Invention

[0004] The present application provides a device stacking method, apparatus, and border device to solve some or all of the technical problems in the prior art.

[0005] In a first aspect, the present application provides a device stacking method, which is executed by a first device and includes:

[0006] Receiving a stacking request sent by a second device, where the stacking request includes identification information and role type information corresponding to the second device, and the identification information corresponding to a device is the identification information of the physical connectivity domain to which the device belongs;

[0007] Comparing the role type information of the first device with the role type information of the second device, and comparing the identification information corresponding to the first device with the identification information corresponding to the second device;

[0008] When it is determined that the role type information of the first device is the same as that of the second device, and the identification information corresponding to the first device is the same as that of the second device, perform a stacking operation with the second device.

[0009] Optionally, when it is determined that the role type information of the first device is different from that of the second device, and / or the identification information corresponding to the first device is different from that of the second device, do not perform a stacking operation with the second device.

[0010] In a second aspect, the present application provides a device stacking method, which is executed by a second device. The method includes:

[0011] Broadcast an address acquisition request;

[0012] Receive response information fed back by a third device according to the address acquisition request. The response information includes first address information assigned to the second device, second address information of a configuration file server, and an indication information for indicating that the second device acquires the identification information of the physical connection domain to which the second device belongs from the configuration file server;

[0013] According to the indication information, establish a communication connection with the configuration file server through the first address information and the second address information;

[0014] Send an identification information acquisition request to the configuration file server;

[0015] Receive the identification information of the physical connection domain to which the second device belongs fed back by the configuration file server;

[0016] Send a stacking request to at least one first device of the same type as the second device, so that the first device determines whether to complete a stacking operation with the second device according to the stacking request. The stacking request includes identification information and pre-acquired role type information of the second device.

[0017] Optionally, before sending a stacking request to at least one first device of the same type as the second device, the method further includes:

[0018] Send a type acquisition request to the configuration file server;

[0019] Receive a type relationship table fed back by the configuration file server;

[0020] When querying a first type corresponding to the identity information from the type relationship table according to the identity information corresponding to the second device, determine that the first type is the role type of the second device, where the identity information is pre-configured identity information of the second device.

[0021] Optionally, when the type corresponding to the identity information is not queried from the type relationship table according to the identity information corresponding to the second device, determine the pre-configured second type corresponding to the second device as the role type of the second device.

[0022] Optionally, before sending a stacking request to at least one first device of the same type as the second device, the method further includes:

[0023] Expand a private field in the packet to be forwarded, and carry identification information in the private field, so as to send the stacking request to at least one first device in the form of a packet, where the role type information of the second device is stored in the public field of the packet.

[0024] In a third aspect, an embodiment of the present application provides a device stacking apparatus, which includes:

[0025] A receiving module, configured to receive a stacking request sent by a second device, where the stacking request includes identification information and role type information corresponding to the second device, and the identification information corresponding to a device is the identification information of the physical connection domain to which the device belongs;

[0026] A processing module, configured to compare the role type information of the first device with the role type information of the second device, and compare the identification information corresponding to the first device with the identification information corresponding to the second device; when it is determined that the role type information of the first device is the same as the role type information of the second device, and the identification information corresponding to the first device is the same as the identification information corresponding to the second device, perform a stacking operation with the second device.

[0027] In a fourth aspect, an embodiment of the present application provides a device stacking apparatus, which includes:

[0028] A broadcast module, configured to broadcast an address reception request;

[0029] A receiving module, configured to receive response information fed back by a third device according to the address reception request, where the response information includes first address information assigned to the second device, second address information of a configuration file server, and an indication information for indicating that the second device receives the identification information of the physical connection domain to which the second device belongs from the configuration file server;

[0030] A communication module, configured to establish a communication connection with the configuration file server according to the indication information through the first address information and the second address information;

[0031] A sending module, configured to send an identification information acquisition request to the configuration file server;

[0032] The receiving module is further configured to receive the identification information of the physical connection domain to which the second device belongs fed back by the configuration file server;

[0033] The sending module is further configured to send a stacking request to at least one first device of the same type as the second device, so that the first device determines whether to complete the stacking operation with the second device according to the stacking request, where the stacking request includes identification information and pre-acquired role type information of the second device.

[0034] In a fifth aspect, an embodiment of the present application provides a boundary device, which includes a first device and a second device; both the first device and the second device include a processor, a communication interface, a memory, and a communication bus. Among them, the processor, the communication interface, and the memory complete mutual communication through the communication bus;

[0035] The memory is used to store a computer program;

[0036] When the processor is configured to execute the program stored in the memory, it implements the steps of the device stacking method provided in any embodiment of the first aspect; or, implements the steps of the device stacking method provided in any embodiment of the second aspect.

[0037] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by the boundary device, it implements the steps of the device stacking method provided in any embodiment of the first aspect, or implements the steps of the device stacking method provided in any embodiment of the second aspect.

[0038] The method provided in the embodiment of the present application receives a stacking request sent by a second device. The stacking request includes identification information corresponding to the second device and role type information of the second device. Among them, the identification information corresponding to a device is the identification information of the physical connection domain to which the device belongs. Compare the role type information of the first device and the role type information of the second device to determine whether they belong to the same type of device. When it is determined that they belong to the same type, it is also necessary to compare whether the first device and the second device belong to the same physical connection domain, that is, to compare whether the identification information corresponding to the first device and the identification information corresponding to the second device are the same. If they are the same, it is determined that the stacking operation with the second device can be executed. In this way, it can be identified whether a certain boundary device and the adjacent boundary device belong to the same physical connection domain. And for stacking, only devices of the same role type can perform the stacking operation. Therefore, it is also necessary to determine whether the two devices are of the same role type. Only when both conditions are met can the stacking operation be executed to achieve the expected stacking effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 It is a schematic structural diagram of two-layer interconnection of boundary devices in a multi-Fabric provided by the present application;

[0040] Figure 2 The schematic diagram of the networking structure formed after the boundary devices in multiple Fabrics provided by this application are isolated by the third-layer isolation device;

[0041] Figure 3 The schematic flow chart of a device stacking interaction method provided by an embodiment of this application;

[0042] Figure 4 The schematic flow chart of a device stacking method provided by an embodiment of this application;

[0043] Figure 5 The schematic flow chart of another device stacking method provided by an embodiment of this application;

[0044] Figure 6 The schematic diagram of the structure of a device stacking device provided by an embodiment of this application;

[0045] Figure 7 The schematic diagram of the structure of another device stacking device provided by an embodiment of this application;

[0046] Figure 8 The schematic diagram of the entity structure corresponding to a boundary device provided by an embodiment of this application. Detailed implementation manners

[0047] To make the objectives, technical solutions and advantages of the embodiments of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are some but not all of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this application without creative efforts shall fall within the protection scope of this application.

[0048] For ease of understanding of the embodiments of this application, the following will further explain with specific embodiments in conjunction with the accompanying drawings. The embodiments do not constitute a limitation to the embodiments of this application.

[0049] Regarding the technical problems mentioned in the background art, specifically refer to Figure 1 as shown in Figure 1As shown in the figure, in the networking of Fabric1 and Fabric2, the edge devices (ED) ED1 and ED2 in Fabric1 are interconnected at Layer 2 with the edge devices ED1 and ED2 in Fabric2. Assume that Fabric2 has been deployed through automated online deployment first. At this time, the ED1 and ED2 devices in Fabric1 start automated online deployment. For ED1 in Fabric1, since it is unable to identify and distinguish ED2 in Fabric1 and ED1 in Fabric2 through the Link Layer Discovery Protocol (LLDP), after ED1 is automatically deployed online, it may be automatically stacked with the ED1 device in Fabric2, and the expected networking requirement of automatic stacking of the ED1 device and ED2 in Fabric1 cannot be achieved (Stacking means connecting multiple switches supporting the stacking feature together through stacking cables and virtually forming a single switching device logically to participate in data forwarding as a whole).

[0050] Considering the above problems, although at least one additional Layer 3 device can be added between Fabric / DC devices for isolation. For details, please refer to Figure 2 as shown Figure 2 in the figure which shows adding a third-layer isolation device in two Fabrics. That is, the ED1 device and ED2 device in Fabric1, and the ED1 device and ED2 device in Fabric2 are physically connected to the third-layer switch switch respectively.

[0051] By utilizing the feature that the roles of the newly added third-layer isolation device and the edge device are inconsistent and stacking cannot be performed, the situation of incorrect stacking can be avoided. However, adding a third-layer isolation device not only increases the cost but also causes the entire network to be unable to adapt to the scenario of pure Layer 2 direct connection. As a result, the networking adaptability is restricted.

[0052] Therefore, this application provides a more optimized technical solution. For details, please refer to Figure 3 as shown Figure 3 which is a schematic diagram of the interaction process of a device stacking method provided by an embodiment of this application. In this interaction process schematic diagram, there are a first device, a second device, a third device, a configuration file server, and a repeater. In the embodiment of this application, the third device and the configuration file server are integrated in the SDN controller. Therefore Figure 3Shown is the SDN controller. In an alternative example, the third device is a Dynamic Host Configuration Protocol (DHCP) server, which is integrated into the SDN controller. Among them, the first device and the second device are adjacent border devices in a multi-Fabric / DC network. The configuration file server is a device to establish a communication connection with the second device. In an alternative example, the configuration file server can be the same device as the SDN controller, and the specific reason will be explained in detail below.

[0053] Specifically, refer to Figure 3 As shown, the interaction method process includes:

[0054] Step 1, the second device broadcasts an address acquisition request.

[0055] Specifically, the second device is a newly factory-produced or empty-configured device. After the second device is powered on and starts up, it sends a DHCP request message in broadcast form to start automatic online. Among them, the address acquisition request may carry media access control (MAC) address information corresponding to the second device.

[0056] Step 2, after the repeater receives the address acquisition request, it determines whether the sender of the address acquisition request belongs to the physical connection domain where it is located according to the MAC address information.

[0057] Specifically, after the repeater receives the DHCP request message, it extracts the MAC address information in the DHCP request message, and then determines whether the second device is in the same physical connection domain as itself according to the MAC address information.

[0058] Step 3, after the repeater determines that the sender of the address acquisition request belongs to the same physical connection domain as itself according to the MAC address information, it forwards the request to the third device after carrying its own corresponding identification information in the address acquisition request.

[0059] Specifically, after the repeater determines that the sender of the address acquisition request belongs to the same physical connection domain as itself according to the MAC address information, it adds its own corresponding identification information to the DHCP request message, and then forwards the updated DHCP message to the third device. In the embodiment of the present application, the third device is a DHCP server.

[0060] Step 4, after the DHCP server receives the updated DHCP message, it determines the address pool corresponding to the physical connection domain where the second device is located according to the identification information corresponding to the repeater.

[0061] Step 5, the DHCP server selects the first address information from the address pool as the address information corresponding to the second device.

[0062] In an optional example, the identification information of the repeater can be the IP of the repeater. Each Fabric corresponds to a repeater. Therefore, after the second device is powered on and starts up, it sends a DHCP request message to the repeater corresponding to the Fabric where it is located. Then, the repeater adds its own IP to the DHCP request message and forwards it to the DHCP server. The DHCP server can determine which border device in which Fabric sent the DHCP request based on the IP of the repeater. Then, it selects address information from the address pool corresponding to that Fabric and feeds it back to the second device through the repeater. In an optional example, the address pool is an IP address pool, and the IP address information randomly selected by the DHCP server from the IP address pool will be used as the IP address information of the second device. The above operations belong to relatively mature technologies in this field, so no more explanations will be given here.

[0063] Step 6, the DHCP server sends response information to the repeater.

[0064] The response information includes the first address information, the second address information, and an indication message. The second address information is the address information corresponding to the configuration file server to establish a communication connection with the second device. The indication message is used to indicate that the second device obtains the identification information of the physical connection domain to which the second device belongs from the configuration file server.

[0065] Specifically, the Trivial File Transfer Protocol (TFTP) server IP address information, that is, the second address information, is stored in the DHCP server. The device corresponding to the TFTP server IP address is the configuration file server. The response information sent by the DHCP server to the repeater also includes the TFTP server IP address information.

[0066] In a specific example, the configuration file server can also be the same device as the SDN controller. In the embodiments of this application, for the sake of simplicity of description, it is directly configured that the configuration file server is the SDN controller. Therefore, subsequently, when the second device establishes a communication connection with the configuration file server, it means that the second device directly establishes a communication connection with the SDN controller. Therefore, Figure 3 what is shown is the SDN controller, which actually integrates the DHCP server and the configuration file server.

[0067] The DHCP server sends the first address information, the second address information, and the indication information, etc. to the repeater in the form of a response, so that the repeater forwards the response information to the second device, completing the preparatory work for the second device to establish a stacking operation with a certain first device.

[0068] Step 7, the repeater forwards the response information to the second device.

[0069] Step 8, the second device receives the response information fed back by the third device according to the address acquisition request, and parses the response information.

[0070] After parsing, the first address information, the second address information, and the indication information in the response information are extracted.

[0071] Step 9, the second device establishes a communication connection with the configuration file server according to the indication information, through the first address information and the second address information.

[0072] In this embodiment, that is, a communication connection between the second device and the SDN controller is directly established.

[0073] Step 10, the second device sends an identification information acquisition request to the configuration file server.

[0074] Step 11, the configuration file server feeds back the identification information of the physical connection domain to which the second device belongs.

[0075] Since the second device establishes a communication connection with the second address information of the configuration file server through the first address information, the configuration file server can determine the physical connection domain where the second device is located according to the first address information, and feed back the identification information corresponding to this physical connection domain, that is, the second identification information, to the second device.

[0076] In an optional example, as introduced above, the configuration file server is the SDN controller. The SDN controller assigns an identification information to each Fabric in advance, such as Fabric ID, and the second identification information mentioned above can be FabricID.

[0077] Step 12, the second device receives the second identification information fed back by the configuration file server.

[0078] Step 13, the second device sends a stacking request to at least one first device of the same type as the second device.

[0079] Specifically, in a multi-Fabric / DC networking, there is at least one first device adjacent to the second device. For example Figure 1In the schematic diagram shown, the boundary devices adjacent to the ED1 device may include ED2 in Fabric1 and ED1 in Fabric2.

[0080] After each first device adjacent to the second device receives a stacking request, it performs the following operations. Taking any one of the first devices as an example, the description is as follows.

[0081] Step 14, the first device receives the stacking request sent by the second device.

[0082] As introduced above, the stacking request includes the identification information and role type information corresponding to the second device. The identification information corresponding to a device is the identification information of the physical connection domain to which the device belongs.

[0083] Step 15, the first device compares the role type information of the first device with the role type information of the second device, and compares the identification information corresponding to the first device with the identification information corresponding to the second device.

[0084] Step 16, when the first device determines that the role type information of the first device is the same as the role type information of the second device, and the identification information corresponding to the first device is the same as the identification information corresponding to the second device, it performs the stacking operation with the second device.

[0085] Specifically, if the role type information of the first device and the second device is the same, it means that the stacking operation can be performed. And, judging whether the identification information corresponding to the first device and the identification information corresponding to the second device are the same is to judge whether the first device and the second device belong to the same Fabric. For example Figure 1 ED1 and ED2 included in Fabric1. Only two boundary devices that belong to the same Fabric and have the same role are the devices that are expected to perform the stacking operation.

[0086] After determining that the above two conditions are met, the first device can complete the stacking operation with the first device according to the template configuration information.

[0087] Step 17, when it is determined that the role type information of the first device is different from the role type information of the second device, and / or, the identification information corresponding to the first device is different from the identification information corresponding to the second device, the stacking operation with the second device is not performed.

[0088] In an alternative embodiment, before the second device sends a stacking request to at least one first device of the same type as the second device, the method may further include:

[0089] Expand a private field in the message to be forwarded, and carry the identification information of the physical connectivity domain to which the second device belongs in the private field, so as to send the stacking request to at least one first device in the form of a message, wherein the role type information of the second device is stored in the public field of the message.

[0090] Specifically, the way for the second device to send a stacking request to at least one first device of the same type as the second device is usually implemented in the form of message forwarding. Therefore, a private field can be expanded in the message to be forwarded, and the identification information can be carried in the private field. The reason is that in the previous solutions, the identification information of the physical connectivity domain to which the second device belongs has not been transmitted. Therefore, in this application document, an additional field needs to be added to the message to store this identification information.

[0091] In an optional example, the message to be forwarded is an LLDP message. The identification information is stored in the private field of the LLDP message, and the role type information of the second device can be stored through the fields that have already existed in LLDP for storing such information.

[0092] Further optionally, before performing the configuration operation, the first device and the second device also need to obtain the configuration files corresponding to themselves respectively. Taking the second device as an example, before the second device sends a stacking request to at least one first device of the same type as the second device, it also needs to send a configuration file acquisition request to the configuration file server to obtain the configuration file corresponding to itself. In the configuration file acquisition request, the configuration file name and the role type information of the second device need to be carried. The configuration file name is carried by the third device in the feedback of the basic information of the configuration file corresponding to the second device. In an optional example, the basic information of the configuration file can be carried together when the third device sends a response message to the second device. It can also be fed back to the second device in other forms. The specific operation method is not elaborated here.

[0093] When the second device sends a configuration file acquisition request to the configuration file server, it carries the configuration file name and the role type information of the second device. Then, the configuration file server feeds back the corresponding configuration file according to the configuration file name and the role type information. Of course, the basic information of the configuration file and the role type information of the second device can also be directly carried, and there is no specific limitation.

[0094] In an optional example, each boundary device has been configured with role type information at the time of leaving the factory. Therefore, the initial role type information of the second device can be included in the configuration file request.

[0095] Of course, in an optional example, in addition to configuring the role type information at the factory, the second device can also obtain the role type information in the following manner.

[0096] Specifically, in step a, the second device sends a type acquisition request to the configuration file server.

[0097] In step b, the configuration file server feeds back the type relationship table according to the type acquisition request.

[0098] In step c, when the second device queries the first type corresponding to the identity information from the type relationship table according to the identity information corresponding to the second device, it determines the first type as the role type of the second device.

[0099] In an optional example, the identity information can be the factory serial number information corresponding to the second device. The configuration file server, which is also the SDN controller in this embodiment, can pre-enter the serial number of each device and the corresponding role type information in advance and establish a binding relationship. For example, generate a correspondence table between device serial numbers and roles, such as the type relationship table mentioned in this embodiment.

[0100] In step d, when the second device does not query the type corresponding to the identity information from the type relationship table according to the identity information corresponding to the second device, it determines the pre-configured second type corresponding to the second device as the role type of the second device.

[0101] Specifically, the second type is the initial role type mentioned above. That is to say, the priority of the role type information corresponding to the serial number in the type relationship table is higher than the priority of the role type set when the device leaves the factory. When there is a role type (the first type mentioned above) corresponding to the serial number of the device in the type relationship table, regardless of whether the initial role type of the device when it leaves the factory is the same as the role type in the type relationship table, the role type in the type relationship table will be used as the role type of the second device. Only when the role type corresponding to the second device cannot be found in the type relationship table will the initial role type of the second device when it leaves the factory be used as the role type of the second device.

[0102] The configuration file server feeds back the template configuration file corresponding to the role type information according to the role type information of the second device and the configuration file name carried in the configuration file acquisition request.

[0103] Specifically, after the configuration file server receives the role type information and the configuration file name transmitted by the second device, it obtains the configuration file with the same name according to the configuration file name, and then compares the role type information of the second device with the documents or lists in the pre-set similar mapping relationship table. The mapping relationship includes the template configuration file established with each role type information and the role type information. Furthermore, it determines the template configuration file corresponding to the second device and feeds it back to the second device.

[0104] In an optional example, the configuration file acquisition request can also belong to the same request as the identification information acquisition request mentioned above. That is, when requesting the configuration file server to obtain the identification information of the physical connection domain to which the second device belongs, the template configuration file can also be obtained at the same time. In this case, a series of operations such as sending a type acquisition request to the configuration file server to obtain the role type information of the second device need to be completed before sending the identification information acquisition request to the configuration file server. The operation of the first device receiving the template configuration file is similar to that of the second device receiving the template configuration file, so it will not be elaborated here too much.

[0105] Optionally, in addition to obtaining the template configuration file, the model information of the template configuration file can also be obtained, etc. For subsequent comparison of the above-mentioned information by the first device and the second device, the model information of the template configuration file can also be compared, and then further determine whether to perform a configuration stacking operation with the second device. In an optional example, the role types of the first device and the second device can include roles such as spine (core) and leaf (branch), etc.

[0106] The above is a relatively complete description of the embodiments in the entire application document. In the following text, the operation processes of different devices will be described from the perspective of each execution subject respectively. For details, please refer to the following.

[0107] The embodiment of the present application provides a device stacking method. For details, please refer to Figure 4 as shown Figure 4 is a schematic flow chart of a device stacking method provided by the embodiment of the present application. The method steps are executed by the first device, and the method steps include:

[0108] Step 410, receive a stacking request sent by the second device.

[0109] Among them, the stacking request includes the identification information and role type information corresponding to the second device. The identification information corresponding to a device is the identification information of the physical connection domain to which the device belongs;

[0110] Step 420: Compare the role type information of the first device with that of the second device, and compare the identification information corresponding to the first device with that corresponding to the second device.

[0111] Step 430: When it is determined that the role type information of the first device is the same as that of the second device, and the identification information corresponding to the first device is the same as that corresponding to the second device, perform a stacking operation with the second device.

[0112] Optionally, when it is determined that the role type information of the first device is different from that of the second device, and / or the identification information corresponding to the first device is different from that corresponding to the second device, do not perform a stacking operation with the second device.

[0113] The specific implementation processes of the above steps have been explained in detail above, so they will not be elaborated here.

[0114] The device stacking method provided by the embodiments of this application receives a stacking request sent by a second device. The stacking request includes the identification information corresponding to the second device and the role type information of the second device. Among them, the identification information corresponding to a device is the identification information of the physical connection domain to which the device belongs. Compare the role type information of the first device with that of the second device to determine whether they belong to the same type of device. When it is determined that they belong to the same type, it is also necessary to compare whether the first device and the second device belong to the same physical connection domain, that is, to compare whether the identification information corresponding to the first device is the same as that corresponding to the second device. If they are the same, it is determined that a stacking operation with the second device can be performed. In this way, it can be identified whether a certain border device and the adjacent border device belong to the same physical connection domain. And for stacking, only devices of the same role type can perform the stacking operation, so it is also necessary to determine whether the two devices are of the same role type. Only when both conditions are met can the stacking operation be performed to achieve the expected stacking effect.

[0115] The embodiments of this application provide a device stacking method. Specifically, see Figure 5 as shown in Figure 5 which is a schematic flowchart of a device stacking method provided by the embodiments of this application. The method steps are executed by the second device, and the method steps include:

[0116] Step 510: Broadcast an address acquisition request.

[0117] Specifically, the second device sends out an address acquisition request in a broadcast form.

[0118] In an optional example, the address acquisition request is a DHCP request. After receiving the address acquisition request, a repeater belonging to the same physical connection domain as the second device adds its own identification information, such as IP information, to the address request and then forwards it to the DHCP server, so that the DHCP server can feedback the first address information, the second address information of the configuration file server, and the indication information to the second device. The specific implementation process is also transmitted through the repeater for transfer. Among them, the first address information is the address information assigned by the DHCP server to the second device. For details, please refer to the above introduction and will not be elaborated here.

[0119] Step 520, receive the response information fed back by the third device according to the address acquisition request.

[0120] Specifically, receive the response information fed back by the third device in the form of a DHCP message. Among them, the response information includes the first address information assigned to the second device, the second address information of the configuration file server, and the indication information, and the indication information is used to indicate that the second device obtains the identification information of the physical connection domain to which the second device belongs from the configuration file server.

[0121] Step 530, establish a communication connection with the configuration file server according to the indication information, the first address information, and the second address information.

[0122] Step 540, send an identification information acquisition request to the configuration file server.

[0123] Step 550, receive the identification information of the physical connection domain to which the second device belongs fed back by the configuration file server according to the identification information acquisition request.

[0124] Step 560, send a stacking request to at least one first device of the same type as the second device.

[0125] So that the first device can determine whether to complete the stacking operation with the second device according to the stacking request. Among them, the stacking request includes the identification information and the pre-acquired role type information of the second device.

[0126] Optionally, before sending a stacking request to at least one first device of the same type as the second device, the method further includes:

[0127] Send a type acquisition request to the configuration file server;

[0128] Receive the type relationship table fed back by the configuration file server;

[0129] When querying the first type corresponding to the identity information from the type relationship table according to the identity information corresponding to the second device, determine that the first type is the role type of the second device, where the identity information is the pre-configured identity information of the second device.

[0130] Optionally, when the type corresponding to the identity information is not queried from the type relationship table according to the identity information corresponding to the second device, determine that the pre-configured second type corresponding to the second device is the role type of the second device.

[0131] Optionally, before sending a stacking request to at least one first device of the same type as the second device, the method further includes:

[0132] Expand a private field in the packet to be forwarded, and carry identification information in the private field, so as to send the stacking request to at least one first device in the form of a packet, where the role type information of the second device is stored in the public field of the packet.

[0133] The specific implementation processes of the above steps have been explained in detail above, so they will not be elaborated here.

[0134] The device stacking method provided by the embodiments of the present application includes: broadcasting an address acquisition request, and receiving response information fed back by a third device according to the address acquisition request. The response information includes first address information assigned to the second device, second address information of a configuration file server, and an indication information. The indication information is used to instruct the second device to obtain the identification information of the physical connection domain to which the second device belongs from the configuration file server. Sending an identification information acquisition request to the configuration file server, and after receiving the identification information fed back by the configuration file server according to the identification information acquisition request, sending a stacking request to at least one first device of the same type as the second device, so that each first device determines whether to complete the stacking operation with the second device according to the stacking request. The role type information of the second device and the identification information of the physical connection domain to which the second device belongs are carried in the stacking request. In this way, the first device can identify whether a certain boundary device and the adjacent boundary device belong to the same physical connection domain. And for stacking, only devices of the same role type can perform the stacking operation. Therefore, it is also necessary to determine whether the two devices are of the same role type. Only when both conditions are met can the stacking operation be performed to achieve the expected stacking effect.

[0135] Figure 6 The figure is a schematic structural diagram of a device stacking device provided by an embodiment of the present application. The device includes: a receiving module 601 and a processing module 602;

[0136] The receiving module 601 is configured to receive a stacking request sent by a second device. The stacking request includes identification information and role type information corresponding to the second device. The identification information corresponding to a device is the identification information of the physical connection domain to which the device belongs;

[0137] A processing module 602 is configured to compare the role type information of the first device with the role type information of the second device, and compare the identification information corresponding to the first device with the identification information corresponding to the second device; when it is determined that the role type information of the first device is the same as the role type information of the second device, and the identification information corresponding to the first device is the same as the identification information corresponding to the second device, perform a stacking operation with the second device.

[0138] Optionally, the processing module 602 is further configured to, when it is determined that the role type information of the first device is different from the role type information of the second device, and / or the identification information corresponding to the first device is different from the identification information corresponding to the second device, not perform a stacking operation with the second device.

[0139] The functions performed by the components in the device stacking apparatus provided in the embodiments of the present application have been described in detail in the foregoing embodiments, and thus will not be elaborated herein.

[0140] A device stacking apparatus provided in an embodiment of the present application receives a stacking request sent by a second device. The stacking request includes the identification information corresponding to the second device and the role type information of the second device. Among them, the identification information corresponding to a device is the identification information of the physical connection domain to which the device belongs. Compare the role type information of the first device with the role type information of the second device to determine whether the two belong to the same type of device. When it is determined that they belong to the same type, it is also necessary to compare whether the first device and the second device belong to the same physical connection domain, that is, to compare whether the identification information corresponding to the first device is the same as the identification information corresponding to the second device. If they are the same, it is determined that a stacking operation with the second device can be performed. In this way, it can be identified whether a certain boundary device and the adjacent boundary device belong to the same physical connection domain. And stacking can only be performed by devices of the same role type, so it is also necessary to determine whether the two devices are of the same role type. Only when both conditions are met can the stacking operation be performed to achieve the expected stacking effect.

[0141] Figure 7 FIG. 13 is a schematic structural diagram of a device stacking apparatus provided in an embodiment of the present application. The apparatus includes: a broadcast module 701, a receiving module 702, a communication module 703, and a sending module 704;

[0142] The broadcast module 701 is configured to broadcast an address acquisition request;

[0143] A receiving module 702, configured to receive response information fed back by a third device according to an address acquisition request, where the response information includes first address information allocated to a second device, second address information of a configuration file server, and an indication information for indicating that the second device acquires identification information of a physical connection domain to which the second device belongs from the configuration file server;

[0144] A communication module 703, configured to establish a communication connection with the configuration file server according to the indication information, via the first address information and the second address information;

[0145] A sending module 704, configured to send an identification information acquisition request to the configuration file server;

[0146] The receiving module 702 is further configured to receive the identification information of the physical connection domain to which the second device belongs, fed back by the configuration file server according to the identification information acquisition request;

[0147] The sending module 704 is further configured to send a stacking request to at least one first device of the same type as the second device, so that the first device determines whether to complete a stacking operation with the second device according to the stacking request, where the stacking request includes the identification information and pre-acquired role type information of the second device.

[0148] Optionally, the apparatus further includes: a processing module 705;

[0149] The sending module 704 is further configured to send a type acquisition request to the configuration file server;

[0150] The receiving module 702 is further configured to receive a type relationship table fed back by the configuration file server;

[0151] The processing module 705 is further configured to, when querying a first type corresponding to the identity information from the type relationship table according to the identity information corresponding to the second device, determine that the first type is the role type of the second device, where the identity information is pre-configured identity information of the second device.

[0152] Optionally, the processing module 705 is further configured to, when not querying a type corresponding to the identity information from the type relationship table according to the identity information corresponding to the second device, determine that a pre-configured second type corresponding to the second device is the role type of the second device.

[0153] Optionally, the processing module 705 is further configured to expand a private field in a packet to be forwarded, and carry the identification information in the private field, so as to send the stacking request to at least one first device in the form of a packet, where the role type information of the second device is stored in a public field of the packet.

[0154] The functions performed by each component in the device stacking apparatus provided in the embodiments of the present application have been described in detail in the foregoing embodiments, and thus will not be elaborated herein.

[0155] A device stacking apparatus provided in an embodiment of the present application, a device stacking method provided in an embodiment of the present application, a broadcast address acquisition request, and response information fed back by a third device according to the address acquisition request are received. The response information includes first address information assigned to a second device, second address information of a configuration file server, and an indication information. The indication information is used to instruct the second device to obtain the identification information of the physical connection domain to which the second device belongs from the configuration file server. An identification information acquisition request is sent to the configuration file server, and after receiving the identification information fed back by the configuration file server according to the identification information acquisition request, a stacking request is sent to at least one first device of the same type as the second device, so that each first device determines whether to complete the stacking operation with the second device according to the stacking request. The role type information of the second device and the identification information of the physical connection domain to which the second device belongs are carried in the stacking request. In this way, the first device can identify whether a certain border device and the border device adjacent thereto belong to the same physical connection domain. And for stacking, only devices of the same role type can perform the stacking operation. Therefore, it is also necessary to determine whether two devices are of the same role type. Only when both conditions are met can the stacking operation be performed to achieve the expected stacking effect.

[0156] As Figure 8 shown, an embodiment of the present application provides a schematic diagram of a border entity structure, including a processor 111, a communication interface 112, a memory 113, and a communication bus 114. Among them, the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0157] The memory 113 is used to store a computer program;

[0158] In an embodiment of the present application, when the processor 111 is used to execute the program stored on the memory 113, the device stacking method provided in the foregoing method embodiment is implemented. The method includes:

[0159] Receiving a stacking request sent by a second device. The stacking request includes identification information and role type information corresponding to the second device. The identification information corresponding to a device is the identification information of the physical connection domain to which the device belongs;

[0160] Comparing the role type information of the first device with the role type information of the second device, and comparing the identification information corresponding to the first device with the identification information corresponding to the second device;

[0161] When it is determined that the role type information of the first device is the same as that of the second device, and the identification information corresponding to the first device is the same as that corresponding to the second device, perform a stacking operation with the second device.

[0162] Optionally, when it is determined that the role type information of the first device is different from that of the second device, and / or the identification information corresponding to the first device is different from that corresponding to the second device, then do not perform a stacking operation with the second device.

[0163] Or,

[0164] In another embodiment of the present application, when the processor 111 executes the program stored on the memory 113, it implements the device stacking method provided by the foregoing method embodiment. The method includes:

[0165] Broadcast an address acquisition request;

[0166] Receive response information fed back by a third device according to the address acquisition request. The response information includes first address information assigned to the second device, second address information of the configuration file server, and an indication information for indicating that the second device acquires the identification information of the physical connection domain to which the second device belongs from the configuration file server;

[0167] According to the indication information, establish a communication connection with the configuration file server through the first address information and the second address information;

[0168] Send an identification information acquisition request to the configuration file server;

[0169] Receive the identification information of the physical connection domain to which the second device belongs fed back by the configuration file server according to the identification information acquisition request;

[0170] Send a stacking request to at least one first device of the same type as the second device, so that the first device determines whether to complete a stacking operation with the second device according to the stacking request. The stacking request includes identification information and pre-acquired role type information of the second device.

[0171] Optionally, before sending a stacking request to at least one first device of the same type as the second device, the method further includes:

[0172] Send a type reception request to the configuration file server;

[0173] Receive a type relationship table fed back by the configuration file server;

[0174] When, according to the identity information corresponding to the second device, the first type corresponding to the identity information is queried from the type relationship table, it is determined that the first type is the role type of the second device, where the identity information is the identity information pre-configured for the second device.

[0175] Optionally, when, according to the identity information corresponding to the second device, no type corresponding to the identity information is queried from the type relationship table, it is determined that the pre-configured second type corresponding to the second device is the role type of the second device.

[0176] Optionally, before sending a stacking request to at least one first device of the same type as the second device, the method further includes:

[0177] Expanding a private field in the packet to be forwarded and carrying identification information in the private field, so as to send the stacking request to at least one first device in the form of a packet, where the role type information of the second device is stored in the public field of the packet.

[0178] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a boundary device, the steps of the device stacking method provided in the foregoing method embodiment are implemented.

[0179] It should be noted that in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the element.

[0180] The above are only specific embodiments of the present application, enabling those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A device stacking method, characterized in that, The method is executed by a second device, and the method includes: Broadcasting an address acquisition request, which is forwarded to a third device by a repeater that belongs to the same physical connection domain as the second device after adding the identification information corresponding to the repeater; Receiving the response information forwarded by the repeater from the third device according to the address acquisition request, where the response information includes first address information assigned to the second device, second address information of a configuration file server, and an indication information for indicating that the second device acquires the identification information of the physical connection domain to which the second device belongs from the configuration file server; Establishing a communication connection with the configuration file server according to the indication information, through the first address information and the second address information; Sending an identification information acquisition request to the configuration file server; Receiving the identification information of the physical connection domain to which the second device belongs, which is forwarded by the configuration file server according to the identification information acquisition request; Sending a stacking request to at least one first device of the same type as the second device, so that the first device determines whether to complete the stacking operation with the second device according to the stacking request, where the stacking request includes the identification information and the pre-acquired role type information of the second device; 2. The method according to claim 1, wherein Before sending the stacking request to at least one first device of the same type as the second device, the method further includes: Sending a type acquisition request to the configuration file server; Receiving the type relationship table fed back by the configuration file server; When querying the first type corresponding to the identity information from the type relationship table according to the identity information corresponding to the second device, determining that the first type is the role type of the second device, where the identity information is the pre-configured identity information of the second device; 3. The method according to claim 2, wherein When not querying the type corresponding to the identity information from the type relationship table according to the identity information corresponding to the second device, determining that the pre-configured second type corresponding to the second device is the role type of the second device; 4. The method according to any one of claims 1 to 3, characterized in that, Before sending the stacking request to at least one first device of the same type as the second device, the method further includes: Expanding a private field in the packet to be forwarded, and carrying the identification information in the private field, so as to send the stacking request to at least one of the first devices in the form of the packet, where the role type information of the second device is stored in the public field of the packet; 5. A device stacking device, characterized in that, The apparatus includes: A broadcasting module, configured to broadcast an address acquisition request, which is forwarded to a third device by a repeater that belongs to the same physical connection domain as the second device after adding the identification information corresponding to the repeater; A receiving module, configured to receive the response information fed back by the third device according to the address acquisition request and forwarded by the repeater, where the response information includes first address information assigned to a second device, second address information of a configuration file server, and an indication information for indicating that the second device receives identification information of a physical connection domain to which the second device belongs from the configuration file server; A communication module, configured to establish a communication connection with the configuration file server according to the indication information, through the first address information and the second address information; A sending module, configured to send an identification information acquisition request to the configuration file server; The receiving module is further configured to receive the identification information of the physical connection domain to which the second device belongs, fed back by the configuration file server; The sending module is further configured to send a stacking request to at least one first device of the same type as the second device, so that the first device determines whether to complete a stacking operation with the second device according to the stacking request, where the stacking request includes the identification information and pre-acquired role type information of the second device.

6. A boundary device, characterized in that, The boundary device includes a first device and a second device; both the first device and the second device include a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the communication bus; A memory, configured to store a computer program; A processor, configured to implement the steps of the device stacking method according to any one of claims 1-4 when executing the program stored on the memory.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, The computer program, when executed by the boundary device, implements the steps of the device stacking method according to any one of claims 1-4.

Images