IDX 3.3 - Release Notes

Release Notes iDX Releases 3.3.x.
Release Notes
For iDX Releases
3.3
3.3.0.x
3.3.2.0
3.3.2.1
3.3.2.2
3.3.2.3
3.3.2.4
3.3.2.5
3.3.3.1
3.3.4
November 30, 2015
Copyright 2015, 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.
iDirect, a subsidiary of VT Systems, is a global leader in IP-based satellite communications providing technology that
enables our partners to optimize their networks, differentiate and expand their businesses. The iDirect Intelligent
Platform allows our partners to run their entire business operations more efficiently via a single, unified IP-based
satellite architecture, whether it's providing core IP applications to the enterprise or specialized services to any
number of diverse vertical markets. iDirect is the #1 name in global satellite communications in key industries
including maritime, military/government, and oil and gas.
iDirect
Company web site: www.idirect.net ~ Main Phone: 703.648.8000
TAC Contact Information: Phone: 703.648.8151 ~ Email: tac@idirect.net ~ Web site: tac.idirect.net
iDirect Government, created in 2007, is a wholly owned subsidiary of iDirect and was formed to better serve the
U.S. government and defense communities.
iDirect Government
Company web site: http://www.idirectgov.com ~ Main Phone: 703.648.8118
TAC Contact Information: Phone: 703.648.8111 ~ Email: tac@idirectgov.com ~ Web site: http://tac.idirectgov.com
Document Name: RN_iDX_3.3.x.x_Rev_K_112415

Document Part Number: T0000646
ii
Release Notes
iDX Releases 3.3.x.x
Revision History
The following table shows all revisions for this document. To determine if this is the latest
revision, check the TAC Web site. Refer to Getting Help on page xii for TAC access
information.
Revision Date Released Reason for Change
A
02/19/2015
Initial Document Release for iDX Release 3.3.2.0.
04/27/2015
Update for iDX Release 3.3.2.1.
05/14/2015
Update to Bug Fixes chapter.
08/14/2015
08/27/2015
Update to Important Notices chapter.

Update the Installation Instructions chapter to include software
download procedure on iGT TAC Web site.
F, G
09/22/2015
10/01/2015
Update for iDX Patch Release 3.3.2.3 for Remotes.
10/21/2015
Update for iDX Patch Release 3.3.2.4.
11/17/2015
Update for iDX Patch Release 3.3.2.5.
11/30/2015
Update for iDX Release 3.3.4.0
Release Notes
ix
Revision History
Release Notes
Contents
Revision History
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xi
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Contents Of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii
iDirect Standard User Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
Installation, Support, and Maintenance Guide . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
Hub Line Card Specifications Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
iBuilder User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
iDirect Features and Chassis Licensing User Guide. . . . . . . . . . . . . . . . . . . . . . . .xiv
iDirect Hardware Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
iDirect Software Features Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
iMonitor User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Link Budget Analysis Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Network Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
NMS Redundancy and Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvi
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvi
Satellite Router Installation and Commissioning Guide . . . . . . . . . . . . . . . . . . . . .xvi
SatManage Integration and Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . .xvi
Software Install Guide for New Hubs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
SCAP User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Release Notes
iii
Contents
Technical Reference Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Web iSite User Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
New Features and Enhancements
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Enhancements in iDX Release 3.3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features in iDX 3.3.3.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Layer 2 Over Satellite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Layer 2 and Layer 3 Hybrid Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Second Demodulator on the X7-Series Satellite Routers . . . . . . . . . . . . . . . . . . . . . 2
Encrypted MCFP Support on 2nd Demodulator . . . . . . . . . . . . . . . . . . . . . . . . . 2
X7-ER Satellite Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
NMS Scalability Improvements in iDX 3.3.2.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
RAMDISK Addition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Memory Utilization Performance Improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Memory Increase for iBuilder and iMonitor Clients. . . . . . . . . . . . . . . . . . . . . . . . . 3
Terminal Security Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
New Features in iDX Release 3.3.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
FIPS 186-4 Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Support for Managing Jitter Sensitive Applications . . . . . . . . . . . . . . . . . . . . . . . . 4
X7 Satellite Routers Support 50 MHz BUC Reference Tone without Manual Custom Keys5
Enhancements in iDX Release 3.3.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
ADTMA Instability Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Nominal Carrier Equivocation Occurring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Network Upgrade Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Ability for e8xxx Remotes to Generate ATDMA Waveforms in Stand-alone Mode . . . . . 6
New Environmental Variable Limits ACQ Sweep Messages . . . . . . . . . . . . . . . . . . . . 6
Support for Large Carriers with Multi-Channel Demodulation (MCD) Using Inclined Orbit
Satellite Bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
New Features in iDX Release 3.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Legacy Supported Features in iDX Release 3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
AES-256 Link Encryption Support for the e150 and X1 Satellite Routers . . . . . . . . . . . 7
Compressed Real-Time Protocol Support for the e150 and X1 Satellite Routers. . . . . . 8
Hub Geographic Redundancy Support for the e150 and X1 Satellite Routers . . . . . . . . 8
iv
Release Notes
Contents
Increase Inbound Symbol Rate to 4 Msps for e150 and X1 Satellite Routers . . . . . . . . 8
NAT/PAT Support for the e150 and X1 Satellite Routers . . . . . . . . . . . . . . . . . . . . . 8
Soft Remote Lock Support for the e150 and X1 Satellite Routers . . . . . . . . . . . . . . . 8
Support for up to Eight VLANs for the e150 and X1 Satellite Routers. . . . . . . . . . . . . 8
Extended L-Band Support for Ka-Band Deployment . . . . . . . . . . . . . . . . . . . . . . . . 9
Supported Features and Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Hardware Feature Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
NMS Client Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Supported Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Features No Longer Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Supported Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Reference Clock Module - Pulse Per Second (RCM-PPS) . . . . . . . . . . . . . . . . . . . . 13
Chassis Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Satellite Routers and Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
NMS and Protocol Processor Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Supported System Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Antenna Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Web iSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Important Notices
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Unsupported TRANSEC for iDX 3.3.3.x Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

X1 Sleep Mode Requires Selecting ODU Tx 10 MHz on Remote VSAT Tab . . . . . . . . . . . . 17
iDX Release 3.3.2.2 Not Compatible for NMS Fresh Installation on Dell R420 Server . . . . 17
Remote Survey Package Not Compatible with Network Upgrades From iDX Release 3.3.2.1 .
18
Unsupported -b Token For DB Replication In a DNMS System . . . . . . . . . . . . . . . . . . 18
X1 Remotes Do Not Support Configuring TCP Service Levels with Spoofing Disabled . . . . 18
ATDMA Return Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Software Upgrade for Network with Replication Enabled. . . . . . . . . . . . . . . . . . . . . . 19
Do Not Use Custom Key blind_feathering_enabled with iDX Release 3.3.2.0 and Beyond . 19
Release Notes
Contents
Remotes May Not Acquire on an Upstream Carrier with High Symbol Rate and Large Block
Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Remotes Drop Out of Network If M1 Is Higher than 2.3 dB Running 8PSK 6/7 . . . . . . . . . 20
Symbol Rate and Transmit IF Frequency Restrictions for Some Evolution e8350 and e800
Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Reconfiguration of Initial/Maximum Powers for Some Evolution e8350 and e800 Remotes 21
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Procedure to Reconfigure Initial and Maximum Powers . . . . . . . . . . . . . . . . . . . . 22
Evolution X7 Should Be Loaded with the Latest Software in Both Flash Partitions. . . . . . 25
Minimum Tx Gain Must Be Adjusted for Some Beam Maps . . . . . . . . . . . . . . . . . . . . . 25
Unsupported 2D 16-State Modulation Codes (MODCODs) . . . . . . . . . . . . . . . . . . . . . . 27
Upstream MODCOD, Payload, and Symbol Rate Usage Recommendations . . . . . . . . . . . 27
QoS Allocation Fairness Relative to Operating MODCOD. . . . . . . . . . . . . . . . . . . . . . . 27
Specification of Receive Line Card Center Frequency . . . . . . . . . . . . . . . . . . . . . . . . 28
Reference Clock Module (RCM-PPS) Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configuring Database Replication on NMS Backup Server . . . . . . . . . . . . . . . . . . . . . . 28
NMS Fast Fade Stats Report Higher Than Actual Count . . . . . . . . . . . . . . . . . . . . . . . 28
Power Requirements for Multichannel Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Line Card Power Usage Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Single Channel Receive Line Card Must Be Reset After Carrier Changes . . . . . . . . . . . . 29
TRANSEC Networks Require SHA2 Key Exchange for Remote and Line Card Connections . 30
Bug Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Bugs Fixed in iDX Release 3.3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
42499, 42305 PP Sarmt Process Terminates Due to Memory Leak . . . . . . . . . . . . . . . . . . 31
42493 Inroute Center Frequency of the Modulated Carrier Exhibits Spurious Spikes . . . . . . . 31
42484 Remote Tags Multicast Fast Path Traffic on Default VLAN with VLAN ID 1 When Two or More
Other VLANs are Configured with Tagging Enabled . . . . . . . . . . . . . . . . . . . . . . 31
42481 Custom Key to Extend Cross-Pol CW Timeout Does Not Work for X1 . . . . . . . . . . . . 32
42480 X7 and X5 Remotes Stop Responding When Pinged. . . . . . . . . . . . . . . . . . . . . . . 32
42472 MODCOD Distribution Displays Incorrectly if Remote Out of Network . . . . . . . . . . . 32
42425 iMonitor Inroute Distribution Pane Does Not Show Correct Distribution . . . . . . . . . . 32
42410 Remote Fails to Rejoin the Original IG After It Has Been Moved to a Different IG . . . . 32
42402 X3 and X5 Remotes Transmit at Unacceptably Higher Power for SCPC Carrier than TDMA
Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
42401 L2SW Mode Overrides Change to VPWSEPC After NMS Upgrade or Restart . . . . . . . . . 32
42400 Event Server Crashed with Signal 8 Arithmetic Exception . . . . . . . . . . . . . . . . . . 33
vi
Release Notes
Contents
42280 X1 Satellite Router Fails to Pass Multicast Upstream Traffic . . . . . . . . . . . . . . . . . 33

42279 odu_tx_10_mhz Value Is Incorrectly Enabled for Line Card Configured as Tx Warm Standby
33
41866 MODCOD Distribution Display for X1 Remote Incorrectly Reports Traffic. .

41579 Incorrect CIR Values Produced After VNO Modifies CIR . . . . . . . . . . . .
41297 Incorrect CPU Status Reported for X7 Remote . . . . . . . . . . . . . . . . .
41187 iSite Does Not Load or Display BUC LO Frequency . . . . . . . . . . . . . . .
31376 Duplicate Packets Observe on X7 LAN Interface . . . . . . . . . . . . . . . .
EVOFT-433 (42506) Storm Flood on Upstream Switch Due to Hair-Pinning on PP .
........
........
........
........
........
........
33
33
33
33
34
34
Bugs Fixed in iDX Release 3.3.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

42294 NMSSVR Process Crashes Due to Database Corruption After Software Upgrade . . . . . . 34
42293 Unable to Upgrade Line Cards from iDX 3.1.1.10 to iDX 3.3.3.1 with Multicast Download .
34
42253 X5 Remote Responses to Ping Exceed 15 Minutes After It Becomes the Master in a VRRP
Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
42145 Cannot Install iDX Release 3.3.2.1 Software to a New X3 Remote . . . . . . . . . . . . . 35
42090, 42122, 42017 SARMT Process Crashing on the PP Blade . . . . . . . . . . . . . . . . . . . 35
41918 X5 Roaming Remote Resets Due to FPGA Memory Leak From Beam Switching . . . . . . 35
41915 X1 Remote with cRTP Enabled Does Not Pass DTMF Tones (RFC 2833) . . . . . . . . . . . 35
41882 Event Server Unable to Detect Event Messages After X1 Upgrade . . . . . . . . . . . . . . 35
41881 X1 Remotes Report Unexpected options file received During Upgrade . . . . . . . . . 35
41852 Spoofing Not Enabled Automatically When Creating New Reliable Service Level . . . . . 36
41850 Changing Symbol Rate Causes e150 Remotes to Go Incomplete . . . . . . . . . . . . . . . 36
41847 X7 Remote Cannot Disable Spoofing on Layer 2 TCP Traffic . . . . . . . . . . . . . . . . . 36
41802 XLC-M (SCD Mode) and XLC-11 Line Cards Do Not Work with Wideband Frequencies . . 36
41777 No Automatic Cleanup for /tmp/build_package Directory . . . . . . . . . . . . . . . . . . 36
41774 iMonitor Time Plan Log File Shows Corrupt Minute Values . . . . . . . . . . . . . . . . . . 36
41728 Upstream QoS Stats Display No Data Under the VR Default Profile . . . . . . . . . . . . . 37
41639 iMonitor Control Panel Does Not Indicate Correct X7 Power Supply . . . . . . . . . . . . . 37
41630 Unable to Modify/Delete Previously Existing Static Routes After iDX 3.3.2.1 Upgrade . 37
41557 Mismatched Error Message in iBuilder When Deleting a Remote Instance . . . . . . . . . 37
41352 Group QoS Stats Window in iMonitor Shows Incorrect VR ID . . . . . . . . . . . . . . . . . 37
41298 iBuilder Accepts Incorrect L2oS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 37
41282 iMonitor Incorrectly Shows TxTDMATrafficMissing for All Network Remotes . . . . . . . . 37
41200 X1 MAC Address Table Entries Do Not Expire . . . . . . . . . . . . . . . . . . . . . . . . . . 38
41160 Remote Antenna Components Assigned to VNO Site Not Visible in iBuilder . . . . . . . . 38
41114 X1 Remote Remains in Idle/Dormant State with Layer 2 Classification Issue . . . . . . . 38
40949 iMonitor Does Not Update SCPC Carrier Maximum Power Levels . . . . . . . . . . . . . . 38
40379 X7 Satellite Router Fan Status Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
40080 iMonitor Upstream Carrier Information Does Not Change Automatically . . . . . . . . . . 38

EVOFT-286 Incorrect Limits for FLL DAC Errors Cause X7 Remotes to Fail . . . . . . . . . . . . . 39
EVOFT-280 Unable to Upgrade TRANSEC Network Due to Missing tlsSwitch Script . . . . . . . . 39
Release Notes
vii
Contents
EVOFT-221 Modem Ignores OpenAMIP ACU Input When Configuring SCPC Return . . . . . . . . . 39
EVOFT-210 (42506) Storm Flood on Upstream Switch Due to Hair-Pinning on PP . . . . . . . . . 39

42473 Activating Multiple IGCs Causes PP Blades to Stop Sweeping. . . . . . . . . . . . . . . . . 39
42419 Inroute Center Frequency of the Modulated Carrier Exhibits Spurious Spikes . . . . . . . 39
42305 PP Sarmt Process Terminates Due to Memory Leak . . . . . . . . . . . . . . . . . . . . . . 40
42376 X1 Remote Randomly Experiences Packet Loss . . . . . . . . . . . . . . . . . . . . . . . . . 40
42272 X7 and X5 Remotes Stop Responding When Pinged. . . . . . . . . . . . . . . . . . . . . . . 40
42189 X1 Satellite Router Fails to Pass Multicast Upstream Traffic . . . . . . . . . . . . . . . . . 40
42076 Custom Key to Extend Cross-Pol CW Timeout Does Not Work for X1 . . . . . . . . . . . . 40
41696 Remote Tags Multicast Fast Path Traffic on Default VLAN with VLAN ID 1 When Two or More
Other VLANs are Configured with Tagging Enabled . . . . . . . . . . . . . . . . . . . . . . 41

42157 iMonitor Incorrectly Shows TxTDMATrafficMissing for All Network Remotes . . . . . . . . 41
42142 X5 Remote Responses to Ping Exceed 15 Minutes After It Becomes the Master in a VRRP
Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
42135 X1 Remote Acknowledges Invalid Unexpected Options File Received Messages . . . . 41
42134 X1 Remote Fails to Acknowledge Successful Software Upgrade . . . . . . . . . . . . . . . 41
42130 NMSSVR Process Crashes Due to Database Corruption After Software Upgrade . . . . . . 42
42129 X1 Remote with cRTP Enabled Does Not Pass DTMF Tones (RFC 2833) . . . . . . . . . . . 42
42124 Lat Server ICMP Requests Fail to Reach The Remote . . . . . . . . . . . . . . . . . . . . . 42
42085 Mismatched Error Message in iBuilder When Deleting a Remote Instance . . . . . . . . . 42
42017 The SARMT Process Resets Due to Memory Over Consumption . . . . . . . . . . . . . . . . 42
42011 X5 Roaming Remote Resets Due to FPGA Driver Memory Leak From Beam Switching . . 42
41995 iMonitor Reports Remote Has Timed Out Even When The Remote is Still Active . . . . . 42
41981 iMonitor Fails to Generate Historical IP Statistics for Remote Instances with NetModemID >
100000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
41943 Cannot Install iDX Release 3.3.2.1 Software to a New X3 Remote . . . . . . . . . . . . . 43
41814 Unable to Modify/Delete Previously Existing Static Routes After iDX 3.3.2.1 Upgrade . 43
41176 Frequencies Above 1450 MHz Use Incorrect I/Q Offset Value From the Calibration File 43

41832 Failed to Reset X7 Remotes Using the TCP/UDP Reset Options in iBuilder . . . . . . . . . 43
41665, 41732, 40799 iMonitor Inroute Distribution Pane Does Not Show Correct Distribution . 43
41628 Updated Bootloader Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
41623, 39970 Round Trip Delay Not Calculated Correctly Based on Acquisition Aperture . . . . 44
41608, 40749 iBuilder Revision Server Does Not Properly Update the Actual Status of Remotes 44
41577 Editing Static Route Setting Does Not Work Consistently . . . . . . . . . . . . . . . . . . . 44
41557 When Deleting Modem Instance iBuilder Error Message Points to Different Modem . . . 44
41553 High Latency Reported When Applying Network Changes . . . . . . . . . . . . . . . . . . . 44
41548 X7 Fails to Update BUC Local Oscillator Freq in Web iSite . . . . . . . . . . . . . . . . . . 45
41490 ActiveSoftwareVersion is Not Updated for All Remote Instances When Physical Remote is
Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
viii
Release Notes
Contents
41405 X1 Remote May Stop Passing TCP Traffic After 49 Days in Network . . . . . . . . . . . . . 45
41393 X7 Memory Leak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
41370, 41649, 41554 iBuilder Add Rule Window Does Not Allow IPv4 Network Address
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
41365 X3/X5 SCPC Remotes Lose Downstream Lock with "RemoteTxSCPCLockLost" Messages . 45
41362 SSH Into X7 Remotes from Other Devices Behind the LAN Port Did Not Work Unless MTU was
Changed to 1504 from the Default 1506 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
41358 X1 Unable to Download or Upload File Using Specific FTP Program . . . . . . . . . . . . . 46
41356 (41354) Rx00 FPGA Image Not Installed on XLC-10 . . . . . . . . . . . . . . . . . . . . . . . 46
41336 E800 and E8350 Transmit DC Power Cannot Be Turned OFF . . . . . . . . . . . . . . . . . 46
41335 Potentially Incorrect Tx Power for e8350, e800, and e850mp Remotes in RF Network . 46
41324 Remote Service Group Configuration Lost when Multiple Remote Instances Modified
Simultaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
41323 NMS Server Occasionally Crashing Due to Lack of Memory . . . . . . . . . . . . . . . . . . 47
41322 Latency Server Continually Pings and Reports Latency Timeouts for an Offline Remote 47
41321 iMonitor Incorrectly Displays Remote Model Type When Displaying L1 or L2 Events for X1
Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
41318 Rate Controller Timer May Cause Some TCP Sessions To Be Incorrectly Rate Shaped for X1
Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
41308 PP Side Assembler Does Not Correctly Assemble TCP Segments Causing Resets to TCP
sessions for X1 Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
41302 16-Bit Number Overflow Caused Configuration Database Issues . . . . . . . . . . . . . . . 47
41301 Demand from Idle VRs Can Go Very High When Sticky Demand is Enabled . . . . . . . . . 47
41291, 41197 Satellite Routers Randomly Not Acquired Into the MCD Mode Network with Inclined
Orbit Satellite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
41275 NMS Database Not Updated When Idle and Dormant States Change for Added Remote . 48
41273 check_db.pl script Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
41270 X3/X5 Remotes Could Produce a Small Center Frequency Spike on SCPC Return . . . . . 48
41246, 41431, 41349 X7 Remote is Missing beam_state.opt File After Upgrade. . . . . . . . . . 48
41221 OpenAMIP 'X' Command Unintended Limitation . . . . . . . . . . . . . . . . . . . . . . . . . 49
41184, 39823 iBuilder Apply Configuration PushRemote-Side with Reset (UDP) Not Working 49
41183, 40220, 40123, 39948 Changing Maximum MODCOD of Network Can Cause Nominal
MODCODs for Remotes to Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
41171 iMonitor Remote Availability Report Shows Incorrect Data . . . . . . . . . . . . . . . . . . 49
41170 Increased NMSSVR Virtual Memory Use Due to Hanged NMS Clients May Cause NMSSVR Crash
50
41169 Memory Corruption When Adding Multiple Remotes In The Network . . . . . . . . . . . . 50

41143 Flash Fails With Multicast Package Download to More Than 150 Remotes . . . . . . . . . 50
40913 Incorrect NCR Time Reporting from SCD-TDMA Line Card Causes Inroute Timeplan Problems
50
40878 X3/X5 Remotes Drop Priority Packets Under Congestion on SCPC Return Channel . . . .
40802 A Few Hundred Upstream TCP Sessions Cause X1 Modem to Reset . . . . . . . . . . . . .
40800 iMonitor Bandwidth Legend Mismatch for Downstream QoS Stats . . . . . . . . . . . . . .
40791 GPS Input Validation Feature Prevents Remotes from Obtaining LATLONG from an ACU
40772 X1 Remote Unable to Establish Link Layer After Power Cycle . . . . . . . . . . . . . . . .
Release Notes
50
51
51
51
51
ix
Contents
40642 NMS Statistics Server Process Might Crash Under Certain Conditions . . . . . . . . . . . . 51
40640 X1 Remote Reboots Under Heavy Traffic Combination of TCP Software Download and User
TCP Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
40605, 38560 OpenAMIP Reflectors Share Elevation and Gain Parameters . . . . . . . . . . . . . 52
40602 EVTSVR Maintains Prior Connections After Creating New Connections to CMSVR . . . . . 52
40600 Event Server Crashes in DNMS Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
40583 NMSSVR Fails to Respond to Clients Command After iBuilder and iMonitor Logins Fail . 52
40577 Backup GKD Server Option File Overwritten When Database is Restored . . . . . . . . . 52
40552 NMS Upgrading to iDX Release 3.2.3 or iDX Release 3.3 Overwrites All Customized Hunt
Frequency Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
40506 Revision Server Does Not Update X7 Remote Status After Upgrade . . . . . . . . . . . . . 53
40510 Cannot Change Serial Number of Remote Cloned from Roaming Remote in iBuilder . . . 53
40358 iMonitor Historical SNR Graph in DVBS2 Stats Does Not List Data and Only Displays SNR Plot
53
40347, 38247 iMonitor Satellite Router ACM Gain Data Reporting Issue . . . . . . . . . . . . . . 53
40270 Edit Service Level Dialog Box GUI Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
40224, 40065 iSite: Retrieved Options File Cannot Be Read in Notepad . . . . . . . . . . . . . . 53
40221, 33901 Unexpected MIR/CIR Changes Pending Triggered After Changing Translation
Frequency of LNB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
40214, 32149 iBuilder: Idle and Dormant States May Still Be Enabled After Disabling in iBuilder .
54
40152 X1 Remote Continues to Demand Slots Even After All TCP/UDP Traffic Has Stopped . . 54
39958, 38375 Mobile Remote Fails to Receive Correct Maplet Updates While Crossing the AntiMeridian Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
39935 SCD Line Cards Require Reset to Handle Real-Time Carrier Updates . . . . . . . . . . . . 54
39932 iBuilder LNB Stability Field is Missing the MHz Unit Reference . . . . . . . . . . . . . . . 55
39115 iMonitor GQoS Distribution Tab Does Not Display CIR, MIR or Cost Data . . . . . . . . . . 55
38332 Confusing iMonitor Command Buttons for Downstream/Upstream GQoS Statistics . . . . 55
38036 iMonitor ATDMA Stats Timeplan Window Incorrectly Reports 64000 Traffic Slots . . . . . 55
35619, 32703 When the Main Downstream and Alternate Downstream Were Identical, X1 Remotes
Did Not Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

41218 e150 Incorrect Downstream Bandwidth allocation Due to Wrong MODCOD . . . . . . . . 56
41182, 40967 Falcon Crashes When Processing igmpv3 Membership Report . . . . . . . . . . . . 56
41156, 41707 iMonitor Error Message from Remote Flash is Truncated . . . . . . . . . . . . . . . 56
41145 X7 Transmits 27 MHz by Default Starting with iDX Release 3.2.2.7 . . . . . . . . . . . . . 56
41141 Remote Displayed Network Key as Clear Text in the Console . . . . . . . . . . . . . . . . 56
41133, 41052 Remote Terminals Unable to Establish SSH Connection to Other Devices Following
Upgrade to iDX Release 3.2.3.0 and Later Releases . . . . . . . . . . . . . . . . . . . . . . 57
41132, 41067 Some Remotes Randomly Enter Offline State . . . . . . . . . . . . . . . . . . . . . 57
41124 Remote Does Not Transmit on All Assigned TDMA Slots . . . . . . . . . . . . . . . . . . . . 57
41120 Incorrect DVB-S2 Overhead Estimation Causing Increased Latency . . . . . . . . . . . . . 57
41119 SADA Process Allocates Double Minimum Information Rate. . . . . . . . . . . . . . . . . . 58
40846 Remotes Log Out of Network When Minimum C/N0 is Not Met . . . . . . . . . . . . . . . . 58
Release Notes
Contents
40393 iMonitor Shows Only One Day of Historical Data for Downstream QoS Service Level Stats .
58
37871, 37782 NMS Reports Larger Latency Spike When Upstream Time Slots Usage Close to 100%
58
Bug Fixes in iDX Release 3.3.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Data Path Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
41263 X1 Packet Segments Are Not Correctly Assembled by the PP Side Assembler . . . . . . . 59
Bug Fixes in iDX Release 3.3.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Data Path Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
40438 X1 Remote Fails to Reacquire Into the Network After a Temporary Outage . . . . . . . . 59
Bugs Fixed in iDX Release 3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Data Path Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
40234, 40202, 40180 Evolution X1 or e150 May Not Acquire in Inroute Group with Unsupported
Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
NMS/Reporting Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
40398, 39852 iBuilder: Users without GQoS Planning Permission Cannot Assign Remote Service
Profile After Moving a Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
40322, 40021, 39603, Roaming Remotes Generate Large Number of State Changes To and From
Elsewhere State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
40300, 38249 iMonitor Displayed Alarm Icon for the Remotes in Offline State . . . . . . . . . . 60
40259, 40208 iBuilder: Configuration Server May Crash When Transponder is Modified . . . . . 60
40205, 40178 iBuilder: Change to Acquisition Aperture Does Not Cause Changes Pending for Line
Cards in Single Channel Receive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
40204 NMS Open Port Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Known Issues in iDX Release 3.3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
42530 X1 Upgrade to iDX Release 3.3.2.1 Fails Using iBuilder TCP Download Feature . . . . . . 63
42512 Mobile Remotes May Acquire into Network Before Receiving a Valid New GPS Input . . 63
42509 Changes Pending Observed at Remote When No Changes Made . . . . . . . . . . . . . . . 63
42503 iBuilder Spacecraft Elements Missing When Logged in as VNO User . . . . . . . . . . . . . 63
42498 After Automatic Failover for Rx Only Line Card Changes Pending Observed and Remote Does
Not Acquire into Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
42470 Applying Multiple Configurations Causes NMS Server and Revision Server to Crash . . . . 64
42411 Cross Polarization Start and Stop Buttons Not Fully Functional on X1 Web iSite . . . . . 64
42340 iMonitor ATDMA Stats Timeplan Incorrectly Displays Total Slots. . . . . . . . . . . . . . . 64
41940 Tx Line Card Replacement Not Visible to VNO on iBuilder Tree . . . . . . . . . . . . . . . 64
EVOFT-422 RoHC Compression with UDP Enabled Does Not Reliably Pass UDP Traffic Upstream .
65
EVOFT-414 Incorrect 20 VDC Output Measured at X7 Second IFL Port with LNB Configured for 13
V or 18 V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Release Notes
xi
Contents
Known Issues in iDX Release 3.3.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

42437 Enabling L2oS at Protocol Processor Disables Layer 3 Compression Options on Remote
Information Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
42435 L2oS Advanced GRE or IP-in-IP Compression Profiles Causes SARMT to Crash . . . . . . . 65
42432 Network Remotes Do Not Receive MCFPE Traffic After Multicast Encryption is Disabled Then
Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
42401 L2SW Mode Overrides Change to VPWSEPC After NMS Upgrade or Restart . . . . . . . . . 66
42398 Certain Idle/Dormant States Causing Incorrect Slot Allocation for Remotes . . . . . . . 66
42394 Protocol Processor SVNs Tab Incorrectly Shows Reserved outer SVN ID for L3 Tag on Layer
3 VLAN After L2OS is Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
42391 Changing Service Level Protocol Generates Incorrect Options File . . . . . . . . . . . . . 67
42387 Unable to Modify All Instances of a Mobile Remote After Modifying GPS Input Parameters
at iBuilder Geo Location Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
42386 Mobile E8350 and X5 Remotes Not Accessible with Baud Rate Set in iBuilder Geo Location
Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
42385 iMonitor Shows Remote in Rx Only Mode Before iBuilder Applies Hub/Remote-Side Changes
67
42371
42360
42358
42349
42337
X7 Ignores Wakeup Service Level Trigger for Layer 2 Traffic . . . . . . . . . . . . . . . . . 68

iBuilder Does Not Accurately Show Remote Upstream MIR . . . . . . . . . . . . . . . . . . 68
X1 with SDT Mode of Access Incorrectly Transmits SNAP/LLC Frames OTA . . . . . . . . 68
Web iSite Does Not Show Layer 2 SVNs for X7 Remote . . . . . . . . . . . . . . . . . . . . 68
ATDMA Remotes Idle and Dormant States Cannot Be Set Lower Than 1 Slot Per 8 Frames .
68
42333 Layer 3 VLAN Traffic without Outer Tag Passes in QinQ SDT Layer 2/Layer 3 Hybrid Mode .
68
42331 No Symbol Rate Range Check for Rx2 at iBuilder VSAT-2 Tab . . . . . . . . . . . . . . . . 69
69
42296 iBuilder Allows Configuring MCFP Encryption on Both X7 Remote Rx Ports . . . . . . . .

42277 iBuilder Does Not Show VNO User Owns Added Blade . . . . . . . . . . . . . . . . . . . . .
42255 Queue Depth Remains Unchanged After Selecting Reliable Service Level Type . . . . . .
42247 iBuilder Cannot Create a PP When an Existing PP Uses the SI Table Default Multicast IP
Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42078 PP Does Not Assign Nominal Carrier Based on Maximum C/N . . . . . . . . . . . . . . . .
42059 Multicast Fastpath Streams Incorrectly Added to Multicast Profile . . . . . . . . . . . . .
41891 Remote Unable to Retrieve Hub Side and Remote Side Options Files . . . . . . . . . . . .
41373 Layer 3 X1 Remote Passes Tagged Packets Upstream in Untagged Mode . . . . . . . . . .
41369 iBuilder Add Rule Window Allows IPv6 Address Prefix of 0 . . . . . . . . . . . . . . . . . .
41165 X7 Switch Port Only Passes Ethertype 8100 When Changed from VLAN to TRUNK . . . .
41153 X7 Remote Priority Service Level Loading Issue . . . . . . . . . . . . . . . . . . . . . . . .
40812 X7 Does Not Support MTU=1540 in L2oS Mode . . . . . . . . . . . . . . . . . . . . . . . . .
38332 Inoperable Buttons on iMonitor Downstream/Upstream Group Stats Screen . . . . . . .
69
69
69
70
70
70
70
70
71
71
71
71
71
xii
Release Notes
Contents
EVOFT-442 (42088) Queue Depth Value Incorrectly Sets As 250ms When Reliable Option is Enabled
in the Service Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

42411 Cross Polarization Start and Stop Buttons Not Fully Functional on X1 Web iSite . . . . . 72
31376 Duplicate Packets Observe on X7 LAN Interface . . . . . . . . . . . . . . . . . . . . . . . . 72
42291Center Frequency Changes for XLC-M Line Card Configured with SCPC MCD When Upgrading
From iDX 3.2.2.7 to iDX 3.3.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
73
42216 Unable to Create a New PP Controller in iBuilder When an Existing One is Using the Default
SI Tables Multicast IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
42139 Activating Multiple IGCs Causes the Network to Switch Between IGCs and Temporary
Outages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

42136, 41802 XLC-M (SCD Mode) and XLC-11 Line Cards Do Not Work with Wideband Frequencies
74
41777 No Automatic Cleanup for /tmp/build_package Directory . . . . . . . . . . . . . . . . . . 74

41696,41697, 41458 Remote Tags Multicast Fast Path Traffic on Default VLAN with VLAN ID 1
When Two or More Other VLANs are Configured with Tagging Enabled . . . . . . . . . . . 75
41685, 41416 Upstream QoS Statistics Do Not Match SAT Traffic If Inroute Carrier Payload is
Changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
41684 Remote Goes to Incomplete State When Moved to SCPC Carrier . . . . . . . . . . . . . . 75
41658 Certain QoS Matching Rules Do Not Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
41654, 41843 iBuilder Spacecraft Elements Missing When Logged in as VNO User . . . . . . . . 75
41643 X1 Upgrade to iDX Release 3.3.2.1 Fails Using iBuilder TCP Download Feature . . . . . . 76
41620 Enable NAT Checkbox is Disabled for e150 Remote . . . . . . . . . . . . . . . . . . . . . . 76
41579 Incorrect CIR Values Produced After VNO Modifies CIR . . . . . . . . . . . . . . . . . . . . 76
41569 Mobile Remotes May Acquire into Network Before Receiving a Valid New GPS Input . . 76
41540 Stopping a Revision Server Remote Package Download Hangs Revision Server Dialog Box .
76
41497 SAT Traffic Graph Displays Incorrect Real Time After iBuilder Changes . . .
41373 Layer 3 X1 Remote Passes Tagged Packets Upstream in Untagged Mode . . .
41329 iBuilder May Crash or Hang with 12 or More Open Control Panels . . . . . . .
41274 Upstream Network Subnet Mask Filter Rule for X1 Remote Does Not Work .
41095 PP Sends Traffic to Absent Remote Side Local LAN Device . . . . . . . . . . .
38986 iBuilder Does Not Enforce Limit of 32 Carriers for Inroute Groups . . . . . .
34713 Rx Hub Line Card Digital AGC Transient Effects During MODCOD Switchover
.......
.......
.......
.......
.......
.......
.......
77
77
77
77
77
77
78

41153 Falcon-Based Remote Priority Service Level Loading Issue . . . . . . . . . . . . . . . . . . 78
Known Issues in iDX Release 3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Data Path Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Release Notes
xiii
Contents
40399, 39823 iBuilder: Apply ConfigurationPush Remote-Side with Reset (UDP) Not Working 78
40394 Time Until Beam Switch Missing from Systray Message . . . . . . . . . . . . . . . . . . . . 79
40321 Link Encryption Fails for X1 Satellite Router When Implementing Geographic Redundancy
79
40069 Data Missing Warning on Remotes in Inclined Orbit Network . . . . . . . . . . . . . . . .

39974 Upstream CRC Errors When Using High-Speed Comms On The Move . . . . . . . . . . .
39971 Single Channel TDMA Line Card Must Be Reset After Carrier Changes . . . . . . . . . .
39681 Fade Slope Margin (M1) Negative After Upgrade to iDX Release 3.3 . . . . . . . . . . .
39170 Standby Line Card with Changes Pending Cannot Complete Automatic Failover . . . .
38751 SCPC Remotes Cannot Acquire After Change to Initial Power . . . . . . . . . . . . . . .
38634 Remotes on Low C/N0 Upstream Carriers May Not Receive Correct Slot Allocation
When CIR Is Oversubscribed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38633, 37866 Remotes on Upstream Carriers with Low C/N0 May Not Receive Correct
Cost-Based Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38572 Remotes on SCPC Return Channels with Spreading Factor 4 or 8 and Block Size
438 Bytes May Not Join the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38463 Multicast Encryption Enabled without Link Encryption License Causes Remotes to
Drop out of Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38002 Over Correction in Frequency Offset Occurred When COTM Was Set to Avionics
and Two or More Remotes Were Added . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36021 All Protocol Processor Processes Down After Cycling Power on Upstream and Tunnel
Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28422 Adding Incomplete Line Card to Inroute Group Can Cause Network Outage . . . . . . .
27082 Remote May Switch to Beam Even if Satellite is Below Minimum Look Angle . . . . . .
.
.
.
.
.
.
79
79
80
80
80
81
. 81
. 81
. 81
. 82
. 82
. 82
. 82
. 83
NMS/Reporting Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
40442, 38333 Upstream QoS Stats Display No Data Under the VR Default Profile . . . . . . . . . 83
40422 iBuilder: Incorrect Revision Server Mode Status After Upgrade . . . . . . . . . . . . . . . 83
40411 iMonitor Conditions Pane Does Not Display Historical Severity Correctly . . . . . . . . . 84
40398, 39852 iBuilder: Users without GQoS Planning Permission Cannot Assign Remote Service
Profile After Moving a Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
40388 iBuilder: No Pending Changes After Enabling/Disabling RIPv2 . . . . . . . . . . . . . . . . 84
40379 X7 Satellite Router Fan Status Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
40350, 38764 iBuilder CIR/MIR Configuration for a Set of Satellite Routers Does Not Work . . 84
40213, 36617, 36105 iMonitor: SATCOM Statistics Interval May Not be Precisely 60 Seconds . . 85
40146 iBuilder: Modifying Initial Power on SCPC Remote May Cause VLAN Mode to Change . . 85
40070 iBuilder: Guard Interval Not Updated in Network Options File After Carrier Symbol Rate
Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
40040, 40082 iMonitor: Nominal Carrier of Remote May Be Mis-Identified on Upstream C/N0 and
Thresholds Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
39203 Web iSite Does Not Show Statistics When GPS Input is Selected for Antenna . . . . . . . 86
39181 When Logged in as VNO Super User, Standby Line Cards IP Address Displays 0.0.0.0 . . 86
38994 iMonitor: Assigned SCPC Carriers Are Not Selected in RX Line Card When Logged in as
Newly-Created VNO User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
38970, 40232 NMS Server Crashes When Deleting an Active VNO User . . . . . . . . . . . . . . . 86
38950 Original VLAN ID Changes on X7 Remote When DNS Cache is Enabled . . . . . . . . . . . 86
xiv
Release Notes
Contents
38672 iBuilder: Disabling FLLDacErrors Warning Type Causes Receive Line Card Carrier to
Be Unassigned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38530 iMonitor: False Warning for Erroneous Report of CRC8 and CRC32 Errors on Acquisition
38493 iMonitor Probe Warning: Modulated Carrier Interferes With Existing 5% ROF Carrier . .
38437 Using Console Commands to Change Tx Frequency Disables RF Energy. . . . . . . . . . .
38251 iBuilder Falsely Reports Failed to Assign Standby Error Message after Successfully
Assigning Standby Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37042 iMonitor Shows Tx Bytes and Attempts = 0 in Tx Line Card Stats . . . . . . . . . . . . . .
36113 Remote Warning Remains in Active Condition When Remote is De-activated . . . . . . .
35904 SNMP Returns Invalid Result For Out-of-Network Remotes . . . . . . . . . . . . . . . . . .
35621 X1 Satellite Router Transmit LED is Green when Transmit is Disabled . . . . . . . . . . .
34442 DSCP Marking Not Working as Expected . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34396 iMonitorSAT Traffic Graph Not Appearing Correctly with Respect to X-Axis . . . . . . .
26749 iBuilderChanges to VLAN Subnet and Gateway at PP Blade Not Shown . . . . . . . . . .
86
87
87
87
87
87
88
88
88
88
88
88
Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Downloading Required Files for iDX Release 3.3.x.x . . . . . . . . . . . . . . . . . . . . . . . . . 89
iDirect software download instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
iDirectGov Software Download Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Installation/Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
DVB-S2 Outbound with TPC Coded Inbound Carriers. . . . . . . . . . . . . . . . . . . . . . . 91
NMS Service Levels May Exceed Maximum Supported . . . . . . . . . . . . . . . . . . . . . . 91
Default NMS Profile Not Correctly Populated after Fresh Install . . . . . . . . . . . . . . . 91
Check Inroute Group Uplink Control Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 91
iDX Release 3.3.2.5 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Installation/Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
iDirect Software Download Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
iDirectGov Software Download Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Installation Instructions iDX Patch Release 3.3.2.5 . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Replace the Evtsvr Executable File on the NMS Server . . . . . . . . . . . . . . . . . . . . . 95
Replace the Sarouter Executable File on the PP Server . . . . . . . . . . . . . . . . . . . . 96
Backup Old Remote Images and Copy New Remote Images to NMS Directory . . . . . . 97
Install Patch on Evolution e8350 and e850MP Remotes . . . . . . . . . . . . . . . . . . . . 98
BSP Package Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Release Notes
xv
Contents
Remote Package Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Reset the Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
iDX Release 3.3.2.4 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
101
Installation/Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Installation Instructions iDX Patch Release 3.3.2.4 . . . . . . . . . . . . . . . . . . . . . . . . . 101
Download and Copy the SARMT File to the PP Server . . . . . . . . . . . . . . . . . . . . . 102
Download and Copy Remote Software Packages to the NMS Server . . . . . . . . . . . . 102
Replace the SARMT Executable on the PP Servers . . . . . . . . . . . . . . . . . . . . . . . 103
Backup Old Remote Images and Copy New Remote Images to NMS Directory . . . . . 104
Install Patch on Evolution X7 Remotes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Remote Package Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Reset the Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Install Patch on Evolution X3, X5, e8350 and e850MP Remotes. . . . . . . . . . . . . . 106
BSP Package Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
109

Download and Copy Software Packages to the NMS Server . . . . . . . . . . . . . . . . . 110
Install Patch on Evolution X1 (Indoor and Outdoor) and X7 Remotes . . . . . . . . . . 111
Install Patch on Evolution X5 Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
BSP Package Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
115
xvi
Release Notes
Contents

Install Patch on Evolution E150 and X1 (Indoor and Outdoor) Remotes . . . . . . . . . 117
119

Install Patch on Evolution E150 and X1 (Indoor and Outdoor) Remotes . . . . . . . . . 121
Release Notes
xvii
Contents
xviii
Release Notes
About
Purpose
The Release Notes introduces a specific release of the iDirect software by providing a
summary overview of new product features and enhancements. It lists supported hardware
and provides upgrade paths. The Release Notes provides important information about the
software and also describes important bug fixes and outstanding known issues. Finally, the
Release Notes provides instructions for downloading and installing the release software.
Intended Audience
This document is intended for use by network operators and network architects that work
with the iDirect network system.
Contents Of This Guide

This document contains the following sections:
New Features and Enhancements
Supported Features and Hardware
Important Notices
Bug Fixes
Known Issues
Installation Instructions
iDX Release 3.3.2.5 Patch Installation
Release Notes
xi
About
This section illustrates and describes the conventions used throughout this document.
Convention Description
Example
Used when the user is required to

enter a command at a command
line prompt or in a console.
Enter the command:
Terminal
Output
Used when showing resulting

output from a command that was
entered at a command line or on a
console.
crc report all
Screen
Reference
Used when referring to text that

appears on the screen on a
Graphical User Interface (GUI).
1. To add a remote to an inroute group, right-click

the Inroute Group and select Add Remote.
Command
Used when specifying names of

commands, menus, folders, tabs,
dialogs, list boxes, and options.
Hyperlink
Used to show all hyperlinked text

within a document or external
links such as web page URLs.
cd /etc/snmp/
8350.3235 : DATA CRC [ 1]

8350.3502 : DATA CRC [5818]
8350.4382 : DATA CRC [ 20]
The Remote dialog box has a number of userselectable tabs across the top. The Information
tab is visible when the dialog box opens.
For instructions on adding a line card to the
network tree, see Adding a Line Card on
page 108.
WARNING: A warning highlights an essential operating or maintenance procedure,

practice, condition, or statement which, if not strictly observed, could result in
injury, death, or long term health hazards.
CAUTION: A caution highlights an essential operating or maintenance procedure,
practice, condition, or statement which, if not strictly observed, could result in
damage to, or destruction of, equipment or a condition that adversely affects
system operation.
NOTE: A note is a statement or other notification that adds, emphasizes, or
clarifies essential information of special importance or interest.
Getting Help
The iDirect Technical Assistance Center (iDirect TAC) and the iDirect Government Technical
Assistance Center (iDirectGov TAC) are available to provide assistance 24 hours a day, 365
days a year. Software user guides, installation procedures, FAQs, and other documents that
support iDirect and iDirectGov products are available on the respective TAC Web site:
Access the iDirect TAC Web site at http://tac.idirect.net
Access the iDirectGov TAC Web site at http://tac.idirectgov.com
The iDirect TAC may be contacted by telephone or email:
xii
Telephone: (703) 648-8151
E-mail: tac@idirect.net
Release Notes
About
The iDirectGov TAC may be contacted by telephone or email:
Telephone: (703) 648.8111
Email: tac@idirectgov.com
iDirect and iDirectGov produce documentation that are technically accurate, easy to use, and
helpful to our customers. Please assist us in improving this document by providing feedback.
Send comments to:
iDirect: techpubs@idirect.net
Direct Government: techpubs@idirectgov.com
For sales or product purchasing information contact iDirect Corporate Sales at the following
telephone number or email address:
Telephone: (703) 648-8000
Email: sales@idirect.net
Related Documents
The following additional iDirect documents are available on the TAC Web sites and may also
contain information relevant to this release. Please refer to these documents for additional
information on installing and using iDirect satellite network software and equipment. To
review a synopsis of a particular document, click on the listed document title.
An overview is provided for each of the following documents:
Installation, Support, and Maintenance Guide on page xiv
Hub Line Card Specifications Guide on page xiv
iBuilder User Guide on page xiv
iDirect Features and Chassis Licensing User Guide on page xiv
iDirect Hardware Matrix on page xiv
iDirect Software Features Matrix on page xv
iMonitor User Guide on page xv
Link Budget Analysis Guide on page xv
Network Upgrade Procedure on page xv
NMS Redundancy and Failover on page xvi
Release Notes on page xvi
Satellite Router Installation and Commissioning Guide on page xvi
SatManage Integration and Configuration Guide on page xvi
Software Install Guide for New Hubs on page xvii
SCAP User Guide on page xvii
Technical Reference Guide on page xvii
Web iSite User Guide on page xviii
Release Notes
xiii
About
iDirect Standard User Documents

Installation, Support, and Maintenance Guide
An Installation, Support, and Maintenance Guide is associated with each iDirect Satellite
Router. The document covers important safety and compliance information, and explains how
to install and maintain the iDirect Satellite Router. It also provides notes, and helpful tips to
assist with the successful and safe operation of the iDirect system hardware.
The Installation, Support, and Maintenance Guide is intended for use by the VSAT (Very Small
Aperture Terminal) equipment installer, system engineer, and network operator responsible
for maintaining the iDirect Network.
Hub Line Card Specifications Guide

The Hub Line Card Specifications Guide provides important information on the specifications
for Hub Line Cards such as interoperability, network configuration, interfaces, and
mechanical and environmental information.
This document is intended for use by network engineers, network operators, or anyone
responsible for making decisions or obtaining information regarding specifications or
capabilities of Hub Line Cards.
iBuilder User Guide

iBuilder is a member of the NMS client tools for working with iDirect networks. It supports
rapid and intuitive configuration of any iDirect networkincluding easily adding network
components, changing the current configuration, and downloading configurations and
software to network elements.
The iBuilder User Guide provides detailed instructions for configuring iDirect networks using
the iBuilder client application of the iDirect Network Management System (NMS).
This document is intended for use by network operators, network architects, and others that
operate or monitor iDirect networks. It is not intended for end users or field installers.
iDirect Features and Chassis Licensing User Guide

iDirect offers several types of licensed features, whereby specific license requirements are
dependent on the iDX release, specific network features, and the specific network hardware.
The iDirect Features and Chassis Licensing User Guide describes each license type in detail,
and explains how licenses are acquired and applied in iDirect networks.
The iDirect Features and Chassis Licensing User Guide is intended for use by network
operators using the iDX iBuilder/iMonitor software suite; network architects; other personnel
who operate or monitor iDirect networks; and personnel responsible for purchasing or
installing iDirect licenses.
iDirect Hardware Matrix

The iDirect Hardware Matrix is a spreadsheet view of the major iDirect hardware
componentsincluding line card, remote, and hub equipment, presented in a matrix format
xiv
Release Notes
About
that shows compatibility of hardware components and features against iDX/iDS releases from
a specific release and through the current iDX release.
The iDirect Hardware Matrix provides useful information regarding which iDX/iDS software
releases are supported on each hardware unit offered by iDirect.
This document is intended for use by network engineers, network architects, or other
personnel that is responsible for the design, engineering, and specifying of iDirect networks.
iDirect Software Features Matrix

The iDirect Software Features Matrix is a spreadsheet view of the major iDirect NMS software
features presented in a matrix format that shows the compatibility of individual features
across iDX/iDS releases from a specific release and through the current iDX release.
The iDirect Software Features Matrix is presented as a quick and comparative overview of the
major NMS software features as supported by each iDS/iDX release from iDS Release 7.0
This document is intended for use by network engineers, network architects, or any other
personnel that is responsible for the design, engineering, and specifying of iDirect networks.
iMonitor User Guide

iMonitor is a member of the NMS client tools for working with iDirect networks. This tool
provides a window into the events, conditions, and warnings of the iDX network, as well a
view of network performance, in the form of real-time and historical data and graphs.
The iMonitor User Guide provides detailed instructions for monitoring iDirect networks using
the iMonitor client application of the iDirect Network Management System (NMS). For details
on configuring iDirect networks, see the iBuilder User Guide.
This guide is intended for network operators, network architects, and other personnel that
operate or monitor iDirect networks. It is not intended for end users or field installers.
Link Budget Analysis Guide

Information presented in this guide is based on iDirect hub and remote products, and is
tailored to a specific releasefor example, iDX Release 3.1.
The Link Budget Analysis Guide provides system and network engineers with satellite modem
performance parameters that are necessary to conduct link budget analysis and accordingly
plan system resource requirements for implementing an iDirect network.
This document is intended for use by network engineers that are planning the integration of
the iDirect hub equipment in an existing teleport or Earth station.
Network Upgrade Procedure

The Network Upgrade Procedure provides procedures for upgrading the iDirect Network
Management Software (NMS) and the Protocol Processor (PP) software. It also covers
upgrading of the remotes and Hub Line Cards in iDirect networks. Each Network Upgrade
Procedure Guide provides guidelines for upgrading from one or more specific iDirect releases
to another releasegenerally to the latest release.
Release Notes
xv
About
This document provides step-by-step guidelines and procedures for necessary preparations
and for the performance of upgrading the various components of the iDirect network. These
guidelines and procedures also include necessary preparations and steps for performing
backup and restoration of the iDirect NMS databases.
This document is intended for use by iDirect network operators, iDirect network architects, or
other personnel who are planning the integration of the iDirect hub equipment.
NMS Redundancy and Failover

The NMS Redundancy and Failover document is a technical note that presents the following
procedures:
Configuring the crontab files for redundancy in a single NMS network.
Configuring the crontab files for redundancy in a distributed NMS network.
Bringing the Backup NMS server online in single NMS network.
Bringing the Backup NMS server online in a distributed NMS network.
This document is intended for use by network operators, using the iDirect NMS client software
suite (iBuilder/iMonitor/iSite); network architects, and any other personnel who operate or
monitor an iDirect network.
Release Notes
The Release Notes introduces a specific release of the iDirect software, by providing a
summary overview of new product features and enhancements. It also describes known issues
that have been resolved, as well as any outstanding issues that may be encountered. Release
Notes also outlines supported hardware and upgrade paths, and provides important notices
and instructions for downloading and installing the release software.
The Release Notes document is intended for use by network operators and network architects
that work with the iDirect network system.
Satellite Router Installation and Commissioning Guide

The Satellite Router Installation and Commissioning Guide provides detailed instructions for
installing and commissioning iDirect Satellite Routers at remote sites. The contents of this
document applies to both iNFINITI and Evolution series Satellite Routers.
This guide is intended for use by iDirect installers and for other satellite technicians tasked
with the installation and commission of iDirect Satellite Routers.
SatManage Integration and Configuration Guide

SatManage provides network operators with a consolidated view of all remotes across all
operational NMS systems; it thereby supports cross-NMS reporting. This high level visibility
greatly reduces the time required for resolving faults, especially in mobile environments.
The SatManage Integration and Configuration Guide provides setup and configuration
guidelines for use when integrating one or more NMS nodes in a SatManage system. It also
documents the various modifications required to allow a SatManage system to interrogate an
xvi
Release Notes
About
iDirect NMS. Discussions in this document assumes that a network operator has received the
SatManage server/package software and all operating systems pre-installed from iDirect.
This document serves as a configuration/integration blueprint, intended for use by SatManage
operators, iDirect Sales Engineers, as well as iDirect professional services installation teams.
It also provides a reference for network designers and system architects that are integrating
SatManage systems with one or more iDirect NMS nodes.
Software Install Guide for New Hubs

The Software Install Guide instructs iDirect network operators how to perform a fresh
installation of the iDirect software for example iDX 3.1, on a new hub (NMS and Protocol
Processor servers). The software installation media installs the iDirect software release and,
if required, an updated version of the Red Hat Linux OS and the MySQL software.
This document presents detailed procedures for installing the iDirect Network Management
System (NMS) and the Protocol Processor (PP) software; it also provides details for installing
the NMS iBuilder and iMonitor clients. It does not cover the full installation and configuration
of the iDX release software. After completing the procedures in this guide, the next step is to
build the iDirect network configuration using the additional information and procedures
contained in the iBuilder User Guide for the specific release.
This document is intended for iDirect network operators and network engineers, or any
personnel that is preparing the NMS and PP blade servers for a fresh software installation.
SCAP User Guide

The SCAP User Guide provides implementation instructions for ensuring that iDirect hub
servers such as the NMS servers and Protocol Processor Blades are implemented in compliance
with recommendations specified in the Security Content Automation Protocol (SCAP) User
Guide.
This document is intended for use by UNIX system administrators responsible for
implementing the SCAP feature on their iDirect UNIX servers.
NOTE: In iDX Release 3.2.3, and future releases, the SCAP User Guide replaces
the STIG User Guide.
Technical Reference Guide

The Technical Reference Guide provides detailed technical information on iDirect technology
and major features as implemented in a specific iDirect software release.
This document is intended for use by network operators, network architects, and anyone
upgrading to a specific iDirect software release.
Release Notes
xvii
About
Web iSite User Guide

Web iSite is used primarily for commissioning new sites and monitoring TDMA remotes from
the local LAN side. It provides configuration and real-time status/statistical information about
the Satellite Router, to which a session is established, and contains functions to help installers
perform the commissioning task for the Satellite Router.
The Web iSite User Guide presents an introduction of the Web iSite tool for working with the
supported iDirect Satellite Routers. A quick overview of Web iSite is providedincluding the
various elements of which the user interface is comprised, and the basics of how to interact
with the various pages of this Web use interface.
For details on configuring supported iDirect Satellite Routers, see the iBuilder User Guide. For
installing and commissioning Satellite Routers, see the iDirect Satellite Router Installation
and Commissioning Guide.
This document is intended for use by iDirect installers and for other field installers and
technicians that are installing and commissioning Web iSite supported Satellite Routers.
xviii
Release Notes
New Features and

Enhancements
This chapter summarizes the features and enhancements introduced in iDX Release 3.3. It
includes the following sections:
Enhancements in iDX Release 3.3.4
New Features in iDX 3.3.3.1
NMS Scalability Improvements in iDX 3.3.2.2
New Features in iDX Release 3.3.2.1
Enhancements in iDX Release 3.3.2.1
New Features in iDX Release 3.3
Enhancements in iDX Release 3.3.4

Enhancements to existing features available in iDX Release 3.3.4 include:
Second IFL for X7 Remotes - Allows an operator to configure the second receiver from the
NMS to listen to either the physical RX1 or RX2 port on X7 remotes that are licensed for a
second receiver.
iDX Release 3.3.4 also includes a number of bug fixes.

This section describes the new features in iDX Release 3.3.3.1.
Layer 2 Over Satellite

The Layer 2 over Satellite (L2oS) feature enables the satellite link to emulate an Ethernet
connection. When an iDirect network is configured for L2oS, Ethernet frames, rather than IP
packets, are transported across the satellite link. In terms of data networking, this is moving
down the stack from the traditional iDirect model of IP network layer connectivity over the
satellite (OSI Layer 3) to Ethernet link layer connectivity (OSI Layer 2).
The following are key L2oS benefits:
The satellite network is invisible to higher-layer protocols.
Seamless inter-working of:

IPv6
Release Notes
Routing protocols such as BGP and OSPF

1
Any protocols supported by network vendors can be used transparently over the VSAT
network.
The support of IEEE 802.1ad Q-in-Q VLAN tagging and tag rewrite at the remote opens up
new flexibility in the deployment and management of virtual networks.
The following iDirect features are retained, including:

Group QoS
DVB-S2/ACM and ATDMA

NOTE: The L2oS feature works with X1 and X7 remotes only.
NOTE: In L2oS Mode, Multicast does not support downstream GQoS. A large
amount of multicast traffic should use Layer 3 mode for efficiency and GQoS
conformance.
For additional information on the L2oS feature, refer to the latest revision of the iDX 3.3
Technical Reference Guide.
Layer 2 and Layer 3 Hybrid Mode

iDX Release 3.3.3.1 supports the Layer 2/Layer 3 Hybrid Mode feature to allow both Layer 2
and Layer 3 traffic to traverse a single VSAT network at the same time, sharing the same NMS,
PP stack, line cards and satellite bandwidth. In addition, each remote, either X1 or X7, can
simultaneously carry Layer 2/Layer 3 traffic, enabling an unprecedented level of flexibility.
When transported in the same network, Layer 2/Layer 3 traffic is separated by individual
Satellite Virtual Networks (SVNs). In other words, SVNs can be marked as either Layer 2 or
Layer 3 during the network configuration.
Second Demodulator on the X7-Series Satellite Routers

The second demodulator on the X7-Series satellite routers (X7, CX700, and X7-ER) provides
the ability to receive two downstream carriers simultaneously. An X7-Series satellite router
can use the second receiver to receive Multicast Fast Path streams from an overlay iDirect
network other than the primary one in which it is configured.
An X7-Series satellite router can also receive Multicast Fast Path traffic from a single
downstream only. This may be the downstream carrier of the primary network or the
downstream carrier of an alternate network received by the X7s secondary receiver. The
second downstream carrier must share the same physical receiver port (Rx1) as the primary
downstream.
A license is required to enable the second receiver on an X7-Series satellite router.
Encrypted MCFP Support on 2nd Demodulator

An X7 remote can be configured to receive encrypted Multicast Fast Path (MCFP) traffic on a
separate outbound carrier using its second receiver. A license is required to enable the second
receiver on an X7. Each network can only support its remotes to receive from no more than 1
encrypted overlay network.
Release Notes
X7-ER Satellite Router

The X7-ER Satellite Router is a powerful, highly integrated remote that built on the X7
satellite router platform to serve many complex applications. The X7-ER features a compact 1
RU rack-mount design, six LAN Ethernet ports, two ESR Router ports, a second DVB-S2
demodulator and Web iSite support making it an ideal enterprise class solution. In addition to
all functionalities found in the X7 Satellite Router, it also has a Cisco 5921 Embedded
Services Router (ESR) that functions as a stand-alone router that supports advanced routing
protocols including BGP routing.
The X7-ER Satellite Router will be available for purchase in Q4 of 2015.

This section describes the NMS scalability improvements introduced in iDX Release 3.3.2.2.
RAMDISK Addition
A RAMDISK has been added to improve memory availability and scalability for the NMS Config
server.
Memory Utilization Performance Improvement

In iDX Release 3.3.2.2, iDirect has implemented a major improvement to the serializing data
structure mechanism. Instead of allocating a large chunk of memory used for sending data to
the client, memory is allocated as needed and uses a smaller buffer. This more efficient
implementation eliminates the need for a large block of contiguous RAM when serializing data
structures and minimizes the OS overhead requirements.
Memory Increase for iBuilder and iMonitor Clients

To enhance scale capabilities of the NMS, enhancements to iBuilder and iMonitor have been
made to enable access up to 3GB of memory on Windows clients.
NOTE: Administrative privilege may be required to perform the commands
specified in this section.
To enable the 3GB switch on Windows XP or Windows 7, perform the following:
1. Click StartAll ProgramsAccessoriesCommand Prompt.
2. At the command prompt, type:
bcdedit /set IncreaseUserVa 3072
3. Restart PC.
To disable the 3GB switch, perform the following:
1. Click StartAll ProgramsAccessoriesCommand Prompt.
2. At the command prompt, type:
bcdedit /deletevalue IncreaseUserVa
Release Notes
3. Restart PC.
Terminal Security Enhancement

In this release, iDirect has implemented an additional security enhancement such that SSH
Tunnel through a remote is not possible without using the configured password.

This section describes the new features offered in iDX Release 3.3.2.1.
FIPS 186-4 Compliance

To support FIPS 186-4-2, iDirect Government implemented the OpenSSL 186-4 fix: RSA Key Fix
code base. As a result, iDirect Government will be able to submit iDX Release 3.3.2.1 for FIPS
140-2 Level 2 certification making this the first defense release certified at Level 2 (previous
certifications were Level 1).
Support for Managing Jitter Sensitive Applications

In this release, iDirect has introduced some additional capabilities to manage jitter to better
support jitter-sensitive applications like 3G cellular back-haul. Managing jitter is a balancing
act involving the satellite network, use cases, and understanding the other networking
equipment in use in the end-to-end solution. Using the newly introduced capabilities, iDirect
will work with its customers to determine the best solution in each case. These capabilities
are currently available through custom keys only. Customers should contact their SE for initial
discussion on such design.
Some of the new capabilities included in this release are:
Upstream Jitter Buffer - This is a new feature designed to reduce the timing variation
introduced by the TDMA subsystem. The jitter buffer is based on the time stamp of the
arrival and the precisely timed playback of each packet.
Full Trigger CIR for Downstream - Ability to configure a VR for full CIR triggered in the
outroute direction analogous to the inroute direction.
Bandwidth Modifiers - Custom keys to modify bandwidth demand based on the actual realtime demand for upstream and downstream.
Selective Disabling of Free Slots - Ability to disable Free Slots Allocation (FSA) on a per
remote and per VR basis.
Selective Disabling Cross Sharing - Ability to disable cross sharing on a per remote and per
VR basis.
NMS Support for Jitter Management - iBuilder support for managing jitter sensitive
applications category includes the addition of text boxes to enter newly introduced
custom keys at the VR level.
NOTE: Contact your SE or TAC for information about jitter management.
Release Notes
X7 Satellite Routers Support 50 MHz BUC Reference Tone

without Manual Custom Keys
With iDX Release 3.3.2.1, it is no longer necessary to manually enter two remote-side custom
keys to configure X7 Satellite Routers with a 50 MHz BUC reference tone. You can now select
50 MHz in the iBuilder Tree. This feature works in both Ka-band and Ku-band networks.

The section describes the enhancements to existing features or operations that are available
in iDX Release 3.3.2.1.
NOTE: All customers who wish to use Adaptive TDMA functionality in this release,
are recommended to contact their SE (Sales Engineers) to review the proposed
design and to make sure the design is implemented as per iDirect
recommendations. Implementing ATDMA without following this process may cause
undesired network implications.
ADTMA Instability Detection

To enhance instability detection, iMonitor offers a new Nominal Carrier Equivocation
Occurring warning.
Nominal Carrier Equivocation Occurring

The Nominal Carrier Equivocation Occurring warning indicates that the remote is switching
nominal carriers rapidly.
Nominal carrier equivocation can occur when the maximum configured power is not the same
as the actual maximum power at which the modem is capable of transmitting. This can occur
when remotes maximum power causes BUC saturation.
Understanding Nominal Carrier Equivocation - The PP assigns a nominal carrier to the
remote. In turn, the remote reports how much power it can provide before hitting its
configured maximum power (this is known as power headroom). If the current SNR that the
hub line card receives from the remote, plus the power headroom, enables the remote to
operate at a higher nominal carrier, then PP switches the remote to the higher carrier.
Because the remote cannot actually transmit at this power level, the line card may see CRC
errors and dropped packets. The PP seeing that the remote cannot operate reliably on this
carrier, will switch it back to the lower carrier. However, the remote will report its power
headroom and the cycle repeats.
What the Warning Means - For a specific remote, the warning indicates the inroute IDs where
nominal carrier equivocation is occurring. The PP generates the warning after at least one
transition from a higher carrier to a lower carrier within a measurement interval.
Recommended User Response - If this warning appears in iMonitor, the user should reevaluate power levels for the remote by considering the following:
The maximum power configuration of the remote vs compression point of the BUC
Whether there are carriers with a minimum C/N0 that are <0.6 dB from each other
Release Notes
The power pushed to the unit by the Uplink Control Process (UCP) vs the transmit power
levels that are returned
Using this data, the user can re-evaluate the power settings for the remote, change them,
and monitor the remote to see if equivocation has been eliminated.
Network Upgrade Improvements

iDX Release 3.3.2.1 provides the following upgrading improvements:
Remote option files are bundled together with the remote package to avoid mismatching
options and packages.
In iBuilder, in the Multicast Download dialog box at the Progress bar, download movement
displays as 0 to 100% per group of 150 remotes.
In iBuilder, Multicast Download dialog box shows state information (e.g., Flash started,
Flash complete, Rebooting OS) during download.
Distinguishes between remotes that have completed the upgrade and remotes that have
only completed the download.
X3 remotes are no longer packaged with X5 packages; X3 remotes now install with BSPs,
packages, and options files. Additionally:
BSP and Remote package for X3 are separated for X3 to manage package size better.
Atomic install prevents mismatched BSP and remote; the remote package first checks
for the right version of BSP and only then installs itself.
Unused FPGA images are deleted from line cards to free up disk space. The new package
will write the images back; however, freeing up disk space in the interim makes the
upgrade ensures a successful upgrade.
Ability for e8xxx Remotes to Generate ATDMA Waveforms in

Stand-alone Mode
iDX Release 3.3.2.1 addresses a bug fix (Bug 40677) that provides the ability to generate
from a stand-alone remote all waveforms that e8xxx remotes support. With this fix,
iDirect Government will have the ability to submit iDX Release 3.3.2.1 for Wideband
Global SATCOM system (WGS) certification to include all defense remotes except for the
e150.
New Environmental Variable Limits ACQ Sweep Messages

A new environment variable (ENV_LOG_ACQ_SWEEP) has been added to the nms_start
script located at /opt/idirect/nms/utils.
When set to the default value (i.e., either no environment variable set or set to
ENV_LOG_ACQ_SWEEP=0), no ACQ sweep messages are stored in the database.
When set to 1 (ENV_LOG_ACQ_SWEEP=1), sweep messages are stored in the archive

database.
Release Notes
Support for Large Carriers with Multi-Channel Demodulation

(MCD) Using Inclined Orbit Satellite Bandwidth
iDX Release 3.3.2.1 introduces two enhancements to allow XLC-M line cards running the MultiChannel Demodulation (MCD) image to support large carriers using inclined orbit satellite
bandwidth. The use of MCD is often preferred over single-channel demodulation (SCD) in
mobility applications due to the support of Superburst Acquisition and full Adaptive TDMA.
This enhancement:
Fully restores the 64k symbols capacity for the acquisition aperture for MCD.
Introduces the ability to disable acquisition slots on specific carriers in an inroute group.
If a network operator wants to configure a large carrier using bandwidth from a highly
inclined satellite, the required acquisition aperture may still exceed the 64k symbols
capacity of a MCD line card. In this case, the operator may choose to setup a
heterogeneous inroute group and disable the acquisition slots on the large carriers that
would have exceeded the 64k symbols limitation. This is accomplished through the use of
a Protocol Processor custom key. The disabled acquisition slot will not be re-used for data
traffic. For more information, refer to the iBuilder User Guide.

With iDX Release 3.3, iDirect introduces a number of new features to support the Evolution X1
Satellite Router. The Evolution X1 Satellite Router is a cost-effective satellite router
optimized for large, narrow band networks with small inbound channels and single client
sites. The X1 Satellite Router leverages the bandwidth efficiencies of the DVB-S2/ACM
standard and incorporates basic routing and VLAN functionality. Developed specifically to
support large-scale broadband access networks, the low-cost X1 Satellite Router is ideal for
demanding broadband applications such as SCADA, point-of-sale, and ATM.
Legacy Supported Features in iDX Release 3.3

iDX Release 3.3 inherits all the system features and capabilities present in iDX 3.2. For a list
of supported features, see the iDirect Software Feature Matrix.
NOTE: X1 feature support is backwards compatible to first-generation X1s.
AES-256 Link Encryption Support for the e150 and X1 Satellite

Routers
For iDX Release 3.3, the e150 and X1 Satellite Routers support AES-256 link encryption.
This feature requires a license on the e150 and X1 Satellite Routers. For additional licensing
information, refer to iDirect Features and Chassis Licensing Guide.
Release Notes
Compressed Real-Time Protocol Support for the e150 and X1

Satellite Routers
Compressed Real-Time Protocol (cRTP) allows a Network Operator to significantly reduce the
bandwidth requirements of VoIP flows. The iDirect implementation uses a standard header
compression scheme that includes heuristic-based RTP detection with negative cache support
for mis-identified UDP streams.
Hub Geographic Redundancy Support for the e150 and X1

Satellite Routers
For iDX Release 3.3, Hub Geographic Redundancy Support allows a stationary e150 or X1 to
operate with a backup teleport, automatically searching for the other teleport's downstream
if it loses the primary teleport's downstream.
Increase Inbound Symbol Rate to 4 Msps for e150 and X1

Satellite Routers
For iDX Release 3.3, e150 and X1 Satellite Routers transmit on an upstream TDMA carrier from
128 ksps to 4 Msps.
NAT/PAT Support for the e150 and X1 Satellite Routers

For iDX Release 3.3, the NAT/PAT feature allows an e150 or X1 to translate between public
addresses on the satellite interface and private network addresses and port numbers on the
LAN. The NMS allows for the configuration of NAT on each VLAN on an e150 or X1.
Soft Remote Lock Support for the e150 and X1 Satellite Routers
For earlier releases, the e150 or X1 only supported hard locking of the remote to a network.
For iDX Release 3.3, the soft remote lock feature provides a locking mechanism that limits an
e150 or X1 Satellite Router to a specific network. After a remote is locked with a Network Key,
it only functions in a network with the same key. For more information, refer to the Web iSite
User Guide.
NOTE: This feature is backward compatible with all deployed X1s in the field; no
hardware upgrade is necessary.
WARNING: Non-Warranty RMA charges of $250 (plus all shipping) apply to all
remotes returned to iDirect for the purpose of removing a network lock.
Support for up to Eight VLANs for the e150 and X1 Satellite

Routers
For iDX Release 3.3, the e150 and X1 Satellite Routers support eight VLANS: one management
VLAN plus seven others.
Release Notes
Extended L-Band Support for Ka-Band Deployment

In earlier releases, the L-band frequency range supported by the XLC-M, XLC-10, and XLC-11
line cards was 950 MHz to 1700 MHz. To facilitate Ka-band deployment with these line cards,
iDX Release 3.3 supports an L-band frequency range of 950 MHz to 2000 MHz. iBuilder supports
this wider range without a custom key.
Release Notes
10
Release Notes
Supported Features and

Hardware
This chapter details the supported features and hardware for iDX Release 3.3.
The following sections are included:
Supported Features
NMS Client Operating Systems
Supported Upgrade Paths
Features No Longer Supported
Supported Hardware
Supported System Interfaces
Supported Features
All major iDX feature sets are supported in this release. New features and enhancements for
this release are covered in New Features and Enhancements on page 1.
For details on which features are supported in iDX Release 3.3, refer to the iDirect Software
Feature Matrix for iDX Release 3.3. For a list of features no longer supported, see Features No
Longer Supported on page 13.
Hardware Feature Licensing Requirements

Licenses are required to enable Link Encryption for the X1 Satellite Router and the iConnex
e150 Satellite Router.
For additional licensing information refer to iDirect Features and Chassis Licensing Guide and
Managing NMS Licenses in the iBuilder User Guide.
NMS Client Operating Systems

iDX Release 3.3 NMS clients are supported on the following platforms:
Windows 7
Windows XP
Release Notes
11

Direct upgrade to iDX Release 3.3.4 is possible from the following releases:
iDX Release 3.3.2.1
iDX Release 3.3.0.0
iDX Release 3.2.3.0
iDX Release 3.2.2.7
iDX Release 3.1.1.2
iDX Release 3.1.0.3
iDX Release 3.1.0.11
iDX Release 3.0.0.3
iDX Release 2.3.1.0
Direct upgrade to iDX Release 3.3.3.1 is possible from the following releases:
iDX Release 3.3.2. x
iDX Release 3.2.2.4 - 3.2.2.7
iDX Release 3.1.0.5
iDX Release 3.0.0.3
Direct upgrade to iDX Release 3.3.2.2 is possible from the following releases:
iDX Release 3.2.2.7
iDX Release 3.2.3
iDX Release 3.1.1.2
iDX Release 3.1.0.3
iDX Release 3.3.0
iDX Release 3.0.0.3
iDX Release 3.1.0.11 (NMS only)
iDX Release 2.3.1
Direct upgrade to iDX Release 3.3 is possible from the following releases:
12
iDX Release 3.3.0
iDX Release 3.2.3
iDX Release 3.2.2.7
iDX Release 3.1.1.2
iDX Release 3.1.0.5
iDX Release 3.0.0.3
Release Notes

The following system features are no longer supported:
Sky Monitor
iNFINITI Mode
Geographic Map
External Device Monitoring via iMonitor
TPC Inbound Coding in DVB-S2 Networks
Daisy Chaining of multiple chassis
Supported Hardware
This section describes iDirect hardware supported by iDX Release 3.3, including server support
for NMS and Protocol Processor servers.
Reference Clock Module - Pulse Per Second (RCM-PPS)

To accommodate timing changes related to Adaptive TDMA and network synchronization, iDX
3.3 networks require a PPS clock source that is provided by the new Reference Clock Module Pulse Per Second (RCM-PPS). With this new requirement all chassis in iDX 3.3 networks require
the new RCM-PPS component to be installed for proper operation. The RCM-PPS modules do
not support daisy chaining of multiple chassis.
Chassis Types
The following DVB-S2 hub chassis hardware, which accommodate the RCM-PPS, are the only
iDirect chassis hardware supported by iDX Release 3.3 networks.
The iDX Release 3.3 network is supported on the following iDirect Hub chassis:
15052, 5 IF 20 Slot TDMA Hub (800 W)
15152, 5 IF 20 Slot TDMA Hub (1500 W)
12102, 4 IF 4 Slot TDMA Hub
12202, 4 IF 4 Slot Industrial TDMA Hub
Satellite Routers and Line Cards

Table 1 lists all iDirect Satellite Routers and Hub Line Cards supported in iDX Release 3.3.
Table 2 lists iDirect Satellite Routers and Hub Line Cards not supported in iDX Release 3.3.
Release Notes
13
Supported Hardware
Table 1. Supported Satellite Routers and Line Cards

Satellite Routers
X1
X3
X5
X7
X7-ER
e8350
e8350-48
e8350-FIPSL2
e8350-FIPSL2-48
iConnex e150
iConnex e800
iConnex e800-FIPSL2
iConnex e850mp
iConnex e850mp-IND with heat sink
iConnex e850mp-IND without heat sink
iConnex e850mp-FIPSL2
Hub Line Cards
XLC-10
XLC-11
XLC-M
eM1D1
eM0DM
Table 2. Unsupported Satellite Routers and Line Cards

Satellite Routers
iNFINITI 8350
iNFINITI 7300, 7350
iNFINITI 5300, 5350
iNFINITI 5100, 5150
iNFINITI 3100, 3125, 3100-NB
(Narrowband)
iConnex 700
iConnex 300,
iConnex 100
Hub Line Cards
iNFINITI M1D1
iNFINITI M0D1
iNFINITI M0D1-NB
iNFINITI M1D1-T
iNFINITI M1D1-TSS
iNFINITI 10000 series Private Hub
iNFINITI 10000 series Mini Hub
NMS and Protocol Processor Servers

The iDX Release 3.3 NMS and Protocol Processor servers are supported on the following
hardware platforms:
14
Augmentix A+R200 (4-Slot Industrial Hub only)
Dell PowerEdge 1950 III
Dell PowerEdge R420
Dell PowerEdge R610
Release Notes

This section briefly describes the various system interfaces supported by iDX Release 3.3.
Antenna Controllers
iDX Release 3.3 is fully compliant with OpenAMIP v1.6. The appropriate protocols are used to
issue antenna controller commands and are automatically selected by the software based on
the reflector configured for use with the system. The following equipment is supported:
SeaTel (DAC-97)
Orbit Marine (AL-7104)
Schlumberger
OpenAMIP Compliant Solutions
Web iSite
Web iSite is a Web-based user interface used in the commissioning of iDirect e150, X1, X7, and
X7-ER Satellite Routers. This interface provides important identifier and network information,
and supports the loading of software packages and configuration options files on the Satellite
Routers. Web iSite also supports antenna alignment and cross polarization, as well as setting
transmit power for the supported Satellite Routers.
Commissioning for other iDirect Satellite Routers requires the iVantage iSite application.
Release Notes
15
16
Release Notes
Important Notices
This chapter covers important information that should be reviewed prior to installing the
software for iDX Release 3.3.
Unsupported TRANSEC for iDX 3.3.3.x Releases

TRANSEC will not be supported for iDX Release 3.3.3.1 and onward due to the implementation
of the MCFP encryption on the X7 second demodulator. This incompatibility does not affect
any iDX 3.3.2.x releases and will be resolved in a future Evolution release.
X1 Sleep Mode Requires Selecting ODU Tx 10 MHz on

Remote VSAT Tab
For iDX Release 3.3.3.1, an X1 remote in a DVB-S2 network does not go into Sleep mode when
upstream traffic stops unless the 10 MHz reference is enabled. In iBuilder, the 10 MHz
reference is enabled by selecting ODU Tx 10 MHz in the BUC configuration dialog box on the
Remote VSAT tab.
iDX Release 3.3.2.2 Not Compatible for NMS Fresh

Installation on Dell R420 Server
Due to an adverse effect of the latest Red Hat Enterprise Linux RPM build included in the iDX
Release 3.3.2.2, the RAID controller driver included in the software is not using the latest
version. This causes an incompatibility issue for a fresh installation using the Kickstart CD of
the NMS with the Dell R420 server. This incompatibility only affects iDX Release 3.3.2.2 for a
fresh installation of the NMS software using the Kickstart CD on a Dell R420 server and will be
addressed in the next full maintenance release.
To properly install the NMS using the iDX Release 3.3.2.2 on a Dell R420 server, customers
must install the iDX Release 3.3.2.1 software first, then update the NMS to iDX Release
3.3.2.2. For the complete network upgrade instructions, refer to the latest Network Upgrade
Procedures for iDX Release 3.3.x.x document available on the TAC Web site.
Release Notes
17
Remote Survey Package Not Compatible with Network Upgrades From iDX Release 3.3.2.1
Remote Survey Package Not Compatible with Network

Upgrades From iDX Release 3.3.2.1
CAUTION: Do not use the Remote Survey Package when upgrading from iDX
Release 3.3.2.1 to iDX Release 3.3.2.2 and later.
The Remote Survey Package is not compatible for network upgrade from iDX Release 3.3.2.1
to iDX Release 3.3.2.2 and later. This is because the NMS that is running on iDX Release 3.3.2.1
does not understand the survey package, and try to attach the options file to it. This will
cause the remote upgrade to fail because the options file is being delivered before the
software package.
Unsupported -b Token For DB Replication In a DNMS

System
When setting up the Database Replication on a DNMS system using the cr8DBMaster, the -b
token, which is normally supported in a non-DMNS system, will cause replication to fail due to
MySQL access violation. Refer to the iDX 3.3 Technical Reference Guide document for
additional details.
X1 Remotes Do Not Support Configuring TCP Service

Levels with Spoofing Disabled
X1 remotes do not support TCP service level configurations with spoofing disabled because of
issues with establishing TCP traffic matching rules within the TCP service level.
An X1 remote configured this way will erroneously demand slots whenever a TCP session
matches the rule in the TCP service level. The demand is continuous and increases whenever
additional sessions hit the TCP service level. As a result, the number of unused slots will
continue to grow, unnecessarily consuming satellite bandwidth.
iDirect recommends not assigning a QoS service levels on X1 remotes when spoofing is
disabled.
ATDMA Return Channels

With the high level of flexibility and the large number of configurable parameters, designing
ATDMA inroute groups can pose challenges for a network designer. To alleviate some of the
challenges, a set of best practices will be published in the Rev D of the iDX 3.3 Technical
Reference Guide. In general, the following two inroute group design objectives can easily be
achieved by applying these guidelines:
18
Improving the efficiency and/or availability in a network of terminals with similar clear
sky link budgets if they currently have rain or edge-of-beam margin provisioned.
Improving the efficiency and/or availability in a network of terminals with different clear
sky link budgets if they are kept in different inroute groups.
Release Notes
Software Upgrade for Network with Replication Enabled
Other design objectives often require full understanding of all system trade-offs, as it is in the
case of merging existing inroute groups to allow terminals with different clear sky link
budgets to share the same bandwidth pool. For these more complex situations, iDirect will
only support those designs that were done through direct consultation and review with iDirect
systems engineers.
In general, we strongly encourage our network operator partners to engage their iDirect
systems engineers when they plan their ATDMA designs.
In Release iDX 3.3.2.1, iDirect enhanced the operation of ATDMA return channels by:
Improving the detection and reporting of power control stability as a result of improperly
configured maximum Tx power in remotes.
Providing the configuration option to keep remotes in network even when the upstream
received power from the remotes is below the thresholds of all carriers.
Software Upgrade for Network with Replication

Enabled
For any networks currently using the Database Replication feature introduced in iDX Release
3.1, replication process must be disabled on both Master and Slave NMS servers prior to the
network upgrade. After both NMS servers have been upgraded to the latest iDX software
release, then the replication process can be reactivated. Procedures to disable and enable
the replication server are described in the iDX 3.3.2.1 Network Upgrade Procedure document.
Follow these procedures in the order described in the Network Upgrade Procedure document
to ensure that Replication feature is still functional after the network has upgrade to the
latest iDX software release.
Do Not Use Custom Key blind_feathering_enabled with

iDX Release 3.3.2.0 and Beyond
For iDX Releases 3.2.x.y through 3.3.1.x, when remotes do not use all of their allocated slots,
it is necessary to use a custom key, blind_feathering_enabled, with Reduce Jitter on
each upstream QoS profile in iBuilder to properly allocate slots.
However, this is no longer necessary going forward from iDX Release 3.3.2.0.
NOTE: The blind_feathering_enabled custom key is not automatically
removed when upgrading to iDX Release 3.3.2.1 and beyond; it must be removed
manually.
Remotes May Not Acquire on an Upstream Carrier with

High Symbol Rate and Large Block Size
Remotes may have difficulty acquiring the network when using iDirect traditional acquisition
and transmitting on a TDMA upstream carrier with a high symbol rate and large block size.
This can occur when there are no other carriers in the IF bandwidth of the receive line card.
Examples include IF test networks, or when there is a single RF carrier on a transponder. This
problem is unlikely to occur in an operational RF network.
Release Notes
19
Remotes Drop Out of Network If M1 Is Higher than 2.3 dB Running 8PSK 6/7
If experiencing this problem, one of the following work-arounds should be applied:

1. Add the following custom key to the Custom tab of the receive line card:
[MODEM_PARAMETERS]
rx_agc_ddc_gain_thresh = 1024
2. Add attenuation to the line card RF port such that the receive power is below -50 dBm.
3. If this is an IF test network, add a large adjacent carrier similar to the carrier under test.
Remotes Drop Out of Network If M1 Is Higher than 2.3

dB Running 8PSK 6/7
If the M1 parameter is increased to 2.4 dB, when using an 8PSK 6/7 carrier with 7.5M 438B
traditional ACQ assigned to HLC, all remotes drop out of network and cannot be made to reacquire even if M1 is reset to 0.6 dB, as recommended. C/N+M1+M2 should never be set for a
target of 14.5 dB or larger.
Symbol Rate and Transmit IF Frequency Restrictions for

Some Evolution e8350 and e800 Remotes
These restrictions generally apply to Evolution e8350 and e800 remotes with serial numbers
below 30500. Customers with active Evolution e8350 and/or e800 remotes with serial
numbers below 30500 should contact the iDirect TAC to verify that these restrictions apply to
the specific remotes.
NOTE: A very small number of e8350/e800 remotes with serial numbers higher
than 30500 are also affected. iDirect will directly contact all customers who have
purchased affected remotes with serial numbers above 30500.
Other remote model types, including Evolution e850mp, e8000AR, e8000AR XL and e8000AE,
are not subject to these restrictions.
The following rules should be followed for these remotes:
20
In the 950 MHz to 1500 MHz transmit band, the modem supports operation over the
power level range of +5 to -35 dBm per specification.
In the 1500 MHz to 2000 MHz transmit band, the modem supports operation over the
restricted power level range of -10 to -35 dBm. The maximum power configured for
network operation in this frequency band should not exceed -10 dBm.
The symbol rates of the upstream carrier must be greater than or equal to 1 Msps. For
spread spectrum carriers the chip rate must be greater than or equal to 1 Mcps.
Affected remotes should only be commissioned or re-commissioned using CW carriers.

The commissioning procedure using a PN modulated carrier should not be performed.
All modulation types may be used. However, these remotes should not be used in Inroute
Group Compositions that combine BPSK modulation with QPSK or 8PSK modulation.
Release Notes
Reconfiguration of Initial/Maximum Powers for Some Evolution e8350 and e800 Remotes
Reconfiguration of Initial/Maximum Powers for Some

Evolution e8350 and e800 Remotes
NOTE: This notice only applies when upgrading from a pre-iDX 3.2 release.
As with the previous notice, this notice generally applies to Evolution e8350 and e800 remotes
with serial numbers below 30500. Customers with active Evolution e8350 and/or e800
remotes with serial numbers below 30500 should contact the iDirect TAC to verify that this
notice applies to the specific remotes.
NOTE: A very small number of e8350/e800 remotes with serial numbers higher
than 30500 are also affected. iDirect will directly contact all customers who have
purchased affected remotes with serial numbers above 30500.
Other remote model types, including Evolution e850mp, e8000AR, e8000AR XL and e8000AE,
are not affected.
Overview
In earlier releases, the actual transmit power of these remotes could differ from the
commanded transmit power by as much as 4.0 dB, depending on the modulation of the
waveform being transmitted. This problem has been corrected in iDX Release 3.2. However, as
a result of the correction, the initial power and maximum power determined during
commissioning and configured in iBuilder are no longer valid.
iDirect strongly recommends performing the following operations on all affected Evolution
e8350 and e800 remotes after upgrading to iDX Release 3.3 from a pre-iDX 3.2 release:
1. Re-determine the correct TDMA Initial Power or SCPC Initial Power.
2. Re-determine the 1 dB compression point.
3. Based on the results of these operations, reconfigure the initial power and maximum
power on the iBuilder Remote Information tab.
If these operations are not performed, a number of problems may occur. Some examples for a
TDMA remote include:
If the TDMA Initial Power is too low, a remote may have difficulty acquiring the network,
or may never acquire the network.
If the TDMA Initial Power is set to high, the acquisition bursts transmitted by the remote
may cause carrier interference, violation of satellite regulatory constraints, or problems
with the UCP algorithm operating at the hub. In some cases, the remote may be unable
to acquire the network, causing CRC errors on other active remotes.
If the TDMA Maximum Power is set too low, the remote may be unable to acquire the
network, or may not have sufficient transmit power margin to stay in the network during
a fade or when moved to a more efficient carrier.
If the TDMA Maximum Power is set too high, the remote may be allowed to transmit at an
unacceptably-high power causing operational problems.
Release Notes
21
The general procedures for determining the 1 dB compression point, maximum power, and
initial power are contained in the Satellite Router Installation and Commissioning Guide for
iDX Release 3.3. That document is available on the TAC Web site. However, the procedure for
determining the 1 dB compression point assumes that an installer is present at the remote
site. To avoid a site visit, the procedure in the next section is performed over-the-air using
only iBuilder and iMonitor. The procedure assumes that the remote is locked to the
downstream carrier even if the remote failed to re-acquire the network after the upgrade due
to misconfiguration of the initial and maximum powers.
It is important to prevent interference from any remotes that were operational before the
upgrade but failed to re-acquire the network after the upgrade. If some remotes failed to reacquire and there are indications of interference, perform Step 1 and Step 3 on all suspect
remotes as soon as possible, even if re-commissioning is to be performed later. This will set
the initial power to -35 dBm and prevent the remotes from transmitting acquisition bursts
with excessive power.
Procedure to Reconfigure Initial and Maximum Powers

Follow this procedure to determine and configure the correct initial power and maximum
powers for a remote. The procedure assumes the remote is locked to the downstream carrier
and may or may not be in the network. The procedure must be performed under clear sky
conditions.
1. On the iBuilder Remote Information tab:
a. Record the current TDMA Initial Power and SCPC Initial Power values.
b. Set the TDMA Initial Power or SCPC Initial Power to the minimum power for the
remote model type (-35 dBm).
c. Set the TDMA Max Power or SCPC Max Power to the maximum power allowable for
the remote model type (+5 dBm).
d. Click OK.
2. If the remote is in the network:
a. Right-click the remote in the iBuilder tree and select Apply ConfigurationBoth
(TCP).
b. Select Reset Now.
3. If the remote is not in the network:
a. Right-click the remote in the iBuilder tree and select Apply ConfigurationPush
Remote-Side with Reset (UDP).
b. Right-click the remote in the iBuilder tree and select Apply ConfigurationReliable
Hub-Side (TCP).
4. Allow at least five minutes for the remote to reset and lock to the downstream carrier.
NOTE: A remote may not lock to the downstream carrier if the upgrade
failed. This procedure assumes that the remote was upgraded successfully.
5. Right-click the remote in the iMonitor tree and select Probe.
22
Release Notes
6. In the Remote Power section of the Probe, click Change to open the Change Remote Tx
Power dialog box (Figure 1).
Figure 1. iMonitor Probe: Change Remote Tx Power Dialog Box

7. Starting at -35 dBm (or at least 5 dB below the previously configured initial power)
gradually increase the transmit power until the remote joins the network.
NOTE: When the remote joins the network, the Transmit Power in the
Remote Power section begins to update. However, there may be a delay of
up to 20 seconds before the value is reported to the NMS.
8. Once the remote has joined the network and the transmit power settles, determine the
correct setting for the initial power. See Figure 2.
Figure 2. iMonitor Probe: Remote Power Dialog Box for Remote In Network
NOTE: If the remote fails to join the network after the upgrade and no
further problems can be determined, discontinue this procedure. Reconfigure
the initial power and maximum power to the original values and call the TAC.
Release Notes
23
9. Contact the Satellite Operator and execute the remaining steps to perform the 1 dB
compression test. Use the Cross Polarization section (Figure 3) to perform this test.
Figure 3. iMonitor Probe: Cross Polarization Section

10. In the Cross Polarization section of the Probe:
a. For RF Uplink Frequency, enter the frequency specified by the Satellite Operator.
b. For BUC LO Frequency, enter the local oscillator frequency of the BUC for this
remote. (This is the Frequency Translation for the BUC assigned to this remote on the
iBuilder VSAT tab.)
c. When instructed to do so by the Satellite Operator, click Start CW to transmit a
Continuous Wave (CW) test tone.
d. Working with the Satellite Operator, use the Adjust Transmit Power section to
determine the 1 dB compression point. For additional information, refer to the
Satellite Router Installation and Commissioning Guide chapter 1 dB Compression
Point and Maximum Power.
e. When the 1 dB compression point has been determined, click Stop to stop
transmitting the CW carrier.
11. On the iBuilder Remote Information tab:
a. Set the TDMA Initial Power or SCPC Initial Power to the value determined in Step 8.
b. Set the TDMA Max Power or SCPC Max Power to the value determined in Step 10.
c. Set the 1 dB Compression Point to the value determined in Step 10. (This field is for
information only.)
d. Click OK.
24
Release Notes
Evolution X7 Should Be Loaded with the Latest Software in Both Flash Partitions
12. Right-click the remote in the iBuilder tree and select Apply ConfigurationPush
Remote-Side with Reset (UDP).
13. Right-click the remote in the iBuilder tree and select Apply ConfigurationReliable HubSide (TCP).
14. Verify that the remote re-acquires the network.
Evolution X7 Should Be Loaded with the Latest

Software in Both Flash Partitions
The Evolution X7 Satellite Router has two flash partitions from which it can execute the
remote software package. If one partition fails, the Satellite Router will switch to the other
partition. When commissioning a new X7 router, or when upgrading an existing X7 to a new
release, iDirect strongly recommends downloading the X7 software package to the X7 twice.
This guarantees that both partitions contain the latest software and that the X7 can continue
to operate if one partition fails.
In iDX Release 3.2.3, the X7 software was improved so that failure of one flash partition is
highly unlikely. Although it is no longer a requirement to load both partitions when running
iDX 3.3, it is still recommended.
The Remote Installation and Commissioning Guide includes the procedures for loading both
partitions of an X7 from Web iSite or over-the-air when commissioning a new X7. The Network
Upgrade Procedure includes the procedure for loading both X7 partitions during a software
upgrade.
Minimum Tx Gain Must Be Adjusted for Some Beam

Maps
NOTE: Customers upgrading to iDX Release 3.3 from a pre-iDX 3.2 release must
perform this adjustment.
iDirect customers upgrading from iDX Release 3.2 who have already performed
this adjustment do not need to perform it again.
This special notice only affects iDirect customers with mobile remotes that use iDirect Beam
Maps with Tx Gain contours defined, and either or both of the following are true:
Maximum Skew is defined for the satellite or for individual mobile remotes on the
iBuilder Remote Geo Location tab.
Maximum C/N is defined for remotes on the iBuilder Remote QoS tab.
For networks using the above features, failure to perform this procedure could allow the
remotes to transmit with excessive power in some locations. Other customers using beam
maps are not required to perform the procedure in this section.
NOTE: The Tx Gain values in the map can be adjusted before upgrading to iDX
Release 3.3.
Release Notes
25
Minimum Tx Gain Must Be Adjusted for Some Beam Maps
NOTE: The following procedure assumes that if the min_gain parameter is

already defined for a beam in the GXT header file, the assigned value correctly
represents the minimum value of the Tx Gain of all usable contours defined in the
beam file.
Follow these steps to adjust the minimum Tx Gain for all beams when using GXT beam maps:
1. Log on to the root account of the server machine running the iDirect Map Server.
2. Change to the directory containing the GXT beam header file. (For example,
/etc/idirect/map/Beams.)
3. Copy the current GXT beam header file (named headerfile) to a new file name as
backup. (For example headerfile.sav.)
4. Edit the GXT beam header file.
5. For each beam (BEAM_<n>) defined in the header file:
a. if the min_gain parameter is not configured for this beam in the header file:
Examine the Tx Gain file (gain_file) to determine the minimum Tx Gain value
of all defined contours.
Set min_gain in the header file to the determined value.
b. Set the gain_offset in the header file to 0.2.

6. Save the GXT beam header file.
7. Enter the following command from the /etc/idirect/map/ directory to re-generate
the map:
newmap_gxt
8. Wait until the conversion is complete.
9. Enter the following command to restart the map server:
service idirect_map restart
For example, if the minimum gain of all contours for BEAM_2 as defined in the gain file is -3,
set the min_gain in the BEAM_2 section of the header file to -3. Then set the
gain_offset in the BEAM_2 section of the header file to 0.2.
The following GXT header file shows a single beam that has been adjusted in accordance with
this procedure. The name of the gain_file is Provider1.gxt. By examining
Provider1.gxt, the minimum Tx Gain for all contours of the beam has been determined to
be -3. Therefore, min_gain has been set to -3 and gain_offset has been set to 0.2, as
required by the procedure.
# Map Server Inputs
# created 2014-05-12:0800UTC
[BEAM_1]
provider = SATELLITE_PROVIDER_1
format = 0.1
beam_name = Beam1_SAT_PROV_1
file = Provider1.gxt
quality_1 = -3.0;0.1
26
Release Notes
Unsupported 2D 16-State Modulation Codes (MODCODs)
quality_2 = -2.0;3
quality_3 = -1;7
quality_4 = 1000;14
gain_file = Provider1.gxt
gain_offset = 0.2
min_gain = -3
Unsupported 2D 16-State Modulation Codes (MODCODs)

NOTE: Customers upgrading to iDX Release 3.3 from a pre-iDX 3.2 release must
perform this adjustment.
The 2D 16-State MODCODs BPSK-170B-3/4 and BPSK-438B-5/6 are not supported in iDX Release
3.3. Before upgrading from a pre-iDX 3.2 release, these MODCODs must be replaced with
MODCODs that are supported in iDX Release 3.3. Recommended replacement MODCODs
include QPSK-170B- 1/2 and QPSK-438-1/2, respectively.
CAUTION: If the unsupported MODCODs are not replaced with supported
MODCODs before the upgrade script is executed, the upgrade will fail.
Upstream MODCOD, Payload, and Symbol Rate Usage

Recommendations
The Link Budget Analysis Guide specifies all upstream MODCODS and payload sizes available in
iDX Release 3.3. The Link Budget Analysis Guide also specifies the maximum symbol rates for
TDMA Upstream Carriers.
In addition, iDirect recommends the following minimum symbol rates for TDMA Upstream
Carriers:
For 100 byte payloads, the minimum symbol rate is 128 ksps.
For 170 byte QPSK or 8PSK payloads, the minimum symbol rate is 128 ksps.
For 170 byte BPSK payloads, the minimum symbol rate is 256 ksps.
For 438 byte payloads, the minimum symbol rate is 500 ksps.
NOTE: Certain combinations of low symbol rate, payload size, acquisition type,
and modulation type can result in a very low number of traffic slots per frame.
When there is an insufficient number of traffic slots per frame, remotes will not
receive a timeplan. Following the recommendations above will ensure that there
are sufficient traffic slots to generate a timeplan.
QoS Allocation Fairness Relative to Operating MODCOD

Although Allocation Fairness Relative to Operating MODCOD can be seen in iBuilder on various
Group QoS configuration screens, this feature is not supported in this release. This setting
should not be selected.
Release Notes
27
Specification of Receive Line Card Center Frequency
Specification of Receive Line Card Center Frequency

NOTE: This notice is for iDX releases before iDX Release 3.2.X.
Specification of the receive line card center frequency has changed with this release. In
previous releases, the line card center frequency was specified in terms of the uplink
frequencies. Starting with iDX Release 3.2, line card center frequency is specified in terms of
the downlink frequencies.
Reference Clock Module (RCM-PPS) Requirement

To accommodate timing changes related to Adaptive-TDMA and network synchronization, iDX
3.3 networks require a PPS clock source that is only provided by the new Reference Clock
Module - Pulse Per Second (RCM-PPS). With this new requirement, all chassis in iDX 3.3
networks require the new RCM-PPS component installed prior to upgrading to iDX 3.3. The old
RCM (P/N TBD) is not supported in iDX Release 3.3 and future releases.
The RCM-PPS retains the functionality of the RCM and is backward-compatible with the
following software releases:
iDS 6.x, 7.x, and 8.x
iDX 1.x, 2.x, and 3.x
For full details refer to TAC Web site Technical Bulletin Introduction of the RCM-PPS, and the
Hub Installation, Support, and Maintenance Guide.
Configuring Database Replication on NMS Backup Server

You can replicate key configuration files to the Backup NMS Server by enabling replication
with the -b option. Replication allows the Backup NMS Server to be easily brought on line as
the Primary NMS Server in the event the primary server fails. However, if you use this option,
the backup server cannot act independently in another role (such as a GKD server.) This is
because the configuration on the backup server will be overwritten by the configuration from
the Primary NMS Server. See the full command explanation and syntax in the iDX 3.3 Technical
Reference Guide, under the section Setting Up NMS Database Replication.
CAUTION: Do not configure GKD and Replication using the -b option in the same
server.
NMS Fast Fade Stats Report Higher Than Actual Count

In iMonitor, the Fast Fade Counts reported by the X1 remote is much higher than expected. In
addition to the fast fade event itself, the X1 remote is incrementing the count on a secondary
parameter. The result is that for every fast fade event, 6-8 counts are actually registered.
However, the SNR and other information required in the ACM process are not adversely
affected.
28
Release Notes
Power Requirements for Multichannel Line Card
Power Requirements for Multichannel Line Card

At least 60 watts of power must be allotted for each Multichannel Line Card in a 20 slot
chassis. The total power available for each 20 slot chassis model type is specified in the Series
15100 Universal Satellite Hub (5IF/20-Slot) Installation and Safety Manual.
Line Card Power Usage Details

Table 3 shows power consumption requirements for eM0DM and XLC-M line cards in
multichannel mode, compared to eM1D1 and XLC-11 line cards in various modes of operation.
This information may be used to calculate the cumulative power consumption of all line cards
installed in a chassis.
Table 3. Line Card Power Usage
Line Card
Power Dissipation Mode of Operation
XLC-10
35 W
DVB-S2 outbound only
eM1D1/XLC-11
35 W
DVB-S2 outbound only
eM1D1/XLC-11
40 W
DVB-S2 outbound, with non-spread and Spread Spectrum

return channel using Spread Factor (SF) of 4 or lower
eM1D1/XLC-11
50 W
DVB-S2 outbound, with Spread Spectrum return channel using

Spread Factor (SF) of 8 or 16
eM0DM/XLC-M
60 W
Multichannel mode (Multiple Channel TDMA and Multiple

Channel SCPC)
Single Channel Receive Line Card Must Be Reset After

Carrier Changes
This notice applies to all Receive Line Cards or Transmit and Receive Line Cards in Single
Channel TDMA Receive Mode or Single Channel SCPC Receive Mode. It does not apply to line
cards in Single Channel TDMA (Adaptive) Receive Mode or Multiple Channel Receive Mode.
When a new TDMA or SCPC carrier is assigned to a line card in Single Channel TDMA or Single
Channel SCPC Receive Mode, or when the configuration of the assigned carrier is changed, the
line card must be reset. Prior to iDX Release 3.2, such modifications resulted in Changes
Pending on the line card and the line card was reset when the changes were applied in
iBuilder. In iDX Release 3.3, there are no Changes Pending on the line card when the carrier
information is modified. However, it is still necessary to reset the line card.
To reset the line card after modifying the assigned upstream carrier or assigning a new
carrier:
1. Right-click the line card in the iBuilder tree.
2. Select Reset Line CardReliable (TCP).
Release Notes
29
TRANSEC Networks Require SHA2 Key Exchange for Remote and Line Card Connections
TRANSEC Networks Require SHA2 Key Exchange for

Remote and Line Card Connections
Beginning with iDX Release 3.2.3, user connections from NMS servers or protocol processor
servers to remotes or line cards in TRANSEC mode require SHA2 key exchange. As a
consequence, the default versions of SSH and SCP provided with Red Hat Linux no longer work
for user connections to TRANSEC remotes and line cards. However, alternate versions of
OpenSSH applications that support SHA2 key exchange are now included on the servers in the
directory /usr/local/openssh/bin/.
Because of this change:
In TRANSEC networks, direct connections from the command line of an NMS server or
protocol processor server to a remote or line card must be made using the following
alternate version of SSH:
/usr/local/openssh/bin/ssh
Version 0.63 of PuTTY, which supports SHA2 connections, is now included with the iDirect
client software. This allows connections established by right-clicking a remote or line
card in iMonitor and selecting Connect to continue to work in TRANSEC networks.
Any externally-developed client that connects directly to a remote or a line card in

TRANSEC mode must use SHA2 key exchange.
The default Red Hat versions of SSH and SCP provided in earlier releases still exist unchanged
in /usr/sbin/and continue to be used under other circumstances. This ensures that
features such as Distributed NMS, database replication, and other uses of SSH and SCP
continue to function.
30
Release Notes
Bug Fixes
This chapter describes all bugs that have been fixed in iDX 3.3.x.x. All bugs fixed in a specific
release are also fixed in all later releases.
Issues resolved in a release may include specific maintenance issues, or specific issues that
were previously reported as Known Issues or as specific limitations.
Bugs Fixed in iDX Release 3.3.4

This section describes the bugs fixed in iDX Release 3.3.4.
42499, 42305 PP Sarmt Process Terminates Due to Memory Leak

It was observed that, in a multi blade network, the PP Sarmt process was gradually
consuming memory over time upon activating and deactivating remotes which lead to
a sarmt process termination. The recovery process required a manual restart or a
blade rebalance.
Fixed in this release.
42493 Inroute Center Frequency of the Modulated Carrier Exhibits Spurious

Spikes
Starting with iDX Release 3.2, remotes in the network are randomly exhibited
irregular spikes around the frequency of the modulated carrier. This issue only
happens when Spectral Inversion is used for all Evolution remotes (except for X1). The
frequency and intensity of the spurious spikes are depended on the frequency used
and the calibration of each remote.
42484 Remote Tags Multicast Fast Path Traffic on Default VLAN with VLAN ID 1
When Two or More Other VLANs are Configured with Tagging Enabled
In this specific scenario, the multicast Fast Path traffic went from PP to remote
untagged on the default VLAN, but when it came out of the LAN port of the remote, it
was tagged with VLAN 1 while there were two or more other VLANs configured and
tagging was enabled. As a result, end devices that were expecting untagged Multicast
traffic could not receive the traffic.
Release Notes
31
42481 Custom Key to Extend Cross-Pol CW Timeout Does Not Work for X1
A custom key (below) to extend the Cross-Pol CW timeout beyond the standard time
out of 5 minutes did not work for the X1 remotes.
[OOB_PARAMS]
cross_pol_test_timeout=XXX
42480 X7 and X5 Remotes Stop Responding When Pinged

Falcon-based X7 and X5 remotes stopped responding when a beam switch was
initiated while the remote was pinged from the Telnet console.
42472 MODCOD Distribution Displays Incorrectly if Remote Out of Network

The iMonitor MODCOD Distribution Window continues to show the last good MODCOD
distribution, even when the remote falls out of the network.
42425 iMonitor Inroute Distribution Pane Does Not Show Correct Distribution
In iMonitor, it was observed intermittently at the Inroute Distribution pane that an
IGC with remotes sending traffic at 100% of inroute capacity displayed a Total
Allocated (%) that was 85% to 90% allocation. This issue was not observed with four or
less remotes, or four or less inroutes.
42410 Remote Fails to Rejoin the Original IG After It Has Been Moved to a
Different IG
When a remote was mistakenly moved to a new network without applying the
changes, moving the remote back to its original network caused the remote to drop
out of the network and become stranded.
42402 X3 and X5 Remotes Transmit at Unacceptably Higher Power for SCPC

Carrier than TDMA Carrier
It was observed that X3 and X5 remotes transmitted at a higher power on an SCPC
carrier than on a TDMA carrier. In a test case using an TDMA carrier, an X3 transmitted
at -20 dBm. The same X3 remote was set all the way to -35 dBm and the actual Tx
transmit power was still unacceptably high.
42401 L2SW Mode Overrides Change to VPWSEPC After NMS Upgrade or Restart
In iBuilder, after configuring L2SW Default in VPWS mode at the Protocol Processor
SVNs tab, adding Layer 2 SVNs in VPWS mode, and performing an NMS upgrade or
restart, the L2SW overrides for some of the Layer 2 SVNs changed to VPWSEPC mode.
32
Release Notes
42400 Event Server Crashed with Signal 8 Arithmetic Exception

In a Global NMS with multiple beams and roaming remotes, the Event Server (evtsvr)
crashed with a Signal 8 Arithmetic Exception during the inroute carrier change.
42280 X1 Satellite Router Fails to Pass Multicast Upstream Traffic

The X1 Satellite Router would not pass multicast packets upstream even when
persistent multicast was configured. Multicast packets containing the destination MAC
address of IPv4 multicast were ignored.
42279 odu_tx_10_mhz Value Is Incorrectly Enabled for Line Card Configured as

Tx Warm Standby
The odu_tx_10_mhz value was incorrectly enabled (set to 1) in the options file of
the line card configured as Tx Warm Standby.
41866 MODCOD Distribution Display for X1 Remote Incorrectly Reports Traffic

In iDX Release 3.3.2.1, for a network with an X1 remote with no downstream traffic
and another type remote with downstream traffic, the MODCOD Distribution display
obtained after right-clicking the X1 in the iMonitor tree, selecting
DVBS2-StatsMODCOD Distribution, and then selecting the X1 in the Select
Remotes dialog box, incorrectly showed the other remotes traffic.
41579 Incorrect CIR Values Produced After VNO Modifies CIR

It was observed that when Virtual Network Operators (VNOs) without visibility to
carriers modified CIR/MIR values for the remotes they owned, sometimes incorrect
CIR/MIR values were saved after modification.
Additionally, when Host Network Operators (HNOs) attempted to resolve the problem
by resetting the correct CIR/MIR values, sometimes the carriers were not visible to
the HNOs.
41297 Incorrect CPU Status Reported for X7 Remote

It was observed during a telnet console session with a local PC connected to an X7
remote that when a cpu command was executed, the X7 did not report btp stats, oob
timeplan, or QoS status as expected.
41187 iSite Does Not Load or Display BUC LO Frequency

In the iSite Tree View, after right-clicking a remote and selecting
Align AntennaCross Polarization, the BUC LO Frequency was not loaded and
Release Notes
33
Bugs Fixed in iDX Release 3.3.3.1
displayed. This required manually updating the BUC LO instead of pulling the
information from the options file.
31376 Duplicate Packets Observe on X7 LAN Interface

An issue with the X7 remote generated duplicate packets on its LAN interface when
responding to ping had been observed. The main reason for the duplicate reply
packets was that both the Falcon process and Linux reply to the ping request.
EVOFT-433 (42506) Storm Flood on Upstream Switch Due to Hair-Pinning on PP

When there was more than one PP configured using different sub-net masks, the PP
re-transmitted packets not destined for it instead of dropping the packets. This
behavior led to a flood on the network.

This section describes the bugs fixed in iDX Release 3.3.3.1.
42294 NMSSVR Process Crashes Due to Database Corruption After Software

Upgrade
When upgrading the NMS server from iDX 3.3.0.1 to iDX 3.3.2.1, the nmssvr process
crashed. The main cause of this issue was data corruption in the QoSProfile and
QoSServiceLevel database tables.
42293 Unable to Upgrade Line Cards from iDX 3.1.1.10 to iDX 3.3.3.1 with
Multicast Download
In iBuilder during an upgrade from iDX 3.1.0.10 to iDX 3.3.3.1 using the Multicast
Download feature, the upgrade for line cards failed and the Multicast Download
dialog box showed the error message: "Download Failed: One or more errors have
caused this multicast download session to fail."
42253 X5 Remote Responses to Ping Exceed 15 Minutes After It Becomes the

Master in a VRRP Group
When the X5 remote became the Master in a VRRP group, it took more than 15
minutes to respond to ping on its virtual IP address.
34
Release Notes
42145 Cannot Install iDX Release 3.3.2.1 Software to a New X3 Remote

A new X3 remote or an X3 remote running iDX Release 2.0.0 cannot be installed with
the iDX Release 3.3.2.1 software. When attempting to install the software package
manually or using the iSite client, the process would fail with error messages.
42090, 42122, 42017 SARMT Process Crashing on the PP Blade

The PP sarmt process on the PP blades created new memory allocations for every
reload of remote options; this caused core dumps that affected customer traffic.
41918 X5 Roaming Remote Resets Due to FPGA Memory Leak From Beam
Switching
It was observed in previous releases that the FPGA memory leak issue would occur
whenever an X5 roaming remote switching from one beam to another. This issue could
cause the remote to randomly reset itself.
41915 X1 Remote with cRTP Enabled Does Not Pass DTMF Tones (RFC 2833)
An issue was discovered that, when an X1 remote was configured with cRTP enabled,
no response was detected for any VoIP call entry using the dial pad.
41887 SSH Tunnel Through a Remote Is Possible Without Any Passwords

An issue was discovered that it is possible to open an SSH Tunnel connection to the
remote Management IP address using the admin user that does not require any
passwords.
41882 Event Server Unable to Detect Event Messages After X1 Upgrade

When upgrading the X1 remote from iDX Release 3.2.x.x to iDX Release 3.3.2.1, the
X1 remote failed to acknowledge the software upgrade was successful with a
sequence of messages, such as: "Download Session Started," "Download Session
Completed," "Flash Started," and "Flash Completed." The only visible message at the
end of the software upgrade was "Options Flash Completed."
41881 X1 Remotes Report Unexpected options file received During Upgrade

During an upgrade to iDX Release 3.3.2.1, each X1 remote reported Unexpected
options file received for all package options files targeted for other X1 remotes. This
caused iBuilder to slow down or freeze.
Release Notes
35
NOTE: This bug does not affect upgrades from iDX Release 3.3.3.1 to future
releases; however, this bug does affect upgrades to iDX Release 3.3.3.1.
41852 Spoofing Not Enabled Automatically When Creating New Reliable Service
Level
In iBuilder, Spoofing was disabled by default when creating a new Reliable Service
Level at the Add Service Level dialog box.
41850 Changing Symbol Rate Causes e150 Remotes to Go Incomplete

In an inroute group with one upstream carrier, increasing the symbol rate to more
than 2000 ksym/sec caused e150 remotes to go Incomplete in the iBuilder tree.
41847 X7 Remote Cannot Disable Spoofing on Layer 2 TCP Traffic

In a L2oS network, after configuring a reliable service level for Layer 2 TCP traffic
with Spoofing disabled, spoofer did not stop spoofing TCP session on L2 TCP traffic.
41802 XLC-M (SCD Mode) and XLC-11 Line Cards Do Not Work with Wideband
Frequencies
Remotes were unable to acquire into a network configured with wideband receive
frequencies higher than 1700 MHz with these hub line cards: an XLC-M in Single
Channel Mode (SCD) and an XLC-11 (Tx/Rx). The remote acquired fine with an XLC-M
line card in Multi-Channel Mode.
41777 No Automatic Cleanup for /tmp/build_package Directory

Performing a Multicast Download or TCP Download on an NMS server sometimes
caused an out of space issue because there was no automatic cleanup of the
/tmp/build_package directory. This was not an issue when using Revision Server.
41774 iMonitor Time Plan Log File Shows Corrupt Minute Values
After right-clicking a time plan listed in the List Data tab of the Time Plan window to
use the iMonitor log function, the minute value in the timestamps column of the
resulting Time Plan log file was corrupted.
36
Release Notes
41728 Upstream QoS Stats Display No Data Under the VR Default Profile
For a Satellite Router configured with a Remote Service Profile, iMonitor did not
display service level data at Upstream QoS StatsDefaultVRDEFAULT even
when a remote-side custom key enabling upstream QoS service level statistics was
defined.
41639 iMonitor Control Panel Does Not Indicate Correct X7 Power Supply
In iMonitor, the BUC 48v field at the Control PanelGeneral tab failed to show the
correct status. As a result, a customer could not determine whether an X7 remote was
configured for 24 VDC or 48 VDC.
41630 Unable to Modify/Delete Previously Existing Static Routes After iDX 3.3.2.1
Upgrade
After upgrading to iDX Release 3.3.2.1, it was observed that when using iBuilder to
modify or delete any static routes that were created prior to the upgrade, these
static routes would remain populated in the options files for both the hub side and
remote side.
41557 Mismatched Error Message in iBuilder When Deleting a Remote Instance

When a remote instance was deleted in iBuilder, an error message contained a
different S/N and remote name than that of the deleted remote instance.
41352 Group QoS Stats Window in iMonitor Shows Incorrect VR ID

After creating a remote profile with two applications in iBuilder, the VR ID mapping
appeared incorrectly in the iMonitor Group QoS stats window.
41298 iBuilder Accepts Incorrect L2oS Configuration

When configuring hub parameters on the L2oS tab of the Protocol Processor, iBuilder
incorrectly accepted a local ID configuration when the remote SDT Mode selected was
Access.
41282 iMonitor Incorrectly Shows TxTDMATrafficMissing for All Network Remotes

iMonitor displayed intermittent RemoteTxTDMATrafficMissing events that lasted about
one minute for all the remotes in a network.
Release Notes
37
41200 X1 MAC Address Table Entries Do Not Expire

MAC entries in the X1 LLIB table never expired and the timer count remained at 180.
In an X7 LLIB table, MAC entries expired after 180 seconds.
41160 Remote Antenna Components Assigned to VNO Site Not Visible in iBuilder
In iBuilder, when an administrator assigned remote antenna components to a VNO
site, the components (IFL, BUC, Reflector Mount, Reflector, and LNB) were not visible
in the users remote VSAT tab.
41114 X1 Remote Remains in Idle/Dormant State with Layer 2 Classification Issue

When an X1 remote with Idle/Dormant states enabled was presented with Layer 2
upstream traffic, the X1 remote reported unclassified L2 frames and remained in the
Idle/Dormant state.
40949 iMonitor Does Not Update SCPC Carrier Maximum Power Levels
After the maximum power for SCPC carriers was changed in iBuilder, iMonitor did not
show the changes in a Network Data Snapshot.
40379 X7 Satellite Router Fan Status Issue

On the X7 Satellite Router, the FAN LED did not illuminate Green when the fans were
working and it did not illuminate Red when there was a fan failure. Also, Web iSite did
not show X7 FAN status and iMonitor did not provide warnings about X7 fan problems.
40080 iMonitor Upstream Carrier Information Does Not Change Automatically

In iMonitor, when a remote was moved from an SCPC network to a TDMA network (or
vice-versa), the upstream carrier information for the selected remote at Control
PanelGeneral tab did not change.
38
Release Notes

EVOFT-286 Incorrect Limits for FLL DAC Errors Cause X7 Remotes to Fail
It was found that the FLL DAC Error limits for X7 Series remotes were incorrectly set
in the iVantage clients. This issue caused the NMS to trigger false FLL DAC warnings
even when the X7 remotes were operating within the acceptable limits.
EVOFT-280 Unable to Upgrade TRANSEC Network Due to Missing tlsSwitch Script

It was found that iDX Release 3.3.2.2 ISO image did not include the tlsSwitch script,
which is required for switching the NMS server between TLS 1.0 and 1.2 to
communicate with all network components during the TRANSEC network upgrade of
pre-iDX 3.2.x.x networks. This issue caused the TRANSEC network upgrade to fail.
EVOFT-221 Modem Ignores OpenAMIP ACU Input When Configuring SCPC Return
When configuring an e8350 remote for SCPC return, it ignores all OpenAMIP ACU
input. This issue causes the antenna controller to not able to turn off the TX when the
remote is using an SCPC Return beam.
EVOFT-210 (42506) Storm Flood on Upstream Switch Due to Hair-Pinning on PP

It was found that a network storm flood could potentially occur when operating with a
specific network configuration which has two or more PP blades configured to operate
in multiple subnets.

42473 Activating Multiple IGCs Causes PP Blades to Stop Sweeping

Shortly after activating more than one IGCs in the network, the PP blades stopped
sending sweeps to the remotes, which caused outages, until the PP rebalance was
performed.
42419 Inroute Center Frequency of the Modulated Carrier Exhibits Spurious

Spikes
Starting with iDX Release 3.2, remotes in the network are randomly exhibited
irregular spikes around the frequency of the modulated carrier. This issue only
happens when Spectral Inversion is used for all Evolution remotes (except for X1). The
Release Notes
39
frequency and intensity of the spurious spikes are depended on the frequency used
and the calibration of each remote.
42305 PP Sarmt Process Terminates Due to Memory Leak

It was observed that, in a multi blade network, the PP Sarmt process was gradually
consuming memory over time upon activating and deactivating remotes which lead to
a sarmt process termination. The recovery process required a manual restart or a
blade rebalance.

42376 X1 Remote Randomly Experiences Packet Loss

It was observed in a customer network that, after the network has upgraded to iDX
Release 3.3.2.2, the X1 remote started to randomly experience packet loss. While the
root cause is still unknown, a custom key has been introduced in this release to
resolve this issue. This custom key will reset the firmware after the X1 acquired into
the network.
In case of experiencing the X1 packet loss, add the following custom key to the X1s
remote side configuration:
[TDMA]
tdma_reset_after_acquire=1
42272 X7 and X5 Remotes Stop Responding When Pinged

Falcon-based X7 and X5 remotes stopped responding when a beam switch was
initiated while the remote was pinged from the from the Telnet console.
42189 X1 Satellite Router Fails to Pass Multicast Upstream Traffic

The X1 Satellite Router would not pass multicast packets upstream even when
persistent multicast was configured. Multicast packets containing the destination MAC
address of IPv4 multicast were ignored.
42076 Custom Key to Extend Cross-Pol CW Timeout Does Not Work for X1
A custom key (below) to extend the Cross-Pol CW timeout beyond the standard time
out of 5 minutes did not work for the X1 remotes.
[OOB_PARAMS]
40
Release Notes
cross_pol_test_timeout=XXX
41696 Remote Tags Multicast Fast Path Traffic on Default VLAN with VLAN ID 1
When Two or More Other VLANs are Configured with Tagging Enabled
In this specific scenario, the multicast Fast Path traffic went from PP to remote
untagged on the default VLAN, but when it came out of the LAN port of the remote, it
was tagged with VLAN 1 while there were two or more other VLANs configured and
tagging was enabled. As a result, end devices that were expecting untagged Multicast
traffic could not receive the traffic.

42157 iMonitor Incorrectly Shows TxTDMATrafficMissing for All Network Remotes

iMonitor displayed intermittent RemoteTxTDMATrafficMissing events that lasted about
one minute for all the remotes in a network.
42142 X5 Remote Responses to Ping Exceed 15 Minutes After It Becomes the

Master in a VRRP Group
When the X5 remote became the Master in a VRRP group, it took more than 15
minutes to respond to ping on its virtual IP address.
42135 X1 Remote Acknowledges Invalid Unexpected Options File Received

Messages
When upgrading the X1 remote to iDX Release 3.3.2.1, the X1 remote acknowledged
all options files received for all other X1 remotes in the network with the
Unexpected Options File Received messages. Depending on the number of X1
remotes in the network, these error messages may temporary freeze the iBuilder
client.
42134 X1 Remote Fails to Acknowledge Successful Software Upgrade

When upgrading the X1 remote to iDX Release 3.3.2.1, the X1 remote failed to
acknowledge the software upgrade was successful with a sequence of messages, such
as: Download Session Started, Download Session Completed, Flash Started, and
Flash Completed. The only visible message at the end of the software upgrade was
Options Flash Completed.
Release Notes
41
42130 NMSSVR Process Crashes Due to Database Corruption After Software

Upgrade
When upgrading the NMS server from iDX 3.3.0.1 to iDX 3.3.2.1, the nmssvr process
crashed. The main cause of this issue was due to data corruption in the QOSProfile
and QOSServiceLevel database tables.
42129 X1 Remote with cRTP Enabled Does Not Pass DTMF Tones (RFC 2833)
An issue was discovered that, when an X1 remote was configured with cRTP enabled,
no response was detected for any VoIP call entry using the dial pad.
42124 Lat Server ICMP Requests Fail to Reach The Remote

iMonitor reported request timed out for the remotes, although ICMP packets sending
to the remotes from the lat server were observed at the PP blade.
42085 Mismatched Error Message in iBuilder When Deleting a Remote Instance

When a remote instance was deleted in iBuilder, an error message reported a
different S/N and remote name than that of the deleted remote instance.
42017 The SARMT Process Resets Due to Memory Over Consumption

It was determined in previous releases that, for all heavily loaded PP blades, the
sarmt process would randomly reset due to over consumption of memory on the PP
server.
42011 X5 Roaming Remote Resets Due to FPGA Driver Memory Leak From Beam
Switching
It was observed in previous releases that the FPGA driver memory leak issue would
occur whenever an X5 roaming remote switching from one beam to another. This issue
could cause the remote to randomly reset.
41995 iMonitor Reports Remote Has Timed Out Even When The Remote is Still
Active
It was observed in previous releases that, for any remotes with NetModem ID greater
than 65535, iMonitor would randomly report Request Timed Out even though the
remote was reachable from the latency server.
42
Release Notes
41981 iMonitor Fails to Generate Historical IP Statistics for Remote Instances with
NetModemID > 100000
iMonitor failed to generate historical IP statistics for remote instances with
NetModemID greater than 100000.
41943 Cannot Install iDX Release 3.3.2.1 Software to a New X3 Remote

A brand new X3 remote cannot be installed with the iDX Release 3.3.2.1 software.
When attempting to install the software package manually or using the iSite client,
the process would fail with error messages.
41814 Unable to Modify/Delete Previously Existing Static Routes After iDX 3.3.2.1
Upgrade
After upgrading to iDX Release 3.3.2.1, it was observed that when using iBuilder to
modify or delete any static routes that were created prior to the upgrade, these
static routes would remain populated in the options files for both the hub side and
remote side.
41176 Frequencies Above 1450 MHz Use Incorrect I/Q Offset Value From the
Calibration File
This issue occurred only when the remotes are in the network. For any e850MP
remotes with inbound frequency from 1450 to 2000 MHz, the I/Q offset value
remained constant at 0x0FB10FE0. For any e8350 remotes with inbound frequency
above 1450 MHz, the I/Q offset value remained constant at 0x0FD10FFE.

41832 Failed to Reset X7 Remotes Using the TCP/UDP Reset Options in iBuilder
In iBuilder, when attempting to reset the X7 remote using both TCP and UDP reset
options, the X7 remote failed to reset. The cause of this issue was due to the remote
failed to allocate sufficient memory to perform the task.
41665, 41732, 40799 iMonitor Inroute Distribution Pane Does Not Show Correct
Distribution
In iMonitor, it was observed intermittently at the Inroute Distribution pane that an
IGC with remotes sending traffic at 100% of inroute capacity displayed a Total
Allocated (%) that was 85% to 90% allocation. This issue was not observed with four or
less remotes, or four or less inroutes.
Release Notes
43
41628 Updated Bootloader Version

For X7 remotes, U-Boot version 2.91 was upgraded to version 3.1 in iDX Release
3.3.2.1. This upgrade prevents GPS fixes coming in through a console port from
locking a remote in U-Boot.
41623, 39970 Round Trip Delay Not Calculated Correctly Based on Acquisition
Aperture
In earlier releases of iDX 3.2, the satellite round trip delay was not always calculated
correctly when the Acquisition Aperture was modified for an inroute group in iBuilder.
Miscalculation of the round trip delay could cause data transmitted by the remotes to
be lost.
41608, 40749 iBuilder Revision Server Does Not Properly Update the Actual
Status of Remotes
In cases such as when performing a Package Download in iBuilder, the Revision Server
does not properly update the status of the remote as upgraded. This could potentially
cause the Revision Server to continue to send packages to the same remote
repeatedly, unless manually stopped.
41577 Editing Static Route Setting Does Not Work Consistently

In iBuilder, creating, editing, and deleting static routes did not work consistently;
static routes were unintentionally duplicated or did not appear.
41557 When Deleting Modem Instance iBuilder Error Message Points to Different
Modem
In very large Global NMS (GNMS) networks (e.g., a GNMS with over 65k remote
instances created), when a remote instance was deleted in iBuilder, an error message
appeared for a remote instance with a completely different serial number and name.
As a result, new commissioning was affected.
41553 High Latency Reported When Applying Network Changes

In very large networks (typically those with over 1000 active remotes), sometimes a
high number of remotes reported warnings for high latency in iMonitor when a
network level change was applied in iBuilder. The high latency warnings cleared
quickly and the remotes returned to normal latency values.
44
Release Notes
41548 X7 Fails to Update BUC Local Oscillator Freq in Web iSite

In iBuilder, the BUC ODU Tx Oscillator field for an X7 remote was changed from
Disabled to 10 MHz or 50 MHz and then applied to the X7. However, after logging on
to the X7 with Web iSite and opening the ODU Status page to view Tx Status, the BUC
Local Oscillator Freq was incorrectly displayed as 0 MHz.
41490 ActiveSoftwareVersion is Not Updated for All Remote Instances When

Physical Remote is Updated
After a physical remote was upgraded, came in network under a teleport, and
reported the new version, the ActiveSoftwareVersion for the remote was updated.
However, other instances of the remote with different TeleportIds were not updated.
This was incorrect; when a physical remote is upgraded and reports its new version,
all instances regardless of the TeleportId must update the ActiveSoftwareVersion.
41405 X1 Remote May Stop Passing TCP Traffic After 49 Days in Network
Due to a timer wraparound issue, X1 remotes can stop passing TCP traffic after 49+
days of continuous operation in network. A reset of the remote resolved the issue.
41393 X7 Memory Leak

On the X7 in previous iDX 3.2 and iDX 3.3 releases, when Falcon restarted, a small
amount of memory leaked in the kernel. So after several hundred Falcon restarts, the
remote could run out of memory and crash.
41370, 41649, 41554 iBuilder Add Rule Window Does Not Allow IPv4 Network
Address Configuration
At the iBuilder Add Rule window, configuring a valid rule that specifies an IPv4
address that starts with a network address and a valid subnet mask caused an invalid
IP address error message to appear. For example: A user wanted to filter traffic for an
entire subnet 192.168.52.0 / 24 and configured a rule specifying network IP address
192.168.52.0 and mask 255.255.255.0. This is a valid rule. However, the GUI did not
allow it and displayed an invalid IP address error message.
41365 X3/X5 SCPC Remotes Lose Downstream Lock with "RemoteTxSCPCLockLost"

Messages
X3 and X5 SCPC remotes lost the downstream lock occasionally generating
RemoteTxSCPCLockLost messages. The remotes reacquired back and within two
minutes but VoIP traffic was affected. It was determined that the remotes were not
checking transport stream (TS) status often enough; as a result, when the
downstream lock was lost, the demodulator could not be quickly reset.
Release Notes
45
41362 SSH Into X7 Remotes from Other Devices Behind the LAN Port Did Not Work
Unless MTU was Changed to 1504 from the Default 1506
Through a kernel enhancement, the default MTU for X7 has been changed back to
1504 (like all other remotes) and the SSH function works as desired.
41358 X1 Unable to Download or Upload File Using Specific FTP Program

An X1 remote was not able to download or upload a file using VxWorks FTP Server
(VxWorks 5.4.2). It was determined that a new function to handle misaligned memory
access was not considering processor endian. This resulted in improper maximum
segment size (MSS) handling such that an MSS of 512 was interpreted as 2 bytes and
caused incorrect segmenting of TCP packets. This caused flooding issues with TCP
spoofing that killed the file transfer sessions.
41356 (41354) Rx00 FPGA Image Not Installed on XLC-10

The RX FPGA image was not installed by default and was actively deleted on the XLC10 line card. If the line card was restarted, it would go to the recovery stack.
NOTE: This issue only affects the XLC-10 line card; no other line cards are
affected.
41336 E800 and E8350 Transmit DC Power Cannot Be Turned OFF

In iDX Releases 3.2 through 3.3.1, the BUC DC power on the Tx port was always on and
could not be turned off through the console.
41335 Potentially Incorrect Tx Power for e8350, e800, and e850mp Remotes in
RF Network
For all current iDX 3.2 and 3.3 releases, the actual transmit power of e8350, e800,
and e850mp remotes could be significantly different from the configured Tx power.
This was due to a software bug when reading calibration files.
This issue will not be seen in IF loop configurations.
41324 Remote Service Group Configuration Lost when Multiple Remote Instances
Modified Simultaneously
When modifying a QoS Remote Profile using the iBuilder Modify All Instances option,
the Remote service Group configuration was lost. As a result, multiple instances had
to be modified one by one.
46
Release Notes
41323 NMS Server Occasionally Crashing Due to Lack of Memory

Several improvements were made in memory utilization and allocation, resulting in
better memory management.
41322 Latency Server Continually Pings and Reports Latency Timeouts for an
Offline Remote
The Latency Server continued to ping and report latency timeouts for n offline
remote.
41321 iMonitor Incorrectly Displays Remote Model Type When Displaying L1 or L2

Events for X1 Remotes
In a network of X1 remotes where one remote had the Idle and Dormant state
enabled, the Event Server did not send the correct Derived ID (DID) for that remote to
iMonitor. As a result, iMonitor incorrectly displayed the model type for that remote in
the Type-SN column in the Events pane.
41318 Rate Controller Timer May Cause Some TCP Sessions To Be Incorrectly Rate
Shaped for X1 Remotes
Rate limit is used to rate shape the payload compressed TCP session. Due to this timer
issue, there was a small probability that some TCP sessions may not be rate shaped
properly and hence may be blocked.
41308 PP Side Assembler Does Not Correctly Assemble TCP Segments Causing
Resets to TCP sessions for X1 Remotes
Under certain conditions, it was found that the PP was not assembling the TCP
segments from X1 remotes correctly. This would cause reset of TCP sessions.
41302 16-Bit Number Overflow Caused Configuration Database Issues

A 16-bit overflow caused numerous bad cases when the total remote instances
exceeded the 16-bit number space in the NMS configuration database. For example,
information that was added to the Contract Number and Site Notes text boxes in the
Remote Information tab was missing after logging out and logging back in to iBuilder.
41301 Demand from Idle VRs Can Go Very High When Sticky Demand is Enabled
Sticky Demand at the upstream is enabled by default; when remotes report demand,
the demand should persist for one second in the Inroute Demand Assigner (PP_DA)
process. However, because of a coding bug this demand grew exponentially until it hit
Release Notes
47
the Maximum Information Rate (MIR). This problem was more pronounced for idle
Virtual Remotes (VRs). For busy VRs, the new demand request cleared out the sticky
state. This issue was only present in Evolution releases 3.1 and earlier.
41291, 41197 Satellite Routers Randomly Not Acquired Into the MCD Mode
Network with Inclined Orbit Satellite
It was found in previous releases that, in a network with inclined orbit satellite, and
depending on the inclination of the satellite and upstream carrier size, the remotes
were randomly not able to acquire into the network. This issue only happened in an
MCD mode network with licensed channel number configured to either 1, 2, or 4. The
cause of this issue was the memory address was incorrectly set by the line card
firmware so the remotes were not able to acquire into the network or get in the
network with the wrong time slot and suffer a lot of missing data.
41275 NMS Database Not Updated When Idle and Dormant States Change for
Added Remote
For a recently added remote, it was observed that when the Enable Idle and Dormant
State check box on the Remote QoS tab was checked or unchecked, the NMS database
was not updated with the change until the Configuration Server was restarted.
41273 check_db.pl script Optimization

The check-db.pl script takes several hours to complete when checking the database
of a large network. During this period, other programs (e.g., SatManage) may not
report any data. The script was optimized to execute faster.
41270 X3/X5 Remotes Could Produce a Small Center Frequency Spike on SCPC
Return
For SCPC return for all versions of iDX Releases 3.2.x.y and 3.3.x.y, it was observed
that X3 and X5 remotes produced a small continuous wave (CW) spike on the center
frequency of the modulated carrier. This occurred because certain register values
were not correctly programmed into the modem.
41246, 41431, 41349 X7 Remote is Missing beam_state.opt File After Upgrade

After an upgrade, an X7 remote took longer to join the network because the
beam_state.opt file was not being copied and preserved during the upgrade. As a
result, the modem looked for the beam with highest BEAM ID instead of the last beam
it was in.
48
Release Notes
41221 OpenAMIP 'X' Command Unintended Limitation

When a remote was defined using an OpenAMIP antenna with an OpenAMIP 'X'
command option that was too long (i.e., more than 150 byes), the remote went into
error stack. In this release, the 'X' command shares the same buffer with the other
[SATELLITE] group parameters; 350 bytes of the buffer are dedicated to storing the 'X'
value.
41184, 39823 iBuilder Apply Configuration PushRemote-Side with Reset (UDP)

Not Working
This issue was seen after an upgrade in an iDirect system with multiple protocol
processor blades. In that instance, attempts to update the options files of the
remotes by selecting the following command in iBuilder did not work:
Apply ConfigurationPush Remote-Side with Reset (UDP)
This problem occurred if the UDP push was sent to a PP blade other than the blade
responsible for network multicast traffic. The blade that handled multicast for the
network was responsible for forwarding the UDP push to the line card.
Normally, when a blade not responsible for network multicast received the UPD push,
it forwarded it as a multicast message to the NMS multicast address. When the blade
responsible for multicast received the multicast message, it forwarded the UDP push
to the transmit line card for transmission on the outbound carrier. However, when the
problem was observed, the UPD push was not forwarded by the non-multicast blade
that originally received it to the NMS multicast address.
41183, 40220, 40123, 39948 Changing Maximum MODCOD of Network Can Cause
Nominal MODCODs for Remotes to Change
When the maximum MODCOD of the network is changed to a MODCOD below the
MODCOD of the remotes and then changed back to the original value, the nominal
MODCOD of the remotes changes incorrectly to be equal to the maximum MODCOD of
the network. Once the Network maximum MODCOD is changed back to the original
value, the nominal MODCODs of the remotes do not return to the original values.
Instead, they are set to the highest MODOCOD of the network.
41171 iMonitor Remote Availability Report Shows Incorrect Data

The iMonitor Remote Availability Report incorrectly displayed 100% availability for all
remotes, including remotes that were not in network. This resulted in incorrect SLA
reporting.
Release Notes
49
41170 Increased NMSSVR Virtual Memory Use Due to Hanged NMS Clients May
Cause NMSSVR Crash
In a Global NMS network with DNMS setup with multi-beams, some NMS clients which
were hanged and not active, used large amounts of memory. The nmssvr.log showed
the QUEUE FULL for those clients; the increased use of NMSSVR virtual memory could
cause an NMSSVR to crash.
41169 Memory Corruption When Adding Multiple Remotes In The Network

In a network with more than 10,000 remote instances, it was observed that NMSSVR
crashes occurred when multiple roaming remotes were added to the network. Core
dumps showed that memory was being corrupted in different areas.
41143 Flash Fails With Multicast Package Download to More Than 150 Remotes
If more than 300 remotes were selected to perform a Multicast package download, it
was possible that the download would not be successful. If the number was reduced
to below 300, the download worked fine. This was because of a limitation to the
maximum number of remotes that could be upgraded using Multicast Download.
This has been resolved in this release through a change in internal logic. Now if more
than 150 remotes are selected by the user, the system automatically separates the
package download into batches of 150 remotes.
40913 Incorrect NCR Time Reporting from SCD-TDMA Line Card Causes Inroute
Timeplan Problems
In an ATDMA system with one carrier and SCD-TDMA line cards, it was observed that
the remotes in a network periodically reported hundreds of TDMA traffic missing
warnings.
Further investigation determined that metastable NCR time stamp reporting from the
SCD-TDMA line cards caused the ACQ bursts to arrive with the wrong frame timing
information under some special frame start delay and symbol rate/ACQ burst duration
combinations. As a result, the iCon process at the PP deleted all previous timeplans.
40878 X3/X5 Remotes Drop Priority Packets Under Congestion on SCPC Return
Channel
X3/X5 remotes in a network were transmitting both Priority and Best Effort traffic
with good latency on a dedicated SCPC return channel; Under congestion the
expected behavior was for the remotes to drop Best Effort traffic and maintain the
Priority traffic. This was not happening under all conditions.
50
Release Notes
40802 A Few Hundred Upstream TCP Sessions Cause X1 Modem to Reset

When a few hundred TCP sessions were generated and the data was sent in the
upstream direction, an X1 modem would reset and then return to the network or it
would require a power reset before it returned. It was determined that this issue was
a result of insufficient memory being allocated for TCP upstream sessions.
Fixed in this release by improving the memory handling logic so that an X1 will not
reset; rather it will manage additional incoming TCP sessions differently.
40800 iMonitor Bandwidth Legend Mismatch for Downstream QoS Stats

After right-clicking a remote in the iMonitor tree, selecting Downstream QoS Stats,
and choosing a service level to view bandwidth (BW) statistics, there was a bandwidth
legend mismatch. The BW Requested graph legend incorrectly showed as Free BW
and the Free BW graph legend incorrectly showed as BW Req.
40791 GPS Input Validation Feature Prevents Remotes from Obtaining LATLONG
from an ACU
In iDX Release 3.2.3, when the custom key parameter gps_validation_active was set
to = 1, remotes were unable to obtain LATLONG from Seacom antenna control units
(ACUs). As a result, remotes were unable to transmit. For iDX Release 3.3.2.1, the
GPS Input Validation feature has been turned off similar to earlier iDX releases.
40772 X1 Remote Unable to Establish Link Layer After Power Cycle

In cases where X1 remotes were powered OFF for several hours and then powered
back ON, they reported LAT TIMEOUT alarms, did not pass traffic, and were unable to
establish the link layer.
This was due to a bug in the sequence of ACM and other messages being sent to X1
remotes when the operating MODCODs might have changed over a period of time.
40642 NMS Statistics Server Process Might Crash Under Certain Conditions
It was observed in iDX Release 3.1.0.11 that the NMS Statistics Server process
(NRDSVR) might crash when historical data was queried and there were long lists of
pending data to be archived. This caused disruptions to monitoring and
troubleshooting. Through examination of core dumps it was determined that a
variable mismatch caused the crashes.
40640 X1 Remote Reboots Under Heavy Traffic Combination of TCP Software

Download and User TCP Traffic Load
The X1 remote had been observed to reboot itself when a TCP software download was
performed concurrent with heavy user TCP traffic. When this happened, the X1
Release Notes
51
remote also issued "ASSERTION: EMPTY EMPTY" and "Invalid Package Format"
messages.
40605, 38560 OpenAMIP Reflectors Share Elevation and Gain Parameters

In the iBuilder tree, under ComponentsRemote Antenna ComponentsReflector,
if there were two or more OpenAMIP-based reflectors and one of those reflectors had
Elevation and Gain added, that Elevation and Gain was also added to unmodified
OpenAMIP reflectors.
40602 EVTSVR Maintains Prior Connections After Creating New Connections to

CMSVR
The Event Server (EVTSVR) created new connections to the Chassis Manager Server
(CMSVR) as required by events at the NMS Server (NMSSVR). However, it did not
disconnect prior connections. As a result, when client threads approached 300 in
number, the CMSVR would run out of memory and crash.
40600 Event Server Crashes in DNMS Setup

In iDX Release 3.1.1.11, the Event Server generated multiple core dumps in a DNMS
setup. It was because of an incorrect pointer.
40583 NMSSVR Fails to Respond to Clients Command After iBuilder and iMonitor
Logins Fail
After logins into iBuilder and iMonitor failed, executing a clients command at the
NMSSVR console caused the NMSSVR to become unresponsive.
40577 Backup GKD Server Option File Overwritten When Database is Restored
A backup GKD server gkd_opts.opt file was overwritten by a primary GKD server
gkd_opts.opt file when the database was restored on the backup NMS using the --inst
option from the primary NMS. This caused backup GKD server to have same priority as
the primary GKD server.
40552 NMS Upgrading to iDX Release 3.2.3 or iDX Release 3.3 Overwrites All
Customized Hunt Frequency Values
It was observed that, after the NMS was upgraded to iDX Release 3.2.3 or iDX Release
3.3, customized Hunt Frequency values configured for all mobile remotes in the
network were overwritten.
52
Release Notes
40506 Revision Server Does Not Update X7 Remote Status After Upgrade
In iDX Release 3.2.2.7, after using Revision Server in iBuilder to upgrade an X7
remote, the Revision Server did not update an X7 remote's status from DownRev to
UpRev at NetworkPackage DownloadRevision Server. It was determined that
the remote was reporting back a version string using an incorrect format.
40510 Cannot Change Serial Number of Remote Cloned from Roaming Remote in
iBuilder
When cloning a remote from a roaming remote, Update Properties in the Roaming
section of the iBuilder Tree was grayed out. As a result, it was not possible to access
the Roaming Properties Update dialog box to change any fields; as a result, the
cloning feature could not be used.
40358 iMonitor Historical SNR Graph in DVBS2 Stats Does Not List Data and Only
Displays SNR Plot
In iMonitor, monitoring the historical downstream Signal to Noise Ratio from DVB Stats
only showed the SNR Plot graph; SNR data was not shown.
40347, 38247 iMonitor Satellite Router ACM Gain Data Reporting Issue
In iMonitor, data reported in the CCM kSym and Actual kSym columns did not match
actual SAT traffic.
40270 Edit Service Level Dialog Box GUI Issue

For some versions of iDX 3.2.2.x, when different option buttons (Priority Queue,
Cost-Based, or Best Effort) were selected at the Edit Service Level dialog box for an
Application Profile or Traffic Profile, the last one clicked would be applied and work
correctly. However, because previously selected option buttons were not cleared, the
screen display was confusing.
40224, 40065 iSite: Retrieved Options File Cannot Be Read in Notepad

When a remote-side options file was retrieved using iSite, it was opened in Notepad
by default. However, due to a formatting error, the options file might not be
readable.
Release Notes
53
40221, 33901 Unexpected MIR/CIR Changes Pending Triggered After Changing

Translation Frequency of LNB
It was observed that a change made to the translation frequency of an LNB triggered
Changes Pending for MIR/CIR values for remotes. The options files showed the
MIR/CIR values reverted to default.
40214, 32149 iBuilder: Idle and Dormant States May Still Be Enabled After
Disabling in iBuilder
In rare cases, if the Idle and Dormant States feature was enabled in iBuilder on the
Remote QoS Tab, disabling this feature and saving the configuration did not result in
changes pending for the remote and the feature was not disabled.
40152 X1 Remote Continues to Demand Slots Even After All TCP/UDP Traffic Has
Stopped
In some rare conditions, the X1 remote has been observed to continue demanding
traffic slots even after all its TCP/UDP traffic has stopped.
39958, 38375 Mobile Remote Fails to Receive Correct Maplet Updates While
Crossing the Anti-Meridian Line
It was observed in previous releases that when a mobile remote was approximately
0.4 degrees from the edge of the last maplet, while crossing over the anti-meridian
line, it never received a maplet containing information for the opposite side of the
anti-meridian line. This issue resulted in an excessive number of maplet requests and
receive messages that caused the remote to assume a busy state.
Only after crossing approximately 0.4 degrees over the anti-meridian did the terminal
receive the correct maplet. At that point, the maplet requests and receive messages
to the terminal console started to stabilize.
39935 SCD Line Cards Require Reset to Handle Real-Time Carrier Updates
As carriers were added or deleted from an inroute group, the traffic guard band
changes that were pushed in real time to the Rx hub line cards (in SCD mode) caused
the demodulator to output misaligned frames that caused CRCs. The SCD line cards
had to be reset before the system could recover.
Because the SI Table handles all carrier changes in SCD mode, the NMS did not alert
the user that a reset was needed. This fix now adds keys to the line card that change,
therefore showing the user a line card reset is needed.
54
Release Notes
39932 iBuilder LNB Stability Field is Missing the MHz Unit Reference
For iDX Releases 3.2.2.4 and 3.2.2.7, it was observed that in iBuilder the Stability
field at ComponentsRemote Antenna ComponentsLNBModify Configuration
Object had no units associated with it except +/-; however, in previous versions the
MHz unit was shown.
39115 iMonitor GQoS Distribution Tab Does Not Display CIR, MIR or Cost Data
In iMonitor, the GQoS Distribution tab did not display any configured CIR, MIR, or Cost
data in either the Group QoS View or the Remote View. As a result, Base Measures
could not be used to see Config CIR or Config MIR.
38332 Confusing iMonitor Command Buttons for Downstream/Upstream GQoS

Statistics
When viewing Downstream QoS Stats or Upstream QoS Stats in iMonitor, the GQoS
Distribution tab at the Group Stats display window had buttons (i.e., Bits, Bytes,
Symbols) that were active for the GQoS Distribution tab but served no useful purpose
and confused users.
38036 iMonitor ATDMA Stats Timeplan Window Incorrectly Reports 64000 Traffic
Slots
When checking the ATDMA time plan in iMonitor by selecting ATDMA
StatsTimePlanSelect Inroute Groups and selecting the inroute groups, data
appeared correctly. However, after modifying the configuration(s) of the inroute
groups, a request for historical data incorrectly reported 64000 traffic slots.
35619, 32703 When the Main Downstream and Alternate Downstream Were
Identical, X1 Remotes Did Not Function
If both the Main and Alt Downstreams are identical, X1 remotes displayed RX
Frequency = 0 (zero). Under this condition the configuration became invalid and the
remote did not acquire into the network.
Release Notes
55

41218 e150 Incorrect Downstream Bandwidth allocation Due to Wrong MODCOD

The downstream MODCOD reported by the PP for the e150 remote was constant at
QPSK 1/4; this limited the bandwidth allocation on the downstream. With a 45 MSym
ACM downstream carrier, the throughput was limited to around 15.5 Mbps of Info
Rate.
41182, 40967 Falcon Crashes When Processing igmpv3 Membership Report

In previous iDX and iDS releases, iDirect software was not able to properly process
igmpv3 membership reports with source-specific addresses. Such reports caused the
iDirect Protocol Processor, line card, or remote software processes to crash while
processing these packets.
41156, 41707 iMonitor Error Message from Remote Flash is Truncated

If a modem failed to flash a package, the iMonitor Events window failed to show the
second line of the error message.
NOTE: Because this is a remote side fix, the benefit is not realized until the
remote is running iDX release 3.3.2.0 or beyond. During an upgrade to iDX release
3.3.2.0, the messages are still truncated.
41145 X7 Transmits 27 MHz by Default Starting with iDX Release 3.2.2.7

Starting with IDX Release 3.2.2.7, the X7 transmit port (Tx) has a 27 MHz tone enabled
(by default). This is not an issue for most use cases since the majority of the BUCs
have appropriate filtering to block the 27 MHz signal. However, in some specific cases
where another amplifier is used in the transmit chain for reasons such as for
converting L-band signal to fiber, this 27 MHz signal may get amplified or translated
up, or saturate the in-line amplifier. These conditions could cause the signal to be
transmitted at RF frequencies and result in possible interference.
41141 Remote Displayed Network Key as Clear Text in the Console

When a Falcon-based remote was added to an iDX 3.3 network, the remote displayed
the network key as clear text in the console.
56
Release Notes
41133, 41052 Remote Terminals Unable to Establish SSH Connection to Other

Devices Following Upgrade to iDX Release 3.2.3.0 and Later Releases
As part of iDirects continued enhancements to the security of iDirect networks, there
are regular updates to the OpenSSL library in iDirect software releases. As part of this
approach, regular updates to the SSL library have also occurred in IDX 3.2.3 and iDX
3.3.x.x releases. These regular updates resulted in some changes to the default
configuration files related to SSH operations.
It was reported that due to differences in the SSL versions operating on iDirect
network components, and other non-iDirect network devices such as Cisco Routers,
there was an incompatibility introduced when performing SSH operations. This
incompatibility was exhibited in two ways: 1) user inability to SSH form a non-iDirect
device - for example a Cisco Router, into an iDirect Remote; and 2) user inability to
SSH from an IDirect remote into another non-iDirect network device.
The issue of establishing an SSH connection from a non-iDirect network device into an
iDirect remote has been fixed in iDX Release 3.3.2.0, through change of configuration
files. However, the issue of establishing an SSH connection from an iDirect remote to
non-iDirect network device depends on the SSL version running on that device. iDirect
recommends that users consult with the support organization for the non-iDirect
device for options to perform the SSH function.
41132, 41067 Some Remotes Randomly Enter Offline State

It was observed that Evolution remotes would randomly drop from the network. In
such cases, the txstate command to the remote would indicate that the remote was
offline.
This issue, which is present in all iDX 3.2.x.x releases prior to iDX Release 3.2.3.5, was
due to logic errors that in rare cases would cause this occurrence.
41124 Remote Does Not Transmit on All Assigned TDMA Slots

Due to changes made in Falcon-based remote software to support ATDMA, it was
observed that sometimes the remote did not transmit on all assigned slots resulting in
wasted bandwidth.
41120 Incorrect DVB-S2 Overhead Estimation Causing Increased Latency

It was observed that the PP did not estimate the amount of overhead per packet
correctly on the DVB-S2 link. As a result of back pressure between the line card and
the PP, additional latency was experienced during congestion that was more apparent
at lower symbol rates.
Release Notes
57
41119 SADA Process Allocates Double Minimum Information Rate

It was observed that the Inroute Demand Allocator (SADA) process allocated more
than the configured Minimum Information Rate (Min IR) slots per frame. The result is
that remotes randomly would not get their assigned Min IR causing additional jitter
and latency.
40846 Remotes Log Out of Network When Minimum C/N0 is Not Met
After upgrading to iDX Release 3.2.x, when the remote reached its maximum power
and the C/N0 was lower than the minimum required (based on inroute group and
carrier configuration), the PP logged the remote out.
NOTE: iDirect recommends that remotes should be logged of out of network if the
minimum C/N0 requirement is not met. However, iDirect recognizes that some
customers in networks with homogeneous carriers have remotes operating below
link budget guidance on the inbound. To support these customers and disable
logging out, iDirect provides the following custom key to be added at the Network
Custom tab:
[INROUTE_GROUP_x]
//x is inroute group number.
hysteresis_logoff= -1
CAUTION: If the custom key is used and an inroute group is deleted, the presence
of the custom key will prevent the Protocol Processor from loading the option file.
This will result in network outage.
40393 iMonitor Shows Only One Day of Historical Data for Downstream QoS
Service Level Stats
iMonitor had more than one day of a remote's historical data records; however, it only
displayed the downstream QoS service level stats for one day.
37871, 37782 NMS Reports Larger Latency Spike When Upstream Time Slots Usage
Close to 100%
Adding an additional remote to an inroute group that was experiencing time slot
usage of about 93% on average caused time slot usage to increase to close to 100%. In
addition, the NMS randomly reported increased latency when pinging remotes.
58
Release Notes
Bug Fixes in iDX Release 3.3.0.2

Data Path Issues

Data Path issues include Protocol Processor, Hub Line Card, and/or Remote issues, as well as
Systray message, and MapTools related issues.
41263 X1 Packet Segments Are Not Correctly Assembled by the PP Side Assembler
With spoofing disabled on the X1 remote, it was observed that any packets sent by the
X1 remote could cause disassembly issues on the PP side assembler; this could cause
throughput degradation in TCP traffic or even reset TCP sessions.

Data Path Issues

40438 X1 Remote Fails to Reacquire Into the Network After a Temporary Outage
It was observed in iDX 3.2.x.x and iDX 3.3 releases that the X1 remote was randomly
unable to reacquire into the network after a temporary outage due to rain fades. The
only solution to fix this issue was to physically reboot the remote.
Bugs Fixed in iDX Release 3.3

This section describes the bugs fixed in iDX Release 3.3.
Data Path Issues

40234, 40202, 40180 Evolution X1 or e150 May Not Acquire in Inroute Group with
Unsupported Carriers
This issue existed in an inroute group containing Evolution X1 or e150 remotes in
combination with upstream carriers not supported by those remotes. For example, it
would occur in an inroute group containing X1 remotes and both spread and nonspread carriers, since the X1 does not support Spread Spectrum.
Release Notes
59
When these conditions existed, an X1 or e150 remote would not join the network if
the carrier in the inroute group with the highest Inroute ID was a carrier on which the
remote was not allowed to transmit.
NMS/Reporting Issues
NMS/Reporting issues include iVantage and NMS Server Side issues.
40398, 39852 iBuilder: Users without GQoS Planning Permission Cannot Assign
Remote Service Profile After Moving a Remote
When an iBuilder user without GQoS Planning permission moved a remote to another
network, the Remote Service Profiles was not displayed and no profile was selected
for the remote. This caused the remote to become incomplete and changed the
remote state to Deactivation Pending.
40322, 40021, 39603, Roaming Remotes Generate Large Number of State

Changes To and From Elsewhere State
In a network with roaming remotes, it was observed that the state change log was
growing rapidly. After investigation, it was found that remotes were generating and
then clearing a large number of events when changing to and from the Elsewhere
state.
40300, 38249 iMonitor Displayed Alarm Icon for the Remotes in Offline State
When a remote was offline, iMonitor displayed the Alarm icon instead of the Offline
icon.
40259, 40208 iBuilder: Configuration Server May Crash When Transponder is

Modified
If the Translation Frequency field was modified for a Transponder in iBuilder, the NMS
Configuration Server would crash, resulting in a mismatch between the configuration
of the receive line card and remotes.
40205, 40178 iBuilder: Change to Acquisition Aperture Does Not Cause Changes
Pending for Line Cards in Single Channel Receive Mode
If the Acquisition Aperture was modified for an Inroute Group containing single
channel receive line cards or line cards in single channel receive mode, the line card
options file was updated but the line card did not change to the changes pending
state. Therefore, the line card continued to operate with the old Acquisition Aperture
until the configuration was reloaded.
60
Release Notes
40204 NMS Open Port Issue

Starting the NMS services on any NMS server (including the auxiliary servers in a DNMS
setup) caused the nms_config process to run. This process used UDP port 4587. This
port could be exploited for unauthorized access to data, applications, services,
networks and/or devices.
Release Notes
61
62
Release Notes
Known Issues
This chapter describes known issues in iDX Release 3.3.
Known Issues in iDX Release 3.3.4

iDX Release 3.3.4 contains the known issues described in the following paragraphs.
42530 X1 Upgrade to iDX Release 3.3.2.1 Fails Using iBuilder TCP Download
Feature
When using TCP Download in iBuilder to upgrade an X1 remote from a previous iDX
release to iDX Release 3.3.2.1, a connection is established but the download never
starts.
Work-around: Use iBuilder's Multicast Download using UDP feature to perform the
upgrade.
42512 Mobile Remotes May Acquire into Network Before Receiving a Valid New
GPS Input
Remotes that have had a previous serial GPS connection may acquire into the network
before receiving updated GPS inputs. The remotes are wrongly fetching the last
known GPS data stored in their falcon_extra.opt files.
Work-around: When decommissioning or moving a remote, remove the following file
from the remote: falcon_extra.opt.
42509 Changes Pending Observed at Remote When No Changes Made

In iBuilder, after right-clicking on a remote and then deactivating the remote,
Changes Pending is observed at the remote when no changes have been made.
Work-around: After selecting the remote to modify, go to the QOS tab and click OK
without making any changes.
42503 iBuilder Spacecraft Elements Missing When Logged in as VNO User

In iBuilder, after configuring a VNO user group, giving the new group Owned
permission for Teleport, logging out and then logging in as admin, Bandwidth Groups
and Carriers are missing under Network in the iBuilder tree.
Work-around: Restart NMS services and log back in to iBuilder.
Release Notes
63
Known Issues in iDX Release 3.3.4
42498 After Automatic Failover for Rx Only Line Card Changes Pending Observed
and Remote Does Not Acquire into Network
After doing an automatic failover of a line card configured as Rx only, Changes
Pending is observed on the iBuilder tree at the Network level and the remote fails to
acquire into the network.
Work-around: The network operator must manually apply the network level changes
for the remotes to acquire into the network.
42470 Applying Multiple Configurations Causes NMS Server and Revision Server to
Crash
After making multiple changes to remotes and line cards, right-clicking the network in
the iBuilder Tree and selecting Apply ConfigurationMultiple causes the NMS server
(nmssvr) and the Revision server (revsvr) to crash.
Work-around: Restart nmssvr and revsvr.
42411 Cross Polarization Start and Stop Buttons Not Fully Functional on X1 Web
iSite
When perform the Cross Polarization on the X1 using the Web iSite, the Start and Stop
buttons sometimes are not fully functioned as designed. In the case where a user
starts the cross polarization test and switches to a different task, when the user
switches back to the cross polarization tab, the Start button still remains active,
while the Stop button is disabled.
Work-around: Do not switch to other windows while performing the Cross
Polarization test. Alternatively, use iMonitor client to perform the Cross Polarization
test.
42340 iMonitor ATDMA Stats Timeplan Incorrectly Displays Total Slots

In the iMonitor timeplan display (accessed at ATDMA StatsTime PlanSelect
Inroute Groups), the Allocated Slots and Free Slots are not always reported correctly.
Work-Around: None.
41940 Tx Line Card Replacement Not Visible to VNO on iBuilder Tree

After a Host Network Operator (HNO) swaps a Tx line card manually or there is an
automatic failover, the replaced line card appears as a standby line card to a VNO
(Virtual Network Operator) and the new line card is not shown.
Work-around: Proceed as follows:
1.
As HNO, select remote and reassign its visibility or ownership to former settings
and save the settings.
VNOs can now see the new active tx line card; however the standby line card is still
visible.
2.
64
As HNO, login to iBuilder, delete the standby line card, and then recreate it.
Release Notes
Known Issues in iDX Release 3.3.3.1
EVOFT-422 RoHC Compression with UDP Enabled Does Not Reliably Pass UDP
Traffic Upstream
RoHC compression with UDP enabled does not pass UDP traffic upstream in a reliable
manner. Traffic seen on the upstream carrier is received by the PP, but the PP does
not forward the traffic to the upstream switch. Satellite Pseudo Wire Protocol (SPWP)
stats for the SVN show "num_decompress_failed" increment.
Work-Around: None.
EVOFT-414 Incorrect 20 VDC Output Measured at X7 Second IFL Port with LNB
Configured for 13 V or 18 V
At the iBuilder Remote VSAT-2 tab, after selecting a DC Voltage of either 13V or 18V
for an LNB and assigning the LNB to the second IFL of an X7 remote (Rx2 in), a
voltmeter measures an incorrect voltage of 20 VDC at the output of the second IFL.
Work-Around: None.

iDX Release 3.3.3.1 contains the known issues described in the following paragraphs.
42437 Enabling L2oS at Protocol Processor Disables Layer 3 Compression Options

on Remote Information Tab
In iBuilder, enabling L2oS at the Protocol Processor Information tab in a Layer
2/Layer 3 Hybrid mode network causes the Layer 3 TCP Payload, UDP Header, CRTP,
and UDP Payload Compression options on the Remote Information tab to be grayed
out.
3.
At the Protocol Processor Information tab, disable L2oS (it is not necessary to
apply the change).
4.
At the Remote Information tab, enable the appropriate Layer 3 compression

options for the required remote(s).
5.
At the Protocol Processor Information tab, enable L2oS.
or alternatively,
Use custom keys to enable Layer 3 compression options.
42435 L2oS Advanced GRE or IP-in-IP Compression Profiles Causes SARMT to Crash
In iBuilder, selecting GRE or IP-in-IP Header Compression Profiles at the Remote L2oS
tab causes SARMT to crash when downstream or upstream traffic initially starts.
SARMT then recovers and works properly.
Work-around: None.
Release Notes
65
42432 Network Remotes Do Not Receive MCFPE Traffic After Multicast Encryption
is Disabled Then Enabled
In iBuilder, when Multicast Encryption is disabled at the Network Information tab for
a Multicast Overlay network, the Protocol Processor stops sending Dynamic Ciphertext
Channel (DCC) keys to the remotes. If Multicast Encryption is again enabled for the
network, all remotes do not receive multicast encrypted traffic.
1.
Disable Multicast Overlay option at the Network Information tab and click OK.
2.
Apply the configuration by right-clicking the network in the iBuilder Tree and
selecting Apply ConfigurationNetwork.
Wait for the configuration to be applied before proceeding.
3.
Enable Multicast Overlay option at the Network Information tab and click OK.
4.
Apply the configuration by right-clicking the network in the iBuilder Tree and
selecting Apply ConfigurationNetwork.
Different IG
An issue has recently discovered that when a remote is mistakenly moved to a new
network without applying the changes, moving the remote back to its original
network will cause the remote to drop out of the network and become stranded.
Work-Around: When this issue occurs, deactivate the remote first, then reactivate it
to make the remote rejoin the network.
42401 L2SW Mode Overrides Change to VPWSEPC After NMS Upgrade or Restart
In iBuilder, after configuring L2SW Default in VPWS mode at the Protocol Processor
SVNs tab, adding Layer 2 SVNs in VPWS mode, and performing an NMS upgrade or
restart, the L2SW overrides for some of the Layer 2 SVNs changed to VPWSEPC mode.
Work-Around: Reconfigure the Layer 2 SVNs to VPWS mode.
42398 Certain Idle/Dormant States Causing Incorrect Slot Allocation for Remotes
When Idle and Dormant States are enabled at the Remote QoS tab with a frequency
of 1 slot / 8 frames, slot allocation functions correctly. However, when the frequency
is changed to 1 slot / 16 frames or 1 slot / 32 frames, then slot allocation functions
incorrectly and the remote receives too many slots.
Work-Around: Change the measurement interval to greater than the idle/dormant
interval (or 8000 ms for the maximum value). However, slowing down the
measurement interval may adversely affect the remotes ability to transmit at the
correct power during rain fade.
42394 Protocol Processor SVNs Tab Incorrectly Shows Reserved outer SVN ID for
L3 Tag on Layer 3 VLAN After L2OS is Disabled
In iBuilder, after disabling L2oS on a Protocol Processor previously configured for SDT
mode QinQ, the Reserved outer SVN ID for L3 tag incorrectly appears on Layer 3
66
Release Notes
VLANs displayed at the Protocol Processor SVNs tab in a_b format where a = Reserved
outer SVN ID for L3 tag and b = L3VID.
This is a display issue; Layer 3 VLANs work and the options file is generated correctly.
However, the incorrect display may be confusing.
Work-Around: To ensure that Layer 3 VLANs display correctly:
1.
Remove all QinQ SVNs from all remotes.
2.
Delete the QinQ SVNs from the Protocol Processor SVNs tab.
3.
Change the Hub SDT mode from QinQ to VLAN.
42391 Changing Service Level Protocol Generates Incorrect Options File

In iBuilder, right-clicking the Downstream or Upstream folder under
QoSApplication Profiles and modifying a reliable service level in the Rules pane by
changing its protocol from TCP to UDP generated an incorrect options file. As a result,
a remote was unable to transmit traffic.
Work-Around: Create a new service level with the new protocol instead of changing
the protocol of an existing service level.
42387 Unable to Modify All Instances of a Mobile Remote After Modifying GPS
Input Parameters at iBuilder Geo Location Tab
After selecting a GPS input of Serial or NEMEA at the Remote Geo Location tab,
right-clicking the remote and selecting Add to Networks, attempting to modify all
instances of the remote by selecting Modify All Instances fails. Only the first instance
is modified.
Work-Around: Select ViewDetails from the iBuilder main menu to display the
remote instances in the Details pane. Right click and modify each remote instance
separately.
42386 Mobile E8350 and X5 Remotes Not Accessible with Baud Rate Set in iBuilder
Geo Location Tab
After configuring E8350 and X5 remotes in the Remote Geo Location tab with a GPS
input of Serial or NMEA and a default Baud Rate of 4800, attempts to connect to
either remote's console using a serial cable failed. However, the remotes were
accessible when the baud rate was set to 9600.
Work-Around: None.
42385 iMonitor Shows Remote in Rx Only Mode Before iBuilder Applies

Hub/Remote-Side Changes
After enabling Rx Only mode for a remote in iBuilder but before applying hub-side
and remote-side changes, iMonitor Event pane shows the remote is in Rx Only mode.
However, a status check at the remote console shows the remote as On, Locked, In
Network, and Established.
After applying the triggered changes in iBuilder, the remote goes to Rx only mode,
and the remote status at the console changes to Warning, Locked, Waiting for
acquisition.
Release Notes
67
Work-Around: None.
42371 X7 Ignores Wakeup Service Level Trigger for Layer 2 Traffic

An X7 remote in sleep mode with a trigger wakeup service level marking of "ARP" fails
to detect Layer 2 traffic with the "ARP" service level marking. As a result, it fails to
wake up and traffic does not pass.
Work-Around: None.
42360 iBuilder Does Not Accurately Show Remote Upstream MIR

After checking Enable for the Minimum Information Rate (MIR) for Upstream Rate
Shaping at the Remote QoS tab, viewing the change with Remote View Properties
shows that MIR is deselected but the corresponding MIR dialog box is not grayed out.
However, the Protocol Processor accepts the MIR changes.
Work-Around: None.
42358 X1 with SDT Mode of Access Incorrectly Transmits SNAP/LLC Frames OTA
An X1 remote configured with an SDT Mode of Access and with one SVN will transmit
SNAP/LLC frames with VLAN tag ingress at its LAN OTA to the hub. The transmitted
packets observed at the Protocol Processor eth0 interface are SNAP / LLC frames with
an extra VLAN tag attached on top of the existing one.
Work-Around: Disable all SNAP/LLC frames on devices with VLANs connected to the
X1 remote that are configured with SDT mode Access.
42349 Web iSite Does Not Show Layer 2 SVNs for X7 Remote
After configuring L2oS hub-side and remote-side parameters with Layer 2 and Layer 3
SVNs, both types of SVNs appear in the iBuilder Remote Switch tab. However, only
Layer 3 SVNs appear at the Web iSite Ethernet Status VLAN Assignments section.
Work-Around: None.
42337 ATDMA Remotes Idle and Dormant States Cannot Be Set Lower Than 1 Slot
Per 8 Frames
In releases starting with iDX 3.2, the UCP algorithm used with ATDMA remotes
requires at least one burst per second (even with all homogeneous carriers). As a
result, the Idle and Dormant Timeout intervals set at the Remote QoS tab cannot be
greater than 1 second.
Work-Around: None.
42333 Layer 3 VLAN Traffic without Outer Tag Passes in QinQ SDT Layer 2/Layer 3
Hybrid Mode
A hub configured for QinQ SDT Layer 2/Layer 3 Hybrid Mode with a Reserved outer
SVN ID for L3 outer tag defined at the Protocol Processor SVNs tab to identify Layer 3
traffic, passes Layer 3 VLAN traffic that does not contain the outer tag.
Work-Around: Enforcement of outer tag should be configured and performed at the
upstream switch.
68
Release Notes
42331 No Symbol Rate Range Check for Rx2 at iBuilder VSAT-2 Tab
In iBuilder, if Rx2 in is enabled as the second Rx port at the VSAT-2 tab and no value
is entered for Symbol Rate (it remains at 0), the X7-ER remote reports that the
symbol rate is out of range. Unlike Rx1 in, there is no symrate range check for Rx2 in.
Work-Around: None.

Tx Warm Standby
The odu_tx_10_mhz value is incorrectly enabled (set to 1) in the options file of the
line card configured as Tx Warm Standby.
Work-Around: To disable the value, login into the line card console and issue the
following command:
tx ifl10 off
Afterward, verify that it has been turned off by issuing the following command:
tx ifl10
The result should display the following:
Usage: tx ifl10 is Off
42296 iBuilder Allows Configuring MCFP Encryption on Both X7 Remote Rx Ports

iBuilder allows configuring Multicast Fast Path Encryption (MCFPE) on the Rx1 port and
the Rx2 port of a network X7 remote. However, the option files that the NMS then
generates only enable MCFPE traffic on the Rx1 port; the remote is unable to receive
MCFPE traffic on the Rx2 port.
Work-Around: None.
42277 iBuilder Does Not Show VNO User Owns Added Blade
After a VNO super user adds a blade in a teleport owned by the VNO, the Delete
option is grayed out. The same blade is grayed out to an admin user. All other
components behave normally.
Work-around: Revoke the owned permission of the VNO super user and set the owned
permission to the teleport again.
42255 Queue Depth Remains Unchanged After Selecting Reliable Service Level
Type
In iBuilder, after creating an Application Profile (Upstream or Downstream) and a new
Service Level and then selecting a Type of Reliable at the Add Service Level dialog
box, the Queue Depth does not change. It remains at 250 ms and spoofing does not
work.
Work-Around: Manually change the Queue Depth by clicking on Configuration and
entering 20 ms.
Release Notes
69
42247 iBuilder Cannot Create a PP When an Existing PP Uses the SI Table Default
Multicast IP Address
Adding a second Protocol Processor to a Teleport causes iBuilder to issue an error
message:
Failed to create new item: The Multicast IP address of SI table
conflicts with one Protocol Processor's SI Multicast address,
which is still set to the default IP of 239.2.2.1.
Work-Around: Follow the guidelines in the iBuilder User Guide to perform the
following:
Change the default Multicast IP address for the Protocol Processor using it.
Do not use the default Multicast IP address when adding other Protocol
Processors to a teleport.
42078 PP Does Not Assign Nominal Carrier Based on Maximum C/N

For iDX Releases 3.2.2.4, 3.2.2.7, and 3.3.2.1, configuring Maximum C/N on a remote
(Remote tab Adaptive Parameters Carrier Constraints Maximum C/N) does
not change the Nominal Carrier displayed. However, the PP correctly allocates traffic
slots only to carriers permitted by the configured Maximum C/N.
Work-around: None.
42059 Multicast Fastpath Streams Incorrectly Added to Multicast Profile

After adding a new Multicast Application Profile for a network element in iBuilder at
ModifyItemGroup QoSQoS Application and saving the configuration, Fastpath
streams incorrectly appear in the Multicast Application Profile at the Group QoS
Group View. Attempts to remove the streams are unsuccessful and iBuilder continues
to show a Fastpath stream assigned to the profile with a number from 1 to x, where x
is the last Fastpath number defined.
Work-around: None.
41891 Remote Unable to Retrieve Hub Side and Remote Side Options Files
On occasion, an issue with the Dynamic Feature and Options Exchange (DFOE)
protocol prevents a remote from retrieving hub-side and remote-side option files
when the NMS_TCP service level has Spoofing enabled at both the NMS Downstream
and Upstream Application Profiles.
Work-around: None.
41373 Layer 3 X1 Remote Passes Tagged Packets Upstream in Untagged Mode

In untagged mode, an X1 remote configured with an additional VLAN and the default
VLAN receives traffic from a tagged device and passes tagged packets in the upstream
direction.
Work-around: None.
70
Release Notes
41369 iBuilder Add Rule Window Allows IPv6 Address Prefix of 0

At the iBuilder Add Rule window, a user is able to configure a valid rule that specifies
an IPv6 Destination IP address or an IPv6 Source IP address with an invalid prefix of 0.
Work-around: Do not configure the invalid address prefix of 0.
41165 X7 Switch Port Only Passes Ethertype 8100 When Changed from VLAN to
TRUNK
When the switch port configuration for an X7 remote is changed at the iBuilder
Remote Switch tab from selective VLANs to All VLANs, the X7 remote only passes
Ethertype 8100; the X7 remote does not pass Ethertype 9100.
Work-around: Reboot the X7 remote.
41153 X7 Remote Priority Service Level Loading Issue

For an X7 remote multi-service level upstream application profile, when Cost-Based
(default) traffic service level scheduling is changed to Priority Queue, it remains in
Priority Queue until a Falcon restart even if it is subsequently changed to Cost-Based
or to Best Effort.
Work-around: Restart Falcon using the service idirect_falcon restart
command.
40812 X7 Does Not Support MTU=1540 in L2oS Mode

After configuring an X7 remote in iBuilder in L2oS mode and changing its Maximum
Transmission Unit (MTU) to 1540 bytes and also changing the MTU to 1540 bytes on the
X7's eth0 and tun0 interfaces using the ipconfig command, packets greater than
1522 bytes do not go through the remote.
Work-around: None.
38332 Inoperable Buttons on iMonitor Downstream/Upstream Group Stats Screen

After opening the Downstream or Upstream QoS Stats views in iMonitor and selecting
a profile, the Bits, Bytes, and Symbol buttons on the left side of the screen are grayed
out and do not work.
Work-around: None.
Release Notes
71

EVOFT-442 (42088) Queue Depth Value Incorrectly Sets As 250ms When Reliable
Option is Enabled in the Service Level
When creating an Application Profile for both upstream and downstream, the Queue
Depth value automatically sets to 250 ms when the Reliable option in the service
level is selected. The correct value should be 20 ms.
Work-Around: Manually change the value to 20 ms.

42411 Cross Polarization Start and Stop Buttons Not Fully Functional on X1 Web
iSite
When perform the Cross Polarization on the X1 using the Web iSite, the Start and Stop
buttons sometimes are not fully functioned as designed. In the case where a user
starts the cross polarization test and switches to a different task, when the user
switches back to the cross polarization tab, the Start button still remains active,
while the Stop button is disabled.
Work-around: Do not switch to other windows while performing the Cross
Polarization test. Alternatively, use iMonitor client to perform the Cross Polarization
test.
Different IG
An issue has recently discovered that when a remote is mistakenly moved to a new
network without applying the changes, moving the remote back to its original
network will cause the remote to drop out of the network and become stranded.
Work-Around: When this issue occurs, deactivate the remote first, then reactivate it
to make the remote rejoin the network.
31376 Duplicate Packets Observe on X7 LAN Interface

An issue with the X7 remote generates duplicate packets on its LAN interface when
responding to ping has been observed. The main reason for the duplicate reply
packets is that both the Falcon process and Linux reply to the ping request.
Work-Around: None.
72
Release Notes

42291Center Frequency Changes for XLC-M Line Card Configured with SCPC MCD
When Upgrading From iDX 3.2.2.7 to iDX 3.3.2.1
After upgrading the NMS from iDX Release 3.2.2.7 to iDX Release 3.3.2.1, the Center
Frequency value changed to 9560 MHz for the XLC-M line card which is configured
with SCPC MCD. This issue may cause the line card upgrade to fail and the remotes
may fail to reacquire into the network.
Work-Around: After the upgrade, perform the following steps to correct the Center
Frequency and reassign the SCPC return channels to the line card:
1.
Using the iBuilder client, double-click the Transponder and make a note of the
Translation Frequency value.
2.
Right-click the multi-channel line card and select Modify Configuration.
3.
From the Receive Properties area, click Configure Carriers.
4.
Update the line card Center Frequency value by adding the noted value in Step 1
to the existing value.
5.
Select the SCPC Upstream Carriers to reassign to the line card.
6.
Click OK to exit the Select Carriers dialog box.
7.
Click OK again to save the line card configuration. At this point, there should be
changes pending at the network level of the iBuilder tree.
8.
Apply the changes to the network.
9.
Verify that the SCPC remotes able to join the network.

Tx Warm Standby
The odu_tx_10_mhz value is incorrectly enabled (set to 1) in the options file of the
line card configured as Tx Warm Standby.
Work-Around: To disable the value, login into the line card console and issue the
following command:
tx ifl10 off
Afterward, verify that it has been turned off by issuing the following command:
tx ifl10
The result should display the following:
Usage: tx ifl10 is Off
Release Notes
73
42216 Unable to Create a New PP Controller in iBuilder When an Existing One is

Using the Default SI Tables Multicast IP Address
When creating a new PP Controller, iBuilder client would fail to create the new PP
Controller and generate an error message Failed to create new item: The Multicast
IP address of SI table conflicts with one Protocol Processor's SI Multicast address,
which is still set to the default IP of 239.2.2.1.
Work-Around: Before adding the new PP Controller, change the SI multicast address
of the existing PP Controller to a different multicast address.
NOTE: It is recommended to change the default SI multicast address when
configuring a new PP Controller.
42139 Activating Multiple IGCs Causes the Network to Switch Between IGCs and
Temporary Outages
When activating more than one IGCs, the network starts to switch between IGCs for
some unknown reasons. After some times, the PP blades stop sending sweeps to the
remotes, which causes temporary outages, until the PP rebalance is performed.
Work-Around: None.

42136, 41802 XLC-M (SCD Mode) and XLC-11 Line Cards Do Not Work with
Wideband Frequencies
Remotes are unable to acquire into a network configured with wideband receive
frequencies higher than 1700 MHz with these hub line cards: an XLC-M in Single
Channel Mode (SCD) and an XLC-11 (Tx/RX). The remote acquires fine with an XLC-M
line card in Multi-Channel Mode.
Work-around: If using wideband frequencies, use an XLC-M line card in Multi-Channel
Mode (MCD).
NOTE: If only one carrier is added, an XLC-M line card in MCD mode does not
require a license.
41777 No Automatic Cleanup for /tmp/build_package Directory

Performing a Multicast Download or TCP Download on an NMS server can cause an out
of space issue because there is no automatic cleanup of the /tmp/build_package
directory. This is not an issue when using Revision Server.
Work-around: Clean files in the tmp folder that are older than three days by adding
the following two lines in the CRONTAB file on the Primary NMS and the Backup NMS:
0 0 * * * find /tmp/build_package -mtime +3 -exec rm -rf {} \
0 5 * * * find /tmp/addr* -mtime +3 -exec rm -rf {} \
74
Release Notes
41696,41697, 41458 Remote Tags Multicast Fast Path Traffic on Default VLAN with
VLAN ID 1 When Two or More Other VLANs are Configured with Tagging
Enabled
In this specific scenario, the multicast Fast Path traffic goes from PP to remote
untagged on the default VLAN, but when it comes out of the LAN port of the remote it
is tagged with VLAN 1 when there are two or more other VLANs configured and
tagging is enabled. As a result, end devices that are expecting untagged Multicast
traffic cannot receive the traffic.
Work-around: In this scenario, either use all tagged VLANs or use regular Multicast
instead of Multicast Fast Path.
41685, 41416 Upstream QoS Statistics Do Not Match SAT Traffic If Inroute Carrier
Payload is Changed
If an upstream carriers payload is changed from iBuilder, the Statistics server (nrdsvr)
will not get updated automatically; as a result, the upstream QOS stats that iMonitor
reports are inaccurate. This issue exists in all iDX releases.
Work-around: Restart the Statistics server (nrdsvr).
41684 Remote Goes to Incomplete State When Moved to SCPC Carrier

In iBuilder, sometimes moving a remote that was not previously a assigned to an SCPC
carrier from an ATDMA inroute to an SCPC line card causes the remote to go to
Deactivation Pending status. While moving the remote, iBuilder gives a warning that
remote will be incomplete until a upstream remote profile is assigned even though
the upstream profile was checked in the Move Remote dialog box.
Work-around: Manually modify the remote and apply the appropriate Upstream
profile.
41658 Certain QoS Matching Rules Do Not Work

In iBuilder, it was observed the Rules pane for Application or Filter Profiles has
certain check boxes with matching rules that do not function in iDX Release 3.3.2.1.
These include SVN ID, SVN PCP, Ethernet Type, Effective Ethernet Type, VLAN PCP,
and VID Ranges. These fields are specific to L2oS support in a future release.
Work-Around: These fields should not be used with this release.
41654, 41843 iBuilder Spacecraft Elements Missing When Logged in as VNO User
In iBuilder, after configuring a VNO user group, giving the new group Owned
permission for Teleport, logging out and then logging in as admin, Bandwidth Groups
and Carriers are missing under Network in the iBuilder tree.
Work-around: Restart NMS services and log back in to iBuilder.
Release Notes
75
41643 X1 Upgrade to iDX Release 3.3.2.1 Fails Using iBuilder TCP Download
Feature
When using TCP Download in iBuilder to upgrade an X1 remote from a previous iDX
release to iDX Release 3.3.2.1, a connection is established but the download never
starts.
Work-around: Use iBuilder's Multicast Download using UDP feature to perform the
upgrade.
41620 Enable NAT Checkbox is Disabled for e150 Remote

In iBuilder, after selecting an e150 remote to modify at RemoteIP ConfigPort
Forwarding, the Enable NAT (Network Address Translation) check box is disabled.
Work-around: None.
41579 Incorrect CIR Values Produced After VNO Modifies CIR

It was observed that when Virtual Network Operators (VNOs) without visibility to
carriers modified CIR/MIR values for the remotes they own, sometimes incorrect
CIR/MIR values were saved after modification.
Additionally, when Host Network Operators (HNOs) attempted to resolve the problem
by resetting the correct CIR/MIR values, sometimes the carriers were not visible to
the HNOs.
Work-around: VNOs should note desired CIR/MIR values and in case the problem is
seen, they should contact the HNO to reset the correct CIR/MIR values.
Before resetting the correct CIR/MIR values, the HNO should restart Configuration
Server as follows:
1.
Using a Secure Shell (SSH) client such as PuTTY, log on to the root account of the
NMS server machine.
2.
Enter the following command to restart the Config Server:

service idirect_nms restart nmssvr
3.
Log off of the NMS server machine.
41569 Mobile Remotes May Acquire into Network Before Receiving a Valid New
GPS Input
Remotes that have had a previous serial GPS connection may acquire into the network
before receiving updated GPS inputs. The remotes are wrongly fetching the last
known GPS data stored in their falcon_extra.opt files.
Work-around: When decommissioning or moving a remote, remove the following file
from the remote: falcon_extra.opt.
41540 Stopping a Revision Server Remote Package Download Hangs Revision

Server Dialog Box
After selecting a remote and starting an upgrade by right-clicking a network in the
iBuilder Tree and selecting Package Download Revision ServerRevision Server,
the download proceeds normally; however, clicking Stop Upgrade causes the Revision
76
Release Notes
Server dialog box to hang. This behavior only occurs when downloading the remote
package; it does not occur while downloading the BSP package.
Work-around: Restart the Revision server with the service idirect_nms restart revsvr
command.
41497 SAT Traffic Graph Displays Incorrect Real Time After iBuilder Changes
After iBuilder modifications cause a re-scaling of an existing real time iMonitor SAT
Traffic Graph, the time that appears on the SAT Traffic Graph lags behind the current
NMS time by several minutes.
Work-around: Close and then reopen the SAT Traffic Graph.
41373 Layer 3 X1 Remote Passes Tagged Packets Upstream in Untagged Mode

In untagged mode, an X1 remote configured with an additional VLAN and the default
VLAN receives traffic from a tagged device and passes tagged packets in the upstream
direction.
Work-around: Switch remote to tagged mode.
41329 iBuilder May Crash or Hang with 12 or More Open Control Panels
iBuilder may crash or hang when opening 12 or more remote Control Panel windows.
Work-around: None.
41274 Upstream Network Subnet Mask Filter Rule for X1 Remote Does Not Work
An upstream network subnet mask filter rule for an X1 remote created in iBuilder at
the Filter Profile dialog box does not work when used with 255.0.0.0, 255.255.0.0,
255.255.255.0, or any other subnets; however, it works for a host rule (e.g.,
255.255.255.255).
Work-around: Specify as host instead of network. For example, use 255.255.255.255
for the subnet mask instead of 255.255.255.0.
41095 PP Sends Traffic to Absent Remote Side Local LAN Device

When a local LAN device on the remote side disappears (e.g., a cable is unplugged),
the hub-side SAROUTER process does not receive any notification so traffic to the MAC
address of the absent device continues until the configured MAC address aging timer
expires. If the missing device is plugged into another LAN, the SAROUTER process will
update the new target destination.
Work-around: None.
38986 iBuilder Does Not Enforce Limit of 32 Carriers for Inroute Groups
in iBuilder, when more than 32 carriers were added to an inroute group and the
configuration changes were applied to the network, all remotes in the most recently
added inroute group went out of network.
Work-around: Remove any carriers above the 32 carrier limit from the inroute group.
Release Notes
77
34713 Rx Hub Line Card Digital AGC Transient Effects During MODCOD Switchover
When changes in MODCOD occur during carrier switch-over for Hub side adaptivity
(IGC switching), the Automatic Gain Control (AGC) value for the second MODCOD is
not updated for several seconds. Transient errors may occur during this interval if the
optimal digital gain for the channel is significantly different between the first
MODCOD and the second MODCOD.
For each inroute carrier (in order to avoid transient errors), the difference in
MODCOD C/N thresholds across all three inroute group compositions should not
exceed 6 dB.
Work-around: iDirect recommends that customers design their Inroute Group
Compositions (IGCs) to avoid large jumps in MODCOD for any given carrier.

41153 Falcon-Based Remote Priority Service Level Loading Issue

For a Falcon-based remote multi-service level upstream application profile, when
Cost-Based (default) traffic service level scheduling is changed to Priority Queue, it
remains in Priority Queue until a Falcon restart even if it is subsequently changed to
Cost-Based or to Best Effort.
Work-around: Restart Falcon.
For a group of remotes: Use the iBuilder TCP Download feature.
For individual remotes: Right-click the remote and select Reset

RemoteReliable (TCP).
Known Issues in iDX Release 3.3

iDX Release 3.3 contains the known issues described in the following paragraphs.
Data Path Issues

Data Path issues include protocol processor, hub line card, and remote issues, as well as
Systray message and MapTools related issues.
40399, 39823 iBuilder: Apply ConfigurationPush Remote-Side with Reset (UDP)

Not Working
After upgrading to iDX Release 3.3, this issue was seen in an iDirect system with
multiple protocol processor blades. In that instance, attempts to update the options
files of the remotes by selecting the following command in iBuilder did not work:
Apply ConfigurationPush Remote-Side with Reset (UDP)
This problem can occur if the UDP push is sent to a PP blade other than the blade
responsible for network multicast traffic. The blade that handles multicast for the
network is responsible for forwarding the UDP push to the line card.
78
Release Notes
Normally, when a blade not responsible for network multicast receives the UPD push,
it forwards it as a multicast message to the NMS multicast address. When the blade
responsible for multicast receives the multicast message, it forwards the UDP push to
the transmit line card for transmission on the outbound carrier. However, when the
problem was observed, the UPD push was not forwarded by the non-multicast blade
that originally received it to the NMS multicast address.
Work-around:
1.
Ensure that multicast forwarding is enabled on the upstream switch.
2.
Right-click the Protocol Processor in the iBuilder tree and select ModifyItem.
3.
Under Multicast Groups, click Add.
4.
In the Persistent Multicast Group dialog box:

a. For VLAN ID, enter 1.
b. For Address, enter the NMS multicast address (typically 239.192.0.0).
5.
Click OK to close the Persistent Multicast Group dialog box.
6.
Click OK again to save the changes.
7.
Right-click the Protocol Processor and select Apply Configuration.
40394 Time Until Beam Switch Missing from Systray Message

Byte 172 of the Systray message from the Satellite Router to the NMS does not display
the time until beam switch value.
Work-around: None.
40321 Link Encryption Fails for X1 Satellite Router When Implementing

Geographic Redundancy
Adding an instance of an X1 Satellite Router to a second network and then enabling
Link Encryption causes a latency timeout.
Work-around: Enable Link Encryption to the X1 Satellite Router instance in the first
network before adding the X1 Satellite Router to the second network.
40069 Data Missing Warning on Remotes in Inclined Orbit Network

This problem has been seen when using single channel receive line cards in a network
using a satellite in inclined orbit. Occasionally, iMonitor reports a Data Missing
Warning for remotes in the inroute group indicating that a high number of remote
bursts are being lost.
Work-around: Restart the receive line card reporting the errors.
39974 Upstream CRC Errors When Using High-Speed Comms On The Move
CRC errors on upstream carriers may be reported in iMonitor when using iDirects
High-Speed Comms On The Move (COTM) feature. Such CRC errors can occur if the
timing offset reaches the traffic slot aperture boundary. In the case that upstream
CRC errors are being caused by problems with the timing offset in a high-speed
Release Notes
79
network, the following work-around should correct the problem. If this work-around
does not solve the issue, contact the iDirect TAC.
Work-around:
Configure the following custom key in the Hub-side Configuration area of the Remote
Custom tab for all remotes in the inroute group:
[REMOTE_DEFINITION]
ucp_update_rate = 4
NOTE: iDirect recommends setting ucp_update_rate to no less that 2.
39971 Single Channel TDMA Line Card Must Be Reset After Carrier Changes
If changes are made to a carrier assigned to a line card in Single Channel TDMA
Receive Mode, the line card must be reset. This does not apply to line cards in Single
Channel TDMA (Adaptive) Receive Mode or Multiple Channel Receive Mode.
For details, see Single Channel Receive Line Card Must Be Reset After Carrier
Changes on page 29.
39681 Fade Slope Margin (M1) Negative After Upgrade to iDX Release 3.3
After upgrading to iDX Release 3.3, the Fade Slope Margin (M1) for existing inroute
groups was incorrectly set to a negative number in some cases. The Fade Slope
Margin (M1) is configured in iBuilder on the Uplink Control tab of the Inroute Group.
iDirect recommends checking the values of all Uplink Control Parameters for all
Inroute Groups immediately after upgrading to iDX 3.3. Incorrect values may affect
the ability of the remotes to operate in the network.
Values for the Uplink Control Parameters depend on the network design. The default
values for M1, M2 and M3 after an upgrade from a pre-3.3 release should be:
Fade Slope Margin (M1): 0.6 dB
Hysteresis Margin (M2): 1.0 dB
Acquisition Margin (M3): 2.0 dB

NOTE: For homogeneous inroute groups, M3 should be set to 0.
39170 Standby Line Card with Changes Pending Cannot Complete Automatic
Failover
If there are changes pending on a transmit or receive line card, automatic failover
does not complete.
Work-around: Do not leave changes pending on any standby line cards.
80
Release Notes
38751 SCPC Remotes Cannot Acquire After Change to Initial Power

If the Initial Power is changed for an SCPC remote, the remote may lose the network
and be unable to re-acquire when transmitting to a line card in Single Channel
Receive Mode. This is caused by a problem on the receive line card.
Work-around: Restart the receive line card.
See also, Single Channel Receive Line Card Must Be Reset After Carrier Changes on
page 29.
38634 Remotes on Low C/N0 Upstream Carriers May Not Receive Correct Slot
Allocation When CIR Is Oversubscribed
This issue occurs only in inroute groups containing heterogeneous upstream carriers
(i.e., carriers with different MODCODs and/or symbol rates) with lower C/N0
thresholds when Committed Information Rate (CIR) is oversubscribed. In that case,
Virtual Remotes using the lower C/N0 carriers do not receive the correct number of
upstream time slots for CIR with respect to Allocation Fairness.
Work-around: Ensure that the upstream carriers with lower C/N0 have sufficient
bandwidth capacity to avoid over subscribing CIR.
38633, 37866 Remotes on Upstream Carriers with Low C/N0 May Not Receive
Correct Cost-Based Bandwidth
This issue occurs only in inroute groups containing heterogeneous upstream carriers
(that is, carriers with different MODCODs and/or symbol rates) when there is
congestion on the carriers with lower C/N0 thresholds. In that case, Virtual Remotes
using the lower C/N0 carriers do not receive the correct number of time slots
according to the relative costs of their cost-based service levels.
Work-around: Ensure that the upstream carriers with lower C/N0 have sufficient
bandwidth capacity when these carriers become the only carriers some remotes can
use.
38572 Remotes on SCPC Return Channels with Spreading Factor 4 or 8 and Block
Size 438 Bytes May Not Join the Network
Remotes transmitting a spread SCPC return channel with spreading factor of 4 or 8
and block size of 438 bytes may not be able to join the network. This can occur even
if the SCPC initial power for the remote is properly set.
Work-around: A network custom key must be configured in iBuilder for each SCPC
return channel having the following characteristics:
Spreading Factor = 4 or 8
Block size = 438 bytes
Chip rate above 4 Mcps
First, determine the inroute ID of the SCPC return channels in iMonitor:
Release Notes
1.
Right-click the line card in the iMonitor tree and select Line Card Stats.
2.
Click OK in the Select Line Cards dialog box.
81
3.
In the HLC Traffic Graph window, select the SCPC channel of interest.
4.
Click the second tab to view the tabular data and find the Inroute ID column. This
is the inroute ID of the SCPC carrier and is required by the network custom key.
5.
For each SCPC return channel, add the following custom key in iBuilder on the
Custom tab of the Network:
[INROUTE_xx]
fec_blocks_per_frame = 2
where xx is the inroute ID of the SCPC return channel.
CAUTION: If the custom key is used and an inroute is deleted, the presence of the
custom key will prevent the Protocol Processor from loading the option file. This
will result in network outage.
38463 Multicast Encryption Enabled without Link Encryption License Causes

Remotes to Drop out of Network
When a Protocol Processor does not have an Link Encryption license, and Multicast
Encryption is enabled, all remotes drop out of network due to reload fail.
Work-around: Do not enable Multicast Encryption without appropriate encryption
licenses applied to the Protocol Processor.
38002 Over Correction in Frequency Offset Occurred When COTM Was Set to
Avionics and Two or More Remotes Were Added
An overcorrection in the frequency offset occurred in a network configured with two
carriers, the lowest possible symbol rate of 400 ksps, and Communications-On-theMove (COTM) set to Avionics. This limited support for 400 ksps operation, the lowest
supported symbol rate in HS-COTM mode.
Work-around: None.
36021 All Protocol Processor Processes Down After Cycling Power on Upstream
and Tunnel Switches
It has been observed that after cycling power on either the upstream switch or on the
tunnel switch, there is no ACQ sweep on the network.
Work-around: Restart the Protocol Processor service.
28422 Adding Incomplete Line Card to Inroute Group Can Cause Network Outage
If an Upstream carrier is assigned to a line card that is not already assigned to a
chassis slot, and subsequently the carrier is assigned to a new inroute group, applying
the changes at the Network level causes the remotes in that network to start to show
LATENCY TIMEOUT alarms, and eventually go down.
Work-around: Do not assign a carrier to a new inroute group unless the line card has
been assigned to a chassis slot.
82
Release Notes
27082 Remote May Switch to Beam Even if Satellite is Below Minimum Look Angle
When a remote that is roaming within two or more networks is positioned such that
only one satellite is visible at all times while the others are below the minimum look
angle, the remote goes out of the network on the current beam.
This issue does not affect network operation because the remote is already out of the
network and there are no other beams available. The net impact, however, is that the
antenna tries to reposition itself every 5 minutes. This behavior could result in
equipment damage.
Work-around: The following two options can help avoid this issue if the remotes are
expected to maintain a stationary position for a long durationfor example 1 hour.
1.
In iBuilder, use the following custom key at the remote side to increase the
default timeout:
[BEAMS_LOCAL]
net_state_timeout= 300 (default is 300 seconds)
2.
Enter the command below, from the remote console, to lock remote to a beam:
Beamselector lock <beam number>
The remote must be rebooted in order to clear the lock.
NMS/Reporting Issues
NMS/Reporting issues include iVantage and NMS server side issues.
NOTE: iVantage issues include iBuilder, iMonitor, and Web iSite related issues.
40442, 38333 Upstream QoS Stats Display No Data Under the VR Default Profile
For a Satellite Router configured with a Remote Service Profile, iMonitor does not
display service level data at Upstream QoS StatsDefaultVRDEFAULT even
when a remote-side custom key enabling upstream QoS service level statistics is
defined.
Work-around: None.
40422 iBuilder: Incorrect Revision Server Mode Status After Upgrade

Under certain circumstances, Revserver cannot detect the UpRev state of a Satellite
Router. As a result, the Satellite Router may retrieve the upgrade package multiple
times and reset multiple times.
Workaround: In iBuilder, perform one of the following for the affected Satellite
Router:
Release Notes
Select RetrieveActive Remote-Side Configuration.
Manually deselect the Satellite Router from the upgrade list.
83
40411 iMonitor Conditions Pane Does Not Display Historical Severity Correctly
When retrieving historical conditions, the Severity column in the Conditions pane
incorrectly shows Unknown for all components.
Work-around: None.
40398, 39852 iBuilder: Users without GQoS Planning Permission Cannot Assign
Remote Service Profile After Moving a Remote
When an iBuilder user without GQoS Planning permission moves a remote to another
network, the Remote Service Profiles is not displayed and no profile is selected for
the remote. This causes the remote to become incomplete and changes the remote
state to Deactivation Pending.
Work-Around: After moving the remote, modify the remote and select the QoS
profile.
40388 iBuilder: No Pending Changes After Enabling/Disabling RIPv2

When using iBuilder for enabling or disabling RIPv2 on a Protocol Processor blade for a
selected VLAN, pending changes are not observed.
Work-around: Use the following steps to observe pending changes after enabling or
disabling RIPv2:
1.
Right-click the Protocol Processor stack in the iBuilder Tree and select
ModifyItem.
2.
Select the VLANs tab in the Protocol Processor dialog box.
3.
Select a VLAN and click Add to display the VLAN dialog box.
4.
Click on Override Address.
5.
Check or uncheck the Enable RIPv2 check box.
40379 X7 Satellite Router Fan Status Issue

On the X7 Satellite Router, the FAN LED does not illuminate Green when the fans are
working and it does not illuminate Red when there is a fan failure. Also, Web iSite
does not show X7 FAN status and iMonitor does not provide warnings about X7 fan
problems.
Work-around: None.
40350, 38764 iBuilder CIR/MIR Configuration for a Set of Satellite Routers Does
Not Work
When using iBuilder for configuring the same CIR/MIR values on a set of Satellite
Routers, iBuilder shows the CIR/MIR values as changed. However, only the
configuration for the first Satellite Router is changed.
Work-around: Use QoS multiple service profiles to configure the same CIR/MIR values
on a set of Satellite Routers.
84
Release Notes
40213, 36617, 36105 iMonitor: SATCOM Statistics Interval May Not be Precisely 60
Seconds
When retrieving historical data for SATCOM graph, the data should be presented in 60
second intervals. However, due to internal calculation logic, the interval may be a
few seconds off in some cases, resulting in an interval that is not precisely 60
seconds.
40146 iBuilder: Modifying Initial Power on SCPC Remote May Cause VLAN Mode to
Change
Modifying the SCPC Initial Power on a remote for an upstream carrier that is not
assigned to that remote may incorrectly cause the VLAN mode to change in the
options files, resulting in hub-side and remote-side changes pending. This problem
only occurs after the following sequence of events:
1. SCPC Initial Power is configured without configuring the SCPC Max Power.
2. iBuilder displays the error message: Max Power of SCPC Carrier cannot be Null.
3. SCPC Max Power is then configured.
This bug is not seen under other circumstances. For example, it is not seen when the
SCPC initial power for the carrier assigned to the remote is changed or when the SCPC
Maximum Power and SCPC Initial Power for a carrier not assigned to the remote are
modified at the same time.
Work-around:
When modifying the SCPC and Initial Powers for carriers other than the carrier
assigned to the remote, avoid assigning the Initial Power without also assigning the
Max Power.
40070 iBuilder: Guard Interval Not Updated in Network Options File After Carrier
Symbol Rate Change
Modifying the symbol rate for an upstream TDMA carrier that is assigned to an inroute
group can cause the Guard Interval configured for the inroute group to change.
Although changes pending are triggered at the network level, the Guard Interval is
not updated to the new value in the configuration.
Work-around:
1. In the iBuilder tree, right-click the inroute group and select ModifyItem.
2. Without changing the configuration, click OK.
3. Apply the changes to the network.
40040, 40082 iMonitor: Nominal Carrier of Remote May Be Mis-Identified on

Upstream C/N0 and Thresholds Display
In iMonitor, the Timeline tab of the Upstream C/N0 and Thresholds display contains a
graph showing the C/N0 measurements for bursts received from individual remotes
versus the C/N0 threshold of the nominal carrier of the remote. If the set of upstream
carriers of a remotes inroute group on which the remote is allowed to transmit are
Release Notes
85
limited, the C/N0 threshold of the nominal carrier of the remote displayed on the
graph may the C/N0 threshold of the wrong carrier.
For example, an Evolution X1 or e150 remote cannot support a symbol rate greater
than 2 Msps in iDX Release 3.3. If, for example, the inroute group of an X1 includes a
4 Msps carrier, and the system is operating at optimal capacity, the Upstream C/N0
and Thresholds graph will incorrectly show the C/N0 of the 4 Msps carrier as long as
the remote has sufficient power to transmit on that carrier. However, because the
remote is not allowed to use the 4 Msps carrier, no slots on that carrier are actually
allocated to the remote.
39203 Web iSite Does Not Show Statistics When GPS Input is Selected for Antenna
X7 Web iSite does not show RX Composite Power, RX SNR, CRC 8, CRC 32, TX Power,
Max TX Power, Initial Power, Latitude, and Longitude when GPS input is configured
for Antenna. For a Stationary or Mobile Remote using Manual or Serial GPS input the
stats are populated correctly, but these stats are not populated when the GPS type is
selected as Antenna.
Work-around: None.
39181 When Logged in as VNO Super User, Standby Line Cards IP Address Displays
0.0.0.0
When logged in as a VNO super user, and selecting View for a standby line card, the
Information tab displays the IP Address as 0.0.0.0. When selecting Modify for a
standby mode line cards, the IP address is correctly configured.
38994 iMonitor: Assigned SCPC Carriers Are Not Selected in RX Line Card When
Logged in as Newly-Created VNO User
When logged on to a MCD-SCPC remote as newly created VNO user, all assigned Rx
Line Card carriers are not selected. When logged on as admin, all assigned carriers
are selected.
38970, 40232 NMS Server Crashes When Deleting an Active VNO User
The NMS Server crashes when a user with admin privileges deletes a newly created
VNO user from an VNO user group with owned permissions for a remote.
38950 Original VLAN ID Changes on X7 Remote When DNS Cache is Enabled

Enabling the DNS cache on an X7 remote with GRE acceleration causes the VLAN ID to
change. Both the hub and remote side display Change Pending for VLAN IDs.
38672 iBuilder: Disabling FLLDacErrors Warning Type Causes Receive Line Card
Carrier to Be Unassigned
Disabling the FLLDacError warning type for transmit and receive line cards results in
the carrier to be unassigned from the receive line cards.
86
Release Notes
38530 iMonitor: False Warning for Erroneous Report of CRC8 and CRC32 Errors on
Acquisition
When a remote first acquires the network, the first remote status message shows a
very large value for CRC8 and CRC32 errors. These erroneous values cause a false
warning to appear in iMonitor. This warning can be ignored.
38493 iMonitor Probe Warning: Modulated Carrier Interferes With Existing 5% ROF
Carrier
When establishing a modulated carrier using iMonitor Probe, a warning message
appears stating that the carrier will interfere with an existing carrier (5% ROF) even
though the message is false.
38437 Using Console Commands to Change Tx Frequency Disables RF Energy

When using the tx cli enable command to commission a Satellite Router,
changing the Tx Frequency disables RF output. To enable RF output, it is necessary to
reset the symbol rates and modulation to the default values.
Work-around: Use the following steps to re-enable RF Tx output:
1.
Set the transmit frequency in MHz:

tx freq 1000
2.
Set the transmit modulation:

tx mod 2
3.
# 0 = BPSK, 1 = QPSK, 2 = 8PSK
Set the symbol rate:

tx symrate 1000000
4.
Set the transmit power:

tx power -25
5.
# symrate in symbols/sec
# Set output in dBm
Turn on PN mode or turn on CW mode:

tx pn or tx cw
38251 iBuilder Falsely Reports Failed to Assign Standby Error Message after
Successfully Assigning Standby Line Card
iBuilder falsely reports Failed to assign standby error message after successfully
assigning the standby line card. This message is displayed only when a Single Channel
TDMA MCD-Rx line card is assigned as warm standby to a Multi-Channel TDMA MCDRX
line card.
37042 iMonitor Shows Tx Bytes and Attempts = 0 in Tx Line Card Stats

In iMonitor, Tx Line Card Statistics display Tx Bytes and Attempts = 0. Since
these fields are only applicable in iNFINITI networks, which are no longer supported,
they do not affect operation.
Release Notes
87
36113 Remote Warning Remains in Active Condition When Remote is De-activated

In iMonitor, a remote warning is still displayed in the Active Conditions tab view even
if the remote is deactivated. The remote state in Tree View is displayed correctly.
35904 SNMP Returns Invalid Result For Out-of-Network Remotes

Out-of-network remotes should respond to IP and Over the Air (OTA) bandwidth
Object IDs (OIDs) with the last counter value while out of network. However, SNMP
reports the following message when a remote is out-of-network:
[root@NMS@31 snmpsvr]# snmpwalk localhost -v 2c -c public rxtcp
IDIRECT-REMOTE-MIB::rxtcp = No Such Instance currently exists at
this OID
35621 X1 Satellite Router Transmit LED is Green when Transmit is Disabled

The Tx LED of the X1 Satellite Router is green when transmit is disabled (no timeplan
sent.) The LED should be amber under such conditions.
34442 DSCP Marking Not Working as Expected

When the Application Profile Rules has a DSCP condition set and the Service Level is
configured to mark the packet with a different DSCP value, the change does not take
effect and matching data packets are not marked. This issue occurs in upstream or
downstream Application Service Groups or Remote Service Groups.
Work-around: Make any QoS related network level change or remote hub side change
and apply the configuration.
34396 iMonitorSAT Traffic Graph Not Appearing Correctly with Respect to X-Axis
It was reported that the iMonitor SAT traffic graph does not appear positioned
correctly with respect to the grid lines of the X-axis, based on the corresponding time
stamp. It appears that the grid is slightly compressed from both sides of the graph.
26749 iBuilderChanges to VLAN Subnet and Gateway at PP Blade Not Shown

When changes are made in iBuilder and applied to the VLAN Subnet Mask and
Gateway, the modifications are not reflected as Changes Pending at the Protocol
Processor Blade level.
Work-around: Make the required changes to the VLAN from the Protocol Processor
level. The Changes Pending icon displays.
88
Release Notes
Installation Instructions
This chapter contains instructions for downloading the iDX Release 3.3 software and any
special installation notes. It contains the following sections:
Downloading Required Files for iDX Release 3.3.x.x
Installation/Upgrade Notes
For detailed installation information, see the Network Upgrade Procedure Guide for iDX
Release 3.0.0.x and Later to iDX Release 3.3.x.x available on the TAC Web site.
Contact the TAC for questions regarding the upgrade instructions provided in this section or
additional information is needed. Refer to Getting Help on page xii for TAC contact
information.

The software packages are available for download on both iDirect and iDirectGov TAC Web
sites. Additional software licenses may be required for software downloads.
NOTE: The software download instructions following the table below only show
the latest complete software releases. Please use the table below to substitute
the software version with the iDX software version that is specifically licensed for
the network upgrade.
For any patch software release downloading instructions, please refer to the
applicable patch download and installation instructions in the subsequent
chapters.
iDX 3.3.x.x Released Versions
3.3
3.3.2.1
3.3.2.2
3.3.3
Release Notes
89
iDirect software download instructions

This section provides download instructions for software releases and supplemental software
on iDirect TAC Web site.
To download the latest software release, perform the following:
1. Using the iDirect login name and password, log on to the iDirect TAC Web site (Refer to
Getting Help on page xii).
2. In the By Product section, click Software.
3. Navigate to iDXiDX 3iDX 3.3.3.
4. Click the iDX 3.3.3 Software Package and Documentation Downloads link.
5. Download all applicable software packages.
To download any supplemental software, perform the following:
3. From Software, click Supplemental Releases.
iDirectGov Software Download Instructions

on iDirectGov TAC Web site.
1. Using the iDirectGov login name and password, log on to the iDirectGov TAC Web site
(Refer to Getting Help on page xii).
2. On the left navigation menu, click Software.
3. Navigate to iDX 3.X Releases3.3.3.
To download any supplemental software, perform the following:
2. On the left navigation menu, click Supplemental Releases.
Follow the instructions in the Network Upgrade Procedure Guide for iDX Release 3.0.0.x and
Later to iDX Release 3.3.x.x to install the full iDX Release 3.3.x.x.
90
Release Notes
This section defines tasks that should be performed (or checked) prior to any installation.
Please refer to the Network Upgrade Procedure Guide for iDX Release 3.0.0.x and Later to
iDX Release 3.3.x.x for information about performing an upgrade and for complete
instructions on backing up a system before upgrading to iDX Release 3.3.
DVB-S2 Outbound with TPC Coded Inbound Carriers

Networks that use DVB-S2 outbound carriers with TPC coded inbound carriers must have the
inbound carriers reconfigured to 2D 16-State. Because they do not support 2D 16-State, any
iNFINITI Rx hub line cards must be replaced with Evolution line cards. All iNFINITI-only
remotes and line cards must be replaced. Please refer to the Network Upgrade Procedure
Guide and the Link Budget Analysis Guide.
CAUTION: Do not upgrade to the new release until all upstream carriers in all
DVB-S2 networks have been configured to use 2D 16-State coding and all remotes
in those networks have received their new options files. If you attempt to upgrade
your network with any remotes that have TPC options files, the remote software
will not restart on those remotes and site visits will be required to recover the
remotes.
NMS Service Levels May Exceed Maximum Supported

In iDX Release 3.1, and later, the NMS requires an additional Service Level to support the Idle
and Dormant States feature in Satellite Routers. A maximum of 32 Service Levels are allowed
for each Satellite Router. If the maximum number of Service Levels is already in use by any
Satellite Router in your network, delete at least one service level or combine two or more
service levels in order to proceed with the installation of iDX Release 3.3.
Default NMS Profile Not Correctly Populated after Fresh Install

After performing a fresh installation of iDX 3.3.x.x, the default NMS Service Profile does not
have either the Upstream or Downstream rules correctly populated. A special script must be
run to populate these rules correctly. The details are in the Software Installation Guide for
New Hubs for iDX Release 3.3.
Check Inroute Group Uplink Control Parameters

After upgrading to iDX Release 3.3, verify the Inroute Group Uplink Control Parameters in
iBuilder for all inroute groups. See Known Issues 39681 Fade Slope Margin (M1) Negative After
Upgrade to iDX Release 3.3 on page 80 and 39170 Standby Line Card with Changes Pending
Cannot Complete Automatic Failover on page 80.
Release Notes
91
92
Release Notes
iDX Release 3.3.2.5

Patch Installation
This chapter describes all required procedures to install the iDX Release 3.3.2.5 patch.
If there are any questions regarding the instructions provided in this section, or additional
information is needed, see Getting Help on page xii.
Before performing the installation, refer to the Installation/Upgrade Notes on page 91. Also,
please refer to the Network Upgrade Procedure Guide for iDX Release 3.3.x.x for information
about performing an upgrade and for complete instructions on backing up your system before
upgrading to iDX Release 3.3.2.5.
Software Download
The software packages are available for download on both iDirect and iDirectGov TAC Web
sites. Additional software licenses may be required for software downloads.
iDirect Software Download Instructions

This section provides download instructions for iDX 3.3.2.5 software on iDirect TAC Web site.
3. Navigate to iDXiDX 3iDX 3.3.2.5
4. Click the iDX 3.3.2.5 Software Package and Documentation Downloads link.
Release Notes
93
iDirectGov Software Download Instructions

on iDirectGov TAC Web site.
2. On the left navigation menu, click Software.
3. Navigate to iDX 3.X Releases3.3.2.5.
Installation Instructions iDX Patch Release 3.3.2.5

This section defines the instructions and guidelines for installing the iDX Release 3.3.2.5
software. Please refer to the Network Upgrade Procedure Guide for iDX Release 3.3.x.x for
information about performing an upgrade and for complete instructions on backing up your
system before upgrading to iDX Release 3.3.2.5. See Related Documents on page xiii.
The patch software consists of the following:
iMonitor/iBuilder clients
evtsvr executable file for NMS server
sarouter executable file for PP server
e8 Series remote software package archived file containing:
Evolution e8350 and e850MP BSP package (evo_bsp-15.0.2.5.pkg)
Evolution e8350 and e850MP remote package (evo_e8_rmt-15.0.2.5.pkg)
To install the patch, complete the following tasks:
Replace the existing evtsvr executable file on your NMS server with the new file
Replace the existing sarouter executable file on your PP server with the new file
Replace the existing e8350 and e850mp remote package files on your NMS server with the
new package files
Download the new remote software packages to all remotes in your networks and reset
the remotes
NOTE: Do not use the Revision Server (RevServer) to download the patch
files. RevServer cannot be used for patch downloads.
94
Release Notes
Replace the Evtsvr Executable File on the NMS Server

Before replacing the existing evtsvr executable file on your NMS server, make sure to copy the
new file previously downloaded from the TAC Web site to the /tmp directory of the NMS
server.
Perform the following:
1. Use Putty or similar SSH client to log on to the NMS server as idirect user. Then, switch
to root using the following command:
su 2. Make a backup copy of the existing executable files:
cp /home/nms/evt/evtsvr /home/nms/evt/evtsvr.old
3. Verify the data integrity of the compressed evtsvr file
md5sum /tmp/evtsvr_3325.tgz
The md5checksum value should be 365b4a729b62ec916c34f3268124cafc
4. Extract the compressed evtsvr file
tar -zxvf evtsvr_3325.tgz
5. Rename the new file to evtsvr
mv evtsvr.tls1.2 evtsvr
6. Copy the new evtsvr executable file to the correct directory:
cp /tmp/evtsvr /home/nms/evt/.
7. Update the access permission of the new evtsvr file to become an executable file:
chmod a+x /home/nms/evt/evtsvr
8. Restart the NMS evtsvr service:
service idirect_nms restart evtsvr
9. Verify the version of the new evtsvr as follows:
a. Telnet to the local machine:
telnet localhost 13259
b. At the Username prompt, log in as the admin user.
c. Verify the evtsvr version at the > prompt:
version
Verify the Code Version same as shown below:
Application: XXUnnamedApplicationXX
Code Version: 15.0.2.5
Build Comment: Final_Build
Build Label: IDS-15.0.2.5-Build-13
Release Notes
95
Replace the Sarouter Executable File on the PP Server

Before replacing the existing sarouter executable file on your PP server, make sure to copy
the new file previously downloaded from the TAC Web site to the /tmp directory of the PP
server.
Perform the following:
1. Use Putty or similar SSH client to log on to the PP server as idirect user. Then, switch to
root using the following command:
su 2. Make a backup copy of the existing executable files:
cp /usr/sbin/idirect/sarouter /usr/sbin/idirect/sarouter.old
3. Verify the data integrity of the new evtsvr file
md5sum /tmp/sarouter_3325.tgz
The md5checksum value should be 47768b40065db8eab4ee04293d3fa755
4. Extract the new sarouter executable file in the /tmp directory:
tar -zxvf sarouter_3325.tgz
5. Copy the new sarouter executable file to the correct directory:
cp /tmp/sarouter /usr/sbin/idirect/.
6. Update the access permission of the new sarouter file to become an executable file:
chmod a+x /usr/sbin/idirect/sarouter
7. Restart the PP services:
service idirect_hpb restart
8. Verify the version of the new sarouter as follows:
c. Switch to the sarouter process:
sarouter;
d. Verify the sarmt version at the > prompt:
version
Application: sarouter
96
Release Notes
Backup Old Remote Images and Copy New Remote Images to NMS
Directory
Perform the following to backup existing remote images and copy the new images to NMS
directory:
1. If you have not downloaded the software packages, then please do so using the
appropriate download instructions in section Software Download on page 93.
2. Extract and save the archived file to a temporary directory on your PC.
3. Use WINSCP, as idirect user, to copy the extracted files to the /tmp directory of the NMS
server.
4. Use Putty or similar SSH client to log on to the NMS server as idirect user. Then switch to
su 5. Identify the software version of the existing remote image file:
ls /home/nms/cfg/image_sets/e8_rmt_package
The output should show the image file name similar to the example shown below:
[root@NMS33 ~]# ls /home/nms/cfg/image_sets/e8_rmt_package
e8_rmt-15.0.2.1.pkg
6. Use the software version number to create a backup directory to store the old remote
image file:
mkdir /root/15.0.2.x_OLD
7. Save the old remote image files for e8350 and e850MP remotes to a backup directory:
mv /home/nms/cfg/image_sets/evo_bsp_package/*
/root/15.0.2.x_OLD/.
mv /home/nms/cfg/image_sets/e8_rmt_package/*
NOTE: Replace 15.0.2.x with the actual software version number used in step
3.
8. Copy the new remote image files from the temporary directory to the appropriate NMS
directories:
cp /tmp/evo_bsp-15.0.2.5.pkg
/home/nms/cfg/image_sets/evo_bsp_package/.
cp /tmp/e8_rmt-15.0.2.5.pkg
/home/nms/cfg/image_sets/e8_rmt_package/.
Release Notes
97
Install Patch on Evolution e8350 and e850MP Remotes

For each network with Evolution e8350 and e850MP remotes, perform a BSP package update,
a remote package update, then reset the remotes.
BSP Package Update

Open iBuilder and perform the following steps to download the remote software package to
the remotes.
1. In the iBuilder tree view, right-click the Network icon and select Package
DownloadMulticast.
2. In the Multicast Download dialog box, click the Hardware list and select Evolution 8
Series (for both e8350 and e850MP remotes).
3. In the Version list, select 15.0.2.5 BSP Update.
4. Verify that the Selected Package field displays the following package:
evo_bsp-15.0.2.5
5. Make sure that all corresponding remotes are selected in the Remotes window.
6. Click Start to download the remote image package.
NOTE: Monitor the status window to make sure the message package flash
completed displays before proceeding to the next step.
7. Repeat this procedure for the remotes not selected in Step 2.
Click Close when the download completes.
Remote Package Update

the remotes.
DownloadMulticast.
2. In the Multicast Download dialog box, click the Hardware list and select Evolution 8
Series (for both e8350 and e850MP remotes)
3. In the Version list, select 15.0.2.5.
e8_rmt-15.0.2.5
7. Repeat this procedure for the remote not selected in Step 2.
98
Release Notes
Reset the Remotes

Perform the following steps to reset the remotes:
1. In the iBuilder tree view, right-click on Network and select Apply
ConfigurationsMultiple.
2. In the Remotes area, select all of the remotes that were updated with the patch.
3. Select the following options:
Target: Remote-side Only
Protocol: Push (UDP)
Reset: Reset Only (do not download).
4. Click Start to apply the configuration.
Release Notes
99
100
Release Notes
iDX Release 3.3.2.4

Patch Installation

NOTE: iDX Release 3.3.2.4 consists of a remote software update. To use the iDX
3.3.2.4 remote software, the network is required to be running with either iDX
Release 3.3.2.1 or 3.3.2.2.
This patch is applicable for all iDX 3.3.2.x networks, utilizing the following remotes:
Evolution X3 remote
Evolution X5 remote
Evolution X7 remote
Evolution e8350 remote
Evolution e850mp remote
The patch software consists of two archived files:

1. Sarmt executable file (sarmt.tgz)
2. Remote software package archived file containing:
Release Notes
Evolution X3 BSP package (evo_x3_bsp-15.0.2.4.pkg)
101
Evolution X3 remote package (evo_x3_rmt-15.0.2.4.pkg)
Evolution e8350 and e850MP BSP package (evo_bsp-15.0.2.4.pkg)
Evolution e8350 and e850MP remote package (evo_e8_rmt-15.0.2.4.pkg)
To install the patch, complete the following tasks:
Download the sarmt executable file and transfer to the PP server.
Download the remote software package files and transfer to the NMS server.
Replace the existing sarmt executable file on your PP server with the new file.
Replace the existing package files, for the remotes listed above, on your NMS server with
the new package files.
the remotes.
Download and Copy the SARMT File to the PP Server

To download and transfer the SARMT file to the PP server, perform the following:
1. Browse the TAC Web site (Refer to Getting Help on page xii for TAC Web site
information.)
2. Click SoftwareiDXiDX3iDX 3.3.2.4.
3. Click iDX Release 3.3.2.4 Software Package and Documentation Downloads link.
4. Click SARMT to download the patch file.
Use WINSCP, as idirect user, to copy the extracted files to the /tmp directory of the PP
server.
Download and Copy Remote Software Packages to the NMS

Server
To download and transfer the remote software packages to the NMS server, perform the
following:
information.)
102
Release Notes
4. Click iDX 3.3.2.4 - Remote Package to download the patch file.

server.
Replace the SARMT Executable on the PP Servers

To replace the original sarmt executable with the new file, perform the following:
1. Use Putty or similar SSH client to log on to the PP server as idirect user. Then, switch to
su 2. Make a backup copy of the existing sarmt executable file:
cp /usr/sbin/idirect/sarmt /usr/sbin/idirect/sarmt.old
3. Extract the new sarmt executable file in the /tmp directory:
tar -zxvf sarmt_15024.tgz
4. Copy the new sarmt executable file to the correct directory:
cp /tmp/sarmt /usr/sbin/idirect/.
5. Update the access permission of new sarmt file to become an executable file:
chmod a+x /usr/sbin/idirect/sarmt
6. Restart the PP services:
service idirect_hpb restart
7. Verify the version of the new sarmt as follows:
c. Switch to the sarmt process:
sarmt;
d. Verify the sarmt version at the > prompt:
version
Application: sarmt
Release Notes
103
Directory
directory:
ls /home/nms/cfg/image_sets/evo_x3_rmt_package
[root@NMS33 ~]# ls /home/nms/cfg/image_sets/evo_x3_rmt_package
evo_x3_rmt-15.0.2.1.pkg
image file:
4. Save the old remote image files to the backup directory
For X3 remote:
mv /home/nms/cfg/image_sets/evo_x3_bsp_package/*
mv /home/nms/cfg/image_sets/evo_x3_rmt_package/*
For X5 remote:
mv /home/nms/cfg/image_sets/evo_x5_bsp_package/*
mv /home/nms/cfg/image_sets/evo_x5_rmt_package/*
For X7 remote:
mv /home/nms/cfg/image_sets/evo_x7_package/*
For e8350 and e850MP remotes:
mv /home/nms/cfg/image_sets/evo_bsp_package/*
mv /home/nms/cfg/image_sets/e8_rmt_package/*
3.
104
Release Notes
directories
For X3 remote:
cp /tmp/evo_x3_bsp-15.0.2.4.pkg
/home/nms/cfg/image_sets/evo_x3_bsp_package/.
cp /tmp/evo_x3_rmt-15.0.2.4.pkg
/home/nms/cfg/image_sets/evo_x3_rmt_package/.
For X5 remote:
/home/nms/cfg/image_sets/evo_x5_bsp_package/.
/home/nms/cfg/image_sets/evo_x5_rmt_package/.
For X7 remote:
/home/nms/cfg/image_sets/evo_x7_package/.
For e8350 and e850MP remotes:
cp /tmp/evo_bsp-15.0.2.4.pkg
/home/nms/cfg/image_sets/evo_bsp_package/.
cp /tmp/e8_rmt-15.0.2.4.pkg
/home/nms/cfg/image_sets/e8_rmt_package/.
Install Patch on Evolution X7 Remotes

For each network with Evolution X7 remotes, perform a remote package update and reset the
remotes.

the remotes.
DownloadMulticast.
2. In the Multicast Download dialog box, click the Hardware list and select Evolution X7.
3. For Version, select 15.0.2.4.
evo_x7_rmt-15.0.2.4
Release Notes
105
Reset the Remotes

Install Patch on Evolution X3, X5, e8350 and e850MP Remotes

For each network with Evolution X3, X5, e8350, and e850MP remotes, perform a BSP package
update, a remote package update, then reset the remotes.
BSP Package Update

the remotes.
DownloadMulticast.
2. In the Multicast Download dialog box, click the Hardware list and select one of the
following:
Evolution X3 Remote
Evolution X5 Remote
Evolution 8 Series (for both e8350 and e850MP remotes)

4. Verify that the Selected Package field displays the package one of the following
packages:
evo_x3_bsp-15.0.2.4 (for Evolution X3 remotes)
evo_x5_bsp-15.0.2.4 (for Evolution X5 remotes)
evo_bsp-15.0.2.4 (for Evolution e8350 and e850MP remotes)
106
Release Notes
7. Repeat this procedure for the remotes not selected in Step 2.


the remotes.
DownloadMulticast.
2. In the Multicast Download dialog box, click the Hardware list and select Evolution X5
Remote.
4. Verify that the Selected Package field displays one of the following packages:
evo_x3_rmt-15.0.2.4 (for Evolution X3 remotes)
e8_rmt-15.0.2.4 (for Evolution e8350 and e850MP remotes)
Reset the Remotes

Release Notes
107
108
Release Notes
iDX Release 3.3.2.3

Patch Installation

NOTE: iDX 3.3.2.3 is a remote side patch only. To use the iDX 3.3.2.3 remote
software the network is required to be running with either iDX Release 3.3.2.1 or
3.3.2.2.
This patch is applicable for all iDX 3.3.2.x networks, utilizing the following remotes:
Evolution X1 Series remote (Indoor and Outdoor)
Evolution X5 remote
Evolution X7 remote
The patch is contained in a single download archive file containing:
Evolution X1 Indoor remote package (evo_x1_indoor_rmt-15.0.2.3.pkg)
Evolution X1 Outdoor remote package (evo_x1_outdoor_rmt-15.0.2.3.pkg)
Release Notes
109
To install the patch, do the following:
the remotes.
Download and Copy Software Packages to the NMS Server

Perform the following to download and transfer iDX 3.3.2.3 patch files to NMS Server:
information.)
4. Click iDX 3.3.2.3 - Remote Package to download the patch file.
server.
Directory
directory:
ls /home/nms/cfg/image_sets/evo_x1_indoor_package
[root@NMS33 ~]# ls /home/nms/cfg/image_sets/evo_x1_indoor_package
evo_x1_indoor_rmt-15.0.2.1.pkg
image file:
110
Release Notes
4. Save the old remote image files to the backup directory:

mv /home/nms/cfg/image_sets/evo_x1_indoor_package/*
mv /home/nms/cfg/image_sets/evo_x1_outdoor_package/*
3.
directories:
cp /tmp/evo_x1_indoor_rmt-15.0.2.3.pkg
/home/nms/cfg/image_sets/evo_x1_indoor_package/.
cp /tmp/evo_x1_outdoor_rmt-15.0.2.3.pkg
/home/nms/cfg/image_sets/evo_x1_outdoor_package/.
Install Patch on Evolution X1 (Indoor and Outdoor) and X7

Remotes
For each network with X7 and Evolution X1 Indoor and Outdoor remotes, perform a remote
package update and reset the remotes.

the remotes.
DownloadMulticast.
following:
Evolution X1 Indoor
Evolution X1 Outdoor
Evolution X7
3. For Version, select 15.0.2.3.
Release Notes
111
evo_x1_indoor_rmt-15.0.2.3 (for Evolution X1 Indoor remotes)

evo_x1_outdoor_rmt-15.0.2.3 (for Evolution X1 Outdoor remotes)
Reset the Remotes

Install Patch on Evolution X5 Remotes

For each network with Evolution X5 remotes, perform a BSP package update, a remote
package update, then reset the remotes.
BSP Package Update

the remotes.
DownloadMulticast.
Remote.
4. Verify that the Selected Package field displays the package evo_x5_bsp-15.0.2.3.
112
Release Notes


the remotes.
DownloadMulticast.
Remote.
4. Verify that the Selected Package field displays the package evo_x5_rmt-15.0.2.3.
Reset the Remotes

Release Notes
113
114
Release Notes
iDX Release 3.3.0.2

Patch Installation
This chapter describes how to install the iDX Release 3.3.0.2 patch.

software the network is required to be running iDX 3.3.0.
This patch is applicable for all iDX 3.3.0 networks, utilizing the following remotes:
Evolution E150 remote
Evolution E150 remote package (evo_e150_rmt-15.0.0.2pkg)
Release Notes
115
the remotes.

Download and transfer iDX 3.3.0.2 patch files to NMS Server 1. Download the patch file as follows:
a. Browse the TAC Web site (Refer to Getting Help on page xii for TAC Web site
information.)
b. Click SoftwareiDXiDX3iDX 3.3
c. Click iDX Release 3.3 Software Package and Documentation Downloads link.
d. Click iDX 3.3.0.2 - Remote Package to download the patch file.
e. Extract and save the archived file to a temporary directory on your PC.
server.
Directory
ls /home/nms/cfg/image_sets/evo_x1_indoor_package
[root@NMS33 ~]# ls /home/nms/cfg/image_sets/evo_x1_indoor_package
evo_x1_indoor_rmt-15.0.0.0.pkg
image file:
116
Release Notes
mv /home/nms/cfg/image_sets/evo_e150_package/*
3.
directories:
cp /tmp/evo_e150_rmt-15.0.0.2.pkg
/home/nms/cfg/image_sets/evo_e150_package/.
Install Patch on Evolution E150 and X1 (Indoor and Outdoor)

Remotes
For each network with E150 and Evolution X1 Indoor and Outdoor remotes, perform a remote

the remotes.
DownloadMulticast.
following:
Evolution X1 Indoor
Evolution E150


evo_e150_rmt-15.0.0.2 (for Evolution e150 remotes)
completed displays before proceeding to Step 7.
Release Notes
117
Reset the Remotes

118
Release Notes
iDX Release 3.3.0.1

Patch Installation
This chapter describes how to install the iDX Release 3.3.0.1 patch.

software the network is required to be running iDX 3.3.0.
This patch is applicable for all iDX 3.3.0 networks, utilizing the following remotes:
Evolution E150 remote
Evolution E150 remote package (evo_e150_rmt-15.0.0.1.pkg)
Release Notes
119
the remotes.

Download and transfer iDX 3.3.0.1 patch files to NMS Server 1. Download the patch file as follows:
a. Browse the TAC Web site (Refer to Getting Help on page xii for TAC Web site
information.)
b. Click SoftwareiDXiDX3iDX 3.3
c. Click iDX Release 3.3 Software Package and Documentation Downloads link.
d. Click iDX 3.3.0.1 - Remote Package to download the patch file.
e. Extract and save the archived file to a temporary directory on your PC.
server.
Directory
su 2. Create a backup directory to store the old remote image file:
mkdir /root/15.0.0.0_OLD
/root/15.0.0.0_OLD/.
/root/15.0.0.0_OLD/.
mv /home/nms/cfg/image_sets/evo_e150_package/*
/root/15.0.0.0_OLD/.
directories:
120
Release Notes
cp /tmp/evo_e150_rmt-15.0.0.1.pkg
/home/nms/cfg/image_sets/evo_e150_package/.
Install Patch on Evolution E150 and X1 (Indoor and Outdoor)

Remotes
For each network with E150 and Evolution X1 Indoor and Outdoor remotes, perform a remote

the remotes.
DownloadMulticast.
following:
Evolution X1 Indoor
Evolution E150


evo_e150_rmt-15.0.0.1 (for Evolution e150 remotes)
NOTE: Monitor the status window status to make sure the message package
flash completed displays before proceeding to Step 7.
Reset the Remotes

Release Notes
121
122
Release Notes
iDirect
13861 Sunrise Valley Drive, Suite 300
Herndon, VA 20171-6126
+1 703.648.8000
+1 866.345.0983
www.idirect.net
Advancing a Connected World

IDX 3.3 - Release Notes

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

IDX 3.3 - Release Notes

Încărcat de

Drepturi de autor:

Formate disponibile

Release Notes iDX Releases 3.3.x.

Document Name: RN_iDX_3.3.x.x_Rev_K_112415

Initial Document Release for iDX Release 3.3.2.0.

Update for iDX Release 3.3.2.1.

Update to Bug Fixes chapter.

Update for iDX Release 3.3.2.2.

Update to Important Notices chapter.

Update for iDX Release 3.3.3.1.

Update for iDX Patch Release 3.3.2.3 for Remotes.

Update for iDX Patch Release 3.3.2.4.

Update for iDX Patch Release 3.3.2.5.

Update for iDX Release 3.3.4.0

Technical Reference Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

New Features and Enhancements

Enhancements in iDX Release 3.3.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Supported Features and Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Unsupported TRANSEC for iDX 3.3.3.x Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

42280 X1 Satellite Router Fails to Pass Multicast Upstream Traffic . . . . . . . . . . . . . . . . . 33

41866 MODCOD Distribution Display for X1 Remote Incorrectly Reports Traffic. .

Bugs Fixed in iDX Release 3.3.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Bugs Fixed in iDX Release 3.3.2.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Bugs Fixed in iDX Release 3.3.2.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Bugs Fixed in iDX Release 3.3.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Bugs Fixed in iDX Release 3.3.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

41169 Memory Corruption When Adding Multiple Remotes In The Network . . . . . . . . . . . . 50

Bugs Fixed in iDX Release 3.3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Bug Fixes in iDX Release 3.3.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Bug Fixes in iDX Release 3.3.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Bugs Fixed in iDX Release 3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Known Issues in iDX Release 3.3.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

X7 Ignores Wakeup Service Level Trigger for Layer 2 Traffic . . . . . . . . . . . . . . . . . 68

42296 iBuilder Allows Configuring MCFP Encryption on Both X7 Remote Rx Ports . . . . . . . .

Known Issues in iDX Release 3.3.2.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Known Issues in iDX Release 3.3.2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Known Issues in iDX Release 3.3.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

41777 No Automatic Cleanup for /tmp/build_package Directory . . . . . . . . . . . . . . . . . . 74

Known Issues in iDX Release 3.3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

40069 Data Missing Warning on Remotes in Inclined Orbit Network . . . . . . . . . . . . . . . .

iDX Release 3.3.2.5 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Remote Package Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

iDX Release 3.3.2.4 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation/Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

iDX Release 3.3.2.3 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation/Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

iDX Release 3.3.0.2 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation/Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Installation Instructions iDX Patch Release 3.3.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . 115

iDX Release 3.3.0.1 Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation/Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Contents Of This Guide

New Features and Enhancements

Supported Features and Hardware

iDX Release 3.3.2.5 Patch Installation

iDX Release 3.3.2.4 Patch Installation

iDX Release 3.3.2.3 Patch Installation

iDX Release 3.3.0.2 Patch Installation

iDX Release 3.3.0.1 Patch Installation

Used when the user is required to

Enter the command:

Used when showing resulting

crc report all

Used when referring to text that

1. To add a remote to an inroute group, right-click

Used when specifying names of