Cisco Technology, Inc.

Juniper Networks, Inc.

Amazon Technologies, Inc.

Sandeep Bajaj

Nitin Kumar

James Michael Murphy

Abhijit Kumar Choudhury

Raghavendra Mallya

Bharani Chadalavada

Pranay Pogde

Scott Mackie

James Washburn

Rahul Kasralikar

Apoorva Jindal

Anna Charny

Rajagopalan Sivaramakrishnan

Jainendra Kumar

Ramya Olichandran

Earl T Cohen

Rahul Jain

Francois Le Faucheur

Stefan Christian Richter

Vinay Prabhu

Christopher J Kappler

Shridhar Kulkarni

Murtuza S Attarwala

Sarah Adelaide Evans

Orlando Maldonado

David Hahm

Pranay Podge

Rahul S Kasralikar

Christopher Kappler

Routing metadata, to be used at a transit gateway to transmit packets among a plurality of networks, is obtained from several routing information sources at a route processing node of a connectivity service. The node applies a rule to a subset of the metadata to generate at least a portion of a routing information base, with the first rule indicating a matching criterion for selecting the subset, as well as a mutation to be implemented with respect to the subset. A packet forwarding node of the connectivity service obtains at least a portion of a forwarding information base (FIB) generated by the node from the RIB, and transmits a data packet received at the transit gateway to a next hop destination indicated in the FIB.

Modification of routing and forwarding information for cloud network traffic using customer-specified rules

A method may include monitoring a network performance metric for multiple paths to a destination through a network, and storing historical performance data for the paths. The method may also include receiving a data flow directed to the destination, where the data flow may be subject to a network performance agreement. The method may additionally include determining aggregate historical performances for the paths, and comparing the aggregate historical performances for the paths. The method may also include, based on the comparison of the aggregate historical performances, routing the data flow through the network.

Network path selection

A method may include receiving a data flow of an application directed to the destination in a software-defined network (SDN). The method may also include identifying a classification of the application. The method may additionally include identifying a set of performance thresholds associated with the classification of the application. The method may also include determining a current performance of the data flow of the application in the SDN. The method may also include generating a performance score for the application based on the set of performance thresholds and the current performance of the data flow of the application in the SDN. The method may further include causing the performance score for the application to be presented via an interface.

Path selection for an application based on a performance score in a software-defined network

A backbone service exposes network parameters, such as a minimum available bandwidth, latency, or packet loss, in a tunnel path between any source-destination pairs. The network parameters can be mapped as a function of time so that service teams can schedule when to use the backbone with minimized interruption to other users. The data generated by the backbone service can be transmitted, stored or displayed for informational purposes to provide insights to service teams on how to better leverage the network and create awareness of the current status of the backbone. The backbone service can be extended to provide bandwidth brokerage for controlling traffic distribution in the network. The backbone service can further provide triggered messages that inform service teams about failures in the network that could reduce the available bandwidth. The messages can further target users of affected source-destination pairs.

Backbone network performance analysis

A method may include generating a set of instructions for a set of devices in software-defined network (SDN) to monitor a set of characteristics. The method may also include sending the set of instructions to the set of devices in the SDN via a control plane that is isolated from a packet forwarding path. The method may further include receiving monitor data via the control plane from at least one device of the set of devices in the SDN. The method may also include determining a change to a set of parameters of the SDN. The method may include generating a policy based on the change to the set of parameters of the SDN. The method may include sending the policy to the set of devices in the SDN.

Virtualized software-defined network

A method may include receiving monitor data via the control plane from at least one device of a set of devices in the SDN. The method may further include generating a data model based on a set of SDN parameters and the monitor data. The method may also include determining a change for at least one device of the set of devices in the SDN based on the data model. The method may include generating a policy, based on the change for at least one device of the set of devices in the SDN. The method may further include sending the policy via the control plane to the set of devices in the SDN.

Controlling a software-defined network

A computer-implemented method for increasing the scalability of software-defined networks may include (1) maintaining a set of databases collectively configured to (i) store a set of flow entries that direct network traffic within a software-defined network and (ii) facilitate searching the set of flow entries based at least in part on at least one key whose size remains substantially constant irrespective of the number of flow entries within the set of flow entries, (2) detecting a request to perform an operation in connection with a flow of data packets within the software-defined network, (3) identifying at least one attribute of the flow of data packets in the request, and then (4) searching, using the attribute of the flow of data packets as a database key, at least one database within the set of databases to facilitate performing the operation. Various other methods, systems, and apparatuses are also disclosed.

Systems and methods for increasing the scalability of software-defined networks

In general, this disclosure describes a high-level forwarding path description language (FPDL) for describing internal forwarding paths within a network device. The FPDL enables developers to create a template that describes a section of an internal forwarding path within the forwarding plane of a network device. The FPDL provides syntactical elements for specifying the allocation of forwarding path structures as well as enabling the run-time construction of internal forwarding paths to interconnect the forwarding path structures in a manner specific to packet, packet flow, and/or interface properties, for example. In conjunction with late binding techniques, whereby the control plane of the network device provides arguments to template parameters that drive allocation by the packet forwarding engines of forwarding path structures specified by the FPDL, the techniques provide control plane processes a unified interface with which to manage the operation of the packet forwarding engines.

Packet forwarding path programming using a high-level description language

In some embodiments, an apparatus includes a first core device configured to be disposed within a network. The network has a set of access nodes and a second core device. The first core device is configured to receive a signal designating the first core device as a master device for a virtual group identifier such that the second core device is designated as a back-up device for that virtual group identifier.

Methods and apparatus for load balancing VLAN traffic

A computer-implemented method for interfacing software-defined networks with non-software-defined networks may include (1) receiving at least one packet via software-defined network at a switching device, (2) searching a set of flow entries that collectively direct network traffic within the software-defined network for a flow entry that corresponds to the packet, (3) determining that the packet is destined for a non-software-defined network based at least in part on the search, and (4) forwarding the packet to the non-software-defined network via a logical tunnel that interfaces the software-defined network with the non-software-defined network by connecting a virtual port within the software-defined network to a virtual port within the non-software-defined network. Various other methods, systems, and computer-readable media are also disclosed.

Systems and methods for interfacing software-defined networks with non-software-defined networks

Growing community of inventors

San Ramon, CA, United States of America

Sandeep Bajaj