Technical SupportSkip Navigation
border

Conferences and Events | Online Resources | Programs | Security | Services | Shared Network | Technical Support | Training
About MOREnet | Contact Us | Search | MyMOREnet Login | Collaboration Matrix


Home » Technical Support » Networks and Workstations » Wide Area Networks » Wide Area Networking Considerations for Library Automation Systems
Networks and Workstations Links
 
Spacer Graphic

Wide Area Networking Considerations for Library Automation Systems

Introduction

Wide Area Networks (WANs) allow related libraries to share automation systems and other local resources in addition to providing Internet access. WAN connectivity options for Missouri public libraries as provided by MOREnet are outlined in the MOREnet document Wide Area Networking Options for REAL.

Libraries should review this document before considering a Wide Area Network to connect to remote libraries. Cost, distance and available technical support are primary considerations in considering WAN options. The technical aspects of specific automation systems must also be considered for optimum connectivity.

IPX Versus IP

Although Local Area Networks (LANs) can use a variety of network protocols, all data that traverses the Internet must use standard TCP/IP protocols. Because modern library Automation Systems typically communicate through TCP/IP communications over the Internet are simple to incorporate. Some automation systems may require communications that rely on the IPX protocol, (a proprietary networking protocol used by Novell Networks). If libraries need to establish connections between two or more sites that require transmission of the IPX protocol there are disadvantages to the libraries involved.

All data that travels the Internet (synonymous with the MOREnet backbone for this discussion) must do so via the TCP/IP protocol suite. For IPX to cross the Internet it must be "encapsulated" or "tunneled" inside of TCP/IP packets. This process requires configuration of the Novell server or the router at each site and will cause additional overhead on the file server and the Wide Area connection. For a technical brief on IP tunneling refer to:

http://www.novell.com/documentation/lg/nw5/docui/
index.html#../uscomm/rtcf_enu/data/h2mutkna.html

Another option would be a point-to-point connection as shown in Figure 5 of Wide Area Networking Options for REAL. A point-to-point connection is a dedicated link that does not involve the Internet between two sites. Two libraries that need to exchange IPX data could simply route or bridge the IPX protocol across this connection. Unfortunately point-to-point connections are distance sensitive and generally if the distance from site A to the telco to site B is greater than five miles this will not be an effective option.

In general, to conform with other standardized library resources, maximize efficiency of network connections, and minimize complexity of administration, it is recommended that Library Automation Systems use the TCP/IP suite of protocols for connectivity. Systems should at least have a client component that can access resources through the Internet using TCP/IP.

border
Copyright © 1999-2003 MOREnet. All rights reserved. Reviewed February 10, 2003.
Contact techsupp@more.net. DMCA and other copyright information.
Site Information: Copyright, accessibility, privacy and other information about this site.
PageMinder: Receive an e-mail notice when this page updates.

Search MOREnet  Advanced Search