Abstract:
Embodiments of the present invention provide a network label allocation method, a device, and a system, which enable a local PE to distinguish packets from different remote PEs. The method includes: generating, by a local provider edge PE, a VPN label route for each remote PE, where VPN labels in VPN label routes of different remote PEs are different, and the remote PE and the local PE at least belong to a same VPN; and sending the VPN label route to the remote PE, so that the remote PE separately matches an IP address of the remote PE with a target device IP address in the VPN label route, and matches an import route target RT of each VRF of the remote PE with a route target RT in the VPN label route, a packet related to a successfully matched VRF.
Abstract:
Method for direct access to information stored in the nodes of a packet switching network comprises the steps of: collecting the pointers, corresponding to which the information required for processing the packets belonging to one and the same flow is stored in each node of the network;—constructing a distributed linked data structure (DLDS) in which the pointers are contained inside packets (PI, P2, P3) that traverse the DLDS-aware routers constituting the path between sender (A) and receiver (B) of the flow;—use of the DLDS data structure for direct access to the information stored in a DLDS-aware router, using a pointer of the DLDS contained in the packet in transit;—selection of the pointer of the DLDS contained in the packet in transit based on its position inside said packet, said position being equal to the serial number of the DLDS-aware router in the flow path, and checking of validity by consistency tests.
Abstract:
A network node for forwarding a data packet to a virtual network. The network node may maintain a table comprising one-to-one mapping information between one or more virtual private network (VPN) labels and one or more identifying labels for a destination virtual network. The network node may receive a data packet from a Multiprotocol Label Switching (MPLS) network. The data packet may comprise one or more VPN labels, at least one of which may be a MPLS Big Label Value that supports one-to-one mapping for more than one million destination virtual network addresses. The MPLS Big Label Value may comprise a destination virtual network address. The network element may map the one or more VPN labels to corresponding identifying labels for the destination virtual network according to the table, and forward the data packet to the destination virtual network.
Abstract:
A method performed by a provider edge device includes generating pseudo-wire tables based on virtual private local area network service advertisements from other provider edge devices, where the provider edge device services customer edge devices, and establishing pseudo-wires with respect to the other provider edge devices, based on the pseudo-wire tables, where the pseudo-wires include an active pseudo-wire and at least one standby pseudo-wire with respect to each of the other provider edge devices. The method also includes generating and advertising VPLS advertisement to the other provider edge devices, detecting a communication link failure associated with one of the customer edge devices in which the provider edge device services, and determining whether the at least one standby pseudo-wire needs to be utilized because of the communication link failure.
Abstract:
Systems, methods, architectures and/or apparatus for reflecting information between provider equipment (PE) nodes associated with a Virtual Private LAN Service (VPLS) via a network element adapted to operate as a Forwarding Equivalence Class (FEC) Reflector (FR) node
Abstract:
Domain-wide unique node identifiers and domain-wide unique service identifiers are distributed within a MPLS domain using routing system LSAs. Nodes on the MPLS network compute shortest path trees for each destination and install unicast forwarding state based on the calculated trees. Nodes also install multicast connectivity between nodes advertising common interest in a common service identifier. Rather than distributing labels to be used in connection with unicast and multicast connectivity, the nodes deterministically calculate the labels. Any number of label contexts may be calculated. The labels may either be domain wide unique per unicast path or per multicast, or may be locally unique and deterministically calculated to provide forwarding context for the associated path. Multicast and unicast paths may be congruent, although this is not a requirement.
Abstract:
A source edge router initiates point-to-point (P2P) label switched paths (LSPs) to multiple receiver edge routers, sends one or more PATH messages to one or more nodes downstream of the source edge router for the P2P LSPs, wherein each one of the set of PATH messages includes a same identifier of a point-to-multipoint (P2MP) LSP that includes a session object that contains a tunnel identifier and a P2MP identifier, and receives from each of those nodes downstream of the source edge router, a set of one or more RESV messages, wherein each one of the received RESV messages received from a respective node downstream of the source edge router includes the identifier of the P2MP LSP and a label allocated by that node downstream of the source edge router.
Abstract:
A system includes an ingress node, an egress node, and one or more intermediate nodes. A path is formed from the ingress node to the egress node via the one or more intermediate nodes, where the path carries label distribution protocol (LDP) packets of an LDP traffic flow. One of the intermediate nodes detects traffic congestion, modifies one of the LDP packets to include an indicator of the traffic congestion, and sends the modified LDP packet towards the egress node. The egress node receives the modified LDP packet and notifies the ingress node of the traffic congestion in response to identifying the indicator of the traffic congestion within the modified LDP packet.
Abstract:
Example methods, apparatus and articles of manufacture to respond to signaling protocol failures in traffic engineering (TE) tunnels are disclosed. A disclosed example apparatus includes a database to store a tunnel state for a first TE tunnel, a signaling engine to detect whether a signaling protocol failure associated with the first TE tunnel occurred, and to set the tunnel state to a first logic state when the signaling protocol failure is detected, and a label switching engine to route the data through a multiprotocol label switching (MPLS) based network via a second TE tunnel when the tunnel state is the first logic state, and to route the data through the MPLS-based network via the first TE tunnel when the tunnel state is a second logic state.
Abstract:
A method and apparatus for implementing Label Information Base (LIB) overload protection for a respective Forwarding Equivalency Class (FEC) type associated with a Label Switched Path (LSP).