Nfs History Files; Timestamps; Enabling Nfs On The Scs - HP 16-port SCS Installation Instructions Manual

server cli history=clear|keep
If Clear is specified, the port history buffer is cleared and all data is discarded at the end of a session.
If Keep is specified, the content of the port history buffer is retained at the end of a session.
Clearing and discarding all port history buffer data
Issue a Clear command while you are in port history mode.
clear
-or-
Issue a Server CLI command, indicating History=Clear.
server cli history=clear
In this case, the history buffer of the port is cleared at the end of each device session.

NFS history files

When the NFS feature is enabled on the SCS and on a port, port history data is written to a file on an NFS server, in
addition to the local history buffer on the SCS. Each serial port has its own files on the NFS server where data is
written. The NFS server must support NFSv3 (RFC1813).

Timestamps

Timestamps are written to the history file in the format: YYYY-MM-DD HH:MM:SS, where the hour (HH) is in 24-hour
format. Each timestamp is preceded and followed by a carriage return and linefeed (CR+LF). The timestamp date and
time uses the current time on the SCS, which is assumed to be Universal Coordinated Time (UTC). You can display the
current time on the SCS at any time by entering a Show Server command.
A timestamp is inserted at the beginning of the file and whenever the file is opened for data to be written, but not
more frequently than once every second.
If the SCS is unable to send incoming data to the NFS server file quickly enough (for example, because of network
load or server speed), an overrun might occur in the history accumulation buffer, and older data will be discarded to
accommodate new incoming data. If this occurs, the location in the history file where the data was lost will indicate
<<data lost due to overrun>> appended to the timestamp.

Enabling NFS on the SCS

To use NFS, you must first enable NFS on the SCS by identifying the address and mount point of the NFS server, plus
the file type and the protocol.
The system administrator of the NFS server must make the appropriate configuration changes to allow the SCS to
access a specific subdirectory in the file system (the mount point) of the NFS server, which might allow the SCS to
access or create subdirectories within the mounted subdirectory. This action will affect what can be specified in the
Port NFS command file parameter.
The valid file types are:
Linear—A file will be opened for writing at the end (appended). This type is the default.
Daily—A new file will be created every midnight.
By default, the TCP network protocol is used for communications between the SCS and the NFS server. You can use
the Protocol parameter to specify the UDP or TCP protocol.
Enabling NFS
Issue an NFS command with the Enable parameter.
nfs enable [ip=<nfs_server>] [mount=<mount>] [ftype=linear|daily] [protocol=tcp|udp]
If this is the first time you are enabling NFS on the SCS, you must include the IP address of the NFS server and a valid
mount point. You can also specify the file type and protocol.
You can also use the NFS Enable command to change the current IP address, mount point, file type, or protocol.
nfs enable ip=<ipaddress> mount=/scs_history ftype=daily protocol=TCP
The values display, and you are prompted to confirm.
Operations 37