Release Bulletin NP V10.4.1R02 - Comtech EF Data

Release Bulletin 

NetPerformer ® Version 10.4.1

COPYRIGHTS AND DISCLAIMERS 

Published Date: April 2009 

Product No.: 621-0008-103 

Software Version: V10.4.1 R02 

Hardware Products: SDM-8400, SDM-9210, SDM-9220, SDM-9230, SDM-9606, SDM-9620 

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. 

Belden is a registered trademark of Belden Inc.in the United States of America and in other countries. 

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

Any other trademarks are the property of their respective companies. 

Copyright © 2009 Memotec Inc. 

Memotec Inc. 

7755 Henri Bourassa Blvd. West 

Montreal, Quebec 

Canada H4S 1P7 

Tel.: (514) 738-4781 

FAX: (514) 738-4436 

www.memotec.com

Contents 

About this Release Bulletin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 

Version 10.4.1 Release Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 

New Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 

SDM-9600 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 

SDM-9620 Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 

Base Product Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 

New Features in V10.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 

GSM A-bis/ter Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 


PowerCell Voice Transport (DCME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 


Internetworking Capabilities in V10.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 

Mixed GSM and Non-GSM Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 

GSM-only Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 

PowerCell-only Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 

SIP VoIP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 

Requirements, Limitations, and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 

Firmware Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 

Main Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 

DSP Algorithms (Quadra File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 

Boot Sector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 

Hardware Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 

List of Subsystems and Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 

Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 

Upgrading the NetPerformer to V10.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 

Password Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 

Memotec Inc.

Memotec Inc. 

Concerning Potential Downgrade Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 

Notice Concerning HyperTerminal Connections . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 

Changes/Fixes in V10.4.1 R01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 

Main Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 

New Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 

Display States (DS)/Redundancy/Remote . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 

Display Errors (DE)/Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 

GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 

ATM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 

PowerCell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 

DCME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 

Ethernet/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 

Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15 

Traffic Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 

Loopback and Troubleshooting Capabilities . . . . . . . . . . . . . . . . . . . . . . . . 3-19 

Legacy Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23 

TCP Acceleration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24 

Alarms, Errors and Restarts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24 

DSP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25 

Display, Console, and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25 

MIB, SNMP and ACTview 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29 

Other Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 

Signaling Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 

DSP Algorithms (Quadra File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35 

QB 1.2.7 R01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35 

QC 1.2.7 R01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35 

Bug Fixes in 10.4.1 R01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 

TT Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 

TT 3606 - Loss of connection at the SNMP agent. . . . . . . . . . . . . . . . . . . . . . . . 4-2 

TT 1888 - Invalid GSM channel configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 

TT 3811 - Memory leak causing a system restart. . . . . . . . . . . . . . . . . . . . . . . . 4-2 

TT 3835 - System restart with some HDLC traffic . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Bug Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 

Bug 4087 - FXS seizure detect time configuration. . . . . . . . . . . . . . . . . . . . . . . . 4-3 

Bug 4097 - WarmStart and LinkStateInSync traps not sent. . . . . . . . . . . . . . . . . 4-3 

Bug 4126 - Stuck in disconnect state with E&M Push-To-Talk . . . . . . . . . . . . . . 4-3 

Bug 4174 - E&M seizure detect time configuration . . . . . . . . . . . . . . . . . . . . . . . 4-3 

Bug 4217 - New Signaling mode choice for E1 . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 

Bug 4079 - Hook detect time configuration for E&M Push-To-Talk . . . . . . . . . . . 4-5 

Bug 4172 - Call command issue with backup ISDN link . . . . . . . . . . . . . . . . . . . 4-6 

Bug 4325 - Memory leak with GSM PVC over IP. . . . . . . . . . . . . . . . . . . . . . . . . 4-6 

Bug 4340 - Voice channels stuck when in transparent signaling . . . . . . . . . . . . . 4-7 

Bug 4369 - New "LDCD" voice compression algorithm . . . . . . . . . . . . . . . . . . . . 4-7 

Bug 4370 - Support for Memotec/Comtech Ethernet MAC address . . . . . . . . . . 4-8 

Bug 4438 - Prevent filling up the Alarm log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 

Bug 4439 - Change of behavior for Delay before Call Deactivation field . . . . . . . 4-9 

Bug 4453 - Secondary link issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 

Bug 4545 - Better control of phone settings for backup link. . . . . . . . . . . . . . . . . 4-9 

Bug 4594 - Invalid alarm at start up with new modules . . . . . . . . . . . . . . . . . . . 4-10 

Quadra QB/QC: Resolved in QB 1.2.7 A08. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 

TT 3819 - Maximum number of groups for GSM . . . . . . . . . . . . . . . . . . . . . . . . 4-11 

TT 3820/3822 - Issue in POSNET application at 2400 Bauds . . . . . . . . . . . . . . 4-11 

TT 3823 and 3824 - Modem relay fix when using POS V.22 . . . . . . . . . . . . . . . 4-11 

Bug 4098 - Memory fragmentation fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 

Memotec Inc.

Memotec Inc.

About this Release Bulletin 

1 

This release bulletin provides up-to-date information about NetPerformer ® Version 10.4.1 

for product models SDM-8400, SDM-9210, SDM-9220, SDM-9230, SDM-9606 and 

SDM-9620. 

The information contained in the present document supplements or supersedes the 

information in the rest of the NetPerformer document set, including: 

• NetPerformer System Reference 

• Hardware installation guides for the individual NetPerformer products that can 

run V10.4.1. 

NOTE: All of these documents are available on the NetPerformer Companion CD, 

which is shipped with every product (Order No. 161-0692-001, Part No. 520- 

0081-001).. 

Memotec Inc. 1-1

Using this Document 

Version 10.4.1 Release Summary 

New Products 

NetPerformer Version V10.4.1 is based on a common source code used to generate all 

firmware versions for the NetPerformer product sub-family that includes: 

• SDM-9620: V10.4.1 is factory installed on this product 

• SDM-8400, SDM-9210, SDM-9220, SDM-9230, SDM-9606: V10.4.1 is factory 

installed on new units. . 

NOTE: If you need to upgrade a unit running V10.2.X or V10.3.X, turn to “Upgrade 

Procedures” on page 2-1. 

V10.4.1 cannot run on legacy NetPerformer products: SDM-9360, SDM- 

9380 and SDM-9585. For these products, as well as all products running 

with SIP VoIP voice transport, the latest software version available is 

V10.2.3 R11. 

SDM-9600 Chassis 

The NetPerformer SDM-9600 is a high-end chassis based on a standardized platform 

architecture for carrier-grade telecommunication applications. It is ideal for large-scale 

network applications such as GSM using point-to-point E1/T1 circuits, transport through 

IP (terrestrial or satellite) or satellite Single Channel Per Carrier (SCPC) connections, and 

Voice over IP (VoIP). Voice/data over PowerCell applications can use IP or WAN 

connections and are able to integrate SCPC on digital or serial interfaces. 

• PICMG 3.0 standard rack solution 

• 19" rack-mountable 

• -48 VDC (dual feed) 

• Maximum 5 blades, each with two components: 

- Main board, loaded from the front 

- (Optional) Rear Transition Module (RTM), loaded from the rear 

All slots on the SDM-9600 must be installed with the same type of blade, in this 

case, the SDM-9620. 

1-2 Memotec Inc.


• RTM for 1:1 redundancy, available as of NetPerformer V10.4.1 R01, connects to 

2 blades in front (maximum 2 per SDM-9600 chassis). 

• Hot swappable components 

• Backplane connectivity 

• IPMC support (available as of NetPerformer V10.4.1 R01) 

• Removable fan control module and air filter. 

SDM-9620 Blade 

• The main board loads into front slots of the SDM-9600 chassis (maximum 5), 

and provides: 

- 2 10/100/1000 Mbps Ethernet ports 

- 1 serial port 

- 1 RJ-45 console port. 

• The main board can be paired with an optional RTM that provides 16 E1/T1 universal 

digital ports 

The RTM for 1:1 redundancy is paired with 2 SDM-9620 blades in front, and 

provides 16 redundant E1/T1 ports. 

• Each SDM-9620 blade can be loaded with up to 5 DSP modules 

• Each blade has a capacity of up to 480 digital telephony channels 

• A fully loaded SDM-9600 supports 2400 simultaneous voice calls 

• Hot swap capability and power management control 

• GSM capable 

• Backplane connectivity between SDM-9620 blades is available as of V10.4.0 

R05, using PVCR (PVCRoBP), IP (IPoBP) or transparent switching via the hub 

blade installed in Hub slot 2 

• IPMC support available as of NetPerformer V10.4.1 R01 

The following diagnostics commands have been added in NetPerformer V10.4.0 

for troubleshooting the SDM-9620: 

• The Display Alarms (DA) command has been added to the boot sector 

• The Temperature Sensor Settings (TEMP) command has been added to the console 

to display the temperature of all sensors 

• Temperature sensor and power supply monitoring with SNMP traps are also 

available. 

Memotec Inc. 1-3


Base Product Software 

New Features in V10.4.1 

• 1:1 Redundancy on the SDM-9620, including a new RTM that provides 16 

redundant E1/T1 ports 

• IPMC communication on the SDM-9600, including direct access to the IPMC 

console 

• Redundant MAC address and dual redundant IP addresses on Ethernet ports 

• PVCR Link Management for point-to-point applications, with end-to-end propagation 

of physical alarms and the possibility of viewing events (DLS command) 

and capturing Link Management traffic (SC command) 

• New loopback capabilities on E1/T1 interfaces for troubleshooting purposes 

• Improvements to the error log, including new configuration, filtering and capture 

processes 

• The ability to monitor cumulative performance statistics over a specific time 

period (DPP command) 

• Various improvements to the display, console and configuration commands on 

the base product command line interface. 

Details on these new features are provided in later sections on changes/fixes in V10.4.1 

(“Changes/Fixes in V10.4.1 R01” on page 3-1). 

GSM A-bis/ter Support 

Support of GSM A and E is offered with the NetPerformer base product. Support of GSM 

A-bis and A-ter requires the GSM A-bis/ter licensed software option. You must install 

the same NetPerformer version and GSM A-bis/ter licensed software option on all 

participating units in the network. 


• Prioritization of SS7 signaling traffic in GSM applications 

• Support of 4 ATM ports on the SDM-9620, with the ability to configure the same 

VPI/VCI on more than one port 

• Capture of GSM trace information from the capture buffer for troubleshooting 

purposes. 

Details on these new features are provided in later sections on changes/fixes in V10.4.1 

(“Changes/Fixes in V10.4.1 R01” on page 3-1). 

1-4 Memotec Inc.

PowerCell Voice Transport (DCME) 



• New statistics for the analysis of voice transmissions in a DCME application 

Details are provided in later sections on changes/fixes in V10.4.1 (“Changes/Fixes in 

V10.4.1 R01” on page 3-1 ). 

Internetworking Capabilities in V10.4.1 

NetPerformer V10.4.1 provides both PowerCell and advanced GSM A-bis/ter support. 

Mixed GSM and Non-GSM Network 

A NetPerformer unit installed with the GSM licensed software option can communicate 

with a unit that does not have the GSM license installed. This requires the following on all 

participating units: 

• Installed with V10.4.0 R01 or later 

• Configured for PowerCell voice transport method (PVCR) 

• A PVCR connection must be configured between the unit running GSM and the 

unit without GSM. 

In addition, the non-GSM unit requires: 

• PowerCell version global parameter set to 2. 

GSM-only Network 

For GSM applications all NetPerformer units must be running the same phase of GSM. 

• Backward compatibility is possible between V10.4.0 R04 or later and 

V10.3.5 

• GSM A-bis/ter support in V10.4.1 is the only version that can run on the SDM- 

9620 

• If an SDM-9620 is installed in the network, all participating NetPerformer 

units must be upgraded to V10.4.1. Refer to “Upgrade Procedures” on page 2- 

1. 

PowerCell-only Network 

When the network uses PowerCell voice transport, a NetPerformer running V10.2.X or 

V10.3.X can communicate with a unit running V10.4.1. 

Memotec Inc. 1-5


NOTE: If any units require GSM, they must be upgraded to V10.4.1 (or at least 

V10.3.5 if no SDM-9620 units are involved) to continue participating in the 

network. Refer to “Upgrade Procedures” on page 2-1. 

SIP VoIP Network 

All units in a SIP VoIP voice transport application must stay at NetPerformer 

V10.2.X. The highest NetPerformer version supporting SIP VoIP is V10.2.3 R11. 

1-6 Memotec Inc.

Requirements, Limitations, and Compatibility 

Requirements, Limitations, and Compatibility 

Caution: These issues could impact service in your application. Read this 

section carefully. 

• For GSM applications, NetPerformer units running V10.4.1 cannot be used in the 

same network as units running an earlier version of the software. 

• To carry WAN traffic across a network that includes GSM, it is not necessary 

that all participating NetPerformer units be installed with the GSM A.bis/ter 

option. See “Mixed GSM and Non-GSM Network” on page 1-5. 

• Data connections, including Frame Relay, PVCR and transparent modes, are 

fully compatible with NetPerformer versions 7.X.X, 8.X.X, 9.X.X, 10.2.X and 

10.3.X. 

• Synchronous DSP modules must be used for a GSM application. This may be the 

low-density DSP-160 module or the high-density HD DSP module. The HD DSP 

is required on the SDM-9606 and SDM-9620. 

These synchronous DSPs are supported only if the latest hardware drivers 

are installed in the NetPerformer unit. Refer to “Hardware Drivers” on page 1- 

10. 

• The SDM-9230 and SDM-9606 are limited to a single Ethernet port when the 

GSM A.bis/ter licensed software option is installed and GSM 3G is activated. In 

this case, only the first Ethernet port (ETH1) can be configured and used. The 

second Ethernet port (ETH2) is not available, as its resources are allocated to support 

GSM 3G. 

When the GSM A.bis/ter licensed software option is not installed or when 

GSM 3G is not activated, both Ethernet ports (ETH1 and ETH2) are available. 

If GSM 3G is not required, it can be disabled to allow utilization of the second 

Ethernet port: 

- At the NetPerformer command line prompt, enter the menu sequence: SE � 

GSM 

- Set Activate 3G support to NO. 

• In V10.4.1, the SIP stack is no longer compiled during system startup. A NetPerformer 

unit installed with V10.4.1 cannot support standard voice using SIP 

VoIP voice transport. 

The last NetPerformer version to support SIP VoIP is V10.2.3 R11. 

• The following products are not supported in NetPerformer V10.4.1: SDM- 

9360, SDM-9380, SDM-9580, SDM-9585. The latest version to support these 

products is NetPerformer V10.2.3 R11. 

Memotec Inc. 1-7


Firmware Naming 

Main Application 

NetPerformer firmware filenames reflect both the model name and the firmware version. 

Use the NetPerformer DIR console command to view the current filenames on your unit. 

The generic filename format for the NetPerformer main application file is XxnnnnYjjj.bin, 

where: 

• Xx is a two-character code that identifies the product type: 

Value Products 

Ha SDM-9210, SDM-9220, 

SDM-9230 

Ia SDM-8400 

Ja SDM-9606 

Ka SDM-9620 

Table 0-1: 

• nnnn is the version number, for example 1041 for NetPerformer version 10.4.1. 

• Y is the revision type identifier: 

Value Revision Type 

A Alpha version 

B Beta version 

R Revision 

S Special release 

Table 0-2: 

• jjj is the two- or three-digit revision number. 

For example, Ha1041R01.bin is the filename for the base application of version 10.4.1, 

Revision 1, that runs on the SDM-9210, SDM-9220 and SDM-9230. 

NOTE: On all products except the SDM-8400, the Signaling Engine file is included in 

the main application file. Separate download and installation of the Signaling 

Engine is not required. There is no Signaling Engine file for the SDM- 

1-8 Memotec Inc.

8400. 

DSP Algorithms (Quadra File) 

Boot Sector 

The Quadra file format is QxnnnYjjj.biz, where: 

• Q is a prefix for Quadra file recognition 

• x identifies the type of DSP module: 

Value Type of DSP Module 


b Low-density DSP module for the SDM-9210, SDM- 

9220 and SDM-9230 

c High-density DSP module for the SDM-9210, SDM- 

9220, SDM-9230, SDM-9606 and SDM-9620 

Table 0-3: 

• nnn is the version number 

• Y is the revision type identifier (none, A, B, R or S) 


The version number, revision type identifier and revision number are used in the 

same way as for the main application, described on “Main Application” on 

page 1-8. 

For example, Qc127R01.biz is the filename for Quadra file version 1.2.7 R01, which 

contains the DSP algorithms for the high-density DSP module. 

NOTE: There is no Quadra file for the SDM-8400. 

The filename format for the boot sector file is zxnnnYjjj, where: 

• z is a prefix for boot sector file recognition 

• x identifies the product type: 


c SDM-9210, SDM-9220, SDM-9230 

Table 0-4: 

Memotec Inc. 1-9


Hardware Drivers 


d SDM-8400 

e SDM-9606 

f SDM-9620 

Table 0-4: 

• nnn is the version number 

• Y is the revision type identifier (A, B, R or S) 


For example, zc121r06.bin is the filename for the boot sector of the SDM-9210, 

SDM-9220 and SDM-9230. 

The boot sector files on the various products are at different revision levels: 

• SDM-9210, SDM-9220 and SDM-9230: version 1.2.1 R06 (file zc121r06.bin) 

• SDM-8400: version 1.2.2 R05 (file ZD122R05.bin) 

• SDM-9606: version 1.4.1 R01 (file ze141r01.bin). 

• SDM-9620: version 1.4.1 R01 (file zf141r01.bin). 

Driver files are required for the SDM-9210, SDM-9220, SDM-9230 and SDM-9606. 

These files must be loaded before the main application file. Refer to “Upgrade 

Procedures” on page 2-1. 

• For the SDM-9210: HAV201R1.DRV and IFV200R3.DRV 

• For the SDM-9220 and SDM-9230: HAV154R1.DRV and IFV109R4.DRV 

• For the SDM-9606: JA100R01.DRV 

The HA*.DRV or JA*.DRV file may be required to allow the bootstrap FPGA to support 

newer interfaces. The IF*.DRV file is required when interfaces are installed in the product 

(E1/T1, Dual Serial, FXO, FXS, E&M, etc.). 

Caution: If you have recently purchased new interface cards or synchronous 

DSPs to install in your SDM-92X0 chassis, please make sure you upgrade to the 

latest version of these files. 

1-10 Memotec Inc.

List of Subsystems and Versions 

Subsystem Version 


NetPerformer main application 10.4.1 R01 (for SDM-8400, SDM-9210, 

SDM-9220, SDM-9230, SDM-9606 and 

SDM-9620) 

NetPerformer MIB MI1041R01.MIB 

Boot Sector 1.2.1 R06 (for SDM-9210, SDM-9220 and 

SDM-9230) 

1.2.2 R05 (for SDM-8400) 

1.4.1 R01 (for SDM-9606 and SDM-9620) 

DSP Algorithms (Quadra) Qb 1.2.7 R01 (for SDM-9210, SDM-9220, and 

SDM-9230 with low-density DSP module) 

Qc 1.2.7 R01 (for SDM-9210, SDM-9220, SDM- 

9230, SDM-9606 and SDM-9620 with high-density 

DSP module) 

Driver files 1 

NMS (ACTView 3000) 3.0.0 R06 

HAV201R1.DRV and IFV200R3.DRV (for SDM- 

9210) 

HAV154R1.DRV and IFV109R4.DRV (for SDM- 

9220 and SDM-9230) 

JA100R01.DRV (for SDM-9606) 

Table 0-5: 

1. The driver files, HA*.DRV, JA*.DRV and IF*.DRV, are used with the SDM- 

9210, SDM-9220, SDM-9230 and SDM-9606 only, and must be downloaded 

before the loading the main application file. 

Memotec Inc. 1-11


1-12 Memotec Inc.

Upgrade Procedures 

2 

Memotec Inc. 2-1


Upgrading the NetPerformer to V10.4.1 

This procedure assumes that your NetPerformer unit is currently running V10.X.X. If your 

unit is running an earlier version, or if you require assistance in downloading any of the 

files required for this procedure, contact Technical Support at: +1 514.738.4781 or 

support@memotec.com. 

To upgrade a NetPerformer unit to V10.4.1: 

1. Ensure that the system time and date are set correctly. Use the Set Time (ST) 

command to adjust the time setting. 

Caution: If the system time is incorrect, the new firmware may be interpreted 

as an older version. 

2. (Optional) Using FTP or ZMODEM, download the boot sector file (z*.bin); refer to 

“Boot Sector” on page 1-9: 

• zc121r06.bin for the SDM-9210, SDM-9220 or SDM-9230 

• ZD122R05.bin for the SDM-8400 

• ze141r01.bin for the SDM-9606 

• zf141r01.bin for the SDM-9620. 

The boot sector file may be downloaded at any time during this procedure, before or 

after the hardware driver files and the main application software. 

3. On the SDM-9210, SDM-9220, SDM-9230 or SDM-9606, download the hardware 

driver files (HA*.DRV, JA*.DRV and IF*.DRV) using FTP or ZMODEM. Refer to 

“Hardware Drivers” on page 1-10 for the exact filenames. 

Caution: The hardware driver files must be downloaded before the 

main application file. On the SDM-9210, SDM-9220 or SDM-9230, 

download the HA*.DRV file before the IF*.DRV file. If you have recently 

purchased new interface cards to install in these products, make sure 

you upgrade to the latest version of these files. 

4. Download the DSP algorithms (Q*.biz); refer to “DSP Algorithms (Quadra File)” on 

page 1-9: 

• Qb127R01.biz for the low-density DSP module on the SDM-9210, SDM-9220 

or SDM-9230 

• Qc127R01.biz for the high-density DSP module on the SDM-9210, SDM-9220, 

SDM-9230, SDM-9606 or SDM-9620. 

There is no Quadra file for the SDM-8400. 

Caution: The unit will decompress the DSP algorithms automatically 

after it receives this file. Wait for decompres-sion to complete before 

continuing with the next step. 

2-2 Memotec Inc.

Password Usage 

Upgrading the NetPerformer to V10.4.1 

5. Download the NetPerformer main application software; refer to “Main Application” 

on page 1-8: 

• Ha1041R01.bin for the SDM-9210, SDM-9220 or SDM-9230 

As of V10.4.0 R05, a flexible filename can be used when downloading the SDM- 

9210, SDM-9220 or SDM-9230 firmware using ZMODEM or TFTP. . 

• Ia1041R01.bin for the SDM-8400 

• Ja1041R01.bin for the SDM-9606 

• Ka1041R01.bin for the SDM-9620. 

NOTE: The unit will restart automatically after it receives this file. Separate download 

and installation of the Signaling Engine file is not required. 

IMPORTANT: Remember your Administrator Password before you commence the 

upgrade procedure. After an upgrade, you must access the unit with the last password 

that was defined, as follows: 

• If the password defined for the previous version was not modified from the factory 

default value, enter: 

Username: ADMIN 

Password: SETUP 

• If you modified the password for the previous version from the factory default 

value, enter: 

Username: ADMIN 

Password: the password you defined 

Memotec Inc. 2-3


Concerning Potential Downgrade Problems 

Caution: NetPerformer downgrade from V10.4.1 to an earlier version can 

produce unexpected results: 

• An alarm will be logged for each parameter that is unknown in the target version, 

and that parameter will be ignored 

• The journal file (JOURNAL.TXT) lists all parameters that have been skipped in 

this way 

• Do not attempt to downgrade to a software version earlier than V10.2.2 on 

150-0022-X2X or 150-0023-X2X release 3 SDM-9230 equipment or higher. 

Notice Concerning HyperTerminal Connections 

The HyperTerminal� communications program comes with Microsoft� Windows� 

products, and can be used for very basic NetPerformer console functions if no terminal 

emulation program is available. 

Caution: HyperTerminal is not recommended for adjusting the 

NetPerformer configuration or monitoring its operations. Known problems 

include the following: 

• The arrow keys cannot be used to view channel status on all slots 

• The console speed cannot be changed once the console connection is up and running 

• On some computers, the default Emulation setting of the HyperTerminal� communications 

program can potentially cause problems for NetPerformer console 

operations. 

If you must use HyperTerminal for your console connection, you should change the 

Emulation setting from Auto detect to ANSI, as follows: 

1. Access HyperTerminal using the Windows Start button and drop-down menus: 

Start > Programs > Accessories > Communications > HyperTerminal 

2. If you have already defined the connection to the NetPerformer console port, open 

that connection: 

File > Open > your_filename.ht 

If you have not yet defined the connection to the NetPerformer console port, create 

a new connection: 

2-4 Memotec Inc.

File > New Connection > your_filename 

3. Open the Properties window for the connection: 

File > Properties 

Notice Concerning HyperTerminal Connections 

4. Click on the Settings tab to view the current value of the Emulation parameter. 

5. Select the value ANSI from the list box for the Emulation parameter. 

6. Click OK. 

NOTE: The above procedure does not resolve the problems with arrow key functionality 

or console speed, and should be considered a temporary solution 

only. You should procure a more robust terminal emulation software program 

for configuration and monitoring purposes. Contact Backhaul Solutions Technical 

Support if you need further assistance. 

Memotec Inc. 2-5


2-6 Memotec Inc.

Changes/Fixes in V10.4.1 R01 

3 

Memotec Inc. 3-1



New Product Support 

• Added: Firmware support of the new RTM on the SDM-9620 which provides 1:1 

redundancy. New software features have been implemented in conjunction with 

this feature, such as the addition of redundant IP and MAC addresses. ARP 

replies (Ethernet V2 and 802.3) are sent when there is a switch from one SDM- 

9620 blade to the other. Refer to the sections “Ethernet/IP” on page 3-13, and 

“Redundancy” on page 3-15 for further details on these features. 

• Added: A hardware assembly ID that distinguishes the new redundant SDM- 

9620 blade with no E1/T1 terminating resistors from the standard SDM-9620 

blade. The redundant blade connects to the RTM designed for 1:1 redundancy, 

which has the E1/T1 terminations. 

Execute the DHI command to view the assembly ID of the SDM-9620 blade, displayed 

as assy id: x. The following table indicates, for each SDM-9620 assembly 

ID, the maximum number of trunks that can be used for ATM traffic, and 

whether the blade supports 1:1 redundancy: 

assy id Product No. 

Max. no. of ATM 

trunks 

Supports 1:1 Redundancy? 

255 100-1205-501 2 No 

1 100-1205-502 4 No 

2 100-1205-503 2 Yes 

3 100-1205-503 4 Yes 

Table 0-1: 

AF.9620-1>DHI 

DISPLAY HARDWARE INFO 

... 

Hardware Info> Board id: 1 fru id: 0 rev id: 1 assy id: 3 

... 

NOTE: The alarm FRU/RTM MISMATCH is displayed when the type of SDM-9620 

blade installed (the FRU) does not correspond to the type of RTM it is connected 

with. 

• Added: The use of Intelligent Platform Management Controller (IPMC) communication 

on the SDM-9600. IPMC can be used to avoid the potential problem in a 

3-2 Memotec Inc.


redundant SDM-9600 system where two SDM-9620 units in different states 

could have the same Unit Name. This situation could occur if one SDM-9620 is 

the Primary Master and another is the Secondary Master with 1:1 redundancy. 

Redundancy requires a direct PVCR link between the two units. On the SDM- 

9600, the backplane offers this connection by default as long as an SDM-9620 is 

installed in slot 2. In other cases, a PVCR PVC over IP connection could be used. 

The SDM-9600 can now provide communication between SDM-9620 units 

through IPMC, as well. If the Secondary Master cannot communicate with the 

Primary Master using PVCR, it will use the IPMC path to retrieve the state of the 

Primary Master. If the Primary Master’s state differs from the local state, the Secondary 

Master will request the Primary Master to change its state to the same 

state as the Secondary Master. In this way, if both units are properly configured 

for redundancy they cannot have the same Unit Name. 

This implementation of IPMC communication requires the configuration of the 

Primary Master and Secondary Master slot numbers in the REDUNDANCY/ 

REMOTE submenu of the Setup (SE) command: 

- Slot number of Primary Master (Configuration file: [Redundancy] SlotNumberPriMaster; 

SNMP: redundancyRemoteSlotNumberPriMaster): 

Specifies the slot number of the Primary Master unit. 

NOTE: This parameter appears at the console only when the Redundancy Role is set 

to SECONDARY MASTER. It is available for the SDM-9620 only. 

- Choice list of values: NONE, 1, 2, 3, 4, 5 

- Default value: NONE 

- Slot number of Secondary Master (Configuration file: [Redundancy] Slot- 

NumberSecMaster; SNMP: redundancyRemoteSlotNumberSecMaster): 

Specifies the slot number of the Secondary Master unit. 

NOTE: This parameter appears at the console only when the Redundancy Role is set 

to PRIMARY MASTER. It is available for the SDM-9620 only. 

- Choice list of values: NONE, 1, 2, 3, 4, 5 

- Default value: NONE 

Other configuration changes for a redundant system have been introduced in 

V10.4.1 R01. Refer to “Redundancy” on page 3-15. 

New statistics have been added to display the Redundancy Remote slot numbers 

and IPMC errors: 

Memotec Inc. 3-3


Display States (DS)/Redundancy/Remote 

AF.9620-2>DS 

DISPLAY STATES 

Item (GLOBAL/PORT/REDUNDANCY/SPAN,def:GLOBAL) ? REDUNDANCY 

Item (LOCAL/REMOTES,def:LOCAL) ? REMOTES 

Number of remotes...................................1 

Role................................................SECONDARY 

MASTER 

Index...............................................2 

Unit name...........................................AF.9620-4 

Backup name.........................................AF.9620-2 

Number of units up..................................1 

Number of units down................................0 

Number of redundant PVCR PVC links up...............0 

Number of redundant PVCR PVC links down.............0 

Number of power supplies up.........................0 

Number of power supplies down.......................0 

Number of fans up...................................0 

Number of fans down.................................0 

Number of signals up................................0 

Number of signals down..............................0 

Number of interfaces up.............................0 

Number of interfaces down...........................0 

Slot number.........................................4 

NOTE: The Redundancy Remote slot number is available through SNMP using the 

statRedundancyRemoteSlotNumber variable. 

Display Errors (DE)/Redundancy 

SDM9620-2>DE 

DISPLAY ERRORS 

Item (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/Q922/REDUNDANCY/SPAN/ 

TIMEP, 

def:REDUNDANCY) ? REDUNDANCY 

Number of frames discarded..........................0 

Number of frames with invalid size..................0 

Number of frames with invalid version field.........0 

Number of frames with invalid command field.........0 

Number of frames from an invalid master.............0 

Number of frames from an invalid remote.............0 

Number of IPMC frames discarded.....................0 

Number of IPMC frames with invalid version..........0 

Number of IPMC frames with invalid length...........0 

Number of IPMC frames with invalid command..........0 

Number of IPMC frames with invalid seq. number......0 

Number of IPMC frames with invalid unit state.......0 

Number of IPMC frames with invalid arguments........0 

3-4 Memotec Inc.

GSM 


• Resolved: The problem where the SDM-9620 would not boot up properly when 

running 8 spans of GSM traffic, and would have an incorrect number of active 

TRSP channels. 

• Added: In a GSM application it is now possible to send SS7, HDLC and PASS- 

THRU traffic through the GSM processing module, which permits improved prioritization 

of these traffic types. 

Formerly all PVCR traffic had to be prioritized over GSM data traffic in order to 

prioritize the SS7 signaling traffic. By rerouting the SS7 traffic through GSM 

module (referred to as CR Bypass), the SS7 signaling can be prioritized over 

GSM data traffic (TCH), which in turn receives higher priority than the PVCR 

traffic. 

The following extended GSM parameters have been added to control CR Bypass: 

- EP GSM CRBYPASSHDLC ENABLE/DISABLE: CR bypass for HDLC. 

When enabled (the default value) all HDLC traffic is routed through the GSM 

processing module. When disabled, HDLC traffic is processed with PVCR 

traffic. 

- EP GSM CRBYPASSPASSTHRU ENABLE/DISABLE: CR bypass for 

PASSTHRU. When enabled (the default value) all PASSTHRU traffic is 

routed through the GSM processing module. When disabled, PASSTHRU 

traffic is processed with PVCR traffic. 

- EP GSM CRBYPASSSS7 ENABLE/DISABLE: CR bypass for SS7. When 

enabled (the default value) all SS7 traffic is routed through the GSM processing 

module. When disabled, SS7 traffic is processed with PVCR traffic. 

The order of traffic prioritization is now as follows: 

1. SS7 and/or HDLC and/or PASSTHRU (depending on the CR Bypass settings) 

2. GSM TCH 

3. PVCR 

NOTE: Traffic prioritization is performed when the driver window reopens. At that 

time, all traffic that was queued while the window was closed is dequeued, 

and then transmitted in order of priority. 

• Modified: The default value of the sorter timeout has been changed to 0 ms when 

the GSM license is activated. This change corrects a problem where packets 

received out of order would not be processed until the next packet arrived, which 

was dependent on when the PVC would receive the next packet and whether any 

jitter occurred. Now the GSM application processes each packet at the time it is 

received, and the GSM layer takes care of any out-of-sequence packets. 

Memotec Inc. 3-5


ATM 

• Modified: The Activate 3G support parameter has been returned to GSM configuration 

(SE/GSM) on an SDM-9620 installed with GSM. The GSM software 

license enables ATM, which automatically reserves 2 or 4 TDM spans, depending 

on the type of blade (see the table on “Added: A hardware assembly ID that 

distinguishes the new redundant SDM-9620 blade with no E1/T1 terminating 

resistors from the standard SDM-9620 blade. The redundant blade connects to 

the RTM designed for 1:1 redundancy, which has the E1/T1 terminations.” on 

page 3-2). Therefore, if ATM is not needed the Activate 3G support parameter 

should be set to NO. This is the default value on the SDM-9620. Configure this 

parameter as YES to allow 2 or 4 TDM spans to be reserved for ATM. 

• Modified: TCH/SIG switching has been implemented in order to remain synchronized 

on the TCH when the BTS or BSC allocates signaling channels dynamically. 

Before this change the destination would be dropped. 

• Resolved: The problem in a GSM application with an SDM-9606 on the BSC 

side, where some GSM channels associated with an SDM-9220 on the BTS side 

would not come up in DATA state after a unit restart (RU command). 

• Resolved: The problem with an SDM-9230 in a GSM application, where the unit 

would reset with an alarm of type M=66 A=300 D=XXXXXXXX when the signaling 

channels were sent over an HDLCoIP connection. In this mode, if packets are 

lost on the WAN link the channel is not resynchronized, the transmission of 

received packets continues, and BSC/BTS synchronization remains up at all 

times. 

• Added: Support of up to 4 ATM trunks on the SDM-9620, at 4 MHz each (64 

timeslots). This implementation is required for Quad IMA. 

IMPORTANT: 4 ATM trunks are available only on a modified Rev. 2 SDM- 

9620 blade, with Assembly ID 1 or 3. On other SDM-9620 blades, only 2 

trunks at 8 MHz (128 timeslots) can be set to ATM. Refer to “Execute the 

DHI command to view the assembly ID of the SDM-9620 blade, displayed as 

assy id: x. The following table indicates, for each SDM-9620 assembly ID, 

the maximum number of trunks that can be used for ATM traffic, and 

whether the blade supports 1:1 redundancy:” on page 3-2 for details on the 

assembly ID. 

The following improvements have also been made: 

- It is now possible to have the same VPI/VCI on two different ports, for use in 

a redundant system 

- The PING/ATM command requests the port number (on the SDM-9620 only) 

- Port ETH2 can now be used at the same time as ATM (on the SDM-9620 

only). 

Limitation: When ATM is activated, the first 31 timeslots of each TDM are 

reserved for ATM. 

3-6 Memotec Inc.


• Modified: On the SDM-9620 with GSM, the number of timeslots reserved for 

ATM on TDM buses (where applicable) has been reduced from 32 to 31. The 

maximum number of timeslots currently allowed on each TDM is 124 (i.e. 4 * 

31). 

This change resolves the problem where an SDM-9620 in a GSM application 

would log alarms of type M=139 A=00 D=XXXXXXXX and 

SE: File .\portctrl\PORTCTRL.c, Line 4083. 

Formerly, when 32 ATM timeslots were reserved, only 2 E1 could be configured 

on a TDM with 31-timeslot HDLC channels instead of 3. In addition, the number 

of timeslots available on a TDM was not calculated properly. ATM timeslots 

were counted as being available, which is not true in non-ATM mode. 

IMPORTANT NOTE: The possible number of 31-timeslot HDLC channels 

now drops from 8 to 6 when the GSM license is activated, due to the 2 TDMs 

reserved for ATM. 

• Resolved: The following problems that occurred when an ATM channel was 

reset (Protocol parameter set to OFF): 

- Another configured ATM channel would go down and not come back up 

again unless the unit was reset 

- The reset ATM channel would not come back up if its Protocol parameter 

was changed back to ATM 

Now, if the ATM licensed software option is detected on unit start-up or reset, 

ATM support will not be deactivated when an ATM channel is set to OFF. 

• Resolved: Several errors related to VPI/VCI parameter management have been 

corrected. 

- Now, when the VCI parameter of an ATMPVCR PVC is changed, no invalid 

journal entries are logged. 

- The VPI/VCI corrections also permit configuration of the same VPI/VCI 

combination on different ATM ports on the SDM-9620, e.g. one PVC with 

VPI/VCI 0/1 that uses port 101, and another PVC with VPI/VCI 0/1 that uses 

port 201. 

• Resolved: On an ATM span, if the Timeslot 16 used as data channel parameter is 

set to NO, timeslot 16 no longer comes up as the default Timeslot value for configuration 

of a channel when the Number of consecutive timeslots on the previous 

channel is set to 15. This would permit configuration of the reserved channel. 

Now timeslot 16 is skipped, and the default Timeslot is displayed as 17. The 

Timeslot 16 used as data channel parameter must be set to YES to permit configuration 

of timeslot 16. 

• Resolved: The problem where alarms of type M=125 A=04 D=XXXXXXXX would 

occur when ATM PVCs were reset using the single-line entry command SE PVC 

x-y RESET after the ATM span was disabled. 

Memotec Inc. 3-7


PowerCell 

• Added: PVCR Link Management for point-to-point applications using T1/E1 

card interfaces has been improved, and physical alarms are now propagated from 

one side of the network to the other. The current status can be displayed with the 

new Display Link State (DLS) command. 

To reflect the digital card interface alarm conditions end to end, the host monitors 

the status of the PVCR link, and the Signaling Engine monitors the status of the 

physical port on the card. An alarm is logged when either status changes, based 

on the current value of the LINK parameter Link management alarm type, which 

can be set to RAI/ YELLOW or AIS. 

Host-side link management will work only if both sides of the connection are 

installed with NetPerformer V10.4.1 R01. 

PVCR link management alarms that are now sent end to end include: 

- RAI: Remote Alarm Indication for E1, Yellow Alarm for T1 

- AIS: Alarm Indication Signal 

- LOF: Loss of Frame 

- LOS: Loss of Signal 

- TS16AIS: Timeslot-16 Alarm Indication Signal, for E1-CAS only 

- LOMF: Loss of Multiframe, for E1-CAS only 

The Display Link Status (DLS) Command 

To execute the Display Link Status command, enter DLS at the NetPerformer 

console command line. Use the left and right arrow keys to change from one slot 

to another. Press K to access a list of other navigation keys. 

The DLS display provides quick access to information about the two primary 

objects of interest for link management: 

- [ LOCAL INTERFACE ]: The local interface that is being monitored. Information 

includes: 

� The monitored interface (link) number, e.g: 0100 

� The current state of the interface, including both physical 

conditions like DISABLED and Link Management alarms such as 

NO ALARM, TX AIS, RX RAI 

For example, you can easily see that the interface has received an RAI alarm, 

transmitted an AIS alarm, or is simply disabled. 

3-8 Memotec Inc.

Examples of 

the DLS 

display: 


- [ MANAGEMENT CHANNEL ]: The management channel through the PVCR 

connection. This is a virtual channel whose status applies to the currently displayed 

link only. Information includes: 

� The remote interface (link) number, e.g. 0200 

� The state of the management channel, e.g. CONNECTED, NOT 

CONNECTED, TARGET NOT FOUND 

� The Unit name of the remote unit (PEER) 

� The Received state (RX) of the management session, e.g. 

LOF+LOS 

� The Sent state (TX) of the management session, e.g. ACK, in 

response to a previous request 

For example, you can easily determine why the local interface has transmitted 

an AIS alarm, e.g. the management channel received an LOS+LOF and 

replied with an ACK. 

1. Normal operations: The links are enabled, Link Management is enabled, the E1/T1 

interfaces are connected and no alarms have occurred. 

>>> SIDE A 

--[ LOCAL INTERFACE ]----------------------------------------------- 

LINK#: 0100 STATE: NO ALARM 

--[ MANAGEMENT CHANNEL ]-------------------------------------------- 

LINK#: 0200 STATE: CONNECTED PEER: SIDE_B 

RX: NO ALARM TX: NO ALARM 

-------------------------------------------------------------------- 

>>> SIDE B 




LINK#: 0100 STATE: CONNECTED PEER: SIDE_A 

RX: NO ALARM TX: NO ALARM 

-------------------------------------------------------------------- 

NOTE: To avoid confusion, the RX and TX statistics are cleared in a NO ALARM situation. 

Memotec Inc. 3-9


2. Link disabled on SIDE A: 

>>> SIDE A 




LINK#: STATE: DISABLED PEER: 

RX: TX: 

-------------------------------------------------------------------- 

>>> SIDE B 




LINK#: 0100 STATE: PROG PEER: SIDE_A 

RX: CONNECT CONF NAK TX: CONNECT REQUEST 

-------------------------------------------------------------------- 

NOTE: The management state shows DISABLED for SIDE A. In fact, the actual 

management channel over PVCR is still keeping other pairs of spans alive. 

This “true” channel is ignored to avoid confusion. 

On SIDE B, TX/RX activity appears as there is still a management channel 

active for another pair of links. The RX field shows CONNECT CONF NAK, 

indicating that the other side (SIDE A) has refused the CONNECT 

REQUEST that was transmitted (see the TX field). SIDE B retries every 5 

seconds. 

The link management status on SIDE B shows PROG in this case, but once 

again the management channel for the other pairs of spans is ignored. 

3. Interface disconnected on SIDE A: 

>>> SIDE A 


LINK#: 0100 STATE: LOF+LOS 


LINK#: 0200 STATE: CONNECTED PEER: SIDE_B 

RX: NO ALARM TX: LOF+LOS 

-------------------------------------------------------------------- 

>>> SIDE B 


LINK#: 0200 STATE: TX AIS 


LINK#: 0100 STATE: CONNECTED PEER: SIDE_A 

RX: LOF+LOS TX: 

-------------------------------------------------------------------- 

3-10 Memotec Inc.


NOTE: Alarm indications (LOF+LOS) are provided on the TX side of SIDE A and the 

RX side of SIDE B. 

4. On SIDE A, Link Management is disabled on the first span, but is enabled on 

another span: 

>>> SIDE A 





RX: TX: 

-------------------------------------------------------------------- 

>>> SIDE B 




LINK#: 0100 STATE: NOT CONNECTED PEER: SIDE_A 

RX: TARGET NOT FOUND TX: CONNECT REQUEST 

-------------------------------------------------------------------- 

NOTE: On SIDE B the message TARGET NOT FOUND was received in response to 

the CONNECT REQUEST transmitted. This response is possible only if a 

management channel is still alive on the system. The NOT CONNECTED state 

is used to describe the management of this link pair. 

5. On SIDE A, Link Management is disabled on all spans: 

>>> SIDE A 





RX: TX: 

-------------------------------------------------------------------- 

>>> SIDE B 




LINK#: 0100 STATE: PROG PEER: SIDE_A 

RX: CONNECT CONF NAK TX: CONNECT REQUEST 

-------------------------------------------------------------------- 

Memotec Inc. 3-11


NOTE: To determine that the actual (true) management channel is not functional for 

any spans, look at the RX statistic for SIDE B. Here, the CONNECT 

REQUEST transmitted did not receive a response (unlike the situation in 

example 4, above). Once again, the management state is PROG. 

6. On SIDE B, Link Management is disabled on all spans: 

>>> SIDE A 





RX: TX: 

-------------------------------------------------------------------- 

>>> SIDE B 

DCME 




LINK#: 0100 STATE: CONN PEER: SIDE_A 

RX: LINK MANAGEMENT DISABLED TX: NO ALARM 

-------------------------------------------------------------------- 

• Modified: The PHONE profile for backup links now accepts the # and + characters 

in addition to the numeric keys, -, D, T, * and the space character. In backup 

applications the # character can be used to inform the modem that the dial string 

has ended. 

• Resolved: The problem where the Link rank in the group parameter would not 

properly control the return of traffic to a higher priority link that came back up 

after a failure. 

• Resolved: An SDM-9620 configured with 8 full spans of data using single-line 

command entry, no longer reboots after a span LINK is disabled. Now a DIS- 

ABLE/ENABLE operation on all channels to reassign the TDM timeslots can be 

carried out without rebooting the unit. 

• Resolved: Potential problems with Frame Relay processing have been repaired. 

• Resolved: The problem where SE (Signaling Engine) alarms occurred when 

DCME voice was configured on an SDM-9620 span, and then the Framer type 

setting was changed from E1 to T1. Whenever the Framer type is changed, all 

current calls are shut down, and all current channels are disabled (Protocol reset 

to OFF). Now the number of channels affected corresponds to the number supported 

by the initial Framer type rather than the newly configured Framer type 

(24 for T1, or 31 for E1). 

3-12 Memotec Inc.

Ethernet/IP 


• Added: The Ethernet port drivers now support 2 MAC addresses to improve the 

reliability of a redundant system at startup. The first is the current BIA or MAC 

address (if configured) and the second is the redundant MAC address, which is 

used when the unit sends an IP frame with the redundant IP address as the source 

IP address. 

To activate the redundant MAC address on an Ethernet port: 

- Set the Ethernet port parameter Redundancy MAC address active to YES 

- Configure the unit for Redundancy 

- The unit must also be in operating state. If it is in STANDBY or REPLACED 

mode, the redundant MAC address state will be displayed as inactive. 

NOTE: In addition to the above requirements, the redundant MAC address will 

be used on transmission only if the source IP address is a redundant IP 

address configured on the Ethernet port. The redundant MAC address is 

used on reception to validate a received frame regardless of the destination IP 

address in the IP frame. 

- Refer to “Redundancy” on page 3-15 for a description of other changes to the 

configuration of Ethernet ports in a redundant system. 

- The DISPLAY option of the ARP command has changed, as well. Now the 

LAN interface is included in the ARP table to distinguish cases where more 

than one ARP entry has the same destination IP address. Refer to “Modified: 

The DISPLAY operation of the ARP command now includes the port index 

of the LAN interface. This distinguishes entries in the ARP cache with the 

same destination address, and resolves a problem with SNMP.” on page 3-14. 

• Added: Statistics for displaying the current status of the redundant MAC address 

in both the Display States (DS) command and statSystem for SNMP. The display 

includes the redundant MAC address and its current status: inactive or active. 

DS Command on an SDM-8400: 

UNITAF1>DS 


Item (GLOBAL/PORT/PVC/REDUNDANCY,def:GLOBAL) ? PORT 

PORT ETH> Protocol..................................ETHERNET 

PORT ETH> Interface.................................10BASET 

PORT ETH> Speed.....................................100M 

PORT ETH> Duplex mode...............................HALF 

PORT ETH> Operating mode............................L- 

PORT ETH> State.....................................OPEN 

PORT ETH> Network address...........................00200AB0AFEF 

PORT ETH> Redundancy MAC address....................00005E000000 

(inactive) 

PORT ETH> Burned-in address.........................00200AB0AFEF 

Memotec Inc. 3-13


PORT ETH> Number of deferred transmissions..........0 

PORT ETH> Number of collision frames................0 

DS command on an SDM-9620: 

AF.9620-2>DS 


Item (GLOBAL/PORT/REDUNDANCY/SPAN,def:GLOBAL) ? PORT 

PORT ETH 1> Protocol................................ETHERNET 

PORT ETH 1> Interface...............................10BASET 

PORT ETH 1> Speed...................................100M 

PORT ETH 1> Duplex mode.............................HALF 

PORT ETH 1> Operating mode..........................L- 

PORT ETH 1> State...................................OPEN 

PORT ETH 1> Network address.........................00200CE014F1 

PORT ETH 1> Redundancy MAC address..................00005E000000 

(inactive) 

PORT ETH 1> Burned-in address.......................00200CE014F1 

PORT ETH 1> Number of deferred transmissions........0 

PORT ETH 1> Number of collision frames..............0 

PORT ETH 2> Protocol................................ETHERNET 

PORT ETH 2> Interface...............................10BASET 

PORT ETH 2> Speed...................................UNKNOWN 

PORT ETH 2> Duplex mode.............................HALF 

PORT ETH 2> Operating mode..........................-- 

PORT ETH 2> State...................................OPEN 

PORT ETH 2> Network address.........................00200CCE014F1 

PORT ETH 2> Redundancy MAC address..................00005E000001 

(active) 

PORT ETH 2> Burned-in address.......................00200CE014F2 

PORT ETH 2> Number of deferred transmissions........0 

PORT ETH 2> Number of collision frames..............0 

The equivalent information can be retrieved in SNMP using new entries in the 

statSystem table: 

- statSystemRedunMacAddrState1 

- statSystemRedunMacAddr1 

- statSystemRedunMacAddrState2 

- statSystemRedunMacAddr2. 

• Modified: An ARP request is now sent to the ARP cache 1 minute before the 

Time To Live (TTL) ends if the NetPerformer needs to send a packet to a specific 

MAC address. This ensures that the entry for this MAC address will not be 

erased from the ARP table. It also prevents traffic bursts when ARP entries are 

renewed. 

• Modified: The DISPLAY operation of the ARP command now includes the port 

index of the LAN interface. This distinguishes entries in the ARP cache with the 

same destination address, and resolves a problem with SNMP. 

SDM-9620-BOTTOM>ARP 

3-14 Memotec Inc.

ARP CACHE 

Operation (DISPLAY/CLEAR,def:DISPLAY) ? 


The ARP cache has 4 entry(ies) used on a maximum of 300 entries. 

PORT DESTINATION MAC ADDRESS STATE TTL 

LAN1-R1 002.222.000.002 00200CE014F1 RESOLVED 3 h 




NOTE: The notation for a redundant IP address on the SDM-9620 is, e.g. LAN1-R1 

for Redundancy IP address 1 on port ETH1. See the next section for information 

about redundant IP addresses. 

• Resolved: The problem on the SDM-9620, where the backplane connection 

would stop when the Physical connectivity detection parameter on port ETH2 

was set to ENABLE and the port lost its connectivity. Now a loss of link connectivity 

on port ETH2 does not affect the backplane connection. 

• Resolved: DHCP is now working properly on an Ethernet port. 

• Resolved: DHCP is now working properly on the SDM-9620. 

• Resolved: The problem where a configured IP Static entry would not come up 

when the IP static route was configured with a cost higher than 0 and an alternate 

route with a lower cost took over the static route, and then failed. Now the IP 

static route comes up automatically when the PVCR link providing the next hop 

rises up. 

• Resolved: The problem where a NetPerformer unit configured for bridging could 

not be pinged, due to a problem with ARP cache management. 

• Resolved: On the SDM-9620 (Rev. 2 board) invalid static entries in the ARL 

table for the Ethernet switch have been resolved through hardware adjustments 

and reprogramming. 

Redundancy 

• Added: An Ethernet port can now be configured with a redundant MAC address 

and up to 2 redundant IP addresses. These redundant addresses can be used in a 

1:1 redundancy setup to ensure that the host on the Ethernet port does not lose 

gateway access when one unit replaces another. 

- IP addresses on the Ethernet ports can be configured on the same subnet 

- Redundant IP addresses are active only when the unit is operative 

- When the unit is in STANDBY mode or is replaced, its redundant IP addresses 

and redundant MAC addresses are deactivated. 

Memotec Inc. 3-15


The following parameters have been added to the configuration of an Ethernet 

port for the redundant MAC and IP addresses: 

- Redundancy MAC address active (Configuration file: [iflan] RedunMacAddrActive; 

SNMP: iflanRedunMacAddressActive): 

YES: (default value) Allows for configuration of a redundant MAC address 

on this Ethernet port. This MAC address will be used as the source address 

instead of the default BIA or configured physical MAC address. 

Set this parameter to YES in a redundant system. This allows the two redundant 

units to have the same MAC address and be on the same LAN. The unit 

that is currently active is the one that uses the redundant MAC address. 

NO: (default value) A redundant MAC address is not available for this Ethernet 

port. 

- Redundancy MAC address (Configuration file: [iflan] RedunMacAddr; 

SNMP: iflanRedunMacAddress): 

Determines the redundant MAC address that the Ethernet port will use as 

source address when the unit is operating in a redundant system. 

1:1 Redundancy must be fully configured on the SDM-9620 (using SE/ 

REDUNDANCY) for this parameter to take effect, including the unit Role, 

fault criteria, Backup name and remote unit identification. 

� Range of hexadecimal values: 00005E000000 to 00005E0000FF 

This range of MAC addresses is the Ethernet address block that the Internet 

Assigned Numbers Authority (IANA) has specified for unicast 

address assignments or other special purposes. 

� Default value: 00005E000000 

Caution: Be careful when configuring this parameter. With the 

exception of the redundant unit, the Redundancy MAC address 

must be different from the MAC address of other units on the same 

LAN if the other units can operate at the same time as the one you 

are configuring. 

- Redundancy IP address 1 (Configuration file: [iflan] RedunIpAddress1; 

SNMP: iflanRedunIpAddress1): 

Specifies the first redundant IP address that is activated by the Redundancy 

feature when the unit is operative. 

� IP address value: class A, class B or class C IP address in x.x.x.x 

format 

� Default value: 0.0.0.0 

- Redundancy subnet mask 1 (number of bits) (Configuration file: [iflan] 

SNRedunMask1; SNMP: iflanRedunSNMask1): 

3-16 Memotec Inc.


Specifies the subnet mask for the first redundant IP address, in number of bits. 

For example, the value 8 corresponds to 255.0.0.0, and 16 corresponds to 

255.255.0.0. 

� Range of integer values: 0 to 32 bits 

� Default value: 8 

- Redundancy IP address 2 (Configuration file: [iflan] RedunIpAddress2; 

SNMP: iflanRedunIpAddress2): 

Specifies the second redundant IP address that is activated by the Redundancy 

feature when the unit is operative. 

� IP address value: class A, class B or class C IP address in x.x.x.x 

format 

� Default value: 0.0.0.0 

- Redundancy subnet mask 2 (number of bits) (Configuration file: [iflan] 

SNRedunMask2; SNMP: iflanRedunSNMask2): 

Specifies the subnet mask for the second redundant IP address, in number of 

bits. For example, the value 8 corresponds to 255.0.0.0, and 16 corresponds to 

255.255.0.0. 

� Range of integer values: 0 to 32 bits 

� Default value: 8 

• Added: The Transition delay (s) parameter has been added to the Redundancy 

Criteria configuration (SE/REDUNDANCY/CRITERIA) on a Secondary Master 

unit only. When two redundant units return to NORMAL mode from BACKUP 

mode, the Transition delay timer must expire before the Secondary Master can 

detect a problem requiring a return to BACKUP mode. 

- Range of values: 0 to 1000 s 

- Default value: 60 s 

- Configuration file: [Redundancy] TransitionDelay; SNMP: redundancyCriteriaTransitionDelay 

NOTE: Formerly, the Startup delay was used for this delay. The Startup delay is now 

activated only on startup, and is used exclusively for processes that must be 

executed on startup. The Startup delay must expire before the Transition 

delay can be activated. 

Features activated after expiration of the Startup delay (on both the Primary Master 

and Secondary Master units): 

- REDUN+BYPASS interfaces that are configured in AUTO STANDBY mode 

- The new RTM on the SDM-9620 which provides 1:1 redundancy 

- Redundant IP addresses and redundant MAC addresses on the LAN port. 

Memotec Inc. 3-17


Feature activated after expiration of the Transition delay (on the Secondary Master 

unit only): 

- Detection of major faults triggering a switch to BACKUP mode. 

• Added: A redundant link can now be configured for transparent protocols on digital 

interfaces, including HDLC and PASSTHRU. From the SLOT/CHANNEL 

submenu of the Setup (SE) command, set the Redundant link parameter to YES 

to configure a transparent channel as a redundant link. 

• Modified: On the redundant RTM for the SDM-9620, the ALM LED on the left 

side of the E1/T1 port connector serves as an alarm LED, rather than an indicator 

of activity on the port. 

When a unit detects a redundant RTM, the extended global parameter 

ALARMONT1E1 is removed from the EP list and is hard configured so the LEDs 

show the alarm status of the span instead of E1/T1 activity. 

The following table shows how the LEDs on the redundant RTM should be interpreted: 

ALM LED SYNC LED Indication 

Off Off Either the port is not configured (State = DIS- 

ABLED) or it did not pass the power-up self test 

and is not synchronized 

• Resolved: The problem in a redundant system in NORMAL mode using 

PVCRoIP PVCs, where the state of the redundant PVC links would not change 

from DOWN or CALL to STANDBY when the Role of the Secondary Master was 

changed from DISABLED to SECONDARY MASTER. Only one redundant unit 

can be up at a time. The state of the other unit is STANDBY. 

Traffic Capture 

Green The digital link is synchronized 

Yellow Off A Red Alarm has been detected on the port 

Green A Yellow Alarm has been detected on the port 

Table 0-2: 

• Added: The capture of PVCR Link Management traffic, using the Setup Capture 

(SC) command. To capture this traffic, set the Capture Link Management parameter 

to YES. 

SDM-9230>SC 

SETUP CAPTURE 

Capture ITEM (DSP/PORT/PU/PVC/SE/SLOT/SVC,def:SLOT) ? 

Capture Link Management (NO/YES,def:YES) ? YES 

SLOT> Slot number (1,def:1) ? 1 

SLOT> Channel Number (100/150/ALL,def:150) ? ALL 

Capture another item, please confirm (NO/YES,def:NO) ? 

Capture direction (def:BOTH) ? 

3-18 Memotec Inc.


Capture mode (def:CONTINUE) ? 

Capture ending (def:MANUAL) ? 

Capture activation (def:FOREGROUND) ? 

Start Capture (def:YES) ? 

The capture is activated in Foreground, use BACKSPACE to continue 

in 

Background 

Baseboard: 3, 0 Kb ( 0 %) 

The capture is terminated 

• Modified: In the Setup Capture (SC) command, the Trigger on DSP error parameter 

is now configured with hexadecimal values, rather than decimal. This parameter 

appears at the console when the Trigger type is set to ERROR LOG. Since all 

values in the Error Log are hexadecimal, this change eliminates the need for conversion. 

• Modified: For the Setup Capture (SC) command, it is now possible to trigger the 

capture ending on the extended ERROR LOG coming from the host. This permits 

stopping a traffic capture when underflows, overflows, other trunk errors or 

extended DSP errors occur. In addition, the occurrence of the specified trigger no 

longer stops a capture when the Capture ending is set to MANUALLY. 

• Resolved: The display of DSP traffic captured with the Setup Capture (SC) command 

now includes packets sent to the DSP as well as those received from the 

DSP. 

• Resolved: The problem where the SILENCE DETECT statistic for a DSP capture 

would not indicate the presence of silence packets for an ACELP-CN voice channel 

configured with a non-zero Comfort Noise Level. 

Loopback and Troubleshooting Capabilities 

• Added: Two new loopback capabilities can be configured on E1/T1 interfaces, 

using the Loopback parameter of the SE/SPAN/LINK or SE/SLOT/LINK menu: 

- LOCAL (INTERNAL) loopback: The data stream normally transmitted on 

the line is looped, inside the framer, to the receive side. 

- TSI-REMOTE (EXTERNAL) loopback: All timeslots on the span are connected 

to themselves within the timeslot interchange (TSI). The data received 

on each timeslot of the line is looped back using the same timeslot on the 

transmit side. 

Before the addition of these loopback types, only REMOTE (external) loopback 

could be selected with the Loopback parameter. 

In addition, loopback capabilities are now available through the new global 

extended parameter, TDMLOOPBACK, which can be set to: 

- REMOTE (EXTERNAL) loopback: All configured timeslots of all spans are 

looped back externally. The received data steam from the line is looped to the 

transmit side at the TDM level. 

Memotec Inc. 3-19


- LOCAL (INTERNAL) loopback: All configured timeslots of all spans are 

looped back internally. The data stream normally transmitted on the line is 

looped to the receive side at the TDM level. 

- TSI-REMOTE (INTERNAL) loopback: Available only on the SDM- 

9620. All configured timeslots of all spans are connected to themselves 

inside the timeslot interchange. The data normally transmitted on each timeslot 

is looped back using the same timeslot on the receive side. 

- RESET: To return the GSM channels to normal operations, that is, the channels 

are reenabled and all connections are reestablished. 

• Added: Several improvements to the error log (ELOG): 

- The default size of the ELOG has been increased from 512 to 5120 entries 

- The ELOG size can be increased further using the global extended parameter, 

ELOGSIZE. The default value, 120 KB, allows for 5120 entries. The maximum 

value, 1200 KB, allows for 51200 entries. 

If the ELOG size is reduced or if the ELOG is filled (it has wrapped 

around at least once), then all ELOG contents are erased. 

- A new command, Erase Error Log (EELOG), resets the error log and deletes 

all of its contents 

- A change of clock source is now indicated in both the error log and the alarm 

log 

- You can now configure what information will be stored in the log using the 

SE/ELOG command. Up to 8 error sources are allowed. 

Notes: 

� Management and Global sources cannot be filtered out 

� Set the Log all unavailable seconds (US) entries filter to NO to 

prevent a disconnected (but enabled) link to fill the log with 

recurrent US entries. Only some of the entries at predefined 

increments are stored, e.g. 50, 60, 100, 200, 500, 1000, 2000 

� The Log extended DSP errors/events, Log PVC errors/events 

and Log UDP errors/events filters replace the earlier ELOG 

COUNTERS global extended parameter. 

• Added: The Loopback Test (LT) command, originally available for serial ports 

only, has been extended to E1/T1 interfaces. Use this command to generate and 

detect a test pattern on a span that is externally looped back. Errors in the test pattern 

indicate connection problems with the customer's equipment. 

EUROPA>LT 

LOOPBACK TEST 

System under test (SERIAL/FRAMER,def:SERIAL) ? FRAMER 

Type of test (PATTERN/TEMPORARY LOOPBACK, 

def:PATTERN) ? PATTERN 

SPAN> Span number (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/ALL,def:1) ? 7 

Pattern type (2^15-1 /2^20-1 /2^11-1 ,def:2^15-1 ) ? 

Number of error insertions during the test (0-50,def:0) ? 2 

Test duration (sec) (10-86400,def:10) ? 120 

3-20 Memotec Inc.

Example of a 

PATTERN test: 

LOOP Background (NO/YES,def:NO) ? 


New LT command parameters and values include: 

- System under test: Select FRAMER to execute the loopback test on an E1/T1 

span 

- Type of test: 

� PATTERN: Applies a test pattern on the span (specified by 

Pattern type) 

� TEMPORARY LOOPBACK: Puts the span in remote loopback 

mode for a limited amount of time. The remote unit that is 

accessed through the E1 or T1 PVCR link is put into temporary 

loopback mode, and after the timeout (set with the Loopback 

duration parameter), the PVCR link comes back to normal 

operation automatically. This is ideal for executing a brief 

remote loopback test without having to change the LINK 

configuration. 

- Span number: Select the span you want to test 

- Pattern type: Choose from 3 test patterns that the built-in pattern tester can 

send over the span. 

The notation 2^15-1 represents 2 15 -1, 2^20-1 represents 2 20 -1, and so on. 

- Test duration (sec): From 10 seconds (default value) to a full day (86400 seconds) 

- LOOP Background: 

� YES: The test results will be compiled in background mode 

� NO: Foreground mode. The test results are displayed every 5 

seconds on the screen. 

EURO>LT 

LOOPBACK TEST 

System under test (SERIAL/FRAMER,def:FRAMER) ? FRAMER 

Type of test (PATTERN/TEMPORARY LOOPBACK, 

def:PATTERN) ? PATTERN 

Display previous framer loopback tests results (NO/YES,def:NO) ? 

SPAN> Span number (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/ALL,def:1) ? 3 

Pattern type (2^15-1 /2^20-1 /2^11-1 ,def:2^15-1 ) ? 2^15-1 

Number of error insertions during the test (0-50,def:0) ? 1 

Test duration (sec) (10-86400,def:120) ? 

LOOP Background (NO/YES,def:NO) ? 

FRAMER LOOPBACK TEST ON SPAN 3 

Time(s) Inserted errors Detected errors Err rate Pattern out of 

sync 

======= =============== =============== ======== 

=================== 

5.000 0 0 0 NO OCCURENCE 



Memotec Inc. 3-21


Example of 

configuring a 

TEMPORARY 

LOOPBACK: 










65.000 1 1 7.8E-09 NO OCCURENCE 

70.000 1 1 7.2E-09 NO OCCURENCE 

75.000 1 1 6.7E-09 NO OCCURENCE 

80.000 1 1 6.3E-09 NO OCCURENCE 

85.000 1 1 5.9E-09 NO OCCURENCE 

90.000 1 1 5.6E-09 NO OCCURENCE 

95.000 1 1 5.3E-09 NO OCCURENCE 

FRAMER LOOPBACK TEST ON SPAN 3 

Time(s) Inserted errors Detected errors Err rate Pattern out of 

sync 

======= =============== =============== ======== 

=================== 

100.000 1 1 5.0E-09 NO OCCURENCE 

105.000 1 1 4.8E-09 NO OCCURENCE 

110.000 1 1 4.6E-09 NO OCCURENCE 

115.000 1 1 4.4E-09 NO OCCURENCE 

120.000 1 1 4.2E-09 NO OCCURENCE 

120.001 1 1 4.2E-09 NO OCCURENCE 

EURO> 

NOTE: Statistics in the Err rate column indicate the number of bits in error divided 

by the total number of bits sent, in x.xE-xx format. The Pattern out of sync 

column indicates whether the pattern was lost at any point during the test. 

UNIT>LT 

LOOPBACK TEST 

System under test (SERIAL/FRAMER,def:FRAMER) ? 

Type of test (PATTERN/TEMPORARY LOOPBACK,def:PATTERN) ? TEMPORARY 

LOOPBACK 

SPAN> Span number (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/ 

ALL,def:1) ? 7 

Loopback duration (sec) (10-86400,def:10) ? 100 

• Added: If an SDM-9620 span is configured in Loopback, a display of the current 

Loopback state is included with the Error Log (ELOG) and Display Link Status 

(DLS) command displays: 

- The ELOG command displays LOOPBACK ACTIVATED for the span: 

2008/03/19-11:37:09 PORT 300 LOOPBACK ACTIVATED ALARM 

3-22 Memotec Inc.

Example: 


- The DLS command displays STATE: LOOP for the local interface of the 

span: 

--[ LOCAL INTERFACE ]-------------------------------------------- 

LINK# 0300 STATE: LOOP 

The Loopback condition discussed here has nothing to do with the Loopback 

Test (LT) command; rather, the Loopback parameter configured on a span. 

• Modified: On the SDM-9606 and SDM-9620 blades, the LED status of E1/T1 

ports is now updated every 10 seconds, rather than on a change of status only. For 

a 1:1 Redundancy application on the SDM-9620, LEDs on the redundant RTM 

are updated only when the unit state of the corresponding SDM-9620 blade is IN 

USE or DEACTIVATION IN PROGRESS, since in all other cases the redundant 

RTM is being used by the other SDM-9620 blade. 

• Resolved: The SDM-9620 no longer reboots in a loop after enabling the Log 

extended DSP errors/events parameter in the ELOG submenu of the Setup (SE) 

command. 

Legacy Protocols 

• Added: Two new extended port parameters can be used on the SDM-8400 to permit 

the transmission of DLE packets on ports configured with the COP protocol 

where the extended port parameter COPSPOOF must be set to NO, and DLE 

SYN ENABLE must be set to YES. 

This application requires the configuration of the DLE ETX and DLE ETB characters, 

which are sent without change over the port: 

• To set the DLE ETX character, enter the following at the console command 

prompt: 

EP PORT n ETXCAR XX 

where: XX is a hexadecimal value 

• To set the DLE ETB character, enter the following: 

EP PORT n ETBCAR XX 

where: XX is a hexadecimal value 

UNIT>EP PORT 3 ETBCAR 83 

EXTENDED PARAMETERS 

PORT 3> (ETBCAR) ETB character (hex).............83 

REMARK: To make this parameter effective, you have to turn off the 

port 

UNIT>EP PORT 3 ETXCAR 26 


PORT 3> (ETXCAR) ETX character (hex).............26 

REMARK: To make this parameter effective, you have to turn off the 

port 

UNIT>EP 

Memotec Inc. 3-23



IP> (MULTIHOMEDTYPE) Multihomed type.............DISABLED 

PORT 1> (BLOCSIZE) Block size....................32 

PORT 1> (DLESYN) Enable..........................YES 

PORT 3> (BLOCSIZE) Block size....................32 

PORT 3> (DLESYN) Enable..........................YES 

PORT 3> (ETBCAR) ETB character (hex).............83 

PORT 3> (ETXCAR) ETX character (hex).............26 

TCP Acceleration 

Resolved: The problem on an SDM-9230 installed with the TCP Acceleration licensed 

software option, where TCP throughput became very slow after a period of time. 

Alarms, Errors and Restarts 

• Resolved: The problem where the maximum number of data channels exceeded 

the permitted limit without just cause, due to timeslots that were previously configured 

on disabled spans. 

Now there is no residual trace of inactive channels in the configuration file, 

CFG.TXT, which permits configuration of new and valid channels. When a span 

is disabled (LINK Status set to DISABLE) all unused data channels are disabled 

with it (Protocol set to OFF). 

• Resolved: The problem where an alarm of type M=116 A=02 D=XXXXXXXX 

would sometimes occur when the Reset Unit (RU) command was executed 

before the Save Profile (SP) command had terminated. 

• Resolved: The file system is no longer subject to failure during a write command, 

with the error ERR_NOT_FOUND. 

• Resolved: The SDM-9230 no longer resets with an alarm of type M=66 A=300 

D=XXXXXXXX shortly after a GSM channel is configured in static mode (where 

timeslot autodetection is not activated). 

• Resolved: The problem on the SDM-9620, where the unit would reboot in a loop 

with alarms of type M=66 A=300 D=XXXXXXXX when the Physical connectivity 

detection parameter on port ETH2 was set to ENABLE and the port was not connected. 

• Resolved: The problem with an alarm of type M=109 A=34 D=XXXXXXXX indicating 

failure of the Signaling Engine watchdog, which occurred after multiple 

executions of the Reset Counters (RC) command. 

• Resolved: The problem that occurred on an SDM-9620 with more than 4 full 

GSM spans active, where the unit would display the message NOT ENOUGH 

MEMORY TO DISPLAY ALL ENTRIES with an alarm of type M=13 A=21 

D=XXXXXXXX when the DC/GROUP or DE/GROUP command was executed at 

the console. 

3-24 Memotec Inc.


• Resolved: The problem with an alarm of type M=66 A=300 D=XXXXXXXX, 

which occurred when resetting the profile of a dual framer interface (SE IFWAN 

x00-y81 RESET). 

• Resolved: STATUS IN SYNC alarms are no longer logged in the ELOG for disabled 

spans. 

• Resolved: The problem in an ISDN-BRI application, where the unit would reset 

with an alarm of type M=66 A=300 D=XXXXXXXX under the following circumstances: 

- The LINK Status was changed to DISABLE during bulk call tests on an 

ISDN-BRI 5ESS connection 

- A call was up on an ISDN-BRI interface and the link was disabled 

- A call was ringing and the ISDN-BRI or T1 Signaling mode was changed. 

• Resolved: The problem with an alarm of type M=13 A=20 D=XXXXXXXX that 

occurred on the SDM-9620 under certain trap and swapping conditions. 

• Resolved: The problem where an SDM-9620 would reset with an alarm of type 

M=66 A=300 D=XXXXXXXX when an ATM span with associated PVCs was disabled 

and then enabled. 

DSP Support 

• Added: A message now appears at the console when the DSP LOAD command is 

executed, indicating which DSP must be loaded first. 

This message is not required and does not appear when DSP1 or DSP2 is running. 

• Resolved: For the SDM-9220 and SDM-9230, GSM is no longer automatically 

loaded on the onboard DSP of an analog interface card (FXS, FXO or E&M) 

when the GSM A.bis/A.ter licensed software option is installed on the unit. This 

error would cause a DSP failure on the card. 

• Resolved: A DSP load now works properly on the first load attempt. Formerly, 

the first attempt would fail and only the second would succeed. 

Display, Console, and Configuration 

F4 R4 A3.6 IPMC >dv 

Memotec Inc. (c) 2008 

IPMC Revision 2.0.1 (A7) Build 11D7 03/25/08-17:00:54 

FRU V2 ADDR: 82 REV:1 ID:0 ASSY:3 / RTM PCB:1 REV:1 / RTM TOP PCB:1 

REV:1 

F4 R4 A3.6 IPMC > 

• Modified: Access to console commands is no longer permitted while the Save 

Profile (SP) command is in progress. A series of dots is displayed on the console 

screen to indicate that the command is being executed. 

Memotec Inc. 3-25


The user can press to access the command line prompt before the SP command 

has terminated. In this case, the message Save profile continuing in background 

is displayed at the console. 

• Modified: It is now possible to switch from the Incoming to the Outgoing window 

when executing the Display Timeslot Subchannels (DTSCH) command. 

Press the space bar to navigate between the two displays. 

• Modified: The Display Timeslot Subchannel (DTSCH) command now has the 

option of displaying information for both incoming and outgoing traffic at the 

same time. 

- When you execute the DTSCH command, select INCOMING & OUTGOING as 

the display type 

- To switch between incoming and outgoing traffic while the DTSCH command 

is running, press the space bar 

- Another alternative is to use the K extended menu, and press J to display one 

or both traffic directions. 

• Modified: The abbreviation KB is now used instead of Kb to represent kilobytes 

for the ELOGSIZE global extended parameter settings. 

• Modified: In the display of several statistics commands, an extra space between 

the type of interface and its number has been removed. 

For example, the Display Destination Table (DD) command formerly displayed 

numbered interfaces in the format WAN 1: 

AF.9230-2>DD 

DISPLAY DESTINATION TABLE 

The destination table has 2 entry(ies) 

DESTINATION VAL COST INTRF NEXT HOP AGE 

AF.9230-1 Y 0 WAN 1 AF.9230-2 0 s 

AF.9230-2 Y 0 LOCAL AF.9230-2 0 s 

The DD command now shows WAN 1 (with no extra space): 

AF.9230-1>DD 

DISPLAY DESTINATION TABLE 

The destination table has 2 entry(ies) 

DESTINATION VAL COST INTRF NEXT HOP AGE 

AF.9230-1 Y 0 LOCAL AF.9230-1 0 s 

AF.9230-2 Y 0 WAN 1 AF.9230-1 0 s 

The commands affected by this formatting change include: 

- Display PVC States (DPVC) 

3-26 Memotec Inc.


- Display PVC DLCI States (DDLCI) 

- Display Backplane Links (DBP) 

- Display Profile Information (DPROFILE) 

- Display Bridge Statistics (DB) 

- Display Bridge Addresses (DBA) 

- Display Destination Table (DD) 

- Display Routing Table (DR) 

- View Capture (VC) 

The following types of interfaces are now displayed without extra spaces before 

their number: 

- CSL i, e.g. CSL 1 

- WAN i, e.g. WAN 1 

- VCE i, e.g. VCE 101 

- SLOT i, e.g. SLOT 1 

- LNK i, e.g. LNK 100 

- PVC i, e.g. PVC 1 

- SVC i, e.g. SVC 1 

- PU i, e.g. PU 1 

- DSP i, e.g. DSP 1 

- DSP i.j, e.g. DSP 1.1 

- ETH i, e.g. ETH 1 

- BP i, e.g. BP 1 

- MAP i, e.g. MAP 1 

- PPPOE i, e.g. PPPOE 1 

- FRF8 i, e.g. FRF8 1 

• Modified: The configuration and display of the Stratum-3 clock module have 

changed. The affected boards are: 

- Part No. 100-1305-001: SDM-9230 Main Board Assembly Stratum-3 Clock 

Module, 0-50C, RoHS and 

- Part No. 100-1305-002: SDM-92X0, Main Board Assembly Stratum-3 Clock 

Module, 0-70C, RoHS 

The changes include the following: 

- To activate the clock, enter TCXO-S3 rather than STRATUM-3 when setting 

the global extended parameter OSCILLATORSOURCE: 

EP GLOBAL OSCILLATORSOURCE TCXO-S3 

Memotec Inc. 3-27


This value will take effect only if the Digital port clock source parameter is 

set to INTERNAL. 

- When the Stratum-3 clock is active, the Display Production Information (DPI) 

command now displays PBUS module: Precision clock rather than PBUS 

module type: 0x1. 

This information can be viewed by selecting P-CLOCK as the Module type. 

AF.BTS-1>DPI 

DISPLAY PRODUCTION INFORMATION 

Module (ALL/APPLICATION/MAIN/DSP/INTERFACE/P-CLOCK,def:ALL) ? P- 

CLOCK 

PBUS module: Precision clock 

PBUS module EEPROM information 

Serial number: B514471 

Working order: WXXXXXXXXXXXXXX 

Assembly: 100-1305-001 

Revision: 1 

Options: 

Test report: D4 00 00 01 03 03 09 81 

... 

• Modified: The values of the global extended parameter ECHOTAIL have been 

changed from msec to ms notation, and the warning to reset the unit after changing 

this parameter is now displayed as: 

WARNING: To apply the new Echo tail length, the unit 

must be reset. 

To do this, execute the Reset Unit (RU) command. 

• Modified: When there are no errors or problems with the file system, the File system 

status at bootup is now displayed as NO ERROR, e.g. using the Display 

Alarms (DA) or Display Version (DV) command. 

• Resolved: The problem on the SDM-9210, where the GPS interface was not displayed 

as a known interface type on execution of the Display Production Information 

(DPI), Display Hardware Information (DHI) and Signaling Engine 

Information (SEI) commands. Now the presence of this interface is indicated as: 

Slot 3 - GPS Mezzanine Interface 

• Resolved: The problem with the Transmitter rate and Receiver rate counters for 

a GSM PVC, where the PVC/MEAN option of the Display Counters (DC) command 

would show a markedly lower rate after a few minutes for traffic that was 

constant. 

• Resolved: The Display Call States (DCS) command now displays V120 for a 

voice channel configured for V.120 modem support. 

• Resolved: The GSM group parameter is now available for the configuration of a 

GSM PVC only. 

3-28 Memotec Inc.


• Resolved: The Global parameter Unit name no longer causes problems for a 

GSM application when configured at its maximum length of 16 characters. With 

this change, it is no longer necessary to limit the Unit name to a maximum of 

15 characters. 

MIB, SNMP and ACTview 3000 

• Added: SNMP traps are now sent whenever an Ethernet port configured with 

Physical connectivity detection set to ENABLE goes up or down. 

• Added: An SNMP trap is now sent whenever the Redundancy function logs the 

alarm NAME CONFLICT/GO TO BACKUP MODE. 

The Redundancy Criteria parameter Detect name conflict must be set to YES for 

this alarm and trap to occur. 

• Modified: The SNMP equivalents of the errors displayed with the SPAN option 

of the Display Errors (DE) command have been moved from statIfwanEntry to 

statIfslotEntry in the MIB, including the following: 

- statIfslotT1E1ESS Counter: Number of errored seconds (ES) 

- statIfslotT1E1SES Counter: Number of severely errored seconds (SES) 

- statIfslotT1E1SEF Counter: Number of severely errored frames (SEFS) 

- statIfslotT1E1UAS Counter: Number of unavailable seconds (UAS) 

- statIfslotT1E1CSS Counter: Number of controlled slip seconds (CSS) 

- statIfslotT1E1PCV Counter: Number of path code violations (PCV) 

- statIfslotT1E1LES Counter: Number of line errored seconds (LES) 

- statIfslotT1E1BES Counter: Number of bursty errored seconds (BES) 

- statIfslotT1E1DM Counter: Number of degraded minutes (DM) 

- statIfslotT1E1LCV Counter: Number of line code violations (LCV) 

- statIfslotCrcError Counter: Number of CRC errors 

- statIfslotFrameLenError Counter: Number of frame length errors 

- statIfslotAbortSequence Counter: Number of abort sequences 

- statIfslotNonAligOctets Counter: Number of non-aligned octets 

- statIfslotHdlcFramingErr Counter: Number of HDLC framing errors 

- statIfslotReturRxBuff Counter: Number of returned rx buffers 

- statIfslotChanRestarts Counter: Number of channel restarts 

• Modified: The values of the SNMP variable ifwanLinkRemotePort have been 

adjusted to support the SDM-9620, with the addition of links 500, 600, 700, 800, 

900, 1000, 1100, 1200, 1300, 1400, 1500 and 1600. This variable specifies the 

remote link number for a PVCR link management application. 

Memotec Inc. 3-29


• Resolved: The problem where ACTView 3000 could not retrieve or display the 

status of an SDM-9620 span configured for voice transmission. 

• Resolved: The SNMP values of ifwanPvcrManagementAlarmType are no longer 

offset by one. 

Other Changes 

Signaling Engine 

• Resolved: The problem where the HA*.bin file could not be sent from a NetPerformer 

unit to a PC using FTP or Zmodem file transfer. 

• Resolved: The SPI clock frequency can no longer go above the maximum value 

allowed for the Ethernet switch (2 MHz). Formerly, the SPI clock frequency 

could go as high as 2.048 MHz. 

• Added: The Display Performance Parameter (DPP) command, which provides 

cumulative performance statistics over a specific 15-minute period. 

- Performance statistics are collected for each span regarding errors, slips, etc., 

and are stored for 24 hours in a buffer containing 96 intervals of 15 minutes 

each. 

- With the DPP command, the statistics cumulated during any one of these 

intervals can be viewed from the NetPerformer console. The current interval 

is 0, and the oldest interval is 95 (if 24 hours have elapsed). The display 

includes the begin and end times of the interval in hours, minutes and seconds. 

In addition, the calculation of performance statistics and the nomenclature for the 

various types of link failure have been modified to make them compliant with 

RFC 4805. Refer to “Modified: The SNMP equivalents of the errors displayed 

with the SPAN option of the Display Errors (DE) command have been moved 

from statIfwanEntry to statIfslotEntry in the MIB, including the following:” on 

page 3-29 for a complete list of link errors and the new acronyms used in console 

displays. 

NOTE: The SPAN or SLOT option of the Display Errors (DE) command provides 

only the sum of performance statistics over the last 24 hours. A history of how 

the performance data evolved can also be deduced from the raw performance 

data in the ELOG. Only the DPP command provides cumulative statistics over 

a specific interval of time. 

3-30 Memotec Inc.


Example of DPP command execution on the SDM-9620: 

To execute the Display Performance Parameter command, enter DPP at the Net- 

Performer console command line. The initial display shows the statistics already 

gathered for the current interval: 

---------------- CURRENT INTERVAL (17:53:18 to NOW) -------------- 

-- 

SPAN| 1| 2| 3| 4| 5| 6| 7| 8| 9| 10| 11| 12| 13| 14| 15| 

16| 

------------------------------------------------------------------ 

ES| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

SES| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

SEFS| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

UAS| 0| 0| 0| 0| 0| 0| 0| 0| 6| 6| 6| 5| 5| 5| 5| 5| 

CSS| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

PCV| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

LES| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

BES| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

DM| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

LCV| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

------------------------------------------------------------------ 

GO TO INTERVAL: __ 

Compose the interval number (2 digits) to display. 

Use DEL to erase the first digit entered, ENTER to confirm it 

(interval < 10). 

Use LEFT and RIGHT arrow keys to go to the previous or next 

interval. 

Use any other key to exit. 

- The start time of the interval is in HH:MM:SS to NOW format 

- The errors (ES, SES, SEFS, etc.) are counted over this interval of time on all 

16 spans 

To change the interval, either: 

- Press the left (�) or right (�) arrow key, or 

- Enter the interval number at the GO TO INTERVAL prompt. The current interval 

is 00, and the oldest available interval is 95. 

The window is refreshed with the information for the new interval. The top line 

of this display shows the interval number, start time and end time (in HH:MM:SS 

to HH:MM:SS format): 

------------------ INTERVAL 4 (17:06:08 to 17:21:07) ------------- 

SPAN| 1| 2| 3| 4| 5| 6| 7| 8| 9| 10| 11| 12| 13| 14| 15| 

16| 

------------------------------------------------------------------ 

ES| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

SES| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

Memotec Inc. 3-31


SEFS| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

UAS| 0| 0| 0| 0| 0| 0| 0| 0| 5| 5| 5| 4| 4| 4| 4| 4| 

CSS| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

PCV| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

LES| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

BES| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

DM| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

LCV| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 

------------------------------------------------------------------ 






interval. 


Example of DPP command execution on the SDM-9230: 

The DPP command is executed in the same way for an SDM-9230, but its display 

is slightly different: 

------------ CURRENT INTERVAL (18:14:18 to NOW) ----------- 

SLOT| 1/1| 1/2| 2/1| 2/2| 3/1| 3/2| 

----------------------------------------------------------- 

ES| N/A| N/A| 0| 0| N/A| N/A| 

SES| N/A| N/A| 0| 0| N/A| N/A| 

SEFS| N/A| N/A| 0| 0| N/A| N/A| 

UAS| N/A| N/A| 0| 0| N/A| N/A| 

CSS| N/A| N/A| 0| 0| N/A| N/A| 

PCV| N/A| N/A| 0| 0| N/A| N/A| 

LES| N/A| N/A| 0| 0| N/A| N/A| 

BES| N/A| N/A| 0| 0| N/A| N/A| 

DM| N/A| N/A| 0| 0| N/A| N/A| 

LCV| N/A| N/A| 0| 0| N/A| N/A| 

----------------------------------------------------------- 






interval. 


- Here, the columns of the table represent the slot/port location on the SDM- 

9230, which has a maximum of 6 digital ports 

3-32 Memotec Inc.


- Some slots may be empty, or contain another type of interface card than the 

E1/T1 card. Error statistics for ports on these slots are shown as N/A (not 

applicable). In the example above, only slot 2 contains an E1/T1 interface 

card. 

• Modified: ELOG code 507 for a DSP error in a voice application (DCME) is now 

decoded with the proper text description: JITTER_BAD_PACKET_SEQ. 

• Modified: The maximum number of channels permitted in the Signaling Engine 

for the SDM-9220 and SDM-9230 has been increased from 128 to 192, to reflect 

the actual capacity of these products (maximum 6 E1 ports on the SDM-9230). 

With this change, it is now possible to configure more than 128 voice and data 

channels. However, the limitations of 128 data channels and 128 voice channels 

remain. For example, you can configure 128 data channels and 50 voice channels 

on a single unit, but not 130 data channels and 50 voice channels. 

• Modified: On a point-to-point circuit using SDM-9230 units connected to PBXs 

that use QSIG signaling, the following changes have been made to permit successful 

call placement and teardown on bearerless and non-bearerless calls 

(QSIG BRI): 

- All information elements (IEs) are now transported end-to-end 

- All STATUS messages are handled properly end-to-end 

IMPORTANT: The global extended parameter LOCALISDNSTATUS 

must be set to DISABLE for this to work. 

- RELEASE messages without prior DISCONNECT messages are now supported, 

permitting the transport of supplementary services 

- Multiple Facility IEs are now supported in all states. 

• Modified: On the SDM-9600, when one or both RTM handles are pulled: 

- The spans on that RTM are now detected as unavailable, and unavailable seconds 

(UAS) are immediately calculated on them 

- All Rx and Tx paths on all spans are set to OFF (high impedance) 

- The green LEDs on the corresponding front-mounted blade(s) are turned off 

- If a non-redundant (standard) RTM, the LEDs on the RTM are also turned off 

- If a redundant RTM: 

� The LEDs on the RTM are also turned off when the Redundancy 

State of the unit is IN USE or DEACTIVATION IN PROGRESS 

� The LEDs on the RTM do not change when the Redundancy 

State of the unit is NOT MANAGED, STANDBY, REPLACED, 

STARTING or ACTIVATION IN PROGRESS. 

NOTE: On the redundant RTM, there are 16 spans and 32 LEDs, with 2 LEDs per 

span. These LEDs are shared by the Primary Master and the Secondary Mas- 

Memotec Inc. 3-33


ter units. Since only one unit can operate at a time, the LEDs are dedicated to 

the unit currently in the IN USE or DEACTIVATION IN PROGRESS state. 

The Primary Master and Secondary Master are never be in those states at the 

same time: 

� When the Primary Master is IN USE, the Secondary Master is 

STANDBY 

� When the Secondary Master is IN USE, the Primary Master is 

REPLACED 

� When the Primary Master is DEACTIVATION IN PROGRESS, the 

Secondary Master is ACTIVATION IN PROGRESS 

� When the Secondary Master is DEACTIVATION IN PROGRESS, 

the Primary Master is ACTIVATION IN PROGRESS. 

Thus, the LEDs on the redundant RTM reflect the status of the Primary Master 

or Secondary Master unit that is currently IN USE or DEACTIVATION IN 

PROGRESS. 

• Resolved: The problem with an SE alarm that occurred in a EURO-ISDN application 

when a large number of ISDN events arrived at the same time, e.g. simultaneous 

disconnection of a large number of timeslots. 

• Resolved: The problem where the Display Production Information (DPI) command 

indicated the detection of a clock source on a link that was not enabled. 

This would occur when the main clock source failed and the system was looking 

for an alternate clock source. Now the link Status must be set to ENABLE to be a 

valid clock source. If no enabled links are available, the clock source reverts to 

INTERNAL instead of a disabled link. 

• Resolved: The problem where no dial tone could be heard on a particular type of 

ISDN phone connected to an ISDN-BRI S/T port on an SDM-9230. A Progress 

information element is now included in the SETUP ACK message to instruct this 

type of phone to open its audio path. 

3-34 Memotec Inc.

DSP Algorithms (Quadra File) 

QB 1.2.7 R01 


• Modified: The NetPerformer now supports an interframe size of 1 to 7 bits for 

HDLC signaling, and provides improved error processing. 

• Modified: Support of TCH/SIG switching, which has been implemented in order 

to remain synchronized on the TCH when the BTS or BSC allocates signaling 

channels dynamically. Before this change the destination would be dropped. 

• Resolved: V.120 transmissions are now fully supported by Quadra QB. 

• Resolved: The problem in a GSM application, where errors would sometimes 

occur at the beginning of AMR traffic transmission. 

QC 1.2.7 R01 

• Modified: The NetPerformer now supports an interframe size of 1 to 7 bits for 

HDLC signaling, and provides improved error processing. 

• Modified: Support of TCH/SIG switching, which has been implemented in order 

to remain synchronized on the TCH when the BTS or BSC allocates signaling 

channels dynamically. Before this change the destination would be dropped. 

• Resolved: The problem that occurred when running Fax Relay in a DCME application, 

where several errors would be logged in the ELOG file as soon as a fax 

call started. 

• Resolved: V.120 transmissions are now fully supported by Quadra QB. 

• Resolved: The problem in a GSM application, where errors would sometimes 

occur at the beginning of AMR traffic transmission. 

Memotec Inc. 3-35


3-36 Memotec Inc.

Bug Fixes in 10.4.1 R01 

4 

Memotec Inc. 4-1


TT Changes 

TT 3606 - Loss of connection at the SNMP agent 

Resolve a loss of connection at the SNMP agent while it acceded the huge statTssubTable, 

statGsmChRxTable, statGsmTsRxTable, statGsmSlotRxTable, statIfslotTable, 

statGsmChTxTable, statGsmTsTxTable and statGsmSlotTxTable tables. 

TT 1888 - Invalid GSM channel configuration 

Add warning message at the console when trying to configure a GSM channel with no 

DSP installed in the unit. 

TT 3811 - Memory leak causing a system restart 

Resolve a memory leak with the alarm "NOT ENOUGH MEM (00085350 00600010)" 

"STK 000863D4 00075454 00075C20" followed by an "M=66 A=300 D=0053247C" 

alarm and unit restart. 

TT 3835 - System restart with some HDLC traffic 

Resolve an "M=13 A=13 D=44F0891B" followed by a unit restart for buffer descriptor 

handling issue in the HDLC module for SCC ports. 

4-2 Memotec Inc.

Bug Changes 

Bug 4087 - FXS seizure detect time configuration 

Bug Changes 

Add an extended parameter allowing the change of the FXS seizure detect time. An 

application like autodial could need a change of this parameter. 

Console: EP VPORT p FXSSEIZUREDETECTTIME v, where p is the port number and 

v is the value in ms 

Range of value: 20 to 600 

Default value: 50 

Configuration file: [ifvce p] FxsSeizureDetectTime=v 

CLI example: NP>EP VPORT 201 FXSSEIZUREDETECTTIME 50 


VPORT 201> (FXSSEIZUREDETECTTIME) FXS seizure detect time (ms) 50 

NP> 

Bug 4097 - WarmStart and LinkStateInSync traps not sent 

Resolve SNMP traps like WarmStart and LinkStateInSync not sent just following a unit 

restart. At startup, the default gateway is often learned before all other routes learned by a 

routing protocol. The default gateway could be used for the sending of the SNMP traps. 

From 10.4.1 A12, the SNMP module will wait a minimum of 120 s before sending an 

SNMP trap on the default gateway letting time to the router for learning routes. 

Bug 4126 - Stuck in disconnect state with E&M Push-To- 

Talk 

Resolve a case where the answer side remains stuck in DISCONNECT state after a 

shutdown of the WAN link in an E&M Push-To-Talk application. 

Bug 4174 - E&M seizure detect time configuration 

Add an extended parameter allowing the change of the E&M seizure detect time. An 

application like redial could need a change of this parameter. 

Console: EP VPORT p EMSEIZUREDETECTTIME v, where p is the port number and v 

is the value in ms 

Memotec Inc. 4-3




Configuration file: [ifvce p] EMSeizureDetectTime=v 

CLI example: NP>EP VPORT 201 EMSEIZUREDETECTTIME 50 


VPORT 201> (EMSEIZUREDETECTTIME) E&M seizure detect time (ms) 50 


Bug 4217 - New Signaling mode choice for E1 

Add the choice "NONE (30 TS)" to the "Signaling mode" choice list to E1 framer ports. 

When the port is configured with this value, the behavior is similar to "NONE" signaling 

mode, except that the timeslot 16 is not used for a configuration with many consecutive 

timeslot. 

CLI example Where the E1 framer port is configured to use 30 timeslots from 1 to 31, but skipping the 

timeslot 16 

AF1.9230-2>SE 

SETUP 

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

IPX/MAP/ 

PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SS7/USER/ 

VLAN, 

def:SLOT) ? SLOT 

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

Port number (1/2,def:1) ? 1 

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

PORT 300> Framer Type (def:E1) ? 

PORT 300> Status (def:ENABLE) ? 

PORT 300> Clock recovery (def:DISABLE) ? 

GLOBAL > Digital port clock source (def:INTERNAL) ? 

PORT 300> Signaling mode (def:NONE (30 TS)) ? NONE (30 TS) 

PORT 300> Interface Mode (def:TE) ? 

PORT 300> Pcm encoding law (def:A-LAW) ? 

PORT 300> Hunt Group Sorting (def:RRA) ? 

PORT 300> Idle code (def:7E) ? 

PORT 300> Zero suppression mode (def:HDB3) ? 

PORT 300> Long Haul (def:NO) ? 

PORT 300> Impedance and Line Build Out (def:120 OHMS) ? 

PORT 300> Custom Waveform (def:DISABLE) ? 

PORT 300> CRC4 mode (def:ENABLE) ? 

PORT 300> International bit (def:ENABLE) ? 

PORT 300> Loopback (def:DISABLE) ? 

PORT 300> PVCR Link management (def:DISABLE) ? 


NP>SE 

SETUP 


4-4 Memotec Inc.

Bug Changes 

IPX/MAP/ 


VLAN, 




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

SLOT> Channel Number (301-331/ALL,def:301) ? 301 

PORT 301> Protocol (def:HDLC) ? PVCR 

PORT 301> Timeslot (def:1) ? 1 

PORT 301> Number of consecutive timeslots (1-30,def:30) ? 30 

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

PORT 301> Mode (def:DEDICATED) ? 

PORT 301> IP address (def:000.000.000.000) ? 

PORT 301> Subnet mask (number of bits) (0-32,def:8) ? 

{255.000.000.000} 

PORT 301> IP RIP (def:V1) ? 

PORT 301> IP RIP TX/RX (def:DUPLEX) ? 

PORT 301> OSPF (def:DISABLE) ? 

PORT 301> IP multicast active (def:NO) ? 

PORT 301> NAT enable (def:NO) ? 

PORT 301> IPX RIP (def:DISABLE) ? 

PORT 301> IPX SAP (def:DISABLE) ? 

PORT 301> IPX network number (def:00000000) ? 

PORT 301> Compression (def:YES) ? 

PORT 301> Remote unit (def:) ? 

PORT 301> Timeout (ms) (1000-30000,def:1000) ? 

PORT 301> Number of retransmission retries (1-1000,def:100) ? 

PORT 301> Maximum number of voice channels (0-10000,def:10000) ? 

PORT 301> Maximum Voice Channels If High Priority Data (0- 

10000,def:10000) ? 

PORT 301> Cell Packetization (def:YES) ? 

PORT 301> Filter (def:ALL) ? 

PORT 301> Use this port as default gateway (def:NO) ? 

PORT 301> Redundant link (def:NO) ? 

PORT 301> Allow load balancing (def:YES) ? 


Bug 4079 - Hook detect time configuration for E&M Push- 

To-Talk 

Add an extended parameter allowing the change of the E&M Push-To-Talk on hook detect 

time 

A PTT application generating a small pulse on the M-Lead could need a modification of 

this parameter. 

Console: EP VPORT p EMPTTONHOOKDETECTTIME v, where p is the port number 

and v is the value in ms 



Memotec Inc. 4-5


Configuration file: [ifvce p] EMPttOnHookDetectTime=v 

CLI example: NP>EP VPORT 201 EMPTTONHOOKDETECTTIME 10 


VPORT 201> (EMPTTONHOOKDETECTTIME) E&M ptt on hook detect time 

(ms) 10 


Bug 4172 - Call command issue with backup ISDN link 

Resolve an issue when using the CALL command to execute a manual CALL activation of 

a backup ISDN link 

CLI example NP>CALL 

ACTIVATE LINK 

Link number (1/101/201/202/203/204/205/206/207,def:207) ? 207 

Phone profile number (1-64,def:3) ? 3 

PHONE 3> Remote unit.............................AF1.9230-1 

PHONE 3> Next hop................................AF3.9220-1 

PHONE 3> Cost....................................1 

PHONE 3> Dialer type.............................ISDN 

PHONE 3> Type....................................BACK-UP 

PHONE 3> Remote number........................... 

PHONE 3> Remote subaddress....................... 

PHONE 3> Local number............................ 

PHONE 3> Local subaddress........................ 

PHONE 3> Number of links.........................3 

Link 207 manual activation, confirm (NO/YES,def:NO) ? YES 

Link 207 state: CALL 

Link 207 state: CALL 

Link 207 state: DATA 


NP>HANG 

DEACTIVATE LINK (1/101/201/202/203/204/205/206/207,def:207) ? 207 

Link 207 manual deactivation, confirm (NO/YES,def:NO) ? YES 

Link 207 state: HANG 



Link 207 state: OFF 


Bug 4325 - Memory leak with GSM PVC over IP 

Resolve a leak memory issue with the "NOT ENOUGH MEM" alarm followed by a unit 

restart with the alarm "M=66 A=300" caused by the use of a GSM PVC over IP. Each 

time that the GSM PVC over IP went down, there was a leak of memory. 

4-6 Memotec Inc.

Bug Changes 

Bug 4340 - Voice channels stuck when in transparent 

signaling 

Resolve an issue where the voice channels could stick in IDLE state in a DCME 

application using a transparent signaling configuration 

Bug 4369 - New "LDCD" voice compression algorithm 

Add support of the "LDCD" new voice compression algorithm for analog and digital 

ports. 

This CODEC allows passing the voice and signaling directly in the voice channel. 

CLI example: NP>SE 

SETUP 


IPX/MAP/ 


VLAN, 




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

SLOT> Channel Number (301-331/ALL,def:301) ? 301 

PORT 301> Protocol (def:OFF) ? LDCD 

VOICE 301> Timeslot (def:1) ? 

VOICE 301> DSP packets per frame 12345678 

VOICE 301> Packetization selection (Y/N) ? YNNNNNNN 

VOICE 301> Signaling type (def:NONE) ? 

VOICE 301> Hoot & Holler application (def:NO) ? 

VOICE 301> Local inbound voice level (db) (def:0) ? 

VOICE 301> Local outbound voice level (db) (def:-3) ? 

VOICE 301> Priority Level (0-10,def:0) ? 

VOICE 301> Echo canceller (def:ENABLE) ? 

VOICE 301> Double talk threshold (db) (def:6) ? 

VOICE 301> Echo suppressor (def:ENABLE) ? 

VOICE 301> Activation type (def:PREDEFINED) ? 

VOICE 301> Link down busy (def:NO) ? 

VOICE 301> TONE type: (def:DTMF) ? 

VOICE 301> TONE regeneration: (0-255,def:1) ? 

VOICE 301> TONE ON (ms) (30-1000,inc:10,def:100) ? 

VOICE 301> TONE OFF (ms) (30-1000,inc:10,def:100) ? 

VOICE 301> Pulse make/break ratio (30-50,inc:4,def:34) ? 

VOICE 301> Fax relay (def:FAX) ? 

VOICE 301> Maximum fax rate (def:14400) ? 

VOICE 301> ECM mode (def:DISABLE) ? 

VOICE 301> Modem relay (def:NONE) ? 

VOICE 301> Remote unit (def:NONE) ? 

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

VOICE 301> DTMF power ratio (5-100,def:5) ? 

VOICE 301> Enable DTMF Detection ON-TIME (def:NO) ? 

VOICE 301> Egress ANI operation mode (def:NONE) ? 

Memotec Inc. 4-7


VOICE 301> Egress CHANNEL ANI digits (def:) ? 

VOICE 301> Ingress ANI operation mode (def:NONE) ? 

VOICE 301> Ingress CHANNEL ANI digits (def:) ? 

VOICE 301> Redundant channel (def:NO) ? 

VOICE 301> V110 mode (def:DISABLE) ? 

VOICE 301> V120 mode (def:DISABLE) ? 


Bug 4370 - Support for Memotec/Comtech Ethernet MAC 

address 

Add support for 

• Comtech EF Data MAC address 00-06-B0 

• Memotec MAC address 00-20-87 

• 9-digit Comtech serial numbers 

Bug 4438 - Prevent filling up the Alarm log 

Add two extended parameters to prevent filling up the alarm log with "LINK x IN SYNC" 

and "LINK x OUT OF SYNC" alarms. 

When the restriction of logging those alarms is activated, the port will wait a validation 

delay before logging an "IN SYNC" alarm. If the port becomes "OUT OF SYNC" before 

the expiration of the timer, neither the "IN SYNC" nor the "OUT OF SYNC" alarms will 

be logged. If the port did not become "OUT OF SYNC" before the expiration of the timer, 

the "IN SYNC" alarm will be logged as usual. 

• Description: Setting this parameter at YES will restrict the number of "LINK x 

IN SYNC" and "LINK x OUT OF SYNC" alarms in the alarm log. 

• Console: EP PORT p RESTRICTSTATUSALARM v, where p is the port 

number (100, 150, 200 …) and v is the value 

• Choice of values: NO and YES 

• Default value: NO 

• Configuration file: [ifwan p] RestrictStatusAlarm=v 

CLI example: NP>EP PORT 300 RESTRICTSTATUSALARM YES 


PORT 300> (RESTRICTSTATUSALARM) Restrict status alarm YES 


• Description: Changing this value will affect the delay of the alarm restrictions 

• Console: EP PORT p RESTRICTSTATUSDELAY v, where p is the port 

number (100, 150, 200 …) and v is the value in second 

4-8 Memotec Inc.

• Value range: 0 to 120 

• Default value: 30 

• Configuration file: [ifwan p] RestrictStatusDelay=v 

Bug Changes 

CLI example: NP>EP PORT 300 RESTRICTSTATUSDELAY 45 


PORT 300> (RESTRICTSTATUSDELAY) Restrict status delay (s) 45 


Bug 4439 - Change of behavior for Delay before Call 

Deactivation field 

Change the way that the "Delay before call deactivation (s)" timer for WAN links in 

PVCR CALL-BKUP mode operate. 

Before, the port did not take care of link instabilities. When the primary link went down 

and rose up before the timer expiration, the secondary link in backup hung. The behavior 

has been changed to restart the timer when the primary link goes down to have a good 

operation of the primary link for the whole period. 

Bug 4453 - Secondary link issue 

Resolve an issue where the secondary link did not rise up after a unit restart when the 

primary PVCR link remains down. 

Bug 4545 - Better control of phone settings for backup link 

Add two parameters in the phone profile to restrict the application of the phone settings to 

a specific backup link. 

• Console: Activate on a specific link 

• Values: NO, YES 

• Default value: NO 

• Configuration file: [phone x] SpecLinkActive 

• SNMP: phoneSpecificLinkActive (1.3.6.1.4.1.727.7.2.7.2.1.14) 

• Console: Specific link number 

• Values: 1, 2, 3, 4, 5, 6, 7, 8, 100, 101, 102, 150, 200, 201, 202, 250, 300, 301, 

302, 350, 400, 401, 402, 450, 500, 550, 600, 650, 700, 750, 800, 850, 900, 950, 

1000, 1050, 1100, 1150, 1200, 1250, 1300, 1350, 1400, 1450, 1500, 1550, 1600, 

1650 

Memotec Inc. 4-9


• Default value: 1 

• Configuration file: [phone x] / SpecLinkNo 

• SNMP: phoneSpecificLinkNumber (1.3.6.1.4.1.727.7.2.7.2.1.15) 

CLI example AF1.9230-1>SE 

SETUP 


IPX/MAP/ 


VLAN, 

def:PHONE) ? PHONE 

Define phone profile for BACKUP links 

PHONE> Profile number (1-64,def:1) ? 1 

PHONE 1> Remote unit (def:AF1.9220-1) ? 

PHONE 1> Next hop (def:AF1.9230-2) ? 

PHONE 1> Cost (0-65534,def:1) ? 

PHONE 1> Dialer type (def:ISDN) ? 

PHONE 1> Type (def:BACK-UP) ? 

PHONE 1> Remote number (def:1150) ? 

PHONE 1> Remote subaddress (def:) ? 

PHONE 1> Local number (def:2150) ? 

PHONE 1> Local subaddress (def:) ? 

PHONE 1> Number of links (1-64,def:2) ? 

PHONE 1> Activate on a specific link (def:YES) ? YES 

PHONE 1> Specific link number (def:150) ? 150 

AF1.9230-1> 

Bug 4594 - Invalid alarm at start up with new modules 

Resolve an alarm at startup requiring a technical support for an issue related to interfaces, 

DSP and precision clock module when those modules come from the Comtech production 

and being registered with a serial number in the Comtech format. At initialization, the 

work order field is no more required when the registering information is entered in the 

Comtech format. The version 10.4.1 R1 still continued to validate this field while it 

shouldn't. This field being not configured, an alarm was generated. The version 10.4.1 R2 

does not validate this field anymore when the registering information is entered in the 

Comtech format. 

NOTE: This change was implemented in V10.4.1 R02. 

4-10 Memotec Inc.

Quadra QB/QC: Resolved in QB 1.2.7 A08 

Quadra QB/QC: Resolved in QB 1.2.7 A08 

TT 3819 - Maximum number of groups for GSM 

Increase the maximum number of groups for GSM application to 50. In 10.4.0 R8, the 

maximum number of destinations was 10. 

TT 3820/3822 - Issue in POSNET application at 2400 Bauds 

Resolve an issue in POSNET application at 2400 Bauds. When POSNET application is 

used, both modems exchange short packets during the channel is up. DSP tone detection 

program did not handle that situation properly and detect end of PASSTHRU mode 

prematurely. To fix this issue, the timers on encoding and/or decoding direction are set to 

zero always when signal is detected in opposite direction. 

TT 3823 and 3824 - Modem relay fix when using POS V.22 

Resolve an issue with modem relay while using the feature POS V.22. 

Bug 4098 - Memory fragmentation fix 

Resolve generation of "M=158 A=21 D=01000007" and "ATTEMPT x TO LOAD DSP 

y" alarms causes by the memory fragmentation. 

Memotec Inc. 4-11

REACH FURTHER. OFFER MORE. 

Contact Memotec: 

tel.: +1-514-738-4781 

e-mail: COE@memotec.com 

7755 Henri Bourassa Blvd. West 

Montreal, Quebec | Canada H4S 1P7 www.memotec.com

Release Bulletin NP V10.4.1R02 - Comtech EF Data

Create successful ePaper yourself

Delete template?

Save as template?