Implementing Tagged VLAN Interfaces for the Management Network in Oracle VM Environments on Exadata (Doc ID 2090345.1)

Last updated on JANUARY 22, 2016

Applies to:

Oracle Exadata Storage Server Software - Version 12.1.2.1.1 and later
Linux x86-64
This document is applicable to Oracle VM Environments on Exadata.

Goal

Demonstrate the implementation of tagged VLAN interfaces in Oracle VM environments on Exadata for the Management network (eth0).

Background

Oracle databases running in Oracle VM guests on Oracle Exadata Database Machine are accessed through the client Ethernet network defined in the Oracle Exadata Deployment Assistant (OEDA) configuration tool. Client network configuration in both the management domain (dom0) and user domains (domUs) is done automatically when OEDA installation tool creates the first user domain during initial deployment.

This document only concerns implementing VLAN Tagging on the Management network with this VLAN's' being mapped to the eth0 interface in one DomU, or guest Domain. To implement VLAN Tagging on the Client network (bondeth0) see <Note 2018550.1>. 

This document covers modifying an existing deployed OVM system. All steps in this document are preformed after a successful deployment of Exadata and the DomU's. This document only concerns the creation of tagged VLAN management network interfaces on the compute nodes on the working network interface (eth0) to a separate Tagged VLAN (eth0.xxxx).

It is assumed that all management protocols, SMTP, ssh, DNS, ntp, ASR, and EM have been validated and work in the existing DomU on the Access VLAN.

The storage nodes are not to be moved to a tagged VLAN. The iLOM cabling is covered in the section "Sun Integrated Lights Out Manager Cabling Tables", but the iLOM's are not to be moved to a tagged VLAN. Each eth0 in each component including the IB switches, Cisco switch, and PDU's are to remain on the Access VLAN. The eth0's in the Dom0 of the compute nodes are to remain on the Access VLAN.

This document does not cover the security or firewall requirements to keep the various management VLAN's separate.

For the Cisco switch port numbers for the compute nodes see the manual:

Before any changes are made, make sure you have the following information:

  1. The new IP address and subnet mask that will be used for the Tagged VLAN interface
  2. The tagged VLAN ID
  3. The ports in the Cisco switch to which the eth0 interfaces are connected

This diagram illustrates the final design goal:

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms