Management access point authentication failure

Some users of Ops Center 12.1.4 are seeing an issue where, after upgrading or doing a new install, their assets are getting dozens of warning incidents that say "Management access point failed authentication during login to asset." Eventually, the severity increases as the warnings pile up, and communication with the asset can be disrupted.

You can prevent this issue, or halt it if you've already hit it, by logging in to the Enterprise Controller and creating a /var/tmp/no_os_selfhealing file if it doesn't exist. For example:

touch /var/tmp/no_os_selfhealing

You can use this fix before you do the upgrade or installation, to prevent the issue from occurring at all.

If you have assets that are already having communication trouble because of the issue, then once you've added the file as described above, you can solve the issue by deleting and rediscovering the asset deleting the Access Point for the Service Processor, and then rediscovering just the hardware. If you have a Proxy Controller or Enterprise Controller that's been affected, you should restart them after applying this fix.

Edit: You can also fix the issue by downloading the latest version of the OCDoctor (4.24) and running it with the --troubleshoot option. Take a look at this bulletin for more info.

Edit 2: Updated to use a less destructive fix for affected assets.

Comments:

"deleting and rediscovering the asset" is not a problem solution. If the asset has many months' worth of statistics, they will be lost. Or if the asset is a global zone managing many non-global zones, it's even worse. The correct solution is to fix the authentication failure.

Posted by guest on August 07, 2013 at 07:27 PM MDT #

Guest,

Yeah, you're right. Deleting the asset can do a lot of damage.

We've now tested a less intrusive fix, which is to remove the SP access point and rediscover the hardware. I've updated the post to explain it.

Posted by Owen on August 09, 2013 at 12:39 PM MDT #

Slightly related, but what if your host at the OS level has its IP changed? There doesn't seem to be a way to tell OC the IP has changed for an asset that it created. We changed the IP manually after failing to find a way to get OC to change the host's IP.

Thanks

Posted by guest on August 21, 2013 at 01:43 PM MDT #

Guest,

I don't know of a way to change the IP address for a managed asset. I think that in that case you would have to unmanage and delete it.

Posted by Owen on August 22, 2013 at 04:06 PM MDT #

If an asset is agentless it only has one access point. Does that mean removing the asset is the only option?

Posted by guest on September 24, 2013 at 10:20 AM MDT #

What happens if I change ip address of the managed asset? I thought like that; agent is installed in the asset and if agent communicates with proxy controller via network whether asset ip is not important because asset agent tries to access to the proxy controller that is not problem to change ip address of the asset?

What do you think about that?

Posted by guest on January 22, 2014 at 01:13 PM MST #

Guest,

The trick is that the Proxy Controller needs to be able to contact the Agent Controller as well. So, if you change an asset's IP address, you then have to rediscover that asset.

Posted by Owen on January 29, 2014 at 09:15 AM MST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

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

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
5
6
7
8
9
11
12
13
14
15
16
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today