NSX-T Eval Guide v2...NSX-T EVAL GUIDE V2 NETWORKING | 28 3.1.2. Create 2 Web VMs in VLAN "VLAN-Web"...

REVISED 20 APRIL 2020

NSX-T EVAL GUIDE V2

NSX-T EVAL GUIDE V2

NETWORKING | 2

Table of Contents

Overview

REQUIREMENTS

2. INSTALLATION OF NSX-T

– 2.1. Download of NSX Manager OVA

– 2.2. Deployment of NSX-T Manager

– 2.3. Register NSX-T to vCenter

–

– 2.5. Deployment of Edge Node

3. NSX EVALUATION

– 3.1. Security only (no Logical Network)

– 3.2. Logical Network and Security

– 3.3. Operation Tools

NSX-T EVAL GUIDE V2

NETWORKING | 3

NSX-T Eval Guide v2

Overview

The goal of this document is to offer a "step by step" NSX Evaluation Guide to test (some) NSX Services: - Security Services -Micro-Segmentation (DFW) - Logical Networking Services - Logical Switching – Logical Routing (with distributed routing) - Operationtools - Network Topology – Traceflow. NSX offers many more services, such as Load Balancing, VPN, IDS, NSX Intelligence,Federation, etc. Those are currently out of scope of that document. Also to limit the ESXi/Storage requirements, this evaluationdoes not cover high-availability and only 1 element of each NSX component will be installed.

REQUIREMENTS

Here are the requirements for NSX-T Evaluation.

Compute & Storage

NSX-T EVAL GUIDE V2

NETWORKING | 4

Networking

2. INSTALLATION OF NSX-TDisclaimer: The below install is a minimal installation intended for a lab environment only. We do not recommend below install in alive production environment.

NSX-T EVAL GUIDE V2

NETWORKING | 5

IP of each Element Management (VLAN11) Overlay -TEP (VLAN12)

vCenter 19.168.50.4 -

ESXi1 19.168.50.21 192.168.51.21

ESXi2 19.168.50.22 192.168.51.22

NSX-T Manager 19.168.50.5 -

Edge Node 19.168.50.31 192.168.51.31

2.1. Download of NSX Manager OVA

NSX-T EVAL GUIDE V2

NETWORKING | 6

2.2. Deployment of NSX-T Manager

From vCenter, deploy NSX-T Unified Appliance OVA.

Select OVF file

NSX-T EVAL GUIDE V2

NETWORKING | 7

From vCenter, deploy NSX-T Unified Appliance OVA.

Select OVF file.

Enter NSX-T Manager VM name + vCenter folder for VM.

Select ESXi to host NSX-T Manager.

NSX-T EVAL GUIDE V2

NETWORKING | 8

Review NSX-T Manager VM details.

Select NSX-T Manager VM size (Small).

https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/2.2.step6.jpg

NSX-T EVAL GUIDE V2

NETWORKING | 9

Select storage for NSX-T Manager VM.

Select VDS Port Group for NSX-T Manager management vNIC (vCenter Management Port Group).

Enter NSX-T Manager information (passwords, hostname, IP, DNS, NTP). Important: Role name is "NSX Manager".



NSX-T EVAL GUIDE V2

NETWORKING | 10

Review NSX-T Manager VM settings.

Once NSX-T Manager deployment is finished, start the VM.




NSX-T EVAL GUIDE V2

NETWORKING | 11

2.3. Register NSX-T to vCenter

Note: NSX-T Manager requires few minutes to fully start and get all its services running.

Log on NSX-T Manager UI.In a browser: https://192.168.50.5/.

Configuration NSX-T License.Under "System - Settings - Licenses", click "Add".

Register NSX-T in vCenter (to allow the deployment of NSX elements into vCenter/ESXi from NSX).Under "System - Configuration - Fabric - Compute Managers", click "Add".

https://192.168.50.5/



NSX-T EVAL GUIDE V2

NETWORKING | 12

Validate NSX-T registration in vCenter.Under "System - Configuration - Fabric - Compute Managers", click "Refresh" (bottom-left).

2.4. ESXi Host Preparation 2.4.1. New VDS-NSX creation

Create New VDS-NSX (for future NSX-T Logical Switches).From vCenter, under "Networking", select the Data Center, and right-click to create a "New Distributed Switch".For this lab, see the top of page for "Number of uplinks (1)",and "Default Port Group (none)".

https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/2.3.step3a.jpg

https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/2.3.step3b.jpg


NSX-T EVAL GUIDE V2

NETWORKING | 13

NSX-T EVAL GUIDE V2

NETWORKING | 14

Add that VDS-NSX to ESXi.From vCenter, under "Networking", select the VDS-NSX, and right-click to "Add and Manage Hosts...".

https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/2.4.1.step6.jpg

NSX-T EVAL GUIDE V2

NETWORKING | 15




NSX-T EVAL GUIDE V2

NETWORKING | 16

Configure that VDS-NSX with a large MTU (at least 1700).From vCenter, under "Networking", select the VDS-NSX, and right-click to "Add and Manage Hosts...".



NSX-T EVAL GUIDE V2

NETWORKING | 17

2.4.2. Uplink Profile CreationCreate Uplink Profile for Transport Nodes ("VLAN-Overlay + NIC" information for ESXis + Edge Node).From NSX-T, under "System - Configuration - Fabric - Profiles - Uplink Profiles", click "Add".For this lab, see the top of page for VLAN for Overlay traffic information (12),and number of uplinks for "VDS - NSX-T" information (1 NIC).



NSX-T EVAL GUIDE V2

NETWORKING | 18

2.4.3. Installation of NSX in ESXiConfigure NSX-T for ESXi.

Select each ESXi of vCenter-Cluster

Under "System - Configuration - Fabric - Node - Host Transport Nodes - Managed by", select "Lab-vCenter".Select Type = VDS (to enable NSX into the existing "VDS-NSX" vCenter Distributed Switch),Mode = Standard,Transport Zone = "nsx-overlay-transportzone" (Default TZ for overlay traffic) + "nsx-vlan-transportzone" (Default TZ for VLANtraffic),Uplink Profile = "Lab-HostProfile" (with VLAN-Overlay information),IP (TEP) = Information on top of the page,Uplink = ESX VDS Uplink1.

For each ESXi, configure its new "VDS - NSX-T"Click "Configure NSX".



NSX-T EVAL GUIDE V2

NETWORKING | 19

For each ESXi, validate "VDS - NSX-T" creation.

2.5. Deployment of Edge NodeNote: If you limit your Evaluation at Security only (no Logical Network) and not Logical Network + Security nor Operation Tools,you don't need to deploy Edge Nodes.

https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/2.4.3.step2a.jpg

https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/2.4.3.step2b.jpg


https://github.com/vmware-nsx/eval-docs/blob/master/docs/3.1-Security-Only.md

https://github.com/vmware-nsx/eval-docs/blob/master/docs/3.2-LogicalNetwork-Security.md

https://github.com/vmware-nsx/eval-docs/blob/master/docs/3.3-Operation-Tools.md

NSX-T EVAL GUIDE V2

NETWORKING | 20

2.5.1. Creation of VDS Port Group "All VLAN"Create a Port Group "All VLAN" (= VLAN Tag 0-4096) on VDS.From vCenter, under "Networking", select the VDS-NSX, and right-click to "New Distributed Port Group...". For this lab, seethe top of page for this Port Group on VDS.




NSX-T EVAL GUIDE V2

NETWORKING | 21

2.5.2. Installation of NSX Edge NodeDeploy 1 Edge Node on ESXi.Under "System - Configuration - Fabric - Nodes - Edge Transport Nodes", click "Add Edge VM".Select Form Factor Medium (useful if you want to test later Load-Balancing),enable SSH for admin and root if you want to try later deeper troubleshooting,Management and Switch (TEP) IP addresses on the top of the page), andTransport Zones = "nsx-overlay-transportzone" (default TZ for Overlay traffic) and "nsx-vlan-transportzone" (defaultTZ for VLAN traffic).




NSX-T EVAL GUIDE V2

NETWORKING | 22


NSX-T EVAL GUIDE V2

NETWORKING | 23

Validate Edge Node deployment.Under "System - Configuration - Fabric - Nodes - Edge Transport Nodes", click "Refresh" (bottom UI)

2.5.3. Creation of Edge ClusterCreate 1 Edge Cluster with EdgeNode1 member.Under "System - Configuration - Fabric - Nodes - Edge Clusters", click "Add".Select EdgeNode1 as member of that Edge Cluster.

NSX-T EVAL GUIDE V2

NETWORKING | 24

Validate Edge Cluster creation.Under "System - Configuration - Fabric - Nodes - Edge Clusters", click "Refresh".

3. NSX EVALUATION

Overview

NSX-T Services evaluated in that Evaluation Guide:

Security ServicesMicro-Segmentation (DFW)

Logical Networking ServicesLogical SwitchingLogical Routing (with distributed routing)



NSX-T EVAL GUIDE V2

NETWORKING | 25

Operation toolsNetwork TopologyTraceflow

NSX offers many more services, such as Load Balancing, VPN, IDS, NSX Intelligence, Federation, etc. Those are currently out ofscope of that document. Limit the ESXi/Storage requirements, this evaluation does not cover high-availability and only 1 elementof each NSX component will be installed.

NSX Evaluation3.Security only (no Logical Network)1.Logical Network + Security2.Operation Tools3.

3.1. Security only (no Logical Network)In this section, you'll configure 2 Web VMs on a new VLAN and provide micro-segmentation (DFW) on those 2 VMs.Important Note: In this section, the routing is still fully done by physical fabric.So your physical router needs an interface for that new VLAN (10.114.218.1/24 in lab).

Logical View

https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/3.1.LogicalView.jpg

NSX-T EVAL GUIDE V2

NETWORKING | 26

Physical View

The Security evaluation done in this chapter is focusing on NSX L4 Stateful North/South and East/West firewalling capabilities. NSX-T offers more than L4 Stateful firewall capabilities, such as Layer7 Firewalling, Intrusion Detection System (IDS), eco-system withSecurity Vendors like Checkpoint, Fortinet, or Palo Alto

3.1.1. Create VLAN in NSX-T


https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/3.1.PhysicalView.jpg

https://192.168.50.5/


NSX-T EVAL GUIDE V2

NETWORKING | 27

Create new VLAN "Web" + interface on physical router for this lab, see on top of the page for the physical routerinterface + VLAN information.There is no steps described in this document, as it varies per physical router.Create new VLAN Segment "VLAN-Web".Under "Networking - Segments", click "Add Segment".For this lab, see on top of the page for the VLAN number (16).Select Transport Zone = "nsx-vlan-transportzone" (Default TZ for VLAN traffic),VLAN = "16", and no extra configuration for that Segment.

Validate new VLAN Segment "VLAN-Web" is available on vCenter.From vCenter, under "Networking", validate "VLAN-Web" is under VDS-NSX.For this lab, see on top of the page for the VM IP addresses.



NSX-T EVAL GUIDE V2

NETWORKING | 28

3.1.2. Create 2 Web VMs in VLAN "VLAN-Web"

Create 2 Web VMs in VLAN "VLAN-Web"From vCenter, under "Host and Clusters", validate 2 Web VMs are well created and connected to "VLAN-Web"

Validate connectivity from external to those VMsFrom external client, validate ping communication to VMs is allowed,and validate SSH communication to VMs is also allowed.Note: I'm using ping + SSH, but you can use any protocol of your choice

root@lab3-jumphost:~# ping 10.16.1.11



NSX-T EVAL GUIDE V2

NETWORKING | 29

PING 10.16.1.11 (10.16.1.11) 56(84) bytes of data.

64 bytes from 10.16.1.11: icmp_seq=1 ttl=63 time=0.565 ms


^C

--- 10.16.1.11 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1022ms

rtt min/avg/max/mdev = 0.565/0.579/0.593/0.014 ms

root@lab3-jumphost:~# ssh [email protected]

The authenticity of host '10.16.1.11 (10.16.1.11)' can't be established.

ECDSA key fingerprint is SHA256:uncl2WyCuNSTwllyvR2He8JEKqZn0K2qdhYB06L+bKE.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '10.16.1.11' (ECDSA) to the list of known hosts.

[email protected]'s password:

Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64)

* Documentation: https://help.ubuntu.com

* Management: https://landscape.canonical.com

* Support: https://ubuntu.com/advantage

217 packages can be updated.

136 updates are security updates.

Last login: Mon Apr 6 16:58:28 2020

root@VLANWebeb-VM1:~#





^C




root@lab3-jumphost:~# ssh [email protected]

mailto:[email protected]


https://help.ubuntu.com

https://landscape.canonical.com

https://ubuntu.com/advantage


NSX-T EVAL GUIDE V2

NETWORKING | 30

The authenticity of host '10.16.1.12 (10.16.1.12)' can't be established.

ECDSA key fingerprint is SHA256:uncl2WyCuNSTwllyvR2He8JEKqZn0K2qdhYB06L+bKE.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '10.16.1.12' (ECDSA) to the list of known hosts.

[email protected]'s password:

Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64)

* Documentation: https://help.ubuntu.com

* Management: https://landscape.canonical.com

* Support: https://ubuntu.com/advantage

217 packages can be updated.

136 updates are security updates.

Last login: Mon Apr 6 16:59:23 2020

root@VLANWeb-VM2:~#

3.1.3. Configure Microsegmentation

3.1.3.1. Create NSX Group "VLAN Web VMs"

To simplify the configuration of micro-segmentation, NSX offers the ability to Group Workload into static or dynamic membership,such as VM name, tags, segment, etc.

Create NSX Group "Group VLAN Web VMs".From NSX-T, under "Inventory - Groups", click "Add Group". For this lab, we create dynamic Membership Criteria based onVM Name "starts with VLAN Web".


https://help.ubuntu.com

https://landscape.canonical.com

https://ubuntu.com/advantage

NSX-T EVAL GUIDE V2

NETWORKING | 31

Validate membership of NSX Group "Group VLAN Web VMs".From NSX-T, under "Inventory - Groups", click "View Members" of "Group VLAN Web VMs".

3.1.3.2. Create Micro-Segmentation (DFW)

Micro-segmentation is defined in "Categories" (Emergency, Infrastructure, Environment, Application), with security "Sections" +"Rules" in each. The security rules in the different sections will be pushed to the relevant VMs vNics based on the "Apply To"defined in the Section and/or Rule.

Create new DFW Section (= Policy).From NSX-T, under "Security - Distributed Firewall - Category Specific Rules", click "Add Policy".For this lab, let's create a Section name "Section-VLANWeb",and with an Applied To = "Group VLAN Web VMs".

NSX-T EVAL GUIDE V2

NETWORKING | 32

Create new DFW Rule.From NSX-T, under "Security - Distributed Firewall - Category Specific Rules", select section "Section-VLAN Web" and click"Add Rule".For this lab, let's create the following rules:

Name Sources Destinations Services Profiles Applied To Action

Internal Group VLANWeb VMs

Group VLAN WebVMs

HTTP +ICMP None DFW Allow

External Any Group VLAN WebVMs HTTP None DFW Allow

Default Any Group VLAN WebVMs Any None DFW Reject

NSX-T EVAL GUIDE V2

NETWORKING | 33

Publish DFW.From NSX-T, under "Security - Distributed Firewall - Category Specific Rules", click "Publish" (top-right).

3.1.4. Validate Micro-Segmentation

Validate connectivity from external to those VMs.From external client, validate HTTP communication to VMs is allowed,and validate ICMP communication to VMs is NOT allowed.Note: I'm using the web client "curl" to access the web page "/test.php", but you can use any web client.

root@lab3-jumphost:~# curl http://10.16.1.11/test.php

The Client IP@ is: 10.114.218.216<br>

The Server IP@ is: 10.16.1.11



From 10.16.1.11 icmp_seq=1 Destination Host Prohibited


^C


2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1013ms

root@lab3-jumphost:~# curl http://10.16.1.12/test.php



NSX-T EVAL GUIDE V2

NETWORKING | 34





^C


2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1001ms

Validate L2 connectivity between those VMs.From VLANWeb VM, validate HTTP + ICMP communication to VLANWeb VM is allowed,and validate SSH communication to VLAN Web VM is NOT allowed.

root@VLANWebeb-VM1:~# ping 10.16.1.12




^C




(reverse-i-search)`cu': ^Crl http://127.0.0.1/response_code.php

root@VLANWebeb-VM1:~# curl http://10.16.1.12/test.php



root@VLANWebeb-VM1:~# ssh 10.16.1.12

ssh: connect to host 10.16.1.12 port 22: Connection refused

3.2. Logical Network and SecurityIn this section, you'll configure Logical Networks for Tenants Green and Blue (Logical Routers = "Tier1" and Logical Switches ="Segments").Those Tenants Logical Networks will have access to the physical fabric via a Logical Router ("Tier0").Routing between the Tier0 and physical router will be done via "static routing" or "BGP".

Important Note: In this section, the internal Tenant routing (East/West) is done in "Logical Space" by NSX. The physical routerprovides the routing between the "logical space" and the "physical world" (North/South).

NSX-T EVAL GUIDE V2

NETWORKING | 35

Logical View

Physical View

The Network evaluation done in this chapter is focusing on NSX Switching and Routing capabilities. NSX-T offers more thanSwitching and Routing capabilities, such as NAT, Load Balancing, VPN.

The Security evaluation done in this chapter is focusing on NSX L4 Stateful North/South and East/West firewalling capabilities.NSX-T offers more than L4 Stateful firewall capabilities, such as Layer7 Firewalling, Intrusion Detection System (IDS), eco-system withSecurity Vendors like Checkpoint, Fortinet, or Palo Alto Networks. More informationon https://www.vmware.com/products/nsx.html and Create Tenants Logical Networks

Log on NSX-T Manager UI.In a browser: https://192.168.50.5/


https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/3.2.PhysicalView.jpg

https://www.vmware.com/products/nsx.html

https://192.168.50.5/

NSX-T EVAL GUIDE V2

NETWORKING | 36

Create new Logical Routers "T1-xxx".Under "Networking - Connectivity - Tier-1 Gateways", click "Add Tier-1 Gateway".For this lab, see on top of the page for the T1 name (T1-Tenant1, and T1-Tenant2).Configure the T1 Name.

Create new Overlay Segments "LSxxx".Under "Networking - Segments", click "Add Segment".For this lab, see on top of the page for the Segment name (LS1.1, LS1.2, and LS2.1).Select Connectivity = "T1-xxx" ("LS1.1 + LS1.2 on T1-Tenant1" and "LS2.1 on T1-Tenant2"),Transport Zone = "nsx-overlay-transportzone" (Default TZ for Overlay traffic),Subnets = 10.x.x.1/24"


NSX-T EVAL GUIDE V2

NETWORKING | 37

Validate new Overlay Segments "LSxxx" is available on vCenter.From vCenter, under "Networking", validate "LSxxx" is under VDS-NSX.

Create 2 Web VMs in each Overlay Segment "LSxxx".From vCenter, under "Host and Clusters", validate VMs are well created and connected to "LSxxx" For this lab, see on top ofthe page for the VM IP addresses.




NSX-T EVAL GUIDE V2

NETWORKING | 38

3.2.2. Configure North/South Communication (T0 / Physical Router)

3.2.2.1. Configure physical router + Create T0-Provider + Connect T1s to T0-Provider

Create new VLAN External + interface on physical router.For this lab, see on top of the page for the physical router interface + VLAN information.There is no steps described in this document, as it varies per physical router.Create VLAN Segment "External".Under "Networking - Segments", click "Add Segment".For this lab, see on top of the page for the VLAN number (3103).Select Transport Zone = "nsx-vlan-transportzone" (Default TZ for VLAN traffic),VLAN = "3103"

Create new Logical Routers "T0-Provider".Under "Networking - Connectivity - Tier-0 Gateways", click "Add Gateway Tier-0".For this lab, see on top of the page for the T0 settings.Select Edge Cluster = ""EdgeCluster1",and the following settings:Interface "20.20.20.2/24" on Segment "External" on Edge Node "EdgeNode1".

https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/3.2.2.1.step1.jpg

NSX-T EVAL GUIDE V2

NETWORKING | 39

Connect the different T1 to the Provider-T0.For each T1, under "Networking - Connectivity - Tier-1 Gateways", edit T1 and link it to "T0-Provider".




NSX-T EVAL GUIDE V2

NETWORKING | 40

Then configure "3.2.2.2. Static Routing." OR "3.2.2.3. Dynamic Routing."

3.2.2.2. Configure North/South Routing Static

Configure static route on physical router.Subnets "10.1.1.0/24" + "10.1.2.0/24" + "10.2.1.0/24" have a static route via "20.20.20.2". There is no steps described inthis document, as it varies per physical router.Just showing the routing table of the physical router

physical-router@lab3:~$ show ip route

Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,

I - ISIS, B - BGP, > - selected route, * - FIB route

S>* 10.1.1.0/24 [1/0] via 20.20.20.2, eth3

S>* 10.1.2.0/24 [1/0] via 20.20.20.2, eth3

S>* 10.2.1.0/24 [1/0] via 20.20.20.2, eth3

Configure static route on T0-Provider.Default gateway via "20.20.20.1".Under "Networking - Connectivity - Tier-0 Gateways", edit the "T0-Provider" and under "Routing - Static Routes", set a"Static Route".

And Configure the "Set Next Hops" = "20.20.20.1"

https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/3.2.2.2.LogicalView.jpg


NSX-T EVAL GUIDE V2

NETWORKING | 41

3.2.2.3. Configure North/South Routing Dynamic with BGP

Configure BGP on physical router.There is no steps described in this document, as it varies per physical router.Just showing the BGP configuration of the physical router

physical-router@lab3:~$ show configuration commands | grep bgp

set protocols bgp 2 neighbor 20.20.20.2 'default-originate' <-- Advertise itself for default gateway

set protocols bgp 2 neighbor 20.20.20.2 remote-as '1'

Configure BGP on T0-Provider.Under "Networking - Connectivity - Tier-0 Gateways", edit the "T0-Provider" and under "BGP", configure the "Local AS" ="1".


https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/3.2.2.3.LogicalView.jpg

NSX-T EVAL GUIDE V2

NETWORKING | 42

And configure the "BGP Neighbors" = "20.20.20.1", with "Remote AS number" = "2", and with "Source Addresses" = "20.20.20.1".

Configure T0-Provider "Route Distribution".Under "Networking - Connectivity - Tier-0 Gateways", edit the "T0-Provider" and under "Route Redistribution", addredistribution of T1 Subnets.

And configure the "T1 Connected Interfaces & Segments".




NSX-T EVAL GUIDE V2

NETWORKING | 43

Configure T1-xxx "Route Distribution".Under "Networking - Connectivity - Tier-1 Gateways", edit each "T1-xxx" and under "Route Advertisement", select "AllConnected Segments & Service Ports".

Validate learned BGP routes on physical router.

physical-router@lab3:~$ show ip bgp neighbors 20.20.20.2

BGP neighbor is 20.20.20.2, remote AS 1, local AS 2, external link

BGP version 4, remote router ID 20.20.20.2

BGP state = Established, up for 00:00:16

<snip>

physical-router@lab3:~$ show ip bgp neighbors 20.20.20.2 routes

BGP table version is 0, local router ID is 192.168.52.1

Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,

r RIB-failure, S Stale, R Removed



NSX-T EVAL GUIDE V2

NETWORKING | 44

Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path

*> 10.1.1.0/24 20.20.20.2 0 0 1 ?

*> 10.1.2.0/24 20.20.20.2 0 0 1 ?

*> 10.2.1.0/24 20.20.20.2 0 0 1 ?

Total number of prefixes 3

Validate BGP status of T0-Provider.Under "Networking - Connectivity - Tier-0 Gateways", expand "BGP", and click on "BGP Neighbors".And click on the "i" next to "Status" ("Connection State" should be "ESTABLISHED").

3.2.3. Validate Networking

Validate North/South connectivity from external to those VMs.From external client, validate communication to VMs





^C







NSX-T EVAL GUIDE V2

NETWORKING | 45






Validate East/West connectivity from VMs to VMs.From VM3, validate communication to VM4, VM5, and VM7.

root@LS1-1-VM3:~# ping 10.1.1.12




^C




root@LS1-1-VM3:~# ping 10.1.2.11




^C




root@LS1-1-VM3:~# ping 10.2.1.11




^C




3.2.4. Configure and Validate Security (Micro-Segmentation)

Follow the procedure detailed in to implement the following Micro-Segmentation:

NSX-T EVAL GUIDE V2

NETWORKING | 46

To simplify the configuration of micro-segmentation, NSX offers the ability to Group Workload into static or dynamic membership,such as VM name, tags, segment, etc.

Groups Members

Group-Tenant1-LS1.1 Segment LS1.1

Group-Tenant1-LS1.2 Segment LS1.2

Group-Tenant1 Group-Tenant1-LS1.1 + Group-Tenant1-LS1.2

Group-Tenant2 Segment LS2.1

Group-AllTenants Group-Tenant1 + Group-Tenant2

Micro-segmentation is defined in "Categories" (Emergency, Infrastructure, Environment, Application), with security "Sections" +"Rules" in each. The security rules in the different sections will be pushed to the relevant VMs vNics based on the "Apply To"defined in the Section and/or Rule.

https://github.com/vmware-nsx/eval-docs/blob/master/docs/assets/Graphics/3.2.4.LogicalView.jpg

NSX-T EVAL GUIDE V2

NETWORKING | 47

Section Rule-Name Sources Destinations Services Profiles AppliedTo Action

Tenant1

ApplyTo =Group-Tenant1

Internal-LS1.1Deny Group-Tenant1-LS1.1 Group-Tenant1-LS1.1 Any None DFW Reject

Internal-LS1.2Deny Group-Tenant1-LS1.2 Group-Tenant1-LS1.2 Any None DFW Reject

L3 East/WestAllow Group-Tenant1-LS1.1 Group-Tenant1-LS1.2 HTTP +

ICMP None DFW Allow

L3 East/WestDeny Group-Tenant1-LS1.1 Group-Tenant1-LS1.2 Any None DFW Reject

Tenant2

ApplyTo =Group-Tenant2

Internal allow Group-Tenant2 Group-Tenant2 Any None DFW Allow

Cross-Tenants

ApplyTo =Group-AllTenants

Cross-TenantsAllow1 Group-Tenant1 Group-Tenant2 HTTP None DFW Allow

Cross-TenantsAllow2 Group-Tenant2 Group-Tenant1 HTTP None DFW Allow

Cross-TenantsDeny1 Group-Tenant1 Group-Tenant2 Any None DFW Reject

Cross-TenantsDeny2 Group-Tenant2 Group-Tenant1 Any None DFW Reject

External

ApplyTo =Group-AllTenants

External Allow Any Group-AllTenants HTTP None DFW Allow

External Deny Any Group-AllTenants Any None DFW Reject

Here is a partial configuration view:

NSX-T EVAL GUIDE V2

NETWORKING | 48

3.3. Operation ToolsIn this section, you'll use 2 popular Operation tools which greatly facilitate Network and Security admins:

Network TopologyTraceflow

The Operation evaluation done in this chapter is focusing on those 2 tools.NSX-T offers more than those tools, such as Port Mirroring, IPFIX, Syslog, advanced status and statistics on its different services.

3.3.1. Network Topology

What has been created so far is the following logical topology:


NSX-T EVAL GUIDE V2

NETWORKING | 49

NSX offers a graphical representation of its network topology.


Display the NSX Network Topology.Under "Networking - Network Topology".


https://192.168.50.5/


NSX-T EVAL GUIDE V2

NETWORKING | 50

And specific Network elements, such as T0 information.

3.3.2. Traceflow

Traceflow allows you to inject a packet into the network and monitor its flow across the network.Traceflow allows you to identify the path a packet takes to reach its destination or, conversely, where a packet is dropped along



NSX-T EVAL GUIDE V2

NETWORKING | 51

the way.Each entity reports the packet handling on input and output, so you can determine whether issues occur when receiving a packetor when forwarding the packet.

Check the Traceflow from VM3 HTTP to VM7.

Under "Plan & Troubleshoot - Traceflow",select the Source "LS1.1-VM3",to Destination "LS2.1-VM7",Protocol Type "TCP" with Source Port = "5000" to Destination Port = "80".

And click "Trace".

You can follow the path through the different Logical NSX Routing + Security elements on the top half of the screen.


NSX-T EVAL GUIDE V2

NETWORKING | 52

You can also follow each step of the different NSX elements on the bottom half of the screen (and on which device it's running).

Note: Worth nothing even if that traffic is routed, it actually does not leave the ESXi1 (192.168.50.21) thanks to the power of NSXservice distribution :-)

Check the Traceflow from VM3 HTTP to VM1.

Under "Plan & Troubleshoot - Traceflow",select the Source "LS1.1-VM3",to Destination "VLANWeb-VM1",



NSX-T EVAL GUIDE V2

NETWORKING | 53

Protocol Type "TCP" with Source Port = "5000" to Destination Port = "80".

And click "Trace".

You can follow the path through the different Logical NSX Routing + Security elements on the top half of the screen.

You can also follow each step of the different NSX elements on the bottom half of the screen (and on which device it's running).



NSX-T EVAL GUIDE V2

NETWORKING | 54

Note: The traceflow tracks the different NSX elements up to it reaches the physical fabric and ends there


VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax650-427-5001 www.vmware.com

Copyright © 2019 VMware, Inc. All rights reserved. This product is protected by U.S. and internationalcopyright and intellectual property laws. VMware products are covered by one or more patents listedat http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc.in the United States and/or other jurisdictions. All other marks and names mentioned herein may betrademarks of their respective companies.

NSX-T Eval Guide v2...NSX-T EVAL GUIDE V2 NETWORKING | 28 3.1.2. Create 2 Web VMs in VLAN "VLAN-Web"...

Documents

Transcript of NSX-T Eval Guide v2...NSX-T EVAL GUIDE V2 NETWORKING | 28 3.1.2. Create 2 Web VMs in VLAN "VLAN-Web"...