Legacy Data System Reference - Comtech EF Data

Legacy Data 

NetPerformer ® System Reference

COPYRIGHTS AND DISCLAIMERS 

Published Date: April 2011 

Document # 1602 

This publication contains information proprietary and confidential to Memotec Inc. Any reproduction, 

disclosure or unauthorized use of this publication is expressly prohibited except as Memotec Inc. may 

otherwise authorize in writing. 

Memotec Inc. reserves the right to make changes without notice in product or component design as warranted 

by evolution in user needs or progress in engineering or manufacturing technology. Changes which affect the 

operation of the unit will be documented in the next revision of the manual. 

We have made every effort to ensure the accuracy of the information presented in our documentation. 

However, Memotec assumes no responsibility for the accuracy of the information published. Product 

documentation is subject to change without notice. Changes, if any, will be incorporated in new editions of 

these documents. Memotec may make improvements or changes in the products or programs described within 

the documents at any time without notice. Mention of products or services not manufactured or sold by 

Memotec is for informational purposes only and constitutes neither an endorsement nor a recommendation for 

such products or services. 

Memotec Inc. is a wholly owned subsidiary of Comtech EF Data Corp., and its parent company Comtech 

Telecommunications Corp (NASDAQ: CMTL). 

AccessView, CXTool, CX-U Series, CX-UA Series, AbisXpress, NetPerformer, AccessGate, ACTView, SDM- 

8400, and the SDM-9000 series of products are either registered trademarks or trademarks of Memotec Inc.in 

Canada, the United States of America, and in other countries. 

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

Any other trademarks are the property of their respective companies. 

Copyright © 2011 Memotec Inc. 

Memotec Inc. 

7755 Henri Bourassa Blvd. West 

Montreal, Quebec 

Canada H4S 1P7 

Tel.: (514) 738-4781 

FAX: (514) 738-4436 

www.memotec.com

Contents 

Chapter 1: HDLC Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 

1. 1 HDLC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 

1. 2 NetPerformer Support of HDLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 

1. 3 Configuring an HDLC Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 

1.3.1 HDLC Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 

1.3.2 HDLC Channel Configuration on Dual Serial Interface Card . . . 1-5 

1.3.3 HDLC Channel Configuration on Digital Channel . . . . . . . . . . . 1-6 

Chapter 2: HDLCOFR Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 

2. 1 NetPerformer Support of HDLCOFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 

2. 2 Configuring an HDLCOFR Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 

Chapter 3: PASSTHRU Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 

3. 1 PASSTHRU Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 

3. 2 NetPerformer Support of PASSTHRU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 

3. 3 Configuring a PASSTHRU Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 

3.3.1 PASSTHRU Channel on a Serial Port . . . . . . . . . . . . . . . . . . . . 3-3 

3.3.2 PASSTHRU Channel on a Digital Channel . . . . . . . . . . . . . . . . 3-3 

Chapter 4: PASSTHRUOFR Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 

4. 1 Support of PASSTHRU over Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . 4-2 

4.1.1 Number of Digital PASSTHRUOFR Channels Supported . . . . . 4-3 

4. 2 Configuring for PASSTHRU over Frame Relay . . . . . . . . . . . . . . . . . . . . . 4-4 

4. 3 Configuring a PASSTHRUOFR Connection . . . . . . . . . . . . . . . . . . . . . . . 4-5 

4.3.1 Built-in Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 

4.3.2 Serial Port on Dual Serial Interface Card . . . . . . . . . . . . . . . . . . 4-6 

4.3.3 Digital Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 

4. 4 Fine Tuning the Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 

4.4.1 Serial PASSTHRUOFR Port . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 

4.4.2 Digital PASSTHRUOFR Channel. . . . . . . . . . . . . . . . . . . . . . . . 4-8 

Chapter 5: Asynchronous Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 

5. 1 NetPerformer Support of Asynchronous Data Traffic . . . . . . . . . . . . . . . . 5-2 

5. 2 R-ASYNC Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 

Memotec Inc.

Memotec Inc. 

5. 3 T-ASYNC Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 

5. 4 Configuring an Asynchronous Data Connection . . . . . . . . . . . . . . . . . . . . 5-3 

5.4.1 T-ASYNC Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 

5.4.2 R-ASYNC Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 

Chapter 6: SNA/SDLC Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 

6. 1 NetPerformer Support of SNA/SDLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 

6.1.1 SDLC Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 

6.1.2 SNA/SDLC Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 

6.1.3 PUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 

6.1.4 Session Timeout Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 

6.1.5 Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 

6.1.6 LLC Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 

6.1.7 SNA Over RFC-1490 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 

6.1.8 Network Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 

6. 2 Configuring an SNA/SDLC Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 

6.2.1 Configuring a Primary SDLC Port . . . . . . . . . . . . . . . . . . . . . . . 6-8 

6.2.2 Configuring a Secondary SDLC Port . . . . . . . . . . . . . . . . . . . . . 6-9 

6. 3 Configuring a PU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11 

6.3.1 Configuring a PU in SDLC-SDLC Mode . . . . . . . . . . . . . . . . . 6-11 

6.3.2 Configuring a PU in SDLC-LINKS Mode . . . . . . . . . . . . . . . . . 6-11 

6.3.3 Configuring a PU in SDLC-LLC Mode . . . . . . . . . . . . . . . . . . . 6-12 

6.3.4 Configuring a PU in SDLC-BAN Mode . . . . . . . . . . . . . . . . . . 6-13 

6.3.5 Configuring a PU in SDLC-BNN Mode . . . . . . . . . . . . . . . . . . 6-14 

6.3.6 Configuring a Non-SDLC PU Connection . . . . . . . . . . . . . . . . 6-15 

Chapter 7: BSC Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 

7. 1 BSC Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 

7. 2 NetPerformer Support of BSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 

7.2.1 Reception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 

7.2.2 Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 

7. 3 Configuring a BSC Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 

7.3.1 BSC on a Built-in Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 

7.3.2 BSC on the Dual Serial Interface Card . . . . . . . . . . . . . . . . . . . 7-4 

Chapter 8: COP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 

8. 1 Support of Character-oriented Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 

8.1.1 Reception: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

8.1.2 Transmission:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 

8. 2 Configuring a COP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 

8.2.1 COP on a Built-in Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 

8.2.2 COP on the Dual Serial Interface Card . . . . . . . . . . . . . . . . . . . 8-4 

Chapter 9: X.25 Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 

9. 1 NetPerformer Support of X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 

9.1.1 X.25 Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 

9.1.2 HDLC Driver Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 

9. 2 Configuring an X25 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 

9.2.1 X25 on a built-in Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 

9.2.2 X25 on the Dual Serial Interface Card . . . . . . . . . . . . . . . . . . . . 9-4 

9. 3 X.25 Application Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 

Chapter 10: IPX Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 

10. 1 NetPerformer Support of IPX Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 

10. 2 Configuring an IPX Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3 

10.2.1 Global IPX Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5 

10.2.2 IPX SAP Filtering Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 10-5 

10. 3 Checking IPX Connection Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6 

10.3.1 IPX RIP Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6 

10.3.2 IPX SAP Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7 

Chapter 11: Monitoring Data Port Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 

11. 1 Checking Legacy Data Connection Status . . . . . . . . . . . . . . . . . . . . . . . 11-2 

11. 2 Display Counters (DC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3 

11. 3 Display States (DS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5 

11. 4 Display Port States (DPORT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7 

11. 5 Display Errors (DE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8 

11. 6 Display PU States (DPU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10 

11. 7 Display Parameters (DP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11 

11. 8 Displaying Active PUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12 

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

12. 1 Common Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2 

12.1.1 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2 

Memotec Inc.

Memotec Inc. 

12.1.2 Port speed (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3 

12.1.3 Clocking mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3 

12. 2 HDLC and PASSTHRU Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5 

12.2.1 Fallback speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5 

12.2.2 Transmission start level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6 

12.2.3 Modem control signal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7 

12.2.4 Frame delay (ms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9 

12.2.5 CRC encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9 

12.2.6 Idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9 

12.2.7 Remote unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10 

12.2.8 Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10 

12.2.9 Remote port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11 

12.2.10 Subchanneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11 

12.2.11 Subchannel mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11 

12. 3 HDLCOFR Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13 

12.3.1 Tx/Rx mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13 

12.3.2 PVC number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13 

12. 4 PASSTHRU Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14 

12.4.1 Congestion flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14 

12. 5 PASSTHRUOFR Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14 

12.5.1 Dynamic clocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14 

12. 6 T-ASYNC Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15 

12.6.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15 

12. 7 R-ASYNC Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16 

12.7.1 Reception flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16 

12.7.2 Transmission flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16 

12.7.3 Transmit holding time (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16 

12. 8 P-SDLC Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17 

12.8.1 SDLC duplex mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17 

12.8.2 Group poll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17 

12.8.3 Group address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17 

12.8.4 Poll delay (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18 

12. 9 COP Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19 

12.9.1 Synchronization character . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19 

12.9.2 Number of desynch. character. . . . . . . . . . . . . . . . . . . . . . . . 12-19 

12.9.3 Desynchronization character . . . . . . . . . . . . . . . . . . . . . . . . . 12-19 

12. 10 X25 Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21

12.10.1 X25 frame relay encapsulation. . . . . . . . . . . . . . . . . . . . . . . . 12-21 

Chapter 13: SE/PU Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1 

13. 1 SDLC-SDLC Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 

13.1.1 PU number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 

13.1.2 Operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 

13.1.3 Controller active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3 

13.1.4 Delay before connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3 

13.1.5 SDLC primary port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4 

13.1.6 SDLC primary address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4 

13.1.7 SDLC secondary port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4 

13.1.8 SDLC secondary address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5 

13.1.9 SDLC retransmission timeout (ms) . . . . . . . . . . . . . . . . . . . . . 13-5 

13.1.10 SDLC number of retransmission retries . . . . . . . . . . . . . . . . . . 13-5 

13.1.11 SDLC transmission window size . . . . . . . . . . . . . . . . . . . . . . . 13-6 

13.1.12 XID support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6 

13.1.13 Suppress DM upon disconnection . . . . . . . . . . . . . . . . . . . . . . 13-6 

13. 2 SDLC-LINKS Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7 

13.2.1 SDLC port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7 

13.2.2 SDLC address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7 

13.2.3 SDLC frame size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7 

13.2.4 Remote unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8 

13.2.5 Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8 

13.2.6 Remote PU number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8 

13. 3 SDLC-LLC Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9 

13.3.1 LLC lan port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9 

13.3.2 LLC destination address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9 

13.3.3 LLC source SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9 

13.3.4 LLC destination SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10 

13.3.5 LLC retransmission timeout (ms). . . . . . . . . . . . . . . . . . . . 13-10 

13.3.6 LLC maximum successive retries . . . . . . . . . . . . . . . . . . . . . 13-11 

13.3.7 LLC transmission window size . . . . . . . . . . . . . . . . . . . . . . . . 13-11 

13.3.8 LLC dynamic window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11 

13.3.9 LLC frame size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12 

13.3.10 XID support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12 

13.3.11 XID identification number . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13 

13.3.12 XID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13 

13.3.13 XID PU type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14 

13. 4 SDLC-BAN Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15 

13.4.1 BAN destination address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15 

Memotec Inc.

Memotec Inc. 

13.4.2 BAN/BNN source SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15 

13.4.3 BAN/BNN destination SAP . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15 

13.4.4 BAN/BNN retransmission timeout (ms) . . . . . . . . . . . . . . . . . 13-16 

13.4.5 BAN/BNN maximum successive retries. . . . . . . . . . . . . . . . . 13-16 

13.4.6 BAN/BNN transmission window size . . . . . . . . . . . . . . . . . . . 13-17 

13.4.7 BAN/BNN dynamic window . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17 

13.4.8 BAN/BNN frame size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18 

13.4.9 BAN routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18 

13. 5 SDLC-BNN Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19 

13.5.1 BNN PVC number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19 

13.5.2 BNN FID type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19 

13. 6 Non-SDLC PU Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20 

13.6.1 LLC Role / BAN/BNN Role . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20 

Chapter 14: SE/IPX Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1 

14. 1 IPX Parameters on the Ethernet Por or WAN Connection . . . . . . . . . . . 14-2 

14.1.1 IPX RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2 

14.1.2 IPX SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2 

14.1.3 IPX network number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3 

14.1.4 IPX encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3 

14. 2 SE/IPX/GLOBAL Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4 

14.2.1 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4 

14.2.2 Internal network number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4 

14. 3 SE/IPX/FILTER Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7 

14.3.1 IPX Filter entry number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7 

14.3.2 Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7 

14.3.3 SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7 

14.3.4 Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8 

Chapter 15: IPX Display Command Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1 

15. 1 IPX Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2 

15.1.1 DR/IPX/RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2 

15.1.2 NETWORK NUMBER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2 

15.1.3 TICKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2 

15.1.4 HOP COUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2 

15.1.5 NEXT HOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2 

15.1.6 AGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2 

15.1.7 DR/IPX/SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3 

15.1.8 NET NUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

15.1.9 NODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3 

15.1.10 SOCKET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3 

15.1.11 SERVICE NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4 

15.1.12 TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4 

15.1.13 HOP COUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4 

15.1.14 AGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5 

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

Memotec Inc.

Memotec Inc.

HDLC Protocol 

1 

Memotec Inc. 1-1


1.1 HDLC Features 

HDLC (High-level Data Link Control) is a protocol defined by the International Standards 

Organization. This protocol is a link-layer protocol having the following features: 

• Error detection using a 16-bit, CRC-CCITT, cyclic redundancy check error 

detection polynomial. 

• Single frame format containing an arbitrary number of bits. 

• Frame boundaries defined by a special bit pattern named FLAG (01111110). 

• Data transparency by means of bit stuffing. 

• Address field used to identify the station. 

• Control field used for error correction and line establishment. 

The HDLC message format is: 

01111110 ADDR CTRL DATA CRC 01111110 

The HDLC protocol is widely used, and many variations exist (ADCCP, transparent 

SDLC, X.25 level II, etc.). The variations differ only in their address and control field 

formats. 

1-2 Memotec Inc.

1.2 NetPerformer Support of HDLC 

HDLC Protocol 

The NetPerformer’s HDLC driver is a transparent driver developed to support all HDLClike 

protocols. It does not interpret or alter any bits in the ADDR, CTRL and DATA fields. 

This driver has the following characteristics: 

• The maximum frame size is 8200 bytes. 

• Frame length should be a multiple of 8 bits, with a minimum length of 16 bits. 

• Flags are stripped before transmission and regenerated at the remote end. 

• Two coding modes: normal (NRZ) or NRZI. 

• Two idle modes: FLAG or MARK. 

The HDLC driver is used when a WAN/user port is configured with the HDLC or X.25 

protocol. In the case of X.25, the HDLC driver: 

• Performs flag and CRC stripping 

• Integrally copies the X.25 into a Frame Relay frame (LAPB header and data), 

• In the case of FRF.3 Annex F encapsulation, adds a Frame Relay header (2 bytes 

of DLCI) and a 6-byte frame identifier to the frame, 

• In the case of FRF.3 Annex G encapsulation, encapsulated all frame types that 

are received on the HDLC port (INFO, UI, SUPERVISOR). 

NOTE: A PVC must be configured to transport the encapsulated X.25 data to the 

remote side. For details, refer to the WAN/Frame Relay module of this document 

series. Configuration of an X.25 data port is dealt with in the chapter 

“X.25 Protocol” on page 9-1. 

Memotec Inc. 1-3


1.3 Configuring an HDLC Connection 

The PORT or SLOT submenu of the SETUP console command includes all parameters 

required to configure an HDLC 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. 

An HDLC 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 an HDLC port: 

- Enter the menu sequence: SE � PORT. 

- Select the Port number. 

- Set the Protocol to HDLC. 

- 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 

an HDLC port: 

- Enter the menu sequence: SE � SLOT. 

- Select the Slot number. 

- On a digital interface card only: enter CHANNEL at the Item prompt. 

- Select the Channel number, e.g. 102, where the first digit indicates the slot 

and the last two digits indicate the channel. 

- Set the Protocol to HDLC. 

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

1.3.1 HDLC Port Configuration 

Console SNMP Text-based Config 

SE/PORT (serial port) 

SE/SLOT (digital channel 

or dual serial port) 

ifwan (category) [ifwan#] (heading) 

When you define a serial port as HDLC, the following port parameters are listed on the 

console: 

SE/PORT/#/ 

HDLC example SDM-9230>SE 

SETUP 

Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/ 

PHONE/ 

PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN, 

def:BRIDGE) ? PORT 

Port number (ETH1/ETH2/CSL/1,def:1) ? 

1-4 Memotec Inc.

HDLC Protocol 

PORT 1> Protocol (def:FR-USER) ? HDLC 

PORT 1> Interface...............................DCE-V35 

PORT 1> Clocking mode (def:INTERNAL) ? 

PORT 1> Port speed (bps) (1200-6144000,def:56000) ? 

PORT 1> Fallback speed (def:ENABLE) ? 

PORT 1> Idle (def:FLAG) ? 

PORT 1> Transmission start level (def:AUTO) ? 

PORT 1> CRC encoding (def:NRZ) ? 

PORT 1> Modem control signal (def:STATIC) ? 

PORT 1> Frame delay (ms) (def:0.0) ? 

PORT 1> Remote unit (def:) ? CHICAGO-9230 

PORT 1> Class (def:3) ? 

PORT 1> Remote port number (1-65534,def:1) ? 

NOTE: Port speed (bps) and Fallback speed parameters appear if Clocking mode is 

set to INTERNAL. This is the case for all dual serial ports. 

• For details on these parameters, refer to “SE/PORT Configuration Parameters” 

on page 12-1. 

1.3.2 HDLC Channel Configuration on Dual Serial Interface Card 

SE/SLOT/ 

Channel/HDLC 

example: on 

Dual Serial 

interface card 

When you define a serial port as HDLC on a Dual Serial interface card, the same 

parameters are listed on the console: 

SDM-9230>SE 

SETUP 


PHONE/ 


def:BRIDGE) ? SLOT 

SLOT> Slot number (1/2/3,def:2) ? 

SLOT> Channel Number (201-202/ALL,def:202) ? 201 

PORT 201> Protocol (def:HDLC) ? 

PORT 201> Interface.............................DCE-V35 

PORT 201> Clocking mode (def:EXTERNAL) ? INTERNAL 







PORT 202> Frame delay (ms) (def:0.0) ? 

PORT 202> Remote unit (def:) ? 



Memotec Inc. 1-5


Limitations on Legacy Dual Serial Interface Card 

Caution: The following limitations apply when the HDLC protocol is configured 

on a Dual Serial interface card on the SDM-9360, SDM-9380 or SDM-9585: 

• Clocking mode cannot be set to IPL 

• Fallback speed is not supported 

• Transmission start level is fixed at MAX 

• CRC encoding is fixed at NRZ 

• Modem control signal is fixed at STATIC 

• Frame delay (ms) is not supported. 

1.3.3 HDLC Channel Configuration on Digital Channel 

SE/SLOT/#/ 

CHANNEL/ 

HDLC 

example: on 

digital channel 

HDLC is available on a digital channel only when the Signaling mode on the LINK is set to 

NONE, TRSP-ORIG, TRSP-ANSW, CAS or ROB BIT. 

When you define a digital channel as HDLC, the following parameters are listed on the 

console: 

SDM-9230>SE 

SETUP 


PHONE/ 




Item (LINK/CHANNEL,def:CHANNEL) ? 


PORT 105> Protocol (def:OFF) ? HDLC 

PORT 105> Subchanneling (def:DISABLE) ? 

PORT 105> Timeslot (def:5) ? 

PORT 105> Number of consecutive timeslots (1-20,def:1) ? 

PORT 105> DS0 speed (bps) (def:64000) ? 





• Subchanneling, Timeslot, Number of consecutive timeslots and DS0 speed (bps) 

are described in the Digital Data module of this document series. 

• The other parameters operate as for a built-in serial port (see page 4 

NOTE: The Number of consecutive timeslots and DS0 speed (bps) parameters are not 

requested when you configure an HDLC channel for subchanneling. 

1-6 Memotec Inc.

HDLCOFR Protocol 

2 

Memotec Inc. 2-1


2.1 NetPerformer Support of HDLCOFR 

HDLC over Frame Relay (HDLCOFR), can be defined on a serial port or digital channel 

for data transport over Frame Relay. It is used for a multicast application of HDLC traffic: 

• An HDLC frame is received at the HDLCOFR port 

• The NetPerformer encapsulates the HDLC frame in a Frame Relay frame structure 

• The encapsulated frame is then sent out to a device capable of doing Frame Relay 

multicast transmissions 

• As a result, several remote stations can receive the same data. 

2.2 Configuring an HDLCOFR Connection 

SE/PORT/#/ 

HDLCOFR 

example 

To configure a port or channel for HDLC over Frame Relay, set the Protocol parameter to 

HDLCOFR. 

SDM-9230>SE 

SETUP 


PHONE/ 




PORT 1> Protocol (def:HDLC) ? HDLCOFR 





PORT 1> Tx/Rx mode (def:FULL) ? 



PORT 1> PVC number (1-300,def:1) ? 

• Protocol, Interface, Clocking mode, Port speed (bps), Fallback speed, CRC 

encoding and Idle are common to HDLC ports, and are detailed in “SE/PORT 

Configuration Parameters” on page 12-1. 

Caution: The Dual Serial interface card for the SDM-9360, SDM- 

9380 and SDM-9585 does not support Fallback. 

• The other parameters are specific to defining an HDLCOFR port. Refer to the 

section “HDLCOFR Port” on page 12-13. 

2-2 Memotec Inc.

PASSTHRU Protocol 

3 

Memotec Inc. 3-1


3.1 PASSTHRU Features 

The PASSTHRU protocol is used for transparent transfer of data traffic, voice, fax or 

TDM communications. When a serial port or digital channel is configured with the 

PASSTHRU protocol: 

• The NetPerformer creates a transparent channel from the available bandwidth on 

the composite links. 

• Traffic prioritization is handled by configuring a class of traffic. For details, refer 

to the Quality of Service (QoS) module of this document series. 

3.2 NetPerformer Support of PASSTHRU 

The PASSTHRU driver has the following characteristics: 

• Manages full-duplex, data stream, serial-by-bit information. 

• All bits received on the port or channel are transmitted transparently to the 

remote unit without alteration or processing. 

- All data received from the DTE device is split into small cells of 48 bytes 

each. 

- These cells are then sent over the composite links via the reserved channel(s). 

- At the remote end the cells are reassembled as the complete data stream, 

which is then transmitted to the destination DTE device. 

• The transmitter is enabled as soon as a minimum level of bytes has been received 

on the PASSTHRU channel (2 cells of 48 bytes). 

NOTE: This also reserves the PASSTHRU channel bandwidth. 

• The constant flow of data ensures the minimum level of bytes, since all cells are 

received over the reserved channel. 

3-2 Memotec Inc.

3.3 Configuring a PASSTHRU Connection 

3.3.1 PASSTHRU Channel on a Serial Port 

SE/PORT/#/ 

PASSTHRU 

example 

PASSTHRU Protocol 

When you define a serial port with the PASSTHRU protocol, the following port 


SDM-9230>SE 

SETUP 

Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/PHONE/ 




PORT 1> Protocol (def:P-SDLC) ? PASSTHRU 




PORT 1> Congestion flow control (def:AUTO) ? 


PORT 1> Transmission start level (def:3) ? 




PORT 1> Redundant link (def:NO) ? 

• Most of these parameters are common to the HDLC ports, and are detailed in 

“SE/PORT Configuration Parameters” on page 12-1 

• The Congestion flow control parameter is described on “Congestion flow control” 

on page 12-14. 

3.3.2 PASSTHRU Channel on a Digital Channel 

The PASSTHRU protocol is available on a digital channel for the SDM-9220 and SDM- 

9230 only. This PASSTHRU mode works in exactly the same way as the PASSTHRU 

mode available on WAN user ports. It is configured on two channels on opposite sides of 

the network. All the bits received at the local side are carried transparently across the 

network, and played back at the remote side. 

A digital channel set to the HDLC or PASSTHRU protocols can be divided into 

subchannels that can be 8, 16, 24, 32, 40, 48 or 56 Kb in size. This feature is also 

available only on the SDM-9220 and SDM-9230. 

• Subchanneling divides a timeslot into 8 sections of 8 Kb each 

• A 64-Kb Subchannel mask determines which sections of the timeslot are 

included in the subchannel 

• The size of each subchannel is therefore a multiple of 8 Kb. Refer to the detailed 

description of “Subchanneling” on page 12-11. 

NOTE: Subchanneling does not increase the number of channels that can be config- 

Memotec Inc. 3-3


SE/SLOT/ 

Channel/ 

PASSTHRU 

example 

ured on a slot, which remains 24 for a T1 connection, and 31 for an E1 connection. 

To configure subchannels on a NetPerformer HDLC or PASSTHRU channel: 

• Enter the menu sequence: SE � SLOT � CHANNEL 

• Select the Channel Number 

• Define the Protocol as either HDLC or PASSTHRU 

• Set the Subchanneling parameter to ENABLE (SNMP variable: IfwanSubChanneling) 

• Select the Timeslot number 

SDM-9230>SE 

SETUP 


PHONE/ 




Item (LINK/CHANNEL,def:CHANNEL) ? 

SLOT> Channel Number (101-124/ALL,def:105) ? 

PORT 105> Protocol (def:HDLC) ? PASSTHRU 

PORT 105> Subchanneling (def:DISABLE) ? 



PORT 105> DS0 speed (bps) (def:64000) ? ? 







If Subchanneling is enabled, the Number of consecutive timeslots and DSO speed (bps) 

parameters are replaced by the Subchannel mask parameter. All parameters listed after the 

Subchannel mask are the same as for a digital channel without subchanneling. 

PORT 105> Subchanneling (def:DISABLE) ? ENABLE 


PORT 105> Subchannel mask (def:00) ? 32 







• These parameters are the same as those for PASSTHRU on a serial port (see 

“PASSTHRU Channel on a Serial Port” on page 3-3). 

• Timeslot, Number of consecutive timeslots and DS0 speed (bps) are described in 

the Digital Data module of this document series. 

3-4 Memotec Inc.

PASSTHRUOFR Protocol 

4 

Memotec Inc. 4-1


4.1 Support of PASSTHRU over Frame Relay 

PASSTHRU over Frame Relay (PASSTHRUOFR), can be defined on a serial port or 

digital channel for data transport over Frame Relay multicast. 

• This protocol is used for multicast applications requiring transport of any type of 

incoming traffic to several remote sites via a Frame Relay network. 

• One application for PASSTHRUOFR is to carry radar information from one 

emitter to several receptors/monitors as illustrated in the figure below. 

NOTE: PASSTHRUOFR on a digital T1 or E1 channel is supported on the SDM- 

9220 and SDM-9230 only. 

Figure 4-1: PASSTHRU over Frame Relay Application 

On the NetPerformer, a serial port or digital PASSTHRUOFR channel serves as the 

Network Port of a TRANSP PVC, as shown in the example application above. The 

PASSTHRUOFR connection operates as follows: 

• A frame of any type is received at the PASSTHRUOFR port (radar traffic, in the 

example above) 

• The NetPerformer encapsulates the payload in a Frame Relay frame structure 

• The encapsulated frame is sent to another unit capable of handling Frame Relay 

multicast transmissions 

• Several remote stations can receive the frames, according to the specific Network 

DLCI. 

4-2 Memotec Inc.

4.1.1 Number of Digital PASSTHRUOFR Channels Supported 


A maximum of 72 T1 or 83 E1 digital channels can be configured with the 

PASSTHRUOFR protocol on a single SDM-9220 or SDM-9230 unit. To support this 

number of channels, you must ensure that there is a sufficient amount of bandwidth on the 

Frame Relay link (6 Mbps). 

Memotec Inc. 4-3


4.2 Configuring for PASSTHRU over Frame Relay 

To set up a PASSTHRUOFR application you need to configure: 

On the source unit (Unit 1 in Figure 4-1): 

• A connection to the Frame Relay network, using a FR-USER port 

• A PASSTHRUOFR port set to receive user traffic (from radar equipment, in this 

example) and packetize it in cells 

• A TRANSP PVC set to transport the PASSTHRUOFR traffic over the Frame 

Relay multicast PVC defined in the Frame Relay switch/network. 

On each destination unit (Units 2 and 3 in Figure 4-1) 

• A FR-USER port facing the Frame Relay network 

• A TRANSP PVC set to receive the PASSTHRUOFR traffic that is multicast by 

the Frame Relay network 

• A PASSTHRUOFR port set to transmit the traffic received from the remote radar 

equipment back to the attached user equipment (monitors, in this example). 

The required commands for complete application configuration are shown in Figure 4-2. 

# 

FR-USER FR-NET 

Port (PO) 

PASSTHRUOFR 

Setup (SE) 

Unit ID> 

(main prompt) 

Slot (SL) 

Link Channel # 

NONE 

FR-USER FR-NET 

PASSTHRUOFR 

Figure 4-2: PASSTHRUOFR Configuration Commands in the CLI Tree 

PVC (PV) 

TRANSP PVCR 

NOTE: For details on configuring the FR-USER and FR-NET ports, as well as the 

TRANSP and PVCR PVCs, consult the WAN/Frame Relay module of this 

document series. 

4-4 Memotec Inc.


4.3 Configuring a PASSTHRUOFR Connection 

4.3.1 Built-in Serial Port 

SE/PORT/#/ 

PASSTHRUOF 

R example 

To configure a port or channel for PASSTHRU over Frame Relay, set the Protocol 

parameter to PASSTHRUOFR. 

PASSTHRUOFR can be defined on a serial port (either built-in or on the Dual Serial 

interface card) or a digital channel (T1 or E1). 

To configure a built-in serial port as a PASSTHRUOFR port: 

1. At the NetPerformer command line prompt, enter the menu sequence: SE � PORT 

2. Select the Port number 

3. Set the Protocol to PASSTHRUOFR 

4. Set the Port speed (bps) 

5. Set the PVC number to the number of a PVC in TRANSP mode. 

6. Change the other port parameters from their default values, if desired. 

9380A>SE 

SETUP 




Port number (ETH/CSL/1/2/3,def:1) ? 2 

PORT 2> Protocol (def:OFF) ? PASSTHRUOFR 




PORT 2> Dynamic clocking (def:YES) ? 



PORT 2> Reception frame size (3-12,def:3) ? 

PORT 2> PVC number (1-300,def:1) 

• Protocol, Interface, Clocking mode, Port speed (bps), Transmission start level 

and Reception frame size are common to HDLC ports, and are detailed in “SE/ 

PORT Configuration Parameters” on page 12-1. 

• Tx/Rx mode and PVC number are also used on an HDLCOFR port. For details, 

refer to the section “HDLCOFR Port” on page 12-13. 

• The Dynamic clocking parameter is specific to a PASSTHRUOFR port. Refer to 

the section “PASSTHRUOFR Port” on page 12-14 for details. 

Memotec Inc. 4-5


4.3.2 Serial Port on Dual Serial Interface Card 

SE/SLOT/ 

Channel/ 

PASSTHRUOF 

R example 

4.3.3 Digital Channel 

To configure a serial port on the Dual Serial interface card as a PASSTHRUOFR 

port: 

1. At the NetPerformer command line prompt, enter the menu sequence: SE � SLOT 

2. Select the Slot number 

3. Select the Channel number 


5. Set the Port speed (bps) 


7. Change the other port parameters from their default values, if desired. 

SDM-9230>SE 

SETUP 


PHONE/ 




SLOT> Channel Number (101-102,def:101) ? 




PORT 101> DS0 speed (bps).......................64000 

PORT 101> Dynamic clocking (def:YES) ? 




PORT 101> PVC number (1-300,def:1) ? 2 

NOTE: These parameters are the same as those for a built-in serial port. 

PASSTHRUOFR on a digital T1 or E1 channel is supported on the SDM-9220 and 

SDM-9230 only. The physical link (SE/SLOT/LINK) can have the Signaling mode 

parameter set to any value. 

To configure a T1/E1 channel as a PASSTHRUOFR port: 

1. At the NetPerformer command line prompt, enter the menu sequence: SE � SLOT 

2. Select the Slot number 

3. Enter CHANNEL at the Item prompt 

4. Select the Channel number, e.g. 102, where the first digit indicates the slot and the 

last two digits indicate the channel 

4-6 Memotec Inc.

SE/SLOT/#/ 

CHANNEL/ 

PASSTHRUOF 

R example 



6. Select a Timeslot and define the Number of consecutive timeslots 


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

9230-2>SE 

SETUP 


PHONE/ 



SLOT> Slot number (1/2/3,def:1) ? 2 

Item (LINK/CHANNEL,def:LINK) ? CHANNEL 






PORT 201> Transmission start level (def:3) ? 12 


PORT 201> PVC number (1-300,def:1) ? 2 

NOTE: Dynamic clocking and Tx/Rx mode are not required on a digital channel. 

Memotec Inc. 4-7


4.4 Fine Tuning the Connection 

4.4.1 Serial PASSTHRUOFR Port 

• Set the Dynamic clocking parameter to YES to allow the NetPerformer to adjust 

the clock it provides to the attached equipment. This may be required to compensate 

for a difference between the clocks at different sites. 

• The Tx/Rx mode parameter determines the direction of data transmissions, and 

can be set to: 

- FULL: The port can both transmit and receive data 

- TX: The port can transmit only 

- RX: The port can receive only 

• The Reception frame size determines the length of each frame sent over Frame 

Relay. Use this parameter to adjust the latency (or delay) introduced by the system: 

- Increase the value for greater latency 

- Decrease the value for less latency. 

NOTE: When the port is in TX mode, this parameter is not used. 

4.4.2 Digital PASSTHRUOFR Channel 

If performance suffers from a high number of errors such as bad frames and underruns, try 

the following adjustments: 

• Raise the Transmission start level on the PASSTHRUOFR port to a higher level 

(maximum 48) 

• Adjust latency using the Reception frame size parameter, in the same way as for a 

serial port 

• Reduce the FRCHECKTIMER extended port parameter from 20 ms to 10 ms 

• Reduce the total number of digital channels operating in PASSTHRUOFR protocol. 

Refer to chapter “Monitoring Data Port Functions” on page 11-1 for display commands 

that you can use to monitor the performance of a PASSTHRUOFR connection. 

4-8 Memotec Inc.

Asynchronous Protocols 

5 

Memotec Inc. 5-1


5.1 NetPerformer Support of Asynchronous Data Traffic 

The NetPerformer supports two asynchronous communication modes on a serial port: 

• Reliable mode (R-ASYNC) 

• Transparent mode (T-ASYNC). 

The ASYNC (Asynchronous communications) driver has the following characteristics: 

• Configurable character format of 7 or 8 bits. 

• Configurable parity bit (NONE, EVEN, ODD, SPACE MARK, IGNORE, 

2STOP). 

• Two types of flow control (XON-XOFF, HARDWARE). 

• Error detection using the parity bit. 

Characters received are forwarded to the compressor in cells of at least 1 byte and at most 

48 bytes. At the remote site, the composite link information is decompressed and passed to 

the transmitter which then transmits the data as it is received. 

5.2 R-ASYNC Mode 

In Reliable mode (R-ASYNC), cells are forwarded to a proprietary level 2 protocol before 

being sent over the composite link. This protocol ensures retransmission in case of errors 

on the link. The NetPerformer provides two flow control methods when the port is 

configured Reliable mode: XON-XOFF and HARDWARE (CTS/DSR). This guarantees 

that the buffers will not overflow and loose data. 

5.3 T-ASYNC Mode 

In Transparent mode (T-ASYNC), all characters received on a user port are transmitted on 

the composite link without any interpretation. If an error occurs on the composite link 

while characters are being transmitted, these characters will be lost. 

The Transparent mode supports link-level asynchronous protocols. These protocols, like 

DDCMP/ASYNC, XMODEM or POLL-SELECT/ASYNC, automatically retransmit 

frames in case of errors or timeouts. If the NetPerformer port is configured in Reliable 

mode for these protocols, multiple retransmissions could occur if both the NetPerformer 

and the connected device start to retransmit data. 

5-2 Memotec Inc.


5.4 Configuring an Asynchronous Data Connection 

5.4.1 T-ASYNC Connection 

SE/PORT/#/T- 

ASYNC 

example 


required to configure a T-ASYNC port. 









A T-ASYNC port can be configured on a built-in serial port or a serial port on a Dual 

Serial Port interface card. 

• To configure a built-in serial port on the base unit as a T-ASYNC port: 



- Set the Protocol to T-ASYNC. 


• To configure a serial port on the Dual Serial interface card as a T-ASYNC port: 





- Set the Protocol to T-ASYNC. 

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

SDM-9230>SE 

SETUP 


PHONE/ 




PORT 1> Protocol (def:S-SDLC) ? T-ASYNC 


PORT 1> Clocking mode (def:ASYNC) ? 


PORT 1> Format (def:8-NONE) ? 


Memotec Inc. 5-3


SE/SLOT/ 

Channel/T- 

ASYNC 

example 

5.4.2 R-ASYNC Connection 




• Protocol, Interface, Clocking mode, Port speed (bps), Modem control signal, 

Remote unit, Class and Remote port number are common to other legacy data 

port protocols. For details, go to “SE/PORT Configuration Parameters” on 

page 12-1. 

• The Format parameter is unique to the asynchronous protocols, and is detailed in 

the section “T-ASYNC Port” on page 12-15. 

SDM-9230>SE 

SETUP 


PHONE/ 





PORT 202> Protocol (def:R-ASYNC) ? T-ASYNC 

PORT 202> Interface.............................DTE-V35 








• These are the same parameters as for T-ASYNC on a built-in serial port. 


required to configure an R-ASYNC port. 









An R-ASYNC port can be configured on a built-in serial port or a serial port on a Dual 

Serial Port interface card. 

• To configure a built-in serial port on the base unit as an R-ASYNC port: 

5-4 Memotec Inc.

SE/PORT/#/R- 

ASYNC 

example 

SE/SLOT/ 

Channel/R- 

ASYNC 

example 




- Set the Protocol to R-ASYNC. 


• To configure a serial port on the Dual Serial interface card as an R-ASYNC port: 





- Set the Protocol to R-ASYNC. 


SDM-9230>SE 

SETUP 


PHONE/ 




PORT 1> Protocol (def:PVCR) ? R-ASYNC 





PORT 1> Reception flow control (def:NONE) ? 

PORT 1> Transmission flow control (def:NONE) ? 

PORT 1> Transmit holding time (s) (0-2000,def:0) ? 




• Protocol, Interface, Clocking mode, Port speed (bps), Remote unit, Class and 

Remote port number are common to other legacy data port protocols. For details, 

go to “SE/PORT Configuration Parameters” on page 12-1. 

• Format is common to the T-ASYNC protocol, and is detailed in “T-ASYNC 

Port” on page 12-15. 

• Reception flow control, Transmission flow control and Transmit holding time (s) 

are unique to the R-ASYNC protocol. For details, turn to “R-ASYNC Port” on 

page 12-16. 

SDM-9230>SE 

SETUP 


PHONE/ 

Memotec Inc. 5-5






PORT 202> Protocol (def:PPP) ? R-ASYNC 





PORT 202> Reception flow control (def:NONE) ? 

PORT 202> Transmission flow control (def:NONE) ? 

PORT 202> Transmit holding time (s) (0-2000,def:0) ? 




• These are the same parameters as for R-ASYNC on a built-in serial port. 

5-6 Memotec Inc.

SNA/SDLC Support 

6 

Memotec Inc. 6-1


6.1 NetPerformer Support of SNA/SDLC 

6.1.1 SDLC Driver 

6.1.2 SNA/SDLC Ports 

6.1.3 PUs 

SDLC (Synchronous Data Link Control) is the link-layer protocol used in the SNA 

architecture for low to medium-speed links. The SDLC discipline manages synchronous, 

code-transparent, serial-by-bit information transfer between nodes that are joined by data 

links. 

The NetPerformer includes a full-featured SDLC driver: 

• Comprehensive detection and recovery procedures for transmission errors. 

• Local polling capabilities, where the NetPerformer generates and responds to 

polls on behalf of the SDLC devices, and filters out administrative information 

such as unnumbered and supervisory frames. 

• The Group Poll feature offered in the IBM 3745 Front End Telecommunication 

Processor. 

• Support of point-to-point or multipoint, switched or non-switched port connections. 

• Support of up to 64 SDLC controllers (PUs). 

SNA/SDLC local polling enhances NetPerformer performance in the SDLC environment, 

particularly for bulk data transfers between two hosts with peer-to-peer SNA PU type 4 

definitions. The polling cycle is dramatically shortened by rapid spoofing of the SDLC 

protocol, which increases the polling frequency of the FEP and improves the response 

time. This permits high-speed LAN-to-LAN and FEP-to-FEP connections. 

An SNA/SDLC port on the NetPerformer is any serial user port configured with an SDLC 

protocol. Each SNA/SDLC port must be defined as either: 

• A primary port (P-SDLC protocol), which connects to a cluster controller (PU), 

or 

• A secondary port (S-SDLC protocol), which connects to a front-end processor or 

IBM mainframe. 

The SNA/SDLC ports take input data from the PUs and send it over the composite link. 

• Traffic priority is determined by the weight class to which the PU belongs; configure 

it using the Class parameter. 

• You can also define a filter to assign all SNA data to a particular class. 

The NetPerformer is designed to handle up to 64 PUs (or controllers), which are 

configured individually. Each active controller is logically attached to two interfaces, each 

of which may be: 

6-2 Memotec Inc.


• SNA/SDLC port (either primary or secondary), 

• LAN interface, 

• WAN port, 

• Boundary Node Network (BNN) connection (Routed SNA Over Frame Relay), 

• Boundary Access Network (BAN) connection (Bridged SNA Over Frame Relay) 

The PU operating mode is determined from these two logical connections. 

6.1.4 Session Timeout Control 

NOTE: For the SDLC-SDLC mode, the logical connections require one primary and 

one secondary SNA/SDLC port. 

SNA, like other delay-sensitive protocols, operates as though a dedicated set of resources 

exists between any pair of communications devices in the network. Without the 

NetPerformer in a LAN/WAN internetwork, SNA transmissions may not be completed 

before the session timer expires, due to competition with traffic from the LANs. In 

addition to severe network delays, users may be faced with session timeouts. 

Protocol spoofing reduces the risk of session timeouts. In addition, the protocol 

prioritization capability of the NetPerformer guarantees session safety even in high traffic 

conditions. Two sets of configurable parameters can be used to prioritize SNA data (or any 

other data type that must be prioritized): 

• FILTERS, using the Setup Filters menu 

• CLASSES, using the Setup Classes menu. 

For details, refer to the Quality of Service (QoS) module of this document series. 

6.1.5 Connection Types 

An SDLC port connection may have a point-to-point or multipoint configuration. In 

addition, point-to-point connections can be switched or non-switched. Data may be sent 

simultaneously in both directions, called two-way simultaneous transmission. 

Alternatively, data may be sent in one direction at a time, which is called two-way 

alternate transmission. 

Multipoint Connection 

Several PUs can be connected to a single user port on the NetPerformer. Simply attach a 

line-sharing device or connect to a multipoint line. The NetPerformer automatically 

establishes and maintains a link session with every device on the drop. 

Memotec Inc. 6-3


Concentration 

6.1.6 LLC Conversion 

The NetPerformer combines multiplexing and concentration techniques. It can support up 

to 64 SDLC devices, each using a dedicated channel of the multiplexer function. At the 

remote end, two or more ports can be configured to handle data coming from a single port 

at the local end. 

Any SDLC device can be attached to any local user port. You do not need to configure 

corresponding ports at the local and remote sites, for example, local port 3 with remote 

port 3, to allow devices at opposite ends of the network to communicate with each other. 

The NetPerformer includes an SDLC-LLC conversion function, through which SNA 

traffic is converted from one format to another (SDLC to/from LLC). Conversion can be 

performed locally on the NetPerformer, or remotely by using an intermediate format 

(LINKS). Both the SDLC and LLC drivers are used to convert SDLC traffic into LLC 

packets. 

LLC Driver 

6.1.7 SNA Over RFC-1490 

The NetPerformer LLC driver conforms to the IEEE 802.2 standard, and supports the 

Automatic Window Extension feature. When SDLC traffic is converted into LLC packets, 

the NetPerformer encapsulates the LLC frames before sending them over the 

internetwork. The network delay can be configured to support slow networks or networks 

with long delays, for example, satellite transmissions. 

NOTE: The LLC driver is available only on a NetPerformer equipped with an Ethernet 

or Token-Ring expansion card. 

The NetPerformer supports SNA over RFC-1490 through BNN (Routed SNA Over Frame 

Relay) and BAN (Bridged SNA Over Frame Relay) connections. The following PU 

operating modes use these connections: SDLC-BAN, SDLC-BNN, LLC-BAN, LLC- 

BNN, BAN-LINKS, BNN-LINKS. 

BNN Connection 

Boundary Network Node (BNN) support is sometimes called “RFC-1490 Support”, since 

the RFC-1490 document defines the Layer 2 protocol identifier (PID) for this format. 

BNN is also referred to as Routed SNA Over Frame Relay. 

With the BNN format, neither the Source MAC address nor the Destination MAC address 

are carried in the frame. To identify the source and destination devices, the NetPerformer 

does “SAP mapping” based on the Source and Destination SAPs. The NetPerformer 

translates each MAC/SAP pair it receives from the network into a unique SAP 

6-4 Memotec Inc.


representing the specified session partner. 

The advantages of a BNN network solution are: 

• Reduced overhead for Frame Relay transmissions. The BNN format has the 

fewest number of bits per packet (only 14 bytes). 

• Ideal for SDLC conversion, since each SNA/SDLC has a unique SAP value. 

BAN Connection 

6.1.8 Network Topologies 

The Boundary Access Node (BAN) frame format is also based on RFC-1490. Contrary to 

the BNN format, BAN carries the actual Source and Destination MAC addresses across 

the network. BAN support is also referred to as Bridged SNA Over Frame Relay. 

The BAN format uses 802.5 (Token-Ring) between the NetPerformer and other routers. 

However, end devices can be attached to Ethernet networks using standard Ethernet 

formats. 

NOTE: The Integrated Data/Voice Branch unit must be equipped with a LAN port 

(optional Ethernet expansion card) to support BAN mode. Otherwise, the 

Destination MAC address cannot be determined. 

The advantages of a BAN network solution are: 

• Network flexibility. BAN devices are defined to the host in the same way as 

LAN-attached devices, and these definitions are easily changed for fast migration. 

• PVCs need not be predefined. The BAN format allows explorers to search for a 

session partner over the network. 

• Simplified problem determination, since the MAC addresses are carried with the 

packet. 

The BAN and BNN frame formats are found in IBM (SNA) networks based on Frame 

Relay. There are two types of SNA solutions for Frame Relay: single switch conversion 

and centralized router operation (see below). Both solutions provide the following 

services for attached SNA devices: 

• Local termination, which avoids SNA timeouts. 

• RIF caching, which allows inbound traffic to be correctly routed by saving the 

Source Route Bridge RIF field. 

Single Switch Conversion 

For single switch conversion, a single NetPerformer and the central site processor (or 

gateway) are directly connected to the Frame Relay network. Each remote site 

Memotec Inc. 6-5


communicates directly to an IBM processor or channel-attached gateway across the Frame 

Relay network. See Figure 6-1 

To support Frame Relay, IBM provides both BNN and BAN formats at the FEP. These 

two types of Frame Relay support are collectively referred to as “Native SNA Over Frame 

Relay”. 

IBM 3745 

Single switch conversion permits: 

• Independent access to SNA services by each connection. 

• Local termination for Ethernet, SDLC and Frame Relay links. 

• Same or mixed media interfaces. 

With single switch conversion, an Ethernet or SDLC frame can be converted to: 

• BNN format for communication to the IBM FEP (Routed SNA Over Frame 

Relay). 

• BAN format for Bridged SNA Over Frame Relay. 

Centralized Router Operation 

For centralized router operation, a NetPerformer at each remote site communicates with a 

NetPerformer at the central site, which routes all traffic to the appropriate destination. The 

IBM FEP typically connects to the central site NetPerformer across a LAN, although an 

SDLC link or Frame Relay connection can also be used. See Figure 6-2. 

IBM 3745/3172 

Frame Relay 

Figure 6-1: Single Switch Conversion 

Frame Relay 

SDLC 

Figure 6-2: Centralized Router Operation 

This topology provides both BNN and BAN support. For BNN, adjacent NetPerformers 

(or other routers) use Routed SNA Over Frame Relay, and an intermediate NetPerformer 

6-6 Memotec Inc. 

SDLC 

LLC 

LLC


routes SNA to the other location. For BAN support, adjacent routers use Bridged SNA 

Over Frame Relay, and the central site NetPerformer offloads the FEP. 

Centralized router operation permits: 

• Sharing a single PVC for all protocols. This results in reduced costs if a public 

Frame Relay network is used. 

• Efficient traffic management. The central NetPerformer directs all traffic 

received from the WAN, and only those packets which are destined for the FEP 

are actually forwarded to it. This in turn reduces the burden on the remote site 

NetPerformers. 

Memotec Inc. 6-7


6.2 Configuring an SNA/SDLC Port 

The Setup Port menu lets you configure all parameters that affect the operation of the 

WAN/user ports, including SDLC ports. For the console, enter SE followed by PORT. For 

SNMP, select the ifwan category, which includes all variables affecting the WAN/user 

ports. For text-based configuration the [ifwan#] heading is used, where # represents the 

number of the port or channel. 

6.2.1 Configuring a Primary SDLC Port 

SE/PORT/#/P- 

SDLC example 

SE/SLOT/ 

Channel/P- 

SDLC example 


SE/PORT ifwan (category) [ifwan#] (heading) 

A primary SDLC port (P-SDLC) connects to one or more PUs. When you define a data 

port as P-SDLC, the following port parameters are listed on the console: 

SDM-9230>SE 

SETUP 


PHONE/ 




PORT 1> Protocol (def:HDLCOFR) ? P-SDLC 








PORT 1> SDLC duplex mode (def:HALF) ? 

PORT 1> Group poll (def:NO) ? 

PORT 1> Group address (def:AE) ? 

PORT 1> Poll delay (ms) (0-1000,def:10) ? 

• Protocol, Interface, Clocking mode, Port speed (bps), Fallback speed, CRC 

encoding, Transmission start level and Idle are common to other legacy data 

ports, and are detailed in “SE/PORT Configuration Parameters” on page 12-1 

• The SDLC duplex mode, Group poll, Group address and Poll delay (ms) parameters 

set specific SNA/SDLC characteristics. For details, turn to “P-SDLC Port” 

on page 12-17. 

When you set a digital channel to P-SDLC, the following parameters are listed on the 

console: 

SDM-9230>SE 

SETUP 


6-8 Memotec Inc.


PHONE/ 





PORT 202> Protocol (def:HDLC) ? P-SDLC 


PORT 202> Clocking mode (def:EXTERNAL) ? 








With the exception of Clocking mode, which has a default value of EXTERNAL instead of 

INTERNAL, all the parameter values and defaults listed here are covered in the “SE/ 

PORT/#/P-SDLC example” on page 6-8. 

Limitations on Legacy Dual Serial Interface Card 

Caution: The following limitations apply when the P-SDLC or S-SDLC protocol 

is configured on a Dual Serial interface card on the SDM-9360, SDM-9380 or 

SDM-9585: 

• Clocking mode cannot be set to IPL 

• Fallback speed is not supported 

• CRC encoding is fixed at NRZ 

• Transmission start level is fixed at MAX. 

6.2.2 Configuring a Secondary SDLC Port 

SE/PORT/#/S- 

SDLC example 

A secondary SDLC port (S-SDLC) connects to a front-end processor or a mainframe. 

When you define a data port as S-SDLC, the following port parameters are listed on the 

console: 

SDM-9230>SE 

SETUP 


PHONE/ 




PORT 1> Protocol (def:R-ASYNC) ? S-SDLC 







Memotec Inc. 6-9


SE/SLOT/ 

Channel/S- 

SDLC example 






• All of these parameters are common to P-SDLC configuration on a built-in serial 

port. 

SDM-9230>SE 

SETUP 


PHONE/ 





PORT 201> Protocol (def:PVCR) ? S-SDLC 











PORT 201> Poll delay (ms) (0-1000,def:10) 

• All of these parameters are common to P-SDLC configuration on a dual serial 

port. 

6-10 Memotec Inc.

6.3 Configuring a PU 


The Setup PU menu lets you configure all operation parameters for the PUs. For the 

console, enter SE followed by PU. For SNMP, the pu category includes all variables 

affecting PU configuration. For text-based configuration the [pu#] heading is used, where 

# represents the number of the PU. 

6.3.1 Configuring a PU in SDLC-SDLC Mode 

SE/PU/SDLC- 

SDLC example 

Configure a PU in SDLC-SDLC mode as follows: 

SDM-9230>SE 

SETUP 


PHONE/ 


def:BRIDGE) ? PU 

PU number (1-64,def:1) ? 2 

PU 2> Operating mode (def:OFF) ? SDLC-SDLC 

PU 2> Controller active (def:NO) ? 

PU 2> Delay before connection (1-1000,def:60) ? 

PU 2> SDLC primary port (def:1) ? 

PU 2> SDLC primary address (def:02) ? 

PU 2> SDLC secondary port (def:1) ? 

PU 2> SDLC secondary address (def:02) ? 

PU 2> SDLC retransmission timeout (ms) (100-30000,def:3000) ? 

PU 2> SDLC number of retransmission retries (1-1000,def:10) ? 

PU 2> SDLC transmission window size (1-7,def:7) ? 

PU 2> XID support (def:YES) ? 

Details on these parameters are provided in “SE/PU Configuration Parameters” on 

page 13-1. 

6.3.2 Configuring a PU in SDLC-LINKS Mode 

SE/PU/SDLC- 

LINKS 

example 


SE/PU pu (category) [pu#] (heading) 

Configure a PU in SDLC-LINKS mode as follows: 

SDM-9230>SE 

SETUP 


PHONE/ 




PU 4> Operating mode (def:OFF) ? SDLC-LINKS 


Memotec Inc. 6-11



PU 4> SDLC port (def:1) ? 

PU 4> SDLC address (def:04) ? 




PU 4> SDLC frame size (def:512) ? 

PU 4> Remote unit (def:) ? CHICAGO-9230 

PU 4> Class (def:2) ? 

PU 4> Remote PU number (1-64,def:4) ? 

PU 4> XID support (def:YES) ? 

• Operating mode, Controller active, Delay before connection, SDLC retransmission 

timeout (ms), SDLC number of retransmission retries, SDLC transmission 

window size and XID support are also used for SDLC-SDLC mode, and are 

detailed in “SDLC-SDLC Mode” on page 13-2. 

• Details on the other parameters can be found in “SDLC-LINKS Mode” on 

page 13-7. 

6.3.3 Configuring a PU in SDLC-LLC Mode 

SE/PU/SDLC- 

LLC example 

NOTE: AN LLC connection requires an Ethernet port. 

Configure a PU in SDLC-LLC mode as follows: 

SDM-9230>SE 

SETUP 


PHONE/ 



PU number (1-64,def:1) ? 

PU 1> Operating mode (def:OFF) ? SDLC-LLC 









PU 1> LLC lan port (def:ETH1) ? 

PU 1> LLC destination address (def:000000000000) ? 

PU 1> LLC source SAP (def:04) ? 

PU 1> LLC destination SAP (def:04) ? 

PU 1> LLC retransmission timeout (ms) (1000-30000,def:3000) ? 

PU 1> LLC maximum successive retries (1-1000,def:10) ? 

PU 1> LLC transmission window size (1-31,def:7) ? 

PU 1> LLC dynamic window (1-1000,def:10) ? 

6-12 Memotec Inc.

PU 1> LLC frame size (def:512) ? 

PU 1> XID support (def:AUTO) ? 




window size and SDLC frame size are described in “SDLC-SDLC Mode” on 

page 13-2. 

• SDLC port and SDLC address are described in “SDLC-LINKS Mode” on 

page 13-7. 

• The other parameters are required to configure the LLC side of the connection. 

For details, refer to “SDLC-LLC Mode” on page 13-9. 

6.3.4 Configuring a PU in SDLC-BAN Mode 

SE/PU/SDLC- 

BAN example 

Configure a PU in SDLC-BAN mode as follows: 

SDM-9230>SE 

SETUP 


PHONE/ 




PU 8> Operating mode (def:OFF) ? SDLC-BAN 









PU 8> BAN destination address (def:000000000000) ? 

PU 8> BAN/BNN source SAP (def:04) ? 

PU 8> BAN/BNN destination SAP (def:04) ? 

PU 8> BAN/BNN retransmission timeout (ms) (1000-30000,def:3000) ? 

PU 8> BAN/BNN maximum successive retries (1-1000,def:10) ? 

PU 8> BAN/BNN transmission window size (1-31,def:7) ? 

PU 8> BAN/BNN dynamic window (1-1000,def:10) ? 

PU 8> BAN/BNN frame size (def:512) ? 

PU 8> BAN routing (def:SOURCE) ? 





page 13-2. 


page 13-7. 

Memotec Inc. 6-13


• XID support is described in “SDLC-LLC Mode” on page 13-9. 

• The other parameters define the BAN side of the connection. For details, refer to 

“SDLC-BAN Mode” on page 13-15. 

6.3.5 Configuring a PU in SDLC-BNN Mode 

Configure a PU in SDLC-BNN mode as follows: 

SE/PU/SDLC- 

BNN example SDM-9230>SE 

SETUP 


PHONE/ 




PU 9> Operating mode (def:OFF) ? SDLC-BNN 









PU 9> BNN PVC number (1-300,def:1) ? 

PU 9> BNN FID type (def:FID2) ? 

PU 9> BAN/BNN source SAP (def:04) ? 

PU 9> BAN/BNN destination SAP (def:04) ? 

PU 9> BAN/BNN retransmission timeout (ms) (1000-30000,def:3000) ? 

PU 9> BAN/BNN maximum successive retries (1-1000,def:10) ? 

PU 9> BAN/BNN transmission window size (1-31,def:7) ? 

PU 9> BAN/BNN dynamic window (1-1000,def:10) ? 

PU 9> BAN/BNN frame size (def:512) ? 





page 13-2. 


page 13-7. 

• XID support is described in “SDLC-LLC Mode” on page 13-9. 

• BAN/BNN source SAP, BAN/BNN destination SAP, BAN/BNN retransmission 

timeout (ms), BAN/BNN maximum successive retries, BAN/BNN transmission 

window size, BAN/BNN dynamic window and BAN/BNN frame size are described 

in “SDLC-BAN Mode” on page 13-15. 

• The other parameters are unique to PUs with a BNN logical connection. For 

details, refer to “SDLC-BNN Mode” on page 13-19. 

6-14 Memotec Inc.

6.3.6 Configuring a Non-SDLC PU Connection 


For the following PU modes, neither side of the logical connection uses SDLC: 

• LLC-LINKS 

• LLC-BAN 

• LLC-BNN 

• BAN-LINKS 

• BNN-LINKS 

When neither side of the PU logical connection is SDLC, you must define which side acts 

as a primary unit (facing the controller) and which acts as a secondary unit (facing the 

host): Do this using the Role parameter (see page 20). 

All other parameters governing configuration of the non-SDLC modes are common to 

other PU types: 

• LLC-LINKS Mode: Controller Active, Delay Before Connection, LLC Role, 

LLC Destination Address, LLC Routing, LLC Source SAP, LLC Destination SAP, 

LLC Retransmission Timeout, LLC Retries, LLC Window, LLC Dynamic Window, 

LLC Frame Size, Remote Unit, Class, Remote PU, XID Support, XID ID, XID 

Format, XID PU Type 

• LLC-BAN Mode: Controller Active, Delay Before Connection, LLC Role, LLC 

Destination Address, LLC Routing, LLC Source SAP, LLC Destination SAP, LLC 

Retransmission Timeout, LLC Retries, LLC Window, LLC Dynamic Window, LLC 

Frame Size, BAN Destination Address, BAN/BNN Source SAP, BAN/BNN Destination 

SAP, BAN/BNN Retransmission Timeout, BAN/BNN Retries, BAN/BNN 

Window, BAN/BNN Dynamic Window, BAN/BNN Frame Size, BAN Routing, XID 

Support, XID ID, XID Format, XID PU Type 

• LLC-BNN Mode: Controller Active, Delay Before Connection, LLC Role, LLC 

Destination Address, LLC Routing, LLC Source SAP, LLC Destination SAP, LLC 

Retransmission Timeout, LLC Retries, LLC Window, LLC Dynamic Window, LLC 

Frame Size, BNN PVC Number, BNN FID Type, BAN/BNN Source SAP, BAN/ 

BNN Destination SAP, BAN/BNN Retransmission Timeout, BAN/BNN Retries, 

BAN/BNN Window, BAN/BNN Dynamic Window, BAN/BNN Frame Size, XID 

Support, XID ID, XID Format XID PU Type 

• BAN-LINKS Mode: Controller Active, Delay Before Connection, BAN/BNN 

Role, BAN Destination Address, BAN/BNN Source SAP, BAN/BNN Destination 

SAP, BAN/BNN Retransmission Timeout, BAN/BNN Retries, BAN/BNN Window, 

BAN/BNN Dynamic Window, BAN/BNN Frame Size, BAN Routing, Remote Unit, 

Class, Remote PU, XID Support, XID ID, XID Format XID PU Type 

• BNN-LINKS Mode: Controller Active, Delay Before Connection, BAN/BNN 

Role, BNN PVC Number, BNN FID Type, BAN/BNN Source SAP, BAN/BNN Destination 

SAP, BAN/BNN Retransmission Timeout, BAN/BNN Retries, BAN/BNN 

Window, BAN/BNN Dynamic Window, BAN/BNN Frame Size, Remote Unit, 

Class, Remote PU, XID Support, XID ID, XID Format XID PU Type 

Memotec Inc. 6-15


6-16 Memotec Inc.

BSC Protocol 

7 

Memotec Inc. 7-1


7.1 BSC Features 

The BSC (Binary Synchronous Communications) protocol is a synchronous characteroriented 

protocol used by IBM. It has the following characteristics: 

• Error detection using a 16-bit, CRC-16, cyclic redundancy check error detection 

polynomial. 

• Transmission method must be synchronous. 

• Data-link control characters are required with each message to delimit the various 

portions of the message and control its transmission. 

• Accommodates three specific transmission code sets: EBCDIC (Extended Binary 

Coded Decimal Interchange Code), USASCII (United States of America Standard 

Code) and 6-bit Transcode 

NOTE: The NetPerformer currently supports only the EBCDIC transmission code. 

• Accommodates a transparent mode, which further increases flexibility since all 

possible bit configurations are treated as “data only”. 

• Flow control using the fallback technique. 

7.2 NetPerformer Support of BSC 

7.2.1 Reception 

BSC is supported on the NetPerformer when a serial port is configured with the BSC 

protocol. 

The NetPerformer’s BSC driver supports all frame formats used by IBM with a DATA 

field of up to 2047 bytes. The BSC driver works in the following way: 

• Strips all characters until synchronization is achieved. 

• Strips all sync characters. 

• Validates messages and rejects invalid frames. 

7.2.2 Transmission 

• Transmits 4 sync bytes, then 

• Transmits the complete frame. 

Except for the SYNC field, the receiver does not alter any byte or bit before forwarding it 

to the compressor and then to the composite link. DATA is forwarded to the compressor in 

48-byte cells as they are received. 

7-2 Memotec Inc.

BSC Protocol 

At the remote end, the composite link information is decompressed and passed to the 

transmitter which then transmits the data. The transmitter can be started on the first cell if 

fallback is enabled, or on the complete frame if fallback is disabled. 

7.3 Configuring a BSC Connection 


required to configure a BSC port. 




A BSC port can be configured on a built-in serial port or a serial port on a Dual Serial Port 

interface card. 

• To configure a built-in serial port on the base unit as a BSC port: 



- Set the Protocol to BSC. 


• To configure a serial port on the Dual Serial interface card as a BSC port: 





- Set the Protocol to BSC. 


7.3.1 BSC on a Built-in Serial Port 

SE/PORT/#/ 

BSC example 



SE/SLOT (dual serial port) 


When you define a serial port with the BSC protocol, the following port parameters are 

listed on the console: 

SDM-9230>SE 

SETUP 


PHONE/ 

Memotec Inc. 7-3




Port number (ETH1/ETH2/CSL/1,def:CSL) ? 1 

PORT 1> Protocol (def:PVCR) ? BSC 










• All of these parameters are common to other legacy protocols, and are detailed in 

“SE/PORT Configuration Parameters” on page 12-1. 

7.3.2 BSC on the Dual Serial Interface Card 

SE/SLOT/ 

Channel/BSC 

example 

When you define a serial port on a Dual Serial interface card with the BSC protocol, the 

following parameters are listed on the console: 

SDM-9230>SE 

SETUP 


PHONE/ 





PORT 201> Protocol (def:OFF) ? BSC 










• These are the same parameters as those for a built-in serial port. 

Caution: The Dual Serial interface card for the SDM-9360, SDM-9380 and 

SDM-9585 does not support Fallback. 

7-4 Memotec Inc.

COP Protocol 

8 

Memotec Inc. 8-1


8.1 Support of Character-oriented Protocols 

8.1.1 Reception: 

8.1.2 Transmission: 

The NetPerformer supports several Character Oriented Protocol (COP) variations: 

• Poll/Select: Unisys (Burroughs) 

• Uniscope, UTS: Unisys 

• VIP, IPARS: Honeywell 

The COP driver is used when a serial port is configured with the COP protocol, and has 

the following features: 

• Two independently configurable sync characters. 

• Configurable character format of 6 or 8 bits. 

• Configurable idle line condition (SPACE or MARK). 

• Configurable Drop Sync count characters. 

• Configurable Drop Sync characters (00H or FFH). 

The COP message format is as follows: 

SYNC1 SYNC2 DATA (up to 4096 bytes) DROP SYNC CHARS 

The COP driver for NetPerformer supports all character-oriented frame formats with a 

DATA field of up to 4096 bytes. This driver works in the following way: 

• Strips all characters until synchronization is achieved. 

• Receives all characters until the Drop Sync characters are completely received. 

• Transmits 2 sync bytes, then 

• Transmits the complete frame, then 

• Transmits the Drop Sync characters. 

Except for the SYNC field, the receiver does not alter any byte or bit before forwarding it 

to the compressor and then to the composite link. DATA is forwarded to the compressor in 

48- byte cells as they are received. 

At the remote end, the composite link information is decompressed and passed to the 

transmitter which then transmits the data. The transmitter can be started on the first cell if 

fallback is enabled, or on the complete frame if fallback is disabled. 

8-2 Memotec Inc.

8.2 Configuring a COP Connection 

COP Protocol 


required to configure a COP port. 




A COP port can be configured on a built-in serial port or a serial port on a Dual Serial Port 

interface card. 

• To configure a built-in serial port on the base unit as a COP port: 



- Set the Protocol to COP. 


• To configure a serial port on the Dual Serial interface card as a COP port: 





- Set the Protocol to COP. 


8.2.1 COP on a Built-in Serial Port 

SE/PORT/#/ 

COP example 






When you define a serial port with the COP protocol, the following port parameters are 

listed on the console: 

SDM-9230>SE 

SETUP 


PHONE/ 




PORT 1> Protocol (def:BSC) ? COP 



Memotec Inc. 8-3






PORT 1> Idle (def:MARK) ? 

PORT 1> Synchronization character (def:1616) ? 

PORT 1> Number of desynch. characters (1-100,def:3) ? 

PORT 1> Desynchronization character (def:FF) ? 




• Protocol, Interface, Clocking mode, Port speed (bps), Fallback speed, Modem 

control signal, Transmission start level, Idle, Remote unit, Class and Remote port 

number are common to other legacy data protocols, and are detailed in SE/PORT 

Configuration Parameters on page 1. 

• Synchronization character, Number of desynch. characters and Desynchronization 

character are unique to the COP protocol. Refer to COP Port on page 19 for 

details. 

8.2.2 COP on the Dual Serial Interface Card 

SE/SLOT/ 

Channel/COP 

example 

When you define a serial port on the Dual Serial interface card with the COP protocol, the 


SDM-9230>SE 

SETUP 


PHONE/ 





PORT 202> Protocol (def:OFF) ? COP 


PORT 202> Clocking mode (def:EXTERNAL) ? 



PORT 202> Idle (def:MARK) ? 

PORT 202> Synchronization character (def:1616) ? 

PORT 202> Number of desynch. characters (1-100,def:3) ? 

PORT 202> Desynchronization character (def:FF) ? 




• These are the same parameters as those for a built-in serial port. 



8-4 Memotec Inc.

X.25 Protocol 

9 

Memotec Inc. 9-1


9.1 NetPerformer Support of X.25 

9.1.1 X.25 Encapsulation 

The NetPerformer is able to encapsulate X.25 in Frame Relay packets, permitting 

connection of an X.25 device to the serial port. This is a simple X.25 solution which 

requires: 

• Configuration of an HDLC-like port on the NetPerformer, using the X25 port 

protocol 

• Configuration of a Frame Relay PVC to transport the encapsulated X.25 data to 

the remote side 

• At least one X.25 switch at some location in the network. 

For an example of this application, turn to “X.25 Application Example” on 

page 9-5. 

The NetPerformer supports two X.25 encapsulation techniques that are part of the ANSI 

T1.617a specification: 

• FRF.3 Annex F: Deals with multiprotocol support over Frame Relay. With 

Annex F encapsulation, a frame identifier header is added to the normal frame to 

differentiate the various protocols. In the case of X.25, this identifier consists of a 

6-byte suite. When an X.25 frame is received by the NetPerformer HDLC driver, 

it is stripped of its leading and trailing flags, as well as its CRC. Then a Frame- 

Relay header (2 bytes of DLCI) and a 6-byte frame identifier is added to the X.25 

frame before transmission. The X.25 frame is integrally copied into a Frame 

Relay frame (LAPB header and data). All types of frames (INFO, UI, SUPERVI- 

SOR) are copied in the same way. 

• FRF.3 Annex G: Deals with CCITT X.25 encapsulation over Frame-Relay. With 

Annex-G encapsulation, an X.25 frame received by the NetPerformer HDLC 

driver is stripped of its leading and trailing flags, as well as its CRC. It is then 

integrally copied into a Frame Relay frame. All frame types that are received on 

the HDLC port (INFO, UI, SUPERVISOR) are encapsulated. 

For details on PVC configuration, refer to the WAN/Frame Relay module of this 

document series. 

9.1.2 HDLC Driver Settings 

To function correctly, the X.25 protocol requires both the HDLC driver and a Frame Relay 

PVC. X25 encapsulation is activated when the PVC is linked with an X25 port. In addition 

to the parameters listed above, other parameters governing the HDLC driver are 

automatically set to the following values: 

• CRC Encoding:NRZ 

• Modem Control Signal:STATIC 

• Transmission Start Level:MAX 

9-2 Memotec Inc.

• Idle:FLAG 

• Frame Delay:0.0 

9.2 Configuring an X25 Port 

X.25 Protocol 


required to configure an X25 port. 




An X25 port can be configured on a built-in serial port or a serial port on a Dual Serial 

Port interface card. 

• To configure a built-in serial port on the base unit as an X25 port: 



- Set the Protocol to X25. 


• To configure a serial port on the Dual Serial interface card as an X25 port: 





- Set the Protocol to X25. 


9.2.1 X25 on a built-in Serial Port 






When you define a built-in serial port with the X25 protocol, the following port 


SE/PORT/#/ 

X25 example SDM-9230>SE 

SETUP 


PHONE/ 

Memotec Inc. 9-3





PORT 1> Protocol (def:T-ASYNC) ? X25 





PORT 1> X25 frame relay encapsulation (def:ANNEX-G) ? 

PORT 1> PVC number (1-300,def:1) ? 

• Protocol , Interface, Clocking mode, Port speed (bps), Fallback speed and PVC 

number are common to other legacy protocols, and are detailed in “SE/PORT 

Configuration Parameters” on page 12-1. 

• The X25 frame relay encapsulation parameter is unique to the X25 protocol. Turn to 

“X25 Port” on page 12-21 for details. 

9.2.2 X25 on the Dual Serial Interface Card 

SE/SLOT/ 

Channel/X25 

example 

When you define a serial port on the Dual Serial interface card with the X25 protocol, the 


SDM-9230>SE 

SETUP 


PHONE/ 





PORT 201> Protocol (def:S-SDLC) ? X25 





PORT 201> X25 frame relay encapsulation (def:ANNEX-G) ? 

• All of these parameters are the same as those for the built-in serial port. 



9-4 Memotec Inc.

9.3 X.25 Application Example 

X.25 Host 

C 

X.25 

X.25 Protocol 

To select an appropriate PVC and configure your network for X.25 encapsulation, study 

the following example: 

X.25 

Switch 

B 

Frames in the Multiplex PVC 

are passed to the Frame 

Relay link to the X.25 switch 

Frame 

Relay 

A 

X.25 frames from user are 

encoded in a Multiplex PVC 

using Annnex G or F 

Multiplex PVCS are passed 

through the Frame Relay 

network via PVCR PVC 

NetPerformer 

LOS ANGELES 

X.25 PVC 

Annex G or F 

BOSTON 

Frame Relay Cloud 

NetPerformer 

Figure 9-1: NetPerformer Solution in an X.25 Network 

X.25 User Equipment 



This example includes three situations where X.25 support is required: 

• The X.25 user equipment supports native X.25 only. It does not support Frame 

Relay. An example of this in Figure 9-1 is the BOSTON site. 

The NetPerformer in BOSTON receives the X.25 frames coming from the user 

equipment, and encapsulates these frames as Frame Relay frames using Annex G 

or Annex F. The frames are then compressed and multiplexed with other data 

using a Multiplex PVC, and are sent to the central NetPerformer (LOS ANGE- 

LES). Once the central NetPerformer has fully decompressed and received a 

frame, it transmits it in a Multiplex PVC on the Frame Relay connection to the 

X.25 switch. 

• The X.25 user equipment supports Frame Relay Annex G or F, and is attached 

directly to the Frame Relay network. An example of this is the NEW YORK site. 

For this situation the NetPerformer at the central location performs normal Frame 

Relay switching with no changes required. 

• The X.25 user equipment supports Frame Relay Annex G or F, but is attached to 

the network via a NetPerformer. An example of this is the WASHINGTON site. 

Here, the NetPerformers in WASHINGTON and LOS ANGELES require normal 

Multiplex PVC mode, with no changes required. 

Memotec Inc. 9-5 

PVC 

PVC 

NetPerformer 

WASHINGTON 

X25 

Frame 

Relay 

X.25 PVC 

Annex G or F 

Frame 

Relay 

X.25 PVC 

Annex G or F 

NEW YORK


9-6 Memotec Inc.

IPX Connections 

10 

Memotec Inc. 10-1


10.1 NetPerformer Support of IPX Routing 

The NetPerformer supports Internetwork Packet Exchange (IPX) routing for use in Novell 

networks. Packets are transported using the Ethernet 802.3, Ethernet V2 or Token-Ring 

802.5 access protocols. The IPX layer handles addressing between networks and nodes, 

based on IPX network numbers. 

Under IPX, the NetPerformer connects the various network segments and manages the 

addressing and routing of information packets. All network layer tasks are performed 

using RIP and the Service Advertising Protocol (SAP). RIP is used to maintain the routing 

tables, and SAP is used to exchange service information between all routers in the 

network. 

To enable IPX functions and commands on the NetPerformer, use the Router parameter of 

the Setup IPX menu (see next section). You must also configure the IPX RIP, IPX SAP and 

IPX Network Number parameters on the port and PVC interfaces, and the IPX 

Encapsulation parameter on the LAN port to allow for IPX routing on the NetPerformer. 

For details on these parameters, refer to “SE/IPX Configuration Parameters” on page 14- 

1. 

10-2 Memotec Inc.

10.2 Configuring an IPX Connection 


As mentioned before, several areas of the NetPerformer console are involved when 

configuring an IPX connection: 

• Ethernet port parameters (refer to the LAN connection and IP Networks module 

of this document series): 

SDM-9230>SE 

SETUP 


PHONE/ 



Port number (ETH1/ETH2/CSL/1,def:ETH1) ? 

PORT ETH 1> Protocol (def:ETH AUTO) ? 

... 

PORT ETH 1> IPX RIP (def:DISABLE) ? 

PORT ETH 1> IPX SAP (def:DISABLE) ? 

PORT ETH 1> IPX network number (def:00000000) ? 

PORT ETH 1> IPX encapsulation (def:ETH 802.2) ? 

... 

• PVCR port parameters (refer to the WAN/Leased Lines module of this document 

series): 

SDM-9230>SE 

SETUP 


PHONE/ 




PORT 1> Protocol (def:PPP) ? PVCR 

... 

PORT 1> IPX RIP (def:DISABLE) ? 

PORT 1> IPX SAP (def:DISABLE) ? 

PORT 1> IPX network number (def:00000000) ? 

... 

• PVCR PVC parameters (refer to the WAN/Frame Relay module of this document 

series): 

SDM-9230>SE 

SETUP 


PHONE/ 


def:BRIDGE) ? PVC 

PVC number (1-300,def:1) ? 

PVC 1> Mode (def:PVCR) ? 

... 

PVC 1> IPX RIP (def:DISABLE) ? 

PVC 1> IPX SAP (def:DISABLE) ? 

PVC 1> IPX NETWORK NUMBER (def:00000000) ? 

... 

Memotec Inc. 10-3


• RFC1490 PVC parameters (refer to the WAN/Frame Relay module of this document 

series): 

SDM-9230>SE 

SETUP 


PHONE/ 


def:BRIDGE) ? PVC 

PVC number (1-300,def:1) ? 2 

PVC 2> Mode (def:OFF) ? RFC1490 

... 

PVC 2> IPX RIP (def:DISABLE) ? 

PVC 2> IPX SAP (def:DISABLE) ? 

PVC 2> IPX NETWORK NUMBER (def:00000000) ? 

... 

• The IPX parameters, which are configured using the IPX option of the SETUP 

command: 


SE, IPX ipx (category) [ipx] (heading) 

IPX 

GLOBAL FILTER 

Setup (SE) 

Unit ID> 

(main prompt) 

Figure 10-1: SETUP/IPX Path on the CLI Tree 

The Setup IPX menu lets you control IPX routing on the NetPerformer. For SNMP, use the 

ipx category. For text-based configuration the [ip] heading is used. At the console, enter 

SE followed by IPX to reach the Setup IPX menu. A second Item prompt is displayed to 

select one of the IPX submenus, as shown below. 

SDM-9230>SE 

SETUP 



def:BRIDGE) ? IPX 

Item (GLOBAL/FILTER,def:GLOBAL) ? 

... 

10-4 Memotec Inc.


The six IP submenus control the following: 

• GLOBAL: configures the unit for general IPX routing characteristics (see next 

section) 

• FILTER: configures the parameters that define IPX SAP filtering (see “IPX SAP 

Filtering Parameters” on page 10-5). 

10.2.1 Global IPX Parameters 

SE/IPX/ 

GLOBAL 

example 

To select global IPX parameters enter GLOBAL at the second Item prompt. The following 

parameters will be listed: 

SDM-9230>SE 

SETUP 




Item (GLOBAL/FILTER,def:GLOBAL) ? 

IPX> Router (def:DISABLE) ? ENABLE 

IPX> Internal network number (def:00000000) ? 

The global IPX parameters are detailed in the section “SE/IPX/GLOBAL Parameters” on 

page 14-4. 

10.2.2 IPX SAP Filtering Parameters 

SE/IPX/FILTER 

example 

The Setup IPX menu includes a set of parameters that define IPX SAP filters. These filters 

permit greater control of SAP table entries, so that only the desired services are routed. For 

access to these parameters using SNMP, select the appropriate MIB variable from the 

ipxfilter group. To access these parameters from the console: 

1. Enter SE to execute the Setup command, 

2. Enter IPX at the Item prompt to select the IPX menu, 

3. Enter FILTERS (or an abbreviation of this term) at the second Item prompt to access 

the IPX Filter parameters. 

4. Select a specific filter entry (1 to 10) with the IPX Filter entry number parameter. 

5. Enable and define the filter with the Enable, SAP and Type parameters. 

SDM-9230>SE 

SETUP 




Item (GLOBAL/FILTER,def:GLOBAL) ? FILTER 

IPX Filter entry number (1-10,def:1) ? 

IPX FILTER 1> Enable (def:DISABLE) ? ENABLE 

IPX FILTER 1> SAP (def:0000) ? 

IPX FILTER 1> Type (def:STANDARD) ? 

Details on these parameters are provided in the section “SE/IPX/FILTER Parameters” on 

page 14-7. 

Memotec Inc. 10-5


10.3 Checking IPX Connection Status 

10.3.1 IPX RIP Routing Table 

DR/IPX/RIP 

example 

The IPX option of the Display Routing Table (DR) command displays both IPX RIP and 

IPX SAP routing tables, from which you can determine the status of IPX connections on 

the NetPerformer. To access IPX routing tables using SNMP, open the private Novell MIB 

and select the private/novell/ipx group. 

Console SNMP 

DR, IPX Novell MIB - private/novell/ipx 

NOTE: To view the tables with IPX option of the DR command, the IPX RIP or IPX 

SAP parameters must be enabled on one or more ports or PVCs. The Router 

parameter of the Setup IPX menu must also be enabled to permit viewing the 

status of remote connections. 

To access this table using SNMP, open the private Novell MIB and select the private/ 

novell/ipx group. To access this table from the console, enter DR on the command line, and 

then select IPX. Two tables are available; select RIP or SAP. 

To view the IPX RIP table from the console, enter RIP at the second Item prompt of the 

Display Routing Table command. 

SDM-9230>DR 

DISPLAY ROUTING TABLE 

Item (IP/IPX,def:IP) ? IPX 

Item (RIP/SAP,def:RIP) ? 

The RIP table has 14 entry(ies) 

NETWORK NUMBER TICKS HOP COUNT NEXT HOP AGE 

30212251 2 1 FCFEE67F 2 s 

B45A3DAD 2 1 FCFEE67F 2 s 

B9360001 3 2 00000000 32 s 

B9360002 4 3 00000000 32 s 

B9360003 2 1 00000000 32 s 

B9360004 3 2 00000000 32 s 

B9360005 14 3 00000000 32 s 

B9380001 3 2 00000000 51 s 

B9380002 2 1 00000000 51 s 

B9380003 3 2 00000000 51 s 

B9380004 14 3 00000000 51 s 

B9380009 25 4 00000000 51 s 

BADBABE0 3 2 FCFEE67F 59 s 

FCFEE67F 1 0 FCFEE67F 0 s 

The IPX RIP routing table entries are detailed in the section “IPX Statistics” on page 15-2. 

10-6 Memotec Inc.

10.3.2 IPX SAP Routing Table 

DR/IPX/SAP 

example 


To view the IPX SAP routing table from the console, enter SAP at the second Item prompt 

of the Display Routing Table command. 

SDM-9230>DR 

DISPLAY ROUTING TABLE 

Item (IP/IPX,def:IPX) ? 

Item (RIP/SAP,def:RIP) ? SAP 

The SAP table has 10 entry(ies) 

NET NUM NODE SOCKET SERVICE NAME TYPE HOP COUNT AGE 

30212251 000000000001 0000 PRE-RD-001 027B 1 38 s 

30212251 000000000001 0005 PRESTICOM______________ 026B 1 38 s 

30212251 000000000001 0451 PRE-RD-001 0004 1 38 s 

30212251 000000000001 4006 PRESTICOM______________ 0278 1 38 s 

30212251 000000000001 4014 ISPRE-RD-00118724008000 0102 1 38 s 

30212251 000000000001 4015 LDPNVIRUS_PROTECT_51213 0102 1 38 s 

30212251 000000000001 4016 IVPRE-RD-00118724008000 0102 1 38 s 

30212251 000000000001 401F PRE-RD-001 0237 1 38 s 

30212251 000000000001 4800 PRE-RD-001 0238 1 38 s 

30212251 000000000001 8059 BSER4.00-6.10_302122500 004B 1 38 s 

The IPX SAP routing table entries are detailed in “DR/IPX/SAP” on page 15-3. 

Memotec Inc. 10-7


10-8 Memotec Inc.

Monitoring Data Port Functions 

11 

Memotec Inc. 11-1


11.1 Checking Legacy Data Connection Status 

Display Counters 

(DC) 

PORT SLOT 

Use the following commands to view statistics on connections configured with a legacy 

protocol: 

• Display the connection counters with the PORT or SLOT option of the Display 

Counters (DC) command 

• View the connection status with the PORT, SLOT or PU option of the Display 

States (DS) command 

• For a continuous display of port status in real time, execute the Display Port 

States (DPORT) command 

• Display connection errors with the PORT, SLOT or PU option of the Display 

Errors (DE) command 

• For an SNA/SDLC application, you can view a display of PU status in real time 

by executing the Display PU States (DPU) command 

• The Active PU command (AP) can be used to verify which PUs are currently 

active in SNA/SDLC polling mode 

• View the current parameter configuration with the PORT, SLOT or PU option of 

the Display Parameters (DP) command. 

Display States 

(DS) 

PORT SLOT PU 

Unit ID> 

(main prompt) 

Display Port 

States (DPORT) 

Display Errors 

(DE) 

PORT SLOT PU 

Display PU 

States (DPU) 

Figure 11-1: Legacy Data Statistics Commands in the CLI Tree 

Display 

Parameters (DP) 

PORT SLOT PU 

11-2 Memotec Inc.

11.2 Display Counters (DC) 

DC/PORT 

example 


SDM-9230>DC 

DISPLAY COUNTERS 

Item (BOOTP/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/SLOT/SVC/ 

TIMEP, 

def:SLOT) ? PORT 

Counters (MEAN/PEAK,def:MEAN) ? 

Compression rate.................................4.51 (M) 

Decompression rate...............................2.56 (M) 

PORT CSL> Transmitter rate.......................16 % (M) 

PORT CSL> Receiver rate..........................12 % (M) 

PORT 1> Transmitter rate........................58 % (M) 

PORT 1> Receiver rate............................3 % (M) 

PORT 1> Number of frames transmitted............115448 

PORT 1> Number of frames received...............115545 

PORT 1> Number of octets transmitted............968993 

PORT 1> Number of octets received...............1206055 

PORT 2> Transmitter rate........................15 % (M) 

PORT 2> Receiver rate...........................17 % (M) 

PORT 2> Number of frames transmitted............3976865 

PORT 2> Number of frames received...............3824471 

PORT 2> Number of octets transmitted............45144025 

PORT 2> Number of octets received...............50688001 

DC/SLOT example 

SDM-9230>DC 

DISPLAY COUNTERS 

Item (BOOTP/CONFIG/DNS/IP/NAT/PORT/PVC/Q922/Q933/QOS/SLOT/SVC/ 

TIMEP, 

def:BOOTP) ? SLOT 

Counters (MEAN/PEAK,def:MEAN) ? 

SLOT 3> 

PORT 303> Transmitter rate......................0 % (M) 

PORT 303> Receiver rate.........................0 % (M) 

PORT 303> Number of frames transmitted..........1313 

PORT 303> Number of frames received.............0 

PORT 303> Number of octets transmitted..........64337 

PORT 303> Number of octets received.............0 

... 












Memotec Inc. 11-3









... 

11-4 Memotec Inc.

11.3 Display States (DS) 

DS/PORT 

example 

DS/SLOT 

example 


SDM-9360>DS 

DISPLAY STATES 

Item (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:GLOBAL) ? PORT 

PORT ETH> Protocol..............................ETHERNET 

PORT ETH> Interface.............................10BASET 

PORT ETH> Speed.................................10M 

PORT ETH> Duplex mode...........................HALF 

PORT ETH> Operating mode........................L- 

PORT ETH> State.................................OPEN 

PORT ETH> Network address.......................AAAAAAAAA001 

PORT ETH> Burned-in address.....................00200AB05825 

PORT ETH> Number of deferred transmissions......430 

PORT ETH> Number of collision frames............2261 

PORT CSL> Protocol..............................CSL 

PORT CSL> Interface.............................DTE-UNDEFINED 

PORT CSL> Speed used [bps]......................0 

PORT CSL> Modem signals.........................----C- 

PORT CSL> State.................................DISC 

PORT 1> Protocol................................P-SDLC 

PORT 1> Interface...............................DTE-V35 

PORT 1> Speed used [bps]........................64000 

PORT 1> Modem signals...........................STDRC- 

PORT 1> State...................................DATA 

PORT 2> Protocol................................S-SDLC 

PORT 2> Interface...............................DTE-V35 

PORT 2> Speed used [bps]........................64000 

PORT 2> Modem signals...........................-T-R-- 

PORT 2> State...................................IDLE 

Modem signals: d(S)r d(T)r (D)cd (R)ts (C)ts r(I) (-)off 

SDM-9230>DS 


Item (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:GLOBAL) ? SLOT 

SLOT> Slot number (1/2/3/ALL,def:3) ? 

SLOT 3> 

PORT 300> State.................................OUT OF SYNC 

PORT 300> Interface.............................E1 

PORT 316> Transparent Signaling Channel.........IN SYNC 

PORT 301> Protocol..............................PVCR 

PORT 301> Speed used [bps]......................64000 

PORT 301> Modem signals.........................--D--- 

PORT 301> State.................................TEST 

PORT 302> Protocol..............................HDLC 


Memotec Inc. 11-5


PORT 302> Modem signals.........................------ 

PORT 302> State.................................CALL 

PORT 303> Protocol..............................PASSTH 


PORT 303> Modem signals.........................------ 

PORT 303> State.................................CALL 

Modem signals: d(S)r d(T)r (D)cd (R)ts (C)ts r(I) (-)off 

DS/PU example 

SDM-9380>DS 


Item (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:PORT) ? PU 

PU 1> State...................................CONNECTED 

PU 2> State...................................WAIT PRI CONN 

PU 3> State...................................WAIT SEC ACTIVE 



PU 6> State...................................PAUSE 



PU 9> State...................................CONNECTION OFF 

PU 10> State..................................CONNECTION OFF 



... 

11-6 Memotec Inc.

11.4 Display Port States (DPORT) 

DPORT 

example 


SDM-9380>DPORT 

DISPLAY PORT STATES 

-------------------------------------------------------------------------------- 

|PORT# PROTOCOL INTERFACE SPEED MODEM STATE DELAY | 

| (BPS) SIGNALS | 

-------------------------------------------------------------------------------- 

| 1 FR-USER DTE-V35 2048k STDRC- DATA | 

| 2 PVCR DTE-V35 2048k S----- OFF | 

| 3 X25 DCE-V35 64000 STDRC- DATA | 

| 101 PVCR T1-TE 1536k STDRC- DATA 16ms | 

| 201 FR-USER E1-TE 1984k 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. 

Memotec Inc. 11-7


11.5 Display Errors (DE) 

DE/PORT 

example 

DE/SLOT 

example: 

PASSTHRUOF 

R channels 

SDM-9230>DE 

DISPLAY ERRORS 

Item (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PU/PVC/Q922/SLOT/SVC/ 

TIMEP, 

def:SLOT) ? PORT 

... 

PORT 1> Number of bad frames......................99 UQFSBA 

PORT 1> Number of underruns.......................0 

PORT 1> Number of retries.........................0 

PORT 1> Number of restarts........................11 

PORT 1> Number of frames discarded (overrun)......0 

PORT 1> Number of octets discarded (bad)..........0 

PORT 1> Number of octets discarded (overrun)......0 

PORT 2> Number of bad frames......................1 ----B- 

PORT 2> Number of underruns.......................0 

PORT 2> Number of retries.........................0 

PORT 2> Number of restarts........................0 

PORT 2> Number of frames discarded (overrun)......0 

PORT 2> Number of octets discarded (bad)..........0 

PORT 2> Number of octets discarded (overrun)......0 

... 

Bad flags: U:Bad LENGTH Q:Overflow F:Flush S:Overrun B:Bad CRC 

A:Abort 

9230A>DE 



TIMEP, 

def:BOOTP) ? SLOT 

SLOT> Slot number (1/2/3/ALL,def:1) ? 2 

SLOT 2> 

PORT 200> Number of errored seconds.............0 

PORT 200> Number of severely errored seconds....0 

PORT 200> Number of severely errored frames.....0 

PORT 200> Number of unavailable seconds.........0 

PORT 200> Number of controlled slip seconds.....0 

PORT 200> Number of path code violations........0 

PORT 200> Number of line errored seconds........0 

PORT 200> Number of bursty errored seconds......0 

PORT 200> Number of degraded minutes............0 

PORT 200> Number of line code violations........0 

PORT 200> Number of CRC errors..................0 

PORT 200> Number of frame length errors.........0 

PORT 200> Number of abort sequences.............0 

PORT 200> Number of non-aligned octets..........0 

PORT 200> Number of HDLC framing errors.........0 

PORT 200> Number of returned rx buffers.........0 

PORT 200> Number of channel restarts............0 

11-8 Memotec Inc.

DE/PU 

example 


PORT 201> Number of bad frames..................3 --F--- 

PORT 201> Number of underruns...................1 

PORT 201> Number of retries.....................0 

PORT 201> Number of restarts....................0 

PORT 201> Number of frames discarded (overrun)..0 

PORT 201> Number of octets discarded (bad)......0 

PORT 201> Number of octets discarded (overrun)..0 

PORT 202> Number of bad frames..................3 --F--- 

PORT 202> Number of underruns...................1 

PORT 202> Number of retries.....................0 

PORT 202> Number of restarts....................0 

PORT 202> Number of frames discarded (overrun)..0 

PORT 202> Number of octets discarded (bad)......0 

PORT 202> Number of octets discarded (overrun)..0 

Bad flags: U:Bad LENGTH Q:Overflow F:Flush S:Overrun B:Bad CRC 

A:Abort 

SDM-9380>DE 



TIMEP, 

def:PORT) ? PU 

PU 1> Number of compressor errors...............0 

PU 1> Number of channel overflow errors.........0 

PU 1> Number of channel abort errors............0 

PU 1> Number of channel sequence errors.........0 













Memotec Inc. 11-9


11.6 Display PU States (DPU) 

DPU example 

SDM-9230>DPU 

DISPLAY PU STATES 

------------------------------------------------------------------ 

| PU# STATE SESSIONS STATE: #SA=5 #SP=2 | 

| | 

------------------------------------------------------------------ 

| 1 WAIT SEC ACTIVE | 

| 2 CONNECTED | 


| 4 WAIT PRI CONN | 



| 7 PAUSE | 


| 9 CONNECTION OFF | 







| | 

| | 

| | 

| | 

------------------------------------------------------------------ 

Use HOME, END, UP and DOWN arrow keys to scroll. Press any other key to exit. 

11-10 Memotec Inc.

11.7 Display Parameters (DP) 

DP/SLOT 

example: 

PASSTHRUOF 

R channels 


9230A>DP 

DISPLAY PARAMETERS 


PHONE/ 

PORT/PU/PVC/SCHEDULE/SLOT/USER/VLAN/ALL,def:BRIDGE) ? SLOT 

SLOT> Slot number (1/2/3,def:1) ? 2 

PORT 200> Status................................ENABLE 

PORT 200> Clock recovery........................DISABLE 

PORT 200> Digital port clock source.............INTERNAL 

PORT 200> Signaling mode........................NONE 

PORT 200> Pcm encoding law......................A-LAW 

PORT 200> Idle code.............................7E 

PORT 200> Zero suppression mode.................HDB3 

PORT 200> Gain limit............................-12DB 

PORT 200> CRC4 mode.............................ENABLE 

PORT 200> International bit.....................ENABLE 

PORT 200> ETS 300 011 mode......................DISABLE 

PORT 200> Loopback..............................DISABLE 

PORT 201> Protocol..............................PASSTHRUOFR 

PORT 201> Timeslot..............................1 

PORT 201> Number of consecutive timeslots.......1 


PORT 201> Transmission start level..............48 

PORT 201> Reception frame size..................3 

PORT 201> PVC number............................32 

PORT 202> Protocol..............................PASSTHRUOFR 

PORT 202> Timeslot..............................2 

PORT 202> Number of consecutive timeslots.......1 


PORT 202> Transmission start level..............48 

PORT 202> Reception frame size..................3 

PORT 202> PVC number............................33 

Memotec Inc. 11-11


11.8 Displaying Active PUs 

AP example 

SDM-9230>AP 

ACTIVE PU 

Active PU> 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 

This command can be used to verify which PUs are currently active. This may be useful 

during the configuration process as well as for troubleshooting purposes. 

NOTE: This command is not available from SNMP. 

11-12 Memotec Inc.

SE/PORT Configuration Parameters 

12 

Memotec Inc. 12-1


12.1 Common Parameters 

12.1.1 Protocol 


Protocol ifwanProtocol [ifwan#] Protocol 

Defines the operating protocol for the port or channel. Legacy protocols provide data 

connections to end-user data-based equipment, including support of: 

• HDLC and BSC protocols 

• Reliable asynchronous (R-ASYNC) or Transparent asynchronous (T-ASYNC) 

applications 

• A generic character-oriented synchronous (COP) application 

• A passthrough channel (PASSTHRU) 

• HDLCOFR and PASSTHRUOFR provide transport of legacy protocols over 

Frame Relay 

• For an SNA/SDLC application, use P-SDLC when the port connects to one or 

more cluster controllers (PUs), or S-SDLC when the port connects to a front-end 

processor or a mainframe. 

• Use the X.25 value of the Protocol parameter when connecting to an X.25 device 

• Use the OFF value when the port is not used. 

NOTE: The PVCR protocol is discussed in the WAN/Leased Lines module of this 

document series, FR-NET and FR-USER in the WAN/Frame Relay module, 

and PPP in the WAN/Point-to-Point (PPP) module. 

Values: OFF, P-SDLC, S-SDLC, HDLC, HDLCOFR, T-ASYNC, 

R-ASYNC, BSC, COP, PVCR, PASSTHRU, PASSTHRUOFR, 

FR-NET, FR-USER, PPP, X25 

Default: Built-in serial port 1: FR-USER 

Other serial ports: PVCR 

Digital channels: OFF 

12-2 Memotec Inc.

12.1.2 Port speed (bps) 

12.1.3 Clocking mode 



Port speed (bps) ifwanSpeed-bps [ifwan#] Speed-bps 

The internal speed of the port. Speeds up to 2 Mbps are supported on a WAN link (port set 

in PVCR; no compression), Frame Relay, SDLC, HDLC or PPP port. 

However, when a serial port is configured with other protocols, the highest attainable 

speed is less than 2 Mbps. For example, PASSTHRU data is transmitted at a maximum of 

128 Kbps. 

NOTE: The Port Speed parameter is not used for a port in external clocking. It is also 

not required for a digital channel. 

Values: 1200 - 128000 

Default: 56000 


Clocking mode ifwanClocking [ifwan#] Clocking 

This parameter determines the clock source for the port. For all protocols except T- 

ASYNC, R-ASYNC and asynchronous PPP, the clock source is automatically controlled 

by the NetPerformer. For the asynchronous ports, this parameter can be used to specify a 

physical clock source, using internal or external isochronous clocking. In isochronous 

mode, the time intervals between significant actions or signals are either equal in duration 

or are whole multiples of the shortest time interval detected. 

Here are the possible settings for ports configured with any protocol except the 

asynchronous protocols (T-ASYNC, R-ASYNC and asynchronous PPP): 

• INTERNAL: For a DTE interface, the unit supplies a clock signal on RS-232D 

pin 24 (V.35 pins U-W) and uses this clock to transmit data. The unit also accepts 

a clock signal on RS-232D pin 15 (V.35 pins V-X) to clock the received data. 

For a DCE interface, the unit provides two independent clock signals: one on RS- 

232 pin 15 (V.35 pins V-X) to clock the data going out and one on RS-232 pin 17 

(V.35 pins Y-AA) to clock the data coming in. 

• EXTERNAL: For a DTE interface, the unit accepts two clock signals: one on 

RS-232 pin 15 (V.35 pins V-X) to clock the received data and one on RS-232 pin 

17 (V.35 pins Y-AA) to clock the transmitted data. 

For a DCE interface, the unit accepts one clock signal on RS-232 pin 24 (V.35 

pins U-W). This clock signal is used to clock both transmitted and received data 

and is returned on RS-232 pins 15 and 17 (V.35 pins V-X and Y-AA). 

Memotec Inc. 12-3


• IPL: This value is available only for WAN/user ports configured with a DCE 

interface and an SDLC or HDLC protocol. The unit provides two clock signals 

exactly in phase: one on RS-232 pin 15 (V.35 pins V-X) to clock the transmitted 

data, and one on RS-232 pin 17 (V.35 pins Y-AA) to clock the received data. This 

clock mode may be required on an IBM 3174 controller when fallback is used. 

NOTE: The Dual Serial interface card for the SDM-9360, SDM-9380 and SDM-9585 

does not support IPL clocking mode. 

Values: (Non-asynchronous ports): INTERNAL, EXTERNAL, IPL 

Default: For DCE interface: INTERNAL 

for DTE interface: EXTERNAL 

Here are the possible settings of the Clocking Mode parameter for asynchronous ports 

(T-ASYNC, R-ASYNC and asynchronous PPP): 

• ASYNC: No physical clocking is used. This value permits sampling using the 

internal clock on the NetPerformer processor. 

• ISO-INT: Configures the asynchronous port with an internal isochronous clock 

source. Here the clock is external to the data, but is generated by the NetPerformer. 

• ISO-EXT: Configures the port with an external isochronous clock source. This 

clock is external to the data, and is received by the NetPerformer from an external 

source. 

Values: (Asynchronous ports only): ASYNC, ISO-INT, ISO-EXT 

Default: ASYNC 

12-4 Memotec Inc.

12.2 HDLC and PASSTHRU Ports 

12.2.1 Fallback speed 



Fallback speed ifwanFallBackSpeed-bps, 

ifwanFallBackSpeed- 

Enable 

[ifwan#] FallBackSpeedbps, 

FallBackSpeed 

Enable 

For all user protocols except ASYNC and PASSTHRU. 

Fallback speed for the transmitter. This parameter determines whether the port speed will 

be reduced if congestion occurs on the WAN links. 

Fallback is applied only if the port is set for DCE Internal clocking. For any other clocking 

mode, the Fallback Speed setting is ignored. 

Caution: If you disable fallback on a unit set for DCE Internal clocking, make 

sure the transmission start level is properly set. Otherwise, data transmission 

problems could occur. Refer to the description of the Transmission start level 

parameter in SE/PORT/#/PVCR Configuration Parameters in the WAN/ 

Leased Lines module of this document series. 

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. 


does not support Fallback. 

For legacy NetPerformer models: 

Select a bit rate that is lower than the value of the Port Speed parameter. As a rule of 

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. 

The range of values given below represents the minimum and maximum fallback speeds 

possible. Some protocols cannot run at the maximum speeds. For these, you must select an 

appropriate lower value. 

For NetPerformer models covered in Values: DISABLE, ENABLE 

this manual: 

Default: ENABLE 

For legacy NetPerformer models: Values: 0 - 2000000 

Default: 2400 

Memotec Inc. 12-5


12.2.2 Transmission start level 


Transmission start level ifwanTxStart 

ifwanTxStartCop 

ifwanTxStartPass 

[ifwan#] TxStart 

TxStartCop 

TxStartPass 

For all user protocols except ASYNC, FR-NET and FR-USER. 

This parameter determines the number of characters (or blocks) that are accumulated 

before the transmitter is enabled when a frame is incomplete. That is, it defines the number 

of cells that are initially queued in the transmitter before starting transmission. 

The possible values of this parameter are different for the PASSTHRU protocol and the 

other user protocols. 

• PASSTHRU Protocol: For a Passthrough channel, the transmission start level 

represents the number of transparent data blocks that the port must accumulate 

before enabling the transmitter. The Transmission Start Level parameter can be 

set from a minimum of 3 to a maximum of 12 blocks of 48 bytes each. The minimum 

level is sufficient when the passthrough speed is lower than 56 Kbps, but 

must be raised at higher speeds in order to minimize underruns. In most applications, 

this parameter does not need to be set higher than 6. The equivalent SNMP 

variable is ifwanTxStartPass. 

• Other User Protocols: For the other user protocols (excluding ASYNC, FR- 

NET and FR-USER), the transmission start level represents the number of characters 

of an incomplete frame that can be held in the output queue. When set to 

MAX, the transmitter is enabled only when a complete frame has been accumulated 

by the NetPerformer. This value prevents underruns but can introduce 

unnecessary delays. 

When the transmission start level is set to a numeric value, the transmitter is enabled at 

that level even if a frame coming from the remote unit has not been completely received. 

The range of values is different for the COP protocol (SNMP ifwanTxStartCop variable) 

and the other user protocols (SNMP ifwanTxStart variable). If the port is DCE with 

INTERNAL clocking mode and Fallback Speed is enabled, the transmitter falls back 

when the number of characters of an incomplete frame in the output queue goes below the 

transmission start level. Otherwise, no fallback occurs. 

An underrun occurs when the transmitter does not receive the end-of-frame on time for the 

frame currently transmitted. If underruns are occurring often, choose a higher value for 

Transmission Start Level parameter. 

Caution: If you choose a numeric value for this parameter, make sure that 

underruns do not occur on the transmitter. 

When this parameter is set to AUTO, the NetPerformer automatically adjusts the 

transmission start level if the port is DCE with INTERNAL clocking mode and Fallback 

Speed enabled. It selects MAX in all other cases. 

12-6 Memotec Inc.

12.2.3 Modem control signal 


NOTE: The Transmission start level is fixed at MAX on a Dual Serial interface card 

on the SDM-9360, SDM-9380 or SDM-9585. 

Values: for PASSTHRU and 

PASSTHRUOFR protocols: 

3 - 48 

for COP protocol: AUTO, MAX, 8, 16, 24, 32, 40, 48, 

96, 144, 192, 256, 512, 1024, 2048 

for other protocols: AUTO, MAX, 8, 16, 24, 32, 48, 96, 

144,192, 256, 512, 1024, 2048 

Default: for PASSTHRU and 

PASSTHRUOFR protocols: 

3 

for COP protocol: AUTO 

for other protocols: AUTO 


Modem control signal ifwanModem [ifwan#] Modem 

For all user protocols except FR-USER, R-ASYNC and X25 

Modem control signal operating mode. With this parameter, the state of the modem signal 

on one user port (DTR for DTE and DSR for DCE) can be passed over the PVCR link to 

the other port. In this way, a port can reflect the modem signals of its corresponding 

remote port. This can be useful when user ports are connected to a dial-up modem, 

especially when the local and remote ports are of different gender (one DTE and one 

DCE). 

Six Modem Control Signal modes are available: STATIC, DYNAMIC, STATPASS, 

DYNAPASS, STATFIX and DYNAFIX. However, some modes are not available on SDLC, 

T-ASYNC and PASSTHRU ports, as explained below. 

STATIC and DYNAMIC: If the port is DCE this parameter controls the operating mode 

of the DCD (or X.21 INDICATION) control signal. In STATIC mode the DCD signal is 

active at all times, as long as the PVCR channel is up. In DYNAMIC mode DCD is active 

only when a frame is transmitted. DYNAMIC mode is not available on T-ASYNC or 

PASSTHRU ports. 

If the port is DTE this parameter controls the operating mode of the RTS (or X.21 

COMMAND) control signal. In STATIC mode the RTS signal is active at all times, as long 

as the PVCR channel is up. In DYNAMIC mode it is active only when a frame is 

transmitted. 

Memotec Inc. 12-7


NOTE: If the port is set in DTE, a frame will be transmitted only when the CTS control 

signal (for RS-232/RS-449/RS-530 or V.35 interface) or X.21 INDICA- 

TION signal is present. 

The Modem control signal is fixed at STATIC on a Dual Serial interface card 

on the SDM-9360, SDM-9380 or SDM-9585. 

The other modes (STATPASS, DYNAPASS, STATFIX, DYNAFIX) are not available on 

SDLC ports. 

STATPASS and DYNAPASS: In these modes the unit conditions activation of the local 

port ready modem signal to the ready modem signal on the remote port. These modes are 

useful when you want the unit to activate or deactivate the local port ready modem signal 

according to signals received from equipment at the remote site. 

For an RS-232 or V.35 port, the ready modem signals are: 

• DCD (Data Carrier Detect) and DSR (Data Signal Ready) when the port is set in 

DCE mode, 

• DTR (Data Terminal Ready) when the port is set in DTE mode. 

For an X.21 port, the ready modem signals are: 

• I (INDICATION) when the port is set in DCE mode, 

• C (COMMAND) when the port is set in DTE mode. 

When the Modem Control Signal parameter is set to STATPASS or DYNAPASS on a DCE 

port, the unit will wait for a raised DCD or DSR signal (or X.21 INDICATION signal) on 

the remote port before activating DCD or DSR on the local port. For a DTE port it will 

wait for a raised DTR (or X.21 COMMAND) signal on the remote port before activating 

DTR on the local port. In STATPASS mode the modem control signals are active at all 

times. That is, once the DTR/DSR signal is raised, the RTS, CTS and DCD signals are 

always high. In DYNAPASS mode they are active only when a frame is transmitted. 

DYNAPASS is not available on T-ASYNC or PASSTHRU ports. 

STATFIX and DYNAFIX: In these modes the ready modem signals stay up, even if the 

line goes down. In STATFIX mode these signals are active at all times. That is, once the 

PVCR channel is established, the modem signals driven by the user port will never go 

down even if the PVCR channel goes down. In DYNAFIX mode the signals are active only 

when a frame is transmitted. DYNAFIX is not available on T-ASYNC or PASSTHRU 

ports. 

Values: STATIC, DYNAMIC, STATPASS, DYNAPASS, STATFIX, 

DYNAFIX 

Default: STATIC 

12-8 Memotec Inc.

12.2.4 Frame delay (ms) 

12.2.5 CRC encoding 

12.2.6 Idle 



Frame delay (ms) ifwanFrameDelay [ifwan#] FrameDelay 

For HDLC protocol only: 

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. 


does not support Frame delay. 

Values: 0.0, 0.5, 1.0, 1.5, 2.0 

Default: 0.0 


CRC encoding ifwanCoding [ifwan#] Coding 

For SDLC, HDLC and PPP protocols only. 

Bit coding for Cyclic Redundancy Check (CRC) purposes. For NRZ (normal) and NRZI 

coding the computed CRC is preset at 1. For normal coding with CRC0 (NRZ-CRC0) and 

NRZI coding with CRC0 (NRZI-CRC0) the computed CRC is preset at 0. The values 

NRZ-CRC0 and NRZI-CRC0 are available for the HDLC and PPP protocols only. 

NOTE: CRC encoding is fixed at NRZ on a Dual Serial interface card on the SDM- 

9360, SDM-9380 or SDM-9585. 

Values: NRZ, NRZI, NRZ-CRC0, NRZI-CRC0 

Default: NRZ 


Idle ifwanIdle [ifwan#] Idle 

For HDLC, SDLC, PPP and COP protocols only. 

Transmitter idle state, which determines the characters to be sent when no data frame is 

transmitted: 

• FLAG: the transmitter continuously sends 7E (flags). 

Memotec Inc. 12-9


12.2.7 Remote unit 

12.2.8 Class 

• MARK: the transmitter continuously sends 1. 

• MARKD: a 20-msec delay is added before the transmitter starts sending 1’s. 

• SPACE: the transmitter continuously sends 0. 

Bit-oriented protocols (SLDC, HLDC, 

PPP): 

Value: FLAG, MARK, MARKD 

Default: FLAG 

Character-oriented protocols (COP): Values: MARK, SPACE 

Default: MARK 


Remote unit ifwanRemoteUnit [ifwan#] RemoteUnit 

The remote NetPerformer to which traffic from this PASSTHRU link will be directed. 

NOTE: The Unit name is defined on the remote unit using the SETUP/GLOBAL submenu. 

Refer to the chapter Global Functions in the Quick Configuration 

module of this document series. 

For a PASSTHRU channel, the Remote unit can be left undefined (the default value). As 

soon as the link comes up the connection is made automatically. 

Values: Maximum 16-character string, determined by remote Net- 

Performer setup: A-Z, 0-9, . (period), , (comma (space), - 

(hyphen) 

Default: none 


Class ifwanClassNumber [ifwan#] ClassNumber 

The priority class for data from this port. Classes are defined according to bandwidth 

weight, or you can choose HIGH PRIORITY. Traffic on a high-priority connection is 

processed before other traffic types. High priority data may be desired for 

videoconferencing applications where the available bandwidth is limited. For information 

on how to set the classes so as to prioritize mission-sensitive data, refer to the Quality of 

Service (QoS) module of this document series. 

Values: 1 - 8, HIGH PRIORITY 

Default: 3 

12-10 Memotec Inc.

12.2.9 Remote port number 

12.2.10 Subchanneling 

12.2.11 Subchannel mask 

The remote port to which data from the local port is sent. 



Remote port number ifwanRemotePort [ifwan#] RemotePort 

Values: 1 - 65534 

Default: the local port number 


Subchanneling IfwanSubChanneling [ifwan#] Subchanneling 

For SDM-9220 and SDM-9230 only 

This parameter enables or disables subchanneling on the digital channel. It is only 

available if an SDM-9220 or SDM9230 digital channel is set to the PASSTHRU or HDLC 

protocols. 

Subchanneling involves dividing a digital channel into subchannels that can be 8, 16, 24, 

32, 40, 48 or 56 Kb in size. A timeslot is divided into 8 sections of 8 Kb each (see 

Figure 12-1), then a 64-Kb Subchannel mask determines which sections of the timeslot are 

included in the subchannel. The size of each subchannel is therefore a multiple of 8 Kb. 

NOTE: Subchanneling does not increase the number of channels that can be configured 

on a slot, which remains 24 for T1, and 31 for E1. 

Values: DISABLE, ENABLE 

Default: DISABLE 


Subchannel mask IfwanSubChannelMask [ifwan#] SubChannel- 

Mask 

For SDM-9220 and SDM-9230 only 

A hexadecimal number that indicates which section(s) of a timeslot comprise a 

subchannel. 

Each bit of the Subchannel mask represents an 8-Kb section of the timeslot. A sequence of 

bits set to 1 in the Subchannel mask indicate which contiguous 8-KB sections comprise 

the subchannel, and therefore define the size of the subchannel. See Figure 12-1) for 

examples. 

Memotec Inc. 12-11


Values: 00 - FF 

Default: 00 

Sections: 1 2 3 4 5 6 7 8 

Bit Positions: 

Sections: 1 2 3 4 5 6 7 8 


Port 101: Timeslot 1 (64 Kb) 

Sections: 1 2 3 4 5 6 7 8 


1 1 

4 3 2 1 4 3 2 1 

4 3 2 1 4 3 2 1 

Figure 12-1: Setting the Subchannel Mask 

12-12 Memotec Inc. 

0 

0 

0 0 0 0 

4 3 2 1 4 3 2 1 

16 Kb subchannel comprising timeslot sections 1 and 2. 

Subchannel mask: C0 


0 0 1 1 1 0 0 0 

24 Kb subchannel comprising timeslot sections 3, 4 and 5. 

Subchannel mask: 38 


0 0 0 0 1 1 1 1 

32 Kb subchannel comprising timeslot sections 5, 6, 7 and 8. 

Subchannel mask: 0F

12.3 HDLCOFR Port 

12.3.1 Tx/Rx mode 

12.3.2 PVC number 



Tx/Rx mode ifwanRxTxmode [ifwan#] RxTxmode 

This parameter determines the direction of data transmissions, and can be set to: 

- FULL: The port can both transmit and receive data 

- TX: The port can transmit only 

- RX: The port can receive only 

Values: FULL, TX, RX 

Default: FULL 


PVC number ifwanPvcNumber [ifwan#] PvcNumber 

For X25 and HDLCOFR protocol only. 

This parameter selects the PVC that will be used to transport the HDLC traffic to the 

remote side. The PVC you select must be in TRANSPARENT mode (configured with the 

PVC Mode parameter). Enter the number of the PVC. 

Values: 1 - 300 

Default: 1 

Memotec Inc. 12-13


12.4 PASSTHRU Port 

12.4.1 Congestion flow control 

For PASSTHRU protocol only: 

Determines the congestion flow control notification for this port: 

• AUTO: Congestion flow control is handled automatically by the NetPerformer 

when congestion occurs on the port (due to congestion on the network). This is 

the default value. 

• ON: The NetPerformer sets the congestion bits in the header of the active frame 

when forward or backward data congestion occurs on the port 

- Forward data congestion affects data transmitted from the user equipment to 

the NetPerformer 

- Backward data congestion affects data transmitted from the NetPerformer to 

the user equipment. 

• OFF: The NetPerformer does not set the congestion bits. In this case, no flow 

control takes place even if congestion occurs. 

12.5 PASSTHRUOFR Port 

12.5.1 Dynamic clocking 


Congestion flow control ifwanFlowControl [ifwan#] FlowControl 

Values: AUTO, OFF, ON 

Default: AUTO 


Dynamic clocking ifwanDynamicClocking [ifwan#] DynamicClocking 

When set to YES (the default value), this parameter allows the NetPerformer to adjust the 

clock it provides to the attached equipment. This may be required to compensate for a 

difference between the clocks at different sites. 

When the port is in TX mode, this parameter can be configured, but is not used. 

Values: NO, YES 

Default: YES 

12-14 Memotec Inc.

12.6 T-ASYNC Port 

12.6.1 Format 



Format ifwanFormat [ifwan#] Format 

For ASYNC and COP protocols only. 

Character format. The parameter values are different for the asynchronous (T-ASYNC and 

R-ASYNC) and COP protocols. 

Asynchronous Protocols: The parameter defines the number of data bits per character, 

the parity bit usage, number of stop bits and idle characters. When not specified in the 

parameter value, the number of stop bits is 1. For example, 8N-2STOP configures the port 

for 8 bits, no parity and 2 stop bits. 

Values: (Asynchronous protocols): 8-NONE, 7-NONE, 7-ODD, 7- 

EVEN, 7-SPACE, 7-MARK, 7-IGNORE, 8-EVEN, 8-ODD, 8N- 

2STOP 

Default: 8-NONE 

COP Protocol: The parameter defines the number of bits per character only. 

Values: (COP protocols): 8 BITS, 6 BITS 

Default: 8 BITS 

Memotec Inc. 12-15


12.7 R-ASYNC Port 

12.7.1 Reception flow control 

For R-ASYNC and asynchronous PPP protocols only. 

Flow control on the receiver. This parameter defines the method used by the NetPerformer 

to control the flow of data received from the attached equipment. Flow control is applied 

when the number of characters on input exceeds a predefined threshold. 

12.7.2 Transmission flow control 


Flow control on the transmitter. This parameter defines the method used by the attached 

equipment to control the flow of data transmitted by the NetPerformer. 

12.7.3 Transmit holding time (s) 


Reception flow control ifwanRxFlow [ifwan#] RxFlow 

Values: NONE, XON_XOFF 

Default: NONE 


Transmission flow control ifwanTxFlow [ifwan#] TxFlow 

Values: NONE, XON_XOFF 

Default: NONE 


Transmit holding time (s) ifwanTxHold-s [ifwan#] TxHold-s 


Hold time on the transmitter. This parameter defines the maximum time, in seconds, that 

the transmitter can be blocked due to flow control. There is no hold time limit if this 

parameter is configured as 0 seconds. 

Values: 0 - 2000 

Default: 0 

12-16 Memotec Inc.

12.8 P-SDLC Port 

12.8.1 SDLC duplex mode 

12.8.2 Group poll 

12.8.3 Group address 



SDLC duplex mode ifwanDuplex [ifwan#] Duplex 

Port duplex mode. When set to FULL (full duplex), the SDLC driver can transmit INFO 

frames to a secondary SDLC port while polling another secondary port. Full duplex mode 

may also be used on a secondary SDLC port in host-to-host applications. 

Values: HALF, FULL 

Default: HALF 


Group poll ifwanGroupPoll [ifwan#] GroupPoll 

Group poll enabled or disabled. When this parameter is set to YES, the group poll feature 

is enabled, using the address set with the Group Address parameter, described below. 

When this parameter is set to NO, the group poll feature is disabled. 


Default: NO 


Group address ifwanGroupAddress [ifwan#] GroupAddress 

This parameter defines the group address, used when the group poll feature is enabled (see 

Group Poll parameter, above). 


Default: AE 

Memotec Inc. 12-17


12.8.4 Poll delay (ms) 


Poll delay (ms) ifwanPollDelay-ms [ifwan#] PollDelay-ms 

The wait time, in milliseconds, before transmitting a poll. This parameter is always 

required for a primary SDLC port connected to a controller. It may also be used on a 

secondary SDLC port that is set to full duplex mode in host-to-host applications. 

Values: 0 - 1000 

Default: 10 

12-18 Memotec Inc.

12.9 COP Port 

12.9.1 Synchronization character 


For COP protocol only. 

The hexadecimal value of the synchronization character. The Synchronization Character 

must be different from the Idle that has been defined for the COP port, or synchronization 

cannot be achieved. For example, if the Synchronization Character is 0000 then the Idle 

parameter cannot be set to SPACE. If the Synchronization Character is set to FFFF, then 

the Idle must be set to SPACE to get the port working. The following table summarizes 

these requirements: 

12.9.2 Number of desynch. character 

s 


This parameter defines the number of contiguous desynchronization characters that must 

be received before the NetPerformer drops synchronization and closes the frame. 

12.9.3 Desynchronization character 


Synchronization character 

Idle Synchronization Character 

SPACE Any value different from 0000 

MARK Any value different from FFFF 

Values: 0000 - FFFF 

Default: 1616 

ifwanSync [ifwan#] Sync 


Number of desynch. 

characters 

Values: 1 - 100 

Default: 3 

ifwanDropSyncCoun-ter ifwan#] 

DropSyncCounter 


Desynchronization character 

ifwanDropSyncCharacter ifwan#] Drop- SyncCharacter 


The hexadecimal value of the desynchronization character. This parameter defines the 

Memotec Inc. 12-19


value of the desynchronization character in hexadecimal. To facilitate the 

desynchronization process the Desynchronization Character must be the same as the Idle 

set on the COP port. For example, to desynchronize on 00 the Idle parameter must be set 

to SPACE on the port. To desynchronize on FF the Idle must be set to MARK. The 

following table summarizes these requirements: 

Idle Desynchronization Character 

SPACE 00 

MARK FF 


Default: FF 

12-20 Memotec Inc.

12.10 X25 Port 

12.10.1 X25 frame relay encapsulation 



X25 frame relay encapsulation 

ifwanX25Encapsulation [ifwan#] 

X25Encapsulation 

For X25 protocol only. 

Defines how the X.25 traffic will be handled by the NetPerformer HDLC driver. In 

particular, it specifies which encapsulation technique is used to get the X.25 traffic 

through the Frame Relay network: 

• ANNEX-F: FRF.3 Annex F deals with multiprotocol support over Frame Relay. 

With Annex-F encapsulation, a frame identifier header is added to the normal 

frame to differentiate the various protocols. In the case of X.25, this identifier 

consists of a 6-byte suite. When an X.25 frame is received by the NetPerformer 

HDLC driver, it is stripped of its leading and trailing flags, as well as its CRC. 

Then a Frame-Relay header (2 bytes of DLCI) and a 6-byte frame identifier is 

added to the X.25 frame before transmission. The X.25 frame is integrally copied 

into a Frame Relay frame (LAPB header and data). All types of frames (INFO, 

UI, SUPERVISOR) are copied in the same way. 

• ANNEX-G: FRF.3 Annex F deals with CCITT X.25 encapsulation over Frame- 

Relay. With Annex-G encapsulation, an X.25 frame received by the NetPerformer 

HDLC driver is stripped of its leading and trailing flags, as well as its 

CRC. It is then integrally copied into a Frame Relay frame. All frame types that 

are received on the HDLC port (INFO, UI, SUPERVISOR) are encapsulated. 

Values: ANNEX-F, ANNEX-G 

Default: ANNEX-G 

Memotec Inc. 12-21


12-22 Memotec Inc.

SE/PU Configuration Parameters 

13 

Memotec Inc. 13-1


13.1 SDLC-SDLC Mode 

13.1.1 PU number 

13.1.2 Operating mode 


PU number puEntry, puIndex [pu#] 

Enter the PU number on the console command line. For SNMP, select the puEntry table 

and look under the puIndex for the desired PU. 

Once you select a PU, the PU number is displayed thereafter at the beginning of each line 

from the console. 

Values: 1 - 64 

Default: 1 


Operating mode puMode [pu#] Mode 

This parameter determines the PU operating mode. In determining the operating mode, 

keep in mind that each active controller is logically attached to two interfaces. These 

interfaces may be: 

• SDLC: SNA/SDLC port (either primary or secondary), 

• LLC: LAN interface, available only when a LAN expansion card is installed, 

• LINKS: WAN port, 

• BNN: Boundary Node Network connection (Routed SNA Over Frame Relay), 

• BAN: Boundary Access Network connection (Bridged SNA Over Frame Relay) 

The PU operating mode is determined from these two logical connections. For example, a 

PU configured with the SDLC-LLC operating mode is logically attached to an SDLC port 

and a LAN interface. 

NOTE: For the SDLC-SDLC mode, the logical connections require one primary 

SNA/SDLC port (configured with the P-SDLC protocol), and one secondary 

SNA/SDLC port (configured with the S-SDLC protocol). 

If you leave this parameter at the OFF value, the PU is not used and no other PU 

parameters can be configured. 

13-2 Memotec Inc.

13.1.3 Controller active 


Values: OFF, SDLC-LLC, SDLC-SDLC, SDLC-LINKS, LLC-LINKS, 

SDLC-BAN, SDLC-BNN, LLC-BAN, LLC-BNN, BAN-LINKS, 

BNN-LINKS 

Default: OFF 

The next two parameters are requested for all PU operating modes. 


Controller active puActive [pu#] Active 

For all PU modes. 

Sets the activation status of the PU, that is, the preferred PU state (active or inactive). For 

example, changing this parameter from NO to YES will force activation of the PU. 

13.1.4 Delay before connection 

NOTE: We recommend that you set all other PU parameters before setting the activation 

status of the PU to YES. 


Default: NO 


Delay before connection puDelayBeforeConn-s [pu#] DelayBefore-Conns 

For all PU modes. 

This parameter sets the maximum length of time, in seconds, allowed to establish the PU 

connection or change from one connection status to another. 

Values: 1 - 1000 

Default: 60 

Memotec Inc. 13-3


13.1.5 SDLC primary port 

Primary SNA/SDLC port (configured with the P-SDLC protocol) to which the PU is 

attached. 

13.1.6 SDLC primary address 

SDLC address for the PU on the primary side of the connection. Two hexadecimal digits 

must be selected. 

To support PU Type 4, where 2 FEPs are connected via an SDLC line, the SDLC 

addressing is different from that of normal SDLC operation. In particular, all PUs in 

primary and secondary mode must be configured with address FF. When a SIM/RIM 

frame is received from the SDLC side or the PVCR side, the PU will go into transparent 

mode. From this point on, all frames received on the SDLC port will be sent out 

transparently to the remote. When an XID or SNRM is detected on the SDLC port, the PU 

exits transparent mode and re-enters emulation mode. Note that with PU Type 4, the 

NetPerformer can perform NCP download using FEP-to-FEP connections. 

13.1.7 SDLC secondary port 


SDLC primary port puSdlcPort [pu#] SdlcPort 

Values: numeric range of values determined by the number of ports 

on the NetPerformer 

Default: 1 


SDLC primary address puSdlcAddress [pu#] SdlcAddress 


Default: the local PU number, in hexadecimal 


SDLC secondary port puSdlcPort2 [pu#] SdlcPort 

Secondary port (configured with the S-SDLC protocol) to which the PU is attached. 



Default: 1 

13-4 Memotec Inc.

13.1.8 SDLC secondary address 


SDLC address for the PU on the secondary side of the connection. Two hexadecimal digits 










13.1.9 SDLC retransmission timeout (ms) 


SDLC secondary address puSdlcAddress2 [pu#] SdlcAddress 




SDLC retransmission 

timeout (ms) 

For all PU modes with an SDLC connection. 

Wait for reply timeout before retransmitting a frame. This timeout is defined in 

milliseconds. 

Values: 100 - 30000 

Default: 3000 

13.1.10 SDLC number of retransmission retries 

puSdlcTimeout-ms [pu#] SdlcTimeout-ms 


SDLC number of retransmission 

retries 

puSdlcRetry [pu#] SdlcRetry 


Maximum number of successive retries on the SDLC side of the connection before the PU 

is declared inoperative. 

Values: 1 - 1000 

Default: 10 

Memotec Inc. 13-5


13.1.11 SDLC transmission window size 

13.1.12 XID support 


SDLC transmission window 

size 

puSdlcWindow [pu#] SdlcWindow 


Transmission window size. 

Values: 1 - 7 

Default: 7 


XID support puXid [pu#] Xid 

For SDLC-SDLC and SDLC-LINKS modes only. 

PU exchanges identification. This parameter determines whether the PU expects to 

exchange PU identification with the device it is connected to, and ensures the identity of 

the remote PU in SNA applications. Set to NO if the PU does not support XID. 


Default: YES 

13.1.13 Suppress DM upon disconnection 


Suppress DM upon disconnection 

puSuppdDmDisc [pu#] SuppdDmDisc 

For PUs associated with secondary SDLC (S-SDLC) ports. 

This parameter controls the transmission of a Disconnect Message (DM) frame. A DM is a 

Disconnect Message sent from the secondary station (controller) to the primary station 

(host). It tells the primary that the secondary is in disconnect mode. 

When set to YES, a DM frame is suppressed rather than transmitted. This prevents the S- 

SDLC PU from replying to a frame from the primary PU with a DM frame. This setting 

may be useful for a PU4-to-PU4 connection when the configuration is downloaded using 

SIM (Set Initialize Mode) messages. 

When set to NO, the PU processes Disconnect Messages like a regular SDLC PU. 


Default: NO 

13-6 Memotec Inc.

13.2 SDLC-LINKS Mode 

13.2.1 SDLC port 

13.2.2 SDLC address 

13.2.3 SDLC frame size 



SDLC port puSdlcPort [pu#] SdlcPort 

The SNA/SDLC port to which the PU is attached. This may be a primary (P-SDLC) or a 

secondary (S-SDLC) SNA/SDLC port. 



Default: 1 


SDLC address puSdlcAddress [pu#] SdlcAddress 

SDLC address for the PU on the SDLC side of the connection. Two hexadecimal digits 













SDLC frame size puSdlcMaxFrame [pu#] SdlcMaxFrame 

Maximum frame size on the SDLC side of the connection, excluding SNA headers. 

For an SDLC-LLC connection, if the value of this parameter is equal to that of the LLC 

Frame Size parameter (described later in this section), then no frame splitting will occur. 

On the other hand, if the value of this parameter is different from that of the LLC Frame 

Size parameter, the NetPerformer will split the frames according to the smaller Frame Size 

value. 

Memotec Inc. 13-7


13.2.4 Remote unit 

13.2.5 Class 

13.2.6 Remote PU number 

Values: 128, 256, 512, 1024, 2048, 4096, 8192 

Default: 512 

The remaining parameters for configuring a PU in SDLC-LINKS mode affect the LINKS 

side of the connection: 


Remote unit puLinkRemoteUnit [pu#] LinkRemoteUnit 

For all PU modes with a LINKS connection. 

Remote unit to which data from this PU should be directed. The unit name is defined on 

the remote unit using the Setup Global menu. A unit name must be defined for each 

NetPerformer that will be participating in the network. Refer to the chapter Global 

Functions in the Quick Configuration module of this document series. 

Values: Maximum 16-character string, determined by remote NetPerformer 

setup 

Default: none 


Class puLinkClassNumber [pu#] ClassNumber 


The priority class for data from this PU. Classes are defined according to bandwidth 

weight. For details, refer to the Quality of Service (QoS) module of this document 

series. 

Values: 1 - 8, HIGH PRIORITY 

Default: 2 


Remote PU number puLinkRemPu [pu#] LinkRemPu 


The remote PU to which data from the local PU is sent. Specify the remote PU number. 


Default: the local PU number 

13-8 Memotec Inc.

13.3 SDLC-LLC Mode 

13.3.1 LLC lan port 


For SDM-9220 and SDM-9230 only for all PU modes with an LLC connection. 

This parameter defines the LAN port to be used on the LLC side. 

13.3.2 LLC destination address 

13.3.3 LLC source SAP 


LLC lan port puLanPort [pu#] LanPort 

Values: EITH1, EITH2 

Default: ETH1 


LLC destination address puLlcDa [pu#] LlcDa 

For all PU modes with an LLC connection. 

Destination address of the device to be reached on the LAN. This address is defined using 

12 hexadecimal digits (6 bytes). 

Values: 000000000000 - FFFFFFFFFFFF 

Default: 000000000000 


LLC source SAP puLlcSsap [pu#] LlcSsap 


Source SAP (Service Access Point) used by the NetPerformer for this PU. 

For an LLC Host application (LLC side acts as primary unit), the NetPerformer can handle 

multiple PUs over the same pair of network addresses: the host LAN Destination Address 

and the MAC Address of the NetPerformer. To distinguish the PUs attached to the same 

host, you must set the LLC Source SAP parameter to a different value for each PU. Valid 

values are multiples of 4, from 04 to DC. This parameter must also be set in the host 

configuration. 

For an LLC Controller application (LLC side acts as secondary unit), this parameter 

should be set to the default SNA SAP, that is, 04. 

Memotec Inc. 13-9


13.3.4 LLC destination SAP 

NOTE: When the other side of the PU logical connection is non-SDLC (the LLC- 

LINKS mode) set the LLC side as primary or secondary using the Role 

parameter, explained at the end of this section. 

Values: 04, 08, 0C, 10, 14, 18, … D8, DC 

Default: 04 


Destination SAP that will be used by the remote LAN device for this PU. Valid values are 

multiples of 4, from 04 to DC. Usually, the SNA destination SAP is 04. 

13.3.5 LLC retransmission timeout (ms) 


LLC destination SAP puLlcDsap [pu#] LlcDsap 

a 

Values: 04, 08, 0C, 10, 14, 18, … D8, DC 

Default: 04 


LLC retransmission timeout 

(ms) 

puLlcTimeout-ms [pu#] LlcTimeout-ms 



milliseconds. 

Values: 1000 - 30000 

Default: 3000 

13-10 Memotec Inc.

13.3.6 LLC maximum successive retries 



Maximum number of successive retries on the LLC side of the connection before the PU is 

declared inoperative. 

13.3.7 LLC transmission window size 

13.3.8 LLC dynamic window 


LLC maximum successive 

retries 

Values: 1 - 1000 

Default: 10 

puLlcRetry [pu#] LlcRetry 


LLC transmission window 

size 

puLlcWindow [pu#] LlcWindow 


Maximum transmission window size on the LAN. The dynamic window algorithm 

increases the window size by one each time the number of frames defined by the LLC 

Dynamic Window parameter (see below) has been acknowledged without a 

retransmission, until the maximum value defined by the LLC Window parameter has been 

reached. The window size is reset to 1 when a retransmission occurs. 


Default: 7 

Console 

SNMP Text-based Config 

LLC dynamic window puLlcDynamicWindow [pu#] LlcDynamicWindow 


Number of information frames that are consecutively acknowledged without a 

retransmission before the window size will be incremented by one. This parameter is used 

for the dynamic window algorithm, in conjunction with the LLC Window parameter 

(explained above). 

Values: 1 - 1000 

Default: 10 

Memotec Inc. 13-11


13.3.9 LLC frame size 

13.3.10 XID support 


LLC frame size puLlcMaxFrame [pu#] LlcMaxFrame 


Maximum frame size on the LLC side of the connection, excluding LLC and SNA 

headers. 

For an SDLC-LLC connection, if the value of this parameter is equal to that of the SDLC 

Frame Size parameter (listed earlier), then no frame splitting will occur. On the other 

hand, if the value of this parameter is different from that of the SDLC Frame Size 

parameter, the NetPerformer will split the frames according to the smaller Frame Size 

value. 

Values: 128, 256, 512, 1024 

Default: 512 


XID support puXid [pu#] Xid 

For all PU modes with an LLC, BAN or BNN connection. 

PU exchanges identification. This parameter determines whether the PU expects to 

exchange PU identification with the device it is connected to, and ensures the identity of 

the remote PU in SNA applications. When set to AUTO, the NetPerformer can get the PU 

ID automatically via the XID request, and pass it to the host side before completing the 

connection. 

If the PU does not support the XID request, you must set this parameter to MANUAL. In 

this case, you will have to set the XID manually by completing the XID fields if the host 

requests this information. 

NOTE: This parameter is slightly different from the XID Support parameter mentioned 

earlier (for configuration of an SDLC connection), where the manual 

setting is not available. 

Values: AUTO, MANUAL 

Default: AUTO 

13-12 Memotec Inc.


The next three parameters are displayed only if you choose the MANUAL setting for the 

XID Support parameter, as shown below: 

13.3.11 XID identification number 

13.3.12 XID format 

PU 1> XID support (def:AUTO) ? MANUAL 

PU 1> XID identification number (def:00000000) ? 

PU 1> XID format (def:0) ? ? 

PU 1> XID format (0/1,def:0) ? 

PU 1> XID PU type (def:1) ? ? 

PU 1> XID PU type (1/2,def:1) ? 


XID identification number puXidId [pu#] XidId 


This parameter contains the ID block (IDBLK) and ID number (IDNUM) of the PU. The 

first 3 digits comprise the IDBLK, and the last 5 digits comprise the IDNUM. 

NOTE: This parameter is not displayed if you are using the AUTO setting for the XID 

Support parameter. 

Values: 00000000 - FFFFFFFF 

Default: 00000000 


XID format puXidFormat [pu#] XidFormat 


This parameter determines the XID format type. Only types 0 and 1 are supported at this 

time. Type 0 is used by older IBM controllers: the IBM 3274 and some of the old 3174, 

5294 and 5394 models. Type 1 is used by the newer models. 



Values: 0, 1 

Default: 0 

Memotec Inc. 13-13


13.3.13 XID PU type 


XID PU type puXidPuType [pu#] XidPuType 


The PU type that is possible in the XID. PU types 1 and 2 are supported. If your PU is type 

2.1 or Type 4, use the AUTO setting of the XID Support parameter, described earlier. 



Values: 1, 2 

Default: 1 

13-14 Memotec Inc.

13.4 SDLC-BAN Mode 

13.4.1 BAN destination address 


For all PU modes with a BAN connection. 

Destination address of the device to be reached on the BAN connection. This address is 

defined using 12 hexadecimal digits (6 bytes). 

13.4.2 BAN/BNN source SAP 

For all PU modes with a BAN or BNN connection. 

Source SAP (Service Access Point) used by the NetPerformer for this side of the PU. 

For a BAN Host application (BAN side acts as secondary unit), the NetPerformer can 

handle multiple PUs attached to the same host. For this application you must set the BAN/ 

BNN Source SAP parameter to a different value for each PU. Valid values are multiples of 

4, from 04 to DC. 

For a BAN Controller application (BAN side acts as primary unit), this parameter should 

be set to the default SNA SAP, that is, 04. 

13.4.3 BAN/BNN destination SAP 


BAN destination address puBanDa [pu#] BanDa 

Values: 000000000000 - FFFFFFFFFFFF 

Default: 000000000000 


BAN/BNN source SAP puBanBnnSsap [pu#] BanBnnSsap 

NOTE: For LLC-BAN mode, the role of the BAN side (primary or secondary) is 

opposite to the value of the LLC Role parameter. 

Values: 04, 08, 0C, 10, 14, 18, … D8, DC 

Default: 04 


BAN/BNN destination 

SAP 


puBanBnnDsap [pu#] BanBnnDsap 

Memotec Inc. 13-15


Destination SAP that will be used by the remote BAN device for this PU. Valid values are 

multiples of 4, from 04 to DC. Usually, the SNA destination SAP is 04. 

Values: 04, 08, 0C, 10, 14, 18, … D8, DC 

Default: 04 

13.4.4 BAN/BNN retransmission timeout (ms) 

Figure 13-1: 


BAN/BNN retransmission 

timeout (ms) 



milliseconds. 

Values: 1000 - 30000 

Default: 3000 

13.4.5 BAN/BNN maximum successive retries 

puBanBnnTimeout-ms [pu#] BanBnnTimeout-ms 


BAN/BNN maximum successive 

retries 

puBanBnnRetry [pu#] BanBnnRetry 


Maximum number of successive retries on the BAN side of the connection before the PU 

is declared inoperative. 

Values: 1 - 1000 

Default: 10 

13-16 Memotec Inc.

13.4.6 BAN/BNN transmission window size 



Maximum transmission window size on the BAN or BNN connection. The dynamic 

window algorithm increases the window size by one each time the number of frames 

defined by the BAN/BNN Dynamic Window parameter (see below) has been 

acknowledged without a retransmission, until the maximum value defined by the BAN/ 

BNN Window parameter has been reached. The window size is reset to 1 when a 

retransmission occurs. 

13.4.7 BAN/BNN dynamic window 


BAN/BNN transmission 

window size 


Default: 7 

puBanBnnWindow [pu#] BanBnnWindow 


BAN/BNN dynamic window 

puBanBnnNw [pu#] BanBnnNw 


Number of information frames that are consecutively acknowledged without a 

retransmission before the window size will be incremented by one. This parameter is used 

for the dynamic window algorithm, in conjunction with the BAN/BNN Window 

parameter (explained above). 

Values: 1 - 1000 

Default: 10 

Memotec Inc. 13-17


13.4.8 BAN/BNN frame size 

13.4.9 BAN routing 


BAN/BNN frame size puBanBnnMaxFrame [pu#] BanBnnMaxFrame 


Maximum frame size on the BAN or BNN side of the connection, excluding BAN/BNN 

and SNA headers. 

For an SDLC-BAN connection, if the value of this parameter is equal to that of the SDLC 

Frame Size parameter (listed earlier), then no frame splitting will occur. On the other 

hand, if the value of this parameter is different from that of the SDLC Frame Size 

parameter, the NetPerformer will split the frames according to the smaller Frame Size 

value. The same is true of an LLC-BAN connection, where the value of LLC Frame Size 

is compared to that of the BAN/BNN Frame Size parameter. 

Values: 128, 256, 512, 1024, 2048, 4096, 8192 

Default: 512 


BAN routing puBanRouting [pu#] BanRouting 

For all PU modes with a BAN connection. 

This parameter defines the type of routing required to access the remote station. Select 

SOURCE for source routing, or TRANSPARENT for transparent routing. For SOURCE, 

the NetPerformer responds to a Single Route Broadcast with a Specific Route, using the 

route received with the frame. SOURCE-A is an alternate form of the source routing 

protocol, where the unit responds to a Single Route Broadcast with an All Routes 

Broadcast. 

NOTE: Use SOURCE when communicating with an IBM processor such as an IBM 

3745, or with a Bay Networks router. When communicating with a Token- 

Ring bridge network, use either SOURCE or SOURCE-A. 

Values: TRANSPARENT, SOURCE, SOURCE-A 

Default: SOURCE 

13-18 Memotec Inc.

13.5 SDLC-BNN Mode 

13.5.1 BNN PVC number 

13.5.2 BNN FID type 



BNN PVC number puBnnPvc [pu#] BnnPvc 

For all PU modes with a BNN connection. 

The number of the remote PVC to which data from this PU will be sent. 

Values: 1 - 300 

Default: 1 


BNN FID type puBnnFid [pu#] BnnFid 

For all PU modes with a BNN connection. 

The type of Format Identification field (FID) for this PU. The following FID types are 

supported: 

• FID2: SNA - Peripheral (FID2) 

• FID4: SNA - Subarea (FID4) 

• APPN: SNA - APPN (FID2) 

Values: FID2, FID4, APPN 

Default: FID2 

Memotec Inc. 13-19


13.6 Non-SDLC PU Connection 

13.6.1 LLC Role / BAN/BNN Role 

LLC Role, 

BAN/BNN Role 


puRole [pu#] Role 

For non-SDLC modes only. 

For PUs with an LLC connection the parameter is displayed as LLC Role. This parameter 

indicates whether the LLC side acts as a primary (facing the controller) or secondary 

(facing the host) unit. The NetPerformer automatically defines the other side with the 

opposite value. 

For PUs with a BAN or BNN connection the parameter is displayed as BAN/BNN Role. 

This parameter indicates whether the BAN/BNN side acts as a primary or secondary unit. 

The NetPerformer automatically defines the other side with the opposite value. 

Values: SEC, PRI 

Default: SEC 

13-20 Memotec Inc.

SE/IPX Configuration Parameters 

14 

Memotec Inc. 14-1


14.1 IPX Parameters on the Ethernet Por or WAN Connection 

14.1.1 IPX RIP 

14.1.2 IPX SAP 


IPX RIP iflanIpxRip 

ifwanIpxRip 

pvcIpxRip 

Enables or disables RIP for Internetwork Packet Exchange (IPX) frames. Configure the 

port 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 port. When IPX RIP is disabled the NetPerformer 

cannot transmit an IPX RIP frame, and discards all IPX RIP frames received. 

NOTE: If you set this parameter to ENABLE you must also configure the IPX Network 

Number and, on an Ethernet port, the IPX Encapsulation parameter, 

described below. 



[iflan#] IpxRip 

[ifwan#] IpxRip 

[pvc#] IpxRip 


IPX SAP iflanIpxSap 

ifwanIpxSap 

pvcIpxSap 

[iflan#] IpxSap 

[ifwan#] IpxSap 

[pvc#] IpxSap 

Enables or disables the Service Advertising Protocol (SAP) for IPX frames. IPX SAP 

frames are exchanged between routers to indicate the nature and location of services 

available on a Novell network. Configure the port 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. 

NOTE: If you set this parameter to ENABLE you must also configure the IPX Network 

Number and, on an Ethernet port, the IPX Encapsulation parameter, 

described below. 

14-2 Memotec Inc.

14.1.3 IPX network number 

14.1.4 IPX encapsulation 





IPX network number iflanIpxNetNum 

ifwanIpxNetNum 

pvcIpxNetNum 

[iflan#] IpxNetNum 

[ifwan#] IpxNetNum 

[pvc#] IpxNetNum 

The network number of the IPX node that is connected to the port. 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 Configuring an 

IPX Connection on page 3. 


Default: 00000000 


IPX encapsulation iflanIpxLanType [iflan#] IpxLanType 

For an Ethernet port only. 

The frame type used on the Ethernet LAN to encapsulate IPX frames. The following 

parameter values are available: 

• ETH 802.2: Specifies Ethernet (802.3) frames using an 802.2 envelope. The 

DSAP and SSAP values indicate that the packets contain IPX frames. 

• ETH SNAP: Specifies Ethernet (802.3) frames using an 802.2 envelope with 

SNAP (protocol ID). The DSAP and SSAP values indicate SNAP encapsulation, 

and the protocol ID indicates the presence of an IPX frame. 

• ETH 802.3: Specifies raw IPX encapsulation of Ethernet (802.3) frames. This 

frame format cannot be used with IPX checksums. 

• ETH II: Specifies Ethernet (802.3) frames using a DEC Ethernet II envelope. 

Values: ETH 802.2, ETH SNAP, ETH 802.3, ETH II 

Default: ETH 802.2 

Memotec Inc. 14-3


14.2 SE/IPX/GLOBAL Parameters 

14.2.1 Router 

This parameter enables or disables all IPX functions and commands on the NetPerformer. 

When the Router parameter is enabled, the NetPerformer behaves like an IPX router, and 

will respond to IPX commands. When this parameter is disabled, the NetPerformer 

ignores all IPX commands received. 

14.2.2 Internal network number 


Router ipxRouterEnable [ipx] RouterEnable 




Internal network number ipxInternalNetNum [ipx] InternalNetNum 

This parameter defines the IPX network number to be used for direct links that do not have 

a configured IPX address (unnumbered links). Unnumbered links include direct PVCR 

links with the IPX network number set to 00000000, and connections made via the 

Firewire (backplane) of a Central Site Unit. The IPX Internal Network Number is a 4-byte 

value in hexadecimal representation. 

When the IPX network number on PVCR or LAN ports 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. 


Default: 00000000 

For example, in the following diagram the PVCR port’s IPX Network Number parameter 

is set to 00000000. The Firewire ports do not have a configurable IPX network number 

parameter. 

14-4 Memotec Inc.

Net1 

Ethernet 

RT1 

PVCR or FW 


Figure 14-1: PVCR port’s IPX Network Number set to 00000000 

In this example, IPX type 20 frames would normally be filtered out by the WAN. 

However, if an internal IPX address is configured, these frames can be transmitted from 

Net1 to Net2 and vice versa. To do this, configure the NetPerformers with the following 

IPX internal network numbers: 

• RT1: 00000001 

• RT2: 00000002 

For an application with several interconnected links, the best way to configure the IPX 

internal network numbers is to define them only on those NetPerformers that must be 

crossed over for correct operation of the Novell network. 

Figure 14-2: 

In the example above, if all servers and stations that communicate over the Novell 

network are located on Net3 and Net4, the values of the IPX Internal Network Number 

parameter could be the following: 

• RT1: 00000000 

• RT2: 00000000 

Memotec Inc. 14-5 

RT2 

11111111 00000000 00000000 22222222 

Net1 

Ethernet 

Net3 

Ethernet 

RT1 

RT3 

IPX Network Numbers 

RT2 

RT4 

Net2 

Ethernet 

Net2 

Ethernet 

Net4 

Ethernet


• RT3: 12345678 

• RT4: 87654321 

This configuration is particularly useful for limiting the number of frames generated by 

the interconnected links. A type 20 IPX frame entering at Net4 is duplicated on the other 

three links of RT4. This is the case for each router that has an internal address. As a result, 

instead of having one frame on output at Net3, there could be as many as 7 frames if all 

four routers have an internal address. One frame would be generated for each possible 

path that passes over the same router no more than once (Exception: the router from which 

the frame came, RT4, can be selected twice since the initial frame transmission is not 

counted). 

14-6 Memotec Inc.

14.3 SE/IPX/FILTER Parameters 

14.3.1 IPX Filter entry number 

14.3.2 Enable 

14.3.3 SAP 



IPX Filter entry number ipxfilterEntry, ipxfilterIndex 

Enter the number of the filter you want to configure on the console command line. Once 

you select an IPX filter, its number is displayed thereafter at the beginning of each line 

from the console. 


Default: 1 

Determines the current state of the IPX filter (enabled or disabled). If this parameter is 

enabled, the unit will filter IPX SAP entries for the SAP given in the next parameter. 

Defines the SAP value to be filtered. 

[ipxfilter#] 


Enable ipxfilterEnable [ipxfilter#] Enable 




SAP ipxfilterSap [ipxfilter#] Sap 

Values: 0000 - FFFF 

Default: 0000 

Memotec Inc. 14-7


14.3.4 Type 


Type ipxfilterType [ipxfilter#] Type 

Defines how the IPX filter should be applied. Select STANDARD to filter out the SAP 

value defined by the SAP parameter. Select REVERSE to filter out all SAP values except 

the one defined by the SAP parameter. 

Values: STANDARD, REVERSE 

Default: STANDARD 

14-8 Memotec Inc.

IPX Display Command Statistics 

15 

Memotec Inc. 15-1


15.1 IPX Statistics 

15.1.1 DR/IPX/RIP 

15.1.2 NETWORK NUMBER 

15.1.3 TICKS 

15.1.4 HOP COUNT 

15.1.5 NEXT HOP 

15.1.6 AGE 

Console SNMP 

NETWORK NUMBER (use private Novell MIB) 

This entry provides the network number of the destination IPX network. It is a 4-byte 

value in hexadecimal representation. If this number is displayed as 00000000, the 

destination can be assumed to be on the same LAN segment as the source network. 

Console SNMP 

TICKS (use private Novell MIB) 

The relative length of time required to reach the destination IPX network. This time is 

indicated in ticks, representing the speed of packet transmission across the link when 

current throughput levels and delays are taken into account. Where more than one route is 

available to a given destination, the NetPerformer uses the route with the lowest number 

of ticks. If the tick values are equal, it uses the route with the lowest hop count (see next 

entry). 

Console SNMP 

HOP COUNT (use private Novell MIB) 

The number of NetPerformers and other routers that must be passed over to reach the 

destination indicated by the network number entry. 

Console SNMP 

NEXT HOP (use private Novell MIB) 

The next router to be reached on the path to the final destination. The next hop is identified 

by its 4-byte hexadecimal network number. 

Console SNMP 

AGE (use private Novell MIB) 

15-2 Memotec Inc.

15.1.7 DR/IPX/SAP 

15.1.8 NET NUM 

15.1.9 NODE 

15.1.10 SOCKET 


This statistic provides the aging time since this destination was entered on the routing 

table. For a valid connection the aging time is incremented until an update is received for 

this entry. It will be displayed in seconds (s), minutes (m), hours (h), days (d) or years (y), 

depending on how long the entry has been in the table. 

If a destination is reached through a direct connection, its AGE value will remain at 0 

seconds, and will increase only when the port is closed. For an invalid connection 

(VALID = NO), the AGE value will increment for 120 seconds, at which time it is removed 

from the routing table. 

Console SNMP 

NET NUM (use private Novell MIB) 

The network number of the network on which the server resides, in 4-byte hexadecimal 

format. 

Console SNMP 

NODE (use private Novell MIB) 

The physical address of the node on which the server resides. This address is up to 6 bytes 

long in hexadecimal format. 

Console SNMP 

SOCKET (use private Novell MIB) 

The hexadecimal socket number used to route service requests to a particular process on 

the server. Commonly used socket numbers are the following: 

Socket Number Process 

0451 NetWare Core Protocol (NCP) process 

0452 SAP process 

0453 RIP process 

0455 NetBIOS process 

0456 Diagnostics process 

Memotec Inc. 15-3


15.1.11 SERVICE NAME 

15.1.12 TYPE 

15.1.13 HOP COUNT 

Socket Number Process 

4000 - 7FFF Dynamic interaction with file servers 

and other network communications 

8000 - FFFF Reserved by Novell 

Console SNMP 

SERVICE NAME (use private Novell MIB) 

The name of the service, up to 48 characters in length. In combination with the service 

type (see next entry), this name uniquely identifies the server in the Internetwork. 

Console SNMP 

TYPE (use private Novell MIB) 

The type of service provided by the server, given in hexadecimal format. Commonly used 

service types are: 

Type Service 

0000 Unknown 

0003 Print Queue 

0004 File Server 

0005 Job Server 

0007 Print Server 

0009 Archive Server 

0024 Remote Bridge Server 

0047 Advertising Print Server 

8000 - FFFF Reserved by Novell 

Console SNMP 

HOP COUNT (use private Novell MIB) 

The number of NetPerformers and other routers that must be passed over to reach the 

server indicated by the network number (NET NUM) and node entries. 

15-4 Memotec Inc.

15.1.14 AGE 

Console SNMP 

AGE (use private Novell MIB) 


This statistic provides the aging time since this destination was entered on the routing 

table. For a valid connection the aging time is incremented until an update is received for 

this entry. It will be displayed in seconds (s), minutes (m), hours (h), days (d) or years (y), 

depending on how long the entry has been in the table. 

If a destination is reached through a direct connection, its AGE value will remain at 0 

seconds, and will increase only when the port is closed. For an invalid connection (VALID 

= NO), the AGE value will increment for 120 seconds, at which time it is removed from 

the routing table. 

Memotec Inc. 15-5


15-6 Memotec Inc.

Index 

A 

Activation status 

of PU 13-3 

Active PUs 

verifying 11-12 

AGE 

displaying for IPX routing table 15-2, 15-5 

Applications 6-2 

X.25 encapsulation to Frame Relay 9-5 

ASYNC driver 5-2 

B 

BAN 6-14 

BAN destination address 13-15 

BAN routing 13-18 

BAN support 6-5 

advantages 6-5 

BAN/BNN 

centralized router operation 6-6 

network topologies 6-5 

single switch conversion 6-6 

BAN/BNN destination SAP 13-15 

BAN/BNN dynamic window 13-17 

BAN/BNN frame size 13-18 

BAN/BNN maximum successive retries 13-16 

BAN/BNN retransmission timeout 13-16 

BAN/BNN Role 13-20 

BAN/BNN source SAP 13-15 

BAN/BNN transmission window size 13-17 

Bit coding 12-9 

BNN 6-14 

BNN FID type 13-19 

BNN PVC number 13-19 

BNN support 6-4 


Bridged SNA Over Frame Relay 6-5 

BSC driver 7-2 

C 

Centralized router operation 6-6 


Character format 12-15 

Class 13-8 

for PUs 13-8 

Class parameter 12-10 

Clock source selection 12-3 

Clocking mode 12-3 

Concentration 6-4 

Configuration 

IPX parameters 10-4 

port parameters 6-8 

PU parameters 6-11 

Congestion flow control 12-14 

Controller active 

for PU 13-3 

Controllers 

configuration 6-2 

Conversion 6-4 

LLC 6-4 

COP driver 8-2 

CRC encoding 12-9 

Legacy Data 1 

D 

DCD signal 

operating mode 12-7 

Delay Before Connection 13-3 

Delay before connection 

for PU 13-3 

Destination 

defining 13-8 

Destination Address 

LLC 13-9 

Destination address 

for PU 13-9 

Destination address for BAN connection 13-15 

Destination SAP 

of PU 13-10 

Destination SAP for BAN/BNN connection 13-16 

Destinations 

age 15-3, 15-5 

Desynchronization character 12-19 

Dynamic clocking 

on PASSTHRUOFR port 12-14 

Dynamic window algorithm 13-11 

Dynamic window for BAN/BNN connection 13-17 

E 

EBCDIC transmission code 7-2 

Enable IPX filter 14-7 

Encapsulation, IPX 14-3 

Ethernet port 

IPX Encapsulation 14-3 

IPX network number 14-3 

IPX RIP 14-2

IPX SAP 14-2 

Exchange PU identification 13-6, 13-12 

F 

Fallback 

disabling 12-5 

Fallback speed 12-5 

FID type for BNN connection 13-19 

Flow control 

on asynchronous port 12-16 

Format parameter 12-15 

Frame delay (ms) 12-9 

Frame Relay 6-5 

Frame size for BAN/BNN connection 13-18 

Frame splitting 13-7, 13-12 

Frame transmission 12-8 

G 

Group address 12-17 

Group poll 12-17 

H 

HDLC 

on digital channel 1-6 

HDLC driver 1-2 

HOP COUNT 

displaying for IPX routing table 15-2, 15-4 

Host configuration 13-9 

I 

ID block 

of PU 13-13 

ID number 

of PU 13-13 

IDBLK 13-13 

Idle parameter 12-9 

IDNUM 13-13 

Internal network number 

IPX 14-4 

IPX 

enabling router 14-4 

encapsulation 14-3 

parameters, configuration of 10-4 

IPX command 10-4 

IPX encapsulation 

on Ethernet port 14-3 

IPX Filter 

SAP 14-7 

type 14-8 

IPX Filter entry number 

SAP filtering 14-7 

IPX internal network number 14-4 

IPX network number 


IPX RIP 


IPX routing 

displaying connections 10-6 

frame identification 14-3 

IPX SAP 


2 Memotec Inc. 

L 

Link-level protocols 5-2 

LLC controller 13-9 

LLC destination address 13-9 

LLC destination SAP 13-10 

LLC driver 6-4 

LLC dynamic window 13-11 

LLC frame size 13-12 

LLC host 13-9 

LLC lan port 13-9 

LLC maximum successive retries 13-11 

LLC retransmission timeout 13-10 

LLC Role 13-20 

LLC source SAP 13-9 

LLC timeout 

of PU 13-10 

LLC transmission window size 13-11 

Local termination for SNA 6-5 

M 

Maximum frame size 

for PU 13-7, 13-12 

Modem control signal 12-7 

Multipoint connection 6-3 

N 

Native SNA Over Frame Relay 6-6 

NET NUM 

displaying for IPX routing table 15-3 

NETWORK NUMBER 


Network number 

internal IPX 14-4 

Network number, for IPX routing 14-3 

Network topologies for BAN/BNN 6-5 

NEXT HOP 


NODE 


NRZI coding 12-9 

Number of desynch. characters 12-19 

Number of retries 

for PU 13-5, 13-11

O 

Operating mode 

of PU 13-2 

P 

Parameter list 






BAN/BNN maximum successive retries 13-16 


BAN/BNN Role 13-20 


BAN/BNN transmission window size 13-17 



Class 12-10, 13-8 

Clocking mode 12-3 

Congestion flow control 12-14 

Controller active 

for PU 13-3 

CRC encoding 12-9 

Delay Before Connection 13-3 

Delay before connection, for PU 13-3 

Desynchronization character, for COP port 12- 

19 

Dynamic clocking, on PASSTHRUOFR port 12- 

14 

Enable, IPX filter 14-7 

Fallback speed 12-5 

Format 12-15 

Group address 12-17 

Group poll 12-17 

Idle 12-9 

Internal network number, IPX 14-4 

IPX encapsulation, on Ethernet port 14-3 

IPX Filter entry number, SAP filtering 14-7 

IPX network number, on Ethernet port 14-3 

IPX RIP, on Ethernet port 14-2 

IPX SAP, on Ethernet port 14-2 

Link-Remote PU 13-8 


LLC destination SAP 13-10 

LLC dynamic window 13-11 

LLC frame size 13-12 

LLC lan port 13-9 

LLC maximum successive retries 13-11 

LLC retransmission timeout 13-10 

LLC Role 13-20 

LLC source SAP 13-9 

LLC transmission window size 13-11 

Modem control signal 12-7 

Number of desynch. characters 12-19 

Operating mode, of PU 13-2 

Poll delay (ms) 12-18 

Port speed 12-3 

Protocol, on port 12-2 

PU number 13-2 

PVC number, on HDLCOFR port 12-13 

Reception flow control 12-16 

Remote port number 12-11 

Remote PU number 13-8 

Remote unit 12-10, 13-8 

Router, IPX 14-4 

SAP, value to be filtered 14-7 

SDLC address 13-7 

SDLC duplex mode 12-17 

SDLC frame size 13-7 

SDLC number of retransmission retries 13-5 

SDLC port 13-7 

SDLC primary address 13-4 

SDLC primary port 13-4 

SDLC retransmission timeout 13-5 

SDLC secondary address 13-5 

SDLC secondary port 13-4 

SDLC transmission window size 13-6 

Subchannel mask 12-11 

Subchanneling 12-11 

Suppress DM upon disconnection 13-6 

Synchronization character 12-19 

Transmission flow control 12-16 

Transmission start level 12-6 

Transmit holding time 12-16 

Tx/Rx mode, on HDLCOFR port 12-13 

Type, IPX filter 14-8 

X25 frame relay encapsulation 12-21 

XID format 13-13 

XID identification number 13-13 

XID PU type 13-14 

XID support 13-6, 13-12 

Pararmeter list 

Frame delay (ms) 12-9 

Passthrough channels 3-2 

PASSTHROUGH driver 3-2 

Poll delay (ms) 12-18 

Port speed 12-3 

Ports 

parameters, configuration of 6-8 

primary & secondary 6-2 

Ports command 6-8 

Primary address 

of PU 13-4 

Primary port 6-2 

PU connection 13-4 

Prioritization 6-3 

Protocol 

on port 12-2 

Legacy Data 3

Protocol spoofing 6-3 

PU command 6-11 

PU number 13-2 

PUs 

activation status 13-3 







BAN/BNN retries 13-16 


BAN/BNN window 13-17 



class 13-8 

delay before connection 13-3 

destination SAP 13-10 

exchange identification 13-6, 13-12 

ID block 13-13 

ID number 13-13 

incrementing transmission window size 13-11 


LLC timeout 13-10 

maximum frame size 13-7, 13-12 

number of retries 13-5, 13-11 

on remote unit 13-8 

operating mode 6-3, 13-2 

parameters, configuration of 6-11, 13-3 

primary address 13-4 

primary port connection 13-4 


SDLC timeout 13-5 

secondary address 13-5 

secondary port connection 13-4 

SNA/SDLC port connection 13-7 

source SAP 13-9 

transmission window size 13-6, 13-11 

type in XID 13-14 

verifying active 11-12 

XID type 13-13 

PVC number 

for BNN connection 13-19 

on HDLCOFR port 12-13 

R 

Reception flow control 12-16 

Remote port 

specifying 12-11 

Remote port number 12-11 

Remote PU 13-8 

Remote PU number 13-8 

Remote Unit 

defining 13-8 

Remote unit 12-10, 13-8 

Retransmission timeout for BAN/BNN connection 

13-16 

Retries for BAN/BNN connection 13-16 

RIF caching 6-5 

Role 

for LLC and BAN/BNN 13-20 

Routed SNA Over Frame Relay 6-4 

Router 

IPX 14-4 

Routing 

IPX 14-3 

IPX RIP 14-2 

IPX SAP 14-2 

Routing for BAN connection 13-18 

Routing table 

age of entry 15-3, 15-5 

hop count, IPX 15-2, 15-4 

NET NUM, IPX 15-3 

network number, IPX 15-2 

next hop, IPX 15-2 

node, IPX 15-3 

service name, IPX 15-4 

service type, IPX 15-4 

socket, IPX 15-3 

ticks, IPX 15-2 

RTS signal 

operating mode 12-7 

4 Memotec Inc. 

S 

SAP 

value to be filtered 14-7 

SAP for IPX filter 14-7 

SAP mapping 6-4 


of PU 13-7 

SDLC driver 6-2 

concentration 6-4 

multipoint connection 6-3 

SDLC duplex mode 12-17 

SDLC Frame Size 13-12 

SDLC frame size 13-7 

SDLC number of retransmission retries 13-5 

SDLC port 13-7 

SDLC primary address 13-4 

SDLC primary port 13-4 

SDLC retransmission timeout 13-5 

SDLC secondary address 13-5 

SDLC secondary port 13-4 

SDLC transmission window size 13-6 

SDLC-SDLC mode 

of PU 6-3, 13-2 

Secondary address 

of PU 13-5 

Secondary port 6-2

PU connection 13-4 

SERVICE NAME 


Setup IPX menu 10-4 

Setup Port menu 6-8 

Setup PU menu 6-11 

Single switch conversion 6-5 


SNA 

data 6-3 

SNA Over Frame Relay 6-5 

SNA Over RFC-1490 6-4 

SNA/SDLC port 

connection, of PU 13-7 

duplex mode 12-17 

group address 12-17 

group poll 12-17 

poll delay 12-18 

SOCKET 


Source SAP 

of PU 13-9 

Source SAP for BAN/BNN connection 13-15 

Statistic 

HOP COUNT, displaying for IPX routing table 

15-4 

NET NUM, displaying for IPX routing table 15-3 

NODE, displaying for IPX routing table 15-3 

SERVICE NAME, displaying for IPX routing 

table 15-4 

SOCKET, displaying for IPX routing table 15-3 

TYPE, displaying for IPX routing table 15-4 

Statistics 

AGE, displaying for IPX routing table 15-2, 15-5 

HOP COUNT, displaying for IPX routing table 

15-2 

IPX routing table 10-6 

NETWORK NUMBER, displaying for IPX routing 

table 15-2 

NEXT HOP, displaying for IPX routing table 15- 

2 

TICKS, displaying for IPX routing table 15-2 

Subchannel mask 12-11 

Subchanneling 12-11 

Suppress DM upon disconnection 13-6 

Synchronization character 12-19 

T 

TICKS 


Timeout 

SDLC 13-5 

Transmission flow control 12-16 

Transmission start level 12-6 

Transmission window size 

dynamic 13-11 

for PU 13-6, 13-11 

incrementing 13-11 

Transmit holding time 12-16 

Transmitter idle state 12-9 

Tx/Rx mode 

on HDLCOFR port 12-13 

TYPE 


Type 

IPX filter 14-8 

Type of IPX filter 14-8 

Legacy Data 5 

U 

Underruns 12-6 

preventing 12-6 

W 

WAN/User ports 

protocol 12-2 

Window for BAN/BNN connection 13-17 

X 

X.25 protocol 

application example 9-5 

configuration of 9-4 

encapsulation method 12-21 

encapsulation to Frame Relay 9-2 

HDLC driver 1-3 

X25 frame relay encapsulation 12-21 

XID 

manual setting 13-12 

XID format 13-13 

XID identification number 13-13 

XID PU type 13-14 

XID support 13-6, 13-12 

XID type 

for PU 13-13

REACH FURTHER. OFFER MORE. 

Contact Memotec: 

tel.: +1-514-738-4781 

e-mail: MemotecSupport@memotec.com 

7755 Henri Bourassa Blvd. West 

Montreal, Quebec | Canada H4S 1P7 www.memotec.com

Legacy Data System Reference - Comtech EF Data

Create successful ePaper yourself

Delete template?

Save as template?