Thursday Apr 07, 2016

What are JMX Credentials and What is Ops Center Doing With Them?

When you discover a Solaris Cluster, you're asked to provide ssh credentials and JMX credentials. You already know the ssh credentials but what about those JMX credentials? They're for the agent on the cluster's global node. The agent uses JMX so they're called JMX credentials. Think of them as agent credentials.

The only thing these credentials are doing is allowing the agent on the global node to respond to the Enterprise Controller. Without the JMX creds, you can discover and manage the cluster server itself, but nothing else. If you look in the log file, you'll see a message like "JMXMP provider exception Connection refused." With the JMX creds, Ops Center authenticates the agent, connects to the agent, and acquires all the agent's information about the global node.

JMX credentials can be anything convenient for you, like cluster1 and cluster2, and simple passwords. For all global nodes to use the same credentials, create one set in the discovery profile and run the discovery job. However, if for some reason, you need to use a unique set of credentials for each global node, create each set of credentials in a credential profile and then run a discovery job for each global node. You'll use the same discovery profile but change the credential profile for each job. You can still keep it simple, like cluster1node1 and cluster1node2.

For more information, take a look at the Oracle Solaris Cluster section of the Configuration Reference.

Thursday Apr 09, 2015

Adding an Asset to a Group During Discovery

A lot of people use user-defined groups to organize their assets in ways that make sense for their environment - like having groups for different locations, or groups based on the primary purpose of the assets. If you're adding a number of new assets, though, it can be a bit of a pain to discover all of them and then manually add them to the correct group.

A solution to this issue is to use group rules and tags to add the assets to the correct group during the discovery process. First, you edit the group and use the Create Group Rules option. You can create a rule that will add assets to the group automatically if they have a specific tag.

Then, when you're discovering systems that belong in a group, use the Tags step of the discovery profile wizard to add the corresponding tag to those assets as they're discovered. They will then be added to the correct group automatically.

See the Asset Management chapter of the Feature Reference Guide for more information about discovery and asset groups.

Thursday Feb 12, 2015

Discovery Changes

There were a few changes to the discovery process in Ops Center 12.2.2. If you've already upgraded, you might have noticed some of them, but I thought I'd give you the rundown.

The first change is an enhancement for zones and LDoms discovery. In version 12.2.2, when you discover a control domain or global zone and manage it with an Agent, any non-global zones or logical domains on them are discovered automatically. There are also some performance enhancements in this area, so the discoveries ought to go quicker now than in past.

The other change is that the Find Assets wizard, which searches for assets using service tags, is now disabled by default. This is mostly because, since this method searches for service tag-equipped products on all networks associated with a Proxy Controller, it can end up being a big resource drain/timesink in a very large environment. If you want, you can still enable it.

Thursday Jun 19, 2014

How-To: Discovering a Fujitsu M10 Server

Discovering an asset, whether it's hardware, an OS, or virtualization, is the first step in managing it with Ops Center. Discovery lets Ops Center know what assets are there, and lets it begin to monitor those assets and target them with jobs.

Most assets can be discovered using the discovery procedures in the Feature Reference Guide. However, there are a few types of assets that have quirks that you have to take into account during discovery. Fujitsu M10 Servers, have a few settings that must be configured before you can discover it through the UI. We put together a how-to guide for these systems that explains those quirks, and then walks you through the entire discovery process.

If you're planning on discovering any Fujitsu M10 Servers, this guide has all of the information you'll need. There are also a few other server-specific discovery how-tos in the Deploy library, so take a look.

Friday Feb 14, 2014

Adding an asset on a remote network

I saw an interesting question about discovering assets:

"I'm trying to discover a new chassis. I have three Proxy Controllers and all of them can ping the chassis, but only one has the firewall access to communicate with it. None of the Proxy Controllers has a direct connection to the network with the chassis, so that network isn't in the network list. How do I get the discovery job to route correctly?"

There is a solution in the discovery profile here. The discovery profile has a field for the target host or IP address, and a dropdown for the network. When you put the profile together, you supply the asset's IP address, and then select a network that has a route to the network with the chassis on it. Run that and you'll be able to discover the asset.

Wednesday Apr 24, 2013

How To: Discover an Oracle SPARC T5 Server

When you're deploying new hardware, it's helpful to have as specific a plan as possible. For instance, it's good to know how to run a discovery in Ops Center, but if you have a guide that specifically explains how to discover the type of hardware that you're installing, that makes your job even simpler.

With that in mind, we put together a How-To that explains how to discover new Oracle SPARC T5 servers. It walks you through creating IPMI and SSH credentials, creating a discovery profile, and running it to discover the new system or systems. It also gives you pointers to the asset management and hardware management chapters in the feature guide, which provide a broader range of information about discovering and managing hardware.

Tuesday Mar 12, 2013

Discovery question

I got a question about discovering operating systems:

"My operating systems are configured not to allow root SSH access. How can I discover these OSes with Ops Center?"

When you're creating a discovery profile, you provide credentials for each protocol being used to access the asset. So, for an Oracle Solaris OS, you provide SSH credentials. If root SSH access is allowed by the system, you can provide root credentials.

However, if root SSH access is not allowed, you can provide one username and password to use for logging in, and then the root credentials to use for managing the asset.

Here's what it looks like in the UI:

The first set is used to log in, and the second set is used to perform tasks that require root access, such as installing or uninstalling Agent Controllers.

Tuesday Dec 11, 2012

Discovering Assets on Multiple Subnets

I saw this question recently, about making discovery work:

"I am attempting to discover a group of ILOMs which seem to be on a different subnet than their hosts. When I try to discover the ILOMs, Ops Center can't find them. Is it a requirement that the ILOM and its host should be on the same subnet?"

The short answer is no, related assets don't have to be on the same subnet for you to discover them. The correlation between related assets doesn't depend on them being on the same subnet.

What's likely going on, if you're running into similar issues, is that the subnet where you're trying to discover systems needs to be associated with a Proxy Controller that can reach it. You can go here to see how to associate a network with a Proxy Controller. Once the network is associated with a Proxy Controller, you should be able to discover and manage assets on it.

Tuesday Sep 25, 2012

Discovery methods

In Ops Center, asset discovery is a process in which the software determines what assets exist in your environment. You can't monitor an asset, or do anything to it through Ops Center, until it's discovered. I've seen a couple of questions about how to discover various types of asset, so I thought I'd explain the discovery methods and what they each do.

Find Assets - This discovery method searches for service tags on all known networks. Service tags are small files on some hardware and operating systems that provide basic identification info. Once a service tag has been found, you provide credentials to manage the asset. This method can discover assets quickly, but only if the target assets have service tags.

Add Assets with discovery profile - This method lets you specify targets by providing IP addresses, IP ranges, or hostnames, as well as the credentials needed to connect to and manage these assets. You can create discovery profiles for any type of asset.

Declare asset - This method lets you specify the details of a server, with or without a configured service processor. You can then use Ops Center to install a new operating system or configure the SP. This method works well for new hardware.

These methods are all discussed in more detail in the Asset Management chapter of the Feature Reference guide.


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


« May 2016