With the previous post, I covered traditional data center networking, and some of the reliability compromises made to accommodate typical workloads. Here I’ll be outlining my take as a series of blog posts on the next iteration of data center network design, Spine and Leaf:
Lab Diagram

Note: This page may change based on content. I’m going to try and keep things generic up until the very end.

Originally published at https://blog.engyak.net.

Get into the OS Shell (all elements)

Controller Log Locations

Note: Everything in /var/lib/avi/logs is managed by Elasticsearch. I wouldn't mess with it.

Events published to the GUI: /var/lib/avi/logs/ALL-EVENTS/

The primary log directory for Avi Vantage Controllers is /opt/avi/log. As this feeds into Elasticsearch, they have file outputs for every severity level. …

Pre-Requisites

Before beginning the Avi installer, I configured the following in my environment:

  • Data Segments (NSX-T Overlay). Avi will build direct routes to IPs in this network for vIP processing. …

Load Balancing is Important

Load balancing is an important aspect of network mobility.

How is a network useful if you can’t move around within it?

  • Wi-Fi networks are designed to facilitate smaller-scale movements. …

When doing ADC/Load Balancer work, nearly all requests fit into two categories:

  • Please change the host header for this reverse proxy

These are fairly simple to implement in NGINX, so I’m creating a couple of cheat-sheet code snippets here.

“Strip Part of the URL Out”

URI stripping is fairly common…

Nick Schmidt

I am a network engineer based out of Alaska, pursuing various methods of achieving SRE/NRE

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store