Network Native

  In this blog post I'm going to discuss the NSX edge. I'll keep the explanation restricted to edges of virtual machine form factor. However, bare metal edges are also possible. The use-case for bare metal edges are high packet throughput scenarios, such as at a telco / ISP.  Architecturally, edges are the bridge between the physical network and NSX overlay network. Edges are a resource on which virtual routers and network services can be deployed. By services, I'm referring to things such as DHCP, NAT, stateful firewall, or most commonly, logical routing and switching and more.  To prepare your infrastructure for edge deployment, consider the following: Is our NSX edge cluster of a collapsed design (i.e. shared with compute cluster) or broken out into its own cluster as recommended by the NSX design guide? What is the management network? (needed: subnet, gateway, vlan, and vCenter portgroup, mgmt ip and FQDN) What network is connecting the TOR to the edge? (needed: subnet,

ESXi command "esxcli esxcli command list" is well documented on may blogs across the web. This blogpost is simply for my personal use. In this post I've listed the namespace of command "esxcli esxcli command list" 7.0 Update 2. By listing the output here, I can review the ESXi command name space without needing to ssh to an ESXi command line.  How do you use this list? First find a command that you think will be useful. For me, the following command was of use: hardware.ipmi.bmc                                   get           Get IPMI Baseboard Management Controller (BMC) properties. Namespace                                           Command       Description --------------------------------------------------  ------------  ----------- daemon.control                                      restart       Restart the daemons for the specified solution ID. daemon.control                                      start         Start the daemons for the specified solution I