Professional Documents
Culture Documents
Release Notes
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
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.
Release Notes ix
iDX Releases 3.3.x.x
Revision History
x Release Notes
iDX Releases 3.3.x.x
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
iv Release Notes
iDX Releases 3.3.x.x
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
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 v
iDX Releases 3.3.x.x
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
iDX Releases 3.3.x.x
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
Bugs Fixed in iDX Release 3.3.2.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
Bugs Fixed in iDX Release 3.3.2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
Bugs Fixed in iDX Release 3.3.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
Bugs Fixed in iDX Release 3.3.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
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 . . . . 50
40802 A Few Hundred Upstream TCP Sessions Cause X1 Modem to Reset . . . . . . . . . . . . . 51
40800 iMonitor Bandwidth Legend Mismatch for Downstream QoS Stats . . . . . . . . . . . . . . 51
40791 GPS Input Validation Feature Prevents Remotes from Obtaining LATLONG from an ACU 51
40772 X1 Remote Unable to Establish Link Layer After Power Cycle . . . . . . . . . . . . . . . . 51
Release Notes ix
iDX Releases 3.3.x.x
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 Anti-
Meridian 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
Bugs Fixed in iDX Release 3.3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
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
x Release Notes
iDX Releases 3.3.x.x
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
iDX Releases 3.3.x.x
Contents
EVOFT-442 (42088) Queue Depth Value Incorrectly Sets As 250ms When Reliable Option is Enabled
in the Service Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Known Issues in iDX Release 3.3.2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
42411 Cross Polarization Start and Stop Buttons Not Fully Functional on X1 Web iSite . . . . . 72
40320 Remote Fails to Rejoin the Original IG After It Has Been Moved to a Different IG . . . . 72
31376 Duplicate Packets Observe on X7 LAN Interface . . . . . . . . . . . . . . . . . . . . . . . . 72
Known Issues in iDX Release 3.3.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
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
42279 odu_tx_10_mhz Value Is Incorrectly Enabled for Line Card Configured as Tx Warm Standby
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
Known Issues in iDX Release 3.3.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . ....... 77
41373 Layer 3 X1 Remote Passes Tagged Packets Upstream in Untagged Mode . . . ....... 77
41329 iBuilder May Crash or Hang with 12 or More Open Control Panels . . . . . . . ....... 77
41274 Upstream Network Subnet Mask Filter Rule for X1 Remote Does Not Work . ....... 77
41095 PP Sends Traffic to Absent Remote Side Local LAN Device . . . . . . . . . . . ....... 77
38986 iBuilder Does Not Enforce Limit of 32 Carriers for Inroute Groups . . . . . . ....... 77
34713 Rx Hub Line Card Digital AGC Transient Effects During MODCOD Switchover ....... 78
Known Issues in iDX Release 3.3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
41153 Falcon-Based Remote Priority Service Level Loading Issue . . . . . . . . . . . . . . . . . . 78
Known Issues in iDX Release 3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Data Path Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
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 . . . . . . . . . . . . . . . . . 79
39974 Upstream CRC Errors When Using High-Speed Comms On The Move . . . . . . . . . . . . 79
39971 Single Channel TDMA Line Card Must Be Reset After Carrier Changes . . . . . . . . . . . 80
39681 Fade Slope Margin (M1) Negative After Upgrade to iDX Release 3.3 . . . . . . . . . . . . 80
39170 Standby Line Card with Changes Pending Cannot Complete Automatic Failover . . . . . 80
38751 SCPC Remotes Cannot Acquire After Change to Initial Power . . . . . . . . . . . . . . . . 81
38634 Remotes on Low C/N0 Upstream Carriers May Not Receive Correct Slot Allocation
When CIR Is Oversubscribed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
38633, 37866 Remotes on Upstream Carriers with Low C/N0 May Not Receive Correct
Cost-Based Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
38572 Remotes on SCPC Return Channels with Spreading Factor 4 or 8 and Block Size
438 Bytes May Not Join the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
38463 Multicast Encryption Enabled without Link Encryption License Causes Remotes to
Drop out of Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
38002 Over Correction in Frequency Offset Occurred When COTM Was Set to Avionics
and Two or More Remotes Were Added . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
36021 All Protocol Processor Processes Down After Cycling Power on Upstream and Tunnel
Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
28422 Adding Incomplete Line Card to Inroute Group Can Cause Network Outage . . . . . . . . 82
27082 Remote May Switch to Beam Even if Satellite is Below Minimum Look Angle . . . . . . . 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
38672 iBuilder: Disabling FLLDacErrors Warning Type Causes Receive Line Card Carrier to
Be Unassigned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
38530 iMonitor: False Warning for Erroneous Report of CRC8 and CRC32 Errors on Acquisition 87
38493 iMonitor Probe Warning: Modulated Carrier Interferes With Existing 5% ROF Carrier . . 87
38437 Using Console Commands to Change Tx Frequency Disables RF Energy. . . . . . . . . . . 87
38251 iBuilder Falsely Reports Failed to Assign Standby Error Message after Successfully
Assigning Standby Line Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
37042 iMonitor Shows Tx Bytes and Attempts = 0 in Tx Line Card Stats . . . . . . . . . . . . . . 87
36113 Remote Warning Remains in Active Condition When Remote is De-activated . . . . . . . 88
35904 SNMP Returns Invalid Result For Out-of-Network Remotes . . . . . . . . . . . . . . . . . . 88
35621 X1 Satellite Router Transmit LED is Green when Transmit is Disabled . . . . . . . . . . . 88
34442 DSCP Marking Not Working as Expected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
34396 iMonitorSAT Traffic Graph Not Appearing Correctly with Respect to X-Axis . . . . . . . 88
26749 iBuilderChanges to VLAN Subnet and Gateway at PP Blade Not Shown . . . . . . . . . . 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
Release Notes xv
iDX Releases 3.3.x.x
Contents
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.
Release Notes xi
iDX Releases 3.3.x.x
About
This section illustrates and describes the conventions used throughout this document.
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:
Telephone: (703) 648-8151
E-mail: tac@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
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.
Release Notes xv
iDX Releases 3.3.x.x
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.
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.
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.
NOTE: In iDX Release 3.2.3, and future releases, the SCAP User Guide replaces
the STIG User Guide.
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
Release Notes 1
iDX Releases 3.3.x.x
New Features in iDX 3.3.3.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: 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.
2 Release Notes
iDX Releases 3.3.x.x
NMS Scalability Improvements in iDX 3.3.2.2
RAMDISK Addition
A RAMDISK has been added to improve memory availability and scalability for the NMS Config
server.
Release Notes 3
iDX Releases 3.3.x.x
New Features in iDX Release 3.3.2.1
3. Restart PC.
4 Release Notes
iDX Releases 3.3.x.x
Enhancements 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.
Release Notes 5
iDX Releases 3.3.x.x
Enhancements in iDX Release 3.3.2.1
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.
6 Release Notes
iDX Releases 3.3.x.x
New Features in iDX Release 3.3
Release Notes 7
iDX Releases 3.3.x.x
New Features in iDX Release 3.3
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.
8 Release Notes
iDX Releases 3.3.x.x
New Features in iDX Release 3.3
Release Notes 9
iDX Releases 3.3.x.x
New Features in iDX Release 3.3
10 Release Notes
iDX Releases 3.3.x.x
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.
Release Notes 11
iDX Releases 3.3.x.x
Supported Upgrade Paths
12 Release Notes
iDX Releases 3.3.x.x
Features No Longer Supported
Supported Hardware
This section describes iDirect hardware supported by iDX Release 3.3, including server support
for NMS and Protocol Processor servers.
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
Release Notes 13
iDX Releases 3.3.x.x
Supported Hardware
14 Release Notes
iDX Releases 3.3.x.x
Supported System Interfaces
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
iDX Releases 3.3.x.x
Supported System Interfaces
16 Release Notes
iDX Releases 3.3.x.x
Important Notices
This chapter covers important information that should be reviewed prior to installing the
software for iDX Release 3.3.
Release Notes 17
iDX Releases 3.3.x.x
Remote Survey Package Not Compatible with Network Upgrades From iDX Release 3.3.2.1
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.
18 Release Notes
iDX Releases 3.3.x.x
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.
Release Notes 19
iDX Releases 3.3.x.x
Remotes Drop Out of Network If M1 Is Higher than 2.3 dB Running 8PSK 6/7
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:
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.
20 Release Notes
iDX Releases 3.3.x.x
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
iDX Releases 3.3.x.x
Reconfiguration of Initial/Maximum Powers for Some Evolution e8350 and e800 Remotes
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 re-
acquire 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.
NOTE: A remote may not lock to the downstream carrier if the upgrade
failed. This procedure assumes that the remote was upgraded successfully.
22 Release Notes
iDX Releases 3.3.x.x
Reconfiguration of Initial/Maximum Powers for Some Evolution e8350 and e800 Remotes
6. In the Remote Power section of the Probe, click Change to open the Change Remote Tx
Power dialog box (Figure 1).
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
iDX Releases 3.3.x.x
Reconfiguration of Initial/Maximum Powers for Some Evolution e8350 and e800 Remotes
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.
24 Release Notes
iDX Releases 3.3.x.x
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 Hub-
Side (TCP).
14. Verify that the remote re-acquires the network.
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
iDX Releases 3.3.x.x
Minimum Tx Gain Must Be Adjusted for Some Beam Maps
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
iDX Releases 3.3.x.x
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
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.
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.
Release Notes 27
iDX Releases 3.3.x.x
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.
CAUTION: Do not configure GKD and Replication using the -b option in the same
server.
28 Release Notes
iDX Releases 3.3.x.x
Power Requirements for Multichannel Line Card
Release Notes 29
iDX Releases 3.3.x.x
TRANSEC Networks Require SHA2 Key Exchange for Remote and Line Card Connections
30 Release Notes
iDX Releases 3.3.x.x
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.
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.
Fixed in this release.
Release Notes 31
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.4
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
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
32 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.4
Release Notes 33
iDX Releases 3.3.x.x
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.
Fixed in this release.
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."
Fixed in this release.
34 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.3.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
Release Notes 35
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.3.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
36 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.3.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
Release Notes 37
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.3.1
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.
Fixed in this release.
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.
Fixed in this release.
38 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.5
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.
Fixed in this release.
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.
Fixed in this release.
Release Notes 39
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.3
frequency and intensity of the spurious spikes are depended on the frequency used
and the calibration of each remote.
Fixed in this release.
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
Fixed in this release.
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
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.2
cross_pol_test_timeout=XXX
Fixed in this release.
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.
Fixed in this release.
Release Notes 41
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.2
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
42 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
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
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
44 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
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.
Fixed in this release.
Release Notes 45
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
NOTE: This issue only affects the XLC-10 line card; no other line cards are
affected.
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.
Fixed in this release.
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.
Fixed in this release.
46 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
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
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
48 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
Release Notes 49
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
50 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
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.
Fixed in this release.
Release Notes 51
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
remote also issued "ASSERTION: EMPTY EMPTY" and "Invalid Package Format"
messages.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
52 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
Release Notes 53
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
54 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.1
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
Release Notes 55
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.0
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.
56 Release Notes
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.0
Release Notes 57
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3.2.0
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
58 Release Notes
iDX Releases 3.3.x.x
Bug Fixes in iDX Release 3.3.0.2
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 non-
spread carriers, since the X1 does not support Spread Spectrum.
Release Notes 59
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3
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.
Fixed in this release.
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.
Fixed in this release.
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.
Fixed in this release.
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
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3
Release Notes 61
iDX Releases 3.3.x.x
Bugs Fixed in iDX Release 3.3
62 Release Notes
iDX Releases 3.3.x.x
Known Issues
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.
Release Notes 63
iDX Releases 3.3.x.x
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.
64 Release Notes
iDX Releases 3.3.x.x
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.
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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.3.1
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.
Work-around: Proceed as follows:
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.
42410 Remote Fails to Rejoin the Original IG After It Has Been Moved to a
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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.3.1
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.
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.
Release Notes 67
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.3.1
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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.3.1
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.
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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.3.1
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.
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.
70 Release Notes
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.3.1
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.
Release Notes 71
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.2.5
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.
40320 Remote Fails to Rejoin the Original IG After It Has Been Moved to a
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.
72 Release Notes
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.2.2
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.
Release Notes 73
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.2.1
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.
74 Release Notes
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.2.1
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).
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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.2.1
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.
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.
76 Release Notes
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.2.1
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.
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.
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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3.2.0
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.
78 Release Notes
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3
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.
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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3
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
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
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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3
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:
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.
Release Notes 81
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3
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.
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-the-
Move (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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3
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.
Release Notes 83
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3
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.
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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3
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.
Release Notes 85
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3
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.
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
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3
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.
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.
Release Notes 87
iDX Releases 3.3.x.x
Known Issues in iDX Release 3.3
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.
88 Release Notes
iDX Releases 3.3.x.x
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.
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.
Release Notes 89
iDX Releases 3.3.x.x
Downloading Required Files for iDX Release 3.3.x.x
90 Release Notes
iDX Releases 3.3.x.x
Installation/Upgrade Notes
Installation/Upgrade 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.
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.
Release Notes 91
iDX Releases 3.3.x.x
Installation/Upgrade Notes
92 Release Notes
iDX Releases 3.3.x.x
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.
Installation/Upgrade Notes
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.
Release Notes 93
iDX Releases 3.3.x.x
iDX Release 3.3.2.5 Patch Installation
NOTE: Do not use the Revision Server (RevServer) to download the patch
files. RevServer cannot be used for patch downloads.
94 Release Notes
iDX Releases 3.3.x.x
iDX Release 3.3.2.5 Patch Installation
Release Notes 95
iDX Releases 3.3.x.x
iDX Release 3.3.2.5 Patch Installation
96 Release Notes
iDX Releases 3.3.x.x
iDX Release 3.3.2.5 Patch Installation
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
root using the following command:
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/*
/root/15.0.2.x_OLD/.
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
iDX Releases 3.3.x.x
iDX Release 3.3.2.5 Patch Installation
NOTE: Monitor the status window to make sure the message package flash
completed displays before proceeding to the next step.
NOTE: Monitor the status window to make sure the message package flash
completed displays before proceeding to the next step.
98 Release Notes
iDX Releases 3.3.x.x
iDX Release 3.3.2.5 Patch Installation
Release Notes 99
iDX Releases 3.3.x.x
iDX Release 3.3.2.5 Patch Installation
This chapter describes all required procedures to install the iDX Release 3.3.2.4 patch.
If there are any questions regarding the instructions provided in this section, or additional
information is needed, see Getting Help on page xii.
Installation/Upgrade Notes
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.4.
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:
Evolution X3 BSP package (evo_x3_bsp-15.0.2.4.pkg)
NOTE: Do not use the Revision Server (RevServer) to download the patch
files. RevServer cannot be used for patch downloads.
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. 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. Identify the software version of the existing remote image file:
ls /home/nms/cfg/image_sets/evo_x3_rmt_package
The output should show the image file name similar to the example shown below:
[root@NMS33 ~]# ls /home/nms/cfg/image_sets/evo_x3_rmt_package
evo_x3_rmt-15.0.2.1.pkg
3. Use the software version number to create a backup directory to store the old remote
image file:
mkdir /root/15.0.2.x_OLD
4. Save the old remote image files to the backup directory
For X3 remote:
mv /home/nms/cfg/image_sets/evo_x3_bsp_package/*
/root/15.0.2.x_OLD/.
mv /home/nms/cfg/image_sets/evo_x3_rmt_package/*
/root/15.0.2.x_OLD/.
For X5 remote:
mv /home/nms/cfg/image_sets/evo_x5_bsp_package/*
/root/15.0.2.x_OLD/.
mv /home/nms/cfg/image_sets/evo_x5_rmt_package/*
/root/15.0.2.x_OLD/.
For X7 remote:
mv /home/nms/cfg/image_sets/evo_x7_package/*
/root/15.0.2.x_OLD/.
For e8350 and e850MP remotes:
mv /home/nms/cfg/image_sets/evo_bsp_package/*
/root/15.0.2.x_OLD/.
mv /home/nms/cfg/image_sets/e8_rmt_package/*
/root/15.0.2.x_OLD/.
NOTE: Replace 15.0.2.x with the actual software version number used in step
3.
5. Copy the new remote image files from the temporary directory to the appropriate NMS
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:
cp /tmp/evo_x5_bsp-15.0.2.4.pkg
/home/nms/cfg/image_sets/evo_x5_bsp_package/.
cp /tmp/evo_x5_rmt-15.0.2.4.pkg
/home/nms/cfg/image_sets/evo_x5_rmt_package/.
For X7 remote:
cp /tmp/evo_x7_rmt-15.0.2.4.pkg
/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/.
NOTE: Monitor the status window to make sure the message package flash
completed displays before proceeding to the next step.
NOTE: Monitor the status window to make sure the message package flash
completed displays before proceeding to the next step.
NOTE: Monitor the status window to make sure the message package flash
completed displays before proceeding to the next step.
This chapter describes all required procedures to install the iDX Release 3.3.2.3 patch.
If there are any questions regarding the instructions provided in this section, or additional
information is needed, see Getting Help on page xii.
Installation/Upgrade Notes
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.3.
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)
Evolution X5 BSP package (evo_x5_bsp-15.0.2.3.pkg)
Evolution X5 remote package (evo_x5_rmt-15.0.2.3.pkg)
Evolution X7 remote package (evo_x7_rmt-15.0.2.3.pkg)
NOTE: Do not use the Revision Server (RevServer) to download the patch
files. RevServer cannot be used for patch downloads.
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. 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. Identify the software version of the existing remote image file:
ls /home/nms/cfg/image_sets/evo_x1_indoor_package
The output should show the image file name similar to the example shown below:
[root@NMS33 ~]# ls /home/nms/cfg/image_sets/evo_x1_indoor_package
evo_x1_indoor_rmt-15.0.2.1.pkg
3. Use the software version number to create a backup directory to store the old remote
image file:
mkdir /root/15.0.2.x_OLD
NOTE: Replace 15.0.2.x with the actual software version number used in step
3.
5. Copy the new remote image files from the temporary directory to the appropriate NMS
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/.
cp /tmp/evo_x5_bsp-15.0.2.3.pkg
/home/nms/cfg/image_sets/evo_x5_package/.
cp /tmp/evo_x5_rmt-15.0.2.3.pkg
/home/nms/cfg/image_sets/evo_x5_package/.
cp /tmp/evo_x7_rmt-15.0.2.3.pkg
/home/nms/cfg/image_sets/evo_x7_package/.
4. Verify that the Selected Package field displays one of the following packages:
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)
evo_x7_rmt-15.0.2.3 (for Evolution X7 remotes)
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.
NOTE: Monitor the status window to make sure the message package flash
completed displays before proceeding to the next step.
NOTE: Monitor the status window to make sure the message package flash
completed displays before proceeding to the next step.
This chapter describes how to install the iDX Release 3.3.0.2 patch.
If there are any questions regarding the instructions provided in this section, or additional
information is needed, see Getting Help on page xii.
Installation/Upgrade Notes
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.0.2.
NOTE: iDX 3.3.0.2 is a remote side patch only. To use the iDX 3.3.0.2 remote
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 X1 Series remote (Indoor and Outdoor)
Evolution E150 remote
The patch is contained in a single download archive file containing:
Evolution X1 Indoor remote package (evo_x1_indoor_rmt-15.0.0.2.pkg)
Evolution X1 Outdoor remote package (evo_x1_outdoor_rmt-15.0.0.2.pkg)
Evolution E150 remote package (evo_e150_rmt-15.0.0.2pkg)
To install the patch, do the following:
Replace the existing package files, for the remotes listed above, 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.
Backup Old Remote Images and Copy New Remote Images to NMS
Directory
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. Identify the software version of the existing remote image file:
ls /home/nms/cfg/image_sets/evo_x1_indoor_package
The output should show the image file name similar to the example shown below:
[root@NMS33 ~]# ls /home/nms/cfg/image_sets/evo_x1_indoor_package
evo_x1_indoor_rmt-15.0.0.0.pkg
3. Use the software version number to create a backup directory to store the old remote
image file:
mkdir /root/15.0.0.x_OLD
4. Save the old remote image files to the backup directory:
mv /home/nms/cfg/image_sets/evo_x1_indoor_package/*
/root/15.0.0.x_OLD/.
mv /home/nms/cfg/image_sets/evo_x1_outdoor_package/*
/root/15.0.0.x_OLD/.
mv /home/nms/cfg/image_sets/evo_e150_package/*
/root/15.0.0.x_OLD/.
NOTE: Replace 15.0.0.x with the actual software version number used in step
3.
5. Copy the new remote image files from the temporary directory to the appropriate NMS
directories:
cp /tmp/evo_x1_indoor_rmt-15.0.0.2.pkg
/home/nms/cfg/image_sets/evo_x1_indoor_package/.
cp /tmp/evo_x1_outdoor_rmt-15.0.0.2.pkg
/home/nms/cfg/image_sets/evo_x1_outdoor_package/.
cp /tmp/evo_e150_rmt-15.0.0.2.pkg
/home/nms/cfg/image_sets/evo_e150_package/.
NOTE: Monitor the status window to make sure the message package flash
completed displays before proceeding to Step 7.
This chapter describes how to install the iDX Release 3.3.0.1 patch.
If there are any questions regarding the instructions provided in this section, or additional
information is needed, see Getting Help on page xii.
Installation/Upgrade Notes
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.0.1.
NOTE: iDX 3.3.0.1 is a remote side patch only. To use the iDX 3.3.0.1 remote
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 X1 Series remote (Indoor and Outdoor)
Evolution E150 remote
The patch is contained in a single download archive file containing:
Evolution X1 Indoor remote package (evo_x1_indoor_rmt-15.0.0.1.pkg)
Evolution X1 Outdoor remote package (evo_x1_outdoor_rmt-15.0.0.1.pkg)
Evolution E150 remote package (evo_e150_rmt-15.0.0.1.pkg)
To install the patch, do the following:
Replace the existing package files, for the remotes listed above, 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.
Backup Old Remote Images and Copy New Remote Images to NMS
Directory
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. Create a backup directory to store the old remote image file:
mkdir /root/15.0.0.0_OLD
3. Save the old remote image files to the backup directory:
mv /home/nms/cfg/image_sets/evo_x1_indoor_package/*
/root/15.0.0.0_OLD/.
mv /home/nms/cfg/image_sets/evo_x1_outdoor_package/*
/root/15.0.0.0_OLD/.
mv /home/nms/cfg/image_sets/evo_e150_package/*
/root/15.0.0.0_OLD/.
4. Copy the new remote image files from the temporary directory to the appropriate NMS
directories:
cp /tmp/evo_x1_indoor_rmt-15.0.0.1.pkg
/home/nms/cfg/image_sets/evo_x1_indoor_package/.
cp /tmp/evo_x1_outdoor_rmt-15.0.0.1.pkg
/home/nms/cfg/image_sets/evo_x1_outdoor_package/.
cp /tmp/evo_e150_rmt-15.0.0.1.pkg
/home/nms/cfg/image_sets/evo_e150_package/.
NOTE: Monitor the status window status to make sure the message package
flash completed displays before proceeding to Step 7.