2.3.1 VLAN Support on Customer-Facing Networks

Oracle Exadata can use VLANs to implement network partitioning in conjunction with the client, backup, administration, and ILOM networks.

By default, the network switches are minimally configured, without VLAN tagging. If VLAN tagging is to be used, then it can be configured by the customer during the initial deployment. Customers can also configure VLAN tagging after the initial deployment. This applies to both physical and virtual machine (VM) deployments.

Notes:

• Oracle Exadata Deployment Assistant (OEDA) supports VLAN tagging for both physical and VM deployments.

• Network VLAN tagging is supported for Oracle Real Application Clusters (Oracle RAC) on the public network.

• Client and backup VLAN networks must be bonded. The administration 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.

• VLAN tagging on the client and backup networks is supported with IPv4 and IPv6 on all hardware models. For IPv6 support on Oracle Database version 12.1.0.2, and later, patch 22289350 is also required.

• VM deployments do not support IPv6 VLANs.

• VLAN tagging on the administration network is only supported with IPv4 addresses on X3-2 and above for two-socket servers, and X4-8 and above for eight-socket servers.

• If the client network uses VLAN tagging and your system uses more than 10 Oracle Clusterware virtual IP (VIP) addresses, then you must use 3-digit VLAN IDs. Do not use 4-digit VLAN IDs because the VLAN name can exceed the operating system interface name limit, which is the 15 characters.