Identity Agent - a few issues

[Alex_Shpilman]

We deployed an Identity Agent  to all the domain machines from SCCM.

There is a VSX cluster in the environment, the agent connects to the active member of VS0 (active on member a) and identities are shared to a different VS which is active on member b.

There are about 1700 clients and running R80.20 HFA73.

A while after the deployment e started to experience a memory leak on member a, 100% of the memory is being consumed and memory allocation errors being observed, only a reboot helps and then the issue comes back after a week or so.

We have an SR for that without much progress so far, perhaps someone experienced the same issue?

Another question, is that possible to suppress any pop-ups of the agent?

The users are quite annoyed with this as they confuse it with the VPN client.

Thanks.

[PhoneBoy]

The memory leak issue definitely needs to be debugged by the TAC.

@Royi_Priov any advice on suppressing popups by the Identity Agent?

[Royi_Priov]

Hi @Alex_Shpilman 

• Memory leak in which process?
• pop-up suppress - we can develop it via RFE (contact your local office for that). which pop up you want to drop? 

Thanks,

Royi.

[Alex_Shpilman]

Hi Royi,

The memory consumption of the process fwk2_dev keeps growing all the time,

The VSX is configured with VSLS and VS2 is standby on the VSX primary cluster member.

I am not sure this is caused by the identity agent but the timing points to when it was deployed.

I'd like to suppress the "connected" and "disconnected" balloon pop-ups, basically keep the agent totally client and not visible to end-users.

RFE will be submitted tomorrow.

Thanks.

[Royi_Priov]

Hi Alex,

Identity Agent directly affects pdpd (the server side for the agents communication) and vpnd for ssl negotiation with the agents.

I suggest to proceed with TAC as I don't see a direct relation.

Thanks,

Royi.