Abstract:
Techniques for providing connectivity fault management (CFM) for a multi-tiered network are described herein. In one embodiment, a link trace message (LTM) is received at a provider edge (PE) router and originated from a first Ethernet node and destined to a second Ethernet node, where the PE router interfaces an Ethernet and a multi-protocol label switching (MPLS) network. In response, the PE router initiates an MPLS trace session, including generating an MPLS trace message based on the LTM message to one or more MPLS nodes along a path between the first and second Ethernet nodes within the MPLS network. Subsequently, in response to one or more MPLS trace reply messages from the MPLS nodes of the MPLS network, the PE router generates a first link trace reply (LTR) message and sends the first LTR message to the first Ethernet node over the Ethernet. Other methods and apparatuses are also described.
Abstract:
There is provided a method for use by a router in a communications network. Forwarding information is maintained (S1) which specifies the next hop node for each of a plurality of possible destination nodes. Update information is maintained (S1) which specifies how, if at all, the next hop nodes specified in the forwarding information are to be updated for a plurality of possible network resource failures. Known failure information is maintained (S1) which relates to a known network resource failure or which specifies that there is no known network resource failure. A failure notification is received (S2) relating to a network resource failure. In response to receipt of the failure notification, it is determined (S3) from the failure notification how, if at all, the known failure information is to be updated, and the known failure information is updated, if required, based on the determination (S4). A communications packet is received (S5). Various steps (S6 to S10) are carried out in response to receipt of the communications packet. The destination node for the received packet is determined (S6). It is determined (S7) whether the next hop node specified by the forwarding information for the determined destination node is potentially invalid in view of the known failure information. If so, then the next hop node for the determined destination node is updated if necessary in the forwarding information using the update information and the known failure information (S8). The next hop node is determined for the received packet using the forwarding information and the determined destination node (S9). The received packet is forwarded towards the determined next hop node (S10).
Abstract:
An hierarchical LSP is established to transport packets belonging to a FEC attached to an egress LSR and includes an egress LSR LSP that is common for each of the FECs attached to the egress LSR and forms a path from the ingress LSR through intermediate LSR(s) to the egress LSR. The egress LSR LSP is used when label switching packets destined for the FECs attached to the egress LSR. The hierarchical LSP also includes a unique FEC LSP for each FEC that is used by the egress LSR to identify and forward packets to that FEC. Responsive to a topology change that changes a next-hop of the ingress LSR to reach the egress LSR, the ingress LSR modifies an entry in a forwarding structure to change the next-hop for the egress LSR LSP and does not modify substantially any forwarding structure entities for the FEC LSPs.
Abstract:
MPLS (Multiprotocol Label Switching) fast re-routing using LDP (Label Distribution Protocol) is described. A first network element in a MPLS network receives a first label advertised from a second network element in the MPLS network. The first network element computes a shortest path tree (SPT) to reach a destination network element under a potential failure condition. The second network element is a nexthop of the first network element in the computed SPT and is not upstream from the potential failure condition. The first network element advertises a second label to one or more third network elements for a backup LDP LSP (Label Switched Path) that will serve as a backup when the potential failure condition is realized. The third network element(s) are upstream neighbors on the computed SPT with respect to the first network element. The first network element installs a swap action from the second label to the first label.
Abstract:
An upgraded edge node (e.g., enhanced PBB edge node, enhanced IP/MPLS edge node) and a method are described herein for providing a VLAN service for a customer in a metro network. In addition, a metro network is described herein which includes the upgraded edge nodes, traditional PB edge nodes, and a PB domain that has PB core nodes located therein.
Abstract:
A method implemented by a first provider equipment (PE) device to enable operations, administration and management (OAM) functionality over a pseudo-wire (PW) between the first PE device and a second PE device, wherein the PW traverses a packet switched network and carries control channel messages and a flow of data packets, and where the packet switched network includes nodes that use information outside a pseudo-wire label stack of the data packets for determining multi-path routing, the method including receiving a control channel message at the first PE to be forwarded over the pseudo-wire to the second PE, and prefixing the control channel message with a pseudo-flow header to ensure that the control channel message is forwarded over a same route by the nodes of the packet switched network as the data packets of the flow, thereby enabling OAM functionality to be accurately performed for the pseudo-wire.
Abstract:
There is provided a method for use by a router in a communications network. Forwarding information is maintained (S1) which specifies the next hop node for each of a plurality of possible destination nodes. Update information is maintained (S1) which specifies how, if at all, the next hop nodes specified in the forwarding information are to be updated for a plurality of possible network resource failures. Known failure information is maintained (S1) which relates to a known network resource failure or which specifies that there is no known network resource failure. A failure notification is received (S2) relating to a network resource failure. In response to receipt of the failure notification, it is determined (S3) from the failure notification how, if at all, the known failure information is to be updated, and the known failure information is updated, if required, based on the determination (S4). A communications packet is received (S5). Various steps (S6 to S10) are carried out in response to receipt of the communications packet. The destination node for the received packet is determined (S6). It is determined (S7) whether the next hop node specified by the forwarding information for the determined destination node is potentially invalid in view of the known failure information. If so, then the next hop node for the determined destination node is updated if necessary in the forwarding information using the update information and the known failure information (S8). The next hop node is determined for the received packet using the forwarding information and the determined destination node (S9). The received packet is forwarded towards the determined next hop node (S10).
Abstract:
There is provided a method for use by a first processing unit in or to be installed in a router. The first processing unit is configured or responsible for routing (or forwarding) packets to and from other routers. There may be other such first processing units in or installed in the router. In a first step (S1), information is received at the first processing unit which requires dissemination to other routers. The information also requires processing to determine what, if any, reconfiguration of the routing (forwarding) performed by the first processing unit is required. In a second step (S2b) the information is forwarded in a packet to other routers as required according to the routing (forwarding) configuration for the first processing unit. In a third step (S2c) the information is forwarded to at least one other first processing unit in the router (if there are any other first processing units in the router) not already in receipt of the information. If an expedited dissemination procedure is required, the second and third steps (S2b, S2c) are performed before the processing (to determine what if any reconfiguration is required) has been performed (completed) and/or before the first processing unit has been informed of the result of such processing and/or before any reconfiguration required in the first processing unit has been requested, arranged or performed (completed).
Abstract:
An edge router runs a Multipath Transmission Control Protocol (MPTCP) proxy to allow for a host that implements TCP (Transmission Control Protocol) to operate normally yet reap the benefits of an MPTCP connection. An upgrade of a TCPIP stack on the host is not necessary. The edge router demultiplexes packets received from the host over a TCP connection to an MPTCP connection and multiplexes packets sent to the host over an MPTCP connection to a TCP connection. As a result, higher throughput of packet communication can be realized, for example, for improved video support.
Abstract:
An edge router runs a Multipath Transmission Control Protocol (MPTCP) proxy to allow for a host that implements TCP (Transmission Control Protocol) to operate normally yet reap the benefits of an MPTCP connection. An upgrade of a TCPIP stack on the host is not necessary. The edge router demultiplexes packets received from the host over a TCP connection to an MPTCP connection and multiplexes packets sent to the host over an MPTCP connection to a TCP connection. As a result, higher throughput of packet communication can be realized, for example, for improved video support.