-
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
-
Preface
-
Preparing for Sun Solaris Operating System and Cisco MGC Software Installation
-
Sun Solaris 8 Operating System Installation
-
Cisco MGC Software Release 9 Installation
-
Cisco PGW 2200 Security Enhancements
-
Configuring the Cisco MGC Software
-
Upgrading the Cisco MGC Software
-
Sun Solaris 2.6 Operating System Installation
-
Cisco MGC Software Release 9.1(5) Installation
-
Upgrading the Cisco MGC to Software Release 9.1(5)
-
Configuring the Local Area Network Switch
-
Migrating to Cisco MGC Software Release 9.3(1)
-
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
-
XECfgParm.dat File Parameters
-
HP OpenView Sample SNMP Configuration
-
Sample LAN Configurations
-
Sample Installation Scripts
-
Sample Uninstall Scripts
-
Index
-
Feedback
Table Of Contents
Configuring the Cisco MGC Software
Quick Guide to Configuring the Cisco MGC Software
Initial Cisco MGC Software Configuration
Parameters Required for Initial Setup
Using the Cisco MGC Environment Configuration Tool
Adding a User with Full MML Privileges
Adding a User with Minimal MML Privileges
Configuring SNMP Support Resources
Migrating the SNMP Configuration to a More Secure Environment (for MGC 9.3(2) or Later)
Before You Run the config-snmp Utility
Running the config-snmp Utility
Adding an SNMP Community Entry
Verifying the SNMP Configuration Migration
Setting up the SNMP Community for Software Releases Before Cisco MGC 9.3(2)
Setting the Destination for Traps
Configuring the Execution Environment
Changing XECfgParm.dat File Parameters
Changing XECfgParm.dat File Parameters in a Running Fault Tolerant System
Configuring Basic System Information
Configuring Call Detail Record File Output
Configuring the Clearing Location and Default Location Parameters
Initializing the Provisioning Object Manager
Configuring the trigger.dat File Attributes
Configuring the Global Title Translation Attribute
Configuring the Service Key Value Attribute
Configuring the Translation Type Attribute
Initializing the Call Screening Database
Initializing Database Replication
Verifying Database Replication
Troubleshooting the Main Memory Database Replication
Displaying the Main Memory Database Replication Status
Verifying Database Synchronization
Checking for Installation Errors
Configuring Disk Monitor During Initial Software Configuration
Configuring the Data Dumper to Support BAMS
Configuring the Cisco MGC Software
This chapter describes how to configure Release 9 of the Cisco Media Gateway Controller (MGC) software.
Quick Guide to Configuring the Cisco MGC Software
Note
The Cisco MGC software files and processes are located in the /opt/CiscoMGC directory.
The following table provides an overview of the configuration procedure. Go to the page indicated in the right most column for more detailed information.
Note
Before You Start
Before you start, verify the following:
•
•
Caution
Software Directory Structure
Table 5-2 shows the Cisco MGC software directory structure.
Caution
Initial Cisco MGC Software Configuration
When configuring the Cisco MGC software for the first time, use the MGC Environment Configuration Tool XECfg program to modify the XECfgParm.dat file. The MGC Environment Configuration Tool is a utility that is based on the Tool Command Language/Toolkit (Tcl/Tk). This utility uses an initialization wizard to facilitate the initial configuration of the XECfgParm.dat file.
The following required configuration parameters in the XECfgParm.dat file (see Table 5-3) are critical to bringing up the system. For more information on XECfgParm.dat files, refer to the "Cisco MGC 9.x XECfgParm.dat File Parameter Definitions" section on page A-2.
Note
When you exit the MGC Environment Configuration Tool, the slave file is sent via FTP to the appropriate system.
Caution
When the initial configuration on the active host is deployed, you must change the pom.dataSync parameter to true in the XECfgParm.dat file in the standby host. After setting this parameter to true, you can start the Cisco MGC on the standby host. As the Cisco MGC comes up, the data on the standby host is synchronized with the data on the active host. Initiate switchover to bring the active host to the standby state.
To accommodate failover conditions where the current active host can become the standby host, you must also set the pom.dataSync parameter to true on the current active host.
When Upgrading the Cisco MGC software: You must set the pom.dataSync parameter to false on the current active host to preserve configuration files.
Parameters Required for Initial Setup
The following table lists the parameter values that must be defined during the initial installation.
Note
Note
Using the Cisco MGC Environment Configuration Tool
You must configure the basic parameters required to bring the system to an operational mode. To use the MGC Environment Configuration Tool XECfg program:
Step 1
MGC_SetupA dialog box is displayed, warning that the MGC Environment Configuration Tool is for initial system set up only and asks if you wish to continue running the XECfg program.
Step 2
A screen similar to the following is displayed:
Figure 5-1 MGC Environment Configuration Tool
Optionally, you can run the MGC Environment Configuration Tool in detail mode by selecting the detail parameter at the command line.
a.
MGC_Setup -detailA dialog box is displayed, warning that the MGC Environment Configuration Tool is for initial system set up only, and asks if you wish to continue running XECfg.
b.
The MGC Environment Configuration Tool screen expands to provide detailed information from the XECfgParm.dat file (see Figure 5-2).
Figure 5-2 MGC Environment Configuration Tool—Detail Mode
Step 3
If you configure your system to be in fault-tolerant mode, you must do the following:
a.
b.
Step 4
Note
After committing the changes, the XECfg program backs up the current XECfgParm.dat file into XECfgParm.dat.xyz, where xyz can be between 0 and 19. The earliest version of the XECfgParm.dat file is version 0 and the latest is version 19.
If the operating mode is stand-alone, the XECfgParm.dat file is updated with new parameters. If the operating mode is fault-tolerant, the XECfgParm.dat file is updated and the XECfgParm.data.slave file is generated, based on the XECfgParm.dat file. There is no backup for the XECfgParm.dat.slave file.
Old parameters are commented out and new parameters are inserted. Use the comment line to keep file history. A history line is inserted every time a change is made against parameters. All required parameters are moved up to the top of the file for ease of use. However, the configuration tool does not depend on the location of the parameters.
Step 5
Configuring Groups and Users
You must set up groups and users for the Cisco MGC software on each host server. A user must be a member of the "mgcgrp" group to use certain Cisco MGC software functions, such as Man-Machine Language (MML). (MML is an interface that enables you to communicate with the Cisco MGC. Users with full MML privileges have monitor and control access; users with minimal MML privileges have only monitor access. For more information on MML, see the Cisco Media Gateway Controller Software Release 9 Provisioning Guide and the Cisco Media Gateway Controller Software Release 9 MML Command Reference.)
Verifying the mgcgrp Group
To verify the mgcgrp group, complete the following steps:
Step 1
Step 2
Step 3
mgcgrp::20000:Step 4
Step 5
mgcusr:x:20000:20000::/opt/CiscoMGC/local:/bin/cshIf the file does not contain the line, add it.
Step 6
This completes the procedures for verifying the mgcgrp group.
Adding a User with Full MML Privileges
To add a user with full MML privileges, complete the following steps.
Caution
Step 1
Step 2
# useradd -u UID -g mgcgrp -d /opt/CiscoMGC/local -s /bin/csh -m usernameUID is a user ID that is an integer from 0 through 2147483647 (excluding the numbers 0, 1, 2, 3, 4, 5, 9, 37, 71, 60001, 60002, and 65534, because they are used by the operating system).
Step 3
# mgcgrp::20000:username
Note
Step 4
passwd usernameStep 5
Step 6
Step 7
cd /opt/CiscoMGC/localStep 8
source .cshrcStep 9
mmlThis completes the procedures for adding a user with full MML privileges.
Adding a User with Minimal MML Privileges
To add a user with minimal MML privileges, follow the steps in the "Adding a User with Full MML Privileges" section, but do not add the user to the mgcgrp group.
This completes the group and user configuration. Continue to the "Configuring SNMP Support Resources" section. If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.
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 Cisco MGC. 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).
Note
The SNMP agent subsystem reports the following event categories to your SNMP Manager:
1.
2.
3.
4.
5.
In a fault tolerant configuration, the SNMP agent subsystem runs on both the active and standby machines.
Note
If your system is running an earlier version of Cisco MGC software 9.3(2), such as version 7.4(x), go to the "Setting up the SNMP Community for Software Releases Before Cisco MGC 9.3(2)" section for SNMP configuration procedures.
Note
Note
- config-snmp utility (for Cisco MGC software 9.3(2) or later)
- vi editor (for Cisco MGC software 9.2(2) or earlier)
Note
Note
Migrating the SNMP Configuration to a More Secure Environment (for MGC 9.3(2) or Later)
If your system is running Cisco MGC software version 9.3(2) or later, Cisco recommends that your SNMP configuration be migrated to a more secure environment by running the config-snmp utility. Use the config-snmp utility to perform the following:
•
•
Note
Note
Basic Tasks
The following is an overview of the major tasks you must perform to get the SNMP security provided by the config-snmp utility:
1.
2.
3.
4.
Before You Run the config-snmp Utility
Note
1. Log in as root and enter the following UNIX commands:
cd /opt/CiscoMGC/snmp
cp snmpd.cnf.tmpl snmpd.cnf
2. Enter the following UNIX commands to restart the snmp daemon:
ps -ef |grep snmpdm
The system will display the process ID for the snmp daemon. Restart the daemon using the
following command:
kill -9 snmpdm_pid
Where snmpdm_pid is the process ID for the snmp daemon.Note that the first instance of ReadAndNotifyToAll in the snmpCommunityEntry will be the only CommunityName used in the Trap.
For example, if your snmpd.cnf file has the following snmpCommunityEntry, you will find only the CommunityName of Iron1 in the Trap.
#Entry type: snmpCommunityEntry#Format: snmpCommunityIndex (text)# snmpCommunityName (text)# snmpCommunitySecurityName (text)# snmpCommunityContextEngineID (octetString)# snmpCommunityContextName (text)# snmpCommunityTransportTag (text)# snmpCommunityStorageType (nonVolatile, permanent, readOnly)snmpCommunityEntry Iron1 ron1 ReadAndNotifyToAll localSnmpID - - nonVolatilesnmpCommunityEntry Iron2 ron2 ReadWriteAll localSnmpID - - nonVolatilesnmpCommunityEntry Iron3 ron3 ReadAndNotifyToAll localSnmpID - - nonVolatilesnmpCommunityEntry admin WBnAGZ54 PGWInternalSignal localSnmpID - localAccess \nonVolatilesnmpCommunityEntry readonly public ReadAndNotifyToAll localSnmpID - - \nonVolatileRunning the config-snmp Utility
Perform the following steps to run the config-snmp utility:
Step 1
Step 2
Step 3
Note
Type one of the following commands and press Enter:
a.
ps -ef |grep snmpdmIf the snmpdm process is running, text similar to the following is displayed:
root 12098 27888 0 Jun 16 ?0:00 /opt/CiscoMGC/snmp/snmpdm -tcplocal -db.
ps -ef |grep critagtIf the critagt process is running, text similar to the following is displayed:
root 27888 1 0 May 19 ?0:15 /opt/CiscoMGC/snmp/critagt -dStep 4
config-snmpThe following screen is displayed:
Migrating snmpd.cnf into a more secure setting...=================== SNMPD Configuration Main Menu ===================1. View Configuration Entries2. Add an SNMP Community3. Delete an SNMP Community4. Add a Trap Destination5. Delete a Trap Destination6. Activate the New SettingsEnter a selection (1 through 6) or 'q' to quit:Step 5
The Entries Menu is displayed and you are prompted to make a selection:
=================== Entries Menu ===================1. sysDescr2. sysObjectID3. sysLocation4. sysContact5. sysName6. snmpEnableAuthenTraps7. MAX_THREADS8. MAX_PDU_TIME9. MAX_OUTPUT_WAITING10. MAX_SUBAGENTS11. subagent12. snmpCommunityEntry13. communityEntry14. snmpEngineBoots15. usmUserEntry16. vacmAccessEntry17. vacmSecurityToGroupEntry18. vacmViewTreeFamilyEntry19. snmpNotifyEntry20. snmpTargetAddrEntry21. snmpTargetParamsEntry22. snmpNotifyFilterProfileEntry23. snmpNotifyFilterEntry24. httpUserNameEntryEnter a selection (1 through 24) or 'q' to quit to Main Menu:Step 6
Adding an SNMP Community Entry
Continuing from Step 6, above (of the section Running the config-snmp Utility):
Step 1
Text similar to the following and the SNMPD Configuration Main Menu are displayed.
#Entry type: snmpCommunityEntry#Format: snmpCommunityIndex (text)# snmpCommunityName (text)# snmpCommunitySecurityName (text)# snmpCommunityContextEngineID (octetString)# snmpCommunityContextName (text)# snmpCommunityTransportTag (text)# snmpCommunityStorageType (nonVolatile, permanent, readOnly)snmpCommunityEntry IT555 T555 ReadWriteAll localSnmpID - - nonVolatilesnmpCommunityEntry Ijammmy jammmy ReadAndNotifyToAll localSnmpID - - nonVolatilesnmpCommunityEntry admin za8RQzBg PGWInternalSignal localSnmpID - localAccess nonVolatile=================== SNMPD Configuration Main Menu ===================1. View Configuration Entries2. Add an SNMP Community3. Delete an SNMP Community4. Add a Trap Destination5. Delete a Trap Destination6. Activate the New SettingsEnter a selection (1 through 6) or 'q' to quit:Step 2
The Add CommunityString Menu is displayed and you are asked if you would like to proceed with adding a community string:
=================== Add CommunityString Menu ===================SnmpCommunityName CommunitySecurityNameT555 ReadWriteAlljammmy ReadAndNotifyToAll-- Where:CommunitySecurityName SecurityModel Read Write NotificationReadWriteAll snmpv1 AllMibObjects AllMibObjects -ReadWriteAll snmpv2c AllMibObjects AllMibObjects -ReadAndNotifyToAll snmpv1 AllMibObjects - AllMibObjectsReadAndNotifyToAll snmpv2c AllMibObjects - AllMibObjectsWould you like to proceed with the Add [n]/[y]?Step 3
The following text is displayed, prompting you to enter an snmpCommunityName.
Enter snmpCommunityName:
Note
Step 4
comname1Text similar to the following is displayed:
Enter CommunitySecurityName (ReadAndNotifyToAll or ReadWriteAll):Step 5
ReadAndNotifyToAll
Note
Text similar to the following text is displayed:
snmpCommunityName: comname1 is about to be added. Are you sure that you want to add this snmpCommunity Name [y]/[n]?Step 6
Text similar to the following is displayed:
Adding snmpCommunity:snmpCommunityEntry Icomname1 comname1 ReadAndNotifyToAll localSnmpID - - nonVolatile=================== SNMPD Configuration Main Menu ===================1. View Configuration Entries2. Add an SNMP Community3. Delete an SNMP Community4. Add a Trap Destination5. Delete a Trap Destination6. Activate the New SettingsEnter a selection (1 through 6) or 'q' to quit:Step 7
•
•
Note
The procedure for adding an SNMP Community Entry is now complete.
From the SNMPD Configuration Main Menu, choose option 6 (Activate the New Settings) to commit the changes, or select other options (1 through 5) to add or delete a community name or trap.
Deleting an SNMP COMMUNITY
From the SNMPD Configuration Main Menu:
Step 1
Note
=================== Delete CommunityString Menu ===================SnmpCommunityName CommunitySecurityNamecomname1 ReadAndNotifyToAllT555 ReadWriteAlljammmy ReadAndNotifyToAll-- Where:CommunitySecurityName SecurityModel Read Write NotificationReadWriteAll snmpv1 AllMibObjects AllMibObjects -ReadWriteAll snmpv2c AllMibObjects AllMibObjects -ReadAndNotifyToAll snmpv1 AllMibObjects - AllMibObjectsReadAndNotifyToAll snmpv2c AllMibObjects - AllMibObjectsWould you like to proceed with the Delete [n]/[y]?Step 2
Text similar to the following is displayed:
Enter snmpCommunityName:Step 3
T555Text similar to the following is displayed:
snmpCommunityName: T555 is about to be deleted. Are you sure that you want to delete this snmpCommunity Name [y]/[n]?Step 4
Text similar to the following is displayed and you are returned to the SNMPD Configuration Main Menu:
Deleting snmpCommunity= T555=================== SNMPD Configuration Main Menu ===================1. View Configuration Entries2. Add an SNMP Community3. Delete an SNMP Community4. Add a Trap Destination5. Delete a Trap Destination6. Activate the New SettingsEnter a selection (1 through 6) or 'q' to quit:Step 5
•
•
The procedure for deleting an SNMP Community Entry is now complete. Proceed to the selection you entered in the SNMPD Configuration Main Menu.
Adding a Trap Destination
From the SNMPD Configuration Main Menu:
Step 1
The Add Trap Menu is displayed:
Note
=================== Add Trap Menu ===================1. TargetAddress: 6.6.6.6:0 , TargetAddrParams: v1ExampleParams , IP Mask: 255.255.255.255:0Would you like to proceed with the Add [n]/[y]?Step 2
Text similar to the following is displayed:
Enter IP Address (x.x.x.x):Step 3
7.7.7.7
Text similar to the following is displayed:
Enter Trap Type (v1 or v2c):Step 4
v1Text similar to the following is displayed:
'snmpTargetAddrEntry 483 snmpUDPDomain 6.6.6.6:0 100 3 TrapSink v1ExampleParams nonVolatile 255.255.255.255:0 2048' is about to be added. Are you sure that you want to add this Trap Entry [n]/[y]?Step 5
Text confirming the addition of the Trap Destination is displayed, followed by the SNMPD Configuration Main Menu:
Adding Trap: snmpTargetAddrEntry 483 snmpUDPDomain 7.7.7.7:0 100 3 TrapSink v1ExampleParams nonVolatile 255.255.255.255:0 2048=================== SNMPD Configuration Main Menu ===================1. View Configuration Entries2. Add an SNMP Community3. Delete an SNMP Community4. Add a Trap Destination5. Delete a Trap Destination6. Activate the New SettingsEnter a selection (1 through 6) or 'q' to quit:ENTER YOUR SELECTION.Step 6
•
•
The procedure for adding a Trap Destination is now complete. Proceed to the selection you entered in the SNMPD Configuration Main Menu.
Deleting a Trap Destination
From the SNMPD Configuration Main Menu:
Step 1
Text similar to the following is displayed:
=================== Delete Trap Menu ===================1. TargetAddress: 7.7.7.7:0 , TargetAddrParams: v1ExampleParams ,IP Mask: 255.255.255.255:02. TargetAddress: 6.6.6.6:0 , TargetAddrParams: v1ExampleParams ,IP Mask: 255.255.255.255:0Would you like to proceed with the Delete [n]/[y]?Step 2
Text similar to the following is displayed:
Enter a selection (1 through 2):
Note
Step 3
Text similar to the following is displayed:
Trap is about to be deleted. Are you sure that you want to delete this Trap Entry [n]/[y]?Step 4
Text confirming the deleted Trap Entry is displayed and you are returned to the SNMPD Configuration Main Menu. Note that 483 (below) is an internal Trap snmpTargetAddrName.
Deleting Trap snmpTargetAddrName = 483=================== SNMPD Configuration Main Menu ===================1. View Configuration Entries2. Add an SNMP Community3. Delete an SNMP Community4. Add a Trap Destination5. Delete a Trap Destination6. Activate the New SettingsEnter a selection (1 through 6) or 'q' to quit:Step 5
•
•
The procedures for deleting a Trap Destination is now complete. Proceed to the selection you entered in the SNMPD Configuration Main Menu.
Activating the New Settings
From the SNMPD Configuration Main Menu:
Step 1
6Text similar to the following is displayed:
Backing up the current snmpd.cnf to snmpd.cnf.backup.snmpd.cnf.backup already exists. Do you want to overwrite the file [y]/[n]?
Note
Step 2
yAre you sure you would like to Activate the New Settings [y]/[n]?
Note
If you choose n, your SNMPD.dat file will not be updated and you will be exited from the utility.Step 3
Text similar to the following is displayed:
snmpd.cnf file has been updated.The procedure for activating the new settings is now complete and you are exited from the config-snmp utility. Proceed to the following section, "Verifying the SNMP Configuration Migration".
Verifying the SNMP Configuration Migration
Perform the following steps to verify that your changes were applied by running the config-snmp utility:
Step 1
config-snmpText similar to the following is displayed:
Migrating snmpd.cnf into a more secure setting...When the SNMPD Configuration Main Menu is displayed, you are prompted to make a selection:
=================== SNMPD Configuration Main Menu ===================1. View Configuration Entries2. Add an SNMP Community3. Delete an SNMP Community4. Add a Trap Destination5. Delete a Trap Destination6. Activate the New SettingsEnter a selection (1 through 6) or 'q' to quit: 1Step 2
The Entries Menu is displayed and you are prompted to make a selection:
=================== Entries Menu ===================1. sysDescr2. sysObjectID3. sysLocation4. sysContact5. sysName6. snmpEnableAuthenTraps7. MAX_THREADS8. MAX_PDU_TIME9. MAX_OUTPUT_WAITING10. MAX_SUBAGENTS11. subagent12. snmpCommunityEntry13. communityEntry14. snmpEngineBoots15. usmUserEntry16. vacmAccessEntry17. vacmSecurityToGroupEntry18. vacmViewTreeFamilyEntry19. snmpNotifyEntry20. snmpTargetAddrEntry21. snmpTargetParamsEntry22. snmpNotifyFilterProfileEntry23. snmpNotifyFilterEntry24. httpUserNameEntryEnter a selection (1 through 24) or 'q' to quit to Main Menu:a.
Note
#Entry type: snmpCommunityEntry#Format: snmpCommunityIndex (text)# snmpCommunityName (text)# snmpCommunitySecurityName (text)# snmpCommunityContextEngineID (octetString)# snmpCommunityContextName (text)# snmpCommunityTransportTag (text)# snmpCommunityStorageType (nonVolatile, permanent, readOnly)snmpCommunityEntry Icomname1 comname1 ReadWriteAll localSnmpID - - nonVolatilesnmpCommunityEntry Ijammmy jammmy ReadAndNotifyToAll localSnmpID - - nonVolatilesnmpCommunityEntry admin VD6FZbov PGWInternalSignal localSnmpID - localAccess nonVolatileb.
Note
#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 531 snmpUDPDomain 6.6.6.6:0 100 3 TrapSink v1ExampleParams nonVolatile 255.255.255.255:0 2048snmpTargetAddrEntry local snmpUDPDomain 127.0.0.1:0 100 3 localAccess - nonVolatile 255.255.255.255:0 2048The SNMP support resource configuration is now complete. Continue to the "Configuring the Execution Environment" section to configure the execution environment. If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.
Setting up the SNMP Community for Software Releases Before Cisco MGC 9.3(2)
If your software release is earlier than Cisco MGC software release 9.3(2), you must edit your files using the vi editor. You can either use the existing SNMP community (public) or create your own.
To create a new SNMP community, log in to the Cisco MGC as root and use the vi editor to modify the /opt/CiscoMGC/snmp/snmpd.cnf file. This file has three default access security levels:
•
•
•
Adding a New Community
To add a new community called myCommunity (for example, a community with an access level of User), do the following procedures:
Step 1
snmpCommunityEntry myUser myCommunity private localSnmpID - - nonvolatileStep 2
Setting the Destination for Traps
Do the following procedures to add a trap destination, which is a machine named manager-host with the IP address of 10.10.10.5. Traps will be sent to this destination by the MGC SNMP agent.
Step 1
snmpNotifyEntry 50 myTrap trap nonvolatile
Note
Step 2
snmpTargetAddrEntry 51 snmpUDPDomain 10.10.10.5:0 100 3 myTrap \v2cExampleParams nonVolatile 255.255.255.255:0 2048There must be nothing (not even a space or any other invisible characters) after the \ on the first line. You can change the following entries in the above line:
•
•
•
•
•
•
Configuring SNMP Entries
To configure the SNMP resources, perform the following steps:
Step 1
Step 2
•
•
•
•
Step 3
For example, you can use the xnmnloadmib -load command from HP OpenView.
Tip
Note
Example 5-1 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.Step 4
Note
Example 5-2 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 5
–
–
–
Step 6
This completes the SNMP support resource configuration. Continue to the following section, "Configuring the Execution Environment", to configure the execution environment. If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.
Configuring the Execution Environment
This section provides instructions for configuring the Cisco MGC execution environment and contains the following topics:
•
•
•
•
•
The configuration data file, or XECfgParm.dat file (located in /opt/CiscoMGC/etc/XECfgParm.dat), lists all the components in the Cisco MGC and defines how it operates. You must edit the execution environment parameters in the XECfgParm.dat file to initialize and configure the Cisco MGC software application. For more detailed information on XECfgParm.dat parameters, refer to Appendix A, "XECfgParm.dat File Parameters" and the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
For samples of configured XECfgParm.dat files, see the "Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files" section on page D-14.
Caution
Do not modify the processes.dat file. This XECfgParm.dat file should remain unmodified, as delivered with the MGC software. If this file is modified, procM may core dump when you start the MGC software.
Changing XECfgParm.dat File Parameters
For a complete list of the parameters found in the XECfgParm.dat file and how they are used by the Cisco MGC, see Appendix A, "XECfgParm.dat File Parameters."
If you have a fault tolerant system with two Cisco MGC hosts, the XECfgParm.dat files are different for each host. For examples of these XECfgParm.dat files, see the "Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files" section on page D-14 and the "Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files" section on page D-21.
To change the XECfgParm.dat file parameters, perform the following steps:
Step 1
Step 2
/etc/init.d/CiscoMGC stopWait until the system returns the following response:
Signalling procM to shut down...shutdown completeStep 3
Step 4
Step 5
Step 6
/etc/init.d/CiscoMGC start
Note
Continue to "Changing XECfgParm.dat File Parameters in a Running Fault Tolerant System" to change parameters without call interruption. Continue to the "Configuring SCP Queries" section to configure Service Control Point (SCP) queries using transaction capabilities application part (TCAP). If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.
Changing XECfgParm.dat File Parameters in a Running Fault Tolerant System
To change parameters in a running fault tolerant system without call interruption, perform the following steps:
Step 1
Step 2
/etc/init.d/CiscoMGC stopStep 3
/etc/init.d/CiscoMGC startStep 4
/etc/init.d/CiscoMGC stopStopping the software on Host X causes switchover to the standby, Host Y. Host Y becomes active and takes over call processing.
Tip
Step 5
/etc/init.d/CiscoMGC startStep 6
SW-OVER::CONFIRM
Tip
Configuring Basic System Information
Note
To configure basic system information required for your system to function, modify the following parameters in the first section of the XECfgParm.dat file:
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 they are on the same subnet. The following example illustrates a valid combination:
*.ipAddrLocalA = 172.22.119.108*.ipAddrLocalB = 172.22.120.54In this example, the subnet mask is 255.255.255.0 (or 255.255.255.128).
If 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
For the engine to run correctly, you must modify the following parameters in the Engine section of the XECfgParm.dat file:
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:
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 Switchover
To configure switchover, modify the following parameters in the foverd section of the XECfgParm.dat file.
:
Note
Initializing the Provisioning Object Manager
To configure the Provisioning Object Manager (POM), modify the following parameters in the POM section of the XECfgParm.dat file:
Configuring SCP Queries
The 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 use to enable SCP database queries. If your site or network requires changes, you can enable SCP queries by manually editing the parameters in the trigger.dat file. The trigger.dat file (located in /opt/CiscoMGC/etc) contains the message-sending table that contains translation values.
This section contains the following topics:
•
Warning
Note
IN/1 Toll Free Service support : GR-1428
AIN 0.1 Toll Free Service support : GR-2902
Before You Start
If you are changing an ANSI query and you need a different Translation Type, you need to know the Translationtype value from the Global Title Translation tables on the Signal Transfer Point (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 start
Note
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Configuring 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 start
Note
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Table 5-5
$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 Documentation, Obtaining Support, and Security Guidelines" section on page xvii.
Initializing the Call Screening Database
This section contains the following topics:
•
Caution
During installation, the installation script (install.sh) installs and initializes the Main Memory Database (MMDB) that the Cisco MGC can use for the following:
•
•
•
•
•
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). For more details, see the Cisco MGC Software Release 9 Dial Plan Guide.
The call screening database is stored in the /opt/TimesTen/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, below.
Caution
.odbc.ini File Information
The .odbc.ini file specifies the location of the database storage. Unless you installed the software to other than the default directory, the .odbc.ini file is located in the /opt/CiscoMGC/local directory. The following is an example of an .odbc.ini file:
[ODBC Data Sources]howdydb=TimesTen 4.1 Driver[howdydb]Driver=/opt/TimesTen4.1/32/lib/libtten.soDataStore= /opt/TimesTen4.1/datastore/howdydbDurableCommits=0ExclAccess=0ThreadSafe=1WaitForConnect=0Size=256[ODBC]Trace=0TraceFile=Installdir=/opt/TimesTen4.1/32Setting Up Replication
If you have two Cisco MGC hosts in a fault tolerant system, you must set up database replication between the two hosts. During replication, any updates applied to the database on one host are replicated on the other. Data is transferred real time and does not require committing or deploying a configuration.
Replication copies data changes to either database after the initial setup. If you have data in one database and want to retain it, go to the host that has the data that you want to retain (usually this is the active host), then follow the procedures below, "Initializing Database Replication" section.
Note
Network Requirements
In most replication schemes, you need to identify the name of the host machine on which your data store resides. The operating system translates this host name to an IP address. This section describes how to configure your host names to ensure they use the correct IP addresses.
Identifying data store hosts (UNIX and VxWorks)
If your Unix or VxWorks host has a single IP address and hostname, you can use the host name returned by the hostname command on UNIX or the hostname() call on VxWorks. If a host contains multiple network interfaces (with different IP addresses), TimesTen replication tries to connect to the IP address in the same order as returned by the gethostbyname() call on UNIX or the hostGetByName() call on VxWorks. It will try to connect using the first address; if a connection cannot be established, it tries the remaining addresses in order until a connection is established. TimesTen replication uses this same sequence each time it establishes a new connection to a host. If a connection to a host fails on one IP address, TimesTen replication attempts to re-connect (or fall back) to another IP address for the host in the same manner described above.
There are two basic ways you can configure a host to use multiple IP addresses on UNIX platforms: DNS or /etc/hosts files. On VxWorks platforms you use the hostAdd() call. For example, the following entry in the /etc/hosts file on a UNIX platform describes a server named Machine1 with two Ethernet IP addresses:
10.10.98.102 Machine1192.168.1.102 Machine1To specify the same configuration for DNS, your entry in the domain zone file would look like:
Machine1 IN A 10.10.98.102IN A 192.168.1.102In either case, you only need to specify Machine1 as the hostname in your replication scheme and replication will use the first available IP address when establishing a connection. In an environment in which multiple IP addresses are used, you can also assign multiple host names to a single IP address in order to restrict a replication connection to a specific IP address. For example, you might have an entry in your /etc/hosts file that looks like:
10.10.98.102 Machine1192.168.1.102 Machine1 RepMachine1Or a DNS zone file that looks like:
Machine1 IN A 10.10.98.102IN A 192.168.1.102RepMachine1 IN A 192.168.1.102Should you want to restrict replication connections to IP address 192.169.1.102 for this host, you can specify RepMachine1 as the hostname in your replication scheme. (Another option is to simply specify the IP address as the hostname in the CREATE REPLICATION statement used to configure your replication scheme.)
The following are example hosts files from an active PGW host and an associated peer PGW host:
Active PGW Host /etc/hosts
27.0.0.1 localhost192.168.11.1 UK-A-Netra1125-1 loghost192.168.12.1 UK-A-Netra1125-1.hme1192.168.11.2 UK-A-Netra1125-2192.168.12.2 UK-A-Netra1125-2.hme1 UK-A-Netra1125-2 <----- Peer PGW hostnamePeer PGW Host /etc/hosts
127.0.0.1 localhost192.168.11.2 UK-A-Netra1125-2 loghost192.168.12.2 UK-A-Netra1125-2.hme1192.168.11.1 UK-A-Netra1125-1 192.168.12.1 UK-A-Netra1125-1.hme1 UK-A-Netra1125-1 <----- Peer PGW hostnameInitializing Database Replication
To set up the initial replication, perform the following steps:
Step 1
setup_replication.sh standbyhost activeWhere standbyhost is the name (not IP address) of your standby host. In the example below, the active host is hostx and the standby host is hosty.
Caution
Example 5-3 Initializing Database Replication on the Active Host
hostx% setup_replication.sh hosty activeSetting 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
/etc/init.d/CiscoMGC stopStep 3
Step 4
setup_replication.sh activehost standbywhere activehost is the name (not IP address) of your active host. In the example below, the active host is hostx and the standby host is hosty.
Caution
Example 5-4 Initializing Database Replication on the Standby Host
Configuring replication for DSN=howdydbRestoring file /opt/TimesTen4.1/datastore/howdydb.ds0 from backupRestoring file /opt/TimesTen4.1/datastore/howdydb.log0 from backupRAM Residence Policy :inUseManually Loaded In Ram :FalseReplication Agent Policy :manualReplication Manually Started :TrueOracle Agent Policy :manualOracle Agent Manually Started :FalseReplication setup completed.Step 5
/etc/init.d/CiscoMGC startProceed to "Verifying Database Replication".
Verifying Database Replication
To verify that replication is working, perform the following steps:
Step 1
Step 2
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 3
Step 4
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. */;
Troubleshooting the Main Memory Database Replication
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 start
Displaying the Main Memory Database Replication Status
The script replication_status.sh displays the status of the MMDB replication, if it is configured.
Run the script by typing the following command:
replication_status.shThe output shows the following replication status:
Peer name Host name Port State Proto---------------- ------------------------ ------ ------- -----HOWDYDB VA-DEALE Auto Start 5Last Msg Sent Last Msg Recv Latency TPS RecordsPS Logs------------- ------------- ------- ------- --------- ----- - -1.00 -1 -1 1
Note
Verifying Database Synchronization
The script db_count.sh provides the number of records configured in each of the database tables. This is useful for checking whether two machines have the same database data configured in them.
Run the script by typing the following command:
db_count.shThe output shows the rows counted in each database table:
CISCO.A_CHARGE_ORIGIN < 0 >CISCO.A_NUMBERDIALPLANSELECTION < 0 >CISCO.BLACKLIST_A < 0 >CISCO.BLACKLIST_B < 0 >CISCO.NUMBERTERM < 0 >CISCO.PORTEDNUMBERS < 0 >CISCO.WHITELIST_A < 0 >CISCO.WHITELIST_B < 3 >Synchronizing Databases
If you have data in the databases in the active and standby hosts, but both databases are out of synch or do not match, re-synchronize both databases by following the steps listed below. Otherwise, contact Cisco TAC for assistance in merging the databases.
Assuming the active host is the "better" database, do the following on the standby host:
Step 1
Step 2
/etc/init.d/CiscoMGC stopStep 3
/etc/init.d/ttreplic stopStep 4
setup_replication <active host> standbyStep 5
/etc/init.d/CiscoMGC start
Checking for Installation Errors
If 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
Reinstalling CSCOga002
If necessary, remove and reinstall the CSCOga002 package, as follows:
Step 1
# pkgrm CSCOga002Step 2
# pkgadd -d CSCOga002.pkgThis completes the Cisco MGC software installation. If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii. If you do not need to install or remove patches, proceed to configure your Cisco SLTs.
Configuring Cisco SLTs
Note
Configuring Disk Monitor During Initial Software Configuration
The setting of the disk monitor parameters in the XECfgParm.dat file typically occurs while you are performing the initial configuration procedures for your Cisco MGC software. To configure the disk monitor settings in the XECfgParm.dat file during initial software configuration, perform the following steps:
Step 1
Step 2
Step 3
Note
Step 4
Step 5
Step 6
Step 7
Step 8
Note
Note
Step 9
This completes the procedures for configuring disk space monitoring. If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.
Configuring the Data Dumper
The data dumper is a Cisco MGC software function that controls the destinations for active and archived log files for CDRs, measurements, and alarms, and controls when the active files are archived. The data dumper runs automatically and works correctly with a default configuration. However, you can customize the dumper settings by editing the dmprSink.dat file.
The following is an example of the contents of the dmprSink.dat file:
"callDetail" bin "cdr" "../var/log" "../var/spool" 1000 0 15"measReport" csv "meas" "../var/log" "../var/spool" 500 0 15"almState" csv "alm" "../var/log" "../var/spool" 500 0 15Table 5-6 lists the fields that can be modified depending on your needs.
To configure the dmprSink.dat file fields, use the following procedure:
Step 1
Step 2
cd /opt/CiscoMGC/etcStep 3
Note
Step 4
Step 5
cd /opt/CiscoMGC/etc/CONFIG_LIB/newStep 6
Step 7
Step 8
Step 9
Step 10
cd /opt/CiscoMGC/etc/active_link/Step 11
Step 12
This completes the procedures for configuring the data dumper. If your system uses BAMS, continue to the "Configuring the Data Dumper to Support BAMS" section. If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.
Configuring the Data Dumper to Support BAMS
If your system will use BAMS to retrieve CDRs from the Cisco MGC, perform the following procedure to configure the data dumper to support BAMS:
Step 1
Step 2
cd /opt/CiscoMGC/etcStep 3
Step 4
Step 5
cd /opt/CiscoMGC/etc/CONFIG_LIB/newStep 6
Step 7
Step 8
Step 9
Step 10
cd /opt/CiscoMGC/etc/active_link/Step 11
Step 12
This completes the procedures for configuring the data dumper to support BAMS. If you have questions or need assistance, see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xvii.
