Description |
This article describes the steps to use to verify the appliance is receiving and processing syslog in FortiGate VPN integrations.
For integration details, see FortiGate VPN Integration reference manual in the Document Library. |
Scope | Version: 8.x and greater. |
Solution |
1) Review FortiGate configuration to verify Syslog messages are configured properly.
2) Using tcpdump, confirm syslog messages are reaching the appliance when client connects. In appliance CLI type:
(Type ctrl-C to stop)
If syslog messages are not being received:
3) If syslog is reaching the appliance, enable debugs (written to /bsc/logs/output.master):
nacdebug -name FortinetVPN true
4) Have the client connect.
5) Review output.master for syslog messaging that provides User ID, assigned endstation VPN IP address, and session information.
yams.SyslogServer FINER :: 2021-11-10 15:53:31:067 :: SyslogServer received: 10.12.240.5 <190>date=2021-11-10 time=16:53:30 devname="FGT-Core" devid="FG81EPTK18005296" eventtime=1636577610467479916 tz="-0500" logid="0101039947" type="event" subtype="vpn" level="information" vd="root" logdesc="SSL VPN tunnel up" action="tunnel-up" tunneltype="ssl-tunnel" tunnelid=733830834 remip=10.12.102.18 tunnelip=172.16.196.10 user="test" group="Radius Servers" dst_host="N/A" reason="tunnel established" msg="SSL tunnel established"
Key information in other syslog messages received:
subtype=”vpn”
Example of FortinetVPNdebug successful output
yams INFO :: 2021-11-10 15:53:31:080 :: parseStr parsed FG81EPTK18005296 <-- FortiGate ID
Contact Support for further assistance. Open a support ticket and provide the following:
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.