are subblocks of the same CIDR. For example, 192.0.2.1/21 and 192.0.2.1/24 are overlapping. As an exception, you can use the same CIDR (not subblock) for multiple systems. For example, you can use 192.2.0.0/22 as a CIDR for public EoIB network on multiple engineered systems. None of the networks configured in Oracle Enterprise Manager Ops Center overlaps with any network, that is, overlapping networks are not supported by Oracle Enterprise Manager Ops Center. Note – To manage two or more Oracle engineered systems that have overlapping networks or any networks already present in Oracle Enterprise Manager Ops Center, reconfigure one of the conflicting systems before it is discovered and managed by the same Oracle Enterprise Manager Ops Center. Example The following are example SuperCluster network configurations that you can use when configuring the network to discover and manage SuperCluster systems. Status OK indicates a valid configuration, and status Fail indicates an invalid configuration. Example SuperCluster Network Configuration 1 1GbE 10GbE IB First SuperCluster System 192.0.251.0/21 192.168.8.0/22 Second SuperCluster System 192.0.251.0/21 192.168.12.0/22 Status OK OK OK Status: OK – First SuperCluster system 1GbE and second SuperCluster system 1GbE share the same network. OK – First SuperCluster system 10GbE and second SuperCluster system 10GbE share the same network. OK – First SuperCluster system IB does not overlap with second SuperCluster system IB. Example SuperCluster Network Configuration 2 1GbE 10GbE IB First SuperCluster System 192.0.251.0/21 192.0.250.0/24 192.168.8.0/22 – IB fabric connected with second SuperCluster system
11 Client Access Networks Configuration Worksheets Complete the worksheets in this chapter to provide the necessary information for each of the client access networks that you want to use for your SuperCluster: Client Network 01 (Default Client Network) Complete these worksheets for additional networks for dedicated domains: Client Network 02 on page 69 Client Network 03 on page 69 Client Network 04 on page 70 Client Network 05 on page 70 Client Network 06 on page 71 Client Network 07 on page 71 Client Network 08 on page 72 Client Network 01 (Default Client Network) 13 -- Client Network 01 (Default Client Network) Item Entry Description and Example Start IP Starting IP address for this client access network. Gateway Gateway IP address for this client access network. Netmask Subnet mask for this client access network. Table 14 – Optional Second Client Network for Root Domains Only complete this table if you selected to configure a second port pair for SuperCluster M8
Table 60 -- RAC Cluster 30 Item Entry Description and Example Client Network The client network that you want to use for this cluster. See the information that you provided in Client Access Networks Configuration Worksheets on page 68 for more information on the available client networks. Example: Client network 1 Network Recipe The network recipe that you want to use for this cluster. See the information that you provided in Network Recipe Configuration Worksheets on page 73 for more information on the available network recipes. Example: Network recipe 1 VLAN The VLAN tag that you want to use for this cluster, if necessary. See VLAN Tag Configuration Worksheets on page 79 for more information on the available VLAN tags. Example: 101 Table 61 -- RAC Cluster 31 Item Entry Description and Example Client Network The client network that you want to use for this cluster. See the information that you provided in Client Access Networks Configuration Worksheets on page 68 for more information on the available client networks. Example: Client network 1 Network Recipe The network recipe that you want to use for this cluster. See the information that you provided in Network Recipe Configuration Worksheets on page 73 for more information on the available network recipes. Example: Network recipe 1 VLAN The VLAN tag that you want to use for this cluster, if necessary. See VLAN Tag Configuration Worksheets on page 79 for more information on the available VLAN tags. Example: 101
Table 81 -- PDomain 0 in Compute Server 1 Configuration Worksheet: Four CMIOUs Number and Type of Domains on PDomain 0 in Compute Server 1 Check One Box Config One Two Four U4-1 Cluster number: OR Client network number: Network recipe: VLAN tag: U4-2 Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: U4-3 Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: U4-4 Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: Database Zone Information If this LDom is a Database Domain with zones, your Oracle installer can set up a maximum of eight zones on this Database Domain during the initial installation. Your Oracle installer will also set up
Client Access Network, Network Recipe, VLAN Tag and Cluster Information Read and understand the information in Understanding Client Access Network, Network Recipe, VLAN Tag, and RAC Cluster Options on page 43 before completing the worksheets in this section. For every RAC cluster in your SuperCluster, you provided client network, network recipe, and VLAN tagging information in RAC Cluster Configuration Worksheets on page 81. Any Database Domain or database zone that is a member of a RAC cluster automatically gets assigned IP addresses from that RAC cluster’s client access network and has that cluster’s network recipe and VLAN tagging information. Therefore: If an LDom is a member of a RAC cluster, enter that RAC cluster number here. It will automatically get IP addresses from that RAC cluster’s client access network and will use that cluster’s network recipe and VLAN tagging information. If an LDom is not a member of a RAC cluster, the following: Client network number that you want to use for this LDom Network recipe that you want to use for this LDom VLAN tagging information, if necessary, for this LDom 96 -- PDomain 1 in Compute Server 1 Configuration Worksheet: Three CMIOUs Number and Type of LDoms on PDomain 1 in Compute Server 1 Check One Box Config One Two Three U3-1 Cluster number: OR Client network number: Network recipe: VLAN tag: U3-2 Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: U3-3 Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag:
U4-3 Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: U4-4 Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: Cluster number: OR Client network number: Network recipe: VLAN tag: Database Zone Information If this LDom is a Database Domain with zones, your Oracle installer can set up a maximum of eight zones on this Database Domain during the initial installation. Your Oracle installer will also set up the RAC clusters for the zones in this Database Domain, where multiple zones within this Database Domain could be clustered together, or could be clustered together with zones in other Database Domains. For every RAC cluster in your SuperCluster, you provided client network, network recipe, and VLAN tagging information in RAC Cluster Configuration Worksheets on page 81. Any database zone that is a member of a RAC cluster automatically gets assigned IP addresses from that RAC cluster’s client access network and has that cluster’s network recipe and VLAN tagging information. For each zone in this Database Domain, enter the RAC cluster number that you want that zone to be a member of. Table 122 -- Zone RAC Assignments Database Zones Cluster Number Database Zones Cluster Number Zone 1 Zone 5 Zone 2 Zone 6 Zone 3 Zone 7