(C)Copyright 1992-1996 SysKonnect,
a business unit of Schneider & Koch & Co. Datensysteme GmbH.
All rights reserved
==========================================================================
UPPSDIAG.TXT

Readme-File for SK-UPPS Diagnostics. /
Subject: UPPSDIAG.EXE SK-UPPS Diagnostics program.
	

Version / Date / Author of this file: v1.14 Rev. A / 15-Mar-1996 / RA
Version / Date / Author of the referred subject: v1.14 / 15-Mar-1996 /
RA


This file contains
(1) Overview
(2) The Menu
(2.1) Choose DLI
(2.2) Driver Status
(2.3) Network Statistics
(2.3.1) General statistics
(2.3.2) Ethernet specific
(2.3.3) FDDI specific
(2.3.4) Token Ring specific
(2.4) Protocols
(2.5) Save Diagnostics
(3) History

===========================================================================


(1) OVERVIEW
============

UPPSDIAG.EXE shows internal information about the UPPS Data Link
Interface driver.
The versions of the drivers and the different settings can be viewed.

Before starting UPPSDIAG you have to load the Data Link Interface driver
(UPPSDLI.COM, UPPSJET.COM, UPPSISDN.COM, UPPSTR.COM,
UPPSFE.EXE, UPPSFI.EXE, UPPSFM.EXE, or UPPSFP.EXE).

UPPSDIAG -d shows all informations on one screen and exits.

Under WINDOWS and the DOS Task Switcher (DOSSHELL) you cannot connect to a
remote SNMPD.

You can leave the program after being asked back with ALT+F10 or without
being asked back with ALT+X.
***


(2) THE MENU
============

This chapter explains the values that are presented in the different menus.
***


(2.1) CHOOSE DLI
================

Choose one of the local DLIs presented or choose connecting to a remote
Simple Network Management Protocol Daemon (SNMPD).
***


(2.2) DRIVER STATUS
===================

- see UPPS Manual -
***


(2.3) NETWORK STATISTICS
========================

The statistics window is split into two logical parts:
- The upper part contains statistics that are independant of the special
  topology.
- The lower part contains topology specific statistics.
***


(2.3.1) GENERAL STATISTICS
==========================

RX demuxed
Number of packets/bytes received that were routed to protocols.

TX total
Number of packets/bytes sent by protocols.

RX multicast
Number of multicast packets/bytes received that were routed to protocols.

RX discarded
Number of received packets that were not routed to a protocol.

Uptime
The time the DLI is loaded (mod 24h).

CRC error
Number of received packets that had an illegal checksum.
Possible reasons for such packets:
	- defective network adapter
	- high frequency interference onto the network cable
        - short-circuit in the network cable

Not byte bound
Number of received packets that have a number of bits that does not end
on byte boundaries.
Reasons as above.

Too long (rec.)
Number of received packets exceeding the maximum length for this topology.
This implies incorrect protocol drivers (on the remote station).
***


(2.3.2) ETHERNET SPECIFIC
=========================

Misaligned pkts
A count of frames received on a particular interface that are not an
integral number of octets in length and do not pass the FCS check.
The count represented by an instance of this object is incremented when
the alignmentError status is returned by the MAC service to the LLC
(or other MAC user).  Received frames for which multiple error conditions
obtain are counted exclusively according to the error status presented to
the LLC.

FCS errors
A count of frames received on a particular interface that are an integral
number of octets in length but do not pass the FCS check.
The count represented by an instance of this object is incremented when the
frameCheckError status is returned by the MAC service to the LLC (or other
MAC user).  Received frames for which multiple error conditions obtain are
counted exclusively according to the error status presented to the LLC.

Single colls
A count of successfully transmitted frames on a particular interface for
which transmission is inhibited by exactly one collision.
A frame that is counted by an instance of this object is also counted by
the corresponding instance of either the ifOutUcastPkts or ifOutNUcastPkts
object and is not counted by the corresponding instance of the
ethStatsMultipleCollisionFrames object.

Multiple colls
A count of successfully transmitted frames on a particular interface for
which transmission is inhibited by more than one collision.
A frame that is counted by an instance of this object is also counted by
the corresponding instance of either the ifOutUcastPkts or ifOutNUcastPkts
object and is not counted by the corresponding instance of the
ethStatsSingleCollisionFrames object.

Bad signal
A count of times that the SQE TEST ERROR message is generated by the PLS
sublayer for a particular interface.

Deferred trans
A count of frames for which the first transmission attempt on a particular
interface is delayed because the medium is busy.  The count represented by
an instance of this object does not include frames involved in collisions.

Late collisions
The number of times that a collision is detected on a particular interface
later than 512 bit-times into the transmission of a packet.
Five hundred and twelve bit-times corresponds to 51.2 microseconds on a
10 Mbit/s system.  A (late) collision included in a count represented by
an instance of this object is also considered as a (generic) collision for
purposes of other collision-related statistics.

Excessive colls
A count of frames for which transmission on a particular interface fails
due to excessive collisions.

Int trans errs
A count of frames for which transmission on a particular interface fails
due to an internal MAC sublayer transmit error.  A frame is only counted
by an instance of this object if it is not counted by the corresponding
instance of either the ethStatsLateCollisions object, the
ethStatsExcessiveCollisions object, the ethStatsCarrierSenseErrors object,
or the ethStatsExcessiveDeferrals object.  The precise meaning of the count
represented by an instance of this object is implementation-specific.  In
particular, an instance of this object may represent a count of
transmission errors on a particular interface that are not otherwise
counted.

Carrier sense
The number of times that the carrier sense condition was lost or never
asserted when attempting to transmit a frame on a particular interface.
The count represented by an instance of this object is incremented at
most once per transmission attempt, even if the carrier sense condition
fluctuates during a transmission attempt.

Excessive defer
A count of frames for which transmission on a particular interface is
deferred for an excessive period of time.

Too long (rec)
A count of frames received on a particular interface that exceed the
maximum permitted frame size.
The count represented by an instance of this object is incremented when
the frameTooLong status is returned by the MAC service to the LLC (or
other MAC user).  Received frames for which multiple error conditions
obtain are counted exclusively according to the error status presented
to the LLC.

Length errors
A count of frames received on a particular interface with a length field
value that falls between the minimum unpadded LLC data size and the
maximum allowed LLC data size inclusive and that does not match the
number of LLC data octets received.
The count represented by an instance of this object also includes frames
for which the length field value is less than the minimum unpadded LLC
data size.

Big len field
A count of frames received on a particular interface for which the length
field value exceeds the maximum allowed LLC data size.
The count represented by an instance of this object is not incremented in
implementations that observe Ethernet encapsulation conventions (by which
the IEEE 802.3 length field is interpreted as the Ethernet Type field).

Int rec errors
A count of frames for which reception on a particular interface fails due
to an internal MAC sublayer receive error.  A frame is only counted by an
instance of this object if it is not counted by the corresponding instance
of either the ethStatsFrameTooLongs object, the ethStatsAlignmentErrors
object, the ethStatsFCSErrors object, the ethStatsInRangeLengthErrors
object, or the ethStatsOutOfRangeLengthFields object.
The precise meaning of the count represented by an instance of this object
is implementation-specific.  In particular, an instance of this object may
represent a count of receive errors on a particular interface that are not
otherwise counted.
***


(2.3.3) FDDI SPECIFIC
=====================

MAC upstream neighbour
The MAC's upstream neighbor's long individual MAC address.  It has an
initial value of the SMT-Unknown-MAC Address and is only modified as
specified by the Neighbor Information Frame protocol.
Note:	SMT-Unknown-MAC is 00:00:1F:00:00:00 (MSB) or
	00-00-F8-00-00-00 (LSB, canonical).

MAC downstream neighbour
The MAC's downstream neighbor's long individual MAC address.  It has an
initial value of the SMT-Unknown-MAC Address and is only modified as
specified by the Neighbor Information Frame protocol.
Note:	SMT-Unknown-MAC is 00:00:1F:00:00:00 (MSB) or
	00-00-F8-00-00-00 (LSB, canonical).

SMT version ID
The version used by this station for operation.  The value of this
attribute is 2 for this SMT revision.

SMT CF state
The CF_State represents the attachment configuration for the station or
concentrator.
CF-State ::= ENUMERATED {
	isolated(0),
	local_a(1),
	local_b(2),
	local_ab(3),
	local_s(4),
	wrap_a(5),
	wrap_b(6),
	wrap_ab(7),
	wrap_s(8),
	c_wrap_a(9),
	c_wrap_b(10),
	c_wrap_s(11),
	thru(12) }

SMT frames send
The number of SMT frames sent.

SMT frames rec
The number of SMT frames received.

SMT ring up
The count of the number of times the ring has changed from the
'Ring_Not_Operational' state to the 'Ring_Operational'state.
This count is updated when a SM_MA_STATUS.Indication of a change in the
Ring_Operational status occurs.  Because of implementation considerations,
this count may be less than the actual RingOp_Ct.  It is not required that
this count is exact.

MAC frame cts
A count of the number of frames received by this MAC.

MAC error cts
A count of the number of error frames detected by this MAC that were not
detected by another MAC.

MAC lost cts
A count of the number of instances that this MAC detected a format error
during frame reception so that the frame was stripped.

Port x ler estimate
A long term average link error rate.  It ranges from 10^-4 to 10^-15 and
is reported as the absolute value of the base 10 logarithm.

Attach class
The capability of a station or concentrator for connection to an FDDI
network.  Stations and concentrators are classified as dual attachment,
single attachment or null attachment.
AttachmentClass ::= INTEGER {
	single-attachment(1),
	dual-attachment(2),
	concentrator(3) }

Attach bypass
A flag indicating if the station has a bypass at its AB dual port.
AttachmentBypass ::= INTEGER {
	true(1),
	false(2) }
***


(2.3.4) TOKEN RING SPECIFIC
===========================

Upstream neighbour
The MAC's upstream neighbour's long individual MAC address.

Ring number
The unique number of the local Token Ring.

Ring up count
The number of times the station made sucessfully an 'open adapter'.

Signal losses
The number of times the adapter detected a loss of signal on the ring.

Lobe wire fault
The number of times the adapter detected an open or short circuit in the
cable between the adapter and the wiring concentrator.

Ring recoveries
The number of times the adapter observes claim token MAC frames on the
ring.  The adapter may be transmitting the claim token frames.

Line errors
The line error counter is incremented whenever
	1) a frame is repeated or copied, and
	2) the error detected indicator is zero in the incoming frame, and
	3) at least one of the following conditions exists:
	  a) a code violation between the starting delimiter and the ending
	     delimiter of the frame,
	  b) a code violation in the token,
	  c) a Frame Check Sequence (FCS) error.
When the line error is incremented, the EDI of the frame is set to one so
that no further station counts the error.

Burst errors
The burst error counter is contained in all adapter configurations and is
incremented when the adapter detects the absence of transitions for five
half-bit times between SDEL and EDEL, or EDEL and SDEL.  Only one adapter
detects the burst five condition because the adapter that detects a burst
four condition (four half bit times without transition) directs its
transmitter to transmit idles if the burst five condition is detected.

ARI/FCI errors
The ARI/FCI error counter is incremented when an adapter receives an
Active Monitor Present (AMP) MAC frame with the ARI/FCI bits equal to
zero and a Standby Monitor Present (SMP) MAC frame with the ARI/FCI bits
equal to zero, or more than one SMP MAC frame with the ARI/FCI bits equal
to zero, without receiving an intervening AMP MAC frame.  This condition
indicates that the upstream neighbor is unable to set the ARI/FCI bits in
a frame that it has copied.

Lost frames
The lost frame error counter is incremented when an adapter is in transmit
(stripping) mode and fails to receive the end of the frame transmitted.

Receive congest
The receive congestion error counter is incremented when an adapter in the
repeat mode recognizes a frame addressed to it but has no buffer available
to copy the frame.

Uncopied frames
The frame copied error counter is incremented when an adapter in the
repeat/receive mode recognizes a frame addressed to its specific address
but finds the ARI bit not equal to zero.  This indicates a possible line
hit or duplicate address.

Token errors
The token error is active only in the active monitor station.  It is
incremented when the active monitor detects an error with the token
protocol as follows:
	1) The MONITOR_COUNT bit of a token with nonzero priority equals
	   one.
	2) The MONITOR_COUNT bit of a frame equals one.
	3) No token or frame is received within a 10ms-window.
	4) The starting delimiter/token sequence has a code violation in
	   an area where code violation must not exist.

DMA bus errors
The DMA bus error counter counts the occurrences of DMA bus errors that
do not exceed the abort thresholds as specified in the initialization
parameters.

DMA parity errs
The DMA parity error counter counts the occurrences of DMA parity errors
that do not exceed the abort thresholds as specified in the
initialization parameters.

Rec overflows
The Receive Overflow error counter counts the occurrences of packets which
do not fit in one DLI Mbuf (>4504 Bytes).
***


(2.4) PROTOCOLS
===============

Here you can view the protocols that are registered at the chosen DLI.
You can also view the receive mode of the protocol and for local DLIs the
multicast addresses the protocol registered.
***


(2.5) SAVE DIAGNOSTICS
======================

The information of the Driver Status, Network Statistics and Protocols
windows are saved to a file as ASCII text.
***


(3) HISTORY
===========

v1.14
    New features:
	- Showing DMA "Busmaster".
    Problems fixed:
	- Long adapter name strings scramble the "Choose DLI" window.
    Known limitations:
	- Does not show sharing flags.

*** End of information file ***