CN109218198B - Data interaction method, device, MPLS network system and storage medium - Google Patents

Data interaction method, device, MPLS network system and storage medium Download PDF

Info

Publication number
CN109218198B
CN109218198B CN201811176842.7A CN201811176842A CN109218198B CN 109218198 B CN109218198 B CN 109218198B CN 201811176842 A CN201811176842 A CN 201811176842A CN 109218198 B CN109218198 B CN 109218198B
Authority
CN
China
Prior art keywords
local address
link local
ipv6 link
notified
address
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201811176842.7A
Other languages
Chinese (zh)
Other versions
CN109218198A (en
Inventor
黄浩
秦川
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Maipu Communication Technology Co Ltd
Original Assignee
Maipu Communication Technology Co Ltd
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 Maipu Communication Technology Co Ltd filed Critical Maipu Communication Technology Co Ltd
Priority to CN201811176842.7A priority Critical patent/CN109218198B/en
Publication of CN109218198A publication Critical patent/CN109218198A/en
Application granted granted Critical
Publication of CN109218198B publication Critical patent/CN109218198B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • 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/5053—Lease time; Renewal aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/659—Internet protocol version 6 [IPv6] addresses

Abstract

The embodiment of the application provides a data interaction method, a data interaction device, an MPLS network system and a storage medium, and relates to the technical field of communication. The method comprises the following steps: after the LDP session is established, traversing all local links to connect the interfaces of UP, acquiring and counting all IPv6 link local addresses of the interfaces of all links UP, and storing the count value of each IPv6 link local address; when determining that the acquired IPv6 link local address is not sent to the opposite terminal equipment of the LDP session, generating an LDP address notification message containing an IPv6 link local address and sending the LDP address notification message to the opposite terminal equipment, and recording the IPv6 link local address notified by the LDP session; when the interface acquiring the new link UP is configured with the notified IPv6 link local address, the count value of the notified IPv6 link local address is updated. The sending quantity of the information is reduced, and the load of the equipment is reduced; and the control logic completely meets the protocol specification, and the compatibility problem caused by different equipment manufacturers can be avoided, so that the condition of equipment error is avoided.

Description

Data interaction method, device, MPLS network system and storage medium
Technical Field
The present application relates to the field of communications technologies, and in particular, to a data interaction method, an apparatus, an MPLS network system, and a storage medium.
Background
In an MPLS network system (Multi-Protocol Label Switching), LDP (Label Distribution Protocol) is a common Protocol. When the device establishes the LDP session based on the LDP protocol, the device can intercommunicate IP addresses, so that the device can determine the upstream and downstream relation when the device distributes labels based on the LDP protocol.
However, when communicating IP addresses, since a plurality of same IPv6(Internet Protocol version 6) Local Link addresses can be configured on a device, in the prior art, each time the device configures an IPv6 Link Local (IPv6 Link Local) address or each time deletes a configured IPv6 Link Local address, the device needs to inform other devices of recording or deleting the recording in real time, which results in a lot of messages communicated between the two devices and increases the redundancy load of the device. However, in order to reduce the load of the device, in the prior art, the device may notify the other devices of the IPv6 link local address configured each time for recording, but only when all the IPv6 link local addresses are configured to be deleted, the device notifies the other devices to delete all the records. Although the method reduces the information amount and reduces the equipment load, if compatibility of other equipment and the equipment is in problem, the other equipment cannot delete all records at one time based on the equipment, thereby causing equipment errors.
Disclosure of Invention
The application provides a data interaction method, a data interaction device, an MPLS network system and a storage medium. The problem of equipment error caused by compatibility can be avoided while the equipment load is effectively reduced.
The embodiment of the application is realized by the following steps:
in a first aspect, an embodiment of the present application provides a data interaction method, where the method includes: after the LDP session is established, traversing all local links to connect the interfaces of UP, acquiring and counting all IPv6 link local addresses of the interfaces of all links UP, and storing the count value of each IPv6 link local address; the count value of each IPv6 link local address is used for storing the number of interfaces of the link UP configuring each IPv6 link local address; when determining that the acquired IPv6 link local address is not sent to the opposite terminal equipment of the LDP session, generating an LDP address notification message containing the IPv6 link local address and sending the LDP address notification message to the opposite terminal equipment, and recording the IPv6 link local address notified by the LDP session; and updating the count value of the notified IPv6 link local address when the interface acquiring the new link UP is configured with the notified IPv6 link local address.
With reference to the first aspect, in some optional implementations, the method further includes: when the link where the interface configured with the notified IPv6 link local address is located is disconnected, or the interface configured with the notified IPv6 link local address deletes the notified IPv6 link local address, updating the count value of the notified IPv6 link local address; when the notified IPv6 link local address count value is determined to become 0, deleting the notified IPv6 link local address recorded in the LDP session, and generating and sending a LDP address withdrawal message to the opposite terminal device, wherein the LDP address withdrawal message is used for indicating the opposite terminal device to delete the notified IPv6 link local address.
With reference to the first aspect, in some optional implementations, the method further includes: when an interface of a new link UP is acquired to be configured with an uninformed IPv6 link local address, the count value of the uninformed IPv6 link local address is saved to be 1, an LDP address notification message containing the uninformed IPv6 link local address is generated and sent to the opposite terminal equipment, and the uninformed IPv6 link local address is recorded as the IPv6 link local address notified by the LDP session.
With reference to the first aspect, in some optional implementations, when the interface that acquires the new link UP is configured with the notified IPv6 link local address, updating a count value of the notified IPv6 link local address includes: when the notified IPv6 link local address is configured on the interface for acquiring the new link UP, adding 1 to the count value of the notified IPv6 link local address; when the link where the interface configured with the notified IPv6 link local address is located is disconnected, or the interface configured with the notified IPv6 link local address deletes the notified IPv6 link local address, updating the count value of the notified IPv6 link local address, including: when the link where the interface configuring the notified IPv6 link local address is located is disconnected, subtracting 1 from the count value of the notified IPv6 link local address; when the interface configuring the informed IPv6 link local address deletes the informed IPv6 link local address, the count value of the informed IPv6 link local address is reduced by 1.
In a second aspect, an embodiment of the present application provides a data interaction apparatus, where the apparatus includes: the counting determination module is used for traversing all local links to connect the interfaces of the UP after the LDP session is established, acquiring all IPv6 link local addresses of the interfaces of all links of the UP, counting and storing the count value of each IPv6 link local address; the count value of each IPv6 link local address is used for storing the interface number of the link UP configuring each IPv6 link local address. A first address recording module, configured to, when it is determined that the obtained IPv6 link local address has not been sent to the peer device of the LDP session, generate a LDP address notification message including the IPv6 link local address, send the LDP address notification message to the peer device, and record the IPv6 link local address notified by the LDP session. And the first count updating module is used for updating the count value of the notified IPv6 link local address when the notified IPv6 link local address is configured on the interface acquiring the new link UP.
With reference to the second aspect, in some optional implementations, the apparatus further includes: and the second count updating module is used for updating the count value of the notified IPv6 link local address when the link where the interface configuring the notified IPv6 link local address is located is disconnected or the interface configuring the notified IPv6 link local address deletes the notified IPv6 link local address. A revocation message sending module, configured to, when it is determined that the count value of the notified IPv6 link local address becomes 0, delete the notified IPv6 link local address recorded in the LDP session, generate a LDP address revocation message, and send the LDP address revocation message to the peer device, where the LDP address revocation message is used to instruct the peer device to delete the notified IPv6 link local address.
With reference to the second aspect, in some optional implementations, the apparatus further includes: a second address recording module, configured to, when an uninformed IPv6 link local address is configured on an interface where a new link UP is acquired, save a count value of the uninformed IPv6 link local address to 1, generate an LDP address notification message including the uninformed IPv6 link local address, send the LDP address notification message to the peer device, and record the uninformed IPv6 link local address as the IPv6 link local address notified by the LDP session.
With reference to the second aspect, in some optional implementations, the first count updating module is further configured to, when the interface that acquires the new link UP is configured with the notified IPv6 link local address, add 1 to a count value of the notified IPv6 link local address; the second count updating module is further configured to subtract 1 from the count value of the notified IPv6 link local address when the link where the interface configuring the notified IPv6 link local address is located is disconnected; when the interface configuring the informed IPv6 link local address deletes the informed IPv6 link local address, the count value of the informed IPv6 link local address is reduced by 1.
In a third aspect, an embodiment of the present application provides an MPLS network system, where the MPLS network system includes: each device of the at least two devices establishes an LDP session with other opposite-end devices of the at least two devices; and each device is used for executing the data interaction method according to the first aspect and any implementation manner of the first aspect.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having computer-executable non-volatile program code, where the program code causes the computer to execute the data interaction method according to the first aspect and any implementation manner of the first aspect.
The beneficial effects of the embodiment of the application include:
after the device establishes the LDP session with the opposite device, the device can obtain and store the number of interfaces of the link UP of each IPv6 link local address. Then the device generates an LDP address notification message containing the IPv6 link local address and sends the LDP address notification message to the peer device, and when the notified IPv6 link local address is configured on the interface of the new link UP, the device can update the count value of the notified IPv6 link local address by itself without notifying the peer device of a retransmission message. Compared with the prior art, the device automatically updates the count value without informing the opposite terminal device, so that the sending amount of information is reduced, and the load of the device is reduced; secondly, because the sent LDP address notification message records each IPv6 link local address once for informing the opposite terminal device, the control logic completely meets the protocol regulation, and the compatibility problem caused by different device manufacturers can be avoided, thereby avoiding the occurrence of device errors.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a block diagram illustrating a structure of an MPLS network system according to a first embodiment of the present application;
FIG. 2 is a flow chart of a data interaction method according to a second embodiment of the present application;
fig. 3 is a schematic diagram illustrating an application scenario of a data interaction method according to a third embodiment of the present application;
fig. 4 shows a block diagram of a data interaction device according to a third embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. The terms "first," "second," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
First embodiment
Referring to fig. 1, an embodiment of the present application provides an MPLS network system 10, where the MPLS network system 10 includes: at least two devices 11.
Each device 11 of the at least two devices 11 may be a network device such as a switch, bridge, router, or gateway. Each device 11 of the at least two devices 11 may establish an LDP session based on the LDP protocol with a peer device 11 of each device of the at least two devices 11. The LDP session established between each device 11 and the peer device 11 may be directly or indirectly connected between each device 11 and the peer device 11, for example, the LDP session established between the device a and the device B may be that the port 1 of the device a is connected to the port 2 of the device B, or may be that the port 1 of the device a is connected to the device C, and the device C is connected to the port 2 of the device B.
In this embodiment, each device 11 may enable each device 11 to execute the data interaction method based on the LDP session established with the peer device 11. For clarity of description to distinguish each device 11 in the MPLS network system 10, each device 11 performing the data interaction method may be referred to as the present device 11, but is not limited thereto.
The data interaction method will be described in detail below by taking an example in which any one device 11 of the at least two devices 11 executes the data interaction method.
Second embodiment
The present embodiments provide a data interaction method, it should be noted that the steps illustrated in the flowchart of the drawings may be performed in a computer system such as a set of computer executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here. The present embodiment will be described in detail below.
Referring to fig. 2, an embodiment of the present application provides a data interaction method, where the data interaction method is applied to any one of at least two devices in an MPLS network system, and the data interaction method includes: step S100, step S200, step S300, step S400, and step S500.
Step S100: after the LDP session is established, traversing all local links to connect the interfaces of UP, acquiring and counting all IPv6 link local addresses of the interfaces of all links UP, and storing the count value of each IPv6 link local address; the count value of each IPv6 link local address is used for storing the interface number of the link UP configuring each IPv6 link local address.
Step S200: and when determining that the acquired IPv6 link local address is not sent to the opposite terminal equipment of the LDP session, generating an LDP address notification message containing the IPv6 link local address, sending the LDP address notification message to the opposite terminal equipment, and recording the IPv6 link local address notified by the LDP session.
Step S300: and updating the count value of the notified IPv6 link local address when the interface acquiring the new link UP is configured with the notified IPv6 link local address.
Step S400: and updating the count value of the notified IPv6 link local address when the link where the interface configuring the notified IPv6 link local address is located is disconnected or the interface configuring the notified IPv6 link local address deletes the notified IPv6 link local address.
Step S500: when the notified IPv6 link local address count value is determined to become 0, deleting the notified IPv6 link local address recorded in the LDP session, and generating and sending a LDP address withdrawal message to the opposite terminal device, wherein the LDP address withdrawal message is used for indicating the opposite terminal device to delete the notified IPv6 link local address.
The flow of the data interaction method will be described in detail below with reference to fig. 2 and 3.
Step S100: after the LDP session is established, traversing all local links to connect the interfaces of UP, acquiring and counting all IPv6 link local addresses of the interfaces of all links UP, and storing the count value of each IPv6 link local address; the count value of each IPv6 link local address is used for storing the interface number of the link UP configuring each IPv6 link local address.
After the device and the opposite terminal device establish the LDP session based on the LDP protocol, the device may traverse all local interfaces where the link communicates UP, where the interface where the link communicates UP may indicate that the interface of UP is connected with the link and is in a normal use state. Thus, through traversal, the device can obtain and count all IPv6 link local addresses of the interfaces of the link UP, and can obtain and store a count value of each IPv6 link local address, wherein the count value of each IPv6 link local address is used for storing the number of interfaces of the link UP configuring each IPv6 link local address.
It is understood that after the device establishes the LDP session, the device may perform a traversal to obtain and store the latest count value of each IPv6 link-local address.
Step S200: and when determining that the acquired IPv6 link local address is not sent to the opposite terminal equipment of the LDP session, generating an LDP address notification message containing the IPv6 link local address, sending the LDP address notification message to the opposite terminal equipment, and recording the IPv6 link local address notified by the LDP session.
After the device and the opposite terminal device establish the LDP session based on the LDP protocol, the device and the opposite terminal device can communicate with each other with IP based on the LDP protocol, so that when labels are subsequently distributed to the device and the opposite terminal device based on the LDP protocol, the device can determine the upstream and downstream relationship between the device and the opposite terminal device in communication based on the own IP and the obtained IP of the opposite terminal device, and meanwhile, the opposite terminal device can determine the upstream and downstream relationship between the device and the device in communication based on the own IP and the obtained IP of the device.
For the device, after the LDP session is established, the device has not sent the obtained IPv6 link local address to the peer device that established the LDP session. Then, the device may send the IPv6 link-local address obtained through traversal to the peer device, so as to record the obtained IPv6 link-local address as the IPv6 link-local address notified by the LDP session.
Optionally, the device may generate, based on a LDP protocol, a LDP address notification message including the obtained IPv6 link local address, and send the LDP address notification message to the peer device. Thus, the device can record the obtained IPv6 link local address as the IPv6 link local address notified by the LDP session, and the peer device can record the IPv6 link local address of the device according to the LDP address notification message, and record the reference count of the device with respect to the IPv6 link local address as 1.
It can be understood that, after the obtained IPv6 link local address is sent to the peer device through the LDP address notification message, the count value of the obtained IPv6 link local address is still the count value determined through the previous traversal, for example, is 2 or 3, which is not necessarily 1 recorded on the peer device. However, in some cases, if the device is configured with an uninformed IPv6 link local address through traversal, when the interface that acquires the new link UP is configured with the uninformed IPv6 link local address, the uninformed IPv6 link local address may be configured on the interface of the new link UP for the first time, so the device may save the count value of the uninformed IPv6 link local address as 1, generate and send an LDP address notification message including the uninformed IPv6 link local address to the peer device, and record the uninformed IPv6 link local address as the IPv6 link local address notified by the LDP session.
The data interaction method of the present embodiment will be explained below by way of an example. Assume that the IPv6 link local address of this device a is FE 80: : 1313, the device a and the opposite terminal device B establish an LDP session based on the LDP protocol. Meanwhile, the interface AG1 of the device a opens and establishes a communication link with the interface BG1 of the opposite device B, and the IPv6 link local address of the AG1 interface of the communication link UP configured by the device a is FE 80: : 1313. since the device a configures the uninformed IPv6 link local address for the first time as FE 80: : 1313, so that device a may send the un-notified FE 80: : 1313, stores the count value of the IPv6 link local address as 1, generates an LDP address notification message including the unreformed IPv6 link local address, and sends the LDP address notification message to the peer apparatus B. At the same time, the device a also configures the uninformed IPv6 link-local address to be FE80 based on the interface AG 1: : 1313, and the number of references of the IPv6 link local address of itself is updated from 0 by 1, so that the updated value of the reference count is 1.
Step S300: and updating the count value of the notified IPv6 link local address when the interface acquiring the new link UP is configured with the notified IPv6 link local address.
Based on the LDP protocol, the device can re-configure the IPv6 link local address on the interfaces where multiple links communicate with UP, so that an interface that communicates with UP of one link while configuring an IPv6 link local address can be considered as the IPv6 link local address being referred to once. Then the device can record the number of references of the IPv6 link local address of the device in real time in order to clearly know how many times the IPv6 link local address is referenced.
Optionally, in a possible case, when an interface on the device with the new link UP is configured with the notified IPv6 link local address for communication with other devices including the peer device, the device adds 1 to the count value of the notified IPv6 link local address, and obtains an updated value of the reference count.
Step S400: and updating the count value of the notified IPv6 link local address when the link where the interface configuring the notified IPv6 link local address is located is disconnected or the interface configuring the notified IPv6 link local address deletes the notified IPv6 link local address.
For the device to record the number of references of its own IPv6 link local address in real time, in another possible case, when the link where the interface configured with the notified IPv6 link local address is located on the device is disconnected, the device may subtract 1 from the count value of the notified IPv6 link local address, and obtain an updated value of the reference count. Or, when the interface configured with the notified IPv6 link local address deletes the notified IPv6 link local address, the device may also subtract 1 from the count value of the notified IPv6 link local address, and obtain an updated value of the reference count. The interface configured with the notified IPv6 link local address may be an interface configured by the device for communicating with other devices including a peer device.
Continuing with the previous assumption, the interface AG2 of the device a opens and establishes a communication link with the interface CG1 of the other device C, and the device a also configures the IPv6 link local address of the interface AG2 as FE 80: : 1313. in this way, since the IPv6 link local address is configured again on the interface AG2, the present device a updates the number of references of its own IPv6 link local address from 1 by 1, so that the updated value of the reference count is 2. And, the interface AG3 of the device a opens and establishes a communication link with the interface DG1 of the other device D, and the device a also configures the IPv6 link local address of the interface AG3 as FE 80: : 1313. thus, since the IPv6 link local address is again configured on the interface AG3, the present device a updates the number of references of its own IPv6 link local address from 2 to 1, so that the updated value of the reference count is 3.
The device a closes the interface AG2, so that the link established with the interface CG1 of the other device C and in which the interface AG2 is located is disconnected, and thus the device a sets the configured IPv6 link local address of the link to be FE 80: : 1313 are deleted. Therefore, since the IPv6 link local address is configured to be deleted, the present device a updates the number of references of its IPv6 link local address from 3 by 1, so that the updated value of the reference count is 2. And, the device a further converts the FE80 configured on the interface AG3 into: : 1313 IPv6 link local address deletion. Therefore, since the IPv6 link local address is configured to be deleted again, the present device a updates the number of references of its IPv6 link local address from 2 to 1, so that the updated value of the reference count is 1.
And the device a closes the interface AG1, so that the communication link where the interface AG1 is located, which is established with the interface BG1 of the peer device B, is disconnected, and thus the device a also sets the IPv6 link local address configured by the interface AG1 to be FE 80: : 1313 are deleted. Therefore, since the IPv6 link local address is configured to be deleted again, this device a updates the number of references of its IPv6 link local address from 1 by 1, so that the updated value of the reference count is 0.
It is to be understood that the present apparatus may perform step S300 when the updated value of the reference count is 0.
Step S500: when the notified IPv6 link local address count value is determined to become 0, deleting the notified IPv6 link local address recorded in the LDP session, and generating and sending a LDP address withdrawal message to the opposite terminal device, wherein the LDP address withdrawal message is used for indicating the opposite terminal device to delete the notified IPv6 link local address. .
When the device determines that the updated value of the reference count is 0, the device is equivalent to determining that the IPv6 link local address of the device is not configured to be used any more. Since the device determines that the device does not use the IPv6 link local address any more, the device may delete the notified IPv6 link local address recorded in the established LDP session, and the device may further notify the peer device to delete the stored notified IPv6 link local address of the device.
In this embodiment, before the device notifies the peer device, the device needs to determine whether it is necessary to notify the peer device to delete the notified IPv6 link local address of the device, that is, the device may determine whether an LDP session is established with the peer device.
If the device determines that the opposite terminal device does not establish the LDP session any more, the device does not need to inform the opposite terminal device to delete the stored IPv6 link local address of the device, but can wait for the opposite terminal device to delete the address according to its own program. Based on this, the device can avoid generating the LDP address withdrawal message.
If the device determines that the opposite device also establishes the LDP session, it needs to inform the opposite device to delete the stored IPv6 link-local address of the device. Therefore, the device can generate a LDP address withdrawal message based on the LDP protocol, and send the LDP address withdrawal message to the peer device. And the opposite terminal equipment updates the stored reference count of the informed IPv6 link local address from 1 to 0 according to the indication of the obtained LDP address withdrawal message, and deletes the informed IPv6 link local address.
Third embodiment
Referring to fig. 4, an embodiment of the present application provides a data interaction apparatus 100, where the data interaction apparatus 100 is applied to any one of at least two devices of an MPLS network system, and the data interaction apparatus 100 includes:
the counting determination module 110 is configured to traverse all local links to connect UP interfaces after establishing the LDP session, obtain and count all IPv6 link local addresses of all link UP interfaces, and store a count value of each IPv6 link local address; the count value of each IPv6 link local address is used for storing the interface number of the link UP configuring each IPv6 link local address.
A first address recording module 120, configured to, when it is determined that the obtained IPv6 link local address has not been sent to a peer device of the LDP session, generate an LDP address notification message including the IPv6 link local address, send the LDP address notification message to the peer device, and record the IPv6 link local address notified by the LDP session.
A first count updating module 130, configured to update a count value of the notified IPv6 link local address when the interface that acquires the new link UP is configured with the notified IPv6 link local address.
A second count updating module 140, configured to update the count value of the notified IPv6 link local address when a link where the interface configured with the notified IPv6 link local address is located is disconnected, or the interface configured with the notified IPv6 link local address deletes the notified IPv6 link local address.
A revocation message sending module 150, configured to, when it is determined that the count value of the notified IPv6 link local address becomes 0, delete the notified IPv6 link local address recorded in the LDP session, and generate and send a LDP address revocation message to the peer device, where the LDP address revocation message is used to instruct the peer device to delete the notified IPv6 link local address
A second address recording module 160, configured to, when an interface that acquires a new link UP is configured with an unreformed IPv6 link local address, save a count value of the unreformed IPv6 link local address to 1, generate an LDP address notification message including the unreformed IPv6 link local address, send the LDP address notification message to the peer device, and record the unreformed IPv6 link local address as the IPv6 link local address notified by the LDP session.
Optionally, the first count updating module 130 is further configured to, when the interface that acquires the new link UP is configured with the notified IPv6 link local address, add 1 to the count value of the notified IPv6 link local address.
The second count updating module 140 is further configured to, when a link where an interface configuring the notified IPv6 link local address is located is disconnected, subtract 1 from the count value of the notified IPv6 link local address; when the interface configuring the informed IPv6 link local address deletes the informed IPv6 link local address, the count value of the informed IPv6 link local address is reduced by 1.
It should be noted that, as those skilled in the art can clearly understand, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
In summary, the embodiments of the present application provide a data interaction method, an apparatus, an MPLS network system, and a storage medium. The method comprises the following steps: after the LDP session is established, traversing all local links to connect the interfaces of UP, acquiring and counting all IPv6 link local addresses of the interfaces of all links UP, and storing the count value of each IPv6 link local address; the count value of each IPv6 link local address is used for storing the interface number of the link UP configuring each IPv6 link local address; when determining that the acquired IPv6 link local address is not sent to the opposite terminal equipment of the LDP session, generating an LDP address notification message containing an IPv6 link local address and sending the LDP address notification message to the opposite terminal equipment, and recording the IPv6 link local address notified by the LDP session; when the interface acquiring the new link UP is configured with the notified IPv6 link local address, the count value of the notified IPv6 link local address is updated.
After the device establishes the LDP session with the opposite device, the device can obtain and store the number of interfaces of the link UP of each IPv6 link local address. Then the device generates an LDP address notification message containing the IPv6 link local address and sends the LDP address notification message to the peer device, and when the notified IPv6 link local address is configured on the interface of the new link UP, the device can update the count value of the notified IPv6 link local address by itself without notifying the peer device of a retransmission message. Compared with the prior art, the device automatically updates the count value without informing the opposite terminal device, so that the sending amount of information is reduced, and the load of the device is reduced; secondly, because the sent LDP address notification message records each IPv6 link local address once for informing the opposite terminal device, the control logic completely meets the protocol regulation, and the compatibility problem caused by different device manufacturers can be avoided, thereby avoiding the occurrence of device errors.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (6)

1. A method of data interaction, the method comprising:
after the LDP session is established, traversing all local links to connect the interfaces of UP, acquiring and counting all IPv6 link local addresses of the interfaces of all links UP, and storing the count value of each IPv6 link local address; the count value of each IPv6 link local address is used for storing the number of interfaces of the link UP configuring each IPv6 link local address;
when determining that the acquired IPv6 link local address is not sent to the opposite terminal equipment of the LDP session, generating an LDP address notification message containing the IPv6 link local address and sending the LDP address notification message to the opposite terminal equipment, and recording the IPv6 link local address notified by the LDP session;
when the notified IPv6 link local address is configured on the interface for acquiring the new link UP, updating the count value of the notified IPv6 link local address;
when an interface of a new link UP is acquired to be configured with an uninformed IPv6 link local address, the count value of the uninformed IPv6 link local address is saved to be 1, an LDP address notification message containing the uninformed IPv6 link local address is generated and sent to the opposite terminal equipment, and the uninformed IPv6 link local address is recorded as the IPv6 link local address notified by the LDP session;
when the link where the interface configured with the notified IPv6 link local address is located is disconnected, or the interface configured with the notified IPv6 link local address deletes the notified IPv6 link local address, updating the count value of the notified IPv6 link local address;
when the notified IPv6 link local address count value is determined to become 0, deleting the notified IPv6 link local address recorded in the LDP session, and generating and sending a LDP address withdrawal message to the opposite terminal device, wherein the LDP address withdrawal message is used for indicating the opposite terminal device to delete the notified IPv6 link local address.
2. The method according to claim 1, wherein updating the count value of the notified IPv6 link local address when the interface acquiring the new link UP is configured with the notified IPv6 link local address comprises:
when the notified IPv6 link local address is configured on the interface for acquiring the new link UP, adding 1 to the count value of the notified IPv6 link local address;
when the link where the interface configured with the notified IPv6 link local address is located is disconnected, or the interface configured with the notified IPv6 link local address deletes the notified IPv6 link local address, updating the count value of the notified IPv6 link local address, including:
when the link where the interface configuring the notified IPv6 link local address is located is disconnected, subtracting 1 from the count value of the notified IPv6 link local address;
when the interface configuring the informed IPv6 link local address deletes the informed IPv6 link local address, the count value of the informed IPv6 link local address is reduced by 1.
3. A data interaction apparatus, the apparatus comprising:
the counting determination module is used for traversing all local links to connect the interfaces of the UP after the LDP session is established, acquiring all IPv6 link local addresses of the interfaces of all links of the UP, counting and storing the count value of each IPv6 link local address; the count value of each IPv6 link local address is used for storing the number of interfaces of the link UP configuring each IPv6 link local address;
a first address recording module, configured to, when it is determined that the acquired IPv6 link local address has not been sent to an opposite end device of the LDP session, generate an LDP address notification message including the IPv6 link local address and send the LDP address notification message to the opposite end device, and record the IPv6 link local address notified by the LDP session;
a first count updating module, configured to update a count value of the notified IPv6 link local address when the notified IPv6 link local address is configured in an interface that acquires a new link UP;
a second address recording module, configured to, when an uninformed IPv6 link local address is configured on an interface where a new link UP is acquired, save a count value of the uninformed IPv6 link local address to 1, generate an LDP address notification message including the uninformed IPv6 link local address, send the LDP address notification message to the peer device, and record the uninformed IPv6 link local address as the IPv6 link local address notified by the LDP session.
A second count updating module, configured to update a count value of the notified IPv6 link local address when a link where the interface configured with the notified IPv6 link local address is located is disconnected, or the interface configured with the notified IPv6 link local address deletes the notified IPv6 link local address;
a revocation message sending module, configured to, when it is determined that the count value of the notified IPv6 link local address becomes 0, delete the notified IPv6 link local address recorded in the LDP session, generate a LDP address revocation message, and send the LDP address revocation message to the peer device, where the LDP address revocation message is used to instruct the peer device to delete the notified IPv6 link local address.
4. The data interaction device of claim 3,
the first count updating module is further configured to, when the notified IPv6 link local address is configured in the interface where the new link UP is acquired, add 1 to the count value of the notified IPv6 link local address;
the second count updating module is further configured to subtract 1 from the count value of the notified IPv6 link local address when the link where the interface configuring the notified IPv6 link local address is located is disconnected; when the interface configuring the informed IPv6 link local address deletes the informed IPv6 link local address, the count value of the informed IPv6 link local address is reduced by 1.
5. An MPLS network system, comprising:
each device of the at least two devices establishes an LDP session with other opposite-end devices of the at least two devices; and each device for performing the data interaction method of any one of claims 1-2.
6. A computer-readable storage medium having computer-executable non-volatile program code, the program code causing the computer to perform the data interaction method of any one of claims 1-2.
CN201811176842.7A 2018-10-09 2018-10-09 Data interaction method, device, MPLS network system and storage medium Active CN109218198B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811176842.7A CN109218198B (en) 2018-10-09 2018-10-09 Data interaction method, device, MPLS network system and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811176842.7A CN109218198B (en) 2018-10-09 2018-10-09 Data interaction method, device, MPLS network system and storage medium

Publications (2)

Publication Number Publication Date
CN109218198A CN109218198A (en) 2019-01-15
CN109218198B true CN109218198B (en) 2021-03-26

Family

ID=64982898

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811176842.7A Active CN109218198B (en) 2018-10-09 2018-10-09 Data interaction method, device, MPLS network system and storage medium

Country Status (1)

Country Link
CN (1) CN109218198B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102035739A (en) * 2010-12-14 2011-04-27 北京星网锐捷网络技术有限公司 Notification method and device for interface address and routing equipment
CN102136957A (en) * 2010-01-25 2011-07-27 华为技术有限公司 Label switched path monitoring realization method, device and system
CN103227843A (en) * 2012-08-31 2013-07-31 杭州华三通信技术有限公司 Physical link address management method and device
CN107888497A (en) * 2016-09-30 2018-04-06 丛林网络公司 Communication means, the network equipment and computer-readable recording medium
CN108521336A (en) * 2018-03-05 2018-09-11 烽火通信科技股份有限公司 A kind of method and device for controlling routing networking IP address conflict

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2842381B1 (en) * 2002-07-12 2006-03-03 Webdyn METHOD AND DEVICE FOR CONNECTING AN ELECTRONIC SYSTEM THROUGH A PROVIDER OF ACCESS TO A COMMUNICATION NETWORK
CN1302646C (en) * 2003-06-24 2007-02-28 华为技术有限公司 Port based MAC address quantity statistical method and apparatus thereof
CN101316236B (en) * 2008-07-23 2010-09-22 杭州华三通信技术有限公司 Vrrp backup group load sharing method and router
CN101465859B (en) * 2009-01-13 2012-09-26 中兴通讯股份有限公司 Method and device for triggering main and standby interface board inverse switch
CN101557343B (en) * 2009-04-03 2011-06-08 联想天工网络(深圳)有限公司 Detecting and protecting method of double-layer loop in VRRP topological network
US20100329258A1 (en) * 2009-06-30 2010-12-30 Alcatel-Lucent Usa Inc. Dynamically enabling mpls stations and ports using an arp database
CN101621550B (en) * 2009-08-14 2012-12-12 杭州华三通信技术有限公司 Method and device for recycling MAC address in VPLS
CN101917324B (en) * 2010-08-25 2012-06-27 北京星网锐捷网络技术有限公司 Communication method, device and equipment for two-layer virtual private network
CN103997422B (en) * 2014-05-05 2019-06-28 大唐移动通信设备有限公司 A kind of fault handling method and device of IP interface board
CN104468365B (en) * 2014-07-09 2017-08-08 北京东土科技股份有限公司 A kind of method, system and device for obtaining equipment room topological connection relation
CN106254245A (en) * 2016-07-29 2016-12-21 杭州迪普科技有限公司 A kind of method and device managing list item

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102136957A (en) * 2010-01-25 2011-07-27 华为技术有限公司 Label switched path monitoring realization method, device and system
CN102035739A (en) * 2010-12-14 2011-04-27 北京星网锐捷网络技术有限公司 Notification method and device for interface address and routing equipment
CN103227843A (en) * 2012-08-31 2013-07-31 杭州华三通信技术有限公司 Physical link address management method and device
CN107888497A (en) * 2016-09-30 2018-04-06 丛林网络公司 Communication means, the network equipment and computer-readable recording medium
CN108521336A (en) * 2018-03-05 2018-09-11 烽火通信科技股份有限公司 A kind of method and device for controlling routing networking IP address conflict

Also Published As

Publication number Publication date
CN109218198A (en) 2019-01-15

Similar Documents

Publication Publication Date Title
CN105281947A (en) Techniques for transforming legacy networks into SDN-enabled networks
CN110580256A (en) Method, device and system for identifying application identifier
EP1798895A1 (en) A method and network element for forwarding data
CN104243205A (en) Message processing method and device used during virtual switch fault
CN109756521B (en) NSH message processing method, device and system
CN112702773B (en) Communication method and device
CN111984290B (en) Method for upgrading embedded equipment, embedded equipment and storage medium
CN111741508B (en) Method, controller, forwarding device, device and medium for establishing communication connection
CN106331152B (en) Method and device for realizing information synchronization between modules
CN103001865B (en) The method and apparatus released news in a kind of LSP fragment message
CN108243102B (en) Method for realizing fast rerouting and PE equipment
CN106911769B (en) Cloud platform routing data processing method and physical server of cloud platform
CN110708275B (en) Protocol message processing method and device
CN107181689B (en) Message interaction method and device between routers
CN109039916B (en) Message forwarding method, device and storage medium
CN110784339A (en) LACP message overtime fault detection method and device, and electronic equipment
CN109218198B (en) Data interaction method, device, MPLS network system and storage medium
CN115152192B (en) PCE controlled network reliability
CN111092770B (en) Virtual network management method and electronic equipment
CN108574587A (en) The capacity update method and device of distributed apparatus
CN111130871B (en) Protection switching method and device and network equipment
CN108270614B (en) SDN network-based fault processing method, device and equipment
JP2015114952A (en) Network system, monitoring control unit, and software verification method
CN113194498A (en) Communication detection method and device
CN115499489B (en) Method, device, equipment and readable medium for managing sub-network in link

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant