Firefox: CONSOLE ACCESS TO VCLOUD DIRECTOR 8.20 VIA WEBMKS

In my previous post about Google Chrome I already described what you might need to do with your certificates to get connected to the console of a VM in a vApp.

Here you will find a step by step description for Firefox and Adobe Flash Player

Access your vCloud Director Portal:

Adobe Flash Player:

flash1

So here you need to configure Firefox to accept the Flash Plugin (enter about:config):

Create a Boolean entry:

Set to true:

After these steps, go ahead connecting to your console port proxy (8443 in my case):

If you see the white and empty browser window, everything is good. Go ahead with downloading and installing the Adobe Flash Player Plugin.

After restarting your browser you are finished:

Google Chrome: Console access to vCloud Director 8.20 via WebMKS

Access to your vCloud Director frontend is working but you may have had the following problem accessing a console of a VM in a vApp:

Disconnected

Assuming you use port 8443 for your console port, you get the following:

IE_no_secure_connection

Click Advanced:

IE_no_secure_connection_advanced

So let’s go to fix it:

You need to use Internet Explorer to deal with the certificates. So you start like described above. After you continue to the insecure webpage:

IE_no_secure_connection_insecure

You see the Certificate error:

IE_no_secure_connection_Certificate_error

You need to be Administrator to import the certificate. Click on the untrusted certificate, View certificates:

IE_no_secure_connection_Certificate_error_View

Next is to install it:

IE_no_secure_connection_Certificate_Install

Use the wizard:

Import1

Import2

Click Browse and select Trusted Root Certification Authorities:

Import3

Import4

Import5

Import6

Import7

After you have restarted your Internet Explorer, connecting again to the console port you see no longer a Certificate error:

Import8

Now you go back to Google Chrome, see version used here:

Connected

VMware vCenter Server 6.0 Upgrade

You need to plan your upgrade before you start. The following aspects need to be checked (but are not limited to them):

  • UDP / TCP ports used
  • DNS name resolution (Forward, Reverse, Short, FQDN)
  • NTP time services
  • Server certificates
  • Plug-ins
  • Valid backup
  • Additional VMware products (f. ex. vCenter Chargeback, vSphere Auto Deploy) in use?
  • 3rd party products (Cisco Nexus 1000v) in use?
  • Target Deployment Model to be achieved
  • Guest OS
  • Database interoperability
  • Linked Mode in use?
  • Multisite Single Sign-On (manual replication)
  • Document Single Sign-On configuration

If you have changed your server certificates or the server name after installing vCenter server you should fix that before starting the upgrade or you should expect more time to succeed. I have had that two times onsite and it can cost a lot of time. You should use the SSL Automation Tool because it helps you.

Some needful Knowledge Base articles:

Upgrading to vCenter Server 6.0 best practices kb.vmware.com/kb/2109772

VMware Platform Services Controller 6.0 FAQs kb.vmware.com/kb/2113115

Check the VMware vSphere 6.0 Documentation Center:

http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.upgrade.doc/GUID-B90D873C-6C97-4C09-886A-0ACCE4A4034C.html

vCenter Server 5.1 upgrade to vCenter Server 6.0

Let us start with the following complex scenario:

  • VMware vCenter Server 5.1 Update 3 (Build 3070521)
  • Microsoft Windows Server 2008 R2 SP1 (Build 6.1.7601)
  • Microsoft SQL Server 2008 R2 SP3 (Build 10.50.6000.34)
  • Three geographical sites in Europe, Asia and USA
  • VMware vCenter Server, vCenter Single Sign-On, Inventory Service, Orchestrator, and Microsoft SQL Server 2008 R2 SP3 running on VMs 105, 106, 107
  • VMware vSphere Web Client and Update Manager running on VMs 102, 103, 104
  • VMware vCenter Server 5.1 Linked Mode configuration
  • VMware vCenter Server 5.1 Multisite Single Sign-On configuration
  • For each site, a Platform Services Controller is required

It is needed to reconfigure the environment before starting the upgrade process because it would result in an Embedded Deployment Model. For more information on that, check: kb.vmware.com/kb/2130433 and kb.vmware.com/kb/2033620

This post is about upgrading from vCenter Server 5.1 Update 3 to vCenter Server 6.0 Update 1 devided in seven parts.

Upgrade vCenter Server 5.1 to vCenter Server 6.0 Part VII

In part seven we upgrade the servers to version 6 update 1.

Upgrade of first VMware vCenter Server 6.0 on sw000105:

–>

1vcup01 1vcup02 1vcup03

–>

1vcup04

For this message, please use kb.vmware.com/kb/2114754 and go ahead.

–>

1vcup05 1vcup06 1vcup07

–>

1vcup08 1vcup09 1vcup11

–>

During the upgrade process (which takes quite a while), you can see the changes around the installed services:

1vcup12 1vcup14 1vcup16

–>

1vcup17

Upgrade of second and third vCenter Server 6.0 on sw000106 and sw000107:

On server sw000106:

I only pasted the screenshots differing from the process described above.

–>

2vcup012vcup02

On server sw000107:

–>

3vcup01 3vcup02

 

Upgrade vCenter Server 5.1 SSO Nodes to vCenter Server 6.0 Platform Services Controller (PSC) Part VI

In part six we upgrade the servers to version 6 update 1.

Install first VMware vCenter Server 6.0 Platform Services Controller on sw000108:

–>

1PSC1 1PSC2 1PSC3

–>

1PSC4 1PSC5 1PSC6

–>

1PSC7

Install second and third PSC on sw000109 and sw000110:

On server sw000109:

I only pasted the screenshots differing from the process described above.

–>

2PSC1 2PSC2 2PSC3

On server sw000110:

–>

3PSC1 3PSC2 3PSC3

The next steps describe the installation of the vCenter Server components.

VMWARE VCENTER SERVER 6.0 PRE-UPGRADE TASKS Part V

The current environment based on vCenter Server 5.1 has vCenter Server and vCenter Single Sign-On installed on one machine which results in an embedded deployment model for the Platform Services Controller (PSC) 6.0 during the upgrade. If a Linked Mode / Multi Site configuration is required, changes to the current environment need to be done next. We need to change the configuration before the upgrade because it is not supported to replicate SSO data between embedded and external deployment model. Please check kb.vmware.com/kb/2130433 and kb.vmware.com/2125119.

To continue, we need to:

  • Isolate the vCenter Servers from Linked Mode
  • Install three new VMs for vCenter Single Sign On
  • Reconfigure vCenter Services
  • Remove the legacy vCenter Single Sign On services from the servers

Isolation from Linked Mode (on sw000105):

–>

LMI1 LMI2 LMI3

–>

LMI4 LMI5 LMI6

We need to repeat the steps on the second vCenter Server (sw000106) in site Asia as well but not on the third or last server (sw000107).

Install new temporary VMware vCenter Single Sign-On on Server (sw000108):

Now we need to install a new Primary SSO Node which will substitute sw000105. We use SQL Express for SSO in the following.

–>

1SSOn1 1SSOn2 1SSOn3

–>

1SSOn4 1SSOn5 1SSOn6

–>

1SSOn7 1SSOn8 1SSOn9

–>

1SSOn10 1SSOn11 1SSOn12

–>

1SSOn13 1SSOn14 1SSOn15

The next steps are about reconfiguring vCenter Server components to the new SSO.

Reconfigure the vSphere Web Client on sw000102 to the new SSO service on sw000108:

–>

1SSOnwc1 1SSOnwc2 1SSOnwc3

I could start the Log Browser Service manually.

Repoint the Inventory Service from sw000105 to the new SSO service on sw000108:

–>

1SSOnis1 1SSOnis2 1SSOnis3

Repoint the vCenter Server Service from sw000105 to the new SSO service on sw000108:

–>

1SSOnvc1 1SSOnvc2 1SSOnvc3

–>

1SSOnvc4 1SSOnvc5

Remove the legacy Single Sign-On service from server sw000105:

–>

1SSOr1 1SSOr2 1SSOr3

–>

1SSOr4 1SSOr5

With that step we have reconfigured our first vCenter Server from site Europe. For the second vCenter server for site Asia and for the third on for USA, I have done the same with a temporary server joining the new existing SSO installation with reconfiguring like above.

VMWARE VCENTER SERVER 5.1 MULTI SITE AND LINKED MODE CONFIGURATION PART IV

The fourth part continues with the configuration of the THIRD site. The configuration of that environment differs a little bit because here we have installed all vCenter Server services on one virtual machine.

Third vCenter Server configuration (USA)

Server sw000107 will be used.

vCenter Single Sign On Third Node Installation (on sw000107):

The screenshots from creating the RSA database, vCenter Server database and vSphere Update Manager are not included in this part, please see Part I if needed.

–>

SSOd1 SSOd2 SSOd3

–>

SSOd4 SSOd5 SSOd6

–>

SSOd7 SSOd8 SSOd9

–>

SSOd10 SSOd11 SSOd12

–>

SSOd13 SSOd14 SSOd15

–>

SSOd16 SSOd17 SSOd18

–>

SSOd19 SSOd20

vCenter SSO Import from Part III (on sw000107):

According to kb.vmware.com/kb/2042849 (Step 6) we import the SSO data from the Primary Site Deployment into the Secondary Site:

–>

SSOd22

Next step is to install the Inventory Service.

VMware vCenter Inventory Service Installation (on sw000107):

–>

ISd1 ISd2 ISd3

–>

ISd4 ISd5 ISd6

–>

ISd7 ISd8 ISd9

–>

ISd10 ISd11 ISd12

–>

ISd13

VMware vCenter Server Installation (on sw000107):

–>

vcd1 vcd2 vcd3

–>

vcd4 vcd5 vcd6

–>

vcd7 vcd8 vcd9

–>

vcd10 vcd11 vcd12

–>

vcd13 vcd14 vcd15

VMware vSphere Web Client Installation (on sw000107):

–>

wcd1 wcd2 wcd3

–>

wcd4 wcd5 wcd6

–>

wcd7 wcd8

This post stops here with the installation screenshots. The VM sw000107 also has vSphere Update Manager and vSphere Client installed. The next important steps (looking into kb.vmware.com/kb/2042849, step 8) are the export of the SSO data from this VM (site USA) and the import of the SSO data into the Primary SSO (site Europe) and the second SSO (site Asia).