Abstract: A method and system for multicast flow restoration following network failure detection. Specifically, in addressing the aftermath following a network failure, one or more embodiments disclosed herein propose a solution through which failure-impacted network multicast(s) may be identified and, subsequently, restored with or without third-party intervention. To that end, one or more embodiments disclosed herein employ(s) a centralized network controller configured to obtain aggregated network state, including network topology information, through numerous logical agents interspersed across a network. Thereafter, the aggregated network state may be leveraged to ascertain and remedy any network multicast disruptions.

Abstract: A logical table is configured with a first set of memory banks, where each logical row in the logical table comprises a corresponding memory row from each of the memory banks. Lookup instructions to access a logical row includes a bank set that lists the memory banks associated with that logical row. In response to a range of memory rows of one of the memory banks being reallocated to another logical table, a new memory bank is identified to store the data in the reallocated memory rows. Logical rows associated with the reallocated memory rows are mapped to the new memory bank. Bank sets in the lookup instructions that refer to the remapped logical rows are updated to list the new memory bank in place of the “old” memory bank.

Abstract: In general, embodiments described herein relate to methods and systems for automating the configuration of network devices. More specifically, embodiments of the invention relate to using configuration commands that specify protocol-specified relationships in order to generate granular (or specific) filtering rules (also referred to as rules). The rules are subsequently programmed into the network device.

Abstract: A method and network device for network traffic flooding. Specifically, the method and network device disclosed herein implement the mitigation of the lack of data-link layer (or L2) addressing resolutions, usually learned by or programmed manually into the network device, through the flooding of affected network traffic across identified network broadcast domains. Flooding of the network traffic in the aforementioned manner may ensure that at least the destination(s) of the network traffic receives the network traffic at least in scenarios where which it is unknown out of which particular physical network interface(s) should the network traffic be transmitted to reach the destination(s).

Abstract: A method for processing packets in a network device, comprising: determining that a packet received by the network device is to be processed using a next hop group, selecting a member of the next hop group, and transmitting the packet to a second network device associated with a second member of the next hop group.

Abstract: In some embodiments, a method sets a threshold for utilization of a first table, wherein the utilization is based on layer 3 addresses and layer 2 addresses being stored in the first table. When a utilization of the first table does not meet the threshold, the method stores a layer 3 address in the first table. The first table uses a first type of lookup to determine a next hop address for the layer 3 addresses or the layer 2 addresses, and the first table also stores one or more layer 2 addresses. When the utilization of the first table meets the threshold, the method stores the layer 3 address in a second table where the second table uses a second type of lookup to determine the next hop address for layer 3 addresses.

Abstract: A processing unit disposed within a compute unit, where the compute unit includes a printed circuit board (PCB) that includes an integrated circuit; a first thermal management device, that includes a first vapor chamber thermally conductively coupled to a first side of the integrated circuit; and a first heatsink thermally conductively coupled to the first vapor chamber; and a second thermal management device, that includes a second vapor chamber; and a second heatsink thermally conductively coupled to the second vapor chamber, where the second thermal management device is thermally conductively coupled to the first thermal management device; where the PCB is interposed between the first thermal management device and the second thermal management device.

Abstract: A network device includes storage. The network device also includes a forwarding information manager. The storage stores forwarding information. The storage also stores information source rankings. The forwarding information manager obtains information from a source. The information source rankings include a ranking associated with the source. The forwarding information manager makes a determination, based on the information source rankings, that the source is undesirable. The forwarding information manager discards the information without processing the information based on the determination.

Abstract: Methods, systems, and computer-readable mediums for managing forwarding equivalence class (FEC) hierarchies, including obtaining a forwarding equivalence class (FEC) hierarchy; making a first determination that a first hardware component supports a maximum levels of indirection (MLI) quantity; making a second determination that the FEC hierarchy has a hierarchy height; based on the first determination and the second determination, performing a comparison between the MLI quantity and the hierarchy height to obtain a comparison result; and based on the comparison result, performing a FEC hierarchy action set.

Abstract: Techniques disclosed herein provide a method for efficiently propagating address resolution reply messages. A first router in a first network receives an address resolution request message from a second router in a second network. The first router generates an entry for the address resolution request message and stores the entry in a pending address resolution requests table. When the first router receives a route advertisement, it extracts a network layer address from the route advertisement and determines whether the pending address resolution requests table includes an entry for the network layer address. If so, the router extracts a link layer address from the route advertisement and generates an address resolution reply message comprising the network layer address and the link layer address. The router then transmits the address resolution reply message to the second router.

Abstract: A pluggable optical module includes: a casing with an internal space; a latching pocket disposed on a side wall of the casing; and a latch plane on a surface of the latching pocket. The surface is a beveled surface, and the beveled surface delimiting the latch plane has an angle of between 3 to 15 degrees.

Abstract: A method and apparatus of a network element that processes control plane data in a network element is described. In an exemplary embodiment, the network element receives control plane data and determines a class of the control plane data. In addition, the network element marks the control plane data based on at least on an existence of an indication of whether the network element had previously processed other data in the same class as the class of the control plane data. Furthermore, the network element queues the control plane data.

Abstract: This disclosure presents several embodiments of a device configured to perform inband telemetry tracking. The device is configured to store a flow table that tracks metrics of a detected packet flow that passes through the device. More specifically, the flow table tracks several telemetry metrics, each telemetry metric being specific to a tracking time period, and tracking statics based only on packets of the packet flow that were received during that specific time period. At an end of an export time period (which is longer than a tracking time period), the device transmits all stored telemetry metrics from the flow table to a collector.

Abstract: Embodiments described herein relate to techniques for distributing shaped subinterfaces among physical interfaces of a port channel. Such techniques include receiving a request to configure a shape rate for a port channel subinterface; generating a physical interface set specifying: a first physical interface and a first allocated bandwidth associated with the first physical interface; and a second physical interface and a second allocated bandwidth associated with the second physical interface; making a selection, using the physical interface set, of the first physical interface based on the first allocated bandwidth being lesser than the second allocated bandwidth; assigning the first physical interface as a first anchor interface for the first port channel subinterface; and adding the first shape rate to the first allocated bandwidth to obtain a first new allocated bandwidth for the first physical interface.

Abstract: A method and system for network endpoint identification through network fingerprint based entity resolution. Particularly, embodiments disclosed herein may entail receiving a network fingerprint descriptive of at least a network endpoint; obtaining at least two network endpoint label sets each inferred from the network fingerprint by a different network fingerprint parser; reducing, through entity resolution and heuristics, the at least two network endpoint label sets into a de-duplicated network endpoint label set; and resolving, through a voting algorithm, the de-duplicated network endpoint label set to obtain a unified network endpoint label that best identifies the network endpoint.

Abstract: Systems and methods are provided herein for implementing multi-table OpenFlow flows that have combinations of packet edits. This may be accomplished by a network device receiving a first flow entry with a first set of actions to be installed into a flow table. The network device may determine that the first set of actions includes edits to a plurality of fields of a matched data packet. In response, the network device may change the first set of actions of the first flow entry to edit a first field of the data packet and create a second flow entry with a second set of actions to edit a second field of the data packet. The network device may install the first and second flow entries into one or more flow tables of the network device.

Abstract: A networking system may include one or more network nodes such as one or more network switches. The network switches include respective matching engines. The matching engines across the network switches may be configured to match on a consistent set of matching criteria based on low and high entropy data fields to sample a same subset of packets for each network flow of interest. The sampled packets may include annotations and may be sent to collector circuitry for analysis. Controller circuitry may enforce consistent sampling policies across the network switches.

Abstract: Embodiments described herein relate to techniques for dynamically adjusting information propagation metrics for information propagation paths of network devices based on signal quality.

Abstract: A method for managing a network device that includes a network operating system (NOS) and a third-party network operating system (3PNOS) includes detecting a 3PNOS state change in a 3PNOS database managed by the 3PNOS, translating the 3PNOS state change into a network device state change, storing the network device state change in a state database managed by the NOS, in response to the storing: detecting a change in the state database by a NOS agent executing in the NOS, initiating, in response to detecting the change in the state database, an update to hardware on the network device by the NOS, wherein the 3PNOS does not directly manage the hardware.

Abstract: Embodiments described herein relate to techniques for route control. The techniques may include obtaining, by a routing information base (RIB) agent, a route policy for performing a route action; receiving, by the RIB agent, a route from a routing protocol; analyzing, by the RIB agent, the route using to make a determination about whether to perform the route action; and performing, by the RIB agent, the route action based on the determination. Route actions may include actions relating to route modification, route redistribution, modifications of various attributes of a route, etc.