Harrisbroadcast NetXpress LX Manual

Installation and Operation Manual
Intraplex® NetXpress™
Audio IP Multiplexer & CM-30 IP Interface Module
NetXpress LX Multiplexer
CM-30 Common Module
MA-230 Module Adapter
Version 1.01
For NetXpress LX Version 1.03

Publication Information
©2014 GatesAir, Inc. . Proprietary and Confidential.
GatesAir considers this document and its contents to be proprietary and confidential. Except for making a
reasonable number of copies for your own internal use, you may not reproduce this publication, or any part
thereof, in any form, by any method, for any purpose, or in any language other than English without the written
consent of GatesAir. All others uses are illegal.
This publication is designed to assist in the use of the product as it exists on the date of publication of this manual,
and may not reflect the product at the current time or an unknown time in the future. This publication does not in
any way warrant description accuracy or guarantee the use for the product to which it refers.
GatesAir reserves the right, without notice to make such changes in equipment, design, specifications,
components, or documentation as progress may warrant to improve the performance of the product.
GatesAir reserves the right, without notice to make such changes in equipment, design, specifications,
components, or documentation as progress may warrant to improve the performance of the product.
Trademarks
® ® ® ®
AudioLink PLUS™, HD Link™, IntraGuide , Intraplex , NetXpress™, NetXpress LX™, STL PLUS , SynchroCast , and
SynchroCast3™ are trademarks of GatesAir Corporation. Other trademarks are the property of their respective
owners.
Customer Service Contact Information
www.gatesair.com
GatesAir
3200 Wismann Lane
Quincy, Il 62305 USA
For Technical Support including Service, Training, Repair and Service Parts:
www.gatesair.com/services/technical-support.aspx
Americas:
24/7 Technical Support +1 217 222 8200
Email tsupport@gatesair.com
Europe, Middle East and Africa:

Email tsupport.europe@gatesair.com
Asia:
Email tsupport.asia@gatesair.com
Version Date Revision History Editor
1.01* 6/21/12 Corrected AC power wattage in Power section. LD

Corrected default IP address on Table 3-2.
Updated section to reflect default system mode setting
change from E1 to T1. Added guidelines for determining
system mode needed.
Added port numbers for specific network protocols.
1 9/20/10 Developed manual. LD

No header
Table of Contents
Section 1 – Introduction ................................................................ 1-1
1.1 Key Features .................................................................................... 1-1
1.2 Manual Use ...................................................................................... 1-1
1.3 Manual Scope ................................................................................... 1-2
1.4 Components ..................................................................................... 1-2
1.4.1 Main Equipment Shelf ............................................................................1-2
1.4.2 CM-30 IP Interface Module......................................................................1-2
1.4.3 MA-230 Module Adapter .........................................................................1-4
1.4.4 Other Modules and Module Adapters ........................................................1-4
1.4.5 Indicator Lights .....................................................................................1-4
1.5 Web Browser User Interface .............................................................. 1-4
Section 2 – Functional Design........................................................ 2-1

2.1 Network Concepts and Considerations ................................................. 2-1
2.1.1 MTU throughout the Network ...................................................................2-1
2.1.2 DHCP Use .............................................................................................2-1
2.1.3 Routing Table Construction .....................................................................2-1
2.1.4 WAN Port Auto-negotiation......................................................................2-2
2.1.5 ICMP Support ........................................................................................2-2
2.1.6 IGMP Multicast ......................................................................................2-2
2.2 Streams........................................................................................... 2-3
2.2.1 Stream Types ........................................................................................2-3
2.2.2 Stream Addressing .................................................................................2-4
2.2.3 Multicast Group Addressing .....................................................................2-4
2.2.4 Telephony .............................................................................................2-5
2.2.5 Echo Cancellation ...................................................................................2-5
2.2.6 Packetization and Overhead ....................................................................2-6
2.2.7 Packet Jitter Compensation .....................................................................2-6
2.2.8 Packet/Stream Information Calculation.....................................................2-6
2.2.9 Stream Statistics ...................................................................................2-7
2.3 System Security ............................................................................... 2-7
2.3.1 NetXpress LX Login ................................................................................2-8
2.3.2 Management Protocols on an Interface .....................................................2-8
2.3.3 IP Access List Use ..................................................................................2-8
2.3.4 SNMP Communities ................................................................................2-8
2.4 NetXpress LX QoS ............................................................................ 2-9
2.4.1 COS Levels for Stream Data ....................................................................2-9
2.4.2 TOS Byte Marking for Outbound Stream Packets .......................................2-9
2.4.3 User-Defined TOS Byte Setting for Outbound SNMP and HTTP Packets .........2-9
2.5 NetXpress LX Internal TDM Busses ..................................................... 2-9
2.5.1 Compatibility with Intraplex TDM Channel Modules ....................................2-9
2.5.2 TDM Channel Loopbacks ....................................................................... 2-11
2.5.3 TDM Bus Mapping ................................................................................ 2-11
2.6 System Time-of-Day....................................................................... 2-12
GatesAir, Inc. i
Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual Table of Contents
Version 1.01
2.7 System Timing............................................................................... 2-12

2.7.1 Types of System Timing ....................................................................... 2-12
2.7.2 NetXpress LX Timing Scenarios ............................................................. 2-13
2.8 NetXpress LX System and FEC ......................................................... 2-17
2.9 Power ........................................................................................... 2-18
2.10 Voice Signaling .............................................................................. 2-18
2.10.1 RBS ................................................................................................... 2-19
2.10.2 CAS ................................................................................................... 2-19
2.11 Software Download ........................................................................ 2-19
2.12 Configuration Files Backup and Restoration ....................................... 2-19
2.13 Fault Detection and Reporting .......................................................... 2-20
2.13.1 Alarm Hierarchy .................................................................................. 2-20
2.13.2 Alarm History ...................................................................................... 2-20
2.13.3 SNMP Traps Use for Fault Reporting ....................................................... 2-20
Section 3 – Installation & Wiring ................................................... 3-1

3.1 Installation Preparation...................................................................... 3-1
3.1.1 Tools & Cables Required .........................................................................3-1
3.1.2 Equipment Unpacking & Inspection ..........................................................3-1
3.2 Installation ....................................................................................... 3-2
3.2.1 Shelf Installation ...................................................................................3-2
3.2.2 CM-30 Module Kit Installation..................................................................3-2
3.2.3 Channel Module Installation ....................................................................3-8
3.2.4 Power Supply Installation .......................................................................3-9
3.3 Wiring & External Connections ............................................................ 3-9
3.4 Power Application ........................................................................... 3-15
Section 4 – Configuration & Operation .......................................... 4-1

4.1 Download Current Software................................................................ 4-1
4.2 Configuration Process ........................................................................ 4-1
4.2.1 Connect and Log On to Access NetXpress LX Home Page ............................4-1
4.2.2 View System Mode .................................................................................4-2
4.2.3 Perform General Setup ...........................................................................4-2
4.3 NetXpress LX Pages ......................................................................... 4-13
4.3.1 Start at the NetXpress LX Home Page ..................................................... 4-13
4.3.2 Define & Review Fault Information ......................................................... 4-15
4.3.3 Configure the System ........................................................................... 4-20
4.3.4 Configure the Network ......................................................................... 4-34
4.3.5 Configure Streams ............................................................................... 4-46
4.3.6 Check Multiplexer Performance.............................................................. 4-56
4.3.7 Set Up Security ................................................................................... 4-68
4.3.8 Send Echo Requests ............................................................................. 4-72
4.3.9 Configure CM-30 Module ...................................................................... 4-72
4.3.10 Configure Individual Modules (TDM Modules) .......................................... 4-75
ii GatesAir, Inc.
Intraplex Products
Table of Contents NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
Section 5 – Testing & Troubleshooting ......................................... 5-1

5.1 Testing ........................................................................................... 5-1
5.1.1 General Status Test ...............................................................................5-1
5.1.2 CM-30 Alarm Test ..................................................................................5-2
5.1.3 Ping Test ..............................................................................................5-4
5.1.4 Streams Test ........................................................................................5-4
5.2 Troubleshooting ................................................................................ 5-6
5.2.1 Channel Module Addition ........................................................................5-6
5.2.2 Web Browser Interface ...........................................................................5-6
Section 6 – Specifications .............................................................. 6-1

6.1 Detailed Specifications ...................................................................... 6-1
6.1.1 NetXpress LX IP Multiplexer ....................................................................6-1
6.1.2 CM-30 IP Interface Module......................................................................6-3
6.2 Notice of FCC Compliance.................................................................. 6-5
Appendix A – T1/E1-to-NetXpress LX Multiplexer Conversion ....... A-1

A.1 Installation Preparation ..................................................................... A-1
A.1.1 Equipment Unpacking & Inspection ......................................................... A-1
A.1.2 Card Slot Selection ............................................................................... A-1
A.2 IP Multiplexer Conversion .................................................................. A-2
A.2.1 CM-30 & MA-230 Installation into the First Multiplexer .............................. A-2
A.2.2 First CM-30 IP Interface Module Configuration .......................................... A-4
A.2.3 CM-30 & MA-230 Installation into the Second Multiplexer .......................... A-4
A.2.4 Second CM-30 IP Interface Module Configuration ...................................... A-4
A.2.5 Configuration of Both CM-30 Modules to Work Together ............................ A-4
A.2.6 Removal of the Original Common Modules ............................................... A-6
GatesAir, Inc. iii

Intraplex Products
Version 1.01
Figures
Figure 1-1. NetXpress LX-300 Front Panel with Cover .................................................1-2
Figure 1-2. NetXpress LX-100 Front Panel with Cover .................................................1-2
Figure 1-3. CM-30 IP Interface Module......................................................................1-3
Figure 2-1. Carrier Multicast Backbone Example .........................................................2-5
Figure 2-2. NetXpress LX Web Interface Login ...........................................................2-8
Figure 2-3. TDM Loopback Scenarios ...................................................................... 2-11
Figure 2-4. Timing Synchronization ........................................................................ 2-14
Figure 2-5. Point-to-Point Timing Synchronization .................................................... 2-14
Figure 2-6. Stream Timing Synchronization ............................................................. 2-15
Figure 2-7. Streams with Different Synchronization Sources ...................................... 2-15
Figure 2-8. Timing Synchronization with GPS ........................................................... 2-16
Figure 2-9. Timing with Off-Air Monitor Streams ...................................................... 2-17
Figure 3-1. NetXpress LX 1RU and 3RU Multiplexers ...................................................3-2
Figure 3-2. CM-30 Module and Indicator Lights ..........................................................3-3
Figure 3-3. Contact Input Circuitry ...........................................................................3-5
Figure 3-4. MA-230 Module Adapter Top and Faceplate Views ......................................3-6
Figure 3-5. MA-230 Connectors with Indicator Lights ..................................................3-7
Figure 3-6. CM-30 Module and MA-230 Midplane Insertion ..........................................3-8
Figure 3-7. 3RU NetXpress LX Rear Panel Connectors with MA-230 Module Adapter...... 3-10
Figure 3-8. 1RU NetXpress LX Rear Panel Connectors with MA-230 Module Adapter...... 3-10
Figure 3-9. Connection for DC Operation of 3RU Systems .......................................... 3-12
Figure 3-10. Connection for DC Operation of 3RU Systems with Two Power Sources ....... 3-12
Figure 3-11. Connection for AC Operation of 3RU System with External Signal Battery ... 3-13
Figure 3-12. Connection for AC Operation of 1RU System with External Signal Battery ... 3-13
Figure 3-13. 3RU Multiplexer Rear Panel with ACS-OPT1 Dual AC Power Feed Option ..... 3-14
Figure 4-1. Intraplex NetXpress LX Home Page ..........................................................4-2
Figure 4-2. Networking | Forwarding Table ................................................................4-3
Figure 4-3. Forwarding Table | Create a New Route Dialog Box ....................................4-4
Figure 4-4. Security | IP Access List .........................................................................4-4
Figure 4-5. IP Access List | Create IP Access List Entry Dialog Box ...............................4-5
Figure 4-6. System Cfg | TDM Bus Information ..........................................................4-5
Figure 4-7. System Cfg | Software Images Configuration ............................................4-6
Figure 4-8. Streams ...............................................................................................4-7
Figure 4-9. Stream Creation – Stage 1 .....................................................................4-7
Figure 4-10. Stream Creation – Stage 2 .....................................................................4-8
Figure 4-11. Stream Creation – Stage 3 for Multi-Unicast .............................................4-8
Figure 4-12. Stream Creation – Stage 4 (TDM to IP) ....................................................4-9
Figure 4-13. Stream Creation Summary ................................................................... 4-10
Figure 4-14. System Cfg | System Timing ................................................................. 4-11
Figure 4-15. Networking | SNMP Configuration .......................................................... 4-12
Figure 4-16. System Cfg | Configuration Files Backup/Restore ..................................... 4-13
Figure 4-17. Intraplex NetXpress LX Home Page ........................................................ 4-14
Figure 4-18. Current Alarms Page ............................................................................ 4-16
Figure 4-19. Alarm Definitions Page ......................................................................... 4-17
Figure 4-20. Specific Alarm Definition Dialog Box ....................................................... 4-17
Figure 4-21. Alarm History Page .............................................................................. 4-18
Figure 4-22. System Logging Page ........................................................................... 4-19
Figure 4-23. General Setup Page ............................................................................. 4-21
Figure 4-24. Contacts Page ..................................................................................... 4-22
Figure 4-25. Configure Input Contact Dialog Box ....................................................... 4-23
iv GatesAir, Inc.
Intraplex Products
Table of Contents NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
Figure 4-26. Configure Output Contact Dialog Box ..................................................... 4-24

Figure 4-27. TDM Bus Information Page ................................................................... 4-24
Figure 4-28. Changes to System Mode Dialog Box ..................................................... 4-25
Figure 4-29. TDM Bus Configuration Page ................................................................. 4-25
Figure 4-30. TDM Bus Map Configuration Page – T1 Mode ........................................... 4-27
Figure 4-31. Edit TDM Bus Map Configuration Page .................................................... 4-28
Figure 4-32. System Timing Page ............................................................................ 4-29
Figure 4-33. Software Images Page ......................................................................... 4-31
Figure 4-34. Configuration Files Backup/Restore Page ................................................ 4-33
Figure 4-35. Ethernet Interfaces Page – WAN and LAN Interfaces ................................ 4-35
Figure 4-36. Forwarding Table ................................................................................. 4-37
Figure 4-37. Add a Route Dialog Box ........................................................................ 4-38
Figure 4-38. DiffServ Marking for Forwarded Packets Page .......................................... 4-39
Figure 4-39. Add a DiffServ Marking Entry Dialog Box ................................................ 4-40
Figure 4-40. DiffServ TOS to Priority Mapping Page .................................................... 4-41
Figure 4-41. Map TOS Value to Priority Level Dialog Box ............................................. 4-41
Figure 4-42. TOS Byte Configurations Page ............................................................... 4-42
Figure 4-43. SNMP Configuration Page ..................................................................... 4-43
Figure 4-44. UDP Listeners Table ............................................................................. 4-44
Figure 4-45. TCP Connections Table ......................................................................... 4-45
Figure 4-46. ARP Table ........................................................................................... 4-46
Figure 4-47. Streams Table ..................................................................................... 4-47
Figure 4-48. Stream Creation – Stage 1 Page – Stream Type ...................................... 4-48
Figure 4-49. Stream Creation – Stage 2 Page – Stream Features ................................. 4-49
Figure 4-50. Stream Creation – Stage 3 Page – IP Parameters .................................... 4-50
Figure 4-51. Stream Creation – Stage 3 Page – IP Config for All Streams (Multi-Unicast) 4-51
Figure 4-52. Stream Creation – Stage 4 Page – TDM Bus Parameters ........................... 4-52
Figure 4-53. Stream Creation Summary Page ............................................................ 4-54
Figure 4-54. Stream Edit Pages ............................................................................... 4-55
Figure 4-55. Stream Statistics Page ......................................................................... 4-57
Figure 4-56. Performance History Page ..................................................................... 4-57
Figure 4-57. Voice Signaling Statistics Page .............................................................. 4-58
Figure 4-58. Ethernet Interface Statistics Page – WAN and LAN ................................... 4-59
Figure 4-59. SNMP Performance Page ....................................................................... 4-60
Figure 4-60. TCP/UDP Performance Page .................................................................. 4-62
Figure 4-61. ICMP Performance Page........................................................................ 4-64
Figure 4-62. IGMP Performance Page ....................................................................... 4-66
Figure 4-63. IP Performance Page ............................................................................ 4-67
Figure 4-64. Web Interface User Accounts Page ......................................................... 4-69
Figure 4-65. Add User Account Dialog Box ................................................................ 4-70
Figure 4-66. Edit User Account Dialog Box ................................................................ 4-70
Figure 4-67. IP Access List Page .............................................................................. 4-71
Figure 4-68. Add an IP Address Dialog Box ............................................................... 4-71
Figure 4-69. Ping Utility Page .................................................................................. 4-72
Figure 4-70. CM-30 Common Module: General Page ................................................... 4-73
Figure 4-71. CM-30 Common Module: Revisions Page ................................................ 4-74
Figure 4-72. CM-30 Common Module: Program Boot ROM Page ................................... 4-75
Figure 4-73. DS-64NC Configuration Page ................................................................. 4-76
Figure 4-74. DS-64NC Status Page .......................................................................... 4-76
Figure 4-75. PT-353 Configuration Page.................................................................... 4-76
Figure 4-76. PT-353 Status Page ............................................................................. 4-78
Figure 4-77. VF-25E Configuration Page ................................................................... 4-80
Figure 4-78. VF-25E Status Page ............................................................................. 4-81
GatesAir, Inc. v
Intraplex Products
Version 1.01
Figure 4-79. DS-64NC Configuration Page ................................................................. 4-83

Figure 4-80. DS-64NC Status Page .......................................................................... 4-85
Figure 5-1. NetXpress LX 3RU Multiplexer – Front View, Closed ...................................5-1
Figure 5-2. NetXpress LX Web Interface Home Page ...................................................5-2
Figure 5-3. Faults | Current Alarms Table ..................................................................5-3
Figure 5-4. Faults | Alarm History Log ......................................................................5-3
Figure 5-5. Ping Utility ............................................................................................5-4
Figure 5-6. Performance | Streams Statistics Table ....................................................5-5
Figure A-1. CM-30 Module and MA-230 Midplane Insertion ......................................... A-2
Tables
Table 2-1. NetXpress LX Stream User and Computed Parameters ..................................2-7
Table 2-2. NetXpress LX-supported TDM Channel Modules .......................................... 2-10
Table 2-3. NetXpress LX FEC Performance Data......................................................... 2-18
Table 3-1. CM-30 Indicator Light Descriptions .............................................................3-4
Table 3-2. CM-30 Switch Settings ..............................................................................3-4
Table 3-3. MA-230 Module Adapter SW1 Switches and Functions ...................................3-6
Table 3-4. MA-230 In/Out and Contact Port Pin Assignments ........................................3-7
Table 3-5. Power and Alarm Connectors ................................................................... 3-11
Table 4-1. TDM Bus Map Profiles ............................................................................. 4-26
Table 4-2. States Associated with Streams ............................................................... 4-48
vi GatesAir, Inc.
Intraplex Products
No header here
Section 1 – Introduction
This manual covers both the NetXpress LX IP multiplexer and the CM-30 IP interface module. The
NetXpress LX multiplexer provides convenient provisioning and management tools to enhance
operational efficiency. This IP platform supports both unicast and multicast and is compatible with the
Intraplex NetXpress multiplexer.
The NetXpress LX multiplexer combines the technology of the original NetXpress multiplexer in a
module configuration compatible with Intraplex T1 or E1 systems. The NetXpress LX multiplexer is
available in either a 3RU frame with capacity for up to 17 application modules or a 1RU frame that can
hold five application modules. This multiplexer can work in a simple point-to-point and point-to-
multipoint designs and also as an “edge” device with the NetXpress multiplexer in large, multisite
networks.
While the CM-30 IP interface module operates as the command module in a NetXpress LX multiplexer,
this module can also replace the network interface module in an existing T1 or E1 system, converting
it to IP while utilizing the existing chassis with all its audio, voice, and data modules. With the CM-30
module, you can easily transition an existing Intraplex T1 or E1 system to cost-effective IP
transmission.
1.1 Key Features

The NetXpress LX system’s features include
● CM-30 IP interface module, which can convert existing T1 or E1 systems to IP
● Compatibility with Intraplex NetXpress systems
● Wide variety of audio, voice, and data interface modules
● Optional echo cancellation for 2-wire voice circuits
● Transport of two contact closures in each direction
● Adjustable packet size
● Programmable jitter buffer depth
● Advanced Intraplex forward error correction
● Quality of Service (QoS) priority tagging
● Unidirectional or bidirectional unicast streaming
● Unidirectional multicast streaming
● Web browser user interface
● SNMP control
● Current and previous software revision storage
● Network statistics monitoring
● Event logging
1.2 Manual Use

Use this manual as the primary reference document for installing, configuring, operating, and
troubleshooting the NetXpress LX multiplexer and the CM-30 IP interface module. If you have
additional questions pertaining to the operation of your Intraplex system, you can contact GatesAir
Customer Service:
● U.S., Canada, and Latin America: +1-217-222-8200 or tsupport@gatesair.com
● Europe, Middle East, and Africa: +44-118-964-8100 or Service.europe@gatesair.com
● Asia and Pacific Rim: +852-2776-0628 or BCDService@gatesair.com
GatesAir, Inc. 1-1

Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual 1 – Introduction
Version 1.01
1.3 Manual Scope

The “Table of Contents” helps you locate specific topics. These guidelines give general information on
manual sections.
● Readers unfamiliar with the NetXpress LX system and/or the CM-30 IP interface module
– Use this manual as a tutorial. Read or skim all sections in order.
● Installers – If you are already familiar with the NetXpress LX system and/or the CM-30 IP
interface module, finish reading this section and go directly to Section 3 – “Installation & Wiring”
for step-by-step installation instructions.
● Transmission and Planning Engineers – The NetXpress LX and CM-30 operation and
configuration overview is in Section 2 – “Functional Design,” and specific instructions are in
Section 4 – “Configuration & Operation.” You can find output, power, and other specification
information in Section 6 – “Specifications.”
● Maintenance Technicians – Section 5 – “Testing & Troubleshooting” discusses system tests and
troubleshooting solutions. Individual channel module setup and test procedures can be found in
the manuals for the modules shipped with your system.
1.4 Components
1.4.1 Main Equipment Shelf

The NetXpress LX chassis has two rack-mount equipment sizes:
● NetXpress LX-300 – 19-inch wide, 5 ¼-inch high 3RU (Figure 1-1)
● NetXpress LX-100 – 19-inch wide, 1 ¾-inch high 1RU (Figure 1-2)
Figure 1-1. NetXpress LX-300 Front Panel with Cover
Figure 1-2. NetXpress LX-100 Front Panel with Cover

Each shelf is equipped with a CM-30 module, a MA-230 module adapter, and slots for plug-in channel
modules and module adapters.
The NetXpress LX-100 multiplexer has a single built-in AC power supply. The LX-300 multiplexer has a
single plug -in AC or DC power supply and optional secondary plug-in AC or DC supplies.
1-2 GatesAir, Inc.

Intraplex Products
1 – Introduction NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
1.4.2 CM-30 IP Interface Module

The CM-30 module (Figure 1-3) is the command center for the NetXpress LX IP multiplexing system.
GatesAir, Inc. 1-3

Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual 1 – Introduction
Version 1.01
Figure 1-3. CM-30 IP Interface Module
1-4 GatesAir, Inc.

Intraplex Products
1 – Introduction NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
This module acts as an IP network interface, a packet engine, and a system manager. When coupled
with the MA-230 module adapter (Section 1.4.3), the CM-30 module provides shelf management
control, WAN and LAN traffic control through 10/100Base-T ports, and timing control for external
stream traffic and system synchronization.
You can use a CM-30 module in place of, but not at the same time as, a T1 or E1 common module
(CM-3, CM-5, CM-5RB, CM-6, CM-7, or CM-7RB) in an existing Intraplex T1 or E1 multiplexer. You can
then revert back to T1 or E1 at a later date by simply removing the CM-30 module and reinserting the
original common module.
1.4.3 MA-230 Module Adapter

The MA-230 module adapter provides connectivity for the CM-30 module. The MA-230 module adapter
connects to the CM-30 module in the rear of the shelf and features these communication ports:
● Two 10/100Base-T ports (WAN and LAN)
● Timing in/out for external stream and system synchronization
● Contact I/O for external control
1.4.4 Other Modules and Module Adapters

The NetXpress LX system offers five channel card slots (1RU shelf) or 17 channel card slots (3RU
shelf) for Intraplex audio, voice, and data modules.
Intraplex module adapters are installed in the rear of the shelf and work in conjunction with the
channel access cards installed in the front.
1.4.5 Indicator Lights

Four system status indicator lights located on the NetXpress LX power supply are visible when the
front shelf cover is on (Figures 1-1 and 1-2).
● POWER – This green light is on when the multiplexer is powered.
● NORMAL – This green light is on when no major nor minor alarm is present.
● ALERT – This yellow light is on when a minor alarm condition exists.
● ALARM – This red light is on when a major alarm condition exists.
Section 5 defines major and minor alarm conditions.
The CM-30 module has indicator lights as well, which are visible when the front shelf cover is off.
Section 3.2.2 gives more information about CM-30 indicator lights.
1.5 Web Browser User Interface

You can control functionality of your NetXpress LX unit and access network statistics and system
status through the NetXpress LX Home page. You can choose to run simultaneous software windows;
each connected to a different NetXpress LX system in the network. The Web browser interface, in
conjunction with an SNMP network manager, lets you control and monitor your system from one
operation center. You can access the Home page from the network management system to research a
particular problem or obtain a graphical view of system configuration or status. Section 4 –
“Configuration & Operation” gives more information on this interface software.
GatesAir, Inc. 1-5

Intraplex Products
No header here
Section 2 – Functional Design

This section describes the intent of IP multiplexing and day-to-day operations of the NetXpress LX
system and the CM-30 IP interface module. The section also describes how to use the IP multiplexer
and interface module to configure real-time payload transport of audio and data over existing IP
networks.
Packet-based media transport with the NetXpress LX system or the CM-30 module provides these
features:
● Transport of audio, voice, data, and video
● Flexibility when integrating to business applications, systems, and networks
● Network monitoring
● Error mitigation
● Transition and migration from legacy systems with reuse of modules and components
2.1 Network Concepts and Considerations

When looking at the NetXpress LX system (or the CM-30 module) and packet-switched services as a
whole, consider these network-related concepts:
● MTU throughout the network
● DHCP use
● Routing table construction
● WAN port auto-negotiation
● ICMP support
● Redundant WAN link configuration
● IGMP multicast
2.1.1 MTU throughout the Network

Prior to configuring a stream, you need to know end-to-end MTU (Maximum Transmission Unit)
between stream endpoints, which you can measure using an external server or router and running the
“Path MTU” tool. The stream payload must be smaller than the path MTU, otherwise fragmentation
occurs, the stream does not come up, and the NetXpress LX system does not support re-assembly.
2.1.2 DHCP Use

Dynamic Host Configuration Protocol (DHCP) is a network protocol that enables a DHCP server to
automatically assign an IP address to an individual computer’s IP network interface. DHCP dynamically
assigns a number from a defined range of numbers configured for a given network.
The NetXpress LX system supports dynamic address assignment for its LAN interface using DHCP. On
the WAN interface, only static IP address assignment is supported. You can elect to enable the DHCP
option for the management interface from the Networking Ethernet Interfaces Web page (Section
4.3.4 – Configure the Network). If DHCP is enabled and the system fails to successfully retrieve an IP
address, it defaults to the factory default address – 192.168.1.1.
2.1.3 Routing Table Construction

The behavior of the NetXpress LX system within the customer’s network is that of an IP host. As such,
the NetXpress LX routing table is used solely to route internally generated packets. For streams that
are unicast, the determination of the next-hop gateway to reach the remote NetXpress LX shelf is
done by examining the system routing table.
GatesAir, Inc. 2-1

Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual 2 – Functional Design
Version 1.01
Routes in the routing table fall into two basic categories: automatic routes and user-defined routes.
The NetXpress LX system adds automatic routes based on the interface IP addresses. These routes
are called “directly connected” routes and are present to identify local subnets. If the destination for
all NetXpress LX traffic (stream and management) is to a host on its local subnet, no user routes are
needed. In most cases, however, you need to add routes to remote networks or hosts so that the
NetXpress LX system can successfully send traffic to it. In the simplest case, if there is only one
gateway on its WAN subnet, a default route (such as 0.0.0.0/0.0.0.0 next-hop “gatewayIP”) pointing
to that gateway should be added. You can manage the NetXpress LX routing table from the NetXpress
LX Home page (Section 4.3.4.2 – Forwarding Table) or via direct SNMP access of the proprietary route
management MIB (Management Information Base).
2.1.4 WAN Port Auto-negotiation

The auto-negotiation mechanism accommodates multi-speed Ethernet network devices. Auto-
negotiation occurs when a physical connection is made between a NetXpress LX Ethernet port and an
Ethernet port on a network switch or router. During this process, the two Ethernet devices use a
protocol to determine at what speed (10 Mbps or 100 Mbps) they communicate and whether the
exchange of data occurs in a half-duplex (only one end transmits at a time) or full-duplex manner.
With the NetXpress LX system, you can enable or disable auto-negotiation for the WAN ports because
it is crucial that the link characteristics are set correctly to facilitate the transmission of stream data.
Auto-negotiation should be enabled when the network port to which the NetXpress LX system is being
connected is capable of negotiating to a mode of 100 Mbps or 10 Mbps and full-duplex operation.
When auto-negotiation is disabled, each Ethernet port is set to operate at 100 Mbps speed in full-
duplex mode, the optimum setting. If the anticipated stream data rate is low enough, the WAN port
can operate effectively at 10 Mbps. Operating the WAN port in half-duplex mode should be avoided.
Both sides of the link need to be set for auto-negotiation. If not, the NetXpress LX system configures
itself for 10 Mbps, half duplex, and streams experience dropped packets due to collision on the
Ethernet link.
The LAN port is always set to auto-negotiate. The management port can satisfy its function even when
operating at 10 Mbps in half-duplex mode.
Note: Do not operate auto-negotiation on only one side of the NetXpress LX link. To work properly,
both sides (NetXpress LX system and connecting device) must be enabled for auto-
negotiation. The NetXpress LX system does not revert to 100 Mbps full-duplex if it is
configured to auto-negotiate and the other device is manually configured for 100 Mbps full-
duplex.
2.1.5 ICMP Support

The ICMP (Internet Control Message Protocol) delivers error and control messages from hosts to
message requestors. An ICMP test may determine whether a destination is reachable. The ICMP
messages typically report errors in the processing of datagrams. Additionally, ICMP provides flow
control and first-hop gateway redirection. On the NetXpress LX WAN port, there is an option to block
ICMP error messages, but the “ping” messages are always allowed.
2.1.6 IGMP Multicast

The NetXpress LX system (or the CM-30 module in an original Intraplex system) interoperates with
multicast routers using the Internet Group Management Protocol (IGMP). The IGMP Multicast mode
involves transmission to specific hosts through IGMP routers. This scheme allows you to route specific
packets onto specific segments, thereby segregating unwanted traffic from narrow segments.
The NetXpress LX system supports IGMP v2 messages. When a “receive” multicast stream is
configured, it sends out IGMP membership reports. Similarly, when the multicast streams are deleted,
the NetXpress LX system sends out an IGMP Leave message and also responds to the membership
2-2 GatesAir, Inc.

Intraplex Products
2 –Functional Design NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
queries from the router. It supports the proprietary IGMP statistics MIB to account for all incoming and
outgoing messages.
2.2 Streams
Within the NetXpress LX multiplexer or an original Intraplex multiplexer, the CM-30 IP interface
module uses packet streaming to transport audio signals.
2.2.1 Stream Types
2.2.1.1 Unidirectional versus Bidirectional

Packet streams can be unidirectional or bidirectional. In other words, streams can travel in one
direction (transmitted or received) or two directions (transmitted and received). The CM-30 module
supports both unidirectional and bidirectional packet streaming.
Most circuit types (such as voice and two-way data circuits) are bidirectional, or full-duplex. Full-
duplex circuits require identical full-duplex (transmit or receive) channel modules at both ends of the
channel they occupy within a system. Other circuit types (such as program audio channels) are
unidirectional (simplex). They always have a transmitter module at one end and a receiver module at
the other. Most bidirectional (full-duplex) channel modules can also be set up to operate in a
unidirectional (simplex) mode.
2.2.1.2 Unicast versus Multicast

Packet streams can also be classified as unicast or multicast. Unicast describes transmitting a piece of
information (a packet stream in this case) from one point to another point. Unicast transfer mode is
still the predominant form of transmission on LANs and within the Internet. Standard unicast
applications include HTTP, SMTP, FTP, and Telnet.
Multicast describes communication where a piece of information is sent from one or more points to a
set of other points (a multicast group address). There may be one or more senders and the
information is sent to a set of receivers (there may be no receiver or any number of receivers). With
multicasting, the same packet is delivered simultaneously to a group of clients. Multicast applications
must use the UDP (User Datagram Protocol) transport protocol, since TCP (Transmission Control
Protocol) only supports the unicast mode.
Most circuits provided by Intraplex multiplexer systems are unicast, including those provided with the
NetXpress LX system. However, several types of channel modules can be configured for point-to-
multipoint operation (multicast). For example, you can set up a single program audio transmitter
module and several program audio receiver modules in a point-to-multipoint or “broadcast” circuit
configuration, allowing multiple locations to receive the same program audio signal.
If your network does not support multicasting, you can configure the NetXpress LX system to multi-
unicast up to four destinations. The programming source must be in contiguous time slots on TDM Bus
A. The receivers can be on the internal TDM bus. Section 4.3.3.4 – TDM Bus Mapping Configuration
gives additional multi-unicast information.
2.2.1.3 Voice Streams versus Data Streams

Streams which are intended to carry information for voice grade audio modules often require
additional signaling information to support pulse dialing, off-hook condition call progress or ringing
states. Special signaling support is required to transport this added information. Voice audio streams
carrying telephone calls are also prone to audio echo back from the receiver. You can use echo
canceling circuits to eliminate this problem. Streams used for transporting linear or compressed
wideband audio modules or other forms of raw information present their data directly into each
channel and do not require signaling support.
GatesAir, Inc. 2-3

Intraplex Products
Version 1.01
2.2.2 Stream Addressing

The stream addressing process involves designating a destination IP address for both unicast and
multicast IP streams (Section 4.3.5– Configure Streams). During the process of adding streams,
individual streams are designated as either unicast or multicast in the Transmission Type field (Section
4.3.5.1 – Stream Creation).
When you create a stream, a UDP port number must be specified for both the local and remote
NetXpress LX devices. The RTP protocol conversation between the two devices takes place through the
specified UDP ports.
The range for UDP port numbers must be greater than or equal to 50000 and a multiple of 5, ending
in either a 0 or a 5. For unicast and multicast receive streams, the combination of peer’s IP address
and source and destination UDP ports must be unique. For multicast transmit streams, each stream
must have unique ports.
Many networks use a device known as a “firewall” at the entry point to the network to provide security
against hackers and other undesirable applications. Usually, network devices in the private network
behind the firewall can freely transmit out using any UDP port number. However, devices are blocked
from receiving packets using a UDP port number until a packet is transmitted out the firewall using the
same UDP port. When setting up the network for a NetXpress LX installation, you may need to
configure the firewall to allow communication on the UDP port numbers used for stream traffic before
attempting to bring up a stream.
2.2.3 Multicast Group Addressing

The CM-30 IP interface module, within the NetXpress LX system or an original Intraplex system,
supports multicast use for stream transmission and supports creating up to 32 transmit, receive, or a
combination of transmit and receive streams. This system does not make any restrictions on the type
of multicast address used for a stream destination. Therefore, you determine how you want the
multicast address space to be administered. Figure 2-1 represents a scenario where multicast
addresses are “administratively scoped.” However, some customers may also require GLOP
assignment by the carrier WAN, using address ranges 233.x.x.x, and the NetXpress LX system can
accommodate that addressing scheme as well. Section 4.3.5.1 – Stream Creation gives additional
information regarding multicast addresses.
2-4 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 2-1. Carrier Multicast Backbone Example
2.2.4 Telephony
The CM-30 module and NetXpress LX system allow you to create streams whose endpoints are
Intraplex voice channel modules that support telephone signaling (for example, the VF-15E, VF-16AE,
and VF-25 modules). The voice circuits generate signaling bits which the NetXpress LX system
transports out-of-band and reinserts onto the NetXpress LX internal TDM bus at the receive end. No
more than 20 telephony streams are allowed in-service at one time.
Telephony streams can be easily identified in the stream table by the telephone icon after the stream
name. The color of the icon, (red, yellow, or green) indicates the current status of the out-of-band
signaling transfer. The NetXpress LX Performance menu provides statistics on signaling packet
transmission, and these statistics are cleared when the other stream statistics are cleared.
The TDM bus in T1 systems inherently supports signaling. In E1 systems, the signaling bits are carried
on the internal TDM bus using Channel Associated Signaling (CAS). Telephony streams need to
originate and terminate on busses where the CAS mode is enabled. You can select the specific TDM
busses for the telephony streams on the TDM Bus Edit screen (System Config | TDM Bus | TDM
Bus Edit). When the CAS mode is enabled, the NetXpress LX system uses Time slot 16 to carry the
signaling bits for all the other channels on that bus; this time slot is not available to carry normal
traffic.
2.2.5 Echo Cancellation

The NetXpress LX system can provide echo cancellation for voice circuits using up to 2 optional echo
canceller cards that plug onto the CM-30 module. Each board can provide echo cancellation for up to
30 channels per echo canceller card on the TDM bus.
Echo cancellation can only be enabled for full-duplex streams with identical bus/channel configuration
in the transmit (Tx) and receive (Rx) direction, and both endpoints of the stream need to have an
echo canceller card installed. Echo cancellers are needed in 2-wire modules (for example, the VF-15E
GatesAir, Inc. 2-5

Intraplex Products
Version 1.01
or 16AE module) but not in 4-wire modules (for example, the VF-25E module). When using echo
cancellation, you should not configure streams to encapsulate more than 60 frames per packet.
2.2.6 Packetization and Overhead

Packetization is a process in which frames of data from the TDM bus are collected into IP packets for
transmission through the IP network. A frame on a NetXpress LX TDM bus is divided into 32 partitions
or time slots, each containing a byte of data. Because of the serial nature of the TDM bus, an entire
TDM bus frame encompasses 125 µs in time. The stream packetization interval defines the number of
TDM frames collected by the NetXpress LX system into a single packet for transmission. The higher
the packetization interval, the greater the accumulation delay introduced to the program because each
frame must be accumulated before the packet can be created. Note that the total program delay is a
combination of packetization delay and network delay.
Each packet in a NetXpress LX stream contains 44 bytes of non-program data (overhead)
corresponding to the header information required for the IP, UDP, and RTP protocol layers. The ratio of
non-program data to program data for a packet can be considered the overhead required to get the
packet through the network. The higher the overhead, the more the network bandwidth available to
an application used to transmit non-program data. Program delay can be minimized by using a small
packetization interval at the expense of an increase in overhead. Conversely, increasing the
packetization interval decreases the overhead but increases the program delay (Table 2-1).
Another overhead determination factor is the number of time slots from each TDM frame that get
placed in the packet. As this number increases, the stream overhead decreases because the ratio of
overhead data to program data decreases. However, the number of time slots consumed from each
frame does not affect the program delay. Therefore, it is desirable to combine time slots from a TDM
bus headed for the same destination into a single stream to reduce overhead and to make the best
use of available network bandwidth.
2.2.7 Packet Jitter Compensation

In an IP network, the time required for a packet to travel through the network from sender to receiver
is not guaranteed to be maintained. As a result, the receiver can see the interval between the arrival
of packets vary throughout the reception of the packet stream. For a given packet, the difference
between the packet’s delay and the average of the delay values for all packets in the stream is known
as jitter. The jitter can be positive or negative depending on whether the packet delay is less than or
greater than the average delay.
For many network services, packet jitter is not an issue, and no technique is needed to compensate.
However, the continuous playout nature of audio and video require that there must be some means of
guaranteeing that the receiver always has the next packet of data when the previous packet is
consumed. The receiver must also hold onto packets that arrive early so that they are available for
playout at the proper time.
The NetXpress LX system compensates for stream packet jitter through the use of a jitter buffer. The
system maintains a jitter buffer for each stream on the receive side. The buffer is sized so that the
buffering delay is greater than the maximum packet delay expected through the network. In the
NetXpress LX system, you specify the jitter buffer size in number of packets ranging from 8 to 128
(Section 4.3.5.1 – Stream Creation). The packetization interval of the stream controls the amount of
packet delay for which the jitter buffer can compensate. Increasing the number of TDM frames
contained in a packet increases the size of the jitter buffer as measured in time.
2.2.8 Packet/Stream Information Calculation

Table 2-1 gives an example of user and computed parameters for a NetXpress LX stream. The user
parameters represent user-defined stream parameters. The computed parameters are for packet
information and network bandwidth based upon the user parameters. This table also gives formulas
for how to derive computed parameters for a stream.
2-6 GatesAir, Inc.

Intraplex Products
Version 1.01
Table 2-1. NetXpress LX Stream User and Computed Parameters

User Parameter Value Description
Number of TDM 1 Number of TDM channels to transport in a stream

Channels
TDM Frames per 160 Number of TDM frames per payload (packet)
Payload
Jitter Buffer Size 64 Configured jitter buffer size in packets

(8 – 128 packets)
Computed Parameter Value Description Formula
TDM Channel Data Rate 64 kB/S Calculated TDM channel data rate in kB/S Number of TDM Channels x 64
Packet Payload Size 160 bytes Calculated payload size in each packet in Number of TDM Channels x
bytes TDM Frames per Payload
Packet Interval 20 mS Calculated packet interval (time between Number of TDM Frames per
packets) in mS Payload ÷ 8
Packet Rate 50 Calculated packet rate for a stream in (1 ÷ Packet Interval) x 1000
packets/S packets/S
Jitter Buffer Delay 640 mS Calculated jitter buffer delay in mS Jitter Buffer Size x Packet
Note: This delay assumes a receive Interval ÷ 2
queue of half the jitter buffer size
Ethernet Frame Size 242 bytes Calculated Ethernet frame size in bytes = Packet Payload Size + 38 + 44
Packet Payload Size + Ethernet overhead
(38 bytes – no VLAN) + IP overhead (20
bytes IP + 8 bytes UDP + 16 bytes RTP)
Ethernet Stream Data 96.8 kB/S Calculated Ethernet stream data rate in Ethernet Frame Size x Packet
Rate kB/S * Rate x 8 ÷ 1000
IP Packet Size 204 bytes Calculated IP packet size in bytes = Packet Payload Size + 44
Packet Payload Size + IP overhead (20
bytes IP + 8 bytes UDP + 16 bytes RTP)
Stream Data Rate 81.6 kB/S Calculated IP stream data rate in kB/S * IP Packet Size x Packet Rate x
8 ÷ 1000
* In most instances, Ethernet overhead is stripped before the packet is transported over a WAN link.
However, in certain instances (such as Metro Ethernet networks that transport the entire frame);
the Ethernet overhead is left on the packet.
2.2.9 Stream Statistics

NetXpress LX stream statistics are receiver-based. The time interval for collecting stream statistics is
user-selectable (from 5-10 seconds for each stream). It is a good practice to review your stream
statistics on a regularly scheduled basis (Section 4.3.6.1 – Stream Statistics). You may be able to
modify your NetXpress LX system for optimum throughput, bandwidth efficiency, and reduced errors.
As an example, you may wish to alter the size of the jitter buffer if you are experiencing too many
lost, underrun, early, or late packets. Specifically, if you are experiencing too many late packets, you
might need to increase the jitter buffer size.
2.3 System Security

System security is controlled through
● Logon and password control.
● Interface protocol management enabling and disabling.
● An IP access list.
GatesAir, Inc. 2-7

Intraplex Products
Version 1.01
● Establishment and and control of SNMP Communities.
2.3.1 NetXpress LX Login

When you launch the Web server interface application, the system immediately displays the logon
screen (Figure 2-2). You must type the proper user name and password to gain access to the
NetXpress LX Web interface. Before it is configured, the NetXpress LX system has a default
administrator user name of “admin” and default password of “admin” for the Web interface. Once you
initially log on, you can change the Web interface administrator password, as well as administrator
and guest accounts for Web FTP access (Section 4.3.7.1 – Accounts).
Figure 2-2. NetXpress LX Web Interface Login
2.3.2 Management Protocols on an Interface

The NetXpress LX system comes with two Ethernet interfaces:
● WAN
● LAN
The LAN interface allows you to run all management traffic on a separate network if desired.
By default, each interface accepts HTTP and SNMP protocols and allows FTP and Telnet sessions to be
established. You can use the interface screens in Section 4.3.4 – Configure the Network to enable or
disable different protocols for each interface. Controlling protocols by interface enables you to
● Tighten security
● Block unwanted traffic
● Ensure network privacy
2.3.3 IP Access List Use

You can add security to your NetXpress LX installation by limiting access based on specific IP
addresses (Section 4.3.7.2 – IP Access List). You can also use the same networking configuration
screen to specify which interface can be used to gain access to the system.
2.3.4 SNMP Communities

An SNMP community is a group of hosts that you can manage as a distinct group with SNMP. You
must use a community name for all SNMP conversations to take place. You can use the same name for
2-8 GatesAir, Inc.

Intraplex Products
Version 1.01
a read-only community and a read-write community, or you can specify two different names to restrict
write-access to the system.
2.4 NetXpress LX QoS

Quality of Service (QoS) / Class of Service (COS) mechanisms can reduce flow complexity by mapping
multiple flows into a few service levels. Network resources are then allocated based on these service
levels and flows can be aggregated and forwarded according to the service class of the packet.
2.4.1 COS Levels for Stream Data

The class of service (COS) level for a stream is established when the stream is created. The NetXpress
LX system offers four COS levels (high, normal, medium, low) for stream data (Section 4.3.5.1 –
Stream Creation). The classes are based on service priority; the higher the priority, the more
immediate the handling of the stream. For example, program audio is critical in many operations, so
when a stream is configured for program audio, you designate a high class of service level for that
packet stream. Conversely, a voice circuit might be considered less critical to operations, so you might
specify a lower COS level.
2.4.2 TOS Byte Marking for Outbound Stream Packets

In an IP network, all IP packets contain a field in the IP header called the Type of Service (TOS) byte.
The value of the TOS byte tells the network what quality of service needs to be applied to the packet.
You can define what the value of the TOS byte field should be for each of the four classes of service
supported by the NetXpress LX system for stream packets. The system places the appropriate TOS
byte value corresponding to the COS provisioned for a stream in every outbound data packet for that
stream (Section 4.3.4.3 – Class of Service). Since TOS byte value can be set to any value per class of
service, the NetXpress LX system can operate in networks using Differential Services (DiffServ) QoS
and networks employing the standard TOS interpretation for QoS.
2.4.3 User-Defined TOS Byte Setting for Outbound SNMP and HTTP
Packets
In addition to supporting the TOS marking for stream data, the NetXpress LX system allows you to
configure the TOS byte value placed in all outbound SNMP and HTTP packets. Therefore, SNMP
management traffic and Web interface traffic to be handled in the network with a different class of
service than other packets.
2.5 NetXpress LX Internal TDM Busses

The NetXpress LX IP multiplexer uses two TDM busses to support data transfer for audio channels.
These busses (TDM Bus 1A and TDM Bus 1B) can be configured to operate in T1 or E1 mode.
Note: Both A side and B side busses operate in the same mode; you cannot have a T1 bus and an E1
bus.
When set for T1 mode, the TDM busses support robbed-bit signaling. When set for E1 mode, the TDM
busses in the NetXpress LX system support CAS (channel associated signaling) and CCS (Common
Channel Signaling). With CAS signaling, time slot 16 is always reserved for telephone signaling. The
data rate is fixed at 1.544 MHz (T1 mode) or 2.048MHz (E1 mode). In E1 mode, you can enable or
disable signaling.
2.5.1 Compatibility with Intraplex TDM Channel Modules

Nearly all Intraplex TDM channel modules are compatible with the NetXpress LX multiplexer. Table 2-2
shows currently supported modules.
GatesAir, Inc. 2-9

Intraplex Products
Version 1.01
Table 2-2. NetXpress LX-supported TDM Channel Modules

Nominal Nominal Nominal
Power Power Power
Module (watts) Module (watts) Module (watts)
PT-150A 4.7 PT-D150 4.7 DA-191A 1.2
Modules–AES\EBU
Program Audio
Input / Output
PT-150B 4.0 PR-D150 6.6 DA-191B 1.2
High Fidelity
PT-150C 4.0 PT-D350 3.0 DA-91A 1.0
PR-150A 6.6 PR-D350 3.4 DA-91i 1.0
PR-150B 6.0 PT-D355 3.0 DS-64NC 2.5
PR-150C 6.0 PR-D355 3.4 D-100 3.0

High Fidelity Program Audio Modules – Analog Input/ Output
Data Modules
PT-153 5.5 VF-15E 2.3 DS-562i 2.0
Voice Modules for E1

PR-153 5.5 VF-16AE 2.3 DS-961D 1.2
PTR-155 5.0 VF-16E 2.3 DS-961DE 1.2
PT-250 3.0 VF-25E 2.0 DS-961DF 1.2
PR-250 3.4 VF-27E* 2.0 DS-961DG 1.2
PTR-255 7.7 VF-28E 2.0 DS-965 1.2
PT-350 3.0 VF-29E 2.0 DS-966A 2.5
PT-350B 3.0 VF-15 2.3 DS-967 2.5
PT-350C 3.0 VF-16 2.3 OCU-DP 2.0

Voice Modules for T1
PR-350 3.4 VF-16A 2.3
PR-350B 3.4 VF-25 2.0
PR-350C 3.4 VF-27* 2.0
PT-353 3.0 VF-28 2.0
PR-353 3.4 VF-29 2.0
PT-355 3.0 VF-40 2.0

Modules
PT-355B 3.0 DV-600 5.0

Secure
Digital
Voice
PT-355C 3.0 DV-600A 5.0
PR-355 3.4
PR-355B 3.4
PR-355C 3.4
* Neither the VF-27 nor VF-27E module supports or operates with E & M signaling when used in a
NetXpress LX system.
You must configure each channel module to use either TDM Bus 1A or TDM Bus 1B. Also, if the TDM
busses are set for E1 operation, you must provision the bus itself to use CAS signaling and then
provision each module on the bus to inform it that CAS signaling is in use. Each TDM bus has its own
frame loss signal to tell the modules to mute if there is a problem with the arriving data intended for
that particular bus.
2-10 GatesAir, Inc.

Intraplex Products
Version 1.01
2.5.2 TDM Channel Loopbacks

Figure 2-3 shows the normal/default of no loopback and the three Time Division Multiplexing (TDM)
channel loopback scenarios for channel modules and TDM busses: internal, external, and both.
Figure 2-3. TDM Loopback Scenarios

When you apply the internal loopback to a time slot or a group of time slots on the TDM bus, the
channel module data is copied back to the receive channel on that same TDM bus, as well as being
transmitted to its IP targets. When you apply the external loopback to a time slot or a group of time
slots on the TDM bus, the received data is delivered to the channel module on that same TDM bus as
well as being transmitted back out to its originating source. You can apply both internal and external
loopbacks simultaneously. This example shows loopbacks for an entire bus. However, you can also
loopback individual time slots within a bus.
2.5.3 TDM Bus Mapping

The NetXpress LX or CM-30 TDM bus is connected by default to a virtual IP bus; this connection is bi-
directional. The TDM bus mapping feature allows you to reconfigure your connections to suit your
needs. You can connect a time slot from TDM A, TDM B, or either of the echo cancellers to the
corresponding time slot on any of the 4 IP ports. You can connect a time slot from TDM A or TDM B to
the corresponding time slot on either of the echo cancellers.
The NetXpress LX system (or CM-30 module) has 2 bus map choices:
● The pre-configured default map has both TDM A and TDM B busses mapped from IP sources to
two (multi-unicast) IP destinations (connections).
● You can select the User Defined Profile and create a customized bus map configuration. For
example, you can create a multi-unicast configuration, where one source is connected to more
than two destinations. Section 4.3.3.4 – TDM Bus Mapping Configuration gives additional multi-
unicast information.
GatesAir, Inc. 2-11

Intraplex Products
Version 1.01
2.6 System Time-of-Day

With the NetXpress LX system, there are two ways to set the system time-of-day: 1) manually and 2)
via NTP (Network Timing Protocol) server. If you choose the latter method, you must use the Web
server interface to enable NTP in the NIM Configuration – General Setup screen and provide the IP
address of the SNTP server (Section 4.3.3.1 – General Setup). The NetXpress LX system maintains the
time and date in a battery-backed time-of-day clock on the CM-30 module.
2.7 System Timing
2.7.1 Types of System Timing

System timing is the process of synchronizing communications and stream traffic between two or
more NetXpress LX systems in a network. Time synchronization is critical to the proper functioning of
the NetXpress LX network. It must be configured correctly.
The primary timing source for all interconnected NetXpress LX systems should trace back to the same
long-term accurate oscillator.
Primary and secondary timing are configured via the Web interface using the System Timing screen
(Section 4.3.3.5 – System Timing). You must specify the timing source for both primary and
secondary timing. If the primary timing source is unavailable, the system uses secondary timing. The
NetXpress LX system provides four timing sources from which to choose:
● Internal
● External
● Stream
● SynchroCast
Timing can be sourced through the RS-422 Timing OUT port on the MIU-201 or MIU-202-2 to feed
additional multiplexers.
2.7.1.1 Internal Timing

Internal timing is derived from an extremely accurate internal oscillator on the CM-30 module. In a
NetXpress LX network, only the master NetXpress LX system can use internal timing. Other NetXpress
LX shelves in the network must use external, stream, or SynchroCast timing derived from the network
master.
2.7.1.2 External Timing

External timing is usually a precision timing signal derived from an external device that is traceable to
a stratum-1 timing source (for example, a public network WAN interface such as T1 or E1). External
timing is input through a connection to the Timing IN port on the MIU-201 or MIU-202-2. The external
timing input accepts an RS-422/RS-485 balanced clock signal. If external timing is selected as the
primary timing source on the master NetXpress LX system, external timing, stream, or SynchroCast
timing must be selected as the primary timing method for the subordinate NetXpress LX systems.
2.7.1.3 Stream Timing

Stream timing is derived from the incoming packet stream. A timing stream must have a packet rate
of 8 packets per second or greater (1000 frames/packet or less). This type of timing uses an algorithm
inherent in the TDMoIP chip. In a NetXpress LX network, only subordinate NetXpress LX systems can
be set to stream timing mode. The NetXpress LX master system monitors stream traffic and adjusts
timing so that the subordinate shelves are synchronized with the master clock frequency. As a general
rule; the faster the packet rate, the better the stream timing. With stream timing, jitter buffer size can
be monitored and regulated to avoid buffer underflow/overflow and negate the effect of packet delay
2-12 GatesAir, Inc.

Intraplex Products
Version 1.01
variation. When a subordinate system derives timing from the master, clock recovery algorithms are
employed to align clock frequency and control packet jitter/wander. Also, in order to recover timing
from a stream, the stream must be active and sending. Networking or router problems can result in
no timing recovery from a stream.
Note: When you configure several receive streams and use a stream as the timing source, you
should use the stream with the highest packet rate (such as the lowest frames per payload
value) as the primary timing stream.
2.7.1.4 SynchroCast3™ Timing

The SynchroCast3 system uses a simulcast technique which transmits to an extended geographic area
using multiple, overlapping transmitters operating on the same frequency. Historically, broadcasts
from nearby transmitters on the same frequency have created serious reception problems where they
overlap. The SynchroCast system, originally developed for use in land mobile radio systems, makes
simulcasting possible in FM broadcast as well. The SynchroCast system can provide dramatically
increased station coverage while reducing or eliminating unwanted artifacts at the listener’s receiver.
The SynchroCast3 system in the NetXpress LX multiplexer maintains the phase alignment of the
transmitted signals using Global Position System (GPS) technology, providing
● GPS controlled carrier frequency synchronization.
● GPS controlled precision audio phase alignment.
● Dynamic adjustments to compensate for network routing changes.
The SynchroCast3 system sends timing reference signals along with the audio content to the
transmitter sites. GPS receivers, placed at the Origination Point and transmitter sites, provide a timing
reference. At the Transmitter, timing signals coming from the Origination Point (along with the audio
content), are compared with the local timing reference and a precise amount of delay is introduced to
correct the timing difference between transport paths. Once the signals are synchronized, the system
operates automatically to keep the preset delay constant. The Intraplex SynchroCast3 System
Installation and Operation Manual gives more information on the SynchroCast3 system.
The SynchroCast3 system carefully controls the receive jitter buffers associated with the IP streams,
allowing multiple locations to deliver their stream data at precisely the same instant. This control is
essential for radios using multiple transmitters so that interference problems associated with them can
be minimized.
2.7.2 NetXpress LX Timing Scenarios

In a system that utilizes multiple NetXpress LX units deployed on an IP network, it is important to
maintain consistent synchronization of the internal NetXpress LX system clocks. This synchronization
ensures that any NetXpress LX system can receive streams generated by any other unit or a
combination of streams from any other units (Figure 2-4).
GatesAir, Inc. 2-13

Intraplex Products
Version 1.01
NetXpress LX
B
Multicast Audio
Stream 1
NetXpress LX
C
NetXpress LX
A
Audio Stream 2
NetXpress LX units at sites A and

C must have synchronized
NetXpress LX
system clocks so that the
D NetXpress LX unit at site D can
properly receive and process its
two incoming audio streams.
Figure 2-4. Timing Synchronization

NetXpress LX units can derive system timing in one of four ways:
1. An internal clock is available, based on a local oscillator within the unit (Internal Timing).
2. An external clock can be applied to the unit (External Timing).
3. An incoming IP unicast or multicast stream (Stream Timing), thereby synchronizing itself to the
NetXpress LX unit that generated the stream.
4. SynchroCast, which incorporates a blend of Stream and External timing from GPS receivers.
Simple point-to-point systems commonly use a combination of internal and stream timing. Figure 2-5
shows the unit at site A set to internal timing, utilizing its local internal oscillator. The unit at Site B
derives timing from the audio stream transmitted from Site A to Site B.
STREAM
INTERNAL TIMING
TIMING
NetXpress LX
NetXpress LX
B
A
Figure 2-5. Point-to-Point Timing Synchronization

The configuration advantage in Figure 2-5 is simplicity of implementation. No external timing sources
are required. This configuration can be extended to multiple site systems by designating one site as
the master timing location and having the rest of the sites derive timing from that site. Figure 2-6
shows such a system, with Site A using internal timing and the remaining sites using stream timing to
achieve synchronization to Site A.
2-14 GatesAir, Inc.

Intraplex Products
Version 1.01
Stream Timing
NetXpress LX
B
Stream Timing
Internal Timing
NetXpress LX
C
NetXpress LX
A
Stream Timing
Sites B, C, and D use stream

timing to derive timing from
NetXpress LX master Site A.
D
Figure 2-6. Stream Timing Synchronization

This method of timing distribution can be very simple and efficient in cases where programming
streams are emanating from one master site to all the remaining sites. However, programming may
be generated at multiple sites within the network, and these program source sites may not all receive
program streams from the master site that can be used as timing sources (Figure 2-7). In this
example, Site A is the master timing source, but Site C does not receive a stream from Site A and
therefore cannot synchronize its outgoing stream to the rest of the network. As a result, the two
streams received at Site D utilize different synchronization sources and cannot be properly received
and decoded.
Stream Timing
NetXpress LX
B
Internal Timing Internal Timing
NetXpress LX
NetXpress LX C
A
Site D cannot process both

NetXpress LX incoming streams because they
D have different timing sources.
Figure 2-7. Streams with Different Synchronization Sources

There are two possible solutions to this situation.
1. Receive a stream at site C from Site A solely for the purpose of synchronization (Figure 2-4). The
cost of this solution is the additional bandwidth required in the network end-link to site C.
2. An alternative approach would be to utilize highly accurate external timing sources at Sites A and
C to achieve network synchronization. One example would be a Stratum 1 traceable timing signal
GatesAir, Inc. 2-15

Intraplex Products
Version 1.01
from a telecom network provider. Another source of accurate external timing signals is a GPS
receiver, using GPS timing at the stream timing sites (Figure 2-8). This solution guarantees the
two streams received at site D have compatible timing, allowing Site D to time from either
incoming stream.
Stream Timing
NetXpress LX
B
GPS GPS
External Timing
External Timing
NetXpress LX
NetXpress LX
C
A
Site D can derive system timing

NetXpress LX
from either incoming steam.
D
Figure 2-8. Timing Synchronization with GPS

In this case, the fixed cost of purchasing and deploying GPS units at Sites A and C can be traded
against the recurring cost of bandwidth to receive a timing stream at Site C.
2.7.2.1 Backup Timing

In networks that generate revenue-critical programming, it may be prudent to design backup timing
scenarios. Each NetXpress LX unit can be programmed to switch to an alternative timing source in the
case of primary timing signal loss. If the primary timing source is an incoming stream, for example,
the secondary source could be a different stream; either an audio stream or a dedicated timing
stream. Another scenario could use Stratum-1 or GPS as the primary timing source with stream timing
as the backup. Once again, the trade-off would be the one-time cost of GPS receivers or Stratum-1
timing sources versus the recurring cost of bandwidth for the backup timing signal. If both the primary
and secondary timing sources fail, the NetXpress LX unit falls back to internal timing.
Sites that are receive-only can usually utilize stream timing since they only need to be synchronized
during the time they are receiving a stream. If receive streams at a receive-only site are changed
frequently, there could be an operational advantage to using external (stratum-1 or GPS) timing, in
that the operator would not need to consider whether or not a receive signal is present.
Certain receive sites may also generate off-air monitor streams back into the network (Figure 2-9). A
logical choice for timing in this network would be to use internal timing at Site A and stream timing at
Sites B and C. In this case, if the audio stream to Site C is lost, the monitoring stream back from Site
C is not properly timed for reception at other network sites, which can result in periodic jitter buffer
underflow or overflow at the receiver with each event causing a brief interruption or audio glitch. If it
is important to maintain smooth continuous reception of this off-air monitoring stream during periods
of primary stream loss, an external timing source or a backup timing stream is needed at Site C.
2-16 GatesAir, Inc.

Intraplex Products
Version 1.01
Stream
Timing Audio
Audio Stream NetXpress LX

B Audio Off-air monitor
Internal Timing audio
Monitor
Stream
NetXpress LX Audio Stream

A
Stream Timing
Monitor
Audio
Stream Off-air monitor
audio
Audio
NetXpress LX
C
Figure 2-9. Timing with Off-Air Monitor Streams
2.7.2.2 Timing Summary

NetXpress LX units that generate streams into the network should share a common timing reference
to guarantee that any NetXpress LX unit can receive or monitor any stream in the network. You can
use stream timing, external (Stratum-1 or GPS) timing, or a combination of the two. In cases where
audio streams are already present and can be used as timing sources, stream timing is essentially
“free.” If a dedicated timing stream must be added, the recurring cost of the stream bandwidth can be
traded off against the one-time cost of implementing GPS receivers.
You should also consider timing failure scenarios. Ideally, a fallback timing source should be available
at each site that keeps that site in synchronization with the other sites even if its primary timing
source fails. Once again, the backup source can be either a stream or an external input (Stratum-1 or
GPS) with the corresponding cost trade-off.
2.8 NetXpress LX System and FEC

The NetXpress LX system maintains uninterrupted audio transport by supporting Forward Error
Correction (FEC). Specifically, the NetXpress LX system supports RFC 2733. Forward error correction
is the process obtaining error control in data transmission in which the source (transmitter) sends
redundant data and the destination (receiver) recognizes only the portion of the data that contains no
apparent errors.
An FEC packet is a special type of RTP packet. It is constructed by placing an FEC header and FEC
payload in the RTP payload.
In the NetXpress LX system, up to 32 streams (16 in each direction) can be designated as FEC
streams. For each of the FEC streams, you can specify either of two techniques for forward error
correction: FEC LOW or FEC HIGH (Section 4.3.5.1 – Stream Creation). This specification affects the
sender only. The receiver processes all FEC packets.
FEC LOW (appropriate for most low packet loss conditions)
Single error correction is engaged. This scheme introduces a 50% overhead (increased bandwidth
required) and can correct all single packet losses – consecutive packets are not lost.
GatesAir, Inc. 2-17

Intraplex Products
Version 1.01
FEC HIGH (used in more serious packet loss conditions)

Triple error correction is engaged. This scheme introduces a 100% overhead (increased bandwidth
required) and can correct one, two, or three consecutive packet losses. In this scheme, the packet
sequence sent is critical if it is to protect against consecutive packet losses.
Table 2-3 shows the NetXpress LX performance data, with an overall loss rate and a percentage of
high versus low FEC loss.
Table 2-3. NetXpress LX FEC Performance Data
Network High Low
Loss FEC FEC
Rate Loss Loss
(%) (%) (%)
1 0.0017 0.027
2 0.0023 0.085
5 0.0168 0.507
10 0.14 2.1
11
12
13
14
15 0.597 4.87
% High FEC Loss ((Lost packets / Rx packets) x 2) x 100

% Low FEC Loss ((Lost packets / Rx packets) x 1.5) x 100
2.9 Power
The system runs on either AC or DC power supplies. The NetXpress LX-100 multiplexer supports 30 W
AC powered. The NetXpress LX-300 multiplexer supports 60 W and 95 W AC powered or 50 W DC
powered supplies.
The NetXpress LX-300 system also supports redundant power supplies. You can install a main power
supply and a redundant supply in case the main supply fails. Section 3.2.4 – Power Supply Installation
gives more information on NetXpress LX power supplies.
2.10 Voice Signaling

Voice signaling communicates voice channel call progress information over a data link. The
information, known as ABCD bits (or E & M) includes busy, idle, or other ringing state indications to
alert the caller that a call is taking place. Two types of voice signaling are robbed-bit signaling (RBS)
and channel associated signaling (CAS).
2-18 GatesAir, Inc.

Intraplex Products
Version 1.01
2.10.1 RBS
T1 systems use the RBS method of channel signaling. This information is embedded into the least
significant bit of the audio channel once every 6th frame and injected into the channel without regard
to the remaining bits. Therefore, RBS does distort the voice audio signal so slightly that you can only
perceive it by distortion measurements. RBS signaling support should not be used on channels
carrying information other than voice audio as it corrupts the data in the channel.
2.10.2 CAS
E1 systems use CAS to carry voice call information. Instead of embedding this information in the same
channel as the voice audio, channel 16 of the E1 is reserved for all of the remaining channels to use
for signaling.
2.11 Software Download

During normal operation, the CM-30 module loads the primary image. Should it fail to boot the
primary image, the module then attempts to load the secondary image.
In the case of a failure in loading both the primary and secondary image, you can configure the CM-30
module to load an image from a remote FTP server. This image is not saved to either of the flash
memory devices. You can also configure the module to load the secondary image first, but if that fails,
the module moves directly to loading from the remote FTP server and does not try to load the primary
image.
When shipped from the factory, the CM-30 IP interface module contains the most recent version of the
system software. As new features and improvements become available, the CM-30 module software
should be updated to the most current revision.
The CM-30 software can be upgraded by opening an FTP session with the module and transferring a
new image file to the flash memory device. You can configure both the primary and secondary images
to be loaded from the same file or from two different file images. In addition, you can store multiple
software images on the CM-30 module 1 up to the limit of the flash memory. To obtain the software
and boot ROM download process in the latest version’s release notes, perform these steps:
1. Go to http://www.gatesair.com/.
2. On the menu bar, point to Services & Support and click Client Support Portal.
3. Log onto the support site.
4. At Self Service, click Download Software Updates.
5. Click Intraplex | NetXpress LX.
6. Click the link for the most recent NetXpress LX version.
7. Click Save on the dialog box and save the zipped file to your hard drive.
8. Open the zipped file and open the release notes.
2.12 Configuration Files Backup and Restoration

The CM-30 module has the ability to back up and restore configuration files at any time using either
the Web browser interface or SNMP software. CM-30 module configuration is stored in multiple files on
the flash memory (/RFA/cfg). Backup/restoration ability is critical to replacing CM-30 modules. It also
facilitates in the replication of NetXpress LX systems across a network.
Once a CM-30 module is removed from a NetXpress LX shelf, the persistent configuration information
for the system remains with the CM-30 module and is not available to a new module inserted in the
system. This same information can be restored quickly from an FTP server (via Internet) to the flash
memory on the new CM-30 module. The information can also be backed up easily to the server using
GatesAir, Inc. 2-19

Intraplex Products
Version 1.01
the same process, only in reverse order. Restored configuration takes effect when the CM-30 module
is rebooted.
2.13 Fault Detection and Reporting

With the use of SNMP traps, the CM-30 system has the ability to detect and report on a number of
alarm conditions.
2.13.1 Alarm Hierarchy

The CM-30 system has major and minor alarms. A major alarm is a fault that has a direct effect on
service, such as a component failure disrupting the delivery or reception of data. A minor alarm is a
fault that has no effect on service, including all other errors detected which do not affect CM-30
operation.
The CM-30 system is also equipped with an alarm cutoff (ACO) switch. The ACO is a switch that can
be enabled to reduce the major alarm output signal to a minor alarm output as an over-ride until the
situation can be corrected.
The indicator lights on the front panel of the NetXpress LX or original Intraplex power supply modules
and on the NetXpress LX Home page give system alarm states (Section 4.3.1 – Start at NetXpress LX
Home Page):
● Red light = Major shelf alarm (Alarm)
● Yellow light = Minor shelf alarm (Alert)
● Green light = No alarm condition exists (Normal)
2.13.2 Alarm History

You can review current alarms and alarm history from the NetXpress LX Home page. Go to Faults |
Alarm Table to display the Current Alarms screen or Faults | Alarm History to display the Alarm
History screen. Both screens contain this data:
● A list of alarms
● Dates and times the alarms occurred
● Severity of the alarms
● A description of each alarm occurrence
For troubleshooting and future reference, you can also off-load he NetXpress LX system alarm history
to a text file.
2.13.3 SNMP Traps Use for Fault Reporting

SNMP traps detect and report system faults. System events that generate SNMP traps include stateful
events (considered ON/OFF alarm events) and informational events (non-alarm, one-time-only
events).
Equipment-related system events indicate a hardware failure on the CM-30 module or in the shelf.
Processing-related system events indicate a failure was detected in software processing. Facility-
related system events indicate a failure occurred with one of the operation interfaces.
The available list of SNMP traps changes with each software version. The Notification section in the
MIB file supplied with your version of CM-30 application software gives a list of available SNMP traps.
2-20 GatesAir, Inc.

Intraplex Products
No header here
Section 3 – Installation & Wiring

This section describes installation procedures and guidelines for the Intraplex NetXpress LX IP
multiplexer and CM-30 IP interface module and covers these topics:
● Tools and cable requirements
● Equipment unpacking and installation
● Transmitter and receiver installation
● Power supply installation
● Wiring and external connections
● Unit powering
3.1 Installation Preparation
3.1.1 Tools & Cables Required

Along with the equipment provided with your NetXpress LX system, these items complete the system
installation package:
● Basic telecommunications installation tool kit (such as screwdrivers and wire stripper)
● Rack mounting hardware (four threaded bolts per shelf)
● Cables for each payload channel module being installed
● Optional: a volt-ohm milliameter (VOM)
3.1.2 Equipment Unpacking & Inspection

Upon receiving your NetXpress LX system, complete these tasks:
1. Inspect all shipping containers for damage. If you observe damage, notify the shipping service as
soon as possible.
2. Unpack all equipment from containers.
3. Inspect equipment for damage.
4. Verify that the NetXpress LX unit is equipped as expected, confirming items from the packing list
(Bill of Materials):
• Chassis with rack mount or module in good condition
• Power supply, cables, and utilities
• Channel modules, MAs, and provided cables (if applicable)
If you have questions regarding possible equipment damage or shipping errors, contact Networking
Customer Service:
Warning! Follow your company’s rules regarding AC powered equipment installation. If there is a
conflict between any procedure in this document and your company’s safety rules, your
company’s safety rules must take priority.
GatesAir, Inc. 3-1

Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual 3 – Installation & Wiring
Version 1.01
3.2 Installation
3.2.1 Shelf Installation

All channel modules, common modules, module adapters, and power supplies plug into the main
equipment shelf (Figure 3-1). As a standard practice, a NetXpress LX shelf ships pre-configured with
the CM-30 module, channel modules, module adapters, and power supplies installed. All modules and
module adapters can remain in place while you install each shelf into its designated equipment rack.
Figure 3-1. NetXpress LX 1RU and 3RU Multiplexers

Consider these points for equipment shelf installation:
● If applicable, bolt the shelf into the designated equipment rack. If shelves are to be stacked in a
rack, allow at least 1RU space between shelves when using DC supplies, or 2RU space between
shelves when using AC supplies, to avoid possible heat problems.
● Make sure all modules, module adapters, and module interface units are properly seated.
Note: If the shelf is AC powered, make sure the power cable can be accessed easily for maintenance
purposes.
3.2.2 CM-30 Module Kit Installation

If you purchased a CM-30 module kit, which includes the CM-30 interface module and an MA-230
module adapter, use these steps and guidelines to install the module and module adapter in your
Intraplex multiplexer.
3.2.2.1 CM-30 Module and Indicator Lights

The CM-30 IP interface module is pre-installed into the NetXpress LX multiplexer at the factory.
However, you may need to access and service the module at some point. Insert the CM-30 module
(Figure 3-2) into the same slot number as the MA-230 module adapter in the NetXpress LX-100 (1RU)
chassis NetXpress LX-300 (3RU) chassis.
3-2 GatesAir, Inc.

Intraplex Products
3 – Installation & Wiring NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
ON
OFF
Figure 3-2. CM-30 Module and Indicator Lights
GatesAir, Inc. 3-3

Intraplex Products
Version 1.01
For IP transport in original Intraplex T1 or E1 systems, insert the CM-30 module into the same slot
number as the MA-230 module adapter in either a 3RU multiplexer or a 1RU multiplexer.
Table 3-1 gives CM-30 indicator light descriptions.
Table 3-1. CM-30 Indicator Light Descriptions
Light Color Description
WAN Green The Ethernet link is established at 100 Mbps, and the blinking light indicates activity.
100 Lnk/Act OFF There is no activity.
WAN Green The Ethernet link is established at 10 Mbps, and blinking light indicates activity.
WAN Green The Ethernet link is full-duplex.

FD OFF The Ethernet link is half-duplex.
LAN Green The Ethernet link is established at 100 Mbps, and blinking light indicates activity.
LAN Green The Ethernet link is established at 10 Mbps, and blinking light indicates activity.
10 Lnk/Act
OFF There is no activity.
LAN Green The Ethernet link is full-duplex.

FD
OFF The Ethernet link is half-duplex.
Yellow Any CM-30 loopback is enabled.

LPBK
OFF Any CM-30 loopback is disabled.
Green The system timing is locked.
Yellow There is a timing alert.

TIMG
Red There is a timing alarm.
OFF The system timing is unlocked.
Green The module is active (online).
Yellow There is an active alert.

ACTIVE
Red There is an active alarm.
OFF The module is not active (offline).
Green The module is not reporting an alarm or alert.
STATUS Yellow The module is reporting an alert.
Red The module is reporting an alarm.
3.2.2.2 CM-30 Switches and Contacts

Table 3-2 gives CM-30 switch settings.
Table 3-2. CM-30 Switch Settings
IP CFG RESET Effect
ON ON Set the system to factory default settings.
On system restart, revert the LAN interface to the factory default IP address:
ON OFF
192.168.1.1
OFF ON Start up with streams out of service and the default TDM Bus Map.
OFF OFF On system restart, the module retains the latest configurations.
3-4 GatesAir, Inc.

Intraplex Products
Version 1.01
The CM-30 module has a General Purpose Contact (GPC) port with two input and two output circuits.
The inputs are opto-isolated and can be controlled by a CMOS, an open collector, or LS TTL logic. The
outputs are normally open SPST relay closures with a maximum current of 120 mA, a maximum
voltage of 350 VDC, and a closed resistance of 23 ohms typical.
Figure 3-3 shows the contact input circuitry for Pins 1, 2, 7, and 8.
Figure 3-3. Contact Input Circuitry

The CM-30 module transports the state transitions of both input contacts along with sender
identification and input contact number. Upon receiving an input contact state transition, the module
applies that state to the same numbered output contact. The CM-30 module uses IP unicast and IP
multicast transmission for contact transport. For multicast transmissions, you must configure—on the
NetXpress LX multiplexer—the multicast group used for contact transport.
You can configure the level (high or low) at which an input contact is considered asserted. You can
view the current state of both input and output contacts, whether asserted or unasserted, with the
Web interface (Section 4.3.3.2 – Contacts) or SNMP.
3.2.2.3 MA-230 Module Adapter with Connectors and Indicator Lights

The MA-230 module adapter provides connectivity for the CM-30 interface module. Figure 3-4 shows
the MA-230 top and faceplate.
GatesAir, Inc. 3-5

Intraplex Products
Version 1.01
Figure 3-4. MA-230 Module Adapter Top and Faceplate Views

SW1 on the MA-230 module adapter performs these functions (Table 3-3):
Table 3-3. MA-230 Module Adapter SW1 Switches and Functions
Factory
Switch Default Description
This switch controls the external timing input impedance (100 Ohms; TIMING IN port). This
1 On switch is normally set to On. When daisy chaining, the last multiplexer in the chain should have
this switch On, and the others should be Off.
These two switches control the external timing input bias of the port. These switches should
2 and 3 On normally be in the On (bias) position. When daisy chaining, one module adapter in the chain
should have these switches On, and the others should be Off.
4-6 On Not used
Table 3-4 gives pin assignments for the MA-230 timing input/output and contact ports.
3-6 GatesAir, Inc.

Intraplex Products
Version 1.01
Table 3-4. MA-230 In/Out and Contact Port Pin Assignments

Connector
Port Type Protocol Comments Signals Pin Assignments
1 – Timing in positive (+)

2 – Timing in negative (-)
6-pin phone Balanced timing in TIMING IN+
IN RS-422 3 – Unused
jack (1.544 or 2.048 MHz) TIMING IN-
4 – Signal ground
5 and 6 – Unused
1 – Timing out positive (+)

2 – Timing out negative (-)
6-pin phone Balanced timing in TIMING OUT+
OUT RS-422 3 – Signal ground
jack (1.544 or 2.048 MHz) TIMING OUT-
4 – Signal ground
5 and 6 – Unused
1 and 2 – Input 1
Outputs:
8-pin phone 3 and 6 – Output 2
Contacts Open=high impedance
jack 4 and 5 – Output 1
Closed=low impedance
7 and 8 – Input 2
The MA-230 module adapter has two Ethernet ports, LAN and WAN. Both ports have these
capabilities:
● Support full-duplex and half-duplex operation
● Can operate at 100 Mbps and 10 Mbps
● Support auto-negotiation of interface rate and duplex
You can set each Ethernet port to operate independently. The LAN port provisioning default is auto-
negotiation. The WAN port provisioning default is 100 Mbps, full-duplex operation. The WAN port can
transport customer side traffic to/from the LAN interface and TDM interfaces to the network. When
connected to your LAN, the NetXpress LX system can carry packet data to or from the WAN based on
static routing rules in the CM-30 common module.
The WAN and LAN ports have indicator lights for 10 Mbps and 100 Mbps activity. Figure 3-5 shows the
port indicator light positions.
Figure 3-5. MA-230 Connectors with Indicator Lights
Note: The MA-230 module adapter’s RJ45 connector is not intended to be connected to
telecommunication networks.
3.2.2.4 MA-230 and CM-30 Module Installation and Connection

The MA-230 module adapter is installed in the slot matching the CM-30 module on the back panel of
the NetXpress LX chassis and connects with the CM-30 IP interface module at the midplane (Figure 3-
6).
GatesAir, Inc. 3-7

Intraplex Products
Version 1.01
Midplane
CM-30
Step 3 Step 1
MA-230
Step 2
Figure 3-6. CM-30 Module and MA-230 Midplane Insertion
To connect the CM-30 module and MA-230 module adapter, perform these steps:
1. Slide the MA-230 module adapter from the rear of the shelf toward the connector on the midplane.
Secure the MA-230 adapter to the back panel with the two Phillips screws that are provided.
2. Orient the white eject tab toward the bottom of the shelf (in a 3RU shelf) or toward the right (in a
1RU shelf) to prevent damage to the module.
3. Slide the CM-30 module into the designated slot from the front of the shelf toward the connector
on the midplane. Do not exert too much pressure. Both the module and the module adapter
should fit snugly onto the pins of the corresponding midplane connectors.
3.2.3 Channel Module Installation

A 1RU NetXpress LX shelf can accommodate up to five channel modules, while a 3RU NetXpress LX
shelf can accommodate up to 17 channel modules. Most existing Intraplex TDM channel modules are
compatible with the NetXpress IP multiplexer (Section 2.5.1 - Compatibility with Intraplex TDM
Channel Modules).
TDM channel modules can be installed in slots 2 through 6 on a NetXpress LX 1RU shelf and slots 2
through 18 on a NetXpress LX 3RU shelf.
Note: When installing any channel module, you must install the corresponding module adapter first.
3.2.3.1 Module Adapter Installation

Each Intraplex TDM channel module requires an installed module adapter (MA) to provide an electrical
interface to external equipment. Before plugging a channel module into the shelf slot, install the
module’s associated module adapter into the matching slot on the back of the chassis.
Warning! Hot insertion or removal of a module adapter while a channel module is in place is not
recommended, as it could damage the channel module or the module adapter. To
remove a module adapter while the system is turned on (has power), first remove the
associated channel module. Similarly, to install a new channel module, first install the
module adapter and then install the module itself.
3.2.3.2 Remote Control Operation

Each TDM channel module includes a small switch labeled REMOTE. To allow remote management of
the TDM channel modules via the NetXpress LX Home page or SNMP, enable the REMOTE mode on
each module.
3.2.3.3 SCB Address Selection

In order to permit remote management of the TDM channel modules via the NetXpress LX Home
page or SNMP, you must assign a unique SCB address for each module installed into the NetXpress
3-8 GatesAir, Inc.

Intraplex Products
Version 1.01
chassis. For consistency and ease of identification, you should set the SCB address to match the
physical slot occupied by the channel module within the NetXpress chassis. Channel modules installed
have access to bus TDM1A or bus TDM1B.
Note: Remove a module from the shelf before changing the SCB address.
3.2.3.4 Channel Module Insertion

To install a TDM channel module, orient the eject tab toward the bottom of the shelf (in a 3RU shelf)
or toward the right of the shelf (in a 1RU shelf) and slide the module into the desired slot on the front
of the shelf until it meets the connector on the front of the midplane. From the rear of the shelf, slide
the module adapter into the corresponding connector on the back of the midplane.
Warning! Do not attempt to install TDM channel modules upside down. When the module is inserted,
the eject tab should be at the bottom on a 3RU shelf or at the right in a 1RU shelf.
Verify that all modules are seated securely in position.
Warning! Hot insertion or removal of a module adapter while a channel module is in place is not
recommended, as it could damage the channel module or the module adapter. To
remove a module adapter while the system is turned on (has power), first remove the
associated channel module. Similarly, to install a new channel module, first install the
module adapter and then install the module itself.
3.2.4 Power Supply Installation
3.2.4.1 Main Power Supply Installation

NetXpress LX multiplexers normally ship pre-configured, with modules, module adapters, and power
supplies already installed. Power supply modules require no special setup. As long as they are plugged
into their slots and system power is applied, they are operating.
3.2.4.2 Redundant Power Supply Installation

Each 3RU NetXpress LX shelf can contain a second power supply for redundancy. If the main supply
fails, the system continues operating using the redundant supply. Simply insert the second power
supply into the redundant supply slot on the front (its indicators will light up identically to those on the
main supply). Due to space limitations, 1RU shelves do not have the capacity for redundant power
supplies.
If a 3RU shelf is equipped with two power supplies (main and redundant) and one of the supplies fails,
it may be removed and a new supply inserted without powering down the system.
Warning! The CM-30 module contains a replaceable battery. There is a danger of explosion if the
battery is incorrectly replaced. Only replace this battery with the same or equivalent type
recommended by the manufacturer. Dispose of used batteries according to the
manufacturer’s instructions.
3.3 Wiring & External Connections

Your NetXpress LX multiplexer must be completely wired before placing any payload circuit into
service. Installation and wiring should ONLY be performed by trained professionals.
Figures 3-7 and 3-8 identify the rear panel connectors for the 3RU and 1RU equipment shelves,
respectively.
GatesAir, Inc. 3-9

Intraplex Products
Version 1.01
Terminal strip 1 (DC power and ring generator)
Terminal strip 2 (alert and alarm relays)
MA-230 for Blank plate covering access AC power in (replaced by a blank

CM-30 to expansion connectors plate if the shelf is DC powered)
Figure 3-7. 3RU NetXpress LX Rear Panel Connectors with MA-230 Module Adapter
Connector for
alarm signal
battery and ring
generator
MA-230 for
CM-30
Available slots for module adapters

AC power input
Figure 3-8. 1RU NetXpress LX Rear Panel Connectors with MA-230 Module Adapter
Table 3-5 defines the power and alarm terminals on a 3RU shelf and lists the equivalent connection
points on a 1RU shelf (these equivalents are pins of the DB-15 alarms connector).
3-10 GatesAir, Inc.

Intraplex Products
Version 1.01
Table 3-5. Power and Alarm Connectors

Terminal 1RU
on 3RU Shelf
Shelf Pins* Description
GND screw Pin 13 Chassis GROUND
SIG BAT Pin 15 -48VDC SIGNALING BATTERY input for connecting to an external signaling voltage
source when needed by one or more channel modules. This input may also be
connected to an external loop current generator.
Warning: This voltage source must be externally fused or current limited.
+BAT A None Primary battery (+DC power output, when the shelf is DC powered). May be used
when connecting a second equipment shelf to the same DC power source. This
terminal, with -BAT A, serve as the primary connections for a DC power supply.
-BAT A None Primary battery (-DC power output, when the shelf is DC powered). May be used
when connecting a second equipment shelf to the same DC power source. Also,
normally jumpered to SIG BAT when the DC power voltage is the same as the
signaling voltage.
+BAT B None Secondary battery (+DC power input) This terminal, with -BAT B, serve as the
secondary connections for a DC power supply.
-BAT B None Secondary battery (-DC power input). This terminal, with +BAT B, serve as the
secondary connections for a DC power supply.
ALARM NO Pin 1 Alarm relay: normally open contact*
ALARM NC Pin 2 Alarm relay: normally closed contact*
ALERT NO Pin 3 Alert relay: normally open contact*
ALERT NC Pin 4 Alert relay: normally closed contact*
ALARM Pin 9 ALARM relay: COMMON

COM
ALERT COM Pin 11 ALERT relay: COMMON
* The 1RU shelf equivalents are pins on the DB-15 ALARMS connector.
** When the shelf is not powered (turned on), all relays default to their alarm positions. Normally
open contacts are closed and normally closed contacts are open.
Figures 3-9, 3-10, and 3-11 show the typical power connections to a 3RU shelf. Figure 3-12 shows the
typical connections to a 1RU shelf.
GatesAir, Inc. 3-11

Intraplex Products
Version 1.01
Figure 3-9. Connection for DC Operation of 3RU Systems
Figure 3-10. Connection for DC Operation of 3RU Systems with Two Power Sources
3-12 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 3-11. Connection for AC Operation of 3RU System with External Signal Battery
Figure 3-12. Connection for AC Operation of 1RU System with External Signal Battery
* In place of a separate signal battery, you can use a 48V DC power source with a parallel
connection from -BAT A to the SIG BAT input and +BAT to GND.
All 3RU multiplexers can be equipped with an ACS-OPT1 option, which provides separate AC power
feeds for each power supply. When the ACS-OPT1 option is in place, the rear panel looks like Figure 3-
13. For maximum redundancy, the two power cords should be connected to two different AC power
sources.
GatesAir, Inc. 3-13

Intraplex Products
Version 1.01
Figure 3-13. 3RU Multiplexer Rear Panel with ACS-OPT1 Dual AC Power Feed Option
Use this procedure to make connections for power and alarms. Each step in this procedure gives the
connection for a 3RU shelf and then the equivalent connection for a 1RU shelf in parentheses if it is
different.
1. Connect the GND screw (pin 13 of the Alarms connector on a 1RU shelf) to station ground.
2. If the shelf is AC-powered, verify that the AC cord is available. Do not plug the cord into the AC
source yet.
3. If the shelf is DC-powered
a. Verify that a 2A slow-blow external fuse is available in the DC-power line to protect the
multiplexer. Remove this fuse and do not replace it until you are ready to power up (turn on)
the shelf.
Warning! This fuse must be provided, both to protect the multiplexer and to provide a safe means of
removing power from a DC-powered shelf.
b. Connect the –BAT A terminal (the black pigtail lead on a 1RU shelf) to the negative terminal of
the station battery.
c. Connect the +BAT A terminal (both the green and white pigtail leads on a 1RU shelf) to the
positive terminal of the station battery, tied to ground.
4. Connect SIG BAT (pin 15 on a 1RU shelf) to signaling battery. This step is required only if the shelf
contains 4-wire E&M voice modules using Type I, II, or III signaling
Check with Intraplex Customer Service if you are not sure whether this battery is necessary. If the
shelf is DC-powered, a separate signal battery is not required; connect SIG BAT and chassis
ground to the DC power source.
Warning! When using a separate signaling battery, place an in-line, slow-blow fuse. The fuse should
be 1A for up to 12 voice circuits, or 2A for 13 to 24 circuits. For safety reasons, this fuse
must be installed unless the back of the multiplexer is enclosed.
5. If ALARM and ALERT contacts are to be used, connect the desired contacts to terminal strip 2 (pins
1, 2, 3, 4, 9, and 11 on a 1RU shelf).
3-14 GatesAir, Inc.

Intraplex Products
Version 1.01
3.4 Power Application

After all equipment has been installed and wired, perform these steps to apply power to each shelf:
1. Verify that all modules (common, channel, and power) are seated snugly.
2. If the shelf is AC-powered, plug in the AC line cord. If the ACS-OPT1 dual AC power feed option is
installed, plug in both AC line cords.
3. If the shelf is DC-powered, insert the external power fuse.
4. Verify that the POWER indicator light is on, and the POWER FAIL indicator light is off. In a 3RU
shelf, both the MAIN POWER FAIL and REDUNDANT POWER FAIL indicator lights should be off.
Ignore all other indicator lights on the shelf for the time being. If no lights for any power supply
are on, one of these scenarios has occurred:
• Both power modules have failed.
• Fuses on both power supply circuit boards have blown.
• Most likely, power has not been wired to the shelf.
If the POWER lights turn on, but the POWER FAIL light for one power supply is on as well, that
power module is not functioning or has a blown fuse on its printed circuit board.
Test for the correct voltages.
Note: On a 3RU shelf, if the POWER indicator lights turn on, but the POWER FAIL indicator light for
one power supply is on as well, that power module is not functioning or has a blown fuse on
its printed circuit board.
5. Observe that each CM-30 module displays indicator lights matching its current mode setting after
power is applied.
GatesAir, Inc. 3-15

Intraplex Products
No header here
This page is left blank intentionally.
3-16 GatesAir, Inc.

Intraplex Products
No header here
Section 4 – Configuration & Operation

This section gives
● Configuration procedures to set up your NetXpress LX/CM-30 system.
● Configuration options available for your NetXpress LX/CM-30 system.
● Discussion on the effect changes to system and component settings can have on system operation
and performance.
Section 4.2 – Configuration Process helps get you started with system operation. Section 4.3 –
NetXpress LX Pages walks you through all the interface pages.
4.1 Download Current Software

When shipped from the factory, the NetXpress LX system has the latest software already installed.
Check periodically to assure you continue to have the latest software version. To obtain the software
and boot ROM download process in the latest version’s release notes, perform these steps:
1. Go to Welcome to GatesAir Support.
2. At Customer Login, enter your log on information.
3. Click Download Software Updates | Intraplex | NetXpress LX.
4. Click the link of the latest software version.
5. Perform these steps to store the zipped file on your hard drive:
On the File Download box, click Save.
On the Save As box, navigate to the folder you want to store the file in.
Click Save.
6. Open the zipped file.
7. Open the release notes.
4.2 Configuration Process

After you confirm your equipment order and make any needed installations (Section 3.2 –
Installation), perform these configuration procedures.
4.2.1 Connect and Log On to Access NetXpress LX Home Page

1. Connect a PC directly to the Ethernet LAN port on the MA-230 module adapter.
Note: The MA-230 module adapter automatically senses the media type, and you may use a cable
wired as straight-through or a cross-over cable for this connection. Auto-negotiation is the
default. Your computer must be set up to auto-negotiate its IP connection.
2. Configure the IP address on the PC to be 192.168.1.10 using netmask 255.255.255.0.

3. Open your Web browser and access the NetXpress LX multiplexer using the default IP Address
192.168.1.1 for LAN.
4. A prompt appears requiring you to type a user name and password to access the NetXpress LX
Web Interface. Type the default User name = “admin” and Password = “admin”.
5. Click OK. If the credentials are accepted, the NetXpress LX Home page appears (Figure 4-1).
GatesAir, Inc. 4-1

Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual 4 – Configuration & Operation
Version 1.01
Figure 4-1. Intraplex NetXpress LX Home Page

When you initially connect to the NetXpress LX system, this Home page appears, showing an
overview of the modules installed in the multiplexer. The NetXpress LX Release system software
revision number appears in the upper left of the window. Compare this installed version with the
available update on the GatesAir Customer Care Web site (Section 4.1 – Download Current Software)
to assure you are running the most recent version. The downloadable update package also includes
installation instructions.
4.2.2 View System Mode

The operating System Mode also appears in the upper left of the Home page, either E1 or T1.
4.2.2.1 System Mode: E1

In this configuration, all four of the NetXpress LX busses (TDM1A, TDM1B, TDM2A, and TDM2B) run at
2.048 Mbps. Installed TDM channel modules also need to be E1 compatible in order to operate
properly. E1 mode does not support VF-15, VF-16A, VF-25, or VF-28 voice modules. (You can change
the System Mode using the TDM Bus Information page. Section 4.3.3.3 gives details.)
4.2.2.2 System Mode: T1

In this configuration, all four of the NetXpress LX busses (TDM1A, TDM1B, TDM2A and TDM2B) run at
1.544 Mbps. Installed TDM channel modules also need to be T1 compatible in order to operate
properly. T1 mode does not support VF-15E, VF-16AE, VF-25E, VF-28E voice modules.
4.2.3 Perform General Setup

To set up delivery of data, voice, or other information from one device to another through the
NetXpress LX system, use the procedures and guidelines on these Web interface pages:
4-2 GatesAir, Inc.

Intraplex Products
4 – Configuration & Operation NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
● Networking
● Routing
● IP Access List
● T1/E1 System Mode Selection
● Stream Creation –TDM to IP
● System Timing Configuration
● SNMP Community
● Configuration Backup/Restore
4.2.3.1 Networking
You need to change each network interface from its default IP address to the target IP address that is
appropriate for your network. The defaults IP address assigned to the network interfaces are
● 192.168.2.1 for the WAN interface – You need to change the default WAN interface IP address
to permit inter-networking of multiple NetXpress LX chassis. The WAN interface requires a static IP
address. Dynamic addressing of the WAN interface (DHCP) is not supported.
● 192.168.1.1 for the LAN interface – You need to change the default LAN interface to permit
inter-networking of multiple NetXpress LX chassis. DHCP is supported on the LAN interface.
Changes to network interfaces are made using the Network Interface Configuration page (Section
4.3.4 – Configure the Network).
4.2.3.2 Routing
Routing is necessary when the path to the destination IP address is not apparent or not within the
same local subnet as the originator. To add routing information to the NetXpress LX system, perform
these steps:
1. Point to Networking and click Forwarding (Figure 4-2).
Figure 4-2. Networking | Forwarding Table
2. Click on the Forwarding Table header (Figure 4-3).
GatesAir, Inc. 4-3

Intraplex Products
Version 1.01
Figure 4-3. Forwarding Table | Create A New Route Dialog Box

3. Type the Route Destination.
4. Type the associated Subnet Mask.
5. Type the Gateway IP address to be used to access this network.
6. Type the Routing metric or accept the system default of -1.
7. Click Add Route.
8. Click Close.
4.2.3.3 IP Access List

Only perform these steps as a security measure to lock down the system after setup.
1. Point to Security and click IP Access List (Figure 4-4).
Figure 4-4. Security | IP Access List
2. Click on the IP Access List table header (Figure 4-5).
4-4 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-5. IP Access List | Create IP Access List Entry Dialog Box
3. Type the IP Address of the host to allow access.
4. Click the Interface to customize (WAN or LAN).
5. Type the Subnet mask for this IP address, allowing single hosts or groups of hosts to be added
on the access list. For a single host, use the 255.255.255.255 mask.
6. Click Submit.
4.2.3.4 T1/E1 System Mode Selection

The default NetXpress LX (CM-30) system mode setting is T1. Use these guidelines to determine
whether to use a T1 or E1 system mode:
● The E1 system mode gives you up to 14 extra time slots of backplane bandwidth (7 per virtual
E1).
● If you are using T1-compatible voice modules, you must use the T1 system mode.
● If you are using E1-compatible voice modules, you must use the E1 system mode.
Perform these steps to set the system to E1 mode:
1. Click System Cfg | TDM Bus (Figure 4-6).
Figure 4-6. System Cfg | TDM Bus Information

2. At Configured System Mode, click the E1 option.
3. Click Submit.
4. Click System Cfg | Software Images (Figure 4-7).
GatesAir, Inc. 4-5

Intraplex Products
Version 1.01
Figure 4-7. System Cfg | Software Images Configuration

5. Change the Primary FPGA Image Filename to an E1 FPGA file name.
6. Click Submit.
7. Click Reset the System.
To change the system setting back from E1 to T1, repeat these steps, clicking the T1 option in Step 2
and changing to a T1 FPGA file name in Step 5.
4.2.3.5 Stream Creation

1. Click Streams (Figure 4-8).
4-6 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-8. Streams
2. Click on the Streams table header (Figure 4-9).
Figure 4-9. Stream Creation – Stage 1

3. On the Stage 1: Stream Type page, perform these steps:
a. Type a unique Stream Name.
b. At Stream Direction, either accept the default (Receive or Transmit) or click the Both
option to receive and transmit.
c. Click Next to advance to Stage 2 (Figure 4-10).
GatesAir, Inc. 4-7

Intraplex Products
Version 1.01
Figure 4-10. Stream Creation – Stage 2

4. On the Stage 2: Stream Features page, perform these steps:
a. Click the level of Forward Error Correction for the stream (None, Low, or High; default is
None).
b. Click a Transmission Type for the stream (Unicast, Multicast, or Multi-Unicast; default is
Unicast). If you selected Receive in Stage 2, Multi-Unicast is not an available
Transmission Type.
c. Select the Enable Voice Signaling check box for a signaling stream.
d. Type the Statistics Measurement Interval if different than 5 (default is 5).
e. Click Next to advance to Stage 3 (Figure 4-11).
Figure 4-11. Stream Creation – Stage 3 for Multi-Unicast

5. On the Stage 3: IP Config page, perform these steps:
a. Type the Destination IP Address.
b. Type the Local UDP Port.
c. Type the Remote UDP Port.
d. For a CoS Priority other than Normal, click an option (Low, Medium, or High; default is
Normal).
e. To change the packet Time To Live time period, type a number at Egress IP Pkts. TTL
(default is 5).
Note: For multi-unicast streams, remember to repeat the previous 5 steps for all stream
tabs.
4-8 GatesAir, Inc.

Intraplex Products
Version 1.01
f. Click Next to advance to Stage 4 (Figure 4-12).
Figure 4-12. Stream Creation – Stage 4 (TDM to IP)

6. On the Stage 4: TDM Bus Parameters page, perform these steps:
a. Either accept the TDM Bus default (TDM Bus 1A) or click TDM Bus 1B.
b. Click appropriate number slots to set the Frameloss Mask (a number slot becomes yellow
when selected).
c. Type the TDM Bus Starting Channel (default is 1).
d. Type the TDM Bus Channel Range (default is 1).
e. Type the TDM Bus Frames Per Packet (default is 200).
f. For Jitter Buffer Size packets other than 32, click a number (8, 16, 64, or 128; default is
32).
g. Click the Stream Program Type if different from Compressed Audio/Data (Enter
Underrun Value Manually or Linear Audio/Voice; default is Compressed Audio/Data).
h. If you selected Enter Underrun Value Manually, type a number for Packet Underrun
Byte. (If you selected Linear Audio/Voice or accepted the default, Packet Underrun Byte
is unavailable; you cannot type in this field.)
Note: You cannot directly change the values for Stream Bandwidth, Stream Delay, or
Packet Size; these values depend on the number of TDM Bus Frames per Packet.
i. Click Next to advance to the Summary page (Figure 4-13).
GatesAir, Inc. 4-9

Intraplex Products
Version 1.01
Figure 4-13. Stream Creation Summary

7. On the Summary page, note the settings. If you need to change any setting, click Prev until you
reach the appropriate page, and make your changes.
8. When the stream variables are correct on the Summary page, click Create to save your changes
or Create & Activate to save changes and put the stream in service.
Note: Configure system timing (Section 4.2.3.6) before putting any streams in service.
4.2.3.6 System Timing Configuration

1. Go to System Cfg | System Timing (Figure 4-14).
4-10 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-14. System Cfg | System Timing

2. Select the Primary Timing Source for the NetXpress LX shelf: Internal, External, Stream, or
Synchrocast.
Notes: You cannot change stream timing if streams are currently active.
If you select Stream timing, select an available Primary RX Timing Stream. You must
have a configured receive stream or bi-directional stream available (Section 4.3.5 –
Configure Streams).
3. If you select External timing, connect a timing cable from the external clock source to the
Timing In on the MA-230 module adapter.
4. Click Submit.
Note: It may take 1-2 minutes for the multiplexer to register the new system timing and the Normal
green light to turn on. The multiplexer may report an Alarm (Major alarm red light) or Alert
(Minor alarm yellow light) before it has successfully synched with the new system timing.
5. After configuring the peer to this CM-30 module in another chassis, verify the current operational
status (up, down) of the primary timing source.
4.2.3.7 SNMP Community

You only need to perform this procedure if you use SNMP. Section 4.3.4.4 – SNMP Communities gives
more information. If you only use the CM-30 software, you do not need this procedure.
1. Point to Networking and click SNMP (Figure 4-15).
GatesAir, Inc. 4-11

Intraplex Products
Version 1.01
Figure 4-15. Networking | SNMP Configuration

2. Type the Read-only community name for read-only access.
3. Type the Read-write community name for read/write access.
4. Click Save.
4.2.3.8 Configuration Backup/Restore

You can operate the NetXpress LX multiplexer without performing this procedure. However, we
recommend you save your configuration files.
1. Point to System Cfg and click Configuration Backup (Figure 4-16).
4-12 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-16. System Cfg | Configuration Files Backup/Restore

2. At Backup Configuration Server, type the IP Address, the address of an available FTP server.
3. Type the Directory where the configuration files should be stored.
4. Type the User name to back up the files.
5. Type the Password associated with the user name.
6. Click Submit to store these values.
7. Click on the Streams table header to back up the configuration files to the server.
4.3 NetXpress LX Pages
4.3.1 Start at the NetXpress LX Home Page

The starting point for all system configuration activity is the NetXpress LX Home page (Figure 4-17).
The Home page provides user access to configuration pages at the system level and at the individual
module level. It also provides a mechanism for controlling account security and individual user access.
Use the left navigation bar to move between pages. Each menu accesses one or more pages.
GatesAir, Inc. 4-13

Intraplex Products
Version 1.01
Figure 4-17. Intraplex NetXpress LX Home Page

Home: The NetXpress LX Home page.
Faults: Access pages of alarm statistics, history, and definitions, as well as system logging.
System Cfg: Access system configuration pages to set parameters such as contacts, TDM bus
mapping, system timing, and configuration backups.
Networking: Access networking parameters pages, such as Ethernet interfaces, forwarding data, and
SNMP statistics.
Streams: Access the data stream table to view, add, and edit streams.
Performance: Access system performance pages to view performance information for streams, voice
signaling, Ethernet interfaces, and so forth.
Security: Access account security settings and IP access tables.
Utilities: Access the Ping Utility page.
The blank gray slots on the page indicate places for additional channel modules or power supplies. The
populated slots indicate the CM-30 module, other modules, and the power supplies presently on the
NetXpress LX multiplexer. The top of a module slot shows the TDM bus associated with the module
and the SCB address of the module.
Note: The address shown for each module is the SCB address, not the physical slot address.
Although not necessary, it is a good practice to set the SCB address (via dip switches on the
module) to match the physical slot address in the shelf. The installation section of each
channel module’s Installation and Operation manual gives module-specific dip switch settings.
4-14 GatesAir, Inc.

Intraplex Products
Version 1.01
4.3.1.1 NetXpress LX Channel Modules

The background of a module slot normally appears white. A yellow background indicates an alert
on the module. A red background indicates an alarm.
The lower section of a module slot, directly above the Open button, shows the type of module
installed (VF-16A in this example). If the module has not been programmed, the NetXpress LX
software cannot pick up any information on it; Not Progr appears in this area rather than the
module type. Here are other module slot components:
Service: Green when module is in service.
Remote: Green when module is being accessed remotely.
Open: Click this button to configure the module or view its status.
4.3.1.2 NetXpress LX CM-30 Module

The CM label at the top of the CM-30 slot indicates it is a common module. Here are other CM-30
slot components:
WAN: This light is green if the module is running on Wide Area Network (WAN).
LAN: This light is green if the module is running on Local Area Network (LAN).
Loopback: This light is green if the module set in Loopback mode.
Timing: This light is green if the module is on primary timing, yellow if it is on secondary timing,
and red if it registers a timing fallout.
Active: This light is green if the CM-30 module is active.
Open: Click this button to configure the module or view its status.
4.3.1.3 NetXpress LX Power Supply Slots

The PS Main label at the top of a power supply slot indicates it is the main power supply. The
bottom of the power supply slot, directly above the Open button, shows the type of power
supply. Here are other power supply slot components:
Power: This light is green if the power supply is active.
Normal: This light is green if power is on and there are no alarms/alerts.
Major: This light is red in an alarm condition. (Physical power supply shows “Alarm.”)
Minor: This light is yellow in an alert condition. (Physical power supply shows “Alert.”)
The Refresh fields at the bottom left of the Home page appear on most NetXpress LX pages.
Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the
browser at 5, 10, or 30 second intervals.
4.3.2 Define & Review Fault Information

Access these pages from the Faults menu:
● Current Alarms: View any current major and minor
alarms or alarm clears.
● Alarm Definition: Set alarm severity, threshold
time, whether the alarm sends an SNMP trap, and if
the alarm triggers a major or minor light.
● Alarm History: View past alarm information.
● System Logging: View log file information and set
up alarm logging and system log server support.
GatesAir, Inc. 4-15

Intraplex Products
Version 1.01
4.3.2.1 Current Alarms

Use the Current Alarms table (Figure 4-18) to view system-detected alarms, including the date,
time, and description of each. To access this table, point to Faults and click Current Alarms. Click
any table header to sort alarm entries in ascending order by that header. On the alarms table, click
the table header a second time to sort in descending order.
Figure 4-18. Current Alarms Page

Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh
the browser at 5, 10, or 30 second intervals.
Date: The date and time the alarm occurred.
Severity: The seriousness of the alarm (Alarm, Alert, None).
Description: Helpful details about the alarm.
Clear fault: Click in the alarm row to delete that alarm from the table. Click in the table
header to delete all alarms from the table.
4.3.2.2 Alarm Definitions

Use the Alarm Definitions table (Figure 4-19) to view and edit descriptions for each alarm the
system is set to detect. To access this table, point to Faults and click Alarm Definitions.
4-16 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-19. Alarm Definitions Page

Refresh: Click to automatically refresh the browser.
ID: The specific alarm.
Alarm Name: The description of the alarm event.
Severity: The importance of the alarm (Major, Minor, or None).
Trap ID: The SNMP trap associated with the alarm.
Trap Enable: Whether the trap is Enabled or Disabled. If it is enabled, the trap is sent to the host.
LED Enable: Whether the light is enabled (turned on) or disabled.
Threshold Time: The amount of time for the system to send the trap and control light (indicator).
Edit definition: Click on the row of a specific alarm to access a Definition dialog box (Figure 4-
20) and edit the alarm definition.
Figure 4-20. Specific Alarm Definition Dialog Box
GatesAir, Inc. 4-17

Intraplex Products
Version 1.01
Alarm Name: The preset identifier for this alarm.

Severity: Select the alarm importance: None, Major, Minor, Major Clear, or Minor Clear.
Threshold time: Select the amount of time before the system sends traps and changes the lights
accordingly: None, 1 sec, 2 secs, 3 secs, 4 secs, or 5 secs.
Send an SNMP Trap: Select this check box to send a trap to the management station (host).
Turn on the LED: Select this check box to turn on the Major or Minor light associated with this
alarm.
Close: Click this button to return to the Alarm Definitions table page without applying the page
entries.
Reset: Click this button to reverse all changes to this page.
Save Definition: Click this button to apply the values entered on this page.
4.3.2.3 Alarm History

Use the Alarm History table (Figure 4-21) to view alarms that have occurred, reboots, and when the
system no longer registers an alarm. To access this table, point to Faults and click Alarm History.
Figure 4-21. Alarm History Page

Date: The date and time the alarm occurred.
Severity: The importance of the alarm (Major clear, Minor clear, Major, Minor, or None).
Description: The details of an alarm event.
Clear alarm history table: Click on the table header to delete all history table entries.
4-18 GatesAir, Inc.

Intraplex Products
Version 1.01
4.3.2.4 System Logging

On the System Logging page (Figure 4-22), you can configure the NetXpress LX system to
automatically use File Transfer Protocol (via FTP client software) to transfer log files to an FTP server
when log files are full. To access this page, point to Faults and click System Logging. If the file
transfer feature is enabled, all alarms are kept in text format in a file on the CM-30’s flash
(/RFA/log/syslog1.txt or /RFA/log/syslog2.txt). System log files are limited in size (1 MB).
Figure 4-22. System Logging Page

Log File Name: The text file name for the log.
Status: Whether the log is currently the Active one or a Backup file.
Size (bytes): The number of bytes in the log file.
Last Modified: The day of week, specific date, and time the log was most recently changed.
Alarm Logging Services

Turn on alarm logging: Select the check box to enable the internal storing of system log messages.
Turn on syslogd server support: Select the check box to begin sending alarms to the external
sysLogD server.
GatesAir, Inc. 4-19

Intraplex Products
Version 1.01
Transfer log files when full: Select the check box to enable automatic transfer of log files to an FTP
server when log files are full. You can only select this check box when the Turn on alarm logging
check box is selected.
System Log Filename on FTP Server: Type the name assigned to the system log file on the FTP
server. Default = syslog.txt.
Automatic FTP Transfer

You can only change information in these fields when both the Turn on alarm logging and the
Transfer log files when full check boxes are selected.
Save file to: Type the location to which the system log file is transferred.
FTP Server user name: Type a required FTP username for the remote FTP server.
FTP server address: Type the IP Address of the FTP server to which the NetXpress LX system
offloads system log files.
FTP server password: Type a required FTP server password for the remote FTP server.
syslogd Server
You can only change information in these fields when the Turn on syslogd server support check
box is selected.
Server address: The IP address of the server where the system log directory is to be filed.
Server UDP port number: The UDP port number for the server where the system log directory is to
be filed.

Save: Click to apply all changes to this page.
4.3.3 Configure the System

Access these pages from the System Cfg menu:
General: Configure parameters such as system
identification, date and time, and SNTP server
configurations.
Contacts: Configure input and output contacts.
TDM Bus: View the TDM bus information table, showing
signaling type and time slot activity for each TDM bus.
TDM Bus Mapping: View and map the TDM bus inter-
networking.
System Timing: View timing source information and select
the type of timing stream network.
Software Images: Set the software image management
parameters.
Configuration Backup: Set the configuration backup file
parameters and view the configuration file status table.
4-20 GatesAir, Inc.

Intraplex Products
Version 1.01
4.3.3.1 General Setup

Use the General Setup page (Figure 4-23) to enter and maintain general configuration information
for the CM-30 module. To access this page, point to System Cfg and click General.
Figure 4-23. General Setup Page

Refresh: Click this button to refresh this page in your browser.
Identification
System Name: Type a name for the NetXpress LX (CM-30) system. Default = NetXpress LX. This
name appears in the browser window and is assigned to the browser task name. This name helps
identify the system when managing multiple NetXpress LX systems on one work station.
System Location: Type a name for the physical location of the NetXpress LX system. Default =
Mason, OH.
Contact Person: Type a name or email address for the support contact person. Default =
tsupport@gatesair.com.
System Description: The system identifier describing the currently installed NetXpress LX application
image. This field is read-only.
System Up Time: The length of time since the last system restart. This field is read-only.
Date and Time

Current Date (YYYY-MM-DD): The current system date.
Current Time (HH:MM:SS): The current system time.
GatesAir, Inc. 4-21

Intraplex Products
Version 1.01
DST Start Date (MM-DD): Change the daylight savings time starting date by selecting the number
and typing a two-digit number for the month, a hyphen, and then a two-digit number for the day of
the month (for example, April 1 = 04-01).
DST End Date (MM-DD): Change the daylight savings time end date by selecting the number and
typing a two-digit number for the month, a hyphen, and then a two-digit number for the day of the
month (for example, April 1 = 04-01).
SNTP Configuration
Use an SNTP server: Select this check box to enable the use of SNTP (Simple Network Timing
Protocol) to retrieve date and time information from the network. Using SNTP requires that a SNTP
server is running on the network and is reachable by the NetXpress LX system through one of its IP
network interfaces. In some configurations, you might need to add a route to the forwarding table, as
well as the access list of the IP interface, before the NetXpress LX system can reach the SNTP server.
If SNTP is enabled, the system time and data is automatically updated to match the time information
received from the SNTP server.
You can change these two fields if the Use an SNTP server check box is selected.
SNTP server address: Type the IP address of the SNTP server.
GMT offset: Type the offset for the local time in +/- minutes from the GMT time.
SNTP server status: Indicates whether the SNTP server was reached at the specified IP address.

Submit: Click this button to apply setup information entered on this page.
4.3.3.2 Contacts
Use the Contacts page (Figure 4-24) to view and edit contacts. The input contact states are mapped
to the peer’s output contact. The IP address assigned to the input contact is the peer’s address where
the contact state messages are sent. At the peer, the incoming contact state messages are reflected
on the appropriate output contact pins. You can assign an input or output contact’s remote IP address
and select whether the input contact has a high or low priority. To access the page, point to System
Cfg and click Contacts.
Figure 4-24. Contacts Page
4-22 GatesAir, Inc.

Intraplex Products
Version 1.01
Input Contacts
Contact: The number assigned to the contact.
Remote IP Address: The specific address for this contact; the IP address where the contact state is
sent. The IP address can be unicast or multicast.
State: Whether the contact is currently asserted or deasserted.
Active Level: The contact priority when active: Active high or Active low.
Edit: Click to configure the input contact.

To configure or edit an input contact, perform these steps:
1. Click on the row of the contact to be configured. The Configure Input Contact dialog box
appears (Figure 4-25).
Figure 4-25. Configure Input Contact Dialog Box
2. To change the location of the dialog box on your monitor page, click and hold while
dragging the dialog box as desired.
3. Type the input contact’s Remote IP Address.
4. Click an Active Level option to signify the contact’s priority: Active high or Active low.
5. Click Submit to apply changes.
6. Click Close or to exit the dialog box.
Output Contacts
Contact: The number assigned to the contact.
Remote IP Address: The IP address from which the contact state messages are processed. For
unicast contact transport, this field is read-only; you cannot change it. For multicast operation, use
this field to configure the multicast group.
State: Whether the contact is currently Asserted or Deasserted.
Edit: Click to configure the output contact.

To configure or edit an output contact, perform these steps:
1. Click on the row of the contact to be configured. The Configure Output Contact dialog box
GatesAir, Inc. 4-23

Intraplex Products
Version 1.01
Figure 4-26. Configure Output Contact Dialog Box
2. To change the location of the dialog box on your monitor page, click and hold while
dragging the dialog box as desired.
3. Type the output contact’s Remote IP Address.
4. Click Submit to apply changes.
5. Click Close or to exit the dialog box.
4.3.3.3 TDM Bus Information

The TDM Bus Information page (Figure 4-27) shows signaling and time slot activity information for
the NetXpress LX TDM busses and to set the system bus mode, E1 or T1. To access the page, point to
System Cfg and click TDM Bus. Once this page appears, you can also click the edit button to change
loopback/ signaling configuration for each TDM Bus (Figure 4-29).
Figure 4-27. TDM Bus Information Page

TDM Bus: The specific TDM bus location.
Signaling: Shows the signaling mode for the bus, either None or CAS (channel associated signaling)
in E1 mode or RBS (robbed bit signaling) in T1 mode.
4-24 GatesAir, Inc.

Intraplex Products
Version 1.01
Timeslot Activity: The TDM bus time slot tables. Thirty two time slots appear for an E1 system, and
twenty four appear for a T1 system. The time slot color codes are:
● Activity in Timeslot: Green indicates a channel module is writing data to the time slot.
● No Activity in Timeslot: Gray indicates no channel module is writing data to the time slot.
● Loopback in Timeslot: Yellow indicates the time slot has been placed in either internal or
external loopback.
● Conflict in Timeslot: Red indicates multiple channel modules on the bus are trying to write data
to the same time slot(s).
Change loopback configuration: Click on a specific TDM bus row to view or change loopback
configuration operations for the bus (Figure 4-14).
Current System Mode: Indicates whether the internal TDM busses are operating in E1 or T1 mode.
Configured System Mode: Click E1 or T1 and Submit to change the configured system mode. If
you change the system mode, a dialog box appears (Figure 4-28) reminding you to re-configure the
FPGA image to reflect this change.
Figure 4-28. Changes to System Mode Dialog Box

Go to System Cfg | Software Images to complete this system mode change.
Submit: Click this button to change the current system mode.
Figure 4-29. TDM Bus Configuration Page

Refresh: Click this button to refresh the browser.
GatesAir, Inc. 4-25

Intraplex Products
Version 1.01
Internal Loopback Settings: Shows the Internal Loopback settings applied for each channel of the
TDM bus. Click a channel number to change its loopback setting. Click the table header to change the
internal loopback setting for all channels of the TDM bus.
External Loopback Settings: Shows the External Loopback settings applied for each channel of the
TDM bus. Click a channel number to change its loopback setting. Click the table header to change the
external loopback setting for all channels of the TDM bus. The loopback color codes are:
● Loopback Enabled in Timeslot: Yellow indicates that loopback is enabled in the specific channel.
● Loopback Disabled in Timeslot: Gray indicates there is no loopback in the specific channel.
Back: Click this button to return to the TDM Bus Information page.
Submit: Click this button to apply all bus configuration changes on this page.
4.3.3.4 TDM Bus Mapping Configuration

The CM-30 module contains a switch fabric that allows manual interconnection of internal TDM busses
when you want to initiate multi-unicast streams to more than two destinations. On the transmit side,
the switch fabric allows content from a single source to be sent across to four unicast destinations. On
the receive side, it allows incoming content to be replicated to the other backplane bus on the same
time slots. When echo modules are installed, the system automatically detects them and performs
internal maping to allow non-multi-unicast streams to be created.
The TDM Bus Map Configuration page shows each available target receive endpoint (TDM1A,
TDM1B, IP1, IP2, IP3, and IP4) displayed as individual columns and lists the source transmit endpoint
(where each target receives its data) for all available channels. Each item is capable of bidirectional
communication, so the names for transmit endpoints are the same as those for receive endpoints. The
name of an endpoint associated with a particular channel in the table describes the source of data for
that channel. To access the page, point to System Cfg and click TDM Bus Mapping (Figure 4-30 for
E1 mode and 4-31 for T1 mode).
The NetXpress LX system has an automatic default profile that connects each of the internal TDM
busses once from an IP source and connects to two IP destinations twice, allowing default multi-
unicasting to two IP destinations. If one echo module is installed, it is tied to 1A. If both echo modules
are installed, they are tied to both 1A and 1B.
To allow for further multi-unicasting operation, you need to create a user profile to map the
appropriate internal TDM bus time slots to the corresponding IP busses. This user profile is internally
stored and applied each time the system restarts.
Table 4-1 shows the two types of profiles available.
Table 4-1. TDM Bus Map Profiles
Profile Connections Application
Default TDM 1A and TDM 1B Use when all of the audio, voice, and data sources are coming from
are connected once Intraplex channel modules in the NetXpress LX system, and the
from the WAN and destination for all of the sources is another NetXpress LX system on the
twice toward the IP network.
WAN
User Defined Created by the user Use when your application does not match the predefined profile but
through the Web instead requires IP multi-unicast streams to more than two destinations.
interface.
If your network does not support multicasting, you can configure the CM-30 system to multi-unicast
up to four destinations/IP addresses. In order to use multi-unicasting with this system, a transmit
unicast stream must be created for every destination you wish to reach. You must also specify busses
for each stream. These source programs can be replicated to four different IP destinations. You also
need to specify a multi-unicast time slot range for the channel module program that is to be multi-
unicasted. Please note that the process of multi-unicasting consumes a significant amount of
4-26 GatesAir, Inc.

Intraplex Products
Version 1.01
bandwidth within the IP network. As previously mentioned, if you require multi-unicasting beyond the
system default, you need to create a user-defined profile with appropriate internal to IP bus mapping.
To access and configure bus mapping, point to System Cfg and click TDM Bus Mapping (Figures
4-30 and 4-31).
The TDM Bus Map Profile drop-down list offers the default profile (Default TDM Profile) and the
User Defined Profile. To create a different bus map configuration, select User Defined Profile to
access the Edit TDM Bus Configuration page. All streams must be out of service before the TDM bus
map can be altered.
Figure 4-30. TDM Bus Map Configuration Page – T1 Mode

Chan: This row indicates the specific TDM bus channel that this configuration pertains to.
TDM 1A, TDM 1B: The two TDM busses.
IP 1, IP 2, IP 3, IP 4: The IP connections.
Edit Map Manually: Click this button to access the edit page (Figure 4-31) and create a custom
configuration. Streams must be out of service in order for this button to be available.
TDM Bus Map Profile: If the TDM bus mapping still matches the factory default settings, the Default
TDM Profile map appears. If the TDM bus has been customized from the original settings, the User
GatesAir, Inc. 4-27

Intraplex Products
Version 1.01
Defined Profile map appears. Select the Default TDM Profile from the drop-down list and click
Submit to restore the default TDM bus mapping. Streams must be out of service in order for this
menu to be available.
Submit: Click this button to apply the selected profile.
Note: If any streams are currently in service, the Edit Map Manually and TDM Bus Map Profile
list are unavailable. You must first place all streams out-of-service before changing the TDM
bus map.
Figure 4-31. Edit TDM Bus Map Configuration Page
TDM Endpoints
Receive endpoint: The destination endpoint for the connection. You can select multiple receive
endpoints if the Connect In Both Directions check box is not selected. If this check box is selected,
you can only select one receive endpoint. There are two possible receive endpoints, the two internal
TDM busses.
Transmit endpoint: The source endpoint for the connection. Besides the six endpoints, there are two
additional possible selections: “All 1s” and “All 0s”. Connecting “All 1s” or “All 0s” to a receive endpoint
disconnects it from any of the six possible endpoints.
Starting timeslot: Type the number of the time slot where this connection begins (automatically
populated if the Connect Entire Bus check box is selected).
Number of timeslots: Type the number of time slots to be used for this connection (automatically
populated if the Connect Entire Bus check box is selected).
Echo Cancellation: Click to route the time slots through one of the CM-30 module’s echo canceller
devices. Default is None. The Echo Cancellation options are only available when you map a TDM to
IP connection in both directions and an echo canceller module is installed (auto-detected) in the
NetXpress LX multiplexer.
4-28 GatesAir, Inc.

Intraplex Products
Version 1.01
Connection Options
Connect entire bus: Select this check box to connect all the time slots (channels) on the bus.
Connect in both directions: Select this check box to create bi-directional data connections.
Break current transmit connections: Select this check box to break any connections between the
transmit endpoint and any receive endpoints that currently exist before making the new connections.
Clear all connections: Select this check box to clear all connections among all endpoints.
Submit: Click this button to apply configuration edits to the current TDM bus map.
4.3.3.5 System Timing

The System Timing configuration page (Figure 4-32) gives primary and secondary NetXpress LX
system timing parameters that you can configure. The NetXpress LX system supports these methods
of timing: Internal, External, Stream, and SynchroCast. To access the page, point to System Cfg
and click System Timing.
Note: When you are configuring several receive streams and you are using a stream as the timing
source, it is highly recommended that the stream with the highest packet rate (that is, the
lowest number of frames per payload value) be used as the primary timing stream.
Figure 4-32. System Timing Page
GatesAir, Inc. 4-29

Intraplex Products
Version 1.01
Current Timing Status

Current source: The timing source the system currently uses. If both the primary and secondary
timing sources have failed, the system operates on its internal clock.
Primary Timing Source Status: The current operational status (Up or Down) of the primary timing
source.
VCXO calibration value: Timing calibration value (in ppm) for the voltage controlled crystal oscillator
(factory calibration only).
PLL Lock Status: The Phase-Locked Loop status (Locked or Unlocked) indicates when the
NetXpress LX system is operating synchronously with the current timing source. The status is
Unlocked when both the primary and secondary timing sources are unavailable, so this NetXpress LX
system is running asynchronously.
Secondary source: The current operational status (up, down) of the secondary timing source.
Timing configuration
Primary source: The primary timing source for the NetXpress LX shelf. Timing choices are Internal,
External, Stream, or SynchroCast.
Internal can only be chosen as the Primary Timing Source for a single NetXpress LX system within
your network. All remaining NetXpress LX systems can derive that same timing source using Stream
timing.
Multiple systems can be set to External Timing if a common source of external timing is available at
all locations. This external timing is typically a satellite (GPS) derived clock or a public telecom
network clock source. External timing must be cabled into the NetXpress LX system using the TIMING
IN jack on the MA-230 module adapter.
Streams must be placed out-of-service to change the primary or secondary timing source selection.
SynchroCast is a valid choice for timing only if you have an SNC-101T module installed in the
NetXpress LX system. If you select SynchroCast3 timing as the primary timing source, you cannot
select External as the secondary timing source.
Primary receive stream: If the primary timing source is set to Stream, this field shows the stream
name to use as the timing source.
Primary stream network type: The network quality to be applied for clock recovery from the
primary stream (Dedicated, Metro, Continental).
Secondary source: The secondary timing source for the NetXpress LX shelf. Choices are Internal,
External, or Stream. The secondary timing source cannot be the same as the primary timing source
except in the case of Stream, but even then the selected streams must be unique.
Secondary receive stream: If the secondary timing source is set to Stream, this field shows the
stream name to use as the timing source.
Secondary stream network type: The network quality to be applied for clock recovery from the
secondary stream (Dedicated, Metro, Continental).
Submit: Click this button to apply all system timing information entries on this page.
4.3.3.6 Software Images Configuration

When the NetXpress LX system first starts up, the CM-30 module attempts to load its operating
system from the Primary Image Filename along with its associated Primary FPGA Image
4-30 GatesAir, Inc.

Intraplex Products
Version 1.01
Filename. If the primary file cannot be loaded, the system attempts to load from the Secondary
Image Filename along with its associated Secondary FPGA Image Filename. Should this file also
fail, the CM-30 module attempts to load the Backup Image Filename from the network FTP
fileserver along with the Backup FPGA Image Filename.
The Software Images page (Figure 4-33) gives CM-30 specific software image parameters that you
can configure. To access the page, point to System Cfg and click Software Images. The latest
NetXpress LX version’s release notes contain the software image file and boot ROM image file
configurations.
Figure 4-33. Software Images Page
Flash Images
Primary image filename: The name of the main software image file.
Primary FPGA filename: The name of the primary Field Programmable Gate Array (FPGA) file.
Current Image Loaded: This read-only field provides the status on which software image was last
loaded (Primary, Secondary, or Backup).
GatesAir, Inc. 4-31

Intraplex Products
Version 1.01
Secondary image filename: The name of the secondary software image file.
Secondary image filename: The name of the secondary FPGA file.
Load on Next Boot: Select an option to specify the image to use when the system is restarted, thus
overriding the default and forcing the CM-30 module to load the Primary, Secondary, or Backup
image.
Backup Image Server

Image filename: The name of the backup software image file.
IP address: The IP address of the backup image FTP server.
FTP username: FTP username for the backup image server.
FPGA filename: The name of the backup FPGA file.
Gateway IP address: The default gateway to get to the backup image FTP server.
FTP password: The FTP user password for backup image server.
Submit: Click this button to apply all configuration entries on this page.
Reset the System: Click this button to physically reset the CM-30 module after performing a
software image load. If you have made any configuration changes on this page, click Submit and wait
for the page to refresh. If your changes have been stored, the file names you entered still appear in
the file name boxes. If the system was unable to find a file matching your entry, the file name box
reverts back to its original selection. Once you verify your desired values are stored properly, click
Reset the System for the CM-30 module to restart with the new values.
NetXpress LX Flash Device Directory: Shows the current directory location of the NetXpress LX
flash device. Use this field to type a new directory location and click Change Directory to submit the
new entry.
Change Directory: Click this button to access the contents of the directory on the NetXpress LX flash
device given in the Directory on NetXpress LX Flash Device field. Use /RFA/ as a valid root
directory.
The table below the Change Directory button lists files stored on the NetXpress LX flash drive. This
information is present on the page in order to assist you in locating the available file names of the
primary and secondary image and FPGA image files. Section 4.1 gives the procedure to obtain the
software and boot ROM download process in the latest version’s release notes.
4.3.3.7 Configuration Files Backup and Restore

You can view and configure access to your network backup FTP server on the Configuration Files
Backup/Restore page (Figure 4-34). An FTP server is required to preserve an archival copy of your
NetXpress LX configuration files or to restore these files to the NetXpress LX system.
To access the page, point to System Cfg and click Configuration Backup. Fields on this page need
to match the parameters of your network FTP server program including the server IP address, backup
server directory location, user name, and password. Many FTP server programs are available
commercially, some of which are freeware (such as TYPSoft FTP Server, Cerberus FTP Server, Cesar
FTP). Restored configuration files do not take effect until the CM-30 module is restarted.
4-32 GatesAir, Inc.

Intraplex Products
Version 1.01
Header
Icons
Config File
Row Icons
Figure 4-34. Configuration Files Backup/Restore Page

Backup Configuration Server

IP address: Type the IP address of the configuration backup server (the address where the FTP
server resides).
Directory: Shows the backup server directory you created and specified in the FTP server program.
User name: Shows the configuration backup server user name (created in the FTP server program).
You must type a valid user name to perform a configuration backup or restore.
Password: Shows the configuration backup server password (created in the FTP server program).
You must type a valid password to perform a configuration backup or restore.
Reset the System: Click this button to perform a physical resetting of the CM-30 module.
Submit: Click this button to apply the configuration information on this page.
Configuration Files
Configuration File Name: Identifies the name of the configuration file to be backed up or restored.
Backup/Restore Status: Identifies whether the file transfer is in process or idle.
GatesAir, Inc. 4-33

Intraplex Products
Version 1.01
Backup: Click to back up the configuration file for the row selected. Click in the table header
to back up all the configuration files. The backup procedure copies the CM-30 files to the FTP server.
Restore: Click to restore the configuration file for the row selected. Click in the table header to
restore all configuration files. The restore procedure copies files from the FTP server to the CM-30
module.
Delete: Click to delete the configuration file for the row selected. Click in the table header to
delete all the configuration files.
4.3.4 Configure the Network

Network configuration (Networking) in the CM-30 system
includes these pages:
Ethernet Interfaces: View and set network addressing
configurations.
Forwarding: View and add routes to the IP address forwarding
table.
Class of Service: View and edit DiffServ markings for forwarded
packets, type of service (TOS) to priority mapping, and TOS byte
configurations.
DiffServ Marking: View and add an address to the DiffServ
markings for forwarded packets table, which includes source and
destination IP addresses and subnet masks and Type of Service
information.
SNMP: View and configure the SNMP (Simple Network
Management Protocol) community and event hosts.
UDP: View the UDP (User Datagram Protocol) Listener table and
set the UDP port number for signaling.
TCP: View the TCP (Transmission Control Protocol) connections
table of local and remote IP addresses and port numbers and
connection states.
ARP: View the ARP (Address Resolution Protocol) table of Media
Access Control and IP addresses for the system and other
devices it communications with.
4.3.4.1 Ethernet Interfaces

To access the Ethernet Interfaces page, point to Networking and click Ethernet Interfaces. Once
the Ethernet Interfaces page appears, click on an interface row to view and modify address
parameters for that interface. Figure 4-35 shows parameters on both the WAN and LAN interfaces.
4-34 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-35. Ethernet Interfaces Page – WAN and LAN Interfaces
GatesAir, Inc. 4-35

Intraplex Products
Version 1.01
Interface: The interfaces with access permission (WAN and LAN).

IP Address: The network IP address used for this interface.
MAC Address:
Speed/Duplex: The speed at which data packets are being transmitted on this interface and the
duplex mode for transmission (Full Duplex, Half Duplex).
Auto-Negotiation: Whether or not auto-negotiation is currently used for this interface.
Actual State: Whether this interface is currently Up (in service) or Down (out of service).
Desired State: Whether this interface is set to be Up or Down.
Put the WAN interface in service or out of service: If the interface is Up, click to set it
Down. If the interface is Down, click to set it Up.
Configure the WAN interface: Click for the specific interface to view configuration details
and/or configure the interface.
Ethernet Configuration
MAC Address: Media Access Control address. Read-only.
Interface Speed: Click an option for numbers of bits transmitted per second (100 Mbits/sec or 10
Mbits/sec). This option cannot be changed when auto-negotiation is initiated (that is, when the Turn
on auto-negotiation check box is selected).
Turn on auto-negotiation: Click this check box to initiate auto-negotiation for the port.
Interface Mode: Whether the interface is operating in full duplex or half duplex mode. Read-only.
IP Configuration
Use DHCP: (LAN interface only) Select this check box to initiate Dynamic Host Configuration Protocol
(DHCP) for this interface.
IP address: Type the network IP address to be used for this interface.
Allow SNMP: Select this check box to accept SNMP traffic on this interface.
Allow FTP: Select this check box to accept FTP sessions on this interface.
Block ICMP Error packets: (WAN interface only) – Click this check box to block all ICMP Error
packets from entering the processor.
Blocked packets: The number of packets that have been blocked since this interface has been in
service. Packets are blocked because they contain a protocol (SNMP, HTTP, Telnet, or FTP) that is
blocked on the interface.
Subnet mask: The address of the subnet mask received by DHCP. Read-only.
Allow HTTP: Select this check box to accept HTTP traffic on this interface.
Allow Telnet: Select this check box to accept Telnet sessions on this interface.
Save: Click this button to record and apply configuration entries on this page.
4.3.4.2 Forwarding Table

Review, create, and edit IP forwarding information for all traffic associated with your Intraplex
NetXpress LX IP Multiplexer on the Forwarding Table page (Figure 4-36). Point to Networking and
click Forwarding. Default routes are automatically created based on the IP addresses assigned to the
4-36 GatesAir, Inc.

Intraplex Products
Version 1.01
WAN and LAN interfaces. When the page appears, review the table, edit entries, or delete entries
(except for automatically assigned routes), or click to create and submit a new IP route (Figure 4-
37).
Figure 4-36. Forwarding Table

Destination: The destination IP address of the route.
Netmask: The logic mask to be combined with the destination address before comparison. The
netmask defines the scope of an IP address and what addresses can exist on that same logical subnet.
Gateway: The gateway routing IP address.
Interface: The description of the interface using this route.
Type: The type of routing (direct, indirect, or invalid).
Protocol: The learned routing mechanism for this route.
Age: The length of time since the route was last updated.
Metric: The primary routing metric for this route.
Add a route: Click to create a new IP route.

Delete this route: Click to delete the specific IP route.
GatesAir, Inc. 4-37

Intraplex Products
Version 1.01
Figure 4-37. Add a Route Dialog Box

Route destination: The destination IP address of this particular route. You may type “0.0.0.0” to
create a default rout to the interface.
Subnet Mask: The logic mask to be combined with the destination address before comparison. The
subnet mask defines the scope of an IP address and what addresses can exist on that same logical
subnet.
Gateway IP address: The IP address of the gateway device responsible for final routing of IP
address for this route.
Routing metric: Primary routing metric for this route.
Close: Click this button to return to the Forwarding Table page.
Add Route: Click this button to apply the information entered and create a new route.
4.3.4.3 Class of Service
Use the Class of Service menu to view and configure this DiffServ and type of service (TOS)
information:
DiffServ Marking: View and add entries for source and destination IP and subnet masks for
forwarded packets. You can use this table to remark the TOS field for the selected IP flow (or flows)
with a configured DiffServ value when traversing from LAN to WAN.
DiffServ Priority Mapping: View and edit TOS value priorities. Use this table to prioritize the IP
packets internal to the system.
TOS Byte Configurations: View and edit stream and system TOS values.
DiffServ Marking
View the source and destination IP and subnet masks for forwarded packets and the type of
service (TOS) for forwarding (Figure 4-38) and add an address entry. To access this page, point to
Networking and click DiffServ Marking.
4-38 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-38. DiffServ Marking for Forwarded Packets Page

Refresh: Click to manually refresh the browser.
Source IP Address: The IP address from which the forwarded packet originates.
Source Subnet Mask: The mask used to determine the subnet to which the source IP address
belongs.
Destination IP Address: The IP address to which the forwarded packet is delivered.
Destination Subnet Mask: The mask used to determine the subnet to which the destination IP
address belongs.
TOS Value: The type of service used for forwarding this packet; the DiffServ value from 0 to 63.
Add an address: Click to access the Add a DiffServ Marking Entry dialog box (Figure
4-39).
GatesAir, Inc. 4-39

Intraplex Products
Version 1.01
Figure 4-39. Add a DiffServ Marking Entry Dialog Box
Move: Click and hold while dragging the dialog box as desired
Source IP address: Type the IP address where the packet originates. This address is used to
classify the IP flow.
Source Subnet mask: Type the subnet mask for the source IP address. This mask is used to
Destination IP address: Type the IP address for the packet’s destination. This address is used to
Destination Subnet mask: Type the subnet mask for the destination IP address. This mask is
used to classify the IP flow.
TOS value: Type the DiffServ value: 0 to 63.
Close: Click this button or to return to the DiffServ Marking for Forwarded Packets page
without creating an entry.
Add Entry: Click this button to create a DiffServ marking entry.
DiffServ TOS to Priority Mapping

View and edit TOS value priorities on this table (Figure 4-40). To access the table, point to
Networking | Class of Service and click DiffServ Priority Mapping.
4-40 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-40. DiffServ TOS to Priority Mapping Page

TOS Value: The DiffServ value number: 0 to 63.
Priority: Whether the TOS value has a High or Low importance.
Edit the priority of DiffServ code point: Click to change the TOS value priority (Figure
4-41).
Figure 4-41. Map TOS Value to Priority Level Dialog Box

TOS Value: The type of service value number, a unique numeric identifier for the TOS value.
Priority Level: Select the level of priority for the TOS value: High or Low (default is Low).
Close: Click this button or to return to the DiffServ Marking for Forwarded Packets page
without creating an entry.
Submit: Click this button to apply the priority level change to the TOS value.
GatesAir, Inc. 4-41

Intraplex Products
Version 1.01
TOS Byte Configurations

View and edit both stream and system TOS byte parameters (Figure 4-42). To access this page,
point to Networking | Class of Service and click TOS Byte Configurations.
Figure 4-42. TOS Byte Configurations Page

The system and stream TOS values are the full 8-bit value of the IP TOS field. The defaults are
based on traditional IP precedence. You should change the values based on the routed network
configuration.
Stream TOS Values
TOS Value for High COS: This field sets the IP TOS (Type of Service) byte for packets from a
stream configured with a high COS (Class of Service). The default value is 184.
TOS Value for Medium COS: This field sets the IP TOS byte for packets from a stream
configured with a medium COS. The default value is 48.
TOS Value for Normal COS: This field sets the IP TOS byte for packets from a stream configured
with a normal COS. The default value is 40.
TOS Value for Low COS: This field sets the IP TOS byte for packets from a stream configured
with a low COS. The default value is 0.
System TOS Values
Web TOS Byte Setting: This field sets the IP TOS byte used by the HTTP packets coming out of
the NetXpress LX system. The default value is 48.
Voice Signaling TOS Byte Setting: This field sets the IP TOS byte used by the signaling
transmission packets. The default value is 48.
SNMP TOS Setting: This field sets the IP TOS byte used by the SNMP packets coming out of the
NetXpress LX system. The default value is 48.
4-42 GatesAir, Inc.

Intraplex Products
Version 1.01

Submit: Click this button to save and apply all changes to this page.
Note: Although the system can assign TOS to traffic leaving the NetXpress LX system, the
effectiveness of tagging packets with TOS/COS depends solely on support from the routers
within the IP network.
4.3.4.4 SNMP Configuration

Use the SNMP Configuration page (Figure 4-43) to establish and manage the Simple Network
Management Protocol (SNMP) event host configuration for Hosts 1 and 2. An SNMP community is a
group of hosts that you can manage as a distinct group with SNMP. The SNMP communities group
contains a list of community/IP address pairs identifying those management stations from which the
agent on the local host accepts queries. Along with each pair is an access field that controls whether
access is allowed, and if so, whether the access granted is read-only or read-write. In addition, the
special community public restricts or allows access to all other members of the public community. To
access this page, point to Networking and click SNMP.
Figure 4-43. SNMP Configuration Page

SNMP Communities
Read-Only community name: The SNMP community name a SNMP manager must use to read an
element of the NetXpress LX MIB.
Read-Write community name: The SNMP community name a SNMP manager must use to modify
an element of the NetXpress LX MIB.
Enable traps on authentication failures: Click this check box to initiate traps for failed logon
attempts.
GatesAir, Inc. 4-43

Intraplex Products
Version 1.01
SNMP Event Hosts

Host 1 IP address: The IP address of the event host 1, usually the computer running the primary
network manager application. If the address is 0.0.0.0, this entry is not active.
Host 1 Community name: The community name given to the SNMP trap. The community name
identifies a collection of SNMP managers and agents.
Host 2 IP address: The IP address of the event host 2. If the address is 0.0.0.0, this entry is not
active.
Host 2 Community name: The community name of the SNMP trap. The community name identifies a
collection of SNMP managers and agents.
Save: Click this button to record and apply configuration entries on this page.
4.3.4.5 UDP Listeners Table

UDP (User Datagram Protocol) is the IP standard protocol that allows an application program on one
machine to send a datagram to an application program on another machine. To access the UDP
Listener Table (Figure 4-44), point to Networking and click UDP.
Figure 4-44. UDP Listeners Table

Local IP Address: The local IP address for the UDP listener.
Local UDP Port Number: The port number assigned to the UDP IP address.
UDP port for voice signaling: The user-selected UDP port number for signaling. Default is 49155.
Submit: Click this button to save and apply all changes to this page.
4-44 GatesAir, Inc.

Intraplex Products
Version 1.01
4.3.4.6 TCP Connection Table

The TCP connection table contains information about an entity’s existing TCP connections. To access
the TCP Connection Table page (Figure 4-45), point to Networking and click TCP.
Figure 4-45. TCP Connections Table

Local IP: The local IP address for this TCP connection.
Local Port: The local port number for this TCP connection.
Remote IP: The remote IP address for this TCP connection. This identifies the computers that are
actively connecting to the NetXpress LX system.
Remote Port: The remote port number for this TCP connection. HTTP traffic typical operates on port
80.
Connection State: The state of this TCP connection: listen or established.
4.3.4.7 ARP Table

The ARP (Address Resolution Protocol) Table shows the Media Access Control (MAC) address and
associated IP addresses of the NetXpress LX shelf and other shelves with which the NetXpress LX shelf
has communicated. The ARP dynamically binds a high level IP address to a low-level physical
hardware address. To access the ARP Table (Figure 4-46), point to Networking and click ARP.
GatesAir, Inc. 4-45

Intraplex Products
Version 1.01
Figure 4-46. ARP Table

IP Address: The IP address of the NetXpress LX shelf.
MAC Address: The Media Access Control address provided by the ARP.
Type: The type of addressing used.
Source Interface: The interface used to learn the entry in the ARP table.
Flush the ARP Table: Click to delete all ARP Table entries.
4.3.5 Configure Streams
You can use the Streams table (Figure 4-47) to add and configure packet streams in
the NetXpress LX system. You need to configure streams at all end points in the
network and instruct the NetXpress LX system to link portions of data among the
TDM busses, electrical ports, or IP destinations. The NetXpress LX system supports
up to 32 full-duplex streams. Streams cannot share the same destination channels
on one NetXpress LX system unless one of the streams is first placed out of service.
To access the table, click Streams.
4-46 GatesAir, Inc.

Intraplex Products
Version 1.01
Header
Icons
Stream
Row Icons
Figure 4-47. Streams Table

To activate (put in service), edit, or delete a stream, click the appropriate icon at the end of the row
for the specific stream. The icons in the header row allow you to add a stream, put all streams in
service, or delete all streams. Click any stream table headers to sort the stream table in ascending
order by that header. Click the header again to sort the stream table in descending order.
Bandwidth (kbits/sec): The bandwidth (in kilobits per second) being used by streams in service at
this time out of the total stream bandwidth (in kilobits per second) required for stream traffic if
you were to activate all of the streams listed in the table.
FEC Streams: The number of IP packet streams in service at this time using forward error correction.
No more than 10 full-duplex streams using FEC are allowed to be in service at a time out of the total
number of IP packet streams using forward error correction.
Telephony Streams: The number of telephony (voice signaling) streams in service at this time out of
the total number of telephony (voice signaling) configured streams created.
ID: An assigned index that uniquely identifies each stream.
Name: The description label that you assign to the stream. If you point to the stream name with your
cursor, additional stream details appear.
Destination: The destination (IP address or electrical interface) for the stream.
Direction: Whether the stream is set to Transmit, Receive, or Both. Multicast streams are always
uni-directional (that is, either Transmit or Receive).
Date Created: The time and date when this stream was created.
Up Time: The length of time this stream has been continuously operational.
Operational State: The actual operational state of the stream: Up, Down, or In Progress.
Admin State: Provisioned state of the stream session: In Service or Out of Service. This status
provides administrative control information regarding the most recent state to which the stream was
set.
Put stream in service/out of service: Click for a specific stream to put the stream in service
(activate it). Click on the header row to put all streams in service. Click the ID of individual
streams to select multiple streams, and then click or on the header row to change the admin
GatesAir, Inc. 4-47

Intraplex Products
Version 1.01
state of many streams at once. Click for a specific stream to put the stream out of service
(deactivate it). Click on the header row to put all streams out service.
Add/Edit/Delete: Click to add a stream, to edit a stream, or to delete a stream. Click

in the header row to delete all streams.
Clock: after the stream name indicates that it has been selected as a timing stream.
Phone: after the stream name indicates that voice signaling is up for the stream. after the
stream name indicates that voice signaling is enabled for the stream but is not up (in service).
Table 4-2 shows the possible combinations of administrative and operations stream states.
Table 4-2. States Associated with Streams
Administrative Operational
State State Comments
Out of Service Down This combination signifies a created stream that is not currently in service.
In Service Down For bidirectional and receive-only streams, you have put the stream in service, but
the NetXpress LX system has not received any packets. Transmit-only streams have
this combination if the interface is down or a route does not exist to the destination.
Out of Service Up This combination is not possible.
In Service Up You have put the stream in service, and the NetXpress LX system has received
packets.
In Service In Progress The process of activating the stream is proceeding.
4.3.5.1 Stream Creation
To add a packet stream, click on the Streams table. The Stream Creation – Stage 1 page
Stream Creation Stage 1
Figure 4-48. Stream Creation – Stage 1 Page – Stream Type

Stream Name: Type a unique name describing the stream.
Stream Direction: Click Transmit or Both to change the stream direction to transmitting or
bidirectional. Receive is the default direction.
Cancel: Click this button to return to the Streams table without creating a new stream.
Next: After completing the Stream Creation – Stage 1 page, click this button to proceed to the next
stream creation page (Figure 4-49).
4-48 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-49. Stream Creation – Stage 2 Page – Stream Features

Stream Name: The unique name entered in Stage 1 that describes the stream.
Forward Error Correction: Click Low or High to specify the type of forward error correction to be
applied to this stream. The default None indicates that forward error correction is not to be applied.
Transmission Type: Click either Multicast or Multi-Unicast (only for transmit streams) to change
the packet transmission. Unicast is the default. Multi-Unicast offers multiple tabs on the Stream
Creation – Stage 3 page (Figure 4-50) to assist you in creating duplicate streams.
Enable Voice Signaling: Select this check box to enable telephony signaling transmission for the
stream. You need to enable signaling to transport telephone call progress signals and E&M state
changes on voice frequency (VF) TDM channel modules. Signaling is transmitted out-of-band in a
separate data stream that gets created when the voice stream is put in-service. For NetXpress LX
GatesAir, Inc. 4-49

Intraplex Products
Version 1.01
systems operating in E1 mode, you also need to enable CAS signaling for the internal TDM bus on
which the voice channel module resides. Otherwise, the signaling bits are not sent over the network.
The next two fields appear if you select the Enable Voice Signaling check box.
Voice Card Used: Select the voice module to be used for signaling, and the system determines the
signaling insertion byte: Enter signaling insertion byte manually, VF-15 or VF-16A, VF-16A in
VF-25 mode or VF-25, or VF-40.
Signaling Insertion Byte: If you selected to enter the insertion byte manually, type the byte
number. If you selected a voice module, this field is read-only.
Statistics Measurement Interval (sec): Provides update interval (in 5 to 10 seconds) on the
stream statistics. The default is 5 seconds.
Cancel: Click this button to return to the Streams Table page without creating a new stream.
Prev: Click this button to return to the Stream Creation Stage 1 page.
Next: After completing the Stream Creation – Stage 2 page, click this button to advance to the
Stream Creation – Stage 3 page (Figure 4-50).
Note: If you clicked Multi-Unicast for Transmission Type on the Stream Creation – Stage 2
page, Stage 3 shows four tabs (Figure 4-51). You need to fill in the IP parameters on each tab
for that specific stream before clicking Next to advance to Stage 4 of the stream creation
process.
Figure 4-50. Stream Creation – Stage 3 Page – IP Parameters
4-50 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-51. Stream Creation – Stage 3 Page – IP Config for All Streams (Multi-Unicast)
Multicast or Destination IP Address: Type the IP address for the WAN interface of the NetXpress
LX system at the other end of this stream.
Local UDP Port: Type the local UDP port in ingress and egress stream packets. The local UDP port
number must be a multiple of 5 between 50000 and 65535, inclusive.
Remote UDP Port: Type the remote or peer’s UDP port for ingress and egress stream packets. The
remote UDP port number must be a multiple of 5 between 50000 and 65535, inclusive.
CoS Priority: Click the CoS level option that applies to all egress packets for the stream: Low,
Medium, Normal, or High. Normal is default.
When the operational state of a receive stream changes to Down, the type of alarm created depends
on the CoS level selected here. A Normal or High level stream going down would create a major
alarm. A Medium level stream going down would create a minor alarm. A Low level stream going
down would not create any hardware alarm but would still contain an entry in the Current Alarms
and Alarm History tables for logging, traps, and other information. You can change the severity of
these alarms on the Networking | Class of Service | TOS Byte Configurations page.
Egress IP Pkts. TTL: Type the value of the IP TTL (Time to Live, # of hops) to be used in egress
stream packets. The default is 64. This number is decremented once by every router that handles the
packet. Once this field reaches 0, the packet is discarded by the router and does not reach any other
systems.
Prev: Click this button to return to the Stream Creation – Stage 2 page.
Stream Creation – Stage 4 page (Figure 4-52).
Note: For multi-unicast streams, remember to click each stream tab and configure the stream
parameters on the corresponding page before going to the Stream Creation – Stage 4 page.
GatesAir, Inc. 4-51

Intraplex Products
Version 1.01
Figure 4-52. Stream Creation – Stage 4 Page – TDM Bus Parameters

TDM Bus: Select the TDM bus (TDM Bus 1A or TDM 1B) for the source of the stream data.
Assert frame loss on stream down: Select this check box to indicate that frame loss (FRML) signals
are to be asserted when the stream encounters loss of ingress packets.
Each bus includes a signal known as FRML, which the channel modules use to mute audio when a
receive stream goes down. If frame loss is enabled on a stream, the loss of that stream causes frame
loss to be asserted on all channel modules residing on that same bus.
TDM Bus Starting Channel: Type the number of the starting time slot (channel) on the TDM bus for
this stream. The default is 1.
TDM Bus Channel Range: Type the number of time slots (channels) on the TDM bus to include in the
stream. The default is 1.
TDM Bus Frames per Packet: Type a number to define the “packetization” interval for the stream.
(Section 2 gives information on packetization.) The maximum frames per payload can go up to 1000
depending on the number of timing TDM channels encapsulated per frame. The maximum payload size
cannot exceed 1400 bytes. The default is 200.
Jitter Buffer Size (packets): Select the number of packets in the jitter buffer: 8, 16, 32, 64, or
128. The default is 32. Streams using FEC are restricted to jitter buffer sizes of 32, 64, or 128.
Increasing the size of the jitter buffer increases the system’s ability to compensate for network jitter
but also increases the latency of the packet stream.
4-52 GatesAir, Inc.

Intraplex Products
Version 1.01
Stream Program Type: Select Compressed Audio/Data (0 channel value), Linear Audio/Voice
(255 channel value), or Enter Underrun Value Manually to type a value between 0 and 255 at
Packet Underrun Byte. The type of stream program defines the contents of the underrun buffer,
which is played out to the internal TDM bus any time there is no packet from the IP network to play.
Since different types of channel modules react differently when receiving long strings of bits with a
zero value or a one value, changing the value of the underrun byte can improve how the module
behaves when the network drops packets. For example, APT-x compression modules mute faster when
presented with a long string zero valued bits.
Packet Underrun Byte: When Enter Underrun Value Manually is selected in the Stream
Program Type field, the Packet Underrun Byte field is enabled so that you can define the value of
the underrun byte. Type a value between 0 and 255. If you select a value other than Enter Underrun
Value Manually for the Stream Program Type, the Packet Underrun Byte field is read-only.
Stream Bandwidth (kbits/sec): The amount of bandwidth in kilobits per second required by the
stream, automatically computed based on number of TDM Bus Frames per Packet. This field is
read-only.
Stream Delay (milliseconds): The initial jitter/lead position in the Jitter Buffer, automatically
computed based on Jitter Buffer Size.
Packet Size (bytes): The number of bytes in a stream packet, automatically computed by adding
TDM Bus Frames per Packet and overhead (62). This field is read-only.
Stream Creation Summary page (Figure 4-53).
GatesAir, Inc. 4-53

Intraplex Products
Version 1.01
Stream Creation Summary
Figure 4-53. Stream Creation Summary Page

This page shows information from the previous Stream Creation pages.
Create: After assuring all entries are correct, click this button to actually create the stream.
Create & Activate: After assuring all entries are correct, click this button to create and activate the
stream on the shelf. This button is enabled only if TDM bus is connected to an IP port in the TDM bus
map.
4-54 GatesAir, Inc.

Intraplex Products
Version 1.01
4.3.5.2 Stream Changes

To edit, delete, or put an existing stream in or out of service, you must click an icon on the Streams
table.
● Edit – To edit an existing stream, click at the end of the stream’s row on the stream table
page to access the Stream Configuration page (Figure 4-54).
● Delete – To delete an existing stream, click at the end of the row.
● In Service – Click to put a stream in service.
● Out of Service – Click to take a stream out of service.
Use these icons in the stream table header row to put all streams in service, take all streams out of
service, or delete all streams.
Figure 4-54. Stream Edit Pages
Use the specific Stream Configuration page as you did the Stream Creation pages (Figures 4-48
through 4-53).
GatesAir, Inc. 4-55

Intraplex Products
Version 1.01
Notes: You cannot edit a stream when it is in service. If the stream is in service when you access the
Stream Configuration page, the Put Out of Service button appears. Click this button to
enable changes to stream information on the page.
When you first access a Stream Configuration page, the Reset and Submit buttons are
unavailable. If you change any data on the page, these buttons become available.
When the Enable Voice Signaling check box is selected, the Voice Card Used and
Signaling Insertion Byte fields appear.
4.3.5.3 Stream Group

Click the ID cell on the stream row to add that stream to the stream group. The selected ID cell
appears blue. Once a stream is added to the group, the , , and in the header of the stream
table operate on all streams in the group instead of all streams in the table. Any stream in the stream
group has an ID in blue. You can remove a stream from the group by clicking its stream ID cell again;
the selection highlight color on the stream disappears. To add or remove all streams from the stream
group, hold down the SHIFT key and click the stream ID header.
4.3.6 Check Multiplexer Performance

Use the Performance menu in the CM-30 system to monitor IP multiplexer performance. Review this
performance information:
Streams: View stream statistics, including the number of
received and transmitted packets; packets lost, early, or late;
and the number of packets in the receive queue.
Voice Signaling: View the Voice Signaling Statistics table.
Ethernet Interfaces: The WAN and LAN Ethernet Interface
Statistics pages.
SNMP: The SNMP Statistics table.
UDP: The UDP Statistics table.
TCP: The TCP Statistics table.
ICMP: The ICMP Statistics table.
IGMP: The IGMP Statistics table.
IP: The IP Statistics table.
4.3.6.1 Stream Statistics

The Streams Statistics table (Figure 4-55) shows statistics from the current interval for each stream
in the table. To access the table, point to Performance and click Streams. Click the ID number of a
stream to access performance history. (Figure 4-56 shows Stream 1 history.) Point to a table header,
and a tooltip appears that gives a definition of the statistic.
4-56 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-55. Stream Statistics Page
Figure 4-56. Performance History Page

Index: On the Performance History page, the system records individual stream statistics for 10
index intervals.
GatesAir, Inc. 4-57

Intraplex Products
Version 1.01
Packet Count
● Rx: The accumulated number of packets received for the stream.
● Tx: The accumulated number of packets transmitted for the stream.
Rx Packet Statistics
● Recovered: The number of packets recovered using Forward Error Correction.
● Lost: The accumulated number of packets that were lost in the packet network. Total underrun
packets minus the sum of early and late packets.
● Under: The accumulated number of times the system had to play out an underrun packet in the
time interval. An underrun condition can happen due to a lost, early, or late packet.
● Early: The accumulated number of packets that were discarded by the system because they
arrived too soon to play out.
● Late: The accumulated number of packets that were discarded by the system because they
arrived after the playout time passed.
Rx Queue
● Cur: The current number of packets present in the jitter buffer at the instance the statistics were
sampled.
● Min: The minimum number of packets that were present in the jitter buffer in the interval.
● Max: The maximum number of packets that were present in the jitter buffer in the interval.
● Avg: The average number of packets present in the jitter buffer in the interval.
Meas PDV: The Measured Packet Delay Variation is the average of maximum and minimum packets
present in the jitter buffer.
Close: Click this button to close the Performance History page.
Clear History: Click this button to clear the stream statistics performance history for the selected
stream.
4.3.6.2 Voice Signaling Statistics

The Voice Signaling Statistics table (Figure 4-57) shows state change, packet loss, and out of order
information for voice signaling streams. To access this table, point to Performance and click Voice
Signaling.
Figure 4-57. Voice Signaling Statistics Page

Index: The assigned number that uniquely identifies the stream in the stream table.
Stream Name: The unique name you assigned to the stream.
Tx Signaling State Changes: The number of transmit call state changes per signaling stream.
Rx Signaling State Changes: The number of receive call state changes per signaling stream.
Packets Lost: The number of lost packets per signaling stream.
Packets Out of Order: The number of packets received out of order per signaling stream.
4-58 GatesAir, Inc.

Intraplex Products
Version 1.01
Clear the voice signaling stats: Click on the stream row to clear all signaling statistics for that
stream. Click on the table header to clear all statistics on the table.
4.3.6.3 Ethernet Interface Statistics – WAN and LAN

The read-only Ethernet Interface Statistics pages (Figure 4-58) show statistics such as packets
received, sent, and discarded and the time elapsed since the interface was last changed. To access the
WAN or LAN statistics, point to Ethernet Interfaces and click WAN or LAN. (These pages have
identical fields, so this section shows only the WAN interface.)
Figure 4-58. Ethernet Interface Statistics Page – WAN and LAN

Total octets received: The number of 8-bit units of data received.
Total octets sent: The number of 8-bit units of data sent.
Unicast packets received: The number of packets received for this IP address only.
Unicast packets sent: The number of packets sent to one IP address only.
Non-unicast packets received: The number of received packets sent to multiple IP addresses
(broadcast or multi-cast).
Non-unicast packets sent: The number of packets to be sent to multiple IP addresses (broadcast or
multi-cast).
Input packets discarded: The number of received packets that were discarded.
Output packets discarded: The number of packets sent that were discarded.
Receive errors: The number of received packets with errors.
Transmit errors: The number of transmitted packets with errors.
Unknown protocols received: The number of protocols received that were not identified.
Interface last change: The time elapsed since this interface has changed.
GatesAir, Inc. 4-59

Intraplex Products
Version 1.01
4.3.6.4 SNMP Statistics

This read-only page (Figure 4-59) shows the SNMP (Simple Network Management Protocol) message
statistic totals since the system was last rebooted. To access the SNMP Statistics page, point to
Performance and click SNMP.
Figure 4-59. SNMP Performance Page

Message Statistics
Total messages received: The number of messages delivered to the CM-30 SNMP Agent from the
transport service.
Total messages sent: The number of messages passed from the CM-30 SNMP Agent to the transport
service.
GET requests received: The number of Get-Request PDUs (protocol data units) accepted and
processed by the CM-30 SNMP Agent.
GET requests sent: The number of GET requests sent by the CM-30 SNMP Agent to another SNMP
protocol entity in the network.
4-60 GatesAir, Inc.

Intraplex Products
Version 1.01
GET responses received: The total number of Get-Response PDUs received by the CM-30 SNMP
Agent from another SNMP protocol entity in the network.
GET responses sent: The total number of Get-Response PDUs generated by the CM-30 SNMP Agent.
GET NEXT requests received: The total number of Get-Next PDUs accepted and processed by the
CM-30 SNMP Agent.
GET NEXT requests sent: The total number of Get-Next PDUs generated by the CM-30 SNMP Agent.
SET requests rcvd: The total number of Set-Request PDUs accepted and processed by the CM-30
SNMP Agent.
SET requests sent: The total number of Set-Request PDUs sent by the CM-30 SNMP Agent to
another SNMP protocol entity in the network.
Total variables requested: The total number of requested variables; the number of variable
bindings processed by the CM-30 SNMP agent
Total variables sent: The number of objects altered successfully by the CM-30 SNMP Agent as the
result of receiving valid Set-Request PDUs.
Traps received: The total number of unsolicited messages (traps) received by the CM-30 SNMP
Agent from another SNMP entity in the network.
Traps sent: The total number of trap PDUs generated by the CM-30 SNMP Agent.
Message Errors
“Too Big” errors: The total number of PDUs for which the value of the error-status field was ‘tooBig’.
“No Such Name” errors: The total number of PDUs with an error-status field value of ‘noSuchName’.
“Bad Value” errors: The number of PDUs with an error-status field value of ‘badValue’.
Generic errors: The total number of PDUs with an error-status field value of ‘genErr’.
“Bad Community” errors: The total number of messages using an SNMP community name not
known to the entity.
ASN Parsing Errors: The total number of ASN.1 or BER errors the Agent found when decoding
received messages.
4.3.6.5 TCP/UDP Statistics

The read-only TCP/UDP Statistics page (Figure 4-60) shows User Datagram Protocol (UDP) and TCP
(Transfer Control Protocol) statistical information. To access this page, point to Performance and
click TCP/UDP.
GatesAir, Inc. 4-61

Intraplex Products
Version 1.01
Figure 4-60. TCP/UDP Performance Page

Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the
browser at 5, 10, or 30 second intervals.
UDP Statistics
Datagrams received: The total number of datagrams received.
Datagrams sent: The total number of datagrams sent.
Datagrams with no listener: The total number datagrams received for which no application in
the system was listening to the destination port.
Datagrams received in error: The number of datagrams received that could not be delivered for
reasons other than the lack of an application at the destination port.
TCP Statistics
TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees
delivery of data and also guarantees that packets are delivered in the same order in which they were
sent.
Segments received: The total number of segments received, including those received in error.
Segments sent: The total number of segments sent, including those on current connections.
Current Connections: The number of TCP connections for which the current state is either
ESTABLISHED or CLOSE-WAIT.
4-62 GatesAir, Inc.

Intraplex Products
Version 1.01
Segments Retransmitted: The number of segments transmitted which contains one or more
previously transmitted octets.
Segments received with error: The number of messages received that were determined to have
ICMP-specific errors (bad TCP checksums, and so forth).
Segments sent with RST Flag: The number of segments sent which contain the RST (reset) flag.
Number of connection resets: The number of established connection resets that have occurred.
Failed connection attempts: The number of times TCP connections have made a direct transition to
the CLOSED state from either SYN-SENT state or SYN-RCVD state, plus the number of times TCP
connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
CLOSED to SYN-SENT transitions: The number of times TCP connections have made a direct
transition to the SYN-SENT state from the CLOSED state.
LISTEN to SYN-RCVD transitions: The number of times TCP connections have made a direct
transition to the SYN-RCVD state from the LISTEN state.
4.3.6.6 ICMP Statistics

The read-only ICMP Performance page (Figure 4-61) shows statistical information related to
Internet Control Message Protocol (ICMP). ICMP delivers error and control messages from hosts to
message requestors. An ICMP test may determine whether a destination is reachable. To access this
page, point to Performance and click ICMP.
GatesAir, Inc. 4-63

Intraplex Products
Version 1.01
Figure 4-61. ICMP Performance Page
General Message Statistics

Total messages received: The total number of received Internet Control Messages.
Total messages sent: The total number of transmitted Internet Control Messages.
Destination unreachable received: The number of received ICMP Destination Unreachable
messages.
4-64 GatesAir, Inc.

Intraplex Products
Version 1.01
Destination unreachable sent: The number of sent ICMP Destination Unreachable messages.
Redirect received: The number of received redirect messages. A redirect message is sent to the
originating computer when a better route is discovered for a datagram sent by that computer.
Redirect sent: The number of sent redirect messages.
Source quench received: The number of requests received to cut back the rate at which it is
sending traffic to the Internet destination.
Source quench sent: The number of requests sent to cut back the rate at which it is sending traffic
to the Internet destination.
Error Message Statistics

Inbound messages with errors received: The number of received messages with errors.
Inbound messages with errors sent: The number of sent messages with errors.
Time exceeded received: The number of received time-to-live (TTL) exceeded messages. A time-to-
live exceeded message is sent to the originating computer when a datagram is discarded because the
number of routers it has passed through exceeds its time-to-live value.
Time exceeded sent: The number of sent time-to-live (TTL) exceeded messages.
Parameter problem received: The number of received parameter-problem messages. A parameter-
problem message is sent to the originating computer when a router or host detects an error in a
datagram's IP header.
Parameter problem sent: The number of sent parameter-problem messages.
Timestamp Message Statistics

Timestamp request received: The number of received time-stamp requests. A time-stamp request
causes the receiving computer to send a time-stamp reply back to the originating computer.
Timestamp request sent: The number of time-stamp requests sent.
Timestamp reply received: The number of time-stamp replies received.
Timestamp reply sent: The number of time-stamp replies sent. A computer sends a time-stamp
reply in response to receiving a time-stamp request. Routers can use time-stamp requests and replies
to measure the transmission speed of datagrams on a network.
Echo Message Statistics

Echo request received: The number of ICMP Echo (request) messages received. An echo request
causes the receiving computer to send an echo reply message back to the originating computer.
Echo request sent: The number of echo requests sent.
Echo reply received: The number of echo replies received. A computer sends an echo reply in
response to receiving an echo request message.
Echo reply sent: The number of echo replies sent.
Address Mask Message Statistics

Address mask request received: The number of address mask requests received. A computer
sends an address mask request to determine the number of bits in the subnet mask for its local
subnet.
Address mask request sent: The number of address mask requests sent.
GatesAir, Inc. 4-65

Intraplex Products
Version 1.01
Address mask reply received: The number of address mask responses received. A computer sends
an address mask response in response to an address mask request.
Address mask reply sent: The number of address mask responses sent.
4.3.6.7 IGMP Statistics

The read-only IGMP Performance page (Figure 4-62) shows Internet Group Management Protocol
(IGMP) statistics relative to your CM-30 operation. IGMP is the standard for IP multicasting. All hosts
conforming to level 2 of the IP multicasting specification require IGMP. To access this page, point to
Performance and click IGMP.
Figure 4-62. IGMP Performance Page

Total queries received: The total number of incoming queries received.
Outgoing membership report sent: The total number of membership reports sent.
Outgoing membership leaves sent: The total number of membership leave messages sent.
Group Address: The IP multicast group address for which this entry contains information.
Membership Reports Sent: The number of membership reports sent for the group.
Total Queries Received: The number of times the router has sent queries for this group.
Up Time: The time elapsed since this entry was created.
4-66 GatesAir, Inc.

Intraplex Products
Version 1.01
4.3.6.8 IP Statistics
The read-only IP Performance page (Figure 4-63) shows IP statistical information related to your
CM-30 operation. IP is a standard regulating how packets of data are transported across the Internet
and recognized as incoming messages. (The statistics shown here do not include statistics on IP
datagrams that are sent over the WAN interface as a result of streams.) To access this page, point to
Performance and click IP.
Figure 4-63. IP Performance Page

Datagram Statistics
Total received: The total number of input datagrams received by the CM-30 IP protocol stack,
including those received in error.
Total sent: The total number of UDP datagrams sent from the CM-30 system.
Total forwarded: The number of datagrams forwarded by the CM-30 system to another destination
in the network.
Total delivered: Total number of IP datagrams received by the CM-30 system.
GatesAir, Inc. 4-67

Intraplex Products
Version 1.01
Default TTL: The default Time to Live (TTL) value put in each IP packet sent by the CM-30 system.
The TTL defines the number of router hops that can be made before this packet is dropped.
Error Statistics
Inbound datagrams discarded: The number of input IP datagrams that were received by CM-30 IP
protocol stack with no errors but were discarded for other reasons (for example, for lack of buffer
space).
Outbound datagrams discarded: The number of output IP datagrams received by the IP protocol
stack with no errors but were discarded for other reasons (for example, lack of buffer space).
Received header errors: The number of packets containing header errors.
Received address errors: The number of packets received by the CM-30 system containing
addressing errors.
Unknown protocols errors: The number of packets received by the CM-30 system containing
unknown protocols.
Unroutable datagrams: The number of datagrams received by the CM-30 IP protocol stack that
could not be routed.
Fragmentation Statistics
Fragments received: The number of received packets fragmented successfully.
Fragments sent: The number of frames requiring fragmentation before sending.
Datagrams reassembled: The number of fragmented datagrams that have been reassembled by the
CM-30 IP protocol stack.
Datagrams fragmented: The number of fragmented datagrams received by the CM-30 IP protocol
stack.
Datagrams failing reassembly: The number of attempted datagram reassemblies by the CM-30
system.
Datagrams failing fragmentation: The number of datagram fragmentations that failed.
4.3.7 Set Up Security

Security configuration in the CM-30 system includes these tables:
Accounts: A list of existing user accounts. You can add, edit, and delete
accounts from this table.
IP Access List: A list of IP addresses that are allowed to manage the
system via the interface. You can add or delete accounts from this table.
4.3.7.1 Accounts
Use the Web Interface User Accounts configuration table (Figure 4-64) to view existing user
accounts and to establish and control user access and FTP privileges through password entry. To
access the table, click Security | Accounts. You can change account passwords and user groups and
delete user accounts from this table.
4-68 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-64. Web Interface User Accounts Page

Refresh: Click to automatically refresh the browser.
Web Interface Accounts
User Name: If the username exists, the system displays it in the account entry page (GUI or FTP). If
it does not exist, type a username for account access.
User Group: The group this user account is associated with: admins or basic. Members of the
admins group have full access to edit and control the system. Members of the basic group may only
log in to view the system status and configuration.
Status: Whether the user account is activated (Enabled) or deactivated (Disabled).
Add a user account: Click on the table header to access the Edit User Account dialog box and
create a new account (Figure 4-65).
Edit user: Click on a user account row to change the password of that account (Figure 4-66).
Remove user: Click on a user account row to delete that account.

FTP Account
There is a default FTP user account on the system.
User name: The user name associated with this account. The default ftp user name is ftpuser.
Password: The password associated with this account. The default ftp password is ftpuser.
GatesAir, Inc. 4-69

Intraplex Products
Version 1.01
Reset: Click this button to reverse all changes on this page.

Submit: Click this button to save and apply all changes on this page.
Figure 4-65. Add User Account Dialog Box

User name: Type a name for this user account.
User password: Type a password for the user name.
User group: Select a group for this user account: admins or basic.
Enable user account: Clear this check box to create but not activate the user account. The check
box is selected by default; when this check box is selected and you click Submit, the user account is
both created and activated (enabled).
Close: Click this button to exit the dialog box without saving any entries.
Submit: Click this button to apply the new entries on this page.
Figure 4-66. Edit User Account Dialog Box

User name: The name of the user account; this field is read-only.
User group: Select a group for this user account: admins or basic. (This field is read-only for
admins user groups.)
Enable user account: Clear this check box to create but not activate the user account. The check
box is selected by default; when this check box is selected and you click Submit, the user account is
both created and activated (enabled).
New password: If you are changing a password, type it in this field.
Confirm password: Retype the password in this field.
Current password: If you are changing an account password, type the existing password in this
field.
Close: Click this button to exit the dialog box without saving any entries.
Submit: Click this button to apply the new entries on this page.
4-70 GatesAir, Inc.

Intraplex Products
Version 1.01
4.3.7.2 IP Access List

The IP Access List table contains a list of IP addresses allowed to manage the system via the
interface. If the list is empty, any address on any interface can access the system. To access the page
(Figure 4-67), point to Networking and click IP Access List.
Figure 4-67. IP Access List Page

Interface: The interfaces with access permission (WAN or LAN).
IP Address: The IP addresses that are currently permitted on the specific interface.
Subnet Mask: The logic mask to be combined with the destination address before comparison. The
subnet mask defines the scope of an IP address and what range of addresses can exist on that same
logical subnet.
Add an address: Click on the table header to add a new IP Access List entry (Figure 4-68).
Delete address: Click on the specific address row to delete that address.
Note: If you are adding the first entry on the interface that connects you to the system, be certain to
add your own IP address to prevent control lockout.
Figure 4-68. Add an IP Address Dialog Box
GatesAir, Inc. 4-71

Intraplex Products
Version 1.01
IP Address: Type an IP address for this entry.

Interface: Click an interface option for this address.
Subnet mask: Type a subnet mask address for this IP address.
Close: Click this button to return to the IP Access List page without creating an entry or after
creating an entry.
Add Address: Click this button to create an address entry within the IP Access List.
4.3.8 Send Echo Requests

You can send echo requests to a host IP address using the PING Utility page
(Figure 4-69). To access this page, point to Utilities and click Ping.
Figure 4-69. Ping Utility Page

Host IP Address: Type the target (Host IP address) for the ping request.
Don’t Route Past Local Network: Select this check box to limit the ping request to the local subnet
only.
Number of Packets: Type a number of echo requests (packet ping requests) to be sent or click the
arrows to increase or decrease the displayed number. The default value is 1.
PING Result: The result of the ping request (Got Response or No Response).
Send Ping: Click this button to execute the ping request.
4.3.9 Configure CM-30 Module

On the Home page of the NetXpress LX interface, click Open on the CM-30 module to access these
configuration pages:
● General
● Revisions
● Program Boot ROM
Click a tab to access that page.
4.3.9.1 CM-30 General Configuration

The General configuration page (Figure 4-70) allows you to view information for the CM-30 module
(such as IP and MAC addresses, serial number, and insertion date) and modify the board description.
4-72 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-70. CM-30 Common Module: General Page

Board description: The unique name you give this CM-30 module. To set a name for the module,
type the name and click Submit.
IP address 1: The address for this CM-30 module. Read-only.
IP address 2: An alternate address for this CM-30 module. Read-only.
MAC address 1: The Media Access Control address for this CM-30 module. Read-only.
MAC address 2: An alternate address for this CM-30 module. Read-only.
Serial number: The serial number assigned to this module when it was manufactured. Read-only.
Manufacturing date: The date the CM-30 module was manufactured in the factory. Read-only.
Module up time: The number of days, hours, minutes, and seconds the module has been in service.
Read-only.
Insertion date: The date and time of the last system restart. Read-only.
Echo cancellers installed: The number of echo cancellers currently installed. Read-only.
Last software upgrade date: The date the system software was last updated. Read-only.
GatesAir, Inc. 4-73

Intraplex Products
Version 1.01
Loopback state: Whether or not there is a loopback set for the system.
Reset the System: Reset the CM-30 system.
Submit: Apply all changes you made to this page.
4.3.9.2 CM-30 Revisions Configuration

The Revisions configuration page (Figure 4-71) allows you to view version information for the CM-30
module (such as application, FPGA, and hardware board revision) and modify the board description.
Figure 4-71. CM-30 Common Module: Revisions Page

Application version: The version number of the CM-30 application software currently running. Read-
only.
Application creation date: The date and time the NIM application software was built. Read-only.
FPGA version: The version number of the CM-30 FPGA (Field Programmable Gate Array) image file.
Read-only.
CPLD version: The version number of the CM-30 CPLD (Complex Programmable Logic Device). Read-
only.
Bootloader version: The revision number for the bootloader software used to load the application
software from the Flash device. Read-only.
Hardware board revision: The revision number for this CM-30 module board. Read-only.
Hardware assembly number: The CM-30 board factory assembly number. Read-only.
4.3.9.3 CM-30 Program Boot ROM Configuration

The Program Boot ROM configuration page (Figure 4-72) allows you to view and modify the Boot
ROM Load Image configuration information used to program the CM-30 system boot code.
4-74 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-72. CM-30 Common Module: Program Boot ROM Page

Boot ROM image filename: The name of the Boot ROM file selected for programming on this CM-30
module. This field is normally left blank when not programming.
Programming status: The current status of the program command (Idle, In Progress, or
Completed). Read-only.
Program: Click this button to initiate the boot code programming command.
NetXpress LX Flash Device Directory: The current directory location of the NetXpress LX flash
device. Use this field to type a new directory location and click Change Directory to submit the new
entry.
Change Directory: Click this button to access the contents of the directory on the NetXpress LX flash
device given in the Directory on NetXpress LX Flash Device field. Use /RFA/ as a valid root
directory.
The table is a directory listing the files stored on the NetXpress LX flash. This information is present on
the page in order to assist you in locating the available boot ROM file name. Section 4.1 gives a
procedure to access the latest version’s release notes for the software and boot ROM download
process.
4.3.10 Configure Individual Modules (TDM Channel Modules)

From the NetXpress LX home page, you can access configuration and status pages for individual TDM
modules and channel access modules. Click the Open button for the desired module displayed on the
Home page.
GatesAir, Inc. 4-75

Intraplex Products
Version 1.01
Figures 4-73 and 4-74 show the configuration and status pages for a DA-91A Data Polling Module.
Once you access the configuration page, click the Status tab to access the module’s status page.
Figure 4-73. DS-64NC Configuration Page
Figure 4-74. DS-64NC Status Page
The P Codes section of each module’s operation manual gives additional details on configuration
parameters for specific audio, voice, and data modules. This section contains configuration and status
sample pages for Intraplex program audio (PT-353 – Figures 4-75 and 4-76), voice (VF-25E – Figures
4-77 and 4-78), and data (DS-64NC – Figures 4-79 and 4-80) modules.
4.3.10.1 Sample Program Audio Module Configuration and Status
Figure 4-75. PT-353 Configuration Page
4-76 GatesAir, Inc.

Intraplex Products
Version 1.01
Alias Name: The name you specify for the module to help identify the module type.
Shelf Name: The name you specify for the multiplexer shelf housing the module.
Card Address: Each module must have a unique address in the shelf. Valid addresses are 1 through
36.
TDM Bus: The TDM bus on which the channel module resides.
Module Adapter: The type of module adapter being used with the module.
Remote Control: The mode of operation the module is set to use: REMOTE or LOCAL.
Enable Module: Select this check box to place the module in service. If not selected, the module is
offline.
Module Configured: Whether the module is properly configured.
TDM Bus Configuration

Timeslot: The desired starting time slot (1 to 24 in T1 system, 1 to 31 in E1 system).
TDM B: The current bus side, either Bus A or Bus B.
Skip Timeslot 16: Select this check box to set the module for use in a 2MB (E1) multiplexer set for
CAS signaling and thus skip time slot 16.
Audio Configuration
Bandwidth: Select a bandwidth from the drop-down list: 32 ksps, 44.1 ksps, or 48 ksps.
Mode: Select a mode from the drop-down list: Mono or Stereo.
Turn Test Tone On: (PT modules only) Select this check box to enable a built-in +8dB test tone on
the active channels.
Use J.17 Emphasis: Select this check box to enable emphasis on the outgoing signal in accordance
with ITU-T Recommendation J.17. If the transmitter module emphasis is enabled, the receiver module
de-emphasis must be enabled and vice versa.
Remove DC Offset: Select this check box to enable DC offset removal in the DSP (digital signal
processor).
Use Sample Rate Converter: Select this check box to enable use of the asynchronous sample rate
converter (ASRC).
Input Sensitivity
dBu F/S: Move the slider to increase or decrease input sensitivity.
Sample Rate: Select an audio sample rate for the receiver: 32kHz, 44.1kHz, or 48kHz.

Submit: Click this button to apply the configuration values entered on this page.
Previous Card: Click this button to view configuration and status pages for the module on the
immediate left of this module.
Next Card: Click this button to view configuration and status pages for the module on the immediate
right of this module.
GatesAir, Inc. 4-77

Intraplex Products
Version 1.01
Figure 4-76. PT-353 Status Page

36.
Enable Module: Select this check box to place the module in service. If not selected, the module is
offline.
In Service: Whether the module is in service (green) or out of service gray).
Alarm: If there is an active alarm (red) or alert (yellow) on the module.
Config Error: Either a configuration error or normal condition. A configuration error occurs when the
time slot for the module is conflicting with another module in the system or when the number of
occupied time slots exceeds system availability.
Refresh: Shows if the automatic browser refresh is enabled for 1 minute (M), 5 seconds (5s), 10
seconds (10s), or 30 seconds (30s). Click a rate to change how frequently the browser refreshes this
page.
4-78 GatesAir, Inc.

Intraplex Products
Version 1.01

Timeslot: The 64 kbps time slots that make up a T1 or E1 circuit. The number of time slots varies for
each type of module. The time slot that you specify is for the starting time slot only. If the module
occupies more than one slot, you must make certain there are sufficient time slots available.
TDM Bus: The current bus side, either Bus A or Bus B.
Version
DSP: The version number of the digital signal processor (DSP) firmware that is currently installed.
Firmware: The version number of the Field Programmable Gate Array (FPGA) design that is currently
installed.
Transmitter Settings
Sample Rate: The current sample rate (in kHz) for the module.
Audio Mode: The current audio mode: Mono or Stereo.
Turn Test Tone On: (PT modules only) If this check box is selected, the built-in +8dB test tone is
enabled on the active channels.
Use J.17 Emphasis: If this check box is selected, emphasis is enabled on the outgoing signal in
accordance with ITU-T Recommendation J.17. If the transmitter module emphasis is enabled, the
receiver module de-emphasis must be enabled and vice versa.
Remove DC Offset: If this check box is selected, DC offset removal is enabled in the DSP (digital
signal processor).
Use Sample Rate Converter: If this check box is selected, use of the asynchronous sample rate
converter (ASRC) is enabled.
Audio Source
Digital input is in use: Audio source is configured for digital input.
Analog input is in use: Audio source is configured for analog input.
Transmit Status
Audio Activity: Either no audio activity or audio activity detected in the left channel if the signal is -
28 dBFS.
Audio Error: Either no audio errors detected or an AES/EBU error detected on the incoming signal.
Digital Transmit Level

Left and Right: Shows the current transmit level on the left and right channels.
Input Sensitivity: Shows the currently configured input sensitivity level in decibels relative to full
scale.
GatesAir, Inc. 4-79

Intraplex Products
Version 1.01
4.3.10.2 Sample Voice Module Configuration and Status
Figure 4-77. VF-25E Configuration Page

36.
Enable Module: Select this check box to place the module in service. If the check box is not selected,
the module is offline.

Active Channels: Select the audio channels (1, 2, 3, 4) to enable them on the module. Each active
channel occupies one DS0 time slot.
4-80 GatesAir, Inc.

Intraplex Products
Version 1.01
Signaling Configuration
Use Signaling: Select this check box to enable E-lead and M-lead circuit signaling. The audio channel
is still operational even if signaling is disabled.
Set C Bit to 1: Select this check box to force the C bit to be on for compatibility.
Loopbacks
Local: Click the On option to enable a local loopback. Click the Off option to disable the loopback. For
testing purposes, a loopback sends the input channel audio and signaling to its own local output
channel.
Channels 1-4: Click the On option to enable a loopback on the specific channel, or click the Off
option to disable the loopback. When a remote loopback is active (On), the local channel module
sends a loopback command to the far end channel module. The far end module continues to process
the incoming receive side data and sends it to the user as usual but also loops that data to the
transmit side of the module, processes it and returns the data to the originating module.

Figure 4-78. VF-25E Status Page
GatesAir, Inc. 4-81

Intraplex Products
Version 1.01
36.
Enable Module: Select this check box to place the module in service. If the check box is not selected,
the module is offline.
In Service: Whether the module is in service (green) or out of service gray).
Alarm: If there is an active alarm (red) or alert (yellow) on the module.
page.

Timeslot: The current setting for the starting time slot on the module.
Other Configuration
Local Loopback: If this check box is selected, local loopback is enabled.
Use Signaling: If this check box is selected, E-lead and M-lead circuit signaling is enabled.
Set C Bit to 1: If this check box is selected, the C bit is set to 1 (forced on).
Channel 1-4
Active: The channel activity (Green = channel is active or off-hook; gray = channel is idle or on-
hook).
M-Lead Busy: The M Lead activity (Green = M lead is active or unknown; gray = M lead is inactive or
not enabled.
E-Lead Busy: The E Lead activity (Green = E signaling lead is active or unknown; gray = E signaling
lead is inactive or not enabled).
Loopback: The channel is in local loop back mode (green), or there is no active loopback (gray).
4-82 GatesAir, Inc.

Intraplex Products
Version 1.01
4.3.10.3 Sample Data Module Configuration and Status
Figure 4-79. DS-64NC Configuration Page

36.
Enable Module: Select this check box to place the module in service. If this check box is not
selected, the module is offline.

Timeslot: Click the up or down arrow to change the number of time slots or type a different number.
TDM Bus: Click Bus A or Bus B on the drop-down list.
GatesAir, Inc. 4-83

Intraplex Products
Version 1.01
T1 (24 time slots): The use of a T1-based system.

E1 (31 time slots): The use of an E1- based system.
Skip Timeslot 16: Select this check box to set the module for CAS signaling in a 2MB (E1)
multiplexer.
Use Alternating Timeslots: Select this check box to use alternating time slots (1, 3, 5, 7, 9, and so
forth). If this check box is not selected, sequential time slots are used (1, 2, 3, 4, 5, and so forth).
Test Mode Configuration

Test Mode: Select the test mode to use: No test, Generate all ones, Generate PRNG (15-bit
pseudo random number generator), Generate 1:15 ones, Verify all ones, Verify PRNG, or Verify
1:15 ones.
Loopback Mode: Select the loopback mode: No Loopback, Equipment Loopback, Local (payload)
Loopback, or Remote Loopback.
Performance Register Selection: Select a performance register for inspection: Receive FIFO
Depth, Receive FIFO Underrun Count, Receive FIFO Overrun Count, Receive Bit Error Count,
Transmit FIFO Depth, Transmit FIFO Underrun Count, or Transmit FIFO Overrun Count.
Reset Performance Register: Select this check box to clear current register entries.
Circuit Configuration
Buffer Depth: The transmit-side and receive-side each have first-in, first-out (FIFO) buffers with a
depth of 12,000 bits. The starting depth of these buffers can be set either to 256 bits for normal
synchronous operation or to half of the full depth (6000 bits) for plesiochronous operation.
Transmit Mode: The mode for transmit side of the DS-64NC module: off at all times for receive only,
polling mode operating only when clear-to-send is asserted, at all times request-to-send/clear-to-send
handshake operational, or clear-to-send forced on at all times.
External Timing: Select this check box to enable the external timing output. The normal condition for
the external timing output is disabled (off).
Turn On Receiver: Select this check box to enable receive features for the module.
Data Rate Configuration

Timeslot Bit Rate: Click 64 kbps for the module to use 8 bits per time slot mode. Click 56 kbps for
the module to use 7 bits per time slot mode.
Data Rate: The total data rate that can be set to any rate from 8 kbps up to the maximum payload
capacity of the multiplexer, in increments of 8 kbps.
Timeslots: The desired starting time slot (1 to 24 in T1 system, 1 to 31 in E1 system).

4-84 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 4-80. DS-64NC Status Page

36.
Enable Module: If this check box is selected, the module has been placed in service. If the check box
is not selected, the module is offline.
Module Configured: If this check box is selected, the module is properly configured. If the check box
is not selected, the module is not configured.
In Service: This green light indicates the module is in service. If the light is off (appears gray), the
module is not in service.
GatesAir, Inc. 4-85

Intraplex Products
Version 1.01
Alarm: If there is an active major alarm (red) or minor alarm/alert (yellow) on the module.
Config Error: This red light indicates a configuration error. A configuration error occurs when the time
slot for the module is conflicting with another module in the system or when the number of occupied
time slots exceeds system availability. If the light is not on (appears gray), it indicates normal
operating condition.
page.

Skip Timeslot 16: If this check box is selected, CAS signaling is enabled.
Use Alternating Timeslots: If this check box is selected, alternating time slots (1, 3, 5, 7, 9, and so
forth) are used. If this check box is clear, sequential time slots are used (1, 2, 3, 4, 5, and so forth).
Test Mode Configuration

Test Mode: The test mode to use: No Test, Generate All Ones, Generate One and 15 Zeros, or
Generate PRNG (pseudo random number generator).
Performance Register: The selected performance register for inspection.
Loopback Mode: The loopback mode: No Loopback, Equipment Loopback, Local (payload)
Loopback, or Remote Loopback.
Performance Register Value: The value of the performance register.
Circuit Configuration
Data Rate: The total data rate that may be set to any rate from 8 kbps up to the maximum payload
capacity of the multiplexer, in increments of 8 kbps.
Transmit Mode: The mode for transmit side of the DS-64NC module: off at all times for receive only,
polling mode operating only when clear-to-send is asserted, at all times request-to-send/clear-to-send
handshake operational, clear-to-send forced on at all times.
Buffers: The amount of bits for the starting buffer depth.
Turn On Receiver: If this check box is selected, receive features are enabled.
Timeslots: The desired starting time slot: 1 to 24 in T1 system or 1 to 31 in E1 system.
Bit Rate: Whether the module is using 8 bits per time slot mode (64 kbps) or 7 bits per time slot
mode (56 kbps).
External Timing: If this check box is selected, the external timing output is enabled. The normal
condition for the external timing output is off.
Card Status
Transmit Activity: This green light indicates there is data activity on the input to the module.
Receive Activity: This green light indicates there is activity on the channel for this module.
Remote Loopback: This green light indicates the loopback from the far end has been initiated.
4-86 GatesAir, Inc.

Intraplex Products
Version 1.01
PLL Status
Transmit side PLL locked: This green light indicates a transmit Phase-Locked Loop error is detected.
Receive side PLL locked: This green light indicates a receive Phase-Locked Loop error is detected.
Shelf reference PLL locked: This green light indicates a shelf reference Phase-Locked Loop error is
detected.
Circuit Errors
Transmit clock output error: This red light indicates a transmit clock output error is detected.
Receive clock output error: This red light indicates a receive clock output error is detected.
Receive data output error: This red light indicates an output error is detected.
Handshake signal error: This red light indicates a handshaking error is detected.
GatesAir, Inc. 4-87

Intraplex Products
No header here
GatesAir, Inc. 4-88

Intraplex Products
No header here
Section 5 – Testing & Troubleshooting
5.1 Testing
You can use these diagnostics tests to check your NetXpress LX/CM-30 operation:
● General status test – Assure the system power is operational and there are no modules
registering major alarms.
● Ping test – Send echo requests to each multiplexer to test communication.
● Multiplexer-to-multiplexer communication test – Assure you can create and activate streams
between NetXpress LX multiplexers and the streams send packets error-free.
● CM-30 alarm test – Assure there are no current alarms or alarm history.
5.1.1 General Status Test

You can start with a very basic test: check module status by looking at indicator lights. You can check
indicator lights on either the physical chassis or through the Web interface.
5.1.1.1 Physical Indicator Lights

When the system is powered up, the POWER and NORMAL green indicator lights on the front panel
should be on, and the ALERT and ALARM lights should be off (Figure 5-1).
Figure 5-1. NetXpress LX 3RU Multiplexer – Front View, Closed

If the POWER light is off, check that power has been wired to the system. If the unit is AC-powered,
the AC line cord should be plugged in. If the unit is DC-powered, the external power fuse should be
inserted.
If the NORMAL light is off and either the ALERT (minor alarm) light or ALARM (major alarm) light is on,
check the Faults | Current Alarms page on the Web interface. If you cannot access the system,
check the CM-30 module WAN and LAN indicator lights for network connectivity.
5.1.1.2 Web Interface Indicator Lights

After you access the Web interface (Section 4.2.1), you can check system status information on the
NetXpress LX Home page (Figure 5-2).
GatesAir, Inc. 5-1

Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual 5 – Testing & Troubleshooting
Version 1.01
Figure 5-2. NetXpress LX Web Interface Home Page

The Home page shows the power module, CM-30 common module, and all channel modules installed
in the multiplexer, including each module’s indicator lights. The power module’s Normal green
indicator light should be on, and its Major (red) and Minor (yellow) indicator lights should be off. The
CM-30 module’s WAN, Timing, and Active green indicator lights should be on. The LAN indicator
light is green if there is a cable connection. If a loopback is configured, the LAN indicator light is
yellow, the multiplexer Minor Alert yellow light is on, and the Normal green light is off (appears
gray). The green Service light for each channel module should be on, and the green Remote light
should be on to allow for remote configuration.
Also, the shade of each channel module panel is white when in normal operation, yellow when
reporting an Alert (Minor alarm), or red when reporting an Alarm (Major alarm).
5.1.2 CM-30 Alarm Test

You need to clear any alarms and alarm history before conducting the next tests (Sections 5.1.3 and
5.1.4). Then you can check any current alarms and alarm history information. Perform these steps:
1. On the navigation pane, point to Faults and click Current Alarms (Figure 5-3). Alarms might
appear upon initial power-up but should self-clear on a properly configured system.
5-2 GatesAir, Inc.

Intraplex Products
5 – Testing & Troubleshooting NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
Figure 5-3. Faults | Current Alarms Table

2. Click to clear these alarms from the table.
3. Point to Faults and click Current Alarms (Figure 5-4). As with the Current Alarms table, the
Alarm History table normally displays alarms after initial power-up.
Figure 5-4. Faults | Alarm History Log

4. Click to clear these alarms from the log.
5. Complete the tests in Sections 5.1.3 and 5.1.4.
6. Keep streams up (Section 5.1.4) for at least 10 minutes.
7. Check the Current Alarms table and Alarm History log. There should be no alarms.
GatesAir, Inc. 5-3

Intraplex Products
Version 1.01
5.1.3 Ping Test

Both this test and the stream test in Section 5.1.4 verify that your two NetXpress LX multiplexers are
communicating with each other. Use the Ping utility tool (Utilities | Ping) to send echo requests to
and receive responses from the multiplexers to verify communication between the two systems
(Figure 5-5).
Figure 5-5. Ping Utility

Perform these steps:
1. From the Web interface of the first NetXpress LX multiplexer (System A), type the Host IP
Address of the other NetXpress LX multiplexer (System B).
2. Click Send Ping.
3. Note the PING Result, which should indicate a response from System B.
4. Repeat the previous three steps to send an echo request from System B to System A.
5.1.4 Stream Test

To assure your NetXpress LX multiplexers are sending and receiving data without issues, perform the
steps in Section 4.2.3.5 – Stream Creation to create and activate streams. Configure the streams to
run at a high packet rate to assure solid performance at high demand. Remember to configure system
timing (Section 4.2.3.6) before activating any streams.
Follow this process:
1. Create a transmission stream on one NetXpress LX multiplexer (System A).
2. Activate the new stream.
3. On the Stream Statistics table (Performance | Streams) of the Web interface (Figure 5-6),
verify that the System A stream is
• Operating (Op State=Up)
• Sending packets (Tx Packet Count)
5-4 GatesAir, Inc.

Intraplex Products
Version 1.01
Figure 5-6. Performance | Streams Statistics Table

4. Create a receive stream on the other NetXpress LX multiplexer (System B).
5. Activate the new stream.
6. On the Stream Statistics table, verify that
• The System B stream is operating (Op State = Up).
• Stream packets are being counted (Rx Packet Count).
• There are no packets dropped (Rx Packet Statistics Lost and Under = 0).
• There is no excessive jitter; that is, the Rx Queue Cur and Avg should equal about half the
Jitter Buffer Value you configured for the stream. It is normal to vary +/-1 from the halfway
point. However, if either the current or average jitter statistic is near 64 or 0, it would indicate
excessive jitter.
Note: It is best to create and activate a stream in the transmitter before creating and activating
streams in the receiver. If you activate the receive stream before first activating the transmit
stream, an alarm occurs.
If the receive stream is activated before the transmit stream, clear the alarm (Section 5.1.2)
and then follow the stream test process.
If you have problems creating or activating the stream, try the troubleshooting guidelines in Section
5.2.2.4. If there are dropped packets, use these guidelines to troubleshoot the difficulty:
● Make sure cable connections for both multiplexers are secure.
● Confirm that the network switches are properly configured: 100Base-T, full duplex is
recommended.
● Confirm that the two systems are using proper timing modes.
● Confirm that the network is not oversubscribed by the NetXpress LX system and other services.
GatesAir, Inc. 5-5

Intraplex Products
Version 1.01
5.2 Troubleshooting
Use these guidelines to troubleshoot various aspects of NetXpress LX/CM-30 operation.
5.2.1 Channel Module Addition

Before adding a channel module to your shelf, you might want to switch the module to REMOTE
control so that you can use the NetXpress LX/CM-30 Web interface to configure the module’s settings.
Insert the module adapter first, and then insert the channel module. All Intraplex channel modules can
be hot-inserted; the modules can be installed while the shelf is operating.
Warning! It is possible to insert the channel module improperly, causing damage to the module
being installed and other installed modules. When inserting the module, make sure the
white ejector tab is next to the floor of the chassis on a 3RU shelf or to the right of the
chassis on a 1RU shelf.
1. Insert the module adapter in the slot on the back panel behind the one you have selected for the
new channel module.
2. Insert the channel module into the front of the shelf. Once it is inserted, the NetXpress LX/CM-30
system detects the module automatically.
3. On the NetXpress LX Home page, click Open on the displayed module to review and, if the
module is set to REMOTE, to adjust its settings. (Section 4.3.10 – Configure Individual Modules
(TDM Channel Modules) gives additional information.)
5.2.2 Web Browser Interface
5.2.2.1 Page Refresh Problems

If you submit changes to a page and the fields remain unaltered, try clicking the Refresh button in
your browser. If none of the fields change, clear the cache in Internet Explorer (Go to Tools |
Internet Options and, in IE 2007, click Delete at Browsing history or, in earlier versions of IE,
click the Clear History button.) Then, press the Refresh button on the specific NetXpress LX/CM-30
Web interface page.
You can also change the page settings for refresh times in Internet Explorer. In IE 2007, perform
these steps:
1. Go to Tools | Internet Options.
2. At Browsing history on the General tab, click Settings.
3. In IE 2007, at Temporary Internet Files, click the Every time I visit the webpage option.
4. In earlier versions of IE, at Check for newer versions of stored pages, click the Every visit to
the page option.
Note: If you are using a non-IE Web browser, your browser’s Help should give instructions on
changing the browser page settings.
5.2.2.2 Route Creation Failures

If you cannot create a route, there is a good chance that the interface does not have an IP address
and correct mask within the network to find the gateway. The new entry must be within the scope of
the interface that is using existing routes. Check the destination IP address and the mask for the route
you are creating. Confirm that the addresses are valid for the network and that it is reachable on the
interface listed on the route. Section 4.3.4.2 – Forwarding Table gives additional information.
5-6 GatesAir, Inc.

Intraplex Products
Version 1.01
5.2.2.3 Absence of Traps

If you are not getting any traps on your trap receiver (SNMP Event Host), make sure the correct IP
address and community name for the trap receiver is configured in the NetXpress LX/CM-30 Web
interface. Section 4.2.3.7 – SNMP Community and Section 4.3.4.4 – SNMP Configuration give
additional information. Also confirm that the Host is routable from the NetXpress LX system using the
intended interface.
5.2.2.4 Stream Creation Troubleshooting
Creation Errors
If you receive an error message when trying to create and activate a stream, try these guidelines
to investigate the problem:
● Verify that the TDM bus and time slots are not already being used by an in-service stream.
● Check the destination IP address and be sure that it is a valid unicast or multicast address.
Activation Failure
If you successfully created a stream but it does not come up, try these guidelines to investigate
the problem:
● Verify that you have placed the stream in-service at the source and the destination.
● Check that the stream bandwidth and the DP port numbers match at the source and
destination.
● Access the Ethernet Interface Statistics – WAN page (Performance | Ethernet
Interfaces | WAN Interface) to check if the WAN interface is down.
● Make sure that there is a valid route to the destination.
● Check the destination NetXpress LX multiplexer to make sure that it is configured properly and
that its stream has an operational state of “In Service.”
● Access the PING Utility screen (Utilities | Ping) and ping the destination to make sure it is
reachable by the WAN interface.
No Audio
If your stream is up but you do not hear any audio, try these guidelines to investigate the
problem:
● Open the configuration screen for the channel module, and make sure that channel module is
configured to use the bus and time slots allocated to the stream. Also, verify that it is in
service.
● Check the remote side channel module configuration and service state.
● Look at the TDM Bus Information page (System Cfg | TDM Bus) on the NetXpress LX/CM-
30 Web interface for the transmitter. The time slots assigned to the transmitter should be
green if it is placing audio data on the bus.
If your stream is up and you hear audio, but the audio quality is not good, try these guidelines to
investigate the problem:
● Verify the channel module configurations on both ends.
● Make sure that timing is properly configured.
● Look at the stream statistics to determine if you are losing packets. Lost packets affect the
audio quality.
● Try increasing the packetization ratio. Low ratios mean high packet rates that could
overwhelm old technology switches and routers.
● Try increasing the size of the jitter buffer if received packets are late. Your network may have
more jitter than can be compensated for by the current size of the jitter buffer.
GatesAir, Inc. 5-7

Intraplex Products
Version 1.01
If this Troubleshooting section does not address your specific problem or if you have tried these
guidelines and still have difficulties, call or send non-emergency email to GatesAir Customer Support:
5-8 GatesAir, Inc.

Intraplex Products
No header here
Section 6 – Specifications
6.1 Detailed Specifications

These specifications are subject to change without notice.
6.1.1 NetXpress LX IP Multiplexer
Shelf Configurations LX-100: 1RU shelf with 5 card slots for audio, voice, and data
modules
LX-300: 3RU shelf with 17 card slots for audio, voice, and
data modules
Each shelf comprises one chassis, one power supply, one
CM-30 IP interface module, and one MA-230 module adapter.
The LX-100 contains a single AC power supply. The LX-300
contains one AC or one DC supply and can be equipped with a
second power supply for hot-standby redundancy.
Audio, voice, and data modules optional.
General
Module Compatibility Accepts Intraplex plug-in audio, voice, and data modules. See
individual module specifications for details and applications.
Contact Closures Two contact closures in each direction

Input Two opto-isolated inputs
Can be controlled by a CMOS, an open collector, or LS TTL
logic
Output Two normally open SPST relay outputs
Maximum current of 120 mA
Maximum voltage of 350 VDC
Closed resistance of 23 ohms typical
Ethernet Data Rate 10/100 Base-T (10 or 100 Mb/s)

Full duplex
Auto-negotiation with network
Network Connections Port 1 — WAN: RJ-45

Network Interface
Port 2 — LAN: RJ-45
Network Protocols IP, TCP, UDP, RTP, DHCP, DNS, HTTP (on port 80), FTP (on
Supported port 21), Telnet, NTP, SNMP v2c (SNMP v1/SNMP v2 –
requests on port 161 and traps on port 162), RTCP, ARP,
ICMP, IGMP v2
Streaming Encapsulation in compliance with RFC5086 (CESoPSN)
Timing Internal
External: RS-422 clock input
Adaptive to incoming program stream
Timing out: RS-422 clock output
GatesAir, Inc. 6-1

Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual 6 - Specifications
Version 1.01
Forward Error Correction High, low, off

User-adjustable
In accordance with RFC2733 framework
Packet Optimization Packet size/rate, allows control over the inherent tradeoff
Stream Parameters
between overhead and delay

(per stream)
Jitter buffer depth to 128 packets, provides compensation in

excess of one second of network jitter
User-adjustable
Circuit Connection Up to 32 streams/connections

Point-to-point unidirectional
Point-to-point bidirectional
Point-to-point multipoint unidirectional multicast per IGMP v2
Quality of Service IPv4 Type of Service (ToS) tagging

Differentiated Service (DiffServ)
LED Indicators Power, Normal, Alert, Alarm

Diagnostics
Status and
Network Performance Packet loss, packets received, packets sent, packets

Statistics (per stream) dropped, packet count and delay variation
Loopbacks Received stream loopback, Equipment loopback

Management
Remote
Web browser user interface

SNMP network management interface
Power Requirement Universal AC 90-240 V AC, 50/60 Hz, 48 V DC, 24 V DC

LX-300 only: Optional 48 V DC, 24 V DC
Mechanical/Environmental
Power Supply LX-100: Single 30 W AC

LX-300: Single or optional dual 60 W AC, 95 W AC, 50 W
48 V DC, 50 W 24 V DC
Power Consumption Depends on number and type of channel modules installed:

LX-100: Less than 15 W typical
LX-300: Less than 40 W typical
Ambient Temperature 32º F – 122º F (0º – 50º C) Operating

Range
Humidity 10% to 90% non-condensing
6-2 GatesAir, Inc.

Intraplex Products
6 – Specifications NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
Height LX-100: 1RU, 1.75 in. (4.45 cm)

LX-300: 3RU, 5.25 in. (13.4 cm)
Width 19" (48.3 cm.)

Physical
Depth 14.25 in. (36.2 cm)
Shipping Weight Depends on number and type of channel modules installed:

LX-100: Less than 20 lbs (7.5 kg) typical
LX-300: Less than 25 lbs (11.4 kg) typical
Rack 19" EIA-rack mountable
CE Compliant
Compliance
Regulatory
FCC Part 15 Class A

UL 1950
RoHS Compliant
6.1.2 CM-30 IP Interface Module
Ethernet Data Rate 10/100 Base-T (10 or 100 Mb/s)

Full duplex
Auto-negotiation with network
Network Connections Port 1 — LAN: RJ-45

LED indicator next to WAN – 100 Mb Link/Activity
LED indicator next to IN – 10 Mb Link/Activity
Port 2 — WAN: RJ-45
Corner LED indicator – 100 Mb Link/Activity
Network Interface
Inside LED indicator – 10 Mb Link/Activity
Circuit Connection Up to 32 streams/connections

Point-to-point unidirectional
Point-to-point bidirectional
Point-to-point multipoint unidirectional multicast per IGMP v2
Network Protocols IP, TCP, UDP, RTP, DHCP, DNS, HTTP (on port 80), FTP (on
Supported port 21), Telnet, NTP, SNMP v2c (SNMP v1/SNMP v2 – requests
on port 161 and traps on port 162), RTCP, ARP, ICMP, IGMP v2
Streaming Encapsulation in compliance with RFC5086 (CESoPSN)
Timing Internal
External: RS-422 clock input
Adaptive to incoming program stream
Timing out: RS-422 clock output
GatesAir, Inc. 6-3

Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual 6 - Specifications
Version 1.01
Forward Error Correction High, low, off

User-adjustable
In accordance with RFC2733 framework
Packet Optimization Packet size/rate, allows control over the inherent tradeoff
between overhead and delay
Jitter buffer depth to 128 packets, provides compensation in
excess of one second of network jitter
Status and Diagnostics
Stream Parameters
User-adjustable
(per stream)
Quality of Service IPv4 Type of Service (ToS) tagging

Differentiated Service (DiffServ)
LED Indicators WAN: 100 Mb Link and Activity

10 Mb Link and Activity
Full-Duplex
LAN: 100 Mb Link and Activity
10 Mb Link and Activity
Full-Duplex
Loopback
Timing
Active
Status
Network Performance Packet loss, packets received, packets sent, packets dropped,
Status and
Diagnosis
Statistics (per stream) packet count and delay variation
Loopbacks Received stream loopback

Equipment loopback
Web browser user interface

Remote Management
SNMP network management interface
CE Compliant
FCC Part 15 Class A
Regulatory Compliance
UL 1950
RoHS Compliant
Can be used in place of a T1 or E1 common module

Module Replacement (CM-3, CM-5, CM-5RB, CM-6, CM-7, CM-7RB) in an existing
Intraplex T1/E1 multiplexer to convert the system to IP.
CE
FCC, Part 15, Class A
Compliance
UL 1950
RoHS
6-4 GatesAir, Inc.

Intraplex Products
6 – Specifications NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
6.2 Notice of FCC Compliance

This equipment has been tested and found to comply with the limits for a Class A digital device
pursuant to Part 15 of FCC Rules. These limits are designed to provide reasonable protection against
harmful interference when this equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy and if not installed and used in accordance
with this manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference in which case, the user will be
required to correct the interference at his/her own expense.
Warning! This is a Class A product. In a domestic environment this product may cause radio
interference, in which case the user may be required to take adequate measures.
GatesAir, Inc. 6-5

Intraplex Products
No header here
6-6 GatesAir, Inc.

Intraplex Products
No header here
Appendix A – T1/E1-to-NetXpress LX
Multiplexer Conversion
This appendix covers the CM-30 package installation, configuration, and troubleshooting for converting
your T1 or E1 Intraplex multiplexers into NetXpress LX multiplexers. This discussion assumes that you
are working with a 3-rack unit (3RU) 19-inch multiplexer shelf.
To minimize system downtime, you may install your CM-30 modules while your Intraplex multiplexers
are powered up (power is on). The CM-30 IP interface module begins “learning” the channel module
information from the existing common module while still operating in T1 or E1 mode, prior to live
operation over the IP network.
Be aware that Alert and Alarm conditions appear on the multiplexer during the update process. If you
have an alarm or remote control system wired to the external relay contacts of the multiplexer, you
might wish to disable the alarm system before proceeding with the installation.
A.1 Installation Preparation
A.1.1 Equipment Unpacking & Inspection

Upon receiving your CM-30 package, complete these tasks:
1. Inspect all shipping containers for damage. If you observe damage, notify the shipping service as
soon as possible.
2. Unpack all equipment from containers.
3. Inspect equipment for damage.
4. Verify that the CM-30 package is equipped as expected, confirming items from the packing list
(Bill of Materials):
• Two (2) CM-30 NetXpress LX IP common modules in good condition
• Two (2) MA-230 NetXpress LX IP module adapters in good condition
• Eight (8) 4-40 Philips screws for securing the MA-230 module adapter
If you have questions regarding possible equipment damage or shipping errors, contact Networking
Customer Service:
Warning! Follow your company’s rules regarding AC powered equipment installation. If there is a
conflict between any procedure in this document and your company’s safety rules, your
company’s safety rules must take priority.
A.1.2 Card Slot Selection

You may install the CM-30 module and MA-230 module adapter into any free card slot within the
multiplexer. However, before installation, consider that some module adapters occupy the width of
two modules on the back panel. Make certain to install the CM-30 module and MA-230 module adapter
into a card slot that is joined to the controller and channel modules that you wish to access.
GatesAir, Inc. A-1

Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual Appendix A – NetXpress LX Conversion
Version 1.01
Consider these guidelines:

● In a TDM-163, TDM-165, STL-163, STL-165, ACS-163, ACS-165, TDM-263, TDM-265, ACS-263,
ACS-265, ADL-263, or ADL-265 multiplexer, any of the 18 available card slots provides access to
the modules located in the remaining card slots.
● A TDM-166, STL-166, TDM-266, ACS-266, or ADL-266 multiplexer system is divided into two
sections; card slots 1 through 9 are in one section, and card slots 10 through 18 are in the other
section.
● In a DCS-9530, DCS-9530E, DCS-9560, or DCS-9560E unit, the multiplexer section only extends
from card slot 1 through card slot 12.
These two components need to be installed into matching slots so that they meet together at the
midplane. Therefore, install the MA-230 module adapter on the back panel of the multiplexer chassis
so that it connects with the CM-30 IP interface module at the midplane (Figure A-1).
Midplane
CM-30 SW1
Step 2 Step 1
MA-230
S2
Figure A-1. CM-30 Module and MA-230 Midplane Insertion
A.2 IP Multiplexer Conversion

There are six basic processes in this conversion:
1. CM-30 and MA-230 installation in the first multiplexer
2. Network configuration of the CM-30 module in the first multiplexer
3. CM-30 and MA-230 installation in the second multiplexer
4. Network configuration of the CM-30 module in the second multiplexer
5. Configuration of the two CM-30 modules to work together
6. Removal of the original common modules from the multiplexers
You must perform these processes in order and in the manner specified in this appendix to
successfully convert your Intraplex multiplexers to NetXpress LX IP multiplexers. Therefore, read all of
these processes, procedures, and guidelines before proceeding to insert the CM-30 modules and the
MA-230 module adapters into your T1/E1 multiplexer shelves.
The next sections cover each of these procedures.
A.2.1 CM-30 & MA-230 Installation into the First Multiplexer

When installing a CM-30 module and MA-230 module adapter into a multiplexer, install the module
adapter first and then install the module. The next sections give installation details.
A.2.1.1 Install the First MA-230 Module Adapter

You can install the MA-230 module adapter while the multiplexer is still in live service. Proceed with
caution when installing the adapter into a live system to prevent service interruption and damage to
components. Perform these steps:
A-2 GatesAir, Inc.

Intraplex Products
Appendix A – NetXpress LX Conversion NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
1. Switch bank SW1 sets the input impedance for the timing input connections. These switches
should be set to ON for most applications. Confirm that these switches are set properly on SW1 on
the MA-230 adapter. (Section 3.2.2.3 and Table 3-4 describe the switch functions.)
2. At the desired location, remove a single-width aluminum blanking plate from the back panel of the
multiplexer shelf by loosening the two retaining screws associated with the plate. The MA-230
adapter only requires one panel width, but you may find that you need to remove a double- or
triple-wide panel from the back panel to locate the desired numbered slot. You need to remove
four Phillips screws in order to free a double- or triple-wide panel.
3. While keeping the name of the MA-230 panel oriented toward the top of the chassis, align the
edges of the module adapter with the module alignment grooves that are provided on the top and
bottom walls of the chassis.
4. Slide the MA-230 module adapter from the rear of the shelf toward its mating connector on the
midplane until the aluminum plate is flush with the top and bottom rails of the back panel.
5. Secure the MA-230 adapter securely to the back panel with the two Phillips screws that are
provided.
6. Install aluminum plates in any remaining blank slots, or reposition the set of aluminum blanking
plates as needed, to completely secure the back panel area.
A.2.1.2 Install the First CM-30 IP Interface Module

You can install the CM-30 module while the multiplexer is still in live service. Proceed with caution
when installing into a live system to prevent service interruption and damage to components.
Before installing the module in the multiplexer, take note of any pre-existing alerts or alarm conditions
being reported by the installed T1/E1 common module. This discussion assumes that the multiplexer is
currently showing a green NORMAL condition on the power supply and the installed T1/E1 common
module controller.
Observe anti-static procedures while handling the CM-30 module outside of its protective packaging.
The packaging should be normalized with the multiplexer prior to opening or handling the bare
module, and the module should not be transported even across the room when not wrapped in anti-
static packaging. If you have a wrist strap, clip it to the multiplexer chassis or the rack into which the
multiplexer is installed.
To install the CM-30 module, perform these steps:
1. Switch bank S2 is used to reset the module to factory defaults. These switches should be set to
OFF for most applications. However, for the very first installation of a new module, you can turn
them ON to initialize the module. Confirm that the two switches on S2 are set properly. (Table 3-2
– CM-30 Switch Settings in Section 3.2.2.2 gives the switch functions.)
2. With the CM-30 module resting on its anti-static bag or other static-safe material, its white tab
turned toward you, and the gold fingers away from you, grasp the module by its edges only and
tilt the module clockwise until the solder side is to your left and the module’s components are to
your right.
Note: If you are not wearing a wrist strap, your free hand should maintain a ground connection
with the multiplexer chassis to reduce any static potential.
3. While keeping the white ejector tab oriented toward the floor of the chassis, align the edges of the
module with the slot alignment rails that are provided along the top and bottom of the chassis,
and slide the module in so that it is now supported by the alignment rails.
4. Fully install the module into its mating connector on the midplane by pressing securely on the
white ejector handle.
GatesAir, Inc. A-3

Intraplex Products
Version 1.01
A.2.2 First CM-30 IP Interface Module Configuration

When the CM-30 module initially receives power, its STATUS indicator light is red, which might also
trigger the Alarm condition on the shelf power supply and any devices that are connected to the Alarm
output contacts on the rear panel. This condition should not impede any T1/E1 services on the system.
After approximately 40 seconds, the ACTV and STATUS indicator lights blink green to show that the
CM-30 module is now in Learning mode and that your T1/E1 controller module is still operating the
multiplexer. To further configure the CM-30 module, perform these steps:
1. Connect and log on to the NetXpress LX (CM-30) Web interface using the instructions in Section
4.2.1 – Connect and Log On to Access NetXpress LX Home Page.
2. If the system power and alarm indicator lights are cycling a pattern of Green, Yellow, Red, Yellow
(showing Normal, Alarm, Alert, Alarm), the configured system mode of the CM-30 bus mode does
not match the detected system. The CM-30 module is currently set to E1 mode but has sensed
that it is installed into a T1 multiplexer, or it is set to T1 mode but has sensed that it is installed
into an E1 multiplexer. Use the instructions in Section 4.3.3.3 – TDM Bus Information to configure
the system mode. The system bus mode does not change until after the CM-30 module resets.
3. Perform an initial network configuration of the system to define the IP address, subnet mask, and
any required forwarding. Note that, when you click Submit to change the network IP address for
the interface by which you are currently connected, you do not receive any further responses from
the CM-30 module.
4. Turn OFF the two switches on the CM-30 module so that it retains your new network settings on
the next reset or power cycle. Alternatively, you may eject the CM-30 module from its position in
the multiplexer, turn off the switches, and then re-insert the module. The module should return to
Learning mode, this time with the stored IP address.
5. Confirm that you are able to reconnect to the CM-30 module using the newly assigned IP address.
A.2.3 CM-30 & MA-230 Installation into the Second Multiplexer
A.2.3.1 Install the Second MA-230 Module Adapter

Use the same guidelines described in Section A.1.2 – Card Slot Selection to choose a location for the
MA-230 adapter at the second multiplexer. Perform the steps in Section A.2.1.1 – Install the First MA-
230 Module Adapter to install and secure this second module adapter into the second multiplexer.
A.2.3.2 Install the Second CM-30 Module

Use the guidelines and steps in Section A.2.1.2 – Install the First CM-30 IP Interface Module to install
the second CM-30 module into the second multiplexer.
A.2.4 Second CM-30 IP Interface Module Configuration

Use the guidelines and steps in Section A.2.2 – First CM-30 IP Interface Module Configuration to
configure this second CM-30 module in the second multiplexer and prepare the module to
communicate on your network. You should now be able to communicate with both CM-30 modules
using your own assigned IP addresses instead of using the factory default IP addresses.
A.2.5 Configuration of Both CM-30 Modules to Work Together

Configuring the two CM-30 modules to take over operation of the T1/E1 multiplexers and thus convert
the multiplexers to IP systems involves these processes:
1. Confirm that the channel modules installed in the multiplexer match the channel modules that the
CM-30 module registers.
A-4 GatesAir, Inc.

Intraplex Products
Appendix A – NetXpress LX Conversion NetXpress LX & CM-30 Installation & Operation Manual
Version 1.01
2. Map the installed channel modules and services across the IP network.
3. Establish a synchronous operation.
4. Confirm the network operations.
A.2.5.1 Confirm the Installed Channel Modules Match the CM-30 Register
Access the Home page of each NetXpress LX/CM-30 Web interface to confirm the CM-30 module
registers the presence of the installed channel modules. The CM-30 module registers any installed
channel modules set to Remote Control mode and previously configured for operation by the T1/E1
controller. Once the T1/E1 controller releases control of the multiplexer shelf to the CM-30 module,
you can use the CM-30 module to control and configure the channel modules.
While the CM-30 module is in Learning mode, it does not register installed channel modules that are
manually configured and set to Local Control mode, but these modules do appear on the Home page
once the CM-30 module becomes the primary controller. Manually configured modules can still use the
TDM bus for sending and receiving data. When the REMOTE switch of a channel module is set to the
right (up, or away from the circuit board), the module is in Local Control mode. To permit the CM-30
module to start learning about these installed modules as well, enable the Remote Control mode on
each channel module by carefully setting the module’s REMOTE switch to the left (down, or toward the
circuit board).
If there is an additional module showing on the CM-30 interface Home page that is not actually
present in your multiplexer, that module is stored in the CM-30 system’s memory. To clear out the
memory history and restart the scan, perform these steps:
1. On the NetXpress LX (CM-30) Home page, go to System Cfg | Configuration Backup.
2. On the Configuration Files Backup/Restore table, click on the /RFA/cfg/scbdata.cfg
row to delete the scbdata.cfg file. The delete confirmation dialog box appears.
3. Click OK to confirm deleting the configuration file.
4. Click Reset the System. The system reset confirmation dialog box appears.
5. Click OK to confirm resetting the system.
If the modules appearing on the Home page now match the modules installed in your multiplexer, the
CM-30 module has completed the learning process.
A.2.5.2 Map the Installed Services

The data from channel modules in each multiplexer is mapped across the Ethernet network to
matching channel modules in another multiplexer using data streams. Each stream entry defines the
IP packet size, the destination IP address, the TDM bus and the range of TDM time slots for a channel
module or group of adjacent modules.
On the Web interface, add entries to the Streams table to send and receive the TDM data for each of
your installed channel modules (Section 4.3.5 – Configure Streams). Create streams with low latency
and signaling support to use with the telephony (VF-) modules and streams without signaling to use
with transporting data (DA- and DS-) modules. You can review the TDM bus selection, the starting
time slot, and other settings for each visible module on the Home page using the Open button on
each module panel. For each transmit (or bidirectional) stream that you create on one multiplexer,
you need to create an identical receive (or bidirectional) stream in the other multiplexer.
A.2.5.3 Establish a Synchronous Operation

For the two CM-30 modules need to operate synchronously across the network, set them both to use
timing derived from the same clock source. For a pair of point-to-point systems, the timing selection
should likely match the former T1/E1 operation.
GatesAir, Inc. A-5

Intraplex Products
Version 1.01
If one of the T1/E1 controllers had been set to use Internal or External timing, the CM-30 module for
that same multiplexer should probably be set to use that same timing method. Where LOOP timing
was used, the CM-30 module instead uses STREAM timing across the IP network.
Select the timing sources for the CM-30 module before you activate the streams. Section 2.7 –
System Timing; Section 4.2.3.6 – Timing Configuration; and Section 4.3.3.5 – System Timing give
more information.
A.2.5.4 Confirm the Network Operations

Activate each data stream. If the settings for a receive stream match the parameters of the arriving
data, the stream operational state remains UP and continues to appear green.
If the timing source for each CM-30 module is present and all clocks are derived from the same
source, the system should remain stable and prevent jitter buffer underflow and overflow.
On the NetXpress LX (CM-30) Home page, go to Performance | Streams to access the Streams
Statistics table and determine how well the streams are delivering the data packets across the
network. Section 2.2.9 – Stream Statistics and Section 4.3.6 – Check Multiplexer Performance give
more information.
A.2.6 Removal of the Original Common Modules

Once you have created and activated data streams to link each of the installed channel modules, and
the steams indicate no lost or late data packets, you can remove the T1/E1 controllers from the
shelves. There is no Disable control available on the T1/E1 common modules. Therefore, you
deactivate them by simply removing each one from the multiplexer using the white ejector tabs.
A-6 GatesAir, Inc.

Intraplex Products
No header here
GatesAir, Inc. A-7

Intraplex Products

Harrisbroadcast NetXpress LX Manual

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Harrisbroadcast NetXpress LX Manual

Загружено:

Авторское право:

Доступные форматы

Installation and Operation Manual

For NetXpress LX Version 1.03

Customer Service Contact Information

Europe, Middle East and Africa:

1.01* 6/21/12 Corrected AC power wattage in Power section. LD

1 9/20/10 Developed manual. LD

Section 2 – Functional Design........................................................ 2-1

2.7 System Timing............................................................................... 2-12

Section 3 – Installation & Wiring ................................................... 3-1

Section 4 – Configuration & Operation .......................................... 4-1

Section 5 – Testing & Troubleshooting ......................................... 5-1

Section 6 – Specifications .............................................................. 6-1

Appendix A – T1/E1-to-NetXpress LX Multiplexer Conversion ....... A-1

GatesAir, Inc. iii

Figure 4-26. Configure Output Contact Dialog Box ..................................................... 4-24

Figure 4-79. DS-64NC Configuration Page ................................................................. 4-83

1.1 Key Features

1.2 Manual Use

GatesAir, Inc. 1-1

1.3 Manual Scope

1.4.1 Main Equipment Shelf

Figure 1-1. NetXpress LX-300 Front Panel with Cover

Figure 1-2. NetXpress LX-100 Front Panel with Cover

1-2 GatesAir, Inc.

1.4.2 CM-30 IP Interface Module

GatesAir, Inc. 1-3

Figure 1-3. CM-30 IP Interface Module

1-4 GatesAir, Inc.

1.4.3 MA-230 Module Adapter

1.4.4 Other Modules and Module Adapters

1.4.5 Indicator Lights

1.5 Web Browser User Interface

GatesAir, Inc. 1-5

Section 2 – Functional Design

2.1 Network Concepts and Considerations

2.1.1 MTU throughout the Network

2.1.2 DHCP Use

2.1.3 Routing Table Construction

GatesAir, Inc. 2-1

2.1.4 WAN Port Auto-negotiation

2.1.5 ICMP Support

2.1.6 IGMP Multicast

2-2 GatesAir, Inc.

2.2.1 Stream Types

2.2.1.1 Unidirectional versus Bidirectional

2.2.1.2 Unicast versus Multicast

2.2.1.3 Voice Streams versus Data Streams

GatesAir, Inc. 2-3

2.2.2 Stream Addressing

2.2.3 Multicast Group Addressing

2-4 GatesAir, Inc.

Figure 2-1. Carrier Multicast Backbone Example

2.2.5 Echo Cancellation

GatesAir, Inc. 2-5

2.2.6 Packetization and Overhead

2.2.7 Packet Jitter Compensation

2.2.8 Packet/Stream Information Calculation

2-6 GatesAir, Inc.

Table 2-1. NetXpress LX Stream User and Computed Parameters

Number of TDM 1 Number of TDM channels to transport in a stream

Jitter Buffer Size 64 Configured jitter buffer size in packets

Computed Parameter Value Description Formula

2.2.9 Stream Statistics

2.3 System Security