ATM Option System Reference - Comtech EF Data

ATM Option
NetPerformer ® System Reference

COPYRIGHTS AND DISCLAIMERS
Published Date: April 2011
Document # 1612
This publication contains information proprietary and confidential to Memotec Inc. Any reproduction,
disclosure or unauthorized use of this publication is expressly prohibited except as Memotec Inc. may
otherwise authorize in writing.
Memotec Inc. reserves the right to make changes without notice in product or component design as warranted
by evolution in user needs or progress in engineering or manufacturing technology. Changes which affect the
operation of the unit will be documented in the next revision of the manual.
We have made every effort to ensure the accuracy of the information presented in our documentation.
However, Memotec assumes no responsibility for the accuracy of the information published. Product
documentation is subject to change without notice. Changes, if any, will be incorporated in new editions of
these documents. Memotec may make improvements or changes in the products or programs described within
the documents at any time without notice. Mention of products or services not manufactured or sold by
Memotec is for informational purposes only and constitutes neither an endorsement nor a recommendation for
such products or services.
Memotec Inc. is a wholly owned subsidiary of Comtech EF Data Corp., and its parent company Comtech
Telecommunications Corp (NASDAQ: CMTL).
AccessView, CXTool, CX-U Series, CX-UA Series, AbisXpress, NetPerformer, AccessGate, ACTView, SDM-
8400, and the SDM-9000 series of products are either registered trademarks or trademarks of Memotec Inc.in
Canada, the United States of America, and in other countries.
Windows is a registered trademark of Microsoft Corporation in the United States and other countries.
Any other trademarks are the property of their respective companies.
Copyright © 2011 Memotec Inc.
Memotec Inc.
7755 Henri Bourassa Blvd. West
St-Laurent, Quebec
Canada H4S 1P7
Tel.: (514) 738-4781
FAX: (514) 738-4436
www.memotec.com

Contents
Chapter 1: Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1. 1 About Asynchronous Transfer Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.1.1 ATM Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.1.2 ATM Layers and Sublayers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1. 2 Principles of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.2.1 ATM Protocols and AAL Service Classes . . . . . . . . . . . . . . . . . 1-4
1.2.2 Error Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.2.3 Cell Transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.2.4 ATM Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
1.2.5 PVCs Versus SVCs in the Network . . . . . . . . . . . . . . . . . . . . . . 1-6
1.2.6 User to Network Interface (UNI). . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1.2.7 ATM Addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1.2.8 Service Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
1. 3 ATM Support on the NetPerformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
1.3.1 PowerCell in the ATM Network . . . . . . . . . . . . . . . . . . . . . . . . 1-16
1.3.2 AAL1 Circuit Emulation Services (CES). . . . . . . . . . . . . . . . . . 1-16
1.3.3 Frame Relay/ATM Service Interworking (FRF.8) . . . . . . . . . . . 1-18
1.3.4 LLC Encapsulation (RFC-1483) . . . . . . . . . . . . . . . . . . . . . . . . 1-22
1.3.5 PPP Over AAL5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
1.3.6 ATM Multiplex Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
1. 4 NetPerformer Architecture and ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
1.4.1 NetPerformer Implementation of ATM SVCs . . . . . . . . . . . . . . 1-27
Chapter 2: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2. 1 About the ATM Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2. 2 Before You Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.2.1 Is the ATM Option Already Installed?. . . . . . . . . . . . . . . . . . . . . 2-3
2. 3 Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2. 4 Configuring the Global Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.4.1 Tips for Configuring Shared RAM Allocation . . . . . . . . . . . . . . . 2-9
2. 5 Configuring the Digital Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
2. 6 Configuring the ATM Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
2. 7 Configuring the ATM PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Memotec Inc.

Memotec Inc.
2.7.1 PVC in ATMPVCR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
2.7.2 PVC in AAL1 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
2.7.3 PVC in FRF.8 Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2.7.4 PVC in RFC1483 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2.7.5 PVC in ATMPPP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
2.7.6 PVC in ATM-MULTIPLEX Mode . . . . . . . . . . . . . . . . . . . . . . . 2-25
2. 8 Configuring the ATM SVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
2.8.1 SVC in ATMPVCR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
2.8.2 SVC in FRF.8 Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
2.8.3 SVC in RFC1483 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
2.8.4 SVC in ATMPPP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
2. 9 Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
2.9.1 Using the NetPerformer as an Integrated Access Device . . . . 2-33
2.9.2 Using the NetPerformer as an ATM Multiplexer . . . . . . . . . . . 2-36
Chapter 3: Monitoring and Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3. 1 About the Statistic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3. 2 Status of ATM SVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.2.1 Displaying the SVC Counters (DC/SVC) . . . . . . . . . . . . . . . . . . 3-4
3.2.2 Displaying the SVC States (DS/SVC) . . . . . . . . . . . . . . . . . . . . 3-5
3.2.3 Displaying the SVC Errors (DE/SVC) . . . . . . . . . . . . . . . . . . . . 3-8
3.2.4 Continuous Display of SVC States (DSVC). . . . . . . . . . . . . . . . 3-8
3. 3 Status of ATM PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
3. 4 Viewing Reserved Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
3. 5 Status of ATM Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Chapter 4: SE/SLOT/CHANNEL Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . 4-1
4. 1 Idle cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4. 2 Idle cell payload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4. 3 HEC coset function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4. 4 Scrambling function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4. 5 UNI Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4. 6 UNI Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4. 7 ATM Signaling Channel VPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4. 8 ATM Signaling Channel VCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4. 9 ILMI Channel VPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

4. 10 ILMI Channel VCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4. 11 Accept Incoming ATM AAL1 Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Chapter 5: SE/PVC Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5. 1 PVC number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5. 2 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5. 3 ATMPVCR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.3.1 VPI address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.3.2 VCI address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.3.3 Service category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.3.4 Peak cell rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.3.5 Sustainable cell rate (SCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.3.6 Maximum burst size (MBS) in cells . . . . . . . . . . . . . . . . . . . . . . 5-7
5.3.7 Remote unit name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.3.8 Timeout (msec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.3.9 Number of retransmission retries . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.3.10 Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.3.11 IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.3.12 Subnet mask (number of bits) . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.3.13 NAT enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.3.14 NAT rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.3.15 NAT side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.3.16 IP RIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.3.17 IP RIP TX/RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.3.18 IP RIP authentication type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.3.19 IP RIP password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.3.20 OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.3.21 OSPF Area ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
5.3.22 OSPF Transit delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
5.3.23 OSPF Retransmit interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
5.3.24 OSPF Hello interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
5.3.25 OSPF Dead interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
5.3.26 OSPF Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
5.3.27 OSPF Metric cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
5.3.28 IP multicast active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
5.3.29 IP multicast protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
5.3.30 IPX RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
5.3.31 IPX SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
5.3.32 IPX network number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
5.3.33 Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
5.3.34 Broadcast group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Memotec Inc.

Memotec Inc.
5.3.35 Maximum number of voice channels . . . . . . . . . . . . . . . . . . . . 5-19
5.3.36 Maximum Voice Channels If High Priority Data. . . . . . . . . . . . 5-20
5.3.37 Cell Packetization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
5. 4 AAL1 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
5.4.1 Number of subchannels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
5.4.2 Super frame format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
5.4.3 Local inbound voice level (db) . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
5.4.4 Local outbound voice level (db) . . . . . . . . . . . . . . . . . . . . . . . . 5-23
5.4.5 Echo canceler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
5.4.6 Double talk threshold (db) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
5.4.7 Idle code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
5.4.8 Jitter buffer (ms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
5.4.9 Signaling type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
5.4.10 TONE type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
5.4.11 TONE regeneration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
5.4.12 TONE ON (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
5.4.13 TONE OFF (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
5.4.14 Pulse make/break ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
5.4.15 Delete digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
5.4.16 Fwd digits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
5.4.17 Fwd delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
5.4.18 Fwd type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
5. 5 FRF.8 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
5.5.1 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
5.5.2 DLCI address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
5.5.3 Committed Information rate . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
5.5.4 Burst Information rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
5.5.5 Header translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
5.5.6 ATM CLP bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
5.5.7 ATM EFCI bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
5.5.8 Frame relay DE bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
5.5.9 Frame relay FECN bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
5.5.10 Congestion queue size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
5.5.11 Maximum queue size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
5. 6 RFC1483 Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
5.6.1 BRG connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
5.6.2 IP connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
5.6.3 Frame size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
5. 7 ATMPPP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
5. 8 ATM-MULTIPLEX Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38

5.8.1 ATM Adaptation Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
5.8.2 Remote PVC number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
5.8.3 Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Chapter 6: SE/SVC Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6. 1 SVC number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6. 2 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6. 3 ATMPVCR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.3.1 SVC Destination address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.3.2 SVC Local Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.3.3 SVC Destination E.164 Address . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.3.4 SVC Local E.164 Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
6.3.5 Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
6.3.6 Call Delay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
6.3.7 Call Retry Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
6.3.8 Peak cell rate (PCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
6. 4 FRF.8 Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
6. 5 RFC1483 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
6. 6 ATMPPP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Memotec Inc.

Memotec Inc.

Product Overview
1
Memotec Inc. 1-1

ATM Option
1.1 About Asynchronous Transfer Mode
Asynchronous Transfer Mode (ATM) provides a viable and popular internetworking
solution for high-volume networks with disparate traffic types. The NetPerformer’s
support of the ATM cell-based traffic structure permits the integration of a wide variety of
end user devices with an ATM network.
• NetPerformer ATM support is provided as an option under special license
• The ATM Option can be installed on the SDM-9230, SDM-9360, SDM-9380 and
SDM-9585 only.
1.1.1 ATM Feature Overview
Asynchronous Transfer Mode (ATM) is a cell-based technology that permits the
transmission of a variety of traffic types using a common packet structure over public and
private networks. All information is organized into fixed-length cells which can be sent
from a large number of service users in aperiodic (or “asynchronous”) succession. With
the addition of ATM, large networks can integrate voice, data and video more efficiently,
and maximize service to all destinations while reducing bandwidth requirements.
• The ATM structure is based on the idea of a uniform cell size for all payload
types.
• It uses standardized ATM packets, or cells, with a 5-octet header and 48-octet
payload.
- The header defines the source and destination, flow control information, payload
type, a Cell Loss Priority Indicator (CLP) and a Header Error Check
(HEC) that is capable of correcting single-bit errors in the header.
- The structure of the payload section can differ, allowing for a variety of traffic
types to be sent in the same way.
- A virtual circuit is set up from source to destination before transmission, and
the packets are then sent along this path in sequence.
• To support both voice and data, ATM networks are able to adapt to their differences.
- Uncompressed voice is generated at a constant rate, whereas for data, the bit
rate can vary.
- Voice circuits are always synchronous, and must maintain strict adherence to
an internal clock. Data transfer is often asynchronous, and its timing is irrelevant.
- Transmission delays must be avoided for voice, but can be tolerated for data.
- The bandwidth for voice remains constant through time, but tends to be bursty
for data. Data applications often require flexible bandwidth capabilities such
as Bandwidth On Demand.
With ATM, high bandwidth requirements are met by using a greater number of cells. The
number of cells are reduced during low traffic periods. Greater efficiency, higher speeds
1-2 Memotec Inc.

Product Overview
and higher capacity are a result of:
• Uniform cell size, which facilitates both transmission and switching,
• Reduced flow control and error handling requirements.
1.1.2 ATM Layers and Sublayers
ATM works through three distinct layers as it processes and transmits data from one end of
the user application to the other:
• ATM Adaptation Layer (AAL), where data from a user application is segmented
to proper length and some control and housekeeping features are added to
make a 48-octet payload.
• ATM Layer, where a 5-octet header is attached to the payload.
• Physical Layer, which handles the interface to the transmission media.
The steps are reversed at the receiving unit:
• The cell is passed upward from the physical layer to the ATM layer, which
removes the 5-octet header.
• From the ATM layer the cell goes to the AAL layer, where the payload is reassembled
and passed up to the user layer.
The AAL has two sublayers:
• Convergence Sublayer (CS), which processes the user data according to the
required AAL service class.
• Segmentation and Reassembly Sublayer (SAR), which fragments the data
units at the transmitting end so that they can be packaged as a fixed-sized payload.
At the receiving end, the SAR reassembles the payloads from several cells
back into the high-level protocol units.
Memotec Inc. 1-3

ATM Option
1.2 Principles of Operation
1.2.1 ATM Protocols and AAL Service Classes
All ATM cells look alike, no matter which AAL service class is used to generate their
payload. There are four ATM protocols that handle these service classes: AAL1, AAL2,
AAL3/4 and AAL5. The SDM-9360, SDM-9380 and SDM-9585 support AAL1 and
AAL5 only. The SDM-9230 supports AAL5 only. Refer to the section “ATM Support on
the NetPerformer” on page 1-13 for details on the current product offering.
• AAL1: for use with constant bit-rate traffic that requires constant timing between
source and destination in a connection-oriented mode (a predefined path based on
virtual circuits).
- This protocol is used for AAL Service Class A
- One octet is reserved for timing information and detection of lost or out-ofsequence
cells, leaving an actual payload size of 45 to 47 octets
- Example applications are uncompressed voice, DS1 circuits and constant bitrate
video
- Not available on the SDM-9230.
• AAL2: for use with variable rate traffic that requires constant timing between
source and destination in a connection-oriented mode.
- This protocol is used for AAL Service Class B
- It includes a payload header with the sequence number and information type,
a trailer indicating the number of data octets in the cell, and a CRC to check
the payload contents
- Example applications are packetized voice or video.
• AAL3/4: for use with variable rate traffic that does not require timing between
source and destination, that is, traffic that is sensitive to loss but not to delay.
- This protocol is used for AAL Service Class C (connection-oriented) or Class
D (connectionless)
- The Convergence Sublayer takes user data up to 65,535 octets, adds a header
with a begin tag and buffer allocation information, and a trailer with an end of
data tag and data length indicator. It may also add a pad to ensure that the data
can be cut into 44-octet payloads
- The SAR Sublayer takes this large packet and breaks it up into 44-octet payloads,
adds payload headers and trailers that include sequence numbering,
segment type, multiplexing and length information as well as a payload CRC
- Example applications are Frame Relay and X.25 traffic (Class C), LAN and
Switched Multi-megabit Data Service (SMDS) traffic (Class D)
• AAL5: for use with variable bit-rate traffic in a connection-oriented mode. Also
known as Simple and Efficient Adaptation Layer (SEAL).
1-4 Memotec Inc.

1.2.2 Error Checking
1.2.3 Cell Transmission
Product Overview
- This protocol is used for AAL Service Class C
- The Convergence Sublayer takes user data up to 65,535 octets, adds an 8-octet
trailer and padding (when required) to allow the data to be cut into 48-octet
payloads at the SAR Sublayer
- The last ATM header contains an End of Message flag and the data trailer
with its CRC error check and length of data indicator. There are no trailers at
the payload level
- Example applications are Frame Relay and X.25 traffic
- Supported on all NetPerformer products that can be installed with the ATM
licensed software option.
Unlike some other packet-transmission protocols, no error checking is performed on the
cell payload as it passes from one network node to another. This reduces the amount of
processing each cell requires at each node, and permits faster transmission rates.
• End-to-end error checking of the payload is usually accomplished within the
AAL.
• The only error-checking performed at each node is on the cell header to ensure
proper delivery of the cell.
ATM cells move along Virtual Channels (VCs) within Virtual Paths (VPs):
• Virtual Channel Link: All circuits terminate at the same end point. Several virtual
channel links connected together form a virtual channel connection which
connects ATM users.
• Virtual Path Link: A link carrying bundles of virtual channel links. A virtual
path can carry numerous virtual channels. However, there is no dedicated bandwidth
or facilities.
• A physical facility, such as fiber, can carry numerous virtual paths.
ATM traffic passes over a virtual connection through the network. Two types of
connections are possible:
• Using PVCs: The network administrator determines the path before it will be
used, and reserves it for the ATM traffic.
• Using SVCs: The connection is established at the start of the session, and is disconnected
through special signaling procedures.
NOTE: The NetPerformer solution is based on PVCs. A maximum of 31 VCs can be
configured on the unit.
Memotec Inc. 1-5

ATM Option
1.2.4 ATM Switching
• The ATM header contains a Virtual Channel Identifier (VCI) and a Virtual Path
Identifier (VPI).
- These identifiers provide the address of the next node that the ATM traffic
will pass through.
- The header is read at this node and is passed to the next node via another virtual
channel and path.
VPs and VCs are switched (or cross-connected) according to the vendor-specific
proprietary techniques of each ATM switch used.
• Usually cells are taken from input links and placed into buffers, where they can
be read out to other links. Switch size is a function of buffer speed versus message
delay tolerance.
• The ATM switch can process cells far more rapidly than the transmission rate of
ATM traffic, so there is usually very little switching delay. There are two types of
ATM switches:
- Virtual path switch: Terminates virtual path links, and translates the virtual
path identifier for a group of virtual channels. With this type of switch, all virtual
channels are switched to a new virtual path link.
- Virtual channel switch: Translates both the virtual channel and the virtual
path identifiers, and can switch a virtual channel from one virtual path to
another.
• Quality of Service (QoS) levels are negotiated at the time of service provisioning,
and are application and service dependent.
1.2.5 PVCs Versus SVCs in the Network
As of V10.1, the NetPerformer supports switched virtual circuits (SVCs) on the ATM
licensed option. SVCs are easier to manage and require less human intervention than
permanent virtual circuits (PVCs).
PVCs are predefined virtual connections. The attributes of a PVC, such as its destination,
bandwidth and QoS requirements, must be defined on every ATM switch where the PVC
is accessed, and on each end system using it (see Figure 1-1 on “ATM PVCs in the
Network” on page 1-7). The only information known to the end system is the VPI and
VCI, which are configured on the NetPerformer itself.
• This makes configuring a large number of PVCs very cumbersome for network
providers. Any change to PVC parameters requires manual intervention of the
network provider to reconfigure the NetPerformer.
1-6 Memotec Inc.

Product Overview
• Another difficulty is that resources allocated to a PVC are guaranteed. This
means that even if the PVC is not being used the resources must be reserved by
the network, which detracts from overall network efficiency.
End System A
ATM SW2
PVC1 (VPI=1, VCI=1)
ATM SW1
VPI=1 & VCI=1 ->ATM SW5
ATM SW4
With SVCs, configuration of the virtual connections is pushed to the end system, greatly
simplifying VC management for network providers.
• SVC parameters are configured on the end system (the NetPerformer), and are
used whenever a connection is established.
• The ATM switch uses these parameters to determine whether it can satisfy the
end system requirements, such as bandwidth and QoS. If the resources are unavailable,
the switch can reject a request to establish an SVC.
• Each end system is assigned a unique ATM address, which is used by other end
systems to establish a VC with this node. This is similar to using a telephone
number to place a phone call. ATM addresses are discussed further on See “ATM
Addressing” on page 9..
1.2.6 User to Network Interface (UNI)
UNI (User-to-Network Interface) is the generic name for the various processes responsible
for the exchange of information between an ATM end system and an ATM switch. UNI is
responsible for controlling ATM SVCs. Two components are required to implement
SVCs:
• UNI signaling (see next section)
• ILMI (Integrated Local Management Interface), described on See “Integrated
Local Management Interface (ILMI)” on page 8..
UNI Signaling
ATM SW3
Figure 1-1: ATM PVCs in the Network
ATM SW5
VPI=2 & VCI=2 ->ATM SW1
End System B
PVC2 (VPI=2, VCI=2)
UNI Signaling is responsible for establishing and tearing down SVCs. It is similar in
function to the D-Channel in ISDN.
NOTE: The ITU-T Q.2931 specification, from which the various UNI implementations
are derived, is based on the ISDN specification, ITU-T Q.931.
Memotec Inc. 1-7

ATM Option
The ATM forum has defined three versions of UNI:
• UNI 3.0: Original UNI implementation. Includes basic point-to-point and
point-to-multipoint connections. This version precedes the ITU standardization
of UNI.
• UNI 3.1: Conforms UNI 3.0 to the ITU-T standard.
• UNI 4.0: Adds new functionality to UNI 3.1.
The only UNI 4.0-specific functionality that the NetPerformer currently supports
is the explicit signaling of QoS parameters.
UNI signaling works in the following way:
• The UNI uses a dedicated channel to exchange signaling information between the
switch and the end system.
The channel is selected with the ATM Signaling Channel VPI and ATM Signaling
Channel VCI parameters.
• The end system builds a connection request using the destination ATM address,
the type of connection (AAL1, AAL2, AAL5, etc.), the QoS and bandwidth
requirements.
• The end system sends the connection request over the UNI to the ATM switch.
• The request is routed through the ATM network to the end system corresponding
to the destination address. Along the way, each switch verifies that all QoS and
bandwidth requirements can be fulfilled. If no path exists to meet the requirements,
the call is rejected.
• Once the request reaches the destination, the target end system sends a response
to accept or reject the connection.
Integrated Local Management Interface (ILMI)
The ILMI is a subpart of UNI. It is an SNMP-based protocol that end systems and
switches use to exchange status information and negotiate parameters. It includes services
that provide auto-configuration and service registration, negotiate ATM addresses and
obtain interface statistics.
NOTE: The only ILMI characteristic that the NetPerformer currently supports is
ATM address negotiation.
ILMI uses various standard MIBs to implement its services. All ILMI-related SNMP
requests are exchanged on a dedicated VC. This channel is usually VPI=0, VCI=16, and is
configurable on the NetPerformer digital channel using the ILMI Channel VPI and ILMI
Channel VCI parameters (refer to See “ILMI Channel VPI” on page 5.).
1-8 Memotec Inc.

1.2.7 ATM Addressing
Product Overview
ATM addresses are used to uniquely identify an end system. These addresses identify the
source and destination nodes when establishing SVCs. An end system can have multiple
addresses or accept multiple calls on the same address.
Types of Addresses
The ATM Forum defines two different types of addressing:
• Public networks use E.164 addresses. These addresses can be up to 15 digits
long (8 bytes), and look much like telephone numbers. While E.164 addresses
have a familiar format, they are not practical for private networks. Each address
must be assigned by the carrier, which can get both cumbersome and expensive.
• Private ATM networks use an addressing structure called ATM End System
Address (AESA) that uses a 40-digit address (20 bytes). Several types of AESA
addresses are available:
- DCC format: Includes a Data Country Code (DCC) in the prefix. The DCC
specifies the country in which the address is registered, and is nationally
assigned.
- ICD format: Includes an International Country Designator (ICD) in the prefix.
The ICD identifies an international organization, assigned by the British
Standards Institute.
NOTE: The only difference between DCC and ICD formats is the scope of the organization
that delivers the country code.
- Imbedded E.164 format: Includes an E.164 address in the AESA prefix.
This format is useful when an end system on a private network has to reach an
end system on a public network.
- Local AFI format: Includes only the Authority and Format Identifier (AFI)
in the prefix. This format can be used for an isolated ATM network or when
creating a network for internal purposes only.
Caution: Local AFI addresses must not be used if the ATM
network connects to a public network, since there is no way to
ensure the global uniqueness of these addresses.
All four AESA address formats contain the following:
• AFI: Authority and Format Identifier. This field indicates the format of the
address (ICD, DCC, E.164 AESA or Local AFI).
• DSP: Domain Specific Part, which is further divided into high order (HO-DSP)
and low order (ESI and SEL) fields.
- HO-DSP: High Order Domain Specific Part. The coding of this field is identified
by the same authority that assigned the AESA address.
Memotec Inc. 1-9

ATM Option
1.2.8 Service Categories
- ESI: End System Identifier. A globally unique identifier that is similar to a
MAC address.
- SEL: Selector. A one-byte field that can be used by the end system to discriminate
between different services. This field is not used for ATM routing purposes.
ILMI Address Registration
AESA addresses are not completely predefined. Part of each address is defined by the
network manager, and part of it comes from the switch. The complete address is built
using ILMI address registration.
NOTE: This address registration process is not used for E.164 addresses.
When the end system connects to the switch, the 13-byte prefix from the switch is
concatenated to a 7-byte user part defined on the end system. The prefix is composed of
the AFI, DCC/ICD and HO-DSP fields, while the user part contains the ESI and SEL.
The called and calling party numbers (or information elements) that are used during call
setup may be in either native E.164 or AESA address format.
• With E.164 native, the phone-number like address is encoded using IA5 characters,
where (as for ASCII) digit 0 = 30, digit 1 = 31, digit 2 = 32, and so on.
For example, the address 18005551000 would be encoded as:
3138303035353531303030
• As mentioned earlier, E.164 addresses can also be imbedded in an AESA
address. In this case the called/calling party information element indicates that
the address type is AESA and not E.164. The AESA address contains the E.164
address in its prefix.
The following shows how the previous example would be encoded in an imbedded
E.164 AESA address:
Field AFI E.164 HO-DSP ESI SEL
Value 45 000018005551000F 00000000 000000000000 00
Table 1-1: Example of an imbedded E.164 AESA address
Service Categories are a means of characterizing the way ATM traffic should flow through
the network in order to meet bandwidth requirements specific to the type of ATM
application used. Each service category is based on a combination of cell rate pacing,
Quality of Service (QoS) and traffic priority characteristics.
1-10 Memotec Inc.

NOTE: Service categories can be defined on the SDM-9230 only.
Product Overview
Four service categories have been defined in the ATM networking standard:
• Constant Bit Rate (CBR), described in the next section
• Unspecified Bit Rate (UBR), on See “Unspecified Bit Rate (UBR)” on page 12.
• Real-Time Variable Bit Rate (RT-VBR), on See “Real-time Variable Bit Rate (RT-
VBR)” on page 12.
• Non-Real-Time Variable Bit Rate (NRT-VBR), on See “Non-real-time Variable
Bit Rate (NRT-VBR)” on page 12..
NOTE: Service categories govern the transmission of traffic from the NetPerformer to
the ATM switch. They do not pertain to the NetPerformer transmitting via
PVCR, ATM or other transport method to another NetPerformer.
Constant Bit Rate (CBR)
Figure 1-2: The Service Category Environment
• A service for connections that require a static amount of bandwidth that is continuously
available during the entire duration of the connection.
• Should be selected for real-time applications that cannot work properly if there
are large variations in the transmission delay, e.g. voice, video and circuit emulation.
• The required amount of bandwidth is defined by the Peak cell rate parameter on
the logical connection (PVC or SVC).
• Once the connection is established, the network ensures the negotiated ATM
layer QoS to all cells. This means that the source unit is able to transmit cells at
the PCR at any time and for any duration, with QoS commitments fully maintained.
Memotec Inc. 1-11

ATM Option
• The source unit can transmit cells at a rate less than the negotiated PCR if
required, or stop transmitting cells for short periods of time.
• Associated ITU QoS class: 1.
Unspecified Bit Rate (UBR)
• A “best effort” service for use in applications where the traffic flow can be regulated
by a network with flexible resource requirements.
• Should be selected for applications that do not need to operate under controlled
delay and delay variation conditions, e.g. file transfer, email, banking transactions
and Telnet.
• Performance parameter objectives are determined internally by the application,
and do not need to be constant during the duration of the connection.
• PCR definition is optional, but the Peak cell rate parameter is available for information
purposes.
• Does not ensure a specific level of traffic service, Cell Loss Ratio (CLR) or Cell
Transfer Delay (CTD). If congestion control is required, it is handled at a higher
network layer.
• Associated ITU QoS class: U or 0 (Unspecified).
Real-time Variable Bit Rate (RT-VBR)
• A service for real-time applications that are highly sensitive to delays and delay
variation, but where traffic is bursty and must be transmitted at a varying rate,
e.g. voice and video.
• Should be selected for any real-time application that could benefit from variable
rate transmissions, and tolerate or recover from a small Cell Loss Ratio.
• Can support statistical multiplexing of traffic from multiple sources in real time.
• Bandwidth needs are defined using the Peak cell rate, Sustainable cell rate
(SCR) and Maximum burst size (MBS) in cells parameters.
• Associated ITU QoS class: 1.
Non-real-time Variable Bit Rate (NRT-VBR)
• A service for applications with bursty traffic that do not operate in real time and
cannot tolerate a high Cell Loss Ratio, e.g. Frame Relay interworking, airline reservations.
• Can support statistical multiplexing of traffic from multiple sources.
• Delays and delay variations are not critical to this category.
• Bandwidth needs are defined using the Peak cell rate, Sustainable cell rate
(SCR) and Maximum burst size (MBS) in cells parameters.
• Associated ITU QoS class: 2 or 3.
1-12 Memotec Inc.

1.3 ATM Support on the NetPerformer
Product Overview
The ATM option is sold under special license only, and requires installation of an ATM
product key on every NetPerformer unit in the ATM application.
The ATM option can be installed on the following NetPerformer products only:
• SDM-9360, SDM-9380 or SDM-9585: Must be running NetPerformer V9.0.0 or
higher and NetPerformer Signaling Engine version 4.0.8 or higher. These products
support both ATM AAL1 and AAL5. Refer to “ATM Protocols and AAL
Service Classes” on page 1-4.
• SDM-9230: Must be running NetPerformer V10.1 or higher. This product supports
ATM AAL5 only.
With the ATM option, a customer can access different network services via ATM from a
single unit using a T1/E1 card installed on that unit. Figure 1-3 illustrates the many ways
that the NetPerformer can provide ATM access.
PSTN
Voice
Internet
Gateway Controller
Figure 1-3: ATM Access from the NetPerformer
The circled numbers in Figure 1-3 refer to the following:
4
10
9
Memotec Inc. 1-13
8
ATM FR
IAD
1
ATM
3
6
OR
5
LAN
2
Frame Relay
Management
System
ATM
Switch
7
IAD

ATM Option
1. Access interface: From the NetPerformer to the ATM network there is a single T1 or
E1 connection provided from a T1 or E1 interface card installed in the NetPerformer
unit.
2. LAN traffic: This traffic, generally IP, can be transported over ATM using the
following methods:
• Proprietary PowerCell technique, using a PVC in ATMPVCR mode,
• Multiprotocol over ATM AAL5 (RFC-1483), using a PVC in RFC1483 mode,
• PPP over ATM AAL5 (RFC-2364), using a PVC in ATMPPP mode.
3. Frame Relay traffic: In most cases this traffic type comes from an external router.
• Frames from this router are converted to ATM cells using a PVC in FRF.8 mode
(Service Interworking).
• All ISO PDU modes are supported and translated correctly, including bridged
PDUs, routed PDUs and connection-oriented protocols.
4. Voice traffic: The voice interfaces can be analog (FXO, FXS, E&M) or digital (T1/
E1), and are linked to DSPs that support a full range of voice processing services.
• Requires a PVC in AAL1 mode.
• Voice over ATM is also supported with the PowerCell technique, using a PVC in
ATMPVCR mode.
• Digital interfaces support a wide variety of CAS and CCS signaling protocols.
• The voice interfaces (or subchannels) can be configured individually to operate
in:
Predefined mode: Voice subchannels are permanently associated with specific
subchannels in a PVC.
Switched mode: Voice subchannels are floating until an off-hook condition is
detected and a phone number is received. Then the NetPerformer analyzes the phone
number and routes the call to the proper destination.
5. Link to legacy ATM application: The NetPerformer can be linked to an ATM
switch using two PVCs:
• One PVC in RFC1483 or ATMPPP mode for data transport,
• One PVC in AAL1 mode for voice transport using circuit emulation.
Voice compression is not available in this mode.
6. Link to Frame Relay device: The NetPerformer can be linked to a remote Frame
Relay device using the following methods:
• PowerCell technique, using a PVC in ATMPVCR mode,
• One PVC in RFC1483 mode for data transport, an FRF.8 interworking device
placed between the ATM network and the Frame Relay network, and multiple
PVCs using AAL5/RTP mode for voice transport.
1-14 Memotec Inc.

Product Overview
7. Link to another Integrated Access Device (IAD): Using the same methods as in
number 6.
Most service providers are unable to reliably prioritize one PVC against another.
When the NetPerformer is linked to another IAD over ATM, congestion could occur
on traffic inbound to the NetPerformer.
8. Link to a gateway controller or network management system: Usually these
devices will be located in enterprise headquarters.
Typically this requires a specific PVC configured in RFC1483 mode for access to
the operation centers. However, the gateway controller and management system
could be collocated with the ATM switch (as in number 5) or anywhere in the IP
network.
9. Internet access: Can be provided with the following:
• PPP over ATM AAL5 (RFC-2364), using a PVC in ATMPPP mode,
• Multiprotocol over ATM AAL5 (RFC-1483), using a PVC in RFC1483 mode.
10. PSTN Access: Can be provided using a PVC in AAL1 mode (circuit emulation) as
described in number 5.
Figure 1-4: Using the NetPerformer as an Integrated Access Device
NOTE: A configuration example for this application is provided on “Using the Net-
Performer as an Integrated Access Device” on page 2-33.
Memotec Inc. 1-15

ATM Option
1.3.1 PowerCell in the ATM Network
As we have seen from Figure 1-3, the proprietary PowerCell protocol can be used over an
ATM network.
• PowerCell allows for the convergence of voice, video, LAN and SNA traffic onto
a single PVC.
• Frames created by PowerCell are transmitted using ATM AAL5, and comply to
the FRF.8 interworking standard.
• The remote device must be another NetPerformer, which can be connected to
either an ATM network or a Frame Relay network.
PowerCell over ATM allows devices connected on either Frame Relay or ATM networks
to interwork together via an FRF.8 compliant interworking device. The interworking
device translates the Q.922 core to AAL5, but does not perform RFC-1483 to RFC-1490
protocol translation.
Local IAD Remote IAD
PowerCell
Q.922
CORE
PHY
Q.922
CORE
In ATMPVCR mode, the Explicit Forward Congestion Indicator (EFCI) and Cell Loss
Priority (CLP) fields of the ATM cell are always set to 0.
1.3.2 AAL1 Circuit Emulation Services (CES)
Figure 1-5: PowerCell Translation
NOTE: AAL1 support is available on the SDM-9360, SDM-9380 and SDM-9585
running V9.1.0 or higher.
AAL1 Circuit Emulation Services (CES) are used to carry 64 Kbps bearer channels at a
constant bit rate (CBR) over ATM networks. CBR is required for carrying uncompressed
voice, which is very sensitive to traffic delays.
The services provided by AAL1 to the AAL user are:
• Transfer of service data units with a constant source bit rate,
• Delivery of these data units with the same bit rate,
• Transfer of structure information between source and destination.
1-16 Memotec Inc.
PHY
I/W Device
FRF.8
AAL5
PHY
PowerCell
AAL5
PHY

Product Overview
The NetPerformer provides CBR through support of the structured DS1/E1 Nx64 Kbps
service (where N represents the number of subchannels configured in the VC).
• This is a fractional DS1/E1 service that supports structured AAL1 framing with
CAS for either DS1 (D4 or ESF) or E1.
• It does not support structured or unstructured framing without CAS signaling.
• A maximum of 24 subchannels for all AAL1 VCs can be configured on the Net-
Performer when using an E1 connection, or 20 subchannels for a T1 connection.
AAL1 Voice Path
The AAL1 voice path is similar to a passthrough voice channel in the sense that voice is
not compressed (TDM) and no voice traffic is passed through the NetPerformer
baseboard.
During call setup, the Signaling Engine assigns a DSP to digit detection and tone
generation. When the remote subchannel (or partner channel) is detected, the Signaling
Engine allocates another DSP to process digit forwarding. Once call setup is complete,
only the DSP assigned to the AAL1 subchannel is used. This DSP also handles echo
cancellation.
Digit Detection for AAL1 Incoming Calls:
Incoming calls from AAL1 subchannels may be in predefined or switched mode.
• The mode of an AAL1 subchannel is predefined if there is a user voice channel in
predefined mode attached to this AAL1 subchannel. In this case, digits are
passed.
• The mode of an AAL1 subchannel is switched if there is no user voice channel in
predefined mode attached to this AAL1 subchannel. In this case, digits are
received and interpreted as for voice channels in a digital span.
AAL1 Cell Coding
The CES specification defines the concept of a block, which is one multiframe containing
a fixed number of DS0 channels.
• This block is fragmented into ATM cells.
• If the block does not fit within a single cell, then the sequence of blocks is fragmented
into multiple ATM cells with no space left unused in the cells. It is thus
possible to have a cell containing the end of one block and the beginning of the
next block.
The AAL1 ATM cell structure includes:
• Generic ATM header (5 bytes).
• AAL1 header (1 or 2 bytes):
- The first byte contains a one-bit flag (CSI) indicating whether the second byte
is present, a 3-bit CRC, a parity bit and a 3-bit sequence number.
Memotec Inc. 1-17

ATM Option
- The second byte, called the PTR byte, is optional. When present it indicates
the position of the block boundary within the cell, if one exists.
• AAL1 payload (46-47 bytes).
• Finally, a Bit Mask is inserted at the beginning of the superframe when Dynamic
Bandwidth is used (1 to 4 bytes). This mode is not supported on the NetPerformer
though.
- It indicates which subchannels are active or inactive, with one bit per
subchannel.
- Data information is not inserted for inactive subchannels, thus reducing bandwidth
requirements.
Bandwidth Utilization
AAL1 without bandwidth management:
On standard ATM AAL1 VC connections, several 64 Kbps subchannels are configured in
the VC. The virtual channel bandwidth is used all the time, even when no calls are active.
1.3.3 Frame Relay/ATM Service Interworking (FRF.8)
The FRF.8 agreement describes service interworking between the Frame Relay and ATM
technologies using PVCs. With service interworking an ATM backbone connects a Frame
Relay user to an ATM user, yet the two service layers remain independent of each other:
• The ATM service user performs no Frame Relay services.
• The Frame Relay service user performs no ATM services.
• All interworking operations between users are performed by the Interworking
Function (IWF) of the NetPerformer (the IAD).
Router
PVC 2
PVC 1
PVC 3
ATM PVC 2
Figure 1-6: Frame Relay to ATM Service Interworking using FRF.8
ATM-CPE
• When setting up FRF.8 on the NetPerformer, each Frame Relay PVC is mapped
to a single ATM PVC.
• Multiprotocol encapsulation is carried out using RFC-1490 Multiprotocol Encapsulation
over Frame Relay (see “Transparent versus Translation Mode” on
1-18 Memotec Inc.
IAD
IWF (FRF.8)
ATM PVC 1
ATM
ATM PVC 3
ATM-CPE
ATM-CPE

Product Overview
page 1-21). However, the PVC can be configured so that the payload is passed
transparently from one end to the other.
PVC 1
PVC 2
PVC 3
FR PORT
IWF
Service Interworking Functions
The Frame Relay/ATM service interworking specification includes five network
interworking functions, all of which are supported by the NetPerformer:
• Frame formatting and delimiting
• Discard eligibility (DE) and cell loss priority (CLP) mapping
• Congestion indication mapping
• Command/response field mapping
• DLCI field mapping.
Frame Formatting and Delimiting
ATM PVC 1
ATM PVC 2
ATM PVC 3
Figure 1-7: Frame Relay to ATM PVC Mapping
This involves a different process in different directions:
• Frame Formatting in the FR-to-ATM direction: The FR frame is mapped onto
an AAL5 Protocol Data Unit (PDU). Frame Relay frame flags, inserted zero bits
and CRC-16 are stripped, the FR header is removed and some of its fields
mapped onto the ATM cell header fields.
• Frame Delimiting in the ATM-to-FR direction: For segmentation and reassembly
purposes the frame boundaries are identified using the AAL5 message
delineation. Zero bits, CRC-16 and flags are inserted, and the protocol fields and
functions of the ATM AAL5 PDU are translated into those of the Frame Relay
frame.
Discard Eligibility and Cell Loss Priority Mapping
ATM
Network
Two modes of loss priority mapping are available in both directions:
• FR-to-ATM direction:
- The value of the Frame Relay DE field is mapped to the ATM CLP field of
every ATM cell generated by the segmentation process. On the NetPerformer
this is the default mode.
Memotec Inc. 1-19

ATM Option
- The CLP field of every ATM cell generated by the segmentation process is set
to a constant value (0 or 1). This value is configured separately for each PVC.
• ATM-to-FR direction:
- If one or more cells belonging to an ATM frame has its CLP field set to 1, the
DE field is also set to 1 in the corresponding Frame Relay frame. On the Net-
Performer this is the default mode.
- No mapping is performed from the ATM layer to FR layer. The DE field of
the Frame Relay frame is set to a constant value (0 or 1), which is configured
separately for each PVC.
Congestion Indication Mapping
The NetPerformer provides both forward and backward congestion indication.
• Congestion is detected when the queue size goes above the threshold defined by
the Congestion Queue Size parameter for the PVC.
• A second threshold, the Maximum Queue Size parameter, determines when
frame discarding is required.
• On the NetPerformer, forward congestion indication is supported at the frame
level with Forward Explicit Congestion Notification (FECN), and at the cell level
with Explicit Forward Congestion Indication (EFCI).
• Congestion Indication Forward in the FR-to-ATM direction: Two modes are
available:
- The value of the Frame Relay FECN field is mapped to the ATM EFCI field
of every cell generated by the segmentation process. On the NetPerformer this
is the default mode.
- No mapping is performed from the FR layer to the ATM layer.The EFCI field
of every ATM cell is set to a constant value (0 or 1). This value is configured
separately for each PVC.
If there is congestion at the ATM layer in the forward direction, the IWF can set
the EFCI field to 1 no matter which mode is configured.
• Congestion Indication Forward in the ATM-to-FR direction: Two modes are
available:
- The value of the ATM EFCI field is mapped to the FECN field of the Frame
Relay frame. On the NetPerformer this is the default mode.
- The FECN field of every ATM cell is set to a constant value (0 or 1). This
value is configured separately for each PVC.
• Congestion Indication Backward: The Frame Relay Backward Explicit Congestion
Notification (BECN) field has no equivalent in ATM.
- In the FR-to-ATM direction, the BECN field is ignored.
- In the ATM-to-FR direction, the BECN field is set to 1 if a congestion situation
is detected by the NetPerformer in the FR-to-ATM direction.
1-20 Memotec Inc.

Product Overview
- Congestion is determined using the Congestion Queue size parameter.
Command/Response Field Mapping
This involves a different process in different directions:
• FR-to-ATM direction: The Frame Relay C/R field is mapped to the Common Part
Convergence Sublayer – User to User (CPCS-UU) Least Significant Bit (LSB) of
the CPCS PDU.
• ATM-to-FR direction: The CPCS-UU LSB is mapped to the C/R field.
• In both directions the NetPerformer handles the mapping internally, with no PVC
configuration required.
DLCI Field Mapping
• With FRF.8 there is a one-to-one mapping between the Frame Relay DLCI and
the ATM VPI/VCI.
Transparent versus Translation Mode
FRF.8 specifies two operating modes for user protocol encapsulation at the upper layer:
• Transparent Mode: The IWF leaves the user data unchanged. No mapping,
fragmentation or reassembly is performed.
• Translation Mode: The IWF maps the Frame Relay RFC-1490 frames to ATM
RFC-1483 CPCS Protocol Data Units (PDU) and vice versa, as shown in Figure
1-8.
- When the IWF receives fragmented packets on a Frame Relay PVC, it reassembles
them before forwarding them to the ATM PVC.
- In the reverse direction, fragmentation is performed on the received CPCS
PDU before forwarding the fragmented packets to the Frame Relay PVC.
• Each FRF.8 PVC is configured separately for transparent versus translation
mode:
- For Transparent Mode, set the Header Translation parameter to NO.
Memotec Inc. 1-21

ATM Option
- For Translation Mode, set the Header Translation parameter to YES. This is
the default value on the NetPerformer for an FRF.8 PVC.
Upper
Layers
RFC-1490
Q.922
CORE
PHY
FRF.8 PVC Status Management
Separate PVC status management procedures are used for the Frame Relay and ATM
services:
• Frame Relay PVC Management: FRF.8 specifies that Q.933 be used for the
Frame Relay PVC management procedures. Since the NetPerformer already supports
Q.933 on its Frame Relay ports, management of Frame Relay PVCs for the
Frame Relay User-to-Network Interface (UNI) side remains unchanged.
• ATM PVC Management: These procedures are based on received Operation,
Administration and Maintenance (OAM) cells indicating inactive status on the
PVC.
- This status information is obtained by the IWF, mapped to the corresponding
Frame Relay status indicators and then delivered to the Frame Relay network.
- DLCI 0 is used to exchange PVC status management between one or more
IWFs and/or ATM-CPEs emulating Frame Relay, following Q.933 Annex A.
In addition, Link Integrity Verification (LIV) performs the function of ensuring that the
link between the IWF and the attached Frame Relay network is operational.
1.3.4 LLC Encapsulation (RFC-1483)
RFC-1490
Q.922
CORE
Figure 1-8: FRF.8 Translation
On the NetPerformer, multiprotocol encapsulation over AAL5 is based on the LLC
encapsulation method described in RFC-1483. This method permits the multiplexing of
multiple protocols over a single ATM Virtual Circuit.
• Routed and bridged PDUs are encapsulated within the Payload field of the AAL5
CPCS-PDU.
- The Payload Field contains the information required to identify the protocol
of the routed or bridged PDU. This allows the receiver to properly process the
incoming AAL5 CPCS-PDU.
1-22 Memotec Inc.
PHY
FRF.8
RFC-1483
AAL5
PHY
Upper
Layers
RFC-1483
AAL5
PHY

1.3.5 PPP Over AAL5
Product Overview
- In LLC Encapsulation this information is encoded in an LLC header placed in
front of the carried PDU.
• RFC-1483 deals only with protocols that operate over LLC Type 1 (unacknowledged
connectionless mode) service.
- In LLC Type 1 operation, the IEEE 802.2 LLC header consists of three oneoctet
fields: DSAP, SSAP and CTRL.
LLC Encapsulation is required when several protocols are carried over the same VC. The
LLC header is different for different protocols:
• For routed non-ISO protocols, the CTRL field specifies an Unnumbered Information
Command PDU, and an IEEE 802.1 Sub-Network Attachment Point (SNAP)
header immediately follows the LLC header. The SNAP header identifies the
routed protocol.
IP is considered a routed non-ISO protocol, and is supported by the NetPerformer.
Routed ISO protocols are not supported.
• Bridged PDUs are encapsulated and the type of bridged protocol is identified in
the SNAP header. The Protocol Identifier (PID) in this header also indicates
whether the original Frame Check Sequence (FCS) is preserved within the
bridged PDU.
PPP over AAL5 is implemented on the NetPerformer based on RFC-2364, which uses the
same frame structure and mechanisms as RFC-1483. With RFC-2364, PDUs are
encapsulated within the Payload field of AAL5 CPCS-PDU.
When transporting a PPP payload over AAL5, two techniques may be used:
• LLC Encapsulation: The protocol type of the payload is explicitly identified by
an LLC header consisting of three one-octet fields: DSAP, SSAP and CTRL.
Refer to the section “LLC Encapsulation (RFC-1483)” on page 1-22.
- The LLC header value indicates that a routed ISO PDU follows. The routed
ISO protocol is PPP, which is identified by a one-octet NLPID field following
the LLC header.
- The PPP payload consists of three one-octet fields: PID, Information and Padding,
which follow the NLPID field in the CPCS-PDU.
• VC Multiplexing: The payload protocol is implicitly determined for each virtual
circuit.
- A VC-multiplexed PPP frame constitutes the CPCS-PDU payload.
Authentication
On the NetPerformer, PPP over ATM includes support of two authentication methods,
Password Authentication Protocol (PAP) and Challenge Handshake Authentication
Protocol (CHAP), both of which protect PPP connections from unauthorized use. Select
the desired authentication method using the Password Type parameter for the PVC.
Memotec Inc. 1-23

ATM Option
1.3.6 ATM Multiplex Connections
• PAP: Provides “one-shot” password protection, as described in RFC-1334.
- Configurable PAP parameters are: User name, Password, Authentication
Retries and Fail Delay (in minutes).
- The Fail Delay takes effect if the number of Authentication Retries has been
exceeded. It forces the PVC connection into an idle state, which reduces the
risk of a password attack.
• CHAP: Requests authentication from the remote side at random intervals, as
described in RFC-1994.
- This method reduces the chance of unauthorized access, particularly for longterm
connections.
- CHAP requires the same parameters as PAP, plus the Maximum Challenge
Interval (in minutes) and Authentication Timeout (in seconds).
On the NetPerformer, multiplexing an ATM application over PowerCell can be
accomplished through the ATM-MULTIPLEX PVC mode. This mode is ideal for
transporting traffic from any type of ATM Adaptation Layer. ATM-MULTIPLEX is also the
only PVC mode that can support AAL2 and AAL3/4 traffic.
Figure 1-9: Using the NetPerformer as an ATM Multiplexer
NOTE: A configuration example for this application is provided on “Using the Net-
Performer as an ATM Multiplexer” on page 2-36.
For the ATM-MULTIPLEX PVC mode the notion of ATM Adaptation Layer is an important
one. It can be defined as either AAL0 (a NetPerformer product-specific term) or AAL5.
1-24 Memotec Inc.

AAL0 Adaptation Layer
Product Overview
• Provides transparent support of all cells in any type of ATM Adaptation Layer:
AAL1 to AAL5, inclusive
• Should be selected for transporting AAL types other than AAL5
• No idle cells are transmitted, only cells that are defined with a VPI/VCI combination
• Traffic is processed on a per cell basis.
AAL5 Adaptation Layer
• For use with variable bit-rate traffic in a connection-oriented mode (refer to
“AAL5: for use with variable bit-rate traffic in a connection-oriented mode. Also
known as Simple and Efficient Adaptation Layer (SEAL).” on page 1-4 for a
complete description of this AAL type)
• Transfers AAL5 traffic from one site to another
• Cells are accumulated into AAL5 frames before being transferred to the destination
unit.
Memotec Inc. 1-25

ATM Option
1.4 NetPerformer Architecture and ATM
The NetPerformer hardware has been modified to support ATM by changing the Signaling
Engine processor to an equivalent processor with ATM capabilities. Older units capable of
supporting ATM are identified by the A suffix in the model number: the SDM-9360A,
SDM-9380A and SDM-9585A. Figure 1-10 illustrates some details of this architecture on
the SDM-9360A.
LAN
Packet Engine
(Data Handler)
Main
Processor
DATA
WAN WAN
Plug-in
Interface
Cards
DSP SIMMs
Signaling Engine
(Voice Handler)
Signaling Engine
Processor *
TimeSlot XCHG
Figure 1-10: NetPerformer Architecture for ATM Suppor
T1
E1
FXS
FXO or
E&M
T1
E1
FXS
FXO or
E&M
NOTE: On the SDM-9220/9230 platform the Signaling Engine runs on the same processor
as the main application (single processor architecture), while on the
SDM-9360, SDM-9380 and SDM-9585 the Signaling Engine runs on a different
processor than the main application.
1-26 Memotec Inc.
T1
To
ATM
Network
ATM
Stack
ATM/SAR
T1
E1
FXS
FXO or
E&M
DSP
VOICE
VOICE
To
PBX

Product Overview
On the SDM-9360A, 2 DSP SIMMs are available for echo cancellation, tone detection and
regeneration, voice compression, modem relay and fax relay. The architecture of the
SDM-9380 and SDM-9585 is similar, but uses a faster processor for data handling and
supports up to 4 DSP SIMMS.
NOTE: The voice channel path in Figure 1-10 is for voice over ATM via AAL1. The
voice path is slightly different for voice over PowerCell or local switching of
voice calls.
1.4.1 NetPerformer Implementation of ATM SVCs
NetPerformer support of ATM SVCs has evolved considerably between V10.1 and V10.2:
• In NetPerformer V10.1, ATM SVCs operated as dialup PVCs:
- This implementation offered PVC functionalities that were applied to a
switched VC
- PVCs and SVC definitions were numbered from the same pool (maximum
300)
- Monitoring functions were based on PVC statistics commands.
• In NetPerformer V10.2, ATM SVCs operate independently of PVCs:
- Up to 300 SVCs can be defined, and they can have the same numbers as configured
PVCs
- New SVC statistics commands have been developed that are entirely separate
from the PVC commands. Refer to the chapter “Monitoring and Statistics” on
page 3-1.
Permanent SVC Connections
Instead of explicitly specified VPI and VCI values, NetPerformer SVCs use a destination
address (or called party address). No inactivity timeout mechanism is included. This
means that:
• SVCs are established at startup and remain permanently connected. They are not
disconnected when there is no traffic.
• If the SVC type is DEDICATED and the connection is lost for some reason (the
link is disconnected or the remote site is restarted, for example) the NetPerformer
tries to re-establish the connection indefinitely.
• If the SVC type is ANSWER and the connection is lost, the NetPerformer will
wait for an incoming call.
SVC Addressing
Each SVC can have a different local address.
Memotec Inc. 1-27

ATM Option
• The SVC local address can be used to differentiate between incompatible services.
For example, if some SVCs use ATMPPP mode and others use ATMPVCR
mode, you must configure the NetPerformer with distinct local addresses for
these two types of SVCs.
• On the other hand, the same local address can also be used for multiple SVCs.
In this case, whenever an incoming call is received, it will be connected to the
first available SVC that matches the called and calling addresses.
NOTE: This method can only be used when all SVCs on the NetPerformer unit are
configured in ATMPVCR mode.
When validating an incoming call, the NetPerformer:
• Checks that both the called and calling party addresses match the Local and Destination
addresses, respectively, on one of its SVCs
• If it cannot find a match, the call is rejected
• This implies that all SVCs in ANSWER mode must have a configured destination
address, even if they are not used to establish the connection, per se.
UNI Signaling Support
The NetPerformer supports UNI 3.0, 3.1 and 4.0. Refer to “User to Network Interface
(UNI)” on page 1-7 for further information.
• To select the UNI version, set the UNI Version parameter on the digital channel.
• To define the signaling channel used, configure the ATM Signaling Channel VPI
and ATM Signaling Channel VCI parameters on the digital channel.
For details on these parameters, refer to the appendix “SE/SLOT/CHANNEL
Configuration Parameters” on page 4-1.
ILMI Address Registration
The user side of the ILMI address registration process is included with NetPerformer
support of ATM SVCs. Refer to “Integrated Local Management Interface (ILMI)” on
page 1-8 for further information.
• To configure the digital channel used for ILMI, configure the ILMI Channel VPI
and ILMI Channel VCI parameters on the digital channel. Refer to the appendix
“SE/SLOT/CHANNEL Configuration Parameters” on page 4-1.
NOTE: Address registration applies only to the DCC and ICD AESA formats.
1-28 Memotec Inc.

SVC Modes Supported
Product Overview
SVCs support the same AAL5 modes for data as those supported by the PVCs:
ATMPVCR, FRF.8, RFC1483 and ATMPPP. ATM-MULTIPLEX is not supported on SVCs.
See “Configuring the ATM SVCs” on page 2-26 for configuration details.
NOTE: In NetPerformer V10.1, ATM AAL1 is not supported with SVCs. You
must use an AAL1 PVC for this purpose, available on the SDM-9360,
SDM-9380 and SDM-9585 only.
Memotec Inc. 1-29

ATM Option
1-30 Memotec Inc.

Configuration
2
Memotec Inc. 2-1

ATM Option
2.1 About the ATM Option
Important: The ATM Option includes a Software Licensing Agreement, which can
be found in the product package.
• You must agree to the terms and conditions of this agreement before loading the
software.
• Each NetPerformer unit that serves as an ATM access node in the application
requires a separate software license.
• The ATM Option can be loaded on a NetPerformer SDM-9230, SDM-9360,
SDM-9380 or SDM-9585 only.
• All NetPerformer units that will serve as ATM access nodes in the network must
be installed with a digital interface card for the ATM channel.
• Only one channel can be set to ATM on only one digital interface per unit. All
other connections are logical connections using ATM PVCs and SVCs.
• When the ATM licensed software option is installed on an SDM-9230, the second
LAN port (ETH2) is not available and does not appear in the choice of ports
for any console command. Only the first LAN port (ETH1) is operative.
2.2 Before You Configure
The ATM software must be activated on the NetPerformer unit (an SDM-9230,
SDM-9360, SDM-9380 or SDM-9585) before you can configure and use any ATM
features. This requires entering the ATM Software License to the License Profile.
NOTE: A specific License Profile is valid for a single NetPerformer unit only.
To prepare for ATM configuration you must first:
• Install the NetPerformer SDM-9230, SDM-9360, SDM-9380 or SDM-9585 unit
according to the instructions given in the Hardware Installation Guide for the
particular product, which is available on the NetPerformer Documentation
CD (Part No. 161-0692-001).
• Install and activate the ATM Option software license, following the procedure
provided in the Software Licensing chapter of the Software Installation and
Licensing fascicle of this document series.
• At any time, you can reset the unit configuration to its factory defaults: enter FS
at the command prompt. The ATM Option is reset along with all other areas of
the configuration, and all previously defined values are lost.
2-2 Memotec Inc.

Configuration
When you execute the FS command, the NetPerformer unit clears its License
Profile and turns off the digital channel that was configured for ATM operation
(channel Protocol set to ATM). You must:
- Re-enter the ATM Option software license, and
- Change the Protocol parameter on the digital channel involved in the application
to ATM (see “Configuring the ATM Channel” on page 2-15).
2.2.1 Is the ATM Option Already Installed?
DP example:
with ATM
option enabled
DV example:
with ATM
option enabled
DA example:
with ATM
option enabled
To determine whether a NetPerformer unit is already installed with the ATM licensed
software option, execute any of the following commands:
• Display Parameters (DP)
• Display Version (DV)
• Display Alarms (DA).
These commands include information on any optional software that has already been
installed on the unit. The message ATM license (AAAA-BBBB-CCCCCCCC-DDDD)
enabled on this unit indicates the software license number. The following line indicates
the maximum number of accelerated connections available on the unit.
SDM-9230>DP
DISPLAY PARAMETERS
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,
def:REDUNDANCY) ? ALL
Wait for after each screen (NO/YES,def:YES) ? NO
NetPerformer SDM-9230 vX.X.X Memotec Inc. (c) 2004
Signaling Engine vX.X.X Memotec Inc. (c) 2004
Console connected on port CSL
ATM license (AAAA-BBBB-CCCCCCCC-DDDD) enabled on this unit
...
SDM-9230>DV
DISPLAY VERSION
SDM-9230 vX.X.X Memotec Inc. (c) 2004
Signaling Engine vX.X.X Memotec Inc. (c) 2004
DSP code version: X.X.X
Console connected on port CSL
ATM license (AAAA-BBBB-CCCCCCCC-DDDD) enabled on this unit
SDM-9230>DA
DISPLAY ALARMS
SDM-9230 vX.X.X Memotec Inc. (c) 2004
Signaling Engine vX.X.X Memotec Inc. (c) 2004
DSP code version: X.X.X
Console connected on port CSL
ATM license (AAAA-BBBB-CCCCCCCC-DDDD) enabled on this unit
...
Memotec Inc. 2-3

ATM Option
2.3 Configuration Overview
To adapt the NetPerformer for access to network services via ATM, follow these
configuration steps:
• Configure the global parameters that affect the allocation of memory for data
channels and ATM AAL5 VCs, using the SETUP/GLOBAL command. Refer to
“Configuring the Global Parameters” on page 2-6.
These GLOBAL parameters are not required on the SDM-9230, which does not
have the memory constraints that the SDM-9360, SDM-9380 and SDM-9585
have in supporting ATM.
• Set up the ATM interface on the digital LINK with the SETUP/SLOT/LINK command,
selecting the slot that contains the ATM access interface: a T1 or E1 interface
card. Refer to “Configuring the Digital Link” on page 2-13.
• Set up the ATM channel with the SETUP/SLOT/CHANNEL command. Refer to
“Configuring the ATM Channel” on page 2-15.
• Set up the LAN port with the SETUP/PORT command. The LAN port is configured
in the same way as for non-ATM applications. For further information, refer
to the LAN Connection and IP Networks fascicle of this document series.
When the ATM licensed software option is activated on an SDM-9230, the
second LAN port (ETH2) is not available and does not appear in the choice
of ports for any console command. Only the first LAN port (ETH1) is operative.
• Set up the Frame Relay port that connects to the user equipment with the SETUP/
PORT or SETUP/SLOT command. The FR-NET port is configured in the same
way as for non-ATM applications. Refer to the NetPerformer User Guide and
NetPerformer System Reference Manual for further information.
• Set up all required ATM PVCs with the SETUP/PVC command. For details, refer
to “Configuring the ATM PVCs” on page 2-17.
• Set up all required ATM SVCs with the SETUP/SVC command. Refer to “Configuring
the ATM SVCs” on page 2-26 for details.
• Set up all required Voice Mapping Table entries using the SETUP/MAP command.
Refer to the NetPerformer User Guide and NetPerformer System
Reference Manual for information on configuring the MAP entries.
2-4 Memotec Inc.

Unit ID>
(main prompt)
Figure 2-1: SETUP Command Paths in the CLI Tree for ATM Configuration
Configuration
Global (GL) MAP (MA) Port (PO)
PVC (PV) Slot (SL)
SVC (SV)
ETH #
Setup (SE)
FR-NET
Memotec Inc. 2-5
Link
NONE
Channel
ATM

ATM Option
2.4 Configuring the Global Parameters
The GLOBAL submenu of the SETUP command includes all global parameters that affect
the ATM Option. These parameters determine how many AAL1 VCs can be defined on
the SDM-9360, SDM-9380 or SDM-9585, and shared RAM allocation for data channels
and AAL5 VCs.
NOTE: The GLOBAL parameters are not required on the SDM-9230, which does not
have the memory constraints that the SDM-9360, SDM-9380 and SDM-9585
have in supporting ATM.
Global (GL)
To configure the global parameters:
Unit ID>
(main prompt)
Setup (SE)
Figure 2-2: TUP/GLOBAL Path in the CLI Tree
1. At the NetPerformer command line prompt, enter the menu sequence: SE � GLOBAL
2. Change a parameter value by entering the new value after the parameter prompt.
Important parameters for the ATM Option include:
• Number of DSPs reserved for AAL1
• Number of data channels reserved
• Number of ATM AAL5 VCs reserved
These parameters appear with the SETUP/GLOBAL console listing only if the
NetPerformer unit detects the ATM SAR and has been installed with the ATM
product license.
See “Tips for Configuring Shared RAM Allocation” on page 2-9 for configuration tips
concerning the shared RAM allocation, which affects other areas of NetPerformer
configuration.
2-6 Memotec Inc.

SE/GLOBAL
example: with
ATM license
installed
Configuration
NPATM2>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ?
GLOBAL
GLOBAL> Unit name (def:NPATM2) ?
GLOBAL> Unit routing version (1-2,def:1) ?
...
GLOBAL> Delay generated by a comma (ms) (250-4000,inc:250,def:250)
?
GLOBAL> ISDN G4 Fax PCM switching enable (def:NO) ?
GLOBAL> Number of DSPs reserved for AAL1 (0-6,def:0) ?
GLOBAL> Auto save configuration delay (sec) (0-255,def:10) ?
GLOBAL> Enable VTR (Voice Traffic Routing) (def:NO) ?
GLOBAL> Enable Domain Dialing (def:YES) ?
GLOBAL> Enable hunt forwarding (def:YES) ?
GLOBAL> Enable user access logging (def:NO) ?
GLOBAL> Exclusive access to console (def:DISABLE) ?
WARNING: Changing the next two parameters will require
a unit reset before the new values take effect.
GLOBAL> Number of data channels reserved (0-32,def:32) ?
GLOBAL> ATM AAL5 VC mode includes ATMPVCR, ATMPPP, RFC1483 and
FRF.8
Number of ATM AAL5 VCs reserved (0-31,def:15) ? 16
----- PROPOSED SHARED RAM ALLOCATION -----
Number of reserved data channels: 32
Number of reserved ATM AAL5 VCs: 16
Number of configured data channels: 0
Number of configured ATM AAL5 VCs: 1
Total memory available: 1076784 bytes,1051K
Allocated memory for data channels (32*23252): 744064 bytes, 726K
Allocated memory for ATM AAL5 VCs (16*20162): 322592 bytes, 315K
Total allocated memory: 1066656 bytes,1041K
Unallocated memory: 10128 bytes, 9K
WARNING: To apply the new configuration the unit must be reset
To do this, execute the Reset Unit (RU) command.
Number of DSPs reserved for AAL1
Console SNMP Text-based Config
Number of DSPs
reserved for AAL1
npsysAtmDspReserved [npsys] AtmDspReserved
Not required on the SDM-9230
Determines the number of DSP SIMMs that will be used for ATM AAL1 operations
(available on the SDM-9360, SDM-9380 and SDM-9585 only).
Memotec Inc. 2-7

ATM Option
• An AAL1 subchannel is configured with the Number of subchannels parameter
of a PVC set to AAL1 mode. Refer to “Configuring the ATM PVCs” on page 2-
17 for details.
• Set the Number of DSPs reserved for AAL1 to a number that is high enough to
accommodate all AAL1 subchannels you intend to configure on this unit.
Values: 0 - 6
Default: 0
NOTE: Later configuration of AAL1 subchannels may be restricted by the Number of
DSPs reserved for AAL1 parameter.
• If you try to configure more AAL1 subchannels than the maximum number permitted
for the digital card (a total of 20 subchannels on a T1 interface card, or 24
subchannels on an E1 interface card), the NetPerformer issues a warning on the
console screen and aborts the SETUP command, as shown in the following
example:
9380-ATM>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/SCHEDULE/SLOT/USER/VLAN,def:GLOBAL) ?
PVC
PVC number (1-300,def:1) ? 2
PVC 2> Mode (def:PVCR) ? AAL1
PVC 2> VPI address (0-255,def:0) ? 1
PVC 2> VCI address (0-65534,def:0) ? 102
PVC 2> PVC name (def:) ? BOSTON-AAL1
PVC 2> Number of subchannels (0-24,def:1) ? 2
WARNING ! The number of AAL1 subchannels exceeds the permitted
limit
(maximum is 20).
9360-ATM>
Number of data channels reserved
Console SNMP Text-based Config
Number of data channels
reserved
npsysAtmDataChannel-
Reserved
[npsys] AtmData-ChannelReserved
Not required on the SDM-9230
Determines the number of non-ATM digital data channels that will be reserved for data
transmission.
• Here, the term data channels refers to digital channels defined with the PVCR,
FR-NET, FR-USER, HDLC or PASSTHRU protocols.
2-8 Memotec Inc.

Configuration
Included in this calculation are serial ports set to one of these protocols on the
Dual Serial interface card. Built-in serial ports are not included.
• Set the Number of data channels reserved to a number that is high enough to
accommodate all data channels you intend to configure in one of these protocols.
Refer to “Effects of Shared RAM Allocation” on page 2-11.
Values: SDM-9360: 0 - 32
Default: 32
Values: SDM-9380 or SDM-9585: 0 - 64
Default: 64
Number of ATM AAL5 VCs reserved
Console SNMP Text-based Config
Number of ATM AAL5
VCs reserved
npsysAtmAAL5Vc-
Reserved
Not required on the SDM-9230
Determines the number of VCs that will be reserved for ATM AAL5 operations.
• Here, ATM AAL5 denotes the ATMPVCR, ATMPPP, RFC1483 and FRF.8
modes, which are set during PVC and SVC configuration (refer to “Configuring
the ATM PVCs” on page 2-17 and “Configuring the ATM SVCs” on page 2-26).
• Set the Number of ATM AAL5 VCs reserved to a number that is high enough to
accommodate all PVCs and SVCs you intend to configure in one of these modes.
Refer to “Effects of Shared RAM Allocation” on page 2-11.
Values: 0 - 31
Default: SDM-9360: 5
SDM-9380 or SDM-9585: 15
2.4.1 Tips for Configuring Shared RAM Allocation
[npsys]
AtmAAL5VcReserved
Two of the Global parameters: Number of Data Channels Reserved and Number of ATM
AAL5 VCs Reserved, affect the allocation of shared RAM on the NetPerformer unit.
• Each time you change either or both of these parameters, the proposed shared
RAM allocation is displayed on the console screen.
• When you change these parameters, you must reset the unit with the Reset Unit
(RU) command to activate the change.
• The combined number of data channels and ATM AAL5 VCs cannot exceed the
total memory available.
Examine the Total allocated memory and Unallocated memory statistics, which
are displayed under the PROPOSED SHARED RAM ALLOCATION heading on
the console screen.
Memotec Inc. 2-9

ATM Option
SE/GLOBAL
example: with
total memory
exceeded
• If you exceed the total memory, a warning is displayed and the Number of Data
Channels Reserved and Number of ATM AAL5 VCs Reserved parameters are provided
once again for reconfiguration.
NPATM2>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ?
GLOBAL
GLOBAL> Unit name (def:NPATM2) ?
GLOBAL> Unit routing version (1-2,def:1) ?
...
GLOBAL> Delay generated by a comma (ms) (250-4000,inc:250,def:250)
?
GLOBAL> ISDN G4 Fax PCM switching enable (def:NO) ?
GLOBAL> Number of DSPs reserved for AAL1 (0-6,def:0) ?
GLOBAL> Auto save configuration delay (sec) (0-255,def:10) ?
GLOBAL> Enable VTR (Voice Traffic Routing) (def:NO) ?
GLOBAL> Enable Domain Dialing (def:YES) ?
GLOBAL> Enable hunt forwarding (def:YES) ?
GLOBAL> Enable user access logging (def:NO) ?
GLOBAL> Exclusive access to console (def:DISABLE) ?
WARNING: Changing the next two parameters will require
a unit reset before the new values take effect.
GLOBAL> Number of data channels reserved (0-32,def:32) ?
GLOBAL> ATM AAL5 VC mode includes ATMPVCR, ATMPPP, RFC1483 and
FRF.8
Number of ATM AAL5 VCs reserved (0-31,def:15) ? 17
----- PROPOSED SHARED RAM ALLOCATION -----
Number of reserved data channels: 32
Number of reserved ATM AAL5 VCs: 17
Number of configured data channels: 0
Number of configured ATM AAL5 VCs: 1
Total memory available: 1076784 bytes,1051K
Allocated memory for data channels (32*23252): 744064 bytes, 726K
Allocated memory for ATM AAL5 VCs (17*20162): 342754 bytes, 334K
Total allocated memory: 1086818 bytes,1061K
Unallocated memory: -10034 bytes, -9K
WARNING !!! The amount of memory needed for the number of data
channels
and the number of ATM AAL5 VCs exceeds the total memory
available.
GLOBAL> Number of data channels reserved (0-32,def:32) ?
GLOBAL> ATM AAL5 VC mode includes ATMPVCR, ATMPPP, RFC1483 and
FRF.8
Number of ATM AAL5 VCs reserved (0-31,def:15) ? 15
2-10 Memotec Inc.

SE/SLOT
example: with
data channels
exceeded
----- CURRENT SHARED RAM ALLOCATION -----
Number of reserved data channels: 32
Number of reserved ATM AAL5 VCs: 15
Number of configured data channels: 0
Number of configured ATM AAL5 VCs: 1
Configuration
Total memory available: 1076784 bytes,1051K
Allocated memory for data channels (32*23252): 744064 bytes, 726K
Allocated memory for ATM AAL5 VCs (15*20162): 302430 bytes, 295K
Total allocated memory: 1046494 bytes,1021K
Unallocated memory: 30290 bytes, 29K
Effects of Shared RAM Allocation
Once you have defined the shared RAM allocation, later configuration of data channels or
AAL5 VCs may be restricted:
• If you try to configure more data channels than the number you have reserved
with the Number of data channels reserved parameter, the NetPerformer issues a
warning on the console screen and aborts the SETUP command.
A data channel is configured with the PVCR, FR-NET, FR-USER, PPP or HDLC
protocol using the SE/SLOT/CHANNEL submenu. Refer to the NetPerformer
User Guide or NetPerformer System Reference Manual for details.
9380-ATM>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/SCHEDULE/SLOT/USER/VLAN,def:GLOBAL) ?
SLOT
SLOT> Slot number (1/2/3/4,def:1) ?
Item (LINK/CHANNEL,def:CHANNEL) ?
SLOT> Channel Number (101-124/ALL,def:101) ?
PORT 101> Protocol (def:OFF) ? PVCR
WARNING !!! The number of data channels exceeds the permitted
limit.
See the Number of Data Channels Reserved parameter in
the global parameters (SETUP GLOBAL).
9380-ATM>
• If you try to configure more AAL5 VCs than the number you have reserved with
the Number of ATM AAL5 VCs reserved parameter, the NetPerformer issues a
warning on the console screen and aborts the SETUP command.
An AAL5 VC is configured when a PVC or SVC is set to ATMPVCR, ATMPPP,
RFC1483 or FRF.8 PVC modes. Refer to “Configuring the ATM PVCs” on
page 2-17 and “Configuring the ATM SVCs” on page 2-26 for details.
Memotec Inc. 2-11

ATM Option
SE/PVC
example: with
ATM AAL5 VCs
exceeded
9380-ATM>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/SCHEDULE/SLOT/USER/VLAN,def:GLOBAL) ?
PVC
PVC number (1-300,def:6) ?
PVC 6> Mode (def:OFF) ? ATMPVCR
WARNING !!! The number of ATM AAL5 VC exceeds the permitted limit.
See the Number of ATM AAL5 VC Reserved parameter in
the global parameters (SETUP GLOBAL).
9380-ATM>
2-12 Memotec Inc.

2.5 Configuring the Digital Link
Configuration
Set up the digital link for an ATM interface with the LINK option of the the SETUP/SLOT
command.
To configure the digital link:
1. At the NetPerformer command line prompt, enter the menu sequence: SE � SLOT
2. Select the Slot number of a slot that contains a T1 or E1 interface card
3. Enter LINK
Unit ID>
(main prompt)
Caution: If you change the configuration of a T1 or E1 interface card
while voice calls are active, the calls will be disrupted.
4. Set the Status parameter to ENABLE
5. Set Clock Recovery to ENABLE
6. Set Digital port clock source to the appropriate value for your application:
• INTERNAL to use the internal reference clock
• 1 to 4 to use the clock received from the network via the digital interface card
installed in that slot number
7. Set the Signaling Mode to NONE
Setup (SE)
Figure 2-3: SETUP/SLOT/LINK Path in the CLI Tree
8. Change the other parameters from their default values, if desired.
Slot (SL)
Memotec Inc. 2-13
Link
NONE

ATM Option
SE/SLOT/LINK
example: for
ATM
application
NPATM1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PVC/SCHEDULE/SLOT/SVC/USER/VLAN,def:SVC) ? SLOT
SLOT> Slot number (1/2/3/4,def:2) ?
Item (LINK/CHANNEL,def:CHANNEL) ? LINK
PORT 200> Status (def:DISABLE) ? ENABLE
PORT 200> Clock recovery (def:DISABLE) ? ENABLE
PORT 200> Digital port clock source (def:INTERNAL) ? 2
PORT 200> Signaling mode (def:NONE) ?
PORT 200> Pcm encoding law (def:MU-LAW) ?
PORT 200> Idle code (def:7F) ?
PORT 200> Zero suppression mode (def:B8ZS) ?
PORT 200> Gain limit (def:-30DB) ?
PORT 200> Framing mode (def:ESF) ?
PORT 200> Line Build Out (def:0-133FT) ?
PORT 200> Loopback (def:DISABLE) ?
For details on these parameters, consult the appendix SE/SLOT/LINK Configuration
Parameters in the Digital Data fascicle of this document series.
2-14 Memotec Inc.

2.6 Configuring the ATM Channel
Configuration
One and only one ATM channel must be defined on the NetPerformer unit to carry ATM
traffic. This channel can be a block of one or more consecutive timeslots.
To define the ATM channel, use the CHANNEL option of the SETUP/SLOT command.
Unit ID>
(main prompt)
To configure the ATM channel:
1. At the NetPerformer command line prompt, enter the menu sequence: SE � SLOT
2. Select the Slot number of a slot that contains a T1 or E1 interface card
3. Enter CHANNEL
Setup (SE)
4. Select the Channel Number
5. Set the Protocol to ATM
Only one channel can be set to ATM on only one digital interface on the
NetPerformer unit.
6. Select the starting Timeslot
Slot (SL)
Figure 2-4: SETUP/SLOT/CHANNEL Path in the CLI Tree
Channel
7. Set the Number of consecutive timeslots allocated to this channel
E1 and T1 are fractional interfaces, which means that some timeslots can be
allocated for ATM while others are allocated for another service. In the example
which follows, the first 12 time slots are allocated to ATM. The remaining 12 free
timeslots could be configured for Frame Relay.
8. Change the other parameters from their default values, if desired. Information about
these parameters is provided below.
Memotec Inc. 2-15
ATM

ATM Option
SE/SLOT/
CHANNEL/
ATM example
SVCATM1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PVC/SCHEDULE/SLOT/SVC/USER/VLAN,def:SLOT) ?
SLOT> Slot number (1/2/3/4,def:2) ?
Item (LINK/CHANNEL,def:LINK) ? CHANNEL
SLOT> Channel Number (201-224/ALL,def:201) ?
PORT 201> Protocol (def:OFF) ? ATM
PORT 201> Timeslot (def:1) ?
PORT 201> Number of consecutive timeslots (1-24,def:24) ? 12
PORT 201> Idle cell (def:ITU-T) ?
PORT 201> Idle cell payload (def:6A6A6A6A) ?
PORT 201> HEC coset function (def:ENABLE) ?
PORT 201> Scrambling function (def:DISABLE) ?
PORT 201> UNI Version (def:4.0) ?
PORT 201> UNI Type (def:PRIVATE) ? PUBLIC
PORT 201> ATM Signaling Channel VPI (0-255,def:0) ?
PORT 201> ATM Signaling Channel VCI (0-65534,def:5) ?
PORT 201> ILMI Channel VPI (0-255,def:0) ?
PORT 201> ILMI Channel VCI (0-65534,def:16) ?
• Protocol, Timeslot and Number of consecutive timeslots are detailed in the appendix
SE/SLOT/CHANNEL Configuration Parameters in the Digital Data fascicle
of this document series
• For details on the other parameters, turn to “SE/SLOT/CHANNEL Configuration
Parameters” on page 4-1 of this document.
2-16 Memotec Inc.

2.7 Configuring the ATM PVCs
Configuration
A separate PVC must be defined for each ATM access point. Set up all required ATM
PVCs with the SETUP/PVC command.
To configure an ATM PVC:
1. At the NetPerformer command line prompt, enter the menu sequence: SE � PVC
2. Select the PVC number
3. Set the mode to one of the following:
• ATMPVCR: for PowerCell over ATM AAL5, an integrated traffic transport
method (see “PowerCell in the ATM Network” on page 1-16 for background
information)
• AAL1: for ATM AAL1, a voice traffic transport method supported on the NetPerformer
SDM-9360, SDM-9380 and SDM-9585 only (see “AAL1 Circuit Emulation
Services (CES)” on page 1-16 for background information)
• FRF.8: for FRF.8, a Service Interworking method ideal for Frame Relay traffic
(see “Frame Relay/ATM Service Interworking (FRF.8)” on page 1-18)
• RFC1483: for multiprotocol over ATM AAL5 using RFC-1483, a data traffic
transport method (see “LLC Encapsulation (RFC-1483)” on page 1-22)
• ATMPPP: for PPP over ATM AAL5 using RFC-2364, a data traffic transport
method ideal for Internet access (see “PPP Over AAL5” on page 1-23)
• ATM-MULTIPLEX: for multiplexing ATM traffic over PowerCell links (see
“ATM Multiplex Connections” on page 1-24). This mode is ideal for transporting
traffic from any ATM Adaptation Layer. It is also the only PVC mode that can
support AAL2 and AAL3/4 traffic.
4. Set the VPI address
Unit ID>
(main prompt)
Setup (SE)
PVC (PV)
ATMPVCR AAL1 ATMPPP
FRF.8 RFC1483 ATM-
MULTIPLEX
Figure 2-5: SETUP/PVC Path in the CLI Tree
Memotec Inc. 2-17

ATM Option
5. Set the VCI address
6. Set the Service category (SDM-9230 only)
7. Set the Peak cell rate
8. For a variable bit rate Service category (RT-VBR or NRT-VBR on the SDM-9230
only), set the:
• Sustainable cell rate (SCR)
• Maximum burst size (MBS) in cells
9. Change the other parameters from their default values if desired.
Examples and explanations of important parameters are provided according to PVC
mode:
• “PVC in ATMPVCR Mode” on page 2-18
• “PVC in AAL1 Mode” on page 2-21
• “PVC in FRF.8 Mode” on page 2-22
• “PVC in RFC1483 Mode” on page 2-22
• “PVC in ATMPPP Mode” on page 2-24
• “PVC in ATM-MULTIPLEX Mode” on page 2-25.
2.7.1 PVC in ATMPVCR Mode
SE/PVC/
ATMPVCR
example: on
the SDM-9360,
SDM-9380 or
SDM-9585
ATMPVCR mode provides an integrated traffic transport method using the PowerCell
technique over ATM AAL5. See the section “PowerCell in the ATM Network” on page 1-
16 for further information.
• Use this method for voice, data, video or LAN traffic
• It can also provide a link to a Frame Relay device or another NetPerformer.
PVCATM2>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:BRIDGE) ? PVC
PVC number (1-300,def:1) ? 1
PVC 1> Mode (def:PVCR) ? ATMPVCR
PVC 1> VPI address (0-255,def:0) ? 1
PVC 1> VCI address (0-65534,def:0) ? 101
PVC 1> Peak cell rate (0-4679,def:1000) ?
PVC 1> Payload information rate is 384000 bps
PVC 1> Total information rate is 424000 bps
PVC 1> Remote unit name (def:) ? BOSTON-ATMPVCR
PVC 1> Timeout (msec) (1000-30000,def:1000) ?
PVC 1> Number of retransmission retries (1-1000,def:100) ?
PVC 1> Compression (def:YES) ?
PVC 1> IP address (def:000.000.000.000) ?
PVC 1> Subnet mask (number of bits) (0-32,def:8) ?
2-18 Memotec Inc.

SE/PVC/
ATMPVCR
example: on
the SDM-9230
with variable
bit rate Service
category
Configuration
{255.000.000.000}
PVC 1> IP RIP (def:V1) ?
PVC 1> IP RIP TX/RX (def:DUPLEX) ?
PVC 1> OSPF (def:DISABLE) ?
PVC 1> IP multicast active (def:NO) ?
PVC 1> NAT enable (def:NO) ?
PVC 1> IPX RIP (def:DISABLE) ?
PVC 1> IPX SAP (def:DISABLE) ?
PVC 1> IPX network number (def:00000000) ?
PVC 1> Filter (def:ALL) ?
PVC 1> Maximum number of voice channels (0-10000,def:10000) ?
PVC 1> Maximum Voice Channels If High Priority Data (0-
10000,def:10000) ?
PVC 1> Cell Packetization (def:YES) ?
8266>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:PVC) ? PVC
PVC number (1-300,def:1) ?
PVC 1> Mode (def:PVCR) ? ATMPVCR
PVC 1> VPI address (0-63,def:0) ? 1
PVC 1> VCI address (0-1023,def:0) ? 34
PVC 1> Service category (def:UBR) ? NRT-VBR
PVC 1> Peak cell rate (PCR) (0-3622,def:1000) ?
PVC 1> Payload information rate is 384000 bps
PVC 1> Total information rate is 424000 bps
PVC 4> Sustainable cell rate (SCR) (0-3622,def:500) ?
PVC 4> Payload information rate is 192000 bps
PVC 4> Total information rate is 212000 bps
PVC 4> Maximum burst size (MBS) in cells (1-65535,def:1000) ?
PVC 1> Remote unit name (def:) ?
PVC 1> Timeout (msec) (1000-30000,def:1000) ?
PVC 1> Number of retransmission retries (1-1000,def:100) ?
PVC 1> Compression (def:YES) ?
PVC 1> IP address (def:000.000.000.000) ?
PVC 1> Subnet mask (number of bits) (0-32,def:8) ?
{255.000.000.000}
PVC 1> IP RIP (def:V1) ?
PVC 1> IP RIP TX/RX (def:DUPLEX) ?
PVC 1> OSPF (def:DISABLE) ?
PVC 1> IP multicast active (def:NO) ?
PVC 1> NAT enable (def:NO) ?
PVC 1> IPX RIP (def:DISABLE) ?
PVC 1> IPX SAP (def:DISABLE) ?
PVC 1> IPX network number (def:00000000) ?
PVC 1> Filter (def:ALL) ?
PVC 1> Maximum number of voice channels (0-10000,def:10000) ?
PVC 1> Maximum Voice Channels If High Priority Data (0-
10000,def:10000) ?
PVC 1> Cell Packetization (def:YES) ?
• These parameters are detailed in the appendix “SE/PVC Configuration Parameters”
on page 5-1.
Memotec Inc. 2-19

ATM Option
Configuring the Cell Rate Parameters for Variable Bit Rate
Service Categories
To define the cell rate on the PVC connection, Variable Bit Rate service categories (RT-
VBR and NRT-VBR) require the Peak Cell Rate (PCR), Sustainable Cell Rate (SCR) and
Maximum Burst Size (MBS). The other service categories require a PCR definition only.
The NetPerformer performs no validation of bandwidth overload, e.g. going over the
permitted PCR. Correct configuration is therefore very important.
In general, to ensure an adequate cell rate:
• Set the Sustainable cell rate (SCR) parameter to the typical bandwidth requirement
of the VC on the PVC
• Set the Maximum burst size (MBS) in cells to the same value as the Peak cell rate
parameter. This assumes that a traffic burst will last one second.
Example 1:
• The ATM switch is VBR with a PCR of 2000 and SCR of 1000
• The NetPerformer PVC is UBR with a PCR of 2000
• In high traffic situations the NetPerformer must transmit at 2000 cells per second
• However, since the ATM switch allows an SCR of only 1000, it will demand
more cells.
• The NetPerformer will lose data, and the line could go down.
Example 2:
• The ATM switch is VBR with a PCR of 2000 and SCR of 1000
• The NetPerformer is UBR with a PCR of 1000
• Therefore, the rate of the NetPerformer will never surpass the SCR of the switch,
and no data will be lost.
NOTE: A PVC that is configured as either CBR or RT-VBR has higher priority than a
PVC in NRT-VBR or UBR. This is not configurable.
2-20 Memotec Inc.

2.7.2 PVC in AAL1 Mode
SE/PVC/AAL1
example
Configuration
AAL1 mode provides a voice traffic transport method using ATM AAL1 (refer to “AAL1
Circuit Emulation Services (CES)” on page 1-16). This mode is supported on the SDM-
9360, SDM-9380 and SDM-9585 only.
• Use this mode for uncompressed voice traffic.
• It can also provide a link to a legacy ATM application, as well as PSTN access.
9360-1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:BRIDGE) ? PVC
PVC number (1-300,def:1) ?
PVC 1> Mode (def:OFF) ? AAL1
PVC 1> VPI address (0-255,def:0) ? 1
PVC 1> VCI address (0-65535,def:32) ? 102
PVC 1> Peak cell rate (PCR) (0-3622,def:1000) ?
PVC 1> Payload information rate is 384000 bps
PVC 1> Total information rate is 424000 bps
PVC 1> Remote unit name (def:) ? 9260-2
PVC 1> Number of subchannels (1-8,def:1) ? 2
WARNING !!! Modifying the subchannels settings will reset all AAL1
VCs.
PVC 1> Super frame format (def:DS1-ESF) ?
PVC 1> Local inbound voice level (db) (def:0) ?
PVC 1> Local outbound voice level (db) (def:-3) ?
PVC 1> Echo canceler (def:ENABLE) ?
PVC 1> Double talk threshold (db) (def:6) ?
PVC 1> Idle code (def:7F) ?
PVC 1> Jitter buffer(ms) (30-240,def:100) ?
PVC 1> Signaling type (def:IMMEDIATE START) ?
PVC 1> TONE type: (def:DTMF) ?
PVC 1> TONE regeneration: (0-255,def:30) ?
PVC 1> TONE ON (ms) (30-1000,def:100) ?
PVC 1> TONE OFF (ms) (30-1000,def:100) ?
PVC 1> Pulse make/break ratio (30-50,inc:4,def:34) ?
PVC 1> Delete digits (0-4,def:0) ?
PVC 1> Fwd digits (def:NONE) ? ALL
PVC 1> Fwd delay (0-10000,inc:250,def:0) ?
PVC 1> Fwd type (def:TONE) ?
• Mode, VPI address, VCI address and Remote unit name are described in the
appendix “SE/PVC Configuration Parameters” on page 5-1.
• The other parameters are specific to the configuration of a PVC in AAL1 mode.
Refer to “AAL1 Mode” on page 5-22 for details.
Memotec Inc. 2-21

ATM Option
2.7.3 PVC in FRF.8 Mode
FRF.8 mode provides a Service Interworking method using FRF.8, and is used for Frame
Relay traffic. See the section “Frame Relay/ATM Service Interworking (FRF.8)” on
page 1-18 for further information.
SE/PVC/FRF.8
example PVCATM2>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:BRIDGE) ? PVC
PVC number (1-300,def:1) ? 4
PVC 4> Mode (def:PVCR) ? FRF.8
PVC 4> VPI address (0-255,def:0) ? 1
PVC 4> VCI address (0-65534,def:0) ? 103
PVC 4> Peak cell rate (0-3622,def:1000) ?
PVC 4> Payload information rate is 384000 bps
PVC 4> Total information rate is 424000 bps
PVC 4> Port (def:1) ?
PVC 4> DLCI address (0-1022,def:0) ?
PVC 4> Committed Information rate (4000-2048000,def:56000) ?
PVC 4> Burst Information rate (4000-2048000,def:56000) ?
PVC 4> Header translation (def:YES) ?
PVC 4> ATM CLP bit (def:DE) ?
PVC 4> ATM EFCI bit (def:FECN) ?
PVC 4> Frame relay DE bit (def:CLP) ?
PVC 4> Frame relay FECN bit (def:EFCI) ?
PVC 4> Congestion queue size (0-100000,def:4000) ?
PVC 4> Maximum queue size (0-100000,def:8000) ?
2.7.4 PVC in RFC1483 Mode
• VPI address, VCI address, Peak cell rate, Payload information rate and Total
information rate are described in “ATMPVCR Mode” on page 5-4
• The other parameters are particular to a PVC in FRF.8 mode. For details, turn to
“FRF.8 Mode” on page 5-31.
RFC1483 mode provides a data traffic transport method using multiprotocol over ATM
AAL5 (RFC-1483). See the section “LLC Encapsulation (RFC-1483)” on page 1-22 for
further information.
• Use this mode for LAN traffic
• It can also provide a link to a legacy ATM application, a gateway controller or
network management system, as well as Internet access.
2-22 Memotec Inc.

SE/PVC/
RFC1483
example
Configuration
PVCATM2>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:BRIDGE) ? PVC
PVC number (1-300,def:1) ? 5
PVC 5> Mode (def:OFF) ? RFC1483
PVC 5> VPI address (0-255,def:0) ? 1
PVC 5> VCI address (0-65535,def:10) ? 104
PVC 5> Peak cell rate (PCR) (0-3622,def:1000) ?
PVC 5> Payload information rate is 384000 bps
PVC 5> Total information rate is 424000 bps
PVC 5> Remote unit name (def:) ? BOSTON-RFC1483
PVC 5> BRG connection (def:NO) ?
PVC 5> IP connection (def:YES) ?
PVC 5> IP address (def:000.000.000.000) ?
PVC 5> Subnet mask (number of bits) (0-32,def:8) ?
{255.000.000.000}
PVC 5> Frame size (128-8192,def:1500) ?
PVC 5> IP RIP (def:V1) ?
PVC 5> IP RIP TX/RX (def:DUPLEX) ?
PVC 5> OSPF (def:DISABLE) ?
PVC 5> IP multicast active (def:NO) ?
PVC 5> NAT enable (def:NO) ?
PVC 5> IPX connection (def:YES) ?
PVC 5> IPX RIP (def:DISABLE) ?
PVC 5> IPX SAP (def:DISABLE) ?
PVC 5> IPX network number (def:00000000) ?
PVC 5> Filter (def:ALL) ?
• VPI address, VCI address, Peak cell rate, Payload information rate, Total information
rate, Remote unit name, IP address, Subnet mask, IP RIP, IP RIP TX/RX,
OSPF, IP multicast active, NAT enable, IPX connection, IPX RIP, IPX SAP, IPX
network number and Filter are detailed in “ATMPVCR Mode” on page 5-4.
Caution: The Remote Unit Name parameter (SNMP pvcRemoteUnit) is optional
for RFC1483 PVCs, and serves only for information purposes. For example, when
you define a Remote Unit Name, the destination of the PVC will be provided in
PVC UP/DOWN alarms (displayed with the Display Alarms (DA) command). You
must ensure that the Remote Unit Name you select does not interfere with an
existing Remote Unit Name in a mixed network of PVCR and RFC1483 links,
as a name conflict will prevent proper connection. The Remote Unit Name
parameter is also optional for ATMPPP and RFC1490 PVCs, and the same
precaution must be taken with them.
• The BRG connection, IP connection and Frame size parameters are particular
to a PVC in RFC1483 mode. For details, turn to “RFC1483 Mode” on page 5-
37.
Memotec Inc. 2-23

ATM Option
2.7.5 PVC in ATMPPP Mode
SE/PVC/
ATMPPP
example
ATMPPP mode provides a data traffic transport method using PPP over ATM AAL5
(RFC-2364). See the section “PPP Over AAL5” on page 1-23 for further information.
• Use this mode for LAN traffic and Internet access.
9230-1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:BRIDGE) ? PVC
PVC number (1-300,def:1) ? 6
PVC 6> Mode (def:OFF) ? ATMPPP
PVC 6> VPI address (0-63,def:0) ? 1
PVC 6> VCI address (0-1023,def:32) ? 105
PVC 6> Service category (def:UBR) ? CBR
PVC 6> Peak cell rate (PCR) (0-3622,def:1000) ?
PVC 6> Payload information rate is 384000 bps
PVC 6> Total information rate is 424000 bps
PVC 6> Remote unit name (def:) ? 9230-2
PVC 6> LLC encapsulation (def:NO) ?
PVC 6> PPP User (def:NONE) ?
PVC 6> Silent (def:SEND REQUEST) ?
PVC 6> LCP timeout (seconds) (1-255,def:3) ?
PVC 6> LCP retries, 255 = forever (0-255,def:255) ?
PVC 6> Negotiate MRU (def:NO) ?
PVC 6> Use MRU proposed by peer (def:NO) ?
PVC 6> Request Magic Number (def:YES) ?
PVC 6> Accept Magic Number Request (def:YES) ?
PVC 6> Keepalive (def:DISABLE) ?
PVC 6> Accept Addresses Old Negotiation (def:NO) ?
PVC 6> Request IP-Address (def:NO) ?
PVC 6> Accept IP-Address Request (def:NO) ?
PVC 6> Request DNS-Address (def:NO) ?
PVC 6> Accept DNS-Address Request (def:NO) ?
PVC 6> IP address (def:000.000.000.000) ?
PVC 6> Subnet mask (number of bits) (0-32,def:8) ?
{255.000.000.000}
PVC 6> IP RIP (def:V1) ?
PVC 6> IP RIP TX/RX (def:DUPLEX) ?
PVC 6> OSPF (def:DISABLE) ?
PVC 6> IP multicast active (def:NO) ?
PVC 6> NAT enable (def:NO) ?
PVC 6> Filter (def:ALL) ?
• VPI address, VCI address, Service category, Peak cell rate, Payload information
rate, Total information rate, Remote unit name, IP address, Subnet mask, IP RIP,
IP RIP TX/RX, OSPF, IP multicast active, NAT enable and Filter are detailed in
“ATMPVCR Mode” on page 5-4
• PPP User, Silent, LCP timeout, LCP retries, Negotiate MRU, Use MRU proposed
by peer, Request Magic Number, Accept Magic Number Request, Keep-
2-24 Memotec Inc.

2.7.6 PVC in ATM-MULTIPLEX Mode
SE/PVC/ATM-
MULTIPLEX
example
Configuration
alive, Accept Addresses Old Negotiation, Request IP-address, Accept IP-Address
Request, Request DNS-Address and Accept DNS-Address Request behave the
same as for other PPP connections, and are described in the appendix SE/PORT/
#/PPP Configuration Parameters in the WAN/Point-to-Point (PPP) fascicle
of this document series.
ATM-MULTIPLEX mode provides multiplexing of ATM traffic on the SDM-9230 only.
See the section “ATM Multiplex Connections” on page 1-24 for further information.
• Use this mode for a multiplexed ATM connection over PowerCell
• It can also be used to transport traffic from any ATM Adaptation Layer.
PVCATM2>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:BRIDGE) ? PVC
PVC number (1-300,def:4) ? 2
PVC 2> Mode (def:OFF) ? ATM-MULTIPLEX
PVC 2> VPI address (0-63,def:0) ? 12
PVC 2> VCI address (0-1023,def:32) ? 35
PVC 2> ATM Adaptation Layer (def:AAL0) ?
PVC 2> Service category (def:UBR) ? CBR
PVC 2> Peak cell rate (PCR) (0-3622,def:1000) ?
PVC 2> Payload information rate is 384000 bps
PVC 2> Total information rate is 424000 bps
PVC 2> Remote unit name (def:) ? 9230-2
PVC 2> Compression (def:YES) ?
PVC 2> Remote PVC number (1-300,def:2) ?
PVC 2> Class number (def:3) ?
• VPI address, VCI address, Service category, Peak cell rate (PCR), Remote unit
name and Compression are detailed in “ATMPVCR Mode” on page 5-4
• ATM Adaptation Layer, Remote PVC number and Class number are particular to
the ATM-MULTIPLEX mode. For details, turn to “ATM-MULTIPLEX Mode” on
page 5-38.
Memotec Inc. 2-25

ATM Option
2.8 Configuring the ATM SVCs
You can use SVCs rather than PVCs for the logical connections (refer to “PVCs Versus
SVCs in the Network” on page 1-6). Set up all required ATM SVCs with the SETUP/SVC
command.
Unit ID>
(main prompt)
To configure an ATM SVC:
1. At the NetPerformer command line prompt, enter the menu sequence: SE � SVC
2. Select the SVC number
Setup (SE)
SVC (SV)
ATMPVCR
FRF.8 RFC1483
Figure 2-6: SETUP/SVC Path in the CLI Tree
3. Set the Mode to one of the following:
- ATMPVCR: Refer to “SVC in ATMPVCR Mode” on page 2-27 for details
- FRF.8: Refer to “SVC in FRF.8 Mode” on page 2-29
- RFC1483: Refer to “SVC in RFC1483 Mode” on page 2-30
- ATMPPP: Refer to “SVC in ATMPPP Mode” on page 2-31.
4. Change the other parameters from their default values, if desired.
ATMPPP
NOTE: You can define up to 300 SVCs on a single NetPerformer unit.
The SVC connections are permanent. That is, the SVC is connected at
startup and remains connected throughout the entire session.
ATM AAL1 is not supported on SVCs. For an AAL1 connection you must
use a PVC on an SDM-9360, SDM-9380 or SDM-9585.
Some of the parameters displayed at the console depend on whether AESA or
2-26 Memotec Inc.

2.8.1 SVC in ATMPVCR Mode
SE/SVC/
ATMPVCR
example: with
PRIVATE UNI
Configuration
E.164 addressing is used, as determined by the UNI Type setting on the digital
channel. Refer to “User to Network Interface (UNI)” on page 1-7. Examples
for both PUBLIC and PRIVATE UNI are provided below (see “SE/SVC/
ATMPVCR example: with PRIVATE UNI” on page 2-27).
ATMPVCR mode provides an integrated traffic transport method using the PowerCell
technique over ATM AAL5.
• Use this method for voice, data, video or LAN traffic transport to another NetPerformer
unit.
NOTE: When the UNI Type parameter on the ATM channel is set to PRIVATE, the
SVC Destination address and Local Address parameters are presented on the
screen. These addresses take the 20-byte AESA (ATM End System Address)
format.
SVCATM1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:BRIDGE) ? SVC
SVC number (1-300,def:1) ?
SVC 1> Mode (def:OFF) ? ATMPVCR
SVC 1> SVC Destination address
(def:0000000000000000000000000000000000000000) ?
47009181000000003080191D0100000000000200
SVC 1> Local Address (def:00000000000000) ? 00000000000100
SVC 1> Type (def:DEDICATED) ?
SVC 1> Call Delay (1-255,def:5) ?
SVC 1> Call Retry Delay (1-255,def:10) ?
SVC 1> Service category (def:UBR) ? CBR
SVC 1> Peak cell rate (PCR) (0-4679,def:1000) ?
SVC 1> Payload information rate is 384000 bps
SVC 1> Total information rate is 424000 bps
SVC 1> Remote unit name (def:) ? SVCATM2
SVC 1> Timeout (msec) (1000-30000,def:1000) ?
SVC 1> Number of retransmission retries (1-1000,def:100) ?
SVC 1> Compression (def:YES) ?
SVC 1> IP address (def:000.000.000.000) ?
SVC 1> Subnet mask (number of bits) (0-32,def:8) ?
{255.000.000.000}
SVC 1> IP RIP (def:V1) ?
SVC 1> IP RIP TX/RX (def:DUPLEX) ?
SVC 1> OSPF (def:DISABLE) ?
SVC 1> IP multicast active (def:NO) ?
SVC 1> NAT enable (def:NO) ?
SVC 1> IPX RIP (def:DISABLE) ?
Memotec Inc. 2-27

ATM Option
SE/SVC/
ATMPVCR
example: with
PUBLIC UNI
SVC 1> IPX SAP (def:DISABLE) ?
SVC 1> IPX network number (def:00000000) ?
SVC 1> Filter (def:ALL) ?
SVC 1> Maximum number of voice channels (0-10000,def:10000) ?
SVC 1> Maximum Voice Channels If High Priority Data (0-
10000,def:10000) ?
SVC 1> Cell Packetization (def:YES) ?
• These parameters are detailed in the appendix “SE/SVC Configuration Parameters”
on page 6-1.
NOTE: The SVC Destination address is composed of the address of the switch, e.g.,
47009181000000003080191D01, and the address of the remote SVC, e.g.,
00000000000200.
When the UNI Type parameter on the ATM channel is set to PUBLIC, the SVC
Destination E.164 address and SVC Local E.164 address parameters appear.
These addresses take the E.164 public UNI format.
SVCATM1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:SLOT) ? SVC
SVC number (1-300,def:1) ?
SVC 1> Mode (def:OFF) ? ATMPVCR
SVC 1> SVC Destination E.164 address (def:0000000000) ? 4182220001
SVC 1> SVC Local E.164 address (def:0000000000) ? 4181110001
SVC 1> Type (def:DEDICATED) ?
SVC 1> Call Delay (1-255,def:5) ?
SVC 1> Call Retry Delay (1-255,def:10) ?
SVC 1> Service category (def:UBR) ? CBR
SVC 1> Peak cell rate (PCR) (0-3622,def:1000) ?
SVC 1> Payload information rate is 384000 bps
SVC 1> Total information rate is 424000 bps
SVC 1> Remote unit name (def:) ? SVCATM2
SVC 1> Timeout (msec) (1000-30000,def:1000) ?
SVC 1> Number of retransmission retries (1-1000,def:100) ?
SVC 1> Compression (def:YES) ?
SVC 1> IP address (def:000.000.000.000) ?
SVC 1> Subnet mask (number of bits) (0-32,def:8) ?
{255.000.000.000}
SVC 1> IP RIP (def:V1) ?
SVC 1> IP RIP TX/RX (def:DUPLEX) ?
SVC 1> OSPF (def:DISABLE) ?
SVC 1> IP multicast active (def:NO) ?
SVC 1> NAT enable (def:NO) ?
SVC 1> IPX RIP (def:DISABLE) ?
SVC 1> IPX SAP (def:DISABLE) ?
SVC 1> IPX NETWORK NUMBER (def:00000000) ?
2-28 Memotec Inc.

SE/SVC/
ATMPVCR
example:
ANSWER Type
2.8.2 SVC in FRF.8 Mode
SE/SVC/FRF.8
example
Configuration
SVC 1> Maximum number of voice channels (0-10000,def:10000) ?
SVC 1> Maximum Voice Channels If High Priority Data (0-
10000,def:10000) ?
SVC 1> Cell Packetization (def:YES) ?
NOTE: When the Type parameter is set to ANSWER, the Call Delay and Call Retry
Delay parameters do not appear, as shown in the following example:
SVCATM2>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:SLOT) ? SVC
SVC number (1-300,def:1) ?
SVC 1> Mode (def:OFF) ? ATMPVCR
SVC 1> SVC Destination E.164 address (def:0000000000) ? 4181110001
SVC 1> SVC Local E.164 address (def:0000000000) ? 4182220001
SVC 1> Type (def:DEDICATED) ? ANSWER
SVC 1> Service category (def:UBR) ? CBR
SVC 1> Peak cell rate (PCR) (0-3622,def:1000) ?
SVC 1> Payload information rate is 384000 bps
SVC 1> Total information rate is 424000 bps
...
FRF.8 mode provides a Service Interworking method using FRF.8.
• Use this mode for transporting Frame Relay traffic.
9230-1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:BRIDGE) ? SVC
SVC number (1-300,def:1) ? 1
SVC 1> Mode (def:OFF) ? FRF.8
SVC 1> SVC Destination address
(def:0000000000000000000000000000000000000000) ?
47009181000000003080191D0100000000000100
SVC 1> Local Address (def:00000000000000) ? 00000000000200
SVC 1> Type (def:DEDICATED) ?
SVC 1> Call Delay (1-255,def:5) ?
SVC 1> Call Retry Delay (1-255,def:10) ?
SVC 1> Service category (def:UBR) ? CBR
SVC 1> Peak cell rate (PCR) (0-3622,def:1000) ?
Memotec Inc. 2-29

ATM Option
2.8.3 SVC in RFC1483 Mode
SE/SVC/
RFC1483
example
SVC 1> Payload information rate is 384000 bps
SVC 1> Total information rate is 424000 bps
SVC 1> Port (def:1) ?
SVC 1> DLCI address (0-1022,def:0) ?
SVC 1> Committed Information rate (4000-6144000,def:56000) ?
SVC 1> Burst Information rate (4000-6144000,def:56000) ?
SVC 1> Header translation (def:YES) ?
SVC 1> ATM CLP bit (def:DE) ?
SVC 1> ATM EFCI bit (def:FECN) ?
SVC 1> Frame relay DE bit (def:CLP) ?
SVC 1> Frame relay FECN bit (def:EFCI) ?
SVC 1> Congestion queue size (0-100000,def:4000) ?
SVC 1> Maximum queue size (0-100000,def:8000) ?
• Mode, SVC Destination address, Local Address, Type and Peak cell rate (PCR)
are described in “ATMPVCR Mode” on page 6-3
• The other parameters are typical of a Frame Relay logical connection, and are
fully described in the appendix “SE/PVC Configuration Parameters” on page 5-
1. Consult the section FRF.8 Mode on page 31 under the equivalent parameter
name.
RFC1483 mode provides a data transmission method using multiprotocol transport over
ATM AAL5 (RFC-1483).
• Use this mode for LAN traffic
• RFC1483 mode can also provide a link to a legacy ATM application, a gateway
controller or network management system, as well as access to the Internet.
SVCATM2>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:SVC) ?
SVC number (1-300,def:3) ?
SVC 3> Mode (def:OFF) ? RFC1483
SVC 3> SVC Destination address
(def:0000000000000000000000000000000000000000) ?
47009181000000003080191D0100000000000500
SVC 3> Local Address (def:00000000000000) ? 00000000000600
SVC 3> Type (def:DEDICATED) ?
SVC 3> Call Delay (1-255,def:5) ?
SVC 3> Call Retry Delay (1-255,def:10) ?
SVC 3> Service category (def:UBR) ? CBR
SVC 3> Peak cell rate (PCR) (0-3622,def:1000) ?
SVC 3> Payload information rate is 384000 bps
SVC 3> Total information rate is 424000 bps
SVC 3> Remote unit name (def:) ? SVCATM1
SVC 3> BRG connection (def:NO) ?
SVC 3> IP connection (def:YES) ?
2-30 Memotec Inc.

2.8.4 SVC in ATMPPP Mode
SE/SVC/
ATMPPP
example
SVC 3> IP address (def:000.000.000.000) ?
SVC 3> Subnet mask (number of bits) (0-32,def:8) ?
{255.000.000.000}
SVC 3> Frame size (128-8192,def:1500) ?
SVC 3> IP RIP (def:V1) ?
SVC 3> IP RIP TX/RX (def:DUPLEX) ?
SVC 3> OSPF (def:DISABLE) ?
SVC 3> IP multicast active (def:NO) ?
SVC 3> NAT enable (def:NO) ?
SVC 3> IPX connection (def:YES) ?
SVC 3> IPX RIP (def:DISABLE) ?
SVC 3> IPX SAP (def:DISABLE) ?
SVC 3> Filter (def:ALL) ?
Configuration
• Mode, SVC Destination address, Local Address, Type, Call Delay, Call Retry
Delay and Peak cell rate (PCR) are described in “ATMPVCR Mode” on page 6-3
• The other parameters are typical of an RFC1483 logical connection, and are fully
described in the appendix “SE/PVC Configuration Parameters” on page 5-1.
Consult the section “RFC1483 Mode” on page 5-37 under the equivalent parameter
name.
ATMPPP mode provides a data traffic transport method using PPP over ATM AAL5
(RFC-2364).
• Use this mode for LAN traffic and Internet access.
SVCATM1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:SLOT) ? SVC
SVC number (1-300,def:1) ? 2
SVC 2> Mode (def:OFF) ? ATMPPP
SVC 2> SVC Destination address
(def:0000000000000000000000000000000000000000) ?
47009181000000003080191D0100000000000100
SVC 2> Local Address (def:00000000000000) ? 00000000000300
SVC 2> Type (def:DEDICATED) ?
SVC 2> Call Delay (1-255,def:5) ?
SVC 2> Call Retry Delay (1-255,def:10) ?
SVC 2> Service category (def:UBR) ? CBR
SVC 2> Peak cell rate (PCR) (0-3622,def:1000) ?
SVC 2> Payload information rate is 384000 bps
SVC 2> Total information rate is 424000 bps
SVC 2> Remote unit name (def:) ? SVCATM2
SVC 2> LLC encapsulation (def:NO) ?
SVC 2> PPP User (def:NONE) ? 1
SVC 1> Silent (def:SEND REQUEST) ?
SVC 1> LCP timeout (seconds) (1-255,def:3) ?
SVC 1> LCP retries, 255 = forever (0-255,def:255) ?
Memotec Inc. 2-31

ATM Option
SVC 1> Negotiate MRU (def:NO) ?
SVC 1> Use MRU proposed by peer (def:NO) ?
SVC 1> Request Magic Number (def:YES) ?
SVC 1> Accept Magic Number Request (def:YES) ?
SVC 1> Accept Addresses Old Negotiation (def:NO) ?
SVC 1> Request IP-Address (def:NO) ?
SVC 1> Accept IP-Address Request (def:NO) ?
SVC 1> Request DNS-Address (def:NO) ?
SVC 1> Accept DNS-Address Request (def:NO) ?
SVC 1> IP address (def:000.000.000.000) ?
SVC 1> Subnet mask (number of bits) (0-32,def:8) ?
{255.000.000.000}
SVC 1> IP RIP (def:V1) ?
SVC 1> IP RIP TX/RX (def:DUPLEX) ?
SVC 1> OSPF (def:DISABLE) ?
SVC 1> IP multicast active (def:NO) ?
SVC 1> NAT enable (def:NO) ?
SVC 1> Filter (def:ALL) ?
• Mode, SVC Destination address, Local Address, Type, Call Delay, Call Retry
Delay and Peak cell rate (PCR) are described in “ATMPVCR Mode” on page 6-3
• The other parameters are typical of a PPP logical connection, and are fully
described in the appendix “SE/PVC Configuration Parameters” on page 5-1.
Consult the section “ATMPPP Mode” on page 5-38 under the equivalent parameter
name.
2-32 Memotec Inc.

2.9 Configuration Examples
Configuration
This section provides an example of NetPerformer ATM configuration for both types of
deployment supported by the product:
• Deployment as an ATM Integrated Access Device (see next section)
• Deployment as an ATM multiplexer (“Using the NetPerformer as an ATM Multiplexer”
on page 2-36).
NOTE: NetPerformer ATM configuration requires that the ATM license be activated
on the unit.
2.9.1 Using the NetPerformer as an Integrated Access Device
Figure 2-7: Using the NetPerformer as an Integrated Access Device
Memotec Inc. 2-33

ATM Option
SE/SLOT/#/
LINK example
SE/SLOT/#/
CHANNEL
example
Slot 1 Configuration
NOTE: This configuration is also required for deployment of the NetPerformer as an
ATM multiplexer.
9230-1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:BRIDGE) ? SLOT
SLOT> Slot number (1/2,def:1) ? 1
Item (LINK/CHANNEL,def:LINK) ? LINK
PORT 100> Status (def:DISABLE) ? ENABLE
PORT 100> Clock recovery (def:ENABLE) ?
GLOBAL > Digital port clock source (def:1) ? 1
PORT 100> Signaling mode (def:NONE) ? NONE
PORT 100> Pcm encoding law (def:MU-LAW) ?
PORT 100> Hunt Group Sorting (def:RRA) ?
PORT 100> Idle code (def:7F) ?
PORT 100> Zero suppression mode (def:B8ZS) ?
PORT 100> Gain limit (def:-30DB) ?
PORT 100> Framing mode (def:ESF) ?
PORT 100> Line Build Out (def:0-133FT) ?
PORT 100> Loopback (def:DISABLE) ?
9230-1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:SLOT) ?
SLOT> Slot number (1/2,def:1) ?
Item (LINK/CHANNEL,def:LINK) ? CHANNEL
SLOT> Channel Number (101-124/ALL,def:101) ?
PORT 101> Protocol (def:OFF) ? ATM
PORT 101> Timeslot (def:1) ?
PORT 101> Number of consecutive timeslots (1-24,def:1) ? 24
PORT 101> Idle cell (def:ITU-T) ?
PORT 101> Idle cell payload (def:6A6A6A6A) ?
PORT 101> HEC coset function (def:ENABLE) ?
PORT 101> Scrambling function (def:DISABLE) ?
PORT 101> UNI Version (def:NONE) ?
PORT 101> UNI Type (def:PRIVATE) ?
PORT 101> ATM Signaling Channel VPI (0-255,def:0) ?
PORT 101> ATM Signaling Channel VCI (0-65535,def:5) ?
PORT 101> ILMI Channel VPI (0-255,def:0) ?
PORT 101> ILMI Channel VCI (0-65535,def:16) ?
2-34 Memotec Inc.

SE/PVC/#/
ATMPVCR
example
PVC Configuration
Configuration
9230-1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:SLOT) ? PVC
PVC number (1-300,def:1) ?
PVC 1> Mode (def:OFF) ? ATMPVCR
PVC 1> VPI address (0-255,def:0) ? 5
PVC 1> VCI address (0-65535,def:32) ? 22
PVC 1> Service category (def:UBR) ? CBR
PVC 1> Peak cell rate (PCR) (0-3622,def:1000) ?
PVC 1> Payload information rate is 384000 bps
PVC 1> Total information rate is 424000 bps
PVC 1> Remote unit name (def:) ? 9230-2
PVC 1> Timeout (msec) (1000-30000,def:1000) ?
PVC 1> Number of retransmission retries (1-1000,def:100) ?
PVC 1> Compression (def:YES) ?
PVC 1> IP address (def:000.000.000.000) ?
PVC 1> Subnet mask (number of bits) (0-32,def:8) ?
{255.000.000.000}
PVC 1> IP RIP (def:V1) ?
PVC 1> IP RIP TX/RX (def:DUPLEX) ?
PVC 1> OSPF (def:DISABLE) ?
PVC 1> IP multicast active (def:NO) ?
PVC 1> NAT enable (def:NO) ?
PVC 1> IPX RIP (def:DISABLE) ?
PVC 1> IPX SAP (def:DISABLE) ?
PVC 1> IPX network number (def:00000000) ?
PVC 1> Filter (def:ALL) ?
PVC 1> Maximum number of voice channels (0-10000,def:10000) ?
PVC 1> Maximum Voice Channels If High Priority Data (0-
10000,def:10000) ?
PVC 1> Cell Packetization (def:YES) ?
Memotec Inc. 2-35

ATM Option
2.9.2 Using the NetPerformer as an ATM Multiplexer
SE/PVC/#/
ATM-
MULTIPLEX
example
Figure 2-8: Using the NetPerformer as an ATM Multiplexer
Slot 1 Configuration
See “Slot 1 Configuration” on page 2-34.
PVC Configuration
9230-1>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SVC/USER/VLAN,
def:PVC) ?
PVC number (1-300,def:12) ? 1
PVC 1> Mode (def:OFF) ? ATM-MULTIPLEX
PVC 1> VPI address (0-255,def:0) ? 10
PVC 1> VCI address (0-65535,def:32) ? 42
PVC 1> ATM Adaptation Layer (def:AAL0) ? AAL5
PVC 1> Service category (def:UBR) ? CBR
PVC 1> Peak cell rate (PCR) (0-3622,def:1000) ?
PVC 1> Payload information rate is 384000 bps
PVC 1> Total information rate is 424000 bps
PVC 1> Remote unit name (def:) ? 9230-2
PVC 1> Compression (def:YES) ?
PVC 1> Remote PVC number (1-300,def:1) ? 1
PVC 1> Class number (def:3) ?
2-36 Memotec Inc.

Monitoring and Statistics
3
Memotec Inc. 3-1

ATM Option
3.1 About the Statistic Commands
Display States
(DS)
Once the unit is powered up, the ATM option installed, and the ATM link, channel, PVCs
and SVCs are configured, you can execute NetPerformer statistics commands from the
console to check the status of ATM operations.
NOTE: All of the commands mentioned in this chapter can be executed by users with
FULL or MONITOR console access.
The ATM statistics commands include the following:
• Display States (DS): Provides current status information concerning a specific
slot, PVC or SVC.
NOTE: These statistics can also be displayed in real time with the DPORT, DPVC and
DSVC commands.
• Display Counters (DC): Shows all counters stored in memory, including the mean
or peak value of the transmitter and receiver rates.
• Display Errors (DE): Displays the values of the error counters for all slots, PVCs
and SVCs.
• Check the current number of reserved and configured data channels and ATM
AAL5 VCs by executing the GLOBAL option of the Display Parameters (DP)
command. Refer to “Tips for Configuring Shared RAM Allocation” on page 2-9.
• View any alarms that were triggered using the Display Alarms (DA) command.
• Enable the capture and display of all traffic through the ATM link, PVC or SVC
with the Setup Capture (SC), Start Capture (STC), and View Capture (VC) commands.
Display Counters
(DC)
Unit ID>
(main prompt)
Display Errors
(DE)
Current status Traffic counters
(tx and rx)
Error counters
Display Parameters
(DP)
SLOT PVC SVC SLOT PVC SVC SLOT PVC SVC
GLOBAL
Parameter
values
Figure 3-1: Display Commands in the CLI Tree for ATM Connections
Display Alarms
(DA)
Alarm log
3-2 Memotec Inc.

Monitoring and Statistics
NOTE: Viewing the status of ATM ports and PVCs is similar in process and display to
the same commands applied to Frame Relay ports and PVCs. Consult the
chapter Checking Frame Relay Connection Status in the WAN/Frame
Relay fascicle of this document series.
Some examples of viewing the status of ATM PVCs are provided in “Status of ATM
PVCs” on page 3-11.
Memotec Inc. 3-3

ATM Option
3.2 Status of ATM SVCs
The status of ATM SVCs can be determined from the following NetPerformer statistics
commands:
• Display Counters (DC), SVC option (see “Displaying the SVC Counters (DC/
SVC)” on page 3-4)
• Display States (DS), SVC option (see “Displaying the SVC States (DS/SVC)” on
page 3-5)
• Display Errors (DE), SVC option (see “Displaying the SVC Errors (DE/SVC)”
on page 3-8)
• Display SVC States (DSVC) command, for a continuously updated real-time status
display (see “Continuous Display of SVC States (DSVC)” on page 3-8).
3.2.1 Displaying the SVC Counters (DC/SVC)
DC/SVC
example
Display Counters
(DC)
SVC
Display States
(DS)
SVC
Unit ID>
(main prompt)
Figure 3-2: ATM SVC Statistics Commands in the CLI Tree
To display the counters for an ATM SVC:
1. At the NetPerformer command line prompt, enter the menu sequence: DC � SVC
2. Select MEAN or PEAK counter values.
Display Errors
(DE)
SVCATM1>DC
DISPLAY COUNTERS
Item (BOOTP/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/SLOT/SVC/
TIMEP,
def:BOOTP) ? SVC
Counters (MEAN/PEAK,def:MEAN) ?
SVC 1> Transmitter cell rate used...............0 % (M)
SVC 1> Transmitter access rate used.............0 % (M)
SVC 1> Receiver cell rate used..................0 % (M)
SVC 1> Receiver access rate used................0 % (M)
SVC 1> Number of frames transmitted.............38
SVC 1> Number of frames received................39
3-4 Memotec Inc.
SVC
Display SVC
States (DSVC)

Monitoring and Statistics
SVC 1> Number of frames received with CLP set...0
SVC 1> Number of octets transmitted.............3498
SVC 1> Number of octets received................3180
SVC 1> Number of cells transmitted..............66
SVC 1> Number of cells received.................60
SVC 1> OAM F5 VC-AIS cells received.............0
SVC 1> OAM F5 VC-AIS cells transmitted..........0
SVC 1> OAM F5 VC-RDI cells received.............0
SVC 1> OAM F5 VC-RDI cells transmitted..........0
SVC 1> OAM F5 VC Loopback cells received........0
SVC 1> OAM F5 VC Loopback cells transmitted.....0
These statistics are also displayed for an ATM PVC connection.
NOTE: The Transmitter cell rate used and Receiver cell rate used statistics refer to
the:
• PCR: For SVCs set to the CBR or UBR Service category
• SCR: For SVCs set to the RT-VBR or NRT-VBR Service category.
3.2.2 Displaying the SVC States (DS/SVC)
To display the status of an ATM SVC:
• At the NetPerformer command line prompt, enter the menu sequence: DS � SVC
The following example shows the status display that is provided for all types of ATM
SVCs.
DS/SVC/ATM
example SSVCATM1>DS
DISPLAY STATES
Item (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:SVC) ?
SVC 2> Mode.....................................ATMPVCR
SVC 2> Information signals......................-A---
SVC 2> Speed used (bps).........................424 k
SVC 2> SVC Status...............................UP
SVC 2> SVC Local
address........................47009181000000003080191D01000000
00000100
SVC 2> SVC Destination
address..................47009181000000003080191D01000000
00000200
SVC 2> VPI......................................0
SVC 2> VCI......................................165
SVC 2> PVC name.................................SVCATM2
SVC 2> State & Delay............................DATA 31ms
---- SVC #3 FRF.8 --> ATM Side ----
SVC 3> Mode.....................................FRF8
SVC 3> Information signals......................-A---
Memotec Inc. 3-5

ATM Option
SVC 3> Speed used (bps).........................424 k
SVC 3> SVC Status...............................UP
SVC 3> SVC Local address..........
........................47009181000000003080191D01A0000000000200
SVC 3> SVC Destination address....
........................47009181000000003080191D01B0000000000200
SVC 3> VPI......................................0
SVC 3> VCI......................................162
SVC 3> State & Delay............................DATA 0ms
---- SVC #3 FRF.8 --> FR port #1 ----
SVC 3> Information signals......................USER -A---
SVC 3> Speed used (bps).........................56000
SVC 3> DLCI.....................................111
SVC 3> State & Delay............................DATA 0ms
SVC 4> Mode.....................................RFC1483
SVC 4> Information signals......................-A---
SVC 4> Speed used (bps).........................424 k
SVC 4> SVC Status...............................UP
SVC 4> SVC Local address..........
........................47009181000000003080191D01A0000000000300
SVC 4> SVC Destination address....
........................47009181000000003080191D01B0000000000300
SVC 4> VPI......................................0
SVC 4> VCI......................................172
SVC 4> PVC name.................................
SVC 4> State & Delay............................DATA 0ms
SVC 5> Mode.....................................ATMPPP
SVC 5> Information signals......................-A---
SVC 5> Speed used (bps).........................424 k
SVC 5> SVC Status...............................UP
SVC 5> SVC Local address..........
........................47009181000000003080191D01A0000000000400
SVC 5> SVC Destination address....
........................47009181000000003080191D01B0000000000400
SVC 5> VPI......................................0
SVC 5> VCI......................................173
SVC 5> PVC name.................................
SVC 5> State & Delay............................DATA 0ms
Info signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn (-
)off
NOTE: Most of these statistics are also displayed for an ATM PVC connection. The
SVC-specific statistics include the following:
3-6 Memotec Inc.

SVC Status
Console SNMP
SVC Status statSvcAtmStatus
Monitoring and Statistics
The SVC status can be:
• DOWN: Indicates the SVC connection is not established. In SNMP this value is
represented as 0
• UP: Indicates the SVC connection has been established, and is up and running.
In SNMP this value is represented as 1.
NOTE: SVC Status shows the current signaling state of the SVC, and not the protocol
state. This means that the SVC status could be UP while the PVCR port
state is DOWN or CALL.
SVC Local address
Console SNMP
SVC Local address statSvcAtmLocalAddr
The value of this field may be:
• A 40-digit AESA address: Indicates that the SVC is connected to a private ATM
network and has been successfully registered with the switch.
• A 15-digit E.164 address: Indicates that the SVC is connected to a public ATM
network and has been successfully registered with the switch.
• NOT REGISTERED: Indicates that the SVC is connected to a private ATM network,
but the address has not been successfully registered with the switch.
NOTE: If the SVC is connected to a public network no address registration is
required. In this case, the SVC Local address statistic always displays 15-digit
E.164 address.
SVC Destination address
Console SNMP
SVC Destination address statSvcAtmDestAddr
The value of this field may be:
• A 40-digit AESA address: Indicates that the SVC is connected to a private ATM
network.
Memotec Inc. 3-7

ATM Option
• A 15-digit E.164 address: Indicates that the SVC is connected to a public ATM
network.
3.2.3 Displaying the SVC Errors (DE/SVC)
To display the error counters for an ATM SVC:
• At the NetPerformer command line prompt, enter the menu sequence: DE � SVC
DE/SVC/ATM
example SVCATM1>DE
DISPLAY ERRORS
Item (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PU/PVC/Q922/SLOT/SVC/
TIMEP,
def:BOOTP) ? SVC
SVC 1> Number of frames discarded (crc error)...0
SVC 1> Number of frames discarded (overrun).....0
SVC 1> Number of invalid frames discarded.......0
SVC 1> Other frames discarded...................0
---- SVC #2 FRF.8 --> ATM Side ----
SVC 2> Number of frames discarded (crc error)..0
SVC 2> Number of frames discarded (overrun)....0
SVC 2> Number of invalid frames discarded......0
SVC 2> Other frames discarded..................0
---- SVC #2 FRF.8 --> FR port #1 ----
SVC 2> Number of errors........................0
SVC 2> Number of restarts......................0
SVC 2> Number of invalid frames discarded......0
SVC 2> Number of frames discarded (overrun)....0
SVC 2> Number of invalid octets discarded......0
SVC 2> Number of octets discarded (overrun)....0
NOTE: These statistics are also displayed for an ATM PVC connection. In the example
above, statistics for SVC 2 are unique to an SVC in FRF.8 mode, and
show both the ATM side and the Frame Relay port side of the connection.
3.2.4 Continuous Display of SVC States (DSVC)
The DSVC command provides a continuously updated display of ATM SVC status in real
time.
To display the status of ATM SVCs in real time:
1. Enter DSVC
2. Enter ATM as the SVC TYPE.
3-8 Memotec Inc.

DSVC/ATM
example
Monitoring and Statistics
SVCATM1>DSVC
DISPLAY SVC STATES
SVC TYPE (ATM/FR,def:FR) ? ATM
--------------------------------------------------------------------------------
|SVC MODE DESTINATION ADDRESS SVC STATE & |
| STATUS DELAY(MS) |
--------------------------------------------------------------------------------
| 1 ATMPVCR 47009181000000003080191D0100000000000200 UP DATA 38 |
| 2 ATMPPP 47009181000000003080191D0100000000000400 UP DATA 0 |
| 3 RFC1483 47009181000000003080191D0100000000000600 UP OFF |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| Information signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn (-)off |
--------------------------------------------------------------------------------
Use HOME, END, UP and DOWN arrow keys to scroll. Press any other key to exit.
SVC MODE
The protocol currently in use on this ATM SVC. The displayed mode may be ATMPVCR,
ATMPPP, RFC1483 or FRF8.
DESTINATION ADDRESS
The AESA or E.164 destination address of the equipment to which this ATM SVC
transmits traffic.
SVC STATUS
Console SNMP
SVC MODE statSvcAtmMode
Console SNMP
DESTINATION ADDRESS statSvcAtmDestAddr
Console SNMP
SVC STATUS statSvcAtmStatus
Indicates whether the ATM SVC is currently connected to its destination (UP or DOWN).
Memotec Inc. 3-9

ATM Option
NOTE: The significance of this statistic depends on the protocol (or mode) used on
the VC. Even if the indicated SVC STATUS is UP, some protocols may require
further negotiation before allowing the exchange of traffic over the VC.
STATE & DELAY (MS)
Console SNMP
STATE & DELAY (MS) statSvcAtmState
The current state and delay in milliseconds on the ATM SVC, continuously refreshed and
displayed in real time.
3-10 Memotec Inc.

3.3 Status of ATM PVCs
DC/PVC
example
Display Counters
(DC)
PVC
Monitoring and Statistics
The status of ATM PVCs can be determined from the following NetPerformer statistics
commands:
• Display Counters (DC), PVC option
• Display States (DS), PVC option
• Display Errors (DE), PVC option
• Display PVC States (DPVC) command, for a continuously updated real-time status
display.
Display States
(DS)
PVC
Unit ID>
(main prompt)
Display Errors
(DE)
Figure 3-3: ATM PVC Statistics Commands in the CLI Tree
These commands are executed in the same way as their counterparts for viewing SVC
status (see “Status of ATM SVCs” on page 3-4), except that you enter PVC instead of
SVC.
NP2>DC
DISPLAY COUNTERS
Item (BOOTP/CHANNEL/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/
REDUNDANCY/
SLOT/SNMP/SVC/TIMEP,def:BOOTP) ? PVC
Counters (MEAN/PEAK,def:MEAN) ?
PVC 1> Transmitter cell rate used...............99 % (M)
PVC 1> Transmitter access rate used.............39 % (M)
PVC 1> Receiver cell rate used..................99 % (M)
PVC 1> Receiver access rate used................39 % (M)
PVC 1> Number of frames transmitted.............3391343
PVC 1> Number of frames received................3391571
PVC 1> Number of frames received with CLP set...0
PVC 1> Number of octets transmitted.............185238127
PVC 1> Number of octets received................185258055
PVC 1> Number of cells transmitted..............3495059
PVC 1> Number of cells received.................3495435
PVC 1> OAM F5 VC-AIS cells received.............0
PVC 1> OAM F5 VC-AIS cells transmitted..........0
PVC 1> OAM F5 VC-RDI cells received.............0
PVC 1> OAM F5 VC-RDI cells transmitted..........0
Memotec Inc. 3-11
PVC
Display PVC States
(DPVC)

ATM Option
PVC 1> OAM F5 VC Loopback cells received........0
PVC 1> OAM F5 VC Loopback cells transmitted.....0
---- PVC #4 FRF.8 --> ATM Side ----
PVC 4> Transmitter cell rate used...............0 % (M)
PVC 4> Transmitter access rate used.............0 % (M)
PVC 4> Receiver cell rate used..................0 % (M)
PVC 4> Receiver access rate used................0 % (M)
PVC 4> Number of frames transmitted.............0
PVC 4> Number of frames received................0
PVC 4> Number of frames received with CLP set...0
PVC 4> Number of octets transmitted.............0
PVC 4> Number of octets received................0
PVC 4> Number of cells transmitted..............0
PVC 4> Number of cells received.................0
PVC 4> OAM F5 VC-AIS cells received.............366
PVC 4> OAM F5 VC-AIS cells transmitted..........699
PVC 4> OAM F5 VC-RDI cells received.............292
PVC 4> OAM F5 VC-RDI cells transmitted..........547
PVC 4> OAM F5 VC Loopback cells received........0
PVC 4> OAM F5 VC Loopback cells transmitted.....0
---- PVC #4 FRF.8 --> FR port #101 ----
PVC 4> Transmitter rate.........................0 % (M)
PVC 4> Receiver rate............................0 % (M)
PVC 4> Number of frames transmitted.............0
PVC 4> Number of frames received................0
PVC 4> Number of octets transmitted.............0
PVC 4> Number of octets received................0
PVC 4> Number of BECN received..................0
PVC 4> Number of BECN transmitted...............0
PVC 4> Number of FECN received..................0
PVC 4> Number of FECN transmitted...............0
PVC 4> Number of CLLM frames received...........0
PVC 4> Number of CLLM frames transmitted........0
NOTE: The Transmitter cell rate used and Receiver cell rate used statistics refer to
the:
• PCR: For SVCs set to the CBR or UBR Service category
• SCR: For SVCs set to the RT-VBR or NRT-VBR Service category.
DS/PVC
example 8266>DS
DISPLAY STATES
Item (GLOBAL/PORT/PVC/REDUNDANCY/SLOT/SVC,def:GLOBAL) ? PVC
PVC 1> Mode.....................................ATMPVCR
PVC 1> Information signals......................-A---
PVC 1> Speed used (bps).........................424 k
PVC 1> VPI......................................1
PVC 1> VCI......................................34
PVC 1> PVC name.................................
3-12 Memotec Inc.

DE/PVC
example
Monitoring and Statistics
PVC 1> State & Delay............................TEST
PVC 2> Mode.....................................ATM-MULTI
PVC 2> Information signals......................-A---
PVC 2> Speed used (bps).........................424 k
PVC 2> VPI......................................12
PVC 2> VCI......................................35
PVC 2> PVC name.................................
PVC 2> State & Delay............................IDLE
PVC 3> Mode.....................................ATMPPP
PVC 3> Information signals......................-A---
PVC 3> Speed used (bps).........................212 k
PVC 3> VPI......................................13
PVC 3> VCI......................................35
PVC 3> PVC name.................................
PVC 3> State & Delay............................CALL
---- PVC #4 FRF.8 --> ATM Side ----
PVC 4> Mode.....................................FRF8
PVC 4> Information signals......................-----
PVC 4> Speed used (bps).........................212 k
PVC 4> VPI......................................15
PVC 4> VCI......................................37
PVC 4> State & Delay............................DOWN (TX VC-AIS)
---- PVC #4 FRF.8 --> FR port #101 ----
PVC 4> Information signals......................off line
PVC 4> Speed used (bps).........................56000
PVC 4> DLCI.....................................104
PVC 4> State & Delay............................DOWN
PVC 5> Mode.....................................RFC1483
PVC 5> Information signals......................-A---
PVC 5> Speed used (bps).........................212 k
PVC 5> VPI......................................18
PVC 5> VCI......................................40
PVC 5> PVC name.................................SDM-9230-REM
PVC 5> State & Delay............................OFF
Info signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn (-
)off
NP2>DE
DISPLAY ERRORS
Item (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PVC/Q922/REDUNDANCY/SLOT/
SVC/
TIMEP,def:BOOTP) ? PVC
PVC 1> Number of frames discarded (crc error)...0
PVC 1> Number of frames discarded (overrun).....0
PVC 1> Number of invalid frames discarded.......0
PVC 1> Other frames discarded...................54
PVC 2> Number of frames discarded (crc error)...0
PVC 2> Number of frames discarded (overrun).....0
Memotec Inc. 3-13

ATM Option
DPVC example
PVC 2> Number of invalid frames discarded.......0
PVC 2> Other frames discarded...................0
NP2>DPVC
DISPLAY PVC STATES
PVC TYPE (ATM/FR,def:ATM) ?
-----------------------------------ATM PVC--------------------------------------
|PVC MODE INFO. SPEED VPI VCI DESTINATION STATE & |
| SIGNALS (BPS) NAME DELAY(MS) |
--------------------------------------------------------------------------------
| 1 ATM-MULTI -A--- 212 k 10 10 9360 DATA |
| 2 ATMPVCR -A--- 212 k 0 32 TEST |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| Information signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn (-)off |
--------------------------------------------------------------------------------
Use HOME, END, UP and DOWN arrow keys to scroll. Press any other key to exit.
3-14 Memotec Inc.

3.4 Viewing Reserved Channels
DP/GLOBAL
example: with
ATM license
installed
Monitoring and Statistics
You can check the current number of reserved and configured data channels and ATM
AAL5 VCs on the SDM-9360, SDM-9380 or SDM-9585 by executing the GLOBAL
option of the Display Parameters (DP) command. Refer to “Tips for Configuring Shared
RAM Allocation” on page 2-9.
NOTE: These GLOBAL parameters are not required on the SDM-9230, which does
not have the memory constraints that the SDM-9360, SDM-9380 and SDM-
9585 have in supporting ATM.
• If you examine the current parameter values with the Display Parameters (DP)
command before you reset the unit, you will see that the current shared RAM
allocation is different from the new allocation you have proposed:
SVCATM2>DP
DISPLAY PARAMETERS
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PVC/SCHEDULE/SLOT/SVC/USER/VLAN,def:BRIDGE) ? GLOBAL
GLOBAL> Unit name (def:SVCATM2) ?
GLOBAL> Unit routing version (1-2,def:1) ?
...
GLOBAL> Delay generated by a comma (ms) (250-4000,inc:250,def:250)
?
GLOBAL> ISDN G4 Fax PCM switching enable (def:NO) ?
GLOBAL> Number of DSPs reserved for AAL1 (0-6,def:0) ?
GLOBAL> Auto save configuration delay (sec) (0-255,def:10) ?
GLOBAL> Enable VTR (Voice Traffic Routing) (def:NO) ?
GLOBAL> Enable Domain Dialing (def:YES) ?
GLOBAL> Enable hunt forwarding (def:YES) ?
GLOBAL> Enable user access logging (def:NO) ?
GLOBAL> Exclusive access to console (def:DISABLE) ?
GLOBAL> Number of data channels reserved (0-32,def:32) ?
GLOBAL> ATM AAL5 VC mode includes ATMPVCR, ATMPPP, RFC1483 and
FRF.8
Number of ATM AAL5 VCs reserved (0-31,def:15) ? 16
----- CURRENT SHARED RAM ALLOCATION -----
Number of reserved data channels: 32
Number of reserved ATM AAL5 VCs: 16
Number of configured data channels: 0
Number of configured ATM AAL5 VCs: 1
Total memory available: 1076784 bytes,1051K
Allocated memory for data channels (32*23252): 744064 bytes, 726K
Allocated memory for ATM AAL5 VCs (16*20162): 322592 bytes, 315K
Total allocated memory: 1066656 bytes,1041K
Unallocated memory: 10128 bytes, 9K
Memotec Inc. 3-15

ATM Option
WARNING: To apply the new configuration the unit must be reset
To do this, execute the Reset Unit (RU) command.
NOTE: Ensure that the Digital port clock source parameter in the Global menu
(SETUP/GLOBAL) is set to the appropriate value for your application:
• INTERNAL to use the internal reference clock, or
• 1 to 4 to use the clock received from the network via the digital card installed in
that slot number.
If the clocking is not configured correctly a high number of Cell Sync errors will occur on
the ATM channel. Execute the Display Errors command (DE/SLOT) and examine the No.
of Cell Sync Lost statistic, as shown in the example on page 18.
3-16 Memotec Inc.

3.5 Status of ATM Channels
DC/SLOT
example
Monitoring and Statistics
The status of ATM channels can be determined from the following NetPerformer statistics
commands:
• Display Counters (DC), SLOT option
• Display States (DS), SLOT option
• Display Errors (DE), SLOT option
8266>DC
DISPLAY COUNTERS
Item (BOOTP/CHANNEL/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/
REDUNDANCY/
SLOT/SNMP/SVC/TIMEP,def:BOOTP) ? SLOT
Counters (MEAN/PEAK,def:MEAN) ?
SLOT 1>
PORT 101> Transmitter rate......................0 % (M)
PORT 101> Receiver rate.........................0 % (M)
PORT 101> Number of cells transmitted...........3345
PORT 101> Number of cells received..............2559
PORT 101> OAM F4 VP-AIS cells received..........0
PORT 101> OAM F4 VP-RDI cells received..........0
PORT 101> OAM F4 VP-RDI cells transmitted.......0
PORT 101> OAM F5 VC-AIS cells received..........377
PORT 101> OAM F5 VC-AIS cells transmitted.......2157
PORT 101> OAM F5 VC-RDI cells received..........301
PORT 101> OAM F5 VC-RDI cells transmitted.......563
PORT 101> OAM F4 VP Loopback received...........0
PORT 101> OAM F4 VP Loopback transmitted........0
PORT 101> OAM F5 VC Loopback received...........0
PORT 101> OAM F5 VC Loopback transmitted........0
DS/SLOT
example 8266>DS
DISPLAY STATES
Item (GLOBAL/PORT/PVC/REDUNDANCY/SLOT/SVC,def:GLOBAL) ? SLOT
SLOT> Slot number (1/ALL,def:1) ?
SLOT 1>
PORT 100> State.................................IN SYNC
PORT 100> Interface.............................T1-TE
PORT 101> Protocol..............................ATM
PORT 101> Speed used (bps)......................1536k
PORT 101> Cell sync state.......................IN SYNC
PORT 101> ILMI state............................DOWN
PORT 101> ATM signaling state...................DOWN
PORT 101> ILMI registered
prefix................00000000000000000000000000
Modem signals: d(S)r d(T)r (D)cd (R)ts (C)ts r(I) (-)off
Memotec Inc. 3-17

ATM Option
DE/SLOT
example
8266>DE
DISPLAY ERRORS
Item (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PVC/Q922/REDUNDANCY/SLOT/
SVC/
TIMEP,def:BOOTP) ? SLOT
SLOT> Slot number (1/ALL,def:1) ?
SLOT 1>
PORT 100> Number of errored seconds.............1
PORT 100> Number of severely errored seconds....0
PORT 100> Number of severely errored frames.....0
PORT 100> Number of unavailable seconds.........0
PORT 100> Number of controlled slip seconds.....624
PORT 100> Number of path code violations........0
PORT 100> Number of line errored seconds........1
PORT 100> Number of bursty errored seconds......0
PORT 100> Number of degraded minutes............0
PORT 100> Number of line code violations........16
PORT 100> Number of CRC errors..................0
PORT 100> Number of frame length errors.........0
PORT 100> Number of abort sequences.............0
PORT 100> Number of non-aligned octets..........0
PORT 100> Number of HDLC framing errors.........0
PORT 100> Number of returned rx buffers.........0
PORT 100> Number of channel restarts............0
PORT 101> No. of frames discarded (overrun).....0
PORT 101> No. of frames discarded (bad).........0
PORT 101> No. of frames discarded (CRC error)...1539
PORT 101> No. of raw cells discarded............1485
PORT 101> No. of cell sync lost.................76496
PORT 101> Invalid VPI.VCI cells received........3
PORT 101> Unsupported OAM cells received........0
Bad flags: U:Bad LENGTH Q:Overflow F:Flush S:Overrun B:Bad CRC
A:Abort
3-18 Memotec Inc.

SE/SLOT/CHANNEL Configuration
Parameters
4
NOTE: The Protocol, Timeslot and Number of consecutive timeslots parameters are
common to all digital channels. For details, refer to the appendix SE/SLOT/
CHANNEL Configuration Parameters in the Digital Data fascicle of this
document series.
Memotec Inc. 4-1

ATM Option
4.1 Idle cell
Determines the format used for idle cells. Select ATM-UNI for the User-to-Network
Interface format. Select ITU-T for the ITU-T format. Refer to “User to Network Interface
(UNI)” on page 1-7.
4.2 Idle cell payload
Console SNMP Text-based Config
Idle cell ifwanIdleCell [ifwan#] IdleCell
Values: ATM-UNI, ITU-T
Default: ITU-T
Console SNMP Text-based Config
Idle cell payload ifwanIdleCellPayload [ifwan#] IdleCellPayload
Determines the payload content for idle cells on the ATM channel.
Values: 00000000 - FFFFFFFF
Default: 6A6A6A6A
4.3 HEC coset function
Console SNMP Text-based Config
HEC coset function ifwanHECCosetFunction [ifwan#] HECCosetFunction
Enables or disables the Header Error Check (HEC) coset function, which is required for
some ATM switches.
• When you select ENABLE (the default value), the NetPerformer applies the HEC
coset to all cells that are transmitted or received across this channel
• When you select DISABLE, the HEC coset rules are not applied.
Values: DISABLE, ENABLE
Default: ENABLE
4-2 Memotec Inc.

4.4 Scrambling function
4.5 UNI Version
SE/SLOT/CHANNEL Configuration Parameters
Console SNMP Text-based Config
Scrambling function ifwanScramblingFunction [ifwan#] ScramblingFunction
Enables or disables cell scrambling, which permits randomizing the cell payload. Cell
scrambling can be used to avoid a continuous stream of invariable bit patterns, which can
improve the efficiency of cell delineation.
• When you select ENABLE the NetPerformer applies cell scrambling before transmission,
and descrambling on the received traffic stream.
Cell scrambling must be enabled on both sides of the connection.
• When you select DISABLE (the default value), cell scrambling is not applied.
Values: DISABLE, ENABLE
Default: DISABLE
Console SNMP Text-based Config
UNI Version ifwanAtmUniVersion [ifwan#] AtmUniVersion
Select the value that matches the UNI version used by the ATM switch:
• NONE: UNI is not used. The ILMI and signaling VCs are not established.
• 4.0: UNI 4.0
• 3.1: UNI 3.1
• 3.0: UNI 3.0
NOTE: Auto configuration of this parameter is not supported.
Refer to “User to Network Interface (UNI)” on page 1-7 for further information.
Values: NONE, 4.0, 3.1, 3.0
Default: 4.0
Memotec Inc. 4-3

ATM Option
4.6 UNI Type
Console SNMP Text-based Config
UNI Type ifwanAtmUniType [ifwan#] AtmUniType
Indicates the type of network that this digital interface is connected to:
• PRIVATE: The interface is connected to a private network. This implies that
AESA address format will be used in the SVC configuration.
• PUBLIC: The interface is connected to a public network. This implies that E.164
address format will be used in the SVC configuration.
NOTE: No address registration is done if UNI Type is PUBLIC.
Refer to “ATM Addressing” on page 1-9 for further information.
Values: PRIVATE, PUBLIC
Default: PRIVATE
4.7 ATM Signaling Channel VPI
Console SNMP Text-based Config
ATM Signaling Channel
VPI
ifwanAtmSigVpi [ifwan#] AtmSigVpi
Determines the address of the Virtual Path Identifier (VPI) for the ATM signaling channel.
Refer to “UNI Signaling” on page 1-7.
NOTE: The zero (0) default value selects VPI 0.
Values: SDM-9360, SDM-9380, 0 - 63
SDM-9585:
SDM-9230: 0 - 255
Default: 0
4-4 Memotec Inc.

4.8 ATM Signaling Channel VCI
SE/SLOT/CHANNEL Configuration Parameters
Determines the address of the Virtual Channel Identifier (VCI) for the ATM signaling
channel.
4.9 ILMI Channel VPI
Console SNMP Text-based Config
ATM Signaling Channel
VCI
Values: SDM-9360, SDM-9380, 0 - 65534
SDM-9585:
SDM-9230: 0 - 1023
Default: 0
ifwanAtmSigVci [ifwan#] AtmSigVci
Console SNMP Text-based Config
ILMI Channel VPI ifwanAtmIlmiVpi [ifwan#] AtmIlmiVpi
Determines the address of the VPI for the Integrated Local Management Interface (ILMI)
channel. Refer to “Integrated Local Management Interface (ILMI)” on page 1-8.
NOTE: The zero (0) default value selects VPI 0.
Values: SDM-9360, SDM-9380, 0 - 63
SDM-9585:
SDM-9230: 0 - 255
Default: 0
Memotec Inc. 4-5

ATM Option
4.10 ILMI Channel VCI
Console SNMP Text-based Config
ILMI Channel VCI ifwanAtmIlmiVci [ifwan#] AtmIlmiVci
Determines the address of the Virtual Channel Identifier (VCI) for the ILMI channel.
Values: SDM-9360, SDM-9380, SDM-9585: 0 - 65534
SDM-9230: 0 - 1023
Default: 0
NOTE: For a NetPerformer unit that supports the ATM option, voice channels have an
additional parameter in the SETUP/SLOT/CHANNEL listing: Accept Incoming
ATM AAL1 Calls.
4.11 Accept Incoming ATM AAL1 Calls
Console SNMP Text-based Config
Accept Incoming ATM
AAL1 Calls
ifvceIncomingAtmAAL1calls
[ifwan#]
IncomingAtmAAL1calls
Set this parameter to YES to permit transport of incoming AAL1 calls on the non-ATM
channel.
Values: NO, YES
Default: YES
4-6 Memotec Inc.

SE/PVC Configuration Parameters
5
Memotec Inc. 5-1

ATM Option
5.1 PVC number
5.2 Mode
Console SNMP Text-based Config
PVC number pvcEntry, pvcIndex [pvc#]
Enter the number of the PVC you want to configure on the console command line. For
SNMP, select the pvcEntry table and look under the pvcIndex for the desired PVC.
Once you select a PVC, the PVC number is displayed thereafter at the beginning of each
line from the console.
Values: 1 - 300
Default: 1
Console SNMP Text-based Config
Mode atmpvcMode [atmpvc#] Mode
Selects the type of PVC to be used for this ATM logical connection.
• ATMPVCR: for PowerCell over ATM AAL5, an integrated traffic transport
method (see “PowerCell in the ATM Network” on page 1-16 for background
information)
• AAL1: for ATM AAL1, a voice traffic transport method supported on the NetPerformer
SDM-9360, SDM-9380 and SDM-9585 only (see “AAL1 Circuit Emulation
Services (CES)” on page 1-16)
• FRF.8: for FRF.8, a Service Interworking method ideal for Frame Relay traffic
(see “Frame Relay/ATM Service Interworking (FRF.8)” on page 1-18)
• RFC1483: for multiprotocol over ATM AAL5 using RFC-1483, a data traffic
transport method (see “LLC Encapsulation (RFC-1483)” on page 1-22)
• ATMPPP: for PPP over ATM AAL5 using RFC-2364, a data traffic transport
method ideal for Internet access (see “PPP Over AAL5” on page 1-23)
• ATM-MULTIPLEX: for multiplexing ATM traffic over PowerCell links (see
“ATM Multiplex Connections” on page 1-24). This mode is ideal for transporting
traffic from any ATM Adaptation Layer. It is also the only PVC mode that can
support AAL2 and AAL3/4 traffic.
NOTE: The other values listed are for non-ATM applications.
5-2 Memotec Inc.

SE/PVC Configuration Parameters
Values: SDM-9360, SDM-9380, OFF, ATMPVCR, ATMPPP, BROADCAST,
SDM-9585:
FRF.8, MULTIPLEX, PVCR, RFC1483,
RFC1490, TRANSP
SDM-9230: OFF, ATMPVCR, ATM-MULTIPLEX,
ATMPPP, BROADCAST, FRF.8, MULTI-
PLEX, PVCR, RFC1483, RFC1490,
TRANSP
Default: PVCs 1 - 8: PVCR
PVCs 9 and higher: OFF
Memotec Inc. 5-3

ATM Option
5.3 ATMPVCR Mode
5.3.1 VPI address
5.3.2 VCI address
NOTE: Many of the parameters detailed in this section are also listed when the PVC
is configured to another mode.
When certain parameters, such as IP RIP, OSPF, IP multicast active and NAT
enable, are enabled or set to specific values, additional parameters requiring
configuration appear on the console. Examples and descriptions of these
parameters are provided under the parameter that governs them.
Console SNMP Text-based Config
VPI address atmpvcVPI [atmpvc#] Vpi
Determines the address of the Virtual Path Identifier (VPI). A zero value (0) leaves this
address undefined.
Values: SDM-9360, SDM-9380, 0 - 255
SDM-9585:
SDM-9230: 0 - 63
Default: 0
Console SNMP Text-based Config
VCI address atmpvcVci [atmpvc#] Vci
Determines the address of the Virtual Channel Identifier (VCI).
• A zero value (0) leaves the VCI address undefined. If the VPI is also 0, the
address is invalid.
• The values 0 to 32 are normally reserved, but can be used if desired.
• VPI 0/VCI 3 and VPI 0/VCI 4 are used for Raw Cell traffic.
Two PVCs cannot have the same VPI/VCI combination. If you try to enter an address that
is already used, the NetPerformer displays a warning specifying which PVC already has
this address.
NOTE: A maximum of 31 VCs can be configured on the SDM-9360, SDM-9380 or
SDM-9585.
5-4 Memotec Inc.

5.3.3 Service category
Values: SDM-9360, SDM-9380, 0 - 65534
SDM-9585:
SDM-9230: 0 - 1023
Default: 0
SE/PVC Configuration Parameters
Console SNMP Text-based Config
Service category atmpvcServiceCategory [atmpvc#] ServiceCategory
On the SDM-9230 only:
Set this parameter to the service category required by the ATM switch. To select the
correct category for your PVC connection you can refer to the ATM switch configuration,
or seek the advice of your ATM service provider.
Each service category is based on a combination of cell rate pacing, Quality of Service
(QoS) and traffic priority characteristics:
• CBR: Constant Bit Rate. Refer to “Constant Bit Rate (CBR)” on page 1-11 for a
description of the characteristics of this service category
• UBR: Unspecified Bit Rate. Refer to “Unspecified Bit Rate (UBR)” on page 1-12
• RT-VBR: Real-Time Variable Bit Rate. Refer to “Real-time Variable Bit Rate
(RT-VBR)” on page 1-12
• NRT-VBR: Non-Real-Time Variable Bit Rate. Refer to “Non-real-time Variable
Bit Rate (NRT-VBR)” on page 1-12.
The Service Categories are available for all PVC types except ATM-MULTIPLEX, in which
the NetPerformer unit is considered part of the ATM network side.
Each end of the connection can be configured differently as to Service category and the
various cell rates defined. Each PVC can also be configured differently, even on the same
NetPerformer unit.
NOTE: On the SDM-9360, SDM-9380 and SDM-9585:
• An AAL5 PVC is always set to UBR
• An AAL1 PVC is always set to CBR.
Values: CBR, RT-VBR, NRT-VBR, UBR
Default: UBR
Memotec Inc. 5-5

ATM Option
5.3.4 Peak cell rate
Set this parameter to the maximum cell rate (in cells per second) that is required by the
application. The NetPerformer calculates the:
• Payload Information Rate: the cell rate multiplied by the cell size, excluding
ATM cell headers,
• Total Information Rate: the cell rate multiplied by the cell size, including ATM
cell headers.
• These rates are displayed in bits per second after the Peak Cell Rate parameter.
NOTE: If 30 timeslots are used on the E1 ATM channel, the SAR driver will limit the
peak cell rate to 4528 cells/sec, even if this parameter is set to a higher value.
For variable bit-rate service categories (RT-VBR and NRT-VBR) the Peak cell rate is
the maximum rate of transfer that can occur during short bursts of traffic. The
parameter is in bps, and should be set in light of the Maximum Burst Size that could
occur on the VCs.
After the Peak cell rate parameter, the Payload information rate and Total information
rate are displayed at the console. These are read-only parameters that are provided for
information purposes.
5.3.5 Sustainable cell rate (SCR)
Console SNMP Text-based Config
Peak cell rate atmpvcPeakCellRate [atmpvc#] PeakCellRate
Values: T1 connection: 0 - 3622 cells/sec
E1 connection: 0 - 4679 cells/sec
Default: 1000
Console SNMP Text-based Config
Sustainable cell rate
(SCR)
atmpvcSustainableCell-
Rate
[atmpvc#] Sustainable-
CellRate
On the SDM-9230 only, when the Service category parameter is set to RT-VBR
or NRT-VBR:
Set this parameter to the Sustainable Cell Rate in cells per second. This is the sustained
rate of transfer, or the average bandwidth required by the VC on this PVC.
For further information and configuration examples, refer to “Configuring the Cell Rate
Parameters for Variable Bit Rate Service Categories” on page 2-20.
5-6 Memotec Inc.

5.3.6 Maximum burst size (MBS) in cells
5.3.7 Remote unit name
Values: T1 connection: 0 - 3622 cells/sec
E1 connection: 0 - 4679 cells/sec
Default: 500
SE/PVC Configuration Parameters
Console SNMP Text-based Config
Maximum burst size
(MBS) in cells
atmpvcMaximumBurst-
Size
[atmpvc#] Maximum-
BurstSize
On the SDM-9230 only, when the Service category parameter is set to RT-VBR
or NRT-VBR:
Set this parameter to the Maximum Burst Size (MBS) in cells. This parameter determines
the amount of time that the connection can maintain the maximum rate of transfer
permitted (the value of the Peak cell rate parameter). Use it to accommodate short bursts
of traffic.
The Maximum burst size (MBS) in cells parameter should be set to the number of cells that
typically occur in a traffic burst. In general, you can set it to the value of the Peak cell rate
parameter, and fine tune if required.
NOTE: The MBS cannot handle a transmission rate that is above the SCR for long
periods of time.
For further information and configuration examples, refer to “Configuring the Cell Rate
Parameters for Variable Bit Rate Service Categories” on page 2-20.
Values: 1-65535
Default: 1000
Console SNMP Text-based Config
Remote unit name atmpvcRemoteUnit [atmpvc#] RemoteUnit
The unit to which data from this PVC should be directed. The unit name is defined on the
remote unit using the SETUP/GLOBAL menu, described in the chapter Global Functions
in the Quick Configuration fascicle of this document series. A unit name must be defined
for each NetPerformer that will be participating in the network.
Values: Maximum 16-character string, determined by remote NetPerformer
setup
Default: none
Memotec Inc. 5-7

ATM Option
5.3.8 Timeout (msec)
The wait for ACK timeout, in milliseconds, before retransmitting a packet on the PVC.
This parameter is required only when at least one PU with a LINKS connection is
configured, for example, LLC-LINKS.
5.3.9 Number of retransmission retries
5.3.10 Compression
5.3.11 IP address
Console SNMP Text-based Config
Timeout (msec) atmpvcTimeout-ms [atmpvc#] Timeout-ms
Values: 1000 - 30000
Default: 1000
Console SNMP Text-based Config
Number of retransmission
retries
Maximum number of successive retries before the PVC connection is declared down.
Values: 1 - 1000
Default: 100
atmpvcRetry [atmpvc#] Retry
Console SNMP Text-based Config
Compression pvcCompression [pvc#] Compression
Use compression on the PVCR PVC connection to the remote NetPerformer. With
compression, the available bandwidth is used more efficiently. When compression is not
used, higher speeds can be obtained on the connection (up to 2 Mbps).
Values: NO, YES
Default: YES
Console SNMP Text-based Config
IP address atmpvcIpAddress [atmpvc#] IpAddress
IP address of the local PVC. This address is a 4-byte value in dotted decimal
representation, with a maximum value of 255 for each byte, for example 128.128.128.122.
When this parameter is set to 000.000.000.000, no IP address is defined for this PVC. In
this case the NetPerformer will use the default IP address defined with the global Default
IP Address parameter. For details, refer to the chapter Global Functions in the Quick
Configuration fascicle of this document series.
5-8 Memotec Inc.

SE/PVC Configuration Parameters
NOTE: If you configure the IP Address parameter, the value of the global Default IP
Address parameter is ignored for this PVC.
5.3.12 Subnet mask (number of bits)
5.3.13 NAT enable
Values: 000.000.000.000 - 255.255.255.255
Default: 000.000.000.000
Console SNMP Text-based Config
Subnet mask (number of
bits)
atmpvcSubnetMask [atmpvc#] SubnetMask
The subnet mask associated with the IP address for this PVC. The Subnet mask identifies
which bits of the IP address correspond to the physical network, and which bits
correspond to host identifiers. For example, in IP address 255.255.000.000 all network
bits are set to 1 and all host bits are set to 0.
To change the value of the subnet mask using the console, enter the number of bits of that
mask.
• For example, select 17 bits to define the mask 255.255.128.000; select 23 bits to
define 255.255.254.000
• When you enter the number of bits at the console, the NetPerformer provides the
resulting mask in dotted decimal notation to the right of the bits value
• For the SNMP interface, you cannot change the number of bits. You must enter
the value of the subnet mask directly.
• If the value of the subnet mask is not valid for the configured IP address, it will
be rejected by the NetPerformer and the IP address will be invalid.
NOTE: As of V10.2 the NetPerformer supports super-netting as well as subnetting. To
accommodate this the subnet mask of any IP address can now be set to any
whole integer value from 0 to 32.
Values: 0 - 32 (equivalent to 000.000.000.000 - 255.255.255.255)
Default: 0 (equivalent to 000.000.000.000)
Console SNMP Text-based Config
NAT enable atmpvcNatEnable [atmpvc#] NatEnable
Memotec Inc. 5-9

ATM Option
5.3.14 NAT rule
5.3.15 NAT side
Enables (YES) or disables (NO) Network Address Translation (NAT) on this PVC
connection.
Values: NO, YES
Default: NO
When the NAT enable parameter is set to YES, the following additional parameters are
also available:
PVC 1> NAT enable (def:NO) ? YES
PVC 1> NAT rule (1-10) (def:) ?
PVC 1> NAT side (def:INTERNAL) ?
Console SNMP Text-based Config
NAT rule atmpvcNatRule [atmpvc#] NatRule
Selects the NAT rule or rules to be used to translate address information for traffic to and
from this PVC connection. A rule defines the correspondence between internal IP
addresses and external, globally unique NAT IP addresses. Select multiple rules by
entering a comma between the rule numbers, for example: 1,3,4.
Define all NAT rules with the SETUP/IP/NAT submenu. For details, refer to the chapter
Network Address Translation (NAT) in the LAN Connection and IP Networks
fascicle of this document series.
Values: 1 - 10
Default: none
Console SNMP Text-based Config
NAT side atmpvcNatSide [atmpvc#] NatSide
Determines which address realm this PVC connection is associated with, and where NAT
is carried out.
• INTERNAL: NAT is carried out on the internal side of the network. Select this
value if the PVC connection is to equipment on the local side (the private network).
• EXTERNAL: NAT is carried out on the external side of the network. Select this
value if the PVC connection is to equipment on the remote side.
Values: INTERNAL, EXTERNAL
Default: INTERNAL
5-10 Memotec Inc.

5.3.16 IP RIP
SE/PVC Configuration Parameters
Console SNMP Text-based Config
IP RIP atmpvcIpRip [atmpvc#] IpRip
Enables or disables the Routing Information Protocol (RIP) on the PVC connection. Three
settings are available to enable IP RIP:
• V1: The PVC uses RIP Version 1. With this version the subnet mask for an IP
address in a routing table entry is determined using the mask of the port on which
the frame was received.
• V2 BROADCAST: The PVC uses RIP Version 2 in Broadcast mode. In Version
2 a subnet mask is transmitted for each address contained in the RIP frame. In
Broadcast mode each RIP V2 frame is sent with IP address 255.255.255.255,
which permits routers running RIP Version 1 to receive and analyze those frames.
• V2 MULTICAST: The PVC uses RIP Version 2 in Multicast mode. In this mode
each RIP V2 frame is sent with IP address 224.000.000.009, which prevents routers
running RIP Version 1 from receiving those frames.
For details on the differences between IP RIP routing using RIP Version 1 and
RIP Version 2, consult the Bridge Router Functions chapter of the LAN Connection
and IP Networks fascicle of this document series.
• Set the IP RIP parameter to DISABLE to prevent the NetPerformer from transmitting
or receiving RIP frames on this PVC. The NetPerformer will discard all
RIP frames received.
NOTE: If you disable IP RIP on the NetPerformer, but require IP routing to a particular
destination (for management under SNMP, for example) you can configure
a static IP address using the IP Static menu, described in the LAN Connection
and IP Networks fascicle of this document series.
Values: DISABLE, V1, V2 BROADCAST, V2 MULTICAST
Default: V1
When the V2 BROADCAST or V2 MULTICAST value is selected for the IP RIP parameter,
additional IP RIP parameters are also available, as shown in this example:
PVC 1> IP RIP (def:V1) ? V2 BROADCAST
PVC 1> IP RIP TX/RX (def:DUPLEX) ?
PVC 1> IP RIP Authentication (def:NONE) ?
PVC 1> IP RIP Password (def:) ?
Memotec Inc. 5-11

ATM Option
5.3.17 IP RIP TX/RX
This parameter sets the directionality of the RIP version used on the PVC connection.
Configure the PVC for two-way IP RIP routing by setting this parameter to DUPLEX (the
default value). The NetPerformer can generate IP routing tables, and both receive and
transmit RIP frames on this PVC.
You can also enable IP RIP in a single direction. Select the TX ONLY value to allow the
NetPerformer to transmit RIP frames only. The NetPerformer will discard all RIP frames
received at the PVC. Select RX ONLY to allow the NetPerformer to receive RIP frames
only. In this case, the PVC cannot transmit a RIP frame.
5.3.18 IP RIP authentication type
5.3.19 IP RIP password
Console SNMP Text-based Config
IP RIP TX/RX atmpvcIpRipTxRx [atmpvc#] IpRipTxRx
Values: DUPLEX, TX ONLY, RX ONLY
Default: DUPLEX
Console SNMP Text-based Config
IP RIP authentication
type
For IP RIP Version 2 only.
This parameter enables or disables password authentication for the interface. Select
SIMPLE to have the password included in all RIP frames sent from this PVC. Frames
containing authentication that are received at this PVC will be accepted only if the
password is valid. The password is defined using the IP RIP Password parameter,
described below.
Values: NONE, SIMPLE
Default: NONE
atmpvcIpRipAuthType [atmpvc#] IpRipAuthType
Console SNMP Text-based Config
IP RIP password atmpvcIpRipPassword [atmpvc#] IpRipPassword
For IP RIP Version 2 only.
This parameter defines the password to be used on the interface. The password allows the
authentication procedure to generate and/or verify the authentication field in the RIP
header.
NOTE: The value of the IP RIP Password parameter must be the same for each inter-
5-12 Memotec Inc.

5.3.20 OSPF
face on both sides of the network.
Values: alphanumeric string, maximum 8 characters
Default: none
SE/PVC Configuration Parameters
Console SNMP Text-based Config
OSPF atmpvcOspfEnable [atmpvc#] OspfEnable
Enables or disables the OSPF protocol on the interface. By default, OSPF is disabled on
all NetPerformer Frame Relay connections. Set this parameter to ENABLE to enable
OSPF. Each slot, port and PVC must be enabled separately. If OSPF is enabled, the
interface will be advertised as an internal route to an area of the Autonomous System
(AS). To disable OSPF, set this parameter to DISABLE.
NOTE: On the console, the other OSPF interface parameters for this PVC will be displayed
only if OSPF is enabled. For complete information on these parameters,
turn to the chapter OSPF Network Support in the LAN Connection
and IP Networks fascicle of this document series.
Values: DISABLE, ENABLE
Default: DISABLE
NOTE: When OSPF is enabled, additional OSPF parameters appear on the console
and must be defined:
PVC 1> OSPF (def:DISABLE) ? ENABLE
PVC 1> OSPF Area ID (def:000.000.000.000) ?
PVC 1> OSPF Router priority (0-255,def:1) ?
PVC 1> OSPF Transit delay (1-360,def:1) ?
PVC 1> OSPF Retransmit interval (1-360,def:5) ?
PVC 1> OSPF Hello interval (1-360,def:10) ?
PVC 1> OSPF Dead interval (1-2000,def:40) ?
PVC 1> OSPF Password (def:) ?
PVC 1> OSPF Metric cost (1-65534,def:10) ?
Memotec Inc. 5-13

ATM Option
5.3.21 OSPF Area ID
5.3.22 OSPF Transit delay
Identifies the area to which this PVC belongs. This parameter requires a 4-byte value in
dotted decimal representation, with a maximum value of 255 for each byte. All routing
protocol packets originating from the PVC are labelled with this Area ID.
The value of this parameter must be the same as the Area ID of the area to which the
attached network belongs. If you want to define subnetted networks as separate areas, you
can use the IP network number as the Area ID.
NOTE: Area ID 000.000.000.000 indicates that this PVC is included in the OSPF
backbone.
The estimated number of seconds required to transmit a Link State Update packet on this
PVC. Link state advertisements contained in the Link State Update packet will have their
age incremented by this amount before transmission.
When configuring the Transit Delay, take into account the transmission and propagation
delays that occur on this port/PVC. For example, you should increase the value of the
Transit Delay for low-speed serial connections. The default value, 1 second, is appropriate
for a LAN connection.
5.3.23 OSPF Retransmit interval
Console SNMP Text-based Config
OSPF Area ID atmpvcOspfAreaId [atmpvc#] OspfAreaId
Values: 000.000.000.000 - 255.255.255.255
Default: 000.000.000.000
Console SNMP Text-based Config
OSPF Transit delay atmpvcOspfTransitDelay [atmpvc#] OspfTransitDelay
Values: 1 - 360
Default: 1
Console SNMP Text-based Config
OSPF Retransmit interval atmpvcOspfRetransmit-
Int
[atmpvc#] OspfRetransmitInt
The number of seconds that elapse between retransmissions of link state advertisements.
This parameter is used for adjacencies that belong to this PVC, and for retransmissions of
5-14 Memotec Inc.

5.3.24 OSPF Hello interval
5.3.25 OSPF Dead interval
5.3.26 OSPF Password
SE/PVC Configuration Parameters
OSPF Database Description and Link State Request packets.
Set this parameter to a value that is higher than the expected round-trip delay between any
two routers on the network attached to this port/PVC. Otherwise, needless retransmissions
will occur. The default value, 5 seconds, is appropriate for a LAN connection. Low-speed
connections require a higher value.
Values: 1 - 360
Default: 5
Console SNMP Text-based Config
OSPF Hello interval atmpvcOspfHelloInt [atmpvc#] OspfHelloInt
The length of time, in seconds, between the Hello Packets that the NetPerformer sends on
this PVC. The value of the Hello Interval parameter is advertised in Hello Packets sent out
from this PVC, and must be the same on all other routers having a connection with the
network attached to this PVC.
If you set the Hello Interval to a short length of time, changes to the OSPF topological
database will be detected more quickly. However, a short Hello Interval creates more
OSPF routing protocol traffic. The default value, 10 seconds, is appropriate for a LAN
connection, whereas a PVC may require a Hello Interval of 30 seconds.
Values: 1 - 360
Default: 10
Console SNMP Text-based Config
OSPF Dead interval atmpvcOspfDeadInt [atmpvc#] OspfDeadInt
The length of time, in seconds, before neighboring routers declare a router down when
they stop hearing its Hello Packets. The value of the Dead Interval parameter is advertised
in Hello Packets sent out from this PVC, and must be the same on all other routers having
a connection with the network attached to this PVC.
Set the Dead Interval to a multiple of the Hello Interval (described above).
Values: 1 - 2000
Default: 40
Console SNMP Text-based Config
OSPF Password atmpvcOspfPassword [atmpvc#] OspfPassword
Memotec Inc. 5-15

ATM Option
5.3.27 OSPF Metric cost
5.3.28 IP multicast active
An 8-character value that will appear in the authentication field of all OSPF packets sent
or received on this PVC. The Password allows the authentication procedure to generate
and/or verify the Authentication field in the OSPF header. If the Authentication Type (an
OSPF Area parameter) specifies a simple password, the Authentication Key is built from
the Password parameter as a 64-bit password. The NetPerformer inserts this key directly
into the OSPF header when creating routing protocol packets.
The value of the Password parameter must be the same as that configured on all other
routers having a connection with the network attached to this PVC. In other words, all
routers in the same area must have the same password (or no authentication at all). Since
the Authentication Key is configured separately for each PVC, there can be a separate
password for each network in the AS.
Values: Maximum 8-character ASCII string
Default: none
Console SNMP Text-based Config
OSPF Metric cost atmpvcOspfMetricCost [atmpvc#] OspfMetric-
Cost
The cost of sending a packet on this PVC, expressed in the link state metric. The value of
this parameter is determined as:
100,000,000 ÷ interface speed
The metric cost is advertised in the router links advertisement as the link cost for this
PVC.
Values: 1 - 65534
Default: 10
Console SNMP Text-based Config
IP multicast active atmpvcIpMulticastActive [atmpvc#] IpMulticastActive
Enable (YES) or disable (NO) IP Multicast on this PVC connection. When IP multicast
active is enabled, the PVC connection becomes an IP Multicast client. All link ports
(PVCR) and PVCs (PVCR and RFC1490) that will participate in the multicast route must
be defined in this way.
Values: NO, YES
Default: NO
5-16 Memotec Inc.

5.3.29 IP multicast protocol
5.3.30 IPX RIP
SE/PVC Configuration Parameters
NOTE: You must also configure the IP Multicast parameters on the LAN connection,
including the IP addresses of all multicast groups that will be recognized by
the LAN port. For details, refer to the LAN connection and IP Networks fascicle
of this document series.
Console SNMP Text-based Config
IP multicast protocol atmpvcIpMulticast-Protocol
Selects the IP multicast protocol.
• PIMDM: Protocol Independent Multicast - Dense Mode. This routing algorithm
was designed for multicast groups that are densely distributed across the network.
• NONE: No IP multicast protocol is used.
Values: NONE, PIMDM
Default: NONE
[atmpvc#] IpMulticast-
Protocol
Console SNMP Text-based Config
IPX RIP atmpvcIpxRip [atmpvc#] IpxRip
Enables or disables RIP for Internetwork Packet Exchange (IPX) frames. Configure the
PVC for IPX RIP routing by setting this parameter to ENABLE. When the IPX RIP
parameter is enabled, the NetPerformer can generate IPX routing tables, and both receive
and transmit IPX RIP frames on this PVC. When IPX RIP is disabled the NetPerformer
cannot transmit an IPX RIP frame, and discards all IPX RIP frames received.
NOTE: If you set this parameter to ENABLE, you must also configure the IPX Network
Number parameter, described below.
Values: DISABLE, ENABLE
Default: DISABLE
Memotec Inc. 5-17

ATM Option
5.3.31 IPX SAP
5.3.32 IPX network number
5.3.33 Filter
Console SNMP Text-based Config
IPX SAP atmpvcIpxSap [atmpvc#] IpxSap
Enables or disables the Service Advertising Protocol (SAP) for IPX frames. IPX SAP
frames are exchanged between routers to indicate the nature and location of services
available on a Novell network. Configure the PVC for IPX SAP routing by setting this
parameter to ENABLE. When the IPX SAP parameter is disabled the NetPerformer cannot
transmit an IPX SAP frame, and discards all IPX SAP frames received.
IPX
Values: DISABLE, ENABLE
Default: DISABLE
Console SNMP Text-based Config
IPX network number atmpvcIpxNetNum [atmpvc#] IpxNetNum
The network number of the IPX node that is connected to the PVC. This number is a 4byte
value in hexadecimal representation. The NetPerformer uses IPX network numbers to
forward frames to their final destination.
When the IPX network number is set to 00000000, the local node is unknown. To allow
the NetPerformer to forward IPX frames to their final destination, an internal IPX network
number must be defined, using the Setup IPX menu.
Values: 00000000 - FFFFFFFF
Default: 00000000
Console SNMP Text-based Config
Filter atmpvcFilter [atmpvc#] Filter
PVC traffic filters can be fine tuned on a port-by-port basis. The Filter parameter lets you
select which filters you would like to apply to this PVC connection.
• Enter ALL to apply all traffic filters that have been defined with the SETUP/FIL-
TER command.
Use DP/FILTER to view the current listing. For details on defining and using traffic
filters, refer to the Quality of Service (QoS) fascicle of this document
series.
• Enter NONE to disable filtering on this PVC connection.
• Enter a specific filter number (from 1 to 32) or a set of filter numbers to select a
subset of the filters that have been defined for this NetPerformer unit.
5-18 Memotec Inc.

5.3.34 Broadcast group
SE/PVC Configuration Parameters
When selecting more than one filter, separate each filter number with commas,
for example:
PVC 1> Filter (def:ALL) ? 2,21,10
The filters you select are applied to the port traffic in the order you specify for
this parameter. In the above example, Filter 21 will be applied before Filter 10.
Values: An automatically generated list of filter numbers
Default: ALL
Console SNMP Text-based Config
Broadcast group atmpvcBroadcastGroup [atmpvc#] Broadcast-
Group
This parameter determines whether the PVCR PVC is a member of a broadcast group. A
broadcast group must be defined for voice broadcasting to multiple remote sites. Refer to
the Analog Voice fascicle of this document series.
NOTE: The Broadcast Group parameter is available only on NetPerformer models
that support voice/fax transmissions.
Set Broadcast Group to YES to define the PVC as a member of a broadcast group. The
PVC will be used to receive broadcast frames from the Frame Relay one-way multicast
server. All PVCR PVCs that must be able to receive broadcast frames on the leaf side of
the connection should be configured with Broadcast Group = YES.
Set Broadcast Group to NO (the default value) when the PVCR PVC is not a member of a
broadcast group. This is the correct setting for the PVCs on the root NetPerformer that
transmit the broadcast frames, and for all PVCR PVCs that are not used for voice
broadcasting.
Values: NO, YES
Default: NO
5.3.35 Maximum number of voice channels
Console SNMP Text-based Config
Maximum number of
voice channels
atmpvcMaxChannels [atmpvc#] MaxChannels
Maximum number of incoming and outgoing channels permitted on this PVC or any other
connection serving the destination specified by the Remote Unit Name for this PVC.
Another connection may be a PVCR, FR-USER or FR-NET port, or a PVCR, FP or FP
Memotec Inc. 5-19

ATM Option
MULTIPLEX PVC.
When this parameter is set to 0, all new voice connections will be blocked. When it is set
to 10000, no new connections will be blocked. In this case the Voice Traffic Control
function is disabled on voice calls to the remote unit if no other port or PVC serving
that unit has been configured with the Maximum Number of Voice Channels set to a
value less than 10000.
Two voice channels are opened when a voice call is relayed through a unit: one to reach
the originator of the call, and the other to reach the receiver of the call. When the two
channels pass through the same port or PVC, the bandwidth taken is twice that taken by
one channel. The Maximum Number of Voice Channels parameter represents the
bandwidth that can be used by all voice calls. For further information refer to the chapter
Voice Traffic Control in the Advanced Voice Features fascicle of this document
series.
Values: 0 - 10000
Default: 10000 (no blocking)
5.3.36 Maximum Voice Channels If High Priority Data
Console SNMP Text-based Config
Maximum Voice
Channels If High Priority
Data
atmpvcLowMaxChannels [atmpvc#] LowMaxChannels
Maximum number of incoming and outgoing voice channels permitted at one time on this
PVC connection when one or more transparent serial ports (HDLC, HDLCOFR, DDCMP,
T-ASYNC, R-ASYNC, BSC, COP, X25, PASSTHRU or PASSTHRUOFR) are set to high
priority. The Maximum Voice Channels If High Priority Data parameter has the effect of
ensuring sufficient bandwidth for the high priority data traffic, while allowing a
reasonable number of voice calls to be placed at the same time.
NOTE: The priority of transparent data ports is configured with the port Class parameter.
Refer to the appendix SE/PORT Configuration Parameters in the Legacy
Data fascicle of this document series.
• The DSR, DCD, DTR and RTS modem signals (RI and RL in X.21) must be
active on the high priority transparent serial port for call blocking to take place.
The modem signals on the remote unit must also be active.
You can assume that the remote modem signals are active if the transparent serial
port modem signals are up, and its Modem control signal parameter is set to
STATPASS or DYNAPASS.
• If the Maximum Voice Channels If High Priority Data is left at its default value
(10000), no call blocking is performed on this connection.
5-20 Memotec Inc.

5.3.37 Cell Packetization
SE/PVC Configuration Parameters
• If you change the value of the Maximum Voice Channels if High Priority Data
parameter, there is no effect on voice calls that have already been established. If
required, you can disconnect these calls using the MODEMCALLCLEAR
extended parameter. For details, refer to the Extended Parameters fascicle of
this document series.
Caution: For any new voice calls, the lower call blocking limit will take
effect, either the Maximum number of voice channels (see previous parameter)
or the Maximum Voice Channels if High Priority Data. To avoid
unexpected results, it is best to configure these two parameters with
the same value.
Values: 0 - 10000
Default: 10000 (no call blocking)
Console SNMP Text-based Config
Cell Packetization atmpvcCellPacketization [atmpvc#] CellPacketization
Enable (YES) or disable (NO) cell packetization on this WAN link. This determines
whether several packets of Frame Relay traffic will be combined before transmission.
Packetization accommodates networks that do not support a rapid sequence of several
small cells. However, with cell packetization there is a slight increase in the
transmission delay. Set Cell Packetization to NO for transmission of Frame Relay
traffic without packetization. Cell Packetization should also be disabled if your
application requires high transmission speeds.
When Cell Packetization is enabled, the number of cells that can be combined depends on
the total number of bytes contained in those cells. To adjust the maximum number of bytes
allowed in a Frame Relay application, use the PVCRFS extended parameter. Refer to the
Extended Parameters fascicle of this document series.
NOTE: This parameter can have different values on opposite sides of the link.
Values: NO, YES
Default: YES
Memotec Inc. 5-21

ATM Option
5.4 AAL1 Mode
5.4.1 Number of subchannels
5.4.2 Super frame format
NOTE: AAL1 mode parameters that are common to other PVC modes are listed under
“ATMPVCR Mode” on page 5-4.
Specifies how many voice subchannels are assigned to this PVC. This determines the
number of voice connections that are supported by this AAL1 transport service.
• Each subchannel uses 75 Kbps of bandwidth.
• A maximum of 24 subchannels is allowed on an E1 connection.
• A maximum of 20 subchannels is allowed on a T1 connection.
Specifies the superframe format to be used for AAL1. Choices for North America are:
• DS1-SF: Superframe, with 12 frames and 2-bit (AB) signaling,
• DS1-ESF: Extended superframe, with 24 frames and 4-bit (ABCD) signaling.
The value E1 is used in other countries.
5.4.3 Local inbound voice level (db)
Console SNMP Text-based Config
Number of subchannels atmpvcVoiceNbSubChannel
Values: 0 - 24
Default: 1
[atmpvc#] VoiceNbSub-
Channel
Console SNMP Text-based Config
Super frame format atmpvcVoiceFrame-Format
Values: DS1-SF, DS1-ESF, E1
Default: DS1-SF
[atmpvc#] VoiceFrame-
Format
Console SNMP Text-based Config
Local Inbound voice level
(db)
atmpvcVoiceLocalInbound
[atmpvc#]VoiceLocalInbound
Specifies the local voice level going into the port, measured in 1 dB increments. The value
5-22 Memotec Inc.

SE/PVC Configuration Parameters
of this parameter determines how sensitive the local voice channel will be to the signal
from the attached device. The lower the value, the more sensitive the voice channel is to
the input, and the louder the voice output at the remote end will sound.
5.4.4 Local outbound voice level (db)
5.4.5 Echo canceler
Values: -22 - +7 dB
Default: 0 dB
Specifies the local voice level going out of the port, measured in 1 dB increments. The
higher the value, the louder the volume will be.
Enables or disables echo cancellation on the channel. Echo canceling automatically
reduces echo to tolerable levels. It adapts automatically to changes in the echo that may
occur in successive connections along the virtual path. It also minimizes background noise
and prevents the negative effects of double talk
5.4.6 Double talk threshold (db)
Console SNMP Text-based Config
Local outbound voice
level (db)
Values: -22 - +7 dB
Default: -3 dB
atmpvcVoiceLocalOutbound
[atmpvc#] VoiceLocalOutbound
Console SNMP Text-based Config
Echo canceler atmpvcVoiceEchoCanceler
Values: DISABLE, ENABLE
Default: ENABLE
[atmpvc#] VoiceEcho-
Canceler
Console SNMP Text-based Config
Double talk threshold (db) atmpvcVoiceDTalk-
Threshold
[atmpvc#] VoiceDTalk-
Threshold
Configures the echo cancellation threshold. It can be set to a value in the range -12 to +12
dB, or disabled. If you experience an echo during voice calls, adjust the value up or down
until the echo disappears.
Values: -12 - +12 dB, DISABLED
Default: +6 Db
Memotec Inc. 5-23

ATM Option
5.4.7 Idle code
5.4.8 Jitter buffer (ms)
5.4.9 Signaling type
Console SNMP Text-based Config
Idle code atmpvcVoiceIdleCode [atmpvc#] VoiceIdleCode
Specifies the content of contiguous flags that the NetPerformer transmits when the AAL1
voice connection is inactive and ON HOOK.
NOTE: This Idle Code differs from that defined for the digital link, which is transmitted
over an unused timeslot in fractional T1/E1.
Values: 00 - FF
Default: 7F
Console SNMP Text-based Config
Jitter buffer (ms) atmpvcVoiceJitterBuffer [atmpvc#] VoiceJitterBuffer
This jitter buffer, in milliseconds, is used to accumulate voice samples and to introduce
underruns in case of network delays.
The optimal jitter buffer value can be deduced from the cell delay variance published by
your network provider.
NOTE: Dynamic jitter buffer is not available with ATM.
Values: 30 - 240 ms
Default: 100 ms
Console SNMP Text-based Config
Signaling type atmpvcVoiceSignaling [atmpvc#] VoiceSignaling
Selects the signaling type for the digital voice port, which determines the telephony
interface to be used. The values available may be different depending on the version of
software installed on your unit. Select one of the following values:
• IMMEDIATE START: Transmission takes place immediately. The called PBX
must be ready to accept digits within a short time after the calling PBX raises its
5-24 Memotec Inc.

SE/PVC Configuration Parameters
M-lead. The called PBX normally supplies a dial tone to inform the user that it is
ready to accept digits. This is the industry standard for E&M operation.
• R2: This is a European signaling type that is defined in CCITT recommendations.
It is similar to loop or ground start signaling in North American installations.
R2 is a Channel Associated Signaling (CAS) signaling type. For details,
refer to the Digital Voice fascicle of this document series.
When a digital voice port is configured for R2 signaling, voice connections with a USER
extension number are not supported (Remote Extension Number Source parameter of
the Setup Map menu set to USER). Extension numbers must be retrieved from the Voice
Mapping Table (Remote Extension Number Source parameter set to MAP). Note that a call
can be attempted on more than one port using the Hunt Group feature (Remote Extension
Number Source parameter set to HUNT).
• FXO: In FXO mode, the NetPerformer presents a Telco/PTT interface that acts
like a standard telephone set. The FXO option provides the appearance of a
two-wire telephone in a loop-start circuit. An FXO port detects ring voltage,
closes the loop during off-hook and opens the loop in an on-hook condition. FXO
is an analog signaling type that can also be used on digital ports.
• FXS: In FXS mode, the NetPerformer presents a Telco/PTT interface that acts
like a Central Office and can interface to a conventional two-wire telephone
(pulse-dial or touch-tone). An FXS port provides loop current and ring voltage,
and detects the off-hook and on-hook states. FXS is an analog signaling type that
can also be used on digital ports.
• GND FXS: A variation of FXS which uses ground start rather than loop start signaling.
Ground FXS is an analog signaling type that can also be used on digital
ports.
• GND FXO: A variation of FXO which uses ground start rather than loop start
signaling. Ground FXO is an analog signaling type that can also be used on digital
ports.
• PLAR: Private Line Automatic Ring-down. PLAR is a leased voice circuit that
connects two single endpoints together. When either telephone handset is taken
off-hook, the remote telephone automatically rings. PLAR signaling allows for
voice channel connections that terminate in a PLAR device like a channel bank.
• R-2 China: This signaling protocol accommodates special E1 signaling requirements
for China.
On previous NetPerformer products, these requirements were handled with an
extended parameter, CHINASIGNALING, that is applied to the voice channel.
• Custom: The Custom signaling choice provides the capability to configure custom
signaling and custom ring for analog and digital voice connections. These
custom parameters define signaling characteristics used on non-standard equipment.
If you select this choice, you must manually configure the Custom Signaling
parameters. Refer to the chapter Custom Signaling in the Advanced Voice
Features fascicle of this document series.
Memotec Inc. 5-25

ATM Option
5.4.10 TONE type
5.4.11 TONE regeneration
• WINK START: When Wink is selected, the NetPerformer expects an attached
PBX to raise its A/B bits to request a dial register. The NetPerformer responds by
sending a dial register to the PBX. When the PBX indicates it is ready to accept
dial digits (no dial tone transmitted to the PBX), the NetPerformer toggles the A/
B-lead. When the A/B-lead returns to its original state, the PBX will transmit dial
digits.
Values: IMMEDIATE START, R2, FXO, FXS, GND FXO, GND FXS, PLAR,
WIND START, R2-CHINA, DELAY DIAL, CUSTOM
Default: IMMEDIATE START
Console SNMP Text-based Config
TONE type atmpvcVoiceToneType [atmpvc#] VoiceToneType
Specifies the kind of multi-frequency tones that will be detected on this port (including
call setup). Choose between Dual Tone Multi-Frequency (DTMF), Multi-Frequency (MF)
and R2 tones.
NOTE: Only the DTMF value is available on NetVoice cards of the Central Site unit.
Values: DTMF, MF, R2
Default: DTMF
Console SNMP Text-based Config
TONE regeneration atmpvcVoiceToneDetect-
Regen-s
[atmpvc#] VoiceToneDetectRegen-s
Specifies the number of seconds during which the tones generated by the remote site user
equipment can be regenerated at the local site.
Tones that have been compressed and decompressed by a voice compression algorithm
may be distorted. Distorted tones may not be recognized by voice switching equipment
(such as a PBX), depending on the error margin of the equipment. The Tone Regeneration
parameter allows tones passed through a voice channel to be regenerated locally, thus
avoiding the possibility of distortion.
When the Tone Regeneration parameter is set to 0, the TONE regenerator is always
disabled and tones coming from the remote side through the voice channel are
decompressed as voice. When set to 1, the tone regenerator is always ON. Values from 2
to 255 define a specific period, in seconds, during which the tone regenerator is enabled
locally.
5-26 Memotec Inc.

5.4.12 TONE ON (ms)
5.4.13 TONE OFF (ms)
SE/PVC Configuration Parameters
NOTE: The human voice can produce frequencies which may be interpreted as tones
and then regenerated at the remote site if Tone Regeneration is always ON (set
to 1). To avoid tone regeneration during a conversation, it is recommended
that this parameter be enabled for a limited amount of time (set to 2 to 255).
Values: 0 - 255 sec
Default: 30 sec
Specifies the duration, in milliseconds, of the multi-frequency tone the NetPerformer uses
to generate a single digit.
Specifies the duration, in milliseconds, of the silence the NetPerformer uses between
multi-frequency tones when generating a dial digit string.
The actual duration of the multi-frequency tone depends to a great extent on the user’s
actions, especially for telephones that sound a tone for as long as a number push-button is
pressed. People typically execute a tone duration of 100 - 750 ms, with silence periods of
300 - 1500 ms. Much shorter periods result from automated dialing: typically 60 - 120 ms
for tones, with 50 - 150 ms of silence between tones.
5.4.14 Pulse make/break ratio
Console SNMP Text-based Config
TONE ON (ms) atmpvcVoiceToneOn-ms [atmpvc#] VoiceToneOnms
Values: 30 - 1000 ms (in increments of 10)
Default: 30 ms
Console SNMP Text-based Config
TONE OFF (ms) atmpvcVoiceToneOff-ms [atmpvc#] VoiceToneOffms
Values: 30 - 1000 ms (in increments of 10)
Default: 30 ms
Console SNMP Text-based Config
Pulse make/break ratio atmpvcVoicePulseMake-
Break-ms
[atmpvc#] VoicePulse-
MakeBreak-ms
Memotec Inc. 5-27

ATM Option
5.4.15 Delete digits
Defines the duration, in milliseconds, of the contact (or “make”) for each digit that is
dialed using rotary type dialing. The NetPerformer calculates the break value by
subtracting the make value from 100.
For example, the value 34 defines the make/break ratio as 34/66. This value is used in
North America, Belgium, Denmark, U.K., France, Portugal and other countries, and is the
default Pulse Make/Break Ratio. When you rotate the dial to a number and release it, a
break/contact sequence is repeated once for each digit the dial passes as it returns to the
starting position. If, for instance, you dial the number 3, what follows is a 66 ms break, a
34 ms make, a 66 ms break, a 34 ms make, a 66 ms break, then a continuous make (closed
loop).
Telephone equipment manufacturers in other countries have implemented other make/
break ratios. For example, a 40/60 ratio is used in Austria, Germany, Italy, Ireland,
Sweden, Switzerland and some other countries. Configure this by setting the Pulse Make/
Break Ratio to 40. To ensure correct configuration of the Pulse Make/Break Ratio
parameter for your site, contact your local telephone company for the make/break ratio
that is currently in use.
Values: 30 - 50 ms (in increments of 4)
Default: 34 ms
Console SNMP Text-based Config
Delete digits atmpvcVoiceDelDigits [atmpvc#] VoiceDelDigits
Specifies the number of leading dial digits (if any) that will be deleted from a dial string
before it is forwarded to the attached voice equipment. When set to 0, no dial digits are
deleted.
This parameter serves to delete the leading dial digits that may be inserted by an attached
PBX. For example, a PBX may insert a “9” prefix in any dial string. If you dial “1234”,
the result would be “91234”. To forward the correct dial string to the remote voice
equipment, the local NetPerformer must be able to delete the first digit of the string. In this
case, you would set the local port’s Delete Digits parameter to 1.
NOTE: This parameter is not required and does not appear on the NetPerformer console
for voice ports associated with an EIC-1MB card that is running Q.SIG
signaling.
Values: 0 - 4
Default: 0
5-28 Memotec Inc.

5.4.16 Fwd digits
SE/PVC Configuration Parameters
Console SNMP Text-based Config
Fwd digits atmpvcVoiceFwdDigits [atmpvc#] VoiceFwdDigits
For switched or autodial activation only.
This parameter takes effect at the receiver site, and specifies which dial digits (if any)
should be forwarded to the attached user equipment. There are three possibilities:
• NONE: No dial digits are forwarded to the attached equipment.
• ALL: The speed dial number and its associated extended digits are forwarded to
the attached equipment. The extended digits may be looked up in the Voice Mapping
Table or manually dialed by the user. For an Autodial port, the source of the
user-dialed extended digits is determined by the Extended Digits Source parameter
configured at the PORT level (described earlier). For a Switched port, refer to
the Extended Digits Source parameter of the Setup Map menu, described later.
• EXT: Only the extended digit string is forwarded to the attached equipment.
Use the Forward Digits parameter when the NetPerformer voice port connects to the trunk
side of a PBX or a CO. If an automated answering system responds to the call, the PBX or
CO can dial the telephone number to connect to a device on the station side.
NOTE: This parameter does not influence the digits that are sent from the local Net-
Performer to the remote NetPerformer. Both the speed dial number and any
associated extended digits are sent to the remote site at all times.
This parameter is not used on voice ports associated with an EIC-1MB card running
Q.SIG signaling. For Q.SIG-to-Q.SIG communications, the Q.SIG signaling stack on the
E1C-1MB card takes care of exchanging the phone numbers. However, the Voice
Mapping Table is still required to perform the proper call routing.
When a non-Q.SIG unit (VFC-03, TIC, EIC with CAS signaling, ISDN-03 card) calls a
Q.SIG device, the Forward Digits parameter should be set to ALL. This means that the
speed dial number will be forwarded, along with any extended digits that were sent by the
originating unit. The EIC-1MB card in turn sends the resultant number (Speed_Dial +
Any_Extended_Digits) to the destination PBX. Then, the PBX will process this number as
if it were received from the CO.
Values: NONE, ALL, EXT
Default: NONE
Memotec Inc. 5-29

ATM Option
5.4.17 Fwd delay
5.4.18 Fwd type
Console SNMP Text-based Config
Fwd delay atmpvcVoiceFwdDelayms
For switched or autodial activation only.
Specifies the length, in milliseconds, of a pause that precedes the forwarded dial digit
string. Set this parameter to a non-zero value if the remote PBX requires a delay before
forwarding the telephone number to the station side. When set to 0, no pause will be made.
The Forward Delay parameter also determines the length of a pause that is inserted in the
extended digits string using the pause (,) character. When this character is encountered, the
forwarding NetPerformer will pause for the length of time specified by Forward Delay
before forwarding additional extended digits.
Values: 0 - 255 ms
Default: 0 ms
[atmpvc#] VoiceFwd-
Delay-ms
Console SNMP Text-based Config
Fwd type atmpvcVoiceFwdType [atmpvc#] VoiceFwdType
For switched or autodial activation only.
Specifies how the dial digits are sent to the remote attached equipment for forwarding to
the station side of an attached PBX or CO. Select TONE or PULSE according to the
requirements of the attached user equipment.
NOTE: If you set the Forward Type parameter to PULSE, ensure that the dial digit
string does not contain an asterisk (*) or pound sign (#). These characters cannot
be generated as pulse digits.
Values: TONE, PULSE
Default: TONE
5-30 Memotec Inc.

5.5 FRF.8 Mode
5.5.1 Port
5.5.2 DLCI address
SE/PVC Configuration Parameters
NOTE: FRF.8 mode parameters that are common to other PVC modes are described
in the section “ATMPVCR Mode” on page 5-4.
Console SNMP Text-based Config
Port atmpvcFrPort [atmpvc#] FrPort
Set to the port or channel number that provides the Frame Relay access link.
NOTE: This list is automatically generated by the NetPerformer, and can include
built-in serial ports, ports on a Dual Serial interface card, and digital data
channels. From this list, you must select a port or channel configured with
the FR-USER protocol.
Values: automatically generated list of ports and channels
Default: 1
Console SNMP Text-based Config
DLCI address atmpvcDlciAddress [atmpvc#] DlciAddress
This parameter determines the Data Link Connection Identifier (DLCI) address of the
PVC. To have the unit learn the DLCI address automatically from the Frame Relay switch,
set this parameter to zero (0, the default value). AUTO DLCI is applicable to PVCs in
PVCR mode only. The NetPerformer obtains the correct address for the PVCR PVC from
the network through the Full Status Report. In the factory setup, 8 PVCR PVCs with
AUTO DLCI are allocated on Port 1.
To set this parameter manually, select a non-zero value. When the PVC is set in PVCR,
RFC1490 or TRANSP mode this address is provided by the carrier, and represents the
virtual circuit identification for accessing the remote unit. When the PVC is set in
MULTIPLEX mode, the DLCI address must be the same as that of the Frame Relay enduser
device attached to the NetPerformer port that this PVC uses.
NOTE: This parameter is not required for a PVC in ATM-MULTIPLEX mode.
Memotec Inc. 5-31

ATM Option
If you define the DLCI Address with a value that has already been configured for another
PVC with the same reference port, you will be alerted of the conflict and requested to
select a different DLCI Address.
NOTE: In some circumstances, a conflict may occur between two PVCs that are configured
while the reference port is offline. If this happens:
• An alarm is logged. Execute the Display Alarms (DA) command to view the
alarms.
• The DPVC and DS/PVC commands will indicate CONFLICT as the PVC State.
• Only one PVC will be functional if the port comes back up.
To avoid possible conflicts between PVCs, we suggest that you complete port
configuration before PVC configuration.
5.5.3 Committed Information rate
NOTE: The LMI (Local Management Interface) protocol uses reserved DLCI address
1023. The ANNEX-D and the Q.933 protocols use reserved DLCI address 0.
When the DLCI address parameter is set for AUTO DLCI, neither of these
reserved addresses will be used as the actual DLCI address of the PVC. To
view the actual DLCI address from the console, execute the Display States
(DS) command and select PVC. If you are using SNMP, select the statPvcDlci
variable.
Values: 0 - 1022
Default: 0 (AUTO DLCI for PVCR PVC)
Console SNMP Text-based Config
Committed Information
rate
atmpvcInfoRate [atmpvc#] InfoRate
PVC Committed Information Rate (CIR) in bits per second. The CIR represents the data
throughput that the network can accept on this PVC. Since frames exceeding the CIR can
be discarded, the CIR parameter must be set properly to prevent data loss in the network.
The current information rate algorithm of the NetPerformer uses two different levels of
information rate: the CIR and BIR. The information rate that is applied is:
• The BIR if it is greater than the CIR and no congestion has been detected (no
BECN received),
5-32 Memotec Inc.

SE/PVC Configuration Parameters
• The CIR if the BIR is not effective or if congestion occurred while running at the
BIR.
A full explanation of how to fine tune the CIR and BIR appears in the section
Information Rate Parameters in the Extended Parameters fascicle of this document
series.
5.5.4 Burst Information rate
NOTE: This parameter is not used for PVCs in ATMPVCR or ATM-MULTIPLEX
mode. Consult “Service Categories” on page 1-10 for a description of all factors
that affect cell rate pacing when these modes are selected.
Values: 4000 - 6144000
Default: 56000
Console SNMP Text-based Config
Burst Information rate atmpvcBurstInfoRate [atmpvc#] BurstInfoRate
PVC Burst Information Rate (BIR) in bits per second. The BIR represents the data
throughput when the PVC is in burst mode. For example, if you configure the BIR at
64000 bps and the CIR at 56000 bps, the NetPerformer will transmit at 64000 bps unless
congestion occurs, when the rate will be reduced to 56000 bps.
NOTE: Two Extended Parameters also control the information rate of Frame Relay
connections. Together these parameters can be used to adjust the committed
and burst rate sampling timers on networks that integrate bursty high-speed
traffic with constant low-speed traffic. They are described in the section
Information Rate Parameters in the Extended Parameters fascicle of
this document series.
NOTE: This parameter is not used for PVCs in ATMPVCR or ATM-MULTIPLEX
mode. Consult “Service Categories” on page 1-10 for a description of all factors
that affect cell rate pacing when these modes are selected.
Values: 4000 - 6144000
Default: 56000
Memotec Inc. 5-33

ATM Option
5.5.5 Header translation
5.5.6 ATM CLP bit
5.5.7 ATM EFCI bit
Console SNMP Text-based Config
Header translation atmpvcFrfHdrTranslation [atmpvc#] FrfHdrTranslation
Activates (YES) or deactivates (NO) header translation for this PVC. The value of this
parameter determines the encapsulation mode (TRANSLATION or TRANSPARENT) for
this PVC.
• Select YES if the RFC-1483 header should be translated to RFC-1490, and vice
versa.
• Select NO for TRANSPARENT mode, where the user data is unchanged as it
passes from one side to the other.
For details, see “Transparent versus Translation Mode” on page 1-21.
Values: NO, YES
Default: YES
Console SNMP Text-based Config
ATM CLP bit atmpvcFrfAtmClp [atmpvc#] FrfAtmClp
Indicates whether the Cell Loss Priority (CLP) bit should be:
• Reset (value = 0)
• Set (value = 1)
• A copy of the Discard Eligibility (DE) bit of the received Frame Relay frames
(value = DE).
For details, see “Service Interworking Functions” on page 1-19.
Values: 0, 1, DE
Default: DE
Console SNMP Text-based Config
ATM EFCI bit atmpvcFrfAtmEfci [atmpvc#] FrfAtmEfci
Indicates whether the Explicit Forward Congestion Indicator (EFCI) bit should be:
• Reset (value = 0)
• Set (value = 1)
5-34 Memotec Inc.

5.5.8 Frame relay DE bit
5.5.9 Frame relay FECN bit
SE/PVC Configuration Parameters
• A copy of the Forward Explicit Congestion Notification (FECN) bit of the
received Frame Relay frames (value = FECN).
For details, see “Service Interworking Functions” on page 1-19.
Values: 0, 1, FECN
Default: FECN
Indicates whether the DE bit should be:
• Reset (value = 0)
• Set (value = 1)
• A copy of the CLP bit of the received ATM frames (value = CLP).
For details, see “Service Interworking Functions” on page 1-19.
Indicates whether the FECN bit should be:
• Reset (value = 0)
• Set (value = 1)
• A copy of the EFCI bit of the received ATM frames (value = EFCI).
For details, see “Service Interworking Functions” on page 1-19.
5.5.10 Congestion queue size
Console SNMP Text-based Config
Frame relay DE bit atmpvcFrfFrDe [atmpvc#] FrfFrDe
Values: 0, 1, CLP
Default: CLP
Console SNMP Text-based Config
Frame relay FECN bit atmpvcFrfFrFecn [atmpvc#] FrfFrFecn
Values: 0, 1, EFCI
Default: EFCI
Console SNMP Text-based Config
Congestion queue size atmpvcFrfCongestionQ-
Size
[atmpvc#] FrfCongestion-
QSize
Defines the threshold, in bytes, at which the NetPerformer determines that congestion is
Memotec Inc. 5-35

ATM Option
5.5.11 Maximum queue size
occurring.
This value is applied in both directions, ATM-to-Frame Relay and Frame Relay-to-ATM.
For details, see “Service Interworking Functions” on page 1-19.
Values: 0 - 100000
Default: 4000
Console SNMP Text-based Config
Maximum queue size atmpvcFrfMaximumQ-
Size
[atmpvc#] FrfMaximumQ-
Size
This parameter defines the threshold, in bytes, at which the NetPerformer determines that
an overflow is occurring and starts discarding further frames.
This value is applied in both directions, ATM-to-Frame Relay and Frame Relay-to-ATM.
For details, see “Service Interworking Functions” on page 1-19.
Values: 0 - 100000
Default: 8000
5-36 Memotec Inc.

5.6 RFC1483 Mode
5.6.1 BRG connection
5.6.2 IP connection
5.6.3 Frame size
SE/PVC Configuration Parameters
NOTE: RFC1483 mode parameters that are common to other PVC modes are
described in the section “ATMPVCR Mode” on page 5-4.
Console SNMP Text-based Config
BRG connection atmpvcBrgConnection [atmpvc#] BrgConnection
Allows or disallows a bridge connection. Set this parameter to YES if the RFC1490compatible
FRAD at the remote end requires bridge frames. If bridge data is not required,
a NO value will prevent the transmission of unnecessary bridge frames from this PVC,
thus reducing your network costs.
Values: NO, YES
Default: NO
Console SNMP Text-based Config
IP connection atmpvcIpConnection [atmpvc#] IpConnection
Allows or disallows an IP connection. Set this parameter to YES if the RFC1490compatible
FRAD at the remote end requires IP frames. If IP data is not required, a NO
value will prevent the transmission of unnecessary IP frames from this PVC, thus reducing
your network costs.
Values: NO, YES
Default: YES
Console SNMP Text-based Config
Frame size pvcMaxFrame [pvc#] MaxFrame
Maximum frame size, in bytes. This parameter determines the largest datagram that can be
sent or received on the PVC in one IP frame. Datagrams larger than the maximum frame
size are divided into fragments before transmission, then reassembled at the remote end.
Values: 128 - 8192
Default: 1500
Memotec Inc. 5-37

ATM Option
5.7 ATMPPP Mode
ATMPPP mode parameters that are common to other PVC modes are described in the
section “ATMPVCR Mode” on page 5-4. Parameters controlling PPP characteristics are
detailed in the appendix SE/PORT/#/PPP Configuration Parameters in the WAN/
Point-to-Point (PPP) fascicle of this document series.
5.8 ATM-MULTIPLEX Mode
5.8.1 ATM Adaptation Layer
NOTE: ATM-MULTIPLEX mode parameters that are common to other PVC modes
are described in the section “ATMPVCR Mode” on page 5-4.
Console SNMP Text-based Config
ATM Adaptation Layer atmpvcAdaptationLayer [atmpvc#] ATM Adaptation
Layer
Determines the AAL type to be used for this PVC:
• AAL0: Provides transparent support of all cells in any type of ATM Adaptation
Layer: AAL1 to AAL5, inclusive
- Should be selected for transporting AAL types other than AAL5
- No idle cells are transmitted, only cells that are defined with a VPI/VCI combination
- Traffic is processed on a per cell basis.
• AAL5: For use with variable bit-rate traffic in a connection-oriented mode.
- Transfers AAL5 traffic from one site to another
- Cells are accumulated into frames before being transferred to the destination
unit.
Refer also to “ATM Multiplex Connections” on page 1-24.
Values: AAL0, AAL5
Default: AAL0
5-38 Memotec Inc.

5.8.2 Remote PVC number
5.8.3 Class
Determines the destination PVC for traffic from this PVC.
SE/PVC Configuration Parameters
Console SNMP Text-based Config
Remote PVC number atmpvcRemotePvc [atmpvc#] RemotePvc
Values: 1 - 300
Default: The local PVC number
Console SNMP Text-based Config
Class atmpvcClass [atmpvc#] PvcClass
The priority class for traffic from this PVC. Classes are defined according to bandwidth
weight, or you can choose HIGH PRIORITY. Traffic on a high-priority connection is
processed before other traffic types.
High priority data may be desired for videoconferencing applications where the available
bandwidth is limited. For information on how to set the classes so as to prioritize missionsensitive
data, refer to the Quality of Service (QoS) fascicle of this document series.
Values: 1 - 8, HIGH PRIORITY
Default: 3
Memotec Inc. 5-39

ATM Option
5-40 Memotec Inc.

SE/SVC Configuration Parameters
6
Memotec Inc. 6-1

ATM Option
6.1 SVC number
6.2 Mode
Console SNMP Text-based Config
SVC number atmsvcEntry, atmsvcIndex
[atmsvc#]
Enter the number of the SVC you want to configure on the console command line. For
SNMP, select the atmsvcEntry table and look under the atmsvcIndex for the desired SVC.
Once you select an SVC, the SVC number is displayed thereafter at the beginning of each
line from the console.
Values: 1 - 300
Default: 1
Console SNMP Text-based Config
Mode atmsvcMode [atmsvc#] Mode
Selects the type of SVC to be used for this ATM logical connection.
• ATMPVCR: for PowerCell over ATM AAL5, an integrated traffic transport
method (see “PowerCell in the ATM Network” on page 1-16 for background
information)
• FRF.8: for FRF.8, a Service Interworking method ideal for Frame Relay traffic
(see “Frame Relay/ATM Service Interworking (FRF.8)” on page 1-18)
• RFC1483: for multiprotocol over ATM AAL5 using RFC-1483, a data traffic
transport method (see “LLC Encapsulation (RFC-1483)” on page 1-22)
• ATMPPP: for PPP over ATM AAL5 using RFC-2364, a data traffic transport
method ideal for Internet access (see “PPP Over AAL5” on page 1-23)
Values: OFF, ATMPVCR, FRF.8, RFC1483, ATMPPP
Default: OFF
6-2 Memotec Inc.

6.3 ATMPVCR Mode
6.3.1 SVC Destination address
6.3.2 SVC Local Address
SE/SVC Configuration Parameters
NOTE: Many of the parameters detailed in this section are also listed when the PVC
is configured to another mode.
Required only if the associated ATM channel is configured with the UNI Type
set to PRIVATE.
Indicates the destination address in AESA format.
Required only if the associated ATM channel is configured with the UNI Type
set to PRIVATE.
Provides the AESA user part (low-order ESI and SEL fields). This address is concatenated
with the prefix of the ATM switch to form the full AESA address.
6.3.3 SVC Destination E.164 Address
Console SNMP Text-based Config
SVC Destination address atmsvcDestAddr [atmsvc#] DestAddr
Values: 40 hexadecimal digits (20 bytes)
Default: all zeros
Console SNMP Text-based Config
SVC Local Address atmsvcLocalAddr [atmsvc#] LocalAddr
Values: 14 hexadecimal digits (7 bytes)
Default: all zeros
Console SNMP Text-based Config
SVC Destination E.164
Address
atmsvcDestAddrE164 [atmsvc#] DestAddrE164
Required only if the associated ATM channel is configured with the UNI Type
set to PUBLIC.
Indicates the destination address in E.164 format.
Values: maximum 15 decimal digits
Default: all zeros
Memotec Inc. 6-3

ATM Option
6.3.4 SVC Local E.164 Address
6.3.5 Type
6.3.6 Call Delay
SVC Local E.164
Address
Console SNMP Text-based Config
atmsvcLocalAddrE164 [atmsvc#] LocalAddrE164
Required only if the associated ATM channel is configured with the UNI Type
set to PUBLIC.
Provides the local address in E.164 format.
Values: maximum 15 decimal digits
Default: all zeros
Console SNMP Text-based Config
Type atmsvcType [atmsvc#] Type
Sets the call activation type:
• DEDICATED: The NetPerformer will attempt to establish the call to the destination
address.
• ANSWER: The NetPerformer will not initiate the call; it will wait for the remote
side to place the call.
NOTE: If both sides are set to DEDICATED, the Call Delay and Call Retry Delay
parameters (see below) can be used to avoid constant call collisions.
Values: DEDICATED, ANSWER
Default: DEDICATED
Console SNMP Text-based Config
Call Delay atmsvcCallDelay [atmsvc#] CallDelay
For DEDICATED type only.
Sets the number of seconds that the NetPerformer will wait before attempting to place a
call to the destination address.
Values: 1 - 255
Default: 5
6-4 Memotec Inc.

6.3.7 Call Retry Delay
6.3.8 Peak cell rate (PCR)
SE/SVC Configuration Parameters
Console SNMP Text-based Config
Call Retry Delay atmsvcCallRetry [atmsvc#] CallRetry
For DEDICATED type only.
Sets the number of seconds that the NetPerformer will wait before retrying a call to the
destination address after a failed attempt.
NOTE: When both sides of an SVC connection are set to Type=DEDICATED, configure
the Call Delay and Call Retry Delay so as to avoid repetitive call collisions.
Values: 1 - 255
Default: 10
Console SNMP Text-based Config
Peak cell rate (PCR) atmsvcPeakCellRate [atmsvc#] PeakCellRate
Sets the maximum cell rate that can be supported by this ATM SVC, in cells per second.
Values: T1 interfaces: 0 - 3622
E1 interfaces: 0 - 4679
Default: 1000
NOTE: The other parameters required for configuration of ATMPVCR mode are typical
of a PowerCell PVC (PVCR) connection, and are fully described in the
appendix “SE/PVC Configuration Parameters” on page 5-1. For further information,
consult the section “ATMPVCR Mode” on page 5-4 under the equivalent
parameter name.
• All SNMP variables have the prefix atmsvc rather than atmpvc
• All text-based configuration entries are under the [atmsvc#] heading rather than
[atmpvc#].
Memotec Inc. 6-5

ATM Option
6.4 FRF.8 Mode
6.5 RFC1483 Mode
FRF.8 mode parameters that are common to other PVC modes are described in the section
“ATMPVCR Mode” on page 6-3.
The other parameters required for configuration of FRF.8 mode are typical of a Frame
Relay logical connection, and are fully described in the appendix “SE/PVC Configuration
Parameters” on page 5-1. Consult the section “FRF.8 Mode” on page 5-31 under the
equivalent parameter name.
• All SNMP variables have the prefix atmsvc rather than atmpvc
• All text-based configuration entries are under the [atmsvc#] heading rather than
[atmpvc#].
RFC1483 mode parameters that are common to other PVC modes are described in the
section “ATMPVCR Mode” on page 6-3.
The other parameters required for configuration of RFC1483 mode are typical of an
RFC1483 logical connection, and are fully described in the appendix “SE/PVC
Configuration Parameters” on page 5-1. Consult the section “RFC1483 Mode” on page 5-
37 under the equivalent parameter name.
• All SNMP variables have the prefix atmsvc rather than atmpvc
• All text-based configuration entries are under the [atmsvc#] heading rather than
[atmpvc#].
6.6 ATMPPP Mode
ATMPPP mode parameters that are common to other PVC modes are described in the
section “ATMPVCR Mode” on page 6-3.
The other parameters required for configuration of ATMPPP mode are typical of a PPP
logical connection, and are fully described in the appendix “SE/PVC Configuration
Parameters” on page 5-1. Consult the section “ATMPPP Mode” on page 5-38 under the
equivalent parameter name.
• All SNMP variables have the prefix atmsvc rather than atmpvc
• All text-based configuration entries are under the [atmsvc#] heading rather than
[atmpvc#].
6-6 Memotec Inc.

Index
A
AAL service classes 1-4
AAL0 1-25
AAL1 1-16
AAL1 PVC 2-21
AAL5 1-23, 1-25
Accept Incoming ATM AAL1 Calls 4-6
ATM
SVC statistics 3-5
ATM Adaptation Layer 5-38
ATM CLP bit 5-34
ATM EFCI bit 5-34
ATM layers 1-3
ATM Signaling Channel VCI 4-5
ATM Signaling Channel VPI 4-4
ATM support 1-13
ATM-MULTIPLEX mode 1-24
ATM-MULTIPLEX PVC 2-25
ATMPPP PVC 2-24
ATMPVCR PVC 2-18
Availability
on NetPerformer products 2-2
B
Bandwidth requirements 1-10
Bit rate 1-10
BRG connection 5-37
Broadcast group 5-19
Burst Information rate 5-33
C
Call Delay 6-4
Call Retry Delay 6-5
CBR 1-11
Cell pacing 1-10
Cell Packetization 5-21
Cell transmission 1-5
Class 5-39
Committed Information rate 5-32
Compression parameter 5-8
Configuration 2-4
AAL1 PVC 2-21
ATM-MULTIPLEX PVC 2-25
ATMPPP PVC 2-24
ATMPVCR PVC 2-18
digital link 2-13
FRF.8 PVC 2-22
preparing for 2-2
PVCs 2-17
RFC1483 PVC 2-22
user channels 2-15
Congestion queue size 5-35
Constant bit rate 1-11
ATM Option 1
D
Delete digits 5-28
DESTINATION ADDRESS, displaying for ATM 3-9
Digital link configuration 2-13
Display states
ATM SVCs 3-5
DLCI address 5-31
Double talk threshold (db) 5-23
DSVC command, for ATM SVCs 3-8
E
Echo canceler 5-23
F
Factory Setup command 2-3
Feature overview 1-2
Filter parameter 5-18
Frame Relay 1-18
Frame relay DE bit 5-35
Frame relay FECN bit 5-35
Frame Relay port 5-31
Frame size, of PVC 5-37
FRF.8 1-18
FRF.8 PVC 2-22
FS command 2-2
Fwd delay 5-30
Fwd digits 5-29
Fwd type 5-30
H
Header translation 5-34
HEC coset function 4-2
I
Idle cell 4-2
Idle cell payload 4-2
Idle code 5-24
ILMI Channel VCI 4-5

ILMI Channel VPI 4-5
Installation status 2-3
IP address 5-8
IP connection 5-37
IP multicast active 5-16
IP multicast protocol 5-17
IP RIP 5-11
IP RIP authentication type 5-12
IP RIP password 5-12
IP RIP TX/RX 5-12
IPX network number 5-18
IPX RIP 5-17
IPX SAP 5-18
J
Jitter buffer (ms) 5-24
L
License 2-2
See also Software license
Link, for ATM 2-13
LLC encapsulation 1-22
Local inbound voice level (db) 5-22
Local outbound voice level (db)
Parameter list
Local outbound voice level (db) 5-23
M
Maximum burst size (MBS) in cells 5-7
Maximum number of voice channels 5-19
Maximum queue size 5-36
Maximum Voice Channels If High Priority Data 5-
20
Mode parameter 5-2
Mode, for SVC 6-2
Multiplexed connection 1-24
N
NAT enable 5-9
NAT rule 5-10
NAT side 5-10
NetPerformer support of ATM 1-13
Non-real-time variable bit rate 1-12
NRT-VBR 1-12
Number of ATM AAL5 VCs reserved 2-9
Number of data channels reserved 2-8
Number of DSPs reserved for AAL1 2-7
Number of retransmission retries 5-8
Number of subchannels 5-22
O
Operation 1-4
OSPF 5-13
OSPF Area ID 5-14
OSPF Dead interval 5-15
OSPF Hello interval 5-15
OSPF Metric cost 5-16
OSPF Password 5-15
OSPF Retransmit interval 5-14
OSPF Transit delay 5-14
2 Memotec Inc.
P
Parameter list
Accept Incoming ATM AAL1 Calls 4-6
ATM Adaptation Layer 5-38
ATM CLP bit 5-34
ATM EFCI bit 5-34
ATM Signaling Channel VCI 4-5
ATM Signaling Channel VPI 4-4
BRG connection 5-37
Broadcast group 5-19
Burst Information rate 5-33
Call Delay 6-4, 6-5
Call Retry Delay 6-5
Cell Packetization 5-21
Class 5-39
Class, on PASSTHRU port 5-38, 5-39
Committed Information rate 5-32
Compression 5-8
Congestion queue size 5-35
Delete digits 5-28
DLCI address 5-31
Double talk threshold 5-23
Double talk threshold (db) 5-23
Echo canceler 5-23
Filter 5-18
Frame relay DE bit 5-35
Frame relay FECN bit 5-35
Frame Relay port 5-31
Frame size 5-37
Frame size, for PVC 5-37
Fwd delay 5-30
Fwd digits 5-29
Fwd type 5-30
Header translation 5-34
HEC coset function 4-2
Idle cell 4-2
Idle cell payload 4-2
Idle code 5-24
ILMI Channel VCI 4-5
ILMI Channel VPI 4-5
IP address 5-8
IP connection 5-37
IP multicast active 5-16
IP multicast protocol 5-17
IP RIP 5-11
IP RIP authentication type 5-12

IP RIP password 5-12
IP RIP TX/RX 5-12
IPX network number 5-18
IPX RIP 5-17
IPX SAP 5-18
Jitter buffer 5-24
Jitter buffer (ms) 5-24
Local inbound voice level 5-22
Local inbound voice level (db) 5-22
Local outbound voice level 5-23
Maximum burst size (MBS) in cells 5-7
Maximum number of voice channels 5-19
maximum number of voice channels 5-19
Maximum queue size 5-36
Maximum Voice Channels If High Priority Data
5-20
Mode 5-2
Mode, for port 5-2
Mode, for PVC 6-2
Mode, for SCV 6-2
NAT Enable 5-9
NAT enable 5-9
NAT Rule 5-10
NAT rule 5-10
NAT Side 5-10
NAT side 5-10
Number of ATM AAL5 VCs reserved 2-9
Number of data channels reserved 2-8
Number of DSPs reserved for AAL1 2-7
Number of retransmission retries 5-8
Number of subchannels 5-22
OSPF 5-13
OSPF Area ID 5-14
OSPF Dead interval 5-15
OSPF Hello interval 5-15
OSPF Metric cost 5-16
OSPF Password 5-15
OSPF Retransmit interval 5-14
OSPF Transit Delay 5-14
OSPF Transit delay 5-14
Payload Information Rate 5-6
Peak cell rate 5-6
Peak cell rate (PCR) 6-5
Pulse make/break ratio 5-28
PVC number 5-2
PVC number, Frame Relay 5-2, 6-2
Remote PVC number 5-39
Remote unit name 5-7
Scrambling function 4-3
Service category 5-5
Signaling type 5-24
Subnet mask 5-9
Super frame format 5-22
Sustainable cell rate (SCR) 5-6
SVC Destination address 6-3
SVC Destination E.164 Address 6-3
SVC Local Address 6-3
SVC Local E.164 Address 6-4
SVC number 6-2
Timeout (msec) 5-8
Tone OFF 5-27
TONE OFF (ms) 5-27
Tone ON 5-27
TONE ON (ms) 5-27
TONE regeneration 5-26
Tone regeneration 5-26
TONE type 5-26
Tone type 5-26
Total Information Rate 5-6
Type, for PVC 6-4
Type, for SVC 6-4
UNI Type 4-4
UNI Version 4-3
VCI address 5-4
VPI address 5-4
Payload Information Rate 5-6
Peak cell rate 5-6
Peak cell rate (PCR) 6-5
PowerCell 1-16
PPP 1-23
Product license 2-2
See also Software license
Protocols 1-4
Pulse make/break ratio 5-28
PVC
AAL1 2-21
ATM-MULTIPLEX 2-25
ATMPPP 2-24
ATMPVCR 2-18
configuration 2-17
FRF.8 2-22
maximum frame size 5-37
RFC1483 2-22
PVC number 5-2
ATM Option 3
Q
QoS 1-10
R
Real-time Variable Bit Rate 1-12
Remote PVC number 5-39
Remote unit name 5-7
RFC-1483 1-22
RFC1483 PVC 2-22
RT-VBR 1-12
S
SC command 3-2

Scrambling function 4-3
Service categories 1-10
Service category parameter 5-5
Signaling type 5-24
Software license 2-2
agreement 2-2
State
ATM SVC 3-5
STATE & DELAY, displaying for ATM 3-10
Statistics
ATM, DSVC command 3-8
DESTINATION ADDRESS, ATM 3-9
STATE & DELAY, ATM 3-10
SVC Destination address, ATM 3-7
SVC Local address, ATM 3-7
SVC MODE, ATM 3-9
SVC STATUS, ATM 3-9
SVC Status, ATM 3-7
STC command 3-2
Subnet mask 5-9
Super frame format 5-22
Sustainable cell rate (SCR) 5-6
SVC 1-27
ATM, DSVC command 3-8
SVC Destination address 6-3
displaying for ATM 3-7
SVC Destination E.164 Address 6-3
SVC Local Address 6-3
SVC Local address, displaying for ATM 3-7
SVC Local E.164 Address 6-4
SVC MODE, displaying for ATM 3-9
SVC number 6-2
SVC STATUS, displaying for ATM 3-9
SVC Status, displaying for ATM 3-7
Switching 1-6
T
Timeout (msec) 5-8
TONE OFF (ms) 5-27
TONE ON (ms) 5-27
TONE regeneration 5-26
TONE type 5-26
Total Information Rate 5-6
Traffic priority 1-10
Type, for SVC 6-4
U
UBR 1-12
UNI Type 4-4
UNI Version 4-3
Unspecified bit rate 1-12
User channels 2-15
4 Memotec Inc.
V
VC command 3-2
VCI address 5-4
Virtual channel (VC) 1-5
Virtual path (VP) 1-5
VPI address 5-4

ATM Option 5

REACH FURTHER. OFFER MORE.
Contact Memotec:
tel.: +1-514-738-4781
e-mail: MemotecSupport@memotec.com
7755 Henri Bourassa Blvd. West
Montreal, Quebec | Canada H4S 1P7 www.memotec.com