Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Technical Note
October 1, 2008
Copyright 2008 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.
ii
Revision History
The following table shows all revisions for this document. Refer to this information to verify
that you have the latest version.
Rev
Date Released
Who Updated?
August 7, 2006
E Hoffman
E Hoffman
E Hoffman
E Hoffman
E Hoffman
October 1, 2008
S Murphy
iii
iv
Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Contents Of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
iDX Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
iDS Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Hardware-Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
.................................. 1
........ 3
2.2 Configuring The NMS to Send Database Backups to The Backup NMS . . 4
2.3 Defining dbBackup Script Default Behavior . . . . . . . . . . . . . . . . . . . 4
2.3.1 Changing the Number of Backup Copies to Save . . . . . . . . . . . . . . . . . . . 5
2.3.2 Changing Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.2 Procedures for Moving pp_controller Files To the Backup NMS Server 16
Logging Into The Primary NMS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Compressing the pp_controller Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Copying the pp_controller Files from the Primary NMS Server to Backup NMS Server
17
vi
Purpose
The purpose of this document is to explain how to set up and automated backup/restore
mechanism for your NMS configuration and/or archve databases.
Intended Audience
This guide is written for network operators using the iDirect iDS iBuilder/iMonitor/iSite
software suite, network architects, and any other personnel who operate or monitor an
iDirect network. A basic knowledge of TCP/IP concepts, satellite communications, Linux and
MS Windows operating systems and tools (including WinSCP and PuTTY) is assumed. Prior
experience with the operation and monitoring of an iDirect network is desirable but not
required.
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 youll know how to interpret the
information presented.
Convention Description
Blue
Courier
font
Example
[SWITCH_PORT_n]
vid = vlan_id
vii
Courier
font
Bold
Trebuchet
font
Bold italic
Trebuchet
font
Used to emphasize
information for the user,
such as in notes.
Note:
Red italic
Trebuchet
font
(or see
table
below)
The following list of documents applies to iDX Release 1.0 and up.
The following iDirect documents are available at http://tac.idirect.net and may also contain
information relevant to this release. Please consult these documents as needed or indicated
within this guide.
viii
The following iDirect documents are available at http://tac.idirect.net and may also contain
information relevant to this release. Please consult these documents as needed or indicated
within this guide.
Hardware-Related Documents
Note:
The following iDirect documents are available at http://tac.idirect.net and may also contain
information relevant to this release. Please consult these documents as needed or indicated
within this guide.
iDirect Software Installation Guide (iDX) OR Network Upgrade Procedure Guide (iDS)
ix
Getting Help
Getting Help
The iDirect Technical Assistance Center (TAC) is available to help you 24x7x365. iDS Software
users guides, installation procedures, an FAQ page, and other documentation that supports
our products are available on the TAC webpage. Please access our TAC webpage at:
http://tac.idirect.net.
If you are unable to find the answers or information that you need, you can contact the TAC at
(703) 648-8151.
The NMS Redundancy and Failover mechanism, when set up on your network, automatically
backs up your primary NMS databases every night and restores them onto the Backup NMS
Server. In the event of a catastrophic NMS Primary Server failure, you can switch to your
Backup NMS Server with the assurance that most, if not all, of your data remains in tact.
The iDirect Technologies Network Management System (NMS) has a number of redundancy
levels that ensure robust operation, each covering a particular point of potential failure.
1.1
Process Redundancy
The standard NMS installation includes a daemon1 process called nms_monitor. This process
monitors all of the other NMS server processes on a constant basis. If any of these processes
terminate abnormally, nms_monitor automatically restarts the process.
To view the status of the NMS monitor and server processes, perform the following:
1. Logon to the NMS as root.
2. At the # prompt, enter the following command:
service idirect_nms status
The output indicates the processes as either stopped or running. The event history of the
NMS monitor can be viewed in the nms_monitor.log file. Each event is listed with a date
and time stamp. This file is located in the /home/nms/utils/ directory. Optionally,
nms_monitor can send email to a designated recipient indicating the restart condition.
The email capability requires Linux sendmail to be configured on the NMS server. iDirect
recommends setting up sendmail only if your NMS Server is behind a firewall.
1.2
vii
Note: As part of a periodic maintenance schedule, inspect the servers (NMS and Protocol
Processor Blades) for physical damage. Verify LED status during scheduled maintenance
periods.
In the event that you experience a partial disk failure, contact the iDirect TAC for support.
You can also contact IBM technical support directly.
viii
2.1
Where:
ipaddr = the IP address of the Backup NMS Server.
1. Developed by SSH Communications Security Ltd., Secure Shell is a program that allows you to log into another computer over
a network to execute commands on a remote machine, and to move files from one machine to another. It provides strong
authentication and secure communications over insecure channels. It is a replacement for rlogin, rsh, rcp, and rdist. SSH protects
a network from attacks such as IP spoofing, IP source routing, and DNS spoofing.
vii
Where:
ipaddr = the IP address of the Backup NMS Server.
9. Verify that this prodecure was a success by repeating Step 6. If you are not prompted for
a password, the procedure was successful.
2.2
1. On the Backup NMS Server, create a directory called backup in the /root directory by
entering:
cd /root
mkdir backup
2.
On the Primary NMS Server, backup and restore scripts and .ini files are contained in
/home/nms/utils/db_maint. Using the vi editor, add the following line to the
dbBackup.ini script for each target db backup machine you want to use:
root@ipaddr:/root/backup
Where:
addr = the IP address of each backup server receiving the backup files.
The backup process creates two archive files, one for each DB: nms.##########.tgz and
nrd_archive.##########.tgz, where ### is a random number.
2.3
viii
Saving more than two copies uses more disk space on the Primary NMS.
5. If you only want to backup your archive database, make the command line cd=nms a
comment by adding the # character to the beginning of the line, shown as follows:
#cd=nms
ix
3.1
Where:
backup_nms_ipaddr = the IP address of the Backup NMS Server.
vii
3.2
5. Optionally, copy the database to the Backup NMS Server by adding the following command
line to the dbBackup.ini file:
root@backup_nms_ipaddr:/root/backup-server_name
Where:
backup_nms_ipaddr = the IP address of the Backup NMS Server
server_name = the name of the Auxiliary Server.
Note:
If the line already exists in the file and you do not want to backup the database,
comment out this line by inserting a # at the beginning of the line, as shown:
#root@backup_nms_ipaddr:/root/backup-server_name
6. Open the crontab file for editing by entering the following command:
crontab e
viii
3.3
6. Open the crontab file for editing by entering the following command:
crontab e
ix
4 Configuring dbRestore
Script Parameters
This section provides the procedure to configure the dbRestore script parameters.
4.1
Note:
The cron job1 performs the restore on the backup mahine nightly.
2. Open the vi editor and press the I key to turn on Insert Mode.
3. Add the following line:
30 1 * * * /home/nms/utils/db_maint/dbRestore>>/home/nms/utils/db_maint/dbrestore.output
2>&1
vii
viii
5.1
vii
1. Record any static routes that are configured on the Primary NMS Server.
2. On the primary NMS, run the backup script to ensure that you have an up-to-date
database on the Backup NMS Server. If the database is not up-to-date, copy any necessary
files over as required.
3. In addition to the database files, additional component files must be copied, shown in
their appropriate directories, as follows:
/home/nms/cfg/options_files/modems
/home/nms/cfg/options_files/rmtdefs
/home/nms/cfg/options_files/chassis
/home/nms/cfg/options_files/pp_globals
/home/nms/cfg/options_files/netdefs
Where:
filename.tar = is the name of the compressed file that contains the component name.
(for example: tar -cvf modems.tar modems).
source file name or directory = is the original name of the file, as displayed in
Step 3. (For example, the first line shows the directory and file name of
/home/nms/cfg/options_files/modems. The source file name is modems).
5. Repeat Step 4 for each component directory, using the commands as follows:
5a. Enter tar cvf modems.tar modem
5b. Enter tar cvf rmtdefs.tar rmtdefs
5c. Enter tar cvf chassis.tar chassis
5d. Enter tar cvf pp_globals.tar pp_globals
5e. Enter tar cvf netdefs.tar netdefs
You are now ready to copy the files you compressed from the Primary NMS Serer to the Backup
NMS Server.
viii
Where:
filename.tar = the name of the compressed file that you created in Step 4.
(for example: modems.tar)
ipaddr = the IP address of the Backup NMS Server.
2. Repeat Step 1 for each component options file, using the commands as follows (you can
refer to Step 1 to understand the elements of this command):
2a. Enter:
scp / modems.tar root@nnn.nnn.nnn:/home/nms/cfg/options_files/
2b. Enter:
scp / rmtdefs.tar root@nnn.nnn.nnn:/home/nms/cfg/options_files/
2c. Enter:
scp / chassis.tar root@nnn.nnn.nnn:/home/nms/cfg/options_files/
2d. Enter:
scp / pp_globals.tar root@nnn.nnn.nnn:/home/nms/cfg/options_files/
2e. Enter:
scp / netdefs.tar root@nnn.nnn.nnn:/home/nms/cfg/options_files/
Now that you have compressed and copied all of the required files, you are ready to extract
these files onto the Backup NMS Server.
modems
netdefs
pp_globals
rmtdefs
ix
Where:
filename.tar = the name of the compressed file that you created in Step 4.
(for example: modems.tar)
5. Repeat Step 4 for each component file, using the commands as follows:
5a. Enter tar xvf modems.tar
5b. Enter tar xvf rmtdefs.tar
5c. Enter tar xvf chassis.tar
5d. Enter tar xvf pp_globals.tar
5e. Enter tar xvf netdefs.tar
Now that you have moved the component files to the Backup NMS Server successfully, you are
ready to move the pp_controller files.
5.2
6 root
root
4096 Sep
4 23:18 .
drwxr-xr-x
82 root
root
8192 Sep
5 14:17 ..
drwx------
3 root
root
drwxr-xr-x
2 root
root
4096 Sep
4 23:18 map
drwxr-xr-x
3 root
root
4096 Sep
5 20:35 pp_controller_15001
drwxr-xr-x
3 root
root
5. Compress all of the pp_controller files (as displayed in previous step) in the 15000 range
by entering the following command for each pp_controller that is listed above
tar -cvf pp_controller_1500n.tar pp_controller_1500n
Where:
n = the number of the pp_controller for which you are extracting files, and is listed when
you list the contents of the /etc/idirect directory.
Note:
Where:
filename.tar = the name of the compressed file that you created in the previous
procedure, Step .
(for example: pp_controller_15002.tar)
ipaddr = the IP address of the Backup NMS Server.
xi
Now that you have compressed and copied all of the required files, you are ready to extract
these files onto the Backup NMS Server.
filename.tar = the name of the compressed file that you created in Step 4.
(for example: pp_controller_15002.tar)
6 root
root
drwxr-xr-x
82 root
root
8192 Sep
drwx------
3 root
root
drwxr-xr-x
2 root
root
4096 Sep
5 14:17 ..
4 23:18 map
-rwxr--r-1 root
pp_controller_15001.tar
root
drwxr-xr-x
3 root
root
drwxr-xr-x
3 root
root
4096 Sep
5 20:35 pp_controller_test
xii
pp_controller_15001/networks/1.net/netdef.opt
pp_controller_15001/networks/1.net/remote_5035562.opt
pp_controller_15001/networks/1.net/remote_5034935.opt
pp_controller_15001/networks/2.net/
pp_controller_15001/networks/2.net/netdef.opt
pp_controller_15001/networks/2.net/remote_6078612.opt
pp_controller_15001/networks/2.net/remote_12857401.opt
pp_controller_15001/networks/6.net/
pp_controller_15001/networks/6.net/netdef.opt
pp_controller_15001/networks/6.net/remote_10491435.opt
pp_controller_15001/networks/10.net/
pp_controller_15001/networks/10.net/netdef.opt
pp_controller_15001/networks/10.net/remote_6345822.opt
pp_controller_15001/controller.conf
pp_controller_15001/global.opt
pp_controller_15001/x509_local_key.txt
pp_controller_15001/x509_local_cert.txt
5.3
2. If the primary NMS remains connected to the network, the iDirect NMS services MUST be
shutdown with the command below and the IP address must be different. Additionally,
these services MUST remain down while the other new (backup) NMS server is online.
service idirect_nms stop
3. Verify that the routing configuration on the Backup NMS Server is correct. If RIP v2 was
running on the Primary NMS Server, it has to be running on the backup. Any static routes
that were configured on the Primary NMS Server need to be configured on the Backup NMS
Server. Make sure they are configured as persistent routes so they remain in effect after a
reboot.
xiii
4. Configure Backup NMS Server eth0 interface with the primary NMS original eth0 interface
address. The reason for this is to match the original primary NMS IP address that is
configured in the configuration (options) files of the iDirect network elements.
5. Reboot the Backup NMS Server machine or restart the network services entering the
following command:
service network restart
6. Verify the new Primary NMS Server routing table by entering the following command:
netstat r -n
9. The network should now be running on the Backup NMS Server. The status on the Line
Cards and the Remotes should be normal in iMonitor.
10. If needed, apply the Protocol Processor level and network level configuration to all
networks via iBuilder.
2. Make the command lines in the crontab file comments by adding a # in front of the each
command line.
3. Adding the following lines:
30 0 * * * /home/nms/utils/db_maint/dbBackup >>
/home/nms/utils/db_maint/dbbackup.output 2>&1
30 1 * * * /home/nms/utils/db_maint/cons.pl >>
/home/nms/utils/db_maint/cons.output 2>&1
4. Press Esc to exit Edit Mode.
5. Save and close the crontab file by entering the following command:
xiv
wq!
6. To configure the new (Backup) NMS Server to start the NMS services every time at bootup, enter the following command:
chkconfig --level 2345 idirect_nms on
The backup is a success if there is no data output after entering this command.
xv