![](/images/new-backgrounds/1306932/3069329x1.webp)
Configuring
Technology Overview
Figure 127 LLC2 Session without Local Acknowledgment
Router A | Router B |
Token | WAN | Token |
Ring |
| Ring |
37x5 |
| 3x74 |
|
|
LLC2 session
SNA session
S1106a
On backbone networks consisting of slow serial links, the T1 timer on end hosts could expire before the frames reach the remote hosts, causing the end host to resend. Resending results in duplicate frames reaching the remote host at the same time as the first frame reaches the remote host. Such frame duplication breaks the LLC2 protocol, resulting in the loss of sessions between the two IBM machines.
One way to solve this time delay is to increase the timeout value on the end nodes to account for the maximum transit time between the two end machines. However, in networks consisting of hundreds or even thousands of nodes, every machine would need to be reconfigured with new values. With local acknowledgment for LLC2 enabled, the LLC2 session between the two end nodes would not be not
Figure 128 LLC2 Session with Local Acknowledgment
TCP session
Token | WAN |
37x5Ring
Router A
LLC2 session
SNA session
Token
Ring
Router B
3x74
LLC2 session
S1107a
With local acknowledgment for LLC2 enabled in both routers, Router A acknowledges frames received from the 37x5. The 37x5 still operates as if the acknowledgments it receives are from the 3x74. Router A looks like the 3x74 to the 37x5. Similarly, Router B acknowledges frames received from the 3x74. The 3x74 operates as if the acknowledgments it receives are from the 37x5. Router B looks like the 3x74 to 37x5. Because the frames do not have to travel the WAN backbone networks to be acknowledged, but are locally acknowledged by routers, the end machines do not time out, resulting in no loss of sessions.
|
| Cisco IOS Bridging and IBM Networking Configuration Guide |
|
|
|
|
|
| |||
|
|
|
|
| |
|
|
|
|