本記事では、VxRailやお客様環境においてvSAN健全性テストにて無視が可能なアラートや項目に抑止（Skip）設定をする方法を記載します

※画像はクリックすることで拡大可能です

■概要

VxRail 4.5（vSAN6.6、vSphere 6.5）から、vSAN健全性テストの項目が増えインターネット接続を要求する機能に関するテストも追加されました

vSANビルドに関する推奨事項エンジンの健全性は非インターネット接続環境では必ず警告になるので無視しても問題ありません

なお、vSAN6.6からの新機能でvSAN健全性テストの項目を個別にスキップ(Silence)することができるようになりました

警告が表示されること自体を望まない場合は、該当の項目をスキップしてください

また、VxRailでは下記に関連する項目も無視することが可能です

・Hardware compatibilityに関連する項目(HCLDB, VMware certified等)：HardwareやFirmwareなどがVxRail Version毎に管理されているため

・VUMに関連する項目：VxRail ManagerからUpgradeを管理しているため

・vSAN Build Recommendation（vSANビルドに関する推奨事項）に関連する項目

     ‐ vSANビルドに関する推奨事項エンジンの健全性(vSAN Build Recommendation Engine Health)：非インターネット接続環境では必ず警告になるため

     ‐ vSAN build recommendation：Upgradeのリリース等はVxRail側で管理しているため

     ‐ vSAN release catalog up-to-date：Upgradeのリリース等はVxRail側で管理しているため

・vSAN Support Insight：VxRailおよびDELL EMC側では使用していないため

■vSAN健全性テスト項目の抑止方法

vSAN Build Recommendation Engine Health(vSAN ビルドに関する推奨事項エンジンの健全性)のテスト項目を例に記載します

・VxRail4.7(vSAN6.7, vSphere6.7)の場合

VxRail4.7ではGUI上から設定することが可能です

1. vSAN健全性テストの項目に移動し、抑止したいテスト項目のvSAN健全性テストのグループを選択

2. 抑止したいテスト項目をクリックし、テスト項目の詳細が表示されたことを確認し「Silence Alert」をクリック

　※選択されたアラートが抑止したいテスト項目であることを確認して実施してください

3. 警告がでるので「YES」を選択

4. vSAN健全性テストの「RETEST」を実施

5. テスト項目が抑止されたことを確認

　抑止されると、チェック部分がグレーのマークに変わり、「Restore Alert」というメニューが表示されるようになります

・VxRail4.5(vSAN6.6, vSphere6.5)の場合

VxRail4.5ではRVCを使用することで設定可能です

1. vCenterにSSHでrootログイン

　SSH有効化手順は下記のコミュニティを参考にしてください

　https://communities.vmware.com/docs/DOC-39994

2. Bashシェルでは無い場合、Bashシェルに遷移

Command> shell.set --enabled True

Command> shell

Shell access is granted to root

root@vc [ ~ ]#

3. RVCにログイン

root@vc [ ~ ]# rvc administrator@vsphere.local@localhost　< vCenter SSO ユーザー名@localhostを入力

Install the "ffi" gem for better tab completion.

password:                                      < vCenter SSO パスワードを入力

0 /

1 localhost/

>

4. ls、cdコマンドでvSANクラスターリソースのパスを特定

5. 下記のコマンドで現在の健全性テストのSilent Statusを確認、及びスキップする対象のHelth Check IDを特定

　vsan.health.silent_health_check_statusのコマンドで確認します

vsan.health.silent_health_check_status /localhost/データセンター名/computers/vSANクラスターリソース

"Silent Status"の状態がNormalとなっている場合は、通常通りvSAN健全性テストの対象となっている状態です

カレントディレクトリが既に"/localhost/データセンター名/computers/vSANクラスターリソース"まで到達している場合は、

下記のようにコマンドの引数を省略もできます

vsan.health.silent_health_check_status 0

~~ 中略 ~~

6. 対象の項目のHelth Check IDを指定してSilent状態へ変更

　※vSAN ビルドに関する推奨事項エンジンの健全性の場合は、vumconfigを指定してください

　vsan.health.silent_health_check_configure -a のコマンドで変更可能です

vsan.health.silent_health_check_configure -a [Health Check Id] /localhost/データセンター名/computers/vSANクラスターリソース

実行例

/localhost/VxRail-Datacenter/computers> vsan.health.silent_health_check_configure -a vumconfig 0
Successfully update silent health check list for VxRail-Virtual-SAN-Cluster-5805c8ee-xxxx-xxxx-xxxx-xxxxxxxxxxxx

/localhost/VxRail-Datacenter/computers>

7. Step 5（vsan.health.silent_health_check_status）を実施してSilentに変わったことを確認

■vSAN健全性テスト項目の抑止解除方法

・VxRail4.7(vSAN6.7, vSphere6.7)の場合

1. 抑止されているテスト項目を選択し、「Restore Alert」をクリック

「Restore Alert」の項目が、「Silence Alert」に変わったことを確認しvSAN健全性テストを実施

・VxRail4.5(vSAN6.6, vSphere6.5)の場合

1. Silentにしたテスト項目をNormalに戻したい場合は抑止方法と同じ要領でRVCを使用し、設定します

vsan.health.silent_health_check_configure -r のコマンドで設定可能です

vsan.health.silent_health_check_configure -r [Health Check Id] /localhost/データセンター名/computers/vSANクラスターリソース名

実行例

/localhost/VxRail-Datacenter/computers> vsan.health.silent_health_check_configure -r vumconfig 0
Successfully update silent health check list for VxRail-Virtual-SAN-Cluster-5805c8ee-d3cd-4af5-9988-bcbe0d7715e9

/localhost/VxRail-Datacenter/computers>

■vCenterのアラーム定義を無効化

RVCの使用が難しい場合は、vCenterのアラーム定義を無効にすることで、自動で発生するアラームを抑制することができます

尚、この方法を取った場合はvSAN健全性テスト上の警告は引き続き発生し続けます

※vSAN健全性テスト項目の抑止を実施している場合は対応不要です

・VxRail4.7(vSAN6.7, vSphere6.7)の場合

1. vSphere Client にLoginし、"Host and Clusters"を選択

2. 左側の最上部に位置するvCenterを選択し、Configure > More > Alarm Definitions を選びアラート一覧から抑止したいアラームを選択

3. 選択された状態で、「DISABLE」をクリック

　選択されたアラームの無効化が出来ます（Enableの項目がDisableになります）

・VxRail4.5(vSAN6.6, vSphere6.5)の場合

1. vSphere Web Client にLoginし、"Host and Clusters"を選択

2. 左側の最上部に位置するvCenterを選択しMonitor > Issues > Alarm Definitions を選びアラート一覧から抑止したいアラームを選択

　右側にあるEditを押す

3. 「Enable this alarm」のチェックを外すことで、アラームの無効化が出来ます

■参考情報

・VxRail: How to silence vSAN Health Checks in VxRail 4.5(User Correctable)

https://support.emc.com/kb/519562

・Silencing a vSAN health check (2151813)

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

・How to silence VMware vSAN Health Checks
https://www.virten.net/2017/04/how-to-silence-vsan-health-checks/

・vSAN Health Service - vSphere Update Manager - vSAN build recommendation engine health (2150914)

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

・VxRail: vSAN Health Service - vSphere Update Manager - vSAN build recommendation engine health

https://support.emc.com/kb/522941

We’re excited to announce a new VMware Skyline release that includes several new features designed to provide even more value to you and your organization. Be sure to update your Skyline Collectors to the latest version (2.3) to take advantage of the new features and functionality. If you have the “Auto Update” feature enabled, your Collectors will update approximately within the next seven days.

New features in this release include:

Enhanced Security Policies: As of November 19^th, Skyline has enhanced security policies and now Skyline Advisor explicit grant access is required. Your Skyline Admin must grant users access permissions to ensure no interruption to their service. To do this, Admins (organization owners) must log into their VMware Cloud Services Platform (CSP) organizations and use the identity and access management feature to assign access permissions to each user they wish to use to Skyline. This will enable users to access the Skyline Findings and Recommendations as well as other features including Log Assist for automatic support log bundle upload. Please refer to the Skyline Advisor Security Enhancement KB article for additional information.

If you need assistance, you can visit the Skyline documentation center or the Skyline Community, which is monitored by expert Skyline engineers.

VMware Skyline Integration with Dell EMC SupportAssist: Thousands of VMware customers leverage Dell EMC SupportAssist to proactively support Dell hardware. SupportAssist Enterprise (SAE) is Dell’s proactive support technology for hardware that is included with their support plans. Skyline and SAE have joined forces, enabling a best-in-class proactive support experience for customers running Dell and VMware. Skyline now integrates with SAE to help customers proactively optimize joint solutions. VMware and Dell PowerEdge 12G+ server customers will see an alert in SAE that provides information about Skyline, with a call to action to download and install Skyline. Similarly, Skyline users will see an alert in Skyline Advisor that provides information about SAE, with a call to action to download and install SAE. This announcement is the first step toward tighter integration between Skyline and SAE. In addition to Skyline Collector 2.3, Dell EMC SupportAssist Enterprise v.4.0.5 is required. Visit the Dell Technologies SupportAssisthttps://www.dell.com/support/driver/us/en/04/sae-ve-download/supportassist-enterprise-v4.0page for more details.

New Proactive Findings: This release includes ten new proactive Findings for vSphere, further expanding Skyline’s ability to alert you to potential issues in your environment.

Log Assist for Horizon Connection Server: We've just made it easier for you to upload a support log bundle for Horizon Connection Servers. Within Skyline Advisor, you can use Skyline Log Assist to initiate a log bundle for a Horizon Connection Server within your environment. To enable this functionality, you need to update your Skyline Collector to version 2.3, as well as update Horizon 7 Connection Server(s) to version 7.10. Please see the Horizon 7 version 7.10 Release Notes for more details.

Collector Health in Skyline Advisor:  The Collector health status is now included on the Collector Details page accessible from the Advisor Dashboard. For additional information, please visit the Troubleshooting an Unhealthy Skyline Collector KB article.

Skyline Advisor Federated Identity Management: Advisor now supports federated identity management. You can use your corporate domain account to access Skyline Advisor within VMware Cloud Services. To set up federated identity management, please see the Setting Up Federated Identity Management documentation. After completing the setup of federated identity management, ensure to add applicable Skyline service roles to each corporate domain user. These roles include Skyline Advisor and Skyline Collector.

Skyline Collector Improved Active Directory Authentication: Before this release, anonymous bind was required to enable Active Directory authentication. Now, anonymous bind is no longer required, and an Account Username and Password is now utilized to validate the Skyline Collector to Active Directory.

For more information on the new features above see our Skyline blog post, Advisor and Collector release notes.

Thank you for your continued use of Skyline proactive support!

I'm trying to switch back to Fusion after using Parallels for a few years.  I'm using a 2019 MacBook Pro 16" with an external 4K display.  The MacBook lid is always closed.

In Fusion, when this app (Altium Designer) tries to render a 3D model of a circuit board, the app pops up an "Out of Memory" error.  If I open the same file in Parallels it works fine.  Both VMs have the exact same settings, 8GB RAM, 1GB of VRAM.  I've tried increasing VRAM in Fusion up to 3GB but it doesn't help.  I've tried a clean install of Windows 10, as well as importing the Parallels VM, same issue.

The only differences I can see between the two machines when I'm inside windows is how they declare the available VRAM.  When running dxdiag, Windows reports 4MB VRAM, 1024MB shared for a total of 1028MB.  When running Parallels Windows dxdiag reports 1024MB VRAM and 1024MB Shared for a total of 2048MB.

When I increase Fusions VRAM the 4MB remains unchanged, only the Shared increases.

Could this be the issue?  Is there a way to tell Fusion to increase the VRAM and not the Shared memory?

Thanks in advance for any help.

We have 2 HPE Simplivity blades.   they have 4 1gb nic ports for management and networking and 2 10gbe ports for storage traffic.

We have vsphere essentials plus 6.7

They originally configured vSwitch0 for the 4 1 gb nic ports (these 4 are in a LACP Trunk Group on stacked Aruba 2390 switches) as vSwitch0 with "Teaming and Failover" set to "Route based on IP hash" and no traffic shaping.  As far as we can tell we can only get 1gb of throughput on vSwitch0.

This morning, i did some research and found information in the simplivity deployment guide that said Load balancing could be changed to "Route Based on the originating virtual port", so i made the change.    this killed network access to the unit.   I had to use ILO, Alt F1 on vcenter to get to the command line.  and do a esxcli network vswitch standard policy failover set -l iphash -v vSwitch0 to get the node back up.

Should this have worked?

Can Nic teaming be accomplished using vsphere essentials plus v6.7?  if it requires a different license, is it an add on license or an entirely new license?

Any help would be greatly appreciated.

Hello,

I'm forwarding all the vRO logs to a Syslog server and I want to reduce the amount of logs.

vRO 7.5.0.10044239

I need to know more information related to 'metrics.log' and 'vc-metrics.log'

/var/log/vco/app-server/metrics.log

According to the documentation this log "contains runtime information about the server. The information is added to this log file once every 5 minutes."

I saw that "metrics.log" is updated once every 1 minute instead.

There is any setting that can control this behavior?

Can this logs be stopped?

All the logs are related to statistics that I'm not interested to keep them on a Syslog server.

Thank you.

Hello all & TIA for any assistance with figuring this out.

I recently created a Windows 10 VM, operating on a Windows 10 Host.  It was running fine & I ran all the W10 updates & such, in preparation to add software (machine was running fine at that point).  I moved the VM to a different file location on my computer (accidentally created in the wrong location), and after that the machine will appear to boot, but just goes to a black screen.  I can click inside the window & I get an audible ding & see the spinning logo, but nothing appears to happen. Machine appears to be running in Workstation, but nothing in the window.  I can shut down the guest & it appears to act normally & doesn't produce any errors.  I've attached the log file & would appreciate any clues you can give me.

Hello Everyone,

So with Snapvol.cfg we can exclude files/folders/registry etc. but I would like to understand how this works if I update the template and already have a lot of existing writable. The reason for that is that we wanted to exclude a specific folder   exclude_uwv_file=\Users\%USERNAME%\AppData\Local\Temp

Now what I have noticed it that whatever information was in it prior to updating template through AV Manager stays like it's frozen. Also, if I delete any subfolder or file with older date next time I log on it is back. Now, if I create a file/folder in there and log off and log back in the file/folder is not there which is to be expected.

My expectation would be that after detaching writable snapvol.cfg gets updated with the exclusion, then user logs back in and gets all of the contents in  Temp directory back but once they log off again nothing gets persisted anymore in that directory.

Can anyone comment on what is happening out here?

Hi VMware forums

I have mistakenly disabled thumbnail preview in windows explorer for images on my  horizon clones Golden image somehow with the optimisation tool , can't seem to roll it back,

I found the setting in the tool but it doesn't know the registry change it does to activate it, i've been through all the Microsoft articles i can and can't  find it,

has anyone experienced this and managed to reverse it?

先月まで Surface Pro ( Windows10 Pro )に

vmware Workstationをインストールしwindows8を使用していました（起動ドライブは外付けHDD）

パソコンが壊れてしまったため、 Mac Book Proを購入しvmware Fusionを導入しました。

このFusionにWorkstationで使用していたwindows8を移行したいのですが、

何か方法はありますでしょいうか。

Workstationのバージョンは覚えていたいのですが、

Fusiopnは11.5になります。（Mac bookはkatalina）

よろしくお願い致します

Just having issues with incorrect hostnames being registered in Infoblox.

We customize the host name in a vRO workflow triggered by  VMPS32.Requested lifecycle state PRE; and update the vcac:Entity with the new hostname.  Shows up in vRA fine new hostname.  Registers original hostname generated via machine prefix in Infoblox. 

For a while I was trying to figure out exactly how the "Allocate" Infoblox workflow was being triggered; seems when you register the endpoint during plugin setup, a hard-coded vRO Workflow ID is being set (which is the Allocate workflow)  What I don't understand is how this actually gets triggered by vRA since we dont set a subscription  event.  It just fires somehow during provisioning

2nd thing I noticed is that the Allocate workflow is being passed  a few variables; one of which is Resource (CompositeType).  The 'Name' key in this Resource has a value of the 'machinePrefix_name'.  When I rerun this allocation by changing that value to a custom hostname, registration in NIOS completes successfully. I just need to know where / how that 'Resource' input value is being passed from vRA to vRO to the 'Allocate' workflow; and potentially how to update what values it's passing Any help greatly appreciated Happy Thanksgiving!

I am trying to assign a new license key (to enable additional features) using the vSphere thick client, but it's not being accepted.

The pop-up error dialog reads:

An internal error occurred in the vSphere Client.
Details: Object reference not set to an instance of an object.

I re-downloaded the client, but that did not make any difference.
Any suggestions would be appreciated.

Hello Folks,

Please help with this weird problem:

After successful provision and power on an blueprint/deployment, tenant admin cannot manage, actions stuck for hours and days in progress and never completes. For example, power off, take snapshot, destroy. Everything stuck with no error message for days in progress. Please see the screenshot attached.

Here are the environment details:

Site 1 -> vCenter 6.5.0 (Build 8307201)

Site 2 -> vCenter 6.5.0 (Build 8307201)

vCenter in Enhanced Linked Mode same SSO Domain

VRA Version: 7.6.0 (Build: 13027133)

VRA architecture enterprise distributed small (no load balancer).

Commercial Certificates.

VRA appliance / embedded orchestrator -

vra01.domain.com

IaaS web server -

iaas-web-01.domain.com

IaaS manager server -

iaas-ms-01.domain.com

DEM 01 -

iaas-dem-01.domain.com

Agent 01, 02 -

iaas-agnt-01.domain.com -> vCenter site 1

iaas-agnt-02.domain.com -> vCenter site 2

Thanks in advance for your attention on this. Regards.

Same as others have reported, there is no Skyline Advisor role that I can see:

I've seen the link to the SmartSheet site, so I'll enter details there after this post is created, since I also need this link.

I just started using Veeam Backup, and it breaks the network on one of my host servers. I have been having this same issue intermittently for months now, but Veeam Backup reliably breaks the network on this host.

This is not an intermittent issue where the host is resources are over taxed and the guests loose network access intermittently during the backup.

The only things on this host are the VCSA VM and my cameras system VM.

Heres what happens, I run Veeam Backup against my camera system VM, as soon as Veeam starts transferring data to my NAS, the VCSA drops off the network, then the Camera VM starts to loose connectivity to the cameras, then it drops off the network too. I've let it sit for a few hours, the guests never regain network access. Rebooting the host brings the network back up.

I did notice there were a bunch of "VMXNET3 TX HANG" messages on my camera VM. After some googling I switched the NIC on that VM to the e1000 vNIC, this had no effect. After some more googling I tried disabing, TSO / LRO, first on the guests, then on the host, then on both. None of this has any effect.

I also tried uninstalling open-vm-tools and installing the VMware Tools provided by vSphere, no luck.

This doesn't seem to effect my other VMware host, just the one running my camera system (Ubuntu 16.04) and the VCSA VM (VMware Photon)

Output of VMKernel follows.

2019-11-26T06:25:43.536Z cpu22:2111250)WARNING: UserSocketInet: 2266: vsanmgmtd: waiters list not empty!

2019-11-26T06:25:43.537Z cpu22:2111250)WARNING: UserSocketInet: 2266: vsanmgmtd: waiters list not empty!

2019-11-26T06:25:44.609Z cpu10:2097865)DVFilter: 5963: Checking disconnected filters for timeouts

2019-11-26T06:35:44.597Z cpu7:2097865)DVFilter: 5963: Checking disconnected filters for timeouts

2019-11-26T06:45:44.586Z cpu0:2097865)DVFilter: 5963: Checking disconnected filters for timeouts

2019-11-26T06:50:44.655Z cpu11:2099882)VSCSI: 6602: handle 8205(vscsi0:0):Destroying Device for world 2099858 (pendCom 0)

2019-11-26T06:50:44.655Z cpu11:2099882)VSCSI: 6602: handle 8206(vscsi0:1):Destroying Device for world 2099858 (pendCom 0)

2019-11-26T06:50:44.656Z cpu11:2099882)cswitch: VSwitchDisablePTIOChainRemoveCB:1149: [nsx@6876 comp="nsx-esx" subcomp="vswitch"]Remove ptDisable IOChain Handle for port 0x2000008

2019-11-26T06:50:44.656Z cpu11:2099882)NetPort: 1580: disabled port 0x2000008

2019-11-26T06:50:44.671Z cpu11:2099882)CBT: 723: Disconnecting the cbt device 70d63-cbt with filehandle 462179

2019-11-26T06:50:44.773Z cpu11:2099882)CBT: 723: Disconnecting the cbt device 70d62-cbt with filehandle 462178

2019-11-26T06:50:45.568Z cpu11:2099882)CBT: 1352: Created device 80d67-cbt for cbt driver with filehandle 527719

2019-11-26T06:50:45.569Z cpu11:2099882)VSCSI: 3782: handle 8207(vscsi0:0):Using sync mode due to sparse disks

2019-11-26T06:50:45.569Z cpu11:2099882)VSCSI: 3810: handle 8207(vscsi0:0):Creating Virtual Device for world 2099858 (FSS handle 920937) numBlocks=335544320 (bs=512)

2019-11-26T06:50:45.569Z cpu11:2099882)VSCSI: 273: handle 8207(vscsi0:0):Input values: res=0 limit=-2 bw=-1 Shares=1000

2019-11-26T06:50:45.572Z cpu11:2099882)FDS: 617: Enabling IO coalescing on driver 'deltadisks' device '2a0d6b-Ubuntu Zoneminder_1-000001-sesparse.vmdk'

2019-11-26T06:50:45.573Z cpu11:2099882)CBT: 1352: Created device 120d6d-cbt for cbt driver with filehandle 1183085

2019-11-26T06:50:45.573Z cpu11:2099882)VSCSI: 3810: handle 8208(vscsi0:1):Creating Virtual Device for world 2099858 (FSS handle 1314159) numBlocks=8589934592 (bs=512)

2019-11-26T06:50:45.573Z cpu11:2099882)VSCSI: 273: handle 8208(vscsi0:1):Input values: res=0 limit=-2 bw=-1 Shares=1000

2019-11-26T06:50:45.574Z cpu11:2099882)NetPort: 1359: enabled port 0x2000008 with mac 00:0c:29:36:01:fb

2019-11-26T06:50:45.574Z cpu11:2099882)cswitch: VSwitchDisablePTIOChainRemoveCB:1149: [nsx@6876 comp="nsx-esx" subcomp="vswitch"]Remove ptDisable IOChain Handle for port 0x2000008

2019-11-26T06:55:44.574Z cpu7:2097865)DVFilter: 5963: Checking disconnected filters for timeouts

2019-11-26T07:00:44.937Z cpu20:2099643)Vmxnet3: 24930: VMware vCenter Server Appliance,00:0c:29:35:dd:b6, portID(33554439): Hang detected,numHangQ: 2, enableGen: 2

2019-11-26T07:00:44.937Z cpu20:2099643)Vmxnet3: 24939: portID:33554439, QID: 0, next2TX: 2842, next2Comp: 1472, lastNext2TX: 1474, next2Write:1893, ringSize: 4096 inFlight: 4, delay(ms): 2656,txStopped: 0

2019-11-26T07:00:44.937Z cpu20:2099643)Vmxnet3: 24943: portID: 33554439, sop: 1472 eop: 1472 enableGen: 0 qid: 2, pkt: 0x45a242feb680

2019-11-26T07:00:44.937Z cpu20:2099643)Vmxnet3: 24939: portID:33554439, QID: 1, next2TX: 3066, next2Comp: 3068, lastNext2TX: 3070, next2Write:3629, ringSize: 4096 inFlight: 21, delay(ms): 26237,txStopped: 0

2019-11-26T07:00:44.937Z cpu20:2099643)Vmxnet3: 24943: portID: 33554439, sop: 3068 eop: 3069 enableGen: 1 qid: 2, pkt: 0x45a25a276780

2019-11-26T07:00:44.938Z cpu20:2099643)NetSched: 717: 0x2000004: received a force quiesce for port 0x2000007, dropped 239 pkts

2019-11-26T07:00:44.945Z cpu20:2099643)cswitch: VSwitchDisablePTIOChainRemoveCB:1149: [nsx@6876 comp="nsx-esx" subcomp="vswitch"]Remove ptDisable IOChain Handle for port 0x2000007

2019-11-26T07:00:44.946Z cpu20:2099643)NetPort: 1580: disabled port 0x2000007

2019-11-26T07:00:44.953Z cpu20:2099643)Vmxnet3: 18576: indLROPktToGuest: 0, vcd->umkShared->vrrsSelected: 1 port 0x2000007

2019-11-26T07:00:44.953Z cpu20:2099643)Vmxnet3: 18817: Using default queue delivery for vmxnet3 for port 0x2000007

2019-11-26T07:00:44.953Z cpu20:2099643)NetPort: 1359: enabled port 0x2000007 with mac 00:0c:29:35:dd:b6

2019-11-26T07:00:44.953Z cpu20:2099643)cswitch: VSwitchDisablePTIOChainRemoveCB:1149: [nsx@6876 comp="nsx-esx" subcomp="vswitch"]Remove ptDisable IOChain Handle for port 0x2000007

If I have two sites with 4 hosts at each site...all with the same specs, can I use the same licenses key if I wanted to create two different 6.7 vCenter environments?

Hi,

I got the following error when I tried to call retreiveInternalContent().

I used smartConnect to get the serverinstance.

Could someone know the reason? Thank you!

Traceback (most recent call last):

  File "perfNamespace.py", line 696, in main

    guestOperationDict.get(args.guestoperation.lower(), unknownOperation)(leftovers, args)

  File "perfNamespace.py", line 189, in listNamespaces

    svcInstIntCont = svcInst.RetrieveInternalContent()

AttributeError: 'vim.ServiceInstance' object has no attribute 'RetrieveInternalContent'

Hello Friends,

Please help me to understand where NSX is playing exactly in Network? i heard from many people that NSX will be at access level i.e. server level but in middle, you will see ACI or legacy multi vendor network.

Is my understanding correct or something not complete ?

please let me know.

I need to create a workflow where it gives us details of user details who put the host in mm mode when we select a ESXi host. I got the event details when a host is selected but unable to filter out the mm mode details alone.

This started occurring after a Windows update.  First it was due to the haspnt drive being installed.  Uninstalled that and it actually allowed me to log in.  Now every time the NIC requests DHCP info, a triple fault occurs.  If setting the NIC to NAT, it'll grab it's own DHCP fine and still can get on the net with no fault.  Setting the  NIC to host only is fine.  Setting it to Bridged but setting a static IP before doing so works also with no fault.   A work-around would be to just section off the DHCP pool for static addresses for these VMs (more that one have this problem) and give them all statics; however, I would like to avoid a workaround if possible, especially if there's a solution out there.

Hi all,

Recently I've been trying to patch some ESXi servers to 6.7u3. The patching is successful. However after the server reboot, the ESXi is unable to exit maintenance mode. vCenter always throw the error message "Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections" whenever I try to exit maintenance mode.

On the esxi hostd.log:

warning hostd[2101206] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x0000008c848b1d50, h:21, <TCP '127.0.0.1 : 57259'>, <TCP '127.0.0.1 : 9095'>>, e: 111(Connection refused)

error hostd[2101206] [Originator@6876 sub=vmomi.soapStub[1]] Resetting stub adapter for server <cs p:0000008c834451e0, 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]zKq7AVICAgAAACEo5QAOaG9zdGQAACxONmxpYnZtYWNvcmUuc28AALC+GwCQnBcAiskoANkbLQCAHi0A3SItAOEqLQAVaSkAteUoAJPpKACrxDYBO30AbGlicHRocmVhZC5zby4wAAJ9nw5saWJjLnNvLjYA[/context]

Been trying to figure out what port 9095 is used for, but to no avail. I'm thinking it might be related to vSAN. We are using VMware vSAN on the cluster. Can anyone help with this issue?