Month: July 2015

Problems logging into newly created vCloud Air virtual machine.

Posted on Updated on

Have you created a virtual machine but are having problems logging in?

If you visit my last post on virtual machine creation in vCloud Air , you will see that there were no options to preselect usernames and passwords for the vm.

How do we logon in??

007-01

To resolve this we are going to have to go through a few steps.

Go back to the vCloud Air portal and power off the machine.

In this image I’m waiting for the vm to go down.

007-02

Once the vm is off,

Select the virtual machine,

Then in the actions drop down box choose: “Manage in vCloud Director”

007-03

A new window will pop up.

In this windows, on the upper left corner click “My cloud”

007-04

Now the view changes.

Click vms and find your virtual machine.

007-05

Right click your virtual machine and select properties

007-06

Select the “Guest OS customization tab”

You should see the auto generated password for your vm

007-07

Now hit cancel and go back and power on your vm

Then open the console. (right click the vm to pop out the console)

007-08

007-09

Now you should be able to logon and change your password.

007-10

Creating a virtual machine on vCloud Air

Posted on Updated on

Objective here is to create a new virtual machine in vCloud Air.

As you can see I have no virtual machines in my Virtual Data Center

Click on “create your first virtual machine”

006-01

Several default options to choose appear.

These are a handful of default options which incluse (as of this posting)

  • CentOS 6.3 (32/64)
  • CentOS 6.4 (32/64)
  • Ubuntu Server 12.04 (32/64)
  • Windows 2008R2 Standard (64)
  • Windows 2012 Standard (64)
  • Windows 2012R2 Standard(64)

Of course you can upload your own options but at the moment we will chose one of the defaults:

I’m choosing Ubuntu server 64.

006-02

Now customization options will appear.

Here you can name your vm, and allocate resources,

The cost per hour is generated as you play around with the options.

The more resources you consume, the greater the charge.

006-03

Now you see the vm being created, and the status will circle.

Still waiting on the status to update.

006-04

Once the vm is ready the status will show that its powered off

I chose to leave it powered off at first

The option to start powered on was also there.

006-05

Check the box next to the vm and power it on

You could also select the drop down and power it on or just the nice big button above.

006-06

Once the vm is on the status changes.

006-07

To view the console of our newly powered on vm

  • Select the vm,
  • Select the actions drop down
  • Choose “open in console”

006-08

Now the Console pops out and we can see the console and use the vm.

The buttons on the upper right are for

  • sending control alt del
  • going full screen

006-09

if you just created your vm you may have problems logging on.

See the next post for updates

Failover using Vmware Site Replication Manager (SRM) 5.5 And Dell Equallogic Storage Replication Adapter (SRA )

Posted on Updated on

Datacenter Site A:

There is a problem where we know we have power outages coming or we have one currently:

In this example: volumesiteA is volume with vms that needs to be failed over to recovery site B.

005-01

Recovery to start actual failover to Datacenter Site B:

A warning will pop up:

The difference between planned migration and disaster recovery is that if there are errors the recovery will stop if its planned.

In a true DR situation where site A is down use forced recovery.

005-02

005-03

One we hit start the recovery begins.

005-04

On the Equallogic side you can see that the volume status is set to offline

005-05

On recovery site B you will see a new volume appear

005-06

Once recovery is complete you can test your migrated servers

005-07

005-08

If we go back to the failed over datastore on site B, we will see

The volume is not replicated

005-09

You may get “amount of in-use snapshot reserve exceeds the warning limit”

005-10

Go over to the snapshot windows and delete some snapshots or increase space dedicated to snapshots

005-11

If we look at the volume on site A

We will see that the volume is still has a replication job to site B, though it will fail (notice the cancel)

005-12