background image
Serial Tunnel (STUN) 485
·
Serial direct is used to connect local controllers to the router. An example of this is a FEP
connected to one port of a Cisco router and a cluster controller connected to another port
of the same router, as shown in Figure 13-10. This is not a very popular method.
Figure 13-10
Serial Direct
Local Acknowledgment for STUN
Local acknowledgment with STUN is a good idea, especially if you have a congested
WAN. Choose local acknowledgment for TCP STUN connections in cases where congestion
and delay in the WAN cause SNA sessions to drop. However, keep in mind that local
acknowledgment can create more overhead on the CPU, and STUN is already
processor-intensive.
Remember, STUN is not just for IBM devices. Any HDLC-based protocol can be encapsulated
with STUN. For example, a Nortel DPN-100 (an X.25 packet switch from the late 1970s) can
have its proprietary protocol encapsulated over a STUN connection to communicate with
another DPN-100 because the DPN-100 Netlink protocol is based on HDLC.
NOTE
X.25 is based on the HDLC protocol.
If the tunnels are carrying critical data, it might be necessary to implement a form of QoS such
as Class-Based Weighted Fair Queuing (CBWFQ) on the routers. This can prioritize the STUN
packets and also guarantee a certain amount of bandwidth for the connection through the
routers. Because SDLC is typically used with slow links (slow links meaning 128 KB or less),
the SDLC timers are more patient before timing out.
IBM 3x74
IBM 3720/25/45
IBM 3720/25/45
Cluster Controller 2
Cluster Controller 1
S0
S1
S2
FEP
87200333.book Page 485 Wednesday, August 22, 2001 1:41 PM