Thursday Aug 27, 2015

How Many Systems Can Ops Center Manage?

I saw a question about how many systems you can manage through Ops Center. This is an important question when you're planning a deployment, or looking at expanding an existing deployment.

In general terms, an Enterprise Controller can manage up to 3,000 assets. A Proxy Controller can manage between 350 and 450 assets, although you'll get better performance if there are fewer assets.

The Sizing and Performance guide has more detailed information about the requirements and sizing guidelines for Ops Center.

Thursday Aug 20, 2015

Editing or Disabling Analytics

There was a recent question thread about how you can tweak the OS analytics settings in Ops Center.

"Ops Center collects analytics data every 5 minutes and retains it for 5 days. Is it possible to edit these settings?"

You can edit the retention period but not the collection interval.

To edit the retention period, log into the UI. Click the Administration section, then click the Configuration tab for the EC, and select the Report Service subsystem.

The repsvc.daily-samples-retention-days property specifies the number of days to retain OS analytics data. You can edit this property, then restart the EC to make it take effect.

"Can I turn off data collection for OS analytics entirely?"

Yes, you can. Bear in mind that this requires you to edit a config file, so be very careful.

Go to the /opt/sun/n1gc/lib directory on the EC and find the XVM_SATELLITE.properties file. Edit it to uncomment this line:

#report.service.disable=true

Then, restart the Enterprise Controller.

Thursday Aug 13, 2015

Recovering After a Proxy Controller Crash

I saw a question recently about how to restore your environment if a remote Proxy Controller system fails. This is a good question, and there are a few facets to the answer, depending on your environment.

Recovery is easiest if you have recently backed up the Proxy Controller. The backup file includes asset data, so if you can restore the PC using the backup file, you should be golden.

If you don't have a backup of the Proxy Controller, it's going to take a bit more work. First, you have to migrate the dead PC's assets to a new PC. If you have automatic failover enabled, this happens automatically (hence the name); otherwise you can do it manually.

Then, you can install a new Proxy Controller (using the Linux or Solaris procedure), and migrate the assets to that PC.

Thursday Jul 30, 2015

Recovering LDoms From a Failed Server

I saw a recent question about Logical Domain recovery: If you have a control domain installed on a server and the server goes down with a hardware fault, what options do you have for recovering the logical domains from that control domain?

The answer is that you have options depending on how your environment is configured:

  • If you have the control domain in a server pool, and you have enabled automatic recovery on the LDom, you have the option of watching as the LDom is automatically brought back up on another control domain in the server pool.
  • If the control domain is in a server pool but you didn't enable automatic recovery, you can still manually migrate the guest by deleting the control domain asset. The guests will then be put in the Shutdown Guests list for the server pool, and you can bring it up on another control domain.
  • If you want to add the failed control back in, before you rediscover it and put it back in the server pool, you should log in and make sure that the guest OS isn't running, to avoid split brain issues.

    Take a look at the Recover Logical Domains from a Failed Server how-to for more information.

    Thursday Jul 23, 2015

    Kernel Zones support in 12.3

    One of the new features in Ops Center 12.3 is support for Oracle Solaris kernel zones. I wanted to talk a bit about this, because there are some caveats, and a new document to help you with using this type of zone.

    Kernel zones differ from other zones in that they have a separate kernel and OS from the global zone, making them more independent. In Ops Center 12.3, you can discover and manage kernel zones. However, you can't migrate them, put them in a server pool, or change their configuration through the user interface.

    We put together a how-to that explains how you can discover existing kernel zones in your environment. You can also take a look at the What's New doc for more information about what's changed in 12.3.

    Thursday Jul 16, 2015

    New Books in 12.3

    One of the changes that we've made in Ops Center 12.3 is a change to the documentation library. We've divided the old Feature Reference Guide up into several smaller books so that it's easier to use:

    • Configure Reference talks about how to get the software working - discovering assets; configuring libraries, networks, and storage; and managing jobs.
    • Operate Reference talks about incidents, reports, hardware management, and OS management, provisioning, and updating.
    • Virtualize Reference describes the use and management of Oracle Solaris Zones, Oracle VM Servers for SPARC, and server pools.
    • Oracle SuperCluster Operate Reference covers the management of Oracle SuperCluster.

    The What's New doc has more information about these new books. You can find the new books by clicking Feature Reference on the main doc site.

    Thursday Jul 09, 2015

    New Virtualization Icons

    There's a change in the UI that I wanted to talk about, since it's been confusing some people after they upgrade to version 12.3. The icons that represent the different virtualization types, such as Oracle Solaris Zones or Logical Domains, have changed. Here are the new icons:

    We made this change because there were getting to be a lot of supported virtualization types, particularly now that Kernel Zones are supported. The new icons make it easier to differentiate between different types so that you know at a glance what sort of system you're dealing with.

    The other new features in version 12.3 are discussed in the What's New document.

    Thursday Jun 25, 2015

    Ops Center 12.3 is Released

    Version 12.3 of Ops Center is now available!

    This is a major upgrade from the prior versions. In addition to bug fixes and performance enhancements, there are a number of new features:

    • Asset discovery refinements, including the ability to run discovery probes only on a specific network or from a specific Proxy Controller
    • Support for discovering and managing existing Oracle Solaris 11 Kernel Zones
    • The ability to create a custom Oracle Solaris 11 AI manifest and use it for provisioning
    • Refined search: Searching for one or more assets now displays the search results in a new tab in the Navigation pane, making navigation a bit easier
    • New and expanded books in the doc library

    Take a look at the What's New In This Release document for a more detailed breakdown of the new features, and the Upgrade guide for more information about upgrading to version 12.3.

    You can also take a look at the 12.3 documentation library here.

    Thursday Jun 11, 2015

    Providing Contact Info for ASR

    Ops Center includes a feature called Auto Service Request, which can automatically file service requests for managed hardware. However, I've seen a bit of confusion about how to get it running.

    First, the prereqs - to get ASR running, you need to be in connected mode, and you need to have a set of My Oracle Support (MOS) credentials entered in the Edit Authentications window. Your MOS credentials have to be associated with a customer service identifier (CSI) with rights over the hardware that you want to be enabled for ASR.

    Once you've got that, you'll click the Edit ASR Contact Information action in the Administration section. This opens a window where you specify the default contact information for your assets, which is used for all ASRs by default.

    If you have assets that need separate contact information, you can specify separate ASR contact information for an asset or a group of assets. That info is used in place of the default contact info.

    Finally, once you've got the contact info in the system, you click Enable ASR. This action launches a job to enable the assets for ASR, and it attempts to enable new assets for ASR when they're discovered. From then on, if a critical incident occurs on the hardware, ASR should create a service request for it.

    Take a look at the Auto Service Request chapter of the Admin Guide for more information.

    Thursday Jun 04, 2015

    Enterprise Controllers in Logical Domains

    I saw a few questions about installing Enterprise Controllers in Logical Domains, and what's possible with that sort of deployment. Here are some answers:

    "Is it supported to install the Enterprise Controller in a Logical Domain?"

    Yep. The Certified Systems Matrix lists the supported OSes for EC installation, and Oracle VM Server for SPARC is supported (as are some Oracle Solaris Zones).

    "Can you use Oracle Solaris Cluster to provide High Availability for an Enterprise Controller installed on a Logical Domain?"

    Yes, this is possible. It deserves its own post, so I'll go into more detail on it soon, but yes, it works.

    "If I have two Enterprise Controllers installed on Logical Domains, can I have EC 1 discover and manage the LDom for EC 2, and vice versa?"

    No. The Agent Controllers installed on EC and PC systems are different from standard Agents, and if you install an Agent from one EC on another EC's system, it's going to get confused.

    Thursday May 28, 2015

    Uploading and Deploying Oracle Solaris 11 Files

    I saw a question recently about uploading flat files, such as a config file, or tarballs to an Oracle Solaris 11 library and then deploy them to Oracle Solaris 11 servers. This is an easy task for Oracle Solaris 8, 9, or 10, but it's trickier to find with Oracle Solaris 11.

    Here are the steps to upload and deploy such files with Oracle Solaris 11 in Ops Center, using our software library for the content.

    1. Create an Oracle Solaris 11 pkg which contains the config files. Here's an example for how to do so: http://docs.oracle.com/cd/E23824_01/html/E21798/glcej.html
    2. Add that pkg to the repository. (The above example also covers this step.)
    3. Sync Ops Center with the repository so that the new pkg is added to Ops Center's catalog of software.
    4. Create an Ops Center Oracle Solaris 11 Profile that installs the pkg created in Step 1.
    5. Apply the profile in an update plan to the target systems.

    For more information about OS Profiles, see the OS Updates chapter.

    Thursday May 21, 2015

    Special Database Options

    When you're installing Ops Center, you have two options for the product database: You can use an embedded database, that's automatically installed on the Enterprise Controller and managed by Ops Center, or you can use a remote database that you manage yourself.

    With regards to the customer-managed database, I saw an important question recently: When you install this database, do you have to enable any of the advanced or special features? Some folks want to use the bare minimum installation for security reasons.

    The answer here is that Ops Center only requires the base installation; no special features are used. As long as you're using one of the DB versions listed in the Certified Systems Matrix, you're golden.

    Thursday May 07, 2015

    Clustered Ops Center installation

    Today's question from an Ops Center user:

    "Can we cluster Ops Center deployments using, say, Solaris Cluster? How would we do it?"

    Well, there are a couple of possible ways that you can install the Enterprise Controller so that it can fail over.

    The first method is to use the documented HA installation, which uses Oracle Clusterware, two or more Enterprise Controller systems, and a remote customer-managed database. The procedures for this kind of installation are documented in the Oracle Solaris and Linux install guides.

    The second is to install the Enterprise Controller in an LDom controlled by Oracle Solaris Cluster, and then have the Enterprise Controller fail over between hosts via Cluster. You can use an embedded database or a remote database with this solution.

    Thursday Apr 30, 2015

    Using Maintenance Mode

    So, after last week's post about blacklisting assets for Ops Center, a couple of people pointed out that there's another - probably easier - way of temporarily stopping an asset from generating ASRs if you're doing maintenance on it: Putting the asset in maintenance mode.

    Putting an asset in maintenance mode stops it from generating new incidents, so that when you power off or reconfigure it, Ops Center doesn't freak out. Ops Center doesn't stop managing the asset, and you can then disable maintenance mode when you're done.

    Bear in mind that Ops Center will also treat the asset as though it's about to go down: If you put a Proxy Controller in maintenance mode it can't run jobs, and if you put an Oracle VM Server for SPARC in maintenance mode Ops Center will try to migrate its guests to another system in the server pool, or stop them if no other system is available.

    Take a look at the Incidents chapter in the Feature Reference Guide for more information about maintenance mode.

    Thursday Apr 23, 2015

    Disabling ASR for a specific asset

    Enabling ASR for your environment helps you get quick assistance when you have a hardware issue - Ops Center takes asset information when a hardware incident occurs, and generates a service request based on contact information and MOS credentials that you've provided.

    The trick, though, is that you enable ASR for your entire environment. You can provide separate contact info for some groups, but when you enable it it's on for all assets that are associated with the credentials. So, what if you're performing some hardware maintenance, and you don't want to accidentally cause ASR to open a service request?

    In cases like this, you can add an asset to a blacklist, to prevent ASRs from being generated for it. Select the Enterprise Controller from the admin section of the UI, then click configuration. In the list of subsystems, select Auto Service Request. You can then enter one or more serial numbers in a comma-separated list in the serial blacklist field to disable ASR creation for those assets. Monitoring of the assets still happens, and ASRs are created for other assets as normal.

    The ASR chapter in the Admin guide goes into more detail about how to get ASR running.

    About

    This blog discusses issues encountered in Ops Center and highlights the ways in which the documentation can help you

    Search

    Archives
    « August 2015
    SunMonTueWedThuFriSat
          
    1
    2
    3
    4
    5
    7
    8
    9
    10
    11
    12
    14
    15
    16
    17
    18
    19
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
         
    Today