What happens when sending to VirtualCenter instead? You should normally go through VirtualCenter instead of to hosts directly if you have hosts managed by VirtualCenter, especially when your h...
See more...
What happens when sending to VirtualCenter instead? You should normally go through VirtualCenter instead of to hosts directly if you have hosts managed by VirtualCenter, especially when your hosts are in clusters which are VirtualCenter-level objects.
Sorry about the lack of documentation for 3.0, we are still feverishly working on completing features and documentation will follow shortly. However, most of the existing documentation will apply...
See more...
Sorry about the lack of documentation for 3.0, we are still feverishly working on completing features and documentation will follow shortly. However, most of the existing documentation will apply to HQ 3.0. You can essentially follow the same procedure to enable the monitoring that you are looking for. Rather than "under" the Services section, you will now click on Services so that the section opens up. You can also get to the same service creation page by going to any platform and clicking on the TOOLS MENU and then click on New Platform Service. Hope this helps.
Hm. I dont see anything interesting in there either. Probably best way to follow up on this if you keep seeing this is to file a customer support incident.
Promiscuous mode is not a VMware specific feature, which is why the haven't explained what they mean by the term. It basically means that when a NIC is set to promiscous mode it will see all t...
See more...
Promiscuous mode is not a VMware specific feature, which is why the haven't explained what they mean by the term. It basically means that when a NIC is set to promiscous mode it will see all traffic that passes it, not just traffic routed directly to it. It's used for things like IDS. http://en.wikipedia.org/wiki/Promiscuous_mode
You do not need to defragment VMFS volumes. Using vmkfstools ensures VMDKs are never fragmented, and the smaller files are all stored in sub-blocks of a single block anyway, so cannot be fragment...
See more...
You do not need to defragment VMFS volumes. Using vmkfstools ensures VMDKs are never fragmented, and the smaller files are all stored in sub-blocks of a single block anyway, so cannot be fragmented. Remember it's not like your average NTFS/EXT3 file system (with 4kb-64kb blocks), VMFS has a huge blocksize (1MB-8MB) so won't fragment in the same way.
Since you don't already have your VCP on version 2.5.x....you'll have to sit the 2-day "What's new" class...or the 4-day "Install & Configure" course before you can take the new VI3 exam and be c...
See more...
Since you don't already have your VCP on version 2.5.x....you'll have to sit the 2-day "What's new" class...or the 4-day "Install & Configure" course before you can take the new VI3 exam and be considered a VCP on version 3. Chris
Think you'll need to use the SDK to achieve this, no built in scripts I know of to put a host into maintenence mode. Pretty easy with the VI Perl Toolkit though, there's actually two sample sc...
See more...
Think you'll need to use the SDK to achieve this, no built in scripts I know of to put a host into maintenence mode. Pretty easy with the VI Perl Toolkit though, there's actually two sample scripts with it that do what you want. hostops.pl allows you to put a host into maintence mode, and there's another script called evacuate.pl that vmotions all VMs off a host. Does require installing a few Perl modules though. http://sourceforge.net/projects/viperltoolkit http://www.vmware.com/support/developer/
As Mr T said, flexible is the replacement for both vmxnet and vlance adapters from ESX2.5.x. The reason you're seeing vmxnet on some VMs is that if they were migrated from a 2.5.x environment to ...
See more...
As Mr T said, flexible is the replacement for both vmxnet and vlance adapters from ESX2.5.x. The reason you're seeing vmxnet on some VMs is that if they were migrated from a 2.5.x environment to 3.x, the vmxnet adapter is left in place. If VMs have been built since the upgrade, they get the flexible adapter by default. Pretty sure there's no performance gain to be had upgrading from vmxnet to the 'flexible' adapter. Would be worth upgrading any vlance VMs though.
Yep, sounds like your installation of iptables is knackered. You can try and re-install it from an RPM but if the system isn't live or you have the capacity to migrate the VMs off the host I'd ju...
See more...
Yep, sounds like your installation of iptables is knackered. You can try and re-install it from an RPM but if the system isn't live or you have the capacity to migrate the VMs off the host I'd just go for a rebuild.
I am looking into the logs. At the same time, you could try VMware convertor: http://www.vmware.com/products/beta/converter/ VMware converter is the next generation of vmimporter. Thanks! ...
See more...
I am looking into the logs. At the same time, you could try VMware convertor: http://www.vmware.com/products/beta/converter/ VMware converter is the next generation of vmimporter. Thanks! Michael
That is correct. It's no different than if you removed the network card, rebooted, and added a new card. When you first log in, you have no network connection. You have to log in locally or us...
See more...
That is correct. It's no different than if you removed the network card, rebooted, and added a new card. When you first log in, you have no network connection. You have to log in locally or use cached credentials. Once you configure the new network adapter (preferably by installing VMware Tools) then you can join the network and then the domain as needed.
Not sure what you mean by "manually set the resource level on the host". Resources are set at 2 levels-- at the VM itself, and a resource pool. The default setting is "normal" for a VM, i.e. ...
See more...
Not sure what you mean by "manually set the resource level on the host". Resources are set at 2 levels-- at the VM itself, and a resource pool. The default setting is "normal" for a VM, i.e. 1000 shares per vCPU and 10 shares per MB of virtual RAM. Once you set the share level of a VM (low, normal, high) it stays the same when you move a VM out of a resource pool to another. The %Shares may adjust in the new resource pool.
Hi Zippy, You need to disable the following in the security policy for the server hosting the SMB share and then reboot it. Disable Microsoft network server: Digitally sign communications...
See more...
Hi Zippy, You need to disable the following in the security policy for the server hosting the SMB share and then reboot it. Disable Microsoft network server: Digitally sign communications (always) Disable Microsoft network server: Digitally sign communications (if client agrees)[/code] This is necessary with ESX3 because of the change of SC from RH 7.2 to RHEL3, under which SMB is handled differently.
Hi Vincent, Glad to hear you were able to compile the packages on your own. The 3.0 branch (trunk) is going through some significant changes as we move from entity beans to hibernate. For n...
See more...
Hi Vincent, Glad to hear you were able to compile the packages on your own. The 3.0 branch (trunk) is going through some significant changes as we move from entity beans to hibernate. For now, I'd suggest building packages from the 2.7 branch, which is the current stable tree. If you checkout the 2.7 tree in a parallel directory to your 3.0 tree the archive-full will work without you needing to pull all the extra packages. The 2.7 branch can be found at: http://svn.hyperic.org/projects/hq/branches/HQ_2_7 -Ryan