> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/products/tmedia/maintenance/800-series-maintenance-guide/centos7-rsyslog-redirect.md).

# rsyslog redirect

This procedure sends successful and failed login attempts to the TMG unit sent to an external syslog server using rsyslog.

### Notes

The default UDP port for the syslog server is 514. Change the hostname of the syslog server accordingly. In the procedure below, the hostname if the syslog server is : *lab\_syslog\_server* .\
This procedure works for a standalone system.

### Procedure For Syslog redirect

Connect to SSH interface: [Connect to SSH](/other-pages/operations/accessing-device.md)

#### Add information to send to remote syslog

For successful/failed login, messages and cron info, do this command:

`echo -e "\n#Send to remote syslog\nauthpriv.*;*.info;cron.* @lab_syslog_server\n" >> /etc/rsyslog.conf`

Then restart the rsyslog service:

`systemctl restart rsyslog`

If server hostname (lab\_syslog\_server) is unreachable, edit the hosts file:

`cat /etc/hosts`

And add this line to the file:

`[IP of syslog server] lab_syslog_server`\
`e.g. 192.168.77.88 lab_syslog_server`

#### Test the process

Tail the file on the syslog server and access the unit with SSH:

`tail -f /var/log/secure`

you will see something like this:

`Jan 4 15:42:11 192.168.101.170 HOSTOSIRIS sshd[3867]: Accepted password for root from 204.23.12.53 port 26149 ssh2`

**Default log files**

By default, access information will be sent to this file on the syslog server:

`tail -f /var/log/secure`

and system messages will be sent to this file:

`tail -f /var/log/messages`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tmediadocs.telcobridges.com/products/tmedia/maintenance/800-series-maintenance-guide/centos7-rsyslog-redirect.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.