Understanding Small Domains (Full Rack)

Language:

Note - If you have the Full Rack, you cannot install a Fibre Channel PCIe card in a slot that is associated with a Small Domain. In Full Rack configurations, Fibre Channel PCIe cards can only be added to domains with more than one 10-GbE NIC. One 10-GbE NIC must be left for connectivity to the client access network, but for domains with more than one 10-GbE NICs, other 10-GbE NICs can be replaced with Fibre Channel HBAs. See Understanding Full Rack Configurations for more information on the configurations with Small Domains and Using an Optional Fibre Channel PCIe Card for more information on the Fibre Channel PCIe card.

These topics provide information on the Small Domain configuration for the Full Rack:

Percentage of CPU and Memory Resource Allocation

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 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 F5-2 (One Large Domain, four Small Domains): The following options are available for CPU and memory resource allocation:
- Four sockets for the Large Domain, one socket apiece for the four Small Domains
- Three sockets for the Large Domain, one socket apiece for the first three Small Domains, two sockets for the fourth Small Domain
- Two sockets for the Large Domain, one socket apiece for the first and second Small Domains, two sockets apiece for the third and fourth Small Domains
- Two sockets for the Large Domain, one socket apiece for the first three Small Domains, three sockets for the fourth Small Domain
- Two sockets for the Large Domain and the for the first Small Domain, one socket apiece for the second and third Small Domains, two sockets for the fourth Small 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
Config F8-1 (Eight Small Domains): One socket for each Small Domain

Management Network

The number and type of 1-GbE host management ports that are assigned to each Small Domain varies, depending on the CPU that the Small Domain is associated with:

CPU0: NET0-1
CPU1: NET1, NET3 (through virtual network devices)
CPU2: NET0, NET2 (through virtual network devices)
CPU3: NET1, NET3 (through virtual network devices)
CPU4: NET0, NET2 (through virtual network devices)
CPU5: NET1, NET3 (through virtual network devices)
CPU6: NET0, NET2 (through virtual network devices)
CPU7: NET2-3

10-GbE Client Access Network

One PCI root complex pair, and therefore one 10-GbE NIC, is associated with the Small Domain on the SPARC T5-8 server in the Full Rack. Both ports are used on each dual-ported 10-GbE NIC, and both ports on each 10-GbE NIC would be part of one IPMP group. Both ports from each dual-ported 10-GbE NIC is connected to the 10-GbE network for the Small Domains.

The following 10-GbE NICs and ports are used for connection to the client access network for the Small Domains, depending on the CPU that the Small Domain is associated with:

CPU0:
- PCIe slot 1, port 0 (active)
- PCIe slot 1, port 1 (standby)
CPU1:
- PCIe slot 9, port 0 (active)
- PCIe slot 9, port 1 (standby)
CPU2:
- PCIe slot 2, port 0 (active)
- PCIe slot 2, port 1 (standby)
CPU3:
- PCIe slot 10, port 0 (active)
- PCIe slot 10, port 1 (standby)
CPU4:
- PCIe slot 5, port 0 (active)
- PCIe slot 5, port 1 (standby)
CPU5:
- PCIe slot 13, port 0 (active)
- PCIe slot 13, port 1 (standby)
CPU6:
- PCIe slot 6, port 0 (active)
- PCIe slot 6, port 1 (standby)
CPU7:
- PCIe slot 14, 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.

Note - You can also connect just one port in each IPMP group to the 10-GbE network rather than both ports, if you are limited in the number of 10-GbE connections that you can make to your 10-GbE network. However, you will not have the redundancy and increased bandwidth in this case.

InfiniBand Network

The connections to the InfiniBand network vary, depending on the type of domain:

Database Domain:
- Storage private network: Connections through P1 (active) and P0 (standby) on the InfiniBand HCA associated with the CPU associated with each Small Domain.
  
  For example, for a Small Domain that is associated with CPU0, these connections would be through the InfiniBand HCA installed in slot 3, through ports P1 (active) and P0 (standby) on that InfiniBand HCA.
- Exadata private network: Connections through P0 (active) and P1 (standby) on the InfiniBand HCA associated with the CPU associated with each Small Domain.
  
  For example, for a Small Domain that is associated with CPU0, these connections would be through the InfiniBand HCA installed in slot 3, through ports P0 (active) and P1 (standby) on that InfiniBand HCA.
Application Domain:
- Storage private network: Connections through P1 (active) and P0 (standby) on the InfiniBand HCA associated with the CPU associated with each Small Domain.
  
  For example, for a Small Domain that is associated with CPU0, these connections would be through the InfiniBand HCA installed in slot 3, through ports P1 (active) and P0 (standby) on that InfiniBand HCA.
- Oracle Solaris Cluster private network: Connections through P0 (active) and P1 (standby) on the InfiniBand HCA associated with the CPU associated with each Small Domain.
  
  For example, for a Small Domain that is associated with CPU0, these connections would be through the InfiniBand HCA installed in slot 3, through ports P0 (active) and P1 (standby) on that InfiniBand HCA.