NUP NetworkUpgradeProc IDX21 and Later To 30 RevC 110311

Network Upgrade
Procedure Guide
iDX Release 2.1 and Later to iDX Release 3.0
November 3, 2011
Copyright © 2011 VT iDirect, Inc. All rights reserved. Reproduction in whole or in part without permission is
prohibited. Information contained herein is subject to change without notice. The specifications and information
regarding the products in this document are subject to change without notice. All statements, information, and
recommendations in this document are believed to be accurate, but are presented without warranty of any kind,
express, or implied. Users must take full responsibility for their application of any products. Trademarks, brand
names and products mentioned in this document are the property of their respective owners. All such references
are used strictly in an editorial fashion with no intent to convey any affiliation with the name or the product's
rightful owner.
Document Name: NUP_NetworkUpgradeProc_iDX21 and Later to 30_RevC_110311.pdf
Document Part Number: T0000382
ii Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0
Revision History
The following table shows all revisions for this document. Refer to this information to verify
that you have the latest version. If you do not have the latest version or you are unsure, you
can access the TAC web page at: http://tac.idirect.net and click on the Software Releases
link. You can then scroll down to the iDS release that is applicable to you and download the
latest version of this document.
Revision Date Released Reason for Change(s) Who Updated?

A June 9, 2011 First release of document TTheus
B July 14, 2011 Updated software file names TTheus
C November 3, 2011 Updated for iDX Release 3.0.0.1 TTheus
remote and hub line card
packages.
Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0 iii
iv Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0
Contents
About This Guide

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Supported Upgrade Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Contents Of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
1 Read This First!

What’s New in Upgrading to iDX Release 3.0? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Upgrade Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Upgrade Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Upgrade Prerequisites
2.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.1 Administrative Requirements and Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.2 Technical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4 Pre-Upgrade Data Capture Recommendations . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.1 Network Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.2 Remote Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Pre-Upgrade Tasks
Procedure 1 Check Line Cards and Remotes for Custom Keys . . . . . . . . . . . . . 13
Procedure 2 Download the iDX 3.0 Images . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0 v
Procedure 3 Modify the CRONTAB File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Procedure 4 Check the NMS Databases for Errors . . . . . . . . . . . . . . . . . . . . . 17
Procedure 5 Backup the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4 Upgrade the NMS Server

Procedure 1 Perform the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Procedure 2 Apply NMS License and Run Service Upgrade . . . . . . . . . . . . . . . 23
Procedure 3 Install the NMS Client Software (iBuilder/iMonitor) . . . . . . . . . . . 24
Procedure 4 Install the iDX Release 3.0.0.1 Remote Package Patch
on the NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Upgrading a Distributed NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5 Upgrade Remotes
Procedure 1 Reconfiguring TPC Inbound Carriers in DVB-S2 Networks . . . . . . . 29
Procedure 2 Perform a Multicast Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Procedure 3 Download the BSP Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Procedure 4 Download Software Packages to Remotes . . . . . . . . . . . . . . . . . . 33
Procedure 5 Apply the Configuration Options File . . . . . . . . . . . . . . . . . . . . . 36
6 Upgrade Hub Line Cards

Procedure 1 Replacing iNFINITI Hub Line Cards with
Evolution Hub Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Procedure 2 Download BSP Update Package . . . . . . . . . . . . . . . . . . . . . . . . . 42
Procedure 3 Download Line Card Packages . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Procedure 4 Apply the Configuration Options File . . . . . . . . . . . . . . . . . . . . . 46
7 Upgrade Protocol Processor Blades

Procedure 1 Upgrade the Protocol Processor . . . . . . . . . . . . . . . . . . . . . . . . 51
Procedure 2 Restart Remaining Services on NMS Server . . . . . . . . . . . . . . . . . 52
Procedure 3 Apply Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8 Upgrade the Backup NMS Server
9 Required Post-Upgrade Activities

Procedure 1 Verify that the Upgrade has Completed Successfully . . . . . . . . . . 57
Procedure 2 Verify Changes Pending on the Remotes and
Incomplete Line Cards after the Upgrade . . . . . . . . . . . . . . . . . . 59
Procedure 3 Reconfigure the crontab File on the NMS Servers . . . . . . . . . . . . 59
Procedure 4 Verify That the Backup is Working . . . . . . . . . . . . . . . . . . . . . . . 60
Procedure 5 Verify iDirect SNMP Configuration Working Settings (if applicable) . 62
Procedure 6 Verify If You Have Remotes Still Out-of-Network . . . . . . . . . . . . . 63
Procedure 7 Remove the ISO Image from the /tmp Folder . . . . . . . . . . . . . . . 63
vi Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0
Appendix A.. Obtaining IBM Server Information . . . . . . . . . . . . . . . 65
Appendix B.. Third-Party Software Options . . . . . . . . . . . . . . . . . 67

B.1 Third Party Software Bundled with IDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
B.1.1 iPerf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
B.1.2 EDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
B.1.3 PuTTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
B.2 Additional Third Party Software Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
B.2.1 WinSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
B.2.2 WinZip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0 vii
viii Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0
List of Figures
Figure 1. Upgrade Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 2. Select Package DownloadMulticast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 3. Multicast Download Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 4. Multicast Download—Downloading the Cumulative Update . . . . . . . . . . . . . . . . . . 32
Figure 5. Multicast Download Window—Selecting Remote Package . . . . . . . . . . . . . . . . . . . 34
Figure 6. Select Apply ConfigurationMultiple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 7. Automated Configuration Downloader Window—TCP with Don’t Reset Option . . . . . 37
Figure 8. Automated Configuration Downloader Window—UDP with Reset Option . . . . . . . . . 38
Figure 9. Selecting Package DownloadTCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 10. TCP Download Window—Selecting BSP Updates for Hub Line Cards . . . . . . . . . . . 43
Figure 11. TCP Download Window - Download Packages to Line Cards . . . . . . . . . . . . . . . . 45
Figure 12. Automated Configuration Downloader Window—TCP with No Reset Option . . . . . . 47
Figure 13. Automated Configuration Downloader Window—Push UDP with Reset Option . . . . . 48
Figure 14. Automated Configuration Downloader Window—Remote Hub-side Configurations . . 53
Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0 ix
x Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0
About This Guide
This chapter includes the following sections:

• Intended Audience
• Supported Upgrade Paths
• Contents Of This Guide
• Document Conventions
• Related Documents
• Getting Help
Intended Audience
The purpose of this guide is to assist iDirect network operators, iDirect network architects, or
any other personnel to successfully upgrade from iDX Release 2.1 and later to iDX Release 3.0.
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.
Supported Upgrade Paths

The following upgrade paths from iDX Releases 2.1 and later to iDX Release 3.0 are supported:
• iDX 2.1.x
• iDX 2.2.x
New installations are also supported. See the Software Installation Guide for New Hubs for
this release for instructions (available on the TAC web page at http://tac.idirect.net).
Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0 xi
Contents Of This Guide
This guide outlines procedures for upgrading the iDirect Network Management Software (NMS)
and the Protocol Processor (PP) software. It also covers upgrading all of the remotes and hub
line cards on your iDirect network(s).
This guide contains the following chapters and appendixes:
• Chapter 1, Read This First!
• Chapter 2, Upgrade Prerequisites
• Chapter 3, Pre-Upgrade Tasks
• Chapter 4, Upgrade the NMS Server
• Chapter 5, Upgrade Remotes
• Chapter 6, Upgrade Hub Line Cards
• Chapter 7, Upgrade Protocol Processor Blades
• Chapter 8, Upgrade the Backup NMS Server
• Chapter 9, Required Post-Upgrade Activities
• Appendix A, Obtaining IBM Server Information
• Appendix B, Third-Party Software Options
Document Conventions
This section illustrates and describes the conventions used throughout the manual. Take a
look now, before you begin using this manual, so that you’ll know how to interpret the
information presented.
Convention Description Example

Blue Used when the user is [SWITCH_PORT_n]
Courier required to enter a vid = vlan_id
font command at a command
line prompt or in a console
Courier Used when showing Output similar to the following sample appears:
font resulting output from a [SECURITY]
command that was entered password =
at a command line or on a
$idi2$/bFMhf$5H8mYAaP1sTZ0m1Ny/dYyLaS40/
console.
admin_password =
$idi2$146rgm$.KtDb4OH5CEBxzH6Ds2xM.ehHCH
os_password =
$1$UTKh0V$cc/UfNThFmBI7sT.zYptQ0
xii Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0
Convention Description Example
Bold Used when the user is If you are adding a remote to an inroute group,
Trebuchet required to type right-click the Inroute Group and select Add Remote.
font information or values into a
field within a windows-type
The Remote dialog box has a number of user-
interface software.
selectable tabs across the top. The Information Tab is
visible when the Dialog opens.
Used when specifying
names of commands,
menus, folders, tabs,
dialogs, list boxes, and
options.
Blue Used to show all For instructions on adding an iSCPC line card to the
Trebuchet hyperlinked text within a network tree and selecting a Hub RFT for the line card,
font document. see “Adding an iSCPC Line Card” on page 108.
Bold italic Used to emphasize Note: Several remote model types can be
Trebuchet information for the user, configured as iSCPC remotes.
font such as in notes.
Red italic Used when the user needs

Trebuchet to STRICTLY follow the
font instructions or have WARNING! The following procedure may cause
(or see additional knowledge about a network outage.
table a procedure or action.
below)
Symbol Warning type Definition
CAUTION: When you see this alert symbol and

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

WARNING this symbol and the WARNING
heading, strictly follow the warning
instructions to avoid electric shock
injury.
STOP! When you see this STOP sign, take heed

STOP of the notice information that is
presented. It provides critical
information that you need to know
before proceeding.
Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0 xiii
Related Documents
The following iDX Release 3.0 related documents are available for download from the TAC
web page at http://tac.idirect.net under the Software section. Refer to these documents as
needed or as indicated within this guide.
• Release Notes
• Upgrade/New Installation Survey
• Software Installation Guide for New Hubs
• iBuilder User Guide
• iMonitor User Guide
• Technical Reference Guide
• Satellite Router Commissioning & Installation Guide
• Features & Chassis Licensing Guide
• Link Budget Analysis Guide
Getting Help
The iDirect Technical Assistance Center (TAC) is available to help you 24x7x365. If you are
unable to find the answers or information that you need in this upgrade guide, you are
encouraged to contact the TAC at (703) 648-8151.
iDirect strives to produce documentation that is technically accurate, easy to use, and helpful
to our customers. Your feedback is welcomed! Send your comments to techpubs@idirect.net.
xiv Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0
1 Read This First!
This chapter contains essential information needed to perform a successful upgrade to

iDX Release 3.0. This guide provides detailed checklists of steps and procedures for upgrading
to iDX Release 3.0 and preserving your existing NMS network configuration (and database) to
use with your new iDX Release 3.0 network.
This chapter contains the following sections:
• What’s New in Upgrading to iDX Release 3.0?
• Upgrade Flowchart
• Upgrade Checklist
What’s New in Upgrading to iDX Release 3.0?

New Upgrade Process
Beginning with iDX Release 2.1.0, the upgrade uses the Redhat Kickstart process to install
RedHat Enterprise Linux (RHEL) release 5.6, MySQL 5.1.46, and either the iDirect NMS or
Protocol Processor server software. Subsequent iDX releases use the same Kickstart method to
upgrade RHEL patches, MySQL and iDirect products on an existing iDirect configured RHEL 5.6
system.
Separate Kickstart menu entries are available to build the following system configurations:
• NMS Server — use this option when upgrading your NMS server(s)
• PP Server — use this option when upgrading your Protocol Processor server(s)
• Standalone iDirect Update Server — The iDirect Standalone Update Server can be
configured to support “pushing” iDirect server upgrades to any other network-connected
iDirect server. This facility allows you to use the normal upgrade procedures to upgrade a
single iDirect server, then use that server to “push” those updates (RHEL, MySQL and IDS)
appropriate to all or selected other iDirect NMS or PP servers. This option is for future use
only.
• GKD (Global Key Distribution Server) — A Global Key Distribution Server is not required to
complete the upgrade. After completing the upgrade, if you wish to install one or more
GKDs to generate and synchronize the ACC Keys for your TRANSEC networks, you can do so
by selecting this option. See the appendix on TRANSEC in the iBuilder User Guide for this
release for more information about installing and using GKD Servers.
Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0 1
2D 16-State Coding Conversion — Starting in iDX Release 3.0, TPC inroutes (and therefore all
iNFINITI hub line cards) are no longer supported with DVB-S2 outbound carriers. As part of this
upgrade, you will migrate your carrier configuration from TPC to 2D 16-State coding.
STOP! The Kickstart installation erases all data on the target

system! Before installing the new operating system, you
will be guided through a procedure in which your entire
system will be backed up to one or more external devices
and restored in a later procedure.
Supported Upgrade Paths

The following upgrade paths from iDX Release 2.1.x and later to iDX Release 3.0 are
supported:
• iDX 2.1.x
• iDX 2.2.x
New installations are also supported. See the Software Installation Guide for New Hubs for
this release for instructions (available on the TAC web page at http://tac.idirect.net).
Protocol Processor (PP) License for Link Encryption and

TRANSEC
Beginning with iDX Release 2.1, a PP blade license is required for Link Encryption and
TRANSEC. This license is requested from the iDirect TAC based on information you provide in
the iDX 3.0 Upgrade/New Installation Survey (available from http://tac.idirect.net).
Instructions for installing the encryption license on your PP blade are provided in this guide
and the iDirect Features and Chassis Licensing Guide. This Network Upgrade Procedure
informs you at what point during the upgrade process you should install the PP blade license.
If you are using high speed Comms on the Move (COTM) or Spread Spectrum, you will also
need license files for these features.
New “idirect” User

As part of the new installation process, you can no longer SSH into the target machine as the
root user. To support SSH access to this machine, an idirect user has been added to each
server installation. By default, the idirect user’s password is “iDirect”. At your first login, the
idirect user is required to select another password.
You have to SSH in as the idirect user and then switch user (“su -”) to root. Be sure to use the
hyphen after the “su” command in order to invoke all the root user privileges.
For example:
[idirect@primary_nms ~]$ su -
Password: <password>
[root@primary_nms ~]#
2 Network Upgrade Procedure Guide for iDX Release 2.1 and Later to iDX 3.0
Upgrade Flowchart
Study Figure 1 on page 4 to determine which upgrade scenario process best applies to your
situation. You can detach the flowchart on the following page from this guide and use it for
reference while performing the upgrade.
Figure 1. Upgrade Flowchart
Upgrade Checklist
This section provides an upgrade checklist to use for reference while performing the upgrade
steps. The steps in your upgrade can differ depending on which version of iDirect software
currently exists on the target server machine, and which models of hub line cards and
remotes are currently configured in your network.
The checklist shown in Table 1 can be detached from this guide and used as a reference while
performing the upgrade.
Execute the procedures and steps that apply to your upgrade in the order in which they are
presented in the checklist.
STOP! The upgrade checklist contains optional steps that only

apply to specific network hardware or specific software
versions. Carefully follow only the tasks and procedures
that apply to your network in the upgrade checklist.
Table 1. Network Upgrade Checklist

Perform Prerequisites
 Notify iDirect, complete and submit the iDX 3.0 Upgrade/Installation

Survey.
 Obtain all required license files from iDirect as detailed in Section 2.3.1,
"Administrative Requirements and Licensing" on page 10.
• 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 11)
 Perform multicast download of a BSP to remotes (without reset) to verify

multicast download capability
 Gather required data from your 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 you have any custom keys
Perform Pre-Upgrade Activities
 Check Line Cards and Remotes for Custom Keys
 Download the iDX 3.0 Images
Table 1. Network Upgrade Checklist (continued)
 Modify the CRONTAB File
 Check the NMS Databases for Errors
Backup Existing Configurations and Data
 Run idsBackup for all servers and save your backups to multiple, safe
locations
Upgrade NMS
 Perform the Upgrade
 Apply NMS License and Run Service Upgrade
 Install the NMS Client Software (iBuilder/iMonitor)
Upgrade Remotes on Your Network
 Consult with the TAC if you have any custom keys
 Perform a Multicast Test
 Download the BSP Update
 Download Software Packages to Remotes
 Apply the Configuration Options File
Upgrade Hub Line Cards
 Replacing iNFINITI Hub Line Cards with Evolution Hub Line Cards
 Download BSP Update Package
 Download Line Card Packages
 Apply the Configuration Options File
Upgrade Your Protocol Processor Blades
 Upgrade the Protocol Processor
 If you are using Link Encryption or TRANSEC, install PP Encryption License
 Restart Remaining Services on NMS Server
 Apply Configurations and the Remote Hub-side Configuration
Upgrade the Backup NMS Server


Required Post-Upgrade Activities
 Verify that the Upgrade has Completed Successfully
Table 1. Network Upgrade Checklist (continued)
 Verify Changes Pending on the Remotes and Incomplete Line Cards after
the Upgrade
 Reconfigure the crontab File on the NMS Servers
 Verify That the Backup is Working
 Verify iDirect SNMP Configuration Working Settings (if applicable)
 Verify If You Have Remotes Still Out-of-Network, enable the Revision

Server until all remotes are recovered.
2 Upgrade Prerequisites
This chapter contains system requirements, data gathering requirements, and important
prerequisites for upgrading from iDX Release 2.1 and later to iDX Release 3.0.
• System Requirements
• Hardware Requirements
• Prerequisites
• Pre-Upgrade Data Capture Recommendations
STOP! NetModem and NetModem II Plus remotes and NetModem

II+ Universal Line Cards are not supported in this release.
STOP! If you have any custom keys defined, especially on the

remotes, contact the TAC to determine if the custom keys
are valid in this release.
Upgrade Prerequisites
2.1 System Requirements

iDirect’s NMS clients (iBuilder, iMonitor, and iSite) are Windows PC-based applications that run
under the following releases of Windows:
• Windows 2000 Workstation, Service Pack 3 or later
• Windows XP Workstation
• Windows 7
Note: Windows Vista, Windows NT, Windows 98 and Windows 95 are not supported.
2.2 Hardware Requirements

For client laptops or PCs, the following hardware specifications are recommended:
• Dual core processor, 2.8 GHz or better, 2 Gig RAM, 1Gig free disk space
Commencing with iDX Release 2.1, the following server hardware is supported:
• IBM eServer xSeries 336
• IBM System x3550
• Augmentix A+R200 (industrialized)
• Dell PowerEdge 1950 III
• Dell PowerEdge R610
Note: Starting with the iDX Release 2.1, IBM 335 servers are no longer supported.
2.3 Prerequisites
You must complete a number of tasks prior to performing an upgrade 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 your networks prior to the 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 affect the upgrade process, post-upgrade network recovery, or
post-upgrade network status.
2.3.1 Administrative Requirements and Licensing

This section lists the required administrative tasks that must be performed prior to the
upgrade.
• 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 you wish to use Link Encryption or TRANSEC, 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 required to generate all required license files is captured
in the iDX Release 3.0 Upgrade/Installation Survey.
2.3.2 Technical Requirements

This section lists the required technical tasks that must be completed prior to your upgrade.
• Obtain access to the TAC web page to download the files required for the upgrade.
• On each of your remotes, 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 3.0 before
other chassis can upgrade to iDX 3.0.
• iDirect strongly recommends performing a multicast download of a BSP package or a
remote package (of your current release) to all remotes on your network in order to
verify the multicast package download capability. This test can be performed without
resetting remotes, so you can be perform this test days prior to the upgrade maintenance
window. Although the multicast download will use as much as 10% of your downstream
bandwidth during the test, performing this verification will ensure your 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.
2.4 Pre-Upgrade Data Capture Recommendations

This section outlines tasks that iDirect strongly recommends you execute prior to the
upgrade.
2.4.1 Network Data Requirements

This section describes the required data that you should extract from the network prior to an
upgrade.
• 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.
• In iBuilder:
– Verify that the transmit powers of your Hub Tx line cards match the configurations in
the line card options files. If not, make the necessary configuration changes. See the
iDX Release 3.0 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 to each inroute group and which line cards are
assigned to which hub chassis slot.
STOP! Starting in iDX Release 3.0, TPC inroutes (and therefore
all iNFINITI receive hub line cards) are no longer
supported with DVB-S2 outbound carriers. As part of this
upgrade, you will migrate your carrier configuration from
TPC to 2D 16-State coding. Make sure you have recorded
the hub line card and inroute carrier group assignments
before continuing.
• In 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 Remote Data Requirements

This section describes the required data to extract from your remotes prior to an upgrade.
Make sure you retain this data to ensure your 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 3.0. The procedures in this chapter prepare your network for an upgrade to iDX 3.0.
Before you begin these procedures, download and review the iDX Release Notes 3.0. In the
Release Notes, note any special instructions that need to be performed before and during the
upgrade process.
This chapter contains the following pre-upgrade procedures:
• Procedure 1, "Check Line Cards and Remotes for Custom Keys" on page 13
• Procedure 2, "Download the iDX 3.0 Images" on page 15
• Procedure 3, "Modify the CRONTAB File" on page 16
• Procedure 4, "Check the NMS Databases for Errors" on page 17
• Procedure 5, "Backup the Database" on page 18
STOP! If you encounter any problems during these procedures,

do not continue the upgrade. Contact iDirect’s Technical
Assistance Center (TAC) at (703) 648-8151 immediately
for assistance.
Procedure 1. Check Line Cards and Remotes for Custom Keys

Before applying custom keys to Evolution line cards and remotes as outlined in Procedures 2
and 3, 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.
1. From the TAC web page (http://tac.idirect.net), navigate to the iDX 3.0 software section
and download the checkcksh.gz file.
2. Using WinSCP, copy the file to the NMS server’s /tmp directory.
3. Logon to the NMS server and go to the /tmp directory.
The # symbol indicates that you are at the root level command line prompt. Enter the
remaining commands in this procedure from this level.
4. Unzip the checkcksh.gz file:
Pre-Upgrade Tasks
gunzip checkcksh.gz
5. Make the script executable:
chmod 755 checkcksh
6. Run the script and write the resulting data to an output file named check_ck.output by
entering the following command:
./checkcksh >check_ck.output
7. Organize the results by entering the following command:
sort check_ck.output
An example of the script commands and its output is shown below.
# ./checkcksh >check_ck.output
# sort check_ck.output
Remote "3100 59542" (NW=3 did=5040278) has hub side Custom Keys
Remote "5350 41462" (NW=2 did=6857206) has remote side Custom
Keys
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=1 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
Pre-Upgrade Tasks
8. Using iBuilder, remove any custom keys that you identified in Chapter 2, Upgrade
Prerequisites on page 9.
Procedure 2. Download the iDX 3.0 Images

Before starting the upgrade process, you need to download the images for this release from
the TAC web page.
To download the images:
1. Create a temporary folder on the PC or laptop’s desktop.
2. Using your iDirect login name and password, log on to the iDirect Technical Assistance
Center web site, located at: http://tac.idirect.net/.
3. In the By Product section, click Software.
4. Navigate to iDX 3.0.
5. Click to download each of the required files to the folder created in Step 1. These files
include:
• iDX 12.0.0.0-390_NMS_PP.iso — Kickstart DVD image
Note: Starting with iDX Release 2.1, both NMS and PP images are merged into a
single .iso image.
• Patches may also be part of the release to which you are upgrading. Ensure that you
also download any related patch software for that 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.
6. Navigate to Supplemental Releases.
7. Click the link Pre-UpdateCheck, DB Check & Repair Tools in Tgz Format to download
the check and repair scripts (in compressed tgz format).
Save the iddb_tools.tgz file to your desktop or other location.
8. In addition, iDirect recommends that you download the following iDX Release 3.0
documents to assist in your upgrade process:
• iMonitor User Guide
• iBuilder User Guide
• Release Notes
• iDirect Features and Chassis Licensing Guide
Pre-Upgrade Tasks
Procedure 3. Modify the CRONTAB File

You must prevent activation of the idsBackup and idsRestore scripts on both the primary NMS
and the backup NMS during the upgrade procedure. To do this, add the comment symbol (#)
to the beginning of all lines in the CRONTAB file.
Perform the following at the root level command line prompt #:
1. Open two PuTTY sessions and logon to both the Primary NMS and the Backup NMS.
2. To edit the CRONTAB file, login as root and 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. To save the changes to the file and exit, press Esc and enter the following command:
:wq!
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:
#00 1 * * * (export macAddr=`/sbin/ifconfig eth0 | grep HWaddr | sed
"s/^.*HWaddr //; s/ .*$//;"` && /opt/idirect/install/idsBackup -
host local --keep 2 && cd /var/idirect/backup && export bkupDir=`ls
-d $macAddr*.d | sort | tail -1` && tar cf - $bkupDir | ssh
idirect@192.168.77.33 "( cd /var/idirect/backup; tar xfp - ; sudo
/opt/idirect/install/idsRestore -host local --bkup $bkupDir -noNet
-noHostCfg && ls -d /var/idirect/backup/$macAddr*.d | sort | head -
-lines=-2 | xargs rm -rf; )") >/tmp/daily_bkup.output 2>&1
#30 0 * * * /opt/idirect/install/idsBackup -host local --keep 2

>/dev/null 2>&1
#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
On the Backup NMS:

>/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 >>
Pre-Upgrade Tasks
Procedure 4. 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 3.0 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 at the root level command line prompt #:
1. Log on to the Primary NMS server using SSH (PuTTY).
2. Stop the NMS server process by entering the following command:
service idirect_nms stop
3. Using WinSCP, copy the iddb_tools.tgz file (downloaded during Procedure 2, "Download
the iDX 3.0 Images", Step 7) to the /root directory on the Primary NMS Server.
4. Change to the /tmp directory by entering the following command:
cd /tmp
5. Unzip the database repair tools by entering the following command:
tar zxvf iddb_tools.tgz
6. Make the file executable by entering the following command:
chmod 755 iddbrepair.sh
7. Repair any faulty database tables by entering the following command:
./iddbrepair.sh
Note: The execution time of this command varies with the size of your database.
For a large database, it can take as long as one hour for the command to
complete.
8. Check for any merge tables or InnoDB tables in the database by entering the following
commands:
chmod 755 preUpdateCheck
./preUpdateCheck
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:
Pre-Upgrade Tasks
Specify "--convertInnoDB" to convert these tables to MyISAM

tables
STOP! If any InnoDB or merge tables are found in your database,

stop the upgrade and call the TAC at (703) 648-8151 for
further instructions.
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.
MySQL appears to be running but PID file does not match hostname:
If either of these messages displays, reboot MySQL by entering the following command:
./preUpdateCheck --restartMySQL
9. If you are proceeding with the upgrade at this time, continue to Procedure 5, "Backup the
Database". If you are not performing the upgrade at this time, restart the NMS services by
entering the following command:
service idirect_nms start
Procedure 5. Backup the Database

During the update from iDX Release 2.1 and later to iDX Release 3.0, all data will be
preserved. For best practices however, iDirect recommends that you manually run the
idsBackup script and save the backup file to an external, safe location (such as your PC or
laptop) before upgrading.
To backup your database, perform the following at the root level command line prompt #:
1. Logon to the Primary NMS server as root.
2. Using WinSCP, transfer the Kickstart ISO image that you downloaded from the TAC web
page to a temp directory on your primary NMS.
3. Create a directory called /media/cdrom by entering the following command:
mkdir -p /media/cdrom
4. Go to the var/idirect/backup directory by entering the following command:
cd /var/idirect/backup
5. Mount the image by entering the following command:
mount -o loop /tmp/IDS-12.0.0.0-390.iso /media/cdrom\
Pre-Upgrade Tasks
6. Run idsBackup by entering the following as one command (press Enter after the “\”
symbol at the end of the first line:
/media/cdrom/iDirect/install/idsBackup --keep 2 --bkup \
/var/idirect/backup/\%ip-\%date
Note: In this command, you must enter “%ip” and “%date” exactly as shown. Do
not substitute them for an actual IP address or date. The IP address and
current date/time of your server are automatically poulated when you
execute this command.
7. Use WinSCP to copy the archived backup file to an external, safe location such as your PC.
8. Unmount the image by entering the following command:
umount /media/cdrom
This completes the pre-upgrade tasks. Proceed to the next chapter for instructions on
upgrading your NMS servers.
Pre-Upgrade Tasks
4 Upgrade the NMS Server
Before upgrading the NMS servers, be sure you have backed up and saved the compressed file
for all of your NMS servers data as described in Procedure 5. Backup the Database on page 18.
Make sure you have copied the backup archive file to one or more safe locations, other than
on the servers you are upgrading.
• Procedure 1. Perform the Upgrade
• Procedure 2. Apply NMS License and Run Service Upgrade
• Procedure 3. Install the NMS Client Software (iBuilder/iMonitor)
• Procedure 4. Install the iDX Release 3.0.0.1 Remote Package Patch on the NMS
• Upgrading a Distributed NMS
Note: For upgrading a Backup NMS, see Chapter 8, "Upgrade the Backup NMS Server"
on page 55.
Procedure 1. Perform the Upgrade

The upgrade software consists of the files you downloaded in Procedure 2. “Download the iDX
3.0 Images” on page 15. The first file contains the ISO image, which contains all the files
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.
• Update all RHEL, MySQL and iDirect RPMs.
• This upgrade may include RHEL 5.x changes that require a reboot to be effective. The
idsUpdate script will detect this condition and require that the option --reboot be
specified before the update will be permitted.
Note: If U.S. Department of Defense Security Technical Implementation Guide (STIG)

compliance is required, use the --harden option to run the latest version of
system hardening scripts. However, if STIG compliance is not required, do not
use the --harden option because it will prevent installation of debug tools and
cannot be reversed.
You must perform this procedure on every NMS that you are upgrading (this includes Primary
and Backup NMSs, and all NMS servers in a Distributed NMS configuration). You can perform
the upgrade using the ISO images directly.
Upgrade the NMS Server

1. Log on to the NMS server and type su - to switch to root.
2. Stop the NMS server process by entering the following command:
service idirect_nms stop
3. Using WinSCP, transfer the Kickstart ISO image and the debug tools ISO image that you
downloaded from the TAC web page the /tmp directory on your primary NMS.
4. Create a directory called /media/cdrom by entering the following command:
5. Update the NMS server by entering the following command:
mount -o loop /tmp/IDS-12.0.0.0-390.iso /media/cdrom
/media/cdrom/iDirect/install/idsUpdate
Note: Use the --harden option with the idsUpdate command if STIG compliance is
required, for example: idsUpdate --harden.
a. 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 message displays, enter the idsUpdate command again with the reboot option
as shown:
/media/cdrom/iDirect/install/idsUpdate --reboot
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:
MySQL appears to be running but PID file does not match hostname:
If either of these messages displays, restart MySQL by entering the following
command:
/media/cdrom/iDirect/install/idsUpdate --restartMySQL
6. After idsUpdate finishes executing (or after the server reboots) enter the following
commands:
umount /media/cdrom
rm -f /tmp/IDS-12.0.0.0-390_NMS_PP.iso
Procedure 2. Apply NMS License and Run Service Upgrade

Perform all of the steps in this procedure on your Primary NMS. On your Backup NMS, perform
steps 1 through 4 (copy the NMS license to /home/nms/config folder) and step 5 (upgrade the
services). You do not perform step 6 on the Backup NMS.
1. Use WINSCP as idirect user to copy the NMS license file that you obtained from the TAC
from your PC and place it in the /tmp directory on your Primary NMS.
2. Logon to the NMS server and enter su - to switch to root.
Note: If you wish 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>
3. Go to the /tmp directory by entering the following command:
cd /tmp
4. Copy your new license file to the /home/nms/cfg directory by entering the following
command:
cp yourlicense.lic /home/nms/cfg/nmssvr_e.lic
Where yourlicense.lic is the name of the license file that the TAC provided to you.
When the Linux prompt is returned, you can continue to the next step.
STOP! The next step provides a work-around for a known issue

with the mapsvr when upgrading from iDX Release 2.0.x
to iDX Release 3.0. See the iDX 3.0 Release Notes for
further information.
5. Remove the mapsvr from the para_list.opt file by entering the following commands:
grep -v mapsvr /home/nms/utils/para_list.opt > /tmp/para_list.opt
mv /tmp/para_list.opt /home/nms/utils/para_list.opt
6. Start the nms service by entering the following command:
service idirect_nms upgrade
Note: The integrity is checked at this point. If it fails, enter the command again.
If it continues to fail, contact the TAC (see “Getting Help” on page xiv).
7. Configure the idirect nms_service to start automatically at boot time, by entering the
following command:
chkconfig idirect_nms on
Procedure 3. Install the NMS Client Software (iBuilder/iMonitor)

Perform the following to install the client software:
1. On the PC/Laptop, logon as administrator.
2. Using Unzip, WinZip, or PKZIP, uncompress the previously downloaded
nmsclients1200010.zip file to a location on your PC/laptop where you can easily locate
it later. If you are running Windows XP, right-click on the file and select Extract All.
3. 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, you have entries for iBuilder, iMonitor, and iSite in
your Windows/Start/Programs menu under iDirect. InstallShield also creates a folder
called NMS Clients 12.0.0.0 with shortcuts on your desktop.
4. Verify NMS connectivity by pinging the Primary NMS Server.
5. Open the newly installed iBuilder and connect to the upgraded NMS. Check the status of
remotes and line cards.
STOP! If you had DVB-S2/TPC networks prior to upgrading to iDX
Release 3.0, the NMS configuration will be incomplete at
this point for these networks. As a result, iMonitor may
show remotes out of these networks. This is an expected
result, and it will be completed later in the upgrade
procedure. Continue to the next step.
STOP! Due to a known issue in iDX 3.0, iNFINITI line cards may
show “incomplete” in the iBuilder Tree View (refer to the
iDX Release Notes 3.0 for further information). There is a
work-around for this issue, which you will perform after
completing the network upgrdade (see Procedure 2.
“Verify Changes Pending on the Remotes and Incomplete
Line Cards after the Upgrade” on page 59).
6. Open the newly installed iMonitor and connect to the same upgraded NMS. Check the
status of remotes and line cards.
This completes the NMS server portion of the upgrade. Proceed to the next chapter for
instructions on upgrading your remotes.
Procedure 4. Install the iDX Release 3.0.0.1 Remote Package

Patch on the NMS
Regardless of which iDS/iDX release you are currently running, you are required to apply the
iDX Release 3.0.0.1 Remote Package Patch before continuing to upgrade your network. The
application of this patch is critical because it fixes two network impacting issues:
• If the receive L-band frequency/symbol rate of an iNFINITI remote falls within certain
ranges, it was possible for the remote to incorrectly affect an internal parameter, and
cause the modem to fail to lock on to the downstream carrier.
• When the DHCP and RIP features were both enabled on a modem, the DHCP timer
prevents the modem from sending RIP updates after running without interruption for 50
days.
Note: For further information about these fixes, refer to the “iDX Release 3.0.0.1
Remote Patch Installation Instructions” readme file, available for download
from the TAC web page.
This section provides the procedures to apply the iDX Release 3.0.0.1 Remote Package Patch.
The remote package file includes:
• The iSite program and support files
• The Linux Board Support (BSP) Package: linux_2.4_bsp-12.0.0.1.pkg
• The iNFINITI Non-3xxx Series Satellite Routers: remote-12.0.0.1.pkg
• The iNFINITI 3000 Series Satellite Routers: remote_3XXX-12.0.0.1.pkg
Of the Satellite Router packages listed above, you need to install the Linux Board Support
Package (BSP) and the appropriate iNFINITI Remote Image Package to each remote.
Perform the following steps to install the patch on your remotes:
1. Download the patch file as follows:
a. Browse to the TAC web page located at http://tac.idirect.net/.
b. Click the links Software › iDX › iDX3 › iDX 3.0.
c. Open the iDX Release 3.0 Software Package and Documentation Downloads link.
d. Scroll down to iDX 3.0.0.1 and click the Remote Software and iSite link to download
the zipped patch file.
e. Extract and save the files to a temporary directory on your PC.
2. Use WINSCP as idirect user to copy the extracted files to the /tmp directory of the NMS
server.
3. Use a Putty connection to log on to the NMS server as idirect and enter su - to switch to
root.
Note: Perform the commands in the steps that follow at the # prompt of the NMS
server.
4. Create a backup folder to store the old BSP package and the old remote image packages
as follows:
mkdir /root/3_0_OLD
5. Copy the Linux Board Support Package from the temporary directory to the appropriate
NMS directory as follows (enter all on one line):
cp /tmp/linux_2.4_bsp-12.0.0.1.pkg
/home/nms/cfg/image_sets/linux_2.4_bsp_package
6. Copy the old Linux Board Support Package to the previously created backup folder as
follows:
cd /home/nms/cfg/image_sets/linux_2.4_bsp_package
cp linux_2.4_bsp-12.0.0.0.pkg /root/3_0_OLD
7. Copy the non-3xxx remote image file from the temporary directory to the appropriate
cp /tmp/remote-12.0.0.1.pkg
/home/nms/cfg/image_sets/remote_package
8. Move the non-3xxx series remote image file to the previously created backup folder as
follows:
cd /home/nms/cfg/image_sets/remote_package
mv remote-12.0.0.0.pkg /root/3_0_OLD
9. Copy the Series 3xxx remote image file from the temporary directory to the appropriate
cp /tmp/remote_3XXX-12.0.0.1.pkg
/home/nms/cfg/image_sets/remote_3XXX_package
10. Move the old Series-3xxx remote image file to the previously created backup folder as
follows:
cd /home/nms/cfg/image_sets/remote_3XXX_package
mv remote_3XXX-12.0.0.0.pkg /root/3_0_OLD
Upgrading a Distributed NMS

If you are upgrading a distributed NMS, perform the following:
1. Upgrade each server using Procedures 1 through 4 as outlined in this chapter.
2. Upgrading to iDX Release 3.0 requires that you reconfigure your Distributed NMS after
upgrading each of the servers. Reconfigure the Distributed NMS at this point. For details
see the appendix on “Configuring a Distributed NMS” of the iBuilder User Guide for this
release.
3. Complete the remaining Procedures 5 through 10 as outlined in this chapter.
4. Because of a known issue in this release, you must manually start the monitor services on
your Primary NMS server (and only on the Primary NMS server). To do this, enter the
following command:
service idirect_nms start nms_monitor
If the Chassis Manager server (cmsvr) is running in one of the NMS servers that belongs to
the DNMS group, you must specify the cmsvr location when configuring the DNMS. For
details, see the appendix on “Configuring a Distributed NMS Server” of the iBuilder User
Guide for this release.
5 Upgrade Remotes
This chapter contains all procedures required to successfully install iDX Release 3.0 software
on your remotes.
STOP! If you have any custom keys defined, especially on the

remotes, contact the TAC to determine if the custom keys
are valid in this release.
• Procedure 1, Reconfiguring TPC Inbound Carriers in DVB-S2 Networks

• Procedure 2, Perform a Multicast Test
• Procedure 3, Download the BSP Update
• Procedure 4, Download Software Packages to Remotes
• Procedure 5, Apply the Configuration Options File
*** NETWORK DOWNTIME BEGINS HERE ***
Note: NetModem and NetModem II Plus remotes are not supported in this release.
Only iNFINITI (all models) and Evolution (models X3, X5, e800, e850mp and
e8350) remotes are supported in iDX 3.0.
The Linux BSP package files and remote package files by remote type are listed in Table 2.
STOP! The figures shown in this chapter are examples only. Be

sure to select the appropriate file from Table 2 when
upgrading the Linux BSP and Remote Packages.
Table 2. Cumulative Update and Remote Upgrade Packages
Type of Remote Linux BSP package Remote Package

iNFINITI 3xxx linux_2.4_bsp-12.0.0.1 remote_3xxx-12.0.0.1
iNFINITI Remote (other than iNFINITI 3xxx) linux_2.4_bsp-12.0.0.1 remote-12.0.0.1
Table 2. Cumulative Update and Remote Upgrade Packages (continued)
Type of Remote Linux BSP package Remote Package

EvolutionX3Remote linux_2.4_bsp-12.0.0.0 evo_x3_rmt-12.0.0.0
EvolutionX5Remote linux_2.4_bsp-12.0.0.0 evo_x5_rmt-12.0.0.0
Evolution8Series linux_2.6_bsp-12.0.0.0 e8_rmt-12.0.0.0

Note: If you have more than one type of remote, you must perform these procedures
once for each remote type, selecting the appropriate update or package each
time.
After you finish upgrading your network, you can use the revision server to automatically
upgrade your off-line remotes.
STOP! 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.
STOP! If you use the Multicast Download option, DO NOT ADJUST

THE DOWNLOAD RATE; iBuilder has automatically set the
download rate to the appropriate value for your
downstream data rate.
STOP! After downloading cumulative updates to 3100 remotes,

you must wait a minimum of 10 minutes before
downloading the upgrade package. This delay depends on
past upgrade history and is due to limited space on the
3100 model. You can check the condition of the remote
package flash by observing the message on the iBuilder
window. Alternatively, Telnet to the remote while
downloading the package and wait for the flash
completion message.
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 be 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.
STOP! Networks with DVB-S2 outbound carriers and TPC
inbounds carriers, will show “incomplete” for Inroute
Groups and TPC receive line cards. The remotes will also
show “deactivation pending”. This is an expected result.
If you have these types of networks, perform Procedure 1,
Reconfiguring TPC Inbound Carriers in DVB-S2 Networks.
Procedure 1. Reconfiguring TPC Inbound Carriers in DVB-S2

Networks
If you have networks with DVB-S2 outbound carriers and TPC inbound carriers, you must
reconfigure your iNFINITI hub line cards as Evolution hub line cards using 2D 16-State coding
on the inbound carriers. This procedure provides the steps to follow to do this. If you do not
have DVB-S2 networks with TPC inbounds, skip this step and go to Procedure 2, Perform a
Multicast Test.
Note: If you have networks with DVB-S2 outbound carriers and TPC inbound carriers,
you must also replace your iNFINITI hub line cards with Evolution hub line
cards. Do not replace them now! You will do this when you upgrade your line
cards in the next chapter.
Perform the following:
1. Using iBuilder, delete each iNFINITI hub line card and create an Evolution line to replace
each iNFINITI hub line card. (Refer to the iDX Release 3.0 iBuilder User Guide for detailed
instructions).
2. Change the Carrier Type from your current TPC configuration to the best 2D 16-State
MODCOD combination for your network. (Refer to the Link Budget Analysis Guide, iDX 3.0
for further information on selecting 2D 16-State the best configuration option for your
network.)
3. Assign each new Evolution hub line card to the hub chassis slot.
4. Assign the Inroutes to the Inroute Group.
Your receive line cards and Inroute Groups now show “complete” or “changes pending”. Your
remotes now show “complete” and “changes pending”.
STOP! If any of your receive line cards, Inroute Groups, or

remote still indicate “incomplete” or “deactivation
pending”, do not proceed with the upgrade. Contact the
TAC for immediate assistance.
Procedure 2. Perform a Multicast Test
A Multicast test determines which remotes are in the network and capable of receiving
multicast messages. “Active” remotes within your network are those that are active in the
NMS database and have been detected when the hub is sweeping for remotes.
1. Launch iBuilder and log on as administrator.
2. In the Tree View, right-click on the Network icon, and select Package
DownloadMulticast.
Figure 2. Select Package DownloadMulticast
The Multicast Download window displays (Figure 3).
Figure 3. Multicast Download Window
When doing a Multicast Test, iBuilder automatically selects all of the active components
in your network. In the Modems area of the Multicast Download window, you should see a
list with all active remotes selected.
3. In the Package pane of the Multicast Download window, select the appropriate Hardware
drop-down field: EvolutionRemote, iNFINITI, or iNFINITI-3xxx.
4. For Role, leave the default Remote selected.
5. For Mode, leave the default selected.
6. In the Version drop-down field select Test-Package.
7. 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.
Procedure 3. Download the BSP Update
If you are updating iNFINITI and/or Evolution remotes, you must first load the Linux BSP
update package listed in Table 2 on page 27 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 4).
Figure 4. Multicast Download—Downloading the Cumulative Update
2. In the Package pane of the Multicast Download window, select the appropriate Hardware
drop-down field: EvolutionxxRemote, iNFINITI, or iNFINITI-3xxx.
3. For Role, select Remote.
5. In the Version drop-down field, select one of the following:
For iNFINITI remotes: 12.0.0.1 BSP UPDATE
For Evolution remotes: 12.0.0.0 BSP UPDATE
6. Make certain no hub line cards are selected.
7. Under Download Parameters, make certain Reset is not selected.
8. 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 4 on page 32).
Watch for the Flash Completed messages at the bottom of the Multicast Download
window.
STOP! Depending on the type of remote, it can take up to 10-20

minutes to completely flash its memory. Do not proceed
until memory flash is complete. You may want to observe
the download and flash activity through the telnet session
previously opened (see TIP on page 24).
9. Repeat Steps 1-8 for every remote type in your network.

When all downloads are complete, go to Procedure 4, Download Software Packages to
Remotes.
Procedure 4. Download Software Packages to Remotes

Perform the steps in this procedure to select appropriate remote software packages and
download them to your remotes.
1. In the Tree View, right-click on the Network icon, and select Package
The Multicast Download window displays.
Look for these same messages
in the telnet session windows
for each remote.
Figure 5. Multicast Download Window—Selecting Remote Package
2. In the Package pane, select the appropriate value from the Hardware drop-down field:
EvolutionxxRemote, iNFINITI, or iNFINITI-3xxx.
3. For Role, select Remote.
5. For Version drop-down field, select one of the following:
For iNFINITI remotes: 12.0.0.1
For Evolution remotes: 12.0.0.0
6. In the Modems area of the Multicast Download window, make certain that only active
remotes are selected.
7. In the Hub area of the Multicast Download window, make certain that no hub line cards
are selected.
8. Under Download Parameters, make certain Reset is NOT selected.
STOP! When using the Multicast Download option, DO NOT

ADJUST THE DOWNLOAD RATE. iBuilder has automatically
set this to the appropriate value for your downstream
data rate.
STOP! DO NOT reset the remotes at this time!
9. 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). Watch for the
Flash Completed messages at the bottom of the Multicast Download window.
STOP! Depending on the type of remote, it can take up to 10-20

minutes to completely flash its memory. Do not proceed
until memory flash is complete. You may want to observe
the download and flash activity through the telnet session
previously opened (see TIP on page 24).
10. Repeat this procedure for the other types of remotes in your network, until you have
downloaded the images to them all.
11. When the software download to all of your active remotes is complete, close the
Multicast Download window.
Procedure 5. Apply the Configuration Options File
After completing the software upgrade, use this procedure to apply the configuration Options
files to all of the active remotes in your network.
1. In the Tree View, right-click the Network icon, and then select Apply Configuration
Multiple (Figure 6).
Figure 6. Select Apply ConfigurationMultiple
The Automated Configuration Downloader window displays your remotes, hub line
cards, and the network (Figure 7). In the Remotes area, iBuilder automatically selects the
affected remotes.
Note: On Global NMS configurations, uncheck all remotes that have an

“ELSEWHERE” status.
Figure 7. Automated Configuration Downloader Window—TCP with Don’t Reset Option
2. For Target, select Remote-side Only.

3. For Protocol, select Reliable (TCP).
4. For Reset, select Don’t Reset.
STOP! Do not reset your remotes at this time. You will reset
your remotes using Push (UDP) later.
5. Clear any selected check boxes in the Line Cards and Network areas.
6. Click Start to send the appropriate Options file to all selected remotes.
Download progress is indicated to the right of each active remote in the Remote-side
Status column.
7. If this TCP download procedure fails for any remotes in the network, repeat Steps 1-6 for
those remotes.
STOP! Carefully follow the instructions in the next step when
upgrading remotes. You must select the “Push (UDP)” and
“Reset on success” options when upgrading remotes.
Failure to select these options could cause your remotes
to not reset properly and become stranded (requiring a
manual power-cycling to rejoin the network).
8. In the Automated Configuration Downloader window, select the Remote-side only, Push
(UDP) and Reset on Success options in the Remotes area (Figure 8).
Figure 8. Automated Configuration Downloader Window—UDP with Reset Option
9. Clear any selected check boxes in the Line Cards and Network areas. Optionally, you can
also uncheck any ELSEWHERE remotes in the Remotes area. [ELSEWHERE remotes will be
upgraded when upgrading the network to which they are currently assigned.]
10. Click Start to send the appropriate Options file to all of the remotes and reset them.
11. When the multiple configuration download to all of your active remotes is complete, close
the Automated Configuration Downloader window.
STOP! For DVB-S2 networks with TPC inbounds, remotes will
show out of network until the hub side portion of the
upgrade is complete. This is an expected result. In the
next section, you will reconfigure your hub line cards from
TPC coding to 2D 16-State coding and the remotes will
join the network.
This completes the remote portion of the iDX Release 3.0 upgrade for this network.
6 Upgrade Hub Line Cards
This chapter contains the following procedures to successfully upgrade your hub line cards:
• Replacing iNFINITI Hub Line Cards with Evolution Hub Line Cards
• Download BSP Update Package
• Download Line Card Packages
• Apply the Configuration Options File
The cumulative update files and the update packages by type of hub line card for the current
release are listed in Table 3.

Table 3. BSP Update and Line Card Upgrade Packages
Type of Line Card BSP Update Package Line Card Package

iNFINITI Hub linux_2.4_bsp-12.0.0.1 hub-12.0.0.1
EvolutionLinecard - DVB-S2 mode linux_2.6_bsp-12.0.0.0 evo_d_hub-12.0.0.0
EvolutionLinecard - iNFINITI mode linux_2.6_bsp-12.0.0.0 evo_l_hub-12.0.0.0
Note: NetModem II+ Universal Line Cards are not supported in this release. Only
iNFINITI (all models) and Evolution (models XLC-10, XLC-11, XLC-M and eM1D1)
line cards are supported in iDX 3.0.
Procedure 1. Replacing iNFINITI Hub Line Cards with Evolution

Hub Line Cards
Perform this procedure only if you performed Procedure 1, "Reconfiguring TPC Inbound
Carriers in DVB-S2 Networks" on page 29.
Now that you have reconfigured your inbound carriers for 2D 16-State coding, you must
replace your iNFINITI hub line cards that are in a DVB-S2 outbound network with Evolution hub
line cards. Perform the following:
1. Physically replace the iNFINITI hub line cards with the Evolution hub line cards in the hub
chassis.
2. Upgrade each new Evolution hub line card by using iSite.
Procedure 2. Download BSP Update Package

Before you download the line card packages, you must download the BSP update package.
To download the BSP update package:
1. Launch iBuilder and log on as administrator.
2. In the Tree View in iBuilder, right-click the Network icon, and then select Package
DownloadTCP (Figure 9 on page 42).
Figure 9. Selecting Package DownloadTCP
The TCP Download window displays (Figure 10 on page 43).
Figure 10. TCP Download Window—Selecting BSP Updates for Hub Line Cards
3. In the Options pane of the TCP Download window, select the appropriate Hardware:
iNFINITI or EvolutionLinecard.
4. For Role, select Hub.
6. In the Version drop-down field, select one of the following:
For iNFINITI hub line cards: 12.0.0.1 BSP UPDATE
For Evolution hub line cards: 12.0.0.0 BSP UPDATE
7. For Image Version Check, select Don’t check versions.
8. For Configurations, select Download images only.
9. For Reset, select Don’t reset.
10. Click Start to download the cumulative package.
Wait for the “Flash Completed” message in the Events Description column in the bottom
pane (Figure 10).
11. Repeat Steps 1 through 10 for each type of line card residing on the network that you are
currently upgrading.
When the download is complete, go to the next procedure.
Procedure 3. Download Line Card Packages

Now that you have downloaded the BSP update package, you can download the line card
packages. Perform the steps in this procedure to select appropriate hub upgrade packages
and download them to your hub line cards.
1. In iBuilder, in the Tree View, right-click the Network icon, and then select Package
DownloadTCP.
The TCP Download window displays (Figure 11).
Figure 11. TCP Download Window - Download Packages to Line Cards
2. In the Options pane of the TCP Download window, select the appropriate Hardware:
iNFINITI or EvolutionLineCard.
3. For Role, select Hub.
5. In the Version drop-down field, select on of the following:
For iNFINITI hub line cards: 12.0.0.1
For Evolution hub line cards: 12.0.0.0
STOP! If you are upgrading an eM0DM, eM1D1, XLC-11, or XLC-M
hub line card (HLC), you download both DVB-S2 and
iNFINITI packages (one at a time) to ensure future use of
either carriers. You should not download the iNFINITI
package for the XLC-10 HLC. With the addition of
multichannel and SCPC return support in iDX 3.0, the
download may take 3-5 minutes.
6. For Image Version Check, select Don’t check versions.

7. For Configurations, select Download images only.
9. 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 11 on page 45).
10. Repeat these Steps 1-9 for each line card type.
11. When all downloads are complete, wait three minutes for the line cards to completely
store the package into flash memory.
Procedure 4. Apply the Configuration Options File

After completing the software image upgrade, use this procedure to apply the configuration
to all of the active line cards in your network.
1. In the Tree View, right-click the Network icon, and then select Apply
ConfigurationMultiple.
The Automated Configuration Downloader window displays your remotes, hub line
cards, and the network (Figure 12 on page 47).
Figure 12. Automated Configuration Downloader Window—TCP with No Reset Option
2. In the Line Cards area, select all line cards.
Note: Verify that the remotes and network are NOT selected. You do NOT send
options files to these components at this time.
3. In the Protocol field, select Reliable (TCP).
4. In the Reset field, select Don’t reset (Figure 12).
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 complete, you will repeat
Steps 2-4, but this time select Push (UDP), as follows:
6. In the Line Cards area, select the Push (UDP) and Reset on Success options (Figure 13).
Figure 13. Automated Configuration Downloader Window—Push UDP with Reset Option
7. Clear any selected check boxes in the Remote and Network areas.
8. Click Start to send the appropriate Options file to all of the line cards and reset them.
Note: At this point a UDP push (with reset option) is performed that reboots the
line card’s board.
9. Verify that the line card was successfully upgraded by telneting into the line card and
issuing the following command:
version
10. When the multiple configuration download to all of your line cards is complete, close the
Automated Configuration Downloader window.
Repeat “Chapter 5, Upgrade Remotes” and “Chapter 6, Upgrade Hub Line Cards” for each
network that you are upgrading before you continue to the next procedure.
STOP! Due to changes in the communication protocol between

the line cards and Protocol Processor, all remotes and
networks will be down at this point. This is an expected
result; remotes will join the networks after the PP is
upgraded.
This completes the line card portion of your upgrade for this network. Proceed to Procedure
7, "Upgrade Protocol Processor Blades" on page 51.
7 Upgrade Protocol
Processor Blades
This chapter contains the procedures for successfully upgrading your Protocol Processor (PP)
Blades in your iDirect networks:
• Upgrade the Protocol Processor
• Restart Remaining Services on NMS Server
• Apply Configurations
Procedure 1. Upgrade the Protocol Processor

You must perform this procedure on every Protocol Processor Blade that you are upgrading. If
U.S. Department of Defense Security Technical Implementation Guide (STIG) compliance is
required, use the --harden option to run the latest version of system hardening scripts.
1. Using WinSCP, copy the Kickstart ISO image that you downloaded from the TAC web page
to the /tmp directory on your Protocol Processor.
2. Create a directory called /media/cdrom:
3. Update the PP Blade by entering the following command (enter as one continuous line):
mount -o loop /tmp/IDS-12.0.0.0-390.iso /media/cdrom\
/media/cdrom/iDirect/install/idsUpdate
Note: Use the --harden option with the idsUpdate command if STIG compliance is
required, for example: idsUpdate --harden. However, if STIG
compliance is not required, do not use the --harden option because it will
prevent installation of debug tools and cannot be reversed.
4. 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:
/media/cdrom/iDirect/install/idsUpdate --reboot
5. After idsUpdate finishes executing, or after the server reboots, enter the following
commands:
umount /media/cdrom
6. Enter the following command to start PP services:
service idirect_hpb start
7. To configure the idirect_hpb service to start automatically at boot time, run the
following command:
chkconfig idirect_hpb on
8. If you are using TRANSEC with Global Key Distribution (GKD), enter the following
commands to start the GKD service and to configure the NMS server to start the GKD
service on boot up:
service idirect_gkd start
chkconfig idirect_gkd on
Refer to the Appendix on “Managing TRANSEC Keys” of the iBuilder User Guide for iDX
Release 3.0 for further information on configuring GKD.
Procedure 2. Restart Remaining Services on NMS Server

1. Open a SSH session on the NMS server and turn on the remaining services by entering:
service idirect_nms start
2. Check to see the NMS services are running by entering:
service idirect_nms status
All services should now indicate that they are running.
Note: You may see that the osssvr (Operation Support Server) and skysvr
(SkyMonitor Server) are stopped. These are optionally licensed features.
3. If you are using Automatic Beam Selection (ABS), 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 3.0 for further
information on configuring ABS.
4. If you are using TRANSEC with Global Key Distribution (GKD), enter the following
commands to start the GKD service and to configure the NMS server to start the GKD
service on boot up:
service idirect_gkd start
chkconfig idirect_gkd on
Refer to the Appendix on “Managing TRANSEC Keys” of the iBuilder User Guide for iDX
Release 3.0 for further information on configuring GKD.
Procedure 3. Apply Configurations
Note: Your remotes may not re-acquire until this step is complete.
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 14 on page 53).
Figure 14. 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).
7. Under Network, select all networks.
8. Click Start to download the hub-side configurations.
Your remotes will now start joining the network.
*** NETWORK DOWNTIME ENDS HERE ***

This completes the Protocol Processor portion of your iDX 3.0 upgrade for this network.
Proceed to the next chapter for instructions on upgrading your backup NMS server.
8 Upgrade the Backup NMS
Server
STOP! Your Backup NMS server is about to be upgraded and you

will lose anything stored on this server. If any information
or files have to be retained, perform idsBackup as
described in Procedure 5. “Backup the Database” on page
18.
Upgrade the Backup NMS using the procedures outlined in Chapter 4, "Upgrade the NMS
Server" on page 21 and using the database backup made by performing Procedure 5. “Backup
the Database” on page 18. However, do not run 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 by entering 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
9 Required Post-Upgrade
Activities
Upon completion of the upgrade, there are some additional procedures that may be required
for your specific environment. This chapter outlines these post-upgrade procedures that are
required to successfully complete the upgrade to your iDirect network.
• Procedure 1, "Verify that the Upgrade has Completed Successfully"
• Procedure 2, "Verify Changes Pending on the Remotes and Incomplete Line Cards after
the Upgrade"
• Procedure 3, "Reconfigure the crontab File on the NMS Servers"
• Procedure 4. “Verify That the Backup is Working” on page 60
• Procedure 5, "Verify iDirect SNMP Configuration Working Settings (if applicable)"
• Procedure 6, "Verify If You Have Remotes Still Out-of-Network"
• Procedure 7, "Remove the ISO Image from the /tmp Folder"
Procedure 1. Verify that the Upgrade has Completed

Successfully
To verify that the upgrade is successful, you need to check that your remotes have acquired
into the network and verify connectivity to your remotes. You may need to perform load
balancing across your PP blades, depending on how many remotes are in the network. Using a
PC on which you have installed the NMS client software:
1. Launch iMonitor and logon as administrator.
2. Verify that all of the remotes have acquired into the network.
3. Check IP connectivity to the remotes and the functionality of your applications.
Note: iNFINITI remotes have no status LED (LED is dark). Only TRANSEC-enabled
iNFINITI remotes will have a GREEN status LED.
4. To ensure that the remote loading across the protocol processor blade set is balanced,
perform a “blades rebalance” to distribute the remotes, perform the following at the root
level command line prompt #:
STOP! Rebalancing the PP blades causes a momentary outage

that can range between from a few seconds to a few
minutes, depending on the number of remotes.
a. Open an SSH session to the Primary NMS using PuTTY.

b. 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
c. Note the port number listed after -cp. In this example, the port number is 15001.
You need the port number to Telnet into the protocol processor.
d. Open the Telnet session to that PP by issuing the following command:
telnet localhost <port#>
Where,
<port#> = the pp_controller port number.
e. Enter the credentials “admin” and “P@55w0rd!” to log on to the pp_controller.
f. To verify that all blades are up (no Sync Needed), enter the following command at the
> prompt:
blades status
STOP! Do not rebalance the blades if any PP blade is down.
g. 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.
h. Repeat the process for each PP Controller that is listed on your NMS server.
Procedure 2. 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.
Due to a known issue in iDX Release 3.0, iNFINITI standby hub line cards may sow
“incomplete” in the iBuilder Tree View. If this is the case for your networks, perform the
following:
1. Right-click the incomplete line card and select ModifyConfiguration.
2. Change the name of the line card to something tempory by adding a character to the
current name, for example, and save the changes.
3. Right-click the incomplete line card and select ModifyConfiguration again.
4. Change the name of the line card back to the original name and save the changes.
The line card status is now “complete”.
Procedure 3. Reconfigure the crontab File on the NMS Servers

The crontab file must be restored to its pre-upgrade condition by removing the # sign from
the lines where you previously inserted them in Procedure 3, "Modify the CRONTAB File".
Perform the following actions on the Primary and Backup NMS.
On the Primary NMS

1. Logon to the Primary NMS server and type su - to switch to root.
2. Edit the crontab file by entering the command:
crontab -e
The crontab file opens in the Vi editor.
3. On the Primary NMS, replace the following line:
30 0 * * * /opt/idirect/install/idsBackup -host local -keep 2
>/dev/null 2>&1
with this line:
00 1 * * * /usr/bin/idsBackup --inst
idirect@192.168.0.101:/var/idirect/backup/\%ip-\%date --keep 2
4. 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
5. On the Backup NMS, remove the comment symbol (#) from all lines in the CRONTAB file,
except for this line:
\%date --keep 2
6. Save changes to the file and exit by pressing Esc and entering the following command:
:wq!
7. Re-issue the SSHKeys on the Backup NMS by entering the following command:
pushSSHKeys <IPaddress>
Where,
<IPaddress> = the IP address of your backup NMS server.
For example:
pushSSHKeys 192.168.0.101
Pushing SSH key for user root to idirect@192.168.0.101:
idirect@192.168.0.101's password:
SSH key for user root successfully pushed to idirect@192.168.0.101
Examples of the reconfigured CRONTABS are shown here:
On the Primary NMS:
\%date --keep 2
0 1 * * * /usr/bin/idsBackup --inst
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:

>/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 4. Verify That the Backup is Working

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 on one continuous line):
/usr/bin/idsBackup --inst
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:
idirect@192.168.0.101:/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
Installing backup on remote host: 192.168.0.101 DONE
2. On the Backup NMS, go to /var/idirect/backup directory by entering the following
command:
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
2011.02.15-15.29.58
[root@Backup_NMS backup]# date
Fri Feb 15 15:36:16 UTC 2011
4. For Distributed NMS only: On the Auxiliary NMS, 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 a few times to ensure that two
copies are kept.
/usr/bin/idsBackup -bkup /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:
idirect@192.168.0.101:/var/idirect/backup/192.168.0.110-2011.02.15-
15.40.50 DONE
5. On the Backup NMS, go to /var/idirect/backup directory by entering the following
command:window
6. Check whether the backup files updated correctly by checking the date of the backup
files. In our example, only the two latest versions are kept.
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@localhost backup]# date
Tue Feb 15 15:55:01 UTC 2011
Procedure 5. Verify iDirect SNMP Configuration Working Settings

(if applicable)
Once the upgrade is complete, you must return your working SNMP configuration.
To return your working SNMP configuration, perform the following at the root level command
line prompt #:
1. From the /root directory of the NMS Server, go to your SNMP directory:
cd /home/nms/snmpsvr
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]
db_host_name = 127.0.0.1
db_user_name = root
db_database_name = nrd_archive
db_password =
drvmgr_max = 20
[TRAP_PARM]
trapsink = localhost
trap2sink = localhost
community = public
[TRAP_PARM]
trapsink = localhost
trap2sink = 10.0.1.12:7031
community = public
Procedure 6. Verify If You Have Remotes Still Out-of-Network

If the upgrade is complete and you still have out-of-network remotes, 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 7. Remove the ISO Image from the /tmp Folder

Now that the upgrade is complete, to improve available disk space, iDirect recommends that
you remove the IDS-12.0.0.0-390_NMS_PP.iso file from the /tmp directories on each of your
NMS servers and PP Blades to improve available disk space. To do this,
1. Log on to the Primary NMS and enter the following commands:
umount /media/cdrom
rm -f /tmp/IDS-12.0.0.0-390_NMS_PP.iso
2. Repeat Step 1 for each NMS server and PP Blade in your network.
Appendix A. Obtaining IBM
Server Information
The following information can be obtained with the specified commands.

1. Operating System Version:
cat /etc/issue
2. Memory Size:
free
total used free …
Mem: 514096 445588 68508 …
3. Disk Space:
df
Filesystem 1K-blocks Used …
/dev/sda2 136890632 33644104 …
/dev/sda1 101089 10036 …
none 1030772 0 …
4. CPU Spec:
The most accurate information is provided at boot time, before the IBM eServer splash
page where it shows the number of CPUs, type of CPU, and speed.
Red Hat Linux has a file to show CPU information:
less /proc/cpuinfo
processor : 0 (<- virtual CPU ID)
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Xeon(TM) CPU 3.20GHz
…
Red Hat EL has a command to show CPU speed and number of (virtual) CPUs.
/usr/sbin/x86info
…
CPU #4
Family: 15 Model: 2 Stepping: 5 Type: 0
CPU Model: Pentium 4 Xeon (Northwood) Original OEM
Processor name string: Intel(R) Xeon(TM) CPU 3.20GHz
Number of logical processors supported within the physical

package: 2
WARNING: Detected SMP, but unable to access cpuid driver.

Used single CPU routines. Results inaccurate.
Appendix B. Third-Party
Software Options
B.1 Third Party Software Bundled with IDS

B.1.1 iPerf
iPerf is downloaded with the iDirect upgrade as third party software. iPerf was developed for
measuring TCP and UDP bandwidth performance. It can be used to measure maximum TCP
bandwidth, allowing the tuning of various parameters and UDP characteristics. iPerf reports
bandwidth, delay jitter, datagram loss.
You can install the iPerf diagnostic tool by running the self-extracting archive
iperf-1.6.5-win32.exe file. The documentation files are HTML files that can be read with a
web browser.
B.1.2 EDAS
The edas.zip file contains a Windows GUI for setting the IP address on the Chassis EDAS
controller.
More information about third_party/nms/edas/edas.zip is available at
http://tac.idirect.net. See the technical note, “NMS Hub Chassis Monitor and Control.”
B.1.3 PuTTY
PuTTY is a free implementation of Telnet and SSH for Win32 and UNIX platforms with an
xterm terminal emulator.
http://www.chiark.greenend.org.uk/~sgtatham/putty/
You must have the server’s IP address and full administrative privileges to the server to use
PuTTY.
Downloading and Installing PuTTY

1. On your PC/Laptop open a connection to the Internet.
2. Copy http://www.chiark.greenend.org.uk/~sgtatham/putty/ into your browser to locate
the PuTTY home page.
3. Under Site Map, click the Download PuTTY hyperlink.
4. On the PuTTY Download page, scroll down to the Binaries section, and select PuTTY.exe.
5. In the Download File window, select Save.
6. In the Save As window, navigate to the desktop on you PC/Laptop. (This automatically
creates a desktop icon).
B.2 Additional Third Party Software Options

There are two third party software options discussed in this appendix:
• WinSCP
• WinZip
B.2.1 WinSCP
WinSCP is an open source SFTP (SSH File Transfer Protocol) and SCP (Secure CoPy) client for
Windows using SSH (Secure SHell). Its main function is safe copying of files between a local
and a remote computer. To use WinSCP 3, you must have the IP address of the server and full
administrative privileges to the server in order to copy files back and forth to the server.
1. Open a connection to the Internet on your PC/Laptop.
2. Copy http://winscp.sourceforge.net/eng/ into your browser bar.
3. Click the Download button on the left hand side of the screen.
4. Select WinSCP3 Installation Package (English only).
5. Select the “Mirror” you want to use (either the closest geographical link or the fastest).
6. In the File Download window, select Open.
7. In the Setup WinSCP3 window, select Next.
8. Accept the agreement and then select Next.
9. Take note of the default destination and required free disk space and select Next.
10. Select Full Installation; then select Next.
11. Note the default start menu folder and select Next.
12. Under Select Additional Tasks, select the following:
• Create a Desktop Icon
• For All Users
13. Register to handle scp:// and sftp:// addresses.
14. In the Please Select Your Preferred Interface Options window, select Explorer-like
Interface, and then select Next.
15. In the Ready to Install window, select Install.
16. In the Completing the WinSCP3 Setup Wizard window, select Finish.
How To Copy A The File To Your Local PC/Laptop Using WinSCP
1. Establish a connection between PC/Laptop and the server.
2. Select on any file that you wish to move and drag it from one machine to the other.
B.2.2 WinZip
1. On your PC/Laptop open a connection to the Internet.
2. Copy http://www.winzip.com/ into your browser to locate the WinZip home page.
3. Click the DOWNLOAD button for either purchasing a licensed copy of WinZip or
downloading an evaluation version.
4. On the Download WinZip Version X page, select a server from which to download.
5. In the File Download window, select Open to download the file.
6. In the WinZip SETUP window, select Setup.
7. In the next WinZip Setup window, note the name of the folder where WinZip installs, and
click OK.
8. In the next WinZip Setup window, select Next.
9. Agree to the WinZip License Agreement and Warranty Disclaimer by selecting Yes, and
then select Next.
10. Select Start in the WinZip Wizard, then select Next.
11. Select Search Entire Hard Disk (recommended), then select Next.
12. Select Next.
13. Select Close.
This will install the WinZip program on the PC and create a WinZip icon on the desktop.

NUP NetworkUpgradeProc IDX21 and Later To 30 RevC 110311

Uploaded by

Copyright:

Available Formats

NUP NetworkUpgradeProc IDX21 and Later To 30 RevC 110311

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 NetworkUpgradeProc IDX21 and Later To 30 RevC 110311

Uploaded by

Copyright:

Available Formats

Network Upgrade

iDX Release 2.1 and Later to iDX Release 3.0

Document Name: NUP_NetworkUpgradeProc_iDX21 and Later to 30_RevC_110311.pdf

Document Part Number: T0000382

Revision Date Released Reason for Change(s) Who Updated?

About This Guide

1 Read This First!

4 Upgrade the NMS Server

6 Upgrade Hub Line Cards

7 Upgrade Protocol Processor Blades

8 Upgrade the Backup NMS Server

9 Required Post-Upgrade Activities

Appendix B.. Third-Party Software Options . . . . . . . . . . . . . . . . . 67

This chapter includes the following sections:

Supported Upgrade Paths

Convention Description Example

Red italic Used when the user needs

Symbol Warning type Definition

CAUTION: When you see this alert symbol and

WARNING! Electric shock hazard: When you see

STOP! When you see this STOP sign, take heed

This chapter contains essential information needed to perform a successful upgrade to

What’s New in Upgrading to iDX Release 3.0?

STOP! The Kickstart installation erases all data on the target

Supported Upgrade Paths

Protocol Processor (PP) License for Link Encryption and

New “idirect” User

STOP! The upgrade checklist contains optional steps that only

Table 1. Network Upgrade Checklist

 Notify iDirect, complete and submit the iDX 3.0 Upgrade/Installation

 Complete technical requirements (see Section 2.3.2, "Technical

 Perform multicast download of a BSP to remotes (without reset) to verify

 Schedule downtime with customer(s)

 Consult with the TAC if you have any custom keys

Perform Pre-Upgrade Activities

 Check Line Cards and Remotes for Custom Keys

 Download the iDX 3.0 Images

 Modify the CRONTAB File

 Check the NMS Databases for Errors

Backup Existing Configurations and Data

 Perform the Upgrade

 Apply NMS License and Run Service Upgrade

 Install the NMS Client Software (iBuilder/iMonitor)

Upgrade Remotes on Your Network

 Consult with the TAC if you have any custom keys

 Perform a Multicast Test

 Download the BSP Update

 Download Software Packages to Remotes

 Apply the Configuration Options File

Upgrade Hub Line Cards

 Download BSP Update Package

 Download Line Card Packages

 Apply the Configuration Options File

Upgrade Your Protocol Processor Blades

 Upgrade the Protocol Processor

 If you are using Link Encryption or TRANSEC, install PP Encryption License

 Restart Remaining Services on NMS Server

 Apply Configurations and the Remote Hub-side Configuration

Upgrade the Backup NMS Server

* NETWORK DOWNTIME BEGINS HERE *