I have a brand new vcsa 6.0 u1 install and we are getting multiple entries showing vcenter appliance trying to connect to hans-moleman.w3.org 128.30.52.100 on port 80

Does anyone know what this is and how we can disable it?

HI Team,

  Can anyone please confirm what are the maximum RDM's we can configure to one Virtual Machine

Today We patched esxi ESXi550-201512401-BG Bug fix KB :2135436 cause ESXI server to get disconnected from vCenter.

Do we have any method to uninstall specific update.

Can vCenter 5.5 manage a single cluster with hosts that are in 2 separate locations (different buildings on the same campus)?  This is for a total of 4 hosts - 2 at each site - and approx. 20 VMs

Considering the storage and networking are available, the only issue I can see is latency for SSO, but I have not really had this question posed - this is a customer request

friends

I can not deploy an OVF, the following message appears: "a connection error occurred. verify that your computer can connect to vcenter server"

Hello everyone,

I am trying to create reports within OM and continue to run into an issue where the resultant report is always blank. This problem persists even if I go into the "views" tab to create/clone custom instances of the views that I am using, and then apply them to a custom report. It would seem to me that the "Preview Source" I select is never saved in the system. Instead OM always seems to go back to the default of "Sample data" and I continue to output blank reports.

Does anyone have any leads regarding this issue? Thank you for any help that you can offer.

What’s new?

Hyperic 5.8.5 is a maintenance release with major and minor bug fixes.

In addition to general issue fixing, the following changes have been made:

• The user interface has been upgraded to use Apache Struts 2 framework.
  Users who have created custom pages or extensions to the user interface, must update their pages to the Struts 2 framework.
• As part of the user interface upgrade, the URLs of all pages have changed.
  Users who have scripts that point to vRealize Hyperic pages must modify the URLs accordingly.
• New buttons are provided in the user interface to set or clear indicator flags for metrics in the Edit Metric Template page.
  Metrics that were enabled or disabled earlier retain their state unless you specifically change them.
• JRE version 7u91 (1.7.0-91) is supported.
• SSLv3 has been removed from the vRealize Hyperic agent.
• TC Server has been updated to version 3.0.2 and Tomcat to verion 8.

• The PostgreSQL database has been upgraded to version 9.1.15.
• The cipher list in the vRealize Hyperic server and agent has been upgraded to provide enhanced security
• JVM MBean query causes update agent message
  A JVM MBean query no longer causes the Unable to deserialize agent data. You may need to update your agent. message.
• vRealize Hyperic server startup takes too long
  The start up time for vRealize Hyperic server has been improved.
• vRealize Hyperic discovers Microsoft Windows 2102r2 as unknown
  Microsoft Windows 2102 r2 is no longer discovered as unknown by vRealize Hyperic.
• Agent using Java 6 cannot connect to the vRealize Hyperic server
  Agents using Java 6 can now connect to the vRealize Hyperic server.
• HibernateTransactionManager timeout too low causing transactions to be aborted
  The timeout for HibernateTransactionManager is no longer so low that transactions are aborted.
• CPU is reported as 1 when the availbility is 0
  The CPU availability is no longer incorrectly reported as 1 (meaning 100%), when the availbility is actually 0.
• Heavy agent CPU utilization when is agent unable to communicate with the server
  Heavy agent CPU utilization no longer occurs when the agent is unable to communicate with the vRealize Hyperic server.
• Sybase JDBC password displayed in clear text
  The Sybase JDBC password is no longer displayed in clear text when plug-in debugging is enabled.

What’s new?

Hyperic 5.8.5 is a maintenance release with major and minor bug fixes.

In addition to general issue fixing, the following changes have been made:

• The user interface has been upgraded to use Apache Struts 2 framework.
  Users who have created custom pages or extensions to the user interface, must update their pages to the Struts 2 framework.
• As part of the user interface upgrade, the URLs of all pages have changed.
  Users who have scripts that point to vRealize Hyperic pages must modify the URLs accordingly.
• New buttons are provided in the user interface to set or clear indicator flags for metrics in the Edit Metric Template page.
  Metrics that were enabled or disabled earlier retain their state unless you specifically change them.
• JRE version 7u91 (1.7.0-91) is supported.
• SSLv3 has been removed from the vRealize Hyperic agent.
• TC Server has been updated to version 3.0.2 and Tomcat to verion 8.

• The PostgreSQL database has been upgraded to version 9.1.15.
• The cipher list in the vRealize Hyperic server and agent has been upgraded to provide enhanced security
• JVM MBean query causes update agent message
  A JVM MBean query no longer causes the Unable to deserialize agent data. You may need to update your agent. message.
• vRealize Hyperic server startup takes too long
  The start up time for vRealize Hyperic server has been improved.
• vRealize Hyperic discovers Microsoft Windows 2102r2 as unknown
  Microsoft Windows 2102 r2 is no longer discovered as unknown by vRealize Hyperic.
• Agent using Java 6 cannot connect to the vRealize Hyperic server
  Agents using Java 6 can now connect to the vRealize Hyperic server.
• HibernateTransactionManager timeout too low causing transactions to be aborted
  The timeout for HibernateTransactionManager is no longer so low that transactions are aborted.
• CPU is reported as 1 when the availbility is 0
  The CPU availability is no longer incorrectly reported as 1 (meaning 100%), when the availbility is actually 0.
• Heavy agent CPU utilization when is agent unable to communicate with the server
  Heavy agent CPU utilization no longer occurs when the agent is unable to communicate with the vRealize Hyperic server.
• Sybase JDBC password displayed in clear text
  The Sybase JDBC password is no longer displayed in clear text when plug-in debugging is enabled.

Known Issues in vRealize Hyperic 5.8.5

The following issue is known to exist in this version of vRealize Hyperic.

• Following an update of vRealize Hyperic, the LDAP password does not display any characters in the user interface. Nevertheless, the password is configured, saved in the database, and works as expected.

Download link

Hyperic Application & System Monitoring - Browse /Hyperic 5.8.5 at SourceForge.net

Hello,

I created a Custom Group in vRealize Operation Manager 6.1 and I'd like to see a Trend graph of all VMs in this group under Details > Views, however there are only List and Distribution 'Types'. If I select a single VM, there are Trend report options. Is it possible to get these Trend Type of graphs created for a group of VMs? It would be nice to see them all on one graph.

Thanks,

Scott

Has anyone had success in deploying vRO in vCloud Air and assigning a static IP to it from the vCloud Air user interface?  When I attempt to give it a specific IP address in the provisioning process through the vCloud Air UI, vCloud Air fails to assign the IP address properly as it does when I deploy it through vCenter.  This is version 5.5

We need to create a DRS group for our SQL VM's because of a new Microsoft support contract i'm  not happy with, and what makes the VMware environment less flexible.

6 ESXi host v5.5. About 80 VM's. 6 SQL VM's

1 ESXi host is going to be licensed for SQL. Not an ideal situation with SQL servers, I know. Still in discussion to license at least 2 ESXi host

Anyway, for the time being I need to create a kinda Passive / Active ESXi hosts situation.

I'll create a Host DRS group with 2 ESX hosts(Host1 and Host2), and a VM DRS group for the SQL VM's.

Move the SQL VM's to Host1 and disable DRS on the VM's, apply the rule, must run on host in group.

VM's will only migrate to host 2 if host1 crashes. Is this correct??

And can I enter maintenance mode for Host1 if DRS is disabled on the VM's??

Thanks

I am trying to get VMware View up and running for testing.  I have installed all components that are required.  I have two Windows 2008 R2 Server in my enviorment.  One has vCenter Server installed with Composer on that machine.  One server has View Connection Server installed on it.  When I go into the VMware Horizon View Administrator to install the vCenter Server I get the following error message:

"Error Saving VCenter Entry"

I have read about this error on some of the threads.  I see that this may be due to a username and password issue.  I am using domain\user and password and an account that I know works properly and has Domain Admin rights.  I read to check the VPXD logs.  I did read the log but, I see that there is a result returned that says:

2015-12-09T09:54:51.992-05:00 [02176 info 'commonvpxLro' opID=367d5331] [VpxLRO] -- BEGIN task-internal-631 --  -- vim.ServiceInstance.retrieveContent -- af32f368-a03c-a894-9847-5b3a4c37522f

2015-12-09T09:54:51.993-05:00 [02176 info 'commonvpxLro' opID=367d5331] [VpxLRO] -- FINISH task-internal-631 --  -- vim.ServiceInstance.retrieveContent --

2015-12-09T09:54:52.080-05:00 [02244 info '[SSO]' opID=627801b3] User PAE\viewservice authenticated successfully.

2015-12-09T09:54:52.080-05:00 [02244 info 'Default' opID=627801b3] [Auth]: User PAE\viewservice

2015-12-09T09:54:52.081-05:00 [02244 info 'commonvpxLro' opID=627801b3] [VpxLRO] -- FINISH task-internal-630 --  -- vim.SessionManager.login --

2015-12-09T09:54:52.081-05:00 [02244 info 'Default' opID=627801b3] [VpxLRO] -- ERROR task-internal-630 --  -- vim.SessionManager.login: vim.fault.NoPermission:

--> Result:

--> (vim.fault.NoPermission) {

-->    dynamicType = <unset>,

-->    faultCause = (vmodl.MethodFault) null,

-->    object = 'vim.Folder:group-d1',

-->    privilegeId = "System.View",

-->    msg = "",

--> }

--> Args:

-->

2015-12-09T09:54:52.218-05:00 [04420 info 'commonvpxLro' opID=5518ce21] [VpxLRO] -- BEGIN task-internal-632 --  -- vim.SessionManager.login -- af32f368-a03c-a894-9847-5b3a4c37522f

2015-12-09T09:54:52.218-05:00 [04420 info '[SSO]' opID=5518ce21] [UserDirectorySso] Authenticate(pae\viewservice, "not shown")

2015-12-09T09:54:52.427-05:00 [04420 info '[SSO]' opID=5518ce21] User PAE\viewservice authenticated successfully.

2015-12-09T09:54:52.428-05:00 [04420 info 'Default' opID=5518ce21] [Auth]: User PAE\viewservice

2015-12-09T09:54:52.428-05:00 [04420 info 'commonvpxLro' opID=5518ce21] [VpxLRO] -- FINISH task-internal-632 --  -- vim.SessionManager.login --

2015-12-09T09:54:52.428-05:00 [04420 info 'Default' opID=5518ce21] [VpxLRO] -- ERROR task-internal-632 --  -- vim.SessionManager.login: vim.fault.NoPermission:

--> Result:

--> (vim.fault.NoPermission) {

-->    dynamicType = <unset>,

-->    faultCause = (vmodl.MethodFault) null,

-->    object = 'vim.Folder:group-d1',

-->    privilegeId = "System.View",

-->    msg = "",

--> }

--> Args:

-->

2015-12-09T09:55:22.433-05:00 [06068 warning 'VpxProfiler' opID=34fbb9cd-SWI-664018d0] VpxUtil_InvokeWithOpId [TotalTime] took 31298 ms

Can anyone help me decipher this log?  I am very new to VMware.  I am sure that I am missing something that is obvious.

Hello,

I have a problem with installing

Device Drivers for HP Custom ESXi 6.0.0 Image v600.9.1

Device Drivers for HP Custom ESXi 6.0.0 Image v600.9.2

Device Drivers for HP Custom ESXi 6.0.0 Image v600.9.3

Device Drivers for HP Custom ESXi 6.0.0 Image v600.9.30

When staging this packages I get an error message with the info to look into the Log Files.

Device Drivers for HP Custom ESXi 6.0.0 Image v600.9.4 are installed.

ESXi Version is from Custom HP Image VMware-ESXi-6.0.0-Update1-3073146-HP-600.9.4.34-Nov2015.

I did some checking with the log and found out the following vibs are missing.

QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400.vib

QLogic_bootbank_scsi-qla4xxx_644.55.34.0-1OEM.550.0.0.1331820.vib

Should I manual install the missing vibs?

Thanks for your help in advance.

Regards,

Dieter

The Log show the following entries:

[2015-12-09 13:33:15:813 'HostUpdateDepotManager' 13716 INFO]  [scanHost20, 1261] Bulletin: hpq-driver-bundle-600.9.1.39 Release Type: extension Status: Missing (  vib: Broadcom_bootbank_misc-cnic-register_1.710.30.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2_2.2.5f.v55.6-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2x_2.710.39.v55.2-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-cnic_2.710.35.v55.5-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-tg3_3.136h.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2fc_1.710.35.v55.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2i_2.710.30.v55.4-1OEM.550.0.0.1331820: obsoleted by Host vib: Brocade_bootbank_scsi-bfa_3.2.3.0-1OEM.550.0.0.1198610: obsoleted by Host vib: Emulex_bootbank_elxnet_10.2.298.5-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_ima-be2iscsi_10.2.250.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_lpfc_10.2.340.18-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_scsi-be2iscsi_10.2.250.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.12-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpsa_5.5.0.74-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0-90OEM.550.0.0.1331820: obsoleted by Host vib: Intel_bootbank_net-igb_5.0.5.1-1OEM.550.0.0.1198611: obsoleted by Host vib: Intel_bootbank_net-ixgbe_3.15.1.8-1OEM.550.0.0.1198611: obsoleted by Host vib: LSI_bootbank_scsi-mpt2sas_15.10.06.00.1vmw-1OEM.550.0.0.1198610: obsoleted by Host vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Missing vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Obsoletes Host vib: QLogic_bootbank_net-nx-nic_5.5.639-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_net-qlcnic_5.5.190-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_qlnativefc_1.1.29.0-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_scsi-qla4xxx_644.55.34.0-1OEM.550.0.0.1331820: Missing vib: QLogic_bootbank_scsi-qla4xxx_644.55.34.0-1OEM.550.0.0.1331820: Obsoletes Host )

[2015-12-09 13:33:15:814 'HostUpdateDepotManager' 13716 INFO]  [scanHost20, 1261] Bulletin: hpq-driver-bundle-600.9.2.38 Release Type: extension Status: Missing (  vib: Broadcom_bootbank_misc-cnic-register_1.710.70.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2_2.2.5f.v55.16-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2x_2.710.70.v55.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-cnic_2.710.70.v55.5-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-tg3_3.137d.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2fc_1.710.70.v55.3-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2i_2.710.70.v55.6-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_elxnet_10.2.445.0-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_ima-be2iscsi_10.2.250.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_lpfc_10.2.455.0-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_scsi-be2iscsi_10.2.250.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.26-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpsa_5.5.0.84-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0-92OEM.550.0.0.1331820: obsoleted by Host vib: Intel_bootbank_net-igb_5.2.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Intel_bootbank_net-ixgbe_3.21.4-1OEM.550.0.0.1331820: obsoleted by Host vib: LSI_bootbank_scsi-mpt2sas_15.10.06.00.1vmw-1OEM.550.0.0.1198610: obsoleted by Host vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Missing vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Obsoletes Host vib: QLogic_bootbank_net-nx-nic_5.5.641-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_net-qlcnic_5.5.190-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_qlnativefc_1.1.39.0-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820: installed vib: QLogic_bootbank_scsi-qla4xxx_644.55.35.0-1OEM.550.0.0.1331820: Missing vib: QLogic_bootbank_scsi-qla4xxx_644.55.35.0-1OEM.550.0.0.1331820: Obsoletes Host )

[2015-12-09 13:33:15:814 'HostUpdateDepotManager' 13716 INFO]  [scanHost20, 1261] Bulletin: hpq-driver-bundle-600.9.3 Release Type: extension Status: Missing (  vib: Broadcom_bootbank_misc-cnic-register_1.710.70.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2_2.2.5f.v55.16-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2x_2.710.70.v55.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-cnic_2.710.70.v55.5-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-tg3_3.137h.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2fc_1.710.70.v55.3-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2i_2.710.70.v55.6-1OEM.550.0.0.1331820: obsoleted by Host vib: EMU_bootbank_lpfc_10.4.236.0-1OEM.600.0.0.2159203: obsoleted by Host vib: Emulex_bootbank_elxnet_10.5.65.4-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_ima-be2iscsi_10.5.65.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_scsi-be2iscsi_10.5.65.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.36-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpsa_5.5.0.106-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0.98-1OEM.550.0.0.1331820: obsoleted by Host vib: Intel_bootbank_net-igb_5.2.10-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_net-ixgbe_3.21.4.3-1OEM.550.0.0.1331820: installed vib: LSI_bootbank_scsi-mpt2sas_15.10.06.00.1vmw-1OEM.550.0.0.1198610: obsoleted by Host vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Missing vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Obsoletes Host vib: QLogic_bootbank_net-nx-nic_5.5.641-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_net-qlcnic_5.5.190-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_qlnativefc_2.1.20.0-1OEM.600.0.0.2159203: obsoleted by Host vib: QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820: installed vib: QLogic_bootbank_scsi-qla4xxx_644.55.36.0-1OEM.550.0.0.1331820: Missing vib: QLogic_bootbank_scsi-qla4xxx_644.55.36.0-1OEM.550.0.0.1331820: Obsoletes Host )

[2015-12-09 13:33:15:815 'HostUpdateDepotManager' 13716 INFO]  [scanHost20, 1261] Bulletin: hpq-driver-bundle-600.9.3.30 Release Type: extension Status: Missing (  vib: Broadcom_bootbank_misc-cnic-register_1.710.70.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2_2.2.5f.v55.16-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2x_2.710.70.v55.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-cnic_2.710.70.v55.5-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-tg3_3.137h.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2fc_1.710.70.v55.3-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2i_2.710.70.v55.6-1OEM.550.0.0.1331820: obsoleted by Host vib: EMU_bootbank_lpfc_10.4.236.0-1OEM.600.0.0.2159203: obsoleted by Host vib: Emulex_bootbank_elxnet_10.5.65.4-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_ima-be2iscsi_10.5.65.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_scsi-be2iscsi_10.5.65.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.36-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpsa_5.5.0.106-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0.100-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_net-igb_5.2.10-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_net-ixgbe_3.21.4.3-1OEM.550.0.0.1331820: installed vib: LSI_bootbank_scsi-mpt2sas_15.10.06.00.1vmw-1OEM.550.0.0.1198610: obsoleted by Host vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Missing vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Obsoletes Host vib: QLogic_bootbank_net-nx-nic_5.5.641-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_net-qlcnic_5.5.190-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_qlnativefc_2.1.20.0-1OEM.600.0.0.2159203: obsoleted by Host vib: QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820: installed vib: QLogic_bootbank_scsi-qla4xxx_644.55.36.0-1OEM.550.0.0.1331820: Missing vib: QLogic_bootbank_scsi-qla4xxx_644.55.36.0-1OEM.550.0.0.1331820: Obsoletes Host )

[2015-12-09 13:33:15:815 'HostUpdateDepotManager' 13716 INFO]  [scanHost20, 1292] Bulletin: hpq-driver-bundle-600.9.4 Release Type: extension Status: Installed (  vib: BRCM_bootbank_net-tg3_3.137l.v60.1-1OEM.600.0.0.2494585: installed vib: EMU_bootbank_elxnet_10.5.121.7-1OEM.600.0.0.2159203: installed vib: EMU_bootbank_ima-be2iscsi_10.5.101.0-1OEM.600.0.0.2159203: installed vib: EMU_bootbank_lpfc_10.5.70.0-1OEM.600.0.0.2159203: installed vib: EMU_bootbank_scsi-be2iscsi_10.5.101.0-1OEM.600.0.0.2159203: installed vib: Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.46-1OEM.550.0.0.1331820: installed vib: Hewlett-Packard_bootbank_scsi-hpsa_6.0.0.114-1OEM.600.0.0.2494585: installed vib: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0.100-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_intelcim-provider_0.5-1.4: installed vib: Intel_bootbank_net-i40e_1.2.48-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_net-igb_5.2.10-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_net-ixgbe_3.21.4.3-1OEM.550.0.0.1331820: installed vib: LSI_bootbank_scsi-mpt2sas_15.10.06.00.1vmw-1OEM.550.0.0.1198610: obsoleted by Host vib: MEL_bootbank_nmlx4-core_3.1.0.0-1OEM.600.0.0.2348722: installed vib: MEL_bootbank_nmlx4-en_3.1.0.0-1OEM.600.0.0.2348722: installed vib: MEL_bootbank_nmst_4.0.0.20-1OEM.600.0.0.2295424: installed vib: QLogic_bootbank_misc-cnic-register_1.712.50.v60.1-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_net-bnx2_2.2.5j.v60.3-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_net-bnx2x_2.712.50.v60.6-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_net-cnic_2.712.50.v60.6-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_net-nx-nic_6.0.643-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_net-qlcnic_6.1.191-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_qlnativefc_2.1.27.0-1OEM.600.0.0.2768847: installed vib: QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820: installed vib: QLogic_bootbank_scsi-bnx2fc_1.712.50.v60.7-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_scsi-bnx2i_2.712.50.v60.4-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_scsi-qla4xxx_644.6.04.0-1OEM.600.0.0.2159203: installed )

Lately I’ve been running into random failures in my deployment workflow when it comes to finding what datastores are attached to what hosts. My workflow selects a host to use, then loops through all datastores, looking to see what hosts are connected and builds a list of available datastores I can pick from.

The relevant section of code is where my problem is:

var allDatastores = System.getModule("com.vmware.library.vc.datastore").getAllDatastores();

var vmStorage = new Array();

var storageName;

if (allDatastores)

{

for (i = 0; i < allDatastores.length; i++)

                {

                                for (j=0; j < allDatastores[i].host.length; j++)

Everything works fine but every now and then, I get the following error: TypeError: Cannot read property "length" from undefined

I believe the error is coming from the host.length call (I’ve adding a little more logging to try and confirm the next time it happens). I added a try/catch block to loop through the same section of the code in the event of a failure but after 10 attempts (with 15 seconds between), it still fails. Another call to the workflow right after works just fine.

Anyone know what might be the cause of if there’s a better way to get a list of datastores and/or datastore clusters attached to a given host? I've seen other random failures (usually with running stuff within the guest OS via vmware tools) and retrying seems to work but in this case, not so much.

Thanks

Porque o vcenter appliance possui tantos discos?

For the last one year i have seen hypercoverged sytems are emerging in market..do any one fell next gen will be software defined datacenter

Hello,

My Vcenter server is stuck on a 5.5 host and I cannot get it to vMotion while powered on. I only have ESXi 6 hosts left at this datacenter. If I power the VMs off, they move. Obviously I cannot power off Vcenter.

The error I get is

A general system error occurred: Failed to copy one or more of the virtual machine's disks. See the virtual machine's log for more details.

Failed to set up disks on the destination host.

vMotion migration [168430346:1445297623259034] failed to read stream keepalive: Connection closed by remote host, possibly due to timeout

Failed waiting for data. Error 195887167. Connection closed by remote host, possibly due to timeout.

Any ideas?

I have 2 Windows vCenters with 2 external PSCs in enhanced linked mode. Should I be able to see both vCenters in the thick client the same as I do in v5.5?