|
|
Table Of Contents
Upgrading Cisco SC2200 Software
Identifying the Active Configuration
Removing a Previous Version of the Cisco MGC Software (Release 7.4(x))
Installing SC Software Release 7.3(x)
Installing SC Software Release 7.4(x)
Installing Patches for the SC Software
Installing a GUI Provisioning Tool on a Separate Server
Installing the Voice Service Provisioning Tool
Configuring SNMP Support Resources
Configuring the Execution Environment
Opening the XECfgParm.dat File
Configuring Basic System Information
Configuring Automatic Congestion Control
Configuring Call Detail Record File Output
Configuring the Clearing Location and Default Location Parameters
Configuring *.GWClearChannelAlgorithm Parameter
Initializing the Provisioning Object Manager (POM)
Configuring the trigger.dat File Attributes
Initializing the Call Screening Database
Verifying Database Replication
Verifying SC Software is Running Properly
Perform a Test Call and Switchover
Verifying the Platform State of the SC Hosts
Verifying the Status of all Signaling Channels
Verifying the Status of all Traffic Channels
Verifying the Status of all Destinations
Verifying Proper Migration of Data
Migrating Inactive SC Host Configurations
Provisioning the Configuration
Upgrading Cisco SC2200 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
Tip
•
TERM=xtermexport TERMstty rows 24•
•
Identifying the Active Configuration
Identify and make note of the name of the active configuration by performing the following steps:
Step 1
config-libThe system returns a response similar to the following.
The Configuration File Library Main Menu1. List Configuration Versions in Library2. Save Production to a new Library Version3. Copy Library Version to Production4. Remove Configuration Library VersionEnter Selection or 'q' to quit>Step 2
At the bottom of the list, a configuration is identified as being the current production version. This is the name of your active configuration.
Removing a Previous Version of the Cisco Telephony Controller Software (Release 4 and Release 7.3(x))
Note
Before upgrading the SC software, you must first uninstall the previous software version. To remove the Cisco telephony controller software, complete the following steps:
Step 1
Step 2
# cd /cdrom/cdrom0# ./uninstall.shStep 3
Timesaver
Step 4
When package removal is finished, the following message appears:
Uninstallation log can be found in /tmp/uninstall.log.Step 5
cd /etcStep 6
Step 7
Step 8
This completes the removal of the previous version of the telephony controller software. If you have questions or need assistance, see the "Obtaining Technical Assistance" section on page xviii.
Removing a Previous Version of the Cisco MGC Software (Release 7.4(x))
Before upgrading an existing release of the SC host software, you must first uninstall the previous software version.
Note
To remove the SC host software, complete the following steps:
Step 1
Step 2
# ./uninstall.shStep 3
If you answer no to the following question you will lose all new provisioning work.Is the uninstall being done in order to upgrade to a new version of the software? [y] [y,n,?,q]Step 4
Timesaver
Step 5
When package removal is finished, the following message appears:
Uninstallation log can be found in /tmp/uninstall.log.Step 6
cd /etcStep 7
Step 8
Step 9
This completes the removal of the previous version of the SC host software. If you have questions or need assistance, see the "Obtaining Technical Assistance" section on page xviii.
Installing SC Software Release 7.3(x)
To install Software Release 7.3(x), follow these steps:
Note
Step 1
Step 2
# cd /cdrom/cdrom0# ./install.shStep 3
Use supplied admin file for unattended install? [n] [y,n,?,q]Answer y to perform an unattended installation. If you answer n, you must answer prompts and press Enter for each package that is installed.
Note
Step 4
Install Telephony Configuration Manager (TCM) package? [n] [y,n,?,q]Answer y if you want to install the CMM on this host.
Tips
Step 5
Base directory for CMM (default /opt/VSCprov) [?,q]Press Enter to accept the default directory, /opt/VSCprov. We recommend that you not change the directory.
Step 6
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]Answer y to install the utilities package. This package must be installed before you install the rest of the software.
Caution
Step 7
Enter transpath user name [transpath]Enter transpath UID [20000]Enter transpath group name [transpath]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 is determined and reused, or you are prompted to enter another ID.
Caution
The system returns a message that the CSCOgu000 utilities package was successfully installed.
Step 8
If a reboot is not required, the installation continues uninterrupted. When the installation is finished, continue to Step 9.
If a reboot is required, perform the following steps when prompted:
a.
Note
b.
# cd /cdrom/cdrom0# ./install.shc.
Step 9
This completes installing the SC software.
Note
Tip
Step 1
Step 2
Step 3
Installing SC Software Release 7.4(x)
To install Software Release 7.4(x), follow these steps:
Note
Step 1
Step 2
cd /etcStep 3
Step 4
Step 5
Step 6
Step 7
Caution
When the upgrade has successfully completed, it is strongly recommended that you delete the software you copied from the CD-ROM to your directory, to avoid running out of disk space.
Step 8
# ./install.shStep 9
Use supplied admin file for unattended install? [n] [y,n,?,q]Answer y to perform an unattended installation. If you answer n, you must answer prompts and press Enter for each package that is installed.
Note
Step 10
Install Cisco Media Gateway Controller Manager (CMM/Toolkit) package?[n] [y,n,?,q]Answer y if you want to install the CMM and the Toolkit applications on this host.
Tips
Step 11
Base directory for CMM/Toolkit (default /opt/CMM) [?,q]Press Enter to accept the default directory, /opt/CMM. We recommend that you not change the directory.
Step 12
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]Answer y to install the utilities package. This package must be installed before you install the rest of the software.
Caution
Step 13
Base directory for CiscoMGC (default /opt/CiscoMGC) [?,q]Enter CiscoMGC user name [mgcusr]Enter CiscoMGC UID [20000]Enter CiscoMGC group name [mgcgrp]Enter CiscoMGC GID [2000]We recommend that you accept the default values for each of the prompts (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
The system returns a message that the CSCOgu000 utilities package was successfully installed.
Step 14
Note
If a reboot is not required, the installation continues uninterrupted. When the installation is finished, continue to Step 15.
If a reboot is required, perform the following steps when prompted:
a.
Note
b.
# ./install.shc.
Use supplied admin file for unattended install? [n] [y,n,?,q]
Install Cisco Media Gateway Controller Manager (CMM/Toolkit) package? [n] [y,n,?,q]
d.
e.
Step 15
After the check is complete, the following prompt appears:
Configure System for (1) Maximum Sustained Calls (2) High Call ThroughputEnter 1 or 2 or q to quit
Note
Enter 1 or 2 to choose the option you want and press Enter.
Step 16
This completes installing the SC software.
Note
Tip
Step 1
Step 2
Step 3
Installing Patches for the SC Software
There may be new patches available for your new SC software. Check the following URL for the latest patches:
http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml
Click on the link for the software version of the Cisco Media Gateway Controller software that you just installed. The README files contain information about installing the patches. Download the files you need and follow the README file instructions.
For more information on patches for your release of the SC software, refer to the Release Notes for the Cisco Media Gateway Controller Software Release 7.
Installing a GUI Provisioning Tool on a Separate Server
You can install the GUI provisioning tools for the Cisco SC2200 on separate servers. The procedures to install the various GUI provisioning tools are described in the following sections:
•
Note
Installing the CMM
You can install the CMM on a separate server than the SC software. To install only the CMM, perform the following steps:
Step 1
Step 2
cd /cdrom/cdrom0Step 3
./install-cmm-tool.shAnswer yes to the onscreen prompts.
This completes installing the CMM on a separate host. Proceed to the "Configuring SNMP Support Resources" section.
Installing the Voice Service Provisioning Tool
The Voice Service Provisioning Tool (VSPT) is a graphical configuration/provisioning tool that enables you to create or modify configuration files across multiple devices such as MGCs and Cisco Media Gateways. If you are a registered Cisco.com user, you can download the VSPT from the Cisco website. For more information on VSPT, see Cisco Voice Services Provisioning Tool Users Guide.
The following files are located on the VSPT:
Prerequisites
To install the VSPT, you must have the following:
•
Note
•
•
–
–
Approximately 1 MB for each configuration
Approximately 1 MB for each configuration snapshot
–
Approximately 0.5 MB for each deployment
•
–
–
•
–
–
Upgrading VSPT Software
If you have an older version of VSPT already installed (such as VSPT Version 1.1) and you are upgrading to VSPT Version 1.5, the existing VSPT data is automatically migrated to VSPT version 1.5; you do not need to uninstall the older version. However, if an incremental version is detected during the installation you will be prompted to uninstall the older version (for example, Version 1.5.1 cannot co-exist with Version 1.5.2 and must first be uninstalled).
To uninstall the software:
Note
Step 1
su -root
cd /
/opt/CSCOspgw/uninstall/uninstall
The uninstallation process removes all files and directories created by the installation process. If a directory contains a file that was not created during the installation process, it is not removed and is logged in the uninstall.log file. This might occur in the data and logs directories.
Step 2
Installing the VSPT Software
To install VSPT, follow the procedures listed below:
Step 1
http:/www/cisco.com/cgi-bin/tablebuild.pl/vspt
Note
Step 2
This completes the VSPT software installation. If you have questions or need assistance, see the "Obtaining Technical Assistance" section on page xviii.
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.
2.
3.
4.
5.
In a continuous-service or high-availability configuration, the SNMP agent subsystem runs on both the active and standby Cisco MGCs.
Note
To configure the SNMP resources, complete the following steps:
Step 1
cd /etcStep 2
Note
If the names match, proceed to Step 4. Otherwise, proceed to Step 3.
Step 3
Save your changes and exit the utility when you are finished.
Step 4
more servicesThe following lines should display among other port entries:
snmp 161/udpsnmp-trap 162/udpIf the ports for SNMP are listed, proceed to Step 9. Otherwise, continue to Step 3.
Step 5
vi servicessnmp 161/udpsnmp-trap 162/udpSave your changes and exit the editor when you are finished.
Step 6
more servicesThe following lines should display among other port entries (otherwise, repeat Step 3):
snmp 161/udpsnmp-trap 162/udpStep 7
ps -ef | grep snmpdStep 8
kill -HUP process_IDWhere process_ID is the process ID number for the SNMP process, as identified in Step 5.
Step 9
ps -ef | grep snmpdStep 10
more/tmp/snmpd.logIf no errors are found, this means the process is working and you can use the ports for SNMP configuration and trap generation.
Step 11
•
•
•
•
•
Step 12
Note
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.(d) From the "Load/Unload MIBs:SNMP /Load MIB from File" window, select the MIB to load (for example, tp.my).(e) Click OK.
Tip
Step 13
Note
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
Tip
Step 14
a.
snoop -d eth_int port 162Where eth_int is the name of the Ethernet interface.
For example, to execute this command on an Ethernet interface called hme1, you would enter the following command:
snoop -d hme1 port 162b.
set-dest-state:dpc1:OOSEntering a command like this should cause an trap notification to appear in the first telnet session. For example, the following trap information is displayed in the first telnet session when a destination is taken out-of-service and then returned to service:
Using device /dev/hme (promiscuous mode)va-perch -> nssuramb4.cisco.com UDP D=162 S=46842 LEN=446va-perch -> nssuramb4.cisco.com UDP D=162 S=46842 LEN=446If trap information appears in the first telnet session, the procedure is complete.
If nothing appears in the first telnet session, re-enter the snoop command for the other Ethernet interface and repeat the above step. If trap information fails to appear in either Ethernet interface, proceed to Step 15.
Step 15
Sample Configured snmpd.cf File
The following shows a sample snmpd.cnf file.
Note
# Entry type: sysDescr# Entry format: octetStringsysDescr "SNMPv3 agent from Cisco Systems, Inc."# Entry type: sysObjectID# Entry format: OIDsysObjectID transpath# Entry type: sysLocation# Entry format: octetStringsysLocation "Herndon, Virginia"# Entry type: sysContact# Entry format: octetStringsysContact "Cisco Systems, Inc. +1 703 484 3000"# Entry type: sysName# Entry format: octetStringsysName "NSSU - MGC"# Entry type: snmpEnableAuthenTraps# Entry format: integersnmpEnableAuthenTraps 1# Entry type: MAX_THREADS# Entry format: integerMAX_THREADS 25# Entry type: MAX_PDU_TIME# Entry format: integerMAX_PDU_TIME 80000# Entry type: MAX_OUTPUT_WAITING# Entry format: integerMAX_OUTPUT_WAITING 65536# Entry type: MAX_SUBAGENTS# Entry format: integerMAX_SUBAGENTS 15# Entry type: subagent# Entry format: octetString#Entry type: snmpCommunityEntry#Format: snmpCommunityIndex (text)# snmpCommunityName (text)# snmpCommunitySecurityName (text)# snmpCommunityContextEngineID (octetString)# snmpCommunityContextName (text)# snmpCommunityTransportTag (text)# snmpCommunityStorageType (nonVolatile, permanent, readOnly)snmpCommunityEntry admin mgcusr mgcusr localSnmpID - - nonVolatilesnmpCommunityEntry readonly public public localSnmpID - - nonVolatilesnmpCommunityEntry user private private localSnmpID - - nonVolatile# Entry type: communityEntry# Entry format: srCommunityAuthSnmpID (snmpID)# srCommunityName (textOctetString)# srCommunityGroupName (textOctetString)# srCommunityContextSnmpID (snmpID)# srCommunityContextName (textOctetString)# srCommunityTransportLabel (textOctetString)# srCommunityMemoryType (integer)# Entry type: snmpEngineBoots# Entry format: integersnmpEngineBoots 3#Entry type: usmUserEntry#Format: usmUserEngineID (octetString)# usmUserName (text)# usmUserAuthProtocol (OID)# usmUserPrivProtocol (OID)# usmUserStorageType (nonVolatile, permanent, readOnly)# usmTargetTag (text)# AuthKey (octetString)# PrivKey (octetString)#Entry type: vacmAccessEntry#Format: vacmGroupName (text)# vacmAccessContextPrefix (text)# vacmAccessSecurityModel (snmpv1, snmpv2c, snmpv2s, usm, http)# vacmAccessSecurityLevel (noAuthNoPriv, authNoPriv, authPriv)# vacmAccessContextMatch (exact, prefix)# vacmAccessReadViewName (text)# vacmAccessWriteViewName (text)# vacmAccessNotifyViewName (text)# vacmAccessStorageType (nonVolatile, permanent, readOnly)vacmAccessEntry User - snmpv1 noAuthNoPriv exact All RemoteWrite All \nonVolatilevacmAccessEntry User - snmpv2c noAuthNoPriv exact All RemoteWrite All \nonVolatilevacmAccessEntry Guest - snmpv1 noAuthNoPriv exact All - All nonVolatilevacmAccessEntry Guest - snmpv2c noAuthNoPriv exact All - All nonVolatilevacmAccessEntry SuperUser - snmpv1 noAuthNoPriv exact All Write All \nonVolatilevacmAccessEntry SuperUser - snmpv2c noAuthNoPriv exact All Write All \nonVolatile#Entry type: vacmSecurityToGroupEntry#Format: vacmSecurityModel (snmpv1, snmpv2c, snmpv2s, usm, http)# vacmSecurityName (text)# vacmGroupName (text)# vacmSecurityToGroupStorageType (nonVolatile, permanent, readOnly)vacmSecurityToGroupEntry snmpv1 mgcusr SuperUser nonVolatilevacmSecurityToGroupEntry snmpv1 public Guest nonVolatilevacmSecurityToGroupEntry snmpv1 private User nonVolatilevacmSecurityToGroupEntry snmpv2c mgcusr SuperUser nonVolatilevacmSecurityToGroupEntry snmpv2c public Guest nonVolatilevacmSecurityToGroupEntry snmpv2c private User nonVolatile#Entry type: vacmViewTreeFamilyEntry#Format: vacmViewTreeFamilyViewName (text)# vacmViewTreeFamilySubtree (OID)# vacmViewTreeFamilyMask (octetString)# vacmViewTreeFamilyType (included, excluded)# vacmViewTreeFamilyStorageType (nonVolatile, permanent, readOnly)vacmViewTreeFamilyEntry All iso - included nonVolatilevacmViewTreeFamilyEntry All 0.0 - included nonVolatilevacmViewTreeFamilyEntry All hrSWRunEntry.0.2147483647 ff:df excluded \nonVolatilevacmViewTreeFamilyEntry All hrSWRunPerfEntry.0.2147483647 ff:df excluded \nonVolatilevacmViewTreeFamilyEntry Write iso - included nonVolatilevacmViewTreeFamilyEntry Write mib_2 - excluded nonVolatilevacmViewTreeFamilyEntry RemoteWrite iso - included nonVolatilevacmViewTreeFamilyEntry RemoteWrite mib_2 - excluded nonVolatilevacmViewTreeFamilyEntry RemoteWrite critAppProcEntry.0.1 ff:f7 excluded \nonVolatilevacmViewTreeFamilyEntry RemoteWrite critAppProcEntry.0.2 ff:f7 excluded \nonVolatilevacmViewTreeFamilyEntry RemoteWrite critAppProcEntry.0.3 ff:f7 excluded \nonVolatilevacmViewTreeFamilyEntry RemoteWrite critAppProcEntry.0.4 ff:f7 excluded \nonVolatile#Entry type: snmpNotifyEntry#Format: snmpNotifyName (text)# snmpNotifyTag (text)# snmpNotifyType (trap(1), inform(2))# snmpNotifyStorageType (nonVolatile, permanent, readOnly)snmpNotifyEntry 32 TrapSink 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)# snmpTargetAddrTMask (transport mask, i.e. 255.255.255.255:0)# snmpTargetAddrMMS (integer)snmpTargetAddrEntry 34 snmpUDPDomain 127.0.0.1:0 100 3 TrapSink \v2cExampleParams nonVolatile 255.255.255.255:0 2048#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 \nonVolatilesnmpTargetParamsEntry 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)#Entry type: httpUserNameEntry#Format: httpUserName (text)# httpUserGroupName (text)# httpUserTransportLabel (text)# httpUserStorageType (nonVolatile, permanent, readOnly)# Password (octetString)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/CiscoMGC/etc), lists all the components in the SC host and defines how it operates. The software automatically migrates your data for the previous release in the XECfgParm.dat file to current 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.
You must manually edit the execution environment parameters in the XECfgParm.dat file to initialize and configure the SC host software application.
Caution
Opening the XECfgParm.dat File
To access and edit the XECfgParm.dat file, complete the following steps:
Note
Step 1
Step 2
Tip
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
Specifying IP Addresses
To specify IP addresses, modify the following parameters in the first section of the XECfgParm.dat file:
Note
For example, consider the following configuration:
*.ipAddrLocalA = 172.22.119.108*.ipAddrLocalB = 172.22.119.54This is not a valid combination because the Ethernet interfaces are on the same subnet. The following example illustrates a valid combination:
*.ipAddrLocalA = 172.22.119.108*.ipAddrLocalB = 172.22.120.54If the two Ethernet interfaces are on the same subnet, then one of them must be physically disconnected from the existing subnet and then connected to a different subnet. The new IP address must be appropriately configured on the system. Refer to the manual pages for the UNIX command ifconfig for more information.
Configuring Engine Parameters
In order for the engine to run correctly, you must modify the following parameters in the Engine section of the XECfgParm.dat file:
Configuring Automatic Congestion Control
As of release 7.4(11), the Cisco SC2200 supports Automatic Congestion Control (ACC). ACC regulates traffic to levels that can be handled effectively by the network by rejecting traffic when the system is congested. This increases the throughput of completed calls through the telephone network during periods of overload.
When the Cisco MGC is congested, an Automatic Congestion Level (ACL) indication is sent to adjacent signaling points using SS7 ISUP. Until the congestion abates, a certain percentage of calls are rejected. Detection of congestion is based on the measurement of the Cisco MGC's CPU utilization level.
ACC is controlled by parameters that are found in the XECfgParm.dat file and by a property associated with the signaling service, which are described in the following sections:
•
•
Overload Level Percentage Parameters
Use the following XECfgParm.dat parameters to set the overload level percentages:
CPU Timer Interval Parameter
The CPUTimerInterval parameter is used to specify the interval, in milliseconds, at which the CPU utilization level of the Cisco MGC is sampled. The default value is 1000. We recommend that you stay within the range of 500 to 2000 milliseconds.
Maximum ACL Value
Another component in ACC is the maximum ACL value. Since ANSI- and ITU-based signaling points have different maximum ACL values, the Cisco MGC uses a property, MaxACL, associated with an SS7 signaling service or trunk group to map the internal maximum ACL value to the value used by the adjacent signaling point.
When the Cisco MGC is congested, its congestion level can be reported to adjacent signaling points by the ACL value in the release message. ANSI-based signaling points use a range of 0 through 3 to define congestion and ITU-based signaling points use a range of 0 through 2 to define congestion. When MaxACL is set to 3, the internal maximum ACL value is mapped to the ANSI standard (the default value for MaxACL is 3). When MaxACL is set to 2, the internal maximum ACL value is mapped to the ITU standard. MaxACL also has a third possible setting, 0, which disables the sending of ACL indications in the Release message.
The procedure to set this property can be found in the Cisco MGC Software Release 7 Operations, Maintenance, and Troubleshooting Guide.
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:
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:
Note
Configuring the System Type
To configure system alarm information, modify the following parameter in the XE section of the XECfgParm.dat file:
Configuring the Clearing Location and Default Location Parameters
This property overrides the Clearing Location and Default Location fields in Call Context. Change the clearing location value if you need a value other than the default to be sent to the switch. Change the default location value if you need to define a customer-specific default location for your system that can differ from the default location set in the type definition of the protocol.
Configuring *.GWClearChannelAlgorithm Parameter
Clear channel calls get through only if you set the *.GWClearChannelAlgorithm parameter to a value other than null. This parameter is sent to the Cisco MGC when the connection is created and matches the Cisco MGC's clear channel parameter.
Configuring Switchover
To configure switchover, modify the following parameters in the Foverd section of the XECfgParm.dat file:
:
Note
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:
Saving the XECfgParm.dat File
Save your changes and close the editor.
Note
This completes the XE configuration. Continue the upgrade process as described in your chosen upgrade procedure.
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/CiscoMGC/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.
This section contains the following topics:
•
Caution
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.
Configuring the trigger.dat File Attributes
Note
Caution
You can configure the following Cisco MGC trigger.dat file attributes to perform a Transaction Capabilities Application Part (TCAP) query:
•
•
•
Configuring the Global Title Translation Attribute
Perform the following steps to configure the Global Title Translation attribute:
Step 1
Step 2
Step 3
Step 4
Step 5
Note
Step 6
Step 7
a.
b.
c.
Note
Step 8
Step 9
# /etc/init.d/CiscoMGC startConfiguring the Service Key Value Attribute
Perform the following steps to configure the Service Key Value (tcv_sk) attribute:
Step 1
Step 2
Step 3
Step 4
Step 5
Note
Step 6
Caution
Step 7
a.
b.
Step 8
Step 9
# /etc/init.d/CiscoMGC startConfiguring the Translation Type Attribute
Perform the following steps to configure the Translation Type (translationType) attribute:
Step 1
Step 2
Step 3
Step 4
Step 5
Note
Step 6
Caution
Step 7
a.
b.
Step 8
Step 9
# /etc/init.d/CiscoMGC startTable 7-2
$MessageSending Table Values
Sample trigger.dat File
#--//******************************************************************************#--//* Table_9.trigger *#--//* *#--//* TRIGGER TABLES *#--//* *#--//* (c) 1999-2000 CISCO SYSTEMS, INC.. ALL RIGHTS RESERVED. *#--//* THIS SOFTWARE CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF *#--//* CISCO SYSTEMS, INC.. USE, DISCLOSURE, OR REPRODUCTION IS PROHIBITED *#--//* WITHOUT THE PRIOR EXPRESS WRITTEN PERMISSION OF THE CISCO SYSTEMS, INC.. *#--//* *#--//******************************************************************************# "$Id: Table_9.trigger,v 1.11.2.3 1999/09/20 18:20:51 xxxxxxxx Exp $";# "(c) 1999-2000 Cisco Systems, Inc.. All Rights Reserved."#############$TriggerTable############## All fields are pointers to records of other types# F1 F2 F3 F4 F5 F6 F7# MA MS RR1 RR2 RR3 RR4 RR5#----------------------------------# TT 1: xxxxxx LNP#----------------------------------1 1 1 2 0 0 0#----------------------------------# TT 2: Generic LNP#----------------------------------2 2 1 3 0 0 0#----------------------------------# TT 3: xxxxxxx 800#----------------------------------3 3 10 4 5 0 0#----------------------------------# TT 4: ANSI AIN 800 NPA#----------------------------------4 4 10 6 7 0 0#----------------------------------# TT 5: ANSI AIN 800 NPA-NXX#----------------------------------4 5 10 6 7 0 0#----------------------------------# TT 6: ANSI AIN 800 NPA-NXX-XXXX#----------------------------------4 6 10 6 7 0 0#----------------------------------# TT 7: ANSI AIN 800 Termination Information#----------------------------------5 7 10 0 0 0 0#----------------------------------# TT 8: ANSI PRE AIN AIN 800#----------------------------------4 8 10 8 9 0 0#----------------------------------# TT 9: ANSI PRE AIN 800 Termination Information#----------------------------------5 9 10 0 0 0 0##############$MessageAction################ F1 F2 F3 F4 F5 F6 F7 F8 F9 F10# ACT1 REQ ACT2 REQ ACT3 REQ ACT4 REQ ACT5 REQ#-------------------------------------------------# MA 1: xxxxxx LNP#-------------------------------------------------1 1 3 0 0 0 0 0 0 0#-------------------------------------------------# MA 2: Generic LNP#-------------------------------------------------1 1 2 1 3 0 0 0 0 0#-------------------------------------------------# MA 3: xxxxxxx 800#-------------------------------------------------1 1 3 0 0 0 0 0 0 0#-------------------------------------------------# MA 4: ANSI AIN 800 / ANSI PRE AIN 800#-------------------------------------------------1 1 3 0 0 0 0 0 0 0#-------------------------------------------------# MA 5: ANSI AIN 800 Termination Information / PRE AIN 800 Termination Information#-------------------------------------------------4 1 0 0 0 0 0 0 0 0###############$MessageSending################# gtFormat Values# GTFORMAT_DO_NOT_USE_GLOBAL_TITLE := 0# GTFORMAT_USE_GLOBAL_TITLE_TRANSLATION_TYPE_NUMBERING_SCHEME_ENCODING_SCHEME := 1# GTFORMAT_USE_GLOBAL_TITLE_TRANSLATION_TYPE := 2# GTFORMAT_USE_GLOBAL_TITLE_ONLY := 3# GTFORMAT_UNKNOWN := 4#
Note
# 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: xxxxxx 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 6 37 255 0 1 0 0 2 0 0 0 0#----------------------------------------------------------------------------------------# MS 3: xxxxxxx 800#----------------------------------------------------------------------------------------2 1 1 0 1 0 0 0 2 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 0 255 0 1 0 0 4 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################$OperationSending################### F1 F2 F3 F4 F5# componentType opClass opCodeFamily opCodeSpecifier opCodeFlag# F6 F7# correlationRequired PS#----------------------------------------------------------------------------------------# OS 1: xxxxxx LNP#----------------------------------------------------------------------------------------6 1 3 0#----------------------------------------------------------------------------------------# OS 2: Generic LNP#----------------------------------------------------------------------------------------6 100 4 2#----------------------------------------------------------------------------------------# OS 3: xxxxxxx 800#----------------------------------------------------------------------------------------1 0 4 3#----------------------------------------------------------------------------------------# OS 4: ANSI AIN 800#----------------------------------------------------------------------------------------6 100 4 0 4#----------------------------------------------------------------------------------------# OS 5: ANSI AIN 800 Termination Information Should have correlationRequired = 1#----------------------------------------------------------------------------------------6 1 103 4 4 0 5#----------------------------------------------------------------------------------------# OS 6: ANSI PRE AIN 800#----------------------------------------------------------------------------------------6 1 3 1 3 0 6#----------------------------------------------------------------------------------------# OS 7: ANSI PRE AIN 800 Termination Information#----------------------------------------------------------------------------------------2 1 0 0 0 0 7################$ParameterSending################### F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 F13 F14 F15 F16 F17 F18# PA1 REQ PA2 REQ PA3 REQ PA4 REQ PA5 REQ PA6 REQ PA7 REQ PA8 REQ PA9 REQ# F19 F20# PA10 REQ#----------------------------------------------------------------------------------------# PS 1: xxxxxx LNP#----------------------------------------------------------------------------------------100 1 101 1 102 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------# PS 2: Generic LNP#----------------------------------------------------------------------------------------100 1 101 1 102 1 103 1 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------# PS 3: xxxxxxx 800#----------------------------------------------------------------------------------------200 1 201 1 202 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------# PS 4: ANSI AIN 800 (All types)#----------------------------------------------------------------------------------------100 1 101 1 102 1 103 1 104 1 109 0 110 0 111 0 112 0 113 0#----------------------------------------------------------------------------------------# PS 5: ANSI AIN 800 Termination Information#----------------------------------------------------------------------------------------105 1 106 1 107 0 108 0 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------# PS 6: ANSI PRE AIN 800#----------------------------------------------------------------------------------------17 1 2 1 16 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------# PS 7: ANSI PRE AIN 800 Termination Information#----------------------------------------------------------------------------------------21 1 20 1 22 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0#################$ReceivedResponse################### F1 F2# MR RA#----------------------------------------------------------------------------------------# RR 1: xxxxxx LNP / Generic LNP Default#----------------------------------------------------------------------------------------0 1#----------------------------------------------------------------------------------------# RR 2: xxxxxx LNP 1st expected#----------------------------------------------------------------------------------------1 2#----------------------------------------------------------------------------------------# RR 3: Generic LNP 1st expected#----------------------------------------------------------------------------------------1 3#----------------------------------------------------------------------------------------# RR 4: xxxxxxx 800 1st expected (Result)#----------------------------------------------------------------------------------------2 1#----------------------------------------------------------------------------------------# RR 5: xxxxxxx 800 2st expected (Error)#----------------------------------------------------------------------------------------3 4#----------------------------------------------------------------------------------------# RR 6: ANSI AIN 800 With termination status notification#----------------------------------------------------------------------------------------4 5#----------------------------------------------------------------------------------------# RR 7: ANSI AIN 800#----------------------------------------------------------------------------------------5 6#----------------------------------------------------------------------------------------# RR 8: ANSI PRE AIN 800 With termination status notification#----------------------------------------------------------------------------------------6 7#----------------------------------------------------------------------------------------# RR 9: ANSI PRE AIN 800#----------------------------------------------------------------------------------------7 8#----------------------------------------------------------------------------------------# RR 10: ANSI AIN 800 / PRE AIN 800 Default#----------------------------------------------------------------------------------------0 9#################$MessageReceiving################### F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11# MSG OR1 REQ OR2 REQ OR3 REQ OR4 REQ OR5 REQ#------------------------------------------------------# MR 1: xxxxxx LNP / Generic LNP#------------------------------------------------------8 1 1 0 0 0 0 0 0 0 0#------------------------------------------------------# MR 2: xxxxxxx 800 (Result)#------------------------------------------------------3 2 1 0 0 0 0 0 0 0 0#------------------------------------------------------# MR 3: xxxxxxx 800 (Error)#------------------------------------------------------3 3 1 0 0 0 0 0 0 0 0#------------------------------------------------------# MR 4: ANSI AIN 800 with termination status notification#------------------------------------------------------8 4 1 5 1 0 0 0 0 0 0#------------------------------------------------------# MR 5: ANSI AIN 800#------------------------------------------------------8 4 1 0 0 0 0 0 0 0 0#------------------------------------------------------# MR 6: ANSI PRE AIN 800 with termination status notification#------------------------------------------------------8 6 1 7 1 0 0 0 0 0 0#------------------------------------------------------# MR 7: ANSI PRE AIN 800#------------------------------------------------------8 6 1 0 0 0 0 0 0 0 0###################$OperationReceiving##################### F1 F2 F3 F4 F5 F6# componentType opClass opCodeFamily opCodeSpecifier opCodeFlag PR#----------------------------------------------------------------------# OR 1: xxxxxx LNP / Generic LNP#----------------------------------------------------------------------6 1 101 1 4 1#----------------------------------------------------------------------# OR 2: xxxxxxx 800 (Result)#----------------------------------------------------------------------1 1 0 20 4 2#----------------------------------------------------------------------# OR 3: xxxxxxx 800 (Error)#----------------------------------------------------------------------3 1 0 0 4 3#----------------------------------------------------------------------# OR 4: ANSI AIN 800#----------------------------------------------------------------------6 1 101 1 4 4#----------------------------------------------------------------------# OR 5: ANSI AIN 800 Request for status notification#----------------------------------------------------------------------6 1 103 5 4 5#----------------------------------------------------------------------# OR 6: ANSI PRE AIN 800#----------------------------------------------------------------------6 1 4 1 3 6#----------------------------------------------------------------------# OR 7: ANSI PRE AIN 800 Request for status notification#----------------------------------------------------------------------6 1 6 1 4 7###################$ParameterReceiving#################### F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 F13 F14 F15 F16# PA1 REQ ACT PA2 REQ ACT PA3 REQ ACT PA4 REQ ACT PA5 REQ ACT PA6REQ F17 F18 F19 F20 F21 F22 F23 F24 F25 F26 F27 F28 F29 F30ACT PA7 REQ ACT PA8 REQ ACT PA9 REQ ACT PA10 REQ ACT#----------------------------------------------------------------------------------------# PR 1: xxxxxx LNP / Generic LNP#----------------------------------------------------------------------------------------102 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------# PR 2: xxxxxxx 800 (Result)#----------------------------------------------------------------------------------------205 1 1 206 1 1 204 1 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------# PR 3: xxxxxxx 800 (Error)#----------------------------------------------------------------------------------------205 1 1 206 1 1 204 1 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------# PR 4: ANSI AIN 800 Result#----------------------------------------------------------------------------------------102 1 1 110 0 2 113 0 2 114 1 2 115 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------# PR 5: ANSI AIN 800 Status request#----------------------------------------------------------------------------------------- ------------------------------------------------------------105 1 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------- ------------------------------------------------------------# PR 6: ANSI PRE AIN 800 Result#----------------------------------------------------------------------------------------- ------------------------------------------------------------8 0 2 4 1 1 18 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0#----------------------------------------------------------------------------------------# PR 7: ANSI PRE AIN 800 Status request#----------------------------------------------------------------------------------------20 1 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0###############$ResponseAction################# F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 F13 F14 F15# ACT1 REQ DAT ACT2 REQ DAT ACT3 REQ DAT ACT4 REQ DAT ACT5 REQ DAT#--------------------------------------------------------------------------# RA 1: xxxxxx LNP Default & Generic LNP Default#--------------------------------------------------------------------------4 1 2 0 0 0 0 0 0 0 0 0 0 0 0#--------------------------------------------------------------------------# RA 2: xxxxxx LNP 1st Expected#--------------------------------------------------------------------------4 1 2 0 0 0 0 0 0 0 0 0 0 0 0#--------------------------------------------------------------------------# RA 3: Generic LNP 1st Expected#--------------------------------------------------------------------------1 1 0 4 1 2 0 0 0 0 0 0 0 0 0#--------------------------------------------------------------------------# RA 4: xxxxxxx (Error)#--------------------------------------------------------------------------0 0 0 0 0 0 0 0 0 0 0 0 0 0 0#--------------------------------------------------------------------------# RA 5: ANSI AIN 800 with termination status notification#--------------------------------------------------------------------------2 0 1 4 1 3 0 0 0 0 0 0 0 0 0#--------------------------------------------------------------------------# RA 6: ANSI AIN AIN 800#--------------------------------------------------------------------------4 1 3 0 0 0 0 0 0 0 0 0 0 0 0#--------------------------------------------------------------------------# RA 7: ANSI PRE AIN 800 with termination status notification#--------------------------------------------------------------------------2 0 4 4 1 3 0 0 0 0 0 0 0 0 0#--------------------------------------------------------------------------# RA 8: ANSI PRE AIN 800#--------------------------------------------------------------------------4 1 3 0 0 0 0 0 0 0 0 0 0 0 0#--------------------------------------------------------------------------# RA 9: 800 Default#--------------------------------------------------------------------------4 1 3 0 0 0 0 0 0 0 0 0 0 0 0###########$ActionData############# F1 F2 F3 F4 F5#-----------------------# AD 1: ANSI AIN 800 Data for RESULT_ACTION_RE_TRIGGER_VIA_LCM (to send termination information)# Trg Pic Null Null Null#--------------------------7 13 0 0 0# AD 2: ANSI LNP Data for RESULT_ACTION_SEND_ACTION_TO_LCM# Act Null Null Null NULL#--------------------------1 0 0 0 0# AD 3: ANSI AIN / PRE AIN 800 Data for RESULT_ACTION_SEND_ACTION_TO_LCM# Act Null Null Null NULL#--------------------------2 0 0 0 0# AD 4: ANSI PRE AIN 800 Data for RESULT_ACTION_RE_TRIGGER_VIA_LCM (to send termination information)# Trg Pic Null Null Null#--------------------------9 13 0 0 0This completes the SCP configuration. Continue to the next section to initialize the call-screening database. If you have questions or need assistance, see the "Obtaining Technical Assistance" section on page xviii.
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.
You might want to perform white and black list screening to include or exclude calls from certain numbers. You can provision white lists that specify allowed A-numbers (calling numbers) or B-numbers (called numbers). Black lists block specified A-numbers (calling numbers) or B-numbers (called numbers).
The call screening database is stored in the /opt/TimesTen32/datastore directory. The database name is howdydb. The maximum database size, 256 MB, is specified in the .odbc.ini file shown in the ".odbc.ini File Information" section.
This section contains the following topics:
Note
.odbc.ini File Information
The .odbc.ini file specifies the location of the database storage, and it 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.soDataStore= /opt/TimesTen32/datastore/howdydbDurableCommits=0ExclAccess=0ThreadSafe=1WaitForConnect=0Size=256[ODBC]Trace=0TraceFile=Installdir=/opt/TimesTen32/32Setting Up Replication
If you have two telephony controller hosts in a continuous-service or high-availability system, you must set up database replication between the two hosts. During replication, any updates applied to the database on one host are replicated in the database on the other. Data is transferred real time and does not require the committing or deploying of a configuration.
Replication copies data changes to either database after the initial setup. However, if you have data on one host, and you want the same data on another host, you must back up and move the data over, in addition to configuring replication.
If this is the initial installation of the software, and you do not have any data in the database, perform the following steps. If you do have data in one database and want to copy it to the other host, proceed to the "Initializing Replication and Copying the Database to Another Host" section.
Note
If you have data in both databases, and the databases do not match, contact the TAC for assistance in merging the databases.
Initializing Database Replication
To set up the initial replication, perform the following steps:
Step 1
setup_replication.sh standbyhost howdydbWhere standbyhost is the name (not IP address) of your standby host. In Example 7-1, the active host is hostx and the standby host is hosty.
Caution
Example 7-1 Initializing Database Replication on the Active Host
hostx% setup_replication.sh hosty howdydbSetting up replication to node hosty for DSN howdydbAdding cisco.whitelist_aAdding cisco.blacklist_aAdding cisco.whitelist_bAdding cisco.blacklist_bAdding cisco.portednumbersAdding cisco.numbertermRAM Residence Policy : inUseRAM Residence Grace (Secs) : 0Manually Loaded In Ram : FalsePurge Logs for Data Store : TrueLogging Enabled : TrueReplication Manually Started : TrueStep 2
setup_replication.sh activehost howdydbWhere activehost is the name (not IP address) of your active host. In the Example 7-2, the active host is hostx and the standby host is hosty.
Caution
Example 7-2 Initializing Database Replication on the Standby Host
hosty% setup_replication.sh hostx howdydbSetting up replication to node hostx for DSN howdydbAdding cisco.whitelist_aAdding cisco.blacklist_aAdding cisco.whitelist_bAdding cisco.blacklist_bAdding cisco.portednumbersAdding cisco.numbertermRAM Residence Policy : inUseRAM Residence Grace (Secs) : 0Manually Loaded In Ram : FalsePurge Logs for Data Store : TrueLogging Enabled : TrueReplication Manually Started : TrueProceed to the "Verifying Database Replication" section.
Initializing Replication and Copying the Database to Another Host
If you have existing data in one database and want to copy the data to another machine—for example, from the active to standby machine—perform the following steps:
Step 1
setup_replication.sh standbyhost howdydbWhere standbyhost is the name (not IP address) of your standby host. In Example 7-3, the active host is hostx and the standby host is hosty.
Caution
Example 7-3 Initializing Database Replication on the Active Host
hostx% setup_replication.sh hosty howdydbSetting up replication to node hosty for DSN howdydbAdding cisco.whitelist_aAdding cisco.blacklist_aAdding cisco.whitelist_bAdding cisco.blacklist_bAdding cisco.portednumbersAdding cisco.numbertermRAM Residence Policy : inUseRAM Residence Grace (Secs) : 0Manually Loaded In Ram : FalsePurge Logs for Data Store : TrueLogging Enabled : TrueReplication Manually Started : TrueStep 2
mkdir /backupdbStep 3
ttRepAdmin -dsn howdydb -receiver -name standbyhost -backup dirnameWhere standbyhost is the name (not IP address) of the standby host and dirname is the name of the directory you created in Step 2.
For example:
ttRepAdmin -dsn howdydb -receiver -name hosty -backup backupdbStep 4
Step 5
ttDestroy /opt/TimesTen32/datastore/howdydbStep 6
ttRestore -fname replica -dir dirname DSN=howdydbwhere dirname is the name of the directory you created. For example:
ttRestore -fname replica -dir backupdb DSN=howdydbThe restore process is being initiatedRestore completeStep 7
ttRepAdmin -dsn howdydb -self -restored dirnamettRepAdmin -dsn howdydb -self -swap standbyhostFor example:
hosty% ttRepAdmin -dsn howdydb -self -restored backupdbhosty% ttRepAdmin -dsn howdydb -self -swap hostySelf swap with peer hosty successfulStep 8
ttRepAdmin -dsn howdydb -table cisco.whitelist_a -sendto activehostttRepAdmin -dsn howdydb -table cisco.whitelist_b -sendto activehostttRepAdmin -dsn howdydb -table cisco.blacklist_b -sendto activehostttRepAdmin -dsn howdydb -table cisco.blacklist_a -sendto activehostttAdmin -repPolicy manual howdydbttAdmin -repStart howdydbFor example:
hosty% ttRepAdmin -dsn howdydb -table cisco.whitelist_a -sendto hostxhosty% ttRepAdmin -dsn howdydb -table cisco.whitelist_b -sendto hostxhosty% ttRepAdmin -dsn howdydb -table cisco.blacklist_b -sendto hostxhosty% ttRepAdmin -dsn howdydb -table cisco.blacklist_a -sendto hostxhosty% ttAdmin -repPolicy manual howdydbRAM Residence Policy : inUseRAM Residence Grace (Secs) : 0Manually Loaded In Ram : FalsePurge Logs for Data Store : TrueLogging Enabled : TrueReplication Manually Started : Falsehosty% ttAdmin -repStart howdydbRAM Residence Policy : inUseRAM Residence Grace (Secs) : 0Manually Loaded In Ram : FalsePurge Logs for Data Store : TrueLogging Enabled : TrueReplication Manually Started : TrueStep 9
Verifying Database Replication
To verify that replication is working, perform the following steps:
Step 1
Step 2
hostx mml> prov-sta::srcver="new",dstver="test",confirmVSC-01 - Media Gateway Controller 2000-08-30 11:31:15M COMPLD"PROV-STA";Step 3
hostx mml> numan-add:bwhite:custgrpid="S018",svcname="testsvc",cli="9998"VSC-01 - Media Gateway Controller 2000-08-30 11:31:25M COMPLD"bwhite";Step 4
Step 5
Step 6
hosty mml> prov-sta::srcver="new",dstver="test",confirmStep 7
hosty mml> numan-rtrv:bwhite:custgrpid="S018",svcname="testsvc",cli="9998"VSC-01 - Media Gateway Controller 2000-08-30 11:33:52M RTRV"session=test:bwhite"/* The cli :9998: exists. */;Step 8
Troubleshooting
If you have problems during replication, try stopping and restarting the replication as follows:
Step 1
# /etc/init.d/ttreplic stopStep 2
# /etc/init.d/ttreplic startIf you still have problems, retry the commands listed in the "Verifying Database Replication" section. If your output differs from the example in that section, or if you suspect problems or errors in the database installation, try the following:
Step 1
Step 2
If you find installation errors in the log file, remove and reinstall the CSCOga002 package, as follows:
Step 1
#pkgrm CSCOga002Step 2
# pkgadd -d CSCOga002.pkgIf you have questions or need assistance, see the "Obtaining Technical Assistance" section on page xviii.
Restarting the SC Software
After configuring the SC software, you must stop and start the SC software.
Tip
To stop the SC software:
Step 1
Step 2
Note
To start the SC software:
Step 1
Step 2
Note
Terminating Signaling Links
The SS7 signaling links connect the SC host running Cisco SC software to an SS7 switch. These SS7 signaling links are connected to the Cisco SLT, which connects to the SC host over IP.
If you are upgrading a standalone machine, you can remove the links from your machine and connect them to the Cisco SLTs now.
If you have a high-availability or continuous service configuration, perform these steps:
Step 1
Step 2
Caution
Note
The Cisco SLT requires the Cisco 2611 modular access router with T1 or E1 interfaces running a special release of Cisco IOS software. The Cisco SLT has the following restrictions:
•
–
–
–
–
–
–
–
–
•
•
•
Moving the Signaling Links in a Standalone Configuration
To move the signaling links, follow these steps:
Step 1
Step 2
If you have one SS7 signaling link, unplug the SS7 signaling link from the ITK card on the SC host and plug it into the WIC on the Cisco SLT.
If you have two SS7 signaling links, follow these steps:
a.
b.
c.
d.
Step 3
Step 4
Step 5
set-sc-state:linkname:ISWhere linkname is the name you provisioned in the "Terminating Signaling Links" section.
If the signaling links cannot go in-service, back out the new SC software installation using the procedures in the "Migrating Inactive SC Host Configurations" section.
Moving the Signaling Links in a Continuous-Service Configuration
To move the signaling links, follow these steps:
Step 1
Step 2
If you have one SS7 signaling link, unplug the SS7 signaling link from the ITK card on the SC host and plug it into the WIC on the Cisco SLT.
If you have two SS7 signaling links, follow these steps:
a.
b.
c.
d.
Tip
Step 3
Step 4
Step 5
set-sc-state:linkname:ISWhere linkname is the name you provisioned in the "Terminating Signaling Links" section.
If the signaling links cannot go in-service, back out the new SC software installation using the procedures in the "Migrating Inactive SC Host Configurations" section.
Verifying SC Software is Running Properly
To verify that the SC software is running properly you should perform the tests described in the following sections:
•
•
•
•
•
•
Perform a Test Call and Switchover
Perform the following procedure to test the ability of the software installed on the upgraded SC host to handle a switchover operation:
Note
Step 1
Step 2
sw-over::confirmIf the call is sustained, the procedure is complete. Otherwise, proceed to Step 3.
Step 3
Verifying the Platform State of the SC Hosts
Ensure that the recently upgraded SC hosts is in the active platform state and that the other SC host is in the standby platform state. If your system uses an SC host in a simplex configuration, the single SC host is always active. To do this, complete the following steps:
Step 1
rtrv-neThe system should return a message, similar to the following, if it is currently the active SC host:
Media Gateway Controller 2001-10-10 14:15:22M RTRV"Type:SC""Hardware platform:sun4u sparc SUNW,Ultra-5_10""Vendor:"Cisco Systems, Inc."""Location:Signaling Controller""Version:"7.4(12)"""Platform State:ACTIVE"The valid values for the Platform State field are ACTIVE, STANDBY, or OOS.
Step 2
rtrv-neThe system should return a message that indicates that it is in the standby platform state.
If the platform state of either SC host is not correct, check for alarms as described in the "Checking for Active Alarms" section, and take the actions necessary to correct the condition that caused the associated alarm(s).
If the platform state of both SC hosts is active, proceed to Step 3.
Step 3
Verifying the Status of all Signaling Channels
To verify the status of all of the signaling channels and linksets, enter the following command at the active SC host:
rtrv-sc:allThe system returns a response similar to the following, which shows the signaling links to and from the SC hosts and the associated media gateways.
Media Gateway Controller 2000-03-26 19:23:23M RTRV"iplink1:nassvc1,LID=0:IS" /* IP Link 1 for NAS 1 */"iplink2:nassvc2,LID=0:IS" /* IP Link 1 for NAS 2 */"iplink3:nassvc3,LID=0:IS" /* IP Link 1 for NAS 3 */"iplink4:nassvc1,LID=0:IS" /* IP Link 2 for NAS 1 */"iplink5:nassvc2,LID=0:IS" /* IP Link 2 for NAS 2 */"iplink6:nassvc3,LID=0:IS" /* IP Link 2 for NAS 3 */"c7iplink1:ls01,LID=0:IS" /* Link 1 in Linkset 1 */"c7iplink2:ls01,LID=1:IS" /* Link 2 in Linkset 1 */"c7iplink3:ls02,LID=0:IS" /* Link 1 in Linkset 2 */"c7iplink4:ls02,LID=1:IS" /* Link 2 in Linkset 2 */If any of the signaling channels are not in-service, check for alarms as described in the "Checking for Active Alarms" section, and take the actions necessary to correct the condition that caused the associated alarm(s).
Verifying the Status of all Traffic Channels
To verify the status of all of the traffic channels, enter the following command at the active SC host:
rtrv-tc:allThe system returns a response similar to the following:
Media Gateway Controller - MGC-01 2000-04-05 08:26:36M RTRV"dpc1:CIC=1,PST=IS,CALL=IDLE,BLK=NONE""dpc1:CIC=2,PST=IS,CALL=IDLE,BLK=NONE""dpc1:CIC=3,PST=IS,CALL=IDLE,BLK=NONE""dpc1:CIC=4,PST=IS,CALL=IDLE,BLK=NONE""dpc1:CIC=5,PST=IS,CALL=IDLE,BLK=NONE""dpc1:CIC=6,PST=IS,CALL=IDLE,BLK=NONE""dpc1:CIC=7,PST=IS,CALL=IDLE,BLK=NONE""dpc1:CIC=8,PST=IS,CALL=IDLE,BLK=NONE""dpc1:CIC=9,PST=IS,CALL=IDLE,BLK=NONE"If any of the traffic channels are not in-service, check for alarms as described in the "Checking for Active Alarms" section, and take the actions necessary to correct the condition that caused the associated alarm(s).
Verifying the Status of all Destinations
To verify the status of all of the destination point codes (DPCs) provisioned on your SC host, enter the following command at the active SC host:
rtrv-dest:allThe system returns a response similar to the following:
Media Gateway Controller - MGC-04 2000-04-05 08:05:36M RTRV"dpc1:PKG=SS7-ANSI,ASSOC=SWITCHED,PST=IS,SST=UND""dpc2:PKG=SS7-ANSI,ASSOC=SWITCHED,PST=IS,SST=UND""dpc3:PKG=SS7-ANSI,ASSOC=SWITCHED,PST=IS,SST=UND""dpc4:PKG=SS7-ANSI,ASSOC=SWITCHED,PST=IS,SST=UND""dpc5:PKG=SS7-ANSI,ASSOC=SWITCHED,PST=IS,SST=UND""dpc6:PKG=SS7-ANSI,ASSOC=SWITCHED,PST=IS,SST=UND"
Note
If any of the DPCs are not in-service, check for alarms as described in the "Checking for Active Alarms" section, and take the actions necessary to correct the condition that caused the associated alarm(s).
Checking for Active Alarms
To retrieve all active alarms, enter the following command at the active SC host:
rtrv-almsThe system returns a response that shows all active alarms, in a format similar to the following:
Media Gateway Controller 2000-02-26 11:41:01M RTRV"LPC-01: 2000-02-26 09:16:07.806,""LPC-01:ALM=\"SCMGC MTP3 COMM FAIL\",SEV=MJ""IOCM-01: 2000-02-26 09:17:00.690,""IOCM-01:ALM=\"Config Fail\",SEV=MN""MGC1alink2: 2000-02-26 09:17:47.224,ALM=\"SC FAIL\",SEV=MJ""MGC1alink3: 2000-02-26 09:17:47.225,ALM=\"SC FAIL\",SEV=MJ""MGC1alink4: 2000-02-26 09:17:47.226,ALM=\"SC FAIL\",SEV=MJ""MGC2alink1: 2000-02-26 09:17:47.227,ALM=\"SC FAIL\",SEV=MJ""MGC2alink2: 2000-02-26 09:17:47.227,ALM=\"SC FAIL\",SEV=MJ""MGC2alink4: 2000-02-26 09:17:47.229,ALM=\"SC FAIL\",SEV=MJ""dpc5: 2000-02-26 09:17:47.271,ALM=\"PC UNAVAIL\",SEV=MJ""ls3link1: 2000-02-26 09:16:28.174,""ls3link1:ALM=\"Config Fail\",SEV=MN""ls3link1: 2000-02-26 09:18:59.844,ALM=\"SC FAIL\",SEV=MJ"If any alarms are present, determine whether you need to take corrective action to resolve the alarm condition. The alarms that require corrective action are listed in the Alarm Troubleshooting Procedures section of the Cisco MGC Node Troubleshooting chapter in the Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide. Information on all alarms can be found in the Cisco Media Gateway Controller Software Release 7 Messages Reference Guide.
Verifying Proper Migration of Data
Verify that the contents of the XECfgParm.dat file and the active configuration file have successfully migrated by performing the following steps:
Step 1
If the parameter settings have not migrated properly, correct the value of the parameters and save the file, as described in the "Saving the XECfgParm.dat File" section. Otherwise, proceed to Step 2.
Note
Step 2
cd /opt/CMM/bin./start.sh toolThe MGC Toolbar window is displayed.
Step 3
Step 4
If the configuration identified in the Config-Lib viewer window as the current production version matches the name of your active configuration, the procedure is complete.
If the configuration identified in the Config-Lib viewer window as the current production version does not match the name of your active configuration, proceed to Step 5.
Step 5
If your active configuration is not listed in the Config-Lib viewer window, proceed to Step 6.
If your active configuration is listed in the Config-Lib viewer window, proceed to Step 8.
Step 6
Step 7
Step 8
etc/init.d/CiscoMGC stopStep 9
Step 10
etc/init.d/CiscoMGC startStep 11
Step 12
Migrating Inactive SC Host Configurations
When installing the SC software, only the active configuration files (located in /opt/CiscoMGC/etc) are migrated. You can use the migrate script to migrate old configurations to a new version. To use the migrate script:
Step 1
Step 2
migrate top-leveldirectory sourcedirectory destinationdirectoryTop-leveldirectory is the software directory. For Software Release 7.3(x), it is /opt/TransPath; for Software Release 7.4(x), it is /opt/CiscoMGC. Sourcedirectory is the relative path of the directory that you want to migrate. Destinationdirectory is the relative path of the directory into which the migrated files are copied. If the directory does not exist, the migrate script creates it. If the directory exists, you are prompted to overwrite it.
Backout Procedures
If the SC software upgrade did not work properly, perform the following steps:
Step 1
Step 2
Note
Step 3
a.
b.
c.
d.
e.
Restoring Your SC Host Data
Use the procedures in these sections to restore the SC data you previously backed up. If you backed up your data to tape, see the "Restoring Your Data from a Local Tape Drive" section. If you backed up your data to a remote machine using the IP network, see the "Restoring Your Data from a Remote Machine" section.
Restoring Your Data from a Local Tape Drive
This procedure restores everything on a tape installed in the local tape drive to the SC software base directory. This procedure assumes the operating system has just been installed and no SC software has been loaded. This procedure returns the etc and dialPlan subdirectories from a tape in the local tape drive to the /opt/TransPath directory. When the new SC software is later installed, it detects these files and uses them to migrate to the new configuration.
Step 1
# ./restore.shThe system returns a response similar to the following:
MGC restore utility-----------------------------Source currently set to Local tape (/dev/rmt/0h)Enter:<N> set source to remote NFS server<L> set source to Local tape (/dev/rmt/0h)<R> for Restore<Q> to quitSelect restore mode:Step 2
Are you sure you want to restore a backup.Current data in the MGC directory will be overwritten and lost.Answer(Y/N):Step 3
Answer(Y/N): yx ., 0 bytes, 0 tape blocksx ./var, 0 bytes, 0 tape blocksx ./var/log, 0 bytes, 0 tape blocksx ./var/log/platform.log, 117 bytes, 1 tape blocksx ./var/log/mml.log, 187 bytes, 1 tape blocks....#Step 4
Step 5
This completes restoring your SC host data from a local tape drive.
Restoring Your Data from a Remote Machine
This procedure restore files from the etc and dialPlan subdirectories to the /opt/CiscoMGC directory from a file on an NFS mountable directory on remote machine. The remote machine must be set up with an NFS mountable directory that is writable by machine being backed up. The NFS set up of the remote machine is beyond the scope of this procedure. When the new SC software is later installed, it detects these files and uses them to migrate to the new configuration.
Step 1
# ./restore.shThe system returns a response similar to the following:
MGC restore utility-----------------------------Source currently set to Local tape (/dev/rmt/0h)Enter:<N> set source to remote NFS server<L> set source to Local tape (/dev/rmt/0h)<R> for Restore<Q> to quitSelect restore mode:Step 2
Step 3
Enter server name: remote_hostnameWhere: remote_hostname—Name of the remote server where the backups are stored.
The system then prompts you to enter the name of the associated directory on the remote server.
Step 4
Enter remote directory : remote_directory_nameWhere: remote_directory_name—Name of the directory path on the remote server where the backups are stored.
The system returns a response similar to the following:
Enter server name: va-panthersEnter remote directory : /backupMGC restore utility-----------------------------Source currently set to remote NFS server (va-panthers:/backup)Enter:<N> set source to remote NFS server<L> set source to Local tape (/dev/rmt/0h)<R> for Restore<Q> to quitThe system then prompts you to select the restore mode.
Select restore mode:Step 5
mount -F nfs -o retry=3 va-panthers:/backup /mntAvailable files:va-blade20000317105201P.tarva-blade20000317105337.tarThe system then prompts you to enter the filename to be restored.
Enter filename to restore from:Step 6
Note
The system then asks you if you really want to restore a backup:
Are you sure you want to restore a backup.Current data in the MGC directory will be overwritten and lost.Answer(Y/N):Step 7
x etc, 0 bytes, 0 tape blocksx etc/Copyright, 545 bytes, 2 tape blocksx etc/CONFIG_LIB, 0 bytes, 0 tape blocksx etc/CONFIG_LIB/new, 0 bytes, 0 tape blocks..restore from va-panthers:/backup/va-blade20000317105337.tar complete#Step 8
Restoring Data to the Main Memory Database
Use this procedure to restore your dial plan data.
Step 1
For example, enter the following UNIX command to change to the /opt/CiscoMGC/local directory:
cd /opt/CiscoMGC/localStep 2
./restoreDb.sh filenameWhere filename is the name of the database backup file.
For example, to restore the contents of a file called dplan to the MMDB, you would enter the following command:
./restoreDb.sh dplanThe system returns a response similar to the following:
Restoring database contents for DSN=howdydb into dplanThe Restore process is being initiated for the datastore howdydbFiles for /opt/TimesTen32/datastore/howdydb are being restored up onto standard outputRestore Complete
Resetting the Configuration
Once the upgrade is complete on the second SC host, you must return to the first SC host you upgraded and reset its configuration to enable it to synchronize with the second SC host. To do this, perform the following steps:
Step 1
Step 2
Step 3
etc/init.d/CiscoMGC stopStep 4
etc/init.d/CiscoMGC start
Provisioning the Configuration
Note
After installing the new software on the SC host, you may need to add provisioning information to your configuration using MML or your GUI provisioning tool. If you added Cisco SLTs, you must provision these into the configuration. You should have the names of the components in your solution available. For more information, see the "Gathering Provisioning Data" section on page 1-4.
For an overview of provisioning and instructions to assist you, see Cisco Media Gateway Controller Software Release 7 Provisioning Guide. For instructions on provisioning a sample Cisco SS7 Interconnect for Access Servers Solution, see the appropriate provisioning guide for your solution.
Timesaver
Tip
Posted: Wed Oct 20 13:28:20 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
