NUP iDX35xx To iDX41 Non TRANSEC T0000954 RevF 07262018

Network Upgrade Procedure
iDX 3.5.x.x to iDX Releases 4.1.x.x

for Non-TRANSEC Networks
July 26, 2018

Copyright © 2018, Inc. All rights reserved. Reproduction in whole or in part without permission is prohibited.
Information contained herein is subject to change without notice. The specifications and information regarding the
products in this document are subject to change without notice. All statements, information and recommendations
in this document are believed to be accurate, but are presented without warranty of any kind, express, or implied.
Users must take full responsibility for their application of any products. Trademarks, brand names and products
mentioned in this document are the property of their respective owners. All such references are used strictly in an
editorial fashion with no intent to convey any affiliation with the name or the product's rightful owner.
iDirect, a subsidiary of VT Systems, is a global leader in IP-based satellite communications providing technology that
enables our partners to optimize their networks, differentiate and expand their businesses. The iDirect Intelligent
Platform™ allows our partners to run their entire business operations more efficiently via a single, unified IP-based
satellite architecture, whether it's providing core IP applications to the enterprise or specialized services to any
number of diverse vertical markets. iDirect is the #1 name in global satellite communications in key industries
including maritime, military/government, and oil and gas.
iDirect
Company web site: http://www.idirect.net ~ Main Phone: 703.648.8000
TAC Contact Information: Phone: 703.648.8151 ~ Email: [email protected] ~ Web site: http://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: [email protected] ~ Web site: http://tac.idirectgov.com
Document Name: NUP_iDX35xx_To_iDX41_Non_TRANSEC_T0000954_RevF_07262018.pdf

Document Part Number: T0000954
ii Network Upgrade Procedure Guide for iDX Release 3.5 and Later to
iDX Release 4.1 For Non-TRANSEC Networks
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 xiii for TAC access
information.
Revision Date Updates

A 28-Nov-2017 Initial release of document.
B 09-Feb-2018 Added procedures to support TLS 1.0 backward compatibility during
the network upgrade.
C 28-Feb-2018 Added iGateway upgrade procedures to Chapter 7, Upgrade
iGateway and PP Blades.
Added additional steps to include new environment variable in the
nms_start file to prevent an issue with iBuilder client not able to
connect to the NMS server after the upgrade.
D 30-Apr-2018 Reorganized Chapter 7, Upgrade iGateway and PP Blades, to three
separate sections:
• Upgrading Protocol Processor Blades on page 46
• Upgrading iGateway Server on page 48
• Finalizing Network Upgrade on page 50
E 30-June-2018 Added a new procedure, Update ULC/DLC Image, to Chapter 6,
Upgrade Hub Line Cards.
Updated Chapter 7, Upgrade iGateway and PP Blades, to include
procedures for updating an iGateway server running in a DVB-S2
network.
F 26-July-2018 Added R630 Server PP (DVB-S2X) Installation on page 79 for
iGateway installation instructions on a Dell R630 server.
Network Upgrade Procedure Guide for iDX Release 3.5 and Later to iii
Revision History
iv Network Upgrade Procedure Guide for iDX Release 3.5 and Later to
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Supported Upgrade Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
iDirect Contact Information: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
iDirectGov Contact Information: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
iDirect software download instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
1 Read This First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Upgrade Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Upgrade Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Upgrade Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
2.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3.1 Administrative Requirements and Licensing . . . . . . . . . . . . . . . . . . . . . . . . . 9
Network Upgrade Procedure Guide for iDX Release 3.5 and Later to v
Contents
2.3.2 Technical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.3.3 Multicast Download Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.4 Pre-Upgrade Data Capture Recommendations . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.1 Network Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.2 Chassis Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.3 Remote Disk Space Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4.4 Remote Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Pre-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Procedure 1 Check Line Cards and Remotes for Custom Keys. . . . . . . . . . . . . 14
Procedure 2 Check Network for Reserved Multicast Address . . . . . . . . . . . . . 15
Procedure 3 Remove Old Entries in NRD_ARCHIVE Database . . . . . . . . . . . . . 15
Procedure 4 Disable the NMS Database Replication Service . . . . . . . . . . . . . . 15
Procedure 5 Download the Latest iDX 4.1.x.x Images . . . . . . . . . . . . . . . . . . 16
Procedure 6 Preserve the SNMP Configurations . . . . . . . . . . . . . . . . . . . . . . 17
Procedure 7 Preserve the CM Configuration File . . . . . . . . . . . . . . . . . . . . . 17
Procedure 8 Preserve the NMS Initialization File . . . . . . . . . . . . . . . . . . . . . 18
Procedure 9 Modify the CRONTAB File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Procedure 10 Check the NMS Databases for Errors . . . . . . . . . . . . . . . . . . . . 19
Procedure 11 Backup NMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 Upgrading NMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Procedure 1 Perform the NMS Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Procedure 2 Restore the SNMP Configurations . . . . . . . . . . . . . . . . . . . . . . . 25
Procedure 3 Restore the CM Configuration File . . . . . . . . . . . . . . . . . . . . . . 26
Procedure 4 Restore the NMS Initialization File . . . . . . . . . . . . . . . . . . . . . . 26
Procedure 5 Update MySQL Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Procedure 6 Restore the NMS Database and Configurations . . . . . . . . . . . . . . 28
Procedure 7 Revert NMS to TLS 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Procedure 8 Apply NMS License and Run Service Upgrade . . . . . . . . . . . . . . . 29
Procedure 9 Install NMS Client Software (iBuilder/iMonitor). . . . . . . . . . . . . . 29
Procedure 10 Upgrade a Distributed NMS (optional) . . . . . . . . . . . . . . . . . . . 30
5 Upgrade Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Procedure 1 Download the BSP Package . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Procedure 2 Configure Ports Tab on iQDesktop Remotes . . . . . . . . . . . . . . . . 34
Procedure 3 Download Image Packages and Options Files . . . . . . . . . . . . . . . 34
Procedure 4 Reset The Remotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
vi Network Upgrade Procedure Guide for iDX Release 3.5 and Later to
Contents
6 Upgrade Hub Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Update ULC/DLC Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Procedure 1 Download BSP Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Procedure 2 Download Image Package and Options File . . . . . . . . . . . . . . . . 42
Procedure 3 Reset the Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7 Upgrade iGateway and PP Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Upgrading Protocol Processor Blades . . . . . . . . . ... ... ... ... ... ... .... . . 46
Procedure 1 Perform the PP Blade Upgrade. ... ... ... ... ... ... .... . . 46
Procedure 2 Restore the PP Configurations . ... ... ... ... ... ... .... . . 47
Procedure 3 Start PP Services . . . . . . . . . . ... ... ... ... ... ... .... . . 47
Upgrading iGateway in a DVB-S2X Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Procedure 1 Perform the iGateway Upgrade . . . . . . . . . . . . . . . . . . . . . . . . 48
Procedure 2 Verify iGW Software Version After Upgrade . . . . . . . . . . . . . . . . 49
Upgrading iGateway in a DVB-S2 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Procedure 1 Perform the iGateway Upgrade . . . . . . . . . . . . . . . . . . . . . . . . 50
Completing the Network Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Procedure 1 Remove the TLS 1.0 Support From NMS . . . . . . . . . . . . . . . . . . 51
Procedure 2 Restart Remaining Services on NMS Server . . . . . . . . . . . . . . . . 51
Procedure 3 Apply Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Procedure 4 Verify the Uplink Control Parameters . . . . . . . . . . . . . . . . . . . . 53
Procedure 5 Rebalance Protocol Processor Blades . . . . . . . . . . . . . . . . . . . . 53
Procedure 6 Restart Transmit Hub Line Cards (Optional) . . . . . . . . . . . . . . . . 54
8 Required Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Procedure 1 Upgrade the Backup NMS Server . . . . . . . . . . . . . . . . . . . . . . . 58
Procedure 2 Verify the Upgrade has Completed Successfully . . . . . . . . . . . . . 58
Procedure 3 Verify Changes Pending on the Remotes and Incomplete Line Cards af-
ter the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Procedure 4 Verify Chassis Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . 59
Procedure 5 Reconfigure the Crontab File on the NMS Servers. . . . . . . . . . . . 59
Procedure 6 Rebuild NMS Database Replication (if applicable) . . . . . . . . . . . . 61
Procedure 7 Verify the Backup is in Working Condition . . . . . . . . . . . . . . . . . 61
Procedure 8 Verify iDirect SNMP Configuration Working Settings (if applicable) 63
Procedure 9 Determine If Any Remotes Still Out-of-Network . . . . . . . . . . . . . 63
Procedure 10 Software Upgrade/Install for X7 and 9-Series Remotes Second Parti-
tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Procedure 11 Remove the ISO Image From the /tmp Folder (Optional) . . . . . . 64
Network Upgrade Procedure Guide for iDX Release 3.5 and Later to vii
Contents
Appendix A SatManage Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Procedure 1 Disabling NMS Polling on SatManage Server . . . . . . . . . . . . . . . . 65
Procedure 2 Enabling NMS Polling on SatManage Server . . . . . . . . . . . . . . . . 67
Procedure 3 Removing Latency Restriction on NMS Server . . . . . . . . . . . . . . 68
Appendix B R630 V-Server NMS and PP Upgrade . . . . . . . . . . . . . . . . . . 71

B.1 Pre-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
B.1.1 Installing MobaXterm Client for Remote Access . . . . . . . . . . . . . . . . . . . . . . 71
B.2 NMS Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
B.3 PP Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Procedure 1 PP Installation Using an ISO . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Procedure 2 Updating Passwords on the Guest OS . . . . . . . . . . . . . . . . . . . . 72
Procedure 3 Updating PP Network Interface on the Guest OS. . . . . . . . . . . . . 73
Procedure 4 Restore the PP Configurations . . . . . . . . . . . . . . . . . . . . . . . . . 75
Procedure 5 Setting the Date and Time on the PP Blades . . . . . . . . . . . . . . . 76
Procedure 6 Changing MTU Size on the PP for L2oS . . . . . . . . . . . . . . . . . . . 76
Procedure 7 Setting Up the DNS Server on the Guest (Optional) . . . . . . . . . . . 77
B.4 Applying PP Performance Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Appendix C R630 Server . . . . . . . . . . . . PP (DVB-S2X) Installation79

C.1 Installing PP (DVB-S2X). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
viii Network Upgrade Procedure Guide for iDX Release 3.5 and Later to
Figures
Figure 1-1. Upgrade Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Figure 2-1. Multicast Download Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Figure 5-1. Multicast Download — Downloading the Cumulative Update . . . . . . . . . . . . . . . 33
Figure 5-2. Multicast Download Window — Selecting Remote Package . . . . . . . . . . . . . . . . 35
Figure 5-3. Automated Configuration Downloader Window — UDP with Reset Option . . . . . . 37
Figure 6-1. TCP Download Window — Selecting BSP Updates for Hub Line Cards . . . . . . . . . 41
Figure 6-2. TCP Download Window — Download Packages to Line Cards . . . . . . . . . . . . . . . 42
Figure 6-3. Automated Configuration Downloader Window — TCP with Reset Option . . . . . . 43
Figure 7-1. Automated Configuration Downloader Window — Remote Hub-side Configurations 52
Figure 7-2. Inroute Group — Uplink Control Configuration Parameters . . . . . . . . . . . . . . . . 53
Figure A-1. SatManage Database Login Screen using Navicat . . . . . . . . . . . . . . . . . . . . . . 65
Figure A-2. SatManage Database — IDIRECT_NMS Table . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure A-3. SatManage Database — Disabling NMS polling. . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure A-4. SatManage Database — Enabling NMS polling . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure B-1. ifcfg-eth0 File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure B-2. ifcfg-eth1 File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure C-1. Changing the BIOS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure C-2. Changing the Boot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure C-3. Status of the Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
ix Network Upgrade Procedure Guide for iDX Release 3.5 and Later to
Tables
Table 1-1. Network Upgrade Checklist..................................................................... 3

Table 3-1. iDX to iDS Version Number Conversion ...................................................... 16
Table 5-1. Cumulative Update and Remote Upgrade Packages ....................................... 32
Table 6-1. BSP Update and Line Card Upgrade Packages .............................................. 39
Table A-1. iDirect NMS software version - derived version string for SatManage .................. 67
Table B-1. Protocol Processor ifcfg-eth0 File Entries .................................................. 73
Table B-2. Protocol Processor ifcfg-eth1 File Entries .................................................. 74
Table B-3. Protocol Processor Host File Commands .................................................... 75
Network Upgrade Procedure Guide for iDX Release 3.5 and Later to x
About
Purpose
The Network Upgrade Procedure Guide outlines procedures for upgrading the iDirect Network
Management Software (NMS) and the Protocol Processor (PP) software for commercial (Non-
TRANSEC) networks. It also covers upgrading of the remotes and hub line cards in iDirect
networks. Each Network Upgrade Procedure Guide provides guidelines for upgrading from one
or more specific iDirect releases to another release — generally, to the latest release.
NOTE: This document is only for network upgrades from iDX 3.5 and later to iDX 4.1.x.x. For
network upgrades from iDX 4.0 to iDX 4.1.x.x, refer to Network Upgrade Procedure for iDX
4.0 to iDX 4.1.x.x Release document.
Audience
This document is intended for use by network operators and network architects that work
with the iDirect network system. Some basic knowledge of TCP/IP concepts, satellite
communications, and Linux and Windows operating systems is expected. Prior experience
operating an iDirect software network, although desirable, is not a requirement.
Contents
This document contains the following major sections:
• Read This First
• Upgrade Prerequisites
• Pre-Upgrade Tasks
• Upgrading NMS Server
• Upgrade Remotes
• Upgrade Hub Line Cards
• Upgrade iGateway and PP Blades
• Required Post-Upgrade Tasks
• SatManage Integration
Network Upgrade Procedure Guide for iDX Release 3.5 and Later to xi
About
Supported Upgrade Paths

The following upgrade paths are supported:
• iDX 3.5.1
• iDX 3.5.2.x
• iDX 3.5.3.x
• iDX 3.5.4.x
• iDX 4.1
• iDX 4.1.0.x
• iDX 4.1.1
New installations are also supported. See the Software Installation Guide for New Hubs
document for this release for instructions (available on the TAC Web site).
Document Conventions
This section illustrates and describes the conventions used throughout this document.
Convention Description Example

Command Used when the user is required to Enter the command:
enter a command at a command cd /etc/snmp/
line prompt or in a console.
Terminal Used when showing resulting crc report all
Output output from a command that was 8350.3235 : DATA CRC [ 1]
entered at a command line or on a 8350.3502 : DATA CRC [5818]
console. 8350.4382 : DATA CRC [ 20]
Screen Used when referring to text that 1. To add a remote to an inroute group, right-click
Reference appears on the screen on a the Inroute Group and select Add Remote.
Graphical User Interface (GUI). The Remote dialog box has a number of user-
Used when specifying names of selectable tabs across the top. The Information
commands, menus, folders, tabs, tab is visible when the dialog box opens.
dialogs, list boxes, and options.
Hyperlink Used to show all hyperlinked text For instructions on adding a line card to the
within a document or external network tree, see Adding a Line Card on
links such as Web page URLs. page 108.
WARNING: A Warning highlights an essential operating or maintenance

procedure, practice, condition, or statement which, if not strictly observed,
could result in injury, death, or long term health hazards.
CAUTION: A Caution highlights an essential operating or maintenance procedure,

practice, condition, or statement which, if not strictly observed, could result in
damage to, or destruction of, equipment or a condition that adversely affects
system operation.
xii Network Upgrade Procedure Guide for iDX Release 3.5 and Later to
About
NOTE: A Note is a statement or other notification that adds, emphasizes, or

clarifies essential information of special importance or interest.
Getting Help
The iDirect Technical Assistance Center (TAC) and the iDirect Government Technologies
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 products are available on the respective TAC Web site.
iDirect Contact Information:

• Web site: http://tac.idirect.net
• Telephone: (703) 648-8151
• E-mail: [email protected]
For sales or product purchasing information contact iDirect Corporate Sales at:
• Telephone: (703) 648-8000
iDirectGov Contact Information:

• Web site: http://tac.idirectgov.com
• Telephone: (703) 648-8111
iDirect and iDirectGov produce documentation that is technically accurate, easy to use, and
helpful to our customers. Please assist us in improving this document by providing feedback.
Send comments to:
• iDirect: [email protected]
• iDirectGov: [email protected]
Network Upgrade Procedure Guide for iDX Release 3.5 and Later to xiii
About
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.
NOTE: The software download instructions below only show the latest software
release. Please use the table below to substitute the software version with the
iDX software version that is specifically licensed for the network upgrade.
iDX 4.1.x.x Released Versions

4.1
4.1.0.1
4.1.0.3
4.1.0.4
4.1.0.5
4.1.1
4.1.2
iDirect software download instructions

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

1. Using the iDirect login name and password, log on to the iDirect TAC Web site (Refer to
Getting Help).
2. In the By Product section, click Software.
3. From Software, click Supplemental Releases.
4. Download all applicable software packages.
xiv Network Upgrade Procedure Guide for iDX Release 3.5 and Later to
About
Related Documents
The following additional iDirect documents are available on the TAC Web site 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.
• Release Notes
• iBuilder User Guide
• iMonitor User Guide
• Web iSite User Guide
• Technical Reference Guide
• Link Budget Analysis Guide
• Network Upgrade Procedure
• NMS Redundancy and Failover Technical Notes
• Software Installation Guide for New Hubs
• Satellite Router Installation and Commissioning Guide
• Installation, Support, and Maintenance Guide
• iDirect Features and Chassis Licensing User Guide
• SCAP User Guide
• iDirect Software Feature Matrix
• iDirect Hardware Matrix
Network Upgrade Procedure Guide for iDX Release 3.5 and Later to xv
About
xvi Network Upgrade Procedure Guide for iDX Release 3.5 and Later to
1 Read This First
This chapter contains essential information needed to perform a successful upgrade from iDX
3.5 and later to iDX Release 4.1.x.x. This guide provides detailed check lists of steps and
procedures for upgrading to iDX Release 4.1.x.x and preserving existing NMS network
configuration (and database) to use with the new iDX 4.1.x.x network.
CAUTION: This Network Upgrade Procedure document is intended only for

upgrading iDirect Non-TRANSEC networks.
NOTE: This document is only for network upgrades from iDX 3.5 and later to iDX
Release 4.1.x.x. For network upgrades from iDX release from Pre-iDX 3.5 releases
to iDX 4.1.x.x, refer to Network Upgrade Procedure for Pre-iDX 3.5 Releases to
iDX 4.1.x.x document.
Network Upgrade Procedure Guide for iDX Release 3.5 and Later to 1
Upgrade Flowchart
Study Figure 1-1 to determine which upgrade scenario process best applies to the existing
network. This flowchart can be detached and used as a reference while performing the
upgrade.
Legend
Upgrading from iDX3.5 and Later Hardware Pre-Upgrade
Version Dependent Dependent Planning
Outage Window Upgrade Window Special Instruction

Submit Upgrade Survey
Run Pre-Upgrade Script
Remove or replace unsupported

Unsupported elements found
? Yes
elements
No
Upgrade RCMs
Upgrade Remotes
Confirm distribution of PPS signal
Upgrade Hub Line Cards
Obtain NMS, Chassis, & Other Required Licenses
Upgrade the PP Server
Download the iDX 4.1.x.x ISO image
Check status of services
Modify the Crontab
Start all services on Primary NMS

Check the NMS databases for errors
Apply pending changes

Backup all servers and save backup files
Upgrade Backup NMS server

Upgrade the Primary NMS
Perform Post-upgrade Steps:

Apply NMS license
1. Reconfigure backup schedule via crontab files
.
2. Restore SNMP configuration.
3. Remove added custom keys(by script or manual) after all
Install NMS iBuilder/iMonitor remotes are recovered.
Figure 1-1. Upgrade Flowchart
2 Network Upgrade Procedure Guide for iDX Release 3.5 and Later to
Upgrade Checklist
This section provides an upgrade checklist to use for reference while performing the upgrade
steps. The steps in the network upgrade can differ depending on which version of iDirect
software currently exists on the target machine, and which models of hub line cards and
remotes are currently configured in the network.
The checklist, shown in Table 1-1, can be detached from this guide and used as a reference
while performing an upgrade.
Execute the procedures and steps that apply to the upgrade in the order in which they are
presented in the checklist.
CAUTION: The upgrade checklist contains optional steps that only apply to
specific network hardware or specific software versions. Be mindful and follow
only the tasks and procedures that apply to the customer specific network.
Table 1-1. Network Upgrade Checklist

Performing Prerequisites
 Complete and submit the iDX 4.1.x.x Upgrade/Installation Survey.
 Obtain all required license files as detailed in Section 2.3.1, "Administrative

Requirements and Licensing" on page 9.
• NMS Server license
• Hub Timing Group (chassis) license
• Hardware-Specific Feature License
• Protocol Processor Blade Feature License
See the iDirect Feature and Chassis Licensing Guide for details.
 Complete technical requirements (see Section 2.3.2, "Technical Requirements" on page 9)
 Multicast Download Verification, perform multicast download of a BSP to remotes

(without reset) to verify multicast download capability
 Perform Pre-Upgrade network requirement validation (see Section 2.4, "Pre-Upgrade Data
Capture Recommendations" on page 11)
In the case of a DNMS network upgrade, perform this procedure for all NMS’s in the
network.
If issues were found with the validation, then customer(s) must be notified to extend the
service window to perform the Pre-Upgrade network conversion (see Section 2.4, "Pre-
Upgrade Data Capture Recommendations" on page 11)
 Perform Pre-Upgrade network conversion (see Section 2.4, "Pre-Upgrade Data Capture
Recommendations" on page 11)
 Gather required data from the network and remotes (see Section 2.4, "Pre-Upgrade Data
Capture Recommendations" on page 11)
 Schedule downtime with customer(s)
 Consult with the TAC if custom keys are being used in the existing network
Performing Pre-Upgrade Activities
 Check Line Cards and Remotes for Custom Keys
 Check Network for Reserved Multicast Address
 Remove Old Entries in NRD_ARCHIVE Database
 Disable the NMS Database Replication Service
 Download the Latest iDX 4.1.x.x Images
 Preserve the SNMP Configurations
 Preserve the CM Configuration File
 Preserve the NMS Initialization File
 Modify the CRONTAB File
 Check the NMS Databases for Errors
Backing Up Existing Configurations and Data
 Backup NMS Server, for all servers and save all backups to multiple, safe locations.
Upgrading NMS
 Perform the NMS Upgrade
 Restore the SNMP Configurations
 Restore the CM Configuration File
 Restore the NMS Initialization File
 Update MySQL Passwords
 Restore the NMS Database and Configurations
 Revert NMS to TLS 1.0
 Apply NMS License and Run Service Upgrade
 Install NMS Client Software (iBuilder/iMonitor)
 Upgrade a Distributed NMS (optional)
Upgrading Remotes
 Consult with the TAC if any custom keys are being used in the existing network
 Download the BSP Package
 Download Image Packages and Options Files
 Reset The Remotes
Upgrading Hub Line Cards
 Download BSP Package
 Download Image Package and Options File
 Reset the Line Cards
Upgrading Protocol Processor Blades
 Upgrading Protocol Processor Blades
 Restore the PP Configurations. If the network is using Link Encryption, install PP

Encryption License
 Start PP Services
Upgrading iGateway Servers in a DVB-S2X Network
 Perform the iGateway Upgrade in a DVB-S2X network
 Verify iGW Software Version After Upgrade
Upgrading iGateway Servers in a DVB-S2 Network
 Upgrading iGateway in a DVB-S2 Network
Completing the Network Upgrade
 Restart Remaining Services on NMS Server
 Apply Configurations and the Remote Hub-side Configuration
 Verify the Uplink Control Parameters
 Rebalance Protocol Processor Blades
 Restart Transmit Hub Line Cards (Optional)
Upgrade the Backup NMS Server


Performing Required Post-Upgrade Activities
 Verify the Upgrade has Completed Successfully
 Verify Changes Pending on the Remotes and Incomplete Line Cards after the Upgrade
 Verify Chassis Configurations
 Reconfigure the Crontab File on the NMS Servers
 Rebuild NMS Database Replication (if applicable)
 Verify the Backup is in Working Condition
 Verify iDirect SNMP Configuration Working Settings (if applicable)
 Determine If Any Remotes Still Out-of-Network, enable the Revision Server until all
remotes are recovered.
 Software Upgrade/Install for X7 and 9-Series Remotes Second Partition
2 Upgrade Prerequisites
This chapter contains system requirements, data gathering requirements, and important
prerequisites for upgrading to iDX Release 4.1.x.x.
This chapter contains the following sections:
• Section 2.1, System Requirements
• Section 2.2, Hardware Requirements
• Section 2.3, Prerequisites
• Section 2.4, Pre-Upgrade Data Capture Recommendations
CAUTION: This Network Upgrade Procedure document is intended for upgrading

iDirect commercial (Non-TRANSEC) networks only.
CAUTION: Be sure to have the new RCM-PPS hardware installed prior to

performing the network upgrade. Refer to the New RCM-PPS Introduction
Technical Bulletin document available on the TAC Web site for detailed
instructions.
CAUTION: If any custom keys are currently used in the network, contact the TAC
to determine if the custom keys are valid in the new software release.
System Requirements
2.1 System Requirements

iDirect NMS clients (iBuilder, iMonitor, and iSite) are Windows PC-based applications that run
under the following releases of Windows:
• Windows 7
• Windows 10
NOTE: Windows 8, XP, Vista, NT, 98, and 95 are not supported in this release.
2.2 Hardware Requirements

NOTE: Starting with the iDX Release 3.2, IBM 336 Series and IBM 3550 Series
servers are no longer supported.
For client laptops or PCs, the following hardware specifications are recommended:
• Dual core processor, 2.8 GHz or better, 2 Gig RAM, 1 Gig available disk space
The following server hardware is supported for iDX 4.1.x.x:
• Dell PowerEdge R420
CAUTION: For Dell PowerEdge R630 V-Server upgrade, please refer to Appendix B,
R630 V-Server NMS and PP Upgrade on page 71.
CAUTION: For PP (in DVB-S2X mode) installation on a Dell PowerEdge R630 server,
please refer to Appendix C, R630 Server PP (DVB-S2X) Installation on page 79.
• Dell PowerEdge FX2
2.3 Prerequisites
Prior to performing an upgrade, the following set of tasks must be performed to ensure that
the upgrade is successful. This section lists all required pre-upgrade tasks. It also describes in
detail the data to be extracted from the existing networks prior to an upgrade. This data is
derived from a number of sources, including the NRD database, iBuilder, iMonitor, console
commands, and information received from the customer or network engineer. The data must
be reviewed for any discrepancies that can effect the upgrade process, post-upgrade network
recovery, or post-upgrade network status.Dell PowerEdge R630
Prerequisites
2.3.1 Administrative Requirements and Licensing

This section lists the required administrative tasks that must be performed prior to the
upgrade. The network operator is required to:
• Notify iDirect at least ten business days before beginning the upgrade procedure
• Obtain all required licensing files from the TAC before performing any of the procedures
in this guide, described as follows:
• Obtain an NMS license file from the TAC
• If the Link Encryption are going to be enabled in the network, then the customers
must obtain the appropriate license from the TAC.
• Download the iDirect Features and Chassis Licensing Guide for a complete description
of licensing issues.
NOTE: The information requires to generate all license files is captured in the
iDX Release 4.1 Upgrade/Installation Survey.
2.3.2 Technical Requirements

This section lists the required technical tasks that must be completed prior to the actual
upgrade. The network operator is required to:
• Obtain access to the TAC Web site to download the files required for the upgrade
• For all active remotes in the network, verify that the initial transmit power is about 3 dB
higher than nominal transmit power. Levels higher than this can interfere with normal
operation of the remotes and line cards.
• In a multi-NMS environment, where the chassis is shared, make sure only one NMS is
controlling the chassis. The NMS controlling the chassis must be running iDX Release 2.0.1
or later before other chassis can upgrade to iDX 4.1.x.x.
2.3.3 Multicast Download Verification

iDirect strongly recommends performing a multicast download of a BSP package or a remote
package (of the current release) to all remotes in the network in order to verify the
multicast package download capability. This test can be performed without resetting
remotes, so network operators can be perform this test days prior to the upgrade
maintenance window. Although the multicast download will use as much as 10% of the
downstream bandwidth during the test, performing this verification will ensure the multicast
download capability at the time of actual upgrade. If the multicast download fails for any
reason, contact TAC to investigate prior to entering the maintenance window.
A Multicast test determines which remotes are in the network and capable of receiving
multicast messages. “Active” remotes within a network are those that are active in the NMS
database and have been detected when the hub is sweeping for remotes.
Perform the following:
1. Launch iBuilder and log in as administrator.
2. In the Tree View, right-click on the Network icon, and select Package
DownloadMulticast.
Prerequisites
The Multicast Download window displays (Figure 2-1).
Figure 2-1. Multicast Download Window
When doing a Multicast Test, iBuilder automatically selects all of the active components
in the network. In the Modems area of the Multicast Download window, a list with all
active remotes selected should be displayed.
3. In the Package pane, select the following:
• For Hardware, select EvolutionXXRemote
• For Role, leave the default Remote selected
• In the Version drop-down field select Test-Package.
4. Click Start to begin the Multicast Test.
During the test, progress is displayed in the Progress bar (lower left corner). As each remote is
successfully tested, “Done” displays to the right of each remote in the Modems area. Also
watch for “PKG: Flash Completed” messages for each remote in the Event Description
column at the bottom of the Multicast Download window.
Pre-Upgrade Data Capture Recommendations
2.4 Pre-Upgrade Data Capture Recommendations

It is strongly recommended that the tasks outlined in this section be performed prior to the
upgrade.
2.4.1 Network Data Requirements

This section describes the required data that network operators must extract from the
network prior to an upgrade.
To acquire the data, perform the following:
• Obtain a copy of the configuration database. If no security restrictions are violated, send
a copy of the database to the TAC for review and analysis
• Using iBuilder:
– Verify that the transmit powers of the Hub Tx line cards match the configurations in
the line card options files. If not, make the necessary configuration changes. See the
iDX Release 4.1 iBuilder User Guide for instructions.
– Check and record each Inroute and its associated hub line card for the Frequency-
Hopping or Carrier-Grooming mode
– Capture all hub line card configurations
– Capture all carriers and Hub equipment details
– Record the Network Acquisition/UCP control window settings
– Record all line cards, Network and Protocol Processor level custom keys
– Record all carriers are assigned for each inroute group
– Record hub chassis slot assignment for each hub line card
• Using iMonitor:
– Record the average number of CRC errors on line cards per Frequency-Hopping
inroute and per Carrier-Grooming inroute.
– Record the Rx composite power for each line card. This can be viewed in iMonitor as
part of the Line Card Stats.
– Capture the GEO location for the teleport and satellite.
2.4.2 Chassis Data Requirements

This section describes the required data that must be preserved for all MIDAS chassis in the
network prior to performing the network upgrade. This procedure is required due to a design
change in the MIDAS chassis to ensure that each MIDAS chassis is properly provisioned for the
first time after the upgrade.
• Take screenshot of all MIDAS chassis configurations
• Be sure that all chassis are reflecting the captured configurations
Pre-Upgrade Data Capture Recommendations
2.4.3 Remote Disk Space Survey

Prior to the actual network upgrade, it is recommended to check the disk space availability
for all remotes in the network. This process helps to minimize the failure rate for those
remotes that do not have sufficient disk space to properly upgrade to the latest software
release.
To perform the remote survey, download the Remote Survey software and user guide from the
TAC Web site. On the TAC Web site, navigate to Supplemental Releases (Refer to Software
Download on page xiv) and click the Remote Survey Software Package link to download the
software and user guide. Follow the provided instructions to survey all remotes in the
network.
NOTE: For iDirectGov TAC Web site, navigate to Supplemental Releases and click
the Remote Survey Software Package to download the software and user guide.
2.4.4 Remote Data Requirements

This section describes the required data to extract from the remotes prior to an upgrade. This
data is necessary to ensure the remote settings are accurate after the upgrade.
1. Obtain a “Network Data Snapshot” for each network and export the data into a
spreadsheet.
2. Take a screenshot of the iMonitor control panel data for several remotes in each network.
3 Pre-Upgrade Tasks
This chapter contains required procedures that must be completed before upgrading to iDX
Release 4.1.x.x. The procedures in this chapter prepare the network for an upgrade to the
latest iDX 4.1.x.x. Before beginning these procedures, it is recommended that customers
review the iDX Release Notes 4.1.x.x. In the Release Notes, note any special instructions that
need to be performed before and during the upgrade process.
This chapter contains the following procedures:
• Procedure 1. "Check Line Cards and Remotes for Custom Keys"
• Procedure 2. "Check Network for Reserved Multicast Address"
• Procedure 3. "Remove Old Entries in NRD_ARCHIVE Database"
• Procedure 4. "Disable the NMS Database Replication Service"
• Procedure 5. "Download the Latest iDX 4.1.x.x Images"
• Procedure 6. "Preserve the SNMP Configurations"
• Procedure 7. "Preserve the CM Configuration File"
• Procedure 8. "Preserve the NMS Initialization File"
• Procedure 9. "Modify the CRONTAB File"
• Procedure 10. "Check the NMS Databases for Errors"
• Procedure 11. "Backup NMS Server"
CAUTION: This Network Upgrade Procedure document is intended only for

upgrading iDirect commercial (Non-TRANSEC) networks.
CAUTION: Do not continue the network upgrade if any problems arise while
performing the procedures in this chapter. Contact TAC at immediately for
assistance (Refer to Getting Help on page xiii).
Procedure 1. Check Line Cards and Remotes for Custom Keys
Before applying custom keys to Evolution line cards and remotes, it is necessary to check for
any existing custom keys on the equipment. The checkcksh script identifies any custom keys
on the remote’s hub side, remote side, or both, including any [BEAMS_LOCAL] custom keys.
It also identifies any Line Card custom keys.
To check all Hub line cards and remotes for custom keys, perform the following:
1. From the TAC Web site, navigate to Supplemental Releases (Refer to Software Download
on page xiv).
2. Download the checkcksh.gz file.
3. Using WinSCP, copy the file to the NMS server’s /tmp directory.
4. Log in to the NMS server and switch to root.
5. Go to the /tmp directory.
cd /tmp
6. Unzip the checkcksh.gz file.
gunzip checkcksh.gz
7. Make the script executable.
chmod 755 checkcksh
8. Run the script and save the resulting data to an output file named check_ck.output.
./checkcksh > check_ck.output
9. Sort the results using the following command:
sort check_ck.output
An example of the script commands and its output is shown below.
# sort check_ck.output
Remote "e8350 1816" (NW=2 did=27264792) has remote and hub side Custom
Keys
Remote "e8350 1816" (NW=3 did=27264792) has remote and hub side Custom
Keys
Remote "eM1D1 17509" (NW=6 did=26494053) has hub side Custom Keys
Remote "eM1D1 17600" (NW=6 did=26494144) has hub side Custom Keys
Remote "iConnex e850mp 45454" (NW=6 did=100708750) has remote and hub
side Custom Keys with Beam header
Remote "New Remote #115" (NW=2 did=4980736) has remote side Custom Keys
with Beam header
Remote "X3 682" (NW=6 did=33555114) has remote side Custom Keys
Remote "X5 9944" (NW=2 did=117450456) has remote and hub side
Custom Keys with Beam header
Remote "X5 9944" (NW=3 did=117450456) has remote and hub side
Custom Keys with Beam header
Remote "XLC-11 17645" (NW=1 did=26756333) has hub side Custom Keys
Remote "XLC-M 17599" (NW=1 did=134235327) has hub side Custom Keys
10. Using iBuilder, remove any custom keys which have been identified in Chapter 2, Upgrade
Prerequisites on page 7.
Procedure 2. Check Network for Reserved Multicast Address
Starting with iDX Release 3.5.1, iDirect has reserved a multicast IP address for internal system
messages that are broadcast by the Protocol Processor to the remotes. The reserved multicast
IP address is 239.2.2.1, which is set by default at the Protocol Processor level. If this multicast
IP address is currently being used in the network, then it must be changed to an unused
multicast IP address prior to the upgrade.
To modify the multicast IP address in the network, perform the following:
1. Log into the network using iBuilder.
2. At the Protocol Processor level, right-click and choose Modify option.
3. At the bottom of the Information tab, locate the Multicast Groups table.
4. Verify all existing multicast groups configured on the network to see if any of them is
configured with the reserved multicast IP address (239.2.2.1).
5. If a conflict with the reserved multicast IP address is found, then modify the conflicted
multicast IP to an unused multicast IP.
6. Save and apply the changes to the Protocol Processor.
Procedure 3. Remove Old Entries in NRD_ARCHIVE Database

In a large iDirect network that has been operating for more than 60 days, the
state_change_log_X tables in the NRD_ARCHIVE database may not have been consolidated
properly causing them to grow to an unmanageable size, affecting backup and consolidation.
Due to the size of these tables, the first regular consolidation after the upgrade may take
several hours before it completes, thereby making the database unavailable for the nrdsvr
process and/or SatManage polling. It is recommended that the expired data be deleted from
these tables in the NRD_ARCHIVE database.
Perform the following steps to remove data that is older than 60 days from the
state_change_log_X tables in the NRD_ARCHIVE database:
1. Log in to the NMS server as idirect and switch to root.
2. Enter the following command (in one line) to remove the database entries:
for TABLE in 0 1 2 3 4 5; do mysql nrd_archive -e "delete from
state_change_log_$TABLE where timestamp < now() - interval 60 day; optimize
table state_change_log_$TABLE;"; done
Procedure 4. Disable the NMS Database Replication Service

When preparing the network upgrade to iDX 4.1, the NMS database replication service must
be disabled for all the NMS servers in the network. Below is the procedure to disable the NMS
database replication service.
To stop the replication service to a Backup NMS server, perform the following:
1. Log in the Primary NMS server as idirect and switch to root.
2. Stop the replication service using the following command:
cr8DbMaster -d <MySQL slave’s IP Address>
NOTE: If there is only one MySQL slave associated with this MySQL master, the
above command also disables database replication on this Primary Server, so it is
no longer configured as a MySQL master.
Procedure 5. Download the Latest iDX 4.1.x.x Images

Before starting the upgrade process, the software release images for this release must be
downloaded from the TAC Web site.
NOTE: Refer to Table 3-1 for the correct iDX/iDS Release version number for the
network upgrade. For all references to the iDX 4.1.x.x and iDS 21.0.x.x in the
document, substitute them with the correct IDX and iDS version number for the
network upgrade.
Table 3-1. iDX to iDS Version Number Conversion
IDX Version iDS Version

4.1.0.0 21.0.0.0
4.1.0.1 21.0.0.1
4.1.0.3 21.0.0.3
4.1.0.4 21.0.0.4
4.1.0.5 21.0.0.5
4.1.1.0 21.0.1.0
4.1.2.0 21.0.2.0
To download the images:

1. Create a temporary folder on the PC or laptop’s desktop.
2. Download all applicable software packages for iDX Release 4.1.x.x (Refer to section
Software Download on page xiv).
NOTE: Patches may also be part of the new release. Be sure to download all
related patch software for the new release. This is typically shown as a link under
the section for that software release. Keep in mind that patches include files that
are in addition to the standard files required for download, and may not contain
full software.
3. Create a Kickstart DVD using the NMS/PP ISO image downloaded from the TAC Web site.
4. From the TAC Web site, navigate to Supplemental Releases (Refer to Software Download
on page xiv).
5. Click the link IDDB Tools For iDX 3.5 and Later to download the check and repair scripts
(in compressed tgz format).
6. Save the iddb_tools_iDX35.tgz file to a remote PC/laptop or other location.
Procedure 6. Preserve the SNMP Configurations
During the software upgrade on the NMS server, the SNMP configuration files may be
overwritten by the upgrade script. This action may cause the NMS server communication to
not completely function normally after the network has upgraded to the latest software
release.
The following configuration files are recommended to preserve before the network upgrade:
• snmpd.conf file located in the /home/nms/snmpsvr directory
• The SNMP trap configuration parameters in the para_cfg.opt file located in the
/home/nms/snmpsvr directory
To preserve the snmpd.conf file, perform the following:
1. Log in the NMS server as idirect and switch to root.
2. Go to the /home/nms/snmpsvr directory
cd /home/nms/snmpsvr
3. Copy the snmpd.conf file to the /var/tmp directory
cp snmpd.conf /var/tmp/.
To preserve the SNMP trap configuration parameters, perform the following:
1. From the /home/nms/snmpsvr directory, view the para_cfg.opt contents
cat para_cfg.opt
The following sample output displays:
[DB_PARM]
db_host_name = 127.0.0.1
db_database_name = nrd_archive
drvmgr_max = 20
[TRAP_PARM]
trapsink = localhost
trap2sink = localhost
community = public
db_user_name = nms
db_password = iDirect
2. Preserve the SNMP trap configuration parameters (highlighted above in red fonts).
Procedure 7. Preserve the CM Configuration File

As part of the NMS software upgrade, the upgrade script may also overwrite the chassis
manager (CM) configuration file named para_cfg.opt located in the /home/nms/cm directory.
In case of the CM IP address configured in the para_cfg.opt file is different than one in the
license file, the upgrade script will overwrite the CM IP address in the para_cfg.opt file with
the IP address configured in the license file causing the NMS server to lose connectivity with
the CM server.
To preserve the para_cfg.opt file, perform the following:
2. Go to the /home/nms/cm directory
cd /home/nms/cm
3. Copy the para_cfg.opt file to the /var/tmp directory
cp para_cfg.opt /var/tmp/CM_para_cfg.opt
Procedure 8. Preserve the NMS Initialization File

NOTE: Perform this procedure only if the nms_start file on the NMS server has
been customized previously to support your network operations.
This procedure describes steps to preserve the nms_start file.

2. Go to the /home/nms/utils directory
cd /home/nms/utils
3. Copy the nms_start file to the /var/tmp directory
cp nms_start /var/tmp/nms_start.bkup
Procedure 9. Modify the CRONTAB File

The idsBackup script on both the primary NMS and the backup NMS must be prevented from
execution during the upgrade procedure. To do this, add the comment symbol (#) to the
beginning of all lines in the CRONTAB file.
1. Open two PuTTY sessions and login as root to both the Primary NMS and the Backup NMS.
2. To edit the CRONTAB file, enter the following command:
crontab -e
This command opens the CRONTAB in the Linux Vi editor.
3. Insert the comment symbol (#) to the beginning of all lines in the CRONTAB file.
4. Save the changes to the file and exit.
Remember to do this on both the Primary NMS and the Backup NMS before performing the
upgrade. Examples are shown here:
On the Primary NMS:
#0 0 * * * /opt/idirect/nms/utils/db_maint/cons.pl >>
/opt/idirect/nms/utils/db_maint/cons.output 2>&1
#0 4 * * 6 /opt/idirect/nms/utils/db_maint/check_db.pl >>
/opt/idirect/nms/utils/db_maint/check_db.output 2>&1
#30 0 * * * /usr/bin/idsBackup -bkup /var/idirect/backup/\%ip-\%date --
keep 2
#00 0,6,12,18 * * * /usr/bin/mysql-binlog-purge
#0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/bin/mysql-repl-monitor
#2,7,12,17,22,27,32,37,42,47,52,57 * * * * /usr/bin/repl-file-send
On the Backup NMS:
#30 0 * * * /opt/idirect/install/idsBackup -host local --keep 2
>/dev/null 2>&1
#0 0 * * * /opt/idirect/nms/utils/db_maint/cons.pl >>
#0 4 * * 6 /opt/idirect/nms/utils/db_maint/check_db.pl >>
Procedure 10. Check the NMS Databases for Errors

Errors in the databases on the NMS may prevent the software installation script from running
correctly. This procedure ensures that no errors exist and also checks for unsupported tables.
NOTE: NMS databases that are to be upgraded to iDX Release 4.1.x.x cannot
contain either InnoDB tables or Merge tables. The preUpdateCheck script checks
for the existence of these tables and optionally converts them to supported table
types.
To check for database errors, perform the following:

1. Log in to the Primary NMS server using SSH (PuTTY).
2. Stop the NMS server process using the following command:
service idirect_nms stop
3. Using WinSCP, copy the iddb_tools_iDX35.tgz file (downloaded during Procedure 5.
"Download the Latest iDX 4.1.x.x Images", Step 7) to the /tmp directory on the Primary
NMS Server.
4. Change to the /tmp directory using the following command:
cd /tmp
5. Unzip the database repair tools using the following command:
tar zxvf iddb_tools_iDX35.tgz
6. Make the file executable using the following command:
chmod 755 iddbrepair.sh
7. Repair any faulty database tables using the following command:
./iddbrepair.sh
NOTE: Execution time of this command may be varied base on the size of
network database. For a large database, it may take as long as an hour for the
command to complete.
8. Check for any merge tables or InnoDB tables in the database using the following
commands:
chmod 755 preUpdateCheck
./preUpdateCheck
The result should show the following:
[root@NMS tmp]# ./preUpdateCheck
No issues found.
a. If any Merge tables or InnoDB tables are detected, the following messages display:
The database contains the following merge tables that cannot be
migrated:
Specify "--dropMerge" to drop these merge tables.
The database contains the following InnoDB tables that cannot be
migrated:
Specify "--convertInnoDB" to convert these tables to MyISAM tables
CAUTION: Do not continue the network upgrade if any InnoDB or Merge tables
are found in the database. Contact TAC immediately for assistance (Refer to
Getting Help on page xiii).
b. If the MySQL PID file is missing or does not match the current hostname, one of the
following messages displays:
MySQL appears to be running but PID file was not found:
/var/lib/mysql/<hostname>.pid
Specify "--restartMySQL" to correct this issue.
or
MySQL appears to be running but PID file does not match hostname:
If either of these messages displays, reboot MySQL using the following command:
./preUpdateCheck --restartMySQL
9. Proceed to the next procedure to prepare the database backup. If the upgrade is not to
be performed at this time, restart the NMS services using the following command:
service idirect_nms start
Procedure 11. Backup NMS Server

NOTE: If the NMS database is currently being polled by a SatManage server, then
NMS polling process MUST be disabled on the SatManage server using Procedure 1.
"Disabling NMS Polling on SatManage Server" on page 65 described in Appendix A
CAUTION: Be sure to note down the current database password. It will be used for
restoring the NMS database when performing the idsRestore procedure.
To backup the NMS and PP servers, perform the following:

1. Login to the Primary NMS server as root.
2. Using WinSCP, transfer the Kickstart ISO image downloaded previously from the TAC Web
site to the /var/tmp directory on the primary NMS.
3. Create a directory called /media/cdrom using the following command:
mkdir -p /media/cdrom
4. Mount the image using the following command:
mount -o loop /var/tmp/IDS-21.0.x.x.iso /media/cdrom
Refer to Table 3-1 for the correct iDS version number.
5. Run idsBackup using the following as a one-line command:
/media/cdrom/iDirect/install/idsBackup --keep 2 --bkup
/var/idirect/backup/\%ip-\%date
NOTE: The command is to be entered exactly shown. Do not substitute the

“%ip” and “%date” for an actual IP address or exact date. The IP address and
current date/time of the server are automatically populated at the command
execution.
6. Use WinSCP to copy the backup file to an external, safe location such as a local PC.
7. Unmount the image using the following command:
umount /media/cdrom
8. Repeat this procedure for the PP servers.
This completes the pre-upgrade tasks. Proceed to the next chapter for instructions on
upgrading the NMS servers.
4 Upgrading NMS Server
Before upgrading the NMS servers, be sure that all NMS servers data have been backed up and
saved as described in Procedure 11 “Backup NMS Server” on page 20. Make sure the backup
archived file has been copied to one or more external and safe locations.
CAUTION: If the NMS server to be upgraded is a part of the DNMS network

configuration, then it MUST be validated using the procedure described in
Section 2.4, Pre-Upgrade Data Capture Recommendations on page 11. If any
issues found, DO NOT continue with the NMS upgrade and contact TAC
immediately for additional supports.
This chapter contains the following procedures:

• Procedure 1. "Perform the NMS Upgrade"
• Procedure 2. "Restore the SNMP Configurations"
• Procedure 3. "Restore the CM Configuration File"
• Procedure 4. "Restore the NMS Initialization File"
• Procedure 5. "Update MySQL Passwords"
• Procedure 6. "Restore the NMS Database and Configurations"
• Procedure 7. "Revert NMS to TLS 1.0"
• Procedure 8. "Apply NMS License and Run Service Upgrade"
• Procedure 9. "Install NMS Client Software (iBuilder/iMonitor)"
• Procedure 10. "Upgrade a Distributed NMS (optional)"
NOTE: For upgrading a Backup NMS server, see Procedure 1. "Upgrade the Backup
NMS Server" on page 58.
NOTE: If the NMS database is currently being polled by a SatManage server, then
NMS polling process MUST be disabled on the SatManage server using Procedure 1.
"Disabling NMS Polling on SatManage Server" on page 65 described in Appendix A,
SatManage Integration.
Procedure 1. Perform the NMS Upgrade
The upgrade software consists of the files downloaded in Procedure 5 “Download the Latest
iDX 4.1.x.x Images” on page 16. The first file contains the ISO image, which contains all the
files, is needed to:
• Verify the upgrade media using the embedded MD5SUM and the checkisomd5 command
• Uninstall the old version of MySQL and install the new version of MySQL
• Install RHEL 6.8
• Install iDX Release 4.1.x.x NMS software (Refer to Table 3-1 for the correct iDX/iDS
version number for the network upgrade).
• Update all RHEL, MySQL, and iDirect RPMs
The upgrade may include RHEL 6.x changes that require a reboot to be effective.
This procedure must be performed on every NMS that are being upgraded (this includes
Primary and Backup NMS servers, and all NMS servers in a Distributed NMS configuration).
1. Log in to the NMS server as idirect and switch to root.
2. Stop the NMS server process using the following command:
service idirect_nms stop
3. Using WinSCP, transfer the Kickstart ISO image that has been downloaded previously to
the /var/tmp directory on the primary NMS.
4. Create a directory called /media/cdrom using the following command:
5. Mount the ISO image to the /media/cdrom directory using the following command:
6. Update the NMS server using the following command:
/media/cdrom/iDirect/install/idsUpdate
NOTE: Use the --harden and --force tokens with the idsUpdate command if
SCAP compliance is required, for example: idsUpdate --harden --force
a. Starting with iDX Release 3.2, the upgrade process requires the MySQL user passwords
to be changed if the existing passwords are iDirect default passwords. If this is the
case, when issuing the idsUpdate script, new passwords are required for the MySQL
‘root’ and ‘nms’ users. Enter a new password for each user:
Changing password for MySQL user: root.
New MySQL password for user root: ********
Retype new MySQL password for user root: ********
Changing password for MySQL user: nms.
New MySQL password for user nms: ********
Retype new MySQL password for user nms: ********
NOTE: When upgrade the Distributed NMS, be sure to assign the same password(s)
for all NMS servers.
b. This upgrade may include RHEL 6.x changes that require a reboot to be effective. If
this is the case, the following error message displays:
One or more of the RPM’s selected for update will require that the
system be rebooted after update.
Update aborted! Specify option --reboot to update the system and reboot.
If this message displays, enter the idsUpdate command again with the reboot option
as shown:
/media/cdrom/iDirect/install/idsUpdate --reboot
c. If the MySQL PID file is missing or does not match the current hostname, one of the
following messages displays:
MySQL appears to be running but PID file was not found:
or
MySQL appears to be running but PID file does not match hostname:
If either of these messages displays, restart MySQL using the following command:
/media/cdrom/iDirect/install/idsUpdate --restartMySQL
Procedure 2. Restore the SNMP Configurations

This procedure is required to restore the SNMP configuration files and parameters, which have
been preserved previously in Procedure 6. "Preserve the SNMP Configurations" of Chapter 3,
Pre-Upgrade Tasks.
To restore the snmpd.conf configuration file, perform the following:
2. Go to the /var/tmp directory
cd /var/tmp
3. Copy the snmpd.conf file to the /etc/idirect directory
cp snmpd.conf /home/nms/snmpsvr/.
To restore the SNMP trap configuration parameters, perform the following:
1. Go to the /home/nms/snmpsvr directory
2. Open the para_cfg.opt file in edit mode using Vi editor
vi para_cfg.opt
3. Overwrite the existing SNMP trap parameters with those previously preserved.
[TRAP_PARM]
community = public
4. Save changes to the file and exit by pressing Esc and entering the following command:
:wq!
Procedure 3. Restore the CM Configuration File

This procedure is required to restore the CM configuration files and parameters, which have
been preserved previously in Procedure 7. "Preserve the CM Configuration File" of Chapter 3,
Pre-Upgrade Tasks.
To restore the para_cfg.opt file, perform the following:
2. Go to the /home/nms/cm directory
cd /home/nms/cm
3. Rename the para_cfg.opt file in the directory to NEW_para_cfg.opt
mv para_cfg.opt NEW_para_cfg.opt
4. Copy the para_cfg.opt file from the /var/tmp directory to the /home/nms/cm directory
cp /var/tmp/CM_para_cfg.opt /home/nms/cm/para_cfg.opt
5. Copy the database configuration parameters from the New_para_cfg.opt file to the
para_cfg.opt file.
A sample of the database configuration parameters is shown below.
[DB_PARM]
db_user_name = nms
Procedure 4. Restore the NMS Initialization File

Perform this procedure only if a backup of the nms_start file has been saved previously using
Procedure 8. "Preserve the NMS Initialization File" of Chapter 3, Pre-Upgrade Tasks.
To restore custom configurations in the nms_start file, perform the following:
2. Go to the /var/tmp directory
cd /var/tmp/
3. Open the nms_start.bkup and identify the custom configurations.
4. Go to the /home/nms/utils directory.
cd /home/nms/utils
5. Open the nms_start file using Vi editor and add the custom configurations to the file.
vi nms_start
CAUTION: Do not delete any lines in the nms_start file that does not appear in
the backup nms_start file.
6. Add the following environment variable to nmssvr) section in the nms_start file to
prevent an issue with iBuilder client not able to connect to the NMS.
export ENV_OMP_DISABLE=1
Below is how the nmssvr) section looks like after adding the new variable.
nmssvr)
export ENV_CFG_MCASTDL_CONNECTION_TIMEOUT="10"
export ENV_TCP_CLIENT_QUEUE_MAX_BYTES=$((1024*1024*1024))
export ENV_SENDQUEUE_THRESHOLD_PERCENT=60
export ENV_NMS_CFG_FILE="/home/nms/cfg/nms_cfg.opt"
export ENV_DB_CFG_PARMS_FILE="/home/nms/cfg/para_cfg.opt"
export ENV_OMP_DISABLE=1
check_and_start "/home/nms/cfg/nmssvr" "--debug 4"
:wq!
Procedure 5. Update MySQL Passwords

Prior to restoring the NMS database and configurations, the MySQL user passwords must be
updated to match what configured in the mysql_accounts.conf file located in the
/home/nms/utils/db_maint directory.
1. Log in the NMS server as idirect user, then switch to root user.
2. Identify the passwords configured in the mysql_accounts.conf file using the following
commands:
cd /home/nms/utils/db_maint
cat mysql_accounts.conf
3. The output should show the mysql_accounts.conf file similar to the example shown below.
[admin]
password = P@55w0rd!
user = root
[app]
password = iDirect
user = nms
4. Update the MySQL user passwords based on the previous output using the following
command:
dbPasswd
5. Follow the prompts to update the passwords for both root and nms MySQL users to match
the passwords configured in the mysql_accounts.conf file.
6. After the passwords have been updated, the script automatically stops the NMS server,
starts the MySQL server and resets passwords for all configured users, and updates all
associated configuration files.
Procedure 6. Restore the NMS Database and Configurations

This procedure is required to restore NMS database and configuration, which have been
preserved previously in Chapter 3, Pre-Upgrade Tasks.
To restore the NMS database and configuration files, perform the following:
1. Using WinSCP to transfer the backup file previously saved to the /tmp directory on the
NMS server.
2. Run the idsRestore script using the following command:
/usr/bin/idsRestore --bkup /tmp/<backup_file> -noNet -noHostCfg
Where,
<backup_file> represents the exact file name of the backup file.
Procedure 7. Revert NMS to TLS 1.0

This procedure must be performed in order for the NMS to continue to talk to all other
network components. Starting with iDX Release 4.1.0.2, the NMS software has been enhanced
to support TLS version 1.2 by default. Since the NMS server has been recently updated to the
latest iDX 4.1.0.x release, it automatically enable the TLS 1.2 support and no longer be able
to communicate with all network components which have yet to be updated. The NMS server
must be revert back to support TLS 1.0 so that it continue to communicate with all other
network components to complete the network upgrade.
2. Go to the /home/nms/utils directory using the following command:
cd /home/nms/utils
3. Use Vi editor to open the nms_start file using the following command:
vi nms_start
4. Add the following environment variable for TLS underneath the “nmssvr)” section:
export USE_TLS1=1
5. Save the changes and close the file.
The “nmssvr)” section should look similar to the example shown below
nmssvr)
export USE_TLS1=1
check_and_start "/home/nms/cfg/nmssvr" "--debug 4
Procedure 8. Apply NMS License and Run Service Upgrade

Perform all of the steps in this procedure on the Primary NMS. On the Backup NMS, perform
steps 1 through 4 (copy the NMS license to /home/nms/cfg folder) and step 5 (replace the
license file). Do not perform step 6 (start NMS services in upgrade mode) on the Backup NMS.
1. Use Win SCP as idirect user to copy the NMS license file obtained from the TAC and place
it in the /var/tmp directory on the Primary NMS.
3. To retain the “old” license file, copy it to another location before overwriting it with the
new license file:
mv /home/nms/cfg/nmssvr_e.lic /home/nms/cfg/nmssvr_e.lic.<release>
4. Go to the /var/tmp directory using the following command:
cd /var/tmp
5. Copy the new license file to the /home/nms/cfg directory using the following command:
cp newlicense.lic /home/nms/cfg/nmssvr_e.lic
Where newlicense.lic is the name of the license file provided by TAC.
When the Linux prompt is returned, continue to the next step.
6. Start the NMS services in upgrade mode using the following command:
service idirect_nms upgrade
Procedure 9. Install NMS Client Software (iBuilder/iMonitor)

To install the client software, perform the following:
1. On the PC/Laptop, log in as an administrator.
Using Unzip, WinZip, or PKZIP, uncompress the previously downloaded 
nmsclients210xx.zip file to a location on a local PC/laptop where it can easily locate
later. If the PC/laptop is running Windows XP, right-click on the file and select Extract All.
2. To install the NMS client software, double-click the nms_clients_setup.exe icon
contained in the NMS Clients folder.
When the setup program has finished, the application shortcut for iBuilder, iMonitor, and
iSite are populated in the Windows/Start/Programs menu under iDirect. InstallShield also
creates a folder called NMS Clients 21.0.x.x with shortcuts on the desktop.
3. Verify NMS connectivity by pinging the Primary NMS Server.
4. Open the newly installed iBuilder and connect to the upgraded NMS. Check the status of
remotes and line cards.
5. Open the newly installed iMonitor and connect to the same upgraded NMS. Check the
status of remotes and line cards.
Procedure 10. Upgrade a Distributed NMS (optional)

To upgrade a distributed NMS, perform the following:
1. Upgrade each server using Procedure 1through Procedure 6 as outlined in this chapter.
2. Upgrading to iDX Release 4.1 requires reconfiguration of the Distributed NMS after
upgrading each of the servers by executing the NMS-configuration-client.pl script
from the Primary NMS server. Reconfigure the Distributed NMS at this point. For additional
details, see the appendix on “Configuring a Distributed NMS” of the iBuilder User Guide
for this release.
3. After the upgrade is completed, run the “dbPasswd” command in all servers to update
and sync the passwords for all server using the only one password.
NOTE: If the Chassis Manager process (cmsvr) is running on one of the NMS
servers that belongs to the D-NMS group, then the cmsvr location must be
specified when reconfiguring the D-NMS group. For additional details, see the
appendix on “Configuring a Distributed NMS Server” of the iBuilder User Guide
for this release.
NOTE: If the NMS server being upgraded is currently configured to run with
SatManage server, then the nms_start script MUST be reconfigured using
Procedure 3. "Removing Latency Restriction on NMS Server" on page 68
described in Appendix A, SatManage Integration.
This completes the NMS server portion of the network upgrade. Proceed to the next chapter
for instructions on upgrading the remotes.
5 Upgrade Remotes
This chapter contains the following procedures to successfully install iDX Release 4.1 software
on the remotes:
• Procedure 1. "Download the BSP Package"
• Procedure 2. "Configure Ports Tab on iQDesktop Remotes"
• Procedure 3. "Download Image Packages and Options Files"
• Procedure 4. "Reset The Remotes"
*** NETWORK DOWNTIME BEGINS HERE ***
NOTE: Prior to performing the remote software upgrade, it is recommended to

reset all active remotes in the network to free up temporary memory and disk
space being used to allow proper download and install of the new software.
NOTE: If more than one type of remotes are configured in the network, then the
procedures in this chapter must be performed separately for each remote type.
NOTE: Refer to Table 3-1 for the correct iDX/iDS Release version number for the
network upgrade. For all references to the iDX 4.1.x.x and iDS 21.0.x.x in this
chapter, substitute them with the correct IDX and iDS version number for the
network upgrade.
The Linux BSP package files and remote package files by remote type for the current release
are listed in Table 5-1.
Table 5-1. Cumulative Update and Remote Upgrade Packages
Type of Remote Linux BSP package Remote Package

Evolution X1 Remote Indoor N/A evo_x1_indoor_rmt-21.0.2.0
Evolution X1 Remote Outdoor N/A evo_x1_outdoor_rmt-21.0.2.0
Evolution E150 Remote N/A evo_e150_rmt-21.0.2.0
Evolution X3 Remote evo_x3_bsp-21.0.2.0 evo_x3_rmt-21.0.2.0
Evolution X5 Remote evo_x5_bsp-21.0.2.0 evo_x5_rmt-21.0.2.0
Evolution X7 Remote N/A evo_x7_rmt-21.0.2.0
Evolution 8 Series evo_bsp-21.0.2.0 e8_rmt-21.0.2.0
Evolution 9 Series N/A 9series_rootfs_rmt-21.0.2.0
Evolution EP100 Series evo_bsp-21.0.2.0 ep100_rmt-21.0.2.0
NOTE: Table 5-1 only specifies the latest iDX/iDS Release software version
number for referencing purposes. Refer to Table 3-1 for the correct iDX/iDS
version number for the network upgrade.
After finished upgrading the network, the revision server can be used to automatically
upgrade any off-line remotes.
CAUTION: When upgrading the remotes using the multicast option in a large
network, the NMS automatically segments the remotes into groups of 150 remotes
for each multicast session and repeats the process until all the remotes in the
network are upgraded.
CAUTION: The multicast download feature can only be run on one network at a
time. It may be necessary to repeat downloading packages to remotes in cases
where remotes do not acknowledge.
CAUTION: When using the Multicast Download option, sets the download rate to
400 Kbps or a lower value based on system calculation for the downstream data
rate.
iDirect recommends keeping a Telnet session open to components being upgraded. This
precaution provides visibility into the state of the package downloads and installations on
these components. However, on large inroute groups, it is not practical to monitor all remotes
this way. In these cases, open telnet sessions only to a few sample remotes, picking the
remotes with the lowest C/N on the downstream.
Procedure 1. Download the BSP Package
To properly upgrade the remote software, first the Linux BSP update package listed in Table
5-1 on page 32 must be downloaded before loading the remote software package.
1. In iBuilder, in the Tree View, right-click the Network icon, and then select Package
The Multicast Download window displays (Figure 5-1).
Figure 5-1. Multicast Download — Downloading the Cumulative Update

• For Role, select Remote
• For Version, select 21.0.x.x BSP Update (Refer to Table 3-1 for the correct iDS/iDX
version number) from the drop-down list
3. Under Download Parameters pane, make certain Reset is NOT selected.
4. Click Start to download the cumulative package.
Progress displays in the Progress bar (lower left corner) and is indicated to the right of
each active remote by the word “Done” in the Status column (Figure 5-1). Watch for the
“PKG: Flash Completed” messages at the bottom of the Multicast Download window.
CAUTION: The progress bar displays “Download Unacknowledged” message
for those remotes that are not in the network.
CAUTION: Depending on the remote type, it may take 10 to 20 minutes to

completely flash its memory. Do not proceed until the memory flash is
complete. Monitoring the download progress and flash activity through the
Telnet session previously opened is recommended.
5. Repeat Steps 1-4 for every remote type in the network.
Procedure 2. Configure Ports Tab on iQDesktop Remotes

This procedure is required for all iQDesktop remotes in the network when upgrading to iDX
Release 4.1.0.4 and later. Starting with iDX Release 4.1.0.4, there is a new tab called “Ports”
available on the remote configuration page that must be configured for the iQDesktop
remotes. Please follow the “Configure iQDesktop Ports” section in the iDX 4.1.x iBuilder
User Guide document to configure all required ports on the iQDesktop remotes.
Procedure 3. Download Image Packages and Options Files

This procedure describes steps to update remote image packages along with the options files
and download them to all active remotes in the network.
1. In the Tree View, right-click on the Network icon, and select Package
The Multicast Download window displays (Figure 5-2 on page 35).
Figure 5-2. Multicast Download Window — Selecting Remote Package

• For Role, select Remote
• For Version, select 21.0.x.x (Refer to Table 3-1 for the correct iDS/iDX version
number) from the drop-down list
3. Under Download Parameters pane, make certain Reset is NOT selected.
CAUTION: When using the Multicast Download option, sets the download rate
to 400 Kbps or a lower value based on system calculation for the downstream
data rate.
*** DO NOT reset the remotes at this time***
4. Click Start to begin multicasting to the remotes.

Progress displays in the Progress bar (lower left corner) and is indicated to the right of
each active remote by the word “Done” in the Status column (Figure 5-2 on page 35).
Watch for the “PKG: Flash Completed” messages at the bottom of the Multicast
Download window.
CAUTION: Depending on the remote type, it may take 10 to 20 minutes to

completely flash its memory. Do not proceed until the memory flash is
complete. Monitoring the download progress and flash activity through the
Telnet session previously opened is recommended.
CAUTION: A known issue has been observed when updating the X1 remote.
After completing the software and option files download and flash, the X1
remote does not acknowledge with the “PKG: Flash Completed” message.
Instead, it acknowledges with the “Options: Flash Completed” message.
CAUTION: Depending on the number of X1 remotes that are active in the

network during the software upgrade, the event viewer window will be
flooded with the “Unexpected options file received” messages. This is only a
display issue and does not affect the X1 remote software upgrade.
5. Repeat this procedure for the other types of remotes in the network, until all remotes in
the network have downloaded the images.
6. When the software download to all active remotes is completed, close the Multicast
Download window.
Procedure 4. Reset The Remotes

CAUTION: Carefully follow the instructions in the next step when upgrading the
remotes. The “Push (UDP)” and “Reset on success” options must be selected
when upgrading them. Failure to select these options could cause the remotes to
not reset properly and become stranded (which will require a manual power-
cycling to re-acquire into the network).
After completing the software upgrade, use this procedure to reset all remotes that have
downloaded the new software in the network.
1. In the Tree View, right-click the Network icon, and then select Apply Configuration
Multiple.
The Automated Configuration Downloader window displays existing remotes, hub line
cards, and networks (Figure 5-3). In the Remotes area, iBuilder automatically selects the
affected remotes.
NOTE: On Global NMS configurations, uncheck all remotes that have an

“ELSEWHERE” status.
2. In the Automated Configuration Downloader window (Figure 5-3), from the Remotes
pane, select the following:
• Remote-side only
• Push (UDP)
• Reset on Success
Figure 5-3. Automated Configuration Downloader Window — UDP with Reset Option
3. Clear any selected check boxes in the Line Cards and Network areas. Optionally, any
ELSEWHERE remotes in the Remotes area can be unselected. [ELSEWHERE remotes will
be upgraded when upgrading the network to which they are currently assigned.]
4. Click Start to send the appropriate Options file to all of the remotes and reset them.
5. When the multiple configuration download to all active remotes is complete, close the
Automated Configuration Downloader window.
NOTE: In order to support link encryption for Evolution X1 and e150 remotes in
iDX Release 3.3, X.509 certificates are generated on all X1 and e150 remotes at
the time of the upgrade. This is a one-time event and can take as long as 20
minutes, during which time remotes with link encryption enabled cannot pass
data. Therefore, if link encryption is enabled for an X1 or e150 remote
immediately after the upgrade, there may be a time lag before the remote
becomes operational. Unencrypted traffic is not affected while the X.509
certificates are being generated.
CAUTION: Do not apply the changes to network configuration at this point.
Repeat “Chapter 5, Upgrade Remotes” for all remote types in each network before continue
to the next procedure.
This completes the Remotes portion of the network upgrade. Proceed to the next chapter for
instructions on upgrading the hub line cards.
6 Upgrade Hub Line Cards
This chapter contains the following procedures to successfully upgrade the hub line cards:
• Update ULC/DLC Image
• Procedure 1. "Download BSP Package"
• Procedure 2. "Download Image Package and Options File"
• Procedure 3. "Reset the Line Cards"
The cumulative update files and the update packages by type of hub line card for the current
release are listed in Table 6-1.
Table 6-1. BSP Update and Line Card Upgrade Packages
Type of Line Card BSP Update Package Line Card Package

Evolution Line card evo_hub_bsp-21.0.2.0 evo_hub-21.0.2.0
ULC/DLC Line Card N/A g4orce-rootfs-3.1.1.1-21.ppc-hub.pkg 1
1
Refer to procedure, Update ULC/DLC Image on page 40, for complete instructions to download and prepare the
ULC image on the NMS server.
NOTE: Table 6-1 only specifies the latest iDX/iDS Release software version
number for referencing purposes. Refer to Table 3-1 for the correct iDS/iDX
version number for the network upgrade.
NOTE: It is recommended to issue a UDP Reset to all “to-be-upgraded” line cards

prior to performing the procedures in this chapter. This is necessary to clear the
HLC’s RAM so that the software upgrade can be performed successfully.
Update ULC/DLC Image
CAUTION: This procedure is required for network upgrade to iDX Release 4.1.1
only. For network upgrades to previous iDX releases, please skip this procedure
and go directly to the next one.
This section provides all required steps to download and prepare the latest ULC/DLC image
(see Table 6-1 on page 39) prior to upgrading the ULC/DLC line cards.
2. Download the ULC/DLC image (see Table 6-1 on page 39) and transfer it to the /var/tmp
directory.
3. Go to /home/nms/cfg/image_sets/ulc_dlc_package directory
cd /home/nms/cfg/image_sets/ulc_dlc_package
4. Move the files in this directory to the /home/idirect/backup directory
mv * /home/idirect/backup
5. Copy the new ULC/DLC image from /var/tmp directory to
/home/nms/cfg/image_sets/ulc_dlc_package directory
cp /var/tmp/g4orce-rootfs-3.1.1.1-21.ppc-hub.pkg
/home/nms/cfg/image_sets/ulc_dlc_package
6. Update the file permissions
chmod a+rx g4orce-rootfs-3.1.1.1-21.ppc-hub.pkg
chown nms:nms g4orce-rootfs-3.1.1.1-21.ppc-hub.pkg
Procedure 1. Download BSP Package
NOTE: This procedure is applicable for XLC and eMxDx hub line cards only.
The BSP package is normally the first package to update the XLC and eMxDx hub line cards
firmware.
To download the BSP package, perform the following:
1. Launch iBuilder and log in as administrator.
2. In the Tree View in iBuilder, right-click the Network icon, and then select Package
DownloadTCP.
The TCP Download window displays (Figure 6-1).
Figure 6-1. TCP Download Window — Selecting BSP Updates for Hub Line Cards
3. In the Selection pane, select the following:

• For Hardware, select EvolutionLinecard
• For Role, select Hub
• For Version, select 21.0.0.0 BSP Update from the drop-down list
4. In the Options pane, select the following:
• Don’t check versions
• Don’t reset
5. Click Start to download the cumulative package.
Wait for the “Flash Completed” message in the Events Description column in the bottom
pane (Figure 6-1).
When the download is complete, go to the next procedure.
Procedure 2. Download Image Package and Options File
Now that the BSP package is completed, the line card image packages and options files can be
updated.
1. In iBuilder, in the Tree View, right-click the Network icon, and then select Package
DownloadTCP.
The TCP Download window displays (Figure 6-2).
Figure 6-2. TCP Download Window — Download Packages to Line Cards
2. In the Selection pane, select the following:

• For Hardware, select EvolutionLineCard
• For Role, select Hub
• For Version, select 21.0.x.x (Refer to Table 3-1 for the correct iDS/iDX version
number) from the drop-down list
3. In the Options pane, select the following:
• Don’t check versions
• Don’t reset
4. Click Start to download the software packages to the line cards.
Wait for the “Flash Completed.” message in the Events Description column in the bottom
pane (Figure 6-2 on page 42).
Procedure 3. Reset the Line Cards

After completing the software image upgrade, use this procedure to apply the configuration
and reset all active line cards in the network.
1. In the Tree View, right-click the Network icon, and then select Apply
ConfigurationMultiple.
The Automated Configuration Downloader window displays the remotes, hub line cards,
and the network (Figure 6-3 on page 43).
Figure 6-3. Automated Configuration Downloader Window — TCP with Reset Option
2. In the Line Cards area, select all line cards.

3. In the Protocol field, select Reliable (TCP).
4. In the Reset field, select Reset on Success (Figure 6-3).
5. Click Start to send the appropriate option files to all of the line cards.
Download progress is indicated to the right of each line card in the Status column.
When the multiple configuration download by Reliable (TCP) is completed, repeat Steps 2-4,
but this time select Push (UDP), as follows:
6. Verify that the line card was successfully upgraded by telneting into the line card and
issuing the following command:
version
7. When the multiple configuration download to all line cards is completed, close the
Automated Configuration Downloader window.
Repeat “Chapter 6, Upgrade Hub Line Cards” for each network before continue to the next
procedure.
CAUTION: Due to changes in the communication protocol between the Hub line
cards and Protocol Processor, all remotes and networks will be down at this point.
This is an expected result; all remotes will re-acquire into the networks after the
Protocol Processor is upgraded.
This completes the Hub Line Cards portion of the network upgrade. Proceed to the next
chapter for instructions on upgrading the PP Blades.
7 Upgrade iGateway and
PP Blades
CAUTION: For iGW (DVB-S2X) installation on a Dell PowerEdge R630 server, please
refer to Appendix C, R630 Server PP (DVB-S2X) Installation on page 79.
This chapter contains the procedures for successfully upgrading the Protocol Processor (PP)
Blades and/or iGateway servers:
• Upgrading Protocol Processor Blades

• Procedure 1. "Perform the PP Blade Upgrade"
• Procedure 2. "Restore the PP Configurations"
• Procedure 3. "Start PP Services"
• Upgrading iGateway in a DVB-S2X Network

• Procedure 1. "Perform the iGateway Upgrade"
• Procedure 2. "Verify iGW Software Version After Upgrade"
• Upgrading iGateway in a DVB-S2 Network

• Procedure 1. "Perform the iGateway Upgrade"
• Completing the Network Upgrade

• Procedure 1. "Remove the TLS 1.0 Support From NMS"
• Procedure 2. "Restart Remaining Services on NMS Server"
• Procedure 3. "Apply Configurations"
• Procedure 4. "Verify the Uplink Control Parameters"
• Procedure 5. "Rebalance Protocol Processor Blades"
• Procedure 6. "Restart Transmit Hub Line Cards (Optional)"
Upgrading Protocol Processor Blades
This section provides all necessary procedures to update a Protocol Processor running on Dell
PowerEdge R420, R610, and/or R630 servers.
CAUTION: If you are upgrading the iGateway server, then skip this section and go
directly to one of the following sections, depending on your network
configuration:
• Upgrading iGateway in a DVB-S2X Network on page 48
• Upgrading iGateway in a DVB-S2 Network on page 50
Procedure 1. Perform the PP Blade Upgrade

The upgrade software consists of the files downloaded in procedure “Download the Latest iDX
4.1.x.x Images” on page 16. The first file contains the ISO image, which contains all the files,
is needed to:
• Verify the upgrade media using the embedded MD5SUM and the checkisomd5 command
• Uninstall the old version of MySQL and install the new version of MySQL
• Install RHEL 6.8
• Install iDX Release 4.1.x.x PP software (Refer to Table 3-1 for the correct iDX/iDS version
number for the network upgrade).
• Update all RHEL, MySQL, and iDirect RPMs
1. Using WinSCP, copy the Kickstart ISO image downloaded previously from the TAC Web site
to the /var/tmp directory on the Protocol Processor.
2. Create a directory called /media/cdrom:
3. Mount the ISO image to the new directory using the following command:
Refer to Table 3-1 for the correct iDS/iDX version number.
4. Update the PP Blade using the following command:
/media/cdrom/iDirect/install/idsUpdate
NOTE: Use the --harden and --force options with the idsUpdate command
if SCAP compliance is required, for example: idsUpdate --harden --force
5. This upgrade may include RHEL 5.x changes that require a reboot to be effective. If this is
the case, the following error message displays:
One or more of the RPM’s selected for update will require that the
system be rebooted after update.
Update aborted! Specify option --reboot to update the system and reboot.
If this error message displays, execute the idsUpdate command again with the reboot
option:
6. After idsUpdate finishes executing, or after the server reboots, enter the following
commands:
umount /media/cdrom
7. Enter the following command to start PP services:
service idirect_hpb start
8. To configure the idirect_hpb service to start automatically at boot time, run the
following command:
chkconfig idirect_hpb on
Procedure 2. Restore the PP Configurations

This procedure is required to restore PP configuration along with any existing licensing files
which have been preserved previously in Chapter 3, Pre-Upgrade Tasks.
To restore the PP configuration and licensing files, perform the following:
1. Using WinSCP to transfer the backup file previously saved to the /tmp directory on the PP
server.
/usr/bin/idsRestore --bkup /tmp/<backup_file>
Where,
Procedure 3. Start PP Services

To start the PP services, perform the following:
1. Log in the NMS server as idirect user, then switch to root user.
2. Enter the following command to start PP services:
3. Configure the idirect_hpb service to start automatically at boot time using the following
command:
Upgrading iGateway in a DVB-S2X Network
This section provides all necessary procedures to upgrade an iGateway server running in a
DVB-S2X network.
NOTE: If the upgrading network does not have any iGateway servers, then skip all
procedures in this section. Go directly to section, Completing the Network
Upgrade on page 51, to continue the network upgrade.
For upgrading an iGateway server running in a DVB-S2 network, please skip this
procedure and go to Upgrading iGateway in a DVB-S2 Network on page 50.
Procedure 1. Perform the iGateway Upgrade

The upgrade software consists of the files downloaded in procedure “Download the Latest iDX
4.1.x.x Images” on page 16.
4. Using WinSCP, transfer the iGW software image downloaded previously from the TAC Web
site to the /home/idirect/upgrade directory on the iGateway VM host server.
5. Extract the iGW software image:
tar -xvf iDirect_IGW_EVO_S2X_upgrade-21.0.x.x.tar .
6. Verify the following files have been extracted from the iGW tar file:
• up-definitions.sh
• upgrade.py
• up-init-setup.sh
• vm-shutdown.sh
• vm-upgrade.sh
• rc-init-setup.sh
• recover.py
• vm-recover.sh
• packer-igw-rook-vm.xz
• packer-igw-pp-vm.xz
7. Upgrade the iGW using the following command:
./upgrade.py
Wait until the upgrade script finishes executing.
Procedure 2. Verify iGW Software Version After Upgrade
To verify iGW software version after the upgrade is successful, perform the following:
1. Switch to the virtualization interactive console:
virsh
2. Verify that all VM instances are running
list -all
A list of all VM instances will be displayed as shown in the example below.
virsh # list --all
Id Name State
----------------------------------------------------
13 b1-rook1 running
14 b1-pp-0 running
15 b1-pp-1 running
16 b1-pp-2 running
17 b1-pp-3 running
18 b1-pp-4 running
19 b1-pp-5 running
20 b1-pp-6 running
3. Exit out of the virtualization interactive console.
Exit
4. Verify the RPM version using the following steps:
a. Log into the PP
b. Issue the following command to verify the RPM version:
rpm -qa | grep protocol
The RPM version should be the latest software version (as shown in red in the example
below).
[root@localhost ~]# rpm -qa | grep protocol
protocol_processor-debuginfo-21.0.x.x-yyy.x86_64
protocol_processor-21.0.x.x-yyy.x86_64
[root@localhost ~]#
5. Verify the package version using the following steps:
a. Log into the Processing Node VM.
b. Issue the following command to verify the package version:
apt list rook-dpdk
A similar output should be displayed as shown below.
idirect@NeoniGW-rook1:~$ apt list rook-dpdk
Listing... Done
rook-dpdk/now 1.2.0.0-XXX amd64 [installed,local]
Upgrading iGateway in a DVB-S2 Network
This section provides all necessary procedures to upgrade an iGateway server running in a
DVB-S2 network.
NOTE: If the upgrading network does not have any iGateway servers, then skip all
procedures in this section. Go directly to section, Completing the Network
Upgrade on page 51, to continue the network upgrade.
For upgrading an iGateway server running in a DVB-S2X network, please skip this
procedure and go to section, Upgrading iGateway in a DVB-S2X Network on
page 48.
Depending on the iDX software release upgraded for the network, iDirect customers need to
upgrade the iGateway (iGW) server to the same software version being installed for the NMS
server. The vPPs and the NMS software versions must match for the vPPs to function.
NOTE: The procedure must be performed on every vPP nodes on the iGW server.
Procedure 1. Perform the iGateway Upgrade

To upgrade the vPP server, perform the following:
1. Using WinSCP, transfer the PP ISO Image file previously downloaded from the TAC Web
site to the /var/tmp directory on the iGW VM host server.
2. Log into the vPP (virtual machine) using SSH.
3. Create a directory called /media/cdrom:
4. Mount the ISO image to the new directory:
Where, 21.0.x.x represents the latest iDS/iDX version number that matches the NMS
software version.
5. Execute the idsUpdate script to start the PP software update:
6. After the server reboot, log back into the vPP
7. Enter the following command to start the PP services:
8. To configure the idirect_hpb service to start automatically at boot time, execute the
following command:
9. Repeat steps 1 through 10 for every vPP nodes on the iGW server.
Completing the Network Upgrade
This section provides all required procedures to complete the network upgrade.
Procedure 1. Remove the TLS 1.0 Support From NMS
NOTE: Perform this procedure is not applicable for iDX 4.1.0.1.
Since all network components have been upgraded successfully to the latest iDX Release
4.1.0.x, the environment variable previously set in Procedure 7. "Revert NMS to TLS 1.0" is no
longer needed. This environment variable must be removed from the nms_start
configuration file to disable TLS version older than TLS 1.2 to avoid security vulnerability of
older TLS versions.
2. Go to the /home/nms/utils directory using the following command:
cd /home/nms/utils
3. Use Vi editor to open the nms_start file using the following command:
vi nms_start
4. Remove the following environment variable for TLS underneath the “nmssvr)” section:
export USE_TLS1=1
5. Save the changes and close the file.
The “nmssvr)” section should look similar to the example shown below
nmssvr)
check_and_start "/home/nms/cfg/nmssvr" "--debug 4"
Procedure 2. Restart Remaining Services on NMS Server

1. Open a SSH session on the NMS server and restart all NMS services using the following
command:
service idirect_nms restart
2. Check to see the NMS services are running using the following command:
service idirect_nms status
All services should now indicate that they are running.
3. Configure the idirect_nms service to start automatically at boot time, using the following
command:
chkconfig idirect_nms on
4. If Automatic Beam Selection (ABS) is configured for the network, enter the following
commands to start the map service and to configure the NMS server to start the map
service on boot up:
service idirect_map start
chkconfig idirect_map on
NOTE: Refer to the Appendix on “Configuring Networks for Automatic Beam

Selection” of the iBuilder User Guide for iDX Release 4.1 for further
information to configure ABS.
Procedure 3. Apply Configurations

CAUTION: All remotes may not re-acquire into the network until this procedure is
completed.

1. Reload the configuration by right-clicking the protocol processor icon and selecting Apply
Configuration.
2. Right-click the network and select Apply ConfigurationMultiple.
The Automated Configuration Downloader window displays (Figure 7-1 on page 52).
Figure 7-1. Automated Configuration Downloader Window — Remote Hub-side

Configurations
3. In the Automated Configuration Downloader window, select all remotes.
4. For Target select Hub-side Only.
5. For Protocol, select Reliable (TCP).
6. For Reset, select Don’t Reset.
7. Under Network, select all networks.
8. Click Start to download the hub-side configurations.
All remotes will now start joining the network.
Procedure 4. Verify the Uplink Control Parameters

This procedure is required to verify the Uplink Control parameters for existing inroute groups
in the network after the network upgrade. Incorrect values for the Uplink Control parameters
may affect the ability of the remotes to operate in the network.
NOTE: The Uplink Control parameters given below are default values only. Refer
to the customer network design for the correct settings of these parameters.
The default values after the software upgrade should be:

• Fade Slope Margin (M1): 1.0 dB
• Hysteresis Margin (M2): 0.6 dB
• Acquisition Margin (M3): 2.0 dB (0.0 dB for homogeneous inroute groups)
• Measurement Spacing: 1000 ms (as shown in Figure 7-2).
Figure 7-2. Inroute Group — Uplink Control Configuration Parameters
Procedure 5. Rebalance Protocol Processor Blades

To ensure that all remotes loading across the protocol processor blade set are balanced,
perform a “blades rebalance” to distribute the remotes.
1. Open an SSH session to the Primary NMS using PuTTY.
2. Enter the following command at the root level command line prompt #:
ps -ef | grep pp
The output displays one line for each Protocol Processor running on the NMS.
For example:
root 25803 1 0 Jun06 ? 00:00:12 pp_controller -cp 15001 -lp 3001
3. Note the port number listed after -cp. In this example, the port number is 15001.
Accessing the Protocol Processor using Telnet will required this port number.
4. Open the Telnet session to that PP by issuing the following command:
telnet localhost <port#>
Where,
<port#> = the pp_controller port number.
5. Enter the credentials “admin” and “P@55w0rd!” to log in to the pp_controller.
6. To verify that all blades are up (no Sync Needed), enter the following command at the >
prompt:
blades status
CAUTION: If any PP blade is down, do NOT perform the PP blade rebalance.
7. Enter the following command at the > prompt:

blades rebalance all
A message displays confirming that the command was issued. View iMonitor and watch the
remotes get redistributed across the blades.
8. Repeat the process for each PP Controller that is listed on the NMS server.
Procedure 6. Restart Transmit Hub Line Cards (Optional)

NOTE: Perform this procedure only if there are any remotes not able to reacquire
into the network after they have been successfully upgraded to the latest
software release.
In rare situations, after the PP blades have been rebalanced, the transmit line card may get
out-of-sync with the PP blades causing the remotes to not acquire into the network. If this is
the case, resetting the transmit line card in the network helps to bring these remotes back in
the network.
To reset the transmit line card, perform the following:
1. In iBuilder, from the Tree View, expand the Network where the remotes have issues re-
acquire into the network,
2. Right-click on the transmit line card, select Reset Line CardReliable (TCP)
Wait for the transmit line card to completely reset, then verify that the remotes start to
reacquire into the network.
*** NETWORK DOWNTIME ENDS HERE ***
This completes the Protocol Processor portion of the network upgrade. Proceed to the next
chapter for instructions on upgrading the backup NMS server.
NOTE: If the NMS polling on the SatManage Server has previously been disabled,
then please use Procedure 2. "Enabling NMS Polling on SatManage Server" on
page 67 in Appendix A to re-enable the NMS polling.
8 Required Post-Upgrade
Tasks
NOTE: For any network upgrades to iDX Release 4.1.x.x from iDX Release 3.0 and
earlier, a new feature called NMS Database Replication introduced in iDX Release
3.1 may alter the idsBackup configuration and function of both Primary and
Backup NMS servers. Please refer to the iDX 4.1 Technical Reference Guide for
more information about this feature.
NOTE: All references to any IP address in this chapter are for illustration only.
Upon completion of the upgrade, there are some additional procedures that may be required
for specific environment. This chapter outlines these post-upgrade procedures that are
required to successfully complete the iDirect network upgrade.
• Procedure 1, Upgrade the Backup NMS Server

• Procedure 2, Verify the Upgrade has Completed Successfully
• Procedure 3, Verify Changes Pending on the Remotes and Incomplete Line Cards after the
Upgrade
• Procedure 4, Verify Chassis Configurations
• Procedure 5, Reconfigure the Crontab File on the NMS Servers
• Procedure 6, Rebuild NMS Database Replication (if applicable)
• Procedure 7, Verify the Backup is in Working Condition
• Procedure 8, Verify iDirect SNMP Configuration Working Settings (if applicable)
• Procedure 9, Determine If Any Remotes Still Out-of-Network
• Procedure 10, Software Upgrade/Install for X7 and 9-Series Remotes Second Partition
• Procedure 11, Remove the ISO Image From the /tmp Folder (Optional)
Procedure 1. Upgrade the Backup NMS Server
CAUTION: The Backup NMS server is about to be upgraded and everything will be
erased. Perform idsBackup as described in Backup NMS Server on page 20 to
preserve an archived copy of existing files on the Backup NMS server.
Upgrade the Backup NMS using the procedures outlined in Chapter 4, "Upgrading NMS Server"
on page 23 and using the database backup made by performing Procedure 11, "Backup NMS
Server" on page 20. However, do not execute the command chkconfig idirect_nms on to
start the nms service automatically at boot time.
1. Make sure that all services (including nms_config) are stopped:
service idirect_nms stop-all
2. Run this command to turn off all levels of services at boot time:
chkconfig idirect_nms off
3. Verify all levels of services are off at boot time using the following command:
chkconfig --list idirect_nms
A sample output indicating the all levels of service are off is shown here:
idirect_nms 0:off 1:off 2:off 3:off 4:off 5:off 6:off
Procedure 2. Verify the Upgrade has Completed Successfully

To verify that the upgrade is successful, confirm that all remotes have acquired into the
network and verify connectivity to the remotes. Performing load balancing across all PP
blades may be required, depending on how many remotes are in the network. Using a PC with
the new NMS client software installed to perform the following:
1. Launch iMonitor and log in as administrator.
2. Verify that all remotes have acquired into the network.
3. Check IP connectivity to the remotes and the functionality of all applications.
Procedure 3. Verify Changes Pending on the Remotes and

Incomplete Line Cards after the Upgrade
If remotes continue to show changes pending after the upgrade, compare the old and new
remote-side options files.
1. Right-click each remote in the iBuilder network tree and select Compare
ConfigurationsRemote-Side.
2. If configurations are the same, right-click the remote in the iBuilder tree and select
RetrieveActive Remote-Side Configuration to retrieve the remote-side options file.
Procedure 4. Verify Chassis Configurations
This procedure is required in consideration of the MIDAS chassis design change. Once the NMS
services have been fully restarted, all MIDAS chassis will show ‘Alarm’ state in iMonitor. This
state is according to the new design. All MIDAS chassis must be provisioned for the first time
by the HNO running the Chassis Manager SVR process.
Perform the following steps to ensure that all MIDAS chassis are provisioned properly:
1. Check and apply the configuration to each MIDAS chassis, once at a time.
2. If the MIDAS chassis configuration does not match the screenshot (previously preserved in
Section 2.4.2, Chassis Data Requirements on page 12), then turn the appropriate slots
ON/OFF to match the preserved configurations and apply the configuration changes.
3. Only after applying the configuration changes to the MIDAS chassis, will iMonitor show the
correct status on each chassis.
Procedure 5. Reconfigure the Crontab File on the NMS Servers

The crontab file must be restored to its pre-upgrade condition by removing the # signs in the
crontab file which was previously modified in Procedure 6, Preserve the SNMP Configurations
on page 17.
On the Primary and Backup NMS, perform the following:
1. Login to the Primary NMS server and switch to root.
2. Edit the crontab file using the command:
crontab -e
The crontab file opens in the Vi editor.
3. On the Primary NMS, remove the comment symbol (#) from the beginning of all lines in
the crontab file, except for this line:
#30 0 * * * /usr/bin/idsBackup --bkup /var/idirect/backup/\%ip-\%date --
keep 2
4. On the Backup NMS, remove the comment symbol (#) from all lines in the CRONTAB file,
except for this line:
keep 2
:wq!
Examples of the reconfigured CRONTABS are shown here:
On the Primary NMS:
keep 2
0 1 * * * /usr/bin/idsBackup --inst
[email protected]:/var/idirect/backup/\%ip-\%date --keep 2
0 0 * * * /opt/idirect/nms/utils/db_maint/cons.pl >>
0 4 * * 6 /opt/idirect/nms/utils/db_maint/check_db.pl >>
On the Backup NMS:
keep 2
6. Re-issue the SSHKeys on the Backup NMS using the following command:
pushSSHKeys <IPaddress>
Where,
<IPaddress> = the IP address of the backup NMS server.
For example:
pushSSHKeys 192.168.0.101
Pushing SSH key for user root to [email protected]:
[email protected]'s password:
SSH key for user root successfully pushed to [email protected]
On the Auxiliary NMS (applies to Distributed NMS Configuration), perform the following:
1. Log in to the Auxiliary NMS as idirect and switch to root.
2. Edit the crontab file using the command:
crontab -e
The crontab file opens in the Vi editor.
3. On the Auxiliary NMS, remove the comment symbol (#) from the beginning of all lines in
the crontab file, except for this line:
keep 2
4. Add the following line to the crontab file, replacing the IP address shown with the NMS IP
address — customized filename tokens may be used.
30 0 * * * /usr/bin/idsBackup --bkup /var/idirect/backup/\%ip-\%date --inst
:wq!
An example of an edited crontab file is shown here:
keep 2
30 2 * * * /usr/bin/idsBackup --bkup /var/idirect/backup/\%ip-\%date --inst
Procedure 6. Rebuild NMS Database Replication (if applicable)
NOTE: This procedure is required for any networks that are currently using the
NMS Database Replication feature, which was first introduced in iDX Release 3.1.
NOTE: Perform this procedure only if the Procedure 4, Disable the NMS Database
Replication Service on page 15 has been previously performed in preparation for
the network upgrade.
The NMS database replication is an iDX Release 3.1 feature that supports replication of NMS
databases from the Primary NMS server to one or more Backup NMS servers. When NMS
database replication is enabled, changes to the NMS databases on the Primary NMS are
automatically replicated to the Backup NMS server(s) using MySQL’s master/slave replication
tools. If the network has the NMS database replication feature enabled prior to the network
upgrade, then it is required that the feature must be reactivated using instructions in the iDX
4.1 Technical Reference Guide (available on the TAC Web site). Follow all steps in the NMS
Database Replication chapter of the iDX 3.5 Technical Reference Guide to reactivate the
feature, just as it was configured for the first time.
Procedure 7. Verify the Backup is in Working Condition

Perform the following steps to verify that the backup script is working and that the
appropriate backups are made on the Backup NMS server:
1. On the Primary NMS, copy the commands in the crontab file except for the time
information, paste them at the root prompt, and press Enter to run the command. Make
sure no error message is reported. Run a few times to ensure that two copies are kept.
The following sample output displays (the command displays in one continuous line):
/usr/bin/idsBackup --inst [email protected]:/var/idirect/backup/\%ip-
\%date --keep 2
Backing up (mysqldump): mysql DONE
Backing up database (mysqlhotcopy): nms DONE
Backing up database (mysqlhotcopy): nrd_archive DONE
Backing up database GRANTS: DONE
Backing up files and directories: DONE
Adding MySQL backups to archive: DONE
Compressing backup archive: DONE
Copying backup to:
[email protected]:/var/idirect/backup/192.168.0.100-2011.02.15-
15.29.58 DONE
Removing backup: 192.168.0.101:/var/idirect/backup/192.168.0.100-
2011.02.15-15.27.09 DONE
Installing backup on remote host: 192.168.0.101 DONE
2. On the Backup NMS, go to /var/idirect/backup directory using the following command:
cd /var/idirect/backup
3. Check whether the backup files updated correctly by checking the date of the backup
files. In this example, only the two latest versions are kept.
[root@Backup_NMS backup]# ll
-rw-r--r-- 1 idirect idirect 7686485 Feb 15 15:33 192.168.0.100-2011.02.15-
15.28.27
-rw-r--r-- 1 idirect idirect 7688771 Feb 15 15:35 192.168.0.100-2011.02.15-
15.29.58
[root@Backup_NMS backup]# date
Fri Feb 15 15:36:16 UTC 2011
For Distributed NMS only:
1. At the Auxiliary NMS root level command line prompt #, copy the command in the crontab
file except for the time information, paste in the root prompt, and press Enter to run the
command. Make sure no error message is reported. Run it twice to ensure that two copies
are kept.
[root@NMS_Aux ~]# /usr/bin/idsBackup --bkup /var/idirect/backup/\%ip-
\%date --inst [email protected]:/var/idirect/backup/\%ip-\%date --
keep 2
Backing up database (mysqldump): mysql DONE
Backing up database (mysqlhotcopy): nms DONE
Backing up database (mysqlhotcopy): nrd_archive DONE
Backing up database GRANTS: DONE
Backing up files and directories: DONE
Adding MySQL backups to archive: DONE
Compressing backup archive: DONE
Copying backup to:/var/idirect/backup/192.168.0.110- 2011.02.15-
15.40.50 DONE
2. On the Backup NMS, go to /var/idirect/backup folder using the following command:
cd /var/idirect/backup
3. Check whether the backup files updated correctly by checking the date of the backup
files. In the example shown below, only the two latest versions are kept.
[root@Backup_NMS backup]# ll
-rw-r--r-- 1 idirect idirect 7686485 Feb 15 15:33 192.168.0.100-
2011.02.15-15.28.27
2011.02.15-15.29.58
2011.02.15-15.40.22
2011.02.15-15.40.50
[root@Backup_NMS backup]# date
Tue Feb 15 15:55:01 UTC 2011
Procedure 8. Verify iDirect SNMP Configuration Working Settings
(if applicable)
Once the upgrade is complete, the working SNMP configuration must be restored.
To restore the working SNMP configuration, perform the following at the root level command
line prompt #:
1. From the /root directory of the NMS Server, go to the SNMP directory:
2. Check the current SNMP file (para_cfg.opt) to verify the settings as before:
cat para_cfg.opt
The following sample output displays:
[DB_PARM]
drvmgr_max = 20
[TRAP_PARM]
community = public
db_user_name = nms
Procedure 9. Determine If Any Remotes Still Out-of-Network

If the upgrade is completed and there are still some remotes that are out-of-network, start
the revsvr (Revision Server) and let it run to automate the upgrade for the out-of-network
remotes. Refer to the iBuilder User Guide for more information about the revsvr.
Procedure 10. Software Upgrade/Install for X7 and 9-Series

Remotes Second Partition
NOTE: The Evolution X7 and 9-Series remotes have two flash partitions from
which it can execute the software package. If one partition fails, the remote will
switch to the other partition. After performing the software upgrade for an
Evolution X7 and 9-Series remotes in Chapter 5, Upgrade Remotes on page 31,
iDirect highly recommends loading the X7 and 9-Series software packages a
second time to ensure that both partitions contain the correct software.
Using iBuilder, perform the following:

1. Select Package DownloadMulticast at the Network level of the iBuilder Tree.
2. Select the appropriate Remote package under Hardware in the Multicast Download dialog
box for:
• X7
• 9-Series
3. Ensure that all associated remotes in the network are selected in the Remotes section of
the Multicast Download dialog.
4. Ensure that Reset is not selected.
5. Click Start.
6. Wait for the software package download to complete.
7. Repeat steps 1 to 6 for the other remote type which has not been selected.
8. Click Close to close the Multicast Download dialog box.
This completes the procedure to upgrade the X7 and 9-Series remotes second partition. It is
not necessary to push the options file or reset the X7 and 9-Series remotes after the
procedure is completed.
Procedure 11. Remove the ISO Image From the /tmp Folder
(Optional)
NOTE: Perform this procedure only to save disk space on the NMS servers.
Otherwise, the ISO image may be saved for later use.
Now that the upgrade is complete, to save available disk space, iDirect recommends removing
the ISO CD/DVD image file from the /tmp directories on all NMS servers and PP Blades to
improve available disk space.
1. Log in to the Primary NMS and enter the following commands:
umount /media/cdrom
rm -f /tmp/IDS-21.0.x.x.iso
Refer to Table 3-1 for the correct iDS version number
Repeat this procedure for each NMS server and PP Blade in the network.
Appendix A SatManage
Integration
This appendix contains the procedures required to integrate SatManage to the newly
upgraded NMS servers. These procedures must be performed on every NMS after the software
upgrade (This includes Primary NMS and all NMS servers in a Distributed NMS configuration).
NOTE: The latest SatManage software version 5.3 recently released fully supports
iDX 3.3.x.x and earlier releases.
NOTE: The SatManage 5.2 does not fully support iDX 3.2.x.x and later releases.
Procedure 1. Disabling NMS Polling on SatManage Server

Before beginning the NMS upgrade, NMS data polling process needs to be disabled on the
SatManage server.
To disable the NMS data polling on the SatManage server, perform the following:
1. Connect to the satmanage_db database on the SatManage server using an MySQL client
software (such as Navicat, Figure A-1) with the user credentials: satadmin as user and
satadminpwd as password.
Figure A-1. SatManage Database Login Screen using Navicat
2. After successfully connected to the SatManage database, navigate to the Tables node and
open the IDIRECT_NMS table in edit mode by double clicking on the object with the same
name (Figure A-2).
Figure A-2. SatManage Database — IDIRECT_NMS Table
3. Modify the two columns enabled and enabled_autohd in the IDIRECT_NMS table to “n”
and commit the change (Figure A-3).
Figure A-3. SatManage Database — Disabling NMS polling
4. Close the SatManage Database connection and continue with the NMS upgrade.
Procedure 2. Enabling NMS Polling on SatManage Server
After the NMS server has been successfully upgraded, NMS polling needs to be re-enabled on
the SatManage server.
Perform the following steps to re-enable the NMS polling on SatManage server:
1. Connect to the satmanage_db database on the SatManage server using an MySQL client
software (such as Navicat, Figure A-1 on page 65) with the user credentials: satadmin as
user and satadminpwd as password.
2. After successfully connected to the SatManage database, navigate to the Tables node and
open the IDIRECT_NMS table in edit mode by double clicking on the object with the same
name (Figure A-2 on page 66).
3. Modify the two columns enabled and enabled_autohd in the IDIRECT_NMS database
table to “y” (Figure A-4).
Figure A-4. SatManage Database — Enabling NMS polling
4. Modify the column Version in the same database table to reflect the new iDirect software
version (Figure A-4). Refer to for the version string to be used for the new iDirect
software releases in Table A-1.
Table A-1. iDirect NMS software version - derived version string for SatManage
iDirect General Release Derived Version String

iDX 2.3 1110
iDX 2.3.1 1111
iDX 3.0 1200
iDX 3.1 1300
iDX 3.1.0.1 1301
iDX 3.1.0.3 1303
iDX 3.1.1.2 1312
iDX 3.2 * 1400
iDX 3.2.1 * 1410
iDX 3.2.2.4 * 1424
iDX 3.2.2.7 * 1427
iDX 3.2.3 * 1430
Table A-1. iDirect NMS software version - derived version string for SatManage
iDirect General Release Derived Version String

iDX 3.2.3.3 * 1433
iDX 3.3 * 1500
iDX 3.3.2.1 * 1521
iDX 3.3.2.2 * 1522
iDX 3.3.3.1 * 1531
iDX 3.3.4 * 1540
iDX 3.4.1 * 1610
iDX 3.4.3* 1630
iDX 3.5.1 * 1710
iDX 3.5.2 * 1720
iDX 3.5.3 * 1730
iDX 3.5.4 * 1740
iDX 4.0 * 2000
iDX 4.1 * 2100
* These iDX releases are not fully supported when integrating with SatManage software
version 5.2 and older releases
5. Commit the changes and close the SatManage database connection.
Procedure 3. Removing Latency Restriction on NMS Server

To save disk space on the NMS server, iDirect implements a latency threshold under which all
latency measures are to be discarded. This threshold limits SatManage ability to accurately
report latency information.
To modify the NMS to store all latency data for SatManage integration, perform the
following at the root level:
1. Log in to the NMS server as root user using SSH.
2. Go to /home/nms/utils folder
cd /home/nms/utils
3. Open the nms_start script using Vi editor
vi nms_start
4. Modify the latsvr section of the nms_start script by adding the line “export
ENV_LAT_ARCHIVE_THRESHOLD=0” as shown in blue text in the following example:
latsvr)
export ENV_DB_PARMS_FILE=”/home/nms/lat/para.opt”
export ENV_LAT_ARCHIVE_THRESHOLD=0
check_and_start “/home/nms/lav/latsvr”
:wq!
6. Restart the latsvr process for the changes to take affect
service idirect_nms restart latsvr
Appendix B R630 V-Server
NMS and PP Upgrade
This appendix contains the procedures required for upgrading both NMS and PP running on
Dell R630 server in Virtual Server mode. Note that, all procedures must be sequentially
performed as listed in this appendix. In case of any issue arises during the software upgrade,
contact TAC immediately for additional support.
This appendix contains the following major sections:
• Section B.1, Pre-Upgrade Tasks
• Section B.2, NMS Upgrade
• Section B.3, PP Upgrade
• Section B.4, Applying PP Performance Patch
B.1 Pre-Upgrade Tasks

This section describes all required tasks to be performed prior to the actual NMS and PP
software upgrade for the Dell R630 V-Server.
In order for the software upgrade to be successfully completed for the Dell R630 V-Server the
following tasks must be completed:
• The Host OS Ethernet Interface (eth3) must be configured with a valid IP address. This is
necessary for remote connectivities and file transfer.
• Procedure 6 through Procedure 11 in Chapter 3, Pre-Upgrade Tasks must be completed.
B.1.1 Installing MobaXterm Client for Remote Access

This section provides the instructions to install the MobaXterm application to use for remote
accessing to the Dell R630 V-Server. Currently, MobaXterm application is the only supported
remote access client for the Dell R630 V-Server.
1. Download the MobaXterm Client application using the following URL:
http://mobaxterm.mobatek.net/download.html
2. Install the MobaXterm Client application on your PC/laptop where you will be using to
remotely connect to the Dell R630 V-Server.
3. SSH to the Host OS (using eth3 IP address) on the Dell R630 V-Server using the MobaXterm
Client with the root user.
NMS Upgrade
B.2 NMS Upgrade

Use the MobaXterm client to SSH into Host OS (using eth3 IP address) on the NMS server and
perform all procedures described in Chapter 4, Upgrading NMS Server on page 23 on the
Guest OS.
CAUTION: When performing the NMS software upgrade for the Dell R630 V-Server,
be sure to perform the upgrade at the Guest OS, not the Host OS.
B.3 PP Upgrade
This sections describes all required procedures to update the PP software running on the Dell
R630 V-Server.
Procedure 1. PP Installation Using an ISO

To install the Guest OS and the iDirect software for the PP using an ISO image, proceed as
follow:
1. Copy ISO image (previously downloaded in procedure Download the Latest iDX 4.1.x.x
Images on page 16) to Host OS under /var/idirect.
2. SSH to the Dell R630 V-Server (Host OS) using the MobaXterm Client as the root user.
3. On the Host OS, open a terminal prompt by clicking ApplicationsUtilitiesTerminal.
4. Navigate to the /var/idirect folder.
cd /var/idirect
5. Install the PP server from the ISO.
./install.sh pp IDS-21.0.x.x.iso force
At this point, the Virtual PP Server instance has been created on the host machine. Continue
to Procedure 2 to update the default passwords for the Guest OS.
Procedure 2. Updating Passwords on the Guest OS

1. Log on to the Guest Virtual Server as root user (default password is iDirect) by selecting
the iDirect Console icon.
2. The root user is required to select a new password. Follow the prompt to update the
password.
3. As the root user, reset the idirect user password.
[root@PP] # passwd idirect
Changing password for user idirect.
New UNIX password: <new_idirect_password>
PP Upgrade
Retype new UNIX password: <new_idirect_password>

passwd: all authentication tokens updated successfully.
Where, <new_idirect_password> is the new password for the idirect user.
Continue to Procedure 3 to configure the IP address of the Guest OS.
Procedure 3. Updating PP Network Interface on the Guest OS

To configure the Guest on PP servers, perform the following:
1. From the Guest terminal console, navigate to the /etc/sysconfig/network-
scripts folder:
cd /etc/sysconfig/network-scripts/
2. From the Guest OS console, open and edit the ifcfg-eth0 file:
vi ifcfg-eth0
Figure B-1 shows the command lines in the ifcfg-eth0 file. Three of the command lines
must be changed; Table B-1 lists these lines.
Figure B-1. ifcfg-eth0 File
Table B-1. Protocol Processor ifcfg-eth0 File Entries
Command Description
BOOTPROTO static
GATEWAY IP address of the upstream router interface
PP Upgrade
Table B-1. Protocol Processor ifcfg-eth0 File Entries (continued)
Command Description
IPADDR PP blade upstream interface (eth0)
NETMASK Subnet mask of the PP Server
3. Modify the three lines in Table B-1. Do not change any other values and retain all other
lines within this file.
4. Open and edit the ifcfg-eth1 file:
vi ifcfg-eth1
Figure B-2 shows the command lines in the ifcfg-eth1 file. Two of the command lines
must be changed; Table B-2 lists these lines.
Figure B-2. ifcfg-eth1 File
Table B-2. Protocol Processor ifcfg-eth1 File Entries
Command Description
IPADDR PP Blade tunnel interface (eth1)
NETMASK subnet mask of the Protocol Processor Blade
5. Modify the two lines in Table B-2. Do not change any other values and retain all other
lines within this file.
6. To save the file and exit, press the Esc key and enter the following command:
PP Upgrade
:wq!
7. Return to the sysconfig directory:
cd /etc/sysconfig
8. Open and edit the network file:
vi network
9. Change the command lines in the network-scripts file as defined in Table B-3. Do not
change any other values and retain all other lines within this file.
Table B-3. Protocol Processor Host File Commands
Command Description
NETWORKING yes
HOSTNAME Company Name_PP_Primary
10. To save the file and exit, press the Esc key and enter the following command:
:wq!
11. Restart network service:
service network restart
12. Start network service at startup/reboot:
chkconfig network on
13. Configure the idirect_hpb service to start automatically at boot time:
Procedure 4. Restore the PP Configurations

This procedure is required to restore PP configuration along with any existing licensing files
which have been preserved previously in Chapter 3, Pre-Upgrade Tasks.
To restore the PP configuration and licensing files, perform the following:
1. Using WinSCP to transfer the backup file previously saved to the Guest OS /tmp directory
on the PP server.
/usr/bin/idsRestore --bkup /tmp/<backup_file>
Where,
PP Upgrade
Procedure 5. Setting the Date and Time on the PP Blades

1. Determine the time zone string for the location by entering the following command:
tzselect
The root@localhost:~ window displays.
2. Configure the time zone based on the physical location of the PP server.
3. Follow the menu prompts to select the site Continent or Ocean, Country, and Time Zone
Regions.
4. Write down the time zone string. For example:
TZ=’America/New_York’
5. Edit the /etc/sysconfig/clock file and change the ZONE variable the string value that
were recorded in the previous step.
6. Save and exit the file by pressing Esc and entering:
:wq!
7. Point the /etc/localtime file to the appropriate zoneinfo file by entering the following
command:
ln -s /usr/share/zoneinfo/<time zone string> /etc/localtime
Where,
<time zone string> = the time zone value that was recorded in Step 4.
For example,
ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
8. Reboot the server by entering the following command:
reboot
9. Verify that the server reboots and the time is set correctly.
10. Repeat this procedure for each PP Blade.
Procedure 6. Changing MTU Size on the PP for L2oS

iDirect supports Layer 2 over Satellite (L2oS). Traffic on an L2oS connection may be
segregated into Synthetic Virtual Networks (SVNs) by the use of VLAN or QinQ Service
Delimiting Tags (SDTs) in the Ethernet frames.
In order to support QinQ mode it is necessary to change MTU size to 1508. This requires
updating the MTU size on eth0 for both the Guest OS and the Host OS on the PP.
To change MTU size on the PP, perform the following:
1. In Guest OS, login as root user and execute:
service idirect_hpb stop
2. Modify ifcfg-eth0 config file using vi editor:
vi /etc/sysconfig/network-scripts/ifcfg-eth0
PP Upgrade
Change the MTU value from 1504 to 1508.

3. Save the file and exit by pressing Esc and entering:
:wq!
4. Login to Guest OS (PP) and shutdown the PP:
shutdown -a -t 0 "now”
5. Login to Host OS as root user and open a terminal prompt.
6. Open the KVM Hypervisor console:
virt-manager
7. Right-click on PP and select Shutdown and then Force Off to stop the VM instance.
8. From terminal prompt, modify ifcfg-eth0 script to change the MTU size to 1508:
vi /etc/sysconfig/network-scripts/ifcfg-eth0
Change the MTU value from 1504 to 1508.
9. Save the file and exit by pressing Esc and entering:
:wq!
10. Restart network services for the change to take effect:
11. Verify that the MTU has been updated to 1508 for the eth0 interface:
ifconfig eth0
12. Verify that the MTU has been updated to 1508 for the br0 interface:
ifconfig br0
13. Navigate back to KVM Hypervisor window, right-click on PP, and select Run to start the
virtual PP server.
14. Login to guest OS and verify the eth0 interface has the updated MTU size.
15. Start idirect_hpb services.
Procedure 7. Setting Up the DNS Server on the Guest (Optional)

This procedure describes how to set up DNS lookup on the PP.
1. Change directories by entering the following command:
cd /etc
2. Open and edit the resolv.conf file by entering the following command:
vi resolv.conf
This file contains default values for DNS IP addresses.
3. Update the resolv.conf file by changing the default values of the DNS IP addresses to the
applicable DNS IP addresses as defined by the network IP addressing schema.
Applying PP Performance Patch
B.4 Applying PP Performance Patch

This section provides steps to download and apply the TCP Fragmentation patch for the PP
server in KVM mode.
To download and install the PP Performance patch, perform the following:
1. Log in the TAC Web site (refer to Getting Help on page xiii).
2. Navigate to V-Server  R630 V-Server Software and Documentation Downloads
3. Click the KVM Performance Patch link to download the zipped file which consists of the
following files:
• README_KVM — contains the patch description and installation instructions for KVM
mode.
• kvm_scripts-82.tar.gz — a compressed file which consists of multiple scripts and
configuration files necessary for patching the PP server.
NOTE: The number in the patch file name indicates the control/version
number and may change for a future patch.
4. Use the README_KVM file for the complete instructions to install the patch.
Appendix C R630 Server PP
(DVB-S2X) Installation
CAUTION: This chapter is specifically for installing and configuring PP (DVB-S2X)

software on a Dell R630 PowerEdge server.
CAUTION: Swapping from DVB-S2 to DVB-S2X mode or vice versa is NOT possible.
To properly switch to the new mode, the server must be reinstalled.
CAUTION: Installing the PP software (in DVB-S2X mode) on an existing NMS/PP

server will overwrite all existing files and configurations of the NMS/PP server.
Starting with iDX Release 4.1.1, the Dell R630 PowerEdge server can be used to install the PP
(DVB-S2X) software. This chapter provides all necessary steps to install and configure a PP
(DVB-S2X) on a Dell R630 PowerEdge server.
Before performing the PP (DVB-S2X) installation and configuration on a Dell R630 server, the
following must be completed:
• Download the PP (DVB-S2X) ISO image file from the TAC Web site.
• Burn the PP (DVB-S2X) ISO image file as dd image to a flash drive using a 3rd-party tool
like Rufus.
Installing PP (DVB-S2X)
C.1 Installing PP (DVB-S2X)

1. Load the flash drive in the server then reboot the server.
2. Click F2 to enter the BIOS manager.
3. In BIOS mode, enter the System BIOS Settings, and change the boot mode from UEFI to
BIOS. Save the settings. See Figure C-1.
Figure C-1. Changing the BIOS Settings
4. Insert the USB that contains the PP (DVB-S2X) ISO image file in the USB slot of the blade.
5. During the reboot process, press F11  System Setup  One shot BIOS Boot Menu. The
user will be prompted to choose the Boot Device. Select Disk Connected to Front USB as
seen in Figure C-2.
Figure C-2. Changing the Boot Process
The iGateway installation is complete and the Host OS login prompt is displayed.
Once the installation is complete, the config-file.json file needs to be edited prior to
executing the setup.py script to deploy the configuration file.
6. Go to /home/idirect/install_scripts directory
7. Modify the config-file.json file to add IP addresses and host names for the following:
• PP (DVB-S2X) host machine
• Rook machine - VM
• PP server machine - VM
• Number of PP machines (#pp) — limited to 1.
NOTE: The parameter #pp is set to 1 only and does not require any IP
addresses.
A sample of the config-file.json is below

{
"host": {
"uip": "172.21.50.2/26",
"uip-gw": "172.21.50.1",
"dns": "172.20.2.98",
"hostname": "neon-igw-blade"},
"rook": {
"uip" : "172.21.50.30/26",
"tip" : "172.21.50.70/26",
"hostname": "Neon-rook1"},
"pp": {
"uip" : "172.21.50.31/26",
"tip" : "172.21.50.71/26",
"#pp" : 1,
"hostname": "Neon-pp"}
}
8. Execute the setup.py script (located in the /home/idirect/install_scripts directory) to
start the configuration process.
./setup.py -n
NOTE: The setup.py script will install the IP address provided by the user
during configuration and assign it to the PP VM.
The script takes around 90 seconds to complete execution and upon successful
completion, the prompt is displayed.
9. Once completed, login to the iGW host and verify that the VMs are created by executing
the following command
virsh list --all
The result should show 2 VMs (one rook and one vPP) in running state as similar to the
example shown below.
Figure C-3. Status of the Virtual Machines
10. Perform a network service restart from the iGW host

11. Confirm that all VMs have been successfully started and in running state by executing the
following command:
virsh list --all
NOTE: All VMs should be in running state.
13861 Sunrise Valley Drive, Suite 300
Herndon, VA 20171
+1 703.648.8000
+1 866.345.0983
www.idirect.net
Advancing a Connected World

NUP iDX35xx To iDX41 Non TRANSEC T0000954 RevF 07262018

Uploaded by

Copyright:

Available Formats

NUP iDX35xx To iDX41 Non TRANSEC T0000954 RevF 07262018

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NUP iDX35xx To iDX41 Non TRANSEC T0000954 RevF 07262018

Uploaded by

Copyright:

Available Formats

What is the purpose of the document?

What is the purpose of the document?

What steps are involved in upgrading the iGateway?

What steps are involved in upgrading the iGateway?

Network Upgrade Procedure

iDX 3.5.x.x to iDX Releases 4.1.x.x

July 26, 2018

Document Name: NUP_iDX35xx_To_iDX41_Non_TRANSEC_T0000954_RevF_07262018.pdf

Revision Date Updates

1 Read This First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2.3.2 Technical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 Upgrading NMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6 Upgrade Hub Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

7 Upgrade iGateway and PP Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

8 Required Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Appendix A SatManage Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Appendix B R630 V-Server NMS and PP Upgrade . . . . . . . . . . . . . . . . . . 71

Appendix C R630 Server . . . . . . . . . . . . PP (DVB-S2X) Installation79

Figure 1-1. Upgrade Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 1-1. Network Upgrade Checklist..................................................................... 3

Supported Upgrade Paths

Convention Description Example

WARNING: A Warning highlights an essential operating or maintenance

CAUTION: A Caution highlights an essential operating or maintenance procedure,

NOTE: A Note is a statement or other notification that adds, emphasizes, or

iDirect Contact Information:

iDirectGov Contact Information:

iDX 4.1.x.x Released Versions

iDirect software download instructions

To download any supplemental software, perform the following:

CAUTION: This Network Upgrade Procedure document is intended only for

Outage Window Upgrade Window Special Instruction

Run Pre-Upgrade Script

Remove or replace unsupported

Confirm distribution of PPS signal

Upgrade Hub Line Cards

Obtain NMS, Chassis, & Other Required Licenses

Upgrade the PP Server

Download the iDX 4.1.x.x ISO image

Check status of services

Modify the Crontab

Start all services on Primary NMS

Apply pending changes

Upgrade Backup NMS server

Perform Post-upgrade Steps:

Figure 1-1. Upgrade Flowchart

Table 1-1. Network Upgrade Checklist

 Complete and submit the iDX 4.1.x.x Upgrade/Installation Survey.

 Obtain all required license files as detailed in Section 2.3.1, "Administrative

 Complete technical requirements (see Section 2.3.2, "Technical Requirements" on page 9)

 Multicast Download Verification, perform multicast download of a BSP to remotes

 Schedule downtime with customer(s)

 Check Line Cards and Remotes for Custom Keys

 Check Network for Reserved Multicast Address

 Remove Old Entries in NRD_ARCHIVE Database

 Disable the NMS Database Replication Service

 Download the Latest iDX 4.1.x.x Images

 Preserve the SNMP Configurations

 Preserve the CM Configuration File