Understanding Small Domains (Half Rack)

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

• Percentage of CPU and Memory Resource Allocation

• Management Network

• 10-GbE Client Access Network

• InfiniBand Network

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:

• One Medium Domain and two Small Domains: The following options are available for CPU and memory resource allocation:

  • Two sockets for the Medium Domain, one socket apiece for the two Small Domains

  • One socket for the Medium Domain, two sockets for the first Small Domain, one socket for the second Small Domain

  • One socket for the Medium Domain and the first Small Domain, two sockets for the second Small Domain

• Four 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)

• 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 Half 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)

• 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.

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.