9.2.3 VLAN Support

OEDA now supports the creation of VLANs on compute nodes and storage servers for the admin network, ILOM, client and the backup access network. Note the following:

• Client and backup VLAN networks must be bonded. The admin network is never bonded.

• If the backup network is on a tagged VLAN network, the client network must also be on a separate tagged VLAN network.

• The backup and client networks can share the same network cables.

• OEDA supports VLAN tagging for both physical and virtual deployments.

• IPv6 VLANs are supported for bare metal on all Oracle Exadata systems except for X2 and V2 systems.

  IPv6 VLAN with VM is not supported currently.

Note:

If your system will use more than 10 VIP addresses in the cluster and you have VLAN configured for the Oracle Clusterware client network, then you must use 3 digit VLAN ids. Do not use 4 digit VLAN ids because the VLAN name can exceed the 15 character operating system interface name limit.

The following table shows IPv4 and IPv6 support on the admin, client, and backup networks for the different Exadata systems and Oracle Database versions.

Version of Oracle Database	VLAN Tagging on Admin Network	Client and Backup Networks
11.2.0.4	Only supported with IPv4 addresses on X3-2 and above for two-socket servers, and X4-8 and above for eight-socket servers.	Supported with IPv4 and IPv6 on all hardware models.
12.1.0.2	Only supported with IPv4 addresses on X3-2 and above for two-socket servers, and X4-8 and above for eight-socket servers.	Supported with IPv4 on all hardware models. Supported with IPv6 on all hardware models with fix for 22289350.

See "Using Network VLAN Tagging with Oracle Exadata Database Machine" in the Oracle Exadata Database Machine Installation and Configuration Guide for details.