US20180227135A1 - Protocol independent multicast sparse mode (pim-sm) support for data center interconnect - Google Patents
Protocol independent multicast sparse mode (pim-sm) support for data center interconnect Download PDFInfo
- Publication number
- US20180227135A1 US20180227135A1 US15/945,671 US201815945671A US2018227135A1 US 20180227135 A1 US20180227135 A1 US 20180227135A1 US 201815945671 A US201815945671 A US 201815945671A US 2018227135 A1 US2018227135 A1 US 2018227135A1
- Authority
- US
- United States
- Prior art keywords
- router
- multicast
- traffic
- pim
- bum
- 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.)
- Abandoned
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/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1886—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
-
- 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
- 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]
- H04L12/4645—Details on frame tagging
- H04L12/465—Details on frame tagging wherein a single frame includes a plurality of VLAN tags
- H04L12/4654—Details on frame tagging wherein a single frame includes a plurality of VLAN tags wherein a VLAN tag represents a customer VLAN, e.g. C-Tag
-
- 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
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/60—Router architectures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/20—Support for services
- H04L49/201—Multicast operation; Broadcast operation
Definitions
- the invention relates to computer networks and, more specifically, to forwarding multicast traffic within data centers.
- a data center is a specialized facility that provides data serving and backup as well as other network-based services for subscribers and other entities.
- a data center in its most simple form may consist of a single facility that hosts all of the infrastructure equipment, such as networking and storage systems, servers, redundant power supplies, and environmental controls.
- L2 interconnect is an Ethernet virtual private network (EVPN) interconnect through an intermediate network coupling multiple physical data centers.
- EVPN Ethernet virtual private network
- This disclosure describes techniques for supporting Protocol Independent Multicast Sparse Mode (PIM-SM) to transport traffic in a Virtual Extensible LAN (VXLAN) underlay of a data center, where the BUM traffic is received on active-active, multi-homed Ethernet virtual private network (EVPN) interconnects between multiple physical data centers.
- PIM-SM Protocol Independent Multicast Sparse Mode
- VXLAN Virtual Extensible LAN
- EVPN virtual private network
- the VXLAN may be multi-homed to provide protection and load balancing, and in some situations is may be desirable to utilize PIM-SM to deliver so-called “BUM” traffic, i.e., broadcast, unknown unicast and multicast traffic in the VXLAN.
- BUM so-called “BUM” traffic
- a method comprises: establishing an Ethernet virtual private network (EVPN) data center interconnect (DCI) between a first data center running a virtual extensible local area network (VXLAN) and a second data center, wherein the VXLAN of the first data center is active-active multi-homed to two or more provider edge (PE) routers of the EVPN and includes VXLAN tunnels established using protocol independent multicast-sparse mode (PIM-SM).
- PIM-SM protocol independent multicast-sparse mode
- the method further includes receiving, with one of the two or more multi-homed PE routers from the EVPN, BUM (broadcast, unknown unicast, and multicast) traffic, wherein the one of the two or more multi-homed PE routers is not a designated forwarder (DF), and forwarding the BUM traffic from the one of the two or more multi-homed PE routers into the VXLAN toward the first data center according to EVPN BUM forwarding rules.
- BUM broadcast, unknown unicast, and multicast
- a router comprises a routing engine having a processor executing an Ethernet virtual private network (EVPN) protocol to establish a data center interconnect (DCI) between a first data center running a virtual extensible local area network (VXLAN) and a second data center using an Ethernet virtual private network (EVPN).
- the router is one of a plurality of active-active routers multi-homed to the data center and providing the EVPN DCI, and wherein the routers establish VXLAN tunnels to transport traffic through the first data center using protocol independent multicast-sparse mode (PIM-SM).
- PIM-SM protocol independent multicast-sparse mode
- the one of the two or more multi-homed PE routers is not a designated forwarder (DF).
- the router further includes a forwarding engine having a plurality of network interfaces to receive BUM (broadcast, unknown unicast, and multicast) traffic and forward the BUM traffic from the one of the two or more multi-homed PE routers into the VXLAN toward the first data center according to EVPN BUM forwarding rules.
- BUM broadcast, unknown unicast, and multicast
- a computer-readable medium comprising instruction that cause a processor of a router of a plurality of active-active multi-homed routers of an Ethernet virtual private network (EVPN) to establish, with the processor of the router, a data center interconnect (DCI) between a first data center running a virtual extensible local area network (VXLAN) and a second data center using the EVPN, wherein the VXLAN is active-active multi-homed to the plurality of routers of the EVPN and includes VXLAN tunnels established using protocol independent multicast-sparse mode (PIM-SM) between the first data center and the two or more multi-homed PE routers.
- DCI data center interconnect
- VXLAN virtual extensible local area network
- PIM-SM protocol independent multicast-sparse mode
- the instruction further cause the computer-readable medium to program, with the processor of the router, a forwarding unit of the router to: receive, with one of the two or more multi-homed PE routers from the EVPN, BUM (broadcast, unknown unicast, and multicast) traffic; and forward the BUM traffic from the router into the VXLAN toward the first data center according to EVPN BUM forwarding rules specifying that any of the multi-homed PE routers are to forward the BUM traffic into the VXLAN regardless of which of the PE routers is the specified as a designated forwarder (DF) for the EVPN
- BUM broadcastcast, unknown unicast, and multicast
- FIG. 1 is a block diagram illustrating an example network system in which routers provide Protocol Independent Multicast Sparse Mode (PIM-SM) support for data center interconnect between multiple physical data centers.
- PIM-SM Protocol Independent Multicast Sparse Mode
- FIGS. 2A-2C are block diagrams illustrating in further detail portions of the example network system of FIG. 1 .
- FIG. 3 is a block diagram illustrating an exemplary router capable of performing the disclosed techniques.
- FIG. 4 is a flow diagram illustrating example operation of a router in accordance with the techniques described herein.
- FIG. 1 is a block diagram illustrating an example network system in which routers provide Protocol Independent Multicast Sparse Mode (PIM-SM) support for data center interconnect between multiple physical data centers.
- data centers 5 A- 5 B are networks having specialized facilities that provide storage, management, and dissemination of data to subscribers and other entities.
- data centers 5 A, 5 B includes a plurality of servers 9 A, 9 B and storage area networks (SANs) 7 A, 7 B respectively that provide computing environments for subscribers/customers. Subscriber devices (not shown) may connect to data centers 5 to request and receive services and data provided by data centers 5 .
- data centers 5 A, 5 B are geographically dispersed facilities, or “sites,” of an overall data center to provide geographical redundancy against localized failure of one of the data centers.
- WAN 4 represents a layer three (L3) network and may include multiple intermediate routing and switching devices (not shown) that transport data traffic over links between data centers 5 .
- L3 layer three
- MPLS Multiprotocol Label Switching
- MPLS/IP MPLS/IP network
- WAN 4 may represent any network capable of transmitting traffic exchanged between provider edge routers (PEs) 6 .
- PEs provider edge routers
- PEs 6 provider edge routers
- PEs 6 may utilize Ethernet VPN (E-VPN) technology through WAN 4 to provide an EVPN data center interconnect (DCI) between data centers 5 A and 5 B.
- E-VPN Ethernet VPN
- DCI data center interconnect
- PEs 6 provide an EVPN 23 to transport L2 communications for customer networks of data centers 5 through an intermediate network (WAN 4 ), in a transparent manner, i.e., as if the intermediate network does not exist and data centers 5 were instead directly connected.
- each of PEs 6 provide the EVPN 23 to transport L2 communications, such as Ethernet packets or “frames,” through WAN 4 for different customers of data centers 5 . That is, various customer networks provided within data centers 5 may be virtually isolated onto different Virtual Extensible LANs (VXLANs) 14 . As shown in FIG. 1 , each of data centers 5 includes an underlay network 17 A, 17 B of transport routers that transport L2 communications through a respective VXLANs 14 . As such, PEs 6 may receive customer traffic from local VXLANs 14 and forward the traffic through WAN 4 via the EVPN 23 . Similarly, PEs 6 may receive L2 communications from EVPN 23 and forward the L2 communications via VXLANs 14 for transport through the local data centers 5 via underlay networks 17 .
- L2 communications such as Ethernet packets or “frames”
- PEs 6 provide an active-active, multi-homed EVPN/VXLAN data center interconnect (DCI) between data centers 5 .
- each of PEs 6 operates as gateway between EVPN 23 and VXLANs, and may function as VXLAN Tunnel Endpoints (shown as “VTEP” in FIG. 1 ). That is, each PE 6 may include logically separate routing instances for VXLAN 14 and EVPN 23 and each operates to bridge traffic between the two distinct internal routing instances.
- VXLAN DCI Using EVPN VXLAN DCI Using EVPN
- IETF Internet Engineering Task Force
- each data center 5 A, 5 B is multi-homed to WAN 4 for redundancy and load balancing. That is, PE routers 6 A, 6 A′ are configured to operate as multi-homed PEs of a single-active or an active-active multi-homed VXLAN 14 A to provide L2 connectively to customer edge router (CE) 18 A of data center 5 A. Similarly, PE routers 6 B, 6 B′ are configured to operate as multi-homed PEs of a single-active or an active-active multi-homed Ethernet segment 14 B to provide L2 connectively to CE 18 B of data center 5 B.
- CE customer edge router
- traffic from a VTEP can arrive at any of PEs 6 of that Ethernet segment 14 and can be forwarded accordingly over the MPLS/IP WAN network 4 .
- traffic destined to a VTEP can be received over the MPLS/IP network at any of the PEs connected to the VXLAN network and be forwarded accordingly.
- the VXLAN network may alternatively be a NVGRE network.
- L2 state information may include media access control (MAC) addressing information associated with the network devices and customer equipment (e.g., virtual machines) within data centers 5 and the ports and/or pseudowire of the PE through which the customer devices are reachable.
- PEs 6 typically store the MAC addressing information in L2 learning tables associated with each of their interfaces.
- PEs 6 of a multi-homed Ethernet segment connected to the same logical VXLAN are typically configured with a common anycast address.
- PEs 6 A and 6 A′ of FIG. 1 would typically be configured with the same common anycast address for the underlay tunnels through underlay networks 17 .
- PEs 6 A, 6 A′ (and similarly PE 6 B, 6 B′) are viewed as a single logical PE from the perspective of the remote PEs across WAN 4 and also from routers within local VXLAN underlay networks 17 .
- remote VTEPs e.g., PEs 6 B and 6 B′
- routers within underlay network 17 as well as CEs 18 and PEs 6 execute a multicast routing protocol such as protocol independent multicast (PIM) to control transport of multicast traffic within each data center 5 .
- PIM protocol independent multicast
- the routers may support both Protocol Independent Multicast Bidirectional Mode (PIM-BIDIR) and Protocol Independent Multicast Sparse Mode (PIM-SM).
- BUM traffic With respect to broadcast, unknown unicast or multicast L2 traffic, so called “BUM” traffic, received from the EVPN 23 of WAN 4 , one of the PEs 6 of EVPN 23 is elected as the designated forwarder (DF), and conventionally only the DF is allowed to forward BUM traffic to the VXLAN according to EVPN BUM traffic forwarding rules.
- DF forwarder
- PIM-BIDIR To transport BUM traffic within the VXLAN underlay networks, PIM-BIDIR is commonly used because the protocol is compatible with use of a common anycast address assigned to multiple PEs in the active-active mode. In some environments, however, it is desirable to also support or otherwise utilize PIM-SM within underlay networks for delivery of BUM traffic received from EVPN 23 .
- PIM-SM is generally not compatible with active-active, multi-homed EVPN environments that, for example, use a common anycast addresses for multiple PEs.
- This disclosure describes techniques that allow PIM-SIM to be used in network topologies having an EVPN/VXLAN DCI when the VXLAN networks are multi-homed to EVPN PEs working in all-active mode (e.g., FIG. 1 ).
- multi-homed PEs 6 configure forwarding planes therein to apply modified EVPN BUM traffic forwarding rules in a manner that allows PIM-SM to be utilized within VXLANs 14 even though active-active pairs of PEs 6 for each data center 5 share a common anycast address.
- the techniques ensure that BUM traffic 15 received from EVPN 23 can be delivered to all the remote VTEPs in the VXLAN underlay network 17 .
- PEs 6 when configured by an administrator or management system, PEs 6 , whether operating as a DF or non-DF for EVPN 23 , forward BUM traffic 15 from the EVPN 23 into the VXLAN for transport through data centers 5 .
- PE routers 6 may automatically configure their respective forwarding hardware (referred to herein as forwarding units or data planes) to operate according to modified forwarding rules that specify that all PE routers forward all BUM traffic from EVPN 23 to underlay tunnels of VXLAN underlay network 17 traversing data centers 5 regardless of which of the PE routers for each Ethernet segment 14 is elected as DF for that segment.
- PEs 6 A, 6 A′ operate according to modified EVPN BUM traffic forwarding rules to forward subsequent BUM traffic 15 from EVPN 23 and into the VXLAN tunnels of underlay network 17 A.
- multiple distribution trees are transparently created and rooted on potentially multiple EVPN routing instances of multi-homed PEs 6 A, 6 A′ and are utilized in an active-active, EVPN environment of FIG. 1 .
- the techniques leverage reverse path forwarding (RPF) check utilized within PIM-SM to ensure that duplicate copies of BUM traffic 15 will be filtered out by the transport routers prior to the multiple copies reaching their destinations (e.g., servers 9 A or SAN 14 A).
- RPF reverse path forwarding
- FIGS. 2A-2C are block diagrams illustrating in further detail portions of the example network system of FIG. 1 in accordance with the techniques described herein.
- all VTEPs for a local VXLAN including VTEP routing instances executing on any transport routers of underlay networks 17 and PEs 6 for that VXLAN, issue (*,G) PIM joins 13 to initiate multicast traffic for a multicast group (G).
- initial PIM joins 13 from VTEP instances for a VXLAN are directed to a designated Rendezvous Point (RP) 11 for the multicast group for that particular VXLAN.
- RP Rendezvous Point
- RP 11 is a router or other device that has been designated to acts as a shared root for a (*,G) multicast tree that will be, or has been, constructed for subsequent injection of multicast traffic for the multicast group into the VXLAN.
- multicast traffic sent from a sender is typically tunneled to RP 11 , and such tunneled traffic is referred to as “non-native” multicast traffic, which RP 11 would in turn forward as a shared root on the (*,G) distribution tree for a given multicast group (G).
- RP 11 may configured to execute on any of PE routers 6 or on a separate device.
- the multicast flow associated with BUM traffic 15 may be uniquely identified within the PIM register messages 21 as a combination of an anycast address assigned to PEs 6 for EVPN 23 and the multicast group, i.e., an (S,G) PIM register message, where S is set to the anycast address of the multi-homed VXLAN 14 A.
- each of PIM register messages 21 may have a source address of the sending interface of the PE router instead of the anycast address on the PE 6 that originated the PIM register message. In this way, RP 11 may be able to uniquely associate each of PIM messages 21 with the sender, i.e., a respective one of PE routers 6 A.
- RP 11 Upon receiving a (S,G) PIM register message 21 , RP 11 selects one of the multi-homed, active-active PE routers 6 A, 6 A′ from which register messages 21 have been received and sends an (S,G) PIM join 25 for the flow uniquely identified in the PIM register message by the combination of the EVPN anycast address of PE routers 6 A, 6 A′ and multicast group.
- PIM join request 25 may be directed toward a closest one of the multi-homed PEs 6 A, 6 A′ regardless of whether the PE to which the PIM join is directed is the DF or a non-DF for all-active EVPN 23 , where “closest” refers to the lowest weight route from RP 11 to any of the PEs based on a standard path computation (e.g., OSPF path computation) performed on the network domain.
- a standard path computation e.g., OSPF path computation
- the receiving one of PEs 6 A, 6 A′ initiates a handoff process by forwarding any subsequent BUM traffic 15 for the identified flow natively (i.e., as native multicast without encapsulation) to RP, which in turn distributes the BUM traffic into data center 5 on the (*,G) PIM multicast distribution tree.
- RP 11 While receiving the native traffic 15 ′ and temporarily operating as a root for the (*,G) distribution tree into data center 5 A, RP 11 will send respective register-stop messages to any of PEs 6 that subsequently send register messages specifying the same multicast flow (e.g., register-stop message 27 sent to PE 6 A′).
- PE 6 A, 6 A′ receives a (S,G) PIM join 25 for a given combination of a multicast group and anycast address for VXLAN 14 A of EVPN 23 .
- PE router 6 A only one of the active-active routers PE 6 switches to native forwarding of BUM traffic 15 to RP 11 , which in the example of FIG. 1 is PE router 6 A. That is, in this example, PE 6 A receives PIM join 25 from RP 11 for the specific multicast group, anycast address combination and PE router 6 A′ receives register-stop message 27 for the combination.
- PE router 6 A switches to native forwarding all subsequent BUM traffic 15 for the combination to RP 11 , and RP 11 in turn forwards the BUM traffic along the (*,G) distribution tree so as to inject BUM traffic into the VXLAN of data center 5 A.
- PE router 6 A′ upon receiving register-stop message 27 stops issuing subsequent register messages 21 .
- RP 11 operates as temporary (*,G) surrogate for the (anycast,G) source of the multicast traffic for forwarding the traffic within VXLAN of data center 5 A and the underlying transport network 17 A.
- PE routers 6 A, 6 A′ encapsulate initial BUM packets 15 within PIM register messages 21 directed to RP 11 .
- RP 11 prior to RP 11 receiving the first natively sent BUM traffic 15 from any of PEs 6 A, 6 A′ for direction into VXLAN 14 A, RP 11 extracts the BUM packets encapsulated in register messages 21 and forwards the BUM traffic along the (*,G) multicast distribution tree. This may have the benefit of avoiding any loss of initial BUM traffic 15 while RP 11 issues PIM join 25 to one of PEs 6 A, i.e., PE 6 A′ in the example of FIG. 1 .
- this example implementation may also cause duplicate copies of initial BUM packets extracted from PIM register messages 21 received from both PE 6 A and PE 6 A′. This occurrence, however, will be transient and will stop as soon as the first native BUM packet 1 is received by RP 11 . If transient duplication is a concern, some example implementations may utilize a null form of PIM register messages 21 that do not encapsulate BUM packets 15 , but this implementation may lead to transient loss of initial BUM packets 15 .
- multi-homed PEs 6 A, 6 A′ may periodically send null PIM register messages 21 to RP 11 as soon as initial provisioning is completed to pre-build and maintain state for multicast flows to be injected into the VXLAN of data center 5 A.
- any of the VTEPs for VXLAN 17 A receive native multicast traffic 15 from RP 11 on the (*,G) distribution tree, the VTEP outputs PIM joins 31 for the particular (S,G) combination, where S is set to the anycast address for the VXLAN and G is set to the multicast group.
- S is set to the anycast address for the VXLAN
- G is set to the multicast group.
- each PIM join 31 is routed to the closest PE, i.e., any one of PE's 6 A, 6 A′ that is closest to respective VTEP, where “closest” again refers to a lowest weight route that is selected from the VTEP to one of the PEs based on a standard path computation performed on the network domain.
- multiple PEs 6 A, 6 A′ may receive (S,G) PIM joins for the (anycast,group). This, in turn causes each of the receiving EVPN routing instances of PEs 6 A, 6 A′ to construct a respective (S,G) multicast distribution tree for forwarding subsequent BUM traffic 15 for the (S,G) into data center 5 A.
- each receiving PE 6 A, 6 A′ creates respective (S,G) PIM multicast distribution trees, each one rooted at the respective PE that is closest to the VTEP sender.
- each of the PEs 6 A, 6 A′ operates as roots for a respect PIM (S,G) multicast distribution trees, and each (S,G) multicast distribution tree is utilized to send BUM traffic 15 into data center 5 A.
- S,G PIM
- each (S,G) multicast distribution tree is utilized to send BUM traffic 15 into data center 5 A.
- handoff from the (*,G) distribution tree rooted at RP 11 to the multiple, (S,G) trees rooted at PEs 6 A, 6 A′ occurs, and native forwarding of BUM traffic 15 may be triggered on multiple PEs 6 A, 6 A′.
- Every multi-homed PEs 6 A, 6 A′ that receives an (anycast,G) PIM join 31 from a VTEP constructs a respective (anycast,G) multicast distribution tree and, in this way, operates according to modified EVPN BUM traffic forwarding rules to forward subsequent BUM traffic 15 from EVPN 23 and into the VXLAN tunnels of underlay network 17 A.
- multiple S,G distribution trees are transparently created and rooted on potentially multiple EVPN routing instances of multi-homed PEs 6 A and are utilized in an active-active, EVPN environment of FIG. 1 .
- any transit router e.g, R 1 or R 2
- underlay network 17 A will only forward a BUM packet if the router received the BUM packet on an input interface that is facing the packet's source according to the internal IPG routing information, which in this case the root PE 6 A or PE 6 A′ for the particular (S,G) multicast distribution tree on which the multicast traffic is expected to be received.
- RPF reverse path forwarding
- router R 1 drops any BUM traffic 15 ′ received on an interface that is not directed upstream along a path to PE 6 A, i.e., the root of the multicast distribution tree on which router R 1 expects to receive the BUM traffic.
- the RFP check performed by PIM-SM executing on individual routers within underlay network 17 A ensures that the routers only forward copies of BUM traffic 15 received on interfaces designated as upstream interfaces the source of the (S,G) tree.
- BUM traffic 15 stops for a threshold period of time relevant PIM state described above may time out and be cleared, and any subsequent BUM packets 15 will trigger the above process again.
- the techniques allow an EVPN all-active interconnect 23 between data centers 5 to be used even when the data center multicast underlay networks 17 are running PIM sparse mode (SM) for transporting multicast traffic.
- SM PIM sparse mode
- multiple PEs 6 attached to the same data center 5 A or 5 B can be configured with the same anycast IP address, which may provide stability to all unicast entries injected into a given data center from other data centers. This allows PEs 6 A, 6 A′ to appear in the routing domain (e.g., IGP) of remote data 5 B center as a single host.
- IGP routing domain
- the techniques herein provide Protocol Independent Multicast Sparse Mode (PIM-SM) support for an active-active, multi-homed EVPN data center interconnect between multiple physical data centers.
- PIM-SM Protocol Independent Multicast Sparse Mode
- the techniques may readily be applied to any data center, e.g., data center 5 B, having active-active, multi-homed PEs 6 B, 6 B′ coupled to EVPN 23 .
- a single PE of an EVPN acts as the designated forwarder of BUM traffic and no other PE of the multi-homed, active-active EVPN forwards BUM traffic into the data center, thereby seeking to prevent packet forwarding loops and receipt of multiple copies of individual BUM packets.
- this disclosure describes techniques that allow each PE 6 of a multi-homed segment 14 , regardless of DF election, to sends BUM traffic from EVPN 23 toward the local data center 5 and rely upon the operation of the RPF check of PIM-SM applied by transit routers of underlay networks 17 to prevent packet forwarding loops and receipt of multiple copies of individual BUM frames within the data centers.
- FIG. 3 is a block diagram illustrating an exemplary router 80 capable of performing the disclosed techniques.
- router 80 may operate substantially similar to PEs 6 of FIG. 1
- router 80 includes interface cards 88 A- 88 N (“IFCs 88 ”) that receive multicast packets via incoming links 90 A- 90 N (“incoming links 90 ”) and send multicast packets via outbound links 92 A- 92 N (“outbound links 92 ”).
- IFCs 88 are typically coupled to links 90 , 92 via a number of interface ports.
- Router 80 also includes a control unit 82 that determines routes of received packets and forwards the packets accordingly via IFCs 88 .
- Control unit 82 may comprise a routing engine 84 and a packet forwarding engine 86 .
- Routing engine 84 operates as the control plane for router 80 and includes an operating system that provides a multi-tasking operating environment for execution of a number of concurrent processes.
- Routing engine 84 may implement one or more routing protocol 102 to execute routing processes.
- routing protocols 102 may include Border Gateway Protocol (BGP) 103 , for exchanging routing information with other routing devices and for updating routing information 94 .
- routing protocols 102 may include PIM 104 , and specifically PIM-SM, for routing multicast traffic in accordance with the techniques described herein.
- Routing information 94 may describe a topology of the computer network in which router 80 resides, and may also include routes through the shared trees in the computer network. Routing information 94 describes various routes within the computer network, and the appropriate next hops for each route, i.e., the neighboring routing devices along each of the routes. Routing engine 84 analyzes stored routing information 94 and generates forwarding information 106 for forwarding engine 86 . Forwarding information 106 may associate, for example, network destinations for certain multicast groups with specific next hops and corresponding IFCs 88 and physical output ports for output links 92 . Forwarding information 106 may be a radix tree programmed into dedicated forwarding chips, a series of tables, a complex database, a link list, a radix tree, a database, a flat file, or various other data structures.
- forwarding information 106 includes forwarding rules 107 .
- PIM-SM 104 may generate and store forwarding rules 107 to include modified EVPN BUM traffic forwarding rules. That is, according to forwarding rules 107 , as an active-active PE router for a multi-homed VXLAN, forwarding unit 86 of router 80 may forward BUM traffic from the EVPN 23 into the VXLAN for transports through data centers 5 . In other words, forwarding unit 86 may apply the modified forwarding rules 107 to forward all BUM traffic from EVPN 23 to underlay tunnels of the multi-homed VXLANs within data centers 5 regardless of DF status.
- router 80 illustrated in FIG. 2 is shown for exemplary purposes only. The invention is not limited to this architecture. In other examples, router 80 may be configured in a variety of ways. In one example, some of the functionally of control unit 82 may be distributed within IFCs 88 . In another example, control unit 82 may comprise a plurality of packet forwarding engines operated as slave routers.
- Control unit 82 may be implemented solely in software, or hardware, or may be implemented as a combination of software, hardware, or firmware.
- control unit 82 may include one or more processors which execute software instructions.
- the various software modules of control unit 82 may comprise executable instructions stored on a computer-readable medium, such as computer memory or hard disk.
- the techniques described herein may be implemented in hardware, software, firmware, or any combination thereof.
- Various features described as modules, units or components may be implemented together in an integrated logic device or separately as discrete but interoperable logic devices or other hardware devices.
- various features of electronic circuitry may be implemented as one or more integrated circuit devices, such as an integrated circuit chip or chipset.
- this disclosure may be directed to an apparatus such a processor or an integrated circuit device, such as an integrated circuit chip or chipset.
- the techniques may be realized at least in part by a computer-readable data storage medium comprising instructions that, when executed, cause a processor to perform one or more of the methods described above.
- the computer-readable data storage medium may store such instructions for execution by a processor.
- a computer-readable medium may form part of a computer program product, which may include packaging materials.
- a computer-readable medium may comprise a computer data storage medium such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), Flash memory, magnetic or optical data storage media, and the like.
- RAM random access memory
- ROM read-only memory
- NVRAM non-volatile random access memory
- EEPROM electrically erasable programmable read-only memory
- Flash memory magnetic or optical data storage media, and the like.
- an article of manufacture may comprise one or more computer-readable storage media.
- the computer-readable storage media may comprise non-transitory media.
- the term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal.
- a non-transitory storage medium may store data that can, over time, change (e.g., in RAM or cache).
- the code or instructions may be software and/or firmware executed by processing circuitry including one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other equivalent integrated or discrete logic circuitry.
- DSPs digital signal processors
- ASICs application-specific integrated circuits
- FPGAs field-programmable gate arrays
- processors may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein.
- functionality described in this disclosure may be provided within software modules or hardware modules.
- FIG. 3 is a flow diagram illustrating example operation of a router, such as any of PE routers 6 of FIG. 1 , in accordance with the techniques described herein.
- a router receives configuration information specifying BUM traffic forwarding rules as described herein ( 100 ).
- the forward rules may, for example, specify that when operating as a VTEP for a VXLAN of a data center that is connected to a remote data center via an EVPN, the router is to forward BUM traffic from the EVPN into the VXLAN toward the data center according to EVPN BUM forwarding rules regardless of whether the router is configured as a designated forwarder (DF) for a plurality of multi-homed routers coupling the data center to the EVPN.
- the router may receive the configuration information from a centralized controller, such as a software defined networking (SDN) controller, from a management system via a configuration protocol (e.g., SNMP), from a local interface or other example mechanisms.
- SDN software defined networking
- SNMP configuration protocol
- the router operates as a VTEP to establish VXLAN tunnels established using protocol independent multicast-sparse mode (PIM-SM) with transport routers within the data center ( 102 ).
- PIM-SM protocol independent multicast-sparse mode
- the router establishes a layer two (L2) data center interconnect (DCI) between the data center running the VXLAN and the second, remote data center ( 104 ).
- the DCI may, for example, be established using an Ethernet virtual private network (EVPN).
- EVPN Ethernet virtual private network
- the router operates as one of a plurality of active-active routers that provided multihomed connectivity for the VXLAN of the data center to the EVPN DCI providing connectivity to the remote data center.
- the router may receive BUM (broadcast, unknown unicast, and multicast) traffic from the remote data center by way of the EVPN DCI ( 106 ).
- BUM broadcastcast, unknown unicast, and multicast
- multiple (S,G) multicast distribution trees may be transparently created with each of the trees rooted on a different EVPN routing instances of a multi-homed, active-active PE router. Moreover, this may occur even for routers that are not designated forwarders for the multi-homed PE routers operating as an Ethernet segment for the EVPN.
- Each of the router operating as a root for the (S,G) multicast distribution tree operates to forward BUM traffic into the VXLAN toward the first data center according to EVPN BUM forwarding rules, wherein the EVPN BUM forwarding rules specify that any of the multi-homed PE routers may forward the BUM traffic into the VXLAN regardless of which of the PE routers is the DF ( 108 ).
- the EVPN BUM forwarding rules specify that any of the multi-homed PE routers may forward the BUM traffic into the VXLAN regardless of which of the PE routers is the DF ( 108 ).
- any of the routers may forward the BUM traffic into an appropriate VXLAN tunnel even though the router is not the designated forwarder for the EVPN.
- reverse path forwarding (RPF) check utilized within PIM-SM is leveraged to filter any redundant copies of BUM traffic received from the EVPN prior to the copies being delivered to the destinations.
- RPF reverse path forwarding
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
Techniques are described for utilizing Protocol Independent Multicast Sparse Mode (PIM-SM) to transport BUM (broadcast, unknown unicast, and multicast) traffic in a Virtual Extensible LAN (VXLAN) underlay of a data center, where the BUM traffic is received on active-active, multi-homed Ethernet virtual private network (EVPN) interconnects between multiple physical data centers. For example, the techniques may readily be applied to support usage of PIM-SM where provider edge (PE) routers of the EVPN operate as gateways between the EVPN and the VXLAN spanning the data center interconnect.
Description
- This application is a continuation of U.S. application Ser. No. 14/580,185, filed Dec. 22, 2014, which claims the benefit of U.S. Provisional Application No. 62/067,362, filed Oct. 22, 2014, the entire contents of both of which are incorporated herein by reference.
- The invention relates to computer networks and, more specifically, to forwarding multicast traffic within data centers.
- A data center is a specialized facility that provides data serving and backup as well as other network-based services for subscribers and other entities. A data center in its most simple form may consist of a single facility that hosts all of the infrastructure equipment, such as networking and storage systems, servers, redundant power supplies, and environmental controls.
- More sophisticated data centers may be provisioned for geographically dispersed organizations using subscriber support equipment located in various physical hosting facilities (sites). As a result, techniques have been developed to interconnect two more physical data centers to form a single, logical data center. One example layer two (L2) interconnect is an Ethernet virtual private network (EVPN) interconnect through an intermediate network coupling multiple physical data centers.
- This disclosure describes techniques for supporting Protocol Independent Multicast Sparse Mode (PIM-SM) to transport traffic in a Virtual Extensible LAN (VXLAN) underlay of a data center, where the BUM traffic is received on active-active, multi-homed Ethernet virtual private network (EVPN) interconnects between multiple physical data centers. For example, the techniques may readily be applied to support usage of PIM-SM where provider edge (PE) routers of the data centers operate as gateways between the VXLAN and the EVPN spanning the data center interconnect. In this example environment, the VXLAN may be multi-homed to provide protection and load balancing, and in some situations is may be desirable to utilize PIM-SM to deliver so-called “BUM” traffic, i.e., broadcast, unknown unicast and multicast traffic in the VXLAN.
- In one example, a method comprises: establishing an Ethernet virtual private network (EVPN) data center interconnect (DCI) between a first data center running a virtual extensible local area network (VXLAN) and a second data center, wherein the VXLAN of the first data center is active-active multi-homed to two or more provider edge (PE) routers of the EVPN and includes VXLAN tunnels established using protocol independent multicast-sparse mode (PIM-SM). The method further includes receiving, with one of the two or more multi-homed PE routers from the EVPN, BUM (broadcast, unknown unicast, and multicast) traffic, wherein the one of the two or more multi-homed PE routers is not a designated forwarder (DF), and forwarding the BUM traffic from the one of the two or more multi-homed PE routers into the VXLAN toward the first data center according to EVPN BUM forwarding rules.
- In another example, a router comprises a routing engine having a processor executing an Ethernet virtual private network (EVPN) protocol to establish a data center interconnect (DCI) between a first data center running a virtual extensible local area network (VXLAN) and a second data center using an Ethernet virtual private network (EVPN). The router is one of a plurality of active-active routers multi-homed to the data center and providing the EVPN DCI, and wherein the routers establish VXLAN tunnels to transport traffic through the first data center using protocol independent multicast-sparse mode (PIM-SM). The one of the two or more multi-homed PE routers is not a designated forwarder (DF). The router further includes a forwarding engine having a plurality of network interfaces to receive BUM (broadcast, unknown unicast, and multicast) traffic and forward the BUM traffic from the one of the two or more multi-homed PE routers into the VXLAN toward the first data center according to EVPN BUM forwarding rules.
- In another example, a computer-readable medium comprising instruction that cause a processor of a router of a plurality of active-active multi-homed routers of an Ethernet virtual private network (EVPN) to establish, with the processor of the router, a data center interconnect (DCI) between a first data center running a virtual extensible local area network (VXLAN) and a second data center using the EVPN, wherein the VXLAN is active-active multi-homed to the plurality of routers of the EVPN and includes VXLAN tunnels established using protocol independent multicast-sparse mode (PIM-SM) between the first data center and the two or more multi-homed PE routers. The instruction further cause the computer-readable medium to program, with the processor of the router, a forwarding unit of the router to: receive, with one of the two or more multi-homed PE routers from the EVPN, BUM (broadcast, unknown unicast, and multicast) traffic; and forward the BUM traffic from the router into the VXLAN toward the first data center according to EVPN BUM forwarding rules specifying that any of the multi-homed PE routers are to forward the BUM traffic into the VXLAN regardless of which of the PE routers is the specified as a designated forwarder (DF) for the EVPN
- The details of one or more examples are set forth in the accompanying drawings and the description below.
-
FIG. 1 is a block diagram illustrating an example network system in which routers provide Protocol Independent Multicast Sparse Mode (PIM-SM) support for data center interconnect between multiple physical data centers. -
FIGS. 2A-2C are block diagrams illustrating in further detail portions of the example network system ofFIG. 1 . -
FIG. 3 is a block diagram illustrating an exemplary router capable of performing the disclosed techniques. -
FIG. 4 is a flow diagram illustrating example operation of a router in accordance with the techniques described herein. -
FIG. 1 is a block diagram illustrating an example network system in which routers provide Protocol Independent Multicast Sparse Mode (PIM-SM) support for data center interconnect between multiple physical data centers. In this example,data centers 5A-5B (collectively, “data centers 5”) are networks having specialized facilities that provide storage, management, and dissemination of data to subscribers and other entities. In the example ofFIG. 1 ,data centers servers data centers - In this example, data centers 5 are interconnected by a wide area network (WAN). In general,
WAN 4 represents a layer three (L3) network and may include multiple intermediate routing and switching devices (not shown) that transport data traffic over links between data centers 5. For example,wide area network 4 may implement Multiprotocol Label Switching (MPLS) techniques and may be referred to as an MPLS/IP network. While described as a wide area network,WAN 4 may represent any network capable of transmitting traffic exchanged between provider edge routers (PEs) 6. - For example, provider edge routers (PEs) 6A, 6A′, 6B and 6B′ (collectively, “PEs 6”) may utilize Ethernet VPN (E-VPN) technology through
WAN 4 to provide an EVPN data center interconnect (DCI) betweendata centers - In particular, each of PEs 6 provide the EVPN 23 to transport L2 communications, such as Ethernet packets or “frames,” through
WAN 4 for different customers of data centers 5. That is, various customer networks provided within data centers 5 may be virtually isolated onto different Virtual Extensible LANs (VXLANs) 14. As shown inFIG. 1 , each of data centers 5 includes anunderlay network - In this way, PEs 6 provide an active-active, multi-homed EVPN/VXLAN data center interconnect (DCI) between data centers 5. As such, each of PEs 6 operates as gateway between EVPN 23 and VXLANs, and may function as VXLAN Tunnel Endpoints (shown as “VTEP” in
FIG. 1 ). That is, each PE 6 may include logically separate routing instances for VXLAN 14 and EVPN 23 and each operates to bridge traffic between the two distinct internal routing instances. Further example structural and functional details of the EVPN/VXLAN DCI implemented by PE routers 6 are described in “VXLAN DCI Using EVPN,” draft-boutros-12vpn-vxlan-evpn-04.txt, Internet Engineering Task Force (IETF), Jul. 2, 2014, the entire contents of which are incorporated herein by reference. - As shown in
FIG. 1 , eachdata center WAN 4 for redundancy and load balancing. That is,PE routers multi-homed VXLAN 14A to provide L2 connectively to customer edge router (CE) 18A ofdata center 5A. Similarly,PE routers multi-homed Ethernet segment 14B to provide L2 connectively to CE 18B ofdata center 5B. As an all-active multi-homing of the VXLAN network to MPLS/IP WAN network 4, traffic from a VTEP can arrive at any of PEs 6 of that Ethernet segment 14 and can be forwarded accordingly over the MPLS/IP WAN network 4. Furthermore, traffic destined to a VTEP can be received over the MPLS/IP network at any of the PEs connected to the VXLAN network and be forwarded accordingly. In some examples, the VXLAN network may alternatively be a NVGRE network. - When forwarding L2 communications (e.g., VXLAN packets) traversing EVPN 23, PEs 6 learn L2 state information for the L2 customer networks within data centers 5. The L2 state information may include media access control (MAC) addressing information associated with the network devices and customer equipment (e.g., virtual machines) within data centers 5 and the ports and/or pseudowire of the PE through which the customer devices are reachable. PEs 6 typically store the MAC addressing information in L2 learning tables associated with each of their interfaces.
- With active-active multi-homing, PEs 6 of a multi-homed Ethernet segment connected to the same logical VXLAN are typically configured with a common anycast address. For example,
PEs FIG. 1 would typically be configured with the same common anycast address for the underlay tunnels through underlay networks 17. As such,PEs PE WAN 4 and also from routers within local VXLAN underlay networks 17. This may be advantageous, for example, to avoid MAC learning flip-flopping on remote VTEPs (e.g.,PEs PEs - In general, routers within underlay network 17 as well as CEs 18 and PEs 6 execute a multicast routing protocol such as protocol independent multicast (PIM) to control transport of multicast traffic within each data center 5. In some examples, the routers may support both Protocol Independent Multicast Bidirectional Mode (PIM-BIDIR) and Protocol Independent Multicast Sparse Mode (PIM-SM).
- With respect to broadcast, unknown unicast or multicast L2 traffic, so called “BUM” traffic, received from the
EVPN 23 ofWAN 4, one of the PEs 6 ofEVPN 23 is elected as the designated forwarder (DF), and conventionally only the DF is allowed to forward BUM traffic to the VXLAN according to EVPN BUM traffic forwarding rules. To transport BUM traffic within the VXLAN underlay networks, PIM-BIDIR is commonly used because the protocol is compatible with use of a common anycast address assigned to multiple PEs in the active-active mode. In some environments, however, it is desirable to also support or otherwise utilize PIM-SM within underlay networks for delivery of BUM traffic received fromEVPN 23. However, conventionally, PIM-SM is generally not compatible with active-active, multi-homed EVPN environments that, for example, use a common anycast addresses for multiple PEs. - This disclosure describes techniques that allow PIM-SIM to be used in network topologies having an EVPN/VXLAN DCI when the VXLAN networks are multi-homed to EVPN PEs working in all-active mode (e.g.,
FIG. 1 ). As described herein, multi-homed PEs 6 configure forwarding planes therein to apply modified EVPN BUM traffic forwarding rules in a manner that allows PIM-SM to be utilized within VXLANs 14 even though active-active pairs of PEs 6 for each data center 5 share a common anycast address. Moreover, the techniques ensure thatBUM traffic 15 received fromEVPN 23 can be delivered to all the remote VTEPs in the VXLAN underlay network 17. That is, if configured by an administrator or management system, PEs 6, whether operating as a DF or non-DF forEVPN 23,forward BUM traffic 15 from theEVPN 23 into the VXLAN for transport through data centers 5. In other words, when underlay network 17 is configured to operate using PIM-SM, PE routers 6 may automatically configure their respective forwarding hardware (referred to herein as forwarding units or data planes) to operate according to modified forwarding rules that specify that all PE routers forward all BUM traffic fromEVPN 23 to underlay tunnels of VXLAN underlay network 17 traversing data centers 5 regardless of which of the PE routers for each Ethernet segment 14 is elected as DF for that segment. - For example, as described in further detail below, the techniques described by which multiple ones of the active-active,
multi-homed PEs BUM traffic 15 throughVXLAN 14A. In this way,PEs subsequent BUM traffic 15 fromEVPN 23 and into the VXLAN tunnels ofunderlay network 17A. As such, without changing the PIM protocols, multiple distribution trees are transparently created and rooted on potentially multiple EVPN routing instances ofmulti-homed PEs FIG. 1 . Moreover, as further described below, the techniques leverage reverse path forwarding (RPF) check utilized within PIM-SM to ensure that duplicate copies ofBUM traffic 15 will be filtered out by the transport routers prior to the multiple copies reaching their destinations (e.g.,servers 9A orSAN 14A). -
FIGS. 2A-2C are block diagrams illustrating in further detail portions of the example network system ofFIG. 1 in accordance with the techniques described herein. As shown inFIG. 2A , initially, all VTEPs for a local VXLAN, including VTEP routing instances executing on any transport routers of underlay networks 17 and PEs 6 for that VXLAN, issue (*,G) PIM joins 13 to initiate multicast traffic for a multicast group (G). Specifically, initial PIM joins 13 from VTEP instances for a VXLAN are directed to a designated Rendezvous Point (RP) 11 for the multicast group for that particular VXLAN. As further described below,RP 11 is a router or other device that has been designated to acts as a shared root for a (*,G) multicast tree that will be, or has been, constructed for subsequent injection of multicast traffic for the multicast group into the VXLAN. In general, multicast traffic sent from a sender is typically tunneled toRP 11, and such tunneled traffic is referred to as “non-native” multicast traffic, whichRP 11 would in turn forward as a shared root on the (*,G) distribution tree for a given multicast group (G). Although shown separately from PE routers 6,RP 11 may configured to execute on any of PE routers 6 or on a separate device. - When copies of a
first BUM packet 15 associated with the requested multicast flow arrive on the EVPN routing instance of PE routers 6, all receiving EVPN PEs 6 will send PIM registermessages 21 to theRP 11 as an indication that the particular multicast traffic is now being received at the particular PE router and that the PE router may now operate as a particular source (S) for the multicast traffic with respect to the PIM-based distribution of the traffic withindata center 5A. The multicast flow associated withBUM traffic 15 may be uniquely identified within thePIM register messages 21 as a combination of an anycast address assigned to PEs 6 forEVPN 23 and the multicast group, i.e., an (S,G) PIM register message, where S is set to the anycast address of themulti-homed VXLAN 14A. Moreover, each ofPIM register messages 21 may have a source address of the sending interface of the PE router instead of the anycast address on the PE 6 that originated the PIM register message. In this way,RP 11 may be able to uniquely associate each ofPIM messages 21 with the sender, i.e., a respective one ofPE routers 6A. - Upon receiving a (S,G)
PIM register message 21,RP 11 selects one of the multi-homed, active-active PE routers messages 21 have been received and sends an (S,G) PIM join 25 for the flow uniquely identified in the PIM register message by the combination of the EVPN anycast address ofPE routers request 25 may be directed toward a closest one of themulti-homed PEs active EVPN 23, where “closest” refers to the lowest weight route fromRP 11 to any of the PEs based on a standard path computation (e.g., OSPF path computation) performed on the network domain. - As shown in
FIG. 2B , in response, the receiving one ofPEs subsequent BUM traffic 15 for the identified flow natively (i.e., as native multicast without encapsulation) to RP, which in turn distributes the BUM traffic into data center 5 on the (*,G) PIM multicast distribution tree. While receiving thenative traffic 15′ and temporarily operating as a root for the (*,G) distribution tree intodata center 5A,RP 11 will send respective register-stop messages to any of PEs 6 that subsequently send register messages specifying the same multicast flow (e.g., register-stop message 27 sent toPE 6A′). As such, only onePE VXLAN 14A ofEVPN 23. Moreover, only one of the active-active routers PE 6 switches to native forwarding ofBUM traffic 15 toRP 11, which in the example ofFIG. 1 isPE router 6A. That is, in this example,PE 6A receives PIM join 25 fromRP 11 for the specific multicast group, anycast address combination andPE router 6A′ receives register-stop message 27 for the combination. As such, upon receiving these messages,PE router 6A switches to native forwarding allsubsequent BUM traffic 15 for the combination toRP 11, andRP 11 in turn forwards the BUM traffic along the (*,G) distribution tree so as to inject BUM traffic into the VXLAN ofdata center 5A.PE router 6A′, upon receiving register-stop message 27 stops issuingsubsequent register messages 21. In this way,RP 11 operates as temporary (*,G) surrogate for the (anycast,G) source of the multicast traffic for forwarding the traffic within VXLAN ofdata center 5A and theunderlying transport network 17A. - In one example implementation,
PE routers initial BUM packets 15 within PIMregister messages 21 directed toRP 11. In such examples, prior toRP 11 receiving the first natively sentBUM traffic 15 from any ofPEs VXLAN 14A,RP 11 extracts the BUM packets encapsulated inregister messages 21 and forwards the BUM traffic along the (*,G) multicast distribution tree. This may have the benefit of avoiding any loss ofinitial BUM traffic 15 whileRP 11 issues PIM join 25 to one ofPEs 6A, i.e.,PE 6A′ in the example ofFIG. 1 . However, this example implementation may also cause duplicate copies of initial BUM packets extracted fromPIM register messages 21 received from bothPE 6A andPE 6A′. This occurrence, however, will be transient and will stop as soon as the first native BUM packet 1 is received byRP 11. If transient duplication is a concern, some example implementations may utilize a null form ofPIM register messages 21 that do not encapsulateBUM packets 15, but this implementation may lead to transient loss ofinitial BUM packets 15. To avoid packet loss and duplication,multi-homed PEs PIM register messages 21 toRP 11 as soon as initial provisioning is completed to pre-build and maintain state for multicast flows to be injected into the VXLAN ofdata center 5A. - Next, as shown in
FIG. 2C , when any of the VTEPs forVXLAN 17A (e.g., any ofPEs transport network 17A acting as a VTEP), receivenative multicast traffic 15 fromRP 11 on the (*,G) distribution tree, the VTEP outputs PIM joins 31 for the particular (S,G) combination, where S is set to the anycast address for the VXLAN and G is set to the multicast group. As shown inFIG. 2C , each PIM join 31 is routed to the closest PE, i.e., any one of PE's 6A, 6A′ that is closest to respective VTEP, where “closest” again refers to a lowest weight route that is selected from the VTEP to one of the PEs based on a standard path computation performed on the network domain. As such,multiple PEs PEs subsequent BUM traffic 15 for the (S,G) intodata center 5A. In this way, multiple (S,G) distribution trees may be created, one for each of the PEs that is a closest PE to one of the VTEPs. In other words, according to PIM-SM, every VTEP sends an (S,G) PIM join 31, where S is the anycast address and G is the multicast Group. In turn, each receivingPE - In the example of
FIG. 2C , each of thePEs BUM traffic 15 intodata center 5A. As a result, handoff from the (*,G) distribution tree rooted atRP 11 to the multiple, (S,G) trees rooted atPEs BUM traffic 15 may be triggered onmultiple PEs multi-homed PEs subsequent BUM traffic 15 fromEVPN 23 and into the VXLAN tunnels ofunderlay network 17A. As such, without changing the PIM protocols, multiple S,G distribution trees are transparently created and rooted on potentially multiple EVPN routing instances ofmulti-homed PEs 6A and are utilized in an active-active, EVPN environment ofFIG. 1 . - Moreover, the techniques described herein leverage reverse path forwarding (RPF) check utilized within PIM-SM by which any transit router (e.g, R1 or R2) within
underlay network 17A will only forward a BUM packet if the router received the BUM packet on an input interface that is facing the packet's source according to the internal IPG routing information, which in this case theroot PE 6A orPE 6A′ for the particular (S,G) multicast distribution tree on which the multicast traffic is expected to be received. For example, applying RPF, router R1 drops anyBUM traffic 15′ received on an interface that is not directed upstream along a path toPE 6A, i.e., the root of the multicast distribution tree on which router R1 expects to receive the BUM traffic. As such, even though multiple copies ofnative BUM traffic 15 may be injected intounderlay networks 17A from active-active PE routers servers 9A orSAN 14A) as the transport routers apply RFP check when transporting the packets using PIM-SM. - As such, the RFP check performed by PIM-SM executing on individual routers within
underlay network 17A ensures that the routers only forward copies ofBUM traffic 15 received on interfaces designated as upstream interfaces the source of the (S,G) tree. In theevent BUM traffic 15 stops for a threshold period of time, relevant PIM state described above may time out and be cleared, and anysubsequent BUM packets 15 will trigger the above process again. - In this way, the techniques allow an EVPN all-
active interconnect 23 between data centers 5 to be used even when the data center multicast underlay networks 17 are running PIM sparse mode (SM) for transporting multicast traffic. As such, multiple PEs 6 attached to thesame data center PEs remote data 5B center as a single host. - As such, the techniques herein provide Protocol Independent Multicast Sparse Mode (PIM-SM) support for an active-active, multi-homed EVPN data center interconnect between multiple physical data centers. Although described with respect to BUM traffic flowing from
EVPN 23 into the VXLAN ofdata center 5A, the techniques may readily be applied to any data center, e.g.,data center 5B, having active-active,multi-homed PEs - As discussed above, in a typical EVPN configuration, a single PE of an EVPN acts as the designated forwarder of BUM traffic and no other PE of the multi-homed, active-active EVPN forwards BUM traffic into the data center, thereby seeking to prevent packet forwarding loops and receipt of multiple copies of individual BUM packets. Moreover, it may be desirable to configured active-active, multi-homed EVPN PEs of an Ethernet segment with the same anycast address for stability with respect to remote routing domains. Conventional PIM SM protocol in which transport routers apply a reverse path forwarding (RPF) check causes the transit routers to only forward a BUM packet if the router received the BUM packet on an input interface that is toward the packet's source, which in conventional configuration is the IP anycast address configured on each of the PEs. As a result, if only one PE is selected as DF, conventional techniques cause some number of transit routers to discard a given BUM packet because it was received on what the transit router decides is an invalid input interface. As described, this disclosure describes techniques that allow each PE 6 of a multi-homed segment 14, regardless of DF election, to sends BUM traffic from
EVPN 23 toward the local data center 5 and rely upon the operation of the RPF check of PIM-SM applied by transit routers of underlay networks 17 to prevent packet forwarding loops and receipt of multiple copies of individual BUM frames within the data centers. -
FIG. 3 is a block diagram illustrating anexemplary router 80 capable of performing the disclosed techniques. In general,router 80 may operate substantially similar to PEs 6 ofFIG. 1 - In this example,
router 80 includesinterface cards 88A-88N (“IFCs 88”) that receive multicast packets viaincoming links 90A-90N (“incoming links 90”) and send multicast packets via outbound links 92A-92N (“outbound links 92”). IFCs 88 are typically coupled to links 90, 92 via a number of interface ports.Router 80 also includes acontrol unit 82 that determines routes of received packets and forwards the packets accordingly via IFCs 88. -
Control unit 82 may comprise arouting engine 84 and apacket forwarding engine 86. Routingengine 84 operates as the control plane forrouter 80 and includes an operating system that provides a multi-tasking operating environment for execution of a number of concurrent processes. Routingengine 84 may implement one ormore routing protocol 102 to execute routing processes. For example,routing protocols 102 may include Border Gateway Protocol (BGP) 103, for exchanging routing information with other routing devices and for updatingrouting information 94. In addition,routing protocols 102 may includePIM 104, and specifically PIM-SM, for routing multicast traffic in accordance with the techniques described herein. - Routing
information 94 may describe a topology of the computer network in whichrouter 80 resides, and may also include routes through the shared trees in the computer network. Routinginformation 94 describes various routes within the computer network, and the appropriate next hops for each route, i.e., the neighboring routing devices along each of the routes. Routingengine 84 analyzes stored routinginformation 94 and generates forwardinginformation 106 for forwardingengine 86.Forwarding information 106 may associate, for example, network destinations for certain multicast groups with specific next hops and corresponding IFCs 88 and physical output ports for output links 92.Forwarding information 106 may be a radix tree programmed into dedicated forwarding chips, a series of tables, a complex database, a link list, a radix tree, a database, a flat file, or various other data structures. - In the illustrated example of
FIG. 2 , forwardinginformation 106 includes forwarding rules 107. For example, PIM-SM 104 may generate and store forwardingrules 107 to include modified EVPN BUM traffic forwarding rules. That is, according to forwardingrules 107, as an active-active PE router for a multi-homed VXLAN, forwardingunit 86 ofrouter 80 may forward BUM traffic from theEVPN 23 into the VXLAN for transports through data centers 5. In other words, forwardingunit 86 may apply the modifiedforwarding rules 107 to forward all BUM traffic fromEVPN 23 to underlay tunnels of the multi-homed VXLANs within data centers 5 regardless of DF status. - The architecture of
router 80 illustrated inFIG. 2 is shown for exemplary purposes only. The invention is not limited to this architecture. In other examples,router 80 may be configured in a variety of ways. In one example, some of the functionally ofcontrol unit 82 may be distributed within IFCs 88. In another example,control unit 82 may comprise a plurality of packet forwarding engines operated as slave routers. -
Control unit 82 may be implemented solely in software, or hardware, or may be implemented as a combination of software, hardware, or firmware. For example,control unit 82 may include one or more processors which execute software instructions. In that case, the various software modules ofcontrol unit 82 may comprise executable instructions stored on a computer-readable medium, such as computer memory or hard disk. - The techniques described herein may be implemented in hardware, software, firmware, or any combination thereof. Various features described as modules, units or components may be implemented together in an integrated logic device or separately as discrete but interoperable logic devices or other hardware devices. In some cases, various features of electronic circuitry may be implemented as one or more integrated circuit devices, such as an integrated circuit chip or chipset.
- If implemented in hardware, this disclosure may be directed to an apparatus such a processor or an integrated circuit device, such as an integrated circuit chip or chipset. Alternatively or additionally, if implemented in software or firmware, the techniques may be realized at least in part by a computer-readable data storage medium comprising instructions that, when executed, cause a processor to perform one or more of the methods described above. For example, the computer-readable data storage medium may store such instructions for execution by a processor.
- A computer-readable medium may form part of a computer program product, which may include packaging materials. A computer-readable medium may comprise a computer data storage medium such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), Flash memory, magnetic or optical data storage media, and the like. In some examples, an article of manufacture may comprise one or more computer-readable storage media.
- In some examples, the computer-readable storage media may comprise non-transitory media. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in RAM or cache).
- The code or instructions may be software and/or firmware executed by processing circuitry including one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, in some aspects, functionality described in this disclosure may be provided within software modules or hardware modules.
-
FIG. 3 is a flow diagram illustrating example operation of a router, such as any of PE routers 6 ofFIG. 1 , in accordance with the techniques described herein. - Initially, a router receives configuration information specifying BUM traffic forwarding rules as described herein (100). The forward rules may, for example, specify that when operating as a VTEP for a VXLAN of a data center that is connected to a remote data center via an EVPN, the router is to forward BUM traffic from the EVPN into the VXLAN toward the data center according to EVPN BUM forwarding rules regardless of whether the router is configured as a designated forwarder (DF) for a plurality of multi-homed routers coupling the data center to the EVPN. The router may receive the configuration information from a centralized controller, such as a software defined networking (SDN) controller, from a management system via a configuration protocol (e.g., SNMP), from a local interface or other example mechanisms.
- Once configured and operational, the router operates as a VTEP to establish VXLAN tunnels established using protocol independent multicast-sparse mode (PIM-SM) with transport routers within the data center (102). In addition, the router establishes a layer two (L2) data center interconnect (DCI) between the data center running the VXLAN and the second, remote data center (104). The DCI may, for example, be established using an Ethernet virtual private network (EVPN). As such, the router operates as one of a plurality of active-active routers that provided multihomed connectivity for the VXLAN of the data center to the EVPN DCI providing connectivity to the remote data center.
- Once the EVPN has been established, the router may receive BUM (broadcast, unknown unicast, and multicast) traffic from the remote data center by way of the EVPN DCI (106). In accordance with the process described above, multiple (S,G) multicast distribution trees may be transparently created with each of the trees rooted on a different EVPN routing instances of a multi-homed, active-active PE router. Moreover, this may occur even for routers that are not designated forwarders for the multi-homed PE routers operating as an Ethernet segment for the EVPN.
- Each of the router operating as a root for the (S,G) multicast distribution tree operates to forward BUM traffic into the VXLAN toward the first data center according to EVPN BUM forwarding rules, wherein the EVPN BUM forwarding rules specify that any of the multi-homed PE routers may forward the BUM traffic into the VXLAN regardless of which of the PE routers is the DF (108). For example, operating as root for an (S,G) multicast distribution tree that has been created, any of the routers may forward the BUM traffic into an appropriate VXLAN tunnel even though the router is not the designated forwarder for the EVPN. Further, as described above, reverse path forwarding (RPF) check utilized within PIM-SM is leveraged to filter any redundant copies of BUM traffic received from the EVPN prior to the copies being delivered to the destinations.
- Various embodiments have been described. These and other embodiments are within the scope of the following examples.
Claims (20)
1: A method comprising:
receiving, by a rendezvous point (RP) for a multicast group and from a first PE router, a first PIM register message for broadcast, unknown unicast, and multicast (BUM) traffic with a multicast flow identified using a combination of a common anycast address and the multicast group;
receiving, by the RP and from a second PE router, a second PIM register message for the BUM traffic with the multicast flow identified using the combination of the common anycast address and the multicast group;
in response to receiving the first PIM register message and the second PIM register message, selecting, by the RP, the first PE router; and
in response to selecting the first PE router:
outputting, by the RP and to the first PE router, a join message for the common anycast address and the multicast group;
forwarding, by the RP, the BUM traffic for the multicast group from the first PE router; and
outputting, by the RP and to the second PE router, a register-stop message for the common anycast address and the multicast group.
2: The method of claim 1 , further comprising:
establishing an Ethernet virtual private network (EVPN) data center interconnect (DCI) between a first data center running a virtual extensible local area network (VXLAN) and a second data center, wherein the VXLAN of the first data center is active-active multi-homed to two or more PE routers of the EVPN and includes VXLAN tunnels established using protocol independent multicast-sparse mode (PIM-SM), wherein the two or more PE routers comprise the first PE router and the second PE router.
3: The method of claim 2 , further comprising receiving, from the two or more PE routers or any one of a plurality of VXLAN tunnel end points (VTEPs), initial join messages to initiate multicast traffic for the multicast group.
4: The method of claim 1 , wherein the second PE router is a designated forwarder (DF) and wherein the first PE router is not a DF.
5: The method of claim 1 , wherein forwarding the BUM traffic comprises:
constructing a multicast distribution tree; and
forwarding the BUM traffic into the multicast distribution tree.
6: The method of claim 1 , wherein the first PIM register message indicates a unique source address of a sending interface of the first PE router, the method further comprising:
associating, by the RP, the first PIM register message with the first PE router based on the unique source address of the sending interface of the first PE router.
7: The method of claim 1 , wherein selecting the first PE router is in response to determining the first PE router is a closest one of two or more PE routers to the RP for the multicast group, wherein the two or more PE routers comprise the first PE router and the second PE router.
8: The method of claim 1 , wherein forwarding the BUM traffic comprises:
natively receiving, by the RP, the BUM traffic from the first PE router without encapsulation; and
forwarding, by the RP, the natively received BUM traffic.
9: The method of claim 1 , wherein the first PIM register message for the BUM traffic encapsulates a packet of the BUM traffic, the method further comprising:
extracting, by the RP, the packet of the BUM traffic from the first PIM register message; and
forwarding, by the RP, the packet of the BUM traffic.
10: The method of claim 1 , wherein the first PIM register message for the BUM traffic comprises a null register message that does not encapsulate a packet of the BUM traffic.
11: A router comprising:
a memory; and
one or more processors coupled to the memory, the one or more processors being configured to:
receive, from a first PE router, a first PIM register message for broadcast, unknown unicast, and multicast (BUM) traffic with a multicast flow identified using a combination of a common anycast address and a multicast group;
receive, from a second PE router, a second PIM register message for the BUM traffic with the multicast flow identified using the combination of the common anycast address and the multicast group;
in response to receiving the first PIM register message and the second PIM register message, select the first PE router; and
in response to selecting the first PE router:
output, to the first PE router, a join message for the common anycast address and the multicast group;
forward the BUM traffic for the multicast group from the first PE router; and
output, to the second PE router, a register-stop message for the common anycast address and the multicast group.
12: The router of claim 11 , wherein the one or more processors are configured to:
establish an Ethernet virtual private network (EVPN) data center interconnect (DCI) between a first data center running a virtual extensible local area network (VXLAN) and a second data center, wherein the VXLAN of the first data center is active-active multi-homed to two or more PE routers of the EVPN and includes VXLAN tunnels established using protocol independent multicast-sparse mode (PIM-SM), wherein the two or more PE routers comprise the first PE router and the second PE router.
13: The router of claim 12 , wherein the one or more processors are configured to receive, from the two or more PE routers or any one of a plurality of VXLAN tunnel end points (VTEPs), initial join messages to initiate multicast traffic for the multicast group.
14: The router of claim 11 , wherein the second PE router is a designated forwarder (DF) and wherein the first PE router is not a DF.
15: The router of claim 11 , wherein, to forward the BUM traffic, the one or more processors are configured to:
construct a multicast distribution tree; and
forward the BUM traffic into the multicast distribution tree.
16: The router of claim 11 , wherein the first PIM register message indicates a unique source address of a sending interface of the first PE router, the one or more processors being configured to:
associate the first PIM register message with the first PE router based on the unique source address of the sending interface of the first PE router.
17: The router of claim 11 , wherein, to select the first PE router, the one or more processors are configured to select the first PE router in response to determining the first PE router is a closest one of two or more PE routers to the RP for the multicast group, wherein the two or more PE routers comprise the first PE router and the second PE router.
18: The router of claim 11 , wherein, to forward the BUM traffic, the one or more processors are configured to:
natively receive the BUM traffic from the first PE router without encapsulation; and
forward, by the RP, the natively received BUM traffic.
19: The router of claim 11 , wherein the first PIM register message for the BUM traffic encapsulates a packet of the BUM traffic, the one or more processors being configured to:
extract the packet of the BUM traffic from the first PIM register message; and
forward the packet of the BUM traffic.
20: A computer-readable medium comprising instruction that cause a processor of a rendezvous point (RP) for a multicast group to:
receive, from a first PE router, a first PIM register message for broadcast, unknown unicast, and multicast (BUM) traffic with a multicast flow identified using a combination of a common anycast address and the multicast group;
receive, from a second PE router, a second PIM register message for the BUM traffic with the multicast flow identified using the combination of the common anycast address and the multicast group;
in response to receiving the first PIM register message and the second PIM register message, select the first PE router; and
in response to selecting the first PE router:
output, to the first PE router, a join message for the common anycast address and the multicast group;
forward the BUM traffic for the multicast group from the first PE router; and
output, to the second PE router, a register-stop message for the common anycast address and the multicast group.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/945,671 US20180227135A1 (en) | 2014-10-22 | 2018-04-04 | Protocol independent multicast sparse mode (pim-sm) support for data center interconnect |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201462067362P | 2014-10-22 | 2014-10-22 | |
US14/580,185 US9948472B2 (en) | 2014-10-22 | 2014-12-22 | Protocol independent multicast sparse mode (PIM-SM) support for data center interconnect |
US15/945,671 US20180227135A1 (en) | 2014-10-22 | 2018-04-04 | Protocol independent multicast sparse mode (pim-sm) support for data center interconnect |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/580,185 Continuation US9948472B2 (en) | 2014-10-22 | 2014-12-22 | Protocol independent multicast sparse mode (PIM-SM) support for data center interconnect |
Publications (1)
Publication Number | Publication Date |
---|---|
US20180227135A1 true US20180227135A1 (en) | 2018-08-09 |
Family
ID=54557219
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/580,185 Expired - Fee Related US9948472B2 (en) | 2014-10-22 | 2014-12-22 | Protocol independent multicast sparse mode (PIM-SM) support for data center interconnect |
US15/945,671 Abandoned US20180227135A1 (en) | 2014-10-22 | 2018-04-04 | Protocol independent multicast sparse mode (pim-sm) support for data center interconnect |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/580,185 Expired - Fee Related US9948472B2 (en) | 2014-10-22 | 2014-12-22 | Protocol independent multicast sparse mode (PIM-SM) support for data center interconnect |
Country Status (3)
Country | Link |
---|---|
US (2) | US9948472B2 (en) |
EP (1) | EP3013006A1 (en) |
CN (1) | CN105553848A (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10425325B2 (en) * | 2017-10-30 | 2019-09-24 | Dell Products Lp | Optimizing traffic paths to orphaned hosts in VXLAN networks using virtual link trunking-based multi-homing |
US10749741B1 (en) * | 2019-04-25 | 2020-08-18 | Dell Products L.P. | Methods and systems for auto-discovery of VXLAN VTEPs using PIM BSR |
US11245631B2 (en) | 2016-12-29 | 2022-02-08 | Huawei Technologies Co., Ltd. | Bum traffic control method, related apparatus, and system |
Families Citing this family (64)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR3010599B1 (en) * | 2013-09-11 | 2016-12-02 | Citypassenger | METHOD AND SYSTEM FOR ESTABLISHING VIRTUAL PRIVATE NETWORKS BETWEEN LOCAL NETWORKS |
US10148484B2 (en) | 2013-10-10 | 2018-12-04 | Nicira, Inc. | Host side method of using a controller assignment list |
US9602392B2 (en) | 2013-12-18 | 2017-03-21 | Nicira, Inc. | Connectivity segment coloring |
US9419855B2 (en) | 2014-03-14 | 2016-08-16 | Nicira, Inc. | Static routes for logical routers |
US9647883B2 (en) | 2014-03-21 | 2017-05-09 | Nicria, Inc. | Multiple levels of logical routers |
US9794079B2 (en) | 2014-03-31 | 2017-10-17 | Nicira, Inc. | Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks |
US10079779B2 (en) | 2015-01-30 | 2018-09-18 | Nicira, Inc. | Implementing logical router uplinks |
US9628409B1 (en) * | 2015-03-11 | 2017-04-18 | Juniper Networks, Inc. | Designated forwarder election for multi-homed data center interconnect using multicast routing protocol state information |
US20160380886A1 (en) * | 2015-06-25 | 2016-12-29 | Ciena Corporation | Distributed data center architecture |
US10129142B2 (en) | 2015-08-11 | 2018-11-13 | Nicira, Inc. | Route configuration for logical router |
US10075363B2 (en) | 2015-08-31 | 2018-09-11 | Nicira, Inc. | Authorization for advertised routes among logical routers |
US10095535B2 (en) | 2015-10-31 | 2018-10-09 | Nicira, Inc. | Static route types for logical routers |
US9853915B2 (en) | 2015-11-04 | 2017-12-26 | Cisco Technology, Inc. | Fast fail-over using tunnels |
CN106936939B (en) * | 2015-12-31 | 2020-06-02 | 华为技术有限公司 | Message processing method, related device and NVO3 network system |
US9781029B2 (en) | 2016-02-04 | 2017-10-03 | Cisco Technology, Inc. | Loop detection and prevention |
US10033539B1 (en) * | 2016-03-31 | 2018-07-24 | Juniper Networks, Inc. | Replicating multicast state information between multi-homed EVPN routing devices |
US10050873B2 (en) | 2016-05-17 | 2018-08-14 | Juniper Networks, Inc. | Egress node protection for broadcast, unknown unicast, or multicast traffic in EVPN topologies |
US10153973B2 (en) | 2016-06-29 | 2018-12-11 | Nicira, Inc. | Installation of routing tables for logical router in route server mode |
CN107623636B (en) * | 2016-07-13 | 2020-08-25 | 华为技术有限公司 | User isolation method and switch |
US10454758B2 (en) * | 2016-08-31 | 2019-10-22 | Nicira, Inc. | Edge node cluster network redundancy and fast convergence using an underlay anycast VTEP IP |
JP7158113B2 (en) | 2016-09-26 | 2022-10-21 | ナント ホールディングス アイピー,エルエルシー | Virtual circuit in cloud network |
US10341236B2 (en) | 2016-09-30 | 2019-07-02 | Nicira, Inc. | Anycast edge service gateways |
CN108075969B (en) * | 2016-11-17 | 2020-01-03 | 新华三技术有限公司 | Message forwarding method and device |
US10164876B2 (en) * | 2016-12-09 | 2018-12-25 | Cisco Technology, Inc. | Efficient multicast traffic forwarding in EVPN-based multi-homed networks |
CN106878134B (en) * | 2016-12-16 | 2020-05-12 | 新华三技术有限公司 | Data center intercommunication method and device |
CN108259291B (en) | 2016-12-29 | 2021-01-29 | 华为技术有限公司 | VXLAN message processing method, device and system |
US10389542B2 (en) | 2017-01-26 | 2019-08-20 | International Business Machines Corporation | Multicast helper to link virtual extensible LANs |
US10142239B2 (en) * | 2017-02-27 | 2018-11-27 | Juniper Networks, Inc. | Synchronizing multicast state between multi-homed routers in an Ethernet virtual private network |
CN108574613B (en) * | 2017-03-07 | 2022-05-10 | 中兴通讯股份有限公司 | Two-layer intercommunication method and device for SDN data center |
CN112929273A (en) | 2017-03-14 | 2021-06-08 | 华为技术有限公司 | Method, equipment and system for processing route |
EP3396897B1 (en) * | 2017-03-31 | 2021-09-22 | Juniper Networks, Inc. | Multicast load balancing in multihoming evpn networks |
US10193812B2 (en) * | 2017-03-31 | 2019-01-29 | Juniper Networks, Inc. | Multicast load balancing in multihoming EVPN networks |
US10880112B2 (en) * | 2017-12-31 | 2020-12-29 | Arista Networks, Inc. | Multicast traffic in a virtual extensible local area network (VXLAN) |
EP3735763A4 (en) * | 2018-01-02 | 2021-07-21 | Telefonaktiebolaget LM Ericsson (publ) | Controlling device and method implemented thereon for ethernet virtual private network |
US10536285B2 (en) * | 2018-01-25 | 2020-01-14 | Juniper Networks, Inc. | Multicast join message processing by multi-homing devices in an ethernet VPN |
CN108306825B (en) * | 2018-01-31 | 2021-06-29 | 新华三技术有限公司 | Equivalent forwarding table item generation method and VTEP device |
CN108494686B (en) * | 2018-02-28 | 2021-05-28 | 新华三技术有限公司 | Route processing method and device |
CN108600074B (en) * | 2018-04-20 | 2021-06-29 | 新华三技术有限公司 | Method and device for forwarding multicast data message |
US10999220B2 (en) | 2018-07-05 | 2021-05-04 | Vmware, Inc. | Context aware middlebox services at datacenter edge |
US11184327B2 (en) * | 2018-07-05 | 2021-11-23 | Vmware, Inc. | Context aware middlebox services at datacenter edges |
CN109194560B (en) * | 2018-08-29 | 2021-06-22 | 迈普通信技术股份有限公司 | Multicast method and VTEP |
US10931560B2 (en) | 2018-11-23 | 2021-02-23 | Vmware, Inc. | Using route type to determine routing protocol behavior |
CN111224870B (en) * | 2018-11-26 | 2022-11-18 | 中兴通讯股份有限公司 | Fault repairing method, equipment and storage medium in SR-MPLS Anycast scene |
US11509494B2 (en) * | 2018-11-30 | 2022-11-22 | Cisco Technology, Inc. | Protocol independent multicast (PIM) designated router (DR) election |
US10797998B2 (en) | 2018-12-05 | 2020-10-06 | Vmware, Inc. | Route server for distributed routers using hierarchical routing protocol |
US10938788B2 (en) | 2018-12-12 | 2021-03-02 | Vmware, Inc. | Static routes for policy-based VPN |
US10904035B2 (en) * | 2019-06-03 | 2021-01-26 | Arista Networks, Inc. | Method and system for processing encapsulated wireless traffic |
CN112054962B (en) * | 2019-06-06 | 2021-12-14 | 华为技术有限公司 | Method and device for realizing multicast |
US10778457B1 (en) | 2019-06-18 | 2020-09-15 | Vmware, Inc. | Traffic replication in overlay networks spanning multiple sites |
CN112311645A (en) * | 2019-07-31 | 2021-02-02 | 中兴通讯股份有限公司 | Method, system and first GW for realizing DCI three-layer communication |
CN110505152B (en) * | 2019-09-11 | 2022-02-22 | 迈普通信技术股份有限公司 | Route filtering method and device and electronic equipment |
KR102245989B1 (en) * | 2019-09-23 | 2021-04-29 | 주식회사 다산네트웍솔루션즈 | Redundancy Administrating Method for a Virtual Private Network and Network Switching Apparatus with the method implemented on it |
US11240144B2 (en) * | 2019-09-30 | 2022-02-01 | Juniper Networks, Inc. | Assisted replication in software defined network |
US11153420B2 (en) * | 2019-10-18 | 2021-10-19 | Arista Networks, Inc. | Neighbor equivalence groups |
US11184276B1 (en) * | 2020-05-08 | 2021-11-23 | Ciena Corporation | EVPN signaling using segment routing |
CN114531319A (en) * | 2020-10-31 | 2022-05-24 | 华为技术有限公司 | Message sending method, equipment and system |
US11570116B1 (en) | 2021-03-10 | 2023-01-31 | Juniper Networks, Inc. | Estimating standby socket window size during asynchronous socket replication |
US11546253B2 (en) * | 2021-03-31 | 2023-01-03 | Juniper Networks, Inc | Fast reroute for ethernet virtual private networks—virtual extensible local area network |
US11784922B2 (en) | 2021-07-03 | 2023-10-10 | Vmware, Inc. | Scalable overlay multicast routing in multi-tier edge gateways |
US11855792B2 (en) * | 2021-09-30 | 2023-12-26 | Hewlett Packard Enterprise Development Lp | Multicast rendezvous point deployment in a virtual gateway of a distributed tunnel fabric |
CN114466016B (en) * | 2022-03-04 | 2023-06-09 | 烽火通信科技股份有限公司 | Method and system for realizing dynamic load balancing of data center gateway |
US20230412503A1 (en) * | 2022-03-07 | 2023-12-21 | Juniper Networks, Inc. | Determining unicast addresses of gateway network devices associated with an anycast address in vxlan-evpn dci environments |
US20230299992A1 (en) * | 2022-03-21 | 2023-09-21 | International Business Machines Corporation | Enhanced endpoint multicast emulation |
US20240015095A1 (en) * | 2022-07-11 | 2024-01-11 | Juniper Networks, Inc. | Designating a primary multicast flow and a backup multicast flow for multicast traffic |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7860112B2 (en) * | 2006-02-07 | 2010-12-28 | Juniper Networks, Inc. | Bi-directional forwarding in ethernet-based service domains over networks |
US8259720B2 (en) * | 2007-02-02 | 2012-09-04 | Cisco Technology, Inc. | Triple-tier anycast addressing |
US7894450B2 (en) * | 2007-12-31 | 2011-02-22 | Nortel Network, Ltd. | Implementation of VPNs over a link state protocol controlled ethernet network |
CN103348630B (en) * | 2011-02-18 | 2016-04-13 | 惠普发展公司,有限责任合伙企业 | For controlling the method selected in multicast network |
US9137142B2 (en) * | 2012-03-31 | 2015-09-15 | Juniper Networks, Inc. | Reduced traffic loss for border gateway protocol sessions in multi-homed network connections |
-
2014
- 2014-12-22 US US14/580,185 patent/US9948472B2/en not_active Expired - Fee Related
-
2015
- 2015-10-16 EP EP15190161.8A patent/EP3013006A1/en not_active Withdrawn
- 2015-10-21 CN CN201510686496.7A patent/CN105553848A/en active Pending
-
2018
- 2018-04-04 US US15/945,671 patent/US20180227135A1/en not_active Abandoned
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11245631B2 (en) | 2016-12-29 | 2022-02-08 | Huawei Technologies Co., Ltd. | Bum traffic control method, related apparatus, and system |
US10425325B2 (en) * | 2017-10-30 | 2019-09-24 | Dell Products Lp | Optimizing traffic paths to orphaned hosts in VXLAN networks using virtual link trunking-based multi-homing |
US10749741B1 (en) * | 2019-04-25 | 2020-08-18 | Dell Products L.P. | Methods and systems for auto-discovery of VXLAN VTEPs using PIM BSR |
Also Published As
Publication number | Publication date |
---|---|
EP3013006A1 (en) | 2016-04-27 |
US20160119156A1 (en) | 2016-04-28 |
CN105553848A (en) | 2016-05-04 |
US9948472B2 (en) | 2018-04-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20180227135A1 (en) | Protocol independent multicast sparse mode (pim-sm) support for data center interconnect | |
US10536285B2 (en) | Multicast join message processing by multi-homing devices in an ethernet VPN | |
US10999126B2 (en) | Failure handling for active-standby redundancy in EVPN data center interconnect | |
US11539619B1 (en) | Local-bias forwarding of L2 multicast, unknown unicast, and broadcast traffic for an ethernet VPN | |
US10666561B2 (en) | Virtual machine migration | |
US9590902B2 (en) | Signaling aliasing capability in data centers | |
US9628409B1 (en) | Designated forwarder election for multi-homed data center interconnect using multicast routing protocol state information | |
US9929940B2 (en) | Update of MAC routes in EVPN single-active topology | |
US9860150B2 (en) | Fast convergence of EVPN networks for multi homing topologies | |
EP3188409A1 (en) | Oam mechanisms for evpn active-active services | |
US20150085862A1 (en) | Forwarding Multicast Data Packets | |
US20170063600A1 (en) | Egress protection for bum traffic with link failures in evpn | |
US11329845B2 (en) | Port mirroring over EVPN VXLAN | |
US11349749B2 (en) | Node protection for bum traffic for multi-homed node failure | |
US20150341183A1 (en) | Forwarding multicast data packets | |
US9954694B2 (en) | Traffic black holing avoidance and fast convergence for active-active PBB-EVPN redundancy | |
US7894430B2 (en) | Hub and spoke multicast model | |
CN111064659A (en) | Node protection of BUM traffic for multi-homed node failures | |
US20210297273A1 (en) | Evpn multicast ingress forwarder election using source-active route | |
EP3018866A1 (en) | Signaling aliasing capability in data centers | |
US9602294B1 (en) | Rendezvous point link resiliency for bidirectional protocol independent multicast (PIM-BIDIR) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |