Abstract: Presented are a system and method of detecting a multicast tree link failure and performing a fast switch from the failed multicast tree communication path to a secondary multicast tree communication path. The methods are suitable for leaf nodes in a multiprotocol label switching network. The method generates a count of communication path failure detection packets and a count of communication path failure detection packets plus other packets and compares the counts to determine the status of the link. The system includes two counter components and a comparison component.

Abstract: A method and apparatus perform fast traffic switchover based on server layer status. To do fast traffic switchover when there is server layer failure, each forwarding entry in a forwarding table contains an index to server layer status table, wherein traffic is associated to a service layer based on the physical communication resources used by the primary path. The server layer status table contains status code for all instances of server layers in the system. One status code indicates the server layer status is normal, and primary paths may be used to carry client layer traffic. Another status code indicates abnormal condition on the server layer, and that primary paths cannot be used to carry client layer traffic. When the forwarding entry is used to forward incoming packets, the server layer status code is checked. If the status code indicates normal functionality, the failover object is checked to route the traffic on either the primary or secondary path.

Abstract: Presented are a system and method of detecting a multicast tree link failure and performing a fast switch from the failed multicast tree communication path to a secondary multicast tree communication path. The methods are suitable for leaf nodes in a multiprotocol label switching network. The method generates a count of communication path failure detection packets and a count of communication path failure detection packets plus other packets and compares the counts to determine the status of the link. The system includes two counter components and a comparison component.

Abstract: An improved system and method for transmitting Operations, Administration, and Maintenance, OAM, messages on in a redundancy path are provided. For each OAM function on a service instance of a redundancy path “17 comprising one primary path and one secondary path “17 only one OAM endpoint is created. The OAM endpoint can transmit packets over both the primary and secondary paths. The OAM endpoint contains an index to the primary path and a redundancy index which is used to lookup into a redundancy table. Each entry in the redundancy table indicates whether the primary path or the secondary path is active. OAM packets are transmitted on the active path (i.e., primary or secondary). When a switchover between the redundant paths is required (i.e., when a failure or its correction is detected on the primary path), the corresponding redundancy table entry is changed to implement the switchover. In one embodiment, PW OAM over protected LSP is implemented in an MPLS or MPLS-TP network.

Abstract: The present invention discloses a method of obtaining forwarding information in a network node device (200). The network node device is used to configure local repair for its downstream node or downstream link to be protected in at least one transport path. The method comprises building (210) a discovery message for discovering the forwarding information, wherein the discovery message contains information related to the at least one transport path; transmitting (220) the discovery message over a protection path for protecting the downstream node or downstream link to a peer end device of the protection path; and receiving (230) a discovery response message containing the forwarding information from the peer end device, the discovery response message being built by the peer end device on the basis of the discovery message. The present invention does not depend on existence of control plane, and does not depend on any other communication capability (e.g.

Abstract: A secondary edge node is coupled between the packet network and a non-packet network and is adapted to function as follows when a failure associated with the primary edge node or circuitry coupled thereto occurs. First, the secondary edge node may detect a failure associated with the primary edge node, which is associated with a primary media access control (MAC) address that is used to direct the packet traffic from the first edge node to the primary edge node. Upon detecting the failure, the secondary edge node may send a switch request message including a secondary media access control address that is associated with the secondary edge node to the first edge node. Sending the switch request message indicates that the first edge node should start sending traffic for the first session to the secondary edge node using the secondary media access control address.

Abstract: A request to add or remove a leaf node to a multicast group in a Point-to-Multipoint Label Switched Path is detected, and the leaf node can select a pre-configured tunnel in accordance with the requested multicast group. The leaf node encapsulates the received request and transmits it through the selected pre-configured tunnel. A root node for the multicast group receives the request through the tunnel and can identify the leaf node responsible for transmitting the message by the tunnel header. The root can determine if a Point-to-Multipoint Label Switched Path exists for the request multicast group and can update the membership of the multicast group by adding or removing the leaf node to the multicast group.

Abstract: A request to add or remove a leaf node to a multicast group in a Point-to-Multipoint Label Switched Path is detected, and the leaf node can select a pre-configured tunnel in accordance with the requested multicast group. The leaf node encapsulates the received request and transmits it through the selected pre-configured tunnel. A root node for the multicast group receives the request through the tunnel and can identify the leaf node responsible for transmitting the message by the tunnel header. The root can determine if a Point-to-Multipoint Label Switched Path exists for the request multicast group and can update the membership of the multicast group by adding or removing the leaf node to the multicast group.