are subblocks of the same CIDR. For example, and 192.0.2.1/21 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 as a CIDR for public 192.2.0.0/22 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 192.0.251.0/21 192.168.8.0/22 First SuperCluster System 192.0.251.0/21 192.168.12.0/22 Second SuperCluster System 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 192.0.251.0/21 192.0.250.0/24 First SuperCluster IB fabric 192.168.8.0/22 – System connected with second SuperCluster system
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
E58632.docx