WO2011144139A1

WO2011144139A1 - Method and device for detecting internet protocol address collision in autonomous system

Info

Publication number: WO2011144139A1
Application number: PCT/CN2011/075157
Authority: WO
Inventors: 刁操; 张鹏; 董辉
Original assignee: 华为技术有限公司
Priority date: 2010-10-30
Filing date: 2011-06-02
Publication date: 2011-11-24
Also published as: CN102457407A; CN102457407B

Abstract

Provided are a method and device for detecting Internet Protocol (IP) address collision in an autonomous system. The method includes: when a new interface enables an interior gateway protocol, a device in the autonomous system constructs a message which bears the IP address information of the interface of the device; the message is sent to all the devices in the autonomous system, and the message enables the devices which receive the message in the autonomous system to give the indication that the IP address collision occurs in the autonomous system, when the message is generated by other device other than the device itself which receives the message, and the IP address information in the message is the same as the IP address information of the interface of the device itself. The present invention can detect IP address collision in an autonomous system, thus improving the maintainability and reliability of IP networks.

Description

Method and device for detecting IP address conflict in autonomous system This application claims to be submitted to the Chinese Patent Office on October 30, 2010, and the application number is 201010525432. 6. The invention name is "Method and Design for Detecting IP Address Conflicts in Autonomous System"

The priority of the Chinese Patent Application, the entire disclosure of which is incorporated herein by reference.

Technical field

The present invention relates to an Internet network of IIPP networks, and particularly relates to a self-healing mechanism mechanism for distributing distributed routing routes of a type of IIPP network. . 1100 Back Background Technique

From the single-unit enterprise of the enterprise enterprise to the campus campus of the university, from the academic institution to the telecom business operator, from the government to the global ball Internet networking, IIPP ((IInntteerrnneett PPrroottooccooll Inter-connected Network Association Agreement)) Network network has achieved great success in the commercial and commercial aspects, from which the IIPP becomes It is the best choice for the best choice of today's communication and communication infrastructure. . Compared with the network network with the traditional connection and the face-to-face connection, on one side, the sub-distributed dynamic dynamic path of the IIPP network is self-healing. The mechanism of the machine provides the greater flexibility and expansion of the 1155, and the cocoa significantly reduces the cost of the lower deployment;; the other side, these The application should be applied to the IIPP network to propose new and new requirements. It is required to provide the IIPP network to provide higher reliability and reliability performance. .

In practice, it should be applied in the middle and the middle, because the network of the IIPP network is getting bigger and bigger, the planning plan is not unreasonable or the operation will be led to the IIPP. The situation of the address and the conflict situation, and the question of the conflict of the current address of the IIPP address. . It is difficult to find out the situation of this kind of situation, and it has a great impact on the business operations of the industry. More likely, it may lead to the whole network network. .

2200 below the lower side to the conflict with the IIPP address address 00SSPPFF agreement ((OOppeenn SShhoorrtteesstt PPaatthh FFiirrsstt RRoouuttiinngg

PPrroottooccooll The shortest short-circuit path is preferred, and the LLDDPP agreement ((LLaabbeell DDiissttrriibbuuttiioonn PPrroottooccooll labeling and distribution agreement)) Explain clearly. .

(( 11 )) The impact of the IIPP address on the 00SSPPFF agreement

As shown in FIG. 11 , in one self-governing system system, it is assumed that two or two sets of equipment in the 00SSPPFF area area 00 are provided with RRTTEE.

2255 and two or two interface ports of RRTTFF are duplicated and reset. The routing is always interrupted from time to time, and severely severely affects the business of the business. . Other areas of its area, such as: area area 11, area area 22, and area area 33 will also frequently perform frequent routing calculations, which may result in The effects of the bad shadows are included in the following:: Frequent frequent routing is calculated by the meter, and the routing of the route is sometimes from time to time;; the CCPPUU of the network network equipment is occupied by high occupancy. ;; and also the time and cost of the large amount of time, and there is no way to accurately find the fault point. .

As shown in FIG. 22, in one self-governing system system, it is assumed that two or two sets of equipment are provided for the RRTTBB and the RRTTCC are disposed in the configuration IIPPvv66. At the address, the local connection is assigned the same address. Since the outgoing interfaces of the device RTA to RTB and RTC are different, there is no problem for the IGP (Interior Gateway Protocol) or BGP (Border Gateway Protocol) protocol. However, it may cause calculation errors for the LDP protocol. LDP can use the next hop address plus the interface and route matching of the neighbor to find the downstream session. However, in the case of a remote session, LDP cannot find the neighbor's interface. If the addresses on the two remote neighbors are the same, the LDP cannot calculate the downstream session and the forwarding service is interrupted.

It can be seen that in an autonomous system, detecting IP address conflicts is very helpful for improving the maintainability and reliability of IP networks. Summary of the invention

The technical problem to be solved by the present invention is to overcome the deficiencies of the prior art described above, and to provide a method and device capable of detecting IP address conflicts in an autonomous system, thereby improving the maintainability and reliability of the IP network.

The technical solution proposed by the present invention for the above technical problem includes a method for detecting an IP address conflict in an autonomous system, the method comprising:

The device in the autonomous system, when a new interface is enabled with the internal gateway protocol, constructs a packet carrying the IP address information of the interface of the device;

Transmitting the packet to all devices in the autonomous system, where the packet is used by the device in the autonomous system to receive the packet, where the packet is the device that receives the packet. When other devices are generated, and the IP address information in the packet is the same as the interface IP address information of the device itself, an indication of an IP address conflict in the autonomous system is given.

In the present invention, the internal gateway protocol may be an OSSPF protocol, and the device in the autonomous system runs a process that supports the 0SPF protocol, and the packet includes a link state advertisement LSA (Link State Advertise).

The process of constructing the LSA specifically includes: constructing a type length value TLV (Type, Length and Value type length value) carrying the interface IP address information of the device, and constructing the LSA by using the TLV.

The LSA is generated when at least one interface of the device in the autonomous system is enabled to the process supporting the 0SPF protocol, and each device in the autonomous system adds a TLV to carry the device correspondingly. Interface IP address information. In the present invention, the internal gateway protocol may be an is-is protocol, and the device in the autonomous system runs a process supporting the IS-IS protocol, and the packet includes a link state packet LSP (Link State Packets). .

The process of constructing the LSP specifically includes: constructing a type length value TLV carrying the interface IP address information of the device, and constructing the LSP by using the TLV.

The TLV is constructed when at least one interface of the device in the autonomous system is enabled to the process supporting the IS-IS protocol, and each additional device in the autonomous system will be correspondingly in the TLV. Add an interface IP address information.

In the present invention, the indication that the device in the autonomous system gives an IP address conflict in the autonomous system specifically includes:

Give an alarm to the network management system;

Log on the device; or

Give an alarm to the NMS and log the device.

The technical solution proposed by the present invention for the above technical problem further includes an apparatus capable of detecting an IP address conflict of an Internet protocol in an autonomous system, including:

The first module is configured to construct a packet carrying the IP address information of the interface of the device when the internal interface protocol is enabled on the new interface;

a second module, configured to send the packet to all devices in the autonomous system, where the packet causes the device in the autonomous system to receive the packet, where the packet is received When the device other than the device itself is generated, and the IP address information in the packet is the same as the interface IP address information of the device itself, an indication of an IP address conflict in the autonomous system is given.

In the present invention, the first module may specifically include:

The first unit, the type length value used to construct the IP address information of the interface carrying the device

TLV;

The second unit constructs the message with the TLV.

Compared with the prior art, the method and device for detecting an IP address conflict in an autonomous system of the present invention can compare the IP address information of the interface with each device by including the interface IP address information in the link information packet. Checking for conflicts can quickly detect IP address conflicts in the autonomous system, thus providing the possibility to improve the maintainability and reliability of the IP network. DRAWINGS

Figure 1 is a hypothetical IP address collision scenario in an autonomous system using 0SPF.

Figure 2 is a hypothetical IP address collision scenario in an autonomous system using LDP.

3 is a flow chart of a method of detecting an IP address conflict in an autonomous system of the present invention.

4 is a block diagram of an apparatus for detecting an IP address conflict in an autonomous system of the present invention.

Figure 5 shows an autonomous system scenario where the assumed IP addresses conflict, and the address is an IPv4 address.

Figure 6 shows an autonomous system scenario where the assumed IP addresses conflict, and the address is an IPv6 address.

7 is a new addition of the present invention when the autonomous system shown in FIG. 5 selects the 0SPF protocol.

Opaque LSA structure.

FIG. 8 is a new Opaque LSA structure of the present invention used when the autonomous system shown in FIG. 6 selects the 0SPF protocol.

Figure 9 is a diagram showing the new TLV structure of the present invention used when the IS-IS protocol is selected for the autonomous system shown in Figure 5.

Figure 10 is a diagram showing the new TLV structure of the present invention used when the IS-IS protocol is selected for the autonomous system shown in Figure 6.

FIG. 11 is an existing TLV used when the autonomous system shown in FIG. 5 selects the IS-IS protocol. FIG. 12 is an existing TLV structure used when the autonomous system shown in FIG. 6 selects the IS-IS protocol. detailed description

The invention will be further elaborated below in conjunction with the drawings.

The method for detecting an IP address conflict of an Internet protocol in an autonomous system of the present invention, as shown in FIG. 3, includes:

Step 101: The device in the autonomous system constructs a packet carrying the IP address information of the interface of the device when the internal interface protocol is enabled on the new interface.

Step 102: Send the packet to all devices in the autonomous system.

Step 103: The packet is generated by the device in the autonomous system that receives the packet, and the packet is generated by the device other than the device itself that received the packet, and the packet is in the packet. The autonomous system is given when the IP address information is the same as the interface IP address information of the device itself. An indication of an IP address conflict occurs.

The device for detecting an IP address conflict of an Internet protocol in an autonomous system, as shown in FIG. 4, includes:

The first module 1 is configured to construct a packet carrying the IP address information of the interface of the device when the internal interface protocol is enabled on the new interface.

a second module 2, configured to send the packet to all devices in the autonomous system, where the packet causes the device in the autonomous system to receive the packet, where the packet is received When the device of the packet is generated by a device other than the device itself, and the IP address information in the packet is the same as the IP address information of the device itself, an indication of an IP address conflict occurs in the autonomous system. .

The first module 1 may specifically include:

The first unit 11 is configured to construct a type length value of the interface carrying the IP address information of the device.

TLV;

The second unit 12 constructs the message with the TLV.

It can be seen that, by carrying the interface IP address information in the packet, each device in the autonomous system compares the IP address information of the interface, and can detect the address conflict, thereby achieving the purpose of quickly detecting the IP address conflict of the entire network.

In the present invention, an autonomous system refers to a router and a network group under the control of a management authority. It can be a router directly connected to a LAN (Local Area Network) and also connected to the Internet (Internet); it can be a LAN connected by an enterprise backbone. All routers in an autonomous system must be connected to each other, run the same routing protocol, and assign the same autonomous system number.

In the present invention, the IGP may be 0SPF or an IS-IS (Intermediate System to Intermediate System). The IP address information can be either an IPv4 address or an IPv6 address.

In the following specific embodiments of the present invention, the internal gateway protocol may use the 0SPF protocol, and the message includes a link state advertisement LSA, which is a new type of the present invention. The LSA construction process may specifically include: constructing a type length value of an interface IP address information carrying the device.

TLV, the LSA was constructed using the TLV.

In the LSA, each interface IP address information may have a total storage space of 8 bytes, including a 4-byte address space and a 4-byte mask space; or may have a total storage space of 20 bytes. Includes a 16-byte address prefix space and a 4-byte prefix length space. In the following specific embodiments of the present invention, the internal gateway protocol may also be an IS-IS protocol, and the packet includes a link state message LSP. The process of constructing the LSP specifically includes: constructing a type length value TLV carrying the interface IP address information of the device, and constructing the LSP by using the TLV. The type of the TLV can be new or existing.

For the case where the TLV is new, the IP address information of each interface may be 8 bytes of total storage space, including 4 bytes of address space and 4 bytes of mask space; or may have a prefix of 1 byte. The length space and the prefix length space of the number of address prefix bytes determined by the prefix length.

For the TLV, the IP address information of each interface can be an IPv4 address with a length of 4 bytes, or an IPv6 address with a length of 16 bytes.

The following is further illustrated by a plurality of embodiments. Example 1 Detecting IPv4 address conflicts by adding OSPF Opaque LSAs (opaque link state advertisements)

An autonomous system situation in which a hypothetical IP address conflicts, as shown in Figure 5, where the interface

The IP address information is an IPv4 address, and the IGP uses 0SPF. The four routers Router_A, Router_B, Router-C, and Router_D can run OSPF-enabled processes and establish 0SPF neighbor relationships. The IP address configuration of the interface between Router-A and Router_D conflicts.

In order to detect the conflict, the present invention adds a new type of Opaque LSA. Considering that an LSA with a type value less than or equal to 11 has been used, the new LSA can be set to a type with a type value greater than 11. Each device in the autonomous system, that is, the routers Router-A, Router-B, Router-C, and Router-D, each add an interface, and the interface is enabled in the process that supports the 0SPF protocol running on the device. , a TLV is added to identify the interface, and the LSA is generated when at least one interface is enabled in the process supporting the 0SPF protocol.

The structure of the LSA, as shown in Figure 7, can be based on the usual Opaque LSA structure, except that the type value is greater than 11. The opaque information Opaque Information item may include multiple TLVs, and may include all interface IP address information of devices in the autonomous system. The length of each interface IP address information is 8 bytes, including a 4-byte address and 4 words. The mask of the section.

Each time an interface is added to a device in an autonomous system, the above Opaque LSA is regenerated. The LSA can be flooded to all devices in the autonomous system.

Usually, the LSA is refreshed every 1800 seconds and flooded into the entire autonomous system.

In Figure 5, the Opaque Information of the Opaque LSA generated by Router-A The entry contains the interface address 1. 1. 1. 1, the mask length is 24 bits, and the mask value is 255. 255. 255. 0, the LSA is flooded to the routers Router-B, Router-C and Router-D. The device is configured to analyze the LSAs of the Opaque LSA, and determine whether the LSAs generated by the routers are generated based on the contents of the reported advertising routers. If not generated by itself, the IP address information of the interfaces in each TLV and the interface IP address of the device are taken. If the IP address information of the interface is the same as the IP address of the interface of the device, the system sends an alarm to the NMS and records the log.

Similarly, the Opaque LSA generated by the router Router-D is also sent to the routers Router-B, Router-C and Router-A, so that the routers Router-A and Router-D in Figure 5 will send out alarms and print log information. The alarm content and log information include the router ID of the conflicting device, the id of the 0SPF area. Therefore, according to the network management alarm and log information, the administrator can quickly correct and resolve the conflict. Embodiment 2 The IPv6 address conflict is detected by adding the 0SPFv3 Opaque LSA. Figure 6 shows an autonomous system in which a hypothetical IP address conflicts. The address is

IPv6 address, IGP selects 0SPF. The four routers Router_A, Router_B, Router-C, and Router-D can run the 0SPFv3 process to establish the 0SPFv3 neighbor relationship. The IP address configuration of the interface between Router-A and Router-D conflicts.

In order to detect the conflict, the present invention adds a new type of Opaque LSA for the 0SPv3, and the LSA is of a type with a type value greater than 11. Each device in the autonomous system adds one interface, and the interface runs on the device. When the process that supports the 0SPF protocol is enabled, a TLV is added to identify the interface. The LSA is generated when at least one interface is enabled in the process that supports the 0SPF protocol.

The structure of the Opaque LSA is as shown in Figure 8. The first three bits of the link state type LS Type are 010 bit strings, indicating that the flooding range is the entire autonomous system, and the link state LS type determined by other bits is greater than 11, The TLV contains all the interface IP address information of the devices in the autonomous system. The IPv6 address information of each interface is 20 bytes long and contains a 16-byte address prefix and a 4-byte prefix length.

In Figure 6, the TLVs entry of the Opaque LSA generated by the router Router-A contains the interface address 20: : 1, the address prefix specified by the prefix length is 64 bits, and the LSA is flooded to the routers Router-B, Router-C and Router_D. The device that receives the LSA parses and obtains the IP address information of the interface in the TLV, and judges according to the content of the analyzed Advertisement Router item. If the LSA is generated by itself, the IP address information of the interface in the TLV is compared with the IP address information of the interface of the device itself. If the IP address information of the interface in the TLV is equal to the IP address of the interface of the device itself. , then send an alarm to the network management system and record the log.

Similarly, the Opaque LSA generated by the router Router-D is also sent to the router.

Router-B, Router-C, and Router-A, so that Router-A and Router-D in Figure 6 will send out alarms and print log information. The alarm content and log information include the router id of the conflicting device, the 0SPF area, and so on. information. Therefore, according to the network management alarm and log information, the administrator can quickly correct and resolve the conflict. The third embodiment detects the IPv4 address conflict by adding the IS-IS IPv4 TLV. In the case of an autonomous system where the assumed IP addresses conflict, as shown in Figure 5, the address is an IPv4 address and the IGP is IS_IS. The four routers Router-A, Router_B, Router-C, and Router-D can run IS-IS processes to establish IS-IS neighbor relationships. The IP address configuration of the interface between Router-A and Router-D conflicts.

In order to detect the conflict, the present invention adds a new TLV, and the name can be InterfaceAddressTLV, and its structure is as shown in FIG. 9. The type of the TLV can be freely selected without being occupied by other protocols, and the TLV can be selected through this TLV. Add all IPv4 host addresses on the interfaces of all devices in the AS to the LSP.

The TLV is constructed when at least one interface of the device in the autonomous system is enabled to support the IS-IS protocol. Each additional interface of the device in the autonomous system adds an interface IP address information to the TLV accordingly.

The value in the InterfaceAddressTLV occupies 8 bytes, where the address occupies 4 bytes and the mask occupies 4 bytes. An IPv4 address is added to the InterfaceAddressTLV and the LSP is refreshed. The LSP is flooded to all devices in the AS.

In Figure 5, the InterfaceAddressTLV in the LSP generated by Router-A contains the IP address of the interface. 1. 1. 1. The mask is occupied by 24 bits. The LSP is flooded to Router-B, Router-C, and Router_D. The device that receives the LSP resolves and obtains the IP address information of the interface in the TLV. The information is compared with the IP address information of the interface of the device. If the IP address information of an interface in the TLV is equal to the IP address of the interface of the device itself, Further compare whether the publisher of the LSP establishes an adjacency relationship with the locality, and if not, sends the network management system to the network management system. Alarm, and log.

Similarly, the Opaque LSA generated by the router Router-D is also sent to the routers Router-B, Router-C and Router-A, so that the routers Router-A and Router-D in Figure 5 will send out alarms and print log information. The alarm content and log information include the system ID of the conflicting device, the IS_IS layer level, and the area address. Therefore, the administrator can quickly correct and resolve conflicts based on network management alarms and log information. Embodiment 4 The IPv6 address conflict is detected by adding an IS-IS IPv6 TLV.

An autonomous system in which a hypothetical IP address conflicts, as shown in Figure 6, where the address is an IPv6 address and the IGP uses IS_IS. Four routers Router_A, Router-B, Router-C, and Router-D can run IS-IS processes to establish IS-IS neighbor relationships. The IP address configuration of the interface between Router-A and Router-D conflicts.

In order to detect the conflict, the present invention adds a new TLV, and the name can be Ipv6InterfaceAddressTLV, and its structure is as shown in FIG. 10, and the type of the TLV can be freely selected without being occupied by other protocols, and the TLV can be selected through this TLV. Add all IPv6 host addresses on the interfaces of all devices to the LSP.

The value of the Ipv6InterfaceAddressTLV is composed of an address prefix and a prefix length, where the prefix length occupies 1 byte, and the number of bytes occupied by the address prefix is determined by the value of the prefix length. Each IPv6 address is added to the interface of the device in the autonomous system. An IPv6 address is added to the Ipv6InterfaceAddressTLV and the LSP is refreshed. The LSP is flooded to all devices in the AS.

In Figure 6, the Ipv6InterfaceAddressTLV in the LSP generated by the router Router-A contains the interface address 20:1, and the address prefix specified by the prefix length is 64 bits. The LSP is flooded to the routers Router-B, Router-C, and Router_D. The device that receives the LSP parses and obtains the IP address information of the interface in the TLV. The information is compared with the IP address information of the interface of the device. If the IP address information of an interface in the TLV is the same as the IP address of the interface on the device, the publisher of the LSP is compared with the local device. , then issue an alarm to the network management system and record the log.

Similarly, the Opaque LSA generated by the router Router-D is also sent to the router. On Router-B, Router-C, and Router-A, Router-A and Router-D in Figure 6 both send alarms and print log information. The alarm content and log information contain the system id of the conflicting device and the IS_IS Level. Information such as the area address. Therefore, according to the network management alarm and log information, the administrator can quickly correct and resolve the conflict. The fifth embodiment detects an IPv4 address conflict by using an existing IS-IS IPv4 TLV. A scenario in which an assumed IP address conflicts, as shown in FIG. 5, where the address is an IPv4 address, and the IGP selects IS_IS. The four routers Router-A, Router-B, Router-C, and Router-D can run IS-IS processes to establish IS-IS neighbor relationships. The IP address configuration of the interface between Router-A and Router-D conflicts.

In order to detect the conflict, the present invention adopts the TLV, IP Interface Address (No. 132) defined in the RFC (Request For Comments Request for Comments) 1195, and its structure is as shown in the figure.

11 is shown.

Although the address of the interface can be carried by this TLV, since there is no mask part, the address information carried in the TLV can only contain the address part.

An interface can be added to the TLV 132 and the LSP can be refreshed. The LSP can be sent to all devices in the AS.

In Figure 5, the 132 TLV in the LSP generated by the router Router-A contains the interface address 1. 1. 1. 1, the mask length is 24 bits, and the LSP is flooded to the routers Router-B, Router-C, and Router- D. The device that receives the LSP parses and obtains the IP address information of the interface in the TLV. The information is compared with the IP address information of the interface of the device. If the IP address information of the interface in the TLV is the same as the IP address of the interface on the device, the publisher of the LSP is compared with the local device. , then send an alarm to the network management system, and record the records.

Similarly, the Opaque LSA generated by the router Router-D is also sent to the routers Router-B, Router-C and Router-A, so that the routers Router-A and Router-D in Figure 5 will send out alarms and print log information. The alarm content and log information include the system id (system number) of the conflicting device, the IS_IS Level, and the area address. Therefore, according to the network management alarm and log information, the administrator can quickly correct and resolve the conflict. Embodiment 6 detects an IPv6 address conflict by using an existing IS-IS IPv6 TLV. An autonomous system in which a hypothetical IP address conflicts, as shown in Figure 6, where the address complies with IPv6, and IGP selects IS-ISo four routers Router-A, Router-B, Router-C, and Router-D to run support. The IS-IS process establishes an IS-IS neighbor relationship. The IP address configuration of the interface between Router_A and Router-D conflicts.

In order to detect the collision, the present invention adopts the TLV defined in RFC5308, IP Interface.

Address (No. 232), its structure is shown in Figure 12.

Although the TLV can be used to carry the interface address information, since there is no prefix length part, the address information carried in the TLV can only contain the address prefix part.

Each additional IPv6 address is added to the interface of the device in the autonomous system. You can add an address to the TLV 232 and refresh the LSP. The LSP is flooded to all devices in the AS.

In Figure 6, the 232 TLV in the LSP generated by the router Router-A contains the interface address 20: : 1, the address prefix specified by the prefix length is 64 bits, and the LSP is flooded to the routers Router-B, Router-C, and Router_D. . The device receiving the LSP parses and obtains the IP address information of the interface in the TLV. The information is compared with the IP address information of the interface of the device. If the IP address information of an interface in the TLV is the same as the IP address of the interface on the device, the publisher of the LSP is compared with the local device. , then issue an alarm to the network management system and record the log.

Similarly, the Opaque LSA generated by the router Router-D is also flooded to Router-B, Router-C, and Router-A. The routers Router-A and Router-D in Figure 6 both send alarms and print log information. The alarm content and log information include the system id of the conflicting device, the IS_IS Level, and the area address. Therefore, according to the network management alarm and log information, the administrator can quickly correct and resolve the conflict. Compared with the prior art, the method and the device for detecting the IP address conflict in the autonomous system of the present invention carry the IP address information of the interface of the device by adding the opaque LSA type, and send the LSA to the IGP. To all devices in the autonomous system; or, in the case of IS-IS, the LSP that carries the IP address information of the interface of the device is configured, and the LSP is sent to all devices in the autonomous system; In contrast, an address conflict can be detected, so as to quickly detect the IP address conflict of the entire network. Those of ordinary skill in the art will appreciate that all or part of the steps in implementing the above embodiments are The related hardware may be instructed by a program, and the program may be stored in a computer readable storage medium, which may be a ROM/RAM, a magnetic disk or an optical disk. The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed by the present invention. Alternatives are intended to be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

Rights request

A method for detecting an IP address conflict of an Internet protocol in an autonomous system, the method comprising:

The method according to claim 1, wherein the internal gateway protocol is an OSSPF protocol, and the device in the autonomous system runs a process that supports the 0SPF protocol, and the packet includes a link state advertisement LSA.

The method according to claim 2, wherein the constructing process of the LSA specifically includes: constructing a type length value TLV carrying the interface IP address information of the device, and constructing the LSA by using the TLV.

The method according to claim 3, wherein the LSA is generated when at least one interface of the device in the autonomous system is enabled to the process supporting the 0SPF protocol, and the intra-autonomous system Each additional interface of the device will be correspondingly added with a TLV to carry the interface IP address information of the device.

The method according to claim 1, wherein the internal gateway protocol is an IS-IS protocol, and the device in the autonomous system runs a process supporting the IS-IS protocol, and the packet includes a link. Status packet LSP.

The method according to claim 5, wherein the constructing process of the LSP specifically includes: constructing a type length value TLV carrying the IP address information of the interface of the device, and constructing the LSP by using the TLV.

The method according to claim 6, wherein the TLV is constructed when at least one interface of the device in the autonomous system is enabled to the process supporting the IS-IS protocol, the autonomous system Each interface added to the device will add an interface IP address information to the TLV accordingly.

The method according to any one of claims 1 to 7, wherein the indication by the device in the autonomous system that an IP address conflict occurs in the autonomous system comprises: Give an alarm to the network management system;

Log on the device; or

Give an alarm to the NMS and log the device.

9. A device capable of detecting an Internet Protocol IP address conflict in an autonomous system, the method comprising:

The device according to claim 9, wherein the first module specifically includes:

TLV;

The second unit constructs the message with the TLV.

The device according to claim 9 or 10, wherein the internal gateway protocol is an OSSPF protocol, and the device runs a process that supports the 0SPF protocol, and the packet includes a link state advertisement LSA.

The apparatus according to claim 11, wherein the LSA is generated when at least one interface of the device is enabled to the process supporting the 0SPF protocol, and each additional interface of the device will be correspondingly Add a TLV to carry the interface IP address information of the device.

The method according to claim 9 or 10, wherein the internal gateway protocol is an IS-IS protocol, the device runs a process that supports the IS-IS protocol, and the packet includes a link status report. LSP.

The method according to claim 13, wherein the TLV is constructed when at least one interface of the device is enabled to the process supporting the IS-IS protocol, and each interface of the device is added. Correspondingly, an interface IP address information is added to the TLV.