Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
Cisco MGC Software Release 9 Installation
Downloads: This chapterpdf (PDF - 623.0KB) The complete bookPDF (PDF - 4.76MB) | Feedback

Cisco MGC Software Release 9 Installation

Table Of Contents

Cisco MGC Software Release 9 Installation

Before You Start

Cautions, Notes, and Tips

Cisco MGC Software Installation/Uninstallation Sequence

Installing the Cisco MGC Software 9.2(x) and Higher Releases

Installing on a Simplex System

Installing on a Fault Tolerant System

Installing the Cisco Security Package (CSCOh013)

Removing the Cisco Security Package (CSCOh013)

Verification Test Suite (VTS) Package (CSCOh014) Overview

Installing the VTS Package

Using the SunVTS Test Package

Normal Unit Test

Running a Test in Brief Mode

Running a Test in Full Mode

vts_script Execution Times

Removing SunVTS

Removing the VTS Package (CSCOh014)


Cisco MGC Software Release 9 Installation


This chapter describes how to install Releases 9.2(x) and later releases of the Cisco Media Gateway Controller (MGC) software.


Note In Release 7.4 and later, the Cisco MGC software files and processes are located in the /opt/CiscoMGC directory.


This chapter contains the following sections:

Before You Start

Cisco MGC Software Installation/Uninstallation Sequence

Installing the Cisco MGC Software 9.2(x) and Higher Releases

Installing the Cisco Security Package (CSCOh013)

Verification Test Suite (VTS) Package (CSCOh014) Overview


Note For information on configuring the Cisco MGC software, see the following publication:
Cisco Media Gateway Controller Software Release 9 Provisioning Guide.


Before You Start

Before you start, perform the following steps:

1. Review the hardware and software requirements found in the document Release Notes for the
Cisco Media Gateway Controller Software Release 9.

2. Have your company's internal support and Cisco support contact information readily available so you can get help with the installation if needed. (If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii of the Cisco support contact information.)

3. Ensure that you have access to the console port on your Cisco MGC host.

4. Before you begin installing the Cisco MGC software, make sure the Sun Operating System is properly installed. The following table provides the location of the installation procedure you may require.

Table 3-1 Installation Overview and Reference Sections

Installation Procedure
Refer to...

If the Sun Solaris 8 operating system is not yet installed, you must first install it...

Start with Chapter 2, "Sun Solaris 8 Operating System Installation."

If the Sun Solaris 8 operating system is already installed and you are installing the Cisco MGC software for the first time...

Follow the procedures found in the "Installing the Cisco MGC Software 9.2(x) and Higher Releases" section.


Cautions, Notes, and Tips


Caution To prevent the system from running out of disk space during installation and to avoid removal of data files and databases to compensate, you must first verify that there is enough hard disk space to support your intended installation. To get free space, you can delete the following files:

   - Unnecessary log files (platform*.log)
   - User-generated trace files (*.btr)
   - Call detail record (CDR) files (.bin or .csv)
   - Old *.tar files
   - User-generated toolkit files (in the /var/cust_specific/toolkit directory)


Caution Make sure to follow the Cisco MGC software installation and uninstallation sequence listed in "Cisco MGC Software Installation/Uninstallation Sequence" section.


Note For the software to work properly, you must reboot the system every time you modify any file in the /etc directory.



Note Monitor system output frequently for error messages during the installation process and correct any error conditions before continuing with the installation.



Tip Allow for at least 2 hours to install the Sun Solaris 8 operating system and approximately 1 hour to install the Cisco MGC software.


Cisco MGC Software Installation/Uninstallation Sequence


Note At this point, the Solaris Operating System 8 and Solaris Operating System 8 patch cluster package (CSCOh015) should be already installed on your system.


For the system to work properly, it is important that Cisco MGC software installation be performed in the following order:

1. Cisco MGC software

2. Solaris System Security Patch (CSCOh013)


Caution Software must be uninstalled in the reverse order in which it is installed. For example, you must first uninstall software package CSCOh013 before you uninstall the Cisco MGC software.


Note You do not have to uninstall the Cisco MGC if only software package CSCOh013 requires updating but the Cisco MGC does not.


Installing the Cisco MGC Software 9.2(x) and Higher Releases


Note For a sample output listing from the install.sh script, see Appendix D, "Sample Output from install.sh" section on page D-1.



Note Remove /usr/ucb from the path environment variable before the initial installation of the Cisco MGC software. However, if /usr/ucb is needed, make sure that it is located in the path variable in the user profile after /usr/sbin.



Note To enable the SIP Improved Failover Support feature, both PGW 2200 systems must be in same VLANs. A trunk line between the two switches must be connected and configured for the SIP Improved Failover Support feature to work. However, if SIP Improved Failover Support is not required on your system, then the trunk line is not mandatory.


Installing on a Simplex System

To install the Cisco MGC software, complete the following steps:


Step 1 Log in as root.

Step 2 Load the Cisco MGC software CD into the CD-ROM drive.

Step 3 To install the Cisco MGC software, enter the following commands:

# cd /cdrom/cdrom0
# ./install.sh

The following prompt is displayed:

Use supplied admin file for unattended install? [n] [y,n,?,q] 

Step 4 Answer y to perform an unattended installation. If you answer n, you must answer prompts and press Enter for each package that is installed.

The following prompt is displayed:

Base directory for Toolkit (default /opt/Toolkit) [?,q]
##########################################################################################
#
# The CSCOgu000 utilities package must be installed prior to other components             
#
# but has not been detected on your system.  This package contains all required system    
#
# parameters necessary for installing the rest of your software.  If you do not install   
#
# this package, the installation script will exit.                                        
#
##########################################################################################

Would you like to install it now? [y] [y,n,?,q] y

Step 5 Answer y if you want to install the Toolkit application on this host.

Step 6 The following prompt is displayed:

Base directory for CiscoMGC (default /opt/CiscoMGC) [?,q] 
Enter CiscoMGC user name [mgcusr]  
Enter CiscoMGC UID [20000] 
Enter CiscoMGC group name [mgcgrp] 
[mgcgrp] group already exists - continuing
[mgcusr] user added
Modifying /etc/init.d/inetinit name is non-existent for this module for a list of valid 
names, use name'?'

We recommend that you accept the default values (by pressing Enter). You can, however, specify a different user ID and a group ID. If the ID you specify already exists on the system, the corresponding ID will be determined and reused, or you will be prompted to enter another ID.


Caution No validation is performed on the IDs you enter. If you enter an invalid ID, the utilities package does not add any accounts.

The system returns the following message, stating that the CSCOgu000 utilities package was successfully installed:

Installation of <CSCOgu000> was successful.
(c)1998 Cisco Systems, Inc. All Right Reserved. Unpublished -- rights reserved under the 
copyright laws of the United States. RESTRICTED RIGHTS LEGEND. Use, duplication, or 
disclosure by the Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 
252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software --
Restricted Rights at 48 CFR 52.227-19, as applicable.  Cisco Systems, Inc. 3615 Dulles 
Technology Drive Herndon, VA 20171 

Step 7 Depending on your system configuration, rebooting after a successful utilities package installation might not be necessary.


Note Rebooting may take approximately 5 minutes.


If a reboot is not required, the installation continues uninterrupted.

If a reboot is required, perform the following steps when prompted:

a. Type the following command displayed on the screen and press Enter.

# shutdown -y -g0 -i6

Note If the command shown on the screen does not work, you can enter the /usr/sbin/reboot command to reboot the system.



Note If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages below are displayed during system boot-up. They are normal Solaris DiskSuite start-up messages and do not indicate any problem with your system.

WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed


b. After the reboot finishes, restart install.sh to install the remaining packages. To restart install.sh, type the following commands at the # prompt and press Enter:

# cd /cdrom/cdrom0
# ./install.sh

The following prompts are displayed:

Use supplied admin file for unattended install? [n] [y,n,?,q]

c. Type y and press Enter.


Note This procedure can take approximately an hour to complete.


Text similar to the following is displayed, showing the packages that were installed:

Installation of <CSCOga000> was successful.
Uncompressing EISUP
Uncompressing ISDNIP
Uncompressing ISDNL3
Uncompressing LogServerd
Uncompressing MGCP
Uncompressing SIP
Uncompressing SS7
Uncompressing TALI
Uncompressing TCAP
Uncompressing almM
Uncompressing amDmpr
Uncompressing cdrDmpr
Uncompressing cfgM
Installing chk_inv
Uncompressing cms
Uncompressing converter
Uncompressing engine.no_smartalloc
Uncompressing engine.smartalloc
Uncompressing foverd
Uncompressing ioChanMgr
Uncompressing measMgr
Uncompressing mmBldCfg
Uncompressing mmdbd
Uncompressing mml
Uncompressing pom
Uncompressing procM
Uncompressing replicator
Installing libACE.so
Uncompressing lib_cmg.so
Uncompressing lib_cxn.so
Uncompressing lib_eng.so
Uncompressing lib_rmg.so
Installing libcms.so
Uncompressing libconvutil.so
Uncompressing libda.so
Uncompressing libmmdb.so
Uncompressing libpolbase.so
Uncompressing libpolcomp.so
Uncompressing libpolfiles.so
Uncompressing libpolnuman.so
Uncompressing libpolroute.so
Uncompressing libpom.so
Uncompressing libpxe.so
Uncompressing libpxelog.so
Uncompressing librudp.so
Uncompressing libsa.so
Installing libsunmath.so.1
Installing libtten.so
Uncompressing libxe.so
Updating parameters for CiscoMGC
Updating parameters for SW_Layout.cfg
Updating parameters for getConfig
Updating parameters for log_rotate.sh
Updating parameters for startAudit.sh
Updating parameters for diagdata
Updating parameters for .cshrc
Updating parameters for .dump-prov
Updating parameters for .master.cks
Updating parameters for actDPlan
Updating parameters for backup.sh
Updating parameters for cdbscript.sh
Updating parameters for config-lib
Updating parameters for diskmonitor.sh
Updating parameters for failover_nfs.sh
Updating parameters for getDPlan
Updating parameters for init.tcl
Updating parameters for listDPlan
Updating parameters for mgcbackup
Updating parameters for mgcrestore
Updating parameters for migrateDPlan.sh
Updating parameters for pmctrl
Updating parameters for reconfig-all.mml
Updating parameters for restore.sh
Updating parameters for rmsem.sh
Updating parameters for startAudit.mml
Updating parameters for startLogServer
Updating parameters for stop-all
Installing /opt/CiscoMGC/man/mml.help.tar.gz

Installation of <CSCOga001> was successful.
Modifying /etc/syslog.conf
Updating parameters for .odbc.ini
Updating parameters for backupDb.sh
Updating parameters for restoreDb.sh
   Preparing to install TimesTen4.1 in /opt on va-jupiter
   Executing TimesTen installation script...

Installing 32-bit version...

Of the three components:

  [1] TimesTen Client/Server and Data Manager
  [2] TimesTen Data Manager Only
  [3] TimesTen Client Only

Begin installing in /opt/TimesTen4.1 ...
Creating /opt/TimesTen4.1 ...
Uncompressing...

The TimesTen Demo applications can take up to 64 Mbytes of 
disk space. Depending on
how your system is configured, you may not want to create the 
DemoDataStore directory in the default location : 
/var/TimesTen/TT4.1/32/DemoDataStore

Creating /var/TimesTen/TT4.1/32/DemoDataStore ...

System logging appears to be configured correctly.
(TimesTen syslog messages seem to be recorded in the file 
'/var/adm/messages')
Starting the daemon ...
Installing TimesTen Server...
Installing TimesTen Server startup/shutdown scripts...
The TimesTen Server has started successfully.
Creating new /var/TimesTen/sys.ttconnect.ini
Creating /opt/TimesTen4.1/doc ...
Extracting /opt/ttdb-install/doc/doc.tar ...
End of TimesTen installation.
TimesTen installation script returned status 0
   
Program complete
Restoring backup schema.
Sun Microsystems Inc.	SunOS 5.8	Generic	February 2000
Restoring database contents for DSN=howdydb from 
/opt/CiscoMGC/etc/export.ttdb
Restoring file /opt/TimesTen4.1/datastore/howdydb.ds0 from backup
Restoring file /opt/TimesTen4.1/datastore/howdydb.log0 from backup
The restore process is being initiated
Restore complete

Installation of <CSCOga002> was successful.
smpd.cnf up to date, no configuration upgrade required
Uncompressing mmSAgt
Uncompressing sagt
Uncompressing libsa.so
Updating parameters for CiscoMGC
Updating parameters for snmpd
Updating inittab

Installation of <CSCOga003> was successful.
Installing /opt/Toolkit/Packages/Packages.tar.gz
Installing /opt/Toolkit/bytecode/XECfg/XECfg.tar.gz
Installing /opt/Toolkit/bytecode/am/am.tar.gz
Installing /opt/Toolkit/bytecode/cdr/cdr.tar.gz
Installing /opt/Toolkit/bytecode/log/Viewer.tar.gz
Installing /opt/Toolkit/bytecode/toolbar/toolbar.tar.gz
Installing /opt/Toolkit/bytecode/tv/tv.tar.gz
Installing /opt/Toolkit/gif/gif.tar.gz
Installing /opt/Toolkit/mibs/common/common.tar.gz
Installing /opt/Toolkit/tcl/tcl.tar.gz
Updating parameters for MGC_Setup
Updating parameters for MGC_Toolkit
Updating parameters for init.tcl
Updating parameters for toolbar.sh
Setting VERSION=9.2(2) in version.dat

Installation of <CSCOga004> was successful.
Installing ca
Installing callver
Installing get_trc.sh
Installing sim
Installing simWriter
Installing siptool
Installing sp

Installation of <CSCOgt001> was successful.
Updating parameters for XECfgParm.dat
Updating parameters for trigger.template
Updating parameters for migrate
Updating parameters for migrateTKGFile
Installing /opt/CiscoMGC/etc/CONFIG_LIB/migrate_mod.tar.gz
Installing /opt/CiscoMGC/etc/migrate/migrate_scr.tar.gz
Migrating .dat files in /opt/CiscoMGC/etc
Checking dialPlan dir: /opt/CiscoMGC/dialPlan/*.dialPlan
Backing up dialPlans
Checking dialPlan dir: /opt/CiscoMGC/dialPlan/*.bin
Backing up binary dialplans
Backing up .dat file
Backing up database
Sun Microsystems Inc.	SunOS 5.8	Generic	February 2000
migrate_XECfgParm: setting *.transpathId = 01
migrate_XECfgParm: setting *.ownTranspathId = 01
migrate_XECfgParm: setting *.peerTranspathId = 02
migrate_XECfgParm: setting *.MGC_CDR_NODE_ID = MGC-CDR-NODE-STRING
migrate_XECfgParm: setting foverd.conn1Type = socket
migrate_XECfgParm: setting foverd.conn2Type = socket
migrate_XECfgParm: setting *.IP_Addr1 = 10.1.0.16
migrate_XECfgParm: setting *.IP_Addr2 = 10.129.0.16
migrate_XECfgParm: setting *.IP_Addr3 = 0.0.0.0
migrate_XECfgParm: setting *.IP_Addr4 = 0.0.0.0
migrate_XECfgParm: setting *.ipAddrLocalA = 10.1.0.16
migrate_XECfgParm: setting *.ipAddrLocalB = 10.129.0.16
migrate_XECfgParm: setting *.ipAddrPeerA = 10.1.0.17
migrate_XECfgParm: setting *.ipAddrPeerB = 10.129.0.17
migrate_XECfgParm: setting *.SysConnectDataAccess = true
migrate_XECfgParm: setting *.SysConnectDataAccess = true
migrate_XECfgParm: setting foverd.abswitchPort = /dev/null
migrate_XECfgParm: setting foverd.ipLocalPortA = 1050
migrate_XECfgParm: setting foverd.ipLocalPortB = 1052
migrate_XECfgParm: setting foverd.ipPeerPortA = 1051
migrate_XECfgParm: setting foverd.ipPeerPortB = 1053
migrate_XECfgParm: setting replicator.portDataChannelSend = 2968
migrate_XECfgParm: setting replicator.portDataChannelRecv = 2970
migrate_XECfgParm: setting replicator.portCommChannelSend = 2972
migrate_XECfgParm: setting replicator.portCommChannelRecv = 2974
migrate_XECfgParm: setting *.SyscheckpointEnabled = true
migrate_XECfgParm: setting *.desiredPlatformState = master
migrate_XECfgParm: setting *.stPort = 7000
migrate_XECfgParm: setting pom.dataSync = true
migrate_XECfgParm: setting *.chkPtPort = 2001
migrate_XECfgParm: setting engine.SysPropagateChanAvail = false
migrate_XECfgParm: setting engine.SysGeneratedCode = true
migrate_XECfgParm: setting engine.SysGRSTimerInterval = 0
migrate_XECfgParm: setting engine.SysGRSBlockSize = 0
migrate_XECfgParm: setting engine.AuditTimerInterval = 1000
migrate_XECfgParm: setting engine.MaxAuditCics = 32
migrate_XECfgParm: setting engine.StartUpAuditEnabled = false
migrate_XECfgParm: setting engine.SysVirtualSwitch = 1
migrate_XECfgParm: setting engine.SysMdlMemoryReduction = 1
migrate_XECfgParm: setting engine.CALL_MEM_BLOCK_SIZE = 0
migrate_XECfgParm: setting engine.CALL_MEM_CHUNK_SIZE = 0
migrate_XECfgParm: setting *.ClearingLocation = 0
migrate_XECfgParm: setting engine.MDLANumberScreening = 0
migrate_XECfgParm: setting *.DefaultLocation = 0
migrate_XECfgParm: setting *.detailedCallEventCapture = 1
migrate_XECfgParm: setting *.DataBaseAccessError = 0
migrate_XECfgParm: setting *.SelectTermCustGrpId = 0
migrate_XECfgParm: setting diskmonitor.Limit = 7
migrate_XECfgParm: setting diskmonitor.Threshold = 80
migrate_XECfgParm: setting diskmonitor.SoftLimit = false
migrate_XECfgParm: setting diskmonitor.CdrRmFinished = 0
migrate_XECfgParm: setting diskmonitor.CoreRmDays = 1
migrate_XECfgParm: setting diskmonitor.CfgRmDirs = 64
migrate_XECfgParm: setting *.logPrio = Error
migrate_XECfgParm: setting *.logDirectory = ../var/log
migrate_XECfgParm: setting *.logFileNamePrefix = platform
migrate_XECfgParm: setting engine.CDRencodingFormat = AnsiCDB
migrate_XECfgParm: setting engine.CDRtimeStamp = S
migrate_XECfgParm: setting engine.CDRmessageTypes = 

"1010,1020,1030,1040,1050,1060,1070"
migrate_XECfgParm: setting *.numberOfThreads = 2
migrate_XECfgParm: setting *.dataSourceName = howdydb
migrate_XECfgParm: setting *.maxNumLinks = 32
migrate_XECfgParm: setting *.maxLinksPerSessionSet = 4
migrate_XECfgParm: setting *.maxNumDChansPerIOCC = 504
migrate_XECfgParm: setting *.maxNumMGCPLinks = 1000
migrate_XECfgParm: setting *.GWClearChannelAlgorithm = null
migrate_XECfgParm: setting *.CallCutoffTimer = 0
migrate_XECfgParm: setting *.CPUTimerInterval = 3000
migrate_XECfgParm: setting *.dataCommitTime = 10
migrate_XECfgParm: setting ioChanMgr.sessionPauseTimer = 8
migrate_XECfgParm: setting ioChanMgr.resumeAckTimer = 1
migrate_XECfgParm: setting MML.timeout = 10000
migrate_XECfgParm: setting *.OverdecadicDigitsSupported = false

migrating XECfgParm.dat ...

starting migration ...
source and destination versions are the same, no need to migrate
copying files from source to destination
No data file changes required to support CMS
trigger.dat exists: not overwriting with trigger.template

Installation of <CSCOgc001> was successful.

The following prompt is displayed:

Would you like to add a protocol set to your system? [y] 
[y,n,?,q] y

Step 8 Select y to add a protocol set.


Note The protocols that you select are specific to your system requirements. These should be decided prior to installation.


The following prompt is displayed:

Please insert a two digit package identifier and type <enter>
If you choose to add all protocols to your system, type "all": <package identifier>

Step 9 You can do either of the following:

a. Type all and press Enter to add all the protocols to your system. If you do, more disk space will be used and the installation process will take some time.

b. For Cisco MGC Software Release 9.3(x) and later releases: Select the specific protocol(s) you need from the following table (instead of selecting all) and enter the protocol identifier(s).

################################### 
##        01       ##     02     ## 
################################### 
##  BTNUP_BTNR167  ##  IETF_SIP  ## 
##  BTNUP_IUP      ##            ## 
##                 ##            ## 
##                 ##            ## 
##                 ##            ## 
##                 ##            ## 
################################### 


SS7 Protocol Family PRI Protocol Family
########################  ####################
##       10           ##  ## 20             ##
########################  ####################
## ANSISS7_92         ##  ## ATT_41459      ##
## ANSISS7_C2         ##  ## ATT_41459_C2   ##
## ANSISS7_C3         ##  ## BELL_1268      ##
## ANSISS7_STANDARD   ##  ## BELL_1268_C2   ##
## GR317              ##  ## ETS_300_102    ##
## GR317_C2           ##  ## ETS_300_102_C2 ##
## GR317_C3           ##  ## ETS_300_172    ##
########################  ####################


Q761 Version 1 Protocol Family
##########################################################################################
##          30      ##         31    ##         32           ##       33                ## 
##########################################################################################
## ETS_300_121      ## Q761_BASE     ## Q761_GERMAN          ## Q761_SINGAPORE          ##
## ETS_300_356      ## Q761_BELG     ## Q761_INDIA           ## Q761_SINGAPORE_C2       ##
## HONGKONG         ## Q761_BELG_C2  ## Q761_KOREAN          ## Q761_TAIWAN             ##
## ISUPV1_POLI      ## Q761_BELG_C3  ## Q761_NEWZEALAND      ## Q761_THAILAND           ##
## Q761_ARGENTINA   ## Q761_CHILE    ## Q761_97VER_BASE      ## Q761_MALAYSIAN          ##
## Q761_ARGENTINA_C2## Q761_CHINA    ## Q761_PERU            ##                         ##
## Q761_AUSTRL      ## Q761_CHINA_C2 ## Q761_PORTUGAL        ##                         ##
## Q761_AUSTRL_C2   ## Q761_DANISH   ##                      ##                         ##
##########################################################################################

Q761 Version 2 Protocol Family                      Q761 Version 3 Protocol Family
###############################################     #################################
##        40          ##          41         ##     ##             50              ##
###############################################     #################################
##  ISUPV2_AUSTRIAN   ##  ISUPV2_NORWEGIAN   ##     ##  ISUPV3                     ##
##  ISUPV2_CZECH      ##  ISUPV2_NTT         ##     ##  ISUPV3_FRENCH              ##
##  ISUPV2_FINNISH96  ##  ISUPV2_SPANISH     ##     ##  ISUPV3_UK                  ##
##  ISUPV2_FRENCH     ##  ISUPV2_SWISS       ##     ##  ISUPV3_UK_AXE10            ##
##  ISUPV2_GERMAN     ##  ISUPV2_SWISS_C2    ##     ##  ISUPV3_UK_AXE10_BTNETCHAT  ##
##  ISUPV2_JAPAN      ##  ISUPV2_TELEFONICA  ##     ##  ISUPV3_UK_BTNETCHAT        ##
##  ISUPV2_KPNPB      ##  ISUPV2_TOKYO       ##     ##                             ##
##                    ##  ISUPV2_VIETNAM     ##     ##                             ##
###############################################     #################################


Q721 Protocol Family        Q767 Protocol Family
#######################     #################################################
##         60        ##     ##           70             ##        71       ##
#######################     #################################################
##  Q721_BASE        ##     ##  Q767_BASE               ##  Q767_RUSS      ##
##  Q721_BRAZILIAN   ##     ##  Q767_BRAZIL             ##  Q767_SINGAPORE ##
##  Q721_CHINA       ##     ##  Q767_COLOMBIA           ##  Q767_SPAN      ##
##  Q721_FRENCH      ##     ##  Q767_GUATEMALA          ##  Q767_SWED      ##
##  Q721_PHILLIPINE  ##     ##  Q767_INDONESIA          ##  Q767_TELSTRA   ##
##                   ##     ##  Q767_ITAL               ##  Q767_TURKISH   ##
##                   ##     ##  Q767_ITAL_INTERCONNECT  ##                 ##
##                   ##     ##  Q767_MEXICAN            ##                 ##
#######################     #################################################


Q931 Protocol Family
######################
##       80         ##
######################
##  Q931            ##
##  Q931_AUSTRALIA  ##
##  Q931_SINGAPORE  ##
##                  ##
##                  ##
##                  ##
##                  ##
##                  ##
######################

The following prompt is displayed:

Would you like to add another protocol set to your system? 
[y] [y,n,?,q] n

c. For Cisco MGC Software Release 9.2(x): Select the specific protocol(s) you need from the following table (instead of selecting all) and enter the protocol identifier(s).

Miscellaneous Protocols                 SS7 Protocol Family
###################################     #########################
##        01       ##     02     ##     ##          10         ##
###################################     #########################
##  BTNUP_BTNR167  ##  IETF_SIP  ##     ##  ANSISS7_92         ##
##  BTNUP_IUP      ##            ##     ##  ANSISS7_CLEAR      ##
##                 ##            ##     ##  ANSISS7_MCI        ##
##                 ##            ##     ##  ANSISS7_STANDARD   ##
##                 ##            ##     ##  GR317              ##
##                 ##            ##     ##  GR317_C1           ##
##                 ##            ##     ##  GR317_NOTPTX       ##
##                 ##            ##     ##                     ##
###################################     #########################


PRI Protocol Family
########################################
##       20       ##       21         ##
########################################
##  ATT_41459     ##  ETS_300_102     ##
##  ATT_41459_C2  ##  ETS_300_102_C1  ##
##  BELL_1268     ##  ETS_300_121     ##
##  BELL_1268_C3  ##  ETS_300_172     ##
##                ##  ETS_300_356     ##
##                ##                  ##
##                ##                  ##
########################################


Q761 Version 1 Protocol Family
#########################################################################################
##          30           ##         31        ##         32           ##       33      ##
#########################################################################################
##  Q761_ARGENTINA       ##  Q761_CHILE       ##  Q761_97VER_BASE     ##  HKTA_2202    ##
##  Q761_ARGENTINA_C2    ##  Q761_CHINA       ##  Q761_PERU           ##  ISUPV1_POLI  ##
##  Q761_AUSTRL          ##  Q761_CHINA_MOB   ##  Q761_PORTUGAL       ##               ##
##  Q761_AUSTRL_C2       ##  Q761_DANISH      ##  Q761_SIEMENS_MOBI   ##               ##
##  Q761_BASE            ##  Q761_INDIA       ##  Q761_SINGAPORE      ##               ##
##  Q761_BELG_BCOM       ##  Q761_KOREAN      ##  Q761_SINGAPORE_C2   ##               ##
##  Q761_BELG_ISUP_CUJO  ##  Q761_NEWZEALAND  ##  Q761_TAIWAN         ##               ##
##  Q761_BELG_MOBI       ##                   ##  Q761_THAILAND       ##               ##
#########################################################################################


Q761 Version 2 Protocol Family                      Q761 Version 3 Protocol Family
###############################################     #################################
##        40          ##          41         ##     ##             50              ##
###############################################     #################################
##  ISUPV2_AUSTRIAN   ##  ISUPV2_NORWEGIAN   ##     ##  ISUPV3                     ##
##  ISUPV2_CZECH      ##  ISUPV2_NTT         ##     ##  ISUPV3_FRENCH              ##
## ISUPV2_FINNISH96   ##  ISUPV2_SPANISH     ##     ##  ISUPV3_UK                  ##
## ISUPV2_FRENCH      ##  ISUPV2_SWISS       ##     ##  ISUPV3_UK_AXE10            ##
## ISUPV2_GERMAN      ##  ISUPV2_SWISS_C2    ##     ##  ISUPV3_UK_AXE10_BTNETCHAT  ##
## ISUPV2_JAPAN       ##  ISUPV2_TELEFONICA  ##     ##  ISUPV3_UK_BTNETCHAT        ##
## ISUPV2_KPNPB       ##  ISUPV2_TOKYO       ##     ##                             ##
##                    ##  ISUPV2_VIETNAM     ##     ##                             ##
###############################################     #################################


Q721 Protocol Family        Q767 Protocol Family
#######################     #################################################
##         60        ##     ##           70             ##        71       ##
#######################     #################################################
##  Q721_BASE        ##     ##  Q767_BASE               ##  Q767_RUSS      ##
##  Q721_BRAZILIAN   ##     ##  Q767_BRAZIL             ##  Q767_SINGAPORE ##
##  Q721_CHINA       ##     ##  Q767_COLOMBIA           ##  Q767_SPAN      ##
##  Q721_FRENCH      ##     ##  Q767_GUATEMALA          ##  Q767_SWED      ##
##  Q721_PHILLIPINE  ##     ##  Q767_INDONESIA          ##  Q767_TELSTRA   ##
##                   ##     ##  Q767_ITAL               ##  Q767_TURKISH   ##
##                   ##     ##  Q767_ITAL_INTERCONNECT  ##                 ##
##                   ##     ##  Q767_MEXICAN            ##                 ##
#######################     #################################################


Q931 Protocol Family
######################
##       80         ##
######################
##  Q931            ##
##  Q931_AUSTRALIA  ##
##  Q931_SINGAPORE  ##
##                  ##
##                  ##
##                  ##
##                  ##
##                  ##
######################

The following prompt is displayed:

Would you like to add another protocol set to your system? 
[y] [y,n,?,q] n

Step 10 Select one of the following options:

a. If you select y, you are prompted by the system to enter another protocol identifier (see Step 9).

a. If you select n, the installation of a stand-alone Cisco MGC is done and text similar to the following is displayed:

OK, no more protocols will be installed on your system
Uncompressing ASP_NotRealProtocol.mdo
Uncompressing ASP_NotRealProtocol.so
Uncompressing CALLVER.mdo
Uncompressing CALLVER.so
Uncompressing CALLVER_GENERIC_ANALYSIS.mdo
Uncompressing CALLVER_GENERIC_ANALYSIS.so
Uncompressing CALLVER_LCM.mdo
Uncompressing CDR_MAN.mdo
Uncompressing CDR_MAN.so
Uncompressing CONNECTION_PLANE_MANAGER.mdo
Uncompressing CONNECTION_PLANE_MANAGER.so
Uncompressing EISUP.mdo
Uncompressing EISUP.so
Uncompressing GENERIC_ANALYSIS.mdo
Uncompressing GENERIC_ANALYSIS.so
Uncompressing IN_TRIGGER.mdo
Uncompressing IN_TRIGGER.so
Uncompressing LEG_CONTROLLER.mdo
Uncompressing LEG_CONTROLLER.so
Uncompressing cc.mdo
Uncompressing cc.so
Uncompressing dummy.mdo
Uncompressing dummy.so
Uncompressing lcm.mdo
Uncompressing lcm.so

Installation of <CSCO00000> was successful.
Uncompressing Q761_ARGENTINA.mdo
Uncompressing Q761_ARGENTINA.so
Uncompressing Q761_ARGENTINA_C2.mdo
Uncompressing Q761_ARGENTINA_C2.so
Uncompressing Q761_AUSTRL.mdo
Uncompressing Q761_AUSTRL.so
Uncompressing Q761_AUSTRL_C2.mdo
Uncompressing Q761_AUSTRL_C2.so
Uncompressing Q761_BASE.mdo
Uncompressing Q761_BASE.so
Uncompressing Q761_BELG_BCOM.mdo
Uncompressing Q761_BELG_BCOM.so
Uncompressing Q761_BELG_ISUP_CUJO.mdo
Uncompressing Q761_BELG_ISUP_CUJO.so
Uncompressing Q761_BELG_MOBI.mdo
Uncompressing Q761_BELG_MOBI.so

Installation of <CSCO30000> was successful.
Beginning Check of System Performance Requirements

Number of CPUs in system  4
Memory size: 4096 Megabytes
The sparcv9 processor operates at 440 MHz,

Swap is total: 36912k bytes allocated + 24272k reserved = 


61184k used, 5446792k available
Please Verify that you have over 4000000K Available swap

install.sh: setting *.numberOfThreads = 2
Shutting down TimesTen Server: done.
Installation completed Fri Feb 22 10:56:24 EST 2002 
Installation log can be found in /var/adm/MGC_install.log

Step 11 Use the following command to set a new password for mgcusr:

# passwd mgcusr

Step 12 Type eject and press Enter to open the door to the CD-ROM drive. Remove the Cisco MGC software CD.

Step 13 Proceed to the "Installing the Cisco Security Package (CSCOh013)" section and follow the CSCOh013 installation procedures.


Note Install the CSCOh013 security package for both simplex and fault tolerant (duplex) systems.


Step 14 Type eject and press Enter to open the door to the CD-ROM drive. Remove the Cisco MGC software CD.



Note During installation of the Cisco MGC software, the system is automatically installed, using a standard performance profile satisfactory for both nailed and switched solutions.


This completes the installation of the Cisco MGC software for a simplex configuration. You can now begin configuring your Cisco MGC software in the "Configuring Groups and Users" section on page 5-10.

For a sample install.sh log file, see Appendix D, "Sample Output from install.sh" section on page D-1.

See the Cisco Media Gateway Controller Provisioning Guide for information on provisioning the Cisco MGC software on a simplex system.

If you have a redundant configuration, continue to the section "Installing on a Fault Tolerant System" section.

If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.

Installing on a Fault Tolerant System


Caution To ensure the successful installation of a fault tolerant configuration, you must first provision the software for the active Cisco MGC host after Step 7 of the "Installing on a Simplex System" section before proceeding to Step 1, below. Refer to the Cisco Media Gateway Controller Provisioning Guide for information about the following:

- Provisioning the active Cisco MGC host
- Procedures for converting the active Cisco MGC host to standby host

Note that only one active provisioning session is permitted and provisioning is only permitted on the active Cisco MGC host.

Exit the provisioning session on the active host and continue to Step 1, below. If software is not provisioned after it is installed on the active Cisco MGC host, the standby host will not be synchronized with the active host. As a result, a forced switchover may cause the switchover to fail.

To install the Cisco MGC software on a fault tolerant system (with two Cisco MGC hosts and Cisco SLTs), complete the following steps:


Note The MGC_install.log and the MGC_pkgerrors.log are stored in the /var/adm directory.



Step 1 Continuing from Step 13 of the "Installing on a Simplex System" section, exit server 1.

Step 2 Log on to server 2 as root and go to the # prompt.

Step 3 Load the Cisco MGC software CD into the server 2 CD-ROM drive.

Step 4 Follow the instructions in "Installing on a Simplex System" section starting from Step 3.

Step 5 Configure the execution environment parameters and database replication for fault tolerant systems, using the following sections:

Configuring Switchover, page 5-41

Initializing the Provisioning Object Manager, page 5-43

Initializing the Call Screening Database, page 5-57


This completes the installation of the Cisco MGC software. Continue to the "Configuring Groups and Users" section on page 5-10 to configure groups and users. If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.


Note Always check CCO (http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml) to ensure that you have the latest required patch version released by Cisco on your system, CD, or file system (if downloaded previously from CCO).


Installing the Cisco Security Package (CSCOh013)

The system security patches install the Cisco Security Package. This package reduces the number of known system security vulnerabilities.


Note The Sun Solaris 8 operating system and Cisco MGC software must already be installed in your system before you can install the Cisco Security Package.

You must have system administrator privileges to install this package.



Caution If you are planning to use DiskSuite, you must first install it before installing the Cisco Security Package. For DiskSuite installation procedures, see the "Installing the Solstice DiskSuite (CSCOh016)" section on page 2-32.


Caution If you are planning to run mgcrestore, make sure you are installing the same version of the Cisco Security Package that was installed on your system when mgcbackup was run. Or, if the Cisco Security Package was not installed on your system when mgcbackup was run, you must first run mgcrestore before installing the Cisco Security Package.


Note During an HSI upgrade, the CSCOh013 security package must be installed after upgrading the HSI application and prior to uninstalling the previous HSI version. Otherwise, the installation of the CSCOh013 package will fail. This does not apply to new HSI installations.


Do the following procedures to install the Cisco Security Package:


Step 1 Before installing the Cisco Security Package, you must first determine the Solaris release version of the package installed on your system. Type the following command and press Enter:

pkginfo -l <package name>

The following is similar to the text that is displayed when the pkginfo command is used:

hostname% pkginfo -l CSCOh013
   PKGINST:  CSCOh013
      NAME:  Media Gateway Controller Security package compatible with Solaris 2.6 and 
Solaris 8
  CATEGORY:  utilities
      ARCH:  sparc
   VERSION:  2.0(1)
   BASEDIR:  /opt/sun_install
    VENDOR:  Cisco System, Inc.
    PSTAMP:  2002/02/25 20:56 GMT (liberty)
  INSTDATE:  Mar 06 2002 16:19
     EMAIL:  sctac@cisco.com
    STATUS:  completely installed
     FILES:      4 installed pathnames
                 2 shared pathnames
                 2 directories
                 2 executables
                57 blocks used (approx)


Note If you have an older version of the Cisco Security patch, you must remove it before installing the new patch. For package removal procedures, see Removing the Cisco Security Package (CSCOh013).


Step 2 Install latest version of the Cisco Security Package either by downloading the software from CCO or from a CD-ROM.

a. If you are downloading the software from CCO, store the Cisco Security Package on your UNIX platform. To determine the Solaris release version of the package you downloaded, use the following command:

pkg -l -d <package instance>.pkginfo

The following is similar to the text that is displayed when using the -d option with the pkginfo command:

hostname% pkginfo -l CSCOh013
   PKGINST:  CSCOh013
      NAME:  Media Gateway Controller Security package compatible with Solaris 2.6 and 
Solaris 8
  CATEGORY:  utilities
      ARCH:  sparc
   VERSION:  2.0(1)
   BASEDIR:  /opt/sun_install
    VENDOR:  Cisco System, Inc.
    PSTAMP:  2002/02/25 20:56 GMT (liberty)
  INSTDATE:  Mar 06 2002 16:19
     EMAIL:  sctac@cisco.com
    STATUS:  completely installed
     FILES:      4 installed pathnames
                 2 shared pathnames
                 2 directories
                 2 executables
                57 blocks used (approx)

b. If you are installing the software from a CD-ROM, insert the Solaris 8 Environment Patches for Cisco PGW CD into the CD-ROM drive.

Step 3 Enter one of the following commands at the # prompt:

a. If you are using the file downloaded from CCO, enter the following command:

# pkgadd -d ./CSCOh013.pkg

b. If you are installing from a CD-ROM, enter the following command:

# pkgadd -d /cdrom/cdrom0/CSCOh013.pkg

The following text is displayed:

The following packages are available:
  1  CSCOh013     Media Gateway Controller Security package compatible with Solaris 2.6 
and Solaris 8
                  (sparc) 2.0(1)

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 

Step 4 Select all by pressing Enter. The following is an example of the text display:


Processing package instance <CSCOh013> from </auto/mgc-sqa/PATCHES/SUN/2.0.1/CSCOh013.pkg>

Media Gateway Controller Security package compatible with Solaris 2.6 and Solaris 8
(sparc) 2.0(1)
Cisco System, Inc.
Using </opt/sun_install> as the package base directory.
## Processing package information.
## Processing system information.
   2 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <CSCOh013> [y,n,?] y

Step 5 Type y and press Enter to install the package. The following is an example of the text that is displayed:

Installing Media Gateway Controller Security package compatible with Solaris 2.5.1, 2.6, 
and 8 as <CSCOh013>
 
## Executing preinstall script.
Cisco MGC software or an adjunct was found.
## Installing part 1 of 1.
/opt/sun_install/CiscoSec.sh
/opt/sun_install/restore_lp.sh
[ verifying class <none> ]
## Executing postinstall script.
You must now run the install security script
 

Step 6 Type eject and press Enter to open the door to the CD-ROM drive. Remove the Solaris 8 Operating Environment Patches CD.

Step 7 Log in as root and enter the following commands to run the install security script.

# cd /opt/sun_install
# ./CiscoSec.sh install /tmp/security.log
 

Text similar t o the following is displayed:

Output will be logged in  /tmp/security.log
 
You are running as root - Good...
 
Operating System: SunOS 5.8
 
Backup directory does not exist - creating it now...
 Original files will be saved. Run this script
 with the parameter 'uninstall' to restore
 system to its original state
 
The following files will be removed from /etc/rc2.d:
File /etc/rc2.d/K60nfs.server not found
File /etc/rc2.d/K77dmi not found
Remove /etc/rc2.d/S47asppp
Remove /etc/rc2.d/S70uucp
Remove /etc/rc2.d/S71rpc
Remove /etc/rc2.d/S73cachefs.daemon
Remove /etc/rc2.d/S73nfs.client
Remove /etc/rc2.d/S74autofs
Remove /etc/rc2.d/S76nscd
Remove /etc/rc2.d/S80lp
Remove /etc/rc2.d/S80spc
Remove /etc/rc2.d/S85power
Remove /etc/rc2.d/S88sendmail
Remove /etc/rc2.d/S89bdconfig
File /etc/rc2.d/S91leoconfig not found
File /etc/rc2.d/S92rtvc-config not found
Remove /etc/rc2.d/S92volmgt
Remove /etc/rc2.d/S93cacheos.finish
Remove /etc/rc2.d/S99dtlogin
The following files will be removed from /etc/rc3.d:
Remove /etc/rc3.d/S15nfs.server
 
Now remove users from the password file
Remove lp from password file
Remove nuucp from password file
Remove uucp from password file
Remove smtp from password file
Remove listen from password file
 
Remove lp crontab entry
Remove uucp crontab entry
Create new inetd.conf file with only ftp,
 telnet and echo services enabled
 
Adjust kernel parameters in the /etc/system file
 
Force TCP/IP to use random initial seeds
 
Enable recording of failed login attempts
 
Create a new (minimal) inetsvc startup file
 
Restrict FTP Usage
 
Don't allow telnet users to log in as root
 
Disable keyboard abort sequence
 
Save existing /etc/shells file
Create /etc/shells file
 
Create /etc/init.d/nddconfig file
 

**************************************************
**************************************************
**                                              **
** NOTE!! The machine must be REBOOTED in order **
**        for these changes to take effect      **
**                                              **
**************************************************


Note If you are planning to install CSCOk9000, do not reboot after installing the CSCOh013 security package. You will be prompted to reboot after the installation of CSCOk9000.


Step 8 Reboot your machine with the -r option. Type the following command and press Enter:

# reboot -- -r


Note If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages below are displayed during system boot-up. They are normal Solaris DiskSuite start-up messages and do not indicate any problem with your system.

WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed



The installation of the Cisco security package (CSCOh013) is now complete. Return to the procedure for installing the Cisco MGC software.

Removing the Cisco Security Package (CSCOh013)

Do the following procedure if you need to remove the Cisco Security Package. Contact Cisco TAC if you need assistance (see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii).


Caution Removing the Cisco Security Package (CSCOh013) is the first step in removing the Cisco MGC software. Remove the Cisco Security Package only if you intend to perform tasks such as upgrading the Cisco MGC or upgrading to a new version of CSCOh013. Otherwise, the /etc/system files might be corrupted if removed out of order and security might be compromised if CSCOh013 is removed without removing the Cisco MGC.

If CSCOk9000 is installed, it must be removed first, before CSCOh013 is removed.


Note Make sure the Sun Solaris 8 operating system and the Cisco MGC software are still installed in your system before you remove the Cisco Security Package.



Step 1 Prior to uninstalling the CSCOh013 package, you must first uninstall the CiscoSec.sh script. Enter the following commands:

cd /opt/sun_install
 
./CiscoSec.sh uninstall /tmp<logfile>.log

Text similar to the following is displayed:

Output will be logged in  /tmp/<logfile>.log
 
You are running as root - Good...
 
Operating System: SunOS 5.8
 
Restoring system to original configuration...
File K60nfs.server not found
File K77dmi not found
Restore /etc/rc2.d/S47asppp
Restore /etc/rc2.d/S70uucp
Restore /etc/rc2.d/S71rpc
Restore /etc/rc2.d/S73cachefs.daemon
Restore /etc/rc2.d/S73nfs.client
Restore /etc/rc2.d/S74autofs
Restore /etc/rc2.d/S76nscd
Restore /etc/rc2.d/S80lp
Restore /etc/rc2.d/S80spc
Restore /etc/rc2.d/S85power
Restore /etc/rc2.d/S88sendmail
Restore /etc/rc2.d/S89bdconfig
File S91leoconfig not found
File S92rtvc-config not found
Restore /etc/rc2.d/S92volmgt
Restore /etc/rc2.d/S93cacheos.finish
Restore /etc/rc2.d/S99dtlogin
 
Restore /etc/rc3.d/S15nfs.server
 
Replace the following userids in the password file
lp nuucp uucp smtp listen
 
Restore lp to the password file
Restore nuucp to the password file
Restore uucp to the password file
Restore smtp to the password file
Restore listen to the password file
 
Restore lp crontab entry
Restore uucp crontab entry
Restore /etc/inetd.conf file
 
Restore /etc/system file
 
Restore /etc/default/inetinit file
 
Disable recording of failed login attempts
 
Restore /etc/init.d/inetsvc file
 
Restore /etc/ftpusers file
 
Restore /etc/default/login file
 
Restore /etc/default/kbd file
 
Restore /etc/shells file
 
/etc/init.d/nddconfig did not exist originally
 Delete existing file
/etc/rc2.d/S70nddconfig did not exist - delete existing file
 
Backup directory is being removed
 
**************************************************
**************************************************
**                                              **
** NOTE!! The machine must be REBOOTED in order **
**        for these changes to take effect      **
**                                              **
**************************************************
**************************************************
 
Done!

Step 2 Type the following command and press Enter:

pkgrm CSCOh013

Text similar to the following is displayed:

The following package is currently installed:
   CSCOh013        Media Gateway Controller Security package compatible with Solaris 
2.5.1, 2.6, and 8
                   (sparc) 2.0(11)
 
Do you want to remove this package? 

Step 3 Type y and press Enter to remove the package.

Text similar to the following is displayed:

## Removing installed package instance <CSCOh013>
 
This package contains scripts which will be executed with super-user
permission during the process of removing this package.
 
Do you want to continue with the removal of this package [y,n,?,q] y

Step 4 Type y and press Enter to continue the removal of the package.

Text similar to the following is displayed:

## Verifying package dependencies.
## Processing package information.
## Executing preremove script.
*** Removal of system security update package started...Fri Jul 30 17:21:56 EDT 2004 ***
## Removing pathnames in class <none>
/var/tmp <shared pathname not removed>
/opt/sun_install/restore_lp.sh
/opt/sun_install/CiscoSec.sh
/opt/sun_install <shared pathname not removed>
## Updating system information.
 
Removal of <CSCOh013> was successful.


This completes the removal of the Cisco Security Package.

Verification Test Suite (VTS) Package (CSCOh014) Overview

The Verification Test Suite (VTS) provides an optional script designed to test configured Sun Solaris 8 platforms used for Cisco MGC and BAMS products. These platforms include the following:

Sun Fire V120

Netra 120

Netra t1 100/105

Netra 20

Sun Fire V210

Netra 240

Netra 440

Netra t 1120/1125

Netra t 1400/1405

VTS test instructions support the following interface cards:

Sun GigaSwift Ethernet PCI card (order # X1150A)

Sun 10/100BT Ethernet PCI card (order # X1033)

Sun Quad Fast Ethernet PCI card (order # X1034A)

Perform all testing with a console log file enabled to capture everything entered at the console input and displayed on the console output. One way to accomplish this is through a terminal server connected to the console port of the Netra box. You can use the xterm program with the -l -lf <logfile> command line option to create the console log file.

You should archive the console log file along with the VTS log file created with other records for each target system during the test below.

Installing the VTS Package


Note The VTS package must be installed before running any tests.


To install the VTS package:


Step 1 Place the PGW Solaris Patches CD in the CD-ROM drive of the target system.

Step 2 Type the following commands to install the VTS package and press Enter:

# /usr/sbin/vold &


Note Entering this command may result in an error indicating the vold daemon is already running. If this happens, the error can be ignored.


# cd /cdrom/cdrom0
# pkgadd -d CSCOh014.pkg

The following text is displayed:

The following packages are available:
  1  CSCOh014     Media Gateway Controller Solaris 8 test
                  (sparc) 2.x(x)

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 1

Processing package instance <CSCOh014> from </auto/monument04/tbova/CSCOh014.pkg>

Media Gateway Controller Solaris 8 test
(sparc) 2.x(x)TJB
Cisco System, Inc.

## Processing package information.
## Processing system information.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.

## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <CSCOh014> [y,n,?] y

Step 3 Answer y and press Enter to continue with the installation.

Text similar to the following is displayed:

Installing Media Gateway Controller Solaris 8 test as <CSCOh014>

## Executing preinstall script.
Platform is SUNW,Ultra-80

NOTICE: Architecture checks passed

## Installing part 1 of 1.
/opt/sun_install/VTSadmin.file
/opt/sun_install/installVTS.sh
/opt/sun_install/uninstallVTS.sh
/opt/sun_install/vts_script
[ verifying class <none> ]
## Executing postinstall script.

Installation of <CSCOh014> was successful.
#

Step 4 Type the following command to eject the CD and press Enter:

# cd / 
# eject

Step 5 Change directories at the end of the CSCOh014 installation, when text similar to the following is displayed:

You must now change directories to /opt/sun_install and run the ./installVTS.sh as root.

Step 6 Change directories and install the SunVTS package. Press Enter when prompted.

# cd /opt/sun_install
# ./installVTS.sh

The following text is displayed:

Changing directories to /cdrom/solaris8_1001_suppcd/SunVTS_4.5/Product
Current directory /cdrom/solaris8_1001_suppcd/SunVTS_4.5/Product

Processing package instance <SUNWvts> from 
</cdrom/solaris8_1001_suppcd/SunVTS_4.5/Product>

SunVTS
(sparc) 4.5,REV=08.01.08.15,OE=5.8
Copyright 2001 Sun Microsystems, Inc. All rights reserved.

SunVTS supports Kerberos V5 network authentication protocol, included in SEAM (Sun 
Enterprise Authentication Mechanism). This protocol is designed to provide strong 
authentication for client/server applications by using secret-key cryptography.
 _In order to use this feature, a SEAM-based Security enabled network must be present. 

Step 7 Enter n when asked if you want the Kerberos V5-based security installed.

Do you want to enable the Kerberos V5 based security? n

The following text is displayed:

## Executing checkinstall script.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying package dependencies.
## Verifying disk space requirements.

Installing SunVTS as <SUNWvts>

## Installing part 1 of 1.
94394 blocks
/opt/SUNWvts/.etc_inetdconf <symbolic link>
Executing i.inetdconf class script...
Completed editing /etc/inetd.conf
Sending signal to inetd to read the modified conf file...
[ verifying class <inetdconf> ]
[ verifying class <gsscfg> ]
## Executing postinstall script.

Installation of <SUNWvts> was successful.

Processing package instance <SUNWvtsx> from 
</cdrom/solaris8_1001_suppcd/SunVTS_4.5/Product>

64-bit SunVTS
(sparc) 4.5,REV=08.01.08.15,OE=5.8
Copyright 2001 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
   2 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.

Installing 64-bit SunVTS as <SUNWvtsx>

## Installing part 1 of 1.
20946 blocks

Installation of <SUNWvtsx> was successful.

Processing package instance <SUNWvtsmn> from 
</cdrom/solaris8_1001_suppcd/SunVTS_4.5/Product>

SunVTS Man Pages
(sparc) 4.5,REV=08.01.08.15,OE=5.8
Copyright 2001 Sun Microsystems, Inc. All rights reserved.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
   1 package pathname is already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.

Installing SunVTS Man Pages as <SUNWvtsmn>

## Installing part 1 of 1.
53 blocks

Installation of <SUNWvtsmn> was successful.
#  


This completes the VTS installation. If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.

Using the SunVTS Test Package


Note Version 4.5 of the SunVTS should be used. This version is available with the 10/01 release of Solaris 8.


Use the SunVTS program to test the following:

CPUs

Memory

Ethernet cards


Note To fully test the Ethernet ports, all Ethernet ports must be configured with valid IP addresses and connected to an Ethernet network with at least one other machine on the network.


Hard disks

CD-ROM drive


Note To test the CD-ROM drive, a CD-ROM must be in the drive.


LOM hardware

Normal Unit Test

The normal unit test must be successfully run on each target system before it is shipped to the customer. A normal unit test checks 20 percent of each disk surface. To run a normal unit test:


Caution Do not run this test while the application is running because it could adversely affect the application performance.


Step 1 Change directories to the following directory:

# cd /var/tmp

Step 2 Enter the following command to start the test:

# ./vts_script

Text similar to the following is displayed:

Platform is SUNW,Ultra-80
OS version is 5.8
OS is 64-bits 
checking for VTS packages
system      SUNWvts        SunVTS
system      SUNWvtsx       64-bit SunVTS
VTS version: 4.5,REV=08.01.08.15,OE=5.8

VTS probe output: 
Processor(s)
   cpu-unit0(fputest)
      Type:SPARC V9 based FPU
      clock-frequency:440 MHz.
   cpu-unit0(cputest)
      Type:SPARC V9 CPU
      clock-frequency: 440 MHz.
   cpu-unit1(fputest)
      Type:SPARC V9 based FPU
      clock-frequency:440 MHz.
   cpu-unit1(cputest)
      Type:SPARC V9 CPU
      clock-frequency: 440 MHz.
   cpu-unit2(fputest)
      Type:SPARC V9 based FPU
      clock-frequency:440 MHz.
   cpu-unit2(cputest)
      Type:SPARC V9 CPU
      clock-frequency: 440 MHz.
   cpu-unit3(fputest)
      Type:SPARC V9 based FPU
      clock-frequency:440 MHz.
   cpu-unit3(cputest)
      Type:SPARC V9 CPU
      clock-frequency: 440 MHz.
   l1dcache(l1dcachetest)
      Level 1 Cache Test
   l2dcache(l2dcachetest)
      Level 2 Cache Test
   mp(mptest)
      Number of processors:4
   mp(mpconstest)
      Number of processors:4
   system(systest)
      System Configuration=  Sun Microsystems  sun4u
      Memory size= 4096 Megabytes
      System clock-frequency= 110 MHz
Memory
   kmem(vmemtest)
      Total Swap: 5404MB
   mem(pmemtest)
      System memory size:4096MB
Network
   hme0(nettest)
      Host_Name: va-panthers
      Host Address: 10.82.80.64
      Host ID: 80c4d518
      Domain Name: 
   hme1(nettest)
      Host_Name: va-panthers-a
      Host Address: 10.82.81.64
      Host ID: 80c4d518
      Domain Name: 
Comm.Ports
   se0(sptest)
      port a = se0 = /dev/term/a = /devices/...se...:a 
      port b = se1 = /dev/term/b = /devices/...se...:b
Monitor&Alarms
   lomlite(lomlitetest)
      Device information:  NONE
OtherDevices
   ecpp0(ecpptest)
      IEEE 1284 parallel port (ECP/nibble/centronics modes)
   ssc100@16(dpmtest)
      DPM controller at ssc100@16
SCSI-Devices(glm0)
   c0t0d0(disktest)
      Capacity: 16.86GB
      Controller: glm0
      Vendor: SEAGATE 
      SUN Id: ST318203LSUN18G 
      Firmware Rev: 034A
      Serial Number: 9946717334
   c0t1d0(disktest)
      Capacity: 16.86GB
      Controller: glm0
      Vendor: SEAGATE 
      SUN Id: ST318203LSUN18G 
      Firmware Rev: 034A
      Serial Number: 9946723866
   c0t6d0(cdtest)
      Controller: glm0

Number of hard disks:        2
 disks:
c0t0d0
c0t1d0

Number of network interfaces:        2
Network interfaces:
hme0
hme1

normal test 

Platform: Netra T140x (LW3)

Floating Point Unit Test ...
Central Processor Unit Test cpu-unit0 ...
Central Processor Unit Test cpu-unit2 ...
Central Processor Unit Test cpu-unit1 ...
Level 1 Data Cache Test ...
Central Processor Unit Test cpu-unit3 ...
Level 2 Data Cache Test ...
System Test ...
Level 1 Data Cache Test done
System Test done
Floating Point Unit Test done
Level 2 Data Cache Test done
Central Processor Unit Test cpu-unit2 done
Central Processor Unit Test cpu-unit0 done
Central Processor Unit Test cpu-unit3 done
Central Processor Unit Test cpu-unit1 done

Virtual Memory Test 64MB ...

Physical Memory Test ...

Virtual Memory Test done

Physical Memory Test done

Network Test hme0 ...

CD-ROM Test c0t6d0 ...

Network Test hme1 ...

Lights Out Management Test lomlite ...

Hard Disk Test c0t0d0 20% ...

Hard Disk Test c0t1d0 20% ...

Network Test hme1 done

Network Test hme0 done
Feb 27 10:03:29 va-panthers lom: LOMlite Alarm 1 OFF Feb 27 10:03:34 va-panthers lom: 
LOMlite Alarm 1 ON Feb 27 10:03:39 va-panthers lom: LOMlite Alarm 2 OFF Feb 27 10:03:44 
va-panthers lom: LOMlite Alarm 2 ON Feb 27 10:03:49 va-panthers lom: LOMlite Alarm 3 OFF 
Feb 27 10:03:53 va-panthers lom: LOMlite Alarm 3 ON 
CD-ROM Test c0t6d0 done
Feb 27 10:04:09 va-panthers lom: LOMlite Fault LED ON Feb 27 10:04:13 va-panthers lom: 
LOMlite Fault LED OFF 
Lights Out Management Test lomlite done

Hard Disk Test c0t1d0 done

Hard Disk Test c0t0d0 done

**************************************
************* RESULTS ****************
**************************************

normal test 

Number of hard disks:        2
 disks:
c0t0d0
c0t1d0

Number of network interfaces:        2
Network interfaces:
hme0
hme1

PPPPPP   AA   SSSSSS SSSSSS
PP  PP  A  A  SS     SS    
PPPPPP AAAAAA SSSSSS SSSSSS
PP     AA  AA     SS     SS
PP     AA  AA SSSSSS SSSSSS
# 


Note Refer to Table 3-2 for the approximate amount of time the test will take on the different platforms supported.


Step 3 Once the test completes, examine the console output and the file /var/tmp/vts_script.log. Verify that the test passed and the proper number of hard disks and Ethernet interfaces were detected.

Step 4 Reboot your host from root by entering the following command:

# reboot -- -r


Running a Test in Brief Mode

When run in brief mode, the vts_script tests 1 percent of each disk surface. To run the test in brief mode:


Step 1 Change directories to the /var/tmp directory. Enter the following command:

# cd /var/tmp

Step 2 Enter the following command to start the test:

# /opt/sun_install/vts_script brief

Step 3 Once the test completes, examine the console output and the file /var/tmp/vts_script.log. Verify that the test passed and the proper number of hard disks and Ethernet interfaces were detected.

Step 4 Reboot your host from root by entering the following command:

# reboot -- -r


Running a Test in Full Mode

When run in full mode, the vts_script tests 100 percent of each disk surface. To run the test in full mode:


Step 1 Change directories to the /var/tmp directory. Enter the following command:

# cd /var/tmp

Step 2 Enter the following command to start the test:

# /opt/sun_install/vts_script full

Step 3 Once the test completes, examine the console output and the file /var/tmp/vts_script.log. Verify that the test passed and the proper number of hard disks and Ethernet interfaces were detected.

Step 4 Reboot your host from root by entering the following command:

# reboot -- -r


vts_script Execution Times

Table 3-2 lists estimated execution times for the VTS script on a sampling of Cisco MGC software host platforms.


Note Actual VTS script execution time on your host platforms differs based on the configuration of your hardware. The size of the disks used in your host platforms has the largest single impact on execution time.


Table 3-2 Sample Estimates of VTS Script Execution Times

VTS Version
Platform Type, Number of CPUs, CPU speed, Amount of RAM, Number of Disks,
Size of Disks
Brief Mode
Execution Time
(hours:minutes: seconds)
Normal Mode
Execution Time
(hours:minutes: seconds)
Full Mode
Execution Time
(hours:minutes: seconds)

4.3

Netra t1 10x, 1, 360MHz, 64M, 2, 9GB

0:5:02

0:8:19

0:36:26

4.3

Netra t 112x, 1, 296MHz, 2GB, 1, 9GB

0:5:42

0:10:23

0:40:31

4.3

Netra t 112x, 2, 440MHz, 2GB, 2, 18GB

0:3.55

0:11:05

0:51:44

4.3

Netra t 140x, 4, 440MHz, 4GB, 2, 18GB

0:4:21

0:11:16

0:52:06

4.3

Netra t 140x, 4, 440MHz, 4GB, 4, 18GB

0:5:23

0:15:03

0:65:40

5.1

Netra 120, 1 440MHz, 2GB, 2, 36GB

0:06:09

1:16:35

estimate unavailable

5.1

Netra 20, 4, 900MHz, 4GB, 2, 73GB

0:09:36

2:31:00

estimate unavailable

5.1

Sun Fire V210, 1, 1340MHz, 2GB, 2, 73GB

0:08:56

2:30:57

estimate unavailable

5.1

Netra 240, 2, 1280MHz, 4GB, 2, 73GB

0:11:30

2:31:00

estimate unavailable

5.1

Netra 440, 4, 1281MHz, 8GB, 4, 73GB

0:09:31

2:22:00

estimate unavailable

 

Netra 240, 2, 1280MHz, 4GB, 2, 146GB

     
         

Removing SunVTS

The following procedure will remove SunVTS software and patch from the target system. The SunVTS software occupies about 60 Mb of disk space under the /opt/SUNWvts directory. The SunVTS software does not have to be removed; however, the if it is left on the target system, it will consume disk space that could otherwise be used for application data.


Step 1 Enter the following commands to remove the SUNVTS package:

# cd /opt/sun_install 
# ./uninstallVTS.sh


This completes the procedures for installing and running the VTS package. If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.

Removing the VTS Package (CSCOh014)

Use the following procedure to remove the VTS test software from the target system after all tests are complete, all the log files are archived, and the SunVTS software is uninstalled.


Note Do not remove the CSCOh014 package without first removing the SunVTS package.


Type the following command and press Enter to remove the VTS package:

# pkgrm CSCOh014