Locally this works fine ... vmkfstools -C vmfs3 -b 1m -S newVMFS /vmfs/devices/disks/vmhba0\:0\:0\:8 Creating vmfs3 file system on "vmhba0:0:0:8" with blockSize 1048576 an...
See more...
Locally this works fine ... vmkfstools -C vmfs3 -b 1m -S newVMFS /vmfs/devices/disks/vmhba0\:0\:0\:8 Creating vmfs3 file system on "vmhba0:0:0:8" with blockSize 1048576 and volume label "newVMFS". Successfully created new volume: 49ccc725-d960f371-a33a-0017a43aeb30
Have you tried it with the /vmfs/devices/disks part and backslashs? like this: vmkfstools.pl --servername <name> --username <user> --password <password> -C vmfs3 -...
See more...
Have you tried it with the /vmfs/devices/disks part and backslashs? like this: vmkfstools.pl --servername <name> --username <user> --password <password> -C vmfs3 -b 1m -S <volumename>/vmfs/devices/disks/vmhbaw\:x\:y\:z
This might be caused by the "Quick Scan when new definitions arrive". Find the setting in Client Administrator Only Option > Scans. If this is set and new defs come in, all VMs in this ...
See more...
This might be caused by the "Quick Scan when new definitions arrive". Find the setting in Client Administrator Only Option > Scans. If this is set and new defs come in, all VMs in this group will do a quick scan and hammer your SAN ... We've seen this happening as well and introduced scheduled scans which run at different times. Still a heavy I/O action but not that intense and we can control when and where it's gonna happen.
Did you see this? Is it an option to install Update 3? http://www.vmware.com/support/vi3/doc/vi3_esx35u3_rel_notes.html#resolvednetworkingissues New: Network connectivity Might be ...
See more...
Did you see this? Is it an option to install Update 3? http://www.vmware.com/support/vi3/doc/vi3_esx35u3_rel_notes.html#resolvednetworkingissues New: Network connectivity Might be Lost When Network Teaming Policy is Based on Port Id. Network connectivity might be lost when using network teaming, and the teaming policy is based on Port Id. The following error message might be logged in VMkernel: Aug 6 23:27:07 vmkernel: 0:02:33:07.052 cpu0:1024)Net: L2Sec_EnforcePortCompliance:229: 0x3000005: peer not allowed promiscuous, revoking setting Network connectivity works fine if you enable the promiscuous mode of the virtual vswitch, and perform a tcpdump -i portgroup. But stopping tcpdump again results in loss of network connectivity. This issue is fixed in this release.
Upgrades usually work quite well, but if you have the option I would rebuild the server completly with the newest ESX build. Unplug your HBA (or disable the SAN Switch Ports) to avoid over...
See more...
Upgrades usually work quite well, but if you have the option I would rebuild the server completly with the newest ESX build. Unplug your HBA (or disable the SAN Switch Ports) to avoid overwriting your datastores.
NFS would be shared storage which is a requirement for doing fancy things like VMotion, DRS and HA. But I'd advise to stay with the HCL for this. Stuff like OpenFiler and FreeNAS is nice ...
See more...
NFS would be shared storage which is a requirement for doing fancy things like VMotion, DRS and HA. But I'd advise to stay with the HCL for this. Stuff like OpenFiler and FreeNAS is nice and works pretty well, but is not supported by VMware. You can create a VM Cluster like this. It is written with the MS Cluster in mind. Works for other OS as well though. http://www.vmware.com/pdf/vi3_35/esx_3/vi3_35_25_u1_mscs.pdf
As shared storage is not an option some replication mechanism must be taken in place. Rsync would help maybe () More apropriate link for Ubuntu: https://help.ubuntu.com/community/rsync
Had a similar experience. It turned out that i tried to update with a different user than i initially installed VC with. I logged on with the local admin (this was the user i installed VC with) a...
See more...
Had a similar experience. It turned out that i tried to update with a different user than i initially installed VC with. I logged on with the local admin (this was the user i installed VC with) and it worked for me ...
Put something like this in your Post-Script Log to central syslog server esxcfg-firewall -o 514,udp,out,syslog echo "" >>/etc/syslog.conf echo "# Send everything to c...
See more...
Put something like this in your Post-Script Log to central syslog server esxcfg-firewall -o 514,udp,out,syslog echo "" >>/etc/syslog.conf echo "# Send everything to central syslog server" >>/etc/syslog.conf echo ". @192.168.1.1" >>/etc/syslog.conf service syslog restart
As far as I know, there is no way to rename a portgroup. Be it with esxcfg-vswif/vswitch or with vmware-vim-cmd. However deleting and adding it with the new name should do the trick for you. ...
See more...
As far as I know, there is no way to rename a portgroup. Be it with esxcfg-vswif/vswitch or with vmware-vim-cmd. However deleting and adding it with the new name should do the trick for you. The addvmportgroup option in kickstart can be 0 or 1. It tells the setup to either add a default portgroup for virtual machines called "VM Network" on the first vSwitch or not. It has nothing to do with the Service Console portgroup naming.
No need for dynamic disks. You can use diskpart to extend the ntfs partition after you blew up the vmdk on cmd enter "diskpart" diskpart>list disk diskpart >select disk 1...
See more...
No need for dynamic disks. You can use diskpart to extend the ntfs partition after you blew up the vmdk on cmd enter "diskpart" diskpart>list disk diskpart >select disk 1 (assuming number 1 is the disk with the partition on it that you want to extend) diskpart>list partition diskpart>select partition 1 (assuming number 1 is the partition that you want to extend) dispart>extend Thats it. Please note that this does not work with the System Partition (C: drive). Message was edited by: cheeko to be more clear.
Add a new SC Portgroup with the desired name and delete the old one named "Service Console" esxcfg-vswitch vSwitch -A "My New Service Console" esxcfg-vswitch vSwitch -D "Service Cons...
See more...
Add a new SC Portgroup with the desired name and delete the old one named "Service Console" esxcfg-vswitch vSwitch -A "My New Service Console" esxcfg-vswitch vSwitch -D "Service Console"
vmkfstools is working with good speed ... it seems that all other (non-ESX aware) native Linux commands are affected by this throtteling ... As for the Cache: Write-Back Cache is enabled on th...
See more...
vmkfstools is working with good speed ... it seems that all other (non-ESX aware) native Linux commands are affected by this throtteling ... As for the Cache: Write-Back Cache is enabled on the LUNs (not Write-Through). Beside that it probably isn't the cache, when writes to EXT3 on SAN are ok. Message was edited by: cheeko We are talking about BL480s not 460s - sorry.