Have been using perforce on my windows 8 laptop without issues, but we recently started using a mac where I have a VMware fusion(windows 10) installed.
However I am not able to sync and get the latest revision of the code I need, since it keeps timing out on me with a WSAECONNRESET error
I'm curious, did that fix your problem?
The KB you linked is what we used to come up with the above ACL's. We are using an HP Procurve core switch. Its firewall and ACL's are not statefull. It appears that the USB and some other traffic that returns from the initial connection is on random ports using RPC. Are these RPC port ranges configurable or even documented?
Hi all and thanks in advance and apologies for the long upfront story.
I am, to say the least, inexperienced with VMware. A company I've had a consulting relationship on and off with for 10 years or so decided 12 months ago to virtualise their environment.
The decision was mostly driven by DR considerations, but there would be other benefits as well.
Unfortunately they chose a local IT provider to perform the system conversion and to be polite about it, they did a piss poor job.
They implementation took longer than expected, there were numerous issues of down time, things didn't work as advertised and so on.
At the start of the year they brought me in to look over things and move things forward. I've got a good overview of modern IT systems and have been in the business for 25+ years. Virtualisation is something I've been aware of, just never really dealt with.
I got a couple of contractors in deal with the initial mess - one to tidy things up as best he could and another for a general audit and planning. The core problem (apart from very basic mistakes in configuration like not taking into account actual required performance, leaving over sized disks in place, massive over commitment of vCPUs and memory) was the storage back end. They'd tried to use a Synology NAS for all back end storage. Their initial configuration didn't even have a separated or vlan'd iSCSI network. However, with running 12 servers (including 2 database servers and 1 exchange server) performance was very poor and once Veeam backups started trampling things would get much worse with ongoing consolidation issues, lagging backup running into production time, servers stunned every which way and so on...
The actual VMware system is a pair of Dell R430s in a HA Cluster, with a similar setup at the DR site. During a normal running day, the servers are balanced with across the pair of esx hosts.
Ok, I've painted my picture!
We had the worst of the configuration issues fixed, and last weekend I installed an MSA2040 with 2 x 16Gb Fibre channel in each controller, and a dual 16Gb (2662?) card in each ESX host. One cable from each controller to each esx host - not FC switch.
The migration work took about 24 hours, and everything is just so much better, more than 5 times the speed across the board and everything steady and stable.
Why did I do the installation? Costs, basically. It seemed like something well within my grasp (after months of studying and examining the systems and options) and not overly complex.
I'm looking at things now and I notice that on host 2 everything shows as multipath Ok, and on host 1 things show as degraded (or Partial/No redundancy).
I would swear I've done nothing different between the two hosts, and the MSA 2040 SMU shows all 4 FC connections as active.
So what am I doing wrong? Or what else am I missing? All input very much appreciated.
Esxcfg-scsidevs -l shows this on
host 1
naa.600c0ff00026e0890000000000000000
Device Type: Enclosure Svc Dev
Size: 0 MB
Display Name: HP Fibre Channel Enclosure Svc Dev (naa.600c0ff00026e0890000000000000000)
Multipath Plugin: NMP
Console Device: /vmfs/devices/genscsi/naa.600c0ff00026e0890000000000000000
Devfs Path: /vmfs/devices/genscsi/naa.600c0ff00026e0890000000000000000
Vendor: HP Model: MSA 2040 SAN Revis: G210
SCSI Level: 6 Is Pseudo: false Status: on
Is RDM Capable: true Is Removable: false
Is Local: false Is SSD: false
Other Names:
vml.020d000000600c0ff00026e08900000000000000004d5341203230
VAAI Status: unsupported
naa.600c0ff00026e0897718f55601000000
Device Type: Direct-Access
Size: 3999708 MB
Display Name: HP Fibre Channel Disk (naa.600c0ff00026e0897718f55601000000)
Multipath Plugin: NMP
Console Device: /vmfs/devices/disks/naa.600c0ff00026e0897718f55601000000
Devfs Path: /vmfs/devices/disks/naa.600c0ff00026e0897718f55601000000
Vendor: HP Model: MSA 2040 SAN Revis: G210
SCSI Level: 6 Is Pseudo: false Status: on
Is RDM Capable: true Is Removable: false
Is Local: false Is SSD: false
Other Names:
vml.0200010000600c0ff00026e0897718f556010000004d5341203230
VAAI Status: supported
naa.600c0ff00026e0f76d18f55601000000
Device Type: Direct-Access
Size: 3999708 MB
Display Name: HP Fibre Channel Disk (naa.600c0ff00026e0f76d18f55601000000)
Multipath Plugin: NMP
Console Device: /vmfs/devices/disks/naa.600c0ff00026e0f76d18f55601000000
Devfs Path: /vmfs/devices/disks/naa.600c0ff00026e0f76d18f55601000000
Vendor: HP Model: MSA 2040 SAN Revis: G210
SCSI Level: 6 Is Pseudo: false Status: degraded
Is RDM Capable: true Is Removable: false
Is Local: false Is SSD: false
Other Names:
vml.0200000000600c0ff00026e0f76d18f556010000004d5341203230
VAAI Status: supported
-------------------------------------------------------------------------------------------------------
host 2
naa.600c0ff00026e0890000000000000000
Device Type: Enclosure Svc Dev
Size: 0 MB
Display Name: HP Fibre Channel Enclosure Svc Dev (naa.600c0ff00026e0890000000000000000)
Multipath Plugin: NMP
Console Device: /vmfs/devices/genscsi/naa.600c0ff00026e0890000000000000000
Devfs Path: /vmfs/devices/genscsi/naa.600c0ff00026e0890000000000000000
Vendor: HP Model: MSA 2040 SAN Revis: G210
SCSI Level: 6 Is Pseudo: false Status: on
Is RDM Capable: true Is Removable: false
Is Local: false Is SSD: false
Other Names:
vml.020d000000600c0ff00026e08900000000000000004d5341203230
VAAI Status: unsupported
naa.600c0ff00026e0897718f55601000000
Device Type: Direct-Access
Size: 3999708 MB
Display Name: HP Fibre Channel Disk (naa.600c0ff00026e0897718f55601000000)
Multipath Plugin: NMP
Console Device: /vmfs/devices/disks/naa.600c0ff00026e0897718f55601000000
Devfs Path: /vmfs/devices/disks/naa.600c0ff00026e0897718f55601000000
Vendor: HP Model: MSA 2040 SAN Revis: G210
SCSI Level: 6 Is Pseudo: false Status: on
Is RDM Capable: true Is Removable: false
Is Local: false Is SSD: false
Other Names:
vml.0200010000600c0ff00026e0897718f556010000004d5341203230
VAAI Status: supported
naa.600c0ff00026e0f76d18f55601000000
Device Type: Direct-Access
Size: 3999708 MB
Display Name: HP Fibre Channel Disk (naa.600c0ff00026e0f76d18f55601000000)
Multipath Plugin: NMP
Console Device: /vmfs/devices/disks/naa.600c0ff00026e0f76d18f55601000000
Devfs Path: /vmfs/devices/disks/naa.600c0ff00026e0f76d18f55601000000
Vendor: HP Model: MSA 2040 SAN Revis: G210
SCSI Level: 6 Is Pseudo: false Status: degraded
Is RDM Capable: true Is Removable: false
Is Local: false Is SSD: false
Other Names:
vml.0200000000600c0ff00026e0f76d18f556010000004d5341203230
VAAI Status: supported
-------------------------------------------------------------------------------------------------------
ccan you right click and open as administrator? Or use the command line to change the file permissions?
Even if I don't understand spanish, I understood the command in Tyepez post and this was the solution for us after migration the boot into a new SAN we had these error on all our esxi host. Thank you for this information.
When you say vAPP,i believe you are referring to VAPP network? .Every VAPP network is a Port-group,based on the Network Pool requirements it can be either on VSwitch Or Distributed Switch.
LucD,
Unfortunately that didn't work. Please forgive me, but I won't be able to update this post until tomorrow as my findings are a little erratic at the moment and need to understand what is happening. It looks like it created all of the accounts, but the VIPermission appears to still be erroring. At least some of the vHost threw the same error "the specified role is from a different server".
I find that get-vmhostaccount does return an account with my account name. However, get-vipermission -principal <<test>> doesn't return anything...just goes to the next line but returns no data or error. A bit odd.....?
Jason
I tried \\server.domain.com\share but still same error. I am using and set to ldap. Still same error.
Thanks for the script, Cormac. It turned out that in my case, all of the objects that failed "due to being locked or lack of vmdk descriptor file" were either ".vswp" files, or "-internal.vmdk" files from floating VMware Horizon View desktop VMs. These files were not orphaned according to VSAN -- running the VSAN health check in RVC resulted in no orphaned objects. They seemed to be "locked" however, despite me having rebooted all of the ESXi hosts and restarted management agents. I think the root cause is that VMware Horizon View comes with VSAN storage policies out-of-the-box specifying FTT=0 for "floating" desktops. This is dangerous IMHO because host reboots and ESXi patching causes these "floating" VMs to become in a "zombie" state. I am guessing this is why I ended up with all of these locked files. I have subsequently changed the VSAN storage policies to FTT=1 in hopes of preventing this in the future. I ended up deleting and re-provisioning the floating desktops via VMware Horizon View, and using the "/usr/lib/vmware/osfs/bin/objtool delete -u" option to delete the old object references that did not go away cleanly. Then I was able to proceed with the VSAN v3 file system upgrade. This was all quite labor intensive -- way more "babysitting" than I've ever had to do with a traditional external storage array -- so I sure hope VMware can focus on making VSAN as user-friendly as traditional external storage arrays, with less manual administrative effort required. It's frustrating how much "poking around" needs to be done in RVC and the ESXi CLI to resolve some of these obscure issues.
So I was missing the VcMachineConfigSpec before the VcToolsUpgradePolicy.
So here is the finished product.
Thanks
B
I have a ProLiant running Windows Server 2012 and want to run this server as a VM within a different box (that's running VMWare).
Can I physically install the ProLiant's hard disk in my VMWare machine and somehow import it ?
I'm assuming the WS 2012 software will get rather confused about appearing in a new hardware environment, so I'm not getting my hopes up that this is possible....but it would be great if this was possible.
I tried to upgrade my ESXi 5.5 hosts to 6.0U2 using a USB drive and 2/6 of the hosts failed with "Directory Not Empty" and referenced $RECYCLE.BIN.
I then rebooted the hosts into the USB and tried again but the second time around; it no longer says Upgrade, it wants to wipe out and reinstall from scratch...
I went through each storage and ESXi wasn't found on any of them... I rebooted without the USB and it seems to boot to ESXi 5.5 just fine.
I am wondering where to go from here; I dont feel comfortable reinstalling EXSi because we have a mix of VMs on Datastore & iSCSI LUNs, I can't risk losing these VMs and trying to reimport critical VMs is troubling.
Is there another way to upgrade these hosts?
Hello all,
I want to have a blueprint with 1 (or more) VMs that has a Routed Network Profile that will create an Edge Gateway to route that network, every time that blueprint is requested.
Is that possible or do I ABSOLUTELY have to use an EXISTING ESG or DLR for Routed Network Profiles?
I can't seem to get it to work, vRA sometimes returns weird errors like below:
vRA6 : Multi-machine service mmbpxyz-123 request failed for component blueprint 'Edge': Allocate reservation operation failed for business group BG-Test. No reservation available that has all specified network profiles: EXTERNAL-NETWORK assigned to any edge network paths.
vRA7 : Machine Edge-TESTRouted-5d4692f4-ddef-4702-a971-5a3e849c9d2a: Allocate reservation operation failed for business group BG-Test. No reservation available that has all specified network profiles: EXTERNAL-NETWORK assigned to any distributed logical router network paths.
(P.S.: That Routed Network Profile's "External Network" is checked in the Reservation that is being used by the VM, and the Reservation that is used by the NSX components, so that's definitely a false positive.)
So you can tell from the error message that vRA (6 & 7) is trying to create an Edge, but fails for no real reason.
Also, notice the error message in vRA7 is slightly different at the end, using the term "distributed logical router" instead of "edge".
So I ask again : Is it possible to have vRA provision an Edge Gateway for VMs using a Routed Network Profile or do I absolutely have to use an existing ESG or DLR to connect the Routed Networks to?
For reference :
vRA: 6.2.1 and vRA 7.0
NSX 6.2.1
NSX plugin for Orchestrator : 1.0.3
Thanks in advance for your help,
Marc
Probably the most common issue: within the vRealize Automation IAAS installer untick the checkbox that sais "use SSL for database connection" if you're using SQL express.
Otherwise, if you want to use SSL: trust the cert that your SQL database is using on the IAAS server and try again.
Are you using NAT? If so try Bridged and see if it makes any difference.
Hello!
I have numerous CentOS 6.5 servers I'm trying to convert into ESX from Xen. The conversions complete fine, and the VM's boot to the grub loader, but then just a white line non-flashing cursor on a black screen.
I've booted to system recovery disks and all the fstab entries align correctly with the new device partitions, and GRUB reflects this. Lost as to what the issue may be...
Anyone else experience this?
We are developing a Windows 10 Enterprise 1511 virtual desktop image in a local domain, with the Store disabled, without Azure sync or Microsoft accounts, and without OneDrive. All the applications and %ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs for all the non persistent VM's will be identical.
Initial testing of these VM's reveals that when a user logs off of one VM and logs into another, their Start Tiles to not roam with them. I read alot of people are a little dismayed and imply that Microsoft is trying to kill the Roaming Profile.
Using Persona Management and roaming %localappdata%, after a logoff, at the next logon there are quite a few issues. The Start menu often fails to open or is blank.
This is Windows 10 Enterprise 64bit with Horizon View Agent 6.2.2.3508800. The Connection server is 6.2.0 build-3005368. We redirect most personal folders with the exception of AppData. I can provide you with logs and will do so OOB.
The issue is present regardless of whether we try to additionally roam %localappdata%. The sequence of events goes like this. With a floating linked clone pool a user logs into Windows 10 for the first time ever. The new .V5 persona directory get created for that user with a .lck lock file. Pin some items to the start menu and task bar. Customize Microsoft Edge by specifying a custom start page and make import some bookmarks, visit a page that sets a cookie. Wait around 15 minutes for the persona to sync up to the repository even though a logoff will trigger the same. Logoff and wait for the VM to finish sync'ing your profile to the repository and then log into another Windows 10 VM.
The Start menu will now be completely absent of any pinned items and Edge will have lost the customization made earlier.
I think he meant to say that the sample chassis-B-html when deploy into virgo in SDK 6.0 does not work (the objects not displayed in the Objects tab). The development environment vCenter version (when you click About) shows it's 5.5 Build 1588022, so would that be the reason the object does not show up?