Upgrading Clustered vRLI Deployment

In this post I will walk through steps of upgrading a clustered vRLI deployment. Before preparing for upgrade, make sure to read VMware documentation for the supported upgrade path.

One very important consideration before you start upgrading vRLI:

Upgrading vRealize Log Insight must be done from the master node’s FQDN. Upgrading using the Integrated Load Balancer IP address is not supported.

To start vRLI upgrade, login to the web interface of master node and navigate to Administration > Cluster and click on Upgrade Cluster button. Read More

Configuring AD Authentication in vRealize Log Insight

vRealize Log Insight supports 3 Authentication methods:

  • Local authentication.
  • VMware Identity Manager authentication.
  • Active Directory authentication.

You can use more than one method in the same deployment and users then select the type of authentication to use at log in.

To AD authentication to vRLI, login to web interface and navigate to Administration > Authentication page

vrli-auth01

Switch to Active Directory tab and toggle the “Enable Active Directory support” button.

vrli-auth02

Specify your domain related details and hit Test Connection button to test whether vRLI is able to talk to AD or not. Hit Save button if test is successful.  Read More

Scaling Up Standalone vRealize Log Insight Deployment

vRealize log insight can be deployed as a standalone or as a clustered solution. In a clustered deployment the first node is the master node and the remaining nodes are termed as worker nodes. The process of scaling up is pretty straight forward and in this post I will walk through the steps of doing so.

Few things which you should consider before expanding a vRealize Log Insight deployment are:

  • vRealize Log Insight does not support WAN clustering (also called geo-clustering or remote clustering). All nodes in the cluster should be deployed in the same Layer 2 LAN. 
  • Configure a minimum of three nodes in a vRealize Log Insight cluster. 2 node cluster is not supported.
  • Verify that the versions of the vRealize Log Insight master and worker nodes are same. Do not add an older version vRealize Log Insight worker to a newer version vRealize Log Insight master node.
  • External load balancers are not supported for vRealize Log Insight clusters. You need to use the vRealize log insight integrated load balancer (ILB). 

Let’s jump into lab to see the process in action.

In this post I am not including deployment steps of my first vRLI instance as it’s a straightforward forward process. If you are still interested to see the deployment steps then you can follow this old post of mine. Read More

Distributed vRA Automated Upgrade via vRLCM

In this post I will walk through steps of upgrading a distributed vRA 7.4 environment to v7.5. This is continuation of my earlier post where I deployed vRA 7.4 via vRLCM.

Upgrade Prerequisites

This post assumes that you have met all the prerequisites of vRA upgrade mentioned in this document

Important: If you are doing upgrade in a distributed environment, then make sure you have disabled the secondary members of pool and all monitors removed for the pool members during the upgrade process. 

To upgrade a vRA deployment, login to vRLCM and navigate to Home > Environments and click on view details. Read More

Cancelling Request in vRealize Suite Lifecycle Manager via API

vRLCM is a great tool but the only shortcoming which is still there with v 2.0 is the ability to cancel any running task via GUI. I faced this situation when I was trying to add a remote collector node to an existing vROPS deployment and task kept running for more than 4 hours.

While searching on internet for how we can stop/cancel/delete a request in vRLCM, came across this thread on VMware Code website, where it was mentioned that it’s not possible from GUI and we need to use REST API.

Below steps shows how to use vRLCM API Read More

vRA Distributed Install using vRealize Suite Lifecycle Manger

In first post of this series, I talked briefly about what vRealize Suite Lifecycle Manager is and its capabilities. Also I covered the installation and initial configuration settings of the appliance.

In this post I will walk through steps of deploying vRA 7.4 distributed install in automated fashion using vRLCM.

Before trying vRLCM, I did a vRA distributed install manually because I wanted to understand the flow of distributed install. If you are new to his topic then I would suggest reading below posts before you can start using vRLCM to automate deployments: Read More

Installing & Configuring vRealize Suite Life Cycle Manager 2.0

vRealize Suite Life Cycle Manager 2.0 was released in September 2018 and with this release a lot of new features were added. Please refer to this post to learn What’s new in vRLCM 2.0.

What is vRealize Suite Lifecycle Manager?

vRealize Suite Lifecycle Manager automates install, configuration, upgrade, patch, configuration management, drift remediation and health from within a single pane of glass, and automates Day 0 to Day 2 operations of the entire vRealize Suite, enabling simplified operational experience for customers. Read More

vRA 7.4 Distributed Install: Part 4: vRA Distributed Install

In last post of this series , I talked about how to configure NSX based load balancer for vRA environment. In this post I will walk through vRA appliance deployment.

If you are not following along this series, then I recommend reading earlier posts of this series from below links:

1: Introduction & Reference Architecture

2: Lab Setup

3: Load Balancer Configuration

Download vRA 7.4 appliance and deploy 2 instances of vRA VM’s.

Once both the appliance boots up, connect to the vami of first appliance by typing https://<vra1-fqdn>:5480/ Read More

vRA 7.4 Distributed Install: Part 3: Load Balancer Configuration

In last post of this series, I talked about my lab setup. In this post I will walk through the load balancer configuration that needs to be in place for supporting the distributed install.

If you are not following along this series, then I recommend reading earlier posts of this series from below links:

1: Introduction & Reference Architecture

2: Lab Setup

Although it’s not mandatory to have the load balancer configured when kicking the distributed install, as we can configure it post vRA deployment, but it is recommended to configure this before attempting the install. Read More

vRA 7.4 Distributed Install: Part 2-Lab Setup

In last post of this series, I talked about high level overview of vRA distributed installation. In this post I will be discussing about my lab setup.

Management Cluster

In my management cluster I have vSphere 6.5 installed and vCenter is deployed with embedded psc. I have total of 5 hosts in my management cluster.

lab-1.PNG

Host Details:

lab-2.PNG

VM/Appliance Details:

  • 2x vRealize Automation 7.4 Appliances
  • 2x Windows Servers for IaaS Web
  • 2x Windows Servers for the Management Service (Active / Passive)
  • 2x Windows Servers for the DEMs/Agents

lab-4.PNG

Windows Template Specifications

I deployed each of the windows vm using a template which was configured as per below:

1: Static IP set and windows domain joined.  Read More

VRA 7.4 Distributed Install: Part 1-Introduction

vRA 7.x brought a lot of enhancements with it and one of the major enhancement was the simplicity of deploying the setup which was very complex till version 6.x. 

The second major enhancement was to cut the overall footprint of vRA. For VRA 6.x implementation, we needed at least 8 VA’s to form the core services (excluding the IaaS components). This limitation is no more with 7.x implementation.

Now a single pair of VRA VA’s forms the core services. In a distributed install, the load balanced VA’s delivers vRA’s framework services, Identity Manager, Database, vRO, and RabbitMQ. All these services are clustered and sits behind a single load balance VIP and a single SSL cert. Read More

Learning vRNI 3.9: Part 3:User Management in vRNI

In last post of this series we learnt how to change default retention period for events etc in vRNI. In this post we will learn how about user management.

If you are not following along this series, then I recommend reading earlier posts of this series from below links:

1: Adding Data Sources in vRNI

2: Changing Default Data Management Policy

Default installation of vRNI allows you to login with admin@local user and this user can add new users (local and LDAP) and configure memberships and other settings of existing users. In this post we will learn how to add a local and LDAP user to vRNI. Read More

Learning vRNI 3.9: Part 2:Changing Default Data Management Policy

By default the data retention policy in vRNI is one month. However if you have an enterprise license, then you can change this policy.  The data is divided into the following categories:

vrni-data retention

We can change the value of any category and can set it to maximum value specified in above table.

To change the default data retention policy, login to vRNI and navigate to Home > Settings > Data Management. 

Click on configure button to change the values.

vrni-dm-1

From the drop down menu, select the new value for each category which you want to change and hit submit button. Read More

Learning vRNI 3.9: Part 1:Adding Data Sources in vRNI

By default when vRNI 3.9 is installed, it starts in the NSX assessment mode and in this mode you will only see option to add vCenter server as data source.

vrni-ds-1

If you click on Add Data Source, the only option available to you is to add vCenter, Infoblox and Netflow Collector.

vrni-ds-2

In order to add different data sources like NSX Manager or Cisco devices, you need to change the evaluation license and then click on “Switch to Full Product Evaluation” button available in the bottom right corner of vRNI homepage. Read More

vRealize Automation 7.3-Simple Installation: Part 10: Catalog Management

In last post of this series we learnt how to create and design blueprints. This post will be focussed on catalog management. Once you have created blueprint items, next thing is to associate them with a service and defining the entitlements so that end-user can start requesting items from catalog to which they are entitled for.

If you have landed directly on this page by mistake, then I encourage you to read earlier posts of this series from below links:

1: vRA Lab Setup

2: Installing and Configuring NSX Read More