The hosts are running on a PowerEdge R710 with a Qlogic 8152. And we are using jumbo frames.
Access to the storage is OK. The vMotion and Storage Networs are in different subnet's.
The hosts are running on a PowerEdge R710 with a Qlogic 8152. And we are using jumbo frames.
Access to the storage is OK. The vMotion and Storage Networs are in different subnet's.
100 - 120 Mb/s ?
thats pretty good for nested VMs IMHO.
You really used vmxnet3 for the ESXi VMs ??? - I would not even consider that.
I would use E1000 nics and then use a hostonly vmnet to connect to the hosts iSCSI targets
and vmkping to the storage is ok?
vmkping -s 9000 storage_ip
Yes. It's OK.
how are you vmkernel interfaces configured? how many nics for vmotion? is vmotion and iscsi vlan separated?
Testing iSCSI storage could be a bit tricker than FC SAN storage because users often fell into network configuration problem.
I think you can try both 1 host-1 datastore and 3 host-3 datastores tests since iSCSI datastores are already shared across hosts.
For maximum IOPS tests, create 9 VMDKs (3 VMDK for each datastores) and attach each VMDK from each datastore for each VM on each host.
In short, since iSCSI storage are shared across hosts, either way should be fine.
the vMotion vmk and the nfs vmk are in separated vlan's, but are in the same standard vswitch which have 2 uplinks. The uplinks are from 2 separated Qlogic 8152 CNA's.
I already check the driver and firmware version and it is ok. both are in the vsphere 5.1 hcl.
I am getting this error on several Vm's in the VIEW 5 environment. I read the following KB from VMware and did exactly what it says and it seemed to help for a while but the error is back. Weird thing is the error only appears if the user logs off of the VM. I have figured out that the only way to fix it is to perform a refresh on the VM.
The following is what we have setup in the environment. Any one have any ideas what to do to take care of this?
Windows 7 VM's
VIEW agent 5.1.2
5.1.2 build-928164 VIEW Environment
Thank you,
Bryan
"You really used vmxnet3 for the ESXi VMs ???"
Well, I found out the hard way.....lol
"100 - 120 Mb/s ?"
Yup, MB/s. That was file copy. That's exactly what I did for my iscsi test. Connected the esxi VM's to the host only vmnet1 and pointed the local iscsi target to present to that IP subnet and bingo!
I think this is related to my "unity" option also being grayed out. What option(s) control whether or not I can run Unity?
Hi VMware family, I'm having some problems.
I'm trying to set up a Windows Server 2003 (yes I know it's old, outdated and blah, but it's all my company will allow me to have so I have to work with it, since my entire budget was spent on purchasing VMWare Workstation 9) and I'm unable to connect any computers to my domain. I can ping the server, and even use RDC to log into the server but I'm unable to connect any computers to my network that I'm creating. When I try, this is the error that I get:
The domain name "FIVESTAR" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS. If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration. The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "FIVESTAR": The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) The query was for the SRV record for _ldap._tcp.dc._msdcs.FIVESTAR Common causes of this error include the following: - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses: 192.168.1.17 - One or more of the following zones do not include delegation to its child zone: FIVESTAR . (the root zone) I need some help because I'm not sure what in tarnation I've done wrong. I configured the DNS, and the AD, as well as the DHCP. Please someone give me something so that I can have this up and functional.
This is what happens when I do the nslookup for my domain:
If you'd archive (compress) and attach the vmware.log file from the target Virtual Machine's Package then one of us will create a new .vmx configuration file for you.
Have a look at: Work with Virtual Machine Packages
お世話になります。
VMWareToolsのSCSIドライバが何か影響していたようで、
これをアンインストールしたところ、正常に動作しました。
ご協力ありがとうございました。
I think I got it figured out.
Looking at var/log/vmkernel I saw many errors. Turned out to be dead luns that I removed from SAN.
I refreshed the hba's and not seeing the problems now,
MANY THANKS for the help.
Tom
Thanks to both of you for your responses. I am going to read some of the vSphere Storage that David recommended as well as Getting Started with vSphere CLI.
I'm not clear - are you saying that this is a hack and backups should NOT be managed with either vSphere Client or Remote CLI, even in a simplified environment?
I have just started with VMware Essentials - should I not even pursue this and just install vCenter Appliance or additional backup software, such as Veeam Free, to do the backups to the Buffalo device?
Thanks again.
Thanks. This will at least keep my stuff uniform for both views!
Hi Twsteffen,
So it sounds like you are talking about IBM Bladecenter with Virtual Fabric adapter or VFA. Please let me know if its not a VFA(II) adapter. But if it is, I think you are seeing the maximum of the vNIC because the phyiscal port can go up to 10Gb. In my opinion it be nice if it displayed the bandwidth set from a switch independent or virtual fabric mode. Each physical 10GbE port will present 4 vNICs to the OS. Since we have two ports you see 8 vNICs. The bandwidth for each vNIC can be configured in increments of 100Mb up to a maximum bandwith of the physical port. The vNICs on a given physical port share the 10Gb bandwidth port.
Maybe this guide can help. Starting on page 22 it talks about the architecture .
Alex
YES!!!!
We were able to get this problems solved by the following:
On the R710 host with the 8152 CNA card do the following:
1. Disable the MSIX capability
esxcli system module parameters set -m qla2xxx --parameter-string "ql2xenablemsix=0"
2. Change the network packet pool size
In vCenter, navigate to the affected Host. Choose Configuration, Choose Advanced Settings under System. Find VMkernel.Boot.netPktPoolMaxSize and change it from 656 to 800.
3. Finally, the Most critical change is to double the netPktHeapMaxSize.
In vCenter, navigate to the affected Host. Choose Configuration, Choose Advanced Settings under System, Change the value of VMkernel.Boot.
anyone ??