Go to main content

Oracle® SuperCluster T5-8 Zones With Oracle Database on Database Domains Configuration Guide

Exit Print View

Updated: April 2020
 
 

IB Network Before Zone Creation (Full Rack)

Connection to the IB network is achieved through the IB host channel adapters (HCAs) installed in express module slots in each SPARC T5-8 server. There are four IB HCAs in each SPARC T5-8 server.

The IB HCAs, and the ports on each HCA, that are assigned to each domain vary, depending on the type of domains on each SPARC T5-8 server:

  • Giant Domain: The HCAs and the ports on those HCAs that are used to connect to the IB network vary, depending on the type of domain:

    • Database Domain:

      - Storage private network: Connections through P1 (active) on the IB HCA associated with the first CPU in the first processor module (PM0) in the domain and P0 (standby) on the IB HCA associated with the last CPU in the last processor module (PM3) in the domain.

      For a Giant Domain in a Full Rack, these connections are through P1 on the IB HCA installed in slot 3 (active) and P0 on the IB HCA installed in slot 16 (standby).

      - Exadata private network: Connections through P0 (active) and P1 (standby) on all IB HCAs associated with the domain.

      For a Giant Domain in a Full Rack, connections are made through all eight IB HCAs, 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 IB HCA associated with the first CPU in the first processor module (PM0) in the domain and P0 (standby) on the IB HCA associated with the last CPU in the last processor module (PM3) in the domain.

      For a Giant Domain in a Full Rack, these connections are through P1 on the IB HCA installed in slot 3 (active) and P0 on the IB HCA installed in slot 16 (standby).

      - Oracle Solaris Cluster private network: Connections through P0 (active) on the IB HCA associated with the first CPU in the second processor module (PM1) in the domain and P1 (standby) on the IB HCA associated with the first CPU in the third processor module (PM2) in the domain.

      For a Giant Domain in a Full Rack, these connections are through P0 on the IB HCA installed in slot 4 (active) and P1 on the IB HCA installed in slot 7 (standby).

  • Large Domains: The HCAs and the ports on those HCAs that are used to connect to the IB network will vary, depending on the type of domain:

    • Database Domain:

      - Storage private network: Connections through P1 (active) on the IB HCA associated with the first CPU in the domain and P0 (standby) on the IB HCA associated with the last CPU in the domain.

      For example, for the first Large Domain in a Full Rack, these connections are through P1 on the IB HCA installed in slot 3 (active) and P0 on the IB HCA installed in slot 12 (standby).

      - Exadata private network: Connections through P0 (active) and P1 (standby) on all IB HCAs associated with the domain.

      For a Large Domain in a Full Rack, connections are made through all eight IB HCAs, 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 IB HCA associated with the first CPU in the domain and P0 (standby) on the IB HCA associated with the last CPU in the domain.

      For example, for the first Large Domain in a Full Rack, these connections are through P1 on the IB HCA installed in slot 3 (active) and P0 on the IB HCA installed in slot 12 (standby).

      - Oracle Solaris Cluster private network: Connections through P0 (active) on the IB HCA associated with the second CPU in the domain and P1 (standby) on the IB HCA associated with the third CPU in the domain.

      For example, for the first Large Domain in a Full Rack, these connections are through P0 on the IB HCA installed in slot 11 (active) and P1 on the IB HCA installed in slot 4 (standby).

  • Medium Domains: The HCAs and the ports on those HCAs that are used to connect to the IB network will vary, depending on the type of domain:

    • Database Domain:

      - Storage private network: Connections through P1 (active) on the IB HCA associated with the first CPU in the domain and P0 (standby) on the IB HCA associated with the second CPU in the domain.

      For example, for the first Medium Domain in a Full Rack, these connections are through P1 on the IB HCA installed in slot 3 (active) and P0 on the IB HCA installed in slot 11 (standby).

      - Exadata private network: Connections through P0 (active) and P1 (standby) on all IB HCAs associated with the domain.

      For example, for the first Medium Domain in a Full Rack, connections are made through both IB 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 IB HCA associated with the first CPU in the domain and P0 (standby) on the IB HCA associated with the second CPU in the domain.

      For example, for the first Medium Domain in a Full Rack, these connections are through P1 on the IB HCA installed in slot 3 (active) and P0 on the IB HCA installed in slot 11 (standby).

      - Oracle Solaris Cluster private network: Connections through P0 (active) on the IB HCA associated with the first CPU in the domain and P1 (standby) on the IB HCA associated with the second CPU in the domain.

      For example, for first Medium Domain in a Full Rack, these connections are through P0 on the IB HCA installed in slot 3 (active) and P1 on the IB HCA installed in slot 11 (standby).

  • Small Domains: The HCAs and the ports on those HCAs that are used to connect to the IB network will vary, depending on the type of domain:

    • Database Domain:

      - Storage private network: Connections through P1 (active) and P0 (standby) on the IB HCA associated with the CPU associated with each Small Domain.

      For example, for a Small Domain that is associated with CPU0, these connections are through the IB HCA installed in slot 3, through ports P1 (active) and P0 (standby) on that IB HCA.

      - Exadata private network: Connections through P0 (active) and P1 (standby) on the IB HCA associated with the CPU associated with each Small Domain.

      For example, for a Small Domain that is associated with CPU0, these connections are through the IB HCA installed in slot 3, through ports P0 (active) and P1 (standby) on that IB HCA.

    • Application Domain:

      - Storage private network: Connections through P1 (active) and P0 (standby) on the IB HCA associated with the CPU associated with each Small Domain.

      For example, for a Small Domain that is associated with CPU0, these connections are through the IB HCA installed in slot 3, through ports P1 (active) and P0 (standby) on that IB HCA.

      - Oracle Solaris Cluster private network: Connections through P0 (active) and P1 (standby) on the IB HCA associated with the CPU associated with each Small Domain.

      For example, for a Small Domain that is associated with CPU0, these connections are through the IB HCA installed in slot 3, through ports P0 (active) and P1 (standby) on that IB HCA.