frankabhinav Super Contributor.
Super Contributor.
1047 views

iManager not working

Hi There,

We have installed eDirectory and iManager on a two different server. Where server1 is our primary and server2 is secondary.

Server1---> eDirectory--Primary(Master)
Server2---> eDirectory--Secondary(Read and write)
Server3---> iManager
Server4---> iManager

Case1: When Shuting down primary server . we are unable to login through imanager through seconday server or it some time takes 30 min or so and also when we are
logged in we are unable open driverset and when we are starting up the primary sever everything work fine. Where our iManager has not communication with eDirectory

Please guys tell me the reason and solution to it
Labels (1)
0 Likes
5 Replies
Knowledge Partner
Knowledge Partner

Re: iManager not working

On 11/20/2018 07:24 AM, frankabhinav wrote:
>
> We have installed eDirectory and iManager on a two different server.
> Where server1 is our primary and server2 is secondary.


Which versions? Any reason you did not put iManager on the eDirectory
boxes themselves? Does iManager Workstation work any better?

> Server1---> eDirectory--Primary(Master)
> Server2---> eDirectory--Secondary(Read and write)
> Server3---> iManager
> Server4---> iManager
>
> Case1: When Shuting down primary server . we are unable to login through
> imanager through seconday server or it some time takes 30 min or so and
> also when we are


How are you telling it to login through the secondary server specifically?
What do you have in the tree field on the login form in either the
working or broken case?

> logged in we are unable open driverset and when we are starting up the
> primary sever everything work fine. Where our iManager has not
> communication with eDirectory


If the Driverset is only hosted on the so-called "primary" server then
that's normal; some things are server-specific with IDM, so if you turn
off one that odes IDM things then you'll get timeouts as iManager tries to
read data from a particular replica.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
frankabhinav Super Contributor.
Super Contributor.

Re: iManager not working

Which versions? Any reason you did not put iManager on the eDirectory
boxes themselves? Does iManager Workstation work any better?


We have put iManager 3.1 and eDirectory 9.0. Yes , We have put all IDM product on different server just to avoid any conflict. Though it would work same.

How are you telling it to login through the secondary server specifically?
What do you have in the tree field on the login form in either the
working or broken case?


We are login into iManager with tree name in working case and ip address of Secondary server edirectory in broken case and username is admin.sa.system.

If the Driverset is only hosted on the so-called "primary" server then
that's normal; some things are server-specific with IDM, so if you turn
off one that odes IDM things then you'll get timeouts as iManager tries to
read data from a particular replica.


We have created drivers on both server and created an script for Driver failover which is constantly running at every 5 min of interval of time.

I dont really get by what you mean by turnoff one that odes IDM things
0 Likes
Knowledge Partner
Knowledge Partner

Re: iManager not working

On 11/20/2018 11:24 PM, frankabhinav wrote:
>
> We have put iManager 3.1 and eDirectory 9.0. Yes , We have put all IDM
> product on different server just to avoid any conflict. Though it would
> work same.


Without knowing the nature of the problem I am not sure how we can know it
would work the same if iManager ran on the eDirectory boxes directly.
Have you tested that to know that is the case, maybe with iManager
Workstation?

> We are login into iManager with tree name in working case and ip address
> of Secondary server edirectory in broken case and username is
> admin.sa.system.


If you specify the IP address of a server and still cannot login then I
would probably start by verifying communication works there. Perhaps the
second server does not allow communication to it from the iManager server
which is on a different box. This could easily be the case if a network
or host-based (windows) firewall is blocking access from machines other
than the other eDirectory server. It could also be the case if the second
server does not have a real replica of the user object, or maybe even the
security container. Knowing more about your eDirectory tree setup on
these two machines may help.

Also, when you login via tree name there is no way to know, without
looking more closely, which server is being accessed. Perhaps the second
server is the one accessed the first time you login, but the next time
iManager could just as easily pick the first server; it all depends on how
the tree name resolves, and that is typically done via SLP, though some
places add the tree name to DNS as well. I would ltroubleshoot this by
only logging in via IP address (for troubleshooting purposes) to see if
that makes a difference. Changing from Tree name to DNS/IP address is
fine, but if you are only doing so when the primary is down then you now
have tow thing changing when the login breaks, both the fact that one
server is down and the fact that you are specifying a different way for
iManager to find the tree itself.

> We have created drivers on both server and created an script for Driver
> failover which is constantly running at every 5 min of interval of time.
>
> I dont really get by what you mean by turnoff one that odes IDM things


Identity Manager (IDM) drivers, as you know, typically run on one machine
or another. As a result, some of the attributes for IDM driver
configuration objects (driver objects) are server-specific, meaning not
replicated at all on purpose. To show all values possible tools like IDM
Designer and iManager know to go to every server that runs driver objects
in the DriverSet and query them specifically for the server-specific data
they hold in order to display the same to the administrator. If you turn
off one of the boxes in the DriverSet, then iManager and Designer will
still try to query them, but will need to, at least, timeout the
connection attempt.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
Knowledge Partner
Knowledge Partner

Re: iManager not working

frankabhinav;2491266 wrote:
We have put iManager 3.1 and eDirectory 9.0.


Since you have posted in the eDirectory for Windows forum I presume you're installing on Windows Servers but which particular version(s)?

HTH.
0 Likes
frankabhinav Super Contributor.
Super Contributor.

Re: iManager not working

Yes we have installed on windows server 2016.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.