This section describes the network connections required for multiple networks of Exalogic machine. The network cables must be run from your network equipment to the location of the Exalogic machine.
The requirements to connect the Exalogic machine to your existing Ethernet network infrastructure are described in the following sections:
Before installation, network cables must be run from your existing network infrastructure to the installation site. The requirements to connect the Exalogic machine to your existing network infrastructure are as follows:
Management network connection requirements
At least one Ethernet connection for the Ethernet switch in the rack to the existing management network. The total number of connections depends on your HA requirements for the data center.
Client access network connection requirements
At least one Ethernet over InfiniBand (EoIB) bond per Exalogic compute node to the client access network is required. Additional client access network interface bonds are added for each physical LAN or each virtual LAN (VLAN) in which the compute node is connected. The minimum configuration requires (single Bond to single LAN per compute node) the number of network connections per Exalogic compute node, as outlined in the subsequent table for Full Rack, Half Rack, and Quarter Rack configurations.
The following table describes the number of required connections:
| Type of Exalogic Machine | Bonded Network Configuration |
|---|---|
|
Exalogic machine full rack |
30 |
|
Exalogic machine half rack |
16 |
|
Exalogic machine quarter rack |
8 |
|
Exalogic machine eighth rack |
4 |
Up to eight external physical networks can be connected through EoIB using the Sun Network QDR InfiniBand Gateway Switch. You can create multiple bonded vNICs on the compute nodes.
Additional network connection requirements
You must determine the following:
How many LANs to connect to (typically, 1 or 2, maximum 8 physically isolated LANs)
How many 10 Gb ports per LAN are required (your network throughput requirements for client access network)
At least two 10 Gb Ethernet ports per compute node - one active and another passive.
The following are the connection choices based on the number of Ethernet ports:
1 active 10 Gb Ethernet port shared by up to 8 compute nodes
2 active 10 Gb Ethernet ports shared by up to 8 compute nodes
1 port shared by 4 compute nodes for 1 LAN
1 port shared by 8 compute nodes for 2 LANs (1 port per LAN per compute node)
4 active 10 Gb Ethernet ports shared by up to 8 compute nodes
1 port shared by 2 compute nodes for 1 LAN (1 port per LAN per compute node)
1 port shared by 4 compute nodes for 2 LANs (1 port per LAN per compute node)
1 port shared by 8 compute nodes for 4 LANs (1 port per LAN per compute node)
8 active 10 Gb Ethernet ports shared by up to 8 compute nodes
1 port per 1 compute node for 1 LAN
1 port shared by 2 compute nodes for 2 LANs (1 port per LAN per compute node)
1 port shared by 4 compute nodes for 4 LANs (1 port per LAN per compute node)
1 port shared by 8 compute nodes for 8 LANs (1 port per LAN per compute node)
An Exalogic machine requires a large number of host names and IP addresses during initial configuration. The number of IP addresses required for a particular network, such as the management network, depends on the type of system. The network configuration, such as host names and IP addresses, used during installation is generated from information you supply to your Oracle technical representative in the completed configuration worksheet. See Network Configuration Worksheets.
Configure the new IP addresses in your existing networks only after you have completed the configuration worksheets, and received the installation Template from your Oracle representative. All IP addresses in the installation Template must be unassigned at the time of initial configuration. In addition, all IP addresses must be statically assigned IP addresses, not dynamically assigned (DHCP) addresses.
All InfiniBand physical IP addresses in BOND0 must be in the same subnet, with a minimum subnet mask of 255.255.240.0 (or /20). The subnet mask chosen should be wide enough to accommodate possible future expansion of the Exalogic machine and InfiniBand network. Each device (compute nodes, switches, and storage appliance) in the Exalogic rack is assigned a separate Local Identifier (LID) by the IB Subnet Manager. Oracle Exalogic supports a single IP over IB (IPoIB) link over a logical Exalogic deployment over the IB subnet. Multiple IP subnets can be layered on top of the default IPoIB link.
Table 6-2 lists the IP address requirements for the Exalogic machine:
Table 6-2 IP Address Requirements for Exalogic Machine
| Type of Exalogic Machine | Management Network Requirements | Client Access Network Requirements | InfiniBand Private Network (IPoIB) Requirements |
|---|---|---|---|
|
full rack |
Minimum of 68 IP addresses
|
Minimum of one IP address per Bond. Additional IP addresses per Bond added as per Service or Protocol requirements. For example, HTTP may only expose a floating IP address to an external Load Balancer and not to the HTTP Client (only observes VIP of Load Balancer), while JMS may expose the virtual IP directly to the JMS Client. Typically, an application server supporting both HTTP and JMS will have a floating IP address for JMS (public) and a floating IP address for HTTP (private to the Load Balancer). In addition, T3 typically uses a minimum of two IP addresses. One of these IP addresses is private to the Load Balancer, and the other floating IP address is exposed to application server clients. An application server client initially accesses the application server through a well-known virtual IP address, such as |
Minimum of one IP address per bond per compute node. Exalogic machine full rack contains 30 compute nodes. One compute node can be a member of only one private network of an application domain. |
|
half rack |
Minimum of 38 IP addresses
|
Same as above. |
Minimum of one IP address per bond per compute node. Exalogic machine half rack contains 16 compute nodes. One compute node can be a member of only one private network of an application domain. |
|
quarter rack |
Minimum of 22 IP addresses
|
Same as above. |
Minimum of one IP address per bond per compute node. Exalogic machine quarter rack contains 8 compute nodes. One compute node can be a member of only one private network of an application domain. |
|
eighth rack |
Minimum of 20 IP addresses
|
Same as above. |
Minimum of one IP address per bond per compute node. Exalogic machine eighth rack contains 4 compute nodes. One compute node can be a member of only one private network of an application domain. |