Paradyne FrameSaver SLV 9124, Technical Reference

Page: 39 / 346

Typical Applications
3-7
9124-A2-GH30-00 June 1999 - Preliminary
Mixing FrameSaver Units in Applications
Deciding which frame relay FrameSaver unit is needed at a central or remote site
is a matter of evaluating the site’s traffic volume to determine the amount of
network access required – FT1/T1 or 56/64 kbps.
A large central site’s requirement for high-speed and high-volume indicates the
need for a FrameSaver 9124 unit at this site. Connecting an RMON probe to the
FrameSaver unit and using NMS application software that supports RMON MIBs
will provide full remote monitoring capability at the site.
However, the amount of traffic at a remote or central site may not require the
speed of T1, and FrameSaver 9624 units can be used.
In addition, not all remote sites need to have the same frame relay FrameSaver
unit. They can have:
H
All FrameSaver 9624 units at the remote sites.
H
FrameSaver 9124 units providing voice service (e.g., SDN, Megacom, etc.) at
some remote sites and FrameSaver 9624s at others.
H
FrameSaver 9124 or 9624 units at remote sites where RMON is desired or
needed, and FrameSaver 9120s at other remote sites. However, using
non-SLV units like 9120s instead of SLV units eliminates any benefits that are
gained by using a FrameSaver 9124 or 9624.
NOTE:
The additional capabilities provided by FrameSaver SLV units include:
— Intelligent latency and delivery verification.
— TruePut data delivery.
— RMON data collection and SLV reporting.
— Configurable alarm thresholds and custom history buckets.
— Interoperability with NetScout applications.
As a result, mixing SLV and non-SLV units is not recommended even
though FrameSaver SLV units support non-SLV FrameSaver units.