Big Switch Networks, Inc.

Arista Networks, Inc.

Kanzhe Jiang

Mandeep Singh Dhami

Srinivasan Ramasubramanian

Robert Edward Adams

Robert Wesley Sherwood

Sudeep Modi

Shunjia Yu

Richard Kyle Forster

Gregor Maier

Subrata Banerjee

Prashant Gandhi

Shudong Zhou

Mei Yang

Vishnu Emmadi

Kuang-Ching Wang

Zhao Dong

Weifan Fu

Jialiu Wang

Guido Appenzeller

Sandip K Shah

Daniel Talayco

Onkar Bhat

Chi Lung Chong

Ryan Izard

Alok Kumar Gupta

Junaid Zulfiqar

Christian Geddings Barrineau

Shengda Wang

Sumit Arun Naiksatam

Michael Cohen

Alexander Stafford David Reimers

Ganesh Kasinathan

Saadet Savas

Alan Hase

Jai Prakash Shukla

Gregor Mathias Maier

Robert W Sherwood

Sudeep Dilip Modi

Daniel E Talayco

Mandeep Singh Diiami

A framework for facilitating the capturing and querying of network traffic (packets) is provided. In one set of embodiments, the framework enables the assignment of tags to sets of related network device interfaces. For example, a tag Tmay be assigned to a set of network device interfaces that carry traffic for an application or service A, a tag Tmay be assigned to a set of network device interfaces that carry traffic for an application or service A, and so on. The framework further enables the use of these tags for provisioning packet capture sessions and for querying the resulting captured packets.

Tag-based packet capture and query

A networking system may include a switch coupled to a computing resource. A resource management system may control the computing resource. A controller may be coupled to the switch. The controller may include a resource management interface that is coupled to the resource management system via a communications link. The resource management interface may receive computing resource information for the computing resource via the communications link. The controller may provide control data to the switch to update a cloud network for the computing resource based on the received computing resource information.

Systems and methods for integrating network switch management with computing resource management

A networking system may include a first network such as a private cloud network and a second network such as a public cloud network. The first network may include a switch coupled to a computing resource. To facilitate a robust and flexible inter-network connection, the networking system may include network connector circuitry having a connector endpoint at the first network and a network connector coupling the connector endpoint to a network element at the second network. A controller for the first network may provide control signals and configuration data to the network connector circuitry to form the connection to the second network and may configure the switch to forward external network traffic to and from the connector endpoint via a switch port directly coupled to the connector endpoint.

Systems and methods for providing network connectors

A packet forwarding network may include spine and leaf switches that forward network traffic between end hosts. The packet forwarding network may be implemented on multiple network racks in a rack-based system. A controller may control the underlying spine and leaf switches to form on-premise virtual private cloud (VPC) resources. In particular, the controller may form enterprise VPC (EVPC) tenants, each having a virtual router that performs routing between different segments within the corresponding EVPC tenant. The different segments may separately include web, application, and database servers, as end hosts. The controller may form a system VPC tenant having a virtual system router that performs routing between different EVPC tenants. A segment in an internal VPC tenant formed by the controller and/or an external VPC tenant formed by the controller may provide external network access for one or more of the EVPC tenants.

Systems and methods for forming on-premise virtual private cloud resources

A network of switches having ports coupled to other switches or end hosts may be controlled by a controller. The controller may identify whether any switch ports have failed. In response to identifying that a port has failed at a first switch, the controller may modify link aggregation group mappings of the other switches to handle failover. The controller may modify the link aggregation group mapping of each other switch to include a first mapping that includes ports coupled to the first switch and a second mapping that does not include any ports coupled to the first switch. The controller may configure forwarding tables at the switches to forward network packets using the first or second mappings based on network topology information maintained by the controller.

Systems and methods for handling link aggregation failover with a controller

A controller implemented on computing equipment may be used to control switches in a network. End hosts may be coupled to the switches. The controller may generate a virtual network topology of virtual switches, virtual routers, and virtual system routers that are distributed over underlying switches in the network. The controller may form virtual switches from respective groups of end hosts, virtual routers from groups of virtual switches that include virtual interfaces that are coupled to virtual switches, and a virtual system router from groups of virtual routers that includes virtual system router interfaces that are coupled to the virtual routers. The controller may control the virtual network topology by generating respective flow table entries based on identified network policies for each of the virtual routers, virtual system routers, and virtual switches. The controller may control the virtual system routers to route packets between the virtual routers.

Systems and methods for performing logical network forwarding using a controller

A controller may fulfill hardware address requests that are sent by source end hosts in a network to discover hardware addresses of destination end hosts. The controller may use network topology information to determine how to process the hardware address requests. The controller may retrieve a requested hardware address from a database of end hosts. If the controller is able to retrieve the hardware address of a destination end host from the database of end hosts, the controller may provide the source end host with a reply packet that contains the requested hardware address. If the controller is unable to retrieve the requested hardware address, the controller may form request packets to discover the address of the second end host and/or to discover a packet forwarding path between the source end host and the destination end host.

System and methods for managing network hardware address requests with a controller

A controller may be used to control client switches in a network that includes non-client, switches. The controller may form client domains from groups of client switches that are separated by intervening non-client domains formed from non-client switches. The controller may determine a network domain topology from the client domains and non-client domains. The controller may determine a spanning tree that interconnects the nodes of the network domain topology. The controller may control client switches of the client domains to allow only network traffic between the client domains and the non-client domains along the spanning tree. The controller may use the network domain topology to generate inter-domain forwarding maps. The inter-domain forwarding maps may be used to determine network forwarding paths between end hosts in the network.

Systems and methods for forwarding network packets in a network using network domain topology information

A controller implemented on computing equipment may be used to control switches in a network. End hosts and service devices may be coupled to the switches in the network. The controller may generate a virtual network topology of virtual switches and virtual routers. The controller may control the virtual routers and/or virtual switches to perform service insertion. The controller may perform service insertion by controlling the virtual routers and/or virtual switches to redirect network traffic through one or more selected service devices. The controller may determine which network traffic is to be redirected to which service devices based on a service insertion policy that identifies network traffic and services to be performed on the network traffic.

Systems and methods for performing network service insertion

A controller may be used to control client switches in a network that includes non-client switches. The controller may form client domains from groups of client switches that are separated by intervening non-client domains formed from non-client switches. The controller may determine a network domain topology from the client domains and non-client domains. The controller may determine a spanning tree that interconnects the nodes of the network domain topology. The controller may control client switches of the client domains to allow only network traffic between the client domains and the non-client domains along the spanning tree. The controller may use the network domain topology to generate inter-domain forwarding maps. The inter-domain forwarding maps may be used to determine network forwarding paths between end hosts in the network.

A controller may help reduce network traffic that is associated with broadcasting of Dynamic Host Configuration Protocol (DHCP) packets by converting broadcast DHCP packets into unicast DHCP packets and forwarding the unicast DHCP packets to appropriate DHCP servers. The servers may be identified from a database of servers that is updated with DHCP server address information based on DHCP reply packets that are received by the controller from servers in the network. To convert DHCP request packets into unicast packets, the controller may modify address header fields of the packets such as Ethernet addresses and Internet Protocol (IP) addresses. The controller may forward the modified DHCP request packets to the server by providing packet forwarding rules such as flow table entries to the switches or by forwarding the modified DHCP request packets through the controller.

System and methods for managing network protocol address assignment with a controller

Network packets may be transmitted from packet sources to packet destinations through a network of switches. The switches may have corresponding flow tables that control how the packets are forwarded through the switches. A controller server may generate network switch forwarding paths for the network packets by modifying the flow tables with entries based on attributes of the network packets and network topology information. The controller server may forward selected packets directly to packet destinations instead of generating the network switch forwarding paths. To determine which packets to directly forward, the controller server may calculate cost metrics associated with the network switch forwarding paths and associated with forwarding network packets directly to packet destinations. The cost metrics may be calculated based on network topology information, network traffic conditions, controller server processing load, packet forwarding delays, an expected number of future network packets, or attributes of the network packets.

System and methods for forwarding packets through a network

Growing community of inventors

Los Altos Hills, CA, United States of America

Kanzhe Jiang