GL Communications, Inc. Emulation using Client-Server MC-MLPPP

The Multi-Class Extension to Multi-Link PPP allows a sender to fragment the packets of various priorities into multiple classes of fragments, and allows high-priority packets to be sent between fragments of lower priorities. MLPPP bundles multiple link-layer channels into a single network-layer channel. Data sent through this channel will be distributed among all the links. It is a technique used to derive larger bandwidth pipe by aggregating smaller bandwidth pipes e.g. from multiple T1s or E1s. GL's flexible and versatile MC-MLPPP Emulator is GUI based WCS client, which simulates MC-MLPPP and PPP protocols over T1/E1 links. The unit is capable of generating and receiving MC-MLPPP/PPP traffic (with or without impairments). Traffic source can be sequence number, HDL files (containing packets/frames), flat binary file, user-defined frames (ASCII HEX file), and Ethernet data. MLPPP emulator can be configured as a router or as a bridge to establish connection and route traffic between LANs. Main Features: Performs MC-MLPPP as well as PPP simulation. Supports LCP with the following negotiation options. PPP options: MRU (Maximum Receive Unit), ACFC (Address and Control Field Compression), PFC (Protocol Field Compression), Magic Number, LQR (Link Quality Report), Reporting Period in tens of millisecond, Authentication, and Link Bandwidth Control. MLPPP Options: MRRU (Maximum Received Reconstructed Unit), Short Sequence Number Format, Long sequence header format, Endpoint Discrimination, PPP in MLPPP, and Multi-class option. Multi-Class Options: Multilink Header Format. Supports the following NCPs - IPCP - RFC 1332 (The PPP Internet Protocol Control Protocol) and RFC 1877 (PPP Internet Protocol Control Protocol Extensions for Name Server Addresses) standards. BCP - RFC 3518 (Point-to-Point (PPP) Bridging Control Protocol) standard. PPPMuxCP - RFC 3153. Payload traffic generation and verification using Sequence number, HDL file (containing packets/frames), Flat Binary file, Ethernet traffic, and User defined frames (ASCII HEX file) for each class independently. Transmit and receive Ethernet traffic over T1E1 links by operating either in bridge or router mode. Provides PPP Multiplexing feature to send / receive multiplexed PPP and MLPPP frames confirming to RFC 3153. Supports up to 16 T1/E1 ports. Supports PAP and CHAP authentication protocols Differential link delay insertion between PPP links during transmission. User configurable timers and counters like Restart-timer, Max-Configure, Max-Terminate, and Max-Failure. User configurable bandwidth using flags. Supports hyper channels with discontinuous (sparse) timeslots. Supports full or fractional timeslots for PPP Link. Supports Fragmentation and Reassembly at MLPPP level. Supports Van Jacobson Compression (RFC 1144) and IP Header Compression (RFC 2507 and RFC 3544). Supports RTP Compression enabling IP/UDP/RTP compression conforming to RFC 2508. Dynamically add/remove (open/close) PPP links without loss in data. Supports various impairments at PPP layer - CRC error, frame error, frame duplication, and more. Supports various Fragment/Packet impairments for each Class at MLPPP level. Provides detailed PPP and MLPPP statistics. Provides detailed test (Tx/Rx) results per class / per link in GUI as well as through log file in command line. Ideal solution for automated testing using command line scripts. Support for HDLC framing with CRC16, CRC32 or without CRC. References RFC 1661 Point-to-Point Protocol (PPP). RFC 1662 PPP links in HDLC framing. RFC 1990 Multi-link PPP bundles. RFC 2686 Multi-class extensions to PPP. RFC 1332 PPP Internet Protocol Control Protocol. RFC 1877 PPP Internet Protocol Control Protocol Extensions for Name Server Addresses. RFC 3518 PPP Bridging Control Protocol. RFC 1144 VanJacobson Compression. RFC 3544 IPHC Compression. RFC 2507 only IP Compression. RFC 2508 Compressed RTP. RFC 3153 PPP Network Control Protocol for PPP Multiplexing (PPPMuxCP).