CN109474520B - Flow forwarding method of multicast VPN (virtual private network), PE (provider edge) and multicast VPN - Google Patents
Flow forwarding method of multicast VPN (virtual private network), PE (provider edge) and multicast VPN Download PDFInfo
- Publication number
- CN109474520B CN109474520B CN201710800739.4A CN201710800739A CN109474520B CN 109474520 B CN109474520 B CN 109474520B CN 201710800739 A CN201710800739 A CN 201710800739A CN 109474520 B CN109474520 B CN 109474520B
- Authority
- CN
- China
- Prior art keywords
- upstream
- path
- routing information
- preset field
- joining
- 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
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/16—Multipoint routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- 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/22—Alternate routing
-
- 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/38—Flow based routing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a flow forwarding method of a multicast VPN (virtual private network), a PE (provider edge) and the multicast VPN, wherein the flow forwarding method of the multicast VPN comprises the following steps: receiving joining routing information sent by an edge PE of a downstream service provider; and determining the self as a standby path device according to the joining routing information, and configuring the self as a state of not forwarding the flow. According to the embodiment of the invention, the first upstream PE and the second upstream PE can determine the main and standby of the first upstream PE and the second upstream PE according to the added routing information by adding the routing information, the main path sets forwarding flow, and the standby path equipment does not forward the flow, so that bandwidth resources of a public network are not consumed, and no redundant flow occurs.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a traffic forwarding method for a multicast VPN network, a PE, and a multicast VPN network.
Background
With the development of multicast VPN technology, a technical scheme of public network multicast VPN tunnel establishment and private network route advertisement through MPLS/BGP is gradually used. Because the PE nodes are used as a tunnel head node and a tunnel tail node, more message interaction and protocol calculation exist, and routing reconvergence is slower than that of the traditional IP multicast after the nodes are powered off.
Related IP Multicast generally uses a MOFRR (Multicast-Only Fast route) scheme for Fast path switching, and the basic idea is to route two paths, namely, a main path and a standby path, to a downstream node, and the downstream node selects a flow of one of the main paths to forward, and when a PE node on the upstream of the main path detects a failure, the standby path takes effect. However, using the MOFRR scheme results in a large amount of redundant traffic in the network.
Disclosure of Invention
The technical problem to be solved by the embodiments of the present invention is to provide a traffic forwarding method for a multicast VPN network, a PE, and a multicast VPN network, so as to implement that an upstream PE on a backup path does not forward traffic and avoid redundant traffic.
In order to solve the foregoing technical problem, an embodiment of the present invention provides a method for forwarding traffic of a multicast VPN network, including:
receiving joining routing information sent by an edge PE of a downstream service provider;
and determining the self as a standby path device according to the joining routing information, and configuring the self as a state of not forwarding the flow.
Further, the joining the routing information includes:
a first preset field, wherein an IP address serving as main path equipment is recorded in the first preset field;
and the second preset field is internally recorded with an IP address serving as the standby path equipment.
Further, the joining routing information further includes:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
Further, the joining routing information further includes:
a fifth preset field for indicating a detection mechanism between the backup path device and the primary path device.
Further, the step of determining itself as the backup path device according to the joining route information includes:
reading the IP addresses recorded in the first preset field and the second preset field of the added routing information;
and when the IP address of the self is the same as the IP address recorded in the second preset field, determining the self as the standby path equipment.
Further, the method further comprises:
reading the fifth preset field of the added routing information;
establishing a detection session with the main path device according to a detection mechanism indicated by the fifth preset field;
and when the detection session is disconnected, determining the detection session as main path equipment, switching the detection session from a state of not forwarding the traffic to a state of forwarding the traffic, and forwarding the traffic in a second path where the detection session is located.
Further, the method further comprises:
and after the tunnel is switched according to a preset strategy, keeping the tunnel in a state of not forwarding the flow.
According to another aspect of the present invention, an embodiment of the present invention further provides a method for forwarding traffic of a multicast VPN network, including:
receiving joining route information sent by downstream PE;
and determining the router as main path equipment according to the adding routing information, and forwarding the flow in the first path where the router is located.
Further, the joining the routing information includes:
a first preset field, wherein an IP address used as a main path device is recorded in the first preset field;
and the second preset field is internally recorded with an IP address serving as the standby path equipment.
Further, the joining routing information further includes:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
Further, the step of determining itself as the main path device according to the joining route information includes:
reading the IP addresses recorded in the first preset field and the second preset field of the added routing information;
and when the IP address of the user self is the same as the IP address recorded in the first preset field, determining the user self as the main path equipment.
Further, the method further comprises:
and after the tunnel is switched according to a preset strategy, forwarding the flow to the switched tunnel.
According to another aspect of the present invention, an embodiment of the present invention further provides a method for forwarding traffic of a multicast VPN network, including:
receiving a joining message requesting to join the multicast VPN network;
respectively sending adding routing information to a first upstream PE on a first path and a second upstream PE on a second path according to the adding message; the joining routing information is used for enabling the first upstream PE to determine itself as main path equipment according to the joining routing information and forward flow in the first path;
and the second upstream PE determines itself as a standby path device according to the joining route information and configures itself into a state of not forwarding traffic.
Further, the adding the routing information includes:
a first preset field, wherein an IP address serving as main path equipment is recorded in the first preset field;
and the second preset field is internally recorded with an IP address serving as the standby path equipment.
Further, the adding the routing information further includes:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
Further, the joining routing information further includes:
a fifth preset field for indicating a detection mechanism between the backup path device and the primary path device.
Further, the step of sending the joining-route information to the first upstream PE on the first path and the second upstream PE on the second path respectively includes:
comparing a size of the IP address of the first upstream PE to a size of the IP address of the second upstream PE;
when the IP address of the first upstream PE is larger than the IP address of the second upstream PE, writing the IP address of the first upstream PE into a first preset field added with routing information, and writing the IP address of the second upstream PE into a second preset field added with the routing information;
and sending the adding route information to the first upstream PE and the second upstream PE respectively.
According to another aspect of the present invention, an embodiment of the present invention further provides a PE, including:
the receiving module is used for receiving the joining routing information sent by the downstream PE;
and the processing module is used for determining the processing module as a standby path device according to the adding route information and configuring the processing module as a state of not forwarding the flow.
According to another aspect of the present invention, an embodiment of the present invention further provides a PE, including:
the receiving module is used for receiving the joining routing information sent by the downstream PE;
and the processing module is used for determining the processing module as main path equipment according to the added routing information and forwarding the flow in the first path where the processing module is located.
According to another aspect of the present invention, an embodiment of the present invention further provides a PE, including:
the receiving module is used for receiving a joining message requesting to join the multicast VPN network;
a sending module, configured to send joining route information to a first upstream PE on a first path and a second upstream PE on a second path, respectively, according to the joining packet; the joining routing information is used for enabling the first upstream PE to determine itself as main path equipment according to the joining routing information, and forwarding the forwarding flow in the first path;
and the second upstream PE determines itself as a standby path device according to the joining route information and configures itself into a state of not forwarding traffic.
According to another aspect of the present invention, an embodiment of the present invention further provides a PE, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor being capable of implementing the steps of the method as described above when executing the computer program.
According to another aspect of the present invention, an embodiment of the present invention further provides a multicast VPN network, including:
the downstream PE is used for receiving an adding message requesting to add into the multicast VPN network and respectively sending adding route information to a first upstream PE on a first path and a second upstream PE on a second path according to the adding message;
the first upstream PE is used for determining the first upstream PE as main path equipment according to the received adding routing information and forwarding flow in a first path where the first upstream PE is located;
and the second upstream PE is used for determining the second upstream PE as a standby path device according to the received joining routing information and configuring the second upstream PE into a state of not forwarding the flow.
Compared with the prior art, the flow forwarding method of the multicast VPN network, the PE and the multicast VPN network provided by the embodiment of the invention at least have the following beneficial effects:
according to the embodiment of the invention, the first upstream PE and the second upstream PE can determine the main and standby of the first upstream PE and the second upstream PE according to the added routing information by adding the routing information, the main path sets forwarding flow, and the standby path equipment does not forward the flow, so that bandwidth resources of a public network are not consumed, and no redundant flow occurs.
Drawings
Fig. 1 is a flowchart of a traffic forwarding method of a multicast VPN network of a second upstream PE according to an embodiment of the present invention;
fig. 2 is a second flowchart of a traffic forwarding method of a multicast VPN network of a second upstream PE according to an embodiment of the present invention;
fig. 3 is a third flowchart of a traffic forwarding method of a multicast VPN network of a second upstream PE according to an embodiment of the present invention;
fig. 4 is a flowchart of a traffic forwarding method of a multicast VPN network of a first upstream PE according to an embodiment of the present invention;
fig. 5 is a second flowchart of a traffic forwarding method of a multicast VPN network of a first upstream PE according to an embodiment of the present invention;
fig. 6 is a flowchart of a method for forwarding traffic of a multicast VPN network of a downstream PE according to an embodiment of the present invention;
fig. 7 is a second flowchart of a traffic forwarding method of a multicast VPN network of a downstream PE according to an embodiment of the present invention;
FIG. 8 is a schematic structural diagram of a PE according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a multicast VPN network according to an embodiment of the present invention;
FIG. 10 is a diagram illustrating a portion of attributes added to routing information according to an embodiment of the present invention;
fig. 11 is a diagram illustrating a fifth default field definition for adding routing information according to an embodiment of the present invention.
Detailed Description
To make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments. In the following description, specific details are provided, such as specific configurations and components, merely to facilitate a thorough understanding of embodiments of the invention. Thus, it will be apparent to those skilled in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
In various embodiments of the present invention, it should be understood that the sequence numbers of the following processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
Referring to fig. 1, an embodiment of the present invention provides a method for forwarding traffic in a multicast VPN network, where the method includes:
the joining route information may be Source Tree joining route (Source Tree Join route) information or Shared Tree joining route (Shared Tree Join route) information.
And 102, determining the self as a standby path device according to the joining route information, and configuring the self as a state of not forwarding the flow.
In the embodiment of the present invention, two forwarding paths are provided, each path includes an upstream PE, and both the two upstream PEs can receive the joining routing information sent by the downstream PE, so as to distinguish the first upstream PE from the second upstream PE, and in order to better understand the present invention, the second upstream PE is taken as a backup path device for example.
In the embodiment of the present invention, the joining routing information carries information for indicating the main path device and the backup path device, and in an embodiment, the information may be BGP (Border Gateway Protocol) information, where the information may be determined to be the backup path device or the main path device by the indicating information carried in the joining routing information, and when the information is determined to be the backup path device according to the joining routing information, the information is configured to be in a state of not forwarding traffic, so that only the main path device forwards traffic, thereby not consuming bandwidth resources of a public network, and not generating redundant traffic.
Wherein the joining routing information may include:
a first preset field, wherein an IP address serving as main path equipment is recorded in the first preset field;
and a second preset field, wherein an IP address serving as a standby path device is recorded in the second preset field.
Further, the joining routing information may further include:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
The third preset field and the fourth preset field can indicate the field lengths of the first preset field and the second preset field by setting field length information, and can also set a preset character, wherein the preset character corresponds to the length of a preset field, so that indication is realized. For example, a character 4 is written in the third preset field, the character 4 may indicate that the first preset field is an IPv4 address, and a character 16 may be written in the fourth preset field, the character 16 may indicate that the second preset field is an IPv6 address.
Further, the joining routing information may further include:
a fifth preset field for indicating a detection mechanism between the backup path device and the primary path device.
For example, when B is written in the fifth preset field, the standby path device performs session detection with the main path device in a BFD detection mode. When the fifth preset field does not indicate a detection mechanism, the detection mode that the backup path device may adopt is determined according to a local configuration policy, where the policy may be to detect according to a local preset detection mechanism when the fifth preset field does not indicate a preset detection mechanism, or may be to manually configure a detection mechanism between the backup path device and the main path device.
Referring to fig. 2, in step 102, the step of determining itself as the backup path device according to the joining route information includes:
When receiving the joining routing information, the upstream PE reads the information recorded in the first preset field and the second preset field, determines the upstream PE as a main path device when the IP address of the upstream PE is the same as the IP address recorded in the first preset field, configures the upstream PE as the main path device, and forwards the flow in the first path where the upstream PE is located; and when the IP address of the self is the same as the IP address recorded in the second preset field, determining the self as the standby path equipment, configuring the self as the standby path equipment, and adjusting the self to be in a state of not forwarding the flow.
The configuration information of the primary path device and the configuration information of the standby path device may be set in a local policy, or may be transmitted to the corresponding devices through a message, which is not limited in the present invention.
Referring to fig. 3, the method may further include:
And when the session is disconnected, the standby path equipment can conclude that the standby path equipment determines the standby path equipment as the main path equipment and forwards the flow, wherein the standby path equipment can quickly find the fault of the main path equipment according to the detection session, so that the aim of quick switching is fulfilled.
Wherein the method may further comprise:
and after the tunnel is switched according to a preset strategy, keeping the tunnel in a state of not forwarding the flow.
In an embodiment, when initiating S-PMSI tunnel switching according to a local policy, the backup path device is still in a state of not forwarding traffic after the tunnel switching.
Referring to fig. 4, according to another aspect of the present invention, an embodiment of the present invention further provides a traffic forwarding method for a multicast VPN network, including:
When the first upstream PE determines itself as the main path device according to the joining route information, the first upstream PE forwards the traffic in the first path where the first upstream PE is located.
Further, the joining routing information may include:
a first preset field, wherein an IP address serving as main path equipment is recorded in the first preset field;
and the second preset field is internally recorded with an IP address serving as the standby path equipment.
Further, the joining routing information may further include:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
Referring to fig. 5, in step 402, the step of determining itself as the main path device according to the joining route information includes:
Further, the method may further include:
and after the tunnel is switched according to a preset strategy, forwarding the flow to the switched tunnel.
In an embodiment, the first upstream PE adds the routing information after receiving the information, and when determining itself as the main path device, the private network multicast routing forwards the traffic to the corresponding I-PMSI. And meanwhile, the switching of the S-PMSI tunnel is initiated according to the local strategy, and after the switching is successful, the private network multicast router (C-Source1, C-Group1) continuously forwards the flow to the corresponding S-PMSI tunnel.
Switching may occur according to a protocol flow PMSI, including switching between I-PMSI (inclusive PMSI) and S-PMSI (selective PMSI), which does not affect the forwarding state of the private network routing PMSI to the egress.
Referring to fig. 6, according to another aspect of the present invention, an embodiment of the present invention further provides a traffic forwarding method for a multicast VPN network, including:
When finding the unicast route of the private network source or the RP, the downstream PE sends the joining route information to the first upstream PE on the first path and the second upstream PE on the second path respectively. The joining route information may be a Source Tree joining route (Source Tree Join route) or a Shared Tree joining route (Shared Tree Join route).
Further, the joining routing information may include:
a first preset field, wherein an IP address used as a main path device is recorded in the first preset field;
and the second preset field is internally recorded with an IP address serving as the standby path equipment.
Further, the joining routing information may further include:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
Further, the joining routing information may further include:
a fifth preset field for indicating a detection mechanism between the backup path device and the primary path device.
Referring to fig. 7, in step 602, the step of sending joining routing information to the first upstream PE on the first path and the second upstream PE on the second path respectively may include:
In one embodiment, the larger one is determined to be the primary path device by comparing the sizes of the IP addresses of the first upstream PE and the second upstream PE. It should be noted that the above-mentioned manner of determining the primary path device and the backup path device is only a preferred embodiment provided by the present invention.
Referring to fig. 8, according to another aspect of the present invention, an embodiment of the present invention further provides a PE, including:
a receiving module 801, configured to receive joining routing information sent by a downstream PE;
a processing module 802, configured to determine itself as a backup path device according to the joining routing information, and configure itself in a state of not forwarding traffic.
Further, the joining the routing information includes:
a first preset field, wherein an IP address serving as main path equipment is recorded in the first preset field;
and the second preset field is internally recorded with an IP address serving as the standby path equipment.
Further, the joining routing information further includes:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
Further, the joining routing information further includes:
a fifth preset field for indicating a detection mechanism between the backup path device and the primary path device.
Further, the processing module 802 is specifically configured to:
reading the IP addresses recorded in the first preset field and the second preset field of the added routing information;
and when the IP address of the self is the same as the IP address recorded in the second preset field, determining the self as the standby path equipment.
Further, the PE further comprises:
a reading module, configured to read the fifth preset field of the joining routing information;
the detection module is used for establishing a detection session with the main path equipment according to a detection mechanism indicated by the fifth preset field;
and the switching module is used for determining the switching module as the main path equipment when the detection session is disconnected, switching the switching module from a state of not forwarding the flow to a state of forwarding the flow, and forwarding the flow in a second path where the switching module is positioned.
Further, the processing module 802 is further configured to:
and after the tunnel is switched according to a preset strategy, keeping the tunnel in a state of not forwarding the flow.
According to another aspect of the present invention, an embodiment of the present invention further provides a PE, including:
the receiving module is used for receiving the joining routing information sent by the downstream PE;
and the processing module is used for determining the processing module as main path equipment according to the added routing information and forwarding the flow in the first path where the processing module is located.
Further, the joining the routing information includes:
a first preset field, wherein an IP address serving as main path equipment is recorded in the first preset field;
and the second preset field is internally recorded with an IP address serving as the standby path equipment.
Further, the joining routing information further includes:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
Further, the processing module is specifically configured to:
reading the IP addresses recorded in the first preset field and the second preset field of the added routing information;
and when the IP address of the user self is the same as the IP address recorded in the first preset field, determining the user self as the main path equipment.
Further, the processing module is further configured to:
and after switching the tunnels according to a preset strategy, forwarding the traffic to the switched tunnels.
According to another aspect of the present invention, an embodiment of the present invention further provides a PE, including:
a receiving module, configured to receive an addition packet requesting to add to a multicast VPN network;
a sending module, configured to send joining route information to a first upstream PE on a first path and a second upstream PE on a second path, respectively, according to the joining packet; the joining routing information is used for enabling the first upstream PE to determine itself as a main path device according to the joining routing information, and forward the forwarding flow in the first path;
and the second upstream PE determines itself as a standby path device according to the joining route information and configures itself into a state of not forwarding traffic.
Further, the joining the routing information includes:
a first preset field, wherein an IP address serving as main path equipment is recorded in the first preset field;
and the second preset field is internally recorded with an IP address serving as the standby path equipment.
Further, the joining routing information further includes:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
Further, the joining routing information further includes:
a fifth preset field for indicating a detection mechanism between the backup path device and the primary path device.
Further, the sending module is specifically configured to:
comparing a size of the IP address of the first upstream PE to a size of the IP address of the second upstream PE;
when the IP address of the first upstream PE is larger than the IP address of the second upstream PE, writing the IP address of the first upstream PE into a first preset field added with routing information, and writing the IP address of the second upstream PE into a second preset field added with the routing information;
and sending the joining routing information to the first upstream PE and the second upstream PE respectively.
According to another aspect of the present invention, an embodiment of the present invention further provides a PE, including: memory, a processor and a computer program stored on the memory and executable on the processor, the processor being able to carry out the steps of the method as described above when executing the computer program.
Referring to fig. 9, according to another aspect of the present invention, an embodiment of the present invention further provides a multicast VPN network, including:
the downstream PE is used for receiving an adding message requesting to add into the multicast VPN network and respectively sending adding route information to a first upstream PE on a first path and a second upstream PE on a second path according to the adding message;
the first upstream PE is used for determining the first upstream PE as main path equipment according to the received adding routing information and forwarding flow in a first path where the first upstream PE is located;
and the second upstream PE is used for determining the second upstream PE as a standby path device according to the received joining routing information and configuring the second upstream PE into a state of not forwarding the flow.
Referring to fig. 9, an example is described below. For convenience of description, PE1 and PE2 are both upstream PEs, and are close to the video source side network; PE3 is a downstream PE, close to the user side network; the unicast route from PE3 to the private network source is an active/standby path, where PE1 is an upstream PE on the active path, and PE2 is an upstream PE on the standby path.
In an embodiment, a BGP backup path attribute (which may be understood as information described in the first to fifth preset fields of the joining routing information) is added to the joining routing information, and the attribute definition is as described in fig. 10 and fig. 11.
The field length of the main Path (Master Path length) indicates the field length of the main Path (Master Path), 4 indicates that the Master Path is an IPv4 address, and 16 indicates that the Master Path is an IPv6 address.
Master Path is the address of the upstream PE node of the main Path.
The field length (Slave Path length) of the backup Path indicates the field length of the backup Path (Slave Path), 4 indicates that the Slave Path is an IPv4 address, and 16 indicates that the Slave Path is an IPv6 address
The Slave Path is the address of the upstream PE node of the main Path
In general, Master Path and Slave Path are IPv4 or IPv6 addresses at the same time
In detail, referring to fig. 11, B in the flag field indicates the BFD detection type, and when B is not set, the detection mode is determined according to the local configuration policy.
In an embodiment, the route identifier (route id) of BGP on PE1 is configured as interface address IP1, the route identifier of BGP on PE2 is configured as interface address IP2, and BFD session is configured between IP1 and IP2 for checking.
When PE3 receives an add message of PIM or IGMP private network side designated Source address (hereinafter referred to as C-Source1) and Group address (hereinafter referred to as C-Group1), it finds a unicast route of C-Source1, selects PE1 as an upstream PE of the main path, and selects PE2 as an upstream PE of the standby path (the selection mechanism may refer to the above judgment of the size of the IP address, or may adopt other selection mechanisms, which is not limited in the present invention).
PE3 sends a source tree joining route to PE1 and PE2 through BGP, and carries backup Path attributes, wherein Master Path upstream PE address IP1, Path upstream PE Address Path Address PE address IP 2. The Flags field B flag is set.
When PE1 receives the address, it judges the Master Path address is itself in the backup Path attribute, the private network multicast route forwards the flow to the corresponding I-PMSI. And meanwhile, the switching of the S-PMSI tunnel is initiated according to the local strategy, and after the switching is successful, the private network multicast router (C-Source1, C-Group1) forwards the flow to the corresponding S-PMSI tunnel.
When PE2 receives the information, it judges that the Slave Path address is in the backup Path attribute, the I-PMSI forwarding state corresponding to the private network multicast route (C-Source1, C-Group1) is associated with the BFD session between Master Path and Slave Path, and if the session is normal, the session is not forwarding state. According to the local strategy, after S-PMSI switching occurs, the forwarding state is still not forwarded.
When the PE1 equipment fails, the PE2 finds that the BFD session between the Master Path and the Slave Path is disconnected, and immediately sets the PMSI of the associated private network multicast route (C-Source1, C-Group1) to a forwarding state. The purpose of fast switching is achieved.
In the above, the BFD session is configured between IP1 and IP2 for checking, and the backup path device may also establish a detection session with the primary path device according to the backup path attribute.
Further, the joining the routing information includes:
a first preset field, wherein an IP address serving as main path equipment is recorded in the first preset field;
and the second preset field is internally recorded with an IP address serving as the standby path equipment.
Further, the joining routing information further includes:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
Further, the joining routing information further includes:
a fifth preset field for indicating a detection mechanism between the backup path device and the primary path device.
Further, the second upstream PE includes:
a first reading module, configured to read the IP addresses recorded in the first preset field and the second preset field of the joining routing information;
and the first determining module is used for determining the self as the standby path equipment when the self IP address is the same as the IP address recorded in the second preset field.
Further, the second upstream PE further includes:
the second reading module is used for reading the fifth preset field of the added routing information;
the detection module is used for establishing a detection session with the main path equipment according to a detection mechanism indicated by the fifth preset field;
and the switching module is used for determining the self as the main path equipment when the detection session is disconnected, switching the self from a state of not forwarding the flow to a state of forwarding the flow, and forwarding the flow in a second path where the self is positioned.
Further, the second upstream PE further includes:
and the first processing module is used for keeping the first processing module in a state of not forwarding the flow after switching the tunnel according to a preset strategy.
Further, the first upstream PE includes:
a third reading module, configured to read the IP addresses recorded in the first preset field and the second preset field of the route joining information;
and the second determining module is used for determining the second determining module as the main path device when the IP address of the second determining module is the same as the IP address recorded in the first preset field.
Further, the first upstream PE further includes:
and the second processing module is used for forwarding the flow to the switched tunnel after the tunnel is switched according to the preset strategy.
Further, the downstream PE includes:
a comparing module, configured to compare a size of the IP address of the first upstream PE with a size of the IP address of the second upstream PE;
a write module, configured to write the IP address of the first upstream PE into a first preset field added to the routing information and write the IP address of the second upstream PE into a second preset field added to the routing information when the size of the IP address of the first upstream PE is greater than the size of the IP address of the second upstream PE;
a sending module, configured to send the joining routing information to the first upstream PE and the second upstream PE, respectively.
To sum up, in the embodiment of the present invention, by adding the routing information, the first upstream PE and the second upstream PE can determine their own main and standby according to the added routing information, and the main path sets the forwarding traffic, and the standby path device does not forward the traffic, so that the bandwidth resource of the public network is not consumed, and no redundant traffic occurs.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion.
While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (16)
1. A method for forwarding traffic of a multicast VPN network is characterized by comprising the following steps:
an upstream service provider edge PE receives joining routing information sent by a downstream PE;
the upstream PE determines that the upstream PE is a main path device or a standby path device according to the adding route information;
when the upstream PE determines itself as the backup path device, the upstream PE configures itself to a state of not forwarding traffic;
and when the upstream PE determines the upstream PE as the main path equipment, forwarding the flow in the first path where the upstream PE is located.
2. The method of claim 1, wherein the joining routing information comprises:
a first preset field, wherein an IP address serving as a main path device is recorded in the first preset field;
and a second preset field, wherein an IP address serving as a standby path device is recorded in the second preset field.
3. The method of claim 2, wherein the joining routing information further comprises:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
4. The method of claim 2, wherein the joining routing information further comprises:
and a fifth preset field, configured to indicate a detection mechanism between the standby path device and the active path device.
5. The method of claim 2, wherein the step of the upstream PE determining that the upstream PE is the active path device or the standby path device according to the joining routing information comprises:
reading the IP addresses recorded in the first preset field and the second preset field of the added routing information;
when the IP address of the self is the same as the IP address recorded in the second preset field, the self is determined as the standby path equipment;
and when the IP address of the self is the same as the IP address recorded in the first preset field, determining the self as the main path equipment.
6. The method of claim 4, further comprising:
reading the fifth preset field of the added routing information;
establishing a detection session with the main path equipment according to a detection mechanism indicated by the fifth preset field; when the detection session is disconnected, the detection session is determined as the main path equipment, the detection session is switched from a state of not forwarding the traffic to a state of forwarding the traffic, and the traffic is forwarded in a second path where the detection session is located.
7. The method of claim 1, further comprising:
when the upstream PE is a standby path device, the upstream PE keeps a state of not forwarding the flow after switching the tunnel according to a preset strategy;
and when the upstream PE is the main path equipment, the upstream PE forwards the flow to the switched tunnel after switching the tunnel according to a preset strategy.
8. A method for forwarding traffic of a multicast VPN network is characterized by comprising the following steps:
the downstream service provider edge PE receives a joining message requesting to join the multicast VPN network;
and the downstream PE respectively sends joining routing information to a first upstream PE on the first path and a second upstream PE on the second path according to the joining message, so that the first upstream PE determines that the first upstream PE is the main path equipment or the standby path equipment according to the joining routing information, when the first upstream PE determines that the first upstream PE is the main path equipment, the downstream PE forwards the flow in the first path where the downstream PE is located, and the second upstream PE determines that the second upstream PE is the main path equipment or the standby path equipment according to the joining routing information, and when the downstream PE determines that the downstream PE is the standby path equipment, the downstream PE configures the downstream PE into a state of not forwarding the flow.
9. The method of claim 8, wherein the joining routing information comprises:
a first preset field, wherein an IP address serving as a main path device is recorded in the first preset field;
and the second preset field is internally recorded with an IP address serving as the standby path equipment.
10. The method of claim 9, wherein the joining routing information further comprises:
a third preset field for indicating a field length of the first preset field;
a fourth preset field for indicating a field length of the second preset field.
11. The method of claim 10, wherein the joining routing information further comprises:
and a fifth preset field, configured to indicate a detection mechanism between the standby path device and the active path device.
12. The method of claim 8, wherein the step of sending joining routing information to the first upstream PE on the first path and the second upstream PE on the second path, respectively, comprises:
comparing a size of the IP address of the first upstream PE to a size of the IP address of the second upstream PE;
when the IP address of the first upstream PE is larger than the IP address of the second upstream PE, writing the IP address of the first upstream PE into a first preset field added into routing information, and writing the IP address of the second upstream PE into a second preset field added into the routing information;
and sending the adding route information to the first upstream PE and the second upstream PE respectively.
13. An upstream service provider edge, PE, comprising:
the receiving module is used for receiving the joining routing information sent by the downstream PE;
and the processing module is used for determining that the processing module is the main path equipment or the standby path equipment according to the added routing information, configuring the processing module into a state of not forwarding the flow when the processing module determines that the processing module is the standby path equipment, and forwarding the flow in the first path where the processing module is positioned when the processing module determines that the processing module is the main path equipment.
14. A downstream service provider edge, PE, comprising:
the receiving module is used for receiving a joining message requesting to join the multicast VPN network;
a sending module, configured to send, according to the join packet, join routing information to a first upstream PE on a first path and a second upstream PE on a second path, respectively, so that the first upstream PE determines that it is an active path device or a standby path device according to the join routing information, and forwards the forwarding traffic in the first path where it is located when it is determined that it is the active path device, and the second upstream PE determines that it is the active path device or the standby path device according to the join routing information, and configures itself into a state of not forwarding traffic when it is determined that it is the standby path device.
15. A PE, comprising: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor being capable of implementing the steps of the method according to any one of claims 1 to 7 when executing the computer program; or a step in a process as claimed in any one of claims 8 to 12.
16. A multicast VPN network, comprising:
the downstream PE is used for receiving an adding message requesting to add into the multicast VPN network and respectively sending adding route information to a first upstream PE on a first path and a second upstream PE on a second path according to the adding message;
the first upstream PE is used for receiving the joining routing information sent by the downstream PE, determining that the first upstream PE is a main path device or a standby path device according to the received joining routing information, and forwarding the flow in a first path where the first upstream PE is located when the first upstream PE is determined as the main path device;
and the second upstream PE is used for receiving the joining routing information sent by the downstream PE, determining that the second upstream PE is the main path equipment or the standby path equipment according to the received joining routing information, and configuring the second upstream PE into a state of not forwarding the flow when the second upstream PE is determined as the standby path equipment.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710800739.4A CN109474520B (en) | 2017-09-07 | 2017-09-07 | Flow forwarding method of multicast VPN (virtual private network), PE (provider edge) and multicast VPN |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710800739.4A CN109474520B (en) | 2017-09-07 | 2017-09-07 | Flow forwarding method of multicast VPN (virtual private network), PE (provider edge) and multicast VPN |
Publications (2)
Publication Number | Publication Date |
---|---|
CN109474520A CN109474520A (en) | 2019-03-15 |
CN109474520B true CN109474520B (en) | 2022-07-08 |
Family
ID=65657589
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201710800739.4A Active CN109474520B (en) | 2017-09-07 | 2017-09-07 | Flow forwarding method of multicast VPN (virtual private network), PE (provider edge) and multicast VPN |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN109474520B (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112039765B (en) * | 2019-06-03 | 2023-05-30 | 中兴通讯股份有限公司 | Method for transmitting route information, method and device for selecting route |
CN112134776B (en) * | 2019-06-25 | 2022-08-26 | 华为技术有限公司 | Method for generating multicast forwarding table item and access gateway |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102316016A (en) * | 2010-07-05 | 2012-01-11 | 华为技术有限公司 | Method and device for forwarding multicasting flow |
CN103795626A (en) * | 2014-02-19 | 2014-05-14 | 华为技术有限公司 | Method and device for rapid protection switching during multicast process |
US8953446B1 (en) * | 2011-12-20 | 2015-02-10 | Juniper Networks, Inc. | Load balancing multicast join requests over interior and exterior BGP paths in a MVPN |
CN104901893A (en) * | 2015-06-11 | 2015-09-09 | 杭州华三通信技术有限公司 | Method and device for protecting multicast traffic |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100527683C (en) * | 2006-08-24 | 2009-08-12 | 华为技术有限公司 | Failure protecting method and system |
CN101631043A (en) * | 2009-08-05 | 2010-01-20 | 杭州华三通信技术有限公司 | Multicast fault recovery method, multicast router and system |
CN101645790B (en) * | 2009-08-10 | 2011-11-16 | 杭州华三通信技术有限公司 | Switching-over method, device and system of multicast distribution tree |
CN101651578B (en) * | 2009-09-08 | 2011-09-07 | 杭州华三通信技术有限公司 | Bidirectional forwarding detection method by cross-domain forwarding and PE devices |
CN101989952B (en) * | 2010-11-03 | 2014-12-17 | 中兴通讯股份有限公司 | Multicasting method and device |
CN102263695A (en) * | 2011-07-27 | 2011-11-30 | 中兴通讯股份有限公司 | Method and system for passing through LDP (label distribution protocol) network by multicast network |
US9998361B2 (en) * | 2015-09-30 | 2018-06-12 | Juniper Networks, Inc. | MLDP multicast only fast re-route over remote loop-free alternate backup path |
US10243821B2 (en) * | 2015-12-30 | 2019-03-26 | Juniper Networks, Inc. | OAM mechanisms for EVPN active-active services |
-
2017
- 2017-09-07 CN CN201710800739.4A patent/CN109474520B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102316016A (en) * | 2010-07-05 | 2012-01-11 | 华为技术有限公司 | Method and device for forwarding multicasting flow |
US8953446B1 (en) * | 2011-12-20 | 2015-02-10 | Juniper Networks, Inc. | Load balancing multicast join requests over interior and exterior BGP paths in a MVPN |
CN103795626A (en) * | 2014-02-19 | 2014-05-14 | 华为技术有限公司 | Method and device for rapid protection switching during multicast process |
CN104901893A (en) * | 2015-06-11 | 2015-09-09 | 杭州华三通信技术有限公司 | Method and device for protecting multicast traffic |
Also Published As
Publication number | Publication date |
---|---|
CN109474520A (en) | 2019-03-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3435595B1 (en) | Maximally redundant trees to redundant multicast source nodes for multicast protection | |
US10129075B2 (en) | Multicast only fast re-route over remote loop-free alternate backup path | |
CN108512739B (en) | Multicast state between multi-homed routers in an Ethernet virtual private network | |
US9077551B2 (en) | Selection of multicast router interfaces in an L2 switch connecting end hosts and routers, which is running IGMP and PIM snooping | |
US8902780B1 (en) | Forwarding detection for point-to-multipoint label switched paths | |
US7969978B2 (en) | Method and apparatus for providing congruent multicast and unicast routing | |
WO2021258754A1 (en) | Message indication method and apparatus, and device and storage medium | |
WO2017156974A1 (en) | Information transmission method, apparatus and system | |
WO2019085822A1 (en) | Method and device for implementing multicast service | |
US9838210B1 (en) | Robust control plane assert for protocol independent multicast (PIM) | |
EP3965368B1 (en) | Replication mode selection for multicast in evpn | |
WO2020001389A1 (en) | Communication method, device and system for avoiding loop | |
US20140241351A1 (en) | Dynamic determination of the root node of an mldp tunnel | |
KR20220062347A (en) | Reverse path forwarding RPF inspection method and apparatus | |
US11632354B2 (en) | Methods and apparatuses for source discovery | |
US9100201B1 (en) | Inter-site PIM-dense mode and PIM-BSR support for MPLS/BGP IP VPNs | |
CN109474520B (en) | Flow forwarding method of multicast VPN (virtual private network), PE (provider edge) and multicast VPN | |
US11323279B1 (en) | Internet group management protocol host mobility in ethernet virtual private network multicast networks | |
WO2023035983A1 (en) | Method and device for electing designated forwarder (df) | |
WO2013135046A1 (en) | Method and device for establishing multicast path | |
WO2022257773A1 (en) | Routing detection method, device, system, and storage medium | |
WO2024061184A1 (en) | Correspondence acquisition method, parameter notification method, and apparatus, device and medium | |
CN112671630B (en) | Multicast method, device, network equipment and storage medium | |
WO2021259292A1 (en) | Information transmission and distribution tree establishment methods, apparatus, device, and storage medium | |
EP3923529A1 (en) | Multicast source discovery protocol (msdp) loop avoidance |
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 | ||
TR01 | Transfer of patent right |
Effective date of registration: 20220922 Address after: No. 3, Xingguang 5th Road, North New District, Yubei District, Chongqing 401120 (Zhongxing Building) Patentee after: Chongqing Zhongxing Software Co.,Ltd. Address before: 518057 Zhongxing building, science and technology south road, Nanshan District hi tech Industrial Park, Guangdong, Shenzhen Patentee before: ZTE Corp. |
|
TR01 | Transfer of patent right |