Paradyne FrameSaver SLV 9124, Technical Reference

Page: 289 / 346

IP Addressing
B-3 9124-A2-GH30-00 June 1999 - Preliminary
Customer Management
When customers are connected to the internet, IP addresses are limited to the
number of IP addresses they own. Using FrameSaver units, private addressing
can be used for the network without taking away from the customer’s pool of
IP addresses.
The illustration below shows this scheme of public and private IP addressing,
which is like having two networks in one.
Frame
Relay
Router 10.10.10.1
99-16224-01
Frame Relay
Network
Frame
Relay
Router
10.10.10.2
Frame
Relay
Router
10.10.10.3
NMS
Physical Connection
PVC Connection
DLCI 200/EDLCI 2
DLCI 200
DLCI 210
DLCI 210/EDLCI 2
DLCI 900
DLCI 200
DLCI 210
135.18.2.1
135.18.2.2
135.18.2.3
Both public and private addressing scheme networks share the near-to-far end
customer-ordered DLCIs (200 and 210) so that user data is multiplexed with
management data using EDLCIs (multiplexed DLCIs, e.g., DLCI 200/EDLCI 2).
Management of the far-end devices is performed via the EDLCIs, creating a
communication path within a communication path.
Using the FrameSaver RIP feature, far end FrameSaver devices can be identified
automatically and reported to the management station via local DLCI 900, which
is configured between the central-site FrameSaver unit and its router. This
DLCI is dedicated to management and is not propagated to the network by the
FrameSaver unit. The DLCI terminates in the FrameSaver unit and is only used
for management.