Alcatel Lucent

Vinod Prabhu

Andrew Dolganow

Florin S Balus

Shafiq Pirbhai

Paul Kwok

Benjamin David Washam

Daniel Lafleur

James Wisener

William McConnochie

Various exemplary embodiments relate to an operational group in a network element of a communication network, where the operational group is associated with monitored objects and monitoring client objects such that the status of the operational group is a function of the operational status of the monitored objects or services. Monitoring client objects can monitor the status of the operational group such that the status of each of the monitoring client objects reflects the status of the operational group.

Method and apparatus for object grouping and state modeling for application instances

A method of non-service affecting APS protection for MLPPP bundles on routing systems, and associated mechanism, including one or more of the following: specifying a working MLPPP bundle and a protection MLPPP bundle; specifying MLPPP parameters; associating the working MLPPP bundle and the protection MLPPP bundle with an APS circuit; bringing up an MLPPP session; changing an operational status of the working MLPPP bundle; synchronizing MLPPP state information between the working MLPPP bundle and the protection MLPPP bundle; and driving an operational status of the protection MLPPP bundle based on said changing the operational status of the working MLPPP bundle.

Mechanism and method for non-service affecting APS protection for MLPPP bundles on routing systems

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

Growing community of inventors

Kanata, Canada

Vinod Prabhu