Cisco Technology, Inc.

Clinton John Grant

Pratap Pereira

Avinash Ashok Kumar Chiganmi

Jeffrey Y D Lo

Vinit Rajan Kizhakkel

Rajeev Kochhar

Calvin Michael Hareng

Winifred Yah Lee

Suman Sarkar

In one embodiment, a device writes messages and corresponding trace-on-failure flags to log files when failure conditions are detected. The device propagates the trace-on-failure flags to headers of the log files. The device forms a file index of the log files that have trace-on-failure flags set in their headers. The device performs, using the file index, a lookup of messages in the log files associated with a particular error context. The device sends data from the lookup to an electronic display.

Tracelog isolation of failed sessions at scale

In one embodiment, a cursor management process inserts temporal references into a plurality of records written to a table of a shared database, the temporal references indicative of an order in which the records are written. A table write cursor points at a last-written record from among the plurality of records, and read cursors point to a last-read record of a corresponding application. The cursor management process may then provide, table updates to a particular application by determining a chain of one or more updated records of the table from the last-read record of the particular application to the last-written record based on walking a particular read cursor for the particular application through the temporal references of the one or more updated records until the particular read cursor points to the last-written record according to the table write cursor.

Cursor-based state-collapse scheme for shared databases

Presented herein are probabilistic flow management techniques in which flow objects are probabilistically evaluated in view of the current contents of a flow table to determine if the flow object should be added to the flow table. An untrusted packet flow may be received at a feature or function of a networking device. The feature initiates addition of an untrusted flow object corresponding to the untrusted packet flow into a flow table. A probabilistic flow management mechanism determines if the number of untrusted flow objects in the flow table is below a predetermined lower limit. If the number of untrusted flow objects exceeds the lower limit and prior to addition of the untrusted flow object into the flow table, the probabilistic flow management mechanism probabilistically determines if the untrusted flow object may be added to the flow table.

Probabilistic flow management

A method for packet routing includes receiving packets over a plurality of virtual private networks (VPNs). Each of the packets includes a respective virtual routing and forwarding (VRF) identifier indicative of a respective VPN over which the packet was transmitted. Each of the packets is assigned to a respective service class having a respective class identifier. For each packet among at least some of the packets, a respective key is computed based on the respective VRF identifier and the respective class identifier of the packet. The respective key is looked up in a configuration table to determine whether the packet is subject to network address translation (NAT). If the packet is subject to NAT, a new address is assigned to the packet, and the packet is forwarded using the new address.

Growing community of inventors

Artarmon, Australia

Clinton John Grant