Abstract:
A method and apparatus for configuring an element management system server (an EMS server) to support new network element service application versions without upgrading the EMS server software is provided. The EMS stores base version data that describes the data model of a first version of a service application installed on a network element. When a second version of the service application is available, incremental version data describing changes to the data model from the first version to the second version is obtained and stored. In response to receiving a client request involving a service application on a particular network element, the EMS may apply incremental version data, associated with the version of the service application installed on the particular network element, to the base version data to form merged version data that describes the data model of the version of the service application installed on the particular network element.
Abstract:
A system and method for advertising out-of-resources (OOR) conditions for entities, such as nodes, line cards and data links, in a manner that does not involve using a maximum cost to indicate the entity is “out-of-resources.” According to the technique, an OOR condition for an entity is advertised in one or more type-length-value (TLV) objects contained in an advertisement message. The advertisement message is flooded to nodes on a data network to inform them of the entity's OOR condition. Head-end nodes that process the advertisement message may use information contained in the TLV object to determine a path for a new label switched path (LSP) that does not include the entity associated with the OOR condition.
Abstract:
In one embodiment, a connection verification (CV) message is initiated from an initiating maintenance end point (MEP) for an MPLS LSP, the CV message carried in a packet having a time-to-live (TTL) value of 1. Each maintenance intermediate point (MIP) along the MPLS LSP receives the packet and decrements the TTL, and in response to determining that the TTL equals 0, examines a payload of the packet to determine that the packet carries the CV message. The MIP may then append its MIP ID to a route record field of the payload having any previous MIP IDs of upstream MIPs, and forwards the CV message downstream along the MPLS LSP in a packet having a TTL value of 1. The end MEP receives the CV message, and sends a CV reply having the route record field with MIP IDs and an end MEP ID to the initiating MEP.
Abstract:
A technique computes a traffic engineering (TE) label switched path (LSP) that spans multiple domains of a computer network from a head-end node of a local domain to a tail-end node of a remote domain. The novel inter-domain TE-LSP computation technique comprises a computation algorithm executed by the head-end node, which utilizes Path Computation Elements (PCEs) located within the remote domains (i.e., other than the local domain). Specifically, the head-end node requests path segments from a PCE in each of the remote domains, in which the path segments represent paths between all entry border routers to either all exit border routers of the particular remote domain (i.e., through the domain), or to the tail-end node. Upon receiving path segments from each remote domain, the head-end node combines the path segments with local domain information, and performs a forward path computation from the head-end node to the tail-end node to find the best (i.e., “shortest”) path.
Abstract:
An apparatus and method as described for constructing a repair path for use in the event of failure of an inter-routing domain connection between respective components in first and second routing domains of a data communications network. The apparatus is arranged to assign a propagatable repair address for use in the event of failure of the inter-routing domain connection and to propagate the repair address via data communications network components other than the inter-routing domain connection.
Abstract:
An apparatus for providing reachability in a routing domain of a data communications network having as components nodes and links therebetween for a routing domain external destination address is provided. The apparatus is arranged to advertise destination address reachability internally to nodes in the routing domain and associate a reachability category with the internal advertisement of the destination address reachability.
Abstract:
A method and apparatus for configuring an element management system server (an EMS server) to support new network element service application versions without upgrading the EMS server software is provided. The EMS stores base version data that describes the data model of a first version of a service application installed on a network element. When a second version of the service application is available, incremental version data describing changes to the data model from the first version to the second version is obtained and stored. In response to receiving a client request involving a service application on a particular network element, the EMS may apply incremental version data, associated with the version of the service application installed on the particular network element, to the base version data to form merged version data that describes the data model of the version of the service application installed on the particular network element.
Abstract:
A method and apparatus for deploying EMS provisioning services is provided. A communication to administer a particular service on a network element is transmitted from an EMS client to an EMS server. The communication contains service data that describes a particular service to be administered on the network element. The EMS server constructs an instance of a generic record that stores the service data. The EMS server selects a service module to process the instance based on which service is associated with the service data stored in the instance. The instance is processed to produce result data that describes the result of processing the service data at the network element. The EMS server stores the result data in a persistent store. This generic framework enables communications between EMS clients and the EMS server involving different services to be processed similarly. New services are added without modification to the generic framework.
Abstract:
A soft notification technique isolates address family application based errors or events occurring within a routing protocol, such as the Border Gateway Protocol (BGP), used to exchange routing information between a router and its peer router over a BGP session operating on a reliable transport. The technique apportions the session into a plurality of logical subsets, each of which is associated with an address family application (AFI/SAFI) module of a BGP protocol executing on the routers. BGP soft notification messaging is employed to allow the router to notify its peer of an isolated error condition or event associated with an AFI/SAFI module. Isolation of the error/event enables restart (“soft reset”) of only the associated AFI/SAFI module, thereby obviating the need to reset or terminate the entire BGP session and reliable transport between the router and peer. Notably, soft reset of the module occurs without disrupting services provided by other AFI/SAFI modules of the BGP protocol.
Abstract:
A protocol for detecting faults in a bidirectional path between two forwarding engines, where parts of the bidirectional path checked may include interfaces, one or more data links, and to the extent possible the forwarding engines themselves, with potentially very low latency. The protocol may operate independently of media, data protocols, and routing protocols.