I see no traffic referencing the IP other than an ARP from the secondary after a failure of the primary.This post will cover why to deploy an appliance along with a DLR, configuring the appliance for high availability and how the DLR high availability feature works.Man is a universe within himself.
B. Marley When you add interfaces to a UDLR the only option is Logical Switches and the table will only show Universal Logical Switches to pick from. Vmware Virtual Router Appliance How To Be SensibleBut then they send me away to teach me how to be sensible An appliance deployed with a DLR will have a simple name in vSphere like MyFirstDLR-0 UDLR appliances have names like edge-768ba914-619b-40de-a5a7-4cf8d0c0640e-0-UDLR Both DLR and UDLR create the same appliance a 1 vCPU 512MB 1GB (two 500MB VMDKs). Interestingly the type is vShield Edge: Which is also what it greets you with at the initial login: Its like Hidden Mickeys To Deploy or not to deploy. Speaking of deploying DLR appliances do you need one The NSX UI says under Deploy Edge Appliance: Deploys NSX Edge Appliance to support Firewall and Dynamic routing. However, you can configure the DLR firewall without deploying an appliance (you can test this in Hands On Labs in about 5 minutes). I believe it means you cant protect the deployed appliance with a firewall unless you deploy the appliance. Which is a little circular The official docs state in section 6.3 Docs Add a Logical (Distributed) Router An edge appliance (also called a logical router virtual appliance) is required for dynamic routing and the logical router appliances firewall, which applies to logical router pings, SSH access, and dynamic routing traffic. Which also all appears to mean that an appliance is required for SSH access (which would be to the deployed appliance) and dynamic routing. In the same section the docs state: High availability is required if you are planning to do dynamic routing. Note that if you choose to deploy an appliance you must select an HA Interface Configuration (logical switch or distributed port group) even if you didnt select HA. However, you dont have to add an IP Address (thats optional and new to version 6.3). More on High availability If you enable DLR HA during deployment it will automatically create two appliances and if you specified two different Resource poolDatastore pairs then it will create one in each location. Start it up. M Jagger If you dont enable DLR HA, you can add another appliance later but it will just sit there undeployed until HA is enabled. Note when you enable HA the Logical Router Appliances table gets a new column to let you know the heartbeat is up. Why HA With high availability enabled, the dynamic router functionality can be recovered in seconds instead of the time it takes vSphere High Availability to recover it. By default, the secondary appliance waits for about 15 seconds after a failure to take over dynamic routing updates. This delay is configurable as Declare Dead Time in the HA Configuration tile in the DLR configuration tab. It also keeps the VM under NSX management the configuration could break if restarted on a different host by vSphere HA. ![]() Im not entirely sure how configuration updates are made to the control VM since network connectivity to the NSX manager is not a requirement. Possibly via VMware Tools If anyone knows please drop me a line. How DLR HA works Note that this is via observation, Wireshark and contemplation. When you configured HA on 6.2 there was no option to add an IP address, you just needed to pick a logical switch or port group to connect to. HA IP address. IP in the pool. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |