Output from nettl.

[David Whitehead]

Below is a chunk of output from nettl:

*******************************LAN/9000 NETWORKING**************************@#%
Timestamp : Wed Sep 20 BST 2000 11:24:14.554871
Process ID : [ICS] Subsystem : NS_LS_DRIVER
User ID ( UID ) : -1 Log Class : INFORMATIVE
Device ID : -1 Path ID : 0
Connection ID : 0 Log Instance : 0
Location : 05041
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Network NS_LS_DRIVER Protocol Log 5041, pid [ICS]
LAN driver dropped packet destined for unlogged DSAP 224
on interface unit 10.

Would some kind soul please translate it for me (I am very inexperienced with nettl) specifically with regards to DSAP (i.e. what that means). Should I be worried that between 1500 and 3000 of these messages (always the same DSAP 224) are being produced every 10 minutes or so.

If I should be worried - what can I do about it.

Many thanks,

David

[David Whitehead]

Anyone?

I cannot find any reference to DSAP anywhere :(

[Andreas Voss]

Sorry,

all i've found is what DSAP is:
SAP stands for:
Service Access Point
and is part of IEEE802.2 layer definition.
D stands for Destination.
Also it gives SSAP where the S stands for source.

Regards

[Berlene Herren]

Here is some more information from the LLA Programmer's Guide
16 Chapter 1
LLA to DLPI Migration
Transmitting Data

LLA requires the user to log a destination address (LOG_DEST_ADDR)
and a destination service access point (LOG_DSAP) prior to sending any
data.
DLPI requires the user to specify the destination address and
destination service access point (dsap) as part of the data transfer
request. The combination of destination MAC address and dsap is
referred to as the DLSAP address.
The DLSAP address format is basically the destination MAC address
followed by the LLC protocol value. A complete description of the DLSAP
address format is described in the DLPI Programmer's Guide.
LLA supports the write system call for sending data requests.
DLPI only supports the putmsg system call for sending data over RAW
(see the DLPI Programmer's Guide) and connectionless mode streams.
The write system call is only supported over connection oriented
streams in the DATA_XFER state (i.e. a connection must be established).


In the ethernet frame, the data imediately follows the type field, while in the 802 frame format 3 bytes of 802.2 LLC and 5 bytes of 802.2 SNAP follow. The DSAP (destination Service Access Point) and the SSAP (Source Service Access Point) are both set to 0xaa. So all this says is that DSAP is par of the IEEE 802.2/802.3 Escapsulation IAW with RFC 1042.

Does this help or does it just muddy the water more :)

Berlene