RN ReleaseNotes iDX20xx Combined RevI 042911 PDF

Release Notes
For iDX Releases:

2.0.0.3
2.0.0.4
2.0.1
2.0.1.1
2.0.1.2
2.0.1.3
2.0.1.4
2.0.1.5
2.0.1.6
April 29, 2011
Copyright 2011 VT iDirect, Inc. All rights reserved. Reproduction in whole or in part without permission is
prohibited. Information contained herein is subject to change without notice. The specifications and information
regarding the products in this document are subject to change without notice. All statements, information, and
recommendations in this document are believed to be accurate, but are presented without warranty of any kind,
express, or implied. Users must take full responsibility for their application of any products. Trademarks, brand
names and products mentioned in this document are the property of their respective owners. All such references
are used strictly in an editorial fashion with no intent to convey any affiliation with the name or the product's
rightful owner.
Document Name: RN_Release Notes_iDX 2.0.x.x_Combined_RevI_042911.pdf

Document Part Number: T0000287
ii
iDX 2.0.x.x Release Notes
Revision History
The following table shows all revisions for this document. Refer to this information to verify
that you have the latest version. If you do not have the latest version or you are unsure, you
can access the TAC web page at: http://tac.idirect.net and click on the Software Releases
link. You can then scroll down to the iDX release that is applicable to you and download the
latest version of this document.
Revision
Date Released
Reason for Change(s)
Who Updated?
04/22/10
First release of document for iDX

2.0.x releases; combines prior
Release Notes for iDX 2.0.0.3,
2.0.0.4, 2.0.1, 2.0.1.1 and
2.0.1.2.
TJenkins
06/23/10
Added known issue 22490.
EHoffman
07/30/10
TJenkins
08/25/10
EHoffman
Added bugs and installation
instructions for iDX 2.0.1.4 patch.
09/23/10
10/21/10

EHoffman
11/8/10
Added Known Issue 21944.
12/7/10

EHoffman
04/29/11
EHoffman
EHoffman
EHoffman
iii
iv
Contents
About This Guide

Purpose ..................................................................................... xiii
Intended Audience ....................................................................... xiii
Contents Of This Guide .................................................................. xiii
Document Conventions ................................................................... xiv
Related Documents ........................................................................ xv
Getting Help ................................................................................ xv
Important Notices
Optional iDX 2.0.1.6 Patch ................................................................ 1
iDX 2.0.1.4 Patch Obsoletes iDX 2.0.1.3 Patch ......................................................... 1


Upgrading e8350/e800 Remotes at Pre-iDX 1.1 Versions ........................... 2

Revision Server Not Supported for Patch Releases ................................... 3
Special Custom Keys for iDX 2.0.1 Upgrade ............................................ 3
Forward Compatibility for Evolution Remotes in DVB-S2 Networks Upgrading to
iDX 2.0.1 [20999, 21171] ................................................................................... 3
Forward Compatibility for Evolution Remotes (e800 / e850mp / e8350) on SCPC
Downstream Carriers [21001] .............................................................................. 4
Change to MIR and CIR Bandwidth Calculation [20486] .............................. 4
Modified Installation Script Behavior [20158] ......................................... 5

Remote Locking .............................................................................. 5
Root Password Now Tied To Admin Password ......................................... 6
PP Blades Balancing Behavior Change ................................................... 6
NMS and PP Servers Supported in iDX 2.0 .............................................. 6
Do Not Modify or Clone iBuilder Bench Test Components ........................... 6
False Reporting of CRC Errors for Unused Slots ....................................... 6
New Features
New Features and Enhancements in iDX 2.0.1.2 ..................................... 7
Tx 10MHz Will be Enabled After Modem Booting Up [21732] ......................................... 7
Add Beam Switch Module Debug Command [21722] .................................................... 7
New Features and Enhancements in iDX 2.0.1.1 ..................................... 7

Enable Co-Pol Operation on Orbit Antennas [21532] ................................................... 7
New Features and Enhancements in iDX 2.0.1 ........................................ 8

Remote Sleep Mode [21141] ............................................................................... 8
Improved Efficiency of DVB-S2 Carriers with Low Symbol Rates [20892] ........................... 8
Ability to Disable Beam Switching to Zero-Quality Beams [21395] .................................. 9
Supported Network Topologies ......................................................... 10

New Supported Hardware in iDX 2.0 .................................................. 10
XLC-11 Evolution Hub Line Card (HLC) .................................................................. 10
XLC-M Evolution Hub Line Card ........................................................................... 11
X5 Mid-Level Evolution Satellite Router ................................................................. 11
Existing Hardware Support .............................................................. 12

Evolution Hardware Sharing Same DVB-S2 Downstream .............................................. 12
iNFINITI Hardware .......................................................................................... 13
Hardware Not Supported ................................................................. 14

Features Not Supported .................................................................. 14
Supported System Modulation and Coding (MODCOD) .............................. 14
New Software Features in iDX 2.0 ..................................................... 15
Software Feature Licensing ...............................................................................
Sharing a 20-Slot Chassis in a Multi-NMS Environment ................................................
GQoS/ACM Enhancements [16546] .......................................................................
Nominal MODCOD Configuration ....................................................................
Remote Maximum MODCOD .........................................................................
Fixed Bandwidth (Default) Configuration .........................................................
vi
15
16
16
17
17
17
Enhanced Information Rate (EIR) Configuration ................................................. 17

Reporting of Operating MODCOD ................................................................... 17
Bandwidth Allocation Fairness Options ............................................................ 17
Allocation Fairness Relative to CIR ........................................................................ 18
Allocation Fairness Relative to MODCOD .................................................................. 18
Use of IP Data Rates in Configuring CIR/MaxIR ...................................................

Alternate Downstream Carrier ............................................................................
Global NMS Restrictions ..............................................................................
Satellite Router Recovery Stack ..........................................................................
Roaming Between Disparate Networks ..................................................................
Full Legacy Support ........................................................................................
18
18
18
19
19
19
System Enhancements in iDX 2.0 ....................................................... 20

GQoS for VNO Ownership Enhancement [12979] .......................................................
Dynamic Features and Options Exchange (DFOE) [19887] ............................................
Query Multicast Blade IP to pp_controller [19966] ....................................................
All BLD* Group Data Now Under VLAN Group [19971] .................................................
Warning Added When Changing SNR Limits [9147] ....................................................
VNO Enhancement for Revision Server [15085] ........................................................
Enhanced Control of VNO Visibility and Ownership ...................................................
Multicast Bandwidth Group Support in GQoS [16237] .................................................
Line Card Failover Enhancement [17659] ...............................................................
Increased GQoS Cost Precision [19314] .................................................................
ABS-Synchronizing Beam Information [19751] ..........................................................
Custom Key To Adjust Remote Time [20428] ..........................................................
20
20
20
20
20
21
21
21
21
21
21
22
Bug Fixes
Tracking of Issues Resolved in iDX 2.0.x.x Releases ............................... 24
Bugs Fixed in iDX 2.0.1.6 ................................................................ 29
Operation Affecting Issues ................................................................................ 29
23454 Number of Configured Beams Limited for ABS Remotes ...................................... 29
Bugs Fixed in iDX 2.0.1.5 ................................................................ 29

23030, 23477 Performance and Tuning Ability Enhancement ....................................... 29
Bugs Fixed in iDX 2.0.1.4 ................................................................ 29

Operation Affecting Issues ................................................................................
17458 Spoofer Handles Type 3 Keepalive Messages Inappropriately ...............................
22161 Frequent Link Layer Down/Up Timeouts (Link Layer Bouncing) .............................
22972 Evolution Remotes Take Excessive Time to Acquire In Network When Using
Spectral Inversion On Tx Side of Remote ...............................................................
29
29
29
30
vii
Bugs Fixed in iDX 2.0.1.3 ................................................................ 30

22106 Protocol Processor and Remotes Cannot Pass ICMP Packets With Invalid Checksum ..... 30
22184 SCPC Errors on iNFINITI Remotes When Using a Specific Combination of 8PSK
and Certain Frequency Range ............................................................................ 30
Bugs Fixed in iDX 2.0.1.2 ................................................................ 31

21704 Nonexistent Beams In Map File Not Treated As Zero Quality Beams .......................
21721 Round-Robin Order for Trying Beams Not Fair In Mapless Mode .............................
21843 net_state_timeout Custom Key Not Working Properly ........................................
31
31
31
31
Bugs Fixed in iDX 2.0.1.1 ................................................................ 32

NMS/Reporting Issues ......................................................................................
21533 OpenAMIP Protocol Not Sending F Command After Configuration Parameters .........
21534 OpenAMIP K Command Was Not Followed by F Command ..............................
21535 Add Support for a Second Parameter for Open-AMIP L Command .......................
21536 Keepalive Interval for Keepalives From Modem to Antenna Misbehaving ..................
21539 Upgrade of e8 Series Remote from pre-iDX 2.0 to iDX 2.0.1 Fails When Using iSite
or iBuilder ...................................................................................................
32
32
32
32
32
32
Bugs Fixed in iDX 2.0.1 ................................................................... 33

20847 QPSK TPC 0.793 Performance Issues .............................................................
20921 SS BPSK SF=1 TPC 0.66 and 0.533 Below SNR Performance Specifications ................
20986, 20898 CRC Errors If Frequency Hopping Between Evolution and iNFINITI Line
Cards ..........................................................................................................
21053 Crypto LED Does Not Light Up in TRANSEC Mode ..............................................
21116, 21319 Expanded Frequency Ranges for XLC-11 and XLC-M Line Cards ....................
21128, 21393 TCP File Transfer Failures ................................................................
21225 No Transmit Line Card Failover When Slot Is Powered Off ...................................
21307 Failed & Recovered PP Blade: Stabilization may take up to 15 minutes ...................
21316 Traffic Dropped If Any Remotes With OTA RIP Enabled Do Not Acquire Network ........
21397 Remote Maximum MODCOD Incorrectly Set After Network Upgrade .......................
21406 Possible XLC-M Line Card Freeze During Boot-Up .............................................
21428 Only First Application Profile is Recognized in an Application Group on Upstream ......
21436 DSCP Not Working in Earlier iDX 2.0 Releases ..................................................
21073 Ability to Delete Default Mesh, Default Multicast and NMS Multicast Profiles ............
21296 iBuilder: Mobile Remote Selection Allowed for Evolution X3 Remotes .....................
21273 iMonitor: http Traffic Counted Twice in IP Traffic Calculation .............................
21301 iMonitor: TDM Lost and SCPC Error Columns Switched in Network Data Snapshot .......
21320 iMonitor: Condition Snapshot Shows Incorrect Status for Deactivated Remotes ..........
21335 iMonitor Freezes Retrieving Latency Statistics for Large Networks .........................
21363 iMonitor: Some User-Defined Service Levels Do Not Appear in QoS Statistics ............
21394 dbBackup.ini and dbRestore.ini Not Saved by Upgrade Script ...............................
21396 iBuilder: iNFINITI 3100 Cannot Be Selected For 8PSK .79 Downstream Carrier ...........
21407 iMonitor Exits When User Resizes QoS Select Group Window .............................
viii
33
33
33
33
33
33
34
34
34
34
35
35
35
35
36
36
36
36
36
36
37
37
37
37
37
21410 iBuilder: VNO User Able to Apply Options Files and Reset Line Cards ...................... 38
21412 iBuilder: Multiple Changes to VNO Access Rights Forces Multiple Acknowledgments
by VNO Users ................................................................................................ 38
21481 iBuilder: Cannot Select iConnex e800 in TRANSEC Network ................................. 38
Bugs Fixed in iDX 2.0.0.4 ................................................................ 38

21183, 21375 Degraded RF Link Condition Caused Link Layer Instability .......................... 38
Bugs Fixed in iDX 2.0.0.3 ................................................................ 39

7743 Remote Advertising/Responding with RIPv2 while Deactivated ..............................
20120 Tx Power Rolloff at Extended L-Band Frequencies for e850mp Remotes ..................
20364 Multiband LNB Not Working for Orbit Marine Antenna Controller ...........................
20436 In ABS Mapless Mode Beam Info Not Updated In beam_state.opt File .....................
20533 Warm Line Card Failover of Rx Card Causes Tx LED to Glow on New Active Line
Card ...........................................................................................................
11422 iMonitorDisplay Issue Regarding True Configured Interface Speed on Remotes ........
11445 iMonitorChassis Warning Message Inconsistent ...............................................
12099 Remote Not Getting New Map File from Map Server ..........................................
13008 iBuilderCrashed Trying to Modify Group QoS Settings on Large Networks ...............
13292 iBuilderMulti-Edit Allows Encryption on Encryption-Incapable Remotes .................
13718 iBuilderLow C/N Warnings Not Varying By Configured Mode ..............................
14228 iBuilderApplication Profiles Reordered in Group View Not Reflected in Profile
View ..........................................................................................................
14301 iBuilderDeleted VLAN Entry Available for Remotes in Choose Details Window .........
14570 iBuilderMismatch in Limit Value Display of Certain Remote Warnings ................
14864 iMonitorDisable Condition in Active Conditions Tab in iMonitor Does Not Work ........
15337 para_cfg.opt File Not Created By NMS-configuration-client.pl Script ......................
15690 iBuilderLNB Voltage Field Omitted From Options File for Orbit Marine Antenna
Type ..........................................................................................................
16457 Activity Log Shows Failure When Applying Configuration to Protocol Processor .........
17476 iMonitorCNO Can View Other Remotes in QoS Statistics Windows ........................
19041 iMonitorTypical Line Card SNMP OID for Tx Bytes Reports Zero on XLC-10 ..............
19566 iBuilderLocked Database Warning Does Not Show VNO User Information ...............
19766 iBuilderCannot Turn Off Warning Messages If Low SNR Limit Values Matched ..........
19814 NRD Server Stops Processing Real Time Statistics After Making Network Changes
in Large Networks ..........................................................................................
19962 Opening Remote Modify Window Resulted in OS Password Change .........................
20083 iMonitorLabeling Error in FO/SO Graph of SATCOM Screen ................................
20494 Sky ServerDoes Not Start After Running the D-NMS Configuration Script ................
39
39
39
39
39
39
40
40
40
40
40
40
40
40
41
41
41
41
41
41
41
42
42
42
42
42
42
42
ix
Known Issues
Operation Affecting Issues ............................................................... 43
24844 Certain Filter and QoS Rule Combinations Not Classifying Packets Correctly .............
18783 Maximum Information Rate Not Enforced in Carrier Grooming Mode ......................
20149 COTM Frequency Tracking Algorithm Not Working Correctly ................................
21812 ICMP Header Processing Error on PP-VLAN Interface .........................................
21841 Queued UDP Traffic Causing Bandwidth Wastage .............................................
21944 iConnex-100 Remotes Cannot be Configured as Mobile Remotes ...........................
22490 Map-based ABS Remote with Serial NMEA Input Operating in Western Hemisphere
may Operate in Mapless Mode ............................................................................
43
43
44
44
44
45
45
NMS/Reporting Issues ..................................................................... 46

17912 SNMP Stops Sending Messages and Needs Restarting ..........................................
19932 NRD ServerRun-time Consolidation Versus get-last Queries .............................
19963 iMonitorHangs When Timeplan Window Left Open ..........................................
20148 iBuilderAll Remotes and Applications Disappear in ProfileApplication Mode
When New Application Added ............................................................................
20196 iMonitorPower Setup in Cross Polarization Portion of Probe Can Go Below
-40 dBm ......................................................................................................
21160 Config Server and Chassis Manager Lose Synch After Failing to Apply Configuration ....
21217 iBuilder: Cannot Assign LNB with 10Mhz Enabled to iConnex e800 Remote ...............
21274 iMonitor: Timeplan Graph Shows Allocated Slots in Free Slot Column .....................
21286 Revision Server Resets Remotes Repeatedly When Updating Large Number of
Remotes ......................................................................................................
21445 NMS Chassis Communications Problem Causes Alarms on Other Chassis ...................
21451 iBuilder Falsely Reports Failed to Assign Standby Error ...................................
22507 iBuilderFast Fade Configuration Changes Do Not Update Options File ...................
46
46
46
46
47
47
47
48
48
49
50
50
Installation Instructions
Installing iDX 2.0.1.6 Patch .............................................................. 51
Installing iDX 2.0.1.5 Patch .............................................................. 53
Verify Installation on Protocol Processor Blades ....................................................... 54
Installing iDX 2.0.1.4 Patch (Obsolete and Replaced by iDX 2.0.1.6) ........... 55
Installing sarmt Protocol Processor Patch .............................................................. 57
Verifying sarmt Patch Installation ....................................................................... 57
Verifying Patch Upgrade On Remotes ................................................................... 58
Installing iDX 2.0.0.3, 2.0.0.4, and 2.0.1 ............................................ 62
Modified Installation Script Behavior [20158] .......................................................... 62
Bench Test Components and Folders in iBuilder ....................................................... 62
Downloading Required Files for iDX 2.0.x .............................................................. 62
List of Tables
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
1. Pre-iDX 2.0 and iDX 2.0 Rate Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2. DVB-S2 OutBound MODCODs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3. iDirect SCPC OutBound MODCODs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4. iDirect SCPC Inbound MODCODs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5. Resolved Issues Tracking Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6. Cumulative Update and Remote Upgrade Packages for DX 2.0.1.6 . . . . . . . . . . . . . 51
7. Source and NMS Target Folders for iDX 2.0.1.6 Remote Packages . . . . . . . . . . . . . . 52
8. Cumulative Update and Remote Upgrade Packages for DX 2.0.1.4 . . . . . . . . . . . . . 55
9. Source and NMS Target Folders for iDX 2.0.1.4 Remote Packages . . . . . . . . . . . . . . 56
10. Cumulative Update and Remote Upgrade Packages for iDX 2.0.1.3 . . . . . . . . . . . . 58
11. Source and NMS Target Folders for iDX 2.0.1.3 Remote Packages . . . . . . . . . . . . . 59
12. Cumulative Update and Remote Upgrade Packages for iDX 2.0.1.2 . . . . . . . . . . . . 60
13. Source and NMS Target Folders for iDX 2.0.1.2 Remote Packages . . . . . . . . . . . . . 61
iDX 2.0.x Release Notes
xi
xii
iDX 2.0.x Release Notes
About This Guide
Purpose
These release notes are written to inform our customers of new features and resolved issues
incorporated into this release. Any outstanding issues that you may encounter in this release
are also described along with associated work-arounds, where applicable. This document
covers all iDX 2.0.x.x releases; specially, iDX 2.0.0.3, 2.0.0.4 and 2.0.1.x.
Intended Audience
The intended audience for this guide are network operators and network architects that work
with the iDirect network system.
Contents Of This Guide

This document contains the following sections:
Important Notices
New Features
Bug Fixes
Known Issues
xiii
About This Guide
Document Conventions
This section illustrates and describes standard conventions used in iDirect documentation.
Take a look now, before you begin using this manual, so that youll know how to interpret the
information presented. As you use this manual, refer to this section as needed.
Convention Description
Example
Blue
Courier
font
Used when the user is

required to enter a
command at a command
line prompt or in a console)
[SWITCH_PORT_n]
vid = vlan_id
Courier
font
Used when showing

resulting output from a
command that was entered
at a command line or on a
console.
Output similar to the following sample appears:

[SECURITY]
password =
$idi2$/bFMhf$5H8mYAaP1sTZ0m1Ny/dYyLaS40/
admin_password =
$idi2$146rgm$.KtDb4OH5CEBxzH6Ds2xM.ehHCH
os_password =
$1$UTKh0V$cc/UfNThFmBI7sT.zYptQ0
Bold
Trebuchet
font
Used when the user is

required to type
information or values into a
field within a windows-type
interface software.
1. If you are adding a remote to an inroute group,

right-click the Inroute Group and select Add Remote.
The Remote dialog box has a number of userselectable tabs across the top. The Information Tab is
visible when the Dialog opens.
Used when specifying

names of commands,
menus, folders, tabs,
dialogs, list boxes, and
options.
xiv
Blue
Trebuchet
font
Used to show all

hyperlinked text within a
document.
For instructions on adding an iSCPC line card to the

network tree and selecting a Hub RFT for the line card,
see Adding an iSCPC Line Card on page 108.
Bold italic
Trebuchet
font
Used to emphasize
information for the user,
such as in notes.
Note:
Red italic
Trebuchet
font
(or see
table
below)
Used when the user needs

to STRICTLY follow the
instructions or have
additional knowledge about
a procedure or action.
Several remote model types can be

configured as iSCPC remotes.
WARNING! The following procedure may cause

a network outage.
About This Guide
Symbol
Warning type
CAUTION
WARNING
Definition
CAUTION: When you see this alert

symbol and the CAUTION heading,
strictly follow the warning instructions
to avoid personal injury, equipment
damage, or loss of data.
WARNING! Electric shock hazard: When

you see this symbol and the WARNING
heading, strictly follow the warning
instructions to avoid electric shock
injury.
Related Documents
The following additional iDirect documents are available at http://tac.idirect.net and may
also contain information relevant to this release. Please refer to these documents as needed
or indicated within this guide.
Network Upgrade Procedure Guide for iDX 2.0.1.x
Software Installation Guide for iDX 2.x
iDX 2.0 iBuilder User Guide
iDX 2.0 iMonitor User Guide
iDX 2.0 Technical Reference Guide
iDX 2.0 Satellite Router Commissioning & Installation Guide
iDX 2.0 Features & Chassis Licensing Guide
iDX 2.0 Upgrade/New Installation Survey
iDX 2.0 Link Budget Analysis Guide
Note:
For details of hardware specifications supported in this release, please refer

to the iDirect web page at the following link:
http://www.idirect.net/Products/Hardware.aspx
Getting Help
The iDirect Technical Assistance Center (TAC) is available to help you 24x7x365. If you are
unable to find the answers or information that you need in these release notes, you can
contact the TAC at (703) 648-8151. You may also contact the TAC by email at tac@idirect.net.
iDirect strives to produce documentation that is technically accurate, easy to use, and helpful
to our customers. You feedback is welcomed! Send your comments to techpubs@idirect.net.
xv
About This Guide
xvi
Important Notices
This section presents important notices and procedures for implementing iDX 2.0.x.x releases.
Please read this information prior to installing the new release.
Optional iDX 2.0.1.6 Patch

This iDX 2.0.1.6 remote patch release corrects a defect found on ABS remotes running in iDX
2.0.1.x networks. Any remote-side bug fixes, enhancements and other code changes included
in previous iDX 2.0.1.x releases and patches are also included in this iDX 2.0.1.6 remote
patch. For more information and the complete procedure for applying this patch, see
Installing iDX 2.0.1.6 Patch on page 51.
Note:
This patch is not applicable to iNFINITI 3100 and Evolution X3 remotes.

This iDX 2.0.1.5 patch release consists of updated Protocol Processor blade sada and sarmt
executables. These two improved executables together help correct voice and fax
performance issues related to upstream jitter, and also provide the ability to fine tune certain
GQoS parameters as required. For more information and the complete procedure for applying
this patch, see Installing iDX 2.0.1.5 Patch on page 53.

iDX 2.0.1.4 is a remote-side and protocol processor patch release. This release can only be
used on remotes with an NMS hub operating at iDX 2.0.1. No other combination of releases has
been tested. If the fixes and enhancements included in iDX 2.0.1.4 are not applicable to your
network, it is NOT required to use this patch release. Instead, use the packages in the
iDX 2.0.1 release for your remotes. For the complete procedure for upgrading remotes to the
iDX 2.0.1.4 patch, see Installing iDX 2.0.1.4 Patch (Obsolete and Replaced by iDX 2.0.1.6) on
page 55.
iDX 2.0.1.4 Patch Obsoletes iDX 2.0.1.3 Patch

Since the iDX 2.0.1.4 patch includes all of the fixes and modifications contained in all
previous patches (iDX 2.0.1.1, iDX 2.0.1.2 and iDX 2.0.1.3), the iDX 2.0.1.4 patch obsoletes
the iDX 2.0.1.3 patch (and all previous patches). If you already have the iDX 2.0.1.3 patch on
Important Notices
your network, you can upgrade to iDX 2.0.1.4 using the same procedure described in Installing
iDX 2.0.1.4 Patch (Obsolete and Replaced by iDX 2.0.1.6) on page 55.

iDX 2.0.1.3 is a remote-side patch release, only. This release can only be used on remotes
with an NMS hub operating at iDX 2.0.1. No other combination of releases has been tested. If
the fixes and enhancements included in iDX 2.0.1.3 are not applicable to your network, it is
NOT required to use this patch release. Instead, use the packages in the iDX 2.0.1 release for
your remotes. For the complete procedure for upgrading remotes to the iDX 2.0.1.3 patch,
see Installing iDX 2.0.1.3 Patch (Obsolete and Replaced by iDX 2.0.1.6) on page 58.

Since the iDX 2.0.1.3 patch includes all of the fixes and modifications contained in the
iDX 2.0.1.2 patch, the iDX 2.0.1.3 patch obsoletes (and replaces) the iDX 2.0.1.2 patch. From
iDX 2.0.1, iDX 2.0.1.1 or iDX 2.0.1.2 you can upgrade directly to iDX 2.0.1.3. If you already
have the iDX 2.0.1.2 patch on your network, you can upgrade to iDX 2.0.1.3 using the same
procedure described in Installing iDX 2.0.1.3 Patch (Obsolete and Replaced by iDX 2.0.1.6) on
page 58.

iDX 2.0.1.2 is a remote-side patch release, only. This release can only be used on remotes
with an NMS hub operating at iDX 2.0.1. No other combination of releases has been tested. If
the fixes and enhancements included in iDX 2.0.1.2 are not applicable to your network, it is
NOT required to use this patch release. Instead, use the packages in the iDX 2.0.1 release for
your remotes. For the complete procedure for upgrading remotes to the iDX 2.0.1.2 patch,
see Installing iDX 2.0.1.2 Patch (Obsolete and Replaced by iDX 2.0.1.6) on page 60.

Since the iDX 2.0.1.2 patch includes all of the fixes and modifications contained in the
iDX 2.0.1.1 patch, the iDX 2.0.1.2 patch obsoletes (and replaces) the iDX 2.0.1.1 patch. From
iDX 2.0.1 or iDX 2.0.1.1, you can upgrade directly to iDX 2.0.1.2. If you already have the
iDX 2.0.1.1 patch on your network, you can upgrade to iDX 2.0.1.2 using the same procedure
described in Installing iDX 2.0.1.2 Patch (Obsolete and Replaced by iDX 2.0.1.6) on page 60.
Upgrading e8350/e800 Remotes at Pre-iDX 1.1 Versions

CAUTION: If you are upgrading e8350/e800 remotes currently at a pre-iDX 1.1 version
(i.e., iDS 8.2.2, iDS 8.3.1 and iDS 8.3.12.1), do not upgrade your remotes using the iDX
2.0.1 remote package. Install the iDX 2.0.1.2 remote package on your e8350/e800
remotes instead (using the same procedure described in Installing iDX 2.0.1.2 Patch
(Obsolete and Replaced by iDX 2.0.1.6) on page 60). If you are upgrading e8350/e800
remotes currently at version iDX 1.1 or above (i.e., iDX 1.1, iDX 2.0.0.3, iDX 2.0.0.4,
iDX 2.0.1, iDX 2.0.1.1 and iDX 2.0.1.2), then you can use the remote package files
provided with your release.
Important Notices
Revision Server Not Supported for Patch Releases

Since the NMS hub remains at iDX 2.0.1 after upgrading your remotes to iDX 2.0.1.1 or
iDX 2.0.1.2, the Revision Server feature can not be used to push these patch installations to
remotes in your networks. The Revision Server can only push remote software versions that
match the software version on the NMS.
Special Custom Keys for iDX 2.0.1 Upgrade

The custom keys in this section may be required for upgrading to iDX 2.0.1. Consult the
Network Upgrade Procedure Guide for iDX 2.0.x for complete instructions.
Forward Compatibility for Evolution Remotes in DVB-S2

Networks Upgrading to iDX 2.0.1 [20999, 21171]
To upgrade to earlier versions of iDX Release 2.0, custom keys had to be defined on all
Evolution X3 remotes receiving DVB-S2 carriers prior to the upgrade to ensure compatibility
with the DVB-S2 downstream format. These DVB-S2 remote custom keys are not required
when you upgrade to iDX 2.0.1 from earlier iDX releases.
However, to upgrade DVB-S2 networks to iDX 2.0.1, you must configure the
network_upgrade_mode custom key on all Tx line cards that transmit DVB-S2 carriers. In
addition, if you are upgrading from iDX 1.1, you must also configure the ncr_sof_offset
custom key on your DVB-S2 Tx line cards.
Define the network_upgrade_mode custom key on the Custom tab of your DVB-S2 Tx line
cards prior to the upgrade as follows:
[DVBS2]
network_upgrade_mode = <Value>
where <Value> is set to 1, 2 or 3 depending on which iDX Release you are upgrading from.
Configure the custom key value as follows:
network_upgrade_mode = 1 if you are upgrading from iDX Release 1.0.x
network_upgrade_mode = 2 if you are upgrading from iDX Release 1.1.x
network_upgrade_mode = 3 if you are upgrading from iDX Release 2.0.0.x
In addition to the network_upgrade_mode custom key, you must also define the
ncr_sof_offset custom key if you are upgrading from iDX 1.1.x. Only define this key if
network_upgrade_mode = 2. Add this custom key to the [DVBS2] group on your DVB-S2
transmit line cards as follows:
ncr_sof_offset = 0
Note:
The ncr_sof_offset custom key must be removed before adding Evolution X3 or

Evolution X5 remotes to the network.
iDX 1.0. networks only support Evolution X3 remotes. Therefore the upgrade only
considers X3 remotes.
iDX 1.1 networks only support Evolution e8350 remotes. Therefore the upgrade only
considers e8350 remotes.
Important Notices
iDX 2.0.0.x networks support Evolution X3, X5 and e8350 remotes. Therefore the upgrade
supports all types of remotes.
Note:
After all of the remotes in a network have been upgraded, you must delete
these custom keys from your Tx line cards. However, do not delete the custom
keys until you have verified that all remotes have upgraded successfully.
For complete details on upgrading your network, see the Network Upgrade Procedure Guide
for iDX 2.0.x.
Forward Compatibility for Evolution Remotes (e800 / e850mp /

e8350) on SCPC Downstream Carriers [21001]
This situation occurs with iDirect SCPC downstream mode only, and is caused by a change in
the naming of the downstream mode between these releases and iDX 2.0.x. To ensure
forward compatibility of the product_mode key during the upgrade DX 2.0.x, a custom key
must be added and applied to the remote side of each Evolution (e800/e850mp/e8350)
remote as shown below:
[OPTIONS_FILE]
product_mode=legacy
Note:
The Network Upgrade Procedure Guide for iDX 2.0.x contains instructions for
running a special script that automatically adds this custom key to your
Evolution (e800/e850mp/e8350) remotes.
Change to MIR and CIR Bandwidth Calculation [20486]

Prior to iDX 2.0, MIR and CIR settings for Group QoS nodes were based on Information Rate,
while MIR and CIR settings for physical remotes (as specified on the Remote QoS tab) were
based on IP Data Rate. Information Rate includes Layer 2 and TDMA (on the upstream)
overhead. On the other hand, IP Data Rate does not include the overhead. Therefore, there
was a difference between the configured MIR and CIR values compared to the actual IP data
rate, which was less than configured.
Beginning with iDX 2.0, all CIR and MIR throughout the system are based on IP Data Rate. This
change makes the configured MIR and CIR closer to the actual expected IP data rate, where
some discrepancy is expected depending on the IP packet size.
Important Notices
Table 1 shows the relationship between the pre-iDX 2.0 and iDX 2.0 (or later) MIR or CIR
configurations. For example, for FEC Rate .793, a configured CIR of 1000 kbps in a pre-iDX 2.0
release is equal to a configured CIR configuration of 902.455 kbps in iDX 2.0 or later.
Table 1. Pre-iDX 2.0 and iDX 2.0 Rate Reference
Pre- 2.0
MIR or CIR
FEC Rate
Equivalent 2.0 L2 and TDMA

MIR or CIR
Overhead
TPC-441/1024 (.431)
1000 kbps
676.457 kbps
32.35%
TPC-546/1024 (.533)
1000 kbps
718.280 kbps
28.17%
TPC-676/1024 (.66)
1000 kbps
752.046 kbps
24.80%
TPC-3249/4096 (.793)
1000 kbps
902.455 kbps
9.75%
Modified Installation Script Behavior [20158]

The installation script for this release no longer prompts the user to install either a primary or
a backup NMS. Instead, the operator must add either a -primary or -backup flag to the
installation script command when installing the software on a primary or backup NMS.
If the installation script is run without any option flags (no -primary or -backup flag
specified) the help text for the installation script command displays instead:
# ./install_nms_servers.pl
USAGE: install_nms_servers.pl [-h] -primary|-backup|-uninstall
-h
- Help, display this usage statement.
-primary
- Target machine will be configured as a primary NMS server.
-backup
- Target machine will be configured as a backup NMS server.
-uninstall
- Uninstall all iDirect NMS RPMS.
After displaying the help text above, the script execution terminates without installing any
software.
Note:
Refer to the Network Upgrade Procedure Guide for iDX 2.0.x for complete
details on how and where to use these new installation scripts.
Remote Locking
Remote locking feature support varies depending on the hardware. iNFINITI remotes support
old style remote Locking, while Evolution X3 remotes support enhanced Remote Locking. See
the iBuilder User Guide for iDX Release 2.0 for complete details.
Note:
The Remote Lock feature is not supported on Evolution X5 remotes.
Important Notices
Root Password Now Tied To Admin Password

In iDX 2.0 (and later), the root account passwords for remotes and line cards are tied to the
admin account. Changing the admin password on iBuilder also changes the root password on
hub line cards and remotes. Additionally, upgrading from any previous iDS/iDX version to iDX
2.0 updates the root password to reflect the iBuilder settings for the admin password.
PP Blades Balancing Behavior Change

PP Blades balancing behavior has changed in iDX 2.0. Now remotes are distributed across
multiple blades with configured multicast bandwidth, number of processes (sarmt, sada,
etc.), number of CPU cores, as well as number of remotes.
To rebalance the remotes across all PP Blades, you must now issue the following command at
the pp_controller console:
> blades rebalance all
NMS and PP Servers Supported in iDX 2.0

iDX 2.0 supports iDirect-provided IBM 335, 336, and x-3550 servers as well as Dell Power Edge
1950 servers. Although these servers function properly with iDX 2.0, the performance of the
servers depends on your network size and server load, as well as your network configuration.
Do Not Modify or Clone iBuilder Bench Test

Components
Do not modify or clone the Bench Test Spacecraft, Bench Test Inroute, or Bench Test
Outroute for your actual network configurations. These should only be used for testing
purposes. For your network configuration, please create new spacecraft, downstream, and
upstream carriers.
False Reporting of CRC Errors for Unused Slots

There is a possibility that you may see CRC errors reported for slots on your upstream carriers
in which no bursts were actually transmitted. This is caused by false burst detection due to
random noise in the idle slots. It occurs primarily in IF test networks or other networks with a
high number of idle bursts on the upstream carrier(s). These CRC errors due to false burst
detection are not a problem and should be ignored.
For details, see the FAQ How Do I Correlate Rx CRC Errors with Remote Modems? on the TAC
web page.
New Features
New Features and Enhancements in iDX 2.0.1.2

The features and enhancements in this section require iDX Release 2.0.1.2. They were not
included in earlier patches or releases of iDX 2.0.x.x.
Tx 10MHz Will be Enabled After Modem Booting Up [21732]

Remotes are designed to keep 10MHz disabled until Rx is locked and GPS information (in case
of a mobile remote) is available. Based on customer feedback, Tx 10MHz is enabled after
booting up only if the Options File has the Tx 10MHz option configured.
Add Beam Switch Module Debug Command [21722]

A newly created remote console command, beam debug 7, turns on the trace level of the
modem to display messages specific to the beam module only. This new command eliminates
unwanted response messages that were present in the generic tlev console command.
New Features and Enhancements in iDX 2.0.1.1

The features and enhancements in this section require iDX Release 2.0.1.1. They were not
included in earlier releases of iDX 2.0.x.x, but are now part of iDX 2.0.1.2.
Enable Co-Pol Operation on Orbit Antennas [21532]

iDirects Open Antenna-Modem Interface Protocol (OpenAMIP) is an ASCII message-based
protocol, a specification for the interchange of information between an antenna controller
and a satellite modem. It allows the modem to command the controller to seek a particular
satellite and allows the modem and controller to exchange information necessary to permit
the modem to initiate and maintain communications through the antenna and the satellite. In
iDX 2.0.x releases, OpenAMIP is implemented by setting fields in the iBuilder VSAT tab for a
remote.
Certain SeaTel and Orbit-marine antennas can now be commanded to select co-pol
operation rather than the more normal cross-pol operation. This feature allows you to
identify a particular beam as a co-pol beam in iBuilder on the remotes VSAT tab in the field
TX Polarization. To enable co-pol operation, select the same value (Horizontal or Vertical)
for both the Rx Polarization and Tx Polarization fields.
New Features
Note:
Do not select left-hand circular or right-hand circular operation for these

antennas. These are not currently supported.
For details on configuring mobile remotes and on using the VSAT tab, see the iBuilder User
Guide for iDX 2.0. For details on OpenAMIP, see the Open Antenna-Modem Interface Protocol
(Open-AMIP) Implementation Technical Note, available on the TAC web page
(http://tac.idirect.net).
New Features and Enhancements in iDX 2.0.1

The features and enhancements in this section require iDX Release 2.0.1. They were not
included in earlier releases of iDX 2.0.x.x.
Remote Sleep Mode [21141]

The Remote Sleep Mode feature is available in iDX Release 2.0.1 for all Evolution and iNFINITI
Remotes. The Sleep Mode feature conserves remote power consumption during periods of
network inactivity. When Sleep Mode is enabled on the iBuilder GUI for a remote, the remote
enters Sleep Mode after a configurable period elapses with no data to transmit. By default,
the remote exits Remote Sleep Mode whenever packets arrive on the local LAN for
transmission on the inbound carrier.
The stimulus for a remote to exit sleep mode is also configurable in iBuilder. You can select
which types of traffic automatically trigger wakeup on the remote by selecting or clearing a
check box for the any of the QoS service levels used by the remote. If no service levels are
configured to trigger wakeup on the remote, you can manually force the remote to exit sleep
mode by disabling sleep mode on the remote configuration screen.
For details on configuring Remote Sleep Mode, see the iBuilder User Guide for iDX Release
2.0. For a technical description of the Remote Sleep Mode feature, including power
consumption specifications for typical remote terminals, see the Technical Reference Guide
for iDX Release 2.0.
Note:
Remote Sleep Mode requires iDX Release 2.0.1. This feature is not available in
earlier iDX 2.0.x.x releases.
Improved Efficiency of DVB-S2 Carriers with Low Symbol Rates

[20892]
In iDX Release 2.0.1, iDirect has improved the efficiency of DVB-S2 carriers operating at low
symbol rates. In earlier releases, the Expected Information Rate of DVB-S2 carriers with
symbol rates above 5 Msps was 90% or better. Smaller carriers did not always achieve this
throughput because of management traffic, packet size, carrier size and minimum and
maximum MODCOD configuration.
In iDX Release 2.0.1, the DVB-S2 algorithm has been improved to allow all DVB-S2 carriers,
including those with symbol rates between 1 Msps and 5 Msps, to achieve Expected
Information Rates of 90% or better.
New Features
Ability to Disable Beam Switching to Zero-Quality Beams

[21395]
iDirects Automatic Beam Selection (ABS) feature allows mobile remotes to automatically
switch between satellite beams based on the geographic location of the remote modem. The
remote modem reads the current location from the antennas GPS and decides which
available beam will provide optimal performance for that location based on the map server
information received from the hub. The beam map file is a large data file containing beam
quality information for each point on the earth's surface. Sections of the beam map file
(maplets) that include the remotes current location are sent to the remote by the NMS.
Based on the quality information in the beam map file, the remote attempts to join the best
available beam.
In earlier releases, a remote modem would always attempt to join any beam included in the
beam map file if that beam was deemed to be the best choice available. This included beams
with a quality value of zero for the remotes current location.
Beginning with iDX 2.0.1, you can configure your remotes so that they never attempt to join a
beam if the quality of the beam at the current location is zero. To enable this feature, you
must configure the following remote-side custom key on the Remote Custom tab in iBuilder:
[BEAMS]
beam_unuse_zero = <Value>
Where:
<Value> = 0 means use zero-quality beams
<Value> = 1 means do not use zero-quality beams.
WARNING! You must apply this custom keys to all instances of your remote.
The example in Figure 1 turns on this feature for a remote. Once the configuration is saved
and the remote-side changes are applied, the remote will no longer attempt to join beams
with a quality value of zero.
Figure 1. Disabling Beam Switching to Zero-Quality Beams

For more information about ABS, see the Technical Reference Guide for iDX Release 2.0 and
the iBuilder User Guide for iDX Release 2.0.
New Features
Supported Network Topologies

The following network topologies are supported in iDX 2.0.0.3:
DVB-S2 star networks
iNFINITI star networks
The following network topologies are not supported:
iNFINITI iSCPC networks
iNFINITI star/mesh networks
New Supported Hardware in iDX 2.0

iDX 2.0 supports the new hardware described in this section.
XLC-11 Evolution Hub Line Card (HLC)
10
The XLC-11 Evolution HLC has 1 modulator and 1 demodulator.
The XLC-11 HLC is configurable to support either an iDirect SCPC or a DVB-S2 outbound.
The XLC-11 HLC is configurable to support a TDMA inbound.
The XLC-11 HLC occupies a single slot in and is fully compatible with the following
chassis:
- 20 slot 1IF
- 20 slot 5IF
- 4 slot
- 4 slot Industrial
The XLC-11 HLC supports the following optional license-enabled features:

- Spread Spectrum (iDirect SCPC outbound)* (SF 2, 4, or 8)
- Spread Spectrum (Inbound) (SF 1, 2, 4, 8, 16)
[Only the eM1D1 and XLC-11 line cards support Spread Spectrum with a TDMA inbound.]
[The e8350 is the only Evolution remote capable of receiving a spread iDirect SCPC
outBound carrier.]
New Features
Standard XLC-11 Functionality

Function
Description/Notes
2D 16-State coding in the Inbound 2D 16-State is available on DVB-S2 networks using

XLC-M, eM1D1 or XLC-11 as Rx line cards.
Operating temperature and
humidity ranges
0 to 45 C Non-Condensing
Hot-swappable
[assuming no II+ HLCs in chassis]
Fully supports software-controlled n:m auto-failover

redundancy.
XLC-M Evolution Hub Line Card

This is a new receive only Evolution line card. This has the capability of supporting multiple
return channels (future). This line card is the new multi-demodulator hub line card, however,
for iDX 2.0, the number of demodulators is one (M=1).
Standard XLC-M Functionality

Function
Description/Notes
TDMA inbound channel
For iDX 2.0, the XLC-M only supports a single TDMA inbound
channel.
Multiple SCPC or multiple TDMA

software demodulators
Hardware-ready to support multiple SCPC or multiple TDMA

demodulators in future. For this release (for TDMA return
channel only), the number of supported demodulators ("M") is
1.
2D 16-State support
For iDX 2.0.0.3, the XLC-M supports 2D 16-State.
X5 Mid-Level Evolution Satellite Router

The Evolution X5 is a new satellite router featuring dual capabilities of receiving either DVBS2/ACM or SCPC on the outbound. The X5 is designed to support business-critical, broadband
applications such as enterprise connectivity, cellular backhaul, maritime and other mobile
applications.
Standard X5 Functionality
Function
Description/Notes
Operational modes
iDirect SCPC or DVB-S2 outbound mode (can switch between

modes in the same release).
TDMA
TDMA Star mode of operation
GNMS and ABS
Full support for G-NMS and ABS, including serial port for GPS
input
VoIP
Support for at least 25 concurrent VoIP calls.
Processor
Fastest processor (533) in the Intel X-Scale processor family
11
New Features
Function
Description/Notes
Memory
32MB of flash memory, 128MB of memory
Minimum Symbol Rate
128 ksps
Remote Lock
not supported
Optional X5 Features (enabled through software license)

Function
Description/Notes
Spread Spectrum
On the Inbound (SF 1, 2, 4, 8, 16)
Encryption
256 bit AES Link Encryption
Note:
Any Evolution remote in a DVB-S2 network that is running iDX 2.0.x.x supports
2D 16-State encoding on the inbound (when used with an Evolution Rx line
card).
Existing Hardware Support

For all existing Evolution hardware, support is defined as full functionality of all features
included in the most current iDX software release that supports that hardware.
The following existing Evolution hardware is supported in this release:
XLC-10
eM1D1 line cards
X3 remote
e8350 remote
e800 iConnex board
e850mp Maximum Portability iConnex board
Note:
The XLC-10 line card currently supports ONLY a DVB-S2 outbound, and this does
not change in iDX 2.0. The XLC-10 does not support an iNFINITI outbound in iDX
2.0.
Evolution Hardware Sharing Same DVB-S2 Downstream

iDX 2.0 allows the following remotes to share the same DVB-S2 downstream:
12
e8350 (and all its iConnex variants)
X5
X3
New Features
iNFINITI Hardware
The following iNFINITI hardware is supported in this release:
iNFINITI 3100 Satellite Router
iNFINITI 3100-NB Satellite Router
iNFINITI 5300 Satellite Router (Star mode only)
iConnex 100 Satellite Router
M1D1 Hub Line Card
M0D1 Hub Line Card
M0D1-NB Hub Line Card
M1D1-T Hub Line Card
M1D1-TSS Hub Line Card
M1D1-IND Industrial Hub Line Card
M1D1-T-IND Industrial Hub Line Card w/ TRANSEC
15052 - 5 IF 20 Slot TDMA Hub with GigE
15050 - 5 IF 20 Slot TDMA Hub
10100 Private Hub
10300 Private Hub
10300-48 Private Hub
10115 Mini Hub
10115-48 Mini Hub
10130 Mini Hub
12102 4 IF 4 Slot TDMA Hub
12202 4 IF 4 Slot Industrial TDMA Hub
SkyMonitor 1880
13
New Features
Hardware Not Supported
NetModem II+ Satellite Router
NetModem II Satellite Router
NetModem II Hub Line Card
iSCPC chassis and iSCPC Line cards
Features Not Supported

The following features are not supported in this iDX 2.0 release:
External Device Monitoring
iSCPC (NMS Managed)
Mesh Topology
Downstream (SCPC) BPSK 0.431
The following features have not been supported since iDS 8.x, and are now completely
removed from the iVantage iBuilder software interface:
Downstream (SCPC) QPSK 0.431
Upstream (TDMA) QPSK 0.431
Upstream (TDMA) 8PSK 0.793 (except Evolution)
Supported System Modulation and Coding (MODCOD)

System MODCOD requirements as first defined in iDX 1.1, are fully supported and tested in iDX
2.0. The DVB-S2 outbound carrier utilizes the following modulation and coding combinations:
Table 2. DVB-S2 OutBound MODCODs
Downstream
DVB-S2: QPSK
MODCOD
DVB-S2: 8PSK
DVB-S2
DVB-S2: 16APSK
The iDirect SCPC outbound is capable of utilizing the following modulation and coding
combinations:
Table 3. iDirect SCPC OutBound MODCODs
Downstream
BPSK/SS .495 .793 .879 (SF 2/4/8)
MODCOD
BPSK .495 .533 .793 .879
(SCPC)
QPSK .495 .533 .793 .879

8PSK .793 .879
14
New Features
CAUTION: The BPSK-0.431 (BPSK with FEC of 0.431) downstream carrier configuration
is not supported in iDX 2.0. If you are using BPSK-0.431 you must change the carrier
prior to upgrading. Additionally, the Downstream (SCPC) BPSK 0.431 configuration is no
longer supported.
The D-TDMA inbound carrier supports spread spectrum with spreading factors of 1, 2, 4, 8 and
16. Spread Spectrum on the inbound is available regardless of the type of outbound in use.
Spreading factors of 8 and 16 on the inbound require Evolution hardware.
Outbound carriers support spread spectrum with spreading factors of 1, 2, 4 and 8. A
spreading factor of 8 on the outbound requires Evolution hardware.
The D-TDMA inbound carrier supports the following MODCODs:
Table 4. iDirect SCPC Inbound MODCODs
Upstream TDMA
BPSK/SS .431 .533 .66
MOD/CODS
BPSK .431 .533 .66 .793
TPC
QPSK .533 .66 .793

8PSK .66 (& .793 Evolution only)
Upstream TDMA
SS 1K Block 2/3, 3/4, 4/5
MOD/CODS
BPSK 1K Block 2/3, 3/4, 4/5
2D 16
QPSK 1K Block 2/3, 3/4, 4/5

8PSK 2K Block 2/3, 3/4, 4/5
New Software Features in iDX 2.0

The following topics detail new functionality in the iDX 2.0 software. For complete
information on all features discussed, please refer to the following guides:
iDX 2.0 iBuilder User Guide
iDX 2.0 iMonitor User Guide
iDX 2.0 Technical Reference Guide
iDX 2.0 Satellite Router Commissioning & Installation Guide
iDX 2.0 Features & Chassis Licensing Guide
Software Feature Licensing

Beginning with the release of iDX 2.0, iDirect is introducing a new method for licensing its
products. After installing or upgrading to iDX 2.0, certain software features can now be
licensed for specific pieces of hardware (line cards and remotes). And, you can now license
slot timing groups in your hub chassis. Because of the new slot group licensing, licenses are
now required to operate a hub chassis that is on iDX 2.0.
Please see the iDX 2.0 Features & Chassis Licensing Guide for complete details.
The following system features are disabled by default, but can be enabled through the
purchased of a license key:
15
New Features
AES link encryption on the X3 or X5 remotes
Spread Spectrum on the Inbound on the X5 remote
Spread Spectrum on the Inbound on XLC-11 HLC (enabled by default on eM1D1)

Note: The license to enable Spread Spectrum on the XLC-11 is included in the
selling price for the line card, although this feature will not function without
first generating and loading an active license.
Spread Spectrum on the iDirect SCPC outbound on XLC-11 HLC.
License-Controlled 5IF Timing Groups.
The above licenses are loaded through iBuilder. No licenses are loaded through iSite.
Notes:
All NMS options that are currently enabled with a license key in the NMS license file
remain unchanged.
TRANSEC (iDirect SCPC, outbound only), and Spread Spectrum (except on DVB-S2
outbound) are standard features on the eM1D1 HLC.
TRANSEC is only available on the eM1D1 HLC or the M1D1-TSS HLC.
Sharing a 20-Slot Chassis in a Multi-NMS Environment

iDX 2.0 adds the capability to configure multiple Network Management Systems to share a
single physical hub chassis. For example, a hub operator may want to allow a VNO customer
with his own NMS to configure or control specific slots in a hub chassis.
For complete information on configuring this capability in iBuilder, refer to Section 8.5,
Sharing a 20 Slot Chassis in a Multi-NMS System, in the iBuilder User Guide for iDX Release
2.0. For further licensing information as it relates to sharing a chassis, also refer to Section
3.2, Using Chassis Manager in Multi-NMS Configurations, in the iDX 2.0 Features and Chassis
Licensing Guide.
GQoS/ACM Enhancements [16546]

New GQoS/ACM features supported in this release include configuring a Nominal MODCOD or
Reference Operating Point per remote on which service pricing can be based, and the option
of extending the CIR during rain fade.
The following additional system options related to bandwidth allocation fairness have also
been added:
16
Clear Sky or Reference Operating Point per remote
Scaling based on fixed bandwidth relative to Clear Sky
CIR Fairness (in Fixed BW mode, EIR Mode and with other Remote CIR)
Configuration enhancements at Carrier, Bandwidth Group and Service Group levels
Additional statistics and reporting capabilities for EIR mode
New Features
Nominal MODCOD Configuration

The remote terminal configuration now includes the selection of a Nominal MODCOD, also
known as a Reference Operating Point (ROP) for the remote. iBuilder now includes a dropdown box where operators can select one of the available MODCODs for the network. The NMS
defaults the selection to the network's best MODCOD.
In a fixed network environment, the Nominal MODCOD is typically chosen to be the

ClearSky MODCOD. In a maritime network where the ClearSky MODCOD depends on the
position of the ship, the Nominal MODCOD can be any point in the beam coverage at
which the service provider chooses to guarantee the CIR.
The CIR/MaxIR configurations are now based on the configured Nominal MODCOD, which is
typically the ClearSky operating point for fixed networks. The Nominal MODCOD is
typically determined based on the link budget but can be adjusted after the remote is
operational. Service Provider pricing is based on expected ClearSky MODCOD and
corresponding satellite bandwidth usage.
The CIR/MaxIR is now limited to the remote's configured Nominal MODCOD. The remote is
allowed to operate at MODCODs higher than the Nominal MODCOD, but can not be
rewarded with a higher CIR/MaxIR if and when it operates above the contracted Nominal
MODCOD. The Service Provider still benefits from the savings in bandwidth while
complying with the Service Level Agreement (SLA).
Remote Maximum MODCOD

By default, the Remote Max MODCOD is now the same as the Network's Best MODCOD. The
NMS allows the operator to limit the Max MODCOD for a remote to a value lower than the
Network's Best MODCOD and higher or equal to the Remote Nominal MODCOD. The remote is
allowed to operate above its configured Nominal MODCOD as long as it does not exceed the
Remote Max MODCOD which can be restricted by the type of LNB used by that remote.
Fixed Bandwidth (Default) Configuration

The CIR/MaxIR is now scaled down during rain fade based on the Remote's configured Nominal
MODCOD. This provides a graceful degradation in CIR/MaxIR during rain fade while consuming
the same satellite bandwidth as at the Nominal MODCOD.
Enhanced Information Rate (EIR) Configuration

The Enhanced Information Rate (EIR) option, also known as Rain Fade Insurance, is now
offered as an option to maintain CIR/MaxIR during rain fade for the physical remote (RemoteBased GQoS Tree) or critical applications (Application-Based GQoS Tree).
Reporting of Operating MODCOD

iMonitor now provides statistics on the operating point of each remote. These statistics can
aid the Service Provider in determining the percentage of time a remote is operating at its
configured Nominal MODCOD, and other MODCODs. This parameter is particularly important
when the EIR option is selected because it allows the Service Provider to determine the
potential additional bandwidth cost of each remote that has purchased the EIR option.
Bandwidth Allocation Fairness Options

iDX 2.0 provides operators with GQoS configuration options that allow selection of the
bandwidth allocation fairness scheme that is most appropriate to the operators business
model. The following two options can be enabled or disabled:
17
New Features
Allocation Fairness relative to CIR
Allocation Fairness relative to MODCOD
Either of these options can be selected independently of the other and applied to an entire
Service Group.
Allocation Fairness Relative to CIR

This option allows the CIR/MaxIR allocation to be proportional to the configured CIR during
contention conditions. The NMS computes an internal "hidden cost" parameter that is used by
the Demand Allocation (DA) algorithm to implement the proportional allocation behavior.
Allocation Fairness Relative to MODCOD

This option allows for a choice of fairness in allocation relative to MODCODs during contention
based on satellite bandwidth or CIR. This option is typically used by Service Providers selling
service based on a CIR and Nominal MODCOD with a pricing model of higher rates for remotes
operating at lower MODCODs.
Use of IP Data Rates in Configuring CIR/MaxIR

Previous inconsistencies introduced confusion for network operators when planning bandwidth
allocation have been eliminated in iDX 2.0. The system now interprets all CIR/MaxIR entered
in iBuilder as IP Data Rates. This applies to physical remote configuration as well as any
CIR/MaxIR at any level in the GQoS tree.
Alternate Downstream Carrier

iDX 2.0 enables a user to define an Alternate Downstream Carrier in iBuilder. This
configuration needs to include all elements of a downstream configuration (center freq,
symbol rate, FEC, etc.). Analogous to beam-switching, a remote attempts to acquire the
downstream using the primary configuration, and if unsuccessful tries the alternate
configuration after a fixed number of minutes.
The Alternate Downstream Carrier is stored in the configuration database. If configured, the
Alternate Downstream Carrier shows up in the Options file as a new group, using the existing
consolidated Options file format.
Global NMS Restrictions

The Alternate Downstream feature is not compatible with Global NMS (GNMS). If operators
have a Global NMS license, the Alternate Downstream feature is disabled. However, when
operators have an Alternate Downstream configured and they change their license from
regular NMS to Global NMS, the previously configured Alternate Downstream does not get
cleared automatically.
CAUTION: Although an Alternate Downstream Carrier on a remote can be removed

manually, if a remote with an Alternate Downstream configured was out of network, it
can still look for this (now) non-existing carrier when it rejoins the network.
18
New Features
Satellite Router Recovery Stack

With this release, a recovery stack is employed on all iNFINITI and Evolution remotes running
iDX 2.0 software. This stack reduces the chances of configuration errors which can force the
remote into an error stack condition, which previously required on-site visits to correct. When
a remote goes into recovery stack due to situations like Options file error, the remote is able
to maintain downstream lock, which allows the hub operator to push updated configurations
and packages from the hub.
The following problems are addressed (on a best attempt basis) by the Recovery Stack
feature:
Older software images with Options file generated by a newer NMS (iDX 2.0 or higher).
Newer software images (iDX 2.x) with a mismatching version of the Options file.
Invalid Options file settings, which could happen even with matching versions of software
and Options files.
Bugs in software/firmware causing a run-time crash.
Roaming Between Disparate Networks

The X5 and the e8350 (including all Evolution iConnex variants) are now capable of roaming
between disparate networks when operating in the Global NMS environment. This capability
includes roaming between networks using iDirect SCPC outbounds and DVB-S2 outbounds, and
is configurable through iBuilder. The ability to roam between disparate networks is supported
by the X5, the e8350 and all future remotes that are capable of receiving iDirect SCPC and
DVB-S2 outbounds. This feature builds towards the ability of a HNO to operate a single GNMS
that is controlling multiple Protocol Processors and line cards in multiple hubs belonging to
multiple network operators.
Full Legacy Support

Legacy outbound, including the complete iNFINITI outbound feature set, is supported by iDX
2.0. iDX 2.0 is fully compatible with iNFINITI hub line cards such as M1D1, M0D1, M0D1-NB,
M1D1-T and M1D1-TSS, and all series of iNFINITI remotes.
This support for legacy iNFINITI products includes iDX 2.0 support for all existing Turbo
Product Codes used by iNFINITI products. Existing iNFINITI customers can upgrade to iDX 2.0
and use their existing iNFINITI hardware without the need for adding any additional Evolution
hardware.
The iDirect SCPC outbound, including the complete iNFINITI outbound feature set, is
supported on the following Evolution products:
XLC-11 Hub Line Card
eM1D1 Hub Line Card
e8350 remote
e800 iConnex board
e850mp Maximum Portability iConnex board
X5 Remote
19
New Features
System Enhancements in iDX 2.0

iDX 2.0 contains the following specific system enhancements detailed in this section.
GQoS for VNO Ownership Enhancement [12979]

In previous releases, when assigning ownership for a Service Group to a VNO, or assigning
Write permissions to a Network or Inroute Group level, VNOs were allowed to select the
following options under Group View and Profile View:
Insert
Clone
Now, VNOs cannot Clone or Insert when there are not enough privileges under the parent
object. (For example, when the parent Bandwidth Group only has visible permissions.)
Dynamic Features and Options Exchange (DFOE) [19887]

With the DFOE (Dynamic Features and Options Exchange) protocol, some configuration
changes can now be dynamically applied without resetting the remote. For a given remote, all
options beginning with RMT_ are sent from the Protocol Processor to the remote using the
DFOE protocol. Using this new feature, many of the options/features can be enabled/disabled
for a remote on the fly, without the need to push an Options file to the remote.
Query Multicast Blade IP to pp_controller [19966]

A new command has been added to the Protocol Processor command console to return the IP
address of the blade holding the multicast flag and the corresponding network ID. The new
command is as follows:
> blade query multicast
The output of this command displays the multicast IP address of the blade that forwards the
multicast.
All BLD* Group Data Now Under VLAN Group [19971]

In previous releases the per-VLAN custom keys for RIP In the global.opt file (such as
rip_enabled, rip_redistribute_static and rip_redistribute_connected) were
dispersed under the [BLD_id_VLAN_vid] groups, meaning they needed to be added for
every Protocol Processor blade.
With iDX 2.0, all RIP options are now added just once under the [VLAN_*] group in the
global.opt file.
Warning Added When Changing SNR Limits [9147]

Warnings are now generated in iMonitor under the remote Conditions tab if an unsupported
value for the Upstream/Downstream SNR field is specified after clicking Edit Low SNR Limit
in a row of the Edit>Global Warming for remotes window. These warnings display the new
(below the threshold) limit the operator is attempting to set.
20
New Features
VNO Enhancement for Revision Server [15085]

HNOs can now grant the use of the Revision Server to individual VNOs. Any given VNO using
the Revision Server can now be limited to the management of cumulative packages, software
images and Options files of remotes owned by that VNO.
Enhanced Control of VNO Visibility and Ownership

An HNO can now define visibility and ownership for the following components on a per-VNO
basis:
Antenna components
Manufacturers
Operators
Distributors
Customers
This change makes possible the ownership of some elements by more than one VNO. In the
case of multiple ownership (of antenna components, for example), each VNO only has
visibility and ownership of the antenna components they have created. This enhancement
allows support of duplicate components, allowing a new instance of the device each time it is
created by a VNO.
Multicast Bandwidth Group Support in GQoS [16237]

Beginning with iDX 2.0, a new default Bandwidth Group named Multicast is automatically
created for every network. This Bandwidth Group can be used to manage both the NMS and
user multicast traffic on the outbound carrier.
Line Card Failover Enhancement [17659]

For iDX 2.0, an HNO can now transfer line card control to a VNO, thus allowing the VNO to
configure and manage line card redundancy, if desired.
Increased GQoS Cost Precision [19314]

The previous cost range of 0.001 to 1.000 for GQoS costs has been enhanced to support a
precision of 5 decimal places (0.00100-1.00000).
ABS-Synchronizing Beam Information [19751]

The previous ABS behavior is now modified so the remote compares beams defined in its
Options file against beams defined in the new maplet header as part of the restart process
(particularly when switching beams). The remote now requests a new maplet any time there
is a beam defined in the Options file but not in the maplet header.
21
New Features
Custom Key To Adjust Remote Time [20428]

To aid in correlating events across servers, line cards and remotes for debugging purposes, the
Protocol Processor now sends the time over the air every 10 minutes to synchronize the
remote and line card time and date setting.
Although the time/date setting for NMS components automatically synchronizes over time,
the remote only catches up with the Protocol Processor time at the rate of approximately one
minute a day. To speed this synchronization along, a custom key has been added to directly
synchronized the remotes with the Protocol Processor.
The following custom key controls the way time is synchronized across the iDirect network
components:
[NET_TIME_SERVICE]
option = 0/1/2
where:
0 = disable the time service
1 = adjust time immediately upon receiving timestamp (default value)
2 = try to adjust time gradually if the difference of time is small
The Protocol Processor now broadcasts the time 5 seconds after it starts and periodically
thereafter. By default, the Protocol Processor broadcasts time every 10 minutes, but
operators now have the option of using the following custom key to change the frequency
interval:
[NETWORK_DEFINITION]
net_key_timeout_sec=xxx
Operators can also disable the time service by setting a very large net_key_timeout_sec
value.
22
Bug Fixes
This chapter lists all bugs that are fixed in the iDX 2.0.x.x releases. All bugs fixed in previous
releases are also fixed in the latest release.
This chapter contains the following major sections:
Tracking of Issues Resolved in iDX 2.0.x.x Releases on page24
Bugs Fixed in iDX 2.0.1.6 on page29
Bugs Fixed in iDX 2.0.1 on page33
In each bug fix section, the fixed bugs are grouped into the following two categories:
Operation Affecting Issues (Protocol Processor, Hub Line Card, Remote, NMS Server)
NMS/Reporting Issues (Client applicationsiBuilder, iMonitor, NMS Server)
23
Bug Fixes
Tracking of Issues Resolved in iDX 2.0.x.x Releases

The information in Table 5 is provided in order to track unresolved/known issues as they are
fixed in successive releases. Table 5 lists the bugs fixed in the iDX 2.0.x.x releases that were
unresolved and/or known issues in prior iDS or iDX releases. Click the page number link in the
last column to go directly to a detailed description of the bug.
Table 5. Resolved Issues Tracking Table
Bug
Number
Title
Affects GA
Release(s)
Reference
7743, 7730
Remote
8.0.2.x
Advertising/Responding with
RIPv2 while Deactivated
2.0.0.3
page 39
11422
iMonitorDisplay Issue
Regarding True Configured
Interface Speed on Remotes
7.0.5
2.0.0.3
page 40
11445
iMonitorChassis Warning
Message Inconsistent
8.2.x
2.0.0.3
page 40
2.0.0.3
page 40
13008, 12065 iBuilderCrashed Trying to

8.0.2.1
Modify Group QoS Settings on
Large Networks
13292, 13261 iBuilderMulti-Edit Allows
Encryption on EncryptionIncapable Remotes
8.0.1, 8.0.2.x
2.0.0.3
page 40
13718, 14569 iBuilderLow C/N Warnings

Not Varying By Configured
Mode
8.0.2.x, 8.2.x, 8.3.x
2.0.0.3
page 40
14228, 12392 iBuilderApplication Profiles 8.2.x

Reordered in Group View Not
Reflected in Profile View
2.0.0.3
page 40
14570, 14556 iBuilderMismatch in Limit

Value Display of Certain
Remote Warnings
8.2.x, 8.3
2.0.0.3
page 41
14864, 14654 iMonitorDisable Condition

in Active Conditions Tab in
iMonitor Does Not Work
8.0.1, 8.0.2.x, 1.0.x
2.0.0.3
page 41
15690, 15685 iBuilderLNB Voltage Field

Omitted From Options File
for Orbit Marine Antenna
Type
8.0.2.1, 8.0.2.3,
8.0.2.5
2.0.0.3
page 41
2.0.0.3
page 41
2.0.1, 2.0.1.1, 2.0.1.2, 2.0.1.4

2.0.1.3
page 29
16457, 16455 Activity Log Shows Failure

7.1.x, 8.0.1, 8.0.2.x,
When Applying Configuration 8.2.x, 8.3.x, 1.0.x
to Protocol Processor
17458
24
Fixed in
Release
Spoofer Handles Type 3

Keep Alive Messages
Inappropriately
Bug Fixes
Table 5. Resolved Issues Tracking Table (continued)

Bug
Number
Affects GA
Release(s)
Fixed in
Release
Reference
17476, 15202 iMonitorCNO Can View

Other Remotes in QoS
Statistics Windows
8.0.2.x
2.0.0.3
page 41
19041, 19803 iMonitorTypical Line Card

SNMP OID for Tx Bytes
Reports Zero on XLC-10
1.0.2, 1.0.3, 1.1
2.0.0.3
page 42
19566, 19702 iBuilderLocked Database

Warning Does Not Show VNO
User Information
8.0.1, 8.0.2.x, 8.2.x,

8.3.x
2.0.0.3
page 42
2.0.0.3
page 42
Title
19766, 19800 iBuilderCannot Turn Off

8.0.1, 8.0.2.x, 8.3.x
Warning Messages If Low SNR
Limit Values Matched
19814, 19844 NRD Server Stops Processing
Real Time Statistics After
Making Network Changes in
Large Networks
8.0.1, 8.0.2.x
2.0.0.3
page 42
19962
Opening Remote Modify

Window Resulted in OS
Password Change
7.x, 8.0.1. 8.0.2.x,

1.0.x, 1.1
2.0.0.3
page 42
20083
iMonitorLabeling Error in
FO/SO Graph of SATCOM
Screen
1.1
2.0.0.3
page 42
20120, 19602 Tx Power Rolloff at Extended 1.1

L-Band Frequencies for
e850mp Remotes
2.0.0.3
page 39
20364
8.0.2.7
2.0.0.3
page 39
20436, 20406 In ABS Mapless Mode Beam

Info Not Updated In
beam_state.opt File
7.0.x, 8.0.2.x, 8.3.x,

1.0.x, 1.1
2.0.0.3
page 39
20494, 20583 Sky ServerDoes Not Start

After Running the D-NMS
Configuration Script
8.3.x, 1.0.x, 1.1
2.0.0.3
page 42
20533, 19109 Warm Line Card Failover of

Rx Card Causes Tx LED to
Glow on New Active Line
Card
7.1.x, 8.0.1, 8.0.2.x,

8.3.x, 1.1, 1.0.x
2.0.0.3
page 39
20847, 21432 QPSK TPC 0.793 Performance 2.0.0.3, 2.0.0.4

Issues
2.0.1
page 33
20921, 21234 SS BPSK SF=1 TPC 0.66 and

0.533 Below SNR
Performance Specifications
2.0.1
page 33
Multiband LNB Not Working

for Orbit Marine Antenna
Controller
2.0.0.3, 2.0.0.4
25
Bug Fixes

Bug
Number
Affects GA
Release(s)
Fixed in
Release
Reference
2.0.0.3, 2.0.0.4
2.0.1
page 33
21053, 18799 Crypto LED Does Not Light Up 8.3.x

in TRANSEC Mode
2.0.1
page 33
21073
Title
20986,
CRC Errors If Frequency
20898, 21189 Hopping Between Evolution
and iNFINITI Line Cards
Ability to Delete Default

Mesh, Default Multicast and
NMS Multicast Profiles
2.0.0.3, 2.0.0.4
2.0.1
page 36
21116, 21319 Expanded Frequency Ranges

for XLC-11 and XLC-M Line
Cards
2.0.0.3, 2.0.0.4
2.0.1
page 33
21128
8.3.x, 2.0.0.3, 2.0.0.4
2.0.1
page 34
21225, 21226 No Transmit Line Card

Failover When Slot Is
Powered Off
2.0.0.3, 2.0.0.4
2.0.1
page 34
21273
2.0.0.3, 2.0.0.4
2.0.1
page 36
2.0.0.3, 2.0.0.4
2.0.1
page 36
21301
iMonitor: TDM Lost and SCPC 2.0.0.3, 2.0.0.4

Error Columns Switched in
Network Data Snapshot
2.0.1
page 36
21307
Failed & Recovered PP Blade: 7.1.x, 8.0.1, 8.0.2.x,

Stabilization may take up to 8.3.x
15 minutes
2.0.1
page 34
21316
Traffic Dropped If Any

Remotes With OTA RIP
Enabled Do Not Acquire
Network
2.0.0.3, 2.0.0.4
2.0.1
page 34
21320, 21207 iMonitor: Condition Snapshot 2.0.0.3, 2.0.0.4

Shows Incorrect Status for
Deactivated Remotes
2.0.1
page 36
21335
2.0.1
page 37
21363,
iMonitor: Some User-Defined 8.0.1, 8.0.2.x, 2.0.0.3, 2.0.1
21290, 21299 Service Levels Do Not Appear 2.0.0.4
in QoS Statistics
page 37
TCP File Transfer Failures
iMonitor: http Traffic

Counted Twice in IP Traffic
Calculation
21296, 19865 iBuilder: Mobile Remote

Selection Allowed for
Evolution X3 Remotes
26
iMonitor Freezes Retrieving

Latency Statistics for Large
Networks
2.0.0.3, 2.0.0.4
Bug Fixes

Bug
Number
Title
Affects GA
Release(s)
Fixed in
Release
Reference
21394
dbBackup.ini and
dbRestore.ini Not Saved by
Upgrade Script
2.0.0.3, 2.0.0.4
2.0.1
page 37
21396
iBuilder: iNFINITI 3100

2.0.0.3, 2.0.0.4
Cannot Be Selected For 8PSK
.79 Downstream Carrier
2.0.1
page 37
21397
Remote Maximum MODCOD

2.0.0.3, 2.0.0.4
Incorrectly Set After Network
Upgrade
2.0.1
page 35
21406
Possible XLC-M Line Card

Freeze During Boot-Up
2.0.0.3, 2.0.0.4
2.0.1
page 35
21407
iMonitor Exits When User

Resizes QoS Select Group
Window
2.0.0.3, 2.0.0.4
2.0.1
page 37
21410
iBuilder: VNO User Able to

2.0.0.3, 2.0.0.4
Apply Options Files and Reset
Line Cards
2.0.1
page 38
21412
iBuilder: Multiple Changes to 2.0.0.3, 2.0.0.4

VNO Access Rights Forces
Multiple Acknowledgments
by VNO Users
2.0.1
page 38
21428
Only First Application Profile 2.0.0.3, 2.0.0.4

is Recognized in an
Application Group on
Upstream
2.0.1
page 35
21436
DSCP Not Working in Earlier

iDX 2.0 Releases
2.0.0.3, 2.0.0.4
2.0.1
page 35
21481
iBuilder: Cannot Select

iConnex e800 in TRANSEC
Network
2.0.0.3, 2.0.0.4
2.0.1
page 38
21533
OpenAMIP Protocol Not

Sending F Command After
Configuration Parameters
2.0.0.3, 2.0.0.4
2.0.1.1
page 32
21534
OpenAMIP K Command Was 2.0.0.3, 2.0.0.4

Not Followed by F
Command
2.0.1.1
page 32
21535, 21631 Add Support for a Second

2.0.0.3, 2.0.0.4
Parameter for Open-AMIP L
Command
2.0.1.1
page 32
21536, 21577 Keepalive Interval for

Keepalives From Modem to
Antenna Misbehaving
2.0.1.1
page 32
2.0.0.3, 2.0.0.4
27
Bug Fixes

Bug
Number
28
Title
Affects GA
Release(s)
Fixed in
Release
Reference
21539
Upgrade of e8 Series Remote 2.0.1

from pre-iDX 2.0 to iDX 2.0.1
Fails When Using iSite or
iBuilder
2.0.1.1
page 32
21704
Nonexistent Beams In Map

File Not Treated As Zero
Quality Beams
2.0.1
2.0.1.2
page 31
21721
Round-Robin Order for

Trying Beams Not Fair In
Mapless Mode
2.0.1
2.0.1.2
page 31
21843
net_state_timeout Custom
Key Not Working Properly
2.0.1, 2.0.1.1
2.0.1.2
page 31
22106
Protocol Processor and

Remotes Cannot Pass ICMP
Packets With Invalid
Checksum
2.0.1
2.0.1.3
page 30
22184
SCPC Errors on iNFINITI

Remotes When Using a
Specific Combination of
8PSK and Certain
Frequency Range
8.0.1, 8.0.2.x, 8.3.x,

2.0.1.3
2.0.0.3, 2.0.0.4, 2.0.1,
2.0.1.1, 2.0.1.2
page 30
22161
Frequent Link Layer

Down/Up Timeouts (Link
Layer Bouncing)
2.0.1, 2.0.1.1, 2.0.1.2, 2.0.1.4

2.0.1.3
page 29
22972
Evolution Remotes Take

Excessive Time to Acquire
In Network When Using
Spectral Inversion On Tx
Side of Remote
2.0.1, 2.0.1.1, 2.0.1.2, 2.0.1.4

2.0.1.3
page 30
23030, 23477 Performance and Tuning

Ability Enhancement
2.0.x
2.0.1.5
page 29
23454
2.0.1.2, 2.0.1.3,
2.0.1.4, 2.0.1.5
2.0.1.6
page 29
Number of Configured
Beams Limited for ABS
Remotes
Bug Fixes
Bugs Fixed in iDX 2.0.1.6

Operation Affecting Issues
23454 Number of Configured Beams Limited for ABS Remotes
In previous releases, there was a limit on the number of configured beams for ABS
remotes. The maximum number varied ranging from 13 to 16 depending on the
network configuration. When the limit was reached, it could potentially crash the
falcon process on the remote. This limitation is enhanced and tested up to 24 beams
in this release.

23030, 23477 Performance and Tuning Ability Enhancement
In rare cases in previous releases, certain voice and fax applications could experience
degraded performance due to jitter on the upstream. This issue has been resolved in
this release. An enhancement to fine tune certain GQoS parameters is also
implemented.

17458 Spoofer Handles Type 3 Keepalive Messages Inappropriately
In previous iDX 2.0.1.x releases, the spoofer does not handle the Type 3 TCP
Keepalive messages appropriately. Consequently, some special applications, such as
ATM machines using such Keepalive messages, may not function properly. This issue
has been resolved in this release.
22161 Frequent Link Layer Down/Up Timeouts (Link Layer Bouncing)

In previous iDX 2.0.1.x releases, if the remote receives out of order frames, it could
result in a Link layer reset. In addition, an LL down message displays in iMonitor for
that remote. This issue has been resolved in this release.
29
Bug Fixes
22972 Evolution Remotes Take Excessive Time to Acquire In Network When Using
Spectral Inversion On Tx Side of Remote
An issue was found on Evolution remote software which calculates its frequency offset
incorrectly when its uplink is on spectral inversion. This causes Evolution remotes to
take longer than usual (as much as one hour) to acquire into network under certain
conditions. Affected products include:
Evolution X3, X5, e8350, e800, and e850mp remotes operating in DVB-S2 mode in
iDX 1.x and iDX 2.x networks
Evolution X5 remotes operating in iNFINITI mode in iDX 2.x networks
iNFINITI remotes are not affected by this issue.

This issue has been fixed in this release.

22106 Protocol Processor and Remotes Cannot Pass ICMP Packets With Invalid
Checksum
In certain cases where ICMP packets may have invalid or malformed checksums
because the packet is encrypted or other similar reasons, the iDirect PP and remotes
drop these ICMP packets due to the invalid checksum. Some customers may require
use of encryptors outside of the iDirect system, and therefore need the ICMP
checksums check to be disabled in order to pass the encrypted traffic. To optionally
disable the ICMP checksum checks, apply the following custom keys:
On the remotes hub-side option file:
[REMOTE_DEFINITION]
icmp_filter_bad_checksums = 0
On the remotes remote-side option file:
[ICMP]
icmp_filter_bad_checksums = 0
22184 SCPC Errors on iNFINITI Remotes When Using a Specific Combination of

8PSK and Certain Frequency Range
Due to some design issues related to the loop stability and phase margin, certain
iNFINITI remotes, when exposed to a very specific frequency and modulation
combination, may experience a high number of SCPC errors. This issue has been fixed
in this release.
30
Bug Fixes

21704 Nonexistent Beams In Map File Not Treated As Zero Quality Beams
In iDX 2.0.1, iDirect added a custom key that allowed network operators to prevent
roaming remotes with ABS from joining beams with a zero quality metric (Ability to
Disable Beam Switching to Zero-Quality Beams [21395] on page9). However, when
testing this new custom key, it was observed that the modem could switch to a
nonexistent beam instead of only choosing active beams as intended. In order to be
treated as a zero quality beam, the beam information for the nonexistent beam had
to be present in the map file as zero quality. The problem was fixed in this release.
21721 Round-Robin Order for Trying Beams Not Fair In Mapless Mode
When a modem is not receiving beam mapping information from the Map server
(mapless operation), it was discovered that the remote was not executing a fair
round-robin beam selection algorithm when attempting to acquire a usable beam. For
example, if 4 beams (1, 2, 3, 4) were defined in a network, the following order of
switching attempts might occur1, 2, 3, 1, 2, 4, 1, 2, 3, 1, 2, 4not a fair round-robin
selection.
To ensure that all beams get at least one chance to be acquired in the round-robin
beam selection algorithm, keep the value of the beam_unuse_timeout custom key
set to 60 minutes (or greater), as shown in the following Options file sample:
[BEAMS]
Beam_unuse_timeout = 60
This custom key defaults to a value of 60 minutes.
With incremental beam switch timeouts or a large number of beams, this value should
be increased above 60.
21843 net_state_timeout Custom Key Not Working Properly

In roaming remotes, net_state_timeout is the custom key that specifies the
length of time a remote should wait before switching to the next beam. During Beta
testing, when upgrading to iDX 2.0.1.2, it was discovered that the fix for Bug 21721
resulted in changes to the way the timer parameter and the beam quality parameter
were interpreted, which resulted in the net_state_timeout key not functioning as
expected. The underlying code was modified and the parameters and custom key now
work correctly.
31
Bug Fixes

NMS/Reporting Issues
The following client application bugs (iBuilder, iMonitor, NMS Server) are fixed in this release:
21533 OpenAMIP Protocol Not Sending F Command After Configuration

Parameters
iDirects OpenAMIP protocol, which is used with mobile remotes to control certain
antennas, was sending an F command in the middle of configuration parameters,
which caused certain configurations to be overlooked. (The F command is used for
finding a satellite or sending a parameter.)
The problem was fixed in this release.
21534 OpenAMIP K Command Was Not Followed by F Command

In some releases, the OpenAMIP K command was not followed by the F command,
which caused the antenna to disregard the K command. The K message conveys the
maximum skew of the short axis of a non-circular beam to the geosynchronous arc.
The OpenAMIP protocol was fixed to properly send F after the K command.
21535 Add Support for a Second Parameter for Open-AMIP L Command

The OpenAMIP L command has an optional second parameter that was not
implemented in prior releases. This second parameter indicates whether the modem
is free to transmit, and may be used by the antenna to remove power from the Tx
amplifiers.
This second parameter is now implemented in this release.
21536 Keepalive Interval for Keepalives From Modem to Antenna Misbehaving

The OpenAMIP keepalive interval for keepalives from modem to the antenna was
taking effect after 30 seconds. It should be effective immediately.
This problem was fixed in this release.
21539 Upgrade of e8 Series Remote from pre-iDX 2.0 to iDX 2.0.1 Fails When
Using iSite or iBuilder
When upgrading Evolution e8350, iConnex e800, or e850mp remotes to iDX 2.0.1, it
was discovered that the amount of memory available for the /tmp/ directory was not
sufficient, resulting in upgrade failures. During the BSP portion of the upgrade, the
script did not allocate sufficient memory for the remote.pkg to install, so the flash
always failed.
At the end of BSP package installation, the /tmp/ directory is remounted with
sufficient memory so that the remote.pkg can successfully install. This problem has
been fixed in this release.
32
Bug Fixes
Bugs Fixed in iDX 2.0.1

The following Protocol Processor, Hub Line Card, Remote, and NMS Server bugs are fixed in
this release:
20847 QPSK TPC 0.793 Performance Issues

In earlier releases of iDX 2.0, upstream TDMA QPSK TPC 0.793 was approximately 1 dB
below the SNR performance specifications published in the Link Budget Analysis
Guide for iDX 2.0. This performance issue has been fixed in this release.
20921 SS BPSK SF=1 TPC 0.66 and 0.533 Below SNR Performance Specifications
In earlier releases of iDX 2.0, upstream TDMA SS-BPSK SF=1 TPC 0.66 and SS-BPSK SF=1
TPC 0.533 were approximately 0.7 dB and 0.5 dB below the SNR performance
specifications published in the Link Budget Analysis Guide for iDX 2.0. This
performance issue has been fixed in this release.
20986, 20898 CRC Errors If Frequency Hopping Between Evolution and iNFINITI
Line Cards
In earlier versions of iDX Release 2.0, when Evolution and iNFINITI line cards were
used as receive line cards in the same Inroute Group (and in Frequency Hopping
mode), some CRC errors were seen on Evolution line cards, while the iNFINITI line
cards remained error free. This anomaly was caused by a symbol difference issue,
which has been corrected in this release.
Note: The custom key required in previous releases when Evolution and iNFINITI
line cards were frequency hopping in the same Inroute Group is no longer
needed in this release.
21053 Crypto LED Does Not Light Up in TRANSEC Mode

The Evolution e8350 Remote has eight LED indicators located on the front panel. One
of these LEDs (called the Crypto LED) should turn green when TRANSEC is enabled on
the remote. In some earlier releases, the Crypto LED on the e8350 Remotes did not
turn green on TRANSEC remotes.
This has been fixed in this release.
21116, 21319 Expanded Frequency Ranges for XLC-11 and XLC-M Line Cards
The Evolution XLC-11 line card Transmit Frequency Range has been expanded in iDX
Release 2.0.1. In earlier releases, the XLC-11 only supported frequencies between
950MHz and 1450MHz on the Tx side. The new Tx Frequency Range is 950MHz1750MHz.
On the Receive side, in previous iDX 2.0 releases both the XLC-M line card and XLC-11
line card had problems supporting the full receive range. Both line card models now
support the full frequency range from 950MHz to 1750MHz.
33
Bug Fixes
21128, 21393 TCP File Transfer Failures

In earlier releases of iDX 2.0, TCP file transfers sometimes failed. Depending on the
circumstances, this problem could affect TCP package or option file downloads, or
user applications such as e-mail or remote desktop services. The problem only
occurred in Application Based QoS Mode.
This problem was resolved by fixing a defect in the TCP spoofing software.
21225 No Transmit Line Card Failover When Slot Is Powered Off

With a Warm Standby line card configured to failover for a Tx line card, automatic
failover did not occur when the Tx line card slot was powered off. Powering off the
slot of the active line card now triggers a line card failover.
21307 Failed & Recovered PP Blade: Stabilization may take up to 15 minutes

In releases between iDS 7.1 and this release when Transmission Layer Security (TLC) is
enabled, it may take as long as 15 minutes to clear the TLC session with a failed blade
(including routing issues on the upstream router). Although automatic failover takes
over the failed blade soon after the failure, if the failed blade recovers within 15
minutes, it may still take as long as 15 minutes to clear the TLC session and reconnect
to update the blade configuration. Meanwhile, the recovered blade may believe it
still has the previously allocated remotes and continue to perform control of the
remotes causing instability to those remotes.
21316 Traffic Dropped If Any Remotes With OTA RIP Enabled Do Not Acquire
Network
This problem applied to earlier releases of iDX 2.0 with over-the-air RIP enabled for
one or more remotes in a network.
During the time when a remote with OTA RIP enabled was attempting to acquire the
network, RIP messages for that remote were stored on the protocol processor and
downstream bandwidth was incorrectly allocated for those messages. The amount of
downstream bandwidth allocated for the remote continued to increase as long as RIP
messages arrived and the remote was not acquired. This wasted bandwidth was not
available for use by any other remotes in the network. In the worst case, this problem
had the potential to consume all downstream bandwidth resulting in a halt to all
network traffic.
34
Bug Fixes
21397 Remote Maximum MODCOD Incorrectly Set After Network Upgrade

The Maximum MODCODs configured for remotes in DVB-S2 networks were not always
set to the correct value during the upgrade to earlier versions of iDX 2.0. In some
cases, after the upgrade, the Maximum MODCODs of the remotes were all set to the
minimum DVB-S2 MODCOD (QPSK 1/4). If this resulted in the Maximum MODCOD
configured for the remotes being below the Minimum MODCOD of the DVB-S2 carrier,
then those remotes could not acquire the network.
By design, a remotes Maximum MODCOD should default to the Maximum MODCOD of
the DVB-S2 carrier unless otherwise set by the operator.
21406 Possible XLC-M Line Card Freeze During Boot-Up

In earlier versions of iDX Release 2.0, if an XLC-M Line Card was used as a receive line
card in a DVB-S2 network, there was a potential for the line card to freeze during
boot-up.
This problem was caused by improper programming and timing sequence of the FPGA
by the software during boot-up. In earlier 2.0 versions, a line card custom key was
required to fix the problem. A custom key is no longer required to fix this issue.
21428 Only First Application Profile is Recognized in an Application Group on

Upstream
When there are multiple application profiles added into one application group, only
the service levels in the first application profile are recognized in this application
group. This happens only on the upstream direction rules. Downstream is not
affected.
This has been fixed on this release.
21436 DSCP Not Working in Earlier iDX 2.0 Releases

DSCP did not work in earlier versions of iDX Release 2.0. In previous iDX 2.0.0.x
releases, the traffic packets with DSCP marking were not being classified properly and
therefore were not being assigned to the proper QoS queue. Instead, all such packets
were being passed to the default queue.
35
Bug Fixes
The following Client application bugs (iBuilder, iMonitor, NMS Server) are fixed in this release:
21073 Ability to Delete Default Mesh, Default Multicast and NMS Multicast Profiles
In iBuilder, users should not be able to delete Default or NMS Application profiles.
However, in earlier releases it was possible under some circumstances to delete the
Default Mesh Upstream Profile, the Default Multicast Downstream Profile, and the
NMS Multicast Downstream Profile. These profiles can no longer be deleted under any
circumstances in this release.
In addition, beginning with this release, a restriction has been placed on VNO users
with respect to deleting QoS profiles. A VNO user can no longer delete a Visible
profile that is not owned by the VNO. A VNO can, however, continue to delete owned
profiles that are not being used by the VNO.
21296 iBuilder: Mobile Remote Selection Allowed for Evolution X3 Remotes

Earlier versions of iDX Release 2.0 allowed you to select the Mobile option for
Evolution X3 remotes on the iBuilder Remote Geo Location tab even though that
option is not supported for X3 remotes. Moreover, once Mobile was selected, you
could not re-select the Stationary option. Therefore, it was necessary to delete and
re-create the remote in iBuilder to correct the problem.
21273 iMonitor: http Traffic Counted Twice in IP Traffic Calculation

In earlier releases of iDX 2.0, http traffic was counted twice when all IP traffic was
totaled in iMonitor. This traffic was correctly counted both as http Traffic and as TCP
traffic when totals for those traffic types were separately calculated. However in the
total IP traffic calculation, it should have been counted only one time.
21301 iMonitor: TDM Lost and SCPC Error Columns Switched in Network Data
Snapshot
In earlier versions of iDX Release 2.0, the data in the TDMA Lost and SCPC Error
columns of the iMonitor Network Data Snapshot were reversed for iNFINITI remotes.
The TDMA Lost count was shown in the SCPC Error column and the SCPC Error count
was shown in the TDMA Lost column.
21320 iMonitor: Condition Snapshot Shows Incorrect Status for Deactivated

Remotes
In earlier releases, the iMonitor Conditions Snapshot sometimes grouped deactivated
remotes into the wrong groups. For example, a deactivated remote could be
incorrectly included in the Layer 2 (alarm) Group rather than in the Deactivated
Group. However, these remotes were correctly shown as Deactivated in the iMonitor
tree.The problem was resolved by fixing a race condition that existed between the
NMS configuration server process and the NMS event server process.
36
Bug Fixes
21335 iMonitor Freezes Retrieving Latency Statistics for Large Networks

The iMonitor display froze when attempting to retrieve Latency information for large
networks, making the results unreadable. This problem was seen when attempting to
retrieve Latency information for approximately 2,000 remotes.
21363 iMonitor: Some User-Defined Service Levels Do Not Appear in QoS Statistics
In iMonitor, you can view Upstream or Downstream QoS statistics for Service Levels
assigned to Virtual Remotes. In some earlier releases, some user-defined Service
Levels were not included when the QoS statistics were displayed in iMonitor.
21394 dbBackup.ini and dbRestore.ini Not Saved by Upgrade Script

When you upgrade to a new iDirect release, the upgrade script should automatically
save the existing versions of the files dbBackup.ini and dbRestore.ini in the NMS
/home/nms/utils/db_maint directory before resetting these files to their default
values. When upgrading to earlier versions of iDX 2.0, the existing files were not
saved.
The upgrade script has been modified to save the current versions of dbBackup.ini
and dbRestore.ini to /home/nms/utils/db_maint with the file names
dbBackup.ini.rpmsave and dbRestore.ini.rpmsave.
21396 iBuilder: iNFINITI 3100 Cannot Be Selected For 8PSK .79 Downstream
Carrier
In some earlier releases, iBuilder users were unable to add iNFINITI 3100 remotes to
networks configured with a Downstream Carrier FEC Rate of 8PSK .79, even though
that FEC Rate is supported for that Remote Model Type.
21407 iMonitor Exits When User Resizes QoS Select Group Window
When an iMonitor user selects QoS Stats from the iMonitor Tree menu, the Select
Group / Virtual Remote window opens to allow the user to select QoS nodes for
viewing. In some earlier releases, resizing this window sometimes caused iMonitor to
exit.
37
Bug Fixes
21410 iBuilder: VNO User Able to Apply Options Files and Reset Line Cards
In earlier release of iDX 2.0, VNO users logged on to iBuilder could apply line card
options files and reset line cards from the Multicast Download and Automated
Configuration Downloader dialog boxes even if the VNO did not have permissions for
these operations. Although these operations were correctly disabled in the iBuilder
tree, they were not disabled in these dialog boxes.
In this release, filtering is applied to the Multicast Download and Automated
Configuration Downloader dialog boxes based on user permissions. Unless the VNO
has permission to perform operations on specific network elements, those elements
are not displayed when a VNO user opens either of these dialog boxes. This prevents
the VNO user from performing prohibited operations on network elements.
21412 iBuilder: Multiple Changes to VNO Access Rights Forces Multiple

Acknowledgments by VNO Users
In earlier releases of iDX 2.0, if an HNO user made multiple changes to a VNOs
visibility and/or permission settings in iBuilder, a VNO user was forced to acknowledge
each change separately rather than all at once. This caused a cycle of pop-up
messages and automatic logging off/on for the VNO user until all queued changes
were acknowledged. With this release, the VNO user is only required to click OK on
the pop-up message one time regardless of the number of changes previously made by
the HNO.
21481 iBuilder: Cannot Select iConnex e800 in TRANSEC Network

In earlier releases of iDX 2.0, you could not select iConnex e800 as the remote model
type for a remote in a TRANSEC-enabled network.

The following Protocol Processor, Hub Line Card, Remote, and NMS Server bugs were fixed in
iDX 2.0.0.4:
21183, 21375 Degraded RF Link Condition Caused Link Layer Instability

In networks where remotes were experiencing degraded RF link conditions or other
similar conditions which result in dropped packets during TCP data transfer sessions,
the link layer for that remote (hub side or remote side) could enter a state where it
would continually bounce (even after returning to the normal RF level) causing traffic
interruption for the affected remote. Operators could observe this condition as
repeated "LL_Down" alarms in iMonitor.
38
Bug Fixes

The following Protocol Processor, Hub Line Card, Remote, and NMS Server bugs were fixed in
iDX 2.0.0.3:
7743 Remote Advertising/Responding with RIPv2 while Deactivated

In previous releases, the remotes continued to advertise RIP Routes even out of
network. Now the remotes stop advertising RIP routes once they are out of network.
20120 Tx Power Rolloff at Extended L-Band Frequencies for e850mp Remotes

For e850mp remotes (which support extended L-band frequencies), when setting the
Tx frequency from the remote command line, the power level dropped off
approximately -35dBm at 1700MHz and above. This did not happen in Peer-to-Peer
mode. Additionally, when in remote mode, changing the frequency from the
command line did not set the Tx band correctly. This issue could impact
commissioning a remote from the command line, since bringing up a modulated
carrier above 1700MHz would produce inaccurate results.
20364 Multiband LNB Not Working for Orbit Marine Antenna Controller
Multiband LNB was not working as expected when a remote was configured to be
connected to an Orbit marine antenna controller. The command/response format was
not as expected, with values being sent as null in lnbv, and with a pol value sent
instead.
Now, Multiband is working correctly with Orbit controllers, with all parameters sent
properly.
20436 In ABS Mapless Mode Beam Info Not Updated In beam_state.opt File
In ABS mapless mode, the remote was not updating the BEAMSELECTOR_STATE
information such as quality, value and time in the beam_state.opt file.
Now, this functionality is working correctly. The remote is able to switch between the
beams, and the BEAMSELECTOR_STATE value is getting updated properly.
20533 Warm Line Card Failover of Rx Card Causes Tx LED to Glow on New Active
Line Card
If an M1D1 line card was used for Rx only redundancy, after a Line Card failover, the
Tx LED on the now active Standby Line Card was glowing instead of the Rx LED.
39
Bug Fixes
The following iBuilder, iMonitor, and NMS Server bugs were fixed in iDX 2.0.0.3:
11422 iMonitorDisplay Issue Regarding True Configured Interface Speed on

Remotes
The Remote Status tab was not displaying correct values for the Eth Mode and Eth
Speed columns for the speed and duplex setting of the device connected to the LAN
port of the 3100 remote. iMonitor was indicating that the port was set to 100 Mbps,
while the mii-diag console command indicated the port was at 10 Mbps.
11445 iMonitorChassis Warning Message Inconsistent

On some previous releases, the RCM-B Warning was incorrectly indicated as
UCP_OUT_OF_NETWORK in the Type field of the iMonitor Conditions window.
12099 Remote Not Getting New Map File from Map Server
In some previous releases, a roaming remote might not receive maplets from the Map
server at certain times.
13008 iBuilderCrashed Trying to Modify Group QoS Settings on Large Networks

When trying to modify Group QoS (GQoS) settings on large networks, users were
prevented from modifying network GQoS settings because they would receive the
error message failed to save ..., after which the iBuilder session immediately
disconnected.
13292 iBuilderMulti-Edit Allows Encryption on Encryption-Incapable Remotes

When modifying multiple remotes, iBuilder failed to restrict encryption capabilities
therefore enabling encryption on remotes which were not capable of supporting this
feature.
13718 iBuilderLow C/N Warnings Not Varying By Configured Mode

In previous releases, LOW C/N warnings were generated whenever the C/N value on
either the upstream or downstream fell below the configured threshold based on
QPSK modulation and popular FECs.
Now the correct Warning properties values on the Warning Properties tab for
remotes are updated correctly based on the published C/N values of various
MODCODs. Refer to the iDirect Link Budget Analysis Guide for default values for
minimum C/N for all modes currently supported in iDX 2.0.0.3.
iMonitor now also correctly reports and triggers alarms when configured
Modulation/FEC values are reached.
14228 iBuilderApplication Profiles Reordered in Group View Not Reflected in

Profile View
Corrected a display problem where new Application Profiles, created in Group view
and then reordered, were not displaying in the correct new order within the Profile
view.
Application Profiles reordered in the Group view are now successfully updated and
correctly ordered in the Profile view.
40
Bug Fixes
14301 iBuilderDeleted VLAN Entry Available for Remotes in Choose Details

Window
Corrected the problem where a VLAN, deleted from both a Protocol Processor and
remote (and with the configuration change applied), was still available for selecting
for the remote. VLAN availability could be observed after selecting View>Choose
Details, then selecting All available fields from Select Filter for Details list...
14570 iBuilderMismatch in Limit Value Display of Certain Remote Warnings

In some previous releases, the Limit Value displayed in the Modify Warning window
was different from the Limit Value displayed in the Properties window (the Modify
Configuration window) for the remote.
14864 iMonitorDisable Condition in Active Conditions Tab in iMonitor Does Not

Work
With a remote disabled in iBuilder, the alarm condition (out of Network/red cross)
still showed up in the Active Conditions tab and could not be disabled using the
right-click>Disable condition operation with the mouse.
Now, disabling the active condition (alarm/warning) for active remotes moves the
warning to the Disabled Conditions tab. All the conditions of deactivated remotes are
removed from the conditions panel.
15337 para_cfg.opt File Not Created By NMS-configuration-client.pl Script

After running the NMS-configuration-client.pl script to configure D-NMS, the
para_cfg.opt file was missing from the Latency server machine. This would cause
the latency data to be populated incorrectly.
The NMS-configuration-client.pl script now creates the required
para_cfg.opt file.
15690 iBuilderLNB Voltage Field Omitted From Options File for Orbit Marine
Antenna Type
When creating and saving a mobile remote configuration with the AL-7104 reflector
type selected, the lnb_vdc=value field under the [SATELLITE] group did not appear
in the remotes Options file.
Now when the antenna type selected is Seatel (Reflector = DAC-97), the
lnb_vdc=value field appears under the [SATELLITE] group.
16457 Activity Log Shows Failure When Applying Configuration to Protocol

Processor
The Activity log erroneously logged a failure entry when applying a configuration to
the Protocol Processor.
17476 iMonitorCNO Can View Other Remotes in QoS Statistics Windows

CNO users were able to view QoS statistics for other remotes in iMonitor. The CNO
could only see their remotes in iMonitor. However, when the QoS Statistics window
was opened in iMonitor, all the remotes in the network were displayed.
Now, only those remotes given visible permission are visible in the tree view.
41
Bug Fixes
19041 iMonitorTypical Line Card SNMP OID for Tx Bytes Reports Zero on XLC-10
The OID for an XLC-10 line card's Tx bytes was reporting as zero even though traffic
was passing through.
19566 iBuilderLocked Database Warning Does Not Show VNO User Information
On some previous releases, when a VNO user was modifying a network configuration,
the database was locked and the HNO user could not modify the network
configuration, which was normal behavior. However, the pop-up message did not
identify (for the HNO) the VNO user modifying the database.
Now the pop-up message provides the VNO user information for the HNO user.
19766 iBuilderCannot Turn Off Warning Messages If Low SNR Limit Values
Matched
In iBuilder, when editing the Global Warning for Remote, then highlighting the
DownsteamSNR or UpstreamSNR LOW Limit Type, the Edit Low SNR Limit button was
active. Users could turn off the warning for low SNR by modifying the Global Warning
table. However, if the carrier configuration matched the value in that table, it would
still raise a warning when meeting thresholds, regardless of the Send Value Change
disabled in the previous table.
See Section 2.14, Configuring Warning Properties in the iBuilder User Guide for iDX
Release 2.0 for complete details about setting Global Warnings in iBuilder.
19814 NRD Server Stops Processing Real Time Statistics After Making Network
Changes in Large Networks
When making a network level change on a large network, the NRD server stopped
processing real time messages. By restarting the NRD server, the statistics started
flowing again.
19962 Opening Remote Modify Window Resulted in OS Password Change

In previous releases, if the network was upgraded from an older version, opening a
modify window for a remote occasionally resulted in an OS password change. This
occurred after opening a modify window for a remote in Builder, and without
changing any value, clicking OK. The remote went into Changes Pending state and the
difference was reported as an OS password change. The Changes Pending state was
due to password encryption hash key changes, not an actual password change.
20083 iMonitorLabeling Error in FO/SO Graph of SATCOM Screen

In iDX 1.1 there was an error in the SATCOM screen with the labeling of the FO/SO
graph. The labeling failed to indicate Symbol and Frequency Offsets, and the last two
values for sym off and freq off were not displayed.
20494 Sky ServerDoes Not Start After Running the D-NMS Configuration Script
In some previous releases, the skysvr process on the NMS failed to start automatically
after running the D-NMS configuration script.
42
Known Issues
This section lists all known issues in the latest release of iDX 2.0.x.x (iDX 2.0.1.2) as of the
date of publication. These issues are grouped into the following two categories:
Operation Affecting Issues (Protocol Processor, Hub Line Card, Remote, NMS Server)
NMS/Reporting Issues (Client applicationsiBuilder, iMonitor, NMS Server)

The following Protocol Processor, Hub Line Card, Remote, and NMS Server known issues are
addressed in this section:
24844 Certain Filter and QoS Rule Combinations Not Classifying Packets Correctly
Beginning with iDX 2.0, iDirect introduced new optimized packet classification logic
which includes Filters and QoS matching rules. In iDX 2.0.x.x an error was introduced
to this logic which can be observed when more than three unique VLAN IDs are
defined in the combination of these Filters and QoS matching rules, leading to the
possibility that the classification of certain packets can fail.
Work-around:
Reduce the number of unique VLAN IDs defined in the Filter and Application Profile
rules to three or less.
18783 Maximum Information Rate Not Enforced in Carrier Grooming Mode

In carrier grooming mode, if you configure upstream Maximum Information Rate (MIR)
in the Group QoS tree for an Inroute Group, then that amount of MIR is granted to
each individual inroute in the inroute group rather than across all inroutes in the
inroute group.
For example, if you have two inroutes in your inroute group, and you configure 1 Mbps
of MIR at the Service Group level of the tree, then the system should allocate 1 Mbps
of upstream MIR for all remotes in the Service Group regardless of which inroute they
are using. However, in carrier grooming mode, each inroute in the inroute group will
be granted 1 Mbps of MIR for remotes in the Service Group, effectively doubling the
MIR available to those remotes in the Inroute Group.
This problem only applies to carrier grooming mode. In Frequency Hopping mode, the
MIR is correctly enforced across all inroutes in the inroute group.
43
Known Issues
20149 COTM Frequency Tracking Algorithm Not Working Correctly

The COTM frequency tracking algorithm in this release appears to exhibit a frequency
error as seen by the demodulator. The period of the SAW tooth waveform is 5 seconds
(equal to the COTM UCP update) and the frequency slope changes every 80 seconds.
The issue is the steady negative and positive frequency offsets seen by the
demodulator that reduce the tolerance capacity of the demodulator.
In previous releases, the SS demodulator tolerance was greater than 2%, though the
published spec was 1.5%. In essence this unwanted offset was absorbed. In iDX 2.0 it
was decided to reduce this range to exactly 1.5% and this shows up as CRC errors.
21812 ICMP Header Processing Error on PP-VLAN Interface

Because of an ICMP header processing bug, users are not able to ping any VLAN
interface on the Protocol Processor blades other than VLAN 1, even though all VLANs
are configured correctly and are working. This issue exists on the Protocol Processor
VLAN interface. Performing a TCPDUMP on the PP eth0 interface will show ICMP
request and response packets, but the actual ping does not occur due to the ICMP
header bug.
This will be fixed in a future release.
21841 Queued UDP Traffic Causing Bandwidth Wastage

If a remote is actively receiving UDP traffic on the downstream and it falls out of the
network (for reasons such as powering off, roaming, etc.), some UDP traffic may be
queued in the Protocol Processor waiting for transmission. This traffic is not released
until the remote synchronizes back with the Protocol Processor. The queued UDP
traffic continues to be allocated downstream bandwidth, which it cannot use.
Normally, a remote remains in this state for a very short period of time. However, in
roaming networks, if a remote moves to a different network while passing UDP
traffic, it may remain in this state permanently, resulting in bandwidth wastage on
the network in which was passing traffic.
Work-around:
If a remote is in this state, deactivating and then reactivating it will resolve the issue.
To prevent this state from occurring: Apply the following custom key on the hubside
for each remote:
[DFOE]
dfoe_always_data_transfer=1
44
Known Issues
21944 iConnex-100 Remotes Cannot be Configured as Mobile Remotes

After upgrading from a previous release, iBuilder does not allow the user to configure
iConnex-100 remotes as mobile remotes. The iConnex-100 remotes can be selected,
but the mobile options on the GEO tab are all grayed out and cannot be selected.
Work-around:
Before upgrading, manually enter the [MOBILE] group custom key settings in the
remote-side custom key window of each iConnex-100 remote. Setting these custom
keys ensures the remote is enabled as mobile after the upgrade.
iDirect advises operators to first examine the existing [MOBILE] group settings of their
iConnex-100 remotes for any differences in values between the existing settings and
the custom key default values recommended in this work-around. If any differences
are found, the existing values should be entered in the remote-side custom key
window, and not replaced with the recommended default values.
Recommended Custom Key Settings:
Before upgrading, manually enter the following custom keys and default values (as
required) in the remote-side custom key window of each iConnex-100 remote:
[MOBILE]
is_mobile = 1
tx_handshake_enabled = 1
gps_input = 1
gps_serial_setting = 4800, 8N1
gps_device = Socket
latlong_timeout = 120
latlong_interval = 15
latlong_fail_interval = 10
init_tx_power_offset = 0.000000
22490 Map-based ABS Remote with Serial NMEA Input Operating in Western
Hemisphere may Operate in Mapless Mode
Mobile ABS remotes which take GPS information from the serial port may not be able
to interpret the NMEA string properly to position its location on the map when the
remote is in the Western Hemisphere. As a result, the remote may run in mapless
mode while requesting a maplet repeatedly. The remote will normally not drop out of
the network because of this condition. However, if the remote drops out, it will be
acquiring the network in a round-robin manner (as in mapless mode operation), and
operators may observe the following message repeating on the console (after
telneting to the remote):
BeamHandler beam check (7.00:visble 7.00:visble):12:0,30:5,on 30
running mapless...
beamselector: s=AwaitGPS,e=MapAvail
GOT NEW MAP...EXIT MAPLESS MODE
LAT-LONG : [LAT = 52.46576N LONG = 0.66083W]
beamselector: s=AwaitGPS,e=GpsAvail
45
Known Issues
The following iBuilder, iMonitor, and NMS Server known issues are addressed in this section:
17912 SNMP Stops Sending Messages and Needs Restarting

Due to a problem in the dbBackup script and a bug in the NET-SNMP code, the SNMP
server stops sending traps and needs to be restarted periodically. A final fix involves
an upgrade of SNMP code which is a part of Linux.
Work-around:
Create the file /etc/snmp/snmpsvr.conf and add the line:
agentxPingInterval 86400
19932 NRD ServerRun-time Consolidation Versus get-last Queries

The NRD server improperly handles data at the border of the historical and realtime portions of a get-last query. The following sample output data illustrates
what happened when a get-last OTA statistics was executed while running steady
traffic:
Time
17:40:40
17:41:40
17:42:20
17:42:25
17:42:30
Diff (s)
60
60
40
5
5
Total (kb)
18229.824
18321.808
1516.624
1516.904
1523.648
Total (kbps)
303.830
305.363
37.916
303.381
304.7296
As shown in the sample output above, although the total data rate was constant at
about 300 kbps, iMonitor reported a much lower rate at query time (a bit before
17:42:20). The 17:42:20 total should be around 12000 kbps, or there should be
another data line with a 17:42:15 entry of approximately 10500 kbps.
Work-around:
For more accurate data, users can refer to real time or historical queries.
19963 iMonitorHangs When Timeplan Window Left Open

When the Timeplan>Slot assignment window is opened in iMonitor and the user
moves to work on another application, then returns, iMonitor keeps on updating the
slot assignment details and hangs rather than allowing the user to work on this data.
The user is finally forced to end the iMonitor application.
20148 iBuilderAll Remotes and Applications Disappear in ProfileApplication

Mode When New Application Added
In Application-based mode, after successfully adding new Applications in Group view
and Profile view, all remotes and Applications (even Default and NMS) disappear in the
Profile>Remote view. After clicking OK and reopening the GQoS tab (or choosing
something different in the Select Group drop-down menu of that window), all
remotes and Applications appear again.
46
Known Issues
20196 iMonitorPower Setup in Cross Polarization Portion of Probe Can Go Below

-40 dBm
The CW TX Power setup in the Cross Polarization portion of the Probe tab in iMonitor
can go below -40 dBm, even though a value below -35dBm on a remote is unreliable
for the Tx power output level.
While iMonitor can display lower values as configured, the remote does not actually
go lower than -40 dBm.
21160 Config Server and Chassis Manager Lose Synch After Failing to Apply
Configuration
When you upgrade to iDX 2.0.x from an earlier release, your chassis configuration is
preserved in the NMS database. After the upgrade, you must import your chassis
licenses into iBuilder and validate the chassis serial number on the chassis
configuration screen. You then apply the chassis changes in iBuilder to activate your
licensed chassis.
Under certain circumstances the iBuilder chassis configuration can be lost during this
process. Specifically, after you import your chassis license and validate your chassis
serial number, then if the changes are not successfully applied to the Chassis Manager,
restarting either the NMS Configuration Server or Chassis Manager will cause the
chassis configuration to be lost. Should the problem occur, you must reconfigure the
chassis in iBuilder.
This problem was seen when a chassis license was issued containing an incorrect
Chassis IP Address. Therefore, to avoid the problem, you should ensure that the
chassis IP address in your license request is the correct IP address for the chassis.
iDirect also suggests that you make a record of the chassis configuration before you
apply the license to the chassis in iBuilder in the event that the problem occurs and
you need to reconfigure the chassis.
21217 iBuilder: Cannot Assign LNB with 10Mhz Enabled to iConnex e800 Remote
On the iBuilder Remote VSAT tab, you cannot assign an LNB with 10MHz enabled to an
iConnex e800, even though the e800 is capable of supplying the 10 MHz clock to the
LNB.
Work-around:
1. Create an LNB (or modify an existing LNB) to meet your specifications but do not
select ODU Rx 10 MHz.
2. Assign the LNB to your iConnex e800 remote on the Remote VSAT tab and save the
changes.
3. On the Remote Custom tab, define the following Remote-side custom key:
[ODU]
odu_rx_10_mhz = 1
4. Save the remotes configuration and apply the changes to your remote.
47
Known Issues
21274 iMonitor: Timeplan Graph Shows Allocated Slots in Free Slot Column
In the iMonitor Timeplan display for a receive line card, the bottom graph (Individual
Allocation) shows slots assigned to individual remotes. (Both free and allocated slots
can be assigned to remotes.) The graph also has a Free column at the far left
representing free slots.
You can control the data represented in the graph using the Allocated Slots and Free
Slots check boxes at the bottom of the graph. When only the Allocated Slots check
box is selected, slots allocated to individual remotes are displayed in the remote
columns and all free slots are grouped in the Free column.
When only the Free Slots check box is selected, the individual remote free slot
allocations are shown in the remote columns. In that case, the Free column should be
empty. In this release, however, when only the Free Slot check box is selected, the
allocated slots are (incorrectly) displayed in the Free column. The problem is
illustrated in Figure 2, where the Free column should be empty.
Figure 2. Timeplan Graph: Incorrect Free Column
21286 Revision Server Resets Remotes Repeatedly When Updating Large Number
of Remotes
When using the Revision Server to update a large number of remotes, some remotes
may reset repeatedly during the upgrade process.
This problem was seen when approximately 200 remotes had changes pending in
iBuilder and the Revision Server was used to update the configurations. During the
update process, a number of remotes reset several times before finally returning to
the network with the new configuration. Although the Revision Server was sending the
correct software/options file, the changes pending were not being cleared for some
of the remotes.
48
Known Issues
This problem can be caused by upstream congestion which may be worsened by

sending new configuration to a large number of remotes simultaneously. When the
remotes receive their new configuration they respond to the NMS (via UDP) to inform
the NMS that they have the new settings. However, if upstream congestion prevents
some of those messages from reaching the NMS configuration server, the NMS will
resend those configuration changes and the non-responsive remotes will reload the
configuration and reset again. Eventually, the problem subsides as more and more
remote responses are received by the NMS.
It may be possible to mitigate this problem by manually retrieving the active
configuration from the remotes in iBuilder in smaller groups.
In iBuilder, repeat this process until you have retrieved all remote configurations. This
should re-synchronize the remotes with the NMS configuration server.
1. On the View menu, select Details and Collapse Details Hierarchy.
2. In the Details pane, select the Type column header to group remotes together in
the window.
3. Select the problem remotes in groups of 20 or 30 remotes
4. Right-click the selected remotes and select Retrieve Multiple Configuration
Active Configuration from the menu.
5. Click OK to retrieve the configurations
Remotes whose configurations are successfully retrieved should cease reloading their
configuration and resetting.
21445 NMS Chassis Communications Problem Causes Alarms on Other Chassis

On rare occasions, in the case of multiple chassis being managed by the same Chassis
Manager Server, if the NMS cannot communicate with one of the chassis, all chassis
may show the Lost connection with chassis alarm in iMonitor. After some time
(typically about 20 minutes), this alarm should clear on all good chassis without any
operator action. However, if you experience this problem and want to clear the
alarms on the good chassis immediately, follow the steps below.
Work-around:
1. Using a Secure Shell (SSH) client such as PuTTY, log on to the root account of the
NMS server machine.
2. Enter the following command to restart the Chassis Manager Server:
service idirect_nms restart cmsvr
3. Log off of the NMS server machine.
49
Known Issues
21451 iBuilder Falsely Reports Failed to Assign Standby Error

In iBuilder, you can use the Manage Line Card Redundancy window to establish
redundancy relationships between active and standby line cards. When assigning a
line card as a standby, you may sometimes see the message Failed to Assign
Standby even though the assignment was successful.
If you see this message, check iBuilder to verify that the redundancy relationship was
correctly established. If the standby line card becomes complete and the redundancy
relationship is shown in the Manage Line Card Redundancy window, then the operation
was successful.
22507 iBuilderFast Fade Configuration Changes Do Not Update Options File

If a user changes the default values of the Fast Fade configuration parameters for a
DVB-S2 network, the first time changes work fine. However, any subsequent changes
may not be properly propagated to the remote Options file.
Work-around:
To get around this issue, iDirect recommends setting the following remote-side
custom keys if the Fast Fade configuration parameters need to be changed for any
reason. Generally, the default values work fine, with the values shown below just an
example:
[DVBS2]
fast_fade_margin = 100
mode = acm
system_margin_steady_state = 50
threshold = 50
50
This section contains the following topics:
Installing iDX 2.0.1.6 Patch
Installing iDX 2.0.1.4 Patch (Obsolete and Replaced by iDX 2.0.1.6)
Installing iDX 2.0.0.3, 2.0.0.4, and 2.0.1

Note:
This patch release can only be installed on networks already running

iDX 2.0.1.x releases.
Note:
This patch is not applicable to iNFINITI 3100 and Evolution X3 remotes.
The iDX 2.0.1.6 remote patch corrects the issue described in Bugs Fixed in iDX 2.0.1.6 on
page 29. This patch release consists of one Linux BSP package and one remote image package
for each applicable remote model. Table 6 lists the Linux BSP package files and remote
package files by remote model type.
Table 6. Cumulative Update and Remote Upgrade Packages for DX 2.0.1.6
Type of Remote
Linux BSP package
Remote Package
iNFINITI Remote (other than iNFINITI 3xxx)
linux_2.4_bsp-10.0.1.6
remote-10.0.1.6
Evolution X5 Remote
linux_2.4_bsp-10.0.1.6
evo_x5_rmt-10.0.1.6
Evolution 8 Series
linux_2.6_bsp-10.0.1.6
e8_rmt-10.0.1.6
Note:
All remote-side bug fixes, enhancements and other code changes included in
iDX 2.0.1.1, iDX 2.0.1.2, iDX 2.0.1.3 and iDX 2.0.1.4 are also included in this
iDX 2.0.1.6 patch. Remotes running iDX 2.0.1.6 are fully operational in any
network where the hub components (and/or other remotes in the same network)
are running any previous iDX 2.0.1.x release.
51
Perform the following steps to download and install this patch.

1. Logon to the TAC web page and click iDX 2.x Releases. On the iDX 2.x.x.x page scroll
down to iDX Release 2.0.1.
2. Download the file Remote Software and iSite - iDX 2.0.1.6.zip, and unzip this file on
your desktop.
The remote package files are contained in the Images folder, in their respective remote
model type folders (i.e., Remote_Evolution_X3_X5, Remote_Evolution_e8series, and
Remote_iNFINITI).
3. Using an SSH connection, logon to the NMS server.
4. Using WinSCP and referring to Table 7, copy the remote Linux BSP package and remote
image package for each model type in your network to the correct folder in the NMS
server.
Table 7. Source and NMS Target Folders for iDX 2.0.1.6 Remote Packages
Source Folders
Software Packages
Package
Size
Remote_Evolution_e8series
e8_rmt-10.0.1.6.pkg
7,833
/home/nms/cfg/image_sets/e8_rmt_
package
WinSCP Target Folder in NMS
linux_2.6_bsp-10.0.1.6.pkg
838
/home/nms/cfg/image_sets/linux_
2.6_bsp_package
Remote_Darwin_X3_X5
evo_x5_rmt-10.0.1.6.pkg
3,812
/home/nms/cfg/image_sets/evo_x5_
remote_package
Remote_Darwin_X3_X5
2,246
2.4_bsp_package
Remote_iNFINITI
remote-10.0.1.6.pkg
4,419
/home/nms/cfg/image_sets/remote_
package
Remote_iNFINITI
2,246
2.4_bsp_package
To download the Linux BSP packages, remote image packages, and to reset your remotes
using iBuilder, please see the chapter entitled, Upgrade Remotes in the Network Upgrade
Procedure Guide for iDX 2.0.1.x.
Note:
52
Revision Server cannot be used to push this patch to remotes.

Note:

The iDX 2.0.1.5 Protocol Processor patch includes updated versions of the sada and sarmt
process files, in binary form. Follow the instructions below to copy the zipped and
compressed sada and sarmt files from the release folder on the TAC web page to your local
PC, rename the old executables, transfer the new executables to your Protocol Processor
blade, and finally run the new executables. Performing this patch installation procedure will
cause a network outage, therefore planning a maintenance window is recommended.
Perform the following installation steps on each Protocol Processor blade in your system:
1. Logon to the TAC web page, and click the Software Releases link.
2. Click the iDX 2.x Releases link and scroll down the iDX 2.x.x.x page to
iDX Release 2.0.1.
3. Download the file Protocol Processor Software iDX 2.0.1.5.zip to a temporary folder
on the desktop of your PC, and unzip this file.
4. Logon to your Protocol Processor blade.
5. Enter the following command to change directories:
cd /usr/sbin/idirect/
6. Enter the following commands to save a backup of your current sada and sarmt
executables:
mv sarmt sarmt.old
mv sada sada.old
7. Using WinSCP, copy the sada.bz2 and sarmt.bz2 files from the temporary folder on
your PC desktop to the /usr/sbin/idirect/ directory on your Protocol Processor
blade.
8. Enter the following commands in sequence to extract all the .bz2 files. (After entering
each command, a new command prompt displays.)
bunzip2 sarmt.bz2
bunzip2 sada.bz2
9. Enter the following commands in sequence to ensure the files you have extracted (sarmt
and sada) have execute permissions. (After entering each command, a new command
prompt displays.)
chmod 755 sarmt
chmod 755 sada
WARNING! The following step will cause a network outage.

10. Enter the following command to restart your iDirect services on the Protocol Processor
blade and allow the new executables to take effect:
service idirect_hpb restart
53
This completes the patch installation procedure. You are now ready to verify that the
installation was successful. Proceed to Verify Installation on Protocol Processor Blades.
Verify Installation on Protocol Processor Blades

Perform the following steps for each Protocol Processor blade to verify the version of the
software on the blades:
1. From iMonitor, enter the following command to telnet to the Protocol Processor blade:
> telnet <blade_IP_address> 13255
where:
blade_IP_address = IP address of the Protocol Processor blade
2. Enter the Username and Password when prompted.
3. From the samnc prompt, enter the following command to display a listing of all processes
running on the blade:
> proc list detail
This command produces output similar to the following partial output:
sada(2):
Up
Console Port: 13461
PID: 16867
NET: 1
remotes (2): X5.45 X5.78
sada(8):
Up
Console Port: 13462
PID: 16868
NET: 2
remotes (2): 5300.45602 5350.41523
sarmt(5):
Up
Console Port: 13464
PID: 16870
NET: 1
remotes (2): X5.45 X5.78
NET: 2
remotes (2): 5300.45602 5350.41523
4. Enter the following command to switch to a sarmt process displayed in the output in
Step 3:
> sarmt X;
where:
X = process number (in parenthesis after process name in listing)
54
5. Enter the following command to verify the version of the running process:
> version
Application: sarmt
Code Version: 10.0.1.5
Build Comment: Final_Build
Build Label: IDS-10.0.1.5-Build-9
The output should display the correct version (in this case 10.0.1.5) to the right of the
Code Version label.
6. Enter the following command to switch to a sada process displayed in the output in
Step 3:
> sada X;
where:
X is the process number (in parenthesis after process name in listing)
7. Enter the following command to verify the version of the running process:
> version
Application: sada
The output should display the correct version (in this case 10.0.1.5) to the right of the
Code Version label.
Installing iDX 2.0.1.4 Patch (Obsolete and Replaced by

iDX 2.0.1.6)
Note:

The iDX 2.0.1.4 remote patch corrects three specific issues, which are described in Bugs Fixed
in iDX 2.0.1.4 on page 29. This patch release consists of one Linux BSP package and one
remote image package for each remote model. This patch release also includes a sarmt
Protocol Processor patch. Table 8 lists the Linux BSP package files and remote package files
by remote model type.
Table 8. Cumulative Update and Remote Upgrade Packages for DX 2.0.1.4
Type of Remote
Linux BSP package
Remote Package
iNFINITI 3xxx
linux_2.4_bsp-10.0.1.4
remote_3XXX-10.0.1.4
linux_2.4_bsp-10.0.1.4
remote-10.0.1.4
Evolution X3 Remote
linux_2.4_bsp-10.0.1.4
evo_x3_rmt-10.0.1.4
Evolution X5 Remote
linux_2.4_bsp-10.0.1.4
evo_x5_rmt-10.0.1.4
Evolution 8 Series
linux_2.6_bsp-10.0.1.4
e8_rmt-10.0.1.4
55
Note:
All remote side bug fixes, enhancements and other code changes included in
iDX 2.0.1.1, iDX 2.0.1.2 and iDX 2.0.1.3 are also included in this iDX 2.0.1.4
patch.

your desktop.
Remote_iNFINITI).
server. Also copy the protocol processor image package.
Source Folders
Software Packages
Package
Size
e8_rmt-10.0.1.4.pkg
7,833
package
838
/home/nms/cfg/image_sets/linux_2.
6_bsp_package
Remote_Darwin_X3_X5
2,895
remote_package
Remote_Darwin_X3_X5
3,812
remote_package
Remote_Darwin_X3_X5
2,246
4_bsp_package
Remote_iNFINITI
remote_3XXX-10.0.1.4.pkg
2,648
3XXX_package
Remote_iNFINITI
remote-10.0.1.4.pkg
4,419
package
Remote_iNFINITI
2,246
4_bsp_package
56
Installing sarmt Protocol Processor Patch

To install the sarmt patch, perform the following:
2. Using WINSCP, copy the sarmt-10.0.1.4.gz file to the /usr/sbin/idirect
directory of the Protocol Processor blade.
3. Login to the Protocol Processor blade.
4. Backup the existing sarmt file by entering the following commands:
cd /usr/sbin/idirect
mv sarmt sarmt.backup
5. Extract the file and make it executable by entering the following commands:
gunzip sarmt-10.0.1.4.gz
mv sarmt-10.0.1.4 sarmt
chmod a+x sarmt
6. Restart the services by entering the following command (this causes a partial network
outage):
service idirect_hpb restart
7. Repeat the Steps 1 through 5 on all the other Protocol Processor blades.
Verifying sarmt Patch Installation

To validate that the sarmt patch is installed and running, perform the following steps:
1. From the Protocol Processor blade, telnet to the samnc process by entering the following
command:
telnet 0 13255
2. When prompted, log in as admin (password is "iDirect")
3. Enter the following command:
sarmt;
4. Display the version by entering the following command:
version -v
The following displays:
[sarmt(1:3)] admin@Internal:
> version
Application: sarmt
57
Verifying Patch Upgrade On Remotes

Verify that your remotes have been successfully upgraded to iDX Release 2.0.1.4 by Telneting
into the remote console and executing the version command. You should receive command
output similar to the following:
> version -v
Application: falcon

iDX 2.0.1.6)
The iDX 2.0.1.3 remote patch corrects two specific issues, which are described in Bugs Fixed
in iDX 2.0.1.3 on page 30, and corrects defects related to OpenAMIP operation, in which
mobile remotes communicate with controllable antennas. This patch consists of one Linux BSP
package and one remote image package for each remote model. Table 10 lists the Linux BSP
package files and remote package files by remote model type.
Table 10. Cumulative Update and Remote Upgrade Packages for iDX 2.0.1.3
Type of Remote
Linux BSP package
Remote Package
iNFINITI 3xxx
linux_2.4_bsp-10.0.1.3
linux_2.4_bsp-10.0.1.3
remote-10.0.1.3
Evolution X3 Remote
linux_2.4_bsp-10.0.1.3
evo_x3_rmt-10.0.1.3
Evolution X5 Remote
linux_2.4_bsp-10.0.1.3
evo_x5_rmt-10.0.1.3
Evolution 8 Series
linux_2.6_bsp-10.0.1.3
e8_rmt-10.0.1.3

your desktop.
Remote_iNFINITI).
58
server.
Source Folders (Remote
Software and iSite - iDX
2.0.1.x\Images\...)
Software Packages
Package
Size
e8_rmt-10.0.1.3.pkg
7,833
package
838
6_bsp_package
Remote_Darwin_X3_X5
2,894
remote_package
Remote_Darwin_X3_X5
3,812
remote_package
Remote_Darwin_X3_X5
2,246
4_bsp_package
Remote_iNFINITI
2,648
3XXX_package
Remote_iNFINITI
remote-10.0.1.3.pkg
4,419
package
Remote_iNFINITI
2,246
4_bsp_package
59

iDX 2.0.1.6)
The iDX 2.0.1.2 remote patch corrects defects related to OpenAMIP operation, in which
mobile remotes communicate with controllable antennas. This patch consists of one Linux BSP
package and one remote image package for each remote model. Table 12 lists the Linux BSP
package files and remote package files by remote model type.
Table 12. Cumulative Update and Remote Upgrade Packages for iDX 2.0.1.2
Type of Remote
Linux BSP package
Remote Package
iNFINITI 3xxx
linux_2.4_bsp-10.0.1.2
linux_2.4_bsp-10.0.1.2
remote-10.0.1.2
Evolution X3 Remote
linux_2.4_bsp-10.0.1.2
evo_x3_rmt-10.0.1.2
Evolution X5 Remote
linux_2.4_bsp-10.0.1.2
evo_x5_rmt-10.0.1.2
Evolution 8 Series
linux_2.6_bsp-10.0.1.2
e8_rmt-10.0.1.2

your desktop.
model type folders (i.e., Remote_Darwin_X3_X5, Remote_Evolution_e8series, and
Remote_iNFINITI).
60
server.
Source Folders (Remote
Software and iSite - iDX
2.0.1.x\Images\...)
Software Packages
Package
Size
e8_rmt-10.0.1.2.pkg
7,832
/home/nms/cfg/image_sets/e8_rmt
_package
838
/home/nms/cfg/image_sets/linux_2
.6_bsp_package
Remote_Darwin_X3_X5
2,894
/home/nms/cfg/image_sets/evo_x3
_remote_package
Remote_Darwin_X3_X5
3,811
/home/nms/cfg/image_sets/evo_x5
_remote_package
Remote_Darwin_X3_X5
2,246
.4_bsp_package
Remote_iNFINITI
2,647
/home/nms/cfg/image_sets/remote
_3XXX_package
Remote_iNFINITI
remote-10.0.1.2.pkg
4,419
/home/nms/cfg/image_sets/remote
_package
Remote_iNFINITI
2,246
.4_bsp_package
5. To download the Linux BSP packages, remote image packages, and to reset your remotes
using iBuilder, please see the chapter entitled, Upgrade Remotes in the Network
Upgrade Procedure Guide for iDX 2.0.1.x.
61
Installing iDX 2.0.0.3, 2.0.0.4, and 2.0.1

This section contains:
Bench Test Components and Folders in iBuilder
Downloading Required Files for iDX 2.0.x

The installation script for this release no longer prompts the user to install either a primary or
a backup NMS. Instead, the operator must add either a -primary or -backup flag to the
installation script command when installing the software on a primary or backup NMS.
If the installation script is run without any option flags (no -primary or -backup flag
specified) the help text for the installation script command displays instead:
# ./install_nms_servers.pl
USAGE: install_nms_servers.pl [-h] -primary|-backup|-uninstall
-h
- Help, display this usage statement.
-primary
- Target machine will be configured as a primary NMS server.
-backup
- Target machine will be configured as a backup NMS server.
-uninstall
- Uninstall all iDirect NMS RPMS.
After displaying the help text above, the script execution terminates without installing any
software. See the Network Upgrade Process Guide for iDX 2.0.x for complete details on
installing this release.
Bench Test Components and Folders in iBuilder

DO NOT modify or clone the Bench Test Spacecraft, Bench Test Inroute, or Bench Test
Outroute for your actual network configurations. These should only be used for testing
purposes. For your network configuration, please create new spacecraft, downstream, and
upstream carriers.
Downloading Required Files for iDX 2.0.x

To retrieve the software, access the TAC web page (located at: tac.idirect.net), click the
Software Releases and scroll down until you find iDX Release 2.0.x.
Upgrading from some previous versions to iDX 2.0.1 can require the application of some
special custom keys. Please refer to Special Custom Keys for iDX 2.0.1 Upgrade on page 3,
and to the Network Upgrade Procedure Guide for iDX 2.0.x for complete instructions.
62
63

RN ReleaseNotes iDX20xx Combined RevI 042911 PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

RN ReleaseNotes iDX20xx Combined RevI 042911 PDF

Enviado por

Direitos autorais:

Formatos disponíveis

Release Notes

For iDX Releases:

Document Name: RN_Release Notes_iDX 2.0.x.x_Combined_RevI_042911.pdf

iDX 2.0.x.x Release Notes

Reason for Change(s)

First release of document for iDX

Added known issue 22490.

Added known issue 22972.

Added known issue 22507.

Added bugs and installation

Added Known Issue 21944.

Added bugs and installation

Added known issue 24844.

iDX 2.0.x.x Release Notes

iDX 2.0.x.x Release Notes

About This Guide

Optional iDX 2.0.1.3 Patch ................................................................ 2

Optional iDX 2.0.1.2 Patch ................................................................ 2

Upgrading e8350/e800 Remotes at Pre-iDX 1.1 Versions ........................... 2

Change to MIR and CIR Bandwidth Calculation [20486] .............................. 4

iDX 2.0.x.x Release Notes

Modified Installation Script Behavior [20158] ......................................... 5

New Features and Enhancements in iDX 2.0.1.1 ..................................... 7

New Features and Enhancements in iDX 2.0.1 ........................................ 8

Supported Network Topologies ......................................................... 10

Existing Hardware Support .............................................................. 12

Hardware Not Supported ................................................................. 14

iDX 2.0.x.x Release Notes

Enhanced Information Rate (EIR) Configuration ................................................. 17

Use of IP Data Rates in Configuring CIR/MaxIR ...................................................

System Enhancements in iDX 2.0 ....................................................... 20

Bugs Fixed in iDX 2.0.1.5 ................................................................ 29

Bugs Fixed in iDX 2.0.1.4 ................................................................ 29

iDX 2.0.x.x Release Notes

Bugs Fixed in iDX 2.0.1.3 ................................................................ 30

Bugs Fixed in iDX 2.0.1.2 ................................................................ 31

Bugs Fixed in iDX 2.0.1.1 ................................................................ 32

Bugs Fixed in iDX 2.0.1 ................................................................... 33

iDX 2.0.x.x Release Notes

Bugs Fixed in iDX 2.0.0.4 ................................................................ 38

Bugs Fixed in iDX 2.0.0.3 ................................................................ 39

iDX 2.0.x.x Release Notes

NMS/Reporting Issues ..................................................................... 46

iDX 2.0.x.x Release Notes

1. Pre-iDX 2.0 and iDX 2.0 Rate Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

iDX 2.0.x Release Notes

iDX 2.0.x Release Notes

About This Guide

Contents Of This Guide

iDX 2.0.x.x Release Notes

About This Guide

Used when the user is

Used when showing

Output similar to the following sample appears:

Used when the user is

1. If you are adding a remote to an inroute group,

Used when specifying

Used to show all

For instructions on adding an iSCPC line card to the

Used when the user needs

Several remote model types can be

WARNING! The following procedure may cause

iDX 2.0.x.x Release Notes