NAME

hps_log − display log and supplementary information from the MVME338 host adapter or cluster controllers

SYNOPSIS

hps_log [ −uc ] [ −a addr ] [ −d device ]

DESCRIPTION

hps_log reads the log table from either an MVME338 host adapter or an MVME338 cluster controller and writes it to standard output.  The default is to interpret the contents and produce a formatted display of the log table of the MVME338 with device name /dev/xedt/mvme338_c0. 

OPTIONS

One or more of the following options may be selected:

−aSpecify that the log table from one of the cluster controllers should be read.  The cluster address is specified in addr. 

−dSpecify the device file name for the host adapter board.  The file name is specified in device. 

−uProduce an unformatted (binary) write of the log table.  This is designed to be piped into another program to interpret the data. 

−cSpecify that the log table be cleared after it is read. 

EXAMPLES

To write a formatted display of the default host adapter’s log table and then clear the log table:

 hps_log -c

To write a formatted display of the cluster controller 1 log table:

 hps_log -a 1

To write a formatted display of the log table of the second MVME338 in the system:

 hps_log -d /dev/xedt/mvme338_c1

The following fields are displayed for an MVME338 host adaptor;  

ModelThe vendor model designation for this device.  At The time this was written, MVME338 controllers were model HPS-6245. This model may change in the future. 

Firmware
The Systech part number of the firmware on this device. The last 3 digits represent the revision of this firmware.

Board
This is UNUSED, Always "X" characters.

Device
A numeric code for the type of device. Please see /usr/include/sys/mvme338/st.dev_type.h for a list of codes and their descriptions.

Station
The network address for this device. Usually this is 0xff for MVME338 boards, and a number from 0x01 to 0xfe for MVME338 terminal servers. All devices on a single network must have a unique station Id.

Option
A hexadecimal representation of the option switch strapping for the MVME338 controller.

Real-time
Simply, the number of clock ticks since a board or log reset.

Idle
The number of times the controller was ready to do a task, but there were no tasks to do.

Bytes
The bytes sent to the MVME338 from the host.

Bytes
The bytes sent to the host from this MVME338.

DMA
The number of timeouts when the DMA hardware was expecting an acknowledgement to a DMA transfer.

DMA
The number of timeouts waiting to obtain a DMA buffer.

DMA
The number of timeouts waiting for a DMA bus request.

IOCB’s
The number of I/O Control Blocks processed.

No memory
The number of times MVME338 software tried to obtain a section of memory but none was left.

Response
The number of times device tried to enqueue a response and queue was full.

Network
The number of times the queue for the network was full.

Miscellaneous
Other Errors.

Packets
The number of packets of data or commands sent.

Packets
The number of packets of  data/cmds received

No
The number of times a terminal server failed to respond to the MVME338.

Bad
The number of times terminal server responded with incorrect data.

Offline
The number of attempts to communicate with an offline terminal server. A terminal server is offline during it’s self test, or while being downloaded.

Reconfigurations
The number of times a device was marked as being dropped or added to the network attached to this MVME338. A constantly rising number on a running system indicates that the MVME338 is having problems communicating over it’s network, or the coaxial cable is unplugged, faulty, or incorrectly  terminated.

reserved
Unused field

ROM
Read Only Memory size

ROM
A checkum for the devices ROM(s)

End
End of Random Access Memory on MVME338

Real
Frequency in Mhz of MVME338’s clock.

reserved
Unused field

Single-chan
The number of bytes read one channel at a time.

Multi-chan
The number of bytes from multi-channel reads. When possible, the MVME338 will multiplex data from several channels into one network packet for transmission to and from the MVME338.

Single-chan
The same as above for writes from the MVME338.

Multi-chan
The Same as above for writes from the MVME338.

ERRORS

The following errors can be reported by the MVME338:

E_OFFLINE
occurs when the Network Manager attempts but fails to transmit a packet of data to a cluster controller.

E_NORESP
occurs when an attempt is made to access a cluster controller that does not respond.

E_BADRESP
occurs when a request for data is made from a cluster controller and incorrect data returned.

SEE ALSO

mvme338(7), hty(7)

BUGS

Earlier versions display "Board assy" header instead of "Running".