|
|
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 SNMP agent is started when the system is booted. It can also be started manually through a startup script.
To start the SNMP agent manually, perform these steps:
Step 1 Type: cd /etc/rc3.d
Step 2 Type: sh s88sp
To start the ACB and server agents, perform the following steps.
Step 1 From the command line, type:
umcli -s start <component>
| Component | Description |
|---|---|
acb | Starts the Agent Communications Broker agent (SPOBJ). This action starts the SPOBJ process and reloads the Schedule table, which triggers the starting of application agents. It also starts the TRAPMAN and the 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, logging, TRAPMAN, and CMA. |
When you stop the ACB or a server agent, the agent's processes are terminated. You cannot safely 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.
Step 1 Quiesce the ACB or server agent.
(a) At the command line, type umcli
(b) At the umcli prompt, type: quiesce <agent>
where agent = acb
Step 2 Stop the following application agents: MWI_Notify, MWI_OnOff, LogRemover, SMS_Notify, and FaxPrint. See "Stopping Application Agents" in this chapter.
Step 3 Ensure that server agent sessions have completed. At the umcli prompt, type:
(a) watch acb entries
(b) watch cma sessions
Step 4 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, CMA, ACB, TRAPMAN, LogRemover, and LOGSUB. |
Step 1 Stop the server agent. At the command line, type:
umcli -s stop <agent>.
(See Table 3-2 for valid values for the <agent>.)
Step 1 Log in as root.
Step 2 Type:
kill <PID of the SNMP agent 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 1 At the command line, type: umcli
Step 2 View the list of running application agents. Type: watch acb entries
Step 3 If the application agent doesn't appear in the listing, ensure that the application agent is not commented out in the $PARMLIB/parms/APP/Schedule.hostname file.
Step 4 Type: resched <agent>
| Agent | 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. |
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 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 1 In the $PARMLIB/parms/APP/Schedule.hostname file, comment out the appropriate lines for the agents you wish to stop.
Step 2 Reload the Schedule table.
(a) At the command line, type: umcli
(b) Type: resched all. See Table 3-3.
Step 3 Type kill <pid> for the process IDs of each application agent you wish to stop.
Step 1 Type:
kill <pid> for the process IDs of each application agent you wish to stop.
MWI_PlugIn is a library that runs as part of the Netscape Messaging Server, and must also be managed.
MWI_PassOff, on the other hand, is a daemon process that runs on the Messaging Server host, but is started and stopped independent of the Messaging Server.
Step 1 Access the Messaging Server host.
Step 2 As super user, type: cd /opt/local/bin
Step 3 Type: ./MWI_PassOff -h <hostname>
where hostname is the machine on which MWI_Notify is running
Step 4 Start the Messaging Server process. This action loads MWI_PlugIn
Step 1 Unconfigure MWI_PlugIn on the Messaging Server.
Step 2 Stop the Messaging Server.
This action stops MWI_PlugIn because it runs as part of Messaging Server. (See your vendor documentation for the procedure for stopping this server.)
Step 3 Terminate the MWI_PassOff process:
Step 4 Start the 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 UM 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 rules configuration file. |
/home2/spmaster/r410/TNT/parms/H323.ini | The H323 protocol 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/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/AmtevaData.ini | UMSA/PMA configuration files. |
/home2/spmaster/ADMIN/cgi-bin/oam.ini /home2/spmaster/ummgr/Scripts/Extractor/version.ini | UCM 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 Log Files", for detailed information about log files.
The subscriber information that you should backup includes:
Posted: Mon Sep 25 19:41:03 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.