WAN Frame Relay System Reference - Comtech EF Data€¦ · · 2017-02-24WAN/Frame Relay NetPerformer® System Reference. COPYRIGHTS AND DISCLAIMERS Published Date: May 2014 Document

WAN/Frame RelayNetPerformer® System Reference

COPYRIGHTS AND DISCLAIMERS

Published Date: May 2014

Document #: 1599

This publication contains information proprietary and confidential to Memotec Inc. Any reproduction, disclosure or unauthorized use of this publication is expressly prohibited except as Memotec Inc. may otherwise authorize in writing.

Memotec Inc. reserves the right to make changes without notice in product or component design as warranted by evolution in user needs or progress in engineering or manufacturing technology. Changes which affect the operation of the unit will be documented in the next revision of the manual.

We have made every effort to ensure the accuracy of the information presented in our documentation. However, Memotec assumes no responsibility for the accuracy of the information published. Product documentation is subject to change without notice. Changes, if any, will be incorporated in new editions of these documents. Memotec may make improvements or changes in the products or programs described within the documents at any time without notice. Mention of products or services not manufactured or sold by Memotec is for informational purposes only and constitutes neither an endorsement nor a recommendation for such products or services.

Memotec Inc. is a wholly owned subsidiary of Comtech EF Data Corp., and its parent company Comtech Telecommunications Corp (NASDAQ: CMTL).

AccessView, CXTool, CX-U Series, CX-UA Series, AbisXpress, NetPerformer, AccessGate, ACTView, SDM-8400, and the SDM-9000 series of products are either registered trademarks or trademarks of Memotec Inc.in Canada, the United States of America, and in other countries.

Windows is a registered trademark of Microsoft Corporation in the United States and other countries.

Any other trademarks are the property of their respective companies.

Copyright © 2014 Memotec Inc.

Memotec Inc.7755 Henri Bourassa Blvd. WestMontreal, QuebecCanada H4S 1P7Tel.: (514) 738-4781FAX: (514) 738-4436www.memotec.com

http://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 Frame Relay Port Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . 3-2

3.1.1 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.1.2 FR-NET Port Configuration Parameters. . . . . . . . . . . . . . . . . . . 3-43.1.3 FR-NET Channel Configuration Parameters . . . . . . . . . . . . . . . 3-43.1.4 FR-USER Port Configuration Parameters . . . . . . . . . . . . . . . . . 3-53.1.5 FR-USER Channel Configuration Parameters . . . . . . . . . . . . . . 3-6

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

3.2.1 PVCR PVC Configuration Parameters . . . . . . . . . . . . . . . . . . . 3-103.2.2 RFC1490 PVC Configuration Parameters . . . . . . . . . . . . . . . . 3-103.2.3 Multiplex PVC Configuration Parameters. . . . . . . . . . . . . . . . . 3-113.2.4 Broadcast PVC Configuration Parameters. . . . . . . . . . . . . . . . 3-123.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-34.2.2 PVC Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44.2.3 Transmitter rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Memotec Inc.

4.2.4 Receiver rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.2.5 Transmitter rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.2.6 Receiver rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.2.7 Number of frames transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.2.8 Number of frames received . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.2.9 Number of octets transmitted. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.2.10 Number of octets received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.2.11 Number of BECN received . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.2.12 Number of BECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.2.13 Number of FECN received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74.2.14 Number of FECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74.2.15 Number of CLLM frames received. . . . . . . . . . . . . . . . . . . . . . . 4-74.2.16 Number of CLLM frames transmitted. . . . . . . . . . . . . . . . . . . . . 4-74.2.17 Transparent PVC Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84.2.18 SVC Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84.2.19 Transmitter rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94.2.20 Receiver rate (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94.2.21 Transmitter rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94.2.22 Receiver rate (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.2.23 Number of frames transmitted . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.2.24 Number of frames received . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.2.25 Number of octets transmitted. . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.2.26 Number of octets received. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.2.27 Number of BECN received . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.2.28 Number of BECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.2.29 Number of FECN received. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.2.30 Number of FECN transmitted . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.2.31 Number of CLLM frames received. . . . . . . . . . . . . . . . . . . . . . 4-114.2.32 Number of CLLM frames transmitted. . . . . . . . . . . . . . . . . . . . 4-114.2.33 Q.922 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.2.34 Q922 Tx retransmissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.2.35 Q922 Release indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.2.36 Q922 Establish indications . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.2.37 Q922 Data link established . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124.2.38 Q922 Tx Iframe Q discards . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.2.39 Q922 Rx frames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.2.40 Q922 Tx frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.2.41 Q922 Rx bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.2.42 Q922 Tx bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.2.43 Q.933 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134.2.44 Q933 Setup success rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144.2.45 Q933 Tx setup messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Memotec Inc.

4.2.46 Q933 Rx setup messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144.2.47 Q933 Tx call proceeding messages. . . . . . . . . . . . . . . . . . . . . 4-144.2.48 Q933 Rx call proceeding messages . . . . . . . . . . . . . . . . . . . . 4-154.2.49 Q933 Tx connect messages . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154.2.50 Q933 Rx connect messages . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154.2.51 Q933 Tx release messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154.2.52 Q933 Rx release messages. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154.2.53 Q933 Tx release complete messages . . . . . . . . . . . . . . . . . . . 4-154.2.54 Q933 Rx release complete messages . . . . . . . . . . . . . . . . . . . 4-164.2.55 Q933 Tx disconnect messages . . . . . . . . . . . . . . . . . . . . . . . . 4-164.2.56 Q933 Rx disconnect messages . . . . . . . . . . . . . . . . . . . . . . . . 4-164.2.57 Q933 Tx status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164.2.58 Q933 Rx status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164.2.59 Q933 Tx status enquiry messages. . . . . . . . . . . . . . . . . . . . . . 4-164.2.60 Q933 Rx status enquiry messages . . . . . . . . . . . . . . . . . . . . . 4-174.2.61 Q933 Protocol timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-174.2.62 Resetting the Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

4. 3 Displaying Frame Relay Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

4.3.1 Port Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184.3.2 Number of bad frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194.3.3 Number of underruns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.3.4 Number of retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.3.5 Number of restarts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.3.6 Number of frames discarded (overrun) . . . . . . . . . . . . . . . . . . 4-204.3.7 Number of octets discarded (bad) . . . . . . . . . . . . . . . . . . . . . . 4-204.3.8 Number of octets discarded (overrun) . . . . . . . . . . . . . . . . . . . 4-214.3.9 PVC Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214.3.10 Number of errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214.3.11 Number of restarts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-224.3.12 Number of invalid frames discarded. . . . . . . . . . . . . . . . . . . . . 4-224.3.13 Number of frames discarded (overrun) . . . . . . . . . . . . . . . . . . 4-224.3.14 Number of invalid octets discarded . . . . . . . . . . . . . . . . . . . . . 4-224.3.15 Number of octets discarded (overrun) . . . . . . . . . . . . . . . . . . . 4-234.3.16 Number of compressor errors . . . . . . . . . . . . . . . . . . . . . . . . . 4-234.3.17 Number of channel overflow errors . . . . . . . . . . . . . . . . . . . . . 4-234.3.18 Number of channel abort errors . . . . . . . . . . . . . . . . . . . . . . . . 4-234.3.19 Number of channel sequence errors . . . . . . . . . . . . . . . . . . . . 4-244.3.20 Transparent PVC Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-244.3.21 Group Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-244.3.22 Sorter overruns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254.3.23 Sorter window overflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

Memotec Inc.

4.3.24 Sorter timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.3.25 Sorter rejected cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.3.26 SVC Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-264.3.27 Number of errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.3.28 Number of restarts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-274.3.29 Number of frames discarded (CRC) . . . . . . . . . . . . . . . . . . . . 4-274.3.30 Number of frames discarded (overrun) . . . . . . . . . . . . . . . . . . 4-274.3.31 Number of octets discarded (CRC) . . . . . . . . . . . . . . . . . . . . . 4-274.3.32 Number of octets discarded (overrun) . . . . . . . . . . . . . . . . . . . 4-274.3.33 Q.922 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284.3.34 Q922 Invalid Rx sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284.3.35 Q922 Missing control blocks . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284.3.36 Q922 Rx Ack expiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-284.3.37 Q922 Tx Ack expiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28

4. 4 Displaying Frame Relay States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

4.4.1 Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-294.4.2 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-304.4.3 Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-304.4.4 Speed used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-304.4.5 Modem signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-314.4.6 State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-314.4.7 Q922 state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-314.4.8 Continuous Display of Port States . . . . . . . . . . . . . . . . . . . . . . 4-334.4.9 PORT#. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-334.4.10 PROTOCOL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-334.4.11 INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-344.4.12 SPEED (BPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-344.4.13 MODEM SIGNALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-344.4.14 STATE DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-354.4.15 PVC Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-354.4.16 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-364.4.17 Information signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-364.4.18 DLCI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-374.4.19 Remote unit name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-374.4.20 State & Delay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-374.4.21 Transparent PVC States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-384.4.22 Continuous Display of PVC States . . . . . . . . . . . . . . . . . . . . . 4-384.4.23 SVC Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-394.4.24 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-394.4.25 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-394.4.26 Information signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40

Memotec Inc.

4.4.27 Speed used (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-404.4.28 DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-404.4.29 State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40

4. 5 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.3.1 Global Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45.3.2 PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

5. 4 Example Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

5.4.1 Local Unit Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75.4.2 Remote Unit Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-95.4.3 Frame over IP, source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105.4.4 Frame over IP, destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-115.4.5 Frame over IP, port number . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-115.4.6 Frame over IP, precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125.4.7 Use a forced route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-135.4.8 Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-135.4.9 Next hop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

5. 5 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Chapter 6: SE/PORT Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

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

6.1.1 Fallback speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.1.2 Frame delay (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.1.3 Management interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.1.4 Congestion flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.1.5 Enquiry timer (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.1.6 CLLM function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56.1.7 Reference port for conditional LMI . . . . . . . . . . . . . . . . . . . . . . . 6-56.1.8 Drop signals on LMI down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

6. 2 FR-USER Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

6.2.1 Report cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.2.2 SVC address type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.2.3 SVC network address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-96.2.4 SVC max Tx Ack timeout T200 . . . . . . . . . . . . . . . . . . . . . . . . . 6-96.2.5 SVC inactive timeout T203. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Memotec Inc.

6.2.6 SVC setup timeout T303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106.2.7 SVC disconnect timeout T305 . . . . . . . . . . . . . . . . . . . . . . . . . 6-116.2.8 SVC release timeout T308. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-116.2.9 SVC call proceeding timeout T310 . . . . . . . . . . . . . . . . . . . . . 6-116.2.10 SVC status enquiry timeout T322 . . . . . . . . . . . . . . . . . . . . . . 6-12

Chapter 7: SE/PVC Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

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

7.1.1 PVC number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27.1.2 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

7. 2 PVCR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

7.2.1 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.2 DLCI address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.2.3 Committed Information rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.2.4 Burst Information rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67.2.5 Remote unit name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67.2.6 Link quality parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77.2.7 Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77.2.8 Delay before call activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-87.2.9 Delay before call deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . 7-87.2.10 Call activation timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-97.2.11 Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-97.2.12 Timeout (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-97.2.13 Send keepalive packets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-107.2.14 Verify the link integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-107.2.15 Number of retransmission retries. . . . . . . . . . . . . . . . . . . . . . . 7-107.2.16 Payload compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-107.2.17 IP Header Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-117.2.18 IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-117.2.19 Subnet mask (number of bits) . . . . . . . . . . . . . . . . . . . . . . . . . 7-127.2.20 NAT enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-127.2.21 NAT rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-137.2.22 NAT side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-137.2.23 IP RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-137.2.24 IP RIP TX/RX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-147.2.25 IP RIP authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-157.2.26 IP RIP password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-157.2.27 OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-167.2.28 IP multicast active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-167.2.29 IP multicast protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-177.2.30 IPX RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

Memotec Inc.

7.2.31 IPX SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-187.2.32 IPX network number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-187.2.33 BRG connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-187.2.34 Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-197.2.35 Broadcast group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-197.2.36 Maximum number of voice channels . . . . . . . . . . . . . . . . . . . . 7-207.2.37 Maximum Voice Channels If High Priority Data . . . . . . . . . . . . 7-207.2.38 Use this port as default gateway . . . . . . . . . . . . . . . . . . . . . . . 7-217.2.39 Redundant link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22

7. 3 RFC1490 Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23

7.3.1 Frame size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-237.3.2 IP connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-237.3.3 IPX connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-237.3.4 LLC connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24

7. 4 MULTIPLEX Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25

7.4.1 Remote PVC number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-257.4.2 Class number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25

7. 5 TRANSP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26

7.5.1 User port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-267.5.2 Network port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-267.5.3 User DLCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-267.5.4 Network DLCI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

Memotec Inc.

Memotec Inc.

1
NetPerformer Frame Relay Support
Memotec Inc. 1-1

WAN Frame Relay

1.1 Packet Mode InterfaceFrame 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 CircuitsThe 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 CircuitsThe 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 EncapsulationThe 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 docu-ment 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 ProtocolAny 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 ModeIn 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 pro-tocol).

NOTE: PVCR mode is the preferred PVC operating mode when linking two NetPer-former units together across a Frame Relay network.

• RFC1490: The PVC is used over a Frame Relay network to access an RFC1490-compatible FRAD (Frame Relay Access Assembler/Disassembler). No fragmen-tation 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 ParametersThe 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 ApplicationFigure 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.

Figure 2-1: PVC Settings for Frame Relay Application

2-4 Memotec Inc.


2.5 Setting the SVCsFor 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,

• 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 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 ParametersThe 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 Net-Performer 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 inac-tive. 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 configu-rable, 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 ParametersThe PORT or SLOT submenu of the SETUP console command includes all parameters required to configure a Frame Relay port.

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.

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

Figure 3-1: SETUP/PORT and SETUP/SLOT/CHANNEL Paths on the CLI Tree for FR-NET and FR-USER Protocols

Console SNMP Text-based Config

SE/PORT (serial port)SE/SLOT (digital channel or dual serial port)

ifwan (category) [ifwan#] (heading)

3-2 Memotec Inc.


- Set the Protocol to:FR-NET if the port connects to a Frame Relay end-user deviceFR-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 deviceFR-USER if the port connects to a Frame Relay network

- Change the other channel parameters from their default values, if desired.

SE/PORT/#/FR-NET example: Setting the Protocol

SDM-9230>SESETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? PORTPort number (ETH1/ETH2/CSL/1,def:1) ?PORT 1> Protocol (def:PVCR) ? FR-NET...

3.1.1 Protocol

This parameter defines the operating protocol for the data port. Use the FR-NET or FR-USER 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 end-user device.

• Set the Protocol to FR-USER when the port connects to a Frame Relay network.


Protocol ifwanProtocol [ifwan#] Protocol

Memotec Inc. 3-3

WAN Frame Relay

3.1.2 FR-NET Port Configuration ParametersA 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/#/FR-NET example SDM-9230>SE

SETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? PORTPort number (ETH1/ETH2/CSL/1,def:ETH1) ? 1PORT 1> Protocol (def:OFF) ? FR-NETPORT 1> Interface...............................DCE-V35PORT 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 (0-10000,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, Maxi-mum 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 ParametersWhen you define a digital channel as FR-NET, the following parameters are listed on the console:

SE/SLOT/#/CHANNEL/FR-NET example

SDM-9230>SESETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? SLOTSLOT> Slot number (1/2/3,def:1) ?Port number (1/2,def:1) ?

3-4 Memotec Inc.


Item (LINK/CHANNEL,def:LINK) ? CHANNELSLOT> Channel Number (101-124/ALL,def:102) ? 103PORT 103> Protocol (def:OFF) ? FR-NETPORT 103> Timeslot (def:3) ?PORT 103> Number of consecutive timeslots (1-22,def:1) ?PORT 103> DS0 speed (bps) (def:64000) ? PORT 103> Management interface (def:LMI) ? PORT 103> Congestion flow control (def:ON) ? PORT 103> Enquiry timer (s) (1-30,def:10) ?PORT 103> CLLM function (def:OFF) ? PORT 103> Cell Packetization (def:YES) ? PORT 103> Maximum number of voice channels (0-10000,def:10000) ?PORT 103> Maximum Voice Channels If High Priority Data (0-10000,def:10000) ?PORT 103> Reference port for conditional LMI (def:0) ? PORT 103> Drop signals on LMI down (def:NO) ?

• Timeslot, Number of consecutive timeslots and DS0 speed (bps) are described in the appendix SE/SLOT/#/CHANNEL Configuration Parameters in the Dig-ital Data module of this document series.

• Management interface, Congestion flow control, Enquiry timer (s), CLLM func-tion, 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 ParametersAs 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/#/FR-USER example SDM-9230>SE

SETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? PORTPort number (ETH1/ETH2/CSL/1,def:ETH1) ? 1PORT 1> Protocol (def:OFF) ? FR-USERPORT 1> Interface...............................DCE-V35PORT 1> Clocking mode (def:INTERNAL) ?PORT 1> Port speed (bps) (1200-6144000,def:56000) ?PORT 1> Fallback speed (def:ENABLE) ?PORT 1> Management interface (def:LMI) ? PORT 1> Congestion flow control (def:ON) ? PORT 1> Enquiry timer (s) (1-30,def:10) ?PORT 1> Report cycle (1-256,def:6) ?PORT 1> CLLM function (def:OFF) ? PORT 1> Cell Packetization (def:YES) ?

Memotec Inc. 3-5

WAN Frame Relay

PORT 1> Maximum number of voice channels (0-10000,def:10000) ?PORT 1> Maximum Voice Channels If High Priority Data (0-10000,def:10000) ?PORT 1> Drop signals on LMI down (def:NO) ?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 mod-ule 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 “FR-USER Protocol” on page 6-8.

3.1.5 FR-USER Channel Configuration ParametersWhen you define a digital channel as FR-USER, the following parameters are listed on the console:

SE/SLOT/#/CHANNEL/FR-USER example

SDM-9230>SESETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? SLOTSLOT> Slot number (1/2/3,def:1) ?Item (LINK/CHANNEL,def:CHANNEL) ?SLOT> Channel Number (101-124/ALL,def:103) ? 104PORT 104> Protocol (def:OFF) ? FR-USERPORT 104> Timeslot (def:4) ?PORT 104> Number of consecutive timeslots (1-21,def:1) ?PORT 104> DS0 speed (bps) (def:64000) ?PORT 104> Management interface (def:LMI) ? PORT 104> Congestion flow control (def:ON) ? PORT 104> Enquiry timer (s) (1-30,def:10) ?PORT 104> Report cycle (1-256,def:6) ?PORT 104> CLLM function (def:OFF) ? PORT 104> Cell Packetization (def:YES) ? PORT 104> Maximum number of voice channels (0-10000,def:10000) ?PORT 104> Maximum Voice Channels If High Priority Data (0-

3-6 Memotec Inc.


10000,def:10000) ?PORT 104> Drop signals on LMI down (def:NO) ? 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 Dig-ital Data module of this document series.

• Management interface, Congestion flow control, Enquiry timer (s), CLLM func-tion 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 ParametersThe PVC submenu of the SETUP console command includes all parameters required to configure a PVC.

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.

• 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>SESETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? PVCPVC number (1-300,def:1) ?PVC 1> Mode (def:OFF) ? RFC1490

NOTE: Details on the PVC number and Mode parameters are provided in the appen-dix “SE/PVC Configuration Parameters” on page 7-1.

Figure 3-2: SETUP/PVC Path on the CLI Tree


SE, PVC pvc (category) [pvc#] (heading)

3-8 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 ParametersA 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 (FR-USER 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>SESETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? PVCPVC number (1-300,def:1) ?PVC 1> Mode (def:PVCR) ? PVC 1> Port (def:1) ?PVC 1> DLCI address (0-1022,def:0) ? 101PVC 1> Committed Information rate (4000-6144000,def:56000) ?PVC 1> Burst Information rate (4000-6144000,def:56000) ?PVC 1> Remote unit name (def:) ? CHICAGO-9230PVC 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 (0-10000,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 ParametersAn 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 (FR-USER 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>SESETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? PVCPVC number (1-300,def:1) ? 2PVC 2> Mode (def:OFF) ? RFC1490PVC 2> Port (def:1) ?PVC 2> DLCI address (0-1022,def:0) ? 103PVC 2> Committed Information rate (4000-6144000,def:56000) ?PVC 2> Burst Information rate (4000-6144000,def:56000) ?PVC 2> Remote unit name (def:) ? CHICAGO-9230PVC 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 MULTICASTPVC 2> IP RIP TX/RX (def:DUPLEX) ? TX ONLYPVC 2> IP RIP Authentication (def:NONE) ? SIMPLEPVC 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) ? YESPVC 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 connec-tion, 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 connec-tion. Refer to “RFC1490 Mode” on page 7-23 for details.

3.2.3 Multiplex PVC Configuration ParametersA 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>SESETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? PVCPVC number (1-300,def:3) ? 4PVC 4> Mode (def:OFF) ? MULTIPLEXPVC 4> Port (def:1) ?PVC 4> DLCI address (0-1022,def:0) ?PVC 4> Committed Information rate (4000-6144000,def:56000) ?PVC 4> Burst Information rate (4000-6144000,def:56000) ?PVC 4> Remote unit name (def:) ? CHICAGO-9230PVC 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-25.

3.2.4 Broadcast PVC Configuration ParametersA 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>SESETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? PVCPVC number (1-300,def:4) ? 5PVC 5> Mode (def:OFF) ? BROADCASTPVC 5> Port (def:1) ?PVC 5> DLCI address (0-1022,def:0) ?PVC 5> Committed Information rate (4000-6144000,def:56000) ?PVC 5> Burst Information rate (4000-6144000,def:56000) ?

• 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 ParametersA 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

SDM-9230>SESETUPItem (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,def:BRIDGE) ? PVCPVC number (1-300,def:5) ? 6PVC 6> Mode (def:OFF) ? TRANSPPVC 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) ?PVC 6> Committed Information rate (4000-6144000,def:56000) ?PVC 6> Burst Information rate (4000-6144000,def:56000) ?

Memotec Inc. 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 connec-tion, and are detailed in “TRANSP Mode” on page 7-26.

3-14 Memotec Inc.

4
Frame Relay Connection Status
Memotec Inc. 4-1

WAN Frame Relay

4.1 About NetPerformer Frame Relay link statusNetPerformer Frame Relay link status information includes:

• Current link counters, using the Display Counters (DC) command (see “Dis-playing 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).

Figure 4-1: Frame Relay Statistics Commands in the CLI Tree

4-2 Memotec Inc.


4.2 Displaying Frame Relay CountersThe 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 2-minute 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.

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 CountersIf you select the port counters for the Display Counters command, a display like the following will appear on the screen:

Console SNMP

DC/PORTDC/SLOTDC/PVCDC/GROUPDC/SVCQ922

statIfwanstatIfwanstatPvcstatGrpstatSvcstat (categories)

Memotec Inc. 4-3

WAN Frame Relay

DC/PORT example SDM-9380>DC

DISPLAY COUNTERSItem (BOOTP/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/SLOT/SVC/TIMEP,def:Q933) ? PORTCounters (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............4123392PORT 1> Number of frames received...............4204532PORT 1> Number of octets transmitted............422183940PORT 1> Number of octets received...............446426291PORT 2> Transmitter rate........................0 % (M)PORT 2> Receiver rate...........................0 % (M)PORT 2> Number of frames transmitted............0PORT 2> Number of frames received...............0PORT 2> Number of octets transmitted............0PORT 2> Number of octets received...............0PORT 3> Transmitter rate........................7 % (M)PORT 3> Receiver rate...........................7 % (M)PORT 3> Number of frames transmitted............788375PORT 3> Number of frames received...............788741PORT 3> Number of octets transmitted............50456000PORT 3> Number of octets received...............52056906

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 CountersIf you select the PVC counters for the Display Counters command, a display like the following will appear on the screen:

DC/PVC example SDM-9380>DC

DISPLAY COUNTERSItem (BOOTP/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/SLOT/SVC/TIMEP,def:TIMEP) ? PVCCounters (MEAN/PEAK,def:MEAN) ?PVC 1> Transmitter rate.........................0 % (M)PVC 1> Receiver rate............................0 % (M)PVC 1> Number of frames transmitted.............191994PVC 1> Number of frames received................410810PVC 1> Number of octets transmitted.............4220172PVC 1> Number of octets received................20543433

4-4 Memotec Inc.


PVC 1> Number of BECN received..................0PVC 1> Number of BECN transmitted...............0PVC 1> Number of FECN received..................0PVC 1> Number of FECN transmitted...............0PVC 1> Number of CLLM frames received...........0PVC 1> Number of CLLM frames transmitted........0

PVC 2> Transmitter rate.........................1 % (M)PVC 2> Receiver rate............................1 % (M)...

These counters can be used to determine the efficiency of Frame Relay PVCs:

4.2.3 Transmitter rate (M)

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)

The average bandwidth usage for data received from the attached equipment.

4.2.5 Transmitter rate (P)

The highest bandwidth usage for transmissions to the attached equipment.

4.2.6 Receiver rate (P)

The highest bandwidth usage for data received from the attached equipment.

Console SNMP

Transmitter rate (M) statPvcMeanTx

Console SNMP

Receiver rate (M) statPvcMeanRx

Console SNMP

Transmitter rate (P) statPvcPeakTx

Console SNMP

Receiver rate (P) statPvcPeakRx

Memotec Inc. 4-5

WAN Frame Relay

4.2.7 Number of frames transmitted

The number of frames that the PVC has transmitted to the attached equipment.

4.2.8 Number of frames received

The number of frames that the PVC has received from the attached equipment.

4.2.9 Number of octets transmitted

The number of octets that the PVC has transmitted to the attached equipment.

4.2.10 Number of octets received

The number of octets that the PVC has received from the attached equipment.

4.2.11 Number of BECN received

The number of Backward Congestion Bits (BECN) that the PVC has received from the attached equipment.

4.2.12 Number of BECN transmitted

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

Console SNMP

Number of frames transmit-ted

statPvcFramesTx

Console SNMP

Number of frames received statPvcFramesRx

Console SNMP

Number of octets transmit-ted

statPvcOctetsTx

Console SNMP

Number of octets received statPvcOctetsRx

Console SNMP

Number of BECN received statPvcBecnRx

Console SNMP

Number of BECN transmit-ted

statPvcBecnTx

4-6 Memotec Inc.


4.2.13 Number of FECN received

The number of Forward Congestion Bits (FECN) that the PVC has received from the attached equipment.

4.2.14 Number of FECN transmitted

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

4.2.15 Number of CLLM frames received

The number of CLLM frames that the PVC has received from the attached equipment.

4.2.16 Number of CLLM frames transmitted

The number of CLLM frames that the PVC has transmitted to the attached equipment.

Console SNMP

Number of FECN received statPvcFecnRx

Console SNMP

Number of FECN transmit-ted

statPvcFecnTx

Console SNMP

Number of CLLM frames received

statPvcCllmRx

Console SNMP

Number of CLLM frames transmitted

statPvcCllmTx

Memotec Inc. 4-7

WAN Frame Relay

4.2.17 Transparent PVC CountersFor a Transparent PVC, the Display Counters command displays both sides of the PVC.

DC/PVC example: for Transparent PVC

SDM-9380>DCDISPLAY COUNTERSItem (BOOTP/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/SLOT/SVC/TIMEP,def:BOOTP) ? PVCCounters (MEAN/PEAK,def:MEAN) ?Transparent PVC #1 --> PORT #1PVC 1> Transmitter rate.........................0 % (M)PVC 1> Receiver rate............................0 % (M)PVC 1> Number of frames transmitted.............146PVC 1> Number of frames received................155PVC 1> Number of octets transmitted.............2205PVC 1> Number of octets received................2736PVC 1> Number of BECN received..................0PVC 1> Number of BECN transmitted...............0PVC 1> Number of FECN received..................0PVC 1> Number of FECN transmitted...............0PVC 1> Number of CLLM frames received...........0PVC 1> Number of CLLM frames transmitted........0

Transparent PVC #1 --> PORT #2PVC 1> Transmitter rate.........................0 % (M)PVC 1> Receiver rate............................0 % (M)PVC 1> Number of frames transmitted.............155PVC 1> Number of frames received................146PVC 1> Number of octets transmitted.............3356PVC 1> Number of octets received................1621PVC 1> Number of BECN received..................0PVC 1> Number of BECN transmitted...............0PVC 1> Number of FECN received..................0PVC 1> Number of FECN transmitted...............0PVC 1> Number of CLLM frames received...........0PVC 1> Number of CLLM frames transmitted........0...

4.2.18 SVC CountersIf you select the SVC counters for the Display Counters command, a display like the following will appear on the screen:

DC/SVC/FR example

SDM-9360>DCDISPLAY COUNTERSItem (BOOTP/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/SLOT/SVC/TIMEP,def:BOOTP) ? SVCCounters (MEAN/PEAK,def:MEAN) ?SVC TYPE (ATM/FR/ALL,def:FR) ?

4-8 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 Transmitter rate (M)

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)

The average bandwidth usage for data received from the attached equipment.

4.2.21 Transmitter rate (P)

The highest bandwidth usage for transmissions to the attached equipment.

Console SNMP

Transmitter rate (M) statSvcMeanTx

Console SNMP

Receiver rate (M) statSvcMeanRx

Console SNMP

Transmitter rate (P) statSvcPeakTx

Memotec Inc. 4-9

WAN Frame Relay

4.2.22 Receiver rate (P)

The highest bandwidth usage for data received from the attached equipment.

4.2.23 Number of frames transmitted

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

4.2.24 Number of frames received

The number of frames that the SVC has received from the attached equipment.

4.2.25 Number of octets transmitted

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

4.2.26 Number of octets received

The number of octets that the SVC has received from the attached equipment.

4.2.27 Number of BECN received

The number of Backward Congestion Bits (BECN) that the SVC has received from the attached equipment.

Console SNMP

Receiver rate (P) statSvcPeakRx

Console SNMP

Number of frames transmit-ted

statSvcFramesTx

Console SNMP

Number of frames received statSvcFramesRx

Console SNMP

Number of octets transmit-ted

statSvcOctetsTx

Console SNMP

Number of octets received statSvcOctetsRx

Console SNMP

Number of BECN received statSvcBecnRx

4-10 Memotec Inc.


4.2.28 Number of BECN transmitted

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

4.2.29 Number of FECN received

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

4.2.30 Number of FECN transmitted

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

4.2.31 Number of CLLM frames received

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

4.2.32 Number of CLLM frames transmitted

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

4.2.33 Q.922 CountersIf you select the Q.922 counters for the Display Counters command, a display like the following will appear on the screen:

Console SNMP

Number of BECN transmit-ted

statSvcBecnTx

Console SNMP

Number of FECN received statSvcFecnRx

Console SNMP

Number of FECN transmit-ted

statSvcFecnTx

Console SNMP

Number of CLLM frames received

statSvcCllmRx

Console SNMP

Number of CLLM frames transmitted

statSvcCllmTx

Memotec Inc. 4-11

WAN Frame Relay

DC/Q922 example SDM-9380>DC

DISPLAY COUNTERSItem (BOOTP/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/SLOT/SVC/TIMEP,def:SVC) ? Q922Q922 Tx retransmissions.........................1Q922 Release indications........................0Q922 Establish indications......................1Q922 Data link established......................5Q922 Tx Iframe Q discards.......................6Q922 Rx frames..................................2799Q922 Tx frames..................................2812Q922 Rx bytes...................................12702Q922 Tx bytes...................................12426

The Q.922 counters include the following:

4.2.34 Q922 Tx retransmissions

The number of retransmissions invoked.

4.2.35 Q922 Release indications

The number of release indications that have occurred.

4.2.36 Q922 Establish indications

The number of establish indications that have occurred.

4.2.37 Q922 Data link established

The number of links that have been established since the last counters reset (see “Resetting the Counters” on page 4-17).

Console SNMP

Q922 Tx retransmissions statTxRetransmissions

Console SNMP

Q922 Release indications statReleaseIndications

Console SNMP

Q922 Establish indications statEstablishIndications

Console SNMP

Q922 Data link established statLinkEstablished

4-12 Memotec Inc.


4.2.38 Q922 Tx Iframe Q discards

The number of TX Iframe Q discards that have occurred.

4.2.39 Q922 Rx frames

The number of frames received by the NetPerformer Q.922 layer.

4.2.40 Q922 Tx frames

The number of frames transmitted by the NetPerformer Q.922 layer.

4.2.41 Q922 Rx bytes

The number of bytes received by the NetPerformer Q.922 layer.

4.2.42 Q922 Tx bytes

The number of bytes transmitted by the NetPerformer Q.922 layer.

4.2.43 Q.933 CountersIf you select the Q.933 counters for the Display Counters command, a display like the following will appear on the screen:

DC/Q933 example SDM-9380>DC

DISPLAY COUNTERSItem (BOOTP/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/SLOT/SVC/TIMEP,def:Q922) ? Q933Q933 Tx setup messages..........................7Q933 Rx setup messages..........................0

Console SNMP

Q922 Tx Iframe Q discards statTxIframeQdiscards

Console SNMP

Q922 Rx frames statRxframes

Console SNMP

Q922 Tx frames statTxframes

Console SNMP

Q922 Rx bytes statRxBytes

Console SNMP

Q922 Tx bytes statTxBytes

Memotec Inc. 4-13

WAN Frame Relay

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

Q933 Tx connect messages........................13Q933 Rx connect messages........................7Q933 Tx release messages........................12Q933 Rx release messages........................7Q933 Tx release complete messages...............7Q933 Rx release complete messages...............12Q933 Tx disconnect messages.....................7Q933 Rx disconnect messages.....................12Q933 Tx status messages.........................0Q933 Rx status messages.........................0Q933 Tx status enquiry messages.................0Q933 Rx status enquiry messages.................0Q933 Protocol timeouts..........................0

Q933 Setup success rate (%).....................37

The Q.933 counters include the following:

4.2.44 Q933 Setup success rate

The percentage of setup attempts that were successfully completed.

4.2.45 Q933 Tx setup messages

The number of setup messages transmitted by the NetPerformer Q.933 layer.

4.2.46 Q933 Rx setup messages

The number of setup messages received by the NetPerformer Q.933 layer.

4.2.47 Q933 Tx call proceeding messages

The number of call proceeding messages transmitted by the NetPerformer Q.933 layer.

Console SNMP

Q933 Setup success rate statSetupSuccessRate

Console SNMP

Q933 Tx setup messages statTxSetupMessages

Console SNMP

Q933 Rx setup messages statRxSetupMessages

Console SNMP

Q933 Tx call proceeding messages

statTxCallProceedingMessages

4-14 Memotec Inc.


4.2.48 Q933 Rx call proceeding messages

The number of call proceeding messages received by the NetPerformer Q.933 layer.

4.2.49 Q933 Tx connect messages

The number of connect messages transmitted by the NetPerformer Q.933 layer.

4.2.50 Q933 Rx connect messages

The number of connect messages received by the NetPerformer Q.933 layer.

4.2.51 Q933 Tx release messages

The number of release messages transmitted by the NetPerformer Q.933 layer.

4.2.52 Q933 Rx release messages

The number of release messages received by the NetPerformer Q.933 layer.

4.2.53 Q933 Tx release complete messages

The number of release complete messages transmitted by the NetPerformer Q.933 layer.

Console SNMP

Q933 Rx call proceeding messages

statRxCallProceedingMessages

Console SNMP

Q933 Tx connect mes-sages

statTxConnectMessages

Console SNMP

Q933 Rx connect mes-sages

statRxConnectMessages

Console SNMP

Q933 Tx release messages statTxReleaseMessages

Console SNMP

Q933 Rx release mes-sages

statRxReleaseMessages

Console SNMP

Q933 Tx release complete messages

statTxReleaseCompleteMessages

Memotec Inc. 4-15

WAN Frame Relay

4.2.54 Q933 Rx release complete messages

The number of release complete messages received by the NetPerformer Q.933 layer.

4.2.55 Q933 Tx disconnect messages

The number of disconnect messages transmitted by the NetPerformer Q.933 layer.

4.2.56 Q933 Rx disconnect messages

The number of disconnect messages received by the NetPerformer Q.933 layer.

4.2.57 Q933 Tx status messages

The number of status messages transmitted by the NetPerformer Q.933 layer.

4.2.58 Q933 Rx status messages

The number of status messages received by the NetPerformer Q.933 layer.

4.2.59 Q933 Tx status enquiry messages

The number of status enquiry messages transmitted by the NetPerformer Q.933 layer.

Console SNMP

Q933 Rx release complete messages

statRxReleaseCompleteMessages

Console SNMP

Q933 Tx disconnect mes-sages

statTxDisconnectMessages

Console SNMP

Q933 Rx disconnect mes-sages

statRxDisconnectMessages

Console SNMP

Q933 Tx status messages statTxStatusMessages

Console SNMP

Q933 Rx status messages statRxStatusMessages

Console SNMP

Q933 Tx status enquiry messages

statTxStatusEnquiryMessages

4-16 Memotec Inc.


4.2.60 Q933 Rx status enquiry messages

The number of status messages received by the NetPerformer Q.933 layer.

4.2.61 Q933 Protocol timeouts

The number of Q.933 protocol timeouts that have occurred since the last counters reset (see next section).

4.2.62 Resetting the Counters

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 exampleSDM-9230>RCRESET COUNTERSLast counter reset : THU 2003/10/16 14:18:02Reset counters, please confirm (NO/YES,def:NO) ? YESCounters 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.

Console SNMP

Q933 Rx status enquiry messages

statRxStatusEnquiryMessages

Console SNMP

Q933 Protocol timeouts statProtocolTimeouts

Console SNMP

RC statSystemResetCounters

Memotec Inc. 4-17

WAN Frame Relay

4.3 Displaying Frame Relay ErrorsThe 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 particu-lar 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)

• On a unit installed with the ATM licensed software option, enter FR at the PVC TYPE or SVC TYPE prompt



4.3.1 Port ErrorsIf you select the port errors with the Display Errors command, a display like the following will appear on the screen:

DE/PORT example SDM-9380>DE

DISPLAY ERRORSItem (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PU/PVC/Q922/SLOT/SVC/TIMEP,def:BOOTP) ? PORT

Console SNMP

DE/PORTDE/SLOTDE/PVCDE/GROUPDE/SVCQ922

statIfwanstatIfwanstatPvcstatGrpstatSvcstat (categories)

4-18 Memotec Inc.


PORT ETH> Number of excessive collisions........0...PORT 1> Number of bad frames....................0 ------PORT 1> Number of underruns.....................0PORT 1> Number of retries.......................0PORT 1> Number of restarts......................0PORT 1> Number of frames discarded (overrun)....0PORT 1> Number of octets discarded (bad)........0PORT 1> Number of octets discarded (overrun)....0PORT 2> Number of bad frames....................0 ------PORT 2> Number of underruns.....................0PORT 2> Number of retries.......................0PORT 2> Number of restarts......................0PORT 2> Number of frames discarded (overrun)....0PORT 2> Number of octets discarded (bad)........0PORT 2> Number of octets discarded (overrun)....0PORT 3> Number of bad frames....................0 ------PORT 3> Number of underruns.....................0PORT 3> Number of retries.......................0PORT 3> Number of restarts......................0PORT 3> Number of frames discarded (overrun)....0PORT 3> Number of octets discarded (bad)........0PORT 3> Number of octets discarded (overrun)....0Bad flags: U:Bad LENGTH Q:Overflow F:Flush S:Overrun B:Bad CRC A:Abort

These statistics can be used to diagnose operating problems on Frame Relay ports.

4.3.2 Number of bad frames

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.

Console SNMP

Number of bad frames statIfwanBadFrames,statIfwanBadFlags

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

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

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

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)

The number of frames that were discarded due to an overrun on the receive queue.

4.3.7 Number of octets discarded (bad)

The number of octets received that were discarded due to transmission errors.

Console SNMP

Number of underruns statIfwanUnderruns

Console SNMP

Number of retries statIfwanRetries

Console SNMP

Number of restarts statIfwanRestart

Console SNMP

Number of frames dis-carded (overrun)

statIfwanOvrFrames

Console SNMP

Number of octets discarded (bad)

statIfwanBadOctets

4-20 Memotec Inc.


4.3.8 Number of octets discarded (overrun)

The number of octets that were discarded due to an overrun on the receive queue.

4.3.9 PVC ErrorsIf you select the PVC errors with the Display Errors command, a display like the following will appear on the screen:

DE/PVC example SDM-9380>DE

DISPLAY ERRORSItem (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PU/PVC/Q922/SLOT/SVC/TIMEP,def:PORT) ? PVCPVC 1> Number of errors.........................32PVC 1> Number of restarts.......................0PVC 1> Number of invalid frames discarded.......1PVC 1> Number of frames discarded (overrun).....0PVC 1> Number of invalid octets discarded.......40PVC 1> Number of octets discarded (overrun).....0

PVC 2> Number of errors.........................0PVC 2> Number of restarts.......................0PVC 2> Number of invalid frames discarded.......0PVC 2> Number of frames discarded (overrun).....0PVC 2> Number of invalid octets discarded.......0PVC 2> Number of octets discarded (overrun).....0PVC 2> Number of compressor errors..............0PVC 2> Number of channel overflow errors........0PVC 2> Number of channel abort errors...........0PVC 2> Number of channel sequence errors........0

PVC 3> Number of errors.........................0PVC 3> Number of restarts.......................0PVC 3> Number of invalid frames discarded.......0PVC 3> Number of frames discarded (overrun).....0PVC 3> Number of invalid octets discarded.......0PVC 3> Number of octets discarded (overrun).....0...

These statistics can be used to diagnose operating problems on Frame Relay PVCs.

4.3.10 Number of errors

Console SNMP

Number of octets discarded (overrun)

statIfwanOvrOctets

Console SNMP

Number of errors statPvcError

Memotec Inc. 4-21

WAN Frame Relay

This counter is incremented every time the NetPerformer detects errors coming from the PVC.


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

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



4.3.14 Number of invalid octets discarded

The number of octets received that were discarded due to invalidity.

Console SNMP

Number of restarts statPvcRestart

Console SNMP

Number of invalid frames discarded

statPvcBadFrames

Console SNMP


statPvcOvrFrames

Console SNMP

Number of invalid octets discarded

statPvcBadOctets

4-22 Memotec Inc.




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: 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.

4.3.16 Number of compressor errors

This counter is incremented every time the connection’s compression dictionary detects an error.

4.3.17 Number of channel overflow errors

This counter is incremented every time the channel discards a cell because its buffer is full.

4.3.18 Number of channel abort errors

This counter is incremented every time the reception of a frame is terminated abruptly.

Console SNMP


statPvcOvrOctets

Console SNMP

Number of compressor errors

statPvcCompErrs

Console SNMP

Number of channel over-flow errors

statPvcChOverflows

Console SNMP

Number of channel abort errors

statPvcChAborts

Memotec Inc. 4-23

WAN Frame Relay

4.3.19 Number of channel sequence errors

This counter is incremented every time that frame reception fails, that is, there is at least one block missing.

4.3.20 Transparent PVC ErrorsFor 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>DEDISPLAY ERRORSItem (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PU/PVC/Q922/SLOT/SVC/TIMEP,def:BOOTP) ? PVCTransparent PVC #1 --> PORT #1PVC 1> Number of errors.........................0PVC 1> Number of restarts.......................0PVC 1> Number of invalid frames discarded.......0PVC 1> Number of frames discarded (overrun).....0PVC 1> Number of invalid octets discarded.......0PVC 1> Number of octets discarded (overrun).....0

Transparent PVC #1 --> PORT #2PVC 1> Number of errors.........................0PVC 1> Number of restarts.......................0PVC 1> Number of invalid frames discarded.......0PVC 1> Number of frames discarded (overrun).....0PVC 1> Number of invalid octets discarded.......0PVC 1> Number of octets discarded (overrun).....0...

4.3.21 Group ErrorsIf you select the GROUP errors with the Display Errors command, a display like the following will appear on the screen:

DE/GROUP example SDM-9390>DE

DISPLAY ERRORSItem (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PU/PVC/Q922/REDUNDANCY/SLOT/SVC/TIMEP,def:CHANNEL) ? GROUPGROUP to FR.80-1 [SDM-9585]

Sorter overruns..................................0

Console SNMP

Number of channel sequence errors

statPvcChSeqErrs

4-24 Memotec Inc.


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

Sorter overruns..................................0Sorter window overflows..........................0Sorter timeouts..................................0Sorter rejected cells............................0

GROUP to FR.80-3 [SDM-9585]


GROUP to FR.60-3 [SDM-9360]


GROUP to FR.80 [SDM-9585]


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

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 SNMP

Sorter overruns statGrpSorterOverruns

Console SNMP

Sorter window overflows statGrpSorterWindow-Overflows

Memotec Inc. 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

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

This error counter is incremented every time that cells are rejected by the sorter because they are invalid or unrecognizable.

4.3.26 SVC ErrorsIf you select the SVC errors with the Display Errors command, a display like the following will appear on the screen:

DE/SVC/FR example

SDM-9360>DEDISPLAY ERRORSItem (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PU/PVC/Q922/SLOT/SVC/TIMEP,def:BOOTP) ? SVCSVC 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.

Console SNMP

Sorter timeouts statGrpSorterTimeouts

Console SNMP

Sorter rejected cells statGrpSorterRejected-Cells

4-26 Memotec Inc.


4.3.27 Number of errors

This counter is incremented every time the NetPerformer detects errors coming from the SVC.


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)

The number of frames received that were discarded due to a bad checksum.



4.3.31 Number of octets discarded (CRC)

The number of octets received that were discarded due to a bad checksum.


Console SNMP

Number of errors statSvcError

Console SNMP

Number of restarts statSvcRestart

Console SNMP

Number of frames dis-carded (CRC)

statSvcBadFrames

Console SNMP


statSvcOvrFrames

Console SNMP

Number of octets discarded (CRC)

statSvcBadOctets

Console SNMP


statSvcOvrOctets

Memotec Inc. 4-27

WAN Frame Relay


4.3.33 Q.922 ErrorsIf 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>DEDISPLAY ERRORSItem (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PU/PVC/Q922/SLOT/SVC/TIMEP,def:SVC) ? Q922Q922 Invalid Rx sizes...........................0Q922 Missing control blocks.....................0Q922 Rx Ack expiry..............................0Q922 Tx Ack expiry..............................0

The Q.922 errors include the following:

4.3.34 Q922 Invalid Rx sizes

The number of frames received with an invalid length.

4.3.35 Q922 Missing control blocks

The number of control blocks that were not found.

4.3.36 Q922 Rx Ack expiry

The number of Receiver Ready (RR) indications that were received due to a Transmission Acknowledge (Tack) expiry.

4.3.37 Q922 Tx Ack expiry

The number of transmission frame acknowledgments that were delayed because the NetPerformer was waiting for a Transmission Acknowledge (Tack).

Console SNMP

Q922 Invalid Rx sizes statInvalidRxSizes

Console SNMP

Q922 Missing control blocks

statMissingControlBlocks

Console SNMP

Q922 Rx Ack expiry statRxAcknowledgeExpiry

Console SNMP

Q922 Tx Ack expiry statTxAcknowledgeExpiry

4-28 Memotec Inc.


4.4 Displaying Frame Relay StatesThe 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 4-33.

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 par-ticular 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)

• On a unit installed with the ATM licensed software option, enter FR at the PVC TYPE or SVC TYPE prompt.



4.4.1 Port StatusIf you select the port statistics with the Display States command, a display like the following will appear on the screen:

DS/PORT example SDM-9230>DS

DISPLAY STATESItem (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:GLOBAL) ? PORTPORT ETH> Protocol..............................ETHERNET...

Console SNMP

DS/PORTDS/SLOTDS/PVCDS/SVC

statIfwanstatIfwanstatPvcstatSvc (categories)

Memotec Inc. 4-29

WAN Frame Relay

PORT 1> Protocol................................FR-USERPORT 1> Interface...............................DTE-V35PORT 1> Speed used [bps]........................2048kPORT 1> Modem signals...........................STDRC-PORT 1> State...................................DATAPORT 1> Q922 state..............................UP

PORT 2> Protocol................................FR-NETPORT 2> Interface...............................DTE-V35PORT 2> Speed used [bps]........................512000PORT 2> Modem signals...........................-T-R--PORT 2> 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

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

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

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: The speed measured by the NetPerformer may be different from the config-ured speed if the Frame Relay connection is configured as DTE.

Console SNMP

Protocol statIfwanProtocol

Console SNMP

Interface statIfwanInterface

Console SNMP

Speed used statIfwanSpeed

4-30 Memotec Inc.


4.4.5 Modem signals

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

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 proto-col), 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 manage-ment protocol is working.

4.4.7 Q922 state

For FR-USER port only.The current status of Q.922 signaling on a FR-USER port that supports SVCs. The possible states are:

Console SNMP

Modem signals statIfwanModemSignal

Console SNMP

State statIfwanState

Console SNMP

Q922 state statIfwanQ922State

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: 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.

4-32 Memotec Inc.


4.4.8 Continuous Display of Port StatesThe 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

SDM-9380>DPORTDISPLAY PORT STATES------------------------------------------------------------------------------

--|PORT# PROTOCOL INTERFACE SPEED MODEM STATE DELAY || (BPS) SIGNALS |------------------------------------------------------------------------------

--| 1 FR-NET DCE-V35 56000 STDRC- DATA || 2 FR-NET DTE-V35 56000 STDRC- DATA || || || || || || || || || || || || || || || || || 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.

4.4.9 PORT#

Provides the current value for the port number, continuously refreshed and displayed in real time.

4.4.10 PROTOCOL

Provides the current value for the Frame Relay protocol used on the port, continuously

Console SNMP

PORT# statIfwanIndex

Console SNMP

PROTOCOL statIfwanProtocol

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

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)

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: The speed measured by the NetPerformer may be different from the config-ured speed if the Frame Relay connection is configured as DTE.

4.4.13 MODEM SIGNALS

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

Console SNMP

INTERFACE statIfwanInterface

Console SNMP

SPEED (BPS) statIfwanSpeed

Console SNMP

MODEM SIGNALS statIfwanModemSignal

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

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 proto-col), 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 manage-ment protocol is working.

4.4.15 PVC StatusIf you select the PVC statistics with the Display States command, a display like the following will appear on the screen:

DS/PVC/FR example SDM-9230>DS

DISPLAY STATESItem (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:PORT) ? PVCPVC TYPE (ATM/FR/ALL,def:FR) ?PVC 1> Mode.....................................PVCRPVC 1> Information signals......................USER -A---PVC 1> Speed used (bps).........................1024 kPVC 1> DLCI.....................................212PVC 1> Remote unit name...........................BOSTONPVC 1> State & Delay............................DATA 11ms

PVC 2> Mode.....................................PVCRPVC 2> Information signals......................USER -A---PVC 2> Speed used (bps).........................1024 kPVC 2> DLCI.....................................221PVC 2> Remote unit name.........................FR.60-3PVC 2> State & Delay............................DATA 14ms

PVC 7> Mode.....................................PVCRPVC 7> Information signals......................USER -A---PVC 7> Speed used (bps).........................640 kPVC 7> DLCI.....................................401PVC 7> Remote unit name.........................ATM1.80-1

Console SNMP

STATE DELAY statIfwanState

Memotec Inc. 4-35

WAN Frame Relay

PVC 7> State & Delay............................DATA 18ms

PVC 8> Mode.....................................PVCRPVC 8> Information signals......................USER -A---PVC 8> Speed used (bps).........................640 kPVC 8> DLCI.....................................402PVC 8> Remote unit name.........................ATM2.60-1PVC 8> 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

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

The information signal status. This statistic is displayed with a five-character field, where the individual characters have the following meaning:

• 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

Console SNMP

Mode statPvcMode

Console SNMP

Information signals statPvcInfoSignal

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 fol-lows the state indicated in the FULL STATUS MESSAGE regardless of the state of the modem signal.

Speed used (bps)

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

Lists the DLCI address of this PVC.

4.4.19 Remote unit name

The unit that is receiving traffic from this PVC.

4.4.20 State & Delay

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

Console SNMP

Speed used (bps) statPvcSpeed

Console SNMP

DLCI statPvcDlci

Console SNMP

Remote unit name statPvcDestName

Console SNMP

State & Delay statPvcState

Memotec Inc. 4-37

WAN Frame Relay

4.4.21 Transparent PVC StatesFor a Transparent PVC, the Display States command displays both sides of the PVC, as shown the following example:

SDM-9380>DSDISPLAY STATESItem (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:GLOBAL) ? PVCTransparent PVC #1 --> PORT #1PVC 1> Mode.....................................TRANSPPVC 1> Information signals......................NET -A---PVC 1> Speed used (bps).........................56000PVC 1> DLCI.....................................101PVC 1> State & Delay............................DATA

Transparent PVC #1 --> PORT #2PVC 1> Mode.....................................TRANSPPVC 1> Information signals......................NET -A---PVC 1> Speed used (bps).........................56000PVC 1> DLCI.....................................102PVC 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 StatesPVC 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 exampleSDM-9230>DPVCDISPLAY 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 StatusIf you select the SVC statistics with the Display States command, a display like the following will appear on the screen:

DS/SVC/FR example SDM-9360>DS

DISPLAY STATESItem (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:GLOBAL) ? SVCSVC TYPE (ATM/FR/ALL,def:FR) ?SVC 1> Mode.....................................PVCR SVC 1> Information signals......................USER -----SVC 1> Speed used (bps).........................56000SVC 1> DLCI.....................................0SVC 1> 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

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

The current operating mode of the SVC. The displayed mode is:

• PVCR: PVCR mode (using Frame Relay port).

Console SNMP

(not available) statSvcProtocol

Console SNMP

Mode statSvcMode

Memotec Inc. 4-39

WAN Frame Relay

4.4.26 Information signals

The information signal status. This statistic is displayed with a five-character field, where the individual characters have the following meaning:

• 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)

This is the speed, in bits per second, measured by the NetPerformer.

4.4.28 DLCI

Lists the DLCI address of the SVC.

4.4.29 State

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

Console SNMP

Information signals statSvcInfoSignal

Console SNMP

Speed used (bps) statSvcSpeed

Console SNMP

DLCI statSvcDlci

Console SNMP

State statSvcState

4-40 Memotec Inc.


4.5 Capturing PVCR Frame Length

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>CLCAPTURE FRAME LENGTHOperation (START/STOP/DELETE/DISPLAY,def:START) ?Number of frames (0-10000,def:1000) ?Type (PORT/PVC,def:PORT) ? PVCCapture PVC (1-300,def:*) ? 1Capture 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.

Console SNMP

CL (not available)

Memotec Inc. 4-41

WAN Frame Relay

CL/DISPLAY example SDM-9380>CL

CAPTURE FRAME LENGTHOperation (START/STOP/DELETE/DISPLAY,def:STOP) ? DISPLAYNumber of frames .......................... 511Smallest frame ............................ 8Largest frame ............................. 245Mean length ............................... 102Distribution: 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 over-writes 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 IPThe 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:

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.

Figure 5-1: FRoIP Network

5-2 Memotec Inc.

Frame Relay over IP

5.2 NetPerformer ImplementationFRoIP 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 param-eter

- Controlling the combined information rate of all PVCs by means of the Glo-bal 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 ConfigurationThere 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 ParametersThe 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.

5.3.2 PVC ParametersThe 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.

Parameter SNMP Variable Values Functions

Global CIR for FR over IP

npsysCirFrOverIp 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 for FR over IP

npsysTimerFr-OverIp

1 - 1000 (def. 50)

Defines the FRoIP check timer interval, which controls the time-out of frames on the IP port when FRoIP is activated.

Max number of voice chan-nels over IP

npsysMaxVoice-CallOverIp

0 - 10000 (def. 10000)

Defines the maximum number of voice channels permitted on the IP port for FRoIP. Default 10000 for no call blocking.

Max voice channels over IP if high pri-ority data

npsysLowMax-VoiceCallOverIp

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-4 Memotec Inc.

Frame Relay over IP

The PVC parameters used for FRoIP are shown in Table 5-2.


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 connec-tion. You must change this parameter from 0, the default value for DLCI auto-learning, 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

pvcIpDest- Address

0.0.0.0 - 255.255.255. 255(def. 0.0.0.0)

Provides the IP address of 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

NOTE: The Burst Information Rate (BIR) parameter is not requested for PVCs con-figured for FRoIP.

Frame over IP, port number

pvcIpPort 1-65535(def. 1024)

Provides the IP address of 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 5-11 for details.

Frame over IP, precedence

pvcIpPrecedence 0-7 (def. 0) Determines the relative prior-ity of the traffic on this PVC with respect to other traffic. See “Frame over IP, prece-dence” on page 5-12 for details.

Use a forced route

pvcForcedRoute-Active

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

5-6 Memotec Inc.

Frame Relay over IP

5.4 Example ApplicationIn the application shown in Figure 5-2, voice and data are integrated over the Internet using Ethernet LAN access and the PVCR protocol.

5.4.1 Local Unit ParametersThe following are essential parameter values for configuring the local unit at the BOSTON site:

BOSTON>DPDISPLAY PARAMETERS

GLOBAL> Unit name...............................BOSTONGLOBAL> Unit routing version....................1GLOBAL> Contact name............................Memotec Inc.GLOBAL> Unit location...........................Head OfficeGLOBAL> Loopback................................NOGLOBAL> Link timeout delay......................0GLOBAL> Transit delay (s).......................4GLOBAL> Daylight saving time....................YESGLOBAL> Default IP address......................000.000.000.000GLOBAL> Default IP mask (number of bits)........0 {000.000.000.000}GLOBAL> Default gateway.........................000.000.000.000GLOBAL> SNMP trap: IP address #1................000.000.000.000GLOBAL> SNMP trap: IP address #2................000.000.000.000GLOBAL> SNMP trap: IP address #3................000.000.000.000GLOBAL> SNMP trap: IP address #4................000.000.000.000GLOBAL> Frame relay status change trap..........DISABLEGLOBAL> Watch power supplies and fan............NONEGLOBAL> Local unit DLCI address.................0GLOBAL> Extension number (no. of digits)........2GLOBAL> Country code............................1GLOBAL> Jitter buffer (ms)......................165GLOBAL> Enable voice/fax log....................YESGLOBAL> Dial timer (s)..........................0GLOBAL> High priority voice class...............YESGLOBAL> Global CIR for FR over IP...............64000GLOBAL> Timer in ms for FR over IP..............50GLOBAL> Max number of voice channels over IP....10000GLOBAL> Max voice channels over IP if high priority data 1000

Figure 5-2: FRoIP Application Example

Memotec Inc. 5-7

WAN Frame Relay

GLOBAL> Delay generated by a comma (ms).........250GLOBAL> ISDN G4 Fax PCM switching enable........NOGLOBAL> Auto save configuration delay (s).......10GLOBAL> Enable VTR (Voice Traffic Routing)......NOGLOBAL> Enable Domain Dialing...................YESGLOBAL> Enable hunt forwarding..................YESGLOBAL> Enable user access logging..............NOGLOBAL> Exclusive access to console.............DISABLE

PORT ETH 1> Protocol............................ETH AUTOPORT ETH 1> LAN speed (mbps)....................AUTOPORT ETH 1> MAC address.........................000000000000PORT ETH 1> DHCP................................DISABLEPORT ETH 1> IP address 1........................182.160.043.025PORT ETH 1> Subnet mask 1 (number of bits)......8 {255.255.255.000}PORT ETH 1> IP address 2........................000.000.000.000PORT ETH 1> Subnet mask 2(number of bits).......0 {255.255.255.000}PORT ETH 1> Frame size..........................1500PORT ETH 1> IP RIP..............................ENABLEPORT ETH 1> IP RIP TX/RX........................DUPLEXPORT ETH 1> OSPF................................DISABLEPORT ETH 1> IGMP enable.........................NOPORT ETH 1> IP multicast active.................NOPORT ETH 1> IP multicast protocol...............NOPORT ETH 1> NAT enable..........................NOPORT ETH 1> VLAN enable.........................NOPORT ETH 1> IPX RIP.............................DISABLEPORT ETH 1> IPX SAP.............................DISABLEPORT ETH 1> IPX network number..................00000000PORT ETH 1> IPX encapsulation...................ETH 802.2PORT ETH 1> Physical connectivity detection.....DISABLE

PVC 1> Mode.....................................PVCRPVC 1> Port.....................................0PVC 1> DLCI.....................................100PVC 1> Committed Information rate...............32000PVC 1> Remote unit name.........................LOS_ANGELESPVC 1> Type.....................................DEDICATEDPVC 1> Timeout (ms).............................1000PVC 1> Number of retransmission retries.........100PVC 1> Compression..............................YESPVC 1> IP address...............................000.000.000.000PVC 1> Subnet mask (number of bits).............8 {255.000.000.000}PVC 1> NAT enable...............................NOPVC 1> BRG connection...........................NOPVC 1> Filter...................................ALLPVC 1> Broadcast group..........................NOPVC 1> Maximum number of voice channels.........10000PVC 1> Maximum Voice Channels If High Priority Data 10000PVC 1> Frame over IP, source....................182.160.043.025PVC 1> Frame over IP, destination...............183.008.127.201PVC 1> Frame over IP, port number...............1024PVC 1> Frame over IP, precedence................0PVC 1> Use a forced route.......................NOPVC 1> Use this port as default gateway.........NOPVC 1> Redundant link...........................NO

5-8 Memotec Inc.

Frame Relay over IP

5.4.2 Remote Unit ParametersThe following are essential parameter values for configuring the remote unit at the LOS ANGELES site:

LOS_ANGELES>DPDISPLAY PARAMETERS

GLOBAL> Unit name...............................LOS_ANGELESGLOBAL> Unit routing version....................1GLOBAL> Contact name............................Memotec Inc.GLOBAL> Unit location...........................Western BranchGLOBAL> Loopback................................NOGLOBAL> Link timeout delay......................0GLOBAL> Transit delay (s).......................4GLOBAL> Daylight saving time....................YESGLOBAL> Default IP address......................000.000.000.000GLOBAL> Default IP mask (number of bits)........0 {000.000.000.000}GLOBAL> Default gateway.........................000.000.000.000GLOBAL> SNMP trap: IP address #1................000.000.000.000GLOBAL> SNMP trap: IP address #2................000.000.000.000GLOBAL> SNMP trap: IP address #3................000.000.000.000GLOBAL> SNMP trap: IP address #4................000.000.000.000GLOBAL> Frame Relay status change trap..........DISABLEGLOBAL> Watch power supplies and fan............NONEGLOBAL> Local unit DLCI address.................0GLOBAL> Extension number (no. of digits)........2GLOBAL> Country code............................1GLOBAL> Jitter buffer (ms)......................165GLOBAL> Enable voice/fax log....................YESGLOBAL> Dial timer (s)..........................0GLOBAL> High priority voice class...............YESGLOBAL> Global CIR for FR over IP...............64000GLOBAL> Timer in ms for FR over IP..............50GLOBAL> Max number of voice channels over IP....10000GLOBAL> Max voice channels over IP if high priority data 1000GLOBAL> Delay generated by a comma (ms).........250GLOBAL> ISDN G4 Fax PCM switching enable........NOGLOBAL> Auto save configuration delay (s).......10GLOBAL> Enable VTR (Voice Traffic Routing)......NOGLOBAL> Enable Domain Dialing...................YESGLOBAL> Enable hunt forwarding..................YESGLOBAL> Enable user access logging..............NOGLOBAL> Exclusive access to console.............DISABLE

PORT ETH 1> Protocol............................ETH AUTOPORT ETH 1> LAN speed (mbps)....................AUTOPORT ETH 1> MAC address.........................000000000000PORT ETH 1> DHCP................................DISABLEPORT ETH 1> IP address 1........................183.008.127.201PORT ETH 1> Subnet mask 1 (number of bits)......0 {255.255.255.000}PORT ETH 1> IP address 2........................000.000.000.000PORT ETH 1> Subnet mask 2(number of bits).......0 {255.255.255.000} PORT PORT ETH 1> Frame size..........................1500PORT ETH 1> IP RIP..............................ENABLEPORT ETH 1> IP RIP TX/RX........................DUPLEXPORT ETH 1> OSPF................................DISABLE

Memotec Inc. 5-9

WAN Frame Relay

PORT ETH 1> IGMP enable.........................NOPORT ETH 1> IP multicast active.................NOPORT ETH 1> IP multicast protocol...............NOPORT ETH 1> NAT enable..........................NOPORT ETH 1> VLAN enable.........................NOPORT ETH 1> IPX RIP.............................DISABLEPORT ETH 1> IPX SAP.............................DISABLEPORT ETH 1> IPX network number..................00000000PORT ETH 1> IPX encapsulation...................ETH 802.2PORT ETH 1> Physical connectivity detection.....DISABLE

PVC 1> Mode.....................................PVCRPVC 1> Port.....................................0PVC 1> DLCI.....................................100PVC 1> Committed Information rate...............32000PVC 1> Remote unit name.........................BOSTONPVC 1> Type.....................................DEDICATEDPVC 1> Timeout (ms).............................1000PVC 1> Number of retransmission retries.........100PVC 1> Compression..............................YESPVC 1> IP address...............................000.000.000.000PVC 1> Subnet mask (number of bits).............8 {255.000.000.000}PVC 1> NAT enable...............................NOPVC 1> BRG connection...........................NOPVC 1> Filter...................................ALLPVC 1> Broadcast group..........................NOPVC 1> Maximum number of voice channels.........10000PVC 1> Maximum Voice Channels If High Priority Data 10000PVC 1> Frame over IP, source....................183.008.127.201PVC 1> Frame over IP, destination...............182.160.043.025PVC 1> Frame over IP, port number...............1024PVC 1> Frame over IP, precedence................0PVC 1> Use a forced route.......................NOPVC 1> Use this port as default gateway.........NOPVC 1> 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

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: This parameter appears only if the PVC Port parameter is set to 0 (indicating


Frame over IP, source pvcIpSrcAddress [pvc#] IpSrcAddress

5-10 Memotec Inc.

Frame Relay over IP

FRoIP support).

5.4.4 Frame over IP, destination

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: This parameter appears only if the PVC Port parameter is set to 0 (indicating FRoIP support).

5.4.5 Frame over IP, port number

IP address of the source UDP port that transmits the FRoIP frames. This parameter can be used to allow transmission across a firewall.


Values: 000.000.000.000 - 255.255.255.255Default: 000.000.000.000


Frame over IP, destina-tion

pvcIpDestAddress [pvc#] IpDestAddress

Values: 000.000.000.000 - 255.255.255.255Default: 000.000.000.000


Frame over IP, port num-ber

pvcIpPort [pvc#] IpPort

Values: 1-65535Default: 1024

Memotec Inc. 5-11

WAN Frame Relay

5.4.6 Frame over IP, precedence

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).


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.

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 net-work

• 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.


Frame over IP, prece-dence

pvcIpPrecedence [pvc#] IpPrecedence

Figure 5-3: IP Precedence Bits

Values: 0-7Default: 0

5-12 Memotec Inc.

Frame Relay over IP

5.4.7 Use a forced route

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.


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

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: This parameter appears only if the PVC Port parameter is set to 0 (indicating FRoIP support) and Use a forced route is set to YES.

5.4.9 Next hop

IP address of the next unit on the path to the final destination that will receive traffic from


Use a forced route pvcForcedRouteActive [pvc#] ForcedRouteAc-tive

Values: YES, NODefault: NO


Port pvcForcedRoutePort [pvc#] ForcedRoutePort

Values: NONE, automatically generated list of ports and PVCs

Default: NONE


Next hop pvcForcedRouteNextHop [pvc#] ForcedRouteN-extHop

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: This parameter appears only if the PVC Port parameter is set to 0 (indicating 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.255Default: 000.000.000.000

5-14 Memotec Inc.

Frame Relay over IP

5.5 StatisticsThe 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 ProtocolMany 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 module of this document series.

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

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 Conges-tion 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 con-trol 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


Fallback speed ifwanFallBackSpeed-bps,ifwanFallBackSpeed-Enable

[ifwan#] FallBackSpeed-bps, FallBackSpeedEnable

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 fall-back speeds possible. Some protocols cannot run at the maximum speeds. For these, you must select an appropriate lower value.

6.1.2 Frame delay (ms)

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.

6.1.3 Management interface

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-

For NetPerformer models covered in this manual:

Values: DISABLE, ENABLE

Default: ENABLEFor legacy NetPerformer models: Values: 0 - 2000000

Default: 2400


Frame delay (ms) ifwanFrameDelay [ifwan#] FrameDelay

Values: 0.0, 0.5, 1.0, 1.5, 2.0Default: 0.0


Management interface ifwanMgmtInterface [ifwan#] MgmtInterface

Memotec Inc. 6-3

WAN Frame Relay

USER Port Configuration Parameters” on page 3-5). The Management Interface of a FR-USER 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.

6.1.4 Congestion flow control

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 dis-abled. 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.

6.1.5 Enquiry timer (s)

Sets the Frame Relay Enquiry Timer, in seconds. For a Frame Relay user port (FR-USER

Values: LMI, ANNEX-D, Q.933, NONEDefault: LMI


Congestion flow control ifwanFlowControl [ifwan#] FlowControl

Values: OFF, ONDefault: ON


Enquiry timer (s) ifwanEnquiryTimer-s [ifwan#] EnquiryTimer-s

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.

6.1.6 CLLM function

Enables or disables Consolidated Link Layer Management (CLLM) on the Frame Relay port. To implement CLLM, set the port’s 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.

6.1.7 Reference port for conditional LMI

For FR-NET protocol only.Link Management Interface activity on the FR-NET port is conditioned by the presence or

Values: 1 - 30Default: 10


CLLM function ifwanCllm [ifwan#] Cllm

Values: OFF, ONDefault: OFF


Reference port for condi-tional LMI

ifwanCondLMIPort [ifwan#] CondLMIPort

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.

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.

6.1.8 Drop signals on LMI down

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.

Values: 0 - 2000Default: 0 (disabled)


Drop signals on LMI down

ifwanDropSignalsOnLMI-Down

[ifwan#] DropSignalsOn-LMIDown

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, YESDefault: NO

Memotec Inc. 6-7

WAN Frame Relay

6.2 FR-USER Protocol

6.2.1 Report cycle

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.

6.2.2 SVC address type

For FR-USER protocol only.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:

• The Link Down Busy parameter must be set to NO on all voice ports that may use SVCs to reach their destination.


Report cycle ifwanReportCycle [ifwan#] ReportCycle



SVC address type ifwanSvcAddressType [ifwan#] SvcAddressType

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.

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 104> SVC address type (def:NONE) ? E.164PORT 104> SVC network address (def:) ? 123456789012345PORT 104> SVC max Tx Ack timeout T200 (1-5,def:1) ?PORT 104> SVC inactive timeout T203 (1-60,def:30) ?PORT 104> SVC Iframe retransmissions N200 (1-16,def:3) ?PORT 104> SVC setup timeout T303 (1-30,def:4) ?PORT 104> SVC disconnect timeout T305 (1-30,def:30) ?PORT 104> SVC release timeout T308 (1-30,def:4) ?PORT 104> SVC call proceeding timeout T310 (1-30,def:4) ?PORT 104> SVC status enquiry timeout T322 (1-30,def:4) ?

6.2.3 SVC network address

For FR-USER protocol only.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.

6.2.4 SVC max Tx Ack timeout T200

For FR-USER protocol only.The value of this parameter sets the maximum delay, in seconds, that is allowed between

Values: NONE, E.164, X.121Default: NONE


SVC network address ifwanSvcNetworkAddress [ifwan#] SvcNetworkAd-dress

Values: 0 - 9 for each digit

Default: none


SVC max Tx Ack timeout T200

ifwanSvcMaxTxTimeout-T200

[ifwan#] SvcMaxTxTimeoutT200

Memotec Inc. 6-9

WAN Frame Relay

each transmission and its acknowledgement. This timeout is referred to as T200.

6.2.5 SVC inactive timeout T203

For FR-USER protocol only.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.

SVC Iframe retransmissions N200

For FR-USER protocol only.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.

6.2.6 SVC setup timeout T303

For FR-USER protocol only.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.



SVC inactive timeout T203

ifwanSvcInactiveTime-outT203

[ifwan#] SvcInactiveTimeoutT203



SVC Iframe retransmis-sions N200

IfwanSvcIframeRetrans-missionsN200

[ifwan#] SVCIframe-RetransmissionsN200



SVC setup timeout T303 ifwanSvcSetupTimeout-T303

[ifwan#] SvcSetupTimeoutT303


6-10 Memotec Inc.


6.2.7 SVC disconnect timeout T305

For FR-USER protocol only.The value of this parameter sets the maximum delay, in seconds, allowed for the network to respond to a Q.933 disconnect message. This timeout is referred to as T305.

6.2.8 SVC release timeout T308

For FR-USER protocol only.The value of this parameter sets the maximum delay, in seconds, allowed for the network to respond to a Q.933 release message. This timeout is referred to as T308.

6.2.9 SVC call proceeding timeout T310

For FR-USER protocol only.The value of this parameter sets the maximum delay, in seconds, allowed for the network to respond to a Q.933 call proceeding message. This timeout is referred to as T310.


SVC disconnect timeout T305

IfwanSvcDisconnect-TimeoutT305

[ifwan#] SvcDisconnect-TimeoutT305



SVC release timeout T308

ifwanSvcReleaseTime-outT308

[ifwan#] SvcReleaseTimeoutT308



SVC call proceeding tim-eout T310

IfwanSvcCallProceeding-Timeout

[ifwan#] SvcCall-Pro-ceedingTimeout


Memotec Inc. 6-11

WAN Frame Relay

6.2.10 SVC status enquiry timeout T322

For FR-USER protocol only.The value of this parameter sets the maximum delay, in seconds, allowed for the network to respond to a Q.933 status enquiry message. This timeout is referred to as T322.


SVC status enquiry time-out T322

ifwanSvcStatusTimeout-T322

[ifwan#] SvcStatusTimeoutT322


6-12 Memotec Inc.

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

WAN Frame Relay

7.1 About SE/PVC Configuration ParametersSpecial 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

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.

7.1.2 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 parame-ters will be presented at the console.

• PVCR: The PVC is used over a Frame Relay network to transport data using Memotec’s variable cell relay technology to access a remote NetPerformer. The local NetPerformer port must be a Frame Relay port (FR-USER or FR-NET pro-tocol).

• RFC1490: The PVC is used over a Frame Relay network to access an RFC1490-compatible FRAD (Frame Relay Access Assembler/Disassembler). No fragmen-tation 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 proto-col.

• 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.


PVC number pvcEntry, pvcIndex [pvc#]

Values: Regional unit:Turbo data only unit:Other models:

1 - 3001 - 1281 - 96

Default: 1


Mode pvcMode [pvc#] Mode

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 ModeAdditional 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

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.

7.2.2 DLCI address

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 end-user device attached to the NetPerformer port that this PVC uses.


Port pvcPort [pvc#] Port

Values: 0, numeric range of values determined by the number of ports on the NetPerformer

Default: 1


DLCI address pvcDlciAddress [pvc#] DlciAddress

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 con-figured 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.

7.2.3 Committed Information rate

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),

Values: 0 - 1022Default: 0 (AUTO DLCI for PVCR PVC)


Committed Information rate

pvcInfoRate [pvc#] InfoRate

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.

7.2.4 Burst Information rate

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 Informa-tion Rate Parameters in the Extended Parameters module of this docu-ment series.

7.2.5 Remote unit name

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: 4000 - 6144000Default: 56000


Burst Information rate pvcBurstInfoRate [pvc#] BurstInfoRate

Values: 4000 - 6144000Default: 56000


Remote unit name pvcRemoteUnit [pvc#] RemoteUnit

Values: Maximum 32-character alphanumeric string, determined by remote NetPerformer setup

Default: no value

7-6 Memotec Inc.


7.2.6 Link quality parameterLink quality monitoring is activated on the PVCR links (Ports or PVCs) using the following parameter.

Description: Link quality monitoring activation parameter.

Values: NO, YES. Default is NO.

Description: This parameter represents the link quality level under which the link will be declared down if the monitored link quality is bellow the set threshold.

Values: 0 to 100. Default is 100.

Description: This timer is used to ensure that the link has been in good state long enough to resume the data transmission by bring the link back UP.

Values: 10-1000. Default is 120.

NOTE: This feature works as follows: In a monitored PVCR link where the feature has been activated, all packets received and transmitted are sequenced. That sequence number helps determine if packets are lost on that link at the quality level of the link. When there is little or no user data to transmit on the PVCR link, special HELLO packets are used to fill up the link to evaluate its integrity or quality as per the threshold configured. For this reason the link utilization will always display close to 100% of utilization.

7.2.7 Type

This parameter defines the PVC as a dedicated or backup connection. The possible settings for this parameter are the following:


PVC x / Link quality active frpvcLQActive [frpvc #] LQActive


PVC x / Link quality threshold (in percentage) frpvcLQThreshold [frpvc #] LQThreshold


PVC x / Link quality stabilization delay (s) frpvcLQStabilizationDelay [frpvc #] LQStabilizationDelay


Type pvcType [pvc#] Type

Memotec Inc. 7-7

WAN Frame Relay

• 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 acti-vated 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).

If you choose CALL-BKUP as the PVC type, the following parameters are displayed for setting the backup characteristics:

PVC 3> Type (def:DEDICATED) ? CALL-BKUPPVC 3> Delay before call activation (1-255,def:10) ?PVC 3> Delay before call deactivation (1-255,def:120) ?PVC 3> Call activation timer (30-255,def:30) ?PVC 3> Backup (def:ANY) ? ...

7.2.8 Delay before call activation

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.

7.2.9 Delay before call deactivation

For PVCR mode, Call-Backup type only.Delay, in seconds, before deactivating the backup PVC after the dedicated PVCR connection or PVC has been restored.

Values: DEDICATED, ANSWER, CALL-BKUPDefault: DEDICATED


Delay before call activa-tion

pvcDelayBeforeCall-Activation-s

[pvc#] DelayBeforeCallActi-vation-s



Delay before call deacti-vation

pvcDelayBeforeCallDe-activation-s

[pvc#] DelayBeforeCall-Deactivation-s

7-8 Memotec Inc.


7.2.10 Call activation timer

For PVCR mode, Call-Backup type only.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.

7.2.11 Backup

For PVCR mode, Call-Backup type only.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).

If you choose ANSWER as the PVC type, no extra parameters are required:

PVC 2> Type (def:DEDICATED) ? ANSWERPVC 2> Timeout (ms) (1000-30000,def:1000) ?...

7.2.12 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.



Call activation timer pvcCallActivationTimer [pvc#] CallActivation-Timer



Backup pvcBackup [pvc#] Backup

Values: ANY, ALLDefault: ANY


Timeout (ms) pvcTimeout-ms [pvc#] Timeout-ms

Memotec Inc. 7-9

WAN Frame Relay

7.2.13 Send keepalive packetsThe following parameter prevents the DAMA/BoD system from reserving time slots for “keepalives” when user applications are idle by disabling NetPerformer from sending keepalives packets in those cases. With this parameter, NetPerformer can keep the site logically connected for the applications even when they are idle, without using any satellite bandwidth.

Values: NO, YES. Default is YES.

7.2.14 Verify the link integrityThe following parameter provides the ability for NetPerformer to ensure that the DAMA/BoD satellite system has the time to wake up and activate effective connections for applications that are requesting bandwidth before starting transmission. This improves efficiency of DAMA/BoD systems that are slow with their bandwidth allocation by preventing lost of user data.


7.2.15 Number of retransmission retries

Maximum number of successive retries before the PVC connection is declared down.

7.2.16 Payload compression

Values: 1000 - 30000Default: 1000

Console Text-based Config

PVC x / Send keepalive packets [frpvc #] Keepalive =value

Console Text-based Config

PVC x / Verify the link integrity [frpvc #] LinkIntegrity =value


Number of retransmission retries

pvcRetry [pvc#] Retry



Payload compression pvcCompression [pvc#] Compression

7-10 Memotec Inc.


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).

7.2.17 IP Header CompressionIP Header compression is activated on the PVCR links (Ports or PVCs) using the following parameters:

Description: IP Header compression activation parameter.


NOTE: The above parameter shows up on the PVCR link ports or PVCs only after the IP header compression license has been installed in the unit using the PLS (Product License Status) console command.

The former PVCR links “Compression” parameter has been renamed “Payload compression” to better reflect what this parameter does.

7.2.18 IP address

IP address of the local PVC. This address is a 4-byte value in dotted decimal representation, with a maximum value of 255 for each byte, for example 128.128.128.122. When this parameter is set to 000.000.000.000, no IP address is defined for this PVC. In this case the NetPerformer will use the default IP address defined with the global Default IP Address parameter. For details, refer to the 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: NO, YESDefault: YES


PVC x / IP Header compression frpvcIpHeaderCompression [frpvc #] IpHeaderCompression


IP address pvcIpAddress [pvc#] IpAddress

Memotec Inc. 7-11

WAN Frame Relay

7.2.19 Subnet mask (number of bits)

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 accommo-date this the subnet mask of any IP address can be set to any whole integer value from 0 to 32.

7.2.20 NAT enable

Enables (YES) or disables (NO) Network Address Translation (NAT) on this PVC connection.

When the NAT enable parameter is set to YES, the following additional parameters are

Values: 000.000.000.000 - 255.255.255.255Default: 000.000.000.000


Subnet mask (number of bits)

pvcSubnetMask [pvc#] SubnetMask

Values: 0 - 32 (equivalent to 000.000.000.000 - 255.255.255.255)

Default: 8 (equivalent to 255.000.000.000)


NAT enable pvcNatEnable [pvc#] NatEnable


7-12 Memotec Inc.


also available:

PVC 1> NAT enable (def:NO) ? YESPVC 1> NAT rule (1-10) (def:) ?PVC 1> NAT side (def:INTERNAL) ?

7.2.21 NAT rule

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 module of this document series.

7.2.22 NAT side

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 net-work).

• 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.

7.2.23 IP RIP

Enables or disables the Routing Information Protocol (RIP) on the PVC connection. Three


NAT rule pvcNatRule [pvc#] NatRule

Values: 1 - 10Default: none


NAT side pvcNatSide [pvc#] NatSide

Values: INTERNAL, EXTERNALDefault: INTERNAL


IP RIP pvcIpRip [pvc#] IpRip

Memotec Inc. 7-13

WAN Frame Relay

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 rout-ers 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 particu-lar destination (for management under SNMP, for example) you can configure a static IP address using the IP Static menu, described in the LAN Connec-tion and IP Networks module of this document series.

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 BROADCASTPVC 1> IP RIP TX/RX (def:DUPLEX) ? PVC 1> IP RIP Authentication (def:NONE) ? PVC 1> IP RIP Password (def:) ?

7.2.24 IP RIP TX/RX

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

Values: DISABLE, V1, V2 BROADCAST, V2 MULTICASTDefault: V1


IP RIP TX/RX pvcIpRipTxRx [pvc#] IpRipTxRx

7-14 Memotec Inc.


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.

7.2.25 IP RIP authentication

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.

7.2.26 IP RIP password

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.

NOTE: The value of the IP RIP Password parameter must be the same for each inter-face on both sides of the network.

Values: DUPLEX, TX ONLY, RX ONLYDefault: DUPLEX


IP RIP authentication pvcIpRipAuthType [pvc#] IpRipAuthType

Values: NONE, SIMPLEDefault: NONE


IP RIP password pvcIpRipPassword [pvc#] IpRipPassword

Values: alphanumeric string, maximum 8 characters

Default: none

Memotec Inc. 7-15

WAN Frame Relay

7.2.27 OSPF

Enables or disables the OSPF protocol on the interface. By default, OSPF is disabled on all NetPerformer Frame Relay connections. Set this parameter to ENABLE to enable OSPF. Each slot, port and PVC must be enabled separately. If OSPF is enabled, the interface will be advertised as an internal route to an area of the Autonomous System (AS). To disable OSPF, set this parameter to DISABLE.

NOTE: When OSPF is enabled, additional OSPF parameters appear on the console and must be defined:

PVC 1> OSPF (def:DISABLE) ? ENABLEPVC 1> OSPF Area ID (def:000.000.000.000) ?PVC 1> OSPF Transit delay (1-360,def:1) ?PVC 1> OSPF Retransmit interval (1-360,def:5) ?PVC 1> OSPF Hello interval (1-360,def:10) ?PVC 1> OSPF Dead interval (1-2000,def:40) ?PVC 1> OSPF Authentication type (def:NONE) ?PVC 1> OSPF 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.2.28 IP multicast active

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.


OSPF pvcOspfEnable [pvc#] OspfEnable

Values: DISABLE, ENABLEDefault: DISABLE


IP multicast active pvcIpMulticastActive [pvc#] IpMulticastActive


7-16 Memotec Inc.


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.

7.2.29 IP multicast protocol

Selects the IP multicast protocol.

• PIMDM: Protocol Independent Multicast - Dense Mode. This routing algorithm was designed for multicast groups that are densely distributed across the net-work.

• NONE: No IP multicast protocol is used.

7.2.30 IPX RIP

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 Net-work Number parameter, described below.


IP multicast protocol pvcIpMulticastProtocol [pvc#] IpMulticastProto-col

Values: NONE, PIMDMDefault: NONE


IPX RIP pvcIpxRip [pvc#] IpxRip

Memotec Inc. 7-17

WAN Frame Relay

7.2.31 IPX SAP

For a unit with Voice transport method set to POWERCELL only.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.

7.2.32 IPX network number

For a unit with Voice transport method set to POWERCELL only.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 number must be defined, using the Setup IPX menu. For details, refer to the Digital Data module of this document series.

7.2.33 BRG connection

For a unit with Voice transport method set to POWERCELL only.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.



IPX SAP pvcIpxSap [pvc#] IpxSap



IPX network number pvcIpxNetNum [pvc#] IpxNetNum

Values: 00000000 - FFFFFFFFDefault: 00000000


BRG connection pvcBrgConnection [pvc#] BrgConnection

7-18 Memotec Inc.


7.2.34 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/FIL-TER 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.

7.2.35 Broadcast group

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



Filter pvcFilter [pvc#] Filter

Values: An automatically generated list of filter numbers

Default: ALL


Broadcast group pvcBroadcastGroup [pvc#] BroadcastGroup

Memotec Inc. 7-19

WAN Frame Relay

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.

7.2.36 Maximum number of voice channels

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 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.

7.2.37 Maximum Voice Channels If High Priority Data

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 number of voice channels

pvcMaxChannels [pvc#] MaxChannels

Values: 0 - 10000Default: 10000 (no blocking)


Maximum Voice Channels If High Pri-ority Data

pvcLowMaxChannels [pvc#] LowMaxChannels

7-20 Memotec Inc.


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 param-eter.

• 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.

Caution: For any new voice calls, the lower call blocking limit will take effect, either the Maximum number of voice channels (see previous param-eter) 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.

7.2.38 Use this port as default gateway

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: 0 - 10000Default: 10000 (no call blocking)


Use this port as default gateway

pvcIsDefaultGateway [pvc#] IsDefaultGateway

Memotec Inc. 7-21

WAN Frame Relay

7.2.39 Redundant link

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.



Redundant link pvcRedundantLink [pvc#] RedundantLink


7-22 Memotec Inc.


7.3 RFC1490 Mode

7.3.1 Frame size

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.

7.3.2 IP connection

Allows or disallows an IP connection. Set this parameter to YES if the RFC1490-compatible 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.

7.3.3 IPX connection

For a unit with Voice transport method set to POWERCELL only.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.


Frame size pvcMaxFrame [pvc#] MaxFrame



IP connection pvcIpConnection [pvc#] IpConnection



IPX connection pvcIpxConnection [pvc#] IpxConnection


Memotec Inc. 7-23

WAN Frame Relay

7.3.4 LLC connection

Allows or disallows an LLC connection. Set this parameter to YES if the RFC1490-compatible 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.


LLC connection pvcLlcConnection [pvc#] LlcConnection


7-24 Memotec Inc.


7.4 MULTIPLEX Mode

7.4.1 Remote PVC number

For a PVC in MULTIPLEX mode only.The remote PVC to which data from the local PVC is sent. Specify the remote PVC number.

7.4.2 Class number

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.


Remote PVC number pvcRemotePvc [pvc#] RemotePvc

Values: 1 - 300Default: the local PVC number


Class number pvcClass [pvc#] Class

Values: 1 - 8, HIGH PRIORITYDefault: 3

Memotec Inc. 7-25

WAN Frame Relay

7.5 TRANSP Mode

7.5.1 User port

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).

7.5.2 Network port

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.

7.5.3 User DLCI

The DLCI address of the transparent PVC on the user side.


User port pvcUserPort [pvc#] UserPort

Values: automatically generated list of ports

Default: 1


Network port pvcNetworkPort [pvc#] NetworkPort

Values: automatically generated list of ports

Default: 1


User DLCI pvcUserDlci [pvc#] UserDlci

7-26 Memotec Inc.


7.5.4 Network DLCI

The DLCI address of the transparent PVC on the network side.



Network DLCI pvcNetworkDlci [pvc#] NetworkDlci


Memotec Inc. 7-27

WAN Frame Relay

7-28 Memotec Inc.

Index

AAnswer-only PVC 7-8Authentication type, for IP RIP 7-15Auto-learning of DLCI address 7-4

BBackup

for PVC 7-9Backup PVC 7-7

call delay 7-8Bad frames

display of 4-19BRG connection

for PVC 7-18Broadcast group

for PVC 7-19Burst Information rate

for PVC 7-6

CCall activation timer

for PVC 7-9Call-backup PVC 7-8Channel sequence errors, display of 4-24CI display 4-31, 4-35CIR 2-3Class number 7-25CLLM function

Frame Relay 6-5Committed Information rate

for PVC 7-5Compression

for PVC 7-10Configuration

PVC parameters 3-8Congestion

Frame Relay 1-3Congestion flow control

Frame Relay 6-4Counters 4-3, 4-18, 4-29

resetting 4-17

DDC command 4-3, 4-18, 4-29Dedicated PVC 7-7Delay before call activation

for PVC 7-8Delay before call deactivation

for PVC 7-8Display Errors command 4-18Display States command

for PVCs 4-35DLCI

displaying for PVC 4-37displaying for SVC 4-40

DLCI address 1-3for PVC 7-4

DLCI Address, for FRoIP 5-5Drop signals on LMI down

Frame Relay 6-6DS command

for PVCs 4-35DTE/DCE

display of 4-34

EEnquiry timer 6-4Errors

display of 4-18resetting counters 4-17

FFallback

disabling 6-2Fallback speed 6-2Filter

for PVC 7-19Frame delay 6-3Frame over IP, destination 5-5, 5-11Frame over IP, port number 5-6, 5-11Frame over IP, precedence 5-6, 5-12Frame over IP, source 5-5, 5-10Frame Relay 1-2

congestion monitoring 1-3management protocol 1-3protocols 2-2

Frame Relay Forum, parameter names used 2-6Frame Relay full status report 7-4Frame Relay over IP

Application 5-7Configuration 5-4Implementation 5-3Statistics 5-15

WAN Frame Relay 1

Frame sizefor PVC 7-23

GGlobal CIR for FR over IP 5-4Global parameters

for FRoIP 5-4Groups

definition of 4-25

IIncomplete frames 4-20Information signal

inactive 4-36, 4-40Information signals

displaying for PVC 4-36displaying for SVC 4-40

Information statusof PVCs 4-36

INTERFACEdisplaying for Frame Relay 4-34

Interfacedisplay of 4-34displaying for Frame Relay 4-30

IP addressfor PVC 7-11

IP connectionfor PVC 7-23

IP multicast activefor PVC 7-16

IP multicast protocolfor PVC 7-17

IP RIPdirectionality, for PVC link 7-14enabling 7-13for PVC 7-13

IP RIP authenticationfor PVC 7-15

IP RIP passwordfor PVC 7-15

IP RIP TX/RXfor PVC 7-14

IP routing 7-13, 7-15IPX connection

for PVC 7-23IPX network number

for PVC 7-18IPX RIP

for PVC 7-17IPX RIP routing 7-17IPX routing 7-18IPX SAP

for PVC 7-18IPX SAP routing 7-18

LLLC connection

for PVC 7-24Logical state

of ports 4-31, 4-35of PVCs 4-36

MManagement interface

Frame Relay 6-3Max number of voice channels over IP 5-4Max voice channels over IP if high priority data 5-4Maximum number of voice channels

for PVC 7-20Maximum Voice Channels If High Priority Data

for PVC 7-20Mode

displaying for PVC 4-36displaying for SVC 4-39for PVC 7-2

MODEM SIGNALSdisplaying for Frame Relay 4-34

Modem signalsdisplaying for Frame Relay 4-31status, display of 4-34

MULTIPLEX modechannel sequence errors 4-24

NNACFB display 4-36, 4-40NAT enable

for PVC 7-12NAT rule

for PVC 7-13NAT side

for PVC 7-13Network DLCI

for PVC 7-27Network number, for IPX routing 7-18Network port

for PVC 7-26Next hop 5-13NNI system parameters 2-6Number of bad frames

displaying for Frame Relay 4-19Number of BECN received

displaying on PVC 4-6displaying on SVC 4-10

Number of BECN transmitteddisplaying on PVC 4-6

Number of BECN transmitted, displaying on SVC 4-11

Number of channel abort errors

2 Memotec Inc.

displaying on PVC 4-23Number of channel overflow errors

displaying on PVC 4-23Number of channel sequence errors

displaying on PVC 4-24Number of CLLM frames received

displaying on SVC 4-11Number of CLLM frames received, displaying on

PVC 4-7Number of CLLM frames transmitted


Number of compressor errorsdisplaying on PVC 4-23

Number of errorsdisplaying for SVC 4-27displaying on PVC 4-21

Number of FECN receiveddisplaying on PVC 4-7displaying on SVC 4-11

Number of FECN transmitteddisplaying on PVC 4-7displaying on SVC 4-11

Number of frames discarded (CRC)displaying for SVC 4-27

Number of frames discarded (overrun)displaying for Frame Relay 4-20displaying for SVC 4-27displaying on PVC 4-22

Number of frames receiveddisplaying on PVC 4-6displaying on SVC 4-10

Number of frames transmitteddisplaying on PVC 4-6displaying on SVC 4-10

Number of invalid frames discardeddisplaying on PVC 4-22

Number of invalid octets discardeddisplaying 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)displaying for Frame Relay 4-21displaying for SVC 4-27displaying on PVC 4-23

Number of octets receiveddisplaying on PVC 4-6displaying on SVC 4-10

Number of octets transmitteddisplaying on PVC 4-6displaying on SVC 4-10

Number of restartsdisplaying for Frame Relay 4-20

displaying for SVC 4-27displaying on PVC 4-22

Number of retransmission retriesfor PVC 7-10

Number of retriesdisplaying for Frame Relay 4-20

Number of underrunsdisplaying for Frame Relay 4-20

OOperating mode

of PVC 2-2OSPF

for PVC 7-16

PParameter list

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

20

WAN Frame Relay 3

Maximum Voice Channels If High Priority Data, for PVC 7-20

Mode, for PVC 7-2NAT Enable, for PVC 7-12NAT Rule, for PVC 7-13NAT Side, for PVC 7-13Network DLCI, for PVC 7-27Network port, for PVC 7-26Number of retransmission retries, for PVC 7-10OSPF, for PVC 7-16Port, used by PVC 7-4Protocol, Frame Relay 3-3PVC number, Frame Relay 7-2Reference port for conditional LMI, Frame

Relay 6-5Remote PVC number, for Frame Relay 7-25Remote unit name, for PVC 7-6Report cycle, Frame Relay 6-8Subnet mask, for PVC 7-12SVC address type, Frame Relay 6-8SVC call proceeding timeout T310, Frame

Relay 6-11SVC disconnect timeout T305, Frame Relay 6-

11SVC Iframe retransmissions N200, Frame

Relay 6-10SVC inactive timeout T203, Frame Relay 6-10SVC max Tx Ack timeout T200, Frame Relay 6-

9SVC network address, Frame Relay 6-9SVC release timeout T308, Frame Relay 6-11SVC setup timeout T303, Frame Relay 6-10SVC status enquiry timeout T322, Frame Relay

6-12Timeout, for PVC 7-9Type, of PVC 7-7User DLCI, for PVC 7-26User port

for PVC 7-26Password

for IP RIP 7-15Port

for FRoIP 5-5used by PVC 7-4

PORT n display 4-30PORT n ERROR display 4-19Port, for FRoIP forced route 5-13PORT#

displaying for Frame Relay 4-33Ports

display of bad frames 4-19displaying status 4-31, 4-35interface, display of 4-34logical state 4-31, 4-35number, display of 4-33

physical state 4-30speed, display of 4-30, 4-34

PowerCell PVC 3-10Protocol

displaying for Frame Relay 4-30displaying for SVC 4-39Frame Relay 3-3of WAN/user port 3-3

PVC command 3-8PVC number

Frame Relay 7-2PVC parameters

for FRoIP 5-4PVC status display 4-35PVCR

configuration of PVC 3-10PVCs 1-3

bridge connection 7-18broadcast group 7-19burst information rate 7-6call delay 7-8committed information rate 7-5dial timeout 7-9display of channel sequence errors 4-24enabling IP RIP 7-13hang delay 7-8information status 4-36IP address 7-11IP connection 7-23IP RIP authentication type 7-15IP RIP directionality 7-14IP RIP password 7-15IPX connection 7-23IPX network number 7-18IPX RIP 7-17IPX SAP 7-18LLC connection 7-24logical state 4-36maximum frame size 7-23modes, selecting 2-2network port 7-26on remote unit 7-25parameters, configuration of 3-8User DLCI address 7-26user port 7-26

QQ 922 Tx bytes 4-13Q922 Data link established 4-12Q922 Establish indications 4-12Q922 Missing control blocks 4-28Q922 Release indications 4-12Q922 Rx Ack expiry 4-28Q922 Rx bytes 4-13Q922 Rx frames 4-13

4 Memotec Inc.

Q922 statedisplaying for Frame Relay 4-31

Q922 Tx Ack expiry 4-28Q922 Tx frames 4-13Q922 Tx Iframe Q discards 4-13Q922 Tx retransmissions 4-12Q933 Invalid Rx sizes 4-28Q933 Protocol timeouts 4-17Q933 Rx call proceeding messages 4-15Q933 Rx connect messages 4-15Q933 Rx disconnect messages 4-16Q933 Rx release complete messages 4-16Q933 Rx release messages 4-15Q933 Rx setup messages 4-14Q933 Rx status enquiry messages 4-17Q933 Rx status messages 4-16Q933 Setup success rate 4-14Q933 Tx call proceeding messages 4-14Q933 Tx connect messages 4-15Q933 Tx disconnect messages 4-16Q933 Tx release complete messages 4-15Q933 Tx release messages 4-15Q933 Tx setup messages 4-14Q933 Tx status enquiry messages 4-16Q933 Tx status messages 4-16

RReceiver rate (M)


Receiver rate (P)displaying on PVC 4-5

Receiver rate (P), displaying on SVC 4-10Redundant link

for PVC 7-22Reference port for conditional LMI

Frame Relay 6-5Remote PVC number

for Frame Relay 7-25Remote unit name

displaying for PVC 4-37for PVC 7-6

Report cycleFrame Relay 6-8

Reset Counters command 4-17Routing

IP 7-13, 7-15IPX 7-18IPX RIP 7-17IPX SAP 7-18

RS-232 interfacemodem signal status 4-31, 4-34

SSend keepalive packets 7-10Setup PVC menu 3-8Sorter overruns

displaying for port/PVC group 4-25Sorter rejected cells

displaying for port/PVC group 4-26Sorter timeouts

displaying for port/PVC group 4-26Sorter window overflows

displaying for port/PVC group 4-25Speed

display of 4-34SPEED (BPS)

displaying for Frame Relay 4-34Speed used

displaying for Frame Relay 4-30displaying for PVC 4-37displaying for SVC 4-40

Statedisplaying for Frame Relay 4-31displaying for SVC 4-40

State & Delaydisplaying for PVC 4-37

STATE DELAYdisplaying for Frame Relay 4-35

Statisticsdisplaying errors 4-18displaying for SVC 4-40DLCI, displaying for PVC 4-37Information signals, displaying for PVC 4-36Information signals, displaying for SVC 4-40INTERFACE, displaying for Frame Relay 4-34Interface, displaying for Frame Relay 4-30logical state of port 4-31, 4-35logical state of PVC 4-36Mode, displaying for PVC 4-36Mode, displaying for SVC 4-39MODEM SIGNALS, displaying for Frame Relay

4-34Modem signals, displaying for Frame Relay 4-

31Number of bad frames, displaying for Frame

Relay 4-19Number of BECH transmitted, displaying on

SVC 4-11Number of BECN received, displaying on PVC 4-

6Number of BECN received, displaying on SVC

4-10Number of BECN transmitted, displaying on

PVC 4-6Number of channel abort errors, displaying on

PVC 4-23

WAN Frame Relay 5

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, displaying on PVC 4-7

Number of CLLM frames transmitted, displaying on SVC 4-11

Number of compressor errors, displaying on PVC 4-23

Number of errors, displaying for SVC 4-27Number of errors, displaying on PVC 4-21Number of FECN received, displaying on PVC 4-

7Number of FECN received, displaying on SVC 4-

11Number of FECN transmitted, displaying on

PVC 4-7Number of FECN transmitted, displaying on

SVC 4-11Number of frames discarded (CRC), displaying

for SVC 4-27Number of frames discarded (overrun),

displaying for Frame Relay 4-20Number of frames discarded (overrun),

displaying for SVC 4-27Number of frames discarded (overrun),

displaying on PVC 4-22Number of frames received, displaying on PVC

4-6Number of frames transmitted, displaying on

PVC 4-6Number of frames transmitted, displaying on

SVC 4-10Number of invalid frames discarded, displaying

on PVC 4-22Number of invalid octets discarded, displaying

on PVC 4-22Number of octets discarded (bad), displaying

for Frame Relay 4-20Number of octets discarded (CRC), displaying

for SVC 4-27Number of octets discarded (overrun),

displaying for Frame Relay 4-21Number of octets discarded (overrun),

displaying for SVC 4-27Number of octets discarded (overrun),

displaying on PVC 4-23Number 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-27Number of restarts, displaying on PVC 4-22Number of retries, displaying for Frame Relay

4-20Number of sorter overruns, displaying for port/

PVC group 4-25Number of sorter timeouts, displaying for port/

PVC group 4-26Number of underruns, displaying for Frame

Relay 4-20PORT#, displaying for Frame Relay 4-33PROTOCOL, displaying for Frame Relay 4-33Protocol, displaying for Frame Relay 4-30Protocol, displaying for SVC 4-39Q922 Data link established 4-12Q922 Establish indications 4-12Q922 Invalid Rx sizes 4-28Q922 Missing control blocks 4-28Q922 Release indications 4-12Q922 Rx Ack expiry 4-28Q922 Rx bytes 4-13Q922 Rx frames 4-13Q922 state, displaying for Frame Relay 4-31Q922 Tx Ack expiry 4-28Q922 Tx bytes 4-13Q922 Tx frames 4-13Q922 Tx Iframe Q discards 4-13Q922 Tx retransmissions 4-12Q933 Protocol timeouts 4-17Q933 Rx call proceeding messages 4-15Q933 Rx connect messages 4-15Q933 Rx disconnect messages 4-16Q933 Rx release complete messages 4-16Q933 Rx release messages 4-15Q933 Rx setup messages 4-14Q933 Rx status enquiry messages 4-17Q933 Rx status messages 4-16Q933 Setup success rate 4-14Q933 Tx call proceeding messages 4-14Q933 Tx connect messages 4-15Q933 Tx disconnect messages 4-16Q933 Tx release complete messages 4-15Q933 Tx release messages 4-15Q933 Tx setup messages 4-14Q933 Tx status enquiry messages 4-16

6 Memotec Inc.

Q933 Tx status messages 4-16Receiver rate (M), displaying on PVC 4-5Receiver rate (M), displaying on SVC 4-9Receiver rate (P), displaying on PVC 4-5Receiver rate (P), displaying on SVC 4-10Remote unit name, displaying for PVC 4-37resetting counters 4-17SPEED (BPS), displaying for Frame Relay 4-34Speed used, displaying for Frame Relay 4-30Speed used, displaying for PVC 4-37Speed used, displaying for SVC 4-40State & Delay, displaying for PVC 4-37STATE DELAY, displaying for Frame Relay 4-35State, displaying for Frame Relay 4-31State, displaying for SVC 4-40Transmitter rate (M), displaying on PVC 4-5Transmitter rate (M), displaying on SVC 4-9Transmitter rate (P), displaying on PVC 4-5Transmitter rate (P), displaying on SVC 4-9

Statistics Number of frames received, displaying on SVC 4-10

STDRCI display 4-31, 4-34Subnet mask

for PVC 7-12SVC address type

Frame Relay 6-8SVC call proceeding timeout T310

Frame Relay 6-11SVC disconnect timeout T305

Frame Relay 6-11SVC Iframe retransmissions N200

Frame Relay 6-10SVC inactive timeout T203

Frame Relay 6-10SVC max Tx Ack timeout T200

Frame Relay 6-9SVC network address

Frame Relay 6-9SVC release timeout T308

Frame Relay 6-11SVC setup timeout T303

Frame Relay 6-10SVC status enquiry timeout T322

Frame Relay 6-12SVCs

configuring 3-6, 6-4, 6-9, 6-10, 6-11, 6-12

TTimeout

for PVC 7-9Timer in ms for FR over IP 5-4Transmitter rate (M)


Transmitter rate (P)


Typeof PVC 7-7

UUQFSBA display 4-19Use a forced route 5-13Use this port as default gateway

for PVC 7-21User DLCI

for PVC 7-26User port

for PVC 7-26

VV.35 interface

modem signal status 4-31, 4-34Verify the link integrity 7-10Version

for IP RIP 7-13Voice fallback 1-3Voice Traffic Control 7-20

WWait for ACK timeout 7-9WAN/User ports

protocol 3-3

XX.21 interface

modem signal status 4-31, 4-35X.25 Protocol

defining Multiplex PVC for 3-12defining Transparent PVC for 7-26

WAN Frame Relay 7

REACH FURTHER. OFFER MORE.

Contact Memotec:

tel.: +1-514-738-4781e-mail: [email protected]

7755 Henri Bourassa Blvd. West Montreal, Quebec | Canada H4S 1P7 www.memotec.com

Documents

WAN Frame Relay System Reference - Comtech EF Data€¦ · · 2017-02-24WAN/Frame Relay NetPerformer® System Reference. COPYRIGHTS AND DISCLAIMERS Published Date: May 2014 Document