As developers, we need to store persistent data for a variety of reasons:
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:
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.
Now that we have:
We now can achieve Infrastructure As Code, where we can take…
Note: Everything in
/var/lib/avi/logs is managed by Elasticsearch. I wouldn't mess with it.
Events published to the GUI:
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. …
Before beginning the Avi installer, I configured the following in my environment:
Load balancing is an important aspect of network mobility.
How is a network useful if you can’t move around within it?
If Avi Vantage IPAM cannot allocate an address for a new vIP, it will advertise an all-zeros host address —
This will cause Palo Alto PAN-OS to restart a peer — even if it is not the immediate downstream prefix. …
NSX-T Edge nodes have a rudimentary packet capture tool built in to the box. It is important to have a built-in tool here, as GENEVE encapsulation will wrap just about everything coming out of a transport node.
NSX-T’s CLI guide indicates the method for packet captures — from here we…
When doing ADC/Load Balancer work, nearly all requests fit into two categories:
These are fairly simple to implement in NGINX, so I’m creating a couple of cheat-sheet code snippets here.
URI stripping is fairly common…