I need to lower the MTU for eth0 in the vCenter Server Appliance. This will be a persistent configuration. What is the proper way to do that for 6.5?

Hi guys,

How do you change the amount of days in which the vSphere web client or HTML client prompts you that a password will expire in X number of days?

Many thanks

Aaron

Is there a way to disable or modify when this alert banner pops up? The reason I ask is we are using our AD credentials to login. when those credentials are 30 days from expiring we start getting this banner which is quite annoying. It would be nice to change this to 7 days or something like that.

I still want to know HOW to disable the message.  It's a domain policy, fine.  But WHY is VMWare reporting it every time I login to vCenter, it's quite annoying.  Probably can't turn it off per-se this is VMware attempt at full transparency because they ASSUME that since they are tied to Active Directory we want to SEE ALL AD messages pertaining to login, but that is false and it should still be preference.

 

I login in Windows RDP all day long and none of them complain my password will expire in 30 days, 29 days, 28 days.. they are members of domain, I get a warning at 10 days (which is what I expect) not 30 days out!

 

We want to know how to turn WARNING or notifications off, not change Max Days setting.  There doesn't appear to be any way.... but your post is misleading, there is still no solution.

This is configurable as part of the vSphere Web (Flex) / H5 (HTML) Client configuration

 

Web Client - /etc/vmware/vsphere-client/webclient.properties

H5 Client - /etc/vmware/vsphere-ui/webclient.properties

 

The default is 30 days

 

# The number of days before the notification about expiring password appears.

sso.pending.password.expiration.notification.days = 30

You'll probably need to restart the service for the change to take effect

 

This document was generated from the following discussion: Password expires in X days notification

Pretty self-explanatory, but I'll try my best to improve the question: since basically vCenter Server needs an OS to run and that's some version of Linux, VMware's Photon I believe, why not eliminate the hypervisor layer to have it get the most of its dedicated host    -- I just found the perfect vCenter for my scenario, an old Mac mini. I have two other dedicated hosts to only one VM and a big server with hundreds of gigs of ram where all the rest of the VMs live so I don't need to perform vMotions, I do need however, vCenter to interface with those features not available an ESXi host alone.

If I'm missing something please tell me, I'm virtually new to virtualizing -- heh--sorry, had to    -- I think it's the bes the best way. Besides, the processor on the Mac mini would force me to downgrade the EVC mode to the Penryn generation, it is that old, for my vCenter it's actually perfect, though.

Dear all

I just installed a SRM6.1 and the storage is Dell Compellent running Storage Center version 7.1. After I installed the SRA, and the pair can be discovered successfully, but some of them cannot match the local datastore, just like below

Then I checked the log in the SRM  and found the below, it said device "#" matches two different devices. Then I checked the NAA ID, the red one is the Protocol Endpoint presented by the Dell Compellent and the black one is the actual LUN.

2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '5' matches two different devices 'naa.6000d310033f60010000000000000005' and 'naa.6000d310033f60000000000000000007'

2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '6' matches two different devices 'naa.6000d310033f60010000000000000006' and 'naa.6000d310033f60000000000000000008'

2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '8' matches two different devices 'naa.6000d310033f60010000000000000008' and 'naa.6000d310033f6000000000000000000a'

2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '9' matches two different devices 'naa.6000d310033f60010000000000000009' and 'naa.6000d310033f6000000000000000000b'

2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '10' matches two different devices 'naa.6000d310033f6001000000000000000a' and 'naa.6000d310033f6000000000000000000c'

2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '12' matches two different devices 'naa.6000d310033f6001000000000000000c' and 'naa.6000d310033f6000000000000000000e'

2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '13' matches two different devices 'naa.6000d310033f6001000000000000000d' and 'naa.6000d310033f6000000000000000000f'

2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '14' matches two different devices 'naa.6000d310033f6001000000000000000e' and 'naa.6000d310033f60000000000000000010'

2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '15' matches two different devices 'naa.6000d310033f6001000000000000000f' and 'naa.6000d310033f60000000000000000011'

2017-12-15T14:34:37.254+08:00 [03796 error 'DatastoreGroupManager' opID=4c35f1e8] Dr::Storage::Match::DeviceMatcher::DeviceMatcher: Device '16' matches two different devices 'naa.6000d310033f60010000000000000010' and 'naa.6000d310033f60000000000000000012'

So may I know any one here got the same experience? Why the vCenter/SRM think protocol endpoint are same as the protocol endpoint? And how to fix it? I checked Dell's manual seems we cannot disable the protocol endpoint in Storage.

Best regards

Alex Tsang

hi,

i seen that when i add a new device to an esx host with vcenter by scanninf the hba controller in device screen appear only one device even if i have 2 paths to the disk in San.Is this because the mpio path on esx is started automatically and create a new device on top of the 2 paths?

Is the best cluster the cluster with fault tolerant feature enabled?

tnx

Guys plz help, a matter of life or death.

We have fresh new installation ESXi 6.5 host on new IBM (Lenovo) x3650 server and wanna create vSAN.

ESXi host installation fast and without any problem, but when we trying install vCenter appliance 6.5  (VMware-VCSA-all-6.5.0-7119157.iso) first stade installation working well, when we login in web and start Setup which every time show error.

First and main error in web browser is "session expiried" and show dialog "root login", after this show many different error on independed progress SetUP step.

Any idea of this?

This error "session expiried" and show dialog "root login" may arise throug 2 min progress setup or 10 min, but always shows.

We try different host and different computer, every thing the same.

Hi All,

I have an embedded PSC (in SSO domain vsphere.local) --- I am trying to add an additional external PSC in the same SSO domain

Time and DNS are fine. These are windows instances on windows 2012 R2.

When I try to add external PSC to embedded one it returns an error.  Any suggestions that I can try here ? Thanks

Converter version: 6.2.0 build-7348398

OS: Windows 10 Pro, 64Bit, Fall Creators Update, December patch installed

Tried to convert the powered machine into a vm. I used as destination system my Unix based NAS mapped to Windows. The converter wasn't able to lock the destination and started to loop.

I cancelled the process in order to use a USB drive as destination.

When I restarted the converter, I got the the error message "Permission to perform this operation was denied." both using the "Next>" button as well as pressing "View source datails..." on the Source System step of the wizard.

I rebooted the system, I uninstalled and reinstalled the converter - nothing changed. I assume the converter didn't remove a lock entry.

I'm frustrated, each support would be appreciated.

Thanks a lot,

Peter

Hi, we tried to do p2v migration with vmware converter 6.1.1 for physical Ubuntu 12.04 server, but it is failing at 95% with below errors, we did couple of other p2v migration and that went well. This on got stuck at below errors. Bottom left window showing.. Error: Unable to clone the volume mounted on '/' from 'ip_address_of_source_server';

Bottom left window showed below errors..

FAILED: An error occurred during the conversion: 'tar: ./tmp/.winbindd/pipe: socket ignored /bin/tar_1.28: ./home/jigsaw/site_monitor/jmineops.log: invalid sparse archive member tar: ./home/jigsaw/site_monitor/jmineops.log: file changed as we read it tar: ./var/lib/postgresql/9.1/main/base/16385/136308: file changed as we read it tar: ./var/lib/postgresql/9.1/main/base/16385/136299.1: file changed as we read it tar: ./var/lib/postgresql/9.1/main/base/16385/136371: 

.. ... .... a lot of similar type error...... .....

File removed before we read it tar: ./var/lib/postgresql/9.1/main/base/16385: file changed as we read it /bin/tar_1.28:
Exiting with failure status due to previous errors /usr/lib/vmware-converter/bin/ssh -z -F /usr/lib/vmware-converter/ssh.conf root@ip-of_source_server  -p 22 " tar --one-file-system --sparse -C '/' -cf - ." | /bin/tar_1.28 --numeric-owner --delay-directory-restore -C '/mnt/p2v-src-root/' -y -xf - (return code 2)'

Looks like it is something related with tar conversion,  not sure though.

Need helps to fix this issue.  Any help is highly appreciated.

Hi Guys,

We have been running vCenter server appliance version 6 (version=6.0.0, build=2776510) in production for about 6 weeks now without issue. 2 days ago logons failed to the server. quick fix was a reboot of the appliance. going through the logs show too many entries with error or failed to filter.

but before the Crash we can see entries such as below: (name of user has been replaced)

2015-12-14T23:54:52.062Z error vpxd[7FED01109700] [Originator@6876 sub=[SSO] opID=24c46df0] [UserDirectorySso] AcquireToken exception: N9SsoClient22CommunicationExceptionE(Operation timed out)

2015-12-14T23:54:52.062Z error vpxd[7FED01109700] [Originator@6876 sub=User opID=24c46df0] Failed to authenticate user 2015-12-14T23:54:52.527Z error vpxd[7FECF3060700] [Originator@6876 sub=[SSO] opID=5ac13399] [UserDirectorySso] AcquireToken exception: N9SsoClient22CommunicationExceptionE(Operation timed out)

2015-12-14T23:54:52.527Z error vpxd[7FECF3060700] [Originator@6876 sub=User opID=5ac13399] Failed to authenticate user 2015-12-14T23:54:57.068Z info vpxd[7FED01109700] [Originator@6876 sub=vpxLro opID=24c46df0] [VpxLRO] -- FINISH task-internal-275213344

2015-12-14T23:54:57.068Z info vpxd[7FED01109700] [Originator@6876 sub=Default opID=24c46df0] [VpxLRO] -- ERROR task-internal-275213344 -- SessionManager -- vim.SessionManager.login: vim.fault.InvalidLogin:

looks like an SSO issue.

SR has been logged with VMware but it seems they are too busy with other customers to deal with our case.

Has anyone experienced anything similar? T

his happens in the middle of a busy backup period (netbackup using snapshot based backup of VMs)

Regards

Ciarán

Is anyone else experiencing a failure when installing VC 6.5?  I have this occuring when installing using the CLI installer, and when deploying the OVA using the ESXi web client.

The version of VC is 6.5.0 build 4240420, the recent release candidate.

The exception report looks like:

Encountered an internal error. Traceback (most recent call last): File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 2017, in main vmidentityFB.boot() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 349, in boot self.configureSTS(self.__stsRetryCount, self.__stsRetryInterval) File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1478, in configureSTS self.startSTSService() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1140, in startSTSService returnCode = self.startService(self.__sts_service_name, self.__stsRetryCount * self.__stsRetryInterval) File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 88, in startService return service_start(svc_name, wait_time) File "/usr/lib/vmware/site-packages/cis/utils.py", line 784, in service_start raise ServiceStartException(svc_name) ServiceStartException: { "resolution": null, "detail": [ { "args": [ "vmware-stsd" ], "id": "install.ciscommon.service.failstart", "localized": "An error occurred while starting service 'vmware-stsd'", "translatable": "An error occurred while starting service '%(0)s'" } ], "componentKey": null, "problemId": null }

My group and I am curious to hear whether or not anyone else is experience this and if there are any workarounds.

Thanks!

Hey all - have to deploy an OVF with prompts/dialogues that do not show in the thick client. I've been able to get it to work previously, but now there's no hope. Chrome 58 doesn't seem to care that it's installed. IE tells me the certs are bad. Firefox continuously loops saying it added the cert to its store. Super crazy frustrating. CIP has been uninstalled, reinstalled, installed as admin, etc. Rebooted machines. Tried other machines. Etc. Anyone have this working?

Gang,

I'm trying to resolve this issue for a long time. My VCSA come up with "vmonapi" service down, always after first LAB boot (all service VMs are starting up - PSC, DNS, NSXM, VRLI, NSXC, etc.).

Issue can be fixed by second reboot VCSA appliance. It is annoying. Here are the logs, pictures and debug infos. Any idea is welcomed!

How to ensure that vmonapi will start over boot storm? Any idea how to troubleshoot? Any recommendations for resource pools for VCSA?

Error from GUI Home->System Config->Summary

HTTP response with status code 503 (enable debug logging for details): <HTML><BODY><H1>503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00007fdba4003a70] _serverNamespace = /vmonapi action = Allow _port = 8900)</H1></BODY></HTML>

root@vcsa-01a [ /var/log/vmware/vmon ]# service-control --status

Running:

applmgmt lwsmd vmafdd vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-rhttpproxy vmware-sca vmware-sps vmware-statsmonitor 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 vmonapi vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-rbd-watchdog vmware-vcha

root@vcsa-01a [ /var/log/vmware/vmon ]# vi vmon-syslog.log

17-12-18T11:28:15.825616+01:00 notice vmon  Executing op START on service statsmonitor...

17-12-18T11:28:15.825715+01:00 notice vmon  Constructed command: /usr/lib/vmware-statsmonitor/statsMonitor.sh /etc/vmware/statsmonitor/statsMonitor.xml

17-12-18T11:28:16.814873+01:00 notice vmon  Constructed command: /usr/bin/python /usr/lib/vmware-rhttpproxy/rhttpproxy-vmon-apihealth.py

17-12-18T11:28:16.815353+01:00 notice vmon  Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonApiHealthCmd.py -n vmware-statsmonitor -f /var/vmware/applmgmt/statsmonitor_health.xml

17-12-18T11:28:18.274459+01:00 warning vmon  Service vmonapi pre-start command's stderr: urlopen() failed! Trying force_refresh=True...

17-12-18T11:28:18.274777+01:00 warning vmon

17-12-18T11:28:18.308797+01:00 warning vmon  Service vmonapi pre-start command's stderr: Failed to start vmonapi service. Exception : <urlopen error [Errno 111] Connection refused>

17-12-18T11:28:18.320921+01:00 err vmon  Service vmonapi pre-start command failed with exit code 255.

17-12-18T11:28:19.256395+01:00 warning vmon  Service rhttpproxy api-health command's stderr: Health URL: https://localhost:443/rhttpproxyhealth

17-12-18T11:28:19.256527+01:00 warning vmon  <urlopen error [Errno 111] Connection refused>

17-12-18T11:28:19.256641+01:00 notice vmon  Re-check service rhttpproxy health since it is still initializing.

17-12-18T11:28:19.274526+01:00 notice vmon  Service applmgmt pre-start command completed successfully.

17-12-18T11:28:19.274696+01:00 notice vmon  Constructed command: /usr/bin/python /usr/lib/applmgmt/base/bin/vherdrunner /usr/lib/applmgmt/transport/bin/multiserve --config /etc/applmgmt/applmgmt.conf

17-12-18T11:28:20.245715+01:00 notice vmon  Constructed command: /usr/bin/python /usr/lib/vmware-rhttpproxy/rhttpproxy-vmon-apihealth.py

17-12-18T11:28:20.393563+01:00 notice vmon  Constructed command: /usr/bin/python /usr/lib/applmgmt/applmgmt_vmonhealth.py

17-12-18T11:28:20.393805+01:00 warning vmon  Service rhttpproxy api-health command's stderr: Health URL: https://localhost:443/rhttpproxyhealth

17-12-18T11:28:20.393942+01:00 warning vmon  <urlopen error [Errno 111] Connection refused>

17-12-18T11:28:20.394053+01:00 notice vmon  Re-check service rhttpproxy health since it is still initializing.

17-12-18T11:28:20.825672+01:00 warning vmon  Service applmgmt api-health command's stderr: error(111, 'Connection refused')

17-12-18T11:28:20.832896+01:00 notice vmon  Re-check service applmgmt health since it is still initializing.

17-12-18T11:28:21.322502+01:00 notice vmon  Constructed command: /usr/bin/python /usr/lib/vmware-rhttpproxy/rhttpproxy-vmon-apihealth.py

I was about to upgrade our vCenter 6.0 Update 3b to 6.0 Update 3c when I noticed this one line in the readme for it, "Upgrading from vCenter Server 6.0 Update 3c to vCenter Server 6.5 is not supported."

Is this true?  If so, will this get fixed?

Regards,

Tom

Hello,

I need to change the FQDN of my 6.5 VCSA, but in both the VCSA web client logged in as the local VCSA admin account, and the VAMI when logged in as root, the FQDN is the only

parameter that I cannot change as it is greyed out in both UI's. How can I change the FQDN?

Thanks

-John

Hi,

I have problem when create a protection group, I can see only one datastore groups which contain all datastores inside. How can I select individual datastore groups by Cluster?

System Details:

vSphere Server     6.0 update 3

vCenter Server      6.0 update 3

SRM                      6.1

Storage:

IBM V7000 connects via IBM SVC with remote mirror datastores to another IBM SVC connects to IBM V7000 at DR site.

Regards

Pavin Kullama

I’m seeing lots of this in /var/log/vmware/applmgmt/StatsMonitor.log (on vCSA 6.5.0.12000 Build Number 7119157)

2017-12-19T10:53:45.451+01:00 error StatsMonitor[7FD04F4AA700] [Originator@6876 sub=LinuxStorageStatsProvider(200148195552)] statvfs(/storage/invsvc) failed with errno 2

Seems there is a check on a directory every 10 minutes, but the directory does not exist. I think it used to be there in an earlier version, but not anymore.

So is this maybe a bug in the StatsMonitor that it still tries to check it? Should I just create an empty folder?

I dug a bit deeper, and found the config file for StatsMonitor (/etc/vmware/statsmonitor/statsMonitor.xml) and it contains config for /storage/invsvc

<!-- File systems to monitor for utilization. -->
...            <filesystem id="invsvc">               <name>invsvc</name>               <path>/storage/invsvc</path>            </filesystem>

Maybe this should have been removed from the vCSA65?

According to the 6.5U1 release notes it seems some alerts, like for invsvc, should have been removed..

snip from resolved Issue:

Alarm definitions for deprecated services are still visible in the user interface

Alarm definitions for certain deprecated services have not been updated. As a result, you can still see alarm definitions for deprecated services in the vSphere user interface.

This issue is resolved in this release.
Alarms have been deprecated for the following services: ts, vws, vmware-syslog, invsvc
Alarms have been updated for the following services: content-library, vpxd-svcs

So should I create this directory or should I update the configuration?

Hi,

I have a situation where there are 3 disks -> /dev/sdj, /dev/sdk, /dev/sdl -> all 3 of same size in a RHEL system.

I want to remove a disk(/dev/sdj) from the system from Vsphere.

How to find the corresponding .vmdk name?

I have been trying.

Needing your help.

Hi all - have VCSA 6.5 installed in two locations now.  Enhanced authentication plugin is installed but not working - cannot check the box for credential fill-in.  Tried a few different things to no avail.  Anyone have it working or know why it may not be working in Chrome or IE in Windows 10?

Thanks all!

How do I reconfigure a stand-alone vCenter Server with an embedded Platform services controller as a vCenter Server with an external Platform services controller, what do we need to do on a separate vCenter Server for the embedded Platform services controller? What to do with vCenter Server with an external Platform services controller? Who can give me some advice, thank you