."This file created Dec 2011
.TH LOGV l "December 2011" " " "High Availability Platform Commands"
.SH NAME
logv \- merge and edit (vi) the various log files in the system
.br
logc \- merge and output (cat) the various log files in the system
to standard out
.br
logw \- watch the requested log file 
.SH SYNOPSIS
.B logv \fI[OPTIONS]... [LOGS...] [-t TIME]... [[-a]FILTERS]...\fR
.br
.B logc \fI[OPTIONS]... [LOGS...] [-t TIME]... [[-a]FILTERS]...\fR
.br
.B logw \fI[OPTIONS]... [LOG] [[-a]FILTERS]...\fR
.br
.sp
.B logv \fI[-?]\fR
.br
.B logc \fI[-?]\fR
.br
.B logw \fI[-?]\fR
.br
.SH DESCRIPTION
.PP
These commands merge and display the various log files in the system.
The logv command allows the user to edit (vi) the specified logs.
The logc command allows the user to cat the specified logs to standard out.
The logw command allows the user to watch the specified log.
.PP
.sp
\fIOPTIONS\fR to modify command operations:
.TP
\fI-?\fR
print a help message and exit
.TP
\fI-v\fR
show the version of the command
.sp
.TP
\fI-c\fR
cat the log (automatically set if called with logc)
.TP
\fI-ls\fR
list the names and sizes of log files
.TP
\fI-w\fR
watch the log (automatically set if called with logw)
.sp
.TP
\fI-b\fR
remove blank lines
.TP
\fI-d\fR
augment timestamps with time delta between entries displayed
.TP
\fI--dsep[N]\fR
output a separator line when delta between entries is greater than N seconds.
The default is one second.
.TP
\fI-g\fR
assume application filters are grep patterns instead of appnames.
Appnames are usually within the application field of the log output,
while grep patterns can be anywhere.
.TP
\fI-l\fR
only the latest file in the log is searched.
Default is all files or files or files specified by time filter.
.TP
\fI-r\fR
reverse order (latest entry is show first)
.TP
\fI-s\fR
strip off the timestamp (and other header) from each line
.TP
\fI-st\fR
strip off other header (leaving timestamp) from each line
.sp
.TP
\fI--views\fR
List the predefined log views.  A view is a shorthand for a log type
(or set of log types) as well as patterns to match in the logs.
.TP
\fI--view VIEWNAME\fR
Display the log using the log types and grep patterns associated with
view \fIVIEWNAME\fR.  See the section below for an explanation of
the built-in VIEWs.
.sp
.TP
\fI-ld dir\fR
look for log files in the directory \fIdir\fR (instead of the default).
Allows copying log files elsewhere (even to a different system) and
using logv to merge and filter them.
.TP
\fI-lf file\fR
.TP
Assume that \fIfile\fR is a log file and read input from it.
Multiple -lf flags can be given.
\fI-clear\fR
clear the log files (with the logclear command)
.sp
.PP
\fILOGS\fR that can be displayed.
Multiple logs can be given.
Logs are merged and sorted by time.
.br
.TP
\fIall\fR
all possible
.br
.TP
\fIlm\fR
Log manager debug trace (default)
.br
Provides information about Communication Manager and High Availability
Platform software such as restarts, initializations, and shutdowns, 
duplication status, process errors, system alarms, and communication
with external gateways and port networks.
The log rolls over when it reaches its size limit.
.TP
\fIlxboot\fR
Linux boot messages
.br
.TP
\fIlxcron\fR
Linux scheduled task log (CRON).
.br
Shows information from the Linux scheduling daemon.
.TP
\fIlxsys\fR
Linux syslog
.br
Collects all the system messages produced by the various subsystems
(proceses) running on Linux.
.TP
\fIlxkern\fR
Linux kernel log
.br
Collects all the kernel messages produced by the Linux Kernel
.TP
\fIlxsec\fR
Linux access security log
.br
Information about logon connections to the Linux system.
Actions logged in this file include opening or closing a
telnet session and modem messages.
.TP
\fIlxwtmp\fR
Linux login/logout/reboot log
.br
Shows information about Linux logon and logout procedures, as well as
system reboots.
.TP
\fIlxxfer\fR
Linux file transfer log
.br
Contains information about files copied to or retrieved from the system.
It indicates, among other things, the time, user, and files that were copied
to or retrieved from the system.
.TP
\fIwd\fR
watchdog logs
.br
Only the watchdog process writes to this log. It contains information about application starts, restarts, failures, shutdowns, heartbeating, and Linux reboots. It also contains information about processes that use excessive CPU cycles. 
.br
The watchdog logs do not contain much specific information about Avaya Communication Manager. If you need information about processes relating to call processing, view the logmanager debug trace log. 
.TP
\fIcmds\fR
platform command history log
.br
High Availability Platform commands are logged to this file.
These are the commands that modify the server administration or status.
For all the shell commands executed on the system see the "lxsys" log
or the "bashhist" view.
.TP
\fIhttperr\fR
HTTP/web server error log
.br
These are errors and events generated by the platform web server and
include items like web server restart, abnormal CGI script file terminations,
and certificate mismatches.
.TP
\fIhttpssl\fR
HTTP/web secure sockets layer (SSL) request log
.br
These are all the requests made of the web servers SSL module.
All pages requested or placed in secure mode are indicated.
.TP
\fIhttpaccess\fR
HTTP/web access log
.br
These are all the files that have been accessed by the web server.
.TP
\fIcmrestart\fR
Communication Manager restart log
.br
The last 16 restarts of the Communication Manager application including the 
level, why they were requested and if they were escalated are in this log.
.TP
\fIfilesync\fR
Communication Manager file synchronization log
.br
Description of file synchronization sessions between main CM server and
other survivable servers.
.PP
.br
.sp
\fIFILTERS\fR to display events matching a particular criteria (Multiple
apps and times can be given):
.br
.TP
\fI-t time-pattern\fR
filter events for a particular date/time pattern (e.g.,
[yyyy[mm[dd]]][:HH[MM[SS[mmm]]]],
or with today or yesterday before the :).
For example, all values for entries in the month of May 2005 can be
matched with the pattern 200505.
If the date part is not specified then today is assumed, so :15 would
show all entries for the 3pm hour of the current day.
Multiple time-patterns can be given.
Entries that match any of the time-patterns will be output.
.br
.TP
\fI-t time-range\fR
filter events for a particular date/time range (e.g.,
[[[[yyyy]mm]]dd][:HH[MM[SS]]]-[[[[yyyy]mm]]dd][:HH[MM[SS]]]
or with today or yesterday before the :).
Entries that match the time between the two specified times
(inclusive) will be output.
Any part of the date not specified is assumed to match today
(e.g. if the current date is 20050518 and 12 was specified for the date
then 20050512 would be assumed, consequently if no date is specified the
date is assumed to be today).
Any part of the time not specified is assumed to be 0.
Note that this is different from the time-pattern format above.
Also the format -time will match all values that occured at or
before the specified time and time- will match all values that
occured at or after the specified time.
Multiple time-ranges can be given.
Entries within any time-range will be output.
.br
.TP
\fIapp\fR
filter events for a particular application/process (e.g., VFM, audit, NW, ...).
These appear in the fourth : separated field of the debug trace log.
.br
.TP
\fI-a\fR
normally any match is displayed.
Filters following a -a are applied to the output of those preceding the -a.
.br
Filters following a -a are always considered to be grep patterns (and not
application names).
.PP
.SH "DIAGNOSTICS"
The following diagnostics may be issued on stderr:
.sp
Nothing to view:
.in +1.0
.br
an invalid option was entered or the matching criteria was not satisfied.
.in
.br
.SH "FILES"
NOTE: The following is an example of where to configure views. 
They do not actually exist unless explicitly created by the Administrator. 
If created, they will be used.

/etc/opt/ecs/logview.conf \- view definition configuration file
.br
/etc/opt/ecs/logview.d \- directory containing view definition files
.P
View definitions consist of single lines with three tab-separated fields.  
The first field is the view name.
The second is the log-name and grep-pattern separated by a '|'.
The third field is the view description.
.SH "VIEWS"
.P
In addition to views that can be defined by placing entries in the logview* files, the following are built-in:
.br
.TP
\fIipevt\fR
List IP events posted by Communication Manager.  These include when IP 
interfaces go in and out of service (IF_UP/IF_DOWN) and when IP telephones
and softphones register and unregister (IPT_REG/IPT_UNREG).
.TP
\(bu
For IF_UP/IF_DOWN the following fields are displayed:
.RS
.IP \fBboard=\fR 8
The board that came in or went out of service.
This is either the port network, carrier, and slot or \fBPROCR\fR for the
control processor IP interface.
.IP \fBip=\fR 8
The IP address of the interface.
.IP \fBnet_reg=\fR  8
The network region in which the interface resides
.IP \fBtype=\fR 8
The type of interface:
.RS
.IP PROCR 8
(again) the control processor IP interface
.IP CLAN 8
a Control Lan circuit pack
.IP MEDPRO 8
a Media Processor circuit pack
.IP VAL 8
a Voice Announcement over the LAN circuit pack
.RE
.IP \fBreason=\fR 8
The embarrassingly obtuse sets of reasons for these events are:
.RS
.IP \fBinitialized\fR 8
The PROCR interface came up normally.
.IP \fBresponded\fR 8
The CLAN or VAL interface came up normally or were released from busyout state.
.IP \fBins\fR 8
The MEDPRO came into service initially or was released from busyout.
.IP \fBrelease\fR 8
The PROCR
was manually released from busyout state.
.IP \fBcfg-change\fR 8
The configuration of the PROCR interface was changed and it's
coming back into service.
.IP \fBconfig-chg\fR 8
The configuration of the CLAN or VAL interface was changed and it's
coming back into service.
.IP \fBsigrestore\fR 8
The CLAN or VAL regained their Ethernet signal.
.IP \fBsigloss\fR 8
The CLAN or VAL lost their Ethernet signal.
.IP \fBintfailure\fR 8
The CLAN or VAL failed or could not be contacted (e.g. because the cabinet that 
it was in failed or the board was removed).
.IP \fBdisable-or-fail\fR 8
The MEDPRO 
was manually disabled or failed in some strange way.
.IP \fBoos\fR 8
The MEDPRO 
was manually busied out or placed out of service automatically.
.IP \fBbusyout\fR 8
The CLAN, VAL, or PROCR
was manually busied out or placed out of service automatically.
.RE
.RE
.TP
\(bu
For IPT_REG and IPT_UNREG:
.RS
.IP \fBboard=\fR 8
The board on which the registration occured.
.IP \fBip=\fR 8
The IP address of the interface.
.IP \fBnet_reg=\fR  8
The network region in which the interface resides
.IP \fBext=\fR 8
The extension for which the phone registered.
.IP \fBip=\fR 8
(the second one)
The IP address of the phone that registered.
.IP \fBnet_reg=\fR 8
(the second one)
The network region in which the phone resides.
.IP \fBreason=\fR 8
The reason for the event:
.RS
.IP \fInumber\fR 8
The denial event code for the (usually forced) unregistration.
These are the same codes available through the Communication 
Manager administration interface (SAT) command: "disp events".
There a brief explanation of the code is also displayed.
See the Communication Manager Maintenance Manual for a listing 
of these codes.
.IP \fBnormal\fR 8
A normal, logon registration.
.IP \fBrecovery\fR 8
A reregistration recovering from an unexpected link disconnect.
.IP \fBunnamed\fR 8
An unnamed registration normally coming from an R300 station.
.IP \fBmove-user\fR 8
A registration taking over another phone.  This is usually a
softphone taking over a non-IP telephone's extenstion.
.IP \fBdual-con\fR 8
An older softphone registration.  Should never occur.  If it does,
go out and buy a lottery ticket.
.IP \fBunknown\fINNNNN\fR 8
An unexpected registration type number \fINNNNN\fR.
.RE
.RE
.br
.TP
\fIbashhist\fR
The list of commands run by interactive bash shells.
The fields:
.RS
.IP PPID= 8
The process ID of the parent of the shell.
.IP PID= 8
The process ID of the shell.
.IP UID= 8
The user ID under which the shell is executing.  0 means root or super user.
.IP command 8
All fields following the UID= are the actual command line that was executed.
.RE
.br
.TP
\fImst\fR
If enabled via a SAT command, entries to the Communication Manager's
message sequence trace (MST) log can be echoed into the debug trace
log as well in (a somewhat) human readable form.
The fields are the raw hex bytes of the MST log entry.
(There really are a few humans who can read this, but it is mainly for
shipping off for deciphering by a tool).
.br
.TP
\fIhwerr\fR
The events that go into the Communication Manager's hardware error
and alarm logs.
This needs special deciphering by an external tool.
.br
.TP
\fIsat\fR
The System Administration and Maintenance activities performed on the 
Communication Manager's (CM) System Access Terminal (SAT)
.br
.TP
\fIswerr\fR
The events that go into the Communication Manager's software error log.
This needs special deciphering by an external tool.
.br
.TP
\fIdenial\fR
The denial events that go into the Communication Manager's software log.
Text descriptions of denial events are added in the output.
.SH "SEE ALSO"
.B logclear(1), logfilter(1), logecho(1)
