Cisco Media Gateway Control Node Manager Installation Guide, 2.4.1
Installing the Provisioning Tool
Download this chapter
Installing the Provisioning ToolInstalling the Provisioning Tool
give_us_feedback

Table Of Contents

Installing Cisco MNM-PT

Installing MNM-PT Version 2.4(1)

Planning and Setting Up for Backup and Restore

Specify a Backup User ID During Installation

Select a Backup Host

Enable TFTP on the Backup Host

Installing SSH on MNM-PT

Uninstalling SSH on MNM-PT

Starting MNM-PT

Exiting the Voice Services Provisioning Tool

Installing an Earlier Version of MNM-PT

Upgrading MNM-PT

Uninstalling MNM-PT


Installing Cisco MNM-PT

The Cisco MGC Node Manager Provisioning Tool (MNM-PT) provides an easy-to-use graphical tool to provision the Cisco PGW 2200 Softswitch running the Cisco MGC software.

Note In previous releases the Cisco MGC Node Manager Provisioning Tool was packaged separately and known as Voice Services Provisioning Tool (VSPT).

Individual releases of MNM-PT are designed to be used with specific releases of the Cisco MGC software. MNM-PT Version 2.4(1) is designed to be used with Cisco MGC Version 9.4(1) If you are using a different release of the Cisco MGC software, see Determine the Correct Provisioning Tool Version to identify the release of MNM-PT that you need.

•Installing MNM-PT Version 2.4(1)

–Planning and Setting Up for Backup and Restore

–Installing SSH on MNM-PT

•Installing an Earlier Version of MNM-PT

•Upgrading MNM-PT

•Uninstalling MNM-PT

Installing MNM-PT Version 2.4(1)

Before installing MNM-PT version 2.4(1), verify the following:

•You want to provision the Cisco PGW 2200 Softswitch running Cisco MGC software version 9.4(1). If you are provisioning an earlier version, see Determine the Correct Provisioning Tool Version

•You have met the workstation hardware and software requirements. See Determine Your Hardware Requirements

•You have established network connectivity between your workstation and the network elements.

•The network elements have the correct release of software installed. See Chapter 2, Task 2: Ensure That Network Devices Have the Correct Software, page 2-3.

•You have identified your desired installation configuration, one of the options described in Determine the Correct Provisioning Tool Version.

•You have decided if you are installing SSH for secure communications with SSH-enabled components.

Note MNM-PT installation must be carried out from the MNM-PT server or a machine with X window capability. Make sure you have root access on your Sun workstation.

Before you begin provisioning, you should have a list of components you want to provision, including the component names, IP addresses, properties, and other parameters. To create this list, use the instructions provided in the Cisco Media Gateway Controller Software Version 9 Provisioning Guide at http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/prvgde/index.htm.

Tip In addition, descriptions of the properties and values contained in MNM-PT are included in Appendix A of the Cisco Media Gateway Controller Software Version 9 Provisioning Guide and in the Cisco MGC Node Manager Provisioning Tool User's Guide. Review this information before you begin provisioning, and keep it available for reference during provisioning.

To install MNM-PT Version 2.4(1), follow this procedure:

Step 1 Verify that the requirements listed in the "Determine Your Hardware Requirements" section have been met.

Step 2 Openan X terminal window.

Step 3 If you are not already logged in as root, become the root user by entering the following command: 

>su - root

Step 4 If you have not already done so, place the Cisco MGC Node Manager installation media into the CD-ROM drive.

Step 5 Enter cd /cdrom/cscocmnm.

Step 6 Enter ./cmnminstall

The Install Package opens and displays the following options: 

1)	CMNM    V.2.4.1 Package	

2)	CMNM-PT V.2.4.1 Package

3)	CMNM-PT V.2.3.2 Package

4)	CMNM-PT V.2.2.2 Package

5)	CMNM-PT V.1.6.4 Package

6)	CMNM-PT V.2.2.2 patch

7)	CMNM-PT V.1.6.4 patch


q)	Quit

Existing installations of any of the installation software are detected and are listed as "Already Installed".

Step 7 Enter 2 to install Cisco MGC Node Manager-Provisioning Tool 2.4(1).

The MNM-PT InstallShield Wizard opens.

Step 8 Follow the onscreen prompts.

Note During installation you are asked to designate a Backup User ID. Only a user logged in with this ID may carry out backup and restore operations. See Specify a Backup User ID During Installation for more information.

Step 9 If you are using the MNM-PT Backup and Restore feature, enable TFTP on the backup server. See Planning and Setting Up for Backup and Restore.

Step 10 If you are installing SSH for MNM-PT, see Installing SSH on MNM-PT.

Step 11 Go on to Starting MNM-PT.

Table 3-1 defines the default MNM-PT directories and files.

.

Table 3-1  Provisioning Tool Installation Directories and Files

/opt/CSCOvsp24

vspt

Provisioning Tool application script

classes/

Class and property files

/docs

 

/help

 

images/

 

jre/

Java Runtime Environment

/netscape

Netscape web browser files

uninstall/

Uninstall script directory

/utils

 

version

Provisioning Tool version

   

/var/opt/CSCOvsp24 (home directory)

data/

Configuration files

logs/

Log files

/etc

 

Note The directories and files listed in Table 3-1 are for the most recent version of MNM-PT. Your directory structure may be different if you are using an older version.

Planning and Setting Up for Backup and Restore

You typically use MNM-PT Backup to back up the configuration on a supported component, such as a Cisco PGW 2200, onto a different server, which we will call the backup host. The configuration can then be restored if needed back to the original machine.

For example, if you are backing up a Cisco PGW 2200 host, MNM-PT logs into the Cisco PGW 2200 host, copies the configuration, and the Cisco PGW 2200 transfers it to the backup host using TFTP. The Backup host must have TFTP enabled.

If you are going to use Backup and Restore, you should do the following, as described below:

•Specify a Backup User ID During Installation

•Select a Backup Host

•Enable TFTP on the Backup Host

Specify a Backup User ID During Installation

During MNM-PT installation, you are prompted for a Backup ID. The Backup ID is the UNIX ID of a user account authorized to use MNM-PT to perform configuration backups. Depending on your security policy, this may be the ID of a particular individual, or an ID created specifically for the purpose and usable by one or more individuals authorized to perform backups.

Starting MNM-PT for a backup operation: In order to schedule backups or perform immediate backups, MNM-PT must be started from a UNIX shell with the backup ID, in either of two ways:

•If MNM-PT is launched from Cisco MGC Node Manager (Cisco MNM), the user must have started the Cisco EMF client with the Backup ID. If the user's normal ID is different from the Backup ID, the user must start a new Cisco MNM session with the Backup ID.

•From the command line in a UNIX shell opened with the Backup ID

If You Reinstall MNM-PT with a Different Backup ID

If you reinstall MNM-PT and select a different Backup ID, you must manually delete two files that are not automatically removed in reinstallation. (This is because the files are read-only and owned by root.)

Step 1 Log in as root.

Step 2 Change to this directory:

/var/opt/CSCOvsp24/logs/

Step 3 Delete these two files:

now.log

testValidTFTP

Select a Backup Host

The backup host to which configurations are copied may be any of the following:

•The same machine where Cisco MGC Node Manager is installed (and typically Cisco MNM PT is also installed), referred to as the network management host

•The same machine where Cisco MNM PT is installed, if this is different from the Cisco MGC Node Manager machine, and if this is not a Cisco PGW 2200 host

•A separate machine used for backups

Note Using a Cisco PGW 2200 host as a backup host is not recommended and is specifically not supported if you are using SSH.

Enable TFTP on the Backup Host

MNM-PT uses TFTP (Trivial File Transfer Protocol) as the transfer utility to transfer configuration files from the Cisco PGW (or BAMS) to the backup host. Although UNIX systems include TFTP, by default it is not enabled. To be able to send configuration files to a backup host, you must first enable TFTP on that host.

Before you begin: Make sure that you are using a Solaris or Solaris-like TFTP server. Unlike some TFTP servers, the Sun Solaris TFTP server will allow a file to be written to the server using TFTP only if the file already exists on the system and is writable by the root user. TFTP software with the behavior of the Solaris TFTP software must be used (the file must exist and have write permissions by the root user before the TFTP transfer will be successful). This is because MNM-PT creates the file with root write permission before attempting to back up the file via TFTP. TFTP server implementations that require the file not to exist before attempting the backup will not work.

To Enable TFTP

Step 1 In the file /etc/inetd.conf, uncomment this line:

# tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot

so that it is:

tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot

Step 2 Create the tftp user home directory:

# mkdir /tftpboot

# chown root /tftpboot

# chmod 777 /tftpboot

Step 3 Restart inetd:

# ps -ef | grep inetd*

# kill -HUP <inetd-pid>

Step 4 Verify that TFTP is working:

# cp /etc/hosts /tftpboot/.

# cd /tmp

# tftp <machine-name>

tftp> get hosts

Installing SSH on MNM-PT

The SSH security package used for MNM-PT is the same CSCOk9000 package used on the Cisco PGW 2200, BAMS, and HSI server. Installing this package on MNM-PT follows the same procedure as for those devices. In addition, you need to check the modify a variable if the base path of ssh and sftp is not the default.

Before you begin: MNM-PT should have software version 2.4(1) installed.

Note We recommend installing SSH on MNM-PT (and Cisco MGC Node Manager) before installing it on the Cisco PGW, so that you can use the element managers to monitor the installation process on the PGW and other managed components.

Step 1 Download the security package, CSCOk9000. You must first secure authorization.

Note There are U.S. Government restrictions on exporting cryptographic technology. The Secure Shell (SSH) program falls under the umbrella of those restrictions. The security package (CSCOk9000) is registered and located in a restricted area from which only authorized customers can download.

Step 2 Stop MNM-PT.

If MNM-PT is co-resident on the Cisco PGW server and CSCOk9000 is already installed, go on to Step 3. If not, go on to Step 2.

Step 3 Install the CSCOk9000 package on the MNM-PT server machine. For instructions, refer to the steps in Cisco PGW 2200 Security Enhancements, "Installing CSCOk9000 on the Cisco PGW 2200 Host", http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/mgcfm/941fm/fmsecenh.htm.

Step 4 If the base path of ssh and sftp is not the default /opt/ssh/bin, modify the sshPath variable in the configuration file:

/opt/CSCOvsp24/classes/com/cisco/transpath/dart/editor/configEditor.properties

sshPath=/usr/local/bin

where /usr/local/bin is the location where ssh and sftp are installed.

After installing the CSCOk9000 package, both secure and nonsecure utilities are enabled. Users can use Telnet or ssh, FTP or sftp. If you want to disable nonsecure utilities, go on to Step 5.

Step 5 (Optional) To disable nonsecure utilities, use the following toggles:

Note The scripts toggle_telnet.sh and toggle_ftp.sh, are located in the /opt/sun_install directory.

•To disable FTP (only sftp will be available):

/opt/sun_install/toggle_ftp disable

•To reenable FTP (both FTP and sftp will be available):

/opt/sun_install/toggle_ftp enable

Uninstalling SSH on MNM-PT

•If you need to uninstall SSH, use the procedure described in Cisco PGW 2200 Security Enhancements, "Fallback Procedures" at http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/mgcfm/941fm/fmsecenh.htm.

This reenables FTP and Telnet and uninstalls the CSCOk9000 package.

Starting MNM-PT

You can start MNM-PT standalone from the operating system or you can start it from Cisco MGC Node Manager.

Note See the Cisco Media Gateway Controller Software Version 9 Installation and Configuration Guide for information on setting up user privileges and access rights.

Perform the following steps to start the Voice Services Provisioning Tool:

Step 1 Do one of the following:

•Start MNM-PT standalone:

–Log in to the MNM-PT server or access it from a machine with X window capability.

–In a terminal window, change to the default directory, typically:

–>cd /opt/CSCOvsp24

–Enter the following command to start MNM-PT:

–>./vspt

•Start MNM-PT from Cisco MGC Node Manager:

–Before starting Cisco MGC Node Manager, log in as root.

–In the Map Viewer, choose Tools > Provisioning Tool.

The login screen shown in Figure 3-1 appears.

Figure 3-1 Login Screen

Step 2 Enter your user name and password, and click OK.

The default user uame is admin, and the password is also admin. The Welcome screen is displayed briefly during the login process, and the main window appears (see Figure 3-2).

Figure 3-2 Main MNM-PT Window

Exiting the Voice Services Provisioning Tool

You can exit the Voice Services Provisioning Tool at any time by performing one of these actions:

•Click File > Exit. Click OK at the resulting prompt.

•Click the close box in the upper right of the Voice Services Provisioning Tool screen. Click OK at the prompt.

Installing an Earlier Version of MNM-PT

Follow the procedure described in Installing MNM-PT Version 2.4(1), selecting the version you want to install. Note that you must install the base version before installing a patch.

Upgrading MNM-PT

To upgrade MNM-PT, you install the new version as described in Installing MNM-PT Version 2.4(1). Depending on the version you are upgrading from, you may need to take some steps beforehand:

•Because two versions of MNM-PT (such as MNM-PT 2.3(2) and 2.4(1)) can exist on the same system, when you are upgrading the older version is not automatically removed. If you do not want to use both versions, you can manually uninstall the older version. See Uninstalling MNM-PT. (Keeping the old version is harmless, however.) Uninstall removes the sofware, but not the configuration data files.

•If you want to use configuration files created in a previous version, you must copy them. Of course, the configuration will not include components new in the 9.4(1) release.

Uninstalling MNM-PT

If you upgrade to MNM-PT version 2.4(1) and no longer need an earlier version, follow these procedures to uninstall an earlier version.

The uninstallation process removes the /var/opt/<CSCOvsp2x> directory (where 2x is the MNM-PT release, such as 24 for release 2.4(1)) created by the installation process. If a directory contains a file that was not created during the installation process, it is not removed and is logged in the uninstall.log file. This might occur in the data and logs directories. All application data stored in the /var/opt/<CSCOvsp2x> directory is retained.

Note Since the uninstall directory and files are removed during uninstall, do not change to the /opt/CSCOvsp2x directory to run the uninstall script.

Step 1 Enter the following commands:

>su -root

>cd /

>/opt/CSCOvsp2x/uninstall/uninstall

Step 2 Proceed with the new MNM-PT software installation (see Installing MNM-PT Version 2.4(1)).

Note If your next installation will specify a different Backup ID, you must manually delete certain files. See If You Reinstall MNM-PT with a Different Backup ID.