Alcatel Lucent

Benjamin David Washam

Andrew Dolganow

Satyam Sinha

Stephen Tan

Praveen Vasant Muley

Shafiq Pirbhai

Tiberiu Grigoriu

Vinod Prabhu

Xiaomei Han

Bassem M Abdouni

Boovaraghavan Ranganathan

Various exemplary embodiments relate to a method and related system and machine-readable medium including one or more of the following: receiving, at the MEP, a connectivity fault management (CFM) message; determining whether the CFM message includes an indication specifying a new value for a timeout factor; and when the CFM message includes an indication specifying a new value for the timeout factor, using the new value as the timeout factor. One or more of the following may also be included: when the CFM message does not include an indication specifying a new timeout factor, using a default value as the timeout factor; determining a timeout period using at least the timeout factor; determining whether the timeout period has elapsed since a most recent CFM message was received; and when the timeout period has elapsed since the last CFM message was received, determining that a timeout has occurred.

Connectivity fault management timeout period control

Various exemplary embodiments relate to a method and related network node including one or more of the following: configuring a maintenance domain on a first network node; configuring a maintenance association within the maintenance domain on a first network node; configuring, within the maintenance association, a local maintenance endpoint (MEP) on the first network node; and establishing a plurality of point-to-point connections within the maintenance association, each point-to-point connection established between the local MEP and a respective remote MEP on a respective network node of the plurality of network nodes using an identifier of the respective remote MEP and a Media Access Control (MAC) address of the respective remote MEP, wherein each point-to-point connection enables transmission of unicast CFM messages from the local MEP to the respective remote MEP, and the plurality of point-to-point connections are established within a single maintenance association.

Scaled Ethernet OAM for mesh and hub-and-spoke networks

A method of managing virtual routing forwarding (VRF) tables at a provider edge PE router of a L3 virtual private network (VPN) is provided. An import route target (ImpRT) tree is maintained at the PE router, which keeps the association between all ImpRT attributes currently configured on said PE router and the virtual routing table VRF at that router. When an ImpRT attribute is configured on a VRF table, the PE router first searches the tree to identify a local VRF table that contains a route(s) with that ImpRT attribute. If this information is available locally, the VRF is updated by copying the route information, and there is no need to do a route refresh. When an ImpRT is deleted from a VRF, a route refresh is avoided by parsing all the routes in the VRF and removing the routes that no longer have a matching route target. In an alternative implementation, the local source is the master RIB (routing information base) which includes all routes in all VRFs at the router, and optionally even rejected routes that were filtered out using ImpRTs. In this variant, even routes associated with ImpRTs that are new to the router would be available to update the VRF without requiring a route refresh.

Managing L3 VPN virtual routing tables

Providing a network service is disclosed. A data associated with the service is received. It is determined whether a local context associated with the service is in an active state with respect to the service. The data is redirected to another chassis, via an inter-chassis backup connection, if it is determined that the local context is not in an active state with respect to the service.

Redundant far-end pseudo-wire connectivity

Growing community of inventors

Ottawa, Canada

Benjamin David Washam