Installing and Configuring the SC Software

Before beginning the upgrade, verify that you have the Cisco Media Gateway Controller Software Release 7 CD-ROM. (For Software Release 7.3(x), this is called the Cisco Telephony Controller Software Release 7 CD-ROM.)

Use the instructions in this section to install new software. If you have a simplex configuration, install the software on your server. If you have a high-availability configuration, install the software on the standby first.

Note Procedures for installing Software Release 7.3(x) differ from Software Release 7.4(x). Follow the instructions for the version you are installing.

This chapter contains the following sections:

Note Always consult the latest Release Notes for Cisco Media Gateway Controller Software Release 7 (available from your Cisco representative) to make sure that you have the most current release of software and that no additional patches are required. If patches are required, consult the release notes for patch installation procedures.

Tips Many of the procedures in this chapter require using an editor such as vi to make changes to files. If you experience screen viewing problems, try the following:

If you are not sure which shell you are using, enter the following commands:

TERM=xterm
export TERM
stty rows 24

If you are using a Bourne shell, enter the TERM=vt100; export TERM command.
If you are using a C shell, enter the setenv TERM vt100 command.

Installing SC Software Release 7.3(x)

To install Software Release 7.3(x), follow these steps:

Note You must be logged in as root. Do not log in as another user and enter su to become root. Logging in as root might require use of a console connected to the SC host.

Step 1 Insert the Cisco Telephony Controller Release 7.3(x) CD-ROM into the CD-ROM drive.

Step 2 Change to the directory containing the CD-ROM by entering the following:

cd /cdrom/cdrom0

Step 3 Start the automated software install script by entering the following command:

./install.sh

Step 4 Install the software using the onscreen instructions. Cisco recommends you accept the default directories for software installation.

Note If you want to install the TCM on a separate server than your host server, answer N to the "install Telephony Controller Manager (TCM) package" prompt. After installing the rest of the software, proceed to the "Installing the TCM or CMM on a Separate Host" section.

# ./install.sh
 
Base directory for Telephony Controller (default /opt/TransPath) [?,q] 
 
Install Telephony Configuration Manager (TCM) package? [n] [y,n,?,q] y
 
Base directory for TCM (default /opt/VSCprov) [?,q] 
 
Use supplied admin file for unattended install? [n] [y,n,?,q] y

TimeSaver If you do not accept the unattended installation, the system prompts you before installing each package; choosing unattended installation saves time.

Step 5 The script installs the utilities, then asks you to reboot the system. Enter init 6 to reboot the system.

Step 6 Log in as root and change to the /cdrom/cdrom0 directory.

Step 7 Restart the install script by entering install.sh. The script installs the software and shows a status message when complete.

This completes installing the SC software. If you chose to install the TCM on a separate server, proceed to the "Installing the TCM or CMM on a Separate Host" section. If you have ITK or PTI signaling cards, proceed to the "Installing Drivers for ITK/PTI Signaling Cards" section. Otherwise, proceed to the "Configuring SNMP Support Resources" section.

Note When installing the software, only the active configuration files (located in /opt/TransPath/etc) are migrated. If you have older configurations you need to migrate, see the "Migrating Additional Configurations" section.

Tips If you did not review your MML names in the components.dat and properties.dat files before beginning the upgrade, and your MML names did not conform to the new standards, you received a migration error. To correct the situation:

Step 1 Uninstall the failed package CSCOgc001 by entering the pkgrm CSCOgc001.pkg command. Answer Y to the prompts.

Step 2 Refer to the "Reviewing Your Components.dat and Properties.dat Files for Potential Problems" section for instructions on editing your MML names.

Step 3 Reinstall the package by changing to the /cdrom/cdrom0/APPLICATIONS directory and entering the pkgadd -d CSCOgc001.pkg command.

Installing SC Software Release 7.4(x)

To install Software Release 7.4(x), follow these steps:

Note You must be logged in as root. Do not log in as another user and enter su to become root. Logging in as root might require use of a console connected to the SC host.

Step 1 Enter the following command:

cd /etc

Step 2 Open the password (passwd) file with your editor.

Step 3 Check that /opt/TransPath does not appear in the path of any user; if it does, change the path to /opt/CiscoMGC. If you have a transpath user, delete it.

Step 4 Save any changes and close the file.

Step 5 Open the group file with your editor.

Step 6 Check that the transpath group does not exist. If it does, delete it.

Step 7 Save any changes and close the file.

Step 8 Insert the Cisco Media Gateway Controller Release 7.4(x) CD-ROM into the CD-ROM drive.

Step 9 Change to the directory containing the CD-ROM by entering the following:

cd /cdrom/cdrom0

Step 10 Start the automated software install script by entering the following command:

./install.sh

Install the software using the onscreen instructions. Cisco recommends you accept the default directories for software installation. Enter responses to the prompts as shown in the following example:

va-lions:52> ./install.sh
 
Use supplied admin file for unattended install? [n] [y,n,?,q] y

TimeSaver If you do not accept the unattended installation, the system prompts you before installing each package; choosing unattended installation saves time.

Install Cisco Media Gateway Controller Manager (CMM) package? [n] [y,n,?,q] y
 
Base directory for CMM (default /opt/CMM) [?,q] 
 
The CSCOgu000 utilities package must be installed prior to other components
but has not been detected on your system.
 
Would you like to install it now? [y] [y,n,?,q] y
 
Base directory for CiscoMGC (default /opt/CiscoMGC) [?,q] 
Enter CiscoMGC user name [mgcusr] 
Enter CiscoMGC group name [mgcgrp]

Note You can specify a user ID or 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. However, no validation is performed on the IDs you enter. If you enter an invalid ID, the utilities package will fail to add any accounts.

Old Base Directory /opt/TransPath recognized, would you like to migrate to
/opt/CiscoMGC?  [y] [y,n,?,q] y
find: cannot open /opt/CiscoMGC/var/trace: No such file or directory

Note Make sure that you followed Step 1 through Step 7, and you do not still have the transpath user in the /etc/passwd file or the transpath group in the /etc/groups file.

Modifying /etc/init.d/inetinit
Inserting shmsys:shminfo_shmmax in /etc/system
Inserting shmsys:shminfo_shmmin in /etc/system
Inserting shmsys:shminfo_shmmni in /etc/system
Inserting shmsys:shminfo_shmseg in /etc/system
Inserting semsys:seminfo_semmsl in /etc/system
Inserting semsys:seminfo_semmns in /etc/system
Inserting sq_max_size in /etc/system
 
Installation of <CSCOgu000> was successful.
 
*** IMPORTANT NOTICE ***
        This machine must now be rebooted in order to ensure
        sane operation.  Execute
               shutdown -y -i6 -g0
        and wait for the "Console Login:" prompt.
CSCOgu000 installation requires system to be rebooted - please restart installas
Installation completed Thu Mar  9 21:33:14 EST 2000 
Installation log can be found in /tmp/install.log

Step 11 The script installs the utilities, then asks you to reboot the system. Enter init 6 to reboot the system.

va-lions:53> init 6

Step 12 Log in as root and change to the /cdrom/cdrom0 directory.

Step 13 Restart the install script by entering install.sh. Enter responses at the prompt as shown in the following example.

Note If you want to install the CMM on a separate server than your host server, answer N to the "install Cisco Media Gateway Controller Manager (CMM) package" prompt. After installing the rest of the software, proceed to the "Installing the TCM or CMM on a Separate Host" section.

va-lions:23> ./install.sh
 
Use supplied admin file for unattended install? [n] [y,n,?,q] y
 
Install Cisco Media Gateway Controller Manager (CMM) package? [n] [y,n,?,q] y
 
(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.
13615 Dulles Technology Drive
Herndon, VA 20171

The script installs the software and shows a status message when complete.

This completes installing the SC software. If you chose to install the CMM on a separate server, proceed to the "Installing the TCM or CMM on a Separate Host" section. If you have ITK or PTI signaling cards, proceed to the "Installing Drivers for ITK/PTI Signaling Cards" section. Otherwise, proceed to the "Configuring SNMP Support Resources" section.

Step 1 Uninstall the failed package CSCOgc001 by entering the pkgrm CSCOgc001.pkg command. Answer Y to the prompts.

Step 2 Refer to the "Reviewing Your Components.dat and Properties.dat Files for Potential Problems" section for instructions on editing your MML names.

Step 3 Reinstall the package by changing to the /cdrom/cdrom0/APPLICATIONS directory and entering the pkgadd -d CSCOgc001.pkg command.

Installing the TCM or CMM on a Separate Host

You can install the TCM or CMM on a separate server than the SC software. To install only the TCM or CMM, perform the following steps:

Step 1 Insert the Cisco Media Gateway Controller Release 7 CD-ROM into the CD-ROM drive of the separate server.

Step 2 Change to the directory containing the CD-ROM by entering the following:

cd /cdrom/cdrom0

Step 3 Enter the following command:

./install-tcm.sh

Answer yes to the onscreen prompts.

Note For Cisco SC Software Release 7.4(x), the configuration tool is called the CMM. Enter ./install-cmm-tool.sh in Step 3.

This completes installing the TCM or CMM on a separate host. If you have ITK or PTI signaling cards, proceed to the "Installing Drivers for ITK/PTI Signaling Cards" section. Otherwise, proceed to the "Configuring SNMP Support Resources" section.

Installing Drivers for ITK/PTI Signaling Cards

If you are using ITK T1/E1 or PTI V.35 cards to terminate SS7 signaling, you need to install drivers for these cards as part of the software installation.

To install the drivers:

Note You must be logged in as root. Do not log in as another user and enter su to become root. Logging in as root might require use of a console connected to the SC host.

Step 1 Insert the Cisco Media Gateway Controller Release 7 CD-ROM into the CD-ROM drive.

Step 2 Change to the directory containing the CD-ROM by entering the following:

cd /cdrom/cdrom0

Step 3 Change to the drivers directory by entering the following:

cd DRIVERS

The drivers directory contains the following driver packages:

CSCOgd001: Drivers for ITK T1/E1 cards
CSCOgd002: Drivers for PTI V.35 cards
CSCOgd003: Drivers for PTK T1/E1 cards (Reserved for future use--Do not use.)

Step 4 Enter the pkgadd -d packagename command to add the appropriate driver for your card. For example:

# pkgadd -d CSCOgd001.pkg
 
The following packages are available:
  1  CSCOgd001     Cisco Media Gateway Controller Software ITK PCI E1/T1 Driver
                   (sparc) 7.4(7)G
 
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:

Step 5 Press Enter to install the package. The script installs the drivers and reboots the SC host.

Configuring SNMP Support Resources

The Cisco MGC software includes a Simple Network Management Protocol (SNMP) agent subsystem that provides an alarm management interface on the SC host. It uses SNMP to report events, or traps (such as alarms), to your SNMP Manager and to provide access to the Cisco MGC Management Information Base (MIB).

The SNMP agent subsystem reports the following event categories to your SNMP Manager:

1. Communications

2. Quality of Service

3. Processing

4. Equipment

5. Environment

In a continuous-service configuration, the SNMP agent subsystem runs on both the active and standby machines.

To configure the SNMP resources, complete the following steps:

Step 1 Log in to the SC host and change to the /etc directory.

Step 2 Verify that the services.dat file lists the following default SNMP ports:

snmp      161/udp
snmp-trap 162/udp

Step 3 Using FTP, transfer the following MIBs (located in /opt/TransPath/snmp) from the Cisco SC host to the machine on which the SNMP manager runs:

CISCO-SMI.my
v3-tgt.my
tp.my
provisioning.my
measurement.my

Note For Software Release 7.4(x), the MIBs are located in /opt/CiscoMGC/snmp.

Step 4 Load the MIBs into the SNMP manager (for example, you can use the xnmnloadmib -load command from HP OpenView).

Note See your SNMP manager documentation for more information. Cisco does not recommend a specific SNMP manager; however, this chapter gives examples using the Hewlett-Packard (HP) OpenView Network Node Manager.

HP OpenView Example: 
If you are using HP OpenView Network Node Manager as your SNMP manager, follow these procedures to load your MIB:
(a) Select Options from the File Menu and choose Load/Unload MIBs:SNMP.
(b) From the Load/Unload MIBs: SNMP window (on the lower left of your screen).
(c) Click the Load... button.
(c) From the "Load/Unload MIBs:SNMP /Load MIB from File" window, select the MIB to load (for example, tp.my).
(d) Click OK.

Tips For more detailed information about configuring HP OpenView, see Appendix B, "HP OpenView Sample SNMP Configuration," in Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide.

Step 5 Connect the SNMP events to an event category to display the event. As Cisco SC events are connected, you can alter the format of the event messages for easier viewing.

Note On many SNMP managers, event categories can be added so that customer-specific events can be mapped to corresponding categories.

HP OpenView Event Configuration Example: 
If you are using HP OpenView Network Node Manager, follow these procedures to configure an event:
(a) Select Options from the File Menu and choose Event Configuration.
(b) From the Event Configuration window, in the Enterprise Identification list, select transpath.
(c) In the Event Identification list, double click on each of the event types, one at a time.
(d) If desired, change the event information display. To change the format of an event, from the Event Configurator / Modify Event window, enter a format in the Event Log Message Box to change the format and labels for received events of this type. 
 
The following example shows how an event can be reformatted using the HP OpenView Network Node Manager.
ID# $13   Name $12   Set $10   MMLname $4   CatDesc    $11  \nCompDesc $3   Severity $8   CompID $6   CompType $5   CatID $14\nAlarmNotify $9   AlarmTime$1   ParentID $2   AlarmReported $7\n$o

Step 6 To verify that SNMP is working, log in to the SC host as root and enter the following command:

traprcv

The traprcv window shows traps being sent from the SNMP daemon. Following is an example of a traprcv session:

Traprcv Session 
Waiting for traps.
     Received SNMPv2c Trap:
     Community: public
     From: 127.0.0.1
     sysUpTime.0 = 304785432
     snmpTrapOID.0 = processingError
     tpAlarmTime.0 = 0xef68e93c00159dc8
     tpComponentParentId.0 = 131079
     tpComponentDesc.0 = Measurement Manager
     tpComponentName.0 = MM-01
     tpComponentType.0 = 3
     tpComponentId.0 = 196611
     tpAlarmReported.0 = yes(2)
     tpAlarmSeverity.0 = major(3)
     tpAlarmNotify.0 = no(1)
     tpAlarmSet.0 = clear(1)
     tpAlarmCatDesc.0 = Required process MOOS
     tpAlarmCatName.0 = MAJOR M-OOS
     tpAlarmCatId.0 = 64
     tpAlarmId.0 = 0
      
     Received SNMPv2c Trap:
     Community: public
     From: 127.0.0.1
     sysUpTime.0 = 304786908
     snmpTrapOID.0 = processingError
     tpAlarmTime.0 = 0xef68e93c00159dc8
     tpComponentParentId.0 = 131079
     tpComponentDesc.0 = Measurement Manager
     tpComponentName.0 = MM-01
     tpComponentType.0 = 3
     tpComponentId.0 = 196611
     tpAlarmReported.0 = yes(2)
     tpAlarmSeverity.0 = major(3)
     tpAlarmNotify.0 = no(1)
     tpAlarmSet.0 = clear(1)
     tpAlarmCatDesc.0 = Required Process Failure
     tpAlarmCatName.0 = SOFTW REQ
     tpAlarmCatId.0 = 5
     tpAlarmId.0 = 0
     _

Step 7 Verify that your SNMP Manager shows the same traps as the traprcv session. If you do not see the events in your SNMP Manager, you might have a port mismatch or an incorrect IP address in your configuration.

Note Traprcv can receive trap events from multiple SC hosts. To send trap events from a Cisco SC host to the machine where traprcv is running, set the SNMP target IP address (snmpTargetAddrEntry in the snmpd.cnf file) in the CMM and load the new configuration.

Sample Configured snmpd.cf File

TSK# Entry type:sysDescr 
# Entry format:octetString
sysDescr  "SNMPv3 agent from Cisco Systems, Inc."
 
 
# Entry type:sysObjectID 
# Entry format:OID
sysObjectID  enterprises.10.999
 
 
# Entry type:sysLocation 
# Entry format:octetString
sysLocation  "Herndon, Virginia"
 
 
# Entry type:sysContact 
# Entry format:octetString
sysContact  "Cisco Systems, Inc.  +1 703 484 3000"
 
 
# Entry type:sysName 
# Entry format:octetString
sysName  "TISU - VSC"
 
 
# Entry type:snmpEnableAuthenTraps 
# Entry format:integer
snmpEnableAuthenTraps  1
 
 
# Entry type:MAX_THREADS 
# Entry format:integer
MAX_THREADS  20
 
# Entry type:MAX_PDU_TIME 
# Entry format:integer
MAX_PDU_TIME  2500
 
 
# Entry type:MAX_OUTPUT_WAITING 
# Entry format:integer
MAX_OUTPUT_WAITING  65536
 
 
# Entry type:MAX_SUBAGENTS 
# Entry format:integer
MAX_SUBAGENTS  10
 
 
# Entry type:subagent 
# Entry format:octetString
 
#Entry type:srCommunityEntry
#Format: srCommunityAuthSnmpID  (octetString)
#         srCommunityName  (text)
#         srCommunityGroupName  (text)
#         srCommunityContextSnmpID  (octetString)
#         srCommunityContextName  (text)
#         srCommunityTransportLabel  (text)
#         srCommunityMemoryType  (nonVolatile, permanent, readOnly)
communityEntry  localSnmpID public Anyone localSnmpID default - nonVolatile
 
 
# Entry type:snmpBoots 
# Entry format:integer
snmpBoots  76
 
 
#Entry type:userNameEntry
#Format: userAuthSnmpID  (octetString)
#         userName  (text)
#         userGroupName  (text)
#         userTransportLabel  (text)
#         userMemoryType  (nonVolatile, permanent, readOnly)
 
 
# Entry type:snmpEngineBoots 
# Entry format:integer
snmpEngineBoots  76
 
 
#Entry type:usmUserEntry
#Format: usmUserEngineID  (octetString)
#         usmUserName  (text)
#         usmUserAuthProtocol  (OID)
#         usmUserPrivProtocol  (OID)
#         usmUserStorageType  (nonVolatile, permanent, readOnly)
#         usmTargetTag  (text)
 
 
#Entry type:vacmAccessEntry
#Format: vacmGroupName  (text)
#         vacmAccessContextPrefix  (text)
#         vacmAccessSecurityModel  (snmpv1, snmpv2c, snmpv2s, usm)
#         vacmAccessSecurityLevel  (noAuthNoPriv, authNoPriv, authPriv)
#         vacmAccessContextMatch  (exact, prefix)
#         vacmAccessReadViewName  (text)
#         vacmAccessWriteViewName  (text)
#         vacmAccessNotifyViewName  (text)
#         vacmAccessStorageType  (nonVolatile, permanent, readOnly)
vacmAccessEntry  Guest - usm noAuthNoPriv exact DemoRead DemoWrite DemoRead \
    nonVolatile
vacmAccessEntry  Guest - snmpv2s noAuthNoPriv exact DemoRead DemoWrite \
    DemoRead nonVolatile
vacmAccessEntry  Anyone - snmpv1 noAuthNoPriv exact All All All nonVolatile
vacmAccessEntry  Anyone - snmpv2c noAuthNoPriv exact All All All nonVolatile
vacmAccessEntry  DayOperator - usm noAuthNoPriv exact All - All nonVolatile
vacmAccessEntry  DayOperator - snmpv2s noAuthNoPriv exact All - All \
    nonVolatile
vacmAccessEntry  DayOperator UPS usm noAuthNoPriv prefix All - All nonVolatile
vacmAccessEntry  DayOperator UPS snmpv2s noAuthNoPriv prefix All - All \
    nonVolatile
vacmAccessEntry  SystemAdmin - usm noAuthNoPriv exact All - All nonVolatile
vacmAccessEntry  SystemAdmin - snmpv2s noAuthNoPriv exact All - All \
    nonVolatile
vacmAccessEntry  SystemAdmin UPS usm noAuthNoPriv prefix All - All nonVolatile
vacmAccessEntry  SystemAdmin UPS snmpv2s noAuthNoPriv prefix All - All \
    nonVolatile
vacmAccessEntry  NightOperator - usm noAuthNoPriv exact All - All nonVolatile
vacmAccessEntry  NightOperator - snmpv2s noAuthNoPriv exact All - All \
    nonVolatile
vacmAccessEntry  NightOperator UPS usm noAuthNoPriv prefix All - All \
    nonVolatile
vacmAccessEntry  NightOperator UPS snmpv2s noAuthNoPriv prefix All - All \
    nonVolatile
 
 
#Entry type:vacmSecurityToGroupEntry
#Format: vacmSecurityModel  (snmpv1, snmpv2c, snmpv2s, usm)
#         vacmSecurityName  (text)
#         vacmGroupName  (text)
#         vacmSecurityToGroupStorageType  (nonVolatile, permanent, readOnly)
vacmSecurityToGroupEntry  snmpv1 public Anyone nonVolatile
vacmSecurityToGroupEntry  snmpv2c public Anyone nonVolatile
vacmSecurityToGroupEntry  usm Guest Guest nonVolatile
vacmSecurityToGroupEntry  usm AnneXPert HelpDesk nonVolatile
vacmSecurityToGroupEntry  usm EarlERiser DayOperator nonVolatile
vacmSecurityToGroupEntry  usm WyleUSleep NightOperator nonVolatile
vacmSecurityToGroupEntry  usm TonyaTTyper Staff nonVolatile
vacmSecurityToGroupEntry  usm CharlieDChief SystemAdmin nonVolatile
vacmSecurityToGroupEntry  usm BobBBookkeeper Staff nonVolatile
vacmSecurityToGroupEntry  usm ShawnNShipping Staff nonVolatile
 
 
#Entry type:vacmViewTreeFamilyEntry
#Format: vacmViewTreeFamilyViewName  (text)
#         vacmViewTreeFamilySubtree  (OID)
#         vacmViewTreeFamilyMask  (octetString)
#         vacmViewTreeFamilyType  (included, excluded)
#         vacmViewTreeFamilyStorageType  (nonVolatile, permanent, readOnly)
vacmViewTreeFamilyEntry  All iso - included nonVolatile
vacmViewTreeFamilyEntry  All 0.0 - included nonVolatile
vacmViewTreeFamilyEntry  Network mib_2 - included nonVolatile
vacmViewTreeFamilyEntry  Network snmpTrap - included nonVolatile
vacmViewTreeFamilyEntry  Network snmpTraps - included nonVolatile
vacmViewTreeFamilyEntry  DemoRead system - included nonVolatile
vacmViewTreeFamilyEntry  DemoRead srExamples - included nonVolatile
vacmViewTreeFamilyEntry  DemoRead snmpTrap - included nonVolatile
vacmViewTreeFamilyEntry  DemoRead snmpTraps - included nonVolatile
vacmViewTreeFamilyEntry  DemoRead ifEntry.0.2 ff:bf included nonVolatile
vacmViewTreeFamilyEntry  HtmlPage htmlpage - included nonVolatile
vacmViewTreeFamilyEntry  Unsecure system - included nonVolatile
vacmViewTreeFamilyEntry  Unsecure snmpTrap - included nonVolatile
vacmViewTreeFamilyEntry  Unsecure snmpTraps - excluded nonVolatile
vacmViewTreeFamilyEntry  DemoWrite srBasics - included nonVolatile
vacmViewTreeFamilyEntry  Confidential enterprises - included nonVolatile
vacmViewTreeFamilyEntry  Confidential system - included nonVolatile
vacmViewTreeFamilyEntry  Confidential snmpTrap - included nonVolatile
vacmViewTreeFamilyEntry  Confidential snmpTraps - included nonVolatile
 
 
#Entry type:snmpNotifyEntry
#Format: snmpNotifyName  (text)
#         snmpNotifyTag  (text)
#         snmpNotifyType  (trap(1), inform(2))
#         snmpNotifyStorageType  (nonVolatile, permanent, readOnly)
snmpNotifyEntry  31 Console trap nonVolatile
snmpNotifyEntry  32 va-primerib trap nonVolatile
 
 
 
#Entry type:snmpTargetAddrEntry
#Format: snmpTargetAddrName  (text)
#         snmpTargetAddrTDomain  (snmpUDPDomain, snmpIPXDomain, etc.)
#         snmpTargetAddrTAddress  (transport address,i.e. 192.147.142.254:0)
#         snmpTargetAddrTimeout  (integer)
#         snmpTargetAddrRetryCount  (integer)
#         snmpTargetAddrTagList  (text)
#         snmpTargetAddrParams  (text)
#         snmpTargetAddrStorageType  (nonVolatile, permanent, readOnly)
#         tgtAddressMask  (transport mask, i.e. 255.255.255.255:0)
snmpTargetAddrEntry  31 snmpUDPDomain 127.0.0.1:0 100 3 Console \
    v1ExampleParams nonVolatile 255.255.255.255:0
snmpTargetAddrEntry  32 snmpUDPDomain 127.0.0.1:0 100 3 Console \
    v2cExampleParams nonVolatile 255.255.255.255:0
snmpTargetAddrEntry  33 snmpUDPDomain 172.24.233.82:0 100 3 va-primerib \
    v1ExampleParams nonVolatile 255.255.255.255:0
snmpTargetAddrEntry  34 snmpUDPDomain 172.24.233.82:0 100 3 va-primerib \
    v2cExampleParams nonVolatile 255.255.255.255:0
 
 
#Entry type:snmpTargetParamsEntry
#Format: snmpTargetParamsName  (text)
#         snmpTargetParamsMPModel  (integer)
#         snmpTargetParamsSecurityModel  (snmpv1, snmpv2c, snmpv2s, usm)
#         snmpTargetParamsSecurityName  (text)
#         snmpTargetParamsSecurityLevel  (noAuthNoPriv,authNoPriv,authPriv)
#         snmpTargetParamsStorageType  (nonVolatile, permanent, readOnly)
snmpTargetParamsEntry  v1ExampleParams 0 snmpv1 public noAuthNoPriv \
    nonVolatile
snmpTargetParamsEntry  v2cExampleParams 1 snmpv2c public noAuthNoPriv \
    nonVolatile
 
 
#Entry type:snmpNotifyFilterProfileEntry
#Format: snmpTargetParamsName  (text)
#         snmpNotifyFilterProfileName  (text)
#         snmpNotifyFilterProfileStorageType  (nonVolatile,permanent,readOnly)
 
 
#Entry type:snmpNotifyFilterEntry
#Format: snmpNotifyFilterProfileName  (text)
#         snmpNotifyFilterSubtree  (OID)
#         snmpNotifyFilterMask  (octetString)
#         snmpNotifyFilterType  (included, excluded)
#         snmpNotifyFilterStorageType  (nonVolatile, permanent, readOnly)

Configuring the Execution Environment

This section provides instructions for configuring the SC host execution environment, and contains the following topics:

The configuration data file, or XECfgParm.dat file (located in /opt/TransPath/etc), lists all the components in the SC host and defines how it operates. The software automatically migrates Release 4 data in the XECfgParm.dat file to Release 7 format. The XECfgParm.dat file contains your execution environment parameters. However, only the default logging levels are migrated for the log priority parameters, including the foverd.logPrio parameter. Therefore, if you have set up specialized logging, you need to reset the parameters after software installation by editing the XECfgParm.dat file.

For more information on the XECfgParm.dat file, including sample files, see the Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide.

Note For Software Release 7.4(x), the XECfgParm.dat file is located in /opt/CiscoMGC/etc.

You must manually edit the execution environment parameters in the XECfgParm.dat file to initialize and configure the SC host software application.

Caution Do not edit any XECfgParm.dat file parameters not listed below, and remember that all parameters are case-sensitive. Otherwise, your system might not work as intended.

Accessing the XECfgParm.dat File

To access and edit the XECfgParm.dat file, complete the following steps:

Note If you have two SC hosts in a continuous-service configuration, the XECfgParm.dat files will be different for each host.

Step 1 Log in as root.

Step 2 If the SC software is running, enter the following command:

# /etc/init.d/transpath stop

Step 3 To ensure that the SC software is stopped, re-enter the stop command until the system verifies that the software is stopped.

Step 4 Change to the /opt/TransPath/etc directory, which contains the XECfgParm.dat file used by your system.

Note For Software Release 7.4(x), change to the /opt/CiscoMGC/etc directory.

Step 5 Open the XECfgParm.dat file with any text editor, such as vi.

Tips Migrated parameters are identified in the XECfgParm.dat file. You should verify these parameters; however, you should concentrate on the new parameters when editing the file.

Configuring Basic System Information

To configure basic system information required for your system to function, modify the following parameters in the first section of the XECfgParm.dat file:

Note If a parameter is identified as migrated, the previously configured value was saved during the upgrade and used in the new XECfgParm.dat file after migration.

Parameter Information Modification

*.transpathId

(Migrated)

Migrated

To identify the local SC host in a continuous-service configuration, enter any one- or two-digit integer.

Note   If you have two SC hosts in a continuous-service configuration, this number must be different in the XECfgParm.dat file for each host.

*.ownTranspathId

Migrated

To identify the local SC host in a redundant configuration, enter the same value that you used for *.transpathID.

Note   If you have two SC hosts hosts in a continuous-service configuration, enter this value in the *.peerTranspathID field in the XECfgParm.dat file on the second host server.
If you have a standalone configuration, leave this value blank.

*.peerTranspathId

Migrated

To identify the peer SC host in a continuous-service configuration, enter any one- or two-digit integer. The IDs must be unique in an active and standby pair.

Note   If you have two SC hosts hosts in a continuous-service configuration, enter the same value that you used for *.transpathID in the XECfgParm.dat file of the second host server in this field. If you have a standalone configuration, leave it blank.

*.desiredPlatformState

New parameter

To determine the desired platform state at initialization, enter one of the following values:

master, if you have two (active and standby) SC hosts

slave, if you have two (active and standby) SC hosts

standalone, if you have a single-host system (default)

Note   If you have two SC hosts in a continuous-service configuration, make sure that the active SC host is set to master and the standby host is set to slave.

*.SysCheckpointEnabled

New parameter

To enable or disable checkpointing, enter one of the following values:

false--Disables checkpointing. Calls are not preserved during switchover, and status messages are not sent to the replicator.

true--Enables checkpointing. Calls that are in the talking state are preserved and survive a control switchover. All status checkpointing information is sent to the replicator on the active side.

Note   If you have two SC hosts in a continuous-service configuration, enter true. If you have a standalone configuration, enter false.

*.numberOfThreads

New parameter

To specify the number of threads generated by multi-threaded processes such as the engine and the log master, enter one of the following values:

0 --Single CPU (default)

1--Two CPUs

2 --Four CPUs

Note   If you have a multi-CPU system, you must set engine.SysGeneratedCode to true (the default).

*.stPort

New parameter

Port number used between peer components or processes.

Enter any unused port number, for example, 7000. If your configuration uses a Cisco SLT, enter the port number on the Cisco SLT.

Note   If you have two SC hosts in a continuous-service configuration, enter a different number for this value in the XECfgParm.dat file on the secondary host, for example, 7001.

*.OwnClli

New parameter

Common language location identifier. To initiate circuit query validation if circuit queries are supported, enter an alphanumeric string of as many as 24 characters.

Default: TTT-SS-BB-XXX

Example: 1-22-33-444

Note   This parameter is commented out by default.

Specifying IP Addresses

To specify IP addresses, modify the following parameters in the first section of the XECfgParm.dat file:

Parameter Information Modification

*.ipAddrLocalA

Migrated from IP_Addr1

Enter the first local IP address (hme0); used for checkpointing and switchover heartbeats.

Note   This is typically the same value as *.IP_Addr1.

Caution No other machine on the network should have *.ipAddrLocalA set to 0.0.0.0.

*.ipAddrPeerA

Migrated from foverd.conn1AddrA

Enter the first corresponding peer IP address; used for checkpointing and failover heartbeats.

Note   If you have two SC hosts in a continuous-service configuration, this value is the IP address of the second host.

*.ipAddrLocalB

Migrated from IP_Addr2

Enter the second local IP address (hme1); used for checkpointing and failover heartbeats.

Note   If your configuration does not use a secondary Ethernet adapter, leave this address set to the default value, 0.0.0.0.

*.ipAddrPeerB

Migrated from foverd.conn2AddrB

Enter the second corresponding peer IP address; used for checkpointing and switchover heartbeats.

Note   If your configuration does not use a secondary Ethernet adapter, leave this address set to the default value, 0.0.0.0.

*.IP_Addr1

Migrated

Enter the IP address of interface 1; used for signaling. This is the same address as ipAddrLocalA.

*.IP_Addr2

Migrated

Enter the IP address of interface 2; used for signaling. This is the same address as ipAddrPeerA.

*.IP_Addr3

Migrated

Enter the IP address of interface 3 (if installed); used for signaling. This is the same address as ipAddrLocalB.

*.IP_Addr4

Migrated

Enter the IP address of interface 4 (if installed); used for signaling. This is the same address as ipAddrPeerB.

Configuring Engine Parameters

To configure parameters required for the engine to run correctly, modify the following parameters in the Engine section of the XECfgParm.dat file:

Parameter Information Modification

engine.SysVirtualSwitch

Migrated

To indicate that the SC host functions as a signaling controller, enter 0 (nailed trunks, no auditing is initiated).

engine.SysCdrCollection

Migrated

To designate the format of call detail records (CDRs), enter one of the following values:

true = generates old-style non-tagged CDRs

false = generates new TLV format CDRs (default)

Note Typically, this value should be false.

engine.SysGRSTimerInterval

New parameter

To specify the interval between group service (GRS) messages, set this value to 1000 (milliseconds).

engine.SysGRSBlockSize

New parameter

To specify the number of simultaneous GRS messages to send when the engine starts, set this value to 1.

engine.SysGeneratedCode

New parameter

To determine whether compiled or interpreted code is used, enter one of the following values:

true = system uses compiled code (default)

false = system uses interpreted code (used only for engineering and debugging)

Note Compiled code runs faster than interpreted code. Typically, this value should be true. If your configuration uses multiple CPUs, this value must be true.

Enabling Call Screening

To initialize the database that stores call screening information, modify the following parameter in the Engine section of the XECfgParm.dat file:

Parameter Information Modification

engine.SysScreeningCheck

New parameter

To enable or disable the A-number and B-number analysis (the call screening database), enter one of the following values:

If you do not have the database environment set with all the required data populated, set this value to false (default).

If you have the database and want the system to access it, set this value to true.

Configuring Call Detail Record File Output

To configure call detail record (CDR) file output, modify the following parameters in the Data Dumper and Engine sections of the XECfgParm.dat file:

Parameter Information Modification

engine.CDRencodingFormat

New parameter

To specify the call detail record (CDR) file encoding format, enter one of the following values:

AnsiCDB = North American (default)

ItuCDB = European

CustCDB = Custom

engine.CDRtimeStamp

New parameter

To specify the CDR file time stamp unit, enter one of the following values:

S = seconds (default)

M = milliseconds

Note   If your configuration uses TCAP, set this parameter to M.

engine.CDRmessageTypes

New parameter

To specify which call detail blocks (CDBs, statistics taken at various points in a call) are recorded during a call, enter one of the following values:

"1010, 1020, 1030, 1040, 1050, 1060, 1070"

"1060, 1110"

Each number represents a point in a call. 1060 is required. 1080 is an external value, used for TCAP.

Note   1110 generates a CDR file containing all CDBs for a call (end of call). If you choose 1110, you must specify milliseconds in the CDRtimeStamp parameter.

dmpr.openCDR

New parameter

To indicate whether the standard data dumper writes out CDR files, enter one of the following values:

true = Standard data dumper opens a CDR file and logs call detail blocks (CDBs).

false = Standard data dumper does not open a CDR file and does not log CDBs.

Note   The default CDR file format has been changed from an ASCII format in Release 4 to a binary format in Release 7. Use the dmpr.callDetail parameter to convert the files to an ASCII format, if necessary.

dmpr.callDetail

New parameter

If your configuration requires ASCII-formatted CDR files, enter /opt/TransPath/bin/converter. For Software Release 7.4(x), enter /opt/CiscoMGC/bin/converter.

If your configuration does not require ASCII-formatted CDR files, accept the default of /opt/TransPath/local/cdbscript.sh. For Software Release 7.4(x), the default is /opt/CiscoMGC/local/cdbscript.sh.

Note   The default CDR file format has changed from an ASCII format in Release 4 to a binary format in Release 7. This setting automatically generates CDR files in an ASCII, comma-delimited format in addition to the default, binary format. The ASCII file has a .csv extension. For more information on generating and viewing CDR files, see
Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.

Note For a detailed description of CDR files, see Cisco Media Gateway Controller Software Release 7 Reference Guide.

Configuring the System Type

To configure system alarm information, modify the following parameter in the XE section of the XECfgParm.dat file:

Parameter Information Modification

XE.systemType

New parameter

To specify the system type for alarm LEDs, enter one of the following values:

NETRA = Sun Netra t 1100, t 1120 (internal LEDs, alarm relays)

SPARC = Generic box (no alarm relays)

SPARC-ARU = Generic box (external alarm relays)

Default: SPARC

Configuring Switchover

: To configure switchover, modify the following parameters in the Foverd section of the XECfgParm.dat file:

Parameter Information Modification

foverd.conn1Type

Migrated

To set the connection type for connection number 1, enter serial or socket.

Note   Typically, set this value to socket.

foverd.ipLocalPortA

Migrated

To define the local port number used for IP communication, enter a unique number, for example, 1051 (if Type is socket).

Note   If you have two SC hosts hosts in a continuous-service configuration, enter this value in the foverd.ipPeerPortA field in the XECfgParm.dat file on the secondary host.

foverd.ipPeerPortA

Migrated

To define the peer port number used for IP communication, enter a unique number; for example, 1052.

Note   If you have two SC hosts in a continuous-service configuration, enter this value in the foverd.ipLocalPortA field in the XECfgParm.dat file on the secondary host.

foverd.conn2Type

New parameter

To set the connection type for connection number 2, enter serial or socket.

Note   Typically, set this value to socket.

foverd.ipLocalPortB

New parameter

To define the secondary local port number used for IP communication, enter a unique number, for example, 1053 (if Type is socket).

Note   If you have two SC hosts in a continuous-service configuration, enter this value in the foverd.ipPeerPortB field in the XECfgParm.dat file on the secondary host.

foverd.ipPeerPortB

New parameter

To define the secondary local port number used for IP communication, enter a unique number; for example, 1054.

Note   If you have two SC hosts in a continuous-service configuration, enter this value in the foverd.ipLocalPortB field in the XECfgParm.dat file on the secondary host.

foverd.conn3Type

New parameter

To set the connection type for connection number 3, enter serial or socket.

Note   Typically, set this value to serial.

foverd.conn3Addr

New parameter

To specify the address of the peer system, enter a location. For example, /dev/term/a.

If your configuration does not use connection number 3, enter /dev/null (default).

Note   If your configuration uses an 8-port connector as a serial connection for switchover, you must modify the read-write permissions for the connection. For more information, see the Release Notes for the Cisco Media Gateway Controller Software Release 7.

foverd.abswitchPort

Migrated

To specify the port used for communication with the A/B switch, enter a location. For example, /dev/term/a.

If your configuration does not use an A/B switch, use the default value (/dev/null).

Note   Because this is a migrated field, if you are discontinuing use of the A/B switch after the upgrade, you need to change the value to /dev/null.

foverd.heartbeatInterval

New parameter

Specifies the maximum time in milliseconds between heartbeat messages from the peer failover daemon. This interval defines the frequency that the failover daemon exchanges heartbeat messages with its peer.

Default: 4000 milliseconds (4 seconds).

Note For more information on switchover, see the Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.

Initializing the Provisioning Object Manager (POM)

To configure the Provisioning Object Manager (POM), modify the following parameters in the POM section of the XECfgParm.dat file:

Parameter Information Modification

pom.dataSync

New parameter

Used in a continuous-service configuration to indicate that the POM should synchronize the provisioning data at startup. If you have a standalone system, set this value to false.

Note In the upgrade, if you have a continuous-service or high-availability configuration, you must initially set this value on the second host server you are upgrading to false. After you upgrade the second SC host and both hosts are running the same version of software, you must change this value to true. See "Completing the Upgrade," for more information.

pom.port

New parameter

Used in a continuous-service configuration to indicate the port number the POM uses to communicate with its peer. Enter any integer from 4001 through 4050, or default.

Note This is a platform-specific value and depends on your system installation. You should only modify this value if the default port (4001) is being used by another process or application.

Saving the XECfgParm.dat File

Save your changes and close the editor.

Note For a complete list of parameters, their function, definition, and example values, see the Cisco Media Gateway Controller Software Release 7 Reference Guide.

This completes the XE configuration. Continue to the next section to configure SCP queries using TCAP. If you do not need to configure SCP queries, go to the "Initializing the Call Screening Database" section.

Configuring SCP Queries

The Signal Control Point (SCP) translates routing information for the Advanced Intelligent Network (AIN) database queries over TCAP. This section provides instructions for selecting the type of translation you will use to enable SCP database queries. The trigger.dat file (located in /opt/TransPath/etc/trigger.dat), contains the message sending table that contains translation values. You must manually edit the parameters in the trigger.dat file to enable SCP queries.

Note In Release 7.4(x), the trigger.dat file is located in /opt/CiscoMGC/etc.

This section contains the following topics:

Caution Do not edit any trigger.dat file parameters not listed below, and remember that all parameters are case-sensitive. Otherwise, your system might not work as intended.

For more information on the trigger.dat file, including a sample configured file, see Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide.

Before You Start

You will need to know the translationType value from the Global Title Translation tables on the STP. Get this value from the administrator of your STP.

Modifying the Trigger.dat File

To access and edit the trigger.dat file, complete the following steps:

Note If you have two SC hosts in a continuous-service configuration, you must modify the trigger.dat file on each host.

Step 1 Navigate to directory /opt/TransPath/etc.

Note For Software Release 7.4(x), navigate to /opt/CiscoMGC/etc.

Step 2 Copy the trigger.dat file to transpathID.trigger, where transpathID is the *.transpathID value in the XECfgParm.dat file on that host:

cd /opt/TransPath/etc
cp trigger.dat 01.trigger

Step 3 Open the transpathID.trigger file in your editor.

Step 4 In the transpathID.trigger file, find the $MessageSending table.

Step 5 Edit the file as follows:

a. In the $MessageSending table, select the type of translation you are using. This value will be the in the seventh column of the table. (See the "$MessageSending Table Values" below.)

# MS 1:Sprint LNP
# MS 2:Generic LNP
# MS 3:Genesys 800
# MS 4:ANSI AIN 800 NPA
# MS 5:ANSI AIN 800 NPA-NXX
# MS 6:ANSI AIN 800 NPA-NXX-XXX
# MS 7:ANSI AIN 800 Termination information
# MS 8:ANSI PRE AIN 800
# MS 9:ANSI PRE AIN 800 Termination information

b. In the table for your translation type, change the translationType value (column F7) to the Global Title Translation table value you got from the administrator of your STP.

Table 6-1:

F1

F2

F3

F4

F5

F6

F7

F8

F9

F10

F11

F12

F13

F14

F15

F16

F17

F18

F19

F20

F21

Transport

tcapType

stpScpGroupIndex

msg

asn1Encoding

tcv_sk

translationType

tcapBodyType

gtSsn

dpcPres

ssnPres

dpcNetwork

dpcCluster

dpcMember

ssn

gtFormat

OS1

OS2

OS3

OS4

OS5

# MS 1: Sprint LNP

1
2
0
6
0
0
255
1
0
0
1
0
0
0
0
2
1
0
0
0
0

# MS 2: Generic LNP

1
2
0
6
0
37
255
1
0
0
1
0
0
0
0
2
2
0
0
0
0

# MS 3: Genesys 800

2
1
1
1
0
0
0
1
0
0
1
0
0
0
0
2
3
0
0
0
0

# MS 4: ANSI AIN 800 NPA

1
2
0
6
0
4
255
1
0
0
1
0
0
0
0
2
4
0
0
0
0

# MS 5: ANSI AIN 800 NPA-NXX

1
2
0
6
0
5
255
1
0
0
1
0
0
0
0
2
4
0
0
0
0

# MS 6: ANSI AIN 800 NPA-NXX-XXX

1
2
0
6
0
8
255
1
0
0
1
0
0
0
0
2
4
0
0
0
0

# MS 7: ANSI AIN 800 Termination information

1
2
0
5
0
0
255
1
0
0
1
0
0
0
0
2
5
0
0
0
0

# MS 8: ANSI PRE AIN 800

1
3
0
6
0
0
254
2
0
0
1
0
0
0
0
2
6
0
0
0
0

# MS 9: ANSI PRE AIN 800 Termination information

1
3
0
5
0
0
254
2
0
0
1
0
0
0
0
2
7
0
0
0
0

$MessageSending Table Values

Step 6 Save your changes and close the editor.

Initializing the Call Screening Database

During installation, the installation script (install.sh) installs and initializes a database that the SC host can use to store call screening information for number analysis. The system performs A-number (calling number) and B-number (called number) call screening. The database stores screened calls to a white list or black list, based on whether or not A-numbers should allowed to complete to specific B-numbers. White listed calls are allowed to complete, and black listed calls are not.

During a typical installation, you should see output similar to the following:

Preparing to install TimesTen 3.2 in /opt on va-cerulean
   Executing TimesTen installation script...
   
   Of the three components:
 
     [1] TimesTen Client/Server and Data Manager
     [2] TimesTen Data Manager Only
     [3] TimesTen Client Only
   
   Install in /opt/TimesTen32
   Creating /opt/TimesTen32 ...
   extracting /opt/ttdb-install/SunOS251/ttserver.tar ...
System logging appears to be configured correctly.
(TimesTen syslog messages seem to be recorded in the file '/var/adm/messages')
   Starting the daemon for solaris ...
The 32-bit daemon has started successfully.
   Server startup scripts not required - ignored
   Installing TimesTen Server...
What is the DNS name, host name, or IP address of the server [va-cerulean]: 
What is the TCP/IP port number that you want the TimesTen Server to listen on [23232]: 
What is Filename and Location of server.odbc.ini file [/var/TimesTen32/32/server/server.odbc.ini]: 
TimesTen Connect Configuration completed.
   extracting /opt/ttdb-install/SunOS251/doc.tar ...
   
Install complete
   TimesTen installation script returned status 0

Call Screening Database Information

The call screening database is stored in the /opt/TimesTen32/datastore directory. It is called the TimesTen database, or howdydb. The maximum database size is 256 megabytes, which is specified in the .odbc.ini file.

Note You cannot change the database name.

.odbc.ini File Information

The .odbc.ini file specifies the location of the database storage, and it is located in the /opt/TransPath/local directory.

Note For Release 7.4(x), the file is located in the /opt/CiscoMGC/local directory.

Following is an example of an .odbc.ini file.

[ODBC Data Sources]
howdydb=TimesTen 3.2 Driver
 
[howdydb]
Driver=/opt/TimesTen32/32/lib/libtten.so
DataStore= /opt/TimesTen32/datastore/howdydb
DurableCommits=0
ExclAccess=0
ThreadSafe=1
WaitForConnect=0
Size=256
 
[ODBC]
Trace=0
TraceFile=
Installdir=/opt/TimesTen32/32

Replication in a Continuous-Service Configuration

If you have two SC hosts in a continuous-service configuration, you must perform database replication between the two machines. During replication, any updates applied to the database on one machine will be replicated to the other.

Note Before you can initialize the databases, you must install the SC software on both machines.

Replication of Identical Data

To perform database replication between two SC hosts having the same (or no) data in the databases, complete the following steps:

Step 1

Active Host

Standby Host

setup_replication.sh system2 howdydb

setup_replication.sh system1 howdydb

Enter the following commands:

Step 2 Perform the procedures in the "Verifying Database Replication" section .

Replication of Existing Data to a Machine Containing No Data

Step 1 Use the following commands to replicate a populated database from one SC host to a machine having no data:

Old System (Existing Data)
New System (No Data)

Shut down the database.

setup_replication.sh NewSystem yourdsn

Mkdir dir_name

TtRepAdmin -dsn yourdsn -receiver -name NewSystem -backup dir_name

Transport the contents of dir_name from OldSystem to NewSystem:

TtRestore -fname replica -dir dir_name DSN=yourdsn

TtRepAdmin -dsn yourdsn -self -restored dir_name

TtRepAdmin -dsn yourdsn -self -swap NewSystem

TtRepAdmin -dsn yourdsn -table cisco.whitelist_a -sendto OldSystem

TtRepAdmin -dsn yourdsn -table cisco.whitelist_b -sendto OldSystem

TtRepAdmin -dsn yourdsn -table cisco.blacklist_a -sendto OldSystem

TtRepAdmin -dsn yourdsn -table cisco.blacklist_b -sendto OldSystem

TtAdmin -repPolicy manual yourdsn

TtAdmin -repStart yourdsn

Step 2 Perform the procedures in the "Verifying Database Replication" section .

Verifying Database Replication

Use the following MML commands to verify that database replication is functioning:

:

To...
enter the following command...

Perform a single insert on one machine

numan-add:bwhite:custgrpid="S018",svcname="TESTSVC",CLI="9999"

Query the entry on the second machine to see if it exists

numan-rtrv:bwhite:custgrpid="S018",svcname="TESTSVC",CLI="9999"

Perform a single delete

numan-dlt:bwhite:custgrpid="S018",svcname="TESTSVC",CLI="9999"

Troubleshooting

If you have problems during replication, try stopping and restarting the replication as follows:

Step 1 Stop the replication by entering:

# /etc/init.d/ttreplic stop

Step 2 Restart the replication by entering:

# /etc/init.d/ttreplic start

Step 3 Retry the commands listed in the "Verifying Database Replication" section .

If your output differs from the example in the "Verifying Database Replication" section , or if you suspect problems or errors in the database installation, try the following:

Ensure that the database is installed in the /opt/TimesTen32 directory.
Check the log file for installation errors (the log file is in the directory /opt/TimesTen32/datastore).
If necessary, remove the CSCOga002 package using the pkgrm command, and reinstall it using the pkgadd -d command.

Note When you remove a package, do not include the .pkg extension. For example, pkgrm CSCOga002. Do use the extension when you are adding the package.

Starting the SC Software

After configuring the SC software, you must stop and start the SC software.

Tips If you installed ITK or PTI drivers, the system rebooted and the SC software will be running. If you did not install the drivers, your SC software has not yet been started.

To stop the SC software:

Step 1 As the root user, enter the /etc/init.d/transpath stop command.

Step 2 Enter ps -ef | grep procM to ensure the software is not running. If you receive no response, the software is stopped.

Note For Software Release 7.4(x), enter /etc/init.d/CiscoMGC stop to stop the software.

To start the SC software:

Step 1 As the root user, enter the /etc/init.d/transpath start command.

Step 2 Enter ps -ef | grep procM to ensure the software is running.

Note For Software Release 7.4(x), enter the /etc/init.d/CiscoMGC start command.

Verifying the SC Software Processes are Running

To verify the software processes are running, start an MML session while logged in as a user that is in the transpath group.

Note For Software Release 7.4(x), start an MML session while logged in as a user in the mgcgrp group.

After starting MML, enter the rtrv-softw:all command. All processes should be running. For example:

SC-7A mml> rtrv-softw:all
   Virtual Switch Controller 2000-04-18 18:23:05
M  RTRV
   "CFM-01:RUNNING"
   "ALM-01:RUNNING"
   "MM-01:RUNNING"
   "AMDMPR-01:RUNNING"
   "CDRDMPR-01:RUNNING"
   "DSKM-01:RUNNING"
   "MMDB-01:RUNNING"
   "POM-01:RUNNING"
   "MEASAGT:RUNNING"
   "OPERSAGT:RUNNING"
   "PROVSAGT:RUNNING"
   "PRIIP-1:RUNNING"
   "Replic-01:RUNNING"
   "ENG-01:RUNNING"
   "IOCM-01:RUNNING"
   "TCAP-01:RUNNING"
   "IOCC-ASP:RUNNING"
   "FOD-01:RUNNING"
   "SS7-A-1:RUNNING"
   ;

Tips If all processes are not running, an error has occurred. You might see a response similar to the following example.

SC-7A mml> rtrv-softw:all
   Virtual Switch Controller 2000-04-18 16:51:13
M  RTRV
   "CFM-01:RUNNING"
   "ALM-01:RUNNING"
   "MM-01:RUNNING"
   "AMDMPR-01:RUNNING"
   "CDRDMPR-01:RUNNING"
   "DSKM-01:RUNNING"
   "MMDB-01:RUNNING"
   "POM-01:RUNNING"
   "MEASAGT:RUNNING"
   "OPERSAGT:RUNNING"
   "PROVSAGT:RUNNING"
   "PRIIP-1:STOPPED"
   "Replic-01:STOPPED"
   "ENG-01:INIT"
   "IOCM-01:STOPPED"
   "TCAP-01:STOPPED"
   "IOCC-ASP:STOPPED"
   "FOD-01:STOPPED"
   "SS7-A-1:STOPPED"
   ;

If all processes are not running, perform the following:

Step 1 Quit MML and return to the UNIX prompt.

Step 2 Verify the swap size by entering the swap -l command. The output is similar to the following:

# swap -l
swapfile             dev  swaplo blocks   free
/dev/dsk/c0t0d0s1   32,121     16 1049744 290320

Note One block equals 512 bytes, so the number of blocks (1049744) divided by 512 gets the size of swap in kilobytes.

Step 3 If your swap size is less than 2040 megabytes, you must add more swap space. To add a swap file, find a partition with extra space and enter mkfile filesizem filename, where filesize is the size of the file in megabytes. Enter swap -a filename to add the swap. Add the swap definition to /etc/vfstab to make it add automatically on a reboot.

Step 4 If you have 2040 megabytes or more of swap space, your IP addresses in the XECfgParm.dat might be incorrect. Look in the replicator log located in /opt/TransPath/var/log. If you see output similar to the following example, you might have an IP address mismatch:

Wed Apr 19 12:19:00:426 2000 | rep_log (PID 18977) <Info>
Replicator:got initialized with serviceId = 196621, ipAddrLocalA = 10.14.7.1, ipAddrLocalB = 10.14.17.1, ipAddrPeerA = 10.14.7.2, ipAddrPeerB = 10.14.17.2, portDataChannelSend = 0, portDataChannelRecv = 2970, portCommChannelSend = 0, portCommChannelRecv = 2974
 
Wed Apr 19 12:19:00:429 2000 | rep_log (PID 18977) <Info>
DataReceiverA:accepting connections at 10.14.7.1:2970
 
Wed Apr 19 12:19:00:432 2000 | rep_log (PID 18977) <Error>
DataSenderA:could not establish connection to 10.14.7.2:2970 (Connection refused) 
 
Wed Apr 19 12:19:00:433 2000 | rep_log (PID 18977) <Info>
DataReceiverB:failed to open acceptor at 10.14.17.1:2970 (Cannot assign requested address)
 
Wed Apr 19 12:19:00:433 2000 | rep_log (PID 18977) <Error>
Replicator:cannot open module DataLinkB
 
Wed Apr 19 12:19:05:807 2000 | rep_log (PID 18986) <Info>
Replicator:got initialized with serviceId = 196621, ipAddrLocalA = 10.14.7.1, ipAddrLocalB = 10.14.17.1, ipAddrPeerA = 10.14.7.2, ipAddrPeerB = 10.14.17.2, portDataChannelSend = 0, portDataChannelRecv = 2970, portCommChannelSend = 0, portCommChannelRecv = 2974
 
Wed Apr 19 12:19:05:810 2000 | rep_log (PID 18986) <Info>
DataReceiverA:accepting connections at 10.14.7.1:2970
 
Wed Apr 19 12:19:05:812 2000 | rep_log (PID 18986) <Error>
DataSenderA:could not establish connection to 10.14.7.2:2970 (Connection refused) 
 
Wed Apr 19 12:19:05:813 2000 | rep_log (PID 18986) <Info>
DataReceiverB:failed to open acceptor at 10.14.17.1:2970 (Cannot assign requested address)
 
Wed Apr 19 12:19:05:813 2000 | rep_log (PID 18986) <Error>
Replicator:cannot open module DataLinkB
 
Wed Apr 19 12:19:15:956 2000 | rep_log (PID 18988) <Info>
Replicator:got initialized with serviceId = 196621, ipAddrLocalA = 10.14.7.1, ipAddrLocalB = 10.14.17.1, ipAddrPeerA = 10.14.7.2, ipAddrPeerB = 10.14.17.2, portDataChannelSend = 0, portDataChannelRecv = 2970, portCommChannelSend = 0, portCommChannelRecv = 2974
 
Wed Apr 19 12:19:15:959 2000 | rep_log (PID 18988) <Info>
DataReceiverA:accepting connections at 10.14.7.1:2970
 
Wed Apr 19 12:19:15:961 2000 | rep_log (PID 18988) <Error>
DataSenderA:could not establish connection to 10.14.7.2:2970 (Connection refused) 
 
Wed Apr 19 12:19:15:962 2000 | rep_log (PID 18988) <Info>
DataReceiverB:failed to open acceptor at 10.14.17.1:2970 (Cannot assign requested address)
 
Wed Apr 19 12:19:15:962 2000 | rep_log (PID 18988) <Error>
Replicator:cannot open module DataLinkB
 
Wed Apr 19 12:19:31:100 2000 | rep_log (PID 18989) <Info>
Replicator:got initialized with serviceId = 196621, ipAddrLocalA = 10.14.7.1, ipAddrLocalB = 10.14.17.1, ipAddrPeerA = 10.14.7.2, ipAddrPeerB = 10.14.17.2, portDataChannelSend = 0, portDataChannelRecv = 2970, portCommChannelSend = 0, portCommChannelRecv = 2974
 
Wed Apr 19 12:19:31:103 2000 | rep_log (PID 18989) <Info>
DataReceiverA:accepting connections at 10.14.7.1:2970
 
Wed Apr 19 12:19:31:105 2000 | rep_log (PID 18989) <Error>
DataSenderA:could not establish connection to 10.14.7.2:2970 (Connection refused) 
 
Wed Apr 19 12:19:31:106 2000 | rep_log (PID 18989) <Info>
DataReceiverB:failed to open acceptor at 10.14.17.1:2970 (Cannot assign requested address)
 
Wed Apr 19 12:19:31:106 2000 | rep_log (PID 18989) <Error>
Replicator:cannot open module DataLinkB
 
Wed Apr 19 12:19:51:259 2000 | rep_log (PID 18993) <Info>
Replicator:got initialized with serviceId = 196621, ipAddrLocalA = 10.14.7.1, ipAddrLocalB = 10.14.17.1, ipAddrPeerA = 10.14.7.2, ipAddrPeerB = 10.14.17.2, portDataChannelSend = 0, portDataChannelRecv = 2970, portCommChannelSend = 0, portCommChannelRecv = 2974
 
Wed Apr 19 12:19:51:261 2000 | rep_log (PID 18993) <Info>
DataReceiverA:accepting connections at 10.14.7.1:2970
 
Wed Apr 19 12:19:51:264 2000 | rep_log (PID 18993) <Error>
DataSenderA:could not establish connection to 10.14.7.2:2970 (Connection refused) 
 
Wed Apr 19 12:19:51:265 2000 | rep_log (PID 18993) <Info>
DataReceiverB:failed to open acceptor at 10.14.17.1:2970 (Cannot assign requested address)
 
Wed Apr 19 12:19:51:265 2000 | rep_log (PID 18993) <Error>
Replicator:cannot open module DataLinkB

Note Refer to the "Specifying IP Addresses" section for more information. Your IP_Addr1 parameter must match the IP address of the hme0 interface on your host. Your IP_Addr2 parameter must match the IP address of the hme1 interface on your host. The hme0 interface was set while installing the Sun Solaris software; refer to the "Loading the Sun Solaris 2.6 Operating System" section. The hme1 interface was set after the operating system installation; refer to the "Configuring a Second Ethernet Interface" section.

Where to Go Next

Proceed to "Completing the Upgrade," for final upgrade procedures.

F1	F2	F3	F4	F5	F6	F7	F8	F9	F10	F11	F12	F13	F14	F15	F16	F17	F18	F19	F20	F21
Transport	tcapType	stpScpGroupIndex	msg	asn1Encoding	tcv_sk	translationType	tcapBodyType	gtSsn	dpcPres	ssnPres	dpcNetwork	dpcCluster	dpcMember	ssn	gtFormat	OS1	OS2	OS3	OS4	OS5
# MS 1: Sprint LNP
1	2	0	6	0	0	255	1	0	0	1	0	0	0	0	2	1	0	0	0	0
# MS 2: Generic LNP
1	2	0	6	0	37	255	1	0	0	1	0	0	0	0	2	2	0	0	0	0
# MS 3: Genesys 800
2	1	1	1	0	0	0	1	0	0	1	0	0	0	0	2	3	0	0	0	0
# MS 4: ANSI AIN 800 NPA
1	2	0	6	0	4	255	1	0	0	1	0	0	0	0	2	4	0	0	0	0
# MS 5: ANSI AIN 800 NPA-NXX
1	2	0	6	0	5	255	1	0	0	1	0	0	0	0	2	4	0	0	0	0
# MS 6: ANSI AIN 800 NPA-NXX-XXX
1	2	0	6	0	8	255	1	0	0	1	0	0	0	0	2	4	0	0	0	0
# MS 7: ANSI AIN 800 Termination information
1	2	0	5	0	0	255	1	0	0	1	0	0	0	0	2	5	0	0	0	0
# MS 8: ANSI PRE AIN 800
1	3	0	6	0	0	254	2	0	0	1	0	0	0	0	2	6	0	0	0	0
# MS 9: ANSI PRE AIN 800 Termination information
1	3	0	5	0	0	254	2	0	0	1	0	0	0	0	2	7	0	0	0	0

Old System (Existing Data)	New System (No Data)
Shut down the database.
setup_replication.sh NewSystem yourdsn
Mkdir dir_name
TtRepAdmin -dsn yourdsn -receiver -name NewSystem -backup dir_name
Transport the contents of dir_name from OldSystem to NewSystem:
	TtRestore -fname replica -dir dir_name DSN=yourdsn
	TtRepAdmin -dsn yourdsn -self -restored dir_name
	TtRepAdmin -dsn yourdsn -self -swap NewSystem
	TtRepAdmin -dsn yourdsn -table cisco.whitelist_a -sendto OldSystem
	TtRepAdmin -dsn yourdsn -table cisco.whitelist_b -sendto OldSystem
	TtRepAdmin -dsn yourdsn -table cisco.blacklist_a -sendto OldSystem
	TtRepAdmin -dsn yourdsn -table cisco.blacklist_b -sendto OldSystem
	TtAdmin -repPolicy manual yourdsn
	TtAdmin -repStart yourdsn

Table of Contents

Installing and Configuring the SC Software