|
|
This chapter introduces you to tasks you'll perform to support the uOne product, the tools that you will use, and recommendations for how often you should perform each task. It includes descriptions of the uOne processes and key concepts.
The uOne product is designed to operate 24 hours a day, seven days a week. As with any such application, it should be consistently monitored. Individual components should be adjusted based on performance requirements, observed performance, processor usage, file system usage, physical memory usage, virtual memory usage, and network usage. This chapter provides a description of the monitoring tools that can be used to analyze and maintain an optimally performing system.
Table 1-1 contains an overview of the tasks you'll perform to monitor and maintain the uOne product. Most of the tasks will be performed on the Gateserver.
![]() |
Note The uOne Manager is an optional web-based OA&M tool. Check with your system administrator to see if that tool is installed on your uOne system |
| Task | Frequency | Tool Used |
|---|---|---|
Monitor agent process status | Daily | uOne Manager, umcli, SNMP1 |
Collect information about system resources | Daily | UNIX commands, SNMP1 |
Back up files and data | Daily/monthly | UNIX commands |
Start/stop agents | When required | umcli, SNMP1 |
Restore files and data | When required | UNIX commands |
When required | UNIX commands, uOne Manager, umcli, SNMP1 |
| 1SNMP support is provided through MIBS and traps. |
Table 1-2 and Table 1-3 describe the processes that should be running for the uOne system to be fully functional. You'll need to monitor these processes to ensure that the uOne system is running smoothly.
![]() |
Note Only those processes that are important to the uOne product are listed in the following tables. Other processes that reside on these servers are not listed. |
In addition to the processes described in the following tables, you'll need to monitor the processes on your messaging, directory, and paging servers. Please check your vendor documentation for details on monitoring these third-party server processes.
| Processes | Description | When It Runs |
|---|---|---|
SPOBJ | The Agent Communications Broker (ACB) server agent process. Runs on all Gateservers. Also known as AMM, APP, and BASE. | Continually |
TNTOBJECT | The Call / Media Control server agent (CMA) process. Only runs on Gateservers where the CMA server agent is configured. Also known as TNT. | Continually |
Outbound Fax process. Only runs on Gateservers where FaxPrint is configured. There can be multiple FaxPrint processes on a host. | Continually | |
httpd Apache 1.3.4 HTTP daemon (web server software) | HTTP server process for the uOne Administration, uOne Manager, and Personal Mailbox Administration (PMA) web interfaces. Only runs on Gateservers where uOne Administration, uOne Manager, or PMA are installed. There can be multiple httpd processes on a host. | Continually |
Log file move/remove process. Runs on all Gateservers. | Continually | |
LOGSUB | The logging process for the ACB, and application and server agents. Also the centralized logging process for remote logging features. | Continually |
Continually | ||
Continually | ||
snmpd (snmpdx) | SNMP subagent process for uOne. (Optional Solaris SNMP master agent process) | Continually |
UM | uOne application agent process. | Only when processing an incoming uOne call |
SMS_Notify | SMS_Notify application process. Receives notification from an SMS_Notify mailbox via notify.so library. | Continually |
TRAPMAN | Process that sends application and server agent traps to the SNMP manager(s). | Continually |
| Process | Description | When It Runs |
|---|---|---|
MWI_PassOff daemon. Receives notification records from MWI_LpugIn.so library. | Continually |
The uOne product provides the following tools for operations personnel:
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon Sep 25 20:16:53 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.