OnCommand Unified Manager 6.1RC1 Quick Install Guide

I needed OCUM 6.1 in my lab to test. I’ve got a vSphere ESXi 5.5U1 standalone host and a vCenter Server 5.5U1 (5.5U1 is not actually supported yet, the Installation and Setup Guide only goes up to ESXi 5.5 and vCenter 5.1!) Remember, OCUM 6.1 is free, no license is required!

Hardware Requirements

The ESXi 5.5U1 host requires minimum: 4 GB RAM, 2 CPU cores, 4 GB Disk Space*

*4 GB is the minimum recommended, it will install on 1 GB though!

OCUM 6.1 requires minimum: 8 GB RAM (reserved), 2 CPU cores and 4786 MHz (reserved), 5 GB Disk Space if using thin provisioning or 152 GB if thick provisioning

                                

OCUM 6.1 recommended requirement is: 12 GB RAM (reserved), 4 CPU cores and 9572 MHz (reserved), 5 GB Disk Space if using thin provisioning or 152 GB if thick provisioning

For my lab - which is all running in VMware Workstation, including the ESXi host - I’ll give the ESXi host 12 GB RAM, 2 CPU cores, 4 GB Disk Space - for the ESXi install - plus a 50 GB thin-provisioned disk for OCUM 6.1. And for OCUM 6.1 - 8 GB RAM (keeping the reservation on), 2 CPU cores (no reservation), and use thin provisioning.

Software Requirements

Browser: IE 8 (not 64-bit), IE9, IE10 - for all 3, compatibility mode is not supported; Chrome versions 30 and 31; Firefox versions 24 and 25

Client Platforms: Windows Vista, 7 and 8; RHEL 6; SLES 11 SP2; MAC OS X 10.8

Port Requirements: Connections to OCUM 6.1

HTTP port 80: Unified Manager web UI (redirects to HTTPS port 443)

HTTPS port 443: Unified Manager web UI and programs using APIs

SSH/SFTP port 22: Maintenance console

MySQL port 3306: OnCommand Workflow Automation and OnCommand Report access

Port Requirements: Connections from OCUM 6.1

HTTPS port 443: Storage systems

HTTPS port 443: AutoSupport server

LDAP port 389: Authentication requests for users and groups

SMTP port 25: Alert notification emails

SNMPv1 or SNMPv3 port 162 (UDP): Send alert notification SNMP traps

NTP port 123 (UDP): Synchronize time

Information Required before Deployment

OVF Template Deployment

- Name for the deployed template in vCenter

- vCenter inventory location for the deployed template

- Disk Format {Thick Lazy Zeroed, Thick Eager Zeroed, Thin}

- Host FQDN

- IP Address

- Network Mask

- Gateway

- Primary DNS

- Secondary DNS

OCUM 6.1 Appliance Setup

- Geographic area

- Time zone

- Maintenance user username

- Maintenance user password

Installation Step by Step Walkthrough

Download the image file

Download the image file - OnCommandUnifiedManager-6.1RC1.ova - from:

http://support.netapp.com/NOW/download/software/oncommand_cdot/6.1RC1/

Deploy OVF Template

Login to the vSphere Client

File Menu > Deploy OVF Template

Image: vSphere Client - Deploy OVF Template...

Follow through the “Deploy OVF Template” wizard as below:

Deploy OVF Template: Source

Deploy from a file or URL: {Point this at your downloaded OnCommandUnifiedManager-6.1RC1.ova}

Click Next >

Deploy OVF Template: OVF Template Wizard Details

The details are as in the image below.

Click Next >

Image: OCUM OVF details

Deploy OVF Template: End User License Agreement

Click Accept to accept the EULA

Click Next >

Deploy OVF Template: Name and Location

Enter name for the deployed template in vCenter

Select the vCenter inventory location for the deployed template

Click Next >

Deploy OVF Template: Disk Format

The choice is: Thick Provision Lazy Zeroed, Thick Provision Eager Zeroed or Thin Provision.

For the lab we’ll definitely select ‘Thin Provision’

Click Next >

Deploy OVF Template: Properties

Complete the ‘Static Networking configuration’ sheet with the information obtained earlier (in the ‘Information Required before Deployment’ section above)

Click Next >

Image: OCUM OVF deploy - ‘Static Networking configuration’

Deploy OVF Template: Ready to Complete

Review the ‘Deployment settings’.

Leave ‘Power on after deployment’ unchecked*

Click Finish

*Only so we can adjust settings before power-on for lab purposes

If all’s good you’ll be rewarded with “Deployment Completed Successfully”.

Image: Deploying OCUM Completed Successfully

Configuring the OCUM 6.1 VM

For a lab environment, you may want to adjust the OCUM 6.1 VM’s Virtual Machine Properties. Out of the box, OCUM 6.1 is configured with 12 GB memory and 4 CPUs. It also comes with a CPU reservation of 9572 MHz and Memory reservation of 12288 MB.

Image: OCUM VM Properties - Hardware tab 

Image: OCUM VM Properties - Resources tab

Powering on the OCUM 6.1 VM

Click the ‘Power On’ button to boot the OCUM 6.1 VM Appliance.

Note: On first boot, the VMware Tools will automatically configure and update.

Configuring the OCUM 6.1 VM in the console: Geographic Area

First prompt is for the ‘Geographic area’, enter as appropriate.

Image: OCUM console - configuring geographic area

Configuring the OCUM 6.1 VM in the console: Time zone

Then you will be prompted for the ‘Time zone’, enter as appropriate.

Image: OCUM console - configuring time zone

Configuring the OCUM 6.1 VM in the console: Username and Password

The next prompt is for the username and password for the new maintenance user.

Image: OCUM console - configuring maintenance user

And that’s it, we’ve deployed OCUM 6.1!

Image: OCUM console - at OCUM login prompt

And can get to the login box via an internet browser at https://OCUM_IP_ADDRESS!

Image: OCUM web UI login

To be continued ... (time permitting - configuring OCUM 6.1, OPM 1.0, and integration with WFA 2.2+)

Further Reading

OnCommand Unified Manager 6.1RC1 Release Notes

OnCommand Unified Manager 6.1 Installation and Setup Guide

Errors in my lab trying to boot the OCUM 6.1 VM

Originally, I gave my ESXi 5.5U1 host 10 GB RAM and 25 GB disk (with OCUM 8GB and 2 CPU). After removing the memory reservation, I got -

Failed to extend swap file from 0 KB to 83888608 KB

- so I put the memory reservation back on (in hindsight, having a bigger disk might have fixed this). Then I got -

The available memory resources in the parent resource pool are insufficient for the operation

- so I shut down the host and gave it 12 GB RAM. Hence my recommendation is for 12 GB RAM for the ESXi lab host and 50GB disk (had only 3.42GB free on first boot with a 25GB disk.)