Re: No compatible network adapter found
Powercli script to list "Status Details" for incompatible vibs during upgrade
Hi,
I'm plagiarized a script that will remove incompatible vibs but I'm struggling with getting the list of incompatible vibs in the "Status Details" after a baseline scan. For example, Mellanox_bootbank_net-mst_2.0.0.0-1OEM.550.0.0.472560 found under "Status Details".
Currently I have to manually select that with my script. If I could get this information with a script automagically the script would be a bit more seamless. Any help would be appreciated.
Re: Is there a script available to determine LUN / datastore GPT corruption?
If the the New-SshSession fails due to incorrect credentials, you should also see an error message like "New-SSHSession : Permission denied (keyboard-interactive)."
Do you get that kind of message?
Re: Powercli script to list "Status Details" for incompatible vibs during upgrade
I'm afraid that functionality is missing.
See also
Which script are you using?
Re: Is there a script available to know how many times a virtual machine has migrated off to different hosts in last 24-48hrs ?
If Host2 and Time2 are empty, you are most probably looking at an svMotion, not a vMotion.
The value in Host1 is directly obtained from the event, if that is missing, there might be an issue with your events.
Can you share what you are seeing?
Re: Powercli script to list "Status Details" for incompatible vibs during upgrade
Thanks for the reply. Here is what I have so far which works well but I'm sure it could be written better. Might help someone out though.
$Combo1 = "net-mst"
#Removes
#Mellanox_bootbank_net-mst_2.0.0.0-1OEM.550.0.0.472560
$Combo2 = "scsi-mpt3sas"
#Removes
#LSI_bootbank_scsi-mpt3sas_04.00.00.00.1vmw-1OEM.500.0.0.472560
$Combo3 = "scsi-lpfc820","net-mst"
#Removes
#Emulex_bootbank_scsi-lpfc820_8.2.4.157.70-1OEM.500.0.0.472560
#Mellanox_bootbank_net-mst_2.0.0.0-1OEM.550.0.0.472560
$Combo4 = "scsi-qla2xxx","net-mst"
#Removes
#qlogic_bootbank_scsi-qla2xxx_911.k1.1-26OEM.500.0.0.472560
#Mellanox_bootbank_net-mst_2.0.0.0-1OEM.550.0.0.472560
$Combo5 = "scsi-qla2xxx","scsi-lpfc820"
#Removes
#qlogic_bootbank_scsi-qla2xxx_911.k1.1-26OEM.500.0.0.472560
#Emulex_bootbank_scsi-lpfc820_8.2.2.126.50-1OEM.500.0.0.472560
$Combo6 = "scsi-lpfc820","scsi-qla2xxx","net-mst"
#Removes
#Emulex_bootbank_scsi-lpfc820_8.2.4.157.70-1OEM.500.0.0.472560
#qlogic_bootbank_scsi-qla2xxx_934.5.20.0-1OEM.500.0.0.472560
#Mellanox_bootbank_net-mst_2.0.0.0-1OEM.550.0.0.472560
$Combo7 = "scsi-mpt3sas","net-bna","scsi-qla2xxx","scsi-bfa","scsi-mtip32xx-scsi"
#Removes
#LSI_bootbank_scsi-mpt3sas_04.00.00.00.1vmw-1OEM.500.0.0.472560
#Brocade_bootbank_net-bna_3.2.0.0-1OEM.500.0.0.472560
#qlogic_bootbank_scsi-qla2xxx_934.5.20.0-1OEM.500.0.0.472560
#Brocade_bootbank_scsi-bfa_3.2.0.0-1OEM.500.0.0.472560
#Micron_bootbank_scsi-mtip32xx-scsi_2.4.10-1OEM.500.0.0.472560
$vibList = $Combo2 # select the comination of vibs to remove
Write-host "You are about to remove the following VIBs from the following hosts"
Write-host "-----------------------"
Write-output $vibList
Write-host "-----------------------"
Write-output $VMhostList.name
Pause
foreach($VMhost in $VMHostList.name){
write-host $VMhost
Write-host "------------------"
foreach ($vib in $vibList){
$esxcli = Get-EsxCli -VMHost $VMhost -V2
$esxliRemoveVibArgs = $esxcli.software.vib.remove.CreateArgs()
$esxliRemoveVibArgs.dryrun = $false # change this to true for testing only
$vibs = $esxcli.software.vib.list.Invoke() | where {$_.Name -match $vib}
foreach ($vib in $vibs){
$esxliRemoveVibArgs.vibname = $vib.Name
$esxcli.software.vib.remove.Invoke($esxliRemoveVibArgs)
}
}}
Pause
Write-host "Hosts will be rebooted"
Write-output $VMhostlist
Foreach ($vmhost in $VMhostlist){
$ismaint = get-VMhost $vmhost.name | select ConnectionState
If ($ismaint.ConnectionState = "Maintenance") {
$eventManager = Get-View eventManager
$vmhost = Get-VMHost -Name $vmhost.name
$message = "Patching and Upgrades"
$eventManager.LogUserEvent($vmhost.ExtensionData.MoRef,$message)
Restart-VMHost $vmhost -Confirm
}
}
Remove-Variable * -Force -ErrorAction SilentlyContinue
#End of script.
Re: Powercli script to list "Status Details" for incompatible vibs during upgrade
Thanks for sharing
Re: Patching/Updating a VCHA not updating
Costum reports in vRops 6.2
What's VRealize Operations
2-node cluster with witness local to one node
I know this would not be a supported production configuration but is it possible to run a 2-node VSAN cluster with the witness appliance living on one of two hosts? If this does work from a functional perspective are there any special considerations around configuration? Appreciate any feedback that is provided.
Re: Installation of Mavericks as VM in Fusion 8.5 Halts at Install Copy of OSX
Ahh, interesting, but that makes sense. Developer program is probably the best way to get a new (legit) installer. It's $99 for the year.
Re: Patching/Updating a VCHA not updating
stopped all services then started all services NO CHANGE
I always use FQDN
I used ip address and got same results
The vpxd.log is too large to attach to the message can I email it to you?
vcenter is still down.
Re: HA host failure/isolation
ЦОД - это не про нас....
резервная серверная ещё в процессе создания и там действительно пока 1 коммутатор на LAN, в проекте к нему в пару будет второй.
Вопрос не в этом. Давайте будем считать, что было смоделировано потеря сетевой связности до резервной серверной (и основной и резервный каналы связи LAN сети в обрыве), ок?
Re: 2-node cluster with witness local to one node
Hello MBrownWFP,
It's unsupported due to the fact that if you lose the node that the Witness components and/or VM reside on, you lose access to 2/3 of the components of all Objects and thus lose quorum and thus these become inaccessible - e.g. this wouldn't provide FTT=1 which is the main purpose of a 1+1+1 or 2+1 cluster.
Don't even consider doing this, not because it is 'unsupported' but because of the fundamental reasons of why it is unsupported.
Bob
Re: vRA 7.5 - Virtual Machine "Monitor" tab
If i click on the Monitor tab selecting the Virtual Machine in my Deployment i see "No Data".
And this is in vROps, right? If so, two things:
- Please move this thread to vROps.
- Check the adapters to ensure it's actually collecting data on the vRA management pack.
Re: best way to build the lab
I would probably deploy ESXi on top of this hardware. This is also not strictly a vRA question and so I'd move to a more appropriate sub-forum so it gets more responses.
VC shows VM powered on from Detached Datastore
All,
I'm stuck, or I should say 2 VM's are stuck in a Powreed On state. This started when my system took a power hit and rebooted with everything up. Nothing good comes from that as we all know. I have 3 Datastores
Primary (Virtual Machines Vitrual-Center-Active, NSX-Manager-Active & NSX-Edge-Active)
Secondary (Virtual Machines Vitrual-Center-Secondary, NSX-Manager-Secondary & NSX-Edge-Secondary)
Recovery (Virtual Machines Vitrual-Center-Recovery, NSX-Manager-Recovery & NSX-Edge-Recovery)
When I powered the ESXi Hosts up. I found the Primary Datastore wasn't seen. I attempted to mount it but it was coming back as Corrupted. Not a problem as I have two other Datastores to recover to, or so I thought. I powered up the VC on the Secondary Datastore, log in and see NSX-Manager-Active & NSX-Edge-Active (from the Primary Datastore) as powered on. As the Datastore wasn't attached I new these were remnants. They show as powered on in PowerCLI, I've tried to remove them using PowerCLI but no luck.
Anyone have a solution?
ovftool drops query parameters for http sources
Why does ovftool appear to drop the query parameters for HTTP OVA sources? I have an OVA stored in an S3 like storage and am trying to use a presigned URL as the source to ovftool.
$ ovftool --X:logLevel=trivia --X:logToConsole 'http://192.168.39.196/ovas/dsl.ova?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=minioadmin%2F20190829%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190829T013555Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=xxx'
2019-08-28T18:52:12.098-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] [SSL_DB] Using /home/rwallace/.ovftool.ssldb as SSL DB
2019-08-28T18:52:12.102-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Subscribing to signal: 2 (SIGINT)
2019-08-28T18:52:12.102-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Subscribing to signal: 4 (SIGILL)
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Subscribing to signal: 6 (SIGABRT)
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Subscribing to signal: 8 (SIGFPE)
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Subscribing to signal: 15 (SIGTERM)
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Subscribing to signal: 1 (SIGHUP)
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Subscribing to signal: 3 (SIGQUIT)
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Subscribing to signal: 5 (SIGTRAP)
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Subscribing to signal: 9 (SIGKILL)
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Subscribing to signal: 13 (SIGPIPE)
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Initializing progress
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] OvfTool Version: VMware ovftool 4.3.0 (build-7948156)
2019-08-28T18:52:12.103-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Using home directory: ./.ovftool
2019-08-28T18:52:12.104-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Curl Version: 7.58.0
2019-08-28T18:52:12.104-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Done initializing libs
2019-08-28T18:52:12.104-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Determining source
2019-08-28T18:52:12.104-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Constructing URL...
2019-08-28T18:52:12.105-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Determining target
2019-08-28T18:52:12.105-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Getting source
2019-08-28T18:52:12.105-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Parsing URL...
2019-08-28T18:52:12.105-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Constructing URL...
2019-08-28T18:52:12.105-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Constructing URL...
2019-08-28T18:52:12.105-07:00 info OVFTool[61924] [Originator@6876 sub=Default] ReaderFactory web request: http://192.168.39.196/ovas/dsl.ova?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=minioadmin%2F20190829%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190829T013555Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=xxx, noBody=true
2019-08-28T18:52:12.105-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Initializing new curl session
2019-08-28T18:52:12.105-07:00 trivia OVFTool[61924] [Originator@6876 sub=Default] Using HIGH OpenSSL ciphers suite.
2019-08-28T18:52:12.106-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: Trying 192.168.39.196...
-->
2019-08-28T18:52:12.106-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: TCP_NODELAY set
-->
2019-08-28T18:52:12.106-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: Connected to 192.168.39.196 (192.168.39.196) port 9001 (#0)
-->
2019-08-28T18:52:12.106-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: header data hidden
2019-08-28T18:52:12.107-07:00 trivia OVFTool[61930] [Originator@6876 sub=Default] CURL: Connection #0 to host 192.168.39.196 left intact
-->
2019-08-28T18:52:12.107-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Constructing URL...
2019-08-28T18:52:12.108-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Curl session torn down
Error: Could not open URL http://192.168.39.196:9001/ovas/dsl.ova (response code: 403)
2019-08-28T18:52:12.108-07:00 verbose OVFTool[61924] [Originator@6876 sub=Default] Backtrace:
--> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-7948156, tag: OVFTool, cpu: x86_64, os: linux, buildType: release
--> backtrace[00] libvmacore.so[0x00356204]: Vmacore::System::Stacktrace::CaptureWork(unsigned int)
--> backtrace[01] libvmacore.so[0x001C35B4]: Vmacore::System::SystemFactory::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
--> backtrace[02] libvmacore.so[0x0018426B]: Vmacore::Throwable::Throwable(std::string&&)
--> backtrace[03] ovftool.bin[0x001FFD76]
--> backtrace[04] ovftool.bin[0x001FCD8A]
--> backtrace[05] ovftool.bin[0x001FDDF8]
--> backtrace[06] ovftool.bin[0x001FEB54]
--> backtrace[07] ovftool.bin[0x001FF234]
--> backtrace[08] ovftool.bin[0x002003C5]
--> backtrace[09] ovftool.bin[0x00200DA5]
--> backtrace[10] ovftool.bin[0x0026B4C1]
--> backtrace[11] ovftool.bin[0x00174CCA]
--> backtrace[12] ovftool.bin[0x001EFEC5]
--> backtrace[13] ovftool.bin[0x001467E7]
--> backtrace[14] libc.so.6[0x00022B8E]
--> backtrace[15] ovftool.bin[0x0014E6B9]
--> [backtrace end]
The request fails because ovftool tries to get the file as just "http://192.168.39.196:9001/ovas/dsl.ova ", without any signatures or anything, which results in the 403 Forbidden response.
Why does ovftool do that? Is there a way to prevent it from doing that? If there isn't now, can it be fixed in the future?
Thanks,
Rich
Re: AppVolumes | Applications not displaying in Start Menu
Are the Start Menu shortcuts present during the provisioning phase?
Can you see the app shortcuts in "C:\ProgramData\Microsoft\Windows\Start Menu\Programs" pre, and post provisioning?