Skip navigation

Blog Posts

Total : 4,155

Blog Posts

Hi all,

so...i figured something out and wanted to share it with you guys. vRA 7.5 (Hotfix4 VMware Knowledge Base ) has come a long way in regards of custom forms. However there are still some things that are annoying, such as that one must imput Memory in MB. I undertsand that that is a left over from the vCenter API...but seriously...its 2019!

 

So I finaly came up with a workaround (requires custom forms, vRA 7.5 Hotfix >=4)

1) create a vRO action (I call it memGB2MB) that looks like this:

Header 1Header 2Header 3
InputmemGBNumber
OutputNumber
Scriptreturn memGB*1024;

 

2) Create an custom form of your  blueprint and drag at least CPU and Mem on it.

3) Add a new Integer field and call it Memory (GB). Then assign it all the restrictions that the blueprint has in regards of Memory.
(If you havent noticed yet. The blueprint restrictions are transfered ONLY once, when creating a custom form. If you update the Mem or CPU limits in the blueprint later, they are not passed dynamically to the custom form.)

4) Now click on the field Memory (MB) field and go to values. Select external source and then the vRO action you have created and Field Memory GB as the input.

5) You can give the whole thing a go now..or just directy set the Memory (MB) fields Visibility to false.

Well..there is more.

 

The method would allow you to use a Array/String to display a dropdown menu for CPU and/or Memory. You just need a new action that has as an input a string, as the output a number and the following script:

return parseInt(memGB*1024,10);

 

have Fun!

vSAN 6.7 U1 では、「仮想マシン ストレージ ポリシー」を考慮した

データストア空き容量の確認ができるようになっています。

 

下記のように、vSAN データストアの「容量の概要」画面の

「ポリシーで使用可能な容量」で仮想マシンが利用できる空き容量を確認できます。

スクリーンショットでは、デフォルトのポリシー「vSAN Default Storage Policy」で算出されています。

vsan-usage-01.png

 

そこで、別の仮想マシンストレージポリシーで使用可能容量を確認してみます。

デフォルトのポリシーでは「許容される障害の数:1 件の障害 - RAID-1(ミラーリング)」なので、

あえて、「policy-vsan-raid0」という名前で「データの冗長性なし」のポリシーを作成しました。

vsan-usage-02.png

 

「容量の概要」画面でこのポリシーを指定すると、このポリシーを利用した場合に

ポリシーで使用可能な容量が 2倍になることがわかります。(ただし冗長性はありません)

vsan-usage-03.png

 

実は、この情報は PowerCLI でも確認できるようになりました。

PowerCLI 11.2 Released, with more goodness for vSAN!

 

そこで、PowerCLI でも 同様の空き容量確認をしてみます。

 

今回は、PowerCLI 11.2 を利用しています。vCenter には既に接続ずみです。

PowerCLI> Import-Module VMware.PowerCLI

PowerCLI> Get-Module VMware.PowerCLI | select Name,Version

 

Name            Version

----            -------

VMware.PowerCLI 11.2.0.12483598

 

 

PowerCLI では、Get-VsanSpaceUsage で vSAN の容量情報を確認できます。

※ infra-cluster-01 は、vSAN クラスタの名前を指定しています。

 

ただし、下記にあるような FreeSpaceGB や CapacityGB には、

今回確認しているポリシーをもとにした空き容量が反映されません。

そこで、VsanWhatIfCapacity プロパティを確認します。

PowerCLI> Get-VsanSpaceUsage -Cluster infra-cluster-01

 

Cluster              FreeSpaceGB     CapacityGB

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

infra-cluster-01     2,911.358       4,657.552

 

 

特に仮想マシン ストレージ ポリシーを指定していない場合、

VsanWhatIfCapacity は情報を持ちません。

PowerCLI> Get-VsanSpaceUsage -Cluster infra-cluster-01 | select -ExpandProperty VsanWhatIfCapacity

PowerCLI>

 

デフォルトのポリシーを指定した場合です。

PowerCLI> Get-VsanSpaceUsage -Cluster infra-cluster-01 -StoragePolicy "vSAN Default Storage Policy" | select -ExpandProperty VsanWhatIfCapacity | Format-List

 

StoragePolicy         : vSAN Default Storage Policy

TotalWhatIfCapacityGB : 2328.77610206604

FreeWhatIfCapacityGB  : 1455.28823816683

 

 

今回作成した「policy-vsan-raid0」を指定すると、結果に反映されます。

PowerCLI> Get-VsanSpaceUsage -Cluster infra-cluster-01 -StoragePolicy "policy-vsan-raid0" | select -ExpandProperty VsanWhatIfCapacity | Format-List

 

StoragePolicy         : policy-vsan-raid0

TotalWhatIfCapacityGB : 4657.55220413208

FreeWhatIfCapacityGB  : 2910.5833046427

 

 

独自の仮想マシン ストレージ ポリシーを作成した時などに

確認手順に取り込んでおくと便利かもしれないと思いました。

 

以上、vSAN データストアの空き容量確認についての話でした。

vRealize Operations is an efficient monitoring tool which enables integration of many endpoints such as: Vcenter , VSAN , Network devices , VRA , Database etc...

 

vROps helps in monitoring entire Infrastructure that you integrate , enables to configure alerts and provide recommendations as a precautionary measure.

For any such endpoint to be monitored from vROps, we would have to perform below steps "

 

1.Download Management pack .

2.Install management pack on vROps.

3.configure it and vROps will start monitoring .

 

Lets know the  tips to check VRA adapter issue.

 

1.Do we have compatible VRA adapter version used and installed

Find your management pack and doc here: VMware Solution Exchange

Search for the pack name --> click on support --> you find docs and list of compatible version with respective pack.

 

2.vRealize Automation Appliance URL used :

Simple deployment use VRA appliance NAME /URL

Distributed set up with LB : Use your LB NAME /URL

NOTE: Prefer DNS name always instead of IP

 

3.Tenant :

Here you can give specific Tenant name / use * symbol to include all tenants.

 

4.Credentials provided while configuring VRA adapter.

*Sysadmin : basically who installs VRA should have System wide role as well as Tenant admin role

*The super user must have the following privileges in VRA :

  • Infrastructure administrator rights for all tenants.
  • Infrastructure architect rights for all tenants.
  • Tenant administrator rights for all tenants.
  • Software architect roles for all tenants.
  • Fabric group administrator rights for all fabric groups, in all tenants.

This should take care of your VRA adapter configuration part, There is another interesting part and thats connectivity .

 

5.Connectivity/Communication between VRA and vROps node

 

If VRA is deployed in Simple Set up then its  very simple :

*vROps node which has VRA solution installed should have connectivity to IAAS web node mainly.

*vROps node which has VRA solution installed should have connectivity to IAAS Manager Node and VRA appliance .

 

If VRA is deployed in Distributed set up with LB below are the checks :

 

*vROps node which has VRA solution installed should have connectivity to LB used between VRA appliances

*vROps node which has VRA solution installed should have connectivity to LB used between IAAS windows servers.

 

*Internally LB should have connectivity to VRA appliances

*LB used between IAAS nodes should have connectivity to IAAS nodes used ( Web and manager)

 

Simple command to check and validate this is:
Curl -v https://<FQDN>

 

This should resolve most of the issues that we hit with VRA adapter failure on vROps and as always Never forget to check logs

 

Mainly analytics and adapter logs .

 

Happy Learning.....

 

 

 

 

 



FROM THE EDITORS VIRTUAL DESK
Hi everyone, it has been a while since our last newsletter and of course there has been so much news in the past few weeks. One of the major topics that is progressing at a rapid rate is the VMware Cloud on AWS (VMC) solution that we have touched on in the past. I would encourage you to check out as many resources as you can and try to keep track of the ever changing landscape in this area which is moving forward at a rapid speed. One of my best resources is the VMware Cloud on AWS Roadmap which we publish and keep updated online. You can check it out here!

I wish you all a fantastic week ahead!

Virtually Yours
VMware TAM Team

Twitter | Facebook | Archive
-
NEXT TAM WEBINAR
March 2019 – VMware IT’s Journey with Horizon: Windows Virtual Desktop

Date: Thursday, March 21st
Time: 11:00am EST/ 10:00am CST/ 8:00am PST
Duration: 1.5 Hour

Synopsis:
VMware IT transformed the way they deliver and manage the virtual desktop environments and published application platforms. In this session we will share our journey of Windows virtual delivery and lifecycle management in an enterprise environment. We will discuss challenges and lessons learned during the migrations as well as the benefits that we achieved. We will discuss the persistent desktop experience in a non-persistent virtual desktop platform in Horizon 7.

Guest speaker:
Aju Sukumaran is an Information Systems Sr. Manager in VMware’s Colleague Experience & Technology Group. Currently he is working on deploying VMWare's End User Computing products in VMware IT’s environments.

Registration Link:
https://vmware.zoom.us/webinar/register/WN_04nKXeG0SwyOUdnxBuHQ9A

NEWS AND DEVELOPMENTS FROM VMWARE

Open Source Blog

Network Virtualization Blog

vSphere Blog

Cloud management Blog

Cloud Native Blog

EUC Blog

vCloud Foundation Blog

EXTERNAL NEWS FROM 3RD PARTY BLOGGERS

Virtually Ghetto

ESX Virtualization

Cormac Hogan

Scott's Weblog

vSphere-land

NTPRO.NL

Virten.net

vinfrastructure

  • VMware vExpert 2019
    Reading Time: 3 minutes This year the vExpert 2019 announce has taken much time compared with the vExpert 2018 ann...
  • March 2019 IT events
    Reading Time: 1 minute Interesting European IT events: Gartner CIO Leadership Forum – London (Mar 4-6) Gartner Data  ...
  • Introducing VMware Essential PKS
    Reading Time: 3 minutes Kubernetes (k8s) is an open-source system for automating deployment, scaling, and management of...
  • Veeam Backup & Replication 10th birthday!
    Reading Time: 2 minutes Ten years ago, on Feb. 26, Veeam Backup & Replication 1.0 was introduced at VMworld Europe ...
  • Veeam ONE Community Edition
    Reading Time: 2 minutes With the new Veeam Availability Suite 9.5 Update 4, not only the Veeam Backup&Replication F...

Nukescloud

vSwitchZero

vNinja

VMExplorer


DISCLAIMER
While I do my best to publish unbiased information specifically related to VMware solutions there is always the possibility of blog posts that are unrelated, competitive or potentially conflicting that may creep into the newsletter. I apologize for this in advance if I offend anyone and do my best to ensure this does not happen. Please get in touch if you feel any inappropriate material has been published. All information in this newsletter is copyright of the original author. If you are an author and wish to no longer be used in this newsletter please get in touch.

© 2018 VMware Inc. All rights reserved.



FROM THE EDITORS VIRTUAL DESK
Hi everyone, as February unfolds one of the items I would like to point you all to is the VMware Learning Zone. Getting certified and attending quality training is important for all of us but it is really hard to get to either live on-line or in-person classes. This is where the VMware Learning Zone comes in. If you head over to https://www.vmware.com/education-services/learning-zone.html you will find options for VMware training and certification that I am sure will be very useful. You can purchase individual courses as well as a full subscription. The subscription option I think will appeal to most and comes in 3 flavors. There is the Free Basic subscription which provides access to over 700 technical videos, 58 short courses as well as training for the VMware Certified Associate. Next is the Standard Learning Subscription and finally the Premium Learning Subscription. There should be a subscription offer no matter what your requirements. Have a chat to your VMware TAM or VMware representative to help with more information and let's make this the year that we all get more certified.

Virtually Yours
VMware TAM Team

Twitter | Facebook | Archive
-
VMWARE TAM CUSTOMER WEBINAR
February 2019 – vSAN 2 Node and Stretched Clusters Deep Dive

Date: Thursday, February 21st
Time: 11:00am EST/ 10:00am CST/ 8:00am PST
Duration: 1.5 Hour

Synopsis:
vSAN 2 Node and Stretched Clusters Deep Dive – Best Practices, Troubleshooting, & Operations Considerations

Guest speaker:
Jase McCarty - Staff Technical Marketing Architect, Storage and Availability

Registration Link:
https://vmware.zoom.us/webinar/register/WN_yyQmR-oMQiaDq-Y-CIbp2w


NEWS AND DEVELOPMENTS FROM VMWARE

Open Source Blog

Network Virtualization Blog

vSphere Blog

Cloud management Blog

Cloud Native Blog

EUC Blog

vCloud Foundation Blog

EXTERNAL NEWS FROM 3RD PARTY BLOGGERS

Virtually Ghetto

ESX Virtualization

Cormac Hogan

Scott's Weblog

vSphere-land

NTPRO.NL

Virten.net

vinfrastructure

Nukescloud

vSwitchZero

vNinja

VMExplorer

 

 

DISCLAIMER
While I do my best to publish unbiased information specifically related to VMware solutions there is always the possibility of blog posts that are unrelated, competitive or potentially conflicting that may creep into the newsletter. I apologize for this in advance if I offend anyone and do my best to ensure this does not happen. Please get in touch if you feel any inappropriate material has been published. All information in this newsletter is copyright of the original author. If you are an author and wish to no longer be used in this newsletter please get in touch.

© 2018 VMware Inc. All rights reserved.

Functional Testing Assists In App Upgradation.jpg

The vital role of Application Development or Functional Testing has been well stated. Nevertheless, in the situation of Application Modernization, the role increases, as it carries in its purview the challenges, risk, and scope for uplifting and upgrading the application. In a way, it also supports teams for authenticating the efforts.

 

Keeping this scenario in mind, we are presenting you with a list of three ways in which functional testing company helps in-app modernization.

 

1. Delivering the Anticipated Result

Functional Testing is required to discourse the apprehensions around the real application of functional needs. It is normally mentioned as black box testing, which does not require much information regarding the implementation procedure. With Functional Test sets, every situation becomes a functional test. Therefore, when a function is applied or presented within the app, the particular functional test is implemented after been unit tested. The significance of functional tests completely hinges on the objectives and priorities defined for the app. The objective is to distribute what is anticipated from the application.

 

2. Continuous Functioning and Anticipated Business Result from All the Functions

With System Testing the teams implement end-to-end functional tests across software units. This assists to guarantee that, as a whole, all the functions distribute anticipated business result. The emphasis is on the complete situation that requires critical units to fit in and distribute a specific activity. Therefore, all subsystems have to be verified primarily before they are combined with the additional subsystem. In order to circumvent any trouble in recognizing instant errors, the components are slowly integrated after being tested in separation.

 

This is very much pertinent in an Application Modernization situation, where the latest features are being entrenched, but these new mechanisms must assimilate with the current ones to deliver a unified experience.

 

3. Application Modifications Do Not Influence the Complete System

Regression Testing is essential to guarantee that the code alterations do not bring in glitches or bugs that might influence the general system. Therefore, it should include plans from the original unit that also comprises of functional as well as system tests. This would assist in explaining the present functionality that is anticipated from the application. Regression testing might not be needed for the entire system, but it might be required for specific functional areas that are complex in nature.

 

Nonetheless, the challenge comes in while modernizing legacy apps, where the development team has to deal with the hardcoded business procedure workflow and other firmly bound legacy codes.

Last option to try when you don't have any option to try from the UI or the admin UI

 

If you have tried multiple options and couldn't resolve vROps related issues and decided to go with new deployment. Before you go for new deployment try one last option below

 

  • Run the Cluster Offline command on the MASTER node in the cluster.
    • $VMWARE_PYTHON_BIN /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin/vcopsClusterManager.py offline-cluster Maintenance
  • Run the below slice offline command on the analytics nodes in the cluster:
    • $VMWARE_PYTHON_BIN $ALIVE_BASE/../vmware-vcopssuite/utilities/sliceConfiguration/bin/vcopsConfigureRoles.py --action bringSliceOffline --offlineReason "recovery"
    • Run the above command on all the nodes DATA, REPLICA and last MASTER in the same order.
  • Reboot all the Nodes
  • Power-on all the Nodes
  • Run the below command to bring the slice online
    • $VMWARE_PYTHON_BIN $VCOPS_BASE/../vmware-vcopssuite/utilities/sliceConfiguration/bin/vcopsConfigureRoles.py --action bringSliceOnline
    • Run the above command on all the nodes in MASTER , REPLICA and DATA node in the same order.
  • Bring cluster online, run the below command on the MASTER Node.
    • $VMWARE_PYTHON_BIN /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin/vcopsClusterManager.py init-cluster

    

Test Cases.jpg

 

A test case can be defined as the sets of variables and conditions utilized by the software testers to check if the system performs as per expectations. Test cases play a major role in authenticating the test coverage of a software app. It entails essential fields that offer information regarding the test case, the expected results, and the activities involved in the execution. These fields entail a different name, any requirement involved, detailed steps, input conditions, and desired outcomes for a specific app function.

Effective test cases are simple to maintain and execute. A test case management tool plays a significant role in streamlining the test case process. They make the testing procedure more effective by saving effort and time.

 

Keeping this scenario in mind we are providing the list of 10 best practices for developing test cases.

 

1. Keep It Easy to Understand and Simple

An effective test case is extremely simple and well-written for the testers to execute and understand. Organize the test cases as per related areas or specific categories of the app. Test cases can be grouped on the basis of their user story or modules like browser specific behaviors. As a result, it becomes easy to maintain and review the test document. Information provided in the test cases must clear to other developers, testers, and stakeholders.

 

2. Entail End User Perspective

Take into consideration, the end user perspective prior to drafting the test case. Put yourself in the shoes of an end user who is the main stakeholder for whom the app is created. You must the end user perspective, the functionality aspects to be covered and the requirement. This will assist in identifying test scenarios that rise in actual conditions.

 

3. Utilize Correct Naming Conventions

The test case must be named in a way that makes it easy for the stakeholders to understand and detect its objective. You should name the test cases in accordance with the functional area or the module that is included for testing.

 

4. Offer Test Case Description

An appropriate test case description will permit the users to comprehend what is being tested and how it is being tested. Provide pertinent details like any other particular information and test environment. Mention the testing tools and the testing data to be utilized to be applied for executing the tests.

 

5. Entail Preconditions and Assumptions

Testers must include all the conditions and assumptions that are valid for test cases. Give details related to the test environment, any special set up for the implementation of the test cases.

 

6. Mention the Steps That You Have Incorporated

Incorporate the actual steps included in the implementation of the test cases. Testers are not missed out on any step. Make sure that all the test case authentication steps are covered. Contain relevant screenshots or documents that can assist in the execution of the steps provided in the test design.

 

7. Provide Details of the Test Data

You should provide the test data details for test case execution, particularly in scenarios where the same data is used again. This assists in time-saving for the development of the test data for every cycle to be run. Mention the value range, for the particular fields. Testers must not try to test each and every value. The objective must be to ensure maximum coverage by selecting some from every class.

 

8. Make it Modular and Reusable

Testers must guarantee that there is zero conflict and dependency among the test cases. In a scenario, where test cases are batched or inter-dependent, you are advised to mention them clearly in the test document.

 

9. Assign Testing Priority

Testers must assign test priority to every test case based on the component or feature involved. This will guarantee that a high priority test case is executed first during the execution.

 

10. Offer Post Conditions and Desired Results

Testers are advised to include the expected outcome for each step of the test case. You can also entail relevant documents and screenshots for reference. Mention the things or post-conditions that must be confirmed after test case execution.

vSAN に RAID5 / RAID6 の 仮想ディスク(VMDK)を配置するには、ノード数の要件があります。

  • RAID5 → 4ノード以上(4つ以上のフォルト ドメイン)
  • RAID6 → 6ノード以上(6つ以上のフォルト ドメイン)

参考: RAID 5 または RAID 6 イレージャ コーディングの使用

 

下記のサイトによると、これは vSAN の RAID の実装によるもので、

RAID5 が 4つ、RAID6 が 6つのコンポーネントとして実装されているためのようです。

 

VSAN ERASURE CODING FAILURE HANDLING

https://cormachogan.com/2018/12/13/vsan-erasure-coding-failure-handling/

 

そこで今回は 6より多いノード数で、

実際に vSAN の RAID5 / RAID6 ポリシーの VM を作成してみました。

 

vSAN 環境。

下記のように、オールフラッシュディスクグループの7ノード構成にしています。

  • vSAN 6.7 U1
  • ESXi 7ノード
  • オール フラッシュ(キャッシュ層 SSD + キャパシティ層 SSD)ディスクグループ
  • ディスクグループは各ノードで 1つずつ(キャッシュ層 x1 + キャパシティ層 x2)
  • フォールト ドメインはデフォルト構成のまま

vsan-raid56-00.png

 

仮想マシン ストレージポリシーの作成。

RAID5 のストレージポリシーを作成します。

今回は「許容される障害の数」だけデフォルト値から変更しています。

vsan-raid56-01.png

 

RAID5 のポリシー名は「vSAN-RAID5-Policy」にしました。

vsan-raid56-02.png

 

RAID6のポリシーも、同様に「vSAN-RAID6-Policy」として作成しました。

vsan-raid56-04.png

 

仮想マシンの作成。(RAID5)

仮想マシンを、「vSAN-RAID5-Policy」で作成しました。

ちなみに、今回は 40GB で Thin プロビジョニングの VMDK を 1つだけ作成しています。

vsan-raid56-05.png

 

RAID5 になっている仮想ディスクの物理配置を確認すると、ノード数が4つより多くても、

コンポーネントは 4つ(4ノード)に分散されています。

vsan-raid56-06.png

 

仮想マシンの作成。(RAID6)

次に、仮想マシンを「vSAN-RAID6-Policy」で作成しました。

vsan-raid56-07.png

 

RAID6 の仮想ディスクの物理配置についても、

ノード数が4つより多くても、コンポーネントは 6つ(6ノード)に分散されています。

vsan-raid56-08.png

 

vSAN の RAID5 / RAID6 は、基本的にはノード数が多いからといって

RAID のストライプ数があわせて増加するわけではないようです。

おそらくは、可用性と性能のバランスをとった設計なのだろうと思います。

 

以上、vSAN の RAID5 / RAID6 の仮想ディスク コンポーネントを見てみる話でした。

karenlaw Lurker
VMware Employees

Poor me - F11 key in karenlaw's Blog

Posted by karenlaw Feb 17, 2019

I am using my new macbook to install new nested esxi on top current cluster environment. During installation, it requests me to input F11. I stuck there for long time. I wonder if all keys failed and checking a lot on VMRC version, grading VMRC, using different browsers and even trying out booth vSphere web client and html5 client.

 

Finally, I solved it by holding "fn"+"command"+"F11 on the Touch Bar". What my lovely MacBookPro!

 

Thanks to vmexplorer post.

https://vmexplorer.com/2015/06/30/f11-key-for-nested-esxi-with-mac-os-x/

 

       

EDIT:

Looks like this affects quite a lot of Properties. Just found the same problems with VMware.VirtualCenter.Folder and VirtualMachine.Network0.Name

 

HI all,

you have probably noticed that when you are using vRA custom forms that the ReservationPolicyID  isn't working and throwing you the following error.:

(vRA 7.5 plus https://kb.vmware.com/s/article/59378  )

The following component requests failed: smallRHEL. Allocation request [Composition RequestId: [969dfad8-52b4-4f39-8e68-ba9c6dcba281], CompTypeId: [Infrastructure.CatalogItem.Machine.Virtual.vSphere], BlueprintId: [smallRHEL], CompId: [smallRHEL], BlueprintRequestId: [5cb0a374-982c-454a-8cc7-c38eb0517dd4], RootCafeRequestId: [9da8ba9d-63ef-4a73-8a16-421f51d9fa5a], SubtenantId: [06890147-51f7-4857-98c7-e5b6ca2d9dcd]] with binding id [20fd1dba-3807-4ece-8b1a-6ad5dc1a5ce2] failed with [Infrastructure service provider error: A server error was encountered. Error requesting machine. Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).].

 

I finally found the workaround that fixes this issue. The problem seems to be caused by  the element coming onto the canvas as an DataGrid, Switching it to DropDown will solve the problem. Here is how to do this:

 

  • Create a ReservationPolicyID Property Definition and link it to the action : com.vmware.vra.reservations/getApplicableReservationPolicies
  • Assign the ReservationPolicyID  to the Blueprint
  • Create a Custom Form
  • Drag the ReservationPolicyID  onto the canvas
  • save the form
  • export the form to JSON
  • Open  the JSON (I use Notepad++ and JSTool)
  • Look in the schema section (scroll down) for your ReservationPolicyID it should look like this:

"CentOS_7~ReservationPolicyID": { "label": "Cluster", "type": { "dataType": "complex", "isMultiple": false }, "default": "", "valueList": { "id": "com.vmware.vra.reservations/getApplicableReservationPolicies", "type": "scriptAction", "parameters": [] }, "placeholder": "No data found", "constraints": { "required": true } },

  • Exhange the "type": { "dataType": "complex", "isMultiple": false } to "type": { "dataType": "string", "isMultiple": false} so only this is left "type": { "dataType": "string"}
  • Save the file
  • Import the JSON into customForms
  • DONE

vSphere 6.0 から vCenter 間での vMotion が可能になりましたが、

標準的な vSphere Web Client / vSphere Client(旧 HTML5 Client)から実行するには

vCenter が同一の PSC / vSphere Single Sign-On(SSO)ドメインに所属している必要があります。

そして vCenter の SSO ドメインが異なる場合の vCenter 間の vMotion は、

API や PowerCLI から実行する必要があります。

vCenter Server インスタンス間の移行の要件

 

そこで、今回は PowerCLI を利用して、できるだけシンプルな構成で

Cross vCenter vMotion を実行してみます。

 

今回の環境。

vCenter 6.7 を 2台用意しました。それぞれ別の SSO ドメインに所属しているので、

それぞれ別の vSphere Client からの管理となっています。

 

移行元の vCenter の名前は、lab-nsxt-vcsa-01.go-lab.jp です。

この vCenter 配下の VM「vm05」を vMotion します。

xvc-vmotion-01.png

 

移行先の vCenter の名前は、infra-vc-01.go-lab.jp です。

xvc-vmotion-02.png

 

PowerCLI 11 を利用します。

PowerCLI> Get-Module -ListAvailable VMware.PowerCLI | select Name,Version

 

Name            Version

----            -------

VMware.PowerCLI 11.0.0.10380590

 

 

PowerCLI による Cross vCenter vMotion の実行。

今回は、PowerCLI のスクリプト実行ではなく、対話的な実行(コマンドラインの手入力)で

できるだけ簡潔に Cross vCenter vMotion を実行してみます。

 

まず、vMotion 元 / 先それぞれの vCenter に接続します。

PowerCLI> $vc_a = Connect-VIServer lab-nsxt-vcsa-01.go-lab.jp

PowerCLI> $vc_b = Connect-VIServer infra-vc-01.go-lab.jp

 

今回は、vCenter のバージョンがそろっています。

PowerCLI> $vc_a | select Name,Version,Build

 

Name                       Version Build

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

lab-nsxt-vcsa-01.go-lab.jp 6.7.0   10244857

 

 

PowerCLI> $vc_b | select Name,Version,Build

 

Name                  Version Build

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

infra-vc-01.go-lab.jp 6.7.0   10244857

 

 

vMotion 先として指定するため、ESXi、データストア、ポートグループを取得して、

それぞれ1件ずつ取得できていることを確認しておきます。

確実に移行先 vCenter から取得するため「-Server」で vCenter を明示的に指定しています。

 

データストアを取得します。

PowerCLI> $ds = Get-Datastore -Server $vc_b -Name "vsanDatastore"

PowerCLI> $ds | select Name,Type

 

Name          Type

----          ----

vsanDatastore vsan

 

 

今回の宛先ポートグループは、vDS の分散仮想スイッチです。

PowerCLI> $pg = Get-VDPortgroup -Server $vc_b -Name "dvpg-infra-0000"

PowerCLI> $pg | select Name

 

Name

----

dvpg-infra-0000

 

 

宛先のESXi です。

ちなみに Cross vCenter vMotion の宛先(Move-VM の -Destination)には、

ESXi(VMHost)かリソースプールを指定できます。

PowerCLI> $hv = Get-VMHost -Server $vc_b -Name "infra-esxi-01.go-lab.jp"

PowerCLI> $hv | select Name

 

Name

----

infra-esxi-01.go-lab.jp

 

 

VM「vm05」の現在の配置を確認しておきます。

「-Server」では、移行元の vCenter を指定しています。

PowerCLI> Get-VM -Server $vc_a -Name vm05 | select Name,PowerState,VMHost,@{N="vCenter";E={$_.Uid -replace ".*@|:.*",""}}| fl

 

Name       : vm05

PowerState : PoweredOn

VMHost     : lab-esxi-21.go-lab.jp

vCenter    : lab-nsxt-vcsa-01.go-lab.jp

 

 

それでは vm05 を vMotion します。

オプションで、あらかじめ取得した ESXi、データストア、ポートグループを指定しています。

PowerCLI> Get-VM -Server $vc_a -Name vm05 | Move-VM -Destination $hv -Datastore $ds -PortGroup $pg

 

vMotion 完了後に VM の配置を確認すると、期待通り vCenter 間で移動されたことがわかります。

PowerCLI> Get-VM -Name vm05 | select Name,PowerState,VMHost,@{N="vCenter";E={$_.Uid -replace ".*@|:.*",""}} | fl

 

Name       : vm05

PowerState : PoweredOn

VMHost     : infra-esxi-01.go-lab.jp

vCenter    : infra-vc-01.go-lab.jp

 

 

今回の処理を vSphere Client から見た様子。

ちなみに vMotion タスクの進捗は、PowerCLI で実行した場合でも

vSphere Client から確認することができます。

 

vMotion 実行中の、移行元 vCenter です。

xvc-vmotion-04.png

 

ほぼ同じタイミングでの、移行先 vCenter です。

タスク ステータスの進捗%は、移行元 / 先で一致するわけではありません。

xvc-vmotion-05.png

 

vCenter をまたいで、指定したホストに vMotion されました。

xvc-vmotion-06.png

 

このように、仮想マシンの vNIC や VMDK の構成がシンプルであれば、

対話的に PowerCLI を利用したとしても(PowerCLI スクリプトを作りこむことをしなくても)

簡単に Cross vCenter vMotion できます。

 

またそれぞれの vCenter / ESXi では、従来の vMotion と同様に

vmkポートでの vMotion トラフィックの有効化や、通信経路でのポート解放などを

済ませておく必要があります。

 

以上、PowerCLI で Cross vCenter vMotion を実行してみる話でした。



FROM THE EDITORS VIRTUAL DESK
Hi everyone, welcome to our second newsletter of 2019. Yes it is almost the end of January already and there has been so much news, updates and other items from our fascinating world of VMware and Virtualization. Please ensure that you interface regularly with your VMware TAM and VMware Team and are well aware of the current editions, patches and security advisories that we have provided to ensure that your environment stays healthy. One of the items that I regularly do with my customers is our TAM Best Practice Review. This is a really important part of our TAM service to provide visibility into the environment with analysis of VMware best practices to ensure that everything is as expected.

Please enjoy our newsletter and feel free to contact us anytime at tamsource@vmware.com.

Virtually Yours
VMware TAM Team

Twitter | Facebook | Archive
-

NEWS AND DEVELOPMENTS FROM VMWARE

Open Source Blog

Network Virtualization Blog

vSphere Blog

Cloud management Blog

Cloud Native Blog

EUC Blog

vCloud Foundation Blog

EXTERNAL NEWS FROM 3RD PARTY BLOGGERS

Virtually Ghetto

ESX Virtualization

Cormac Hogan

Scott's Weblog

vSphere-land

NTPRO.NL

Virten.net

vinfrastructure

Nukescloud

vSwitchZero

vNinja

VMExplorer

 

 

DISCLAIMER
While I do my best to publish unbiased information specifically related to VMware solutions there is always the possibility of blog posts that are unrelated, competitive or potentially conflicting that may creep into the newsletter. I apologize for this in advance if I offend anyone and do my best to ensure this does not happen. Please get in touch if you feel any inappropriate material has been published. All information in this newsletter is copyright of the original author. If you are an author and wish to no longer be used in this newsletter please get in touch.

© 2018 VMware Inc. All rights reserved.

To Troubleshoot Poor vSphere Performance. Below are few questions you should ask :

 

A: Is this Really Unexpected Behavior(Analyze application specific I/O Behavior )

B : Running Latest Product Check HCL;

C: VM Running Vmware Tools ?

D: VM Resource/Share Issue ;

E: Antivirus Software or Recent Changes made on VM/Esxi Host ?

F: Underlying Storage Healthy;

G: ESXI have enough Resources;

H: Verify Networking Front

I : CPU Power management enabled :BIOS Power policies

 

 

Performance issues may be caused by Several different Areas such as :

 

1:CPU

2:Memory

3:Storage

4:Network Latency.

 

 

ESXTOP Command Overview

 

 

 

Things that can cause poor storage performance:

 

– Under sized storage arrays/devices unable to provide the needed performance

– I/O Stack Queue congestion

– I/O Bandwidth saturation, Link/Pipe Saturation

– Host CPU Saturation

– Guest Level Driver and Queuing Interactions

– Incorrectly Tuned Applications

 

 

Storage Stack Components :

 

GAVG (Guest Average Latency) total latency as seen from vSphere

KAVG (Kernel Average Latency) time an I/O request spent waiting inside the vSphere storage stack.

QAVG (Queue Average latency) time spent waiting in a queue inside the vSphere Storage Stack.

DAVG (Device Average Latency) latency coming from the physical hardware, HBA and Storage device.

 

To find out more about the threshold for each Metrics Read : http://www.yellow-bricks.com/esxtop/

 

 

Memory Constraints :

 

Examine the MEM overcommit avg on the first line of the command output. This value reflects the ratio of the requested memory to the available memory, minus 1.

If memory is Overcommitted

                                                   A: Increase the amount of physical RAM on the host

                                                   B: Decrease the amount of RAM allocated to the virtual machines

 

Determine whether the virtual machines are ballooning and/or swapping

MCTLSZ (MB) displays the amount of guest physical memory reclaimed by the balloon driver.

SWCUR (MB) displays the current Swap Usage.

ensure that the ballooning and/or swapping is not caused by the memory limit being incorrectly set.

 

 

CPU Constraints :

 

Check For Load Average. A load average of 1.00 means that the ESXi/ESX Server machine’s physical CPUs are fully utilized, and a load average of 0.5 means that they are half utilized.

Examine  %READY percentage of time that the virtual machine was ready but could not be scheduled to run on a physical CPU. It should remain under 5 % If not  Increase number of Physical CPU on the host or Decrease Virtual CPU Allocated to the host (Either by reducing CPU allocated to the Vm running on Esxi host or Reduce Vm running on the host )

 

 

Network Latency :

Network performance can be highly affected by CPU performance. First we have to Rule out a CPU performance issue before investigating network latency.

For Network latency Test the maximum bandwidth from the virtual machine with the Iperf tool

If you identify a bottleneck on the network: Verify VMwre Tools Version ;Verify speed settings for Network adapters; Use multiple nics to increase overall network capacity for port group that contain VM’s.If you are using iSCSI storage and jumbo frames, ensure that everything is properly configured.

 

If you are using Network I/O Control, ensure that the shares and limits are properly configured for your traffic. Also Ensure that traffic shaping is correctly configured.

Actions

Looking for a blog?

Can't find a specific blog? Try using the Blog page to browse and search blogs.