we have been trying for some time now to get our msm765 syslog to be read by our pa500 / user agent. we want to use RADIUS authentication on our MSM765 controller and for the agent to read the user to IP mapping. however we have the following issue. our syslog filter looks like this our raw syslog string is 02/20/15 13:17:36:568[Debug 372]: Syslog: Msg is '<143>iprulesmgr: Received RADIUS Access Accept (id='13') for user (nas-port='1',name='sy',calling-station-id='F4-09-D8-6F-73-62',framed-ip-address='172.16.32.7').' when we view the useragent log we see the following 02/20/15 13:17:36:568[Debug 137]: Found Syslog Server (msm76501), address is (172.16.40.3) 02/20/15 13:17:36:568[Debug 372]: Syslog: Msg is '<143>iprulesmgr: Received RADIUS Access Accept (id='13') for user (nas-port='1',name='sy',calling-station-id='F4-09-D8-6F-73-62',framed-ip-address='172.16.32.7').' 02/20/15 13:17:36:568[Debug 454]: Syslog: Discovered User ('sy'), Address ('172.16.32.7').) in tId (6088) <<<<<<this information must be coming from the palo agent as it does not appear in the raw syslog 02/20/15 13:17:36:568[Debug 149]: UserIpMap: '172.16.32.7'). is not a valid IP. any ideas? we are on the latest agent / pa firmware. we are only doing it this way as the agent refuses to match 4624 events direct from the RADIUS server windows event log (reads these on all our other DC agents without issue. .
... View more