Patton electronic 2800 - Manual (Page 2)

Page 2 of 2
Product Brief
Solution Description
Rapid service deployment is the key to grabbing market share, the lifeblood of carrier business economics. Sometimes
the infrastructure needed to support subscriber services is not in place, creating delays that can cost millions in long-term
lost revenues. Other times subscribers prefer to avoid emerging technologies. To combat these ills carriers with
inexpensive T1/E1 circuits can reuse the already installed TDM network to bridge customer Ethernet traffic, avoiding
endless hours of complex IP routing configurations and providing their subscribers a right-sized service.
Problem Issue Impact Our Solution
Service Providers
are Losing Market
Share A single T1/E1 is not fast
enough for customers, a
T3/E3 is overkill Millions of dollars lost in
potential long-term
revenue streams Bond well-known T1/E1
circuits together for
greater speed
Complex Network
Infrastructure
Installations Complex equipment is
installed for simple
access applications
Slows the pace of
service provisioning and
makes troubleshooting
problems difficult Deliver plug-and-play
broadband access with
routed edge services
over standard facilities
Customers
resisting switch to
broadband Customers still distrust
the reliability of
broadband service Customers are
demanding TDM
solutions Provide broadband-
speeds over bonded
TDM circuits
Unique Selling Position
The IpLink™ Model 2888 Multi-Megabit Inverse Mux provides broadband Ethernet/IP bandwidth over existing TDM
circuits, increasing service deployment speed and reach, reducing configuration complexity, and enabling low-cost
immediate service roll-out without changes to the network infrastructure.
Top FAQs
Q. If all my Q. If all my Q. If all my Q. If all my traffic is IP why should I use Ethernet bridging? traffic is IP why should I use Ethernet bridging? traffic is IP why should I use Ethernet bridging? traffic is IP why should I use Ethernet bridging?
A. A. A. A. The other alternative, configuring a router for load-balancing can be a difficult task. First of all, a router can load
balance outbound traffic only. To get bidirectional load balancing requires complex configuration at both ends.
Secondly, both routers must be configured to assign the same administrative distance and cost to a destination. Lastly,
load balancing at the IP packet layer creates a situation where packets can reach the destination out of order, creating a
problem for streaming media such as video. By using Ethernet bridging and relying on ML-PPP, the configuration is
simplified and the out of order packet problem eliminated.
Q. What happens if one of my T1/E1 fails, does my entire link go Q. What happens if one of my T1/E1 fails, does my entire link go Q. What happens if one of my T1/E1 fails, does my entire link go Q. What happens if one of my T1/E1 fails, does my entire link go down? down? down? down?
A. A. A. A. No, with ML-PPP, if a T1/E1 goes down, the Ethernet traffic will continue to flow across the active links. When the
failed link comes back up, full bandwidth is automatically restored without manual intervention.
Q. Does the Inverse Mux use ATM Q. Does the Inverse Mux use ATM Q. Does the Inverse Mux use ATM Q. Does the Inverse Mux use ATM to multiplex the T1/E1 circuits? to multiplex the T1/E1 circuits? to multiplex the T1/E1 circuits? to multiplex the T1/E1 circuits?
A. A. A. A. No. The Inverse Mux uses Multi-Link PPP (ML-PPP) which is 18% more efficient than ATM when using 256 byte
packets. Efficiency increases further with packet sizes of over 1,000 bytes which are typically used by streaming video.
Q. Q. Q. Q. Does the IpLink Does the IpLink Does the IpLink Does the IpLink™ ™ ™ ™ Inverse Mux support VLANs Inverse Mux support VLANs Inverse Mux support VLANs Inverse Mux support VLANs????
A. A. A. A. Yes. The Inverse Mux can be configured to apply QoS based on VLAN tags as well as tag untagged VLAN traffic. It
can likewise transparently pass VLAN, Cisco ISL and MAC-in-MAC (PBB) frames as well as MPLS tagged traffic.