For previous versions of Oracle Enterprise Manager Ops Center, the Ops Center software was installed and run from the SuperCluster system. Beginning with the Oracle Enterprise Manager Ops Center 12c Release 2 (12.2.0.0.0) release, the Ops Center software must now run on a system (Enterprise Controller host) outside of the SuperCluster system.
The following conditions apply to Oracle engineered systems, such as SuperCluster systems.
One or more Oracle engineered systems can be discovered and managed by a single Oracle Enterprise Manager Ops Center instance based on these conditions:
• None of the Oracle engineered system instances have overlapping private networks connected through IB, that is, networks that have the same CIDR (Classless Inter-Domain Routing) or networks that are subblocks of the same CIDR. For example, 192.0.2.1/21 and 192.0.2.1/24 are overlapping.
• None of the Oracle engineered system instances or generic datacenter assets have overlapping management or client access networks connected through Ethernet, that is, networks that have the same CIDR or networks that 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.0.2.1/22 as a CIDR for Ethernet network on one or more engineered systems or generic datacenter assets.
• None of the Oracle engineered system instances have overlapping public networks connected through EoIB, that is, networks that have the same CIDR or networks that 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.
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.
|
Result:
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 network does not overlap with second SuperCluster system IB.
|
Result:
FAIL – First SuperCluster system 1GbE and second SuperCluster system 1GbE have overlapping networks.
OK – First SuperCluster system 10GbE and second SuperCluster system 10GbE have different non-overlapping networks.
FAIL – First SuperCluster system IB and second SuperCluster system IB networks do not have unique private networks (racks are not interconnected).