Nexio Server Core TG - MNT - 02 29 2012

NEXIO Server Core
Technical Training Guide
2012-January-30
HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®
Copyright © 2012 Harris Corporation Release , February 29, 2012

Doc No: NE XIO_SVR_T G_MNT

Copyright © 2012 Harris Corporation. All rights reserved. This
Harris Corporation publication supersedes all previous releases. No part of this
Broadcast documentation may be reproduced in any form or by any means or
Communications used to make any derivative work without permission from Harris
Division Corporation.
9451 Corbin Ave. Suite #
150 Harris Corporation reserves the right to revise this documentation
Northridge, CA 91324 and to make changes in content from time to time without obligation
on the part of Harris Corporation to provide notification of such
revision or change.
UNITED STATES GOVERNMENT LEGEND If you are a United

States government agency, then this documentation and the
software described herein are provided to you subject to the
following:
All technical data and computer software are commercial in nature
and developed solely at private expense. Software is delivered as
“Commercial Computer Software” as defined in DFARS 252.227-
7014 (June 1995) or as a “commercial item” as defined in FAR
2.101(a) and as such is provided with only such rights as are
provided by Harris’ standard commercial license for the Software.
Technical data is provided with limited rights only as provided in
DFAR 252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987),
whichever is applicable. You agree not to remove or deface any
portion of any legend provided on any licensed program or
documentation contained in, or delivered to you in conjunction with,
this User Guide.
CCS, CCS CoPilot, CCS Navigator, CCS Pilot, Command Control

System, CineTone, CinePhase, CineSound, DigiBus, DigiPeek,
Digital Glue, DigiWorks, DTV Glue, EventWORKS, EZ HD, Genesis,
HDTV Glue, Image Q, Inca, Inca Station, InfoCaster, Inscriber,
Inscriber CG FX, Integrator, Integrated Content Environment (ICE),
LeFont, Leitch, LogoMotion, MediaFile, Mix Box, NEO, the NEO
design, NEOSCOPE, NewsFlash, NEXIO, NEXIO AMP, NEXIO Pilot,
Opus, Panacea, PanelMapper, Playlist, Portal, PROM-Slide,
RAIDsoft, RouterMapper, RouterWorks, Signal Quality Manager,
SpyderWeb, SuiteView, TitleMotion, UNIFRAME, Velocity,
VelocityHD, VideoCarte, Videotek, and X75 are trademarks of Harris
Corporation which may be registered in the United States, Canada,
and/or other countries.
Windows is a registered trademark of Microsoft Corporation. AMD

and Operton are trademarks of Advanced Micro Devices, Inc. Dolby
Digital is a registered trademark of Dolby Laboratories.
All other trademarks are the property of their respective holders.


Table of Contents
Training Outline .................................................................................................... 11
Training Objectives .............................................................................................. 11
Day 1 - Objectives ................................................................................................ 11
Day 1 - Agenda .................................................................................................... 13
Introduction ..................................................................................................................... 15
Objectives ............................................................................................................ 15
Pre-requisites ....................................................................................................... 15
Course Structure .................................................................................................. 16
Course Focus ....................................................................................................... 16
Technical Support ................................................................................................ 17
Pre-training Quiz .................................................................................................. 19
Windows Operating System.................................................................... 19
Terminology ............................................................................................ 20
System Overview ............................................................................................................ 21

The NEXIO Video Server ..................................................................................... 22
NX3801HDI ............................................................................................. 24
Front Server view: ................................................................................... 25
Back Server View ................................................................................... 26
Video Server Basics ............................................................................................. 30
What is a Video Server? ......................................................................... 30
Video Server System .............................................................................. 30
System Hardware................................................................................................. 31
Work Station............................................................................................ 31
Server Chassis ........................................................................................ 31
Networks ................................................................................................. 31
Storage Area ........................................................................................... 31
Servers .................................................................................................... 32
Speciality Servers Overview ................................................................................ 33
Harris News Solution .............................................................................. 35
Specialty Servers ................................................................................................. 36
Editing Servers ........................................................................................ 36
Newsroom Systems ................................................................................ 37
NEXIO Proxy Browse (Low-Res) Systems ............................................. 41
Media Transfer and Management ........................................................... 43
Other Server Solutions ............................................................................ 44
Software Overview ............................................................................................... 47
LLM ......................................................................................................... 47
Ingest - ICM............................................................................................. 48
Digitize .................................................................................................... 49
Crash Recording ..................................................................................... 50
Playout .................................................................................................... 50
ClipSync .................................................................................................. 52
Delay ....................................................................................................... 52
NX3601HDX / HDI G2 or Higher Models Software Options ................................ 54
NEXIO AMP ChannelView ...................................................................... 54
Logo Inserter ........................................................................................... 54
Quiz 1 System overview ..................................................................................... 55
System Architecture ....................................................................................................... 57

Typical Systems ................................................................................................... 57
3601HDX Redundant Fiber Channel ...................................................... 57
Multi Drive Max Allowable Configuration ................................................ 57
Redundant fibre server system with Fibre switches ............................... 57
Redundant direct connect fibre channel system ..................................... 57
FARAD Storage Solution ........................................................................ 57
NX3000VNES ......................................................................................... 57
Redundant Fiber Channel Drawing ..................................................................... 58
Multi Drive Max Allowable Configuration ............................................................. 59
Redundant fibre server system with Fibre switches ............................................ 59
FARAD Storage Solution ..................................................................................... 61
Direct connect fibre channel system .................................................................... 62
NX3000VNES connections ..................................................................... 63
Quiz 2 System Architecture ................................................................................. 64
Server System Components .......................................................................................... 65

Server Hardware .................................................................................................. 65
Generic PC Hardware .......................................................................................... 66
NX3601HDX, 3000VESX Models, & NXAMP3801HDX Hardware Tyan
S2915 Motherboard ................................................................................ 66
Tyan S2915 Motherboard fan connections ............................................. 67
NX3601HDX S2915 MB .......................................................................... 68
NXAMP3801HDX Hardware Tyan S2915 Rev. E MB Specification....... 68
BIOS Update and Settings ................................................................................... 69
SATA Connections ............................................................................................... 70
SATA Mirror ......................................................................................................... 71
3601 & 3801 SATA Mirror Set ................................................................ 71
Creating a mirror raid .............................................................................. 71
Table: Servers – Generic PC Hardware Generations.......................................... 72
Video/Audio Input/Output ..................................................................................... 73
video and audio input/output only; for servers using software codec ..... 73
ATTO FC-42XS Dual Optical Port 4Gbps HBA ................................................... 79
ATTO ExpressSAS348 HBA - HDI server .......................................................... 81
SAS Specifications .................................................................................. 81
AfterBurner-3 Boards ........................................................................................... 84
Specifications .......................................................................................... 85
Pin out tables .......................................................................................... 86
Afterburner 3 GPI Circuit ......................................................................... 88
Afterburner 3 Features ......................................................................................... 89
Block Explanation ................................................................................... 89
AB3 I/O BOARD TEST PROCEDURE ................................................... 91
Lab 1 – Afterburner card test ............................................................................... 92
Pro-panel Assembly ............................................................................................. 93
Rear Chassis........................................................................................................ 94
Pro-panel boards.................................................................................................. 95
Lab 2 – Physical inspection ................................................................................. 95
Fibre Channel Drive Array Enclosure (DAE) ....................................................... 96
JBOD Raid Chassis interconnect......................................................................... 98
SBOD raid chassis interconnect configuration .................................................... 98
Fibre Channel Drive Arrays .................................................................................. 99
External shared video and audio media storage .................................... 99
System Fibre Channel ......................................................................................... 99
Fibre Channel Primer .............................................................................. 99
Daisy chain SBOD chassis ................................................................................ 102
Fibre Channel Switch ......................................................................................... 105
SANbox 2 (NXS1622): .......................................................................... 105
SANbox 5600 (NXS1644): .................................................................... 105
8Gb Fibre Channel ................................................................................ 106
Dual Fibre Channel Switch Configurations ........................................................ 107
SANbox2, Single Server Connection, ISL Failover............................... 107
SANbox5600, Dual Server Connection, No Xpak Failover ................... 108
FARAD Fiber Channel Topology .......................................................... 109
System Ethernet................................................................................................. 110
LLM fail over setup ................................................................................ 111
NXESD1224X2 from D-Link.................................................................. 111
xtreme Networks (Summit 450-24t) ...................................................... 112
Layer 3 Extreme Networks Summit 450-48 .......................................... 112
NXESB624 ............................................................................................ 112
NXESB648 ............................................................................................ 112
House Time code Interface ................................................................... 113
NXUSBLTC ........................................................................................... 114
Quiz 3 - System components ............................................................................ 116
System Spec .................................................................................................................. 119

Transmission Video Servers .............................................................................. 119
NX3801 & NX3601 – NEXIO AMP ....................................................... 119
NEXIO AMP Configurations ............................................................................... 120
NEXIO AMP Upgrades and Options .................................................................. 120
Optional Software Applications .......................................................................... 121
Key Features ...................................................................................................... 121
Specifications ..................................................................................................... 123
NEXIO AMP Video Specifications......................................................... 124
Audio Specifications .............................................................................. 124
Standard Definition Video Compression Specifications ....................... 125
High Definition Video Compression Specifications ............................... 126
2 Channel Mode — High Definition Video Compression Specifications
.............................................................................................................. 127
.............................................................................................................. 128
.............................................................................................................. 129
High Definition Video Compression Specification for AVC-Intra .......... 129
RAID Redundancy ................................................................................ 130
Timecode Connection Options.............................................................. 130
Remote GPI Control .............................................................................. 130
Remote Serial Interface ........................................................................ 130
Controls ................................................................................................. 130
NEXIO AMP size specifications. ........................................................... 131
Power Supply ........................................................................................ 131
Specifications ..................................................................................................... 137
Quiz 4 – System Specification ........................................................................... 139
NX3801 - Installation Quick Start ................................................................................. 141

Harris Supplied Products ................................................................................... 141
Customer Supplied Products ............................................................................. 141
Safety Guidelines ............................................................................................... 141
Electrical Safety Guidelines .................................................................. 141
NX3801 - Installation and Configuration ..................................................................... 143

Rack Mounting ................................................................................................... 143
Connecting NEXIO AMP .................................................................................... 144
Connecting the NX3601HDX ............................................................................. 146
NX3601HDI Rear Panel Port Connectors ............................................. 146
NEXIO Config................................................................................................................. 149

Working with Configuration Presets ................................................................... 151
Creating a Default Preset...................................................................... 152
NEXIO Config Windows ..................................................................................... 155
Node/Domain ........................................................................................ 155
Channel Configuration .......................................................................... 156
Video Options ....................................................................................... 157
Audio Options ....................................................................................... 160
GPRX Options ...................................................................................... 162
Automation/Serial .................................................................................. 163
IP Config ............................................................................................... 166
FTP Folders .......................................................................................... 169
LLM Parameters ................................................................................... 170
Error Logging ........................................................................................ 171
LLM ....................................................................................................... 173
MPEG.................................................................................................... 174
FTP ....................................................................................................... 175
Startup................................................................................................... 176
CV/Logo ................................................................................................ 177
Other ..................................................................................................... 178
LLM 1 .................................................................................................... 179
Initializing The Shared Storage RAID Sets: .......................................... 181
ATTO Celerity Card Setup .................................................................... 183
NXS31xxC Drive Chassis: .................................................................... 184
Configuring the Brocade NXESBTI24 with NXESB-10GLINK module . 188
Changing switch boot-preference to support router code. .................... 189
Assigning permanent passwords .......................................................... 190
Enabling Jumbo Frame ......................................................................... 192
Disabling the Spanning Tree Protocol (STP) ........................................ 192
Disabling Stack ..................................................................................... 193
Configuring VLAN ................................................................................. 193
Copying a configuration file to or from a TFTP server .......................... 195
Extreme Switch Setup ........................................................................... 196
Fibre Channel Switch Setup .............................................................................. 198
Commissioning NX3601HDX with a MIOH server ............................................. 205
Ethernet Switch Minimum Requirements .............................................. 209
NEXIO Streaming SAN ......................................................................... 209
NetworkServer Service ......................................................................... 209
NetDiskServer Service .......................................................................... 210
FTP Server Service ............................................................................... 210
Commissioning the System/Configuration ............................................ 210
Intel Pro 1000GT Network Interface Card (NIC) Settings ..................... 212
Chelsio N320E Dual Port configuration ................................................ 212
Day 2 - Agenda .................................................................................................. 215
Intrinsic Mirroring................................................................................................ 217
Intrinsic Mirror FC Physical Layer ......................................................... 217
Writing Mirror Data ................................................................................ 218
Write Flowchart ..................................................................................... 219
Reading Mirror Data .............................................................................. 219
Mirrored WRITE and READ .................................................................. 220
Response to Faults ............................................................................... 221
Intrinsic Mirroring LIP Events ................................................................ 223
Mirrored Rebuild Process ..................................................................... 223
Intrinsic Synchronization ....................................................................... 224
Intrinsic Mirroring Commissioning ...................................................................... 225
To set up Intrinsic Mirroring for a RAID-3 Parity ................................... 225
Parity Intrinsic Mirroring ........................................................................ 226
Intrinsic Mirroring for an ECC SAN ....................................................... 229
Monitoring Intrinsic Mirroring.............................................................................. 232
Lab 5 - Intrinsic Mirroring ................................................................................... 234
Day 3 - Agenda .................................................................................................. 235
LLM ................................................................................................................................. 237

LLM Overview .................................................................................................... 237
To start the LLM .................................................................................... 237
Logical Disks Pane ............................................................................... 238
Creating an ECC logical disk ................................................................ 239
Initialize Logical Disk ............................................................................. 239
To create a new ECC RAID set ............................................................ 240
Resize segments .................................................................................. 242
To adjust the minimum segments ......................................................... 242
Resize segments .................................................................................. 243
ID Name Size ........................................................................................ 243
Minimum Segments .............................................................................. 243
Extended Fields Size ............................................................................ 243
Network properties ................................................................................ 244
Codec control window ........................................................................... 244
Physical disks........................................................................................ 246
Working with logical disks ..................................................................... 246
Error History .......................................................................................... 247
Properties Dialog Box ........................................................................... 247
Drive Replacement ............................................................................... 248
LLM Drive Failures ................................................................................ 249
LLM reseat a drive ................................................................................ 250
Broken Logical Disk .............................................................................. 252
Drive Sense Codes ............................................................................... 255
Lab 6 - LLM ....................................................................................................... 257
Workflow ........................................................................................................................ 259

NEXIO Servers installed in a facility that have automation ............................... 259
Starting NXOS ...................................................................................... 259
Playback an clip ID ............................................................................... 261
NEXIO Servers installed in a facility that do not have automation .................... 262
Day 4 - Agenda .................................................................................................. 269
NXOS Admin functions ......................................................................... 271
Warning Tab.......................................................................................... 273
Lab 7 - NXOS Admin functions ........................................................................ 275
CONSOLIDATION ................................................................................ 276
Lab 8 - NXOS Admin functions ......................................................................... 277
Lab 9 - NXOS Admin functions ........................................................................ 282
Playlist ................................................................................................................ 283
PlayList Toolbar .................................................................................... 285
PlayList Columns .................................................................................. 286
Lab 10 - Playlist .................................................................................... 290
Creating traffic filters .......................................................................................... 291
Traffic Filter Troubleshooting Procedure .............................................. 297
Lab 11 - Traffic filter ........................................................................................... 298
FTP Client .......................................................................................................... 299
Video formats that can be transferred to the SAN ................................ 299
NXOS FTP ......................................................................................................... 306
FTP connections can also be done within ............................................ 306
Day 5 - Agenda .................................................................................................. 308
Assessing System Health ............................................................................................ 309

Server Health ..................................................................................................... 309
Hardware Level .................................................................................................. 310
Operating System Level ........................................................................ 311
Generic PC Component Health ............................................................ 317
Network Properties ............................................................................... 318
Fibre Channel Health ............................................................................ 320
Video I/O, Codec Health ....................................................................... 328
Miscellaneous Elements Health ............................................................ 331
System Health – Ethernet ..................................................................... 339
System Health – Fibre Channel ............................................................ 340
Operational panel for JBOD .................................................................. 341
Operational panel for SBOD ................................................................. 342
System Health – Fibre Channel ............................................................ 343
Issue Resolution ........................................................................................................... 345

Server Configuration – Hardware ...................................................................... 346
Hardware/BIOS/Firmware ..................................................................... 346
Server Configuration - Operating System .......................................................... 348
Memory configuration ........................................................................... 348
Naming convention ............................................................................... 351
Ethernet negotiation .............................................................................. 352
Windows Registry Editor ....................................................................... 353
Server Startup ....................................................................................... 354
NEXIO Startup Configuration Aplication ............................................... 355
Fibre Channel........................................................................................ 361
Array drive firmware .............................................................................. 364
Fibre Channel Switch Settings .............................................................. 370
System Benchmarking ....................................................................................... 371
Configuration – System Elements ........................................................ 371
High Stress Ping Test ........................................................................... 372
Data Gathering Procedures .................................................................. 374
Troubleshooting Software Problems .......................................................................... 377

FXP Error Conditions: ........................................................................... 377
FXPLOG.txt ........................................................................................... 377
LLM CODEC Window ........................................................................... 377
Display Settings .................................................................................... 378
Network Adapter Settings ..................................................................... 378
NX3601HDX I/O Specifications ............................................................ 381
User Login .......................................................................................................... 381
Q: What is the NXOS Admin password? .............................................. 381
Q: What is the MS OS login for the Server? ......................................... 382
Q: What is the LLM Properties login password?................................... 382
Powering Up Issues ........................................................................................... 382
Q: The Server is not powering up? ....................................................... 382
Q: The PS Fault Led is red on the front of the panel, what do I need to
do? The Nexio Monitor is also indicating a Power Supply Error?......... 382
Q: How do I find the log on window for the NXOS application, it just
sitting there stuck on Indexing ID? ........................................................ 382
Networking ......................................................................................................... 382
Q: My Networking icon is showing ‘Not connected’? ............................ 382
Q: My Networking icon is showing limited connectivity? ...................... 383
Q: My Networking Icon indicates there is duplicate IP’s? ..................... 383
Q: My Server keeps going into Play Only mode? ................................. 384
Closed Captioning .............................................................................................. 384
Q: Closed Captioning is not passing through when ingesting and playing
out? ....................................................................................................... 384
Player E’E .......................................................................................................... 385
Q: I am not getting the PlayerE’E confirmation on the signal being
recorded? .............................................................................................. 385
Window OS Clock .............................................................................................. 385
Q: My time code is not updating the Windows OS Clock? ................... 385
Recording Capacity ............................................................................................ 386
Q: How do I check how many hours of record time I have left on my
server? .................................................................................................. 386
Redundancy ....................................................................................................... 388
Q: How many parity drives are required for redundancy? .................... 388
Replacement Drive Serial Number .................................................................... 388
Q: How do I go about identifying the serial number for a particular drive
to request a replacement? .................................................................... 388
Drive Replacement ............................................................................................ 389
Q: How do I go about doing a Drive Replacement? ............................. 389
Identifying Drive for Replacement ......................................................... 389
Replacing Drive ..................................................................................... 389
Rebuild .................................................................................................. 389
NxSnapshot........................................................................................................ 390
Q: How do I complete a Snapshot? ...................................................... 390
Sense Code ....................................................................................................... 391
Q: What is Sense Code of 0 [00] [00]? ................................................. 391
Q: How do I identify the Sense Code I am getting for a particular Drive?
.............................................................................................................. 391
Array Drive Status .............................................................................................. 392
Q: How can I check the status of all my drives in an Array? ................ 392
SATA Mirror Raid Setup – NX3600HDX ............................................................ 392
Q: How do I setup the SATA Mirror Raid on a NX3600HDX SuperMicro
Server?.................................................................................................. 392
Vertical & Horizontal Phase Adjustments – Genlock Verification ...................... 393
Q: How do I adjust the Vertical and Horizontal Phase, plus verify
Genlock? ............................................................................................... 393
VTR Communication .......................................................................................... 393
Q: I can’t communication with a VTR and I have an AB3 RS422 back
plan? ..................................................................................................... 393
Training Outline
 Introduction
 System Overview
 System Architecture
 Server System Components
 System Spec
 NX3801 Installation Quick Start
 NX3801 Installation and Configuration
 NX3801 NEXIO Config
 LLM
 Workflows
 Assessing System Health
 Issue Resolution
Training Objectives
 Understand the NEXIO Server Systems
 Know NEXIO Server Workflows
 How to install & Configure a typical system
 How to troubleshoot
 Hands On
Day 1 - Objectives
 System Overview
 Features
 Architecture
 Physical installation
 Software installation
 Configuration
Day 1 - Agenda
 Pre-Training Quiz
 System Overview
 System Architecture
 System Specs
 Q & A Session
 Quiz
 Installation
 Configuration (HDI, HDX, and MIOH systems)
 Q & A Session
 Lab - Hands On
 Quiz
NEXIO
Tech Guide Introduction
Introduction
Farad is a high capacity, high throughput, and high availability storage. Farad is based online SAS drive
storage for systems requiring 8 to 32 Gbps throughput and 50 to 768 TB of storage. Designed for high
bandwidth codec’s and large I/O counts. Farad improves drive diagnostic and management functions.
Better tools provided to Service organization for commissioning and troubleshooting.
Objectives
To provide the understanding and tools required to effectively install, troubleshoot and isolate
issues in the NEXIO 3801, 3601, 3600 and VOLT video server chassis along with an overview
of the latest LLM and NXOS software.
Pre-requisites
Below is a list of knowledge and experience pre-requisites that will help an individual better
understand the information provided in this guide:
 Windows 7 & XP
o Behind-the-scene configuration
o Management tools.
 PC hardware – experience with major subsystems – motherboards, CPU, memory, hard
drives, adapter card installation
 A very basic understanding of video and audio
 A very basic understanding of computer networking
 Fibre Channel networks
 No in-depth video or networking experience is required

Doc No: NEXIO_SVR_TG_MNT 15
NEXIO
Course Structure
This course is taught in a tiered approach, starting with an overview that simply scratches the
surface for familiarity, followed by system status and then configuration passes that each get
into successively more detail:
• overview of the basic building blocks of a Harris server system

• quick tour demonstrating main software applications and how the shared storage
concept works
• detailed breakdown of:
o all the hardware elements that together make a server
o all the software elements that run on a server
o all the system elements involved in a server implementation
• how to assess the health of the above 3 items
• how to verify correct configuration of these same items
• subsystem benchmarking
• common procedures
Course Focus
 This training is driven for the current server series – NEXIO AMP NX3601 G1, NX3601
G2, NX3601 G3, NX3601 G4, VOLT, Velocities, and NX3801.
 Concepts and models apply to previous series – NX3600HDX/HDI, NX4200HDX/HDI,
NX4000TXS/ITS, VR400, VR445 and VR300.
 The course focuses on the NX3801HDX, NX3801HDI, NX3601HDX, and NX3601HDI

servers.

NEXIO
Related Documentation
NEXIO Low Level Module User Guide (175-000308-03)
NEXIO NXOS User Guide (175-000307-04_RevB)
NEXIO NXOS Quick Reference (175-000310-02)
NEXIO Safety & Compliance Information (175-000364-02)
NXUSBTC User Guide (175-000398-00)
NXUSLTC User Guide (175-100009-00_RevB)
NXUSLTC Quick Start Sheet
NEXIO AMP NX3601HDI User Guide (175-000407-04_RevE)
NEXIO AMP NX3601HDX User Guide (175-000406-05_RevD)
NEXIO AMP NX3801HDI User Guide (175-100257-00_RevA)
NEXIO AMP NX3801HDX User Guide (175-100244-00_RevA)
NEXIO Intrinsic Mirroring UserGuide (175-000510-00)
NEXIO NX1010MIOH UserGuide (175-100040-00-RevB)
Technical Support
Technical support is available 24 hours a day, 7 days a week. You can contact technical
support by phone or e-mail.
Phone:
+1 888-534-8246
+1 416-445-4032 (International)
+1 852-2174-2504 (Asia)
E-mail:
BCDService@harris.com
Service.Europe@harris.com

NEXIO

NEXIO
Pre-training Quiz
Windows Operating System
For each of the following, indicate where in Windows the requested information can be
found, and how to open the applet/utility in question:
1. Configuration settings for most Windows operating system functions:
2. A concise listing of a PC’s hardware:
3. Logs indicating key operating system occurrences and/or faults:
4. Two GUI-based approaches to viewing file system folders and files:
5. A grouping of applets/utilities relating to both hardware and software:

NEXIO
Terminology
In two lines or less, describe the following terms:
Media
Bandwidth
Protocol
Fibre optic
Ethernet

NEXIO
Tech Guide System Overview
System Overview

NEXIO
The NEXIO Video Server

NXAMP3801HDX
LED LED Boot

Indicators LED Keypad Drives
USB Firewire SYS ID

Ports Port Indicator
Turn On – press and hold the button for 5 seconds to power on

system.
System Reset – when powered on; press and hold the button for 3
seconds to reset the system.
Power Off – press and hold the power off button for 5 seconds to
shutdown the system.
Power Power On/ Reset

Off

NEXIO
Port Description
SYS ID Button Used to identify a server from the
SYS ID
front.
Power Supply
Power Supply Alarm Reset Silences the power supply alarm.
Alarm Reset Button
Two hot swappable, redundant power
Power Supplies Power Supply 1, Power Supply
supplies.
2
HD/SD and SDI Four BNC connectors for HD-SDI
IN1, IN2, IN3, IN4
and SDI video inputs 1 through 4.
Video
BNC connector for analog bi-level or
REF IN
tri-level reference input.
LOOP IN1, LOOP IN2, LOOP Four BNC connectors for loop-
IN3, through of inputs 1 through 4.
LOOP IN4
Four BNC connectors for HD-SDI
OUT1, OUT2, OUT3, OUT4
and SDI video outputs 1 through 4.
Four HD-BNC connectors for
AES Audio IN1 1/2, 3/4, 5/6, 7/8
AES/EBU
audio input. Connect to these ports
when using AES/EBU audio and
Dolby E for input 1.
IN2 1/2, 3/4, 5/6, 7/8
AES/EBU
IN3 1/2, 3/4, 5/6, 7/8
AES/EBU
Dolby E
for input 3.
IN4 1/2, 3/4, 5/6, 7/8
AES/EBU

NEXIO

OUT1 1/2, 3/4, 5/6, 7/8
AES/EBU
audio output 1.
OUT2 1/2, 3/4, 5/6, 7/8
AES/EBU
audio output 2.
OUT3 1/2, 3/4, 5/6,
AES/EBU
7/8
audio output 3.
OUT4 1/2, 3/4, 5/6,
AES/EBU
7/8
audio output 4.
USB 2.0 port connector for mouse.
USB USB1 MOUSE
USB 2.0 port connector for keyboard.
USB2 KEYBOARD
Two unassigned USB 2.0 port
USB3, USB4
connectors.
9-pin D-sub connector for RS232
RS232 RS232
serial
port connection.
Computer speaker port connector.
PC Speaker PC SPKR
Not
used.
Two 8Gb Fibre Channel connections
Fibre Channel PORT 0, PORT 1
to shared storage.
Two DVI-I primary monitor
DVI DVI1, DVI2
connections.
ETHERNET1, ETHERNET2, Four RJ-45, 10/100/1000 Mbps
Ethernet
Ethernet
ETHERNET3, ETHERNET4
connections.
Two 26-pin MDR connectors for GPI
GPI Ports GPI IN 1-16, 17-32
input.
COM PORTS Eight RJ-12, RS-422 ports for serial
COM Ports
1, 2, 3, 4, 5, 6, 7, 8 control.
NX3801HDI

NEXIO
NX3601HDX
Front Server view:

 Raid 1 SATA boot system drives
 USB port
 Fire wire port
 Power (on/off) button
 Reset button
 Alarm Cancel button
 Bezel illumination switch
 Bezel illumination LED
 DVD-ROM/CD-RW drive
 LED indicators
o LED Status:
 Power Supply (PS) Good
 Power Supply (PS) Failure
 Drive access
 FAN Failure
 Overheat
 Fault (LLM errors)

NEXIO
NX3601HDX
Back Server View

 Video inputs/outputs
 Audio inputs/outputs
 4 - USB ports
 RS232 COM Port
 Two Ethernet Ports
 Two Fiber Channel Ports
 Two DVI Connections
 GPI inputsouputs
 8 – RS422 Control Ports
 Speaker Connector

NEXIO
NEXIO VOLT
Model numbers:
NXVOLT1401SSD2H, NXVOLT1401SSD3H, NXVOLT1401SSD4H
Description
The NEXIO Volt™ SSD integrated storage server addresses the need for highly resilient server
systems that have longer duty cycles and lower running costs compared to hard drive-based servers.
The NEXIO Volt SSD server is a small form-factor, high-performance baseband video server,
performing baseband ingest, playout and file-based I/O in a 1 RU package. Equipped with its own
solid state media storage, the NEXIO Volt SSD delivers higher levels of performance compared to
hard drive-based servers. It is well suited for standalone applications as well as part of larger
workflows thanks its support of file based workflows, file transfer during ingest, and a wide range of
codecs and wrapper types, such as MXF, QuickTime, GXF, MPG and AVI.
The NEXIO Volt SSD integrated storage server offers support for up to four mixed SD/HD or SD-only
baseband channels in a 1RU package. Its software licensing model allows you to pay for the
channels you use. Software upgrades enable you to add channels later if needed.
Built from the same technology as the award-winning NEXIO AMP® advanced media platform,
NEXIO Volt includes built-in RAID-protected media storage for video and audio essence. This makes
NEXIO Volt ideal for applications including disaster recovery, delay, edge server, on-air cache,
production play-out and ingest to archive. It supports up to 36 hours of XDCAM HD422 50 Mbps or
approximately 140 hours of MPEG-2 material at 12 Mbps.
The NEXIO Volt integrated storage server is ready to use in a variety of broadcast applications. This
is possible due to industry-standard VDCP support and the bundled media applications. The server
comes with the NEXIO Playlist™ event sequencing application for playing content to air, NEXIO
Remote™ for ingest, play-out and media management, and FTP for media interchange via Ethernet
and USB. These media applications can control the server over a local area network (LAN)
enhancing flexibility and ease of access.

NEXIO
Hardware
 1RU form factor
Storage System
 Solid State media drives support 1 TB of usable storage with RAIDsoft™ storage protection
Video I/O
 Software-based codecs for coding and decoding SD and HD media
 Real time, software-based up/down/cross conversion support
 Automatic Aspect Ratio Conversion (ARC) and AFD support
 Supports up to 4 SD only channels, or up to 4 SD/HD channels
 Software licensing for 2 SD/HD, 3 SD/HD and 4 SD/HD channel configurations
 Supports SD (525i, 625i) and HD (1080i, 720p) content on the same chassis
Audio I/O
 16 channels of embedded audio – 16, 20 and 24 bit; per video channel
 Dolby® Digital and Dolby E audio pass-through; per video channel
Ancillary Metadata
 Read, generate, and write continuous and discontinuous VITC
 EIA-608 <> EIA-708 and WST <> OP-47 closed caption support using software based real
time processing
NXVOLT1401HDX

NEXIO
NEXIO VOLT HDX Topology

NEXIO
NEXIO VOLT HDX Topology Continued
Video Server Basics

What is a Video Server?
In its simplest sense, a video server is a computer that records and plays back video and
audio material. Typically, the video and audio signals in and out of the server are baseband
signals, which in the current era means digital: HD - SDI video and either embedded (SDI)
or AES/EBU audio. The NEXIO server also supports FTP clips from different file formats.
Video Server System

A video server system is made up of the following elements a base computer with its core
motherboard, CPU, and memory components. Other elements are required such as user interface
devices like a keyboard, mouse, and VGA monitor. Input and output sources such as video and
audio, control (RS422 or NDVCP), and general purpose interface (GPI) connections. A codec is
required to encode incoming video/audio data into raw bits for storage, and then decode it back to
video/audio for playback. A storage media chassis, operating system, server software applications.

NEXIO
System Hardware
The system hardware can be grouped under the following categories:
Work Station
The work stations are located in the areas where the application is used such as ingest.
Server Chassis
The individual server chassis each include the following elements:
I/O – Inputs and Outputs
Physical video, audio, communication and control ports are located on the rear panel for all
server chassis hardware.
Processors
The server chassis have input Codec (encoders) boards with fast processors that convert the
input video/audio signals to a digital file for storage. Another Codec (decoder) is used to
convert digital files from the central storage to the required video format for playback via the
chassis output spigots.
Raid Controller
The way the digital file streams are sent and retrieved from the central storage is controlled
by the software RAID controller known as RAIDsoft. RAIDsoft also organizes backup parity
data used in the event of data corruption to enable rebuilding and retrieval of essential data.
Harris uses it’s proprietary RAIDsoft software RAID controller running on every server
chassis (if applicable) to maximize redundancy and flexibility. Because RAIDsoft is running
on each server chassis there is no single point of failure for the RAID controller and the
multiple versions of RAIDsoft can work together to speed up rebuilds.
Database
A list of all media stored on the central storage is required. This database/list (MediaBase) is
updated immediately whenever new media is ingested or unwanted media is deleted. The
main MediaBase is located on the central storage area with versions of MediaBase also
stored on every server chassis (if applicable). All versions of MediaBase are kept in sync and
up to date by regular communication over the Gigabit Ethernet network.
Networks
The Ethernet networks consist of the Nexio LAN and the Transfer LAN.
Fiber Channel Network consists of the fiber optic transfer of media between the storage area.
For external server storage area applications Harris uses high speed optical Fibre channel
networks to transfer the compressed video and audio data streams, to and from the
Input/Output chassis Codec’s and the shared central storage. A Gigabit Ethernet network is
employed for communication, networking all server chassis and the storage area network to
keep the MediaBase information up to date.
Storage Area
The storage area network consists of one or more drive array enclosure (DAE) chassis
containing multiple physical disks. The physical disks are where the digital video, audio,
graphics, meta-data, parity data and the servers’ database are stored.

NEXIO
Servers
The following are a list of our Windows XP legacy transmission servers:
 Transmission
o SD: 4000
 2 channels or 4 channels
 channels are either ingest/playout, or play-only (in pairs)
o SD: 3600
 2 record and 4 playback
o HD: 3600/4200
 4200 Series: 1 ingest/playout, 1 play-only channel
 3600 Series: configurable up to 1 ingest, 2 playout ports
o SD: 3601
 2 Bi-directional – 2 playback
o HD: 3601
 3601 Series: 1 ingest/playout, 1 play-only channel
 3601 Series: configurable up to 1 ingest, 2 playout ports
o SD: 3801
 2 Bi-directional – 2 playback
o HD: 3801
 2 ingest/playout, 2 play-only channel
 1 ingest, 2 playout ports

NEXIO
Speciality Servers Overview

NEXIO
Speciality Servers Overview - continued

NEXIO
Harris News Solution

NEXIO
Specialty Servers
Beyond the core models, other system needs may require the features found in the following
servers:
Editing Servers
Velocity is a non-linear desktop editing and special effects software package for the NEXIO line of
broadcast solutions. The strength of Velocity is its flexibility. You can customize your interface to flow
in the manner most efficient for you including customizing keyboard shortcuts and default GUI
layouts. With Velocity, you can interface with NEXIO servers to manage projects and ingest video
source material. You can work with a wide range of digital video, audio, image and animation files. In
addition to the wide range of transitions and effects included with Velocity, you can also create
customized transitions and effects. By using Velocity, you have many output options, including DVD,
web distribution, direct digital output, and printing to DVD and videotape.
NEXIO 3000ESX editing server
Velocity Express Card

This card is installed as an option for Newsroom and Editing systems.

NEXIO
Newsroom Systems
Hi-Res Editing – HD Option 1
The Velocity Express Card option, also known as the hardware option, allows editors to record video
from multiple sources such as feeds and VTRs into the raid storage.
o NX3000ESX Chassis + Velocity Express Card + Velocity ESX Software
Hi-res Editing – HD Option 2

The Velocity software option only allows the editor to create projects using clips from the raid storage.
o NX3000ESX Chassis + Velocity ESX Software
Hi-Res offline editing

The XNG Laptop option gives the editor the flexibility to edit on a remote location and to transfer clips
to the SAN via a network connection.
o Laptop (Customer Supplied) + Velocity XNG Software
NXA1000VESX
Software-only version of Velocity ESX installed on a customer supplied PC that meets or exceeds the
minimum system requirements. Shares all the same software features as the turnkey system minus
the hardware I/O capabilities and the bundled VST audio filters and custom keyboard. Capture and
print to tape is limited to DV and HDV formats via firewire. Velocity ESX can also be used with select
3rd party firewire I/O devices, allowing baseband input and output in a variety of formats. Intelligent
playout eliminates any rendering for cuts only edits maintained in the native format.
NX1011VESX Software-only version of Velocity ESX require software release 2.5 or higher
Requires Gigabit Ethernet for connection to SAN via MIOH topology.
NX1011VESX-FC
Velocity ESX hardware-based turnkey system is built on 1RU platform. Provides Fibre Channel or
Gigabit Ethernet for connection to SAN. Bundled with Velocity software and custom keyboard.
NXA-VEL-DNXHD
Velocity ESX or Velocity XNG with Avid DNxHD codec for playback only of DNxHD content from
NEXIO SAN or local MOV files. Must be used in conjunction with Velocity 2.5 or higher

NEXIO
NXA-VEL-3D
Stereoscopic 3D editing and conforming software license key option for Velocity ESX. Must be used
in conjunction with Velocity 2.5 or higher
NX1011VESX-SDI
Provides SD/HD-SDI and analog I/O as well as AES, Genlock and RS-422*. Gigabit Ethernet for
connection to SAN. Bundled with Velocity software and custom keyboard.
Model Number: NXA-VEL-BMIO
Hi-Res conforming/rendering
The Instant On Line (IOL) server conform timelines from the Low-Res PRX editors into Hi-Res. The
IOL is capable of rendering project from Velocity NLEs and can convert different file format into LXF
just by dropping the clips into the pending cue folder.
o IOL Chassis + IOL “Instant Online” Software

NEXIO
NX1011IOL Ethernet Connection
Takes timeline from Velocity, FCP, Invenio or 3rd party EDL/XML and conforms it to high-
resolution content residing on NEXIO SAN. Provides Gigabit Ethernet for connection to
SAN.
NX1011IOL-FC Fiber Channel Connection

NEXIO
Playout Control – GUI

The MPLM is used to load the newsroom rundown and play the news stories on-air. The MPLM can
control up to four channel and can simultaneously trigger two channels, on-air and protect channel for
each played story.
o MPLM “MOS Playlist Manager”
NXAMPLM
The MPLM software application is sold and customer can provide their own Windows 7 PC.
NX1011MPLM
The MPLM software is also sold with a NX1011 chassis.
Playout Control – Gateway

The MOS Gateway server is responsible for directing the MOS information from NRCS, NXMB (a
database active X plug-in the newsroom client PCs), the SAN Mediabase, and MPLM.
o MGX Server + MG “MOS Gateway”
NX1011HMG

NEXIO
NEXIO Proxy Browse (Low-Res) Systems

Velocity PRX – Proxy Editor
With Velocity PRX, you can interface with NEXIO servers to create low-resolution edits, which can be
conformed using NEXIO Instant Online III. The low-resolution edits can also be finished on a Velocity
ESX high-resolution edit station or on a Final Cut Pro high-resolution edit station.
The PRX Velocity computer is usually provided by the customer but Harris can also provide a
computer.
PRX Player – Proxy Player

The PRX Player application permits H.264 Low-Res browsing of Hi-Res content, clips can be
selected from a mediabase list.

NEXIO
NXMB – NEXIO Mediabase

The NXMB application is launch from an active X window within the newsroom client PC; it receives
constant database updates, and allows newsroom personnel to create empty IDs.
PTCD – NEXIO Proxy Transcoder

The H.264 proxy files generated by the NX1010PTCD are then available for browse viewing with
PRXPlayer or though the NEXIO Mediabase plug-in (NXMB), when used with a NEXIO MOS
gateway. These proxy files are also available for simple editing with the Velocity PRX proxy editor.
NX1011PTCD
Proxy Media Host

The Proxy Media Host can host 30 PRX Players and 30 PRX editors. The proxy media host also has
a license application that restricts the amount users that can access the Lo-Res media in the LRS.
NOTE: Proxy media host is not used with current solution, currently we use a map drive to
store the low resolution H.264 clips.

NEXIO
Encoder – Low-Res Encoder

The Encoder program resides in the NEXIO server and its capable of creating low resolution proxy
files from clips that are currently being ingested by a NEXIO AMP ingest channel.
Media Transfer and Management

MS – Mirror Streamer
The MS Server can be configured to transfer clips from domain A to domain B, domain B to domain
A, or bi-directional via fibre channel connections between domains.
CM – Content Manager
The CM application runs on a NEXIO Server and can be configured to transfer clips from domain A to
domain B, domain B to domain A, or bi-directional via gig Ethernet connections between domains.
The CM application can be configured to transfer to a near line storage (NLS) device. The CM can
go on a stand alone on a NEXIO Server.
FTP – FTP Client

The FTP client application can be configured to do manual transfers between domains, folders, P2
decks, XDCAMs, or NLS. The FTP client connects to the FTP Server to move clips to or from the
raid storage.
FTP Server NX1010MGX is solely used for transferring clips into the storage raid:
FTP Server NX1011MGX-GE or NX1011MGX-10GE

NEXIO
Other Server Solutions

NAV – NEXIO Navigator CCS
NEXIO Navigator is a remote monitoring solution that tracks server, raid storage, and
terminal gear errors and notifies facility engineers. The NEXIO Navigator is supplied by the
customer.
MGX - Expander Chassis

The expander chassis configuration is used when fiber channel connections are not
available, system bandwidth can still sustain another NEXIO server, and it allows access to
the video clips via an Ethernet connection to another NEXIO server which has access to the
video via fiber channel connection to the storage.
The Velocity NXA1000VESX or NX1000VESX can be configured as expander configuration

connecting to a NXAMP3801HDI server models.
MIOH - Media Input Output Host

The logical data connections are distributed among the population of MIOH frames via a
redundant network connection from a NEXIO server (client) to two different MIOH servers.
Client connections to the MIOH frames such that failure of an MIOH frame will result in an
even distribution of additional load to the remaining MIOH frames.
NX1011MIOH-10GE or NX1011MIOH-GE

NEXIO
FCP - NX1000FCP
The NX1000FCP is capable of hosting four final cut pro edit bays to have access to he SAN
media and render projects to the SAN.
NX1011FCP-10GE or NX1011FCP-GE
ICM - NX1000ICM
ICM uses direct and indirect communication with devices. Direct communication is made to
IP-ready devices such as the NEXIO servers and DPS synchronizers. Indirect
communication is sent over IP to the Device Server for translation to serial devices such as
routers, VTRs, and GPIs.
The new ICM model number is NX1011ICM and shipped with the above chassis.

NEXIO
NXR – NXRemote
The NEXIO Remote is can control six server channels. NEXIO can be brought with playlist,
delay or ClipSync option. This application can run on any Windows XP or 7 machine.

NEXIO
Software Overview
Before examining the NEXIO 3601HDX/3601HDI server in detail, we’ll take a quick tour of
the servers software interface.
LLM
The LLM provides system connection information, raid storage access, and manages the low level
communications. It provides the following:
 Confirmation the NX3601HDX is connected to additional systems by viewing information in
the Nodes area.
 The logical disk indicates the server is accessing the raid storage device.
 Manages the low level communications between the storage devices and the video/audio
codec’s.
 Manages communication with other NEXIO server nodes, automation systems, and tape
machines.
 Handles the storage and retrieval of audio, video, and ancillary data to and from the storage
system.
 Can be used to check codec status, verify that the server is connected to your storage, verify
that the server is connected to your NEXIO network, and view disk performance.
Nodes
Physical
Disks
Logical Disks

NEXIO
Ingest - ICM
The Device Server is an independent software server that bridges the gap between the network and
serial devices. The ICM client communicates over internet protocol (IP) to all hardware devices.
ICM uses direct and indirect communication with devices. Direct communication is made to
IP-ready devices such as the NEXIO servers and DPS synchronizers. Indirect
communication is sent over IP to the Device Server for translation to serial devices such as
routers, VTRs, and GPIs.
Similar to NEXIO Lower Level Module (LLM), the Device Server functions as the hardware
controller for ICM. The Device Server can manage IP communication from hundreds of
clients simultaneously.
The ICM Server can control:

 Maximum 16 Leitch server channels controlled via Ethernet connection.
 Maximum 16 serial-controlled devices (including VTRs and Routers) with the following
protocols:
 Sony serial protocol for VTRs: ICM supports VTRs that support the Sony protocol.
 Leitch routers (all makes and models)
 Probel routers (General Remote Control Protocol)

NEXIO
 Sony routers (Cart +)

 GVG routers (GVG-7000)
 BTS routers (ASCII)
 Pesa routers (CPU Link Protocol #1)
 N-Vision routers (NV9000)
 Maximum 16 synchronizers controlled via Ethernet
Digitize
This window is the main controller for an external VTR connected to the video server. In addition, the
capability exists here to create a new entry into MediaBase and record desired material from a tape
into that ID in a frame accurate manner. Operation of the transport controls are the same as that of
the channel window, except for lack of a record button.

NEXIO
Crash Recording
The Add ID function is used to create new IDs for recordings. This does not create the new material;
the material fills in this ID when you use the record function.
Playout
PlayList provides clip playout capability on as many as four NEXIO™ channels simultaneously. Use
PlayList to do the following:
 Provides playout up to 4 channels simultaneously.
 Build a list of clips for sequential or timed playback
 Create loop lists
 Trigger GPI events during playback
 Import traffic files
 Store playlists to disk
 Timed GPI events
You can open multiple PlayList windows simultaneously. However, only one PlayList window can be
assigned to a server channel at a time.
Old Playlist:

NEXIO
New Playlist:

NEXIO
ClipSync
ClipSync is an optional application in NXOS that lets you synchronize two channels. This lets two
channels act as one single channel. ClipSync is used for applications that use moving or animated
linear keys that are comprised of both key and fill channel information. ClipSync synchronizes the
animated key and fill channels so they act as one channel.
Delay
NEXIO™ Delay is an application in NXOS that lets you create a delay for your play-to-air content.
You can specify the program ID, target delay times, and additional buffers for delay manipulation.
Once the parameters are set and the record mode is selected, Delay automatically outputs the
delayed video after the countdown timer has expired.
Delay is capable of 1 record and up to 3 play outs or 2 records and 2 playouts on a four-codec
system. For a two-codec system, only 1 record and 1 play out is possible. A codec used to record will
be referred to as a Recorder. A codec used to play out will be referred to as a Player.

NEXIO
New Delay Software GUI

NEXIO
NX3601HDX / HDI G2 or Higher Models Software Options

NEXIO AMP ChannelView
Optional software that provides multiviewer I/O monitoring, enabling up to two NEXIO AMP inputs and
four NEXIO AMP outputs to be viewed in real time.
The benefits of ChannelView compatibility with CENTRIO™ are:
 Similar GUI. Familiar product interfaces and features between CENTRIO™ and ChannelView.
 Common Roadmap. New CENTRIO™ features are feature candidates for ChannelView.
 Common Layout Designer Application. This is used to customize layouts for either product.
Logo Inserter
The Logo Inserter option allows the display of screen logos directly from the NEXIO server.

NEXIO
Quiz 1 System overview

1. List at less three inherent functions A NEXIO server can be used for?
1.
2.
3.
2. List at least three options a NEXIO server can perform?
1.
2.
3.

NEXIO

NEXIO
Tech Guide System Architecture
System Architecture
The fibre channel systems below where designed to meet customers need. The current fibre channel
chassis use is the Xyratex SBOD chassis which are capable of 4, 2, or 1 Gbps data transfer. The
previous chassis Xyratex JBOD chassis which are capable of 2 or 1 Gbps data transfer.
Typical Systems
3601HDX Redundant Fiber Channel
Servers offer a level of fibre channel redundancy that was previously not available. This is due
to their use of the ATTO Celerity Fibre Channel card with its dual fibre channel ports. With these
dual ports, in a direct connect configuration, each server can be connected to both loops on the
drive arrays. Now if the connection from the server to one of the array loops is lost, the server
will still have full fibre channel functionality via the other loop.
Multi Drive Max Allowable Configuration

Six fibre channel drive chassis is the maximum amount of chassis that can be daisy chained.
Redundant fibre server system with Fibre switches

The difference in the hardware configuration is fiber channel switch which provides a better bandwidth
management.
Redundant direct connect fibre channel system

The redundant direct server system provides a failover path for fibre channel communication.
FARAD Storage Solution

FARAD solution provdes Raid 601 protection where every LUN of 6 can loss 2 drives and the LUN also
copied on another drives.
NX3000VNES
Velocity Edit station.

NEXIO
Redundant Fiber Channel Drawing

NEXIO
Multi Drive Max Allowable Configuration
Redundant fibre
server system with
Fibre switches

NEXIO

NEXIO
FARAD Storage Solution

NEXIO
Direct connect fibre channel system

NEXIO
NX3000VNES connections

NEXIO
Quiz 2 System Architecture

1. Draw a four SBOD fibre channel chassis with three NEXIO servers direct connect.
2. Draw a four SBOD fibre channel chassis with three NEXIO servers interfacing with a fibre
channel switch.
3. How many SBOD fiber channel drives can a direct connect or fiber switch system support?
4. What is the approximatement bandwidth of a direct connect fiber channel SBOD system
support? How many drives?
5. In a FARAD storage system up to what number chassis gives you bandwideth and storage?
6. After what chassis number gives you storage but not no bandwideth in a FARAD system?
7. How many stacks are supported in a FARAD system?
8. How many fiber channel (SBOD drives) nodes can a fiber switch system support?
9. How many fiber channel (SBOD drives) nodes can a direct connect system support?
10. How many fiber channel nodes can a FARAD system support?

NEXIO
Tech Guide Server System Components
Server System Components

A server system can be broken down into three general areas:
 Servers – hardware and software
 Fibre Channel
 Ethernet
Server Hardware
Most technical personnel have a reasonable knowledge of basic PC technology. By
building on this common knowledge in a logical progression, servers can be explained in
a way that can be more readily assimilated.

NEXIO
Generic PC Hardware
NX3601HDX, 3000VESX Models, & NXAMP3801HDX Hardware
Tyan S2915 Motherboard
The NX3801 server use Tyan S2915 Revision E motherboard and BIOS firmware version 4.0.x or
higher.
We’re cuurently using the Opteron CPU processor.

NEXIO
Tyan S2915 Motherboard fan connections
FAN1 (short lead)

→ SYSFAN2
FAN2 →
SYSFAN3
FAN4 →
SYSFAN1
FAN3 →
SYSFAN0
These four fans are connected in the server mid-section plane for cooling the motherboard and all
its components.

NEXIO
NX3601HDX S2915 MB
NXAMP3801HDX Hardware Tyan S2915 Rev. E MB Specification

Hardware Specifications - One x16 from NPF3600 PRO
Processors - One x16 from NPF3600 PRO with x8
Dual 1207-pin ZIF sockets signal
Supports up to two AMD Opteron - One x16 from NPF3050 with x8 signal
2000 Series processors • Two (2) PCI-X 100/133MHz slots from
• Two onboard 5-phase digital VRMs NEC nPD720404
Chipset • One (1) PCI 32-bit 33MHz slot
• NVIDIA NPF3600 + NPF3050 • Seven (7) expansion slots total
• NEC nPD720404 PCI-X tunnel • Front panel audio header
• SMsC 5307 Super I/O controller • CD-in, Aux-in headers (4-pin
Integrated I/O configuration)
• One 9-pin 16550 UART serial port Integrated SAS Controller (for
• 10 USB 2.0 ports (6 at rear, 1 internal S2915WA2NRF only)
Vertical connector and 3 front ports • LSI 1068E SAS controller
Via optional cables) • Eight SAS ports
• PS/2 mouse and keyboard connectors BIOS
• 6 SATA-II connectors • Phoenix BIOS on 8Mbit LPC Flash
• Dual RJ-45 10/100/1000 LAN ports ROM
•One IDE and one Floppy connectors • Supports ACPI (S0, S1, S3, S4, S5)
System Management • Serial console Redirect
• CPU thermal & voltage monitor support • PXE via Ethernet, USB device boot
• Six 4-pin fan header (PWM and • PnP, DMI 2.0, WfM 2.0 Power
Memory Management
• Dual-channel memory bus • User-configurable H/W monitoring
• Eight DDR2 sockets (four per CPU) • Auto-configuration of hard disk types
• Supports ECC Registered DIMMs • Multiple boot options
• Maximum of 32GB DDR2- • 48-bit LBA support
400/533/667 Regulatory
Integrated Network Processor • FCC Class B (DoC)
• Two GbE via Marvell PHY 88E1121 • European Community CE (DoC
• Supports WOL and PXE
• Two RJ-45 ports with LEDs
Integrated FireWire (1394a) Controller
• TI TSB43AB22A 1394a PCI controller
• 1394a channel for rear (connector)
• 1394a channel for front (header)
Integrated Audio Controller
• HDA link
• RealTek ALC262 controller (High
Definition Audio)
• Line-in, Line-out, Mic-in rear ports
• SPDIF-out in rear
tachometer support)
• One 2-pin chassis intrusion header
• Watchdog timer support
Expansion Slots
• Four (4) PCI Express x16 slots
- One x16 signal from NPF3050

NEXIO
BIOS Update and Settings

Updating the NX3601 & NXAMP3801 BIOS
 If you already have a CD with the bootable BIOS image, insert it in the CD/DVD ROM drive and
restart the system.
 If you don’t have the most current bootable BIOS CD, you can burn an image via the
Tyan2915_102.iso file found in C:\As Shipped\Driver Backups\System Setup…”. The BIOS image
file can also be found on the Harris network under:
o \\BurApp1\DirEng\ Wolverine\NX3602\BIOS
 The bootable BIOS CD will automatically run the BIOS update when the system is booted. If the
CD doesn’t run, Press F2 to enter the BIOS and verify the CD/DVD drive is the first item in the
boot sequence.
 After updating the BIOS, press F2 to enter setup.
o Left Arrow to the Exit menu and select Load Setup Defaults. Answer Yes to load defaults.
o Adjust only the settings as detailed in the following page.
 TYAN S2915 BIOS 1.02 SETUP

o Advanced -> Hammer Configuration -> ECC Options
 ECC Mode = Basic
 Advanced -> Hammer Configuration -> Memory Controller Options
o Memory Hole Remap = Disabled
 Advanced -> Hammer Configuration
o Node Interleave = Auto
o Dram Bank Interleave = Auto
 Advanced -> Integrated Devices -> NV Raid Configuration
o NV Raid Configuration = Enabled
o SATA Port 0 Raid = Enabled
o SATA Port 1 Raid = Enabled
 Advanced -> Floppy Configuration
o Legacy Diskette A = Disabled
 Advanced -> PCI Configuration
o OPROM SCAN Order = Add-on fir
 Advanced -> PCI Configuration -> Integrated SAS Controller
o Integrated SAS = Disabled
 Boot -> Boot Device Priority
o IDE CD: Optiarc CD-RW
o PCI SCSI: HD or Ary01 NVidia Mirror*
 Power
o ACPI S3 = Disabled
o After Power Failure = Stay Off
Note: Once changes have been made based on the above, Press F10 to save and exit.

NEXIO
SATA Connections
SATA 1
SATA 0
(from drive closest to wall)
The boot drives are mirror SATA drives.

NEXIO
SATA Mirror
3601 & 3801 SATA Mirror Set
 Navigate to c:/vr/utilities and run LLMDiskTool.exe. Select disable.
 Restart server and then press F2 to enter BIOS.
o Under Advanced -- > Integrated Devices -- > Scroll down to NV Raid Configuration.
 The following should be enabled:
o NVidia Raid Configuration - Enabled
o SATA Port 0 RAID - Enabled
o SATA Port 1 RAID – Enabled
o Hit F10 to save and exit BIOS.
Creating a mirror raid
1. Press 'F10' when the "Nvidia RAID IDE ROM BIOS" or Media Shield Rom BIOS prompt appears
during POST. In the NVIDIA RAID Utility create a mirrored drive manually as follows:
2. Under the Free Disks column, right arrow to add both disk to the array (array drives should be
listed 0.0 and 0.1)
3. Set the Raid Mode to, Mirrored
4. Press 'F7' to finish
5. At Existing disk data will be lost: Continue? Press ‘Y’
6. At, Clear MBR prompt press ‘N’.
7. Press Enter, then [R] and select Port 0.1 (second port).
8. Press F7.
9. Press Enter at the “Rebuild Array?” prompt
10. Press ‘Y’ at the Existing data will be lost prompt.
11. Press Enter, then CTRL-X to exit.
12. System will now restart.

NEXIO
Table: Servers – Generic PC Hardware Generations

Baseline Cores
Total Memory CPU
Platform Gen Software Motherboard CPU Name CPU per Windows
Memory Modules GHz
Release CPU
4200HDX 1 2.5.0 Sledgehammer Opteron 2.4 1
2 3.1.1 Iwill DK8N Opteron 252 2.6
Beta 3.1.1 4GB 4x 1GB Opteron 250 2.4 32-bit
1 3.3.1 Kingston Troy
3600HDX 2 3.5.0 SuperMicro 2
Opteron 252 2.6
1b/2b 4.1.1 Iwill/
SuperMicro
1c/2c 5.7.0
8x 1GB
1 4.1.0 Kingston Santa Rosa Opteron 2220 2.8
Tyan S2915
4x 2GB
2a 4.5.0 8GB
SMART
3601HDX 2b Barcelona Opteron 2356 2.3 64-bit
4
2c 5.0.0 4x 2GB
Kingston
3a 5.5.0 Shanghai Opteron 2387 2.8
Tyan S2915-E
3801HDX 3b 5.7.0
Istanbul Opteron 2435 2.6 6
4 6.0.0
8x 2GB
Beta 5.7.0 16GB Kingston Shanghai Opteron 2387 2.8 4
1401VOLT SuperMicro
1 5.7.0++ Istanbul Opteron 2435 2.6 6

NEXIO
Video/Audio Input/Output
video and audio input/output only; for servers using software codec
• 3600/4200HDX/I Models: Matrox X.mio

NEXIO
• 3601 Model: MA200

• 3601 Model MA200Q Accelerator Card

NEXIO

NEXIO

NEXIO

NEXIO
3801 Model: MA400
This I/O board has the same video and audio specifications as the MA200 card.

NEXIO
ATTO FC-42XS Dual Optical Port 4Gbps HBA
1st Gen HD servers sharing storage – 4 Gbps-capable ports): Atto FC-42XS
Fabric Specifications
 Dual independent FC ports
 4-Gigabit FC data-transfer rates
 800 MB/sec. maximum full-duplex throughput per channel
 Supports all FC topologies: direct fabric, arbitrated loop and point-to-point
 ANSI Fibre Channel: FC-PH, FC-FCP, FC-AL, FC-AL2, FC-PLDA, FC-FLA
 Flash ROM for easy field upgrades
 FC Class 3 Support
 Buffer Credits: 8 @ 512 Bytes; 8 @ 2KB
 Advanced Data Streaming (ADSTM) Technology
Advanced FC Capabilities:
 Backward compatible with 2-Gb and 1-Gb Fibre Channel
PCI Bus Specifications:

 x4 mechanical and x4 electrical PCI Express interconnect
 Supports PCI Express Base Spec 1.0a
 Supports PCI Express CEM Spec 1.0a
 PCI Express to PCI/PCI-X Bridge spec 1.0
Optical Cabling:
 50/125µm up to 100m @ 4-Gbps, 2-Gbps, and 1-Gbps

NEXIO
Dimensions
 Conforms to PCI Express Low Profile form-factor specifications
 Length 5.600”
 Height 2.712”
Electrical
 12V @ 0.4A max
 3.3V @ 1.5A max
NX3601 G2 and higher servers sharing storage – 4 Gbps-capable ports: Atto FC-4xES
NX3801 servers sharing storage – 8 Gbps-capable ports Celerity FC-82En
This card is used in FARAD fiber channel systems.

NEXIO
SCSI
1st gen HD servers with internal storage: Atto ExpressPCI UL4S
This card is used in the NX3600HDI servers.
ATTO ExpressSAS348 HBA - HDI server
This Card is used in the NX3601HDI servers.
SAS Specifications
• Up to 3-Gb/sec per port
• Device support for SAS, SATA and SATA II
• Support for RAID levels 0, 1, 4, 5, 6, 10, 40, 50, 60, JBOD and DVRAID
• On-line capacity expansion
• Native Command Queuing
• Cache memory—256MB ECC protected memory
• User friendly GUI for RAID setup
• External LEDs for on-line status

NEXIO
Atto H30F NXAMP3801HDI
This has been replaced by the H60F Atto SAS card.

NEXIO
Atto H60F NXAMP3801HDI

NEXIO
AfterBurner-3 Boards
JMP2
JMP1
Upper Assembly
JP1
Lower Assembly USB
JP2
Note that
ONLY the
BOTTOM AB-3
has a jumper at
this location.

NEXIO
Specifications

NEXIO
Pin out tables

NEXIO

NEXIO
Afterburner 3 GPI Circuit

NEXIO
Afterburner 3 Features
 USB 2.0 Full Speed support
 Powered directly from USB
 “Slot less” design, no PCI slot used
 Four serial ports offering full duplex buffered I/O operation
 Serial ports will be hard configured for four slave mode ports.
 Total of four RJ12 connectors.
 DB9 to RJ12 Adapters to be provided with SMPTE pin-out.
 Baud rates up to 115.2K baud for all serial channels
 Capable of at least 1.5Mbps data throughput
 Harris VDCP pin-out connections on all RS422 serial ports
 8 - Discrete relays with both normally open and normally closed contacts
 16 - Opto-isolated inputs for either TTL or dry switch input with internal and external power and
isolated grounds
 Lead free components
Block Explanation
 USB-B:

NEXIO
o This is the input USB connection via USB–B receptacle on PCB.

 USB-MicroP:
o This is a NetSilicon NS9360 USB capable embedded processor:
o 50 GPI I/O
o 23 GPI/O multiplexed with other functions
o Programmable wait states
o Programmable timers
o Programmable interrupts
o Ethernet MAC
o Memory Controller
o LCD Controller
o 4 UARTs
o ThreadX RTOS support
 Voltage Stepdown/Regulator:
o Voltage regulation for the 5V, 3.3V, and 1.5V requirements of all the devices.
 jtag:
o JTAG port used for real-time debugging. This is a 20pin IDC connector.
 Memory SDRAM:
o This block contains SDRAM modules for fast memory access such as cache memory and
data buffers.
 FLASH:
o This block contains a flash that connects to the embedded processor and is used for boot
up and configuration.
 UARTS:
o This block consists of four UARTs compatible to ST16C550 UART, which are capable of
1.5Mbps data rate. A total of eight UARTS are required, but four are internal to the
embedded processor. UARTs can be integrated into the embedded processor and
external as well. Possible device could be used is an Exar XR16L784 quad UART or a
MAXIM 3096/3030E combination. .
o RS422 Line drivers:
o This block consists of quad differential line drivers. Must meet TIA/EIA-422-B
requirements.
o Compatible devices include.
o Transistor Array Relay Driver:
o This block contains a high current Darlington transistor array. This provides enough
current to energize the relays. Compatible devices include the Texas Instruments 2803A,
which has eight 500mA sink outputs.
 Relays:
o This block consists of eight “C” type contact or reed relays.
 OptoIsolator:
o This block consists of octal transistor output optoisolators. Four Fairchild MOCD207M
dual phototransistors will be utilized.
 GPI In/Out:
o These blocks consist of four High Density DB26-pin connectors. Compatible connectors
may include NorComp part no.195-26-213-031.

NEXIO
AB3 I/O BOARD TEST PROCEDURE
Do the AB3 I/O board test on NEXIO platform before troubleshooting with ADC control problem.
AB3 I/O BOARD TEST

Exit the NXOS, FTP and LLM before you run the IOTesterV2.exe.
Open Windows Device Manager and verify that there are two occurrences of the HARRIS
AFTERBURNER 3 device under USB Controllers.
If HARRIS AFTERBURNER 3 device display missing on the Universal Serial Bus Controllers, you need to
verify that the AB3 power connector are installed correctly, some case the power connectors are off on
the chases side.
You need have two RJ12 test loop cable to do the AB3/IO test.
1. Disable the second device by right clicking and selecting disable.

2. Connect one RJ12 loop back from COM PORT 1 to COM PORT 2. (On top B3 panel.)
3. Connect one RJ12 loop back from COM PORT 3 to COM PORT 4. (On top B3 panel.)
4. Open “System Test” and then “AB3 Tester” folder on the C:\ drive (You also can find it on the
install folder.).
5. Double click to run the IOTesterV2.exe
6. Verify the COM Ports are selected.
7. Click “Run Selected Port Test”.
8. Did the port test pass or fail? (As indicated on the main screen upon completion, the status
messages box and report). If failed, perform standard troubleshooting.
9. Re-enable the AB3 in Device Manager. The test loop cable pin assignment sees below.
Orange 1 ----------- 4 Orange

Orange/White 2 ----------- 3 Orange White
Brown 3 ----------- 2 Brown
Brown/White 4 ----------- 1 Brown/White
Blue 5 ----------- 5 Blue
Blue/white 6 ----------- 6 Blue/ White

NEXIO
Lab 1 – Afterburner card test
1. Connect faculty supplied cable from COM1 to COM2 and from COM3 to COM4. Also use the GPI
input and output cable, connect as labeled. Now run the IOTeseterV2.exe application and select GPI and
RS422 test, run test. Did the test pass or fail?
2. Now lets use the standard faculty supplied cables to perform RS422 test.

NEXIO
Pro-panel Assembly

NEXIO
Rear Chassis
SERVER EXPRESS
FIBRE
CARD
Filler Panel
Filler Panel
VIDEO
CARD
Filler Panel
Custom slotted filler panel

w/ audio cable coming
through.

NEXIO
Pro-panel boards
USB
Video
Audio
Lab 2 – Physical inspection

1. Open the NEXIO server and inspection the corresponding parts.

NEXIO
Fibre Channel Drive Array Enclosure (DAE)

The Nexio server line utilizes the Xyratex drive array enclosure to house fibre channel drives for shared
media storage. These systems may have one or more of these DAE chassis.
Each fibre channel drive in the chassis is housed in a carrier or sled that mounts horizontally:
Xyratex’s drive numbering is zero-based, so a chassis starts at 0 and ends at 15. Harris’ drive numbering
is base 1, so a chassis starts at 1 and ends at 16.
The rear panel shows dual supplies to the left and right, with input/output modules and control panel in
the middle:

NEXIO
Below is a close-up of the key modules:

 2 fibre channel input/output modules called Loop Resiliency Circuit (LRC)
 1 Operator/Control panel or Ops Panel
Each LRC input/output module provides access to one of the two fibre channel ports that each drive has.
The left LRC input/output module is LRC “B”. It connects to the “Port B” on each fibre channel drive. The
right module is LRC “A” and it connects to “Port A” on each drive.
The Ops Panel allows some configuration parameters to be set, and provides some status indications.

NEXIO
JBOD Raid Chassis interconnect
The most basic fibre channel configuration is direct connect where as the name
applies, server fibre channel ports are connected directly to drive array ports. In the
simplest of these, a single server can be connected to one array. If a system has more
than one drive array enclosure (DAE), the DAEs can be interconnected with loop
cables using the pattern in the diagram below. Red lines show interconnects between
arrays; blue lines show server connections.
SBOD raid chassis interconnect configuration

NEXIO
Fibre Channel Drive Arrays

External shared video and audio media storage
System Fibre Channel

Fibre Channel Primer
A short conceptual overview of the fibre channel interface will help in the understanding of its key role in
Harris server systems.
The following section is taken from Seagate Fibre Channel documentation:
Fibre channel is a transport vehicle that can process the command sets of several existing
interface protocols, including SCSI-3 and ATM. Fibre channel arbitrated loop (FC-AL) is one
topology used to connect devices within this standard.
Nodes
Fibre Channel devices are called nodes. This is a generic term describing any device
(workstation, printer, disc drive, scanner, etc.) connected to a Fibre Channel topology. Each node
has at least one port, called an N_Port to provide access to other nodes. The “N” in N_Port
stands for node. As you will see later, ports used in a Fibre Channel Arbitrated Loop topology are
called NL_Ports where the “NL” stands for node loop.

NEXIO
The components that connect two or more node ports together are what are collectively called a
topology. Nodes work within the provided topology to communicate with all other nodes.
Ports
Ports are the link to the outside world for a Fibre Channel node. See Figure 2. As stated above,
each node has at least one port to provide access to other nodes. Each Seagate Fibre Channel
drive has two ports. Each port uses a pair of fibers—one to carry information into the port and one
to carry information out of the port. This pair of fibers (actually copper wire) is called a “link” and is
part of each topology. The Fibre Channel ANSI specification also supports fibers made of optical
strands as a medium for data transfer.
Links
Each port is comprised of two fibers; one carries information into the port and is called a receiver.
The other carries information out of the port and is appropriately called a transmitter. Fibre
Channel supports two types of fibers—electrical wires (most commonly copper) and optical
strands. This pair of wires is called a link. See Figure 2.
Links carry the data frames between nodes. Each link can handle multiple frame types; therefore,
frame multiplexing is possible. For example, a frame containing SCSI information may be
followed by a frame containing TCP/IP followed by a frame containing yet another protocol’s
information.

NEXIO
Port bypass circuits

So far, we’ve discussed links, ports, nodes, and topology logins. All’s fine with this model as long
as the loop is intact. What happens, then, if a device is disconnected from the loop? Doesn’t this
break the loop? The answer is no. Fibre Channel provides port bypass circuitry which bypasses
the drive if it is removed, incapable of providing loop services, unable to obtain a valid address, or
otherwise incapable of providing loop services. Loop operation recovers after a brief interruption.
These port bypass circuits (PBCs) are located external to the drive or other FC-AL device. Figure
3 shows the relationship between the PBC and drive.
Several key features make fibre channel ideally suited to video server applications:
1. The ability to hot swap drives

Being able to substitute failed individual drives while the system is in use involves both hardware and
software. The port bypass circuits described above provide the physical level component; Harris’ LLM
software controls the process of taking advantage of this fibre channel feature.
2. Dual I/O connections to each drive “Port A” and “Port B”

Allows for a redundant path, so that the failure of one connection doesn’t mean complete loss of
functionality.
3. High data rates: 1, 2, 4, and now 8 Gbit/second for FARAD storage systems.
4. Up to 125 devices can be connected on one loop
5. Extremely long distances between fibre channel nodes:

10 kilometers for optical interfaces. Although this is the theoretical limit, latency issues in Harris
server systems dictate significantly shorter lengths. The longest cable we currently sell is 80 meters.
Harris server systems use Seagate fibre channel drives exclusively.

NEXIO
Daisy chain SBOD chassis

Large system using DAE looping to integrate multiple DAE chassis

NEXIO
Loop B Loop A
ID3
Drive 3-16
Drive 3-2
Drive 3-1
1 1
2 2
Server 4 Server 3
ID2
1 1
2 2
Server 2 Server 1
Drive 2-1
Drive 2-2
Drive 2-16
This drawing illustrates the data flow in a direct connect, multiple DAE channel drive array
implementation:
Example data flow – recording on Server 1:
 Server 1 port out > ID2 Loop A-2 port in

 ID2 Loop A-1 port out > ID3 Loop A-1 port in
 ID3 Loop A-2 port out > Server 3 port in
 Server 3 port out > ID3 Loop A-2 port in
 Data at this point loops through the chassis’ drives:
o Into Drive 3-1 port in
o Out to Drive 3-2 in, etc.
o Drive 3-16 port out and back to Loop A-1 port out
 ID3 Loop A-1 port out > ID2 Loop A-1 port in
 Loop through all the chassis’ drives and back to Server 1 port in
Servers offer a level of fibre channel redundancy that was previously not available. This is due to their use of the
ATTO Celerity Fibre Channel card with its dual fibre channel ports. With these dual ports, in a direct connect
configuration, each server can be connected to both loops on the drive arrays. Now if the connection from the
server to one of the array loops is lost, the server will still have full fibre channel functionality via the other loop.

NEXIO
With the physical drive array in place, the final piece of the shared media storage puzzle is to create a
logical grouping of the physical drives. This is done using the Initialize function of the LLM module,
resulting in the creation of a Logical Disk. There is a limitation as to how many physical drives can be
included in a Logical Disk. This is why for example there is more than one logical disk – Drive D and Drive
E - in the 4 chassis drawing shown earlier.
All the drives in any one Logical Disk operate in tandem; each drive handles a slice of each video/audio
frame.

NEXIO
Fibre Channel Switch

Systems can be designed to accommodate higher data throughput (i.e. more server channels) with the
use of fibre channel switches. Most fibre channel switch implementations utilize dual switches, which
enables enhanced redundancy also. Harris uses the Qlogic SANbox series of fibre channel switches.
SANbox 2 (NXS1622):
This is a 2 Gbit/second 16-port switch that was originally introduced during the VR4xx Series Production.
SANbox 5600 (NXS1644):
This is a 4 Gbit/second 16+4-port switch that was originally introduced about the same time as the Nexio
HD servers.

NEXIO
8Gb Fibre Channel

NXFS8400 (Brocade 300) FC Switch
NOTE: This fibre channel switch is only used in Farad storage solutions and its data transfer speed is 8
Gbps.
No configuration required just plug and play.

Switches achieve higher overall bandwidth via bandwidth splitting. In a basic multi-DAE loop, all the data
relating to any server or any drive on that loop must travel in series through every server and through
every drive on the loop in the process. For example, data packets going from Server 2 to Drive 12 would
pass through Server 1 and all the other drive chassis and drives in the process.
When a switch is used in a fibre channel loop, data from Server 2 to Drive 12 would not pass through any
nd
other server, and would be split out at the switch and only sent down the cable connected to the 2 array
chassis. The following drawing illustrates a system with SANbox 2 switches using this approach.

NEXIO
Dual Fibre Channel Switch Configurations

SANbox2, Single Server Connection, ISL Failover
Blue and orange lines along the top row of the switches are server connections; blue lines on the bottom
row are DAE connections.
The aqua lines between the bottom left and bottom right ports of the two switches are fail-over
connections. These provide redundancy in the event that a switch-to-DAE connection fails. If, for
example, the cable to the bottom port on the left-hand LRC of the bottom DAE were to fail, servers
connected to the left-hand switch would not normally be able to read and write data relating to the bottom
array. With failover though, the switch can re-route the data, by having it pass through the aqua “ISL”
cable, and from there on to the bottom port on the right-hand LRC of the bottom DAE.
On a SANbox 2 switch, all 16 ports are generic 2 Gbit capable, and ports chosen for ISL connections are
simply custom-configured.

NEXIO
SANbox5600, Dual Server Connection, No Xpak Failover
In this configuration, blue lines above the left switch are connections to each server’s “Port 0”. Pink lines
above the right switch are connections to all the same servers, but on their “Port 1”. Blue lines below the
switches are DAE connections. The above configuration only applies to servers that use the ATTO dual
fibre channel port card.
Here there are no ISL failover connections. This is because if any if top left blue server connections or the
bottom left array connections fails, each server still has access to the array through the top right pink
server connection and bottom blue right array connections (and vice-versa). Redundancy here therefore
extends right back to the server, whereas without dual server connections, it only exists between the
switch and the array.
SANbox 5600 switches can also be run in an ISL type configuration. Servers would connect via a single
port, and the switches would be linked via one of the four larger rectangular “Xpak” ports, which provide a
high-speed 10 Gbit link.

NEXIO
FARAD Fiber Channel Topology
The FARAD fiber channel topology comes with standard intrinsic mirroring and redundant fiber Brocade
300 switches.

NEXIO
System Ethernet
Ethernet is critical to the operation of a server system using shared storage. For this reason, a dedicated
private Ethernet is used for the NexioNet, the 100 Mbps full duplex Ethernet in which the LLM
intercommunication is done. NEVER set Ethernet adapters to Auto Detect, the LLM would use the
transfer LAN if the LLM LAN is disconnected. If 100 Mbps is not available then set the NIC for 1000 Mbps
Full Auto Negotiate.
1 Gigabit Quad Port Ethernet
• Media Host and Client servers Intel Pro/1000 GT
10 Gigabit Ethernet
• Media Host servers – two 10 gigiabit ports: Chelsio N320E

NEXIO
LLM fail over setup

 [HKEY_CURRENT_USER\Software\ASC Audio Video\LLM\Control]
– "IPAddress"="127.22.0.1“
– "IPAddress1"="127.22.10.11"
– "IPSubnetMask"="255.255.255.0"
– "IPSubnetMask1"="255.255.255.0"
– "LLMDomainLetters"="A“
– "LLMNodeNumber"=dword:00000001
The LLM would use the IPAddress1 if the first Ethernet card is disconnected. This can be configured via
the NEXIO configuration wizard.
The NexioNet communication path:

1. allows server Low Level Modules to be instantaneously aware of how other servers have updated
shared media storage (i.e. new recordings)
2. Provides path through which Nexio Remote user GUI application, or 3rd party automation, can
take control of a remote server’s Low Level Module (thus allowing record, playback, etc.)
Layer 3 E Gigabit Ethernet Switches for NEXIO Servers:
NXESD1224X2 from D-Link
Model Number: NXESD1224X2and NXESD1224SPR

The NEXIO product line is introducing a new, lower-cost switch solution for the NEXIO LAN to replace the
entry-level niche formerly occupied by the NXES20024 from Extreme.
Customers with high-performance Ethernet network requirements, MIOH configurations, should consider
the NXES45024/48 Extreme Ethernet switches.
Criteria for selecting the NXESD1224X2 are as follows:
Network primarily used for NEXIO server communications by NEXIO systems supporting
Redundant Ethernet
Occasional to moderate file transfer requirements with no Ethernet teaming for high
performance
Network does not include Final Cut Pro systems connected via FCP Integration Gateway
Network does not support Media Host connection architecture
NXESD1224X2 is not supported for NEXIO networks configured for the following:

NEXIO
Media Host architecture

Use of MGX gateway with teaming for high-performance file transfers
On-SAN editing with Final Cut Pro using the FCP Integration Gateway
xtreme Networks (Summit 450-24t)

Harris PN: NXES45024
Layer 3 Extreme Networks Summit 450-48

Harris PN: NXES45048
Harris is also offering the Extreme Black Diamond 8810 Switch for more complex network solutions.
Harris also offers the Summit 250-24 switch that the ports are hard set at 100 Full Duplex and cannot be
changed.
NXESB624
Brocade FCX624
NXESB648
Brocade FCX648
The Brocade Ethernet switch has four 10 Gbps port and optional 24 or 48 1 Gbps ports.

NEXIO
House Time code Interface

The NXUSBTC is a small non-rack mountable box that accepts analog longitudinal time code (LTC) in,
and outputs a serialized RS-232 level signal. This signal is typically connected to Com Port 1 on one
server. When a server is configured to look for this signal, its LLM reads the incoming time code, updates
its local Windows OS clock with this time every minute, and also distributes this information to all other
running LLM applications in the system, so they can do the same.
The NXUSBTC is used to input LTC time code from a house time code system into standalone and SAN-
based NEXIO video server systems. This allows servers to perform time-of-day recordings with time
code from a single reference source that is locked to the house time code for all servers in a system.
• Situations where absolute timing comes into play are:

o When NXOS Playlist utilizes Absolute Timed Events
o When any logging functionality within the server writes timestamps into the individual log
entries
• Keep in mind that most operations requiring frame-accuracy of playout, have the timing of such
commands determined external to the server.
o For example, an automation system that itself is receiving a house time code reference
signal sends out appropriately timed play commands.
o Since the server has a consistent delay in processing such commands, the automation
system sends them ahead of the desired play start time, such that the server output rolls
at precisely the desired resultant time.
o The server therefore doesn’t need to be aware of house time, because playout frame-
accuracy is determined solely by the automation system that has this information.

NEXIO
NXUSBLTC
Specifications
The NXUSBLTC comes with the following specifications:
 Model. NXUSBLTC
 Power. 1.5 amps at 5 Volt DC (external wall adapter)
 LTC Inputs and Outputs. Standard XLR
 Dimensions. 8L x 6W x 1.725H inches (20.3cm x 15.2cm x 4.4 cm)
 Compliance.
 The NXUSBLTC is lead-free and meets all CE and RoHS requirements.
 TUV, CE mark, & CCC mark approved
 SMPTE RP 188 and EBUTechnical Standard N12-1999 LTC specifications
 Weight. 16 oz. (not including cables) (454 g)
LTC Input Connections:
 LTC Input levels of 100mVpp to 2Vpp are readable.
 LTC Input impedance > Jumper selectable. High impedance or 600 Ohm.
 SMPTE/NTSC and EBU/PAL frame rates 25 fps and 29.97 fps
LTC Output
1.0 Vpp
 LTC Output impedance > Jumper selectable. Low impedance or
 600 Ohm.
 SMPTE/NTSC (29.97 fps) and EBU/PAL (25 fps)
The output LTC signal is phase locked to the reference input, not to the associated video signal. If video
output timing is adjusted on an NX3601 AMP server, it will stay within range of the frame that is indicated
by the time code. The maximum cumulative amount of timing offset in the video signal path must stay
within 30 lines maximum.
The NXUSBLTC Front Panel Connection:

 LTC IN 3 (Secondary Timecode Input). This secondary input would be connected to the house
timecode generator or from the local timecode generator. It is used to set Windows Time of Day
and NEXIO
 Time. This provides Windows time information to the entire LLM network. Planned for a future
release.
 LTC IN 4. This will be a future feature which will support four input channels.
The NXUSBLTC Back Panel Connections:

NEXIO
 LTC IN 1 and 2 (Primary Timecode Input). These primary inputs come from the house timecode
generator or from a local timecode source such as a VTR. Each one is dedicated to a record
channel.
 LTC Outputs. Use the XLR outputs to provide LTC timecode to downstream devices. Each one
is dedicated to a corresponding play channel.
 Ref In. Input for bi-level house reference signal.
 Loop. REF IN loop should be 75 ohm terminated when unused. When not in use, terminate the
Reference LOOP through. Also, see note below.
 Power Source. This is a +5 VDC power 2mm receptacle input. Insert and turn clockwise to lock.
 USB Connection to NEXIO. This is the physical connection between the NXUSBLTC unit and
the NEXIO server that uses the LTC inputs and outputs. It should be connected using one of the
USB cables provided.
To Connect the NXUSBLTC

1 Use the provided power cable and connect the 5V power connection to the NXUSBLTC
module. The NXUSBLTC is not powered by the USB port.
2 Connect the USB connector to an available USB port on the NEXIO server that will use the LTC
timecode input/output device.
The NXUSBLTC is only compatible with NEXIO AMP software release 5.7.0 or later. The two streams of
LTC can be recorded to the NEXIO storage array matching the servers two ingest channels. Auxiliary
input 3 will be used in a future release to lock NEXIO server Windows time to house time reference, as
the NXUSBTC module currently does.

NEXIO
Quiz 3 - System components

1. How much RAM can the Tyan motherboard support?
____________________________________________________________________________________
2. Do we use HASP USB dongles or software license?

____________________________________________________________________________________
3. What raid are the boot drives configure for?

____________________________________________________________________________________
4. How many RS422 ports can the afterburner card control?

____________________________________________________________________________________
5. How many GPI inputs does the afterburner have?

____________________________________________________________________________________
6. How are the RS422 ports set (MASTER or SLAVE)?

____________________________________________________________________________________
7. How many GPI outputs does the afterburner have?

____________________________________________________________________________________
8. What audio sample rate can the server express card support?
____________________________________________________________________________________
9. What sampling rate does the server express card support and which do we use?
____________________________________________________________________________________
10. Can the ATTO Celerity card auto 1, 2, and 4 Gbps?

____________________________________________________________________________________
11. How FC ports does the NEXIO AMP ATTO card have?
____________________________________________________________________________________
12. What is the highest transfer rate for the Xyratex chassis?
____________________________________________________________________________________
13. Draw how would you interconnect two JBOD chassis?

____________________________________________________________________________________
14. Draw how would you interconnect two SBOD chassis?

____________________________________________________________________________________
15. What does SBOD mean?

____________________________________________________________________________________
16. What does JBOD mean?

____________________________________________________________________________________

NEXIO
17. Explain the difference between a direct connect and FC switch system? Explain the data flow?
____________________________________________________________________________________
18. When a fiber channel drive dies what happens to the port?
____________________________________________________________________________________
19. Do you need an ISL connection for a fully redundant FC system? Explain.
____________________________________________________________________________________
20. What is the data transfer speed of the NXS1644 FC switch?

____________________________________________________________________________________
21. What is the main advantage of the Extreme switch?

____________________________________________________________________________________
22. What is the main function of the D-Link switch?

____________________________________________________________________________________
23. Where do you connect the NXUSBTC box and on what numbered server?
____________________________________________________________________________________
24. What is the maximum amount of NEXIO servers that a fiber switch system support?
____________________________________________________________________________________
25. What NEXIO software release do you need to use the NXUSBLTC box?
____________________________________________________________________________________
26. Can the new Brocade fiber switch be used in the xyrtex storage solution (SBOD drives)?
____________________________________________________________________________________
27. The Brocade Ethernet switch replaces what existing Ethernet switch?
____________________________________________________________________________________
28. Does the new Brocade Ethernet switch support 10 Gbps networks? How many ports of 10 Gbps per
module?
____________________________________________________________________________________

NEXIO

NEXIO
Tech Guide System Spec
System Spec
Transmission Video Servers
NX3801 & NX3601 – NEXIO AMP
FIbe
NX3601HDX Raid Storage
NX3601HDX & NXAMP3801HDX Description

 NX3601HDX is a broadcast video server with software-based agile codec for standard
definition (SD) and high definition (HD) video.
 Based on enterprise class high-performance, true 64-bit dual-core processor platform, this
technology allows the integration of mixed baseband SD and HD record and playback directly
into the NEXIO server system.
NX3801HDX Front Panel

NEXIO
NX3801HDX Rear Panel Port Connectors
NEXIO AMP Configurations

NEXIO AMP Generation 5 is available in a variety of configurations.
Model SD Channels Enabled HD Channels Enabled
NXAMP3801HDX1 2 Bi-directional 1 Bi-directional
2 Record + 4 Play Only
NXAMP3801HDX4 4 Bi-directional (not available 4 Bi-directional (not available
with all codecs) with all codecs)
4 Record + 4 Play Only
Note: SD-only channel configurations do not support up/down/cross conversion; Bi-directional

HD is not available with all codecs.
NEXIO AMP Upgrades and Options

Software License Upgrades — The software license upgrades enable additional HD or SD channels,
and optional Media Applications.
NEXIO AMP NXCP Codec Processor Upgrade Kit — The NEXIO NXCP Codec Processor Upgrade Kit
provides hardware-assisted codec support for up to 4 channels of AVC-Intra play out (50 and 100 Mbps)
or 2 channels of AVC-Intra encoding.

NEXIO
Optional Software Applications

Application Description
Remotely administer and control NEXIO video servers from any PC on the same
NEXIO Remote LAN as your NEXIO server.
Event sequencing application that runs on NEXIO NXOS or NEXIO Remote for
NEXIO PlayList media playback.
Create a delay for play-to-air. You can set various parameters and step in and
NEXIO Delay out of delay as needed.
Monitors and provides system-wide diagnostics for NEXIO servers and
NEXIO Navigator associated system components.
NEXIO ClipSync Play back two separate clips together at the same time frame accurately.
Generate a simultaneous low resolution proxy of content being ingested via
NEXIO PRX Encoder baseband.
NEXIO Intrinsic
Mirroring (if
configured in your Optional software that controls and monitors mirroring of
system) volumes on the NEXIO SAN.
Optional software that provides multiviewer I/O monitoring, enabling up to
NEXIO AMP two NEXIO AMP inputs and four NEXIO AMP outputs to be viewed in real time
ChannelView on a computer monitor.
Optional software that enables the display of upto 4layers of static or
NEXIO AMP Logo animated logo graphics per video output. Requires NEXIO AMP ChannelView.
NEXIO Track Optional software for NEXIO Remote and NXOS that
Key Features
The following list outlines some of the key features of NEXIO AMP:
 3RU form factor
 Two Six-Core AMD Opteron 64-bit processors "
 Dual mirrored boot drives
 Dual port 4Gbps Fibre Channel support
 Dual hot-swappable power supplies
 USB ports on the front and rear of the chassis
 IEEE1394 FireWire port
 10/100/1000BaseT Ethernet ports
 Supports up to 96 TB of usable storage with RAIDsoft storage protection.
 48TB=2 logicaldisks consisting of forty-eight 600 GB drives

NEXIO
 96TB=4 logicaldisks consisting of forty-eight 600 GB drives via Media

 Host architecture
 Supports NEXIO Farad shared storage
 Software-based codecs for coding and decoding SD and HD media
 Supports up to 8SDchannels, or up to 4HDchannels
 Supports SD (525i, 625i) and HD (1080i, 1080p, 720p) content on the same hassis
 Supports SDI (SMPTE-259M) and AES/EBU interfaces
 Record and playback SD:
 MPEG-2 l-frame and MPEG-2 Long GOP 4:2:0 profile up to 15 Mbps, and 4:2:2 profile up to
50 Mbps
 IMX 30, IMX 40, and IMX 50
 DVCPRO25 and DVCPRO50
 DVCAM at 25 Mbps (625 only)
 H.264 playback only (optional -requires software licensing)
 Supports HD-SDI (SMPTE-292M) and AES/EBU interfaces
 Record and playback HD:
 MPEG-2 MP@HL l-frame 4:2:0 profile up to 100 Mbps, and 4:2:2 profile up to 150 Mbps
 MPEG-2 MP@HL Long GOP 4:2:0 profile and 4:2:2 profile up to 80 Mbps
 XDCAM HD at 35 Mbps (not available in 720p)
 DVCPRO HD at 100 Mbps
 XDCAM EX at 35 Mbps
 XDCAM HD422 at 50 Mbps
 H.264 playback only (optional - requires software licensing)
 DNxHD (optional - requires software licensing)
 Supports Panasonic AVC-Intra for up to 4 channels of playout with the NXCP Upgrade Kit
 Supports Panasonic AVC-Intra for up to 2 channels of ingest with the NXCP Upgrade Kit
 SD scales to 450+ channels — with NXS3100 Series and 1600+ with NEXIO Farad
 HD scales to 210+ channels — with NXS3100 Series and 500+ with NEXIO Farad
 Integrated up/down/cross conversion support using software based real time processing (HD
licensed servers only)
 Automatic Aspect Ratio Conversion (ARC) using AFD (HD licensed servers only)
 Read, generate, and write continuous and discontinuous VITC
 EIA-608 <> EIA-708 and WST <> OP-47 closed caption transcoding using software based real
time processing (HD licensed servers only)
 Easy integration with IP networks using Gigabit Ethernet for media transfers
 Supports redundant Ethernet, which automatically switches operation from one Ethernet network
to the other, if one Ethernet network fails

NEXIO
 Runs NEXIO operating system (NXOS) software for ingest, playout, file transfers, content
management, and additional optional applications
 Multitier user account access, prevents unauthorized operators from altering video/audio
procamps or deleting media
 Dolby® Digital and Dolby E audio pass-through; record and play
 Off-speed play
 Works with a wide range of 3rd party automation, archiving, and media management applications
 Includes FTP Server to move media from server-to-server and between attached general purpose
drives
 MXF OP-1a
 QuickTime
 AVI
 Native LXF
 MPEG2 PS/TS Ingest
 Pinnacle private audio stream (mixed services with MPEG audio)
Specifications
The following list describes the general specifications for NEXIO AMP:
 Two Six-Core AMD Opteron 64-bit processors
 PCI Express platform
 16 GB RAM
 Two redundant 8 Gb Fibre Channel ports
 Four 10/100/1000Base-T Ethernet adapters
 Dual-head DVI-I monitor interface
 Two USB 2.0 ports on front panel
 Four USB 2.0 ports on back panel
 One FireWire (IEEE 1394) port (not powered) on front panel
 Windows 7 Professional x64
 NEXIO Operating System (NXOS)

NEXIO
NEXIO AMP Video Specifications

Channels SD = SDI (SMPTE-259M)
HD = HD-SDI (SMPTE-292M)
SD Formats 525 @29.97fps 625 @25fps
HD Formats 1080i @29.97fps
1080i @25fps
1080p @29.97fps
1080p @25fps
720p @59.94fps
720p @50fps
SD Aspect Ratio 4:3
16:9
HD Aspect Ratio 16:9
Aspect Ratio Up/down/cross conversion support (SD only)
Conversion EIA-608 <> 708 &WST <> OP-47 caption conversion AFD aspect
ratio conversion Port based aspect ratio conversion User-based
aspect ratio conversion
Audio Specifications
Channels &Formats 4AES/EBU pairs per input channel
4AES/EBU pairs per output channel
8pairs embedded per input channel
8pairs embedded per output channel
Inputs 4pairs HD-BNC, unbalanced (AES/EBU)
75ƒÇ termination
1V p-p nominal levels
Outputs 4pairs HD-BNC, unbalanced (AES/EBU)
75ƒÇ termination
1V p-p nominal levels
Processing &Storage 16, 20, or 24-bit, PCM, 48kHz
Compressed Audio Dolby Digital (AC-3) and Dolby Epass-through

NEXIO
Standard Definition Video Compression Specifications

Compression Profile Resolution and Frame Rate
SD Coding and MPEG-2 l-frame — 4to
Decoding 15 Mbps 4:2:0 525 @29.97fps 625 @25fps
MPEG-2 l-frame — 10to
50 Mbps 4:2:2 525 @29.97fps 625 @25fps
MPEG-2 Long GOP — 4
to 15 Mbps 4:2:0 525 @29.97fps 625 @25fps
MPEG-2 Long GOP — 10
to 50 Mbps 4:2:2 525 @29.97fps 625 @25fps
IMX — 30, 40, and 50
Mbps 525 @29.97fps 625 @25fps
DVCPRO — 25and 50
Mbps 525 @29.97fps 625 @25fps
DVCAM* — 25Mbps 625 @25fps

NEXIO
High Definition Video Compression Specifications

HD Coding and 1080i @29.97fps 1080i @25fps
Decoding MPEG-2 l-frame — 50, 1080p @29.97fps 1080p @25fps
80, and 100 Mbps 4:2:0 720p @59.94fps 720p @50fps
MPEG-2 l-frame — 50, 1080i @29.97fps 1080i @25fps
70, 80, 100, 120, and 1080p @29.97fps 1080p @25fps
150 Mbps 4:2:2 720p @59.94fps 720p @50fps
MPEG-2 Long GOP — 1080i @29.97fps 1080i @25fps
18, 25, 35, 50, 60, 70, 1080p @29.97fps 1080p @25fps
and 80 Mbps 4:2:0 720p @59.94fps 720p @50fps
MPEG-2 Long GOP — 1080i @29.97fps 1080i @25fps
25, 35, 50, 70, and 80 1080p @29.97fps 1080p @25fps
Mbps 4:2:2 720p @59.94fps 720p @50fps
DVCPRO HD — 100 1080i @29.97fps 720p @59.94fps
Mbps 1080i @25fps 720p @50fps
XDCAM HD — 35Mbps
(not available in 720p) 1080i @29.97fps 1080i @25fps
XDCAM HD422 — 50 1080i @29.97fps 720p @59.94fps
Mbps 1080i @25fps 720p @50fps
1080i @29.97fps 720p @59.94fps
XDCAM EX — 35Mbps 1080i @25fps 720p @50fps
1080i @29.97fps 720p @59.94fps
H.264 (decode only) 1080i @25fps 720p @50fps
1080i @29.97fps 720p @59.94fps
DNxHD 1080i @25fps 720p @50fps
AVC-Intra encode on
servers with six-core
processors (2 channel 1080i @29.97fps 720p @59.94fps
mode only) 1080i @25fps 720p @50fps

NEXIO

HD Coding and 1080i @29.97fps
Decoding 1080i @25fps
1080p @ 29.97fps 1080p @25fps
MPEG-2 l-frame — 50, 720p @59.94fps
80, and 100 Mbps 4:2:0 720p @50fps
1080i @29.97fps
1080i @25fps
MPEG-2 l-frame — 50, 1080p @ 29.97fps 1080p @25fps
70, 80, 100, 120, and 720p @59.94fps
150 Mbps 4:2:2 720p @50fps
1080i @29.97fps
1080i @25fps
MPEG-2 Long GOP — 1080p @ 29.97fps 1080p @25fps
18, 25, 35, 50, 60, 70, 720p @59.94fps
and 80 Mbps 4:2:0 720p @50fps
1080i @29.97fps
1080i @25fps
MPEG-2 Long GOP — 1080p @ 29.97fps 1080p @25fps
25, 35, 50, 70, and 80 720p @59.94fps
Mbps 4:2:2 720p @50fps
1080i @29.97fps
720p @59.94fps
DVCPRO HD — 100 1080i @25fps
Mbps 720p @50fps
XDCAM HD — 35Mbps 1080i @29.97fps
(not available in 720p) 1080i @25fps
1080i @29.97fps
720p @59.94fps
XDCAM HD422 — 50 1080i @25fps
Mbps 720p @50fps
1080i @29.97fps
720p @59.94fps
1080i @25fps
XDCAM EX — 35Mbps 720p @50fps
1080i @29.97fps
720p @59.94fps
1080i @25fps
H.264 (decode only) 720p @50fps
1080i @29.97fps
720p @59.94fps
1080i @25fps
DNxHD 720p @50fps

NEXIO
Compression Profile Resolution and Frame

Rate
HD Coding and 1080i @29.97fps
Decoding 720p @59.94fps
MPEG-2 l-frame — 50, 1080i @25fps
80, and 100 Mbps 4:2:0 720p @50fps
1080i @29.97fps
720p @59.94fps
MPEG-2 l-frame — 50, 1080i @25fps
70, 80, and 100 Mbps 4:2:2 720p @50fps
1080i @29.97fps
MPEG-2 Long GOP — 720p @59.94fps
18, 25, 35, 50, 60, 70, 1080i @25fps
and 80 Mbps 4:2:0 720p @50fps
1080i @29.97fps
MPEG-2 Long GOP — 720p @59.94fps
25, 35, 50, 70, and 80 1080i @25fps
Mbps 4:2:2 720p @50fps
1080i @29.97fps
720p @59.94fps
XDCAM HD — 35Mbps 1080i @25fps
(not available in 720p) 720p @50fps
1080i @29.97fps
720p @59.94fps
XDCAM HD422 — 50 1080i @25fps
Mbps 720p @50fps
1080i @29.97fps
720p @59.94fps
1080i @25fps
XDCAM EX — 35Mbps 720p @50fps
1080i @29.97fps
720p @59.94fps
1080i @25fps
H.264 (decode only) 720p @50fps

NEXIO

HD Coding and MPEG-2 l-frame — 50 1080i @29.97fps 720p @59.94fps
Decoding Mbps 4:2:0 1080i @25fps 720p @50fps
MPEG-2 l-frame — 50 1080i @29.97fps 720p @59.94fps
Mbps 4:2:2 1080i @25fps 720p @50fps
MPEG-2 Long GOP —
18, 25, 35, 50, 60, 70, 1080i @29.97fps 720p @59.94fps
and 80 Mbps 4:2:0 1080i @25fps 720p @50fps
MPEG-2 Long GOP —
25, 35, 50, 70, and 80 1080i @29.97fps 720p @59.94fps
Mbps 4:2:2 1080i @25fps 720p @50fps
XDCAM HD — 35Mbps
(not available in 720p) 1080i @29.97fps 1080i @25fps
1080i @ 29.97fps
720p @ 59.94fps
XDCAM HD422 — 50 1080i @ 25fps
Mbps 720p @ 50fps
720p @ 59.94fps
XDCAM EX — 35 Mbps 1080i @ 25fps
1080i @ 29.97fps 720p @ 50fps
720p @ 59.94fps
H.264 (decode only) 1080i @ 25fps
1080i @ 29.97fps 720p @ 50fps
High Definition Video Compression Specification for AVC-Intra

1080i @29.97fps
720p @59.94fps
AVC-Intra: • 1080i @25fps
HD Coding 2ingest+0playonly 720p @50fps
AVC-Intra: • 1080i @29.97fps
0ingest+2playonly • 720p @59.94fps
0ingest+3playonly • 1080i @25fps
HD Decoding 0ingest+4playonly 720p @50fps

NEXIO
RAID Redundancy
RAIDsoft software RAID management "
Controller system
RAID-3 (single drive parity; single drive
failure protection)
-OR-
RAID Protection Schemes ECC (multiple drive parity; dual drive failure
Per Volume protection)
Intrinsic Mirroring Choice of RAID-3 or ECC storage
Protection Scheme (if protection plus fully mirrored storage
configured in your system) area networks*
RAID 6(drive protection) + RAID 0
(striping by NEXIO's RAIDsoft to add
NEXIO Farad RAID-601 bandwidth) + Intrinsic Mirroring
Timecode Connection Options

The following list describes the timecode connections options for NEXIO AMP.
 RS-232
 TCP/IP
 Leitch clock interface
 VITC reader, writer, and generator
Remote GPI Control

Inputs 32 inputs (two 26-pin MDR connectors)
Outputs 16 outputs (two 26-pin MDR connectors)
Remote Serial Interface

 RS-422 ports for control of up to eight channels; one port can be allocated for a VTR
 RJ-12 connector
 Harris ADC VDCP
Controls
 Ethernet, TCP/IP via socket or UDP

 RS-422
Input/Output  GPI
 NEXIO Native Protocol
 VDCP
Protocols  Sony 9-Pin

NEXIO
NEXIO AMP size specifications.

Height 5.25 in. (13.4 cm); 3RU
Width 19 in. (48.3 cm)
26 in. (71.4 cm) from the rack ears to the
Length rear panel
Weight 47 lbs. (21.3 kg)
Power Supply
 Redundant dual hot-swappable, dual load-sharing
 AC 115-120 V; 200-240 V, auto select
 60/50 Hz
 750 W

NEXIO
NX3601HDX Front Panel
NX3601HDX Rear Panel Port Connectors
NX3601HDX Key Features

The following list outlines some of the key features of the NX3601HDX:
 3RU form factor
 Two dual core AMD Opteron™ 64-bit processors (G1) or Quad Core Barcelona 2.3GHz AMD
Opteron 64-bit processors (G2) or Quad Core Shanghai 2.8GHz AMD Operon 64-bit processors
(G3) and Hex Core AMD Opteron 64-bit processors Istanbul (G4)*
 8GB system memory
 Dual mirror (RAID 1) SATA boot drives
 Dual port 4Gbps Fibre Channel support
 Two 10/100/1000Base-T Ethernet adapters (G1) & (G2) & (G3)
 Intel PRO 1000GT adapter with Four Ethernet ports (G2) & (G3)
 USB 2.0 ports – 5 altogether 1 on the front and 4 in the rear of the chassis
 5.25” drive bay
 Server Express Board has E to E output.
 Windows XP Professional x64 Edition
 Removable front bezel
 Software-based codec’s for coding and decoding SD and HD media
 Supports SD and HD content on a single file system
 Supports SDI (SMPTE-259M) and AES-3 interfaces
 Record and playback SD MPEG-2 l-frame and MPEG-2 Long GOP 4:2:0 profile up to 15 Mbps,
and 4:2:2 profile up to 50 Mbps; SD IMX 30, IMX 40, and IMX 50; DVCPRO25 and DVCPRO50;
DVCAM at 25 Mbps (625 only)

NEXIO
 Record and playback HD MPEG-2 MP@HL l-frame 4:2:0 profile up to 100 Mbps, and 4:2:2 profile
up to 150 Mbps; MPEG-2 MP@HL Long GOP 4:2:0 profile and 4:2:2 profile up to 80 Mbps;
XDCAM HD at 35 Mbps; DVCPRO HD at 100 Mbps; AVC-Intra Class 50 and Class 100 (2 play
only channels)
 Integrated up/down/cross conversion support using software based real time processing
 EIA-608 <> EIA-708 closed caption transcoding using software based real time processing
 Easy integration with IP networks using Gigabit Ethernet for media transfers
 Runs NEXIO operating system (NXOS) software for ingest, playout, file transfers, content
management, and additional optional applications
 Includes FTP Server
 Transfer Manager built into NXOS to move media from server-to-server and between attached
general purpose drives and the server using FTP
 Dolby® Digital and Dolby E audio pass-through
 Dual hot swappable power supplies
 Supports up to 25.2TB of storage with RAIDsoft™ storage protection
 Off speed play
 Works with a wide range of 3rd party automation, archiving, and media management applications
Video
The following describes the NX3601HDX video specifications.
 Channels SD = SDI (SMPTE-259M)
o HD = HD-SDI (SMPTE-292M)
 SD Formats 525 @ 29.97fps, 625 @ 25fps
 HD Formats 1080i @ 29.97fps
o 1080i @ 25fps
o 720p @ 59.94fps
o 720p @ 50fps
 SD Input/Output 4 Channel — 2 bi-directional channels, 2 play only channels
 6 Channel — 2 record only channels, 4 play only Channels
 HD Input/Output 2 Channel — 1 bi-directional channel, 1 play only
 Configurations channel HD
o 3 Channel — 1 record only channel, 2 play only channels
o 3 Channel — 0 record, 3 play only channels*
o 4 Channel — 2 ingest + 2 play only (G2) & (G3)
o 4 Channel — 0 ingest + 4 play only (G2) & (G3)
 SD Aspect Ratio 4:3 or 16:9
 HD Aspect Ratio 16:9
 Up/down/cross conversion support
 EIA-608 <> 708 caption conversion
 AFD aspect ratio conversion
 Port based aspect ratio conversion
 User-based aspect ratio conversion
Audio
 The following table describes the NX3601HDX audio specifications.
 Channels & Formats 4 AES/EBU pairs per input channel
 4 AES/EBU pairs per output channel
o 16 channels embedded per input channel
o 16 channels embedded per output channel
 Inputs 4 pairs BNC, unbalanced (AES/EBU)
o 75Ω termination
 Outputs 4 pairs BNC, unbalanced (AES/EBU)

NEXIO
o 75Ω termination
 Audio Processing 16, 20, or 24-bit, PCM, 48kHz
 Compressed Audio Dolby Digital (AC-3) and Dolby E pass through
Server Chassis
 The individual server chassis each include the following elements:
 I/O – Inputs and Outputs
 Physical video, audio, communication and control ports are located on the rear panel for all
server chassis hardware.

NEXIO
Storage
Storage Options 8 or 16 drives per chassis
RAID-3 or ECC SAN Up to 96 drives (146 GB, 300 GB, or 450 GB each)
per SAN using Fibre Channel connectivity
-OR
Up to 192 drives (146 GB, 300 GB, or 450 GB each)
per SAN using Media Host architecture
Intrinsic Mirrored SAN Up to 192 drives (146 GB, 300 GB, or 450 GB each)
per SAN using Fibre Channel connectivity
-ORUp to 384 drives (146 GB, 300 GB, or 450 GB
each) per SAN using Media Host architecture\
Interface Dual-port, redundant 4 Gbps Fibre Channel

-OR
Dualport, redundant Gigabit Ethernet (Media Host
architecture)
Raid Redundancy
Controller RAIDsoft™ software RAID management system
RAID Protection Schemes RAID-3 (single drive parity; single drive failure protection)
Per Volume
-OR
ECC (multiple drive parity; dual drive failure protection)
Intrinsic Mirroring Protection Choice of RAID-3 or ECC storage protection plus fully mirrored
Scheme (if configured in storage area networks
your system)
Time code Connection Options

 The following list describes the time code connections options for the NX3601HDX.
 RS-232
 TCP/IP
 VITC reader, writer, and generator

NEXIO
Remote GPI Control

The following table describes the GPI control specifications for the NX3601HDX.
Inputs 32 inputs (two 26-pin MDR connectors)
Outputs 16 outputs (two 26-pin MDR connectors)
Remote Serial Interface

The following list describes the remote serial interface specifications for the NX3601HDX:
 RS-422 ports for control of up to six channels, one VTR, and one unused
 RJ-12 connector
 Harris ADC VDCP pin out (see NX3601HDX RS-422 Pin outs on page 96)
Controls
The following table describes the NX3601HDX control specifications.
Input/Output  Ethernet, TCP/IP via socket or UDP

 RS-422
 GPI
Protocols  NEXIO Native Protocol

 VDCP
 Sony 9-Pin
Physical Specifications
The following table describes the NX3601HDX size specifications.
Height 5.25 in. (13.4 cm); 3RU
Width 19 in. (48.3 cm)
Length 28 in. (71.4 cm) from the rack ears to the rear panel 29 in. (73.7cm)
from the front of the bezel to the rear panel
Weight 47 lbs. (27.3 kg)

NEXIO
NEXIO AMP™ NX3601HDI
Specifications
The following list describes the general specifications for NEXIO AMP:
 Two Six-Core AMD Opteron 64-bit processors
 16 GB RAM
 Storage options 8 drive raid 3 or 16 drives ECC parity
 2.5 inch SATA drives 500 GB
 Four 10/100/1000Base-T Ethernet adapters
 Dual-head DVI-I monitor interface
 Two USB 2.0 ports on front panel
 One FireWire (IEEE 1394) port (not powered) on front panel
 Windows 7 Professional x64

NEXIO
NEXIO AMP™ NX3601HDI
This section describes the hardware and software specifications for the NX3601HDI.
System Configuration
The following list describes the general specifications for the NX3601HDI:
 Two dual core AMD Opteron™ 64-bit processors (G1) or Quad Core Barcelona 2.3 GHz AMD
Opteron 64-bit processors (G2) or Quad Core Shanghai 2.8GHz AMD Operon 64-bit processors
(G3) and Hex Core AMD Opteron 64-bit processors Istanbul (G4)*
 * need 16 GB of RAM
 8GB system memory
 Dual RAID 1 protected SATA boot drives
 Six 750GB SATA drives for internal media storage – original models.
 Newer HDI servers have 2TB SATA drives
 Two 10/100/1000Base-T Ethernet adapters (G1) & (G2) & (G3) & (G4)
 Intel PRO 1000GT adapter with Four Ethernet ports (G2) & (G3) & (G4)
 One USB 2.0 port on front panel
 Windows XP Professional x64 Edition
Storage
 Storage 6x internal 2TB SATA drives
RAID Redundancy
 Controller Software RAID
 RAID Protection Scheme Single drive parity (RAID-3 single failure Per Volume
protection), 6 drives
Time code Connection Options

 RS-232

NEXIO
Quiz 4 – System Specification

1. What are the maximum amount of FC chassis can a HDX system support? How many FC
drives?
___________________________________________________________________________
2. How many drives can a HDX support if configured in an intrinsic mirroring topology?
___________________________________________________________________________
3. How many drives does a MIOH support without IM?

___________________________________________________________________________
4. How many drives does a MIOH support with IM?

___________________________________________________________________________
5. How many storage drives does a 3601HDI have? What type? What size? How many parity?
___________________________________________________________________________
6. How many storage drives does a 3801HDI have? What type? What size? How many parity?
____________________________________________________________________________

NEXIO

NEXIO
Tech Guide NX3801 - Installation Quick Start
NX3801 - Installation Quick Start

The release button on the outside of each inner rail, and pull the chassis out of the rack.
Harris Supplied Products

 3 RU chassis (1)
 Power cables (2)
 Ethernet cables (2)
 DVI to VGA adapters (2)
 USB to Dual PS2 adapter (1)
Customer Supplied Products

 VGA monitor
 Phillips screwdriver
 Keyboard
 Mouse
Safety Guidelines
Adhere to the following safety guidelines to avoid personal injury or damage to your system.
Electrical Safety Guidelines
Check the Power Cables

 Use the exact type of power cables as required.
 Be sure to use power cable(s) that came with safety certifications.
 The power cable(s) must be compliant with the AC voltage requirements in your region.
 The power cable plug cap must have an electrical current rating that is at least 125% of the
electrical current rating of this product.
 The power cable plug cap that plugs into the AC receptacle on the power supply must be an IEC
320, sheet C13, type female connector.
 Be sure to disconnect the power supply before accessing the chassis or its components.
 Plug the Power cable(s) into a socket that is properly grounded before turning on the power.

NEXIO
Tech Guide NX3801 - Installation Quick Start
General Electrical Safety Guidelines

 Be aware of the locations of the power switches on the chassis and in the room, so you can
disconnect the power supply if an accident occurs.
 Take extra precautionary measures when working with high voltage components. It is not
recommended to work alone.
 Before removing or installing main system components, be sure to disconnect the power first.
Turn off the system before you connect
 The power supply.
 Use only one hand when working with powered-on electrical equipment to avoid possible
electrical shock.
 Use rubber mats specifically designed as electrical insulators when working with computer
systems.
 The power supply or power cable must include a grounding plug and must be plugged into
grounded outlets.
 CD-ROM Laser: CAUTION – Do not open the enclosure of the CD ROM to avoid injury.
General Safety Guidelines

 Do not operate the NX3601HDX with the top panel off. This will cause the chassis to overheat
and will result in damage.
 Keep the area around the chassis clean and free of clutter.
 To avoid injuries to the back, be sure to use your leg muscles, keep your back straight, and bend
your knees, when lifting the system.
 Avoid wearing loose clothing to prevent it from coming into contact with power circuits.
 After removing the components or chassis covers from the system, place them on a table for
safeguard.
 Be sure to remove any jewelry or metal objects before working on the chassis to avoid short
circuits should these objects come into contact with power circuits.
 After accessing the interior of the chassis, be sure to close the chassis with the chassis cover and
secure the chassis to the racks with screws.

NEXIO
Tech Guide NX3801 - Installation and Configuration
NX3801 - Installation and

Configuration
This chapter describes how to install and begin using the NEXIO AMP™ NX3601HDI. This
chapter includes the following sections:
 Rack Mounting
 Connecting the NX3601HDX
Rack Mounting
The NX3601HDX comes with the rack mounting rails. The following are installation
requirements/recommendations:
 Equipment — Mount the chassis on an appropriate rack using the provided rack
mounting and support equipment.
 Power source — connect the power inlet to an adequate power source. Using a UPS is
strongly recommended. Connect each of the two redundant power supply connections to
a separate electrical circuit for added protection.
 Adequate airflow — The NEXIO frames require adequate airflow around the chassis to
provide sufficient cooling. All components draw air in through the front and exhaust via
the rear of the frame. The surfaces must be clear of obstructions to provide proper air
circulation and cooling.
 External device connections — Video monitors and all connections to external devices
should be available and in working order.
 Cable clearance — Provide at least 2 inches of clearance in the rear of the rack for
cabling.
Ensure that the rack is anchored to the floor so that it cannot tip over when the
NX3601HDI is extended out of the rack.

NEXIO
Connecting NEXIO AMP
Port Description
Used to identify a server from
SYS ID SYS ID Button the front.
Power Supply Alarm Reset
Power Supply Alarm Reset Button Silences the power supply alarm.
Two hot swappable, redundant
Power Supplies Power Supply 1, Power Supply 2 power supplies.
IN1, IN2, IN3, IN4 and SDI video inputs 1through 4.
BNC connector for analog bi-
REF IN level or tri-level reference input.
BNC connector for analog
reference passive loop-through.
Loop output = REF IN input. Ifthe
loop-through is not used,
connect a 75ƒÇƒnterminator to
LOOP this jack.
LOOP IN1, LOOP IN2, LOOP IN3, Four BNC connectors for loop-
LOOP IN4 through of inputs 1through 4.
and SDI video outputs 1through
HD/SD and SDI Video OUT1, OUT2, OUT3, OUT4 4.
AES/EBU audio input. Connect to
IN1 these ports when using AES/EBU
1/2, 3/4, 5/6, 7/8 audio and Dolby E for input 1.
AES Audio 1/2, 3/4, 5/6, 7/8 audio and Dolby E for input 2.
IN3 Four HD-BNC connectors for

NEXIO
1/2, 3/4, 5/6, 7/8 AES/EBU audio input. Connect to

these ports when using AES/EBU
audio and Dolby E for input 3.
1/2, 3/4, 5/6, 7/8 audio and Dolby E for input 4.
OUT1 Four HD-BNC connectors for
1/2, 3/4, 5/6, 7/8 AES/EBU audio output 1.
USB1 USB 2.0 port connector for
USB MOUSE mouse.
USB2 USB 2.0 port connector for
KEYBOARD keyboard.
Two unassigned USB 2.0 port
USB3, USB4 connectors.
9-pin D-sub connector for RS232
RS232 RS232 serial port connection.
Computer speaker port
PC Speaker PC SPKR connector. Not used.
Two 4Gb Fibre Channel
Fibre Channel PORT 0, PORT 1 connections to shared storage.
Two DVI-I primary monitor
DVI DVI1, DVI2 connections.
ETHERNET1, ETHERNET2, Four RJ-45, 10/100/1000 Mbps
Ethernet ETHERNET3, ETHERNET4 Ethernet connections.
Two 26-pin MDR connectors for
GPI Ports GPI IN 1-16, 17-32 GPI input.
Two 26-pin MDR connectors for
GPI OUT 1-8, 9-16 GPI output.
COM PORTS Eight RJ-12, RS-422 ports for
COM Ports 1, 2, 3, 4, 5, 6, 7, 8 serial control.

NEXIO
Connecting the NX3601HDX

NX3601HDI Rear Panel Port Connectors
The NX3601HDI has two different rear panel types. The NX3601HDI (G1) provides 2 Ethernet ports and
the NX3601HDI (G2) & (G3) provides 4 Ethernet ports.

NEXIO

NEXIO
The NX3601HDI supports one VTR either in COM Port 7 or COM Port 8.

NEXIO
Tech Guide NEXIO Config
NEXIO Config
This chapter describes how to configure video and audio settings for the NEXIO AMP™ NX3801HDI
using the NEXIO Config application. The NEXIO server software is pre-installed in the operating drive,
software upgrades will discuss on a subsequent section.
This chapter includes the following sections:
 Overview
 Changing Video and Audio Settings
 Commissioning a NX3801HDI
 Commissioning NX3801HDX direct connect
 Commissioning NX3801HDX with FC switch
 Commissioning NX3801HDX with a MIOH server

NEXIO
To start NEXIO Config

Double-click on the NEXIO Config desktop shortcut (see Figure 5-1).
Figure 5-1 NEXIO Config Desktop Shortcut

If you have not registered your software using your Software License Key (SLK), a message appears
telling you to contact Harris BCD Support to obtain a license. See Technical Support on page 9 for
contact information.
The NEXIO Config Node/Domain window appears (see Figure 5-2).
Figure 5-2 NEXIO Config Node/Domain Window

NEXIO
Working with Configuration Presets

NEXIO Config allows you to select an existing template, or create a new template to use for your
configuration. You can easily apply and discard changes, and save your configuration template using the
following icons:
Save — displays the Save Current Template dialog box where you can name and save the
configuration template.
Discard — discards all changes made to the configuration template.
Apply — displays the Apply Changes dialog box so that you can view the changes made to the
configuration template. No changes will be applied until you click OK.
Defaults—You can restore the factory default settings (i.e., 2 SD channels), or you can restore the
preset that you specify as the default
To create or modify a configuration preset
1. In the preset in use list, select the desired template, or select <new> to create a new template.
2. Click the desired window tab or click Next to view the current settings.
3. Make the desired changes to each NEXIO Config window.
You can click Discard at anytime to discard all the changes made to the selected configuration template.
4. Click Apply to view the changes.
The Apply Changes dialog box appears (see Figure 5-3).
Figure 5-3 NEXIO Config — Apply Changes

NEXIO
5. Review all of the changes in the list.

6. Click OK to write the changes to the registry.
7. Restart the LLM to apply the changes.
Creating a Default Preset

The following procedures describe how to restore the system to the factory default settings (i.e., 2 SD
channels) and how to specify a selected configuration as the default preset.
To restore the factory default settings

1. Click the Defaults icon.
The Defaults dialog box appears (see Figure 5-4).
Figure 5-4 NEXIO Config — Factory Defaults

2. Click Factory Defaults.
The following warning appears.
Figure 5-5 NEXIO Config — Factory Defaults Warning

3. Click OK.
The following dialog box appears asking if you want to review the changes.
Figure 5-6 NEXIO Config — Factory Defaults Message

NEXIO
4. Click Yes to open the Apply Changes dialog box and review the changes prior to
restoring the factory defaults.
-OR
Click No to restore the factory defaults without reviewing the changes.
The following dialog box appears recommending that you restart the system.
Figure 5-7 NEXIO Config — Defaults Reboot

5. Click OK to restart the system and apply the factory defaults.
To specify a default preset

1. Create a preset as described in Creating or Modifying a Preset on page 64.
2. In Windows Explorer, open the presets folder.
Tip The presets folder is in C:\Program Files\Harris\NEXIO Config (x64).
3. Copy the file that you want to use as the default from C:\Program
Files\Harris\NEXIO Config (x64)\presets to C:\Program Files\Harris\NEXIO
Config (x64).
4. Rename the file to default.xml.
5. Click the Defaults icon.
The Defaults dialog box appears. Since you have defined a default preset, the
Default Preset button is available (see Figure 5-8).
Figure 4-8 NEXIO Config — Default Preset

6. Click Default Preset.
Figure 5-9 NEXIO Config — Default Preset Message

NEXIO
7. Click Yes to open the Apply Changes dialog box and review the changes prior to restoring the default
preset.
-OR
Click No to restore the default preset without reviewing the changes.
The following dialog box appears recommending that you restart the system.
Figure 5-10 NEXIO Config — Defaults Reboot

8. Click OK to restart the system and apply the default preset settings.

NEXIO
NEXIO Config Windows

Node/Domain
The NEXIO Config Node/Domain window (see Figure 5-4) provides the following information. No changes
can be made in this window.
Identification — displays the host name of the computer
Node information — indicates the NEXIO domain to which this computer belongs and
its node number in that domain
Hardware — indicates the number and type of processors in the computer
Platform — identifies the NEXIO Volt platform and its connection to the media storage
system
Firmware — indicates the version of firmware loaded on the computer’s video hardware
(this information is typically not retrievable if the LLM is currently running)
Software — lists the installed media services and core components
Figure 5-11 NEXIO Config — Information

NEXIO
Channel Configuration
The NEXIO Config Channel Configuration window (Figure 5-12) allows you to select the channel type
and select options.
Figure 5-12 NEXIO Config — Channel Configuration

To select a configuration and include or exclude features
1. In the Channel Type list, select the configuration for your system.
2. In the Record/Bi-directional Channels list, select the number of record or bi-directions channels.
3. In the Play Only Channels list, select the number of play out channels.
4. In the Low Res Proxy Channel list, select the number of low resolution channels if applicable.
5. In the Options area, select the check boxes for the options that you want to include, and clear the
check boxes for the options that you want to exclude.

NEXIO
Video Options
The NEXIO Config Video Options window (Figure 4-13) allows you to specify the Global Configuration
and the Channel Configuration for your system.
Figure 5-13 NEXIO Config — Video Options

To specify video options
1. Click All Channels to set the video configuration for all of the channels, or click the desired channel
(e.g., CH1 Play) to configure a channel individually.
2. In the Global Configuration area, set the options described below:
Video Standard
 Under Video Standard, select the video standard (i.e., NTSC or PAL).
Genlock
 Under Genlock, select the source and resolution setting.
The available Source settings are:
 Internal — this uses the internal clock of the server rather than referencing to an external
reference source.
 Input1 — this references the output video of all channels to the timing derived from video
input 1.

NEXIO
 External—this references the video outputs to the external reference signal applied to the
REF IN connector. This is the recommended setting.
The available Resolution settings are:
 Standard — use for bi-level 525 or 625 line reference.
 HD1080i — use for tri-level 1080i reference.
 HD720 — use for tri-level 720p reference.
 HD1080p — use for tri-level 1080p reference.
VBI and Closed Captioning
a. Under VBI and Closed Captioning, set the start and stop lines for stored closed captioning and other
ancillary data. This data is stored as clip essence.
b. Select the SD MPEG Extended Height check box to compress the ancillary data. This only applies to
SD-only, MPEG 4:2:2 configurations.
Extended Record
a. Select the Extended Record check box to increase the number of vertical pixels recorded to include
those that make up the VBI data closed captioning. This saves space if the recorded VBI lines are set to
the same values. This only applies to SD MPEG 4:2:2 configurations.
3. In the Channel Configuration area, set the options described below:
Resolution
 In the Resolution area, select the desired resolution for the channel configuration (i.e., SD, HD
1080i, HD 720p, and HD 1080p). On a server configured for SD-only, HD 1080i, HD 720p, and
HD 1080p options are not available.
Play Format and ARC
a Click the appropriate Play Aspect option, and then in the Default Channel ARC list select the
ARC play format. For details on selecting the Play Aspect and Default Channel ARC see the
appropriate section below:
SD 16:9 Aspect Ratio Output
For channels configured to play out SD media, it is important to identify the aspect ratio of the video
output. If a channel is intended to display a 16:9 aspect ratio, click the 16:9 option, and then select the
desired ARC setting. The selected ARC setting becomes the default ARC setting for any SD 4:3 clips
(that do not have pre-defined ARC settings) loaded into that channel.
The available settings for a SD channel configured for a 16:9 aspect ratio are:
 Default — Uses the Pillar Box option to display the clip.
 Anamorphic — Stretches the clip in the horizontal dimension to fit the 16:9 frame.
 Pillar Box — Adds black bars on each side of the clip to fit the 16:9 frame.
 Middle Cut — Enlarges the clip on four sides to fit the 16:9 frame.
 14:9 HD — Changes the aspect ratio of the clip to 14:9.
 21:9 HD — Changes the aspect ratio of the clip to 21:9.

NEXIO
SD 4:3 Aspect Ratio Output

If a channel is intended to display a 4:3 aspect ratio, click the 4:3 option, and then select the desired ARC
setting. The selected ARC setting becomes the default ARC setting for any SD 16:9 clips (that do not
have pre-defined ARC settings) loaded into that channel.
Default — Uses the Letter Box option to display the clip.
Anamorphic — Shrinks the clip in the horizontal dimension to fit the 4:3 frame.
Letter Box — Adds black bars to the top and bottom of the clip to fit the 4:3 frame.
Center Cut — Crops the sides of the clip to fit the 4:3 frame.
14:9 SD — Changes the aspect ratio of the clip to 14:9.
21:9 SD — Changes the aspect ratio of the clip to 21:9.
For SD clips loaded into SD channels, the aspect ratio conversion has been disabled. Whether the SD
clips have the 16:9 or the 4:3 aspect ratio flag enabled, they will be played out of all SD configured
channels without an aspect ratio conversion applied.
HD Aspect Ratio Output
For channels configured to play out HD media, the aspect ratio of the video output is always 16:9.
Select the desired ARC setting from the list. The selected ARC setting becomes the default ARC setting
for any SD 4:3 clips (that do not have pre-defined ARC settings) loaded into that channel.
The available settings for an HD channel configured for 16:9 aspect ratio are:
Default — Uses the Pillar Box option to display the clip.
Anamorphic — Stretches the clip in the horizontal dimension to fit the 16:9 frame.
Pillar Box — Adds black bars on each side of the clip to fit the 16:9 frame.
Middle Cut — Enlarges the clip on four sides to fit the 16:9 frame.
14:9 HD — Changes the aspect ratio of the clip to 14:9.
21:9 HD — Changes the aspect ratio of the clip to 21:9.
b Select the desired Timecode Insert check boxes (i.e., VITC and/or LTC). This will insert the clip’s
timecode data into the media play out so that downstream devices are able to interpret the current
timecode of the clip that is playing out.
c. In the Line Select list, select the desired line for the VITC output (i.e., 10, 11, 12, 13, 14, 15, 16, 17,
18, 19, or 20). This option is only applicable for SD-only clips and if VITC insert is selected.
d. Select the Duplicate line 0 check box if desired to add a duplicate line of the VITC output 2 lines later.
For example, if you have VITC output on line 16, a duplicate of the output will appear on line 18. This
option is only applicable for SD-only clips and if VITC insert is selected.
e. Select the Legacy timecode display check box to report a channel’s current output timecode based
on the start time of a currently playing clip instead of the embedded timecode within the clip.
Record Format and ARC

a. In the Format list, select the appropriate record format.
b. In the Bit Rate (Mbps) list, select the appropriate bit rate for the format.

NEXIO
c. Click the appropriate Record Aspect option.

d. Select the Record VBI check box if you want to record the VBI information.
e. Click the appropriate GOP option, and select the M and N value if applicable.
Audio Options
The Audio Options window (Figure 5-14) allows you to select the audiotype, audio bits, audio tracks, and
audio control for your configuration.
Figure 5-14 NEXIO Config — Audio Options

NEXIO
To specify audio options

1. Click All Channels to set the audio configuration for all of the channels, or click the desired channel
(e.g., CH1 Play) to configure a channel individually.
2. In the Audio Input Type area, click the desired input (i.e., Embedded or AES/EBU).
When the Audio Input Type is AES/EBU, the color of each video port in the System Master window is
related to the corresponding audio ports in the Audio Options window (see Figure 5-15).
Figure 5-15 Video and Audio Ports when AES/EBU is Selected

3. In the Audio Bits area, click the number of bits per sample (i.e., 16 Bit, 20 Bit, or 24 Bit).
4. In the Audio Tracks area, select the number of audio tracks (i.e., 4, 8, or 16).
5. In the Audio Control area, select the desired controls (i.e., Volume Enable to control the volume of the
audio, and/or Audio Fades to create an automatic fade between clips within NXOS).
If you have compressed audio (e.g., Dolby), clear the Volume Enable and Auto Fades check boxes and
do not manually adjust the volume.
6. Select the Audio Restriction Bypass check box to allow audio that has restrictions to be accepted by an
appropriate deck, regardless of compatibility.

NEXIO
GPRX Options
The GPRX Options window (Figure 5-16) allows you to select the video and audio bit rates for GPRX
(low resolution proxy).
Figure 5-16 NEXIO Config — GPRX Options

To specify GPRX options
1. In the Video Bitrate(Khps) list, select the desired video bitrate for your configuration.
2. IIn the Audio Bitrate(Khps) list, select the desired audio bitrate for your configuration.

NEXIO
Automation/Serial
The Automation/Serial window (Figure 5-17) allows you to set control ports, general parameters, and
VDCP parameters for your configuration.
Figure 5-17 NEXIO Config — Automation/Serial
To specify each available 422 port

1. In the Channel/VTR list, select the channel that you want to assign to the port or select VTR to assign
the port to a VTR.
2. In the Protocol list, select the desired protocol for the selected channel.

NEXIO
To specify general parameters

1. Select the Auto Clip Protect check box to prevent the deletion of any clip while cued or stacked.
 In the Max Segment Ref Count box enter a value greater than 0 to enable reference ID
protection, which is required for auto clip protection to work. The default value is 2.
2. The Cue With Data Mode parameter allows optional VDCP functionality when cueing a clip with
timecode data. In the Cue With Data Mode list, select one of the following:
 0 — a clip cued to timecode outside of its existing In and Out point cues to the nearest existing
frame.
 1 — the cue command is ignored and an error bit it set.
 2 — the cue command is ignored, an error bit is set, and the cued bit is cleared. In addition, if a
clip is playing and another is stacked, the stacked clip will be unloaded.
3. In the Exact Duration Update list, select one of the following:
 0 — to disable exact duration update.
 1 — to guarantee that playback from any node of the system will not overrun the media written to
disk.
4. In the Jog/Shuttle Speed Limit list, select the desired value. The default is 1.5625.
NOTE: The maximum recommended value for this parameter is 2.0. If you set the value to greater than
2.0 you may run out of bandwidth. If you run out of bandwidth, the clip in that channel may not play out
correctly. In addition, the clips in the other channels may not play out correctly either.
Set to 0, it is disabled. Set to 1, it is enabled.
5. The Blanking Control parameter for the output of the play channel to go to black at the end of a
playing a clip when there is no clip following it stacked to play. In the Blanking Control list, select one of
the following:
 0 — to disable automatic blanking.
 1 — to enable automatic blanking. The blanking is reset at the point that the next clip is cued or
by playing the current clip in reverse.
 2 — to blank the channel even when the clip is first cued in the channel.
6. In the Record Latency parameter defines the time in fields between when the NEXIO receives the
record command and actually initiates the record. This value should only be changed to match an
automation controller whose latency is greater than 6 fields. The minimum value is 6.
7. In the Clock Source list, select one of the following:
 COM1 or COM2—to sync the internal clock and Harris applications to an LTC TCC.
 SYSTEM — to lock the Harris applications to the Windows 7 system clock.
Note The Auto Stop option is for Internal Use Only.
To specify VDCP parameters
1. Select the Disk Preroll Mode check box to enable disk preroll. The amount of the preroll specified by
the VDCP controller is added to any existing timecode offsets established for the channel.
2. Select the Jog Smooth check box to enable jog smooth. If the jump threshold is exceeded then VDCP
Jog command performs a jump without a scrub, otherwise it performs a smooth jog with scrub.
 In the Jump Threshold list, select one of the following:

NEXIO
 0 — to translate to CX.01/CX.02. This is the default.

 1 — to translate to C1.00/C4.00.
3. Select the Port Mode check box to enable a more flexible interpretation of the VDCP protocol.
Specifically it enables VDCP controllers to send record commands to a play port and play commands to a
record port.
4 Select the Stop On Next check box to enable this feature. During stacked (back-to-back ID) playout,
the play channel will stop when it reaches the end of the current ID as long as no play command has
been sent to play the stacked clip.
5. Select the Unload Record Complete check box to enable automatic record-channel unloading of
completed recordings.
6. In the Play Latency list, enter the field value that you want between the receipt of a play-command and
the time the first frame of video plays. The minimum value is 12.
Note: Stack Stop Late is not an available option.

NEXIO
IP Config
The NEXIO Config IP Config window (see Figure 5-18) shows the following network settings:
 Server and Order Configuration
 Network Settings
 LLM Domain and Node Settings
 High-Res Network Server (MIOH)
 Low-Res Network Server (PRXH)
Figure 5-18 NEXIO Config — IP Config

NEXIO
To specify IP configuration settings

1. If you want to change the NEXIO Volt name, in the Server Name box, type a new name, and then click
Set Server Name.
The Set Server Name dialog box appears asking you if you want to change the name (see Figure 5-19).
Figure 5-19 NEXIO Config — Set Server Name

 Click OK to change the name.
Steps 3 through 10 should only be performed if instructed to do so by Harris BCD Support.
2. The order number should appear in the Order Number box. If instructed to do so by Harris BCD
Support, in the Order Number box, type the order number.
3. The Platform Type is read by the registry and should match the Platform information shown in the
Node/Domain window. If instructed to do so by Harris BCD Support, in the Platform Type list, change the
default platform type.
The Network Settings area shows the current IP address, the subnet address, the role, and the
connection name of the selected adapter (see Figure 5-20).
Figure 5-20 NEXIO Config — Network Settings

4. To change the current IP address or subnet mask, double-click in any of the Network Settings boxes
to select that adapter and display the IP Config dialog box (see Figure 4-21).
Figure 4-21 NEXIO Config — IP Config

NEXIO
 Figure 5-21 NEXIO Config — IP Config

 In the IP Address box, type the new IP address.
 In the Subnet Mask box, type the new subnet mask.
 Click Apply to save the changes and return to the IP Config window.
5. In the LLM Domain and Node Settings area, type the Domain Letters and Node Number in the
appropriate boxes.
Note: Do not set the Node Number greater than 127 or the LLM will not launch.
6. If the computer is connected to the NEXIO Storage SAN through a network server (Media Host
architecture), in the High-Res Network Server (MIOH) area, type the Host 1 address and the Host 2
address (if configured for dual paths) in the
appropriate boxes.
7. If the computer is connected to a Low-Res Network Server, in the Low-Res Settings area do one of the
following:
 Type the location of the folder where you want to store the low resolution files in the GPRX
Location box.
 Click Browse to locate the folder where you want to store the low resolution files.

NEXIO
FTP Folders
The NEXIO Config FTP Folders window (Figure 5-22) allows you to select virtual folders and MXF
options.
Figure 5--22 NEXIO Config — FTP Folders

To change virtual folders settings
1. In the Virtual Folders area, select the file types for which you want to create virtual folders.
Tip Virtual folders are used to identify which media files meet the requirements of the selected file type
(e.g., .avi, .mov, etc.) and can be wrapped and exported as that file type.
2. In the MXF Options area, select how you want to export the MXF files to the virtual folders.

NEXIO
LLM Parameters
The NEXIO Config LLM Parameters window (Figure 5-23) allows you to view and change disk
parameters, performance tuning, and NetDisk server parameters.
Do not change these settings unless you are instructed to do so by Harris BCD Support.
Figure 5-23 NEXIO Config — LLM Parameters
To change LLM parameters

1. In the Raid Configuration area, click the appropriate option.
2. In the LLM Disk Parameters and Performance Tuning areas, enter the new value(s) for the registry
setting(s).
3. In the NetDisk Server area, select the appropriate value from the NDWindowSize list.

NEXIO
Error Logging
The NEXIO Config Error Logging window (Figure 5-24) allows you to set logging options for debugging.
The Debug String defines what is written to the errlog.txt.
This can be modified using the Debug Codes area. The number of days a log is kept and the size of the
log options apply to the errlog.txt, tract.txt, traceVDCP.txt, and rwerrlog.txt. These logs are located in the
C:\VR\Logs\LLM folder.
Note: If these logs are not already created and you need help creating them, contact Harris Technical
Support.
Figure 5-24 NEXIO Config — LLM Debug
To change Error Logging settings

1. In the Available list, click the code that you want to include in the Debug String and click > to move it to
the Selected list.
2. In the Selected list, click the code that you do not want to include in the Debug String and click < to
move it back to the Available list.
Tip Click >> to move all of the codes to the Selected list. Click << to move all of the
codes to the Available list.

NEXIO
Note: All codes that appear in the Debug String are included in the errlog.txt file.
3. In the Number of days to keep logs list, select the number of days that you want the logs to be saved.
Tip It is recommended that you select a minimum of 3 days to keep the logs so that they are saved
through the weekend.
4. In the Size of log files list, select the maximum size in kB for the log files.
Tip It is recommended that you select at least 32000 kB for the log files.
5. In the CheckDisk area Interval list, select the desired time (in seconds) that you want between LLM
integrity checks (i.e., 15, 30, 60, 120, 340).
Note: When CheckDisk is added to the Debug String, the CheckDisk area becomes available. The LLM
performs an integrity check on the FAT table held in RAM at the
selected time interval.
6. In the SaveDisk area:

 In the Interval list select the desired time (in seconds) that you want between FAT snapshots
(i.e., 900, 1800, 3600, 7200).
 In the Files list select the desired number of files that you want to save in the snapshot (i.e., 3, 4,
5, 6, 7, 8, 9, 10).

NEXIO
LLM
The NEXIO Config LLM window (Figure 5-25) allows you to view and change various LLM registry
settings. The name, type, data value, and status of each parameter is shown.
Figure 5-25 NEXIO Config — LLM

To change LLM registry settings
1. Double-click in the Data column of the registry setting that you want to change.
2. Type the new value for the registry setting. Changed values appear in bold.
The status of each parameter appears in the Status column. The status icons are described below:
green check mark — indicates that the LLM parameter currently exists in the registry.
green plus sign — indicates that the LLM parameter is absent in the registry and will be created.
red minus sign — indicates that the LLM parameter will be deleted.
purple question mark — indicates that the LLM parameter has no meaning in the current
configuration.
yellow explanation mark — indicates that the LLM parameter has been manually changed and does
not meet the predefined rules.

NEXIO
MPEG
The NEXIO Config MPEG window (Figure 5-26) allows you to view and change various MPEG registry
settings.
Figure 5-26 NEXIO Config — MPEG

To change MPEG registry settings
green check mark — indicates that the MPEG parameter currently exists in the registry.
green plus sign — indicates that the MPEG parameter is absent in the registry and will be created.
red minus sign — indicates that the MPEG parameter will be deleted.
purple question mark — indicates that the MPEG parameter has no meaning in the current
configuration.
yellow explanation mark — indicates that the MPEG parameter has been manually changed and
does not meet the predefined rule.

NEXIO
FTP
The NEXIO Config FTP window (Figure 5-27) allows you to view and change various FTP registry
settings. The name, type, data value, and status of each parameter is shown.
Figure 5-27 NEXIO Config — FTP Parameters

To change FTP parameters
green check mark — indicates that the FTP parameter currently exists in the registry.
green plus sign — indicates that the FTP parameter is absent in the registry and will be created.
red minus sign — indicates that the FTP parameter will be deleted.
purple question mark — indicates that the FTP parameter has no meaning in the current
configuration.
yellow explanation mark — indicates that the FTP parameter has been manually changed and
does not meet the predefined rule.

NEXIO
Startup
The NEXIO Config Startup window (Figure 5-28) enables you to change the install location of the
specified applications and their startup parameters.
Note: Do not change these settings unless you are instructed to do so by Harris BCD Support.
Figure 5-28 NEXIO Config — Startup

To change Startup registry settings
green check mark — indicates that the parameter currently exists in the registry.
green plus sign — indicates that the parameter is absent in the registry and will be created.
red minus sign — indicates that the parameter will be deleted.

purple question mark — indicates that the parameter has no meaning in the current
configuration.
yellow explanation mark — indicates that the parameter has been manually changed and does
not meet the predefined rule.

NEXIO
CV/Logo
The NEXIO Config CV/Logo window (Figure 5-29) allows you to view and change various ChannelView
and Logo registry settings. The name, type, data value, and
status of each parameter is shown.
Figure 5-29 NEXIO Config — CV/Logo
To change CV/Logo registry settings


NEXIO
Other
The NEXIO Config Other window (Figure 5-30) allows you to view and change various additional registry
settings.
Figure 5-30 NEXIO Config — Other
To change Other registry settings

green check mark — indicates that the parameter currently exists in the registry.
green plus sign — indicates that the parameter is absent in the registry and will be created.
red minus sign — indicates that the parameter will be deleted.
purple question mark — indicates that the parameter has no meaning in the current configuration.
yellow explanation mark — indicates that the parameter has been manually changed and does
not meet the predefined rules.

NEXIO
LLM 1
The NEXIO Config LLM1 window (Figure 5-31) becomes available when you select a low res proxy
channel in the Channel Configuration tab (see Figure 5-12). The
LLM1 window allows you to view and change various LLM1 registry settings. The name, type, data value,
and status of each parameter is shown.
Figure 5-31 NEXIO Config — LLM1
To change LLM1 registry settings


NEXIO
Lab 3 - Commissioning via NEXIO Config

Reference the technical training guide to commission the NEXIO HDI server.
• As class exercise commission a NX3801HDI
• Configure ATTO card for direct connect
• Configure the NX3801HDX server direct connect
• Follow the technical training guide to commission a FC switch and an Extreme switch
• Commission a NX3801HDX server to a FC switch to a DAE chassis
• Config the MIOH system

NEXIO
Initializing The Shared Storage RAID Sets:

 Note: On HDX platforms with more than one node on the NEXIO LAN, this process will be
performed once. After a raid set has been created, nodes that adhere to the rules below will be
able to connect to the valid raid set and see other connected nodes upon launch of the LLM:
 Attached to the same storage, either through direct attachment or FC switch,
 Connected to the same Ethernet network on the same subnet,
 Using the same buffer size (see step 4 of 6 in NEXIO Wizard),
 Using the same LLM Domain Letters (see step 3 of 6 in NEXIO Wizard),
 Having a Unique LLM Node Number (see step 3 of 6 in NEXIO Wizard).
Sizing the RAID set NXS31xxC

RAID set size is generally planned at the time of sale, and involves calculating the desired number of
hours of storage, the throughput performance of the RAID set, and the number of hot spares desired. The
end user should also consider future upgrade opportunities, as additional storage must be added in
increments of the existing configured RAID set size. Here is a table showing common RAID set
populations and parameters.
16 total drives
# Raid Sets Data Parity Hot Spares Total Disks Raid Type Direct
drives\set drives\set setting connect\switch
(Wizardstep Throughput
4 of 6) (Mb/s)
2 6 1 1 7 RAID 3 3276\2672
1 14 1 1 15 RAID 3 5895\3426
1 11 4 1 15 ECC 4719\2681
24 total drives
drives\set drives\set
setting connect\switch
(Wizard
Throughput
step 4 of 6)
(Mb/s)
1 18 5 1 23 ECC 6536\4835
32 total drives
(Wizard
Throughput
step 4 of 6)
(Mb/s)
2 11 4 1 15 ECC 4719\2681
2 14 1 1 15 RAID 3 5895\3426

NEXIO
1 26 5 1 31 ECC 7293\5772
48 total drives
drives\set drives\set setting
connect\switch
(Wizard step
4 of 6) Throughput
(Mb/s)
3 11 4 1 15 ECC 4719\3426
3 14 1 1 15 RAID 3 5895\2681
2 8 5 1 23 ECC 6536\4835
1 41 6 1 47 ECC 7560\8348
64 total drives
(Wizard
Throughput
step 4 of 6)
(Mb/s)
4 11 4 1 15 ECC 4719\2681
4 14 1 1 15 RAID 3 5895\3426
2 26 5 1 31 ECC 7293\5772
96 total drives
(Wizard
Throughput
step 4 of 6)
(Mb/s)
3 26 5 1 31 ECC 7293\5772
2 41 6 1 47 ECC 7560\8348
The process below assumes less than 48 disks are targeted for initialization. For systems with a greater
number of drives, you will need to initialize the first 48 or less first to create a Logical D: raid set and the
next 48 or less second to create a logical E: raid set. Intrinsic Mirror setups are not yet covered in this
document.

NEXIO
1. With only one LLM running (all other nodes powered off or at desktop), highlight all disks physical disk
pane, excluding any spares. Note: Make sure you have accounted for any spare disk by reducing the
number in the Total Disks box in step 4 of 6 in NEXIO Wizard.
2. Right click, and select Initialize.
3. In the Min Kb/field drop down combo box, select 200.
4. In the ID Name Size drop down combo box, select 32 UNICODE as the disk size.
5. In the Min Segments box, leave the default of 0.
6. In the Extended Error Info box, leave the default of None.
7. Optionally, in the Volume Label box, type a name for the volume.
8. In the Select Physical Drives list, right click the last drive X number drives and select Parity. The
number of drives selected as parity must match the number of Parity Drives in step 4 of 6 in NEXIO
Wizard.
9. Click OK.
10. The LLM should now show a gray Logical disk D: which indicates the process succeeded.
The XYratex 65xx FARAD storage will discussed in the FARAD training guide or class.
ATTO Celerity Card Setup

For HDX, open Start, Programs, ATTO Configuration Tool, and finally Configuration Tool. Expand host,
localhost, Celerity FC-4x… Select, Channel 1. If using direct connect topology, set the Connect Mode
dropdown to AL (Arbitrary Loop). If using switch topology, set the Connect Mode dropdown to Point-
to-Point. Press the commit button, after making changes to the ATTO card restart system verify LLM
sees disks. If using both ATTO ports verify the setting for Channel 2.

NEXIO
NXS31xxC Drive Chassis:

Reference Drawings:
166-000477 – Single Attached Drive, the servers FC port 0 shall be connected to any port of the
NXS31xx enclosure ID 2 (first enclosure ID) or n (last enclosure ID). The maximum number of the servers
on this case is 8.
166-000478 – Dual Attached Drive, the servers FC port 0 shall be connected to the left side port 3/1 of
the NXS31xx enclosure ID 2 (first enclosure ID) or port 0/2 of ID n (last enclosure ID), and the servers FC
port 1 shall be connected to the right side port 0/2 of the NXS31xx enclosure ID 2 (first enclosure ID) or
port 3/1 of ID n (last enclosure ID), the maximum number of the servers in this case is 4.
166-000479 – FC switch attach. The number of drive enclosures is equal to or less than 3
166-100028 – FC switch attach. The number of drive enclosures is equal to or less than 6
166-100029 – The number of nodes (13 maximum) added to the number of drive enclosures (6
maximum) is greater than 16. Note that all nodes shall be connected to one switch, and all NXS31xx drive
enclosures shall be connected to another switch. Both switches shall be connected via 2 ISLs (XPAK
cables).
Initial setup:
Configure FC cables as shown in the reference drawings delivered with your systems. The drawings
show maximum possible configuration. The delivered system may not contain all the hardware shown on
the reference drawings. Configure the chassis starting with ID 2 and ignore the hardware that does not
exist in the delivered system.
Front and Rear View of the NX31xx Enclosure

The XYratex 65xx FARAD storage will discussed in the FARAD training guide or class

NEXIO
Ops Panel Description showing default switch positions:
Ops Panel

NEXIO
OPS Panel Dip Switch Setup
Harris Ops Panel Switch 4Gpbs setup (note switch #7 is off (RIGHT), and #8 is on (LEFT)):
Harris 4Gbps DIP Switch Setup

NEXIO
Ops Panel LEDs indicators:
OPS Panel LEDs

NEXIO
Configuring the Brocade NXESBTI24 with NXESB-10GLINK module
Attaching a PC or terminal
To assign an IP address, you must have access to the Command Line Interface (CLI). The CLI is a text-
based interface that can be accessed through a direct serial connection to the device and through Telnet
connections. The CLI is described in detail in the FastIron Configuration Guide. Access the CLI by
attaching a serial cable to the Console port. After you assign an IP address, you can access the system
through Telnet, or the Web management interface
Use the following steps to attach a management station to the serial port.
1. Connect a PC or terminal to the serial port of the system using a provided straight-through cable. The
serial port has a male DB-9 connector. See Figure 1.
2. Launch the terminal emulation program and set the following session parameters:
• Baud: 9600 bps
• Data bits: 8
• Parity: None
• Stop bits: 1
• Flow control: None
The EIA or TIA 232 serial communication port serves as a connection point for management by a PC or
SNMP workstation. Brocade devices come with a standard male DB-9 connector, shown in Figure 1.
FIGURE 1 Serial Port (DB-9 DTE) Pin-Out

NEXIO
Most PC serial ports also require a cable with a female DB-9 connector. Terminal connections will vary,
requiring either a DB-9 or DB-25 connector, male or female. Serial cable options between a switch and a
PC or terminal are shown in Table 1.
Wiring map for serial cable
TABLE 1 Serial cable wiring
Switch 9-Pin Serial P ort Null Modem PC 9-Pin DTE Port
2 TXD (transmit data) ----------------------------> 2 RXD (receive data)
3 RXD (receive data) <---------------------------- 3 TXD (transmit data)
5 SGND (signal ground) <--------------------------> 5 SGND (signal ground)
No other pins are used.
NOTE
As indicated above, some of the wires should not be connected.
Changing switch boot-preference to support router code.

Use the following methods to display the software versions running on the device and the versions
installed in flash memory.
Determining the flash image version running on the device
To determine the flash image version running on a device, enter the show version command at any level
of the CLI. Some examples are shown below.
FCX648 Router>?
FCX648 Router>enable
FCX648 Router# Show Version
SW: Version 03.0.00T53 Copyright (c) 2009 Brocade Communications Systems, Inc.
Compiled on Mar 26 2003 at 13:50:31 labeled as FER03000
(3089381 bytes) from Primary fer03000.bin
HW: Stackable FES2402-PREM-ILP
==========================================================================
330 MHz Power PC processor 8245 (version 129/1014) 66 MHz bus
512 KB boot flash memory
16384 KB code flash memory
128 MB DRAM
Monitor Option is on
The system uptime is 4 days 4 hours 8 minutes 33 seconds
The system: started=warm start
Determining the boot image version running on the device
To determine the boot image running on a device, enter the show flash command at any level of the CLI.
The following shows an example output.
FCX648 Switch> show flash

NEXIO
Stack unit 1:
Compressed Pri Code size = 4474947, Version: 07.2.00aT7f1 (FCXS07200a.bin)
Compressed SecCode size = 5592877, Version: 07.2.00aT7f1 (FCXR07200a.bin)
Compressed Boot-Monitor Image size = 369292, Version: 07.1.00T7f5
Code Flash Free Space = 55312384
FCX648 Switch> Show boot-preference
Boot system flash primary

Boot system flash secondary
To load Router code, perform the following steps:
• FCX648 Switch> en
• FCX648 switch# config term
• FCX648 switch(config)#boot system flash secondary
• FCX648 Switch(config)#Exit
• FCX648 Switch# Write mem
• FCX648 Switch# reload
– Are you sure? (enter 'y' or 'n'): y
– Do you want to continue the reload anyway? (enter 'y' or 'n'):y
Note:
The software versions should not be older than:
• Switch code: version:07.2.00aT7f1(FCXS07200a.bin)
• Router code version:07.2.00aT7f1(FCXR07200a.bin
Assigning permanent passwords

By default, the CLI is not protected by passwords. To secure CLI access, it is strongly recommended to
assign passwords. See the FastIron Configuration Guide.
----------------------------------------------------------------------------------------------------------------------
NOTE
You cannot assign a password using the Web management interface
------------------------------------------------------------------------------------------------------------------------
The CLI contains the following access levels:
To set superuser password must be at the configuration section of the CLI.
• User EXEC – The level you enter when you first start a CLI session. At this level, you can view some
system information but you cannot configure system or port parameters.
• Privileged EXEC – This level is also called the Enable level and can be secured by a password. You
can perform tasks such as manage files on the flash module, save the system configuration to flash and
clear caches at this level.
• CONFIG – The configuration level. This level lets you configure the system IP address and configure
switching and routing features. To access the CONFIG mode, you must already be logged into the
Privileged level of the EXEC mode.

NEXIO
You can set the following levels of Enable passwords:
• Super User – Allows complete read-and-write access to the system. This is generally for system
administrators and is the only password level that allows you to configure passwords.
----------------------------------------------------------------------------------------------------------------------
NOTE
You must set a super user password before you can set other types of passwords.
------------------------------------------------------------------------------------------------------------------------
• Port Configuration – Allows read-and-write access for specific ports but not for global (system-wide)
parameters.
• Read Only – Allows access to the Privileged EXEC mode and CONFIG mode but only with read
access.
Setting passwords
1. At the opening CLI prompt, enter the following command to change to the Privileged level of the EXEC
mode:
FCX648SHPOE Switch> enable
2. Access the CONFIG level of the CLI by entering the following command:
FCX648S Router# configure terminal

FCX648 Router (config)#
3. Enter the following command to set the super user password:

FCX648 Router (config) # enable super-user-password <text>
Syntax: enable super-user-password | read-only-password | port-config-password <text>

Passwords can be up to 32 characters long.
---------------------------------------------------------------------------------------------------------------------------
NOTE
You must set the super user password before you can set other types of passwords.
-----------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------
NOTE
If you forget your super user password, refer to “Recovering from a lost password”
below.
--------------------------------------------------------------------------------------------------------------
Recovering from a lost password
In the event if someone has configured a password for the device but the password has
been lost, you can regain super user access to the device using the following
procedure.
-------------------------------------------------------------------------------------------------------------------------------
NOTE
Recovery from a lost password requires direct access to the serial port and a system reset.
-------------------------------------------------------------------------------------------------------------------------------

NEXIO
Use the following procedure to recover from a lost password.

1. Start a CLI session over the serial interface to the switch.
2. Reboot the device.
3. While the system is booting, before the initial system prompt appears, enter b to enter the boot monitor
mode.
4. Enter no password at the prompt. (You cannot abbreviate this command.)
5. Enter boot system flash primary at the prompt. This command causes the device to bypass the
system password check.
After the console prompt reappears, assign a new password.
Enabling Jumbo Frame

Ethernet traffic moves in units called frames. The maximum size of frames is called the Maximum
Transmission Unit (MTU). When a network device receives a frame larger than its MTU, the data is either
fragmented or dropped. Historically, Ethernet has a maximum frame size of 1500 bytes, so most devices
use 1500 as their default MTU.
Jumbo frames are Ethernet frames with more than 1,500 bytes MTU. In Farad, it is required that all 10
Gbps Ethernet adapters, and all clients’ Gig Ethernet adapters to be set jumbo frames of 9,000 bytes
MTU.
FCX648 Router> en
FCX648 Router# config term
FCX648 Router (config) # jumbo
FCX648 Router (config) # writes memory
FCX648 Router (config)# end
FCX648 Router # reload
Disabling the Spanning Tree Protocol (STP)

The Spanning Tree Protocol (STP) eliminates Layer 2 loops in networks, by selectively blocking some
ports and allowing other ports to forward traffic. To prevent delay when connecting hosts to a switch, or
during some topology changes, or uplink failure; which might results in black to air, disabling Spanning-
tree protocol is required. Use the following method to disable STP on the switch.
FCX648 Router> en
FCX648 Router (config) # No spanning-tree
FCX648 Router (config) # exit
FCX648 Router # write mem

NEXIO
Disabling Stack
In NXESB648 and NXESB624 switches the first two ports of slot 2 (4 ports 10 Gbps module) are set as
stacking ports (1/2/1 and 1/2/2) by default. To remove and disable stacking capability, enter the stack
disable command. The stack disable command prevents a unit from sending or listening for any stacking
probe messages.
FCX648 Router> en
FCX648 Router (config) # stack disable
FCX648 Router (config) # exit
FCX648 Router # write mem
Configuring VLAN
Before attaching equipment to a Brocade Layer 3 Switch, you must assign an interface IP address to the
subnet on which the router will be located. You must use the serial connection to assign the first IP
address. For subsequent addresses, you also can use the CLI through Telnet or the Web management
interface.
Switch # 1
Switch # 2
When using the CLI, port and protocol-based VLANs are created by entering one of the following
commands at the global CONFIG level of the CLI.
Below is an example of configuring two switches with appropriate VLANs. In switch # 1 and switch # 2
VLAN 150 and 152 represents UDP SAN LAN, while VLANs V150 and V153, VLAN V151 and 154 are for
NETDISK SERVER, and VLAN V152 and V155 are for other types of traffic such as FTP and PTCD.

NEXIO
FCX648 Router> en
FCX624 Router(config)# vlan 150 name V150
FCX624 Router (config-vlan-150)# untag 1/1/1 to 1/1/12 /* assigning ports that are in the VLAN */
FCX624 Router(config-vlan-150)# router-interface ve 150 /* Create Virtual routing interface */

FCX624 Router(config-vlan-150)# interface ve 150 /*configuring virtual routing interface */
FCX624 Router (config-vif-150)# ip address 172.16.150.1/24 /*Assigning IP address to the virtual routing
interface */
FCX624 Router (config-vlan-151)# untag 1/1/13 to 1/1/38, 1/2/1 to 1/2/2
FCX624 Router (config-vlan-151)# router-interface ve 151
FCX624 Router (config-vlan-151)# interface ve 151
FCX624 Router(config-vif-151)# ip address 172.16.151.1/24
FCX624 Router(config-vlan-152)# router-interface ve 152
FCX624 Router(config-vlan-152)# interface ve 152
For the second switch

FCX648 Router> en
FCX624 Router (config-vlan-153)# untag 1/1/1 to 1/1/12

FCX624 Router (config-vlan-154) # untag 1/1/13 to 1/1/38, 1/2/1 to 1/2/2
FCX624 Router (config-vif-155)# ip address 172.16.155.1/24

NEXIO
Copying a configuration file to or from a TFTP server
To copy the startup-config or running-config file to or from a TFTP server, use one of the following
methods.
NOTE:
You can name the configuration file when you copy it to a TFTP server. However, when you copy a
configuration file from the server to NXESB624 and NXESB648, the file is always copied as “startup-
config” or “running-config”, depending on which type of file you saved to the server.
To initiate transfers of configuration files to or from a TFTP server using the CLI, enter one of the following
commands:
• copy startup-config tftp <tftp-ip-addr> <filename> – Use this command to upload a copy of the startup
configuration file from a switch to a TFTP server.
• FCX648 Router> en
• FCX648 Router# Copy Startup-config tftp 172.16.250.18 FXX648-01_Startup.conf
• copy running-config tftp <tftp-ip-addr> <filename> – Use this command to upload a copy of the running
configuration file from a switch to a TFTP server.
Example:
FCX648 Router> en
FCX648 Router# Copy Running-config tftp 172.16.250.18 FXX648-01_Running.conf
• copy tftp startup-config <tftp-ip-addr> <filename> – Use this command to download a copy of the
startup configuration file from a switch.
Example:
FCX648 Router> en
FCX648 Router# Copy Startup-config tftp 172.16.250.18 FXX648-01_Startup.conf

NEXIO
Extreme Switch Setup

The extreme switch is required if more then one server is being commissioning, the servers need to
update the database information via the NEXIO LAN. The NEXIO LAN should be set for 100 Full Duplex,
1000 FULL or auto negotiate some adapters may have only have the 1000 full or others 1000 full auto
negotiate. Just a remainder that both switch and server network have to be set the same, e.g. 100 full
duplex on server adapter then the switch port has to set 100 full duplex. The transfer LAN can be set 100
Full Duplex or 1000 Full Auto Negotiate if only used for transferring clips, but if also used for LLM failover
then same conditions apply as for the NEXIO LAN.
NOTE: Never set the NEXIO LAN to Auto Negotiate only.
The latest generation of Extreme Networks switches standardizes on the same operating system across
the entire line. The older ExtremeWare has been replaced with XOS in all edge switches. This means that
all products use the same command syntax.
The default factory configuration is a flat layer 2 switch that will allow basic operations. It is recommended
that the end user or commissioning engineer go through basic settings during the commissioning process.
This process will setup the administrative password, port speed and duplex, and default IP interface.
Preparing for switch configuration:

Connect the serial cable that is shipped with the switch to a standard PC com port. Set the port communication
parameters to 9600 baud, 8 data bits, no parity, and 1 stop bit. Connect using a terminal emulator program such as
HyperTerminal.
Note: that the password will either be empty, password, or set to “harris”.
Example Configuration Session:

login: admin
password:
ExtremeXOS
Copyright (C) 2000-2007 Extreme Networks. All rights reserved.
Protected by US Patent Nos: 6,678,248; 6,104,700; 6,766,482; 6,618,388; 6,034,957;
6,859,438;
6,912,592; 6,954,436; 6,977,891; 6,980,550; 6,981,174; 7,003,705; 7,017,082;
7,046,665;
7,126,923; 7,142,509; 7,149,217; 7,152,124; 7,154,861.
==============================================================================
NOTE: If at this point, you are at a command prompt (X450e-48p #) instead of being presented with the
following questions, then you need to issue the command: “unconfigure switch all” then answer “yes” to
any subsequent prompts. This will restore the switch to factory defaults and reboot the switch. Upon
reboot, and login, you will then be presented with the following series of questions. Otherwise continue…
Press the <tab> or '?' key at any time for completions.

Remember to save your configuration changes.
This switch currently has all management methods enabled for convenience reasons.

NEXIO
Please answer these questions about the security settings you would like to use.
Telnet is enabled by default. Telnet is unencrypted and has been the target of
security exploits in the past.
Would you like to disable Telnet? [y/N]: No
SNMP access is enabled by default. SNMP uses no encryption, SNMPv3 can be
Configured to eliminate this problem.
Would you like to disable SNMP? [y/N]: No
All ports are enabled by default. In some secure applications, it maybe more
Desirable for the ports to be turned off.
Would you like unconfigured ports to be turned off by default? [y/N]: No
Changing the default failsafe account username and password is highly recommended. If
you choose to do so, please remember the username and password as this information
cannot be recovered by Extreme Networks.
Would you like to change the failsafe account username and password now? [y/N]: No
Would you like to permit failsafe account access via the management port?[y/N]: No
Since you have chosen less secure management methods, please remember to increase the
security of your network by taking the following actions:
* change your admin password
* change your failsafe account username and password
* change your SNMP public and private strings
* consider using SNMPv3 to secure network management traffic
X450e-48p # configure vlan Mgmt ipaddress 192.168.90.195/24
IP interface for VLAN Mgmt has been created.
NOTE: set management address as required for the end user installation
X450e-48p # configure ports 1-48 auto on speed 1000 duplex full
X450e-48p # configure ipforwarding
X450e-48p # enable web http
X450e-48p # enable web https
X450e-48p # save configuration primary
No default configuration database has been selected to boot up the system. Save configuration
will set the new configuration as the default database.
The configuration file primary.cfg already exists.

Do you want to save configuration to primary.cfg and overwrite it? (y/N) Yes
Saving configuration on master ........ done!
Configuration saved to primary.cfg successfully.
The selected configuration will take effect after the next switch reboot.
X450e-48p # save configuration secondary
The configuration file secondary.cfg already exists.
Do you want to save configuration to secondary.cfg and overwrite it? (y/N) Yes
Saving configuration on master ...... done!
Configuration saved to secondary.cfg successfully.
The current selected default configuration database to boot up the system
(primary.cfg) is different than the one just saved (secondary.cfg).
Do you want to make secondary.cfg the default database? (y/N) No
Default configuration database selection cancelled.
X450e-48p # reboot
Are you sure you want to reboot the switch? (y/N) Yes
The system is going down NOW !!
Sending SIGTERM to all processes.
Sending SIGKILL to all processes.
Please stand by while rebooting the system.

NEXIO
NXES45024:
Use the same procedure as NXES45048. The only exception is the following command, which must
account for the actual number of ports on the switch.
configure ports 1-24 auto on speed 1000 duplex full
NXES25048:
account for the actual speed capabilities of the switch.
Configure ports 1-48 auto off speed 100 duplex full
NXES25024:
account for the actual number of ports and speed capabilities of the switch.
Configure ports 1-24 auto off speed 100 duplex full
Fibre Channel Switch Setup

The new NXFS8400 (Brocade 300) fiber channel switch does not require any configuration it’s just plug
and play.
Note: The switch can only be used in FARAD systems and cannot be in legacy Xyratex systems.
NXFS1644:
Reference Drawings:
166-000479 – The number of nodes is equal to or less than 13, and the number of drive enclosures is
equal to or less than 3
166-100028 – The number of nodes is equal to or less than 10, and the number of the drive enclosures is
equal to or less than 6
166-100029 – The number of nodes (13 maximum) added to the number of drive enclosures (6
maximum) is greater than
16. Note that all nodes shall be connected to one switch, and all NXS31xx drive enclosures shall be
connected to another switch. Both switches shall be connected via 2 ISLs (XPAK cables).
Unpacking:

NEXIO
 Unpack the switches and accessories. The NXFS1644 product is shipped with the components
shown in Figure 1:
 NXFS1644 Fibre Channel Switch (1) with firmware installed
 Power cords (2)
 Rubber feet (4)
 CD-ROM containing the SANsurfer Switch Manager switch management application, release
notes, and documentation.
 XPAK cable if required, not shown (1)
 RS232 null modem cable, not shown
(1)
NXFS1644 Fiber Channel Switch

Installing a NXFS1644 switch involves the following steps:
1. Mount the switch.
2. Install transceivers.
3. Connect the management workstation to the switch.
4. Configure the management workstation.
Install Transceivers (SFPs)

To install a transceiver, insert the transceiver into the port and gently press until it snaps in place. To
remove a transceiver, gently press the transceiver into the port to release the tension, then pull on the
release tab or lever and remove the transceiver If you are using the 10-Gbps ISL ports, remove the port
covers by the cover tabs using your fingers or pliers as shown in Figure below.
Note: The transceiver will fit only one way. If the transceiver does not install under gentle pressure, flip it
over and try again.
CAUTION! To maintain proper airflow and prevent the switch from overheating, keep covers installed in
unused 10-Gbps ISL ports.

NEXIO
Removing 10_Gbps Port Covers

To install XPAK switch stacking cables, position the cable connectors with the circuit board toward the
mid line of the respective switch faceplates as shown in Figure 2. When installing the 3-inch XPAK switch
stacking cable, insert the cable connectors into the 10-Gbps ports at the same time.
Installing XPAK Switch Stacking ISL Cables
Setup management connection to the switch

Setup the switch using a command line interface over RS232. Connect the supplied null modem cable to
either a NEXIO node or an external management computer. Launch HyperTerminal and set the
connection for 9600 baud, 8 data bits, no parity, 1 stop bit, no flow control.

NEXIO
Configure the switch

Press ENTER to bring up the SANbox login prompt. Login as “admin” using the password “password”.
Once
logged in, follow these instructions:
SANbox login: admin
Password: password
Establishing connection... Please wait.
*****************************************************
* *
* Command Line Interface SHell (CLISH) *
* *
*****************************************************
SystemDescription NXFS1644 FC Switch
Eth0NetworkAddress 192.168.90.196 (use 'set setup system' to update)
MACAddress 00:c0:dd:07:0b:7c
WorldWideName 10:00:00:c0:dd:07:0b:7c
SerialNumber 0504A00313
SymbolicName NXFS1644-A
ActiveSWVersion V5.0.0.17.0
ActiveTimestamp Thu Mar 10 16:11:44 2005
DiagnosticsStatus Passed
LicensedPorts 20
The alarm log is empty.
Activate Administrative Mode
To properly configure the NXFS1644 FC switch, administrative privileges are required. The “admin” command
opens and closes an Admin session granting Admin authority. The Admin session provides commands that change
the fabric and switch configurations. Only one Admin session can be open in the fabric at any time. An inactive Admin
session will time out after a period of time that can be changed using the Set Setup command.
Issue the “admin start” command to begin an administrative session:
NXFS1644-A #> admin start
Valid “admin” commands are: start, cancel and end.
Activate Configuration Mode

The “config” command manages the Fibre Channel configurations on a switch. Issue the “config edit” command to
edit the current configuration:
NXFS1644-A (admin) #> config edit
Valid “config” commands are: activate, cancel, copy, delete, edit, list and save.
Set Port Configuration

The “set config” command sets Fibre Channel port configuration parameters. The port configuration parameters are
separated in 3 groups: “NX” (Hosts), “DAE” (Targets) and “Interconnect” (E-Port). Use the following “I/O Stream
Guard & AL Fairness check-off sheet” to configure the ports properly:
For each port, issue the “set config port” followed by the port number, command.

NEXIO
Configuring ports that will be attached to NEXIO nodes (Hosts):

NXFS1644-A (admin) #> show config port 1
Configuration Name: default
-------------------
Port Number: 1
------------
AdminState Online
LinkSpeed Auto
PortType GL
SymbolicName Port1
ALFairness False
DeviceScanEnabled True
ForceOfflineRSCN False
ARB_FF False
InteropCredit 0
ExtCredit 0
FANEnabled True
AutoPerfTuning True
MSEnabled True
NoClose False
IOStreamGuard Enabled
PDISCPingEnabled False
Configuring ports that will be attached to Drive Arrays (Targets):

-------------------
Port Number: 15
------------
AdminState Online
LinkSpeed Auto
PortType GL
SymbolicName Port1
ALFairness False
DeviceScanEnabled False
ARB_FF False
InteropCredit 0
ExtCredit 0
FANEnabled True
AutoPerfTuning True
MSEnabled True
NoClose False
IOStreamGuard Auto
PDISCPingEnabled False

NEXIO
Configuring an Inter Switch Link (Ports 16-19):

No change from the default configuration is necessary.

-------------------
Port Number: 19
------------
AdminState Online
LinkSpeed 10Gb/s
PortType G
SymbolicName 10G-19
DeviceScanEnabled True
AutoPerfTuning True
MSEnabled True
IOStreamGuard Auto
Set Domain ID
The “set config switch” command prompts you in a line-by-line fashion to change switch configuration
settings. Issue the “set config switch” command and enter the value “1” for DefaultDomainID, “false”
for DomainIDLock and “NXFS1644-A” for the SymbolicName.
If more than one NXFS1644 switch are to be used in a system:

 The DefaultDomainID of subsequent switches must be incremented by one for each additional
units. (example: switch 2 = 2, switch 3 = 3, etc…)
 The SymbolicName of subsequent switches must be incremented by one ASCII character for
each additional unit.
Switch number DefaultDomainID SymbolicName
1 1 NXFS1644-A
2 2 NXFS1644-B
3 3 NXFS1644-C
4 4 NXFS1644-D
Example Switch Configuration settings
NXFS1644-A (admin-config) #> set config switch
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the default value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
AdminState (1=Online, 2=Offline, 3=Diagnostics) [Online ]
BroadcastEnabled (True / False) [True ]
InbandEnabled (True / False) [True ]
FdmiEnabled (True / False) [True ]
FdmiEntries (decimal value, 0-1000) [1000 ]
DefaultDomainID (decimal value, 1-239) [3 ] 1
DomainIDLock (True / False) [False ] False
SymbolicName (string, max=32 chars) [NXFS1644-A] NXFS1644-A
R_A_TOV (decimal value, 100-100000 msec) [10000 ]
E_D_TOV (decimal value, 10-20000 msec) [2000 ]
PrincipalPriority (decimal value, 1-255) [254 ]
ConfigDescription (string, max=64 chars) [Default Config]
InteropMode (0=Standard, 1=Interop_1) [Standard ]
Finished configuring attributes.

NEXIO
This configuration must be saved (see config save command) and activated (see config activate command) before it
can take effect. To discard this configuration use the config cancel command.
Save Configuration
The “config” command manages the Fibre Channel configurations on a switch. Issue the “config save” command
to save the changes made to the original configuration.
NXFS1644-A (admin-config) #> config save

Activate the New Configuration
The “config” command manages the Fibre Channel configurations on a switch. Issue the “config activate”
command to activate the changes.
NXFS1644-A (admin-config) #> config activate
Reply “y” (yes) to the following activation request:

The configuration will be activated. Please confirm (y/n): [n] y
Setup IP address
The “set setup system” command prompts you in a line-by-line fashion to change system configuration settings.
Issue the “set setup system” command and enter a value that can be reached by either the NEXIO nodes or a
management computer. In the example below, “192.169.90.198” is used for NetworkIPAddress, and
“255.255.255.0” for the NetworkIPMask. If you intend to reach the switch through a gateway, then make sure to
configure the appropriate address as well. In the example below, “192.168.90.254” is used for the
GatewayIPAddress.
Make sure that NetworkDiscovery is set for “Static” unless the network practices in the facility require a different
setting.
Important note: If more than one NXFS1644 switch is to be used in a system, the NetworkIPAddress of
subsequent switches must be incremented by one for each additional unit.
(Example: switch 2 = 192.168.90.199, switch 3 = 192.168.90.200, etc…)
NXFS1644-A (admin) #> set setup system
A list of attributes with formatting and current values will follow.

Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
Press 'q' or 'Q' and the ENTER key to do so.
Eth0NetworkDiscovery (1=Static, 2=Bootp, 3=Dhcp, 4=Rarp) [Static ]

Eth0NetworkAddress (dot-notated IP Address) [10.0.0.1 ] 192.168.90.198
Eth0NetworkMask (dot-notated IP Address) [255.0.0.0 ] 255.255.255.0
Eth0GatewayAddress (dot-notated IP Address) [10.0.0.254] 192.168.90.254
AdminTimeout (dec value 0-1440 minutes, 0=never) [30 ]
InactivityTimeout (dec value 0-1440 minutes, 0=never) [0 ]
LocalLogEnabled (True / False) [True ]
RemoteLogEnabled (True / False) [False ]
RemoteLogHostAddress (dot-notated IP Address) [10.0.0.254]
NTPClientEnabled (True / False) [False ]
NTPServerAddress (dot-notated IP Address) [10.0.0.254]
EmbeddedGUIEnabled (True / False) [True ]
Answer “y” (yes) went asked if you want to activate this system setup.
Do you want to save and activate this system setup? (y/n) [y]
System setup saved and activated.

NEXIO
Commissioning NX3601HDX with a MIOH server

This section provides Media Host (MIOH) Failover topology and configuration information needed to
commission a NEXIO™ system that uses NX1000MIOH to connect NEXIO clients (I/O nodes) to Gigabit
Ethernet.
Media Host Server NX1011MIOH-10GE or NX1011MIOH-GE
Media Host Server NX1010MIOH
Media Host Server NX1000MIOH

The Media Host Failover topology is designed to support N + 1 Media Host servers streaming data from
Fibre Channel shared storage over Ethernet to clients (I/O nodes) that are attached via Ethernet. This
system design allows NEXIO to scale to very large channel counts, without being vulnerable to single
points of failure in the connective layer. Groups of clients (I/O nodes) are not supported by single Ethernet
to Fibre Channel bridge device. Instead, each client (I/O node) is able to automatically and seamlessly
change to an alternate Media Host machine in the event there are communication problems with their
primary Media Host.

NEXIO

NEXIO
NX1010MIOH Media Host Topology with Intrinsic Mirroring

NEXIO
The two logical Ethernet data connections from each client (I/O node) terminate at separate Media Host
frames. The failure of any one Media Host frame will not affect ongoing client (I/O node) operations. In
this topology, the logical data connections are distributed among the population of Media Host frames via
a distance pairing distribution algorithm. This algorithm assigns client (I/O node) connections to the
Media Host frames such that failure of a Media Host frame will result in an even distribution of additional
load to the remaining Media Host frames.
This topology is redundant to all physical layer failures when installed in compliance with the following
requirements:
 The physical layer connections from each device; Media Host servers and clients (I/O nodes) are
split evenly between two different Ethernet infrastructures, or carried on different blades of an
enterprise class switch.
 The logical connections are configured so that the failure of any one piece of hardware (NIC,
cable, switch or blade) will not result in lost connectivity on both connections simultaneously.
The physical connection pattern to assure redundancy at the physical layer. The physical layer
connections of all clients (I/O nodes) and servers are evenly split among the two network infrastructures.
Physical Layer Example

NEXIO
Ethernet Switch Minimum Requirements

The network environment must meet all of the following criteria:
 802.3x Flow Control must be supported by the switches.
 The TCP retransmissions incurred due to the switch infrastructure must not exceed 2
counts/second on any server or client (I/O node). This is measured during the commissioning
phase.
 802.3ad link aggregation must not be used on any Ethernet ports supporting the Media Host
interconnections. See the NEXIO Streaming SAN, NetworkServer Service, and NetDiskServer
Service sections.
 The packet delay between any two nodes must not exceed 4 ms.
 The total amount of packet delay when a message is passed in sequence from the highest node
to the lowest node must not exceed one video field time. This metric is displayed in the LLM
Codec window as “rt” time in the XOR Read Activity window. For more information on the Codec
window, see the NEXIO Low Level Module User Guide, Part #175-00308-03.
 Both network infrastructures must not experience simultaneous outages longer than 100 ms.
 Both network infrastructures must offer the same speed and duplex specifications.
The available NXES45024 and NXES45048 switches meet these requirements, as does the Extreme
Black Diamond series switches.
There are three network services used by every Media Host server frame described in this section:
 NEXIO Streaming SAN
 NetworkServer Service
 NetDiskServer Service
NEXIO Streaming SAN

This peer to peer network service is supported only on the Media Host frames and on other nodes that
are directly attached to the storage system via Fibre Channel. This network service is responsible for
communicating all changes made by any Media Host or client (I/O node) to all the other server frames in
the domain. The communication method used is layer 2 (UDP) broadcasts with acknowledgments
returned circularly through all Media Host frames.
This network service is bound to two configured IP addresses on different subnets, and assigned to the
two motherboard ports on each Media Host. All Media Host frames require access to this service and
must use the same two subnets, and use the same ordering in the Registry. The following
Example uses the default addresses for Media Host 1:

HKCU\Software\ASC Audio Video\LLM\Control
“IPADDRESS” = 172.16.250.181; Primary UDP
SAN binding, motherboard port 1
“IPADDRESS1” = 172.16.251.181; Redundant UDP
SAN binding, motherboard port 2
NetworkServer Service
The NetworkServer Service is used by the Media Host to extend the NEXIO Streaming SAN
communications path to the attached clients (I/O nodes).
This service is available on TCP port 561 on all IP addresses configured on the Media Host. In practice,
the four ports on the peripheral network card are the targets used for clients (I/O nodes) to attach to the
service. By convention, the clients (I/O nodes) will attach to the service either on peripheral port pair A
and B, or C and D. Each port pair is configured with consecutive subnet pairing.

NEXIO
Clients (I/O nodes) are configured to attach to the NetworkServer service via two registry entries and will
always result in redundant attachment to two Media Host servers, with different physical paths selected
for each.
For example:
“NetworkServer” = 172.16.252.181; Primary
NetworkServer connection to Media Host 1
“NetworkServer1” = 172.16.253.182; Redundant
NetworkServer connection to Media Host 2
NetDiskServer Service
The NetDiskServer Service extends the Fibre Channel SCSI block-based commands for storage and
retrieval from the Media Host to the clients (I/O nodes) over the Ethernet links. This is the service that
transports video and audio data through the system, and therefore large amounts of data travel over
these links.
This service is available on TCP port 562 on all IP addresses configured on the Media Host. In practice,
the four ports on the peripheral network card are the targets used for clients (I/O nodes) to attach to the
service. By convention, the clients (I/O nodes) will attach to the service either on peripheral port pair A
and B, or C and D. Each port pair is configured with consecutive subnet pairing.
Clients (I/O nodes) are configured to attach to the NetDiskServer service via two registry entries. The two
entries will be provided by Harris with your System Drawings, and will always result in redundant
attachment to two Media Host servers, with different physical paths selected for each.
For example:
HKCU\Software\ASC Audio Video\LLM\Parameters
“NetDiskServer” = 172.16.252.181; Primary NetDiskServer connection to Media Host 1
“NetDiskServer1” = 172.16.253.182; Redundant NetDiskServer connection to Media Host 2
FTP Server Service

FTP Server is only supported on dedicated NX1000MGX servers. FTP Server cannot be used on
NX1000MIOH or any client (I/O node) that is attached to Media Host via Ethernet.
Commissioning the System/Configuration

The Commissioning the System/Configuration section contains the following:
 System Software and Firmware Versions
 IP Addresses and Registry Settings
 Switch Settings
 Intel Network Interface Card (NIC) Settings
 NVIDIA Network Interface Card (NIC) Settings
 Proper Flow Control in Extreme 450 Series Switches
 Special Registry Settings
 Startup, Test, and Fine Tune

NEXIO
System Software and Firmware Versions

The following versions of software are the minimum version numbers needed to support the Media Host
architecture.
Application Version Applies to
OS WinXP 64 All
LLM 607.97.70 All
Network.dll 6.07.98.1405 HDX
Network.dll 6.07.98.1404 Media Host

Application Version Applies to
OS WinXP 64 All
DSX.dll 1.0.0.5 3600HDX
FXP.exe 11.31.5.5702 HDX
Intel NIC 8.10.1.0 All
NVIDIA NIC 67.64 3601HDX
Extreme XOS 12.0.2.25 x450 series switches

Switch Settings
The switches must be setup with appropriate VLANs assigned to the proper ports to support the six
networks involved. IP Forwarding should be enabled to allow house networks to access the server system
for command, control, and diagnostics.
Extreme Networks switches are required to have all ports auto-negotiate settings enabled, as this is
required to activate the flow control mechanism in the switch. Customer provided switches must be
examined and set as necessary to activate flow control.

NEXIO
Intel Pro 1000GT Network Interface Card (NIC) Settings
Intel Network Interface Cards (NICs) are used in the Media Host frames; NX3600 frames modified for use
with the Media Host architecture, enhanced NX3601, and NXAMP3801 frames.
Note: The configuration and network settings can be referenced in the MIOH user guide.
Chelsio N320E Dual Port configuration

The NX1011-10GE-2 upgrade procedures describe the proper removal of the Intel® PRO/1000 Quad
Port Server Adapter and the proper installation of the Chelsio N320E Dual Port Server Adapter (10 Gb/s
Ethernet card).
Note: The configuration and network settings can be referenced in the 175-100228-01 NEXIO
NX1011-10GE-2 Upgrade guide.

NEXIO
Special Registry
Settings
The following tables specify the Server and Client (I/O Node) registry settings required for Media Host
Failover to function properly.
Software Versions Tested:

Program Version Date Program Version Date
LLM – 64 bits 607.97.4781 09/15/07 LLM – 64 607.97.4738 08/24/07

bits
LLM – 32 bits 607.97.4781 09/15/07 LLM – 32 607.97.4738 08/24/07

bits
Registry Settings Significant to this Test:

[HKEY_CURRENT_USER\Software\ASC Audio Video\LLM\Control]
NAME SERVER SETTING CLIENT SETTING NOTES
"IPAddress" "172.16.250.56" Server: This value must
match the IP Address
(Server) assigned to the first team of
the Ethernet.
Client: None
"IPAddress1" "172.16.251.56" Server: This value must
match the IP Address
(Server) assigned to the second team
of the Ethernet.
Client: None.
"IPAddress2" "172.16.252.56"
(Server)
"IPAddress3" "172.16.253.56"
(Server)
"IPSubnetMask" "255.255.255.0" The value must match the
Subnet assigned to the
Ethernet port connected to
NEXIO LAN.
"IPSubnetMask1" "255.255.255.0" The value must match the
Subnet assigned to the
Ethernet port connected to
NEXIO LAN.
"IPSubnetMask2" "255.255.255.0"
"IPSubnetMask3" "255.255.255.0"
“NetworkServer” “” "172.16.250.56" Server: blank
Client: This value must
(Server) match the IP Address
assigned to the Ethernet port
1 of the Server.
“NetworkServer1” “” "172.16.251.56" Server: blank
Client: This value must
(Server) match the IP Address
assigned to the Ethernet port
2 of the Server.

NEXIO
[HKEY_CURRENT_USER\Software\ASC Audio Video\LLM\Parameters]

NAME SERVER CLIENT NOTES
SETTING SETTING
“FileBuffs” dword:00000006 dword:00000006
(6) (6)
“MaxIOs” dword:0000000a dword:0000000a
(10) (10)
“MaxIOQuota” dword:00000003 dword:00000003
(3) (3)
“NetDiskServerClients” dword:000000018 dword:00000000 Server:
2*maxIOQuota*clients_per_mgx
(24) (0) For example: maxIOQuota=3, 3
clients per server, then
2*3*3 = 18
“NetDiskServerAgents” dword:000000014 dword:00000010
(20) (16)
“NetDiskServerIOs” dword:00000000a dword:0000000a
(10) (10)
dword:00000200 dword:00000064
“NetDiskServerBuffer”
(512) (100)
dword:000007d0
“NetDiskTimeout”
(2000)
dword:00002710 dword:00002710
“NetDiskRecovery”
(10000) (10000)
Server: None.
“NetDiskServer” sz: Sz:172.16.250.56 Client: IP address of the Server Port
2.
Server: None.
“NetDiskServer1” sz: Sz:172.16.251.56 Client: IP address of the Server Port
2.

NEXIO
Day 2 - Agenda
 Quiz
 Finish the MIOH system lab
 Intrinsic Mirroring Overview
 Q & A Session
 Quiz
 Intrinsic Mirroring Installation
 Configuration (IM direct connect, fiber channel, and via MIOH)
 Q & A Session
 Lab - Hands On
 Quiz

NEXIO

NEXIO
Intrinsic Mirroring
Intrinsic Mirroring allows you to build a redundant Storage Area Network (SAN) that contains two
(mirrored) copies of each piece of content. NEXIO Intrinsic Mirroring adds mirrored writes (X-parity) as an
extra level of protection to ECC or RAID-3 parity (Y-parity). The following shows the top-level design
criteria for this technology.
• Dedicated mirroring software integrated directly into the server engine file system on all nodes.
• A minimum of two storage enclosures.
• The Data & Parity Members are on separate Fibre Channel domains for high redundancy and
availability.
• Data is written to both the Data Member and the Parity Member simultaneously. This mirrored
write operation is the X-Parity.
• The Data Member and the Parity Member are each protected by the traditional RAID-3 or ECC Y-
parity.
• With X-parity and ECC Y-parity, one SAN and at least 3 drives must fail before media is
unrecoverable.
• Dual-ported Fibre Channel adapters on each server are used to create two independent SANs.
• SAN 0 and SAN 1 are fully redundant.
Intrinsic Mirror FC Physical Layer
Server Server
FC Switch FC Switch
FC Switch FC Switch
Copy 1 Copy 2
Media Media
ECC Parity ECC Parity
- X Parity

NEXIO
Writing Mirror Data

Data that enters the server passes through the LLM whether it is baseband video or FTP files.
The LLM writes the data simultaneously to each SAN.
The file system keeps cached copies of the Frame Allocation Table (FAT) on each SAN and on disk
providing drive error detection.
Write Operation: Standard -vs. - Mirrored
Standard Write
LOGICAL VOLUME = RAID SET – 48 DRIVES (42d/6p)
DAE 1 DAE 2 DAE 3
16
17
32
33
48
1
DATA STRIPE –D PARITY
Mirrored Write
LOGICAL VOLUME D1 = 48 DRIVE ECC RAID SET (42d/6p)
DAE 1 DAE 2 DAE 3

16
17
32
33
48
1
DATA STRIPE –D PARITY
DAE 1 DAE 2 DAE 3

16
17
32
33
48
1
LOGICAL VOLUME D2 = 48 DRIVE ECC RAID SET (42d/6p)

NEXIO
Write Flowchart
START WRITE
WRITE
D1
WRITE D1 WRITE
NO
OK? D2
YES
WRITE D2
WRITE NO
OK?
D2
YES
WRITE D2
NO
OK?
YES
UPDATE FAT1 UPDATE FAT1 UPDATE FAT1 UPDATE FAT1

D1 = OK D1 = OK D1 = BAD D1 = BAD
D2 = OK D2 = BAD D2 = OK D2 = BAD
TS = t TS = t TS = t TS = t
UPDATE FAT2 UPDATE FAT2 UPDATE FAT2 UPDATE FAT2

D1 = OK D1 = OK D1 = BAD D1 = BAD
D2 = OK D2 = BAD D2 = OK D2 = BAD
TS = t TS = t TS = t TS = t
WRITE WRITE
FAT1 to FAT2 to END WRITE
DISK1 DISK2
Reading Mirror Data

• Data is read first from alternating SANs based on the server node number through the LLM for
baseband or file output.
• The LLM validates the data integrity during the read process applying ECC Y-parity as needed.
• If the initial read fails for any reason, the data is then read from the other SAN through the LLM
for baseband or file output.
• There is no disturbance to air play out.
• If a SAN is “down” the SAN is not accessed again until the problem is cleared.
• Probe commands are sent periodically to determine when the
• SAN returns to operation.

NEXIO
Mirrored WRITE and READ
Mirrored Write Mirrored Read

VOL = D1 (RAID 3) VOL = D1 (RAID 3)
d10
d11
d12
d13
d14
d15
d10
d11
d12
d13
d14
d15
d1
d2
d3
d4
d5
d6
d7
d8
d9
d1
d2
d3
d4
d5
d6
d7
d8
d9
P
P
STRIPE D DATA PARITY STRIPE D DATA PARITY
d10
d11
d12
d13
d14
d15
d10
d11
d12
d13
d14
d15
d1
d2
d3
d4
d5
d6
d7
d8
d9
d1
d2
d3
d4
d5
d6
d7
d8
d9
P
P
VOL = D2 (RAID 3) VOL = D2 (RAID 3)
Read Flowchart
START READ
(odd index)
CHECK FAT1 CHECK FAT2
“OR” RESULT
D1 OK D1 OK D1 BAD D1 BAD
D2 BAD D2 OK D2 OK D2 BAD
COMPARE
TS1>TS2 TS2>TS1
TS1 with TS2
TS1 = TS2
READ D1 READ D1
NO READ OK READ OK NO READ D2
YES YES
READ OK NO
YES
OUTPUT OUTPUT OUTPUT OUTPUT OUTPUT

BLACK D1 D1 D2 BLACK

NEXIO
Response to Faults
Drive Failures
• Each SAN independently supports the same number of drive failures as a single SAN.
• Each SAN remains operational per its individual configuration.
• For example: an Intrinsic Mirror made up of two 16 drive ECC SANs can support up to 4
drive failures (2 per side of the mirror) and still remain fully mirrored.
Storage Enclosure and Volume Failures

• If an entire storage enclosure fails due to 3 or more drive failures in a volume or in a
storage enclosure, I/O operations continue uninterrupted on the functional SAN.
• SAN Failures If an entire SAN fails, I/O operations continue uninterrupted on the
functional SAN.

NEXIO
Response to Faults - continued

VOL = D1 (RAID 3)
d10
d11
d12
d13
d14
d15
d1
d2
d3
d4
d5
d6
d7
d8
d9
P
STRIPE D DATA PARITY
d10
d11
d12
d13
d14
d15
d1
d2
d3
d4
d5
d6
d7
d8
d9
P
VOL = D2 (RAID 3)
FAULT A single disk fails in a RAID3 set FAULT
(or 3 in an ECC Raid Set) A Fibre Channel cable is unplugged from

one of the servers, drive chassis, or switch
System Response - No disruption to air!
Data is recovered on the fly from Y parity. A Fibre Channel switch is accidentally
unplugged or fails
RAID set Data is recovered on the fly from X parity.
User Action Required A Drive Chassis loses power of fails
Replace drives and rebuild set
System Response - No disruption to air!

Servers will lose access to one of the RAID sets, but will continue to read
and write from the mirrored set with no effect on air.
Sectors written by the affected servers during this event are remembered as
bad in the FAT on the opposite set, so will not be used in subsequent read
operations by any server.
User Action Required

Plug in cable, restore power or replace failed component, etc.

NEXIO
Intrinsic Mirroring LIP Events

If one side of the mirror is subject to LIP (Loop Initialization Primitive) events that cause the
drives to become inaccessible for a short time, the server system runs uninterrupted from
the operational SAN.
Remirroring
When a failed SAN is repaired and brought back on line, it remirrors data in the background.
Remirroring uses spare CPU cycles and bandwidth in all servers together to rebuild the
SAN.
Mirrored Rebuild Process

In the case where both SANs are bad or out of sync sectors on all drives are written
with the recovered data.
The recovered data is always the most recent copy, taken from whichever necessary
SAN.
If the data has a read fault from an individual drive, then the Y-parity data is used to
repair the data before writing the data to the SAN.
When a rebuild is commanded, historic write error data and stripe timestamps are
scanned on both copies, which meet the following rebuilt criteria:
• Disk stripes that contain content AND that have suffered a previous data write error
OR
• Disk stripes that have an out of date timestamp.
At the end of the rebuild, all data and timestamps will be synchronized.
If a drive is replaced, all stripes that contain content are rebuilt. The time to complete this
operation is dependent both on system usage and the amount of content stored.

NEXIO
Intrinsic Synchronization
Synchronization of Copies
• There is no manual process needed to select the correct data copy because the
most recent copy is always the one that is available.
• The FATs are time stamped so that if one SAN is down for a period of time and
contains an old FAT, the software knows not to use the Metadata.
• Each SAN keeps a history of the FATs showing bad and out of date sectors.
• The FATs are also stored on all servers that are connected to the SAN.
• They are updated over the Ethernet network and are written to both SANs on a
regular basis.
Intrinsic Mirroring
The example below consists of two mirrored SANs, each with two storage enclosures. Each
storage enclosure contains a total of 16 drives (14 data drives, 1 parity drive, and 1 hot
spare). In this example, these storage enclosures become logical disks DO, D1*, EO, and
E1*.
Parity Intrinsic Mirroring

Warning: You must use non-suffixed drives for the Data Members, and “B” suffixed
drives for the Parity Members to maintain physical port separation of the Data and
Parity Members. If this warning is not followed, a failure of one FC component might
take down both the Data and Parity Members, compromising access to the content.

NEXIO
Intrinsic Mirroring Commissioning
To set up Intrinsic Mirroring for a RAID-3 Parity

1. On the desktop, double-click on the LLM icon.
2. In the Physical Disks area, select disks 2-01 through 2-15 right-click the selected disks, and
then click Initialize.
3. The Initialize New Disk dialog box appears showing the selected data drives.
4. In the Min Kb/field list, click 200. This is the recommended setting.
5. In the Extended Error Info list, click Data Member.
6. In the Min Segments box, leave the default of 0. This is the recommended setting.
7. In the Volume Label box, type a name for the volume (e.g., MirrorA) followed by \0.
8. The entire name appears as MirrorA\0. The first portion of the volume label can be any
characters, but the \0 is required and indicates that the disk is a data member.
9. Click OK.

NEXIO

1. The LLM window appears showing disk D in the Logical Disks area there are now 15 drives
including 1 parity drive configured as logical disk D with drive 2-16 as the hot spare.
2. In the Physical Disks area, select disks 3-17 through 3-31right-click the selected disks, and
6. In the Volume Label box, type a name for the volume (e.g., MirrorB) followed by \0.
7. The entire name appears as MirrorB\0. The first

portion of the volume label can be any
characters, but the \0 is required and indicates
that the disk is a data member.
8. In the Selected Physical Drives area, right-click
drive 3-31 and click Parity. The drive icon
changes to yellow indicating that it is a parity
drive.
9. Click OK.
The LLM window appears and disk E is added to the

Logical Disks area. There are now 15 drives including 1
parity drive configured as logical disk E with drive 3-32
as the hot spare.

NEXIO

1. In the Physical Disks area, select disks 2-01B through 2-15B right-click the selected disks,
and then click Initialize.
3. In the Extended Error Info list, click Parity Member.
5. In the Volume Label box, type a name for the disk (e.g., MirrorA) followed by \1.
6. The entire name appears as MirrorA\1. The first portion of the volume label must match the
companion Data Member name. The \1 is required and indicates that the disk is a parity
member.
7. In the Selected Physical Drives area, right-click drive 2-15B and click Parity. The drive icon
changes to yellow indicating that it is a parity drive.
8. Click OK.
The LLM window appears and disk D1* is added to the Logical Disks area. There are now 15 drives
including 1 parity drive configured as logical disk D1* with drive 2-16B as the hot spare.

NEXIO
1. The entire name appears as MirrorA\1. The first portion of the volume label must match the
member.
2. In the Physical Disks area, select drives 3-17B through 3-31B right-click the selected drives,
and then click Initialize.
3. The Initialize New Disk dialog box appears showing the selected data drives
4. In the Min Kb/field list, click 200.
7. In the Volume Label box, type a name for the disk (e.g., MirrorB) followed by \1.
8. The entire name appears as MirrorB\1. The first portion of the volume label must match the
member.
9. In the Selected Physical Drives area, right-click drive 2-31B and click Parity. The drive icon
changes to yellow indicating that it is a parity drive.
10. Click OK.
The LLM window appears and disk E1* is added to the Logical Disks area. There are now 15 drives
including 1 parity drive configured as logical disk E1* with drive 3-32B as the hot spare. Logical disk
E1* is the Intrinsic Mirror of logical disk EO.

NEXIO
Intrinsic Mirroring for an ECC SAN

Setting up Intrinsic Mirroring for ECC protection involves defining parameters to create two logical
disks; one data member and one parity member.
The example below consists of two mirrored SANs, each with one volume. Each volume contains a
total of 32 drives (26 data drives, 5 parity drives, and 1 hot spare). In this example, the volumes
become logical disks DO and D1*.
Warning: You must use non-suffixed drives for the Data Members, and “B” suffixed drives for the
Parity Members to maintain physical port separation of the Data and Parity Members. If this warning
is not followed, a failure of one FC component might take down both the Data and Parity Members,
compromising access to the content.
1. In the Physical Disks area, select disks 3-01 through 3-31 right-click the selected disks, and
5. In the Volume Label box, type a name for the volume (e.g., MirrorA) followed by \0.

NEXIO

6. The entire name appears as MirrorA\0. The first portion of the volume label can be any
characters, but the \0 is required and indicates that the disk is a data member.
7. In the Selected Physical Drives area, right-click drive 3-27 and click Parity. Repeat for drives
3-28, 3-29, 3-30, and 3-31. The drive icons change to yellow indicating that they are parity
drives.
8. Click OK.
The LLM window appears showing disk D in the Logical Disks area. In the Physical Disks area,
select disks 2-01B through 3-31B right-click the selected disks, and then click Initialize.

NEXIO
1. The Initialize New Disk dialog box appears showing the selected data drives for MirrorA\1.
5. In the Volume Label box, type a name for the disk (e.g., MirrorA) followed by \1.
6. In the Selected Physical Drives area, right-click drive 3-27B and click
7. Parity. Repeat for drives 3-28B, 3-29B, 3-30B, and 3-31B. The drive icons change to yellow
indicating that they are parity drives.
8. Click OK.
The LLM window appears and logical disk D1* is added to the Logical Disks area. There are now 31
drives including 5 parity drives assigned to logical disk. D1* has drive 3-32B as the hot spare.
Logical disk D1* is the Intrinsic Mirror of logical disk DO.

NEXIO
Monitoring Intrinsic Mirroring
The IM Monitor enables you to monitor your NEXIO Intrinsic Mirroring setup and view errors including
member errors, volume errors, and unrecoverable errors. The IM Monitor also allows you to report
errors to NEXIO Pilot Manager.
To install IM Monitor
1. Double-click on the setup.exe icon located on your NEXIO Software CD.
2. The IM Monitor – Install Shield Wizard appears.
3. Follow the instructions to complete the IM Monitor installation.
4. To access IM Monitor
5. Double-click on the IM Monitor icon
6. IM Monitor window

NEXIO
Monitoring Intrinsic Mirroring
The LLM Address appears showing the node to which you are connected.
To connect to a different node, enter the name of the node in the LLM Address box, and click Connect.
• Inform SNMP notification (SNMP v.1 or v.2) — IM Monitor sends error notification to NEXIO Pilot
Manager, CCS Navigator, or any other supported SNMP Manager using the SNMP. The CCS
CNMP client service needs to be installed on the NEXIO server to send error notifications to the
CCS Navigator server.
If you are using NEXIO Pilot Manager, errors will appear in the NEXIO Pilot Manager Trap Log.
• Date and Time — Indicates the current date and time.
• Label — Indicates the Volume Label that you specified in the LLM.
• Volume — Indicates the volume number of the disk. Volume 1 is the data member; volume 2 is
the parity member.
• Member Recoverable — Indicates the number of stripes on the disk that have a data write error
on a physical drive. This data is recoverable.
• Volume Recoverable — Indicates the number of stripes on the disk that have data that are not
mirrored (on the data member and the parity member). This data is recoverable.
• Unrecoverable — Indicates the number of stripes on the disk that have data write errors that are
not recoverable. The only way to fix these errors is to delete the clips that contain the errors.
These errors are extremely rare and probably indicate a server failure during recording.

NEXIO
Lab 5 - Intrinsic Mirroring

• Create an intrinsic mirror parity raid set direct connect
• Create an intrinsic mirror parity raid set using MIOH
• Remove one FC drive on each chassis to verify data stability on the on playback
• Turn off one raid set
• Check playback on the other raid set

NEXIO
Day 3 - Agenda
 Quiz
 Finish Intrinsic Mirroring system lab
 Q & A Session
 LLM Overview
 LLM Lab
 Workflow
o Servers installed with automation
o Servers installed Iin none automation installs
 NXOS
 Labs - Hands On
 Quiz

NEXIO

NEXIO
Tech Guide LLM
LLM
LLM Overview
The LLM handles the low level communications between the storage devices and the video/audio codecs.
The LLM also handles communication with other NEXIO server nodes, automation systems, and tape
machines. It handles the storage and retrieval of audio, video, and ancillary data to and from the storage
system.
• The LLM includes RAIDsoft™ technology to create and manage ECC and non-ECC RAID sets.
• The LLM must remain running for the NEXIO Server to function.
• Updates to the LLM are installed with NEXIO software releases.
Do not uninstall the LLM.

You can use the LLM to do the following:
- Check codec status
- Verify that the server is connected to your storage
- Verify that the server is connected to your network of NEXIO servers
- View disk performance
To start the LLM

On the desktop, double-click on the LLM icon.
The LLM window appears.
Nodes Pane The Nodes pane displays all of the NEXIO video servers connected to the Fibre Channel
network.

NEXIO
Tech Guide LLM
Logical Disks Pane

The Logical Disks pane displays all of the logical disk sets. A logical disk is one or more physical disks
which have been initialized with the RAIDsoft™ formatting information to create a high speed storage
system or RAID set. Your system may have from one to four logical disks depending on its configuration.
The Logical Disks pane displays one icon for each logical disk set. See Table 1-4 for more information
about the logical disk icons.
Physical Disks Pane

The Physical Disks pane displays any physical disks in the connected enclosure(s) that are not part of a
RAID set. If the physical Disk pane is empty it indicates that all available disks are being used to create a
logical disk. The Physical Disks pane also displays hot spare drives. Hot spare drives are extra drives that
are stored in the drive enclosure instead of on the shelf.
Logging as admin
To access the LLM Administrator features, you must first log on as an Administrator. Contact Harris
Customer Support if you do not know the Administrator password.
To log on as an administrator
1. In the Logical Disks pane, right-click on a logical disk icon and select Properties. The Properties
window appears.
2. Click the Security tab. Once done with admin functions click LogOff.

NEXIO
Tech Guide LLM
Creating an ECC logical disk

You can create a new RAID set if you have added or replaced your hard disk drive storage. When adding
storage to an existing storage system, each RAID set needs to have the same number of disks and parity
configuration. You can mix drive capacities; however, you must have the same number of data and parity
disks in each RAID set. A RAID-3 RAID configuration can have either 8 or 16 drives including 1 parity
drive. An ECC RAID configuration can have 16, 24, 32, or 48 drives including 4 or more parity drives.
Initialize Logical Disk

Redundancy
• Parity: requires a single drive be allocated, and provides protection from a single drive failure
• ECC: requires that multiple drives be allocated (according to the following table), and provides
protection from two concurrent drive failures
TOTAL DRIVES IN Logical Disk PARITY DRIVES REQUIRED

1-8 NO ECC PARITY
9 - 15 4*
16 - 31 5
32 - 48 6
Note: The NX3801HDI supports ECC parity raid sets e.g. 11 data drives and 4 parity drives with one hot
spare.
Minimum Stripe Set

• this is the total quantity of drives contained in the logical disk
To determine your RAID set size, refer to your System Diagram.
Server Model Buffer Size

NX3600 4096
NX3601 7664
NX3601 G2 , G3 & G4 7664
NX3801 7664
The example below uses the RAID set size shown above to show how to create an ECC RAID set with 16
drives (15 drives including 4 parity, and 1 hot spare).
HKEY_CURRENT_USER\Software\ASC Audio Video\llm\Parameters
"BuffSize"=dword:00001000 (hex) or 4096 (decimal)

NEXIO
Tech Guide LLM
To create a new ECC RAID set

1. On the desktop, double-click on the LLM icon. The LLM window appears showing the available
physical drives.
2. In the Physical Disks area, select disks 2-01 through 2-15 (figure below) right-click the selected
disks, and then click Initialize.

NEXIO
Tech Guide LLM
The Initialize New Disk dialog box appears

2. In the ID Name Size list, select 32 UNICODE as the disk size.
4. In the Volume Label box, type a name for the volume.
5. In the Selected Physical Drives area, right-click drive 2-12 and click Parity. Repeat for drives 2-
13, 2-14, and 2-15. The drive icons change to yellow indicating that they are parity drives 6 Click
OK.
The LLM window appears showing disk D in the Logical Disks area.
There are now 15 drives including 4 parity drives configured as logical disk D with drive 2-16 as the hot
spare.

NEXIO
Tech Guide LLM
Resize segments
When the RAID set initializes a default number of blank object entries (segments) are created. As you
create and store clips, these entries are used one per clip. If you delete clips from the RAID set the
entries are released and are able to be used again. If your system runs out of segments, you need to
delete media from your disks or increase the minimum number of segments.
To adjust the minimum segments

Adjusting minimum segments is only supported when ID Name Size is set to 32 UNICODE.
1 Click the LLM icon on the Desktop. All other machines on the system must be shut down to the
Desktop.
2 Right-click on the logical disk icon and click Resize
3 Increment the number in the Min Segments box by 1. This increases the number of available segments
by several thousand. Do not increase the number in the Min Segments box by any other number

NEXIO
Tech Guide LLM
Resize segments
The rare occasions the mediabase runs out of available database entries by doing a segment resize it
increases the amount of entries by thousands.
ID Name Size
• The customer was initially interfacing with an automation system that could only handle 8-
character ID names, but would now like to upgrade to handle the more flexible 32-character ID
names
Minimum Segments
• This is essentially the number of record entries allowed in the FAT table. The amount is typically
assigned automatically to a default value at the time of Initialization. If the customer however
records a lot of short duration IDs, they may run out of database entries before they run out of
recording space
Extended Fields Size

• This allocates space for metadata. Again, it is typically assigned automatically to a default value
at the time of Initialization. If this however was over-ridden initially, it can be altered
• In any case, resize is only available in one direction – an increase in any of the above
parameters. It will not allow existing Mediabase information to be truncated. In the case of ID
Name Size, and Extended Fields, only the available options will be presented. Manual
adjustments to Min Segments should only be made with engineering approval.

NEXIO
Tech Guide LLM
Network properties
To view the network properties In the Nodes pane, right-click on a node (device) icon.
The Network Properties window appears.
You can view the network properties of any of the connected NEXIO devices. You can view the following
network properties:
TCP/IP Address — The NEXIO network address of the device. Each device should have a unique
network address on your system. NEXIO systems typically ship with network addresses in the
92.168.90.xxx subnet as this is a protected class. IP addresses in the protected class are available for
use on systems that are not connected to the Internet.
Link Inits — The number of times the LLM has established a new connection to other LLM nodes.
Each time the LLM is stopped and restarted, the Link Inits value is reset to 1.
Retries — The number of times connected nodes have failed to reply to a TCP/IP packet sent by the
local node. The LLM makes up to four attempts to successfully send a packet and receive a reply. After
four attempts, the retry status is reset and the LLM performs a new link initiation.
Codec control window
Opening the Codec Window

From the Nodes pane, you can open the codec window of a connected NEXIO video
server. The codec window lets you view video server status and diagnostic information.
To open the codec window

In the Nodes pane, double-click on a local node. The codec window will appear.

NEXIO
Tech Guide LLM
The Codec Control dialog box has the following sections:

Codec Controls — Provides record, play, pause, and stop functions on the codecs.
These functions are for hardware diagnostics only and should not be used on air.
Buffer Usage — Shows the system buffer usage.
Use the Special area only if instructed to do so by Harris Customer Support.
Special — The Special area allows you to view the Rate Log, and save the field.
Drive Activity — Shows event messages for the RAID set. You can view the following event messages:
• Read Activity — Shows data transfer activity for read operations.
• Write Activity — Shows data transfer activity for write operations.
• XOR Read Activity — Includes parity calculation processes.
• XOR Write Activity — Includes parity calculation processes.
• Errors — Shows error messages returned by the LLM since the last restart of the LLM.
• Connections — Shows the number of active connections.

NEXIO
Tech Guide LLM
Physical disks
Working with physical disks
 The Physical Disks pane displays all of the available hard drive disks which are not part
of the logical disk.
 The physical drive is called the hot spare.
 The physical disk are used to create a logical if no drives are available this indicates that
all of the drives were used to create a logical disk.
Identifying a physical disk
 Right click on the drive and select identification. The drive LED will turn amber.
Working with logical disks
Viewing RAID Set Properties

 In the Logical Disks pane, right-click on a RAID set icon and click Properties. The
Properties window appears.
 Click the General tab to view the logical disk parameters and to view
 label, Data rate, Used time, Free time, Used segments, and Free segment
Click the Information tab to identify a disk.

 Right click on the drive and select identification.

NEXIO
Tech Guide LLM
Error History
To view error history

• In the Logical Disks pane, right-click on a RAID set icon and select Error History. The Error Chart
window appears.
Properties Dialog Box
Information Tab
• Displays the number of data and parity drives.
o When right clicking on the drives
 Identification - Drive turns amber
 Errors - Sense codes
o When logging as admin you get two other options
 Prepare drive for removal
 Replace with new drive
Properties Dialog Box
Security tab
o The default admin password is “LEITCH”
o This password can be changed by going into the registry
\HKEY_CURRENT_USER\software\ASC Audio Video\llm\Password\Password.

NEXIO
Tech Guide LLM
Drive Replacement
Determining type of Drive Failure

• Hard disk fails electrically or mechanically. It needs to be reseated, or replaced and rebuilt to
maintain data integrity.
• There are two different replace and rebuild procedures depending whether you receive a failure
indicator or the drive was rejected.
o Drive is ejected then the logical disk is degraded
 appears yellow with a red explanation point
o You are given an LED amber status.
o User interface indication (Nexio Monitor)
Logical disk is graded – mechanical failure

 Verify that all servers show same status. If not all the servers have the same status then apps
need to be rebooted or do prepare drive for removal on a good logical disk.
 The bad drive will appear in the physical disk pane. Right click on the drive select identification,
the drive will turn amber, repeat procedure a couple of times. Put a piece of tape on drive.
 Pull the old drive.
 Put in the new drive.
 In the Security tab of the Properties dialog box, type the admin password and click on logon.
 In the Information tab of the Properties dialog box, right-click the drive with the circle/slash, and
then click Replace with new drive.

NEXIO
Tech Guide LLM
Drive Replacement - continued
Logical is graded – mechanical failure

• The Select New Drive dialog box appears showing all of the drives in the Physical Disks pane.
• Highlight the drive with the correct ID.
• Click OK to complete the drive replacement.
• In the LLM window, right-click the logical disk, and then click Start Rebuild.
• The Logical Disk icon will return to normal state until the rebuild is done.
LLM Drive Failures
Correcting Drive Failures

• If one or more drive fails, the system design enables the failed drive to be replaced and the data
restored without impacting normal record/play operations. (Parity or ECC).
Reseat Procedure
When a drive has a communication problem, the drive’s activity light does not flash in tandem with the
other drives in the array.
Sense codes of the type 0 [00] [00] occur when communication is lost between the fibre channel and the
drive. This is typically caused by one of the following occurrences:
• microprocessor on the drive has crashed
• drive array enclosure has bypassed the drive on the fibre channel
For any drive in this state, the activity light will not flash in tandem with the other drives in the array.

NEXIO
Tech Guide LLM
LLM reseat a drive

In the Information tab of the Properties dialog box, right-click the drive that is reporting the errors, and
then click Identification.
In the example on the right the Physical Disk ID is 2-03, indicating that the Frame number is 2 and the
Slot number is 3. Notice that the Slot number shown in the text is 2. This is because the numbers in the
title bar are 1-based and the numbers in the text are 0-based. Note the Serial Number shown in the
Physical Disk Identification window.
• Pull the identified drive from the chassis about 2 inches.

• Observe the front of the array. The indicator light for the suspect drive should be illuminated the
entire time that the Physical Disk Identification window is open.
• Wait about 30 seconds.
• Reseat (replace) the drive into the chassis.
• Confirm that the drive has resumed normal operations. The LED of the drive flashes for 10-15
seconds and then becomes solid green.
• If any operations were in process when the drive was reseated, the reseated drive’s
activity light should be flashing in tandem with the other drives.
• Verify that this has resolved the communication problem.
• Play an ID that has been recorded before the problem occurred.
• Make sure all drives in the Physical Drive List appear normal.
• In the Information tab of the Properties dialog box, right-click the reseated drive, and then click
Errors.

NEXIO
Tech Guide LLM
• Note the Read and Write numbers in parenthesis in the Errors window.
• Close the Errors window and wait 30 seconds.
• Re-open the Errors window and compare the numbers.
• If the numbers in the Error window have not increased the communication problem has been
resolved. If the errors are still increasing then the drive needs to be replaced.

NEXIO
Tech Guide LLM
Broken Logical Disk
On rare occasions when an LLM is restarted, a broken disk icon may appear, instead of the usual grey
disk icon:
The appearance of this broken disk icon indicates that there is a corruption in the FAT table that instructs
the LLM where it can find all the Mediabase IDs on the array. Although the odds of success in addressing
this condition are very high, this still likely represents the most serious condition that can be encountered
in a server system, in that failure to resolve it fully can mean partial or complete loss of the customer’s
media.
WARNING: check the disks in “Information Tab” and verify that they appear good before processing with
procedure.
To fully understand a broken disk scenario, an overview of how Mediabase information is handled in the
server system is in order.
When a server system is completely shut down, the FAT table index to Mediabase IDs exists in only one
place – on the drive array. When a single LLM is launched, it retrieves a copy of this “master” table from
the array, and places it into LLM memory. When the LLM on another server is launched, it too retrieves a
copy of this table from the array, and places it in this server’s LLM memory. At this point, copies of the
FAT table now exist in three places – on the drive array, and in LLM memory on two servers.
When a change is made to Mediabase – for example when a recording is made – the LLM doing the
recording (call it “LLM 1”) writes this update back to the master FAT table on the drive array, and
distributes this update information to all the other LLMs in the system via Ethernet (call the LLMs 2&3).
These LLMs (2&3) then in turn update the copies of the FAT table that they hold in their LLM memory.
These LLMs (2&3) would have read the current copy of the FAT table at the time they were started, and
will have applied all the updates that occurred since that time based on updates from other LLMs via
Ethernet (LLM 1 in this example).
On rare occasions, a server doing a recording (LLM 1 above) may corrupt the master FAT table when it
updates it. In this state, any LLM restart (say LLM 2 for this example) would retrieve this corrupted FAT
table; place it into the newly restarted LLM’s memory, and display the broken disk icon to indicate the
problem.
Initial Broken Disk Actions

When a broken disk occurs, there are two key points to keep in mind:
DO NOT shut down more than a couple of LLMs during the early troubleshooting of this issue. Each LLM
has a copy of the FAT table in its memory, and that copy may be the key to successfully resolving the
situation
No action should be taken without first verifying that all aspects of the fibre channel are physically sound –
primarily, that all array drives can be seen by servers on both fibre channel loops.
There are a couple of possible resolution procedures for Broken Disk scenarios:

NEXIO
Tech Guide LLM
Repair Without Fix

The preferable approach to rectifying a broken disk is to take advantage of the existence of multiple
copies of the FAT table, as described above. Although LLM 1 may have corrupted the master FAT table
when it wrote its update to it, there are other copies of the FAT table in existence in the memory of other
LLMs in the system that may not be corrupted.
The way to determine whether or not these copies are corrupt is to trigger an update of the master FAT
table from one of them:
Choose another server in the system whose LLM has been running since before the broken disk was
discovered (say, LLM 3), and from that unit:
Do a short recording, or
Double-click on an existing ID in Mediabase, edit its Description, and save the change
Either of these actions will cause the LLM from this server to update the master FAT table on the array
using the copy in its own LLM’s memory. Since this FAT table copy is updated independently from the
one that presumably corrupted the master FAT table in the first place, this action will hopefully restore a
good FAT table copy back to the master FAT table on the array
Now restart the LLM that displayed the broken disk (LLM 2).
If indeed the FAT table copy from LLM 3 was good when it over-wrote the master FAT table on the array,
then when LLM 2 is restarted this time, it will retrieve the newly corrected FAT table from the array, and
will launch successfully with a good grey logical disk

NEXIO
Tech Guide LLM
Repair With Fix

If the above procedure for repairing without Fix still results in a broken disk, then a Fix procedure may be
required. If you are not familiar with and completely comfortable with all aspects of Broken Disks and the
Fix routine, however, it is highly recommended that you involve others with more experience in these
situations. Keep in mind that although there is a very high success rate in resolving broken disks, if the
situation is not handled appropriately, the possibility of full or partial loss of the customer’s media may be
greatly increased.
Before proceeding with a Fix routine, messaging generated by the LLM startup that resulted in a Broken
Disk should be checked. In situations with a high probability of Fix succeeding, messages of the following
types are typically observed:
Video Chain FREE_SEG (1) broken: 1

Video Chain %00004EF (1263) broken: 2
SegmentList(ROOT_SEG) broken: 2
Messages of the following types may not have the same likelihood of success:
ReadStripe() error -1, disk: 0

raid.error[17] : -1
Directory read error -1, disk: 0, stripes: 3, offset:0/3b8000
directoryReadError[0]: -1
ProgVerifyXor() error: 6872352291731500895
In either case, provided that all the physical drives can be seen by the LLM, proceed with the Fix routine,
which will clean up the most common problems, such as orphaned or cross- linked clusters:
• On the server that displayed the “high probability” messaging, leave its LLM running
• Shut all other server applications down, leaving them at the Windows Desktop
• On the remaining LLM, confirm that the only node in the top nodes pane is the local orange node
• Right-click on the logical disk, and choose Properties
• In the Security tab, type in the password “LEITCH”, and choose Login
• Right-click on the logical disk again, and this time choose Fix
• Popup window will prompt: “Fix Disk D:?”
• Choose OK
Shortly afterwards, a grey logical disk icon should appear in the LLM. At this point, all LLMs can be
restarted, and normal operation resumed.
Note: that although the parity scheme (“Redundancy”) for media is chosen at the time the logical disk is
initialized, the selection of “Parity” (RAID 3) or “ECC” does not apply to how the FAT Table parity is
handled. In all logical disks, even though the media parity scheme may be either Parity (RAID 3) or ECC,
the FAT Table parity scheme is always ECC.

NEXIO
Tech Guide LLM
Drive Sense Codes

Right-click the logical disk and choose Properties in the Information tab, right-click the suspect drive and
choose Errors:
The number in parentheses indicates the total quantity of errors that have occurred for the drive in
question, as relates to the local server operation, since its LLM was started.
The remaining information characterizes the nature of the last error recorded:
Sense x[yy][zz]
x Sense Key
yy Additional Sense Code (ASC)
zz Additional Sense Code Qualifier (ASCQ)
• A Sense Code of 0 [00] [00] indicates that the drive is experiencing communication issues
• Any Sense Code other than 0 [00] [00] indicates that the drive is experiencing physical issues
Addressing Communication Issues – Sense Code is 0 [00] [00]
• Sense codes of the type 0 [00] [00] occur when communication is lost between the fibre channel
and the drive. This is typically caused by one of the following occurrences:
o microprocessor on the drive has crashed
o drive array enclosure has bypassed the drive on the fibre channel
• For any drive in this state, the activity light will not flash in tandem with the other drives in the
array

NEXIO
Tech Guide LLM
Sense Code 0 [00] [00] Resolution:

• Pull the identified drive out about 2 inches to unseat it from the chassis
• wait about 30 seconds and reseat the drive
• wait another 30 seconds, then confirm the drive has resumed normal operations:
o if any record or play operations are occurring in progress on the system, the
newly re-inserted drive should now be flashing in tandem with the other array
drives
Verify if this has cured the issue as follows:

• Play an ID that is believed to have been recorded before the current problem started
• from the LLM Properties, Information tab, right-click the drive again and choose Errors
• note the numbers in parentheses – ( ) – after Read and Write
• close the Errors window for 30 seconds
• again right-click the drive and choose Errors
• compare the numbers now in the parentheses
o If the numbers have not increased, the communication issue has been resolved.
Proceed to Rebuild
o if the numbers are still increasing, proceed with the Drive Replacement
Addressing Physical Issues; Sense Codes are non-zero

• Sense codes other than the type 0 [00] [00] occur when the drive itself cannot process data to
and/or from the disk platter correctly. Drives experiencing these non-zero sense code errors
should not be replaced unless they meet the error rates specified by Engineering.
Verify if the drive errors meet the rate criteria as follows:

• Play an ID that is believed to have been recorded before the current problem started
• from the LLM Properties, Information tab, right-click the drive and choose Errors
• note the numbers in parentheses – ( ) – after Read and Write
• close the Errors window for 5 minutes
• again right-click the drive and choose Errors
• compare the numbers now in the parentheses
o If the number of errors has not increased by more than 100 in this 5 minute period, do not
continue with this procedure. Monitor the drive occasionally to see if the rate of errors
exceeds the specified rate
o if the number of errors has increased by more than 100 in this 5 minute period, proceed
with the next section on drive replacement

NEXIO
Tech Guide LLM
Lab 6 - LLM
1. Initialize a raid set

• ECC
• Parity
2. Replace a fibre channel drive
3. Reseat a fibre channel drive

NEXIO
Tech Guide LLM

NEXIO
Tech Guide Workflow
Workflow
This chapter describes a standard television workflow and how our video servers affect that workflow
This chapter includes the following sections:
 NEXIO Servers installed in a facility that have automation

 NEXIO Servers installed in a facility that does not have automation
NEXIO Servers installed in a facility that have

automation
Facilities that have automation generally do not use the server LLM and NXOS applications. The NXOS
application is used to monitor video content, playback clips, from any channel or to test a record channel.
Starting NXOS
Use one of the following desktop icons to start NXOS:
 NXOS — Starts NXOS only
 NEXIO Startup — Starts NXOS, the LLM(s), and FTP Server
In general, use the NEXIO Startup shortcut icon to start NXOS. Use the NXOS icon only if the LLM(s) and
FTP Server are already running.
To start NXOS
1 From your desktop, double-click NEXIO Startup or NXOS. The Log On dialog box appears.
2 In the Accounts list, select Administrator. This is the default Administrator user name. In the User Name
text box, Administrator appears.

NEXIO
Tech Guide Workflow
3 In the Password text box, type system. This is the default password.
4 Click Log On. The NXOS main window appears.
1 Open a record channel window and the MediaBase window.
2 Click Add ID. The New ID dialog box appears. Type an ID and (optionally) a Description and Duration.
If you leave the duration at 00:00:00:00, NXOS performs an open ended recording. An open ended
recording ends when you stop it manually
Add ID Dialog Box

3 Click OK. The Channel 1 window enters Record Ready mode. The ID has been created, but no material
has been recorded.
4 Start Channel 1 recording by positioning the mouse cursor over the Record button.

NEXIO
Tech Guide Workflow
a. Hold down the left mouse button .

b. Tap the right mouse button to begin recording.
The Record button changes color , and the time code position field begins to count up. The status
indicator along the bottom of the window shows a “Recording” message.
5 Click STOP or PAUSE to stop recording.
You have just made your first recording. Refer to the next section, Playing Media, to play back what you
have just recorded.
Playback an clip ID
Moving a Clip ID into a Channel Window
You can move clip IDs from MediaBase to a channel window using the drag-and-drop feature.
To move a clip into a Channel window
1 Click on the MediaBase icon on the toolbar to open the MediaBase window.
2 In the MediaBase window, select an ID.
3 Over the highlighted ID hold down your left mouse button. A document icon appears.
4 Continuing to hold down the left mouse button move the document over to the channel window using
the drag-and-drop operation. The channel window now shows the ID as loaded.
5 Click Play.

NEXIO
Tech Guide Workflow
Loading a Clip ID into a Channel Window

You can load clips into one of the channel windows. The clip ID format must be supported by the current
channel configuration. For example, you can load SD clips into an SD playout channel window.
For 4 or 6 channel configuration, you cannot load HD clips into a configured SD playout channel window.
To load a clip:
1. In the channel window, click Load ID.
2. Type the name of the desired ID.
3. Click OK or press <ENTER>.
The ID can now be viewed using any of the transport controls in this window.
NEXIO Servers installed in a facility that do not have

automation
To start NXOS
1. From the desktop double-click NEXIO Startup or NXOS. The Log On dialog box appears.
List of the buttons, from left to right:

• Open Channel 1
• Open Channel 2
• Open Channel 3 (Four Channel Systems Only)
• Open Channel 4 (Four Channel Systems Only)
• Open a new PlayList
• Open MediaBase
• Open the Digitize window

NEXIO
Tech Guide Workflow
• Open the Tapebase

• MediaBase Find
• MediaBase Preview
Your First Recording
The following section describes how to record media. Typically, media content is ingested and stored in
MediaBase.
To record media
Open a record channel window and the MediaBase window.

NEXIO
Tech Guide Workflow
Click Add ID. The New ID dialog box appears. Type an ID and (optionally) a Description and Duration.
If you leave the duration at 00:00:00:00, NXOS performs an open ended recording. An open ended
recording ends when you stop it manually.
Different recording types:
 Duration clips
 Open ended
 Loop clips.

NEXIO
Tech Guide Workflow
Digitized Recordings
This window is the main controller for an external VTR connected to the video server. In
addition the capability exists here to create a new entry into MediaBase and record
desired material from a tape into that ID in a frame accurate manner. Operation of the
transport controls are the same as that of the channel window, except for lack of a
record button.

NEXIO
Tech Guide Workflow
NXOS Media container types

NEXIO
Tech Guide Workflow
NXOS - Media container types

NEXIO
Tech Guide Workflow

NEXIO
Tech Guide Workflow
Day 4 - Agenda
 Q & A Session
 Workflow Overview
 NXOS Admin functions
o Lab 7 - NXOS Admin functions
 Playlist
o Lab 10 – Playlist
 Creating traffic filters
 Traffic Filter Troubleshooting Procedure
o Lab 11 - Traffic filter
 FTP Client
 Video formats that can be transferred to the SAN
o Lab 12 - FTP Client

NEXIO
Tech Guide Workflow

NEXIO
Tech Guide Workflow
NXOS Admin functions

System Setup
The Setup window is only accessible to users with Administrator rights.
Select the Remote check box to allow that channel to be locked by an external command.
Select the All check box to lock that channel locally, from NXOS. Click Apply or OK to lock the
channel immediately.

NEXIO
Tech Guide Workflow
VTR Tab

NEXIO
Tech Guide Workflow
Warning Tab

NEXIO
Tech Guide Workflow
Deleting clips
2. A single clip can be deleted or multiple clips by selecting multiple clips and selecting delete from
the MB.
Other method of deleting clips is by using a DeleteList (also called a PurgeList).
3. Create a simple Unicode text or XML document that specifies the clip IDs that need to be deleted.
4. The clip Ids should lined in the same column.
5. Works like a delete filter

NEXIO
Tech Guide Workflow
Lab 7 - NXOS Admin functions

1. Purge list:
 Create a text unicode document
o Enter an IDs that you want to delete.
o The clips must line up on specific column
o Process the purge list using the “deleted Options”
o Verify that the clips were deleted from the media base
2. Record a clip
 Trim it
 Create subclips

NEXIO
Tech Guide Workflow
CONSOLIDATION
The concept of Consolidation was designed for freeing up the “non-SubClipped” space on the
Logical Disk. A Parent ID with a duration of 30 minutes and a one minute SubClip from the
middle of Parent ID, using consolidation to delete all but the one minute SubClip can free up 29
minutes of space.

NEXIO
Tech Guide Workflow

1. Consolidating a clip:
 Create a 2 minute parent clip
 Crate 4 sub-clips
 Consolidate the parent clip
 Play the parent clip. How does the PB look?
 Play the sub-clip. How the video look?

NEXIO
Tech Guide Workflow
Creating new users

 To access the “User Manager” you must login as administrator.
 Once a new admin account is created the default admin account is removed.
 The first time a user is created the user name is the password
To change the password login as the new admin:

Go to User Settings > Change Password
User Settings
You can change and save user defined application settings by navigating to User Settings>Modify
Settings.

NEXIO
Tech Guide Workflow
User Settings

NEXIO
Tech Guide Workflow

NEXIO
Tech Guide Workflow
Removing Hot Key Assignments

To remove a Hot Key assignment Right-click on the desired key and select Remove
Assignment.

NEXIO
Tech Guide Workflow
1. User settings management

– Create a new user and set as a template.
– Use the template to assign other user the same rights.
– Verify that the right are the same.
– Note that the default admin user is gone because we created a new admin user.
2. User settings
– Change the kill date.
– Record a new clip and verify that the kill date value took.
– Modify the hot keys and verify the new keys work.

NEXIO
Tech Guide Workflow
Playlist
• PlayList provides clip playout capability on as many as four NEXIO™ channels simultaneously.
• You can build a list of clips for sequential or timed playback.
• Create loop lists.
• Trigger GPI events during playback.
• Import traffic files and store playlists to disk.
• You can open multiple PlayList windows simultaneously, but only one can be assigned to a server
channel at a time.
PlayList Window
To open PlayList use one of the following methods
1. In the NXOS toolbar, click New PlayList. OR
2. From the main menu, choose View > PlayList > New PlayList to open a new (empty) playlist
window.
PLRealtime must be installed and running on the NEXIO server that PlayList controls. NEXIO Software
Release 6.0.0 or higher installs PLRealtime automatically. The current playlist can be installed on the
server or any PC connected in the NEXIO LAN.

NEXIO
Tech Guide Workflow
1 PlayList Toolbar
2 Clip Timer
3 Current Time
4 Alarm Section
5 Segment Timer
6 Function Section
7 PlayList Section
8 PlayList Status Area
1. The PlayList Toolbar enables you to open a new playlist, load an existing playlist, save a playList,
insert items, lock a playlist, and open the GPI window. For more information.
2. The Clip Timer counts down to the end of the clip currently on air. This clip is highlighted in cyan in the
PlayList, and the label beneath the timer shows the clip’s ID. The label ”On Air“ appears in the clip’s
status column.
3. The Current Time field displays the server’s clock — which can also be synchronized to your facility’s
”house“ clock.
4. The Alarm section can include up to two blinking alarm icons, plus a number that indicates how many
alarms of the indicated type are present in the PlayList. Refer to the Status and Alarms.
5. The Segment Timer displays the time remaining until the next EOS (End of Sequence) marker, or until
the end of list. When you ”set start“ on a particular event, the timer recalculates the break duration
from that point forward.
6. The Function section provides the status fields and buttons.
 Select the Lock check box to prevent changes from being made to the current PlayList. Deselect
the check box to allow PlayList editing. Note that the box is automatically selected whenever
playback begins (either via the Start button or via GPI).
 Click Start to start list playback from the current ”set start“ position (as indicated by an arrow in
the PlayList), or at the top of the list if a start position has not been set. In the list, the clip is
marked ”On Air,“ and the Start button has no effect once playback has started.
 Click Stop to stop list playback. In the list, the clip is marked ”clipped.“ If Start is clicked, the
clipped spot starts again from the beginning.
If you right-click the button, you can change the button’s mode (and label) to ”Pause.“ The mode can be
changed during playback.
7. The PlayList section lists all of the events, markers, and messages in
the current PlayList.
8. The PlayList Status area provides information on the status of each

server including their name and channel description.

NEXIO
Tech Guide Workflow
PlayList Toolbar
1 New PlayList 4 Insert Items

2 Open PlayList 5 Lock
3 Save PlayList 6 GPI
The Save PlayList menu has the following options.

 Click Save to save the current playlist.
 Click Save As to save the current playlist with a different name or in a different location.
Click Insert Items to display the Insert menu
 Click New as-run log to insert an “New as-run log” marker in the PlayList. When the list reaches
the marker, a new as-run log is generated using the settings specified in the Client Settings tab.
 Click Link Event to open the Input Linked PlayList dialog box.

NEXIO
Tech Guide Workflow
PlayList Columns
PlayList columns can be customized in a variety of ways, however, you cannot sort by column.
To rearrange a column, click and drag a column heading to the new desired location. To change the
column width, place your cursor between column headings until the double-headed arrow appears. Click
and drag the edge to the desired width. To change the fields shown in a PlayList Window, right-click any
column heading to display the Field Chooser dialog box.

NEXIO
Tech Guide Workflow
PlayList Columns definition
Field Description
Video Type The video type of the recording (MPEG or DV). If MPEG, the profile is also shown.
A five character field used to categorize clips, such as COM, PGM, PROMO, PSA, NET,
Type etc.
The Agency field supports textual information as populated by the traffic system. The
Agency traffic import filter must be properly configured.
The Event Code field supports information as populated by the traffic system. The
EVT Code traffic import filter must be properly configured.
The Slot# field supports information as populated by the traffic system. The traffic
Slot# import filter must be properly configured.
Video
Information Shows the video resolution and frame rate of the clip.
Data Rate Shows the bit rate of the video portion of the compressed signal.
Aspect Ratio Indicates if a clip is 4:3 or 16:9.
GOP The complete GOP structure for an MPEG clip.

NEXIO
Tech Guide Workflow
Playlist Pop-up Menu
Right-click on any clip on the playlist and the playlist pop-up menu will appear.
• Recue to re-cue and play the current (on-air) clip from the beginning.
• Next to immediately cue and play the next event.
• Save (or press Ctrl + S) used to Save playlist.
• Save As allows you to save the current PlayList.
• Open (or press Ctrl + O) allows you to open a saved PlayList replacing the current list.
• Append is used to append a list from disk to the end of the current PlayList, a playlist
can only have 2000 entries.
• Traffic is used to import a program log and automatically create a playlist.
• Close File used to close the current PlayList file.
Recue - to re-cue and play the current (on-air) clip

from the beginning.
Next - to immediately cue and play the next event.
Save - (or press Ctrl + S) used to Save playlist.
Save As - allows you to save the current PlayList.
Open - (or press Ctrl + O) allows you to open a saved
PlayList replacing the current list.
Append - is used to append a list from disk to the end
of the current PlayList, a playlist can only have 2000
entries.
Traffic - is used to import a program log and
automatically create a playlist.
Close - File used to close the current PlayList file.

NEXIO
Tech Guide Workflow
Playlist Alarms
 The yellow alarm indicates an event that cannot be found in the MediaBase. The ID may have
been deleted from the server.
 The red alarm indicates that an event has passed its kill date and expired.
Messages
The playlist status are written into an asrunlog file (ARL file), which can be specfified by the end user.

NEXIO
Tech Guide Workflow
Lab 10 - Playlist
1. Create playlist which has:

– Time event
• Absolute
– Insert
• Ids
• EOSs

NEXIO
Tech Guide Workflow
Creating traffic filters
Make sure the program log file is an ANSI file format.
1. Open a playlist, on the white space right click, select Traffic, and then select Generate Traffic
Filter.
2. Click the NEXT button.
3. Type name of traffic filter and click NEXT.

NEXIO
Tech Guide Workflow
4. Click the Browse button and open the traffic program log the click NEXT.
5. Select the drop down box and select filter statement then press NEXT.

NEXIO
Tech Guide Workflow
6. Select any one line that contains the ID information, the highlighted line will appear
under “traffic file line” header. Highlight the indicator that specifies an ID is present on
that line then press NEXT.
7. Now highlight the entire ID, this will define the start and end position of the ID. Thus, the
ID length will be defined, now press NEXT.

NEXIO
Tech Guide Workflow
8. Highlight the entire description field and click on NEXT.
9. Highlight the entire duration field, now click on NEXT.

Note: The actual duration field that is used for each ID is extracted from the Mediabase.
10. Highlight agency field if required or provided by the traffic company not all traffic use an agency
field.

NEXIO
Tech Guide Workflow
11. Highlight slot number field if required or provided by the traffic company not all traffic use
a slot number field.
12. Highlight event code field if required or provided by the traffic company not all traffic use
an event code field.
13. At this point you have to select FINISH or click NEXT to ad a different filter statement to
apply a target, label, EOS, EOS E-E or a goto.

NEXIO
Tech Guide Workflow
14. Once the filter is created you can go back to step number six and specify other ID
indicators or edit the filter using notepad as shown below. The ID indicator for the
example below is 8 if any additional indicators need to be added just copy the entire line,
insert it below the other, and replaced the 8 with other possible ID indicator.
15. The example below can have up to 35 possible ID indicators 0 thru 9 and A thru Z. The
example below only covers 0 thru 9, A, B, and C. We still need 22 possibilities which are
D thru Z.
16. Set the filter as default by Right-Clicking on the playlist, select traffic, set default filter
file, browse for the traffic filter file, and select OPEN.
17. To import a traffic file follow the same procedure as step 16, but select import traffic file,
select browse, and then select the program log file.

NEXIO
Tech Guide Workflow
Traffic Filter Troubleshooting Procedure
The example below provides a colored coded key guide that defines all the variables used on
an ID line. Thus, allows the end user to understand and edit the filter file needed.

NEXIO
Tech Guide Workflow
Lab 11 - Traffic filter
1. Create a traffic filter using an OSI program log file.

NEXIO
Tech Guide Workflow
FTP Client
FTP client application that allows access to the FTP server built in to NEXIO servers. Simplifies
transfers of audio and video content into and out of your NEXIO server system. Transfer clips
between server domains LXF files. Transfer clips from the raid to folder or mapped drive to
archive. Import clips from DVCPRO P2 or XDCAM decks..
Video formats that can be transferred to the SAN
Also SCC, Media Stream, and DNx files can be import to our SAN.

NEXIO
Tech Guide Workflow
FTP Client Configuration
1. To add a FTP connection -> right click on FTP connections -> Select Add FTP
Site.

NEXIO
Tech Guide Workflow
2. Add a local connection
Adding a remote drive connection

NEXIO
Tech Guide Workflow
Add a FTP connection on another domain

NEXIO
Tech Guide Workflow
Localhost- Open in Separate Window
6. Open folder connection in a Separate Window

NEXIO
Tech Guide Workflow
7. Drag and drop local window to folder connection

NEXIO
Tech Guide Workflow
. After the clip transfers FTP server will display a transaction success message.
You are now able to use NXOS to drag/drop the transferred ID to a playout codec, or use
Playlist or an Automation system to load and play the ID.

NEXIO
Tech Guide Workflow
NXOS FTP
FTP connections can also be done within NXOS.

NEXIO
Tech Guide Workflow
Lab 12 - FTP Client

1. Setup a FTP transfer between a folder and a server.
2. Setup a FTP transfer between servers.
3. If available demonstrate the functionality of the P2 and XDCAM decks with our servers.

NEXIO
Tech Guide Workflow
Day 5 - Agenda
 Assessing System Health
o Server Health
o Hardware Level
o Operating System Level
o Generic PC Component Health
o Network Properties
o Fibre Channel Health
o Video I/O, Codec Health
o Miscellaneous Elements Health
o System Health – Ethernet
o System Health – Fibre Channel
o Operational panel for JBOD
o Operational panel for SBOD
o System Health – Fibre Channel
 Issue Resolution
o Server Configuration – Hardware
o Hardware/BIOS/Firmware
o Server Configuration - Operating System
o Memory configuration
o Naming convention
o Ethernet negotiation
o Windows Registry Editor
o Server Startup
o NEXIO Startup Configuration Aplication
o Fibre Channel
o Array drive firmware
o Fibre Channel Switch Settings
o System Benchmarking
o Configuration – System Elements
o Configuration – System Elements
o Data Gathering Procedures
o Troubleshooting Software Problems
o FXP Error Conditions:
o FXPLOG.txt
o LLM CODEC Window
o Display Settings
o Network Adapter Settings
o NX3601HDX I/O Specifications

NEXIO
Tech Guide Assessing System Health
Assessing System Health

The first section will cover assessing the health of individual servers. The second section will cover the
Ethernet and fibre channel systems external to the server.
Server Health
Working from the bottom up, indications of the health of core server subsystems can be obtained at
various levels:
Hardware
Motherboard monitoring, FC card BIOS
Operating system
Driver tools and OS applets/utilities
Harris applications
Higher level view
Running statistics
Taken from various levels - quantitative data over a time period
Log events
Time stamped detailed sequence of events that shed light on exact nature of problems that the above
indicators allude to (Log events are covered separately at the end of this section).
We will be assessing health of core server subsystems, by starting at the lowest, simplest levels, and
building up from there. This will make you familiar with “early” indications of system health, without which,
the higher functionality Harris applications will not work anyway.
Knowing these techniques makes it possible to accurately assess conditions, when for instance, Harris
applications will not start. In typical troubleshooting however, you will start from the higher levels, and only
work down to these lower level techniques if problems are observed

NEXIO
Hardware Level
Generic PC Component Health
NX3801
LED Label Color Description

Overheat Red Indicates that the motherboard or video I/O card temperature
is above the critical threshold
Fan Fail Red Indicates that the front fans or CPU fan have stopped rotating
or falls below programmed RPM limit
Power supply Red Indicates a problem with one or both of the power supply
connections
Media Red Os drive or storage drive error
3600/01:

PS Good Green Indicates that one or both of the power supply connections is
operating
PS Fault Red Indicates a problem with one or both of the power supply
connections
is above the critical threshold.
Note: that the logic for the power supply LEDs is different between the two Series
• One green “good” indication for each supply (driven directly from hardware; no NEXIO Monitor
involvement)
• An overall green “good” and a red “fail” indication (driven by Nexio Monitor).
An overall green “good” and a red “fail” indication (driven by NEXIO Monitor).

NEXIO
Operating System Level
Device Manager
Firewire 3801
USB 3801
Firewire 3600/01

NEXIO
USB 3600/01
Note: The HASP dongle is now replaced by the software license key options that enable different
options via software.

NEXIO
Device Manager
SATA RAID 3801HDX/HDI:

NEXIO
SATA RAID 3600/01HDX/HDI:

NEXIO
Device Manager
Fibre Channel NX3801HDX
HDI and HDX Windows will recognize the storage drives.
Fibre Channel NX3600/01HDX

NOTE: NX301HDI Windows disk management will detect the drives and ATTO Tools Configuration
application is use to create the internal storage raid.
Fibre channel card NX3600/01HDX

NEXIO
Nexio Monitor
IT industry standards allow hardware to provide status information to the Windows operating system. This
Harris application displays some of this information, and also displays some status information reported
by LLM.
3801 & 3600/01:
A green indicator says there is no issue. The following icons indicate a problem condition in both Series:
• Fan – three fans are monitored:

o 2 mounted behind NEXIO’s front panel
o CPU fan
• Temperature – two temperatures are monitored:

o CPU temperature
o PCI server board temperature
3xxx Models Only:

• Power supply status information is available at the OS level in the 3xxx Series
• The Nexio Monitor GUI will set these indicators green if there are no issues
• When an error icon appears, the NEXIO Monitor icon in the System Tray will alternate between
that error icon and its normal indication.
• NEXIO Monitor also illuminates the appropriate front panel LED. In the bottom row, the left-most
LED is Fan Fail; the centre LED is OVERHEAT
NOTE: If the Nexio Monitor application is not running in Windows, the front panel LEDs will not indicate
these error conditions!
NX3801

NEXIO

is above the critical threshold
Power supply Red Indicates a problem with one or both of the power supply
connections
Media Red Os drive or storage drive error
Generic PC Component Health
Ethernet Health
NX3601 G1:
NX3601 G2 Intel Pro 1000GT uad port
NX3801

NEXIO
Network Properties
The new NX3801 operating system is Windows 7, NX3601, and older models are Windows XP.
Before Windows XP Service Pack 2:

• No connection: “x”-ed icon and “Network cable unplugged”
• Connection: standard icon and “Enabled”
With Service Pack 2:
• No connection: standard icon and “Network cable unplugged”
• Connection: standard icon and “Connected”
Ethernet Health
My Network Places
• View all server nodes

NEXIO
Harris Application Level

LLM: Nodes pane
• Confirm that each server currently running LLM appears
NOTE: If Ethernet connection disrupted, even momentarily, affected node will disappear from Node pane
on other servers and will not re-appear until LLM on affected node is restarted – “Play-only mode”
Running Statistics
LLM: Nodes pane
• Right -click for Link Inits / Retries
o Link Inits indicate newly started LLMs since local one was started
o Retries indicate re-sent TCP/IP packets due to failed responses

NEXIO
Fibre Channel Health

The ultimate goal of the fibre channel subsystem is to get data to and from the array drives. There are
several categories of fibre channel health. Each category in the following list requires the one above it to
be for the most part functional, in order to proceed.
• The fibre channel signal path
• Communication to array drives
• Read/write errors on array drives
• Logical Disk health
Hardware Level
ATTO BIOS utility - Communication to drives:
• Scan Fibre Devices drive listing

NEXIO
OS Boot up - Communication to drives:

Array drives polled while Windows fibre channel card driver loading (Windows progress bar screen). A
flash of each drive’s LED will ripple through the array.
Device Manager - Communication to drives:
NX3801
The newer NX3801 server models do not use Harris Windows driver LLMDisk1.sys masks the array
drives from the operating system.
NX3601/00 and older models

The proprietary Harris Windows driver LLMDisk1.sys masks the array drives from the operating system,
in order to give Harris software exclusive access to them. When this masking occurs, it results in the
following indication in Windows Device Manager
Note: that when working correctly, each drive in the array must appear in Device Manager with the
icon.

NEXIO
RaidTools - Communication to drives:

Presence of individual drives in Available Disks pane on DISKtools tab confirms that server has
communication with them
On systems with larger arrays, it is not as easy to quickly verify that all drives are present in the DISKtools
tab. By selecting the DISKinfo tab and scrolling to the bottom, the Total Disks quantity quickly confirms
whether or not the expected quantity is present. (With Xyratex arrays, the total is typically in increments of
16, or sometimes of 8).
Front Panel LEDs – Fibre channel signal path:

NEXIO
NX3801
NEXIO Monitor will illuminate the bottom LED red when there is a fibre channel error.
NX3601/00:
NEXIO Monitor will illuminate the top right LED yellow when there is activity on either the fibre channel or
SATA array connection.
NOTE: The LED will only indicate activity initiated by the codec (i.e. LLM). It will not display activity
initiated at the driver level (i.e. fibre channel / SATA polling of array on Windows startup), nor activity
initiated by RaidTools read tests.
NEXIO Monitor - Read/write errors:

NEXIO Monitor’s LLM status indicator will illuminate either yellow or with an icon when read or
write errors reach a frequency of 5 per minute.
When this error icon appears, the Nexio Monitor icon in the System Tray will alternate between and its
normal indication -

NEXIO
Icon in System Tray - Read/write errors:

LLM will place a red disk icon with a yellow exclamation mark on it in the System Tray (the bottom right
corner of Windows Desktop) if the server in question is accessing the array, and accumulating 4 or more
errors in a 20 second interval
Clicking on this icon makes it disappear (at least temporarily), and brings the LLM window to the front, in
preparation for diagnosing the situation.
LLM - Logical disk health:

1) Verify healthy logical disk: gray disk icon

NEXIO
2) Right click logical disk, and choose Properties, General tab:

• View the usage pie chart to verify expected usage
Note: that Free Time values are calculated based on the current Channel 1 compression settings.
Segments are Mediabase entries. Similar to when Free Time reaches zero, no recording can be done, if
Free Segments reaches zero, no new recordings can be initiated.
3) Right click logical disk, and choose Properties, Information tab:

Ensure there are no circle/slash drives

NEXIO
NXOS – Remaining Space:

When problems are encountered making recordings, a quick check that there is available storage space
may be warranted. In addition, the LLM pie chart remaining time information can also be viewed in the
NXOS View menu:
Running Statistics
LLM - Read/write errors – total array errors:
Right click logical disk, Properties, Information quantities here pertain only to local server’s drive array
usage quantities represent error totals from all array drives as relates to this local server
Note: Although the pattern of overall errors across a system’s servers can be determined by observing
the above window on each server, a much more efficient way to accomplish this is by taking advantage of
the central error logging functionality provided by Nexio Manager.
Fibre Channel Health

NEXIO
LLM - Read/write errors – individual array drive errors:

Inside Properties, Information tab right-click on individual drive and choose Errors. Quantities here
represent error totals from that individual array drive as relates to this local server’s drive array usage
Although the pattern of errors across array drives could be determined by right-clicking on each
individually in the Information tab, a much better tool is provided:
Right-click logical disk, Error History:
Error History:
Chart shows read/write errors per individual physical drive:
• Chart is auto-scaling; full bar may only represent 1 error.
• Errors shown here relate only to the activities of the local server.
• Servers that have not actively accessed the array while the problem exists will therefore show no
errors.

NEXIO
Video I/O, Codec Health

Device Manager
3801
• PCI video express card
• Drivers MA.sys and ksthunk.sys
• Device name is MA000
3601/00:
• PCI video express card
• Drivers MA.sys and ksthunk.sys
• Device name is MA200
Nexio Monitor
Although Nexio Monitor is technically a Harris application, this indication is essentially hardware-related,
and being reported at the operating system level:
Nexio Monitor’s Temperature status indicator will illuminate either yellow or with an icon when any
video card temperature rises above a defined acceptable level. When this error icon appears, the Nexio
Monitor icon in the System Tray will alternate between this icon and its normal indication - .
Nexio Monitor also illuminates in red the centre LED in the bottom row on the front panel

NEXIO

On the LLM: Nodes pane double click on the Local Node for Codec status.
• Read and Write Activity fields: throughput during record/playback - typically > 80,000 Kb/s.
• Buffer Usage field: PCI express card buffers - peak use / available if peak use exceeds available,
buffer overruns have occurred.
• Drift fields: frames that failed to play, in HH:MM:SS:FF.

NEXIO
3801 & 3601/00: NXOS

Highlight a video channel, then choose Channels from the menu bar then select “Video Configuration”
Verify presence of external reference, play a clip from the selected codec and time the codec on the input
configuration window interface.

NEXIO
Miscellaneous Elements Health

The checks in this section are simply to verify the existence of the described indicators, which are
necessary for the described function to be operational
Device Manager
RS422 / GPI Functions (After burner 3 card).
Task Manager
• In the processes tab, the following functions can be confirmed as operational by the existence of
the indicated process:
• VR Run Server
o vrsvr20.exe
• Nexio Monitor
o NexioMonitor.exe
• GPI and control driver
o Bulkusb.sys & bulkusb.inf - links GPI functionality from Antona Serial card to LLM
• Leitch Timeline Playback
o TLPlayback.exe – on editing servers and transmission servers that need to play back
Media IDs
• SATA storage raid driver

NEXIO

System Tray
The presence of the appropriate icon shows the following are functional:
VR Run Server
Nexio Monitor
LLM
System Logs
• Event Viewer startup messages
3601HDX/I:

NEXIO
System Logs
The core logging information from Harris applications is provided by LLM. This information can be broken
into two groups: message logging, and quantitative logging.
Message Logging: LLM Codec window

• Details on LLM events originate as time stamped log entries in the codec window Errors field
“Next” button steps forwards through time to view recent errors

NOTE: One time viewing here only! "Next" clears error events from temp buffer!
The event details from the codec window Errors field may also be written to log files in one of two ways:
Servers running software versions older then NEXIO 5.7.1 the file “errlog.txt” exists in the same folder as
the server’s LLM application (“c:\vr”) at the time when the LLM application launches, these events will
automatically be appended to it.
This file is not limited in size; it grows indefinitely. Although this is only typically 1 Mbyte a day maximum,
it’s important to ensure that it never fills up the system drive
Keep in mind that this file only retains events from the local server. To get full system information using
local log files, “c:\vr\errlog.txt” must exist on most servers in the system.
The server running NEXIO 6.0.0 or higher software versions has new log file logic that limits the size and
age of log files generated by the LLM and FXP. This feature prevents log files from growing too large to
be useful in troubleshooting issues. To enable, use NEXIO Config's LLM tab to change the setting for
LogLimitKB to a size value in kilobytes that determines when a log file will be closed a new log file is
opened to take its place (recommended setting: 32000). Each succeeding log file name will be appended
with the date and time stamp of its creation. There is also a setting called LogDeleteAfterDays which sets
in days how long log files will be kept on the hard drive before being automatically deleted (recommended
setting = 3). In order for this feature to work, you must first create the following empty files in the
C:\VR\logs\LLM folder: trace.txt, tracevdcp.txt, rwerrorlog.txt and errlog.txt. Also create an empty
fxplog.txt in the

NEXIO
C:\VR\logs\FXP if you want to record that log file as well.

Level of Detail
Default message logging configuration captures only critical events. To log in more detail, it is necessary
to edit the registry. The following registry entry causes most significant event information to be logged.
The logging level can also be set using the NEXIO Config application:
[HKEY_CURRENT_USER\Software\asc audio video\LLM\Control]

"DebugOptions"="LOUTH,TCP,SERIAL,LINKINIT,CODECINIT,UDP, SAVEDISK=3600=5,TCREADER“
This level of information allows identification of most operator actions, which can then be compared
against the operator’s observations on the perceived problem, and possibly coincident hardware error
messages, to help isolate the nature of the issue

NEXIO
Debug Options
Debug All of the LLM’s can have any options enabled. If a particular LLM does not support one option or
the other, then it is completely and safely ignored.
• My personal “default” LLM DebugOptions are: “TCP UDP SERIAL LOUTH CODECINIT
LINKINIT OVERWRITE”.
• On at least one server per domain (but no more than two!), add the “SAVEDISK=3600,9”
DebugOption. This will ensure that at least one server has a backup copy of the RAID FAT to
assist you in the event of a catastrophe.
• Always create a blank C:\VR\fxplog.txt and C:\VR\errlog.txt, even if you have no options
enabled! This will ensure that it at least logs critical errors and startup/shutdown times.
The Mirror logs themselves are in the C:\Datastream\Logs\ folder. You need to set
HKLM/Software/Harris/MirMgr/Settings/DebugMask to decimal (15) for Mirror to debug log. (May also
be in HKCU/Software/ASC Audio Video/MirMgr/Settings depending on version). This will cause the
Mirror application to show you the command-line arguments that Mirror uses when starting up the LLM’s,
do not be alarmed at the pop-ups!
The DebugOptions that I know to exist are:
 TCP
 UDP
 SERIAL
 VRMGR
 LOUTH
 CODECINIT
 LINKINIT
 DTA
 OVERWRITE
 SAVEDISK
 VERIFYXOR
 TCREADER
 TRANSITIONPAUSE
 CLIPSYNC
 CHECKDISK
TCP, UDP, SERIAL, and VRMGR

 Monitors and reports requests to the LLM to perform an action. The request is only put in errlog if
it is understood - these options have a limited scope of knowledge. Not all of the Leitch Native
and Louth protocol commands will generate an entry. Essentially, as troubleshooting was
required for a particular command, then the command was added to the “watch list” that these
options will capture.
 NXOS uses TCP, as does Nexio Remote (same application).
 ICM uses TCP
 The Nexio and VR Manager do not send commands to the LLM via the normal TCP or UDP
sockets, therefore a special DebugOption was created to watch commands passed from the
Manager.
 SERIAL will capture any command coming in from the RS-422 ports. Usually used for VDCP
automation control.

NEXIO
Debug Options (continued)

LOUTH
 Reports all LLM actions as the result of the requests above. This is the feedback that the LLM
has not only received the request, but has understood and is performing an action. The same
limited command-set applies as above, not all actions are reported.
CODECINIT
 Reports the audio to video sync/offset within the codec (software or hardware) at the moment that
a recording starts. This is useful to troubleshoot any record issues, since it shows that the codec
is not starved or overflowing buffers.
LINKINIT
 Reports every time an LLM joins or departs the domain. This is useful to show when an LLM is
having connect issues, because it will be dropping and rejoining frequently.
DTA
 Reports any DTA-mode activity to/from the LLM. This is most common with FTP transfers, but
NXOS itself also creates occasional DTA activity. Most useful for troubleshooting issues with
FTP transfers. If you conduct a very high number of FTP transfers per day, it is not
recommended to enable this option unless necessary. Errlog will grow to a large size very
quickly.
OVERWRITE
 Reports any time the LLM is told to overwrite an existing clip. This would be seen if a topical
promo name is not changed from day to day, and is reused. Not implemented in all LLM
branches.
SAVEDISK
 This allows the LLM to store a backup copy of the RAID FAT table on the local C:\ drive in the
event of a catastrophe which results in an irrecoverable logical broken-disk.
o SAVEDISK=(seconds between saves),(number of stored copies less than 10)
o An example would be: “SAVEDISK=3600,9”. This would store 9 copies at 3600 seconds
(one hour) between each copy. Not recommended to go below 30 minutes as this
creates a large overhead load to fibrechannel to download.
o Local saved copies are named “SNAPSHOT_0_n.DAT”. The latest stored copy is always
the highest numbered copy. As new copies are made, the number of the previous copy
is decremented until it reaches 0. Therefore, every new copy will delete the
“SNAPSHOT_0_0.DAT” file, and rename “SNAPSHOT_0_1.DAT” to “0_0”, and so on.
 Currently in LLM versions (and higher):
o 506.59.28 - NT4 for VR420/VR440 [November 02 / M2 / Update (patch) required]
o 6.07.95.116 - WinXP for NX4200/3600 (.95 branch, no up/down convert) [Baseline
3.3.1 required]
o 6.07.96.11 - WinXP for NX4200/3600/Velocity (.96 branch for VNX, up/down
conversion) [Baseline 3.5.0 pending SQA approval]
o 6.09.95.96 - WinXP for VelocityNX only
TCREADER
 Reports the offset between the codec genlock frequency reference and the external TimeCode
feed (where used). Errlog already reports information when the TimeCode feed forces a reset of
the codec reference, but TCREADER reports the continuous offset several times per second.
This is a very high-volume DebugOption, and should not be left running on operational on-air
servers. It should be used only when there is a question about the stability of the codec
reference, or the external feed.

NEXIO
Debug Options (continued)
TRANSITIONPAUSE
 Causes the LLM to stop at the end of playout of an ID, even if an ID is stacked in the codec for
sequential playout. For troubleshooting only, never to be used for operational on-air servers.
VERIFYXOR
 Forces the LLM to recalculate and compare the checksum of LBA’s and parity data committed to
the RAID. This is an extremely intensive operation, and should only be used for testing – never
on an operational on-air server!! This was designed to detect latent memory errors on a
particular server, or fibrechannel issues related to defective hardware.
CHECKDISK
 Forces the LLM to verify FAT in memory against actual FAT on RAID in n second intervals. For
troubleshooting only, not to be used for operational on-air servers.
 An example would be “CHECKDISK=180”. This would verify memory copy against the RAID
every 3 minutes.
CLIPSYNC
 Functionality and usage unknown

NEXIO
Logging Methods – Quantitative
Logging Method 1: Logging Method 2:

System Wide Local Server Only
Message Logging
original source of error llm.exe
messages
where messages first appear llm codec window (d-click local node)
filename where log entries are c:\vr\errlog.txt NEXIO 5.7.1 or older c:\vr\logs\errlog.txt NEXIO 6.0.0 or
written NEWER.
file contents messages from the local server messages from the local server
only only
how to enable the writing of log ensure that the file "c:\vr\errlog.txt" ensure that the file
entries exists before starting LLM "c:\vr\logs\errlog.txt" exists before
starting LLM
amount of history retained unlimited: entries never get The amount of days kept depend
discarded on the velue set in NEXIO Config.
file size unlimited; typically grows by no The file is specified in NEXIO

more than 1 MB per day Config.
retrieving logs file size can get massive over time. Retrieve the file needed, depending
May warrant opening and copying date the error occurred.
only entries for the relevant day
into a new file
NOTE: do not edit errlog.txt while
the llm is running!

NEXIO
Note: The errlog.txt can be deleted or moved if the LLM is closed and create a new text file with the same
name. If your system consider of MIOH topology NEXIO Manager must be ran on the client machines.
6xx Series LLM Message Logging servers running NEXIO 5.7.1 or older
• With the introduction of the 6xx Series LLM to accommodate servers not using Matrox hardware
codecs, came additional software modules that combined to carry out LLM functions.
• One of these processes – fxp.exe – has its own logging functionality.
• Similar to how the Matrox Digiserver codec writes information to errlog.txt, the fxp.exe process writes
information to c:\vr\fxplog.txt.
• If the file “fxplog.txt” exists in the same folder as the server’s LLM application (“c:\vr”) at the time when
the LLM application launches, these events will automatically be written to it.
FTP Server Logging

The FTP Server application – archdiag.exe – maintains its own logs.
Dated files (1 day per file) are placed into the folder c:\archdiag\Wanlogs.
6xx Series LLM Message Logging servers running NEXIO 6.0.0 or newer
• Create an empty fxplog.txt in the C:\VR\logs\FXP if you want to record that log file as well.
System Health – Ethernet

Verify Ethernet port link status from any server interface

NEXIO
System Health – Fibre Channel

Xyratex DAE

NEXIO
Operational panel for JBOD

NEXIO
Operational panel for SBOD

NEXIO
System Health – Fibre Channel

Qlogic SANbox2-16 Fibre Channel Switch
Qlogic Sanbox5600 Fibre Channel Switch
The System Fault LED illuminates to indicate that a fault exists in the switch firmware or hardware. If the
System Fault LED illuminates, do the following:
 Check the Heartbeat LED for an error blink pattern
 Check the power supply LEDs and take the necessary actions.
Qlogic Sanbox5600 Fibre Channel Switch

 The Heartbeat LED shows an error blink pattern for the following conditions:
 2 blinks - Internal Firmware Failure Blink Pattern
 3 blinks - System Error Blink Pattern
 4 blinks - Configuration File System Error Blink Pattern
5 blinks - Over Temperature Blink Pattern

NEXIO
Tech Guide Issue Resolution

NEXIO
Issue Resolution
There are literally hundreds of configuration settings on any server. A single incorrectly configured value
may affect a server’s operation, render it non-functional, or in some cases, cause a corruption in the
media file system that could possibly result in the complete loss of a system’s media.
Exercise extreme caution whenever making a change to a server’s configuration. If not 100%
confident regarding a change being made, contact Harris Technical Support for advice.

NEXIO
Server Configuration – Hardware

Hardware/BIOS/Firmware
Motherboard Jumpers
3600HDX/I:
There are two jumpers that are very important to performance and stability.
• CN21 must be set for 66Mhz
• CN25 must be set for 133Mhz
Motherboard BIOS Settings

Motherboard BIOS is not normally meddled with, so it’s easy to forget its significance. Incorrect settings
here however can have a significant impact on server operation. Checking BIOS early in a
troubleshooting process is not normally justified, however, in situations where symptoms are highly
unusual and possibly widespread, and normal troubleshooting methods don’t seem to make any headway
in isolating the root of an issue, checking BIOS settings is warranted. In older servers, replacement of the
CMOS battery may also be warranted.
4000SD:
Current BIOS is: v6.00PG, dated 06/16/2003
Motherboard model: IWill DP533S Motherboard
3600HDX/I:
Current BIOS is:
Motherboard model: SuperMicro Motherboard
3600/4200HDX/I:
Current BIOS is: DK8NV115, dated 06/09/2006
Motherboard model: IWill DK8N Motherboard
3000VNXES:
Current BIOS is: DKEWV130, dated 5/18/2006
Motherboard model: IWill DK8EW Motherboard
3601HDX/I:
Current BIOS is specified: 3.0.0
Motherboard model: Tyan 2915 Motherboard
3601 G2HDX/I:
Current BIOS is specified: 3.0.0
Motherboard model: Tyan 2915 Motherboard

NEXIO
FC Card firmware/configuration
Fibre Channel configurations that a server may work with can vary. The default BIOS configuration of a
given fibre channel card upon delivery therefore may not be correct for the system it is to be used in.
These settings must therefore be verified during commissioning, card replacement, and any time there
appears to be systemic fibre channel issues.
4zzzSD:
• Details for the Qlogic 2300 card can be found in:
• BU229/SA043 QL2310 modification and BIOS setup
HD:
• Details for the ATTO Celerity FC-42XS can be found in:
• BU356_ATTO FC-42XS DualPorts 4Gbps_HBA
• ATTO FC-42XS-HBA Installation & BIOS_Setup
Serial 422 Card Jumper Settings for Afterburner 2
Jumpers on the card determine whether each port is either a Master or Slave port. 4465/75ES servers are
set one way; 4000TXS/ITS servers are set another. Incorrect setting would mean that port may appear to
be dead, but a crossover or turnaround jumper (that reverses the transmit and receive lines) would rectify
the situation. Also an external null RS422 adapter can connected in serial with the control cable to control
the server.
Afterburner 3 card
The RS422 Afterburner 3 card is normally configured as attributory, in order to control a VTR use a null
RS422 adapter to reverse transmit and receive lines.

NEXIO
Server Configuration - Operating System

Memory configuration
The upper limit of LLM-exclusive memory is defined using the Windows driver “mapmem.sys”. The
number defined in the MemoryStop value below informs mapmem.sys where this LLM-exclusive memory
ends:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MapMem\Parameters]
"MemoryStop"=dword:00001200 (4608)
HD servers have done away with the use of boot.ini “MAXMEM” and define the lower limit using mapmem
also:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MapMem\Parameters]
“MemoryStart”=dword:00001c00 (7168)

NEXIO
Memory configuration - continued
Nexio Model Number MAXMEM MemoryStart MemoryStop

Format
NX3801 Decimal 4096 12288
Tyan 2915-E Hex 1000 3000
NX3601 G2HD Decimal 4476 7492

Tyan 2915
Hex 117c 1d44
NX3601HD Decimal 4608 7168

Tyan 2915
Hex 1200 1C00

SuperMicro
Hex 460 B64

IWILL
Hex 500 C00
NX3000ESX Decimal 4608 7168
Hex 1200 1C00
NX3000VNX Decimal 1920 2178
Hex 780 880
NX4000 Decimal 1520 2048
Hex 800

NEXIO
Networking configuration
In most installed systems, each server in the system is uniquely identified in two ways:
Windows XP’s “Full Computer Name”
R-click My Computer, Properties, select the Computer Name tab, and the full computer name is the
Network Identification name.
Names are specifically configured in the form:
NX???????-xxYYYYYYY , where:
• ??????? is the server model number.
• xx after the hyphen is a number used by the LLM to generate the server’s node number.
• xx must be unique on each server, irrespective of different server types.
• YYYYYYY after the hyphen is from one to seven letters interpreted by the LLM, informing it which
servers are on the same domain – i.e. Which servers are sharing the same storage an example
would be in an ftp scenario, the LLMs on each end must have unique suffix letters, in order for each
to correctly track what media is local to itself, and what is remote.

NEXIO
Naming convention
A typical example system may therefore include the following names:
• NX4000TXS-1A
• NX4000TXS-2A
• NX4000TXS-3A
• NX4475ES-4A
• NX3600HDX-1A
• NX3601HDX-2A
Since the 2.5.1 software release in February, 2005, it is now possible to hard-define the local server’s
LLM node number via a registry entry, irrespective of how the Full Computer name is defined.
These settings are:
[HKEY_CURRENT_USER\Software\asc audio video\llm\Control]
LLMNodeNumber=xx
Where x is a number from 1-32 (DWORD)
LLMDomainLetters=YYYYYYY
Where Y is an alphabetic character(s)
These registry entries, if non-blank, now override any use of numbers or letters in the hyphenated portion
of Full Computer name.
TCP/IP address
Class C subnet “192.168.90.x” always used (subnet mask 255.255.255.0)
The last octet of the IP address is always set to match the hyphenated suffix of Computer name for
example, if Computer name is “NX4000TXS-4”, then IP address is “192.168.90.4”

NEXIO
Ethernet negotiation
Two key parameters affect how Ethernet devices communicate at the hardware level: link speed, and
duplex.
• Link speed is simply the set data rate at which nodes agree to communicate over the link. Current top
speed is 1 gigabit/second, which can also be referred to as “Gig-e” or 1000 megabit/second.
Somewhat older, but still in common use is 100 megabit/second. Legacy 10 megabit/second links are
seldom encountered nowadays.
• Duplex defines whether a link can transmit data in both directions at the same time. A good analogy
is a cell phone link, where when you talk; it interrupts what the other person was saying to you at the
time.
Note: For the network port handling Nexio Net communications (LLM), never leave these settings on
auto; always force them to Full Duplex, 100 Mbps

NEXIO
Windows Registry Editor

All aspects of a server’s configuration at the Operating System level involve the Registry.
Although many of the more commonly adjusted registry parameters have user-friendly GUI-type
application front ends for viewing and making changes (e.g. Nexio Manager, Nexio Wizard), less
frequently considered parameters often can only be accessed using the Windows Registry Editor
(regedit).
NOTE:
• User-friendly front ends for making changes to Windows Registry values often put practical
constraints on data entry.
• No such constraints exist when editing the registry directly. Exercise extreme caution when
using Windows Registry Editor.
• Never make a change unless explicitly instructed to do so by
• Harris Applications
Call Harris Technical Support if unclear or not confident in making changes in the registry.
Some of the key registry branches that may be visited during Registry checks include:
HKEY_LOCAL_MACHINE\SOFTWARE\Harris
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MapMem
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\attomgtd\Parameters
HKEY_CURRENT_USER\Software\asc audio video
NOTE:
Until 2006, most of the Leitch/Harris registry configuration parameters were held in the
HKEY_CURRENT_USER branch.
A migration was started in 2006, such that in the future, all of the parameters will be held under
HKEY_LOCAL_MACHINE\software\Harris.

NEXIO
Be aware that many of the key server parameters are held in “DWORD” registry value types.
When these value types are opened (double-clicking), they default display in Hexadecimal number base.
User-friendly GUI utilities that access these same values (Nexio Monitor, Nexio Manager) always display
DWORD values in Decimal number base.
When accessing DWORD values from Registry Editor therefore, it is advisable to always select Decimal
number base. Doing so will convert the displayed number to Decimal
Default Hexadecimal Base Display:
Decimal Base Display:
Server Startup
3601HDX/I:
When HDX/I servers are booted up, the NxWolf.exe application typically gets called by the NexioStartup
shortcut in the Startup folder. Harris applications that get launched automatically by NxWolf are set with
the following registry entry:
[HKEY_LOCAL_MACHINE\SOFTWARE\LEITCH\NxWolf]
"StartupOptions"=dword:00000000
0 = Everything
1 = LLM and NXOS only.
2 = LLM Only.
3 = LLM and FTP Server (ArchDiag)

NEXIO
NEXIO Startup Configuration Aplication

1. Go to Start -> Programs -> Harris -> Config -> NEXIO Startup Configuration. Double click to open.
Figure 1-1 NEXIO Startup Configuration

2. Uncheck the “All Server Core” check box.
Figure 1-2 Configuration Startup Sequence

NEXIO
3. Select the options that you need to automatically start after boot.

4. For example, I selected LLM FCPort, FTP server, and NXOS. Click on “OK”.

NEXIO
5. Set the LLM Domain, Fibre Channel Port, LLM LAN Address, and LLM Node. The NEXIO application
will automatically start after clicking on the Apply button.
Figure 1-5 Active Domain

NEXIO
6. You login as admin, the password is system. The NXOS application will appear.
Figure 1-6 NXOS login window

NEXIO
7. The NEXIO startup options can be found in HKEY_LOCAL_MACHINE\Software\Harris\NXWolf.
Figure 1-7 Registry Editor

NEXIO
House Time code Interface

Providing that the NXTC2110 is receiving drop frame house-referenced longitudinal time code and its
connected on COM 1 on server labeled as one (NX3601HDX-1A). The same applies to the new time
code device part number NXUSBTC. The following configuration will enable the LLM to set the Windows
OS clock on all servers.
[HKEY_CURRENT_USER\Software\asc audio video\LLM\Control]

"TCReader"="COM1"
If time code is not updating the Windows OS clock, test for the existence of time code on the COM1 port
as follows:
• Launch HyperTerminal
• Select COM1
• Configure as follows: 9600 baud, 8 Data, No Parity, 1 Stop, no Flow Control
• Observe the appearance of HH:MM:SS time values every second
• If time values are appearing here, then the problem is likely with the registry configuration
• if they are not appearing, then one of the following is suspect:
o the longitudinal time code source
o NXTC2110 and NXUSBTC
o cabling between the devices
Even if simple testing appears to reveal that the time code is getting correctly set on the server, it’s
important to verify synchronous operation as follows:
• Shut down any GUI applications and then shut down LLM
• Under the same registry branch, add “TCREADER” to DebugOptions
• [HKEY_CURRENT_USER\Software\asc audio video\LLM\Control]
• “DebugOptions”=”TCREADER”
• Restart LLM
• Start Nexio Manager
• In the Error Message Log, observe the entries that appear every second. Confirm that they do not
drift over time. They should indicate a value less the .020 seconds
If they meet these criteria, everything is functioning fine:

• Shut LLM down again
• Remove the added DebugOptions TCREADER registry value
• Restart LLM
If they don’t meet this criteria verify the following:

• both the server and the time code source feeding the NXTC2110 are both referenced with the
same video reference signal
• the time code source is configured to deliver the proper frame rate and time code type
• retest
• ensure that the DebugOptions TCREADER value is removed once the problem has been rectified

NEXIO
Fibre Channel
DAE Settings for JBOD chassis
Below are the default dipswitch settings on the Ops Panel. Switches number from the top one down. Left
is ON; right is OFF

NEXIO
DAE Settings for a SBOD chassis

NEXIO

NEXIO
Array drive firmware

It is critical that all array drives are running on the appropriate firmware. All drives of the same model
should have the same version, although drives with different model numbers may be mixed within the
same array

NEXIO
Table: Array drive firmware

Capacity Series Model Oracle # SubAssemby ChassisFirmware RaidTools
300 GB Cheetah 7ST3300007FC 146-000065-00 146-000063-00Xyratex XV35 1.2.3
XV32 1.1.17
XV31 1.1.14
XBV0 1.1.10
181 GB BarracudaST1181677FCV146-000001-00 Ciprico FC_0001 1.00.10
146 GB Cheetah 7ST3146707FC NXS3000SD146 146-000068-00Xyratex XV35 1.2.3

XV32 1.1.17
XV31 1.1.14
XBV0
Cheetah 6ST3146807FC 146-000053-00 Xyratex modepage1.1.17

obseleted by BU293 XV10 1.00.18
0006 1.00.18
146-000015-00 Ciprico 0006 1.00.26?

FC_F96F 1.00.11
73 GB Cheetah 7ST373207FC NXS3000SD73 146-000069-00Xyratex XV35 1.2.3

XV32 1.1.17
XV31 1.1.14
XBV0
DD-FC073 146-000069-00Ciprico XV31 1.1.16

PNLCIP001
DDFCREPLACEMENT146-000072-00Clariion
obseleted by BU296 PNLCLA001
Cheetah 6ST373307FC 146-000055-00 Xyratex modepage1.1.17

obseleted by BU293 XV10 1.00.18
0006 1.00.18
146-000048-00 (included sled) Ciprico 0006 1.00.26?

obseleted by BU308 FC_F96F 1.00.11
0004 1.00.11
DDFCREPLACEMENT146-000073-00Clariion XV10 1.1.14

PNLCLA001
Cheetah ST373405FC DD-FC073L Ciprico FC_0005 1.00.26?

0003

NEXIO
Cheetah ST173404FC DD-FC073 Ciprico 0005 1.00.26?

0002
Table: Array drive firmware (con’d)
Capacity Series Model Oracle # SubAssembyChassisFirmwareRaidToolsECOSA
50 GB BarracudaST150176FCDD-FC50 ClariionCL62
CL61
18 GB Cheetah ST318203FCDDFC-18 Clariion3943
BarracudaST118273FCDDFC-18 Clariion3525 (sw)

351B (hub)
9 GB BarracudaST19171FC DDFC-09 ClariionCDCB

CC97
CD09

NEXIO
Array Drive Modeset

• Array drives are not just passive devices that write and read data.
• Each has an intelligent controller that, for example, has the ability to re-read a sector if an error is
detected.
• Parameters affect, for example, how many times a re-read operation will be done.
• Modeset is the collective low level configuration of all of an array drive’s parameters.
• RaidTools allows the current configuration to be read or set to standard values.
• Array drives are not just passive devices that write and read data.
• Each has an intelligent controller that, for example, has the ability to re-read a sector if an error is
detected.
• Parameters affect, for example, how many times a re-read operation will be done.
• Modeset is the collective low level configuration of all of an array drive’s parameters.
• RaidTools allows the current configuration to be read or set to standard values.
RaidTools
It is a low level utility for media drives, used to:
• check/update firmware & low level configuration
• perform throughput tests
Note: When RaidTools is launched, it runs in read-only mode until logged in. In read-only mode,
potentially impactful operations are disabled. It is safe to capture current Modeset configuration settings,
and the fibre channel throughput with the array drives can be benchmarked.
Configuration – System Elements

NEXIO
Array Drive Modeset

To read the current mode set:
• Ensure that RaidTools is not logged in; Logout button should be greyed out.
To write the current mode set:

Login first then move all drives from Available Disks to Selected Disks using the >> button
Click Mode Set. Approve prompts to proceed, and enter a filename

NEXIO
Array Drive Modeset

When OK is clicked, a ripple across the array drive lights can be observed, and the Modeset configuration
data will be written to the file and displayed in Notepad
Note: That while the data in the file can be compared to known standards to determine if all drives are
appropriately configured, it is a tedious task, and is more prudent to simply write the modeset to all drives,
which will ensure all are set correctly.
To write the correct modeset values:

• Ensure that the latest version of RaidTools is installed
• Ensure that in the folder that RaidTools is launched from (c:\Leitch\Raidtools, or
c:\vr\Utilities\RaidTools), there is no “pattern.txt” file. If there is, rename to “pattern.old”
• Launch RaidTools, click Login, enter the password “warning”, OK
• Login button should now be greyed out
Read Array Drive Modeset

• Login button should now be greyed out
• Move all drives from Available Disks to Selected Disks using the >> button
• click Mode Set. Approve prompts to proceed, and enter a filename
• When OK is clicked, array drives will flash one at a time (more slowly than the read) as each drive
has its configuration re-written. The Modeset configuration data will be written to the file and
displayed in Notepad
• Be sure to Logout when done. Inappropriate actions while logged into Raidtools can result in the
complete loss of media (Exitting the application logs it out also).
• The output file from a write will indicate changes that were made, which may explain problems such
as Rebuild issues that may have existed before the corrections were made

NEXIO
Fibre Channel Switch Settings
Qlogic SANboxNXFS1622/822
Below are the port settings for the final ECO’s for the NXFS1622/822 switch. Earlier switches had less
onboard memory which will not accommodate the final firmware version 2.0.0.3
Parameter Settings
Firmware 1.3.56 Firmware 2.0.0.3
Factory Default
(BU167) (BU192)
VR Connections - all even # ports

PortType GL F F
TLPortMode TLTargetMode TLInitiatorMode N/A*
ALFairness FALSE FALSE FALSE
FANEnable TRUE TRUE TRUE
IOStreamGuard Disabled ENABLE ENABLE
DAE Connections - 3,5,7,9,11,13

PortType GL GL GL
TLPortMode TLTargetMode TLTargetMode N/A*
ALFairness FALSE TRUE FALSE
FANEnable TRUE TRUE FALSE
IOStreamGuard Disabled DISABLED DISABLED
ISL Connections - 0,15

PortType GL GL GL
TLPortMode TLTargetMode TLTargetMode N/A*
ALFairness FALSE FALSE FALSE
FANEnable TRUE TRUE TRUE
IOStreamGuard Disabled DISABLED DISABLED
Qlogic SANbox5600: NXFS1644
Configuration for this switch is described in
BU321_NXFS1644_SANbox5602
For systems that include both QLogic and ATTO fibre channel host adapter cards:
SA135 - Mixed ATTO and Qlogic on NXFS1644
SA155 new fibre switch configuration procedure

NEXIO
System Benchmarking
Configuration – System Elements
Ethernet
• The Ethernet is a critically important component in a Nexio System's health.
• Most importantly, it is the path through which synchronization of local Spotbase copies is maintained.
• By benchmarking Ethernet throughput capability, cabling issues and errors in configuration can be
identified and rectified.
• These tests should only be carried out when the system is not in use - i.e. no recording, playing back,
or editing taking place.
• If the network is bogged down sufficiently while in normal use (as these tests will likely do), system
problems may be caused.
• Two tests will be used to gauge overall performance
• The Ethernet is a critically important component in a Nexio System's health.
• Most importantly, it is the path through which synchronization of local Spotbase copies is maintained.
• By benchmarking Ethernet throughput capability, cabling issues and errors in configuration can be
identified and rectified.
• These tests should only be carried out when the system is not in use - i.e. no recording, playing back,
or editing taking place.
• If the network is bogged down sufficiently while in normal use (as these tests will likely do), system
problems may be caused.
• Two tests will be used to gauge overall performance
High Stress Ping Test

• While a standard ping command (ping ipaddress) verifies the existence of a TCP/IP communication
path between servers, it doesn't qualify the integrity of the link.
• The small packet size used in the standard command often allows good performance results (i.e. a
response with times < 10 ms) even across a seriously compromised network.
• The following command structure can be used to force a large message to be sent in one continuous
packet:

NEXIO

ping -l 64000 -t 192.168.90.x
• where x represents the node number of the destination being tested
• The -l switch (lowercase of the letter L) allows a packet size to be defined (in bytes). The default for a
standard ping is only 64 bytes
• the -t causes packets to be sent continuously, once per second
• NOTE: since the "-t” makes this a perpetual ping, “Ctrl+c” is required to terminate it.
• A typical result line is as follows:
• Reply from 192.168.90.2: bytes=64000 time<10ms TTL=128
• The value after "time" is the performance indicator
• Let the test repeat for at least one minute

• Record the number of “request timed out” messages observed (not counting the initial one), and the
typical “time=” value

NEXIO

• An overloaded or malfunctioning ethernet will likely be unable to process the large packets
• It would show readings significantly higher than the norm of less than 20 ms on a 100 Mbps Ethernet
switch system, often with an unusual amount of "request timed out" responses.
• Incorrect color coding resulting in a signal not being carried across a twisted pair will usually show in
this test. Ethernet cable testers may indicate such cables are fine because there is continuity on all
the pins, but high frequency data will exhibit problems, as this test reveals. Primarily, you should be
looking for nodes that under-perform the average and may contain a lot of "request timed out"
responses.
• Often Ethernet problems relate to the integrity of cable terminations inside connectors, and the
seating of cable connectors inside panel receptacles.
• For this reason, it is recommended that while the ping command is running, jostle the cable-to-panel
connections gently (but don't tug on them) to see if it affects the response.
• Do this at both the server connection point and the Ethernet hub/switch connection point while the
repeated ping commands are being sent.
• If "hiccups" seem to occur relating to these movements, replace the cable.
Large File Transfers

• The other important component of Ethernet testing is to transfer a large file across the Ethernet using
Network Neighborhood.
• Pick a file on the node 1 server in the 10 MByte or larger range. You can typically find one in the
server’s c:\install or d:\install folder tree.
• Pay attention to time as you initiate the copy. The transfer should take about 0.2 seconds per MByte
in systems using 100 Mbps network cards
• If a node passes the large packet ping test fine, but fails the large file transfer test, it is typically an
indication that there is an inconsistency in the duplex setting between the node’s card and the
Ethernet hub/switch.

NEXIO
Ethernet
LLM Record Ethernet test
• codec window XOR field
o rt <= 16 ms (NTSC); rt <= 20 ms (PAL)
o cc = 1 (occasional rise to 2 acceptable)
Manually start a record on the machine where the rt is being viewed.
Data Gathering Procedures
Snapshot
• This Harris utility has a number of handy embedded links to some Windows utilities, but primarily, it is
used to create a report on key server parameters – adapter card information, registry settings, file
versions, etc.
• “Save Report” generates a text file with this information.
Event Viewer
• Clues to server problems are often found in these operating system logs.
• Both the System log and Application log are of interest.
• Highlight on each one, and from the first menu, choose Export, select file of type “Tab-delimited”, then
OK.
• This file format pastes directly into an Excel spreadsheet to aid analysis.

NEXIO
Registry Export
• Regardless of the tool used to set configuration, settings are ultimately written to the Windows
Registry.
• Registry exports therefore will allow for confirmation of a large majority of settings.
• Always export with Save as Type set to “.reg”, as this is the common format, and provides a handy
mechanism for re-introducing edited changes (double-clicking .reg files writes their values back to the
registry).
Registration Procedures
Key Client
The KeyClient document describes the process for registering server hardware for use with a server for
all three CPU processor types found in NX4000, 420 and 440 server systems.
USB Hardware Security Key

The USB Hardware Security Key Installation and Upgrade Training describes how the security keys
(formerly called “dongles”) can be upgraded in the field to accommodate newly purchased option
software. The security dongle device was implemented in NX4200HDX and newer model numbers.
Software License Key

The software license key option was implemented in NEXIO software release 5.0.0 and higher.

NEXIO
Tech Guide Troubleshooting Software Problems

NEXIO
Troubleshooting Software
Problems
The initial steps to troubleshooting software problems on the NX3601 platform are as follows:
1. Close all Leitch applications currently running.

2. Start FXP via CMD prompt, by type C:VR>fxp
FXP works in conjunction with the LLM and must start successfully in order for the LLM to start.
If FXP fails to start when starting the LLM a “Com Server not found” message.
FXP Error Conditions:

Mapmem.sys not found. This is the most common error that users run into after configuring
or installing a system. This error can occur under the following circumstances:
• The MAPMEM.sys driver doesn’t exist under C:\Windows\System32\Drivers”.
• HKLM\...\Services\MapMem\Parameters key doesn’t exist.
• The Start and Stop values under …\Parameters is invalid or point to a non-existing
memory allocation block.
• The Mapmem.sys driver is not setup to start at boot time.
• In rare cases, installation of a language pack can cause this error to occur. However, we
can fix this problem by moving the responsible DLL to a different memory location.
FXPLOG.txt
FxpLog.txt is not automatically created and must be created manually in the same folder as
FXP.exe. If it exists, FXP will write all debugging information to it. The same information that
appears in the FXP screen when started via the CMD prompt will be written to FxpLog.txt.
When troubleshooting audio and video problems, it’s best practice to send a copy of FxpLog.txt
with a textual description of the problem to Leitch Server Division SQA/Engineering. Note: End
users in most circumstances should send problem reports to Customer Support and not directly
to Engineering.
LLM CODEC Window

The LLM codec window can be used to diagnose disk issues, buffer usage, and other critical
information. However, on the HD system, A/V I/O problems are logged in FxpLog.txt. This file
must be manually created in order to capture logging information output by FXP.exe.

NEXIO
MAPMEM.SYS
The mapmem.sys driver is installed under C:\Windows\System32\Drivers. In order for the
mapmem.sys driver to start successfully the following must be set:
Q: I have set mapmem settings but I still get mapmem.sys error in FXP.
A: It’s possible that some other application (DLL) is resident in the memory address range used
by mapmem.sys. To correct the problem, the DLL will need to be rebased to a different memory
base address using Rebase.exe.
Display Settings
The recommended display settings are 1024x768 32-bit true color. Higher resolutions can be
used if the monitor supports them as long as the bit-depth is not compromised.
Drivers for AGP Adapter can be found on the Nexio 3601HDX CD under: \Customer
Support\Driver backups\ Intel Ethernet Driver\IntelPRO1000MT Driver. Always use the latest
release CD.
Network Adapter Settings

Network adapter settings are critical to overall system performance and operation. There are
two network adapters on the NX3601 platform.
Nexio LAN - This is the first the Ethernet port and must be configured for the Nexio LAN. The
motherboard’s onboard Ethernet port is used for this purpose. The card must be configured to
compliment the attached Ethernet switch.
Set port to: Speed Link \ Duplex: 100Mbps \ 1000 Mbps FULL Auto negotiate
Registry Setting:
The LLM must be told which of the two Ethernet addresses it must use for intra-communication.
To achieve this, two registry settings must be changed:
IPAddress = <NexioLAN IP>
IPSubnetMask=<NexioLAN Subnet>
Transfer LAN - This is the second Ethernet port and must be configured for the Transfer
LAN. The Intel PCI NIC is used for this purpose. The card must be configured to complement
the attached Ethernet switch.
Set port to:

Speed Link \ Duplex: 1000Mbps\Full or Auto.
Note: Some switches may not allow 1000Mbps FULL, in this case set to Auto. The important
thing to remember is that an inappropriate setting will cause connection problems so it may be
necessary to try different duplex settings depending on the hardware at the other end.

NEXIO
General FAQ:
Q: I’m set to Input video as my reference source, what should I set

DsxGenlockResolution to?
A: You must set the DsxGenlockResolution to what ever the source input feed is. Example, of
the video input is 1080i, and then set DsxGenlockResolution to 1. If the source input feed is
720p, then set DsxGenlockResolution to 2.
Q: Can the HD server passthrough or play out AC3 audio?

A: No, however if the AC3 audio is stored in the LXF file that was created via an MTS, then the
AC3 audio is left as is and won’t be heard out of the HD server.
Q: What’s the sample size used in the HD Server, 8 bit or 10 bit?

A: 8 Bit.
Q: I attempted to transfer clips in both PAL mode and NTSC mode, but all
transfer ended up with that "Invalid format" error message.
A: This can occur if the clips that are to be transferred were created with a different LXF format.
For instance, clips recorded with a 605 level LLM cannot be transferred to 606 level LLM unless
a specific DTA mode is specified. Unfortunately transfer manager in NXOS does not yet support
changing the DTA mode.
This will no longer be a problem once the unified LLM architecture is complete and released.
The estimated time of release is to be determined.
Q: I tried using my USB jump drive for the first, but it’s not being
recognized. Why is this?
A: You have to insert the jump drive twice in order for Windows XP to properly recognize the
device and locate the appropriate driver. You should only need to do this the first time you use
the USB Jump Drive.
Q: How does the system drive interface with the motherboard?

A: Serial ATA.
Q: Does the NX3601 Server support MPEG-2 IBP in HD?

A: Yes, but decode only.
Q: Does the NX3601 support MPEG-2 IBP in SD?

A: Yes, encode and decode.

NEXIO
Q: What’s the maximum audio resolution supported?

A: 24 Bits @ 48 KHz.
Q: Can I do slow motion playback on the NX3601?

A: Yes.
Q: What are the supported HD resolutions and frame rates?

A: Supported Formats:
NTSC /ATSC 1080i – 59.94, 60 fps or 29.97, 30 Fps
NTSC / ATSC 720p – 29.97, 30 fps or 59.94, 60 Fps
PAL / DVB 1080i – 25 fps or 50 Fps
Q: Can a USB keyboard be used with NX3601?

A: Yes.
Q: I’m setting up an HDI system, what bus speed should I use for the SATA
drives?
A: 160. The first seven devices must be set for 160MB/s.
Q: Does the NX3601 support VBI in HD mode?

A: Yes.
Q: What type of memory does the NX3601 use?

A: 8GB DDR400 PC3200 Reg. CL3 ECC 184-Pins Dim
Q: Are 16x9 and 4x3 aspect ratios supported?

A: Yes.
Q: Can I connect an NX3601 and TXS to the same raid set?

A: Yes, although this requires our v.606 LLM or the new unified LLM. The raid set must also
have been initialized with either of these LLM’s or an NX4000 based LLM. The same
Network.dll version has to be installed on servers.
Q: Using our API how many frames does it take to load a clip into a VR
channel in a NX3601 server?
A: Variable, can be up to several seconds. Depends on system load, resolution of clip being
loaded etc.

NEXIO
Q: Once the clip is loaded how many frames does it take to execute the
play command?
A: 6 Frames
NX3601HDX I/O Specifications
Video Input Signals
Signal Type Qty Voltage Impedance

Reference In 1 1.0V p-p *
SDI/HD-SDI 1 Compliant with 75 ohm
SMPTE
259M/SMPTE 292M
* Requires an external 75 ohm termination on the reference loop output.
Video Output Signals
Signal Type Qty Voltage Impedance

Reference Loop 1 1.0V p-p 75 ohm
SDI/HD-SDI 2 Compliant with 75 ohm
SMPTE
259M/SMPTE 292M
Audio Input/Output Signals
Balanced AES-EBU (2 stereo input pairs)

Supports 16-bit, 20-bit and 24-bit audio streams
Input impedance 110 ohm
Nominal levels 7V p-p
Balanced AES-EBU (4 stereo output pairs)

Output impedance 110 ohm
Nominal levels 3.2V p-p
User Login
Q: What is the NXOS Admin password?
A: The password is “system”.

NEXIO
Q: What is the MS OS login for the Server?

A: The password is “VR300”.
Q: What is the LLM Properties login password?

A: The Password is “LEITCH”.
Powering Up Issues
Q: The Server is not powering up?
A: Check the back of the unit and ensure the power cables are plugged in.
Q: The PS Fault Led is red on the front of the panel, what do I need to
do? The Nexio Monitor is also indicating a Power Supply Error?
A: Check the back of the unit and see if there is a green LED on the Main and Stby power
supplies. If anyone of the power supplies don’t have an LED, check if it’s properly inserted.
Q: How do I find the log on window for the NXOS application, it just
sitting there stuck on Indexing ID?
A: The Login window is usually behind another application, so right click on the XP taskbar and
select cascade windows. Then select the Log On window and continue with the NXOS login.
Networking
Q: My Networking icon is showing ‘Not connected’?
A: Ensure the Ethernet cable is connected at the back on the unit. Ethernet Port 1 for the
NEXIO LAN, and Ethernet Port 2 for the FTP LAN. If problem persists, check the RJ45
connector is not faulty.

NEXIO
Q: My Networking icon is showing limited connectivity?

A: Double click on the Network Icon in the System Tray, click the Support tab and ensure you
have a valid IP Address. If you have a valid IP address, ensure you don’t have duplicate IP
address.
Q: My Networking Icon indicates there is duplicate IP’s?

A: Double click on the Network Icon in the System Tray. Under the ‘General Tab” click
Properties and double click on TCP/IP. The TCP/IP properties window will allow you to edit the
current IP address & Subnet mask of the unit.

NEXIO
Q: My Server keeps going into Play Only mode?
A: Check to ensure the NEXIO LAN Ethernet Port

is set to 100 Mbps Full Duplex.
Go to the Nexio LAN Properties window and select
configure for the Ethernet card, then select the
advance tab. Her you should be able to select Link
Speed & Duplex, to check and fix the
configuration.
If you are still encountering problems, check the

Ethernet switch that this server connects to and
confirm all the port are configured to 100 Mbps
Full Duplex.
Closed Captioning
Q: Closed Captioning is not passing through when ingesting and
playing out?
A: Ensure NXOS and the LLM application is closed. Run the “NEXIO Configuration Wizard”,
under the channel mode, select “I/O Routing”. On this screen you can select the VBI and Close
Captioning line. Use the start and stop line to indicate which lines will be captured and
processed during recording.
Once the lines are selected, complete the NEXIO Wizard, run Nexio Startup.
VBIStoredLines VBIStoredLines
VBIStartLine VBIStopLine
(Raw VBI) (RP202)
SDI Line 21
21 22 2 0
(legal minimum)
SDI Lines 17-21 17 22 10 0
720p HD Line 9 9 10 1 N/A

1080i HD Line 9 9 10 2 N/A
720p HD Lines 7-11 7 12 5 N/A

1080i HD Lines 7-11 7 12 10 N/A

NEXIO
Player E’E
Q: I am not getting the PlayerE’E confirmation on the signal being
recorded?
A: Close NXOS and the LLM, then launch the NEXIO Wizard, and under I/O Routing you have
the Record Channel Configuration, which allows you to select Player E’E. Note: In 3-Ch HD & 6-
Ch SD modes, there is no E-E capability all channels are either play-only or record only.
PlayerE’E invokes dynamic assignment of a play-only channel output for E-E services if that
channel currently has no ID loaded.
Window OS Clock
Q: My time code is not updating the Windows OS Clock?
A: Ensure the following registry (HKEY_CURRENT_USER\ Software\ ASC Audio Video\ LLM\
Control) setting TCReader is set to “COM1”, and you have physically connected the time code
source from the NXTX2110 unit to Com Port 1 of the server.
To access the registry go to Start Run and type ‘regedit’
Open the following tree path: HKEY_CURRENT_USER\ Software\ ASC Audio Video\ LLM\
Control. Ensure the variable TCReader = COM1.
If not double click on the TCReader and under “Value data” enter COM1 and click ‘OK’.

NEXIO
If time code still fails complete the following test;

• Launch HyperTerminal
• Select COM1
• Configure as follows: 9600 baud, 8 Data, No Parity, 1 Stop, no Flow Control
• Observe the appearance of HH:MM:SS time values every second
If time values are appearing here, then the problem is likely with the registry configuration. If
they are not appearing, then one of the following is suspect:
• the longitudinal time-code source
• cabling between the devices
Recording Capacity
Q: How do I check how many hours of record time I have left on my
server?
A; In the LLM, right mouse click on a logical disk and select properties, then select the General
tab, and you will see an overview of used and free recordable time.

NEXIO
Note: When you have fewer than 5% of recordable storage left you will consistently get a
warning message. Your raid needs to be cleaned to provide for additional recording. If the Free
Time reaches zero, no recording can be done.

NEXIO
Redundancy
Q: How many parity drives are required for redundancy?
A: The General rule is 2 to the power of ‘n’. Where n is the number of parity drives.
Total Drives in Logical Disk Parity Drives Required
1 -8 No C Parity
9 – 15 4
16 – 31 5
32 – 48 6
Replacement Drive Serial Number

Q: How do I go about identifying the serial number for a particular
drive to request a replacement?
A: In the LLM, right-
click the logical disk
and select properties.
Next, go to the
Information tab and
identify the drive
that’s giving you
read/write errors, right
mouse click the drive
and select
“Identification”. You
will get the Frame slot
details, physical drive,
the serial number &
amber light will
illuminate above the
drive.

NEXIO
Drive Replacement
Q: How do I go about doing a Drive Replacement?
A: Right-click the Logical Disk and select Properties. In the Security tab, key in the LLM
password “LEITCH” and click on Login.
Identifying Drive for Replacement

 The first critical step in a drive replacement is to ensure that the drive reporting errors is
the one that gets physically replaced. Replacing the wrong drive in this situation can
result in loss of media.
 Once the drive giving the errors is identified, right click and choose identification. Record
the “Physical Disk” number and also record the Serial Number displayed.
 Observe the front of the array. The indicator light for the drive in question should be
illuminated for as long as the Identification window is open.
Replacing Drive
 Now in the Information tab, right-click on the same drive and select Prepare Drive for
Removal. After a brief period, the drive in question should appear in the Physical Disks
pane.
 NOTE: Anytime the Physical Disks pane does not show the expected display, right-
clicking inside the Physical Disks pane and choosing Rescan may refresh the display
correctly.
 In the Information tab, the drive in question should now appear with a circle/slash
 Remove the failed drive from the array. After a brief period, the drive in the Physical
Disks pane should disappear.
 Obtain a known good drive to do the replacement with. Record the serial number of this
new drive.
 Insert the new drive, and allow it to spin up. The new drive should now appear in the
Physical Disks pane.
 Right-click on the circle/slash drive in the Information tab and choose Replace with new
drive, this will pop up a Select New Drive window containing all the drives in the Physical
Disks pane.
 Click OK to complete the logical replacement.
Rebuild
 The Logical Disk icon does not yet return to its normal grey icon, because although the
array is now physically whole, recordings that have taken place in the interim have not
been getting striped to the drive in question.
 To restore the missing data to the replaced drive, right-click on the logical disk, and
choose Start Rebuild. When the Rebuild is complete, the logical disk icon will return to
its normal indication.

NEXIO
NxSnapshot
Q: How do I complete a Snapshot?
A: First you need to launch the NXSnapShot program.
Go to StartProgramsLeitchUtilitiesNxSnapShot.
Once the program is launched, ensure everything is ticked under ‘Includes’, and then click
“Generate Report”. You will see a bunch of information appear in the Report Look window. Go
to File Save As and save the file to a text file.

NEXIO
Sense Code
Q: What is Sense Code of 0 [00] [00]?
A: Sense code of the type 0 [00] [00] occurs when communication is lost between the fiber
channel and the drive. This occurs due to the microprocessor on the drive has crashed or drive
array enclosure has bypassed the drive on the fiber channel.
For any drive in this state, the activity light will not be flash in tandem with the other drives in the
array.
Resolution: Pull the identified drive out about 2 inches to unseat it from the chassis, wait 30
seconds and reseat the drive. Wait another 30 seconds and confirm the drive has resumed
normal operation. If any record or play operations are occurring in progress on the system, the
newly re-instead drive should new be flashing in tandem with the other array drives.
Q: How do I identify the Sense Code I am getting for a particular

Drive?
A: Right-click the Logical Disk in the LLM and select Properties.
Inside Properties, Information tab, right-click on individual drive and choose Errors
• Errors for Physical Disk: The quantities here represent error totals from that individual array
drive as relates to this local server’s drive array usage:

NEXIO
Array Drive Status

Q: How can I check the status of all my drives in an Array?
A: Utilize the Error History Chart. Right mouse click the logical disk in the LLM and select Error
History.
• This chart shows read/write errors per individual physical drive. The chart is auto-scaling; full
bar may only represent 1 error!
• Errors shown here relate only to the activities of the local server. Servers that have not actively
accessed the array while the problem exists will therefore show no errors
SATA Mirror Raid Setup – NX3600HDX

Q: How do I setup the SATA Mirror Raid on a NX3600HDX SuperMicro
Server?
A:
1. During POST, press F10 when prompted to enter NVidia Raid Utility
2. Press left arrow to move Free Disk to Array Disk column
3. Press F7 to Finish
4. Select NO at the Clear Disk Data prompt.
5. Press B to set the array for BOOT
6. Press Enter
7. Press “R” to Rebuild
8. Arrow down to second disk (SECONDARY DRIVE – Adapt 1, Channel 1), press Enter
9. Press F7 to Finish
10. Press Enter to Rebuild
11. Press CTRL+X to exit
12. Reboot

NEXIO
Vertical & Horizontal Phase Adjustments – Genlock

Verification
Q: How do I adjust the Vertical and Horizontal Phase, plus verify
Genlock?
3801 & 3600/01HDX/I: Highlight the VR Channel, and then choose Channels, Video
Configuration
This tool verifies the presence of external reference, and allows you to adjust the video phase.
VTR Communication
Q: I can’t communication with a VTR and I have an AB3 RS422 back
plan?
A: Ensure you are using the “Master” DB9 to RJ12 adapter.
Then go to StartRun Regedit
Go to the follow path: HCUSoftwareASC Audio VideoLLMControl
Ensure Protocol6 & 7 = “SONY”.
Ensure Serial6 & 7 = “VTR”.
If not make the registry changes, and re-start the LLM and NXOS.
Then Login to NXOS as an administrator and go to fileSystem SetupVTR Tab.
Then select Com Port Number ‘7’ or ‘8’ to refer to the physical com port at the back of the server
you will connect the VTR. Also select the Digitize Channel.

NEXIO
Tech Guide Error ! N o te x t of s pe ci fie d s t yl e i n doc um e nt.


Nexio Server Core TG - MNT - 02 29 2012

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

Nexio Server Core TG - MNT - 02 29 2012

Uploaded by

Copyright:

Available Formats

NEXIO Server Core

Technical Training Guide

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

Copyright © 2012 Harris Corporation Release , February 29, 2012

UNITED STATES GOVERNMENT LEGEND If you are a United

CCS, CCS CoPilot, CCS Navigator, CCS Pilot, Command Control

Windows is a registered trademark of Microsoft Corporation. AMD

All other trademarks are the property of their respective holders.

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

Copyright © 2012 Harris Corporation Release , February 29, 2012

System Overview ............................................................................................................ 21

System Architecture ....................................................................................................... 57

Server System Components .......................................................................................... 65

System Spec .................................................................................................................. 119

NX3801 - Installation Quick Start ................................................................................. 141

NX3801 - Installation and Configuration ..................................................................... 143

NEXIO Config................................................................................................................. 149

LLM ................................................................................................................................. 237

Workflow ........................................................................................................................ 259

Assessing System Health ............................................................................................ 309

Issue Resolution ........................................................................................................... 345

Troubleshooting Software Problems .......................................................................... 377

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

• overview of the basic building blocks of a Harris server system

 The course focuses on the NX3801HDX, NX3801HDI, NX3601HDX, and NX3601HDI

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

1. Configuration settings for most Windows operating system functions:

2. A concise listing of a PC’s hardware:

3. Logs indicating key operating system occurrences and/or faults:

4. Two GUI-based approaches to viewing file system folders and files:

5. A grouping of applets/utilities relating to both hardware and software:

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

The NEXIO Video Server

LED LED Boot

USB Firewire SYS ID

Turn On – press and hold the button for 5 seconds to power on

Power Power On/ Reset

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

when using AES/EBU audio and

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

Front Server view:

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012

Back Server View

HARRIS CORPORATION | Broadcast Communications Division assuredcommunications®

Copyright © 2012 Harris Corporation Release , February 29, 2012