|
|
This chapter includes:
This section provides instructions for starting and stopping server and application agents. When you are managing agents, keep the following in mind:
The uOne SNMP agent is started when the system is booted. It can also be started manually through a startup script.
 |
Note You cannot use the umcli tool to start the SNMP agent. |
To start the uOne SNMP agent manually, perform these steps:
Step 2 Type: cd /etc/rc3.d
Step 3 Type: sh S88sp
|
Note If AutoRestart is on, this command will start all server and configured application agents. |
To start the ACB and server agents, perform the following steps.
|
Note The ACB must be running for any agent to run, except for the SNMP agent. |
Step 2 From the command line, type:
umcli -s start <component>
| Component | Description |
|---|---|
acb | Starts the Agent Communications Broker (SPOBJ). This action starts the SPOBJ process and reloads the Schedule table, which triggers the starting of STATIC_NOWAIT application agents and server agents. It also starts the TRAPMAN and LOGSUB processes if they are not already running. |
cma | Starts the Call/Media Control agent (TNTOBJECT). This action starts the TNTOBJECT process. |
system | Starts the ACB, LOGSUB, TRAPMAN, and CMA. |
Step 3 To exit umcli, type:
exit
When you stop the ACB or a server agent, the corresponding processes are terminated. You cannot gracefully stop the ACB or a server agent while it is in use. Therefore, in the following procedure all sessions to the ACB or server agents are terminated before actually stopping the ACB or server agent.
When you put the ACB or a server agent in a quiesced state, the ACB or server agent will not allow new sessions to begin. (For example, the ACB will not allow startapp requests.) However, the ACB or server agent will allow current sessions to complete.
|
Note If an ungraceful stopping of the ACB or server agent is acceptable, you may stop the ACB or agent without quiescing. |
Step 2 Quiesce the ACB or server agent.
a. At the command line, type:
b. At the umcli prompt, type:
|
Note The umcli tool does not currently support quiescing the CMA agent. |
Step 3 Gracefully stop the following persistent application agents: MWI_Notify, MWI_OnOff, LogRemover, SMS_Notify, and FaxPrint. See "Stopping Application Agents" in this chapter.
Step 4 Ensure that all application agent sessions have completed. At the umcli prompt, type:
watch acb entries
Step 5 Stop the ACB or server agent(s). At the umcli prompt, type:
stop <agent>
| Agent | Description |
|---|---|
acb | Stops all application agents, CMA, and ACB. |
cma | Stops the Call/Media Control agent (TNTOBJECT). |
system | Stops all application agents (including LogRemover), CMA, ACB, TRAPMAN, and LOGSUB. |
Use the following procedure to ungracefully stop the ACB or a server agent.
Step 2 Stop the server agent. At the command line, type:
umcli -s stop <agent>(See Table 3-2 for valid values for the <agent>.)
Step 2 Obtain the PID of the SNMP agent process:
ps -ef | grep snmpd
Step 3 Type:
kill <PID of the snmpd process> |
Note If the above command is not effective, try kill -9 <PID of the snmpd process>. |
The application agents that run in the uOne system are UM, MWI_Notify, MWI_OnOff, LogRemover, SMS_Notify, and FaxPrint. This section contains procedures for starting and stopping these application agents.
Step 2 At the command line, type:
umcliStep 3 View the list of running application agents. Type:
watch acb entriesStep 4 If the desired application agent doesn't appear in the listing, ensure that the application agent is not scheduled as STATIC_NOWAIT and is not commented out in the $PARMLIB/parms/APP/Schedule.<hostname> file.
Step 5 Type: reload sched <parameter>
| Parameter | Description |
|---|---|
all | Forces the ACB to reload the Schedule.hostname table and starts any static agents in the table that are not running. It will not stop any agents currently running. |
static <token> | Starts a specified static application that already exists in the Schedule.<hostname> table. <token>=any token in the Schedule.<hostname> table that is designated as a static application, for example, FaxPrint, LogRemover, etc. |
|
Note If you add a new token to the Schedule.<hostname> table, you must use reload sched all or start acb to initially start the application. If you need to restart the application at a later time, you can use reload sched static <token> to restart a static application since it is listed in the currently loaded schedule table. |
You may want to stop an application agent under certain circumstances. For instance, when an application agent malfunctions, you may need to stop the application agent and then restart it. It is important to stop application agents before upgrading their software or before removing an application agent from the system.
If you want to stop all application agents and the ACB, you can just stop the ACB. This action will stop the application agents automatically. If you intend to upgrade or remove the entire system, you should first issue a "stop system."
Step 2 In the $PARMLIB/parms/APP/Schedule.<hostname> file, comment out the appropriate lines for the agents you wish to stop.
Step 3 Reload the Schedule table.
a. At the command line, type:
b. At the umcli prompt, type:
Step 4 For the process IDs of each application agent you wish to stop, at the command line type:
kill <pid> |
Note If the process with that pid is still running, try kill -9 <pid>. |
The following procedure only works if the agent is not configured to auto restart by the ACB. If the agent is configured to auto restart, the current instance of it will stop, however, the ACB will automatically replace it with a new instance. If this is not what you want, use the procedure in the previous section.
Step 2 For the process IDs of each application agent you wish to stop, at the command line, type:
kill <pid> |
Note If the process with that pid is still running, try kill -9 <pid>. |
MWI_PlugIn.so and notify.so are libraries that run as part of the Netscape Messaging Server, and must therefore be managed. as part of the Netscape Messaging Server. The notify.so library is needed only if the SMS feature is configured.
|
Note MWI_PlugIn.so is only needed for MWI/pager notification of new messages; notify.so is only needed for SMS notification of new messages. |
MWI_PassOff, on the other hand, is a daemon process that runs on the Netscape Messaging Server host, but is started and stopped independent of the messaging server.
Step 2 Log in as root.
Step 3 Type: cd /opt/local/bin
Step 4 At the command line, type:
./MWI_PassOff -h <hostname> |
Note Do not specify the -d option (debugging) in a production environment |
Step 5 Start the Netscape Messaging Server process. This action loads MWI_PlugIn.
This action stops the MWI_PlugIn.so and notify.so libraries because they run as part of Netscape Messaging Server. (See your vendor documentation for the procedure for stopping this server.)
Step 2 Terminate the MWI_PassOff process:
|
Note If the above command is not effective, try kill -9 <pid>. |
Step 3 Start the Netscape Messaging Server.
You should backup three types of information on the uOne system:
Table 3-4 identifies all of the Gateserver configuration directories and files that you should back up.
| Configuration Directory or File | Description |
|---|---|
/home2/spmaster/r410/parms | Directory containing ACB, CMA, and application agents configuration files, as well as overrides of ACB parameter settings. |
/home2/spmaster/r410/apps/UM/UM.ini | Main configuration file for the uOne application. |
/home2/spmaster/r410/apps/UM/FaxPrint.ini and any other FaxPrint ini files used for parallel sends. | Configuration file for the FaxPrint application agent. |
/home2/spmaster/r410/apps/MWI_OnOff/MWI_OnOff.ini | Configuration file for the MWI_OnOff application agent. |
/home2/spmaster/r410/apps/MWI_Notify/MWI_Notify.ini | Configuration file for MWI_Notify application agent. |
/home2/spmaster/r410/apps/LogRemover/LogRemover.ini | Configuration file for the LogRemover application agent. |
/home2/spmaster/r410/apps/SMS_Notify/SMS_Notify.ini | Configuration file for the SMS_Notify application agent. |
/home2/spmaster/r410/parms/SNMP/SPsnmp.ini | SNMP subagent configuration files. |
/home2/spmaster/r410/TNT/parms/DialMap.ini | The address and dialing rules configuration file. |
/home2/spmaster/r410/TNT/parms/H323.ini | The H323 resource module configuration file |
/home2/spmaster/r410/TNT/parms/XGCP.ini | The XGCP resource module configuration file |
/home2/spmaster/r410/TNT/parms/SMSI.ini | The SMSI configuration file. |
/home2/spmaster/r410/TNT/parms/TNT.ini | The CMA server agent configuration file. |
/home2/spmaster/r410/TNT/parms/TTSP.ini | The Text-to-Speech configuration file. |
/home2/spmaster/r410/TNT/parms/vendor/* | Radvision (H.323) set up files. |
/home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata/schemaConfig.ini /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata/pagerData.ini /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata/indexData.ini /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata/languageData.ini /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata/loggingData.ini /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata/defaultData.ini /home2/spmaster/ADMIN/cgi-bin/SUBadmin/UI/Cisco_Data.ini | uOne Administration/PMA configuration files. |
/home2/spmaster/ADMIN/cgi-bin/oam.ini /home2/spmaster/ummgr/Scripts/Extractor/version.ini | uOne Manager configuration files. |
The information in log files is helpful for troubleshooting problems, especially if a problem is the result of events that occur over a period of time. Also, certain log files contain call detail record data useful for billing and capacity planning. You should back up the directories that contain log files on all servers in your uOne system. Refer to "Working with uOne Log Files", for detailed information about log files.
The subscriber information that you should backup includes:
Posted: Mon Sep 25 20:15:46 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.