NetScaler Console service

Configuring syslog on instances

June 6, 2024

Contributed by:

C P

The syslog protocol provides a transport to allow the NetScaler instances to send event notification messages to NetScaler Console, which is configured as a collector or the syslog server for these messages.

You can monitor the syslog events generated on your NetScaler instances if you have configured your device to redirect all syslog messages to NetScaler Console. To monitor syslog events, you need to first configure NetScaler Console as the syslog server for your NetScaler instance. After the instance is configured, all the syslog messages are redirected to NetScaler Console, so that these logs can be displayed to the user in a structured manner.

Syslog uses the User Datagram Protocol (UDP), port 514, for communication, and because UDP is a connectionless protocol it does not provide any acknowledgment back to the instances. The syslog packet size is limited to 1024 bytes and carries the following information:

Facility
Severity
Host name
Timestamp
Message

In NetScaler Console, you must configure facility and log severity levels on the instances.

Facility - Syslog messages are broadly categorized on the basis of the sources that generate them. These sources can be the operating system, the process, or an application. These categories are called facilities and are represented by integers. For example, 0 is used by kernel messages, 1 is used by user-level messages, 2 is used by the mail system, and so on. The local use facilities (from local0 to local7) are not reserved and are available for general use. Hence, the processes and applications that do not have pre-assigned facility values can be directed to any of the eight local use facilities.

Severity - The source or facility that generates the syslog message also specifies the severity of the message using a single-digit integer, as shown below:

- Emergency: System is unusable.

- Alert: Action must be taken immediately.

- Critical: Critical conditions.

- Error: Error conditions.

- Warning: Warning conditions.

- Notice: Normal but significant condition.

- Informational: Informational messages.

- Debug: Debug-level messages.

To configure syslog on NetScaler instances:

In NetScaler Console, navigate to Infrastructure > Instances.
Select the NetScaler instance from which you want the syslog messages to be collected and displayed in NetScaler Console.
In the Action drop-down list, select Configure Syslog.
Click Enable.
In the Facility drop-down list, select a local or user-level facility.
Select the required log level for the syslog messages.
Click OK.

This configures all the syslog commands in the NetScaler instance, and NetScaler Console starts receiving the syslog messages. You can view the messages by navigating to Infrastructure > Events > Syslog Messages.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Configuring syslog on instances

June 6, 2024

Contributed by:

C P

June 6, 2024

Contributed by:

C P

Configuring syslog on instances

In this article