zeebahi Tracker

Mutiple t0 t1 on esxi transport node and vtep

zeebahi — Fri, 27 Oct 2023 08:28:26 GMT

Hi everyone,

Let say we have single converge vds with single vtep.

We create two separate t0 and t1 routers:

T0-a, t1-a

T0-b, t1-b

Can we do that ? Or do we need two converge vds with their vteps , one vds for t0-a,t1-a, and other vds for t0-b,t1-b?

Much appreciated!!

Can we control Edge VM active selection?

zeebahi — Tue, 26 Sep 2023 14:14:55 GMT

Hi everyone,

I am wondering if we can control which edge VM assumes stand-by role and which edge VM assumes Active role in Active stand by case?

Much appreciated!!

Single Tier T0 Routing question

zeebahi — Mon, 01 Aug 2022 02:34:51 GMT

Hi everyone,

Consider the following example:

We have two transport hosts with over lay segments SEG-A, SEG-B . ESX1 and ESXI2 ,SEG-A: 172.172.172.0/24 and SEG-B 173.173.173.0/24 have been attached to T0 DR routers. To DR1 has two LIF-A: 172.172.172.1/24 and LIF-B: 173.173.1/24

VM-A on ESXI1, is attached to SEG-A ( 172.172.172.10), VM-B on ESXI2, is attached to SEG-B ( 173.173.173.10)

VM-A pings VM-2. 1723.173.173.10.which is received by T0 DR on ESXI1. T0 DR on ESXI1 performs routing look up against 173.173.173.10, and finds it is reachable via directly connected LIF-B.

Next T0DR on ESXI1 needs to find VM-2 MAC address before traffic can be forwarded.

1) Will T0 DR look up VM-B MAC in LIF-A's arp table? Or Will T0 DR look up VM-B MAC in arp table associated with logical switch of SEG-B?

Additional info:

I find conflicting info :

This VM's blog suggest ToDR performs MAC look up in logical switch's arp table:

https://blogs.vmware.com/networkvirtualization/2017/09/nsx-t-routing-where-you-need-it.html/

Distributed Routing for VMs hosted on the different Hypervisors (ESXi & KVM):

Destination MAC, i.e. MAC address of DB VM1 is needed to forward the frame. An ARP entry exists for DB VM1. MAC address of DB VM1 is learnt via remote TEP 192.168.150.152. Again, this MAC/TEP association table was published by NSX Controller to the hosts.

NSX-T guide on the other hand says,

https://nsx.techzone.vmware.com/resource/nsx-t-reference-design-guide-3-0#_Toc59008623

Page 51:

The routing lookup happens on the HV1 DR, which determines that the destination
subnet 172.16.20.0/24 is a directly connected subnet on “LIF2”. A lookup is performed in
the “LIF2” ARP table to determine the MAC address associated with the IP address for
“App2”. This destination MAC, “MAC2”, is learned via the remote HV2 TEP
20.20.20.20.

Thanks !!!

Layer 2 Bridging between two Host transport nodes question

zeebahi — Sat, 19 Jun 2021 02:48:28 GMT

Hi everybody,

Please consider following scenarios:

Scenario#1

VM1-10.10.10.10-ESXI1 TEP 1.1.1.1---WAN---2.2.2.2 ESXI2-VM2 10.10.10.20

Both ESXI are running 7.0.1, controlled by V center 7.0.1, and NSX manger 3.1.

Both ESXI hosts are tied to TZ-overlay zone, which in turn tied to NSX overlay segment Overlay-seg10, Both VMS on ESXI are using Overlay-seg10. VM1 can ping VM2.

In above scenario, ESXI hosts are using TEP IP to perform bridging for VM1 and VM2? If corrert, we do not need any Edge VM to provide bridging between two VMS if they are using same Overlay segment?

Convesly speaking, if VM1 is using Overlay-seg10, and VM2 is using distributed port group V10, only then do we need Edge VM for bridging traffic between VM1 and VM2?

Thanks and have a good weekend!!

Re: Host route and NSX-T

zeebahi — Sat, 19 Jun 2021 02:35:51 GMT

No problem!!

Appreciated!!

Re: Host route and NSX-T

zeebahi — Sun, 13 Jun 2021 18:20:30 GMT

Thanks Sreec!!

As you mentioned in both Multisite and Federation solutions , T0/T1 routers do not learn host route

Does VXLAN solution from VMWare can do headend ingress replication for bum traffic without requiring multicast functionality in underlay?

Because this video from Vmware at 0:56 mentions Multicast underlay being the requirement:

https://www.youtube.com/watch?v=MUFheGbIIws

Screenshot of the video:

Host route and NSX-T

zeebahi — Sat, 12 Jun 2021 16:20:56 GMT

Hi everybody,

I am new to NSX-T, but have experience with VXLAN-BGPEVPN.

In VXLAN BGPEVPN, VTEP can learn host routes ( /32) by snopping on ARP, DHCP messages from attached hosts.

Now my question, I will illustrate as below:

Case:T0 Only

We have two ESXi : ESXA and ESXB, both these ESXI are at two different data centers DC1 and DC2 joined by layer 3 WAN CKT:

DC1---1.1.1.1--WAN----2.2.2.2-DC2

ESXIA ESXB

1) Over lay segment SEG-APP :(10.10.10.0/24) has been created and attached to Over lay transport TZ1 which is then attached to both ESXI hosts.

2) VMSERVER 10.10.10.10 is on ESXIA.

2) Edge node VM1 is on ESXI1 A and Edge node VM2 is on ESXB. Only TO routers have been created, no T1 router is configured.

3) T0 routers are attached to TZ1 and also conncted to VLAN backed transport zone for external communication with non NSX network.

Considerig the above, can T0 rouer on Edge1VM( Which is on ESXIA) learn 10.10.10.10/32 host route for attached VMSERVER1 by snooping on ARP, DHCP etc?

CASE: T1 and T0

Just like case1 but we are using T1 routers in addition to T0.

We have two ESXi : ESXA and ESXB, both these ESXI are at two different data centers DC1 and DC2 joined by layer 3 WAN CKT:

DC1---1.1.1.1--WAN----2.2.2.2-DC2

ESXIA ESXB

1) Over lay segment SEG-APP :(10.10.10.0/24) has been created and attached to Over lay transport TZ1 which is then attached to both ESXI hosts.

2) VMSERVER 10.10.10.10 is on ESXIA.

2) Edge node VM1 is on ESXI1 A and Edge node VM2 is on ESXB. T1/T0 routers have been created.

3) T1 routers are attached to TZ1 , T1 routers are also connected to T0, T0 routers are connected to non NSX's network using VLAN-back segment.

Considerig the above, can T1 rouer on Edge1VM( Which is on ESXIA) learn 10.10.10.10/32 host route for attached VMSERVER1 by snooping on ARP, DHCP etc?

Thanks and have a good weekend!!

HCX and SRM

zeebahi — Sat, 08 May 2021 17:15:03 GMT

Hi everyone,

I am new to VM's technologies so have very basic questions:

I am exploring HCX's DR feature versus SRM.

1)Given both, which one is simpler and better, only focusing on DR feature.

2)Does HCX's DR feature require NX-T/NX-V environment as prerequisite ? Again only focusing DR feature of HCX.

3) Does HCX's L2 extension service require NX-V/NX-T be set up first?

Thanks and have a good weekend!!

Re: NIC Teaming: Standby NIC

zeebahi — Fri, 12 Mar 2021 18:01:31 GMT

Thanks for your response!!

But I see different behavior:

Test set up:

ESXI 6.5

VMNIC2 is active, VMNIC 3 is stand by.

VMNIC2--------gig0/13 Physical SW
VMNIC3--------gig0/14

Physiacl sw set up:
int gig 0/14
switchport mode trunk
switch trunk encapsulation dot1q
switch trunk allowed vlan 24
int vlan 24
ip address 24.24.24.1/24

Ubuntu wire shark machine:
24.24.24.24.24
Ping issued to 24.24.24.24 from physical SW, is send out of gig 0/14, connected standby port VMNIC3.
Ubuntu does see arp packet from physical switch

So we do see traffic received on standby uplink is forwarded to attached VM. Is this expected behavior ?

NIC Teaming: Standby NIC

zeebahi — Wed, 10 Mar 2021 02:32:42 GMT

Hi everyone.

Please consider following scenario:

VM----PG-A---vSW---vmnic1-------f1-Physical SW

|-----vmic2------f2

PG A has following NIC teaming policy:

vmnic1 active

vmnic2 standby.

Let say physical SW transmits a ARP for VM's IP on f2. What will VSW do next? Will it discard this ARP because it is received on standby vmnic2? Or will it transmit it to VM ?

Thanks and have a good day!!

Vcenter managed ESXI host and SOAP API's purpose

zeebahi — Fri, 05 Mar 2021 15:04:49 GMT

Hi everybody,

I am wondering if Vcenter uses ESXI's SOAP API to manage ESXI. What are some management activities for which Vcenter uses ESXI's SOAP API to manage it. I did not find enough info about it on google.

Thanks and have a nice day!!

Acceptable logical CPU oversubscription and vCPU ready time

zeebahi — Thu, 11 Feb 2021 01:47:36 GMT

Hi guys,

1) Not an expert, but my understanding is ideally we should avoid oversubscription of logical CPU on ESXI host, but if we must do oversubscription of logical CPU, is there any maximum limit say 3:1 , where 3 is vCPU and 1 is logical CPU on the host?

2) What is max acceptable ready time for vcpu?

Google search shows following:

https://www.ibm.com/support/pages/virtual-machine-cpu-ready#:~:text=It%20is%20normal%20for%20a,VMs%20with%20fewer%20vCPUs%20configured.

It is normal for a VM to average between 0–50 ms of CPU ready time; anything over 1000 ms is considered to lead to VM performance problems

Are we saying:

1) 0-50msec ( acceptable)

2) Anything between 50msec-1000msec is abnormal, but it should not impact performance

3) Anything above 1000msec, performance issue.

Thanks and have a good day!!

Re: SRM basic question.

zeebahi — Fri, 29 Jan 2021 05:40:04 GMT

Much appreciated!!!

Re: SRM basic question.

zeebahi — Fri, 29 Jan 2021 04:34:55 GMT

Appreciated!!

Just another question popped in my mind:

VM1 , VM2 both needs to be protected via SRM, both VMS have requirement to run together at one location at a time.

So if VM1 goes down, VM2 must also be powered down or vice versa, this will allow DR site to have recovered VM1 and VM2.

Can we do that with SRM?

Re: SRM basic question.

zeebahi — Fri, 29 Jan 2021 03:52:22 GMT

Thanks Ashilkrishnan !!

SRM basic question.

zeebahi — Fri, 29 Jan 2021 01:07:38 GMT

Hi everybody,

I am starting to learn VM's stuff so bear with me.

VM1 vNIC 1.1.1.1 Site A Active site

VM1 VNIC x.x.x.x Site B DR site.

Above, we have VM1 at site A , we are using SRM to copy VM1's states from site A to DR site B, VM1 at site B represents replicated VM1 at Site A. The goal is to bring VM1 up at Site B using SRM if VM1 at Site A goes down.

Does VM1 vNIC at site B should have the same 1.1.1.1 or it can have any IP associated with Site B say 2.2.2.2?

Thanks and have a day!!

NFS versus ISCSI for VM storage

zeebahi — Thu, 21 Jan 2021 19:48:21 GMT

Hi everyone,

We can store VM files in a centralized storage so we can do Vmotion, HA etc, being new to VMs, I am trying to understand why one should choose one over the other. So far, I have seen by using NFS, we can avoid dealing with LUNS on storage site.

Thanks and have a good day!!

Re: vSAN across WAN

zeebahi — Wed, 09 Dec 2020 01:25:25 GMT

Thanks !!!

I just found out:

Network latency

Maximum of 1 ms RTT for standard (non-stretched) vSAN clusters between all hosts in the cluster
Maximum of 5 ms RTT between the two main sites for stretched clusters
Maximum of 200 ms RTT from a main site to the vSAN witness host

Maximum network delay for ESXI host and NAS.

zeebahi — Wed, 09 Dec 2020 01:18:49 GMT

Hi everybody,

Is there any upper limit imposed by VM ware for Network delay between ESXI host and NAS?

I am wondering if anyone of you has deployed NAS at one geographical location while ESXI hosts( which are using NAS) are located at other geographical locations with round trip delay of 230msec? If yes, any issue?

Thanks and have a good night!!

vSAN across WAN

zeebahi — Wed, 09 Dec 2020 01:11:51 GMT

Hi everybody,

I am trying to find if there is any maximum network latency limit for vSAN.

We have to sites in two different continents, the round trip time between the two is 230msec. We are wondering if we can still do vSAN with cluster stretched between these two locations.

Thanks and have a good night!!