Quantcast
Channel: VMware Communities: Message List
Viewing all 247559 articles
Browse latest View live

VMware ESXi 6.5.0 intaller fails to recognize Intel Xeon D-1541 x552 NIC

$
0
0

I am installing VSphere Hpervisor 6.5.0 Update 1 to a  Intel Xeon D-1541 based server. It is setup to do PXE UEFI install. I am able to boot from the D-1541 embedded X522 NIC. However, the installer comes up with "No compatible network adapter found."

 

                                                                       

x       VMware ESXi 6.5.0 (VMKernel Release Build 5969303)                     x

x                                                                              x                                                      x

x                                                                              x

x       Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz                                  x

x       31.7 GiB Memory                                                        x

x                                                                              x

x                                                                              x

x       No compatible network adapter found. Please consult the                x

x       product's Hardware Compatibility Guide (HCG) for a list of             x

x       supported adapters.                                                    x

 

How can I add the driver for X552 to my PXE server?

 

My boot.cfg is

>>>>>>>>>

bootstate=0

title=Loading ESXi installer

timeout=5

kernel=tboot.b00

#kernelopt=runweasel gdbPort=none logPort=none tty2Port=com2 com2_baud=38400

kernelopt=gdbPort=none logPort=none tty2Port=com2 com2_baud=38400

modules=b.b00 --- jumpstrt.gz --- useropts.gz --- features.gz --- k.b00 --- chardevs.b00 --- a.b00 --- user.b00 --- uc_intel.b00 --- uc_amd.b00 --- sb.v00 --- s.v00 --- ata_liba.v00 --- ata_pata.v00 --- ata_pata.v01 --- ata_pata.v02 --- ata_pata.v03 --- ata_pata.v04 --- ata_pata.v05 --- ata_pata.v06 --- ata_pata.v07 --- block_cc.v00 --- char_ran.v00 --- ehci_ehc.v00 --- elxnet.v00 --- hid_hid.v00 --- i40en.v00 --- igbn.v00 --- ima_qla4.v00 --- ipmi_ipm.v00 --- ipmi_ipm.v01 --- ipmi_ipm.v02 --- ixgben.v00 --- lpfc.v00 --- lsi_mr3.v00 --- lsi_msgp.v00 --- lsi_msgp.v01 --- misc_cni.v00 --- misc_dri.v00 --- mtip32xx.v00 --- ne1000.v00 --- nenic.v00 --- net_bnx2.v00 --- net_bnx2.v01 --- net_cdc_.v00 --- net_cnic.v00 --- net_e100.v00 --- net_e100.v01 --- net_enic.v00 --- net_fcoe.v00 --- net_forc.v00 --- net_igb.v00 --- net_ixgb.v00 --- net_libf.v00 --- net_mlx4.v00 --- net_mlx4.v01 --- net_nx_n.v00 --- net_tg3.v00 --- net_usbn.v00 --- net_vmxn.v00 --- nhpsa.v00 --- nmlx4_co.v00 --- nmlx4_en.v00 --- nmlx4_rd.v00 --- nmlx5_co.v00 --- ntg3.v00 --- nvme.v00 --- nvmxnet3.v00 --- ohci_usb.v00 --- pvscsi.v00 --- qedentv.v00 --- qfle3.v00 --- qflge.v00 --- qlnative.v00 --- sata_ahc.v00 --- sata_ata.v00 --- sata_sat.v00 --- sata_sat.v01 --- sata_sat.v02 --- sata_sat.v03 --- sata_sat.v04 --- scsi_aac.v00 --- scsi_adp.v00 --- scsi_aic.v00 --- scsi_bnx.v00 --- scsi_bnx.v01 --- scsi_fni.v00 --- scsi_hps.v00 --- scsi_ips.v00 --- scsi_isc.v00 --- scsi_lib.v00 --- scsi_meg.v00 --- scsi_meg.v01 --- scsi_meg.v02 --- scsi_mpt.v00 --- scsi_mpt.v01 --- scsi_mpt.v02 --- scsi_qla.v00 --- shim_isc.v00 --- shim_isc.v01 --- shim_lib.v00 --- shim_lib.v01 --- shim_lib.v02 --- shim_lib.v03 --- shim_lib.v04 --- shim_lib.v05 --- shim_vmk.v00 --- shim_vmk.v01 --- shim_vmk.v02 --- uhci_usb.v00 --- usb_stor.v00 --- usbcore_.v00 --- vmkata.v00 --- vmkplexe.v00 --- vmkusb.v00 --- vmw_ahci.v00 --- xhci_xhc.v00 --- emulex_e.v00 --- btldr.t00 --- weaselin.t00 --- esx_dvfi.v00 --- esx_ui.v00 --- lsu_hp_h.v00 --- lsu_lsi_.v00 --- lsu_lsi_.v01 --- lsu_lsi_.v02 --- lsu_lsi_.v03 --- native_m.v00 --- rste.v00 --- vmware_e.v00 --- vsan.v00 --- vsanheal.v00 --- vsanmgmt.v00 --- tools.t00 --- xorg.v00 --- imgdb.tgz --- imgpayld.tgz

build=

updated=0

>>>>>>>>>


Management Components Fail to Start After NSX 6.4 Upgrade (Timezone)

$
0
0

I came across this bug after attempting to perform and in-place upgrade from NSX 6.3.5 to 6.4  Apparently upon the completion of the upgrade reboot, neither management component attempts to start or can even be started manually even though the upgrade process seemed to complete properly.  Tech-support logs displayed the following sample errors:

 

upgrade/upgrade-script.log:7585:2018-01-24 03:00:07.052 GMT [4764]: [1-1] FATAL:  invalid value for parameter "TimeZone": "PST"
upgrade/upgrade-script.log:7586:FATAL: invalid value for parameter "TimeZone": "PST"
upgrade/upgrade-script.log:7588: MESSAGE: FATAL: invalid value for parameter "TimeZone": "PST";
upgrade/upgrade-script.log:7589: CAUSE: (org.postgresql.util.PSQLException: FATAL: invalid value for parameter "TimeZone": "PST") upgrade/upgrade-script.log:7595:Caused by: org.postgresql.util.PSQLException: FATAL: invalid value for parameter "TimeZone": "PST"
upgrade/upgrade-script.log:7610:2018-01-24 03:00:07.064 GMT [4765]: [1-1] FATAL:  invalid value for parameter "TimeZone": "PST"
upgrade/upgrade-script.log:7611:FATAL: invalid value for parameter "TimeZone": "PST"
upgrade/upgrade-script.log:7613: MESSAGE: FATAL: invalid value for parameter "TimeZone": "PST";
upgrade/upgrade-script.log:7614: CAUSE: (org.postgresql.util.PSQLException: FATAL: invalid value for parameter "TimeZone": "PST") upgrade/upgrade-script.log:7620:Caused by: org.postgresql.util.PSQLException: FATAL: invalid value for parameter "TimeZone": "PST"
upgrade/upgrade-script.log:7636:2018-01-24 03:00:07.066 GMT [4766]: [1-1] FATAL:  invalid value for parameter "TimeZone": "PST"
upgrade/upgrade-script.log:7637:FATAL: invalid value for parameter "TimeZone": "PST"
upgrade/upgrade-script.log:7639: MESSAGE: FATAL: invalid value for parameter "TimeZone": "PST";
upgrade/upgrade-script.log:7640: CAUSE: (org.postgresql.util.PSQLException: FATAL: invalid value for parameter "TimeZone": "PST")

 

VMware support helped nail it down by changing the timezone of the NSX Manager to US/Pacific from PST on the NSX 6.3.5 recovered instance, and then performing the upgrade process once again in where everything successfully began working as engineered.

 

Hope this helps someone out in the meantime while VMware researches this bug in the meantime.

 

J

Re: VMWare Mouse Click Problem

$
0
0

Thank you!

 

WizMouse caused the same issue for me on Windows 10, and uninstalling it fixed it!

download vcenter problem

$
0
0

Hi

i'm trying to download VMware vCenter Server 6.0 U3d

but it says :

You either are not entitled or do not have permissions to download this product.

Check with your My VMware Super User, Procurement Contact or Administrator.

 

If you recently purchased this product through VMware Store or through a third-party, try downloading later.

 

Download Trial

 

when i go to trial it gives me vcenter 6.5

i want to download 6 !!

Re: Clean up "Other" objects?

$
0
0

ab1a7259-3c21-e8ce-5a61-246e963e72f0 is not accessible, no-exist.....

 

[root@nfh-vhost03:/vmfs/volumes/vsan:5208d5c6f81944d9-8520459c09710020] cd ab1a7259-3c21-e8ce-5a61-246e963e72f0

-sh: cd: can't cd to ab1a7259-3c21-e8ce-5a61-246e963e72f0

 

I see only these in file browser as well:

 

ob1.jpg

 

ob2.jpg

Re: VMWare Mouse Click Problem

$
0
0

Spoke too soon - removing WizMouse didn't infact fix the issue.

 

However, reverting to Player 12 *does* fix it.

 

I would advise fixing this in 14 ASAP.

Re: VMware ESXi 6.5.0 intaller fails to recognize Intel Xeon D-1541 x552 NIC

Re: VMware ESXi 6.5.0 intaller fails to recognize Intel Xeon D-1541  x552 NIC

$
0
0

I have downloaded this package but how do I create the the driver for installer i.e. something similar to "net_ixgb.v00"

 

In the driver package I see only the vib file.

 

\update-from-esxi6.5-6.5_update01\vib20\net-ixgbe\VMW_bootbank_net-ixgbe_3.7.13.7.14iov-20vmw.650.0.0.4564106.vib


Re: Get-vmhost shows duplicates

$
0
0

if I connect to vcenter then get-vmhost shows I am connected to the hosts.  these particular connections are not sufficient to run certain commands (one example: Get-VMHostSnmp wont work for me until i have directly connect to the host)

 

if I then direct connect to the hosts, get-vmhost (also get-vm) will return duplicate entries

 

is this not a bug?

 

 

EDIT:

another example is Get-EsxCli requires a connection to both vcenter and the host (during my tests) so I'm destined to have duplicates.  i am confused how others are looping through hosts and vm's without dealing with duplicates.

Re: Old Data Receiving

$
0
0

I wanted to come back and revisit this as we might have this resolved, for now. I installed the vSAN hotfix (2.0.0.7192536) for our Large environments. Actually, all of our vROPs clusters are Large environments, but we do have some vSAN adapters with 200-900 objects.

 

Along with the hotfix above, I also put in some workarounds that were suggested by VMware engineering: We made changes to the below file

 

File:  /usr/lib/vmware-vcops/user/plugins/inbound/VirtualAndPhysicalSANAdapter3/conf/config.properties

 

 

Original File:

 

# Frequency the resource collection should take place

RESOURCE_DISCOVERY_FREQUENCY = 5

 

# vCenter resources cache update frequency

VCENTER_RESOURCE_DISCOVERY_FREQUENCY = 5

 

# Pool sizes for discovery & collection

DISCOVERY_POOL_SIZE = 3

COLLECTION_POOL_SIZE = 5

 

# VIM Client read timeout (ms)

VIMCLIENT_READ_TIMEOUT = 120000

 

 

 

 

Edited File:

# Frequency the resource collection should take place

RESOURCE_DISCOVERY_FREQUENCY = 5

 

# vCenter resources cache update frequency

VCENTER_RESOURCE_DISCOVERY_FREQUENCY = 5

 

# Pool sizes for discovery & collection

DISCOVERY_POOL_SIZE = 3

COLLECTION_POOL_SIZE = 5

 

# VIM Client read timeout (ms)

# VIMCLIENT_READ_TIMEOUT = 120000

 

 

# VMWARE WORKAROUNDS TO VSAN BUG

CIM_SERVICE_PROTOCOL = none

VIMCLIENT_READ_TIMEOUT = 900000

 

 

 

I have this now installed in 2 cluster which were seeing the "Old Data Receiving" issue. I can now say that we seem to be receiving metrics, although, some of the vSAN metrics seem to be 20 mins behind, which I would expect since we increased the READ_TIMEOUT. I will wait for the weekend to pull a full log bundle to confirm the cluster is not seeing the errors pertaining to the vSAN bug.

 

 

I hope everyone else who was affected has this resolved now. I am looking forward to the new vROps release with fixes.

Re: Deploying a VM from a Content Library through the API with Powershell Help

$
0
0

Thanks for the reply.  I guess I should have provided a bit more details.  This is not against a vcenter appliance its against a vcenter server running on windows.

vcenter sever version 6.0.0 build: 5318200

Powercli version:

                         VMware Cis Core PowerCLI Component 6.5 build 6230110

 

                          VMware VimAutomation Core PowerCLI Component 6.5 build 6234650

 

 

 

Not sure this changes things but without the appliance not sure the bypass applies?

Audit when objects put into/removed from maintenance mode

$
0
0

Hi all,

 

We recently had an outage on some hosts while doing some automated upgrades for vCenter servers, via a script.

 

Question:

I wanted to find an audit of when the hosts were put into/removed from maintenance mode.

 

Investigation:

I have checked the User Activity Audit under Admin>History>Audit>User Activity Audit, unfortunately this does not seem to give me the information I am looking for.

I also checked under the Recent Tasks in Admin>History>Recent Tasks, but I see nothing there, and I assume this is only used for the "Actions" adapter.

 

Would anyone know if there is a way to achieve auditing when an object was put into/removed from maintenance mode?

 

 

Thanks!

Re: Audit when objects put into/removed from maintenance mode

$
0
0

You probably won't be able to get exactly this with vROps, but you could with vRLI by watching the logged entries either from the host or from the events stream within vCenter (which is configured when you enable vSphere integration).

ESXi 6.5 Storage issue

$
0
0

I cannot get VMware to recognize a RAID 5 SSD array from within the management console.  It doesn't show any available datastores exist.  If i run the command "esxcli storage nmp device list" it does show the storage array there but does not show it in the console.  I have a separate RAID 5 array from the same RAID controller that has standard SATA drives and that array does show up properly within the console.   Anyone have this issue.. Any suggestions?

Re: Error: Tech preview of vRO vCenter plug-in for vSphere 6.5 - Version 6.5.0.7646854

$
0
0

I upgraded my instance from 6.5.0.6216831 to 6.5.0.7646854 without incident. I wonder if this is a problem with your initial version. Can you change the formatting of your error output so it doesn't truncate the messages? I'm curious what the whole thing says.


Re: Get-vmhost shows duplicates

$
0
0

When you connect to the vCenter and do a Get-VMHost, you see the ConnectionState of the VMHost towards the vCenter.

This doesn't mean that you are connected to all these VMHost.

Check by displaying $global:defaultVIServers

 

And yes, Get-VMHostSnmp does require a connection to a VMHost, it will not work when connected to a vCenter.

 

And no, Get-EsxCli does not require a conenction to the VMHost, it will work with only a connection to the vCenter.

 

In conclusion, this is not a bug, I'm afraid you are misinterpreting the ConnectionState

Re: ESXi 6.5 Storage issue

$
0
0

What hardware is this running (HBA and system itself)?

Re: ESXi 6.5 Storage issue

$
0
0

It is a Lenovo System X server, with an AVAGO RAID controller.

Re: ESXi 6.5 Storage issue

Re: error codes 30

$
0
0

Can you check if the datastore is listed in /vmfs/volumes or can you verify if they have the mapping correctly..

 

Thanks,

MS

Viewing all 247559 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>