Hey Everyone.

I'm currently learning ESXi and have set up my virtual serves etc.

However i have recently purchased a Chromebook and would like to know how i go about accessing my server via the Chromebook from the internet no matter where i am located? The idea is to have a machine that I can run any OS on inc the built on Chrome OS.

Ideally i want to be able to have access to things by just pumping in an external ip address in to Chrome browser,  but i also i understand that i would need a VPN set up for things to be most secure?

How can i go about doing both methods for learning purposes and then choosing the best route that suits me long term?

Many thanks in advance.

Hi everyone,

I am setting up a vSphere 5.5 environment in the lab that is to use stateless caching to USB.  I am under the gun to get this into production yesterday.

The hardware used is a Cisco UCS B200-M3 blade with B200M3.2.2.2.0.04282014643 firmware and Cisco provided 4GB USB disk.  There are 4 fiber channel LUNs presented, but these are meant to be data only.

I have been able to validate that the USB disk works by manually installing ESXi to it, and booting from it.

The short version:

We have the vCenter/Auto Deploy/DNS/DHCP/TFTP infrastructure validated and working.  Auto Deploy rules are working.  Applying the Host Profile with "Enable stateless caching to a USB disk on the host" fails with an error that the cache does not meet specification and that the host needs to be rebooted.  Rebooting once or many times does not resolve the error.  The USB disk is blank; the host will not boot from it.  I tried switching the Host Profile setting to "Enable stateless caching on the host" with the first argument being "usb", selected to overwrite any existing VMFS volumes, and selected to ignore any SSD devices.  Same thing happens.

The long version:

I have spent a fair bit of time troubleshooting this, and believe that I found the root cause:  the USB is being claimed for passthrough when it should be left alone for ESXi to mount it and use it.

Here's the story:

/var/log # lsusb

Bus 02 Device 04: ID 0624:0402 Avocent Corp.

Bus 02 Device 03: ID 13fe:3100 Kingston Technology Company Inc. 2/4 GB stick

Bus 02 Device 02: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 02 Device 01: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 01 Device 02: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 01 Device 01: ID 1d6b:0002 Linux Foundation 2.0 root hub

* note: the USB stick is a Cisco part number made by UNIGEN, not Kingston

/var/log # dmesg | grep 13fe

2014-09-05T18:07:23.336Z cpu8:33604)<6>usb 2-1.3: New USB device found, idVendor=13fe, idProduct=3100

2014-09-05T18:07:26.950Z cpu6:33693)<6>usb 2-1.3: Vendor: 0x13fe, Product: 0x3100, Revision: 0x0100

/var/log # dmesg | grep 2-1.3

2014-09-05T18:07:23.216Z cpu8:33604)<6>usb 2-1.3: new high speed USB device number 3 using ehci_hcd

2014-09-05T18:07:23.336Z cpu8:33604)<6>usb 2-1.3: New USB device found, idVendor=13fe, idProduct=3100

2014-09-05T18:07:23.336Z cpu8:33604)<6>usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

2014-09-05T18:07:23.336Z cpu8:33604)<6>usb 2-1.3: Product: PSE4000S3

2014-09-05T18:07:23.336Z cpu8:33604)<6>usb 2-1.3: Manufacturer: UNIGEN

2014-09-05T18:07:23.336Z cpu8:33604)<6>usb 2-1.3: SerialNumber: 40E11B0086921B5A

2014-09-05T18:07:23.336Z cpu8:33604)<6>usb 2-1.3: usbfs: registered usb0203

2014-09-05T18:07:26.950Z cpu6:33693)<6>usb 2-1.3: Vendor: 0x13fe, Product: 0x3100, Revision: 0x0100

2014-09-05T18:07:26.950Z cpu6:33693)<6>usb 2-1.3: Interface Subclass: 0x06, Protocol: 0x50

2014-09-05T18:07:27.237Z cpu6:33693)<6>usb-storage 2-1.3:1.0: interface is claimed by usb-storage

2014-09-05T18:07:27.237Z cpu6:33693)<6>usb 2-1.3: device is not available for passthrough

2014-09-05T18:08:42.445Z cpu18:33546)<6>usb-storage 2-1.3:1.0: unclaiming vmhba32

2014-09-05T18:08:42.445Z cpu18:33546)<6>usb 2-1.3: device is available for passthrough

It appears that the USB device is being unclaimed and made available for passthrough to VMs.  This is not the desired behaviour.

To find our what my USB device is called, I ran:

esxcli storage core device list | less  (output shortened for clarity)

mpx.vmhba32:C0:T0:L0

  Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)

  Vendor: UNIGEN

  Model: PSE4000S3

Based on my understanding, there is a way to prevent making a device available for passthrough by marking it perenially reserved.  This can be done in the host profile, which I've done:

Also, I turned off the USB arbitrator service and tried to reapply the Host Profile to no avail:

/etc/init.d/usbarbitrator stop

So I kept on digging for the reason why ESXi is not writing the cache to USB.

Looking at syslog.log, here's what I found.  (results redacted and shortened)

1. 2014-09-05T17:47:46Z 2014-09-05 17: 47:46,938 Host Profiles[40280]: INFO: Now caching to disk...^@ <-- this is good!

2014-09-05T17:47:55Z HostProfileManager: [2014-09-05 17:47:55,380 root     INFO] Scanning mpx.vmhba32:C0:T0:L0 for any installs ...^@

2014-09-05T17:47:55Z HostProfileManager: [2014-09-05 17:47:55,715 root     INFO] gpt

487 255 63 7831552

1 2048 7829503 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

^@

2014-09-05T17:47:55Z HostProfileManager: [2014-09-05 17:47:55,942 root     INFO] ^@

1. 2014-09-05T17:48:01Z HostProfileManager: [2014-09-05 17:48:01,945 root     INFO]   Found nothing on mpx.vmhba32:C0:T0:L0.^@ <-- this is good!

2014-09-05T17:48:02Z HostProfileManager: [2014-09-05 17:48:02,279 root     INFO] gpt

487 255 63 7831552

1 2048 7829503 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

^@

2014-09-05T17:48:02Z HostProfileManager: [2014-09-05 17:48:02,280 root     INFO] Fresh install.  Using GPT^@

2014-09-05T17:48:02Z HostProfileManager: [2014-09-05 17:48:02,280 root     INFO]   Using the standard, minimum partition layout.^@

2014-09-05T17:48:02Z HostProfileManager: [2014-09-05 17:48:02,280 root     INFO] Checking USB device...^@

2014-09-05T17:48:02Z HostProfileManager: [2014-09-05 17:48:02,807 root     INFO] gpt

0 0 0 0

1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B 128

5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 0

6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 0

7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 0

8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 0

^@ <-- this is good!

2014-09-05T17:48:02Z HostProfileManager: [2014-09-05 17:48:02,807 root     INFO] Preparing Visor volumes on disk /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0...^@ <-- this is good!

2014-09-05T17:48:03Z HostProfileManager: [2014-09-05 17:48:03,112 root     INFO] stderr: create fs deviceName:'/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:8', fsShortName:'vfat', fsName:'(null)'

deviceFullPath:/dev/disks/mpx.vmhba32:C0:T0:L0:8 deviceFile:mpx.vmhba32:C0:T0:L0:8

Checking if remote hosts are using this device as a valid file system. This may take a few seconds...

Creating vfat file system on "mpx.vmhba32:C0:T0:L0:8" with blockSize 1048576 and volume label "none".

Filesystem was created but mount failed on device "mpx.vmhba32:C0:T0:L0:8".: Not found. ^@  <-- ERROR!

Going back to try and find out what happened to my USB storage, I found:

esxcli storage core device list | less

   mpx.vmhba32:C0:T0:L0

   Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)

   Has Settable Display Name: false

   Size: 0

   Device Type: Direct-Access

   Multipath Plugin: NMP

   Devfs Path:

   Vendor: UNIGEN

   Model: PSE4000S3

   Revision: PMAP

   SCSI Level: 2

   Is Pseudo: false

   Status: dead timeout

   Is RDM Capable: false

   Is Local: true

   Is Removable: true

   Is SSD: false

   Is Offline: false

   Is Perennially Reserved: false

   Queue Full Sample Size: 0

   Queue Full Threshold: 0

   Thin Provisioning Status: unknown

   Attached Filters:

   VAAI Status: unsupported

   Other UIDs: vml.0000000000766d68626133323a303a30

   Is Local SAS Device: false

   Is Boot USB Device: false

   No of outstanding IOs with competing worlds: 32

The USB disk is in "dead timeout" and the "perenially reserved" setting from the Host Profile had no effect.

However, I was able to prove that the USB device worked fine, at least for a while:

esxcli storage core device stats get | less

   mpx.vmhba32:C0:T0:L0

   Device: mpx.vmhba32:C0:T0:L0

   Successful Commands: 471

   Blocks Read: 7455

   Blocks Written: 0

   Read Operations: 309

   Write Operations: 0

   Reserve Operations: 0

   Reservation Conflicts: 0

   Failed Commands: 85

   Failed Blocks Read: 0

   Failed Blocks Written: 0

   Failed Read Operations: 0

   Failed Write Operations: 0

   Failed Reserve Operations: 0

Looking at the VM kernel log, see this:

vmkernel.log | less

2014-09-05T19:03:50.242Z cpu9:39820 opID=9efa2c3c)World: 14296: VC opID hostd-8b72 maps to vmkernel opID 9efa2c3c

2014-09-05T19:03:55.446Z cpu9:39820 opID=252dfa49)World: 14296: VC opID 58F84D94-00000680-7b-4e maps to vmkernel opID 252dfa49

2014-09-05T19:03:55.475Z cpu9:33047 opID=252dfa49)ScsiPath: 5151: DeletePath : adapter=vmhba32, channel=0, target=0, lun=0

2014-09-05T19:03:55.475Z cpu9:33047 opID=252dfa49)ScsiDevice: 3612: Can't unregister device mpx.vmhba32:C0:T0:L0 because it is in use.  OpenCount:1 InternalOpenCount:0 RefCount:2 FilterCount:0

2014-09-05T19:03:55.475Z cpu9:33047 opID=252dfa49)ScsiDevice: 3623: Device mpx.vmhba32:C0:T0:L0 was in use by worldId 0

2014-09-05T19:03:55.475Z cpu9:33047 opID=252dfa49)WARNING: NMP: nmpUnclaimPath:1502: NMP device "mpx.vmhba32:C0:T0:L0" quiesce state change failed: Busy

2014-09-05T19:03:55.475Z cpu9:33047 opID=252dfa49)WARNING: ScsiPath: 3708: Path vmhba32:C0:T0:L0 is being removed

2014-09-05T19:03:55.475Z cpu9:33047 opID=252dfa49)WARNING: ScsiPath: 3914: Failed to issue command 0x0 (cmdSN 0x0) on path vmhba32:C0:T0:L0: No connection

2014-09-05T19:03:55.475Z cpu9:33047 opID=252dfa49)ScsiPath: 4874: Path vmhba32:C0:T0:L0 could not be unclaimed from plugin, status Busy. Continue path unclaiming

2014-09-05T19:03:55.475Z cpu9:33047 opID=252dfa49)WARNING: ScsiScan: 1758: Could not delete path vmhba32:C0:T0:L0

I confirmed that mpx.vmhba32:C0:T0:L0 is truly unavailable by trying to read from it.

/dev/disks # ls -l ./mpx*

-rw-------    1 root     root     4009754624 Sep  5 19:42 ./mpx.vmhba32:C0:T0:L0

-rw-------    1 root     root       4161536 Sep  5 19:42 ./mpx.vmhba32:C0:T0:L0:1

-rw-------    1 root     root     262127616 Sep  5 19:42 ./mpx.vmhba32:C0:T0:L0:5

-rw-------    1 root     root     262127616 Sep  5 19:42 ./mpx.vmhba32:C0:T0:L0:6

-rw-------    1 root     root     115326976 Sep  5 19:42 ./mpx.vmhba32:C0:T0:L0:7

-rw-------    1 root     root     299876352 Sep  5 19:42 ./mpx.vmhba32:C0:T0:L0:8

/dev/disks # cat  ./mpx.vmhba32\:C0\:T0\:L0\:1

cat: read error: Input/output error

(yes, I know I would get a bunch of garbage, but no error)

So it appears that the USB stick is recognized, partially configured (partitions are written), but fails at some point before ESXi is able to mount it to write the cache to it.

I was hoping to reset the USB bus by disabling and re-enabling the ESXi kernel USB and USB-storage modules, but that didn't seem to work - it was a bit of a long shot.

esxcli system module set --enabled=false  --module=usb

esxcli system module set --enabled=true  --module=usb

esxcli system module set --enabled=false  --module=usb-storage

esxcli system module set --enabled=true  --module=usb-storage

Has anyone else seen this behaviour??  Any help would be greatly appreciated.

Thanks,

Michal

Hello,

How to view real-time CPU frequency inside guest OS?

I tried to look in Task Manager and CPU-Z, but always see 2.2 GHz

host: ESXi 6.7

CPU: Xeon Silver 4114 (base 2.2/ turbo 3.0 GHz)

guest: Windows Server 2016

Hi all,

So I am on VMWare ESXI 6.7 running a vm host. I set a static IP on the ESXI host of 192.168.1.254 (prior it had a 192.168.1.14 DHCP address) and it accepts it. When I go login via the web interface via 192.168.1.254 it works. However when I try to open a console to a VM (browser console) via the web interface I am unable to connect because the web interface is still using 192.168.1.14. I can tell its trying to do this because If I try to connect via VMRC, the VMRC app will time out trying to connect to 192.168.1.14.  So something in the web interface is still using the old ip address of 192.168.1.14 for some reason. In the top right corner of the web interface after logging in it also says root@192.168.1.14 which is incorrect.

I tried many things:

Rebooting the ESXI host.

Clearing Cookies on my browser.

Rebooting my only VM.

None of this has worked, and I can tell that vmk0 has the correct ip 192.168.1.254 (static) assigned. This seems like a bug but how can this be fixed?

Hello,

I have host ESXi 6.7, RAID controller PERC H730P, RAID10 volume on SATA SSD

When i try Mark the disk as a flash disk, i get error:

Cannot change the host configuration

I need to check performance issues in a VMware vSphere 5.5 infrastructure based on 4 ESXi 5.5 hosts.

Some specialists say that VMware suggests as a general rule to avoid using more that 4 virtual cores for each physical core.

Is such 4:1 relationship true?

Is it documented anywhere?

Regards

marius

Hello vmware community!

We want to use two monitor for a virtual machine (guest SO: windows 2000 server) under ESXi 6.5 (with vCenter server) with remote console, but not working. The system sais that not possible with ESXi version..... What version of vmware support two monitor with remote console?.

In remote console, I can see the option, but when I do click in option "cycle multiple monitors", the system says....

any body know whitch version of vmware support this function?

Many thanks!!

Dear All,

We have two DL 380P Gen8 server connected with MSA P2000 G3 FC storage, currently we are running Esxi 5.5 U2. The Esxi OS is installed on local disks of DL 380P gen8 and in MSA we have created LUNS which are presented to vmware for datastores and virtual machines are running on them.

We are eligible to upgrade our product license to vSphere 6.0 and I have checked DL380p Gen 8 support it, that means we can upgrade OS of Esxi on local disk of servers from current 5.5. to 6.0 U2, however my concern is for storage, this upgrade will have any effect or not, since storage is only for presenting data store, if Esxi is 5.5 or 6 this makes any difference?

Please help and guide. I hope I am clear.

regards,
Wajeeh

I would like to maintain a single ESXi ISO file that I can use to install on different Server types; for example, I have servers with 2 different vendors' RAID drivers. I don't want to have to find and install the correct ISO file, but maintain one which has the drivers for both server types.

I'm thinking I could create a single ISO (using PowerCLI) which would include the VIBs for both vendors.  I'm hoping that the hypervisor would recognize and install the correct VIB.

If I get a chance, I hope to try it out next week, but figured I would see if anyone had tried anything like it

Thanks,

Maureen

Hi all,

I have an ESXI host with one physical NIC which is attached a a vSwitch with 4 port groups, 1 which is native the other 3 are VLAN tagged.

One guest has 4 NICs configured fom the port groups above (minus 1 ) and another from a 2nd vSwitch (no phtsical NIC). It is currently working as expected. However, when I add an additional NIC from a VLAN tagged port group to the guest, it is as if the VLAN associated with those port groups are swapped or random.

The indication of this is:

- The DHCP issued address for one NIC is from a network connected to another NIC

- A series of ARP errors on the guest

If I remove the added NIC, the issue is rolled back.

I have an unusual problem, that is fairly hard to chase down and am wondering if it may be a change in ESXi behavior.

Environment

Have a series of 2 NIC ESXi servers that have been in use since ESXi 5.5 and upgraded all the way to ESXi 6.7 (free license)

Have a single managed switch (HP Procurve/Aruba 2350) with HP trunks to both NIC's on each server

Have 4 iSCSI subnets with no routing

iSCSI storage provided via a NexentaStor box with 4 NIC (no aggregation to switch)

each NIC has one IP on each iSCSI subnet via VLAN, for a total 16 IP's presented

NexentaStor iSCSI server presents a VAAI compatible LUN with 4 targets, each individual target with 4 IP's from the same iSCSI subnet

ESXi uses single vSwitch with NIC teaming with trunk

under vSwitch, have 4 iSCSI portgroups for each ISCSI VLAN, each iSCSI portgroup has a single vmknic

each iSCSI portgroup has override and use only one pNIC with other unused (alternate which pNIC is active and unused per portgroup)

use iSCSI portbinding on iSCSI vmk (all available for portbinding)

use round robin path selection, all active (all 16 paths)

previous behavior under ESXi 6.5 was mostly balanced reads and balanced writes. This is because while outbound writes are evenly split due to round robin path selection between 4 vmk (and thus evenly split between between 2 pNIC), return traffic must go through switch trunk load balance algorithm. Thus it's blind luck which iSCSI session will go through which trunk port and on to which pNIC. Basic statistics says I have better odds of more even balance if the number of TCP sessions is higher (think bell curve of possibilities). With only two targets with one IP each, worst case is all traffic goes to one pNIC. So the temporary solution was increasing the target IP count as the odds of all 16 sessions being on one pNIC is low. Note that while the distribution of traffic from switch to ESXi is due to switch internal load balance algorithm, traffic from NexentaStor to the switch was evenly balanced, suggesting that reads are being commanded evenly. Since the iSCSI server had 4 NIC's, it was thought to be better to balance traffic across all 4 NIC's, so need target/target IP's in multiples of 4.

after the ESXi 6.7 upgrade though, something changed and now reads are coming almost exclusively from a single NexentaStor NIC, though the switch seems to evenly distribute the read traffic from the switch to the ESXi servers. Which NIC is being almost exclusively read from can change after rebooting the ESXi server.  The NexentaStor iSCSI server had no changes during the ESXi upgrade.

my guess is some weird behavior due to the large number of targets and target IP, and target IP distribution, and carryover from the upgrade. Each LUN has 4 targets, each target has 4 IP's in the same subnet. Each NexentaStor NIC has the same final octet in each subnet.

So

NIC 1 has addresses x.x.A.11 x.x.B.11 x.x.C.11 x.x.D.11

NIC 2 has addresses x.x.A.12 x.x.B.12 x.x.C.12 x.x.D.12

NIC 3 has addresses x.x.A.13 x.x.B.13 x.x.C.13 x.x.D.13

NIC 4 has addresses x.x.A.14 x.x.B.14 x.x.C.14 x.x.D.14

4 targets

target W (x.x.A.1-4)

target X (x.x.B.1-4)

target Y (x.x.C.1-4)

target Z (x.x.D.1-4)

There is also the somewhat changed guidance from VMware regarding iSCSI portbinding for 6.7

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.storage.doc/GUID-BC516B24-7EAB-4ADA-819A-10DC496DEE9B.html

Looking at the current iSCSI settings, the host client shows weird behavior.

Clicking the "Software iSCSI" button under Storage -> Adapters shows it sorta thinks port binding is active as it lists the 4 port bindings previosuly used under ESXi 6.5, however if I select the iSCSI software adapter, the "Configure iSCSI" button becomes un-greyed out and if I click it, it shows the iSCSI configuration details but no port bindings (and can't add port bindings).

I confirmed via ESXTOP that the vmk are evenly reading, but I can't see which path they are selecting or the load per path. Based on what the switch is showing though, it suggests the possibility that ESXi is reading from 4 targets but only the (first?) IP of each target, which ends up being all the same iSCSI server NIC.

Since I am a free license user, I don't have a vCenter to keep an eye on things and get more detailed information. The host client is sorely lacking, as you can't even see network activity by vmk (at least the old C# client showed that). While the host client won't let you even select a path selection policy, I did confirm via CLI that it was still round robin, and that it thinks all paths are active. Since the NexentaStor iSCSI server feeds other ESXi servers of lesser version, I would prefer to not make any changes that only work well for ESXi 6.7 but not 6.5 or 5.5 if I can avoid it.

There was a mention somewhere that having more than 32 paths causes weird behavior, which can occur if I am using 2 or more LUN's from the iSCSi server (previously the C# client under an early version of 6.5 showed a boatload of paths). The VMware guidance might suggest that the 1:1 port binding means for 2 pNIC vSwitches, you can only add 2 vmk correctly for port binding, and adding more than that might lead to undefined behavior?

So, anybody have an idea what the hell is wrong? One possible solution might be adjusting the vmk count and redefining the iSCSI target, but with only 2 pNIC's but 4 NIC's on the storage server, what would be the correct/better target/target IP mapping and vmk count?

Hi, this issue started 2 days ago when I attempted to update from 6.5.0.20100 to "VC-6.5.0U2b-Appliance-FP" (6.5.0.21000 Build Number 8815520) in the vSphere Appliance Management. It stopped at 60% and prompted with an error code about "not being able to contact the server...". I then restarted the Appliance and from there it went down hill.

I figured out if I ran the command "Service vami-lighttp start" and  it came up again, but after some time I couldn't authenticate etc.. seems as some services aren't running.

I did find this discussion in a different thread and noticed it was the exact same issue I have -> vCenter 6.5 - vcenter appliance stops working out of the blue, AGAIN!!

I will post the same output and hopefully figure this out. (I did notice those 4 commands, but haven't used those yet since I don't quite understand what they do)

service-control --status
Running:
 applmgmt lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-psc-client vmware-rhttpproxy vmware-sca vmware-sps vmware-sts-idmd vmware-stsd vmware-updatemgr vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui
Stopped:
 vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-rbd-watchdog vmware-statsmonitor vmware-vcha

service-control --start vmware-vpxd-svcs
Perform start operation. vmon_profile=None, svc_names=['vmware-vpxd-svcs'], include_coreossvcs=False, include_leafossvcs=False
2018-07-18T17:45:49.534Z   Service vpxd-svcs state STARTED
Successfully started service vpxd-svcs

systemctl list-unit-files | grep vmware
vmware-bigsister.service               static
vmware-cis-license.service             masked
vmware-cm.service                      masked
vmware-content-library.service         masked
vmware-eam.service                     masked
vmware-firewall.service                enabled
vmware-imagebuilder.service            masked
vmware-mbcs.service                    masked
vmware-netdump.service                 masked
vmware-perfcharts.service              masked
vmware-pschealth.service               masked
vmware-rbd-watchdog.service            masked
vmware-rhttpproxy.service              masked
vmware-sca.service                     masked
vmware-sps.service                     masked
vmware-statsmonitor.service            masked
vmware-updatemgr.service               masked
vmware-vapi.service                    masked
vmware-vcha.service                    masked
vmware-vmon.service                    enabled
vmware-vmonapi.service                 masked
vmware-vpostgres.service               masked
vmware-vpxd-svcs.service               masked
vmware-vpxd.service                    masked
vmware-vsan-health.service             masked
vmware-vsm.service                     masked
vmware-bigsister.timer                 disabled

After running the "service-control --start vmware-vpxd-svcs" the Appliance Manager came up again.

systemctl list-unit-files | grep masked
applmgmt.service                       masked
vmcam.service                          masked
vmware-cis-license.service             masked
vmware-cm.service                      masked
vmware-content-library.service         masked
vmware-eam.service                     masked
vmware-imagebuilder.service            masked
vmware-mbcs.service                    masked
vmware-netdump.service                 masked
vmware-perfcharts.service              masked
vmware-pschealth.service               masked
vmware-rbd-watchdog.service            masked
vmware-rhttpproxy.service              masked
vmware-sca.service                     masked
vmware-sps.service                     masked
vmware-statsmonitor.service            masked
vmware-updatemgr.service               masked
vmware-vapi.service                    masked
vmware-vcha.service                    masked
vmware-vmonapi.service                 masked
vmware-vpostgres.service               masked
vmware-vpxd-svcs.service               masked
vmware-vpxd.service                    masked
vmware-vsan-health.service             masked
vmware-vsm.service                     masked
vsphere-client.service                 masked
vsphere-ui.service                     masked
ctrl-alt-del.target                    masked

/etc/systemd/system ]# ls -lisa
total 108
180710 4 drwxr-xr-x 24 root root 4096 Jul 17 17:01 .
180226 4 drwxr-xr-x  7 root root 4096 May 31 15:04 ..
183069 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 applmgmt.service -> /dev/null
183110 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 applmgmt.service.d
182577 0 lrwxrwxrwx  1 root root   40 Feb  3  2017 default.target -> /usr/lib/systemd/system/runlevel3.target
180712 4 drwxr-xr-x  2 root root 4096 May 31 15:03 getty.target.wants
183131 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 halt.target.wants
188806 4 drwxr-xr-x  2 root root 4096 Feb  3  2017 local-fs.target.wants
182743 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 lwsmd.service.d
180714 4 drwxr-xr-x  2 root root 4096 Jul 17 19:58 multi-user.target.wants
180718 4 drwxr-xr-x  2 root root 4096 May 31 15:03 network-online.target.wants
183133 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 poweroff.target.wants
183129 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 reboot.target.wants
182530 4 -rw-r--r--  1 root root  268 Jun  7  2016 sendmail.service
183127 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 shutdown.target.wants
182483 4 -rw-r--r--  1 root root  476 Mar  1 19:03 snmpd.service
180720 4 drwxr-xr-x  2 root root 4096 May 31 15:03 sockets.target.wants
180722 4 drwxr-xr-x  2 root root 4096 May 31 15:03 sysinit.target.wants
182042 0 lrwxrwxrwx  1 root root   39 Feb  3  2017 syslog.service -> /usr/lib/systemd/system/rsyslog.service
182708 4 -r-xr-xr-x  1 root root  470 Jun 13 09:50 vcha-hacheck.service
232102 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmafdd.service.d
320650 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmcad.service.d
183086 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmcam.service -> /dev/null
182854 4 drwxr-xr-x  2 root root 4096 May  7 12:12 vmcam.service.d
320579 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmdird.service.d
320789 4 drwxr-xr-x  2 root root 4096 May  7 12:12 vmdnsd.service.d
182138 4 drwxr-xr-x  2 root root 4096 Feb  3  2017 vmtoolsd.service.requires
182905 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-cis-license.service -> /dev/null
182904 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-cm.service -> /dev/null
183082 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-content-library.service -> /dev/null
183083 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-eam.service -> /dev/null
183104 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-imagebuilder.service -> /dev/null
183076 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-mbcs.service -> /dev/null
183072 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-netdump.service -> /dev/null
183105 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-perfcharts.service -> /dev/null
182906 4 drwxr-xr-x  2 root root 4096 Jul 17 23:18 vmware-psc-client.service.d
183073 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-pschealth.service -> /dev/null
183084 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-rbd-watchdog.service -> /dev/null
182903 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-rhttpproxy.service -> /dev/null
182916 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-sca.service -> /dev/null
183087 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-sps.service -> /dev/null
183074 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-statsmonitor.service -> /dev/null
183118 4 drwxr-xr-x  2 root root 4096 Jul 17 23:18 vmware-stsd.service.d
183122 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmware-sts-idmd.service.d
183093 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-updatemgr.service -> /dev/null
183060 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vapi.service -> /dev/null
182878 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vcha.service -> /dev/null
183067 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vmonapi.service -> /dev/null
183114 4 drwxr-xr-x  2 root root 4096 Jul 17 23:18 vmware-vmon.service.d
183075 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vpostgres.service -> /dev/null
183081 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vpxd.service -> /dev/null
182872 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vpxd-svcs.service -> /dev/null
183094 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vsan-health.service -> /dev/null
183103 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vsm.service -> /dev/null
183077 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vsphere-client.service -> /dev/null
183080 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vsphere-ui.service -> /dev/null

Dear All

I have a problem while upgrading from ESXi 6.5 to 6.7,

I choosed the ISO method to upgrade, burn it on usb and boot it, it recognized the installation of 6.5 and got the option to upgrade at 19% there was an error, and the whole installation process restarted and , but at 2nd time it didn't offer the upgrade option, so as if the first time it changed something about the installation , the configuration of the original 6.5 is still the same, nothing changed I can work with it as before, only I don't know how to get the upgrade, since it will now give me a new installation, any Idea?

can I do a configuration restore of 6.5 on a 6.7?

or any Idea?

many thanks

Jordi

Hi Folks,

I faced a serious issue of resource crunch in data store recently, although I figured out that it was a snapshot that had overgrown and resolved it.

But I wanted to get the historical logs of DataStore events wherein I could find the exact point in time of the threshold breach and how fast did its size grow.

Here is the vsphere security hardening guide.

can any one explain these three columns in details?

hardening is true and why

site specific settings is true and why false

audit setting is false and why false.

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/files/xls/vmware-6-5-update-1-security-configuration-guide…

I am putting together a Dell R720 SFF with an H710p. Only planning on running 2x VMS right now; server 2102 R2 for DC/file shares and a secondary server for backup DC. Will be installing ESXi on dual SD cards.

I originally had thought to use 2x 500GB SSD's in Raid 1 for 1 data store to host the guest VM's. Then install 4x2TB HDD's in Raid 10 as a second data store. The VM's would use the HDD array fro file storage, roaming user profile storage.

My question is if that is feasible? I asked previously on spice works but never received an answer to my last posts. It was suggested to only have one data store. But price becomes an issue.

I could put 4x500GB consumer ssd's in Raid 10 and 2tb would suffice for now. Another option would be 8x1TB SAS HDD's in Raid 10 to get the desired 4TB's.

Thank you for the help.

Hi All

I installed custom certs in our vSphere 6.5 environment. There are 2 sites in enhanced link mode vCenter and PSC in each both with a custom cert from our local CA of SHA1 and connected SRM.

I need to upgrade these certs to SHA256. I cant find much info on the internet about it, does anyone have any experience with this and steps taken?

Thank you so much for any info

On some ESXi servers I see an activity peak (CPU at 100%) at some given times, i.e. 11:00, 14:00, 17:00 even during the week-end.

I can't exclude some VM related issues, but I need to perform a a more in-depth analysis at the host side.

• Is there any host related task that can cause a CPU overload, i.e. any internal housekeeping task?
• If so, how can I monitor it?
• How can I identify any single guest VM causing the CPU overload?
• How can I trace the performance issues occurring during the week-end in order to analyze them on Monday?

Is there any best practice I can follow to troubleshoot the performance issue?

Regards

marius

Hello VMware community. I use VMware ESXI free 6.5.

Yestarday I unfortunately try to perform VMs backup with one of the free scripts, after some error I decided to reboot ESXI. After this operation all .vmx and machine.vmdk files dissapered.

I have only machine-flat.vmdk and machine-delta.vmdk. As I understand delta file is growing snapshot over flat?  I've successfully recovered .vmdk file from 'flat' (and .vmx after that) with help from this topic, but it is raw system image(without my data). I think that I should merge flat and delta in some way, after that generate new machine.vdmk but I can't find if it is possible and how to do that.

I will be grateful for any help.

Hey Guys

Little Background: Existing backup server is Backup exec 2010 R3 and configured on B200 M3 blade in UCS 5108 chassis. We are moving away from from legacy backup system to Veeam and would like to preserve the ability to do tape restores using backup exec. So, I am trying to virtualize the backup exec server.

I am trying to connect Quantum scaler I40 to my ESXi 5.1 host connected via FC. I am not very good with drawing yet I have tried best to present my setup. There are 2 drives in Tape library HP and IBM. After zoning ESXi host with tape library, both tape drives show upon scanning HBA. However, HBA is showing one dead path and also the quantum library is not able to discover these drives.

fc.20100025b50000df:20100025b50a007f-fc.500308c38d7d6000:500308c38d7d6001-
  UID: fc.20100025b50000df:20100025b50a007f-fc.500308c38d7d6000:500308c38d7d600                                                                               1-
  Runtime Name: vmhba3:C0:T0:L1
  Device: No associated device
  Device Display Name: No associated device
  Adapter: vmhba3
  Channel: 0
  Target: 0
  LUN: 1
  Plugin: (unclaimed)
  State: dead
  Transport: fc
  Adapter Identifier: fc.20100025b50000df:20100025b50a007f
  Target Identifier: fc.500308c38d7d6000:500308c38d7d6001
  Adapter Transport Details: Unavailable or path is unclaimed
  Target Transport Details: Unavailable or path is unclaimed
  Maximum IO Size: 33553920

Requesting all you experts out there for your advise. I am really stuck