•
1 Ethernet port for Sun Integrated Lights Out Manager (ILOM) remote
management
Note:
The SFP+ modules for the NEMs are purchased separately.
2.3 Using Network VLAN Tagging with Oracle Exadata
Database Machine
Compute nodes and storage nodes can use VLANs for the management network,
ILOM, client network, and the backup access network.
By default, the network switch is minimally configured, without VLAN tagging. If VLAN
tagging is to be used, then it must be enabled by the customer after the initial
deployment. This applies to both physical and Oracle VM deployments.
Client and backup VLAN networks must be bonded. The admin network is never
bonded.
Notes:
•
VLANs do not exist in InfiniBand. For equivalent functionality, use
InfiniBand partitioning as described in Oracle Exadata Database Machine
Maintenance Guide.
•
Network VLAN tagging is supported for Oracle Real Application Clusters
on the public network.
•
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.
•
Oracle Exadata Deployment Assistant (OEDA) supports VLAN tagging for
both physical and virtual deployments.
•
Virtual deployments do not support IPv6 VLANs.
•
If your system will use more than 10 VIP addresses in the Oracle RAC
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/IPv6 support on the admin, client, and backup
networks for the different Exadata systems and Oracle Database versions.
Chapter 2
Using Network VLAN Tagging with Oracle Exadata Database Machine
2-10
