That's got it, thanks for the solution a.p.!
Re: Networking VMs on a fully Isolated switch
Re: vCenter Install Fails when trying to install the vCenter Server to the PSC node in HA mode
Were you able to solve this we are having the same issue with our configuration behind an F5 load balance appliance?
Packet captures show clean connectivity between hosts when we get the error it appears that the vCenter install is terminating the session to the PSC (tear down in the packet capture).
We can telnet to port 443 from vCenter to each PSC and to the PSC load balanced name and IP.
We can ping each PSC from vCenter and vice versa.
Re: vRealize Buisness 7.0.1 can see only 1 Vcenter server information even though configured 3
Hello,
In the status page, do you see a last successful run date for all 3 vCenters?
Something you can try is remove all 3 vCenters, and add each vCenter one by one. Add one, let it collect and run a cost calculation automatically and then add the second one and let it run, etc.
Re: Prescript for diferent operations
Hi,
where did you find that inf file ? I will try to have a look at it.
Thank you.
Re: vCenter Install Fails when trying to install the vCenter Server to the PSC node in HA mode
You're more than likely going to have to get GSS involved.
Can I ask why you are choosing to use the load balancer as opposed to deploying multiple PSCs and repoint in case of failure? There's no right or wrong answer, just asking. Because of the difficulty in deploying and then operating this setup, many customers just forgo the load balancer and repoint if there is a PSC failure. But that isn't appropriate for ALL environments.
ESXi 6.0 U1 to U2 upgrade, iSCSI issues
Hello,
First time posting, so I'll try and sum up my thoughts and what I've done with troubleshooting. Please let me know if I left anything out or more information is needed.
I'm running the free ESXi 6.0 on a Supermicro X10SLL-F mATX board with an Intel Xeon E3-1231v3 CPU and 32 GB of DDR3 ECC UDIMMs. I use a 4G USB flash drive for boot, 75 GB 2.5" SATA for local storage (i.e. /scratch), and a portion of a 120 GB SSD for host cache as well as local storage. The main datastore for the VMs are located on on an iSCSI target (running FreeNAS 9.3.x). This setup has worked very well since the install of ESXi 6.0 (June 2015), then 6.0 U1 (Sept. 2015) and I just recently took the plunge to 6.0 U2. I figured everything should be business as usual for the upgrade...
However, after upgrading to 6.0 U2 none of the iSCSI volumes are "seen" by ESXi anymore -- vmhba38:C0:T0 &vmhba38:C0:T1, although I can confirm that I can ping the iSCSI target and that the NIC (vmnic1), vSwitch, and VMware iSCSI Software Adapter are loaded -- I have not made any changes to either ESXi nor the iSCSI host prior to the upgrade to 6.0 U2. It was all working beforehand.
I next went digging into logs; vmkernel.log and vobd.log all report that it couldn't contact the storage due to a network issue. I also did some standard network troubleshooting (see VMware KB 1008083); everything passed, except for the jumbo frame test.
[root@vmware6:~] tail –f /var/log/vmkernel.log | grep iscsi
[ ... ]
2016-03-31T05:05:48.217Z cpu0:33248)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T:0 CN:0: iSCSI connection is being marked "OFFLINE" (Event:5)
2016-03-31T05:05:48.217Z cpu0:33248)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]
2016-03-31T05:05:48.217Z cpu0:33248)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 10.xxx.yyy.195:41620 R: 10.xxx.yyy.109:3260]
2016-03-31T05:05:48.218Z cpu4:33248)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:5)
2016-03-31T05:05:48.218Z cpu4:33248)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: (null) TPGT: 0 TSIH: 0]
2016-03-31T05:05:48.218Z cpu4:33248)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 10.xxx.yyy.195:32715 R: 10.xxx.yyy.109:3260]
[root@vmware6:~] tail –f /var/log/vobd.log
[ ... ]
2016-03-31T05:05:48.217Z: [iscsiCorrelator] 1622023006us: [vob.iscsi.connection.stopped] iScsi connection 0 stopped for vmhba38:C0:T0
2016-03-31T05:05:48.217Z: [iscsiCorrelator] 1622023183us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 failed to login to iqn.2005-10.org.freenas.ctl:vmware-iscsi because of a network connection failure.
2016-03-31T05:05:48.217Z: [iscsiCorrelator] 1622002451us: [esx.problem.storage.iscsi.target.connect.error] Login to iSCSI target iqn.2005-10.org.freenas.ctl:vmware-iscsi on vmhba38 @ vmk1 failed. The iSCSI initiator could not establish a network connection to the target.
2016-03-31T05:05:48.218Z: [iscsiCorrelator] 1622023640us: [vob.iscsi.connection.stopped] iScsi connection 0 stopped for vmhba38:C0:T1
2016-03-31T05:05:48.218Z: [iscsiCorrelator] 1622023703us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 failed to login to
[root@vmware6:~] ping 10.xxx.yyy.109
PING 10.xxx.yyy.109 (10.xxx.yyy.109): 56 data bytes
64 bytes from 10.xxx.yyy.109: icmp_seq=0 ttl=64 time=0.174 ms
64 bytes from 10.xxx.yyy.109: icmp_seq=1 ttl=64 time=0.238 ms
64 bytes from 10.xxx.yyy.109: icmp_seq=2 ttl=64 time=0.309 ms
--- 10.xxx.yyy.109 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.174/0.240/0.309 ms
[root@vmware6:~] vmkping 10.xxx.yyy.109
PING 10.xxx.yyy.109 (10.xxx.yyy.109): 56 data bytes
64 bytes from 10.xxx.yyy.109: icmp_seq=0 ttl=64 time=0.179 ms
64 bytes from 10.xxx.yyy.109: icmp_seq=1 ttl=64 time=0.337 ms
64 bytes from 10.xxx.yyy.109: icmp_seq=2 ttl=64 time=0.382 ms
--- 10.xxx.yyy.109 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.179/0.299/0.382 ms
[root@vmware6:~] nc -z 10.xxx.yyy.109 3260
Connection to 10.xxx.yyy.109 3260 port [tcp/*] succeeded!
[root@vmware6:~] vmkping -s 8972 10.xxx.yyy.109 -d
PING 10.xxx.yyy.109 (10.xxx.yyy.109): 8972 data bytes
--- 10.xxx.yyy.109 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
I then started looking at the NIC drivers thinking maybe something got screwed up during the upgrade; not the first time I've seen issues with the out-of-box drivers provided by VMware. I checked VMware's HCL for I/O devices; the physical NICs used on this host are Intel I217-LM (nic-e1000e), Intel I210 (nic-igb), and Intel 82574L (nic-e1000e). VMware's HCL lists that the driver for the I217-LM & 82574L should be version 2.5.4-6vmw and I210 should be 5.0.5.1.1-5vmw. When I went to check, I noticed it was using a different version for the e1000e driver (I210 driver version was correct).
[root@vmware6:~] esxcli software vib list | grep e1000e
Name Version Vendor Acceptance Level Install Date
----------------------------- ------------------------------------ ------ ---------------- ------------
net-e1000e 3.2.2.1-1vmw.600.1.26.3380124 VMware VMwareCertified 2016-03-31
The esxupgrade.log would seem to indicate that VMware's e1000e 2.5.4-6vmw should have been loaded...
[root@esxi6-lab:~] grep e1000e /var/log/esxupdate.log
[ ... ]
### ESXi 6.0 U1 upgrade
2015-09-29T22:20:29Z esxupdate: BootBankInstaller.pyc: DEBUG: About to write payload 'net-e100' of VIB VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585 to '/tmp/stagebootbank'
[ … ]
### ESXi 6.0 U2 upgrade
2016-03-31T03:47:24Z esxupdate: BootBankInstaller.pyc: DEBUG: About to write payload 'net-e100' of VIB VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585 to ''/tmp/stagebootbank'
The e1000e 3.2.2.1-1vmw is the recommended driver for ESXi 5.5 U3 and not ESXi 6.0 U2! Since these drivers are listed as "Inbox", I'm not sure if there an easy path to download vendor-provided drivers (vib) for it, or if they exist even. I found an article on-line to manually update drivers on an ESXi host using esxcli; I attempted to check for and install any newer e1000e drivers.
[root@vmware6:~] esxcli software vib update -n net-e1000e -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMware_bootbank_net-e1000e_3.2.2.1-2vmw.550.3.78.3248547
VIBs Removed: VMware_bootbank_net-e1000e_3.2.2.1-1vmw.600.1.26.3380124
VIBs Skipped:
As you can see it found a newer version and installed it. However after rebooting it still did not fix the issue. I even went so far as to force the CHAP password used to authenticate by resetting it and updating it on both sides (iSCSI initiator & target). At this point I'm wondering if I need to somehow downgrade and use the 2.5.4-6vmw driver (how?) or if there is some other issue at play here. Am I going down a rabbit hole with my idea that it's a NIC driver issue?
Thanks in advance.
-- G
Re: Detect when a VM hits Disk IOPs Limit
You may be able to create a custom alert using PowerCLI if you can identify the EventTypeID that you're wanting to monitor.
VMware Front Experience: Creating vCenter alarms with PowerCLI
Re: Goodbye from Dave Briccetti
Hey Dave, it was great working with you! Sad to see you go. Good luck with your future endeavors!
Re: vRB7 can't collect data from vRA7. data collection status error
Hello,
The users should only have 1 of the user roles assigned. If you give it all 3 user roles, it takes the role with the least permissions, IE the read only role. This role doesn't have permissions to add the license. You need just the Business Management Administrator role to add the license.
For vRB 7.0.1 it is compatible with vRA 7.0.1, 7.0, and 6.2.4, the matrix is indeed correct.
Re: Unable to Create File Share in App Vol 3.0
i am having the same issue...
created the share on file server, trying to add the share and get the same error. i have everyone as read/write to the share.
my LDAP is not using secure...
did anyone find a solution yet?
Environment variables
hi,
We are just implementing VMWare UEM in our vmware view environment (both changing from persona management in combination with RES). Does anybody know if the environment variables feature can be used to reference ActiveDirectory user attributes (like DisplayName for instance)?
Thanks for the advise.
Maarten
notify switches?
Hello there.
I`ve faced unfamiliar situation.
I got scheme like on the screenshot
Actually each host has 6 nics, not 2, but I think this scheme is ok for example.
These switches are embedded HPc7000 enclosure switches. Afaik they are unstackable, even if they are, I doubt that I have enough skills to stack them correctly. So I got 2 questions:
1. Lets imagine I make port group (in dvswitch) and use it for vms communication only, so the traffic wouldn`t go further than procurves. I set uplink1 and uplink2 both as active in Nic Teaming options (based on nic load). I got some dilemma here: h2.nic2 can communicate only with h1.nic2 (across procurve2) and respectively h2.nic1 can communicate only with h1.nic1 (across procurve1). Lets imagine that h2.nic2 is down, but host1 continues to send traffic via h1.nic2 and miscommunication happens. If I set option "notify switches", host1 will "aknowledge" that h2.nic2 is down and will not send traffic via h1.nic2 anymore, am I right?
2. Wanna use 2 vmnics on each host for vmotion. Will make 2 port groups: 1st group - uplink1 active, uplink2 standby; 2nd group - uplink2 active, uplink1 standby. I guess there is a point to use different network addressing for each port group (I think its not necessary to use different vlan for each group), because of
h2.nic2 can communicate only with h1.nic2 (across procurve2) and respectively h2.nic1 can communicate only with h1.nic1 (across procurve1)
So I will get different routes for each pair (h1.nic1-h2.nic1 and h1.nic2-h2.nic2).
Re: VMWare Workstation on Linux DNS adding localdomain to response
FWIW I see the same behavior on archlinux with kernel 4.4.5-1, VMware 12.1, and Win7Pro guest using NAT.
A quick work-around is to manipulate the Windows guest network settings so that the default DNS server is external to the host. I set the guest DNS to my network router, rebooted, and now DNS works.
(Kinda implied in the first post here.)
This seems to be an uncommon problem. It might be that it occurs only on networks with a named domain (e.g. myveryowndomainname rather than no-name); I haven't experimented.
It also seems to be an entirely artificial problem created by vmware workstation 12 configuration. I didn't have this problem with Workstation 11.
Re: Cloud Client4.0 error
By the looks of the path, you have cloud client installed on a windows machine, correct?
It might be that cloud client is unable to see the path C:\Installers
session: [INACTIVE] shows up on ours as well, but as long as login:[ACTIVE] is true it should work.
In our environment, I installed cloud client 4.0 on one of the vRA appliances, used winscp to copy the package to the /tmp folder and import from there.
Once installed and running I logged into first vra, then iaas.
then ran the command:
vra content import --path /tmp/MicrosoftSharePoint2013-composite-blueprint.zip --dry-run true --resolution overwrite
once verified it would work changed the dry-run flag to false.
I also had an issue where logging into the model manager first logged in but stopped once logging into vra.
It might also be that the package you are trying to import is invalid, the SharePoint2013 one include the software blueprint that you are trying to import.
Hope this helps
Communication from within a ESXi Host
Hi, I'm relatively new to this technology, and i was wondering if there is a way to monitor NSX running on a host, and have the host send if the amount of memory surpasses a percentage of the total memory to another server.
I tried opening SSH, but i cant have it opened and closed every time. I also tried using netcat to send the log, but wont communicate to any other server.
Any ideas, everything is helpful at this point.
Thanks.
PD: Im working in 5.5.
Re: Does VMWare Fusion support shared disks?
It seems to be working if also setting disk.locking = "FALSE"
But can someone let me know if the correct parameter is scsi0:1.sharing = "multi-writer" os scsi0:1.shared = "TRUE"?
Re: Environment variables
Can you give us an example and maybe some screenshots on what you need to happen? Not sure this is the settings you need to be in.
2 node HA Cluster both nodes showing up as MASTER
I have a 2 node vRops 6 HA cluster that have both nodes showing up as "MASTER" as their cluster role. everything seems to be functioning ok, just not sure as to why both nodes show MASTER and not MASTER, MASTER replica ? has anyone else ran across this issue and if so how should it be resolved.
Re: NAT crashed with Workstation Pro 12.1.0
Same issue here, created a NAT rule to allow access to a web server running on a local Linux VM. (Host OS is Windows 10.) Every time you try to access it, the NAT service crashes. Took me a while to figure out what was going on, I thought I was crazy and the configuration was broken.
Guess I'll revert to 12.0.1...
[Edit]
Workaround --- Taking a page from user 4llan above.
I installed VMware Workstation 12.0.1 (in a VM) and grabbed the vmnat.exe file (C:\Windows\SysWOW64).
I stopped the VMware NAT service on the host, plopped this file over top of the old one on the host, and started the service again.
All seems good now.
Re: List DataStore VM's
Thank you once again Luc,
As usual, you don't fail to impress with your PowerCLI abilities