Abstract:
In one embodiment, an access component of a local network edge device receives traffic, and generates a frame for the traffic that includes a remote context label that identifies an access component of the remote network edge device to which the traffic is to be forwarded upon arrival at the remote network edge device, and a virtual circuit label corresponding to a particular virtual service of the traffic. The local network edge device forwards the frame towards the remote network edge device. In another embodiment, the frame may be received at a core component of the remote network edge device, an in response to the remote context label identifying an access component of the remote network edge device, forwarded to the access component, which determines the particular virtual service, and forwards the traffic from the frame out the access component towards an endpoint for the traffic.
Abstract:
In one embodiment, associated differential processing of decapsulated packets is performed using Service Function Instances (SFIs) identified by Service Function Values (SFVs) derived from their encapsulating transport packets. By using different SFVs associated with different processing policies within a same processing context, one embodiment performs differential processing of streams of packets (arriving in transport packets) as identified by the particular SFV obtained from each particular transport packet. In other words, the processing policy identifies processing performed on the corresponding decapsulated original packet, not processing of the transport packet. Thus, if the original packet is an Internet Protocol (IP) packet, the SFI identifies Layer 3 processing that is performed on the original IP packet. Additionally, one embodiment uses a route advertising protocol (e.g., Border Gateway Protocol) to distribute associations between different SFVs and different addresses in a processing context (e.g., VRF).
Abstract:
In some embodiments, a first provider edge (PE) router is coupled to a first customer edge (CE) router; a second CE router; and a second PE router. The second PE router is coupled to the first CE router and the second CE router. The first PE router is configured with a primary label comprising a primary next hop of the first CE router and a backup next hop of the second PE router and a secondary label comprising a primary next hop of the first CE router and a backup next hop of the second CE router. The second PE router is configured with a primary label comprising a primary next hop of the first CE router and a backup next hop of the first PE router and a secondary label comprising a primary next hop of the first CE router and a backup next hop of the second CE router.
Abstract:
In some embodiments, a first provider edge (PE) router is coupled to a first customer edge (CE) router; a second CE router; and a second PE router. The second PE router is coupled to the first CE router and the second CE router. The first PE router is configured with a primary label comprising a primary next hop of the first CE router and a backup next hop of the second PE router and a secondary label comprising a primary next hop of the first CE router and a backup next hop of the second CE router. The second PE router is configured with a primary label comprising a primary next hop of the first CE router and a backup next hop of the first PE router and a secondary label comprising a primary next hop of the first CE router and a backup next hop of the second CE router.
Abstract:
In one embodiment, an access component of a local network edge device receives traffic, and generates a frame for the traffic that includes a remote context label that identifies an access component of the remote network edge device to which the traffic is to be forwarded upon arrival at the remote network edge device, and a virtual circuit label corresponding to a particular virtual service of the traffic. The local network edge device forwards the frame towards the remote network edge device. In another embodiment, the frame may be received at a core component of the remote network edge device, an in response to the remote context label identifying an access component of the remote network edge device, forwarded to the access component, which determines the particular virtual service, and forwards the traffic from the frame out the access component towards an endpoint for the traffic.
Abstract:
A mechanism that allows CE-to-PE traffic to achieve minimal traffic loss at the same rate as PE-to-CE redirection (FRR). The solution relies on a fast-unblocking of the Backup-DF interface based on appearance of redirected packets from the active DF-Elected peer. A slow-path confirmation mechanism is included to further mitigate false-positives, as well as maintaining data plane and control plane in sync.
Abstract:
First and second egress nodes are each multi-homed to a customer edge (CE) that participates in virtual routing and forwarding (VRF). First forwarding information is configured on the first egress node. The first information includes VRF labels and defines forwarding of traffic based on the VRF labels and a status of a primary path to the CE. The VRF labels include a per-VRF label for the VRF and a per-CE label for the CE. Second forwarding information is configured on the second egress node. The second forwarding information includes the per-VRF label and the per-CE label, and defines traffic forwarding based on the VRF labels. Upon receiving traffic for the CE that carries the per-VRF label, the first egress node determines the status of the primary path, and forwards the traffic to either the CE over the primary path or to the second egress node, depending on the status.
Abstract:
First and second egress nodes are each multi-homed to a customer edge (CE) that participates in virtual routing and forwarding (VRF). First forwarding information is configured on the first egress node. The first information includes VRF labels and defines forwarding of traffic based on the VRF labels and a status of a primary path to the CE. The VRF labels include a per-VRF label for the VRF and a per-CE label for the CE. Second forwarding information is configured on the second egress node. The second forwarding information includes the per-VRF label and the per-CE label, and defines traffic forwarding based on the VRF labels. Upon receiving traffic for the CE that carries the per-VRF label, the first egress node determines the status of the primary path, and forwards the traffic to either the CE over the primary path or to the second egress node, depending on the status.