Thursday, November 13, 2014

SRM Logging

Recently we were asked to enable trivia logging for SRM to troubleshoot some issues we ran during test recovery

Following are various logging levels for SRM
  • Error
  • Warning
  • Info
  • Trivia
  • Verbose.

 To change the log level, locate the following section of vmware-dr.xml
Default Location is C\:Program Files\Vmware\VMware Site Recovery Manager\config\vmware-dr.xml

C:\Documents and Settings\All Users\Application Data\VMware\VMware Site Recovery Manager\Logs
vmware-dr
verbose
C:\Documents and Settings\All Users\Application Data\VMware\VMware Site Recovery Manager\DumpFiles


Change From: verbose To:trivia
When increasing the log level to trivia, increase the log retention policy as well. This can be achieved by adding the maxFileNum and maxFileSize tags between the <log></log> of the same vmware-dr.xml

Reference Documents 




SRM IP Customization Error

I came across the below mentioned issue for which I am working towards to resolve.
We are still having discussions whether we should be performing the work around  given
I thought of sharing and check whether we have other users who also have similar issues and get any feedback from the community

Setup

 VMware vCenter 5.1 Update 2
ESXi 5.1 Update 2
SRM 5.1 Update 2

 Issue

At the time of Test Failover VMs have faced an error “Error - Internal error: std::exception 'class Dr::Vix::SharedSecretNotPermitted' "Shared Secret is not permitted on this guest".” with IP Customization


Resolution/WorkAround

We were asked to modify following setting on all the VMs and it requires VM to be Powered Off and the value needs to be set to either 1 or true.

guest.commands.allowSharedSecretLogin


 Description

 All VIX clients, including SRM, need to have this parameter enabled so the client can do things inside the VM's OS like copying files over to that VM. For example, SRM generates the IP customization script on the fly and copies it together with the three other IP customization tools over to the VM. To do that SRM must open a VIX connection to the VM first (using the "SharedScretLogin" mechanism. That is, in a nutshell, how it works.

The error message we are getting indicates that SRM's VIX connection to the VM will not go through because "SharedScretyLogin" is not enabled for that VM somehow. SRM normally sets this parameter when it opens VIX connection to the VM for the purpose of IP customization. So that means that SRM, for some unknown reason, is not able to enable to set that flag on the fly. The suggestion to add that parameter manually into the VM config file is to do it on behalf of SRM. Then see if SRM is able to open the VIX connection and continue with the IP customization process on that VM.

Horizon View PowerShell Not Working

Last Year I wrote Power CLI Script for VMware View 5.1 to capture the Remote Session details for that particular point in time


We had team upgrading that to Horizon View 6.0 and suddenly we noticed that it was not working as expected. It was generating the empty file
Based on research we found that it was known behavior and followed instructions based on following KB Article which resolved the issue



Monday, November 10, 2014

ESXi Dump Partition

Recently we upgraded from ESXi 5.0 to 5.1 Update 2 and we got following alert that’s when we realized that we need to configure coredump server

Researching later we found that it  cannot be located on an iSCSI LUN accessed through the software iSCSI or dependent hardware iSCSI adapter and we were using Boot from SAN using Software iSCSI


Following KB Article disk recommendations for the disk/lun sizes where we understood it was not the default behavior in 5.0 where as it got changed 5.1


Now we will need to configure Network Core Dump Collector which is part of the package for vCenter 5.1 Update 2 and following KB Article details around the same



Monday, November 3, 2014

Accessing VMware vCenter Site Recovery Manager (SRM) GUI generates continuous and immediate log-in prompts to remote vCenter Server (2090370)


Symptoms
·    Accessing VMware vCenter Site Recovery Manager (SRM) GUI generates continuous and immediate log-in prompts to remote vCenter Server.
·    This issue occurs when SRM is deployed in two sites in an environment in which:

o The two vCenter Servers may or may not be in linked-mode.
o The C# VMware Infrastructure (VI) Client is used to access the SRM GUI.

Resolution

This is a known issue affecting SRM 5.0.x, 5.1.x and 5.5.x.

Notes: If you are running:
  • SRM 5.0.3, 5.1.x or 5.5.x, contact VMware technical support for assistance.
  • SRM 5.8, this issue does not occur as SRM GUI is now managed through the next generation web client (NGC).
To work around this issue, run the VI Client from outside of the vCenter Server machine.
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2090370&src=vmw_so_vex_mmakh_407


Supported host operating systems for VMware vCenter Server installation

This table lists the supported host operating systems for vCenter Server installation.

Windows Operating System
5.5 U2
5.5 U1
5.5
5.1 U2
5.1 U1
5.1
5.0 U3
5.0 U2
5.0 U1
5.0
4.1 U3
4.1 U2
4.0 U4
Microsoft Windows Server 2012 R2 64-bit
Yes
Yes
Yes
Microsoft Windows Server 2012 64-bit
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Microsoft Windows Server 2008 Service Pack 2 64-bit
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Microsoft Windows Server 2008 Service Pack 1 64-bit
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Microsoft Windows Server 2008 R2 Service Pack 1 64-bit
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Microsoft Windows Server 2008 R2 64-bit
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Microsoft Windows Server 2003 R2 Service Pack 2 64-bit
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Microsoft Windows Server 2003 R2 64-bit
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Microsoft Windows Server 2003 Service Pack 2 64-bit
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Microsoft Windows Server 2003 64-bit
Yes
Yes
Yes
Microsoft Windows Server 2003 32-bit
Yes
Microsoft Windows XP 64-bit
Yes
Yes
Microsoft Windows XP 32-bit
Yes



Wednesday, October 29, 2014

Upgrade vSphere Distributed Switch from 5.0 to 5.1

We recently upgraded our vCenter Server from 5.0 to 5.1 Update 2

As part of the activity we also need to upgrade our distributed switch from 5.0 to 5.1

As per VMware documentation is a non-disruptive operation i.e. hosts and virtual machines attached to the switch don’t experience any downtime


I wanted to test in a live environment during day time and guess and I just did it and didn't observe any issues. It hardly took 30 seconds






Saturday, October 18, 2014

ESXTop Plugin for vSphere Web Client

VMware Labs released ESXTop Plugin for vSphere Web Client

Plugin is an enhanced, plugin-version of ESXtop for the vSphere Web Client. The plugin displays ESX server stats in new and more powerful ways by tapping into the GUI capabilities of the Web Client.

Features

Separate tabs for CPU, memory, network and disk performance statistics
Flexible batch output
Flexible counter selection
Advanced data grid for displaying stats (sortable columns, expandable rows, etc.)
Configurable refresh rate
VM-only stats
Embedded tooltip for counter description



vSphere 5.8 Installation


We will be deploying the vSphere Replication Appliance from web client

Right Click on Hosts/Clusters and Select Deploy OVF Template


Select the OVF file from the local computer where you are accessing web client



By default its 4 vCPU and it has option for 2 vCPU




Nested ESXi Installation


Enable SSH to the Physical ESXi Host
Login using root
Execute following command
echo ‘vhv.allow = “true” ‘ >> /etc/vmware/config


Now we need to modify the security Settings for the Port Group which is going to be used for the virtual esxi and make Promiscuous Mode as "Accept"


Now we need to create the VM. We need to take care of following
Virtual Machine Version should be 8
Guest Operating System should be "Other (64- bit)"
CPUs should be 2 virtual sockets 2 cores per socket for ESXi 5.1 or above
RAM should be 4 GB
2 NIC for redundancy with E1000
HDD should be 1 GB or above
Once the VM is created then Right Click and go to Edit Settings --> Options and change the Guest Operating System. You should be able to VMware ESXi 5.X


Ensure CPUID Mask is set to Expose the NX/XD flag to guest


Mount the CD/DVD with ESXi Install and you should be able to boot with ESXi Installer once you Power ON




Thursday, October 16, 2014

SRM 5.8 Installation

 
 
 
Here we need to select the DNS which we created before for the DB Instance created in the SQL/DB Server
 
 
Login to Web Client and you will notice the Site Recovery in the Inventory
 

vCenter 5.5 Update 2 Installation

 
 
It requires minimum 10G free space
 
This is where you will select whether to use SQL Express of use existing database
We need to ensure the System DSN is created and point it to the database created in SQL/DB Server
 
 
We need to make sure the database connectivity is there else we can get similar errors which I got here
 
 
In my case as it pointed SQL Server Agent service was not running because it was pointing to Manual
 
 
 
By default only administrator@vsphere.local has access to vCenter which is the SSO account
We need to login and add the permission for accounts/users  you want to allow access