Specifications

Application View Cisco DLSW Application
Device Management Page 131 Cisco Router
other, activePersistent, activeOnDemand,
passive, and excluded.
Sap List
The SAP list indicates which SAPs are advertised
to the transport connection defined by the local
peer whose transport address is given by Local T
Addr (Page 129). The SAP list is configured on the
local peer, and the SAP list is sent to other peers
via capabilities exchange. The SAP list represents
the SAPs specified via the configuration
command: dlsw icanreach saps X or dlsw
icannotreach saps X Where X is in the range 0-
FE.
Only SAPs with even numbers are represented, in
the form of the most significant bit of the first
octet representing the SAP 0, the next most
significant bit representing the SAP 2, to the least
significant bit of the last octet representing the
SAP 254. Data link switching is allowed for those
SAPs which have one in its corresponding bit, not
allowed otherwise. The whole SAP list has to be
changed together. Changing the SAP list affects
only new circuit establishments and has no effect
on established circuits.
This list can be used to restrict specific partners
from knowing about all the SAPs used by DLSw
on all its interfaces (these are represented in
ciscoDlswIfSapList for each interface). For
instance, one may want to run NetBIOS with
some partners but not others.
If a node supports sending run-time capabilities
exchange messages, changes to this value should
cause that action. It is up to the implementation
exactly when to start the run-time capabilities
exchange. The default value of
'ffffffffffffffffffffffffffffffff'h
indicates support for all SAPs.
Advertise Mac
The value of true indicates that defined local
MAC addresses and NetBIOS names will be
advertised to a partner node via initial and (if
supported) run-time capabilities exchange
messages.
NB Init Cir Recv
The initial circuit receive pacing window size, in
the unit of SSP messages, to be used for future
transport connections activated using this table
row. The managed node sends this value as its
initial receive pacing window in its initial
capabilities exchange message. Changing this
value does not affect the initial circuit receive
pacing window size of currently active transport
connections. If the standard window pacing
scheme is not supported, the value is zero.