Digital Subscriber Line Access Multiplexer (DSLAM) Example Design

Digital Subscriber Line Access Multiplexer (DSLAM) Example Design
Table 5.
Test Case Descriptions and their Files
Test
Case Description
NetworkTraffic.dll
(all file names start with:
dslam_proc_2ixp_)
NetSim.dll
(all file names start with:
dslam_proc_2ixp_)
NetSim TCS File
(all file names start with:
dslam_proc_2ixp_)
021
022
023
024
025
026
027
028
029
IP LPM with
UBR
IP LPM with
VBR
IP LPM with
CBR
IP 5TUPLE
with UBR
IP 5TUPLE
with VBR
IP 5TUPLE
with CBR
IP LPM with
CBR/VBR/
UBR
IP 5TUPLE
with CBR/
VBR/UBR
IP LPM and
IP 5TUPLE
with CBR/
VBR/UBR
test_case_021.ind test_case_021_netsim.ind test_case_021.tcs
test_case_022.ind test_case_022_netsim.ind test_case_022.tcs
test_case_023.ind test_case_023_netsim.ind test_case_023.tcs
test_case_024.ind test_case_024_netsim.ind test_case_024.tcs
test_case_025.ind test_case_025_netsim.ind test_case_025.tcs
test_case_026.ind test_case_026_netsim.ind test_case_026.tcs
test_case_027.ind test_case_027_netsim.ind test_case_027.tcs
test_case_028.ind unsupported unsupported
test_case_029.ind test_case_029_netsim.ind test_case_029.tcs
030 Flow Control test_case_030.ind unsupported unsupported
8.0 Performance
The overall performance of the system is currently limited by the traffic shaping/scheduling and
transmit portion of the application, and has been measured at speeds just over 400 Mbs.
9.0 Limitations
The current implementation of the example design only allows for traffic to pass from the DSL
aggregator to the WAN, and not vice versa. The design could be relatively easily extended to cover
traffic in the other direction, but the input from the WAN would need to deliver a custom header
similar to the one provided by the aggregator, with information on physical ports to send to.
Similarly, the design only implements the AAL5 segmented ATM transport protocol for the WAN.
The code has hooks built in for handling both Ethernet and frame relay, which can be filled in to
that end. This version also doesn’t implement the StrongARM side of packet exception handling,
nor does it implement any PCI functionality. The example design also uses a custom header for
physical port information, which, as of the initial release of this document, is not producible with
our current hardware. Therefore, the design has only had limited software testing, and has, as of
Application Note 37