IntraUser Manual 9010v30e

NetProcessor 9010
Network Adaptor
User Manual
Release 3.0
46072497EA01
June 2008
ITALIANO
LEGGERE QUESTO AVVISO PER PRIMO!
Se non si capisce il contenuto del presente manuale
NON UTILIZZARE L’APPARECCHIATURA.
È anche disponibile la versione italiana di questo manuale, ma il costo è a carico dell’utente.
SVENSKA
LÄS DETTA FÖRST!
Om Ni inte förstår informationen i denna handbok
ARBETA DÅ INTE MED DENNA UTRUSTNING.
En översättning till detta språk av denna handbok kan också anskaffas, på Er bekostnad.
NEDERLANDS
LEES DIT EERST!
Als u de inhoud van deze handleiding niet begrijpt
STEL DEZE APPARATUUR DAN NIET IN WERKING.
U kunt tevens, op eigen kosten, een vertaling van deze handleiding krijgen.
PORTUGUÊS
LEIA O TEXTO ABAIXO ANTES DE MAIS NADA!
Se não compreende o texto deste manual
NÃO UTILIZE O EQUIPAMENTO.
O utilizador poderá também obter uma tradução do manual para o português à própria custa.
SUOMI
LUE ENNEN KÄYTTÖÄ!
Jos et ymmärrä käsikirjan sisältöä
ÄLÄ KÄYTÄ LAITETTA.
Käsikirja voidaan myös suomentaa asiakkaan kustannuksella.
FRANÇAIS
AVANT TOUT, LISEZ CE QUI SUIT!
Si vous ne comprenez pas les instructions contenues dans ce manuel
NE FAITES PAS FONCTIONNER CET APPAREIL.
En outre, nous pouvons vous proposer, à vos frais, une version française de ce manuel.
DANSK
LÆS DETTE FØRST!
Udstyret må ikke betjenes
MEDMINDRE DE TIL FULDE FORSTÅR INDHOLDET AF DENNE HÅNDBOG.
Vi kan også for Deres regning levere en dansk oversættelse af denne håndbog.
DEUTSCH
LESEN SIE ZUERST DIESEN HINWEIS!
Sollte Ihnen der Inhalf dieses Handbuches nicht klar verständlich sein, dann
BEDIENEN SIE DIESE GERÄTE NICHT!
Eine Übersetzung des Handbuches in diese Sprache ist gegen Berechnung lieferbar.
ESPAÑOL
LEA ESTE AVISO PRIMERO!
Si no entiende el contenido de este manual
NO OPERE ESTE EQUIPO.
Podemos asimismo suministrarle una traducción de este manual al (idioma) previo pago de una can-
tidad adicional que deberá abonar usted mismo.
Contacting Thomson
Contacting Thomson: www.thomsongrassvalley.com/contact/
Thomson reserves the right to make changes at any time without

prior notice in order to improve design and supply the best possible
product.
Manual Conventions
The following symbol conventions are used in this manual:
This symbol is intended to alert the User to the presence of a

potential for property damage, personal injury or death.
This symbol identifies conditions or practices that could result in

damage to this device or other property.
This symbol indicates supplemental information that helps you make

better use of the device.
This symbol indicates important information that helps you make

better use of the device.
This symbol indicates the following information will help you solve
a problem.
v
PURPOSE OF THIS MANUAL
This manual contains five chapters.

Chapter 1 - SPECIFICATIONS provides technical specifications and detailed
characteristics of the NetProcessor 9010 device.
Chapter 2 - INSTALLATION and START UP explains the operations required

on initial start up: equipment installation, connection, power up and set-up.
Chapter 3 - OPERATION WITH WEB BROWSER describes the functions

provided by the Web Interface.
Chapter 4 - SERVICING gives useful basic preventive and corrective

maintenance information.
Chapter 5 - ALARMS provides the list of alarms managed by NetProcessor 9010.
46072497EA01 NetProcessor 9010, release 3.0

June 2008 User Manual
vi
WHAT’S NEW IN RELEASE 3.0?
1. Some of the following features can be limited by software option

settings.
2. The features mentioned above are part of Product release V3.0.
This does not mean that support in XMS/XMU is simultaneous.
Please refer to the XMS/XMU User Manual to know exactly which
NetProcessor features are supported in its different releases.
¤ MPEGoverIP evolution
• The maximum throughput is now 700 Mbps compared with 520 Mbps;
• The number of IP streams processed has been multiplied by 4, an increase from
10 (Rx + Tx) to 20 Rx + 20 Tx, all with FEC according to SMPTE 2022
(Forward Error Correction for Real-Time Video/Audio Transport Over IP
Networks) designed for IP network error characteristics (packet loss and burst
loss);
• IGMP protocol adaptation is no longer automatic for source security and startup
time after linkup reasons. IGMP Protocol must be defined explicitly;
• Early network degradation signaling.
Degradation is estimated by the number of RTP frame losses within a reordering
window. It measures loss density. A threshold specifies when this density is too
high and will be used to generate an alarm. The threshold value is expressed as
consecutive lost frames and can be set to the following values: infinite (infinite
means no alarm), 1, 2, 4, 8, 16. This applies to all RTP streams (and not UDP
streams);
• Graceful degradation on IP with high error rate (with or without FEC).
As packet losses not corrected via FEC are not regenerated, the resulting IPLR
would cause PLL frequency deviation even up to unlocking. To prevent this,
empty packets are generated when packets are timed out. This feature is always
active.
NetProcessor 9010, release 3.0 46072497EA01

User Manual June 2008
vii
¤ Pricing simplification
The complete order for a product now consists of:
• A mandatory code for power supply combination (only with DC frames);
• A mandatory code for the frame (see section "Bundles" later in this document);
• An optional code for ATM extension;
• A mandatory code for application software (N901SBASAE);
• License codes (see section "Licenses" later in this document).
Bundles
With release V3.0, only 2 codes are required to order the basic working 9010
configurations: one of the 6 N901BXYYAA bundles and the software release.
The bundles include the chassis, the main board and the 10 ASI in/out board. Each
bundle is able to process 2 IP streams and/or 2 ATM streams.
Figure 1: Bundles

viii
Licenses
Incremental licenses have been replaced by unique code.
• N901SATMAA is the unique licence for ATM connections
• N901S01PAA is the unique licence for IP connections
The quantity ordered indicates the number of additional connections.
Note that newly ordered products come with 2 IP (respectively ATM) connections if
Gigabit Ethernet ports (respectively ATM ports) are present.
N901SATMAA Additional ATM stream processing, can be ordered max. 6 times for
the E3/DS3 ATM board and 8 times for the STM1/OC3 ATM board.
N901S01PAA Additional IP stream processing, can be ordered max. 38 times.

ix
Configuration examples
Minimum 9010 configuration

for transmission over IP: 2 IP
streams processed
1 x N901BMAGAA 1 PSU AC chassis, 10 ASI interfaces, 2 IP streams.

1 x N901SBASAE V3.0 basic software.
9010 configuration for

transmission over IP: processing
of 10 IP streams
1 x N901BMA0AA 1 PSU AC chassis, 10 ASI interfaces, includes the processing of

2 IP streams.
8 x N901S01PAA Options for the processing of 8 additional IP streams.
9010 configuration for

transmission over PDH/DS3:
processing of 5 ATM streams
1 x N901BMA0AA 1 PSU AC chassis, 10 ASI interfaces, includes the processing of

2 ATM streams.
1 x N901PDH0GA 1 PDH board, includes the processing of 2 ATM streams.
3 x N901S01PAA Options for the processing of 3 additional ATM streams.

x
¤ Input Transport Stream Redundancy

An option has to be ordered to obtain this feature: N901SSTRAA.
With this option, NetProcessor 9010 is used as an input Transport Stream monitor
and a 1 + 1 redundancy switch.
Any input TS can have a backup TS coming from the same media or another one
(e.g. IP and IP, IP and ATM). The NetProcessor 9010 monitors the quality of both
TSs and automatically selects the best one.
The switching conditions are:
• For ASI interface: BITRATE_OVERFLOW, LOSS_OF_STREAM,
LOSS_OF_SIGNAL, LOSS_OF_SYNCHRONISATION,
NO_STREAM_RECEIVED, PAT_NOT_PRESENT, PMT_NOT_PRESENT;
• For ATM interface: OUTPUTDEVICEERROR, STREAM_OVERFLOW,

BITRATE_UNDERFLOW, CORRECTED_ERROR, LOSS_OF_TS_SYNCHRO,
NO_STREAM_RECEIVED, UNCORRECTABLE_ERRORS, UNLOCKED_PLL,
PAT_NOT_PRESENT, PMT_NOT_PRESENT;
• For IP interface: BITRATE_OVERFLOW, BITRATE_UNDERFLOW,

LOW_QUALITY_OUTPUT_CLOCK, OUTPUTDEVICEERROR,
STREAM_OVERFLOW, UNLOCKED_PLL, NO_STREAM_RECEIVED,
LOSS_OF_TS_SYNCHRO, FRAMING_ERROR, UNCORRECTABLE_ERRORS,
LOSS_OF_FRAME, SIGNAL_DEGRADE, PAT_NOT_PRESENT,
PMT_NOT_PRESENT.
Three (global) modes are managed:
• No redundancy;
• Revertive Redundancy (connection goes back to nominal after a "holdover"
period of time. The "holdover" period of time is the time for a nominal to be
continuously OK before switching back from backup). Holdover can be set to
10 s, 30 s or 60 s;
• Non-revertive redundancy (connection never goes back to nominal).
For each redundancy group, the Operator can select a manual mode to enable the
direct switch command.
Nominal, backup and switch states can be read via SNMP.

xi
Input Transport Stream Redundancy performances are:

• 0.7s from event to switch action;
• Switch time is packet accurate.
NetProcessor 9010 automatic stream redundancy is mutually

exclusive with redundancy management by XMS/XMU.
¤ GUI changes
• IP TX configuration page readability has been improved. Parameters are now
displayed in a more natural order, with a clear separation between ordinary and
expert parameters.
• The Data service configuration page has been simplified, as policing rate entry is
no longer proposed. Rate is simply regulated according to ATM settings.
• A threshold can be set for all IP inputs to raise an alarm with some anticipation of
FEC overflow.
• Internal connection configuration has been changed to adapt to the new
redundancy feature.
¤ ATM Data service improvement

ATM data service performance has been redesigned to offer better performance and
stability with LAN traffic. It offers large buffering to cope with traffic with many
concurrent TCP sessions.
¤ Upgrade to V3.0 SW release

V2.0 to V3.0 and V2.5 to V3.0 upgrades are allowed. Order the V3.0 software CD:
N901SBASAE.
When upgrading, the existing license commercial codes are converted.
Legacy hardware is still supported by V3.0 release with a restriction on
performance enhancement. These enhancements are not available with
N9010A00GB and N9010A1PGB legacy main boards.

xii
BLANK PAGE

General Safety Instructions xiii
General Safety Instructions
Please observe the following safety precautions to avoid injury and prevent damage to
this product or any products connected to it.
These servicing instructions are for use by qualified personnel only. To
avoid any risk of electric shock, do not perform any servicing other than
that contained in the Operating Instructions unless you are qualified to
do so. Refer all servicing to qualified service personnel.
SAFETY PRECAUTIONS
AC mains power cord AC mains cords are only shipped with devices if
ordered. Otherwise, it is advisable to use mains
cords as described in section Power supply and
protective ground restrictions page 96.
DC power supply cord Use the power supply cords shipped with the
device. See section Power supply and protective
ground restrictions page 96.
Avoid electric overload Do not apply a mains voltage that is outside the
range specified in this manual.
Reliable earthing Ensure that your device is properly grounded before
power-up. Grounding is through the power cord.
Mains power and circuit The connection panel should feature overload and
overloading earth fault protection and a bipolar cut-off device or
a differential circuit breaker.
DC power and circuit The connection panel should feature protection
overloading against overload, which accepts 48V + 20%
tensions and supports inrush current when the
device is plugged in.

xiv General Safety Instructions
Mains power: The connection panel should comply with the

Connection panel legislation in force in the country of installation.
Connection panel position in the rack must ensure
that plug and power cord are within easy reach for
switching off purposes.
Rack Mount Elevated Operating Ambient: If installed in a
instructions closed or multi-unit rack assembly, the operating air
ambient temperature of the rack environment may
be greater than room ambient. Provide proper
ventilation as described in section Rack mounting
page 88 to keep the equipment in an environment
compatible with the maximum ambient temperature
(Tma=50°C) specified by the manufacturer.
Reduced Air Flow: installation of the equipment in
a rack should be such that the amount of air flow
required for safe operation of the equipment is not
compromised.
Mechanical loading: mounting of the equipment in
the rack should be such that a hazardous condition
is not achieved due to uneven mechanical loading.
Circuit Overloading: considerations should be
given to the connection of the equipment to the
supply circuit and the effect that overloading of the
circuits might have on overcurrent protection and
supply wiring. Appropriate consideration of
equipment nameplate ratings should be used when
addressing this concern.
Reliable earthing: reliable earthing of
rack-mounted equipment should be maintained.
Particular attention should be given to supply
connections other than direct connections to the
branch circuit (e.g. use of power strips).
Power disconnecting: disconnect power before
removing protective panel, soldering or replacing
components (these operations can be performed by
qualified service personnel only).

General Safety Instructions xv
Rack Mount The chassis must not be fixed with its rack
instructions mounting ears only. If you intend to install it in a
rack, L-profiles are required and you must observe
the ventilation and safety instructions described in
section Rack mounting page 88.
Do not operate without To avoid electric shock or fire hazard, do not
covers operate this equipment with cover or blank panels
removed.
Overload protection Power supply unit has integrated overload
protection which cannot be accessed or reset. In the
event of a malfunction, please contact the Thomson
Customer Services Department.
Do not operate in To avoid injury or fire hazard, do not operate this
explosive atmosphere product in an explosive environment (atmosphere
and materials).
Do not operate in To avoid electric shock, this product should only be
wet/damp conditions operated in dry conditions.
Multiple Power Supply The chassis may or does feature more than one
(Servicing) power supply cords. To reduce the risk of electric
shock, disconnect all power supply cords before
servicing.
Handling precautions To avoid injury while installing the device in a rack
(or removing it from a rack), take all the necessary
precautions. Ask another person for help or use an
adapted carry lift.

xvi General Safety Instructions
Replacement of RAM The product includes non volatile RAM with

with built-in lithium built-in lithium batteries which should never require
battery replacing. If for any reason replacement does prove
necessary, please observe the following conditions:
. The operation must only be performed by
qualified personnel;
. Only replace with the same or equivalent memory
type. Caution: Danger of explosion if memory is
incorrectly replaced;
. Ensure the memory is inserted the right way
round;
. Please dispose of dead memories according to the
manufacturer’s instructions.
Class 1 Laser The device may or does feature a board emitting
class 1 invisible laser radiation (SFP OSH and SFP
OLH ATM boards).
Caution: the use of controls or adjustments or
performance of procedure other than those specified
herein may result in hasardous radiation exposure.
No standard applies to this device. Nevertheless,
you are strongly recommended not to look directly
at the optical connector when the device is switched
on (or the end of the fibre connected to it).
Laser characteristics:
For SFP OSH: Class1, 1300 nm, AVAGO,
HFCT-5760TL, CDRH n°9521220-47 et TUV
n°933/510116/02, maximum optical output power:
-8dBm.
For SFP OLH: Class1, 1300 nm, AVAGO,
HFCT-5760TL, CDRH n°9521220-46 et TUV
n°933/510206/03, maximum optical output power:
-8dBm.
Specific safety Finland: Laite on liitettävä
instructions for suojamaadoituskoskettimilla varustettuun
Finland, pistorasiaan.
Norway and Sweden Norway: Apparatet må tilkoples jordet stikkontakt.
Sweden: Apparaten skall anslutas till jordat uttag.

General Safety Instructions xvii
PRODUCT DAMAGE PRECAUTIONS
Fitting Observe the installation instructions in section Rack

mounting page 88.
Dusty atmosphere As the device features no air filter, it must be
mounted in a dust free environment. Refer to
section Rack mounting page 88.
Provide proper Provide proper ventilation to prevent product
ventilation overheating. Refer to section Rack mounting page
88. All empty slots should be fitted with blank
panels (mask plates) so as not to impair ventilation.
Do not operate with If you suspect there is damage to this product, have
suspected failures it inspected by qualified service personnel.
Replacing components Only use components from or approved by
Thomson.
Retain original If equipment is returned to the Customer Service
packaging Department, the faulty device must be packed
where possible in its original packaging (protective
corners and boxes). If you no longer have the
packaging, the faulty device must be protected
against shocks during transportation.
The Customer Service Department examines
packaging on arrival and can refuse to carry out
repairs if the packaging has been visibly damaged
during transportation and this has led to further
damage in addition to the fault originally noted.
Transportation costs and risks for equipment returns
are borne by the customer. Equipment should only
be returned with a Return Material Authorisation
form.

xviii General Safety Instructions
BLANK PAGE

CONTENTS xix
Contents
Contacting Thomson .....................................................................................iii
Manual Conventions ......................................................................................iv
Purpose of this manual ..................................................................................v
What’s new In release 3.0? ...........................................................................vi
General Safety Instructions ........................................................................xiii
CHAPTER 1
SPECIFICATIONS
1.1 - System overview ............................................................................................... 3
1.1.1 - Introduction.................................................................................................. 3
1.1.2 - Applications ................................................................................................. 3
1.2 - Product overview............................................................................................... 6

1.2.1 - Interfaces and processing ........................................................................... 6
1.2.2 - Input Transport Stream Redundancy .......................................................... 7
1.2.3 - Supervision.................................................................................................. 8
1.3 - Ordering guide................................................................................................... 9
1.4 - Device description........................................................................................... 14

1.4.1 - Front panel ................................................................................................ 14
1.4.2 - Rear panel................................................................................................. 15
1.4.2.1 - Power inlet ..................................................................................... 15
1.4.2.2 - Inputs/Outputs................................................................................ 16
1.4.3 - NetProcessor 9010’s functional architecture............................................. 23
1.4.4 - ASI network interface ................................................................................ 25
1.4.4.1 - MPEG over ASI adaptation layer ................................................... 26
1.4.4.2 - MPEG over ASI rate capacity ........................................................ 27
1.4.4.3 - Latency .......................................................................................... 27
1.4.5 - ATM network adaptation ........................................................................... 28

xx CONTENTS
1.4.5.1 - MPEG over ATM Adaptation layer ................................................. 29

1.4.5.1.1 - Transmission .................................................................... 29
1.4.5.1.2 - Reception ......................................................................... 30
1.4.5.2 - Network interface features.............................................................. 31
1.4.5.2.1 - Multiplexing (ATM layer)................................................... 31
1.4.5.2.2 - Data links.......................................................................... 34
1.4.5.2.3 - Physical layer ................................................................... 40
1.4.5.3 - MPEG over ATM rate capacity ....................................................... 42
1.4.5.4 - Latency ........................................................................................... 43
1.4.6 - IP network adaptation ................................................................................ 44
1.4.6.1 - MPEG over IP adaptation layer ...................................................... 45
1.4.6.1.1 - Transmission .................................................................... 45
1.4.6.1.2 - Reception ......................................................................... 51
1.4.6.2 - Network Interface ........................................................................... 53
1.4.6.2.1 - IP routing .......................................................................... 53
1.4.6.2.2 - In-Band management....................................................... 53
1.4.6.2.3 - MAC Layer and VLAN support ......................................... 53
1.4.6.2.4 - Gigabit Ethernet ports ...................................................... 54
1.4.6.3 - MPEG over IP rate capacity ........................................................... 55
1.4.6.4 - MPEG over IP overheads............................................................... 55
1.4.6.4.1 - Stacks and overheads...................................................... 55
1.4.6.4.2 - Calculating used bandwidth ............................................. 57
1.4.6.5 - Latency ........................................................................................... 58
1.4.7 - TS Routing ................................................................................................. 60
1.4.8 - Input Transport Stream redundancy .......................................................... 61
1.5 - Description of the management systems...................................................... 67

1.5.1 - SNMP agent............................................................................................... 69
1.5.1.1 - Agent .............................................................................................. 69
1.5.1.2 - MIB ................................................................................................. 69
1.5.2 - Web Interface............................................................................................. 70
1.5.3 - Command Line Interface (CLI)................................................................... 70
1.5.4 - XMS 3500 eXtensible Management System ............................................. 70
1.6 - Standard Compliance ...................................................................................... 71
1.7 - General device Specifications ........................................................................ 73

1.7.1 - Electrical specifications.............................................................................. 73
1.7.2 - Mechanical features................................................................................... 76
1.7.3 - Ventilation .................................................................................................. 78
1.7.4 - Environmental specifications ..................................................................... 79
1.7.5 - Reliability.................................................................................................... 80
1.8 - EU declaration of conformity.......................................................................... 81

CONTENTS xxi
CHAPTER 2
INSTALLATION AND START UP
2.1 - Installation procedure ..................................................................................... 85
2.2 - NetProcessor 9010 mechanical features....................................................... 86
2.3 - Rack mounting................................................................................................. 88

2.3.1 - Removing the securing brackets ............................................................... 88
2.3.2 - NetProcessor 9010 installation requirements............................................ 89
2.3.3 - Ventilation restrictions ............................................................................... 89
2.3.4 - Cabling restrictions.................................................................................... 95
2.3.5 - EMC ground restrictions............................................................................ 95
2.3.6 - Power supply and protective ground restrictions....................................... 96
2.3.6.1 - Power inlet ..................................................................................... 96
2.3.6.2 - Power supply cord(s) ..................................................................... 97
2.3.6.2.1 - Cord(s) for AC mains power supply ................................. 97
2.3.6.2.2 - Cord(s) for DC power supply ........................................... 98
2.3.7 - Mechanical and Electrical Specifications .................................................. 99
2.3.7.1 - Mechanical specifications .............................................................. 99
2.3.7.2 - Electrical specifications ................................................................ 101
2.4 - Power up ........................................................................................................ 104
2.5 - Setting the initial parameters via the Command Line Interface................ 105
2.5.1 - Accessing the Command Line Interface.................................................. 105
2.5.2 - Login and password ................................................................................ 107
2.5.3 - Help ......................................................................................................... 109
2.5.4 - Setting initial parameters......................................................................... 110
2.5.5 - Commands relating to IP parameters...................................................... 111
2.5.5.1 - Displaying IP parameters (ipdisp) ................................................ 111
2.5.5.2 - Editing IP parameters (ipset) ....................................................... 111
2.5.6 - Commands relating to the date and time ................................................ 113
2.5.6.1 - Displaying the current date and time (ddate) ............................... 113
2.5.6.2 - Changing the date and time (sdate)............................................. 113
2.5.7 - Commands related to the number of ASI inputs for
the ASI FLEX board............................................................................................ 114
2.5.7.1 - Displaying the number of ASI inputs for ASI FLEX board (dasiin) 115
2.5.7.2 - Editing the number of ASI inputs for ASI FLEX board (sasiin)..... 115
2.5.8 - Commands related to SysName, SysContact and SysLocation ............. 117
2.5.8.1 - Displaying SysName, SysContact and SysLocation (rinfo) ......... 117
2.5.8.2 - Editing SysName, SysContact and SysLocation (winfo).............. 118
2.6 - Connecting the cables .................................................................................. 119

xxii CONTENTS
2.6.1 - Connecting the cables on the main board ............................................... 119

2.6.2 - Connecting the cables on the Gigabit Ethernet interfaces....................... 121
2.6.3 - Connecting the cables on the ATM extension board ............................... 121
2.6.4 - CMD1 LEDS ............................................................................................ 122
CHAPTER 3
OPERATION WITH WEB INTERFACE
3.1 - Introduction .................................................................................................... 125
3.1.1 - Foreword.................................................................................................. 125
3.1.2 - Introduction .............................................................................................. 125
3.1.3 - Setting the device .................................................................................... 125
3.1.4 - Step 1: Setting the interface static parameters ........................................ 127
3.1.5 - Step 2: Setting the dynamic Tx and Rx network
communication parameters................................................................................. 130
3.1.6 - Step 3: Managing internal TS connections (patch panel) ........................ 135
3.1.7 - Step 4: Setting data service over ATM and In-Band Control & Command over
ATM parameters ................................................................................................. 141
3.2 - Web Interface page breakdown .................................................................... 144
3.3 - Setting up the link between the PC and the Web Interface........................ 145
3.4 - Identification page ......................................................................................... 147

3.4.1 - LEDs ........................................................................................................ 147
3.4.2 - Charts ...................................................................................................... 148
3.4.2.1 - Clicking on the charts ................................................................... 148
3.4.2.2 - Shortcut commands attached to the charts .................................. 150
3.5 - Installation menu ........................................................................................... 162

3.5.1 - In-Band Control & Command over ATM setup menu .............................. 163
3.5.2 - Data service over ATM menus................................................................. 166
3.6 - Configuration menu....................................................................................... 169

3.6.1 - Top view menus....................................................................................... 170
3.6.1.1 - Interface setup menus .................................................................. 171
3.6.1.1.1 - ASI setup dialog boxes................................................... 172
3.6.1.1.2 - ATM setup dialog boxes................................................. 173
3.6.1.1.3 - IP setup dialog boxes ..................................................... 176
3.6.1.2 - Rx and Tx setup menus................................................................ 181
3.6.1.2.1 - ATM Rx and ATM Tx setup menus ................................ 182
3.6.1.2.2 - IP Rx and IP Tx setup menus......................................... 186
3.6.1.3 - Patch panel................................................................................... 197

CONTENTS xxiii
3.6.1.3.1 - Connection list ............................................................... 197

3.6.1.3.2 - Input Transport Stream Redundancy............................. 202
3.6.1.3.3 - Alarm setup for early IP network degradation signaling. 216
3.6.2 - Connection list menu............................................................................... 217
3.6.3 - Stored configurations command.............................................................. 218
3.7 - Maintenance menu ........................................................................................ 225

3.7.1 - Reboot..................................................................................................... 225
3.7.2 - Options .................................................................................................... 226
3.7.3 - Global setting .......................................................................................... 227
3.8 - Status menu ................................................................................................... 228

3.8.1 - All alarms page........................................................................................ 228
3.8.2 - Events page ............................................................................................ 229
3.8.3 - Report page............................................................................................. 230
3.9 - Monitoring menu ........................................................................................... 231

3.9.1 - Monitoring menu...................................................................................... 231
3.9.2 - Network port counters page .................................................................... 232
CHAPTER 4
SERVICING
4.1 - Introduction.................................................................................................... 235
4.2 - Accessing the Command Line Interface ..................................................... 236

4.2.1 - Accessing the Command Line Interface.................................................. 236
4.2.2 - Login and password ................................................................................ 238
4.3 - Installing software options ........................................................................... 240

4.3.1 - Introduction.............................................................................................. 240
4.3.2 - Displaying software options (lsopt).......................................................... 240
4.3.3 - Ordering and installing a software option ................................................ 241
4.4 - Downloading software .................................................................................. 244

4.4.1 - Introduction.............................................................................................. 244
4.4.2 - Displaying firmware releases (view)........................................................ 245
4.4.3 - Downloading procedure (server, down, view, result, togg) ..................... 246
4.4.4 - Procedure for returning to the previous software release ....................... 249
4.4.5 - Upgrade from V2.x to V3.0...................................................................... 249
4.4.6 - Upgrade a V1.5 Product.......................................................................... 249
4.5 - Erasing the configurations ........................................................................... 250

xxiv CONTENTS
4.6 - Community strings and access rights......................................................... 251

4.6.1 - Introduction .............................................................................................. 251
4.6.1.1 - Accessibility values....................................................................... 251
4.6.1.2 - Access level values ...................................................................... 251
4.6.2 - Community string edition ......................................................................... 251
4.7 - Maintenance ................................................................................................... 254

4.7.1 - Cleaning chassis ventilation grids............................................................ 254
4.7.2 - Replacing the fans ................................................................................... 254
4.7.3 - Replacing a PSU in a chassis with two Power Supply units .................... 254
4.7.3.1 - Fault diagnosis ............................................................................. 255
4.7.3.2 - Procedure for replacing a PSU..................................................... 255
4.8 - Installing an NTP server under Windows 2000 and Windows XP ............. 257
4.8.1 - Architecture.............................................................................................. 257
4.8.2 - Installation................................................................................................ 258
4.9 - Installing an FTP server under Windows 2000 and Windows XP.............. 263
4.9.1 - Installation................................................................................................ 263
4.9.2 - Setting up the server................................................................................ 264
CHAPTER 5
ALARMS
INDEX

Chapter 1 - Specifications 1
Chapter 1
Specifications
1.1 - System overview .................................................................................... 3

1.1.1 - Introduction ....................................................................................... 3
1.1.2 - Applications ...................................................................................... 3
1.2 - Product overview ................................................................................... 6

1.2.1 - Interfaces and processing................................................................. 6
1.2.2 - Input Transport Stream Redundancy................................................ 7
1.2.3 - Supervision ....................................................................................... 8
1.3 - Ordering guide........................................................................................ 9
1.4 - Device description ............................................................................... 14

1.4.1 - Front panel...................................................................................... 14
1.4.2 - Rear panel ...................................................................................... 15
1.4.2.1 - Power inlet ..................................................................................... 15
1.4.2.2 - Inputs/Outputs................................................................................ 16
1.4.3 - NetProcessor 9010’s functional architecture .................................. 23
1.4.4 - ASI network interface...................................................................... 25
1.4.4.1 - MPEG over ASI adaptation layer ................................................... 26
1.4.4.2 - MPEG over ASI rate capacity ........................................................ 27
1.4.4.3 - Latency .......................................................................................... 27
1.4.5 - ATM network adaptation................................................................. 28
1.4.5.1 - MPEG over ATM Adaptation layer ................................................. 29
1.4.5.1.1 - Transmission................................................................................. 29
1.4.5.1.2 - Reception...................................................................................... 30
1.4.5.2 - Network interface features ............................................................. 31
1.4.5.2.1 - Multiplexing (ATM layer) ............................................................... 31
1.4.5.2.2 - Data links ...................................................................................... 34
1.4.5.2.3 - Physical layer................................................................................ 40
1.4.5.3 - MPEG over ATM rate capacity ...................................................... 42
1.4.5.4 - Latency .......................................................................................... 43
1.4.6 - IP network adaptation ..................................................................... 44

2 Chapter 1 - Specifications
1.4.6.1 - MPEG over IP adaptation layer ...................................................... 45

1.4.6.1.1 - Transmission ................................................................................. 45
1.4.6.1.2 - Reception ...................................................................................... 51
1.4.6.2 - Network Interface ........................................................................... 53
1.4.6.2.1 - IP routing ....................................................................................... 53
1.4.6.2.2 - In-Band management.................................................................... 53
1.4.6.2.3 - MAC Layer and VLAN support ...................................................... 53
1.4.6.2.4 - Gigabit Ethernet ports ................................................................... 54
1.4.6.3 - MPEG over IP rate capacity ........................................................... 55
1.4.6.4 - MPEG over IP overheads............................................................... 55
1.4.6.4.1 - Stacks and overheads................................................................... 55
1.4.6.4.2 - Calculating used bandwidth .......................................................... 57
1.4.6.5 - Latency ........................................................................................... 58
1.4.7 - TS Routing ..................................................................................... 60
1.4.8 - Input Transport Stream redundancy............................................... 61
1.5 - Description of the management systems .......................................... 67

1.5.1 - SNMP agent ................................................................................... 69
1.5.1.1 - Agent .............................................................................................. 69
1.5.1.2 - MIB ................................................................................................. 69
1.5.2 - Web Interface ................................................................................. 70
1.5.3 - Command Line Interface (CLI) ....................................................... 70
1.5.4 - XMS 3500 eXtensible Management System .................................. 70
1.6 - Standard Compliance .......................................................................... 71
1.7 - General device Specifications ............................................................ 73

1.7.1 - Electrical specifications .................................................................. 73
1.7.2 - Mechanical features ....................................................................... 76
1.7.3 - Ventilation....................................................................................... 78
1.7.4 - Environmental specifications .......................................................... 79
1.7.5 - Reliability ........................................................................................ 80
1.8 - EU declaration of conformity .............................................................. 81

1.1 - System overview
1.1 - SYSTEM OVERVIEW
1.1.1 - Introduction
NetProcessor 9010 is a 1RU highly integrated network adaptor designed for

pass-through bit-accurate transmission of MPEG2-TS streams over PDH or SDH
lines and ATM or IP networks. It can transport either MPEG-2 or MPEG-4, either
SD or HD.
Simultaneous support of ATM and IP networking offers a smooth migration path
from legacy telecom standard to IP.
NetProcessor 9010 is not a modular product but offers flexibility via hardware and
software configuration options. NetProcessor 9010 can be equipped with a dual port
ATM network interface and/or a dual port 1000Base-T/1000Base-X IP network
interface.
NetProcessor 9010 can support up to 10 DVB ASI IN or OUT interfaces.
NetProcessor 9010 is managed via an embedded web server, and provides an
SNMP agent.
NetProcessor 9010 is supported by the Thomson XMS 3500 management system.
NetProcessor 9010 is available with one AC Power Supply or with two Power
Supplies in any mode (2 AC, 2 DC or 1 AC + 1 DC) for redundancy.
1.1.2 - Applications
The NetProcessor 9010 network adaptor meets a wide variety of applications such
as primary distribution, contribution, high-quality videoconferencing and
telemedicine, etc.
Nevertheless, contribution and primary distribution are the two privileged
applications of the NetProcessor 9010 network adaptor.

¤ Contribution system architecture

Contribution includes events coverage (in fixed or mobile infrastructure) and
exchanges between production and post-production centers.
Transmission of MPEG compressed video over any telecom network

Figure 1.1: NetProcessor 9010 in Contribution

¤ Primary distribution system architecture

Primary distribution covers the broadcast of services from studios to primary
headends and from primary headends to secondary headends. The diagram below
shows how the NetProcessor 9010 network adaptor can be used in conjunction with
the NetProcessor 9030/9040.
Figure 1.2: NetProcessor 9010 in the Broadcasting architecture

1.2 - Product overview
1.2 - PRODUCT OVERVIEW
ASI interface (10 ASI In/Out)
2 Gigabit Ethernet network interface ports CMD management port
2 ATM network interface ports (PDH E3 / DS3 or SDH STM1 / STS3c optical, electrical)
Figure 1.3: NetProcessor 9010 rear panel
1. Some of the following features can be limited by software option

settings.
2. The features mentioned above are part of the Product release V3.0.
This does not mean that support in XMS/XMU is simultaneous.
Please refer to the XMS/XMU User Manual to know exactly which
NetProcessor features are supported within its different releases.
1.2.1 - Interfaces and processing
• DVB ASI service interfaces

- Up to 10 ASI In or Out interfaces are available for MPEG transmission over
ATM or for MPEG transmission over IP.
• ATM network interfaces
- 2 network interfaces are available per chassis. Each of them can be PDH
E3 / DS3 or SDH STM1 / STS3c (electrical or optical),
- MPEG over ATM adaptation provides:
- emission of up to 4 MPEG streams and reception of up to 4 MPEG
streams with the PDH E3/DS3 interface board.
- simultaneous emission of up to N MPEG streams and reception of up to

(10-N) MPEG streams with the SDH STM1 / STS3c interface board.
- Encapsulation is AAL1 with or without FEC,
- Connection mode is PVC.
• IP network interface
- Two 1000Base-T/1000Base-X interfaces are available per chassis,
- Unicast and Multicast modes are supported,
- Transmission uses either RTP/UDP encapsulation with or without FEC, or
UDP encapsulation.
- Reception uses RTP/UDP encapsulation with or without FEC.
- Source Specific Multicast (SSM) is supported. SSM is an IP technology
where the destination host can select a source when joining a multicast
group.
- The number of IP streams processed is 20 Rx + 20 Tx, all with FEC
according to SMPTE 2022 (Forward Error Correction for Real-Time
Video/Audio Transport Over IP Networks) designed for IP network error
characteristics (packet loss and burst loss).
• Data service
- The Data service feature consists of Ethernet bridging between
NetProcessor 9010 Extension 1 port (configured as a 10/100 Ethernet port)
and one ATM PVC.
1.2.2 - Input Transport Stream Redundancy
Input TS redundancy requires a software option license (N901SSTRAA).

Any input TS can have a backup TS coming from the same media or another one
(e.g. IP and IP, IP and ATM).
The switch can be either triggered:
• in manual mode (Operator explicitly toggles inputs);
• in revertive automatic mode (switch is automatic, switch back also);
• in non-revertive automatic mode (switch is automatic, switch back is performed
by the Operator).
Nominal, backup and switch states can be read via SNMP.

NetProcessor 9010 automatic stream redundancy is mutually

exclusive with redundancy management by XMS/XMU.
1.2.3 - Supervision
NetProcessor 9010 is managed over a range of interfaces:

• A Web server gives access to the detailed configuration parameters and all
monitoring information;
• An SNMP V2 agent provides a specific MIB to third-party NMS for element
monitoring.
• An FTP client provides easy configuration upload/download and software
upgrade/downgrade.
• An NTP client provides element synchronization.
These are available via a 100Base-T port (CMD1 port used for Commands,
Monitoring & Diagnostics). A basic interface for setup and maintenance operations
is also available via either Telnet or RS232.

1.3 - Ordering guide
1.3 - ORDERING GUIDE
Figure 1.4: Ordering references

NP9030 Main units
N901BMyyAA: NetProcessor 9010 Single AC PSU in 1RU chassis

N901BMA0AA NetProcessor 9010 single AC Power Supply chassis for
transmission over E3/DS3/STM1/ATM, 10 ASI ports
configurable in/out. One ATM option board MUST be ordered
N901BMAGAA NetProcessor 9010 single AC Power Supply chassis for

transmission over IP, 10 ASI ports configurable in/out. Can
support an ATM option board.
N901BAyyAA: NetProcessor 9010 Dual swappable AC PSU in 1RU chassis

N901BAA0AA NetProcessor 9010 dual hot swappable AC Power Supply chassis
for transmission over E3/DS3/STM1/ATM. 10 ASI ports
configurable in/out. One ATM option board MUST be ordered
N901BAAGAA NetProcessor 9010 dual hot swappable AC Power Supply chassis

for transmission over IP. 10 ASI ports configurable in/out. Can
support an ATM option board.

N901BDyyAA: NetProcessor 9010 Dual swappable DC/DC or DC/AC PSU

in 1RU chassis
One DC Power Supply Unit is included. The second Power Supply Unit MUST
BE ORDERED and chosen between DC and AC.
N901BDA0AA NetProcessor 9010 DC/DC or DC/AC dual Power Supply in 1RU
chassis for transmission over E3/DS3/STM1/ATM. One DC
Power Supply included. The second Power Supply MUST BE
ORDERED and chosen between DC and AC. 10 ASI ports
configurable in/out. One ATM option board MUST be ordered.
N901BDAGAA NetProcessor 9010 DC/DC or DC/AC dual Power Supply in 1RU

chassis for transmission over IP. One DC Power Supply included.
The second Power Supply MUST be ordered and chosen between
DC and AC. 10 ASI ports configurable in/out. Can support an
ATM option board.
Power Supplies (Second Power Supply for Dual swappable PS Chassis)

N900PS2AAA Second Power Supply for AC/DC Chassis (mounting kit included),
110/220VAC Version.
N900PS2DAA Spare Power Supply Unit for AC/DC or DC/DC dual PS chassis,
-48VDC Version.
Power Supplies (Spare)

N900SPACGA Spare Power Supply Unit for AC/AC or AC/DC dual PS chassis,
110/220VAC Version.
N900SPDCGA Spare Power Supply Unit for Netxxx chassis, -48VDC Version.
Cables (Options)
N900RSRJAA RS232 serial link over RJ45 for fine-tuning and maintenance
purposes
N900PCEUAA Power cord for continental Europe.
N900PCUSAA Power cord for US and Japan.
N900PCUKAA Power cord for UK.
N900PCSWAA Power cord for Switzerland.
N900PCAUAA Power cord for Australia.
N900PCARAA Power cord for Argentina.

Hardware Options
SFP Transceivers for Gigabit Ethernet ports
N900GSF0GA SFP duplex optical multimode transceiver for the Gigabit Ethernet
interfaces.
N900GSF1GA SFP duplex optical single mode short haul transceiver for the
Gigabit Ethernet interfaces.
SFP Transceivers for STM1 ports

N900SSF0GA SFP duplex optical multimode transceiver for the STM1 boards.
N900SSF1GA SFP duplex optical single mode short haul transceiver for the
STM1 boards.
N900SSF2GA SFP duplex optical single mode long haul transceiver for the STM1
boards.
N900SSF3GA SFP duplex electrical transceiver for the STM1 boards.
ATM extension
N901PDH0GA PDH E3/DS3 ATM network interface board. 2 bidirectional ports -
1 active. Software configurable E3 or DS3. Licenses to activate
additional ATM streams have to be ordered. Max ATM streams for
MPEG: 4 in + 4 out.
N901STMFGA SDH-STM1/ Sonet-OC3 ATM network interface board. 2

bidirectional ports - 1 active. Software configurable STM1 or OC3.
SFP modules MUST be ordered. Mix of SFP type is allowed.
Licenses to activate additional ATM streams have to be ordered.
Max ATM streams supported for MPEG: 10, mix of Rx and Tx

Software
Main Software
N901SBASAE NetProcessor 9010 Basic software license release V3.0. Includes
the delivery of a documentation CD-ROM. 2 active IP streams (for
chassis supporting transmission over IP), 2 active ATM stream (for
chassis with ATM option board). .
Software Options
Additional ATM streams
N901SATMAA Software option. Additional ATM streams can be ordered (max 6
times for the E3/DS3 ATM board and 8 times for the STM1/OC3
ATM board). Available from release V3.0.
Additional IP streams
N901S01PAA Software option. Additional IP streams can be ordered (max 38
times for max 20 IP connections out + 20 IP connections in).
Available from release V3.0.
Miscellaneous options
N901SAEPAA Software option. License for activation of the second ATM physical
port.
N901S1EPAA Software option. License for activation of the second Gigabit
Ethernet physical port.
N903S10AAA Software option. License for IP data services over ATM over a
dedicated 100BTport. Available from release V2.0.
N901SETRAA Software option. License for TS and bitrate monitoring.
N901SSTRAA Software option. License for automatic input Transport Stream
redundancy.

1.4 - Device description
1.4 - DEVICE DESCRIPTION
NetProcessor 9010 is built in a 1RU chassis which is designed for standard 19"
racks.
Electrical and mechanical features are given at the end of this chapter (page 73).
1.4.1 - Front panel
Figure 1.5: NetProcessor 9010 front panel
The NetProcessor 9010’s front panel features a set of three LEDs to provide a visual
indication of overall device operation.
The various LEDs indicate the following:
LED Colour Description

POWER green Device on
UNIT FAIL red Major alarm preventing operation
WARNING orange Minor alarm not preventing operation or start-up phase

1.4.2 - Rear panel
1.4.2.1 - Power inlet

The power outlet comprises a connector without an On/Off switch.
There are four kinds of power inlet according to the chassis model.
• chassis with one built-in AC Power Supply.
• chassis with two AC Power Supplies for redundancy.
• chassis with two DC Power Supplies for redundancy.
• chassis with one AC Power Supply and one DC Power Supply for redundancy.
Figure 1.6: Chassis models and their associated power supply inlets

1.4.2.2 - Inputs/Outputs
1 10 ASI IN / OUT
GPS
EXT #1 EXT #2 CMD2 USB
4 EXT 3 CMD1 2 TERM
LAN/WAN LAN/WAN GPS, CMD2, USB, EXT 2

port #1 port #2 not available in this
ATM #1 ATM #2
product release
6 ATM network interface 5 Gigabit Ethernet interface
Connector Description
ASI 1 Ten DVB-ASI standard TS coaxial ports in compliance with CENELEC
to EN 50083-9 (DVB - PI). These ports can be programmed individually as
ASI 10 inputs or outputs via the CLI interface (sasiin command). When a port is
programmed as an output, the orange LED located near the connector
lights up. All output ports are grouped on the right hand side of the strip.
Features for ASI IN:
• Connector type: BNC, 75 ohms
• Bitrate: 270 Mbit/s
• MPEG bitrate: driven by transport capabilities (see section “MPEG
over ASI rate capacity”, page 27)
• Accepted format: 188, 188+16 (no Reed-Solomon decoding support)
• Accepted traffic: Data burst mode (byte per byte) or Data Packet mode
(packet per packet).
• Code: 8b/10b
• Min. sensitivity (D21.5 idle pattern): 200 mV
• Max. input voltage: 880 mV p-p
• Return loss (S11 in the range of 0.1 to 1.0 x bitrate): - 17 dB
• Return loss between 0.3MHz and 1GHz: - 15dB

Features for ASI OUT:

• Connector type: BNC, 75 ohms
• Bitrate: 270 Mbit/s
• MPEG bitrate: driven by transport capabilities (see section “MPEG
over ASI rate capacity”, page 27)
• Generated format: 188, 188+16 (no Reed-Solomon encoding support)
• Generated traffic: Data Packet mode (packet per packet).
• Code: 8b/10b
• Output voltage: 800 mV +/- 10%
• Deterministic Jitter: 10%
• Random Jitter: 8%
• Rise/fall time (20-80%): 1.2 ns
TERM RS232 serial link over RJ45 for fine-tuning and maintenance purposes.
RJ45 for • RJ45 pinout on NetProcessor 9010:
serial link
8 1
• RJ45-SubD9 female cable wiring:
The connector provides 2 LEDs. These LEDs are lit to indicate the end of
the product boot phase.

CMD 1 Ethernet link for device supervision.

100Base-T Features:
• Standard: IEEE 802.3-2002
• Bitrate: 10/100 Mb/s with autosensing,
• Operating mode: Half duplex/Full duplex with autonegotiation,
• Code: Manchester encoding,
• Connector type: RJ45
• Pinout:
8 1
Pin 1: TDP (Transmitted Data +)

Pin 2: TDN (Transmitted Data -)
Pin 3: RDP (Received Data +)
Pin 4: Not connected
Pin 6: RDN (Received Data -)
• Input impedance: 110 ohms
• Auto-crossover mechanism (Auto MDI/MDI-X) for cable connection.
• Cabling: two twisted pairs, category STP5 or FTP5,
• EMC and Security: according to IEEE 802.3-2002,
• Permissible output jitter: according to IEEE 802.3-2002,
• Input jitter tolerance: according to IEEE 802.3-2002,
• LEDs: Four LEDs indicate operation modes,
ty
i
iv
ct
n
A
sio
d/
lli
ee
Co
Sp
Full
8 1 100
Left LED above the connector (Collision)

Yellow fixed: collision
Off = no collision
Right LED above the connector (Speed/Activity)
Green fixed: link
Green flashing: activity
Off: no link, no activity
Top LED on the right hand side of the connector (Full)
Green fixed = Full Duplex
Off = Half Duplex
Bottom LED on the right hand side of the connector (100)
Green fixed = 100Mbps
Off = 10Mbps

EXT 1 Ethernet link for data service. The Data service feature consists of
Gigabit Ethernet bridging between Ext_1 port (configured as a 10/100/1000
Ethernet Ethernet port) and one ATM PVC. Only EXT_1 port is used.
ports Features:
• Standard: IEEE 802.3-2002
• Bitrate: 10/100/1000 Mbit/s with autosensing.
• Operating mode: Half duplex/Full duplex with autonegotiation.
• Code: Manchester / dibit-PAM (Gigabit Ethernet).
• Connector type: RJ45.
• Auto-crossover mechanism (Auto MDI/MDI-X) for cable connection.
• Input impedance: 110 ohms.
• Cabling requirement: Cat5E cable.
• EMC and Security: Acc. To IEEE 802.3-2002
• Permissible output Jitter: Acc. To IEEE 802.3-2002
• Input Jitter tolerance: Acc. To IEEE 802.3-2002
WAN/LAN Two Gigabit Ethernet ports for transmission over IP networks.
Gigabit Features:
Ethernet • Standard: IEEE 802.3-2002
ports • Number: 2
• Bitrate: 10/100/1000 Mbit/s with autosensing.
• Operating mode: Half duplex/Full duplex with autonegotiation.
• Code: Manchester / dibit-PAM (Gigabit Ethernet).
• Connector type: RJ45 and SFP (Small Form-Factor Pluggable, for
1000 Mbit/s only).
• Auto-crossover mechanism (Auto MDI/MDI-X) for cable connection
on RJ45 connector.
• Input impedance: 110 ohms.
• Cabling requirement: Cat5E cable for RJ45, mono or multi-mode fiber
for SFP.
• EMC and Security: Acc. To IEEE 802.3-2002
• Permissible output Jitter: Acc. To IEEE 802.3-2002
• Input Jitter tolerance: Acc. To IEEE 802.3-2002

RJ45 and SFP connector usage are mutually exclusive.

SFP Module characteristics:
Single Mode
• Type of interface: Single mode 1300 nm optical.
• Standard: IEEE 802.3z 1000Base-LX.
• Connector: LC-Duplex.
• Typical cable length: Up to 10000 m with 9 um single mode fiber.
• Up to 550m with 50/125 or 62.5/125 multimode fiber.
• Output Power: -9.5 dBm to -3 dBm
• Input Power: -20 dBm to -3 dBm
• Stressed receiver sensitivity: -14.4 dBm
• Regulatory compliance:
- UL,
- Eye safety:
- US FDA CDRH AEL Class 1, CDRH certified,
- EN(IEC)60825-1,2, EN60950 TUV certified Class 1.
Multi Mode
• Type of interface: Multi mode 850 nm optical.
• Standard: IEEE 802.3z 1000Base-SX
• Typical cable length: Up to 275m with 62.5/125 type.
• Up to 550 m with 50/125 type.
• Output Power: -9.5 dBm to 0 dBm
• Input Power: -17dBm to 0 dBm (standard 1 dBm penalty is accounted
for on shipping).
• Regulatory compliance:
- UL,
- Eye safety:
- US FDA CDRH AEL Class 1, CDRH certified,
- EN(IEC)60825-1,2, EN60950 TUV certified Class 1.

ATM ports The ATM network interface is used for transmission (Tx/Rx) over the
Telecom network. The ATM network interface can be a SDH/Sonet
board or a PDH board. Each board hosts two ATM ports. No mix of PDH
and SDH is possible for the 2 ports.
ATM SDH/Sonet Features:
SDH/Sonet • Standard: Small Form-Factor Pluggable (SFP) Multi-Source
board Agreement (MSA),
• Number: 2, independent.
• Bitrate: 155.520 Mbit/s + 20ppm.
• Framing: STM1 VC4 mapping or STS3c.
• Connector type: SFP.
• Cabling requirement: Performance and reliability are guaranteed only
when using Thomson SFP modules.
• Permissible output jitter: complies with ITU-T G825 "The control of
jitter and wander within digital networks which are based on the
synchronous digital hierarchy (SDH)". This device shall not be used as a
reference clock (neither primary nor slave).
• Input jitter tolerance: complies with ITU-T G824 "The control of jitter
and wander within digital networks which are based on the 1544 kbit/s
hierarchy".
SFP Module Features:
Electrical N900SSF3AA
• Code: CMI.
• Type of interface: electrical interface.
• Standard: ITU-T G703 "Physical/electrical characteristics of
hierarchical digital interfaces".
• Connectors: 75 ohm female BNC.
Electrical SFP module is provided with two BNC adaptation cables. The
BNC connectors should be mounted on a panel.
Optical, Short haul N900SSF1AA
• Type of interface: Monomode 1330 nm optical Short haul.
• Standard: S1.1 ITU-T G957 "Optical interfaces for equipment and
systems relating to the synchronous digital hierarchy".
• Output Power: -15 dBm to -8 dBm.
• Input Power: -28 dBm to -8 dBm (standard 1 dBm penalty is accounted
for on shipping).
• Security: Optical security standard EN650825 is complied with (class
1 laser).
• Code: NRZ.

Optical, Long haul N900SSF2AA

• Type of interface: Monomode 1330 nm optical Long haul.
• Standard: L1.1 ITU-T G957 "Optical interfaces for equipment and
systems relating to the synchronous digital hierarchy".
• Input Power: -34 dBm to -10 dBm (standard 1dBm penalty is
accounted for on shipping).
1 laser).
• Code: NRZ.
Optical, Multimode N900SSF0AA

• Type of interface: Multimode 1330 nm optical.
• Optical fiber: 62.5/125/0.275
• Input Power: -29 dBm to -14 dBm (standard 1dBm penalty is
accounted for on shipping).
1 laser).
• Code: NRZ.
ATM PDH PDH Features:
board • Standard: ITU-T J131 / ETS 300814 DVB interfaces to PDH networks
ITU-T G703 PDH interface.
• Rate: 34.368 Mbit/s + 20ppm (E3) or 44.736 Mbit/s + 20ppm (DS3).
• Rate selection: software configurable on each port independently.
• Connectors: 75 ohms female BNC.
• E3 line encoding: HDB3 electrical interface ITU-T G703.
• E3 Jitter generation and tolerance: ITU-T G823. The device cannot be
used as primary or slave clock reference.
• DS3 Framing: ITU-T G804 with HEC based mapping (G832 frame).
• DS3 line encoding: B3ZS electrical interface ITU-T G703 and ANSI
T1.107.
• DS3 Jitter generation and tolerance: ITU-T G824. The device cannot
be used as primary or slave clock reference.
• DS3 Framing: ITU-T G804 either with HEC based or PLCP mapping
(C-bit parity frame style).

1.4.3 - NetProcessor 9010’s functional architecture
NetProcessor 9010’s functional architecture is shown below.
Figure 1.7: NetProcessor 9010’s functional architecture

NetProcessor 9010’s processing can also be represented as follows:
Figure 1.8: NetProcessor 9010’s processing representation

1.4.4 - ASI network interface
Figure 1.9: ASI block diagram

1.4.4.1 - MPEG over ASI adaptation layer

NetProcessor 9010 features ten DVB-ASI standard TS coaxial ports in compliance
with CENELEC EN 50083-9 (DVB - PI). These ports can be programmed
individually as inputs or outputs via the CLI interface (sasiin command). When a
port is programmed as an output, the orange LED located near the connector lights
up. All output ports are grouped on the right hand side of the strip.
Figure 1.10: ASI interface
¤ ASI input
The size of the incident packets contained in the TS flows is 188 or 188+16 bytes in
data burst or packet mode. NetProcessor 9010 automatically recognizes the size of
incident packets. 204 byte packets including 16 additional bytes of Reed-Solomon
code or auxiliary data are processed as 188 + 16 format. The RS bytes are discarded
and the Reed-Solomon code is ignored.
As NetProcessor 9010 is designed for pass-through bit-accurate transmission, null
packets are not discarded, packet order is maintained, PCR are left unchanged.
NetProcessor 9010 supports the following ETR 290 Monitoring features:
TS_sync_loss, Sync_byte_error.
A configurable rate limitation is applied to any ASI input. This limiter can cope
with burst. Maximum burst size is 30 TS packets at maximum rate. Any packet
received above the limits is discarded.
¤ ASI output
The packets feature 188 or 188 + 16 bytes. In the second case, 16 additional bytes
of random value are included for the Reed-Solomon error-correcting code inserted
by the modulators.
The physical output interface is of ASI type in compliance with CENELEC EN
50083-9 (DVB - PI) and uses Data packet mode (packet per packet).

1.4.4.2 - MPEG over ASI rate capacity

ASI adaptation can cope with a total MPEG TS rate of 345748 TS packets per
second, i.e. 520 Mbps for 188-byte format or 564 Mbps for (188+16)byte format
simultaneously each way.
Maximum individual TS Rate is 213 Mbps either in 188-byte format or
(188+16)byte format.
The minimum MPEG rate is 60 TS packets per second, i.e. 91 kb/s for 188-byte
format or 98 kb/s for (188 + 16) byte format.
1.4.4.3 - Latency
Delay from ASI In to ASI Out is 20ms.
Figure 1.11: ASI-ASI latency

1.4.5 - ATM network adaptation
Figure 1.12: ATM network adaptation block diagram

1.4.5.1 - MPEG over ATM Adaptation layer

MPEG over ATM adaptation uses AAL1 (ATM Adaptation Layer type 1) as
required by DVB and ITU-T. Adaptation is compliant with ETS300813/814 and
ITU-T J131/132.
MPEG over ATM adaptation provides:
• simultaneous emission of up to 4 MPEG streams and reception of up to 4 MPEG
streams with the N901PDH0GA E3/DS3 interface board.
• simultaneous emission of up to N MPEG streams and reception of up to (10-N)
MPEG streams with the N901STMFGA interface board.
The total number of transmitted and received MPEG streams may also be limited by
the number of N901SATMAA licenses installed in the device (see section
“Ordering guide”, page 9).
AAL1 allows TS CBR constant bit rate transportation (with possible CBR or VBR
embedded video streams).
FEC included in the AAL1 standard delivers high performance over real wide area
network infrastructures.
FEC can be disabled to slightly improve bandwidth efficiency at the cost of
potential artifacts even on good quality networks.
The AAL adaptation layers are split into two sublayers: the CS sublayer
(Convergence sublayer) and the SAR sublayer (Segmentation and Reassembly
sublayer).
1.4.5.1.1 - Transmission
¤ Transmission CS sublayer
• 4 bytes of Reed Solomon Forward Error Correction are inserted every incoming
124 bytes. Reed Solomon code RS(128,124) complies with the ITU-T I.363.1
specification.
• Bytes are interleaved using a 128*47 matrix.
• The first byte of the interleaving matrix is the first byte of an MPEG-TS packet
to comply with ITU-T J131/132.
• The CS sublayer process can be bypassed by deactivating the FEC process.

¤ Transmission SAR sublayer

• A sequence numbering byte is inserted in interlaced 47-byte blocks to form 48-
byte ATM cell payloads.
• The ATM layer adds its 5-byte header to the 48-byte payloads. It includes virtual
channel identification (VPI and VCI). Adaptation to the SAR also includes input
port selection. Any channel can be freely set to use either port1 or port 2.
1.4.5.1.2 - Reception
¤ Reception SAR sublayer

• 48-byte ATM cell payloads are received from the ATM layer. They are selected
from their virtual channel identification (VPI and VCI) and input port selection.
Any channel can be freely set to use either port1 or port 2.
• Sequence numbering is corrected.
¤ Reception CS sublayer
• Sequence numbering is analyzed to check for cell misinsertion and lost cells. The
algorithm used enables detection of isolated misinserted cells and loss bursts up
to 6 consecutive lost cells.
• Misinserted cells are discarded, dummy cells (all filled) are created to replace
lost cells.
• If the FEC process is set, the resulting 47-byte payloads are deinterleaved; The
128-byte Reed-Solomon word is corrected if possible. Correction is possible
until L+2E=4, where L stands for lost bytes, and E for errored bytes. Loss
correction capacity is up to 4 cells every 128 cells, and up to 2 errored cells every
128 cells. The result of error correction is 124-byte corrected words.
• Independently of the FEC process, MPEG TS packet delineation is performed on
retrieved data and jitter is filtered on TS flow.
• Network jitter smoothing is performed using adaptive clock recovery (phase
locked loop). The PLL can cope with large amounts of network jitter (CDV: Cell
Delay Variation):
- PLL will lock with up to 3ms CDV,
- PLL will not unlock with up to 4ms CDV.
CDV must be nominally kept below 1ms to ensure optimum recovered
MPEG-TS timing accuracy. In this condition, PLL accuracy is better than
0.1ppm. Full accuracy is reached after a 20min. stabilization period. If CDV
increases, PLL accuracy will degrade linearly.

Lock time varies with conditions:

- On startup and when the TS rate changes, lock time is 25s,
- For an unchanged TS rate and a signal cut longer than 1s, lock time is 3s,
- For an unchanged TS rate and a signal cut shorter than 1s, lock time is 0.5s.
1.4.5.2 - Network interface features
1.4.5.2.1 - Multiplexing (ATM layer)
The ATM multiplexing unit manages asynchronous multiplexing/demultiplexing of

services in a stream of useful ATM cells. The services come from or are delivered
by the various ASI interfaces, Gigabit Ethernet interfaces and, in the case of
NetProcessor 9010 cascading, by ATM interfaces.
In the current release, the ATM multiplexing unit does not provide any port to port
switching capability.

Figure 1.13: ATM multiplexing

MPEG TS VCCI can be transmitted on any of the two ports. Simultaneous

transmission of one MPEG TS over the two ports can be performed by using two
VCCI / adaptation layer.
MPEG Transmit MPEG Receive

any VP any VP
VCI> 31 VCI> 31
ATM cells are 53-byte fixed length cells and include 48 useful data bytes supplied
by the AAL layer and five header bytes supplied by the ATM layer. These five bytes
carry the following information: GFC (Generic Flow Control), VPI (Virtual Path
Identifier), VCI (Virtual Channel Identifier), PT (Payload Type), CLP (Cell Loss
Priority), HEC (Header Error Control).
¤ Asynchronous multiplexing
In the multiplexing direction,
• the GFC and CLP fields take the value 1;
• the VPI/VCI pair is unique to each ASI interface (possible values: 0< VPI<255
and 31<VCI<65536). The In-Band management flows use VCI in the range 32 to
63;
• the HEC field is generated by the PL-TC sublayer and provides both header bit
error correction and protection and cell delineation.
¤ Asynchronous demultiplexing
In the demultiplexing direction, the ATM cells are demultiplexed on the basis of
VPI and VCI field filtering. The GFC, PTI and CLP fields are ignored.

1.4.5.2.2 - Data links
¤ In-Band Management links

A management channel using Classical IP over ATM protocol offers connectivity to
a management center with 2 ATM VCC (one per port). These links are also usable
externally via CMD1 and/or CMD2 Fast Ethernet ports, provided that adequate
routes are configured.
Classical IP over ATM is a layer 3 (IP forwarding) technology. It will not forward
layer 2 protocols (e.g. DHCP). It will not forward any broadcast datagram.
Multicast traffic is discarded.
Connectivity is obtained via explicit static routes towards IP subnets. Up to 4 static
routes are stored in the configuration.
Figure 1.14: In-Band management (with oneVCC here)

ATM Layer
Connection management NetProcessor 9010 can be reached by 2 PVC CIPa ATM
connections with VCI from 32 to 63.
Traffic profile NetProcessor 9010 handles traffic shaping on
transmission on ATM connections dedicated to In-Band
management.
The Traffic profile is UBR. If you need to minimize
frame drops, set traffic shaping lower than the available
bandwidth on the PDH or SDH port.
The maximum data rate is configurable. It is advisable
to set the data rate in the range of 0.1 to 2 Mbit/s.
Nevertheless, the data rate can be set up to 20 Mbit/s but
high data rate on this service can noticeably slow down
product configuration time.
IP Layer
Encapsulation IP encapsulation over ATM complies with [RFC-1483].
IP over ATM IP over ATM protocol complies with [RFC-1577]
routing.
a.Classical IP over ATM (RFC-1483, RFC-1577, RFC-1626, RFC-2331)
ClassicalIPoATM based In-Band management must not be used

simultaneously with the ATM data service.

¤ ATM Data service

Overview
The ATM Data service creates a bridged tunnel between two NetProcessor 9010 by
interconnecting traffic over AAL type 5 over ATM. It uses RFC2684 §5.2 Payload
Format for Bridged Ethernet/802.3 PDUs.
- LAN FCS (Frame Check Sequence) is not carried.
- PID is 0x00-07 (which is the media type value used in ATM encapsulation
for Ethernet/802.3 without preserved FCS).
The Data service feature consists of Ethernet bridging between Extension 1 port
(configured as a 10/100/1000 Ethernet port) and one ATM PVC (possible values:
0 ≤ VPI ≤ 255 and 32 ≤ VCI ≤ 63). It means it will connect Ethernet devices within
the same IP subnet.
It supports any Ethernet traffic except multicast.
An application note gives measured typical ATM data service performance of
NetProcessor at TCP level. Please contact Thomson Customer Services for a copy.
ATM data service must not be used simultaneously with

ClassicalIPoATM based In-Band management.

Use cases
Case 1: controlling a remote NetProcessor 9010
Figure 1.15: ATM remote NetProcessor 9010
Comments: Extension 1 port must be externally connected to CMD1 (or CMD2)

port on the remote NetProcessor 9010.

Case 2: controlling a remote NetProcessor 9010 and other devices
Figure 1.16: ATM remote system
Comments: on the remote NetProcessor 9010, Extension 1 port must be externally

connected to CMD1 (or CMD2) port. If no other device has to be connected, plug
an Ethernet cable between these two ports, otherwise connect both ports to the
Ethernet switch.

Case 3: interconnecting third party devices
Figure 1.17: ATM pure data service
Comments: remote NetProcessor 9010 is controlled via an out-of-band link.

1.4.5.2.3 - Physical layer
The PL (Physical Layer) is split into two sublayers:

• the TC (Transmission Convergence) sublayer performs all functions
required to convert a flow of cells into a flow of bits which is then trans-
mitted and received on a physical medium;
• the PMD (Physical Medium Dependent) sublayer includes only physical
medium dependent functions.
¤ TC sublayer
At the Transmission end, the TC (Transmission Convergence) sublayer performs
the following operations:
• computing of the error corrector code (HEC);
• scrambling;
• cell rate decoupling;
• framing (SDH STM-1, STS3c SONET, PDH G704) with generation of
ATM standard mapping in a unique VC4;
• alarm generation and transmission:
- generation of OAM F1, F2 and F3 flows according to SONET, SDH or
PDH mode,
- generation of B1, B2, B3 parities,
- generation of FERF, FEBE, path FERF, path FEBE.
At the Reception end, the TC (receiver) sublayer performs the following tasks:
• transmission frame recovery;
• cell delineation;
• descrambling;
• HEC header checking;
• processing of OAM F1, F2 and F3 flows according to SDH or PDH mode;
• verification of B2, B3 parities.
• detection of LOS, LOF, AIS, LOP, RDI, REI, path AIS, path RDI, path REI
and LCD. This detection can be globally inhibited for each port.
Overhead termination does not include any Data Communication Channel (DCC)
handling or network synchronization features.
¤ PMD sublayer
The PMD sublayer includes the following functions:
• generation/recovery of bit timing;

• coding/decoding.
Various hardware configurations are available for the two network interfaces.
SDH/SONET network interface
Various SFP types are supported:
• 155.52 Mbit/s electrical network interface;
• 155.52 Mbit/s single-mode short-haul optical network interface (S1.1 class
compliant with ITU-T G957 "Optical interfaces for equipment and systems
relating to the synchronous digital hierarchy");
• 155.52 Mbit/s single-mode long-haul optical network interface (L1.1 class
compliant with ITU-T G957 "Optical interfaces for equipment and systems
relating to the synchronous digital hierarchy");
• 155.52 Mbit/s multi-mode optical network interface.
The SDH-STM1 / Sonet-OC3 ATM network interface board (N901STM1FGA)
provides 2 bidirectional ports. The first network interface is enabled by default, the
second network interface is subject to activation of a software license
(N901SAEPAA).
The maximum number of ATM streams supported for MPEG is 10, mix of Rx and
Tx.
The network interfaces are used independently and the two ports can be equipped
with different SFP variants.
The two 155.52 Mbit/s ATM ports can be set by software either in STM1 (ITU-T)
or STS3c (SONET) framing mode.
PDH network interface
PDH interface is software configurable on each port independently: E3 (34.368
Mbit/s + 20ppm) or DS3 (44.736 Mbit/s + 20ppm).
Use of the second network interface is subject to activation of a software license.
The maximum number of ATM streams supported for MPEG is 4 Rx and 4 Tx.
For E3, PDH supported framing is ATM direct mapping in a G832 frame as per
ITU-T G804. The line encoding is HDB3 electrical interface ITU-T G703. E3 Jitter
generation and tolerance is compliant with ITU-T G823. The device cannot be used
as a primary or slave clock reference.
For DS3, PDH supported framing is ATM direct mapping or PLCP in a C-parity
frame as per ITU-T G804. The line encoding is B3ZS electrical interface ITU-T
G703 and ANSI T1.107. DS3 Jitter generation and tolerance is compliant with
ITU-T G824. The device cannot be used as a primary or slave clock reference.

1.4.5.3 - MPEG over ATM rate capacity

ATM adaptation can cope with full SDH or PDH line rate.
Maximum per service TS Rate varies with network interface settings and usage or
not of FEC:
TS packet/s 188 rate (Mb/s) 188+16 rate (Mb/s)
SDH with FEC 85535 128,64 139,59
without 88105 132,51 143,79
E3 with FEC 19195 28,87 31,33
without 19815 29,80 32,34
DS3 with FEC 25070 37,71 40,91
direct without 25880 38,92 42,24
DS3 with FEC 23070 34,70 37,65
plcp without 23815 35,82 38,87
The minimum service MPEG rate to prevent PLL unlocking is 998 TS packets per
second, i.e. 1.5 Mb/s for 188-byte format or 1.7 Mb/s for (188 + 16) byte format.
On transmission, the minimum MPEG rate is 60 TS packets per

second, i.e. 91 kb/s for 188-byte format or 98 kb/s for (188 + 16) byte
format.
The In-Band management ATM rate capacity is 700 cells per second (i.e.
approximately 256kb/s of IP).

1.4.5.4 - Latency
Delay from ASI In to ASI Out via ATM is:
2 × 47 × 124 × 8
DelayASItoASIviaATM = 52ms + ----------------------------------------------------------------
TSrateInKbitPerSecond
Figure 1.18: ASI-ATM-ATM-ASI latency

1.4.6 - IP network adaptation
Figure 1.19: IP network adaptation block diagram

1.4.6.1 - MPEG over IP adaptation layer

MPEG over IP adaptation can use either pure UDP encapsulation or RTP/UDP
adaptation layer.
Adaptation provides simultaneous reception of up to 20 MPEG streams and
transmission of up to 20 MPEG streams.
Adaptation allows TS CBR constant bit rate transportation (with possible CBR or
VBR embedded video streams).
1.4.6.1.1 - Transmission
¤ Transmission adaptation
MPEG packets are grouped into messages. Message size is fixed and can be freely
set to contain from 1 to 7 MPEG TS packets.
RTP header is inserted. It adds mainly
- Sequence numbering that will allow far end loss detection and packet
re-ordering;
- Time stamping.
NetProcessor inserts an accurate timestamp, generated from an internal reference
with a + 5 ppm accuracy.
RTP can be bypassed. Use of RTP is recommended as it enables network induced
error compensation. When using RTP, FEC protection can be added to the
transmitted streams. The FEC scheme complies with SMPTE 2022 (Forward Error
Correction for Real-Time Video/Audio Transport Over IP Networks) and is fully
configurable within the limits permitted by this recommendation.
A UDP header is inserted. It adds a port number that enables channel identification.
FEC messages implicitly use UDP port number +2 (Column FEC) and UDP port
number +4 (Row FEC). You are advised to always use a minimum +6 increment
between consecutive TS UDP ports on the same interface.
¤ FEC
FEC features
The FEC option is available with RTP framing mode. Its implementation complies
with SMPTE 2022 (Forward Error Correction for Real-Time Video/Audio
Transport Over IP Networks).

• FEC is bi-dimensional and uses two IP streams added to the video IP stream.
These two streams are transmitted on two independent UDP ports (n+2 and n+4
where n is the MPEG UDP port number);
• FEC implements matrix encoding (column and row operations) which is used to
recover isolated packet losses and burst packet losses.
• FEC can be enabled or disabled for each MPEGoIP channel. The relevant FEC
options are required.
• FEC parameters are set for each MPEGoIP channel via WEB interface.
FEC principle
To solve bit errors (which lead to packet loss) and packet errors in an IP network,
NetProcessor 9010 uses the following solutions: FEC used in the
NetProcessor 9010 complies with SMPTE 2022 (Forward Error Correction for
Real-Time Video/Audio Transport Over IP Networks) designed for IP network
error characteristics (packet loss and burst loss). FEC packets are calculated by an
XOR boolean operator. Tx FEC parameters can be set to suit network conditions.
Row FEC has a low latency and is designed to recover isolated errors. Column FEC
is adding more latency and is designed to recover burst errors. Column FEC packet
interleaving can be set to adapt the compromise between latency and IP stream
burstiness.
FEC configuration detection is automatic at reception end.

Example: Dual FEC mode structure (L=8, D=6, L'=8) FEC scheme based on
SMPTE 2022 (Forward Error Correction for Real-Time Video/Audio Transport
Over IP Networks).
L columns
L': row FEC protection length
RTP pkt 0 RTP pkt 1 RTP pkt 2 RTP pkt 7 FEC' pkt 0
D rows
XOR operation is applied to the RTP

packets to get the FEC packet.
FEC pkt 0 FEC pkt 1 FEC pkt 2 FEC pkt 7 FEC is calculated on column and
row packets.
Figure 1.20: Dual FEC mode structure (L=8, D=6, L'=8) FEC scheme
The matrix is organized as follows:

• RTP packets = the media packet,
• FEC packets = the column FEC stream which copes with burst packet loss,
• FEC' packets = the row FEC stream which copes with single packet loss within
the length L'.
Dual FEC mode structure (2D FEC) recovers up to L+D-1 packets (a complete
dropped row and a complete dropped column). The FEC algorithm fails if packet
loss combination includes three packets as shown (1 data packet with its 2
associated FEC packets) or describes a rectangle shape in the matrix (e.g.: RTP pkt#
1,3,9,11).

Example of un-recoverable losses:
L columns
D rows
FEC pkt 0 FEC pkt 1 FEC pkt 2 FEC pkt 3
L columns
D rows
FEC pkt 0 FEC pkt 1 FEC pkt 2 FEC pkt 3
Figure 1.21: Example of un-recoverable losses
Example of recoverable losses
FEC' packets
L columns result from XOR
operation on L'=L
packets
RTP pkt 0 RTP pkt 1 RTP pkt 2 RTP pkt 3 RTP pkt 4 RTP pkt 5 RTP pkt 6 RTP pkt 7 FEC' pkt 0
D rows
FEC pkt 0 FEC pkt 1 FEC pkt 2 FEC pkt 3 FEC pkt 4 FEC pkt 5 FEC pkt 6 FEC pkt 7
Lost packet
FEC packets result from XOR operation on D packets
Figure 1.22: Example of recoverable losses

Performances are compliant with SMPTE 2022 limits
Matrix size L*D ≤ 100 packets

Burst protection 1 ≤ L ≤ 20 packets
Number of rows 4 ≤ D ≤ 20 packets
Row FEC capacity 4 ≤ L’≤ 20 packets
Total FEC packets per matrix : ≤ 30 pkts

Output flow
The output flow is a combination of RTP media packets, column FEC and row FEC
packets which are transmitted on different UDP ports:
• Main UDP port for RTP media packet. This parameter is the only UDP port
which can be set via the management system, Column FEC UDP port and Row
FEC UDP port are automatically deduced from that primary port.
• The Column FEC UDP port is equal to the main UDP port + 2. This FEC flow is
interleaved with a depth of D in the next matrix to ensure a higher burst loss
tolerance. When configuring an interleaving of D, FEC latency is equal to 2
matrixes. Interleaving can be modified to reduce latency.
• The Row FEC UDP port is equal to the main UDP port + 4. This FEC flow is
transmitted in the current matrix after the last media packet of the protection set.

Example:
Matrix
representation
L=4 Row FEC'
packets
D=5
Column FEC
packets
Stream
representation
Main Stream
Column FEC' 4:20 FEC, 20% column overhead,

Corrects 4 losses per 20 pkts
packets
Row FEC 1:4 FEC, 25% row overhead,

packets Corrects 1 loss per 4 pkts
Ethernet 0 1 2 3 4, 5 6 7 8, 9 10 11 12, 13 14 15 16, 17 18 19 20, 21 22 23 24, 25,

Frame FEC'0 FEC'1 FEC'2 FEC'3 FEC'4 FEC'5 FEC1
Distribution
FEC0
26 27 28, 29 30, 31 32, 33 34 35, 36, 37 38 39

FEC'6 FEC2 FEC'7 FEC3 FEC'8
Figure 1.23: Output flow
¤ IP transmission settings
Configuration offers fine tuning at IP level per IP channel.
NetProcessor 9010 provides either unicast or multicast transmission mode.
NetProcessor 9010 allows forcing a source IP address instead of inheriting the
native IP address of the chosen interface. This mode is provided for specific
redundancy schemes. This must be used only in that case as it can otherwise cause
major network administration issues.
NetProcessor 9010 provides TimeToLive setting.
NetProcessor 9010 provides TOS byte setting, either manually or using DiffServ
values.
¤ QOS tagging support
NetProcessor 9010 provides IEEE 802.1P QOS tagging per channel.

1.4.6.1.2 - Reception
¤ Unicast
In Unicast mode, NetProcessor 9010 will automatically use the selected native port
address for IP stream reception.
¤ Multicast
In Multicast mode, NetProcessor 9010 will automatically manage IGMP join and
leave for seamless operation in real scale IP networks.
The Operator chooses which type of IGMP protocol should be used by
NetProcessor 9010:
• IGMPv2,
• IGMPv3 partial with no source control.
• IGMPv3 with SSM (Source Specific Multicast which is an IP technology where
the destination host can select a source when joining a multicast group).
Interoperability features:
• The SSM service is not commonly supported by routers and rarely
by Ethernet switches.
• The Operator must specifically check the behavior of Ethernet
switches. Usual IGMP snooping may not work at all when using
SSM.
Setting the proper IGMP version is recommended as it speeds up NetProcessor start

time. If detected network capabilities are below the level set by the Operator (e.g.:
the network is using IGMPv2 while IGMPv3 is selected), NetProcessor
automatically reverts to a network supported version of IGMP.
When IGMPv3 with SSM protocol is chosen, the Operator must set (or not) a
source IP address whether the multicast group address matches the SSM range or
not. NetProcessor 9010 does not require the SSM range to match the default IANA
value (232.0.0.0 through 232.255.255.255 for SSM applications).
When IGMPv2 protocol is chosen, only the basic multicast service runs. Then, the
source IP address can be set but has a different meaning. When set, the
NetProcessor 9010 will activate a filter to reject frames coming from unexpected
sources, while IGMP join/leave are of any source type.

¤ Decapsulation scheme
NetProcessor 9010 supports MPEG/UDP/IP and MPEG/RTP/UDP/IP
decapsulation schemes according to the Operator choice. Otherwise, receiver
automatically adapts to received frame length.
¤ Reordering
The Reordering tolerance default setting is ten RTP frames, but it can be adjusted
when FEC error correction is disabled, within the range of 0 to 128. Reordering
cannot be performed on pure UDP streams. When FEC error correction is activated,
the reordering process is able to recover any ordering within a window of one FEC
matrix plus 10 frames.
When the IP Rx threshold alarm feature is enabled, RTP reordering

will be set to the threshold or configured reordering value, whichever
is the highest.
¤ FEC
FEC error correction can be enabled or disabled through the management system. If
enabled, FEC configuration detection is automatic at reception end for each
received MPEG over IP channel.
¤ Jitter absorption
Efficient network jitter absorption is provided on each received stream whatever the
used protocol. Dejittering requires stable MPEG-2 TS rate with a long term
accuracy within + 30 ppm. Residual drift will cope with the most stringent PAL or
NTSC timing requirements provided the source stream is compatible, for incoming
jitter (IPDV) up to 60ms. The Operator can modify the maximum accepted IPDV
up to 200ms to cope with medium grade network characteristics.
¤ TS rate recovery
MPEG-2 TS rate recovery locks in less than 2s. As the TS rate recovery mechanism
uses PCR present in the TS, some streams that do not include any PCR, e.g. some
pure DVB-H streams will not be recovered. That is why a Fixed rate mode has been
implemented. In Fixed rate mode, received TS is expected to be within + 30 ppm of
the nominal rate entered by the Operator.

1.4.6.2 - Network Interface
1.4.6.2.1 - IP routing
NetProcessor 9010 provides either static or dynamic (RIP or OSPF) routing

features. It will output a stream if and only if routing is resolved, and MAC address
resolution is successful.
Up to 4 static routes can be entered per Gigabit Ethernet WAN port.
Output port setting has a higher priority than IP next hop determination. It means a
stream will be sent only if a next hop IP destination is found that is reachable on the
specified Ethernet port.
1.4.6.2.2 - In-Band management
Although MPEG over IP is processed by a dedicated high speed coprocessor,

NetProcessor 9010 behaves like a real IP host on each of its IP Gigabit Ethernet
WAN ports. Non MPEG protocols can be accessed via these interfaces. There is no
firewall to bar access to the NetProcessor 9010 host from its Gigabit Ethernet ports.
1.4.6.2.3 - MAC Layer and VLAN support
In addition to standard MAC address resolution via ARP protocol, the destination
MAC address can be manually set.
The VLAN Tag is normally padded on ingress traffic by switches, and stripped on
egress traffic. This is done on a per port basis, or even on more complex criteria.
VLAN Tagging can also be used to add some redundancy switching capacity to
multicast traffic. To facilitate such system cases, NetProcessor 9010 can tag
transmitted MPEG streams independently for each channel.
NetProcessor 9010 transparently accepts tagged or untagged frames on received
MPEG streams. VLAN is not used for traffic filtering, thus two streams on different
VLAN must not use the same UDP port/IP address settings.

Tagged or untagged frames

on transmitted MPEG streams
Tagged or untagged frames

on received MPEG streams
VLAN is not supported

for non MPEG over IP traffic
Figure 1.24: VLAN management.
1.4.6.2.4 - Gigabit Ethernet ports
Both ports are combo 10/100/1000Base-T, 1000Base-X (SFP) ports. Selection

between copper and optical interfaces is automatic with a priority for copper. If an
optional SFP module is plugged in, this link will be activated only if the copper link
is down (e.g. not connected).
Ports provide auto-negotiation but can be forced in 1000 Mbps, 100 Mbps Full
Duplex, 100 Mbps Half Duplex or 10 Mbps Half Duplex.
Note that the performances indicated in this manual are based on the assumption
that 1000 Mbps is used.
Ports provide auto-crossover mechanism (auto MDI/MDI-X).
Additionally, each port offers a global shaping setting. Global Ethernet traffic can
be limited to a specified rate ranging from 1 Mbps to 1000 Mbps in 1 Mbps steps.

1.4.6.3 - MPEG over IP rate capacity

IP adaptation can cope with a total MPEG TS rate of 465425 TS packets per
second, i.e. 700 Mbps for 188-byte format or 760 Mbps for (188+16)byte format
simultaneously each way.
Maximum per service TS Rate can reach full capacity: 465425 TS packets per
second, i.e. 700 Mbps for 188-byte format or 760 Mbps for (188+16)byte format.
second, i.e. 1.5 Mb/s for 188-byte format or 1.7 Mb/s for (188 + 16)byte format.

second, i.e. 91 kb/s for 188-byte format or 98 kb/s for (188 + 16)byte
format.
1.4.6.4 - MPEG over IP overheads
1.4.6.4.1 - Stacks and overheads
Figure 1.25: Stacks and overheads

¤ Payload
Payload size is n TS packets, size is thus n*188 bytes.
FEC Payload size is identical.
FEC frames are longer supported because they use an RTP header ex-
tension.
¤ TCP/IP
RTP header size is 12 bytes for main data or 12+16=28 bytes for FEC.
UDP header size is 8 bytes.
IP header size is 20 bytes.
¤ Ethernet
MAC header size is 14 bytes.
MAC trailer size is 4 bytes.
MAC preamble size is 8 bytes.
Ethernet inter-frame guard time duration is equal to 12 bytes.
Integrating guard time in overhead calculation is the only way to be

consistent with the "easy to remember" 1 Gb/s Ethernet line capacity.
¤ FEC
Line FEC is 1 FEC every L' MPEG, thus adding a 1/L' frames overhead.
Column FEC is L FEC every L*D MPEG, thus adding a 1/D frames overhead.

1.4.6.4.2 - Calculating used bandwidth
¤ Ethernet rate versus MPEG TS rate

Case 1: UDP
Overhead is 8+20+14+4+8+12=66
TotalEthernetRate = [66/(n*188) +1]* MpegTsRate
Case 2: RTP/UDP
Overhead is 12+8+20+14+4+8+12=78
FEC Overhead is 28+8+20+14+4+8+12=94
MpegEthernetRate = [78/(n*188) +1]* MpegTsRate
LineFecEthernetRate = [94/(n*188) +1]*[1/L']* MpegTsRate
ColumnFecEthernetRate = [94/(n*188) +1]*[1/D]* MpegTsRate
TotalEthernetRate = MpegEthernetRate + (L'>0)*LineFecEthernetRate +
(D>0)*ColumnFecEthernetRate
¤ IP rate versus MPEG TS rate
Case 1: UDP
Overhead is 8+20=28
TotalIpRate = [28/(n*188) +1]* MpegTsRate
Case 2: RTP/UDP
Overhead is 12+8+20=40
FEC Overhead is 28+8+20=56
MpegIpRate = [40/(n*188) +1]* MpegTsRate
LineFecIpRate = [56/(n*188) +1]*[1/L']* MpegTsRate
ColumnFecIpRate = [56/(n*188) +1]*[1/D]* MpegTsRate
TotalIpRate = MpegIpRate + (L'>0)*LineFecIpRate + (D>0)*ColumnFecIpRate

1.4.6.5 - Latency
Sources of latency are:
• FEC calculation delay in transmitter,
• Reordering,
• FEC packet loss recovery,
• Jitter absorption delay.
¤ End to end delay introduced by FEC processing
The end to end delay introduced by FEC processing (including re-ordering) varies
with TS rate. When frame size is set to n packets/frame, the time delay (expressed
in milliseconds) is:
( 32 + 2LD ) × n × 188 × 8
EndtoEndDelayForFEC = ----------------------------------------------------------------------
( TSRateInKbitPerSecond )
¤ Delay introduced by re-ordering
The equivalent delay when not using FEC processing includes only re-ordering:
R frames (where R is the reordering set by the Operator). When frame size is set to
n packets/frame, this gives a time delay (expressed in milliseconds) of:
R × n × 188 × 8
DelayForReordering = ----------------------------------------------------------------------
( TSRateInKbitPerSecond )
¤ Delay introduced by jitter absorption

The delay introduced by jitter absorption does not change with TS rate. It is
(expressed in milliseconds):
8 × IPDVInMilliseconds
DelayForJitterAbsorption = ---------------------------------------------------------------- + 29.6milli sec onds
7
¤ Total end to end delay

The total end to end delay is equal to
• EndtoEndDelayForFEC + DelayForJitterAbsorption when FEC processing is
enabled.
• DelayForReordering + DelayForJitterAbsorption when FEC processing is
disabled.

¤ 1st Example: End to End Delay with FEC processing Tx + Rx

where
- Number of packets per IP Packet is n = 7
- Number of rows in the FEC matrix is D = 10
- Number of columns in the FEC matrix is L = 10
- Transport Stream Bitrate is TSRateInKbitPerSecond = 40 000 kbps
- IP absorption buffer is IPDVInMilliseconds = 20 ms
- Reordering buffer size is R = 10 IP frames
( 32 + 2 ( 10 × 10 ) ) × 7 × 188 × 8
EndtoEndDelayForFEC = ------------------------------------------------------------------------------ = 61milli sec onds
40000
8 × 20
DelayForJitterAbsorption = --------------- + 29.6 = 52milli sec onds
7
The total End to End delay is equal to 61 ms + 52 ms = 113 ms

¤ 2nd Example: End to End Delay without FEC processing
where
- Number of packets per IP Packet is n = 7
- Transport Stream Bitrate is TSRateInKbitPerSecond = 40 000 kbps
- IP absorption buffer is IPDVInMilliseconds = 20 ms
- Reordering buffer size is R = 10 IP frames
10 × 7 × 188 × 8
DelayForReordering = --------------------------------------- = 3milli sec onds
40000
8 × 20
DelayForJitterAbsorption = --------------- + 29.6 = 52milli sec onds
7
The total End to End delay is equal to 3 ms + 52 ms = 55 ms

1.4.7 - TS Routing
NetProcessor 9010 can route any input stream (from ASI or ATM or Gigabit
Ethernet input) to any output (to ASI or ATM or Gigabit Ethernet outputs).
Any input stream can be routed to up to 4 outputs (ASI, ATM or Gigabit Ethernet
input).
Total routing capacity is 700 Mbps (including TS packet replication). Throughput is
generally limited by network interface capabilities.
The following diagram illustrates some typical TS routing examples:
¤ ASI Interfaces
Monitoring a transmitted stream
or
Multiple outputs of a received stream
or
Figure 1.26: Some typical TS routing examples with ASI interfaces
¤ ATM or Gigabit Ethernet interfaces
Transmit a stream over two network interfaces
port1
or
port2
or
Bridge between two networks
port1 port2
or or
Figure 1.27: Some typical TS routing examples with ATM and Gigabit Ethernet interfaces

¤ Performance with redundancy

Protected switch inputs are fully decoded to enable accurate alarm evaluation. They
must be counted in total processed rate. Thus, if performing n*(1+1) IP reception,
the total maximum rate is 700 Mb/s and forwarded traffic is 350Mb/s maximum.
1.4.8 - Input Transport Stream redundancy
¤ Overview
Input Transport Stream redundancy is an option (N901SSTRAA).
This feature adds 2>1 switches to any pair of TSs coming from the same media or
another one (e.g. IP and IP, IP and ATM).
by the Operator).
Figure 1.28: Input Transport Stream redundancy (here in manual mode)
Figure 1.29: Input Transport Stream redundancy (here in automatic mode)
In automatic mode, a switch to a new input will only occur when the new input has
been free of alarms for almost the holdover period of time.

Redundancy holdover is set to infinite for non-revertive automatic mode and can
be adjusted to 10, 30 or 60 seconds for revertive automatic mode.
Figure 1.30: Redundancy holdover setup
¤ Redundancy principle
A switch engine is inserted between TS inputs and the routing core.
Streams are first secured by a 2>1 switch then dispatched. Thus, replication of a
protected stream is possible:
Figure 1.31: Redundancy principle
But the replication of an input is not possible.

Figure 1.32: Replication of an input is not possible
NetProcessor accepts any mix of direct connections and switched connections. Any
input (ASI, ATM or IP) can be used in a 1+1 redundancy switch.
¤ Switching criteria
When the mode is set to manual, the Operator configures which input stream is the
passing one.
When the mode is set to automatic, an automat is launched that analyzes the alarms
raised by both inputs. If the nominal input is out-of-order, and the other one is
running, the source is switched to the other one.
The switch can occur once (non-revertive) or at any time (revertive), whether
automat holdover is set to infinite or any finite value. When in revertive mode, the
automat goes back to nominal as soon as possible.
¤ Automat adjustment
Automats can be set to infinite holdover. Then switching can occur only once.
Automats can be set to finite holdover. The holdover prevents unwanted switch
oscillations. It can be set to 10, 30 or 60 seconds. A switch to a new input will only
occur when the new input has been free of alarms for almost the holdover period of
time.
Holdover setting is global for all automats.
¤ Redundancy rules
When an automat is in automatic mode, the Operator cannot force the toggle. The
mode must be set to Manual.
When changing to manual mode, the switch position remains unchanged and the
connection can be edited to select which input goes through.

The automat considers the input selected for pass through when started, as nominal.
When redundancy is disabled, connection is established with the nominal input, and
the other input is disconnected.
¤ Redundancy and configuration file application
As soon as redundancy is active, automats take priority over a part of the internal
configuration. This may cause conflict with configuration file application.
Before loading a new configuration file, redundancy must be disabled.
¤ Redundancy and XMS/XMU
As soon as redundancy is active, automats take priority over a part of the internal
configuration. This will cause conflict with XMS/XMU management.
When managed by an XMS, redundancy must be disabled.
¤ Redundancy switching performance
Alarm detection and switch time depends both on configuration size (number of
connections) and alarm toggling rate. Maximum switching time is qualified at
700 ms. The reference case is 10 * (1+1) Rx IP with all active Rx falling down
simultaneously.
The response time can exceed this value if alarms are frenetically raised and cleared
on all inputs. Nevertheless, in such a case, redundancy will not help to maintain the
service.
¤ Alarm triggers
Alarms that can trigger a toggle are listed here. Some triggers are fixed. These are
alarms that always reveal stream unavailability. Some others can be declared (or
not) as triggers during configuration. This enables tuning of behavior in the case of
errors, and selection whether the main MPEG table presence is checked or not.

For an IP Rx input:
Alarm Probable Cause Fixed Operator
trigger choice
BITRATE_OVERFLOW YES NO
BITRATE_UNDERFLOW YES NO
LOW_QUALITY_OUTPUT_CLOCK YES NO
OUTPUTDEVICEERROR YES NO
STREAM_OVERFLOW YES NO
UNLOCKED_PLL YES NO
NO_STREAM_RECEIVED YES NO
LOSS_OF_TS_SYNCHRO YES NO
FRAMING_ERROR YES NO
UNCORRECTABLE_ERRORS NO YES
LOSS_OF_FRAME YES NO
SIGNAL_DEGRADE NO YES
PAT_NOT_PRESENT NO YES
PMT_NOT_PRESENT NO YES
For an ATM Rx input:

Alarm Probable Cause Fixed User
trigger choice
OUTPUTDEVICEERROR YES NO
STREAM_OVERFLOW YES NO
BITRATE_UNDERFLOW YES NO
CORRECTED_ERROR NO NO
LOSS_OF_TS_SYNCHRO YES NO
UNCORRECTABLE_ERRORS NO YES
UNLOCKED_PLL YES NO

For an ASI input:

Alarm Probable Cause Fixed User
trigger choice
BITRATE_OVERFLOW YES NO
LOSS_OF_STREAM YES NO
LOSS_OF_SIGNAL YES NO
LOSS_OF_SYNCHRONISATION YES NO

1.5 - Description of the management systems
1.5 - DESCRIPTION OF THE MANAGEMENT SYSTEMS
NetProcessor 9010 provides the following Configuration, Monitoring and

Diagnostics accesses:
• SNMP agent for alarm, statistics & monitoring collection, and alarm traps;
• Web Interface for configuration management and current state browsing;
• Command Line Interface available via a terminal port or Telnet for configuration
and current state browsing and debugging;
• XMS 3500 management system for monitoring. Monitoring of incoming
services is limited to 100 services maximum per TS.

Figure 1.33: Configuration, Monitoring and Diagnostics accesses

1.5.1 - SNMP agent
1.5.1.1 - Agent
¤ Protocol
NetProcessor 9010 provides an SNMP interface based on SNMPv2c.
¤ Trap management
NetProcessor 9010 can register up to 10 NMSs as trap receivers. The ability to set
the managers' IP is provided by the MIB itself through the Trap destination address
setting.
Traps are raised for events such as alarms, Cold or Warm Starts and Configuration
changes (used for redundancy managed by an NMS).
The trap loss detection mechanism is provided by NetProcessor 9010. If an NMS
detects a trap loss, it can be re-synchronized by retrieving the active alarm list or
any other information relating to traps.
1.5.1.2 - MIB
The MIB is organized into three parts:
• The standard MIB, which includes the MIB II system group. The SNMP agent
manages the following variables under the MIB-II standard MIB (according to
RFC1213): SysDescr, SysObjectId, SysUpTime, SysContact, SysName and
SysLocation.
• The Thomson General MIB, which manages the following variables: a log of
latest events, the list of active alarms, Firmware identifier, Option identifier,
Detected boards, Reboot command, Configuration commands (Save, Download,
Apply) and Upgrade commands.
• The Thomson NFP MIB, which manages MPEG Services & Components
Statistics & Monitoring variables based on ETR290.

1.5.2 - Web Interface
The protocol used to connect the Web browser (Microsoft Internet Explorer release
6.0 or later) to the Web Server hosted in NetProcessor 9010 is HTTP.
JRE 1.5.0 is required.
Some information is available in read/write mode for configuration management:
- Static configuration (provisioning, interfaces, options),
- Multiplexing setting,
- Firmware download,
- Configuration file upload and application.
Some information is available in read-only mode for monitoring purposes:
- Alarms, statistics, monitoring and chassis identifier.
This interface is not intended for operation but mainly for product configuration.
1.5.3 - Command Line Interface (CLI)
This interface is accessible either via the Ethernet link and Telnet if the IP address is
known or via the serial link and the PC hyperterminal application.
Command Line Interface use is the same regardless of the access mode used.
The Command Line Interface is used for IP address setting, Web server
enabling/disabling and port number setting: these settings are public.
The available CLI commands depend on the user group (operator or service
authenticated by specific logins and passwords). There is no GUI for this interface.
Command lines are interactive (question/answer).
1.5.4 - XMS 3500 eXtensible Management System
NetProcessor 9010 is fully controlled by the Thomson XMS 3500 eXtensible

Management System (Configuration, Monitoring and Diagnostics).

1.6 - Standard Compliance
1.6 - STANDARD COMPLIANCE
NetProcessor 9010 complies with the following standards:
ISO/IEC 13818-1 Information technology - Generic coding of moving pictures

and associated audio information: Systems
ETSI ETR 290 Measurement Guidelines for DVB systems
ETS300429 Interfaces for CATV/SMATV headends and similar
professional equipment
EN 50083-9 Cabled distribution systems for television, sound and

interactive multimedia signals
Part 9: Interfaces for CATV/SMATV headends and similar
professional equipment for DVB/MPEG-2 transport streams
IETF RFC 791 IP v4

IETF RFC 768 User Datagram Protocol (UDP)
IETF RFC 793 Transmission Control Protocol (TCP)
IETF RFC 1889 Real-time Transport Protocol (RTP)
IETF RFC1065 Structure and identification of management information for
TCP/IP-based internets – SNMP v1
IETF RFC1066 Management information base for network management of
TCP/IP-based internets – SNMP v1
IETF RFC1067 A simple network management protocol – SNMP v1
IETF RFC1901 Introduction to Community-based SNMPv2
IETF RFC1908 Coexistence between Version 1 and Version 2 of the
Internet-standard Network Management Framework
IETF RFC2616 Hypertext Transfer Protocol - HTTP/1.1

ITU-T J131 Transport of MPEG-2 signals in PDH networks
ITU-T J132 Transport of MPEG-2 signals in SDH networks
DVB/ETS 300813 DVB interfaces to Plesiochronous Digital Hierarchy (PDH)
networks
DVB/ETS 300814 DVB interfaces to Synchronous Digital Hierarchy (SDH)
networks

1.6 - Standard Compliance
ITU-T I363.1 B-ISDN ATM Adaptation Layer specification: Type 1 AAL

ITU-T J83 Annex A Digital Multi-programme systems for television, sound and data
services for cable distribution
ITU-T G783 Characteristics of synchronous digital hierarchy (SDH)
equipment functional blocks
ITU-T G841 Types and characteristics of SDH network protection

architectures
ITU-T G957 Optical interfaces for equipments and systems relating to the
synchronous digital hierarchy
ITU-T G825 The control of jitter and wander within digital networks which
are based on the synchronous digital hierarchy (SDH)
ITU-T G703 Physical/electrical characteristics of hierarchical digital
interfaces
ITU-T G704 Synchronous frame structures used at 1544, 6312, 2048, 8448
and 44 736 kbit/s hierarchical levels
ITU-T G804 ATM cell mapping into plesiochronous digital hierarchy (PDH)
ITU-T G832 Transport of SDH elements on PDH networks – Frame and
multiplexing structures
SMPTE 2022-1-2007 Forward Error Correction for Real-Time Video/Audio
Transport Over IP Networks
SMPTE 2022-2-2007 Unidirectional Transport of Constant Bit Rate MPEG-2

Transport Streams on IP Networks
IETF RFC3550 "RTP, a transport for real time applications"

2004-07

1.7 - General device Specifications
1.7 - GENERAL DEVICE SPECIFICATIONS
1.7.1 - Electrical specifications
¤ Power supply
Built-in AC power supply for chassis without redundancy
Power supply characteristics

Mains voltage 100 - 240VAC (one range with no switching).
Mains type 50 - 60Hz
Max. input current 1.9A - 1.3A
(in normal mode)
Inrush current < 30A cold start up, 230V, < 5ms
Network connection Type A device connected with a non-industrial
CEI 60320 compliant plug.
Earthing arrangement TN/TT
For Norway and only for this country, this
device can be connected to an earthing
arrangement of IT type for a voltage, between
phases, of 230V.
Isolation class I
Installation category II
Overcurrent protection Built-in protection, cannot be accessed or reset.
Additional power supply characteristics

Efficiency 80% average at 230VAC
Power factor (cos Φ) 0.98
Overheating protection Built-in
Overload protection Built-in

Pluggable AC power supply for chassis with two AC Power Supplies or

chassis with one AC Power Supply + one DC Power Supply (chassis with
redundancy)
Characteristics
Mains voltage 100 - 240Vac (one range with no switching).
Max. input current. 1.7A - 0.7A per PSU (with two PSUs operating
(in normal mode) in the same chassis).
Max. input current. 3.4A - 1.4A for a single PSU in operation (if
(in default mode) one PSU is faulty).
Inrush current < 15A cold start up, 230V per unit.
Network connection Type A device connected by a non-industrial
arrangement of IT type for a voltage between
phases of 230V.
Isolation class I
Sales reference for the 2nd Power N900PS2AAA
Supply in an AC/DC dual PS
chassis
Sales reference (spare) N900SPACGx
Additional characteristics
Efficiency 75% to 82% according to the load
Power factor (cos Φ) 95.4 minimum
Front panel signalling Green Power indicator: correct output voltage
Red Fault indicator:
• overheating;
• absence of mains power;
• absence of secondary voltages.
Width 8TE
Weight 0.8 kg

Pluggable DC power supply for chassis with one AC Power Supply + one
DC Power Supply (chassis with redundancy)
Characteristics
Input voltage 48VDC + 20% - 16%
Current type DC supply
Max. input current 3.35A per PSU
(in normal mode) (with two PSUs operating in the same chassis).
Max. input current 6.75A for a single PSU in operation
(in default mode) (if one PSU is faulty).
Inrush current 12A cold start up, 48V per unit.
Network connection Male/female 3-pin SubD connector.
Earthing arrangement DCI system (DC return isolated)
Isolation class I
DC network ETS 300132-2, September 1996
Earthing standard ETS 300253
Sales reference for the 2nd Power N900PS2DAA
Supply in a DC/DC dual PS
chassis
Sales reference for spare N900SPDCGx
Overheating protection. Built-in
Overload protection. Built-in
• overheating;
• absence of primary power;
• absence of one of the secondary voltages.
Width 8TE
Weight 0.8kg
¤ Power consumption
Power Consumption for NetProcessor 9010 (full equipped): 180W

1.7.2 - Mechanical features
¤ DIMENSIONS
Device width 19"

Device height 1RU
Device depth with BNC connectors 570 mm for chassis with one built-in AC
Power Supply and 580 mm for chassis with
two Power Supplies for redundancy
(AC/AC, AC/DC or DC/DC)
Figure 1.34: NetProcessor 9010 dimensions

for chassis with one built-in AC Power Supply

AC + DC version
DC + DC version
AC + AC version
36,2 445 36,2

M4 screw M4 screw
for EMC for EMC
ground ground
145,4
257,2
145,4
502
560
580
392,8
502
162,6
219
219
115,3
26
26
41
36
4,8 33,6
33,6 483
44,2

for chassis with two Power Supplies for redundancy (AC/AC, AC/DC or DC/DC)
¤ WEIGHT
NetProcessor 9010 full equipped 7kg
¤ Miscellaneous
Boards are not pluggable.

1.7.3 - Ventilation
Built-in ventilation system (five fan units)

Ventilation Air circulated from left to right (as seen from front)
Ventilated air flow 50 m3/h
Air in Air out
Figure 1.36: Ventilation
The following precautions should be observed when mounting the

device in a standard 19" rack:
• Position the device on "low profile" L-profiles (10mm-height
reduced to 5mm in the areas facing the air inlet and outlet).
• Ensure the rack is well ventilated.

1.7.4 - Environmental specifications
¤ CE labeling
• Complies with European Directive 93/68/EEC (22/07/93).
¤ Safety specifications
• Legislation
Complies with European Low Voltage Directive 2006/95/EC.
• Standards
Complies with IEC 60950-1 (2001 First Edition).
Complies with EN 60950-1 (2001 First Edition).
UL 60950-1 (2003) and CSA C22.2 No. 60950-1-03 (2003) Certification for
Canada (file E300838).
¤ Electromagnetic specifications
• Legislation
Complies with European Directive 2004/108/EC.
• Standards
Complies with EN 55022 A1 (2001), A2 (2003) and EN 61000-3-2 for emissions.
Complies with EN 55024 A1 (2001) for immunity.
Complies with FCC Part 15, Class A recommendations.
Complies with VCCI, Class A recommendations:
¤ Climatic specifications
• During operation
Complies with ETS 300 019-1-3 (February 1992):
• Environmental class 3.1;
• Operation in temperature-controlled locations;

• + 5oC to + 50oC;
• 85% humidity compliant with the climatogram featured in the standard.
• During storage
• Environmental class 1.2;
• Storage in weather-protected, partly temperature-controlled locations;
• - 25°C to + 70°C;
¤ Transport specifications
• Environmental class 2.2: "Careful transportation" for mechanical conditions;
• - 25°C to + 70°C;
¤ Vibration, shock and fall specifications
Complies with ETS 300 019-1-2 (February 1992).
¤ Protection specifications
• IP20 protection.
¤ Pollution specifications
• No. 2 pollution.
1.7.5 - Reliability
MTBF at 30°C: 100,000 hours with one PSU.

1.8 - EU declaration of conformity
1.8 - EU DECLARATION OF CONFORMITY

1.8 - EU declaration of conformity
BLANK PAGE

Chapter 2 - Installation and Start up 83
Chapter 2
Installation and Start up
2.1 - Installation procedure.......................................................................... 85
2.2 - NetProcessor 9010 mechanical features ........................................... 86
2.3 - Rack mounting ..................................................................................... 88

2.3.1 - Removing the securing brackets .................................................... 88
2.3.2 - NetProcessor 9010 installation requirements ................................. 89
2.3.3 - Ventilation restrictions..................................................................... 89
2.3.4 - Cabling restrictions ......................................................................... 95
2.3.5 - EMC ground restrictions ................................................................. 95
2.3.6 - Power supply and protective ground restrictions ............................ 96
2.3.6.1 - Power inlet ..................................................................................... 96
2.3.6.2 - Power supply cord(s) ..................................................................... 97
2.3.6.2.1 - Cord(s) for AC mains power supply .............................................. 97
2.3.6.2.2 - Cord(s) for DC power supply ........................................................ 98
2.3.7 - Mechanical and Electrical Specifications........................................ 99
2.3.7.1 - Mechanical specifications .............................................................. 99
2.3.7.2 - Electrical specifications ................................................................ 101
2.4 - Power up ............................................................................................. 104
2.5 - Setting the initial parameters via the Command Line Interface..... 105
2.5.1 - Accessing the Command Line Interface ....................................... 105
2.5.2 - Login and password...................................................................... 107
2.5.3 - Help .............................................................................................. 109
2.5.4 - Setting initial parameters .............................................................. 110
2.5.5 - Commands relating to IP parameters ........................................... 111
2.5.5.1 - Displaying IP parameters (ipdisp) ................................................ 111
2.5.5.2 - Editing IP parameters (ipset) ....................................................... 111
2.5.6 - Commands relating to the date and time...................................... 113
2.5.6.1 - Displaying the current date and time (ddate) ............................... 113
2.5.6.2 - Changing the date and time (sdate)............................................. 113

84 Chapter 2 - Installation and Start up

the ASI FLEX board ........................................................................... 114
2.5.7.1 - Displaying the number of ASI inputs for ASI FLEX board (dasiin) 115
2.5.7.2 - Editing the number of ASI inputs for ASI FLEX board (sasiin) ..... 115
2.5.8 - Commands related to SysName, SysContact and SysLocation .. 117
2.5.8.1 - Displaying SysName, SysContact and SysLocation (rinfo) .......... 117
2.5.8.2 - Editing SysName, SysContact and SysLocation (winfo) .............. 118
2.6 - Connecting the cables....................................................................... 119

2.6.1 - Connecting the cables on the main board .................................... 119
2.6.2 - Connecting the cables on the Gigabit Ethernet interfaces ........... 121
2.6.3 - Connecting the cables on the ATM extension board.................... 121
2.6.4 - CMD1 LEDS ................................................................................. 122

2.1 - Installation procedure
2.1 - INSTALLATION PROCEDURE
The following steps are required for device installation and initial configuration:
1. Mounting the device in a rack;
2. Powering the device;
3. Entering the initial parameters via the Command Line Interface (IP parameters,
Date/Time, NTP configuration);
4. Connecting the device to the other devices;
5. Checking the LEDs.

2.2 - NetProcessor 9010 mechanical features
2.2 - NETPROCESSOR 9010 MECHANICAL FEATURES
¤ Chassis types
NetProcessor 9010 is a 1RU chassis which is available in four versions:
• chassis with one AC Power Supply.
• chassis with one AC and one DC Power Supply for redundancy.
¤ Power Supply Units (PSU)
There are three PSU models:
• A built-in AC PSU model for chassis with one AC Power Supply.
• A pluggable AC PSU model for chassis with two AC Power Supplies and for
chassis with one AC and one DC Power Supply.
• A pluggable DC PSU model for chassis with two DC Power Supplies and for
chassis with one AC and one DC Power Supply.
Mixing two different PSU models in the same chassis is authorised for chassis with
one AC and one DC Power Supply for redundancy only (a foolproof system on the
power supply boards and chassis prevents such combinations on other chassis
models).
In a redundant chassis the two PSUs share the overall chassis consumption in
normal mode. If one PSU fails, the other will supply the whole chassis.
¤ Dimensions
NetProcessor 9010 has the following dimensions:
• Width: 19",
• Height: 1RU,
• Depth (with BNC connectors): 570 mm for chassis with one built-in AC Power
Supply and 580 mm for chassis with two Power Supplies for redundancy
(AC/AC, AC/DC or DC/DC).
See section Mechanical specifications, page 99 for more details.

2.2 - NetProcessor 9010 mechanical features
¤ Air flow
Cold air is taken in from the left and hot air is expelled to the right.
Air in Air out
Figure 2.1: Cooling air flow for NetProcessor 9010
A build up of dust on the air inlet grill will cause the internal
temperature to rise and will result in a deterioration in performance,
reliability and service life of the device.
You are advised to regularly clean the air inlet grill (at least once a
year).

2.3 - Rack mounting
2.3 - RACK MOUNTING
Rack mounting is not mandatory for NetProcessor 9010 but the ventilation and
safety requirements given in this section must be observed in all cases.
The chassis must not be fixed with its rack mounting ears only. If
you intend to install it in a rack, L-profiles are required and you must
observe the ventilation and safety instructions described in the
following sections.
2.3.1 - Removing the securing brackets
Two brackets, located at the side of the chassis, are used to secure the device in its
packaging.
Remove the two screws from these brackets before mounting the device in a rack.
Figure 2.2: Securing brackets

2.3 - Rack mounting
2.3.2 - NetProcessor 9010 installation requirements
This section lists the principles to be observed and the steps to be taken when
installing NetProcessor 9010 in a 19" rack.
The following restrictions must be observed:
Ventilation restrictions page 89

Cabling restrictions page 95
EMC ground restrictions page 95
Power supply and protective ground restrictions page 96
2.3.3 - Ventilation restrictions
Please note that product failure rates are increased by high temperatures. The
following precautions should therefore be observed:
• Prevent hot air from one device being introduced into other devices;
• Ensure adequate distribution of air flows to the device intakes;
• Avoid the effects of natural convection between devices;
• Avoid hot/cold air short-circuits;
• Avoid transverse effects in coupled racks;
• Prevent hot air from accumulating in the rack;
• Check the air flows: the rack should ensure a sufficient supply of cold air and
sufficient evacuation of hot air (according to the number of devices mounted in
the rack and their corresponding air flows);

2.3 - Rack mounting
The following important requirements should be added to the general

recommendations:
• As the device does not feature an air filter, it must be installed in a room with
low dust levels. The maximum density of dust in the air must not exceed
100µg/m3 and the maximum number of particles with a diameter greater than
1µm must not exceed 1 million/m3. To prevent the power supply from
overheating, remember to regularly clean the rack filter (if there is one), according
to the filter manufacturer’s recommendations, and also NetProcessor 9010’s air
inlet grill (at least once a year);
• There must be enough room for a column of cold air to circulate on the left of
the chassis and a column of hot air to circulate on the right of the chassis, from the
bottom to the top of the rack.
• Cut the L-profiles so as they do not exceed 4.8mm in height in the areas facing
NetProcessor 9010’s air inlet and outlet. This will prevent any hot air from
accumulating in the device.
L-Profile
40mm
4.8mm
depends on the rack depth
Cut the L-profiles so as they do not exceed 4.8mm in height in the areas facing
NetProcessor 9010’s air inlet and outlet

2.3 - Rack mounting
• Given its exact 1RU height, NetProcessor 9010 can be placed on top of
another NetProcessor or other 1RU equipment without an L-profile. It is however
advisable to observe the following restrictions:
• If the rack is positioned on a pressurised floor, it is possible to stack
NetProcessors or other 1RU equipment in groups of four, each group being
separated from another group by a space of 1RU.
(however, maintenance operations are facilitated if these groups are limited

to two NetProcessors or other 1RU equipment);
• In the absence of a pressurised floor, limit the group size to two chassis.
Failure to observe these installation requirements will directly result in a
deterioration in performance, reliability and service life of equipment.

2.3 - Rack mounting
Figure 2.3: First example: NetProcessor and other 1RU equipment

on a pressurized floor & in a standard rack (front view)

2.3 - Rack mounting
Figure 2.4: First example : NetProcessor and other 1RU equipment

on a pressurized floor & in a standard rack (side view)

2.3 - Rack mounting
Figure 2.5: Second example :NetProcessor and other 1RU equipment

on a unpressurized floor & in a standard rack (front view)

2.3 - Rack mounting
2.3.4 - Cabling restrictions
It is essential to separate the power supply cables from the signal cables. When
facing the rear of the rack (as the device is connected via the rear panel), the power
supply cables must be guided to the right of the chassis and the signal cables to the
left.
2.3.5 - EMC ground restrictions
The EMC connection is required to ensure ground equipotentiality between the

different devices in the technical center (only one connection is required per
device).
Each chassis side panel features a tapped hole to connect an bonding strip. This
bonding strip is fixed using an M4 screw whose length depends on the bonding strip
type (no more than 8mm of the screw must enter the chassis in relation to its outer
edge). The bonding strip must have a 6mm² cross-section and be shorter than
500mm.
Figure 2.6: EMC connection

2.3 - Rack mounting
2.3.6 - Power supply and protective ground restrictions
2.3.6.1 - Power inlet

The power outlet comprises a connector without an On/Off switch.
There are four kinds of power inlet according to the chassis model.
• chassis with one built-in AC Power Supply.
• chassis with one AC Power Supply and one DC Power Supply for redundancy.
Figure 2.7: Chassis models and their associated power supply inlets

2.3 - Rack mounting
2.3.6.2 - Power supply cord(s)
2.3.6.2.1 - Cord(s) for AC mains power supply
1. Never supply a unit which is not in the chassis.

2. The built-in overload protection cannot be accessed or reset.
¤ Specifications
The AC mains power cords are only shipped with the device if ordered. Otherwise,
it is advisable to use AC mains cables with the following features:
• Device end of cable: CEI 320 compliant connector;
• Flexible wire: 3 x 1 mm2 cross-section or 18 AWG, 10 A minimum, 250 V
compliant with the applicable standard or rules of the country where the device
is installed;
• Mains outlet end of cable: plug compliant with the applicable standard or rules
of the country where the device is installed.
¤ Connecting AC mains power supply cord(s)
Power supply end
The connection panel should comply with the legislation in force in the country of
installation. The connection panel must be positioned in the rack in such a way that
the plug and power cord(s) are within easy reach for switching off purposes.
For (each) mains inlet, the wiring system must feature overload and earth fault
protection and a bipolar cut-off device or a differential circuit breaker. If in doubt,
contact a qualified electrician.
NetProcessor 9010 end
Plug the power cord(s) into the mains inlet.

2.3 - Rack mounting
2.3.6.2.2 - Cord(s) for DC power supply
¤ Specifications
The DC power supply cable wires are coloured in accordance with the following
codes:
Pin layout Terminals Wire colour

INTERNATIONAL
(Cable Ref. 46131742)
A1: - BLUE
A2: protective earth GREEN/YELLOW
A1 A2 A3 A3: + BROWN
The earthing standard is DC/I with DC return isolated.
- must be linked to a cut-off device.

+ must be linked to the protective earth (safety ground) outside the
device.
The DC power source must be of SELV type (Secundary Electrical Low Voltage). It
must be located in the same building as the device and the entire source circuit must
be kept within the building.
¤ Connecting DC power supply cords
Power supply end
The connection panel should comply with the legislation in force in the country of
installation. The connection panel must be positioned in the rack in such a way that
the plug and power cords are within easy reach for switching off purposes.
The wiring system must feature protection against overcurrents which accepts
voltages of 48 VDC + 20% - 16% and supports inrush current when the device is
plugged in. If in doubt, contact a qualified electrician.
NetProcessor 9010 end
Connect the power cord(s) to the DC power inlet(s).

2.3 - Rack mounting
2.3.7 - Mechanical and Electrical Specifications
2.3.7.1 - Mechanical specifications

¤ DIMENSIONS
Device width 19"

Device height 1RU
Device depth with BNC connectors 570 mm for chassis with one built-in AC
Power Supply and 580 mm for chassis with
two Power Supplies for redundancy
(AC/AC, AC/DC or DC/DC).
Figure 2.8: NetProcessor 9010 dimensions for chassis with one built-in AC Power Supply

2.3 - Rack mounting
AC + DC version
DC + DC version
AC + AC version
36,2 445 36,2

M4 screw M4 screw
for EMC for EMC
ground ground
145,4
257,2
145,4
502
560
580
392,8
502
162,6
219
219
115,3
26
26
41
36
4,8 33,6
33,6 483
44,2

for chassis with two Power Supplies for redundancy (AC/AC, AC/DC or DC/DC)
¤ WEIGHT
NetProcessor 9010 fully equipped 7kg
¤ VENTILATION
Built-in ventilation system

Ventilated air flow 50m3/h
Delta T 13°C

2.3 - Rack mounting
2.3.7.2 - Electrical specifications

¤ Power supply
Built-in AC power supply for chassis without redundancy
Power supply characteristics

Mains voltage 100 - 240VAC (one range with no switching).
Max. input current 1.9A - 1.3A
(in normal mode)
Inrush current < 30A cold start up, 230V, < 5ms
Network connection Type A device connected with a non-industrial
arrangement of IT type for a voltage, between
phases, of 230V.
Isolation class I
Additional power supply characteristics

Efficiency 80% average at 230VAC
Power factor (cos Φ) 0.98

2.3 - Rack mounting
Pluggable AC power supply for chassis with two AC Power Supplies or

chassis with one AC Power Supply + one DC Power Supply (chassis with
redundancy)
Characteristics
Mains voltage 100 - 240Vac (one range with no switching).
Max. input current. 1.7A - 0.7A per PSU (with two PSUs operating
(in normal mode) in the same chassis).
Max. input current. 3.4A - 1.4A for a single PSU in operation (if
(in default mode) one PSU is faulty).
Inrush current < 15A cold start up, 230V per unit.
Network connection Type A device connected by a non-industrial
arrangement of IT type for a voltage between
phases of 230V.
Isolation class I
Sales reference for the 2nd Power N900PS2AAA
Supply in an AC/DC dual PS
chassis
Sales reference (spare) N900SPACGx
Power factor (cos Φ) 95.4 minimum
• overheating;
• absence of mains power;
• absence of secondary voltages.
Width 8TE
Weight 0.8 kg

2.3 - Rack mounting
Pluggable DC power supply for chassis with one AC Power Supply + one
DC Power Supply (chassis with redundancy)
Characteristics
Input voltage 48VDC + 20% - 16%
Current type DC supply
Max. input current 3.35A per PSU
(in normal mode) (with two PSUs operating in the same chassis).
Max. input current 6.75A for a single PSU in operation
(in default mode) (if one PSU is faulty).
Inrush current 12A cold start up, 48V per unit.
Network connection Male/female 3-pin SubD connector.
Earthing arrangement DCI system (DC return isolated)
Isolation class I
DC network ETS 300132-2, September 1996
Earthing standard ETS 300253
Sales reference for the 2nd Power N900PS2DAA
Supply in a DC/DC dual PS
chassis
Sales reference for spare N900SPDCGx
Overheating protection. Built-in
Overload protection. Built-in
• overheating;
• absence of primary power;
• absence of one of the secondary voltages.
Width 8TE
Weight 0.8kg
¤ Power consumption
The maximum power required for a NetProcessor 9010 is 180W.

2.4 - Power up
2.4 - POWER UP
Check that NetProcessor 9010 is not yet connected to the LAN, as

factory-set IP addresses may cause disturbance on the LAN when
NetProcessor 9010 is switched on (address conflict).
Connect the power cord and switch on the device. The green POWER LED(s) will
come on.
After a start-up phase, the device will become operational. When the device is
switched on, the last stored configuration will be active.

2.5 - Setting the initial parameters via the Command Line Interface
2.5 - SETTING THE INITIAL PARAMETERS VIA THE COMMAND

LINE INTERFACE
2.5.1 - Accessing the Command Line Interface
In this section and those that follow, the Command Line Interface will be
abbreviated by CLI.
CLI can be accessed:
• either via the Ethernet link and the PC Telnet application if the device IP address
is known;
• or via the serial link and the PC hyperterminal application (or any terminal
emulator).
CLI use is the same regardless of the access mode used.
¤ Accessing the CLI via the Ethernet link
The CLI is accessed via the Telnet application installed on the PC.
The NetProcessor 9010 IP address, which is required for Telnet connection, is given
on the Acceptance Test Report shipped with the device.
Factory set IP address for CMD1: 10.11.129.107
As the NetProcessor 9010 CMD Ethernet interfaces host an autocrossover

mechanism, you can use direct or crossed cable connection between the PC and
NetProcessor 9010.

The Telnet application must be set up as follows:
Terminal options No local echo

Block cursor
no CR LF
Emulation VT100 / ANSI
Set up the Telnet connection between the PC and NetProcessor 9010;
A welcome page will be displayed.

¤ Accessing the CLI via the serial link
The CLI is accessed via a serial link between NetProcessor 9010 and a terminal or a
PC emulating a terminal.
• Connect the terminal (or the PC emulating a terminal) to the NetProcessor 9010
RJ45 connector via an RS232 to Ethernet adapter cable.
- The RJ45 pinout on NetProcessor 9010 is:
8 1
- The RJ45-SubD9 female adapter cable wiring is:

• Set up the terminal port as follows: 9600 bauds, 8 bits, no parity, 1 start, 1 stop,
no flow control;
Figure 2.10: Terminal port setup for accessing the CLI
Click on OK to set up the connection between the PC and NetProcessor 9010;

A welcome page will be displayed.
2.5.2 - Login and password
The welcome page displayed after connection will request the user login and
password.
CLI has two predefined user groups: "service" and "operator".
• The Service group is for Technicians who are responsible for installation. The
Login and password are respectively: service and service.
• The Operator group is for Users who are in charge of operation. The Login and
password are respectively: operator and operator.

1. In the current release, you must proceed as follows to log in as

service:
• Log in as operator (with login and password: operator and
operator);
• Type user
• Answer service and service for login and password.
2. CLI is case sensitive (service is correct, Service is not correct).

2.5.3 - Help
¤ General Help
To get the list of all available CLI commands (related to user rights), the Operator
has to type help after the prompt. Two types of help are available: one for Service
and one for Operator.
Example:
CLI.Operator> help
The CLI provides many commands. Some of these commands are

not, however, intended for the device user but reserved for Thomson
use only. It is therefore important to only use the commands
described in this manual so as not to disrupt device operation or jam
the device, as this would require assistance from Thomson Customer
Services.

2.5.4 - Setting initial parameters
The following table lists the commands used to set the initial parameters.
User operation Associated Section
commands
Setting basic parameters ipdisp1, Displaying IP parameters (ipdisp), page 111
ipdisp2
ipset1, Editing IP parameters (ipset), page 111
ipset2
ddate Displaying the current date and time (ddate),
page 113
sdate Changing the date and time (sdate), page 113
dasiin Displaying the number of ASI inputs for ASI
FLEX board (dasiin), page 115
sasiin Editing the number of ASI inputs for ASI FLEX
board (sasiin), page 115
rinfo Displaying SysName, SysContact and SysLoca-
tion (rinfo), page 117
winfo Editing SysName, SysContact and SysLocation
(winfo), page 118
Table 1: List of CLI commands associated with the initial parameters

2.5.5 - Commands relating to IP parameters
The procedure for setting IP parameters is the same for both CMD1 and CMD2
ports. CMD1 port is used for Commands, Monitoring & Diagnostics.
2.5.5.1 - Displaying IP parameters (ipdisp)

(Login: Service or Operator)
Two commands are available to display IP parameters for CMD1 and CMD2.
To display the IP address for CMD1, type ipdisp1 after the prompt.
To display the IP address for CMD2, type ipdisp2 after the prompt.
Example:
Figure 2.11: Displaying IP parameters (ipdisp)
2.5.5.2 - Editing IP parameters (ipset)

(Login: Service)
Two commands are available to edit IP parameters for CMD1 and CMD2.
¤ CMD1 IP parameters
To set the IP address for CMD1, type ipset1 after the prompt then enter the
following fields:
• Type the new IP address, gateway and netmask values for CMD1;
• Type y after Do you really want to apply these parameters [Y]/[N(default)]? if
you wish to confirm the new values or n if you wish to keep the previous values.

Example:
Figure 2.12: Setting IP CMD1 parameters (ipset1)
Type Y.
As indicated in the MESSAGE line, you have to reboot the device by typing reboot
after the prompt.
Figure 2.13: Rebooting the device
Type y to confirm the reboot (or n if you want to cancel the reboot).
¤ CMD2 IP parameters
To set the IP address for CMD2, type ipset2 and proceed as with ipset1.
Figure 2.14: Displaying and editing IP CMD2 parameters (ipdisp2 and ipset2)

2.5.6 - Commands relating to the date and time
2.5.6.1 - Displaying the current date and time (ddate)

To display the current date and time, type ddate after the prompt.
The UTC date and time will be displayed.
Example:
Figure 2.15: Displaying the current date and time (ddate)
2.5.6.2 - Changing the date and time (sdate)

(Login: Service)
To change the date and time, type sdate after the prompt and enter the following
fields:
• Type the new date and time values in month, day, hour, minute and year format
(without spaces) after UTC time ?;
• Type y after Apply date&time now? if you wish to confirm the new values or n
if you wish to keep the previous values.

Example:
Figure 2.16: Setting the current date and time (sdate)

the ASI FLEX board
The ASI FLEX board supports 10 ASI ports which can be programmed individually
as inputs or outputs via the CLI interface.
ASI Flex board
Figure 2.17: Flexible ASI interface

2.5.7.1 - Displaying the number of ASI inputs for ASI FLEX board
(dasiin)
To display the number of ASI inputs, type dasiin after the prompt.
Example:
Figure 2.18: Displaying the number of ASI inputs for FLEX ASI board (dasiin)
2.5.7.2 - Editing the number of ASI inputs for ASI FLEX board
(sasiin)
(Login: Service)
1. To set the number of ASI inputs, type sasiin after the prompt.
2. Type the number of ASI inputs you require after INPUT_ASI_NUMBER.
3. Type y after Do you really want to apply these parameters? if you wish to
confirm the new values or n if you wish to keep the previous values.
Example:
Figure 2.19: Setting the number of ASI inputs for FLEX ASI board (ssasiin)
Type Y.

As indicated in the MESSAGE line, you have to reboot the device by typing reboot
after the prompt.
After the reboot, the ASI connections will be cleared from your
current configuration. Check your ASI cabling before reactivation of
your ASI IO to avoid signal conflicts.

2.5.8 - Commands related to SysName, SysContact and

SysLocation
SysName, SysContact and SysLocation can be edited when installing the product
using the CLI winfo command. Both parameters are readable in the MIB2 system.
When using the XMS 3500/XMU 3500 supervision system, the XMS
will apply its own Device name (independently of the SNMP
SysName). The current device name is displayed on every WebPage:
XMS Device Name or SysName.
Device name
2.5.8.1 - Displaying SysName, SysContact and SysLocation

(rinfo)
To display SysName, SysContact and SysLocation, type rinfo after the prompt.
Example:
Figure 2.21: Displaying SysName, SysContact and SysLocation (rinfo)

2.5.8.2 - Editing SysName, SysContact and SysLocation (winfo)

(Login: Service)
1. To set SysName, SysContact and SysLocation, type winfo after the prompt.
2. Type y after Do you really want to apply these parameters? if you wish to
confirm the new values or n if you wish to keep the previous values.
Example:
Figure 2.22: Setting the number of ASI inputs for FLEX ASI board (ssasiin)
Type Y.
The Device name is automatically refreshed on Web interface.
To update the MIB2 system, you have to reboot the device by typing reboot after
the prompt.

2.6 - Connecting the cables
2.6 - CONNECTING THE CABLES
2.6.1 - Connecting the cables on the main board
¤ ASI and CMD1 ports
Connect the upstream ASI devices to the ASI IN connectors and

the downstream ASI devices to the ASI OUT connectors.
CMD1
Connect the Management system to

the CMD1 10/100Base-T connector.
Note: CMD1 port performs 10/100Mbps autosensing, Half Duplex/Full Duplex

autonegotiation and hosts an autocrossover mechanism (auto MDI/MDI-X) for cable
connection.
Figure 2.24: Connecting the cables on the main board

¤ EXT_1 port
EXT_1 is used to create a bridged tunnel between 2 devices (e.g.
NetProcessor 9010) using one ATM PVC. The devices must belong to the same IP
subnet. Connection depends on the application. An example is given below:
EXT_1 CMD_1
EXT_1 CMD_1
Note: EXT_1 port performs 10/100/1000Mbps autosensing, Half Duplex/Full Duplex

autonegotiation and hosts an autocrossover mechanism (auto MDI/MDI-X) for cable
connection.
Figure 2.25: ATM remote NetProcessor 9010
Comments: on the remote NetProcessor 9010, Extension 1 port must be externally

connected to CMD1 (or CMD2) port.

2.6.2 - Connecting the cables on the Gigabit Ethernet

interfaces
LAN/WAN port 1 LAN/WAN port 2
Both ports are combo 10/100/1000Base-T, 1000Base-X (SFP) ports. Selection between
copper and optical interfaces is automatic with a priority to copper. If an optional SFP
module is plugged in, this link will be activated only if copper link is down (e.g. not
connected).
1000Base-T ports (electrical with RJ45) perform 100/1000Mbps autosensing, Half
Duplex/Full Duplex autonegotiation and host an autocrossover mechanism (auto
MDI/MDI-X) for cable connection.
Figure 2.26 : Connecting the cables on the Gigabit Ethernet interfaces
2.6.3 - Connecting the cables on the ATM extension board
Port ATM# 1 Port ATM# 2
Connect the ATM network(s) input/output to the SFP module of the ATM extension
board.
Note concerning the electrical SFP module N900SSF3AA

Electrical SFP module is provided with two BNC adaptation
cables. These BNC connectors should be mounted on a panel.
Panel cutout to use is described on the following drawing.
Figure 2.27: Connecting the cables on the ATM extension board

2.6.4 - CMD1 LEDS
CMD1
LEDs
ity
iv
ct
n
/A
io
s
d
lli
ee
Co
Sp
Full
8 1 100
Figure 2.28 : CMD1 LEDs
Left LED above the CMD1 connector (Collision)

Yellow fixed: collision
Off: no collision
Right LED above the CMD1 connector (Speed/Activity)
Green fixed: link
Green flashing: activity
Off: no link, no activity
Top LED on the right hand side of the CMD1 connector (Full)
Green fixed: Full Duplex
Off: Half Duplex
Bottom LED on the right hand side of the CMD1 connector (100)
Green fixed: 100Mbps
Off: 10Mbps

Chapter 3 - Operation with Web Interface 123
Chapter 3
Operation with Web Interface
3.1 - Introduction ........................................................................................ 125

3.1.1 - Foreword....................................................................................... 125
3.1.2 - Introduction ................................................................................... 125
3.1.3 - Setting the device ......................................................................... 125
3.1.4 - Step 1: Setting the interface static parameters............................. 127
communication parameters ................................................................ 130
3.1.6 - Step 3: Managing internal TS connections (patch panel) ............. 135
3.1.7 - Step 4: Setting data service over ATM and In-Band Control & Command
over ATM parameters......................................................................... 141
3.2 - Web Interface page breakdown ........................................................ 144
3.3 - Setting up the link between the PC and the Web Interface ............ 145
3.4 - Identification page.............................................................................. 147

3.4.1 - LEDs ............................................................................................. 147
3.4.2 - Charts ........................................................................................... 148
3.4.2.1 - Clicking on the charts................................................................... 148
3.4.2.2 - Shortcut commands attached to the charts ................................. 150
3.5 - Installation menu................................................................................ 162

3.5.1 - In-Band Control & Command over ATM setup menu ................... 163
3.5.2 - Data service over ATM menus ..................................................... 166
3.6 - Configuration menu ........................................................................... 169

3.6.1 - Top view menus............................................................................ 170
3.6.1.1 - Interface setup menus ................................................................. 171
3.6.1.1.1 - ASI setup dialog boxes ............................................................... 172
3.6.1.1.2 - ATM setup dialog boxes ............................................................. 173
3.6.1.1.3 - IP setup dialog boxes.................................................................. 176
3.6.1.2 - Rx and Tx setup menus ............................................................... 181
3.6.1.2.1 - ATM Rx and ATM Tx setup menus............................................. 182
3.6.1.2.2 - IP Rx and IP Tx setup menus ..................................................... 186
3.6.1.3 - Patch panel .................................................................................. 197

124 Chapter 3 - Operation with Web Interface
3.6.1.3.1 - Connection list............................................................................. 197

3.6.1.3.2 - Input Transport Stream Redundancy .......................................... 202
3.6.1.3.3 - Alarm setup for early IP network degradation signaling .............. 216
3.6.2 - Connection list menu.................................................................... 217
3.6.3 - Stored configurations command................................................... 218
3.7 - Maintenance menu............................................................................. 225

3.7.1 - Reboot .......................................................................................... 225
3.7.2 - Options ......................................................................................... 226
3.7.3 - Global setting ............................................................................... 227
3.8 - Status menu........................................................................................ 228

3.8.1 - All alarms page............................................................................. 228
3.8.2 - Events page ................................................................................. 229
3.8.3 - Report page.................................................................................. 230
3.9 - Monitoring menu ................................................................................ 231

3.9.1 - Monitoring menu........................................................................... 231
3.9.2 - Network port counters page ......................................................... 232

3.1 - Introduction
3.1 - INTRODUCTION
3.1.1 - Foreword
The Web Browser must be Microsoft Internet Explorer release 6.0 or +.

The JRE (Java Run Environment) release must be 1.5.0.
The NetProcessor 9010 Web interface allows the Operator to:

• set the device and the data service;
• get input and output stream descriptions with bitrate indication;
• get alarms and event logs;
• launch maintenance commands, e.g. device restart.
3.1.3 - Setting the device
NetProcessor 9010 processing is illustrated in the following block diagram. This

diagram also shows setup procedure steps, including:
1. Setting the ASI, ATM and Gigabit Ethernet interface static configuration;
2. Setting Tx and Rx dynamic network communication parameters;
3. Setting internal TS connections;
4. Setting the data service over ATM and the In-Band Control & Command over
ATM.

3.1 - Introduction
Figure 3.1: NetProcessor 9010’s processing block diagram

3.1 - Introduction
3.1.4 - Step 1: Setting the interface static parameters
Figure 3.2: Setting the interface static parameters
The static parameters called ASI setup, ATM setup and ETH setup set the operating
mode for the ASI, ATM and Gigabit Ethernet interfaces.
The commands for setting these parameters are only used during initial setup (or in
rare cases such as after the device has been moved).
These commands are used to configure:
• the following ASI setup parameters: Label, Enable/Disable and Maximum
bitrate for the ASI IN setup parameters and Label, Enable/Disable and Packet
size for the ASI OUT setup parameters.
• the following ATM setup parameters: Label, Enable/Disable, Clock Source,
OAM activity, Mode and Scrambling, Cosset.
• the following ETH setup parameters: Physical port label, Operation status
(Enable/Disable), Interface nominal status, Interface backup status, Interface
Speed & Mode, IP address and Netmask, Shaping On/Off, Maximum output
bit rate, Dynamic IP routing, Static IP Routing.

3.1 - Introduction
All these commands can be found in the Top view view.
Two ways of accessing

the same dialog box

the same dialog box
Figure 3.3: Configuration editing: Top view (ASI, ATM and Gigabit Ethernet setup)

3.1 - Introduction
The ASI, ATM and Gigabit Ethernet commands can also be accessed by clicking on
the connector icons on the Identification page.
ATM #1 ATM #2 LAN/WAN LAN/WAN

port #1 port #2
Figure 3.4: Identification page
A detailed description of the ASI, ATM and Gigabit Ethernet commands will be
given in section “Interface setup menus”, page 171.

3.1 - Introduction

communication parameters
Figure 3.5: Setting the Tx and Rx network communication parameters
ATM or IP transmission and reception parameters are required for setting up

network communications.
A mix of up to 10 Rx and Tx ATM connections with the SDH STM1 / STS3c
interface board, up to 4 Rx and 4 Tx ATM connections with the PDH E3/DS3
interface board, and up to 20 Rx and 20 Tx IP channels can be activated
simultaneously. This can be limited by software option settings.
The following parameters are adjusted with each transmission setup.
• For ATM Rx: Label, Activity on/off, Selected port, VPI, VCI and FEC.
• For ATM Tx: Label, Activity on/off, Selected port, VPI, VCI, FEC and Rate.
• For IP Rx:
- Transport layer: Label, Activity on/off, Selected port, Multicast destination
IP address, Source IP address and Reception UDP port.
- Adaptation layer: Rx Decapsulation, Rx FEC module on/off, Requested
IPDV Tolerance, Reordering Tolerance, Fixed rate on/off, Fixed rate

3.1 - Introduction
value.
• For IP Tx:
- Transport layer: Label, Activity on/off, Selected port, Destination IP
address, Use ARP, Destination MAC Address, Source IP address, Destina-
tion UDP port, MPEG TOS/Diffserv byte, TTL, QOS tagging, VLANId,
User Priority and Rate.
- Adaptation layer: TS Encapsulation, MPEG packets per IP frame, Max
TS output rate, FEC settings.
These parameters can be found in the ATM Rx list, ATM Tx list and IP Rx list, IP
Tx list views, which are accessible via the ATM Setup and Gigabit Ethernet Setup
menus in the Top view.

3.1 - Introduction
Figure 3.6: ATM Rx setup, ATM Tx setup and IP Rx setupIP, Tx setup dialog boxes
via the ATM Rx list, ATM Tx list and IP Tx list, IP Tx list views

3.1 - Introduction
They are also available via the Connection list by clicking on the Input and Output
labels.
via the Connections views

3.1 - Introduction

port #1 port #2
A detailed description of the Tx and Rx network communication commands will be

given in section “Rx and Tx setup menus”, page 181.

3.1 - Introduction
3.1.6 - Step 3: Managing internal TS connections (patch panel)
Figure 3.9: Managing internal TS connections
¤ Connections
The Operator can create/edit/duplicate/delete internal TS connections to send TSs
from ASI, ATM and Gigabit Ethernet interfaces to other interfaces.
These parameters are adjusted according to operating condition requirements.

3.1 - Introduction
They can be found in the Connection list window, accessible via the Connection
list command in the Patch panel or via the Connection list command in the menu
bar.
Figure 3.10: Connection list view

3.1 - Introduction
¤ Input Transport Stream Redundancy

by the Operator).
• Redundancy holdover is set to infinite for non-revertive automatic mode.
• Redundancy holdover can be adjusted to 10, 30 or 60 seconds for revertive
automatic mode.

3.1 - Introduction
Commands for setting the global input TS redundancy parameters (Redundancy

switching enable/disable, IP/ATM/MPEG triggers for automatic redundancy,
Redundancy holdover for automatic redundancy) are accessible via the
Redundancy command in the Patch panel.
Figure 3.14: Input TS redundancy
Commands for individual 1+1 input TS redundancy parameters (creating protected

connections, duplicating a protected output, connection monitoring, redundancy
operations) can be found in the Connection list window, accessible via the
Connection list command in the Patch panel or via the Connection list command
in the menu bar.

3.1 - Introduction
Create new
connections
Edit manual
switch

3.1 - Introduction
¤ Alarm setup for early IP network degradation signaling

Degradation is estimated by the number of RTP frame losses within a reordering
window. It measures loss density. A threshold specifies when this density is too
high and will be used to generate an alarm. The threshold value is expressed as
consecutive lost frames and can be set to the following values: infinite (infinite
means no alarm), 1 loss, 2 losses, 4 losses, 8 losses, 16 losses. This applies to all
RTP streams (and not UDP streams).
Figure 3.16: Alarm setup (Early IP network degradation signaling)

3.1 - Introduction
3.1.7 - Step 4: Setting data service over ATM and In-Band

Control & Command over ATM parameters
¤ Setting the Data link over ATM
Figure 3.17: Setting the data service over ATM
The Data service feature consists of Ethernet bridging between NetProcessor 9010
Extension 1 port (configured as a 10/100 Ethernet port) and one ATM PVC.
The following parameters need to be adjusted:
• For Extension port setup: Physical port label, Enable/Disable, Interface
Speed / Mode.
• For Data service setup: Data service mode, Policing rate, Label, Activity,
Selected port, VPI, VCI, Rate.
These parameters can be found in the Extension port setup menu and Data service
setup menu, which are accessible from the shortcut menu attached to the
Extension_1 port in the Identification page.

3.1 - Introduction
Figure 3.18: Extension Port 1 setup and Data service setup dialog boxes
in the Identification page

3.1 - Introduction
¤ Setting In-Band Control & Command over ATM

The In-Band C&C setup menu is used to set In-Band connection parameters, i.e.
the IP routing parameters (in the Global settings sub-panel) and the link parameters
Activity, VPI, VCI, Netmask, Local Ip and Remote IP (in the Links list sub-panel).
These parameters can be found in the shortcut menu attached to the ATM port in the
Identification page.
Figure 3.19: ATM In-Band C&C shortcut menus in the Edit configuration main window

3.2 - Web Interface page breakdown
3.2 - WEB INTERFACE PAGE BREAKDOWN
Each page has the same structure.
Figure 3.20: Web Interface page breakdown
A page contains four distinct zones:

• The header, which contains the navigation menus: Installation, Configuration,
Maintenance, Status and Monitoring.
• A panel which gives the name of the user, the number of connected users, the
NetProcessor 9010 SysName, and a link for the user to logout.
• The body (core) of the page which depends on the context.
• The footer, which provides contextual information, copyright information and
the software version.

3.3 - Setting up the link between the PC and the Web Interface
3.3 - SETTING UP THE LINK BETWEEN THE PC AND THE WEB

INTERFACE
To set up the link between the operating PC and the NetProcessor 9010 Web
Interface, proceed as follows:
1. Connect the PC Ethernet link to the CMD1 connector on the
NetProcessor 9010 rear panel, or to the network connected to this connector.
2. Run the Web Browser on the PC and enter the NetProcessor 9010 IP address in
the URL (factory set address: 10.11.129.107):
Following connection, the Web Interface Login page will be displayed:
Figure 3.21: Login page

3.3 - Setting up the link between the PC and the Web Interface
The login page enables the Operator to be authenticated by the system.
A message indicates whether the browser configuration is optimal. If

this is not the case, you must update your JRE (Java Run
Environment) with the 1.5.0 release which can be found on the
CD-Rom.
3. Provide a user name and a password.

The Web Interface has two predefined user groups: service and operator.
• The service group is for Technicians who are responsible for installation. The
Login and password are respectively: service and service.
• The operator group is for Users who are in charge of operation. The Login and
password are respectively: operator and operator.
Web Interface commands are the same regardless of the user group used.
The Web interface is case sensitive (e.g. service is correct, Service is

not correct).
4. Click on the Login button to confirm.

The Identification page, which is the home page, will be displayed:

3.4 - Identification page
3.4 - IDENTIFICATION PAGE
This page displays NetProcessor 9010’s front and back panels.

You can gain access to information:
• via the LEDs;
• by clicking on the charts;
• via the shortcut commands attached to the charts.
3.4.1 - LEDs
The three LEDs on the front panel indicate alarm severity.
LEDs
Figure 3.23: LEDs on the chassis front panel
Click on the LED chart to directly access the Alarms page.
Figure 3.24: Alarm menu accessed by clicking on the LEDs

3.4.2 - Charts
3.4.2.1 - Clicking on the charts

¤ Chassis chart
Click on the chassis chart to access the factory parameters.
Figure 3.25: Clicking on the chassis
Figure 3.26: Chassis information
¤ Main Board chart

Click on the main board chart to access the factory parameters.
Figure 3.27: Clicking on the main board

Figure 3.28: Main board information
¤ Extension Board chart

Click on the extension board chart to access the factory parameters.

port #1 port #2
Figure 3.29: Clicking on the main board
Figure 3.30: Extension ATM board information

3.4.2.2 - Shortcut commands attached to the charts

port #1 port #2
Figure 3.31: Shortcut commands attached to the charts
The ten DVB-ASI standard TS coaxial ports can be programmed individually as

inputs or outputs via the CLI interface (sasiin command). All output ports are
grouped on the right hand side of the strip.
Arrow direction indicates if the ASI is programmed as input or output

A red arrow indicates that interface is disabled or an alarm is present
on the interface.
Figure 3.32: LEDs and arrows on the interface

¤ ASI IN charts
Figure 3.33: Shortcut commands attached to the ASI IN charts
The Interface setup shortcut command is used to give a name to the input interface,
enable or disable the interface and set the maximum bitrate. For more details, refer
to section “Interface setup menus”, page 171.
Figure 3.34: Interface configuration dialog box for an ASI IN
A green LED will be displayed on the right hand connector when the ASI IN
interface is enabled. If an alarm is raised, this LED will turn red and a new Alarms
command will be displayed in the shortcut menu enabling the Operator to access the
Alarms menu.
¤ ASI OUT charts
Figure 3.35: Shortcut commands attached to the ASI OUT charts
The Interface setup shortcut command is used to give a name to the output
interface, enable or disable the interface, set the TS bitrate and the packet size. For
more details, refer to section “Interface setup menus”, page 171.
Figure 3.36: Interface configuration dialog box for an ASI OUT

¤ ATM charts
Figure 3.37: Shortcut commands attached to the ATM charts
The Interface setup shortcut command is used to give a name to the ATM interface,
enable or disable the interface, set the Clock source (internal or recovered), set
OAM activity and set STM1 or STS3c mode for SDH/SONET or Direct mapping:
for PDH E3 or DS3 mode or PLCP C-Bit parity (G804) for DS3 mode. For more
details, refer to section “Interface setup menus”, page 171.
Figure 3.38: Interface configuration dialog box for an ATM extension board

The ATM RX list shortcut command is used to show and edit the activity, VPI, VCI
and FEC of the existing ATM connections.
Figure 3.39: RX list for an ATM extension board
The ATM TX list shortcut command is used to show and edit the activity, VPI, VCI,
FEC and bitrates of the existing ATM connections. For more details, refer to section
“Rx and Tx setup menus”, page 181.
Figure 3.40: TX list for an ATM extension board

The In-Band C&C setup shortcut command is used to set the In-Band connection
parameters. For more details, refer to section “In-Band Control & Command over
ATM setup menu”, page 163.
Figure 3.41: In-Band C&C setup with an ATM extension board

The Network ports counters shortcut command is used to consult ATM port
information and statistics. For more details, refer to section “Network port counters
page”, page 232.
Figure 3.42: ATM port information and statistics
A green LED will be displayed on the right hand side connector when the ATM
interface is enabled. If an alarm is raised, this LED will turn red and a new Alarms
command will be displayed in the shortcut menu enabling the Operator to access the
Alarms menu.

¤ LAN/WAN charts
Figure 3.43: Shortcut commands attached to the LAN/WAN charts
The Interface setup shortcut command is used to give a name to the LAN/WAN
interface, enable or disable the interface when the interface has a nominal status,
enable or disable the interface when the interface has a backup status, set the
interface speed/mode, set the IP parameters (address and netmask), enable or
disable the traffic shaping, set the output bitrate and configure the static routing or
dynamic IP routing. For more details, refer to section “Interface setup menus”,
page 171.
Figure 3.44: Interface configuration dialog box for LAN/WAN interface

The IP RX list shortcut command is used to give a name to the IP stream, set the
activity, select the port (LAN/WAN1 or LAN/WAN2), set the Multicast IP address
and UDP port, select the decapsulation scheme (MPEG/RTP/UDP/IP or
MPEG/UDP/IP), enable or disable the FEC, set the Requested IPDV Tolerance and
Reordering Tolerance, enable or disable a fixed rate for reception and set the fixed
rate value. For more details, refer to section “IP Rx and IP Tx setup menus”,
page 186.
Figure 3.45: RX list for LAN/WAN interface

The IP TX list shortcut command is used to give a name to the IP stream, set the
activity, select the port (LAN/WAN1 or LAN/WAN2), set the address parameters
(IP address and UDP port, Use ARP, Destination MAC address, Source IP address),
set the QoS parameters (TOS, Diffserv label, QOS tagging, User Priority), set the
VLAN ID, select the encapsulation scheme (MPEG/RTP/UDP/IP or
MPEG/UDP/IP), select the number of MPEG packets per IP frame, set the output
bitrate, enable or disable FEC and set FEC parameters. For more details, refer to
section “IP Rx and IP Tx setup menus”, page 186.
Figure 3.46: TX list for LAN/WAN interface

The Network ports counters shortcut command is used to consult IP port

information and statistics. For more details, refer to section “Network port counters
page”, page 232.
WAN port counters
Figure 3.47: IP WAN port information and statistics

¤ EXT_1 chart
Figure 3.48: Shortcut commands attached to the EXT_1 chart
The Interface setup shortcut command is used to give a name to the port, enable or
disable the port and select the Interface speed/mode.
For more details, refer to section “Extension port dialog box”, page 167.
Figure 3.49: Extension 1 port dialog box

The Data service shortcut command is used to select a data link (only one can be
active at a time), give a name to the link, enable or disable the link and set the ATM
connection parameters for this link (VCI, VPI, selected port).
For more details, refer to section “Data service dialog box”, page 167.
Figure 3.50: Data service dialog boxes

3.5 - Installation menu
3.5 - INSTALLATION MENU
Figure 3.51: Shortcut commands attached to the Installation main menu
The Identification shortcut command is used to display the Identification page

(which is the home page) where NetProcessor’s front and back panels are visible.
For general information, refer to section “Identification page”, page 147.

In-Band Control and Command over ATM and Data service over ATM can be
accessed from the front panel view and are described in the following sections.

3.5.1 - In-Band Control & Command over ATM setup menu
Figure 3.53: ATM In-Band C&C shortcut menus in the Edit configuration main window

The In-Band C&C setup menu is used to set In-Band connection parameters, i.e.
the IP routing parameters (in the Global settings sub-panel) and the link parameters
Activity, VPI, VCI, Netmask, Local IP and Remote IP (in the Links list sub-panel)
.
¤ Global settings sub-panel

Global setup (IP routing)
Up to four IP static routes (Destination address, Subnet mask and Gateway

address) can be entered here. They can be used whether ATM in-band is used or
not.
¤ Links list sub-panel

Links list
Check the Edit box to the right of the corresponding row in the ATM Control
In-Band list window.

The following dialog dialog box will be displayed:
Figure 3.56: ATM Control In-Band setup dialog box
Label, Activity, Selected port, VPI, VCI

Description of the ATM VCC channel to be used as a
connection for data where 0 ≤ VPI ≤ 255 and
32 ≤ VCI ≤ 63.
Local IP IP address of the product over the ATM IP subnet. The
subnet mask is Netmask.
Remote IP IP address of the remote ATM device over the ATM IP
subnet (another NetProcessor, a router or a PC).
Rate The maximum data rate is configurable. It is recommended
to set the data rate in the range of 0.1 to 2 Mbit/s.
Nevertheless, the data rate can be set up to 20 Mbit/s but
high data rate on this service can noticeably slow down
product configuration time.
CMD1, CMD2, LAN/WAN1, LAN/WAN2, and the two IP over

ATM interfaces are all IP interfaces of the product and are mapped on
a unique IP stack. Any overlap between the 6 IP subnets can disable
access to the product.
IP over ATM setup requires a clear IP subnetting strategy. All paths

must be explicitly routed (both ways!). Remember to enter routes on
other hosts as well.

3.5.2 - Data service over ATM menus
Data service menus are the Extension port setup menu and Data service setup
menu, which are accessible from the shortcut menu attached to the Extension_1
port on the Identification page.
Figure 3.57: Extension Port 1 setup and Data service setup dialog boxes
in the Identification page

¤ Extension port dialog box
Figure 3.58: Extension 1 port dialog box
Physical port label A name can be given to the port. It will be used to identify
the port for alarms or monitoring. If left empty, the interface
will be identified as the Extension port#1 default value.
Enabled The port can be enabled/disabled. If disabled, the port will
not send any streams, but its settings are maintained within
the current configuration.
Interface speed/mode You are advised to leave speed and mode as negotiated.
¤ Data service dialog box
Figure 3.59: Data service dialog box

In the Global setup area,

Data service mode Choice between None and Data over ATM.
Rate is simply regulated according to ATM settings.
In the ATM links list area, two data links are proposed but only one can be active at
any time.
To edit or change the parameters of an ATM link used for the data service, check the
Edit box to the right of the corresponding row on the ATM links list window.
Figure 3.60: Data service dialog box
Set the connection parameters as usual (see “ATM Rx and ATM Tx setup menus”,
page 182).
1. Traffic contract is UBR and peak rate is set to enable carriage of

the selected Ethernet rate (when frame size equals MTU).
2. Possible values for VPI and VCI are: 0 ≤ VPI ≤ 255 and
32 ≤ VCI ≤ 63).

3.6 - Configuration menu
3.6 - CONFIGURATION MENU
Figure 3.61: Shortcut commands attached to the Configuration bar menu
The Configuration menu gives access to the following features:

• Top view;
• Connection list;
• Stored configurations.

3.6.1 - Top view menus
The Top view shortcut command displays the Top view main window:
Figure 3.62: Top View main window
The Operator can perform the following operations via this window:
• Set all input and output interface parameters (see section “Interface setup
menus”, page 171);
• View/Set Rx and Tx connections (see section “Rx and Tx setup menus”,
page 181).
• View/Set internal TS routing (see section “Connection list”, page 197);
• Set Input Transport Stream Redundancy (see section “Input Transport Stream
Redundancy”, page 202);
• Set the alarms threshold for early IP network degradation signaling (see section
“Alarm setup for early IP network degradation signaling”, page 216);
• Get ATM and Gigabit Ethernet port statistics (see section “Network port
counters page”, page 232).

3.6.1.1 - Interface setup menus

the same dialog box

the same dialog box
Figure 3.63: Interface setup shortcut menus in the Top View main window

3.6.1.1.1 - ASI setup dialog boxes
The ten DVB-ASI standard TS coaxial ports can be programmed

individually as inputs or outputs via the CLI interface (sasiin
command). All output ports are grouped on the right hand side of the
strip.
Arrow direction indicates if the ASI is programmed as input or output.

A red arrow indicates that interface is disabled or an alarm is present
on the interface.
¤ ASI In setup dialog box
Figure 3.64: ASI In setup dialog box
Label A name can be given to the interface. It will be used to

identify the port for alarms or monitoring. If left empty, the
interface will be identified as the ASI In x default value.
Enabled The interface can be enabled/disabled. A disabled interface
will not be able to send or receive any streams.
Maximum bit rate If the bitrate exceeds the limit, NetProcessor 9010 will
generate an alarm and stop the service in question in the
output flow.

¤ ASI Out setup dialog box
Figure 3.65: ASI Out setup dialog box

interface will be identified as the ASI Out x default value.
Packet size The packets feature 188 or 188 + 16 bytes. In the second
case, 16 additional bytes of random value are included for
the Reed-Solomon error-correcting code inserted by the
modulators.
3.6.1.1.2 - ATM setup dialog boxes
The interface setup menu can be accessed either on the "input side" or the "output
side" of the Top view.
same shortcut
same shortcut
input side output side
Figure 3.66: Two ways of accessing the ATM#x port setup dialog box
The Port ATM # x Setup shortcut command will display the following dialog box:

Figure 3.67: ATM Port setup dialog box (Basic page)
Figure 3.68: ATM Port setup dialog box (Advanced page)
All the standard ATM interface parameters can be set through the Basic dialog
boxes: naming the interface, enabling/disabling the interface, selecting the clock
source, enabling or disabling OAM activity and selecting SDH or PDH framing
mode.
interface will be identified as the Port ATM In 1 or Port
ATM In 2 default value.
Clock Source Choice between Internal and Recovered.
Internal: transmit clock is derived from a + 20ppm local
oscillator.
Recovered: transmit clock is derived from the received
signal. This must be used when connected to an ADM (Add
and Drop Multiplexer).
OAM Activity Choice between Yes and No.
Yes: far end received failure/block error bits are managed.
This should be used with a duplex connection to an ADM or
a switch.
No: far end received failure/block error bits are not set in
transmitted SDH frame overheads. This must be used when

interconnection is one way only to avoid alarm detection on

the facing device.
Mode Framing mode.
For the SDH interface, there is a choice between:
STM1: regular STM1 frame.
STS3c: Sonet frame. This setting must be used when
NetProcessor 9010 is connected to a Sonet network. If you
do not know which type of frame is required, choose STS3c.
For the PDH interface, there is a choice between:
Direct mapping: applicable to E3 or DS3 mode.
PLCP C-Bit parity (G804): applicable to DS3 mode as per
ITU-T G804.
The Advanced dialog box gives access to non standard ATM settings.
Loopback mode Keep this parameter value at its default value (Normal - No
loopback) except if you want to prevent unwanted alarms on
an ATM PDH Tx only interface:
Scrambling Unless you know and master this setting, keep this
parameter value at its default value (Yes).
Cosset Unless you know and master this setting, keep this
parameter value at its default value (Yes).

3.6.1.1.3 - IP setup dialog boxes
The interface setup menu can be accessed either on the "input side" or the "output
side" of the Top view.
input side output side
same shortcut
same shortcut
Figure 3.69: Two ways of accessing the LAN/WAN port x setup dialog box
The LAN/WAN port # x shortcut command will display the following dialog box:
Figure 3.70: Interface configuration dialog box for LAN/WAN interface
First page Basic

Physical port label A name can be given to the interface. It will be used to

interface will be identified as the LAN/WAN1 or

LAN/WAN2 default value.
Operation status and Interface nominal status
When NetProcessor 9010 is set to active (nominal) mode,
this LAN/WAN interface can be enabled/disabled via this
command. A disabled interface will not be able to send or
receive any streams.
Interface backup status
When NetProcessor 9010 is set to standby mode (after a
switchover for system redundancy purposes), this
LAN/WAN interface can be left unchanged (enabled) or
disabled using this command, depending on Operator
preference.
Interface speed/mode, IP address and Netmask
These are standard IP device parameters. You are advised to
leave speed mode as negotiated. Set your IP subnet
carefully. These ports and also CMD ports must be part of
different IP subnets, without overlap.
IGMP protocol handling
In multicast mode, NetProcessor will automatically manage
IGMP join and leave for seamless operation in real scale IP
networks. The Operator chooses which type of IGMP
protocol should be used by NetProcessor:
• IGMPv2,
• IGMPv3 partial with no source control.
• IGMPv3 with SSM (Source Specific Multicast which is an
IP technology where the destination host can select a source
when joining a multicast group).
Setting the proper IGMP version is recommended as it
speeds up NetProcessor start time. If detected network
capabilities are below the level set by the Operator (e.g. the
network is using IGMPv2 while IGMPv3 is selected),
NetProcessor automatically falls back to the network
supported version of IGMP.
Shaping and Maximum output bitrate
Shaping can be applied at output to prevent any network
overload. This is useful when you know that there is a fixed
rate limitation in the network after NetProcessor 9010,

below the directly visible line rate. Leave shaping disabled

in any other case.
There is no configuration associated with the SFP module. The port will
automatically use SFP when a module is detected AND RJ45 is left unconnected. If
both are connected, the RJ45 attachment has priority over the SFP.
SFP are 1000Base-X and compatible with auto-negotiation and 1000Mbps Full
Duplex speed modes only.
The second page, Routing, is used to select the dynamic routing protocol and to set
up to 4 static routing entries.
Figure 3.71: Routing setup dialog box (Routing page)
Dynamic IP routing NetProcessor 9010 supports RIPv2 and OSPF as dynamic

routing protocols. Leave as None if no dynamic routing
protocol is used.
Static IP routing Up to 4 static routes can be entered. NetProcessor 9010 will
only accept gateways that are directly reachable via the
Gigabit Ethernet port (i.e. gateway address must belong to
the port IP subnet). To clear a route entry, clear each of the 3
fields and apply.
The third page, RIPv2, is only visible if the RIPv2 dynamic routing protocol is
selected on the Routing Page.

Figure 3.72: Routing setup dialog box (RIPv2 page)
This page is used to set the following RIPv2 routing protocol parameters:
• Route Update frequency,
• Route disable Time out,
• Route Garbage Time Out,
• Authentication mode (None, Text, MD5),
• Password,
• MD5 key id (Secret key used to encrypt passwords through MD5. This field is
only available if MD5 mode is selected).
Refer to RFC 2453 for an explanation of these fields.

The fourth page, OSPF, is only visible if the OSPF dynamic routing protocol is
selected on the Routing Page.
Figure 3.73: Routing setup dialog box (OSPF page)
This page is used to set the following OSPF routing protocol parameters:
• Area
• Stub area
• Hello Generation Frequency
• Route Disable Time Out
• Authentication mode (None, Text, MD5 Key)
• Password,
• MD5 key id (Secret key used to encrypt passwords through MD5. This field is
only available if MD5 mode is selected).
Refer to RFC 2328 for an explanation of these fields.

3.6.1.2 - Rx and Tx setup menus
via the ATM Rx list, ATM Tx list and IP Rx list, IP Tx list views

3.6.1.2.1 - ATM Rx and ATM Tx setup menus
Figure 3.75: ATM Rx and Tx setup shortcut menus

in the Edit configuration main window
¤ ATM Rx list and ATM Rx setup dialog box
Figure 3.76: ATM Rx list
To change the parameters of an existing ATM connection, check the Edit box to the
right of the corresponding row in the ATM RX list window.

To add a new ATM connection, use the Add a new Rx link at the bottom of the same
list. MPEG over ATM adaptation provides:
• simultaneous emission of up to 4 MPEG streams and reception of up to 4 MPEG
streams with the N901PDH0GA E3/DS3 interface board.
• simultaneous emission of up to N MPEG streams and reception of up to (10-N)
MPEG streams with the N901STMFGA interface board. The total number of
transmitted and received MPEG streams may also be limited by the software
option installed in the device.
In all cases, the following ATM RX setup dialog box will be displayed:
Figure 3.77: ATM RX setup dialog box
Label A name can be given to the channel. It will be used to

interface will be identified as the ATM RX default
value.
Activity The channel can be enabled/disabled. A disabled channel
will not extract any streams, but its settings are maintained
within the current configuration.
Selected port Choose which port should be used for streaming. Avoid
leaving Port set to None for an enabled channel.
VPI The authorised range is 0 to 255.
VCI The authorised range is 32 to 65535.
FEC Select Yes if you want to use error correction.

¤ ATM Tx list and ATM Tx setup dialog box
Figure 3.78: ATM TX dialog box
To change the parameters of an existing ATM connection, check the Edit box to the
right of the corresponding row in the ATM TX list window.
To add a new ATM connection, use the Add a new Tx link at the bottom of the same
list. The following ATM TX setup dialog box will be displayed:
Figure 3.79: ATM Tx dialog box

interface will be identified as the ATM TX default
value.
will not send any streams, but its settings are maintained

VPI The authorised range is 0 to 255.

VCI The authorised range is 32 to 65535.
FEC Select Yes if you want to use error correction.
Rate Enter the Transport Stream rate. This rate is used to set up
the internal ATM cell rate shaper. ATM rate is computed
from the TS rate and FEC usage using the following
formula:
ATMrate(cell/s) = INT[1.00002*MPEGrate(kb/s)*(1+accuracy)*AALcoeff+23]
where AALcoeff = 2.659557447 without FEC or 2.74536720 with FEC and
accuracy is MPEGrate accuracy (recommended value: 50.10-6).
MPEGrate must be in 188 byte format. With 188+16 byte format, the total TS rate
must be corrected by the 188/204 factor before calculation.
Maximum per service TS Rate varies with network interface settings and FEC
usage:
TS packet/s 188 rate (Mb/s) 188+16 rate (Mb/s)
SDH with FEC 85535 128,64 139,59
without 88105 132,51 143,79
E3 with FEC 19195 28,87 31,33
without 19815 29,80 32,34
DS3 with FEC 25070 37,71 40,91
direct without 25880 38,92 42,24
DS3 with FEC 23070 34,70 37,65
plcp without 23815 35,82 38,87
second, i.e. 1.5 Mb/s for 188-byte format or 1.7 Mb/s for (188 + 16) byte format.

second, i.e. 91 kb/s for 188-byte format or 98 kb/s for (188 + 16) byte
format.

3.6.1.2.2 - IP Rx and IP Tx setup menus
Figure 3.80: IP Rx and Tx setup shortcut menus

in the Top view main window

¤ IP Rx list and IP Rx setup dialog box
Figure 3.81: IP Rx list
To change the parameters of an existing IP connection, check the Edit box to the
right of the corresponding row in the IP RX list window.
To add a new IP connection, use the Add a new Rx link at the bottom of the same
list. Up to 20 RX and 20 TX connections can be activated simultaneously. This can
be limited by software option setting.
In both cases, the following IP RX setup dialog box will be displayed:
Figure 3.82: IP RX setup dialog box (Transport layer page)

interface will be identified as the IP RX default value.


will not extract any streams, but its settings are maintained
Multicast destination IP address
In unicast mode, the destination IP address should be left
empty. NetProcessor 9010 will automatically use the
selected native port address in that case. In multicast mode,
the multicast IP address has to be entered.
NetProcessor 9010 will automatically manage IGMP join
and leave for seamless operation in real scale IP networks.
Source IP address Enter a Source IP address for secure or backup operation.
When an IGMPv3 environment is selected and detected
(see IGMP protocol handling, page 177), Source Specific
Multicast is used for each stream that has been set by the
Operator with a source IP address (Source Specific
Multicast is an IP technology where the destination host can
select a source when joining a multicast group enabling
NetProcessor to switch to a designated backup source).
When an IGMPv2 environment is selected and detected,
(see IGMP protocol handling, page 177), the source IP
address can be set but has a different meaning. When set, the
NetProcessor will activate a filter to reject frames coming
from unexpected sources, while IGMP join/leave are of any
source type.
Reception UDP port The Reception UDP port enables stream discrimination.
Remember that RTP standard usage uses 4 contiguous UDP
port numbers, this one being the first. You are also advised
to start from port 49152 to avoid conflict with any standard
protocol-allocated port numbers. It is good practice to
always use a +6 increment (or +10 for readability).

Figure 3.83: IP RX setup dialog box (Transport layer page)
RX Decapsulation Selection of the decapsulation scheme between

MPEG/UDP/IP and MPEG/RTP/UDP/IP. Otherwise, the
receiver automatically adapts to the received frame length.
RX FEC module To be set to Enable if FEC usage is required. No other
parameter is required, as the receiver automatically adapts
to the received FEC scheme.
Requested IPDV Tolerance....At nominal rate
The Jitter removal buffer is sized from entered IPDV
tolerance and rate. The Buffer is sized to cope with set IPDV
at the set rate. Rate does not have to perfectly match the
actual received signal rate but should not be underestimated
(risk of overflow) or overestimated (because of excessive
delay).
Reordering Tolerance The Reordering tolerance default setting is ten RTP frames,
but it can be adjusted when FEC error correction is disabled,
within the range 0 to 128. When set to 0 or 1,
NetProcessor 9010 handles out of order frames as lost
frames. Of course, reordering cannot be performed on pure
UDP streams. When FEC error correction is enabled, the
reordering process is able to recover any ordering within a
window of FEC matrix plus 10 frames.
When the IP Rx threshold alarm feature is

enabled (see page 216), RTP reordering will
be set to the threshold or configured
reordering value, whichever is the highest.

Fixed rate and Fixed rate value

As the TS rate recovery mechanism uses PCR present in the
TS, some streams that do not include any PCR, e.g. some
pure DVB-H streams will not be recovered. That is why this
field has been implemented. In Fixed rate mode, received
TS is expected to be within + 30 ppm of the entered nominal
rate.
The Advanced page is not used with NetProcessor 9010.
¤ IP Tx list and IP Tx setup dialog box
Figure 3.84: IP TX list
To change the parameters of an existing IP connection, check the Edit box on the
right of the corresponding row in the IP TX list window.
To add a new IP connection, use the Add a new Tx link at the bottom of the same
list. This can be limited by software option setting.
In both cases, the following IP TX setup dialog box will be displayed:

The Transport Layer tab provides mandatory information to configure the

interface.
Figure 3.85: IP Tx setup dialog box (Transport layer)

interface will be identified by the IP TX default value.
will not send any streams, but its settings will be maintained
leaving the Port set to None for an enabled channel.
Destination IP address
This field sets the destination IP address for transmitted
MPEG frames. Possible values are 0.0.0.0 to
255.255.255.255.
For unicast transmission, the IP address must be the native
port address of the receiver.

For multicast transmission, IP addresses range from

224.0.0.0 to 239.255.255.255, or, equivalently, 224.0.0.0/4.
Address assignments from within this range are specified in
the IETF 'best current practice' document also known as
RFC 3171.
Destination UDP port This parameter enables stream discrimination. Reminder:
standard RTP usage is based on 4 contiguous UDP port
numbers, this one being the first. You are also recommended
to start from port 49152 to avoid conflict with any standard
protocol-allocated port numbers. It is good practice to
always use a +6 increment (or +10 for readability).
Source IP address Leave the Source IP address field empty for normal
operation. NetProcessor will automatically insert the
selected port’s native address in this case. This field can
only be used for some redundancy schemes and should be
used carefully.
In the Expert parameters area
Use ARP This parameter is normally enabled.
Destination MAC address
The MAC address entry is ignored when Use ARP is
enabled.
Other fields (TOS/DiffServ, TTL for MPEG IP datagrams, QoS Tagging, VLAN Id,
User Priority) are standard fields that can be changed for fine network usage tuning.

The Adaptation Layer tab provides basic adaptation settings and FEC settings.
Figure 3.86: IP Tx setup dialog box (Adaptation layer)

¤ Basic settings
TX Encapsulation Choice between MPEG/UDP/IP and MPEG/RTP/UDP/IP.
MPEG packets per IP frame
Choice from 1 to 7.
Parameters governing frame length shall not be changed on an

active IP Tx Channel.
The number of packets per frame can be set from 1 to 7, framing can
be either set to RTP/UDP or pure UDP. Changing any of these set-
tings on an active transmission can block all MPEGoIP transmis-
sions.
Workaround: Select frame length before activating a transmission. If
blocked, change all IP Tx activity to Off, then reboot
NetProcessor 9010 and set Tx activity back to On.
Max TS output rate TS output rate is used to define IP traffic shaping on the
transmitted stream. It must be set to a rate slightly higher
than nominal conveyed MPEG2 rate. Generated traffic
regularity is better when the rate is closer to the actual rate.
When the optimum (i.e. minimum) margin cannot be
accurately estimated, a margin of +100ppm will be a very
good compromise. A minimum rate margin will include:
• Source rate inaccuracy,
• Provision for transients.
Null packet discard This field is not used with NetProcessor 9010.
¤ FEC settings
TX FEC module FEC on IP TX streams can be enabled/disabled.
Two FEC programming modes are available when FEC is
enabled: IPLR <1e-6 and Expert.
FEC operation is described below.
Configuring column 2D FEC using the quick mode (i.e., IPLR <1e-6 mode)
1. Select IPLR <1e-6 programming mode.
2. Adjust the burst tolerance L and column depth D. Correction capacity is up to L
consecutive lost frames every L*D. Overhead decreases when D increases. A
good compromise is to choose L=D=10 square matrix (10% overhead). If this
setting does not provide enough robustness, L should be increased: L=20, D=5
is suggested (20% overhead).

Configuring column 2D FEC using the expert mode:

1. Select Expert programming mode.
2. Adjust the burst tolerance L.
3. Adjust Column FEC interleaving as follows:
Row FEC are generated regularly without creating IP traffic burst, but column FEC
can only be computed at the end of a matrix. This creates a traffic burst (2L frames
at doubled rate). To avoid such a burst, NetProcessor sends Column FEC frames
every N TS frames.
To obtain perfectly smooth traffic, select D interleaving. It means N=D and the
column FEC frames are periodically sent over the entire next matrix. This
introduces a latency of one matrix (L*D frames).
If latency is critical and the network link is sufficiently oversized to cope with
bursts, the Operator can set a smaller N value.
1. Select Custom interleaving (recommended configuration).
2. Enter the custom N value (from 1 to D). Latency is reduced to L*D frames. But
a burst rate provision is required on the link.
Configuring line+column 2D FEC using the expert mode:
2. Adjust the burst tolerance L and column depth D. Correction capacity is up to L
consecutive lost frames every L*D. Overhead decreases when D increases. A
good compromise is to choose L=D=10 square matrix (20% overhead). If this
setting does not provide enough robustness L should be increased: L=20, D=5
is suggested (25% overhead).
L' is usually chosen to equal L (overhead figures are given based on this).
NetProcessor accepts any L' value that divides the matrix size (L*D). If L'<L,
overhead is increased. If L'>L, overhead is decreased but correction capacity is
decreased.
Configuring line 1D FEC using the expert mode:
2. Set the burst tolerance L to 0.
3. Set L' to select overhead and thus correction capacity. One protection parity
frame is generated every L' MPEG frame.

This mode enables light protection (5% overhead with L'=20) that can be sufficient
on a link with very good QOS performance.
Expert parameter settings
Expert parameters are standard parameters (TOS/DiffServ and TTL for FEC IP
datagrams) that can be changed for fine network usage tuning.

3.6.1.3 - Patch panel
Figure 3.87: Patch panel
The following commands are available in the patch panel:

- Connection list
- Redundancy
- Alarm setup
These commands are described in the following sections.
3.6.1.3.1 - Connection list
The Operator can create/edit/delete internal TS connections to send TSs from ASI,
ATM and Gigabit Ethernet interfaces to other interfaces. These operations are
performed in the Connection list window, accessible via the Connection list
command in the Patch panel or via the Connection list command in the menu bar.


¤ Connection management in Direct mode

Direct mode stands for basic operation, i.e. without Input TS redundancy.
When there are still outputs available for connection, a New connection panel is
displayed below the connections list. It can be used to create a new connection, or to
append a new connection to an existing one.
Edit button is not used in Direct mode
New connection panel is displayed when there are still ouputs

available for connection
This panel is not displayed when all outputs of a NetProcessor are used.

¤ Creating a new connection
Figure 3.89: Creating a new connection
1. To create a connection, select an Output in the unused Output drop-down list;

2. Select Create connection in the Action drop-down list;
3. Select an Input in the available Input Drop-down list;
4. Click on Apply.
If no input is available, it means that this input is already used in a connection. Use
the Append connection action instead.
¤ Appending to connection
Figure 3.90: Appending to connection
To set a connection with an input already used in a connection, proceed as follows:

1. Select an Output in the unused Output drop-down list;
2. Select Append to connection in the Action drop-down list;
3. Select an Original connection output in the used Outputs drop-down list;
4. Click on Apply.
Drop-down lists only propose coherent entries.

¤ Deleting a connection
Connection deletion is explicit with the Remove button.
Figure 3.91: Deleting a connection
The Operator will be asked for confirmation prior to connection removal.

¤ Other features
1. By clicking on the input label or output label in this dialog box, you will gain
access to the associated ASI interface or Rx or Tx setup dialog box (described
in sections “Interface setup menus”, page 171 and “Rx and Tx setup menus”,
page 181).
Figure 3.92: Access to the interface setup dialog box

(here, ASI IN and ATM Tx setups)
2. The Edit button is not used in Direct mode.

3.6.1.3.2 - Input Transport Stream Redundancy
¤ Overview
by the Operator).
• Redundancy holdover is set to infinite for non-revertive automatic mode
• Redundancy holdover can be adjusted to 10, 30 or 60 seconds for revertive
automatic mode.

¤ Flowchart
The following flowchart shows how to set manual and automatic input TS
redundancy and all possible switching operations.
Figure 3.96: Redundancy flowchart (enabling redundancy)

Figure 3.97: Redundancy flowchart (Creating a protected connection)

Figure 3.98: Redundancy flowchart (duplicating a protected connection)

Figure 3.99: Redundancy flowchart (Switching operations)
The detailed procedure is given in the following sections.

¤ Enabling input TS redundancy and setting triggers and holdover for

automatic input TS redundancy
Proceed as follows:
1. Select the Redundancy shortcut command in the Top view panel.
Figure 3.100: (Input TS) Redundancy shortcut command
A dialog box comprising 4 pages is displayed.
Figure 3.101: (Input TS) Redundancy dialog box
• For manual redundancy, only the Automatic redundancy switching line in the
first page will be used. It must be set to Active to enable the input TS redundancy
feature.

• For automatic redundancy, triggers should be also be set. Set the MPEG, IP
triggers and ATM triggers before activating redundancy as indicated hereafter.
¤ ATM triggers page
Figure 3.102: ATM triggers for redundancy
For ATM triggers, select Used on Uncorrected errors if you want an automatic
switch at the first non corrected error bit. Select Not used in other cases. This is
evaluated after error correction.
¤ IP triggers page
Figure 3.103: IP triggers for redundancy
For IP triggers,
1. Select Used on Uncorrected errors if you want an automatic switch at the first
non corrected error bit. Select Not used in other cases. This is evaluated after
error correction.

2. Select Used on Signal degrade if you want an automatic switch based on loss
evaluation before correction. Select Not used in other cases. The Signal
degrade alarm is explained in section “Alarm setup for early IP network
degradation signaling”, page 216.
¤ MPEG triggers page
Figure 3.104: MPEG triggers for redundancy
For MPEG triggers, select Used on PAT errors and on PMT errors if you want an
automatic switch based on SI presence. These errors are raised by a NetProcessor
9010 only if selected as triggers. MPEG triggering applies to either ASI, ATM or IP
streams.
Now redundancy switching can be activated and configured in the Redundancy
switching page.
¤ Redundancy switching page
In this page, one of the following three (global) modes can be selected:
• No redundancy (Automatic redundancy switching must be set to Inactive);
• Revertive Redundancy (Automatic redundancy switching must be set to Active
and connection goes back to nominal after a "holdover" period of time. The
"holdover" period of time is the time for a nominal to be continuously OK before
switching back from backup). Redundancy holdover can be set to 10 s, 30 s or
60 s;
• Non-revertive redundancy (Automatic redundancy switching must be set to
Active and connection never goes back to nominal, as Redundancy holdover is
set to infinite).

Figure 3.105: Redundancy switching
1. Set Redundancy holdover to Infinite if you want non-revertive mode. In other

cases you can adjust holdover to 10, 30 or 60 seconds.
2. Set Automatic redundancy switching to Active. Going back to Inactive will
inactivate redundancy, connect all nominal inputs, and clear switches from
configuration.

¤ Creating protected connections

Connection are created in the Connections list window.
Create new
connections
Edit manual
switch

The New connection form can be used to create a direct connection or a protected
connection with manual or automatic switching.
Figure 3.106: Creating protected connections
1. Select one available Output in the Output drop-down list.

2. Select Create connection in the Action drop-down list.
In the Connection properties area,
3. Select as Connection mode:
- Direct for a non-protected connection,
- Auto switch for a protected connection with automatic switching,
- Manual switch for a protected connection with manual switching.
4. If the connection is Direct, select Input in the drop-down list, otherwise select
the First input and the Second input. Only unused inputs are proposed in the
drop-down list.
5. Select which of the two inputs should be the Nominal input.
6. Click on Apply.
The new connection appears in the list at the top of the Connection page.

¤ Duplicating a protected output
Figure 3.107: Duplicating a protected output
1. Select one available Output in the Output drop-down list.

2. Select Append to connection in the Action drop-down list.
3. Select the Original connection output, i.e. the replicated output selected in the
used Output drop-down list.
4. Click on Apply.
The new connection appears in the list at the top of the Connection page.
¤ Connection monitoring
The connection appears in the list at the top of the Connection page.
Direct connections appear with a straight black connector:
Figure 3.108: Connection monitoring for direct connections

Protected connections appear with a graphic representation of the switch:
Figure 3.109: Connection monitoring for protected connections
The nominal input is on the first line.

The backup is on the second line.
The active connection is displayed with a plain line, the inactive with a doted line.
Connector colors vary with Input state:
- Green means input is up,
- Red means input is down,
- Grey means input is disabled.
The list displayed is refreshed every 5 s to give an accurate view of the actual state
of connections.
¤ Redundancy operations (manual mode)
When the mode is automatic, access to connection edition is locked.
To force an input, you must select the Set to manual switch shortcut command in
the menu which appears when focus is on Mode.
Figure 3.110: Force an Input to Manual mode
You will be asked for confirmation.

Setting to manual will change the nominal input to the currently active input and
stop the automat. Thus connections are left unchanged.

In Manual mode, the connection can be edited to change the nominal (thus toggle
inputs) as follows:
Click on the Edit button attached to the 1+1 redundancy group in the Edit
configuration page.
Edit
Figure 3.111: Edit connection to change the nominal input
Figure 3.112: Connection setup dialog box
Select the Nominal input.

When Connection mode is set to Manual switch, the nominal input is selected to go
through when clicking on Apply.
When Connection mode is changed to Auto switch, the nominal input is selected to
go through and the automat is reactivated when clicking on Apply.
The New connection panel in the Edit configuration page can also be used to
modify input selection.
When an output is replicated, connection display is repeated for each output.
Nevertheless, changing the mode will change the mode for all identical outputs and
editing connection will modify inputs for all identical ouputs.

3.6.1.3.3 - Alarm setup for early IP network degradation signaling
A threshold can be set for all IP inputs to raise an alarm with some anticipation of
FEC overflow.
It is evaluated at RTP level, thus it is not available on pure UDP inputs.
The threshold is not based on RTP discontinuity counting, because simple loss rate
estimation will trigger too late (after FEC overflow). The alarm is based on how
many losses are accepted in a reordering window.
Without FEC, the window is explicitly defined.
Warning: for proper operation, if the threshold alarm is active, RTP reordering will
be set to threshold or configured reordering, whichever is the highest.
With FEC, the window is the FEC matrix + ten IP frames.
Configuration of the alarm is accessed in the Patch panel menu:
Figure 3.113: Signal degrade threshold for early IP network degradation signaling
The threshold value is expressed as consecutive lost frames and can be set to the
following values: infinite (infinite means no alarm), 1 loss, 2 losses, 4 losses,
8 losses, 16 losses.
Selection of a Signal degrade threshold value of 1 loss leads to an alarm being
raised for the very first loss.

3.6.2 - Connection list menu
This menu opens the Connection list attached to the Patch panel (refer to section
“Connection list”, page 197).

3.6.3 - Stored configurations command
The Stored configurations shortcut command displays the following Stored

Configurations main window:
Figure 3.114: Access to the Stored Configurations main window
NetProcessor 9010 has 10 built-in memories.

The following commands are available via this menu for managing memories:
• save the current device configuration to any memory;
• export a memory content to a remote PC;
• import a saved configuration from a remote PC;
• apply a saved configuration that will become the current configuration;
• apply an empty configuration;
• delete the content of a memory.
The procedure is described below.

¤ Save the current device configuration to any memory

1. Select the Save active configuration command at the bottom of the Stored
Configuration main window.
Figure 3.115: Save active configuration command
The following dialog box will be displayed.
Figure 3.116: Save active configuration dialog box
2. Select the memory where the configuration will be saved and give a
description.
3. Click on Apply.
The Stored configurations window is updated with the new memory contents.
Figure 3.117: Stored Configurations main window after a save operation

¤ Export a memory content to a remote PC

1. Select the Export command in the Stored Configurations main window to
display the link used to export the configuration.
Export command
Figure 3.118: Export command in the Stored Configurations main window
Figure 3.119: Link used to export the configuration
2. Click on the Configuration x link to display the File Browser.
Figure 3.120: File browser
3. Select the destination folder then click on Save.

¤ Import a saved configuration from a remote PC

1. Select the Import configuration file command at the bottom of the Stored
Configurations main window.
Figure 3.121: Import configuration file command
The following dialog box will be displayed.
Figure 3.122: Load configuration from file dialog box
2. First select the memory where the configuration will be saved then enter the file
name and path using the file Browser.
3. Click on Apply.

¤ Apply a saved configuration that will become the current

configuration
Select the Apply command in the Stored Configurations main window to apply the
content of the selected configuration memory as the current configuration.
Apply command
Figure 3.123: Apply command in the Stored Configurations main window
A configuration file created with the last previous software main

release will be automatically upgraded when applied to active. Active
configuration is the result of conversion and stored configuration is
unchanged. If you want storage to be upgraded you should delete the
configuration slot and then save active configuration back to it.
A configuration file created from the active configuration of another

product that contains more or other hardware options that the actual
one will be rejected.
A configuration file created from the active configuration of another
product that contains less hardware options that the actual one will be
accepted. In that case, the configuration will be automatically
upgraded when applied to active. Use previous method if you want to
save the result of upgrade.

¤ Apply an empty configuration that will become the current

configuration
Select the Apply an empty configuration command at the bottom of the Stored
Configuration main window.
Figure 3.124: Apply an empty configuration command
You will be asked for confirmation prior to the configuration change:
Figure 3.125: Confirmation request before configuration change

¤ Delete the content of a memory

Select the Delete command in the Stored Configurations main window to delete the
content of the selected memory.
Delete command
Figure 3.126: Delete command in the Stored Configurations main window
You will be asked for confirmation prior to configuration removal:
Figure 3.127: Confirmation request before removal

3.7 - Maintenance menu
3.7 - MAINTENANCE MENU
Figure 3.128: Shortcut commands attached to the Maintenance bar menu
The Maintenance menu gives access to the following commands:
3.7.1 - Reboot
The Operator will be asked for confirmation prior to restarting the device.
Figure 3.129: Confirmation request before device restart
Click on Yes or No as required (or Abort to exit without a reboot or Reboot to restart
the equipment).

3.7.2 - Options
A window displays all the options installed in the device.
Figure 3.130: Option list
This list can be exported in text format via the Export options list in a file
command.
Figure 3.131: Exporting the option list

3.7.3 - Global setting
Figure 3.132: Global setting
Time set mode Choice between:

Time set off: NetProcessor 9010 clock is in free-running
mode;
Time set from NTP: NetProcessor 9010 clock is locked to a
NTP server.
NTP server IP address
IP address of the NTP server if Time set from NTP has been
selected in the previous field.
The Time set mode and NTP server IP address parameters are stored
in the current configuration and are not permanent like CLI
parameters. It means that when loading a stored configuration, these
parameters can change according to the content of the loaded
configuration.
The Multiplexer Input field and the Advanced page are not used for
NetProcessor 9010.

3.8 - Status menu
3.8 - STATUS MENU
Figure 3.133: Shortcut commands attached to the Status bar menu
The Status menu gives access to the All Alarms page, Events page and Report page.
3.8.1 - All alarms page
The All alarms page allows the Operator to consult device alarms.
Figure 3.134: All Alarms window
The alarm list is automatically refreshed.

Refer to section 5 to know the meaning of alarms.

3.8 - Status menu
3.8.2 - Events page
Figure 3.135: Events page
The Events page displays the last events raised. Alarm raising is indicated by a
rising arrow. The color indicates alarm severity. Alarm clearance is indicated by a
falling arrow. Non-alarm events are indicated by an info icon. The order can be
sorted by clicking on any column header. The table is automatically refreshed.
This page can be exported in CSV format (Comma-Separated Values) via the
icon in the bottom left corner of the window.
The number of events is indicated in the bottom right corner of the window.

3.8 - Status menu
3.8.3 - Report page
Figure 3.136: Shortcut commands attached to the Monitoring bar menu

with Administrator rights
The Report shortcut command is used to identify a problem by generating a report

containing traces and general information. This report together with the
configuration file and the event file have to be supplied to Customer Services for
faster product support.

3.9 - Monitoring menu
3.9 - MONITORING MENU
Figure 3.137: Shortcut commands attached to the Monitoring bar menu
The Monitoring menu gives access to the Monitoring page and Network port
counters page.
3.9.1 - Monitoring menu
The Monitoring menu allows the Operator to get input and output stream
descriptions: TS, Services, Components with bitrate indication.
To select the stream to monitor, click on the corresponding input/output stream on
the Monitoring page. This will focus on the selected stream, closing the tree of the
previously displayed stream.
Then to display the detail of the selected stream, click on the ''+'' on the node to
expand the view in order to have all information, service per service.
Figure 3.138: Example for an IP Tx output
The window is automatically refreshed.

3.9 - Monitoring menu
3.9.2 - Network port counters page
The Network port counters menu allows the Operator to get ATM and Gigabit
Ethernet port statistics. They include traffic and Errored second counters.
The ATM counters are reset every 15 minutes.
The IP counters are free running.
WAN port counters ATM port counters
Figure 3.139: ATM and Gigabit Ethernet port statistics
The statistics can be exported as text files using the Export info to a file link located
at the bottom of the page.
Refresh the page to refresh the counters.

Chapter 4 - Servicing 233
Chapter 4
Servicing
4.1 - Introduction ........................................................................................ 235
4.2 - Accessing the Command Line Interface .......................................... 236

4.2.1 - Accessing the Command Line Interface ....................................... 236
4.2.2 - Login and password...................................................................... 238
4.3 - Installing software options ................................................................ 240

4.3.1 - Introduction ................................................................................... 240
4.3.2 - Displaying software options (lsopt) ............................................... 240
4.3.3 - Ordering and installing a software option ..................................... 241
4.4 - Downloading software ....................................................................... 244

4.4.1 - Introduction ................................................................................... 244
4.4.2 - Displaying firmware releases (view) ............................................. 245
4.4.3 - Downloading procedure (server, down, view, result, togg)........... 246
4.4.4 - Procedure for returning to the previous software release............. 249
4.4.5 - Upgrade from V2.x to V3.0 ........................................................... 249
4.4.6 - Upgrade a V1.5 Product ............................................................... 249
4.5 - Erasing the configurations................................................................ 250
4.6 - Community strings and access rights ............................................. 251

4.6.1 - Introduction ................................................................................... 251
4.6.1.1 - Accessibility values ...................................................................... 251
4.6.1.2 - Access level values...................................................................... 251
4.6.2 - Community string edition .............................................................. 251
4.7 - Maintenance........................................................................................ 254

4.7.1 - Cleaning chassis ventilation grids................................................. 254
4.7.2 - Replacing the fans ........................................................................ 254
4.7.3 - Replacing a PSU in a chassis with two Power Supply units......... 254
4.7.3.1 - Fault diagnosis............................................................................. 255

234 Chapter 4 - Servicing
4.7.3.2 - Procedure for replacing a PSU..................................................... 255
4.8 - Installing an NTP server under Windows 2000 and Windows XP . 257
4.8.1 - Architecture .................................................................................. 257
4.8.2 - Installation .................................................................................... 258
4.9 - Installing an FTP server under Windows 2000 and Windows XP.. 263
4.9.1 - Installation .................................................................................... 263
4.9.2 - Setting up the server .................................................................... 264

4.1 - Introduction
4.1 - INTRODUCTION
This chapter describes the following servicing operations:

• Accessing the Command Line Interface
• Installing software options (performed via the Command Line Interface);
• Downloading software (performed via the Command Line Interface);
• Erasing the configurations;
• Maintenance;
• Installing an NTP server under Windows 2000 or XP;
• Installing an FTP server under Windows 2000 or XP.

4.2 - Accessing the Command Line Interface
4.2 - ACCESSING THE COMMAND LINE INTERFACE
In the present and following sections the term CLI will be used for Command Line
Interface.
4.2.1 - Accessing the Command Line Interface
CLI can be accessed:

• either via the Ethernet link and the PC Telnet application if the device IP address
is known;
• or via the serial link and the PC hyperterminal application (or any terminal
emulator).
CLI use is the same regardless of the access mode used.
¤ Accessing the CLI via the Ethernet link
The CLI is accessed via the Telnet application installed on the PC.
The NetProcessor 9010 IP address which is required for Telnet connection is the
last entered value for the CMD1 interface.
As NetProcessor 9010 CMD1 Ethernet interface hosts an autocrossover
mechanism, you can use direct or crossed cable for connection between the PC and
NetProcessor 9010.

The Telnet application must be set up with the following parameters:
Terminal options No local echo

Block cursor
no CR LF
Emulation VT100 / ANSI
Set up the Telnet connection between the PC and NetProcessor 9010;
Figure 4.1: Command Line
A welcome page will be displayed asking login and password.

¤ Accessing the CLI via the serial link
The CLI is accessed via a serial link between NetProcessor 9010 and a terminal or a
PC emulating a terminal.
• Connect the terminal (or the PC emulating a terminal) to the NetProcessor 9010
RJ45 connector via an RS232 to Ethernet adapter cable.
- The RJ45 pinout on NetProcessor 9010 is:
8 1
- The RJ45-SubD9 female adapter cable wiring is:

• Set up the terminal port as follows: 8 bits, 1 start, 1 stop, no parity, no flow
control, 9600 bauds;
Figure 4.2: Terminal port setup for accessing the Local Console
Click on OK to set up the connection between the PC and NetProcessor 9010.

A welcome page will be displayed asking login and password.
4.2.2 - Login and password
The welcome page displayed after connection asks for the user login and password.
For servicing operations, you must use service and service as the login and
password respectively.
1. In the current release, you must proceed as follows to log in as

service:
• Log in as operator (with login and password: operator and
operator);
• Type user
• Enter service and service for the login and password
2. CLI is case sensitive (service is correct, Service is not correct).

The CLI provides many commands. Some of these commands are

not, however, intended for the device user but reserved for Thomson
use only. It is therefore important to only use the commands
described in this manual so as not to disrupt device operation or jam
the device, as this would require assistance from Thomson Customer
Services.

4.3 - Installing software options
4.3 - INSTALLING SOFTWARE OPTIONS
The operations described in this section are performed using the Command Line
Interface.
The purpose of this section is to explain the procedures for displaying device
software option status and for ordering and installing a software option.
If the options are ordered with the product, they will be installed in-
factory and will be available to the operator straight away.
4.3.2 - Displaying software options (lsopt)
To display software options, type lsopt after the Service prompt:
Figure 4.3: Displaying software option status - lsopt command
The following information is displayed:

Id Software option ID;
Ref. Software option sales reference;
Status Option status, installed indicates that the option has been
installed. "-----" indicates that the option has not been
installed;

Key Key used to install the option;

Number Number of options (tokens);
Comment Option label.
4.3.3 - Ordering and installing a software option
To order and install a software option, please observe the following procedure:
1. Order the software option from Thomson.
2. Install the option using the key supplied by Thomson.
¤ Ordering a software option (eqcod)
1. Read the equipment code of the board requiring the option by typing eqcod
after the Service prompt:
Figure 4.4: Reading the equipment code with the CLI - eqcod command
2. Provide Thomson with the equipment code and specify the software option
required.
3. Thomson will then supply a specific key (which is unique and can only be used
for your NetProcessor 9010).
4. Install the software option as described below.
¤ Installing a software option (insopt)
To install a software option using the code supplied by Thomson:
1. Type insopt after the Service prompt:
2. Enter the software option Option Key.

Figure 4.5: Enabling a software option via the CLI - insopt command
3. To finish installing the option, reboot the device by typing reboot after the
Service prompt:
Figure 4.6: Rebooting NetProcessor 9010 via the CLI - reboot command
Ensure that the option has been validated using the lsopt command (see section
Displaying software options (lsopt), page 240).
¤ Uninstalling a software option (rmopt)
To uninstall a software option:
1. Type rmopt after the Service prompt:
Figure 4.7: Uninstalling a software option via the CLI - rmopt command (1/2)
1. Enter the Option id of the software option to be uninstalled (see section

Displaying software options (lsopt), page 240 to know the option IDs):

Figure 4.8: Uninstalling a software option via the CLI - rmopt command (2/2)
The remove option done message is displayed to indicate that the option has been
uninstalled.
2. Reboot the device to complete the uninstall procedure (sfreboot command).
¤ Recovering lost keys
If you lose a software option key, please contact Thomson Customer Services
with:
• Option purchase order;
• Board Equipment code;
• Sales reference of the option relating to the lost key.

4.4 - Downloading software
4.4 - DOWNLOADING SOFTWARE
Downloading is used to upgrade device firmware. Downloading is performed with

the Command Line Interface as described in this section.
Software is downloaded using the Command Line Interface and TELNET (it cannot
be downloaded using the Local Console and the serial link). The view command,
described in section Displaying firmware releases (view), page 245, is used to
display the software release installed in the device.
An FTP server must be installed on the PC supporting the software files to be
downloaded onto NetProcessor 9010. The downloading function is compatible with
all standard FTP servers. Downloading is performed in passive mode
(NetProcessor 9010 sets up the connection).
NetProcessor 9010 features two program memories. After downloading, one of
these memories contains the program which has just been downloaded (but which is
not installed), and the other contains the current program. The togg command,
which triggers a board reboot, is used to install the downloaded program and
uninstall the other one (without changing it).
If enabling downloaded software causes the device to malfunction, you can toggle
each board to the previous software release. See section Procedure for returning to
the previous software release, page 249.

Reboot
PROCESSOR
Toggpkg Toggle
=
Toggle & Reboot
Active Downloaded
Package Package
Downloaded
files
Figure 4.9: Downloading and the Toggpkg command
4.4.2 - Displaying firmware releases (view)
To display the software releases installed on the device, type view after the Service
prompt:
Figure 4.10: Displaying software releases via the CLI - view command

The following information is displayed:

Active package Active software releases.
Inactive package Inactive software releases. "---" is displayed if the content of
the given slot is incorrect.
4.4.3 - Downloading procedure (server, down, view, result,

togg)
1. Put the files to be downloaded on the FTP server (in the directory defined when
the server was set up);
2. Using the Command Line Interface, type sftpsvr after the Service prompt and
set the parameters for accessing the directory containing the files to be
downloaded:
FTP Server Address Server IP address.
Press Return to validate the address in brackets.
Login FTP account "Login".
Press Return to validate the login in brackets.
Password FTP account password set when the server was installed.
Path Path to directory containing the files on the server.
Press Return to validate the path in brackets.
Notes concerning the Path field:

• The path must be set via the FTP server root;
• Directory names must be entered as they appear on the server
(observe upper and lower case letters);
• Use " / " and not " \ " as a separator.

Figure 4.11: Downloading via the CLI - Defining the directory containing the files to
download - sftpsvr command
3. Type downpkg after the Service prompt to trigger downloading:
Figure 4.12: Downloading via the CLI

- Defining the files to be downloaded - downpkg command
Fill in the following fields:

• Do you want to update Board package on slot 1 [Y]/[N]: type y (yes) if you
would like to download software onto the device;
• Product Package to be downloaded into inactive flash bank? Name of the .tar
file to be downloaded onto device. This file must be located in the directory
previously indicated using sftpsvr command.
• Start updating the inactive bank? <yes> to begin downloading

4. Check downloading progress:

Downloading progress can be viewed using the viewpkg command or result
command:

- Displaying downloading progress - viewpkg command

- Displaying downloading progress - result command
5. When downloading is complete, enable the downloaded software by typing

toggpkg after the Service prompt:

Figure 4.15: Downloading via the Local Console - Software toggling - toggpkg command
6. Reboot the device by typing reboot after the Service prompt:
Figure 4.16: Rebooting NetProcessor 9010 via the CLI - reboot command
4.4.4 - Procedure for returning to the previous software

release
You may need to return to the previous software release if enabling downloaded
software causes the device to malfunction.
Type toggpkg after the Service prompt.
4.4.5 - Upgrade from V2.x to V3.0
Refer to the Document upg-9010-V300-A.
4.4.6 - Upgrade a V1.5 Product
Refer to the same document (upg-9010-V300-A).

4.5 - Erasing the configurations
4.5 - ERASING THE CONFIGURATIONS
Two commands are available to erase configurations:

• initcfg command erases the current and saved configurations.
• initcur command erases the current configuration only.
These commands do not alter the parameters edited via the CLI.
1. Type initcfg (initcur respectively) after the Service prompt and confirm twice.
Figure 4.17: Erasing the configuration via the CLI - initcfg (or initcur) command
2. Reboot the device.
Figure 4.18: Reboot request

4.6 - Community strings and access rights
4.6 - COMMUNITY STRINGS AND ACCESS RIGHTS
Community strings are used to implement a basic access right mechanism on

SNMP requests.
Each community string is associated with an access level.
The access level is used to deny write access to one community string even if write
access has been granted in the MIB.
4.6.1.1 - Accessibility values

One of the two following accessibility values can be granted to a MIB variable:
• R/O: the variable is accessible in read mode;
• R/W: the variable is accessible in read mode & write mode if the access level is
set to R/W.
4.6.1.2 - Access level values

Each community string is associated with one of the two following access levels:
• R/O: read-only access to MIB variables.
• R/W: no access restriction.
4.6.2 - Community string edition
By default, 2 community strings are declared:

• public associated with RO access level.
• private associated with RW access level.
Other community strings can be defined by the Operator by using the following CLI
commands:
- CLIST: Show Communities

- CADD: Add a new Community

- CDEL: Delete Community
- CREAD: Read Communities from file
- CSAVE: Save Communities to file
1. Type cread after the Service prompt to see all defined community strings in
persistent storage.
Figure 4.19: cread command
2. Type cadd after the Service prompt to add a community string and set the
association between the community string and the access levels. Confirm.
Figure 4.20:cadd command
3. Type csave after the Service prompt to make the change persistent then
confirm.

Figure 4.21:csave command
4. Type cread after the Service prompt to read the updated list of community
strings.
Figure 4.22: cread command
If you want to remove a community string, type cdel, type the community to be
removed, then confirm. Do not forget to type csave to make the change persistent.
Figure 4.23: cdel command

4.7 - Maintenance
4.7 - MAINTENANCE
4.7.1 - Cleaning chassis ventilation grids
If dust is left to build up on the chassis ventilation grids, the internal temperature of
the chassis will rise and this will affect device performance, service life and
reliability.
You are therefore advised to clean the ventilation grids every year.
4.7.2 - Replacing the fans
The fans fitted in the unit have a service life of 60,000 hours. The fan unit should
therefore be replaced at least every six years. To perform this operation, please
contact Thomson Customer Services.
4.7.3 - Replacing a PSU in a chassis with two Power Supply

units
PSU1 PSU2
Figure 4.24: PSU front panel for chassis with two Power Supply units (fascia removed)
The in-built Power Supply board of the chassis with one AC Power
Supply cannot be replaced by the Customer.

4.7 - Maintenance
4.7.3.1 - Fault diagnosis

If one of the two PSUs is not working, an alarm will be fed back to the Management
system and the green Power LED on the front panel of the faulty unit will go out.
You will need to replace the PSU.
4.7.3.2 - Procedure for replacing a PSU

For a NetProcessor chassis fed by two PSUs, one PSU can be replaced without
chassis operation being affected.
Chassis operation with a single PSU corresponds to a reduced

operating mode which is not authorised during normal operation. It is
essential to replace the faulty PSU as quickly as possible.
¤ Removing the PSU to be replaced

1. Unplug the cord attached to the faulty PSU;
Figure 4.25: Power inlet according to the chassis model

4.7 - Maintenance
2. Remove the front fascia by unscrewing the knurled knobs on both sides of the
front fascia.
knurled knob knurled knob
Figure 4.26: Knurled knobs on both sides of the front fascia
3. Unscrew the fixing screws on the PSU;
PSU1 PSU2
Figure 4.27: PSU front panel for chassis with two Power Supply units (fascia removed)
4. Remove the faulty PSU.
Never apply current to the PSU outside the chassis.
¤ Installing the new PSU

1. Insert the new PSU into the runners then press on the front panel to insert the
PSU connector into the chassis backplane connector;
2. Tighten the fixing screws;
3. Reinstall the front fascia;
4. Plug in the power cord;
5. Check that the Power LED comes on.

4.8 - Installing an NTP server under Windows 2000 and Windows XP
4.8 - INSTALLING AN NTP SERVER UNDER WINDOWS 2000 AND

WINDOWS XP
As the NTP server shipped with Windows is not fully standard-com-

pliant, it will not operate correctly with NetProcessor 9010. The fol-
lowing procedure can be used to install an NTP server which has
been tested with NetProcessor 9010.
4.8.1 - Architecture
This section shows you how to install a local NTP (Network Time Protocol) server
on a PC.
The architecture described below ensures that NetProcessor 9010 is synchronised
with a single source. For the PC real time clock to be accurate, you must
synchronise the PC time with a GPS board, a radio board or a connection to a
specific NTP server. The following figure shows the recommended architecture:
Figure 4.28: Architecture of a NetProcessor 9010 controlled

by a remote accurate NTP server
Other solutions are also available with other products dedicated to

NTP synchronisation.

4.8.2 - Installation
This section describes how to install an NTP server on PC under Windows 2000 and
Windows XP.
The server source code is available at http://www.ntp.org/.
The server executable code is available at http://norloff.org/ntp/.
Release 4.1.2 of the server was used for the tests.
¤ Installing the server
1. Log on to the PC with administrator rights;
2. Download the ntp-4.1.2-nt.zip file from http://norloff.org/ntp/. If the file is not
available, go to http://www.ntp.org/ for a binary file that will need to be
compiled.
3. Unzip the downloaded file in a directory (c:\ntp for instance)
4. Create a text file called ntp.conf in the System32\drivers\etc sub-directory
located in the Windows installation directory. This file must contain at least the
following row:
server 127.127.1.0 iburst minpoll 5 maxpoll 6
5. To synchronise the time server with a more accurate external NTP server, add
the following row to the ntp.conf file: server <address> prefer burst iburst. In
the following ntp.conf example file, the local time server is synchronised with
a server called timeserver.thmulti.com or with itself if the remote server is not
available:
Figure 4.29: ntp.conf file
6. Enter c:\ntp\instsrv c:\ntp\ntpd.exe in a command window. The following

screen is displayed:

Figure 4.30: Installing NTP
7. Open the Windows Control panel (Start / Settings / Control panel);

8. Open Services in Administrative tools;
Figure 4.31 :Service icon
9. Select Properties from the Network Time Protocol shortcut menu;

Figure 4.32: Network Time Protocol shortcut menu
Figure 4.33 : Propriétés de Network Time Protocol
10. Select Automatic for Start up type and click on Start;

The NTP server is now installed.
¤ Checking NTP server operation:

1. Enter c:\ntp\ntpq -p in a command window. The following screen will be
displayed if the server is operating correctly:
Figure 4.34: Checking NTP server operation
In the event of problems, an error message may be displayed in Control panel /

Administrative Tools / Event Viewer / Application log.
2. After a few minutes, the NTP server will be synchronised with the PC local
clock. Synchronisation is indicated by an asterisk displayed in the first column
when the c:\ntp\ntpq -p command is reentered:
Figure 4.35: The NTP server is synchronised with the PC local clock
¤ Uninstalling the server

1. Open the Windows Control panel (Start / Settings / Control panel);
2. Open Services in Administrative tools;
3. Select Properties from the Network Time Protocol shortcut menu;
4. Click on Stop;

Figure 4.36: Stopping the server
5. Enter c:\ntp\instsrv remove in a command window:
Figure 4.37: Deleting the NTP server

4.9 - Installing an FTP server under Windows 2000 and Windows XP
4.9 - INSTALLING AN FTP SERVER UNDER WINDOWS 2000 AND

WINDOWS XP
This section decribes how to install and configure an FTP server. For more
information about server installation and setup, please refer to the Windows 2000 or
XP (professional edition) manual.
4.9.1 - Installation
Depending on how Windows was installed, the Windows CD-ROM may be

required to install the FTP server.
Procedure :
1. Check whether an FTP server has already been installed. To do this, type Ftp
localhost in a command line. If connection is made, an FTP server has already
been installed;
2. Click on Control Panel in the Start/Settings menu;
3. In the Control Panel window, double-click on Add/Remove Programs;
4. Select Add/Remove Windows Components;
5. In the Windows Components Wizard window, select Internet Information
Services (IIS) and then click on Details;
6. Select Common Files, Documentation, File Transfer Protocol (FTP) Server
and Internet Information Services Snap-In and then click on OK:

7. Click on Next;
8. If you are prompted to configure Terminal Services, click on Next;
9. If you are prompted for the Windows source file path, select the drive
containing the Windows installation CD. If a copy of this CD has been made on
the hard disk (e.g. in C:\I386), select the copy path;
10. If you are prompted for the FTP root folder path, type the path to access the
folder. The default path is C:\Inetpub\Ftproot. For additional security, you are
advised to use an NTFS drive. Click on OK to continue;
11. When prompted, insert the Windows CD or, if a copy of this CD has been made
on the hard drive (e.g. in C:\I386), select the copy path and then click on OK;
12. Click on Finish.
4.9.2 - Setting up the server
This section describes how to set up the Windows FTP server.

The default configuration gives access to the FTP server with a low security level.
Refer to Windows documentation if you require a different configuration.

Procedure:
1. Select the Computer Management icon in the Control Panel/Administrative
tools;
2. On the left-hand side of the window, select Default FTP Site under Services
and Applications/Internet Information Services:
3. Check that the server is in use in the top of the window: select the Start
command if it is not greyed out;
4. Right click to select Properties in the short-cut menu;
5. Check the FTP Site page parameters:

6. Check the Security Accounts page parameters:

Ensure that the Allow Anonymous Connections and Allow only anonymous
connections boxes are checked. Keep the suggested Username. It will be used by
the anonymous connection:

7. On the Home Directory page, select the path to access the files to be
downloaded. E.g.: c:\NetProcessor 9010\download. If you select a path to a
network drive, you must set the Windows account so that it has access to this
drive.
Ensure that the Write box is not checked for security purposes.
Check that Directory Listing Style is set to UNIX.

8. Once the FTP server has been set up, check that it is operating correctly. Open
a shell command and type ftp 127.0.0.1 (loopback @). Type anonymous as the
user name and any value for the password.
9. Type ls to list the contents of your directory.

10. If the command is run and the contents of the directory are displayed, the server
is operating correctly and is ready for use.
If you do not use the anonymous connection, you can force users to enter a
specific login and password. To do so:
1. In the Computer Management window, select New User in the Users
short-cut menu (right click) under Local Users and Groups.
2. Enter the User name and password required to log on to the FTP server.
Check the User cannot change password, Password never expires and
Account is disabled boxes:

3. Right click on the User name which has just been created to edit its
properties. Delete the user from the Users group and add it to the Guests
group:
4. Go back to the Default FTP Site window, Security Accounts page and
uncheck the Allow Anonymous Connections box:


BLANK PAGE

Chapter 5 - Alarms 273
Chapter 5
Alarms

274 Chapter 5 - Alarms
BLANK PAGE

¤ Atm port lossOfSignal
Source ATM port 

Cause Loss of signal
Diagnosis The line decoder cannot lock on incoming signal
Corrective Check your cabling. Check signal levels.
Action A check of received signal shall be made. If no cause is directly detected
there, a transmission analyzer shall be used in place of the network
adaptor for comparison. If a test system is not available a network
adaptor exchange is worth being tried.
¤ Atm port lossOfFrame
Source ATM port 

Cause Loss of frame
Diagnosis Frame synchronization loss. Received signal is unframed or there is an
excessive bit error rate.
¤ Atm port lossOfPointer
Source ATM port 

Cause Loss of pointer or plcp
Diagnosis Impossible to extract frame payload. Received signal has a different
syntax than expected or there is an excessive bit error rate

¤ Atm port lossOfCellDelineation
Source ATM port 

Cause Loss of cell delineation
Diagnosis Impossible to extract final payload. Received signal has a different
syntax than expected or there is an excessive bit error rate
Action Check configuration. Scrambling and cosset settings should be equal on
both ends.
A check of received signal shall be made. If no cause is directly detected
¤ Atm port AIS
Source ATM port 

Cause Alarm Indication Signal
Diagnosis Transmission is broken before last equipment in the signal path towards
the network adaptor.
Corrective This condition is raised by a distant device. Check network backward,
Action element by element, to find first device not raising AIS. Issue has to be
fixed at that point.
¤ Atm port PathAIS
Source ATM port 

Cause Path or plcp AIS
Diagnosis Transmission is broken before last Add & Drop Mux equipment in the
signal path towards the network adaptor.
Corrective This condition is raised by a distant device. Check network backward,
Action element by element, to find first device raising a major alarm. Issue has
to be fixed at that point.

¤ Atm port RDI
Source ATM port 

Cause Line RDI
Diagnosis A remote indication or a far end failure (FERF) is received. Indicates a
distant external failure. The network does not receive the generated
signal. This condition is raised by the device facing network adaptor.
Corrective Analyze alarm raised by facing device to fix problem.
Action
¤ Atm port PathRDI
Source ATM port 

Cause Path or plcp RDI/RAI
Diagnosis A remote indication or a far end failure (FERF) is received. Indicates a
distant external failure. The network does not receive the generated
Action
¤ Atm port REI
Source ATM port 

Cause Remote error indication
Diagnosis A remote indication or a far end block errors (FEBE) is received.
Indicates a distant external anomaly. The network receives a degraded
Action

¤ Atm port Congestion
Source ATM port 

Cause Congestion
Diagnosis A part of traffic is discarded before multiplexing, because total rate is
above available bandwidth.
Corrective Check if bandwidth allocation can be increased. If congestion occurs
Action despite the mean rate of source is well below guaranteed allocation, it
means source is bursty. Check source configuration to reduce burstiness.
¤ Atm port Unequipped
Source ATM port 

Cause Unequipped
Diagnosis SFP module is not detected.
Corrective Check for SFP presence, and, if present, check if it is correctly locked.
Action You should hear a “click” when locking in an SFP.
¤ Atm port HardwareFailure
Source ATM port 

Cause Hardware failure
Diagnosis A hardware componet is not responding, normal operation is
impossible.
Corrective This event, as many others, can be produced transiently by, for example
Action a major electromagnetic disturbance. A one time transient alarm shall
not be taken as an evidence of a failure. Always try the following
procedure.
Switch off then on the device and wait for device start-up. If the state is
still the same, please contact your after sales representative for analysis
and repair.

¤ Atm rx UnlockedPll
Source ATM RX 

Cause Unlocked PLL
Diagnosis This alarm is normal during establishment phase of a connection. If
permanent, check incoming signal and far end configuration. There may
be a source clock poor stability or an excessive jitter introduce by the
transmission.
Corrective Check signal source rate stability and transmission quality
Action
¤ Atm rx lossOfTsSync
Source ATM RX 

Cause Loss of TS synchro
Diagnosis Transport Stream packet delineation failure
Corrective Check network routing (not receiving a TS signal),. Check FEC
Action settings. FEC configuration shall be identical on both end of
transmission. Check TS source.
A check of received signal shall be made. If no cause is directly
detected there, a transmission analyzer shall be used in place of the
network adaptor for comparison. If a test system is not available a
network adaptor exchange is worth being tried.

¤ Atm rx NoStreamReceived
Source ATM RX 

Cause No stream received
Diagnosis No useful traffic is received on specified communication channel.
Note : This event, as many other reception alarms, is generally produced
by transmission problems in the network. It can also come from
configuration errors. The quality of transmission shall be analyzed by
skilled staff. A check of network state shall be made. If no cause is
directly detected there, a transmission analyzer shall be used in place of
the device for comparison. If a test system is not available a device
exchange can be performed. Hereunder analysis proposal covers only
trivial causes.
Corrective Contact the operator of the transmitting equipment. The service is
Action probably disrupted on this side.
This event, as many other reception alarms, is generally produced by
transmission problems in the network. It can also comes from
configuration errors. The quality of transmission shall be analyzed by
skilled staff. A check of network state shall be made. If no cause is
directly detected there, a transmission analyser shall be used in place of
the device for comparison. If a test system is not available a device
exchange can be performed.
If received signal conformity is proved, stop then restart connection. If
the state is still the same, please contact your after sales representative
for analysis and repair.
¤ Atm rx RateTooLow
Source ATM RX 

Cause Rate too low
Diagnosis Service bit rate is lower than the minimum specified for proper
operation
Corrective Modify your system configuration (increase bit rate)
Action

¤ Atm rx CorrectedErrors
Source ATM RX 

Cause Corrected errors
Diagnosis The device is delivering a fully valid signal while errors and (or) packet
losses are received. It is issued only if used adaptation processing
provides an error correction mechanism.
Corrective Check transmission quality
Action This event, as many other reception alarms, is mostly produced by
transmission problems in the network. The quality of transmission shall
be analyzed by skilled staff. A check of network state shall be made. If
no cause is directly detected there, a transmission analyzer shall be used
in place of the device for comparison. If a test system is not available a
device exchange can be performed.
¤ Atm rx UncorrectableErrors
Source ATM RX 

Cause Uncorrectable error
Diagnosis The device is not able to deliver a fully valid signal because errors and
(or) packet losses are exceeding error correction capabilities. It is issued
only if used adaptation processing is providing an error correction
mechanism.
Corrective Check transmission quality
Action This event, as many other reception alarms, is mostly produced by
transmission problems in the network. The quality of transmission shall
be analyzed by skilled staff. A check of network state shall be made. If
no cause is directly detected there, a transmission analyzer shall be used
in place of the device for comparison. If a test system is not available a
device exchange can be performed.

¤ Atm rx AalLossOfSync
Source ATM RX 

Cause AAL synchro loss
Diagnosis The AAL protocol used by the received service is not compatible with
the one used by sender, or a very high rate of transmission errors
disables any decoding.
Corrective Check transmission quality and configuration coherency.
Action This event, as many other reception alarms, is generally produced by
transmission problems in the network. It can also come from internal
failure. The quality of transmission shall be analyzed first by skilled
staff. A check of network state shall be made. If no cause is directly
detected there, a transmission analyzer shall be used in place of the
device for comparison. If a test system is not available a device
exchange can be performed.
If the failure is proved not due to transmission errors. Contact the
operator of the sending equipment. The service profiles used on each
side are probably not coherent.
If received signal conformity is proved, stop then restart connection. If
the state is still the same, please contact your after sales representative
for analysis and repair.
¤ Atm tx Congestion
Source ATM TX 

Cause Congestion
Diagnosis Service bandwidth is too high for the specified traffic contract.
Corrective Check coherency between transmission configuration and input signal
Action rate. Check source stability and burstiness.

¤ ASI in LossOfSignal
Source ASI in 

Cause Loss of signal
Diagnosis Received signal below detection threshold
¤ ASI in LossOfStream
Source ASI in 

Cause Loss of stream
Diagnosis The line decoder cannot lock on incoming signal. Or bitrate below
minimum supported.
¤ ASI in lossOfTsSync
Source ASI in 

Diagnosis Transport stream delineation failure

¤ ASI in BitrateOverflow
Source ASI in 

Cause Bitrate overflow
Diagnosis Bitrate is above configured maximum bitrate. Packets are dropped.
Corrective Determine whether it is a configuration error or an unexpected source
Action behavior. Do appropriate change. Beware of source burstiness. The
limitation is based on instantaneous packet rate, that can be higher than
mean rate.
¤ ASI out lossOfTsSync
Source ASI out 

Diagnosis Some output packets have incorrect synchro bytes.
Corrective Check signal on the corresponding input. Input TS synchro is flexible
Action and can cope with isolated wrong synchro. They will be passed
transparently.

¤ IP Port HarwareFailure
Source IP Port 

Cause Hardware failure
Diagnosis One of the WAN/LAN interface has it mac address set to 0
Corrective action please contact your Customer Service for repair.
¤ IP Port LinkDown
Source IP Port 

Cause Link down
Diagnosis The line transceiver of the board cannot lock on incoming signal.
by transmission problems in the network. It can also comes for a device
partial failure. The quality of transmission shall be analysed by skilled
detected there, a transmission analyser shall be used in place of the
trivial causes
Corrective action Check if the good cable is plug on the physical input. If received signal
conformity is proved, reboot the equipment. Wait until it is recognised
by the control and command software. If the state is still the same,
please contact your Customer Service for analysis and repair.
¤ IP Port HalfDuplexMode
Source IP Port 

Cause Half duplex mode
Diagnosis Auto negociation done in half duplex mode (transceiver status)
Corrective action Transmission and Reception stream could be correct but it is
recommends to work in Full Duplex Mode

¤ IP Port BandwidthReduced
Source IP Port 

Cause Bandwidth reduced
Diagnosis Available bandwidth is reduced
Corrective action Transmission and Reception stream could be correct but it is
recommended to work at enhanced bandwidth. Collect extra
information in the log to get value
¤ IP Port Congestion
Source IP Port 

Cause Congestion
Diagnosis Input network rate is greater than equipment capacity.
device for comparison. If a test system is not available an device
trivial causes.
Corrective action Check input rate: it MUST be within the equipment capacity. Check
transmission quality. If received signal conformity is proved, reboot the
equipment. Wait until it is recognised by the control and command
software. If the state is still the same, please contact your Customer
Service for analysis and repair.
¤ IP UnexpectedAccess
Source IP BLOCK RX
Cause Unexpected access
Diagnosis Bad source IP address or bad destination UDP port for received frames
Corrective action Check the transmitter configuration. If configuration is correct, contact
your network infrastructure representative

¤ IP Congestion
Source IP BLOC TX
Cause Congestion
Diagnosis At output, sum of useful components TS rate exceeding line capacity.
Corrective action Check your throughput configuration in the complete system.
¤ IP Rx NoStreamReceived
Source IP RX 
Cause No stream received
Diagnosis Nothing received on specified channel: No IP datagrams on the selected
IP @
Corrective action Check if it is the correct cable connected to the board.If received signal
conformity is proved, reboot the equipment. If the state is unchanged,
contact your network infrastructure representative
¤ IP Rx LossOfTSSynchro
Source IP RX 
Diagnosis The board cannot find frame synchronisation pattern on incoming TS
signal.
by interconnection or external source equipment. It can also comes for a
device partial failure. The quality and conformity of received signal
shall be analysed by skilled staff. A check of source equipment shall be
made. If no cause is directly detected there, the adequate signal
analyser shall be used in place of the device for comparison. If a test
system is not available a device exchange can be performed. Hereunder
analysis proposal covers only trivial causes.
Corrective action Check if the good cable is plugged on the physical input. If received
signal conformity is proved, reboot the equipment. Wait until it is
recognised by the control and command software. If the state is still the
same, please contact your Customer Service for analysis and repair.

¤ IP Rx FramingError
Source IP RX 
Cause Framing Error
Diagnosis The board cannot find frame synchronisation pattern on incoming TS
signal.
by interconnection or external source equipment. It can also comes for a
device partial failure. The quality and conformity of received signal
shall be analysed by skilled staff. A check of source equipment shall be
made. If no cause is directly detected there, the adequate signal
analyser shall be used in place of the device for comparison. If a test
system is not available a device exchange can be performed. Hereunder
analysis proposal covers only trivial causes.
Corrective action Check if the good cable is plugged on the physical input. If received
signal conformity is proved, reboot the equipment. Wait until it is
recognised by the control and command software. If the state is still the
same, please contact your Customer Service for analysis and repair.
¤ IP Rx UncorrectableErrors
Source IP RX 
Cause Uncorrectable errors
Diagnosis The board is delivering a corrupted signal with frame loss. It is issued
only if used mode provides error detection mechanism. Means FEC
capacity is overflowed.
trivial causes.
Corrective action To enhance the behavior of the system, adjust the FEC parameters at the
emission side.

¤ IP Rx Low Quality output clock
Source IP RX 
Cause Low quality output clock
Diagnosis The variation on received stream data rate is out of expected boundary
or frequency information carried by PCRs is far away from a 27Mhz
system clock. This is an early warning of potential PLL unlock events.
Corrective action Usual case is the reception of a VBR data stream. Check stream source.
Null packets should not have been discarded, or, if source is a splitter, a
fixed TS rate must be regenerated explicitly by the source. Other case is
when Ts is generated by a server where playback rate differs from
record rate. Check server configuration. Check server local timing
source accuracy.
¤ IP Rx LossOfFrame
Source IP RX 
Cause Loss of Frame
Diagnosis The board is delivering a fully valid signal while there are frame losses
(all losses are corrected)
Corrective action Check the transmission quality to improve the received signal
conformity.
¤ IP Tx UnreachableDestination
Source IP TX 
Cause Unreachable destination
Diagnosis Unreachable destination. Destination host is not connected to network,
or bad IP settings of destination host or problem of configuration on
intermediate routers.
Corrective action Check destination host. Contact your network infrastructure
representative

¤ IoDeviceError
Source “multiple”
Cause IO device error
Diagnosis Internal packet engine has detected data loss
Corrective This event can appear transiently at system startup.
Action If alarm is permanent, first check ther is no unexpected very high bit
rate input that overflows the engine. You can switch off all inputs one by
one to detect such a case.
If this does not solve the issue, clear all internal connections. Re-apply
initial configuration. If alarm is still raised, try a general power cycling.
If the state is still the same contact your after sales representative for
analysis and repair.
¤ OutputDeviceError
Source “multiple”
Cause Output device error
Diagnosis Internal packet engine has detected data loss
Corrective This event can appear transiently at system startup.
Action If alarm is permanent, first check ther is no unexpected very high bit rate
input that overflows the engine. You can switch off all inputs one by one
to detect such a case.
If this does not solve the issue, clear all internal connections. Re-apply
initial configuration. If alarm is still raised, try a general power cycling.
If the state is still the same contact your after sales representative for
analysis and repair.

Return your comments
All comments help us to improve our publications.

Do not hesitate to contact us:
Thomson Grass Valley
Integration and Networking Solutions
Département Marketing
Service Documentation
Rue du Clos-Courtel
35517 CESSON-SEVIGNE - FRANCE
------------------------------------------------------------------------------
Please give the manual reference:
Reader name:
Company:
Address:
Phone:
Fax:
E-mail:
Your comments:

BLANK PAGE

Index 293
Index
Numerics PMD sublayer ......................................40

Reception CS sublayer.........................30
1000Mbps Full Duplex ...........................178
Reception SAR sublayer......................30
SDH/SONET network interface ..........41
TC sublayer..........................................40
Transmission CS sublayer ...................29
A Transmission SAR sublayer.................30
AC Mains power supply cord(s)...............97 ATM Data service ....................................36
Activity ....................................183, 184, 188 ATM extension board.............................121
Activity ....................................................191 ATM RX list ............................................182
Add a new Rx ..................................183, 187 ATM TX list.............................................184
Add a new Tx ..........................................184 Authentication mode .......................179, 180
Advanced ........................................175, 227 Auto-negotiation .....................................178
Air flow ....................................................87
All alarms ...............................................228
Applications................................................3
Apply.......................................................222 C
Apply an empty configuration ................223 Cables .....................................................119
Architecture Cabling .....................................................95
Contribution system...............................4 Calculating used bandwidth .....................57
NetFeeder’s functional architecture.....23 Case sensitive .........................................146
Primary distribution ...............................5 Chassis types ............................................86
Area ........................................................180 CLI commands
ASI dasiin..................................................115
Displaying the number of ASI inputs 115 ddate...................................................113
Editing the number of ASI inputs ......115 ipdisp..................................................111
Input .....................................................26 ipset....................................................111
Network interface ................................25 ipset2..................................................112
Output ..................................................26
rinfo....................................................117
ATM sasiin ..................................................115
Asynchronous demultiplexing .............33 sdate ...................................................113
Asynchronous multiplexing.................33 winfo ..................................................118
Multiplexing (ATM layer) ...................31 Clock Source...........................................174
Network adaptation..............................28 CMD1 LEDS ..........................................122
Network interface features...................31 Command Line Interface ..................70, 105
PDH network interface ........................41 Connection list........................136, 138, 197
Physical layer.......................................40 Connections ............................................119

Index 294
Cosset .....................................................175 FEC.................................................183, 185

FEC RTP
FEC features ........................................45
FEC principle.......................................46
Output flow ..........................................49
D Fixed rate................................................190
Data links..................................................34 Fixed rate value ......................................190
Date and time
Displaying..........................................113
Editing................................................113
Declaration of conformity ........................81
Delete......................................................224 G
Destination IP address ...........................191 Gigabit Ethernet interfaces .....................121
Destination UDP port.............................192 Gigabit Ethernet ports...............................54
Device description ....................................14
DiffServ...................................................192
Dimensions .........................................76, 99
Direct mapping.......................................175
Dynamic IP routing ................................178
H
Hello Generation Frequency ..................180
Help ........................................................109
E
EMC ground .............................................95
Enabled...................................172, 173, 174
I
Ethernet rate..............................................57 Import configuration file ........................221
Events .....................................................229 In-Band Control & Command setup.......163
Expert parameters settings......................196 In-Band management................................53
Export .....................................................220 In-Band management links.......................34
Export info to a file.................................232 Initial parameters ....................................105
EXT_1 port .............................................120 Inputs/Outputs description........................16
Installation procedure ...............................85
Interface backup status...........................177
Interface nominal status .........................177
Interface speed/mode..............................177
F Interfaces ....................................................6
Factory set IP address .............................105 Internal ...................................................174
Fault diagnosis........................................255 IP

Index 295
Decapsulation.......................................52 Max TS output rate .................................194

FEC ......................................................52 Maximum bit rate ...................................172
Jitter absorption....................................52 Maximum output bitrate .........................177
MAC Layer ..........................................53 MD5 key id .....................................179, 180
Network adaptation..............................44 Mode .......................................................175
Rate ......................................................57 Monitoring..............................................231
Reception .............................................51 MPEG over ASI adaptation layer.............26
Reordering ...........................................52 MPEG over ASI rate capacity ..................27
Routing.................................................53 MPEG over ATM Adaptation layer .........29
Transmission........................................45 MPEG over ATM rate capacity................42
Transmission adaptation ......................45 MPEG over IP adaptation layer................45
Transmission settings...........................50 MPEG over IP overheads .........................55
TS rate recovery...................................52 MPEG over IP rate capacity .....................55
Unicast and Multicast ..........................51 MPEG packets per IP frame...................194
IP address ...............................................177 MPEG TS rate ..........................................57
IP parameters Multicast destination IP address ............188
CMD1 IP parameters .........................111 Multiplexer Input ....................................227
CMD2 IP parameters .........................112
Displaying..........................................111
Editing................................................111
IP RX list.................................................187
IP RX setup .............................................187
N
Netmask ..................................................177
Network port counters ............................232
Network ports counters...........................231
NTP server IP address............................227
L Null packet discard.................................194
Label ...............172, 173, 174, 183, 184, 187
Label .......................................................191
Latency .........................................27, 43, 58
Login.......................................................107
Loopback mode.......................................175
O
OAM Activity ..........................................174
Operation status .....................................177
Ordering guide............................................9
OSPF ......................................................180
M Overheads .................................................55
Management systems................................67

Index 296
P RX FEC module ......................................189

Packet size ..............................................173
Password.................................................107
Password ........................................179, 180
Physical port label..................................176 S
PLCP C-Bit parity ..................................175 Save active configuration .......................219
Power consumption ..................................75 Scrambling..............................................175
Power outlet........................................15, 96 Securing brackets......................................88
Power supply ............................................73 Selected port ...........................183, 184, 188
Power up .................................................104 Selected port ...........................................191
Procedure for replacing a PSU ...............255 Serial link................................................106
Product overview........................................6 Shaping ...................................................177
Protective ground......................................96 SNMP agent
MIB......................................................69
Protocol................................................69
Trap management ................................69
Q Source IP address...................................192
Specifications
QoS .........................................................192 CE labeling ..........................................79
Climatic................................................79
Electromagnetic ...................................79
Environmental......................................79
R Mechanical...........................................76
Rack mounting..........................................88 Pollution...............................................80
Rate.........................................................185 Protection .............................................80
Reception UDP port ...............................188 Safety ...................................................79
Recovered ...............................................174 Transport..............................................80
Reliability .................................................80 Vibration, shock and Fall.....................80
Reordering Tolerance.............................189 Stacks........................................................55
Replacing a PSU.....................................254 Standard Compliance................................71
Requested IPDV Tolerance ....................189 Static IP routing .....................................178
RIPv2 ......................................................178 Status ......................................................228
Route Disable Time Out .........................180 STM1.......................................................175
Route disable Time out ...........................179 Stored configurations .............................218
Route Garbage Time Out........................179 STS3c ......................................................175
Route Update frequency .........................179 Stub area.................................................180
RX Decapsulation ...................................189 Supervision .................................................8

Index 297
SysContact ..............................................117 W
SysLocation ............................................117
Web Interface ...........................................70
SysName.................................................117
Weight ......................................................77
System overview ........................................3
T X
XMS 3500 Management System..............70
Time set from NTP..................................227
Time set mode .........................................227
Time set off .............................................227
TOS .........................................................192
TS Routing................................................60
TTL .........................................................192
TX Encapsulation ...................................194
TX FEC module ......................................194
U
Use ARP..................................................192
User Priority...........................................192
V
VCI..................................................183, 185
Ventilation ..........................................78, 89
VLAN ......................................................192
VLAN support ..........................................53
VPI ..................................................183, 185

IntraUser Manual 9010v30e

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IntraUser Manual 9010v30e

Uploaded by

Copyright:

Available Formats

NetProcessor 9010

Contacting Thomson: www.thomsongrassvalley.com/contact/

Thomson reserves the right to make changes at any time without

The following symbol conventions are used in this manual:

This symbol is intended to alert the User to the presence of a

This symbol identifies conditions or practices that could result in

This symbol indicates supplemental information that helps you make

This symbol indicates important information that helps you make

PURPOSE OF THIS MANUAL

This manual contains five chapters.

Chapter 2 - INSTALLATION and START UP explains the operations required

Chapter 3 - OPERATION WITH WEB BROWSER describes the functions

Chapter 4 - SERVICING gives useful basic preventive and corrective

Chapter 5 - ALARMS provides the list of alarms managed by NetProcessor 9010.

46072497EA01 NetProcessor 9010, release 3.0

WHAT’S NEW IN RELEASE 3.0?

1. Some of the following features can be limited by software option

NetProcessor 9010, release 3.0 46072497EA01

46072497EA01 NetProcessor 9010, release 3.0

NetProcessor 9010, release 3.0 46072497EA01

Minimum 9010 configuration

1 x N901BMAGAA 1 PSU AC chassis, 10 ASI interfaces, 2 IP streams.

9010 configuration for

1 x N901BMA0AA 1 PSU AC chassis, 10 ASI interfaces, includes the processing of

9010 configuration for

1 x N901BMA0AA 1 PSU AC chassis, 10 ASI interfaces, includes the processing of

46072497EA01 NetProcessor 9010, release 3.0

¤ Input Transport Stream Redundancy

• For ATM interface: OUTPUTDEVICEERROR, STREAM_OVERFLOW,

• For IP interface: BITRATE_OVERFLOW, BITRATE_UNDERFLOW,

NetProcessor 9010, release 3.0 46072497EA01

Input Transport Stream Redundancy performances are:

NetProcessor 9010 automatic stream redundancy is mutually

¤ ATM Data service improvement

¤ Upgrade to V3.0 SW release

46072497EA01 NetProcessor 9010, release 3.0

NetProcessor 9010, release 3.0 46072497EA01

General Safety Instructions

46072497EA01 NetProcessor 9010, release 3.0

Mains power: The connection panel should comply with the

NetProcessor 9010, release 3.0 46072497EA01

46072497EA01 NetProcessor 9010, release 3.0

Replacement of RAM The product includes non volatile RAM with

NetProcessor 9010, release 3.0 46072497EA01

PRODUCT DAMAGE PRECAUTIONS

Fitting Observe the installation instructions in section Rack

46072497EA01 NetProcessor 9010, release 3.0

NetProcessor 9010, release 3.0 46072497EA01

Contacting Thomson .....................................................................................iii

Manual Conventions ......................................................................................iv

Purpose of this manual ..................................................................................v

What’s new In release 3.0? ...........................................................................vi

General Safety Instructions ........................................................................xiii

1.2 - Product overview............................................................................................... 6

1.3 - Ordering guide................................................................................................... 9

1.4 - Device description........................................................................................... 14

46072497EA01 NetProcessor 9010, release 3.0

1.4.5.1 - MPEG over ATM Adaptation layer ................................................. 29

1.5 - Description of the management systems...................................................... 67

1.6 - Standard Compliance ...................................................................................... 71

1.7 - General device Specifications ........................................................................ 73

1.8 - EU declaration of conformity.......................................................................... 81

NetProcessor 9010, release 3.0 46072497EA01