|
|
This chapter contains the configuration steps you must perform before you operate the telephony controller software.
You need a basic knowledge of the UNIX operating system to enter commands for the telephony controller. See "UNIX System Operation" for a brief overview and pointer to additional UNIX resources.
This chapter includes the following sections:
Before you begin configuring the telephony controller, verify that the following steps have been performed:
Step 1 The host server hardware has been set up and configured in accordance with the manufacturer's instructions. The terminal type should be set to VT100.
Step 2 The disk has been partitioned correctly as shown in either Table 2-1 or Table 2-2.
| Slice Number | Mount Point | Size (MB) |
|---|---|---|
0 | / | 512 |
1 | Swap | 512 |
2 | backup (whole disk) | 4092 |
3 | /var | 512 |
4 | /opt | 2356 |
5 | /export/home | 200 |
| Slice Number | Mount Point | Size (MB) |
|---|---|---|
0 | / | 512 |
1 | Swap | 512 |
2 | backup (whole disk) | 8633 |
3 | /var | 1024 |
4 | /opt | 5561 |
5 | /export/home | 512 |
To verify, log in to the telephony controller and enter the following command:
df -k
Or enter the format command, choose disk, enter partition, and choose p to print to the screen.
If the disk is not partitioned correctly, partition the disk according to the guidelines above.
Step 3 Verify that the Sun serial port expansion module and asynchronous drivers and utilities have been installed. To verify, log in to the telephony controller and enter the following command:
pkginfo | grep SUNWsaip
The system returns a message similar to the following example that shows the drivers have been installed:
va-tan% pkginfo | grep SUNWsaip system SUNWsaip Serial Asynchronous Interface Driver (PCI) application SUNWsaipu Serial Asynchronous Interface Utilities (PCI)
Step 4 Verify that the hardware devices have been installed. Change to the /dev/term directory and enter the ls command. Verify that devices a000 to a007 are present, as shown in this example:
va-tan% cd /dev/term va-tan% ls a a000 a001 a002 a003 a004 a005 a006 a007 b
Step 5 Change to the /dev/cua directory and enter the ls command. Verify that devices a000 to a007 are present as shown here:
va-tan% cd /dev/cua va-tan% ls
Step 6 If these are not installed or have been installed incorrectly, reload the driver using the CD-ROM and documentation provided with the serial port expansion module.
Step 7 Verify that IP has been configured correctly:
(a) Change to the /etc directory and view the hostname.hme0 file. This file should contain the name of your host server. If not, edit the file to reflect the correct host name.
(b) View the hosts file. This file should contain the host name and IP address of the server machine, and, if you have a failover configuration, the unqualified host name and IP address of the standby server.
(c) View the defaultrouter file to ensure that the file contains the IP address of the default router.
(d) View the nsswitch.conf file. The file should contain the following line:
hosts: files dns
(e) View the resolv.conf file. The file should contain the following lines:
domain domain name (for example, test.cisco.com) nameserver IP address of first DNS nameserver IP address of second DNS (if applicable) nameserver IP address of third DNS (if applicable)
(f) Test the IP configuration and network connectivity by using the ping command to contact the default router, DNS systems, network access servers, the NT workstation, and, if applicable, the standby server. If there are problems, verify the configuration using the ifconfig -a and netstat -r commands.
Step 8 Verify that the alarm relay unit (ARU) is set up correctly. To set up your failover system, you need the following three hardware components:
To configure the telephony controller, you must configure several different software components. Table 2-3 displays the configuration steps and the location of the steps in this chapter.
| Step | Page |
|---|---|
Set up the transpath group and users | |
Configure NTP (if applicable) | |
Configure SNMP (if applicable) | |
Configure your site using the configuration tool | |
Retrieve the files generated by the configuration tool and install on the host server | |
Set up your dial plan for call routing | |
Set up the execution environment configuration parameters | |
Set up the Network File System (NFS) for failover configurations |
You must set up the transpath group and users for the telephony controller software on each host server. A user must be a member of the transpath group to perform certain telephony controller software commands, such as using man machine language (MML). MML is an interface in the telephony controller software that you use to communicate with the telephony controller. Users with full MML privileges will have monitor and control access; users with minimal MML privileges will have monitor access. See "MML Commands" for more information.
To check the transpath group:
Step 1 Log into the telephony controller as Root.
Step 2 Change to the /etc directory.
Step 3 View the group file to verify the entry for the transpath group. The file should contain the following line:
transpath::20000:
Step 4 Edit the group file to add a user called "transpath" to the transpath group. The line should then appear as follows:
transpath::20000:transpath
Step 5 View the passwd file to verify the entry for the transpath user. The file should contain the following line:
transpath:x:20000:20000::/opt/TransPath/local:/bin/csh
To add a user with full MML privileges, perform the following steps:
Step 1 Log in to the telephony controller as Root.
Step 2 Enter:
useradd -u UID -g transpath -d /export/home/username -s /bin/csh -m username
UID = user ID that is an integer between 0 and 2147483647 (excluding 0,1,2,3,4,5,9,37,71,60001,60002 and 65534 because they are used by the operating system).
Step 3 Create a .cshrc file for each user by copying the local.cshrc file to the user's home directory. Enter:
cp /export/home/username/local.cshrc /export/home/username/.cshrc
Step 4 Change to the /export/home/username directory and add the following lines to the user's .cshrc file:
if (-e /opt/TransPath/local/.cshrc) then cd /opt/TransPath/local source ./.cshrc endif
Step 5 Make sure the user "owns" the .cshrc file by entering:
chown username:groupname .cshrc
Step 6 Change to the /etc directory and edit the group file to add the new username to the transpath group:
transpath::20000:username
Step 7 Enter passwd username
Step 8 Enter password twice when prompted.
Step 1 Log in to the telephony controller.
Step 2 Enter cd /opt/TransPath/local
Step 3 Enter source .cshrc
Step 4 Enter mml
To set up a user with minimal MML privileges, follow the steps in the "Adding a User with Full MML Privileges" but do not add the user to the transpath group.
Step 1 Log in to the telephony controller.
Step 2 Enter cd /opt/TransPath/local
Step 3 Enter source .cshrc
Step 4 Enter mml
Network Time Protocol (NTP) software is usually installed on your host server. This software allows you to synchronize the time on the telephony controller with that of another server or reference time source to provide greater accuracy and reliability.
To use NTP, you must have one or more NTP servers configured on a network that is accessible to the telephony controller. You must configure your software to connect with these servers.
To configure NTP:
Step 1 Log into the telephony controller as Root.
Step 2 Change to the /opt/ntp/etc directory.
Step 3 Edit the ntp.conf file. Delete the broadcastclient line and add lines for each NTP server with which you want to synchronize. Each server is denoted by a line in the following format:
server servername
For other configurations, see http://www.eecis/udel.edu/~mills/ntp/html/index.htm or open the htdocs.tar file located in /opt/ntp and view the index.html file.
The telephony controller software includes a Simple Network Management Protocol (SNMP) agent subsystem that provides an alarm management interface on the telephony controller. It uses SNMP to report events, or traps (such as alarms), to your SNMP Manager and to provide access to the telephony controller Management Information Base (MIB).
The SNMP agent subsystem reports the following event categories to your SNMP Manager:
1. Communications
2. Quality of Service
3. Processing
4. Equipment
5. Environment
In a failover configuration, the SNMP agent subsystem runs on both the active and standby machines.
To configure SNMP:
Step 1 Log in to the telephony controller and change to the /etc directory.
Verify that the services file lists the following default SNMP ports:
snmp 161/udp snmp-trap 162/udp
Step 2 Transfer the MIB located on the telephony controller using FTP to the computer where the SNMP manager runs. The MIB file is called tp.my and is normally located in the /opt/TransPath/snmp directory.
Step 3 Load the MIB into the SNMP manager. (See your SNMP manager documentation for more information. Cisco does not recommend an SNMP manager; however, this chapter gives examples using the Hewlett-Packard [HP] OpenView Network Node Manager.)
 | Tips 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), 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) and click OK.
Step 4 Connect the SNMP events to an event category to display the event. As telephony controller events are connected, the format of the event messages can generally be altered for ease of viewing.
| Tips If you are using HP OpenView Network Node Manager, follow these procedures to configure an event: |
(a) Select Options from the File Menu and choose Event Configuration.
(b) From the Event Configuration window, in the Enterprise Identification list, select transpath.
(c) In the Event Identification list, double click on each of the event types, one at a time.
(d) If desired, change the event information display. To change the format of an event, from the Event Configurator / Modify Event window, enter a format in the Event Log Message Box to change the format and labels for received events of this type.
The following example shows how an event can be reformatted using the HP OpenView Network Node Manager.
ID# $13 Name $12 Set $10 MMLname $4 CatDesc $11 \nCompDesc $3 Severity $8 CompID $6 CompType $5 CatID $14\nAlarmNotify $9 AlarmTime$1 ParentID $2 AlarmReported $7\n$o
Step 5 Verify that SNMP is working by logging in to the telephony controller as Root and entering the following command:
traprcv
The traprcv window shows traps that are being sent from the SNMP daemon. Example 2-1 shows a sample traprcv session.
Waiting for traps. Received SNMPv2c Trap: Community: public From: 127.0.0.1 sysUpTime.0 = 304785432 snmpTrapOID.0 = processingError tpAlarmTime.0 = 0xef68e93c00159dc8 tpComponentParentId.0 = 131079 tpComponentDesc.0 = Measurement Manager tpComponentName.0 = MM-01 tpComponentType.0 = 3 tpComponentId.0 = 196611 tpAlarmReported.0 = yes(2) tpAlarmSeverity.0 = major(3) tpAlarmNotify.0 = no(1) tpAlarmSet.0 = clear(1) tpAlarmCatDesc.0 = Required process MOOS tpAlarmCatName.0 = MAJOR M-OOS tpAlarmCatId.0 = 64 tpAlarmId.0 = 0 Received SNMPv2c Trap: Community: public From: 127.0.0.1 sysUpTime.0 = 304786908 snmpTrapOID.0 = processingError tpAlarmTime.0 = 0xef68e93c00159dc8 tpComponentParentId.0 = 131079 tpComponentDesc.0 = Measurement Manager tpComponentName.0 = MM-01 tpComponentType.0 = 3 tpComponentId.0 = 196611 tpAlarmReported.0 = yes(2) tpAlarmSeverity.0 = major(3) tpAlarmNotify.0 = no(1) tpAlarmSet.0 = clear(1) tpAlarmCatDesc.0 = Required Process Failure tpAlarmCatName.0 = SOFTW REQ tpAlarmCatId.0 = 5 tpAlarmId.0 = 0 _
Step 6 Verify that your SNMP Manager is showing the same traps as the traprcv session. If you do not see the events in your SNMP Manager, you may have a port mismatch or an incorrect IP address in your configurations.
Traprcv can receive trap events from multiple telephony controllers. To send trap events from a telephony controller to the computer where traprcv is running, set the SNMP target IP address in the telephony controller software configuration tool and load the new configuration. You can also edit the file /etc/snmpd.conf and change either one of the snmpTargetAddrEntry fields to point to the IP address of the node where traprcv is running, or you can add a new snmpTargetAddrEntry field to the file. However, if you change this file manually, your changes might be lost the next time a configuration is downloaded using the configuration library utility so you might need to make the changes again.
There are two components to use in configuring your telephony controller. The configuration tool is a Java applet that runs in a Web browser on the Network Element Management Server (NEMS) in your telephony solution. Use the configuration tool to create and maintain the configuration files for the telephony controller software. After using the configuration tool to set up your system, use the configuration library utility to transfer and update your configuration files.
Instructions for using the configuration tool to configure your site are found in other documents. For the Cisco SC2200 signaling controller, see the Cisco SC2200 Signaling Controller Configuration Tool Guide, 78-5943-xx. For the Cisco VSC2700 virtual switch controller, see the Cisco VSC2700 Virtual Switch Controller Configuration Tool Guide, 78-6262-xx.
 | Caution The configuration tool is the only approved method for modifying your telephony controller configuration. If you use any other method to make changes to your configuration, these changes may not be copied to the configuration tool and you may not be able to use the configuration tool for subsequent configuration. |
Cisco does not support manual modification of data files or any method of configuration other than the configuration tool, with the following exceptions:
See the "Setting Up the Execution Environment Configuration Parameters" section and the "Configuring Log Files" section for more information on changing these files.
Use the telephony controller's configuration library utility to retrieve the configuration files you created with the configuration tool. You can also use the configuration library utility to store multiple versions of the configuration files. To retrieve your configuration:
Step 1 Log in to the host server. Change to the /opt/TransPath directory and enter the following command:
config-lib retrieve configuration name
The system retrieves the files from the NEMS and stores them in the configuration library under the name that you enter. If you do not choose a name, the configuration is saved with the name "download." The system then copies the files to the software's production area (/opt/TransPath/etc).
You can retrieve earlier configurations for the telephony controller software by using the configuration library utility. To enter the configuration library utility, type the following command:
config-lib
The system returns the following menu:
1. List Configuration Versions in Library 2. Save Production to a new Library Version 3. Copy Library Version to Production 4. Remove Configuration Library Version 5. Backup Configuration Library 6. Restore Configuration Library
Step 2 Restart your system by entering the following command:
init 6
Step 3 Verify that the telephony controller software is running by entering the following command:
ps -ef | grep tran
The system returns a response similar to the following:
transpat 24778 24775 0 Mar 05 ? 1:19 ../bin/dmpr -X 30004 transpat 25306 24775 0 Mar 05 ? 0:12 ../bin/engine -X 30006 transpat 25333 24775 0 Mar 05 ? 0:00 ../bin/ASP -X 30008 transpat 24777 24775 0 Mar 05 ? 0:18 ../bin/cfgM -X 30001 transpat 24775 1 0 Mar 05 ? 2:35 procM transpat 25331 24775 1 Mar 05 ? 8:41 ../bin/ioChanMgr -X 30007 transpat 25334 24775 0 Mar 05 ? 0:03 ../bin/IOCCIP -X 3000d transpat 25335 24775 0 Mar 05 ? 0:02 ../bin/IOCCIP -X 3000c transpat 24779 24775 0 Mar 05 ? 9:39 ../bin/measMgr -X 30003 transpat 24776 24775 0 Mar 05 ? 0:24 ../bin/almM -X 30002 transpat 25332 24775 0 Mar 05 ? 1:59 ../bin/ISDNPRI -X 3000b
This response shows the telephony controller software processes that are running. If you have a failover configuration, the failover daemon should also be running and waiting for an IP connection on port 1050.
Step 4 Verify that the network element (the host server) is operational. Start an MML session by changing to any subdirectory under /opt/TransPath (for example, /opt/Transpath/bin) and entering the following command:
mml
If you receive an error message that sessions are already in use, enter the following command:
mml -s session number
Use any number from 2 to 12 and repeat until you find a vacant session. After successfully entering MML, the prompt changes to:
mml>
Step 5 Enter the following command:
RTRV-NE
The system returns a message similar to the following:
TransPath: SC22 VA-BLACK/TAN (SC2200) 1999-02-23 19:05:45 M RTRV "Type:LPC" "Hardware platform:sun4u sparc SUNW,Ultra-30" "Vendor:"Cisco Systems, Inc"" "Location:TransPath: SC22 VA-BLACK/TAN (SC2200)" "Version:"4.2(10)"" "PStamp:"19981216""
Step 6 Verify that the telephony controller software is running. Enter the following MML command:
RTRV-SOFTW:ALL
The system returns a message similar to the following:
TransPath: SC22 VA-BLACK/TAN (SC2200) 1999-02-23 19:06:05 M RTRV "CFM-01:RUNNING" "ALM-01:RUNNING" "MM-01:RUNNING" "DMPR-01:RUNNING" "DSKM-01:RUNNING" "ENG-01:RUNNING" "IOCM-01:RUNNING" "IOCC-ASP:RUNNING" "SNMP-AGT:RUNNING" "IOCC-01:RUNNING" "IOCC-PRIIP:RUNNING" ;
Use the dial plan provisioning (DPP) tool to set up your dial plan for call routing. Instructions for setting up your dial plan are in other documents. For the VSC, see the Cisco VSC2700 Virtual Switch Controller Dial Plan Provisioning Guide (OL-0128-xx). For the DAS, see the Cisco SC2200 Signaling Controller Dial Plan Provisioning Guide (78-5942-xx).
The telephony controller software uses data files to perform system operations. These data files are created by using the configuration tool and are downloaded to the host server by using the configuration library utility. However, you must edit the data file that contains your execution environment configuration parameters (the XECfgParm.dat file). See the "XECfgParm.dat - XE Configuration Parameters" section for more information about this file.
To set up the configuration parameters:
Step 1 Log in to the host server as Root and change to the /opt/TransPath/etc directory. Edit the XECfgParm.dat file as described in the following steps.
Step 2 Change the *.emsHost = 0.0.0.0 line to *ems.Host = host name or IP address, where host name or IP address is the Network Element Management Server on which the configuration tool is installed.
Step 3 Change the *.transpathID = 1A to *.transpathID = TransPath ID numberA, where TransPath ID number is the number given to the host server when you configured the site using the configuration tool.
Step 4 If you have a single telephony controller and an ARU is present and attached to COM port B, change XE.ARUWriteDevice = /dev/null to XE.ARUWriteDevice = /dev/cua/b. Otherwise, leave the default value.
Step 5 Change *.logPrio = Debug to *.logPrio = Info.
Step 6 Verify that the following entries are prefixed with the # comment symbol so they will not be read by the software:
For a failover configuration, make the following changes to the XECfgParm.dat file:
Step 1 If an ARU is present and a MON port is attached to serial interface adapter port 2, change XE.ARUWriteDevice = /dev/null to XE.ARUWriteDevice =/dev/cua/a002. Otherwise, leave the default value.
Step 2 Set procM.runAsDaemon = false and foverd.runAsDaemon = true to allow the failover daemon to start the system process manager if it is active or the failover replication daemon if it is on standby.
Step 3 Set foverd.conn1Type = socket.
Step 4 Set foverd.conn1AddrA = IP address of this server:1050.
Step 5 Set foverd.conn1AddrB = IP address of other server:1050.
Step 6 Set foverd.conn2Type = serial.
Step 7 Set foverd.conn2AddrA = /dev/cua/a000.
Step 8 Set foverd.conn2AddrB = /dev/cua/a000.
Step 9 Set foverd.abswitchPort = /dev/cua/a001.
Step 10 Prefix foverd.logPrio = Debug and foverd.logDest = all with the # comment symbol so they will not be read by the software.
If you have a Cisco VSC2700 virtual switch controller, edit the XECfgParm.dat file to change the engine.Sys.VirtualSwitch = false parameter to engine.SysVirtualSwitch = true. If you have a Cisco SC2200 signaling controller, use the default value.
If you have a failover system, you need to configure the Network File System (NFS) for your active and standby servers. To configure NFS:
Step 1 Log in to the host server as Root and change to the /opt/TransPath/local directory.
Step 2 Enter the following command:
ls -al
The failover_nfs.sh script should display.
Step 3 Enter the following command:
./failover_nfs.sh
Step 4 At the prompt, enter the host name of the redundant server (not the IP Address that the system requests). Do not include the domain name with the hostname. For example, enter redundant_host rather than redundant_host.cisco.com.
Step 5 Verify that the /opt/remote/etc directory exists.
Step 6 Verify that /etc/dfs/dfstab was updated properly. The dfstab file should include lines similar to the following example:
share -F nfs -o rw=va-tan,root=va-tan /opt/TransPath/etc share -F nfs -o rw=va-tan,root=va-tan /opt/TransPath/dialPlan
Step 7 Verify that /etc/vfstab was updated properly. The vfstab file should include lines similar to the following example:
va-tan:/opt/TransPath/etc - /opt/remote/etc nfs 0 yes bg va-tan:/opt/TransPath/dialPlan - /opt/remote/dialPlan nfs 0 yes bg
Step 8 Verify NFS mounts by entering the df -k command. The returned message should contain lines similar to the following example:
Filesystem kbytes used avail capacity Mounted on
va-tan:/opt/TransPath/etc
1446048 512240 789208 40% /opt/remote/etc
va-tan:/opt/TransPath/dialPlan
1446048 512240 789208 40% /opt/remote/dialPlan
This chapter described how to prepare your telephony controller. To see an overview of basic telephony controller operations, proceed to "Operating Your Telephony Controller" that describes operational procedures, including how to start and stop processes, retrieve signal channel attributes, and manage signal channels.
Posted: Fri Jan 7 09:59:21 PST 2000
Copyright 2000©Cisco Systems Inc.