Table of Contents
Advertisement
Grey Headline (continued)
System configuration
Overview
The VCS provides an Event Logging facility for troubleshooting and auditing purposes. The Event Log
records information about such things as calls, registrations, and messages sent and received.
The Logging page lets you:
•
specify the Log level to set the amount of information to record
•
copy the Event Log to a Remote syslog server
To go to the Logging page:
•
System configuration > Logging
To view the Event Log using the web interface:
•
Status > Logs > Event Log
To view the Event Log using the CLI:
eventlog
•
About Event Log levels
All events have an associated level in the range 1-4, with Level 1 Events considered the most
important. The table below gives an overview of the levels assigned to different events.
See the
Events and levels
section for a complete list of all events that are logged by the
VCS, and the level at which they are logged.
Level
Assigned Events
Level 1
High-level events such as registration requests and call attempts. Easily human
readable. For example:
•
call attempt/connected/disconnected
•
registration attempt/accepted/rejected
Level 2
All Level 1 Events, plus:
•
logs of protocol messages sent and received (SIP, H.323, LDAP etc.) excluding
noisy messages such as H.460.18 keepalives and H.245 video fast-updates
Level 3
All Level 1 and Level 2 Events, plus:
•
protocol keepalives
•
call-related SIP signaling messages
Level 4
The most verbose level: all Level 1, Level 2 and Level 3 Events, plus:
•
network level SIP messages
Overview and
System
Introduction
status
configuration
D14049.07
March 2010
VCS
Zones and
Clustering and
configuration
neighbors
peers
Logging
Setting the Event Log level
You can control which events are logged by the VCS by setting the log level. All events with a level
numerically equal to and lower than the specified logging level are recorded in the Event Log. So, at
Level 1, only Level 1 events are logged; at Level 2, both Level 1 and Level 2 events are logged, and
so on. The default is 1. To set the log level:
•
System configuration > Logging
xConfiguration Log Level
•
TANDBERG does not usually recommend logging at Level 3 or Level 4 as the Event Log holds
!
a maximum of 2GB of data and logging at these levels on a busy system could cause the
Event Log to be recycled too quickly.
Changes to the Event Log level affect both the Event Log that you can view using the web
interface, and the information that is copied to the
configured.
Changes to the Event Log level are not retrospective. If you change the Event Log level, it will
only affect what is logged from that point onwards.
About remote logging
The Event Log is always stored locally on the VCS. However, it is often convenient to collect copies
of all Event Logs from various systems in a single location. A computer running a BSD-style syslog
server, as defined in
RFC 3164
[4], may be used as the central log server. Note that:
•
A VCS will not act as a central logging server for other systems.
•
Events are always logged locally (to the Event Log) regardless of whether or not remote logging is
enabled.
•
The VCS may use any of the 23 available syslog facilities for different messages. Specifically,
LOCAL0..LOCAL7 (facilities 16..23) are used by different components of the application software
on the VCS.
Enabling remote logging
To enable remote logging, you must configure the VCS with the address of the central log server to
which the Event Log will be copied. To do this:
•
System configuration > Logging
xConfiguration Log Server Address
•
Call
Bandwidth
processing
control
46
TANDBERG
VIDEO COMMUNICATION SERVER
remote log server
(if any) that you have
Firewall
Applications
Maintenance
traversal
ADMINISTRATOR GUIDE
Appendices
Advertisement
Table of Contents
