03 Setting Cloud for IaaS 2

Overview

Once I resolved the issue described in OVMM Fails to Enable TCPS Connections, I was able to continue with Setting Cloud for IaaS.

References

• EM 12c: OVM Manager Metric Collection Error or Registration not working after upgrading to Enterprise Manager 12c Release 2 (Doc ID 1490283.1)
• Oracle® Enterprise Manager Cloud Administration Guide 12c Release 3 (12.1.0.3)
  • 4 Setting Cloud for IaaS
    • 4.3 Registering the Oracle VM Manager
    • 4.4 Synchronizing the Oracle VM Manager Targets
    • 4.5 Discovering a Virtual Server
    • 4.7 Setting Up Networks
    • 4.8 Creating a Network Profile

Procedure

4.3 Registering the Oracle VM Manager

I repeated the following steps from 02 Setting Cloud for IaaS.

Export OVMM Certificate

No change to the procedure.

Import OVMM Certificate into OEM Agent

First, I had to delete the imported certificate from the agent's key-store as follows:

${JAVA_HOME}/bin/keytool -delete -keystore /u01/app/oracle/agent/agent_inst/sysman/config/montrust/AgentTrust.jks -alias ovmm

As described in MOS Document 1490283.1, the password is welcome.

The procedure continues as before.

Remove the Exported OVMM Certificate

No change to the procedure.

Second Attempt to Register OVMM

Used the same parameters from the first attempt.

The job took 55 seconds to complete successfully.

4.4 Synchronizing the Oracle VM Manager Targets

Following the procedure in 4.3 Synchronizing the Oracle VM Manager Targets, I found that I had already enable automatic synchronisation of targets via the OVMM registration process described above.

4.5 Discovering a Virtual Server

Following the procedure in 4.4 Discovering a Virtual Server, I submitted a job to discover the Oracle VM Server on VICTORIA

. The job completed successfully after 32 seconds.

4.7 Setting Up Networks

Followed the procedure in 4.7 Setting Up Networks.

4.7.1 Generating MAC Addresses

I created the same VNICs as described in the manual (starting at 00:21:f6:12:00:00).

4.7.2 Configuring a VLAN Group

Since no VLANs exist in my home network, I skipped this step.

4.7.3 Creating Networks

Since I am not using VLANs, I decided to create a networks for:

1. the cluster interconnect on VICTORIA
2. the storage network from ETH2 on VICTORIA with static IP address of 192.168.1.104 and MTU of 9000

I now have the following networks:

IP Addresses has been updated to reflect this IP address allocation.

4.8 Creating a Network Profile

Decided not to follow the procedure in 4.8 Creating a Network Profile.