RP4VM – iSCSI Configuration to Support ESXi Splitter to vRPA Communication

Each ESXi Host in a vSphere cluster hosting the RP4VM vRPA’s (virtual appliances running on ESXi hosts) require the iSCSI channel to allow communication between the ESXi hosts kernel embedded I/O splitter and the vRPA’s, utilizing an iSCSI software adapter running on the ESXi hosts. Thus a software iSCSI adapter and associated VMkernel ports need to be configured on every ESXi node hosting the RP4VM vRPA’s.

This post provides an example of the iSCSI configuration required when using a VMware vSphere distributed switch (VDS). This example displays how to configure the iSCSI settings required for RP4VM via the vSphere web client.

The below steps provide an example on how to create additional port groups on a VDS, create the VMkernel adapters, add the software iSCSI adapter and bind the VMkernel Port Groups to the ESXi iSCSI Adapter along with associated config such as MTU and uplink order.

Note: An upcoming release of RP4VM 5.X introduces a new TCP/IP based communication path for the splitter, which will eliminate the need to configure the iSCSI based software initiator (More on this later).

RP4VMiSCSIdvs0a Continue reading

EMC RecoverPoint for VMs ESXi Splitter Installation

The following steps detail the installation of the ‘EMC RecoverPoint for VMs’ Splitter VIB on ESXi hosts. The requirement is to Install the ‘RP for VMs’ splitter on each ESXi server hosting VMs that require RP protection. The recommendation is to allow 800MB of RAM per ESXi host for the RP4VM Splitter.

Note:

  • The use of VUM is not supported for the splitter install at present.
  • vRPAs must be deployed on an ESXi with a splitter.

Begin by ensuring that SSH is enabled on the ESXi hosts where the splitter will be installed in order to issue the ESXCLI cmds (After completing the splitter install then SSH may be disabled).
pp_remove_3

Using WINSCP to securely copy over the RP splitter VIB to /tmp:
RP4VM2
RP4VM3

Change directory to /tmp where the VIB has been copied to and ensure the VIB is present:
cd /tmp
ls -l
du -ah

RP4VM-4

RP4VM-5

Run the installation of the VIB file on ESXi host:
# esxcli software vib install –v kdriver_RPESX-00.4.3.0.1.0.c.122_md5_d4e7e95a89e74c7ca17be8f4344830b8.vib –no-sig-check

RP4VM-6

Retrieve the names of the packages installed on the vSphere host confirming the splitter installation:
# esxcli software vib list
# esxcli software vib list | grep RP
RP4VM-7
Note: VIB stands for vSphere Installation Bundle

 

PowerCLI Script:

##########################################################

# RP4VM Splitter Install Version 1.0

# Date: 2016-04-08

# Created by: David Ring

##########################################################

############# vCenter Connectivity Details ################

Write-Host “Please enter the vCenter Host IP Address:” -ForegroundColor Yellow -NoNewline

$VMHost = Read-Host

Write-Host “Please enter the vCenter Username:” -ForegroundColor Yellow -NoNewline

$User = Read-Host

Write-Host “Please enter the vCenter Password:” -ForegroundColor Yellow -NoNewline

$Pass = Read-Host

Connect-VIServer -Server $VMHost -User $User -Password $Pass

####### Please enter the Cluster to install RP4VM Splitter #######

Write-Host “Clusters Associated with this vCenter:” -ForegroundColor Green

$VMcluster = ‘*’

ForEach ($VMcluster in (Get-Cluster -name $VMcluster)| sort)

{

Write-Host $VMcluster

}

Write-Host “Please enter the Cluster to install RP4VM Splitter:” -ForegroundColor Yellow -NoNewline

$VMcluster = Read-Host

################# Enabling SSH ######################

Write-Host “Enabling SSH on all hosts in your specified cluster:” -ForegroundColor Green

Get-Cluster $VMcluster | Get-VMHost | ForEach {Start-VMHostService -HostService ($_ | Get-VMHostService | Where {$_.Key -eq “TSM-SSH”})}

############ Please enter the VMFS datastore #############

Write-Host “From the list provided – Please enter the VMFS datastore where the VIB has been uploaded to:” -ForegroundColor Green

$Datastore = ‘*’

ForEach ($Datastore in (Get-Datastore -name $Datastore)| sort)

{

Write-Host $Datastore

}

Write-Host “Please enter the VMFS datastore Name:” -ForegroundColor Yellow -NoNewline

$Datastore = Read-Host

########## Please enter the VIB name ##########

Write-Host “Please enter the VIB name e.g. kdriver_RPESX-00.4.3.0.1.0.c.122_md5_d4e7e95a89e74c7ca17be8f4344830b8.vib:” -ForegroundColor Yellow -NoNewline

$VIB = Read-Host

########## Installing RP4VM Splitter ###########

Write-Host “Installing RP4VM Splitter” -ForegroundColor Green

$hosts = Get-Cluster $VMcluster | Get-VMHost

foreach($vihost in $hosts)

{

$esxcli = get-vmhost $vihost | Get-EsxCli

$esxcli.software.vib.install($null,$false,$false,$false,$false,$true,$null,$null,”/vmfs/volumes/$Datastore/$VIB”)

}

###### Confirm Splitter Installed Successfully #######

Write-Host “Confirm Splitter Installed Successfully” -ForegroundColor Green

$hosts = Get-Cluster $VMcluster | Get-VMHost

forEach ($vihost in $hosts)

{

$esxcli = get-vmhost $vihost | Get-EsxCli

$esxcli.software.vib.list() | Where { $_.Name -like “*RP*”} | Select @{N=”VMHost”;E={$ESXCLI.VMHost}}, Name, Version

}

####### Enter each host in maintenance mode and reboot (use with caution!) #######

Write-Host “Enter all Cluster hosts in maintenance mode and reboot (use with caution!)” -ForegroundColor Yellow -NoNewline

Write-Host ” Y/N:” -ForegroundColor Red -NoNewline

$Reboot = Read-Host

if ($Reboot -eq “y”) {

$hosts = Get-Cluster $VMcluster | Get-VMHost

forEach ($vihost in $hosts)

{

$esxcli = get-vmhost $vihost | Get-EsxCli

$esxcli.system.maintenanceMode.set($true)

$esxcli.system.shutdown.reboot(10,”RP4VM Splitter”)

}

}

######## Disabling SSH #########

Write-Host “Disabling SSH” -ForegroundColor Green

Get-Cluster $VMcluster | Get-VMHost | ForEach {Stop-VMHostService -HostService ($_ | Get-VMHostService | Where {$_.Key -eq “TSM-SSH”}) -Confirm:$FALSE}

######### RP4VM INSTALLATION COMPLETE #########

Write-Host “RP4VM INSTALLATION COMPLETE” -ForegroundColor Green

EMC VNX – RecoverPoint Enabler Installation

Installing the RecoverPoint Enabler using NAVICLI:

Check the list of all ENABLERS currently installed on the VNX:
naviseccli -h SP_IP ndu -list

A series of rule checks need to be performed in advance and correct any rule failures before proceeding:
naviseccli -h SP_IP ndu -runrules -listrules

Your configuration will run the following rules
===============================================
Host Connectivity
Redundant SPs
No Thin Provisioning Transitions
Version Compatibility
No Active Replication I/O
Acceptable Processor Utilization
Statistics Logging Disabled
No Transitions
All Packages Committed
Special Conditions
No Trespassed LUNs
No System Faults
No Interrupted Operations
No Incompatible Operations
FAST Cache Status
No Un-owned LUNs

Run through the Pre-installation rules to ensure the success of this software upgrade:
naviseccli -h 10.73.113.40 ndu -runrules -verbose

A common result is a warning for tresspassed LUNs:
RULE NAME: No Trespassed LUNs
RULE STATUS: Rule has warning.
RULE DESCRIPTION: This rule checks for trespassed LUNs on the storage system.
A total of 1 trespassed LUNs were found.
RULE INSTRUCTION: If these LUNs are not trespassed back, connectivity will be disrupted.

To remediate this rule failure and change the Current Owner you will need to execute a trespass command on the LUN using navicli or by right clicking on the LUN in Unisphere and click the trespass option:
naviseccli -h SP_IP trespass lun 1
If changing on multiple LUNs then running the trespass mine command from the SP will trespass all the LUNs that the SP has DEFAULT ownership of. For example to trespass LUNs with Default Ownership of ‘SP B’ but which are currently owned by ‘SP A’:
naviseccli -h SPB_IP trespass mine

Statistics Logging Disabled : Rule failed.
naviseccli -h SP_IP setstats -off

Confirm all rule checks for RPSplitterEnabler are met:
naviseccli -h SP_IP ndu -runrules c:\VNX\Enablers\RPSplitterEnabler-01.01.5.002.ena -verbose

Running install rules...
===============================================
Version Compatibility : Rule passed.
Redundant SPs : Rule passed.
Acceptable Processor Utilization : Rule passed.
No Trespassed LUNs : Rule passed.
No Transitions : Rule passed.
No System Faults : Rule passed.
All Packages Committed : Rule passed.
Special Conditions : Rule passed.
Statistics Logging Disabled : Rule passed.
Host Connectivity : Rule passed.
No Un-owned LUNs : Rule passed.
No Active Replication I/O : Rule passed.
No Thin Provisioning Transitions : Rule passed.
No Incompatible Operations : Rule passed.
No Interrupted Operations : Rule passed.
FAST Cache Status : Rule passed.

Install the RPSplitterEnabler:
naviseccli -h SP_IP ndu -install “c:\VNX Enablers\RPSplitterEnabler-01.01.5.002.ena” -delay 360 -force -gen -verbose

Name of the software package: -RecoverpointSplitter
Already Installed Revision NO
Installable YES
Disruptive upgrade: NO
NDU Delay: 360 secs

Monitoring the progress of the installation:
naviseccli -h SP_IP ndu -status
Is Completed: NO
Status: Activating software on primary SP
Operation: Install

naviseccli -h SP_IP ndu -status
Is Completed: NO
Status: Completing install on secondary SP
Operation: Install

naviseccli -h SP_IP ndu -status
Is Completed: YES
Status: Operation completed successfully
Operation: Install

naviseccli -h SP_IP ndu -list -name -RPSplitterEnabler

Commit Required: NO
Revert Possible: NO
Active State: YES
Is installation completed: YES
Is this System Software: NO

Re-enable stats logging:
naviseccli -h SP_IP setstats -on

If uninstall required:
naviseccli -h SP_IP ndu -messner -uninstall -RPSplitterEnabler -delay 360
Uninstall operation will uninstall
-RPSplitterEnabler
from both SPs Set NDU delay with interval time of 360 secs.Do you still want to continue. (y/n)? y

Installing the RecoverPoint Enabler via Unisphere Service Manager (USM):

Enabler_Install_USM1

Enabler_Install_USM2

Enabler_Install_USM3

Enabler_Install_USM4

Enabler_Install_USM5

Enabler_Install_USM6

Enabler_Install_USM7

Enabler_Install_USM8

Enabler_Install_USM9

Enabler_Install_USM10

Enabler_Install_USM11

Enabler_Install_USM12

Enabler_Install_USM13

Enabler_Install_USM14