Issue: B-series blade fails to power on in UCSM and the following critical fault:

Severity: Critical

Code: F0868

Last Transition Time: 2020-02-25T03:34:17Z

ID: 11500997

Status: None

Description: Motherboard of server 1/7 (service profile: org-root/ls-IN-ESX-01) power: failed

Affected Object: sys/chassis-1/blade-7/board

Name: Compute Board Power Fail

Cause: Power Problem

Type: Environmental

Acknowledged: No

Occurrences: 2

Creation Time: 2020-02-25T03:33:07Z

Original Severity: Critical

Previous Severity: Critical

Highest Severity: Critical

Following entries seen in the server's SEL log:

671 | 02/25/2020 04:23:06 EST | CIMC | Module/Board SUPER_CAP_FLT #0x8f | Predictive Failure deasserted | Asserted

672 | 02/25/2020 04:23:40 EST | CIMC | Processor WILL_BOOT_FAULT #0x90 | Predictive Failure deasserted | Asserted

673 | 02/25/2020 04:23:55 EST | CIMC | Platform alert POWER_ON_FAIL #0x8c | Predictive Failure asserted | Asserted

674 | 02/25/2020 04:24:06 EST | CIMC | Platform alert POWER_ON_FAIL #0x8c | Predictive Failure deasserted | Asserted

675 | 02/25/2020 04:24:58 EST | CIMC | Platform alert POWER_ON_FAIL #0x8c | Predictive Failure asserted | Asserted

Following entries seen in the server's Oblf Log:

Feb 25 04:23:55 EST:4.1(30b):IPMI:1708: Pilot3SrvPower.c:483:  -> Power State On: LPC RESET is     IN RESET; powerOnLPCOff[2b]

Feb 25 04:23:55 EST:4.1(30b):IPMI:1708: Pilot3SrvPower.c:483:  -> Power State On: LPC RESET is     IN RESET; powerOnLPCOff[2c]

Feb 25 04:23:55 EST:4.1(30b):IPMI:1708: Pilot3SrvPower.c:483:  -> Power State On: LPC RESET is     IN RESET; powerOnLPCOff[2d]

Feb 25 04:23:55 EST:4.1(30b):IPMI:1708: Pilot3SrvPower.c:483:  -> Power State On: LPC RESET is     IN RESET; powerOnLPCOff[2e]

Feb 25 04:23:55 EST:4.1(30b):IPMI:1708: Pilot3SrvPower.c:483:  -> Power State On: LPC RESET is     IN RESET; powerOnLPCOff[2f]

Feb 25 04:23:55 EST:4.1(30b):IPMI:1708: Pilot3SrvPower.c:483:  -> Power State On: LPC RESET is     IN RESET; powerOnLPCOff[30]

Feb 25 04:23:55 EST:4.1(30b):IPMI:1708: Pilot3SrvPower.c:483:  -> Power State On: LPC RESET is     IN RESET; powerOnLPCOff[31]

Feb 25 04:23:55 EST:4.1(30b):IPMI:1708: Pilot3SrvPower.c:483:  -> Power State On: LPC RESET is     IN RESET; powerOnLPCOff[32]

SEL log location:

Chassis log bundle -> CIMCx_TechSupport.tar.gz -> var -> log -> sel

OBFL log location:

Chassis log bundle -> CIMCx_TechSupport.tar.gz -> obfl

Cause: This fault is caused by a hardware failure on the motherboard.

Solution:

Attempt following troubleshooting steps:

1. Reset CIMC

2. Physically reseat server in chassis

Note: If the above actions do not resolve issue and blade still does not power on, it is likely there is a hardware failure.

3. Contact Cisco TAC for part replacement.

Request to please like and comment.

I setup a UAG to act as a Reverse proxy for our intranet.

When I visit the URL  https://uag.doman.com/intranet

I get ERR_TOO_MANY_REDIRECTS

Any ideas?

Hi,

I am new to VRO and I would like to create a workflow that will give me the number and details of vMotions that has taken place within a cluster in last 7 days.

Please help.

We started migrating the flex plugin and have come till a way where I see my plugin in the admin category and when I click on it it fecthes some data from a backend and displays on our first screen. All this happens angular2 way. We have components and services so far. The next thing is to move to another page on a button click. For that I was exploring Routing in the sample which is part of Fling. Have couple of questions...

1. If I don't have a route for index.html, it cribs. Any obvious reasons?

2. I have the following routes

   const routes: Routes = [

   {path: '', pathMatch: 'full', redirectTo: 'index.html',},

   {path: 'index.html', component: AppComponent},

   {path: 'register', component: UCSDomainRegister}

   ];

AppComponent is my bootstrap component and index.html is my targetviewID in plugin.xml as the target for my icon which goes as a vise.global.views extension.

I have two issues at present.

a. Runtime error - ZoneAwareError {__zone_symbol__error: Error: Uncaught (in promise): Error: Cannot find primary outlet to load 'AppComponent'

b. My router link to register route is not working. I have the following button in my HTML template for the AppComponent.

  <input type="button" class="btn btn-primary" value="Register" routerLink="register" />

Also given is the base href settings as below.

 <script>

         (function(){

            var href = document.location.href;

            href = href.substring(0, href.indexOf("index.html"));

            document.write('<base href="' + href + '" />');

         })();

      </script>

Please let me know if there is a guidelines document which I can follow while developing a H5 plugin based on angular2. Basically how to manipulate the plugin.xml and various routes for the plugin.

Thanks much in anticipation.

Manoj

In our environment  we have vCSA 6.5.0 U2G 13638625 with 100 ESXi host and around 600 VMs.  Webclient is running too slow and gives timeout errors (See attached) while trying to pull out any inventory details such as datastores, performance charges, VMs running on the datastores etc.  The refresh sign keep spinning and then it results in query timeout errors.  This issue is recurring after very 2 to 2.5 months.  As a workaround, we planned a reboot every 2 months and it was working as after reboot of appliance, webclient performance seems to be better for few days.  But, this time even after rebooting, it is giving same issue.  The query time out errors are very annoying and end users are unable to work properly due to this. 

Raised a support case with VMware and they tried to increase the memory size of vmware-vpxd-svcs and vsphere-client service to 2048 but it didnt resolve the problem.  Any suggestions on this ?  Has it got something to with this - We still have previous vCSA 6.0 appliance server in powered off mode in this inventory.  (Just considering) or anything else.  We take a daily clone of appliance but we stopped that also in order to check, but it didn't work out. 

Hi Team,

I have a setup with 1 horizon server with 10 virtual desktops. I have a host pc with installed applications and the same image has been pushed to all VDI.

Now, I tried to login outlook and it works fine. But every time when I open outlook, emails are downloading. This happens for all users.

Is there a way to setup a permanent outlook profile for each user who logged in to VDI, so that emails will not download all the time for every login?

Thanks,
Ram

Hi,

We're planning to introduce FSLogix containers in our Horizon v7.11 environment.

We're currenlty using Linked Clones with persistent disks which includes the profile data.

Is there a way to migrate the profile data somehow to the new FS Logix Container?

We want to retain all profile data, like favourites, desktop items, ...

For updates on this blog and other blogs: Follow @SteveIDM

In the third installment of the Okta Integration with Workspace ONE, we are going to cover SCIM Provisioning from Okta to Workspace ONE.

In the first release of this functionality, there will be a lot of manual steps. I fully expect a more seamless process in future releases.

Minimum Requirements:

• Workspace ONE UEM SAAS or version 19.09 for dedicated/on-premise.
• Workspace ONE Access SAAS
  • Note: Although some aspects of the integration will work for on-premise customers, not all functionality is currently available.

Note: When creating users in Workspace ONE from Okta, they will be created as new users in Workspace ONE Access and UEM. Any previous users synchronized from AD will not get over written. Users that are currently enrolled with AD credentials will need to re-enroll with Okta credentials (if you are switching from AD to Okta).

This process will require some proficiency and knowledge in using Postman to manage identities in Workspace ONE Access (formerly known as VMware Identity Manager).  Please check out my blog on using Postman to Manage Workspace ONE Identities.

https://communities.vmware.com/blogs/steveIDM/2019/05/09/using-postman-to-manage-workspace-one-identities

Here is a high level overview of the process:

1. Okta is configured to use Workspace ONE Provisioning Application
2. Okta will SCIM the user to Workspace ONE Access
3. The AirWatch Provisioning Adapter in Workspace ONE Access will provision the user to Workspace ONE UEM.

This blog will not going into detail on the provisioning to UEM. Please see the following blog on provisioning to UEM:

Workspace ONE - AirWatch Provisioning App

Step 1:  Create a Remote App Access Client

1. Log into Workspace ONE Access
2. Click on Catalog (Down Arrow) and then Settings
3. Click on Remote App Access
4. Click Create Client
5. Select "Service Client Token"
6. Enter a Client ID ie. OktaSCIM
7. Expand Advanced
8. Click Generate Shared Secret
9. Update the Access Token TTL to something longer then the default. Note: If you choose 1 year, you will need to update the Okta configuration every year with a new bearer token.
   
   
   
10. Copy the shared secret. You will need this later.
11. Click Add

Step 2:  Configure Postman to use your OAuth Token

Note: Depending on your version of Postman, these steps below might be slightly different.

1. Open a new Tab in Postman
2. For the HTTP Method, select "POST"
3. For the URL, enter: https://[TENANTURL]SAAS/jersey/manager/api/connectormanagement/directoryconfigs
   Replace the Tenant URL with your URL
   https://dsas.vmwareidentity.com/SAAS/jersey/manager/api/connectormanagement/directoryconfigs
4. In the authorization section, select "OAuth 2.0" as the type:
   
5. Click Get New Access Token
6. Provide a Token Name (ie. Workspace ONE)
7. Under Grant Type, select "Client Credentials"
8. "Under Access Token URL", enter https:[Tenant URL]/SAAS/auth/oauthtoken
9. ie. https://dsas.vmwareidentity.com/SAAS/auth/oauthtoken
10. Under Client ID, enter your Client ID from step 1.
11. Under Secret, enter your secret from step 1.
12. Under Scope, enter 'admin'
    
13. Click Request Token
14. On the left hand side, Select "Request Headers" and click "Preview Request".
    
    
15. You should see a message saying headers were updated correctly:
    
16. Click the Headers Tab and verify that the bearer token was added as a temporary header.
    
17. If the bearer token was not added, return to the Authorization Tab and select your token from the available tokens drop down list and preview the request again.

Step 3:  Create an "Other" Directory for your Okta Users.

1. Under "Headers", Set the Content-Type to "application/vnd.vmware.horizon.manager.connector.management.directory.other+json"
   
   
2. Click on the Body tab
3. Use the following as a sample and Click Send

{  
"type":"OTHER_DIRECTORY",  
"domains":["Okta.com"],  
"name":"Okta Universal Directory"  
}  

You should see a similar result

Step 4:  Add the VMware Workspace ONE App in Okta

1. Log into the Okta Admin Console
2. Click on Applications -> Applications
3. Click Add Application
4. Search for the "VMware Workspace ONE"
5. Select VMware Workspace ONE under Integrations:
   
   
6. Click Add
   
   
   
7. Enter your Workspace ONE URL in the field labeled "Base URL"
   ie. https://dsas.vmwareidentity.com
   
8. Click Done
9. Click on the Provisioning Tab and Click Configure API Integration
10. Select Enable API Integration
11. Paste your bearer token that was created in the earlier step with postman.
12. Click Test API Credentials
    
13. Ensure you have a "Success" before proceeding.
14. Click Save
15. Click on the Edit Button
    
16. Select Enable for Create and Deactivate and click Save
17. If you used a different domain then "okta.com" when creating your directory (using Postman), you will need scroll down and edit the domain attribute so it matches your domain.
    
    
    
    

Known Issues:

1. When pushing groups from Okta to Workspace ONE, Okta has a feature called "Push Now". If you run into an error when using this capability, click the Retry All Groups button:
   
   

For additional troubleshooting see:

https://communities.vmware.com/blogs/steveIDM/2019/10/21/workspace-one-and-okta-troubleshooting-blog

Why is it taking so long to load the powershell modules. Below is an example of me loading the modules and it taking almost 1 minute to load the modules. However on a few machines it is much faster. Is this a known issue? Any way to speed this up?

PS C:\scripts> measure-command {import-module vmware.hv.helper, vmware.vimautomation.core, vmware.vimautomation.horizonview}

Days              : 0

Hours             : 0

Minutes           : 0

Seconds           : 49

Milliseconds      : 921

Ticks             : 499213694

TotalDays         : 0.000577793627314815

TotalHours        : 0.0138670470555556

TotalMinutes      : 0.832022823333333

TotalSeconds      : 49.9213694

TotalMilliseconds : 49921.3694

PS C:\scripts> Get-Module -name *vmware* -ListAvailable

    Directory: C:\Program Files\WindowsPowerShell\Modules

ModuleType Version    Name                                ExportedCommands

---------- -------    ----                                ----------------

Script     6.7.0.1... VMware.DeployAutomation             {Add-DeployRule, Add-ProxyServer, Add-ScriptBundle, Copy-D...

Manifest   1.3.1      VMware.Hv.Helper                    {Get-HVMachineSummary, New-HVHomeSite, Set-HVlicense, Get-...

Script     6.7.0.1... VMware.ImageBuilder                 {Add-EsxSoftwareDepot, Add-EsxSoftwarePackage, Compare-Esx...

Manifest   11.5.0.... VMware.PowerCLI

Script     6.7.0.1... VMware.Vim

Script     11.5.0.... VMware.VimAutomation.Cis.Core       {Connect-CisServer, Disconnect-CisServer, Get-CisService}

Script     11.0.0.... VMware.VimAutomation.Cloud          {Add-CIDatastore, Connect-CIServer, Disconnect-CIServer, G...

Script     11.5.0.... VMware.VimAutomation.Common         {Get-Task, Stop-Task, Wait-Task}

Script     11.5.0.... VMware.VimAutomation.Core           {Add-PassthroughDevice, Add-VirtualSwitchPhysicalNetworkAd...

Script     11.5.0.... VMware.VimAutomation.Hcx            {Connect-HCXServer, Disconnect-HCXServer, Get-HCXAppliance...

Script     7.10.0.... VMware.VimAutomation.HorizonView    {Connect-HVServer, Disconnect-HVServer}

Script     11.3.0.... VMware.VimAutomation.License        Get-LicenseDataManager

Script     11.5.0.... VMware.VimAutomation.Nsxt           {Connect-NsxtServer, Disconnect-NsxtServer, Get-NsxtPolicy...

Script     11.5.0.... VMware.VimAutomation.Sdk            {Get-ErrorReport, Get-PSVersion, Get-InstallPath}

Script     11.0.0.... VMware.VimAutomation.Security       {Get-SecurityInfo, Get-VTpm, Get-VTpmCertificate, Get-VTpm...

Script     11.5.0.... VMware.VimAutomation.Srm            {Connect-SrmServer, Disconnect-SrmServer}

Script     11.5.0.... VMware.VimAutomation.Storage        {Add-KeyManagementServer, Add-VsanObjectToRepairQueue, Cop...

Script     1.3.0.0    VMware.VimAutomation.StorageUtility Update-VmfsDatastore

Script     11.2.0.... VMware.VimAutomation.Vds            {Add-VDSwitchPhysicalNetworkAdapter, Add-VDSwitchVMHost, E...

Script     11.5.0.... VMware.VimAutomation.Vmc            {Add-VmcSddcHost, Connect-Vmc, Disconnect-Vmc, Get-AwsAcco...

Script     10.0.0.... VMware.VimAutomation.vROps          {Connect-OMServer, Disconnect-OMServer, Get-OMAlert, Get-O...

Script     6.5.1.7... VMware.VumAutomation                {Add-EntityBaseline, Copy-Patch, Get-Baseline, Get-Complia...

Custom Scripts execution for stopping services in  Protected VM using SRM 8.x

Hello Everyone

I am struggling to find a way to disable the add device option in SSP or somehow prevent users that have been imported from active derictory to be able to enroll devices other than the ones designated to them

Any suggest

自宅ラボの vSphere を眺めていたら、クラスタの vMotion 数がいい感じに増えていました。

そこで vMotion と DRS の様子を、vCenter Server と vRealize Operations Manager（vROps） で

観察する Tips を紹介しようと思います。

今回の環境は、vCenter 6.7 U3 ＋ vROps 8.0 です。

vCenter / vSphere Client での vMotion 観察。

まず、クラスタでの vMotion 数についてです。

vCenter Server では、クラスタごとに vMotion 実行数を記録しています。

自宅ラボのクラスタ「infra-cluster-01」では、これまで 45781 回の vMotion が実行されたことがわかります。

このクラスタでは vSphere DRS が有効化されており、ほとんどの vMotion は自動実行されたものです。

検証環境なので使用リソース増減も激しく、結構頻繁に vMotion が発生します。

vMotion の合計移行回数は、vSphere Client のパフォーマンス チャートでも表示できます。

対応しているカウンタは、クラスタの「仮想マシン操作」→「vMotion 数」です。

直近1年間の、vMotion の積み重ねが可視化されました。

いい感じに自宅ラボが使われていそうな気がします。

しかし、パフォーマンス チャートの情報は一定期間ごとにロールアップされてしまうため、

vCenter だけでは詳しく vMotion の様子を確認しにくいかなと思います。

そこで、vRealize Operations Manager（vROps）でも、

このクラスタでの vMotion の様子を見てみます。

vRealize Operations Manager での vMotion 観察。

vROps を利用すると、過去にさかのぼって一定間隔ごと（最短で5分間隔くらい）の vMotion 数が確認できます。

これで、クラスタで普段と異なる動きがないか確認することもできます。

2月23日あたりのグラフ上昇は、自宅ラボの ESXi を1台ずつローリング アップデートしたため vMotion が特に増えています。

※残念ながらこの vROps は最近デプロイしたもので1年間の情報が蓄積されていないため、年間通してのチャートは表示しません。

さらに、vMotion が DRS によるものか、それ以外（手動 vMotion）なのかも可視化できます。

赤枠内の紫線のところだけは、DRS ではない手動 vMotion のはずです。

おまけとして・・・

本来の利用方法ではないと思いますが、VM がどの時間帯に、どの ESXi ホストにいたかをチャートに表示することもできます。

VM（例では lab-rancher-01）の「メトリック」で、「サマリ」→「親ホスト」のチャートを表示すると、

時系列で VM がどの ESXi で稼働していたか確認することができます。

ただし、ESXi がチャートの縦軸で表現されているので、ESXi 台数が多くなると見にくいかもしれません。

この例の VM は、5台 の ESXi （クラスタは 6ノードですが）の間だけで移動しています。

DRS / vMotion の観察方法はいろいろあり、vCenter のイベント情報や他の vRealize 製品でも違った見方ができます。

今回は、あえて GUI で簡単に確認できそうな方法を選択してみました。

以上、vMotion 観察の Tips 紹介でした。

Guys, I see in my downloads section there are open source versions of VRealize Orchestration. Is this freeware? Any guides on setup?

Hi! I have a small infrastructure consisting of two hosts (SuperServer 1019GP-TT) and QNAP TS-983XU-RP NAS.

I want to use this server for VCSA installation (lastest version) to control these 2 ESXi hosts and NAS:

DELL PowerEdge R210 Perc S100 2x3.5" 1*250W, 1xXeon X3430(4 Core, 2.4/2,8), 8GB DDR3-10600E

Is such an unusual configuration workable? Thanks.

I hope someone can give me a quick answer - our esx hosts are already 6.7 U3, why vmware tools version v10 and v11 both show as 'current'? shouldn't the current one be v11?

Hi ,

I am checking proactive HA functionality and it seems it is not working with cisco ucs provider.

Can someone please help me regarding this.

Hello all,

My company is looking to do tech refresh on all our current ESXi hosts ( total 22 hosts). My question is what is the best way to do this?

Stand up all new ESXi hosts and add them to existing vCenter and migrate all VMS over? what if we like to keep the same hostname and IP for the hosts?

Any suggestion would be appreciate.

Hi

I have recieved a VM running some sensitive software (changes to MAC-addresse, IP-address, Windows settings is not good).

The VM was originally created on VMware Workstation and then imported into an 6.x ESXi/vCenter environment (now running 6.7).

vSphere is now complaining when trying to migrate - "Virtual Machine is configured to use a device that prevents the operation: Device 'HD Audio'...

I want to remove the device but the 'HD Audio' device cannot be removed under VM Settings (since its not supported on vSphere).

I have read that you can delete it directly from the .vmx-file by removing:

sound.autoDetect = "TRUE"

sound.virtualDev = "hdaudio"

sound.fileName = "-1"

sound.present = "TRUE"

sound.pciSlotNumber = "35"

Now for my question: can I just shut down the VM, connect to ESXi-host via SSH and edit the .vmx-file, and then it wil apply at power-on?

Or do I have to first unregister the VM from the inventory and then subsequently re-register it? (and will this operation make canges to MAC-address etc.?!?).

Regards,

Soren

I'm a VMware newbie trying to wrap my head around all the different components. I have vSphere Client 6.5 and I need a feature that's in 6.7. If I upgrade vCenter to 6.7 that will upgrade the vSphere Client as well?

And any hard-won words of wisdom in doing an upgrade would be much appreciated.

Thank you!

hi Luc,

good morning

if you could suggest on the following error which i got running the below function .

though its not the proper function structure but it will allow users to update powercli online .