Quantcast
Channel: VMware Communities : Blog List - All Communities
Viewing all 3135 articles
Browse latest View live

GSS Tech Seminar (2014. 06. 27) APD와 PDL

$
0
0

안녕하세요,

 

2014년 6월 27일 세미나 APD(All Path Down)과 PDL(Permanent Device Loss)에 대한 세미나 입니다. 녹화는 이루어지지 않았습니다.

발표에 사용된 파일을 첨부하니 참고 하시기 바랍니다. 2 주 연속으로 진행되었으나 두번 모두 녹화가 되지 않았습니다.

 

감사합니다.


GSS Tech Seminar (2014. 07. 18) Horizon View SSL Certificate

$
0
0

안녕하세요,

 

2014년 7월 18일에 있었던 Horizon View SSL Certificate에 관한 내용입니다. 녹화는 되지 않았고, 발표에 사용된 파일을 첨부하니 참고하시기 바랍니다. 시리즈로 이어지는 세미나입니다.

 

감사합니다.

Guest VMs with an Odd Number of vCPUs

$
0
0

I’ve recently been working with a customer who has been a program of right-sizing vCPUs and Memory based on recommendations from vC Ops oversized VM reports. For many virtual machines, the vC Ops report has recommended a vCPU count of 3, and I’ve had to work hard to justify this to the customer, and realign their thinking away from the traditional pCPU architecture based on a 20=1, 21=2, 2^2=4, etc. system.


Just to clarify, vSphere 5 introduced VM Hardware Version 8 (AKA Hardware Compatibility Mode). This is the minimum version of virtual machine hardware that is required to allow odd numbered vCPUs on the guest.


Although vSphere 5 supports VMs with odd or/and even number of vCPUs, there is no specific recommendations about this from VMware. Basically, vC Ops recommends the number of required vCPUs depending on the requirements of the workload displayed over time, and  the most important thing is that you’re careful about allocating more vCPU's than physical cores per pCPU (for NUMA locality) and that you only allocate as many vCPU cores as the application needs.


  Whilst there is no recommendation for/against odd numbers of vCPU’s, we are all of course tuned to the physical world where we talk about 2, 4, 6, 8  CPUs etc. and 1024MB, 2048MB etc. of memory and it sometimes hard to unlearn what we’ve learned over such a long time.  Below is an article that covers this question in a bit more depth. http://blog.solori.net/tag/odd-core-counts-with-vmware/

VMware Newsletter 6.31

$
0
0

Email not displaying correctly? View it in your browser: http://us2.campaign-archive1.com/?u=84638d120599c4461b514e1a0&id=55c75e5f89&e=[UNIQID]

 

From the editors virtual desk

Hi everyone, well I had a very interesting discussion this week. It was one that I haven;t had in depth for a while and with my VCP5 and VCAP5 completed quite a few years ago it turned out that I needed to ensure I was totally up to speed with things before I could provide the ideal solution. The discussion was around networking and more specifically a customer with a large environment who needs to re architect their networking on vSphere with an upcoming upgrade to 5.5. The discussion was of a very technical nature and I really enjoyed having it but I must admit that I did ensure that while we were discussing I had the latest most relevant documents to hand.

 

It is really great sometimes to just get back to basics and have a good deep technical chat about the fundamentals of a system. It made me draw on some skills that I have not used in quite some time and I really enjoyed the discussion and I hope I can do more of them in the future.

 

This week I am focusing on the future and hope to start delivering a number of Roadmap and VMware strategic presentations to my customers to help us align their business objectives and VMware's upcoming solutions and technology releases. This is something that is a critical part of the Technical Account Manager program and something my customers find very valuable in helping them plan for future services.

 

We are just a few weeks from VMworld. As usual I have included some of the more important BLOG posts for you right up front. If you are heading to San Francisco for VMworld drop me an email.

 

Have a fantastic week and I look forward to speaking to you again next week and bring you more VMware news.

 

Virtually Yours

Neil Isserow

Senior Technical Account Manager

VMware Australia

nisserow @ vmware . com

 

VMworld

- VMworld Sessions Online

- Hands-on Labs – What To Expect at VMworld 2014 US

 

Local Events (BRISBANE)

- VMUG

 

Local Training Classes

Tinyurl.com/au7z3cr

VMware vSphere: Install, Configure, Manage [V5.5] 25-29 Aug

VMware vSphere: Install, Configure, Manage [V5.5] 22-26 Sep

 

 

VMware Bloggers

  •  

    Don’t Miss Out: Ops Transformation is Big at VMworld (http://blogs.vmware.com/cloudops/?p=1074)Have you built your schedule for VMworld yet? Don’t forget to add sessions from the Operations Transformation track, with options that include: Moody’s IT Transformation Learn how credit rating giant Moody’s is transforming its IT department into a service brokerage, starting with implementing VMware vCloud Automation Center. SVP of Infrastructure Services Rajiv Doshi presents with […]

     

  •  

    Question of the Week (ESXi) (http://blogs.vmware.com/education/?p=4467)This week’s question comes from the VCP5- Data Center Virtualization practice exam.   A) HTTP B) SNMP C) HTTPS D) NTP Click through to the comments for the answer and learn more here. Follow @VMwareEducation on Instagram to see more #TechTrivia every Friday and visual updates from the VMware Education and Certification community.  

     

  •  

    New VCAP5-DCD Exam Available on vSphere 5.5 (http://blogs.vmware.com/education/?p=4101)We have released a new exam to qualify candidates for the VMware Certified Advanced Professional 5 – Data Center Design (VCAP5-DCD) Certification. This new exam (exam code VDCD550) is based on vSphere v5.5, where the existing exam (exam code VDCD510) is based on vSphere 5.0/5.1. Passing either of these exams will earn VCAP 5-DCD certification if you have […]

     

  •  

    VMware Virtual SAN with Cisco UCS Reference Architecture (http://blogs.vmware.com/vsphere/?p=13413)

     

    co-author Bhumik Patel,  VMware Partner Architect  As customers look to implement Virtual SAN in their environments, it is critical that the underlying platform has the matching attributes of rapid provisioning, unified management, linear scalability and operational simplicity to be able to fully leverage the capabilities of a scale-out, hypervisor-converged Virtual SAN solution. With Cisco UCS […]

  •  

    Discover VMware Virtual SAN at VMworld! (http://blogs.vmware.com/vsphere/?p=13392)We invite you to learn more about VMware Virtual SAN — our software-defined storage solution designed for vSphere environments — at VMworld 2014. The sessions, like the rest of VMworld, will take place at the Moscone Center in San Francisco, California. Depending on your needs, there will be several important VMware Virtual SAN sessions you’ll […]

     

  •  

    Performance Advantages of vCloud Hybrid Service (http://cto.vmware.com/?p=2814)Today, Principled Technologies published performance benchmarks that show how vCloud Hybrid Service outperforms competing public clouds. These strong results highlight key architectural decisions that our team made when we designed vCloud Hybrid Service. Many customers struggle with the topic of performance when transitioning to the cloud, particularly in a hybrid cloud scenario, where IT teams are personally involved in making the hardware decisions and building their private clouds. They are used to…

     


  •  

    Great read: Virtualizing SQL Server with VMware: doing IT right (http://www.yellow-bricks.com/?p=15210)A couple of months back I received an email from Jeff Szastak. He asked me if I wanted to write a foreword for the book he was authoring with Michael Corey an Michael Webster. When he mentioned the book was on the topic of virtualizing SQL Server I knew it would be an instant classic, and I did […] " Great read: Virtualizing SQL Server with VMware: doing IT right " originally appeared on Yellow-Bricks.com . Follow me on twitter - @DuncanYB. Pre-order my upcoming book Essential Virtual SAN…

     

  •  

    Technology Short Take #43 (http://blog.scottlowe.org/?p=3484)It's time for another instance of Technology Short Takes, my irregularly-published series of articles and links about various data center technologies. This article was originally posted on blog.scottlowe.org . Visit the site for more information on virtualization, servers, storage, and other enterprise technologies. Technology Short Take #43

     

  •  

    Sessions at the Fall OpenStack Summit (http://blog.scottlowe.org/?p=3489)

     

    Here's a list of sessions at the fall OpenStack Summit that I'd like you to consider supporting. This article was originally posted on blog.scottlowe.org . Visit the site for more information on virtualization, servers, storage, and other enterprise technologies. Sessions at the Fall OpenStack Summit

  •  

    Login VSI 4.1 Released (http://www.penguinpunk.net/blog/?p=2112)

     

    Disclaimer: I received a free Login VSI 12-month license this year as part of my membership of the vExpert programme. There is no requirement for me to blog about their products and I am not compensated in any way for this post.  This disclaimer is also probably longer than I’d intended the original post to be, but […]

  •  

    VMware Fling – ViewDbChk tool (http://www.vmguru.nl/?p=12545)VMware released a new VMware Fling, the ViewDbChk tool. The ViewDbChk tool allows administrators to scan for, and fix provisioning errors that can not be addressed using View Administrator. Provisioning errors occur when there are inconsistencies between the LDAP, vCenter and View Composer databases. These can be caused by: direct editing of the vCenter inventory, restoring a backup, or a long term network problem. This tool allows VMware View administrators to scan for machines which can not be provisioned…

     

  •  

    Login VSI 4.1 is out with new workloads and more (http://www.vmguru.nl/?p=12475)Today Login VSI, Inc. announced a new version of Login VSI: Login VSI, Inc. announces Login VSI 4.1, a substantial update to its flagship product. Login VSI is the industry-standard performance validation solution for centralized virtualized desktop and server-based environments. The new release, which has been tested in limited private beta since May 2014, benefits two main audiences: Enterprises and vendors. Enterprises use Login VSI to optimize the performance of their virtualized environments. Vendors…

     

  •  

    VMware Fling – VMware OS Optimization Tool (http://www.vmguru.nl/?p=12429)

     

    The VMware OS Optimization Tool helps optimize Windows 7/8/2008/2012 systems for use with VMware Horizon View. The optimization tool includes customizable templates to enable or disable Windows system services and features, per VMware recommendations and best practices, across multiple systems. Since most Windows system services are enabled by default, the optimization tool can be used to easily disable unnecessary services and features to improve performance. Local Analyze/Optimize; Remote…

  •  

    The new Nutanix Script Repository (http://myvirtualcloud.net/?p=6517)

     

    The new Nutanix Script Repository is dedicated to the system administrator scripters of the world whom use automation to reduce time spent performing mundane tasks. Overtime you will find resources written in PowerShell, Java, Python and other script languages. You can simply download the scripts or interact with them using Git. Git is an open-source … Continue reading »

  •  

    Long Haul VMUG (http://professionalvmware.com/?p=4715)It is my turn to make some VMUG pilgrimages. In September I am going to be at the Chicago VMUG summit making vBrownBag video awesome. Since it is such a long way to go I thought I’d make the most of it and also visit the SoCal VMUG Summit on my way home. Later I […]

     

  •  

    VMworld USA Final Sponsors, SimpliVity (http://professionalvmware.com/?p=4688)I’m delighted to announce SimpliVity as our sixth and final sponsor for VMworld USA 2014. SimpliVity are a hyperconverged VM infrastructure company. Their OmniCube platform uses a hardware engine for storage deduplication and compression, which also enables replication for disaster recovery. The TechTalk schedule is pretty full, but if you’d like to present, propose yours […]

     

 

 

 

This email was sent to <<Email Address>>
why did I get this?    unsubscribe from this list    update subscription preferences
VMware · Lvl 18 333 Ann Street · Brisbane, Queensland 4000 · Australia

VMware Certificate Toolkit

$
0
0

Hello everyone,

 

I am going introduce you to my new tool that I developed during the last 3 weeks. This is called VMware Certificate Toolkit.

As I am used to implement CA signed certificate on vSphere and vCloud environment at work, it takes always some time to prepare all the files with OpenSSL or Java Keytool even with scripts.

I decided to create a Java program that handle the creation of files needed when implementing CA signed certificate on VMware. VCT is not based on OpenSSL, it uses Java cryptographics

API and is able to create compatible certificate, RSA key and keystore to implement on your VMware Infrastructure.

 

The application is still in beta, and I need your help to test this app on VMware product, it has already been tested on vSphere 5.1/5.5 and vCloud Director 5.1.

 

VCT is available on source forge at: https://sourceforge.net/projects/vmwarecertificatetoolkit/

 

 

ss1.jpg

ss2.jpg

ss3.jpg

ss4.jpg

ss5.jpg

ss6.jpg

vSS の 標準ポートグループ観察。

$
0
0

最近、自宅 vSphere 環境にネットワークセグメントを追加したくなり、

標準スイッチ(vSS)と標準ポートグループを観察してみました。


標準ポートグループは、ESXi ごとに存在する vSS に作成されるもので、

ESXi ごとに存在確認しないといけないかと思ったら・・・

pg-list-01.png

 

意外とそんなことはなく、ネットワークのインベントリを開けば

同様のポートグループがどの ESXi に作成されているか、まとめて確認できます。

pg-list-02.png

 

クラシックな vSphere Client でも、

ネットワークのインベントリからうまい具合に見られます。

pg-list-03.png

 

ちなみに、PowerCLI では、

下記のような感じで vSS のポートグループを操作できます。

 

今回は、vSS「vSwitch0」に「pg-vlan-0004」というポートグループを作成してみます。

まず vCenter に接続して、ホストの一覧を見てみます。

PowerCLI> Connect-VIServer vc55u1-1.vmad.local, vc55u1-2.vmad.local -User vmad\administrator -Password *****

 

Name                           Port  User

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

vc55u1-1.vmad.local            443   VMAD\Administrator

vc55u1-2.vmad.local            443   VMAD\Administrator

 

PowerCLI> Get-VMHost -State Connected | select Name,ConnectionState,PowerState,Version | ft -AutoSize

 

Name                   ConnectionState PowerState Version

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

hv51-hpp1.gowatana.lab       Connected  PoweredOn 5.1.0

hv51-opt1.gowatana.lab       Connected  PoweredOn 5.1.0

hv55n1.vmad.local            Connected  PoweredOn 5.5.0

hv55n2.vmad.local            Connected  PoweredOn 5.5.0

hv55-has1.vmad.local         Connected  PoweredOn 5.5.0

hv55-has2.vmad.local         Connected  PoweredOn 5.5.0

hv55-ivy1.vmad.local         Connected  PoweredOn 5.5.0

 

この時点では、まだこれから作成するポートグループが

どの ESXi にも無い状態です。

PowerCLI> Get-VMHost -State Connected | Get-VirtualSwitch -Name vSwitch0 | select Name,VMHost,{$_|Get-VirtualPortGroup -Name pg-vlan-0004} | ft -AutoSize

 

Name     VMHost                 $_|Get-VirtualPortGroup -Name pg-vlan-0004

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

vSwitch0 hv51-hpp1.gowatana.lab {}

vSwitch0 hv51-opt1.gowatana.lab {}

vSwitch0 hv55n1.vmad.local      {}

vSwitch0 hv55n2.vmad.local      {}

vSwitch0 hv55-has1.vmad.local   {}

vSwitch0 hv55-has2.vmad.local   {}

vSwitch0 hv55-ivy1.vmad.local   {}

 

それぞれの ESXi の vSS にポートグループを作成します。

PowerCLI> Get-VMHost -State Connected | Get-VirtualSwitch -Name vSwitch0 | New-VirtualPortGroup -Name pg-vlan-0004 -VLanId 4

 

Name                      Key                            VLanId PortBinding NumPorts

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

pg-vlan-0004              key-vim.host.PortGroup-pg-v... 4

pg-vlan-0004              key-vim.host.PortGroup-pg-v... 4

pg-vlan-0004              key-vim.host.PortGroup-pg-v... 4

pg-vlan-0004              key-vim.host.PortGroup-pg-v... 4

pg-vlan-0004              key-vim.host.PortGroup-pg-v... 4

pg-vlan-0004              key-vim.host.PortGroup-pg-v... 4

pg-vlan-0004              key-vim.host.PortGroup-pg-v... 4

 

ポートグループがができました。

PowerCLI> Get-VMHost -State Connected | Get-VirtualSwitch -Name vSwitch0 | select Name,VMHost,{$_|Get-VirtualPortGroup -Name pg-vlan-0004} | ft -AutoSize

 

Name     VMHost                 $_|Get-VirtualPortGroup -Name pg-vlan-0004

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

vSwitch0 hv51-hpp1.gowatana.lab pg-vlan-0004

vSwitch0 hv51-opt1.gowatana.lab pg-vlan-0004

vSwitch0 hv55n1.vmad.local      pg-vlan-0004

vSwitch0 hv55n2.vmad.local      pg-vlan-0004

vSwitch0 hv55-has1.vmad.local   pg-vlan-0004

vSwitch0 hv55-has2.vmad.local   pg-vlan-0004

vSwitch0 hv55-ivy1.vmad.local   pg-vlan-0004

 

VM の vNIC のポートグループも変更してみます。

PowerCLI> Get-VM dg01,dg02 | Get-NetworkAdapter -Name "Network adapter 1" | select Parent,NetworkName | ft -AutoSize

 

 

Parent NetworkName

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

dg02   VM Network

dg01   VM Network

 

PowerCLI> Get-VM dg01,dg02 | Get-NetworkAdapter -Name "Network adapter 1" | Set-NetworkAdapter -NetworkName pg-vlan-0004 -Confirm:$false

 

Name                 Type       NetworkName  MacAddress         WakeOnLan

                                                                  Enabled

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

Network adapter 1    Vmxnet3    pg-vlan-0004 00:50:56:b2:d1:f8       True

Network adapter 1    Vmxnet3    pg-vlan-0004 00:50:56:b2:c1:a8       True

 

PowerCLI> Get-VM dg01,dg02 | Get-NetworkAdapter -Name "Network adapter 1" | select Parent,NetworkName | ft -AutoSize

 

Parent NetworkName

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

dg02   pg-vlan-0004

dg01   pg-vlan-0004

 

以上、vSS と ポートグループについてでした・・・

VCOPS のヒートマップでデータストアを見てみる。

$
0
0

以前、PowerCLI でデータストアを確認してみるポストをしましたが・・・

ESXi データストアへの VM 配置について。(PowerCLI でデータストア空き容量と IOPS を見てみる)

 

VCOPS だと、ヒートマップというグラフで

視覚的に使用状況の確認ができたりします。

 

標準 UI の「分析」タブには

「ヒートマップ ギャラリー」に色々なグラフ表示設定が登録されています。

 

たとえば、どこかのデータストアに 新規 VM を配置したいときに

下記のような使い方ができます。

 

データストアの空き容量についてヒートマップを見るときは

「どのデータストアのディスク容量オーバーコミットが最も高く、残り時間が最も少ないか?」

を見ると・・・

→ ds_local_04 というデータストアにそこそこ空きがありそう。

※となりの ds_nfs_181_02 というデータストアはさらに空きがありそうですが

 今回は事情により空けてます・・・

vcops-ds-heatmap-01.png

シンプロビジョニングの仮想ディスクによる容量オーバーコミットが大きいほど

グラフの色が赤くなっています。

ちなみに、ヒートマップの名前にある「~残り時間が」というのは、

「VCOPS が分析したキャパシティ管理的に、

あと何日くらいもつ空き容量がありそうか」みたいな発想のものです。

 

データストアのディスク IO 遅延についてヒートマップを見るときは

「どのデータストアの I/O 使用率が最も高く、待ち時間が発生しているか?」

あたりをみてみると・・・

→上のヒートマップで、割と空いていそうな ds_local_04 データストアは

 ディスク遅延もあまり大きくなく、負荷が割と低そう。

※となりの ds_nfs_181_02 というデータストアはさらにディスク遅延が無そうですが

 今回は事情により空けてます・・・

vcops-ds-heatmap-02.png

IO使用率(KB/秒)が大きいデータストアほど、グラフの面積が広く

遅延(読み書きあたりの遅延ミリ秒)が大きいほど色が赤くなっています。

 

といった感じで、見た感じで

「容量が空いていて負荷が低そうな ds_local_04 データストアに新規 VM を配置しよう」

みたいなことが考えやすくなります。

 

自宅検証環境なので特定の ESXi を指定してデータストアのヒートマップを見ていますが、

本来はクラスタ単位や、vCenter 単位でヒートマップを見るともっと効果的ではないかと思います。

当然ながら、データストアだけでなく CPU / メモリ / ネットワーク などについても

ヒートマップで表示できます。

 

こちらもどうぞ・・・

vCenter Operations Manager(VCOPS) 入門。

VCOPS の UI タイムアウト時間を変更する。

 

以上、VCOPS のヒートマップについてでした。

ESXi Tardisks, Ramdisks & ESXi Local State

$
0
0

Hi All..

 

During my study for my VCAP-DCD (Wish me to pass it ), I came through an interesting point that I'd like to share with you.
During reading vSphere Design Sybex V2 by Scott Lowe and Forbies Guthrie, they came though ESXi boot disk partitions and how the boot image is loaded into memory during boot.

 

Long story short, ESXi base image essentially is a TGZ file -Tar compressed file. When booting ESXi image, that tar file is uncompressed into the memory producing two types of files: VMkernel Executives and Archive Files . VMkernel are .gz files that aren't shown in the list of filesystem files and they form the main files system. Archive files are also known as VIBs or VMware Installation Bundles (Anyone experienced with Auto Deploy knows them) that contains all configurations and drivers needed for ESXi system to operate. So, what is the difference? What is the point of this post? Here it comes..

 

VIBs are always compressed files, mainly TGZ, V0n files, called Tardisks. They're not uncompressed inside the memory and used, but they're mounted as mount points in the file system as well as any other disk partition of boot disk. This makes these tardisks always read-only files read from the memory. To modify these bundles/tardisks, ESXi VMkernel uses a "Branching Technique". Each new bundle/tardisk overlays the old one and the file system sees only the last branch available. When the last bundle/tardisk is removed, the previous branch appears and is used by the file system. What if a modification is required for certain file on any tardisk?? Branching technique is used again.

 

When a modification is required, a read/write copy of the tardisk is created on a Ramdisk. Ramdisk is a container for that working read/write copy. Using branching technique, ESXi VMkernel uses the read/write copy instead of the original read-only one and any modification is done to this read/write copy. Unfortunately, this modifications will not persist any boot as it's written to RAM. To come over this, a TGZ file called state.tgz is created by internal backup process to contain all of these modified files as well as all last-laid bundles (Confirmation needed for bundles part). This state.tgz file is called ESXi State Archive.

 

So what about that internal backup process?!
This backup process was a point of small discussion between me and Mr. Wiliam Lam (@lamw). We managed to discover that blog post of Kyle Gleed that stated that this internal backup process has four scenarios to run and backup the state.tgz file to the boot disk. It's saved in /bootbank partition on the boot disk.
You can also run this backup process manually by using the command: autobackup.shas stated by Mr. Lam in his blog post.

 

I wish I was clear and straight forward in this tricky point.
Lastly, I recommend reading vSphere Design Sybex V2.

Share the knowledge..


NSX-v Multi-VTEP VM to vmnic/vmknic mapping

$
0
0

Its been a while since I last wrote a blog post so I thought I should put up a quick one.

In NSX deployments and designs I have worked on, common questions I get when using a teaming method on NSX-v of Loadbalance-SRCID/MAC is:

 

1. How can I determine what physical interface VXLAN encapsulated traffic will egress/ingress via on an ESXi host?

2. What will be the SRC IP address and SRC MAC address of the VXLAN traffic?

Please note this does not include traffic traversing a DLR, I will cover that in a later post.

So to determine this you can follow the below process:

 

If you run the command esxtop from an ESXi hosts cli, then type n (for network) you will get a list of VM's DVPorts and VMKernel interfaces (VTEPs) and more importantly what DVUplink/vmnic on the host they are mapped to as below shows. In this example I'm going to be using VM04 as an example.

 

So in the below example from esxtop VM04 is using vmnic1 (DVUplink1) on my DVSwitch.

 

Output of esxtop for VM's:

 

  67108876      39870:VM04.eth0     vmnic1 DvsPortset-1         0.00    0.00       1.94    0.00   0.00   0.00

  67108877      49943:wah1.eth3     vmnic1 DvsPortset-1          0.00    0.00       0.00    0.00   0.00   0.00

  67108878      49943:wah1.eth2     vmnic2 DvsPortset-1          0.00    0.00       0.00    0.00   0.00   0.00

  67108879      49943:wah1.eth1     vmnic2 DvsPortset-1          0.00    0.00       0.00    0.00   0.00   0.00

  67108880      49943:wah1.eth0     vmnic1 DvsPortset-1          0.00    0.00       0.00    0.00   0.00   0.00

  67108881      50475:wah2.eth3     vmnic1 DvsPortset-1          0.00    0.00       0.00    0.00   0.00   0.00

  67108882      50475:wah2.eth2     vmnic2 DvsPortset-1          0.00    0.00       0.00    0.00   0.00   0.00

  67108883      50475:wah2.eth1     vmnic2 DvsPortset-1          0.00    0.00       0.00    0.00   0.00   0.00

  67108884      50475:wah2.eth0     vmnic1 DvsPortset-1          0.00    0.00       0.00    0.00   0.00   0.00

  67108885      51009:wah3.eth0     vmnic1 DvsPortset-1          0.00    0.00       0.00    0.00   0.00   0.00

 

If you then run the below esxcli command to list what VTEP a DVPort is using, we can see that VM04 on Switch port 67108876is using a VTEP with an ID of 0.

 

/var/log # esxcli network vswitch dvs vmware vxlan network port list --vds-name=DSwitch-Cluster2 --vxlan-id=5000

Switch Port ID  VDS Port ID  VMKNIC ID

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

      67108870  vdrPort             1

      67108876  142                  0    <<< VM04

      67108877  141                  0

      67108878  143                  1

      67108879  144                  1

      67108880  145                  0

      67108883  139                  1

      67108884  140                  0

      67108885  138                  0

 

If we then use the below esxcli command to check what vmknic VTEP ID 0 maps to, this will provide the IP address and MAC address we will SRC traffic from when VM04 traffic is encapsulated in VXLAN from this host.

 

~ # esxcli network vswitch dvs vmware vxlan vmknic list --vds-name=DSwitch-Cluster2

Vmknic Name  Switch Port ID  VDS Port ID  Endpoint ID  VLAN ID  IP          Netmask        IP Acquire Timeout  Multicast Group Count  Segment ID

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

vmk1               67108871  130                    0        0  172.16.1.5  255.255.255.0                   0                      0  172.16.1.0

vmk2               67108872  137                    1        0  172.16.1.6  255.255.255.0                   0                      0  172.16.1.0

 

~ # esxcfg-vmknic -l <trunkated output>

Interface  Port Group/DVPort   IP Family IP Address        Netmask         Broadcast       MAC Address       MTU     TSO MSS   Enabled Type            

vmk1       130                 IPv4      172.16.1.5                   255.255.255.0   172.16.1.255    00:50:56:68:93:ed 1600    65535     true    STATIC           

 

We can then check again in esxtop what vmnic the VTEP vmk1 also mapped to and see if they matches what VM04 was using (vmnic1)

 

Output of esxtop for vmknic's:

 

~ #

  67108871                vmk1    vmnic1 DvsPortset-1          0.19    0.00       0.77    0.00   0.00   0.00

  67108872                 vmk2     vmnic2 DvsPortset-1          0.00    0.00       0.97    0.00   0.00   0.00

 

So from the above VM04 is using VTEP ID 0 which is vmk1. Both vmk1 and VM04 are using vmnic1

 

So in conclusion when VM04 sends traffic to be encapsulated in VXLAN:

 

1. Outer SRC IP address is 172.16.1.5 (vmknic1)

2. Outer SRC MAC address is 00:50:56:68:93:ed (vmknic1)

3. Egress host physical nic - vmnic1 (DVUplink1)

 

Thanks for reading

Kev Barrass

vCenter Server @vmworld

$
0
0

It is an exciting month at VMware with VMworld starting on Sunday in San Francisco. If you care about vCenter Server in any way, we have lined up several compelling sessions at VMworld. Many teams have spent countless hours preparing for these deep dive sessions in several key areas. We have many breakout sessions in key areas such as performance, architecture, deployment, availability, lifecycle management and distributed resource management.

In addition to the breakout sessions, we have also organized deep dives as part of TAM Customer Central. These sessions are led by Product Managers with the help of Engineering, and present a great opportunity to ask hard questions in a more intimate setting. Note that the TAM sessions are protected by a mutual NDA, and are available on a first come, first serve basis.

Make sure you add these sessions to your schedule. Look forward to meeting you at some of these sessions!

 

Breakout Sessions

TitleSpeakerDate & Time, Location
INF2705 - Datacenter and vCenter Availability Best PracticesAnil Kapur, Justin KingMonday, Aug 25, 3:30 PM - 4:30 PM
– Marriott, Yerba Buena Level, Salon 15
Tuesday, Aug 26, 11:30 AM - 12:30 PM
– Marriott, Yerba Buena Level, Salon 9
SDDC3327 - The Software-defined Datacenter, VMs, and Containers: A “Better Together” StoryKit ColbertTuesday, Aug 26, 2:00 PM - 3:00 PM– Marriott, Yerba Buena Level, Salon 6
INF1720 - Getting the Most out of vMotion - Architecture, Features, DebuggingGabriel Tarasuk-Levin,
Sreekanth Setty
Tuesday, Aug 26, 3:30 PM - 4:30 PM
– Moscone West, Room 2002
Wednesday, Aug 27, 12:30 PM - 1:30 PM
– Moscone West, Room 2003
INF2311 - vCenter Server Architecture and Deployment Deep DiveJustin King, Bob Perugini, Harish NiddagattaTuesday, Aug 26, 5:00 PM - 6:00 PM
– Moscone West, Room 3022
Wednesday, Aug 27, 12:30 PM - 1:30 PM
– Moscone West, Room 2020
SDDC3281 - A DevOps Story: Unlocking the Power of Docker with the VMware platform and its ecosystem.George Hicken, Aaron SweemerTuesday, Aug 26, 5:30 PM - 6:30 PM– Moscone West, Room 3007
INF1972 - Managing Database Size Growth for vCenter ServerRaju Angani, Jignesh ShahWednesday, Aug 27, 8:00 AM - 9:00 AM
– Moscone West, Room 3011
INF1506 - Extreme Performance Series: vCenter PerformanceRavi Soundarrajan, Ameet JaniWednesday, Aug 27, 12:30 PM - 1:30 PM
– Marriott, Yerba Buena Level, Salon 11
Thursday, Aug 28, 12:00 PM - 1:00 PM
– Moscone West, Room 2020
INF2427 - DRS : Advanced Concepts, Best Practices and Future DirectionsJeevitha, PuneetWednesday, Aug 27, 12:30 PM - 1:30 PM
– Marriott, Yerba Buena Level, Salon 8
Thursday, Aug 28, 1:30 PM - 2:30 PM
– Moscone West, Room 3003

 

 

TAM Central Deep Dives

TitleSpeakerDate & TimeRoom
vCenter Server RoadmapNarayan BharadwajMonday August 25, 11:00am – 12:00pmFoothill E, Marriott Marquis
vCenter Install & UpgradeHarish NiddagattaMonday, August 25, 12:15pm – 1:15pmFoothill F, Marriott Marquis
vSphere User Interface enhancementsMatt DreyerTuesday, August 26, 12:15pm – 1:15pmFoothill E, Marriott Marquis
vCenter Policy Based Management and Intelligent PlacementMadhup GulatiTuesday, August 26, 2:45pm – 3:45pmFoothill E, Marriott Marquis
vCenter Workload Management [vMotion, VMFork, Content Library]Mahdi Ben Hamida, Uma ChingundeWednesday, August 27, 10:30am – 11:30amFoothill E, Marriott Marquis
SLA-Driven Automated Scaling of Database ResourcesAnil Kapur, Xiaoyun Zhu, Lei LuWednesday, August 27, 10:30 - 11:30Foothill H, Marriott Marquis
Multi Hypervisor ManagementMatt DreyerWednesday, August 27, 2:15pm – 3:15pmFoothill E, Marriott Marquis
Hybrid DRS: Managing virtual infrastructure spanning private data center and hybrid cloudAnil Kapur, Anne Holler,Wednesday, August 27, 2:15pm – 3:15pmFoothill H, Marriott Marquis
vCenter Customer Q&ANarayan Bharadwaj, with vCenter EngineeringWednesday, August 27, 3:30 – 4:30Foothill E, Marriott Marquis
Data Center Facilities Management Through Virtualization : Technical Deep DiveAnil Kapur, Anne Holler, Maarten WiggersWednesday, August 27, 3:30 - 4:30Foothill F, Marriott Marquis

StorMagic & VMworld 2014 SFO

$
0
0

It’s that time of the year and StorMagic is once again in the city by the bay exhibiting at VMworld 2014 – No Limits.  This year StorMagic is busier than ever. We’ll be showcasing the newest version of SvSAN due for release in September 2014. SvSAN 5.2 boasts some advanced new features to further improve performance, manageability and efficiency of shared storage in distributed environments. Visit our booth #2519 for a live demo of these new and not yet released features.

Also, join StorMagic CEO, Hans O’Sullivan, and Cisco Product Manager for UCS E-Series Application On-boarding, Umang Barman, at the Cisco booth theatre, VMworld on the 24th August at 18:30 for a live session: Building a Robust Converged Branch Infrastructure.
They will discuss how the latest storage, virtualization and data center technologies work together to simplify and optimize application experience and availability for branch office users.

Last but not least, we’ll be giving away 3 awesome prizes at our booth on the Monday, Tuesday and Wednesday of the show at 15:00. We have Cookoo Smart Watches, Attacknid battling robot spiders and Makey Makey kits to win. But, if you’re not that lucky, why not come by the booth and grab a free powerbank to charge your devices when on the move.

We look forward to seeing you next week.

prizes for show.jpg

VMware Newsletter 6.32

$
0
0

From the editors virtual desk

Hi everyone, well I had a really great week even though it was slightly interrupted by a local public holiday on Wednesday which I had completely forgotten about. It was a bit of a surprise as I had been booking meetings and wondering why I wasn't getting any accepts.

 

I had a really good conversation and organised a technical session for one of my customers on vSphere Networking, specifically geared towards the latest features and functionality of the Distributed Switch as well as our NSX network virtualisation solution. I found the session really informative and a good reminder of how the basics need to always be revisited to ensure we are getting optimal use of our solutions.

 

I have continued to discuss this on my LinkedIn blog at http://tinyurl.com/pjduwtm.

 

VMworld is just 1 week away and it is getting really exciting. I know a number of colleagues and customers who will be traveling over for the event and I must admit I would love to be going this year with all of the awesome announcements that will be made. It is such an awesome conference and if you are going then you will be in for such a treat.

 

I hope you have a great week and look forward to chatting to you all again next week. Please feel free to get in touch with me anytime.

 

Virtually Yours

Neil Isserow

Senior Technical Account Manager

VMware Australia

nisserow @ vmware . com

 

VMworld News

Women of Purpose at VMworld - http://www.vmworld.com/blogs/vmworld/2014/08/15/women-of-purpose-at-vmworld

Women of Purpose is a community that promotes, elevates and connects women within VMware, customers, partners and employees. We were founded in 2010 and are thrilled to host our 5th annual Women of Purpose at VMworld 2014.

 

Local Events

 

Local Training Classes

VMware vSphere: Install, Configure, Manage [V5.5] Various

VMware vCloud Automation Center: Install, Configure, Manage [V6.0] 15-19 Sept

VMware vSphere: Troubleshooting Workshop [V5.5] 29-03 Oct

 

VMware Bloggers

vCenter Log Insight のデプロイ。

$
0
0

最近話題の vCenter Log Insight をデプロイしてみました。


Log Insight についてはこちらを参照・・・

http://www.vmware.com/jp/products/vcenter-log-insight

 

Log Insight は、VMware 製のログ収集&解析ツールで、

近いものとしては、Splunk や fluentd などが挙げられると思います。

 

今回使用したバージョン

VMware-vCenter-Log-Insight-2.0.3-1879692_1.ova

※OVA ファイルは、MyVMware から入手できます。

 

Web Client からデプロイ

Log Insight は 仮想アプライアンスの OVA ファイルとして

提供されているので、そのファイルを

Web Client(または vSphere Client)からデプロイするだけで使用できます。

 

今回は Web Client で「OVF テンプレートのデプロイ」してみます。

log-insight-deploy01.png

 

デプロイする OVA ファイルを選択します。

log-insight-deploy02.png

 

「追加の構成オプションの承諾」にチェックを入れると

次へ進めるようになります。

log-insight-deploy03.png

 

EULA の承諾 画面で、「承諾」ボタンをクリックすると

「次へ」進めるようになります。

log-insight-deploy04.png

 

デプロイする VM の名前は、デフォルトのまま

「VMware vCenter Log Insight」にしました。

デプロイ先のデータセンタ か フォルダを選択して「次へ」。

log-insight-deploy05.png

 

VM の構成を選択します。

今回は一番小さい「Extra Small」にしてみました。

2vCPU、メモリ 4GB、仮想ディスク 132GB になります。

log-insight-deploy06.png

 

デプロイ先のリソースを選択します。

例では、ESXi を選択しています。

log-insight-deploy07.png

 

仮想ディスク フォーマットは

動作確認目的なので「Thin Provisison」にしました。

仮想ディスクのサイズは 132GB ですが、

Thin 形式であれば 5GB くらいあればとりあえずデプロイできます。

log-insight-deploy08.png

 

Log Insight の VM を接続するポートグループを選択します。

log-insight-deploy09.png

 

Log Insight の VM に設定するネットワーク構成情報を入力します。

  • ホスト名
  • IP アドレス
  • サブネットマスク
  • デフォルトゲートウェイ
  • DNS サーバのアドレス

log-insight-deploy10.png

 

この画面で、root パスワードも設定します。

log-insight-deploy11.png

 

確認して「終了」をクリックすると、デプロイが開始されます。

log-insight-deploy12.png

 

デプロイされた VM は Extra Small だと

仮想マシンバージョンが「7」なので、バージョンアップしておきます。

log-insight-deploy13.png

 

仮想マシンバージョンは、

「ESXi 5.5 以降」(vmx-10)にしておきます。

log-insight-deploy14.png

 

Log Insight の VM を起動します。このような起動画面です。

初回起動は少し時間がかかるようなので、しばらく待ちます。

log-insight-deploy15.png

 

起動すると、このような画面になります。

log-insight-deploy16.png

 

上の画面で「ALT + F1」キーを押すと、コンソール画面を表示してログインできます。

ちなみに OS は SUSE Linux です。

log-insight-deploy17.png

 

Web ブラウザでアクセスすると、

Log Insight のセットアップ画面が表示されます。

log-insight-deploy18.png

セットアップにつづく・・・

vCenter Log Insight のデプロイの続き。

 

以上、Log Insight のデプロイでした。

vCenter Log Insight のデプロイの続き。

$
0
0

前回のポストの続きで、Log Insight をセットアップしていきます。

vCenter Log Insight のデプロイ。

 

それでは、OVA ファイルのデプロイ後に起動した Log Insight のセットアップを進めます。

 

Web ブラウザでアクセスすると、セットアップ画面が表示されます。

  https://<Log Insight 仮想アプライアンスに設定したアドレス>

log-insight-setup01.png

 

「Deployment Type」は、最初の 1台目の Log Insight なので

「Start New Deployment」を選択します。

log-insight-setup02.png

 

Log Insight の Web UI にログインするための

admin ユーザのパスワードを設定します。

log-insight-setup03.png

 

ライセンスキーを入力して、「Add License Key」をクリックします。

log-insight-setup04.png

 

入力したライセンスキーの情報が表示されるので「Continue」。

log-insight-setup05.png

 

Log Insight からの情報通知先のメールアドレス設定、

カスタマエクスペリエンス向上プログラムへの送信などができますが、

今回はメールサーバもなく、インターネットにつながらない検証サーバなのでスキップします。

log-insight-setup06.png

 

時刻同期の設定は

デフォルトでは VMware の NTP サーバが 4台 設定されていますが、

今回は 自宅内の NTP サーバにしました。

log-insight-setup07.png

 

SMTP サーバの設定も、

今回はメールを使わないつもりなのでデフォルトのままです。

log-insight-setup08.png

 

Log Insight のセットアップが終わりました。

log-insight-setup09.png

 

まだ、ログ収集対象を何も登録していないので、

この流れで vCenter (と ESXi)を登録しておきます。

画面に表示される「vSphere Integration」のリンクをクリックすると、

そのまま vCenter 登録の画面に進めます。

log-insight-setup10.png

 

vSphere Integration の画面で、ログを収集する vCenter の情報を入力します。

  • vCenter のアドレス(hostname)
  • vCenter にログインするユーザ名
  • vCenter にログインするユーザのパスワード

この画面で「Advanced options」リンクをクリックすると

vCenter 管理下の ESXi を個別選択して登録することもできます。

log-insight-setup11.png

 

「Advanced options」をクリックすると、ESXi の一覧が表示されます。

ちなみに、デフォルトは ESXi をまとめて登録できる

「Configure all ESXi hosts」でした。

log-insight-setup12.png

 

「Test Connection」で接続テストをして、「Save」します。

log-insight-setup13.png

 

vCenter や ESXi の登録設定中です。

ESXi の Syslog 転送先設定も、自動的に Log Insight に変更されます。

log-insight-setup14.png

 

設定完了です。

log-insight-setup15.png

 

Dashboards を開くと、

ログがすでに収集されている様子が見られます。

log-insight-setup16.png

 

ESXi の Syslog 設定もちゃんと変更されてました。

※今回は PowerCLI で確認してます。

※「192.168.5.197」は、今回 Log Insight に設定した IP アドレスです。

PowerCLI C:\> Connect-VIServer vc55u1-1.vmad.local

PowerCLI C:\> Get-VMHost | select Name,Version,Build | sort Name | ft -AutoSize

 

Name                 Version Build

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

hv55-has1.vmad.local 5.5.0   1623387

hv55-has2.vmad.local 5.5.0   1623387

hv55-ivy1.vmad.local 5.5.0   1623387

hv55n1.vmad.local    5.5.0   1623387

hv55n2.vmad.local    5.5.0   1623387

hv55n3.vmad.local    5.5.0   1623387

hv55n4.vmad.local    5.5.0   1623387

 

PowerCLI C:\> Get-VMHost | select Name,{$_|Get-VMHostSysLogServer} | sort Name | ft -AutoSize

 

Name                 $_|Get-VMHostSysLogServer

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

hv55-has1.vmad.local udp://192.168.5.197:514

hv55-has2.vmad.local udp://192.168.5.197:514

hv55-ivy1.vmad.local udp://192.168.5.197:514

hv55n1.vmad.local    udp://192.168.5.197:514

hv55n2.vmad.local    udp://192.168.5.197:514

hv55n3.vmad.local    udp://192.168.5.197:514

hv55n4.vmad.local    udp://192.168.5.197:514

 

ちなみに、今回の Log Insight のバージョンは

2.0 GA (2.0.3-1879692)でした。

log-insight-setup17.png

 

ふと VMworld などの発表を見ていたら

どうやらクラウド管理製品群が vRealize Suite という名前になって、

vCenter Log Insight も

vRealize Log Insight という名前になるようです。

 

すでに vRealize な Datasheet も公開されていました。

http://www.vmware.com/files/pdf/products/vrealize-cmp/vmware_vrealize_cloud_management_platform.pdf

 

以上、Log Insight のセットアップでした。

VMware Newsletter 6.33

$
0
0

From the editors virtual desk

Hi everyone, I am just back from a trip to Sydney which was very enjoyable but because of this I have fallen behind on some of my additional learning which I hope to catch up on next week.

My customers are almost all finished with their vSphere 5.5 upgrades and many are now turning their attention to other more advanced and potentially valuable projects now that this is complete. One of these that is gaining momentum amongst my customers is preparing for a Hybrid Cloud by ensuring that their internal private cloud which is almost 100% virtualised is being operated in a similar way. What I am seeing now is many customers really asking the important questions not around moving to the public cloud but rather how do they operate their own internal environment more like a private cloud but with the benefits they have enjoyed in their own environment.

I think this is a very exciting time as many of our customers start to shift their highly virtualised environments to a more cloud like structure and I would say that many will then start to investigate the Hybrid Cloud offering from VMware as the next step to extend their current environment for suitable workloads.

This brings me on to my final topic of VMworld which starts this week in San Francisco. Its going to be awesome with literally tens of thousands of VMware faithful descending on the beautiful city of San Francisco for the premier event of the year. There have been so many pre-announcements and one of them which I beieve is gaining much traction is vCloud Air. VMware is committed to the cloud more than anyone else with our rich history in helping organisations with their internal private cloud and now extending that to the Hybrid Cloud to bring even more solution capacity. Get familiar with this and the additional benefits at http://vcloud.vmware.com/.

If you are in San Francisco for VMworld have an amazing time and have a vBeer on me

Virtually Yours

Neil Isserow

Senior Technical Account Manager

VMware Australia

nisserow @ vmware . com

VMworld Blog (http://www.vmworld.com/blogs/vmworld/)

Solutions Exchange - the Whole SHEBANG!

There are two parts to the Solutions Exchange: the countless number ofsolutions(try to count – we dare you!) and theexchange of ideas, information, and some great swag. The expo hall  truly illustrates VMware’s story. We are excited to highlight about 250 companies who are part of our very important Partner ecosystem. Malery Lassen, Sponsorship Manager, says “we’re an industry event and we’re happy to let our customers interface with companies who hold different philosophies… seems fitting that 2 out of the 3 major networking events at VMworld happen inside the Solutions Exchange!”

Hang Space Social Media & Community

The VMworld Hang Space is a huge open-space room next to the General Session auditorium in lower Moscone North (just below the escalators).  Whether new to VMworld, or experienced alumni, plan to spend time here networking with bloggers, subject experts, co-workers and VMworld attendees. It's the perfect place to meet-up, get organized, catch up on news & email, write blogs, browse social media streams, charge devices, or just relax.

VMworld 2014 Hands-on Labs – What to Expect

Hello Friends,

We are very excited about another great Hands-on Labs at VMworld and happy to give you an inside peek at what is coming.
Why attend Hands-on Labs during VMworld ?
#1.Be the first to take the latest Hands-on Labs.  Our labs are released every year at VMworld US. The labs feature the latest products, features and solutions from VMware and partners.
#2.Interact with over 225 VMware product experts under one roof. Our experts are ready to provide guidance, share best practices when using our products.  This is probably the only place in the universe where you can get access to this many product experts under one roof.
#3. Interact with your peers, and colleagues. This year we are featuring “Focus Areas” where like-minded individuals can take the same lab and share their experiences in a very casual and interactive manner.

 

Local Training Classes (Brisbane)

Tinyurl.com/au7z3cr

VMware vCloud Automation Center: Install, Configure, Manage [V6.0] 15-19 Sept

 

VMware vSphere: Install, Configure, Manage [V5.5] 22 - 26 Sept

 

VMware vSphere: Troubleshooting Workshop [V5.5] 29 - 03 Oct

VMware Bloggers


Optimising vCenter Performance

$
0
0

Description:  This document outlines considerations around optimisation of vCenter Server instances and best practice recommendations to maximise performance of your vCenter ecosystem. Each item listed should be addressed in the context of the target environment as there is no one solution to optimise the vCenter management environment. The following is simply a list of recommendations that should, to some extent, improve performance in most environments.

 

Prerequisites: 

             Microsoft Windows vCenter Server

             Microsoft SQL Database Instance

 

Part 1 – vCenter Server

                             

Description

Recommendations / Best Practices / KB Links

Virtual Server Sizing

Ensure that the vCenter virtual   system(s) are sized accordingly based in the inventory size. Where vCenter   components are separated and distributed across multiple virtual machines   ensure that all systems meet the sizing recommendation set out in the   installation and configuration documentation https://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html

(vSphere 5.1 )

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2021202

Distribute vCenter Services across   multiple virtual machines

Depending on inventory size, multiple   virtual machines can be used to accommodate different vCenter roles. VMware   recommends separating VMware vCenter, SSO Server, Update Manager and SQL for   flexibility during maintenance and to improve scalability of the vCenter   management ecosystem.

Dedicated Management Cluster

For anything other than the smallest   of environments, VMware recommends separating all vSphere management   components onto a separate out-of-band management cluster. The primary   benefits of management component separation, include:

·           Facilitating quicker troubleshooting and problem resolution as   management components are strictly contained in a relatively small and   manageable cluster.

·           Providing resource isolation between workloads running in the   production environment and the actual systems used to manage the   infrastructure.

·         Separating the management components from the resources they are   managing.

vCenter to Host operational latency

The number of network hops between   the vCenter Server and the ESXi host affects operational latency. The ESXi   host should reside as few network hops away from the vCenter Server as   possible.

vCenter to SQL Server operational   latency

The number of network hops between   the vCenter Server and the SQL database affects operational latency. Where   possible, vCenter should reside on the same network segment as the supporting   database. If appropriate, configure an affinity rule to ensure that the   vCenter Server and database server reside on the same ESXi host, reducing   latency still further.

Java Max Heap Size

Ensure that the max heap size for   Java virtual machine is set correctly based on the inventory size.  Confirm heap size on JVM Heap settings on   vCenter, Inventory Service, SSO and Web Client are checked. Monitor Web   Services to verify. (vSphere 5.1)

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2021302

Client Connections

Attempt to limit the number of   clients connected to vCenter Server as this affects its performance. This is   particularly the case for the traditional Windows C# client.

Performance Monitoring

Use performance monitoring tools to   ensure the health of the vCenter eco system and troubleshot problems as they   arise. Where appropriate, configure a vC Ops Custom Dashboard for   vCenter/Management components.  Also   ensure appropriate alerts and notifications on performance monitoring tools   exist.

Virtual disk type

All management virtual machine VMDK’s   should be provisioned in an eagerZeroedThick format.  This   provides approximately a 10-20 percent performance improvement over the other   two disk formats.

vCenter vNIC  type

Ensure to employ the VMXNET3 paravirtualized network adaptor to maximise network   throughput, efficiency and reduce latency.

ODBC Connection

Ensure that the vCenter and VUM ODBC   connections are configured with the minimum permissions required for daily   operations. Additional permissions are required during installation and   upgrade activities but not for day to day operations. Please refer to the   Service Account Permissions section below.

vCenter Logs Clean Up

vCenter server has no automated way of purging old vCenter   Log files. These files can grow and consume significant disk space on the   vCenter Server. Consider a 3/6 monthly scheduled task to delete or move log   files older than the period of time defined by business requirements.

The example, the VBscript  below could be used to clean up old log files from vCenter. This script   delete files that are older than a fixed number of days, defined in line 9,   from the path set in line 6. This VBscript can be   configured to run as a scheduled task using the windows task scheduler.

Dim Fso

Dim Directory

Dim Modified

Dim Files

Set Fso = CreateObject("Scripting.FileSystemObject")

Set Directory = Fso.GetFolder("C:\ProgramData\VMware\VMware   VirtualCenter\Logs\")

Set Files = Directory.Files

For Each Modified in Files

If DateDiff("D",   Modified.DateLastModified, Now) > 180 Then Modified.Delete

Next


For more information, refer to KB article: KB1021804Location of vCenter Server log files. 

For additional information on modifying logging   levels in vCenter please refer toKB1004795 and KB1001584.

Note:   Once a log file reaches a maximum   size it is rotated and numbered similar to component-nnn.log files and they   may be compressed.

Statistics   Levels

Statistic   collection intervals determine the frequency at which statistic queries   occur, the length of time statistical data is stored in the database, and the   type of statistical data that is collected.


As   historical performance statistics can take up to 90% of the vCenter server   database size, they are the primary factor in the performance and scalability   of the vCenter Server database. You can view the collected historical statistics   through the performance charts in the vSphere Web Client, through the   traditional Windows Client or through command-line monitoring utilities for   up to 1 year after the data was first ingested into the database.

Ensure   that statistics collection times are set as conservatively as possible so   that the system does not become overloaded. At the same it is equally   important to ensure that the retention of this historical data meets the   customer’s data compliance requirements.

Because   the statistics data consumes such a large proportion of the database, proper   management of vCenter statistics is an important consideration for the overall   database health. In addition, the processing of this data through a series of   rollup jobs to stop the SQL server becoming overloaded, is also a key consideration   for vCenter Server performance.


For   Instance:

Set   new DB Data Retention Period of 60 Days

Configure   DB to not retain performance data beyond 60 days.

Task   and Events Retention

Ensure   that Task and Events Retention levels are set as conservatively as possible   whilst meeting the customer’s data retention requirements. Every time a task   or event that is executed via vCenter, this is stored in the database. For   example a task is created when a user powers on or off on a virtual machine   or an event when something occurs such as vCPU  usage for a VM changing to red.

vCenter Server has a   Database Retention Policy setting that allows you to specify after how long   vCenter Server tasks and events should be deleted. This correlates to a   database rollup job that purges the data from the database after the selected   period of time.

Whilst   compared to statistical data these tables consume a relevantly small amounts   database space, it is good practice to consider this option for further   database optimisation. 

For   Instance, by default, vCenter is configured to store tasks and events data   for 180 days. However, it may be possible, based on the customer’s compliance   requirements, to configure vCenter not to retain Event and Task Data in the   database beyond 60 days.

vCenter   Server Backup Best Practice

In addition to scheduling regular backups of the vCenter database, the backups   for the vCenter Server should also include the SSL certificates and license   key information.

 

 

Part 2 – SQL DB Server

                                 

SQL   Database Server Disk Configuration

The   database data file generates mostly random I/O, while database transaction   logs generate mostly sequential I/O. The traffic for these files is almost   always simultaneous so it’s preferable to keep these files on two separate   storage resources that don’t share disks or I/O.

Therefore,   where a large inventory demands it, ensure that the vCenter Server database   uses separate drives for data and logs which, in turn, are backed by   different physical disks.

tempDB Separation

For   large inventories place tempDB on a different   drive, backed by different physical disks than the vCenter database files or   transaction logs.

Reduce   Allocation Contention in SQL Server tempDB database

Use   multiple data files to increase the I/O throughput to tempDB.   Configure 1:1 alignment between TempDB files and vCPUs  (up to eight) by spreading TempDB across at least as many equal sized files   as there are vCPUs.

For   instance, where 4 vCPUs exist on the SQL server,   create three additional TempDB data files, and make them all equally sized.   They should also be configured to  grow   in equal amounts

After   changing the configuration, restart the SQL Server instance. For more   information please refer to: http://support.microsoft.com/kb/2154845

Database   Connection Pool

vCenter server starts,   by default, with a database connection pool of 50 threads. This pool is then   dynamically sized according to vCenter workload. If high load is expected due   to a large inventory, then the size of the pool can be increased to 128   threads. This will increase memory consumption and load time of the vCenter   Server. To change the pool size, edit   the vpxd.cfgfile,   adding: Where ‘128’ is the number of connection threads to be configured.


    
< vpxd>
  < odbc>
  < maxConnections>128</maxConnections>
  < /odbc>
  < /vpxd>

Table   Statistics

Update statistics   of the tables and indexes on a regular basis for better overall performance   of the database. Create an SQL job to carry out this task or   alternatively it should form part of a vSphere database maintenance plan.

http://sqlserverplanet.com/dba/update-statistics

Index   Fragmentation

(Not   Applicable to vCenter 5.1 or newer)

Check   for fragmentation of index objects and recreate indexes if needed. This   happens with vCenter due to statistic roll ups. Defragment after <30%   fragmentation. See thisKB1003990.

Note: With the new enhancements and   design changes made in the vCenter Server 5.1 database and later versions,   this is no longer applicable or required.

Database   Recovery Model

Set   the transaction logs to SIMPLE  recovery. This model will reduce the disk space needed for the logs as well   decrease I/O load. 

Choosing   the Recovery Model for a Database:

http://msdn.microsoft.com/en-us/library/ms175987(SQL.90).aspx

How   to view or Change the Recovery Model of a Database in SQL Server Management   Studio

http://msdn.microsoft.com/en-us/library/ms189272(SQL.90).aspx

Virtual   Disk Type

Where the vCenter database server is   a virtual machine, ensure that all VMDK’s are provisioned in an eagerZeroedThick format.  This   option provides approximately 10-20 percent performance improvement over the   other two disk formats.

Verify   SQL Rollup Jobs

Ensure SQL Agent rollup jobs have   been created on SQL during the vCenter Installation.  For instance:

  • Past Day stats rollup
  • Past Week stats rollup
  • Past Month stats rollup

For the full set of   stored procedures and jobs please refer to the appropriate article below.

If necessary, recreate MSSQL agent   rollup jobs.

Note that detaching, attaching,   importing, and restoring a database to a newer version of MSSQL Server does   not automatically recreate these jobs. To recreate these jobs, if missing,   please refer to:  KB1004382.

KB 2033096 (vSphere 5.1   & 5.5)

http://kb.vmware.com/kb/2033096

KB 2006097 (vSphere   5.0)

http://kb.vmware.com/kb/2006097

Ensure that the myDB  references the vCenter Server database and not the master or some other   database. If these jobs reference any other database, you must delete and   recreate the jobs.

Ensure database jobs are running   correctly

Monitor scheduled database jobs to   ensure they are running correctly.

For more information, refer to KB   article: Checking   the status of vCenter Server performance rollup jobs: KB2012226

Verify MSSQL Permissions

Ensure that the local, SQL and AD   Permissions required are in place and align with the principle of least   privilege (see below)

If necessary, truncate all unrequired   performance data from the database (Purging Historical Statistical Performance   Data)

For more information, refer to   KB article: Reducing   the size of the vCenter Server database when the rollup scripts take a long   time to run KB1007453

To truncate all performance data from   vCenter Server 5.1 and 5.5:

Warning:This procedure   permanently removes all historical performance data. Ensure to take a backup   of the database/schema before proceeding.

Shrink Database

After purging historical data from   the database optionally shrink the database.    This is an online procedure to reduce the database size and to free up   space on the VMDK, however, this activity will not in itself improve   performance.

Shrinking the size of the VMware   vCenter Server SQL database  KB1036738

http://msdn.microsoft.com/en-us/library/ms189080.aspx

Rebuilding indexes to Optimize the performance of SQL Server

Configure regular maintenance job to rebuild indexes. KB2009918

VPX_HIST_STAT  

Table   Sizes

VMware   recommend a fill factor of 70% for the 4 VPX_HIST_STAT tables. If this is too   high for resources on the server, then it will need to take time splitting   pages, which equates to additional I/O.

If   you are experiencing high unexplained I/O in the environment, monitor the SQL   Server Access Methods object: Page Splits/sec. Page splits are expensive, and cause your table to perform   more poorly due to fragmentation. Therefore, the fewer page splits you have   the better your system will perform.

By   decreasing the fillfactor in your indexes, what you   are doing is increasing the amount of empty space on each data page. The more   empty space there is, the fewer page splits you will experience. On the other   hand, having too much unnecessary empty space can also hurt performance   because it means that less data is stored per page, which means it takes more   disk I/O to read tables, and less data can be stored in the buffer cache.

High   Page Splits/sec will result in the   database being larger than necessary and having more pages to read during   normal operations. 

Determining   where growth is occurring in the VMware vCenter Server database (1028356)

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1028356

Troubleshooting VPX_HIST_STAT table sizes in VMware   vCenter Server 5.1KB2038474

Reducing   the size of the vCenter Server database when the rollup scripts take a long   time to runKB1007453

Monitor Database Growth

Monitor database growth over a period   of time to ensure the database is functioning as expected. For more   information, refer to KB article: Determining where growth is occurring in   the vCenter Server database KB1028356

schedule and verify regular database   backups

The vCenter, SSO, VUM and SRM servers   are by themselves stateless. The databases themselves are far more critical   since they store all the configuration and state information for each of the   management components. These databases must be backed-up nightly and the   restore process of each database needs to be tested periodically. 

Ensure that a schedule of regular   backups exists of the vCenter database and based on requirements of the   business, restore and mount databases from backup periodically onto a non-production   system to ensure a clean recovery is possible, should database corruption or   data loss occur in the production environment.

Create a Maintenance Plan for vSphere   databases

Work with your DBA’s to create a   daily and weekly database maintenance plan. For Instance:

·           Check Database   Integrity

·           Rebuild Index

·           Update Statistics

·           Back Up Database (Full)

·           Maintenance Cleanup Task

Note: DO NOT SHRINK DB IN   MAINTENACE PLAN UNLESS THERE IS A SPECIFIC REQUIREMENT TO RECLAIM DISK SPACE

http://msdn.microsoft.com/en-us/library/ms189080.aspx

 

 

 

Part 3 - Service Account Permissions (Least Privilege)

       

vCenter Service Account  

Required by the ODBC Connection for   access to the database. The vCenter service account must be configured with dbo_owner  privileges for normal operational use.    However, the vCenter database account being used to make the ODBC   connection also requires the db_ownerrole   on the MSDB System database during installation or upgrade of the vCenter   Server.  This permission facilitates the installation of SQL Agent jobs   for vCenter statistic rollups.

Typically the DBA would only grant   the vCenter service account the db_owner role on the MSDB System database when installing   or upgrading vCenter, then revoke that role when these activities are   complete.

RSA_DBO

Only Required for SSO 5.1 the RSA_DBA   account is a local SQL account which is used for creating the schema (DDL)   and requires dbo_owner  permissions.

RSA_USER

Only Required for SSO 5.1, the   RSA_USER reads and writes data (only DML).

VUM Service Account

Despite being a 64bit application,   VUM requires a 32bit ODBC connection from “C:\Windows\SysWOW64\odbcad32.exe”.   The VUM service account must be provide the dbo_owner permission on the   VUM DB. The installation of vCenter Update Manager 5.x with a Microsoft SQL   back end database also requires the ODBC connection account to temporarily   have db_owner  permissions on the MSDB System database. This was a new requirement in   vSphere 5.0.

As with the vCenter service account,   typically the DBA would only grant the VUM service account the db_owner role   for the MSDB System database when installing or upgrading the VUM component   of vCenter, then revoke that role when this task is complete.

SRM Service Account

Despite being a 64bit application,   SRM requires a 32bit ODBC connection from “C:\Windows\SysWOW64\odbcad32.exe”.   The SRM service account must be configured with the dbo_owner privilege on the SRM   database.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1027973 

 

vCenter Log Insight に VC 追加登録。

$
0
0

Log Insight には 複数台の vCenter Server を登録できます。

解析対象のログを増やしたかったので、vCenter を追加登録してみました。


Log Insight の Web UI にログインして、画面右上のアイコン →「Administration」を開き

左画面にある「vSphere」を開きます。

ここで「Add vCenter Server」をクリックします。

log-insight-vcadd-01.png


追加登録する vCenter の情報を入力して「Test Connection」でテストします。

そして「Save」で保存します。

log-insight-vcadd-02.png


設定変更が完了しました。

log-insight-vcadd-03.png

 

追加登録した vCenter の「View details」をクリックすると・・・

log-insight-vcadd-04.png


その vCenter で管理していた ESXi も登録されたことがわかります。

※ ESXi の Syslog 転送先が変更されます。

log-insight-vcadd-05.png

 

ダッシュボードを開いて

ホスト名などで検索すると、新たにログが追加されていることがわかります。

log-insight-vcadd-06.png

 

以上、地味な話ですが、Log Insight への vCenter 追加登録でした。

[VMware] VMware announced EVO:RAIL

$
0
0

先週サンフランシスコで開催されましたVMworld 2014でVMware発のコンバージドインフラストラクチャーEVO:RAILが公開されました。

 

このEVO:RAILはプロジェクトMARVINで知られていたものでハードウェア/ソフトウェアの統合ソリューションの新しい名称で、去年からVMwareがハードウェア市場にまで手を伸ばすという風に噂されていたものです。

 

2UのハードウェアにvSphere、Virtual SAN、LogInsightが提供されるアプライアンスで、最短パスワードを2回入力するだけで、構成が終わるとのことです。(完全自動構成時の場合)

 

紹介ビデオを見れば一目瞭然。今までハードウェアの設置から始まるvSphereの導入が劇的に短縮されます。

 

EVO:RAILアプライアンスは、4ノードで構成され、最大4アプライアンス(16ノード)まで拡張できるとのことです。

 

各ノードはIvy-Bridgeプロセッサー×2、192GBメモリ、1.2TB×3 HDD、400GB×1 SDD、10GbE×ネットワークポートで構成され、アプライアンス当たり最大100台の仮想マシンまたは最大250台の仮想デスクトップを集約できることを想定しているとのことです。

 

現在EVO:RAILのパートナーとしてはDELL、Fujitsu、EMC、SuperMicro、NetOne Systems、Inspurの6社で、各パートナーは自社製x86サーバーwモデルとしてプロダクトを発表していますし、価格は$80,000~$250,000帯になると予想されています。

 

非常に魅力的なプロダクトです。

Swap to Host Cache (wrongly aka. Swap to SSD)

$
0
0

Hi All ...

 

vSphere 5.0 and later came with so many enhancement for Virtual Infrastructure and Swap to Host Cache is one of these. This feature allows you to use any SSD datastore -some or all of it- as Write-back Cache to swap to it ESXi memory pages in case of Hard State memory contention. Many of vExperts wrote about it and its technical how-to configuration, like Duncan Epping in his complete-guide blog posthere.

 

Now, you're asking: "So, why do you write this blog post?? Do you wanna to copy-paste??!"  The answer is unfortunately, NO!!

I write this blog post to answer a question that may come to your mind while reading about this awesome feature: "What is the difference between using SSD Datastore as a Host Cache and just configure the host to put VMs .vswp files in this datastore???"

 

While reading many sources about Host Cache feature, I didn't find anyone stated clearly any answer to this question, but the following screenshot gave me the first ray of light. It's a screenshot -from Duncan's post- of comments between him and one of his visitors who compares and asks the same question nearly.

Duncan.jpg

 

Matt van Mater -the visitor- compared the two features: Host Cache and Dedicating certain SSD Datastore for VMs .vswp files. Duncan's answer clearly stated that the space usage would be really lower if you use Host Cache. I began to search about Write-back Cache technologies (It was my first time to deal deeply with Cache technologies) and I found that simple diagram from Wikipedia:

Write-back_with_write-allocation.svg.jpg

This simple diagram also indicates how Write-back Cache works and why it really uses small space size and gives high response. All of these things, gave me the following answer to the question above nad it was all in the underlined word Write-back Cache:

            1-) Host Cache is a Write-back cache, which means that it makes both Read/Write operations fast, as it reads and writes mainly to SSD Drive. That improves reading from swap and changing after warming up period. Only some blocks of swap files are written back to the .vswp files reside with VMs folders.

2-) Host Cache is shared between VMs, as it doesn't create a specific file for each VM like normal .vswp file. It only creates a bunch of files on Hose Cache that ESXi host will just swap to it. That makes any Read/Write operation from any VM on the host configured will benefit from a sharing probability of its memory page with any other VM (same concept like Transparent Page Sharing). This greatly reduces the chance to access .vswp file location and improves performance if the shared block under operation is on the cache, thus Host Cache needs some Warming up period.

3-) SSD Datastore size for placing swap files of N VMs= N*Size of single Swapfile (assuming equal .vswp file sizes). Using Host Cache, and due to sharing memory pages of it, this size is greatly reduced (same concept like Transparent Page Sharing).

4-) In case of using Network/FC-based SSD Datastore for placing swap files, the network latency -even when using FC SAN- is much greater than SSD access latency and hence, Host Cache -which should only configured on local SSD disks for the same reason- always gives higher performance.

 

I hope this clears this small mystery about the difference between Swap to Host Cache and setting SSD Datastore as a .vswp files location.
Waiting for your feedback and comments.

Special Thanks to: Duncan Epping - Matt van Mater


Share the knowledge...

PowerCLI で接続中 vCenter の確認。($global:DefaultVIServers)

$
0
0

PowerCLI で、接続中の vCenter を確認したいことがあります。


実は $global:DefaultVIServer、$global:DefaultVIServers

という変数に、接続中 vCenter が含まれまれるので

それを参照するとよいのではないかと思いました。

 

まず、PowerCLI で vCenter に接続しておきます。

今回は、2台の vCenter に接続します。

 

※複数 vCenter への接続については下記もどうぞ。

PowerCLI から複数の vCenter に接続する方法。

PowerCLI> Connect-VIServer vc55u1-1.vmad.local, vc55u1-2.vmad.local

 

Name                           Port  User

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

vc55u1-1.vmad.local            443   VMAD\Administrator

vc55u1-2.vmad.local            443   VMAD\Administrator

 

このような感じで、何らかのオブジェクトの UID で

確認もできるのですが、結構微妙な感じです。

PowerCLI> Get-Datacenter | select Uid -Unique

 

Uid

---

/VIServer=vmad\administrator@vc55u1-1.vmad.local:443/Datacenter=Datacenter-datacenter-21/

/VIServer=vmad\administrator@vc55u1-2.vmad.local:443/Datacenter=Datacenter-datacenter-2/

 

PowerCLI> Get-Datacenter | select @{N="VIServer";E={$_.Uid -replace ".*@|:443.*",""}} -Unique

 

VIServer

--------

vc55u1-1.vmad.local

vc55u1-2.vmad.local

 

そんなとき

上記よりよさそうな確認方法を見つけました。

 

では、$global:DefaultVIServer と $global:DefaultVIServers

という変数を見てみます。

接続中の vCenter 情報が入っていて、

$global:DefaultVIServers の方が複数 vCenter に接続した時も使えて便利そうです。

PowerCLI> $global:DefaultVIServer

 

Name                           Port  User

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

vc55u1-2.vmad.local            443   VMAD\Administrator

 

PowerCLI> $global:DefaultVIServers

 

Name                           Port  User

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

vc55u1-2.vmad.local            443   VMAD\Administrator

vc55u1-1.vmad.local            443   VMAD\Administrator

 

下記のようなコマンドラインで、接続中の vCenter が確認できます。

2台の vCenter 5.5 に接続していることがわかります。

PowerCLI> $global:DefaultVIServers | select Name,IsConnected,Version,Build | ft -AutoSize

 

Name                IsConnected Version Build

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

vc55u1-2.vmad.local        True 5.5     1623101

vc55u1-1.vmad.local        True 5.5     1623101

 

ちなみに、ESXi にも PowerCLI 接続した場合も、

ちゃんと見分けることができます。

ためしに、ESXi 5.1 u1 に追加接続してみました。

PowerCLI> Connect-VIServer hv51-opt1.gowatana.lab

Name                           Port  User

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

hv51-opt1.gowatana.lab         443   root

 

ProductLine が

vpx だと vCenter で、embeddedEsx だと ESXi です。

PowerCLI> $global:DefaultVIServers | select Name,IsConnected,ProductLine,Version,Build | ft -AutoSize

 

Name                   IsConnected ProductLine Version Build

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

hv51-opt1.gowatana.lab        True embeddedEsx 5.1     1065491

vc55u1-2.vmad.local           True vpx         5.5     1623101

vc55u1-1.vmad.local           True vpx         5.5     1623101

 

作業手順書とかで「接続している vCenter が正しいことを確認して~」

みたいなときに便利そうな気がしました。

 

ちなみに、今回試した PowerCLI のバージョンはこれです。

PowerCLI> $version.UserFriendlyVersion

VMware vSphere PowerCLI 5.5 Release 2 build 1671586

 

以上、PowerCLI で接続中 vCenter を確認する方法でした。

Viewing all 3135 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>