03-07-2025 12:52 AM
Hi Cisco Community, may I ask for your expertise please. I configured this syslog command from the CLI. When I checked, it is sending logs to our external syslog server, however, only one log message was logged to our external syslog server.
vmanage(config)#system logging server 172.16.30.100 transport udp port 14514 vpn 512 source-interface eth0
vmanage(config)#commit
vmanage-1#show running-config system
logging
disk
enable
!
server 172.16.30.100
vpn 512
source-interface eth0
transport udp
port 14514
exit
!
Is there any other configuration I need to do here? TIA!
03-07-2025 07:06 AM
Hello @Sors
Based on the configuration you provided, the syslog server is configured correctly to send logs to the external syslog server at 172.16.30.100
using UDP on port 14514
from VPN 512
and the eth0
interface. However, if only one log message is being sent to the external syslog server, there are a few things you should check to ensure everything is working as expected:
vmanage(config)#system logging server 172.16.30.100 level info
vmanage(config)#commit
This ensures that logs with a severity level of info
and higher (e.g., warnings, errors) are sent to the syslog server.vmanage(config)#system logging enable
vmanage(config)#commit
512
is properly configured and has connectivity to the syslog server (172.16.30.100
). You can test connectivity using a ping command:
vmanage#ping vpn 512 172.16.30.100
512
and ensure that the syslog server is reachable.eth0
. Ensure that eth0
is part of VPN 512
and has an IP address assigned. You can verify this with:
vmanage#show interface vpn 512
eth0
is not part of VPN 512
or does not have an IP address, update the configuration accordingly.172.16.30.100
) is properly configured to receive logs on UDP port 14514
. Ensure that there are no firewall rules or network issues blocking the logs.vmanage#request system logging generate level info message "Test log message"
vmanage#show log
vmanage#show configuration committed
If everything checks out, you may need to add or verify the following commands:
vmanage(config)#system logging enable
vmanage(config)#system logging server 172.16.30.100 level info
vmanage(config)#commit
After making these changes, test again to see if logs are being sent to the external syslog server. If the issue persists, check the syslog server configuration and network connectivity.
Hope This Helps!!!
AshSe
Community Etiquette:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide