User-ID in multiple vsys failing for vsys2

Reply
Highlighted
L4 Transporter

User-ID in multiple vsys failing for vsys2

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.

 

Server: dc(vsys: vsys2) (job 65118073)
Host: 172.16.2.2
num of log query made : 51
num of log query failed : 0
num of log read : 22995
last record timestamp : 1576001375
last record time : 20191210180935.604110-000

 

We are also using redistribution and the agents for that also show amber in GUI.

 

Agent: BR220(vsys: vsys2) Host: 10.1.4.11(10.1.4.11):5007
Status : conn:Get IPs

Highlighted
L7 Applicator

Re: User-ID in multiple vsys failing for vsys2

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

reaper - PANgurus.com
I drink and I know things
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!