The upgrade contains the following set of conflicting vibs cisco bootbank cisco vem

Whilst attempting to upgrade a series of VMware ESXi hosts i ran into a small issues with regards to the VIB version installed. Below is our scenario

VMware vSphere ESXi 5.0 upgrading to ESXi 6.0

Cisco Nexus 1010v VDS

The error i was receiving was:

‘the upgrade contains the following set of conflicting vibs cisco bootbank cisco vem’

Capture

Below is the process i followed to rectify this

SSH to the VMware ESXi host

vem status

1

vem stop

2

verify the vem pid has correctly stopped

lsof | grep cisco

lsof grep cisco

if process is still running use the kill-9 switch against the PID

identify the VEM name

esxcli software vib list | grep cisco

3

Put host into maintenance mode

esxcli software remove cisco-vem-v173-esx

4

Now the upgrade should complete as planned

Caveat: information presented in this how to guide is as is,  myself or my employer hold no responsibility to the guaranteed success of this guide

 

 

Installation of Veeam Availability Console 2.0

I’ve been privileged enough to get my hands on the RC version of Veeam Availability Console, or VAC as its more commonly known. The build number of this version is  2.0.1.983.

What is Veeam Availability Console?

VAC is the new iteration of Veeam Managed Backup Portal which is available to Veeam Certified Service Providers. VAC provides the following features:

  • Allows VCSP’s and Enterprise customers to deploy, mange and report on their BaaS or DRaaS customers utilising Veeam Cloud Connect
  • Provides the ability to deploy  Veeam Agents across multiple physical, virtual or cloud platforms
  • Supports multi-tenancy to provide managed customers with unique dashboards and reports of the backup or replication jobs

How to install Veeam Availability Console?

1

Initial Setup

2

.NET Framework 4.5.2 is required for this installation

3

Reboot after .NET Framework Installation

4

Accept the EULA

5

Install License File

6

Installation Components

7

Installation pre-reqs

8

Installation of missing pre-reqs

9

Completion of pre-reqs

10

Credentials for local windows service

11

Confirmation on ports required. These can be customised to suit your environment

12

Installation of SQL 2012

13

Installation of components

14

Installation of components

15

Installation complete

16

 

Next i will follow up with a post on configuration of Veeam Availability Console

NetApp FAS2650 node panic – ONTAP 9.1

After installing a new NetApp FAS2650 recently, a bug was observed which was causing one of the nodes to panic, and restart to the LOADER A prompt. After engaging with NetApp support, the following bug was found

A PCI NMI error triggers from QLogic 16Gb FC or 10 GbE Converged Network Adapter
(CNA) ports on some storage systems, such as FAS8200, FAS2650, FAS2620,
AFF A300, or AFF A200. The issue might continue to reoccur several times. This
issue only occurs when the port pair is configured in CNA mode.
An example of an error message is displayed, as follows:
PANIC : PCI Error NMI from device(s):RPT(0,3,3):QLogic FC/10GbE CNA on
Controller.

http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1026931

To resolve this, the following workaround is available:

Use the service processor to perform a system power cycle on the affected controller.

Reconfigure all unused CNA port pairs to Fibre Channel (FC) mode. Run the below commands from the Service Processor, commands below:

  1. ucadmin show –node “Affected Node” –adapter *
  2. ucadmin modify -node * -adapter * -mode fc -type target

You will need to make sure all CNA adapters are changed to fc to resolve the issue. Example below:

Before example:

*> ucadmin show

Current  Current    Pending  Pending    Admin

Adapter  Mode     Type       Mode     Type       Status

——-  ——-  ———  ——-  ———  ——-

0c     fc       target     –        –          offline

0d     fc       target     –        –          offline

0e     cna      target     fc       –          offline

0f     cna      target     fc       –          offline

Example 2/:

*> ucadmin modify -m fc -t target 0f

ucadmin modify: Mode on adapter 0f and also adapter 0e will be changed to fc.

Do you want to continue (y/n)? y

*> ucadmin show

Current  Current    Pending  Pending    Admin

Adapter  Mode     Type       Mode     Type       Status

——-  ——-  ———  ——-  ———  ——-

0c     fc       target     –        –          offline

0d     fc       target     –        –          offline

0e     cna      target     fc       –          offline

0f     cna      target     fc       –          offline

After Modify command is used

::> ucadmin show

Current  Current    Pending  Pending    Admin

Node          Adapter  Mode     Type       Mode     Type       Status

————  ——-  ——-  ———  ——-  ———  ———–

Node01            0c       fc       target     –        –          online

Node01            0d       fc       target     –        –          online

Node01            0e       fc       target     –        –          online

Node01            0f       fc       target     –        –          offline

 

Caveat: information presented in this how to guide is as is,  myself or my employer hold no responsibility to the guaranteed success of this guide

 

Upgrading VMware ESXi whilst using Nexus 1010v VDS

Recently i went through a process of upgrading a VMware environment that utilised the Nexus 1010v Virtual Distributed Switches.

The automatic upgrade that can be performed from the 1010v failed due to an issue on the VMware ESXi hosts. This was troubleshooted and identified as a stuck services on the VEM. The following process was completed to resolve the issue

It is advised to run this process whilst no virtual machines are located on the ESXi host

From ESXi Shell:

vem status -v

vem status -v

This command will identify the running version and status of the VEM package

To stop the VEM service

vem stop

Identify the process id of the VEM

lsof | grep Cisco

lsof grep cisco

Document the version and process ID. In this example we are using v173 and process id is 5516

Now kill the process:

kill -9 5516

Now install the upload the new vib to the ESXi host. We are using /var/log as our location

esxcli software vib install -v /var/log/vib_version.vib

Now check the status

vem status -v

Ensure this picks up the new version

Now from the Cisco NEXUS 1010v you should see the hosts logging in with the correct VEM version

 

Caveat: information presented in this how to guide is as is,  myself or my employer hold no responsibility to the guaranteed success of this guide

 

Veeam – Free Cloud Services

You may have recently seen that Veeam have been advertising a huge $200 million giveaway.  This promotion is to help Veeam customers leverage cloud resources from service providers for free! Each Veeam customer is now entitled to $1000 of free cloud resources, or £640 in the UK.

So how do you get your hands your $1000 worth of free services?

First Step, head to  https://go.veeam.com/promo-free-cloud-services

cloud_services_landing.PNG

Fill in your details using the same email address that your Veeam licenses are associated with.

Veeam will now check your details and provide you with a unique code.

Next choose your Cloud Service Provider. Head to https://www.veeam.com/find-a-veeam-cloud-provider.html to find your preferred service provider. Please note you can also contact Enquiries@tctg.co.uk to receive these services

service_provider_landing.PNG

Now your chosen Cloud Service Provider will contact you with the details to set you up, and you’re good to go!

Veeam Agent for Windows Workstation – Backup Direct to Cloud Connect

Veeam Agent for Windows 2.0 is currently available for public beta, with general release just round the corner. If you have been using Veeam, you will be familiar with the strategy change Veeam have been working on in the last 18 months; providing the ability to backup physical devices. Starting with Endpoint Backup, Veeam have been working on delivering agent based backups for both Windows and Linux devices.

Today i am going to be talking about the Veeam Agent for Windows(VAW), more specifically the ability to backup direct to Veeam Cloud Connect. Veeam Cloud Connect is a great feature which allows customer backup direct to service providers over the net. (For more information take a look at:THIS)

Veeam Agent for Windows will come in three license editions, for the purpose of this exercise i will be working with the ‘Workstation’ variant. For reference, here’s is the edition matrix alongside the respective features.

veeam agent matrix

Installing VAW is pretty simple, after some Next > Next > Finish we have the product installed, and the control panel available.

If you’ve been using Veeam Endpoint Backup, the VAW control panel will look familiar. Here we will ‘Configure Backup’

vaw_blog_01

From the Configure Backup pane, we have three options. Entire computer will take a bare-metal backup the machine entirely. Volume level backup will allow you to take block based back up individual volumes, and finally file level backup will give you an explorer view of your machine.

vaw_blog_02

For the purpose of this article, we will go ahead and use file level backup and identify a folder structure to backup. In this case my downloads folder within my profile (for reference i’m not using roaming profiles and carting around 42GB of downloads within my profile)

vaw_blog_03

Next up we choose a destination. Local storage will allow you to backup to a locally attached device, for example external USB drive. Shared folder will allow you to connect to a remote share. Veeam backup repository will connect to your internal VBR and store backups in the same locations as your production virtual machines. Veeam Cloud Connect Repository will connect direct to our service provider

vaw_blog_04

We’re going to go ahead and chose the Veeam Cloud Connect Repository. Now insert the URL and port to connect to your preferred service provider. In this instance I am using our own Cloud Connect infrastructure

vaw_blog_05

Next verify this will verify the service providers SSL certificate, and now we can insert credentials that have been provided

vaw_blog_06

Your repository name, quota and free space will now populate. We also have the ability to choose how many retention points we require

vaw_blog_07

For the purpose of this article, local backup cache will remain disabled. This feature will create a cache on your local device in case the connection to your service provide fails. Once the connection has been re-established, the contents of the cache will be copied to your service provider.

vaw_blog_08

Schedule, pretty self explanatory. I will be backing up after I lock my machine

vaw_blog_09

Confirm, and run now. My backup is now in progress

vaw_blog_11