Juniper Networks, Inc.

Cisco Technology, Inc.

Manoj Leelanivas

Nischal Sheth

Ping Pan

Yakov Rekhter

Steven Lin

Kireeti Kompella

Der-Hwa Gan

Keith Eric Holleman

Wing Eng

Paul S Traina

Andrew H Heffernan

Arun Vaidyanathan

Dennis C Ferguson

Ken Kuwabara

Ravi Vaidyanathan

Scott Mackie

Kaushik Ghosh

Kenneth A Moberg

Hsien-Chung Woo

Claude Alan Cartee

Techniques are described for implementing one or more logical routers within a single physical routing device. These logical routers, as referred to herein, are logically isolated in the sense that they achieve operational and organizational isolation within the routing device without requiring the use of additional or redundant hardware, e.g., additional hardware-based routing controllers. The routing device may, for example, include a computing platform, and a plurality of software process executing within the computing platform, wherein the software processes operate as logical routers. The routing device may include a forwarding component shared by the logical routers to forward network packets received from a network in accordance with the forwarding tables.

Routing device having multiple logical routers

When a node has to restart its control component, or a (e.g., label-switched path signaling) part of its control component, if that node can preserve its forwarding information across the restart, the effects of such restarts on label switched path(s) include the restarting node are minimized. A node's ability to preserve forwarding information across a control component (part) restart is advertised. In the event of a restart, stale forwarding information can be used for a limited time before. The restarting node can use its forwarding information, as well as received label-path advertisements, to determine which of its labels should be associated with the path, for advertisement to its peers.

Graceful restart for use in nodes employing label switched path signaling protocols

A connection between network nodes in a communication network is backed up. A failover switched path such as a label-switched path (LSP) is created starting at a first network node of a connection and ending at the second node of the connection, while bypassing the protected connection. In the event of connection failure, data is transmitted through the failover switched path (e.g., LSP). A network operator can selectively protect different types of data by using filters that bind one or more types of traffic received over one or more interfaces to different failover switched paths (LSPs).

Protecting connection traffic using filters

A routing device may be connected to multiple spoke site networks, and may receive local routes from these spoke site networks. The routing device may include routing information and forwarding information. The routing device may update the routing information to include the local routes, and selectively generate the forwarding information to exclude the local routes. The routing device may associate labels with the local routes and advertise the labels and local routes to other routing devices. The labels may be associated with interfaces of the routing device or access links that connect the routing device to a spoke site network, and the associations of labels with interfaces or access links may be stored in the forwarding information. The routing device may forward received packets that include the labels according to the labels, and may forward other received packets according to the routes within the forwarding information.

Managing routing information in a hub-and-spokes network

A connection between network nodes in a communication network is backed up. A failover label-switched path (LSP) is created starting at a first network node of a connection and endingat the second node of the connection, while bypassing the protected connection. In the event of connection failure, data is transmitted through the failover LSP. A network operator can selectively protect different types of data by using filters that bind one or more types of traffic received over one or more interfaces to different failover LSPs.

When a node has to restart its control component, or a (e.g., label-switched path signaling) part of its control component, if that node can preserve its forwarding information across the restart, the effects of such restarts on label switched path(s) the include the restarting node are minimized. A node's ability to preserve forwarding information across a control component (part) restart is advertised. In the event of a restart, stale forwarding information can be used for an limited time before. The restarting node can use its forwarding information, as well as received label-path advertisements, to determine which of its labels should be associated with the path, for advertisement to its peers.

A router receives destination address information for a packet and determines, among entries in a first forwarding table, a closest match for the received destination address information. The router receives a pointer to a second forwarding table in accordance with the closest match determined in the first forwarding table and determines, among entries in the second forwarding table, a closest match for the received destination address information.

Nexthop to a forwarding table

A connection between network nodes in a communication network is backed up. A failover label-switched path (LSP) is created starting at a first network node of a connection and ending at the second node of the connection, while bypassing the protected connection. In the event of connection failure, data is transmitted through the failover LSP. A network operator can selectively protect different types of data by using filters that bind one or more types of traffic received over one or more interfaces to different failover LSPs.

Samples from an addressed data forwarding devices, such as a router, are associated with path-centric information. Information from the samples is used to update corresponding path-centric traffic information, such as flow information for example. The aggregated path-centric traffic information can then be used by traffic analysis operations.

Generating path-centric traffic information for analysis using an association of packet-centric information to path-centric information

A routing system decouples the routing functionality from the packet forwarding functionality. The decoupling of functionality is accomplished by coupling a set of routing engines to a set of packet-forwarding engines via a switch. The decoupling of functionality allows the routing system to easily be reconfigured and scaled. The decoupling of functionality also reduces the susceptibility of concurrently executing software processes from the malfunction of a single software process.

Growing community of inventors

Los Gatos, CA, United States of America

Manoj Leelanivas