--- title: "Brocade VRouter configuration" slug: "brocade-vrouter-configuration-1" tags: ["Reference", "Helix Enterprise", "Sec Ops and Analytics"] updated: 2026-08-07T17:37:46Z published: 2026-09-05T14:07:18Z canonical: "docs.trellix.com/brocade-vrouter-configuration-1" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Brocade VRouter configuration The vRouter uses the standard Linux syslogd process to allow the logging capabilities of most vRouter processes. > [!NOTE] > Note > > Log messages are stored in `/var/log/messages`. When the file size reaches 500 KB, the `messages` file is renamed to `messages.#`, with `#` being an incremental number. Use the `show log` command to view logs. You can use the following versions of this command to view the active log file. - `show log` - `show log | match <string>` - `show log | more` - `show log all` - `show log tail` - `show log vpn ipsec` To send logs from Brocade vRouter to the Comm Broker using syslog: - Use a single command string with the `<destination>` variable to configure different custom logging scenarios, such as location, file name, and user. The command syntax follows: ``` set system syslog facility level ``` The following example uses `host` as the logging destination (your Trellix Comm Broker Sender), `local3` as the facility, and `info` as the logging level. ``` set system syslog host 10.176.10.10 facility local3 level info ```