please could you explain with more detail how could i acces the ESXi sw for managing the virtual machines.
i understood that i need to power off the machine and in that moment i could login as a root.
Another question since you mention the version 6.7 is the one that presents problems, do you think will better maybe with a lower version.
I really appreciate all the help you can provide me so i can continue the vm course i am taking.
Thanks in advance,
Manuel
Hi vXav,
I also tried with the keybord binding, but this not work.
Thanks,
Manuel
This isn't happening in Workstation 15.1 (for me, at least), so it may be Player-specific.
Hi,
Could you please instruct how to handle certain SRM operation e.g.
- If the option SYNCDATA option $true fails to synchronize the VM, SRM Recovery Failover operation should fail and revert back VM to original state, should not perform unplanned failover
Please advise...
This may be due to the fact that the template is in the content library. To test, either move it out of the CL or use the source template which is just a regular vSphere template. Apply the cust. spec. to the non-CL template and see if it works.
Doesn't have anything to do with ESXi. The IP you provide the guest OS is connected to a virtual machine port group. There are no firewall rules applied to VM port group traffic, so the issue is either localized to your guest OS (a config issue) or upstream in your physical network somewhere.
Hi, IMHO the issue is related to the following from the KB you posted:
A Datastore on a LUN detected as a snapshot cannot be grown
Now why it detects it as a snapshot volume is unknown but likely a matter of opening a case with VMWare but I'm pretty sure it has to do with:
Device naa.600508b100104c395657453248550006:3 detected to be a snapshot
If you're running the free ESXi consider purchasing the essentials kit, it's very cheap and it will allow you do open a pay-per-incident case with support.
~B
I've gone through many VCSA issues in the past and my conclusion at this point based on my own observations and experiences is that the only predictable outcome with messing with VCSA is to scrap it and start from clean install. I've had cases where the integrated VCSA updater would render an appliance useless, not booting or booting but not functioning correctly. Literally a GUI "update" could do that. So in summary yah it is a hassle but the alternative is a support case that may or may not lead anywhere.
So in a way one can achieve limitless ESXi hosts (properly licensed under essentials of course) but they will have to be managed separately 3 at a time and each threesome will be managed by its own VCSA, from a management stand point far from ideal but in terms of compute power the license can scale, I read more around specifically VMW prohibiting this kind of setup and I couldn't find anything that explicitly says one can't use essentials license in such a way. The management piece, of course is the downfall of such deployment
$DateStart = (Get-Date).AddDays(-1)
$TaskNumber = 1000 #1000 max how to fix this?
$TaskMgr = Get-view TaskManager
$tFilter = New-Object VMware.Vim.TaskFilterSpec
$tFilter.Time = New-Object VMware.Vim.TaskFilterSpecByTime
$tFilter.Time.beginTime = $DateStart
$tFilter.Time.timeType = "startedTime"
$tCollector = Get-View ($taskMgr.CreateCollectorForTasks($tFilter))
$dummy = $tCollector.RewindCollector
$Tasks = $tCollector.ReadNextTasks($TaskNumber)
foreach ($Task in $Tasks)
{
$TaskName = $Task.Name
$TaskName
}
If I make $TaskNumber =1001 or greater, I get the following error
Exception calling "ReadNextTasks" with "1" argument(s): "A specified parameter was not correct: maxCount"
At C:\scripts\Powershell\VMware\vCenter\GetSnapshotTasks.ps1:120 char:1
+ $Tasks = $tCollector.ReadNextTasks($TaskNumber)
We have a vSphere cluster consisting of two identical servers running ESXi 6.7U2.
Each server has three 1Gbps uplinks. The uplinks have public IP addresses and are connected to the ISP's top-of-the rack switch.
Two of the uplinks are for traffic in and out of ESXi itself (largely for redundancy) one uplink per machine is to serve as the external IP address of a VM-based router to which a different /24 per server is routed. The VM-based routers on each server then make the two /24s available to both cluster members via two Distributed Switches. One Distributed Switch for each /24.
That way, both servers can draw out of either /24 pool as desired.
The servers have a second set of NICs that offer 2x 40Gbps connectivity and are directly connected via DAC cables.
How do we need to configure those interconnect NICs and ESXi to ensure that traffic between the servers used by VMs attached to the he Distributed Switches will only run through the 2x 40bps NIC and never take a "detour" through the slower 1Gbps side (and its associated vSwitch)?
I read quite a few docs, watched a lot of how-to videos, and searched on google, but I can't figure out how to actually enforce such a routing.
Finally, what IP addresses should be used for the interconnect NICs? I presume that if we we use IP addresses out of the two /24s, traffic from one /24 to the other /24 would be routed out via one router VM, back in via the other router VM and therefore again be bottlenecked.
Do we use private IP addresses on each of the 40Gbps NICs and them somehow force a route between the /24s via the interconnect NICs from the ESXi command line somehow?
My apologies, I am neither an ESXi nor a networking expert.
Big Thanks!
--Marc
This sounds like a really convoluted design and I'm not fully understanding how you have these things connected. Before digging in, can you explain why you have settled on this design pattern? What is running on these two ESXi hosts and what are you trying to accomplish? Because almost certainly there exists better ways to go about this that make more sense and makes traffic flow distribution easier.
You can't increase the windowsize, that is indeed maxmum 1000 entries.
But you have a small error in the RewindCollector call (you forgot the parenthesis) which made it be possitioned on the last 'page'.
Try like this
$TaskNumber=1000
$TaskMgr=Get-view TaskManager
$tFilter=New-Object VMware.Vim.TaskFilterSpec
$tFilter.Time=New-Object VMware.Vim.TaskFilterSpecByTime
$tFilter.Time.beginTime=$DateStart
$tFilter.Time.timeType="startedTime"
$tCollector=Get-View($taskMgr.CreateCollectorForTasks($tFilter))
$tCollector.RewindCollector()
do
{
$Tasks=$tCollector.ReadNextTasks($TaskNumber)
$Tasks.Count
}until($Tasks.Count-eq0)
$tCollector.DestroyCollector()
Selecting Accelerate 3D graphics bugs the program. No matter what i do afterwards, an error pops up.Observation 2: This error wasn't happening on previous versions (15.0.2, 15.0.3, 15.0.4).
daphnissov: the are a few reasons:
1) Redundancy: if one of the two servers (and its associated VM-based router for one of the /24s) goes down, we can trivially temporarily run the VMs of both cluster members on the other cluster member server, using its /24 uplink space. I probably should mention that both VM-based routers will serve IP addresses to the VMs using a particular Distributed Switch /24 via DHCP/DHCPv6, so if one server goes down we simply run all its VM's on the other server, switch the VMs uplink to the remaining functioning Distributed Switch, they will automatically get renumbered out of the other /24, and all we need to do is to update DNS to be back up and running with the full set of VMs until the dead cluster member gets repaired.
2) We need a fast interconnect between VMs running on two difference cluster members to test some clustering performance of certain Open Source software. There exist users of that Open Source software that do connect their systems via QFSP+ NICs and switches, but we've never had the hardware to test this ourselves. With a two servers that each have a two dual-port QFSP+ NIC and two DAC cables between them, we will finally have a setup that should at least in theory allow us to do testing approaching real-life usage of the software.
3) The ISP at which we are hosting the two cluster members doesn't offer top-of-rack switches with QSFP+ ports and unlikely ever will. High-speed clustering via DAC is our only technically feasible way to achieve high-speed interconnects between the two ESXi hosts in the cluster.
Does that help explain things?
Thanks,
--Marc
I've been trying to pin down the issue for hours. I took your advice and I'm trying to find the problem on my guest OS or upstream in my physical network. It appears as if the port 25565 is being listened on by Ubuntu, according to the image I've attached. I'm seriously stuck, I have no idea how to pin down the problem of why people can't connect to the Minecraft server from outside the LAN network.
I have just created a new post on the VMware Workstation Player discussion page because it's the write place of my post to be (I thought i was posting on the right discussion page.). Nevertheless, i guess people with the Pro version may experience the same problem than i.
I'm having a difficult time visualizing what you're describing with regard to this VM router and what VMs you have running that need those services plus how these interconnected 40 GbE interfaces come into play. It'd be very helpful if you can paste in some screenshots of your vSphere networking for us to examine.
That netstat output only shows port 25565 being listened to on an IPv6 socket, not IPv4.
How would I go about making port 25565 listen on IPv4? I can't seem to figure it out.