FLAGS:

DSIC

SRC sees the incoming INTERCONNECT signal from its destination.

SDIC

DST sees the incoming INTERCONNECT signal from its source.

ACCEPTING

DST is accepting connections. When this flag is not listed, the DST is rejecting connections.

DST.PKT

DST sees that the PACKET input signal is asserted

DST.REQ

DST sees that the REQUEST input signal is asserted

SRC.REQ

SRC channel's REQUEST output signal is asserted

SRC.CON

SRC sees that the CONNECT input signal is asserted

SRC connections:

Count of total connection REQUEST signals issued by source.

SRC packets:

Count of total packets sent by source.

SRC rejects:

Count of SRC's connection attempts that were rejected by the remote destination.

SRC seq errors (dm):

Count of sequence errors detected within the SRC's data state machine.

SRC seq errors (cd):

Count of illegal sequencing of inbound control signals at SRC's connection state machine. The remote destination is believed to be at fault.

SRC seq errors (cs):

Count of sequence errors detected within the SRC's connection state machine.

SRC dsic lost:

Count of connections dropped due to lost DSIC signal.

SRC time outs:

Count of connection attempts that timed out so that the SRC withdrew the request.

SRC connects lost:

Count of connections that were dropped by the remote destination.

SRC parity errs:

Count of SRC's parity errors.This error indicates that a local parity error (for example, on the IRIS HIPPI board) resulted in the transmission of invalid data.

DST connections:

Count of connections accepted by DST.

DST packets:

Count of total packets received

DST rcv on bad ulp:

Count of packets discarded by DST due to unknown ULP-id.

DST hippi-le drop:

Count of HIPPI-LE packets discarded by DST.

DST llrc:

Count of connections dropped by DST due to LLRC errors.

DST parity:

Count of connections dropped by DST due to parity errors in incoming data. Bit-error rates below 10^-20 are not counted; for example, if the DST encounters 1 error after receiving 10^-21 bits of correct data, it does not drop the connection.

DST sequence err:

Count of connections dropped by DST due to sequence errors. Sequence errors are invalid combinations of HIPPI-PH signals (for example, an asserted BURST signal when the PACKET signal is not asserted).

DST sync err:

Count of synchronization errors detected by DST.

DST illegal burst:

Count of inbound packets of an illegal burst size.

DST sdic lost:

Count of connections dropped by DST due to lost SDIC signal.

DST null connections

Count of connections with zero-length packets.

FLAGS:

LOOPBACK

The board is operating in internal loopback mode. Packets are not being passed to the fiber; instead they are going directly from the board's SRC to its DST. When this flag is absent (not set), the board is operating in normal mode; packets are transmitted onto the fiber.

DST.SIG_DET

HIPPI-Serial DST is detecting a signal on inbound fiber. Normal operation requires the presence of this flag.

DST.LNK_RDY

HIPPI-Serial DST is in operational state (that is, it has successfully completed reset and is currently in HIPPI-Serial link state 2). This flag is absent (not set) only if the DST state machine transitions to state 0 or 1, caused by losing contact with the HIPPI-Serial (G-link) chip on the board or the fiber connection. Normal operation requires the presence of this flag.

DST.FSYNC

HIPPI-Serial DST is seeing/interpreting the Flag (alternating 0/1) bit from the coding nibbles of the incoming data frames. Normal operation requires the presence of this flag.

DST.OH8SYNC

HIPPI-Serial DST is synchronizing with the OH8 framing (alternating 0/1) overhead bit. Normal operation requires the presence of this flag.

ACCEPTING

DST is accepting connections. When this flag is not listed, the DST is rejecting connections. Normal operation requires the presence of this flag.

DST.PKT

DST sees that the inbound PACKET signal is asserted.

DST.REQ

DST sees that the inbound REQUEST signal is asserted.

SRC.REQ

SRC channel's outbound REQUEST signal is asserted.

SRC.CON

SRC sees that the inbound CONNECT signal is asserted.

SRC connections:

Count of connection REQUEST signals issued by source.

SRC packets:

Count of total packets sent by local SRC.

SRC rejects:

Count of SRC's connection attempts that were rejected by the remote destination.

SRC xmit retry:

Count of attempts driver made to retransmit packets that were interrupted, either because the remote destination disconnected, or because there was a parity error while transmitting the packet.

SRC glink reset:

Count of times that the firmware reset both the HIPPI-Serial (G-link) chips. A reset occurs when the firmware believes one of the HIPPI-Serial (G-link) chips is not responding. However, a reset can be caused by faulty cabling, ODLs, or connectors since the firmware cannot identify the true cause for an unresponsive HIPPI-Serial portion of the board.

SRC glink lost;

Count of times that the firmware fails to see any one of the following flags for more than half a second: DST.OH8SYNC, DST.FSYNC, DST.LNK.RDY, or DST.SIG.DET. This event can be counted, at maximum, 50 times per second (at 25MHz).

SRC time outs:

Count of connection attempts by SRC that timed out.

SRC connects lost:

Count of connections made by SRC that were dropped by the other side.

SRC parity errs:

Count of SRC parity errors. This error indicates that a local parity error (for example, on the IRIS HIPPI board) resulted in the transmission of invalid data.

SRC number bytes sent:

Count of bytes transmitted. Maximum count, before starting over at zero, is 2⁶⁴ (that is, more than 18 quintillion).

DST connections:

Count of connections that were accepted by DST.

DST packets:

Count of total packets received by DST.

DST rcv on bad ulp:

Count of HIPPI-FP packets that DST discarded due to unknown ULP-id. Some programs produce a few of these events when they are terminated unexpectedly (for example, doing a Ctrl-C to hiptest), because the receiver goes away before the transmitter.

DST hippi-le drop:

Count of HIPPI-LE packets discarded by DST due to no accessible space on the receive packet queue.

DST llrc:

Count of bursts received by DST with LLRC errors.

DST parity:

Count of bursts received by DST with parity errors. Bit-error rates below 10^-20 are not counted; for example, if the DST encounters 1 error after receiving 10^-21 bits of correct data, it does not drop the connection.

DST frame/state err:

Count of (1) framing (alternating OH8 overhead bit) errors that occurred while PACKET signal was asserted, and (2) illegal HIPPI signal states or transitions (for example, a PACKET signal was received without a preceding REQUEST signal).

DST flag err:

Count of data frame alternating flag bit synchronizations that were lost while PACKET signal was asserted.

DST illegal burst:

Count of packets with illegal burst sizes.

DST link rdy lost in pkt:

Count of packets that were aborted due to the DST.FSYNC, DST.OH8SYNC, or DST.LNK.RDY flag becoming unset (not true) when the PACKET signal was asserted.

DST null connections:

Count of connections over which no data was sent.

DST ready errors:

Number of bursts received for which no READYs had been sent.

DST bad packet starts:

Count of inbound HIPPI packets that encountered errors almost immediately (for example, a PACKET-BURST-no_PACKET sequence occurred for a HIPPI-FP connection but less than 12 bytes was transmitted, or a PACKET signal was asserted then deasserted without a BURST ever occurring).

DST number bytes received

Count of bytes received. Maximum count, before starting over at zero, is 2⁶⁴ (that is, more than 18 quintillion).

SRC connections:

Value should constantly increase, as long as local applications are sending data.

SRC packets:

Value should constantly increase, as long as local applications are sending data.

SRC rejects:

Count should be 0. The most probable cause for this event is incorrect configuration (for example, the I-field is incorrectly formatted or has an invalid setting, such as a W-bit set to indicate 64-bit-wide HIPPI).

SRC time outs:

Count should be 0. Each event indicates the remote system did not continue responding correctly after the initial connection was set up. This event can be caused by a timeout value that is too short.

SRC connects lost:

Count should be 0. Each event indicates a problem with a remote HIPPI system.

SRC parity errs:

Count should be 0. Each event indicates a problem with the local IRIS HIPPI hardware.

SRC seq errors (dm):

Count should be 0. Each event indicates a problem with the local hardware.

SRC seq errors (cd):

Count should be 0. Each event indicates a hardware problem with a remote HIPPI device.

SRC seq errors (cs):

Count should be 0. Each event indicates a problem with the local IRIS HIPPI hardware.

SRC dsic lost:

Count should be 0. Each event indicates a hardware or cabling problem located somewhere between the outbound port on the local panel plate connector and the inbound port on the adjacent HIPPI device (for example, the switch).

SRC number bytes sent:

Value should constantly increase, as long as local applications are sending data.

DST connections:

Value should constantly increase, as long as remote applications are sending data to this host.

DST packets:

Value should constantly increase, as long as remote applications are sending data to this host.

DST rcv on bad ulp:

Count should be 0. The most probable cause for this event is incorrect configuration (for example, the remote endpoint's HIPPI-FP layer is incorrectly configured or a local customer-developed application has not bound to its ULP-id correctly). Some programs can produce a few of these events when terminated unexpectedly (for example, doing a Ctrl-C to hiptest), because the receiver goes away before the transmitter.

DST hippi-le drop:

Count should be 0 or low. Usually caused by co-existence problems between IP and HIPPI-FP. For example, a local HIPPI-FP application may not be reading its input queue fast enough or it may be hogging the DMA engine with large-sized packets. Both conditions can result in the board's receive FIFO being blocked, so arriving IP packets are dropped. In rare instances, this condition can be caused by ULPs using very small-sized packets that results in more time spent on overhead processing than on data processing. In this case, increase the packet size (MTU) used by the sources.

DST llrc:

Count should be 0 or very low. The most probable cause is a high bit error rate along the physical link (for example, a dirty fiber end, a loose connector, a length of cable that is too long).

DST parity:

Count should be very low. The most probable cause for a high count is dirty fiber-optic ferrule tips, loose connectors, or too-long cabling.

DST null connections

May indicate a problem with a remote HIPPI system. Usually indicates that a remote application is opening and closing connections without sending data or has an intermittent hardware problem.

DST illegal burst:

Count should be 0. Each event indicates a hardware problem with a remote HIPPI device.

DST sequence err:

Count should be 0. Each event indicates a hardware problem with a remote HIPPI device.

DST sync err:

Count should be 0. Each event indicates that DST lost synchronization with its source.

DST sdic lost:

Count should be 0. Each event indicates a hardware or cabling problem located somewhere between the inbound port on the local panel plate connector and the outbound port on the adjacent HIPPI device (for example, the switch)

DST frame/state err:

Count should be 0. Each event indicates a hardware problem with a remote HIPPI device.

DST flag err:

Count should be 0 or very low. Each event indicates a hardware problem with a remote HIPPI device, except immediately following a local reset of the IRIS HIPPI hardware.

DST ready errors:

Count should be 0. Each event indicates a hardware problem with a remote HIPPI device.

DST bad packet starts:

Count should be 0. Each event indicates a hardware problem with a remote HIPPI device.

DST number bytes
received

Value should constantly increase, as long as a remote system is sending data to this host.

SRC connections:

Value should constantly increase, as long as local applications are sending data.

SRC packets:

Value should constantly increase, as long as local applications are sending data.

SRC rejects:

Count should be 0. The most probable cause for this event is incorrect configuration (for example, the I-field is incorrectly formatted or has an invalid setting, such as a W-bit set to indicate 64-bit-wide HIPPI).

SRC glink reset

Count should be 0. Each event indicates a problem with the local IRIS HIPPI hardware and/or cabling.

SRC glink lost

Count should be 0. Each event indicates a problem with the local IRIS HIPPI hardware and/or cabling.

SRC time outs:

Count should be 0. Each event indicates the remote system did not continue responding correctly after the initial connection was set up. This event can be caused by a timeout value that is too short.

SRC connects lost:

Count should be 0. Each event indicates a problem with a remote HIPPI system.

SRC parity errs:

Count should be 0. Each event indicates a problem with the local IRIS HIPPI hardware.

SRC number bytes sent:

Value should constantly increase, as long as local applications are sending data.

DST connections:

Value should constantly increase, as long as remote applications are sending data to this host.

DST packets:

Value should constantly increase, as long as remote applications are sending data to this host.

DST rcv on bad ulp:

Count should be 0. The most probable cause for this event is incorrect configuration (for example, the remote endpoint's HIPPI-FP layer is incorrectly configured or a local customer-developed application has not bound to its ULP-id correctly). Some programs can produce a few of these events when terminated unexpectedly (for example, doing a Ctrl-C to hiptest), because the receiver goes away before the transmitter.

DST hippi-le drop:

Count should be 0 or low. Usually caused by co-existence problems between IP and HIPPI-FP. For example, a local HIPPI-FP application may not be reading its input queue fast enough or it may be hogging the DMA engine with large-sized packets. Both conditions can result in the board's receive FIFO being blocked, so arriving IP packets are dropped. In rare instances, this condition can be caused by ULPs using very small-sized packets that results in more time spent on overhead processing than on data processing. In this case, increase the packet size (MTU) used by the sources.

DST llrc:

Count should be 0 or very low. The most probable cause is a high bit error rate along the physical link (for example, a dirty fiber end, a loose connector, a length of cable that is too long).

DST parity:

Count should be very low. The most probable cause for a high count is dirty fiber-optic ferrule tips, loose connectors, or too-long cabling.

DST frame/state err:

Count should be 0. Each event indicates a hardware problem with a remote HIPPI device.

DST flag err:

Count should be 0 or very low. Each event indicates a hardware problem with a remote HIPPI device, except immediately following a local reset of the IRIS HIPPI hardware.

DST illegal burst:

Count should be 0. Each event indicates a hardware problem with a remote HIPPI device.

DST link rdy lost in pkt:

Count should be 0. Each event indicates a problem with the local IRIS HIPPI hardware (for example, dirty fiber-optic end, loose connector, too-long or too-short cable, kinked/cracked cable) or possibly with a remote source. Use the various loopback tests to isolate the problem.

DST null connections

May indicate a problem with a remote HIPPI system. Usually indicates that a remote application is opening and closing connections without sending data or has an intermittent hardware problem.

DST ready errors:

Count should be 0. Each event indicates a hardware problem with a remote HIPPI device.

DST bad packet starts:

Count should be 0. Each event indicates a hardware problem with a remote HIPPI device.

DST number bytes received

Value should constantly increase, as long as a remote system is sending data to this host.