it. On-demand peers require very little configuration. The router must be in promiscuous
(listening) mode to receive the connection request.
switched and therefore uses more CPU power than either FST or Direct encapsulation.
TCP transports SNA and NetBIOS traffic across WANs, where local acknowledgment is
required to minimize unnecessary traffic and prevent data-link control timeouts and where
nondisruptive rerouting around link failures is critical. A Cisco 4700 router running
DLSw+ can switch up to 8 Mbps of data, so TCP will meet most of the requirements.
methods to encapsulate the data.
is fast-switched, this encapsulation allows DLSw+ to process more packets per second
than TCP. FST transports SNA and NetBIOS traffic across WANs with an arbitrary
topology. This solution allows rerouting around link failures, but recovery might be
disruptive, depending on the time required to find an alternative path. This option does not
support local acknowledgment of frames. FST is supported only when the end systems are
Token Ring, whereas TCP is supported if one of the end systems is on Ethernet. Load
balancing is not recommended with FST because frames might arrive out of order.
traffic across a point-to-point or Frame Relay connection, where the benefits of an
arbitrary topology are unimportant and where nondisruptive rerouting around link failures
is not required. This option does not support local acknowledgment of frames. Like FST,
Direct is supported only when the end systems reside on Token Ring.