CN115499414A - Address allocation method and device - Google Patents

Abstract

The present application provides an address allocation method and device, the method comprising: when receiving the first DHCP Discover message sent by the first DHCP client, judging whether the first subnet segment exists locally; if not, judging whether The first subnet segment can be divided from the first network segment; if so, the first subnet segment is created and the first address is obtained; when it is determined that the first DHCP client uses the first address to go online, the slave device sends the first subnet segment A synchronization message, the first synchronization message includes the network segment information of the first subnet segment and the first entry of the first DHCP client, so that the slave device can determine whether there is a corresponding first subnet segment locally, if it exists, Then remove the first address from the first subnet segment, and generate the first entry; if it does not exist, create the first subnet segment from the second network segment according to the network segment information of the first subnet segment, and create the first subnet segment from the The first address is removed from the first subnet segment, and the first entry is generated.

Description

Address allocation method and device

technical field

The present application relates to the technical field of communications, and in particular to an address allocation method and device.

Background technique

Distributed Resilient Network Interconnect (English: Distributed Resilient Network Interconnect, referred to as: DRNI) is a cross-device link aggregation technology, which virtualizes multiple physical devices into one network device at the aggregation level to achieve cross-device link aggregation , thus providing device-level redundancy protection and traffic load sharing.

As shown in Figure 1, Figure 1 is a schematic diagram of the DRNI network model. In FIG. 1 , a network device (Device A) and a network device B are neighbors to each other, network device A is a master device, and network device B is a slave device. The master and slave devices form load sharing and jointly forward the business traffic sent by the master. When one of the network devices fails, the service traffic can be quickly forwarded by the other network device to ensure the normal operation of the service traffic.

Dynamic Host Configuration Protocol (English: Dynamic Host Configuration Protocol, referred to as: DHCP) adopts the client (Client)/server (Server) mode, and the server dynamically assigns network configuration parameters such as IP addresses and default gateways to network devices.

As shown in FIG. 2 , FIG. 2 is a schematic diagram of a basic DHCP network. In FIG. 2, when the DHCP client and multiple DHCP servers are in the same physical network segment, the DHCP client broadcasts and sends a DHCP discovery (Discover) message. After each DHCP server receives the DHCP Discover message, it searches for an address pool on the same network segment according to the address of the interface receiving the DHCP Discover message, and selects an address from the address pool to assign to the DHCP client. Each DHCP server sends a DHCP offer (Offer) message to the client, and the DHCP Offer message includes information such as an address allocated by the DHCP server to the DHCP client, a default gateway address, and a DNS server address.

After receiving multiple DHCP Offer messages, the DHCP client may process the first received first DHCP Offer message, where the first DHCP Offer message includes an address of a DHCP server. The DHCP client broadcasts and sends a DHCP request (Request) message, and the DHCP Request message includes the DHCP server address selected by the DHCP client. The selected DHCP server sends a DHCP acknowledgment (Ack) message to the DHCP client, and the DHCP Ack message includes the lease period of the address allocated by the DHCP server. So far, the interaction process between the DHCP client and the DHCP server is completed.

After receiving the DHCP ACK message, the DHCP client checks whether the address assigned by the DHCP server can be used. If it can be used, the DHCP client successfully obtains the address and automatically starts the renewal process according to the lease period of the address; if it cannot be used, the DHCP client sends a DHCP rejection (Decline) message to the DHCP server to notify the DHCP service end to disable the address. The DHCP client starts a new address application process again.

Since DHCP is a widely used address allocation and management technology, and DRNI is also widely used, how to support DHCP in the DRNI environment is a problem that needs to be solved at present.

Currently, DHCP support in the DRNI environment can be implemented in the following ways:

Configure the DHCP server in the master and slave devices at the same time, but the assignable address segments of the address pools in the two network devices do not overlap. For example, address pool test_pool is configured in network device A and network device B, and the network segment of the address pool is 20.0.0.0/24. However, the address segment that network device A can allocate is 20.0.0.1-20.0.0.125, and the address segment that network device B can allocate is 20.0.0.126-20.0.0.254.

After each network device receives the DHCP Discover message sent by the DHCP client, it can use its own configured address segment to independently assign an address to the DHCP client, and after assigning the address, synchronize the locally generated client entry to the peer end , to ensure that the DHCP client can complete operations such as contract renewal and offline on any network device.

However, in the above implementation manners, the master and slave devices do not implement centralized management and allocation of addresses. For example, after the address segment in network device A is used up, even if there are still available addresses in the address segment in network device B, the DHCP client cannot successfully go online from network device A.

Contents of the invention

In view of this, the present application provides an address allocation method and device to solve the problem that the master-slave equipment cannot implement centralized management and allocation of addresses in the existing DRNI environment to support DHCP, resulting in the inability of the DHCP client to be in the The problem of going online at any network device in the DRNI environment.

In the first aspect, the present application provides an address allocation method, the method is applied to a master device, the master device is in the DRNI network, and the DRNI network also includes a slave device, and the master device is configured with a first An address pool, the first address pool has a corresponding first network segment, a second address pool is configured in the slave device, and the second address pool has a corresponding second network segment, the method includes:

When receiving the first DHCP Discover message sent by the first DHCP client, determine whether there is a first subnet segment that can be used to assign addresses locally;

If it does not exist, judging whether the first subnet segment can be divided from the first network segment;

If so, create the first subnet segment, and obtain the first address from the first subnet segment;

sending a first DHCP Offer message to the first DHCP client, where the first DHCP Offer message includes the first address;

After determining that the first DHCP client uses the first address to go online, send a first synchronization message to the slave device, the first synchronization message includes network segment information of the first subnet segment and The first entry of the first DHCP client, the first entry includes the first address, so that the slave device judges whether there is a corresponding first subnet segment locally, and if it exists, from the first subnet Eliminate the first address from the segment, and generate the first entry; if it does not exist, create the first subnet from the second subnet according to the network segment information of the first subnet a network segment, removing the first address from the first subnet segment, and generating the first entry;

Wherein, the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment.

In a second aspect, the present application provides an address allocation method, the method is applied to a slave device, the slave device is in the DRNI network, and the DRNI network also includes a master device, and the master device is configured with a first An address pool, the first address pool has a corresponding first network segment, a second address pool is configured in the slave device, and the second address pool has a corresponding second network segment, the method includes:

Receive a first synchronization message sent by the master device, where the first synchronization message includes the network segment information of the first subnet segment created by the master device in the first network segment and the first DHCP client's a first entry, where the first entry includes the first address of the first DHCP client;

According to the network segment information of the first subnet segment, determine whether there is a corresponding first subnet segment locally;

If it exists, removing the first address from the first subnet segment, and generating the first entry;

If it does not exist, create the first subnet segment from the second network segment, remove the first address from the first subnet segment, and generate the first entry;

Wherein, the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment.

In a third aspect, the present application provides an address allocation device, the device is applied to a master device, the master device is in the DRNI network, the DRNI network also includes a slave device, and the master device is configured with a first An address pool, the first address pool has a corresponding first network segment, a second address pool is configured in the slave device, the second address pool has a corresponding second network segment, and the device includes:

The first judging unit is configured to judge whether there is a first subnet segment locally available for address allocation when receiving the first DHCP Discover message sent by the first DHCP client;

A second judging unit, configured to judge whether the first subnet segment can be divided from the first subnet segment if it does not exist;

The obtaining unit is configured to, if yes, create the first subnet segment, and obtain the first address from the first subnet segment;

a sending unit, configured to send a first DHCP Offer message to the first DHCP client, where the first DHCP Offer message includes the first address;

The sending unit is further configured to, when it is determined that the first DHCP client uses the first address to go online, send a first synchronization message to the slave device, the first synchronization message includes the first The network segment information of the subnet segment and the first entry of the first DHCP client, the first entry includes the first address, so that the slave device determines whether there is a corresponding first subnet segment locally, and if so, Then remove the first address from the first subnet segment, and generate the first table entry; if it does not exist, according to the network segment information of the first subnet segment, from the second network segment creating the first subnet segment in the segment, removing the first address from the first subnet segment, and generating the first entry;

Wherein, the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment.

In a fourth aspect, the present application provides an address allocation device, the device is applied to a slave device, the slave device is in a DRNI network, and the DRNI network also includes a master device, and the master device is configured with a first An address pool, the first address pool has a corresponding first network segment, a second address pool is configured in the slave device, the second address pool has a corresponding second network segment, and the device includes:

a receiving unit, configured to receive a first synchronization message sent by the master device, where the first synchronization message includes network segment information of a first subnet segment created by the master device in the first network segment; A first entry of the first DHCP client, where the first entry includes a first address of the first DHCP client;

A first judging unit, configured to judge whether there is a corresponding first subnet segment locally according to the network segment information of the first subnet segment;

an elimination unit, configured to, if present, exclude the first address from the first subnet segment, and generate the first entry;

A creating unit, configured to create the first subnet segment from the second network segment if it does not exist, remove the first address from the first subnet segment, and generate the first table item;

Wherein, the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment.

In a fifth aspect, the present application provides a network device, including a processor and a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions that can be executed by the processor, and the processor is prompted to execute by the machine-executable instructions The method provided in the first aspect of the present application.

In a sixth aspect, the present application provides a network device, including a processor and a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions that can be executed by the processor, and the processor is prompted to execute by the machine-executable instructions The method provided by the second aspect of the present application.

Therefore, by applying the address assignment method and device provided by the present application, when the master device receives the first DHCP Discover message sent by the first DHCP client, the master device judges whether there is a first subnet segment that can be used to assign addresses locally; If it does not exist, the master device judges whether the first subnet segment can be divided from the first network segment; if so, the master device creates the first subnet segment and obtains the first address from the first subnet segment; The device sends the first DHCP Offer message to the first DHCP client, and the first DHCP Offer message includes the first address; when the master device determines that the first DHCP client uses the first address to go online, the master device sends the first DHCP Offer message to the slave device. Synchronization message, the first synchronization message includes the network segment information of the first subnet segment and the first entry of the first DHCP client, the first entry includes the first address, so that the slave device can determine whether there is a second The first subnet segment to which an address belongs, if it exists, the slave device will remove the first address from the first subnet segment and generate the first entry; if it does not exist, the slave device will Segment information, create the first subnet segment from the second network segment, remove the first address from the first subnet segment, and generate the first entry; wherein, the first address pool is the same as the second address pool, and the first The network segment is the same as the second network segment.

In this way, the master and slave devices share the same total network segment, and the subnet segment on the slave device is allocated by the master device, but each device exclusively enjoys the local subnet segment and assigns addresses to the DHCP clients that go online on itself, which realizes The centralized management of addresses avoids conflicts when multiple devices assign addresses at the same time. It solves the problem that in the existing implementation mode of supporting DHCP in the DRNI environment, the master and slave devices cannot realize the centralized management and allocation of addresses, which leads to the problem that the DHCP client cannot go online at any network device in the DRNI environment. Realized reducing the performance pressure of network equipment and increasing the online rate of DHCP clients.

Description of drawings

Figure 1 is a schematic diagram of the DRNI network model;

Fig. 2 is a schematic diagram of DHCP basic networking;

FIG. 3 is a flow chart of an address allocation method provided in an embodiment of the present application;

FIG. 4 is a flow chart of another address allocation method provided in the embodiment of the present application;

FIG. 5 is a structural diagram of an address allocation device provided by an embodiment of the present application;

FIG. 6 is a structural diagram of another address allocation device provided by the embodiment of the present application;

FIG. 7 is a hardware structure of a network device provided by an embodiment of the present application.

detailed description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present application as recited in the appended claims.

The terminology used in this application is for the purpose of describing particular embodiments only, and is not intended to limit the application. As used in this application and the appended claims, the singular forms "a", "the", and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more corresponding listed items.

It should be understood that although the terms first, second, third, etc. may be used in this application to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of the present application, first information may also be called second information, and similarly, second information may also be called first information. Depending on the context, the word "if" as used herein may be interpreted as "at" or "when" or "in response to a determination."

An address allocation method provided by the embodiment of the present application will be described in detail below. Referring to FIG. 3 , FIG. 3 is a flowchart of an address allocation method provided by an embodiment of the present application. This method is applied to the master device. The address allocation method provided in the embodiment of the present application may include the following steps.

Step 310: When receiving the first DHCP Discover message sent by the first DHCP client, determine whether there is a first subnet segment available locally for address allocation.

Specifically, as shown in Figure 1, the DRNI network includes a master device and a slave device. The master and slave devices are connected to the same switching device and receive messages sent by the host through the switching device, or the master and slave devices pass through the switch The device sends a message to the host. An IPL link has been established between the master and slave devices. The master and slave devices form load sharing and jointly forward the business traffic sent by the master. When one of the network devices fails, the service traffic can be quickly forwarded by the other network device to ensure the normal operation of the service traffic.

In the embodiment of this application, the same address pool has been configured in the master and slave devices, and the address segments that can be allocated by each address pool are exactly the same. The DHCP server function has been configured in the master and slave devices, which can independently receive the DHCP message sent by the DHCP client and assign addresses to the DHCP client.

Further, a first address pool is configured in the master device, and the first address pool has a corresponding first network segment, and a second address pool is configured in the slave device, and the second address pool has a corresponding second network segment. Wherein, the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment. For example, both the first network segment and the second network segment are 20.0.0.0/16.

When the main device receives the first DHCP Discover message sent by the first DHCP client, the main device judges whether there is a first subnet segment that can be used for address allocation locally. If the first subnet segment does not exist locally, the master device executes step 320 .

In the embodiment of the present application, the first network segment may be divided into multiple subnet segments, for example, 20.0.1.0/24, 20.0.2.0/24, 20.0.3.0/24 and so on. As an implementation method, the first subnet segment currently available for address allocation in the master device does not exist, that is, there are no remaining addresses in the currently existing subnet segment, that is, the number of unallocated addresses is 0, and the remaining The network segment of has not been divided; or, the first network segment has not been divided.

Step 320, if not, judge whether the first sub-network segment can be divided from the first network segment.

Specifically, according to the determination in step 310, if the first subnet segment does not exist, the master device continues to determine whether the first subnet segment can be divided from the first network segment. If the first subnet segment can be divided in the first network segment, the master device executes step 330; if the first subnet segment cannot be divided in the first network segment, the master device generates and sends the first subnet segment to the first DHCP client. The first notification message is used to prompt the first DHCP client that the address allocation fails.

Wherein, the first sub-network segment cannot be divided into the first network segment, that is, there is no remaining network segment in the first network segment to be divided.

Step 330, if yes, create the first subnet segment, and obtain the first address from the first subnet segment.

Specifically, according to the judgment in step 330, if the first subnet segment can be divided into the first network segment, the master device creates a subnet segment, that is, the first subnet segment, and obtains the first subnet segment from the first subnet segment. an address. the address of the first place.

It should be noted that although the master device assigns addresses to DHCP clients from available subnets, the mask assigned to clients is still the mask of the first network segment (that is, 16 in the previous example), not The mask of the subnet segment (ie, 24 in the previous example).

The main device can refer to the existing process of assigning addresses to DHCP clients, and obtain the first address from the first subnet segment, which will not be repeated here.

Step 340: Send a first DHCP Offer message to the first DHCP client, where the first DHCP Offer message includes the first address.

Specifically, according to the description of step 330, after the master device assigns an address to the first DHCP client, it generates a first DHCP Offer message according to existing DHCP regulations, and the first DHCP Offer message includes a yiaddr field and a siaddr field. The yiaddr field carries the first address, and the siaddr field carries the master device address.

The master device sends the first DHCP Offer message to the first DHCP client. After receiving the first DHCP Offer message, the first DHCP client obtains the first address and the address of the master device therefrom, and determines that the master device assigns the first address to itself.

It can be understood that, according to existing DHCP regulations, after assigning the first address to the first DHCP client, the main device also records the assigned first address corresponding to the first DHCP client.

Step 350, when it is determined that the first DHCP client uses the first address to go online, send a first synchronization message to the slave device, the first synchronization message includes the network address of the first subnet segment Segment information and the first entry of the first DHCP client, the first entry includes the first address, so that the slave device determines whether there is a corresponding first subnet segment locally, and if it exists, from the first address Eliminate the first address in a subnet segment, and generate the first entry; if it does not exist, create the address from the second network segment according to the network segment information of the first subnet segment The first subnet segment, removing the first address from the first subnet segment, and generating the first entry.

Specifically, according to the description of step 340, after the first DHCP client receives the first DHCP Offer message, according to the existing DHCP regulations, select the address sent by the DHCP server, broadcast and send the DHCP Request message, verify whether the address is available, etc. process. At the same time, as the master device of the DHCP server, it also continues to perform DHCP interaction with the first DHCP client.

When the first DHCP client successfully uses the first address as its own address, the main device generates a first entry of the first DHCP client. The first entry includes the first DHCP client identifier, the first address, the lease information of the first address, and the like.

The master device generates and sends the first synchronization message to the slave device through the IPL link. The first synchronization message includes network segment information of the first subnet segment and a first entry.

After receiving the first synchronization message, the slave device acquires the network segment information of the first subnet segment and the first table entry therefrom. The slave device judges whether there is a corresponding first subnet segment locally.

It can be understood that if the first DHCP client is the first client to go online in the first subnet segment, when the master device synchronizes the network segment information and DHCP client entries with the slave device, there is no corresponding DHCP client in the slave device. The first subnet segment. At this time, the slave device creates the first subnet segment from the second network segment according to the network segment information of the first subnet segment, and removes the first address from the first subnet segment. The slave device also locally generates the first entry. In this way, the master and slave devices realize the synchronization of DHCP client entries.

If the first DHCP client is not the first client to go online in the first subnet segment, when the master device synchronizes the network segment information and DHCP client entries with the slave device, there should be a corresponding first subnet segment in the slave device . At this time, the slave device removes the first address from the first subnet segment. The slave device also locally generates the first entry. In this way, the master and slave devices realize the synchronization of DHCP client entries.

The aforementioned slave device removes the first address from the first subnet segment, that is, the slave device records the first address as an allocated address, and records the first address corresponding to the first DHCP client.

Therefore, by applying the address allocation method provided by this application, when the master device receives the first DHCP Discover message sent by the first DHCP client, the master device judges whether there is a first subnet segment available for address allocation locally; if not exists, the master device judges whether the first subnet segment can be divided from the first network segment; if so, the master device creates the first subnet segment and obtains the first address from the first subnet segment; The first DHCP client sends the first DHCPOffer message, the first DHCP Offer message includes the first address; when the master device determines that the first DHCP client uses the first address to go online, the master device sends the first synchronization message to the slave device , the first synchronization message includes the network segment information of the first subnet segment and the first entry of the first DHCP client, and the first entry includes the first address, so that the slave device can determine whether there is a first address belonging to the local If it exists, the slave device will remove the first address from the first subnet segment and generate the first table entry; if it does not exist, the slave device will, according to the network segment information of the first subnet segment, Create the first subnet segment from the second network segment, remove the first address from the first subnet segment, and generate the first entry; wherein, the first address pool is the same as the second address pool, and the first network segment and The second network segment is the same.

In this way, the master and slave devices share the same total network segment, and the subnet segment on the slave device is allocated by the master device, but each device exclusively enjoys the local subnet segment and assigns addresses to the DHCP clients that go online on itself, which realizes The centralized management of addresses avoids conflicts when multiple devices assign addresses at the same time. It solves the problem that in the existing implementation mode of supporting DHCP in the DRNI environment, the master and slave devices cannot realize the centralized management and allocation of addresses, which leads to the problem that the DHCP client cannot go online at any network device in the DRNI environment. Realized reducing the performance pressure of network equipment and increasing the online rate of DHCP clients.

Optionally, the embodiment of the present application further includes: after the master device locally exists the first subnet segment, the master device assigns an address to the first DHCP client.

Specifically, if the first subnet segment exists locally, the main device obtains the first address from the first subnet segment. The first address is the address allocated by the master device to the first DHCP client.

It can be understood that after the master device assigns an address to the first DHCP client, steps 340 to 350 may be performed repeatedly, which will not be repeated here.

In the embodiment of this application, since the first network segment can be divided into multiple subnet segments, as an implementation method, there is usually one first subnet segment currently available for address allocation in the main device, that is, the current There is only one subnet segment that can provide unassigned addresses.

Of course, in another implementation manner, there may also be multiple subnet segments for address allocation in the main device, that is to say, currently there are multiple subnet segments that can provide unallocated addresses. If there are multiple subnet segments locally, the master device can determine the subnet segment to which the interface address belongs through the interface address of the interface receiving the DHCP Discover message, and obtain an address in the subnet segment.

In this embodiment of the present application, the number of subnetwork segments that can currently provide unallocated addresses is taken as one for subsequent descriptions, and the case of multiple subnetwork segments is the same.

Optionally, the embodiment of the present application also includes: the slave device cannot assign an address to the second DHCP client, and applies for a subnet segment from the master device.

Specifically, when the slave device receives the second DHCP Discover message sent by the second DHCP client, the slave device judges whether there is a subnet segment that can be used to assign addresses locally, for example, the second subnet segment (in order to be consistent with the aforementioned implementation The subnet segment in the example is distinguished, which is called the second subnet segment here).

If there is a second subnet segment, the slave device obtains the first address from the second subnet segment. The second address is the address allocated by the slave device to the second DHCP client.

It can be understood that, after the slave device assigns an address to the second DHCP client, it may repeat the same process as the master device performs step 340-step 350, which will not be repeated here.

If there is no second subnet segment, the slave device sends a second DHCP Discover message to the master device through the IPL link.

It can be understood that the second subnet segment currently available for address allocation in the slave device does not exist, that is, there are no remaining addresses in the currently existing subnet segment, that is, the number of unallocated addresses is 0, and the remaining The network segment has not been divided; or, the second network segment has not been divided.

After receiving the second DHCP Discover message, the master device judges whether the second subnet segment can be divided from the first network segment. If the second subnet can be divided in the first network segment, the master device creates the second subnet segment and obtains the second address from the second subnet segment, and the second address is the second DHCP client for the master device assigned address. Wherein, the second subnet segment does not overlap with other subnet segments created in the master device, so as to avoid address conflicts.

If the second subnet segment cannot be divided in the first network segment, the master device generates and sends a DHCP NAK message to the slave device to prompt the slave device to fail to allocate an address for the second DHCP client. The slave device generates and sends a second notification message to the second DHCP client, to prompt the second DHCP client that the address allocation fails.

Wherein, the second sub-network segment cannot be divided in the first network segment, that is, there is no remaining network segment in the first network segment for division.

After assigning the address to the second DHCP client, the master device generates a second DHCP Offer message, where the second DHCP Offer message includes a yiaddr field and a siaddr field. The yiaddr field carries the second address, and the siaddr field carries the primary device address.

The master device sends the second DHCP Offer message to the slave device. After receiving the second DHCP Offer message, the slave device acquires the second address therefrom. According to the second address, the slave device creates a second subnet segment in the second network segment. The slave device updates the master device address carried in the siaddr field included in the second DHCP Offer message to the slave device address, and sends the second DHCP Offer message to the second DHCP client. After receiving the second DHCP Offer message, the second DHCP client obtains the second address and the address of the slave device, and determines that the slave device allocates the second address for itself.

It can be understood that, according to existing DHCP regulations, the slave device also records the assigned second address corresponding to the second DHCP client. At the same time, when the second DHCP client successfully uses the second address as its own address, the slave device also generates a second entry of the second client. The second entry includes the second DHCP client identifier, the second address, and the second entry. Lease information of the second address, etc.

The slave device generates and sends the second synchronization message to the master device through the IPL link. The second synchronization message includes network segment information of the second subnet segment and a second entry.

After receiving the second synchronization message, the master device acquires the network segment information of the second subnet segment and the second table entry therefrom. According to the network segment information of the second subnet segment and the second address, the master device removes the second address from the second subnet segment. The master device also locally generates the second entry. In this way, the master and slave devices realize the synchronization of DHCP client entries.

The main device removes the second address from the second subnet segment, that is, the main device records the second address as an allocated address, and records the second address corresponding to the second DHCP client.

Optionally, the embodiment of the present application also includes: a process in which the master and slave devices reclaim the allocated addresses and synchronize to the peer end.

Specifically, according to existing DHCP regulations, after successfully obtaining an address, the DHCP client can release its own address at any time by sending a DHCPRelease message. After receiving the DHCP Release message, the DHCP server will recycle the corresponding address and reassign it.

After receiving the DHCP Release message sent by the third DHCP client, the master device reclaims the third address allocated to the third DHCP client. At the same time, the master device deletes the locally recorded correspondence between the third address and the third DHCP client, and related entries of the third DHCP client.

The master device generates and sends a third synchronization message to the slave device through the IPL link, where the third synchronization message includes the third address and network segment information of the third subnet segment.

After receiving the third synchronization message, the slave device obtains the third address and network segment information of the third subnet segment. The slave device reclaims the third address from the third subnet segment. At the same time, the slave device deletes the correspondence between the locally recorded third address and the third DHCP client, and the related entries of the third DHCP client. The slave device also judges whether all addresses included in the third subnet segment have been recycled, and if so, deletes the third subnet segment from the device.

Similarly, the master device also judges whether all the addresses included in the third subnet segment have been recycled, and if so, the master device deletes the third subnet segment, and the third subnet segment can be repeatedly divided later.

Further, if the fourth DHCP client goes online at the slave device, when the fourth DHCP client releases its own fourth address, it may send a DHCP Release message to the slave device through the IPL link.

After the slave device receives the DHCP Release message, it also executes the above-mentioned process of reclaiming the address of the master device, deleting the local record, sending the synchronization message, and deleting the subnet segment; The entire process of recording and deleting subnet segments is only briefly described here.

The master device receives the fourth synchronization message sent by the slave device, where the fourth synchronization message includes the fourth address and network segment information of the fourth subnet segment to which the fourth address belongs. According to the network segment information of the fourth subnet segment and the fourth address, the master device reclaims the fourth address from the fourth subnet segment. The master device judges whether all the addresses included in the fourth subnet segment have been recycled; if so, the master device deletes the fourth subnet segment, and the fourth subnet segment can be repeatedly divided subsequently.

Optionally, the embodiment of the present application further includes: after the master-slave device is switched, the new master device synchronizes information with the new slave device.

Specifically, if the master device fails, the master device restarts, and after the restart, the master and slave devices perform role switching, the master device is downgraded to a new slave device, and the slave device is upgraded to a new master device.

The new master device will update the network segment status of the local subnet segment in the peer state to the local state, while the network segment status of the local subnet segment remains unchanged. The new master device generates and sends the fifth synchronization message to the new slave device through the IPL link. The fifth synchronization message includes the network segment information of all subnet segments existing in the new master device and all DHCP clients that have gone online. The third entry of the client, the third entry includes the fifth address of each DHCP client.

After the new slave device receives the fifth synchronization message, it obtains the network segment information of all existing subnet segments in the new master device and the third entries of all the online DHCP clients. According to the network segment information of all subnet segments, the new slave device creates corresponding subnet segments in the first network segment.

According to the fifth address, the new slave device removes the fifth address from the corresponding subnet segment; at the same time, the new slave device also generates a third entry.

It can be understood that, in the foregoing embodiments, the process of the device removing addresses from the subnet segment and generating DHCP client entries has been described in detail, and will not be repeated here.

Optionally, the embodiment of the present application further includes: after the master device creates a subnet segment in the local network segment, it records the network segment status of the created subnet segment.

Specifically, after the master device creates the first subnet segment, the master device records the network segment status of the first subnet segment as the local state, that is, the first subnet segment created by the master device in the first local network segment , the addresses in the first subnet segment can only be allocated by the master device. At the same time, the first subnet segment is also created in the slave device, and the status of the first subnet segment is recorded as the peer state, and the address in the first subnet segment cannot be allocated by the slave device.

After the master device creates the second subnet segment, the master device records the status of the second subnet segment as the peer state, that is, the master device creates the second subnet segment for the slave device in the first network segment. The addresses in the second subnet segment can only be assigned by the slave device, not the master device.

The new slave device, that is, the original master device creates the fifth subnet segment. After the master-slave device is switched over, the new slave device records the status of the fifth subnet segment as the peer state, that is, the network segment in the fifth subnet segment The address can only be assigned by the new master device, that is, the original slave device, and the new slave device cannot be assigned.

For example, before the failure of the primary device, the existing subnet segments in the primary device include the first subnet segment 20.0.2.0/24 (local status), the second subnet segment 20.0.4.0/24 (peer status), and the backup The existing subnet segments in the device include the first subnet segment 20.0.2.0/24 (peer state) and the second subnet segment 20.0.4.0/24 (local state).

After the master device restarts, the slave device is upgraded to the new master device, and the master device is downgraded to the new slave device. The new master device will update the network segment status of the local subnet segment in the peer state to the local state, while the network segment status of the local subnet segment remains unchanged.

The new master device generates and sends the fifth synchronization message to the new slave device through the IPL link. In this way, after the master-slave device is switched over, the new master device includes the first subnet segment 20.0.2.0/24 (local status), the second subnet segment 20.0.4.0/24 (local status); the new slave device includes The first subnet segment is 20.0.2.0/24 (peer state), and the second subnet segment is 20.0.4.0/24 (peer state).

It should be noted that, in the foregoing embodiments, the above-mentioned synchronization message can be realized by using the following messages, one is realized by borrowing DHCP protocol messages, and the other is realized by private network messages defined by each manufacturer.

Another address allocation method provided by the embodiment of the present application will be described in detail below. Referring to FIG. 4, FIG. 4 is a flow chart of another address allocation method provided by the embodiment of the present application. This method is applied to slave devices. The address allocation method provided in the embodiment of the present application may include the following steps.

Step 410: Receive a first synchronization packet sent by the master device, where the first synchronization packet includes the network segment information of the first subnet segment created by the master device in the first network segment and the first A first entry of the DHCP client, where the first entry includes the first address of the first DHCP client.

Specifically, the same address pool has been configured in the master and slave devices, and the address segments that can be allocated by each address pool are exactly the same. The DHCP server function has been configured in the master and slave devices, which can independently receive the DHCP message sent by the DHCP client and assign addresses to the DHCP client.

Further, a first address pool is configured in the master device, and the first address pool has a corresponding first network segment, and a second address pool is configured in the slave device, and the second address pool has a corresponding second network segment. Wherein, the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment. For example, both the first network segment and the second network segment are 20.0.0.0/16.

According to the foregoing embodiments, it can be seen that the master device assigns an address to the first DHCP client, and when the first DHCP client successfully uses the first address as its own address, the master device generates a first entry of the first DHCP client. The master device generates and sends the first synchronization message to the slave device through the IPL link. The first synchronization message includes network segment information of the first subnet segment and a first entry.

After receiving the first synchronization message, the slave device acquires the network segment information of the first subnet segment and the first table entry therefrom.

Step 420, according to the network segment information of the first subnet segment, determine whether there is a corresponding first subnet segment locally.

Specifically, according to the description of step 410, after obtaining the network segment information of the first subnet segment from the device, it is determined whether there is a corresponding first subnet segment locally.

If the first subnet segment exists locally, the slave device executes step 430; if the first subnet segment does not exist locally, the slave device executes step 440.

Step 430, if it exists, remove the first address from the first subnet segment, and generate the first entry.

Specifically, according to the judgment in step 420, the slave device locally has the first subnet segment, and the slave device removes the first address from the first subnet segment. The slave device also locally generates the first entry. In this way, the master and slave devices realize the synchronization of DHCP client entries.

Step 440: If it does not exist, create the first subnet segment from the second network segment, remove the first address from the first subnet segment, and generate the first entry.

Specifically, according to the judgment in step 420, the first subnet segment does not exist locally in the slave device, and the slave device creates the first subnet segment from the second network segment according to the network segment information of the first subnet segment, and creates the first subnet segment from the first subnet segment. Eliminate the first address in the subnet segment. The slave device also locally generates the first entry. In this way, the master and slave devices realize the synchronization of DHCP client entries.

Therefore, by applying the address allocation method provided by this application, the slave device receives the first synchronization message sent by the master device, and the first synchronization message includes the network segment of the first subnet segment created by the master device in the first network segment Information and the first entry of the first DHCP client, the first entry includes the first address of the first DHCP client; according to the network segment information of the first subnet segment, the slave device determines whether there is a corresponding first subnet locally segment; if it exists, the slave device will remove the first address from the first subnet segment and generate the first entry; if it does not exist, the slave device will create the first subnet segment from the second The first address is removed from the subnet segment, and the first entry is generated.

In this way, the master and slave devices share the same total network segment, and the subnet segment on the slave device is allocated by the master device, but each device exclusively enjoys the local subnet segment and assigns addresses to the DHCP clients that go online on itself, which realizes The centralized management of addresses avoids conflicts when multiple devices assign addresses at the same time. It solves the problem that in the existing implementation mode of supporting DHCP in the DRNI environment, the master and slave devices cannot realize the centralized management and allocation of addresses, which leads to the problem that the DHCP client cannot go online at any network device in the DRNI environment. Realized reducing the performance pressure of network equipment and increasing the online rate of DHCP clients.

Optionally, the embodiment of the present application also includes: the slave device cannot assign an address to the second DHCP client, and applies for a subnet segment from the master device.

Specifically, when the slave device receives the second DHCP Discover message sent by the second DHCP client, the slave device judges whether there is a subnet segment that can be used to assign addresses locally, for example, the second subnet segment (in order to be consistent with the aforementioned implementation The subnet segment in the example is distinguished, which is called the second subnet segment here).

If there is a second subnet segment, the slave device obtains the first address from the second subnet segment. The second address is the address allocated by the slave device to the second DHCP client.

It can be understood that, after the slave device assigns an address to the second DHCP client, it may repeat the same process as the master device performs step 340-step 350, which will not be repeated here.

If there is no second subnet segment, the slave device sends a second DHCP Discover message to the master device through the IPL link.

After receiving the second DHCP Discover message, the master device judges whether the second subnet segment can be divided from the first network segment. If the second subnet can be divided in the first network segment, the master device creates the second subnet segment and obtains the second address from the second subnet segment, and the second address is the second DHCP client for the master device assigned address. Wherein, the second subnet segment does not overlap with other subnet segments created in the master device, so as to avoid address conflicts.

If the second subnet segment cannot be divided in the first network segment, the master device generates and sends a DHCP NAK message to the slave device to prompt the slave device to fail to allocate an address for the second DHCP client. The slave device generates and sends a second notification message to the second DHCP client, to prompt the second DHCP client that the address allocation fails.

After assigning the address to the second DHCP client, the master device generates a first DHCP Offer message, where the first DHCP Offer message includes a yiaddr field and a siaddr field. The yiaddr field carries the second address, and the siaddr field carries the primary device address.

The master device sends the first DHCP Offer message to the slave device. After receiving the first DHCP Offer message, the slave device acquires the second address therefrom. According to the second address, the slave device creates a second subnet segment in the second network segment. The slave device updates the master device address carried in the siaddr field included in the first DHCP Offer message to the slave device address to obtain the second DHCP Offer message.

Send the second DHCP Offer message from the device to the second DHCP client. After receiving the second DHCP Offer message, the second DHCP client obtains the second address and the address of the slave device, and determines that the slave device allocates the second address for itself.

It can be understood that, according to existing DHCP regulations, the slave device also records the assigned second address corresponding to the second DHCP client. At the same time, when the second DHCP client successfully uses the second address as its own address, the slave device also generates a second entry of the second client. The second entry includes the second DHCP client identifier, the second address, and the second entry. Lease information of the second address, etc.

The slave device generates and sends the second synchronization message to the master device through the IPL link. The second synchronization message includes network segment information of the second subnet segment and a second entry.

After receiving the second synchronization message, the master device acquires the network segment information of the second subnet segment and the second table entry therefrom. According to the network segment information of the second subnet segment and the second address, the master device removes the second address from the second subnet segment. The master device also locally generates the second entry. In this way, the master and slave devices realize the synchronization of DHCP client entries.

Optionally, the embodiment of the present application also includes: a process in which the master and slave devices reclaim the allocated addresses and synchronize to the peer end.

Specifically, according to existing DHCP regulations, after successfully obtaining an address, the DHCP client can release its own address at any time by sending a DHCPRelease message. After receiving the DHCP Release message, the DHCP server will recycle the corresponding address and reassign it.

After receiving the DHCP Release message sent by the third DHCP client, the master device reclaims the third address allocated to the third DHCP client. At the same time, the master device deletes the locally recorded correspondence between the third address and the third DHCP client, and related entries of the third DHCP client.

The master device generates and sends a third synchronization message to the slave device through the IPL link, where the third synchronization message includes the third address and network segment information of the third subnet segment.

After receiving the third synchronization message, the slave device obtains the third address and network segment information of the third subnet segment. The slave device reclaims the third address from the third subnet segment. At the same time, the slave device deletes the correspondence between the locally recorded third address and the third DHCP client, and the related entries of the third DHCP client. The slave device also judges whether all the addresses included in the third subnet segment have been reclaimed, and if so, deletes the third subnet segment from the device, and the third subnet segment can be redistributed later.

Similarly, the master device also judges whether all addresses included in the third subnet segment have been recycled, and if so, the master device deletes the third subnet segment.

Further, if the fourth DHCP client goes online at the slave device, when the fourth DHCP client releases its own fourth address, it may send a DHCP Release message to the slave device through the IPL link.

After the slave device receives the DHCP Release message, it also executes the above-mentioned process of reclaiming the address of the master device, deleting the local record, sending the synchronization message, and deleting the subnet segment; The entire process of recording and deleting subnet segments is only briefly described here.

The slave device generates and sends a fourth synchronization message to the master device through the IPL link, where the fourth synchronization message includes the fourth address and network segment information of the fourth subnet segment to which the fourth address belongs.

After the master device receives the fourth synchronization message, according to the network segment information of the fourth subnet segment and the fourth address, the master device recovers the fourth address from the fourth subnet segment. The master device judges whether all addresses included in the fourth subnet segment have been recycled; if yes, the master device deletes the fourth subnet segment.

Similarly, the slave device also judges whether all addresses included in the fourth subnet segment have been recycled, and if so, deletes the fourth subnet segment from the device.

Optionally, the embodiment of the present application further includes: after the master-slave device is switched, the new master device synchronizes information with the new slave device.

Specifically, if the master device fails, the master device restarts, and after restarting, the master and slave devices perform role switching, the master device is downgraded to a new slave device, and the slave device is upgraded to a new master device.

The new master device will update the network segment status of the local subnet segment in the peer state to the local state, while the network segment status of the local subnet segment remains unchanged. The new master device generates and sends the fifth synchronization message to the new slave device through the IPL link. The fifth synchronization message includes the network segment information of all subnet segments existing in the new master device and all DHCP clients that have gone online. The third entry of the client, the third entry includes the fifth address of each DHCP client.

After the new slave device receives the fifth synchronization message, it obtains the network segment information of all existing subnet segments in the new master device and the third entries of all the online DHCP clients. According to the network segment information of all subnet segments, the new slave device creates corresponding subnet segments in the first network segment.

According to the fifth address, the new slave device removes the fifth address from the corresponding subnet segment; at the same time, the new slave device also generates a third entry.

Optionally, the embodiment of the present application further includes: after the slave device creates a subnet segment in the local network segment, a process of recording the network segment status of the created subnet segment.

Specifically, after the slave device creates the first subnet segment, the slave device records the network segment status of the first subnet segment as the peer state, that is, the address in the first subnet segment cannot be allocated by the slave device, only can be assigned by the master device.

After the slave device creates the second subnet segment, the slave device records the network segment status of the second subnet segment as the local state, and the address in the second subnet segment can only be allocated by the slave device, but not by the master device.

It should be noted that, in the foregoing embodiments, the above-mentioned synchronization message can be realized by using the following messages, one is realized by borrowing DHCP protocol messages, and the other is realized by private network messages defined by each manufacturer.

Based on the same inventive concept, the embodiment of the present application also provides an address allocation device corresponding to the address allocation method. Referring to Fig. 5, Fig. 5 is an address allocation device provided by an embodiment of the present application, the device is applied to a master device, the master device is in the DRNI network, and the DRNI network also includes slave devices, the master device A first address pool is configured in the device, the first address pool has a corresponding first network segment, a second address pool is configured in the slave device, the second address pool has a corresponding second network segment, and the device include:

The first judging unit 510 is configured to, when receiving the first DHCP Discover message sent by the first DHCP client, judge whether there is a first subnet segment available locally for address allocation;

The second judging unit 520 is configured to judge whether the first subnet segment can be divided from the first subnet segment if it does not exist;

The obtaining unit 530 is configured to, if yes, create the first subnet segment, and obtain the first address from the first subnet segment;

A sending unit 540, configured to send a first DHCP Offer message to the first DHCP client, where the first DHCP Offer message includes the first address;

The sending unit 540 is further configured to, when it is determined that the first DHCP client uses the first address to go online, send a first synchronization message to the slave device, the first synchronization message includes the first The network segment information of a subnet segment and the first entry of the first DHCP client, the first entry includes the first address, so that the slave device can determine whether there is a corresponding first subnet segment locally, if there is , remove the first address from the first subnet segment and generate the first entry; if it does not exist, according to the network segment information of the first subnet segment, from the Create the first subnet segment in the network segment, remove the first address from the first subnet segment, and generate the first entry;

Wherein, the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment.

Optionally, the acquiring unit 530 is further configured to, if it exists, acquire the first address from the first subnet segment;

The sending unit 540 is further configured to send a first DHCP Offer message to the first DHCP client, where the first DHCP Offer message includes the obtained first address;

The sending unit 540 is further configured to, when it is determined that the first DHCP client uses the first address to go online, send a first synchronization message to the slave device, the first synchronization message includes the first The network segment information of a subnet segment and the first entry of the first DHCP client, the first entry includes the first address, so that the slave device can determine whether there is a corresponding first subnet segment locally, if there is , then remove the first address from the first subnet segment and generate the first entry; if it does not exist, according to the network segment information of the first subnet segment, in the second The first subnet segment is created in the network segment, the first address is removed from the first subnet segment, and the first entry is generated.

Optionally, the second judging unit 520 is further configured to, when receiving the second DHCPDiscover message sent by the slave device, judge whether the second subnet segment can be divided from the first network segment;

The obtaining unit 530 is further configured to, if yes, create the second subnet segment, and obtain a second address from the second subnet segment, the second address is for the master device to send the The address assigned by the second DHCP client of the second DHCP Discover message;

The sending unit 540 is further configured to send a second DHCP Offer message to the slave device, where the second DHCP Offer message includes the second address, so that the slave device, according to the second address, creating the second subnet segment in the second network segment;

The device also includes: a receiving unit (not shown in the figure), configured to receive the second synchronization message sent by the slave device, the second synchronization message including the network segment information of the second subnet segment and a second entry of the second DHCP client, where the second entry includes the second address;

an elimination unit (not shown in the figure), configured to eliminate the second address from the second subnet segment according to the network segment information of the second subnet segment and the second address;

a generating unit (not shown in the figure), configured to generate the second entry;

Wherein, the second subnet segment does not overlap with other subnet segments created in the master device.

Optionally, the sending unit 540 is further configured to send a third synchronization message to the slave device if the third address included in the third subnet segment has been recovered, and the third synchronization message includes the The third address and the network segment information of the third subnet segment, so that the slave device reclaims the third address from the third subnet segment, and determines the third subnet segment After all the included addresses have been recycled, delete the third subnet segment;

The device also includes: a deletion unit (not shown in the figure), configured to delete the third subnet segment if all addresses included in the third subnet segment have been recovered;

Wherein, the third address is the address of the third DHCP client.

Optionally, the receiving unit (not shown in the figure) is further configured to receive a fourth synchronization message sent by the slave device, the fourth synchronization message includes a fourth address and the fourth address belongs to The network segment information of the fourth subnet segment;

The device further includes: a reclaiming unit (not shown in the figure), configured to reclaim the first subnetwork segment from the fourth subnetwork segment according to the network segment information of the fourth subnetwork segment and the fourth address. Four addresses;

A third judging unit (not shown in the figure), configured to judge whether all addresses included in the fourth subnet segment have been recycled;

The deletion unit (not shown in the figure) is also used to, if yes, delete the fourth subnet segment;

Wherein, the fourth address is the address of the fourth DHCP client.

Optionally, when the master device is downgraded to a new slave device and the slave device is upgraded to a new master device, the receiving unit (not shown in the figure) is further configured to receive the first Five synchronization messages, the fifth synchronization message includes the network segment information of all existing subnet segments in the new master device and the third entry of all DHCP clients that have gone online, and the third entry includes a fifth address for each DHCP client;

The eliminating unit (not shown in the figure) is further configured to, according to the network segment information of all the subnet segments and the fifth address, create corresponding subnet segments in the first network segment, and from Removing the fifth address from the corresponding subnet segment;

The generating unit (not shown in the figure) is further configured to generate the third entry.

Optionally, the device further includes: a recording unit (not shown in the figure), configured to record the network segment state of the first subnet segment as a local state;

The recording unit (not shown in the figure) is also used to record the network segment status of the second subnet segment as the opposite end status;

The recording unit (not shown in the figure) is further configured to record the network segment state of the fifth subnetwork segment as the opposite end state.

Based on the same inventive concept, the embodiment of the present application also provides an address allocation device corresponding to the address allocation method. Referring to Fig. 6, Fig. 6 is another address allocation device provided by the embodiment of the present application, the device is applied to a slave device, the slave device is in the DRNI network, and the DRNI network also includes a master device, the A first address pool is configured in the master device, the first address pool has a corresponding first network segment, a second address pool is configured in the slave device, the second address pool has a corresponding second network segment, and the Devices include:

A receiving unit 610, configured to receive a first synchronization message sent by the master device, where the first synchronization message includes network segment information of a first subnet segment created by the master device in the first network segment and a first entry of the first DHCP client, where the first entry includes the first address of the first DHCP client;

The first judging unit 620 is configured to judge whether there is a corresponding first subnet segment locally according to the network segment information of the first subnet segment;

The elimination unit 630 is configured to, if it exists, eliminate the first address from the first subnet segment, and generate the first entry;

The creation unit 640 is configured to create the first subnet segment from the second network segment if it does not exist, remove the first address from the first subnet segment, and generate the first subnet segment. entry;

Wherein, the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment.

Optionally, the second judging unit (not shown in the figure) is configured to judge whether there is a second subnet segment locally available for address allocation when receiving the second DHCP Discover message sent by the second DHCP client ;

The device further includes: a sending unit (not shown in the figure), configured to send the second DHCP Discover message to the master device if it does not exist;

The receiving unit 610 is further configured to receive a first DHCP Offer message sent by the master device, the first DHCP Offer message includes a second address, and the second address is locally created by the master device The address assigned to the second DHCP client in the second subnet segment;

The creating unit 640 is further configured to create the second subnet segment in the second network segment according to the second address;

The sending unit (not shown in the figure) is further configured to send a second DHCP Offer message to the second DHCP client, where the second DHCP Offer message includes the second address;

The sending unit (not shown in the figure) is further configured to, when it is determined that the second DHCP client uses the second address to go online, send a second synchronization message to the master device, and the second synchronization The message includes the network segment information of the second subnet segment and the second entry of the second DHCP client, and the second entry includes the second address, so that the master device obtains from the locally created Eliminate the second address from the second subnet segment, and generate the second entry.

Optionally, the receiving unit 610 is further configured to receive a third synchronization message sent by the master device, where the third synchronization message includes a third address and a third subnet segment to which the third address belongs network segment information;

The device further includes: a recovery unit (not shown in the figure), configured to recover the first subnetwork segment from the third subnetwork segment according to the network segment information of the third subnetwork segment and the third address. Three addresses;

A third judging unit (not shown in the figure), configured to judge whether all addresses included in the third subnet segment have been recycled;

A deletion unit (not shown in the figure), configured to delete the third subnet segment if so;

Wherein, the third address is the address of the third DHCP client.

Optionally, the sending unit (not shown in the figure) is further configured to send a fourth synchronization message to the master device if the fourth address included in the fourth subnet segment has been recycled, and the first The four synchronization messages include the fourth address and network segment information of the fourth subnet segment, so that the master device reclaims the fourth address from the fourth subnet segment, and determines the After all the addresses included in the fourth subnet segment have been recycled, delete the fourth subnet segment;

The deletion unit (not shown in the figure) is also used to delete the fourth subnet segment if all addresses included in the fourth subnet segment have been recovered;

Wherein, the fourth address is the address of the fourth DHCP client.

Optionally, when the master device is downgraded to a new slave device and the slave device is upgraded to a new master device, the method further includes:

The device also includes: an updating unit (not shown in the figure), which is used to update the state of the network segment of the local subnet segment that will be the state of the opposite end to the state of the local end;

The sending unit (not shown in the figure) is further configured to send a fifth synchronization message to the new slave device, and the fifth synchronization message includes all existing subnet segments in the new master device Network segment status and the third entry of all DHCP clients that have been online, the third entry includes the fifth address of each DHCP client, so that the new slave device can , creating a corresponding subnet segment, removing the fifth address from the corresponding subnet segment, and generating the third entry.

Optionally, the device further includes: a recording unit (not shown in the figure), configured to record the network segment status of the first subnet segment as the opposite end status;

The recording unit (not shown in the figure) is further configured to record the network segment state of the second subnetwork segment as the local state.

Therefore, by applying the address allocation device provided by the present application, when the master device receives the first DHCP Discover message sent by the first DHCP client, the master device judges whether there is a first subnet segment available for address allocation locally; if not exists, the master device judges whether the first subnet segment can be divided from the first network segment; if so, the master device creates the first subnet segment and obtains the first address from the first subnet segment; The first DHCP client sends the first DHCPOffer message, the first DHCP Offer message includes the first address; when the master device determines that the first DHCP client uses the first address to go online, the master device sends the first synchronization message to the slave device , the first synchronization message includes the network segment information of the first subnet segment and the first entry of the first DHCP client, and the first entry includes the first address, so that the slave device can determine whether there is a first address belonging to the local If it exists, the slave device will remove the first address from the first subnet segment and generate the first table entry; if it does not exist, the slave device will, according to the network segment information of the first subnet segment, Create the first subnet segment from the second network segment, remove the first address from the first subnet segment, and generate the first entry; wherein, the first address pool is the same as the second address pool, and the first network segment and The second network segment is the same.

In this way, the master and slave devices share the same total network segment, and the subnet segment on the slave device is allocated by the master device, but each device exclusively enjoys the local subnet segment and assigns addresses to the DHCP clients that go online on itself, which realizes The centralized management of addresses avoids conflicts when multiple devices assign addresses at the same time. It solves the problem that in the existing implementation mode of supporting DHCP in the DRNI environment, the master and slave devices cannot realize the centralized management and allocation of addresses, which leads to the problem that the DHCP client cannot go online at any network device in the DRNI environment. Realized reducing the performance pressure of network equipment and increasing the online rate of DHCP clients.

Based on the same inventive concept, the embodiment of the present application also provides a network device, as shown in FIG. 7 , including a processor 710, a transceiver 720, and a machine-readable storage medium 730. The processor 710 executes the machine-executable instructions, and the processor 710 is prompted by the machine-executable instructions to execute the address allocation method provided in the embodiment of the present application. The aforementioned address allocation devices shown in FIG. 5 and FIG. 6 can be realized by using the hardware structure of the network equipment shown in FIG. 7 .

The above-mentioned computer-readable storage medium 730 may include a random access memory (English: Random Access Memory, abbreviated as RAM), and may also include a non-volatile memory (English: Non-volatile Memory, abbreviated: NVM), such as at least one disk memory . Optionally, the computer-readable storage medium 730 may also be at least one storage device located away from the aforementioned processor 710 .

The above-mentioned processor 710 may be a general-purpose processor, including a central processing unit (English: Central Processing Unit, referred to as: CPU), a network processor (English: Network Processor, referred to as: NP), etc.; it may also be a digital signal processor (English: Digital Signal Processor (abbreviation: DSP), application specific integrated circuit (English: Application Specific Integrated Circuit, abbreviation: ASIC), field programmable gate array (English: Field-Programmable Gate Array, abbreviation: FPGA) or other programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

In the embodiment of the present application, the processor 710 reads the machine-executable instructions stored in the machine-readable storage medium 730, and is prompted by the machine-executable instructions to implement the processor 710 itself and call the transceiver 720 to execute the foregoing description of the embodiment of the present application. address allocation method.

In addition, the embodiment of the present application provides a machine-readable storage medium 730. The machine-readable storage medium 730 stores machine-executable instructions. When called and executed by the processor 710, the machine-executable instructions prompt the processor 710 itself and The transceiver 720 is invoked to execute the address allocation method described in the foregoing embodiments of the present application.

For the implementation process of the functions and effects of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method for details, and will not be repeated here.

As for the device embodiment, since it basically corresponds to the method embodiment, for related parts, please refer to the part description of the method embodiment. The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this application. It can be understood and implemented by those skilled in the art without creative effort.

As for the embodiment of the address allocation device and the machine-readable storage medium, since the content of the method involved is basically similar to the foregoing method embodiment, the description is relatively simple. For relevant details, please refer to the part of the description of the method embodiment.

The above is only a preferred embodiment of the application, and is not intended to limit the application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the application should be included in the application. within the scope of protection.

Claims (15)

1. An address allocation method applied to a master device, wherein the master device is in a DRNI mesh network, the DRNI mesh network further includes a slave device, a first address pool is configured in the master device, the first address pool has a corresponding first network segment, a second address pool is configured in the slave device, the second address pool has a corresponding second network segment, and the method includes:

when a first DHCP Discover message sent by a first DHCP client is received, judging whether a first sub-network segment which can be used for distributing addresses exists locally;

if not, judging whether the first sub-network segment can be divided from the first network segment or not;

if so, creating the first sub-network segment, and acquiring a first address from the first sub-network segment;

sending a first DHCP Offer message to the first DHCP client, wherein the first DHCP Offer message comprises the first address;

when the first DHCP client is determined to use the first address to be on-line, sending a first synchronization message to the slave device, wherein the first synchronization message comprises network segment information of the first sub-network segment and a first table entry of the first DHCP client, and the first table entry comprises the first address, so that the slave device judges whether a corresponding first sub-network segment exists locally, if so, the first address is removed from the first sub-network segment, and the first table entry is generated; if the first sub-network segment does not exist, the first sub-network segment is created from the second network segment according to the network segment information of the first sub-network segment, the first address is removed from the first sub-network segment, and the first table entry is generated;

the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment.

2. The method of claim 1, further comprising:

if yes, acquiring a first address from the first sub-network segment;

sending a first DHCP Offer message to the first DHCP client, wherein the first DHCP Offer message comprises the acquired first address;

when the first DHCP client is determined to use the first address to be on-line, sending a first synchronization message to the slave device, wherein the first synchronization message comprises network segment information of the first sub-network segment and a first table entry of the first DHCP client, and the first table entry comprises the first address, so that the slave device judges whether a corresponding first sub-network segment exists locally, if so, the first address is removed from the first sub-network segment, and the first table entry is generated; if the first sub-network segment does not exist, the first sub-network segment is created in the second network segment according to the network segment information of the first sub-network segment, the first address is removed from the first sub-network segment, and the first table entry is generated.

3. The method of claim 1, further comprising:

when a second DHCP Discover message sent by the slave equipment is received, judging whether a second sub-network segment can be divided from the first network segment or not;

if so, creating the second sub-network segment, and acquiring a second address from the second sub-network segment, wherein the second address is an address allocated by the main device for a second DHCP client side which sends the second DHCP Discover message;

sending a second DHCP Offer message to the slave device, the second DHCP Offer message including the second address, so that the slave device creates the second sub-network segment within the second network segment according to the second address;

receiving a second synchronization message sent by the slave device, where the second synchronization message includes network segment information of the second subnet segment and a second entry of the second DHCP client, and the second entry includes the second address;

according to the network segment information of the second sub-network segment and the second address, the second address is removed from the second sub-network segment;

generating the second table entry;

wherein the second sub-network segment does not overlap with other sub-network segments already created within the master device.

4. The method of claim 1, further comprising:

if a third address included in a third subnet section is recovered, sending a third synchronous message to the slave device, wherein the third synchronous message includes the third address and the network segment information of the third subnet section, so that the slave device recovers the third address from the third subnet section, and deletes the third subnet section after determining that all the addresses included in the third subnet section are recovered;

if all the addresses included in the third subnet section are recovered, deleting the third subnet section;

and the third address is the address of a third DHCP client.

5. The method of claim 1, further comprising:

receiving a fourth synchronous message sent by the slave device, wherein the fourth synchronous message comprises a fourth address and network segment information of a fourth sub-network segment to which the fourth address belongs;

recovering the fourth address from the fourth sub-network segment according to the network segment information of the fourth sub-network segment and the fourth address;

judging whether all the addresses included in the fourth subnet section are recycled;

if yes, deleting the fourth sub-network segment;

and the fourth address is the address of a fourth DHCP client.

6. The method of claim 1, wherein when the master device is downgraded to a new slave device and the slave device is upgraded to a new master device, the method further comprises:

receiving a fifth synchronization message sent by the new master device, where the fifth synchronization message includes network segment information of all existing sub-network segments in the new master device and third entries of all online DHCP clients, and the third entries include a fifth address of each DHCP client;

creating a corresponding subnet section in the first network segment according to the network segment information of all the subnet segments and the fifth address, and removing the fifth address from the corresponding subnet section;

and generating the third table entry.

7. The method of any of claims 1, 3 or 6, wherein after the creating the first subnet fragment, the method further comprises:

recording the network segment state of the first sub-network segment as a local state;

after the creating the second subnet segment, the method further comprises:

recording the network segment state of the second sub-network segment as an opposite terminal state;

after the creating the fifth subnet segment, the method further comprises:

and recording the network segment state of the fifth sub-network segment as an opposite terminal state.

8. An address allocation method applied to a slave device, wherein the slave device is in a DRNI networking, the DRNI networking further includes a master device, a first address pool is configured in the master device, the first address pool has a corresponding first network segment, a second address pool is configured in the slave device, the second address pool has a corresponding second network segment, and the method includes:

receiving a first synchronization message sent by the master device, where the first synchronization message includes network segment information of a first sub-network segment created in the first network segment by the master device and a first entry of a first DHCP client, and the first entry includes a first address of the first DHCP client;

judging whether a corresponding first sub-network segment exists locally according to the network segment information of the first sub-network segment;

if the first address exists, the first address is removed from the first sub-network segment, and the first table entry is generated;

if the address does not exist in the second network segment, the first sub-network segment is created from the second network segment, the first address is removed from the first sub-network segment, and the first table entry is generated;

the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment.

9. The method of claim 8, further comprising:

when a second DHCP Discover message sent by a second DHCP client is received, judging whether a second sub-network segment which can be used for distributing addresses exists locally;

if the second DHCP Discover message does not exist, the second DHCP Discover message is sent to the main equipment;

receiving a first DHCP Offer message sent by the main device, wherein the first DHCP Offer message comprises a second address, and the second address is an address allocated to the second DHCP client side by the main device from a second sub-network segment created locally;

creating the second sub-network segment in the second network segment according to the second address;

sending a second DHCP Offer message to the second DHCP client, the second DHCP Offer message including the second address;

and after determining that the second address used by the second DHCP client is on line, sending a second synchronization message to the main device, wherein the second synchronization message comprises network segment information of the second sub-network segment and a second table entry of the second DHCP client, and the second table entry comprises the second address, so that the main device removes the second address from the second sub-network segment which is created locally, and generates the second table entry.

10. The method of claim 8, further comprising:

receiving a third synchronous message sent by the master device, wherein the third synchronous message comprises a third address and network segment information of a third sub-network segment to which the third address belongs;

according to the network segment information of the third sub-network segment and the third address, the third address is recovered from the third sub-network segment;

judging whether all the addresses included in the third subnet section are recycled;

if yes, deleting the third sub-network segment;

and the third address is the address of a third DHCP client.

11. The method of claim 8, further comprising:

if a fourth address included in a fourth subnet section is recovered, sending a fourth synchronous message to the master device, wherein the fourth synchronous message includes the fourth address and the network segment information of the fourth subnet section, so that the master device recovers the fourth address from the fourth subnet section, and deletes the fourth subnet section after determining that all the addresses included in the fourth subnet section are recovered;

if all the addresses included in the fourth subnet section are recovered, deleting the fourth subnet section;

and the fourth address is the address of a fourth DHCP client.

12. The method of claim 8, wherein when the master device is downgraded to a new slave device and the slave device is upgraded to a new master device, the method further comprises:

updating the network segment state of the local sub-network segment in the opposite terminal state into the local terminal state;

and sending a fifth synchronous message to the new slave device, wherein the fifth synchronous message comprises network segment states of all existing sub-network segments in the new master device and third table entries of all online DHCP clients, and the third table entry comprises a fifth address of each DHCP client, so that the new slave device creates a corresponding sub-network segment according to the network segment information of all sub-network segments, removes the fifth address from the corresponding sub-network segment, and generates the third table entry.

13. The method of any of claims 8 or 9, wherein after the creating the first subnet fragment, the method further comprises:

recording the network segment state of the first sub-network segment as an opposite terminal state;

after the creating the second subnet segment, the method further comprises:

and recording the network segment state of the second sub-network segment as the home terminal state.

14. An address allocation apparatus, applied to a master device, the master device being in a DRNI mesh network, the DRNI mesh network further including a slave device, a first address pool being configured in the master device, the first address pool having a corresponding first network segment, a second address pool being configured in the slave device, the second address pool having a corresponding second network segment, the apparatus comprising:

the first judging unit is used for judging whether a first sub-network segment which can be used for distributing addresses exists locally or not when a first DHCP Discover message sent by a first DHCP client side is received;

a second judging unit, configured to judge whether the first sub-network segment can be divided from the first network segment if the first sub-network segment does not exist;

the acquisition unit is used for creating the first sub-network segment and acquiring a first address from the first sub-network segment if the first address is the first address;

a sending unit, configured to send a first DHCP Offer packet to the first DHCP client, where the first DHCP Offer packet includes the first address;

the sending unit is further configured to send a first synchronization packet to the slave device after it is determined that the first DHCP client uses the first address to go online, where the first synchronization packet includes network segment information of the first subnet segment and a first entry of the first DHCP client, and the first entry includes the first address, so that the slave device determines whether a corresponding first subnet segment exists locally, and if so, removes the first address from the first subnet segment, and generates the first entry; if the first sub-network segment does not exist, the first sub-network segment is created from the second network segment according to the network segment information of the first sub-network segment, the first address is removed from the first sub-network segment, and the first table entry is generated;

the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment.

15. An address allocation apparatus, applied to a slave device, the slave device being in a DRNI networking, the DRNI networking further including a master device, a first address pool being configured in the master device, the first address pool having a corresponding first network segment, a second address pool being configured in the slave device, the second address pool having a corresponding second network segment, the apparatus comprising:

a receiving unit, configured to receive a first synchronization packet sent by the master device, where the first synchronization packet includes network segment information of a first subnet segment created in the first network segment by the master device and a first entry of a first DHCP client, and the first entry includes a first address of the first DHCP client;

the first judgment unit is used for judging whether a corresponding first sub-network segment exists locally or not according to the network segment information of the first sub-network segment;

the removing unit is used for removing the first address from the first sub-network segment and generating the first table entry if the first address exists;

a creating unit, configured to create the first sub-network segment from the second network segment if the first sub-network segment does not exist, remove the first address from the first sub-network segment, and generate the first entry;

the first address pool is the same as the second address pool, and the first network segment is the same as the second network segment.

Images