These topics provide information on the Medium Domain configuration for the Full Rack:
The amount of CPU and memory resources that you allocate to the logical domain varies, depending on the size of the other domains that are also on the SPARC T5-8 server:
Config F3-1 (One Large Domain and two Medium Domains): The following options are available for CPU and memory resource allocation:
Four sockets for the Large Domain, two sockets apiece for the two Medium Domains
Two sockets for the Large Domain, four sockets for the first Medium Domain, two sockets for the second Medium Domain
Two sockets for the Large Domain and the first Medium Domain, four sockets for the second Medium Domain
Six sockets for the Large Domain, one socket apiece for the two Medium Domains
Five sockets for the Large Domain, two sockets for the first Medium Domain, one socket for the second Medium Domain
Five sockets for the Large Domain, one socket for the first Medium Domain, two sockets for the second Medium Domain
Config F4-1 (Four Medium Domains): The following options are available for CPU and memory resource allocation:
Two sockets apiece for all four Medium Domains
One socket for the first Medium Domain, two sockets apiece for the second and third Medium Domains, and three sockets for the fourth Medium Domain
Three sockets for the first Medium Domain, one socket for the second Medium Domain, and two sockets apiece for the third and fourth Medium Domains
Three sockets for the first Medium Domain, two sockets apiece for the second and fourth Medium Domain, and one socket for the third Medium Domain
Three sockets for the first Medium Domain, two sockets apiece for the second and third Medium Domains, and one socket for the fourth Medium Domain
Config F4-2 (One Large Domain, two Small Domains, one Medium Domain): The following options are available for CPU and memory resource allocation:
Four sockets for the Large Domain, one socket apiece for the two Small Domains, two sockets for the Medium Domain
Three sockets for the Large Domain, one socket apiece for the two Small Domains, three sockets for the Medium Domain
Two sockets for the Large Domain, one socket apiece for the two Small Domains, four sockets for the Medium Domain
Five sockets for the Large Domain, one socket apiece for the two Small Domains and the Medium Domain
Config F5-1 (Three Medium Domains, two Small Domains): The following options are available for CPU and memory resource allocation:
Two sockets apiece for the first and second Medium Domains, one socket apiece for the first and second Small Domains, two sockets for the third Medium Domain
One socket for the first Medium Domain, two sockets for the second Medium Domain, one socket for the first Small Domain, two sockets apiece for the second Small Domain and the third Medium Domain
Two sockets apiece for the first and second Medium Domains, one socket for the first Small Domain, two sockets for the second Small Domain, one socket for the third Medium Domain
Two sockets for the first Medium Domain, one socket for the second Medium Domain, two sockets for the first Small Domain, one socket for the second Small Domain, two sockets for the third Medium Domain
Config F6-1 (Two Medium Domains, four Small Domains): The following options are available for CPU and memory resource allocation:
Two sockets for the first Medium Domain, one socket apiece for the four Small Domains, two sockets for the second Medium Domain
Three sockets for the first Medium Domain, one socket apiece for the four Small Domains and the second Medium Domain
One socket apiece for the first Medium Domain and the four Small Domains, three sockets for the second Medium Domain
Config F7-1 (One Medium Domains, six Small Domains): Two sockets for the Medium Domain, one socket apiece for the six Small Domains
The number and type of 1-GbE host management ports that are assigned to each Medium Domain varies, depending on the CPUs that the Medium Domain is associated with:
CPU0/CPU1: NET0-1
CPU2/CPU3: NET1, NET3 (through virtual network devices)
CPU4/CPU5: NET0, NET2 (through virtual network devices)
CPU6/CPU7: NET2-3
Two PCI root complex pairs, and therefore two 10-GbE NICs, are associated with the Medium Domain on the SPARC T5-8 server in the Full Rack. One port is used on each dual-ported 10-GbE NIC. The two ports on the two separate 10-GbE NICs would be part of one IPMP group.
The following 10-GbE NICs and ports are used for connection to the client access network for the Medium Domains, depending on the CPUs that the Medium Domain is associated with:
CPU0/CPU1:
PCIe slot 1, port 0 (active)
PCIe slot 9, port 1 (standby)
CPU2/CPU3:
PCIe slot 2, port 0 (active)
PCIe slot 10, port 1 (standby)
CPU4/CPU5:
PCIe slot 5, port 0 (active)
PCIe slot 13, port 1 (standby)
CPU6/CPU7:
PCIe slot 6, port 0 (active)
PCIe slot 14, port 1 (standby)
A single data address is used to access these two physical ports. That data address allows traffic to continue flowing to the ports in the IPMP group, even if the connection to one of the two ports on the 10-GbE NIC fails.
The connections to the InfiniBand network vary, depending on the type of domain:
Database Domain:
Storage private network: Connections through P1 (active) on the InfiniBand HCA associated with the first CPU in the domain and P0 (standby) on the InfiniBand HCA associated with the second CPU in the domain.
For example, for the first Medium Domain in a Full Rack, these connections would be through P1 on the InfiniBand HCA installed in slot 3 (active) and P0 on the InfiniBand HCA installed in slot 11 (standby).
Exadata private network: Connections through P0 (active) and P1 (standby) on all InfiniBand HCAs associated with the domain.
For example, for the first Medium Domain in a Full Rack, connections would be made through both InfiniBand HCAs (slot 3 and slot 11), with P0 on each as the active connection and P1 on each as the standby connection.
Application Domain:
Storage private network: Connections through P1 (active) on the InfiniBand HCA associated with the first CPU in the domain and P0 (standby) on the InfiniBand HCA associated with the second CPU in the domain.
For example, for the first Medium Domain in a Full Rack, these connections would be through P1 on the InfiniBand HCA installed in slot 3 (active) and P0 on the InfiniBand HCA installed in slot 11 (standby).
Oracle Solaris Cluster private network: Connections through P0 (active) on the InfiniBand HCA associated with the first CPU in the domain and P1 (standby) on the InfiniBand HCA associated with the second CPU in the domain.
For example, for first Medium Domain in a Full Rack, these connections would be through P0 on the InfiniBand HCA installed in slot 3 (active) and P1 on the InfiniBand HCA installed in slot 11 (standby).