ddesmidt's Posts

ddesmidt · ‎09-30-2019

Available now

ddesmidt · ‎08-19-2019

This is one document to learn everything about NSX-T native LB capabilities. NSX-T LB ToI This document highlights NSX-T LB capabilities and its latest NSX-T 3.1 enhancements. You can ...

This is one document to learn everything about NSX-T native LB capabilities. NSX-T LB ToI This document highlights NSX-T LB capabilities and its latest NSX-T 3.1 enhancements. You can find another great document to learn everything about NSX-T LB Configuration and Management: NSX-T LB Encyclopedia This document goes over all the Configuration and Management questions you may have on NSX-T LB and much more! It lists all NSX-T LB capabilities (LB Deployment, Monitor, Server Pool, L4 VIP, L7-HTTP VIP, L7-HTTPS VIP, LB Rules, and Troubleshooting) with detailed examples for each. Document available on NSX-T LB Encyclopedia

ddesmidt · ‎08-19-2019

This is one document to learn everything about NSX-T LB Configuration and Management. NSX-T LB Encyclopedia. This document goes over all the Configuration and Management questions you may hav...

This is one document to learn everything about NSX-T LB Configuration and Management. NSX-T LB Encyclopedia. This document goes over all the Configuration and Management questions you may have on NSX-T LB and much more! It lists all NSX-T LB capabilities (LB Deployment, Monitor, Server Pool, L4 VIP, L7-HTTP VIP, L7-HTTPS VIP, LB Rules, and Troubleshooting) with detailed examples for each. Note: Deck updated with NSX-T 3.1. You can find another great document to learn everything about NSX-T native LB capabilities: NSX-T LB ToI This document highlights NSX-T native LB capabilities and its latest NSX-T 3.1 enhancements. Document available on: NSX-T LB ToI

ddesmidt · ‎08-19-2019

No it does not.

ddesmidt · ‎07-01-2019

As discussed by email, you have an extra “space” before the “=”. DEFAULT_OVERLAY_TZ_UUID=6bdb981c-a030-4a11-a235-6ea243c2dbb8

ddesmidt · ‎06-04-2019

. I can only attach one router per network. Correct. And with Neutron AZ, you can decide on which Edge Cluster it will be deployed (configuring special "default_tier0_router"). . With NSX-...

. I can only attach one router per network. Correct. And with Neutron AZ, you can decide on which Edge Cluster it will be deployed (configuring special "default_tier0_router"). . With NSX-T a router can be associated with only one AZ. (This differs from openvswitch OpenStack Docs: Availability zones) Correct. . I can not attach routers to routers. My application needs to exchange some data between instances. With Neutron NSX-T plugin, only 1 OpenStack Router can be attached to a specific OpenStack Network. This OpenStack Router is "translater" to one NSX-T Tier-1 Gateway. If your application is on different Openstack Networks each connected to different OpenStack Routers, then the communication is still possible with Neutron NSX-T Plugin. It will go from VM-A to T1-A to T0 to T1-B to VM-B. Now if you have very specific design question, please send me a diagram on my email (ddesmidt@vmware.com)

ddesmidt · ‎03-25-2019

There is no committed day/release for that feature yet. Can you contact ddesmidt@vmware.com for your "Local Egress" Use case and understand how you are looking at using it. Thanks, Dimitri

ddesmidt · ‎03-21-2019

NSX-T 2.4 enhanced its management plane with the support of NSX-T Manager Cluster. NSX-T Managers Cluster offer a built-in VIP for high-availability. But the usage of an external load balance...

NSX-T 2.4 enhanced its management plane with the support of NSX-T Manager Cluster. NSX-T Managers Cluster offer a built-in VIP for high-availability. But the usage of an external load balancer offers the following benefits: Load spread across all NSX-T Managers NSX-T Managers can be in different subnets Faster failover NSX-T supports load balancing service, and the same NSX-T platform can be configured to load balance its NSX-T Managers Cluster. This document describes this configuration and is valid for NSX-T 2.4 and more recent releases (like NSX-T 2.5 and NSX-T 3.0).

ddesmidt · ‎03-18-2019

This document highlights NSX MultiSite capabilities including: . Latest enhancements . What is NSX Multisite . NSX Multisite Capabilities . Recorded Demos For deeper information, we...

This document highlights NSX MultiSite capabilities including: . Latest enhancements . What is NSX Multisite . NSX Multisite Capabilities . Recorded Demos For deeper information, we also offer the "NSX Federation Multi-Location Design Guide (Federation + Multisite)" here. Also FYI, VMworld 2019 had a public session presenting NSX Multisite "NSX-T Design for Multi-Site [CNET1334BU]" Recording + Deck. Note1: This ToI may be updated in the future so always check you have the latest version. . NSX 4.0-4.1 Multisite 101 ToI version is 1.0 done on 03/02/2023. . NSX-T 3.2 Multisite 101 ToI version is 1.1 done on 01/10/2023. Note2: NSX Multisite solution is perfect for customers who want a "Smaller NSX Management Footprint" (with only 3x NSX Mgr VMs for all their locations), and accept a "DR Recovery Procedure with few more requirements or steps". For other use cases, NSX-T 3.0 introduced a second Multi-Location solution: NSX Federation. NSX Federation solution is based on a new component: “NSX Global Manager Cluster” (GM). GM offers a central global configuration of multiple (local) NSX Manager Cluster, each offering Network & Security services for a Location. NSX Federation solution replies to "Specific Site Management/ GDPR/ Policy Requirements", and offers "Simplified DR".

ddesmidt · ‎11-12-2018

Just did add the "AZ" section. It's a small section, as it's simply offers specific NSX-T configuration per AZ. And use cases are: . different NSX-T Mgr . different Edge Nodes for default_T...

Just did add the "AZ" section. It's a small section, as it's simply offers specific NSX-T configuration per AZ. And use cases are: . different NSX-T Mgr . different Edge Nodes for default_T0, and/or default_overlay, and/or default_vlan, and/or the metadata-proxy, and/or DHCP.

ddesmidt · ‎12-07-2017

The goal of that document is to give a very deep technical understanding on . How to configure the different network and security services in OpenStack . How OpenStack/NSX-T works It ...

The goal of that document is to give a very deep technical understanding on . How to configure the different network and security services in OpenStack . How OpenStack/NSX-T works It is based on OpenStack Queens. Note: It also highlights the specifics with VIO. Dimitri

ddesmidt · ‎03-07-2017

I suggest you look at the CLI "show service loadbalancer virtual". This will give you information on why the pool member is detected down. This should give you clue on what's wrong. Dimitri

ddesmidt · ‎02-16-2017

When you do "SSL-Passthrough" the clients terminate their HTTPS traffic on the pool members. So your Pool members are on https TCP 443. When you do "SSL-Offload" the clients terminate their HT...

When you do "SSL-Passthrough" the clients terminate their HTTPS traffic on the pool members. So your Pool members are on https TCP 443. When you do "SSL-Offload" the clients terminate their HTTPS traffic on the Edge-LB and then Edge-LB talks to the Pool members on http TCP 80. Did you do change your pool member configuration and healthchecks? Dimitri

ddesmidt · ‎02-08-2017

NSX does not offer Network & Security configuration via CLI (LB included). The 2 options are: . UI . API For the API you can find a dedicated API documentation. Note: If you like Power...

NSX does not offer Network & Security configuration via CLI (LB included). The 2 options are: . UI . API For the API you can find a dedicated API documentation. Note: If you like PowerCLI, there is also an open project to drive NSX via PowerCLI called PowerNSX https://github.com/vmware/powernsx. There was a dedicated session at the last VMworld 2016: NET7701. Thanks, Dimitri

ddesmidt · ‎01-28-2017

With NSX Load Balancing (as with any load balancer): . The incoming traffic (client to server) has to go through to the load balancer That's easily done since the client talks to a VIP whi...

With NSX Load Balancing (as with any load balancer): . The incoming traffic (client to server) has to go through to the load balancer That's easily done since the client talks to a VIP which is hosted by the LB . The return traffic (server to client) has to go through to the load balancer If that traffic "naturally" goes via the LB (because the server default gw is the LB for instance), then you're all good. If that traffic does NOT go via the load balancer (like in 1-arm mode), then the workaround is to use SNAT on the load balancer to ensure the server response will go through it In your case I understand you're in 1-arm mode and I bet the server default gw is NOT the LB => so you must use SNAT on your LB VIP. Dimitri

ddesmidt · ‎01-23-2017

Yes you can do that. In that case, you do NOT configure any logical switch on NSX. You simply plug the VMs on the vSphere VDS Port Group associated to that VLAN (nothing to do with NSX). The...

Yes you can do that. In that case, you do NOT configure any logical switch on NSX. You simply plug the VMs on the vSphere VDS Port Group associated to that VLAN (nothing to do with NSX). Then about: . DFW: You can still use DFW even for VMs plugged on VDS-VLAN_PortGroup. . LB You can still do it in one-arm mode (with the Edge-LB connected to the VDS-VLAN_ProtGroup All good Dimitri

ddesmidt · ‎01-23-2017

When backend pool member is down and/or the whole VIP is down; the Edge will generate a syslog message. Dimitri

ddesmidt · ‎01-23-2017

I understand you have your VLAN A (10.1.1.0/24). And you want to do an L2 extension to VXLAN B. So VXLAN B has the same subnet 10.1.1.0/24. But you don't explain how you configure the L2 exte...

I understand you have your VLAN A (10.1.1.0/24). And you want to do an L2 extension to VXLAN B. So VXLAN B has the same subnet 10.1.1.0/24. But you don't explain how you configure the L2 extension. If that's NOT with L2 Bridging NOR L2 VPN, how is it done? DImitri

ddesmidt · ‎01-19-2017

We don't clearly say "LB Persistence table is synched" in our Admin Guide. However we say in the HA section: NSX Edge HA synchronizes the connection tracker of the statefull firewall, or the st...

We don't clearly say "LB Persistence table is synched" in our Admin Guide. However we say in the HA section: NSX Edge HA synchronizes the connection tracker of the statefull firewall, or the statefull information held by the load balancer. Dimitri

ddesmidt · ‎01-18-2017

You're 100% right

All

ddesmidt's Posts

Re: NSX-T LB Encyclopedia

NSX-T LB ToI

NSX-T LB Encyclopedia

Re: NSX-v 6.4 - Load Balancing ToI

Re: OpenStack&NSX-T - Network Topologies Configuration Guide

Re: OpenStack&NSX-T - Network Topologies Configuration Guide

Re: NSX-T Multisite

NSX-T Manager Cluster External LB by NSX-T

NSX Multisite 101 ToI

Re: OpenStack&NSX-T - Network Topologies Configuration Guide

OpenStack&NSX-T - Network Topologies Configuration Guide

Re: NSX Load Balancer issue

Re: LB works fine in ssl passthru but it does not work properly in ssl offload.

Re: Can NSX load balancer be managed by CLI?

Re: One Arm Load Balancer

Re: L2 Extension to NSX

Re: NSX Load Balancer - Test Plan

Re: L2 Extension to NSX

Re: NSX Native Load Balancer vs BIG IP Load Balancer

Re: NSX Native Load Balancer vs BIG IP Load Balancer