sviridov_a_m Absent Member.
Absent Member.
323 views

Syslog collecting problem. S-terra CSP VPN Gate

Jump to solution

Hi, all

There is following problem:

Our device S-terra CSP VPN Gate 3000 does not support the ability to send syslog messages to 2 directions. Only local OR external syslog server. It is not safe. Because we lose all logs in case of rupture of the connection between the Syslog Daemon placed on ConAPP and the device .

S-terra based on CentOS 5.3

log file placed in /var/log/cspvpngate.log

I ask u for advice and suggestions

Maybe I have to look at flex-connector? but what kind of flex-connector to choose?

thanks

regards

Labels (3)
0 Likes
1 Solution

Accepted Solutions
novakm92 Super Contributor.
Super Contributor.

Re: Syslog collecting problem. S-terra CSP VPN Gate

Jump to solution

You can log everything on local server and configure local syslog/rsyslog to forward messages to remote syslog (ConApp).

Just add:

facility.priority @192.168.1.1:514

to your syslog/rsyslog config file and replace facility, priority, IP address and optionally port. This way, everything with matching facility and priority will be forwarded to given IP address over UDP (you can also use @@ for TCP).

View solution in original post

0 Likes
2 Replies
novakm92 Super Contributor.
Super Contributor.

Re: Syslog collecting problem. S-terra CSP VPN Gate

Jump to solution

You can log everything on local server and configure local syslog/rsyslog to forward messages to remote syslog (ConApp).

Just add:

facility.priority @192.168.1.1:514

to your syslog/rsyslog config file and replace facility, priority, IP address and optionally port. This way, everything with matching facility and priority will be forwarded to given IP address over UDP (you can also use @@ for TCP).

View solution in original post

0 Likes
sviridov_a_m Absent Member.
Absent Member.

Re: Syslog collecting problem. S-terra CSP VPN Gate

Jump to solution

thank u, Michal

it works.

regards

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.