Harrisbroadcast NetXpress LX Manual
Harrisbroadcast NetXpress LX Manual
Harrisbroadcast NetXpress LX 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
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.
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 [email protected]
Asia:
24/7 Technical Support +1 217 222 8200
Email [email protected]
Version Date Revision History Editor
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
GatesAir, Inc. i
Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual Table of Contents
Version 1.01
ii GatesAir, Inc.
Intraplex Products
Table of Contents NetXpress LX & CM-30 Installation & Operation Manual
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
GatesAir, Inc. v
Intraplex Products
NetXpress LX & CM-30 Installation & Operation Manual Table of Contents
Version 1.01
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.4 Components
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.
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).
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.
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.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.
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.
TDM Frames per 160 Number of TDM frames per payload (packet)
Payload
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.
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.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.
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.
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
Data Modules
PT-153 5.5 VF-15E 2.3 DS-562i 2.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.
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.
NetXpress LX
B
Multicast Audio
Stream 1
NetXpress LX
C
NetXpress LX
A
Audio Stream 2
STREAM
INTERNAL TIMING
TIMING
NetXpress LX
NetXpress LX
B
A
Stream Timing
NetXpress LX
B
Stream Timing
Internal Timing
NetXpress LX
C
NetXpress LX
A
Stream Timing
Stream Timing
NetXpress LX
B
NetXpress LX
NetXpress LX C
A
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
Stream
Timing Audio
Audio
NetXpress LX
C
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
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.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.
the same process, only in reverse order. Restored configuration takes effect when the CM-30 module
is rebooted.
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.
3.2 Installation
Note: If the shelf is AC powered, make sure the power cable can be accessed easily for maintenance
purposes.
ON
OFF
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.
10 Lnk/Act OFF There is no activity.
LAN Green The Ethernet link is established at 100 Mbps, and blinking light indicates activity.
100 Lnk/Act OFF There is no activity.
LAN Green The Ethernet link is established at 10 Mbps, and blinking light indicates activity.
10 Lnk/Act
OFF There is no activity.
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.
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.
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.
Table 3-4 gives pin assignments for the MA-230 timing input/output and contact ports.
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.
Note: The MA-230 module adapter’s RJ45 connector is not intended to be connected to
telecommunication networks.
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.
Note: When installing any channel module, you must install the corresponding module adapter first.
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.
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.
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.
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.
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.
Connector for
alarm signal
battery and ring
generator
MA-230 for
CM-30
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).
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.
* 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.
Figure 3-10. Connection for DC Operation of 3RU Systems with Two Power Sources
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.
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).
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.
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.
● 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-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.
Note: For multi-unicast streams, remember to repeat the previous 5 steps for all stream
tabs.
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.
Note: Configure system timing (Section 4.2.3.6) before putting any streams in service.
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.
7. Click on the Streams table header to back up the configuration files to the server.
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.
Edit definition: Click on the row of a specific alarm to access a Definition dialog box (Figure 4-
20) and edit the alarm definition.
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.
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.
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 =
[email protected].
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.
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.
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.
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.
1. Click on the row of the contact to be configured. The Configure Input Contact dialog box
appears (Figure 4-25).
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.
1. Click on the row of the contact to be configured. The Configure Output Contact dialog box
appears (Figure 4-26).
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.
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.
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.
Reset: Click this button to reverse all changes to this page.
Submit: Click this button to apply all bus configuration changes on this page.
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
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.
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.
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.
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.
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.
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.
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).
Reset: Click this button to reverse all changes to this page.
Submit: Click this button to apply all system timing information entries on this page.
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.
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).
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.
Header
Icons
Config File
Row Icons
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.
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.
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.
Reset: Click this button to reverse all changes to this page.
Save: Click this button to record and apply configuration entries on this page.
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).
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.
Add an address: Click to access the Add a DiffServ Marking Entry dialog box (Figure
4-39).
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
classify the IP flow.
Destination IP address: Type the IP address for the packet’s destination. This address is used to
classify the IP flow.
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.
Edit the priority of DiffServ code point: Click to change the TOS value priority (Figure
4-41).
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.
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.
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.
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.
Header
Icons
Stream
Row Icons
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
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.
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.
In Service Up You have put the stream in service, and the NetXpress LX system has received
packets.
To add a packet stream, click on the Streams table. The Stream Creation – Stage 1 page
appears (Figure 4-48).
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-51. Stream Creation – Stage 3 Page – IP Config for All Streams (Multi-Unicast)
Stream Name: The unique name entered in Stage 1 that describes the stream.
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.
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 2 page.
Next: After completing the Stream Creation – Stage 3 page, click this button to advance to the
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.
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.
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 3 page.
Next: After completing the Stream Creation – Stage 4 page, click this button to advance to the
Stream Creation Summary page (Figure 4-53).
● 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.
Use the specific Stream Configuration page as you did the Stream Creation pages (Figures 4-48
through 4-53).
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.
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.
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.
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.
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.
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.
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.
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.
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.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.
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.
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.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.
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).
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.
Loopback state: Whether or not there is a loopback set for the system.
Reset the System: Reset the CM-30 system.
Reset: Click this button to reverse all changes to this page.
Submit: Apply all changes you made to this page.
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.
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
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.
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.
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.
Active Channels: Select the audio channels (1, 2, 3, 4) to enable them on the module. Each active
channel occupies one DS0 time slot.
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.
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 the check box is not selected,
the module is offline.
Module Configured: Whether the module is properly configured.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
5.2 Troubleshooting
Use these guidelines to troubleshoot various aspects of NetXpress LX/CM-30 operation.
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.)
Note: If you are using a non-IE Web browser, your browser’s Help should give instructions on
changing the browser page settings.
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.
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:
● U.S., Canada, and Latin America: +1-217-222-8200 or [email protected]
● Europe, Middle East, and Africa: +44-118-964-8100 or [email protected]
● Asia and Pacific Rim: +852-2776-0628 or [email protected]
Section 6 – Specifications
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.
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
Timing Internal
External: RS-422 clock input
Adaptive to incoming program stream
Timing out: RS-422 clock output
Packet Optimization Packet size/rate, allows control over the inherent tradeoff
Stream Parameters
CE Compliant
Compliance
Regulatory
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
Timing Internal
External: RS-422 clock input
Adaptive to incoming program stream
Timing out: RS-422 clock output
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)
Network Performance Packet loss, packets received, packets sent, packets dropped,
Status and
Diagnosis
CE Compliant
FCC Part 15 Class A
Regulatory Compliance
UL 1950
RoHS Compliant
CE
FCC, Part 15, Class A
Compliance
UL 1950
RoHS
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.
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.
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.
Midplane
CM-30 SW1
Step 2 Step 1
MA-230
S2
Figure A-1. CM-30 Module and MA-230 Midplane Insertion
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.
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.
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.
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.