You can download the setup file from Oracle. Now extract the Ops Center installation zip:. Installer will ask your email to be able to install Oracle Configuration Manager. When the installer passed first steps, all you need is to wait.
Installation will smoothly complete. Installation is done. Now we need to connect to web interface of Ops Center to complete the configuration. We open our favorite browser and enter hostname of our server i. Ops Center warns us again about memory and disk space, we also see a warning about Java environment.
In this step, enter the hostname of Ops Center. As you know, Ops Center communicate with target systems through Proxy controllers and we may need to deploy multiple proxy controllers for separate networks.
Select the correct network interface from the pull-down menu and click next. Proxy controller will manage the systems which can connect through this network interface. If your server is connected to the internet, I recommend you to choose the connected mode to be able to use this new feature. Accept the default values or enter the locations to store Software library.
You can use NFS shares. Enter a name for discovery profile, and choose the target types you want to discover and click next. Conversion of old samples : starting Exit the CLI. Logical Domain Relationship is Lost After Automatic Recovery Automatic recovery of a logical domain results in loss of relationship information, such as the current name and associations with other assets. Workaround File a service request to recover the relationship information.
Upgrade your environment. Workaround Install the ksh and zlib. Workaround Perform the following steps: Delete the current Oracle Solaris 11 Library in the user interface. Create a new library directory for the existing Oracle Solaris 11 Library contents. Initialize the library using the new directory.
Workaround Delete the access point, then rediscover the ILom. Workaround 1 Retry the Agent Controller upgrade on the non-global zone. Workaround 2 Restart the Agent Controller on the non-global zone. Repeat the discovery of the Oracle SuperCluster system. The rack and its server assets are added. Association of Network to Oracle Solaris 11 Control Domain Job Fails With Unclear Results In an environment with multiple Control Domains that are directly interconnected using statistically allocated IPs, attempting to attach a new network can fail with an inconsistent error message.
Solution Log in to the Control Domain. Remove the IP address. Select the Control Domain and click Refresh in the actions pane. Workaround Copy the ISO image to the target system and use the local copy. Workaround Restart the Enterprise Controller.
Workaround Select the Operational Plan first and then select the group as a target. Unable to Use Console for Manually Created Zone in Agent-Managed Control Domain If you manually create a zone in an agent-managed control domain, the console access user is given an incorrect role and cannot access the console.
Workarounds The first workaround is to connect to the control domain console, then connect to the zone. The second workaround is to give the user the correct role. If a second deployment plan is initiated using the same SAN library, when the first deployment plan is still in progress, the deployment wizard will use the same available LUNs for zone storage which were already used earlier.
Therefore, both jobs will partially fail with only a few zones created. Do not submit these kind of jobs in parallel. The accounts that are created as part of the Oracle Enterprise Manager Ops Center 12c installation are not listed in the documentation. The svctag and xvm users are expected to have the default UIDs of 95 and 60, respectively. On an Oracle Solaris platform, when you reboot the global zone hosting the kernel zone based on iSCSI storage, an error is displayed. After the global zone has booted successfully, manually attach zones on the global zone again by using the following command:.
During the creation of zone with a shared CPU, if you choose the allow override any profile values option, the shared CPU value is changed to dedicated CPU value and hence the creation of kernel zone fails. The dynamic network edit of a zone is based on the Global Zone Solaris version.
For Oracle S10 branded zones, the dynamic network edition should not be allowed. You can start a job when the zone is running. This job will not dynamically edit the zone configuration. Restart the S10 branded zone at the end of the job for the zone configuration to be updated. Log in to the service processor and enable the servicestate property value by using the following commands:. When creating a Kernel Zone from Oracle Enterprise Manager Ops Center user interface, if the user requires 2 interfaces, in order to connect 2 networks with an IP address in both interface in the Kernel Zone and if both networks are connected on the same interface in the Global Zone that will host the Kernel Zone, then both anets are properly created but one of the IPs may be missing in the Kernel Zone OS the datalink is not configured in the OS.
Create the Kernel Zone without a maximum of 1 network interface from the same Global Zone lower-link. Once the Kernel Zone is created, additional network connections may be added from the same Global Zone lower-link using the Attach Network action.
When adding a new network interface with an IP address to a running kernel zone from its server asset, the new anet will be added only in the persistent zone configuration but does not add in the live zone configuration. After an automatic move of the logical domain guest from a source server to a destination server, launching some operations on the recovered guest reboot, delete, migrate, connect network, move metadata, automatic recovery fails.
Some operations fail when the host ID collision detection finds two images for the recovered guest, on source server and destination server. This issue will be automatically fixed when the source server is reachable again, since the image gets cleaned once the server is available. You can also set collision.
This will prevent checking host ID collisions before launching these operations. After the source server is available again, set the variable back to true. There is mismatch between vlan tagging information shown on network Dashboard and Network Details tab. Follow the Network Details tab to get the correct vlan tagging information about the network.
When upgrade fails at a customer site for some reason, rolling back to previous version, the subsequent successful upgrade leaves Proxy Controller in OFFLINE state, until it is manually restarted by the customer. For example, reporting host ids collisions. JDK 1. This breaks OpsCenter agent controllers and proxy controllers that rely on Java derby for monitored data. With Solaris This is also observed outside of Ops Center when the zone is created through through command line as well.
Port must be available for the Proxy Controller. No other application on the Proxy Controller should use this port. After upgrading Solaris to Solaris This is an underlying Solaris bug.
This affects the corresponding operations like patching Solaris 10 servers, downloading OS image, and so on. Solaris The workaround is to install these packages on the global zones as well. Describes information on prerequisites, installation, upgrade, known issues, and uninstall of Oracle Enterprise Manager Ops Center software.
Describes the new features included in the release, prerequisites, known issues, and information about installing and uninstalling Oracle Enterprise Manager Ops Center software.
Installation and Administration Quick Start Guide. Describes how to quickly install and configure the Oracle Enterprise Manager Ops Center software for a basic monitoring setup.
0コメント