Serial number	IP address	Subnet mask	Port numbering	Port state	VPN name
						1	192.168.1.2	255.255.255.0	1	UP	A
2	192.168.1.2	255.255.255.0	2	UP	A
						3	192.168.1.3	255.255.255.0	3	DOWN	A
4	192.168.1.3	255.255.255.0	4	UP	A
						5	192.168.1.4	255.255.255.0	5	DOWN	A
6	172.16.11.5	255.255.0.0	6	UP	A

The working personnel configure a preset IP address pool on the server, the IP address in the preset IP address pool is the IP address used by the local area network, for example, the value range of the IP address in the preset IP address pool is 192.168.1.0-192.168.16.0.

And comparing the IP address in the preset mapping relation table with the IP address in the preset IP address pool, and if the IP address in the mapping relation table does not exist in the preset IP address pool, defining the IP address in the preset mapping relation table as an abnormal IP address.

In this embodiment, taking the mapping relationship entries in table 1 as an example, the IP addresses in all the mapping relationship entries are extracted, and the IP addresses are sequentially compared with the IP addresses in the preset IP address pool, and since the IP address 172.16.11.5 corresponding to the sequence number 6 is not in the range of 192.168.1.0-192.168.16.0, 172.16.11.5 is defined as an abnormal IP address.

Because the abnormal IP address interferes with the division of the IP address types in the local area network, the mapping relationship entry corresponding to the abnormal IP address needs to be deleted from the preset mapping relationship table, so as to obtain table 2.

TABLE 2

Serial number	IP address	Subnet mask	Port numbering	Port state	VPN name	Type of IP address
							1	192.168.1.2	255.255.255.0	1	UP	A
2	192.168.1.2	255.255.255.0	2	UP	A	Multiplexing IP addresses
							3	192.168.1.3	255.255.255.0	3	DOWN	A	Redundant IP address
4	192.168.1.3	255.255.255.0	4	UP	A
							5	192.168.1.4	255.255.255.0	5	DOWN	A

Step S300, dividing the types of the IP addresses in the preset mapping relation table, wherein the types of the IP addresses comprise multiplexing IP addresses and/or redundant IP addresses.

Comparing every two mapping relation items in a preset mapping relation table; if two mapping relation items exist, wherein the IP address and the VPN information are the same, and the port state is UP, the IP address corresponding to one of the mapping relation items is defined as a multiplexing IP address; and if two mapping relation entries with the same IP address and VPN information and different port states exist, defining the IP address corresponding to the mapping relation entry with the port state of DOWN as a redundant IP address.

Step S300 is illustrated below with reference to the preset mapping table shown in table 2. Mapping relation entries corresponding to sequence number 1 are 192.168.1.2, 255.255.255.0, 1, UP and a, mapping relation entries corresponding to sequence number 2 are 192.168.1.2, 255.255.255.0, 2, UP and a, and since port states in the mapping relation entries corresponding to sequence numbers 1 and 2 are both UP, 192.168.1.2 in the mapping relation entry corresponding to sequence number 2 is defined as a multiplexing IP address.

When a managed device with an IP address of 192.168.1.3 sends information to a managed device with an IP address of 192.168.1.2, since two identical IP addresses of 192.168.1.2 exist in the lan and the corresponding port states are both UP states, 192.168.1.3 does not know which managed device with an IP address of 192.168.1.2 is sent to, and a situation may occur that 192.168.1.3 information does not reach the corresponding managed device, so deleting one of the mapping relation entries and deleting a multiplexing IP address on the management device corresponding to the mapping relation entry, for example deleting the mapping relation entry of 192.168.1.2, 255.255.255.0, 2, UP, and a, and reallocating an IP address to the managed device with the IP address deleted, in this embodiment, reallocating an IP address to the managed device with the IP address deleted is not specifically limited.

In table 2, mapping entries corresponding to sequence number 3 are 192.168.1.3, 255.255.255.0, 3, DOWN, and a, mapping entries corresponding to sequence number 4 are 192.168.1.3, 255.255.255.0, 3, UP, and a, and since the state of the first port corresponding to sequence number 3 is DOWN, the IP address corresponding to sequence number 3 is defined as a redundant IP address. When the port status of the redundant IP address is changed from DOWN to UP, the redundant IP address is changed to a multiplexing IP address, so that the mapping relationship entry corresponding to the redundant IP address in the preset mapping relationship table and the redundant IP address on the corresponding managed device need to be deleted, and the IP address needs to be reallocated to the managed device.

And deleting mapping relation entries corresponding to the abnormal IP address, the multiplexing IP address and the redundant IP address in the table 1 to obtain a table 3.

TABLE 3

Serial number	IP address	Subnet mask	Port numbering	Port state	VPN name	Type of IP address
							1	192.168.1.2	255.255.255.0	2	UP	A
2	192.168.1.3	255.255.255.0	4	UP	A
							3	192.168.1.4	255.255.255.0	5	DOWN	A	Recyclable IP address

And if the duration time of the port state DOWN reaches the preset time, defining the IP address corresponding to the port state DOWN as the recyclable IP address.

In this embodiment, the preset time may be one day, a mapping relationship entry with a port state of DOWN in a preset mapping relationship table is extracted, if the duration of the port state of DOWN reaches one day, the IP address corresponding to the port is defined as a recoverable IP address, and the mapping relationship entry is deleted in the preset mapping relationship table, such as the relationship mapping entry shown in table 3, the mapping relationship entry corresponding to sequence number 3 should be deleted, and the recoverable IP address is deleted on the corresponding managed device, at this time, 192.168.1.4 in the preset IP address pool is defined as an unused IP address, other managed devices are reallocated, and the problem of waste of IP addresses is reduced.

After classifying the IP addresses in the preset mapping relationship table, the IP addresses in the preset IP address pool need to be divided into available IP addresses and unused IP addresses based on the IP addresses in the preset mapping relationship table.

Specifically, as shown in fig. 2, dividing the IP addresses in the preset IP address pool includes the following steps:

step S401, obtaining an IP address in a preset mapping relation table and a subnet mask corresponding to the IP address;

step S402, converting the IP address into a network address based on the IP address and the subnet mask;

in this embodiment, the IP address 192.168.1.255 and the subnet mask 255.255.255.192 are used as an example, and both the IP address and the subnet mask corresponding to the IP address are converted into binary values, where both the IP address and the subnet mask include 32-bit binary numbers. The binary system corresponding to the IP address 192.168.1.255 is 11000000.10101000.00000001.11100001, the binary system corresponding to the subnet mask is 11111111.11111111.11000000, each bit of the IP address corresponds to each bit of the subnet mask one by one, and bit and operation is performed to obtain the network address, wherein the network address corresponding to 192.168.1.255 and 255.255.192 is 11000000.10101000.11000000, and the network address is converted into the decimal system 192.168.1.192.

Step S403, dividing the network segment corresponding to the network address in the preset IP address pool into used network segments, and dividing the rest network segments in the preset IP address pool into unused network segments.

In this embodiment, network addresses corresponding to all IP addresses in the preset mapping table are obtained, whether the same network address exists in the preset mapping table is searched for, if yes, redundant network addresses are deleted, a network segment to which the network address corresponding to the IP address in the preset mapping table belongs is defined as a used network segment, and a remaining network segment in the preset IP address pool is defined as an unused network segment. The IP address in the used network segment is the used IP address in the preset IP address pool; and the IP address in the unused network segment is an unused IP address in a preset IP address pool.

Taking the network addresses in step S401 and step S402 as an example, since the network segments 192.168.1.192 to 192.168.1.255 correspond to 192.168.1.192, 192.168.1.192 to 192.168.1.255 are divided into used IP addresses in the preset IP address pool.

Fig. 3 is a block diagram of an IPaddress management apparatus 500 according to an embodiment of the present application. As shown in fig. 3, the IPaddress management apparatus 500 mainly includes:

an obtainingmodule 501, configured to obtain multiple pieces of connection information of all managed devices, where the connection information includes an IP address of the managed device, a number and a state of a first port corresponding to the IP address, and a number and a state of a second port corresponding to VPN information and VPN information;

a generating and addingmodule 502, configured to generate a mapping relationship entry including an IP address corresponding to a number of a first port, VPN information corresponding to a number of a second port, and a port state if the number of the first port is the same as the number of the second port in the plurality of connection information, and add the mapping relationship entry to a preset mapping relationship table;

thefirst dividing module 503 is configured to divide the types of the IP addresses in the preset mapping relationship table, where the types of the IP addresses include a multiplexing IP address and/or a redundant IP address.

As an optional implementation manner of this embodiment, thefirst dividing module 503 includes:

the comparison submodule is used for comparing every two mapping relation items in the preset mapping relation table;

the first definition sub-module is used for defining the IP address corresponding to one mapping relation item as a multiplexing IP address if two mapping relation items exist, wherein the IP address and the VPN information are the same, and the port state is UP;

and the second definition sub-module is used for defining the IP address corresponding to the mapping relation item with the port state of DOWN as a redundant IP address if two mapping relation items with the same IP address and VPN information and different port states exist.

In this optional embodiment, the IP address management apparatus 400 further includes:

and the first deleting module is used for deleting the mapping relation item to which the multiplexing IP address belongs in the preset mapping relation table and deleting the multiplexing IP address on the managed equipment after the IP address corresponding to one of the mapping relation items is defined as the multiplexing IP address.

and the second deleting module is used for deleting the mapping relation item to which the redundant IP address belongs in the preset mapping relation table and deleting the redundant IP address on the managed equipment after the IP address corresponding to the mapping relation item with the port state of DOWN is defined as the redundant IP address.

As an optional implementation manner of this embodiment, the IP address management apparatus 400 further includes:

the comparison definition module is used for comparing the IP address in the preset mapping relation table with the IP address in the preset IP address pool after the mapping relation item is added into the preset mapping relation table; and if the IP address in the mapping relation table does not exist in the preset IP address pool, defining the IP address in the preset mapping relation table as an abnormal IP address.

And the third deleting module is used for deleting the mapping relation items to which the abnormal IP addresses belong in the preset mapping relation table before the types of the IP addresses in the preset mapping relation table are divided.

the acquisition definition module is used for acquiring port state information of a first port number after dividing the IP addresses in the preset mapping relation table, and the port state information represents the service condition of the ports; and if the duration time of the port state DOWN reaches the preset time, defining the IP address corresponding to the port state DOWN as the recyclable IP address.

a definition deleting module, configured to delete a mapping relationship entry to which a recyclable IP address belongs in a preset mapping relationship table after an IP address corresponding to a DOWN port state is defined as the recyclable IP address, and delete the recyclable IP address from a corresponding managed device;

and the second division module is used for dividing the IP address which is the same as the recyclable IP address in the preset IP address pool into unused IP addresses.

As an optional implementation manner of this embodiment, the mapping relationship entry further includes a subnet mask corresponding to the IP address; the IP address management apparatus 400 further includes:

the obtaining and adding module is used for obtaining the IP address in the preset mapping relation table and the subnet mask corresponding to the IP address after the mapping relation item is added into the preset mapping relation table;

a conversion module for converting the IP address into a network address based on the IP address and the subnet mask;

and the third division module is used for dividing the network segments corresponding to the network addresses in the preset IP address pool into used network segments and dividing the rest network segments in the preset IP address pool into unused network segments.

The functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part. The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium and includes several instructions to enable an electronic device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the IP address management method according to the embodiments of the present application.

Fig. 4 is a block diagram of an IPaddress management device 600 according to an embodiment of the present application. As shown in fig. 4, the IPaddress management apparatus 600 includes amemory 601, aprocessor 602, and acommunication bus 603; the memory,processor 602 are connected by acommunication bus 603. Thememory 601 stores thereon an IP address management method capable of being loaded and executed by theprocessor 602 as provided in the above-described embodiments.

Thememory 601 may be used to store instructions, programs, code, sets of codes, or sets of instructions. Thememory 601 may include a storage program area and a storage data area, wherein the storage program area may store instructions for implementing an operating system, instructions for at least one function, and instructions for implementing the IP address management method provided by the above-described embodiments, and the like; the storage data area may store data and the like involved in the IP address management method provided by the above-described embodiment.

Processor 602 may include one or more processing cores. Theprocessor 602 executes various functions of the present application and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in thememory 601 to invoke data stored in thememory 601. TheProcessor 602 may be at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), a controller, a microcontroller, and a microprocessor. It is understood that the electronic devices for implementing the functions of theprocessor 502 may be other devices, and the embodiments of the present application are not limited in particular.

Communication bus 603 may include a path that conveys information between the aforementioned components. Thecommunication bus 603 may be a PCI (PerIPheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. Thecommunication bus 603 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 4, but that does not indicate only one bus or one type of bus.

Embodiments of the present application provide a computer-readable storage medium storing a computer program that can be loaded by a processor and execute the IP address management method provided in the above embodiments.

In this embodiment, the computer readable storage medium may be a tangible device that retains and stores instructions for use by an instruction execution device. The computer readable storage medium may be, but is not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any combination of the foregoing. In particular, the computer readable storage medium may be a portable computer diskette, a hard disk, a U-disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a podium random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, an optical disk, a magnetic disk, a mechanical coding device, and any combination thereof.

The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.

The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the application referred to in the present application is not limited to the embodiments with a particular combination of the above-mentioned features, but also encompasses other embodiments with any combination of the above-mentioned features or their equivalents without departing from the spirit of the application. For example, the above features may be replaced with (but not limited to) features having similar functions as those described in this application.