NIO CommKit Host Interface Installation and System Administration Manual

DKSTAT(1M) DKSTAT(1M)
E-36 CommKit Host Interface, Release 4.0
r_nobuf Number of incoming URP data packets dropped by the dkhs(7) driver because of
buffer exhaustion. This statistic is the count of URP data packets dropped and is not a
count of user messages lost. A user message may consist of many URP data packets.
Dropped packets normally result in the retransmission of data and adversely affect
performance by wasting network bandwidth.
r_parity Number of times the fiber optic receiver circuitry reported a parity error for the
received data stream. Data with errors is discarded and normally results in a
retransmission. A large r_parity count probably indicates a hardware problem.
r_frame Number of times the fiber optic receiver circuitry reported a framing error for the
received data stream. Data with errors is discarded and normally results in a
retransmission. Momentary interruption of the fiber-optic data link often causes a
framing error. A large r_frame count probably indicates a hardware problem. A bad
clock or repeater module on the data switch node will cause the framing error count
to increase rapidly. This will cause communication problems between the node and the
host and may result in the loss of service to the host.
r_ovrun Number of times the dkhs(7) receiver interrupt routine detected that the hardware
receive FIFO was overflowed. A receiver overrun causes data loss and normally results
in a retransmission. A large r_ovrun count indicates an overloaded system or a
problem with higher priority interrupts blocking interrupts to dkhs(7).
The dkhs(7) driver collects channel statistics for every active channel. These statistics are available for
individual channels while the channels remain active and are available as an interface-wide channel summary
whenever the interface is active. Both Channel Statistics and Channel Summary Statistics contain the
following fields:
x_msgs User (STREAMS) data messages transmitted.
x_blocks URP data blocks transmitted. Each user STREAMS message transmitted is broken up
into one or more URP data blocks during transmission across the data switch network.
The size of the URP data blocks is negotiated at call setup time.
x_bytes User data bytes transmitted.
x_enq Transmitter ENQuires sent. Whenever a transmitted URP data block is not properly
acknowledged by the remote endpoint within the expected interval, the URP ENQ
character is periodically transmitted until a satisfactory response is received.
x_init Number of URP INIT1 characters transmitted. These initialization characters are
transmitted when a circuit is initialized or reinitialized.
r_msgs User (STREAMS) data messages received.
r_blocks Valid URP data blocks received. A complete user message may consist of one or more
URP data blocks. The size of the URP data blocks is negotiated at call setup time.
r_bytes User data bytes received.
r_badblk Bad URP data blocks received. Bad URP data blocks result in the transmission of URP
REJect characters which cause the bad blocks to be retransmitted. These bad blocks
can be received when one or more packets are lost during transmission. This is usually
caused by noisy trunks or other network congestion, but may also be caused by
STREAMS message exhaustion.
r_rej URP REJect characters received. The REJ characters are received whenever a
transmitted URP data block is lost or damaged during transmission and is rejected by
a remote endpoint. The rejected block is retransmitted. URP data blocks are rejected
by remote endpoints when one or more packets are lost during transmission. This is
usually caused by noisy trunks or other network congestion, but may also be caused by
buffer exhaustion at the remote endpoint.