Category Archives: TKG/TKGI/Tanzu Run/Cloud Native/Modern Application

Certified Kubernetes Administrator (CKA) Exam Experience Sharing

First of All Happy New Year 2021 every one and have blessed 2021 🙂

Last 3-4 months have been great learning  for Cloud Native. Started my cloud native  journey with VMware Tanzu Portfolio covering –

  • VMware Tanzu Kubernetes Grid (TKG)
  • Tanzu Kubernetes Grid Service (TKGS)
  • VMware Tanzu Mission Control (TMC)
  • VMware Tanzu Kubernetes Grid Integrated Edition (TKGI)
  • VMware vSphere with kubernetes
  • VMware Enterprise PKS (Pivotal Container Service)

While going through all the above, Where all the discussion starts and end with cloud native aka Kubernetes (K8s), this attract me to Certified Kubernetes Administrator (CKA) exam. 

The Certified Kubernetes Administrator (CKA) created by the Cloud Native Computing Foundation (CNCF), in collaboration with The Linux Foundation.

Started exploring the best course for this, which covers all the topics in CKA exam and also provide Labs to practice, as this is complete hands on exam and need hell lot of practice to clear this exam.

Came across these 2 super awesome courses developed by Mumshad Mannambeth on Udemy.

1. Kubernetes for the Absolute Beginners – Hands-on

2. Certified Kubernetes Administrator (CKA) with Practice Tests (Kubernetes v1.19)

My focus was more on Practice Tests with these courses, and frankly speaking i did 4-5 times all the labs to be confident enough before booked my exam. Not easy to complete 4-5 times all the labs, need many days to complete and i know how many sleepless night i had to complete these labs.

Exam fee is US$ 300. You can find 30-40% discount coupons on this exam fee.

There were total 17 questions with 120 mins to complete. For my experience, I tried all  17 questions, i know few i did wrong 😉 but i tried all to finish. In general, the questions are not too difficult if you practice enough or your fundamentals is clear, but I think it’s still harder and need better time control to complete all 17 questions in 120 minutes (2 Hours).

For the CKA Exam, a score of 66% or above must be earned to pass. And I Scored 75% not bad in first attempt 🙂

Kubectl Cheat Sheet

It’s highly recommended to go through all the commands at least once before the exam, it would help you to become more familiar of some frequent-use command and be easier to find them during the exam. https://kubernetes.io/docs/reference/kubectl/cheatsheet

Best part is that you can access this during the exam to refer and you can copy the YAML format in the exam – https://kubernetes.io/docs/home/  

Results will be emailed to you within 36 hours from the time that the Exam was completed.  If you clear in first attempt is great achievement, if not you’ll have “Free Retake” another free chance to PASS it.

If you have any friend/colleague who has PASS this, do have conversation with him and discuss time management and some insider tips 🙂

I suggest whether you are working on Cloud Native aka Kubernetes (K8s) or not MUST do this, this is upcoming  and good to know or have updated yourself 🙂

Thank you and Hope this will help. Do reach out to me if need any help or wants to discuss further .. Cheers 🙂

 

  

 

 

 

 

 

 

 

 

 

 

 

 

VMware Tanzu Kubernetes Grid (TKG) Bootstrap – Part 3

Preview in new tab

In the second series VMware Tanzu Kubernetes Grid (TKG) – PART2. I  covered the basic of VMware Tanzu Portfolio, supported platform for Tanzu whether VMware Cloud  (On-Premises or VCPP Cloud) or Public cloud  (AWS or Azure) and supported  kubernetes versions with latest VMware Tanzu Kubernetes Grid 1.2 release.

Before  deep diving  into Tanzu Kubernetes Grid (TKG) Architecture, Let’s discuss about Bootstrap Environment

The bootstrap environment is typically a VM on which you run the Tanzu Kubernetes Grid CLI or VM from where you plan to deploy the Management or Workload Cluster/s. When you initiate Tanzu Kubernetes Grid instance, it bootstrap on local VM first and then transfer to the cloud infrastructure of your choice whether VMware cloud  (On-Premises or VCPP Cloud) or Public cloud  (AWS or Azure). After bootstrapping the management cluster, This VM can be  used to manage the Tanzu Kubernetes Grid instance.

The TKG CLI is used to initialize cluster, as well as to create, scale, upgrade, and delete Tanzu Kubernetes clusters. Basically Administrator or Developer needs to have TKG CLI to administrator or manage the kubernetes infrastructures or Applications.

When you initialize the TKG cluster, A cluster plan runs within bootstrap VM to provides a set of configurable values for deployment, for example, the number of control plane machines, worker machines, number of vCPUs, amount of memory, and other parameters you want for your TKG cluster. 

TKG Management Cluster

The Management Cluster is the first cluster that you deploy when you create a Tanzu Kubernetes Grid instance. This is Kubernetes cluster that performs the role of the primary management and operational center for the Tanzu Kubernetes Grid instance. This cluster is where Cluster API runs.

TKG Workload Cluster

Once you have deployed Management Cluster, You can initiate the deployment of Tanzu Kubernetes cluster/s from the management cluster by using the Tanzu Kubernetes Grid CLI. These clusters are also called workload clusters. These are clusters where PODs/Containers will run and will host your applications.

A single bootstrap environment can be used to bootstrap as many instances of Tanzu Kubernetes Grid as you want to have for different environments, e.g. Test, dev, Production running in different IaaS Providers – vSphere, AWS or Azure.

That’s all about bootstrap, will discuss more on architecture in VMware Tanzu Kubernetes Grid (TKG) Architecture – Part 4. Stay tuned for next part.

Hope this will be informative. Happy learning and happy sharing 🙂 

VMware Tanzu Kubernetes Grid (TKG) – PART2

In the first series GETTING STARTED WITH VMWARE TANZU PORTFOLIO – PART1. I tried to cover the basic of VMware Tanzu Portfolio, Basic of Cloud Native and what are the products VMware offers to customers under VMware Tanzu portfolio.

Let me recap again before moving to TKG acrchitecture, VMware provide following products for complete Kubernetes life cycle management (LCM):

  • VMware Tanzu Kubernetes Grid, informally known as TKG
  • VMware Tanzu Kubernetes Grid Integrated Edition, informally known as TKGI (Formerly known as Enterprise PKS) – Rebranded after VMware acquisition of Pivotal.
  • VMware Tanzu Kubernetes Grid Service, informally known as TKGS, This is the native Kubernetes in vsphere 7 (vSphere with Tanzu).
  • VMware Tanzu Mission Control, informally known as TMC.

These are complete Tanzu portfolio, which provides broad range of options and covers variety of use-cases for customers to have single platform to run traditional applications and Cloud Native or Modern Applications.

Tanzu Supported Platform

With Lateset release of VMware Tanzu Kubernetes Grid 1.2, customer can run on on-premises software defined data center (SDDC), and public cloud environments, including vSphere, Microsoft Azure, and Amazon EC2.

When we say vSphere it can run within your on-premises (Private Cloud) data center or vSphere base VMware certified cloud runs and managed by VMware Partners. To know more about VMware Certified Cloud or VCPP partners pls refer to VMware Certified Service Provider portal – https://www.vmware.com/partners/service-provider.html

Until VMware Tanzu Kubernetes Grid 1.1, it was only supported on vSphere (either Private cloud or VMware Certified Service Provider Cloud) and AWS. But with the relaese of VMware Tanzu Kubernetes Grid 1.2, now it also support for deployment on Microsoft Azure Public cloud.

With VMware Tanzu Kubernetes Grid 1.2 Release, customer can choose to run these  Kubernetes versions:

  • 1.19.1
  • 1.18.8
  • 1.17.11

For more details what’s new in VMware Tanzu Kubernetes Grid 1.2, Please refer release notes – https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/1.2/rn/VMware-Tanzu-Kubernetes-Grid-12-Release-Notes.html

Will discuss more on architecture in VMware Tanzu Kubernetes Grid (TKG) Bootstrap – Part 3. Stay tuned for next part.

Hope this will be informative. Please feel free to share if you wish to 🙂 

 

Getting Started with Vmware Tanzu Portfolio – Part1

Last few months I have been learning about Cloud Native Applications and how VMware Tanzu Portfolio helping thousands of customers around the world to build and run modern application on their existing private cloud running on VMware software defined data center (SDDC). 

Customers are looking for one stop shop to run Traditional Enterprise Apps and Cloud Native Apps on one platform, customer wants to limit CapEx and OpEx  to have single infrastructure which can support to run both modern and traditional applications, and want to focus more on application modernization and business development which helps them to generate more revenue.

This is where VMware Tanzu Portfolio helps to have one infrastructure where customer can run Traditional Enterprise Apps and Cloud Native Apps side by side. Which gives freedom and visibility to software developers and IT operations with the goal of delivering high-quality software that solves business challenges.

How do you build and run cloud native applications?

Whenever we talk or discuss about cloud native application, these are few important terms come into mind, let’s briefly discuss about these terms –

Microservices – Microservices is an architectural approach to developing an application. The microservices approach is the opposite of traditional monolithic software which consists of tightly integrated modules as a single unit. microservices have become popular with companies that need greater agility and scalability for their application.

Microservices characteristics and operations are :

  • A collection of small services where each service implements business capabilities
  • Runs in its own process and communicates via an HTTP API
  • Can be deployed, upgraded, scaled, and restarted independent of other services in the application

Containers – Container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another. Containers offer both efficiency and speed compared with standard virtual machines (VMs). Using operating-system-level virtualization, a single OS instance is dynamically divided among one or more isolated containers, each with a unique writable file system and resource quota. The low overhead of creating and destroying containers combined with the high packing density in a single VM makes containers an ideal compute vehicle for deploying individual microservices.

The most popular container is Docker, A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.

VMware Tanzu Portfolio

The goal of the VMware Tanzu portfolio is to provide a modern application platform, which helps customer to transform business, not just IT. VMware Tanzu can run on vSphere with Tanzu, vSphere, Public cloud and Edge environments. Edge refers to branch offices or remote locations outside of data center.

VMware Tanzu portfolio products provides complete end to end solutions for customers to RUN and MANAGE their cloud native applications.

Under Tanzu RUN, VMware provide following products for complete Kubernetes life cycle management (LCM):

  • VMware Tanzu Kubernetes Grid
  • VMware Tanzu Kubernetes Grid Integrated Edition (Formerly known as Enterprise PKS)
  • VMware vSphere with Tanzu

Under Tanzu Manage, VMware provides VMware Tanzu Mission Control, which Provides a centralized management platform for consistently operating and securing your Kubernetes infrastructure and modern applications running across multiple clouds. In nutshell, it provides unified managements for all the Kubernetes infrastructure, whether running on-prem, public cloud or running in multi public clouds environments.

What is Kubernetes and why do we need Kubernetes?

When running containers at scale in production – thousands of containers across your enterprise—things get complex and out of reach for developers or DevOps team to manage them efficiently. In such environments you must have unified and centralized ways to automate the deployment and management of all those containers. This is where we need orchestration engine for container.

Kubernetes, is the industry-standard for container management and provides orchestration engine for container, Kubernetes streamline container orchestration to avoid the complexities of interdependent system architectures. 

VMware Tanzu Kubernetes Grid is CNCF-certified, enterprise ready Kubernetes runtime solution to streamlines and simplify installation and Day 2 operations of Kubernetes across enterprise. It is tightly integrated with vSphere and can be extended to run with consistency across your public cloud and edge environments.

VMware Tanzu Kubernetes Grid is a multi cloud Kubernetes distribution that you can run on, VMware vSphere  and Amazon Web Services. TKG are tested, signed, and supported by VMware. VMware TKG Includes signed and supported versions of open-source applications to provide the networking, authentication, ingress control, and logging services that a production Kubernetes environment requires.

For more details pls visit VMware Tanzu documentation site – https://tanzu.vmware.com/ or https://docs.pivotal.io/

Will leave here in this post, In VMware Tanzu Kubernetes Grid (TKG) – PART2 will discuss more on TKG architecture.

Stay tunned, Keep learing and keep sharing 🙂

 

 

 

Deploying VMware ESXi 5.5. with vSphere Auto Deploy 5.5 – Part 2

We have discussed Install and Configure vCenter Server, Auto Deploy Server, TFTP Server and DHCP Server configuration in Deploying VMware ESXi 5.5. with vSphere Auto Deploy 5.5 – Part 1

Let’s discuss remaining parts here –

  • Download Offline Bundle for ESXi 5.5 with all other VIBs.
  • Install VMware PowerCLI 5.5.
  • Create Software Depot / Image Profile / Deploy Rule / Create Host profiles / Update Rules with Host Profile.

Download Offline Bundle for ESXi 5.5 with all other VIBs.

1. To download ESXi 5.5 Offline Bundle Go To https://my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/5_5

Offline22. Under Product type (Enterprise Plus) –> VMware ESXi 5.5.0 Update 2 and Click on Go to Downloads

Offline33. Under Product Downloads –> ESXi 5.5 Update 2 Offline Bundle –> Click on Download Now

Offline14. Enter My VMware Log In credentials and Click on Log In

Offline45. Tick the check box to Agree VMware End User Licence Agreement and Click Accept.

Offline56. It will start downloading ESXi 5.5 offline bundle Zip file and will take few minutes to download.

Offline67. Download others Agents / Drivers / VIBs as per your requirements to customize with bundle.

——————————————————————————————————

Now let’s Install VMware PowerCLI 5.5

1. Download VMware PowerCLI 5.5 from here https://my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsphere_with_operations_management/5_5?productId=352#drivers_tools

Offline72. Start the Installation by double Clicking VMware-PowerCLI-5.5.0-1295336.exe

Offline83. VMware vSphere PowerCLI installation will start and will give Security Warning for PowerShell Execution policy is not set to “RemoteSigned”

PCLI24. Open Windows PowerShell and Run Set-ExecutionPolicy remotesigned command to change the execution policy. And Click Continue to continue Installation.

PCLI35. On Welcome to the VMware vSphere PowerCLI Installation screen Click Next to continue.

PCLI46. Check radio button to Accept the License Agreement and Click Next to Continue.

PCLI57. Select vSphere PowerCLI program and change the Installation location (If required) and click Next to continue.

PCLI68. On Ready to Install the Program screen click Install to begin Installation.

PCLI79. This will take few minutes to install VMware vSphere PowerCLI on the machine.

PCLI810. On InstallShield Wizard Completed screen click Finish to exit the wizard.

PCLI911. Launch VMware vSphere PowerCLI by clicking VMware vSphere PowerCLI.

Offline912. We are all set with VMware vSphere PowerCLI Installation.

Offline10We have fulfilled all other requirements for Auto Deploy. Now will discuss how to Create Software Depot / Image Profile / Deploy Rule / Create Host profiles / Update Rules with Host Profile.

1.  Connect to vCenter server :- Connect-VIServer vc.dca.com.                                       It will ask for login Credential for vCenter Server. Provide User Name and                 Password click Ok to connect to vCenter Server.

AD1.12. As you can see connected to vCenter Server with provided User Name.

AD1.23. First Thing we need to do is create Software Depot, but before creating Software Depot we can check any existing Depot by command :- Get-EsxSoftwareDepot. 

AD14. To Create Software Depot use below command :-                                                                Add-EsxSoftwareDepot “C:\data\update-from-esxi5.5-5.5_update02-2068190.zip”   

AD25. Run again Get-EsxSoftwareDepot to see the Software Depot.

AD36. Next thing we need to do is create Image Profile.                                                                 New-EsxImageProfile -CloneProfile “ESXi-5.5.0-20140902001-stan*” -Name “Roshtestprofile”

AD47.  Use Get-EsxImageProfile to verify that Image Profile got created.

AD58. After Creating Image Profile we need to create DeplyRule                                             New-DeployRule -Name “PreHostProfile” -Item Roshtestprofile -Pattern “ipv4=192.168.174.206-192.168.174.220”                                                                 (Pattern can be IP Range, MAC Address, Make, etc.)

AD69. It has created Deploy Rule (PreHostProfile) for Pattern (IP Range) with Item (Image Profile) RoshtestProfile.

AD810. After Creating Deploy Rule we need to Add/Active Deploy Rule :-                                                    Add-DeployRule -DeployRule “PreHostProfile”

AD911. As you can see there is only one ESXi Host (esxi1.dca.com) is connected to this vCenter Server.

AD1012. We have created Rule with Pattern for IP Range, We’ll have to create Reservation for hosts with those IP Addresses. As you can see below i have created Virtual Machine (Auto_ESXi1) and reserved 192.168.174.210 IP address for host.

AD1113. Let’s Power ON the Virtual Machine Now.                                                                         (Note :- This is Stateless VM as have not allocated Hard Disk to VM)

AD1214. Host booted and get 192.168.174.210 IP Address from DHCP Server as per Reservation and trying to connect to TFTP Server to get Boot Image …

AD1315. Walla… Connected to Auto Deploy Server and loading Image into Memory….

AD1416. Installation is in Process…

AD1517. Once Installation finished host will be added to vCenter Server by Auto Deploy.

AD1718. Next thing we need to do to Create Host profile, Edit Host Profile and Update Deploy Rule to apply Host profile after deploying the ESXi host.

To create Host Profile Go To Home –> Management –> Host Profile

HP119. In Create Profile Wizard select Create Profile from existing Host and Click Next to continue..

HP220. Name the Host Profile and Click Next to continue ..

HP421. On the ready to complete the Profile Window Review and Click Finish to Create Host profile.

HP522. After creating Host Profile we need to edit the Profile to configure all the things want to deploy on hosts. (e.g. Syslog Server, Coredump collector, Stateless chashing , NTP settings, DNS configuration etc.)

HP6 HP7 HP823. Once profile is created and edited as per requirements. We need to Create New DeployRule with Host Profile and Cluster Name to Deploy host with Specific requirement and Add to specific Cluster. And Add/Active new created Deploy Rule.

AD1824. Again i have created one more VM with Name Auto_ESXi2 and reserved IP address 192.168.174.211. Now let’s reboot this VM to deploy with new created Rule.

AD2025. As you can see in below screen that Host Profile is being applied on the host.

AD2126. Once all done host has been added to mentioned Cluster DCA.

AD23That’s all. Hope this will help you all.

Cheers….Roshan Jha 🙂

Deploying VMware ESXi 5.5. with vSphere Auto Deploy 5.5 – Part 1

Auto Deploy allows rapid deployment and configuration of a large number of ESXi hosts. vSphere Auto deploy can be configured with one of the three modes:

  • Stateless
  • Stateless Caching
  • Stateful Install

Stateless :-  You Deploy ESXi using Auto Deploy are not installing ESXi onto a Local disk, or a SAN boot LUN. ESXi is directly loaded into memory on a host as it boots.

Stateless Caching :- You deploy ESXi using Auto Deploy just as with Stateless, but the Image is cached on the server’s local disk or SAN boot LUN. In the event that Auto Deploy infrastructure is not available, the hosts boots from a local cache of the Image.

Stateful Install :- You can provision a host with Auto Deploy and set up the host to store the image to disk. On subsequent boots, the host boots from disk. This process is similar to performing a scripted installation. With a scripted installation, the script provisions a host and the host then boots from disk. In this case, Auto Deploy provisions a host and the host then boots from disk.

Auto Deploy Requirements:-

1.  vCenter Server 5.5 (Install/Upgrade vCenter Server 5.5)

2. Install Auto Deploy Server 5.5.

3. Install TFTP server (SolarWinds).

4. Configure TFTP Server and Boot Loader Data.

5. Configure DHCP server with 66 and 67 Options.

6. Install VMware PowerCLI 5.5.

7. Download Offline Bundle 5.5 with all other VIBs

8. Create Software Depot / Image Profile / Deploy Rule / Create Host profiles / Update Rules

How to Install Auto Deploy server

You can install vSphere Auto Deploy on the same system as vCenter Server or on a separate Windows based system. If you are installing Auto Deploy on a system separate from vCenter Server, Specify the IP Address or Name of the vCenter Server with which this Auto Deploy server should register.

1. Launch the VMware vCenter Installer media and Select vSphere Auto Deploy and then click Install to start the installer.

AD12. Select the appropriate language and Click OK.

AD23. Installer will prepare setup process.

AD34. From the vSphere Auto Deploy installer Welcome Screen, Click Next to Continue.

AD45. Select Radio button to accept End User License Agreement and Click Next.

AD56. Select the vSphere Auto Deploy Installer and Repository Directory and Size of the Repository and Click Next to continue.

AD67. Provide vCenter Server details and Credentials to register Auto Deploy with vCenter Server and click Next to continue.

AD78. Select the default Auto Deploy Server and Management Port and Click Next.                   (Do not change unless there is conflicts with port numbers)

AD89. The Next screen allows to choose how the vSphere Auto Deploy Server will be identified on the network. It Will detect host name on which we are installing Auto Deploy choose default name name Click Next.

AD910. On Ready to Install screen click Install to begin the installation.

AD1011. Ignore the Security Warning and Click Finish to Complete the Installation.

AD1112. Once Installation Completed Connect to vCenter Server –> Home –> Administration –> Auto Deploy. See below screenshot.

AD1413. Click on Auto Deploy to open.

AD15We have completed Auto Deploy Installation, Now let’s Install and Configure TFTP server.

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

Install and Configure TFTP Server

There are so many TFTP server available but i am going to use here Solarwinds TFTP Server.

1. Download the SolarWinds TFTP server Software and Double Click SolarWindsTFTPServer.exe to launch the TFTP installer.

TFTP62. On the Open File – Security Warning page Click Run to start the installation.

TFTP13. On Welcome to the SolarWinds TFTP Server Setup screen and click Next to continue.

TFTP24. Click tick box to Accept End-User License Agreement and Click Next to Continue.

TFTP35. On Ready to Install screen click Install to begin the installation.

TFTP46. once Installation completed click Finish to exit setup wizard.

TFTP5

We have Installed TFTP server now Let’s configure TFTP Server.

1. Open the TFTP Server by going Start –> All Programs –> SolarWinds TFTP Server –> TFTP Server.

TFTP102. We need to download TFTP Boot ZIP from Auto Deploy Server. Let’s connect to vCenter Server and open Auto Deploy Server.

AD153. Click On Download TFTP Boot Zip and Save Deploy-TFTP.Zip to Local Drive.

TFTP83. Choose the location and Click Save to save on the specified location.

TFTP94. Open the Deploy-tftp.zip folder, Extract and copy all files inside this folder to TFTP Server Root location.

TFTP135. In my case TFTP Root is C:\TFTP-Root, So Paste copied files here.

PCLI246. Now we have to Configure C:\TFTP-Root as Root Directory for TFTP Server. So choose File –> Configure.

TFTP117. Under the Storage –> TFTP Server Root Directory –> Click Browse and choose C:\TFTP-Root and Click OK.

PCLI258. After Setting Up Root Directory Stop and Start the TFTP Server Service and Click OK to close the configuration window.

PCLI269. TFTP Server Configuration Completed and TFTP Server Service is Up and Running fine now.

PCLI27

We have installed and Configured Auto Deploy Server and TFTP Server, Now will Configure DHCP server ( Reservation and Configure Options 66 and 67 )

Configure DHCP Server

1. Open DHCP Server, Right Click on Reservation and choose New Reservation.

DHCP12. We need to specify MAC Address of the server for which reserving IP Address. And Also you can see have not assigned disk to this Virtual Machine (Stateless Host)

DHCP23. Provide Reservation Name same as Host Name, IP Address want to reserved for this host and MAC Address of the host.(Replace Colon (:) with Dash (-)) and Click Add to add reservation.

DHCP34. Now need to Configure Options for reservation with 66 (TFTP Server Name) and            67 (BootFile Name). Right Click Reservation and choose Configure Options.

DHCP45. Scroll Down to Options 66. Tick the check box 66 and Specify TFTP Server Name in Data Entry –> String value and Click Apply.

DHCP56.  Tick the check box 67 (Bootfile Name) and in the String Value enter Name of the Bootfile from TFTP Server Root Directory.

DHCP6

DHCP7

Done.

So far we have discussed Install and Configure vCenter Server, Auto Deploy Server, TFTP Server and DHCP Scope.

We’ll discuss Download Offline Bundle for ESXi 5.5 with all other VIBsInstall VMware PowerCLI 5.5, and Create Software Depot / Image Profile / Deploy Rule / Create Host profiles / Update Rules with Host Profile in the Deploying VMware ESXi 5.5. with vSphere Auto Deploy 5.5 – Part 2.

Click Here for Part 2 – Deploying VMware ESXi 5.5. with vSphere Auto Deploy 5.5

Thank You!

Roshan Jha 

vSphere Syslog Collector 5.5 – Install and Configure

Syslog Collector

Syslog is a way for network devices to send event messages to a logging server – usually known as a Syslog server. The Syslog protocol is supported by a wide range of devices and can be used to log different types of events. An ESXi host will by defaults save its log files locally. This is particularly important for hosts deployed without a persistent scratch Partition, Such as a Stateless host provisioned by Auto Deploy. Syslog Collector also addresses the issue of an Auto Deployed host not having a local disk.  With no local disk the log files are stored on a Ramdisk, which means each time the server boots the logs are lost.   Not having persistent logs can complicate troubleshooting.  Use the syslog collector to capture the ESXi host’s log on a network server.

Syslog Collector on VCSA

A Syslog Collector is bundled with the the vCenter Server Appliance (VCSA) and requires no extra setup. By default logs are saved in /var/log/remote/<HostName>. Just configure the hosts to send their logs to the Syslog collector.

Syslog Collector on a Windows Server

Syslog Collector can be installed on vCenter Server or on a standalone Windows Server.

1. From VMware vCenter Installer media choose vSphere Syslog Collector and Click Install to start the installation process.

SLS12. Select the appropriate language for the Syslog Collector and Click OK.

SLS23. Installer will prepare setup process to guide and install Syslog Collector.

SLS34. On the Welcome screen Click Next to continue.

SLS45. Select Radio button to accept End User License Agreement and Click Next.

SLS56. Select where to install the application and where to stored the logs and also Size of the log file before Rotation and Number of Logs to keep on the Syslog Collector Server. Unless you have specific requirements select default settings and Click Next.

SLS67. Setup Type screen allows to register the Syslog Collector instance with vCenter Server instance. Select VMware vCenter Server Installation and Click Next.

SLS78. On VMware vCenter Server Information screen provide the vCenter Server Name, Port, and Appropriate account credentials to Register Syslog Collector to vCenter Server and Click Next.

SLS8.19. Accept the default ports settings and Click Next.

SLS810. The Next screen allows to choose how the Syslog Collector will be identified on the networks and by the ESXi hosts. It Will detect host name on which we are installing Syslog collector choose default name and Click Next.

SLS911. On Ready to Install screen click Install to begin the installation.

SLS1012. On Installation Completed screen click Finish to complete the Installation.

SLS1613. Once Installation completed connect to vCenter Server –> Home –> Administration –> VMware Syslog Collector–> Double Click to open Syslog Collector.

SLS12

SLS13===========================================================

Configuring ESXi Hosts to Redirect to a Syslog Collector

There are several ways to Configure ESXi hosts to redirect logs to a Syslog Collector.

  • Advanced Configuration Options on the ESXi host
  • Via Host’s command Line
  • Host Profile

Configuring ESXi Hosts using the Advanced Configuration Options

1. Connect to vCenter Server using vSphere Client or Web Client –> Home –> Select Host and Clusters.

2. Select the ESXi Host –> Configuration –> Under Software Advanced Settings.

SLS143. Under Advanced Settings –> Syslog –> Global –> Syslog.global.loghost enter Syslog Collector host name and Click OK to complete the configuration.

SLS15===============================================================

Configuring ESXi Hosts using Host’s Command Line

1. Connect ESXi host using putty.

SLS172. Enter the Root credentials to log into to host.

SLS183. Review the existing Syslog Collector Configuration using below command –                                 esxcli system syslog config get

SLS194. If you do not remember the configuration parameters/options use below commands to get the help – esxcli system syslog config set –help

SLS205. To configure the remote log host server and enable syslog collector server on host use this command –

esxcli system syslog set –loghost=vum.dca.com –logdir-unique=true                    

esxcli system syslog reload

SLS216. Verify configuration using below command – esxcli system syslog config get

SLS22=============================================================

Configuring ESXi Hosts using Host Profile.

1. Edit the Host profile with below settings.

Advanced Configuration Option –> syslog.global.loghost –> Enter the syslog Collector host name and click OK. Apply this Host Profile on other hosts and compliant.

SLS23

Done. We are all set now 🙂

 

Cheers..Roshan Jha

Setting up the ESXi 5.5 Dump Collector

The ESXi Dump Collector is a centralized service that can receive and store Memory dumps from ESXi servers when they crashed unexpectedly. These Memory Dumps occurs when an ESXi hosts crashed with PSOD (Purple Screen of death). The Kernel grabs the contents of Memory and dumps them to nonvolatile disk storage before the server reboots. By default, a core dump is saved to the local disk.  In the case where there may not be a local disk the core dump will be saved to a ramdisk in memory, which is a problem because the core dumps will be lost when the host reboots.

To solve this vSphere 5.0 includes a new feature called the ESXi Dump Collector.  The Dump Collector enables you redirect ESXi host core dumps onto a network server.

The dump collector is included as part of the vCenter Server Appliance (VCSA) and requires no extra setup.

CDC1

How to Install ESXi Dump Collector on Windows.

1. To install the dump collector on Windows simply load the VMware vCenter installation media, launch autorun.exe and from the main install menu choose “vSphere ESXi Dump Collector”.

DC12. Select the appropriate language for ESXi Dump Collector and Click OK.

DC23. Installer will prepare setup process for ESXi Dump Collector.

DC34. On the Welcome screen Click Next to start installation process.

DC45. Select Radio button to accept End User License Agreement and click Next.

DC56. Select where to install the ESXi Dump Collector and Where to store the Dump (Repository Directory), If desired change the location and Repository Size and Click Next.

DC67. Setup Type screen allows to register the ESXi Dump Collector instance with vCenter Server instance. Select VMware vCenter Server Installation and Click Next.

DC78. On VMware vCenter Server Information screen provide the vCenter Server Name, Port, and Appropriate account credentials to Register ESXi Dump Collector to vCenter Server and Click Next.

DC89. Accept default port 6500 and Click Next.

DC910. The Next screen allows to choose how the ESXi Dump Collector will be identified on the networks and by the ESXi hosts. It Will detect host name on which we are installing Dump collector choose default name name Click Next.

DC1011. On Ready to Install screen click Install to begin the installation.

DC1112. On Installation Completed screen click Finish to complete the Installation.

DC1213. Once Installation completed connect to vCenter Server –> Home –> Administration –> VMware ESXi Dump Collector–> Double Click to open ESXi Dump Collector.

DC13You can see Dump Collector’s details and Port Number.

DC14=============================================================

Now we need to configure ESXi host to Redirect their Core Dumps

There are 2 methods to configure ESXi Hosts to redirects Core Dumps to ESXi Dump Collector server.

  • Using ESXCLI command-line Tools
  • Using Host Profile.

1. Log into ESXi host via SSH.

DC152. Enter the Root credentials to log into to host.

DC163. Review the existing Dump Collector Configuration using below command –                                 esxcli system coredump network get

DC174. If you do not remember the configuration parameters/options use below commands to get the help – esxcli system coredump network set –help

DC195. Use below command to configure the host’s dump redirection settings                             esxcli system coredump network set -v vmk0 -i 192.168.174.204 -o 6500

6. Turn On / enable Dump Collector using below command                                                     esxcli system coredump network set -e true

DC207. At the end verify Dump Collector service status with this command.                                             esxcli system coredump network check

DC21

Done!

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

Now will configure ESXi Dump Collector on hosts using Host Profile

1. Create Host Profile and Edit Host Profile with Below settings to enable and configuration Network Coredump Settings. Once done apply this Profile on the rest of Hosts to make complaint with hosts.

DC22

We are all set now.

 

Thank You!

Roshan Jha

Upgrade vCenter Server 4.1 to 5.5

Last night upgraded my home lab from vSphere 4.1 to vSphere 5.5.

The vCenter upgrade process is actually fairly simple, (all things considered). You basically just backup your existing database (SQL or Oracle), snapshot (or clone) your existing vCenter (if virtual), mount the ISO and start the upgrade process.

There are Prerequisites for vCenter Server 5.1 and Later (vCenter Single Sign-On and vCenter Inventory Service) which does not include in vCenter Server 5.0 and earlier so we need to install these 2 components before starting upgrade from 4.1 to 5.5.

up1You can install vCenter Single Sign-On, the vSphere Web Client, vCenter Inventory Service, and vCenter Server on the same host machine (as with vCenter Simple Install) or on different machines as Custom Install.

Let’s start to Install vCenter Single Sign-On

1. Download or Copy Installation Media VMware VMware-VIMSetup-all-5.5.0-2105955-20140901-update02 on the server where want to install vCenter Single Sign-On and Double-click autorun.exe to Start the Installer Media.

up22. From the VMware vCenter Installer, Select vCenter Single Sign-On and then Click Install button to start vCenter Single Sign-On installation.

up33. On Welcome vCenter Single Sign-On Setup screen click Next to continue..

SSO14. Select the tick box to Accept the Licence Agreement and Click NEXT..

SS)25. It will Auto check Prerequisites for vCenter Single Sign-On (e.g. Host Name, FQDN name of the Host, IP Address of the host, Machine is part of the Domain or not, and DNS is able to resolve the host name or Not). As you can see in below screen. If you want to add this Domain as identity Source in SSO check the tick box and Click NEXT..

SSO36. As this is First vCenter Server so choose Standalone vCenter Single Sign-On Server and click NEXT (For more details on all these please refer http://pubs.vmware.com/vsphere-55/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-55-upgrade-guide.pdf)

SSO47. Installation will create default SSO Domain. Choose a password for the SSO administrator – the “Master SSO Password” (administrator@vsphere.local).Enter Password and the click Next

SSO58. Choose an appropriate Site Name for this Installation and then Click NEXT..

SSO69. On the SSO Port settings page enter the port number and then Click NEXT..                   ( Unless there is conflict in the environment, recommend not to change default      Port Number)

SSO710. Change the Directory for installation if desired and Click NEXT..

SSO811. Finally, Review the installation options and click Install to start the installation.

SSO912. It will take few minutes to install. Once the installation is complete, Click Finish to close the Installer.

SSO10==========================================================

Installing vCenter Inventory Service

The second prerequisite for vCenter Server installation is the vCenter Inventory Service:

1. From the VMware vCenter Installer, Select vCenter Inventory Service and then click Install to start the installer.

IC12. Select the language for the installation and Click OK.

IC23. VMware vCenter Inventory Service installer will start..

IC34. From the vCenter Inventory Service installer Welcome Screen, Click Next to Continue..

IC45. Select the radio button to accept the End User License Agreement and Click Next.

IC56. Change the directory for installation if desired and click Next to continue.

IC67. Enter the vCenter Inventory Service local system name or select default and Click Next.

IC78. On the Configure Port settings page enter the port number and then Click NEXT..           ( Unless there is conflict in the environment, recommend not to change default      Port Number)

IC89. On the JVM Memory screen asks how big your vCenter Inventory will be once it’s fully configured. Select the desired option depending on your requirement and click Next.

IC910. On the vCenter Single Sign-On Information Screen enter the “Master Password” you choosed during SSO installation. Enter the Password (changed port number in the Lookup Service URL if you changed in SSO installation) and click Next to Continue..

IC1011. Because this is the first installation of vCenter Server, So default security certificates need to be accepted. These can be changed to “self-Signed” at a later time. Click Yes to accept and Click Install Certificates to install default certificates.

IC11

 

IC1212. Finally Click Install to commence the Installation and start the services.

IC1313. It will take few minutes to install and register with SSO.

IC1414. Once the installation is complete, Click Finish to Close the installer.

IC15=============================================================

 Installing vCenter Server

We have installed both prerequisites for vCenter Server now ready to upgrade vCenter Server 4.1 to 5.5.

Logged on as Administrative user (Administrator or Service Account) to the computer that will run vCenter Server.

1. Start the vCenter Server installation process by selecting vCenter Server and then Click Install.

VC32. As you can see that minimum RAM required is 4GB and i was started installation on host with 2GB So got failed with NOT ENOUGH SYSTEM RAM. Increased RAM to 4 GB on this VM and restarted installation process.

VC23. Select the language for the installation and click OK.

VC44. Setup will Prepare the InstallSheild Wizard to guide through the setup process…

VC55. On the Welcome screen you can see that An earlier version of vCenter Server is already installed on this computer and will be upgraded to vCenter Server 5.5.warning message. Click Next to continue upgrade process.

VC66. Select the Radio Button to Accept End User License Agreement and click Next.

VC77. Enter vCenter Server license key or leave it blank to install in evaluation mode for 60 days trail click Next to continue.

VC88. At this point you must select whether to use SQL Server 2008 Express Edition or a Separate Database server. I am using embedded database for my Home lab.

UP49. You will get Database Upgrade Warning choose as per your requirement and click Next.

VC1110.  By default the vCenter Server service use Windows Local System Account, if you are using another administrative user service account, provide the credentials and click Next to continue.

VC1311. On the vCenter Agent Upgrade screen choose how do you want to upgrade vCenter Agent on connected ESXi Host and Click Next.

VC1212. The next screen provides the option to change the default TCP and UDP ports on which vCenter server communicates. (Unless there is conflict in the environment, recommend not to change default Port Numbers)

VC1413. On the JVM Memory screen asks how big your vCenter Server will be once it’s fully configured. Select the desired option depending on your requirement and click Next.

VC1514. On the vCenter Single Sign-On Information Screen enter the “Master Password” you choosed during SSO installation. Enter the Password (changed port number in the Lookup Service URL if you changed in SSO installation) and click Next to Continue..

VC1615. Click Yes to accept Certificates and continue.

VC1716. Change the Inventory service address and Port if required and Click Next to continue.

VC1817. As we are upgrading the earlier version so can not change installation directory Click next to accept the location and continue.

VC1918. On the Ready to Install screen Click Install to start the Installation Process ( If you want to Participate in Customer Experience Improvement Program Tick the Enable Data Collection Box – by enabling this we are agreeing to send technical data weekly to VMware)

VC2019. As you can see on Installing VMware vCenter Server Screen it will take 15-20 minutes (depending on how big your environment is) to complete the upgrade.

VC2120. It is being installed as per options/features selected..

VC2221. Once Installation completed click Finish to close the Wizard.

VC23===============================================================

Installing vSphere Web Client

There are 2 different clients that can be used to administer a vCenter Server.

  • vSphere C# Client
  • vSphere Web Client

From vSphere 5.1 onward, VMware stated that it was no longer adding features to the .NET vSphere client: only the vSphere Web Client would gain new feature capabilities.

Any few features that are part of the vSphere 5.5 release are not available from the vSphere Client.

1. From the VMware vCenter Installer, Select vSphere Web Client and then Click Install to start process.

WC12. Select the appropriate language and click OK.

WC23. Installer will prepare the setup process..

WC34. On the Welcome screen click Next to continue.

WC45. Select radio button to accept End User License Agreement and click Next to continue.

WC56. Change the Installation Directory if required and Click Next to continue.

WC67. The next screen provides the option to change or accept the default ports for HTTP and HTTPS on which vSphere Web Client will communicate. (Unless there is conflict in the environment, recommend not to change default Port Numbers)

WC78. On the vCenter Single Sign-On Information Screen enter the “Master Password” you choosed during SSO installation. Enter the Password (changed port number in the Lookup Service URL if you changed in SSO installation) and click Next to Continue..

WC89. Click Yes to accept the certificate.

WC910. On the Ready to Install screen click Install to start the installation.

WC1011. It will take few minutes to install.

WC1112. Once Installation completed click Finish to exit the Wizard.

WC12Done!

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