Intraplex® NetXpress™ IP Multiplexer Installation & Operation Manual

Installation and Operation Manual

Intraplex® NetXpress™ IP Multiplexer NetXpress™ IP Multiplexer (3RU) NIM-1 Network Interface Module MIU-201 Module Interface Unit MIU-202 Module Interface Unit

Version 3.05

Publication Information ©2014 GatesAir, Inc. . Proprietary and Confidential. GatesAir considers this document and its contents to be proprietary and confidential. Except for making a reasonable number of copies for your own internal use, you may not reproduce this publication, or any part thereof, in any form, by any method, for any purpose, or in any language other than English without the written consent of GatesAir. All others uses are illegal. This publication is designed to assist in the use of the product as it exists on the date of publication of this manual, and may not reflect the product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the product to which it refers. GatesAir reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product. GatesAir reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product.

Trademarks ®

®

®

®

AudioLink PLUS™, HD Link™, IntraGuide , Intraplex , NetXpress™, NetXpress LX™, STL PLUS , SynchroCast , and SynchroCast3™ are trademarks of GatesAir Corporation. Other trademarks are the property of their respective owners.

Customer Service Contact Information www.gatesair.com GatesAir 3200 Wismann Lane Quincy, Il 62305 USA For Technical Support including Service, Training, Repair and Service Parts:

www.gatesair.com/services/technical-support.aspx Americas: 24/7 Technical Support

+1 217 222 8200

Email

[email protected]

Europe, Middle East and Africa: 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

3.05

11/27/12

3.04*

3.03*

Revisions Made

Editor

Updated all figures of rear panel with correct power supplies.

LD

2/21/12

Corrected Table 3-6 Pin 1 and 2 assignments for T1/E1 ports. Various other corrections

LD

7/15/11

Updated Quick Start Guide with various interface naming changes,

LD

Updated TDM bus information, added automated TDM bus mapping, IGMP auto recovery, and WAN port mirror to New Feature section, updated Software Download procedure, and clarified SNMP Traps Use for Fault Reporting first paragraph; Updated Stream Creation procedure steps 3.02*

5/25/10

Added VF-40 module to Table 2-2 and put table on one page.

LD

Added RFC2733 to FEC spec and streaming with RFC5086. 3.01*

3.0

7/01/08

5/07/08

Revised Table 2-2 (NetXpress-supported TDM Channel Cards). Added missing TDM channel cards; removed VF-17E, VF-18AE, PTD-353, and PTR-353; added note for VF-27 and VF-27E; and repaginated the rest of the section. Added T1 and E1 specs to Specifications section and repaginated the rest of the section.

LD

Put entire manual into new template, reformatted, and updated for release.

LD

*Version numbers usually correspond to software releases. If the manual versions differ in number from the release, the front page shows both the manual version and the release version.

No header

Table of Contents NetXpress Quick Start Guide .......................................................... vii Section 1 – Introduction ................................................................ 1-1 1.1 Features .......................................................................................... 1-1 1.2 Applications ..................................................................................... 1-2 1.3 Manual Scope ................................................................................... 1-2 1.4 Manual Use ...................................................................................... 1-2 1.5 NetXpress Components...................................................................... 1-2 1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.5.6 1.5.7 1.5.8 1.5.9

Main Equipment Shelf .............................................................................1-2 TDM Channel Modules ............................................................................1-3 Channel Access Modules (CAMs) ..............................................................1-3 Network Interface Modules (NIMs) ...........................................................1-4 Module Adapters ....................................................................................1-4 Module Interface Unit (MIU) - 201............................................................1-4 MIU-202 ...............................................................................................1-4 Power Supplies ......................................................................................1-5 Indicator Lights .....................................................................................1-5

1.6 NetXpress Software .......................................................................... 1-6

Section 2 – Functional Design ........................................................ 2-1 2.1 Network Concepts and Considerations ................................................. 2-1 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.1.7

MTU throughout the Network ...................................................................2-1 DHCP Use .............................................................................................2-1 Routing Table Construction .....................................................................2-1 WAN and LAN Port Auto-negotiation .........................................................2-2 NetXpress ICMP Support .........................................................................2-2 Redundant WAN Link Configuration ..........................................................2-2 IGMP Multicast.......................................................................................2-3

2.2 Streams........................................................................................... 2-3 2.2.1 Stream Types ........................................................................................2-3 2.2.2 Protocol Stack for TDM-based Streams .....................................................2-4 2.2.3 Stream Addressing .................................................................................2-4 2.2.4 Multicast Group Addressing .....................................................................2-5 2.2.5 Media Switch Map ..................................................................................2-5 2.2.6 IGMP Auto Recovery ...............................................................................2-6 2.2.7 Telephony .............................................................................................2-7 2.2.8 Echo Cancellation ...................................................................................2-7 2.2.9 Packetization and Overhead ....................................................................2-7 2.2.10 Packet Jitter Compensation ...................................................................2-8 2.2.11 Packet /Stream Information Calculation ..................................................2-8 2.2.12 Stream Statistics..................................................................................2-9

2.3 System Security ............................................................................... 2-9 2.3.1 NetXpress Logon .................................................................................. 2-10 2.3.2 Management Protocols on an Interface ................................................... 2-10 2.3.3 IP Access List Use ................................................................................ 2-10 GatesAir, Inc. Intraplex Products

i

Intraplex NetXpress IP Multiplexer Version 3.05

Table of Contents

2.3.4 SNMP Communities .............................................................................. 2-10

2.4 NetXpress QoS ............................................................................... 2-10 2.4.1 COS Levels for Stream Data .................................................................. 2-11 2.4.2 TOS Byte Marking for Outbound Stream Packets ...................................... 2-11 2.4.3 User-defined TOS Byte Setting for Outbound SNMP and HTTP Packets ........ 2-11

2.5 NetXpress Internal TDM Busses ........................................................ 2-11 2.5.1 Compatibility with Intraplex TDM Channel Modules................................... 2-11 2.5.2 TDM Channel Loopbacks ....................................................................... 2-13 2.5.3 TDM Bus Mapping ................................................................................ 2-13

2.6 System Time-of-Day ....................................................................... 2-14 2.7 System Timing ............................................................................... 2-14 2.7.1 Types of System Timing........................................................................ 2-14 2.7.2 NetXpress Timing Scenarios .................................................................. 2-15

2.8 NetXpress System and FEC .............................................................. 2-19 2.9 Power ............................................................................................ 2-19 2.10 Voice Signaling ............................................................................. 2-20 2.10.1 RBS .................................................................................................. 2-20 2.10.2 CAS .................................................................................................. 2-20

2.11 ObjectVideo® Software ................................................................... 2-20 2.12 Network Interface Module (NIM) Redundancy ................................... 2-20 2.13 Software Download ....................................................................... 2-21 2.14 Configuration Files Backup and Restoration ...................................... 2-21 2.15 Fault Detection and Reporting ......................................................... 2-22 2.15.1 Alarm Hierarchy ................................................................................. 2-22 2.15.2 Alarm History .................................................................................... 2-22 2.15.3 SNMP Traps Use for Fault Reporting ..................................................... 2-22

Section 3 – Installation, Wiring, and Setup ................................... 3-1 3.1 Tool and Cable Requirements ............................................................. 3-1 3.2 NetXpress Equipment Unpacking and Installation .................................. 3-1 3.3 NetXpress Shelf Installation ............................................................... 3-2 3.4 NIM-1 Installation ............................................................................. 3-2 3.5 Secondary NIM-1 Installation ............................................................. 3-4 3.6 MIU-201 Installation and Connection with NIM-1 .................................. 3-4 3.7 MIU-202 Installation ......................................................................... 3-4 3.8 TDM Channel Module and Channel Access Module Installation................. 3-5 3.8.1 3.8.2 3.8.3 3.8.4

ii

Module Adapter Installation .....................................................................3-5 Remote Control Operation .......................................................................3-5 SCB Address Selection ............................................................................3-5 Channel Module Insertion ........................................................................3-6

GatesAir, Inc. Intraplex Products

Table of Contents


3.9 Power Supplies Installation ................................................................ 3-7 3.10 Wiring and External Connections ....................................................... 3-8 3.10.1 3.10.2 3.10.3 3.10.4

Power Connections ...............................................................................3-8 Alarms .............................................................................................. 3-10 MIU-201 Connections and Wiring ......................................................... 3-11 MIU-202 Connections and Wiring ......................................................... 3-14

3.11 Unit Powering ............................................................................... 3-14

Section 4 – System Configuration and Operation .......................... 4-1 4.1 Software Downloads ......................................................................... 4-1 4.1.1 Download Current Software .....................................................................4-1 4.1.2 Download Current Software with NIM Redundancy .....................................4-1

4.2 NetXpress Configuration Procedures .................................................... 4-2 4.2.1 Connect and Log On to Access NetXpress Home Page .................................4-2 4.2.2 View System Mode .................................................................................4-2 4.2.3 Perform General Setup ...........................................................................4-3

4.3 Network Interface Module (NIM) Redundancy ..................................... 4-16 4.3.1 Redundancy Terms............................................................................... 4-16 4.3.2 Redundancy Capabilities ....................................................................... 4-16 4.3.3 Redundancy Synchronization ................................................................. 4-16

4.4 NetXpress Pages ............................................................................. 4-17 4.4.1 Start at NetXpress Home Page ............................................................... 4-17 4.4.2 Define and Review Fault Information ...................................................... 4-19 4.4.3 Configure the System ........................................................................... 4-23 4.4.4 Configure the Network ......................................................................... 4-41 4.4.5 Configure Streams ............................................................................... 4-49 4.4.6 Check Multiplexer Performance .............................................................. 4-60 4.4.7 Set Up Accounts .................................................................................. 4-73 4.4.8 Send Echo Requests ............................................................................. 4-74 4.4.9 View Power Supply Information ............................................................. 4-74 4.4.10 Configure Primary/Secondary Network Interface Module (NIM) ................ 4-76 4.4.11 Configure Individual Modules (TDM Modules and CAMs) .......................... 4-81

Section 5 – Frequently Asked Questions ........................................ 5-1 Section 6 – NetXpress Specifications ............................................. 6-1 6.1 Detailed Specifications ....................................................................... 6-1 6.2 Notice of FCC Compliance .................................................................. 6-3 6.2.1 Compliance with FCC Part 15 Requirements ..............................................6-3 6.2.2 Compliance with FCC Part 68 Requirements ..............................................6-3

Section 7 – Glossary ...................................................................... 7-1


iii


Table of Contents

Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure iv

1-1 1-2 1-3 1-4 1-5 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 4-1 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10 4-11 4-12 4-13 4-14 4-15 4-16 4-17 4-18 4-19 4-20 4-21 4-22

MIU-201 Module Interface Unit Panel .......................................................1-4 NetXpress System Status Indicators ........................................................1-5 Front View of the NetXpress Shelf without Cover .......................................1-5 Rear View of the NetXpress Shelf – AC or AC/DC Powered ..........................1-5 Multi-shelf NetXpress System Network .....................................................1-6 Carrier Multicast Backbone Example .........................................................2-5 Media Switching on Incoming Media Stream ..............................................2-6 Media Switching of a Stream to Multiple Destinations .................................2-6 NetXpress Web-Interface Logon Screen .................................................. 2-10 TDM Loopback Scenarios ...................................................................... 2-13 Timing Synchronization ........................................................................ 2-15 Point-to-point Timing Synchronization .................................................... 2-16 Stream Timing Synchronization ............................................................. 2-16 Streams with Different Synchronization Sources ...................................... 2-17 Timing Synchronization with GPS ........................................................... 2-17 Timing with Off-Air Monitor Streams ...................................................... 2-18 NetXpress Equipment Shelf with Thumbscrews ..........................................3-2 NetXpress NIM-1 Module and Indicator Lights ...........................................3-3 NetXpress NIM-1 and MIU-201 Midplane Insertion .....................................3-4 Front View of NetXpress Shelf with Cover Removed ...................................3-5 Side View – TDM Channel Module and Module Adapter Insertion ..................3-6 Rear Panel of NetXpress Shelf .................................................................3-8 Connections for AC and AC/DC Operation .................................................3-8 Rear Panel of NetXpress Shelf .................................................................3-9 Connection for DC Operation ................................................................. 3-10 Connection for DC Operation Using Dual Power Supply Setup .................... 3-10 DC Power & Alarm Connectors ............................................................... 3-11 NetXpress MIU-201 .............................................................................. 3-12 NetXpress Home Page ............................................................................4-2 Networking | IP Routing Table .................................................................4-3 IP Routing Table | Create a New Route Page .............................................4-4 Networking | IP Access List .....................................................................4-4 IP Access List | Create IP Access List Entry Page .......................................4-4 System Cfg | TDM Bus Information Page ..................................................4-5 System Cfg | Software Load Image Configuration Page ..............................4-6 System Cfg | Interfaces Table – Port A Configuration .................................4-7 Streams Page........................................................................................4-8 Streams | Stream Creation – Stage 1 Page ...............................................4-8 Streams | Stream Creation – Stage 1 (TDM to TDM) Page ..........................4-9 Stream Creation – Stage 2 (TDM to TDM) Page .........................................4-9 Stream Creation Summary (TDM to TDM) Page ....................................... 4-10 Stream Creation – Stage 2 (TDM to IP) Page........................................... 4-11 Stream Creation – Stage 3 (TDM to IP) Page........................................... 4-11 Stream Creation – Stage 4 (TDM to IP) Page........................................... 4-12 Stream Creation Summary (TDM to IP) Page .......................................... 4-13 System Cfg | System Timing Page ......................................................... 4-14 Networking | SNMP Configuration Page .................................................. 4-15 System Cfg | Configuration Files Backup/Restore Page ............................. 4-15 NetXpress Home Page .......................................................................... 4-18 Current Alarms Page ............................................................................ 4-20 GatesAir, Inc. Intraplex Products

Table of Contents

Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure

4-23 4-24 4-25 4-26 4-27 4-28 4-29 4-30 4-31 4-32 4-33 4-34 4-35 4-36 4-37 4-38 4-39 4-40 4-41 4-42 4-43 4-44 4-45 4-46 4-47 4-48 4-49 4-50 4-51 4-52 4-53 4-54 4-55 4-56 4-57 4-58 4-59 4-60 4-61 4-62 4-63 4-64 4-65 4-66 4-67 4-68 4-69 4-70 4-71 4-72 4-73 4-74 4-75


Alarm Definitions Page ......................................................................... 4-20 Alarm Definition Edit Page .................................................................... 4-21 Alarm History Page .............................................................................. 4-21 Remote Log Server Page ...................................................................... 4-22 System Log Files Page .......................................................................... 4-22 General Setup Page ............................................................................. 4-24 Interfaces Table .................................................................................. 4-25 E1 Interfaces Table .............................................................................. 4-27 T1 Interfaces Table .............................................................................. 4-28 TDM Bus Information Page ................................................................... 4-30 Changes to System Mode Dialog Box ..................................................... 4-31 TDM Bus Configuration Edit Page ........................................................... 4-31 Media Switch Map Page – E1 Mode ........................................................ 4-33 System Timing Page ............................................................................ 4-34 System TOS Byte Definitions Page ......................................................... 4-36 Software Load Image Configuration Page................................................ 4-37 Configuration Files Backup/Restore ........................................................ 4-39 Redundancy Configuration Page ............................................................ 4-40 Redundancy System Synchronization Page ............................................. 4-41 Network Interface Configuration Page .................................................... 4-42 WAN Network Interface Configuration Page............................................. 4-43 LAN Network Interface Configuration Page .............................................. 4-44 IP Routing Table .................................................................................. 4-45 Create a New Route ............................................................................. 4-45 IP Access List ...................................................................................... 4-46 Create IP Access List Entry Page ............................................................ 4-46 SNMP Configuration Page ..................................................................... 4-47 UDP Listener Table .............................................................................. 4-47 TCP Connection Table........................................................................... 4-48 ARP Table ........................................................................................... 4-48 Streams Page...................................................................................... 4-49 Stream Creation – Stage 1 Page (TDM to IP)........................................... 4-51 Stream Creation – Stage 1 Page (TDM to TDM) ....................................... 4-51 Stream Creation – Stage 2 (TDM to IP) Page........................................... 4-52 Stream Creation – Stage 3 (TDM to IP) Page........................................... 4-53 Stream Creation – Stage 4 (TDM to IP) Page........................................... 4-54 Stream Creation Summary (TDM to IP) Page .......................................... 4-55 Stream Creation – Stage 2 (TDM to TDM) Page ....................................... 4-56 Stream Creation Summary (TDM to TDM) Page ....................................... 4-57 Streams Page...................................................................................... 4-58 TDM to IP Stream Edit Page .................................................................. 4-59 TDM to TDM Stream Edit Page ............................................................... 4-59 Stream Statistics Page ......................................................................... 4-60 Performance History Page ..................................................................... 4-61 Voice Signaling Statistics Page .............................................................. 4-62 E1 Port Statistics Page ......................................................................... 4-62 T1 Port Statistics Page ......................................................................... 4-63 Port Statistics Intervals Page – E1 Near End ........................................... 4-63 Port Statistics Intervals Page – T1 Near End............................................ 4-63 SNMP Statistics Page............................................................................ 4-65 UDP Statistics Page .............................................................................. 4-67 TCP Statistics Page .............................................................................. 4-67 ICMP Statistics Page ............................................................................ 4-69


v


Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure

4-76 4-77 4-78 4-79 4-80 4-81 4-82 4-83 4-84 4-85 4-86 4-87 4-88 4-89 4-90 4-91 4-92 4-93

Table of Contents

IGMP Statistics Page ............................................................................ 4-71 IP Statistics Page ................................................................................. 4-72 Accounts Configuration Pages ............................................................... 4-73 Ping Utility Page .................................................................................. 4-74 Standard Power Supply Page................................................................. 4-74 200W-AC Power Supply Configuration Page ............................................ 4-75 NIM-1 Network Interface Module: General Page ...................................... 4-77 NIM-1 Network Interface Module: Revisions Page .................................... 4-78 NIM-1 Network Interface Module: Program Boot ROM Page ....................... 4-79 NIM-1 Network Interface Module: MIU-201 Page ..................................... 4-80 DA-91A Configuration Page ................................................................... 4-81 DA-91A Status Page............................................................................. 4-81 PT-353 Configuration Page.................................................................... 4-82 PT-353 Status Page ............................................................................. 4-83 VF-25E Configuration Page ................................................................... 4-85 VF-25E Status Page ............................................................................. 4-86 DS-64NC Configuration Page ................................................................ 4-87 DS-64NC Status Page .......................................................................... 4-89

Tables Table Table Table Table Table Table Table Table Table Table Table Table Table

vi

2-1 2-2 2-3 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 4-1 5-1

NetXpress Stream User and Computed Parameters ......................................2-9 NetXpress-supported TDM Channel Modules with Nominal Power.................. 2-12 NetXpress FEC Performance Data ............................................................. 2-19 NIM-1 Switch Settings (S3 Location) ..........................................................3-3 SCB Switch Settings for TDM Channel Modules.............................................3-6 System Indicator Lights ............................................................................3-7 Power and Alarm Connectors ................................................................... 3-11 Pin Assignments for the LAN/WAN/MGMT Ports .......................................... 3-13 Pin Assignments for the T1/E1 Ports ......................................................... 3-13 Pin Assignments for the MIU-201 External Timing In Port ............................ 3-14 Pin Assignments for the MIU-201 Timing Out Port ...................................... 3-14 States Associated with Streams ............................................................... 4-50 SCB Switch Settings .................................................................................5-2


No header here

Section 1 – Introduction GatesAir Intraplex NetXpress IP multiplexer represents the next generation in IP transport systems. This robust multiplexing server provides efficient transport and managed control of real time payloads (voice, audio, video, and data) over IP networks. The system’s capabilities enable your organization to leverage existing LANs and WANs, public packet switched networks, corporate intranets, and the Internet. The NetXpress platform provides a smooth transition from circuit switched to packet switched networks without requiring an overhaul of your existing infrastructure.

1.1 Features Key features of the NetXpress system include ●

Built-in optimization for robust streaming

●

Increased bandwidth capacity for multi-channel operation, consolidation, and program sharing

●

Precise management of services (audio, voice, data) for links over multiple networks (TDM/IP)

●

Packet delay jitter compensation with adjustable jitter buffer (up to 128 packets)

●

Adjustable packet sizing

●

Priority tagging for critical traffic routing

●

QoS (Quality of Service) Prioritization

●

Standard 19-inch (3RU) rack-mountable chassis

●

Definable alarms and alarm history

●

Forward Error Correction (FEC) for up to 20 streams

●

Configuration backup and restore

●

Downloadable software upgrades

●

Internal, external, and adaptive (stream) timing

●

Four internal TDM busses for utilization of existing Intraplex channel modules

●

Automatic TDM bus mapping

●

Hot-swappable modules

●

High-Speed Packet Bus for the transport of high bandwidth services such as video

●

Two external T1/E1 ports for TDM-to-TDM or TDM-over-IP transport services

●

Multiple independent unicast or multicast IP streams (create up to 32 full duplex streams)

●

Compatibility with Intraplex T1 and E1 multiplexers and cross-connect equipment

●

MPEG4/H.264 two-channel video compression boards with ObjectVideo® OnBoard 4.0.1 analytics software

●

Redundant Network Interface Module (NIM)

●

Redundant power supplies

●

Allows configuration and status monitoring from SNMP-based network management systems

●

Web browser user interface

●

Stream statistics tracking and reporting

●

SynchroCast3 simulcasting over IP


1-1


1—Introduction

1.2 Applications The NetXpress IP multiplexing solution includes these applications: ●

Broadcast Audio Distribution: Contribution and Distribution networks, Studio-to-Transmitter (STL) and Transmitter-to-Studio (TSL) links, Inter-studio communications, production feeds, and transport backup.

●

Private and Enterprise Networks: Audio and video program distribution, data link overlays, and consolidation of real-time and packet network facilities.

●

Land Mobile Radio: Migration to next generation network topologies, inter-site transport of encrypted and clear channel voice, and support for legacy data protocols.

●

xDSL Based Broadcast: Take advantage of digital subscriber line technology for audio distribution and reduce transmitter costs.

●

TDM over IP: TDM over IP can significantly reduce recurring costs by consolidating T1/E1 circuit traffic.

●

Legacy Data Communications via IP: Synchronous or asynchronous data communications.

●

Campus / Corporate A/V over IP: Audio and video program distribution, data link overlays, and consolidation of real-time and packet network facilities.

●

Surveillance over IP: Cost-effective video distribution via WAN.

●

Mobile Video Infrastructure: IP network video distribution to portable video devices.

1.3 Manual Scope This manual is the primary reference document for installing, configuring, operating, and troubleshooting the NetXpress IP Multiplexer system. If you have additional questions pertaining to the operation of your Intraplex system, you can call Networking Customer Service 24 hours daily at (217) 222-8200 or send an e-mail to [email protected].

1.4 Manual Use The manual “Table of Contents” shows locations for specific topic information. For general information, use these guidelines: ●

Readers unfamiliar with the NetXpress IP Multiplexer System – Use this manual as a tutorial. Read or skim all sections in order.

●

Installers – If you are already familiar with the NetXpress system, finish reading this section and go directly to Section 3 – “Installation and Wiring,” for step-by-step installation instructions.

●

Transmission and Planning Engineers – NetXpress operation and configuration overview is in Section 2 – “Functional Design” and specific guidelines are in Section 4 – “System Configuration.” Output, power, and other specification information can be found in Section 6 – “Specifications.”

●

Maintenance Technicians – Section 5 – “Troubleshooting/Frequently Asked Questions” gives troubleshooting information and guidelines. Individual channel module setup and test procedures can be found in the manuals for the modules shipped with your system.

1.5 NetXpress Components 1.5.1

Main Equipment Shelf

The NetXpress chassis is a 19-inch wide, 5 1/4-inch high (3RU) rack-mount equipment shelf. The shelf is equipped with slots for plug-in TDM Channel Modules, Channel Access Modules (CAMs), Network Interface Modules (NIMs), Module Adapters, Module Interface Units (MIUs), and power supplies (Figure 1-3). 1-2


1—Introduction

1.5.2


TDM Channel Modules

Up to 12 Intraplex TDM channel modules can be plugged into the 3RU NetXpress shelf for voice, data, high-fidelity audio, and video applications. Each channel module may terminate one or more payload circuits. There are four internal TDM busses (totaling up to 8 Mbps in E1 mode or 6 Mbps in T1 mode). Each slot can access two of the four busses. Slots 1 through 6 can access TDM1A and TDM1B. Slots 7 through 12 can access TDM2A and TDM2B. The NetXpress system supports existing channel modules used in GatesAir Intraplex Access Server models (ACS-160 series and ACS-260 series, as well as STL Plus and AudioLink Plus). ●

Voice Modules: Voice modules provide digital transport of telephony, fax and modem circuits. Signaling options include E&M Types I, II, III, V, loop start/ground start, ARD, and transmit only, which provide these voice capabilities: • • • •

●

Data Modules: Data modules provide digital transport of one-way or full-duplex data circuits, supporting a variety of data rates and formats including synchronous, asynchronous, and plesiochronous (almost synchronous) and providing these data capabilities: • • • •

●

High-speed synchronous data up to 2 Mbps for E1 and 1.5 Mbps for T1 for 10Base LAN, V.35, X.21, RS-449 and TTL, optionally decoupled from the network timing 10BaseT Ethernet LAN bridging Four-port asynchronous data up to 38.4 kbps for RS-232 and RS-449 Five-port synchronous data up to 19.2 kbps for RS-232

Program Audio Modules: Program audio modules provide digital transport for signals up to 22.5 kHz stereo. They are available with analog or AES/EBU input or output and provide these audio capabilities: • • • •

●

2-wire Foreign Exchange Office (FXO/FXS) PCM and ADPCM voice 2-wire and 4-wire E&M PCM and ADPCM voice Wideband 7.5 kHz voice Motorola SECURENET™ secure digital voice

Linear, uncompressed 22 kHz stereo audio with minimum delay Enhanced apt-X100 4:1 compressed audio for signals up to 20 kHz stereo with low delay ITU-T J.41 audio that employs 14:11 and 15:11 instantaneous companding Full-duplex codec modules that provide MPEG Layer 2 and Layer 3 (MP3) compressed audio for the highest fidelity stereo audio relative to bandwidth

Video Modules: Video codec modules support MPEG-4 and H.264 compliant video encoding in both unicast and multicast streams. Applications for these modules include surveillance, remote monitoring, and video distribution and provide these video capabilities: • • • •

1.5.3

NTSC and PAL video inputs Encoder and decoder configurations 64 kbps – 3Mbps Optional video analytics for automated surveillance

Channel Access Modules (CAMs)

In addition to TDM channel modules, you can have up to 4 channel access modules (CAMs) for video, voice, data, and various audio applications. For enhanced reliability and throughput, each CAM has its own 100Mbps spoke on the internal high-speed packet bus.

1.5.4

Network Interface Modules (NIMs)

The primary NIM is inserted into slot 17 of the NetXpress chassis. If you have a secondary NIM, it can be inserted into slot 15. The NIM-1 module is the command center for the NetXpress IP multiplexing system. The NIM-1 acts as an IP network interface, a packet engine, and a system manager. When coupled with the MIU-201 module interface unit (or MIU-202 module interface unit for external T1/E1 port or timing redundancy), the NIM-1 provides shelf management control, TDM over IP GatesAir, Inc. Intraplex Products

1-3


1—Introduction

encapsulation, LAN and WAN traffic control through 10/100 BaseT Ports, and timing control for external stream traffic and system synchronization.

1.5.5

Module Adapters

In addition to supporting TDM channel modules, the NetXpress system supports existing module adapters (that is, module adapters used with Intraplex Access Server models ACS-160 and ACS-260 Series). Intraplex module adapters are installed in the rear of the shelf and work in conjunction with the channel cards installed in the front.

1.5.6

Module Interface Unit (MIU) – 201

Figure 1-1 shows the panel view of a MIU-201 module interface unit.

Figure 1-1. MIU-201 Module Interface Unit Panel The MIU-201 unit provides connectivity for the NIM-1 network interface module. The MIU-201 connects to the NIM-1 in the rear of the shelf and features these communication ports: ●

Two T1/E1 Ports for full or fractional circuit emulation over IP

●

Two 10/100 BaseT Ports (LAN port can serve as a second WAN port)

●

Timing in/out for external stream and system synchronization

●

Serial Port for local craft access, Contact I/O for external control

●

Management Ethernet Port (Management traffic can also be mapped to LAN and WAN ports)

You can use two MIU-201 units with two NIM-1 modules to provide NIM-1 redundancy. However, you need two MIU-202 units to enable T1/E1 interface connections to switch automatically (T1/E1 redundancy).

1.5.7

MIU-202

The MIU-202 module interface unit provides connectivity for the secondary NIM for external T1/E1 port or timing redundancy. The MIU-202 connects to the secondary NIM in the rear of the shelf and has the same communication ports and similar capabilities as the MIU-201. For T1/E1 redundancy to work correctly, both the main and redundant NIM-1 cards must be equipped with MIU-202 units behind them instead of MIU-201 units.

1-4


1—Introduction

1.5.8


Power Supplies

The NetXpress chassis can accommodate slot-mounted, single or dual redundant power supplies. The chassis has both DC source and universal AC source power supplies.

1.5.9

Indicator Lights

Four visible system status indicator lights are located on the front of each power supply module. Figure 1-2 shows the system status indicator lights and provides an explanation of each light. Figure 1-3 shows the front of the NetXpress shelf (uncovered), and Figure 1-4 shows the back of the shelf for AC powered or AC/DC powered. NORMAL – Green light: When lit, indicates power is on and the NetXpress shelf is operating normally MAJOR – Red light: When lit, indicates an alarm condition exists (for example, stream loss, signal failure, loss of frame on an external T1/E1 port, power failure if redundant supply is installed) MINOR – Yellow light: When lit, indicates that an alert condition exists (for example, channel module inserted or removed, stream jitter buffer reset occurred) ACO – Green light: When lit, indicates alarm cut-off is active, reset by the NIM-1 when the alarm condition has been cleared (ACO is triggered by the push button switch located on the front panel of the NIM-1) Figure 1-2. NetXpress System Status Indicators TDM Bus

Slots 1 to 12 for TDM channel modules

TDM Bus

Slots 13, 14, & 16 for channel access modules (CAMs)

High Speed Packet Bus

Slot 15 for Secondary NIM or Additional CAM

Redundant power supplies

Slot 17 used for Primary network interface module (NIM)

Figure 1-3. Front View of the NetXpress Shelf without Cover

Figure 1-4. Rear View of the NetXpress Shelf – AC or AC/DC Powered GatesAir, Inc. Intraplex Products

1-5


1—Introduction

1.6 NetXpress Software You can control all the functions of your NetXpress unit and access network statistics and system status through the NetXpress Home page. You can choose to run simultaneous software windows, each connected to a different NetXpress system in the network (Figure 1-5).

NetXpress Home Page

IP Network

Figure 1-5. Multi-shelf NetXpress System Network The SNMP Configuration screen lets you control and monitor your NetXpress system from a central network management system. You can access the NetXpress Home page from the network management system to research a particular problem or obtain a graphical view of system configuration or status.

1-6


No header

Section 2 – Functional Design This section of the manual describes the intent of IP multiplexing and day-to-day operations of the Intraplex NetXpress IP multiplexer system. It also describes how to use the IP multiplexer to configure real-time payload transport of voice, audio, video, and data over existing IP networks. IP multiplexing offers many advantages and benefits to broadcasters and service providers. Packetbased media transport with the NetXpress system provides these competitive advantages: ●

Economical, efficient transport of audio, voice, data, and video

●

Flexibility when integrating to business applications, systems, and networks

●

Scalability to accommodate additional applications and network growth

●

Reliable service due to hardware redundancy, network monitoring, and error mitigation

●

Easy transition and migration from legacy systems, and reuse of cards and components

2.1 Network Concepts and Considerations When looking at the NetXpress system and packet-switched services as a whole, there are a number of network-related concepts and topics to consider.

2.1.1

MTU throughout the Network

Prior to configuring a stream, the user must have prior knowledge of end-to-end MTU (Maximum Transmission Unit) between stream endpoints. This can also be measured 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 system does not support re-assembly.

2.1.2

DHCP Use

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

2.1.3

Routing Table Construction

The behavior of the NetXpress system within the customer’s network is that of an IP host. As such, the NetXpress routing table is used solely to route internally generated packets. For streams that are unicast, the determination of the next-hop gateway to reach the remote NetXpress shelf is done by examining the system routing table. Routes in the routing table fall into two basic categories: automatic routes and user-defined routes. The NetXpress 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 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 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 routing table from the NetXpress Home GatesAir, Inc. Intraplex Products

2-1


2—Functional Design

page (Section 4.4.4.2 IP Routing Table) or via direct SNMP access of the proprietary route management MIB (Management Information Base).

2.1.4

WAN and LAN Port Auto-negotiation

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

2.1.5

NetXpress ICMP Support

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

2.1.6

Redundant WAN Link Configuration

In the NetXpress system, WAN link redundancy is achieved via the Link Aggregation feature, which provides load sharing between the LAN and WAN port. The WAN redundancy option is available when the LAN port is not going to be used as a normal customer data port. The NetXpress system supports configuration of LAN and WAN ports into a single logical Trunk group. Similar configuration must be performed on the switcher/router to enable the corresponding ports into a single Trunk group.

2.1.6.1

Enable WAN Link Redundancy

To enable this feature, the redundancy parameter of the WAN port configuration must be set (Section 4.4.4.1 – Network Image Configuration); correspondingly, ports on the connecting switch must also be configured for Trunking. Once enabled, the NetXpress system and the switch load balance traffic on all active links automatically. Should one of the two links fail, the other assumes the full traffic load of the two links up to its available capacity.

2-2



2.1.6.2


Disable WAN Link Redundancy

If you are going to disable WAN link redundancy, you must clear the Use LAN as Redundant WAN Link check box on the WAN Interface Configuration screen (Section 4.4.4.1 – Network Interface Configuration) and Trunking must be disabled on the switch ports. We also recommend that the LAN cable be disconnected so that the switch releases any cached MAC addresses.

2.1.7

IGMP Multicast

The NetXpress system interoperates with Multicast Routers using the Internet Group Management Protocol (IGMP). The IGMP Multicast mode involves transmission to specific hosts through IGMP routers. This scheme allows you to route specific packets onto specific segments, thereby segregating unwanted traffic from narrow segments. The NetXpress 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 system sends out an IGMP Leave message and also responds to the membership queries from the router. It supports the proprietary IGMP statistics MIB to account for all incoming and outgoing messages.

2.2 Streams The NetXpress IP multiplexer uses packet streaming to transport audio, voice, data, and video signals.

2.2.1

Stream Types

2.2.1.1

Unidirectional

versus Bidirectional

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

2.2.1.2

Unicast versus Multicast

Packet streams can also be classified as unicast or multicast. Unicast describes the transmission of a piece of information (a packet stream in this case) from one point to another point. Unicast transfer mode is still the predominant form of transmission on LANs and within the Internet. Examples of standard unicast applications include HTTP, SMTP, FTP, and Telnet. Multicast describes communication where a piece of information is sent from one or more points to a set of other points (a multicast group address). There may be one or more senders and the information is sent to a set of receivers (there may be no receiver or any number of receivers). With multicasting, the same packet is delivered simultaneously to a group of clients. Multicast applications must use the UDP (User Datagram Protocol) transport protocol, since TCP (Transmission Control Protocol) only supports the unicast mode. Most circuits provided by Intraplex multiplexer systems are unicast, including those provided with the NetXpress system. However, several types of channel modules can be configured for point-tomultipoint operation (multicast). For example, a single program audio transmitter module and several program audio receiver modules can be set up in a point-to-multipoint or “broadcast” circuit GatesAir, Inc. Intraplex Products

2-3



configuration, allowing multiple locations to receive the same program audio signal without the need for tandem decoding and re-encoding at each receive site. In order to achieve this, you must set all the receive modules to the same time slots as the transmit module. If your network does not support multicasting, you can configure the NetXpress system to multiunicast up to four destinations. The programming source must be in contiguous time slots on TDM Bus 1A. The receivers can be on any of the internal TDM busses. Section 4.4.3.6 – Media Switch Map gives additional multi-unicast information.

2.2.1.3

Voice Streams versus Data Streams

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

2.2.2

Protocol Stack for TDM-based Streams

The protocol stack that the NetXpress system uses is the protocol hierarchy used for TDM-based packet streaming. The figure below represents the protocol stack inherent to the NetXpress system.

Ethernet 2.2.3

IP

UDP

RTP

TDM

Stream Addressing

In the NetXpress system, the process of stream addressing involves the designation of a destination IP address for both unicast and multicast IP streams (Section 4.4.5 – Configure Streams). During the process of adding streams, individual streams are designated as either unicast or multicast in the Transmission Type field (Section 4.4.5.1 – Stream Creation).

2.2.3.1

UDP Port Addressing

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

2.2.3.2

Source and Destination Definitions on the TDM Bus

The NetXpress system allows you to define TDM source and TDM destination busses. TDM Bus 1A, TDM Bus 1B, TDM Bus 2A, TDM Bus 2B are your choices for both source and destination busses. If you need to connect to a T1 or E1 circuit, the TDM busses within the NetXpress system must also be 2-4




configured in the corresponding T1 or E1 system mode. (Section 2.6 – NetXpress Internal TDM Busses and 4.4.5.1 – Stream Creation gives more information.)

2.2.4

Multicast Group Addressing

The NetXpress system supports the use of multicast for stream transmission and supports the creation of up to 32 transmit, receive, or a combination of transmit and receive streams. You can use a multicast class D IP address in one of these ranges: ●

233.0.0.0 – 233.255.255.255

●

239.0.0.0 – 239.255.255.255

Figure 2-1 represents a scenario where multicast addresses are “administratively scoped.” Some customers may also require GLOP assignment by the carrier WAN using 233.x.x.x address ranges as well. Section 4.4.5.1 – Stream Creation shows multicast addresses in stream configuration.

Figure 2-1. Carrier Multicast Backbone Example

2.2.5

Media Switch Map

The NetXpress system now includes a media switch which dynamically allocates system resources to satisfy active stream requirements. Before the V3.03 release, the system supported six multi-unicast transmit streams. Now the number of transmit streams is only limited by the available time slots on the four IP buses and two external buses; therefore, it is possible—depending on your time slot requirements—to have all 32 streams multi-unicasting the same content. Previously, the incoming receive stream was only mapped to one internal TDM destination on which the channel module resides. Now you can create multiple receive streams with the same classification, allowing the content of the single incoming stream to be mapped to multiple receive channel modules. Figure 2-2 shows the media switching capability on an incoming media stream. The switch can take a single incoming media and signaling stream and create multiple internal streams, anchored to that one stream, to drop the same content onto as possibly all channel modules and to external TDM ports, up to a maximum of 32 streams copies. GatesAir, Inc. Intraplex Products

2-5



Audio/ Voice card 1 Audio/ Voice card 2

WAN IP Network

Media Switch

Audio/ Voice card 3

Incoming Media and Signaling Stream

Audio/ Voice card N

TDM Network

Figure 2-2. Media Switching on Incoming Media Stream Figure 2-3 shows the media switch taking a single media stream from an internal audio or voice module (or from an external TDM interface) and switching that same content to multiple IP and TDM destinations. The maximum amount of destinations depends on the availability of switching resources and the maximum number of 32 streams of identical content that can be created.

Media Stream to IP Dest 1

Audio Card

Media Stream

WAN IP Network

Media Switch

Media Stream to IP Dest 2 Media Stream to IP Dest N

Media Stream to TDM Dest TDM Network

Figure 2-3. Media Switching of a Stream to Multiple Destinations

2.2.6

IGMP Auto Recovery

Version 3.03 also offers an IGMP auto recovery function. Enable IGMP auto recovery with multicast receive streams configured in a routed network. This function monitors several conditions to determine when an unsolicited IGMP membership report is sent for each receive group, thus preventing the routers from aging out the receive groups. Here are the specific conditions in which the unsolicited membership reports are sent:

2-6




●

If a router IGMP general query has not been received for more than two minutes – This condition assumes that the default query interval on the router is set to one minute. The router allows three query responses to be missed before the groups are purged. This check helps queries reach the software stack in spite of incoming congestion.

●

If an IGMP query is received but the operating system has not sent membership reports – The NetXpress system then generates these reports.

The NetXpress system can also log all IGMP messages to use in debugging any multicast problems.

2.2.7

Telephony

The NetXpress system allows the creation of streams whose endpoints are Intraplex voice channel modules that support telephone signaling (for example, VF-15E, VF-16AE, and VF-25 modules). The voice circuits generate signaling bits which the NetXpress system transports out-of-band and reinserts onto the NetXpress 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 Performance menu provides statistics on signaling packet transmission, and these statistics are cleared when the other stream statistics are cleared. Signaling bits are carried on the internal TDM busses using Channel Associated Signaling (CAS). Telephony streams need to originate and terminate on busses where 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 CAS mode is enabled, the NetXpress system uses time slot 16 to carry the signaling bits for all the other channels on that bus; this time slot is not available to carry normal traffic.

2.2.8

Echo Cancellation

The NetXpress system can provide echo cancellation for voice circuits using up to 2 optional echo canceller cards that plug onto the NIM-1 module. Each board can provide echo cancellation for up to 30 channels per echo canceller card on the TDM bus. Echo cancellation can only be enabled for full-duplex streams with identical Bus/Channel configuration in the transmit (Tx) and receive (Rx) direction, and both endpoints of the stream need to have an echo canceller card installed. Echo cancellers are needed in 2-wire modules (for example, VF15E/16AE) but not in 4-wire modules (for example, VF-25E). When using echo cancellation, you should not configure streams to encapsulate more than 60 frames per packet.

2.2.9

Packetization and Overhead

Packetization in the NetXpress system is a process in which frames of data from the TDM bus are collected into IP packets for transmission through the IP network. A frame on a NetXpress TDM bus is divided into 32 partitions or time slots, each containing a byte of data. Because of the serial nature of the TDM bus, an entire TDM bus frame encompasses 125 µs in time. The packetization interval for a stream defines the number of TDM frames collected by the NetXpress system into a single packet for transmission. The higher the packetization interval, the greater the accumulation delay introduced to the program because each frame must be accumulated before the packet can be created. Note that the total program delay is a combination of packetization delay and network delay. Each packet in a NetXpress stream contains 44 bytes of non-program data (overhead) corresponding to the header information required for the IP, UDP, and RTP protocol layers. The ratio of non-program data to program data for a packet can be thought of as the overhead required to get the packet through the network. The higher the overhead, the more the network bandwidth available to an application used to transmit non-program data. Program delay can be minimized by using a small packetization interval at the expense of an increase in overhead. Conversely, increasing the packetization interval decreases the overhead but increases the program delay (Table 2-1).


2-7



Another factor in determining the overhead associated with a stream is the number of time slots from each TDM frame that get placed in the packet. As the number of time slots from each frame increases, the stream overhead decreases because the ratio of overhead data to program data decreases. However, the number of time slots consumed from each frame does not affect the program delay. Therefore, it is desirable to combine time slots from a TDM bus headed for the same destination into a single stream to reduce overhead and to make the best use of available network bandwidth.

2.2.10

Packet Jitter Compensation

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

2.2.11

Packet/Stream Information Calculation

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

2-8




Table 2-1. NetXpress Stream User and Computed Parameters User Parameter Number of TDM Channels TDM Frames per Payload Jitter Buffer Size (8 – 128 packets) Computed Parameter TDM Channel Data Rate Packet Payload Size Packet Interval Packet Rate

Value 1 160 64 Value 64 kB/S

Number of TDM channels to transport in a stream Number of TDM frames per payload (packet) Configured jitter buffer size in packets Description

Formula

Calculated TDM channel data rate in kB/S Number of TDM Channels x 64

160 bytes

Calculated payload size in each packet in bytes

Number of TDM Channels x TDM Frames per Payload

20 mS

Calculated packet interval (time between packets) in mS

Number of TDM Frames per Payload ÷ 8

Calculated packet rate for a stream in packets/S

(1 ÷ Packet Interval) x 1000

50 packets/S

Jitter Buffer Delay

Description

640 mS

Calculated jitter buffer delay in mS

Jitter Buffer Size x Packet Note: This delay assumes a receive queue Interval ÷ 2 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 Rate

96.8 kB/S

Calculated Ethernet stream data rate in kB/S *

Ethernet Frame Size x Packet Rate x 8 ÷ 1000

IP Packet Size

204 bytes

Calculated IP packet size in bytes = Packet Payload Size + IP overhead (20 bytes IP + 8 bytes UDP + 16 bytes RTP)

Packet Payload Size + 44

Stream Data Rate

81.6 kB/S

Calculated IP stream data rate in kB/S *

IP Packet Size x Packet Rate x 8 ÷ 1000

* In most instances, Ethernet overhead is stripped before the packet is transported over a WAN link. However, in certain instances (such as Metro Ethernet networks that transport the entire frame); the Ethernet overhead is left on the packet.

2.2.12

Stream Statistics

NetXpress 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.4.6.1 – Stream Statistics). You may be able to modify your NetXpress system for optimum throughput, bandwidth efficiency, and reduced errors. As an example, you may wish to alter the size of the jitter buffer if you are experiencing too many lost, underrun, early, or late packets. Specifically, if you are experiencing too many late packets, you might need to increase the jitter buffer size.

2.3 System Security System security in the NetXpress system is controlled through login and password control, interface protocol management enabling/disabling, an IP Access List, and the establishment and control of SNMP Communities.


2-9


2.3.1


NetXpress Logon

When you launch the Web server interface application in the NetXpress system, the system immediately displays the logon screen (Figure 2-4). You must type the proper user name and password to gain access to the NetXpress Web interface. Before it is configured, the NetXpress system has a default user name of “admin” and default password of “admin” for the Web interface. Once you have logged on, you can change the Web interface user name and password, as well as create user names and passwords for FTP access (Section 4.4.7 – Set up Accounts for more information).

Figure 2-4. NetXpress Web-Interface Logon Screen

2.3.2

Management Protocols on an Interface

The NetXpress system comes with three Ethernet interfaces: WAN interface, LAN interface, and a Management interface (MGMT). The management interface allows users to run all management traffic on a separate network if desired. By default, each interface accepts HTTP and SNMP protocols and allows FTP and Telnet sessions to be established. You can use the interface screens in 4.4.4.1 - Network Interface Configuration to enable or disable different protocols for each interface. Controlling protocols by interface enables you to tighten security, block unwanted traffic, and ensure network privacy.

2.3.3

IP Access List Use

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

2.3.4

SNMP Communities

An SNMP community is a group of hosts that you can manage as a distinct group with SNMP. A community name must be used for all SNMP conversations to take place. The same name can be used for a read-only community and a read-write community, or two different names can be specified to restrict write-access to the system.

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



2.4.1


COS Levels for Stream Data

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

2.4.2

TOS Byte Marking for Outbound Stream Packets

In an IP network, all IP packets contain a field in the IP header called the Type of Service (TOS) byte. The value of the TOS byte tells the network what quality of service needs to be applied to the packet. You can define what the value of the TOS byte field should be for each of the four classes of service supported by The NetXpress system for stream packets. The system places the appropriate TOS byte value corresponding to the COS provisioned for a stream in every outbound data packet for that stream (Section 4.4.3.8 – System TOS Byte Definitions). Since TOS byte value can be set to any value per class of service, the NetXpress system can operate in networks using Differential Services (DiffServ) QoS and networks employing the standard TOS interpretation for QoS.

2.4.3

User-defined TOS Byte Setting for Outbound SNMP and HTTP Packets

In addition to supporting the TOS marking for stream data, the NetXpress system allows you to configure the TOS byte value placed in all outbound SNMP and HTTP packets. This allows SNMP management traffic and Web interface traffic to be handled in the network with a different class of service than other packets.

2.5 NetXpress Internal TDM Busses The NetXpress IP multiplexer uses up to four TDM busses to support data transfer for audio channels. These busses can be configured to operate in T1 or E1 mode. Note: All four TDM busses operate in the same mode; you cannot have some T1 busses and some E1 busses. When set for E1 mode, the TDM busses in the NetXpress system support CAS (channel associated signaling) and CCS (common channel signaling). With CAS signaling, time slot 16 is always reserved for telephone signaling. For all TDM busses, the data rate is fixed at 1.544 MHz (T1 mode) or 2.048MHz (E1 mode).

2.5.1

Compatibility with Intraplex TDM Channel Modules

Nearly all Intraplex TDM channel cards are compatible with the NetXpress IP multiplexer. Table 2-2 shows the modules currently supported.


2-11



Table 2-2. NetXpress-supported TDM Channel Modules with Nominal Power

DA-191A

1.2

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

VF-15E

2.3

DS-562i

2.0

PR-153

5.5

VF-16AE

2.3

DS-961D

1.2

PTR-155

5.0

VF-16E

2.3

DS-961DE

1.2

PT-250

3.0

VF-25E

2.0

DS-961DF

1.2

PR-250

3.4

VF-27E*

2.0

DS-961DG

1.2

PTR-255

7.7

VF-28E

2.0

DS-965

1.2

PT-350

3.0

VF-29E

2.0

DS-966A

2.5

PT-350B

3.0

VF-15

2.3

DS-967

2.5

PT-350C

3.0

VF-16

2.3

OCU-DP

2.0

PR-350

3.4

VF-16A

2.3

PR-350B

3.4

VF-25

2.0

PR-350C

3.4

VF-27*

2.0

PT-353

3.0

VF-28

2.0

PR-353

3.4

VF-29

2.0

PT-355

3.0

VF-40

2.0

PT-355B

3.0

DV-600

5.0

PT-355C

3.0

DV-600A

5.0

PR-355

3.4

PR-355B

3.4

PR-355C

3.4

Data Modules

4.0

Module

Nominal Power (watts)

4.7

Voice Modules for E1

PT-150B


PT-D150

Voice Modules for T1

4.7

High Fidelity Program Audio Modules–AES\EBU Input / Output

PT-150A

Module

Secure Digital Voice Modules

High Fidelity Program Audio Modules – Analog Input/ Output

Module


* Neither the VF-27 nor VF-27E module supports or operates with E & M signaling in a NetXpress system. Channel modules require no configuration to use particular busses. However, you must configure channel modules to use either the A or B side of the bus. Also, if the TDM busses are set for E1 operation, you must provision the bus itself to use CAS signaling and then provision every module on the bus to inform it that CAS signaling is in use. Each of the 12 TDM chassis slots has its own frame loss signal to tell the module to mute if there is a problem on the bus for that particular module.

2-12



2.5.2


TDM Channel Loopbacks

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

Figure 2-5. TDM Loopback Scenarios When the Internal Loopback is applied to a channel or an entire 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. You can set the Internal Loopback at any time. However, if a stream using the corresponding time slot is activated or de-activated, the loopback is cleared. When the External Loopback is applied to a channel or an entire TDM bus, the received data is delivered to the channel module on that same TDM bus as well as being transmitted back out to its originating source. The External Loopback for a time slot only succeeds if an active stream is currently using that time slot. You can apply both internal and external loopbacks simultaneously. This example shows loopbacks for an entire bus, but you can also loopback individual channels within a bus.

2.5.3

TDM Bus Mapping

Each NetXpress TDM bus is connected by default to a virtual IP bus; this connection is bi-directional. The NetXpress system sets bus mapping automatically based on the stream parameters. Section 2.2.5 – Media Switch Map and Section 4.4.3.6 – Media Switch Map give additional mapping information.

2.6 System Time-of-Day With the NetXpress system, there are two ways to set the system time-of-day: 1) manually and 2) via NTP (Network Timing Protocol) server. If you choose the latter method, you must use the Web server


2-13



interface to enable NTP in the NIM Configuration – General Setup screen and provide the IP address of the SNTP server (Section 4.4.3.1 – General Setup). The NetXpress system maintains the time and date in a battery-backed time-of-day clock on the NIM-1 module.

2.7 System Timing 2.7.1

Types of System Timing

System timing is the process of synchronizing communications and stream traffic between two or more NetXpress systems in a network. Time synchronization is critical to the proper functioning of the NetXpress network. It must be configured correctly. Primary and Secondary timing is configured via the Web interface using the System Timing screen (Section 4.4.3.7 – System Timing). If primary and secondary timing fail, the system uses internal timing. The NetXpress system provides three timing modes from which to choose: Internal, External, or Stream. You must specify the timing source for both Primary and Secondary timing.

2.7.1.1

Internal Timing

Internal timing is derived from an extremely accurate internal oscillator on the Network Interface Module (NIM-1). With a primary timing source, all NetXpress systems use timing that is traceable to the same long-term accurate oscillator. In a NetXpress network, only the master NetXpress system can use internal timing. Other NetXpress shelves in the network must use external or stream timing.

2.7.1.2

External Timing

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

2.7.1.3

Stream Timing

Stream timing is derived from the incoming packet stream. A timing stream must have a packet rate of at least 8 pps (1000 frames/packet). Timing can be sourced through the RS-422 Timing OUT port on the MIU-201 or MIU-202. This type of timing uses an algorithm inherent in the TDMoIP chip. In a NetXpress network, only subordinate NetXpress systems can be set to stream timing mode. The NetXpress master system monitors stream traffic and adjusts timing so that the subordinate shelves are synchronized with the master clock frequency. As a general rule; the faster the packet rate, the better the stream timing. With stream timing, jitter buffer size can be monitored and regulated to avoid buffer underflow/overflow and negate the effect of packet delay 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. It should be noted that networking or router problems can result in no recovery of timing from a stream. Note: When you configure several receive streams and use a stream as the timing source, we highly recommend that the stream with the highest packet rate (such as the lowest frames per payload value) be used as the primary timing stream.

2.7.1.4

SynchroCast3™ Timing

The SynchroCast3 system uses a simulcast technique which transmits to an extended geographic area using multiple, overlapping transmitters operating on the same frequency. Historically, broadcasts 2-14




from nearby transmitters on the same frequency have created serious reception problems where they overlap. The SynchroCast system, originally developed for use in land mobile radio systems, makes simulcasting possible in FM broadcast as well. The SynchroCast system can provide dramatically increased station coverage while reducing or eliminating unwanted artifacts at the listener’s receiver. The SynchroCast3 system in the NetXpress multiplexer maintains the phase alignment of the transmitted signals using Global Position System (GPS) technology, providing ●

GPS controlled carrier frequency synchronization.

●

GPS controlled precision audio phase alignment.

●

Dynamic adjustments to compensate for network routing changes.

The SynchroCast3 system sends timing reference signals along with the audio content to the transmitter sites. GPS receivers, placed at the Origination Point and transmitter sites, provide a timing reference. At the Transmitter, timing signals coming from the Origination Point (along with the audio content), are compared with the local timing reference and a precise amount of delay is introduced to correct the timing difference between transport paths. Once the signals are synchronized, the system operates automatically to keep the preset delay constant. The Intraplex SychroCast3™ System Installation & Operation Manual gives more information. The SynchroCast3 system carefully controls the receive jitter buffers associate with the IP streams, allowing multiple locations to deliver their stream data at precisely the same instant. This is essential for radios using multiple transmitters so that interference problems associated with them can be minimized.

2.7.2

NetXpress Timing Scenarios

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

Multicast Audio Stream 1

NetXpress C

NetXpress A

Audio Stream 2

NetXpress D

NetXpress units at sites A and C must have synchronized system clocks so that the NetXpress unit at site D can properly receive and process its two incoming audio streams.

Figure 2-6. Timing Synchronization NetXpress units can derive system timing in one of three ways: 1. An internal clock is available, based on a local oscillator within the unit (Internal Timing) 2. An external clock can be applied to the unit (External Timing) 3. An incoming IP unicast or multicast stream (Stream Timing), thereby synchronizing itself to the NetXpress unit that generated the stream


2-15



In simple point-to-point systems, it is common to use a combination of internal and stream timing. Figure 2-7 shows the unit at site A is set to Internal Timing, utilizing its local internal oscillator. The unit at Site B derives timing from the audio stream transmitted from site A to site B. STREAM TIMING

INTERNAL TIMING

NetXpress B

NetXpress A

Figure 2-7. Point-to-point Timing Synchronization The advantage of the configuration in Figure 2-7 is simplicity of implementation. No external timing sources are required. This can be extended to multiple site systems by designating one site as the master timing location and having the rest of the sites derive timing from that site. Figure 2-8 shows such a system, with site A using internal timing and the remaining sites using stream timing to achieve synchronization to site A. STREAM TIMING NetXpress B INTERNAL TIMING

STREAM TIMING

NetXpress C

NetXpress A

STREAM TIMING

NetXpress D

Sites B, C, and D use stream timing to derive timing from master site A.

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

2-16




STREAM TIMING NetXpress B INTERNAL TIMING

INTERNAL TIMING

NetXpress C

NetXpress A

NetXpress D

Site D cannot process both incoming streams because they have different timing sources.

Figure 2-9. Streams with Different Synchronization Sources There are two possible solutions to this situation. 1. Receive a stream at site C from site A solely for the purpose of synchronization (Figure 2-6). The cost of this is the additional bandwidth required in the network end-link to site C. 2. An alternative approach would be to utilize highly accurate external timing sources at sites A and C to achieve network synchronization. One example would be a Stratum 1 traceable timing signal 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-10). This guarantees the two streams received at site D have compatible timing, allowing site D to time from either incoming stream. STREAM TIMING NetXpress B

EXTERNAL TIMING

GPS

EXTERNAL TIMING

GPS

NetXpress C

NetXpress A

NetXpress D

Site D can derive system timing from either incoming steam.

Figure 2-10. Timing Synchronization with GPS In this case, the fixed cost of purchasing and deploying GPS units at sites A and C can be traded against the recurring cost of bandwidth to receive a timing stream at site C.


2-17


2.7.2.1


Backup Timing

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

STREAM TIMING

Audio Stream INTERNAL TIMING

Audio

NetXpress B

Audio

Off-air monitor audio

Monitor Stream

Audio Stream

NetXpress A

STREAM TIMING Monitor Stream

Audio

NetXpress C

Audio

Off-air monitor audio

Figure 2-11. Timing with Off-Air Monitor Streams

2.7.2.2

Timing Summary

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

2-18




2.8 NetXpress System and FEC The NetXpress system maintains uninterrupted audio transport by supporting Forward Error Correction (FEC). Specifically, the NetXpress system supports RFC 2733 framework. Basically, forward error correction is an error control process in data transmission where the source (transmitter) sends redundant data and the destination (receiver) accepts only 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 system versions 2.2 or higher, up to 32 streams (16 in each direction) can be designated as FEC streams. For each of the FEC streams, you can specify either of two techniques for forward error correction: FEC LOW or FEC HIGH (Section 4.4.5.1 – Stream Creation). This specification affects the sender only. The receiver processes all FEC packets. FEC LOW (appropriate for most low packet loss conditions) Single error correction is engaged. This scheme introduces a 50% overhead (increased bandwidth required) and can correct all single packet losses – consecutive packets are not lost. FEC HIGH (used in more serious packet loss conditions) Triple error correction is engaged. This scheme introduces a 100% overhead (increased bandwidth required) and can correct one, two, or three consecutive packet losses. In this scheme, the sequence of packets sent is critical if it is to protect against consecutive packet losses. Table 2-3 shows NetXpress rate loss for both FEC low and FEC high options. Table 2-3. NetXpress FEC Performance Data Network Loss Rate (%)

High FEC Loss (%)

Low FEC Loss (%)

1

0.0017

0.027

2

0.0023

0.085

0.0168

0.507

0.14

2.1

0.597

4.87

3 4 5 6 7 8 9 10 11 12 13 14 15

% 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 system supports redundant power supplies. You can install a main power supply and a redundant supply in case the main supply fails. The system runs on either AC or DC power supplies, GatesAir, Inc. Intraplex Products

2-19



and it supports AC 200W and DC 150W power supplies. NetXpress also offers support for the NXPS48-DC 48 volt DC-DC converter and the NX-PS24-DC 24 volt DC-DC converter power supplies. Section 3.9 – Power Supply Installation and 4.4.9 – View Power Supply Information give more information on NetXpress power supplies.

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

2.10.1

RBS

T1 systems use the RBS method of channel associated signaling. This information is embedded into the least significant bit of the audio channel once every 6th frame and injected into the channel without regard to the remaining bits. Therefore, RBS does distort the voice audio signal so slightly that you can only perceive it by distortion measurements. RBS signaling support should not be used on channels carrying information other than voice audio as it corrupts the data in the channel.

2.10.2

CAS

E1 systems use CAS to carry voice call information. Instead of embedding this information in the same channel as the voice audio, channel 16 of the E1 is reserved for all of the remaining channels to use for signaling.

2.11 ObjectVideo® Software ObjectVideo software empowers video systems to become intelligent by turning video into data. Devices can then respond and issue alerts based on a variety of human and non-human events, such as ●

Classifications of people and vehicles.

●

A person or vehicle breaking a perimeter.

●

A person leaving a bag unattended.

●

A person or vehicle loitering beyond a user-determined amount of time.

●

An object being taken/stolen.

The NetXpress system now acts as a remote analytics device along with video encoding. This includes the software and tools to enable the ObjectVideo system, create/modify analytics rules, and store/collect ObjectVideo alerts.

2.12 Network Interface Module (NIM) Redundancy You can add an additional NIM/MIU set to your NetXpress multiplexer. This secondary NIM (which is located in slot 15 of the NetXpress system) can be synced to the primary NIM (in slot 17), and the secondary one can automatically or manually switch over from Standby to Active when the primary has failed or been removed from the system. With a redundant NIM, the NetXpress system offers these attributes: ●

Module failure redundancy

●

User control of failover

●

Automatic switchback from Secondary to Primary NIM with user configurable options

●

Manual switchover to Standby NIM

●

Automatic synchronization of configuration and load images

●

User control for disabling synchronization

●

MIU-202 module interface pair, used with secondary NIM

2-20




Section 4.3 – Network Interface Module (NIM) Redundancy, Section 4.4.3.11 – Redundancy Configuration, and Section 4.4.10 – Configure Primary/Secondary Network Interface Module (NIM) give more details on configuring and operating a primary and secondary NIM (such as NIM redundancy). Note: NIM-1 Rev B10 or higher supports NIM-1 redundancy. For NIM redundancy, both NIM-1 modules need to be Rev B10 or higher. You can use either two MIU-201 module interface units or the MIU-202 pair (MIU-202-1 and MIU-2022) to provide NIM redundancy. The MIU-202 pair provides connectivity for the both NIMs for redundant support of external T1/E1 ports and external timing. With the MIU pair, the secondary NIM1 in slot 15 can become Active and access the T1/E1 interface ports used by the NIM-1 in slot 17. This MIU functionality alleviates the need for an external line switch on the T1/E1 interface ports.

2.13 Software Download When shipped from the factory, the NetXpress NIM-1 contains two identical software images, primary and secondary, each located in different flash memory devices. During normal operation, the NIM-1 loads the primary image. Should it fail to boot the primary image, the NIM-1 then attempts to load the secondary image. In the case of a failure in loading both the primary and secondary image, you can configure the NIM-1 to load an image from a remote FTP server. This image is not saved to either of the flash memory devices. You can also configure the NIM-1 to load the secondary image first, but if that fails, the NIM1 moves directly to loading from the remote FTP server and does not try to load the primary image. The NIM-1 software can be upgraded by opening an FTP session with the NIM-1 and transferring a new image file to one or both of the flash memory devices. You can configure both the primary and secondary images to be loaded from the same flash memory device; there is no requirement for them to be on different devices. In addition, you can store multiple software images on the NIM-1 up to the limit of the flash memory. To obtain the software and boot ROM download process in the latest version’s release notes, follow these steps: 1. Go to http://www.gatesair.com 2. Click Services and Support | Customer Support Portal. 3. At Customer Login, enter your User ID and Password. 4. At Self Service, click Download Software Updates. 5. At the Table of Contents, click Intraplex. 6. At the Intraplex: Table of Contents, click NetXpress. 7. Click the link for the latest version of the NetXpress software. 8. Click Save on the dialog box and save the zipped file to your hard drive. 9. Open the zipped file and open the release notes. You can also obtain the latest copy of MIBs from this page on the Customer Support Portal as well.

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

2-21



the new NIM-1 module. It can also be backed up easily to the server using the same process, only in reverse order. Restored configuration takes effect when the NIM-1 is rebooted. Restoring configuration for a redundant NIM system follows a similar process.

2.15 Fault Detection and Reporting With the use of SNMP traps, the NetXpress system has the ability to detect and report on a number of alarm conditions.

2.15.1

Alarm Hierarchy

The NetXpress system has major and minor alarms. A major alarm is a fault that has a direct effect on service, such as a component failure disrupting the delivery or reception of data. A minor alarm is a fault that has no effect on service. This includes all other errors detected which do not affect NetXpress operation. The NetXpress system is also equipped with an alarm cutoff (ACO) device. The ACO is a momentary push-button switch that can be pressed once to cut the external contacts and pressed a second time to re-arm the external contacts. System alarm states are visible in the form of colored lights on the front panel of the NetXpress power supply modules and on the NetXpress Home page (Section 4.4.1 – Start at NetXpress Home Page). A red light indicates a major shelf alarm. A yellow light indicates a minor shelf alarm. A green light indicates no alarm condition exists.

2.15.2

Alarm History

Current alarms and alarm history can be reviewed from the NetXpress Home page. Go to Faults | Alarm Table to display the Current Alarms screen or Faults | Alarm History to display the Alarm History screen. Both screens contain this information: ●

A list of alarms

●

The dates and times the alarms occurred

●

The severity of the alarms

●

A description of each alarm occurrence

For the purpose of troubleshooting and future reference, alarm history in the NetXpress system can also be off-loaded to a text file.

2.15.3

SNMP Traps Use for Fault Reporting

The NetXpress system uses SNMP traps to report system faults, stateful events and informational events. Stateful events are considered ON/OFF alarm events. Informational events are non-alarm, one-time-only events. Equipment-related system events indicate a failure of the hardware on the NIM-1 or in the NetXpress shelf. Processing-related system events indicate a failure was detected in software processing. Facility-related system events indicate a failure occurred with one of the operation interfaces. The available list of SNMP traps changes with each software version. The MIB supplied with your version of NIM-1 application software gives a list of available SNMP traps.

2-22


No header here

Section 3 – Installation, Wiring, and Setup This section of the manual describes installation procedures and guidelines for the Intraplex NetXpress IP multiplexer and covers these topics: ●

Tools and cable requirements

●

NetXpress equipment unpacking and installation

●

NetXpress shelf installation

●

NIM installation

●

MIU-201 or MIU-202 installation

●

TDM channel module installation

●

CAM installation

●

Power supply installation

●

Wiring and external connections

●

Unit powering

3.1 Tools and Cable Requirements In addition to the equipment provided with your NetXpress system, we recommend these items to complete the system installation: ●

Basic telecommunications installation tool kit (screwdrivers, wire stripper, and so forth)

●

Rack mounting hardware (four threaded bolts per shelf)

●

Cables for each payload channel module being installed

●

Optional: a volt-ohm milliameter (VOM)

3.2 NetXpress Equipment Unpacking and Installation Upon receipt of your NetXpress system, complete these tasks: ●

Inspect all shipping containers for damage. If you observe damage, notify the shipping service as soon as possible.

●

Unpack all equipment from containers.

●

Inspect equipment for damage.

●

Verify that the NetXpress IP multiplexer is equipped as expected, confirming items from the packing list (Bill of Materials): Chassis with rack mount is in good condition One or two NIMs, one or two MIUs (depending on number of NIMs), and provided cables Power supply, cables, and utilities Channel modules, MAs, and provided cables CD containing NetXpress Installation and Operation manual and Intraplex channel module manuals


3-1


3—Installation and Wiring

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.3 NetXpress Shelf Installation All channel access modules (CAMs), TDM channel modules, module interface units (MIUs), module adapters, and power supplies plug into the main equipment shelf (Figure 3-1). These components communicate with each other via the shelf backplane or motherboard, which contains signal (TDM and Packet) and power distribution buses. As a standard practice, NetXpress shelf units are shipped pre-configured with power, network interface modules (NIMs), channel access modules, and TDM channel modules installed. All modules, module adapters, and module interface units can remain in place while you install each shelf into its designated equipment rack. Consider these points for equipment shelf installation: ●

If applicable, bolt the shelf into the designated equipment rack. If shelves are to be stacked in a rack, allow at least 1RU space between shelves to avoid possible heat problems.

●

Make sure all modules, module adapters, and module interface units are properly seated.

Note: If the shelf is AC powered, make sure the power cable can be accessed easily for maintenance purposes. To remove or install modules, you must first remove the front panel of the NetXpress shelf. Twist each of the four thumbscrews to loosen them. Tighten or loosen the screws by hand. Warning! When you remove the front panel to install or remove modules, make sure the NetXpress chassis is grounded to the rack and observe proper anti-static procedures. There is a chassis ground point located on the rear panel of the chassis (Figure 3-8). If the chassis has not been mounted in a rack, you should wear a grounding wrist strap when installing/removing modules.

3.4 NIM-1 Installation The NetXpress multiplexer utilizes a NIM-1 module. Install this primary NIM (Figure 3-2) in slot 17 of the NetXpress shelf. The connector on the NIM-1 prevents it from being installed in the wrong orientation. The power indicators and other components are positioned to the right of the PC board, closer to the shelf power supply. Warning! Do not attempt to install a TDM channel module in slot 17 (for NIM-1), slots 13, 14, or 16 (for CAM slots), or slot 15 (for redundant NIM-1 or additional CAM). Attempting to install a TDM channel module in one of these slots can result in damage to the module and/or the NetXpress shelf midplane.

3-2




LINK TX/RX 100MB

JP5

LINK TX/RX 100MB

JP7

JP8

LINK TX/RX 100MB

LPBK

JP4

JP9

DIP

JP6

ACO

WAN

LAN

MGMT

LPBK

NIM-1 Front Board View

T1/E1

ACTIVE

A BC

STATUS

Figure 3-2. NetXpress NIM-1 Module and Indicator Lights

NIM-1 Top Board View

WANWAN, LAN MGMT C: When lit, 100MB rate for LAN, or MGMT.

B

A

B: Tx/Rx, blinks to indicate data transmission for WAN, LAN, or MGMT.

ACTIVE

TIMG

LINK Tx/Rx 100MB

LINK Tx/Rx 100MB

LINK Tx/Rx 100MB

ACO

A: WAN, LAN, or MGMT Link (active/inactive).

LPBK

ACO: Alarm Cut-Off button switch.

IP CFG DFLT

STATUS

DIP: DIP switches used to set default IP configuration and user configuration.

T1/E1

LPBK: Indicates loopback enabled. T1/E1: Green = good; yellow = minor fault; red = major fault. TIM: Timing, green = good, yellow = secondary, red = backup, blinks until synchronized and then lit. ACTIVE: Green when module is active, otherwise not lit. STATUS: Green = good, red = hardware failure. Note: The STATUS indicator light turns red briefly during power up. Table 3-1 shows NIM-1 switch settings for S3 Switch 1 and Switch 2. Table 3-1. NIM-1 Switch Settings (S3 Location) Switch 1

Switch 2

OFF

OFF

Normal boot with existing configuration files.

OFF

ON

Boot with existing configuration files. Force the MGMT IP address to 192.168.1.1 and reset the Web interface user name/password to “admin/admin”.

ON

OFF

Keep the IP address and route table configuration files. Move the rest of the configuration files to the backup area and revert to the NIM’s default configuration.

ON

ON

Move all configuration files to backup area. Boot from the network backup server 192.168.1.10 using the MGMT IP address 192.168.1.1.


Effect

3-3



Notes: When the NIM is inserted into the NetXpress chassis, pushing the dipswitches inward (towards the backplane) changes the state from OFF to ON. Pushing the dipswitches outward (towards the connector tab) changes the state from ON to OFF. When the NIM boots from the Network backup server, it deletes its current configuration. It does not copy the configuration to the backup area. You must save the configuration using the Configuration Backup functionality or perform a Save CFG using the dipswitch value 1=ON and 2=OFF before booting from the network backup server.

3.5 Secondary NIM-1 Installation If you choose, you can also install a secondary NIM (Figure 3-3). The NetXpress multiplexer utilizes a secondary NIM for redundancy, which you install in slot 15 of the NetXpress shelf. This NIM-1 has the same capabilities as the primary NIM. Note: NIM-1 Rev B10 or higher supports NIM-1 redundancy. For NIM redundancy, both NIM-1 modules need to be Rev B10 or higher.

3.6 MIU-201 Installation and Connection with NIM-1 The MIU-201 module interface unit is installed into slot 17 on the back panel of the NetXpress chassis and connects with the NIM-1 network interface module at the NetXpress midplane (Figure 3-3). NIM-1

Shelf Midplane

MIU-201/MIU-202

F2

F1

F4

F3

F7

F8

F5

F6

JP9

JP10 LINK TX/RX 100MB

JP5

LINK TX/RX 100MB

JP7

JP8

JP4

ABCDEF LINK TX/RX 100MB

JP6

LPBK

JP1

JP12

JP4

JP9 JP5

JP6

Figure 3-3. NetXpress NIM-1 and MIU-201 Midplane Insertion To connect the NIM-1 and the MIU-201, slide the NIM-1 module into slot 17 from the front of the shelf toward the connector on the midplane (Figures 3-4 and 3-5). Slide the MIU-201 module from the rear of the shelf toward the connector on the midplane. Do not exert too much pressure. Both modules should fit snugly onto the pins of the corresponding midplane connectors.

3.7 MIU-202 Installation The MIU-202 module is used with a secondary (that is redundant) NIM system to support failover of external T1/E1 ports and external timing. The MIU-202 module interface unit comes in a pair. The MIU-202-1 unit is installed in slot 17, while MIU-202-2 is installed in slot 15. After you install both units, connect them with the external cable that was shipped in your order. After installation, you need to connect the IP interfaces to the respective sub-networks of the MIU-202 pair, similar to the MIU-201.

3-4




3.8 TDM Channel Module and Channel Access Module Installation The NetXpress shelf can accommodate up to 12 TDM channel modules and 4 channel access modules (CAMs). (Figure 3-4) Most existing Intraplex TDM channel modules are compatible with the NetXpress multiplexer (Section 2.5.1 – Compatibility with Intraplex TDM Channel Modules).

Figure 3-4. Front View of NetXpress Shelf with Cover Removed TDM channel modules can be installed in slots 1 through 12 of the NetXpress shelf. CAMs are designed to be inserted into the connectors in slots 13, 14, 15, and 16. You could use slot 15 for a redundant NIM-1 instead of a CAM. (The Intraplex NetXpress AVC-1 Installation and Operation manual gives more information on video modules.) Note: When installing any channel module, you must first install the module adapter.

3.8.1

Module Adapter Installation

Each TDM channel module requires an installed module adapter (MA) to provide an electrical interface to external equipment. Before plugging a TDM channel module into the shelf slot, install the module’s associated module adapter into the matching slot on the back of the chassis.

3.8.2

Remote Control Operation

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

3.8.3

SCB Address Selection

In order to permit remote management of the TDM channel modules via the NetXpress Home page or SNMP, you must assign a unique SCB address for each module installed into the NetXpress chassis. For consistency and ease of identification, we recommend that you set the SCB address to match the physical slot occupied by the channel module within the NetXpress chassis. Channel modules installed into slots 1-6 have access to Bus 1 (TDM1A and TDM1B), while modules installed in slots 7-12 access Bus 2 (TDM2A and TDM2B). Table 3-2 shows the switch positions required to assign the SCB address to a TDM channel module.


3-5



Table 3-2. SCB Switch Settings for TDM Channel Modules SCB Switch Setting*

Card Address

1

2

3

4

5

6

1

0

0

0

0

0

1

2

0

0

0

0

1

0

3

0

0

0

0

1

1

4

0

0

0

1

0

0

5

0

0

0

1

0

1

6

0

0

0

1

1

0

7

0

0

0

1

1

1

8

0

0

1

0

0

0

9

0

0

1

0

0

1

10

0

0

1

0

1

0

11

0

0

1

0

1

1

12

0

0

1

1

0

0

*

0 = OFF, 1 = ON

Note: Remove a module from the shelf when changing the SCB address.

3.8.4

Channel Module Insertion

To install a TDM channel module, orient the ejector tab toward the bottom of the shelf and slide the module into the desired slot on the front of the shelf until it meets the connector on the front of the midplane. From the rear of the shelf, slide the module adapter into the corresponding connector on the back of the midplane. Warning! Do not attempt to install TDM channel modules upside down. The Eject Tab (Figure 3-5) should be at the bottom when the module is inserted.

Figure 3-5. Side View – TDM Channel Module and Module Adapter Insertion 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 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. Verify that all modules (NIM-1, CAM, TDM channel modules, and power modules) are seated securely in position.

3-6




3.9 Power Supply Installation The standard (main) power supply for the NetXpress IP Multiplexer is an 80-watt universal AC powered supply. An optional (redundant) 200-watt universal AC powered supply is available for applications with higher power requirements. Also, 150-watt DC Power supplies are available with -24 volts and input voltage of -48 VDC. On the front of the NetXpress chassis, the main power supply is on the far right, and the redundant power supply—if present—is left of the main supply. See Section 6 — “Specifications” for details on available power supplies. Note: The NetXpress system allows for the combined use of AC and DC power supply operation at the same time. Power supply modules do not require a special setup procedure. If the power supply is seated properly and external power is applied, it should operate as expected. Separate AC or DC mains feed each individual power supply module for added redundancy. Each NetXpress (3RU size) shelf is capable of supporting a second power supply for redundancy. Should the main power supply fail, the system continues to operate using the redundant power supply. Install a redundant power supply by simply inserting the second power supply into the slot adjacent to the main power supply slot in the front of the shelf chassis. The redundant power supply’s indicator lights function identically to the indicator lights on the main power supply. Additionally, with dual supplies installed, a failed power supply can be removed and a new supply inserted without turning off the system. Some power supply models have fans and the capability to monitor and report ●

Voltage, both from the power supply side and the midplane side.

●

Temperature.

●

Fan speed.

●

Redundant supply for failure.

When a supply fails, all the lights on that supply go out, indicating a failure. The MINOR indicator light of the redundant supply, if installed, is lit to show an alert state. Table 3-3 shows the system indicator lights. Note: When the system first comes on, the fans run at full speed temporarily and then slows down to normal operating speed under the control of the NIM-1 module Table 3-3. System Indicator Lights Light Normal

Definition The overall system is functioning properly.

Major

Serious hardware/software operational error.

Minor

Abnormal hardware/software operation or malfunction.

ACO

Alarm cut off; relay contacts are disengaged. When active, the ACO indicator flashes.

Press the push-button switch on the front of the NIM to activate/deactivate the ACO. Warning! Under heavy load conditions, power supplies can become extremely hot. Take caution when handling NetXpress power supplies, and provide adequate ventilation.


3-7



3.10 Wiring and External Connections Note: Your NetXpress IP multiplexer must be completely wired before placing any payload circuit into service. Installation and wiring should be performed ONLY by trained professionals.

3.10.1

Power Connections

Figures 3-6 and 3-7 show the rear panel connectors for the NetXpress equipment shelf. You can have a NetXpress shelf with either AC power or AC/DC power. Warning! To reduce the risk of fire, only use power conductors of No. 20 AWG or greater.

Figure 3-6. Rear Panel of NetXpress Shelf

3.10.1.1 AC Powered Systems All NetXpress systems have two chassis connections for AC line cords located directly behind the power supply modules on the rear of the system. Figure 3-7 shows the rear panel connectors for the Intraplex NetXpress equipment shelf with AC power only. The AC line input for the main power supply is located to the left, closest to the edge of the NetXpress chassis. The AC line input connector located to the right supplies AC power to the redundant or backup power supply module.

Figure 3-7. Connections for AC and AC/DC Operation 3-8




On the rear of the NetXpress chassis, the main power supply is on the far left, and the redundant power supply—if present—is right of the main supply. As there is no power switch on the NetXpress shelf, do not connect powered AC line cords to the NetXpress chassis until you complete the wiring to the network and channel modules. If you are using redundant power supplies, you need two power cords. A chassis ground connection is available on the rear panel (circled in red in Figure 3-8) just above the ALARMS terminal. This needs to be connected to an appropriate system ground for safety. 1. Install the channel modules into the slots. Note: The TDM Channel module may initialize in an “out-of-service” state, requiring activation through the Web Interface or SNMP. 2. Verify that all modules (NIM-1, CAM, TDM Channel, and Power) are seated snugly. 3. If the shelf is AC powered, plug the AC line cord into the appropriate AC input connector. If you have redundant AC supplies, plug both AC line cords into the appropriate AC input connectors. 4. If the shelf requires DC power, hook the appropriate wires to the DC terminal connector.

3.10.1.2 DC Powered Systems If the NetXpress chassis contains factory-installed DC power supplies, a barrier terminal strip is present on the rear panel for connections to the DC power sources. Figure 3-8 shows the rear panel connectors for the Intraplex NetXpress equipment shelf with AC and DC power capability. Table 3-4 describes the terminals on the DC power input barrier strip.

Figure 3-8. Rear Panel of NetXpress Shelf Metal bridging links are included on the DC barrier strip to connect both positive power terminal input leads together and to link the negative power input leads together. This permits a single external DC source to supply power to both the main and redundant supplies. If you wish to independently source the main and the redundant supplies, you need to remove these bridging clips from the barrier terminals. You should install an external fuse in the DC-power line to protect the multiplexer. The fuse rating is 6.3A for -48 volt input or 10A for -24 volt input. Remove this fuse and do not replace it until you complete the rest of the system wiring and are ready to turn on the system. 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. Two are required for power-redundant systems. 1. Connect the +BAT A terminal to the positive terminal of the station battery. 2. A chassis ground connection is available on the rear panel just above the ALARMS terminal. This needs to be connected to an appropriate system ground for safety. 3. Connect the –BAT A terminal to the negative terminal of the station battery.


3-9



4. If you have dual power supplies for redundancy, repeat the process for +BAT A and then –BAT A. Figure 3-9 shows single DC supply connections and Figure 3-10 shows DC connection operation with dual source power setup.

Figure 3-9. Connection for DC Operation Note: Jumpers between +BAT A and B / -BAT A & B (circled in red in Figure 3-9) are the Factory Default configuration and are intended for use with a single DC power source. Be sure to remove jumpers when using dual power sources.

Figure 3-10. Connection for DC Operation Using Dual Power Supply Setup Note: Be sure to remove jumpers when using dual power sources.

3.10.2

Alarms

All NetXpress chassis include barrier strip connections to the system alarms (Figure 3-11). Table 3-4 includes details for each of the power and alarm connections on a NetXpress shelf.

3-10




Figure 3-11. DC Power & Alarm Connectors Table 3-4. Power and Alarm Connectors Terminal

Description

+BAT A

This terminal and -BAT A serve as DC power input connections for a DC supply installed as the primary or main supply. (DC systems only)

+BAT B

This terminal and -BAT B serve as DC power input connections for a DC power supply installed as the redundant or backup power module. (DC systems only)

-BAT A

This terminal and +BAT A serve as DC power input connections for a DC supply installed as the primary or main supply. (DC systems only)

-BAT B

This terminal and +BAT B serve as DC power input connections for a DC power supply installed as the redundant or backup power module. (DC systems only)

ALARM: MINOR NO

Minor alarm condition, normally open contact*. This terminal electrically meets the MINOR COM terminal when the system exhibits a minor fault or when the system has no power.

ALARM: MINOR COM

Minor alarm, common.* This terminal electrically meets the MINOR NO terminal when the system exhibits a minor fault or the system has no power. Else this terminal will electrically connect to MINOR NC.

ALARM: MINOR NC

Minor alarm condition; normally closed contact*. This terminal electrically meets the MINOR COM terminal when the system has power and there is no minor fault exhibited. During a minor alarm, this terminal is electrically isolated.

ALARM: MAJOR NO

Major alarm condition, normally open contact*. This terminal electrically meets the MAJOR COM terminal when the system exhibits a major fault or when the system has no power.

ALARM: MAJOR COM

Major alarm, common.* This terminal electrically meets the MAJOR NO terminal when the system exhibits a major fault or the system has no power. Else this terminal will electrically connect to MAJOR NC.

ALARM: MAJOR NC

Major alarm condition; normally closed contact*. This terminal electrically meets the MAJOR COM terminal when the system has no power and there is no major fault exhibited. During a major alarm, this terminal is electrically isolated.

* When the shelf is not on (does not have power), all relays default to their alarm positions. Normally open contacts are closed and normally closed contacts are open. The NORMAL, ALARM:MINOR and ALARM:MAJOR are all mutually exclusive. If there is a minor or major alarm condition present, the NORMAL indicator light on the NetXpress chassis is off, and the MINOR (yellow) or MAJOR (red) indicator light is on, showing the degree of fault.

3.10.3

MIU-201 Connections and Wiring

The MIU-201 is the module interface unit for the NIM-1 module. All hardware networking connections terminate at the MIU. The MIU has connections for ●

Two T1 or E1 networks.

●

Ethernet WAN, LAN, and MGMT (management) connections.

●

Network timing input and output.


3-11

Intraplex NetXpress IP Multiplexer Version 3.05 ●

Contact closures.

●

Serial craft port.


3.10.3.1 MGMT Port The MGMT port on the MIU-201 module (Figure 3-12) is an 8-pin RJ48 modular socket primarily used for management access to the NIM-1 module. Use a standard Category 5 or better twisted-pair cable to connect MGMT to an Ethernet switch. The port is auto-sensing, so you may use a straight-through pinned or network crossover cable to connect MGMT directly to a Network Interface Card (NIC) of a personal computer. Table 3-5 gives MGMT port pin assignment information.

Figure 3-12. NetXpress MIU-201 T1-E1 A/T1-E1 B: T1/E1 ports for circuit emulation over IP, used as customer ports for full or fractional T1 or E1 data. WAN/LAN: 10/100 BaseT Ethernet ports for network LAN/WAN communications. Orange: Tx/Rx activity. Green: Link activity. TIMING IN/OUT: Timing IN/OUT ports for network stream synchronization. CONTACTS: Contact I/O – future use. SERIAL: Serial Port input/output – factory use. MGMT: Management Ethernet port.

3.10.3.2 WAN Port The WAN port on the MIU-201 is an 8-pin RJ48 modular 10/100BASE-T (10 or 100 Mbps) Ethernet port. The NIM-1 uses the WAN interface for all stream traffic. When provisioned, the WAN port can also be used for management access to the NIM-1 module. Use a standard Category 5 or better twisted-pair cable to connect the WAN to an Ethernet switch. The port is auto-sensing, so you can connect to uplink ports on a router as well as standard port connections. Table 3-5 gives WAN port pin assignment information.

3-12




Table 3-5. Pin Assignments for the LAN/WAN/MGMT Ports Connector

Pin

Description

1

Transmit (+)

2

Transmit (-)

3

Receive (+)

4

Not used

5

Not used

6

Receive (-)

7

Not used

8

Not used

3.10.3.3 LAN Port The LAN port on the MIU-201 is an 8-pin RJ48 modular 10/100BASE-T (10 or 100 Mbps) Ethernet port. When provisioned on the NIM-1, the LAN port can act as a redundant WAN interface. Use a standard Category 5 or better twisted-pair cable to connect LAN to an Ethernet switch. The port is auto-sensing, so you can connect to uplink ports on a router as well as standard port connections. Table 3-5 gives LAN port pin assignment information.

3.10.3.4 T1/E1-A Port The T1/E1-A port on the MIU-201 is an 8-pin RJ48 modular synchronous T1 (1.544Mbps) or E1 (2.048Mbps) bidirectional interface for interconnection with external T1 or E1 based devices or networks. Use an EIA/TIA T568A or T568B wired Category 5 or better twisted-pair cable to connect T1/E1-A to the external T1 or E1 circuit or equipment. Do not use USOC wired cabling for this connection, as the pairs are not twisted in the required combinations. Table 3-6 gives T1/E1 port pin assignment information. Table 3-6. Pin Assignments for the T1/E1 Ports Connector

Pin

Description

1

Receive from network, ring

2

Receive from network, tip

3

Not used

4

Send towards network, ring

5

Send towards network, tip

6

Not used

7

Frame ground (transmit)

8

Frame ground (receive)

3.10.3.5 T1/E1-B Port The T1/E1-B port on the MIU-201 is an 8-pin RJ48 modular synchronous T1 (1.544Mbps) or E1 (2.048Mbps) bidirectional interface for additional interconnections with T1 or E1 based devices or networks. Use an EIA/TIA T568A or T568B wired Category 5 or better twisted-pair cable to connect T1/E1-B to the external T1 or E1 circuit or equipment. Do not use USOC wired cabling for this connection, as the pairs are not twisted in the required combinations. Table 3-6 gives T1/E1 port pin assignment information.


3-13



3.10.3.6 Timing Ports The MIU-201 also includes separate 6-pin RJ-11 ports for timing input and timing output. The timing input is a balanced RS-422/RS-485 signal for both the Timing In and the Timing Out. The Timing Out connector supplies an external T1 (1.544Mbps) or E1 (2.048Mbps) timing source to synchronize other equipment. The Timing In connector may be linked to an external T1 or E1 clock source to provide network timing for the NIM-1. Tables 3-7 and 3-8 gives pin assignment information specific to MIU201 external timing in and timing out ports. Table 3-7. Pin Assignments for the MIU-201 External Timing In Port Connector

Pin

Description

1

External timing in positive (+)

2

External timing in negative (-)

3

Not used

4

Signal ground

5

Not used

6

Not used

Table 3-8. Pin Assignments for the MIU-201 Timing Out Port Connector

Pin

Description

1

External timing out positive (+)

2

External timing out negative (-)

3

Signal ground

4

Signal ground

5

Not used

6

Not used

3.10.3.7 Redundancy for IP If you have a redundant NIM and are using NetXpress for IP connections only, you can install an MIU201 for each NIM. The MIU-202 pair provides redundancy support for external T1/E1 ports as well as an external timing port.

3.10.4

MIU-202 Connections and Wiring

The MIU-202 pair has the same connections as the MIU-201. After installing and connecting the MIU201-1 and MIU-202-2, connect them with the shipped cable so that automatic failover (switching operation from one NIM to the other) occurs without the need for manually unplugging and plugging cables between the MIU-202s.

3.11 Unit Powering 1. Verify that all modules (NIM-1, CAM, TDM Channel, and Power) are seated snugly. 2. If the shelf is AC powered, plug the AC line cord into the appropriate AC input connector. If you have redundant AC supplies, plug both AC line cords into the appropriate AC input connectors. Note: Before plugging in the AC line cord(s), make sure the socket-outlet is near the NetXpress chassis and easily accessible.

3-14




3. If the shelf is DC powered, turn on the DC input power at the fused power distribution panel. 4. Verify that all four system indicators turn on for each installed power supply. The MAJOR (red) light stays on until the NIM is fully operational. After initialization, the NORMAL (green) light turns on and the MAJOR light turns off. Note: Some newly installed TDM channel modules may initialize in an “out-of-service” state and may cause the MINOR alarm light to remain lit. Section 4.2 – NetXpress Configuration Procedures gives information for clearing MINOR alarm conditions on a module-by-module basis.


3-15

No header here

This page is left blank intentionally.

3-16


No header here

Section 4 – System Configuration and Operation This section gives ●

Configuration procedures to set up your NetXpress system.

●

Configuration options available for your NetXpress system.

●

An explanation of how changes to your system and component settings affect your system’s operation and performance.

●

Page by page descriptions of the NetXpress Web browser interface.

4.1 Software Downloads 4.1.1

Download Current Software

When shipped from the factory, the NetXpress system has the latest software already installed. You should periodically check updates to assure you continue to have the latest version of the NetXpress software. To obtain the software and boot ROM download process in the latest version’s release notes, perform these steps: 1. Go to http://www.gatesair.com. 2. Click Services and Support | Customer Support Portal. 3. At Customer Login, enter your User ID and Password. 4. At Self Service, click Download Software Updates. 5. At the Table of Contents, click Intraplex. 6. At the Intraplex: Table of Contents, click NetXpress. 7. Click the link for the latest version of the NetXpress software. 8. Click Save on the dialog box and save the zipped file to your hard drive. 9. Open the zipped file and open the release notes. 10. Repeat the previous two steps to download the latest version of the MIBs and MIB overview as well. Warning! You cannot navigate in the NIM (network interface module) pages or configure either the primary NIM (in slot 17) or secondary NIM (in slot 15) while programming the boot ROM for either NIM. Do not put either NIM out of service during this programming time. When a NIM goes out of service while programming the boot ROM, the NIM is permanently damaged and must be replaced.

4.1.2

Download Current Software with NIM Redundancy

If you are an existing customer with a single NIM NetXpress system and want to upgrade to the redundant system, perform the procedures outlined in the release notes. Upgrading software to an existing redundant system is automatically handled by the system. When the new software is transferred to the current active NIM, the system automatically transfers it to the standby NIM. Therefore, this process looks exactly like that of a single NIM system. Note: NIM-1 REV B10 or higher supports NIM-1 redundancy. For NIM redundancy, both NIM-1 modules should be REV B10 or higher.


4-1


4—System Configuration and Operation

4.2 NetXpress Configuration Procedures After you confirm your equipment order and make any needed installations (Section 3.3 – Intraplex NetXpress Equipment Unpacking and Installation) perform these configuration procedures.

4.2.1

Connect and Log On to Access NetXpress Home Page

1. Connect a PC directly to the Ethernet MGMT port on the MIU-201 or MIU-202. Note: The MIU automatically senses the media type and you may use a cable wired as straightthrough or a cross-over cable for this connection. Auto-negotiation is the default and your PC must also be set up to auto-negotiate its IP connection. 2. Configure the IP address on the PC to be 192.168.1.10 using netmask 255.255.255.0. 3. Open your Web browser and access the NetXpress multiplexer using the default IP Address 192.168.1.1 for MGMT. 4. A prompt appears requiring you to type a user name and password to access the NetXpress Web Interface. Type the default User name = “admin” and Password = “admin”. 5. Click OK. If the credentials are accepted, the NetXpress Home page appears (Figure 4-1).

Figure 4-1. NetXpress Home Page When you initially connect to the NetXpress system, this Home page appears, showing an overview of the modules installed in the multiplexer. The NetXpress Release system software revision number appears in the upper left of the window. Compare this installed version with the available updates mentioned in Section 4.1 – Software Downloads to assure you are running the most recent version. The downloadable update packages also include installation instructions.

4.2.2

View System Mode

The operating System Mode also appears in the upper left of the Home page.

4.2.2.1

System Mode:

E1

In this configuration the two electrical interfaces (“T1-E1 A” and “T1-E1 B”) communicate using E1 line coding, formats and date rates (2.048Mbps) and all four of the NetXpress busses (TDM1A, TDM1B, TDM2A and TDM2B) run at 2.048Mbps. Installed TDM Channel Modules also need to be E1 compatible in order to operate properly. E1 mode does not support VF-15, VF-16A, VF-25, or VF-28 voice modules. 4-2



4.2.2.2

System Mode:


T1

In this configuration the two electrical interfaces (“T1-E1 A” and “T1-E1 B”) communicate using T1 line coding, formats and date rates (1.544Mbps) and all four of the NetXpress busses (TDM1A, TDM1B, TDM2A and TDM2B) run at 1.544Mbps. Installed TDM Channel Modules also need to be T1 compatible in order to operate properly. T1 mode does not support VF-15E, VF-16AE, VF-25E, VF-28E voice modules. You can change the System Mode using the TDM Bus Information page, covered in 4.4.3.5.

4.2.3

Perform General Setup

To set up delivery of data, voice, or other information from one device to another through the NetXpress system, review each of the next topics.

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.1.1 for the MGMT interface. This can remain unchanged if you only use a direct cable connection on the MIU-201. You can enable remote management on the WAN interface.

●

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 chassis. The WAN interface requires a static IP address. Dynamic addressing of the WAN interface (DHCP) is not supported.

●

192.168.3.1 for the LAN interface. You need to change the default LAN interface to permit internetworking of multiple NetXpress chassis. The WAN interface requires a static IP address. Dynamic addressing of the WAN interface (DHCP) is not supported.

Changes to network interfaces are made using the Network Interface Configuration page (Section 4.4.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 system: 1. Point to Networking and click Forwarding. The IP Routing Table appears (Figure 4-2).

Figure 4-2. Networking | IP Routing Table 2. Click

on the IP Routing Table header. The Create A New Route page appears (Figure 4-3).


4-3



Figure 4-3. IP Routing Table | Create a New Route Page 3. Type the IP Destination. 4. Type the associated Network Mask. 5. Type the Gateway IP address to be used to access this network. 6. At Type, click the interface through which this network is to be accessed by the NetXpress system. 7. Click Create.

4.2.3.3

IP Access List

Only perform these steps as a security measure to lock down the system after setup. 1. Point to Networking and click IP Access List (Figure 4-4).

Figure 4-4. Networking | IP Access List 2. Click 4-5).

on the IP Access List table header. The Create IP Access List Entry page appears (Figure

Figure 4-5. IP Access List | Create IP Access List Entry Page 3. Click the Interface to customize (MGMT, WAN, or LAN). 4. Type the IP Address of the host to allow access. 5. Click Submit.

4-4



4.2.3.4


T1/E1 System Mode Selection

The default NetXpress system mode setting is E1. Perform these steps to set the NetXpress system to T1 mode. 1. Click System Cfg | TDM Bus Config. The TDM Bus Information page appears (Figure 4-6).

Figure 4-6. System Cfg | TDM Bus Information Page 2. At Configured System Mode, click the T1 option. 3. Click Submit. 4. Click System Cfg | Software Load Image. The Software Load Image Configuration page appears (Figure 4-7).


4-5



Figure 4-7. System Cfg | Software Load Image Configuration Page 5. Change the Primary FPGA Image Filename to a T1 FPGA file name. 6. Click Submit. 7. Click Reset Module. To change the system setting from T1 to E1, repeat these steps, clicking the E1 option in Step 2 and changing to an E1 FPGA file name in Step 5.

4.2.3.5

T1/E1 Interface

Perform these steps to configure your T1/E1 ports and put them in service. 1. Point to System Cfg and click T1 Interface/E1 Interface. 2. Click on the Port A row. Either the T1 Interfaces Table or the E1 Interfaces Table appears, depending on whether your NetXpress system is set for T1 or E1 (Figure 4-8).

4-6




Figure 4-8. System Cfg | Interfaces Table – Port A Configuration 3. At Configuration for Port A, type the Circuit Identifier. 4. To enable one of the Local Loopback Modes, click the appropriate option (Payload, Line, or Equipment; default is None). 5. Click the appropriate Line Coding option for your circuit. (T1 default is B8ZS, E1 default is HDB3). 6. Click the appropriate Framing Type (T1 default is ESF, E1 default is (CAS) with CRC). 7. For T1 interface, click the Line Build Out (-7.5dB, -15dB, -25dB, default is 0dB) to configure the line build out according to the specifications from your T1 service provider. 8. To generate an SNMP trap when the circuit changes state, select the Enable Traps On Line Status Change check box. 9. For enhanced performance, select the Use Robust Framing check box. 10. Click Submit. 11. Click

on the Port B row.

12. Repeat the previous steps from the Port B row to configure Port B and put it in service.

4.2.3.6

Stream Creation – TDM to TDM

1. Click Streams on the navigation bar (Figure 4-9).


4-7



Figure 4-9. Streams Page 2. Click 4-10).

on the Streams table header. The Stream Creation – Stage 1 page appears (Figure

Figure 4-10. Streams | Stream Creation – Stage 1 Page 3. On the Stage 1 page, perform these steps: a. b.

4-8

Type a unique Stream Name. At Stream Type, click the TDM to TDM option. The Stream Direction options change to One Way and Both (Figure 4-11).




Figure 4-11. Streams | Stream Creation – Stage 1 (TDM to TDM) Page c. d.

At Stream Direction, either accept the default (One Way) or click the Both option to receive and transmit. Click Next. The Stage 2 page appears (Figure 4-12).

Figure 4-12. Stream Creation – Stage 2 (TDM to TDM) Page 4. On the Stage 2 page, perform these steps: a. b. c. d. e. f. g.

Click a Source TDM Bus for the stream (TDM 1A, TDM 1B, TDM 2A, TDM 2B, T1/E1 Port A, T1/E1 Port B). Click the Destination TDM Bus for the stream (TDM 1A, TDM 1B, TDM 2A, TDM 2B, T1/E1 Port A, T1/E1 Port B). Type the Source TDM Channel Start (default is 1). Type the Destination TDM Channel Start (default is 1). Type the Source TDM Channel Range (default is 1). Type the Destination TDM Channel Range (default is 1). If applicable, select the Enable Voice Signaling check box.


4-9


h. i. j.

k. l.


 If you selected the check box, go to h.  If you did not select the check box, go to j. (Visible when Enable Voice Signaling check box is selected) Select the Voice Card Used from the drop-down list or select Enter signaling insertion byte to type a byte value. (Visible when Enable Voice Signaling check box is selected) This field is populated based on the voice card selected. If you selected Enter signaling insertion byte from the Voice Card Used drop-down list, type the value here. At the Stream Program Type list, click Linear Audio/Voice for linear modules (the default is Compressed Audio/Data). The Packet Underrun Byte is automatically set by the Stream Program Type. To set the underrun byte amount yourself, click Enter underrun value manually and then type the Packet Underrun Byte. Click appropriate number slots to set the Frameloss Mask (a number slot becomes yellow when selected). Section 4.4.5.1 Stream Creation gives more information on frameloss masking. Click Next. The Summary page appears (Figure 4-13).

Figure 4-13. Stream Creation Summary (TDM to TDM) Page 5. On the Summary page, note the settings. If you need to change any, click Prev until you reach the appropriate page and make your changes. 6. When the stream variables are correct on the Summary page, click Create & Activate to create the stream and put it in service.

4.2.3.7

Stream Creation – TDM to IP

1. Click Streams. 2. Click

on the Streams table header.

3. On the Stage 1 page, perform these steps: a. b. c. d.

4-10

Type a unique Stream Name. At Stream Type, click the TDM to IP option. At Stream Direction, click an option if different than Receive (Transmit or Both; default is Receive). Click Next. The Stage 2 page appears (Figure 4-14).




Figure 4-14. Stream Creation – Stage 2 (TDM to IP) Page 4. On the Stage 2 page, perform these steps: a. b. c. d. e. f.

For Forward Error Correction, click the Low or High option. For a Transmission Type other than Unicast, click Multicast; default is Unicast). For voice signaling, select the Enable Voice Signaling check box. If echo cancellation is installed and needed for this stream, select the Enable Echo Cancellation check box. (This check box does not appear if no echo cancellation is installed.) Type the Statistics Measurement Interval if different than 5 (default is 5). Click Next. The Stage 3 page appears (Figure 4-15).

Figure 4-15. Stream Creation – Stage 3 (TDM to IP) Page 5. On the Stage 3 page, perform these steps: a. b. c. d. e. f.

Type the Destination IP Address. Type the Local UDP Port. Type the Remote UDP Port. For a CoS Priority other than Normal, click an option (Low, Medium, or High; default is Normal). To change the packet Time to Live (TTL) time period, type a number at Egress IP Pkts. TTL (default is 5). Click Next. The Stage 4 page appears (Figure 4-16).


4-11



Figure 4-16. Stream Creation – Stage 4 (TDM to IP) Page 6. On the Stage 4 page, perform these steps: a. b. c. d. e. f. g. h. i.

4-12

Click appropriate number slots to set the Frameloss Mask (a number slot becomes yellow when selected). For a TDM Bus other than TDM Bus 1A, click a bus from the list (TDM Bus 2A, TDM Bus 1B, TDM Bus 2B, T1/E1 Port A, T1/E1 Port B; default is TDM Bus 1A). Type the TDM Bus Starting Channel (default is 1). Type the TDM Bus Channel Range (default is 1). Type the TDM Bus Frames per Packet (default is 200). For Jitter Buffer Size packets other than 32, click a number from the list (8, 16, or 64; default is 32). At the Stream Program Type list, click Enter underrun value manually or Linear Audio/Voice or accept the default: Compressed Audio/Data. If you selected Enter underrun value manually, type a number for Packet Underrun Byte. Click Next. The Summary page appears (Figure 4-17).




Figure 4-17. Stream Creation Summary (TDM to IP) Page 7. On the Summary page, note the settings. If you need to change any, click Prev until you reach the appropriate page and make your changes. 8. When the stream variables are correct on the Summary page, click Create & Activate to create the stream and put it in service

4.2.3.8

System Timing Configuration

1. Point to System Cfg and click System Timing (Figure 4-18).


4-13



Figure 4-18. System Cfg | System Timing Page 2. Click a selection from the Primary Timing Source list for the NetXpress shelf (Internal, External, Stream, E1/T1 Port A, E1/T1 Port B, Synchrocast). Notes: You cannot change stream timing if the stream is currently active. If you selected Stream timing, click an available Primary RX Timing Stream from the list. The stream is not available if it is in service. (You must have a configured stream available. Section 4.4.5 – Configure Streams gives additional information.) 3. If you selected External timing, connect a timing cable from the external clock source to the Timing In on the MIU-201. 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 continue to report an alarm (Major red light) or alert (Minor yellow light) until it has successfully synchronized to the new system timing. 5. After configuring the peer to this NIM-1 in another chassis, verify the current operational status (up, down) of the primary timing source.

4.2.3.9

SNMP Community

You only need to perform this procedure if you use SNMP. Section 2.3.4 – SNMP Communities gives more information. If you only use the NetXpress software, this procedure is not necessary. 1. Point to Networking and click SNMP. The SNMP Configuration page appears (Figure 4-19).

4-14




Figure 4-19. Networking | SNMP Configuration Page 2. Type the SNMP Read-Only Community name for read-only access. 3. Type the SNMP Read-Write Community name for read/write access. 4. Click Submit.

4.2.3.10 Configuration Backup/Restore You can operate the NetXpress multiplexer without performing this procedure. However, we recommend you save your configuration files. 1. Point to System Cfg and click Configuration Backup (Figure 4-20).

Figure 4-20. System Cfg | Configuration Files Backup/Restore Page 2. Type the Config Backup Server IP address, the address of an available FTP server. 3. Type the Config Backup Server Directory where the configuration files should be stored. 4. Type the Username. 5. Type the Password. 6. Click Submit to store these values. 7. Click

on the Streams table header to back up the configuration files to the server.


4-15



4.3 Network Interface Module (NIM) Redundancy 4.3.1

Redundancy Terms

In all manual discussions, guidelines, and procedures regarding redundancy, remember these terms and their definitions: ●

Primary NIM: The NIM in slot 17.

●

Secondary NIM: The NIM in slot 15.

●

Active NIM: The role of a NIM currently providing operational services, either the Primary or Secondary NIM.

●

Standby NIM: The role of a NIM that is either synchronized with or in process of synchronizing with the Active NIM and can take over the role of Active NIM. The Standby NIM can be either the Primary or Secondary NIM.

●

Switch to Standby NIM: When the current Active NIM fails, the Standby NIM changes its role to Active.

●

Switch back to Primary NIM: When the Active NIM in the Secondary slot (in slot 15) fails, the Standby NIM in the Primary slot (in slot 17) takes over as the Active NIM.

4.3.2

Redundancy Capabilities

You can have two NIMs in a NetXpress system, one in slot 17 (called the Primary NIM) and the other in slot 15 (called the Secondary or Redundant NIM). NIM redundancy gives you these capabilities: ●

Module failure redundancy – When the Active NIM fails, or you take it out of service, or you physically take the module out of the slot, the Secondary NIM automatically takes over.

●

User control of failover – You can set the administrative state of the Standby NIM to Out of Service so that, if the Active NIM fails, the Standby NIM does not take over. As long as there are two NIMs in the system, the Out of Service NIM does not take on the role of Active NIM.

●

Automatic switchback from Secondary to Primary NIM with user configurable options – You can configure conditions regarding when the Primary NIM takes over for the Secondary NIM.

●

Manual switchover to Standby NIM – You can manually switch the Standby NIM over to an Active role.

●

Automatic synchronization of configuration and load images – You can set the NIM to automatically synchronize so that whatever configurations occur on the Active NIM also occurs on the Standby NIM.

●

User control for disabling synchronization – You can turn off the automatic synchronization and manually synch the NIMs.

●

MIU-202 module interface pair – This module pair is used when you have a secondary NIM, with the MIU-202-1 installed in slot 17 and the MIU-202-2 installed in slot 15.

4.3.3

Redundancy Synchronization

When the system starts up, it first determines which NIM is Active and which is Standby. If both NIMs are functional at startup, the Primary NIM (in slot 17) becomes Active. The Active NIM starts up normally with the stored configuration. You can decide whether the NIMs are automatically synchronized or not. The auto-sync option is disabled (turned off) by default. When you enable auto-sync, the NIMs are synchronized, so the system copies configuration and load images from the Active NIM to the Standby NIM. Therefore, when you start up (give power to) the system, the Standby NIM synchronizes its load image files and then its configuration files to those of the Active NIM. Note: The standby NIM is not in a Ready state until it completes synchronizing its load image files and its configuration files. During the load image synchronization stage, the Standby NIM may restart automatically if it needs to install another image file. 4-16




When you upgrade the application and boot ROM on the Active NIM, all changes on the Active NIM are automatically copied to the Standby NIM. Also, whenever a change occurs in the system, such as a channel module configuration change or a stream put in service or out of service, that change is copied from the Active NIM to the Standby NIM. Even when you place Standby NIM Out of Service, any changes in the Active NIM are copied to the Standby NIM. Conversely, if auto-sync is disabled, the Standby NIM does not copy information from the Active NIM. When you start up (give power to) the system and auto-sync is disabled, the Standby NIM does not compare its information to the Active NIM and copy anything that is different. When you upgrade the application and boot ROM on the Active NIM, no changes occur on the Standby NIM. When a change occurs in the system, no changes occur on the Standby NIM. You can manually synchronize the Standby NIM as well. When you manually synchronize the Standby NIM, all changes on the Active NIM are copied to the Standby NIM. Make sure you want all changes in the Active NIM copied to the Standby NIM as well before enabling auto-sync. Determine whether you want to control synchronization between the NIMs and manually sync them or allow the system to synchronize them by auto-sync. The Activity indicator light on the Standby NIM displays various colors and patterns during and after synchronization. This light is not visible behind the NetXpress cover. If you usually keep the cover on your NetXpress system, skip to 4.4 – NetXpress Pages. The Activity indicator light turns yellow when the Standby begins to synchronize files. It might remain yellow from a few seconds to a few minutes, depending on the number and size of files to be copied from the Active to the Standby. If auto-sync is enabled, whenever a configuration file changes on the Active NIM, the Activity light on the Standby turns yellow while the file is being copied, usually 1-2 seconds. When larger files (such as software load image files) are copied, the yellow light stays on as long as the files are being copied, sometimes several minutes. After the Standby NIM initials starts up and syncs, or after you manually sync the Standby NIM, the Activity light blinks in one of three patterns of colors: ●

Ready: three short green blinks, pause, three short green blinks, pause, three short green blinks. This means the Standby NIM is operating with the auto-sync enabled, it has completed synchronization with the Active NIM, and it is ready to take over as Active NIM if it needs to.

●

Ready-Not-Synced: three short yellow blinks, pause, three short yellow blinks, pause, three short yellow blinks. This means the Standby NIM is operating with the auto-sync disabled but the Standby has completed booting with the files it has. If it needs to take over as Active NIM, it uses the files it has, which may not be the same files as those on the presently Active NIM.

●

Error: five short red blinks, pause, five short red blinks, pause, five short red blinks. The synchronization failed in some way. The Standby NIM is not synchronized with the Active NIM. If the Active NIM fails, or you take it out of service, or you physically take the module out of the slot, the Standby NIM may or may not be able to take over.

4.4 NetXpress Pages 4.4.1

Start at NetXpress Home Page

The starting point for all system configuration activity is the NetXpress Home page (Figure 4-21). The Home page provides user access to configuration pages at the system level and at the individual module level. It also provides a mechanism for controlling account security and individual user access.


4-17



Figure 4-21. NetXpress Home Page Use the navigation pane (left of the Home page) to move between pages. Each menu accesses one or more pages. Home: The NetXpress Home page. Faults: Various alarm pages. System Cfg: System configuration pages. Networking: Networking parameters pages. Streams: View and manage data streams. Performance: View and manage system performance data. Accounts: Account security settings/user access. Utilities: The Ping Utility page. The blank gray slots on the page indicate places for additional modules, Network Interface Module (NIM), or power supplies. The populated slots indicate modules, NIM, and power supplies presently on the NetXpress multiplexer. The top of a module slot shows the TDM bus associated with the module and the SCB address of the module. Note: The address shown for each module is the SCB address, not the physical slot address. Although not necessary, it is a good practice to set the SCB address (via dip switches on the module) to match the physical slot address in the shelf. The installation section of each channel module’s Installation and Operation manual gives module-specific dip switch settings.

4-18



4.4.1.1


NetXpress Channel Modules

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

4.4.1.2

NetXpress Network Interface Modules (NIMs)

The top of the NIM slots (15/17) indicate their slot positions. Here are other page components of a NIM slot: WAN: Green if NIM is running on Wide Area Network (WAN). LAN: Green if NIM is running on Local Area Network (LAN). MGMT: Green if NIM is running on Management network (MGMT). Loopback: Green if set in Loopback mode. T1/E1 A: Green if Port A is in service. T1/E1 B: Green if Port B is in service. Timing: Green if on primary timing; yellow if on secondary; red if timing fallout. Active: Green if NIM is active.

4.4.1.3

NetXpress Power Supply Slots

The top of a power supply slot (PS Main/PS Red) indicates whether it is the main or the redundant power supply. The bottom of the power supply slot, directly above the Open button, shows the type of power supply. Here are page components of a power supply slot: Normal: Green if power is on and there are no alarms/alerts. Major: Red if in alarm condition. Minor: Yellow if in alert condition. ACO: Alarm Cut Off; green if active. The Refresh fields at the bottom left of the Home page appear on most NetXpress pages. Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals.

4.4.2

Define and Review Fault Information Use the Faults information pages to define and review NetXpress system faults (major and minor alarms) and configure the System Log Server. To access the pages, point to Faults on the navigation panel and click Current Alarms, Alarm Definition, Alarm History, syslogd Server Config, or System Log Files.


4-19


4.4.2.1


Current Alarms

Click Current Alarms on the Faults menu and the Current Alarms page appears (Figure 4-22). Click any table header to sort alarm entries in ascending order by that header. Click the table header a second time to sort in descending order.

Figure 4-22. Current Alarms Page Date: The date and time the alarm occurred. Severity: The seriousness of the alarm (Major, Minor, None). Description: Helpful details about the alarm. Clear fault: Click from the table.

4.4.2.2

to delete this alarm from the table. Click

in the table header to delete all alarms

Alarm Definitions

Click Alarm Definitions on the Faults menu, and the Alarm Definitions page appears (Figure 4-23).

Figure 4-23. Alarm Definitions Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. ID: The specific alarm. Message: The description of the alarm event. Severity: The seriousness of the alarm (Major, Minor, or None). Trap ID: The SNMP trap associated with the alarm. Trap: Whether the trap is enabled or disabled. If it is enabled, the trap is sent to the host. LED: Whether the light is enabled (turned on) or disabled. Threshold time: The amount of time for the system to send the trap and control light (indicator). Edit definition: Click When you click alarm.

4-20

to edit the alarm definition.

on the row of a specific alarm, a Definition edit page (Figure 4-24) appears for the




Figure 4-24. Alarm Definition Edit Page Severity: Identifies the severity level of the alarm. Click an item on the list: none, major, minor, major clear, or minor clear. Threshold time: Defines the amount of time before the system sends traps and changes the lights accordingly. Click a time interval in seconds: none, 1 sec, 2 sec, 3 sec, 4 sec, or 5 sec. Trap: Click either the enabled or disabled option. If enabled, the trap is sent to the management station (host). LED: Click either the enabled or disabled option. If enabled, the major or minor light is turned on. Back: Click this button to return to the Alarm Definitions table without applying entries. Reset: Click this button to change page fields back to the original values. Submit: Click this button to apply the values entered on this page.

4.4.2.3

Alarm History

Click Alarm History on the Faults menu and the Alarm History page (Figure 4-25) appears.

Figure 4-25. Alarm History Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. Behavior When History Is Full: When the history table fills, click Stop for no more entries or Wrap to overwrite the table entries. Date: The date and time the alarm occurred. Severity: The importance of the alarm (Major, Minor, or None). Description: The details of an alarm event. Clear alarm history table: Click

4.4.2.4

on the table header to delete all history table entries.

System Log Server Configuration

Click syslogd Server Config on the Faults menu, and the System Log Server Configuration page (Figure 4-26) appears. GatesAir, Inc. Intraplex Products

4-21



Figure 4-26. Remote Log Server Page syslogd Server IP Address: Sets the system log server IP address. syslogd Server UDP Port Number: Indicates the port to which the NetXpress system log client sends messages. Default is 514. Enable Logging to syslogd Server: Select this check box to send messages to the syslogd server. Reset: Click to clear any configuration changes without applying the changes. Submit: Click to apply all configuration changes to this page.

4.4.2.5

System Log Files

Click System Log Files on the Faults menu, and the System Log Files table appears (Figure 4-27). If enabled, all alarms are kept in text format in a file on the NIM’s flash (/RFA/log/syslog1.txt or /RFA/log/syslog2.txt). System log files are limited in size (1 mb). You can configure the NetXpress system to automatically use File Transfer Protocol (via FTP client software) to transfer log files to an FTP server when log files are full.

Figure 4-27. System Log Files Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. Enable System Logging: Enables/disables the internal storing of system log messages. System Log Directory on FTP Server: Sets the system log server directory. System Log Filename on FTP Server: Name assigned to system log file on the FTP server. System Log FTP Server User Name: FTP username on remote FTP server. 4-22




System Log FTP Server Password: Sets the FTP server password. System Log FTP Server IP Address: IP Address of FTP server to which the NetXpress system offloads system log files. Enable Automatic System Log FTP Transfer: Enables/disables automatic transfer of log files to an FTP server when log files are full. Reset: Click this button to clear any changes without applying the changes. Submit: Click this button to apply all changes to this page. Name: The system log file name. Type: The type of system log file. Status: The status of the system log file (active or backup). Size: The current size of the system log file. Last modified: The date and time the system log file was last modified.

4.4.3

Configure the System

System Configuration involves these pages: General: The general setup page for NIM. IP Interfaces: The IP Interfaces table for NIM. E1 Interfaces: The E1 Interfaces table for NIM. T1 Interfaces: The T1 Interfaces table for NIM. TDM Bus Config: TDM bus information. Media Switch Map: Automatically set TDM bus maps. System Timing: System timing information. TOS Byte Definitions: Outbound packet TOS byte information. Software Load Image: Software load management information. Configuration Backup: Configuration backup server information. Redundancy: Redundancy configuration and system synchronization.

4.4.3.1

General Setup

Use the General Setup page to type and maintain general configuration information for the Network Interface Module (primary or redundant) selected. Point to System Cfg and click General (Figure 428). You can also reach this page by clicking the NIM module’s Open button on the NetXpress Home page.


4-23



Figure 4-28. General Setup Page Refresh: Click this button to refresh this page in your browser. System Name: User-defined name given to the NetXpress Network Interface Manager (NIM). Default = netXpress. This name appears in the browser window and is assigned to the browser task name. This helps identify the system when managing multiple NetXpress systems on one work station. System Description: Identifier describing the currently installed NetXpress application image. Readonly. System Location: User-defined physical location of the NetXpress system. Default = Mason, OH. Contact Person: User-defined name or e-mail address of the support contact person. System Up Time: Length of time since the last system restart. Read-only. Current Date (YYYY-MM-DD): Current system date. Current Time (HH:MM:SS): Current system time. Daylight Savings Time Start Date (MM-DD): Daylight savings time Start Date. User-defined. To change, select the present entry and type a two-digit number for the month, a hyphen, and then a twodigit number for the day of the month (for example, April 1 = 04-01). Daylight Savings Time End Date (MM-DD): Daylight savings time End Date. User-defined. To change, select the present entry and type 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). Enable SNTP: Enables/disables 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 system through one of its IP network interfaces. In some configurations, you might need to add a route to the forwarding table before the NetXpress 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. GMT Offset: Indicates the offset for the local time in +/- minutes from the GMT time. User-defined if SNTP is enabled. SNTP Server Address: IP address of the SNTP Server. 4-24




SNTP Server Status: Indicates whether the SNTP Server was reached at the specified IP address. Reset: Click this button to clear all recent configuration entries and/or changes and return to previous values. Submit: Click this button to apply setup changes.

4.4.3.2

Interfaces Table

Use the Interfaces Table to view NIM interface statistics. Point to System Cfg and click IP Interfaces. Once the Interface Table appears, click to view statistics for the interface that you selected. Figure 4-29 shows information for the WAN interface. Note: If WAN redundancy is enabled, the Operational State and Administrative State columns for the LAN interface are Redundant.

Figure 4-29. Interfaces Table Refresh: Click this button to refresh this page in your browser. Interface: Identifies the NetXpress IP interface. Type: Interface type (from MIB-II specification). Speed/Duplex: Interface speed/Duplex state. Operational State: Current operational state of the interface. Administrative State: Current administrative state, which is user defined as either in service or out of service.


4-25



Physical Address: MAC (Media Access Control) access. The Physical Address is an identifier that is embedded in the Ethernet interface. Read Only. MTU: Maximum Transmission Unit for the interface (in bytes). This is the largest size packet that the NetXpress system transmits on the interface. Put in service/out of service: Click to put the specific interface in service. Click to put the specific interface out of service. An interface must be out of service to effect any configuration changes. Show interface statistics: Click

to show the statistics for the specific interface.

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. Total Octets Received: Total number of octets (8-bit data units) successfully received by the interface. Total Octets Sent: Total number of octets successfully transmitted by the interface. Unicast Packets Received: Number of unicast (information sent from one point to another point) packets received by the interface. Unicast Packets Sent: Number of unicast (information sent from one point to another point) packets sent by the interface. Non-Unicast Packets Received: The number of non-unicast (that is, multicast or broadcast) packets received by the interface. Non-Unicast Packets Sent: The number of non-unicast (that is, multicast or broadcast) packets sent by the interface. Receive Errors: Number of packet receiving errors encountered by the interface. Transmit Errors: Number of packet transmission errors encountered by the interface. Input Packets Discarded: Number of input packets discarded due to size, timing, buffer availability, and so forth Output Packets Discarded: Number of output packets discarded due to size, timing, buffer availability, and so forth Unknown Protocols Received: Number of non-standard or undefined protocols received by the interface. Output Queue Length (packets): Number of output packets that can be stored in the queue by the interface. Last State Change: Number of days, hours, minutes, and seconds since the interface statistics were last updated.

4.4.3.3

E1 Interfaces Table

Access the E1 Interfaces Table (Figure 4-30) to view information for Ports A and B and to put a port in or out of service. Point to System Cfg and click E1 Interfaces. Note: E1 Interfaces is available in the System Cfg menu only when the TDM Bus (from System Cfg menu) has been configured for E1 System Mode, and the NIM has loaded an E1 version of the FPGA Image File. On the E1 Interfaces Table, click

4-26

for the specific port to view or edit the configuration of that port.




Figure 4-30. E1 Interfaces Table Refresh: Click this button to refresh this page in the browser. Interface: The available ports. Last Status Change: The day, date, and time of the last state change on the designated port. Line Status: The line operational state and error indications that the interface is sending and receiving, if any. Admin State: Whether the port is in or out of service. Loopback Status: The local loopback mode for the selected interface. Shows when a loopback is activated (yellow) or not (gray). If the port is not in service, or is in service with no active loopback, the Loopback Status is None. Normal operating mode = None. Desired Loopback: The local loopback mode configured for this port: Payload, Line, Equipment, or None. Default = None. Put port in service/out of service: Click service. Configure: Click

to put the port in service. Click

to take the port out of

for a specific port to view configuration details and configure the port.

Circuit Identifier: This identifier is the name you specify to identify the E1 interface. The name can only be changed while the interface is out of service. Framing Type: ●

Click CAS (Channel Associated Signaling) to enable the framing mode that is required for signaling support of voice frequency (VF) TDM channel modules. In CAS framing mode channel of the E1, 16 is reserved for voice channel signaling and is therefore not available for any payload data.

●

Click CCS (Common Channel Signaling) framing type when support for voice frequency modules is not required. In CCS framing all 31 channels are available for payload data.

CAS and CCS are each available with or without CRC (cyclical redundancy check). It is important to select the Framing Type that matches the hardware equipment connected to the E1 interface. Line Coding: ●

Click HDB3 (High Density Bipolar 3) for a modified bipolar line code in which strings of four zeros are replaced by zero-substitution codes. HDB3 is the factory default line code.

●

Click AMI (Alternate Mark Inversion) if you need to enable this legacy line coding. (AMI cannot support 64 kbps clear channel operation.)


4-27



Local Loopback Mode: Select a mode and click Submit to test an E1 interface. ●

Payload Loopback Mode: Traffic is received from the E1 interface to the NIM and the same traffic is re-transmitted out the E1 interface.

●

Line Loopback Mode: Traffic is received from the E1 interface to the NIM and the same traffic is transmitted directly out the E1 interface.

●

Equipment Loopback Mode: Local NIM traffic is transmitted out the E1 interface and also returned directly to the NIM.

●

None: The system default. No loopback enabled, allowing normal traffic through the E1 interface.

Enable Traps On Line Status Change: Select this check box to generate SNMP traps whenever there is a change of line status. Use Robust Framing: Select this check box for the interface to prevent the generation of an OOF (Out Of Frame) line code on the E1 interface until 4 consecutive framing bits are lost, as opposed to one frame bit error in the normal framing mode. Reset: Click this button to clear all recent E1 interface entries and/or changes and return to previous values. Submit: Click this button to apply all E1 interface changes.

4.4.3.4

T1 Interfaces Table

Access the T1 Interfaces Table (Figure 4-31) to view information for Ports A and B and put a port in or out of service. To access the page, point to System Cfg and click T1 Interfaces. Note: T1 Interfaces is available in the System Cfg menu only when the TDM Bus (from System Cfg menu) has been configured for T1 System Mode, and the NIM has loaded a T1 version of the FPGA Image File. On the T1 Interfaces Table, click

for the specific port to view or edit the configuration of that port.

Figure 4-31. T1 Interfaces Table Refresh: Click this button to refresh this page in the browser. 4-28




Interface: The available ports. Last Status Change: The day, date, and time of the last state change on the designated port. Line Status: The line operational state and any error indications that the interface is sending and receiving, if any. Admin State: Whether the port is in or out of service. Loopback Status: The local loopback mode for the selected interface. Shows when a loopback is activated (yellow) or not (gray). If the port is not in service, or is in service with no active loopback, the Loopback Status is None. Normal operating mode = None. Desired Loopback: The local loopback mode configured for this port: Payload, Line, Equipment, or None. Default = None. Put port in service/out of service: Click service. Configure: Click

to put the port in service. Click

to take the port out of

for a specific port to view configuration details and configure the port.

Circuit Identifier: This identifier is the name you specify to identify the T1 interface. The name can only be changed while the interface is out of service. Framing Type: Click a type from the drop-down list. ●

Click ESF (Extended Super Frame) for interoperability with contemporary T1 devices.

●

Click D4 (Super Frame) if you need to enable this legacy framing type. It is important to select the Framing Type that matches the hardware equipment connected to the T1 interface.

Line Coding: Click an option. ●

Click B8ZS (Bipolar with 8 Zero Substitution) for a modified bipolar line code in which strings of eight zeros are replaced by zero-substitution codes. B8ZS is the factory default line code.

●

Click AMI (Alternate Mark Inversion) to enable this legacy line coding. (AMI cannot support 64 kbps clear channel capacity.)

Local Loopback Mode: Click a mode and click Submit to test a T1 interface. ●

None: The system default. No loopback enabled, allowing normal traffic through the T1 interface.

●

Payload: Traffic is received from the T1 interface to the NIM and the same traffic is re-transmitted out the T1 interface.

●

Line: Traffic is received from the T1 interface to the NIM and the same traffic is transmitted directly out the T1 interface.

●

Equipment: Local NIM traffic is transmitted out the T1 interface and also returned directly to the NIM.

ATT TR54016 Performance Reports: Select this check box to enable the transmission of AT&T TR54016 formatted performance reports on the Facilities Data Link (FDL). ANSI T1.403 Performance Reports: Select this check box to enable the transmission of ANSI (American National Standards Institution) T1.403 formatted performance reports on the FDL. Line Build Out: If the CSU is enabled for the interface, the Line Build Out defines the signal level for the interface in dB. Possible choices are 0 dB, -7.5 dB, -15 dB, and -22.5 dB. With the CSU disabled, Line Build Out specifies the length of the cable from the NetXpress system to the externally connected CSU/DSU. Possible choices are 0 – 133ft, 133 – 266ft, 266 – 399ft, 399 – 533ft, and 533 – 655ft. Enable CSU: Select this check box to enable the external CSU (Channel Service Unit) when you are connecting the NetXpress T1 port directly to the Telco network. If you are connecting to an external CSU/DSU, do not check this box. Enable Traps On Line Status Change: Select this check box to generate SNMP traps whenever there is a change of line status.


4-29



Use Robust Framing: Select this check box for the interface to prevent the generation of an Out Of Frame (OOF) line code on the T1 interface until 4 consecutive framing bits are lost, as opposed to one frame bit error in the normal framing mode. Reset: Click this button to clear all recent T1 interface entries and/or changes and return to previous values. Submit: Click this button to apply all T1 interface changes.

4.4.3.5

TDM Bus Information

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

Figure 4-32. TDM Bus Information Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. TDM Bus: The specific TDM bus location. Signaling: The signaling mode for the bus, either None or CAS in E1 mode. When the system is in T1 mode, the signaling mode for the TDM busses is always robbed bit signaling (RBS). 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 modules are 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 loopback configuration details (Figure 4-34) and configure loopback operations for the bus. Current System Mode: Indicates whether the internal TDM busses and the external TDM interfaces are operating in E1 or T1 mode. 4-30




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-33) reminding you to re-configure the FPGA image to reflect this change.

Figure 4-33. Changes to System Mode Dialog Box Go to System Cfg | Software Load Image to complete this system mode change. Submit: Click this button to change the current system mode.

Figure 4-34. TDM Bus Configuration Edit Page Refresh: Click this button to refresh the browser. Signaling: Specifies the signaling type (none or CAS) in E1 configurations. If CAS is selected, channel 16 is not reserved for signaling and is unavailable for TDM channel module traffic. Internal Loopback Settings: 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: 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 delete and NOT save any changes. Submit: Click this button to apply all bus configuration changes.

4.4.3.6

Media Switch Map

The NetXpress system contains a switch fabric on the NIM-1 that allows the interconnection of ten TDM busses in the system: the four internal TDM busses, the two external T1/E1 ports, and the four TDM GatesAir, Inc. Intraplex Products

4-31



busses on the TDM-IP engine ASIC. To send data from the external ports or internal TDM busses over the IP network, they must be connected in the switch fabric to one of the four busses on the TDM-IP ASIC. Any number of time slots from one bus can be connected to another, and the same time slot from a bus can be connected to multiple receive busses. This allows the complex switch maps to be created to support applications such as IP multi-unicasting, simulcasting audio or data over the IP network and a T1/E1 interface, or drop and insert of time slots between the external T1/E1 ports and the internal TDM busses. Access the Media Switch Map page to view each of the available target receive endpoints (TDM1A, TDM2A, TDM2A, TDM2B, E1/T1-A, E1/T1-B, IP1, IP2, IP3, and IP4) shown as individual columns and the source transmit endpoint (where each target receives its data) for all of the available channels. Each item is capable of bidirectional communication, so the names for transmit endpoints are the same as those for receive endpoints. The name of an endpoint associated with a particular channel in the table describes the source of data for that channel. To access the page, point to System Cfg and click Media Switch Map (Figure 4-35).

4-32




Figure 4-35. Media Switch Map Page – E1 Mode This figure shows an E1 system mode. A T1 system mode shows 24 channels. Individual streams have different colors to better identify the same stream in different buses and channels. Therefore, time slots associated with the same stream have the same color. In addition, receive streams that share the same incoming IP stream have the same color. (In this example, there are several time slots with identical colors in Figure 4-35 to show they share the same stream. Also, Streams 13, 16, 17, 18, and 19 share the same source and are therefore all colored beige.)


4-33



Refresh: Click this button to refresh the browser. Chan: This row indicates the specific TDM bus channel that this configuration pertains to. TDM 1A, TDM 1B, TDM 2A, TDM 2B: The four TDM busses. E1 A, T1 A, E1 B, T1 B: The E1 or T1 ports. IP 1, IP 2, IP 3, IP 4: The IP connections. Echo Cancellers: If echo cancellers are installed on the NIM module, additional columns appear for the transmit (Echo AO, Echo BO) and receive (Echo AI, Echo BI) endpoints on these modules.

4.4.3.7

System Timing

Access the System Timing configuration page (Figure 4-36) to view and configure primary and secondary NetXpress system timing information. The NetXpress system supports these methods of timing: Internal, External, Stream, E1/T1, and SynchroCast3. To access the page, point to System Cfg and click System Timing. Note: When you are configuring several receive streams and you are using a stream as the timing source, it is highly recommended that the stream with the highest packet rate (that is, the lowest number of frames per payload value) be used as the primary timing stream.

Figure 4-36. System Timing Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. Current Timing Source: The timing source the system currently uses. If both the primary and secondary timing sources have failed, the system operates on its internal clock. PLL Status: The Phase-Locked Loop (PLL) status (locked, unlocked) indicates when the NetXpress system is operating synchronously with the current timing source. The status is Unlocked when both the primary and secondary timing sources are unavailable, so this NetXpress system is running asynchronously. Primary Timing Source Status: The current operational status (up, down) of the primary timing source.

4-34




Secondary Timing Source Status: The current operational status (up, down) of the secondary timing source. Primary Timing Source: The primary timing source for the NetXpress shelf. Timing choices are Internal, External, Stream, E1/T1 Port A, E1/T1 Port B, or SynchroCast3. Internal can only be chosen as the Primary Timing Source for a single NetXpress system within your network. All remaining NetXpress systems can derive that same timing source using Stream or E1/T1 timing. Multiple systems can be set to External Timing if a common source of external timing is available at all locations. This is typically a satellite (GPS) derived clock or a public telecom network clock source. External timing must be cabled into the NetXpress system using the TIMING IN jack on the MIU-201. Streams must be placed out-of-service to change the primary or secondary timing source selection. SynchroCast3 is a valid choice for timing only if you have an SNC-101T module installed in the NetXpress system. If you selected SynchroCast3 timing as the primary timing source, you cannot select External as the secondary timing source. Secondary Timing Source: The secondary timing source for the NetXpress shelf. Choices are Internal, External, Stream, E1/T1 Port A, or E1/T1 Port B. 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. Primary RX Timing Stream: If the primary timing source is set to Stream, this field shows the stream name to use as the timing source. Secondary RX Timing Stream: If the secondary 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 Stream Network Type: The network quality to be applied for clock recovery from the secondary stream (Dedicated, Metro, Continental). Timing Input 100 Ohm Impedance: Enabling/Disabling switch. Controls the external timing input impedance, 100 ohms at the TIMING IN port. The Timing In connector is a balanced RS-422/RS-485 input. This switch is normally set to Enabled. To change the TIMING IN to a high impedance input, select Disabled and click Submit to apply your changes. VCXO Timing Calibration Value: Timing calibration value (in ppm) for the voltage controlled crystal oscillator (factory calibration only). Submit: Click this button to apply all system timing information changes.

4.4.3.8

System TOS Byte Definitions

Access the System TOS Byte Definitions page (Figure 4-37) to view or modify the TOS byte values associated with High COS, Normal COS, Medium COS and Low COS, as well as TOS byte values for Web, SNMP, and Voice Signaling. To access the page, point to System Cfg and click TOS Byte Definitions.


4-35



Figure 4-37. System TOS Byte Definitions Page Note: Although the system can assign TOS to traffic leaving the NetXpress system, the effectiveness of tagging packets with TOS/COS depends solely on support from the routers within the IP network. TOS Setting for High COS: This field sets the IP TOS (Type of Service) byte for packets from a stream configured with a high COS (Class of Service). Default value is 188 (precedence 5, request low delay/high throughput/high reliability). Optional values are 220 (precedence 6) or 252 (precedence 7). TOS Setting for Normal COS: This field sets the IP TOS byte for packets from a stream configured with a normal COS. Default value is 92 (precedence 2, request low delay/high throughput/high reliability). Optional values are 124 (precedence 3) or 156 (precedence 4). TOS Setting for Medium COS: This field sets the IP TOS byte for packets from a stream configured with a medium COS. Default value is 60 (precedence 1, request low delay/high throughput/high reliability). TOS Setting for Low COS: This field sets the IP TOS (Type of Service) byte for packets from a stream configured with a low COS (Class of Service). Default value is 0 (precedence 0). Suggested optional value is 28 (precedence 0, request low delay/high throughput/high reliability). Web TOS Byte Setting: This field sets the IP TOS byte used by the HTTP packets coming out of the NetXpress system. Default value is 32 (precedence 1). SNMP TOS Setting: This field sets the IP TOS byte used by the SNMP packets coming out of the NetXpress system. Default value is 32 (precedence 1). Voice Signaling TOS Byte Setting: This field sets the IP TOS byte used by the signaling transmission packets. Default value is 32 (precedence 1). Submit: Click this button to apply and record the TOS Byte definition information entered.

4.4.3.9

Software Load Image Configuration

When the NetXpress system first starts up, the NIM(s) attempts to load its operating system from the Primary Image Filename along with its associated Primary FPGA Image 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 also fail, the NIM attempts to load the Backup Image Filename from the network FTP fileserver along with the Backup FPGA Image Filename. Access the Software Load Image Configuration page (Figure 4-38) to view and modify NIM specific software load information. To access the page, point to System Cfg and click Software Load Image. The latest NetXpress version’s release notes gives the software load image and boot ROM load image configurations.

4-36




Figure 4-38. Software Load Image Configuration Page Primary Image Filename: Name of the primary software image file. Secondary Image Filename: Name of the secondary software image file. Primary FPGA Image Filename: Name of the primary Field Programmable Gate Array (FPGA) file. Secondary FPGA Image Filename: Name of the secondary FPGA file. Current Image Loaded: Provides status on which software image was last loaded (primary, secondary, or backup). Page area is read-only. Image to Load on Next Boot: Specifies the image to use when the system is restarted. This allows the user to override the default and force the NIM to load either the primary or secondary. Backup Image Filename: Name of the backup software image file. Backup FPGA Image Filename: Name of the backup FPGA file. Backup Image Server IP: IP address of the backup image FTP server. Gateway to Backup Image Server: Default gateway to get to the backup image FTP server. Backup Image Server FTP Username: FTP username for backup image server. Backup Image Server FTP Password: FTP user password for backup image server. Reset Form: Click this button to reset the page to the previous values. Submit: Click this button to apply all configuration changes. GatesAir, Inc. Intraplex Products

4-37



Reset NIM: Click this button to physically reset the NIM after performing a software image load. If you have made any configuration changes on this page, click Submit and click Reset NIM for the NIM to be set according to the values now shown on this page. NetXpress Flash Device Directory: The current directory location of the NetXpress flash device. Use this field to type a new directory location and click Change Directory to submit the new entry. Change Directory: Click this button to view the contents of the directory on the NetXpress flash device given in the Directory on NetXpress Flash Device field. Use /RFA/ and /RFA2/ as valid root directories. The gray table is the directory listing showing the files stored on the NetXpress flash. This information is present on the page in order to assist you in locating the available file names of the primary and secondary image and FPGA image files To obtain the software and boot ROM download process in the latest version’s release notes: 1. Go to http://www.gatesar.com. 2. Click Services and Support | Customer Support Portal. 3. At Customer Login, enter your User ID and Password. 4. At Self Service, click Download Software Updates. 5. At the Table of Contents, click Intraplex. 6. At the Intraplex: Table of Contents, click NetXpress. 7. Click the link for the latest version of the NetXpress software. 8. Click Save on the dialog box and save the zipped file to your hard drive. 9. Open the zipped file and open the release notes. 10. Repeat the previous two steps to download the latest version of the MIBs and MIB overview as well.

4.4.3.10 Configuration Files Backup and Restore You can view and configure access to your network backup FTP server on the Configuration Files Backup/Restore page (Figure 4-39). An FTP server is required to preserve an archival copy of your NetXpress configuration files or to restore these files to the NetXpress system. To access the page, point to System Cfg and click Configuration Backup. Fields on this page need to match the parameters of your network FTP server program including the server IP address, backup server directory location, user name, and password. Many FTP server programs are available commercially, some of which are freeware (such as TYPSoft FTP Server, Cerberus FTP Server, Cesar FTP). The NetXpress Quick Start Guide in this manual gives additional details on backing up/restoring configuration files. Restored configuration files do not take effect until the NIM-1 is restarted.

4-38




Figure 4-39. Configuration Files Backup/Restore Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. Config Backup Server IP: Specifies IP address of the configuration backup server IP Address (the address where the FTP server resides). Config Backup Server Directory: Identifies the backup server directory created by the user and specified in the FTP server program. Username: Identifies configuration backup server user name (created in the FTP server program). Password: Identifies configuration backup server user password (created in the FTP server program). You must type a valid password to perform a configuration backup or restore. Reset: Click this button to change the page fields back to the original values. Submit: Click this button to apply the configuration information on this page. Reset the System: Click this button to perform a physical resetting of the NIM-1. 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 configuration files. The backup procedure copies files from the NIM 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 NIM. Delete: Click to delete the configuration file for the row selected. Click delete all configuration files.

in the table header to

4.4.3.11 Redundancy Configuration You can view and configure the primary and the secondary NIM on the Redundancy configuration page (Figures 4-40 and 4-41). Section 4.3 gives more details on configuration and operation of primary and secondary NIMs and NIM redundancy. Note: If you do not have two NIMs on your system, you cannot see this option on the System Cfg menu and cannot access this page.


4-39



To access the page, point to System Cfg and click Redundancy. Fields on this page allow you to take the primary and secondary NIMs out of service or put them in service, to set up manual or automatic reversion, and to configure system synchronization.

Figure 4-40. Redundancy Configuration Page There are two tabs on this page: Configuration and Synchronization. Configuration Tab You can take the NIMs out of service or put them in service on this tab. You can also set up manual or automatic reversion page. Refresh: Click this button to refresh the browser. NIM: Indicates Primary and Secondary NIM. Role: Indicates the present function of the Primary or Secondary NIM. If Active, the NIM is currently providing operational services. If Standby, the NIM is either synchronized or in the process of synchronizing with the Active NIM and can take over the role of Active NIM. Operational State: Indicates whether the NIM is presently Up, Down, or Ready. If Up, the NIM is presently in service and has the Active role in the NetXpress system. If Down, the NIM is not in service. If Ready, the NIM has a Standby role and is ready to transition to the Active role. Administrative State: Indicates whether the NIM is In Service or Out of Service. An Out of Service state prohibits the NIM from taking the Active role in a redundant NIM system. Put in service/Put out of service: Click specific NIM out of service.

to put the specific NIM in service. Click

to put the

Switch back to primary if secondary fails: Select this check box to enable automatic switchback, the Primary NIM takes over as Active, if the secondary NIM fails. Switch back to primary when it recovers after ___ (type amount) seconds: Select this check box to enable automatic switchback, the Primary NIM takes over as Active, after the Secondary NIM has been Active for the number of seconds shown. The default number of seconds is “30.” Automatic Reversion Timer (secs): Indicates how long the system waits for the automatic reversion to commence. Reset: Click this button to clear all recent redundancy configuration entries and/or changes and return to the previous values. Submit: Click this button to apply the configuration changes. 4-40




Figure 4-41. Redundancy System Synchronization Page Synchronization Tab You can configure system synchronization on this tab. Refresh: Click this button to refresh the browser. Auto Synchronization: Select this check box to automatically synchronize the active and standby NIMs. Synchronization Group: The group of files that are affected by NIM synchronization. Synchronization Group Status: Whether or not data within this group is currently synchronized on the active and standby NIMs. Configuration File: The specific configuration file being synchronized. Configuration File Status: Whether or not this file is currently synchronized on the active and standby NIMs. Check System Synchronization: Click this button to verify the synchronization status between the NIMs. Force System Synchronization: Click this button to begin a forced synchronization between NIMs.

4.4.4

Configure the Network

Network configuration (Networking) in the NetXpress system involves configuring these pages: Interface Configuration: The network addressing table Forwarding: The IP routing table IP Access List: The list of IP addresses allowed to access the device SNMP: The SNMP (Simple Network Management Protocol) Host Configuration UDP: The UDP (User Datagram Protocol) Listener table TCP: The TCP (Transmission Control Protocol) Connection table ARP: The ARP (Address Resolution Protocol) table


4-41


4.4.4.1


Network Interface Configuration

To access the Network Interface Configuration page, point to Networking and click Interface Configuration. Once the Network Interface Configuration page appears, click on an interface row to view and modify address information for that interface. Figure 4-42 shows configuration on the MGMT interface.

Figure 4-42. Network Interface Configuration Page Interface: The interfaces with access permission (MGMT, WAN, or LAN). Current IP Address: The network IP address currently used for this interface. Note: When using NIM redundancy, the IP address needed for the Standby NIM to do a network boot is set to one higher than the static IP address set for the Management interface. Therefore, you must reserve two addresses when setting the static address of the Management interface. For example, if the IP address of the Management interface is set at “192.245.66.172:255.255.255.0” the address “192.245.66.175:255.255.255.0” is reserved by the Standby NIM to do a network boot. Current Netmask: The subnet mask currently used for this interface. DHCP: Whether or not Dynamic Host Configuration Protocol (DHCP) is currently used for this interface. If DHCP is used in a redundant system, both NIMs have a different Management interface, and you need to maintain the relationship of IP address to the physical NIM. SNMP: Whether or not Simple Network Management Protocol (SNMP) is currently allowed for this interface. HTTP: Whether or not Hypertext Transfer Protocol (HTTP) is currently allowed for this interface. FTP: Whether or not File Transfer Protocol (FTP) is currently allowed for this interface. Telnet: Whether or not Telnet is allowed for this interface. Blocked Pkts: The number of packets blocked because they contain a protocol (SNMP, HTTP, Telnet, or FTP) that is blocked on the interface. Configure: Click 4-42

for the specific interface to view configuration details and/or configure the interface. GatesAir, Inc. Intraplex Products



Use DHCP: Whether or not DHCP should be used on this interface to determine its IP address and subnet mask. Note: DHCP is only allowed on the Management (MGMT) interface. Current IP Address: The network IP address currently used for this interface. Read-only. Current Netmask: The subnet mask address received by DHCP. Read-only. Static IP Address: If DHCP is not enabled, this field defines the IP address to use for this interface. Static Netmask: If DHCP is not enabled, this field defines the subnet mask to use for this interface. Allow SNMP: Whether SNMP traffic is accepted on this interface. Allow HTTP: Whether HTTP traffic is accepted on this interface. Allow FTP: Whether FTP sessions are accepted on this interface. Allow Telnet: Whether Telnet sessions are accepted on this interface. Submit: Click this button to apply configuration changes. Note: If you change the IP address on the Management (MGMT) interface, you need to reconfigure your PC and/or browser to meet the NetXpress system on the newly assigned address before continuing. Figure 4-43 shows configuration on the WAN interface.

Figure 4-43. WAN Network Interface Configuration Page Static IP Address: This field defines the IP address to use for this interface. Static Netmask: This field defines the subnet mask to use for this interface. Allow SNMP: Whether SNMP traffic is accepted on this interface. Allow HTTP: Whether HTTP traffic is accepted on this interface. Allow FTP: Whether FTP sessions are accepted on this interface. Allow Telnet: Whether Telnet sessions are accepted on this interface. Enable IGMP Auto-Recovery: Select this check box to enable the internal IGMP recovery logic. This feature helps prevent the router from missing the subscribed multicast group by monitoring conditions within the system and sending out an unsolicited report for the subscribed groups. (This feature assumes


4-43



that the router is configured for a one-minute IGMP general query interval, which is the default for most routers.) Enable IGMP Logging: Only select this check box at a request of GatesAir technical personnel, as this feature is for debugging known issues. Selecting this check box enables the network driver to capture the IGMP messages. Enable Auto-Negotiation: Controls auto-negotiation state for the port. Default is enabled. Enable ICMP Error Blocking: Controls enabling/disabling of ICMP error messages on WAN port. Use LAN as Redundant WAN Link: When selected, LAN port acts as redundant WAN port. When not selected, the port acts as a normal data port. Port Speed: Speed of the interface (10 or 100 Mbps). Read-only. Port Duplex State: Duplex mode (full or half). Read-only. Submit: Click this button to apply configuration changes. Figure 4-44 shows configuration on the LAN interface.

Figure 4-44. LAN Network Interface Configuration Page Static IP Address: This field defines the IP address to use for this interface. Static Netmask: This field defines the subnet mask to use for this interface. Allow SNMP: Whether SNMP traffic is accepted on this interface. Allow HTTP: Whether HTTP traffic is accepted on this interface. Allow FTP: Whether FTP sessions are accepted on this interface. Allow Telnet: Whether Telnet sessions are accepted on this interface. Enable Auto-Negotiation: Controls auto-negotiation state for the port. Default is enabled. Mirror the WAN interface: When selected, LAN port acts as redundant WAN port. When not selected, the port acts as a normal data port. Port Speed: Speed of the interface (10 or 100 Mbps). Read-only. Port Duplex State: Duplex mode (full or half). Read-only. Submit: Click this button to apply configuration changes.

4.4.4.2

IP Routing Table

Review, create, and edit IP route information for all traffic associated with your Intraplex NetXpress IP Multiplexer on the IP Routing Table (Figure 4-45). Point to Networking and click Forwarding. Default 4-44




routes are automatically created based on the IP addresses assigned to the MGMT, 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-45).

Figure 4-45. IP Routing Table 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. Destination: The destination IP address of the route. Default is 0.0.0.0. Netmask: The logic mask to be combined with the destination address before comparison. The netmask defines the scope of an IP address, and what addresses can exist on that same logical subnet. Gateway: The gateway routing IP address. Interface: The description of the interface using this route. Type: The type of routing (Direct, Indirect, or Invalid). Protocol: The learned routing mechanism for this route. Age: The length of time since the route was last updated. Metric: The primary routing metric for this route. Add Route: Click

to create a new IP route. The Create A New Route page appears (Figure 4-46).

Delete this route: Click

to delete the specific IP route.

Figure 4-46. Create a New Route Page Destination: Type the destination IP address of this particular route. Network Mask: Type the logic mask to be combined with the destination address before comparison. The network mask defines the scope of an IP address and what addresses can exist on that same logical subnet. Gateway: Type the IP address of the gateway device responsible for final routing of IP address for this route. Type: Click the type of routing from this list: Direct (default), Indirect, Other, or Invalid. Back: Click this button to return to the IP Routing Table without saving changes to the page or creating a route. Create: Click this button to apply the information entered and create a new route. GatesAir, Inc. Intraplex Products

4-45


4.4.4.3


IP Access List

The IP Access List table contains a list of IP addresses allowed to manage the system via the interface. If the list is empty, any address on any interface can access the system. To access the page (Figure 447), point to Networking and click IP Access List. You can review the list or click submit interface entries along with an associated IP address (Figure 4-48).

to create and

Figure 4-47. IP Access List Refresh: Click this button to refresh the browser. Interface: The interfaces with access permission (MGMT, WAN, or LAN). IP Address: The IP address of the specific interface. Add IP Access entry: Click to add a new IP Access List entry. The Create IP Access List Entry page appears (Figure 4-48). You first need to type the IP address of the computer that you are currently using to configure the system or the NetXpress system refuses further communication.

Figure 4-48. Create IP Access List Entry Page Interface: Click the interface to which the address applies: MGMT (default), WAN, or LAN. IP Address: Type the IP address to add it to this interface. Back: Click this button to return to the IP Access List without creating an entry. Submit: Click this button to create the IP Access List Entry. 4.4.4.4

SNMP Configuration

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

4-46




Figure 4-49. SNMP Configuration Page SNMP Read-Only community: The SNMP community name a SNMP manager must use to read an element of the NetXpress MIB. SNMP Read-Write community: The SNMP community name a SNMP manager must use to modify an element of the NetXpress MIB. SNMP Event Host 1 IP: The IP address of the event host 1. This address is the usually the computer running the primary network manager application. If the address is 0.0.0.0, this entry is not active. SNMP Event Host 1 Community: The community name given to the SNMP trap. This name identifies a collection of SNMP managers and agents. SNMP Event Host 2 IP: The IP address of the event host 2. If the address is 0.0.0.0, this entry is not active. SNMP Event Host 2 Community: The community name of the SNMP trap. This name identifies a collection of SNMP managers and agents. Submit: Click this button to apply the configuration information changes. Reset: Click this button to change the page fields back to the original values.

4.4.4.5

UDP Listener Table

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

Figure 4-50. UDP Listener Table GatesAir, Inc. Intraplex Products

4-47



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. Local IP Address: The local IP address for the UDP listener. Local Port Number: The port number assigned to the IP address. UDP Port for Voice Signaling: The user-selected UDP port number for signaling. Default number is 49155. Submit: Click this button to apply changes to the UDP Port for Voice Signaling.

4.4.4.6

TCP Connection Table

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

Figure 4-51. TCP Connection Table 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. Local IP: The local IP address for this TCP connection. Local Port: The local port number for this TCP connection. Remote IP: The remote IP address for this TCP connection. This identifies the computers that are actively connecting to the NetXpress system. Remote Port: The remote port number for this TCP connection. HTTP traffic typical operates on port 80. Connection State: The state of this TCP connection.

4.4.4.7

ARP Table

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

Figure 4-52. ARP Table

4-48




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. IP Address: The IP address of the NetXpress shelf. Physical Address: The MAC address provided by the ARP. Type: The type of addressing used. Source Interface: The interface used to learn the entry in the ARP table. Clear ARP Table: Click this button to delete all ARP Table entries.

4.4.5

Configure Streams You can use the next group of pages to add and configure packet streams in the NetXpress system. Streams must be configured at all end points in the network, and you must instruct the NetXpress system to link portions of data among the TDM busses, electrical ports, or IP destinations. The NetXpress system supports up to 32 full-duplex streams. Streams cannot share the same source or destination channels on one NetXpress system unless one of the streams is first placed out of service. Click Streams to access the Streams table (Figure 4-53). To activate (put in service), edit or delete streams, click the appropriate icon appearing at the end of the row for the specific stream. The icons in the header row allow you to add a stream, put all streams in service, or delete all streams. Click any stream table headers to sort the stream table in ascending order by that header. Click the header again to sort the stream table in descending order.

Figure 4-53. Streams Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. In-Service Stream Bandwidth (kbits/sec): The bandwidth (in kilobits per second) being used by streams now in service. In-Service FEC Streams: The number of IP packet streams in service at this time using forward error correction. No more than 10 full duplex streams using FEC are allowed to be in service at a time.


4-49



In-Service Telephony Streams: The number of telephony (voice signaling) streams now in service. Total Stream Bandwidth (kbits/sec): The total bandwidth (in kilobits per second) required for stream traffic if you were to activate all of the streams listed in the table. Total Number of FEC Streams: The total number of IP packet streams using forward error correction. Total Number of Telephony Streams: The total number of telephony (voice signaling) streams. ID: An assigned index that uniquely identifies each stream. Name: The description label that you may assign to the stream. If you point to the stream name with your cursor, additional stream details appear. Destination: The destination (IP address or electrical interface) for the stream. Direction: Whether the stream is set to Transmit, Receive, or Both. Multicast streams are always simplex (that is, either Transmit or Receive). Date Created: The time and date when this stream was created. Up Time: The length of time this stream has been continuously operational. Operational State: The actual operational state of the stream (Up, Down, In Progress). Admin State: Provisioned state of the stream session (In Service, Out of Service). This state is used to provide administrative control information regarding the last state that was requested of the stream. Table 4-1 shows the meaning of operational state/administrative state combinations. Table 4-1. States Associated with Streams Administrative State

Operational State

Out of Service

Down

Created stream not currently in service.

In Service

Down

For bidirectional and receive streams, you have put the stream in service, but the NetXpress system has not received any packets. Transmit only streams have this combination if the interface is down or a route does not exist to the destination.

Out of Service

Up

Not possible.

In Service

Up

You have put the stream in service, and the NetXpress system has received packets.

In Service

In Progress

Definition

The process of activating the stream is proceeding.

Put stream in service/out of service: Click (activate it). Click

for a specific stream to put the stream in service

on the header row to put all streams in service. Click the ID of individual streams in

order to select multiple streams and then click many streams at once. Click

or

on the header row to change the admin state of

for a specific stream to put the stream out service (deactivate it). Click

on the header row to put all streams out service. Add/Edit/Delete: Click to add a stream, header row to delete all streams. Clock: The

to edit a stream, or

to delete a stream. Click

in the

next to the stream name indicates that it has been selected as a timing stream.

Phone: The next to the stream name indicates that voice signaling is enabled for the stream. The color code of this icon matches that of the Operational State (green=no alarm or alert; yellow=alert; and red=alarm).

4.4.5.1

Stream Creation

To add a packet stream, click (Figure 4-54). 4-50

on the Streams table. The Stream Creation – Stage 1 page appears




Figure 4-54. Stream Creation – Stage 1 Page (TDM to IP) If you click TDM to TDM on the Stream Creation – Stage 1 page, the page changes to this view (Figure 4-55):

Figure 4-55. Stream Creation – Stage 1 Page (TDM to TDM) Stream Name: Type a unique name describing the stream. Stream Type: Click TDM to TDM if the endpoints of the stream are one of the system’s TDM busses or TDM electrical interfaces rather than the IP network. TDM to IP is the default stream type. Stream Direction – TDM to IP: Click Transmit or Both to change the stream direction to transmitting or bidirectional. Receive is the default direction. TDM to TDM: Click Both to change the stream direction to bidirectional. One Way (receive or transmit) is the default direction. Cancel: Click this button to return to the Streams Table page without creating a new stream. Next: After completing the Stream Creation – Stage 1 page, click this button to proceed to the Stage 2 stream creation page (Figure 4-56). Note: See Figures 4-56 through 4-59 for TDM to IP Stream Creation page details. Figures 4-60 and 4-61 show TDM to TDM Stream Creation page details.


4-51



TDM to IP Stream Creation

Figure 4-56. Stream Creation – Stage 2 (TDM to IP) Page Stream Name: The unique name entered in Stage 1 that describes the stream. Transmission Type: Click Multicast to change the packet transmission (Unicast is default). Forward Error Correction: Click either Low or High to specify the type of forward error correction to be applied to this stream. None, the default, indicates that forward error correction is not to be applied. Stats Meas. Interval (secs): The update interval (5 to 10 seconds) on the stream statistics (5 seconds is default). Enable Voice Signaling: Select this check box to enable telephony signaling transmission for the stream. You need to enable signaling in order to transport telephone call progress signals and E&M state changes on voice frequency (VF) TDM channel modules, as well as external T1/E1 ports. For TDM over IP streams, signaling is transmitted out-of-band in a separate data stream that gets created when the voice stream is put in-service. For NetXpress systems operating in E1 mode, you also have to turn on CAS signaling for the internal TDM on which the voice channel module resides. Otherwise, the signaling bits are not sent over the network. Enable Echo Cancellation: Select this check box to enable echo cancellation for this stream. Echo cancellation is only required for bi-directional two-wire voice streams where the destination is across an IP network. If there are no echo cancellation boards installed on the NIM-1, this check box does not appear. 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-57).

4-52




Figure 4-57. Stream Creation – Stage 3 (TDM to IP) Page Stream Name: The unique name entered in Stage 1 that describes the stream. Destination IP Address: Type the IP address for the WAN interface of the NetXpress 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 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 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 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 the destination NetXpress system. 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-58).


4-53



Figure 4-58. Stream Creation – Stage 4 (TDM to IP) Page Stream Name: The unique name entered in Stage 1 that describes the stream. Frameloss Mask: Click a number on this mask to indicate in which channel module slot(s) frame loss (FRML) signals are to be asserted when the stream encounters loss of ingress packets. Each slot in a GatesAir Intraplex T1/E1 multiplexer shares a signal known as FRML. This signal is used by the channel modules to mute audio when the T1/E1 interface goes out of frame. This functionality has also been incorporated in the NetXpress system so that the channel modules can mute audio when a stream goes down. While one FRML signal is bussed to all slots in a Intraplex T1/E1 multiplexer, a separate FRML signal is routed to each slot in the NetXpress chassis. That way, the loss of a stream will not force FRML to be asserted on all channel modules. TDM Bus: Select the TDM bus (Bus 1A, Bus 2A, Bus 1B, Bus 2B, E1 Port A, E1 Port B, T1 Port A, or T1 Port B) for the source of the stream data. Packet Size (bytes): This is the number of bytes in a stream packet, automatically computed by adding TDM Bus Frames per Packet and overhead (62). TDM Bus Starting Channel: Type the number of the starting time slot (channel) on the TDM bus or external T1/E1 port for this stream. TDM Bus Channel Range: Type the number of time slots (channels) on the TDM bus or the external T1/E1 port to include in the stream. TDM Bus Frames per Packet: Type a number to define the “packetization” interval for the stream. For a stream used as a timing source, the number of frames per payload should not exceed 8. For a non-timing stream, the maximum frames per payload can go up to 1000 depending on the number of timing TDM channels encapsulated per frame. The maximum payload size cannot exceed 1400 bytes. Section 2 gives more information on packetization. Jitter Buffer Size (packets): Select the number of packets in the jitter buffer (that is, 8, 16, 32, 64, or 128). Streams using FEC are restricted to jitter buffer sizes of 32, 64, or 128. The default is 32 packets. Increasing the size of the jitter buffer increases the system’s ability to compensate for network jitter, but it also increases the latency of the packet stream.

4-54




Stream Bandwidth (kbits/sec): This is the amount of bandwidth in kilobits per second required by the stream, automatically computed based on number of TDM Bus Frames per Packet. Stream Delay (milliseconds): This is the initial jitter/lead position in the Jitter Buffer, automatically computed based on Jitter Buffer Size. Stream Program Type: Defines the contents of the underrun buffer based on the type of program stream. The underrun buffer gets played out to the internal TDM bus or external T1/E1 port 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. 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. 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. 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-59). If the TDM bus associated with this stream is not connected to an IP port in the TDM bus map, a warning splash page appears.

Figure 4-59. Stream Creation Summary (TDM to IP) Page GatesAir, Inc. Intraplex Products

4-55



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

Figure 4-60. Stream Creation – Stage 2 (TDM to TDM) Page Stream Name: The unique name entered in Stage 1 that describes the stream. Stream Direction: Whether the stream is One Way (receive or transmit) or Both. Source TDM Bus: Click the TDM bus or external T1/E1 interface on the list that is the source for the stream: TDM Bus 1A, TDM Bus 2A, TDM Bus 1B, TDM Bus 2B, E1 Port A, E1 Port B, T1 Port A, or T1 Port B. For bidirectional streams, it does not matter which of the two busses is selected to be the source. Destination TDM Bus: Click the TDM bus or external T1/E1 interface on the list that is the destination for the stream: TDM Bus 1A, TDM Bus 2A, TDM Bus 1B, TDM Bus 2B, E1 Port A, E1 Port B, T1 Port A, or T1 Port B. For bidirectional streams, it does not matter which of the two busses is selected to be the source. Source TDM Channel Start: Type the number of the starting time slot (channel) on the source TDM bus or external T1/E1 port for this stream. Destination TDM Channel Start: Type the number of the starting time slot (channel) on the destination TDM bus or external T1/E1 port for this stream.

4-56




Source TDM Channel Range: Type the number of time slots (channels) on the source TDM bus or the external T1/E1 port to include in the stream. Destination TDM Channel Range: Type the number of time slots (channels) on the destination TDM bus or the external T1/E1 port to include in the stream. Enable Voice Signaling: Select this check box to enable telephony for the stream. Voice Card Used: Appears when the Enable Voice Signaling check box is selected. From the dropdown list, select the voice card to be used for signaling in this stream or select Enter signaling insertion byte to type a value in the Signaling Insertion Byte field. Signaling Insertion Byte: Appears when the Enable Voice Signaling check box is selected. This field is automatically populated when you select Voice Card Used. If you select Enter signaling insertion byte from the Voice Card Used drop-down list, you can type a value in this field. Stream Program Type: Accept the default Compressed Audio/Data or click Linear Audio/Voice on the list. To enter the number of packet underrun bytes, click Enter underrun value manually. Packet Underrun Byte: Set automatically when Compressed Audio/Data or Linear Audio/Voice is selected as the Stream Program Type. Otherwise, type the number of bytes for the packet underrun. Frameloss Mask: Click a number on this mask to indicate which channel module slot(s) FRML signals are to be asserted when the stream encounters loss of ingress packets. 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 Summary page (Figure 4-61). If the source and destination busses are not connected in the TDM bus map, a warning splash page appears, asking if you want to continue.

Figure 4-61. Stream Creation Summary (TDM to TDM) Page This page shows information from the previous Stream Creation pages. Cancel: Click this button to return to the Streams Table without creating a new stream. Prev: Click this button to return to the Stream Creation – Stage 2 page. Create: After assuring all entries are correct, click this button to actually create the stream. Create & Activate: After assuring all entries are correct, click this button to create and activate the stream on the shelf. This button is enabled only if the source and destination busses are connected to each other in the TDM bus map. GatesAir, Inc. Intraplex Products

4-57


4.4.5.2


Stream Edit/Deletion

To edit, delete, or put an existing stream in service, you must click an icon on the Streams table (Figure 4-62).

Figure 4-62. Streams Page To edit an existing stream, click

at the end of the stream’s row on the stream table to access the edit

page (Figures 4-63 and 4-64). To delete an existing stream, click

at the end of the row. To put a

stream in service, click . To take a stream out of service, click . You can also use the icons in the stream table header row to put all streams in service, take all streams out of service, or delete all streams.

4-58




Figure 4-63. TDM to IP Stream Edit Page

Figure 4-64. TDM to TDM Stream Edit Page GatesAir, Inc. Intraplex Products

4-59



When the editing page appears for the stream selected, you can edit the stream information in the same manner as with the stream creation stages (Figures 4-54 and 4-56 through 4-59 to create a TDM to IP stream and Figures 4-55, 4-60, and 4-61 to create a TDM to TDM stream). Note: When you first access a stream edit page, the Put In Service button appears on the page. If you change any data on the page, this button changes to Submit & Activate.

4.4.5.3

Stream Group

Click the ID cell on the stream row to add that stream to the stream group. Once a stream is added to the group, the , , and in the header of the stream table operate on all streams in the group instead of all streams in the table. Any stream in the stream group has an ID in blue. You can remove a stream from the group by clicking its stream ID cell again; the ID color returns to gray. To add or remove all streams from the stream group, hold down the SHIFT key and click the stream ID header.

4.4.6

Check Multiplexer Performance

Use the Performance function in the NetXpress system to monitor IP multiplexer performance: Streams: Streams Statistics table. Voice Signaling: Voice Signaling Statistics table. E1 Interfaces: E1 Port Statistics table. T1 Interfaces: T1 Port Statistics table. SNMP: SNMP Statistics table. UDP: UDP Statistics table. TCP: TCP Statistics table. ICMP: ICMP Statistics table. IGMP: IGMP Statistics table. IP: IP Statistics table. 4.4.6.1

Stream Statistics

Click Streams on the Performance menu to access the Streams Statistics table (Figure 4-65). This page shows statistics from the current interval for each stream in the table. Click the ID number of a stream to view performance history (statistics for Stream 1 in Figure 4-66). Point to a table header and a tooltip appears that gives a definition of the statistic.

Figure 4-65. Stream Statistics Page

4-60




Figure 4-66. Performance History Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. ID/Index: On the current statistics interval page, the ID is the identification number assigned by the system that uniquely identifies each stream (ID). The system keeps individual stream statistics for 10 index intervals. Click the ID button to view all the statistics from all the statistics intervals for the stream selected. Op State: Whether the stream is currently operational (in service). Packet Count – Rx: The accumulated number of packets received for the stream. Packet Count – Tx: The accumulated number of packets transmitted for the stream. Rx Packet Statistics – Recovered: The number of packets recovered using Forward Error Correction. Rx Packet Statistics – Lost: The accumulated number of packets that were lost in the packet network. Total underrun packets minus the sum of early and late packets. Rx Packet Statistics – 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. Rx Packet Statistics – Early: The accumulated number of packets that were discarded by the system because they arrived too soon to play out. Rx Packet Statistics – 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. Rx Queue – Min: The minimum number of packets that were present in the jitter buffer in the interval. Rx Queue – Max: The maximum number of packets that were present in the jitter buffer in the interval. Rx Queue – Avg: The average number of packets present in the jitter buffer in the interval. Meas – PDV: The Measured Packet Delay Variation, the average of maximum and minimum packets present in the jitter buffer. Clear Stats/History: Click

on the header row of the Streams Statistics table to clear all statistics

on the table. Click on the stream row to clear all statistics for that stream. Click the Clear History button on the Performance History table to clear the stream statistics performance history for that stream. Close: Click this button to close the Performance History page.

4.4.6.2

Voice Signaling Statistics

Click Voice Signaling on the Performance menu to access the Voice Signaling Statistics table (Figure 4-67). This table shows state change, packet loss, and out of order information for voice signaling streams.


4-61



Figure 4-67. Voice Signaling Statistics Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. Index: Number assigned that uniquely identifies the stream in the stream table. Stream Name: Unique name assigned to the stream by the user. Tx Signaling State Changes: The number of transmit call state changes per signaling stream. Rx Signaling State Changes: The number of receive call state changes per signaling stream. Packets Lost: The number of lost packets per signaling stream. Packets Out of Order: The number of packets received out of order per signaling stream.

4.4.6.3

E1 and T1 Port Statistics

Click E1 Interfaces on the Performance menu to access the E1 Port Statistics table (Figure 4-68) and T1 Interfaces on the Performance menu to access the T1 Port Statistics table (Figure 4-69). These pages show both current and cumulative interval statistics for the near and far ends of the E1 and T1 Port A and Port B. Click a Current Interval port button to view statistic intervals for that port. Figures 4-70 and 4-71 show statistic intervals for an E1 Port A Far End and a T1 Port A Far End. The Near End pages do not show the LCV statistic intervals.

Figure 4-68. E1 Port Statistics Page

4-62




Figure 4-69. T1 Port Statistics Page

Figure 4-70. Port Statistics Intervals Page – E1 Near End Port

Figure 4-71. Port Statistics Intervals Page – T1 Near End Port 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.


4-63



Near End: The statistics for the closer end of the E1 port. Far End: The statistics for the farther end of the E1 port. Current Interval Statistics: The statistics of the interval currently. Cumulative Interval Statistics: An average of interval statistics. ES: Errored Seconds; the number of seconds in which at least one code violation (CV) was detected on the circuit. SES: Severely Errored Seconds. An SES is a second in which a severe number of errors are detected over the circuit. SEFS: Severely Errored Framed Seconds; a count of the number of seconds during which, at any point, the Severely Errored Framing (SEF) defect was present. UAS: Unavailable Seconds; a count of one-second intervals during which service is unavailable. CSS: Controlled Slip Seconds; a count of one-second intervals of one or more controlled slips. A controlled slip is the occurrence of a replication or deletion of a T1 frame by the receiving terminal. PCV: Path Coding Violations; the number of code violations per second within the path. LES: Line Errored Seconds; a count of one-second intervals in which one or more LCV error events were detected. BES: Bursty Errored Seconds; a count of one-second intervals greater than one and less than 320 CRC error events. LCV: Line Code Violations; the number of code violations per second within the line. Interval: The specific interval to which these statistics correspond.

4.4.6.4

SNMP Statistics

Select SNMP (Simple Network Management Protocol) from the Performance menu to view SNMP message information on the SNMP Statistics page for the IP multiplexer (Figure 4-72). These are total statistics since the system last rebooted. All of the statistics are totals since the system last rebooted.

4-64




Figure 4-72. SNMP Statistics Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. Total Messages Rcvd: The number of messages delivered to the NetXpress SNMP Agent from the transport service. Total Messages Sent: The number of SNMP Messages passed from the NetXpress SNMP Agent to the transport service. Get Requests Rcvd: The number of SNMP Get-Request PDUs (protocol data units) accepted and processed by the NetXpress SNMP Agent. Get Requests Sent: The number of SNMP GET requests sent by the NetXpress SNMP Agent to the another SNMP protocol entity in the network. Get Responses Rcvd: The total number of SNMP Get-Response PDUs received by the NetXpress SNMP Agent from another SNMP protocol entity in the network. Get Responses Sent: The total number of SNMP Get-Response PDUs generated by the NetXpress SNMP Agent. Get Next Requests Rcvd: The total number of SNMP Get-Next PDUs accepted and processed by the NetXpress SNMP Agent.


4-65



Get Next Requests Sent: The total number of SNMP Get-Next PDUs generated by the NetXpress SNMP Agent. Set Requests Rcvd: The total number of SNMP Set-Request PDUs accepted and processed by the NetXpress SNMP Agent. Set Requests Sent: The total number of SNMP Set-Request PDUs sent by the NetXpress SNMP Agent to another SNMP protocol entity in the network. Total Variables Requested: The total number of requested variables - number of variable bindings processed by the NetXpress SNMP agent Total Variables Set: The number of objects altered successfully by the NetXpress SNMP Agent as the result of receiving valid SNMP Set-Request PDUs. Traps Rcvd: The total number of unsolicited messages (traps) received by the NetXpress SNMP

Agent from another SNMP protocol entity in the network. Traps Sent: The total number of SNMP Trap PDUs generated by the NetXpress SNMP Agent. Too Big Rcvd: The total number of SNMP PDUs received by the NetXpress SNMP Agent for which the value of the error-status field was “tooBig”. Too Big Sent: The total number of SNMP PDUs generated by the NetXpress SNMP Agent for which the value of the error-status field was “tooBig”. No Such Name Rcvd: The total number of SNMP PDUs received by the NetXpress SNMP Agent for which the value of the error-status field was “noSuchName”. No Such Name Sent: The total number of SNMP PDUs generated by the NetXpress SNMP Agent for which the value of the error-status was “noSuchName”. Bad Value Rcvd: The number of SNMP PDUs received by the NetXpress SNMP Agent for which the value of the error-status field is “badValue”. Bad Value Sent: The total number of SNMP PDUs generated by the NetXpress SNMP Agent for which the value of the error-status field was “badValue”. Generic Error Rcvd: The total number of SNMP PDUs received by the NetXpress SNMP Agent for which the value of the error-status field was “genErr”. Generic Error Sent: The total number of SNMP PDUs generated by the NetXpress SNMP Agent for which the value of the error-status field was “genErr”. Bad Versions Rcvd: The total number of SNMP messages received by the NetXpress SNMP Agent for an unsupported SNMP version. Bad Community Names Rcvd: The total number of SNMP messages received by the NetXpress SNMP Agent using an SNMP community name not known to the entity. Bad Community Uses Rcvd: The total number of SNMP Messages received by the NetXpress SNMP Agent representing an SNMP operation not allowed by the SNMP community named in the message. ASN Parse Errors: The total number of ASN.1 or BER errors encountered by the NetXpress SNMP Agent when decoding received SNMP messages. Readonlys Rcvd: The number of valid SNMP PDUs delivered to the SNMP protocol entity for which the value of the error-status field is “readOnly”, indicating incorrect implementation of SNMP.

4.4.6.5

UDP Statistics

This page (Figure 4-73) reveals User Datagram Protocol (UDP) statistical information. A datagram is an independent, self-contained message sent over the network. To access the UDP Statistics page, point to Performance and click UDP.

4-66




Figure 4-73. UDP Statistics Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. Total Datagrams Received: The total number of UDP datagrams received by the NetXpress system from the network. Total Datagrams Sent: The total number of UDP datagrams sent from the NetXpress system to the network. Total Datagrams Rcvd With No Listener: The total number UDP datagrams received by NetXpress for which there was no application in the NetXpress system listening to the destination port Total Datagrams Rcvd In Error: The number of UDP datagrams received by the NetXpress system that could not be delivered for reasons other than the lack of an application at the destination port.

4.4.6.6

TCP Statistics

This read-only page (Figure 4-74) reveals TCP (Transfer Control Protocol) statistical information specific to your NetXpress operation. 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. To access the TCP Statistics page, point to Performance and click TCP.

Figure 4-74. TCP Statistics Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. Total Segments Rcvd: The total number of segments received by the NetXpress system, including those received in error.


4-67



Total Segments Sent: The total number of segments sent by the NetXpress system, including those on current connections. Total Error Segments Rcvd: The number of TCP messages received by the NetXpress system but were determined to have ICMP-specific errors (bad TCP checksums, and so forth). Total Segments Sent with RST Flag: The number of TCP segments sent by the NetXpress system containing the RST (reset) flag. Maximum Number of Connections: The maximum number of open connections TCP supported on the NetXpress system simultaneously. This number is only limited by available memory. Total Segments Retransmitted: The number of TCP segments transmitted by the NetXpress system containing one or more previously transmitted octets. Minimum Retransmission Timeout: The minimum number of times that TCP retransmits a packet before a retransmission is started. Maximum Retransmission Timeout: This is the maximum number of times that TCP retransmits a packet before a retransmission is started. Current Established Connections: The number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT. Failed Connection Attempts: 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. Transitions from CLOSED to SYN-SENT: The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state. Transitions from LISTEN to SYN-RCVD: The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state. Number Connection Resets: Specifies the number of established connections reset.

4.4.6.7

ICMP Statistics

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

4-68




Figure 4-75. ICMP Statistics Page Total Messages Rcvd: Total number of Internet Control Messages received by the NetXpress system. Total Messages Sent: Total number of Internet Control Messages transmitted by the NetXpress system. Destination Unreachable Messages Rcvd: The number of ICMP Destination Unreachable messages received by the NetXpress system. Destination Unreachable Messages Sent: The number of ICMP Destination Unreachable messages sent by the NetXpress system. Redirect Messages Rcvd: The number of redirect messages received by the NetXpress system. A redirect message is sent to the originating computer when a better route is discovered for a datagram sent by that computer. Redirect Messages Sent: The number of redirect messages sent by the NetXpress system. Source Quench Messages Rcvd: The number of requests received by the NetXpress system to cut back the rate at which it is sending traffic to the internet destination. Source Quench Messages Sent: The number of requests sent to the NetXpress system to cut back the rate at which it is sending traffic to the internet destination.


4-69



Echo Request Messages Rcvd: The number of ICMP Echo (request) messages received by the NetXpress system. Echo Reply Messages Sent: The number of echo replies sent by the NetXpress system. A computer sends an echo reply in response to receiving an echo request message. Echo Request Messages Sent: The number of echo requests sent by the NetXpress system. An echo request causes the receiving computer to send an echo reply message back to the originating computer. Echo Reply Messages Rcvd: The number of echo replies received by the NetXpress system. A computer sends an echo reply in response to receiving an echo request message. Time Exceeded Messages Rcvd: The number of time-to-live (TTL) exceeded messages received by the NetXpress system. A time-to-live exceeded message is sent to the originating computer when a datagram is discarded because the number of routers it has passed through exceeds its time-to-live value. Time Exceeded Messages Sent: The number of time-to-live (TTL) exceeded messages sent by the NetXpress system. Parameter Problem Messages Rcvd: The number of parameter-problem messages received by the NetXpress system. A parameter-problem message is sent to the originating computer when a router or host detects an error in a datagram's IP header. Parameter Problem Messages Sent: The number of parameter-problem messages sent by the NetXpress system. Inbound Messages with Errors: The number of messages received by the NetXpress system with errors. Outbound Messages with Errors: The number of messages sent by the NetXpress system with errors. Timestamp Request Messages Rcvd: The number of time-stamp requests received by the NetXpress system. A time-stamp request causes the receiving computer to send a time-stamp reply back to the originating computer. Timestamp Reply Messages Sent: The number of time-stamp replies sent by the NetXpress system. A computer sends a time-stamp reply in response to receiving a time-stamp request. Routers can use timestamp requests and replies to measure the transmission speed of datagrams on a network. Timestamp Request Messages Sent: The number of time-stamp requests sent by the NetXpress system. Timestamp Reply Messages Rcvd: The number of time-stamp replies received by the NetXpress system. Address Mask Request Messages Rcvd: The number of address mask requests received by the NetXpress system. A computer sends an address mask request to determine the number of bits in the subnet mask for its local subnet. Address Mask Reply Messages Sent: The number of address mask responses sent by the NetXpress system. A computer sends an address mask response in response to an address mask request. Address Mask Request Messages Sent: The number of address mask requests sent by the NetXpress system. Address Mask Reply Messages Rcvd: The number of address mask responses received by the NetXpress system.

4.4.6.8

IGMP Statistics

This read-only page (Figure 4-76) shows Internet Group Management Protocol (IGMP) statistics relative to your NetXpress operation. IGMP is defined as the standard for IP multicasting. All hosts conforming to level 2 of the IP multicasting specification require IGMP. To access the IGMP Statistics page, point to Performance and click IGMP.

4-70




Figure 4-76. IGMP Statistics Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. Total Queries Received: Total number of incoming queries received by the NetXpress system. Outgoing Membership Report Sent: Total number of membership reports sent by the NetXpress system. Outgoing Membership Leave Sent: Total number of membership leave messages sent by the NetXpress system. Group Address: IP multicast group address for which this entry contains information. Membership Reports Sent: Number of membership reports sent for the group. Total Queries Received: Number of times the router has sent queries for this group. Uptime: Time elapsed since this entry was created.

4.4.6.9

IP Statistics

This read-only page (Figure 4-77) shows IP statistical information related to your NetXpress 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 the IP Statistics page, point to Performance and click IP.


4-71



Figure 4-77. IP Statistics Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. IP Forwarding: Whether IP forwarding is enabled or disabled. IP Default TTL: The default Time to Live (TTL) value put in each IP packet sent by the NetXpress system. This defines the number of router hops that can be made before this packet is dropped. Total Datagrams Rcvd: The total number of input datagrams received by the NetXpress IP protocol stack, including those received in error. Total Datagrams Sent: The total number of UDP datagrams sent from the NetXpress system. Delivered Datagrams: Total number of IP datagrams received by the NetXpress system. Forwarded Datagrams: The number of datagrams forwarded by the NetXpress system to another destination in the network. Input Datagrams Discarded: The number of input IP datagrams received by NetXpress IP protocol stack with no errors but were discarded for other reasons (for example, for lack of buffer space). Output Datagrams Discarded: The number of output IP datagrams received by the NetXpress IP protocol stack with no errors but were discarded for other reasons (for example, for lack of buffer space). Rx Header Errors: The number of packets containing header errors. Rx Address Errors: The number of packets received by the NetXpress system containing addressing errors.

4-72




Unknown Protocols Rcvd: The number of packets received by the NetXpress system containing unknown protocols. Unroutable Datagrams: The number of datagrams received by the NetXpress IP protocol stack that could not be routed. IP Fragments Rcvd: The number of received packets fragmented successfully. IP Fragments Sent: The number of frames requiring fragmentation before sending. Reassembled Datagrams: The number of fragmented datagrams that have been reassembled by the NetXpress IP protocol stack. Fragmented Datagrams: The number of fragmented datagrams received by the NetXpress IP protocol stack. Failed Reassemblies: The number of attempted datagram reassemblies by the NetXpress system. Failed Fragmentations: The number of datagram fragmentations that failed. Reassembly Timeout: A value in seconds. A host may receive a Reassembly Timeout message from a destination host that has timed out and discarded an incomplete datagram. Routing Discards: Number of valid and invalid routing entries discarded by the NetXpress system.

4.4.7

Set up Accounts Use the Accounts configuration function in the NetXpress system to establish and control user access and FTP privileges through password entry. To begin NetXpress accounts configuration, click Accounts. The first Accounts page appears (Figure 4-78), allowing you to create and change account passwords. To change the password for the GUI account or to edit an FTP account, click

on the corresponding row. To restore the GUI password

or delete an FTP account, click

on the corresponding row.

Figure 4-78. Accounts Configuration Pages Username: If the username exists, the system shows it in the account entry page (GUI or FTP). If it does not exist, type a username for account access. Current Password: If you are changing an account password, type your current password in this field. New Password: If you are changing a password or typing a password for the first time, type it in this field. Confirm New Password: Retype the password in this field. Back: Click this button to exit this page without saving any entries. Submit: Click this button to apply the new entries on this page.


4-73


4.4.8


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

Figure 4-79. Ping Utility Page Host IP Address: Type the target (Host IP address) to be pinged. Don’t Route Past Local Network: Select this check box to limit the ping request to the local subnet only. Number of Packets: Type a number of echo requests (packet ping requests) to be sent or click the arrows to increase or decrease the number shown. Default is 1. PING Result: The result of the ping request (Got Response or No Response). Send Ping: Click this button to execute the ping request.

4.4.9

View Power Supply Information

To configure the primary or backup power supply module in the NetXpress system, click the Open button at the bottom of the power supply module column on the NetXpress Home page. Figure 4-80 shows a standard power supply, and Figure 4-81 shows a 200W-AC power supply.

Figure 4-80. Standard Power Supply Page Refresh: Click this button to refresh the browser. Power Supply Status: Current status of the power supply module (Running or Failed). 4-74




Power Supply Temperature Sensor 1: The temperature of the first power supply sensor. Power Supply Temperature Sensor 2: The temperature of the second power supply sensor. Power Supply 3.3 Volts PS: 3.3 Volts power supply measured voltage. Power Supply 5 Volts PS: 5 Volts power supply measured voltage. Power Supply 3.3 Volts Midplane: 3.3 Volts power supply measured midplane measured voltage. Power Supply 5 Volts Midplane: 5 Volts power supply measured midplane measured voltage. Power Supply +/- 15 Volts Bus: +/-15 volts bus measured voltage. High Temperature Alarm Threshold (°C): Type the Maximum Power Supply Temperature Threshold in degrees Celsius (default value 90). When the temperature of the power supply exceeds the value entered (90 for example), the NetXpress system generates an SNMP trap and shows an alarm message on the Current Alarms and Alarm History pages. Submit: Click this button to apply changes to your Hi Temperature Alarm Threshold. All other page fields are read-only.

Figure 4-81. 200W-AC Power Supply Configuration Page Refresh: Click this button to refresh the browser. Power Supply Status: Current status of the power supply module (Running or Failed). 3.3 Volts Measurement: 3.3 Volts power supply measured voltage. 5 Volts Measurement: 5 Volts power supply measured voltage. +15 Volts Measurement: +15 Volts bus measured voltage. -15 Volts Measurement: -15 Volts bus measured voltage.


4-75



Fan 1 Speed (RPM): Revolutions Per Minute of the first (top) fan. Fan 2 Speed (RPM): RPM of the second (middle) fan. Fan 3 Speed (RPM): RPM of the third (bottom) fan. Revision: Identifies which version of power supply code this module is using. High Temperature Alarm Threshold (°C): Type the Maximum Power Supply Temperature Threshold in degrees Celsius (default value 90). When the temperature of the power supply exceeds the value entered (90 for example), the NetXpress system generates an SNMP trap and shows an alarm message on the Current Alarms and Alarm History pages. Peak Supply Temperature (°C): The highest temperature of the three power supply sensors (Temperature Sensor 1, Temperature Sensor 2, and Temperature Sensor 3). Submit: Click this button to apply your Hi Temperature Alarm Threshold. All other page fields are readonly. Show Extended Parameters: Select this check box to view these additional fields: 3.3 Volts Measurement (System): 3.3 Volts power supply measured voltage. 5 Volts Measurement (System): 5 Volts power supply measured voltage. +15 Volts Measurement (System): +15 Volts bus measured voltage. -15 Volts Measurement (System): -15 Volts bus measured voltage. Temperature Sensor 1 (°C): The temperature at the first power supply sensor. Temperature Sensor 2 (°C): The temperature at the second power supply sensor. Temperature Sensor 3 (°C): The temperature at the third power supply sensor.

4.4.10

Configure Primary/Secondary Network Interface Module (NIM)

You can have a secondary (redundant) NIM in case the primary NIM fails or to help reduce service interruption when installing software upgrades. Section 4.3 gives details on configuring and operating primary and secondary NIMs (that is, NIM redundancy). Both the primary and the secondary NIMs have four configuration pages: ●

General

●

Revisions

●

Program Boot ROM

●

MIU 202

If the NIM you are viewing is auto-programmed, you only see the General page. There are no tabs for revisions, the boot ROM, or the module interface unit (MIU).

4.4.10.1 NIM-1 General Configuration The General configuration page (Figure 4-82) allows you to view information for the NIM (for example, IP and MAC addresses, serial number, and insertion date) and modify the board description.

4-76




Figure 4-82. NIM-1 Network Interface Module: General Page Active/Standby status bar: This bar indicates whether the NIM is Active (that is, currently providing operational services) or Standby (that is, currently synchronized with or in the process of synchronizing with the Active NIM and can take over the role of the Active NIM). If the NIM is Active, the bar appears green. If the NIM is Standby, the bar appears gray. Board Description: The unique name you give this NIM. Type a name and click Submit to set that name for the NIM. Slot Number: The slot position this NIM currently occupies. Read-only. IP Address 1: The address for this NIM. Read-only. MAC Address 1: The MAC address for this NIM. Read-only. IP Address 2: An alternate address for this NIM. Read-only. MAC Address 2: An alternate address for this NIM. Read-only. IP Address 3: An alternate address for this NIM. Read-only. MAC Address 3: An alternate address for this NIM. Read-only. Serial Number: The serial number assigned to this NIM when it was manufactured. Read-only. Manufacturing Date: The date the NIM was manufactured in the factory. Read-only. Module Up Time: How long the module has been in service. Read-only. GatesAir, Inc. Intraplex Products

4-77



Insertion Date: Date and time of the last system restart. Read-only. Echo Cancellers Installed: Number of echo cancellers currently installed. Read-only. Last Software Upgrade Date: The date the system software was last updated. Read-only. Loopback State: Whether or not there is a loopback set for the system. 5 Volts Power Consumption (watts): 5 Volts power supply measured voltage. 3.3 Volts Power Consumption (watts): 3.3 Volts power supply measured voltage. 15 Volts Power Consumption (watts): 15 Volts power consumption measured voltage. -15 Volts Power Consumption (watts): Negative 15 Volts power consumption measured voltage. Reset: Click this button to change the page fields back to the original values. Submit: Apply all changes you made to this page. Put In/Out of Service: Click this button to put the NIM in service or take the NIM out of service. If the NIM is operating, this button appears as “Put Out of Service.” Likewise, if the NIM is not operating, this button appears as “Put In Service.” Reset Module: Reset the NIM.

4.4.10.2 NIM-1 Revisions Configuration The Revisions configuration page (Figure 4-83) allows you to view version information for the NIM (for example, application, FPGA, hardware board revision, and so forth) and modify the board description.

Figure 4-83. NIM-1 Network Interface Module: Revisions Page Application Version: Version number of the NIM application software currently running on the NIM. Read-only. Application Creation Date: Date and time the NIM application software was built. Read-only. FPGA Version: Version number of the NIM FPGA (Field Programmable Gate Array) image file. Read-only. CPLD Version: Version number of the NIM CPLD (Complex Programmable Logic Device). Read-only. Boot Loader Version: Revision number for the bootloader software used to load the application software from the Flash device. Read-only. Hardware Board Revision: Revision number for this NIM module board. Read-only. Hardware Assembly Number: Factory assembly number for this NIM module board. Read-only.

4-78




4.4.10.3 NIM-1 Program Boot ROM Configuration The Program Boot ROM configuration page (Figure 4-84) allows you to view and modify the Boot ROM Load Image configuration information used to program the system boot code of the NIM-1.

Figure 4-84. NIM-1 Network Interface Module: Program Boot ROM Page Refresh: Click M to refresh the browser manually, or click 5s, 10s, or 30s to automatically refresh the browser at 5, 10, or 30 second intervals. Boot ROM Image Filename: The name of the Boot ROM file presently programmed on this NIM. Readonly. Programming Status: The current status of the program command (Idle, In Progress, or Completed). Read-only. Program: Click this button to initiate the boot code programming command. NetXpress Flash Device Directory: The current directory location of the NetXpress flash device. Use this field to type a new directory location and click Change Directory to submit the new entry. Change Directory: Click this button to view the contents of the directory on the NetXpress flash device given in the Directory on NetXpress Flash Device field. Use /RFA/ and /RFA2/ as valid root directories. The gray table is the directory listing showing the files stored on the NetXpress flash. This information is present on the page in order to assist you in locating the available boot ROM file name. To obtain the software and boot ROM download process in the latest version’s release notes:


4-79



1. Go to http://www.gatesair.com. 2. Click Services and Support | Customer Support Portal. 3. At Customer Login, enter your User ID and Password. 4. At Self Service, click Download Software Updates. 5. At the Table of Contents, click Intraplex. 6. At the Intraplex: Table of Contents, click NetXpress. 7. Click the link for the latest version of the NetXpress software. 8. Click Save on the dialog box and save the zipped file to your hard drive. 9. Open the zipped file and open the release notes. 10. Repeat the previous two steps to download the latest version of the MIBs and MIB overview as well.

4.4.10.4 MIU-202 Configuration The MIU 202 configuration page (Figure 4-85) allows you to view MIU-202 information for the NIM (for example, serial number, time module has been in service, manufacturing date, power consumption, and so forth) and modify the board description.

Figure 4-85. NIM-1 Network Interface Module: MIU-201 Page Board Description: The unique user-defined name for this NIM. You can type a name and click Submit to set that name for the NIM. Slot Number: The slot position this NIM currently occupies. Read-only. Serial Number: The serial number assigned to this NIM when it was manufactured. Read-only. Manufacturing Date: The date the NIM was manufactured in the factory. Read-only.

4-80




Hardware Version: Version number for this MIU 202. Read-only. Module Up Time: The number of days, hours, minutes, and seconds that this board has been in service. Read-only. Insertion Date: The date this module was most recently inserted in the multiplexer slot. Read-only. FPGA Version: Version number of the NIM FPGA (Field Programmable Gate Array) image file. Read-only. Hardware Assembly Number: Factory assembly number for this MIU 202. Read-only. 5 Volts Power Consumption (watts): 5 Volts power supply measured voltage. 3.3 Volts Power Consumption (watts): 3.3 Volts power supply measured voltage. 15 Volts Power Consumption (watts): 15 Volts power consumption measured voltage. -15 Volts Power Consumption (watts): Negative 15 Volts power consumption measured voltage. Reset: Click this button to change page fields back to the original values. Submit: Apply all changes you made to this page.

4.4.11

Configure Individual Modules (TDM Modules and CAMs)

From the NetXpress Home page, you can access configuration and status pages for individual TDM modules and channel access modules. Click the Open button for the desired module on the Home page.

Figure 4-86. DA-91A Configuration Page

The examples to the right (Figures 4-86 and 4-87) show the configuration and status pages for a DA-91A Data Polling Module. Once you access the configuration page (above), click the Status tab to access the module’s status page (right). The P Codes section of each module’s operation manual gives additional details on configuration parameters for specific audio, voice, and data modules. (Section 3.4.1 – P Codes of the PT/PR-150C Module Installation and Operation Manual gives details relative to configuration parameters.) These pages contain configuration and status sample pages for Intraplex program audio (PT/PR-353 – Figures 4-88 and 4-89), voice (VF-25E – Figures 4-90 and 4-91), and data (DS-64NC – Figures 4-92 and 4-93) modules. Below each sample page is a detailed explanation of each page field.

Figure 4-87. DA-91A Status Page


4-81


4.4.11.1


Sample Program Audio Module Configuration and Status

Figure 4-88. PT-353 Configuration Page Alias Name: Type a name to help identify the module type. Shelf Address: The IP address for the multiplexer shelf housing the module. This field is read-only. Card Address: SCB address assigned to the module. Each module must have a unique address. Valid addresses are 1 through 36. This field is read-only. TDM Bus: The TDM bus identifier on which the channel module resides. This field is read-only. Module Adapter: The type of module adapter installed in the rear of the shelf. Remote Control: The desired operation for the module (REMOTE or LOCAL). This field is read-only. Enable Module: Select this check box to place the module in service. If left blank, the module remains offline. Module Configured: Whether the module is properly configured. This field is read-only. TDM Bus Configuration ●

Timeslot: Click an up or down arrow to specify the desired starting time slot (1 to 24 in T1 system, 1 to 31 in E1 system).

●

TDM Bus: Click either Bus A or Bus B on the list to indicate the current bus side.

●

Skip Timeslot 16: Select this check box to set the module for use in an E1 (2MB) multiplexer set for CAS signaling.

Audio Configuration ●

Bandwidth: Click the audio sample rate bandwidth from the list (32 ksps, 44.1 ksps, 48 ksps).

●

Mode: Click the mode (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.

4-82




●

Remove DC Offset: Select this check box to enable DC offset removal in DSP (digital signal processor). Offset refers to the removal of any DC component in the waveform.

●

Use Sample Rate Converter: Select this check box to enable use of the Asynchronous Sample Rate Converter (ASRC). The digital audio sample rate can be locked to a local reference at the receive site using an ASRC.

Input Sensitivity (dBu F/S): Shows the module’s current input sensitivity. This field is read-only. Refresh: Click this button to refresh the browser. Submit: Click this button to apply the configuration values entered on this page. Reset: Click this button to change page fields back to the original values. 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.

Figure 4-89. PT-353 Status Page The Status page fields are read-only; you cannot change any values on this page. Alias Name: The user-specified name for the module to help identify module type. Shelf Address: IP address for the multiplexer shelf housing the module. Card Address: SCB address assigned to the module. Each module must have a unique address. Valid addresses are 1 through 36. TDM Bus: The TDM bus on which the channel module resides. Module Adapter: Type of module adapter installed in the rear of the shelf. Remote Control: Desired operation for the module (REMOTE or LOCAL).


4-83



Enable Module: Whether the module is in service or 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. Config Error: Whether there is a configuration error (red) or normal condition (green). A configuration error occurs when the time slot for the module is conflicting with another module in the system or when the number of occupied time slots exceeds system availability. Refresh: Click M to refresh the browser manually or click an option to set the browser to refresh automatically at 5 second, 10 second, or 30 second intervals. TDM Bus Configuration ●

Timeslot: The 64 kbps time slots that make up a T1 or E1 circuit. The number of time slots varies for each type of module. The time slot that you specify is for the starting time slot only. If the module occupies more than one slot, you must make certain there are sufficient time slots available.

●

TDM Bus: The current bus side, either Bus A or Bus B.

Version ●

DSP: The version number of the Digital Signal Processor (DSP) firmware that is currently installed.

●

Firmware: The version number of the Field Programmable Gate Array (FPGA) design that is currently installed.

Transmitter Settings ●

Sample Rate: The current sample rate (in ksps) for the module.

●

Audio Mode: The current audio setting (Mono or Stereo).

●

Test Tone On: When selected, the test tone is enabled for the module.

●

Use J.17 Emphasis: When selected, Analog Emphasis is used. To reduce the effects of noise on the signal, higher frequency signals are amplified to produce a more equitable modulation index for the transmitted signal. The emphasis must be removed from the received signal before processing.

●

Remove DC Offset: When selected, Offset is enabled. Offset enable provides DC offset removal in the DSP (digital signal processor).

●

Use Sample Rate Converter: When selected, Sample Rate Conversion is enabled for the audio sample.

Audio Source: ●

Digital input is in use: This light is green if the input is in use and gray if it is not in use.

●

Analog input is in use: This light is green if the input is in use and gray if it is not in use.

Transmit Status ●

Audio Activity: When this light is green, either there is no audio activity or audio activity detected in the left channel if the signal is -28 dBFS.

●

Audio Error: When this light is red, either there is no audio errors detected or an AES/EBU error detected on the incoming signal.

Digital Transmit Level ●

Left and Right: The transmission signal strength on left and right channels. The signal should not consistently exceed the Red indicator that signifies an overload condition of +20dBm or more.

●

Input Sensitivity: The module’s current input sensitivity setting.

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.

4-84



4.4.11.2


Sample Voice Module Configuration and Status

Figure 4-90. VF-25E Configuration Page Alias Name: Type a name to help identify the module type. Shelf Address: The IP address for the multiplexer shelf housing the module. This field is read-only. Card Address: SCB address assigned to the module. Each module must have a unique address. Valid addresses are 1 through 36. This field is read-only. TDM Bus: The TDM bus identifier on which the channel module resides. This field is read-only. Module Adapter: The type of module adapter installed in the rear of the shelf. Remote Control: The desired operation for the module (REMOTE or LOCAL). This field is read-only. Enable Module: Select this check box to place the module in service. If left blank, the module remains offline. Module Configured: Whether the module is properly configured. This field is read-only. TDM Bus Configuration ●

Timeslot: Click an up or down arrow to specify the desired starting time slot (1 to 24 in T1 system, 1 to 31 in E1 system).

●


Active Channels: Select the audio channels (1, 2, 3, 4) to enable 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: For REV A1 and later, select this check box to set the C bit to 1. (If the check box is cleared, the C bit is set to 0.)

Loopbacks ●

Local: For testing purposes, loopback sends the input channel audio and signaling to its own local output channel.

●

Channels 1-4: 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


4-85



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. Refresh: Click this button to refresh the browser. Submit: Click this button to apply the configuration values entered on this page. Reset: Click this button to change page fields back to the original values. 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.

Figure 4-91. VF-25E Status Page The Status page fields are read-only; you cannot change any values on this page. Alias Name: The name you specify to help identify the module type. Shelf Address: The IP address for the multiplexer shelf housing the module. Card Address: The SCB address assigned to the module. Each module must have a unique address. Valid addresses are 1 through 36. TDM Bus: The TDM bus on which the channel module resides. Module Adapter: The type of module adapter installed in the rear of the shelf. Remote Control: The desired operation for the module (REMOTE or LOCAL). Enable Module: Whether the module is in service or 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: Click M to refresh the browser manually or click an option to set the browser to refresh automatically at 5 second, 10 second, or 30 second intervals.

4-86




TDM Bus Configuration ●


●

Timeslot: The current setting for the starting time slot on the module.

Other Configuration ●

Local Loopback: If this check box is selected, the module is in local loopback mode.

●

Use Signaling: If this check box is selected, E-lead and M-lead circuit signaling is enabled. (The audio channel is still operational even if signaling is disabled.)

●

Set C Bit to 1: For REV A1 and later, the C bit is set to 1 if this check box is selected. (If the check box is cleared, the C bit is set to 0.)

Channels 1-4 ●

Active: The channel activity (Green = channel is active or off-hook, gray = channel is idle or onhook).

●

M-Lead Busy: The M Lead activity (Green = M lead is active or unknown, gray = M lead is inactive or not enabled.

●

E-Lead Busy: The E Lead activity (Green = E signaling lead is active or unknown, gray = E signaling lead is inactive or not enabled).

●

Loopback: The channel is in local loop back mode (green) or there is no active loopback (gray).


4.4.11.3

Sample Data Module Configuration and Status

Figure 4-92. DS-64NC Configuration Page GatesAir, Inc. Intraplex Products

4-87



Alias Name: Type a name to help identify the module type. Shelf Address: The IP address for the multiplexer shelf housing the module. This field is read-only. Card Address: SCB address assigned to the module. Each module must have a unique address. Valid addresses are 1 through 36. This field is read-only. TDM Bus: The TDM bus identifier on which the channel module resides. This field is read-only. Module Adapter: The type of module adapter installed in the rear of the shelf. Remote Control: The desired operation for the module (REMOTE or LOCAL). This field is read-only. Enable Module: Select this check box to place the module in service. If left blank, the module remains offline. Module Configured: Whether the module is properly configured. This field is read-only. TDM Bus Configuration ●

Timeslot: Click an up or down arrow to specify the desired starting time slot (1 to 24 in a T1 system, 1 to 31 in an E1 system).

●


●

T1 (24 time slots): This option is set when using a T1-based system. This field is read-only.

●

E1 (31 time slots): This option is set when using an E1-based system. This field is read-only.

●

Skip Timeslot 16: Select this check box to set the module for use in an E1 (2MB) multiplexer set for CAS signaling.

●

Use Alternating Timeslots: Select this check box to use alternating time slots (1, 3, 5, 7, 9, and so forth). If this check box is cleared, sequential time slots (1, 2, 3, 4, 5, and so forth) are used.

Test Mode Configuration ●

Test Mode: Click a mode from the list: No test, Generate all ones, Generate PRNG (15-bit pseudo random number generator), Generate 1:15 ones, Verify all ones, Verify PRNG, Verify 1:15 ones.

●

Loopback Mode: Click a loopback mode from the list: No Loopback, Local (payload) Loopback, Equipment Loopback, or Remote Loopback.

●

Performance Register Selection: Click a performance register from the list: Receive FIFO Depth, Receive FIFO Underrun Count, Receive FIFO Overrun Count, Transmit FIFO Depth, Transmit FIFO Underrun Count, Transmit FIFO Overrun Count.

●

Reset Performance Register: Select this check box to reset the register.

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. Click the starting depth of these buffers from the list: 256 Bits for normal synchronous operation or 6000 Bits for half of the full depth (plesiochronous operation).

●

Transmit Mode: Click the mode for transmit side of DS-64NC from the list: Transmit Side Off, Transmit Only with CS, Transmit On (RS/CS), Transmit On (CS).

●

External Timing: Select this check box to set the external timing output on or off. The normal condition for the external timing output is off.

●

Turn Receiver On: Select this check box to enable receive features for the module.

Data Rate Configuration ●

Timeslot Bit Rate: Click 64 kbps for the module to use 8 bits per time slot mode. Click 56 kbps for the module to use 7 bits per time slot mode.

●

Data Rate: Click the total data rate from the list, any rate from 8 kbps up to the maximum payload capacity of the multiplexer, in increments of 8 kbps.

●

Timeslots: The number of timeslots this module is using.

Refresh: Click this button to refresh the browser.

4-88




Submit: Click this button to apply the configuration values entered on this page. Reset: Click this button to change page fields back to the original values. 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.

Figure 4-93. DS-64NC Status Page The Status page fields are read-only; you cannot change any values on this page. Alias Name: The name you specify to help identify the module type. Shelf Address: The IP address for the multiplexer shelf housing the module. Card Address: The SCB address assigned to the module. Each module must have a unique address. Valid addresses are 1 through 36. TDM Bus: The TDM bus on which the channel module resides. Module Adapter: The type of module adapter installed in the rear of the shelf. Remote Control: The desired operation for the module (REMOTE or LOCAL). Enable Module: Whether the module is in service or 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. GatesAir, Inc. Intraplex Products

4-89



Config Error: Configuration error or normal condition. A configuration error occurs when the time slot for the module is conflicting with another module in the system or when the number of occupied time slots exceeds system availability. Refresh: Click M to refresh the browser manually or click an option to set the browser to refresh automatically at 5 second, 10 second, or 30 second intervals. TDM Bus Configuration ●


●

Timeslot: The desired starting time slot (1 to 24 in T1 system, 1 to 31 in E1 system).

●

Skip Timeslot 16: This check box is selected if the module is being used in an E1 (2MB) multiplexer set for CAS signaling.

●

Use Alternating Timeslots: This check box is selected if alternating time slots (1, 3, 5, 7, 9, and so forth) are being used. If this check box is cleared, sequential time slots (1, 2, 3, 4, 5, and so forth) are being used.

Test Mode Configuration ●

Test Mode: The test mode in use: No test, Generate all ones, Generate PRNG (15-bit pseudo random number generator), Generate 1:15 ones, Verify all ones, Verify PRNG, Verify 1:15 ones.

●

Loopback Mode: The loopback mode in use: No Loopback, Local (payload) Loopback, Equipment Loopback, or Remote Loopback.

●

Performance Register: The selected performance register for inspection.

●

Performance Register Value: The value of the performance register.

Circuit Configuration ●

Data Rate: The total data rate that may be set to any rate from 8 kbps up to the maximum payload capacity of the multiplexer, in increments of 8 kbps.

●

Timeslots: The number of time slots the module is using.

●

Transmit Mode: The mode for transmit side of DS-64NC Transmit Side Off, Transmit Only with CS, Transmit On (RS/CS), Transmit On (CS).

●

Bit Rate: Shows 64 kbps if the module uses 8 bits per time slot mode or 56 kbps if the module uses 7 bits per time slot mode.

●

Buffers: The amount of bits for the starting buffer depth: 256 Bits for normal synchronous operation or 6000 Bits for half of the full depth (plesiochronous operation).

●

Turn On Receiver: This check box is selected if receive features for the module are enabled.

●

External Timing: This check box is selected if the external timing output is on.

Card Status ●

Transmit Activity: Green if there is data activity on the input to the module (otherwise gray).

●

Receive Activity: Green if there is activity on the channel for this module (otherwise gray).

●

Remote Loopback: Green if the loopback from the far end has been initiated or is inactive (otherwise gray).

PLL Status ●

Transmit side PLL locked: Green if a Transmit Phase-Locked Loop error is detected (otherwise gray).

●

Receive side PLL locked: Green if a Receive Phase-Locked Loop error is detected (otherwise gray).

●

Shelf reference PLL locked: Green if a Shelf Reference Phased Lock Loop error is detected (otherwise gray).

4-90




Circuit Errors ●

Transmit clock output error detected: Red if a Transmit Clock Output error is detected (otherwise gray).

●

Receive clock output error detected: Red if a Receive Clock Output error is detected (otherwise gray).

●

Receive data output error detected: Red if an Output error is detected (otherwise gray).

●

Handshake signal error detected: Red if a Handshaking error is detected (otherwise gray).



4-91

No header here


4-92


No header here

Section 5 – Troubleshooting Frequently Asked Questions This list of questions and answers can help troubleshoot NetXpress system operations. Q: How do I begin? What is the proper start-up procedure for my NetXpress system? A: You can find step-by-step system setup instructions in the NetXpress Quick Start Guide at the beginning of this manual. Q: I want to add a channel module to my shelf. What is the proper procedure for adding a module? A: Prior to insertion, no special configuration is required. However, you might want to switch the module to REMOTE control so that you can change its settings from the NetXpress Web interface. Also, when adding channel modules, insert the module adapter first and then insert the channel module. All Intraplex channel modules are hot-insertable, so the module can be installed while the shelf is operating. 1. Insert the module adapter for the module in the slot behind the one you have selected for the new channel module. 2. Insert the module. Once the module is inserted, the NetXpress system detects the module automatically. 3. On the NetXpress home page, click Open on the displayed module to review and adjust the settings specific to the module (Section 4.4.10 – Configure Individual Modules (TDM Modules and CAMs) gives additional information). Q: Is it possible to stack more than one NetXpress chassis in a rack system? A: Yes, you can stack shelves; however, make sure the shelf rack is in a well ventilated area and allow at least 1RU spacing above and below the shelves when stacking. Q: I plan on using eight Intraplex channel modules in my main NetXpress shelf. Will the standard power supply module be adequate for my system? A: Your exact power requirements depend on the specific applications and modules you intend to use. The standard power supply module for the NetXpress system is an 80-watt unit. In some instances, this unit can accommodate as many as twelve channel modules. However, some applications and modules require additional power and might be better served by the optional 200-watt power supply. It is best to consult a GatesAir professional to determine your specific power requirements. Q: What is the procedure for installing a redundant power supply? A: After the primary power supply has been installed, perform these steps: 1. Install the Redundant power supply into the slot labeled PS Redundant. 2. If the system is AC-powered, connect the AC power cable to the back of the chassis directly behind the Redundant power supply. 3. If the system is DC-powered, connect the +BAT A terminal, then the chassis ground connection, then the –BAT A terminal for the Redundant power supply. 4. Verify that all four indicator lights are on. Note: The Major indicator light remains red until the NIM is fully operational and, when other channel cards are installed, the Minor indicator light may also remain yellow.


5-1


5—Troubleshooting FAQs

Q: How do I add an IP address to the Access List Table in the NetXpress system? A: To add an IP address, perform these steps: 1. Point to Networking and click IP Access List. 2. On the IP Access List, click

.

3. On the Create IP Access List Entry screen, click the Interface on the list that is associated with the physical port (MGMT, WAN, or LAN). 4. Type the IP Address of the host to allow access. 5. Click Submit. Section 4.4.4.3 – IP Access List gives additional information. Q: The SCB addresses for my channel modules do not match the slot numbers. Should the numbers match? A: It is recommended but not required that you set the SCB address on a channel module to match the number of the slot where the channel module is to reside. To change the SCB address on any channel module, locate the 6 switches labeled SCB ADDR on the module and change the switch settings according to the Table 5-1 chart. (* 0 = off, 1 = on) Table 5-1. SCB Switch Settings Card Address

Switch Settings:* S1, Positions 123456

1

000001

2

000010

3

000011

4

000100

5

000101

6

000110

7

000111

8

001000

9

001001

10

001010

11

001011

12

001100

Q: How do I install an update? A: You can update the NIM-1 (Network Interface Module) software in the NetXpress software by opening an FTP session with the NIM-1 and transferring a new image file to one or both of the flash memory devices. You can configure both the primary and secondary images to be loaded from the same flash memory device; there is no requirement for them to be on different devices. (If your system has NIM redundancy and is auto-synced, you only need to upgrade one NIM. If it is not auto-synced, you need to upgrade both NIMs.) Detailed installation procedures are included in the update files. Q: How do I reset the NIM-1 to factory default values if I want to default all values? A: Perform these steps: 5-2




1. Using Dip Switch SW1, move switches 1 and 2 to the ON position. 2. Apply power to the system.

ON OFF

3. Wait 60 seconds. 4. Disconnect power. 5. Return the switches to normal. 6. Restore power to the NIM again. The settings for the interfaces (MGMT, WAN, LAN) default to the original factory values. Q: When I use the NetXpress software, some screen fields appear to be unchanged. How can I be sure the screen information is current? A: Try clicking the Refresh button in your browser. If none of the fields on the screen change, clear the cache in Internet Explorer (on the Tools menu, click Internet Options and click the Clear History button.) Then, press the NetXpress screen Refresh button. You can also change the page settings for refresh times in Internet Explorer: 1. Go to Tools | Internet Options. 2. At Browsing history, click Settings. 3. At Check for newer versions of stored pages, click the Every time I visit the webpage option. Note: If you are not using Internet Explorer as your browser, your browser’s Help should give instructions on changing the browser page settings. Q: What do I do if creating a route fails? A: There is a good chance that the interface does not have an IP address and mask in the network to find the gateway. Check the destination IP address and the mask for the route you are creating. Confirm that the addresses are valid for the network and that it is reachable on the interface listed on the route. Section 4.4.4.2 – IP Routing Table gives additional information. Q: Why am I not getting any traps on my trap receiver (SNMP Event Host) A: Make sure the correct IP address and community name for the trap receiver is configured in the NetXpress software. Section 4.4.4.4 – SNMP Configuration gives additional information. Q: What should I do if I receive an error message when attempting to create and activate a stream? A: 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.

Q: I successfully created a stream. Why does it never come up? A: Try these guidelines to investigate the problem: 1. Verify that you have placed the stream in-service. 2. Access the Interfaces Table (System Cfg | IP Interfaces) to see if the WAN interface is down. 3. Make sure that there is a valid route to the destination.


5-3



4. Check the destination NetXpress multiplexer to make sure that it is configured properly and that its stream has an operational state of “In Service.” 5. Access the PING Utility screen (Utilities | Ping) and ping the destination to make sure it is reachable by the WAN interface. Q: My stream is up, but I do not hear any audio. What should I do? A: Try these guidelines: • • •

Open the configuration screen for the channel card, and make sure that channel card 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 card configuration and service state. Look at the TDM Bus Information screen (System Cfg | TDM Bus Config) on the NetXpress software where the transmitter is located. The time slots assigned to the transmitter should be green if it is placing audio data on the bus.

Q: My stream is up. I hear audio, but it does not sound very good. What should I do? A: Try these guidelines to investigate the problem: • • • • •

Verify the channel card configurations on both ends. Make sure that timing is properly configured. Look at the stream statistics to see how much packet loss is happening. 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. Your network may have more jitter than can be compensated for by the current size of the jitter buffer.

If these FAQs do not meet your needs, or you have additional questions, you can call Customer Service or send non-emergency e-mail for more in-depth support:

www.gatesair.com/services/technical-support.aspx Americas: 24/7 Technical Support Email

+1 217 222 8200 [email protected]

Europe, Middle East and Africa: 24/7 Technical Support +1 217 222 8200 Email [email protected] Asia: 24/7 Technical Support Email

5-4

+1 217 222 8200 [email protected]


No header here

Section 6 – Specifications 6.1 Detailed Specifications Ethernet Data Rate

10/100 BASE-T (10 or 100 Mbps) Full duplex Auto-negotiation with network

Ethernet Connector

Port 1 – Management LAN- Female RJ-45 Port 2 – WAN- Female RJ-45 Port 3 – LAN- Female RJ-45

T1/E1 Data Rate

T1: 1.544Mbps E1: 2.048Mbps

T1/E1 Connector

2 – Female RJ-45

T1 Specifications Physical Interface RJ-48C: 8-pin Modular Compatibility ATT 54016, ATT 62411, and ANSI T1.403 Line Rate 1.544 Mbps +/- 30 PPM, using internal timing Line Code AMI or B8ZS Line Build Out 0, -7.5, -15, or -22 dB Line Input Impedance 100 Ohms Framing D4 (SF) or ESF Robust Framing Mean time to lose frame at 10-3 BER: Greater than 450 hours for ESF Greater than 225 hours for SF Performance Monitoring ANSI T1.231, ANSI T1.403 PRM, and ATT 54016 Compliance FCC Part 68 Industry Canada CS-03 E1 Specifications Physical Interface RJ-48C: 8-pin Modular Compatibility ITU G.703, G.704, G.706, G.732, G.736, and G.823 Line Rate 2.048 Mbps +/- 30 PPM, using internal timing Line Code AMI or HDB3 Line Input Impedance 120 Ohms Framing CAS (Channel Associated Signaling) or CCS (Common Channel Signaling) Robust Framing Mean time to lose frame at 10-3 BER greater than 20 hours Performance Monitoring G.826 Compliance ETSI TBR12 and TBR13


6-1


6.1

6—Specifications

Detailed Specifications (continued)

Payload Bandwidth

4 TDM Buses for up to 8Mbps Up to 32Mbps from next generation Channel Access Modules

Circuit Connection

Point-to-point unidirectional Point-to-point bidirectional Point-to-multipoint unidirectional using IP Multicast or multiple IP Unicast streams

Network Protocols

IPv4, TCP, UDP, RTP, DHCP, DNS, HTTP (on port 80), FTP (on port 21), Telnet, SNTP, SNMP v2c (SNMP v1/SNMP v2 – requests on port 161 and traps on port 162), ARP, ICMP, IGMPv2

Streaming

Encapsulation in compliance with RFC5086 (CESoPSN)

Timing

Internal External, RS-422/RS-485 clock input Adaptive to incoming program stream for synchronous clock distribution across IP networks SynchroCast3™ precision buffer depth controlled timing Timing out, RS-422 clock output

Quality of Service

Forward Error Correction (FEC) in accordance with RFC2733 framework High, Low, Off, User-selectable Packet Optimization Programmable jitter buffer depth can provide compensation in excess of 1 second of network jitter (based on specific number of T1/E1 equivalent frames/packet.)

IP Priority

Supporting routers give priority to critical traffic: IPv4 Type of Service tagging Differentiated Service (DiffServ) tagging

Indicator Lights

Normal, Major Alarm, Minor Alert, Alarm Cutoff (ACO), LAN Link Status, LAN 100 MB, LAN Activity, T1/E1 Status External Timing, Internal Timing, Adaptive Timing, Network Status

External Alarm and Alert

NO/NC relay contacts

Diagnostic Network Statistics

Packet Loss, packets received, packets sent, packets recovered using FEC, late arriving packets, early arriving packets, received packet queue depth, measured packet delay

Loopbacks

Payload, line, and equipment loopback on the external T1/E1 ports, internal and external loopback on the system TDM busses.

User Interface

Remote control, monitoring, and diagnostics via Web browser interface

Remote Management

Web Browser Compatible with IE, Netscape, Mozilla, Firefox, Opera SNMP based Network Management Compatible with HP OpenView, Castle Rock, and similar software

Power Requirements

Universal AC 100-240 Vac, 50/60 Hz DC input: 48 Vdc, 8 A 24 Vdc, 4 A

Power Supply

Single or redundant, 80 W AC, 200W AC, 150 W DC options

Power Supply Alarm Contact rating

50 Vdc, 100mA

Base Power Requirements*

40 W or less typical

6-2


6—Specifications

6.1


Detailed Specifications (continued)

Environmental

Temperature: 0 C – 50 C operating (AC/DC powered) Humidity: 10% - 90% non-condensing

Physical

3RU – 5.25" (13.4cm) H x 14.25" (36.2cm) D x 19" (48.3cm) W Weight: 11 lb. (5 kg) approximate, w/o channel modules installed; Max weight dependent on number and type of modules installed.

Regulatory Compliance

CE Compliant, FCC Part 15 Class A, UL 1950

NIM Redundancy with External T1/E1 Port Redundancy

MIU-202-1 and MIU-202-2

* This includes power for the NIM, MIU, and power supplies. Each module has its own specific power requirements as defined in Table 2-1.

6.2 Notice of FCC Compliance 6.2.1

Compliance with FCC Part 15 Requirements

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

6.2.2

Compliance with FCC Part 68 Requirements

This equipment complies with Part 68 of the FCC rules. On the left of the chassis is a label that contains, among other information, the FCC registration number for this equipment. If requested, this information must be provided to the telephone company. If this equipment causes harm to the telephone network, the telephone company will notify you in advance that temporary discontinuance of service may be required. If advance notice is not practical, the telephone company will notify the customer as soon as possible. Also, you will be advised of your right to file a complaint with the FCC if you believe it is necessary. The telephone company may make changes in its facilities, equipment, operation, or procedures that could affect the operation of this equipment. If this happens, the telephone company will provide advance notice in order for you to make the necessary modifications to maintain uninterrupted service. If you experience difficulty with the NetXpress system, please contact GatesAir at 217-222-8200 for repair and warranty information. If your equipment is causing harm to the telephone network, the telephone company may request that you disconnect the equipment until the problem is resolved. The chassis contains no user-serviceable parts. The facility interface and service order codes are Interface Type

Facility Interface Codes (FIC)

Service Order Code (SOC)

Jack Type (USOC)

T1 Data

04DU9.BN 04DU9.DN 04DU9.1KN 04DU9.1SN

6.0Y

RJ-48C


6-3

No header here


6-4


No header here

Section 7 – Glossary Reference

Description

ABCD Signaling

Relative to the NetXpress system, refers to ABCD voice channel signaling in T1/E1 circuits and existing Intraplex voice channel modules. ABCD is also known as E & M (ear & mouth) signaling.

AC

Electrical current that reverses direction, usually many times per second

ACO

Alarm Cut Off device; the green light on front of a shelf indicates the alarm cut-off is active. It is reset by the NIM-1 when the alarm condition has been cleared (ACO is triggered by the switch located on the NIM-1 front panel).

Active NIM

Role of a NIM that is currently providing operational services, which can be either the Primary or Secondary NIM.

AES/EBU

Audio Engineering Society and European Broadcast Union digital format standard for audio modules.

Alarm Status

NetXpress shelf alarm status conditions: Major - Red light, indicates alarm condition exists (for example, stream loss, signal failure, loss of frame, power failure if redundant supply is installed) Minor - Yellow light, indicates that alert condition exists (for example, packet loss, network delay) Normal - Green light, indicates power is on and the NetXpress shelf is operating normally

ANSI TR54016 FDL

American National Standards Institution formatted Facilities Data Link reporting criterion, a form of statistical measurement.

ARD

Automatic RingDown; a private line that connects a station instrument in one location to one in another location with automatic two-way signaling.

ARP

Address Resolution Protocol; primarily used to translate IP addresses into Ethernet MAC addresses, ARP is the method of finding a host’s hardware address when only the network layer address is known. ARP is also used for IP over other LAN technologies.

ASN.1

Abstract Syntax Notation.1; an international data classification standard used in the NetXpress management information database.

ASCII

American Standard Code for Information Interchange; a built-in binary code for representing characters in most computers.

ATT T1.403 FDL

AT&T formatted Facilities Data Link reporting criterion, a form of statistical measurement.

BES

Bursty Errored Seconds; a count of one-second intervals in which more than one but less than 320 CRC error events, used as an interval statistic.

Boot ROM

The memory chip on the NIM-1 containing an executable program capable of bringing the system up to a state where the NIM-1 application software can be loaded onto the processor and ran.

Buffer

A packet buffer is memory space set aside for storing a packet awaiting transmission or reception over a network.

CAM

Channel Access Module (one or more, up to 4) for video, voice over IP, data, and various audio applications. For streaming purposes, each CAM has its own 100Mbps spoke on the internal high-speed bus. Slots 13, 14, 15, and 16 are available for slot insertion, provided that slot 15 is not used for NIM redundancy.


7-1

Intraplex NetXpress IP Multiplexer Version 3.05 Reference

7—Glossary

Description

CAS

Channel Associated Signaling; the transmission of signaling information within the information band, or in-band signaling.

CCS

Common Channel Signaling; transmitting signaling information on a separate channel from the data, the signaling channel controlling the data channels.

Contact

A metal strip or piece making an electrical contact when some electromechanical device (that is, relay or magnet) operates.

CM

Channel Module.

COS

IP Class of Service based on bandwidth and delay guarantees.

CPLD

Complex Programmable Logic Device; a programmable logic device is a circuit with which a designer can customize chip functionality. A CPLD is composed of several simple PLDs with a programmable switching matrix between the logic blocks.

CRC

Cyclic Redundancy Check; a number derived from a block of data and stored or transmitted with the data to detect any errors in transmission, similar but more complex than a checksum. A CRC is often calculated by adding words or bytes of data. The receiving computer recalculates the CRC from the received data and compares it to the value originally transmitted. If the values are not the same, it indicates a transmission error. The CRC is “redundant” since it adds no important information to the transmission itself.

CS

Controlled Slip; the occurrence of a replication or deletion of a T1 frame by the receiving terminal.

CSS

Controlled Split Seconds; a second with one or more controlled slips, used as an interval statistic.

CSU

Channel Service Unit; a device to terminate a digital channel on the local port.

DC

Direct Current; electrical current that goes in one direction only.

DHCP

Dynamic Host Configuration Protocol; the DHCP server assigns an IP address to a device on a session basis.

DNS

Domain Name Server; associates domain names with URL addresses.

Echo Canceller

Refers to the NIM-1 echo canceller daughterboard(s) or the process of canceling voice echo in high delay > 20 mS networks. Echo Canceller A NIM-1 echo canceller daughterboard, A Echo Canceller B NIM-1 echo canceller daughterboard, B

ES

Errored Seconds; a second in which at least one code violation (CV) was detected on the circuit; used as an interval statistic.

ES

Errored Seconds; a second in which at least one code violation (CV) was detected on the circuit; used as an interval statistic.

Ethernet

IEEE 802.1/2/3 compatible interface; LAN and data-link protocol based on a packet frame. WAN Ethernet – NIM-1/MIU-201 Interface connects to customer WAN router. LAN Ethernet – NIM-1/MIU-201 Interface connects to customer LAN network. MGMT Ethernet – NIM-1/MIU-201 Interface for management.

External Timing

Mode of timing in which an external clock source is used to generate the reference timing for the NetXpress system.

Failover

The process in which the current Active NIM fails and the Standby NIM changes its role to Active.

7-2


7—Glossary

Reference

Intraplex NetXpress IP Multiplexer Version 3.05 Description

FEC

Forward Error Correction; detects/corrects fewer than predetermined number or fraction of bits or symbols corrupted by transmission errors.

Frame

Refers to TDM Bus frames that occur at an 8 KHz rate (125 uS). Also used to refer to Ethernet frames.

FIFO

First in, first out; refers to transmitted and received packets.

FPGA

Field Programmable Gate Array; a type of gate array that is programmed in the field rather than in a semiconductor fab. Containing up to hundreds of thousands of gates, there are a variety of FPGA architectures on the market. Some are very sophisticated, including not only programmable logic blocks, but programmable interconnects and switches between the blocks. The interconnects take up a lot of FPGA real estate, resulting in a chip with very low gate density compared to other technologies.

FTP

File Transfer Protocol; used to provide file transfers across a variety of systems. This application is at the seventh layer of the OSI model.

GARP

Generic Attribute Registration Protocol; a standard for a generic method by which various devices automatically disseminate attribute information across a bridged Local Area Network (LAN).

Gateway

A node on a network representing an entrance to another network.

GLOP

A mechanism allocating multicast addresses to autonomous systems. GLOP is not an acronym or abbreviation.

GPS

Global Positioning System; developed by the U.S. Department of Defense, this is a worldwide radio-navigation system used in military, marine, and terrestrial navigation and in location based services.

GUI

Graphical User Interface; a means by which humans interact with computers via windows, buttons, and menus that the human uses a mouse to manipulate.

HTML

Hypertext Markup Language; "tag" language used to specify branch labels within a hypertext document.

HTTP

Hypertext Transfer Protocol; communications protocol that enables Web browsing.

ICMP

Internet Control Message Protocol; this protocol delivers error and control messages from hosts to message requestors.

IGMP

Internet Group Management Protocol; these statistics are the standard for IP multicasting.

INS

In Service; indicates that the NIM is currently in service.

Internal Timing

Mode of timing in which a calibrated internal oscillator is used to generate the reference timing for the NetXpress system.

IP

Internet Protocol; the IP part of TCP/IP, the protocol used to route a data packet from its source to its destination over the Internet.

JPEG

Joint Photographic Experts Group; a format that compresses graphics of photographic color depth so that the files are smaller and quicker to download. The image deteriorates in quality as you add compression.

Jitter

High-frequency delay variation as opposed to wander (low-frequency delay variation).


7-3


Reference Jitter Buffer

7—Glossary

Description A packet queue used to reorder out-of-order packets and absorb variation in packet delay across a communications network.

Jitter Buffer Avg. Delay Average buffer delay over a period of time. Jitter Buffer Delay

Actual number of received packets in the buffer multiplied by the payload size in time.

Jitter Buffer Initial Delay

Pre-filled jitter buffer, user-specified delay.

Jitter Buffer Size

Maximum number of packets that can be stored.

Jitter Buffer Underrun/ Refers to the jitter buffer fill level either exceeding the maximum fill level Overrun (overrun) or the fill level becoming so depleted that the jitter buffer can no longer be maintained (underrun). LAN

Local Area Network; short-distance data communications network, typically within a building or campus. Used to link together computers and peripherals under a standard protocol.

LCV

Line Code Violations; the number of code violations per second within the line; an interval statistic.

LED

Light Emitting Diode; an electronic device that projects a light while generating very little heat.

LES

Line Errored Seconds; a count of one-second intervals in which one or more LCV error events were detected; an interval statistic.

Loopback

Internal Loopback; loopback that loops internally generated data. For example, internal loopback could be used to test channel modules. The channel module transmit data is looped back to the receiver. External Loopback; loopback that loops externally generated data. Note: In the NIM-1, all loopbacks occur at the TDMBus and are loop thru.

MA

Module adapter.

MAC Address

Media Access Control address; unique hardware number assigned to a physical device type.

Media Switch

A switch fabric on the NIM-1 that allows the interconnection of ten TDM busses in the system: the four internal TDM busses, the two external T1/E1 ports, and the four TDM busses on the TDM-IP engine ASIC.

Media Switch Map

A complex switch map supporting applications such as IP multi-unicasting, simulcasting audio or data over the IP network and T1/E1 interface, or drop and insert of time slots between the external T1/E1 ports and the internal TDM busses.

Modulation

Process of varying some electrical carrier wave characteristics as information to be transmitted on that carrier wave varies. The three types of modulation commonly used for communications are amplitude, frequency, and phase.

MGMT

Management; the management interface for which the NetXpress system supports dynamic address assignment using DHCP.

MIB

Management Information Base; an SNMP structure that describes the particular device being monitored.

MIU

Module Interface Unit; the term used for CAM and NIM module adapters

7-4


7—Glossary

Reference


Description

MTU

Maximum Transmission Unit; the limit of bytes the interface can transmit at one time.

Multicast

Communication between one sender and multiple receivers over a network; a packet type in IP.

Netmask

A sequence of 0s and 1s that screen out (mask) the network part of an IP address; ones in the bit position are used for the network and subnet parts, while zeros are for the host.

NIM

Network Interface Module (the NetXpress multiplexer uses the NIM-1 model); the Primary NIM installs in slot 17 of the NetXpress shelf. The Backup NIM installs in slot 15 of the shelf. When coupled with the MIU-201 module interface unit, the NIM-1 provides control for T1/E1 circuit emulation, LAN and WAN traffic through 10/100 BaseT Ports, and timing control for external stream traffic and system synchronization.

NTSC

National TV Standards Committee; either the committee that developed television standards for the U.S. or the standards themselves. These standards are also used in Canada, Japan, South Korea and several Central and South American countries.

OOF

Out Of Frame; an OOF state starts when any two or four incorrect consecutive frame synchronizing bits are received from the network interface and ends when reframe occurs.

OOS

Out Of Service; indicates that the NIM is not currently in service.

Packet

In the NetXpress system, this is a reference to an IP protocol packet. Early Packet - arrives too early for assembly into the jitter buffer. Subsequently discarded. Packet sequence number determines jitter buffer location. Late Packet - arrives too late for assembly into the jitter buffer. Subsequently discarded. Packet sequence number determines jitter buffer location. Lost Packet - packet in the jitter buffer that is missing (has not arrived). Must be played out to the TDM Bus. Underrun Packet - discarded packet due to jitter buffer underrun condition. Overrun Packet - discarded packet due to jitter buffer overrun condition.

Packet Bus

High Speed Packet Bus (100 Mbs, full-duplex Ethernet) used for new modules (CAMs and NIMs).

PAD

Program Associated Data; associated with transmission (that is, song titles and station call letters).

PAL

Phrase Alternating Line; this color video and broadcasting standard has a screen resolution of 625 lines, a refresh rate of 50 Hertz, and is used primarily in western Europe and South America.

PCV

Path Coding Violations; the number of code violations per second within the path; an interval statistic.

PDU

Protocol Data Unit; a frame of data transmitted over the data link layer (for example, Ethernet and Token Ring) in a communications network. Most people do not use this term or the term “frame” but refer to every unit of data over a network as a “packet.”

PDV

Packet Delay Variation; also called “jitter.”

Plesiochronous

Almost synchronous; when sending and receiving devices of a transmission are synchronized but yet are set to different clocks.


7-5


Reference

7—Glossary

Description

PLL

Phase Lock Loop; a closed-loop feedback control system producing a signal relating to the frequency and phase of the input signals.

Power Supply

Power Supply Module for the NetXpress shelf. Main Power Supply Power supply module in right-most slot. Redundant Supply Power supply module in slot to the left of main power supply.

Primary NIM

NIM present in slot 17.

Primary Timing/ Secondary Timing/ Fallback Timing

A timing source is selected for the primary and another is selected for the secondary. The primary timing source is the most desirable. If the primary timing source is unavailable, the NIM uses the secondary timing source. If the secondary is unavailable, the NIM uses fallback timing which is fixed to be internal timing.

PTZ

Pan-Tilt-Zoom.

QoS

Quality of Service; refers to performance attributes of an end-to-end connection. Elements of a QoS definition depend on the information being transported. QoS for voice defines limits on specific parameters such as delay, signal loss, noise, and echo. QoS for data may identify attributes such as error rates, lost packet rates, throughput, and delay.

RBS

Robbed Bit Signaling; specific type of signaling that uses T1 trunks; the signaling information travels in the least significant bit of the audio channel once every sixth frame and goes into the channel without regard to the remaining bits. RBS distorts the voice audio signal so slightly that you can only perceive it by distortion measurements.

RPM

Revolutions Per Minute; the number of times per minute that a fan blade on the NetXpress power supply turns in a complete circle.

RTP

Real-time Transport Protocol; provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data.

Rx

Receive/receiver; upstream data received by the network-based router from your client.

SCB

Serial Control Bus; serial communication link between the NIM and TDM modules installed in the NetXpress shelf.

SCB2

Serial Control Bus 2; serial communication link between the NIM and Channel Access Modules installed in the NetXpress shelf.

Secondary NIM

NIM present in slot 15.

SEF

Severely Errored Framing; a SONET defect; the first indication of trouble in detecting valid signal framing patterns.

SEFS

Severely Errored Framed Seconds; a count of the number of seconds during which, at any point, the Severely Errored Framing (SEF) defect was present, used as an interval statistic.

Serial Port

NIM-1/MIU Serial Port.

SES

Severely Errored Seconds; a second with 320 CRC error events or one or more OOFs, used as an interval statistic.

Signaling

Refers to ABCD voice channel signaling in T1/E1 circuits and existing Intraplex voice channel modules.

7-6


7—Glossary


Reference

Description

SNMP

Simple Network Management Protocol; Internet standard protocol developed to manage nodes (servers, workstations, routers, switches and hubs, and so forth) on an IP network. SNMP enables network administrators to manage network performance, find and solve network problems, and plan for network growth.

SNTP

Simple Network Time Protocol.

Source / Destination

Terms used to describe the end points (locations) for an IP data packet.

Standby NIM

Role of a NIM that is either synchronized with or in process of synchronizing with the Active NIM and can take over the role of Active NIM. The Standby NIM can be either the Primary or Secondary NIM.

STL

Studio to Transmitter Links.

Stratum-1

A radio receiver which receives time from Stratum-0, the United States Naval Observatory (USNO) clock.

Stream

An IP / UDP / RTP connection and subsequent stream of data packets.

Switch Back

The process in which the Active NIM in the Secondary slot (slot 15) fails and the NIM in the Primary slot (slot 17) takes over as the Active NIM.

Synchronized State

This state indicates that the Standby NIM is synchronized with the Active NIM’s configuration database.

syslogd

syslog daemon or syslog server; the receiver of a small textual message (less than 1024 bytes) in syslog protocol, which is a protocol for forwarding log messages through an IP network.

T1/E1

Used to refer to the user-selectable T1 or E1 ports on the NIM-1 module. T1/E1 A T1/E1 Port A T1/E1 B T1/E1 Port B

T1/E1 Timing

Mode of timing in which one T1/E1 port receiver is used to generate the reference timing for the NetXpress system.

TCP

Transmission Control Protocol; data communication standard for interconnection of dissimilar networks and computing systems.

TDM

Time Division Multiplexing; method of mixing multiple signals on a single channel by transmitting in tightly controlled time slots.

TDM Bus

Intraplex TDM bus. TDM Bus 1 TDM Bus 2 TDM Bus 1A TDM Bus 1B TDM Bus 2A TDM Bus 2B

Intraplex Intraplex Intraplex Intraplex Intraplex Intraplex

TDM TDM TDM TDM TDM TDM

bus bus bus bus bus bus

(slots (slots (slots (slots (slots (slots

1 7 1 1 7 7

to to to to to to

6) 12) 6, terminal mode) 6, DI-B mode) 12, terminal mode) 12, DI-B mode)

Telnet

Internet communications protocol which enables a computer to work as a terminal while functioning from a remote computer.

Time slot

Refers to a TDM time slot. E1 time slots are 0 to 31 (time slot 0 is reserved for framing, time slot 16 is reserved for CAS signaling). T1 time slots are 1 to 24.


7-7


7—Glossary

Reference

Description

Time slot conflict

When two or more channel modules are transmitting data at the same time slot. Time slot Activity - when a single channel module is transmitting data at a particular time slot.

Timing In/Out

Timing In Timing Out

TOS

Terms Of Service; an 8-bit field in an IP packet (IP datagram) broken into five subfields that is used for quality of service (QoS).

TSL

Transmitter to Studio Link.

TTL

Time To Live; a specific time period (seconds) after which a device can delete a fragment.

Tx

Transmit/transmitter; downstream traffic transmitted from the network-based router to your client.

UAS

Unavailable Seconds; a count of one-second intervals during which service is unavailable, used as an interval statistic.

UDP

User Datagram Protocol; IP standard protocol that allows an application program on one machine to send a datagram to an application program on another machine. UDP uses the Internet IP to deliver datagrams.

Unicast

Communication between one sender and one receiver over a network.

URL

Uniform Resource Locator; the global address of documents and other resources on the World Wide Web.

VCXO

Voltage-controlled crystal oscillator.

VOM

Volt-Ohm Milliameter; in testing, an instrument measuring voltage, resistance, and amperage.

WAN

Wide Area Network; remote computer communications system. WANs allow file sharing among geographically distributed workgroups (typically at higher cost and slower speed than LANs). WANs typically use common carriers' circuits and networks. WANs may serve as a customized communication “backbone” that interconnects all of an organization’s local networks with communications trunks.

Wander

Low-frequency delay variation as opposed to jitter (high-frequency delay variation).

7-8

NIM-1/MIU-201 Timing in port. NIM-1/MIU-201 Timing out port.


No header here



7-9

Intraplex® NetXpress™ IP Multiplexer Installation & Operation Manual

Intraplex® NetXpress™ IP Multiplexer Installation & Operation Manual

Suggest Documents

INSTALLATION/OPERATION MANUAL

Installation & Operation Manual - Metron

INSTALLATION AND OPERATION MANUAL

PM2000 Operation/Installation Manual

INSTALLATION & OPERATION MANUAL

OPERATION AND INSTALLATION MANUAL

OPERATION AND INSTALLATION MANUAL

Installation and Operation Manual

Installation / Operation Manual

Installation and Operation Manual

Installation & Operation Manual

INSTALLATION - OPERATION MANUAL

INSTALLATION/OPERATION MANUAL

INSTALLATION & OPERATION MANUAL

OPERATION AND INSTALLATION MANUAL

Installation & Operation Manual

INSTALLATION AND OPERATION MANUAL

INSTALLATION & OPERATION MANUAL

Installation and Operation Manual

INSTALLATION & OPERATION MANUAL

installation & operation manual - INYOPools.com

Installation, Maintenance, Operation Manual

INSTALLATION & OPERATION MANUAL

INSTALLATION & OPERATION MANUAL