abckdc Tracker

NSX Edge Node Deletion.

abckdc — Thu, 02 Nov 2023 09:59:06 GMT

HI All,

We recently faced a storage failure in one of our secondary sites, which resulted into NSX edge node being completely deleted (the edge VMs no longer exists). As a result we had to redploy the edge node and reconfigure the NSX on the hosts. For the task, we removed previously used T1, T0 and were trying to remove the failed Edge nodes but when we initiated the edge node deletion, it could not be deleted and the status is set to Deletion Failed.

We did try the KB https://kb.vmware.com/s/article/89283 but the api call does not do anything, the Failed Edge nodes still exists.

I will be very grateful for any suggestions.

NSX-T Version: 4.1.0.2.0.21761691

Thank You.

Re: Local Datastore Completly Utilized.

abckdc — Wed, 25 Oct 2023 08:39:16 GMT

I have attached the output

Thank You

Re: Local Datastore Completly Utilized.

abckdc — Tue, 17 Oct 2023 09:27:14 GMT

Hi,

Thanks for the response.

I did try with the "", but its not allowing me to get inside the datastore. The catch is there is no VM in that particular datastore.

Thank You.

Local Datastore Completly Utilized.

abckdc — Tue, 17 Oct 2023 06:30:50 GMT

Hi All,

I recently came across a client system where his local datastore is completely utilized. Since there was no space left in the local datastore it has now moved to an inaccessible state. I tried to access the local datastore via SSH as well but its not letting me in the datastore.

[root@esxi1:/vmfs/volumes] cd "DATASTORE-ESXi"
-sh: cd: can't cd to DATASTORE-ESXi: No such file or directory

Is there any way possible to access or format the local datastore or the only option is the reinstall the ESXi.

I will be very grateful for any suggestions.

Version: 7.0 Update 2

Thank You.

LACP with iSCSI.

abckdc — Tue, 29 Aug 2023 09:25:13 GMT

Hi All,

We are currently using VDS with LACP in our environment. We are currently in need of attaching the iSCSI-based storage in our hosts. I am aware that iSCSI with LACP is a no-go in every case and we will be unable to use MPIO. But we cannot break our LACP configuration on the host ( other software products are bound to call LACP port groups) and there are no other physical port remaining. Has anybody attached iSCSI storage with LACP-enabled VDS?

What are things that need to be considered if am I to go with LACP iSCSI.

Thanks

NSX-T network stops working.

abckdc — Wed, 09 Aug 2023 09:02:04 GMT

Hi All,

I am new to NSX world and just looking for any kind of suggestions for the issue.

We are currently trying to migrate our NSX cluster to new nodes (replacing the old hosts). There are two NSX-T edge VM and three NSX-T managers configured. For the migration we are creating a new cluster and adding the new nodes to the cluster. OLD nodes are in Cluster A while new nodes are added in Cluster B. After the nodes are added to the cluster B, the new nodes were attached to the same VDS that was being used in the old nodes. The new host has been successfully configured from the VDS, MTU, and underlay switches perspective.

The nodes were then host prepared and added to NSX-T. Everything until here is working optimal. The NSX-T segments are now available in the new nodes as well and operating successfully (Tested on a newly created VM).

Once verifying everthing is working fine we then started vMotion of NSX-T manager to the new cluster, no problem, all nodes were sucessfully migrated. Then we started vMotion of our NSX-T edge nodes, that when the problems start, once we migrate NSX-T Edge VMs the NSX-T segments stops being reachable from outside network. But if I go into a certain VM under the segment everything is reachable.

Everything works fine if we leave the NSX-T edge nodes on the Cluster A and migrate all VMs connected to NSX-T Segment to Cluster B. The issue arises only when we migrate NSX-T Edge VMs.

At first we thought that there might be issue in the underlay network, VLAN and MTU set on the physical switches that is being used for NSX-T Edge connectivity to physical network. But everything is fine on the physical side, all required VLANS are passed with MTU being set to 9000.

On the NSX-T side there is no any error after we migrate the Edge VM. All tunnels are up, all connectivity is working, BGP peer with upper bound router is also working. No any errors are displayed on NSX-T manager UI.

NOTE: Once EDGE VMs were migrated we did face alarm being raised due to "Display Name" and "Compute Id" being mismatch. It was resolved once we redployed the NSX-T Edge VMs

We did thought that issue might be with the mac adress not being updated on the switch side, we also tried to flush mac address on switch as well as arp on routers.

Once we vMotion the EDGE VM to old cluster everything starts working.

NSX-T Version: 4.1.0.2.0.21761691

We are currently out of ideas on what might be causing the issue. I will be very grateful for any suggestions.

Re: Edge Node mismatch.

abckdc — Wed, 09 Aug 2023 07:36:41 GMT

Thanks @EvertAM for the response. We did had to redeploy the Edge nodes.

Edge Node mismatch.

abckdc — Tue, 01 Aug 2023 13:31:13 GMT

Hi all,

We are currenlty migrating our NSX to our new cluster from the old cluster. We have successfully migrated NSX Manager and Edge Nodes but after migrating edge node we are seeing an alarm being raised due to "Display Name" and "Compute Id" being mismatch as in KB

https://kb.vmware.com/s/article/93464

but we did try to resolve the issue with "vSphere/Edge Appliance" as a Source in Resolve option. But it gets back to the same error after some time, as mentioned in KB https://kb.vmware.com/s/article/92213

The KB then mentioned selecting NSX as the source to resolve the issue but we have a dilemma if this will redeploy our edge nodes as the message is mentioned while selecting NSX as the source that it may redeploy the edge VM.

We do not want to bear any downtime currently so, will selecting NSX as source to resolve the issue redoply the edge VM.

Thank You.

NSX-T host replace.

abckdc — Wed, 05 Jul 2023 05:27:47 GMT

Hi All,

We are currently running NSX-T in our 2 Host clusters for Production. The host has now reached EOL and we are replacing the host with a new host with higher compute power. So, now we will need to migrate our current NSX-T scenario to be on to be replaced the new Host. What will be the correct pathway to replace the existing host with a new one keeping the NSX-T configuration intact and with minimal downtime?

The only thing coming into my mind is adding a new host to the same cluster ( enable EVC) and configure NSX-T on the new host ( but what about licensing) keeping all the configurations the same and migrating the VMs to the new host? Once all VMs are migrated depreciate the host from NSX and VMware cluster.

I will be very much grateful for any suggestions.

Re: vSphere Replication RPO

abckdc — Tue, 13 Sep 2022 10:21:53 GMT

Hello,

Thank you very much for the detail information.

Thank You Agian.

Re: vSphere Replication RPO

abckdc — Tue, 13 Sep 2022 03:30:44 GMT

Hi,

Thank you very much for the response. So, this means that sync can occur regardless of the mentioned RPO time, only requiremnet being that it must always meet the set RPO time. "The next synchronization can start no later than 12:10." Can you please elaborate more in the mentioned statement. Do you mean 12:15 or 12:10. If the sync can occur after 12:10 does this mean that even though we have set the RPO to 15 min, multiple sync can occur during that 15 min time frame i.e. from 12:00 to 12:15.

Thank You again for the response.

vSphere Replication Point in time Recovey

abckdc — Mon, 12 Sep 2022 10:18:01 GMT

Hi All,

I am testing vSphere Replication in our test environment for production usage. I have enabled the Point in Time Recovery option while initiating the Replication. I have set the RPO to be at 5 min. I have set the retention policy to 3 instances per day for 5 days (just for testing purpose). Is there any relation between Point in time recovery and RPO. Does vSphere repliction mainatain snapshot on random time interval or based on the RPO i.e. every 5 minutes. In my test environment I have observed that the 3 recovery instances are on random time i.e. first instace is on 1:00PM, another on 6:00 PM and another on 11:00 PM. But as per my understanding it should have maintained instances on every 5 minutes i.e. 12:00 PM, 12:05 PM and 12:10 PM and so on. with new arrivial of data at 12:20 PM the first instance of 12:00 is removed and so on.

I am very sorry for the bad explantion. I will be very pleased for any response.

Thank You.

vSphere Replication RPO

abckdc — Mon, 12 Sep 2022 08:46:40 GMT

Hello All,

I am new to vSphere Replication. I have just configured vSphere Replication in my test lab and its working great. I have studied some documentation regarding vSphere Replication RPO and its confusing me. Lets say I am replicating a VM with 5 minutes RPO. Does this mean that it will sync on every 5 minutes or the sync can occur any time within the timeframe ( requirement being changes can not be older than 5 minutes). If a VM starts replication at 12:00 then will the VM resync at every 5 minutes being 12:05, 12:10 etc. or the resync can happen at any time. If it took only a minute to sync data between the sites lets say 12:01 will it wait for the RPO time to pass i.e. 12:05 to resync the data or it can resync the data again at 12:03 or 12:04.

I will be very grateful for any response.

Thank You.

Port Group is not working.

abckdc — Tue, 16 Aug 2022 13:36:30 GMT

Hello All,

We have configured a virtual distributed switch with LACP and everything was working fine. But now we had a new requirement to add new Port Group. We did add a new port group to the VDS as well as on the Switch side(LACP) config. But the port group is not reachable.

It's port group is working on the same host. Tested with 2 VM on the same host with same port group. But when I migrate one VM to another host and test connection between the VM's its not reachable. Verified all config on the switch side its fine as all the previously created port group are working. The VLANs and LACP config on the switch side are correct. Can anybody suggest me the troubleshooting steps on the VMware LACP side.

Thank You.

ESXCLI change the lacp mode to active.

abckdc — Tue, 16 Aug 2022 12:02:02 GMT

Hello All,

There has been some misconfiguration in our VDS and the LACP mode was set to passive. We currently do not hold access to the upper level switch and all the LACP is currently down meaning all the host is down. Can anybody suggest me to bring back the lacp mode to active via backend cli in ESXi host. I will be very much grateful for any suggestion.

Thank You.

Re: vSan 3 node consideration.

abckdc — Wed, 09 Mar 2022 05:05:51 GMT

Thanks @Tibmeister and @TheBobkin for the detailed clarification. I am very grateful for the response. I now have better understanding for the cluster.

Thanks Again.

vSan 3 node consideration.

abckdc — Mon, 07 Mar 2022 06:31:40 GMT

Hello All,

We are considering on setting up 3 node vsan cluster. Each host have 1 TB * 10 Disk= 10 DISK. We are considering to have 2 disk group of 4 capicity disk and 2 disk as cache on each node. We are considering using FTT policy of 1 with RAID 1 setup. My question is regarding the disk usage. As one host is used as witness node, will the diskgroup of the witness node be used to store data other than meta data of RAID 1 setup. Will I be able to use all the diskgroups of all three hosts or only 2 host(RAID 1) and 3rd host for witness. If so then I do not see a point in populating my 3rd host with 10 TB disks to just hold meta data. OR will the data be distributed among the disk groups of all 3 hosts so that all my disk gets utilized and will this increase my usable capacity slightly rather than 2 node usage.

Also, if 1 node fails then will I be able to repopulate a new node in the same cluster and will the RAID start rebuilding.

Sorry if my query has been answered already, I have not been able to find the exact answer to my query.

Thank You.

Re: vSAN with 3 node

abckdc — Mon, 02 Aug 2021 03:49:48 GMT

Thank you very much for the reply. So, I can proceed to two node cluster with ftt=1 and set witness appliance on the third host. This third host without storage can reside in the same cluster right or do I have to put it somewhere else (under same vcenter)? If yes can I start machine on this third host(witness) with datastore being vsan. Also, If I need to migrate machine from host 1 to host 3(running witness machine) will it be possible?

vSAN with 3 node

abckdc — Sun, 01 Aug 2021 07:58:03 GMT

Hello EveyOne,

I am running vSphere 7 in my test environment and I am working with 3 host (new to the environment). I am looking towards deploying vSAN in my enviromnment where two host have local storage of 21 TB each but the third host doesn't have local storage except running esxi disk. I will be very grateful if anyone can guide me to which cluster method shall I proceed to. 2 node cluster or 3 node cluster? Does the disk requirement on all the hosts needs to be same.

I will be very grateful for any suggestion.

Thank You

Re: vCenter, ESXi VM's total bandwidth consumption.

abckdc — Mon, 08 Feb 2021 12:28:52 GMT

Hello Sir,

I am just trying to find if there is any possible way by which we can calculate a total data consumption of a VM in the past month and so on. I was working on Libre NMS and found that they have a feature called Billing module. It tracks the ports usage and shows you the total usage over time period. It gets this data via SNMP from the devices also esxi, vcenter but we can only track total usage based on host level(i.e total consumption of esxi machine over the time period) not on individual VM level. So, I was wondering if any other software or tools can achieve this. I don't want to enable SNMP on all VM's and add all of them to monitoring server. I just want to achieve this via host machine(esxi, vcenter).

https://docs.librenms.org/Extensions/Billing-Module/

I was wondering if its possible to do so on vCenter or Esxi host level by tracking port assigned to VM's.

Sorry for the bad explanation.