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

Re: dont run unprovision when buildmachine fails

December 1, 2019, 3:28 pm
$
0
0

You have a couple options.

 

If you are attempting to create DNS/AD in PRE-BuildingMachine and it fails because the records already exist for another machine, the provisioning will finish all remaining subscriptions in PRE-BuildingMachine and then move to PRE-Disposing. As a result you should have your cleanup activity for AD/DNS occur in the lifecycle state PRE-UnprovisionMachine (if you need blocking) or POST-UnprovisionMachine (no blocking) if it can only occur after the VM is destroyed; these subscriptions will never run in the above use case. This could be an issue if you do legitimately create new records in DNS/AD but another blocking subscription within PRE-BuildingMachine fails; it will never move to PRE-UnprovisionMachine as the VM was never created and thus will not clean up your created records.

 

If you can't or don't want the cleanup to occur within PRE-MachineProvisioned then you will need to extend your VM with a custom property. During the EBS that is supposed to create the DNS/AD records, add a custom property to your IaaS VM (vCAC:Entity) with the result (e.g., needToCleanRecords=true). Then ether filter your PRE-Disposing subscription by that property (if it has no need to run at all) or check it within the vRO workflow itself.

 

Of course this entire problem is solved when you're generating new names for every VM you provision. Forcing state changes will not help you in this case and I generally recommend never doing it.

↧
Search

Re: VRA8 - Service broker action policy

December 1, 2019, 3:30 pm
$
0
0

Action policies are not available in vRA 8; the feature was added to vRAC (Cloud Service Broker) after the feature freeze.

 

I would guess that it's currently slated for vRA 8.1 (not 8.0.1).

↧
↧

Re: Requesting a Catalog item with custo form Using REST API

December 1, 2019, 3:33 pm
$
0
0

You cannot request a catalog item using the custom forms through the API.

 

Custom Forms themselves are just a wrapper for requesting via the standard request template.

 

Whatever is running your API call should be doing everything programmatically or it has it's own UI (XaaS, vRO workflow, external script/service, etc.)

↧

Re: I need help with Actions after upgrade of vRO

December 1, 2019, 4:04 pm
$
0
0

The dunes path has changed for objects in the vCenter plug-in. As Illiav said the plug-in was completely redone and is one reason why accessing objects through the full dunes path is not a good idea.

 

You need to change your find to this (I have bolded the relevant part):

 

var dunesId =

"dunes://service.dunes.ch/CustomSDKObject?id='" +

vc.id +

",id:" +

id +

"'&dunesName='VC:" +

type +

"'";

foundObjects.push(dunesId);

 

You should also be doing a System.isNotFound() before adding it to the vm array when doing Server.fromUri(dunesId); as the return type is NotFound from that method (rather than null or undefined) you are getting the error on .split instead of simply accessing the .name property of vm1 or vm2.

 

As for when you attempted to do System.log(vm1.name) and got the parsing error, I'm assuming you tried to put inside the var lexicographical =  instantiation which is one statement split across four lines (notice the commas).

 

Finally, as an aside, this whole thing is a nightmare to read and you should really redo your entire approach if you can.

↧

Re: Infoblox plugin - Allocate workflow input

December 1, 2019, 4:09 pm
$
0
0

It's a known issue with the Infoblox implementation. I actually thought it got fixed a while ago? People had to update the record in Infoblox after the fact (identifying the record via IP Address).

 

What version of vRA and Infoblox?

↧
↧

Workstation crashes as soon as I try to run VM on Kali Linux

December 1, 2019, 4:10 pm
$
0
0

Hey guys, super new to the scene here and trying to get my berrings. Finding out I may have been overconfident and installed Kali too early because I've had errors that I've had to work through on almost every installation (including linux itself), but have been working through each problem in good time with a quick web search. This is the first thing I've gotten truly stuck on, so forgive me for lacking some technical terms etc.

     I downloaded Workstation (free) and also installed metasploit 2. Unzipped and tried to run with the vmx file as instructed, and as it said "connecting", all of a sudden it just said 'error' super fast and Workstation crashed. I tried multiple times, then re-installed metasploit. Also tried downloading an SSH shell but the guide to downloading an SSH led me to a non-working command. Tried to open a non metasploit virtualmachine as well, both crash immediately and dont even show me an error message now. As soon as I hit run it just crashed. Reinstalled Workstation, same issue occurring. Tried to run this: vmplayer /path/to/virtual machine

and got

failed to load external entity "/etc/vmware/hostd/proxy.xml"

vmplayer: Too many arguments; only one virtual machine can be specified at a time.

Try 'vmplayer --help' for more information.

How do I upload my logs?

 

Thanks in advance!

 

x-manlord

↧

Re: 仮想マシンの　ハードウェアバージョン　を　複数仮想マシン同時に上げる方法について

December 1, 2019, 4:30 pm
$
0
0

ご回答ありがとうございます。

 

まさに、探していた方法でした。

全VM名取得→全仮想マシンバージョンアップスクリプト流す→再起動指示

 

という流れで解決できそうです。

 

ありがとうございました。

↧

Re: VMs run a higher CPU load on Catalina

December 1, 2019, 5:41 pm
$
0
0

This seems to have done the trick.

 

Thanks heaps

↧
Search

Re: Update to 6.7u3 failed

December 1, 2019, 6:11 pm
$
0
0

The hostd logs are just repetitions of what is pasted below. It did mention that port 9095 was not running, but we could not determine which service was using that port.

 

Hostd logs:

 

2019-11-29T01:53:43.390Z warning hostd[2101652] [Originator@6876 sub=SessionOrientedStub[0] opID=7c4de4b3] Invoke method vim.host.VsanSystemEx.GetVsanRuntimeInfo failed: N7Vmacore15SystemExceptionE(Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections.)

--> [context]zKq7AVICAgAAAASD2gAOaG9zdGQAACxONmxpYnZtYWNvcmUuc28AALC+GwCQnBcAiskoANkbLQCAHi0A3SItAOEqLQAVaSkAteUoAJPpKACrxDYBO30AbGlicHRocmVhZC5zby4wAAJ9nw5saWJjLnNvLjYA[/context]

2019-11-29T01:53:43.391Z warning hostd[2101652] [Originator@6876 sub=Hostsvc.HaHost opID=7c4de4b3] Fail to get VsanSystem runtime info.Maybe VSAN isn't started? Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections.

2019-11-29T01:53:43.391Z warning hostd[2101652] [Originator@6876 sub=PropertyProvider opID=7c4de4b3] It took 10011677 microseconds, 00:00:10.011677 (hh:mm:ss.us), to get property summary for vim.HostSystem:ha-host

2019-11-29T01:53:43.390Z error hostd[2101562] [Originator@6876 sub=vmomi.soapStub[0]] Resetting stub adapter for server <cs p:0000007a374eae00, TCP:localhost.localdomain:9095> : service state request failed: N7Vmacore15SystemExceptionE(Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections.)

--> [context]zKq7AVICAgAAAASD2gAOaG9zdGQAACxONmxpYnZtYWNvcmUuc28AALC+GwCQnBcAiskoANkbLQCAHi0A3SItAOEqLQAVaSkAteUoAJPpKACrxDYBO30AbGlicHRocmVhZC5zby4wAAJ9nw5saWJjLnNvLjYA[/context]

2019-11-29T01:53:43.460Z warning hostd[2101562] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x0000007a38e02800, h:28, <TCP '127.0.0.1 : 56351'>, <TCP '127.0.0.1 : 9095'>>, e: 111(Connection refused)

2019-11-29T01:53:45.462Z warning hostd[2101985] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x0000007a391228e0, h:28, <TCP '127.0.0.1 : 47015'>, <TCP '127.0.0.1 : 9095'>>, e: 111(Connection refused)

2019-11-29T01:53:45.463Z warning hostd[2102313] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x00000079b9b88720, h:19, <TCP '127.0.0.1 : 38140'>, <TCP '127.0.0.1 : 9095'>>, e: 111(Connection refused)

2019-11-29T01:53:45.463Z error hostd[2102313] [Originator@6876 sub=vmomi.soapStub[0]] Resetting stub adapter for server <cs p:0000007a374eae00, TCP:localhost.localdomain:9095> : service state request failed: N7Vmacore15SystemExceptionE(Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections.)

 

vpxa.logs:

 

2019-11-29T01:52:19.725Z - time the service was last started, Section for VMware ESX, pid=2101804, version=6.7.0, build=14320388, option=Release

2019-11-29T01:52:19.725Z info -[2101804] [Originator@6876 sub=Default] Glibc malloc guards disabled.

2019-11-29T01:52:19.725Z info -[2101804] [Originator@6876 sub=Default] Initialized SystemFactory

2019-11-29T01:52:19.748Z warning vpxa[2101804] [Originator@6876 sub=vpxLro] [VpxLRO] 98 requested for task.maxThreads exceedsmax allowed; capping to 32

2019-11-29T01:52:19.763Z error vpxa[2101804] [Originator@6876 sub=Default] [VimXml] Error fetching /sdk/vimServiceVersions.xml: 503 (Service Unavailable)

2019-11-29T01:52:19.763Z warning vpxa[2101804] [Originator@6876 sub=Default] Closing Response processing in unexpected state: 3

2019-11-29T01:52:19.763Z error vpxa[2101804] [Originator@6876 sub=Default] Can not discover support for WSDL namespace vim25

2019-11-29T01:52:19.763Z warning vpxa[2101804] [Originator@6876 sub=hostdcnx] Could not resolve version for authenticating to host agent

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Using default for nonChunkingAgents

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Using default for agentsNeedingContentLength

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Max buffered response size is 104857600 bytes

2019-11-29T01:52:20.569Z warning vpxa[2101804] [Originator@6876 sub=Default] Document root directory not found at /etc/vmware/vpxa/docRoot

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Using default for nonChunkingAgents

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Using default for agentsNeedingContentLength

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Max buffered response size is 104857600 bytes

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Http Service started: <server <acceptor p:0x000000699d9d4900, h:12, <TCP '127.0.0.1 : 8089'>>, >

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Using default for nonChunkingAgents

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Using default for agentsNeedingContentLength

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Max buffered response size is 104857600 bytes

2019-11-29T01:52:20.569Z warning vpxa[2101804] [Originator@6876 sub=Default] Document root directory not found at /etc/vmware/vpxa/docRoot

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Using default for nonChunkingAgents

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Using default for agentsNeedingContentLength

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Max buffered response size is 104857600 bytes

2019-11-29T01:52:20.569Z info vpxa[2101804] [Originator@6876 sub=SoapAdapter.HTTPService] Http Service started: <server <acceptor p:0x000000699d9fe4b0, h:13, <UNIX '/var/run/vmware/proxy-vpxa'>>, >

2019-11-29T01:54:03.810Z warning vpxa[2101822] [Originator@6876 sub=VpxProfiler] InvokeWithOpId [TotalTime] took 84042 ms

2019-11-29T01:54:13.838Z warning vpxa[2101818] [Originator@6876 sub=vpxaAuthorize opID=lro-2541221-7ded7eb1-43] No auth data found for privileged operation:method=setServer

2019-11-29T01:55:04.361Z warning vpxa[2101815] [Originator@6876 sub=hostdstats] Host to vpxd translation is empty, dropping results

2019-11-29T01:55:04.362Z warning vpxa[2101815] [Originator@6876 sub=VpxProfiler] InvokeWithOpId [TotalTime] took 44591 ms

2019-11-29T01:55:14.392Z warning vpxa[2101825] [Originator@6876 sub=VpxProfiler opID=SWI-3113c398] InvokeWithOpId [TotalTime] took 10034 ms

2019-11-29T01:55:24.367Z warning vpxa[2101815] [Originator@6876 sub=hostdstats] Host to vpxd translation is empty, dropping results

2019-11-29T01:55:44.369Z warning vpxa[2101824] [Originator@6876 sub=hostdstats] Host to vpxd translation is empty, dropping results

↧
↧

Re: ESXi 6.5 cannot login with new local user

December 1, 2019, 6:13 pm
$
0
0

pam_tally2 --user esximon --reset won't help, still can't login

cat /etc/security/access.conf

+:dcui:ALL

+:root:ALL

+:vpxuser:ALL

+:vslauser:ALL

-:esximon:ALL

-:ALL:ALL

 

I guess the clue is in the minus?

↧

Re: ESXi 6.5 cannot login with new local user

December 1, 2019, 6:25 pm
$
0
0

So I just edited cat /etc/security/access.conf to

+:dcui:ALL

+:root:ALL

+:vpxuser:ALL

+:vslauser:ALL

+:esximon:ALL

-:ALL:ALL

 

and now esximon is able to login. I think the problem is solved but I still have some questions about the access.conf and its rules.

↧

Re: vShere6.5→vShere6.5U2適用方法について

December 1, 2019, 6:25 pm
$
0
0

kawamanさん

 

ご回答頂き有難うございます。

 

追加の質問となり申し訳ないのですが

 

■質問1

今回、U2適用対象であるvCenterはVCSAとなります。

VCSAが導入されているESXiもU2適用対象ですが、作業手順としては以下のURLにある通り

先にVCSAをU2適用してからESXiを適用する認識で大丈夫でしょうか。

※URLにある仮想アプライアンスのアップグレードがVCSAに該当しないかを気にしています。

 

vSphere のアップグレード プロセスの概要

 

■質問2

ESXi、VCSAのU2適用に際して、現在運用している機器情報を調査する予定です。

以下の観点で調査する予定ですが、その他追加で確認すべき項目はありますでしょうか。

・以下を参考にvMotionで退避した際に、キャパシティ上、問題が無いか確認

あとどのくらい仮想マシンを載せられるか（リソースの残量を知る）〜 VMware vCenter Operations Manager活用法（第1回） - Japan Cloud Infrastructure Blog - VMware Bl…

・ESXiのU2になった時にHW(DL380　Gen９)がサポートされているかを以下のURLで確認

VMware Compatibility Guide - System Search

 

・ESXiとvCenterの組み合わせがサポートされているか確認

VMware Product Interoperability Matrices

 

以上、よろしくお願いします。

↧

Port Forward on VMWare Workstation, But Range not a Port

December 1, 2019, 6:54 pm
$
0
0

Hi everyone, thanks for helping me,

1. I installed VMWare Workstation 15.5 on Windows Server 2019

2. I use NAT to Port Forward and it's working well from NAT8

3. I want to Forward UDP ports 10000 - 19999 but it's a huge range

I can only forward a port, how can I forward many ports at the same time???

=============================

Second way:

1. I tried to use bridge mode

2. I set bridge mode to specific adaptor

3. but my VM never get IP from DHCP

4. I added IP manually and it's not working well

how can I use bridge mode for my VM to get IP to how can I set Manual IP to works well

 

My VM OS: Kerio Operator

Thanks a lot

↧
↧

Re: vShere6.5→vShere6.5U2適用方法について

December 1, 2019, 6:59 pm
$
0
0

■質問1

今回、U2適用対象であるvCenterはVCSAとなります。

VCSAが導入されているESXiもU2適用対象ですが、作業手順としては以下のURLにある通り

先にVCSAをU2適用してからESXiを適用する認識で大丈夫でしょうか。

※URLにある仮想アプライアンスのアップグレードがVCSAに該当しないかを気にしています。

vSphere 6.5のUpgrade順序に関するKBとして以下があります。

https://kb.vmware.com/s/article/2147289

結論として、vCSAを先にUpgradeするので正しいです。（※現状でVCSAとESXiの相互運用性がある前提）

ちなみにですが、VCSAのバックアップ＆リストアを考慮される場合、VDSしかない環境においては、VCSA/PSCが所属するdvportgroup と同じVLAN＆サブネットに接続されるEphemeralポートを作成しておくことがおすすめです。（※VCSAがない状態では、vDSのPGに仮想マシンをアサインできないため）

 

■質問2

ESXi、VCSAのU2適用に際して、現在運用している機器情報を調査する予定です。

以下の観点で調査する予定ですが、その他追加で確認すべき項目はありますでしょうか。

・以下を参考にvMotionで退避した際に、キャパシティ上、問題が無いか確認

あとどのくらい仮想マシンを載せられるか（リソースの残量を知る）〜 VMware vCenter Operations Manager活用法（第1回） - Japan Cloud Infrastructure Blog - VMware Bl…

・ESXiのU2になった時にHW(DL380　Gen９)がサポートされているかを以下のURLで確認

VMware Compatibility Guide - System Search

 

・ESXiとvCenterの組み合わせがサポートされているか確認

VMware Product Interoperability Matrices

こちらについてはそれくらいかなぁ、という気がしますね。

vSphereと連携するソリューション（NSXやVDP、もしくはサードパーティのバックアップソリューションなど）がある場合は、別途Upgrade後のvSphereとの互換性を確認する必要がありますね。

↧

Re: Workstation crashes as soon as I try to run VM on Kali Linux

December 1, 2019, 7:16 pm
$
0
0

EDIT update: Just tried to switch my network setting to Bridged instead of NAT, same error. Did see this pop up once though: "Launch error. Failed to run VMware-player.desktop. timeout was reached. Any suggestions??

 

anything i can do to make my question better, such as help with how to find my logs and put them here, I'll certainly do whatever I can.

↧
Search

Re: Can I use nVidia Quadro P4000 in vSGA mode?

December 1, 2019, 7:25 pm
↧

Re: vSphere 6.7 ICM Course

December 1, 2019, 7:48 pm
$
0
0

Hello friends,

 

 

please help me to get more information about that how many hours of theory training and how many hours of LAB available in ON DEMAND format in VCP vsphere or NSX ?

 

Thank you..

↧
↧

Re: vShere6.5→vShere6.5U2適用方法について

December 1, 2019, 8:28 pm
$
0
0

▼ 回答1

アップグレードの順番としてはご認識の通り、基本は親となる vCenter (vCSA) をバージョンアップ後に、子となる ESXi をバージョンアップするのが通常です。

※ 確認いただいている VMware Product Interoperability Matrices  にある様に、vCSA をバージョンアップしなくても ESXi の次のバージョンがサポートされる場合は ESXi のみパッチを適用する事もあります。

 

参照先のページにある、「仮想マシン・仮想アプライアンスのアップグレード」は仮想マシンハードウェアバージョンや VMware Tools のアップグレードを意味します。

 

▼ 回答2

事前調査については、記載いただいた片寄時のリソースが満たせるか、ハードウェアのコンパチが満たしているか、

クラスタを構成するコンポーネント間のコンパチが満たせているかの3点と合わせて、

もう一点確認する点として、サーバーメーカー側の BIOS・Firmwear のサポート情報も併せて確認した方が良いです。

 

バージョンアップ時に利用するバイナリを今回は DL380Gen8 用になると思いますので、

HPE と VMware がリリースしているパッケージをあらかじめ入手して、Dry Run でドライバなど各パッケージの前後バージョンを確認しておくのも有効かと思います。

 

 

後、ESXi 自体のエラーやアラート、空き容量なども確認して必要であれば事前に解決しておくのが良いかと思います。

長期稼働し続けている環境の場合、作業前（1週間前など）に順々に VM を退避させて ESXi を再起動をしておけば、当日の作業時間の確認にもなりますし、

再起動する事でキャッシュなどもクリアされて、潜んでいるかも知れない不具合を知ることもできるので安定したバージョンアップの本番に臨むことが出来ます。

↧

Could not establish secure channel for SSL/TLS with authority using PowerCLI.

December 1, 2019, 9:38 pm
$
0
0

I've already set the invalid certificate action to ignore.

Able to connect to vcenter using the web or desktop client just fine,

↧

Re: Could not establish secure channel for SSL/TLS with authority using PowerCLI.

December 1, 2019, 9:46 pm
$
0
0

Try running this before

 

[System.Net.ServicePointManager]::SecurityProtocol =[System.Net.SecurityProtocolType]::Tls11,[System.Net.SecurityProtocolType]::Tls12

↧
Viewing all 198737 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>