Basic terms Flashcards

1
Q

Compare NSX-T with NSX-V

A

NSX-T
decoupled from VCenter
Supports : ESXI, KVM, Bare Metal, Kubernetes, AWS and Azure
supports containers
Standalone Solution
can point to VCenter in order to register hosts
NSX manager and controller are on the same appliance
Uses GENEVE for encapsulation

NSX-V 
VCenter based 
has NSX manager registered with VCenter 
Separate appliances for NSX manager and NSX Controller
Uses vSphere distributed switch
Uses VXLAN for encapsulation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

NSX Management
Control Plane
Data Plane

A

Management Plane
Three Nodes cluster of three virtual appliances
user interface
desired configuration to device

Control Plane
provided by the same NSX management cluster
dynamic state of logical routing, distributed firewall
it learns topology information and pushes it down to data plane

Date Plane 
VMs 
Containers 
NSX Edge Nodes 
NSX Transport Nodes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

NSX Manager Roles

A

Policy
Manager
Controller

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

NSX Manager Cluster VIP

A

Each of the nodes in the management cluster has a dedicated IP but they are managed by a VIP that points to one Node at a time (Leader Node)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

NSX Manager Database

A

A distributed shared database to ensure all information is synchronized between all devices in the cluster. Replicated and distributed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

NSX Controller Functions

A

Logical Switching
Logical Routing
Distributed Firewall
CCP and LCP

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

CCP and LCP

A

CCP
Central control plane that exists on the NSX manager and pushes information to the local control plane that exists on nodes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

NSX Controller Plane Shrading

A

Each Transport Node is controlled by one NSX Controller in the NSX Management cluster.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Preparing Transport Nodes for NSX-T - Data Plane

A

On
Hypervisors
Bare Metal Servers

Transport Zone
NVDS
TEPS
VIBs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

MPA

A

Management Plane Agent
retrieves status of distributed firewall
retrieves statistics from Host

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

NSX-T Segment

A
Similar to VLAN 
Identifies a layer 2 segment 
Spans multiple transport nodes 
Like a distributed port group on vSphere 
Identified by a VNI
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Distributed Router

A

Used to route traffic between multiple segments
Spans multiple Transport Nodes
Exists on Edge Nodes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Distributed Firewall

A

Applies firewall rules directly on the VM Level

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

ARP Request without NSX

ARP Request with NSX

A

Without NSX you can’t have a layer 2 network that spans a layer 3 network. A router will drop the ARP broadcast.

NSX allows layer 2 extension by using the concept of overlay and underlay.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

GENEVE and TEP

A

VMkernel port
payload - IP -MAC - VNI - IP - MAC
VNI used to identify the segment that is dropping the frame into the correct Segment aka Correct Logical Switch

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Transport Zones

A

Identifies the scope of an NSX network
A collection of transport nodes that are connected by the GENEVE overlay

When created an N-VDS will be created
Two types:
Overlay transport zone 
 each transport node can be a member of one 
 the overlay part of the network

VLAN transport zone
used with endpoints we connect directly to vlan backed distributed group
supports 802.1q

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

NSX Uplink Profile

A

Has the settings for :
Teaming method
MTU
And more

18
Q

VTEP IP Pool

A

Needed to allocate IP addresses for Nodes in the Fabric

19
Q

VLAN Transport Zone

A

We can create Segments inside it
each Segment is associated with a specific VLAN
Backed port groups are being created on the ESXi Hosts
edge Nodes will connect to these Nodes

20
Q

Transport Node Profile

A

collection of settings applied to host transport Node
transport zone
uplink profile
TEP Pool

21
Q

Transport VLAN in Uplink Profile

A

The underlay VLAN connection

22
Q

Logical Switching

A

Provided by the N-VDS Switch

23
Q

NSX Controller Tables

A

MAC Table -> MAC to TEP mapping
ARP Table -> IP to MAC mapping
TEP table -> VNI to TEP to MAC mapping

24
Q

MAC Table

A

Which VTEP each mac is reachable through
After a VM is detected a MAC report is sent to the NSX controller
Distributed across all Nodes in that VNI

25
Q

ARP Table

A

ARP regular table
When an ip to mac is detected on a VM an IP report is sent to the NSX controller
Replicated across all nodes in a specific VNI
Used to suppress ARP broadcasts Locally

26
Q

VTEP Table

A

Tracks all TEPs participating in a VNI
Important for layer 2 broadcast in a VNI
Distributed to all hosts in that VNI

27
Q

Command to display tables

A

get logical-switch [uuid] mac-table
get logical-switch [uuid] arp-table
get logical-switch [uuid] vtep

28
Q

BUM

A

Broadcast
Unknown Multicast
Multicast

29
Q

BUM handling

A

Flooded inside the VNI using the VTEP table

30
Q

Routing without NSX

A

Traffic should be sent across a trunk outside ESXI and then sent back on the correct VLAN. Same as classic intervlan routing

31
Q

East West Routing with NSX-T DR

A

Kernel Module that runs on each host
Distributed to Hosts
IPv6 Support
Has a leg in each segment it is active on
Uses VTEP to Route packets to different hosts

32
Q

Single Tier Routing

A

Each Transport Node has a T0 DR
T0 DRs are connected across a Transit Overlay Link
Edge Node has a T0 DR and a Service Router (SR ) that has two connection one to Transit network and one to External network
Edge node has its own TEP too

33
Q

Services Router

A
Handles N-S routing 
NAT 
DHCP
Load Balancing 
Gateway Firewall 
VPN
Bridging 
Connects to an outside work via an external segment 
Transit link connect DR routers with SR router
34
Q

North South Packet Walk with T0 Architecture

A

Packet sent from VM to DR gateway
DR routes packet via default Route to SR [VTEP]
SR Routes packet outside via the external network

35
Q

NSX Multi Tier Routing Use Cases

A

Multi Tenant Support
Logical Separation between Provider Router and Tenant Router
Top tier is T0 gateway
Bottom tier is T1 gateway
Tenant has complete control of Tier-1 Gateway

36
Q

Multi Tier Routing Connections

A

Service Interface : from T0 GW to VLAN segment
Router Link Interface : from T1 GW to T0 GW
T0 can also connect to segments overlay

37
Q

Two Tier Routing on Same host

A

VM1 to T1 DR
T1 DR T1 to T0 GW
T0 GW to T2 DR

38
Q

Two Tier Routing on Different hosts

A

VM1 to T1 DR [inside host]
T1 DR T1 to T0 GW [inside host ]
T0 GW to T2 DR [TEP overlay]

39
Q

Two Tier Routing External

A

VM1 -> Tenant 1 T1 DR
Tenant 1 T1 DR -> T0 GW DR
T0 GW DR -> T0 SR

40
Q

SR High Availability Active Standby

A
All Traffic Flows through a single SR 
Required for Stateful Services 
Supported on T0 and T1 
one edge node is preferred 
Multiple GWs can run on each node
41
Q

NSX-T edge Nodes

A
run network services that can't be distributed 
north South connectivity 
Centralized Services:
 DHCP
NAT 
VPN 
LB
l2 bridging 
Service interface 
Gateway FW
42
Q

VLAN Segments

A

a layer 2 broadcast domain implemented as a traditional VLAN in the physical infrastructure.
this requires traffic between two VMS on two different transport nodes but attached to same VLAN backed segment gets carried over the same VLAN on physical network