Hi,

vSphere 6.5

I have a pretty flat network where VM, management, and the NAS hosting NFS datastores are all on the same subnet. Currently I have in ESXi:

vmk0 --> management

vmk1 --> NFS storage

The reason I have two vmkernel interfaces is to separate backup traffic (which should go through the management interface) from the NFS storage. I only have 1g nics so separating them to reduce the chance backup traffic impacting storage traffic. However, I notice since they are on the same subnet and use the same TCP/IP Stack in Vmware, the TCP/IP Stack has route table:

Network     Prefix     Gateway     Device

10.60.0.0     17     0.0.0.0     vmk0

0.0.0.0     0     10.60.0.1     vmk0

Because the NFS storage backing the datastore is also on the same subnet, it will always use vmk0 instead of vmk1 for NFS storage traffic which is not what I want. Is there a way to work around this? Can I create two TCP/IP stacks for the same subnet? If so, how do I associate a vmkernel interface to a specific TCP/IP Stack?

Thanks,

I was wondering if there is any script or similiar available to schedule VCSA backups to a FTP server.

I tried multiple stuff but none seems to be working . Adapted a Bash script but it doesn't give me output as below

VMware vSphere 6.5 Documentation Library

Tried Backup vCenter Server Appliance (VCSA) 6.5 Using PowerShell – VCDX56 

But https://www.brianjgraf.com/2016/11/18/vsphere-6-5-automate-vcsa-backup/  the link at end on guthub is missing . Page missing...

Is there a way to schedule these backups for VCSA.

Hello.

I have upgrade to VCSA 6.5 and I'm using it's Update Manager to try and "Scan for Updates" and checkmark in Upgrades. I have attached the baseline a Cluster level.

When doing so for an already upgraded Host I get the error: Cannot deplay upgrade agent on Host.

When doing so for a not yet upgraded Host I get the error: VMware vSphere Update Manager has an unknown error. Check the network connectivity and logs fiies for details.

The list shows 2 Compliant, 3 Non-Compliant and 3 Unknown.

One of our Hosts are Out Cold and awaiting a systemboard change. NSX is installed but only for use for Guest Introspection and McAfee MOVE AV. Both show Installation Status Failed. The one Host is probably the problem there.

If I de-attached the baseline from Cluster level and attach it to a yet to be upgrade Host I get "VMware vSphere Update Manager has an unknown error. Check the network connectivity and logs fiies for details."

Scan entity stops at 17%, I see no errors in Event Console

Repeat this for the upgraded server I get: "Cannot deploy host upgrade agent. Check the network connectivity and logs of host agent and vpxa for details." Scan Entity stops after two seconds.

Any ideas?

Best Regards

Peter

I've created a new baseline for 6.5 critical host patches and specifically excluded ESXi 6.5 Complete Update 2.  When I click the Remediate... button and get to the Patches and extensions section it doesn't list Update 2.  But after remediation is done Update 2 is installed on the host.

Am I doing something that is causing 6.5 U2 to be installed even thought I explicitly excluded the patch?

Hello!

During an upgrade from ESXi 6.0 to ESXi 6.5 the Host is rebooted but never come back up due the a hardware error.

After replacing the faulty parts the Hypervisor stops at loading /tboot.b00 with the error Fatal Error 3 Invalid Parameter.

Shift-E gives me only one boot choice which is the one that does not work.

Shift-O gives an no-auto-partition-boot-uuid= some-long-number and that leads to the same error.

Can I find different UUID or how do I proceed from here?

Right now I'm booting the Host from the ISO file containing the ESXi upgrade I used over Update Manager until this Host.

Best Regards

Peter

I have two Vcenter Servers, DEV and STAGE.  Both Vcenter Servers control different hosts and VMs, but all hosts attach to a common SAN.  I am able to create Virtual Volumes (VVOLs) on each server, but I am unable to mount a VVOL on both Vcenter Servers.  Is this a limitation of Vcenter Server?  If not, how can I do it?

I haven't seen it when looking, but wanted to check with the community about this.

I've been trying to solve a problem and trying to do it without creating a shell/proxy VM to test this.

I want to be able to have vCenter tell me which ESXi host in a DRS + HA Enabled cluster would be

e.g. I give the API call a VM Specification (all CPU/Memory/Disk/Network requirements), and the API call would return back with the prediction at that point in time.

When DRS is set to manual mode and you power up a VM, there will be a prompt with what hosts could power on the VM.  This is effectively what I want, but I don't want to actually create a proxy VM to check this.

I could do some automation, but the idea is that I want to create a net new VM using the same spec ... but create it on the host it would power on to.

Hi all,

I am configuring PSC HA in a 6.5 environment.

All appliances are at the 6.5 express patch 3 version level. (I copied and replaced the updateSSOConfig.py and UpdateLsEndpoint.py scripts from a GA version of a PSC due to the known issue)

What I have is the following:
vCenter 6.5 connected to an external temporary PSC

2 extra PSCs in the same SSO domain and site as the temporary PSC

(all 3 PSCs are in the same SSO domain and site)

NLB configured in NSX.

I am trying to configure these 2 extra PSCs in a NLB to be able to repoint the vCenter from the temporary PSC to the NLB PSCs.

I have created the certificate and imported it to both extra PSCs.

Then I have successfully run the "python updateSSOConfig.py --lb-fqdn=xxx.xxx.xxx" command on both PSCs.

However when I run the "python UpdateLsEndpoint.py --lb-fqdn=nlb_fqdn --user=administrator@vsphere.local" command I am getting an error message and it doesn´t complete correctly.

The endpoints don´t update.

The error message is attached.

I see the following in the error message:

Invalid value of command option ´--site´, value:´ ´

That implies to me that the command is expecting a different site-name than the current site-name i.e. the site-name cannot be null?

If I try adding the --site parameter to the command it fails saying that that is not how to run the command correctly.

Has anyone seen this message before or do you know what is happening here?

I tested everything in a lab however, I used Netscaler in my lab and also I only had the 2 PSCs to play with (no vCenter connected to a temp PSC).

Anybody??

Regards

Mark

Hi everyone,

I was wondering if it's possible to link already deployed Vcenter VCSA with Embedded PSC as Embedded link mode is now supported on 6.5u2.

All I could found mention the link process at the deployment of the VCSA, but nothing about already deployed appliances.

Joining a vCenter Embedded Linked Mode Domain

Thanks in advance,

Best regards.

Is there a way to "stage" a resource change on a VM so that it will apply the next time the VM is rebooted?

I need to increase the memory on numerous Windows VMs (hot-add is not enabled), but the only downtime opportunity is during automated monthly patching/reboot.

I thought it might be possible to modify the "memSize" parameter in the .vmdk file, and then the change would be picked up when the machine is rebooted.

               I believe this script is from LucD, he always has some amazing scripts. I am new to powercli ise and have not had just about any training or skills in scripting. I am attempting to gather any metrics using get-stat for all available entries and getting ESXtop statistic points. Here is the script i found, I just need to be able to print this to a .csv. Please help!

Situation is this...

vSphere 6

I have about a dozen VMs that fail at 20% when trying to vmotion. VMware Tools is up to date. I have three hosts in a cluster and the problem is not specific to any one host. I have cloned these VMs and the issues persists on the clones suggesting the problem is with a VM config or possibly within the guest OS. Most of the VMs on these host are not experiencing any issues during vmotion. The physical network is good.

Hey folks,

I can't seem to unregister an Hitachi VASA storage provider.   We're using VCenter Appliance version 6.5 (build 8667236).

I've tried a sync, rescan, unregister... but with no success.

Here's what I see in the logs (/var/log/vmware/vmware-sps/sps.log):

2018-06-14T12:36:30.439-04:00 [pool-22-thread-5] DEBUG opId=StorageProvidersViewMediator-apply-17929-ngc:70002804 com.vmware.vim.sms.provider.vasa.VasaProviderImpl - Received API Call: sync

2018-06-14T12:36:30.439-04:00 [pool-22-thread-5] INFO  opId=StorageProvidersViewMediator-apply-17929-ngc:70002804 com.vmware.vim.sms.provider.vasa.VasaProviderImpl - VasaProviderImpl.scheduleSyncTask for vpId=49a83597-d674-4097-b718-85de18b9b8ab, arrayId=null and syncType=PROVIDER

2018-06-14T12:36:30.439-04:00 [pool-22-thread-5] DEBUG opId=StorageProvidersViewMediator-apply-17929-ngc:70002804 com.vmware.vim.sms.provider.vasa.VasaProviderImpl - Validating VP 49a83597-d674-4097-b718-85de18b9b8ab schemas

2018-06-14T12:36:30.439-04:00 [pool-22-thread-5] ERROR opId=StorageProvidersViewMediator-apply-17929-ngc:70002804 com.vmware.vim.sms.policy.SyncPolicyManager - Provider 49a83597-d674-4097-b718-85de18b9b8ab is not active!!!

2018-06-14T12:36:30.439-04:00 [pool-22-thread-5] ERROR opId=StorageProvidersViewMediator-apply-17929-ngc:70002804 com.vmware.sps.vp.VasaProviderValidatorImpl - Unable to retrieve capability schemas from VP 49a83597-d674-4097-b718-85de18b9b8ab

com.vmware.vim.sms.fault.ProviderNotActiveException: Provider 49a83597-d674-4097-b718-85de18b9b8ab is not active!!!

at com.vmware.vim.sms.policy.SyncPolicyManager.getProviderAndCheckIsActive(SyncPolicyManager.java:126)

at com.vmware.vim.sms.policy.SyncPolicyManager.queryCapabilitySchema(SyncPolicyManager.java:86)

at com.vmware.vim.sms.policy.PolicyManagerImpl.queryCapabilitySchema(PolicyManagerImpl.java:270)

at com.vmware.sps.vp.VasaProviderValidatorImpl.retrieveCapabilitySchemas(VasaProviderValidatorImpl.java:90)

at com.vmware.sps.vp.VasaProviderValidatorImpl.validate(VasaProviderValidatorImpl.java:67)

at com.vmware.vim.sms.provider.vasa.validation.VasaProviderValidationManagerImpl.validateVasaProvider(VasaProviderValidationManagerImpl.java:87)

at com.vmware.vim.sms.provider.vasa.VasaProviderImpl.validateSchemas(VasaProviderImpl.java:1883)

at com.vmware.vim.sms.provider.vasa.VasaProviderImpl.scheduleSyncTask(VasaProviderImpl.java:1924)

at com.vmware.vim.sms.provider.vasa.VasaProviderImpl.sync(VasaProviderImpl.java:1700)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at com.vmware.vim.vmomi.server.impl.InvocationTask.run(InvocationTask.java:65)

at com.vmware.vim.vmomi.server.common.impl.RunnableWrapper$1.run(RunnableWrapper.java:47)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

2018-06-14T12:36:30.439-04:00 [pool-22-thread-5] ERROR opId=StorageProvidersViewMediator-apply-17929-ngc:70002804 com.vmware.vim.sms.provider.vasa.VasaProviderImpl - Validation for VP 49a83597-d674-4097-b718-85de18b9b8ab failed with error com.vmware.vim.sms.fault.ProviderValidationException: com.vmware.vim.sms.fault.ProviderNotActiveException: Provider 49a83597-d674-4097-b718-85de18b9b8ab is not active!!!, setting status to syncError and also re-scheduling the timer sync

2018-06-14T12:36:30.440-04:00 [pool-22-thread-5] DEBUG opId=StorageProvidersViewMediator-apply-17929-ngc:70002804 com.vmware.vim.sms.provider.vasa.VasaProviderImpl - [setStatus] For provider https://132.207.180.48:50001/version.xml, new status is equal to the current status : syncError

2018-06-14T12:36:30.545-04:00 [pool-24-thread-6] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17930-ngc:70002805 com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...

2018-06-14T12:36:30.552-04:00 [pool-22-thread-6] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17930-ngc:70002805 com.vmware.vim.sms.StorageManagerImpl - [queryArray] Received API Call: queryArray

2018-06-14T12:36:30.552-04:00 [pool-22-thread-6] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17930-ngc:70002805 com.vmware.vim.sms.query.QueryManagerImpl - [getStorageArrays] Fetching for providerIds null

2018-06-14T12:36:30.562-04:00 [pool-24-thread-7] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17931-ngc:70002805 com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...

2018-06-14T12:36:30.568-04:00 [pool-22-thread-7] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17931-ngc:70002805 com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STARTED: queryProvider

2018-06-14T12:36:30.568-04:00 [pool-22-thread-7] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17931-ngc:70002805 com.vmware.vim.sms.provider.ProviderCache - [queryProvider] Returning result of size - 4

2018-06-14T12:36:30.569-04:00 [pool-22-thread-7] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17931-ngc:70002805 com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMER STOPPED: queryProvider, TIME TAKEN: 1 ms.

2018-06-14T12:36:30.579-04:00 [pool-24-thread-8] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17932-ngc:70002805 com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...

2018-06-14T12:36:30.588-04:00 [pool-24-thread-9] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17933-ngc:70002805 com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...

2018-06-14T12:36:30.598-04:00 [pool-24-thread-10] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17934-ngc:70002805 com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...

2018-06-14T12:36:30.608-04:00 [pool-24-thread-1] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-1311:SmsPropertyProvider:200127:5198-17935-ngc:70002805 com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...

2018-06-14T12:36:55.698-04:00 [pool-13-thread-1] DEBUG opId=sps-SHPoller-992235-84 com.vmware.vim.sms.health.ServiceHealthPoller - Certificate expiry check succeeded!

Anyone have any ideas?  I opened a support case with VMWare... but almost days later, I've not yet spoken to a storage engineer.

Thank You!

Hi people,

I have implemented vCenter Server 6 WEB appliance and tried to import self signed SSL Machine certificate, in order to access on vCenter web interface using that certificate for HTTPS. Certificate was signed by Windows Server 2008 CA with template configured using these instrustions: Creating a Microsoft Certificate Authority Template for SSL certificate creation in vSphere 6.0 (2112009) | VMware KB. Also, I tried to import Comodo Trial Positive SSL certificate with same issue - couldn't import it.

I used the VMCA script for certificate management and also tried to import them manually using this procedure: vSphere 6.0 Documentation Center. In both cases, process crashed during vmware-vpxd service restarting process. VMCA script exited with rolling-back old certificates. After trying to manual replace certificates using commands certool and vecs-cli, I tried to start vmware-vpxd service using command service vmware-vpxd start. It produced following output:

virtual:~ # service vmware-vpxd start

vmware-vpxd: VC SSL Certificate does not exist, it will be generated by vpxd

Waiting for the embedded database to start up: success

Executing pre-startup scripts...

vmware-vpxd: Starting vpxd by administrative request.

success

vmware-vpxd: Waiting for vpxd to start listening for requests on 8089

Waiting for vpxd to initialize: ..........................................................Fri Jun 17 14:19:51 CEST 2016 Captured live core: /var/core/live_core.vpxd.7892.06-17-2016-14-19-51

[INFO] writing vpxd process dump retry:2 Time(Y-M-D H:M:S):2016-06-17 12:19:48

.Fri Jun 17 14:20:13 CEST 2016 Captured live core: /var/core/live_core.vpxd.7892.06-17-2016-14-20-13

[INFO] writing vpxd process dump retry:1 Time(Y-M-D H:M:S):2016-06-17 12:20:01

.failed

failed

vmware-vpxd: vpxd failed to initialize in time.

End of the /var/log/messages log file contains following:

2016-06-17T14:10:04.149368+02:00 virtual vmware-vpxd: VC SSL Certificate does not exist, it will be generated by vpxd

2016-06-17T14:10:04.158972+02:00 virtual root: RHTTPPROXY_HTTP_PORT = 80

2016-06-17T14:10:04.168334+02:00 virtual root: RHTTPPROXY_HTTPS_PORT = 443

2016-06-17T14:10:04.748884+02:00 virtual vmware-vpxd: Starting vpxd by administrative request.

2016-06-17T14:10:05.811146+02:00 virtual vmware-vpxd: Waiting for vpxd to start listening for requests on 8089

2016-06-17T14:10:11.068787+02:00 virtual kernel: [ 8262.100377] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=32356 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:10:41.045286+02:00 virtual kernel: [ 8292.062481] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=32645 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:11:11.392806+02:00 virtual kernel: [ 8322.396547] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=280 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:11:41.380687+02:00 virtual kernel: [ 8352.368229] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=593 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:12:11.508805+02:00 virtual kernel: [ 8382.477595] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=905 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:12:41.124668+02:00 virtual kernel: [ 8412.078362] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=1173 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:13:11.068788+02:00 virtual kernel: [ 8442.006593] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=1480 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:13:41.052756+02:00 virtual kernel: [ 8471.975786] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=1805 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:14:10.948713+02:00 virtual kernel: [ 8501.859385] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=2068 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:14:41.048793+02:00 virtual kernel: [ 8531.942485] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=2336 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:15:01.102632+02:00 virtual /usr/sbin/cron[6935]: (root) CMD ( /usr/sbin/iiad.sh >/dev/null 2>&1)

2016-06-17T14:15:10.976770+02:00 virtual kernel: [ 8561.853765] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=2622 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:15:41.220689+02:00 virtual kernel: [ 8592.076813] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:fc:4d:d4:d2:e5:a9:08:00 SRC=192.168.0.23 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=5745 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:16:10.988809+02:00 virtual kernel: [ 8621.836572] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:3c:97:0e:32:f7:1c:08:00 SRC=192.168.0.80 DST=192.168.0.255 LEN=229 TOS=0x00 PREC=0x00 TTL=128 ID=16631 PROTO=UDP SPT=138 DPT=138 LEN=209

2016-06-17T14:16:41.200814+02:00 virtual kernel: [ 8652.031163] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=3292 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:17:11.040715+02:00 virtual kernel: [ 8681.856944] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=3595 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:17:41.012706+02:00 virtual kernel: [ 8711.812066] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=3808 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:18:10.948718+02:00 virtual kernel: [ 8741.730820] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=4046 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:18:40.936986+02:00 virtual kernel: [ 8771.705858] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=4360 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:19:11.024790+02:00 virtual kernel: [ 8801.777535] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=4647 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:19:41.144770+02:00 virtual kernel: [ 8831.881485] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=5909 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:20:01.147104+02:00 virtual /usr/sbin/cron[13172]: (root) CMD ( /usr/sbin/iiad.sh >/dev/null 2>&1)

2016-06-17T14:20:01.153980+02:00 virtual /usr/sbin/cron[13171]: (root) CMD ([ -x /usr/lib64/sa/sa1 ] && exec /usr/lib64/sa/sa1 -S ALL 1 1)

2016-06-17T14:20:01.157092+02:00 virtual /usr/sbin/cron[13175]: (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)

2016-06-17T14:20:01.163979+02:00 virtual /usr/sbin/cron[13170]: (root) CMD ( test -x /usr/sbin/cloudvm_ram_size_periodic && /usr/sbin/cloudvm_ram_size_periodic >/dev/null 2>&1)

2016-06-17T14:20:11.664891+02:00 virtual kernel: [ 8862.387284] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=6251 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:20:23.877678+02:00 virtual vmware-vpxd: vpxd failed to initialize in time.

2016-06-17T14:20:41.260666+02:00 virtual kernel: [ 8891.967607] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=6551 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:21:10.940726+02:00 virtual kernel: [ 8921.632250] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=6906 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:21:41.452588+02:00 virtual kernel: [ 8952.121422] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:8d:f4:26:08:00 SRC=192.168.0.51 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=22577 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:22:11.080638+02:00 virtual kernel: [ 8981.739467] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=7505 PROTO=UDP SPT=137 DPT=137 LEN=58

Please help me, tell me where I made mistake. Thank you in advance.

Hello,

We started deploying a new multi-site VM cluster earlier on in the year. We planned on two vCenter Servers in Enhanced Linked Mode and saw that the only way to do this was using an external PSC. We deployed vCenter Appliance with External PSC and are managing all the sites but have yet to deploy the second vCenter server. Now that 6.7 is out and ELM is supported on the embedded model, because we haven't actually deployed and linked our second vCenter server, is there a way I can deploy it in Embedded mode and migrate everything over and then re-deploy the first site? I understand there isn't a way to convert from external to embedded yet (if ever)...

We are using vSAN and vDS on the existing configration.

If this is possible, how much downtime should we expect (if any?) and can I deploy this new instance using the same SSO domain? Or do I need a brand new one?

JAVA_TOOLS_OPTIONS needs to be removed. How?

Hi Everyone

I have three hosts on my vcenter, however I can't seem to move any VMs into a resource pool as I get the following error(for example):

Move into resource pool SALES Cannot complete operation due to concurrent modification by another operation.

Any ideas? I can move VMs around on the other two hosts without a problem. The only difference is that the problematic host is running ESXi version 5.1.0 1065491, the others are running 5.1.0 799733

Any help would be greatly appreciated...

Thanks!

Hi everyone.

Today I saw this video from VMware - vCenter Embedded Linked Mode - YouTube  - And got myself a doubt. Is it really a best practice? I mean, following the VMware Knowledge Base this topology is listed as deprecated topology. Now I'm bit confused!

Thanks.

Hi!

We have vCenter 6.0 working normally but it has a local hostname (vCenter.domain.local). This was build by an employee that left the company. I need to open the web client to the web (with Inbound filter) but my issue is that anytime I access the external IP or the external FQDN, it redirect to the local name, so it doesn't work.

https://vcenter.domain.local/websso/SAML2/SSOSSL?RelyingPartyEntityId=aHR0cHM6Ly8yMDYuNDEuOTUuMjU0OjQ0NDMvdnNwaGVyZS…

How can I fix this, without breaking anything?

Thanks for any help

I need to track logins to vcsa as email alerts.