Amazon Technologies, Inc.

Justin Oliver Pietsch

Alan Michael Judge

Jagwinder Singh Brar

Mark Noel Kelly

Michael David Marr

Tyson James Lamoreaux

James Robert Hamilton

Frederick David Sinn

David J O'Meara

David J McGaugh

Mark Y Kelly

Leonard Thomas Tracy

Stephen Callaghan

Rachit Chawla

Colin John Whittaker

Edward Crabbe

David J Mcgaugh

Alan M Judge

David J O'meara

Richendra Khanna

Richard Hazen Galliher, Iii

Jeremy Volkman

Abhoy Bhaktwatsalam

Christopher John Rose

Mayilan Balachandran

Spencer Giacalone

Nafea Bshara

Thomas A Volpe

Mark Bradley Davis

Matthew Shawn Wilson

Andrew Bruce Dickinson

Thomas Bradley Scholl

Aaron Craig Thompson

Dmytro Taran

Daril Alexandre Vilhena

Kenneth Oliver Henderson, Jr

Amit Sahoo

Brian Myungjin Choi

Christopher Edward Folger

Tyson J Lemoreaux

David J O'MEARA

The following description is directed to managing a hierarchical network including one or more network zones. In one example, a method of managing a hierarchical network includes collecting network state from respective devices of a network zone; using the collected network state to build an aggregated topology of the network zone; and transmitting the aggregated topology of the network zone to a traffic engineering service.

Managing a hierarchical network

Network packet tracing may be implemented on packet processors or other devices that perform packet processing. As network packets are received, a determination may be made as to whether tracing is enabled for the network packets. For those network packets with tracing enabled, trace information may be generated and the network packets modified to include the trace information such that forwarding decisions for the network packets ignore the trace information. Trace information indicate a packet processor as a location in a route traversed by the network packets and may include ingress and egress timestamps. Forwarding decisions may then be made and the network packets sent according to the forwarding decisions. Tracing may be enabled or disabled by packet processors for individual network packets. Trace information may also be truncated at a packet processor.

Network packet tracing

Techniques for dynamic augmentation of server rack network capacity are provided herein. Network nodes are described that are connected between server rack switches and a rack aggregation layer device. A port allocation controller is also described that can automatically reconfigure the network nodes to create connections, via the network nodes, between the rack aggregation layer device and the server rack switches. These network node connections can be used to alter the network capacities of the server rack switches in response to changing network demands.

Dynamic network capacity augmentation for server rack connectivity

A dynamic configuration system can manage and configure switches or other network devices that come online in a network. When the dynamic configuration system determines that a network device has come online, the dynamic configuration system can identify the network device (e.g., based on its network location, neighbors, fingerprint, identifier, address or the like), select the appropriate configuration data for the network based on the desired network topology, and transmit the configuration data to the network device. The network device can then load the configuration data and function as a component of the desired network topology.

Dynamic network device configuration

Disclosed are various embodiments for performing network traffic redirection at the client side. Sending of data to a service at a network address is initiated. Whether the network address is in a predetermined network address range is determined. The network address is translated, when the network address is in the predetermined network address range, to one of multiple other network addresses based at least in part on an availability of the service at the other network address. The data is routed to the other network address.

Client traffic redirection service

Efficient and highly-scalable network solutions are provided that each utilize deployment units based on Clos networks, but in an environment such as a data center of Internet Protocol-based network. Each of the deployment units can include multiple stages of devices, where connections between devices are only made between stages and the deployment units are highly connected. In some embodiments, the level of connectivity between two stages can be reduced, providing available connections to add edge switches and additional host connections while keeping the same number of between-tier connections. In some embodiments, where deployment units (or other network groups) can be used at different levels to connect other deployment units, the edges of the deployment units can be fused to reduce the number of devices per host connection.

Connecting network deployment units

A hierarchical distributed routing architecture including at least three levels, or layers, for receiving, processing and forwarding data packets between network components is provided. The core level router components receive an incoming packet from a network component and identify a distribution level router component based on processing a subset of the destination address associated with the received packet. The distribution level router components that receiving a forwarded packet and identify a transit level router component based a second processing of at least a subset of the destination address associated with the received packet. The transit level router components receive the forwarded packet and forward the packet to a respective network. The mapping, or other assignment, of portions of the FIB associated with the distributed routing environment is managed by a router management component.

Distributed routing architecture

The following description is directed to configuring network devices. In one example, at a network device deployment pipeline, a request can be received from a non-integrated configuration tool to configure a network device of a network. The configuration of the network device can be scheduled so that both an integrated configuration tool of the network device deployment pipeline and the non-integrated configuration tool can configure the network.

Network device configuration deployment pipeline

A method for adjusting capacity in a multi-stage routing network includes monitoring a number of available connections between a router in a first stage of a multi-stage router network and one or more routers in a second stage of the multi-stage router network. Each of the stages of the multi-stage router network may include a plurality of routers. The method may also include detecting that the number of available connections falls below a threshold number. A notification can be sent to one or more routers in a third stage of the multi-stage router network that the router in the first stage is deprioritized. The one or more routers in the third stage can be operated so that communications to the first stage are routed to one or more other routers in the first stage.

Adjusting communication capacity in a multi-stage routing network

Efficient highly connected deployment units

Techniques and solutions for distributing routing updates using timing information are described. For example, inter-device messaging protocols can support timing information (e.g., routing protocols be extended to support timing information). The timing information can indicate a time at which the routing update is to be put into effect where the time decreases the further away a given routing device is from the source of the routing update. For example, each routing device can determine a decayed update reference time when the given routing device will put the routing update into effect according to a decay mode. Routing updates can be managed between routing devices that support timing information and routing devices that do not support timing information.

Distributing routing updates according to a decay mode

Fused data center fabrics

Techniques and solutions for distributing routing updates using timing information are described. For example, inter-device messaging protocols can support timing information (e.g., routing protocols be extended to support timing information). The timing information can comprise an indication of a time at which the routing update is to be put into effect. Using the timing information, a number of routing devices can put the routing update into effect at the same time (e.g., at an update reference time) according to a synchronous mode. Routing updates can be managed between routing devices that support timing information and routing devices that do not support timing information.

Distributing routing updates according to a synchronous mode

Methods and apparatus for transparent multipath utilization through encapsulation are disclosed. Respective encapsulation packets are generated for at least two different baseline packets transmitted between a source and destination linked by multiple network paths. Each encapsulation packet comprises contents of a corresponding baseline packet, and one or more data values selected in accordance with a path balancing policy. The data values added to one encapsulation packet may differ from those added to another. Different network paths to the destination may be selected for different encapsulation packets of a given transmission based at least in part on the added data values.

Transparent network multipath utilization through encapsulation

Growing community of inventors

Bothell, WA, United States of America

Justin Oliver Pietsch