LeoKurz2's Posts

O.K., Google is your friend It seems like iptables is the appropriate tool to accomplish the redirection, but there is no iptables on the appliance Any other idea? I don't want to mess arou... See more...
O.K., Google is your friend It seems like iptables is the appropriate tool to accomplish the redirection, but there is no iptables on the appliance Any other idea? I don't want to mess around too much with the appliance as I'm afraid that all is lost sooner or later when it comes to updates etc. Before I start figuring out how to change the standard snmp port on devices like ups, switches etc. (on may I'm sure I won't stand a chance), I'll prefer switching to vco on windows. Shame, but as this has to be a robust and reliable solution, I'm not too keen on any text adventures on the Linux shell of an applince... __Leo
Ivan, thanx a lot for your reply! Any hint how to redirect port 162 to 4000 in the applinace? I hav only limited Linux knowledge... __Leo
Hello, the documentation says: %<--------------------------------------------snip The default port for SNMP traps is 162. However, on Linux systems, you can open ports bellow 1024 only with... See more...
Hello, the documentation says: %<--------------------------------------------snip The default port for SNMP traps is 162. However, on Linux systems, you can open ports bellow 1024 only with superuser privileges. To ensure better compatibility, the default port for listening to SNMP traps in the SNMP plug-in is set to 4000. snap-------------------------------------------->% So, is there a way to use port 162 on the vco appliance (as it runs on linux)? Any help appreciated! __Leo
Hello, just upgraded to vDC 1.5 and noticed that I can't use catalogue media from a PvDC different form the PvDC the vApp is running in. I didn't notice this in vCD 1.0. Has this changed or ha... See more...
Hello, just upgraded to vDC 1.5 and noticed that I can't use catalogue media from a PvDC different form the PvDC the vApp is running in. I didn't notice this in vCD 1.0. Has this changed or have I just overlooked that before the update? We have 3 PvDCs and this would mean, that we would have to copy the contents of each Catalogue 3 times!?! Cheers __Leo
Hello, thank you for your input. Did you run several clones at the same time in the same network? Besides from things like hostname, ip-address etc. I think you would at least have to change t... See more...
Hello, thank you for your input. Did you run several clones at the same time in the same network? Besides from things like hostname, ip-address etc. I think you would at least have to change the mac-address of the kernel port!? And I don't know if there is something like a UUID or something similar. __Leo
Hello, in the "Fibre Channel SAN Configuration Guide", boot from SAN is recommended "If you need easy cloning of service consoles". I know ESXi has no real service console, but this recommenda... See more...
Hello, in the "Fibre Channel SAN Configuration Guide", boot from SAN is recommended "If you need easy cloning of service consoles". I know ESXi has no real service console, but this recommendation IMHO implies, that you can clone ESX and/or ESXi installations but I can't find anything in documentation and knowledgebase. Anyone any idea how to clone ESXi boot devices, in this special case a LUN with ESXi on it for boot from SAN (kind of "sysprep" for ESXi)? Thanx! __Leo
I think the major problem is that there is no quick way to roll back patches on ESX (apart from having a installation base in the network and the up to date installation scrips for every machin... See more...
I think the major problem is that there is no quick way to roll back patches on ESX (apart from having a installation base in the network and the up to date installation scrips for every machine sitting there...). __Leo
@sisi: Nope, no vmotion and I don't think HA will be able to bring VM's up on a U2 ESX after a fialover. Just don't move until the patch is available
If you install all patches from Update Manager, you'll get U2 as well... The U2 patch is simply an XML-file reffering to all available patches. Just take a look at the tar-ball update, it's mor... See more...
If you install all patches from Update Manager, you'll get U2 as well... The U2 patch is simply an XML-file reffering to all available patches. Just take a look at the tar-ball update, it's more than twice(!) the size of the iso because it includes all the patches. The directory for U1 & U2 simply contain the XML metadata. Makes the tar-balls quite useless... __Leo
To avoid time issues within th VMs, for those who start the VMs out of the GUI: Set the time of the ESX to a date before today, then use the new option to boot the VM into the BIOS, set the rig... See more...
To avoid time issues within th VMs, for those who start the VMs out of the GUI: Set the time of the ESX to a date before today, then use the new option to boot the VM into the BIOS, set the right date & time on the ESX machine, set the right date & time in the BIOS of the VM, exit the BIOS and the VM will start with accurate date & time. Disable timesync within VMware tools if enabled and get the right time within the guest OS (DC, NTP...) __Leo
Anyone an idea / procedure how to roll back to U1 (apart from throwing in a CD an do a reinstall)? Will remove certain RPMs work?? __Leo
Just my 5 cent on timesync: The VM will pick up the ESX date & time during reboot. The BIOS clock of the vm is set by ESX. When you have turned on timesync in the VMware tools, the clock of the... See more...
Just my 5 cent on timesync: The VM will pick up the ESX date & time during reboot. The BIOS clock of the vm is set by ESX. When you have turned on timesync in the VMware tools, the clock of the VM will not be set back but it will be slowed down until the ESX clock "catches up". So time in VMs is affected if you use the tools to sync time. Cheers __Leo
Hi, up to now, the user for a vcb proxy had to have the following rights: VM->Provisioning->Allow Virtula Machine Download VM->State->Create Snapshot VM->State->Remove Snapshot VM->Confi... See more...
Hi, up to now, the user for a vcb proxy had to have the following rights: VM->Provisioning->Allow Virtula Machine Download VM->State->Create Snapshot VM->State->Remove Snapshot VM->Configuration->Disk Lease With the latest releases (ESX 3.0.2, VC 2.0.2 & VCB 1.0.3) this doesn't work anymore. vcbVmName works all right. vcbMounter retrives the log files, but when it comes to export the disk files in fullvm mode, I get the error message: \[2007-08-27 11:24:03.421 'BlockList' 3332 error] No permission to perform this action. File mode brings the same error. Using Administrator works all right. Anyone any idea which rights are missing? Cheers __Leo
I'm working on a tricky one... A customer of mine has a "swap problem". Tech support didn't answer at all so I went on site. Modified resource pools as they where one of the causes to swap. Reboo... See more...
I'm working on a tricky one... A customer of mine has a "swap problem". Tech support didn't answer at all so I went on site. Modified resource pools as they where one of the causes to swap. Rebooted some vm's (where possible) and some still started to swap although still RAM available and a failover capacity of 3! HA and DRS with 3 star recommendation switched on. Found that now swapping only occurred on one host. 3 ESX are configured with 2 cores and 8GB RAM and one is configured with 8 cores and also 8GB of RAM. I think what happens is, that DRS assigns a lot of vm's to the fourth server because of the many cpu's. As HA only allows you to use 75% of resources (4 machines), my theory is that on the fourth machine, DRS pushes a lot of vm's (due to cpu's) and "thinks" there is enough memory available but HA doesn't allow the machine to use all it's memory. I'm trying to find s/o within VMware to discuss the issue and in parallel I try to test things out, that's why I need a method to force back swap. __Leo
You might like this: http://www.vmware.com/vmtn/appliances/directory/232 Cheers __Leo
I like this subtle exchange of opinions (the picture is great!), but can we get back from the very basics of ressource scheduling to the original question? ::Leo
There is no limit and no reservation. The VMs swapped once because two servers in the cluster failed, HA started the VMs on the other hosts and then it became a little crowded. When the servers c... See more...
There is no limit and no reservation. The VMs swapped once because two servers in the cluster failed, HA started the VMs on the other hosts and then it became a little crowded. When the servers came back, DRS moved the VMs back but they still have memory swapped out. ESX doesn't move memory back to RAM if there's not really a need for it. For my purpose though, I have to make sure that non of the machines has mem swapped out and rebooting is no option. __Leo
Thanx for the hint, but still this doesn't answer my question. BTW, 10% overhead is not allways a good idea. Depends on amount of assigned memory, number of cpu's and if it's a 32bit or 64bit gue... See more...
Thanx for the hint, but still this doesn't answer my question. BTW, 10% overhead is not allways a good idea. Depends on amount of assigned memory, number of cpu's and if it's a 32bit or 64bit guest. The mem overhead e.g. for a 2 cpu 64bit guest is quite impressive! __Leo
Thanx for the answer. I know how to validate performance. The problem is that I have to do some tests and verification and I need some way to force the swapped memory back into RAM. __Leo
ESX 3.0.1, I see the swap used in VC performance statistics and in esxtop. There \*was* a shortage of memory, but not anymore. The problem ist, that under normal conditions, the memory once swapp... See more...
ESX 3.0.1, I see the swap used in VC performance statistics and in esxtop. There \*was* a shortage of memory, but not anymore. The problem ist, that under normal conditions, the memory once swapped is not relocated back into physical RAM even if there is enough RAM there. One way would be to reboot all vm's but that's not possible. I need a way to force the swapped memory back into physical RAM. __Leo