Your browser failed to load CSS style sheets. Your browser or web proxy might not support elliptic-curve TLS

Building network automation solutions

6 week online course

reserve a seat
back to overview

Traffic Trombone (what it is and how you get them)

Every so often I get a question “what exactly is a traffic trombone/tromboning”. Here’s my attempt at a semi-formal definition.

Traffic trombone is a term (probably invented by Greg Ferro) that colorfully describes inter-VLAN traffic flows in a network with stretched (usually overlapping) L2 domains.

In a traditional L2/L3 data center architecture with small L2 domains in the access layer and L3 forwarding across the core network, the inter-subnet traffic flows were close to optimal: a host would send a packet toward the first-hop (ingress) router (across a bridged L2 subnet), the ingress router would forward the packet across an optimal path toward the egress router, and the egress router would deliver the packet (yet again, across a bridged L2 subnet) to the destination host.

If you draw your network diagrams with core layer at the top and access layer at the bottom, the north-south traffic would be bridged (or you could already introduce routing in access or aggregation layer) and the east-west traffic would be routed. The traffic across the network core and the end-to-end latency would be minimal (the same packet would traverse the core only once).

In designs that stretch a single L2 domain across the network core (within or even between data centers), the first-hop router might be far away from the host originating the packet. The packet thus traverses the core before reaching the first-hop router, significantly increasing the latency and east-west traffic load.

In a truly broken design with mixed routing and bridging in the network core (or in designs where L3 forwarding is implemented by virtual machines), the packet might have to traverse the core multiple times before reaching the destination host.

When L2 domains stretch across multiple data centers, traffic flows belonging to a single user session might have to traverse Data Center Interconnect (DCI) link multiple times.

More information

The Data Center Interconnect webinar (register here) describes network designs that help you avoid stretched L2 domains and the tools you can use to reduce the amount of east-west traffic caused by stretched VLANs.


  1. If you can find a quote from Greg that predates this reference to trombone with respect to wireless traffic flow -

  2. Already common in 2000: cellular network:
    Note that it was deliberate: connections re-circulated through the network to avoid expensive termination points. The EU took the opposite view: connections should be optimally routed regardless of cost.

  3. I came across the term "tromboning" in connection with telephone networks in around 1965. Consider the following scenario. A external call is received in Office A and is then transferred over a trunk link to an extension in Offfice B at the other side of town. The call is then transferred back to another extension in Office A. Two of the limited intersite trunk links are then in use and it can get worse if the call is then transferred back to et another extension in Office B. We had just 6 intersite links in those days.


You don't have to log in to post a comment, but please do provide your real name/URL. Anonymous comments might get deleted.