RN iDX 2121 RevG 030411

Release Notes
For iDX Releases:

2.1.0
2.1.1
2.1.2
2.1.2.1
March 4, 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_ReleaseNotes_iDX_21x_Rev G_030411.pdf

Document Part Number: T0000293
ii
iDX Release Notes 2.1.x
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?
05/28/10
Initial release of document for

iDX Release 2.1
EHoffman
06/14/10
Added minor changes/corrections EHoffman
06/23/10
Added known issue 22490
EHoffman
08/09/10
Update for Release 2.1.1
JVespoli
11/30/10
Consolidated for 2.1.0 and 2.1.1
EHoffman
12/13/10
Update for Release 2.1.2
TJenkins
03/04/11
Update for Release 2.1.2.1
TTheus
iii
iv
Contents
About This Guide

Purpose ....................................................................................... xi
Intended Audience ......................................................................... xi
Contents Of This Guide .................................................................... xi
Document Conventions ................................................................... xii
Related Documents ....................................................................... xiii
Getting Help ............................................................................... xiii
Supported Hardware and Features

Supported Remotes and Line Cards ...................................................... 1
Supported NMS and PP Servers ........................................................... 1
Supported System Modulation and Coding (MODCOD) ................................ 2
Supported Features ......................................................................... 3
Supported NMS Client Operating Systems .............................................. 3
Supported Upgrade Paths .................................................................. 3
New Features & Enhancements

New Features and Enhancements in iDX 2.1.2.1 ..................................... 5
New Features and Enhancements in iDX 2.1.2 ........................................ 6
Latency Improvement Implemented in iDX 2.1.2 ....................................................... 6
Latest Operating System and Database Support ....................................... 6

RedHat Enterprise Linux 5.4 Support ..................................................................... 6
MySQL 5.1.45 Support ....................................................................................... 6
Security Enhancements .................................................................... 6
Telnet Command Change Due to Upgrade of Busybox ................................................. 6

Strengthened Security for root Access to Servers ...................................................... 6
Scalability and PPS Enhancements ....................................................... 7

Licensing Support for Encryption and TRANSEC on Protocol Processor Blades . 7
Group QoS Enhancements ................................................................. 7
Remote Service Groups ..................................................................................... 7
GQoS Cost Precision Improvement ........................................................................ 8
Roaming Remote Enhancements ......................................................... 8

Edit All Instances of Roaming Remotes ................................................................... 8
Other Feature Improvements ............................................................. 8

Redesigned Backup and Restore Procedures ............................................................ 8
Enhanced Sat Traffic Graph Options ...................................................................... 8
Continuous Monitoring of Mapserver Process ............................................................ 9
Bug Fixes
Bugs Fixed in iDX 2.1.2 ................................................................... 11
Operation Affecting Issues ................................................................................ 11
24155 Number of Configured Beams Limited for ABS Remotes ...................................... 11
24147 TCP Compression on X5 May not Function Properly via DFOE ............................... 11
23689/23695 Low Demand Causes Upstream Jitter on Congested Networks ...................... 12
NMS/Reporting Issues ...................................................................................... 12
23046 iMonitor Report Restrictions Dialog Too Many Messages Requested ..................... 12
23668 idsRestore Does Not Convert Legacy QoS to GQoS Properly ................................. 12
23669 Service Levels Missing From Options Files After Upgrade to iDX 2.1.1 ..................... 12
23670 UDP Push Does Not Work in Global NMS Environment ........................................ 12
23701 Changing Remote from iNFINITI to Evolution Sets GPS Input Incorrectly .................. 12
23758 Some Specific Service Levels May Be Deleted from Application Profiles if NMS Services Are
Restarted ............................................................................................. 12
23815 When Retrieving Options from Modem Using iSite, the Options File May Not Display Properly
in Notepad ........................................................................................... 13
Bugs Fixed in iDX 2.1.1 ................................................................... 13

22632 Downstream GQoS ID is Zero in Options File for Newly-Created Remotes ................. 13
22670 ABS Remote Incorrectly Requests New Map when Valid Map is Loaded .................... 13
22811 Error in crontab.templates Can Cause Backup and Restore to Fail ......................... 13
22989 Evolution Remote with Spectral Inversion on its Uplink May Take Longer to Acquire ... 14
23054 Evolution X3 and X5 Remotes Lock Up at Temperatures Below 15oC ...................... 14
23167 Excessive Jitter on VoIP Calls During Upstream Congestion ................................. 14
21179 iMonitorMultiple Changes to VNO Access Rights Forces Multiple Acknowledgments by VNO
Users .................................................................................................. 14
21709 iBuilderRemote MIR or CIR Cannot Be Set Higher than the Information Rate of the Network
vi
or Inroute Groups ................................................................................... 15

22473 iBuilderModify All Instances Does Not Modify Downstream MIR ........................ 15
22476 iMonitorMulticast Bytes Not Displayed in SAT Downstream Tab ........................... 15
22519 iBuilderClicking Service Profile in Service Profile-Remote View Adds Replica of Remotes
15
22520 Upstream MIR/CIR setting for Virtual Remote Not Based on IP Data Rate in All Cases .. 15
22525 iBuilderHNO Cannot Modify Visibility of Reflector Components for VNO ................ 16
22531 iMonitorDisplays Incorrect MODCOD Values Under Control Panel QoS Tab .............. 16
22532 iMonitorX3/X5 Remote Statistics Not Displaying in Data Snapshot Window ............. 16
22543 iMonitorIncorrect Value for SAT Traffic When Using Symbol Button ..................... 16
22546 iMonitorClicking View Stats after Selecting Route in Protocol Layer Field Does Not
Display Data ......................................................................................... 16
22658 iBuilderApplying Configuration to Multiple Remotes Causes iBuilder to Exit ............ 16
22697 SNMP OID for TDM Loss Increments Incorrectly ................................................ 17
22778 iBuilderProblem When Assigning Receive Carrier to TxRx Line Card ..................... 17
23016 iMonitorControl Panel Data Takes a Long Time to Load .................................... 17
Bugs Fixed in iDX 2.1.0 ................................................................... 18

22404 Unsupported Characters When Defining Beam Map Names .................................. 18
22277 Maximum Broadcast bps Calculated from Symbol Rate ....................................... 18
22210 SCPC Errors Generated on iNFINITI Remotes when Using Combination of 8PSK and Certain
Frequency Range .................................................................................... 18
22182 Protocol Processor and Remotes Cannot Pass ICMP Packets with Invalid Checksum ..... 19
22188 Problem with Line Card Upgrades ................................................................ 19
22156 Beamselector Lists Wrong Beam Number after Beam Number Changed ................... 19
22051 Sporadic Link Layer Bounces on Multiple Networks and Multiple Remotes ................ 19
21927 ICMP Header Processing Error on Protocol Processor-VLAN Interface ...................... 20
21904 Round-Robin Order for Trying Beams Not Fair In Mapless Mode ............................. 20
21879 Remote Causing Downstream Congestion ....................................................... 20
21588 Console ipstats Command Produces Negative Values in Long Term Bandwidth Report .. 20
21571 keepalive Interval from Modem to Antenna Does Not Take Effect Immediately ......... 21
21508 iBuilderNewly Created Remote Set Upstream QoS Profile to Default .................... 21
21391 DFOE Traffic Sent Over Clear Channel .......................................................... 21
20259 Maximum Information Rate Not Enforced in Carrier Grooming Mode ...................... 21
20057 samnc Process Utilizes 100% of CPU During Network Options File Reload ................. 21
17912 SNMP Server Stops Sending Messages and Needs Restarting ................................. 21
22390 iMonitorRemote Status Displays Inconsistent for Roaming Remotes Activated in Multiple
Networks ............................................................................................. 22
22201 iBuilderModify All Instances on Roaming Remote after Updating Properties Not Allowed
22
22174 iBuilderUpstream MIR/CIR Setting for Virtual Remotes Not Based on IP Data Rate .... 22
22165 iMonitorUCP and Remote Status Events Missing ............................................. 22
22125 Mobile Remote latlong_timeout Values Below 120 Seconds Not Supported ............... 22
22099 iMonitorIncorrect Display of MODCOD for Remotes ......................................... 23
22090 iBuilderUpstream Filter Rule Modification Not Reflected in Options File ............... 23
22076 iMonitorLine Card CRC Errors Show Up as RCM Fault Warning Type in Conditions Log 23
vii
22007 iMonitorQoS Statistics for BW Requested and BW Allocated Data Displaying in Wrong Columns .................................................................................................. 23
21931 iMonitorSat Traffic Graph Historical Report Not Working .................................. 23
21912 iMonitorIncorrect Reporting of CPU Usage .................................................... 23
21834 iBuilderChanging Remote Site Notes Caused Configuration Changes at Both Hub Side and
Remote Side ......................................................................................... 24
21685 iMonitorIP Graph Displays Incorrect Time Scale ............................................. 24
21588 iMonitorIP Statistics Display as Negative Values in Long Term Bandwidth Report ..... 24
21589 iBuilderNMS Does Not Allow Creation of VLAN With /28 Subnet .......................... 24
21513 iMonitorSNMP Server MIB Missing DVB-S2 Statistics .......................................... 24
21494 iBuilderVNO Users with No Ownership of Network Can View Changes ................... 25
21468 iMonitorCommunication Problem Between Chassis and NMS .............................. 25
21418 iBuilderControl and Visibility Issues with VNOs .............................................. 25
21305 iBuilderVNO Protocol Processor Blade Visibility Not Limited .............................. 25
21181 iBuilderCarrier Visibility for VNO Users Not Limited ........................................ 25
21182 iBuilderVNO Sees Newly Added Remote As Only Visible Not Owned ................ 26
10563 iBuilderCarriers with Symbol Rates Lower than 64 Ksps Prohibited ...................... 26
Known Issues
Known Issues in iDX 2.1.x ................................................................ 27
23984 X5 May Exhibit Degraded SNR Performance in iNFINITI mode ............................... 27
24216 Revision Server is Disabled for VNO Super User Even Though Network Owned Permission is
Given ................................................................................................. 28
22425 Evolution Antenna Pointing Not Scaled for Lower MODCODs ................................ 28
22254 Spurious RCM Alarms Reported in Daisy-Chain Chassis Configuration ...................... 28
22217 Mapserver Process Does Not Rebind to Port 5003 If Restarted .............................. 28
24157 iBuilderIn Modify all Instances Option, Multicast Tab Gets Greyed Out After Adding One
Multicast IP Address ................................................................................ 28
22548 iBuilderAllows Priority Field To Be Left Blank On Remote QoS Tab ...................... 29
22507 iBuilderDVB-S2 Fast Fade Configuration Changes Do Not Update Options File .......... 29
22421 iMonitorDisabled Warnings Display In Blade Info Window .................................. 29
22334 iMonitorQoS Options On Remote Control Panel Do Not Show CIR Enabled .............. 29
21503 Global and Local Group with Same Name in Options File Causes Remote to Behave Unexpectedly .............................................................................................. 30
21274 iMonitorTimeplan Graph Shows Allocated Slots in Free Slot Column ..................... 30
21160 iBuilderConfiguration Server and Chassis Manager Lose Synch After Failing to Apply . 30
20822 iMonitorRx Power Not Displayed In eM1D1 TxRx Standby Line Card ...................... 31
20196 iMonitorPower Setup in Cross Polarization Portion of Probe Can Go Below -40 dBm .. 31
20148 iBuilderAll Remotes and Applications Disappear In Application Based Mode When New Application Added ..................................................................................... 31
23107 iMonitorControl Panel Does Not Load After Upgrade to iDX 2.1 ........................... 31
23155 iMonitorRoaming Remote MODCOD Toggles on the SAT Traffic Graph ................... 32
21735 iMonitorRemote Availability Sometimes Inaccurate When Viewed for Multiple Remotes .
32
viii
Known Issues in iDX 2.1.0 Only ......................................................... 33

22490 Map-based ABS Remote with Serial NMEA Input Operating in Western Hemisphere may Operate in Mapless Mode ............................................................................. 33
22632 Downstream GQoS ID is Zero in Options File for Newly-Created Remotes ................. 33
22989Evolution Remotes with Upstream Spectral Inversion May Take Longer to Acquire ...... 34
23054 Evolution X3 and X5 Remotes Lock Up at Temperatures Below 15oC ...................... 34
23167 Excessive Jitter on VoIP Calls During Upstream Congestion ................................. 34
22546 iMonitorClicking View Stats after Selecting Route in Protocol Layer Field Does Not
Display Data ......................................................................................... 34
22525 iBuilderHNO Cannot Modify Visibility of Reflector Components for VNO ................ 35
22519 iBuilderClicking Service Profile in Service Profile-Remote View Adds Replica of Virtual Remotes ................................................................................................. 35
22473 iBuilderModify All Instances Does Not Modify Downstream MIR ........................ 35
22476 iMonitorMulticast Bytes Not Displayed in SAT Downstream Tab ........................... 35
22543 iMonitorIncorrect Value for SAT Traffic When Using Symbol Button ..................... 35
22532 iMonitorX3/X5 Remote Statistics Not Displayed in Data Snapshot Window .............. 35
22778 iBuilderProblem When Assigning Receive Carrier to TxRx Line Card ..................... 36
22531 iMonitorDisplays Incorrect MODCOD Values Under Remote QoS Tab ..................... 36
Installation Instructions
Installing iDX Release 2.1.x .............................................................. 37
Downloading Required Files for iDX Release 2.1.x .................................................... 37
Installation Notes .......................................................................... 37

Maintaining Pre-iDS 8.x Compatibility ................................................................... 37
Service Level Changes after QoS Conversion ........................................................... 37
Copying Daily Backup Files ................................................................................ 38
ix
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.
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:
Supported Hardware and Features
New Features & Enhancements
Bug Fixes
Known Issues
xi
Document Conventions
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.
xii
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.
Related Documents
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 Release 2.1.x
Network Upgrade Procedure Guide from iDX Release 2.1.0 to 2.1.x
iDX Release 2.1 iBuilder User Guide
iDX Release 2.1 iMonitor User Guide
iDX Release 2.1 Technical Reference Guide
iDX Release 2.1 Satellite Router Commissioning & Installation Guide
iDX 2.1 iDirect Features & Chassis Licensing Guide
iDX Release 2.1 Upgrade/New Installation Survey
iDX 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.
xiii
Getting Help
xiv
Supported Hardware and

Features
This chapter details the supported hardware and feature set for iDX Release 2.1.x, along with
supported upgrade paths. The following sections are included:
Supported Remotes and Line Cards
Supported NMS and PP Servers
Supported System Modulation and Coding (MODCOD)
Supported Features
Supported NMS Client Operating Systems
Supported Upgrade Paths
Supported Remotes and Line Cards

iDX Release 2.1 supports all existing iNFINITI and Evolution line cards and remotes. Refer to
the Hardware Matrix table on the TAC web page for full details.
Note:
NetModem II and NetModem II+ remotes and line cards are not supported in this
release.
Supported NMS and PP Servers

To provide greater choice and flexibility to customers, iDirect now supports the following NMS
and Protocol Processor servers to run iDX Release 2.1 with Red Hat Enterprise Linux 5.4:
Dell PowerEdge 1950 III
Dell PowerEdge R610
Augmentix A+R200
IBM x336 eServer
IBM x3550 eServer
Note:
The IBM x335 and the IBM x330 eServers are no longer supported in this
release.

System MODCOD requirements as first defined in iDX 1.1, are fully supported and tested in iDX
Release 2.1. The DVB-S2 outbound carrier utilizes the following modulation and coding
combinations:
Table 1. DVB-S2 OutBound MODCODs
Downstream
QPSK 1/4, 1/3, 2/5, 1/2, 3/5, 2/3, 3/4, 4/5, 5/6, 8/9
MODCOD
8PSK 3/5, 2/3, 3/4, 5/6, 8/9
DVB-S2
16APSK 2/3, 3/4, 4/5, 5/6, 8/9
The iDirect SCPC outbound is capable of utilizing the following modulation and coding
combinations:
Table 2. 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
CAUTION: The BPSK-0.431 (BPSK with FEC of 0.431) downstream carrier configuration
is not supported in iDX Release 2.1. If you are using BPSK-0.431 you must change the
carrier prior to upgrading.
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 3. TDMA 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
Supported Features
Supported Features
All major feature sets (except as noted) of existing iNFINITI and Evolution platforms are
supported in this release.
Note:
For a listing of major supported features across major software releases, refer
to the Software Matrix table which can be found on the TAC web page.
The new features introduced in this release are summarized below:
Latest Operating System and Database Support
Security Enhancements
Licensing Support for Encryption and TRANSEC on Protocol Processor Blades
Group QoS Enhancements
Roaming Remote Enhancements
Other Feature Improvements
The following features are not supported:
Mesh
iSCPC
Note:
For more details on new features introduced in iDX Release 2.1, refer to the
New Features & Enhancements chapter on page 5.
Supported NMS Client Operating Systems

iDX Release 2.1 clients are now supported on the following platforms:
Windows 7 (new for iDX Release 2.1)
Windows XP
Windows 2000 (Service Pack 3 or later)

You can directly upgrade to iDX Release 2.1.2.1 from the following releases:
iDS 6.0.9.7
iDS 7.0.8
iDS 7.1.2
iDS 8.0.1
iDS 8.0.2.1
iDS 8.0.2.7
iDS 8.3.x
iDX 1.0.x
iDX 1.1
iDX 2.0.x
New Features &

Enhancements
iDX Release 2.1 features a complete operating system and database upgrade, along with
numerous security enhancements. Encryption functionality and licensing are now software
controlled. Group QoS is enhanced to include Remote Service Groups, while the roaming
remote feature is improved to allow simultaneous editing of all remote instances. The VNO
feature is also improved to enhance control, visibility and performance.
This chapter includes the following:
New Features and Enhancements in iDX 2.1.2.1
New Features and Enhancements in iDX 2.1.2
Scalability and PPS Enhancements
Licensing Support for Encryption and TRANSEC on Protocol Processor Blades
New Features and Enhancements in iDX 2.1.2.1

This section discusses the RedHat and MySQL enhancements included in iDX Release 2.1.2.1.
RedHat Enterprise Linux 5.6 Support

iDX 2.1.2.1 includes a RedHat Enterprise Linux upgrade from RHEL 5.4 to RHEL 5.6. Since
RHEL 5.6 t is installed when you upgrade to iDX 2.1.2.1, the RHEL upgrade is transparent to
you and to your customers.
MySQL 5.1.46 Support

Also included in iDX 2.1.2.1, is an upgrade to MSQL 5.1.46. As with RHEL 5.6, MySQL 5.1.46 is
installed when you upgrade to iDX 2.1.2.1.
This database engine upgrade is designed to be transparent to you and to your customers.
However, if you (or they) have customized your current MySQL database, you may experience
some incompatibility issues. There is a preUpgradeCheck procedure that you can use to
detect these issues. Refer to the iDirect iDX 2.1.2.1 Upgrade/New Installation Survey for
more information.

Latency Improvement Implemented in iDX 2.1.2
On releases iDS 8.2 and later, it was observed that overall latency was higher by 40 to 70 msec
depending on the network condition. Several improvements are implemented to reduce the
overall latency and jitter in iDX Release 2.1.2.

This section discusses the RedHat and MySQL enhancements included in iDX Release 2.1.
RedHat Enterprise Linux 5.4 Support

iDX Release 2.1 is designed to run on Red Hat Enterprise Linux 5.4 (RHEL 5.4). iDX Release 2.1
will not operate on any previous RedHat releases. Servers which are running previous RHEL
releases must be upgraded to RHEL 5.4. RHEL 5.4 brings together innovations, patches, and
security enhancements. RHEL 5.4 includes the capability to continually update the operating
system with future patches or upgrades.
MySQL 5.1.45 Support

The RHEL upgrade enables support for the MySQL 5.1.45 release.
This section describes additional security enhancements implemented in iDX Release 2.1.
Telnet Command Change Due to Upgrade of Busybox

As part of the Linux OS upgrade, iDirect is also upgrading the Busybox process on all remotes.
The telnet 0 command to login to the remote console is changed to telnet 0.0.0.0 due
to this busybox upgrade.
Strengthened Security for root Access to Servers

For iDX Release 2.1 and above, secure shell login (ssh) or secure copy (scp) using root user is
prohibited due to security considerations. Users can now obtain administrative access through
the newly defined user name idirect created for this purpose.
For complete instructions on installing and upgrading to iDX Release 2.1, please refer to the
iDX Network Upgrade Procedure Guide for 2.1.

iDX Release 2.1 has been developed to meet specific scalability requirements, such as
supporting up to 5,000 remotes in a single network. Additionally, support for up to 10,000
virtual remotes is a design goal for this release.
iDX Release 2.1 also includes software optimizations that are designed to yield a 10% to 15%
improvement in packet-per-second (PPS) performance across all iNFINITI and Evolution
remotes. System performance and scalability characterization testing of iDX Release 2.1 is
well underway and will complete in approximately 4-6 weeks after the release date. Data
based on preliminary tests conducted so far is promising and there is a good chance the PPS
performance improvement could exceed the design goal.
Specific test scenarios and results will be published when completed.
Licensing Support for Encryption and TRANSEC on

Protocol Processor Blades
With iDX Release 2.1, Encryption and TRANSEC support can now be enabled on each individual
Protocol Processor blade through a software license. By default, Encryption and TRANSEC
support on a Protocol Processor is disabled. The HiFN card no longer participates in the
encryption process with this release and is no longer required to enable the Encryption
feature. You must obtain an Encryption license to enable this feature whether you have been
using a HiFN card or not.
Note:
For IBM x3550 eServers currently installed with a HiFN card, the HiFN card
interface must be disabled prior to upgrade. For details refer to the
iDX Network Upgrade Procedure Guide for 2.1.
WARNING! x3550 Protocol Processors with HiFN cards may not boot properly after
upgrade if all required interfaces are not disabled as detailed in the iDX Network
Upgrade Procedure Guide for 2.1.

This section describes enhancements to the Group QoS (GQoS) feature.
Remote Service Groups

Remote Service Groups are new to iDX Release 2.1, and allow remotes to retain their QoS
configuration when moving between networks. Each remote is configured with its own QoS
properties such as MIR and CIR and independently allocates its bandwidth to its Applications.
The bandwidth for the Remote Service Group is partitioned first among the physical remotes,
after which each physical remotes bandwidth is partitioned into Application bandwidth.
Note:
For complete information, please refer to the iBuilder User Guide for iDX 2.1
and the iDX Release 2.1Technical Reference Guide.
GQoS Cost Precision Improvement

In order to facilitate the crafting of differentiated services by operators, the current cost
range for GQoS cost precision (0.000 to 1.000) has been replaced with a new 5 decimal place
cost precision (0.00001 to 1.00000), providing 100,000 unit cost weighting.

Edit All Instances of Roaming Remotes
To more conveniently modify all instances of roaming remotes, a new Modify All Instances
option is added to the right-click menu for remotes on the iBuilder tree (Figure 1).
Figure 1. Modify All Instances Selection

Selecting this option selects all instances of a remote (across all networks) for a group edit in
the Modify Configuration Object dialog box.
See the Configuring Remotes chapter of the iBuilder User Guide for iDX 2.1 for complete
details.

Redesigned Backup and Restore Procedures
In order to harden security on all iDX Release 2.1 servers, the entire backup and restore
process is redesigned. For complete instructions on backup and restore procedures for
iDX Release 2.1, please refer to the Technical Note NMS Redundancy and Failover for iDX
Release 2.1 and Later.
Enhanced Sat Traffic Graph Options

When selecting Bits (Kbps) or Bytes (KBps), the actual satellite bandwidth consumed on an
ACM carrier varies at any given data rate depending on which MODCODs are being transmitted
at the time. A new Symbol button has been added to the Sat Traffic graph button panel,
replacing the old Scale button. Clicking the Symbol button allows you to view the total
satellite traffic in kilosymbols per second, which is independent of the MODCODs being
transmitted.
Figure 2. Symbol ButtonSat Traffic Graph Button Panel

The Symbol button applies only to the Downstream graph for DVB-S2 ACM networks. If the
Symbol button is selected, the Y axis shows the satellite traffic in kilosymbols per second.
Continuous Monitoring of Mapserver Process

The nms_monitor process was not monitoring the mapserver process in previous releases. Now
the nms_monitor process automatically restarts the mapserver process whenever the
mapserver is not running.
10
Bug Fixes
This chapter lists all bugs that are fixed in iDX 2.1.2, iDX 2.1.1, and iDX 2.1.0. All bugs fixed in
previous iDX 2.1.x releases are also fixed in this release.
This chapter contains the following major sections:
Bugs Fixed in iDX 2.1.2 on page11
In each 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)
Bugs Fixed in iDX 2.1.2

Operation Affecting Issues
24155 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.
Fixed in this release.
24147 TCP Compression on X5 May not Function Properly via DFOE

On iDX 2.1, when the TCP compression feature is enabled on X5 remotes, it is
expected that the Dynamic Features and Options Exchange (DFOE) feature should
push the change to X5 remotes on the fly. However, it was discovered that this was
not happening properly for X5 remotes.
11
23689/23695 Low Demand Causes Upstream Jitter on Congested Networks

In certain cases in congested networks, in previous releases, certain voice and fax
applications could experience degraded performance due to jitter on the upstream
caused by inaccurate slot allocation.
NMS/Reporting Issues
23046 iMonitor Report Restrictions Dialog Too Many Messages Requested
A design change for the purposes of scalability resulted in customers not being to get
the Remote Availability Report when requested for 250 or more remotes. Instead, a
dialog displayed too many messages requested. This restriction has been removed
and the software behaves as in pre-iDX 2.1 releases.
23668 idsRestore Does Not Convert Legacy QoS to GQoS Properly

When using idsRestore to upgrade from iDS 7.0.x to iDX 2.1.1 and selecting -gqos RMT
for Group QoS conversion, it was observed that the upgraded remotes incorrectly had
spoofing disabled for all reliable (TCP) service levels.
23669 Service Levels Missing From Options Files After Upgrade to iDX 2.1.1
After upgrading to iDX 2.1.1, it was observed that all GQoS profiles were missing at
least one service level. While service levels were displayed properly in iBuilder when
viewing the Application Profile, the actual options files were missing some service
level information.
23670 UDP Push Does Not Work in Global NMS Environment

When upgrading to iDX 2.1.1 and attempting to do a UDP Push of options files in a
Global NMS environment, the UDP Push did not work properly. When attempting to do
a UDP push of options files, the NMS only sent to the multicast group address and did
not attempt to proxy through the PP blade while the system was in upgrade mode.
23701 Changing Remote from iNFINITI to Evolution Sets GPS Input Incorrectly
When changing an existing mobile remote from iNFINITI 5xxx to X5 in iBuilder, the
gps_device defaults to ttyS0 instead of socket and also changes dedicated_port key to
ixp1.
23758 Some Specific Service Levels May Be Deleted from Application Profiles if
NMS Services Are Restarted
Due to a mistake in the script controlling NMS services, certain service levels in the
Application Profiles may be deleted if NMS services are restarted.
12
23815 When Retrieving Options from Modem Using iSite, the Options File May Not
Display Properly in Notepad
When retrieving an options file from a remote modem using iSite, the retrieved
options file was unreadable in Notepad.

22632 Downstream GQoS ID is Zero in Options File for Newly-Created Remotes
When creating a new remote in iBuilder in iDX 2.1.0, if you selected the QoS tab and
assigned one direction (upstream or downstream) to a Service Profile and the other
direction to a Remote Profile, then the gqos_id in the hub-side options file was
incorrectly set to zero. This resulted in the remote being unable to come into the
network.
This only happened if the profile assignments were made while creating the remote.
It did not happen if the profile assignments were made by modifying an existing
remote.
22670 ABS Remote Incorrectly Requests New Map when Valid Map is Loaded
This problem only affected remotes using the iDirect Automatic Beam Selection (ABS)
feature to receive GPS data over the serial port using the NMEA protocol. The
problem did not affect ABS remotes using other protocols to receive GPS data or when
using the LAN port.
If the remote was operating in the western hemisphere, a problem in the remote
embedded software caused the remote to misinterpret the GPS data and therefore to
miscalculate its current geographic location. This miscalculation caused the remote
to continuously request a new map from the NMS mapserver and to operate in
mapless mode even when the remote had already received a valid map.
22811 Error in crontab.templates Can Cause Backup and Restore to Fail

In iDX Release 2.1.0, an error in the crontab.templates file could result in an
incorrect crontab file on the NMS server when the template file contents were copied
to the crontab file. The resulting incorrect crontab file could then cause the failure of
daily backup and restore of the NMS databases.
13
22989 Evolution Remote with Spectral Inversion on its Uplink May Take Longer to
Acquire
An issue was found in the Evolution remote software which caused incorrect
calculation of the remotes frequency offset when its uplink (Tx) was spectrally
inverted. This caused Evolution remotes to take longer than usual (as much as one
hour) to acquire into the network under certain conditions.
Affected Products:
Evolution X3, X5, e8350, e800, and e850mp operating in DVB-S2s networks
Evolution X5 remotes operating in SCPC networks
Note:
iNFINITI remote model types were not affected by this issue.
23054 Evolution X3 and X5 Remotes Lock Up at Temperatures Below 15oC

In iDX Release 2.1.0, on rare occasions, the processor on Evolution X3 and X5 Remote
Modems locked up at temperatures below ~15oC. This problem only affected X3 and
X5 remotes receiving DVB-S2 downstream carriers. It did not affect remotes receiving
SCPC carriers.
When the problem occurred, the remote LEDs remained constant and no response was
seen from the console or LAN ports. A power cycle was required to recover the
modem.
23167 Excessive Jitter on VoIP Calls During Upstream Congestion

In earlier releases, VoIP calls sometimes experienced jitter when the upstream carrier
was congested. This occurred even though the VoIP Application had higher priority
than other traffic and therefore should have been granted sufficient bandwidth for
the calls. In iDX Release 2.1.1, the bandwidth allocation algorithm has been adjusted
to fix this issue.
21179 iMonitorMultiple Changes to VNO Access Rights Forces Multiple
Acknowledgments by VNO Users
In some earlier releases, if an HNO user made multiple changes to a VNOs visibility
and/or permission settings in iBuilder, a VNO user logged on to iBuilder or iMonitor
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. This bug was fixed in iDX 2.1.0 for
iBuilder users but it was not fixed for iMonitor users.
With this release, the VNO iMonitor 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.
14
21709 iBuilderRemote MIR or CIR Cannot Be Set Higher than the Information
Rate of the Network or Inroute Groups
In previous releases, iBuilder did not allow the operator to set the Maximum
Information Rate (MIR) or Committed Information Rate (CIR) on the Remote QoS tab
to a value higher than the information rate of the carrier. Therefore, if a remote was
moved to a network or inroute group with carrier information rates lower than the
remotes CIR/MIR, the Network Operator was forced to reconfigure the remotes
CIR/MIR. In this release, iDirect has removed this constraint in order to facilitate
mobility of remotes between networks and inroute groups with different information
rates.
22473 iBuilderModify All Instances Does Not Modify Downstream MIR

In iDX 2.1.0, on occasion, selecting the Modify All Instances option when rightclicking a remote in the iBuilder tree did not modify the Downstream MIR for all
instances.
22476 iMonitorMulticast Bytes Not Displayed in SAT Downstream Tab

In iDX 2.1.0, although downstream multicast traffic transmitted was correctly
displayed on the SAT Traffic graph, in some cases the multicast bytes were not shown
in Multicast column of the SAT Downstream tab of the SAT Traffic graph.
22519 iBuilderClicking Service Profile in Service Profile-Remote View Adds

Replica of Remotes
In iDX 2.1.0, clicking a Service Profile in the Service Profile-Remote View of the Group
QoS Tab for a Network or Inroute Group visually added replicas of all remotes assigned
to the Service Profile. This was a display issue only and had no impact on actual
configuration. However, modifying or deleting any of the duplicate Remotes displayed
in the Service Profile-Remote View affected the actual Remote Service Profile
assignments.
For example, deleting any of the duplicate Remotes would remove the actual Remote
from the Service Profile. Clicking OK could then leave the Remote with no Service
Profile assignment and change it to the Deactivation Pending state.
22520 Upstream MIR/CIR setting for Virtual Remote Not Based on IP Data Rate in
All Cases
In iDX 2.0, satellite overhead added by the system was not included in MIR and CIR
calculations when overriding Application Properties on Virtual Remotes in the Service
Profile View of the Group QoS tab of a Network or Inroute Group. Therefore, the MIR
and CIR configured for Virtual Remotes were not based on IP Data Rate, making those
calculations inconsistent with other configured MIR and CIR calculations.
Most cases of this bug were fixed in iDX 2.1.0. However, in iDX 2.1.0 there was one
specific configuration which still did not calculate MIR/CIR properly. In an Application
Service Group, if a remote was in remote-based mode, and MIR/CIR were assigned to
15
the Virtual Remote, the satellite overhead was added twice, resulting in allocation of
slightly more bandwidth than configured.
This final case has been fixed in this release.
22525 iBuilderHNO Cannot Modify Visibility of Reflector Components for VNO

Reflector components have default visibility once they are created by the HNO. In iDX
2.1.0, if this visibility was removed, and the reflector component was assigned to a
remote, the HNO was unable to re-enable visibility.
22531 iMonitorDisplays Incorrect MODCOD Values Under Control Panel QoS Tab
In some earlier releases, the Minimum MODCOD, Nominal MODCOD and Maximum
MODCOD for X5 and e8350 DVB-S2 remotes were all displayed as QPSK-1/4 on the
iMonitor Control Panel QoS tab regardless of how these values were configured in
iBuilder.
22532 iMonitorX3/X5 Remote Statistics Not Displaying in Data Snapshot Window

In some earlier releases, for X5 and X3 remotes in DVB-S2 networks, attempting to
display the Rx Composite Power and Tuner AGC Gain values in the Data Snapshot
display resulted in N/A appearing for these two statistics. For e8350/mp850
remotes, this data was displayed as expected.
22543 iMonitorIncorrect Value for SAT Traffic When Using Symbol Button
In iDX 2.1.0, when you selected the Symbol Button for downstream traffic on the SAT
Traffic graph for multiple remotes, incorrect symbol rates were sometimes displayed.
The Symbol Button worked correctly when selecting a single remote.
22546 iMonitorClicking View Stats after Selecting Route in Protocol Layer

Field Does Not Display Data
In some earlier releases, on the Probe tab of the Control Panel, selecting Route in the
Protocol Layer drop-down field and clicking the Protocol Layer drop-down field
button failed to display any data.
22658 iBuilderApplying Configuration to Multiple Remotes Causes iBuilder to

Exit
In iDX 2.1.0, applying multiple configurations to a large number of remotes using the
Automated Configuration Downloader dialog box sometimes caused iBuilder to crash.
16
22697 SNMP OID for TDM Loss Increments Incorrectly

In earlier releases, due to a software bug, the SNMP Object ID for TDM Loss
incremented even when no TDM Loss errors had occurred or were observed in
iMonitor. This caused SNMP queries to return false TDM Loss counts.
22778 iBuilderProblem When Assigning Receive Carrier to TxRx Line Card

The following problem was observed in iBuilder in iDX 2.1.0 in an Inroute Group with
two upstream carriers, with one carrier assigned to a TxRx Line Card and the other
carrier assigned to an Rx-only Line Card.
After further modifications to the TxRx line card, the carrier assigned to the line card
was incorrectly displayed as None in the iBuilder View Properties window.
Furthermore, the options file was no longer correct, the TxRx Line Card became
incomplete, and the entire network went into the deactivation pending state. The
only way to recover was to remove the upstream carrier from the Inroute Group and
from the TxRx Line card and then add it back.
23016 iMonitorControl Panel Data Takes a Long Time to Load

In iDX 2.1.0, it was observed that the iMonitor Control Panel sometimes took over a
minute to load data in a large network. During that time, the message Please wait,
loading data was displayed to the operator.
17

22404 Unsupported Characters When Defining Beam Map Names
In previous releases, the mapserver code only supported alphanumeric characters for
network names and header files. If any other characters were used, it could cause the
mapserver to not generate proper maps. In this release, this issue has been resolved
by using the following method:
When defining a beam name in the header file of the mapserver, users are now
allowed to choose any character as long as the entire name is contained within double
quotes (). For example, the name NSS-7-America | Pacific should appear as
NSS-7-America | Pacific in the header file.
Note:
Users must not use double quotes when defining the Network name in
iBuilder.
22277 Maximum Broadcast bps Calculated from Symbol Rate

Previously in DVB-S2 networks, the maximum broadcast bits per second (bps)
calculation was done by multiplying the carrier symbol rate instead of the carrier
information rate. For example, with a 1000 ksym carrier, the maximum broadcast bps
was calculated at 250k (1000 x .25 = 250k). This could be an insufficient value, if for
example, the carrier's bps capacity was 3.3 Mbps at its best MODCOD. To be
consistent, all calculations of maximum broadcast bps are now performed using the
carrier information rate.
22210 SCPC Errors Generated on iNFINITI Remotes when Using Combination of

8PSK and Certain Frequency Range
Due to some design issues related to loop stability and phase margin, certain iNFINITI
remotes, when exposed to a very specific frequency and modulation combination, can
experience a high number of SCPC errors. This issue has been generally resolved in
this release.
There are still some very specific and very rare combinations of modulation and
frequency where the remotes can still generate some SCPC errors. In such situations,
the following custom key can be applied on each remote to resolve the issue.
[MODEM_PARAMETERS]
rx_nco_centered_at_dc = 0
18
22182 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 for other similar reasons), the iDirect Protocol
Processor and remotes drop these ICMP packets due to the invalid checksum. Some
operators may need to use encryptors outside of the iDirect system, and therefore
need to ensure that the ICMP checksums are disabled in order to pass the encrypted
traffic. To optionally disable the ICMP checksum checks, apply the following custom
keys:
In the Hub-side area of the Remote Custom tab enter:
[REMOTE_DEFINITION]
icmp_filter_bad_checksums = 0
In the Remote-side area of the Remote Custom tab enter:
[ICMP]
icmp_filter_bad_checksums = 0
22188 Problem with Line Card Upgrades

Some iNFINITI line cards could fail to upgrade to iDX 2.0.1 because the iDX 2.0.1 BSP
resized the /tmp folder to 6M after the flash completed. The 6 MB /tmp folder size
was not sufficient because the iNFINITI hub compressed package itself was 5.4 MB. To
accommodate the iNFINITI package the /tmp folder is now resized to 12 MB after the
BSP install.
22156 Beamselector Lists Wrong Beam Number after Beam Number Changed
After assigning a different carrier to a beam number, and pushing the Options file to
the remote and the hub, the beam number in the remote-side Options file correctly
changed. However, the beam number displayed after issuing the beamselector
command was the old beam number in the beam_state.opt file. This was a display
issue only and did not affect the beam switching algorithm. The old beam number
remained in beam_state.opt until the remote switched to this beam, then the
beam_state.opt file was overwritten with the correct beam number.
22051 Sporadic Link Layer Bounces on Multiple Networks and Multiple Remotes
Under certain conditions in a network with mesh and frequency hopping, a Protocol
Processor link layer could see out-of-order reliable frames. If these out-of-order
frames caused a change in the receive window of the Protocol Processor and if enough
out-of-order frames arrived sequentially, the Protocol Processor would restart the link
layer session. In an Inroute Group with Mesh enabled, if there was TCP traffic
present, there might be sporadic link layer bounces seen on some remotes. This issue
could cause the TCP application to disconnect, but did not affect other unreliable
traffic.
19
21927 ICMP Header Processing Error on Protocol Processor-VLAN Interface

Because of an ICMP header processing bug, operators were not able to ping any VLAN
interface on the Protocol Processor blades other than VLAN 1, even though all VLANs
were configured correctly and were working. This issue existed on the Protocol
ProcessorVLAN interface. Performing a TCPDUMP on the Protocol Processor eth0
interface showed ICMP request and response packets, but the actual ping did not
occur due to the ICMP header bug.
21904 Round-Robin Order for Trying Beams Not Fair In Mapless Mode
When a modem was not receiving beam mapping information from the mapserver
(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.
21879 Remote Causing Downstream Congestion

If a remote was actively receiving UDP traffic on the downstream and it fell out of the
network (for reasons such as powering off, roaming, etc.), some UDP traffic could be
queued in the Protocol Processor waiting for transmission. This traffic was not
released until the remote re-synchronized with the Protocol Processor. The queued
UDP traffic continued to be allocated downstream bandwidth, which it could not 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 could remain in this state permanently resulting in bandwidth wastage on
the network in which it was formerly passing traffic.
21588 Console ipstats Command Produces Negative Values in Long Term

Bandwidth Report
In previous iDX releases, running the ipstats command on the remote console
displayed the raw ipstats values, some of which rolled over to negative values after
several hours. These statistics are now incremented properly, rolling over to nonnegative values (after several hours).
20
21571 keepalive Interval from Modem to Antenna Does Not Take Effect
Immediately
In previous iDX releases, the keepalive interval sent from the modem to the antenna
controller took effect after 30 seconds instead of immediately.
21508 iBuilderNewly Created Remote Set Upstream QoS Profile to Default

In previous iDS/iDX releases, after creating a new remote and configuring the
necessary parameters, configuring QoS by selecting Downstream and Upstream
Service Profiles on the QoS tab and clicking OK, and finally rechecking the QoS tab of
the remote revealed the Upstream Service profile was replaced with the Default
profile. However, once the initial configuration was complete and the remote saved,
operators could reselect the correct profile, and the changes were executed. This
problem only occurred during the initial creation (save) of the remote.
21391 DFOE Traffic Sent Over Clear Channel

In TRANSEC mode, DFOE traffic was previously sent over a clear channel. In TRANSEC
mode, all options are now considered as critical security parameters and encrypted
during over-the-air transmission.
20259 Maximum Information Rate Not Enforced in Carrier Grooming Mode

In an Inroute Group with multiple Inroutes, the MIR configuration in the GQoS tree for
the upstream direction was not strictly enforced when the Inroute Group was in
carrier grooming mode. The MIR was enforced in frequency hopping mode. This has
been resolved in this release through various design changes and enhancements in the
GQoS structure.
20057 samnc Process Utilizes 100% of CPU During Network Options File Reload
Applying changes to a large network Options file caused significant processing delays
in pp_controller, samnc, and all child processes. The larger the Options file, the
greater the delay. As a result, the processes failed to perform critical tasks such as
timeplan calculation and heartbeat processing, which could result in remotes losing
UCP or going out of network.
17912 SNMP Server 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 stopped sending traps and needed to be restarted periodically. To correct this
problem, the SNMP code (a part of Linux) has been upgraded.
21
22390 iMonitorRemote Status Displays Inconsistent for Roaming Remotes
Activated in Multiple Networks
Remote status displays for an active remote were not consistent for the in network
instance. Additionally, only some of the remote status information was updated for
the elsewhere instances. The different instances of the same remote each
displayed different data.
22201 iBuilderModify All Instances on Roaming Remote after Updating

Properties Not Allowed
After selecting the Modify All Instances option to change the power setting for a
roaming remote, then updating properties and changing the remote model type,
iBuilder did not permit the operator to again use the Modify All Instances option to
change back to the original power setting. iBuilder reported not a unique serial
number, as if the system did not consider this remote to be roaming.
22174 iBuilderUpstream MIR/CIR Setting for Virtual Remotes Not Based on IP

Data Rate
In iDX 2.0, information overhead was not included in MIR and CIR calculations when
overriding Application Properties on Virtual Remotes in the Service Profile View of the
Group QoS tab of a Network or Inroute Group. Therefore, the MIR and CIR configured
for Virtual Remotes were not based on IP Data Rate, making those calculations
inconsistent with other configured MIR and CIR calculations.
Note: There is one specific configuration which still does not calculate MIR/CIR
properly in iDX 2.1.0. In an Application Service Group, if a remote is in
remote-based mode, and MIR/CIR are assigned to the Virtual Remote, the
satellite overhead is added twice, resulting in allocation of slightly more
bandwidth than configured. This final case is fixed in iDX 2.1.1.
22165 iMonitorUCP and Remote Status Events Missing

When certain time ranges were selected in the Select Time Range dialog, UCP and
Remote Status events for a particular time period of the day were missing in the
Modem Events window. When the time range selected was broadened (to envelop the
relevant period), the missing events could appear. This anomaly applied to event data
viewed in the iMonitor tabs and also event data saved as a text data file.
22125 Mobile Remote latlong_timeout Values Below 120 Seconds Not Supported
In previous releases, the latlong_timeout value for mobile remotes was set to a
default of 120 seconds and could not be set to a smaller value. In this release,
changes have been made to allow an operator to set this value to any different
number by using the following custom key:
[MOBILE]
22
latlong_timeout = xxx
where:
xxx is any number in seconds smaller or larger than 120
22099 iMonitorIncorrect Display of MODCOD for Remotes

There was a reporting and display problem in which iMonitor displayed a MODCOD of
16PSK for a remote receiving a DVB-S2 carrier configured with a Maximum MODCOD of
8PSK-5/6. This was only an iMonitor display problem. The actual MODCOD received by
the remote did not exceed the Maximum MODCOD configured for the carrier.
22090 iBuilderUpstream Filter Rule Modification Not Reflected in Options File

Options files were not regenerated after an upstream Filter profile was modified. For
example, after assigning a Filter profile to a remote in the upstream direction, then
modifying the profile (for example, changing the source or destination IP port) and
clicking OK, no hub-side changes were pending on the remote. However, after
modifying the remote password to force an Options file regeneration, the filter rule
change was generated in the Options file.
22076 iMonitorLine Card CRC Errors Show Up as RCM Fault Warning Type in
Conditions Log
When CRC errors were generated on Tx/Rx or Rx-only line cards, instead of displaying
the correct error in the Conditions tab, an RCM_FAULT_WARNING error displayed
instead. The Active Conditions and Observation View tabs did not display this
erroneous message.
22007 iMonitorQoS Statistics for BW Requested and BW Allocated Data

Displaying in Wrong Columns
When viewing either the Upstream QoS Stats or Downstream QoS Stats for a remote
in iMonitor, the BW Requested data and BW Allocated data were switched on the List
tab. BW Requested data was displayed in the BW Allocated column and BW
Allocated data was displayed in the BW Requested column
21931 iMonitorSat Traffic Graph Historical Report Not Working

After selecting the SAT Traffic Graph option in the iMonitor tree selecting Historical
in the Select Items dialog box, the system was not reporting the historical SAT Traffic
data.
21912 iMonitorIncorrect Reporting of CPU Usage

Due to an iMonitor display issue, the CPU Usage graph displayed an incorrect value
after the Time Range interval was increased. CPU usage increased dramatically after
23
the interval was increased. The data was correct, but the graph displayed the wrong
value (with either the Min or Hour interval selections).
21834 iBuilderChanging Remote Site Notes Caused Configuration Changes at

Both Hub Side and Remote Side
In some isolated cases, changing the Name field on the remote Information tab (or
even changing the Site Notes field), caused the remote to unnecessarily enter the
Changes Pending state on both the Remote side and Hub side. Examination of the
remote Options file indicated that minor changes to Spoof buffer sizes and QoS queue
depths appeared to be driving this condition.
Additionally, changing the Information Rate field on the Information tab of a Carrier
configuration window then clicking Symbol Rate, caused the Information Rate value
to change slightly after closing and then reopening the Carrier configuration window.
Upon investigation, iDirect discovered that any changes affecting a carrier
configuration had the potential of rounding up on the calculated bitrate, which could
generate minor changes in Options file values. To drastically reduce the likelihood of
bitrate calculations being affected by decimal value rounding, iDirect doubled the
decimal precision from 10 to 20 decimal places.
Both issues fixed in this release.
21685 iMonitorIP Graph Displays Incorrect Time Scale

The IP graph in iDX 2.0.1 displayed an incorrect time scaleless than the actual time
by 6 hours.
21588 iMonitorIP Statistics Display as Negative Values in Long Term Bandwidth

Report
In previous releases, while attempting to generate an IP Long Term Bandwidth usage
report for a line card, some of the entries in the report displayed negative values,
which is abnormal.
21589 iBuilderNMS Does Not Allow Creation of VLAN With /28 Subnet
In previous releases, the NMS would not allow creation of a VLAN with a /28 subnet.
After entering x.x.x.240 in the Subnet Mask field of the VLAN create dialog and
clicking OK, the VLAN create dialog would not close. Other VLANs with different
subnets could be created without issue. iBuilder allowed creation of any VLAN as long
as the subnet mask was not /28.
21513 iMonitorSNMP Server MIB Missing DVB-S2 Statistics

In previous releases, all DVB-S2 related statistics were missing from the SNMP server
MIB. In this release, the DVB-S2 statistics have been added to the SNMP MIB. See
Appendix C, SNMP Proxy Agent, in the iMonitor User Guide for iDX 2.1 for complete
information.
24
21494 iBuilderVNO Users with No Ownership of Network Can View Changes

A status leak that could compromise VNO privacy existed where VNOs received edit
notifications for elements they did not own and could not view. For example, VNO
users with no Ownership or Visibility permissions for a particular network were able
to view configuration changes made to a Carrier component of a line card belonging
to this network. This unauthorized visibility by the VNO would apply to changes for
both upstream and downstream Carriers assigned to the line card.
21468 iMonitorCommunication Problem Between Chassis and NMS

On rare occasions, in the case of multiple chassis being managed by the same Chassis
Manager server, if the NMS could not communicate with one of the chassis, all chassis
could show the Lost connection with chassis alarm in iMonitor. After some time
(typically about 20 minutes), this alarm cleared on all good chassis without any
operator action.
21418 iBuilderControl and Visibility Issues with VNOs

Previously, for VNOs to control and make changes at the Inroute Group level, they also
automatically had the rights to reset the Tx line card. With this change, line cards can
now be reset only if the parent node has ownership rights. In all other cases (in shared
scenarios), VNOs are not able to reset line cards, even if the VNO has Control rights
over the Network.
Control rights at the Network level can now be assigned to VNO user groups by a Host
Network Operator (HNO), which allows the VNO group to apply changes made to an
Inroute Group in the same Network, while preventing the same VNO from resetting
the Tx line cards in the same network. This change eliminates the possibility of a VNO
bringing down an entire network.
21305 iBuilderVNO Protocol Processor Blade Visibility Not Limited

In previous releases, a VNO user was able to view the Protocol Processor blade
information (for example, IP addresses, processes, CPU). In this release, visibility
control of Protocol Processor blade information is now tightened in iMonitor and
iBuilder. This prevents situations in which a VNO user can view Protocol Processor
blade information, unless specifically allowed by the HNO.
21181 iBuilderCarrier Visibility for VNO Users Not Limited

In previous releases, a VNO user could see all the carriers, including the ones not used
by the line cards in the VNOs network. In this release, VNO ownership rules are now
extended to components in the Spacecraft portion of the iBuilder tree. This ensures
that a VNO line card can only be configured with a carrier that is visible to the VNO
(with all carriers and spacecraft invisible by default).
25
21182 iBuilderVNO Sees Newly Added Remote As Only Visible Not Owned
When a VNO user added a remote to an Inroute Group (with Create permissions),
iBuilder saw the remote as only visible, which made converting it to a roaming
remote impossible. Restarting iBuilder corrected the problem.
10563 iBuilderCarriers with Symbol Rates Lower than 64 Ksps Prohibited

To eliminate operator confusion and to be consistent with iBuilder design, iSite now
prohibits configuration of carriers with symbol rates lower than 64 ksps.
26
Known Issues
This chapter lists all known issues in iDX 2.1.x. It contains the following sections:
Known Issues in iDX 2.1.x on page27 lists known issues that exist in iDX 2.1.0, iDX
2.1.1, and iDX 2.1.2.
Known Issues in iDX 2.1.0 Only on page33 lists known issues that exist in iDX 2.1.0 but
were fixed in iDX 2.1.1. These issues are also documented as bug fixes in Bugs Fixed in
iDX 2.1.1 on page13.
In each section, the known 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)
Known Issues in iDX 2.1.x

This section lists known issues that exist in iDX 2.1.0, iDX 2.1.1, and iDX 2.1.2. In addition to
the known issues listed in this section, the known issues listed in Known Issues in iDX 2.1.0
Only on page33 also exist in iDX 2.1.0.

The following Protocol Processor, Hub Line Card, Remote, and NMS Server known issues affect
iDX 2.1.0, iDX 2.1.1, and iDX 2.1.2:
23984 X5 May Exhibit Degraded SNR Performance in iNFINITI mode

It was discovered that some Evolution X5 remotes may be affected by adjacent carrier
interference (ACI) when operating in iNFINITI mode. The affected remotes may
exhibit some degradation in downstream SNR values when operating in iNFINITI mode
(TPC downstream and with less than 5 Msps size) with the presence of large adjacent
carriers. A fix has been identified to improve performance and we are currently in the
process of incorporating it into the next release. X5 remotes using DVB-S2
downstream carriers are not affected. This issue will be resolved in the next release.
27
24216 Revision Server is Disabled for VNO Super User Even Though Network
Owned Permission is Given
When a VNO super user is given owned permission of a network, the option to use
Revision Server to download packages is disabled.
Work-around:
Give the VNO super user visible permission with control permission of the
network and owned permission of the remote. Then Revision Server is enabled.
22425 Evolution Antenna Pointing Not Scaled for Lower MODCODs

When pointing the antenna for a remote with the minimum MODCOD set below QPSK3/4, the modem may lock with a pointing Signal Strength value in the range that
indicates strong RF energy and not locked but with low SNR.
This situation can create confusion because installers might assume they are on the
wrong satellite because the dish is coarse adjusted just enough to lock to the carrier,
but the indication is high RF energy rather than locked but with low SNR.
This situation occurs in both PWM and Console pointing modes.
22254 Spurious RCM Alarms Reported in Daisy-Chain Chassis Configuration

When multiple chassis are configured in a Daisy Chain, the RCM modules may report
intermittent alarms. These alarms are primarily reported by the Slave RCM in the
Master chassis. However, on occasion either the Master or Slave RCM in the Slave
chassis also reports alarms. This anomaly only appears in DVB-S2 networks. The RCM
alarm clears itself after the next status poll.
22217 Mapserver Process Does Not Rebind to Port 5003 If Restarted

In certain cases, if the mapserver process is stopped and immediately restarted, it
can fail to bind to port 5003 as it normally should. In such situations, the mapserver
process may not start automatically and may need to be manually started.
Work-around:
If you need to stop and restart the mapserver process, you should wait a couple of
minutes after stopping the process before restarting. This will allow the old session to
clear and mapserver to start normally.
The following iBuilder, iMonitor, and NMS Server known issues affect iDX 2.1.2, iDX 2.1.1 and
iDX 2.1.0:
24157 iBuilderIn Modify all Instances Option, Multicast Tab Gets Greyed Out
After Adding One Multicast IP Address
In global networks, you can add a multicast address to a remote and select Modify All
Instances to apply the address to all instances of that remote. However, if you need
to go back and change the multicast address, the Multicast Tab is disabled (greyed
out) on the IP Tab of the Modify Configuration Object window.
Work-around:
28
The multicast address can be changed in each individual instance.
22548 iBuilderAllows Priority Field To Be Left Blank On Remote QoS Tab

iBuilder allows the Priority field on the Remote QoS tab to be left blank when the
remote is in a Remote Service Group. In this case, the Priority value is set to Best
Effort (the lowest priority).
22507 iBuilderDVB-S2 Fast Fade Configuration Changes Do Not Update Options

File
If a user changes the default values of the Fast Fade configuration parameters for a
network, the first time changes work fine, but any subsequent changes may not be
properly propagated to the remote Options files.
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. The values shown below are just an
example:
[DVBS2]
fast_fade_margin = 100
mode = acm
system_margin_steady_state = 50
threshold = 50
22421 iMonitorDisabled Warnings Display In Blade Info Window

When operators disable warnings in the Active Conditions tab, the iMonitor Tree view
plus all other iMonitor windows (for example, Blade Info, Network Condition windows)
are notified and forced to change the remote status to Nominal. When these same
warnings are later generated, the Active Conditions tab should filter out the disabled
warnings, then broadcast other warnings to the Tree view and other windows.
However, the iMonitor Blade Info window still receives these disabled warnings. The
remote remains in this same state even if a new Blade Info window is opened.
22334 iMonitorQoS Options On Remote Control Panel Do Not Show CIR Enabled
The Upstream Rate Shaping and Downstream Rate Shaping options on the QoS tab
on the remote Control Panel do not indicate CIR as enabled (Enable checkbox not
checked in Committed Information Rate section) even when CIR has been enabled on
the Remote QoS tab in iBuilder.
29
21503 Global and Local Group with Same Name in Options File Causes Remote to
Behave Unexpectedly
This issue is present in all ABS releases and affects the [BEAMS] group in roaming
remote Options files. In a mobile network, when you add custom keys to the [BEAMS]
group of a remote Options file, it is expected that the NMS will consolidate the local
Options files (containing the custom keys) with the Global Options file, and send the
consolidated Options file to remotes for processing. Instead, only the local Options
file is processed by the remote, which can cause the remote to behave in unexpected
ways.
Work-around:
Add the exact same custom keys to all instances of the roaming remote, then the NMS
will generate one consolidated [BEAMS] group in the Options file.
21274 iMonitorTimeplan Graph Shows Allocated Slots in Free Slot Column

In the iMonitor Timeplan display for an Rx line card, when only the Free Slots check
box is selected, the individual remote free slot allocations are shown in the remote
columns. In this 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 3. The Free column
(far left) should be empty in the figure.
Figure 3. Timeplan Graph: Incorrect Free Column
21160 iBuilderConfiguration Server and Chassis Manager Lose Synch After

Failing to Apply
When upgrading from an earlier release, the chassis configuration is preserved in the
NMS database. After the upgrade, chassis licenses must be imported into iBuilder and
the chassis serial number validated on the Chassis Configuration screen. You then
apply the chassis changes in iBuilder to activate your licensed chassis.
30
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, if the changes are not successfully applied to the Chassis Manager,
restarting either the NMS Configuration server or Chassis Manager causes the chassis
configuration to be lost. Should this problem occur, you must reconfigure the chassis
in iBuilder.
Work-around:
This problem was seen when a chassis license was issued containing an incorrect
chassis IP address. Therefore, to avoid the problem, you can 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 applying the
license to the chassis in iBuilder, in the event that the problem occurs and you need
to reconfigure the chassis.
20822 iMonitorRx Power Not Displayed In eM1D1 TxRx Standby Line Card
TxRx eM1D1 Standby line cards do not display the Rx power in the Hub Stats window.
This information is needed for the operator to determine whether the Rx connection
of the Standby line card is healthy.
Work-around:
To determine the Rx power, telnet to the line card and enter the following command:
[HUB:17599]
> rxdiag rxpower
Rx RF Composite Power : -61.646000
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.
20148 iBuilderAll Remotes and Applications Disappear In Application Based

Mode When New Application Added
In Group QoS Application-based mode, after successfully adding new Applications in
the Group view and the Service Profile view of the Group QoS tab for a network or
inroute group, all remotes and Applications (even Default and NMS) disappeared in
the Service Profile Remote view. After clicking OK and reopening the GQoS tab (or
choosing something different in the Select Group drop-down menu), all remotes and
Applications re-appeared. If you see a similar problem, choose a different group in
the Select Group drop-down, then re-select the original group.
23107 iMonitorControl Panel Does Not Load After Upgrade to iDX 2.1
In iDX Release 2.1, a VNO enhancement allows the HNO to selectively set the VNO
visibility for upstream and downstream carriers. Due to this enhancement, carriers
that should be visible to a VNO in iBuilder may not be visible to the VNO after
upgrading to iDX 2.1.x. When that happens, attempts by a VNO user to open the
iMonitor Control Panel for a remote in the Network fail and a message is displayed
31
stating that there are not enough Windows resources available to open the Control
Panel View.
Workaround:
If this problem occurs, the HNO should make the carriers visible to the VNO User
Group in iBuilder. To do this:
1.Right-click the carrier in the iBuilder Tree and select ModifyVNO.
2.In the Visible to VNO Group area of the dialog box, select the check box for the
VNO.
3.Click OK.
4.Apply the changes to the VNOs Network.
23155 iMonitorRoaming Remote MODCOD Toggles on the SAT Traffic Graph

When a Roaming Remote is configured in multiple DVB-S2 networks in iBuilder, the
MODCOD reported to the NMS sometimes toggles between the remotes current
operational MODCOD and the minimum MODCOD(s) configured for the non-active
network(s). This causes the throughput displayed on the iMonitor SAT Traffic graph for
the remote to zigzag as the reported MODCODs vary.
Typically, the higher throughput reported for the remote is correct. If in doubt, you
can verify the operational MODCOD of the remote by right-clicking the remote in the
iMonitor tree and selecting MODCOD Distribution.
21735 iMonitorRemote Availability Sometimes Inaccurate When Viewed for

Multiple Remotes
You can view Remote Availability at the Network, Inroute Group, and Remote levels of
the iMonitor tree. When viewing remote availability for multiple remotes (Network or
Inroute Group level), the data is sometimes incorrect for one or more of the remotes
in the list.
This problem does not occur when you view remote availability for a single remote.
Therefore, to ensure that the availability data for a specific remote is correct, click
the individual remote in the tree and select Remote Availability.
32
Known Issues in iDX 2.1.0 Only

This section lists additional known issues that exist in iDX 2.1.0 but were fixed in iDX 2.1.1.
This section is only applicable if you are running iDX 2.1.0. In addition to the known issues
listed in this section, the known issues listed in Known Issues in iDX 2.1.x on page27 also
exist in iDX 2.1.0.

In addition to the known issues listed in Operation Affecting Issues on page27, the
following additional operation-affecting known issues affect iDX 2.1.0:
22490 Map-based ABS Remote with Serial NMEA Input Operating in Western
Hemisphere may Operate in Mapless Mode
A mobile ABS remote that receives 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 reacquire the network in a round-robin manner (as in mapless mode operation), and
operators logged on to the remote may observe the following message repeating on
the remote console:
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
22632 Downstream GQoS ID is Zero in Options File for Newly-Created Remotes

When creating a new remote iBuilder, if you select the QoS tab and assign one
direction (upstream or downstream) to a Service Profile and the other direction to a
Remote Profile, then the gqos_id in the hub-side options file is incorrectly set to zero.
This results in the remote being unable to come into the network.
Note:
This problem only occurs if the profile assignments are made while
creating a new remote.
Note:
This problem does not occur if both upstream and downstream profiles
are of the same type (that is, if both are Service Profiles or both are
Remote Profiles).
Work-around:
First create and save the remote without assigning the profiles. Then modify the
remote, click the QoS tab, and assign the profiles.
33
22989Evolution Remotes with Upstream Spectral Inversion May Take Longer to

Acquire
An issue was found in the Evolution remote software which causes incorrect
calculation of the remotes frequency offset when its uplink is on spectral inversion.
As a result, Evolution remotes may take longer than usual (as much as one hour) to
acquire into the network under certain conditions.
Affected Products:
Evolution X3, X5, e8350, e800, and e850mp operating in DVB-S2 networks
Evolution X5 remotes operating in SCPC networks
Note:
iNFINITI remote model types are not affected by this issue.
Workaround:
To fix this problem, apply the following custom key in the hub-side area of the
Remote Custom tab and apply the changes:
[REMOTE_DEFINITION]
sweep_method=0
This custom key disables iDirects fast-acquisition method. It can be applied without
resetting the remote.
23054 Evolution X3 and X5 Remotes Lock Up at Temperatures Below 15oC

In iDX Release 2.1.0, on rare occasions the processor on Evolution X3 and X5 Remote
Modems can lock up at temperatures below ~15oC. This problem only affects X3 and
X5 remotes receiving DVB-S2 downstream carriers. It does not affect remotes
receiving SCPC carriers.
When the problem occurs, the remote LEDs remain constant and no response is seen
from the console or LAN ports. Typically, a single power cycle is required to recover
the modem. If the modem locks up again, wait until the temperature rises above
~15oC and power cycle the remote again.
23167 Excessive Jitter on VoIP Calls During Upstream Congestion

VoIP calls may experience jitter when the upstream carrier is congested even when
the VoIP Application has higher priority than other traffic and therefore should be
granted sufficient bandwidth for the calls. If you experience this problem, iDirect
recommends that you upgrade to iDX Release 2.1.1.
In addition to the known issues listed in NMS/Reporting Issues on page28, the following
additional iBuilder, iMonitor, and NMS Server known issues affect iDX 2.1.0:
22546 iMonitorClicking View Stats after Selecting Route in Protocol Layer

Field Does Not Display Data
On the Probe tab of the iMonitor Control Panel, selecting Route in the Protocol Layer
drop-down field and clicking the Protocol Layer drop-down field button fails to
display any data.
34
22525 iBuilderHNO Cannot Modify Visibility of Reflector Components for VNO

Reflector components have default visibility once they are created by the HNO. If this
visibility is removed, and the reflector component is assigned to a remote, the HNO is
unable to enable visibility again.
Work-around:
Unassign the reflector component away from the remote. This allows the HNO to
change the visibility, and then reassign the reflector back to the remote.
22519 iBuilderClicking Service Profile in Service Profile-Remote View Adds

Replica of Virtual Remotes
Clicking a Service Profile in the Service Profile-Remote View of the Group QoS Tab for
a Network or Inroute Group visually adds replicas of all remotes assigned to the
Service Profile. This is a display issue only and has no impact on actual configuration.
However, modifying or deleting any of the Remotes displayed in the Service ProfileRemote View affects the actual Remote Service Profile Assignment.
For example, deleting any of the duplicate Remotes removes the actual Remote from
the Service Profile. Selecting OK may then leave the Remote with no Service Profile
assignment and change it to the Deactivation Pending state.
Work-around:
Leave the Service Profile-Remote View by clicking Cancel to clear duplicates from the
display. The display will be correct the next time the window is opened.
22473 iBuilderModify All Instances Does Not Modify Downstream MIR

On occasion, selecting the Modify All Instances option when right-clicking a remote
in the iBuilder tree does not modify the Downstream MIR for all instances.
22476 iMonitorMulticast Bytes Not Displayed in SAT Downstream Tab

When downstream multicast traffic is sent in the network, the traffic flow is
displayed in the SAT Traffic graph, where multicast packets are shown properly.
However, in some cases the multicast bytes are not displayed in the Multicast column
of the SAT Downstream tab of the SAT Traffic graph.
22543 iMonitorIncorrect Value for SAT Traffic When Using Symbol Button
When you select the Symbol Button for downstream DVB-S2 traffic on the iMonitor SAT
Traffic graph for multiple remotes, incorrect symbol rates may be displayed. The
Symbol Button works correctly when selecting a single remote.
22532 iMonitorX3/X5 Remote Statistics Not Displayed in Data Snapshot Window

For Evolution X5 and X3 remotes in DVB-S2 networks, attempting to display the Rx
Composite Power and Tuner AGC Gain values in the iMonitor Network Data Snapshot
results in N/A appearing for these two statistics. For Evolution e8350/mp850
remotes, this data is displayed as expected.
Work-around:
As a partial work-around, you can view the Rx Composite Power for an X3 or X5
remote by right-clicking the remote in the iMonitor Tree and selecting Remote
35
Status/UCP, or by clicking the Remote Status tab on the Control Panel for the
remote.
22778 iBuilderProblem When Assigning Receive Carrier to TxRx Line Card

The following problem was observed one time in iBuilder in iDX 2.1.0 in an Inroute
Group with two upstream carriers, with one carrier assigned to a TxRx Line Card and
the other carrier assigned to an Rx-only Line Card.
After further modifications to the TxRx line card, the carrier assigned to the line card
was incorrectly displayed as None in the iBuilder View Properties window.
Furthermore, the options file was no longer correct, the TxRx Line Card became
incomplete, and the entire network went into the deactivation pending state.
Work-around:
To recover, remove the upstream carrier from the Inroute Group and from the TxRx
Line card and then add it back.
22531 iMonitorDisplays Incorrect MODCOD Values Under Remote QoS Tab

The Minimum MODCOD, Nominal MODCOD and Maximum MODCOD for X5 and e8350
DVB-S2 remotes are all displayed as QPSK-1/4 on the iMonitor Control Panel QoS tab
regardless of how these values are configured in iBuilder. Check the iBuilder Remote
QoS tab to determine the correct configuration.
36
This chapter contains instructions for downloading iDX Release 2.1 software, as well as special
installation notes.
Installing iDX Release 2.1.x
Installation Notes
Installing iDX Release 2.1.x

Downloading Required Files for iDX Release 2.1.x
To retrieve iDX Release 2.1.x software, access the TAC web page (located at: tac.idirect.net),
click the Software Releases link, then click the iDX 2.x Releases link and scroll down until
you find iDX Release 2.1.x.
Installation Notes
Maintaining Pre-iDS 8.x Compatibility
When upgrading from an iDirect release that did not support Group QoS (pre-iDS 8.x) you can
choose to upgrade to Application Service Groups or Remote Service Groups. Select Remote
Service Groups to best preserve your pre-iDS 8.x QoS functionality.
Service Level Changes after QoS Conversion

After upgrading from a pre-GQoS release to iDX Release 2.1, the QoS structure in your iDX
Release 2.1 system will see the following changes:
If an additional Service Level with the rule Protocol = TCP was created in a pre-GQoS
release, it will be deleted during the conversion. This action follows the conversion logic
where all rules with Protocol = TCP are included in the Default Application Group TCP
Service Level. If any special configuration parameters were set for this Service Level (for
example, Priority, Cost value) they will be lost with the parameters reverted to default
values.
37
Installation Notes
The Default Service Levels Protocol = TCP and Default are replaced by the Default
Application Group after the conversion. Therefore, if the Default Service Level had any
special configuration parameters (for example, Priority or Cost values) configured, this
data is lost after the conversion.
Copying Daily Backup Files

In daily operation, if it is necessary to copy the backup files in the /var/idirect/backup
directory to other locations using SCP or winSCP, due to reasons related to permissions and
ownership iDirect recommends the following steps.
1. Compress the backup files to a .tgz format first using either the tar -zcvf command, or
creating a tar archive by executing the idsBackup script with the -z option.
2. Copy the tar file to other locations for future restoration using the idsRestore script.
Note:
38
Simply changing permissions and ownership will not work. The tar archive
format must be used.
Installation Notes
39

RN iDX 2121 RevG 030411

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

RN iDX 2121 RevG 030411

Hochgeladen von

Copyright:

Verfügbare Formate

Release Notes

For iDX Releases:

Document Name: RN_ReleaseNotes_iDX_21x_Rev G_030411.pdf

iDX Release Notes 2.1.x

Reason for Change(s)

Initial release of document for

Added minor changes/corrections EHoffman

Added known issue 22490

Update for Release 2.1.1

Consolidated for 2.1.0 and 2.1.1

Update for Release 2.1.2

Update for Release 2.1.2.1

iDX Release Notes 2.1.x

iDX Release Notes 2.1.x

About This Guide

Supported Hardware and Features

New Features & Enhancements

Latest Operating System and Database Support ....................................... 6

Security Enhancements .................................................................... 6

iDX Release Notes 2.1.x

Telnet Command Change Due to Upgrade of Busybox ................................................. 6

Scalability and PPS Enhancements ....................................................... 7

Roaming Remote Enhancements ......................................................... 8

Other Feature Improvements ............................................................. 8

Bugs Fixed in iDX 2.1.1 ................................................................... 13

iDX Release Notes 2.1.x

or Inroute Groups ................................................................................... 15

Bugs Fixed in iDX 2.1.0 ................................................................... 18

iDX Release Notes 2.1.x

iDX Release Notes 2.1.x

Known Issues in iDX 2.1.0 Only ......................................................... 33

Installation Notes .......................................................................... 37

iDX Release Notes 2.1.x

iDX Release Notes 2.1.x

About This Guide

Contents Of This Guide

Supported Hardware and Features

New Features & Enhancements

iDX Release Notes 2.1.x

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 Release Notes 2.1.x

CAUTION: When you see this alert

WARNING! Electric shock hazard: When

Network Upgrade Procedure Guide for iDX Release 2.1.x

Network Upgrade Procedure Guide from iDX Release 2.1.0 to 2.1.x

iDX Release 2.1 iBuilder User Guide

iDX Release 2.1 iMonitor User Guide

iDX Release 2.1 Technical Reference Guide

iDX Release 2.1 Satellite Router Commissioning & Installation Guide

iDX 2.1 iDirect Features & Chassis Licensing Guide

iDX Release 2.1 Upgrade/New Installation Survey

iDX Link Budget Analysis Guide

For details of hardware specifications supported in this release, please refer