Currently have two pvcs on remote routers across the WAN. One delivers traffic to my site for APPS and the second one delivers to an ASP. My site also has connectivity to ASP on a large pipe (DS3) on a sonet ring. We have connectivity to a mainframe at the ASP to deliver 5250 and 3270 sessions; some via SNA server and some via MTX controllers. This same scenario plays out at the remote sites via the second PVC to the ASP.
We are migrating one site to connectivity using one PVC to my site and are trying to architect the right config to port the sessions to the ASP via our DS3.
There are config lines on the remote routers (which were set up before my time) which refer to DLSw and an ACL for that SNA/DLSw which contains permit statements in HEX.
I understand DLSw and the fact that it keeps the chatty LLC local rather than on the WAN, but I want to know if: 1. Can I accomplish this traffic pattern change if the DLSw config lines point to addressing that I also can reach from my site? 2. Can I just cut and paste most of the config lines pertaining to DLSw, except for the local peer statements but including the addition of the ACL HEX permits?
Why are all of my questions so intricate?...lol Ah, what a tangled web we (I) weave!
Any help would be great....Sahirh? (Hi)
A scapegoat is often as welcome as a solution...never memorize what you can look up.
The administrator has disabled public write access.