https://live.paloaltonetworks.com/t5/general-topics/user-id-in-multiple-vsys-failing-for-vsys2/m-p/303172#M78936 <P>If both vsys are polling the same DC, I would recommend using the client (instead of clientless) so your firewall doesnt need to bombard the DC with duplicate reads</P> Wed, 11 Dec 2019 12:32:56 GMT reaper 2019-12-11T12:32:56Z https://live.paloaltonetworks.com/t5/general-topics/user-id-in-multiple-vsys-failing-for-vsys2/m-p/302962#M78905 <P>Both vsys1 and vsys2 are using same agentless settings and are accessing same DC servers. While vsys1 shows as connected vsys2 shows nothing under status and system logs show 'connect-server-monitor-failure'. I have rechecked password in both vsys but that doesn't seem to be the issue. or is the issue just cosmetic in GUI.</P><P>&nbsp;</P><P>Server: dc(vsys: vsys2) (job 65118073)<BR />Host: 172.16.2.2<BR />num of log query made : 51<BR />num of log query failed : 0<BR />num of log read : 22995<BR />last record timestamp : 1576001375<BR />last record time : 20191210180935.604110-000</P><P>&nbsp;</P><P>We are also using redistribution and the agents for that also show amber in GUI.</P><P>&nbsp;</P><P>Agent: BR220(vsys: vsys2) Host: 10.1.4.11(10.1.4.11):5007<BR />Status : conn:Get IPs</P> Tue, 10 Dec 2019 18:35:15 GMT https://live.paloaltonetworks.com/t5/general-topics/user-id-in-multiple-vsys-failing-for-vsys2/m-p/302962#M78905 raji_toor 2019-12-10T18:35:15Z https://live.paloaltonetworks.com/t5/general-topics/user-id-in-multiple-vsys-failing-for-vsys2/m-p/303172#M78936 <P>If both vsys are polling the same DC, I would recommend using the client (instead of clientless) so your firewall doesnt need to bombard the DC with duplicate reads</P> Wed, 11 Dec 2019 12:32:56 GMT https://live.paloaltonetworks.com/t5/general-topics/user-id-in-multiple-vsys-failing-for-vsys2/m-p/303172#M78936 reaper 2019-12-11T12:32:56Z