Business Services Industry

Sync Research Introduces IBM Boundary Access Network, BAN, Support with New Software for the FrameNode 400 Series Internetworking FRAD

Business Wire, July 24, 1995

IRVINE, Calif.--(BUSINESS WIRE)--July 24, 1995--Sync Research announced the immediate availability of a new software release for the FrameNode(TM) 400 Series of multiprotocol internetworking Frame Relay Access Devices (FRADs). Release 3 extends Sync's IBM interoperability primacy and adds unique connection switching features for SNA and other connection-oriented legacy and LAN protocols, and enhances legacy multiprotocol support.

NEW KEY FEATURES INTRODUCED IN 3 INCLUDE:

Boundary Access Node Support: Sync extends its leadership role in SNA internetworking and IBM interoperability with the release of Boundary Access Node (BAN) support for the FrameNode 400 series internetworking of FRAD. BAN is a new architectural feature of 3745/3746 ACF/NCP Version 7 Release 3 that supports bridged and IP connections through the FEP thereby, augmenting its role as a frame relay WAN to IBM mainframe termination node for IBM-centric networks.

BAN support in the FrameNode 400 is the byproduct of a new Release 3 feature called Logical Link Switching (LLSw). LLSw is a RFC1490-compliant level 2 frame switching technique which provides the benefits of Data Link Switching (DLSw)-SDLC-to-LLC2 conversion, LLC2 WAN transport, non-disruptive alternate routing, and local serial SDLC and LAN LLC2 termination -- but without DLSw's bandwidth robbing overhead, lack of determinism, and operational complexity. The FrameNode's versatile LLSw function supports both Type I and Type II BAN connections as well as provides concurrent support for RFC1490 Annex F SNA over frame relay format. Each format is assignable on a per downstream controller basis. BAN support on the FrameNode 400 solves several key problems found in 3745/3746 ACF/NCF Version 7 Release 1 based networks running the RFC1490 Annex F format: Passthrough of FRAD management connections on a single PVC to the branch. And, consolidation of SNA, bridged, IP and non-SNA legacy traffic into a single FEP terminating the frame relay WAN at the data center. Since the FrameNode uses LLSw to transport non-SNA legacy protocols like BSC/3270 and Async, these protocols can be transported through the BAN FEP at the data center and passed onto a Token Ring LAN where they can be converted back to their native host protocol using Syncs ConversionNode legacy-to-LAN conversion products.

Virtual Routing Switching: The Release 3 Virtual Route Switching feature is band on the LLSw level 2 switching mechanism and allows the assignment of multiple frame relay PVC connections to a downstream SNA/SDLC, SNA/LLC2 or other connection-oriented serial or LAN device to be used as primary and alternate routes. An Explicit Virtual Route (eVR) can be assigned to a SNA controller to provide it deterministic primary route across the frame relay backbone and campus network and all the way to the FEP. If the eVR fails anywhere along that route, the SNA sessions can be automatically switched to a predefined Parallel Virtual Route (pVR) to the same host destination without loss of SNA sessions. If the primary host destination is not available, the FrameNode automatically switches the connections to a disaster recovery hot-site or alternate host site via an Alternate Virtual Route (aVR) PVC. This new feature provides deterministic pathing overhead for connection-oriented protocols like SNA without incessant broadcast or router table update overhead flowing across the relatively skinny branch trunks. Additionally, it provides immediate and automatic switch-over to predefined redundant and disaster recovery hot-site PVCs without network operator intervention. This feature was designed to complement the special multiPVC pricing structures emerging from frame relay carriers to address such alternate routing requirements for mission critical applications.

Virtual Route Switching allows connection-oriented devices, like SNA/SDLC, SNA/LLC2 and BSC/3270 controllers, to dynamically switch logical link connections from a failed frame relay PVC or path to a second, parallel PVC without session loss. When the failed PVC is restored, the frame relay network notifies the FrameNode which then restores the switched connections back onto their original PVC. Virtual Route Switching is RFC1490-compliant, requires no additional protocols or overhead, and is non-proprietary while remaining IBM and multivendor interoperable. The feature also provides SNA/SDLC, SNA/LLC2, BSC/3270 and other connection-oriented legacy applications with multipathing and session resiliency functionality found only in complex, high overhead TCP/IP/DLSw or proprietary transport implementations.

Extended Quality of Service Features: The FrameNode's Priority Dependent Queuing and Priority Dependent Transmission class of service and bandwidth allocation quality of service features have been extended to the individual controller for both serial and LAN traffic and to the individual user for LAN applications. Previously, PDQ and PDT were definable on a per protocol basis. This extension allows a SNA 3770 RJE station and SNA 3174 controller on the same FrameNode attached multipoint line to different quality of service definitions.


 

BNET TalkbackShare your ideas and expertise on this topic

Please add your comment:

  1. You are currently: a Guest |
  2.  

Basic HTML tags that work in comments are: bold (<b></b>), italic (<i></i>), underline (<u></u>), and hyperlink (<a href></a)

advertisement
advertisement
  • Click Here
  • Click Here
  • Click Here
advertisement

Content provided in partnership with Thompson Gale