CN111245974A

CN111245974A - Address allocation method, device, equipment and storage medium

Info

Publication number: CN111245974A
Application number: CN202010084106.XA
Authority: CN
Inventors: 付翔
Original assignee: Sangfor Technologies Co Ltd
Current assignee: Sangfor Technologies Co Ltd
Priority date: 2020-02-10
Filing date: 2020-02-10
Publication date: 2020-06-05
Anticipated expiration: 2040-02-10
Also published as: CN111245974B

Abstract

The embodiment of the application discloses an address allocation method, an address allocation device, address allocation equipment and a storage medium, wherein the method comprises the following steps: when an address allocation request sent by a terminal is received, determining an available address in an address pool as an address to be allocated; wherein an address in the address pool is attributed to a stack member; determining a target stacking member to which the address to be distributed belongs; determining the activity state of the target stack member in a stack group connected with the terminal; and when the active state is the online state, allocating the address to be allocated to the terminal.

Description

Address allocation method, device, equipment and storage medium

Technical Field

Embodiments of the present disclosure relate to, but not limited to, network technologies, and in particular, to an address allocation method, apparatus, device, and storage medium.

Background

In modern networks, requirements on performance and stability of the switch are greatly improved, and a common box-type switch cannot meet networking requirements of key network positions, so that stacking technology comes up at the end. The stacking technology virtualizes a plurality of switches into one switch, which is embodied by one virtual device in the network, and a user can make configuration effective in all stack member switches by only one operation. Since multiple devices can form a stack, the stack may also be split into multiple groups of stacks, and stack split detection is usually configured to avoid the network impact of stack splitting.

If the stack is split and the stack split detection of the Configuration fails, two sets of stacks with the same Configuration appear in the network, and since the position of the stacks in the network is generally in the core layer, users often configure a Dynamic Host Configuration Protocol (DHCP) server for the stacks. Thus, after the stack is split, when two users request addresses from the DHCP server at the same time, the two users may have the same Internet Protocol (IP) address. After the stack splitting is solved, two terminals with the same IP address appear in the same local area network, which will generate IP address conflict, because the DHCP protocol does not support the DHCP server to actively recover the IP address, the network administrator can only manually release the IP address on the terminal equipment and reacquire the IP address, and if no intervention is carried out, the two terminals will always have network problems such as packet loss and the like within the lease validity period. If the network administrator does not solve the problem of stack splitting in time, a large number of terminals acquire the same IP addresses, and a catastrophic problem is generated after stacking and merging, and a large amount of manpower is consumed if the problem needs to be solved.

In view of the above problems in the related art, no solution has been proposed at present.

Disclosure of Invention

In view of this, embodiments of the present application provide an address allocation method, apparatus, device, and storage medium.

The technical scheme of the embodiment of the application is realized as follows:

in one aspect, an embodiment of the present application provides an address allocation method, where the method includes:

when an address allocation request sent by a terminal is received, determining an available address in an address pool as an address to be allocated; wherein an address in the address pool is attributed to a stack member;

determining a target stacking member to which the address to be distributed belongs;

determining the activity state of the target stack member in a stack group connected with the terminal;

and when the active state is the online state, allocating the address to be allocated to the terminal.

In another aspect, an embodiment of the present application provides an address allocation apparatus, where the apparatus includes:

the first determining module is used for determining one available address in the address pool as an address to be allocated when receiving an address allocation request sent by a terminal; wherein an address in the address pool is attributed to a stack member;

the second determining module is used for determining a target stacking member to which the address to be allocated belongs;

a third determining module, configured to determine an active state of the target stack member in a stack group to which the terminal is connected;

and the first sending module is used for distributing the address to be distributed to the terminal when the active state is an online state.

In another aspect, an embodiment of the present application provides an address allocation apparatus, which includes a memory and a processor, where the memory stores a computer program that is executable on the processor, and the processor implements the steps in the method when executing the program.

In yet another aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps in the method.

In the embodiment of the application, the IP addresses in the address pool are virtualized into a plurality of parts, so that each independent IP address only belongs to one stacking member, and the DHCP server can only allocate the addresses of the stacking members belonging to the online state when allocating the addresses. Because the online members of any one group of stacked after the stack splitting are not the online members in other stacked groups after the stack splitting, the addresses belonging to the online members are not allowed to be allocated in other stacked groups after the stack splitting, and thus, after the stack splitting, different users do not allocate the same IP address when requesting the address from the DHCP server, thereby avoiding the generation of IP collision after the stack splitting is combined again.

Drawings

Fig. 1 is a schematic flowchart illustrating an implementation process of an address allocation method according to an embodiment of the present application;

fig. 2 is a schematic flowchart illustrating an implementation process of an address allocation method according to an embodiment of the present application;

fig. 3A is a schematic flowchart illustrating an implementation process of an address allocation method according to an embodiment of the present application;

fig. 3B is a schematic flow chart illustrating an implementation of determining an identifier of a target stack member to which the address to be allocated belongs according to the embodiment of the present application;

fig. 4 is a schematic flowchart illustrating an implementation process of an address allocation method according to an embodiment of the present application;

fig. 5 is a schematic flowchart illustrating an implementation process of an address allocation method according to an embodiment of the present application;

fig. 6 is a schematic flowchart illustrating an implementation process of an address allocation method according to an embodiment of the present application;

fig. 7A is a schematic flowchart illustrating an implementation process of an address allocation method according to an embodiment of the present application;

fig. 7B is a schematic diagram of address allocation before and after stack splitting according to the address allocation method provided in the embodiment of the present application;

fig. 8 is a schematic structural diagram of an address allocation apparatus according to an embodiment of the present disclosure;

fig. 9 is a schematic hardware entity diagram of an address assignment device in an embodiment of the present application.

Detailed Description

In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application are further described in detail with reference to the drawings and the embodiments, the described embodiments should not be considered as limiting the present application, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts belong to the protection scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.

Where similar language of "first/second" appears in the specification, the following description is added, and where reference is made to the term "first \ second \ third" merely to distinguish between similar items and not to imply a particular ordering with respect to the items, it is to be understood that "first \ second \ third" may be interchanged with a particular sequence or order as permitted, to enable the embodiments of the application described herein to be performed in an order other than that illustrated or described herein.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the application.

In order to better understand an address allocation method provided by the embodiment of the present application, a brief description is first made on a related technology related to the present application.

The stacking technology is a technology for improving the bandwidth of a back plate available to a port, expanding ports of switches, improving the reliability of a network and managing a plurality of switches in a centralized manner.

The stack splitting refers to that a part of member switches are moved out in a live mode in a stack system in a steady-state operation, or a multi-point fault of a stack cable causes one stack system to become a plurality of stack systems. After the stack system is split, a plurality of stack systems with the same configuration may be generated, resulting in a conflict between an IP address and a Media Access Control (MAC) address in a network, and causing a network failure.

The DHCP is a dynamic host configuration protocol, and the device in the lan can automatically obtain an IP address from a DHCP server after opening the protocol. The DHCP is a protocol widely used in the local area network, and after setting the DHCP server, the terminal user does not need to know how to fill in the gateway and Domain Name Service (DNS) addresses, and the administrator does not need to allocate a specific IP address to each person, and the terminal can conveniently access the network only by starting the DHCP client service. Similarly, for a large network, it is time-consuming and labor-consuming to configure an IP address for each device one by one, and human operations may also introduce errors, and after starting the DHCP client service, the IP address allocation of the device may be completed quickly.

An embodiment of the present application provides an address allocation method, and fig. 1 is a schematic flowchart illustrating an implementation process of the address allocation method provided in the embodiment of the present application, where the method may be executed by a DHCP server, and as shown in fig. 1, the method includes:

step S101, when an address allocation request sent by a terminal is received, determining an available address in an address pool as an address to be allocated; wherein an address in the address pool is attributed to a stack member;

here, the address pool is a resource pool of addresses that can be allocated by the current stacking system, and when performing address allocation for a terminal connected in the current stacking system, the DHCP server searches for an available address from the corresponding address pool to perform the allocation. In implementation, when configuring a DHCP service for the stack system, a user may configure a corresponding address pool, and the DHCP server may determine an address in the address pool by reading a configuration file of the stack system.

The addresses in the address pool may be IP addresses and the available addresses may be unassigned IP addresses in the address pool. The DHCP server may find an available address in the address pool as an address to be allocated according to a certain traversal order. In implementation, a person skilled in the art may select a suitable traversal order according to actual situations, which is not limited in the embodiment of the present application.

Each address in the address pool has and is attributed to only one stack member, such that the addresses attributed to any two stack members do not overlap. In implementation, the addresses in the address pool may be virtually divided into the same number of shares as the total number according to the attribution correspondence relationship between the specific addresses and the stack members, and each address is attributed to one stack member. In some embodiments, an equal number of addresses may be divided for each stack member. In some embodiments, the number of addresses attributed to each stack member may also be determined according to the number of ports provided by different stack members, the number of terminals connected, and the like.

Step S102, determining the target stacking member to which the address to be distributed belongs;

here, the target stack member to which the address to be allocated belongs may be determined according to the attribution correspondence relationship between the address and the stack member in the above step S101. In some embodiments, the attribution correspondence may be a mapping relationship table that is stored locally after being preset, and in implementation, the mapping relationship table may be queried according to the address to be allocated to obtain the target stack member. In some embodiments, the attribution correspondence may also be determined by a specific mapping algorithm, and in implementation, the target stack member may be obtained by using the address to be allocated through the specific mapping algorithm.

Step S103, determining the activity state of the target stack member in the stack group connected with the terminal;

here, after the stack is split, the stack group connected to the terminal may change with the split, and each stack member may have an active status in a different stack group after the split, where the active status is used to identify whether the stack member is online in the stack group. In practice, the active state may include an online state and an offline state. After the stack is split, each stack member is online only in one stack group and offline in the other stack groups, that is, no online member of any stack group after the stack is split is an online member in the other split stack groups.

In implementation, the active state of the target stack member in the stack group connected to the terminal may be acquired by reading local configuration information.

And step S104, when the activity state is an online state, allocating the address to be allocated to the terminal.

Here, the DHCP server can only assign addresses attributed to stack members that are online. Therefore, when the active state of the target stack member in the stack group connected with the terminal is determined to be the online state, the address to be allocated is allocated to the terminal. In implementation, the DHCP server may send a response carrying the address to be allocated to the terminal. In some embodiments, the DHCP server may further determine a lease validity period for the address to be allocated, and add the lease validity period to a response carrying the address to be allocated and sent to the terminal.

In the address allocation method provided in the embodiment of the present application, each independent IP address is attributed to only one stack member by virtualizing the IP address in the address pool into a plurality of parts, and the DHCP server can only allocate addresses of stack members that belong to an online state when allocating addresses. Because the online members of any one group of stacked after the stack splitting are not the online members in other stacked groups after the stack splitting, the addresses belonging to the online members are not allowed to be allocated in other stacked groups after the stack splitting, and thus, after the stack splitting, different users do not allocate the same IP address when requesting the address from the DHCP server, thereby avoiding the generation of IP collision after the stack splitting is combined again.

An embodiment of the present application provides an address allocation method, and fig. 2 is a schematic diagram illustrating an implementation flow of the address allocation method provided in the embodiment of the present application, where the method may be executed by a DHCP server, and as shown in fig. 2, the method includes:

step S201, when receiving an address allocation request sent by a terminal, determining an available address in an address pool as an address to be allocated; wherein an address in the address pool is attributed to a stack member;

step S202, determining the target stacking member to which the address to be distributed belongs;

step S203, determining the activity state of the target stack member in the stack group connected with the terminal;

step S204, when the activity state is an online state, the address to be allocated is allocated to the terminal;

here, the steps S201 to S204 correspond to the steps S101 to S104, respectively, so those skilled in the art can refer to the steps S101 to S104 to understand the steps S201 to S204, and for saving brevity, the description is omitted here.

Step S205, when the active state is an offline state, determining that the next available address in the address pool is a new address to be allocated; return to step S202.

Here, when the DHCP server determines that the active state of the target stack member in the stack group to which the terminal is connected is an offline state, the address to be allocated is not allowed to be allocated, a next available address needs to be searched in the address pool as a new address to be allocated, and it is determined whether the new address to be allocated is allowed to be allocated through the above steps S202 to S203, and so on, until the new address to be allocated searched in the address pool is allowed to be allocated, the new address to be allocated is allocated to the terminal. In some embodiments, when all available addresses in the address pool have been traversed and no address to be allocated is found that allows allocation, the DHCP server may send a response to the terminal that the address allocation failed.

An embodiment of the present application provides an address allocation method, and fig. 3A is a schematic flowchart illustrating an implementation flow of the address allocation method provided in the embodiment of the present application, where the method may be executed by a DHCP server, and as shown in fig. 3A, the method includes:

step S301, when an address allocation request sent by a terminal is received, determining an available address in an address pool as an address to be allocated; wherein an address in the address pool is attributed to a stack member;

step S302, determining the identifier of the target stacking member to which the address to be distributed belongs through a mapping algorithm between a specific address and the identifier of the stacking member to which the address belongs;

here, the addresses in the address pool may be virtually divided into the same number of shares as the total number according to a specific mapping algorithm, in accordance with the total number of stack members referencing the address pool, and each share of addresses may be attributed to one stack member. Through the mapping algorithm, each address in the address pool can be mapped to the identification of a unique stacking member, so that the stacking member to which each address in the address pool belongs can be determined, and the addresses belonging to any two stacking members are not overlapped. In implementation, a person skilled in the art may select a suitable mapping algorithm according to actual situations, which is not limited in the embodiment of the present application.

In some embodiments, the mapping algorithm may be any suitable hashing algorithm, including, but not limited to, any one or more of remainder methods, folding methods, random number methods, and the like. For example, when the remainder method is adopted, the remainder value of the IP address to be allocated may be used to perform a remainder operation on the total number of the stacking members, and the obtained remainder is used as the identifier of the target stacking member; when a folding method is adopted, adding numerical values corresponding to each bit in the point-cellular IP addresses to be distributed, judging whether the obtained result is smaller than the total number of the stacking members or not, taking the current result as the identification of the target stacking member when the result is smaller than the total number of the stacking members, and continuing to add the numerical values corresponding to each bit of the obtained result until the identification of the target stacking member is obtained; when the random number method is adopted, assuming that the total number of the stacking members is N, a random function with a value range of [0, N) can be selected, an integer value of an IP address to be allocated is taken as a seed of the random function, and a generated random value is taken as an identifier of a target stacking member.

In some embodiments, the identification of the target stack member to which the address to be assigned belongs may be determined by a method, as shown in fig. 3B, comprising:

step S311, determining the total number of stack members referencing the address pool;

here, addresses in the address pool can only be attributed to stack members that reference the address pool. The total number of stack members referencing the address pool may be determined by detecting whether each stack member references the address pool, or may be determined by storing, in advance, a reference relationship between each address pool and a stack member locally as configuration information and by querying the configuration information, the total number of stack members referencing the address pool.

Step S312, converting the address to be allocated into a host byte order format to obtain an integer value of the address to be allocated;

here, the host endian may be big-end endian or small-end endian according to the difference between the operating system and the CPU, and an integer value corresponding to the dot-grid IP address can be obtained by converting the IP address into the host endian.

Step 313, performing remainder operation on the total number by using the integer value of the address to be allocated to obtain a remainder;

step S314, determining the identifier of the stack member with the sequence number being the remainder as the identifier of the target stack member according to the list of identifiers of the stack members referencing the address pool.

Here, the list of the identifications of the stack members referring to the address pool may be stored in a local storage or a database after being configured in advance, and the DHCP server may read from the local storage or query from the database when necessary.

Because the IP addresses in the same address pool are usually continuous, the integer values converted into the host byte order format can also have the same continuity, the total number is subjected to remainder operation by utilizing the integer values corresponding to the IP addresses converted into the host byte order format, and the identifications of the stacking members are determined by taking the remainders as serial numbers, so that the IP addresses in the address pool can be more uniformly mapped to the stacking members.

Step S303, determining the target stacking member according to the identification of the target stacking member;

here, each stack member has a specific identifier from which a unique stack member can be determined.

Step S304, determining the active state of the target stack member in the stack group connected with the terminal;

step S305, when the active state is an online state, allocating the address to be allocated to the terminal.

Here, the steps S301, S304, and S305 correspond to the steps S101, S103, and S104, respectively, so those skilled in the art can refer to the steps S101, S103, and S104 to understand the steps S301, S304, and S305, and therefore, for brevity, description is omitted here.

In some embodiments, prior to said determining the total number of stack members referencing the address pool, the method further comprises: for each of the stack members in a current stack system, determining whether the address pool is referenced by the stack member.

Since an address pool may be configured on a physical port, a Virtual Local Area Network (VLAN) port, or an aggregation port in a stackable switch, in some embodiments, the manner of determining whether the address pool is referenced by the stack member may include: when the address pool is configured on a physical port and the physical port belongs to the stack member, determining that the address pool is referenced by the stack member; or when the address pool is configured on a VLAN interface and any port of the stack member refers to the VLAN interface, determining that the address pool is referred by the stack member; or, when the address pool is configured on an aggregation port and any one member port of the aggregation port belongs to the stack member, determining that the address pool is referred to by the stack member.

In some embodiments, after determining whether the address pool is referenced by the stack member, for each stack member in the current stack system, the reference relationship between the address pool and each stack member may be stored locally as configuration information. In some embodiments, the identifiers of the stack members referencing the address pool may be further grouped into a sequence string, an array, or a list according to a specific order, and stored locally, where in implementation, the specific order may be from large to small, or from small to large.

An embodiment of the present application provides an address allocation method, which may be executed by a DHCP server, and as shown in fig. 4, the method includes:

step S401, when an address allocation request sent by a terminal is received, determining an available address in an address pool as an address to be allocated; wherein an address in the address pool is attributed to a stack member;

step S402, inquiring a specific first mapping relation table according to the address to be distributed to obtain the identification of the target stack member; the mapping relation table is used for representing the corresponding relation between an address and the identifier of the stack member to which the address belongs;

here, the first mapping relation table may be stored in a local storage or a database after being predetermined, and the DHCP server may read from the local storage or query from the database when necessary.

Step S403, determining the target stacking member according to the identification of the target stacking member;

step S404, determining the active state of the target stack member in the stack group connected with the terminal;

step S405, when the activity state is the online state, the address to be allocated is allocated to the terminal.

Here, the steps S401, S403 to S405 correspond to the steps S301, S303 to S305, respectively, so that those skilled in the art can understand the steps S401, S403 to S405 by referring to the steps S301, S303 to S305, which is not described herein again.

In some embodiments, prior to the determining a target stack member to which the address to be assigned belongs, the method further comprises: for each address in the address pool, determining an identification of a stack member to which each address belongs; establishing a mapping relation between each address and the identifier of the stacking member to which the address belongs; adding each mapping relation to the first mapping relation table.

Here, the stack members to which all addresses in the address pool respectively belong may be determined according to a specific attribution correspondence. In implementation, the identifier of the stack member to which each address belongs may be configured by a user, or the method for determining the identifier of the target stack member to which the address to be allocated belongs in step S302 may be referred to, which is not described herein again.

An embodiment of the present application provides an address allocation method, which may be executed by a DHCP server, and as shown in fig. 5, the method includes:

step S501, when an address allocation request sent by a terminal is received, determining an available address in an address pool as an address to be allocated; wherein an address in the address pool is attributed to a stack member;

step S502, determining a target stacking member to which the address to be distributed belongs;

step S503, determining the identification of the target stacking member;

step S504, determining the identifier of the stack group connected with the terminal;

step S505, according to the identification of the target stack member and the identification of the stack group, querying a specific second mapping relation table to obtain the activity state of the target stack member in the stack group connected with the terminal; the second mapping relation table is used for representing the corresponding relation among the identification of the stacking member, the identification of the stacking group and the activity state of the stacking member;

here, the second mapping relation table is used for recording the basic information of the stack members, including the basic information of all members of the current stack system, including but not limited to the identification of the stack, the identification of the stack group and the activity state of the stack group. Each stack member is active online only in the stack group to which it belongs, and is active offline in the other stack groups.

In some embodiments, each stack member has a corresponding piece of basic information for each stack group after the stack splitting, and only one piece of basic information among all pieces of basic information of each stack member has an active state being an online state, and the others being offline states.

In implementation, the stacking system may have a common management and control module, configured to record basic information of all stacking members in the current stacking system, and store the recorded basic information in the second mapping relationship table. After the stack is split, because the stack group to which the stack member belongs may change, the management and control module further needs to determine new basic information of each stack member according to the stack group of each split stack member, and update the basic information to the second mapping relationship table. After the stack splitting and merging, all stack members in the current stack system are merged into the same stack group, and all stack groups after the stack group is merged are in an online state, at this time, the management and control module also needs to determine the new basic information of each stack member and update the basic information to the second mapping relation table.

Step S506, when the active state is an online state, allocating the address to be allocated to the terminal.

Here, the steps S501, S502, and S506 correspond to the steps S101, S102, and S104, respectively, so those skilled in the art can understand the steps S501, S502, and S506 by referring to the steps S101, S102, and S104, and the description thereof is omitted here.

An embodiment of the present application provides an address allocation method, which may be executed by a DHCP server, and as shown in fig. 6, the method includes:

step S601, when receiving an address allocation request sent by a terminal, determining an available address in an address pool as an address to be allocated; wherein an address in the address pool is attributed to a stack member;

step S602, determining the target stacking member to which the address to be distributed belongs;

step S603, determining an active state of the target stack member in the stack group to which the terminal is connected;

step S604, when the activity state is an online state, the address to be allocated is allocated to the terminal;

here, the steps S601 to S604 correspond to the steps S101 to S104, respectively, so that those skilled in the art can refer to the steps S101 to S104 to understand the steps S601 to S604, and the description thereof is omitted.

Step S605, when receiving an address renewal request sent by a terminal, determining a target stack member to which an address requesting renewal belongs;

here, the method of determining the target stacking member to which the address to be allocated belongs in the foregoing step S102 may be referred to for determining the target stacking member to which the address to be allocated belongs. In implementation, the terminal may initiate a DHCPREQUEST message to the DHCP server for renewal, and after receiving the DHCP REQUEST message, the DHCP server obtains an IP address to which the terminal REQUESTs renewal from the DHCPREQUEST message, and determines a target stack member to which the IP address requesting renewal belongs.

Step S606, determining the active state of the target stack member in the stack group connected with the terminal;

here, the step S606 corresponds to the step S103, and therefore, a person skilled in the art can understand the step S606 by referring to the step S103, which is not described herein again.

Step S607, when the active state is on-line, sending a response for allowing renewal of lease to the terminal, and updating lease time;

here, renewal of lease is allowed and lease time is updated when the active state is the online state. In implementation, the DHCP server can reply a DHCP ACK message to the terminal and add the use lease information of the IP address in the option field;

step S608, when the active state is the offline state, sending a response of rejecting renewal to the terminal.

Here, when the active state is the offline state, it is described that the address requesting renewal is not allowed to be allocated, and it is necessary to refuse renewal. In implementation, the DHCP server may reply a DHCP NAK message to the terminal. After receiving the DHCP NAK message, the terminal can reinitiate the address request process.

Because the IP address allocated by the terminal already connected in the stacking system may belong to another stacking group different from the stacking group connected to the terminal after the stack is split, at this time, if the terminal still continues to lease the IP address, the terminal may occupy the address resource of the stacking group where the stacking member to which the IP address belongs is located, thereby affecting the allocation of the IP address of the terminal connected to the stacking group. In the address allocation method provided in the embodiment of the present application, the DHCP server only allows renewing addresses of stack members belonging to an online state when processing an address renewal request sent by a terminal. Therefore, the terminal can be prevented from renewing the lease of the IP addresses of the stack members belonging to other stack groups, and each stack group is ensured to have enough assignable addresses.

An embodiment of the present application provides an address allocation method, as shown in fig. 7A, the method includes:

step S701, a management and control module of the stacking system records basic information of stacking members;

here, the management and control module of the stacking system may be a common module of the stacking system, and the management and control module records basic information of all stack members in the current stacking system, including basic information of active members and split members, the basic information including Identification (ID) of the stack, active state, and stack group ID.

After the stack is split, the stack group ID and the activity state corresponding to the stack member may change, and each stack member is only in the online state in the stack group to which it belongs, and in the offline state in the other stack groups.

Step S702, the DHCP server calculates and saves the reference relationship between the address pool and the stack members;

here, the DHCP server may traverse each stack member in turn, computing whether the respective address pool is referenced by the stack member. The method of determining whether an address pool is referenced by the stack member may include: if the address pool is configured on the physical port and the port belongs to the stack member, the address pool is considered to be referred by the stack member; if the address pool is configured on the VLAN interface and any port of the stack member refers to the VLAN, the address pool is considered to be referred by the stack member; and if the address pool is configured on the aggregation port and any member port of the aggregation port belongs to the stack member, the address pool is considered to be referred by the stack member. After traversing each stacking member, the DHCP server calculates the number of the stacking members referred by each block address pool, and forms a sequence character string by the IDs of the stacking members referring to the address pool from small to large, wherein the ID of each stacking member in the sequence character string occupies one byte.

Step S703, when receiving an address allocation request sent by a terminal, a DHCP server allocates an address for the terminal according to the basic information of the stack members and the reference relationship between the address pool and the stack members;

here, the DHCP server first obtains the total number of stack members referencing each address pool according to the reference relationship between the address pools and the stack members, and divides each address pool into a plurality of blocks of a corresponding number according to the total number of stack members.

When a DHCP server receives a DHCP request sent by a terminal, a first available IP address is searched in an address pool corresponding to a current stacking system, an integer value corresponding to a little-end byte order of the IP address is subjected to remainder operation on the total number of stacking members referring to the address pool to obtain a result n, the nth byte of a sequence character string corresponding to the address pool is taken to obtain a stacking member ID, if the stacking member corresponding to the ID is in a stacking group connected with the current terminal, the IP address can be allocated, the DHCP server allocates the address to be allocated to the terminal, otherwise, the next available IP address is searched, and whether the IP address can be allocated is judged according to the same method. In implementation, the active state of the stack member in the current stack group can be obtained by reading the local configuration information, and if the stack member is in an online state, the stack member is determined to be in the stack group connected to the current terminal.

Fig. 7B is a schematic diagram of address allocation before and after stack splitting in the address allocation method provided in the embodiment of the present application, and as shown in fig. 7B, before stack splitting, all addresses 1 to 10 in the DHCP address pool 200 can be used, and the user 301 initiates a DHCP request and allocates the DHCP request to obtain address 1. After the stack is split, the stack group 100 is split into a stack group 110 composed of stack members 101 and a stack group 120 composed of stack members 102, the stack group 110 allows addresses to be allocated as

addresses

2, 4, 6, 8, 10, the stack group 120 allows addresses to be allocated as

addresses

1, 3, 5, 7, 9, and the addresses available for the two stacks do not overlap. The user 302 obtains the address 2 from the stack member 101 by initiating a DHCP request, the user 303 obtains the address 3 from the stack member 102 by initiating a DHCP request, and the addresses distributed by each user after stacking and merging do not conflict with each other.

In step S704, the DHCP server performs lease renewal processing when receiving the address lease renewal request from the terminal.

Here, if the terminal initiates a DHCP REQUEST message for renewal after the stack splitting, the DHCP server may determine whether the address is allowed to be allocated according to the method set forth in step S703, and if the address is allowed to be allocated, reply a DHCP ACK message to the terminal and update lease time; if the assignment is not allowed, replying a DHCP NAK message to the terminal to refuse to renew the lease, and releasing the address and re-acquiring the address after the terminal receives the DHCP NAK message.

Based on the foregoing embodiments, an address assignment apparatus provided in an embodiment of the present application includes modules, which may be implemented by a processor in an address assignment device (e.g., a DHCP server); of course, the implementation can also be realized through a specific logic circuit; in implementation, the processor may be a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like.

Fig. 8 is a schematic structural diagram of an address assignment apparatus according to an embodiment of the present application, and as shown in fig. 8, the apparatus 800 includes a first determining module 801, a second determining module 802, a third determining module 803, and a first sending module 804, where:

the first determining module 801 is configured to determine, when an address allocation request sent by a terminal is received, that one available address in an address pool is an address to be allocated; wherein an address in the address pool is attributed to a stack member;

the second determining module 802 is configured to determine a target stacking member to which the address to be allocated belongs;

the third determining module 803 is configured to determine an active state of the target stack member in the stack group to which the terminal is connected;

the first sending module 804 is configured to allocate the address to be allocated to the terminal when the active state is an online state.

In some embodiments, the apparatus further comprises: and the fourth determining module is used for determining the next available address in the address pool as a new address to be allocated when the active state is the offline state. Correspondingly, the second determining module is further configured to determine a target stacking member to which the new address to be allocated belongs; the third determination module is further configured to determine a status of the target stack member in the stack group; the first sending module is further configured to allocate the new address to be allocated to the terminal when the active state is an online state.

In some embodiments, the second determination module is further configured to: determining the identifier of a target stacking member to which the address to be distributed belongs through a mapping algorithm between a specific address and the identifier of the stacking member to which the address belongs; and determining the target stacking member according to the identification of the target stacking member.

In some embodiments, the second determination module is further configured to: determining a total number of stack members referencing the address pool; converting the address to be distributed into a host byte order format to obtain an integer value of the address to be distributed; carrying out remainder operation on the total number by utilizing the integer value of the address to be distributed to obtain a remainder; and determining the identifier of the stacking member with the sequence number of the remainder as the identifier of the target stacking member according to a specific list of identifiers of the stacking members which refer to the address pool.

In some embodiments, the second determination module is further configured to: determining, for each of the stack members in a current stack system, whether the address pool is referenced by the stack member prior to the determining a total number of stack members referencing the address pool.

In some embodiments, the second determination module is further configured to: when the address pool is configured on a physical port and the physical port belongs to the stack member, determining that the address pool is referenced by the stack member; or when the address pool is configured on a VLAN interface and any port of the stack member refers to the VLAN interface, determining that the address pool is referred by the stack member; or, when the address pool is configured on an aggregation port and any one member port of the aggregation port belongs to the stack member, determining that the address pool is referred to by the stack member.

In some embodiments, the second determination module is further configured to: inquiring a specific first mapping relation table according to the address to be distributed to obtain the identification of the target stack member; the mapping relation table is used for representing the corresponding relation between an address and the identifier of the stack member to which the address belongs; and determining the target stacking member according to the identification of the target stacking member.

In some embodiments, the second determination module is further configured to: before the target stacking member to which the address to be allocated belongs is determined, for each address in the address pool, determining the identifier of the stacking member to which each address belongs; establishing a mapping relation between each address and the identifier of the stacking member to which the address belongs; adding each mapping relation to the first mapping relation table.

In some embodiments, the third determination module is further configured to: determining an identity of the target stack member; determining an identifier of a stack group to which the terminal is connected; inquiring a specific second mapping relation table according to the identifier of the target stack member and the identifier of the stack group to obtain the activity state of the target stack member in the stack group connected with the terminal; the second mapping relation table is used for representing the corresponding relation among the identification of the stack member, the identification of the stack group and the activity state of the stack member.

In some embodiments, the second determining module is further configured to determine, when an address renewal request sent by the terminal is received, a target stacking member to which an address requesting for renewal belongs; the third determining module is further configured to determine an active status of the target stack member in a stack group to which the terminal is connected. Correspondingly, the device further comprises: a second sending module, configured to: when the active state is an online state, sending a response of allowing lease renewal to the terminal, and updating lease time; and when the active state is the offline state, sending a response of refusing to renew the lease to the terminal.

The above description of the apparatus embodiments, similar to the above description of the method embodiments, has similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the apparatus of the present application, reference is made to the description of the embodiments of the method of the present application for understanding.

It should be noted that, in the embodiment of the present application, if the address assignment method is implemented in the form of a software functional module and is sold or used as a standalone product, the address assignment method may also be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing an address allocation apparatus to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the present application are not limited to any specific combination of hardware and software.

Correspondingly, the embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program realizes the steps of the above method when being executed by a processor.

Correspondingly, an embodiment of the present application provides an address allocation apparatus, including a memory and a processor, where the memory stores a computer program executable on the processor, and the processor implements the steps in the above method when executing the program.

Here, it should be noted that: the above description of the storage medium and device embodiments is similar to the description of the method embodiments above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the embodiments of the storage medium and apparatus of the present application, reference is made to the description of the embodiments of the method of the present application for understanding.

It should be noted that fig. 9 is a schematic diagram of a hardware entity of an address assignment device in an embodiment of the present application, and as shown in fig. 9, the hardware entity of the device 900 includes: a processor 901, a communication interface 902 and a memory 903, wherein

The processor 901 generally controls the overall operation of the device 900.

The communication interface 902 may enable the device to communicate with other terminals or servers via a network.

The Memory 903 is configured to store instructions and applications executable by the processor 901, and may also cache data to be processed or already processed by the processor 901 and modules in the device 900, and may be implemented by a FLASH Memory (FLASH) or a Random Access Memory (RAM).

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.

It should be noted that, in this document, 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 like elements in a process, method, article, or apparatus that comprises the element.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units; can be located in one place or distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps for realizing the method embodiments can be completed by hardware related to program instructions, the program can be stored in a computer readable storage medium, and the program executes the steps comprising the method embodiments when executed; and the aforementioned storage medium includes: various media that can store program codes, such as a removable Memory device, a Read Only Memory (ROM), a magnetic disk, or an optical disk.

Alternatively, the integrated units described above in the present application may be stored in a computer-readable storage medium if they are implemented in the form of software functional modules and sold or used as independent products. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing an address allocation apparatus to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a removable storage device, a ROM, a magnetic or optical disk, or other various media that can store program code.

The above description is only for the embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for address allocation, the method comprising:

2. The method of claim 1, further comprising:

when the active state is an offline state, determining that the next available address in the address pool is a new address to be allocated;

determining a target stacking member to which the new address to be allocated belongs;

determining a status of the target stack member in the stack group;

and when the active state is the online state, allocating the new address to be allocated to the terminal.

3. The method of claim 1, wherein the determining the target stack member to which the address to be allocated belongs comprises:

determining the identifier of a target stacking member to which the address to be distributed belongs through a mapping algorithm between a specific address and the identifier of the stacking member to which the address belongs;

and determining the target stacking member according to the identification of the target stacking member.

4. The method according to claim 3, wherein the determining the identity of the target stack member to which the address to be allocated belongs by a mapping algorithm between a specific address and the identity of the stack member to which the address belongs comprises:

determining a total number of stack members referencing the address pool;

converting the address to be distributed into a host byte order format to obtain an integer value of the address to be distributed;

carrying out remainder operation on the total number by utilizing the integer value of the address to be distributed to obtain a remainder;

and determining the identifier of the stacking member with the sequence number of the remainder as the identifier of the target stacking member according to a specific list of identifiers of the stacking members which refer to the address pool.

5. The method of claim 4, wherein prior to said determining the total number of stack members referencing the address pool, the method further comprises:

for each of the stack members in a current stack system, determining whether the address pool is referenced by the stack member.

6. The method of claim 5, wherein the determining whether the address pool is referenced by the stack member comprises:

when the address pool is configured on a physical port and the physical port belongs to the stack member, determining that the address pool is referenced by the stack member;

or when the address pool is configured on a VLAN interface and any port of the stack member refers to the VLAN interface, determining that the address pool is referred by the stack member;

or, when the address pool is configured on an aggregation port and any one member port of the aggregation port belongs to the stack member, determining that the address pool is referred to by the stack member.

7. The method of claim 1, wherein the determining the target stack member to which the address to be allocated belongs comprises:

inquiring a specific first mapping relation table according to the address to be distributed to obtain the identification of the target stack member; the mapping relation table is used for representing the corresponding relation between an address and the identifier of the stack member to which the address belongs;

8. The method according to claim 7, wherein prior to said determining a target stack member to which the address to be assigned belongs, the method further comprises:

for each address in the address pool, determining an identification of a stack member to which each address belongs;

establishing a mapping relation between each address and the identifier of the stacking member to which the address belongs;

adding each mapping relation to the first mapping relation table.

9. The method of claim 1, wherein determining the activity status of the target stack member in the terminal-connected stack group comprises:

determining an identity of the target stack member;

determining an identifier of a stack group to which the terminal is connected;

inquiring a specific second mapping relation table according to the identifier of the target stack member and the identifier of the stack group to obtain the activity state of the target stack member in the stack group connected with the terminal;

the second mapping relation table is used for representing the corresponding relation among the identification of the stack member, the identification of the stack group and the activity state of the stack member.

10. The method of claim 1, further comprising:

when an address renewal request sent by a terminal is received, determining a target stacking member to which an address requesting for renewal belongs;

when the active state is an online state, sending a response of allowing lease renewal to the terminal, and updating lease time;

and when the active state is the offline state, sending a response of refusing to renew the lease to the terminal.

11. An address assignment device, the device comprising:

12. An address allocation apparatus comprising a memory and a processor, the memory storing a computer program operable on the processor, wherein the processor implements the steps of the method of any one of claims 1 to 10 when executing the program.

13. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 10.