620-0216-006-WAN - Frame Relay

WAN/Frame Relay
NetPerformer System Reference
COPYRIGHTS AND DISCLAIMERS

Published Date: April 2009
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, SDM8400, 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 2009 Memotec Inc.
Memotec Inc.
7755 Henri Bourassa Blvd. West

Montreal, Quebec
Canada H4S 1P7
Tel.: (514) 738-4781
FAX: (514) 738-4436
www.memotec.com
Contents
Chapter 1: NetPerformer Frame Relay Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1. 1
Packet Mode Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1. 2
Permanent Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1. 3
Switched Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1. 4
Frame Relay Encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Chapter 2: Planning the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2. 1
Selecting the Port Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2. 2
Selecting the PVC Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2. 3
Other PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2. 4
Example Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2. 5
Setting the SVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2. 6
NNI System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Chapter 3: Frame Relay Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3. 1
3. 2
Frame Relay Port Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . 3-2

3.1.1
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.1.2
FR-NET Port Configuration Parameters . . . . . . . . . . . . . . . . . . 3-4
3.1.3
FR-NET Channel Configuration Parameters . . . . . . . . . . . . . . . 3-4
3.1.4
FR-USER Port Configuration Parameters . . . . . . . . . . . . . . . . . 3-5
3.1.5
FR-USER Channel Configuration Parameters . . . . . . . . . . . . . . 3-6
PVC Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

3.2.1
PVCR PVC Configuration Parameters . . . . . . . . . . . . . . . . . . . 3-10
3.2.2
RFC1490 PVC Configuration Parameters . . . . . . . . . . . . . . . . 3-10
3.2.3
Multiplex PVC Configuration Parameters. . . . . . . . . . . . . . . . . 3-11
3.2.4
Broadcast PVC Configuration Parameters. . . . . . . . . . . . . . . . 3-12
3.2.5
Transparent PVC Configuration Parameters . . . . . . . . . . . . . . 3-13
Chapter 4: Frame Relay Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4. 1
About NetPerformer Frame Relay link status . . . . . . . . . . . . . . . . . . . . . . 4-2
4. 2
Displaying Frame Relay Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

4.2.1
Port Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.2.2
PVC Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.2.3
Transmitter rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Memotec Inc.
Memotec Inc.
4.2.4
Receiver rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.2.5
Transmitter rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.2.6
Receiver rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.2.7
Number of frames transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.2.8
Number of frames received . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.2.9
Number of octets transmitted. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.2.10
Number of octets received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.2.11
Number of BECN received . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.2.12
Number of BECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.2.13
Number of FECN received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.2.14
Number of FECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.2.15
Number of CLLM frames received. . . . . . . . . . . . . . . . . . . . . . . 4-7
4.2.16
Number of CLLM frames transmitted. . . . . . . . . . . . . . . . . . . . . 4-7
4.2.17
Transparent PVC Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.2.18
SVC Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.2.19
Transmitter rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.2.20
Receiver rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.2.21
Transmitter rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.2.22
Receiver rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.2.23
Number of frames transmitted . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.2.24
Number of frames received . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.2.25
Number of octets transmitted. . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.2.26
Number of octets received. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.2.27
Number of BECN received . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.2.28
Number of BECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.2.29
Number of FECN received. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.2.30
Number of FECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.2.31
Number of CLLM frames received. . . . . . . . . . . . . . . . . . . . . . 4-11
4.2.32
Number of CLLM frames transmitted. . . . . . . . . . . . . . . . . . . . 4-11
4.2.33
Q.922 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.2.34
Q922 Tx retransmissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.2.35
Q922 Release indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.2.36
Q922 Establish indications . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.2.37
Q922 Data link established . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.2.38
Q922 Tx Iframe Q discards . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.2.39
Q922 Rx frames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.2.40
Q922 Tx frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.2.41
Q922 Rx bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.2.42
Q922 Tx bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.2.43
Q.933 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.2.44
Q933 Setup success rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.2.45
Q933 Tx setup messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4. 3
4.2.46
Q933 Rx setup messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.2.47
Q933 Tx call proceeding messages . . . . . . . . . . . . . . . . . . . . . 4-14
4.2.48
Q933 Rx call proceeding messages . . . . . . . . . . . . . . . . . . . . 4-15
4.2.49
Q933 Tx connect messages . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
4.2.50
Q933 Rx connect messages . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
4.2.51
Q933 Tx release messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
4.2.52
Q933 Rx release messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
4.2.53
Q933 Tx release complete messages . . . . . . . . . . . . . . . . . . . 4-15
4.2.54
Q933 Rx release complete messages . . . . . . . . . . . . . . . . . . . 4-16
4.2.55
Q933 Tx disconnect messages . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.2.56
Q933 Rx disconnect messages . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.2.57
Q933 Tx status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.2.58
Q933 Rx status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.2.59
Q933 Tx status enquiry messages. . . . . . . . . . . . . . . . . . . . . . 4-16
4.2.60
Q933 Rx status enquiry messages . . . . . . . . . . . . . . . . . . . . . 4-17
4.2.61
Q933 Protocol timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
4.2.62
Resetting the Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Displaying Frame Relay Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

4.3.1
Port Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
4.3.2
Number of bad frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.3.3
Number of underruns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.3.4
Number of retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.3.5
Number of restarts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.3.6
Number of frames discarded (overrun) . . . . . . . . . . . . . . . . . . 4-20
4.3.7
Number of octets discarded (bad) . . . . . . . . . . . . . . . . . . . . . . 4-20
4.3.8
Number of octets discarded (overrun) . . . . . . . . . . . . . . . . . . . 4-21
4.3.9
PVC Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
4.3.10
Number of errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
4.3.11
4.3.12
Number of invalid frames discarded. . . . . . . . . . . . . . . . . . . . . 4-22
4.3.13
4.3.14
Number of invalid octets discarded . . . . . . . . . . . . . . . . . . . . . 4-22
4.3.15
4.3.16
Number of compressor errors . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
4.3.17
Number of channel overflow errors . . . . . . . . . . . . . . . . . . . . . 4-23
4.3.18
Number of channel abort errors . . . . . . . . . . . . . . . . . . . . . . . . 4-23
4.3.19
Number of channel sequence errors . . . . . . . . . . . . . . . . . . . . 4-24
4.3.20
Transparent PVC Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
4.3.21
Group Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
4.3.22
Sorter overruns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
4.3.23
Sorter window overflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Memotec Inc.
4. 4
Memotec Inc.
4.3.24
Sorter timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
4.3.25
Sorter rejected cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
4.3.26
SVC Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
4.3.27
Number of errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
4.3.28
4.3.29
Number of frames discarded (CRC) . . . . . . . . . . . . . . . . . . . . 4-27
4.3.30
4.3.31
Number of octets discarded (CRC) . . . . . . . . . . . . . . . . . . . . . 4-27
4.3.32
4.3.33
Q.922 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
4.3.34
Q922 Invalid Rx sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
4.3.35
Q922 Missing control blocks . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
4.3.36
Q922 Rx Ack expiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
4.3.37
Q922 Tx Ack expiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Displaying Frame Relay States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

4.4.1
Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
4.4.2
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
4.4.3
Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
4.4.4
Speed used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
4.4.5
Modem signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
4.4.6
State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
4.4.7
Q922 state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
4.4.8
Continuous Display of Port States . . . . . . . . . . . . . . . . . . . . . . 4-33
4.4.9
PORT#. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
4.4.10
PROTOCOL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
4.4.11
INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
4.4.12
SPEED (BPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
4.4.13
MODEM SIGNALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
4.4.14
STATE DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
4.4.15
PVC Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
4.4.16
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
4.4.17
Information signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
4.4.18
DLCI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
4.4.19
Remote unit name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
4.4.20
State & Delay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
4.4.21
Transparent PVC States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
4.4.22
Continuous Display of PVC States . . . . . . . . . . . . . . . . . . . . . 4-38
4.4.23
SVC Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
4.4.24
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
4.4.25
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
4.4.26
Information signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
4. 5
4.4.27
Speed used (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
4.4.28
DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
4.4.29
State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Capturing PVCR Frame Length. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Chapter 5: Frame Relay over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5. 1
About Frame Relay over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5. 2
NetPerformer Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5. 3
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5. 4
5. 5
5.3.1
Global Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.3.2
PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Example Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

5.4.1
Local Unit Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.4.2
Remote Unit Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.4.3
Frame over IP, source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.4.4
Frame over IP, destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.4.5
Frame over IP, port number . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.4.6
Frame over IP, precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.4.7
Use a forced route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.4.8
Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.4.9
Next hop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Chapter 6: SE/PORT Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6. 1
6. 2
FR-NET Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

6.1.1
Fallback speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6.1.2
Frame delay (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.1.3
Management interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.1.4
Congestion flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
6.1.5
Enquiry timer (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
6.1.6
CLLM function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
6.1.7
Reference port for conditional LMI . . . . . . . . . . . . . . . . . . . . . . . 6-5
6.1.8
Drop signals on LMI down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
FR-USER Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

6.2.1
Report cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
6.2.2
SVC address type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
6.2.3
SVC network address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
6.2.4
SVC max Tx Ack timeout T200 . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
6.2.5
SVC inactive timeout T203. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Memotec Inc.
6.2.6
SVC setup timeout T303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
6.2.7
SVC disconnect timeout T305 . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
6.2.8
SVC release timeout T308. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
6.2.9
SVC call proceeding timeout T310 . . . . . . . . . . . . . . . . . . . . . 6-11
6.2.10
SVC status enquiry timeout T322 . . . . . . . . . . . . . . . . . . . . . . 6-12
Chapter 7: SE/PVC Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

7. 1
7. 2
Memotec Inc.
About SE/PVC Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . 7-2

7.1.1
PVC number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.1.2
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
PVCR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

7.2.1
Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
7.2.2
DLCI address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
7.2.3
Committed Information rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
7.2.4
Burst Information rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
7.2.5
Remote unit name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
7.2.6
Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
7.2.7
Delay before call activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
7.2.8
Delay before call deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
7.2.9
Call activation timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
7.2.10
Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
7.2.11
Timeout (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
7.2.12
Number of retransmission retries. . . . . . . . . . . . . . . . . . . . . . . . 7-9
7.2.13
Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
7.2.14
IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
7.2.15
Subnet mask (number of bits) . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
7.2.16
NAT enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
7.2.17
NAT rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
7.2.18
NAT side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
7.2.19
IP RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
7.2.20
IP RIP TX/RX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
7.2.21
IP RIP authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
7.2.22
IP RIP password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
7.2.23
OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
7.2.24
IP multicast active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
7.2.25
IP multicast protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
7.2.26
IPX RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
7.2.27
IPX SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
7.2.28
IPX network number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
7.2.29
BRG connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
7.2.30
Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
7. 3
7. 4
7. 5
7.2.31
Broadcast group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
7.2.32
Maximum number of voice channels . . . . . . . . . . . . . . . . . . . . 7-18
7.2.33
Maximum Voice Channels If High Priority Data . . . . . . . . . . . . 7-19
7.2.34
Use this port as default gateway . . . . . . . . . . . . . . . . . . . . . . . 7-20
7.2.35
Redundant link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
RFC1490 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21

7.3.1
Frame size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
7.3.2
IP connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
7.3.3
IPX connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
7.3.4
LLC connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
MULTIPLEX Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23

7.4.1
Remote PVC number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
7.4.2
Class number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
TRANSP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24

7.5.1
User port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
7.5.2
Network port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
7.5.3
User DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
7.5.4
Network DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Memotec Inc.
Memotec Inc.
1
NetPerformer Frame Relay Support
Memotec Inc.
1-1
WAN Frame Relay
1.1
Packet Mode Interface

Frame Relay is a packet mode interface specification that provides a signaling and data
transfer mechanism between data equipment and a network. It allows LANs located far
apart from each other to be interconnected with a high-speed WAN protocol.
Each frame (or packet) contains header information that influences the routing of the data
to the desired destination. The Memotec NetPerformer can concentrate Frame Relay
traffic originating from multiple devices, local or remote, onto a single Frame Relay
connection. The NetPerformer also supports Frame Relay over IP. This permits using the
NetPerformer PVCR protocol to integrate voice and data over the Internet. With FRoIP,
the NetPerformer routes a PVC connection over IP instead of Frame Relay
A Frame Relay network uses virtual circuits, which are logical paths established between
two network access points. A Permanent Virtual Circuit (PVC) is established using
administrative procedures, typically a network manager who configures the network using
a network management facility. This type of virtual circuit remains in the network until
the network manager removes it.
A Switched Virtual Circuit (SVC) is dynamically established through an exchange of call
control messages across the user/network interface (UNI). This type of circuit is
maintained until a user at one end of the call initiates a call termination. The circuit is then
disconnected using call control messages exchanged at the UNI.
One or more Frame Relay connections can be configured on a digital link (T1 or E1) by
configuring a certain number of timeslots with the FR-USER protocol. PVCs can then be
assigned to these virtual Frame Relay ports for access to remote units. Frame Relay over a
digital link provides an increased number of possible Frame Relay connections on the
NetPerformer unit.
1-2
Memotec Inc.
1.2
Permanent Virtual Circuits

The NetPerformer supports the Frame Relay interface using multiple PVCs. These PVCs
are linked to different locations, bundled and attached to the same physical connection to
the Frame Relay network. Frame Relay packets are routed over the network via the PVCs
according to the address information embedded in the frame header.
NOTE:
No error correction is done by the network. The responsibility to retransmit is

left to the user equipment.
The address information in the frame header is known as the Data Link Connection
Identifier (DLCI), which is provided by the carrier. A separate DLCI address is required
for each PVC used by the NetPerformer. The NetPerformer encloses the DLCI address,
representing the destination of the frame, in a two-byte field header. The carrier can then
route the frame to the proper destination.
The carrier also provides notification of any congestion conditions in the network by
setting the Forward and Backward Explicit Congestion Notification bits (FECN and
BECN) in the header of the routed frame. The NetPerformer monitors these bits in the
header frame to determine when congestion control is required. This is particularly
important for Voice Over Frame Relay transmissions, where the NetPerformer can
perform voice fallback based on the status of the BECN bits.
On each Frame Relay port of the NetPerformer, two DLCI addresses are reserved for the
Frame Relay Management Interface Protocol. DLCI address 1023 is used for the LMI
(Local Management Interface) protocol, and DLCI address 0 is used for the ANNEX-D
protocol, which is part of the ANSI standard, or the Q.933 protocol, which is part of the
CCITT standard. These management interface protocols provide a polling mechanism for
requesting status information on the currently active PVC in the network.
Memotec Inc.
1-3
WAN Frame Relay
1.3
Switched Virtual Circuits

The NetPerformer also supports Voice over Frame Relay through SVCs. The benefits of
SVCs are:
They are activated only when required,
Reduced configuration time,
Predictable quality of service.
For the more complex network topologies such as mesh and dual star, the dynamic call
control provided by SVCs reduces the number of connections which must be maintained
by the network. Only circuits for active channels need to be established. With SVC
connections, the network can support any-to-any connectivity among all nodes without
having to maintain virtual circuits for all possible node-to-node connections at all times.
On the NetPerformer, SVCs provide support of voice connections only. The voice
connections can be defined for switched or autodial line activation. Predefined voice port
connections are not supported. You can configure one voice channel per SVC: each call
requires its own SVC, and no SVCs can be shared. To prevent data frames with the same
destination from using the same SVC, the destination name is associated with a unique
numeric extension.
When configuring the NetPerformer for SVCs, you must define:
A Frame Relay port with the FR-USER protocol, using the Setup Slot menu,
A Voice Mapping Table entry, using the Setup/MAP menu.
You must also observe certain conditions:
the Management Interface parameter for the FR-USER port must be set to
ANNEX-D,
The Link Down Busy parameter must be set to NO on all voice ports that may use
SVCs to reach their destination,
If you are using SVCs, but not fax or modem communications, the Fax/Modem
Relay parameter on the voice port must be set to NONE.
If you are using both SVCs and fax/modem, the Maximum Fax/Modem Rate
parameter must be set to the maximum speed that the voice port may require for
fax or modem communications.
Configuration details are provided in FR-USER Port Configuration Parameters on
page 3-5, and in the Digital Voice module of this document series.
All NetPerformers with SVC support also support PVC call setup operation. This allows
for a gradual phasing in of SVCs in legacy networks. PVCs and SVCs can be mixed and
matched on the same unit or port. If required, the network administrator can continue to
place and accept calls from nodes that support only PVC-type call setup. If a PVC
connection has been established between the NetPerformer and a particular destination, an
SVC can nevertheless be set up to improve the quality of service and simplify SVC
management. The NetPerformer tries to set up an SVC whenever an SVC type is entered
in the Voice Mapping Table, regardless of whether a PVC has already been defined for
1-4
Memotec Inc.
that destination.
Frame Relay access can be provided on more than one port. In some cases, this is because
the Frame Relay supplier can provide only 56K or T1 access, and no other service levels.
The NetPerformer supports two SVC addressing types: X.121 and E.164. If more than one
Frame Relay port is configured for the same addressing type, the ports will send SVC
setup calls in turn, thus distributing the load.
1.4
Frame Relay Encapsulation

The NetPerformer also supports the following Frame Relay encapsulation techniques:
X.25 encapsulation, which permits connection of an X.25 device to a serial port.
Refer to the chapter X.25 Protocol in the Legacy Data module of this document series.
Frame Relay over IP (FRoIP), to route a PVC connection over IP instead of
Frame Relay. Turn to the chapter Frame Relay over IP on page 5-1.
Memotec Inc.
1-5
WAN Frame Relay
1-6
Memotec Inc.
2
Planning the Configuration
Memotec Inc.
2-1
WAN Frame Relay
2.1
Selecting the Port Protocol

Any serial port or digital data channel on the NetPerformer can be used as a Frame Relay
User (FR-USER) or Frame Relay Network (FR-NET) port. These protocols are set using
the Protocol parameter of the SETUP/PORT or SETUP/SLOT menu.
Use the FR-USER protocol when the port connects with a Frame Relay network.
Refer to FR-USER Port Configuration Parameters on page 3-5 for details
Use the FR-NET protocol when it connects with a Frame Relay end-user device.
Refer to FR-NET Channel Configuration Parameters on page 3-4.
2.2
Selecting the PVC Operating Mode

In addition to setting the Frame Relay protocol on the port, if you are using PVCs in your
network you must configure all PVCs. Refer to PVC Configuration Parameters on
page 3-8.
The NetPerformer has a minimum pool of 96 PVCs, each requiring a DLCI address and
identification of the port(s) it uses. The PVC mode must also be determined, using the
Mode parameter. The following modes are available on the NetPerformer base product
when the Voice transport method (a global parameter) is set to POWERCELL:
PVCR: The PVC is used over a Frame Relay network to transport data using the
Memotec variable cell relay technology to access a remote NetPerformer. The
local NetPerformer port must be a Frame Relay port (FR-USER or FR-NET protocol).
NOTE:
PVCR mode is the preferred PVC operating mode when linking two NetPerformer units together across a Frame Relay network.
RFC1490: The PVC is used over a Frame Relay network to access an RFC1490compatible FRAD (Frame Relay Access Assembler/Disassembler). No fragmentation or data compression is performed. The local NetPerformer port must be a
Frame Relay port (FR-USER or FR-NET protocol).
MULTIPLEX: The PVC is used to multiplex data coming from a Frame Relay
end-user device. The local port must be set to the FR-NET protocol.
BROADCAST: The PVC is used to send broadcast frames to the multicast
server (the Frame Relay switch). The DLCI you define for this PVC is the Mdlci.
The local NetPerformer port must be an analog voice port. Voice broadcasting
concepts are described in the Analog Voice module of this document series.
2-2
Memotec Inc.
NOTE:
Broadcast mode is available only on NetPerformer models that support voice/

fax transmissions.
TRANSP: The PVC is used to switch data coming from one end-user device
directly to the network and the destination end-user device without alteration on
the frame. For this mode the PVC uses either two Frame Relay network ports
(FR-NET protocol) or one Frame Relay user port (FR-USER protocol) and one
network port.
2.3
Other PVC Parameters

The Committed Information Rate (CIR) should also be set for each PVC, based on the CIR
provided by the carrier. The information rate used for PVCs can be fine-tuned using the
extended parameter IRFACTOR (Information Rate Factor).
Depending on the mode chosen for the PVC, other configurable parameters include the
Burst Information Rate, Remote Unit, Timeout, Retries and parameters controlling IP and
IPX routing. All of these parameters are available from the SETUP/PVC menu. Refer to
PVC Configuration Parameters on page 3-8 for details.
Memotec Inc.
2-3
WAN Frame Relay
2.4
Example Application
Figure 2-1 provides an example of a NetPerformer in a Frame Relay application, and
indicates the values of the some of the port and PVC configuration parameters.
CHICAGO
PVC 2:
Mode: PVCR
DLCI: 100
Remote unit: Montreal
CIR: 56K
PVC 1:
Mode: MULTIPLEX
DLCI: 100
Remote PVC: 1
2
MONTREAL
Frame Relay
Network
Router
FR-NET
2 Mbps
1 FR-USER
512 Kbps
PVC 2:
Mode: MULTIPLEX
DLCI: 101
Remote unit: New York
Remote PVC: 1
PVC 3:
Mode: PVCR
DLCI: 100
Remote unit: Chicago
CIR: 56K
FR
25 -U
6 SE
Kb R
ps
PVC 4:
Mode: PVCR
DLCI: 101
Remote unit: New York
CIR: 56K
PVC 5:
Mode: TRANSP
User DLCI: 102
Network DLCI: 102
CIR: 56K
User Port: 1
Network Port: 2
Router
R
SE s
-U Kbp
R
F 56
2
NEW YORK
PVC 1:
Mode: MULTIPLEX
DLCI: 100
Remote unit: Chicago
Remote PVC: 1
FR-NET
1 Mbps
Router
DLCI: 102
PVC 1:
Mode: MULTIPLEX
DLCI: 101
Remote PVC: 2
FR-NET
1 Mbps
Router
PVC 2:
Mode: PVCR
DLCI: 101
CIR: 56K
LOS ANGELES
Figure 2-1: PVC Settings for Frame Relay Application
2-4
Memotec Inc.
2.5
Setting the SVCs

For outgoing calls, the SVC call setup type is determined by the Voice Mapping Table
entry. The MAP table configuration, using the SETUP/MAP menu, includes a parameter
that specifies SVC or PVC call setup. No negotiation between nodes is required. For
details on the parameters required, refer to the Digital Voice module of this document
series.
SVC addressing and response parameters are determined by the Frame Relay port
configuration (FR-USER protocol). Consult FR-USER Port Configuration Parameters
on page 3-5.
For successful SVC setup, the FR-USER port and voice port configurations must meet
certain conditions:
the Management Interface parameter for the FR-USER port must be set to
ANNEX-D,
SVCs to reach their destination,
If you are using both SVCs and fax/modem, the Maximum Fax/Modem Rate
parameter must be set to the maximum speed that the voice port may require for
fax or modem communications.
NOTE:
An SVC call placed to a non-SVC node will be rejected by the network, since
the Q.922/Q.933 interface is not active at the UNI of the called node.
Configuration details for the voice port parameters are provided in the Digital Voice
module of this document series.
Memotec Inc.
2-5
WAN Frame Relay
2.6
NNI System Parameters

The table below shows the equivalencies between the Frame Relay port parameter names
used on the NetPerformer and the NNI system parameter names used in the Frame Relay
Forum Document FRF.2.1 (July, 1995): Differences between each pair of parameters are
also noted.
NNI System
Parameter
NetPerformer
Parameter
Differences
N391
Report Cycle
The NNI parameter range is 1-255, on the NetPerformer it is 1-256.
N392
N/A
This is the maximum number of errors that can

occur during monitored events before the user
or network side procedures are declared inactive. On the NetPerformer this parameter is not
configurable, and is permanently set to 3.
N393 (or NT3)
N/A
This is the number of monitored events. On the

NetPerformer this parameter is not configurable, and is permanently set to 4.
T391
Enquiry Timer on
FR-USER port
The NNI parameter range is 5-30 seconds, on

the NetPerformer it is 1-30 seconds.
T392
Enquiry Timer on
FR-NET port
The NNI parameter default is 15 seconds, on

the NetPerformer it is 10 seconds.
Table 2-1: Equivalencies Between NetPerformer Frame Relay Port Parameters and NNI System
Parameters
2-6
Memotec Inc.
3
Frame Relay Configuration
Memotec Inc.
3-1
WAN Frame Relay
3.1
Frame Relay Port Configuration Parameters

The PORT or SLOT submenu of the SETUP console command includes all parameters
required to configure a Frame Relay port.
Unit ID>
(main prompt)
Setup (SE)
Port (PO)
FR-NET
Slot (SL)
FR-USER
Channel (CH)
FR-NET
FR-USER
Figure 3-1: SETUP/PORT and SETUP/SLOT/CHANNEL Paths on the CLI Tree for FR-NET and
FR-USER Protocols
If you are using SNMP, the required configuration variables are grouped under the ifwan
category. For text-based configuration the [ifwan#] heading is used, where # represents
the number of the port or channel.
Console
SE/PORT (serial port)

SE/SLOT (digital channel
or dual serial port)
SNMP
ifwan (category)
Text-based Config
[ifwan#] (heading)
A Frame Relay port can be configured on a serial port (including ports built into the base
unit and ports on the Dual Serial Port interface card) or a channel on a digital interface
card.
To configure a built-in serial port on the base unit as a Frame Relay port:
- Enter the menu sequence: SE PORT
- Select the Port number
3-2
Memotec Inc.
- Set the Protocol to:

FR-NET if the port connects to a Frame Relay end-user device
FR-USER if the port connects to a Frame Relay network
- Change the other port parameters from their default values, if desired.
To configure a digital channel or a serial port on the Dual Serial interface card as
a Frame Relay port:
- Enter the menu sequence: SE SLOT
- Select the Slot number
- On an E1/T1 (dual framer) interface only: select the Port number
- On a digital interface only: enter CHANNEL at the Item prompt
- Select the Channel number, e.g. 102, where the first digit indicates the slot or
span, and the last two digits indicate the channel
- Set the Protocol to:
FR-NET if the port connects to a Frame Relay end-user device
FR-USER if the port connects to a Frame Relay network
- Change the other channel parameters from their default values, if desired.
SE/PORT/#/FRNET example:
Setting the
Protocol
3.1.1
SDM-9230>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,
def:BRIDGE) ? PORT
Port number (ETH1/ETH2/CSL/1,def:1) ?
PORT 1> Protocol (def:PVCR) ? FR-NET
...
Protocol
Console
Protocol
SNMP
ifwanProtocol
Text-based Config
[ifwan#] Protocol
This parameter defines the operating protocol for the data port. Use the FR-NET or FRUSER values to define the port as a Frame Relay port. The other values of this parameter
are described in the appendix SE/PORT/#/PVCR Configuration Parameters in the
WAN/Leased Lines module of this document series.
Any serial port or digital data channel can be used as a Frame Relay port.
Set the port Protocol to FR-NET when the port connects to a Frame Relay enduser device.
Set the Protocol to FR-USER when the port connects to a Frame Relay network.
Memotec Inc.
3-3
WAN Frame Relay
3.1.2
FR-NET Port Configuration Parameters

A FR-NET port connects to a Frame Relay end-user device. When you define a serial port
as FR-NET, the following port parameters are listed on the console:
SE/PORT/#/FRNET example
SDM-9230>SE
SETUP
PHONE/
def:BRIDGE) ? PORT
Port number (ETH1/ETH2/CSL/1,def:ETH1) ? 1
PORT 1> Protocol (def:OFF) ? FR-NET
PORT 1> Interface...............................DCE-V35
PORT 1> Clocking mode (def:INTERNAL) ?
PORT 1> Port speed (bps) (1200-6144000,def:56000) ?
PORT 1> Fallback speed (def:ENABLE) ?
PORT 1> Frame delay (ms) (def:0.0) ?
PORT 1> Management interface (def:LMI) ?
PORT 1> Congestion flow control (def:ON) ?
PORT 1> Enquiry timer (s) (1-30,def:10) ?
PORT 1> CLLM function (def:OFF) ?
PORT 1> Cell Packetization (def:YES) ?
PORT 1> Maximum number of voice channels (0-10000,def:10000) ?
PORT 1> Maximum Voice Channels If High Priority Data (010000,def:10000) ?
PORT 1> Reference port for conditional LMI (def:0) ?
PORT 1> Drop signals on LMI down (def:NO) ?
PORT 1> Redundant link (def:NO) ?
The parameters Interface, Clocking Mode, Port Speed, Cell Packetization, Maximum Number of Voice Channels, Maximum Voice Channels If High Priority
Data and Redundant link are common to other WAN/user ports, and are
described in the appendix SE/PORT/#/PVCR Configuration Parameters in
the WAN/Leased Lines module of this document series.
The other parameters set specific Frame Relay characteristics, and are detailed in
the appendix SE/PORT Configuration Parameters on page 6-1.
3.1.3
FR-NET Channel Configuration Parameters

When you define a digital channel as FR-NET, the following parameters are listed on the
console:
SE/SLOT/#/
CHANNEL/FRNET example
3-4
SDM-9230>SE
SETUP
PHONE/
def:BRIDGE) ? SLOT
SLOT> Slot number (1/2/3,def:1) ?
Port number (1/2,def:1) ?
Memotec Inc.
Item (LINK/CHANNEL,def:LINK) ? CHANNEL

SLOT> Channel Number (101-124/ALL,def:102) ? 103
PORT 103> Protocol (def:OFF) ? FR-NET
PORT 103> Timeslot (def:3) ?
PORT 103> Number of consecutive timeslots (1-22,def:1) ?
PORT 103> DS0 speed (bps) (def:64000) ?
PORT 103> Reference port for conditional LMI (def:0) ?
Timeslot, Number of consecutive timeslots and DS0 speed (bps) are described in
the appendix SE/SLOT/#/CHANNEL Configuration Parameters in the Digital Data module of this document series.
Management interface, Congestion flow control, Enquiry timer (s), CLLM function, Reference port for conditional LMI and Drop signals on LMI down are
described in FR-NET Protocol on page 6-2.
Cell Packetization, Maximum number of voice channels and Maximum Voice
Channels If High Priority Data are described in the appendix SE/PORT/#/
PVCR Configuration Parameters in the WAN/Leased Lines module of this
document series.
3.1.4
FR-USER Port Configuration Parameters

As mentioned earlier, a FR-USER port connects to a Frame Relay network. When you
define a serial port as FR-USER, the following port parameters are listed on the console:
SE/PORT/#/FRUSER example
Memotec Inc.
SDM-9230>SE
SETUP
PHONE/
def:BRIDGE) ? PORT
Port number (ETH1/ETH2/CSL/1,def:ETH1) ? 1
PORT 1> Protocol (def:OFF) ? FR-USER
PORT 1> Interface...............................DCE-V35
PORT 1> Clocking mode (def:INTERNAL) ?
PORT 1> Port speed (bps) (1200-6144000,def:56000) ?
PORT 1> Fallback speed (def:ENABLE) ?
PORT 1> Report cycle (1-256,def:6) ?
3-5
WAN Frame Relay

PORT 1> SVC address type (def:NONE) ?
PORT 1> Redundant link (def:NO) ?
Interface, Clocking Mode, Port Speed, Cell Packetization, Maximum Number of

Voice Channels, Maximum Voice Channels If High Priority Data and Redundant
link are common to other WAN/user ports, and are described in the appendix SE/
PORT/#/PVCR Configuration Parameters in the WAN/Leased Lines module of this document series.
Fallback Speed, Management interface, Congestion flow control, Enquiry timer
(s), CLLM function, and Drop signals on LMI down are described in FR-NET
Protocol on page 6-2.
NOTE:
The Management interface of a FR-USER port must be set to ANNEX-D when

using SVCs.
The other parameters are unique to FR-USER ports, and are detailed in FRUSER Protocol on page 6-8.
3.1.5
FR-USER Channel Configuration Parameters

When you define a digital channel as FR-USER, the following parameters are listed on the
console:
SE/SLOT/#/
CHANNEL/FRUSER example
3-6
SDM-9230>SE
SETUP
PHONE/
def:BRIDGE) ? SLOT
SLOT> Slot number (1/2/3,def:1) ?
Item (LINK/CHANNEL,def:CHANNEL) ?
SLOT> Channel Number (101-124/ALL,def:103) ? 104
PORT 104> Protocol (def:OFF) ? FR-USER
PORT 104> Timeslot (def:4) ?
PORT 104> Number of consecutive timeslots (1-21,def:1) ?
PORT 104> DS0 speed (bps) (def:64000) ?
PORT 104> Report cycle (1-256,def:6) ?
PORT 104> Maximum Voice Channels If High Priority Data (0-
Memotec Inc.
10000,def:10000) ?
PORT 104> SVC address type (def:NONE) ?
Timeslot, Number of consecutive timeslots and DS0 speed (bps) are described in
the appendix SE/SLOT/#/CHANNEL Configuration Parameters in the Digital Data module of this document series.
Management interface, Congestion flow control, Enquiry timer (s), CLLM function and Drop signals on LMI down are described in FR-NET Protocol on
page 6-2.
Report cycle and SVC address type are described in FR-USER Protocol on
page 6-8.
Cell Packetization, Maximum number of voice channels and Maximum Voice
Channels If High Priority Data are described in the appendix SE/PORT/#/
PVCR Configuration Parameters in the WAN/Leased Lines module of this
document series.
Memotec Inc.
3-7
WAN Frame Relay
3.2
PVC Configuration Parameters

The PVC submenu of the SETUP console command includes all parameters required to
configure a PVC.
Unit ID>
(main prompt)
Setup (SE)
PVC (PV)
PVCR
RFC1490
TRANSP MULTIPLEX . . .
Figure 3-2: SETUP/PVC Path on the CLI Tree
If you are using SNMP, the required configuration variables are grouped under the pvc
category. For text-based configuration the [pvc#] heading is used, where # represents the
number of the PVC.
Console
SE, PVC
SNMP
pvc (category)
Text-based Config
[pvc#] (heading)
Enter the menu sequence: SE PVC.

Select the PVC number of the PVC you want to configure.
Set the Mode parameter.
Change the other PVCR parameters from their default values, if desired.
SE/PVC/PVCR
example:
setting the
Mode
SDM-9230>SE
SETUP
PHONE/
def:BRIDGE) ? PVC
PVC number (1-300,def:1) ?
PVC 1> Mode (def:OFF) ? RFC1490
NOTE:
3-8
Details on the PVC number and Mode parameters are provided in the appendix SE/PVC Configuration Parameters on page 7-1.
Memotec Inc.
The following PVC modes are available on the NetPerformer base product when the Voice
transport method is set to POWERCELL:
PVCR (see PVCR PVC Configuration Parameters on page 3-10)
RFC1490 (see RFC1490 PVC Configuration Parameters on page 3-10)
MULTIPLEX (see Multiplex PVC Configuration Parameters on page 3-11)
BROADCAST (see Broadcast PVC Configuration Parameters on page 3-12)
TRANSP (see Transparent PVC Configuration Parameters on page 3-13).
When the Voice transport method is set to SIP VoIP, only the RFC1490 PVC mode is
available.
When the GSM A-bis/ter licensed software option is installed, the mode can be set to GSM
in addition to the modes listed above. Refer to the GSM Support module of this
document series for information on this PVC mode.
When the ATM licensed software option is installed, the following PVC modes are
available in addition to the modes listed above:
ATMPVCR, ATM-MULTIPLEX, ATMPPP, FRF.8, RFC1483
These ATM PVC modes are explained further in the ATM Option module of this
document series.
Memotec Inc.
3-9
WAN Frame Relay
3.2.1
PVCR PVC Configuration Parameters

A PVCR PVC is used over a Frame Relay network to access a remote NetPerformer using
PowerCell technology. The local NetPerformer port must be a Frame Relay port (FRUSER or FR-NET protocol). When you define a PVC in PVCR mode, the following PVC
parameters are listed on the console:
SE/PVC/PVCR
example:
DEDICATED
Type
SDM-9230>SE
SETUP
PHONE/
def:BRIDGE) ? PVC
PVC number (1-300,def:1) ?
PVC 1> Mode (def:PVCR) ?
PVC 1> Port (def:1) ?
PVC 1> DLCI address (0-1022,def:0) ? 101
PVC 1> Committed Information rate (4000-6144000,def:56000) ?
PVC 1> Burst Information rate (4000-6144000,def:56000) ?
PVC 1> Remote unit name (def:) ? CHICAGO-9230
PVC 1> Type (def:DEDICATED) ?
PVC 1> Timeout (ms) (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> NAT enable (def:NO) ?
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> IPX RIP (def:DISABLE) ?
PVC 1> IPX SAP (def:DISABLE) ?
PVC 1> IPX network number (def:00000000) ?
PVC 1> BRG connection (def:NO) ?
PVC 1> Filter (def:ALL) ?
PVC 1> Broadcast group (def:NO) ?
PVC 1> Maximum number of voice channels (0-10000,def:10000) ?
PVC 1> Maximum Voice Channels If High Priority Data (010000,def:10000) ?
PVC 1> Use this port as default gateway (def:NO) ?
PVC 1> Redundant link (def:NO) ?
Details on these parameters are provided in PVCR Mode on page 7-4.
3.2.2
RFC1490 PVC Configuration Parameters

An RFC1490 PVC is used over a Frame Relay network to access an RFC1490-compatible
FRAD (Frame Relay Access Assembler/Disassembler). No fragmentation or data
compression is performed. The local NetPerformer port must be a Frame Relay port (FRUSER or FR-NET protocol).
3-10
Memotec Inc.
When you define a PVC in RFC1490 mode, the following PVC parameters are listed on
the console:
SE/PVC/
RFC1490
example
SDM-9230>SE
SETUP
PHONE/
def:BRIDGE) ? PVC
PVC number (1-300,def:1) ? 2
PVC 2> Mode (def:OFF) ? RFC1490
PVC 2> DLCI address (0-1022,def:0) ? 103
PVC 2> IP address (def:000.000.000.000) ?
PVC 2> Subnet mask (number of bits) (0-32,def:8) ?
{255.000.000.000}
PVC 2> NAT enable (def:NO) ?
PVC 2> Frame size (128-8192,def:1500) ?
PVC 2> IP RIP (def:V1) ? V2 MULTICAST
PVC 2> IP RIP TX/RX (def:DUPLEX) ? TX ONLY
PVC 2> IP RIP Authentication (def:NONE) ? SIMPLE
PVC 2> IP RIP Password (def:) ?
PVC 2> OSPF (def:DISABLE) ?
PVC 2> IP multicast active (def:NO) ?
PVC 2> IPX RIP (def:DISABLE) ?
PVC 2> IPX SAP (def:DISABLE) ?
PVC 2> IPX network number (def:00000000) ?
PVC 2> BRG connection (def:NO) ? YES
PVC 2> IP connection (def:YES) ?
PVC 2> IPX connection (def:YES) ?
PVC 2> LLC connection (def:YES) ?
PVC 2> Filter (def:ALL) ?
PVC 2> Use this port as default gateway (def:NO) ?
Port, DLCI address, Committed Information rate, Burst Information rate,

Remote unit name, IP address, Subnet mask (number of bits), NAT enable, the IP
RIP parameters, OSPF, the IP multicast active, the IPX parameters, BRG connection, Filter and Use this port as default gateway are described in PVCR
Mode on page 7-4.
The other parameters set specific characteristics for an RFC1490 PVC connection. Refer to RFC1490 Mode on page 7-21 for details.
3.2.3
Multiplex PVC Configuration Parameters

A Multiplex PVC is used to multiplex data coming from a Frame Relay end-user device.
The local NetPerformer port must be set to the FR-NET protocol (or X.25, in the case of
X.25 encapsulation to Frame Relay).
A Multiplex PVC configuration requires just 1 PVC at the switch, whereas a Transparent
Memotec Inc.
3-11
WAN Frame Relay
PVC configuration requires 2 PVCs. A Multiplex solution allows the connection to carry
data from multiple sources, with multiplexing performed at the local site, and
demultiplexing at the remote site.
NOTE:
When a Multiplex PVC is connected on a FR-NET port, the port does not tag
the DLCI as active unless the connection to the remote site is up.
When you define a PVC in Multiplex mode, the following PVC parameters are listed on
the console:
SE/PVC/
MULTIPLEX
example
SDM-9230>SE
SETUP
PHONE/
def:BRIDGE) ? PVC
PVC 4> Mode (def:OFF) ? MULTIPLEX
PVC 4> DLCI address (0-1022,def:0) ?
PVC 4> Remote PVC number (1-300,def:4) ?
PVC 4> Class number (def:3) ?
PVC 4> Compression (def:YES) ?
Port, DLCI address, Committed Information rate, Burst Information rate and
Remote unit name and Compression are described in PVCR Mode on page 7-4.
NOTE:
When used for X.25 encapsulation to Frame Relay, the Port parameter of a
Multiplex PVC refers to the X.25 port (NetPerformer data port configured
with the X25 protocol). X25 encapsulation is activated when the Multiplex
PVC is associated with an X25 port.
The other parameters set specific characteristics for a Multiplex PVC connection,
and are described in MULTIPLEX Mode on page 7-23.
3.2.4
Broadcast PVC Configuration Parameters

A Broadcast PVC is used to send broadcast frames to the multicast server (the Frame
Relay switch). The DLCI you define for this PVC is the Mdlci. The local NetPerformer
port must be an analog voice port.
3-12
Memotec Inc.
NOTE:
Broadcast mode is available only on NetPerformer models that support voice/

fax transmissions.
When you define a PVC in Broadcast mode, the following PVC parameters are listed on
the console:
SE/PVC/
BROADCAST
example
SDM-9230>SE
SETUP
PHONE/
def:BRIDGE) ? PVC
PVC 5> Mode (def:OFF) ? BROADCAST
PVC 5> DLCI address (0-1022,def:0) ?
Port, DLCI address, Committed Information rate and Burst Information rate are
described in the section PVCR Mode on page 7-4.
There are no parameters which are unique to this PVC mode.
3.2.5
Transparent PVC Configuration Parameters

A Transparent PVC is used to switch data coming from one end-user device directly to the
network and the destination end-user device without alteration on the frame. For this mode
the PVC uses either two network ports (FR-NET protocol) or one Frame Relay user port
(FR-USER protocol) and one network port.
When you define a PVC in Transparent mode, the following PVC parameters are listed on
the console:
SE/PVC/
TRANSP
example
Memotec Inc.
SDM-9230>SE
SETUP
PHONE/
def:BRIDGE) ? PVC
PVC 6> Mode (def:OFF) ? TRANSP
PVC 6> User port (def:1) ?
PVC 6> Network port (def:1) ?
PVC 6> User DLCI (0-1022,def:0) ?
PVC 6> Network DLCI (0-1022,def:0) ?
3-13
WAN Frame Relay
Committed Information rate and Burst Information rate are described in PVCR
Mode on page 7-4.
The other parameters set specific characteristics for a Transparent PVC connection, and are detailed in TRANSP Mode on page 7-24.
3-14
Memotec Inc.
4
Frame Relay Connection Status
Memotec Inc.
4-1
WAN Frame Relay
4.1
About NetPerformer Frame Relay link status

NetPerformer Frame Relay link status information includes:
Current link counters, using the Display Counters (DC) command (see Displaying Frame Relay Counters on page 4-3)
Number of link errors that have occurred on all ports, PVCs, Port/PVC groups
and SVCs using the Display Errors (DE) command (see Displaying Frame
Relay Errors on page 4-18)
A static display of current status information concerning a specific Frame Relay
connection, using the Display States (DS) command (see Displaying Frame
Relay States on page 4-29)
A real-time display of Frame Relay port states, using the Display Port States
(DPORT) command (see Continuous Display of Port States on page 4-33)
A real-time display of Frame Relay PVC states, using the Display PVC States
(DPVC) command (see Continuous Display of PVC States on page 4-38)
Display of information concerning the length of frames sent over the Frame
Relay network via a WAN link, using the Display Port States (CL) command (see
Capturing PVCR Frame Length on page 4-41).
Unit ID>
(main prompt)
Display Counters
(DC)
Display Errors
(DE)
Display States
(DS)
Display Port
States (DPORT)
Display PVC
States (DPVC)
PORT SLOT PVC . . . PORT SLOT PVC . . . PORT SLOT PVC . . .
Capture Frame
Length (CL)
PORT
PVC
Figure 4-1: Frame Relay Statistics Commands in the CLI Tree
4-2
Memotec Inc.
4.2
Displaying Frame Relay Counters

The Display Counters (DC) command shows all counters stored in memory, including the
mean or peak values of transmitter and receiver rates on all ports, PVCs and SVCs.
The NetPerformer takes a snapshot of these counters every 5 seconds, and keeps this
information for a maximum of 2 minutes. Mean rates are calculated over the entire 2minute period, whereas peak rates are obtained by comparing all the snapshots taken. The
NetPerformer also keeps statistics on the number of frames and octets transmitted and
received on the ports, PVCs and SVCs. In addition, the Display Counters command
provides statistics that are specific to the Q.922 and Q.933 layers of SVC support.
To display the counters for Frame Relay connections:
Enter DC at the console command prompt.
At the Item prompt, enter the type of connection you want to inspect:
- PORT: To view the counters for all built-in serial ports (see next section).
- SLOT: To view the counters for all digital channels or dual serial ports on a
particular slot. Enter the Slot number at the prompt. The display for slot
counters is the same as that for port counters (see next section).
- PVC: To view the counters for all PVCs (see PVC Counters on page 4-4).
- SVC: To view the counters for all SVCs (see SVC Counters on page 4-8).
- Q922: To view the Q.922 counters (see Q.922 Counters on page 4-11).
- Q933: to view the Q.933 counters (see Q.933 Counters on page 4-13).
At the Counters prompt, select MEAN or PEAK counters.
On a unit installed with the ATM licensed software option, enter FR at the PVC
TYPE or SVC TYPE prompt.
For SNMP, all Frame Relay connection statistics are grouped under the categories shown
in the SNMP column of the table below.
Console
DC/PORT
DC/SLOT
DC/PVC
DC/GROUP
DC/SVC
Q922
SNMP
statIfwan
statIfwan
statPvc
statGrp
statSvc
stat (categories)
The same statistics are displayed for a built-in serial port, a port on the Dual Serial
interface card, and a digital channel.
4.2.1
Port Counters
If you select the port counters for the Display Counters command, a display like the
following will appear on the screen:
Memotec Inc.
4-3
WAN Frame Relay
DC/PORT
example
SDM-9380>DC
DISPLAY COUNTERS
Item (BOOTP/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/SLOT/SVC/
TIMEP,
def:Q933) ? PORT
Counters (MEAN/PEAK,def:MEAN) ?
Compression rate................................6.04 (M)
Decompression rate..............................6.18 (M)
PORT ETH> Transmitter rate......................0
kbps (M)
PORT ETH> Receiver rate.........................0
kbps (M)
PORT CSL> Transmitter rate......................0
% (M)
PORT CSL> Receiver rate.........................0
% (M)
PORT 1> Transmitter rate........................2
% (M)
PORT 1> Receiver rate...........................2
% (M)
PORT 1> Number of frames transmitted............4123392
PORT 1> Number of frames received...............4204532
PORT 1> Number of octets transmitted............422183940
PORT 1> Number of octets received...............446426291
% (M)
% (M)
% (M)
% (M)
The data port counters can be used to determine the efficiency of Frame Relay ports. For
details, refer to the description of the DC command in the chapter Checking WAN Link
Status in the WAN/Leased Lines module of this document series.
4.2.2
PVC Counters
If you select the PVC counters for the Display Counters command, a display like the
DC/PVC
example
4-4
SDM-9380>DC
DISPLAY COUNTERS
TIMEP,
def:TIMEP) ? PVC
PVC 1> Transmitter rate.........................0
% (M)
PVC 1> Receiver rate............................0
% (M)
PVC 1> Number of frames transmitted.............191994
PVC 1> Number of frames received................410810
PVC 1> Number of octets transmitted.............4220172
PVC 1> Number of octets received................20543433
Memotec Inc.
PVC
PVC
PVC
PVC
PVC
PVC
1>
1>
1>
1>
1>
1>
Number
Number
Number
Number
Number
Number
of
of
of
of
of
of
BECN
BECN
FECN
FECN
CLLM
CLLM
received..................0
transmitted...............0
received..................0
transmitted...............0
frames received...........0
frames transmitted........0

...
% (M)
% (M)
These counters can be used to determine the efficiency of Frame Relay PVCs:
4.2.3
Transmitter rate (M)

Console
SNMP
statPvcMeanTx
The average bandwidth usage for transmissions to the attached equipment. This statistic as
well as the other transmitter/receiver rate statistics are given as a percentage of the
available bandwidth.
4.2.4
Receiver rate (M)

Console
SNMP
Receiver rate (M)
statPvcMeanRx
The average bandwidth usage for data received from the attached equipment.
4.2.5
Transmitter rate (P)

Console
SNMP
statPvcPeakTx
The highest bandwidth usage for transmissions to the attached equipment.
4.2.6
Receiver rate (P)

Console
Receiver rate (P)
SNMP
statPvcPeakRx
The highest bandwidth usage for data received from the attached equipment.
Memotec Inc.
4-5
WAN Frame Relay
4.2.7
Number of frames transmitted

Console
SNMP
Number of frames transmit- statPvcFramesTx

ted
The number of frames that the PVC has transmitted to the attached equipment.
4.2.8
Number of frames received

Console
SNMP
Number of frames received statPvcFramesRx
The number of frames that the PVC has received from the attached equipment.
4.2.9
Number of octets transmitted

Console
SNMP
Number of octets transmit- statPvcOctetsTx

ted
The number of octets that the PVC has transmitted to the attached equipment.
4.2.10
Number of octets received

Console
SNMP
statPvcOctetsRx
The number of octets that the PVC has received from the attached equipment.
4.2.11
Number of BECN received

Console
SNMP
Number of BECN received statPvcBecnRx
The number of Backward Congestion Bits (BECN) that the PVC has received from the
attached equipment.
4.2.12
Number of BECN transmitted

Console
SNMP
Number of BECN transmit- statPvcBecnTx

ted
The number of Backward Congestion Bits (BECN) that the PVC has transmitted to the
attached equipment.
4-6
Memotec Inc.
4.2.13
Number of FECN received

Console
SNMP
statPvcFecnRx
The number of Forward Congestion Bits (FECN) that the PVC has received from the
attached equipment.
4.2.14
Number of FECN transmitted

Console
SNMP
Number of FECN transmit- statPvcFecnTx

ted
The number of Forward Congestion Bits (FECN) that the PVC has transmitted to the
attached equipment.
4.2.15
Number of CLLM frames received

Console
Number of CLLM frames

received
SNMP
statPvcCllmRx
The number of CLLM frames that the PVC has received from the attached equipment.
4.2.16
Number of CLLM frames transmitted

Console

transmitted
SNMP
statPvcCllmTx
The number of CLLM frames that the PVC has transmitted to the attached equipment.
Memotec Inc.
4-7
WAN Frame Relay
4.2.17
Transparent PVC Counters

For a Transparent PVC, the Display Counters command displays both sides of the PVC.
DC/PVC
example: for
Transparent
PVC
SDM-9380>DC
DISPLAY COUNTERS
TIMEP,
def:BOOTP) ? PVC
Transparent PVC #1 --> PORT #1
% (M)
% (M)
PVC 1> Number of BECN received..................0
PVC 1> Number of BECN transmitted...............0
PVC 1> Number of FECN received..................0
PVC 1> Number of FECN transmitted...............0
PVC 1> Number of CLLM frames received...........0
PVC 1> Number of CLLM frames transmitted........0
% (M)
% (M)
PVC 1> Number of BECN received..................0
PVC 1> Number of BECN transmitted...............0
PVC 1> Number of FECN received..................0
PVC 1> Number of FECN transmitted...............0
PVC 1> Number of CLLM frames received...........0
PVC 1> Number of CLLM frames transmitted........0
...
4.2.18
SVC Counters
If you select the SVC counters for the Display Counters command, a display like the
DC/SVC/FR
example
4-8
SDM-9360>DC
DISPLAY COUNTERS
TIMEP,
def:BOOTP) ? SVC
SVC TYPE (ATM/FR/ALL,def:FR) ?
Memotec Inc.
SVC 1> Transmitter rate.........................3
% (M)
SVC 1> Receiver rate............................2
% (M)
SVC 1> Number of frames transmitted.............315409

SVC 1> Number of frames received................187761
SVC 1> Number of octets transmitted.............512439
SVC 1> Number of octets received................290091
SVC 1> Number of BECN received..................56
SVC 1> Number of BECN transmitted...............29
SVC 1> Number of FECN received..................0
SVC 1> Number of FECN transmitted...............0
SVC 1> Number of CLLM frames received...........21
SVC 1> Number of CLLM frames transmitted........10
SVC 2> Transmitter rate.........................6
% (M)
SVC 2> Receiver rate............................5
% (M)
...
These counters can be used to determine the efficiency of Frame Relay SVCs. The display
is similar to that for the PVCs, but the SNMP variable names are different, as specified in
the following descriptions.
4.2.19

Console
SNMP
statSvcMeanTx
The average bandwidth usage for transmissions to the attached equipment. This statistic as
well as the other transmitter/receiver rate statistics are given as a percentage of the
available bandwidth.
4.2.20
Receiver rate (M)

Console
SNMP
Receiver rate (M)
statSvcMeanRx
The average bandwidth usage for data received from the attached equipment.
4.2.21

Console
SNMP
statSvcPeakTx
The highest bandwidth usage for transmissions to the attached equipment.
Memotec Inc.
4-9
WAN Frame Relay
4.2.22
Receiver rate (P)

Console
Receiver rate (P)
SNMP
statSvcPeakRx
The highest bandwidth usage for data received from the attached equipment.
4.2.23

Console
SNMP
Number of frames transmit- statSvcFramesTx

ted
The number of frames that the SVC has transmitted to the attached equipment.
4.2.24

Console
SNMP
Number of frames received statSvcFramesRx
The number of frames that the SVC has received from the attached equipment.
4.2.25

Console
SNMP
Number of octets transmit- statSvcOctetsTx

ted
The number of octets that the SVC has transmitted to the attached equipment.
4.2.26

Console
SNMP
statSvcOctetsRx
The number of octets that the SVC has received from the attached equipment.
4.2.27

Console
SNMP
Number of BECN received statSvcBecnRx
The number of Backward Congestion Bits (BECN) that the SVC has received from the
attached equipment.
4-10
Memotec Inc.
4.2.28

Console
SNMP
Number of BECN transmit- statSvcBecnTx

ted
The number of Backward Congestion Bits (BECN) that the SVC has transmitted to the
attached equipment.
4.2.29

Console
SNMP
statSvcFecnRx
The number of Forward Congestion Bits (FECN) that the SVC has received from the
attached equipment.
4.2.30

Console
SNMP
Number of FECN transmit- statSvcFecnTx

ted
The number of Forward Congestion Bits (FECN) that the SVC has transmitted to the
attached equipment.
4.2.31

Console

received
SNMP
statSvcCllmRx
The number of CLLM frames that the SVC has received from the attached equipment.
4.2.32

Console

transmitted
SNMP
statSvcCllmTx
The number of CLLM frames that the SVC has transmitted to the attached equipment.
4.2.33
Q.922 Counters
If you select the Q.922 counters for the Display Counters command, a display like the
Memotec Inc.
4-11
WAN Frame Relay
DC/Q922
example
SDM-9380>DC
DISPLAY COUNTERS
TIMEP,
def:SVC) ? Q922
Q922 Tx retransmissions.........................1
Q922 Release indications........................0
Q922 Establish indications......................1
Q922 Data link established......................5
Q922 Tx Iframe Q discards.......................6
Q922 Rx frames..................................2799
Q922 Tx frames..................................2812
Q922 Rx bytes...................................12702
Q922 Tx bytes...................................12426
The Q.922 counters include the following:
4.2.34
Q922 Tx retransmissions
Console
Q922 Tx retransmissions
SNMP
statTxRetransmissions
The number of retransmissions invoked.
4.2.35
Q922 Release indications

Console
Q922 Release indications
SNMP
statReleaseIndications
The number of release indications that have occurred.
4.2.36
Q922 Establish indications

Console
SNMP
Q922 Establish indications statEstablishIndications
The number of establish indications that have occurred.
4.2.37
Q922 Data link established

Console
SNMP
Q922 Data link established statLinkEstablished
The number of links that have been established since the last counters reset (see Resetting
the Counters on page 4-17).
4-12
Memotec Inc.
4.2.38
Q922 Tx Iframe Q discards

Console
SNMP
Q922 Tx Iframe Q discards statTxIframeQdiscards
The number of TX Iframe Q discards that have occurred.
4.2.39
Q922 Rx frames
Console
Q922 Rx frames
SNMP
statRxframes
The number of frames received by the NetPerformer Q.922 layer.
4.2.40
Q922 Tx frames
Console
Q922 Tx frames
SNMP
statTxframes
The number of frames transmitted by the NetPerformer Q.922 layer.
4.2.41
Q922 Rx bytes
Console
Q922 Rx bytes
SNMP
statRxBytes
The number of bytes received by the NetPerformer Q.922 layer.
4.2.42
Q922 Tx bytes
Console
Q922 Tx bytes
SNMP
statTxBytes
The number of bytes transmitted by the NetPerformer Q.922 layer.
4.2.43
Q.933 Counters
If you select the Q.933 counters for the Display Counters command, a display like the
DC/Q933
example
Memotec Inc.
SDM-9380>DC
DISPLAY COUNTERS
TIMEP,
def:Q922) ? Q933
Q933 Tx setup messages..........................7
Q933 Rx setup messages..........................0
4-13
WAN Frame Relay
Q933 Tx call proceeding messages................0

Q933 Rx call proceeding messages................0
Q933 Tx connect messages........................13

Q933
Q933
Q933
Q933
Q933
Q933
Q933
Q933
Q933
Q933
Q933
Q933
Rx connect messages........................7
Tx release messages........................12
Rx release messages........................7
Tx release complete messages...............7
Rx release complete messages...............12
Tx disconnect messages.....................7
Rx disconnect messages.....................12
Tx status messages.........................0
Rx status messages.........................0
Tx status enquiry messages.................0
Rx status enquiry messages.................0
Protocol timeouts..........................0
Q933 Setup success rate (%).....................37

The Q.933 counters include the following:
4.2.44
Q933 Setup success rate

Console
Q933 Setup success rate
SNMP
statSetupSuccessRate
The percentage of setup attempts that were successfully completed.
4.2.45
Q933 Tx setup messages

Console
Q933 Tx setup messages
SNMP
statTxSetupMessages
The number of setup messages transmitted by the NetPerformer Q.933 layer.
4.2.46
Q933 Rx setup messages

Console
Q933 Rx setup messages
SNMP
statRxSetupMessages
The number of setup messages received by the NetPerformer Q.933 layer.
4.2.47
Q933 Tx call proceeding messages

Console
Q933 Tx call proceeding

messages
SNMP
statTxCallProceedingMessages
The number of call proceeding messages transmitted by the NetPerformer Q.933 layer.
4-14
Memotec Inc.
4.2.48
Q933 Rx call proceeding messages

Console
Q933 Rx call proceeding

messages
SNMP
statRxCallProceedingMessages
The number of call proceeding messages received by the NetPerformer Q.933 layer.
4.2.49
Q933 Tx connect messages

Console
Q933 Tx connect messages
SNMP
statTxConnectMessages
The number of connect messages transmitted by the NetPerformer Q.933 layer.
4.2.50
Q933 Rx connect messages

Console
Q933 Rx connect messages
SNMP
statRxConnectMessages
The number of connect messages received by the NetPerformer Q.933 layer.
4.2.51
Q933 Tx release messages

Console
SNMP
Q933 Tx release messages statTxReleaseMessages
The number of release messages transmitted by the NetPerformer Q.933 layer.
4.2.52
Q933 Rx release messages

Console
Q933 Rx release messages
SNMP
statRxReleaseMessages
The number of release messages received by the NetPerformer Q.933 layer.
4.2.53
Q933 Tx release complete messages

Console
Q933 Tx release complete

messages
SNMP
statTxReleaseCompleteMessages
The number of release complete messages transmitted by the NetPerformer Q.933 layer.
Memotec Inc.
4-15
WAN Frame Relay
4.2.54
Q933 Rx release complete messages

Console
SNMP
Q933 Rx release complete statRxReleaseCompleteMessages

messages
The number of release complete messages received by the NetPerformer Q.933 layer.
4.2.55
Q933 Tx disconnect messages

Console
Q933 Tx disconnect messages
SNMP
statTxDisconnectMessages
The number of disconnect messages transmitted by the NetPerformer Q.933 layer.
4.2.56
Q933 Rx disconnect messages

Console
Q933 Rx disconnect messages
SNMP
statRxDisconnectMessages
The number of disconnect messages received by the NetPerformer Q.933 layer.
4.2.57
Q933 Tx status messages

Console
Q933 Tx status messages
SNMP
statTxStatusMessages
The number of status messages transmitted by the NetPerformer Q.933 layer.
4.2.58
Q933 Rx status messages

Console
Q933 Rx status messages
SNMP
statRxStatusMessages
The number of status messages received by the NetPerformer Q.933 layer.
4.2.59
Q933 Tx status enquiry messages

Console
Q933 Tx status enquiry

messages
SNMP
statTxStatusEnquiryMessages
The number of status enquiry messages transmitted by the NetPerformer Q.933 layer.
4-16
Memotec Inc.
4.2.60
Q933 Rx status enquiry messages

Console
Q933 Rx status enquiry

messages
SNMP
statRxStatusEnquiryMessages
The number of status messages received by the NetPerformer Q.933 layer.
4.2.61
Q933 Protocol timeouts

Console
Q933 Protocol timeouts
SNMP
statProtocolTimeouts
The number of Q.933 protocol timeouts that have occurred since the last counters reset
(see next section).
4.2.62
Resetting the Counters

Console
RC
SNMP
statSystemResetCounters
Use the Reset Counters command to return the port and PVC counters, as well as other
statistics and error counters, to zero. For the console, enter RC on the command line. The
date and time of the last reset is displayed, and then you are requested to confirm a new
reset, as in the following example:
RC example
SDM-9230>RC
RESET COUNTERS
Last counter reset : THU
2003/10/16 14:18:02
Reset counters, please confirm (NO/YES,def:NO) ? YES
Counters reset !
If you enter YES, the counters are reset and the Last Counter Reset timestamp is updated.
If you enter NO, no changes are applied.
For SNMP, set the statSystemResetCounters variable to YES to reset all counters to a zero
value.
Memotec Inc.
4-17
WAN Frame Relay
4.3
Displaying Frame Relay Errors

The Display Errors command (DE) shows the number of errors that have occurred on all
Frame Relay connections for each error type stored in memory. These statistics can be
used to diagnose operating problems on the connections.
To display the number of errors that have occurred on the Frame Relay connections:
Enter DE at the console command prompt.
- PORT: To view errors for all built-in serial ports (see next section).
- SLOT: To view errors for all digital channels or dual serial ports on a particular slot. Enter the Slot number at the prompt. The display for slot errors is the
same as that for port errors (see next section).
- PVC: To view errors for all PVCs (see PVC Errors on page 4-21).
- GROUP: To view errors for all Port/PVC groups (see Group Errors on
page 4-24).
- SVC: To view errors for all SVCs (see SVC Errors on page 4-26).
- Q922: To view all Q922 errors (see Q.922 Errors on page 4-28)
TYPE or SVC TYPE prompt
Console
DE/PORT
DE/SLOT
DE/PVC
DE/GROUP
DE/SVC
Q922
SNMP
statIfwan
statIfwan
statPvc
statGrp
statSvc
stat (categories)
4.3.1
Port Errors
If you select the port errors with the Display Errors command, a display like the following
will appear on the screen:
DE/PORT
example
4-18
SDM-9380>DE
DISPLAY ERRORS
Item (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PU/PVC/Q922/SLOT/SVC/
TIMEP,
def:BOOTP) ? PORT
Memotec Inc.
PORT ETH> Number of excessive collisions........0

...
PORT 1> Number of bad frames....................0
PORT 1> Number of underruns.....................0
PORT 1> Number of retries.......................0
PORT 1> Number of restarts......................0
PORT 1> Number of frames discarded (overrun)....0
PORT 1> Number of octets discarded (bad)........0
PORT 1> Number of octets discarded (overrun)....0
Bad flags: U:Bad LENGTH Q:Overflow F:Flush S:Overrun
A:Abort
------
------
------
B:Bad CRC
These statistics can be used to diagnose operating problems on Frame Relay ports.
4.3.2
Number of bad frames

Console
SNMP
statIfwanBadFrames,
statIfwanBadFlags
The BAD counter (statIfwanBadFrames in SNMP) indicates the number of bad frames
received and rejected, and the flags indicate the types of errors that have occurred. The
BAD flags (statIfwanBadFlags in SNMP) are displayed with a six-character field, where
the individual characters have the following meaning:
U: Bad length; invalid cell type or length (PVCR port only)
Q: Overflow; overflow on reception
F: Flush; overflow on reception
S: Overrun; overflow on reception
B: Bad CRC; frame contains a bad CRC
A: Abort; frame contains an abort sequence
The B and A flags on a FR-USER port are caused by transmission errors on the network.
For a FR-NET port, the B and A flags are caused by transmission errors on the Frame
Relay user equipment side. The BAD counter is incremented by one for each frame
received with a B or A type error.
Memotec Inc.
4-19
WAN Frame Relay
When the Q, F or S flags are set on a FR-NET port, the BAD counter is incremented by
one for each frame discarded when the input queue overloads. For a FR-USER port, the
BAD counter is meaningless. The Q, F and S flags indicate that the unit was temporarily
unable to receive a frame because the input queue was full. Use the Reset Counters (RC)
command to reset the BAD counter to zero.
4.3.3
Number of underruns
Console
Number of underruns
SNMP
statIfwanUnderruns
An underrun indicates a transmission error for an incomplete frame. The Underruns

counter is incremented when a frame currently in transmission has been aborted because
the end of the frame was not received on time.
4.3.4
Number of retries
Console
SNMP
Number of retries
statIfwanRetries
The Retries counter indicates the number of retries on SDLC ports. For Frame Relay ports,
it is displayed as 0.
4.3.5
Number of restarts
Console
Number of restarts
SNMP
statIfwanRestart
This counter is incremented every time an error on the Frame Relay connection causes the
port to restart. It indicates how many times this port has had to be resynchronized due to
errors occurring on the connection.
4.3.6
Number of frames discarded (overrun)

Console
SNMP
statIfwanOvrFrames
The number of frames that were discarded due to an overrun on the receive queue.
4.3.7
Number of octets discarded (bad)

Console
SNMP
Number of octets discarded statIfwanBadOctets

(bad)
The number of octets received that were discarded due to transmission errors.
4-20
Memotec Inc.
4.3.8
Number of octets discarded (overrun)

Console
SNMP
Number of octets discarded statIfwanOvrOctets

(overrun)
The number of octets that were discarded due to an overrun on the receive queue.
4.3.9
PVC Errors
If you select the PVC errors with the Display Errors command, a display like the
DE/PVC
example
SDM-9380>DE
DISPLAY ERRORS
TIMEP,
def:PORT) ? PVC
PVC 1> Number of errors.........................32
PVC 1> Number of restarts.......................0
PVC 1> Number of invalid frames discarded.......1
PVC 1> Number of frames discarded (overrun).....0
PVC 1> Number of invalid octets discarded.......40
PVC 1> Number of octets discarded (overrun).....0
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
2>
2>
2>
2>
2>
2>
2>
2>
2>
2>
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
of
of
of
of
of
of
of
of
of
of
errors.........................0
restarts.......................0
invalid frames discarded.......0
frames discarded (overrun).....0
invalid octets discarded.......0
octets discarded (overrun).....0
compressor errors..............0
channel overflow errors........0
channel abort errors...........0
channel sequence errors........0
PVC
PVC
PVC
PVC
PVC
PVC
...
3>
3>
3>
3>
3>
3>
Number
Number
Number
Number
Number
Number
of
of
of
of
of
of
errors.........................0
restarts.......................0
invalid frames discarded.......0
frames discarded (overrun).....0
invalid octets discarded.......0
octets discarded (overrun).....0
These statistics can be used to diagnose operating problems on Frame Relay PVCs.
4.3.10
Number of errors
Console
Number of errors
Memotec Inc.
SNMP
statPvcError
4-21
WAN Frame Relay
This counter is incremented every time the NetPerformer detects errors coming from the
PVC.
4.3.11
Number of restarts
Console
Number of restarts
SNMP
statPvcRestart
This counter indicates the number of restarts that have occurred on the PVC. The meaning
of this counter depends on the PVC mode:
PVC in PVCR Mode: The restart counter is incremented every time the Frame
Relay connection is down for more than the number of seconds determined by
the port Report cycle parameter times the cycle count (see the description of
Report cycle on page 6-8). In addition, if the PVCR PVC is not restored within
the time set by the Link timeout global parameter, the NetPerformer will log a
LINK PVC DOWN alarm.
PVC in MULTIPLEX Mode: The restart counter is incremented every time an
error on the Frame Relay connection has caused the PVC to restart.
PVC in TRANSP or RFC1490 Mode: The restart counter is not used, and
remains at 0.
4.3.12
Number of invalid frames discarded

Console
Number of invalid frames

discarded
SNMP
statPvcBadFrames
The number of frames received that were discarded due to invalidity.
4.3.13

Console
SNMP
statPvcOvrFrames
4.3.14
Number of invalid octets discarded

Console
Number of invalid octets

discarded
SNMP
statPvcBadOctets
The number of octets received that were discarded due to invalidity.
4-22
Memotec Inc.
4.3.15

Console
SNMP
Number of octets discarded statPvcOvrOctets

(overrun)
The last four error counters provide statistics on channel and compression dictionary
operations. They are calculated and displayed for PVCs in MULTIPLEX mode only.
NOTE:
4.3.16
A global overview of all channel and compression dictionary error statistics is

also available using the Display Errors command. Select the CHANNEL for
channel statistics and DICT for compression dictionary statistics. For details,
refer to the chapter Global Functions in the Quick Configuration module
of this document series.
Number of compressor errors

Console
Number of compressor
errors
SNMP
statPvcCompErrs
This counter is incremented every time the connections compression dictionary detects an
error.
4.3.17
Number of channel overflow errors

Console
SNMP
statPvcChOverflows
This counter is incremented every time the channel discards a cell because its buffer is
full.
4.3.18
Number of channel abort errors

Console
Number of channel abort

errors
SNMP
statPvcChAborts
This counter is incremented every time the reception of a frame is terminated abruptly.
Memotec Inc.
4-23
WAN Frame Relay
4.3.19
Number of channel sequence errors

Console
Number of channel
sequence errors
SNMP
statPvcChSeqErrs
This counter is incremented every time that frame reception fails, that is, there is at least
one block missing.
4.3.20
Transparent PVC Errors

For a Transparent PVC, the Display Errors command displays both sides of the PVC, as
shown the following example:
DE/PVC
example: for
Transparent
PVC
SDM-9380>DE
DISPLAY ERRORS
TIMEP,
def:BOOTP) ? PVC
...
4.3.21
Group Errors
If you select the GROUP errors with the Display Errors command, a display like the
DE/GROUP
example
SDM-9390>DE
DISPLAY ERRORS
Item (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PU/PVC/Q922/REDUNDANCY/
SLOT/SVC/
TIMEP,def:CHANNEL) ? GROUP
GROUP to FR.80-1 [SDM-9585]
Sorter overruns..................................0
4-24
Memotec Inc.
Sorter window overflows..........................0

Sorter timeouts..................................0
Sorter rejected cells............................0
GROUP to PVC
3 [SDM-0]
Sorter
Sorter
Sorter
Sorter
overruns..................................0
window overflows..........................0
timeouts..................................0
rejected cells............................0

Sorter
Sorter
Sorter
Sorter
overruns..................................0
timeouts..................................0
rejected cells............................0

Sorter
Sorter
Sorter
Sorter
overruns..................................0
timeouts..................................0
rejected cells............................0
GROUP to FR.80 [SDM-9585]

Sorter
Sorter
Sorter
Sorter
overruns..................................0
timeouts..................................0
rejected cells............................0
These statistics can be used to diagnose problems occurring on the Port/PVC groups. A
group is a set of Frame Relay connections in PVCR mode that communicate with a
particular remote site. The error counters can be used to determine whether and where
cells are being lost in the network.
The following errors are displayed for each Port/PVC group:
4.3.22
Sorter overruns
Console
Sorter overruns
SNMP
statGrpSorterOverruns
This error counter is incremented every time the sorter cannot process cells for this group
because its receive buffer is full.
4.3.23
Sorter window overflows

Console
Memotec Inc.
SNMP
statGrpSorterWindowOverflows
4-25
WAN Frame Relay
This error counter is incremented every time that cells are lost due to an overflow of the
sorter window.
4.3.24
Sorter timeouts
Console
Sorter timeouts
SNMP
statGrpSorterTimeouts
This error counter is incremented every time the sorter waits too long to put the received
cells in the right order.
4.3.25
Sorter rejected cells

Console
SNMP
statGrpSorterRejectedCells
This error counter is incremented every time that cells are rejected by the sorter because
they are invalid or unrecognizable.
4.3.26
SVC Errors
If you select the SVC errors with the Display Errors command, a display like the
DE/SVC/FR
example
SDM-9360>DE
DISPLAY ERRORS
TIMEP,
def:BOOTP) ? SVC
SVC TYPE (ATM/FR/ALL,def:FR) ? FR
SVC 1> Number of errors.........................4
SVC 1> Number of restarts.......................0
SVC 1> Number of frames discarded (CRC).........0
SVC 1> Number of frames discarded (overrun).....2
SVC 1> Number of octets discarded (CRC).........0
SVC 1> Number of octets discarded (overrun).....16
...
These statistics can be used to diagnose operating problems on Frame Relay SVCs.
4-26
Memotec Inc.
4.3.27
Number of errors
Console
Number of errors
SNMP
statSvcError
This counter is incremented every time the NetPerformer detects errors coming from the
SVC.
4.3.28
Number of restarts
Console
Number of restarts
SNMP
statSvcRestart
This counter indicates the number of restarts that have occurred on the SVC. The restart
counter is incremented every time an error on the Frame Relay connection has caused the
SVC to restart.
4.3.29
Number of frames discarded (CRC)

Console
SNMP
statSvcBadFrames
The number of frames received that were discarded due to a bad checksum.
4.3.30

Console
SNMP
statSvcOvrFrames
4.3.31
Number of octets discarded (CRC)

Console
SNMP
Number of octets discarded statSvcBadOctets

(CRC)
The number of octets received that were discarded due to a bad checksum.
4.3.32

Console
SNMP
Number of octets discarded statSvcOvrOctets

(overrun)
Memotec Inc.
4-27
WAN Frame Relay
4.3.33
Q.922 Errors
If you select the Q.922 errors for the Display Errors command, a display like the following
will appear on the screen:
DE/Q922
example
SDM-9380>DE
DISPLAY ERRORS
TIMEP,
def:SVC) ? Q922
Q922 Invalid Rx sizes...........................0
Q922 Missing control blocks.....................0
Q922 Rx Ack expiry..............................0
Q922 Tx Ack expiry..............................0
The Q.922 errors include the following:
4.3.34
Q922 Invalid Rx sizes

Console
Q922 Invalid Rx sizes
SNMP
statInvalidRxSizes
The number of frames received with an invalid length.
4.3.35
Q922 Missing control blocks

Console
Q922 Missing control

blocks
SNMP
statMissingControlBlocks
The number of control blocks that were not found.
4.3.36
Q922 Rx Ack expiry

Console
Q922 Rx Ack expiry
SNMP
statRxAcknowledgeExpiry
The number of Receiver Ready (RR) indications that were received due to a Transmission
Acknowledge (Tack) expiry.
4.3.37
Q922 Tx Ack expiry

Console
Q922 Tx Ack expiry
SNMP
statTxAcknowledgeExpiry
The number of transmission frame acknowledgments that were delayed because the
NetPerformer was waiting for a Transmission Acknowledge (Tack).
4-28
Memotec Inc.
4.4
Displaying Frame Relay States

The Display States (DS) command provides current status information for the Frame
Relay ports, PVCs and SVCs.
NOTE:
The DPORT command is also available for viewing a continuously updated

display of port states. Refer to Continuous Display of Port States on page 433.
To display the current status of all Frame Relay connections:

Enter DS at the console command prompt.
- PORT: To view the current status of all built-in serial ports (see next section)
- SLOT: To view the status of all digital channels or dual serial ports on a particular slot. Enter the Slot number at the prompt. The status display for slots is
the same as that for ports (see next section).
- PVC: To view the current status all PVCs (see PVC Status on page 4-35)
- SVC: To view the current status of all SVCs (see SVC Status on page 4-39)
TYPE or SVC TYPE prompt.
Console
DS/PORT
DS/SLOT
DS/PVC
DS/SVC
SNMP
statIfwan
statIfwan
statPvc
statSvc (categories)
4.4.1
Port Status
If you select the port statistics with the Display States command, a display like the
DS/PORT
example
Memotec Inc.
SDM-9230>DS
DISPLAY STATES
Item (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:GLOBAL) ? PORT
PORT ETH> Protocol..............................ETHERNET
...
4-29
WAN Frame Relay
PORT
PORT
PORT
PORT
PORT
1>
1>
1>
1>
1>
Protocol................................FR-USER
Interface...............................DTE-V35
Speed used [bps]........................2048k
Modem signals...........................STDRCState...................................DATA
PORT 1> Q922 state..............................UP

PORT
PORT
PORT
PORT
PORT
2>
2>
2>
2>
2>
Protocol................................FR-NET
Interface...............................DTE-V35
Speed used [bps]........................512000
Modem signals...........................-T-R-State...................................WAIT
Modem signals:
d(S)r
d(T)r
(D)cd
(R)ts
(C)ts
r(I)
(-)off
These statistics can be used to determine the current status of Frame Relay ports.
4.4.2
Protocol
Console
Protocol
SNMP
statIfwanProtocol
The protocol used on the port. The Frame Relay port protocols are displayed as:
FR-NET: Frame Relay Network
FR-USER: Frame Relay User
4.4.3
Interface
Console
Interface
SNMP
statIfwanInterface
This display includes the physical interface (V.35/X.21/RS-232/RS-449/RS-530) and

gender of the port (DTE or DCE). These are taken from the interface configured with the
Interface parameter of the Setup Port menu.
4.4.4
Speed used
Console
Speed used
SNMP
statIfwanSpeed
This is the speed measured by the NetPerformer. The NetPerformer automatically

measures the port speed every 10 seconds if the port is in external clocking. Otherwise, the
displayed speed is the speed configured with the Speed parameter of the Setup Port menu.
NOTE:
4-30
The speed measured by the NetPerformer may be different from the configured speed if the Frame Relay connection is configured as DTE.
Memotec Inc.
4.4.5
Modem signals
Console
Modem signals
SNMP
statIfwanModemSignal
The modem signal status. The modem signal status for an RS-232/RS-449/RS530 or V.35
interface is displayed with a six-character field, where the individual characters have the
following meaning:
S: DSR ON
T: DTR ON
D: DCD ON
R: RTS ON
C: CTS ON
I: RI ON
The modem signal status for an X.21 interface is displayed with a two-character field,
where the individual characters have the following meaning:
C: COMMAND ON
I: INDICATION ON
When a modem control signal is inactive, the NetPerformer displays a dash [-] in the
appropriate field position.
4.4.6
State
Console
State
SNMP
statIfwanState
The current status of the Frame Relay connection or user port. The possible states for a
Frame Relay port are:
WAIT: Waiting for a status response from the network (if in FR-USER protocol), or waiting for a status enquiry from the attached equipment (if in FR-NET
protocol).
DATA: Data can flow normally across the Frame Relay network. The management protocol is working.
4.4.7
Q922 state
Console
Q922 state
SNMP
statIfwanQ922State
For FR-USER port only.

The current status of Q.922 signaling on a FR-USER port that supports SVCs. The
possible states are:
Memotec Inc.
4-31
WAN Frame Relay
UP: The Q.922 connection is up. The local NetPerformer can now use SVCs
because it has established a Q.922 connection with the Frame Relay switch.
DOWN: The Q.922 connection went down. This will occur if to many errors
have occurred on the Q.922 connection or if the Frame Relay port (FR-USER
protocol) is down.
NOTE:
4-32
Although the Q.922 connection relies on the FR-USER port to send and
receive messages, its status (UP or DOWN) is independent of port status. For
example, the Q.922 connection will often be up before the FR-USER port
reaches the DATA state. Also, the Q.922 connection may be down while the
FR-USER port remains functional.
Memotec Inc.
4.4.8
Continuous Display of Port States

The Display Port States (DPORT) command displays the real-time status of Frame Relay
ports. The statistics displayed are similar to those displayed by the Display States
command.
When you execute the Display Port States command, a display like the following will
appear on the screen:
DPORT
example
4.4.9
SDM-9380>DPORT
DISPLAY PORT STATES
------------------------------------------------------------------------------|PORT# PROTOCOL
INTERFACE SPEED
MODEM
STATE DELAY
|
|
(BPS)
SIGNALS
|
------------------------------------------------------------------------------|
1 FR-NET
DCE-V35
56000
STDRCDATA
|
|
2 FR-NET
DTE-V35
56000
STDRCDATA
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Modem signals: d(S)r d(T)r (D)cd (R)ts (C)ts r(I) (-)off
|
------------------------------------------------------------------------------Use HOME, END, UP and DOWN arrow keys to scroll. Press any other key to exit.
PORT#
Console
PORT#
SNMP
statIfwanIndex
Provides the current value for the port number, continuously refreshed and displayed in
real time.
4.4.10
PROTOCOL
Console
PROTOCOL
SNMP
statIfwanProtocol
Provides the current value for the Frame Relay protocol used on the port, continuously
Memotec Inc.
4-33
WAN Frame Relay
refreshed and displayed in real time. The Frame Relay port protocols are displayed as:
FR-NET: Frame Relay Network
FR-USER: Frame Relay User
4.4.11
INTERFACE
Console
INTERFACE
SNMP
statIfwanInterface
Provides the current value for the physical interface (V.35/X.21/RS-232/RS-449/RS-530)

and gender of the port (DTE or DCE), continuously refreshed and displayed in real time.
4.4.12
SPEED (BPS)
Console
SPEED (BPS)
SNMP
statIfwanSpeed
Provides the current value for the speed measured by the NetPerformer, continuously
refreshed and displayed in real time. The NetPerformer automatically measures the port
speed every 10 seconds if the port is in external clocking. Otherwise, the displayed speed
is the speed configured with the Speed parameter of the Setup Port menu.
NOTE:
4.4.13
The speed measured by the NetPerformer may be different from the configured speed if the Frame Relay connection is configured as DTE.
MODEM SIGNALS
Console
MODEM SIGNALS
SNMP
statIfwanModemSignal
Provides the current value for the modem signal status., continuously refreshed and
displayed in real time. The modem signal status for an RS-232/RS-449/RS530 or V.35
interface is displayed with a six-character field, where the individual characters have the
following meaning:
S: DSR ON
T: DTR ON
D: DCD ON
R: RTS ON
C: CTS ON
I: RI ON
4-34
Memotec Inc.
The modem signal status for an X.21 interface is displayed with a two-character field,
where the individual characters have the following meaning:
C: COMMAND ON
I: INDICATION ON
When a modem control signal is inactive, the NetPerformer displays a dash [-] in the
appropriate field position.
4.4.14
STATE DELAY
Console
STATE DELAY
SNMP
statIfwanState
Provides the current status of the Frame Relay connection or user port, continuously
refreshed and displayed in real time. The possible states for a Frame Relay port are:
WAIT: Waiting for a status response from the network (if in FR-USER protocol), or waiting for a status enquiry from the attached equipment (if in FR-NET
protocol).
DATA: Data can flow normally across the Frame Relay network. The management protocol is working.
4.4.15
PVC Status
If you select the PVC statistics with the Display States command, a display like the
DS/PVC/FR
example
Memotec Inc.
SDM-9230>DS
DISPLAY STATES
Item (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:PORT) ? PVC
PVC TYPE (ATM/FR/ALL,def:FR) ?
PVC 1> Mode.....................................PVCR
PVC 1> Information signals......................USER -A--PVC 1> Speed used (bps).........................1024 k
PVC 1> DLCI.....................................212
PVC 1> Remote unit name...........................BOSTON
PVC 1> State & Delay............................DATA 11ms
PVC
PVC
PVC
PVC
PVC
PVC
2>
2>
2>
2>
2>
2>
Mode.....................................PVCR
Information signals......................USER -A--Speed used (bps).........................1024 k
DLCI.....................................221
Remote unit name.........................FR.60-3
State & Delay............................DATA 14ms
PVC
PVC
PVC
PVC
PVC
7>
7>
7>
7>
7>
Mode.....................................PVCR
DLCI.....................................401
Remote unit name.........................ATM1.80-1
4-35
WAN Frame Relay
PVC 7> State & Delay............................DATA 18ms

PVC
PVC
PVC
PVC
PVC
PVC
8>
8>
8>
8>
8>
8>
Mode.....................................PVCR
DLCI.....................................402
Remote unit name.........................ATM2.60-1
State & Delay............................DATA 104ms
Info signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn ()off
These statistics can be used to determine the current status of Frame Relay PVCs.
4.4.16
Mode
Console
Mode
SNMP
statPvcMode
The current operating mode of the PVC. This may be any of:
OFF: No mode configured
PVCR: PVCR mode (using Frame Relay port)
1490: RFC1490 mode (using Frame Relay port)
MULTIPLEX: Multiplex mode (using Frame Relay port, FR-NET protocol
only)
BROADCAST: Broadcast mode (using analog voice port)
TRANSP: Transparent mode (using 2 Frame Relay ports)
4.4.17
Information signals
Console
Information signals
SNMP
statPvcInfoSignal
The information signal status. This statistic is displayed with a five-character field, where
N: New PVC
A: Active PVC
C: CIR reached
F: Forward Congestion (to destination PVC)
B: Backward Congestion (from destination PVC)
When an information signal is not present, the NetPerformer displays a dash [-] in the
appropriate field position. If the PVC is inactive, the NetPerformer displays off line.
For a PVC used to carry Frame Relay traffic over IP, the status bits next to the Information
4-36
Memotec Inc.
Signals are static and unchanging. The Active (A) bit is automatically set as soon as the
DLCI Address is non-zero and the PVC port is set to a virtual IP port (0).
For an RFC1490 PVC, The status of the Active (A) bit is no longer affected by the status
of modem signals on the corresponding FR-NET or FR-USER port:
When an RFC1490 PVC is configured on a FR-NET port, the Active bit is
always ON regardless of the state of the modem signal.
When an RFC1490 PVC is configured on a FR-USER port, the Active bit follows the state indicated in the FULL STATUS MESSAGE regardless of the state
of the modem signal.
Speed used (bps)
Console
Speed used (bps)
SNMP
statPvcSpeed
This is the speed measured by the NetPerformer. For a PVC used to carry Frame Relay
traffic over IP, Speed used (bps) is the value of the CIR parameter for this PVC, and not
the global CIR value.
4.4.18
DLCI
Console
DLCI
SNMP
statPvcDlci
Lists the DLCI address of this PVC.
4.4.19
Remote unit name

Console
Remote unit name
SNMP
statPvcDestName
The unit that is receiving traffic from this PVC.
4.4.20
State & Delay

Console
State & Delay
SNMP
statPvcState
The current status of the PVC. The possible PVC states are:
OFF: PVC inactive
CALL: Waiting for active signal from the network
TEST: PVC in test mode
DATA: PVC in operation
Memotec Inc.
4-37
WAN Frame Relay
4.4.21
Transparent PVC States

For a Transparent PVC, the Display States command displays both sides of the PVC, as
shown the following example:
SDM-9380>DS
DISPLAY STATES
Item (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:GLOBAL) ? PVC
PVC 1> Mode.....................................TRANSP
PVC 1> Information signals......................NET -A--PVC 1> Speed used (bps).........................56000
PVC 1> DLCI.....................................101
PVC 1> State & Delay............................DATA
PVC 1> Mode.....................................TRANSP
PVC 1> Information signals......................NET -A--PVC 1> Speed used (bps).........................56000
PVC 1> DLCI.....................................102
PVC 1> State & Delay............................DATA
...
Info signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn ()off
4.4.22
Continuous Display of PVC States

PVC status information is also available in a continuously refreshed real-time format,
using the Display PVC States (DPVC) command. The name of the destination unit for
each PVC is also provided in this display.
To display the status of all PVCs in real time:
Enter DPVC at the NetPerformer console command line prompt.
The statistics displayed are similar to those displayed using the Display States (DS)
command.
DPVC example
SDM-9230>DPVC
DISPLAY PVC STATES
-----------------------------------FR PVC-------------------------------------|PVC MODE
INFO.
SPEED
PORT
DLCI DESTINATION
STATE &
|
|
SIGNALS
(BPS)
NAME
DELAY(MS) |
------------------------------------------------------------------------------| 1 PVCR
off line
56000
WAN
1 102 CHICAGO-9230
CALL
|
| 2 PVCR
off line
56000
WAN
1 103 CHICAGO-9230
OFF
|
| 3 PVCR
off line
56000
WAN
1 0
OFF
|
| 4 MULTIPLEX
MULT ----- 56000
WAN
1 0
CHICAGO-9230
IDLE
|
| 5 BROADCAST
off line
56000
WAN
1 0
IDLE
|
| 6 TRANSP-USR
USER ----- 56000
WAN
1 0
IDLE
|
| 6 TRANSP-NET
USER ----- 56000
WAN
1 0
IDLE
|
|
|
|
|
|
|
4-38
Memotec Inc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
4.4.23
SVC Status
If you select the SVC statistics with the Display States command, a display like the
DS/SVC/FR
example
SDM-9360>DS
DISPLAY STATES
Item (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:GLOBAL) ? SVC
SVC TYPE (ATM/FR/ALL,def:FR) ?
SVC
SVC
SVC
SVC
SVC
1>
1>
1>
1>
1>
Mode.....................................PVCR
Information signals......................USER
Speed used (bps).........................56000
DLCI.....................................0
State....................................CALL
-----
...
Info signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn (-)off
These statistics can be used to determine the current status of Frame Relay SVCs. The
display is similar to that for the PVCs, but the SNMP variable names are different, as
specified in the following descriptions.
4.4.24
Protocol
Console
(not available)
SNMP
statSvcProtocol
This display provides the Frame Relay protocol used for this SVC. For SVCs, it is always
set to USER. This information is available from SNMP access only.
4.4.25
Mode
Console
Mode
SNMP
statSvcMode
The current operating mode of the SVC. The displayed mode is:
PVCR: PVCR mode (using Frame Relay port).
Memotec Inc.
4-39
WAN Frame Relay
4.4.26
Information signals
Console
Information signals
SNMP
statSvcInfoSignal
The information signal status. This statistic is displayed with a five-character field, where
N: New SVC
A: Active SVC
C: CIR reached
F: Forward Congestion (to destination SVC)
B: Backward Congestion (from destination SVC)
When an information signal is not present, the NetPerformer displays a dash [-] in the
appropriate field position. If the SVC is inactive, the NetPerformer displays off line.
4.4.27
Speed used (bps)

Console
Speed used (bps)
SNMP
statSvcSpeed
This is the speed, in bits per second, measured by the NetPerformer.
4.4.28
DLCI
Console
DLCI
SNMP
statSvcDlci
Lists the DLCI address of the SVC.
4.4.29
State
Console
State
SNMP
statSvcState
The current status of the SVC. The possible SVC states are:
OFF: SVC inactive
CALL: Waiting for active signal from the network
TEST: SVC in test mode
DATA: SVC in operation
4-40
Memotec Inc.
4.5
Capturing PVCR Frame Length

Console
CL
SNMP
(not available)
The Capture PVCR Frame Length (CL) command displays information concerning the
length of frames sent over the Frame Relay network via a Frame Relay connection. This
command analyzes and displays the frame length statistics of frames sent from a port or
PVC. These statistics are helpful for troubleshooting transmission problems on public
Frame Relay networks.
The Capture PVCR Frame Length command is available from the console only. To
execute this command:
Enter CL at the console command line.
Enter START.
Set the number of frames you want analyzed (default 1000).
Select PORT or PVC data.
Enter the Port or PVC number at the Capture prompt
SDM-9380>CL
CAPTURE FRAME LENGTH
Operation (START/STOP/DELETE/DISPLAY,def:START) ?
Number of frames (0-10000,def:1000) ?
Type (PORT/PVC,def:PORT) ? PVC
Capture PVC (1-300,def:*) ? 1
Capture of frame length is running !
The CL command operates in background mode. It will stop automatically when it has
finished analyzing the number of frames you requested.
Let the capture run for a sufficient amount of time before viewing the frame length
analysis:
Enter CL at the console command line.
Enter DISPLAY.
Memotec Inc.
4-41
WAN Frame Relay
CL/DISPLAY
example
SDM-9380>CL
CAPTURE FRAME LENGTH
Operation (START/STOP/DELETE/DISPLAY,def:STOP) ? DISPLAY
Number of frames ..........................
511
Smallest frame ............................
8
Largest frame .............................
245
Mean length ...............................
102
Distribution: less than 10 bytes
.......
3
10 to
19 bytes
........
13
20 to
29 bytes
........
6
30 to
49 bytes
........
75
50 to
74 bytes
........
86
75 to
99 bytes
........
93
100 to 249 bytes
........
235
250 to 499 bytes
........
0
500 to 749 bytes
........
0
750 to 999 bytes
........
0
1000 to 1499 bytes
........
0
1500 to 1999 bytes
........
0
2000 to 3999 bytes
........
0
more than 4000 bytes ........
0
The CL command displays the following:

Number of frames: The total number of frames analyzed.
Smallest frame: The length, in bytes, of the smallest frame.
Largest frame: The length, in bytes, of the largest frame.
Mean length: The average frame length based on all frames analyzed.
Distribution: The number of frames analyzed that fall into each size category.
The CL command also has the following operations:
STOP: To stop a capture before the entire frame sample has been collected.
Since the capture is carried out in background mode, you can execute the STOP
operation at any time.
DELETE: To delete the contents of the capture buffer. Since each capture overwrites the previous buffer contents, the DELETE operation is not required before
executing another capture.
4-42
Memotec Inc.
5
Frame Relay over IP
Memotec Inc.
5-1
WAN Frame Relay
5.1
About Frame Relay over IP

The Frame Relay over IP (FRoIP) function allows the NetPerformer to route a PVC
connection over IP instead of Frame Relay. Frame Relay over IP permits using the PVCR
protocol over the Internet to integrate voice and data. It can also be used to prioritize GSM
traffic (refer to the chapter Advanced GSM Applications in the GSM Support module
of this document series).
The following example illustrates a simple network using FRoIP:
Unit A
Frame Relay
Internet
Unit B
Unit C
Unit D
Unit E
Figure 5-1: FRoIP Network
This application has the effect of combining units B and C on the IP/Internet network with
units D and E on the Frame Relay network into one global network managed by central
site unit A. When the PVCR protocol is used, a voice call or data connection from one unit
can be forwarded to any other unit in the network.
5-2
Memotec Inc.
Frame Relay over IP
5.2
NetPerformer Implementation
FRoIP is implemented using a proprietary encapsulation technique over a UDP/IP
protocol stack.
PVCs are used to carry the voice/data traffic, which provides traffic shaping, a
controlled speed and controlled frame size.
The traffic is shaped by:
- Cell Packetization is always ON. The Cell Packetization parameter is not
requested during configuration of PVCR ports in an FRoIP application.
- Controlling the frame size
- Controlling the timeout of frames by means of the Timer in ms for FR Over IP
parameter in the Global profile
- Controlling the information rate of a single PVC by means of the CIR parameter
- Controlling the combined information rate of all PVCs by means of the Global CIR for FR Over IP parameter in the Global profile.
NOTE:
Multihomed IP routing must not be used in an FRoIP application. To turn it

off, enter the following at the NetPerformer console command line:
EP IP MULTIHOMEDTYPE DISABLED
Memotec Inc.
5-3
WAN Frame Relay
5.3
Configuration
There are two areas of the NetPerformer configuration that must be adjusted to support
FRoIP: the global parameters and the PVC parameters.
5.3.1
Global Parameters
The global Frame Relay over IP parameters are configured using the SETUP/GLOBAL
command on the NetPerformer console (see Table 5-1). Refer to the appendix SE/
GLOBAL Configuration Parameters in the Quick Configuration module of this
document series.
Parameter
SNMP Variable
Values
Functions
Global CIR for npsysCirFrOverIp

FR over IP
1 - 100000000
(def. 64000)
Committed Information Rate

(CIR) for the IP port when FRoIP
is activated. The CIR represents
the maximum data throughput
accepted on the IP port.
Timer in ms
npsysTimerFrfor FR over IP OverIp
1 - 1000
(def. 50)
Defines the FRoIP check timer

interval, which controls the timeout of frames on the IP port when
FRoIP is activated.
Max number npsysMaxVoiceof voice chan- CallOverIp

nels over IP
0 - 10000
(def. 10000)
Defines the maximum number of

voice channels permitted on the
IP port for FRoIP. Default 10000
for no call blocking.
npsysLowMaxMax voice
channels over VoiceCallOverIp
IP if high priority data
0 - 10000
(def. 1000)
Defines the maximum number of

voice channels permitted on the
IP port when data traffic has been
assigned the highest priority (with
the port Class parameter).
Table 5-1: Global Parameters for FRoIP
5.3.2
PVC Parameters
The Frame Relay over IP parameters for the PVCs are configured using the SETUP/PVC
command on the NetPerformer console.
The PVC must be set to PVCR or RFC1490 mode
The PVC Port parameter must be set to 0.
5-4
Memotec Inc.
Frame Relay over IP
The PVC parameters used for FRoIP are shown in Table 5-2.
Parameter
SNMP Variable
Values
Functions
Port
pvcPort
0 - max. no. of
data ports (def.
1)
Defines the reference port for

this PVC. Select 0 to assign
this PVC to a virtual IP port
and enable Frame Relay
over IP.
DLCI Address
pvcDlciAddress
0 1022 (def. 0) Defines the DLCI address to

be used by this PVC connection. You must change this
parameter from 0, the
default value for DLCI autolearning, to another value.
There is no link management
for Frame Relay over IP.
Each PVC connection for a
particular reference port must
have a unique DLCI address.
For each connection, the
local and remote DLCI
addresses must match.
Frame over IP,

source
pvcIpSrcAddress
0.0.0.0 255.255.255.
255
(def. 0.0.0.0)
Provides the IP address of

the source that transmits the
frames. If left at its default
value, 000.000.000.000, the
NetPerformer uses the IP
address of the port that sends
the FRoIP frames over the
network. See Frame over IP,
source on page 5-10 for
details.
Frame over IP,

destination
pvcIpDestAddress
0.0.0.0 255.255.255.
255
(def. 0.0.0.0)

the destination unit. The
default value,
000.000.000.000 leaves the
destination undefined; no
traffic can be transferred
between the Internet and
Frame Relay networks. See
Frame over IP, destination
on page 5-11 for details.
Table 5-2: PVC Parameters for FRoIP
Memotec Inc.
5-5
WAN Frame Relay
Parameter
SNMP Variable
Values
Functions
Frame over IP,

port number
pvcIpPort
1-65535
(def. 1024)

the source UDP port that
transmits the FRoIP frames.
This parameter can be used
to allow transmission across
a firewall. See Frame over
IP, port number on page 511 for details.
Frame over IP,

precedence
pvcIpPrecedence
0-7 (def. 0)
Determines the relative priority of the traffic on this PVC

with respect to other traffic.
See Frame over IP, precedence on page 5-12 for
details.
Use a forced
route
pvcForcedRouteActive
NO, YES (def.

NO)
Determines whether all

FRoIP traffic from this PVC
will be sent through a specific
port or PVC connection.
When activated, the Port and
Next hop must also be
defined. See Use a forced
route on page 5-13 for
details.
Table 5-2: PVC Parameters for FRoIP
NOTE:
5-6
The Burst Information Rate (BIR) parameter is not requested for PVCs configured for FRoIP.
Memotec Inc.
Frame Relay over IP
5.4
Example Application
In the application shown in Figure 5-2, voice and data are integrated over the Internet
using Ethernet LAN access and the PVCR protocol.
BOSTON
LOS ANGELES
PBX
LAN
Local Unit
182.160.43.25
IP Network
PBX
LAN
Remote Unit
183.8.127.201
Host
Host
Figure 5-2: FRoIP Application Example
5.4.1
Local Unit Parameters

The following are essential parameter values for configuring the local unit at the
BOSTON site:
BOSTON>DP
DISPLAY PARAMETERS
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
Memotec Inc.
Unit name...............................BOSTON
Unit routing version....................1
Contact name............................Memotec Inc.
Unit location...........................Head Office
Loopback................................NO
Link timeout delay......................0
Transit delay (s).......................4
Daylight saving time....................YES
Default IP address......................000.000.000.000
Default IP mask (number of bits)........0 {000.000.000.000}
Default gateway.........................000.000.000.000
SNMP trap: IP address #1................000.000.000.000
Frame relay status change trap..........DISABLE
Watch power supplies and fan............NONE
Local unit DLCI address.................0
Extension number (no. of digits)........2
Country code............................1
Jitter buffer (ms)......................165
Enable voice/fax log....................YES
Dial timer (s)..........................0
High priority voice class...............YES
Global CIR for FR over IP...............64000
Timer in ms for FR over IP..............50
Max number of voice channels over IP....10000
Max voice channels over IP if high priority data 1000
5-7
WAN Frame Relay
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
5-8
Delay generated by a comma (ms).........250

ISDN G4 Fax PCM switching enable........NO
Auto save configuration delay (s).......10
Enable VTR (Voice Traffic Routing)......NO
Enable Domain Dialing...................YES
Enable hunt forwarding..................YES
Enable user access logging..............NO
Exclusive access to console.............DISABLE
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
Protocol............................ETH AUTO
LAN speed (mbps)....................AUTO
MAC address.........................000000000000
DHCP................................DISABLE
IP address 1........................182.160.043.025
Subnet mask 1 (number of bits)......8 {255.255.255.000}
IP address 2........................000.000.000.000
Subnet mask 2(number of bits).......0 {255.255.255.000}
Frame size..........................1500
IP RIP..............................ENABLE
IP RIP TX/RX........................DUPLEX
OSPF................................DISABLE
IGMP enable.........................NO
IP multicast active.................NO
IP multicast protocol...............NO
NAT enable..........................NO
VLAN enable.........................NO
IPX RIP.............................DISABLE
IPX SAP.............................DISABLE
IPX network number..................00000000
IPX encapsulation...................ETH 802.2
Physical connectivity detection.....DISABLE
Mode.....................................PVCR
Port.....................................0
DLCI.....................................100
Committed Information rate...............32000
Remote unit name.........................LOS_ANGELES
Type.....................................DEDICATED
Timeout (ms).............................1000
Number of retransmission retries.........100
Compression..............................YES
IP address...............................000.000.000.000
Subnet mask (number of bits).............8 {255.000.000.000}
NAT enable...............................NO
BRG connection...........................NO
Filter...................................ALL
Broadcast group..........................NO
Maximum number of voice channels.........10000
Maximum Voice Channels If High Priority Data 10000
Frame over IP, source....................182.160.043.025
Frame over IP, destination...............183.008.127.201
Frame over IP, port number...............1024
Frame over IP, precedence................0
Use a forced route.......................NO
Use this port as default gateway.........NO
Redundant link...........................NO
Memotec Inc.
Frame Relay over IP
5.4.2
Remote Unit Parameters

The following are essential parameter values for configuring the remote unit at the LOS
ANGELES site:
LOS_ANGELES>DP
DISPLAY PARAMETERS
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
GLOBAL>
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
Memotec Inc.
Unit name...............................LOS_ANGELES
Unit routing version....................1
Contact name............................Memotec Inc.
Unit location...........................Western Branch
Loopback................................NO
Link timeout delay......................0
Transit delay (s).......................4
Daylight saving time....................YES
Default IP address......................000.000.000.000
Default IP mask (number of bits)........0 {000.000.000.000}
Default gateway.........................000.000.000.000
Frame Relay status change trap..........DISABLE
Watch power supplies and fan............NONE
Local unit DLCI address.................0
Extension number (no. of digits)........2
Country code............................1
Jitter buffer (ms)......................165
Enable voice/fax log....................YES
Dial timer (s)..........................0
High priority voice class...............YES
Global CIR for FR over IP...............64000
Timer in ms for FR over IP..............50
Max number of voice channels over IP....10000
Max voice channels over IP if high priority data 1000
Delay generated by a comma (ms).........250
ISDN G4 Fax PCM switching enable........NO
Auto save configuration delay (s).......10
Enable VTR (Voice Traffic Routing)......NO
Enable Domain Dialing...................YES
Enable hunt forwarding..................YES
Enable user access logging..............NO
Exclusive access to console.............DISABLE
ETH 1> Protocol............................ETH AUTO

ETH 1> LAN speed (mbps)....................AUTO
ETH 1> MAC address.........................000000000000
ETH 1> DHCP................................DISABLE
ETH 1> IP address 1........................183.008.127.201
ETH 1> Subnet mask 1 (number of bits)......0 {255.255.255.000}
ETH 1> IP address 2........................000.000.000.000
ETH 1> Subnet mask 2(number of bits).......0 {255.255.255.000}
PORT ETH 1> Frame size..........................1500
ETH 1> IP RIP..............................ENABLE
ETH 1> IP RIP TX/RX........................DUPLEX
ETH 1> OSPF................................DISABLE
5-9
WAN Frame Relay
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
ETH
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
1>
IGMP enable.........................NO
IP multicast active.................NO
IP multicast protocol...............NO
NAT enable..........................NO
VLAN enable.........................NO
IPX RIP.............................DISABLE
IPX SAP.............................DISABLE
IPX network number..................00000000
IPX encapsulation...................ETH 802.2
Physical connectivity detection.....DISABLE
Mode.....................................PVCR
Port.....................................0
DLCI.....................................100
Committed Information rate...............32000
Remote unit name.........................BOSTON
Type.....................................DEDICATED
Timeout (ms).............................1000
Number of retransmission retries.........100
Compression..............................YES
IP address...............................000.000.000.000
Subnet mask (number of bits).............8 {255.000.000.000}
NAT enable...............................NO
BRG connection...........................NO
Filter...................................ALL
Broadcast group..........................NO
Maximum number of voice channels.........10000
Maximum Voice Channels If High Priority Data 10000
Frame over IP, source....................183.008.127.201
Frame over IP, destination...............182.160.043.025
Frame over IP, port number...............1024
Frame over IP, precedence................0
Use a forced route.......................NO
Use this port as default gateway.........NO
Redundant link...........................NO
Except for the parameters described below, all parameters for the local and remote units
are explained in the appendices SE/PORT Configuration Parameters on page 6-1 and
SE/PVC Configuration Parameters on page 7-1. The following parameters are specific
to FRoIP:
5.4.3
Frame over IP, source

Console
Frame over IP, source
SNMP
pvcIpSrcAddress
Text-based Config
[pvc#] IpSrcAddress
IP address of the source of traffic over this PVC. If left at its default value,
000.000.000.000, the NetPerformer uses the IP address of the port that sends the FRoIP
frames over the network.
NOTE:
5-10
This parameter appears only if the PVC Port parameter is set to 0 (indicating
Memotec Inc.
Frame Relay over IP
FRoIP support).
Values: 000.000.000.000 - 255.255.255.255

Default: 000.000.000.000
5.4.4

Console
SNMP
pvcIpDestAddress
Text-based Config
[pvc#] IpDestAddress
IP address of the remote unit that receives traffic from this PVC. The default value,
000.000.000.000, leaves the destination undefined; no traffic can be transferred between
Internet and Frame Relay networks.
NOTE:
FRoIP support).
Values: 000.000.000.000 - 255.255.255.255

Default: 000.000.000.000
5.4.5
Frame over IP, port number

Console
Frame over IP, port num- pvcIpPort

ber
SNMP
Text-based Config
[pvc#] IpPort
IP address of the source UDP port that transmits the FRoIP frames. This parameter can be
used to allow transmission across a firewall.
NOTE:
FRoIP support).
Values: 1-65535
Default: 1024
Memotec Inc.
5-11
WAN Frame Relay
5.4.6
Frame over IP, precedence

Console
Frame over IP, precedence
SNMP
pvcIpPrecedence
Text-based Config
[pvc#] IpPrecedence
Determines the relative priority of the traffic on this PVC with respect to other traffic. This
provides a way of prioritizing GSM traffic using FRoIP (refer to the chapter Advanced
GSM Applications in the GSM Support module of this document series).
NOTE:
FRoIP support).
Frame over IP, precedence specifies which IP precedence bit settings should be applied to
traffic on the individual PVC. Three IP Precedence bits are set in the Type of Service
(TOS) field in the IP header, permitting the definition of eight classes of traffic.
Figure 5-3: IP Precedence Bits
The value of the Frame over IP, precedence parameter usually represents classes of
service from 0 to 7:
Typically, the 0 value is used when no QoS is implemented in the backbone network
The specific priority level of each class will vary depending on the IP service
provided (private or public). However, 0 (zero) is commonly associated with the
lowest priority level, and 7 the highest priority level.
Values: 0-7
Default: 0
5-12
Memotec Inc.
Frame Relay over IP
5.4.7
Use a forced route

Console
Use a forced route
SNMP
pvcForcedRouteActive
Text-based Config
[pvc#] ForcedRouteActive
Determines whether all FRoIP traffic from this PVC will be sent through a specific serial
(WAN) or LAN port, digital channel or PVC connection. Set this parameter to YES to
activate the forced route.
NOTE:
FRoIP support).
Values: YES, NO
Default: NO
If you set Use a forced route to YES, the following parameters are also presented at the
NetPerformer console to define the forced route:
5.4.8
Port
Console
Port
SNMP
pvcForcedRoutePort
Text-based Config
[pvc#] ForcedRoutePort
Defines which port, channel or PVC connection will be used to carry all FRoIP traffic
from this PVC. Enter a question mark, ?, at the parameter prompt to view a list of possible
values.
NOTE:
FRoIP support) and Use a forced route is set to YES.
Values: NONE, automatically generated list of ports and PVCs

Default: NONE
5.4.9
Next hop
Console
Next hop
SNMP
Text-based Config
pvcForcedRouteNextHop [pvc#] ForcedRouteNextHop
IP address of the next unit on the path to the final destination that will receive traffic from
Memotec Inc.
5-13
WAN Frame Relay
this PVC. The default value, 000.000.000.000, leaves the destination undefined; no traffic
can be transferred from the remote NetPerformer unit to another unit.
NOTE:
FRoIP support), Use a forced route is set to YES and the Port defined for the
forced route is a LAN port.
Values: 000.000.000.000 - 255.255.255.255

Default: 000.000.000.000
5-14
Memotec Inc.
Frame Relay over IP
5.5
Statistics
The status bits of the Display States (DS) command for the PVC indicate the current status
of Frame Relay over IP operations. Refer to PVC Status on page 4-35.
There are two differences between the display for a FRoIP PVC and other PVCs:
The status bits next to the Information Signals are static and unchanging. The
Active (A) bit is automatically set as soon as the DLCI Address is non-zero and
the PVC port is set to a virtual IP port (0).
The Speed Used statistic indicates the value of the CIR parameter for this PVC,
and not the global CIR value.
All other statistic commands for FRoIP PVCs are the same as those for Frame Relay
PVCs. Refer to Frame Relay Connection Status on page 4-1.
Memotec Inc.
5-15
WAN Frame Relay
5-16
Memotec Inc.
6
SE/PORT Configuration Parameters
Memotec Inc.
6-1
WAN Frame Relay
6.1
FR-NET Protocol
Many of the parameters detailed in this section are also listed when the port is configured
to FR-USER.
FR-NET parameters that are common to other port configurations are described in the
appendix SE/PORT/#/PVCR Configuration Parameters in the WAN/Leased Lines

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 in this section
under the parameter that governs them.
6.1.1
Fallback speed
Console
Fallback speed
SNMP
Text-based Config
ifwanFallBackSpeed-bps, [ifwan#] FallBackSpeedifwanFallBackSpeedbps, FallBackSpeed

Enable
Enable
For all user protocols except ASYNC and PASSTHRU.
Fallback speed for the transmitter. This parameter determines whether the port speed will
be reduced if congestion occurs on the WAN links.
Fallback is applied only if the port is set for DCE Internal clocking. For any other clocking
mode, the Fallback Speed setting is ignored.
Caution: If you disable fallback on a unit set for DCE Internal clocking, make
sure the transmission start level is properly set. Otherwise, data transmission
problems could occur. Refer to the description of the Transmission start level
parameter in the appendix SE/PORT/#/PVCR Configuration Parameters in the
WAN/Leased Lines module of this document series.
NOTE:
Fallback will be disabled if the Congestion Flow Control parameter is left

ON. If you prefer to use fallback rather than flow control for this port, set
Congestion flow control to OFF. This is required for applications where the
attached equipment is unable to process the BECN bits. When Congestion
flow control is OFF, the current value of the Fallback speed parameter will be
used to control fallback of the port speed.
For NetPerformer models covered in this document series.

Set the Fallback Speed to ENABLE (the default value) to allow the NetPerformer to
automatically reduce the port speed when required. Set Fallback Speed to DISABLE to
prevent fallback on the port.

For legacy NetPerformer models.
Select a bit rate that is lower than the value of the Port Speed parameter. As a rule of
6-2
Memotec Inc.
thumb, the fallback speed should be one half of the sum of the speeds of all links to the
destination unit. Set this parameter to 0 to disable fallback.
Caution: The Dual Serial interface card for the SDM-9360, SDM-9380 and
SDM-9585 does not support Fallback.
NOTE:
The range of values given below represents the minimum and maximum fallback speeds possible. Some protocols cannot run at the maximum speeds. For
these, you must select an appropriate lower value.
For NetPerformer models covered in

this manual:
For legacy NetPerformer models:
6.1.2
Values:
DISABLE, ENABLE
Default:
ENABLE
Values:
0 - 2000000
Default:
2400
Frame delay (ms)

Console
Frame delay (ms)
SNMP
ifwanFrameDelay
Text-based Config
[ifwan#] FrameDelay
Delay, in milliseconds, added between each packet transmitted on the port. This delay is
required by some DTE equipment operating at speeds higher than 56 Kbps.
Caution: The Dual Serial interface card for the SDM-9360, SDM-9380 and
SDM-9585 does not support Frame delay.
Values: 0.0, 0.5, 1.0, 1.5, 2.0
Default: 0.0
6.1.3
Management interface
Console
SNMP
ifwanMgmtInterface
Text-based Config
[ifwan#] MgmtInterface
Frame Relay Management Interface Protocol. The LMI (Local Management Interface)
protocol uses reserved DLCI address 1023. The ANNEX-D and the Q.933 protocols use
reserved DLCI address 0.
Set this parameter according to the Management Interface Protocol used on the equipment
attached to the NetPerformer port. Use the NONE value to declare all PVCs on the port
automatically ready. This may be required when you want to enable CLLM, described
later.
The Management interface parameter is also required for a FR-USER port (see FR-
Memotec Inc.
6-3
WAN Frame Relay
USER Port Configuration Parameters on page 3-5). The Management Interface of a FRUSER port must be set to ANNEX-D when using SVCs.
NOTE:
Management Interface activity on the port can be conditioned by the presence

or absence of LMI frames from the Frame Relay network. Use the Reference
Port for Conditional LMI parameter, described later in this section.
Values: LMI, ANNEX-D, Q.933, NONE

Default: LMI
6.1.4
Congestion flow control

Console
SNMP
ifwanFlowControl
Text-based Config
[ifwan#] FlowControl
Congestion flow control notification. If the Congestion Flow Control parameter is ON, the
NetPerformer will set the Forward and Backward Congestion Bits in the header of the
active PVC frame when congestion occurs on the port (due to congestion on the network).
Forward data congestion affects data transmitted from the Frame Relay equipment to the
NetPerformer. Backward data congestion affects data transmitted from the NetPerformer
to the Frame Relay equipment.
NOTE:
If the Congestion Flow Control parameter is left ON, fallback will be disabled. If you prefer to use fallback rather than flow control for this port, set
Congestion Flow Control to OFF. This is required for applications where the
attached equipment is unable to process the BECN bits. When Congestion
Flow Control is OFF, the current value of the Fallback Speed parameter will
be used to control fallback of the port speed.
If the Congestion Flow Control parameter is OFF, the NetPerformer does not set the
congestion bits. In this case, they are reset to zero.
Values: OFF, ON
Default: ON
6.1.5
Enquiry timer (s)

Console
Enquiry timer (s)
SNMP
ifwanEnquiryTimer-s
Text-based Config
[ifwan#] EnquiryTimer-s
Sets the Frame Relay Enquiry Timer, in seconds. For a Frame Relay user port (FR-USER
6-4
Memotec Inc.
protocol), the NetPerformer will poll the network with STATUS ENQUIRY frames when
this timer expires. For a Frame Relay network port (FR-NET protocol), the NetPerformer
will log errors if no STATUS ENQUIRY frames have been received before the timer
expires.
NOTE:
The equivalent NNI system parameter names used in the Frame Relay Forum
Document FRF.2.1 (July, 1995) are T391 for Enquiry Timer on a FR-USER
port and T392 for Enquiry Timer on a FR-NET port.
Values: 1 - 30
Default: 10
6.1.6
CLLM function
Console
CLLM function
SNMP
ifwanCllm
Text-based Config
[ifwan#] Cllm
Enables or disables Consolidated Link Layer Management (CLLM) on the Frame Relay
port. To implement CLLM, set the ports CLLM parameter to ON.
This management feature reduces the risk of congestion in the network as well as the
number of frames discarded. It supplements the flow control feature based on the Forward
and Backward Congestion Bits (FECN and BECN) and will work even if there are no
frames moving backward to the source of congestion.
Data Link Connection Identifier (DLCI) 1023 is used to send Link Layer control messages
from the Frame Relay network to the user device. These messages are formatted as CLLM
frames indicating:
the type of congestion that has occurred
which PVCs should reduce their Committed Information Rate (CIR).
When a Frame Relay port is configured for CLLM and a CLLM frame arrives, the
NetPerformer automatically reduces the CIR of the PVCs identified in the frame.
Values: OFF, ON
Default: OFF
6.1.7
Reference port for conditional LMI

Console
SNMP
Reference port for condi- ifwanCondLMIPort

tional LMI
Text-based Config
[ifwan#] CondLMIPort
For FR-NET protocol only.
Link Management Interface activity on the FR-NET port is conditioned by the presence or
Memotec Inc.
6-5
WAN Frame Relay
absence of LMI frames on the port specified by this parameter. Enter the number of the
FR-USER port that connects to the Frame Relay network. When this parameter is set to 0,
Conditional LMI is disabled.
Conditional LMI allows LMI activity on the port to be conditioned by the presence or
absence of LMI from the Frame Relay network. If the connection to the network goes
down or the network no longer sends LMI to the NetPerformer, the FR-NET port stops
sending LMI to the destination device. In this way, the FR-NET port is able to indicate to
the end device whether the connection to the Frame Relay network is still alive.
The purpose of Conditional LMI is to reflect the status of the Frame Relay network to a
device connected to a NetPerformer unit when that NetPerformer is configured as a Frame
Relay switch.
Conditional LMI to port 1
Frame Relay
USER device
1
NetPerformer
FR-NET 2
LMI
FR-USER
LMI
Frame
Relay
LMI activity on port 2 stops if

no LMI received on port 1
The FR-NET port must have a reference port for Conditional LMI to determine which
Frame Relay user port (FR-USER) it should examine when generating LMI frames. If the
reference port is set to 0, Conditional LMI is disabled. If it is set to a non-zero value, the
FR-NET port will not respond to an LMI request if the referenced FR-USER port no
longer detects LMI. This feature affects Transparent and Multiplex PVCs.
Values: 0 - 2000
Default: 0 (disabled)
6.1.8
Drop signals on LMI down

Console
Drop signals on LMI

down
SNMP
Text-based Config
ifwanDropSignalsOnLMI- [ifwan#] DropSignalsOnDown

LMIDown
Defines the behavior of modem signals when the Frame Relay management interface is
down.
When this parameter is set to YES, the modem signals will go down when the
management interface is down. The delay before the drop of modem signals is determined
as 3 times the current value of the Enquiry Timer parameter. For example, if the Enquiry
Timer is set to 10 seconds, the modem signals will drop 30 seconds after the management
interface is declared down.
6-6
Memotec Inc.
The modem signals are reactivated 3 seconds after they are dropped. This activation/
deactivation cycle continues as long as the management interface is declared down; that is,
as long as no response is received from networks connected to the FR-USER port, or no
request is received from the user equipment connected to the FR-NET port. Activation and
deactivation of the modem signals can be observed from the DTR control LED, which
repeatedly turns off for 3 seconds and on for 30 seconds (if Enquiry Timer set to 10) while
the Frame Relay management interface is down.
The default value of the Drop Signals on LMI Down parameter is NO. When set to this
value, no action is taken to drop the modem signals when the Frame Relay management
interface goes down. In this case, the DTR control LED stays green throughout the
management interface failure.
Values: NO, YES
Default: NO
Memotec Inc.
6-7
WAN Frame Relay
6.2
6.2.1
FR-USER Protocol
Report cycle
Console
Report cycle
SNMP
ifwanReportCycle
Text-based Config
[ifwan#] ReportCycle
For FR-USER protocol only.

The value of this parameter determines the number of STATUS ENQUIRY frames that
the NetPerformer will send before sending a full status enquiry to the network. It is also
used in determining the number of restart errors for PVCs in PVCR mode. Refer to PVC
Errors on page 4-21.
In response to a full status enquiry the network sends a full status report. This report
indicates the currently active PVC on the network. The NetPerformer uses this
information to learn PVC DLCI addresses from the network, and to determine if a
particular PVC is ready to receive data.
NOTE:
The equivalent NNI system parameter name used in the Frame Relay Forum
Document FRF.2.1 (July, 1995) is N391.
Values: 1 - 256
Default: 6
6.2.2
SVC address type

Console
SVC address type
SNMP
ifwanSvcAddressType
Text-based Config
[ifwan#] SvcAddressType

Determines the type of SVC network addressing supported. Select either E.164 or X.121
to enable SVC addressing. Select NONE to disable SVC addressing.
NOTE:
SVCs are activated by setting the Use SVC Connection parameter for the
Voice Mapping Table entry to YES. Refer to the section on Configuring the
Voice Mapping Table in the Digital Voice module of this document series.
If you are using SVCs, ensure that the FR-USER port Management interface parameter is
set to ANNEX-D, and that the voice port configuration meets the following conditions:
SVCs to reach their destination.
6-8
Memotec Inc.
If you are using both SVCs and fax/modem, set the Maximum Fax/Modem Rate
parameter to the maximum speed the voice port may require for fax or modem
communications.
The Link Down Busy, Fax/Modem Relay and Maximum Fax/Modem Rate voice port
parameters are described in the Digital Voice module of this document series.
Values: NONE, E.164, X.121
Default: NONE
When an address type value is selected for the SVC address type parameter, additional
SVC parameters are also available, as shown in this example:
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
PORT
6.2.3
104>
104>
104>
104>
104>
104>
104>
104>
104>
104>
SVC
SVC
SVC
SVC
SVC
SVC
SVC
SVC
SVC
SVC
address type (def:NONE) ? E.164

network address (def:) ? 123456789012345
max Tx Ack timeout T200 (1-5,def:1) ?
inactive timeout T203 (1-60,def:30) ?
Iframe retransmissions N200 (1-16,def:3) ?
setup timeout T303 (1-30,def:4) ?
disconnect timeout T305 (1-30,def:30) ?
release timeout T308 (1-30,def:4) ?
call proceeding timeout T310 (1-30,def:4) ?
status enquiry timeout T322 (1-30,def:4) ?
SVC network address

Console
SVC network address
SNMP
Text-based Config
ifwanSvcNetworkAddress [ifwan#] SvcNetworkAddress

The SVC network address for this Frame Relay port. This may be an E.164 or X.121
address, depending on the value of the SVC address type parameter.
Values: 0 - 9 for each digit
Default: none
6.2.4
SVC max Tx Ack timeout T200

Console
SNMP
SVC max Tx Ack timeout ifwanSvcMaxTxTimeoutT200

T200
Text-based Config
[ifwan#]
SvcMaxTxTimeoutT200

The value of this parameter sets the maximum delay, in seconds, that is allowed between
Memotec Inc.
6-9
WAN Frame Relay
each transmission and its acknowledgement. This timeout is referred to as T200.

Values: 1 - 5
Default: 1
6.2.5
SVC inactive timeout T203

Console
SVC inactive timeout

T203
SNMP
ifwanSvcInactiveTimeoutT203
Text-based Config
[ifwan#]
SvcInactiveTimeoutT203

The value of this parameter sets the maximum number of seconds that can elapse without
activity on the port. This timeout is referred to as T203.
Values: 1 - 60
Default: 30
SVC Iframe retransmissions N200
Console
SNMP
IfwanSvcIframeRetransmissionsN200
Text-based Config
[ifwan#] SVCIframeRetransmissionsN200

The value of this parameter sets the maximum number of retransmissions of I frames for
the Q.922 layer. This number is referred to as N200.
Values: 1 - 16
Default: 3
6.2.6
SVC setup timeout T303

Console
SNMP
ifwanSvcSetupTimeoutT303
Text-based Config
[ifwan#]
SvcSetupTimeoutT303

The value of this parameter sets the maximum delay, in seconds, allowed for the network
to respond to a Q.933 setup message. This timeout is referred to as T303.
Values: 1 - 30
Default: 4
6-10
Memotec Inc.
6.2.7
SVC disconnect timeout T305

Console
SVC disconnect timeout

T305
SNMP
IfwanSvcDisconnectTimeoutT305
Text-based Config
[ifwan#] SvcDisconnectTimeoutT305

to respond to a Q.933 disconnect message. This timeout is referred to as T305.
Values: 1 - 30
Default: 30
6.2.8
SVC release timeout T308

Console
SVC release timeout

T308
SNMP
ifwanSvcReleaseTimeoutT308
Text-based Config
[ifwan#]
SvcReleaseTimeoutT308

to respond to a Q.933 release message. This timeout is referred to as T308.
Values: 1 - 30
Default: 4
6.2.9
SVC call proceeding timeout T310

Console
SNMP
Text-based Config
IfwanSvcCallProceeding- [ifwan#] SvcCall-ProTimeout

ceedingTimeout

to respond to a Q.933 call proceeding message. This timeout is referred to as T310.
Values: 1 - 30
Default: 4
Memotec Inc.
6-11
WAN Frame Relay
6.2.10
SVC status enquiry timeout T322

Console
SNMP
SVC status enquiry time- ifwanSvcStatusTimeoutout T322

T322
Text-based Config
[ifwan#]
SvcStatusTimeoutT322

to respond to a Q.933 status enquiry message. This timeout is referred to as T322.
Values: 1 - 30
Default: 4
6-12
Memotec Inc.
7
SE/PVC Configuration Parameters
Memotec Inc.
7-1
WAN Frame Relay
7.1
About SE/PVC Configuration Parameters

Special PVC parameters required for a Frame Relay over IP application are described in
PVC Parameters for FRoIP on page 5-5.
7.1.1
PVC number
Console
PVC number
SNMP
pvcEntry, pvcIndex
Text-based Config
[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: Regional unit:
1 - 300
Turbo data only unit: 1 - 128
Other models:
1 - 96
Default: 1
7.1.2
Mode
Console
Mode
SNMP
pvcMode
Text-based Config
[pvc#] Mode
Determines the PVC operating mode. The following PVC modes are available on the
NetPerformer base product when the Voice transport method (a global parameter) is set to
POWERCELL:
OFF: The PVC is inactive. When this setting is chosen, no further PVC parameters will be presented at the console.
PVCR: The PVC is used over a Frame Relay network to transport data using
Memotecs variable cell relay technology to access a remote NetPerformer. The
local NetPerformer port must be a Frame Relay port (FR-USER or FR-NET protocol).
RFC1490: The PVC is used over a Frame Relay network to access an RFC1490compatible FRAD (Frame Relay Access Assembler/Disassembler). No fragmentation or data compression is performed. The local NetPerformer port must be a
Frame Relay port (FR-USER or FR-NET protocol).
MULTIPLEX: The PVC is used to multiplex data coming from a Frame Relay
end-user device. The local NetPerformer port must be set to the FR-NET protocol.
BROADCAST: The PVC is used to send broadcast frames to the multicast
server (the Frame Relay switch). The DLCI you define for this PVC is the Mdlci.
7-2
Memotec Inc.
The local NetPerformer port must be an analog voice port. Voice broadcasting
concepts are described in the Analog Voice module of this document series.
Broadcast mode is available only on NetPerformer models that support voice/fax
transmissions.
TRANSP: The PVC is used to switch data coming from one end-user device
directly to the network and the destination end-user device without alteration on
the frame. For this mode the PVC uses either two Frame Relay network ports
(FR-NET protocol) or one Frame Relay user port (FR-USER protocol) and one
network port.
When the Voice transport method is set to SIP VoIP, only the RFC1490 PVC mode is
available.
When the GSM A-bis/ter licensed software option is installed, the mode can be set to GSM
in addition to the modes listed above. Refer to the GSM Support module of this
document series for information on this PVC mode.
When the ATM licensed software option is installed, the following PVC modes are
available in addition to the modes listed above:
ATMPVCR, ATM-MULTIPLEX, ATMPPP, FRF.8, RFC1483
These ATM PVC modes are explained further in the ATM Option module of this
document series.
Values: OFF, PVCR, RFC1490, MULTIPLEX, BROADCAST,
TRANSP
Default: OFF
Memotec Inc.
7-3
WAN Frame Relay
7.2
PVCR Mode
Additional parameters for a PVCR PVC defined for FRoIP (Port parameter set to 0) are
described in the chapter Frame Relay over IP on page 5-1.
7.2.1
Port
Console
Port
SNMP
pvcPort
Text-based Config
[pvc#] Port
The Frame Relay port used by the PVC. The port you select must be configured as a
Frame Relay port using the port Protocol parameter (see Frame Relay Port Configuration
Parameters on page 3-2).
When the PVC is in PVCR or RFC1490 mode, its associated port must be a Frame Relay
user port (FR-USER protocol) to be able to interface with a Frame Relay network. When
the PVC is in Multiplex mode, its associated port must be a Frame Relay network port
(FR-NET protocol) to be able to interface with a Frame Relay end-user device.
NOTE:
More than one PVC can access the same Frame Relay port.
Set the Port parameter to 0 to configure the PVC for a Frame Relay over IP application.
Refer to Frame Relay over IP on page 5-1.
Values: 0, numeric range of values determined by the number of ports
on the NetPerformer
Default: 1
7.2.2
DLCI address
Console
DLCI address
SNMP
pvcDlciAddress
Text-based Config
[pvc#] 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.
7-4
Memotec Inc.
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.
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)
7.2.3
Committed Information rate

Console
Committed Information
rate
SNMP
pvcInfoRate
Text-based Config
[pvc#] 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),
Memotec Inc.
7-5
WAN Frame Relay
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 discussion of
Information Rate Parameters in the Extended Parameters module of this document
series.
Values: 4000 - 6144000
Default: 56000
7.2.4
Burst Information rate

Console
SNMP
pvcBurstInfoRate
Text-based Config
[pvc#] 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. Refer to the discussion of Information Rate Parameters in the Extended Parameters module of this document series.
Values: 4000 - 6144000

Default: 56000
7.2.5
Remote unit name

Console
Remote unit name
SNMP
pvcRemoteUnit
Text-based Config
[pvc#] 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. Refer to the appendix SE/GLOBAL
Configuration Parameters in the Quick Configuration module of this document
series. A unit name must be defined for each NetPerformer that will be participating in the
network.
Values: Maximum 32-character alphanumeric string, determined by
remote NetPerformer setup
Default: no value
7-6
Memotec Inc.
7.2.6
Type
Console
Type
SNMP
Text-based Config
pvcType
[pvc#] Type
This parameter defines the PVC as a dedicated or backup connection. The possible
settings for this parameter are the following:
DEDICATED: Communication is carried out over a dedicated PVC connection.
ANSWER: The PVC can receive calls only.
CALL-BKUP: Call mode using a backup recovery mechanism. The PVC is activated in case of failure on the dedicated PVCR connections or PVCs.
When you install a backup PVC connection between two NetPerformer units, one unit
must be configured with a call-backup PVC (CALL-BKUP setting) and the other with an
answer-only PVC (ANSWER setting).
Values: DEDICATED, ANSWER, CALL-BKUP
Default: DEDICATED
If you choose CALL-BKUP as the PVC type, the following parameters are displayed for
setting the backup characteristics:
PVC
PVC
PVC
PVC
PVC
...
7.2.7
3>
3>
3>
3>
3>
Type (def:DEDICATED) ? CALL-BKUP

Delay before call activation (1-255,def:10) ?
Delay before call deactivation (1-255,def:120) ?
Call activation timer (30-255,def:30) ?
Backup (def:ANY) ?
Delay before call activation

Console
SNMP
pvcDelayBeforeCallActivation-s
Text-based Config
[pvc#] DelayBeforeCallActivation-s
For PVCR mode, Call-Backup type only.

Delay, in seconds, before activating the backup PVC when a line failure has occurred on a
dedicated PVCR connection or PVC.
Values: 1 - 255
Default: 30
Memotec Inc.
7-7
WAN Frame Relay
7.2.8
Delay before call deactivation

Console
SNMP
pvcDelayBeforeCallDeactivation-s
Text-based Config
[pvc#] DelayBeforeCallDeactivation-s

Delay, in seconds, before deactivating the backup PVC after the dedicated PVCR
connection or PVC has been restored.
Values: 1 - 255
Default: 120
7.2.9
Call activation timer

Console
SNMP
pvcCallActivationTimer
Text-based Config
[pvc#] CallActivationTimer

This parameter defines the wait time, in seconds, that is provided to allow the
NetPerformer to establish a backup PVC using a dial phone number. An extended delay
may be necessary when modem signals are required to raise the backup PVC. If the Dial
Timeout expires, the connection procedure is aborted and the backup PVC returns to
inactive status.
Values: 30 - 255
Default: 120
7.2.10
Backup
Console
Backup
SNMP
pvcBackup
Text-based Config
[pvc#] Backup

The PVCR connections and PVCs that this PVC backs up. Backup PVCs can be
configured to monitor and backup any PVCR connection or PVC that fails (ANY), or all
PVCR connections and PVCs (ALL).
Values: ANY, ALL
Default: ANY
If you choose ANSWER as the PVC type, no extra parameters are required:
PVC 2> Type (def:DEDICATED) ? ANSWER
PVC 2> Timeout (ms) (1000-30000,def:1000) ?
...
7-8
Memotec Inc.
7.2.11
Timeout (ms)
Console
Timeout (ms)
SNMP
pvcTimeout-ms
Text-based Config
[pvc#] Timeout-ms
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.
Values: 1000 - 30000
Default: 1000
7.2.12
Number of retransmission retries

Console
SNMP
Number of retransmission pvcRetry

retries
Text-based Config
[pvc#] Retry
Maximum number of successive retries before the PVC connection is declared down.
Values: 1 - 1000
Default: 100
7.2.13
Compression
Console
Compression
SNMP
pvcCompression
Text-based Config
[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
7.2.14
IP address
Console
IP address
SNMP
pvcIpAddress
Text-based Config
[pvc#] 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
Memotec Inc.
7-9
WAN Frame Relay
IP Address parameter. For details, refer to the appendix SE/GLOBAL Configuration

Parameters in the Quick Configuration module of this document series.
NOTE:
If you configure the IP Address parameter, the value of the global Default IP
Address parameter is ignored for this PVC.
Values: 000.000.000.000 - 255.255.255.255

Default: 000.000.000.000
7.2.15
Subnet mask (number of bits)

Console
Subnet mask (number of

bits)
SNMP
pvcSubnetMask
Text-based Config
[pvc#] 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
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:
The NetPerformer supports super-netting as well as subnetting. To accommodate this the subnet mask of any IP address can 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: 8 (equivalent to 255.000.000.000)
7-10
Memotec Inc.
7.2.16
NAT enable
Console
NAT enable
SNMP
pvcNatEnable
Text-based Config
[pvc#] NatEnable
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) ?
7.2.17
NAT rule
Console
NAT rule
SNMP
pvcNatRule
Text-based Config
[pvc#] 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
Values: 1 - 10
Default: none
7.2.18
NAT side
Console
NAT side
SNMP
pvcNatSide
Text-based Config
[pvc#] 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).
Memotec Inc.
7-11
WAN Frame Relay
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
7.2.19
IP RIP
Console
IP RIP
SNMP
pvcIpRip
Text-based Config
[pvc#] 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 section IP Routing with RIP Version 2 in the LAN Connection
and IP Networks module 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 module 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
7-12
Memotec Inc.
PVC 1> IP RIP TX/RX (def:DUPLEX) ?

PVC 1> IP RIP Authentication (def:NONE) ?
PVC 1> IP RIP Password (def:) ?
7.2.20
IP RIP TX/RX
Console
IP RIP TX/RX
SNMP
pvcIpRipTxRx
Text-based Config
[pvc#] IpRipTxRx
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.
Values: DUPLEX, TX ONLY, RX ONLY
Default: DUPLEX
7.2.21
IP RIP authentication
Console
SNMP
pvcIpRipAuthType
Text-based Config
[pvc#] IpRipAuthType
For IP RIP Version 2 only.

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
7.2.22
IP RIP password
Console
IP RIP password
SNMP
pvcIpRipPassword
Text-based Config
[pvc#] IpRipPassword
For IP RIP Version 2 only.

Defines the password to be used on this PVC. The password allows the authentication
procedure to generate and/or verify the authentication field in the RIP header.
Memotec Inc.
7-13
WAN Frame Relay
NOTE:
The value of the IP RIP Password parameter must be the same for each interface on both sides of the network.
Values: alphanumeric string, maximum 8 characters

Default: none
7.2.23
OSPF
Console
SNMP
OSPF
pvcOspfEnable
Text-based Config
[pvc#] 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.
Values: DISABLE, ENABLE
Default: DISABLE
NOTE:
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
When OSPF is enabled, additional OSPF parameters appear on the console

and must be defined:
1>
1>
1>
1>
1>
1>
1>
1>
OSPF
OSPF
OSPF
OSPF
OSPF
OSPF
OSPF
OSPF
(def:DISABLE) ? ENABLE
Area ID (def:000.000.000.000) ?
Transit delay (1-360,def:1) ?
Retransmit interval (1-360,def:5) ?
Hello interval (1-360,def:10) ?
Dead interval (1-2000,def:40) ?
Authentication type (def:NONE) ?
Metric cost (1-65534,def:10) ?
These parameters are identical to those defined on a PVCR port. For details, refer to the
appendix SE/PORT/#/PVCR Configuration Parameters in the WAN/Leased Lines
module of this document series. Further information on NetPerformer support of OSPF
routing is found in the chapter OSPF Network Support of the LAN Connection and IP
Networks module.
7-14
Memotec Inc.
7.2.24
IP multicast active
Console
IP multicast active
SNMP
pvcIpMulticastActive
Text-based Config
[pvc#] 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
7.2.25
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. Refer to the LAN Connection and IP Networks module of this
document series.
NOTE:
When IP multicast active is set to YES, the IP multicast protocol parameter is

also displayed at the console.
IP multicast protocol
Console
SNMP
pvcIpMulticastProtocol
Text-based Config
[pvc#] IpMulticastProtocol
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
Memotec Inc.
7-15
WAN Frame Relay
7.2.26
IPX RIP
Console
IPX RIP
SNMP
pvcIpxRip
Text-based Config
[pvc#] IpxRip
For a unit with Voice transport method set to POWERCELL only.
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.

Default: DISABLE
7.2.27
IPX SAP
Console
IPX SAP
SNMP
pvcIpxSap
Text-based Config
[pvc#] 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.
Default: DISABLE
7.2.28
IPX network number

Console
IPX network number
SNMP
pvcIpxNetNum
Text-based Config
[pvc#] IpxNetNum
Defines the network number of the IPX node that is connected to the PVC. This number is
a 4-byte 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
7-16
Memotec Inc.
number must be defined, using the Setup IPX menu. For details, refer to the Digital Data
Values: 00000000 - FFFFFFFF
Default: 00000000
7.2.29
BRG connection
Console
BRG connection
SNMP
pvcBrgConnection
Text-based Config
[pvc#] BrgConnection

Allows or disallows a bridge connection. Set this parameter to YES if the PowerCell or
RFC1490-compatible unit at the remote end requires bridged frames. If bridged data is not
required, a NO value will prevent the transmission of unnecessary bridged frames from
this PVC, thus reducing network costs.
Values: NO, YES
Default: NO
7.2.30
Filter
Console
Filter
SNMP
pvcFilter
Text-based Config
[pvc#] Filter
Traffic filters can be applied to a single PVC. 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/FILTER command.
Use DP/FILTER to view the current listing. Refer to the Quality of Service
(QoS) module 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.
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
Memotec Inc.
7-17
WAN Frame Relay
7.2.31
Broadcast group
Console
Broadcast group
SNMP
pvcBroadcastGroup
Text-based Config
[pvc#] BroadcastGroup
Determines whether this 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 module 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 set to 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
7.2.32
Maximum number of voice channels

Console
Maximum number of
voice channels
SNMP
pvcMaxChannels
Text-based Config
[pvc#] MaxChannels
Defines the maximum number of incoming and outgoing voice 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
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
7-18
Memotec Inc.
bandwidth that can be used by all voice calls. For further information refer to the section
Voice Traffic Control in the Advanced Voice Features module of this document
series.
Values: 0 - 10000
Default: 10000 (no blocking)
7.2.33
Maximum Voice Channels If High Priority Data

Console
SNMP
Maximum Voice
pvcLowMaxChannels
Channels If High Priority Data
Text-based Config
[pvc#] LowMaxChannels
Defines the maximum number of incoming and outgoing voice channels permitted at one
time on this PVC connection when one or more transparent user port (Protocol set to
HDLC, T-ASYNC, R-ASYNC, BSC, COP or PASSTHRU) 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 user ports is configured with the port Class parameter.
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.
NOTE:
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.
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. Refer to the Extended Parameters module in this document
series.
Memotec Inc.
7-19
WAN Frame Relay

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)
7.2.34
Use this port as default gateway

Console
Use this port as default

gateway
SNMP
pvcIsDefaultGateway
Text-based Config
[pvc#] IsDefaultGateway
Determines whether this PVC will provide the route for the default gateway. Set to YES
for default gateway functionality. The PVC connection must be up to provide this
functionality.
Values: NO, YES
Default: NO
7.2.35
Redundant link
Console
Redundant link
SNMP
pvcRedundantLink
Text-based Config
[pvc#] RedundantLink
Determines whether this PVC will be used as a redundant link in a redundant system. Set
to YES for redundant link functionality. Refer to the Redundancy Option module of this
document series for further information.
Values: NO, YES
Default: NO
7-20
Memotec Inc.
7.3
7.3.1
RFC1490 Mode
Frame size
Console
Frame size
SNMP
pvcMaxFrame
Text-based Config
[pvc#] MaxFrame
Determines the 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
7.3.2
IP connection
Console
IP connection
SNMP
pvcIpConnection
Text-based Config
[pvc#] 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
7.3.3
IPX connection
Console
IPX connection
SNMP
pvcIpxConnection
Text-based Config
[pvc#] IpxConnection

Allows or disallows an IPX connection. Set this parameter to YES if the RFC1490-
compatible FRAD at the remote end requires IPX packets. If IPX encapsulated data is not
required, a NO value will prevent the transmission of unnecessary IPX packets from this
PVC, thus reducing your network costs.
Values: NO, YES
Default: YES
Memotec Inc.
7-21
WAN Frame Relay
7.3.4
LLC connection
Console
LLC connection
SNMP
pvcLlcConnection
Text-based Config
[pvc#] LlcConnection
Allows or disallows an LLC connection. Set this parameter to YES if the RFC1490compatible FRAD at the remote end requires LLC frames. If LLC data is not required, a
NO value will prevent the transmission of unnecessary LLC frames from this PVC, thus
reducing your network costs.
Values: NO, YES
Default: YES
7-22
Memotec Inc.
7.4
7.4.1
MULTIPLEX Mode
Remote PVC number
Console
Remote PVC number
SNMP
pvcRemotePvc
Text-based Config
[pvc#] RemotePvc
For a PVC in MULTIPLEX mode only.
The remote PVC to which data from the local PVC is sent. Specify the remote PVC
number.
Values: 1 - 300
Default: the local PVC number
7.4.2
Class number
Console
Class number
SNMP
pvcClass
Text-based Config
[pvc#] Class
For a PVC in MULTIPLEX mode only.
The priority class for traffic on this PVC. Classes are defined according to bandwidth
weight. For further information, refer to the Quality of Service (QoS) module of this
document series.
Values: 1 - 8, HIGH PRIORITY
Default: 3
Memotec Inc.
7-23
WAN Frame Relay
7.5
7.5.1
TRANSP Mode
User port
Console
User port
SNMP
pvcUserPort
Text-based Config
[pvc#] UserPort
The Frame Relay user port used by the transparent PVC. The port you select must be
configured as a Frame Relay port (FR-USER or FR-NET protocol) using the port Protocol
parameter (see Frame Relay Port Configuration Parameters on page 3-2). All frames
received on the user port side for that PVC will be transmitted to the network port side (see
next parameter).
Values: automatically generated list of ports
Default: 1
7.5.2
Network port
Console
Network port
SNMP
pvcNetworkPort
Text-based Config
[pvc#] NetworkPort
The Frame Relay network port used by the transparent PVC. The port you select must be
configured as a Frame Relay network port (FR-NET protocol) using the port Protocol
parameter (see Frame Relay Port Configuration Parameters on page 3-2). All frames
received on the network port side for that PVC will be transmitted to the user port side.
NOTE:
When a Transparent PVC is used for X.25 encapsulation to Frame Relay, the
Network Port refers to the X.25 port (NetPerformer data port configured with
the X25 protocol). X.25 encapsulation is activated when the Transparent PVC
is associated with an X.25 port.
Values: automatically generated list of ports

Default: 1
7.5.3
User DLCI
Console
User DLCI
SNMP
pvcUserDlci
Text-based Config
[pvc#] UserDlci
The DLCI address of the transparent PVC on the user side.
7-24
Memotec Inc.
Values: 0 - 1022
Default: 0
7.5.4
Network DLCI
Console
Network DLCI
SNMP
pvcNetworkDlci
Text-based Config
[pvc#] NetworkDlci
The DLCI address of the transparent PVC on the network side.

Values: 0 - 1022
Default: 0
Memotec Inc.
7-25
WAN Frame Relay
7-26
Memotec Inc.
Index
A
Answer-only PVC 7-7
Authentication type, for IP RIP 7-13
Auto-learning of DLCI address 7-4
B
Backup
for PVC 7-8
Backup PVC 7-7
call delay 7-7
Bad frames
display of 4-19
BRG connection
for PVC 7-17
Broadcast group
for PVC 7-18
for PVC 7-6
C
for PVC 7-8
Call-backup PVC 7-7
Channel sequence errors, display of 4-24
CI display 4-31, 4-35
CIR 2-3
Class number 7-23
CLLM function
Frame Relay 6-5
Committed Information rate
for PVC 7-5
Compression
for PVC 7-9
Configuration
PVC parameters 3-8
Congestion
Frame Relay 1-3
Frame Relay 6-4
Counters 4-3, 4-18, 4-29
resetting 4-17
D
DC command 4-3, 4-18, 4-29
Dedicated PVC 7-7
WAN Frame Relay
for PVC 7-7

for PVC 7-8
Display Errors command 4-18
Display States command
for PVCs 4-35
DLCI
displaying for PVC 4-37
displaying for SVC 4-40
DLCI address 1-3
for PVC 7-4
DLCI Address, for FRoIP 5-5
Drop signals on LMI down
Frame Relay 6-6
DS command
for PVCs 4-35
DTE/DCE
display of 4-34
E
Enquiry timer 6-4
Errors
display of 4-18
resetting counters 4-17
F
Fallback
disabling 6-2
Fallback speed 6-2
Filter
for PVC 7-17
Frame delay 6-3
Frame over IP, destination 5-5, 5-11
Frame over IP, port number 5-6, 5-11
Frame over IP, precedence 5-6, 5-12
Frame over IP, source 5-5, 5-10
Frame Relay 1-2
congestion monitoring 1-3
management protocol 1-3
protocols 2-2
Frame Relay Forum, parameter names used 2-6
Frame Relay full status report 7-4
Frame Relay over IP
Application 5-7
Configuration 5-4
Implementation 5-3
Statistics 5-15
Frame size
for PVC 7-21
G
Global CIR for FR over IP 5-4
Global parameters
for FRoIP 5-4
Groups
definition of 4-25
I
Incomplete frames 4-20
Information signal
inactive 4-36, 4-40
Information signals
Information status
of PVCs 4-36
INTERFACE
displaying for Frame Relay 4-34
Interface
display of 4-34
IP address
for PVC 7-9
IP connection
for PVC 7-21
IP multicast active
for PVC 7-15
for PVC 7-15
IP RIP
directionality, for PVC link 7-13
enabling 7-12
for PVC 7-12
for PVC 7-13
IP RIP password
for PVC 7-13
IP RIP TX/RX
for PVC 7-13
IP routing 7-12, 7-13
IPX connection
for PVC 7-21
IPX network number
for PVC 7-16
IPX RIP
for PVC 7-16
IPX RIP routing 7-16
IPX routing 7-16
IPX SAP
for PVC 7-16
IPX SAP routing 7-16
L
LLC connection
for PVC 7-22
Logical state
of ports 4-31, 4-35
of PVCs 4-36
M
Frame Relay 6-3
Max number of voice channels over IP 5-4
Max voice channels over IP if high priority data 5-4
Maximum number of voice channels
for PVC 7-18
Maximum Voice Channels If High Priority Data
for PVC 7-19
Mode
for PVC 7-2
MODEM SIGNALS
Modem signals
status, display of 4-34
MULTIPLEX mode
channel sequence errors 4-24
N
NACFB display 4-36, 4-40
NAT enable
for PVC 7-11
NAT rule
for PVC 7-11
NAT side
for PVC 7-11
Network DLCI
for PVC 7-25
Network number, for IPX routing 7-16
Network port
for PVC 7-24
Next hop 5-13
NNI system parameters 2-6
displaying on PVC 4-6
displaying on SVC 4-10
Number of BECN transmitted, displaying on SVC 411
Number of channel abort errors
Memotec Inc.

Number of channel sequence errors
Number of CLLM frames received, displaying on
PVC 4-7
Number of compressor errors
Number of errors
Number of invalid frames discarded
Number of invalid octets discarded
Number of octets discarded (bad)
Number of octets discarded (CRC)
Number of restarts
WAN Frame Relay

Number of retransmission retries
for PVC 7-9
Number of retries
Number of underruns
O
Operating mode
of PVC 2-2
OSPF
for PVC 7-14
P
Parameter list
Backup, for PVC 7-8
BRG connection, for PVC 7-17, 7-20
Broadcast group, for PVC 7-18
Burst Information rate, for PVC 7-6
Call activation timer, for PVC 7-8
Class number, for PVC 7-23
CLLM function, Frame Relay 6-5
Committed Information rate, for PVC 7-5
Compression, for PVC 7-9
Congestion flow control, Frame Relay 6-4
Delay before call activation, for PVC 7-7
Delay before call deactivation, for PVC 7-8
Drop signals on LMI down, Frame Relay 6-6
Enquiry timer 6-4
Fallback speed, on HDLCOFR port 6-2
Filter, for PVC 7-17
Frame delay 6-3
Frame over IP, destination 5-6, 5-11, 5-12, 5-13
Frame over IP, source 5-10
Frame size, for PVC 7-21
IP address, for PVC 7-9
IP connection, for PVC 7-21
IP multicast active, for PVC 7-15
IP multicast protocol, for PVC 7-15
IP RIP authentication type, for PVC 7-13
IP RIP password, for PVC 7-13
IP RIP TX/RX, for PVC 7-13
IP RIP, for PVC 7-12
IPX connection, for PVC 7-21
IPX network number, for PVC 7-16
IPX RIP, for PVC 7-16
IPX SAP, for PVC 7-16
LLC connection, for PVC 7-22
Management interface, Frame Relay 6-3
Maximum number of voice channels, for PVC 718
Maximum Voice Channels If High Priority Data,

for PVC 7-19
Mode, for PVC 7-2
NAT Enable, for PVC 7-11
NAT Rule, for PVC 7-11
NAT Side, for PVC 7-11
Network DLCI, for PVC 7-25
Network port, for PVC 7-24
Number of retransmission retries, for PVC 7-9
OSPF, for PVC 7-14
Port, used by PVC 7-4
Protocol, Frame Relay 3-3
PVC number, Frame Relay 7-2
Reference port for conditional LMI, Frame
Relay 6-5
Remote PVC number, for Frame Relay 7-23
Remote unit name, for PVC 7-6
Report cycle, Frame Relay 6-8
Subnet mask, for PVC 7-10
SVC address type, Frame Relay 6-8
SVC call proceeding timeout T310, Frame
Relay 6-11
SVC disconnect timeout T305, Frame Relay 611
SVC Iframe retransmissions N200, Frame
Relay 6-10
SVC inactive timeout T203, Frame Relay 6-10
SVC max Tx Ack timeout T200, Frame Relay 69
SVC network address, Frame Relay 6-9
SVC release timeout T308, Frame Relay 6-11
SVC setup timeout T303, Frame Relay 6-10
SVC status enquiry timeout T322, Frame Relay
6-12
Timeout, for PVC 7-9
Type, of PVC 7-7
User DLCI, for PVC 7-24
User port
for PVC 7-24
Password
for IP RIP 7-13
Port
for FRoIP 5-5
used by PVC 7-4
PORT n display 4-30
PORT n ERROR display 4-19
PORT#
Port, for FRoIP forced route 5-13
Ports
display of bad frames 4-19
displaying status 4-31, 4-35
interface, display of 4-34
logical state 4-31, 4-35
number, display of 4-33
physical state 4-30

speed, display of 4-30, 4-34
PowerCell PVC 3-10
Protocol
Frame Relay 3-3
of WAN/user port 3-3
PVC command 3-8
PVC number
Frame Relay 7-2
PVC parameters
for FRoIP 5-4
PVC status display 4-35
PVCR
configuration of PVC 3-10
PVCs 1-3
bridge connection 7-17
broadcast group 7-18
burst information rate 7-6
call delay 7-7
committed information rate 7-5
dial timeout 7-8
display of channel sequence errors 4-24
enabling IP RIP 7-12
hang delay 7-8
information status 4-36
IP address 7-9
IP connection 7-21
IP RIP authentication type 7-13
IP RIP directionality 7-13
IP RIP password 7-13
IPX connection 7-21
IPX network number 7-16
IPX RIP 7-16
IPX SAP 7-16
LLC connection 7-22
logical state 4-36
maximum frame size 7-21
modes, selecting 2-2
network port 7-24
on remote unit 7-23
parameters, configuration of 3-8
User DLCI address 7-24
user port 7-24
Q
Q 922 Tx bytes 4-13
Q922 Data link established 4-12
Q922 Establish indications 4-12
Q922 Missing control blocks 4-28
Q922 Release indications 4-12
Q922 Rx Ack expiry 4-28
Q922 Rx bytes 4-13
Q922 Rx frames 4-13
Memotec Inc.
Q922 state
Q922 Tx Ack expiry 4-28
Q922 Tx frames 4-13
Q922 Tx Iframe Q discards 4-13
Q922 Tx retransmissions 4-12
Q933 Invalid Rx sizes 4-28
Q933 Protocol timeouts 4-17
Q933 Rx call proceeding messages 4-15
Q933 Rx connect messages 4-15
Q933 Rx disconnect messages 4-16
Q933 Rx release complete messages 4-16
Q933 Rx release messages 4-15
Q933 Rx setup messages 4-14
Q933 Rx status enquiry messages 4-17
Q933 Rx status messages 4-16
Q933 Setup success rate 4-14
Q933 Tx call proceeding messages 4-14
Q933 Tx connect messages 4-15
Q933 Tx disconnect messages 4-16
Q933 Tx release complete messages 4-15
Q933 Tx release messages 4-15
Q933 Tx setup messages 4-14
Q933 Tx status enquiry messages 4-16
Q933 Tx status messages 4-16
R
Receiver rate (M)
Receiver rate (P)
Receiver rate (P), displaying on SVC 4-10
Redundant link
for PVC 7-20
Reference port for conditional LMI
Frame Relay 6-5
Remote PVC number
for Frame Relay 7-23
Remote unit name
for PVC 7-6
Report cycle
Frame Relay 6-8
Reset Counters command 4-17
Routing
IP 7-12, 7-13
IPX 7-16
IPX RIP 7-16
IPX SAP 7-16
RS-232 interface
modem signal status 4-31, 4-34
WAN Frame Relay
S
Setup PVC menu 3-8
Sorter overruns
displaying for port/PVC group 4-25
Sorter timeouts
Speed
display of 4-34
SPEED (BPS)
Speed used
State
State & Delay
STATE DELAY
Statistics
displaying errors 4-18
DLCI, displaying for PVC 4-37
Information signals, displaying for PVC 4-36
Information signals, displaying for SVC 4-40
INTERFACE, displaying for Frame Relay 4-34
Interface, displaying for Frame Relay 4-30
logical state of port 4-31, 4-35
logical state of PVC 4-36
Mode, displaying for PVC 4-36
Mode, displaying for SVC 4-39
MODEM SIGNALS, displaying for Frame Relay
4-34
Modem signals, displaying for Frame Relay 431
Number of bad frames, displaying for Frame
Relay 4-19
Number of BECH transmitted, displaying on
SVC 4-11
Number of BECN received, displaying on PVC 46
Number of BECN received, displaying on SVC
4-10
Number of BECN transmitted, displaying on
PVC 4-6
Number of channel abort errors, displaying on
PVC 4-23
Number of channel overflow errors, displaying
on PVC 4-23
Number of channel sequence errors, displaying

on PVC 4-24
Number of CLLM frames received, displaying
on PVC 4-7
Number of CLLM frames received, displaying
on SVC 4-11
Number of CLLM frames transmitted,
Number of CLLM frames transmitted,
Number of compressor errors, displaying on
PVC 4-23
Number of errors, displaying for SVC 4-27
Number of errors, displaying on PVC 4-21
Number of FECN received, displaying on PVC 47
Number of FECN received, displaying on SVC 411
Number of FECN transmitted, displaying on
PVC 4-7
Number of FECN transmitted, displaying on
SVC 4-11
Number of frames discarded (CRC), displaying
for SVC 4-27
Number of frames discarded (overrun),
Number of frames received, displaying on PVC
4-6
Number of frames transmitted, displaying on
PVC 4-6
Number of frames transmitted, displaying on
SVC 4-10
Number of invalid frames discarded, displaying
on PVC 4-22
Number of invalid octets discarded, displaying
on PVC 4-22
Number of octets discarded (bad), displaying
for Frame Relay 4-20
Number of octets discarded (CRC), displaying
for SVC 4-27
Number of octets discarded (overrun),
Number of octets received, displaying on PVC
4-6
Number of octets received, displaying on SVC
4-10
Number of octets transmitted, displaying on

PVC 4-6
Number of octets transmitted, displaying on
SVC 4-10
Number of out of sequence errors, displaying
for port/PVC group 4-25, 4-26
Number of restarts, displaying for Frame Relay
4-20
Number of restarts, displaying for SVC 4-27
Number of restarts, displaying on PVC 4-22
Number of retries, displaying for Frame Relay
4-20
Number of sorter overruns, displaying for port/
PVC group 4-25
Number of sorter timeouts, displaying for port/
PVC group 4-26
Number of underruns, displaying for Frame
Relay 4-20
PORT#, displaying for Frame Relay 4-33
PROTOCOL, displaying for Frame Relay 4-33
Protocol, displaying for Frame Relay 4-30
Protocol, displaying for SVC 4-39
Q922 Data link established 4-12
Q922 Establish indications 4-12
Q922 Invalid Rx sizes 4-28
Q922 Missing control blocks 4-28
Q922 Release indications 4-12
Q922 Rx Ack expiry 4-28
Q922 Rx bytes 4-13
Q922 Rx frames 4-13
Q922 state, displaying for Frame Relay 4-31
Q922 Tx Ack expiry 4-28
Q922 Tx bytes 4-13
Q922 Tx frames 4-13
Q922 Tx Iframe Q discards 4-13
Q922 Tx retransmissions 4-12
Q933 Protocol timeouts 4-17
Q933 Rx call proceeding messages 4-15
Q933 Rx connect messages 4-15
Q933 Rx disconnect messages 4-16
Q933 Rx release complete messages 4-16
Q933 Rx release messages 4-15
Q933 Rx setup messages 4-14
Q933 Rx status enquiry messages 4-17
Q933 Rx status messages 4-16
Q933 Setup success rate 4-14
Q933 Tx call proceeding messages 4-14
Q933 Tx connect messages 4-15
Q933 Tx disconnect messages 4-16
Q933 Tx release complete messages 4-15
Q933 Tx release messages 4-15
Q933 Tx setup messages 4-14
Q933 Tx status enquiry messages 4-16
Q933 Tx status messages 4-16
Receiver rate (M), displaying on PVC 4-5
Memotec Inc.
Receiver rate (M), displaying on SVC 4-9

Receiver rate (P), displaying on PVC 4-5
Receiver rate (P), displaying on SVC 4-10
Remote unit name, displaying for PVC 4-37
resetting counters 4-17
SPEED (BPS), displaying for Frame Relay 4-34
Speed used, displaying for Frame Relay 4-30
Speed used, displaying for PVC 4-37
Speed used, displaying for SVC 4-40
State & Delay, displaying for PVC 4-37
STATE DELAY, displaying for Frame Relay 4-35
State, displaying for Frame Relay 4-31
State, displaying for SVC 4-40
Transmitter rate (M), displaying on PVC 4-5
Transmitter rate (M), displaying on SVC 4-9
Transmitter rate (P), displaying on PVC 4-5
Transmitter rate (P), displaying on SVC 4-9
Statistics Number of frames received, displaying
on SVC 4-10
STDRCI display 4-31, 4-34
Subnet mask
for PVC 7-10
SVC address type
Frame Relay 6-8
Frame Relay 6-11
SVC disconnect timeout T305
Frame Relay 6-11
Frame Relay 6-10
SVC inactive timeout T203
Frame Relay 6-10
SVC max Tx Ack timeout T200
Frame Relay 6-9
SVC network address
Frame Relay 6-9
SVC release timeout T308
Frame Relay 6-11
Frame Relay 6-10
SVC status enquiry timeout T322
Frame Relay 6-12
SVCs
configuring 3-6, 6-4, 6-9, 6-10, 6-11, 6-12
Type
of PVC 7-7
U
UQFSBA display 4-19
Use a forced route 5-13
Use this port as default gateway
for PVC 7-20
User DLCI
for PVC 7-24
User port
for PVC 7-24
V
V.35 interface
Version
for IP RIP 7-12
Voice fallback 1-3
Voice Traffic Control 7-18
W
Wait for ACK timeout 7-9
WAN/User ports
protocol 3-3
X
X.21 interface
X.25 Protocol
defining Multiplex PVC for 3-12
defining Transparent PVC for 7-24
T
Timeout
for PVC 7-9
Timer in ms for FR over IP 5-4
WAN Frame Relay
REACH FURTHER. OFFER MORE.

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

620-0216-006-WAN - Frame Relay

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

620-0216-006-WAN - Frame Relay

Uploaded by

Copyright:

Available Formats

WAN/Frame Relay

NetPerformer System Reference

COPYRIGHTS AND DISCLAIMERS

7755 Henri Bourassa Blvd. West

Packet Mode Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Permanent Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Switched Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Frame Relay Encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Chapter 2: Planning the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Selecting the Port Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Selecting the PVC Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Other PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Example Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Setting the SVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

NNI System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Chapter 3: Frame Relay Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Frame Relay Port Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . 3-2

FR-NET Port Configuration Parameters . . . . . . . . . . . . . . . . . . 3-4

FR-NET Channel Configuration Parameters . . . . . . . . . . . . . . . 3-4

FR-USER Port Configuration Parameters . . . . . . . . . . . . . . . . . 3-5

FR-USER Channel Configuration Parameters . . . . . . . . . . . . . . 3-6

PVC Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

PVCR PVC Configuration Parameters . . . . . . . . . . . . . . . . . . . 3-10

RFC1490 PVC Configuration Parameters . . . . . . . . . . . . . . . . 3-10

Multiplex PVC Configuration Parameters. . . . . . . . . . . . . . . . . 3-11

Broadcast PVC Configuration Parameters. . . . . . . . . . . . . . . . 3-12

Transparent PVC Configuration Parameters . . . . . . . . . . . . . . 3-13

Chapter 4: Frame Relay Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

About NetPerformer Frame Relay link status . . . . . . . . . . . . . . . . . . . . . . 4-2

Displaying Frame Relay Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Port Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

PVC Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Transmitter rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Receiver rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Transmitter rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Receiver rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Number of frames transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Number of frames received . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Number of octets transmitted. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Number of octets received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Number of BECN received . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Number of BECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Number of FECN received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Number of FECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Number of CLLM frames received. . . . . . . . . . . . . . . . . . . . . . . 4-7

Number of CLLM frames transmitted. . . . . . . . . . . . . . . . . . . . . 4-7

Transparent PVC Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

SVC Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Transmitter rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Receiver rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Transmitter rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Receiver rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Number of frames transmitted . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Number of frames received . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Number of octets transmitted. . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Number of octets received. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Number of BECN received . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Number of BECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Number of FECN received. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Number of FECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Number of CLLM frames received. . . . . . . . . . . . . . . . . . . . . . 4-11

Number of CLLM frames transmitted. . . . . . . . . . . . . . . . . . . . 4-11

Q.922 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11