To Previous Chapter To Table of Contents To Bottom of Page To Next Chapter

CS457/557 - Computer Networks: Chapter 9 - Connecting LANs: Inter-Networking

Objectives

  1. Understand the rationale, methodology, technology, and business analysis for standalone PCs accessing a LAN remotely for either use of LAN services or LAN management purposes.
  2. Understand the rationale, methodology, technology, and business analysis for standalone PCs accessing a mainframe remotely.
  3. Understand the rationale, methodology, technology, and business analysis for connecting two or more local area networks.
  4. Understand the additional consequences, advantages, and limitations involved when connecting LANs of differing topologies, network operating systems, media, or protocols.
  5. Understand how micro-mainframe PC connectivity solutions may vary in different technological environments
  6. Understand major characteristics of IBM SNA and the direction of the architecture in terms of integration with the LAN environment.
  7. Understand the current state of internetworking technology as well as future trends in internetworking.
  8. Understand the importance of the OSI model to effective internetworking analysis and design.

Introduction

internetworking - transmitting data into and out of a LAN

  1. Dialing into and out of a LAN
  2. LAN-to-LAN connections
  3. Micro-to-mainframe / minicomputer connectivity

Internetworking Category 1: Dialing Into and Out of the LAN

Business Uses of Remote Computing

Needs Analysis

  1. Exchange e-mail
  2. Upload/download files
  3. Run interactive applications remotely
  4. Utilize LAN attached resources

Physical Topology

  1. Modem connection of a LAN attached PC
  2. Communications server
  3. LAN modem

Logical Topology

Remote Operation Mode: Where does the Processing Occur?
  1. Remote client operation mode
  2. Modem remote control operation mode

Technology

Hardware Software
Modems
Communications servers
LAN modems
Redirector hardware
Remote control software
Comm server software
Redirector software

ACCESS POINT 1: REMOTE PC TO LOCAL LAN-ATTACHED PC

ACCESS POINT 2: COMMUNICATIONS SERVERS

ACCESS POINT 3: LAN MODEM OR DIAL-IN SERVER

modem attaches directly to the network

Dialing Out from the LAN

requires a modem server and a redirector to route traffic via network card to modem

Internetworking Category 2: LAN-to-LAN Connections

Overall Internetworking Design Strategies

LANs can differ in
  1. Network architecture
  2. Media
  3. NOS
  4. OS
InterLAN devices:

Bridging

80/20 rule: 80% of all LAN traffic should stay local with 20% being forwarded across the bridge

Addressing

Advantages

Limitations

Routing

routers only reads data packets addressed to it, confirms the existence of the destination address, and chooses the best path for the data packet to reach its destination

Addressing

Advantages

Limitations

- more complicated to configure and manage

Switching

used in microsegmentation by creating point-to-point connections using ASIC (application-specific integrated circuit) chips

Addressing

uses MAC addresses to build a switched connection

Advantages

produces dramatic increases in bandwidth; used in virtual LANs

Limitations

more complicated to manage; more expensive than simple bridging

The OSI Model and Internetworking Devices

Repeaters: Layer 1 -- The Physical Layer

  1. Repeat signal by regenerating, retiming, and amplifying the signal
  2. Pass all signals between attached segments
  3. notread destination addresses of data packets
  4. allow for the connection of different types of media
  5. extend overall LAN distance effectively by repeating signals between LAN segments

Bridges: Layer 2 -- The Data Link Layer

bridges are more discriminating (bridge reads the destination addressof each data frame and decides whether the destination is local or remote and only allows packets with remote addresses to "cross the bridge"

bridges also check the source address of each frame and adds it to a table of known local addresses

forward-if-not-local

MAC Sublayer Protocol: Types of Bridges

  1. Transparent bridges (both LANs must be the same type)
  2. Translating bridges (multiprotocol bridges contain a format converter)
  3. Encapsulation bridges (bridges Ethernet & FDDI)
  4. Source routing bridges (source routing Token Ring to Ethernet)

Source Routing - data contains path instructions for bridge

Data Storms - can result in a looping topology (requires IEEE 802.1 -spanning tree algorithm)

Bridge performance can be measuered by the filtering rate (packets/sec) and the forwarding rate (packets/sec)

Wireless Bridges

Preamble Address (64 bit) Destination Address(48 bit) Source Address(48 bit) Type(16 bit) Data(46-1500 bytes) 32 bit CRC
used for timing / synchronization bridges uses to determine which side of the bridge bridge uses to build "known local nodes" identifies type of network layer protocol data packets error detection

Routers: The Network Layer Processors

(Network layer establishes, maintains, and terminates the link between two points on the network

Functionality

Data link header Network Layer header Source Address Destination Address Data field Data link trailer

Determining the Best Path

  1. number of intermediate hops
  2. speed/condition of the communications circuits
  3. NOS protocol
Network Layer Protocol NOS or Protocol Stack Name
IPX Netware
IP TCP/IP
VIP Vines
AFP Appletalk
XNS 3Com
OSI Open Systems
Data-link control protocols processed by some routers:
LAT DecNet
SNA/SDLC IBM SNA
NetBEUI Windows-based LANs

Routing Protocols

Routing Protocol Acronym Routing Protocol Name Associated Protocol Suites
RIP Routing Information Protocol XNS, IPX, TCP/IP
OSPF Open Shortest Path First TCP/IP
IS-IS Intermediate System to Intermediate System DECNET, OSI
RTMP Routing Table Maintenance Protocol Appletalk
PPP Point-to-Point Protocol Internet standard that replaces SLIP
RTP Router Table Protocol Vines

Internetworking Category 3: LAN-to-Mainframe/Minicomputer Connectivity

gateway - hardware device used to connect different types of networks

Micro-Mainframe Hierarchical Network

Classic SNA Architecture

SNA - systems network architecture
Front-end processor (FEP) (IBM3745) - compuer that offloads the communications processing from the mainframe; also known as a communications controller
Cluster Controller (IBM 3174, 3274) - device that allows connection of 3270 terminals and LANs
PCs as 3270 Terminals requires a 3270 protocol conversion controller (can be emulated with software & a modem)
3270s are connected using RG-62 coax cable
Coax muxes (multiplexer) is required to connect large numbers of terminals to the cluster controller
Balun - used to convert BNC connector to UTP RJ-45 connector

SNA Architecture

Layer Number Layer Name Function
7 Transaction Services provides network management services. controls document exchange
6 Presentation Services Formats data, data compression & data transformation
5 Data Flow Control synchronous exchange of data supports communications session for end-user applications. (assures reliability)
4 Transmission Control Matches the data exchange rate, establishes, maintains, and terminates sessions. Guarantees reliable delivery of data between end-points. Error control, flow control
3 Path Control
Overall layer: creates the link between two end-points for the transmission control protocols to manage
Virtual Route Control Create virual route, manages end-to-end flow control
Explicit Route Control Determines actual end-to-end route for link between end nodes via intermediate nodes
Transmission Group Control manages to use multiple lines to assure reliability and load balancing
2 Data Link Control Establishes, maintains, and terminates data transmission between two adjacentnodes. uses SDLC
1 Physical Control provides physical connections specifications from nodes to shared media
SDLC (synchronous data link control) - nonroutable protocol (has no network layer address)

Three SNA/LAN Integration Challenges

  1. reduce unnecessary traffic
  2. find way to prioritize SNA traffice to avoid time-outs
  3. find way to allow internetwork protocols to transport, or route, SDLC frames

Four Possible SNA/LAN Integration Solutions

  1. Attach token ring LAN to the Cluster controller (only handles #3)
  2. encapsulation (passthrough, tunneling) - stuff each SDLC frame into an IP "envelope"
  3. SDLC conversion - uses a SDLC converter to change SDLC frames into token ring frames
  4. use protocol independent routers - adds a MAC layer address to each frame received

APPN (advanced peer-to-peer network)

allows all attached devices to talk directly with each other without going through the mainframe

New SNA

Applications
  1. Conversion (CPI-C)
  2. Remote Procedure Call (RPC)
  3. Message Queueing (MQI)
  4. Standard applications
  5. Distributed services
Multivendor application support
  1. APPC OSI/TP
  2. OSF DCE
  3. FTAM X.400, TELNET, FTP
  4. Data directory, security, recovery time
Common Transport Semantics
Multiprotocol transport networking
  1. SNA, APPN
  2. TCP/IP
  3. OSI
  4. NetBIOS, IPX
Network Architecture
  1. LANs frame relay
  2. X.25 cell packet
Media physical

DECNET

Internetworking Category 4: Integration of LANs and the UNIX Environment

TCP/IP - Transmission Control Protocol / Internet Protocol
Layer OSI INTERNET Data Format Protocols
7 Application Application Messages / Streams TELNET
FTP
TFTP
SMTP
SNMP
CMOT
MIB
6 Presentation " " "
5 Session " " "
4 Transport Transport or Host-Host Transport Protocol Packets TCP, UDP
3 Network Internet IP Datagrams IP
2 Data Link Network Access Frames
1 Physical " "
Multiple Protocol Stacks - loading multiple network & transport layer protocols in a single client PC
requirres multiple protocol device drivers (NDIS (network driver interface specification) or ODI (open data-link interface))
NOS Transport Protocol
UNIX TCP/IP or UDP/IP
MS Windows NETBEUI
Netware SPX/IPX
DECNET LAT
VINES VIPC/VIP
DOS based LANs NETBIOS
APPLETALK ATP
TCP/IP Gateway - place multiprotocol software on the server
ex. Netware NFS

Important Features and Options for Multiprotocol Software

  1. Which Protocols Need Supporting?
  2. What is the Client Operating Environment?
  3. What NICs and Device Drivers are available?
  4. Ease of Use/Transparency?
  5. Cross-Platform E-mail Support?
  6. Terminal Emulation?

Internetworking Category 5: Macintosh Integration

Needs:
  1. file sharing
  2. printer sharing
  3. file transfer
  4. E-mail

Compatability Issues

Network Architecture

Localtalk - 230.6 Kbps using DIN plugs [used mainly for peer-to-peer networks]
AppleTalk - suite of protocols compliant with OSI Model
AppleTalk can run over Ethernet or Token ring
7-Application
AppleTalk Filing protocol(AFP) Postscript
6-Presentation
AppleTalk Filing protocol(AFP) Postscript
5-Session
AppleTalk Data Stream protocol(ADSP) Zone Information Protocol (ZIP) Appletalk Session Protocol (ASP) Printer Access Protocol (PAP)
4-Transport
Routing table Maintenance Protocol (RTMP) AppleTalk Echo Protocol (AEP) AppleTalk Transaction Protocol (ATP) Name Binding Protocol (NBP)
3-Network Datagram Delivery Protocol (DDP)
2-DataLink
TokenTalk Link Access Protocol (TLAP) EtherTalk Link Access Protocol (ELAP) LocalTalk Link Access Protocol (LLAP)
1-Physical
token ring hardware ethernet hardware Localtalk hardware
Router supports Appletalk Protocols while Gateways translate AppleTalk protocols into SNA / DECNET

10BASET Hubs support Appletalk over Localtalk and Ethernet

Netware, Vines & Windows include features for Macintosh integration

Internetworking in Perspective


Slides


Review Questions(due Nov. 10): 7, 34

To Previous Chapter To Table of Contents To top of page To Next Chapter