Zsoldier's Tech Blog

via GIPHY Summary: Basically, I work through VPN's most of my existence.  The problem lies when I have to switch to different VPN's it disrupts my communications w/ other tools that only exist in one VPN, but not the other.  There does appear to be tools around some of these things, but I wanted something quick and dirty.  AND DIRTY it is.  This enables me to stay connected to the main VPN and cheat by sshuttle'ing through systems of access temporarily. Details: I'm using MACOS and to launch a terminal in a new window turned me on to AppleScript.  I wanted to pass two variables. 1st was basically an identifier for the end system I wanted to shuttle my traffic through. 2nd was to pass a password variable to any system inbetween that was not setup w/ my SSH public key. So I made a bash function, to call applescript to open my terminals to run what is effectively a python binary.  It works, but has several prerequisites for it to run smoothly....

Summary: My colleague asked if there is a way to see in the UI whether an ER circuit is enabled for Global Reach .  After a quick check, there doesn't appear to be any obvious way to know.  So I decided to make something in powershell using the AZ module to return circuits that are Global Reach enabled and to return the data in a human readable form. Script: I'm using nothing but "Gets" so it's pretty safe to use.  Has come in handy on more than one occasion.  Anyway feel free submit feedback on gist or transform it for your use cases.

While there are a lot of differences between the two underneath, the basic setup remains largely the same.  However, know that the Manager and Controllers are now combined.  You basically have a manager/controller cluster now instead.  Basically 3 VMs instead of 4.  The biggest differences start to come into play when you begin deploying components (N-VDS, logical switches, routers, etc.) after these steps. With both, to start, you deploy the NSX Manager/Controller first.  NSX-V was ova only, NSX-T Manager has both ova and qcow2 (for KVM) appliances.  Going to focus on vSphere with vCenter available. After the manager/controller node is deployed is where things diverge significantly. NSX-T: Add "Compute Manager" (as of version 2.3) vCenter 6.5+ Adding vCenter makes management overhead of adding new hosts easier since you've now effectively delegate that job to vCenter. With NSX-V this process is very similar except that NSX-V was tightly co...