INFO: Keep Track of Events on Orbitor with Syslog

Knowledge Base
• New Search • • References • • Support •	Keep Track of Events on Orbitor with Syslog
	Article Number: I018 Article Type: Info Modified: August 6, 1999

	SUMMARY If you are managing the activities and use of an Orbitor router network, or are simply interested in maintaining an ongoing log of events of an Orbitor router, you will be interested in this feature. This article will provide an overview of the use of Syslog in an Orbitor environment. MORE INFORMATION Syslog Syslog is quite simply a contraction for System Log. Its purpose is to accept messages of any type and log them to a destination file based upon the priority and source descriptors contained within the message. Its use is wide spread but its roots are firmly planted in the UNIX-world. The Server Most often, Syslog Servers (often called daemons) will be provided by a centralized server facility. Servers whether they are UNIX-based (i.e. LINUX) or Windows NT-based can offer Syslog services that will listen for Syslog messages from various sources. In response, these servers will log the message following the rules that had been configured for that message type, priority and source. Many Syslog servers provide additional processing capabilities including monitoring for particular text/message patterns and performing an action as a result. For example, a Syslog server may be configured to send an Email message to the system administrator when the server detects the reception of a message containing security violation information. However, each server is different in its capabilities to perform such actions and their representative documentation should be consulted. The Orbitor Advantage The Orbitor product family offers the ability to log system events, call activation events, or security authentication events to a Syslog server. The use of Syslog in this capacity eliminates the event log history size of 200 messages in the Orbitor, and will allow the continous logging of events on an ongoing basis. As a logging tool, it serves to augment the management of a router network. It can be used in concert with SNMP as another form of reporting and event monitoring. However, it is not intended to replace an effective Network Management System. The use of this feature can be enabled through the Applications menu of the Orbitor. Why bother? The decision to use this capability will be based upon the operational needs of your organization. However, the cost to implement this feature is almost zero, but the benefits of traceability, call accounting, and security monitoring are all of value. A Syslog File Example Presented below is an example of a Syslog file. Note that the actual messages are what is logged in the Orbitor's Event Log. Aug 5 11:14:13 wasat syslogd: restart Aug 5 11:14:29 R1 : * Configuration saved. Aug 5 11:15:08 R1 : * Dsl 1 Activation In Progress (NT) Aug 5 11:15:08 R1 : * LAN connection established Aug 5 11:30:38 R1 : * Link 1 down Aug 5 11:30:38 R1 : * Link 1 Disconnect: 31 Normal, Unspecified Aug 5 11:30:42 R1 : * Link 1 Outgoing Data Call to 94165551212 Aug 5 11:30:44 R1 : * Link 1 Connected Aug 5 11:30:48 R1 : * Link 1 up Aug 5 11:30:48 R1 : * Link 1 attached to remote site Toronto The "R1" designator is the name of the device issuing the message, in this case the Orbitor. REFERENCES If you require additional details regarding this feature, the Orbitor Installation and Reference manual may be consulted. If you are in need of a Syslog server, there is an application from Kiwi Enterprises that should serve the purpose.§

	Keywords: Syslog, logging, activation, security Product: Orbitor Model: All
	Copyright © 1999 Develcon Electronics Ltd. All Rights Reserved.