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:
To reveal link bundles' component links in an MPLS network, transmit a sequence of request and reply packets. For a router receiving a request packet, the packet identifies that link bundles should be revealed, detect the link bundle links connected to the router, and for each, its component links are added to a downstream mapping field (DMF). A link bundle mapping field (LBMF) is also added to the request packet. Each LBMF specifies the component links of that link bundle by pointing to the component links added to the DMF. For a router responding to a request packet with a reply packet, determine if any links in the DMF are component links, and for each, identify a LBMF containing information regarding that link. Each component link in the DMF is processed. The component links in each LBMF are iterated through to ensure each matches the determined links in the DMF.
Abstract:
A method and system for protecting valuable resources within an autonomous system network. Address prefixes within the system are designated as valuable and a flag bit is associated with the address within routing tables of routers of the network. Interfaces to border routers are identified and when packets are received at those interfaces, the packets are flagged with a flag or tag bit. The destination address of the received packet is compared to the flag bit associated with the valuable resource prefix, and if the packet is directed to that resource the packet is dropped and/or logged, but the packet is not forwarded to that resource. In specific cases an interface from an external source may be configured to not create the flag or tag bit, wherein that packet will be delivered to the destination prefix of the packet.
Abstract:
A path verification protocol (PVP) which enumerates a series of messages sent to a set of nodes, or routers, along a suspected path identifies forwarding plane problems for effecting changes at the control plane level. The messages include a command requesting interrogation of a further remote node for obtaining information about the path between the node receiving the PVP message and the further remote node. The node receiving the PVP message replies with a command response indicative of the outcome of attempts to reach the further remote node. The series of messages collectively covers a set of important routing points along a path from the originator to the recipient. The aggregate command responses to the series of PVP messages is analyzed to identify not only whether the entire path is operational, but also the location and nature of the problem.
Abstract:
A system and method routes data traffic over a unidirectional link of a computer network configured to implement a routing protocol, such as the ISIS routing protocol. To that end, the invention extends the ISIS routing protocol to allow dynamic discovery of neighboring routers (i.e., neighbors) that are connected via the unidirectional link and subsequent establishment of an adjacency between the neighbors over the link. Adjacency establishment is illustratively effected through the use of novel type/length/value (TLV) encoded formats appended to ISIS Hello packets to convey information between the neighbors.
Abstract:
In one embodiment, a local network device may determine an inability to establish a connectivity verification protocol (e.g., Bidirectional Forwarding Detection, “BFD”) session to a remote network device, such as from unreturned control messages. In response, the local network device may send at least one connectivity verification protocol echo message to the remote network device destined to be returned to the local network device and forwarded using a forwarding protocol. In response to receiving or not receiving the echo message, the local network device may thus determine whether the forwarding protocol is functioning between the local and remote network devices. In this manner, the local network device may determine whether an inability to establish a connectivity verification protocol session is due to an inability to forward packets between the devices, or due to the connectivity verification protocol not working (or not being configured) on the remote network device.
Abstract:
In one embodiment, a node identifies a plurality of equal cost best paths to a destination, the best paths having one or more associated links. The node receives dynamic link utilization information for the associated links, and determines an amount of traffic to the destination to forward over each of the equal cost best paths, the amount being dynamically dependent upon the dynamic link utilization of the associated links for each equal cost best path.
Abstract:
A graceful shutdown technique modifies a routing protocol to allow an intermediate node, such as a router, to announce to its peer routers (peers) its intention to be gracefully shutdown and removed from service in a network. By announcing its intention to be removed from service, the shutdown router closes (terminates) all connections with its peers and all original routes advertised on those connections are removed (withdrawn) from service. According to the inventive technique, the shutdown router may continue forwarding packets over the network for a “grace” period of time, i.e., the router maintains the validity of those original routes so that packets mapped to the routes are not dropped (at least during the grace period). The grace period also allows backup paths to be propagated to each peer and put into service prior to a final withdrawal of the shutdown router's paths from a forwarding information base of the peer. Thus, the grace period enables the network to continue using the shutdown router as a next hop as it re-converges to use the alternate, backup paths.
Abstract:
A technique protects against failure of a network element using Multi-Topology Repair Routing (MTRR) in a computer network. According to the novel technique, a protecting node (e.g., a router) maintains Multi-Topology Routing (MTR) databases for a first topology and at least a second topology. The protecting node determines whether any acceptable repair paths are available in the first topology for a protected network element (e.g., node, link, etc.) of the first topology. If not, the protecting node may establish a repair path (e.g., for Fast ReRoute, FRR) in the second topology for the protected network element.
Abstract:
In one embodiment, a router generates a notification message that indicates the router is to be gracefully removed from service. The router sends the notification message to peers of the router in a network. The router then continues to forward packets for a grace period after sending the notification message, to permit backup paths to be propagated to peers, and to be put into service, prior to withdrawal from service of paths through the router. Thereafter, the router is removed from service at the expiration of the grace period.