Harris CM-30, MA-230 Installation & Operation Manual

Intraplex

NetXpress LX™ Audio IP Multiplexer

& CM-30 IP Interface Module

Installat ion & Operation Manual

NetXpress LX Multiplexer

CM-30 Common Module MA-230 Module Adapter

Version 1

TOTAL CONTENT DELIVERY SOLUTIONS | Managing content. Delivering results.

Intraplex® NetXpress LX & CM-30

http://www.broadcast.harris.com/servicesandsupport/productsSupport.asp

Installation & Operation Manual

without prior writ te n permission is prohibited, except as allowed under the copyright laws.

Warranty

The information c ontained in this document is subject to change without notice. Harris makes no warranty of any kind with regard to this material, including, but not limited to, the implied

Harris Corporation Intraplex Products 4393 Digital Way Mason, OH 45040 USA

Sales: +1 513 459 3400 Fax: +1 513 701 5316 E-mail: Web:

intraplex@harris.com www.broadcast.harris.com

Get Support If you have a technical question or issu e with your Intraplex

Products equipment, pleas e c heck our customer support Web page:

warranties of m er chantability and f itness for a particular purpose.

Harris shall not b e liable for errors contained herein or for incidental or consequential dam age in connection with the furnishing, performance, or use of this material.

Trademark Credits

AudioLink PLUS™, HD Link™, IntraGuide NetXpress LX™, STL PLUS SynchroCast

, Intraplex®, NetXpress™,

, and SynchroCast3™ are

You can also call Customer Service or send non-emergency e-mail:

● U.S., Canada, and Latin America: +1-217-222-8200 or

tsupport@harris.com

● Europe, Middle East, and Africa: +44-118-967-8100 or

Service.europe@harris.com

● Asia and Pacific Rim: +852-2776-0628 or

BCDService@harris.com

trademarks of Harris Corporation. Other trademarks are the property of their respective owners.

Version Date Revisions Made Section Pages Editor

1 9/20/10 Developed manual. All All LD

No header here

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 Int e r f ace Module ......................................................................1-2

1.4.3 MA-230 Module Adapter .........................................................................1-4

1.4.4 Other Modules and Module Adapters ........................................................1-4

1.4.5 Indicator Lights .....................................................................................1-4

1.5 Web Browser User Interface .............................................................. 1-4

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

2.1 Network Concepts and Considerations ................................................. 2-1

2.1.1 MTU throughout the Network ...................................................................2-1

2.1.2 DHCP Use .............................................................................................2-1

2.1.3 Routing Table Construction .....................................................................2-1

2.1.4 WAN Port Auto-negotiation ......................................................................2-2

2.1.5 ICMP Support ........................................................................................2-2

2.1.6 IGMP Multicast ......................................................................................2-2

2.2 Streams ........................................................................................... 2-3

2.2.1 Stream Types ........................................................................................2-3

2.2.2 Stream Addressing .................................................................................2-4

2.2.3 Multicast Group Addressing .....................................................................2-4

2.2.4 Telephony .............................................................................................2-5

2.2.5 Echo Cancellation ...................................................................................2-5

2.2.6 Packetization and Overhead ....................................................................2-6

2.2.7 Packet Jitter Compensation .....................................................................2-6

2.2.8 Packet/Stream Information Calculation .....................................................2-6

2.2.9 Stream Statistics ...................................................................................2-7

2.3 System Security ............................................................................... 2-7

2.3.1 NetXpress LX Login ................................................................................2-8

2.3.2 Management Protocols on an Interface .....................................................2-8

2.3.3 IP Access List Use ..................................................................................2-8

2.3.4 SNMP Communities ................................................................................2-8

2.4 NetXpress LX QoS ............................................................................ 2-9

2.4.1 COS Levels for Stream Data ....................................................................2-9

2.4.2 TOS Byte Marking for Outbound Stream Packets .......................................2-9

2.4.3 User-Defined TOS Byte Setting for Outbound SNMP and HTTP Packets .........2-9

2.5 NetXpress LX Internal TDM Busses ..................................................... 2-9

2.5.1 Compatibility with Intraplex TDM Channe l Modules ....................................2-9

2.5.2 TDM Channel Loopbacks ....................................................................... 2-11

2.5.3 TDM Bus Mapping ................................................................................ 2-11

Harris Corporation i Intraplex Products

NetXpress LX & CM-30 Installation & Operati on Manual Table of Contents Version 1, September 2010

2.6 System Time-of-Day ....................................................................... 2-12

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

2.7.1 Types of System Timing ....................................................................... 2-12

2.7.2 NetXpress LX Timing Scenarios ............................................................. 2-13

2.8 NetXpress LX System and FEC ......................................................... 2-17

2.9 Power ........................................................................................... 2-18

2.10 Voice Signaling .............................................................................. 2-18

2.10.1 RBS ................................................................................................... 2-18

2.10.2 CAS ................................................................................................... 2-18

2.11 Software Download ........................................................................ 2-19

2.12 Configuration Files Backup and Restoration ....................................... 2-19

2.13 Fault Detection and Reporting .......................................................... 2-19

2.13.1 Alarm Hierarchy .................................................................................. 2-20

2.13.2 Alarm History ...................................................................................... 2-20

2.13.3 SNMP Traps Use for Fault Reporting ....................................................... 2-20

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

3.1 Installation Preparation...................................................................... 3-1

3.1.1 Tools & Cables Required .........................................................................3-1

3.1.2 Equipment Unpacking & Inspection ..........................................................3-1

3.2 Installation ....................................................................................... 3-2

3.2.1 Shelf Installation ...................................................................................3-2

3.2.2 CM-30 Module Kit Installation ..................................................................3-2

3.2.3 Channel Module Inst allation ....................................................................3-8

3.2.4 Power Supply Installation .......................................................................3-9

3.3 Wiring & External Connections ............................................................ 3-9

3.4 Power Application ........................................................................... 3-15

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

4.1 Download Current Software................................................................ 4-1

4.2 Configuration Procedures ................................................................... 4-1

4.2.1 Connect and Log On to Access NetXpress LX Home Page ............................4-1

4.2.2 View System Mode .................................................................................4-2

4.2.3 Perform General Setup ...........................................................................4-2

4.3 NetXpress LX Pages ......................................................................... 4-14

4.3.1 Start at NetXpress LX Home Page .......................................................... 4-14

4.3.2 Define & Review Fault Information ......................................................... 4-16

4.3.3 Configure the System ........................................................................... 4-21

4.3.4 Configure the Network ......................................................................... 4-36

4.3.5 Configure Streams ............................................................................... 4-49

4.3.6 Check Multiplexer Performance .............................................................. 4-59

4.3.7 Set Up Security ................................................................................... 4-71

4.3.8 Send Echo Requests ............................................................................. 4-75

4.3.9 Configure CM-30 Module ...................................................................... 4-75

ii Harris Corporation Intraplex Produc ts

Table of Contents NetXpress LX & CM-30 Installation & Oper ation Manual Version 1, September 2010

4.3.10 Configure Individual Modules (TDM Modules and CAMs) ............................ 4-79

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

5.1 Testing ........................................................................................... 5-1

5.1.1 General Status Test ...............................................................................5-1

5.1.2 CM-30 Alarm Test ..................................................................................5-2

5.1.3 Ping Test ..............................................................................................5-4

5.1.4 Streams Test ........................................................................................5-4

5.2 Troubleshooting ................................................................................ 5-6

5.2.1 Channel Module Additio n ........................................................................5-6

5.2.2 Web Browser Interface ...........................................................................5-6

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

6.1 Detailed Specifications ...................................................................... 6-1

6.1.1 NetXpress LX IP Multiplexer ....................................................................6-1

6.1.2 CM-30 IP Int e r f ace Module ......................................................................6-3

6.2 Notice of FCC Compliance .................................................................. 6-5

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

A.1 Installation Preparation ..................................................................... A-1

A.1.1 Equipment Unpac king & Inspection ......................................................... A-1

A.1.2 Card Slot Selection ............................................................................... A-2

A.2 IP Multiplexer Conversion Pr ocess ...................................................... A-2

A.2.1 CM-30 & MA-230 Installation into the First Multiplexer .............................. A-2

A.2.2 First CM-30 IP Interface Module Configuration .......................................... A-3

A.2.3 CM-30 & MA-230 Installation into the Second Multiplexe r .......................... A-4

A.2.4 Second CM-30 IP Interf ace M od u le Configuration ...................................... A-4

A.2.5 Configuration of Both CM-30 Modules to Work Together ............................ A-4

A.2.6 Removal of the Original Common Modules ............................................... A-6

Harris Corporation iii Intraplex Products

No header here

This page is left blank intentionally.

iv Harris Corporation Intraplex Produc ts

No header here

Section 1 – Introduction

This manual covers both the N etXpress LX IP multiplexer and the CM-30 IP interface module. The NetXpress LX multiplexer provides convenient provision ing and managemen t tools to enhance operational efficiency. This IP platform supports both u nicast and multicast a nd is compatible with the Intraplex NetXpress multiplexer.

The NetXpress LX mu ltip lexer combines the tec hnology of the original NetXpress multiplexer in a module configur a tion compatible with Intraplex T1 or E1 systems. The NetXpress LX multiplexer is available in either a 3RU frame with cap a c ity for up to 17 application modules or a 1RU frame that can hold five applica tion modules. This mu ltip lexer can work in a simple point-to-point an d point-tomultipoint designs and also as an “edge” device with the NetXpress m ultiplexer in large, multisite networks.

While the CM-30 I P interf a c e m odule operates as the command module in a NetXpress LX multiplexer, this module can also replace the netw or k interface module in an existing T1 or E1 system, conv er ting it to IP while utilizing the existing c hassis with all its audio, voice, and data modules. With the CM-30 module, you can easily transition an existing Intr aplex T1 or E1 system to cost-effective IP transmission.

1.1 Key Features

The NetXpress LX system’s features include

● CM-30 IP interface module, which can convert existing T1 or E1 systems to IP

● Compatibility w ith Intraplex NetXpress systems

● Wide variety of au d io, voice, and data inter face modules

● Optional echo ca ncellation for 2-wire voice circuits

● Transport of two c ontact closures in each direction

● Adjustable packet size

● Programmable jitter buffer depth

● Advanced Intraplex forw a rd error c orr ec tion

● Quality of Serv ic e ( Q oS) priority tagging

● Unidirectional or bidirectional unicast streaming

● Unidirectional multicast stream ing

● Web browser user interface

● SNMP control

● Current and prev ious software revis ion storage

● Network statistic s monitoring

● Event logging

1.2 Manual Use

This manual is th e pr im ary reference document for installin g, configuring, operatin g, a nd troubleshootin g the NetXpress LX multiplexer and the CM-30 IP interface module. If you have additional quest ions pertainin g to the operation of you r Intraplex system, you can contact Harris Customer Service:

● U.S., Canada, and Latin America: +1-217-222-8200 or

● Europe, Middle East, and Af r ica : +44-118-964-8100 or

● Asia and Pacific Rim: +852-2776-0628 or

Harris Corporation 1-1 Intraplex Products

tsupport@harris.com

Service.europe@harris.com

BCDService@harris.com

NetXpress LX & CM-30 Installation & Operati on Manual 1 – Introduction Version 1, September 2010

1.3 Manual Scope

The “Table of Contents” helps you locate specif ic topics. Thes e guidelines give general information on manual sections.

● Readers unfamil iar with the NetXpress LX system and/or the CM-30 IP interface module – Use this manua l as a tutorial. Read or skim a ll s ections in order.

● Installers – If y ou are already familiar with the NetXpress LX system and/or the CM-30 IP interface module, finish reading this section and go d ir ectly to Section 3 – “Installation & Wiring” for step-by-step installation instr uctions.

● Transmission and Planning Engineers – The NetXpress LX and CM-30 operation and configuration overview is in Sec tion 2 – “Functional Desig n,” and specific instructions are in Section 4 – “Configuration & Operation.” You can find output, power, and other specification information in S ection 6 – “Specifications.”

● Maintenance Technicians – Section 5 – “Testing & Troubleshooting” discusses system tests and troubleshooting solutions. I ndividual channel module setup an d tes t proc edures can be found in the manuals f or the modules shipped with y our system.

1.4 Components

1.4.1 Main Equipment Shelf

The NetXpress LX chassis has two rack-mount equipment sizes:

● NetXpress LX-300 – 19-inch wide, 5 ¼-inch high 3RU (Figure 1-1)

● NetXpress LX-100 – 19-inch wide, 1 ¾-inch high 1RU (Figure 1-2)

Figure 1-1. NetXpress L X-300 F ront Panel with Cover

Figure 1-2. NetXpress L X-100 F ront Panel with Cover

Each shelf is equipped with a CM-30 module, a MA-230 module adapter, and slots for plug-in channel modules and module adapters.

The NetXpress LX-100 multip lexer has a single built-in AC pow er s upply. The LX-300 multiplexer has a single plug -in AC or DC power supply and optional secondary plug-in AC or DC supplies.

1.4.2 CM-30 IP Interface Module

The CM-30 module (Figure 1-3) is the comma nd center for the NetXpress LX IP multiplex ing system.

1-2 Harris Corporation Intraplex Produc ts

1 – Introduction NetXpress LX & CM-30 Installation & O p er ation Manual Version 1, September 2010

Harris Corporation 1-3 Intraplex Products

Figure 1-3. CM-30 IP In terface Module

NetXpress LX & CM-30 Installation & Operati on Manual 1 – Introduction Version 1, September 2010

This module acts as an IP network interface, a packet engine, and a system manager. When coupled with the MA-230 module ada pter (Section 1.4.3), the CM-30 module provides sh elf m a nagement control, WAN an d LAN traffic control throu g h 10/100Base-T ports , and timing contr ol for external stream traffic and system synchronization.

You can use a CM-30 module in place of, bu t 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 Intra p lex T1 or E1 multiplexer. Y ou can then revert back to T1 or E1 at a la ter da te by simply removing the C M-30 module and reinserting the original common m od ule.

1.4.3 MA-230 Module Adapter

The MA-230 module adapter provides connectivity for the CM-30 module. The MA-230 module adapter connects to the CM-30 module in the rear of the shelf and features these communication ports:

● Two 10/100Base-T ports (WA N an d LAN)

● Timing in/out for external stream an d s ystem synchroniza tion

● Contact I/O f or external control

1.4.4 Other Modules and Module Adapters

The NetXpress LX system offers five channel card slots (1RU shelf) or 17 channel card slots (3RU shelf) for Intraplex audio, voice, and data modules.

Intraplex module a d a pte r s are installed in th e rear of the shelf a nd work in conjunction w ith the channel access cards installed in the front.

1.4.5 Indicator Lights

Four system status indica tor lig hts located on the NetXpress LX power su pply a r e visible when the front shelf cover is on (Figures 1-1 and 1-2).

● POWER – This green light is on when the multiplexer is pow er ed.

● NORMAL – This green light is on when no major nor minor alarm is present.

● ALERT – This yellow light is on when a minor alarm condition exists.

● ALARM – This red light is on when a major alarm condition exists.

Section 5 defines major and minor alarm c onditions. The CM-30 module has indicator lights as well, which are visible when the front shelf cover is off.

Section 3.2.2 gives more information about CM-30 indicator ligh ts.

1.5 Web Browser User Interface

You can control functionality of your NetXpress LX unit and access network statistics and system status through the NetXpress LX Home page. You can choose to ru n simultaneous software windows; each connected to a differen t N etX pr es s LX system in the network. The Web browser interface, in conjunction w ith an SNMP network manager, lets you control and monitor your system from one operation center. You can access the Home page from the netw or k management system to research a particular problem or obtain a grap hical view of system configuration or s ta tus. Section 4 – “Configuration & Operation” giv es more information on this interface software.

1-4 Harris Corporation Intraplex Produc ts

No header here

Section 2 – Functional Design

This section describes the intent of IP multiplexing and day-to-day operations of the NetXpress LX system and the CM-30 IP interface module. The section also describes how to use the IP multiplexer and interface module to configure real-time payl oad transport of audio and data over exis ting IP networks.

Packet-based media transport with the N etX pr es s LX system or the CM -30 m odule provides

● Transport of aud io, voice, data, and video.

● Flexibility when integrating to bus iness applications, systems, and networks.

● Network monitoring.

● Error mitigation .

● Transition and mig r a tion from legacy sys te m s with reuse of modules and components.

2.1 Network Concepts and Considerations

When looking at th e N etXpress LX system (or the CM-30 module) and packet-switched services as a whole, consider these net work-related concepts:

● MTU throughout the network

● DHCP use

● Routing table con s truction

● WAN port auto-negotiation

● ICMP support

● Redundant WA N lin k configuration

● IGMP multicast

2.1.1 MTU throughout the Network

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

2.1.2 DHCP Use

Dynamic Host C onfiguration Protocol ( D HCP) is a network pr otoc ol that enables a D HCP server to automatically assign an IP address to an individual computer’s IP network interface. DHCP dynamically assigns a number from a defined r a nge of numbers configured for a given network.

The NetXpress LX system supports dynamic address assignment for its LAN interface using DHCP. On the WAN interfa c e , only static IP addres s assignment is supp or ted . You can elect to enab le the DHCP option for the management interfac e from the Networking Ethernet Interfaces Web page (Section

4.3.4 – Configure the Ne twork). If DHCP is enabled and the system fails to successfully retrieve an IP

address, it defaults to the factory default address – 192.168.1.1.

2.1.3 Routing Tab le Construc tion

The behavior of the NetXpress LX system within the customer’s network is that of a n IP host. As such, the NetXpress LX routing table is used sole ly to route internally generated packe ts . For streams that are unicast, the determination of the next-hop gateway to reac h the remote NetXpress LX shelf is done by examinin g the system routing tab le.

Harris Corporation 2-1 Intraplex Products

NetXpress LX & CM-30 Installation & O p er ation Manual 2 – Functional Design Version 1, September 2010

Routes in the rou ting table fall into two ba sic categories: a utomatic routes and user-defined routes. The NetXpress LX system adds automatic routes based on the interface IP addresses. These routes are called “directly connec ted” 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, how ever, you need to add routes to remote n etw orks or hosts so that the NetXpress LX system can successfully send traffic to it. In the simples t c ase, 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 “gatew ayIP”) pointin g 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 SNM P access of the proprie tary route management MIB (Management Information Base).

2.1.4 WAN Port Auto-negotiation

The auto-negotiation mechanism accommodates multi-speed Ethernet network devices. Autonegotiation occurs when a physical connection is made between a NetXpress LX Ethernet port and an Ethernet port on a network switch or r outer. During this proc ess, the two Ethernet devices use a protocol to determine at what speed (10 Mbps or 100 Mbps) they commu nicate and whether the exchange of data occurs in a half-duplex (only one end transmits a t a tim e ) or full-duplex manner.

With the NetXpress LX system, you can enable or disable auto-negotiation for the WAN ports beca use it is crucial that the link characteristics are set correctly to facilitate the tra nsmission of stream d a ta . Auto-negotiation should be e nabled when the network port to which the NetXpress LX system is being connected is capab le of negotiating t o a mode of 100 Mbps or 10 Mbps and full -duplex operation. When auto-negotiation is disabled, each Ethernet port is set to o per a te at 100 Mbps speed in fullduplex mode, the op timum setting. I f the anticipated str eam data rate is low en ough, the WAN port can operate effectively at 10 Mbps. Operating the W A N por t in half-duplex mode should be avoided. Both sides of the lin k need to be set for auto-negotiation. I f not, the NetXpress LX system configures itself for 10 Mbps, half duplex , and streams experience dropp ed pa c kets due to collision on the Ethernet link.

The LAN port is always set to auto-ne gotiate. The mana ge m ent port can satisfy its f unction even when operating at 10 Mbps in half -duplex mode.

Note: Do not operate auto-negotiation on only one side of the NetXpress LX link . To work properly,

both sides (NetXpress LX system and connecting dev ice) m ust 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 configu r ed for 100 Mbps fullduplex.

2.1.5 ICMP Support

The ICMP (Intern e t Control Message Pr otocol) delivers e r r or and control messages from hosts to message requestors. An ICMP test may determine whether a des tin a tion is reachable. The ICMP messages typically report errors in the processing of datagrams. A dd itionally, ICMP provides flow control and first-hop gateway r edirection. On the NetX p r ess LX WAN port, the r e is an option to block ICMP error messages, but the “ping” messages are always allowed.

2.1.6 IGMP Multicast

The NetXpress LX system (or the CM-30 modu le in an original Intr aplex system) interoperates with multicast routers u s ing the Intern et Group Management Pr otocol (IGMP). The IGMP Mu lticast mode involves transmission to specific hosts through IGMP routers. This scheme allows you to route specific packets onto specific segments, thereby segregating unwanted traffic from na r row segm ents.

The NetXpress LX system supports IGMP v2 messages. When a “receive” multicast stream is configured, it sends out IGMP membership reports. Similarly, when the multicast streams are deleted, the NetXpress LX system sends out an IGMP Leave message and also responds to the membership

2-2 Harris Corporation Intraplex Produc ts

2 –Functional Design NetXpress LX & CM-30 Installation & O p er ation Man ual Version 1, September 2010

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 Intrap lex multiplexer, th e CM-30 IP interface module uses packet streaming to transport audio signals.

2.2.1 Stream Types

2.2.1.1 Unidirectional versus Bidirectional

Packet streams c an be unidirectional or bidirectional. In other words, streams can travel in one direction (transmitted or received) or two directions ( tr ansmitted and rece ived). The CM-30 module supports both u nidirectional and bid ir ect ion al pack et str eam ing.

Most circuit types (su ch as voice and two-way data circuits) are bidirectional, or full-duplex. Fullduplex circuits re quire identical f ull-duplex (transmit or receive) channel modules at both ends of the channel they occupy within a system. Other circ uit types (such as program audio channels) are unidirectional (simplex ) . They always have a transmitter modu le a t on e end and a receiver module at the other. Most bid ir e c tional (full-du plex) channel modules can also be set up to operate in a unidirectional (simplex) mode.

2.2.1.2 Unicast versus Multicast

Packet streams can also be classified as unicast or multicast. Unicast describes transmitting a piece of information (a pa c ket stream in this c a se) from one point to an other point. Unicast transfer mode is still the predomin ant form of transmission on LANs and within the Internet. Standard unicast applications include HTTP, SMTP, FTP, and Telnet.

Multicast descri b es communication w here a piece of inform a tion is sent from one or m or e points to a set of other points (a multic a s t gr ou p a ddr es s ) . There may be one or more senders a nd the information is sent to a set of receivers (there may be no receiver or any number of receivers). With multicasting, the same packet is delive red simultane ously to a group of c lients. Multicast applic ations must use the UDP (User Datagram Protoc ol) tr ansport protoco l, since TCP (Trans m ission Control Protocol) only supports the unic a s t mode.

Most circuits provided by Intraplex m ultiplexer syste m s are unicast, including those provided with the NetXpress LX system. However, several types of c hannel modules can be configured for poin t -tomultipoint opera tion (multicast) . For example, you can set up a single program audio tra nsmitter module and several program audio receiver modules in a point-to-multipoint or “ br oadcast” circuit configuration, allowing multiple loc ations to receive the same program audio signal.

If your network does not support multicasting, you can configure the NetXpress LX system to m ultiunicast up to four destin a tions. The programm ing source must be in contiguous time slots on TDM Bus A. The receivers can be on the in ternal TDM bus. Section 4.3.3.4 – TDM Bus Mapping Configur ation gives additional mu lti-unicast infor mation.

2.2.1.3 Voice Streams versus Data Streams

Streams which are intended to carry in formation for voice gr a d e audio modules of ten require additional signaling information to s upport pulse dialing, off-hook con d ition call progress or ringing states. Special signaling support is required to transport this added information. V oic e a udio streams carrying telephone calls are also prone to audio echo back from the receiver. You can use echo canceling circuits to eliminate this p r oblem. Streams us e d for transporting linear or compressed wideband audio modu les or other forms of raw information p r esent their data d ir ectly into each channel and do not require signaling s upport.

Harris Corporation 2-3 Intraplex Products

NetXpress LX & CM-30 Installation & O p er ation Manual 2 – Functional Design Version 1, September 2010

2.2.2 Stream Addressing

The stream addressing process involves designating a de s tination IP address for both unicast and multicast IP streams (Section 4.3.5– Configure Streams). During the process of adding streams, individual streams are designated as either unicast or m ulticast in the Transmission Type field (Section

4.3.5.1 – Stream Creation).

When you create a stream, a UDP port number must be specified for both the lo c a l a nd remote NetXpress LX devices. The RTP protocol convers a tion between the two devices tak es pla c e through the specified UDP ports.

The range for UDP port numbers must be greater than or equal to 5000 0 a nd a multiple of 5, ending in either a 0 or a 5. For unicast and multicast receive streams, the combination of peer’s IP address and source and destination UDP ports must be unique. For multicast transmit streams, each stream must have unique ports.

Many networks use a device known as a “ firewall” at the entry point to the network to prov ide security against hackers and other undesira b le applications. Usually, network d evices in the private network behind the firewall can freely transmit out using any UDP port number. However, devices ar e blocked from receiving packets using a UDP por t number until a packe t is tr ansmitted out th e firewall using the same UDP port. When setting up the network for a NetXpress LX installation, you may need to configure the firewall to allow commun ic a tion on the UDP port nu m b er s used for stream tra ffic before attempting to brin g up a stream.

2.2.3 Multicast Group Addressing

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

2-4 Harris Corporation Intraplex Produc ts

2 –Functional Design NetXpress LX & CM-30 Installation & O p er ation Man ual Version 1, September 2010

Figure 2-1. Carrier Multicast Backbone Example

2.2.4 Telephony

The CM-30 module and NetXpress LX system allow you to cr e a te streams whose endpoints are Intraplex voice channel modules that s upport telephone s ignaling (for examp le, the VF-15E, VF-16AE, and VF-25 modules). The voice circuits generate signaling bits which the NetXpress LX system transports out-of-ba nd and reinserts onto the NetXpress LX intern a l T DM bus at the receive end. No more than 20 telephony streams are a llowed in-service at one time.

Telephony streams can be easily iden tified in the stream table by the tel ephone 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 sig naling 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 TD M bus using Channel A ssociated Signalin g ( CAS). Telephony streams need to originate and term inate on busses where the CAS mode is enabled. You can s elec t th e s pec if ic T D M busses for the telephony strea m s 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 car r y the signaling bits for a ll the other channels on that bus; this time slot is not available to carry normal traffic.

2.2.5 Echo Cancellation

The NetXpress LX system can provide echo c a ncellation for voic e circuits using up to 2 optional echo canceller cards that plug onto the CM-30 modu le. Each board can provide echo cancellation for up to 30 channels per echo canceller card on the TDM bus.

Echo cancellation can only be enabled f or full-duplex str ea ms with identical bus/cha nnel configuration in the transmit (Tx) and receive (Rx) direction, and both en dp oints of the stream need to have an echo canceller card installed. Echo cancellers are needed in 2-wire modules (for example, the VF-15E

Harris Corporation 2-5 Intraplex Products

NetXpress LX & CM-30 Installation & O p er ation Manual 2 – Functional Design Version 1, September 2010

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 enca ps ulate more than 60 fr a mes per packet.

2.2.6 Packetization and Overhead

Packetization is a process in which frames of data from the TDM bus are collected into IP packets f or transmission th r ough the IP network . A frame on a NetXpress LX T D M bus is divided into 32 par titions or time slots, each containing a byte of data. Because of the serial nature of the TDM bus, an entire TDM bus frame encompasses 125 µs in time. The stream packetization interval def ines the number of TDM frames collected by th e NetXpress LX sy stem into a single packet for transmission. The higher the packetization interval, the greater the accumula tion delay introduce d to the program because each frame must be accumulated befor e th e pa c ket can be created. Note that the tot a l progr a m delay is a combination of pa cketization delay a nd network delay.

Each packet in a NetXpress LX stream contains 44 bytes of non-program data (overhead) corresponding to the header infor m a tion required for th e IP, UDP, and RTP protocol la yers. The ratio of non-program data to program data for a packet can be considered the overhead requ ir ed to get the packet through the network. The higher the overhead, the more the network b a ndwidth available t o an application used to transmit non-program data. Program delay can be m in im iz ed by using a small packetization interval at th e expense of an increase in overh ea d. Conversely, increasing the packetization interval decreases the ov er head but increases the program de la y (Table 2-1).

Another overhead determination factor is the number of time slots from each TDM frame that get placed in the packet. As this number increases, the stream overhea d dec rea s es because the ratio of overhead data to program da ta dec r ea s es . However, the number of time s lots consumed from each frame does not affect the progra m delay. Therefore, it is desirable t o c ombine time slots from a TDM bus headed for th e same destination into a single stream to reduce overhead and to make the best use of available network bandwidth.

2.2.7 Packet Jitter Compensation

In an IP network, the time required for a pa cket to travel through the network from s e nder to receiver is not guaranteed to be maintained. As a r es ult, the receiver can see the interva l betw een the arrival of packets vary throu ghout the rec eption of the packet stream. For a giv en packet, the difference between the packet’s delay a nd the average of the delay values for all packets in the stream is known as jitter. The jitter can be pos itive or negative depending on whether the packet delay is less than or greater than the average delay .

For many network services, packet jitter is not an issue, and no techniqu e is needed to compensate. However, the continuous playout nature of audio and video require that there must be s ome means of guaranteeing that the receiver always has the next pack et of da ta w hen the previous packet is consumed. Th e r eceiver must also hold onto pa ckets that arriv e early so that they a re available for playout at the prop er time.

The NetXpress LX system compensates for s tr eam packet jitter through the use of a jitter buffer. The system maintain s a jitter buffer for ea ch stream on the receiv e s ide . The buffer is siz ed s o that the buffering delay is greater t han the maximum packet delay expected through the network. In the NetXpress LX system, you specify the jitter buffer size in number of packets rangin g from 8 to 128 (Section 4.3.5.1 – Stream Cr ea tion). The packetization interval of the stream controls the amount of packet delay for which the jitter buffer can compensate. I ncreasing the number of TDM fra m es contained in a pac ket increases the size of the jitter buf fer as measured in time.

2.2.8 Packet/Stream Information Calculation

Table 2-1 gives an example of user and computed parameters for a NetXpress LX stream. The user parameters represent us er -defined stream parameters. The computed parameters ar e for packet information and network bandwidth based upon the user parameters. This table also gives formulas for how to derive com puted parameters for a stream.

2-6 Harris Corporation Intraplex Produc ts

2 –Functional Design NetXpress LX & CM-30 Installation & O p er ation Man ual Version 1, September 2010

Table 2-1. NetXpress LX Stream User and Computed Parameter s

User Parameter Value Description

Number of TDM Channels

TDM Frames per Payload

Jitter Buffer Size (8 – 128 packets)

Computed Parameter Value Description Formula

TDM Channel Data Rate 64 kB/S Calculated TDM channel data rate in kB/S Number of TDM Channels x 64 Packet Payload Size 160 bytes Calculated payload size in each packet in

Packet Interval 20 mS Calculated packet interval (time between

Packet Rate 50

Jitter Buffer Delay 640 mS Calculated jitter buffer delay in mS

Ethernet Frame Size 242 bytes Calcula te d Ethe rnet frame size in bytes =

Ethernet Stream Data Rate

IP Packet Size 204 bytes Calculated IP packet size in bytes =

Stream Data Rate 81.6 kB/S Calculated IP s trea m data rate in kB/S * IP Packet Size x Packet Rate x

1 Number of TDM channels to transport in a stream

160 Number of TDM frames per payload (packet)

64 Configured jitter buffer size in packets

bytes

packets) in mS

packets/S

96.8 kB/S Calculated Ethe r ne t str e am data rate in

Calculated packet rate for a stream in packets/S

Note: This delay assumes a receive queue of half the jitter buffer size

Packet Payload Size + Ethernet overhead (38 bytes – no VLAN) + IP overhead (20 bytes IP + 8 bytes UDP + 16 bytes RTP)

kB/S *

Packet Payload Size + IP overhead (20 bytes IP + 8 bytes UDP + 16 bytes RTP)

Number of TDM Channels x TDM Frames per Payload

Number of TDM Frames per Payload ÷ 8

(1 ÷ Packet Interval) x 1000

Jitter Buffer Size x Packet Interval ÷ 2

Packet Payload Size + 38 + 44

Ethernet Frame Size x Packet Rate x 8 ÷ 1000

Packet Payload Size + 44

8 ÷ 1000

* In most instances, Ethernet overhead is stripped before the pac k et is tra nsported over a WAN link.

However, in cer tain instances (su c h a s Metro Ethernet networ ks that transport the entire frame); the Ethernet overhead is left on the packet.

2.2.9 Stream Statistics

NetXpress LX stream statistics are receiver-based. The time interval for collecting stream statistics is user-selectable (from 5-10 seconds for each stream). It is a good practice to review your stream statistics on a regularly scheduled basis (Section 4.3.6.1 – Stream Statistics). Y ou may be able to modify your NetXpress LX system for optimum throughput, bandwidth efficiency, and reduced errors.

As an example, you may wish to alter the siz e of the jitter buffe r if you are experiencing too many lost, underrun, early, or late packets. Specifically , if you are experienc ing too many late packets, you might need to increase the jitter buffer size.

2.3 System Security

System security is controlled throu gh

● Logon and passwor d c ontrol.

● Interface protocol mana gement enabling and disabling.

● An IP access list.

Harris Corporation 2-7 Intraplex Products

NetXpress LX & CM-30 Installation & O p er ation Manual 2 – Functional Design Version 1, September 2010

● Establishment and and control of SNMP Com m unities.

2.3.1 NetXpress LX Login

When you launch the Web server interf a c e a p plic ation, the system immediately displays the logon screen (Figure 2-2). You must type the proper user name a nd password to gain access to the NetXpress LX Web interface. Before it is c onfigured, the NetXpress LX system has a default administrator user name of “admin” and default password of “admin” for the Web interface. Once you initially log on, you can change the Web interface administrator password, as well as administrator and guest accounts for Web FTP access (Section 4.3.7.1 – Accounts).

Figure 2-2. NetXpress LX Web Interface Logi n

2.3.2 Management Protocols on an Interface

The NetXpress LX system comes with two Ethernet interfaces:

● WAN

● LAN

The LAN interface allows you to run all managem ent traffic on a separate network if desired. By default, each interface accepts HTTP and SNMP protocols and allows FTP and Telnet sessions to be

established. You can use the interface screens in Section 4.3.4 – Configure the Network to enable or disable differen t p r otocols for each interface. Contr olling protocols by interf ace enables you to

● Tighten security

● Block unwanted tr a ffic

● Ensure network privacy

2.3.3 IP Access List Use

You can add secur ity to your NetXpress LX installation b y limiting access based on specific IP addresses (Section 4.3.7.2 – IP Access List). You can also use th e s a me networking configuration screen to specify which interface can be used to gain access to the system.

2.3.4 SNMP Communities

An SNMP community is a group of hosts that you can man age as a distinct group with SNMP. You must use a community name for all SNMP c onversations to take p la ce. You can use the same name for

2-8 Harris Corporation Intraplex Produc ts

2 –Functional Design NetXpress LX & CM-30 Installation & O p er ation Man ual Version 1, September 2010

a read-only community a nd a r e a d -write community, or you can specify two different nam e s to r e s tr ict write-access to the system.

2.4 NetXpress LX QoS

Quality of Service (QoS) / Class of Service (COS) mechanisms can reduce flow complexity by mapping multiple flows in to a few service levels. N etwork resources are then allocated ba s ed on these service levels and flows can be aggregat ed a nd forwarded according to the ser vice class of the packet.

2.4.1 COS Levels for Stream Data

The class of service (COS) level for a stream is established when the strea m is created. The NetXpress LX system offers four COS levels (high, normal, medium, low) for stream data (Section 4.3.5.1 – Stream Creation). The classes are based on service priority; the higher the priority, the more immediate the handling of the stream. For example, program audio is critical in many operations, so when a stream is configured for program a udio, you designate a high class of service le vel for that packet stream. C onversely, a voic e c ircuit might be consider ed less critical to operations, so y ou might specify a lower COS level.

2.4.2 TOS Byte Marking for Outbound Stream Packets

In an IP network, all IP packets contain a field in the IP header called the Type of Service (TOS) by te. The value of the TOS byte tells the network what quality of service needs to be applied to the packet. You can define what the value of the TOS b yte field should be for ea c h of the four classes of service supported by the NetXpress LX s ystem for stream packets. The system pla c es the appropriate TOS byte value corres ponding to the COS pr ovisioned for a stream in every outbound data p a c ket for that stream (Section 4.3.4.3 – Class of Service). Since TOS byte value can be set to any value per class of service, the NetXpress LX system can operate in networks using Differential Services (Diff Serv) QoS and networks em p loying the standard T O S interpretation for QoS.

2.4.3 User-Defined TOS Byte Setting for Outbound SNMP and HTTP

Packets

In addition to suppor ting 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 interfac e tr a ffic to be handled in the network with a d ifferent class of service than other packets.

2.5 NetXpress LX Internal TDM Busses

The NetXpress LX IP multiplexer uses two TDM busses to support data transfer for audio channels. These busses (TDM Bus 1A and TDM Bus 1B) can be configured to operate in T1 or E1 mode.

Note: Both A side and B side busses operate in th e s a m e mode; you cannot have a T1 bus and an E1

bus.

When set for T1 mode, the TDM bu sses support robbed-bit signaling. When set for E1 mode, the TD M busses in the NetXpress LX system support CAS (channel associated signaling) and CCS (Common Channel Signaling). With CAS sign aling, time slot 16 is always reserved for telephone signaling. The data rate is fixed at 1.544 MHz (T1 mode) or 2.048MHz (E1 mode). In E1 mode, you can enable or disable signaling.

2.5.1 Compatibility with Intraplex TDM Channel Modules

Nearly all Intra p lex TDM channel modules are compatible with the NetXpress LX multiplexer. Table 2-2 shows currently supported modules.

Harris Corporation 2-9 Intraplex Products

NetXpress LX & CM-30 Installation & O p er ation Manual 2 – Functional Design Version 1, September 2010

Table 2-2. NetXpress LX-supported TDM Chann el Modules

Module

PT-150A 4.7 PT-150B 4.0 PR-D150 6.6 DA-191B 1.2 PT-150C 4.0 PT-D350 3.0 DA-91A 1.0 PR-150A 6.6 PR-D350 3.4 DA-91i 1.0 PR-150B 6.0 PT-D355 3.0 DS-64NC 2.5 PR-150C 6.0 PR-D355 3.4 D-100 3.0 PT-153 5.5 PR-153 5.5 VF-16AE 2.3 DS-961D 1.2 PTR-155 5.0 VF-16E 2.3 DS-961DE 1.2 PT-250 3.0 VF-25E 2.0 DS-961DF 1.2 PR-250 3.4 VF-27E* 2.0 DS-961DG 1.2 PTR-255 7.7 VF-28E 2.0 DS-965 1.2 PT-350 3.0 VF-29E 2.0 DS-966 2.5 PT-350B 3.0 PT-350C 3.0 VF-16 2.3 PR-350 3.4 VF-16A 2.3

Nominal

Power

(watts)

High Fidelity

Nominal

Module

PT-D150 4.7

Input / Output

Program Audio

Modules–AES\EBU

VF-15E 2.3 DS-562i 2.0

Voice Modules for E1

VF-15 2.3 OCU-DP 2.0

Power

(watts)

Module

DA-191A 1.2

Data Modules

Nominal

Power

(watts)

PR-350B 3.4 VF-25 2.0 PR-350C 3.4 VF-27* 2.0

PT-353 3.0 VF-28 2.0 PR-353 3.4 VF-29 2.0 PT-355 3.0

High Fidelity Program Audio Modules – Analo g Inp u t/ Output

PT-355B

PT-355C

PR-355 3.4 PR-355B 3.4 PR-355C 3.4

3.0

Secure

Voice Modules for T1

VF-40 2.0

DV-600 5.0

Voice

Digital

Modules

DV-600A 5.0

* Neither the VF-27 nor VF-27E module supports or oper a tes 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 infor m it that CAS signalin g is in use. Each TDM bus has its own frame loss signal to tell the modules to mute if there is a problem with th e a rr iving data intended for that particular bus.

2-10 Harris Corporation Intraplex Produc ts

2 –Functional Design NetXpress LX & CM-30 Installation & O p er ation Man ual Version 1, September 2010

2.5.2 TDM Channel Loopbacks

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

Figure 2-3. NetXpress LX TDM Loopback Scenarios

When you apply the internal loopback to a time slot or a group of time slots on the TDM bus, the channel module data is copied back to the receive channel on that same TDM bus, as well as being transmitted to its IP targets. Wh en you apply the external loopback to a time slot or a group of tim e slots on the TDM bus, the received data is d eliv ered to the channel modu le on t h at same TDM bus as well as being trans m itted back out to its originating sour c e. You can apply both internal and extern al loopbacks simultaneously. This e xample shows loopba c ks for an entire bus. However, you can also loopback individual time slots within a bus.

2.5.3 TDM Bus Mapping

The NetXpress LX or CM-30 TDM bus is connected by default to a virtua l IP bus; this connection is bidirectional. The TDM bus mapping fea ture allows you to r econfigure your c onnections to suit your needs. You can connect a time slot from TDM A, TDM B, or either of the echo cancellers to the corresponding tim e s lot on any of the 4 IP ports . You can connect a time s lot from TDM A or TDM B to the corresponding time slot on either of the echo cancellers.

The NetXpress LX system (or CM-30 module) has 2 bus map choices:

● The pre-configured default map has both TDM A and TDM B busses mapped from IP sources to two (multi-unicast) IP destinations (connections) .

● You can select the User Defined Profile and create a customized bus map configuration. For example, you can create a multi-unicast configuration, where one source is c onnected to more than two destinations. Section 4.3.3.4 – TDM Bus M apping Configuration gives additional mult i- unicast information.

Harris Corporation 2-11 Intraplex Products

NetXpress LX & CM-30 Installation & O p er ation Manual 2 – Functional Design Version 1, September 2010

2.6 System Time-of-Day

With the NetXpress LX system, ther e are two ways to set the s ystem time-of-day: 1) manually and 2) via NTP (Networ k Timing Protocol) server . If you choose the latter method, you m ust use the Web server interface to enable N TP in the NIM Configuration – General Setup screen and provide the IP address of the SNTP server (Section 4.3.3.1 – General Setup). The NetXpress LX system maintains the time and date in a battery-backed time-of-day clock on the CM-30 module.

2.7 System Timing

2.7.1 Types of System Timing

System timing is the process of s ynchronizing com munications and strea m traffic between two or more NetXpress LX systems in a network. Time synchroniz ation is critical to the proper functioning of the NetXpress LX network. It must be configured correctly.

The primary timing sour c e for all interconnected NetXpress LX systems should trace back to the same long-term accurate oscillator.

Primary and secondary timing are conf igu r ed via the Web interface using the System Timing screen (Section 4.3.3.5 – System Tim ing). You must specif y the timing source for both primary and secondary timing. If the primary timing source is unava ila b le, the system uses secondary timing. The NetXpress LX system provides four timing sources from which to choose:

● Internal

● External

● Stream

● SynchroCast

Timing can be sourced through the RS-422 Timing OUT port on the MIU-201 or MIU-202-2 to feed additional multip lexers.

2.7.1.1 Internal Timing

Internal timing is derived from an ex tr emely accurate inter nal oscillator on the CM-30 module. In a NetXpress LX network, only the m a ster NetXpress LX system can use inte r nal timing. Other NetXpress LX shelves in the network must use external, stream, or SynchroCast timing derived from the n etw or k master.

2.7.1.2 External Timing

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

2.7.1.3 Stream Timing

Stream timing is derived from the incom ing packet stream. A timing stream mus t have a packet rate of 8 packets per second or greater (1000 frames/packet or less). Th is typ e of timing uses an algorithm inherent in the TDMoIP chip. In a NetXpress LX network, only subordin a te NetXpress LX systems can be set to stream timing mode. Th e NetXpress LX master system monitors stream traffic and adjusts timing so that the su b or dinate shelves are s ynchronized with the master clock frequency. As a general rule; the faster the packet rate, the be tter the stream timing. With stream tim ing, jitter buffer size can be monitored and regulated to av oid bu ffer underflow/overflow a nd negate the effect of pack et delay

2-12 Harris Corporation Intraplex Produc ts

2 –Functional Design NetXpress LX & CM-30 Installation & O p er ation Man ual Version 1, September 2010

variation. Whe n a subordinate system derives timing from the master, clock recovery algorithms are employed to align c lock frequency an d c ontrol packet jitter/w ander. Also, in order to recover timin g from a stream, the stream must be active and sending. Networking or router problems can result in no timing recovery from a stream.

Note: When you configure several receive streams and use a stream as the timing source, you

should use the stream with the highest packet rate ( such as the lowest frames per payload value) as the primary timing stream.

2.7.1.4 SynchroCast3™ Timing

The SynchroCast3 system uses a simulcast technique which transmits to an extended geographic area using multiple, ov er lapping transmitters operating on the same frequency. Historically, broadcasts from nearby transmitters on the same frequency have crea ted s erious reception problems where they overlap. The SynchroCast system, or ig inally developed f or use in land mobile radio s ystems, makes simulcasting possible in FM broadcast as well. The SynchroCast system can provide dramatically increased station coverage while r ed ucing or eliminatin g unwanted artifacts at the listener’s receiver.

The SynchroCast3 system in the NetXpress LX multiplexer maintains the phase alignment of the transmitted signals using Global Position S ystem (GPS) tech nology, providing

● GPS controlled car r ier frequency sy nchronization.

● GPS controlled precision audio pha s e a lignment.

● Dynamic adjus tm e nts to compensate for network routing c hanges.

The SynchroCast3 system sends timing reference signals along with the a udio content to the transmitter sites. GPS receivers, placed at the Origination Point and transmitter sites, provide a timing reference. At the Transmitter, timing signals coming from the Origination Point (along with the audio content), are com p a r e d with the local timing reference and a p r ecise amount of delay is introduced to correct the timing differenc e between transport paths. Once the signals are synchronized, the system operates automatically to keep the preset delay constant. The Intraplex SynchroCast3 System Installation an d Operation Manu al gives more inform a tion on the SynchroCast3 system.

The SynchroC ast3 system carefully controls the receive jitter buffers as sociated with the IP streams, allowing multipl e loc a tions to deliver their stream data at pr ec isely the same instant. This control is essential for radios using multiple transmitters so that interference p r oblems associated with them can be minimized.

2.7.2 NetXpress LX Timing Scenarios

In a system that utilizes multiple NetXpress LX units de ployed on an IP network, it is important to maintain consis tent synchronization of the internal NetXpress LX system clocks. This synchronization ensures that any NetXpress LX system can receive streams generated by any other unit or a combination of s tr e a m s from any other units (Figure 2-4).

Harris Corporation 2-13 Intraplex Products

NetXpress LX & CM-30 Installation & O p er ation Manual 2 – Functional Design

INTERNAL

STREAM

Version 1, September 2010

NetXpress LX

Multicast Audio

Stream 1

NetXpress LX

Audio Stream 2

NetXpress LX units at sites A and C must have synchronized

NetXpress LX

system clocks so that the NetXpress LX unit at site D can properly receive and process its

Figure 2-4. NetXpress LX Timing Synchronization

NetXpress LX units can derive sys te m tim ing in one of four ways:

1. An internal clock is av a ila b le, based on a local osci llator within the u nit (Internal Timing ).

2. An external clock can be appli e d to the unit (Exter nal Timing).

3. An incoming IP unicast or mu ltic ast stream (Stream Timing), thereby synchronizing its e lf to the NetXpress LX unit that generated the stream.

4. SynchroCast, which incorporates a blend of Str eam and Extern al timing from GPS receivers.

Simple point-to-point sy s te m s commonly use a c om bination of intern a l and stream timing. Figure 2-5 shows the unit at s ite A set to internal timing, utilizing its local internal oscilla tor. The unit at Site B derives timing from the audio stream tra nsmitted from Site A to Site B.

TIMING

NetXpress LX

TIMING

NetXpress LX

Figure 2-5. NetXpress LX Point-to-point Timi ng Synchronizati on

The configuration advantage in Figure 2-5 is simp licity of implementation. No external timing sources are required. This configuration can be extended to multiple site systems by design a ting one site as the master timing loc a tion and having th e r est of the sites derive timing from that site. Figure 2-6 shows such a system, with Site A using internal timing a nd the remaining sites using stream timin g to achieve synch r onization to Site A.

2-14 Harris Corporation Intraplex Produc ts

2 –Functional Design NetXpress LX & CM-30 Installation & O p er ation Man ual

Stream Timing

NetXpress LX

Version 1, September 2010

Stream Timing

NetXpress LX

Internal Timing

NetXpress LX

Stream Timing

Sites B, C, and D use stream timing to derive timing from

NetXpress LX

master Site A.

Figure 2-6. Stream Ti ming Synchroni z a t ion

This method of timin g distribution c a n be very simple and efficient in cases where pr ogr amming streams are eman a ting from one master s ite to all the remaining sites. However, p r ogr amming may be generated at mu ltiple sites within the network, and these program source sites may not all receive program streams from the master site that can be used as timing sources (Figure 2-7). In this example, Site A is the master timing sou rce, but Site C does not receive a stream f rom Site A and therefore cannot synchronize its outgoing stream to the rest of the network. As a result, the two streams received at Site D utilize different synchronization sources and cannot be properly received and decoded.

Stream Timing

Internal Timing

NetXpress LX

Internal Timing

Site D cannot process both

NetXpress LX

incoming streams because they have different timing sources.

Figure 2-7. Streams with Different Synchroniz a t ion Sources

There are two possib le solutions to this s ituation.

1. Receive a stream at site C from Site A solely for the pur pose of synchroniz a tion (Figure 2-4). The cost of this solution is the additiona l b a ndwidth required in the network end-link to site C.

2. An alternative approach would be to utilize highly accurate exter nal timing sources at Sites A and C to achieve netw or k synchronization. One example would be a Stratum 1 traceable t im ing signal

Harris Corporation 2-15 Intraplex Products

NetXpress LX & CM-30 Installation & O p er ation Manual 2 – Functional Design

Version 1, September 2010

from a telecom networ k provider. An other source of accurate external timing signals is a GPS receiver, usin g GPS timing at the stream timing sites (F ig ure 2-8). This solution guara ntees the two streams received at site D have c ompatible timing, allowing Site D to time from either incoming stream.

Stream Timing

NetXpress LX

GPS

External Timing

NetXpress LX

External Timing

NetXpress LX

Site D can derive system timing from either incoming steam.

GPS

Figure 2-8. Timing Sy n chronization wit h GPS

In this case, th e fixed cost of purchasing and deploying G PS units at Sites A and C can be traded against the recu r r ing cost of bandwidth to r eceive a timing stream at Site C.

2.7.2.1 Backup Timing

In networks that generate revenue-critical programming, it may be prudent to design back up timing scenarios. Each NetXpress LX unit can be programmed to switch to an alternative timing source in the case of primary tim ing signal loss. If the primary timing s ource is an incomin g stre a m , for example, the secondary source cou ld be a dif ferent stream; either an a udio stream or a dedicated timing stream. Another scenario could use Stratum -1 or GPS as the primary tim ing source with stream timing as the backup. Once again, the trade-off w ould be the one-time cost of GPS receivers or Str atum-1 timing sources versus the recur r ing cost of bandwidt h for the backup timin g s ig nal. If both the prima r y and secondary timing sources fail, the NetXpress LX unit falls bac k to internal timing.

Sites that are receive-only can usually utilize stream tim ing since they only need to be synchron ized during the time they are receiving a stream. If receive stream s a t a r ec eiv e-only site are changed frequently, there could be an operational advanta g e to using external (stratum-1 or GPS) timing, in that the operator would not need to consider whether or not a r eceive signal is presen t.

Certain receive sites may also gen era te off-air monitor s treams back into the network (Figure 2-9). A logical choice for timing in this netw or k would be to use internal timing at Site A and stream timing at Sites B and C. In th is case, if the audio stream to Site C is lost, the monitoring stream ba ck from Site C is not properly tim e d for reception at other network sites, which can result in periodic jitter buffer underflow or ove r flow at the receiver w ith each event caus ing a brief interruption or audio glitch. If it is important to main tain smooth contin uous reception of this off-air monitoring stream during periods of primary stream loss, an external timing source or a backup timing stream is needed at Site C.

2-16 Harris Corporation Intraplex Produc ts

2 –Functional Design NetXpress LX & CM-30 Installation & O p er ation Man ual

Version 1, September 2010

Internal Timing

NetXpress LX

Audio Stream

Monitor Stream

Stream

Timing

NetXpress LX

Monitor Stream

Audio Stream

Audio

Stream Timing

NetXpress LX

Off-air monitor

audio

Audio

Off-air monitor

audio

Figure 2-9. Timing wi t h Off-Air Monitor Stream s

2.7.2.2 Timing Summary

NetXpress LX units that generate s tr e a m s into the network should share a comm on timing reference to guarantee that a ny NetXpress LX unit can receive or monitor any stream in the network. You can use stream timing, external ( Stratum-1 or GPS) tim ing, or a combination of the two. In cases where audio streams are already present and can be used as timing sources, stream timing is essentially “free.” If a dedicated timing stream must be added, the recurring cost of the stream bandw idth c a n be traded off agains t the one-time cost of implementing GP S receivers.

You should also consider timing failure scenarios. I d ea lly, a fallback timing source should be a vailable at each site that ke ep s that site in synch r onization with the other s ites even if its prima r y timing source fails. Once again, the backup source can be either a stream or an external input (Stratum-1 or GPS) with the corr esponding cost trade-off.

2.8 NetXpress LX System and FEC

The NetXpress LX system maintains uninterrupted audio transport by supporti ng Forward Error Correction (FEC). Specifically, the NetXpress LX system supports RFC 2733. Forward error correction is the process obta ining error control in data transmission in which the source (transmitter) s e nds redundant data a nd the destination ( receiver) recogn izes only the portion of the data that contains no apparent errors.

An FEC packet is a special type of RTP packet. It is constructed by placing an FEC header and FEC payload in the RTP payload.

In the NetXpress LX system, up to 32 streams (16 in each direction) can be designated as FEC streams. For each of the FEC streams, you can specify either of two techniques f or forward error correction: FEC LOW or FEC HIGH (Section 4.3.5.1 – Stream Creation). This specification affects the sender only. The receiv er process es a ll F E C packets.

FEC LOW (appropriate for most low packet loss c onditions)

Single error correction is engaged. This scheme introduc es a 50% overhead (increased bandwidth required) and can correct all single packet losses – consecutive packets are not lost.

Harris Corporation 2-17 Intraplex Products

NetXpress LX & CM-30 Installation & O p er ation Manual 2 – Functional Design Version 1, September 2010

FEC HIGH (used in more serious pac ket loss conditions)

Triple error correction is engaged. This scheme introduces a 100% overhead (increased ba ndwidth required) and can correct on e, two, or three consecutive packet losses. In this scheme, the packet sequence sent is critical if it is to protect against consec utive packet losses.

Table 2-3 shows the NetXpress LX performance data, with an overall loss rate and a percentage of high versus low F EC loss.

Table 2-3. NetXpress LX FEC Performance Da ta

Network

Loss

Rate

(%)

1 0.0017 0.027 2 0.0023 0.085 3 4 5 0.0168 0.507 6 7 8

9 10 0.14 2.1 11 12 13 14 15 0.597 4.87

High

FEC

Loss

(%)

Low

FEC

Loss

(%)

% High FEC Loss ((Lost packets / Rx packets) x 2) x 100 % Low FEC Loss ((Lost packets / Rx packets) x 1.5) x 100

2.9 Power

The NetXpress LX-300 system supports redundant power supplies. You can install a main power supply and a redundant supply in c a s e the main supply fails. The system r uns on either AC or DC power supplies, and suppo r ts 60 W a nd 100 W AC powered and 50 W DC powered supplies. (Section

3.2.4 – Power Supply Installation gives more information on NetXpress LX power supplies.)

2.10 Voice Signaling

Voice signaling communicates voice channel call progress information over a data link. The information, k nown as ABCD bits (or E & M) includes busy, idle, or othe r r inging state indications to alert the caller that a call is taking place. Two types of voic e signaling are robbed -bit signaling (RBS) and channel associated signaling (CAS).

2.10.1 RBS

T1 systems use the RBS method of channel signaling. T his information is em b edded into the least significant bit of the audio channe l once every 6th frame and injected into the channel without regard to the remaining bi ts. Therefore, RBS does dis tor t the voice audio signal so slightly tha t you can only

2-18 Harris Corporation Intraplex Produc ts

2 –Functional Design NetXpress LX & CM-30 Installation & O p er ation Man ual Version 1, September 2010

perceive it by distortion measurements . RBS signaling su pp or t s hould not be used on channels carrying information other than voice audio as it corrup ts the data in the channel.

2.10.2 CAS

E1 systems use CAS to carry voice call information. Instead of embedd ing this informa tion in the same channel as the v oice audio, channel 16 of the E1 is reserved for a ll of the remaining channels to use for signaling.

2.11 Software Download

During normal oper a tion, the CM-30 module loads the primary image. Should it fail to boot the primary image, the module then attempts to load the secondary im a g e.

In the case of a failure in loading both the primary and secondary ima ge, you can configure the CM-30 module to load an image from a remote FTP server. This imag e is not saved to either of the flash memory devices. You can also configu re the module to loa d the secondary image first, but if that f a ils , the module moves directly to loading from the remote FTP server and does not try to load the primary image.

When shipped from the factory , the CM-30 IP interfa ce m odule contains the most recent version of the system software. As new features and improvements become a v a ila ble, the CM-30 module software should be updated to the most cur rent revision.

The CM-30 software can be upgraded by opening an F TP session with the module and transferring a new image file to the flash memory device. You can configure both the pr ima r y and secondary images to be loaded from the same file or from two differen t file images. In addition , you can store mu ltip le software images on the CM-30 module 1 up to the lim it of the flash memory . To obtain the softwa re and boot ROM downloa d process in the latest version’s releas e notes, perform these steps:

1. Go to

2. On the menu bar, point to Services & Support and click Client Support Portal.

3. Log onto the support site.

http://www.broadcast.harris.com/

4. At Self Se rv ice, click Download Softwa r e Updates.

5. Click Intraplex | NetXpr ess LX.

6. Click the link for the most rec ent NetXpress LX ver sion.

7. Click Save on the dialog box and save the zipped file to your hard drive.

8. Open the zipped file and open the release notes.

2.12 Configuration Files Backup and Restoration

The CM-30 module has the ability to back up and restore configuration files a t any time using e ither the Web browser interface or SNMP software. CM-30 module con figuration is stored in multiple files on the flash memory (/RFA/cfg). Backup/restoration ability is critical to replacing CM-30 modules. It also facilitates in th e r ep lic ation of NetXpress LX systems across a network.

Once a CM-30 module is removed from a NetXpress LX she lf, the persistent con figuration inform a tion for the system rem ains with the CM-30 module an d is not available to a n e w module inserted in the system. This s ame information can be r estored quickly fr om an FTP server (via Inte r net) to the flash memory on the new CM-30 module. The information can also be backed up easily to the server using the same process, only in reverse order. Restored configuration takes effect when the CM-30 module is rebooted.

Harris Corporation 2-19 Intraplex Products

NetXpress LX & CM-30 Installation & O p er ation Manual 2 – Functional Design Version 1, September 2010

2.13 Fault Detection and Reporting

With the use of S NMP traps, the CM-30 system ha s the ability to detect an d r e port on a number of alarm conditions .

2.13.1 Alarm Hierarchy

The CM-30 system has major and minor alarms. A major alarm is a fault that has a direct effect on service, such a s a c om ponent failure disrupting the delivery or reception of data. A minor alarm is a fault that has no effect on service, in cluding all other err or s detected which do not affect CM-30 operation.

The CM-30 system is also equipped with an alarm cutof f (ACO) switch. The ACO is a switch that can be enabled to reduc e the major alarm outpu t s ig nal to a minor alarm output as an over-ride until the situation can be corrected.

The indicator lights on the front panel of the NetXpress LX or original Intraplex power s upply modules and on the NetXpress LX Home page give system alarm states (Section 4.3.1 – Start at the NetXpress LX Home Page):

● Red light = Major shelf alarm (Alarm)

● Yellow light = Minor shelf alarm (Alert)

● Green light = No alarm condition exists (Normal)

2.13.2 Alarm History

You can review current alarms and alarm history from the NetXpress LX Home page. G o to Faults | Alarm Table to display the Current Alarms screen or Faults | Alarm History to display the Alarm History screen. Both screens contain this data:

● A list of alarms

● Dates and times the alarms occurred

● Severity of the alar m s

● A description of each alarm occurrence

For troubleshooting and futu r e r ef er ence, you can also off -load he NetXpress LX system alarm history to a text file.

2.13.3 SNMP Traps Use for Fault Reporting

SNMP traps detect and report system faults. System events that generate SNMP traps include stateful events (considered ON/OFF alarm events) and informational events (non-alarm, one-time-only events).

Equipment-related system events indicate a hardware failur e on the CM-30 module or in the shelf. Processing-related system events indica te a failure was detected in software processing. Facilityrelated system ev e nts indicate a failure occurred with one of the operation interfaces.

The available list of SNMP traps changes with each software version. The Notification section in the MIB file supplied with you r version of CM-30 applica tion software gives a list of available SNMP traps.

2-20 Harris Corporation Intraplex Produc ts

+ 127 hidden pages

Harris CM-30, MA-230 Installation & Operation Manual

Specifications and Main Features

Frequently Asked Questions

User Manual