Excessive Port errors, CRC errors, or Retransmissions can degrade the effective speed of the connection.
Port errors and CRC errors may be caused by a failure of the system to keep up with the incoming traffic rate. Try setting up the port to use Hardware Flow Control. If port errors persist, try lowering the Maximum Speed setting. A malfunctioning port may also cause these errors.
Retransmissions may be caused by Port or CRC errors. They may also be caused by the remote end of the connection experiencing Port or CRC errors.
PortErrors
CRCErrors
ReXmts
0S0E
Categori_zeK
_Edit Document
Send Docu_ment
_Forward
_Move To Folder...
_Remove From FolderK
O=Lotus Notes
O=Lotus Notes
PURSAFO
|.:#U
O=Lotus Notes
CN=Lotus Notes Template Development/O=Lotus Notes
PURSAFO
Fde!f^^
$Author
$TITLE
$INFO
$WINDOWTITLE
$$ScriptName
StartTime
FinishTime
CallStatus
ElapsedTime
KBytesXmt
KBytesRcvd
PortErrors
CRCErrors
ReXmts
$BODY
$ACTIONS
Phone Call Log Entry
Phone Call - Incoming
Rob Slapikoff-Rob
IncomingCall
Server
StartTime
FinishTime
CallStatus
Remote Server or User:
RemoteServer
Network Port:
Elapsed Time:
FinishTimeh
FinishTime
StartTime
(Unknown)
ElapsedTime
minutes
Port Baud Rate:
PortSpeed
Carrier Baud Rate:
CarrierSpeed
Traffic:
BytesXmt
KBytesXmt
KBytes sent
BytesRcvd
KBytesRcvd
KBytes received
Errors:
PortErrors
Port errors
CRCErrors
Received CRC errors
ReXmts
Retransmissions
PortErrors
CRCErrors
ReXmts
0S0E
Excessive Port errors, CRC errors, or Retransmissions can degrade the effective speed of the connection.
Port errors and CRC errors may be caused by a failure of the system to keep up with the incoming traffic rate. Try setting up the port to use Hardware Flow Control. If port errors persist, try lowering the Maximum Speed setting. A malfunctioning port may also cause these errors.
Retransmissions may be caused by Port or CRC errors. They may also be caused by the remote end of the connection experiencing Port or CRC errors.
Excessive Port errors, CRC errors, or Retransmissions can degrade the effective speed of the connection.
Port errors and CRC errors may be caused by a failure of the system to keep up with the incoming traffic rate. Try setting up the port to use Hardware Flow Control. If port errors persist, try lowering the Maximum Speed setting. A malfunctioning port may also cause these errors.
Retransmissions may be caused by Port or CRC errors. They may also be caused by the remote end of the connection experiencing Port or CRC errors.
Categori_zeK
_Edit Document
Send Docu_ment
_Forward
_Move To Folder...
_Remove From FolderK
O=Lotus Notes
O=Lotus Notes
PURSAFO
|.:#U
O=Lotus Notes
CN=Lotus Notes Template Development/O=Lotus Notes
PURSAFO
Fde!f^^
~l:B+5~,
$Author
$TITLE
$INFO
$WINDOWTITLE
$$ScriptName
StartTime
FinishTime
ElapsedTime
PortSpeed
CarrierSpeed
KBytesXmt
KBytesRcvd
PortErrors
CRCErrors
ReXmts
$BODY
$ACTIONS
Times New Roman
Task List
&Switch To
About Notes Log
@___@
<a>7`^
`!bb!R
The Notes Log is a special template, used to automatically create a database that records and stores information about all types of Notes server activities, and remote workstation communication activities.
The Notes Log (LOG.NSF) is automatically created during Notes Setup.
For more information on the Notes Log, see the
Administrator's Guide
and
Dial-up Notes
Server administrators and database managers should look at the Notes Log often to see if:
o Databases are replicating, and how often
o Disk space is low
o Enough memory is available
o Phone communications are working properly.
To the Database Manager
Review the following list before making the database available to users.
Access Control List:
On a Notes server
, the Access Control List (ACL) is set up so that, by default, the server is defined as manager. Immediately after the Log is created, the server administrator should change the ACL to make him/herself manager of the database.
The default access is Reader.
The administrator maintains the ACL. He/she may change the default access or add additional managers.
On a remote workstation
, the person whose ID is active during Notes Setup will be defined as manager of the Log.
About the Notes Log:
Read (and maybe print) this information. Replace the current contents with a paragraph or two that explains the purpose of this database, its audience, and how to contact the manager(s).
(To edit the About Database document, select Design, Help Document, About Database.)
Using the Notes Log:
Be sure to update the Using Database document. It should give users specific information on the use of the database.
(To edit the Using Database document, select Design, Help Document, Using Database.)
This database records events for the Notes server or the Notes workstation.
For the Notes server, information on the following events is recorded:
o Sessions established
o Replications performed
o Mail routed
o Remote connections
o Phone calls (outgoing and incoming)
For the Notes workstation, information on the following events is recorded:
o Replications performed
o Mail routed
o Phone calls (outgoing)
Composing Documents
You cannot compose documents for this database. The documents are automatically created by the server or workstation activities that take place.
Views
Database Sizes
(server only)
shows all databases, sorted by size.
Database Usage
- on both server and workstation - shows replications; categorized by database.
Miscellaneous Events
on a server, shows the starting and ending time of "miscellaneous events" such as mail routing; on a workstation, shows the timing of modem I/O. Categorized by server and then by date.
Phone Calls
- on a server, shows information on the calls the server has made and received; on a workstation, shows calls made from the modem, including problems such as CRC errors and retransmissions.
Replication Events
- on a server, shows all replications between servers, including when they replicated, how long it took to replicate, and which server initiated the call. On a workstation, shows replications, sorted by servers, and lists problems encountered during replication, such as ACL problems.
Sample Billing
(server only)
shows sessions that the server has had with users or other servers, sorted by user name; includes number and duration of sessions. Formatted for export to a spreadsheet bill.
Usage by Date
(server only)
- shows sessions the server has had with users or other servers. Includes number and duration of sessions, databases opened, duration of access per database, number of transactions, and network usage (by Kbytes transferred). Categorized by date.
(.txt)