Infrastructure Manager Not Working After Upgrading to Secure State

[Akash Saini]

Hi Folks,

After upgrading from CA UIM 9.20 to 9.33S secure state, Infrastructure Manager (IM) stops working. In this case, when I try to log in to the primary hub using 127.0.0.1, no hubs or domains are listed,

Please help me out this issue.

Thanks in advance !

[Garin Walsh]

Have you tried running IM on your central hub and does it work any better/different than wherever you are currently running it?

IM should continue to work just recognize that IM will only be able to display information that the local hub knows already.

[David Michel]

Additionally, if the hub is running Linux the IM console will not work, and it is necessary to setup a Windows hub with IM console.

[Akash Saini]

Hi David,

All our hub are Windows hub.

[Akash Saini]

Hi Garin,

Yes ,Currently IM running on central hub.

And we also tried follow the below steps.

After upgrading from CA UIM 9.0.2 to 9.2.0 secure state, Infrastructure Manager (IM) stops working. In this case, when I try to log in to the primary hub using 127.0.0.1, no hubs or domains are listed.

 

Solution:

 

If you have a saved user profile, delete it from the 

..\Nimsoft\hub\profiles

 location.

But every time delete the profile is not good practice.

[Akash Saini]

Any one help me please .

[Garin Walsh]

Suggest you open a support case - there you have an SLA and expected response times. 

If IM was working before it should continue to work. The difference between secure and not secure hubs boils down to which ports and network interfaces on a given system the hub probe listens to. If you have your central hub configured as a secure hub and you RDP to that windows server and launch IM from there using a hub IP of 127.0.0.1, it should work the same as the older versions.

The fact that you can log in and authenticate says that it's talking at some level to the hub probe.

If it doesn't then you can get some additional information about what might not be working by viewing the message window in IM.

[Akash Saini]

Hi Garin,

Yes ,we already working with support case.

And in the past IM console working fine, Only issue started when we secure our primary hub.

And after delete the default profile in hub folder(\Nimsoft\hub\profiles) and restart the nimsoft service .IM working fine.
And every time follow this step this is not good practice.

And we also checked the message tab in IM ,-There is some error message -

Could you please help me of these error ?

Thanks in advance !

Akash Saini

[Akash Saini]

Any one please help me on this point.

Thanks in advance !

[Garin Walsh]

gethubs is the call that provides the list of hubs that IM displays so if you have a communications error here then that would be an obvious cause for IM not displaying data.

When you logged in to IM did you specify to log into 127.0.0.1? That's the only address the secure hub listens on for these connections from IM.

[Akash Saini]

Hi Garin,

Thanks for update .

yes we always use 127.0.0.1.

Because secure hub always login through the 127.0.0.1 in IM.

Akash Saini

[Andrew Cooper]

Akash

We run hubs v9.33S (ie secure hubs) but still use robots v9.33.

We have to install and run IM on the hub(s), we do not specify an address and just provide userid and password and it works. we do get a number of error in the console but we get the hub/robot/probe tree and most functionality of IM.  What we have seen is that we cannot launch the tools separately, they need to be launched from IM or they are not able to login.

When we were back at v9.20 not only did we get secure hubs working but we upgrqded the robots to secure version and this was a disaster, the robot worked BUT after 2 secure robots wher connected to the hub running a secure robot then the robots all starting timing out, they could not encrypt/decrypt the nimbus messages fast enought (log level 5 showed the problem), due to the timeouts nothing worked reliably including IM (I don't know what or how Broadcom did their QA for the configuration, but it must have been magically) and we upgraded the secure robots to plain robots and everything went back to normal.  Now the only issue is when we do a version update on the primary hub we have to "upgrade" the secure hub to the non-secure version and then do the version upgrade otherwise the upgrader forces us to do a secure upgrade which F..... us by upgrading both the hub and the robot to the secure version as part of the version upgrade.

So set your robots to plain version and see if you still have the problem, once you have it working like this then do the robot  upgrade to secure (and good like).

Regards, Andrew

------------------------------
Knows a little about UIM/DXim, AE, Automic
------------------------------