RuggedCom RS400 Configuring Local Syslog, Administration Dhcp Client Ports, Default Debugging

Models: RS400

1 275
Download 275 pages 11.85 Kb
Page 49
Image 49

Administration

DHCP Client Ports

Synopsis: Any combination of numbers valid for this parameter

Default: None

This parameter specifies ports where DHCP clients are connected.

Examples:

All - all ports of the switch can have DHCP clients connected.

2,4-6,8 - ports 2,4,5,6 and 8 can have DHCP clients connected

1.15 Syslog

The syslog provides users the ability to configure local syslog and remote syslog. The remote syslog protocol, defined in RFC 3164, provides a UDP/IP based transport to allow a device to send event notification messages across IP networks to event message collectors, also known as syslog servers. The protocol is simply designed to transport these event messages from the generating device to the collector.

Syslog client resides in ROSTM and supports up to 5 collectors (syslog servers). The ROSTM Remote Syslog provides the ability to configure:

IP address(es) of collector(s)

Source UDP port

Destination UDP port per collector

Syslog source facility ID per collector (same value for all ROSTM modules)

Filtering severity level per collector (in case different collectors are interested in syslog reports with different severity levels)

1.15.1Configuring Local Syslog

The local syslog configuration enables users to control what level of syslog information will be logged. Only the messages with higher than or equal to the configured severity level are written to the syslog.txt file in the unit.

Figure 25: Local Syslog Form

Local Syslog Level

Synopsis: { EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, NOTICE, INFORMATION

AL, DEBUGGING }

Default: DEBUGGING

RS400

49

ROS™ v3.5

Page 49
Image 49
RuggedCom RS400 Configuring Local Syslog, Administration Dhcp Client Ports, Local Syslog Level, Default Debugging