have you tried registering AIX server? we're able to configure syslog setting but AIX still not sending logs to Fortisiem.
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hi,
The IBM AIX server can be integrated via syslog , ssh and snmp.
If syslogs are not reaching Fortisiem then it has to be checked on end device or network.
You can take a packet capture to verify:
Collect a tcpdump on the FortiSiem using below commands (Leave it for 5mins) :
# tcpdump -i any "host x.x.x.x" -vvv -w AIXserver.pcap //x.x.x.x --- is the server IP . Export the pcap and review.
Documentation Link:
Hi,
The IBM AIX server can be integrated via syslog , ssh and snmp.
If syslogs are not reaching Fortisiem then it has to be checked on end device or network.
You can take a packet capture to verify:
Collect a tcpdump on the FortiSiem using below commands (Leave it for 5mins) :
# tcpdump -i any "host x.x.x.x" -vvv -w AIXserver.pcap //x.x.x.x --- is the server IP . Export the pcap and review.
Documentation Link:
using the tcpdump command aix is not sending logs to the siem. any ideas what can be checked on the end device? since the syslog config is pretty straightforward (*.* @IPadd)
Is there any other sides that can be look into?
Hi @plip ,
If there are no traffic in tcpdump then it is network layer issue and further probe should be done via firewall or in network. You can also try traceroute to the SIEM from end device.
Welcome to your new Fortinet Community!
You'll find your previous forum posts under "Forums"
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.