Cabletron Systems CSX1000 Manual Do Utilizador
USER’S GUIDE
340 CyberSWITCH
files and devices depending upon its configuration. Refer to your UNIX system documentation for
more information on syslogd.
more information on syslogd.
Each log message sent to a syslogd server has a priority tag associated with it. The priority tag is
encoded as a combination: facility.level. The facility identifies the part of the system creating the
log message and the level describes the severity of the condition which caused the log message to
be written.
encoded as a combination: facility.level. The facility identifies the part of the system creating the
log message and the level describes the severity of the condition which caused the log message to
be written.
When sending a log message to a Syslog Server, the message is formatted as an ASCII string with
the first item in the string being the syslog priority enclosed in angle brackets. The priority is
presented as a decimal value, not a hexadecimal value. For example, to log the string “CDR
VERIFY” with a priority of authentication.info, the priority (26 hex) would be converted to 38
decimal and the syslog server would be sent the string “<38> CDR VERIFY”. The Syslog daemon
will use the priority of 38 (26 hex) to determine where the message should be sent or stored. The
string “CDR VERIFY” will then be sent to that destination.
the first item in the string being the syslog priority enclosed in angle brackets. The priority is
presented as a decimal value, not a hexadecimal value. For example, to log the string “CDR
VERIFY” with a priority of authentication.info, the priority (26 hex) would be converted to 38
decimal and the syslog server would be sent the string “<38> CDR VERIFY”. The Syslog daemon
will use the priority of 38 (26 hex) to determine where the message should be sent or stored. The
string “CDR VERIFY” will then be sent to that destination.
The priority tag is implemented as an 8 bit hexadecimal integer. The low order three bits contain
the severity level; the high order 5 bits contain the facility. Thus, for a convenient example, level
info is encoded as the value 6 and facility authentication is encoded as the value 4 (in BSD UNIX
v4.3). These two fields are combined as follows:
•
the severity level; the high order 5 bits contain the facility. Thus, for a convenient example, level
info is encoded as the value 6 and facility authentication is encoded as the value 4 (in BSD UNIX
v4.3). These two fields are combined as follows:
•
level ‘6’
=> 06 hex
•
facility ‘4’ shifted left 3 bits to use the high order 5 bits
=> 20 hex
•
bitwise OR the two values together
=> 26 hex
In result, priority of authentication.info is encoded as 26 hex.
Note:
Because the values for both the facilities and the severity levels may vary from one version
of UNIX to the next, the system allows you to set the entire priority value as an integer. This
integer will be prepended to all messages sent to the Syslog Server.
of UNIX to the next, the system allows you to set the entire priority value as an integer. This
integer will be prepended to all messages sent to the Syslog Server.
One of the sources from which syslogd accepts log messages is UDP port 514. This is the access
point that the system’s CDR subsystem uses when logging to a syslog server. It sends its log
messages to UDP port 514 at the server’s IP address.
point that the system’s CDR subsystem uses when logging to a syslog server. It sends its log
messages to UDP port 514 at the server’s IP address.
Syslog Servers use UDP which is a datagram service. When a datagram is sent to a Syslog Server,
there is no acknowledgment that the datagram was properly received. To reduce the possibility of
lost data, two Syslog Servers may be used. The two resulting log files can be compared to detect
missing data in one or the other.
there is no acknowledgment that the datagram was properly received. To reduce the possibility of
lost data, two Syslog Servers may be used. The two resulting log files can be compared to detect
missing data in one or the other.
CDR L
OG
R
EPORT
O
VERVIEW
This option allows you select the storage destination of your CDR log reports. You may send the
CDR log reports to the local log, or to a previously configured offnode Syslog Server(s). A total of
three destinations may be selected. For example, you could select the local log, and two previously
configured Syslog Servers for your CDR log reports’ destinations.
CDR log reports to the local log, or to a previously configured offnode Syslog Server(s). A total of
three destinations may be selected. For example, you could select the local log, and two previously
configured Syslog Servers for your CDR log reports’ destinations.
Storage on the local log is not recommended for production use; it is intended primarily for
diagnostic use. This is because the local log only retains a fixed number of log entries. Once the file
is full, each new entry overwrites the oldest entry. This will not give you a complete CDR Log.
diagnostic use. This is because the local log only retains a fixed number of log entries. Once the file
is full, each new entry overwrites the oldest entry. This will not give you a complete CDR Log.
CDR reports sent to the local file can be written to disk by issuing the
log cdr write
command.
The file is the written to the \LOG directory. The file name is CDR_LOG. The file extensions are .1,