What are the capabilities in Ops Center for RSC-based servers? (Doc ID 1520211.1)

Last updated on JULY 20, 2023

Applies to:

Goal

Customer concerns:

What are the capabilities in Ops Center for RSC-based servers? It appears RSC-based devices are not working when 'add asset' was selected in the GUI. I have attempted to add a number of RSC-based servers to OC12cU2 without success. I realize that RSC's are not going to give me hardware monitoring capabilities, but I am more concerned with the ability to patch the OS on these servers, and single-user mode activities will require connection to the RSC poweron/poweroff/console operations.

When I use add asset and specify the profile and the target IP <IP>  , I receive an error:

12/31/2012 01:39:02 PM EST INFO Starting default discovery (Server) for target <IP> (<IP>)... (10111)
12/31/2012 01:39:07 PM EST ERROR Discovery driver reported: Fail to retrieve the ethernet ports Cannot obtain ethernet port MAC addresses for <IP>. Check that the device is powered off while discovering it and ensure that the OBP and Rsc firmware versions are supported., driver=ServerDriver:rsc, at target <IP>. (10137)
12/31/2012 01:39:07 PM EST INFO Ending default discovery (Server), found 0 resource(s) at target <IP> (<IP>). (10112)

The message is confusing; should I really have the device powered off to detect the ethernet MAC? Sounds more like the query doesn't return MAC info properly, but that is supposition.

I'm assuming that they are supported (there's a discovery profile for them). Has anyone been able to get RSC connections working with OC12cU2?

Section added Later...

I did test adding a RSC-based device (a V880) to OpsCenter. I made an OpsCenter account on the RSC. I powered off the host OS. I then did the RSC discovery, I watched the messages on the RSC screen..

RSC Alert: Host System has Reset
RSC Alert: Host system has shut down.
RSC Alert: Host System has Reset
RSC Alert: Host system has shut down.
RSC Alert: Host System has Reset
RSC Alert: Host system has shut down.

Reset 8 times, powered off 3 times.

But in the end it did add it, and yes there is no hardware info, nor is there anything about onboard memory or server type, that's ok - I can get the serial number.

By reading the OpsCenter documentation, I was under the impression that a LOM-based account was required for OS patching. Like, for example, if patching requires single-user mode, the LOM connecion would be used because console access is available. Is this incorrect? Do I really need LOM-based connectivity for patching?

Bigger question: if I do not need LOM-based connectivity for patching, then can I use OpsCenter to patch my E20K frames (they have SC connections that are not supported by OpsCenter, but they can run the OS-based agent)?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.