WO2021238699A1 - 一种配置网络设备ip地址的方法及相关设备 - Google Patents

一种配置网络设备ip地址的方法及相关设备 Download PDF

Info

Publication number
WO2021238699A1
WO2021238699A1 PCT/CN2021/094077 CN2021094077W WO2021238699A1 WO 2021238699 A1 WO2021238699 A1 WO 2021238699A1 CN 2021094077 W CN2021094077 W CN 2021094077W WO 2021238699 A1 WO2021238699 A1 WO 2021238699A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
identifier
address
interface
network
Prior art date
Application number
PCT/CN2021/094077
Other languages
English (en)
French (fr)
Inventor
李晓晶
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2021238699A1 publication Critical patent/WO2021238699A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5046—Resolving address allocation conflicts; Testing of addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/344—Out-of-band transfers

Definitions

  • the embodiments of the present application relate to the field of circuit technology, and in particular, to a method for configuring an IP address of a network device and related devices.
  • DCN data communication network
  • IP radio access network IP radio access network
  • IPRAN Internet Protocol
  • the embodiment of the present application provides a method for configuring the IP address of a network device and related equipment to solve the current technical problem that the IP address still needs to be manually planned by the network administrator.
  • an embodiment of the present application provides a method for configuring an IP address of a network device, which includes: a first network device obtains a second identity of a second network device; Identification, which determines the Internet Protocol IP address of the interface on the first network device; wherein, the first identification is the device identification of the first network device, and the second identification is the device of the second network device Identification, the first identification and the second identification are different.
  • This application provides a method for configuring the IP address of a network device and the network device. The IP address of the interface of the network device is determined by the first identifier and the second identifier, so that the network device can automatically configure the IP address, which simplifies the manual participation in network planning and reduces Labor costs.
  • the interface on the first network device is an interface on a link between the first network device and the second network device.
  • the method for configuring the IP address of a network device provided by the embodiment of the application can automatically configure the IP address of the interface on the first network device and the IP address of the interface on the second network device, thereby automatically configuring the first network device and the second network device. Configure the link, the first network device and the second network device can transmit data according to the IP addresses on their respective interfaces.
  • the first network device determines the Internet Protocol IP address on the first network device according to the first identifier and the second identifier, including: The first network device determines the IP address on the first network device according to the first identifier, the second identifier, and a first preset value.
  • the first network device determines the IP address, it can intervene in the determination process through the first preset value, and realize the control and operation of the process of determining the IP address by modifying the first preset value, and finally meet the requirements Or an IP address that complies with the protocol.
  • the The method further includes: the first network device sends an address resolution protocol ARP message to the second network device according to the IP address of the interface of the first network device, so that the second network device is based on the ARP message and the subnet
  • the mask generates the IP address of the interface on the second network device.
  • the first network device can also send an ARP message to the second network device based on the IP address of the interface of the first network device that has been generated, so that the second network device can generate the second network based on the ARP message and the subnet mask.
  • the IP address of the device's interface can avoid IP conflicts and realize the automatic configuration of the IP addresses of the links between the two network devices.
  • the first network device determines the IP address on the first network device according to the first identifier, the second identifier, and a first preset value , Including: the first network device determines the target identifier according to the first identifier and the second identifier; the first network device determines the first network device according to the target identifier and the first preset value The IP address on the network device.
  • the first network device may determine the target identifier according to the first identifier and the second identifier.
  • the first network device may select one of the first identifier and the second identifier that meets a preset condition as the target identifier.
  • Choosing one of the two identifiers as the basis for determining the IP address can reduce the number of identifiers used to determine the IP address, simplify the process of determining the IP address, and increase the rate of determining the IP address.
  • the first network device selects an identifier to determine the IP address, and the first identifier and the second identifier are different. Therefore, when multiple network devices configure links, IP conflicts can be prevented.
  • determining the target identifier by the first network device according to the first identifier and the second identifier includes: comparing the first identifier with the second identifier; If the first identification is numerically smaller than the second identification, the first identification is selected as the target identification; if the first identification is numerically greater than the second identification, the second identification is selected as the target Logo.
  • determining the target identifier by the first network device according to the first identifier and the second identifier includes: comparing the first identifier with the second identifier; If the first identifier is numerically greater than the second identifier, the first identifier is selected as the target identifier; if the first identifier is numerically smaller than the second identifier, the second identifier is selected as the target Logo.
  • the first identifier is a preset IP address of the first network device
  • the second identifier is a preset IP address of the second network device address.
  • the first network device determines the IP address of the interface according to the preset IP address. Since the preset IP address and the IP address of the interface are similar in format, a simpler algorithm can be used to determine the IP address of the interface , Can improve the efficiency of determining the IP address.
  • the first network device determining the IP address of the interface on the first network device according to the target identifier and the first preset value includes: The first network device uses the first 24 bits of the target identifier as the first 24 bits of the IP address of the interface of the first network device, and uses the first preset value as the IP address of the interface of the first network device. The last 8 bits of the address constitute the IP address of the interface of the first network device.
  • the method further includes: the first network device determining a loopback address according to a second preset value and the first identifier.
  • the method further includes: obtaining a label distribution protocol In the configuration of the LDP tunnel, the loopback address is used as the identification number ID of the network device in the configuration; and the LDP tunnel is established according to the configuration.
  • the method further includes: obtaining a traffic engineering TE Tunnel configuration.
  • the loopback address is used as the source address of the TE tunnel
  • the loopback address of the second network device is used as the target address of the TE tunnel
  • the configuration is involved in establishing the TE tunnel according to the configuration. TE tunnel.
  • an embodiment of the present application provides a first network device, including: an obtaining module, configured to obtain a second identifier of the second network device; and a processing module, configured to determine the The Internet Protocol IP address of the interface on the first network device; wherein the first identifier is the device identifier of the first network device, the second identifier is the device identifier of the second network device, and the first identifier is the device identifier of the second network device. The first identifier is different from the second identifier.
  • the interface on the first network device is an interface on the link between the first network device and the second network device.
  • the processing module is configured to: determine the interface on the first network device according to the first identifier, the second identifier, and a first preset value IP address.
  • the processing module is further configured to: send an address resolution protocol ARP message to the second network device according to the IP address of the interface of the first network device, so that all The second network device generates the IP address of the interface on the second network device according to the ARP message and the subnet mask.
  • the processing module is configured to: determine a target identifier according to the first identifier and the second identifier; according to the target identifier and the first preset value To determine the IP address on the first network device.
  • the processing module is configured to: compare the first identifier with the second identifier; if the first identifier is numerically smaller than the second identifier, Then the first identifier is selected as the target identifier; if the first identifier is larger in value than the second identifier, the second identifier is selected as the target identifier.
  • the processing module is configured to: compare the first identifier with the second identifier; if the first identifier is larger in value than the second identifier, The first identifier is selected as the target identifier; if the first identifier is numerically smaller than the second identifier, the second identifier is selected as the target identifier.
  • the first identifier is a preset IP address of the first network device
  • the second identifier is a preset IP address of the second network device address.
  • the processing module is configured to: use the first 24 bits of the target identifier as the first 24 bits of the IP address of the interface of the first network device, and use the The first preset value is the last 8 bits of the IP address of the interface of the first network device, which constitutes the IP address of the interface of the first network device.
  • the processing module is further configured to: determine a loopback address based on a second preset value and the first identifier.
  • the processing module is further configured to: obtain the configuration of the label distribution protocol LDP tunnel, in which the loopback address is used as the identification number ID of the network device; The configuration participates in establishing the LDP tunnel.
  • the processing module is further configured to: obtain the configuration of a traffic engineering TE tunnel, in which the loopback address is used as the source address of the TE tunnel, and the The loopback address of the second network device is the target address of the TE tunnel; it participates in establishing the TE tunnel according to the configuration.
  • an embodiment of the present application provides a network device, including one or more central processing units, a memory, a wired or wireless network interface, and a power supply; the memory is a short-term storage memory or a persistent storage memory; the central processing unit It is configured to communicate with the memory, and execute the instruction operation in the memory on the network device, so that the network device executes the method according to the first aspect.
  • an embodiment of the present application provides a chip, and the chip is used in the method of the first aspect.
  • an embodiment of the present application provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, which when run on a computer, causes the computer to execute the method of the first aspect.
  • the embodiments of the present application provide a method for configuring an IP address of a network device and related devices.
  • the first network device determines the interface of the first network device through its own device identifier and the acquired device identifier of the second network device.
  • IP address which realizes automatic configuration of IP address, simplifies manual participation in network planning, and reduces labor costs.
  • the first network device can also send an ARP message to the second network device according to the generated IP address, so that the second network device can generate the IP address of the interface of the second network device according to the ARP message and the subnet mask, thus producing
  • the two IP addresses can avoid IP conflicts, and realize the automatic configuration of the IP address of the link between the two network devices.
  • Figure 1 is a schematic diagram of an IP wireless access network in an embodiment of the application
  • FIG. 2 is a flowchart of a method for configuring an IP address of a network device in an embodiment of the application
  • FIG. 3 is a schematic diagram of an application scenario of an embodiment of the application.
  • Figure 4 is a schematic diagram of network device interaction in an embodiment of this application.
  • FIG. 5 is a schematic diagram of module division of a network device in an embodiment of the application.
  • Fig. 6 is a schematic diagram of a network device provided by an embodiment of the application.
  • the embodiment of the present application provides a method for configuring the IP address of a network device and related equipment to solve the current technical problem that the IP link address still needs to be manually planned by the network administrator.
  • words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner.
  • the data communication network refers to providing a transmission path for management information and control information communication within the transmission plane, the control plane, and the management plane, and between the three.
  • DCN is a network that supports the functions of the first layer (physical layer), the second layer (data link layer) and the third layer (network layer) in the seven-layer protocol stack of the network. It mainly carries management information and distributed signaling messages. .
  • the public data communication network there are three forms of data transmission services: circuit switching, packet switching and leased circuit.
  • FIG. 1 is a schematic diagram of an IP wireless access network in an embodiment of the application.
  • IP Internet protocol
  • loopback address the local loopback address
  • link local addresses (linklocal addresses) of IPv6 can be used to plan link IP addresses, eliminating the need for link IP address planning and configuration, but there is currently no technology that can automatically return local loopback addresses. Configuration. There is currently no technology in IPv4 networks capable of automatic address configuration.
  • IPv4 address planning still requires manual planning.
  • some network administrators make manual planning according to certain rules. Although the scenario of address duplication can be avoided, automatic deployment is still not possible.
  • the embodiment of the present application provides a method for configuring the IP address of a network device to solve the above-mentioned technical problem that the IP address cannot be automatically configured, especially the problem that the IPv4 address cannot be automatically configured.
  • Fig. 2 is a flowchart of a method for configuring an IP address of a network device in an embodiment of the application. The method includes the following steps:
  • the network device 1 obtains the device identification of the network device 2.
  • the network device may refer to a network element in the DCN, and therefore may also be referred to as a network element (NE) device.
  • the network device may be a router, a switch, or an access point, a base station, etc., which is not limited in the embodiment of the present application.
  • the embodiments of this application are intended to illustrate the automatic configuration of IP addresses between network devices.
  • two network devices namely network device 1 and network device 2 are used as examples for description. Other network devices can be implemented with reference to the embodiments of this application. The application examples will not be repeated.
  • the device identification may be NE_IP.
  • NE_IP is the IP address of the DCN that comes with the network device. It is a unique identifier for the entire network. It is generally the identifier that comes with the network device when it leaves the factory (also known as the preset device identifier). It can be stored inside the network device. In reading the storage medium, the network device can read the identification at any time.
  • the NE_IP can be understood as an IP address in a special format, which can be pre-configured by the network manager when the network device is produced, or it can be configured and saved by the network manager after the network device leaves the factory.
  • NE_IP of the network device in other ways, which is not limited in the embodiment of the present application.
  • the NE_IP can guarantee that it will not be repeated for a long period of time.
  • NE_IP may be a 32-bit address.
  • the first 8 bits of the NE_IP can be set to a preset value. Exemplarily, the first 8 bits of a certain NE_IP are "10.".
  • the device identifier may also be another type of identifier, such as the serial number of the network device, or the media access control (MAC) address of the network device.
  • MAC media access control
  • it may also be other types of identifiers, which are not limited in the embodiment of the present application.
  • the embodiment of this application is described with NE_IP, and other types of device identifiers can be implemented with reference to the embodiment of this application, and will not be repeated.
  • the network device can convert the MAC address into a format similar to NE_IP through a preset algorithm, so as to use the converted identifier according to the format.
  • a special algorithm can also be used to negotiate and determine the IP address of the interface of the network device based on the identifiers of the two network devices, which is not limited in the embodiment of the present application.
  • the network device 1 can trigger step 101 according to the automatic configuration IP address command issued by the network management, and in actual applications, step 101 can also be triggered in other ways, which is not limited in the embodiment of the present application.
  • the length of the subnet mask is also issued, for example, the length of the subnet mask is 8 bits, the length of the subnet mask is 4 bits, and so on.
  • the subnet mask can be used to cooperate with the ARP message to generate the IP address of the interface of the network device.
  • the network device 1 may obtain the NE_IP of the network device 2 through the link layer discovery protocol (LLDP). Specifically, the network device 1 can obtain the NE_IP of the network device 2 when the LLDP obtains the neighbor detailed information. Exemplarily, the network device 1 may obtain the NE_IP of the network device 2 according to the management IP (a parameter) in the LLDP neighbor.
  • LLDP link layer discovery protocol
  • LLDP provides a standard link layer discovery method, which can organize the main capabilities, management address, device identification, interface identification and other information of the local device into different TLVs (Type/Length/Value, Type/Length) /Value), and encapsulated in the link layer discovery protocol data unit (link layer discovery protocol data unit, LLDPDU) and published to the neighbors directly connected to them. After the neighbors receive the information, they will use the standard management information database (management information). Base, MIB) are stored in the form for the network management system to query and judge the communication status of the link. Network devices can advertise their own status to other devices by sending LLDP in the local network. Therefore, LLDP is a protocol that enables devices in the network to discover each other, announce status, and exchange information.
  • the network device 1 can determine the IP address of the interface of the network device 1 according to the device identification of the network device 1 and the device identification of the network device 2.
  • the network device 1 may determine the IP address of the interface of the network device 1 according to the device identification of the network device 1 and the device identification of the network device 2. Different from the NE_IP or loopback address, in the embodiment of the present application, the IP address of the interface of the network device may also be referred to as the interface IP address or the link IP address.
  • the format of the device identification is an IP address format, such as NE_IP
  • the network device 1 can determine the interface of the network device 1 according to the device identification of the network device 1 and the device identification of the network device 2 according to a preset algorithm IP address (for example, select one of the device identifiers as the IP address of the interface of the network device 1).
  • IP address for example, select one of the device identifiers as the IP address of the interface of the network device 1).
  • the embodiment of the present application does not limit any of the foregoing preset algorithms. Taking NE_IP as an example, after network device 1 obtains the NE_IP of network device 1 and the NE_IP of network device 2, it can compare the NE_IP of the two and select the smaller NE_IP as the IP address of the interface of network device 1.
  • the comparison method of NE_IP may be to compare the corresponding numerical value. If the value of NE_IP is smaller than the value of another NE_IP, it can be determined that the NE_IP with the smaller value is the smaller NE_IP. Exemplarily, if one NE_IP is 170.0.0.1 and the other NE_IP is 170.0.0.2, then the NE_IP of 170.0.0.1 is the smaller NE_IP. In other embodiments, after the network device 1 obtains the NE_IP of the network device 1 and the NE_IP of the network device 2, it can compare the NE_IP of the two and select the larger NE_IP as the IP address of the interface of the network device 1.
  • the network device 1 may not compare the size of NE_IP, but use other methods or algorithms to select one of the NE_IPs, which is not limited in the embodiment of the present application. In actual applications, the network device 1 may not select one of the NE_IPs, but generate a new NE_IP based on the NE_IPs of the two, which is not limited in the embodiment of the present application.
  • the NE_IP of network device 1 and the NE_IP of network device 2 will not be the same. However, if the NE_IP of the network device 1 and the NE_IP of the network device 2 are the same, the network device 1 can select any one of the NE_IPs.
  • the network device 1 may determine the IP address of the interface of the network device 1 according to the device identification of the network device 1, the device identification of the network device 2, and the preset value according to a preset algorithm. Specifically, the network device 1 may select one of the device identification of the network device 1 and the device identification of the network device 2 as the target identification, and then determine the IP address of the interface of the network device 1 according to the target identification and the preset value.
  • the method for selecting one of the two device identifiers is similar to the foregoing embodiment, and will not be repeated here.
  • network device 1 After network device 1 determines the smaller NE_IP as the target identifier, it can use the first 24 bits of NE_IP as the first 24 bits of the IP address of the interface, and use the preset value as the last 8 bits of the IP address of the interface.
  • the IP address that forms the interface Exemplarily, if the smaller NE_IP is 170.0.0.1 and the preset value is 254, the network device can use the first 24 bits of the smaller NE_IP as the first 24 bits of the IP address of the interface, and 254 is the IP address of the interface The last 8 bits of the interface IP address is 170.0.0.254.
  • network device 1 can compare the NE_IP of network device 1 with the NE_IP of network device 2, and then select the first 24 bits of the larger NE_IP as the first 24 bits of the IP address of the interface, and use the preset value as The last 8 bits of the IP address of the interface form the IP address of the interface. Exemplarily, if one NE_IP is 170.0.0.1 and the other NE_IP is 170.0.0.2, the NE_IP of 170.0.0.2 is the larger NE_IP.
  • the network device 1 can use the first 24 bits of the larger NE_IP as the first 24 bits of the IP address of the interface, and if 254 is the last 8 bits of the IP address of the interface, the IP address of the interface is 170.0.0.254.
  • network device 1 can compare the NE_IP of network device 1 with the NE_IP of network device 2, and then select the last 24 bits of the smaller NE_IP as the last 24 bits of the IP address of the interface, and use the preset value as The first 8 bits of the IP address of the interface form the IP address of the interface. Exemplarily, if one NE_IP is 170.0.0.1 and the other NE_IP is 170.0.0.2, then the NE_IP of 170.0.0.1 is the smaller NE_IP.
  • the network device 1 can use the last 24 bits of the smaller NE_IP as the last 24 bits of the IP address of the interface, and if 254 is the first 8 bits of the IP address of the interface, the IP address of the interface is 254.0.0.1.
  • the specific method of configuring the IP address of the interface in the network device 1 can also be set according to actual needs.
  • the first 16 bits of the target identifier are selected as the first 16 bits of the IP address of the interface, and the preset value is the IP address of the interface.
  • the last 16 bits of the address, etc., are not limited in this embodiment of the application.
  • the format of the device identification is a format other than an IP address
  • the network device 1 can convert the format of the device identification into an IP address format through a preset algorithm, and then determine the IP address of the interface of the network device 1.
  • the device identifier is a MAC address, where the device identifier of network device 1 is 08:00:20:0A:8C:6D, and the device identifier of network device 2 is 04:00:40:0B:8D:6E, then The network device 1 can determine the IP address of the interface of the network device 1 based on the above two MAC addresses through a preset special algorithm, or the network device 1 can convert the above two MAC addresses into an IP address format through a preset algorithm, for example Convert 08:00: 20: 0A: 8C: 6D to 8.0.20.10, and convert 04:00: 40: 0B: 8D: 6E to 4.0.4.11, and then according to the above-mentioned embodiment, according to 8.0.
  • the format of the device identification is a format other than an IP address
  • the network device 1 can directly determine the interface of the network device 1 based on the device identification of the network device 1 and the device identification of the network device 2 through a preset special algorithm IP address.
  • the embodiment of the present application does not limit any of the foregoing preset algorithms.
  • the network device 1 sends an ARP message to the network device 2, so that the network device 2 generates the IP address of the interface of the network device 2 in combination with the mask after receiving the ARP message.
  • the IP address of the interface of the network device 1 may be referred to as the local interface IP, and the IP address of the interface of the network device 2 may be referred to as the peer interface IP.
  • the free ARP message sent by network device 1 carries the IP address of the interface of network device 1.
  • the gratuitous ARP message After network device 2 receives the gratuitous ARP message, it can be combined with the interface of network device 1 carried in the gratuitous ARP message
  • the IP address and the configured mask generate the IP address of the interface of network device 2. Since network device 2 can obtain the IP address of the interface of network device 1 from ARP, the IP address of the interface of network device 2 generated by network device 2 will not conflict with the IP address of the interface of network device 1, thereby preventing IP conflicts .
  • a mask can also be called a subnet mask, which is a way to indicate which bits of an IP address identify the subnet where the host is located, and which bits identify the bits of the host. Mask.
  • IP address of the interface of network device 2 When the IP address of the interface of network device 2 is established, the IP address of the interface of network device 1 and the IP address of the interface of network device 2 are both known, and then network device 1 and network device 2 can pass through the two interfaces. IP address to send and receive data.
  • IGP interior gateway protocol
  • the network management server issues the configuration of the LDP tunnel to the network device 1 and the network device 2 according to the respective loopback addresses of the network device 1 and the network device 2, so that the network device 1 and the network device 2 can establish the LDP tunnel.
  • the network management server manages network device 1 and network device 2. Therefore, the network management server can deliver the configuration of the LDP tunnel to the network device 1 and the network device 2.
  • the configuration of the LDP tunnel includes the attributes of multiprotocol label switching (MPLS) and label distribution protocol (LDP) under the interface.
  • MPLS multiprotocol label switching
  • LDP label distribution protocol
  • the network management server can designate the MPLS LSR-ID as the loopback address (loopback address) of the network device after NE_IP conversion.
  • LSR-ID refers to the identity document (ID) of a router (lable switching router, LSR) that uses label switching technology to forward messages.
  • the loopback address is the address corresponding to the loopback interface.
  • the Loopback interface is a virtual interface, which is a pure software virtual interface. Any network data message sent to the loopback interface will be considered as sent to the device itself. Therefore, loopback interface and loopback address are widely used.
  • the network device may determine the loopback address according to the preset value and the device identifier. For example, in some embodiments, the network device can use NE_IP to convert to a loopback address.
  • the network device 1 may configure the preset value A as the first 8 bits of the loopback address, and configure the last 24 bits of the NE_IP as the last 24 bits of the loopback address, that is, the loopback address is A.NE_IP. For example, if the default value A is 127 and the last 24 bits of NE_IP are 0.0.1, the loopback address is 127.0.0.1.
  • Other network devices determine the loopback address in the same way, which is not repeated in the embodiment of this application.
  • network devices can also use other algorithms to determine the loopback address, such as converting a device identifier in a non-IP address format to a device identifier in IP address format, and then determining the loopback address based on the preset value and the device identifier. This application is implemented I won’t repeat this example.
  • the network management server specifies the LSR-ID and delivers the conventional configuration
  • the end-to-end LDP LSP has been deployed, and the network management server has a complete topology relationship. If the business requires an iterative LDP tunnel, the network administrator can deploy the corresponding LDP tunnel through the network management server.
  • the network management server designates the loopback address of network device 2 as the target IP of the TE tunnel, and designates the loopback address of network device 1 as the source address of the TE tunnel, and delivers the specified configuration to network device 1 and network device 2 to establish TE tunnel.
  • step 104 there is no sequence relationship between step 104 and step 105.
  • Step 105 may be executed first, and then step 105 may be executed, or step 105 may be executed first, and then step 104 may be executed.
  • step 104 and step 105 may be performed at the same time, which is not limited in the embodiment of the present application.
  • only step 104 or only step 105 may be performed.
  • the traffic engineering (traffic engineering, TE) tunnel monitors the network process and the load of the network unit in real time, dynamically adjusts the traffic management parameters, routing parameters, and resource constraint parameters, etc., so that the network operation state can be transferred to the ideal state. Optimize the use of network resources and avoid congestion caused by unbalanced load.
  • the network management server can designate the loopback address of network device 2 as the target IP of the TE tunnel, and designate the loopback address of network device 1 as the source address of the TE tunnel, form the corresponding configuration, and send it to network device 1 and Network equipment 2.
  • the network administrator can add segment-related configuration to the customized template through the network management server to implement the corresponding tunnel service.
  • segment routing best effort SRBE
  • the network administrator can issue the BGP neighbor configuration through the network management server and the loopback address on the network device to establish related connections.
  • BGP border gateway protocol
  • the network management server can configure various tunnels through the aforementioned loopback address to implement management of each network device. After a tunnel is established between the network devices, data can be forwarded through the IP address of the interface established in the aforementioned steps. Specifically, the network management server can specify the configuration of various tunnels according to the loopback address. For example, the above-mentioned MPLS LSR-ID is specified as the loopback address of the network device, and then these configurations are delivered to the network device, so that the network device establishes a correspondence based on these configurations Tunnels to realize automatic deployment of tunnels.
  • Fig. 3 is a schematic diagram of an application scenario according to an embodiment of the application.
  • the network devices connected from the base station side are the cell site gate (CSG), the access service gateway (ASG), the radio service gateway (RSG), and the wireless service gateway.
  • Network controller radio network controller, RNC.
  • the system also includes a DCN network and a network monitoring service (network monitoring service).
  • every two network devices can generate the IP address of the interface in the manner as in the foregoing embodiment to establish a link.
  • the base station side gateway and the access service gateway 1 may generate the IP addresses of the interfaces in the manner as in the above-mentioned embodiment, and establish a link.
  • the access service gateway 1 and the access service gateway 2 can also generate the IP addresses of the interfaces in the manner as in the foregoing embodiment to establish a link. This is not repeated in the embodiment of the application.
  • the wireless service gateway may report each link information to a data communication network, and the data communication network is connected to a network monitoring server. Managers can monitor the link status and communication status of each network device in real time through the network monitoring server. In the event of a network failure, the management personnel can learn the specific network device where the network failure occurred in real time through the network monitoring server, and then repair the network failure.
  • FIG 4 is a schematic diagram of network device interaction in an embodiment of this application. It can be seen that both network device 1 and network device 2 can use their NE_IP to generate loopback addresses, and respectively generate their own loopback addresses (ie, loopback1 address and loopback2 address).
  • network device 1 can use the last 24 bits of NE_IP1 (NE_IP of network device 1 is NE_IP1, and NE_IP of network device 2 is NE_IP2) as the last 24 bits of loopback1 address, and the front of loopback1 address 8 bits are set to the preset value A, thereby generating the loopback1 address as A.NE_IP1.
  • the network device 1 may use the first 24 bits of NE_IP1 as the first 24 bits of the loopback1 address, and set the last 8 bits of the loopback1 address to the preset value B, thereby generating the loopback1 address as NE_IP1.B.
  • the network device 1 may also use other similar methods to generate the loopback1 address, which is not limited in the embodiment of the present application.
  • the way the network device 2 generates the loopback2 address is similar, and the preset value used can be the same as that of the network device 1, for example, the preset value is A, or it can be different from the network device 1, for example, the preset value is C, which will not be repeated here.
  • the network device 1 and the network device 2 can generate the IP addresses of their respective interfaces according to the NE_IP negotiation between the two parties.
  • the specific steps and methods are similar to the foregoing embodiment, and will not be repeated here.
  • network device 1 and network device 2 After network device 1 and network device 2 generate loopback addresses and negotiate to establish a link, they can establish LDP tunnels, TE tunnels, or SRBE tunnels based on the loopback addresses, and forward corresponding data based on the IP address of the interface. In practical applications, other similar tunnels can also be established, which is not limited in the embodiment of the present application.
  • the IP address of the interface can be established by referring to the steps and methods of the foregoing embodiment to realize the automatic configuration of the IP of the network device 1 and the network device 3.
  • Fig. 5 is a schematic diagram of module division of a network device in an embodiment of the application.
  • the network device 500 includes: an acquiring module 501, configured to acquire a second identifier of a second network device; and a processing module 502, configured to determine the status of the interface on the first network device according to the first identifier and the second identifier Internet Protocol IP address; wherein the first identifier is the device identifier of the first network device, the second identifier is the device identifier of the second network device, the first identifier and the second identifier different.
  • the obtaining module 501 may perform step 101 performed by the network device 1 in the embodiment shown in FIG. 2 and the operation of the network device in the embodiment shown in FIG. 4 to obtain the NE_IP of the opposite end.
  • the processing module 502 can perform the operations performed by the network device 1 in the embodiment shown in FIG. 2 or FIG. 4 (except the operations performed by the obtaining module described above), and the details are not repeated here.
  • Fig. 6 is a schematic diagram of a network device provided by an embodiment of the application.
  • the network device may include one or more central processing units 601, a memory 602, a wired or wireless network interface 603, and a power supply 604.
  • the memory 602 may be short-term storage or persistent storage. Furthermore, the central processing unit 601 may be configured to communicate with the memory 602, execute a series of instruction operations in the memory 602 on the network device, and cooperate with the network interface 603, so that the network device in FIG. 6 can execute the aforementioned FIG. 2 Or the operation performed by the network device 1 in the embodiment shown in FIG. 4, which will not be described in detail here.
  • the wired or wireless network interface 603 can be used to send and receive ARP packets, or obtain the configuration of an LDP or TE tunnel, or send and receive corresponding packets while participating in the establishment of an LDP or TE tunnel. It should be understood that the wired or wireless network interface 603 includes at least one network interface.
  • the specific functional module division in the central processing unit 601 may be similar to the functional module division of the acquisition module and the processing module described in FIG. 5, and will not be repeated here.
  • the embodiment of the present application also provides a chip, which can execute the method executed by the network device 1 in the foregoing embodiment.
  • the embodiment of the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, which when run on a computer, causes the computer to execute the method executed by the network device 1 in the foregoing embodiment.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .

Abstract

本申请提供一种配置网络设备IP地址的方法及相关设备，该方法中，第一网络设备通过自身的设备标识和获取到的第二网络设备的设备标识确定第一网络设备的接口的IP地址，从而实现自动配置IP地址，简化了人工参与网络规划，减少了人力成本。此外，第一网络设备还可以根据生成好的IP地址发送ARP消息至第二网络设备，使得第二网络设备能够根据该ARP消息和子网掩码生成第二网络设备的接口的IP地址，这样生成的两个IP地址能够避免IP冲突，实现了两个网络设备之间链路的IP地址自动配置。

Description

一种配置网络设备IP地址的方法及相关设备
本申请要求于2020年5月25日提交的、中国申请号为202010451992.5、发明名称为“一种配置网络设备IP地址的方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及电路技术领域，尤其涉及一种配置网络设备IP地址的方法及相关设备。
背景技术
随着通信技术的发展，数据通信网络(data communication network，DCN)的技术愈发成熟。
然而，在IP无线接入网络(IP radio access network，IPRAN)中，网络设备之间链路的网际互联协议(internet protocol，IP)地址仍需要网络管理员手工规划。为了防止网络中IP地址存在冲突，现网网络部署时需要用一张非常大的表格进行地址维护，每次网络部署时需要去申请空余地址，并且当需要查找一个IP地址时也很费工作量。
发明内容
本申请实施例提供了一种配置网络设备IP地址的方法及相关设备，以解决目前IP地址仍需要网络管理员手工规划的技术问题。
第一方面，本申请实施例提供一种配置网络设备IP地址的方法，包括：第一网络设备获取第二网络设备的第二标识；所述第一网络设备根据第一标识和所述第二标识，确定所述第一网络设备上的接口的互联网协议IP地址；其中，所述第一标识为所述第一网络设备的设备标识，所述第二标识为所述第二网络设备的设备标识，所述第一标识和所述第二标识不同。本申请提供一种配置网络设备IP地址的方法及网络设备，通过第一标识和第二标识确定网络设备的接口的IP地址，从而实现网络设备自动配置IP地址，简化了人工参与网络规划，减少人力成本。
结合第一方面，在一种可能的实现方式中，所述第一网络设备上的接口，是所述第一网络设备和所述第二网络设备间的链路上的接口。本申请实施例提供的配置网络设备IP地址的方法可以自动配置第一网络设备上的接口的IP地址以及第二网络设备上的接口的IP地址，从而为第一网络设备和第二网络设备自动配置链路，第一网络设备和第二网络设备可以根据各自接口上的IP地址传输数据。
结合第一方面，在一种可能的实现方式中，所述第一网络设备根据所述第一标识和所述第二标识，确定所述第一网络设备上的互联网协议IP地址，包括：所述第一网络设备根据所述第一标识，所述第二标识和第一预设值，确定所述第一网络设备上的IP地址。本申请中，第一网络设备在确定IP地址时，可以通过第一预设值对确定过程进行干预，通过修改第一预设值实现对确定IP地址的过程进行控制和操作，最终得到符合要求或符合协议的IP地址。
结合第一方面，在一种可能的实现方式中，所述第一网络设备根据所述第一标识和所 述第二标识，确定所述第一网络设备上的互联网协议IP地址之后，所述方法还包括：所述第一网络设备根据所述第一网络设备的接口的IP地址向所述第二网络设备发送地址解析协议ARP消息，使得所述第二网络设备根据所述ARP消息和子网掩码生成所述第二网络设备上的接口的IP地址。在本申请中，第一网络设备还可以根据生成好第一网络设备的接口的IP地址发送ARP消息至第二网络设备，使得第二网络设备能够根据该ARP消息和子网掩码生成第二网络设备的接口的IP地址。通过这种方式生成的两个IP地址能够避免IP冲突，实现两个网络设备之间链路的IP地址自动配置。
结合第一方面，在一种可能的实现方式中，所述第一网络设备根据所述第一标识，所述第二标识和第一预设值，确定所述第一网络设备上的IP地址，包括：所述第一网络设备根据所述第一标识与所述第二标识确定目标标识；所述第一网络设备根据所述目标标识和所述第一预设值，确定所述第一网络设备上的IP地址。本申请中，第一网络设备可以根据第一标识和第二标识确定目标标识。优选地，第一网络设备可以从第一标识和第二标识中选择符合预设条件的一个作为目标标识。从两个标识中选择一个作为确定IP地址的依据，能够减少确定IP地址所用标识的数量，使得确定IP地址的过程更简化，提高IP地址的确定速率。第一网络设备择一标识来确定IP地址，并且第一标识和第二标识不同，因而当多个网络设备配置链路时，能够防止IP冲突。
结合第一方面，在一种可能的实现方式中，所述第一网络设备根据第一标识与所述第二标识确定目标标识包括：比较所述第一标识与所述第二标识；若所述第一标识比所述第二标识数值上小，则选择所述第一标识作为目标标识；若所述第一标识比所述第二标识数值上大，则选择所述第二标识作为目标标识。
结合第一方面，在一种可能的实现方式中，所述第一网络设备根据第一标识与所述第二标识确定目标标识包括：比较所述第一标识与所述第二标识；若所述第一标识比所述第二标识数值上大，则选择所述第一标识作为目标标识；若所述第一标识比所述第二标识数值上小，则选择所述第二标识作为目标标识。
结合第一方面，在一种可能的实现方式中，所述第一标识为所述第一网络设备的预置的IP地址，所述第二标识为所述第二网络设备的预置的IP地址。本申请中，第一网络设备根据预置的IP地址来确定接口的IP地址，由于预置的IP地址和接口的IP地址在格式上类似，因此确定接口的IP地址时能够采用更加简单的算法，能够提高确定IP地址的效率。
结合第一方面，在一种可能的实现方式中，所述第一网络设备根据所述目标标识和所述第一预设值，确定所述第一网络设备上的接口的IP地址包括：所述第一网络设备以所述目标标识的前24位为所述第一网络设备的接口的IP地址的前24位，以所述第一预设值为所述第一网络设备的接口的IP地址的后8位，组成所述第一网络设备的接口的IP地址。
结合第一方面，在一种可能的实现方式中，所述方法还包括：所述第一网络设备根据第二预设值和所述第一标识，确定环回loopback地址。
结合第一方面，在一种可能的实现方式中，所述第一网络设备根据第二预设值和所述第一标识，确定环回loopback地址之后，所述方法还包括：获取标签分发协议LDP隧道的 配置，所述配置中以所述loopback地址为网络设备的身份标识号ID；根据所述配置参与建立所述LDP隧道。
结合第一方面，在一种可能的实现方式中，所述第一网络设备根据第二预设值和所述第一标识，确定环回loopback地址之后，所述方法还包括：获取流量工程TE隧道的配置，所述配置中以所述loopback地址为所述TE隧道的源地址，以所述第二网络设备的loopback地址为所述TE隧道的的目标地址；根据所述配置参与建立所述TE隧道。
第二方面，本申请实施例提供第一网络设备，包括：获取模块，用于获取第二网络设备的第二标识；处理模块，用于根据第一标识和所述第二标识，确定所述第一网络设备上的接口的互联网协议IP地址；其中，所述第一标识为所述第一网络设备的设备标识，所述第二标识为所述第二网络设备的设备标识，所述第一标识和所述第二标识不同。
结合第二方面，在一种可能的实现方式中，所述第一网络设备上的接口，是所述第一网络设备和所述第二网络设备间的链路上的接口。
结合第二方面，在一种可能的实现方式中，所述处理模块用于：根据所述第一标识，所述第二标识和第一预设值，确定所述第一网络设备上的接口的IP地址。
结合第二方面，在一种可能的实现方式中，所述处理模块还用于：根据所述第一网络设备的接口的IP地址向所述第二网络设备发送地址解析协议ARP消息，使得所述第二网络设备根据所述ARP消息和子网掩码生成所述第二网络设备上的接口的IP地址。
结合第二方面，在一种可能的实现方式中，所述处理模块用于：根据所述第一标识与所述第二标识确定目标标识；根据所述目标标识和所述第一预设值，确定所述第一网络设备上的IP地址。
结合第二方面，在一种可能的实现方式中，所述处理模块用于：比较所述第一标识与所述第二标识；若所述第一标识比所述第二标识数值上小，则选择所述第一标识作为目标标识；若所述第一标识比所述第二标识数值上大，则选择所述第二标识作为目标标识。
结合第二方面，在一种可能的实现方式中，所述处理模块用于：比较所述第一标识与所述第二标识；若所述第一标识比所述第二标识数值上大，则选择所述第一标识作为目标标识；若所述第一标识比所述第二标识数值上小，则选择所述第二标识作为目标标识。
结合第二方面，在一种可能的实现方式中，所述第一标识为所述第一网络设备的预置的IP地址，所述第二标识为所述第二网络设备的预置的IP地址。
结合第二方面，在一种可能的实现方式中，所述处理模块用于：以所述目标标识的前24位为所述第一网络设备的接口的IP地址的前24位，以所述第一预设值为所述第一网络设备的接口的IP地址的后8位，组成所述第一网络设备的接口的IP地址。
结合第二方面，在一种可能的实现方式中，所述处理模块还用于：根据第二预设值和所述第一标识，确定环回loopback地址。
结合第二方面，在一种可能的实现方式中，所述处理模块还用于：获取标签分发协议LDP隧道的配置，所述配置中以所述loopback地址为网络设备的身份标识号ID；根据所述配置参与建立所述LDP隧道。
结合第二方面，在一种可能的实现方式中，所述处理模块还用于：获取流量工程TE隧 道的配置，所述配置中以所述loopback地址为所述TE隧道的源地址，以所述第二网络设备的loopback地址为所述TE隧道的的目标地址；根据所述配置参与建立所述TE隧道。
第三方面，本申请实施例提供一种网络设备，包括一个或一个以上中央处理器，存储器，有线或无线网络接口，电源；所述存储器为短暂存储存储器或持久存储存储器；所述中央处理器配置为与所述存储器通信，在所述网络设备上执行所述存储器中的指令操作，使得所述网络设备执行如第一方面的方法。
第四方面，本申请实施例提供一种芯片，所述芯片用于如第一方面的方法。
第五方面，本申请实施例提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行如第一方面的方法。
从以上技术方案可以看出，本申请实施例具有以下优点：
本申请实施例提供一种配置网络设备IP地址的方法及相关设备，该方法中，第一网络设备通过自身的设备标识和获取到的第二网络设备的设备标识确定第一网络设备的接口的IP地址，从而实现自动配置IP地址，简化了人工参与网络规划，减少人力成本。此外，第一网络设备还可以根据生成好的IP地址发送ARP消息至第二网络设备，使得第二网络设备能够根据该ARP消息和子网掩码生成第二网络设备的接口的IP地址，这样生产的两个IP地址能够避免IP冲突，实现两个网络设备之间链路的IP地址自动配置。
附图说明
图1为本申请实施例中IP无线接入网络的示意图；
图2为本申请实施例中配置网络设备IP地址的方法的流程图；
图3为本申请实施例一种应用场景的示意图；
图4为本申请实施例中网络设备交互的示意图；
图5为本申请实施例中网络设备的模块划分示意图；
图6为本申请实施例提供的一种网络设备的示意图。
具体实施方式
本申请实施例提供了一种配置网络设备IP地址的方法及相关设备，以解决目前IP链路地址仍需要网络管理员手工规划的技术问题。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“对应于”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为 比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
为了下述各实施例的描述清楚简洁，首先给出相关技术的简要介绍：
数据通信网络(data communication network，DCN)是指为传送平面、控制平面和管理平面的内部以及三者之间的管理信息和控制信息通信提供传送通路。DCN是一种支持网络七层协议栈中第一层(物理层)、第二层(数据链路层)和第三层(网络层)功能的网络，主要承载管理信息和分布式信令消息。在公用数据通信网中有电路交换、分组交换和租用电路三种形式的数据传输业务。
图1为本申请实施例中IP无线接入网络的示意图。如图1所示，当前IP无线接入网络(IP radio access network，IPRAN)中，链路中的网际互联协议(internet protocol，IP)地址和本地回环地址(loopback address)的配置为手工规划。为了防止网络中IP地址存在冲突，现网网络部署时需要用一张非常大的表格进行地址维护，每次网络部署时需要去申请空余地址，并且当需要查找一个IP地址时也很费工作量。
因此，在IPv6网络中，可以使用IPv6的链路本地地址(linklocal addresses)规划链路IP地址，省去了链路IP地址的规划配置，但本地还回环地址(loopback)目前还没有技术能够自动配置。IPv4网络目前还没有技术能够做到地址自动配置。
当前IPRAN网络还无法做到IPv6全量替代IPv4，在未来很长一段时间内，公网采用IPv4的方案还将是主流方案，IPv4地址规划还需要人工规划。目前一些网络管理员是按照一定的规律进行手工规划，虽然可以避免地址重复的场景，但依旧无法做到自动部署。
因此，本申请实施例提供一种配置网络设备IP地址的方法，用于解决上述IP地址无法自动配置的技术问题，特别是IPv4地址无法自动配置的问题。
图2为本申请实施例中配置网络设备IP地址的方法的流程图。该方法包括以下步骤：
101、网络设备1获取网络设备2的设备标识。
在本申请实施例中，网络设备可以是指DCN中的网元，因此也可以称为是网元(net element，NE)设备。在本申请实施例中，网络设备可以是路由器、交换机，还可以是接入点、基站等，本申请实施例对此不做限定。本申请实施例意在说明网络设备之间的IP地址自动配置，此处以两个网络设备，即网络设备1和网络设备2为例进行描述，其他网络设备可参照本申请实施例以实施，本申请实施例将不再赘述。
在一些实施例中，设备标识可以是NE_IP。NE_IP是网络设备自带的DCN的IP地址，是一种全网唯一的标识，一般是网络设备出厂时自带的标识(也可称为预置的设备标识)，可以保存在网络设备内部可读存储介质中，网络设备可以随时读取该标识。该NE_IP可以理解为一种特殊格式的IP地址，可以是网络管理人员在生产网络设备时预先配置的，也可以是网络设备出厂后，由网络管理人员对网络设备进行配置保存。在实际应用中，还可能通过其他方式配置网络设备的NE_IP，本申请实施例对此不做限定。该NE_IP能够保证在很长一段时间内不会重复。在本申请实施例中，NE_IP可以是32位的地址。该NE_IP的前8位为可以设定为预设的值。示例性的，某一NE_IP的前8位为“10.”。
在一些实施例中，设备标识也可以是其他类型的标识，例如网络设备的序列号，或者 网络设备的媒体存取控制(media access control，MAC)地址。在应用中，还可以是其他类型的标识，本申请实施例对此不做限定。为方便描述，本申请实施例以NE_IP进行描述，其他类型的设备标识可参照本申请实施例以实施，将不再赘述。
在一些实施例中，网络设备若采用其他类型的标识，例如网络设备的MAC地址，则网络设备可以通过预置的算法将该MAC地址转化为类似NE_IP的格式，以根据该转换格式后的标识来实施本申请实施例。在另一些情况下，网络设备采用其他类型的标识时，也可以采用特别的算法，根据两个网络设备的标识来协商确定网络设备的接口的IP地址，本申请实施例对此不做限定。
可以理解的是，网络设备1可以根据网管下发的自动配置IP地址命令来触发步骤101，在实际应用中也可以是其他方式触发步骤101，本申请实施例对此不做限定。在一些实施例中，网管下发命令时，还会下发子网掩码长度，例如子网掩码长度为8位，子网掩码长度为4位等。子网掩码可以用于配合ARP消息生成网络设备的接口的IP地址。
在一些实施例中，网络设备1可以通过链路层发现协议(link layer discovery protocol，LLDP)获取网络设备2的NE_IP。具体地，网络设备1可以在LLDP获取邻居详细信息时获取到网络设备2的NE_IP。示例性的，网络设备1可以根据LLDP邻居中的management IP(一种参数)获取到网络设备2的NE_IP。
其中，LLDP提供了一种标准的链路层发现方式，可以将本端设备的的主要能力、管理地址、设备标识、接口标识等信息组织成不同的TLV(Type/Length/Value，类型/长度/值)，并封装在链路层发现协议数据单元(link layer discovery protocol data unit，LLDPDU)中发布给与自己直连的邻居，邻居收到这些信息后将其以标准管理信息库(management information base，MIB)的形式保存起来，以供网络管理系统查询及判断链路的通信状况。网络设备可以通过在本地网络中发送LLDP来通告其他设备自身的状态。因此，LLDP是一种能够使网络中的设备互相发现并通告状态、交互信息的协议。
102、网络设备1可以根据网络设备1的设备标识和网络设备2的设备标识确定网络设备1的接口的IP地址。
在本申请实施例中，网络设备1可以根据网络设备1的设备标识和网络设备2的设备标识确定网络设备1的接口的IP地址。区别于NE_IP或环回(loopback)地址，本申请实施例中，网络设备的接口的IP地址也可以称为接口IP地址或链路IP地址。
在一些实施例中，设备标识的格式为IP地址的格式，如NE_IP，则网络设备1可以按照预置的算法根据网络设备1的设备标识和网络设备2的设备标识确定网络设备1的接口的IP地址(例如，选择其中一个设备标识作为网络设备1的接口的IP地址)。本申请实施例对上述任一预置的算法不做限定。以NE_IP为例，网络设备1获取到网络设备1的NE_IP和网络设备2的NE_IP后，可以对比两者的NE_IP，选择较小的NE_IP作为网络设备1的接口的IP地址。在本申请实施例中，NE_IP的对比方式可以是比较对应的数值大小，若NE_IP的数值比另一NE_IP的数值小，则可以确定该数值小的NE_IP为较小的NE_IP。示例性的，一个NE_IP为170.0.0.1，另一个NE_IP为170.0.0.2，则该170.0.0.1的NE_IP为较小的NE_IP。在另一些实施例中，网络设备1获取到网络设备1的NE_IP和网络设备2的NE_IP 后，可以对比两者的NE_IP，选择较大的NE_IP作为网络设备1的接口的IP地址。具体过程与前述实施例类似，此处不再赘述。在实际应用中，网络设备1也可以不是对比NE_IP的大小，而是采用其他方式或算法来选择其中一个NE_IP，本申请实施例对此不做限定。在实际应用中，网络设备1还可以不是选择其中一个NE_IP，而是根据两者的NE_IP生成一个新的NE_IP，本申请实施例对此不作限定。
一般地，网络设备1的的NE_IP和网络设备2的NE_IP不会相同。然而，若出现网络设备1的的NE_IP和网络设备2的NE_IP相同的情况，则网络设备1可以选择其中任意一个NE_IP。
在一些实施例中，网络设备1可以按照预置的算法，根据网络设备1的设备标识、网络设备2的设备标识以及预设值确定网络设备1的接口的IP地址。具体地，网络设备1可以从网络设备1的设备标识、网络设备2的设备标识中选择一个作为目标标识，然后根据目标标识和预设值确定网络设备1的接口的IP地址。其中，从两个设备标识中选择一个的方式与前述实施例类似，此处不再赘述。
以NE_IP为例，网络设备1确定较小的NE_IP为目标标识后，可以将NE_IP的前24位作为接口的IP地址的前24位，以预设的值作为接口的IP地址的后8位，形成接口的IP地址。示例性的，较小的NE_IP为170.0.0.1，预设的值为254，则网络设备可以将较小的NE_IP的前24位作为接口的IP地址的前24位，以254为接口的IP地址的后8位，则接口的IP地址为170.0.0.254。
在另一些实施例中，网络设备1可以对比网络设备1的NE_IP和网络设备2的NE_IP，然后选择较大的NE_IP的前24位作为接口的IP地址的前24位，以预设的值作为接口的IP地址的后8位，形成接口的IP地址。示例性的，一个NE_IP为170.0.0.1，另一个NE_IP为170.0.0.2，则该170.0.0.2的NE_IP为较大的NE_IP。而预设的值为254，则网络设备1可以将较大的NE_IP的前24位作为接口的IP地址的前24位，以254为接口的IP地址的后8位，则接口的IP地址为170.0.0.254。
在另一些实施例中，网络设备1可以对比网络设备1的NE_IP和网络设备2的NE_IP，然后选择较小的NE_IP的后24位作为接口的IP地址的后24位，以预设的值作为接口的IP地址的前8位，形成接口的IP地址。示例性的，一个NE_IP为170.0.0.1，另一个NE_IP为170.0.0.2，则该170.0.0.1的NE_IP为较小的NE_IP。而预设的值为254，则网络设备1可以将较小的NE_IP的后24位作为接口的IP地址的后24位，以254为接口的IP地址的前8位，则接口的IP地址为254.0.0.1。
在实际应用中，网络设备1中配置接口的IP地址的具体方式还可以根据实际需要具体设置，例如选择目标标识的前16位为接口的IP地址的前16位，预设值为接口的IP地址的后16位等方式，本申请实施例对此不做限定。
在一些实施例中，设备标识的格式为非IP地址的格式，则网络设备1可以将该设备标识的格式通过预置算法转换为IP地址的格式，然后确定网络设备1的接口的IP地址。示例性的，设备标识为MAC地址，其中网络设备1的设备标识为08：00：20：0A：8C：6D，网络设备2的设备标识为04：00：40：0B：8D：6E，则网络设备1可以通过预置特别的算 法根据上述两个MAC地址确定网络设备1的接口的IP地址，或者网络设备1可以通过预置的算法将上述两个MAC地址转换为IP地址的格式，例如将08：00：20：0A：8C：6D转换为8.0.20.10，将04：00：40：0B：8D：6E转换为4.0.4.11，然后再按照上述实施例的方式，根据8.0.20.10和4.0.4.11确定网络设备1的接口的IP地址。本申请实施例对上述任一预置的算法不做限定。
在另一些实施例中，设备标识的格式为非IP地址的格式，则网络设备1可以通过预置特别的算法直接根据网络设备1的设备标识和网络设备2的设备标识确定网络设备1的接口的IP地址。本申请实施例对上述任一预置的算法不做限定。
103、网络设备1发送ARP消息至网络设备2，使得网络设备2接收到该ARP消息后结合掩码生成网络设备2的接口的IP地址。
在本申请实施例中，网络设备1的接口的IP地址可以称为本地接口IP，网络设备2的接口的IP地址可以称为对端接口IP。
在本申请实施例中，网络设备1发送免费ARP消息中携带的是网络设备1的接口的IP地址，网络设备2接收到免费ARP消息后，可以结合免费ARP消息中携带的网络设备1的接口的IP地址以及配置的掩码生成网络设备2的接口的IP地址。由于网络设备2从ARP中可以得到网络设备1的接口的IP地址，因此网络设备2生成的网络设备2的接口的IP地址不会与网络设备1的接口的IP地址冲突，从而防止了IP冲突。
可以理解的是，掩码也可以称为子网掩码(subnet mask)，是一种用来指明一个IP地址的哪些位标识的是主机所在的子网，以及哪些位标识的是主机的位掩码。
当网络设备2的接口的IP地址建立后，网络设备1接口的的IP地址和网络设备2的接口的IP地址均已知，则网络设备1和网络设备2之间可以通过两者的接口的IP地址收发数据。
上述网络设备1和网络设备2组成的内部网关协议(interior gateway protocol，IGP)域内，网络设备1和网络设备2的地址不会重复。
104、网管服务器根据网络设备1和网络设备2各自的环回地址向网络设备1和网络设备2下发LDP隧道的配置，使得网络设备1和网络设备2可以建立LDP隧道。
在本申请实施例中，网络设备1和网络设备2配置好接口的IP地址后，可以通过DCN网络通道交给网管服务器管理。即网管服务器管理网络设备1和网络设备2。因此，网管服务器可以向网络设备1和网络设备2下发LDP隧道的配置。
LDP隧道的配置中，包括接口下的多协议标签交换技术(multiprotocol label switching，MPLS)属性、标签分发协议(label distribution protocol，LDP)属性等。其中，网管服务器可以将MPLS LSR-ID指定为网络设备的NE_IP转换后的环回地址(loopback address)。
其中，LSR-ID是指采用标签交换技术转发报文的路由器(lable switching router，LSR)的身份证标识号(identity document，ID)。
其中，loopback地址是loopback接口对应的地址。Loopback接口是虚拟接口，是一种纯软件性质的虚拟接口。任何送到该loopback接口的网络数据报文都会被认为是送往设 备自身的。因此，loopback接口和loopback地址都有广泛的应用。
在本申请实施例中，网络设备可以根据预设值和设备标识确定loopback地址。例如，在一些实施例中，网络设备可以利用NE_IP转换为loopback地址。示例性的，网络设备1可以配置预设值A为loopback地址的前8位，配置NE_IP的后24位为loopback地址的后24位，即loopback地址为A.NE_IP。例如，预设值A为127，NE_IP的后24位为0.0.1，则loopback地址为127.0.0.1。其他网络设备确定loopback地址的方式同理，本申请实施例不再赘述。在实际应用中，网络设备还可以采用其他算法来确定loopback地址，例如将非IP地址格式的设备标识转换为IP地址格式的设备标识，再根据预设值和设备标识确定loopback地址，本申请实施例对此不再赘述。
在本申请实施例中，网管服务器指定LSR-ID和下发常规配置后，端到端的LDP LSP已经部署完成，并且网管服务器上已经有完整的拓扑关系。若业务需要迭代的LDP隧道，则网络管理员可以通过网管服务器自行部署相应的LDP隧道。
105、网管服务器指定网络设备2的loopback地址为TE隧道的目标IP，指定网络设备1的loopback地址为TE隧道的源地址，下发指定后的配置到网络设备1和网络设备2，以建立TE隧道。
在本申请实施例中，步骤104和步骤105没有顺序关系，可以先执行步骤105，后执行步骤105，也可以先执行步骤105，再执行步骤104。在一些实施例中，步骤104和步骤105可以同时执行，本申请实施例对此不做限定。此外，也可以只执行步骤104，或只执行步骤105。
在本申请实施例中，流量工程(traffic engineering，TE)隧道通过实时监控网络的流程和网络单元的负载，动态调整流量管理参数、路由参数和资源约束参数等，使网络运行状态迁移到理想状态，优化网络资源的使用，避免负载不均衡导致的拥塞。
在配置TE隧道时，网管服务器可以指定网络设备2的loopback地址为TE隧道的目标IP，指定网络设备1的loopback地址为TE隧道的源地址，形成相应的配置，并下发给网络设备1和网络设备2。
在一些实施例中，若需要下发标签转发路径(segmentrouting best effort，SRBE)，则网络管理员可以通过网管服务器在定制化模板中增加segment相关的配置即可实现相应的隧道业务。
在一些实施例中，若需要下发边界网关协议(border gateway protocol，BGP)，则网络管理员可以通过网管服务器以及网络设备上的loopback地址下发BGP的邻居配置，建立相关的连接。
因此，网管服务器可以通过上述的loopback地址配置各种隧道实现对各个网络设备的管理，当网络设备之间建立隧道后，可以通过上述步骤建立的接口的IP地址进行转发数据。具体地，网管服务器可以根据loopback地址指定各种隧道的配置，例如上述的将MPLS LSR-ID指定为网络设备的loopback地址，然后将这些配置下发到网络设备，使得网络设备根据这些配置建立对应的隧道，实现隧道的自动部署。
图3为本申请实施例一种应用场景的示意图。在DCN网络下，从基站侧开始连接的网 络设备分别为基站侧网关(cell site gate，CSG)、接入业务网关(access service gateway，ASG)、无线业务网关(radio service gateway，RSG)、无线网络控制器(radio network controller，RNC)。此外，该系统中还包括DCN网络以及网络监控服务器(network monitoring service)。
如图3所示的网络设备中，每两个网络设备都可以采用如上述实施例的方式生成接口的IP地址，建立链路。示例性的，基站侧网关与接入业务网关1可按照如上述实施例的方式生成接口的IP地址，建立链路。接入业务网关1和接入业务网关2也可以按照如上述实施例的方式生成接口的IP地址，建立链路。本申请实施例对此不再赘述。
在一些实施例中，无线业务网关可以将各个链路信息上报至数据通信网络，数据通信网络连接有网络监控服务器。管理人员可以通过网络监控服务器实时监控各个网络设备的链路情况以及通信情况。若发生网络故障，管理人员可以通过网络监控服务器实时了解到发生网络故障的具体网络设备，然后修复该网络故障。
图4为本申请实施例中网络设备交互的示意图。可见网络设备1和网络设备2均可利用各自的NE_IP生成loopback地址，分别生成各自的loopback地址(即loopback1地址和loopback2地址)。
以网络设备1生成loopback1地址为例，网络设备1可以将NE_IP1(网络设备1的NE_IP为NE_IP1，网络设备2的NE_IP为NE_IP2)的后24位作为loopback1地址的后24位，将loopback1地址的前8位设置为预设值A，从而生成loopback1地址为A.NE_IP1。
在另一些实施例中，网络设备1可以将NE_IP1的前24位作为loopback1地址的前24位，将loopback1地址的后8位设置为预设值B，从而生成loopback1地址为NE_IP1.B。
在实际应用中，网络设备1还可以采用其他类似的方式生成loopback1地址，本申请实施例对此不做限定。网络设备2生成loopback2地址的方式类似，采用的预设值可以与网络设备1相同，例如预设值为A，也可以与网络设备1不同，例如预设值为C，此处不再赘述。
在本申请实施例中，网络设备1和网络设备2可以根据双方的NE_IP协商生成各自的接口的IP地址，具体的步骤方法与前述实施例类似，此处不再赘述。
网络设备1和网络设备2生成loopback地址以及协商建立链路后，可以根据loopback地址建立LDP隧道、TE隧道或SRBE隧道，根据接口的IP地址转发对应的数据。在实际应用中，还可以建立其他类似的隧道，本申请实施例对此不做限定。
同理，若存在网络设备3准备与网络设备1建立链路，则可以参照上述实施例的步骤方法建立接口的IP地址，实现网络设备1和网络设备3的IP自动配置。
图5为本申请实施例中网络设备的模块划分示意图。该网络设备500包括：获取模块501，用于获取第二网络设备的第二标识；处理模块502，用于根据第一标识和所述第二标识，确定所述第一网络设备上的接口的互联网协议IP地址；其中，所述第一标识为所述第一网络设备的设备标识，所述第二标识为所述第二网络设备的设备标识，所述第一标识和所述第二标识不同。
在一些实施例中，获取模块501可以执行前述图2所示实施例中网络设备1执行的步 骤101以及图4所示实施例中网络设备获取对端NE_IP的操作。处理模块502可以执行前述图2或图4所示实施例中网络设备1所执行的操作(除去前述获取模块所执行的操作)，具体此处不再赘述。
图6为本申请实施例提供的一种网络设备的示意图。该网络设备可以包括一个或一个以上中央处理器601，存储器602，有线或无线网络接口603，电源604。
存储器602可以是短暂存储或持久存储。更进一步地，中央处理器601可以配置为与存储器602通信，在网络设备上执行存储器602中的一系列指令操作，并配合所述网络接口603，使得图6中的网络设备可以执行前述图2或图4所示实施例中网络设备1所执行的操作，具体此处不再赘述。
在一些实施例中，有线或无线网络接口603，可以用于发送和接收ARP报文，或者获取LDP或TE隧道的配置，或者在参与建立LDP或TE隧道中发送和接收相应的报文。应理解，有线或无线网络接口603包括至少一个网络接口。
本实施例中，中央处理器601中的具体功能模块划分可以与前述图5中所描述的获取模块、处理模块的功能模块划分方式类似，此处不再赘述。
本申请实施例还提供一种芯片，所述芯片可以执行上述实施例中网络设备1所执行的方法。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述实施例中网络设备1所执行的方法。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部 分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (27)

  1. 一种配置网络设备IP地址的方法，其特征在于，包括：
    第一网络设备获取第二网络设备的第二标识；
    所述第一网络设备根据第一标识和所述第二标识，确定所述第一网络设备上的接口的互联网协议IP地址；
    其中，所述第一标识为所述第一网络设备的设备标识，所述第二标识为所述第二网络设备的设备标识，所述第一标识和所述第二标识不同。
  2. 根据权利要求1所述的方法，其特征在于，所述第一网络设备上的接口，是所述第一网络设备和所述第二网络设备间的链路上的接口。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一网络设备根据所述第一标识和所述第二标识，确定所述第一网络设备上的互联网协议IP地址，包括：
    所述第一网络设备根据所述第一标识，所述第二标识和第一预设值，确定所述第一网络设备上的IP地址。
  4. 根据权利要求1至3任意一项所述的方法，其特征在于，所述第一网络设备根据所述第一标识和所述第二标识，确定所述第一网络设备上的互联网协议IP地址之后，所述方法还包括：
    所述第一网络设备根据所述第一网络设备的接口的IP地址向所述第二网络设备发送地址解析协议ARP消息，使得所述第二网络设备根据所述ARP消息和子网掩码生成所述第二网络设备上的接口的IP地址。
  5. 根据权利要求3至4任意一项所述的方法，其特征在于，所述第一网络设备根据所述第一标识，所述第二标识和第一预设值，确定所述第一网络设备上的IP地址，包括：
    所述第一网络设备根据所述第一标识与所述第二标识确定目标标识；
    所述第一网络设备根据所述目标标识和所述第一预设值，确定所述第一网络设备上的接口的IP地址。
  6. 根据权利要求5所述的方法，其特征在于，所述第一网络设备根据第一标识与所述第二标识确定目标标识包括：
    所述第一网络设备比较所述第一标识与所述第二标识；
    若所述第一标识比所述第二标识数值上小，则所述第一网络设备选择所述第一标识作为目标标识；
    若所述第一标识比所述第二标识数值上大，则所述第一网络设备选择所述第二标识作为目标标识。
  7. 根据权利要求5所述的方法，其特征在于，所述第一网络设备根据第一标识与所述第二标识确定目标标识包括：
    所述第一网络设备比较所述第一标识与所述第二标识；
    若所述第一标识比所述第二标识数值上大，则所述第一网络设备选择所述第一标识作为目标标识；
    若所述第一标识比所述第二标识数值上小，则所述第一网络设备选择所述第二标识作 为目标标识。
  8. 根据权利要求1至7任意一项所述的方法，其特征在于，所述第一标识为所述第一网络设备的预置的IP地址，所述第二标识为所述第二网络设备的预置的IP地址。
  9. 根据权利要求5至8任意一项所述的方法，其特征在于，所述第一网络设备根据所述目标标识和所述第一预设值，确定所述第一网络设备上的接口的IP地址包括：
    所述第一网络设备以所述目标标识的前24位为所述第一网络设备的接口的IP地址的前24位，以所述第一预设值为所述第一网络设备的接口的IP地址的后8位，组成所述第一网络设备的接口的IP地址。
  10. 根据权利要求1至9任意一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备根据第二预设值和所述第一标识，确定环回loopback地址。
  11. 根据权利要求1至10任意一项所述的方法，其特征在于，所述第一网络设备根据第二预设值和所述第一标识，确定环回loopback地址之后，所述方法还包括：
    所述第一网络设备获取标签分发协议LDP隧道的配置，所述配置中以所述loopback地址为网络设备的身份标识号ID；
    所述第一网络设备根据所述配置参与建立所述LDP隧道。
  12. 根据权利要求1至10任意一项所述的方法，其特征在于，所述第一网络设备根据第二预设值和所述第一标识，确定环回loopback地址之后，所述方法还包括：
    所述第一网络设备获取流量工程TE隧道的配置，所述配置中以所述loopback地址为所述TE隧道的源地址，以所述第二网络设备的loopback地址为所述TE隧道的的目标地址；
    所述第一网络设备根据所述配置参与建立所述TE隧道。
  13. 第一网络设备，其特征在于，包括：
    获取模块，用于获取第二网络设备的第二标识；
    处理模块，用于根据第一标识和所述第二标识，确定所述第一网络设备上的接口的互联网协议IP地址；
    其中，所述第一标识为所述第一网络设备的设备标识，所述第二标识为所述第二网络设备的设备标识，所述第一标识和所述第二标识不同。
  14. 根据权利要求13所述的网络设备，其特征在于，所述第一网络设备上的接口，是所述第一网络设备和所述第二网络设备间的链路上的接口。
  15. 根据权利要求13或14所述的网络设备，其特征在于，所述处理模块用于：
    根据所述第一标识，所述第二标识和第一预设值，确定所述第一网络设备上的接口的IP地址。
  16. 根据权利要求13至15任意一项所述的网络设备，其特征在于，所述处理模块还用于：
    根据所述第一网络设备的接口的IP地址向所述第二网络设备发送地址解析协议ARP消息，使得所述第二网络设备根据所述ARP消息和子网掩码生成所述第二网络设备上的接口的IP地址。
  17. 根据权利要求13至16任意一项所述的网络设备，其特征在于，所述处理模块用于：
    根据所述第一标识与所述第二标识确定目标标识；
    根据所述目标标识和所述第一预设值，确定所述第一网络设备上的IP地址。
  18. 根据权利要求13至17任意一项所述的网络设备，其特征在于，所述处理模块用于：
    比较所述第一标识与所述第二标识；
    若所述第一标识比所述第二标识数值上小，则选择所述第一标识作为目标标识；
    若所述第一标识比所述第二标识数值上大，则选择所述第二标识作为目标标识。
  19. 根据权利要求13至17任意一项所述的网络设备，其特征在于，所述处理模块用于：
    比较所述第一标识与所述第二标识；
    若所述第一标识比所述第二标识数值上大，则选择所述第一标识作为目标标识；
    若所述第一标识比所述第二标识数值上小，则选择所述第二标识作为目标标识。
  20. 根据权利要求13至19任意一项所述的网络设备，其特征在于，所述第一标识为所述第一网络设备的预置的IP地址，所述第二标识为所述第二网络设备的预置的IP地址。
  21. 根据权利要求13至20所述的网络设备，其特征在于，所述处理模块用于：
    以所述目标标识的前24位为所述第一网络设备的接口的IP地址的前24位，以所述第一预设值为所述第一网络设备的接口的IP地址的后8位，组成所述第一网络设备的接口的IP地址。
  22. 根据权利要求13至21任意一项所述的网络设备，其特征在于，所述处理模块还用于：
    根据第二预设值和所述第一标识，确定环回loopback地址。
  23. 根据权利要求13至22任意一项所述的网络设备，其特征在于，所述处理模块还用于：
    获取标签分发协议LDP隧道的配置，所述配置中以所述loopback地址为网络设备的身份标识号ID；
    根据所述配置参与建立所述LDP隧道。
  24. 根据权利要求13至23任意一项所述的网络设备，其特征在于，所述处理模块还用于：
    获取流量工程TE隧道的配置，所述配置中以所述loopback地址为所述TE隧道的源地址，以所述第二网络设备的loopback地址为所述TE隧道的的目标地址；
    根据所述配置参与建立所述TE隧道。
  25. 一种网络设备，其特征在于，包括一个或一个以上中央处理器，存储器，有线或无线网络接口，电源；
    所述存储器为短暂存储存储器或持久存储存储器；
    所述中央处理器配置为与所述存储器通信，在所述网络设备上执行所述存储器中的指令操作，使得所述网络设备执行权利要求1至12中任意一项所述的方法。
  26. 一种芯片，其特征在于，所述芯片用于执行权利要求1至12任意一项所述的方法。
  27. 一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行权利要求1至12任意一项所述的方法。
PCT/CN2021/094077 2020-05-25 2021-05-17 一种配置网络设备ip地址的方法及相关设备 WO2021238699A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010451992.5 2020-05-25
CN202010451992.5A CN113726916B (zh) 2020-05-25 2020-05-25 一种配置网络设备ip地址的方法及相关设备

Publications (1)

Publication Number Publication Date
WO2021238699A1 true WO2021238699A1 (zh) 2021-12-02

Family

ID=78671206

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/094077 WO2021238699A1 (zh) 2020-05-25 2021-05-17 一种配置网络设备ip地址的方法及相关设备

Country Status (2)

Country Link
CN (1) CN113726916B (zh)
WO (1) WO2021238699A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090201832A1 (en) * 2008-02-07 2009-08-13 Frederick Brown Methods and systems for preventing the misconfiguration of osrp and osi/isis networks using a network management system
CN102164188A (zh) * 2011-03-31 2011-08-24 华为技术有限公司 网络地址的分配方法、装置和系统
CN105337754A (zh) * 2014-08-07 2016-02-17 中兴通讯股份有限公司 一种数据通信网络开通方法及系统
CN107769939A (zh) * 2016-08-17 2018-03-06 华为技术有限公司 数据通信网中网元管理方法、网管、网关网元及系统
CN108134705A (zh) * 2017-12-29 2018-06-08 北京华为数字技术有限公司 一种dcn管理方法、设备及系统
CN109582439A (zh) * 2018-11-26 2019-04-05 深圳前海微众银行股份有限公司 Dcn部署方法、装置、设备及计算机可读存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104579728B (zh) * 2013-10-17 2019-02-26 中兴通讯股份有限公司 网元设备配置和管理方法、装置及网元设备
CN105591798B (zh) * 2015-07-24 2019-04-09 新华三技术有限公司 Dcn中传输oam信息的方法、装置
US9979693B2 (en) * 2016-01-28 2018-05-22 Fiber Logic Communications, Inc. IP allocation method for use in telecommunication network automatic construction
US10484515B2 (en) * 2016-04-29 2019-11-19 Nicira, Inc. Implementing logical metadata proxy servers in logical networks
CN110971716B (zh) * 2018-09-29 2022-08-30 中国电信股份有限公司 地址配置方法、装置、系统和计算机可读存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090201832A1 (en) * 2008-02-07 2009-08-13 Frederick Brown Methods and systems for preventing the misconfiguration of osrp and osi/isis networks using a network management system
CN102164188A (zh) * 2011-03-31 2011-08-24 华为技术有限公司 网络地址的分配方法、装置和系统
CN105337754A (zh) * 2014-08-07 2016-02-17 中兴通讯股份有限公司 一种数据通信网络开通方法及系统
CN107769939A (zh) * 2016-08-17 2018-03-06 华为技术有限公司 数据通信网中网元管理方法、网管、网关网元及系统
CN108134705A (zh) * 2017-12-29 2018-06-08 北京华为数字技术有限公司 一种dcn管理方法、设备及系统
CN109582439A (zh) * 2018-11-26 2019-04-05 深圳前海微众银行股份有限公司 Dcn部署方法、装置、设备及计算机可读存储介质

Also Published As

Publication number Publication date
CN113726916B (zh) 2023-02-03
CN113726916A (zh) 2021-11-30

Similar Documents

Publication Publication Date Title
CN107438016B (zh) 网络管理方法、设备、系统以及存储介质
US10057116B2 (en) Method and device for configuring and managing network element equipment, and network element equipment
WO2022166691A1 (zh) 一种业务处理方法、装置、存储介质及电子装置
US11374857B2 (en) Network device management method and apparatus, and system for indicating a network device to perform management operation
US6628623B1 (en) Methods and systems for determining switch connection topology on ethernet LANs
WO2016177030A1 (zh) Sdn网络设备建链方法、设备和系统
US8295204B2 (en) Method and system for dynamic assignment of network addresses in a communications network
WO2021018155A1 (zh) 一种路由信息监控方法和装置
CN108964940B (zh) 消息发送方法及装置、存储介质
US20230283554A1 (en) BIER Packet Forwarding Method, Device, and System
CN102801623B (zh) 一种多接入数据转发方法及设备
WO2021047320A1 (zh) 一种转发路径的确定方法及装置
EP3675431B1 (en) Core isolation for logical tunnels stitching multi-homed evpn and l2 circuit
US20070233887A1 (en) Method and apparatus for neighborhood discovery across disparate point-to-point networks
EP3975514A1 (en) Targeted neighbor discovery for border gateway protocol
EP3817285B1 (en) Method and device for monitoring forwarding table entry
US20230086487A1 (en) Method for Determining Processing Capability, Node, and System
US20230010837A1 (en) Fault diagnosis method and apparatus thereof
EP3461080B1 (en) Topology determination method, message response method, controller and switch
JP7119174B2 (ja) ネットワークトポロジディスカバリ方法、ネットワークトポロジディスカバリ装置及びネットワークトポロジディスカバリシステム
US10686752B2 (en) Methods for configuring and managing an IP network, corresponding devices and computer programs
WO2021238699A1 (zh) 一种配置网络设备ip地址的方法及相关设备
US20230048037A1 (en) Information Reporting Method, Information Processing Method, Apparatus, and Device
US11784919B2 (en) Method for sending BIERv6 packet and first network device
EP2890053B1 (en) Ds domain generating method and system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21812609

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21812609

Country of ref document: EP

Kind code of ref document: A1