Managing rendezvous point redundancy in a dynamic fabric network architecture
US-2015372827-A1 · Dec 24, 2015 · US
US9166807B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9166807-B2 |
| Application number | US-40478609-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 16, 2009 |
| Priority date | Jul 28, 2005 |
| Publication date | Oct 20, 2015 |
| Grant date | Oct 20, 2015 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Principles of the invention relate to techniques for transmission of Layer 2 (L2) traffic over a point to multi-point (P2MP) label switched path (LSP) within a multi-protocol Label Switching (MPLS) network. A source or ingress network device may implement the techniques to connect multiple L2 interfaces to a P2MP LSP within an MPLS network via a P2MP Pseudo-Wire (PW) mechanism that emulates delivery of L2 data units over a packet switched network, such as the MPLS network. The ingress network device first establishes the P2MP LSP and then connects two or more L2 interfaces to the P2MP LSP via the P2MP PW mechanism. Egress network devices may also implement the techniques to terminate the P2MP LSP and de-multiplex traffic arriving via multiple P2MP PWs carried over the same P2MP LSP.
Opening claim text (preview).
The invention claimed is: 1. A method comprising: establishing, with a source device of a computer network, a point to multi-point (P2MP) label switched path (LSP) that connects the source device to multiple receiver devices included within the computer network, where the source device is configured to operate as an ingress to the P2MP LSP and the multiple receiver devices are configured to operate as egresses for the P2MP; connecting, with the source device, two or more ingress layer two (L2) interfaces of the source device to the P2MP LSP; and forwarding, with the source device, L2 data units from the two or more ingress L2 interfaces to the multiple receiver devices via the P2MP LSP. 2. The method of claim 1 , wherein the two or more ingress L2 interfaces comprise two or more of a plurality of ingress attachment circuits (ACs) of the source device, and wherein connecting the ingress L2 interfaces comprises: for each of the ACs of the source device, signaling, with the source device, a corresponding PW label identifying a P2MP Pseudo Wire (PW) to the multiple receiver devices to establish the plurality of P2MP PWs over the same P2MP LSP; and mapping the plurality of ingress ACs to the P2MP Pseudo Wires (PWs) to connect the plurality of ACs to the P2MP LSP. 3. The method of claim 2 , further comprising connecting the P2MP PW to at least one egress AC within one of the multiple receiver devices. 4. The method of claim 3 , wherein connecting the P2MP PW to at least one egress AC comprises mapping packets received on an incoming link of the receiver device associated with the P2MP PW to the at least one egress AC. 5. The method of claim 2 , wherein forwarding L2 traffic comprises: receiving the L2 data units from one or more L2 networks over the two or more ingress ACs of the source device; selecting, with the source device, an inner label for each of the L2 data units to correspond to the ingress AC of the source device by which the L2 data units was received to identify the P2MP PW; encapsulating each of the L2 data units in a Multi-Protocol Label Switching (MPLS) packet by appending to each of the L2 data units an outer label that identifies the P2MP LSP and the inner label selected for the L2 data unit to identify the P2MP PW; and forwarding the MPLS packets via the P2MP LSP connected to the ingress ACs. 6. The method of claim 5 , further comprising: receiving the MPLS packet from the P2MP LSP with one of the multiple receiver devices, wherein the one of the multiple receiver devices stores first and second mapping data, wherein the first mapping data maps the outer label of the MPLS packet to one of a plurality of context-specific label spaces, wherein the one of the plurality of context-specific label spaces comprises the second mapping data that maps the inner label of the MPLS packet to at least one egress AC of the one of the multiple receiver devices; retreiving the outer and inner labels from the MPLS packet; accessing the first mapping data in response to retrieving the outer label to select the one of the context-specific label spaces associated with the outer label; accessing, in response to selecting the one of the context-specific label spaces, the second mapping to determine, based on the inner label, the at least one egress AC of the one of the multiple receiver devices on which to forward the L2 data units; retrieving the L2 data units encapsulated within the MPLS packet; and forwarding the L2 data units on the at least one egress AC of the one of the multiple receiver devices associated with the inner label. 7. The method of claim 1 , wherein establishing the P2MP LSP comprises: with the source device, automatically discovering the multiple receiver devices; and with the source device, establishing the P2MP LSP to connect the source device to the automatically discovered receiver devices. 8. The method of claim 1 , wherein forwarding L2 traffic comprises: receiving the L2 data units on the two or more ingress L2 interfaces of the source device; encapsulating the L2 data units in a Multi-protocol Label Switching (MPLS) packet; and forwarding the MPLS packet on the P2MP LSP connected to the two or more ingress L2 interfaces. 9. The method of claim 8 , further comprising: receiving the MPLS packet from the P2MP LSP on one of the multiple receiver devices; retrieving the L2 data units encapsulated within the MPLS packet; and forwarding the L2 data units on at least one egress L2 interface connected to the P2MP LSP. 10. The method of claim 1 , further comprising: transporting L2 data units via the P2MP LSP; and duplicating the L2 data units at an intermediate device associated with the P2MP LSP when two or more branch LSPs of the P2MP LSP originate at the intermediate device. 11. The method of claim 1 , further comprising: transporting L2 data units via the P2MP LSP; and duplicating the L2 data units at one of the receiver devices when two or more egress L2 interfaces of the receiver device are connected to the P2MP LSP. 12. The method of claim 1 , wherein connecting the two or more ingress L2 interfaces to the P2MP LSP comprises mapping L2 data units received on the two or more ingress L2 interfaces to at least one outgoing network link of the source device associated with the P2MP LSP. 13. The method of claim 1 , wherein the computer network comprises a Multi-protocol Label Switching (MPLS) network, wherein the two or more ingress L2 interfaces couple one or more L2 source networks to the source device, wherein at least one egress L2 interface couples one of the multiple receiver devices to at least one L2 customer network, and wherein the source device and the receiver devices are routers. 14. A network device comprising: at least one layer two (L2) interface card having two or more ingress L2 interfaces; and a control unit that establishes a point to multi-point (P2MP) label switched path (LSP) through a computer network to connect, as a source device, the network device to multiple receiver devices and connect the two or more ingress L2 interfaces to the P2MP LSP, where the source device is configured to operate as an ingress to the P2MP LSP and the multiple receiver devices are configured to operate as egresses for the P2MP, and wherein the at least one L2 interface card forwards L2 data units from the two or more ingress L2 interfaces to the multiple receiver devices via the P2MP LSP. 15. The network device of claim 14 , wherein the two or more ingress L2 interfaces comprise two or more of a plurality of ingress attachment circuits (ACs), and wherein the control unit further, for each of the ACs of the source device, signals a corresponding PW label identifying a P2MP Pseudo Wire (PW) to the multiple receiver devices to establish the plurality of P2MP PWs over the same P2MP LSP, and maps the plurality of ingress ACs to the established P2MP Pseudo Wires (PWs) to connect the plurality of ACs to the P2MP LSP. 16. The network device of claim 15 , wherein the L2 interface cards receive the L2 data units from one or more L2 networks on one of the ingress ACs of the source device, and wherein the control unit includes an interconnection module that selects an inner label for each of the L2 data units to correspond to the ingress AC of the source device by which the L2 data units was received to identify the P2MP PW, encapsulates each of the L2 data units in a Multi-Protocol Label Switching (MPLS) packet by appending to the L2 data units an outer label that identifies the P2MP LSP and an inner label selected for the L2 data u
using label swapping, e.g. multi-protocol label switch [MPLS] · CPC title
with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains · CPC title
Multipoint routing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.