Table of Contents
Advertisement
Installing and Setting Up the 9820 FrameSaver Unit
The following sections guide you through installation and setup of a FrameSaver unit.
It is assumed that the FrameSaver unit is configured for factory default settings at the
start of installation.
For correct operation of the unit's Hardware Bypass feature, both the network and user
port interface types need to be the same, and the combined length of their cables
should not exceed the maximum length limitation for the interface type (EIA-530A, V.35,
or X.21). In addition, both the source and primary destination DLCI numbers need to be
the same.
See the following illustration for an example of a network that includes FrameSaver
units at the central site (e.g., the company's headquarters in Munich) and the remote
sites (e.g., branch offices in London and Singapore). User data PVCs provide
LAN-to-LAN connectivity between the central site and the remote sites.
Munich
Headquarters
NMS
Frame
Central Site
Relay
FrameSaver
Router
DLCI/EDLCIs:
100/0 User Data for London
200/0 User Data for Singapore
100/2 Management Data for London
200/2 Management Data for Singapore
From a network management perspective, the central site FrameSaver unit should be
configured for management from a Network Management System (NMS), through
either the attached router as shown in the above figure, or through the Network
Operations Center (NOC) router (for management by the Network Service Provider).
Multiple management PVCs then connect the central site unit to the remote site units
using Paradyne's proprietary PVC multiplexing method (embedded DLCIs).
NTU
Port NET
Unit
NTU
NTU
NTU
NTU
NTU
NTU
100
DLCI/EDLCIs:
100/0 User Data
100/2 Management Data
Frame
Relay
Network
200
NTU
NTU
NTU
DLCI/EDLCIs:
200/0 User Data
200/2 Management Data
7
London Office
London Office
London Office
Remote Site
FrameSaver
Unit
NET Port
Remote Site
FrameSaver
Unit
NET Port
Singapore Office
Frame
Relay
Router
Frame
Relay
Router
98-15989-01
Advertisement
Table of Contents
