Table of Contents

Getting Started

Overview of Operations Tasks
Key Maintenance Concepts
Understanding uOne Processes
Using uOne Tools

Getting Started

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.

Overview of Operations Tasks

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, 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.

Key Maintenance Concepts

Every computer system is unique; therefore, system monitoring and maintenance requirements will differ from system to system. Certain concepts, however, apply to keeping any system running smoothly. The following list defines items that will help with your daily operations.

• Response Time: How fast an external subscriber will see a response to initial input or connection request. This is the most visible measure of service quality; therefore, anything that has a negative impact on server response times can be viewed as unacceptable to customers.

• Optimum Capacity: A system's capacity level is pre-determined by hardware components and network bandwidth specified prior to software installation. This capacity level can be optimized by performance "tuning" during the pre-production and production process. A service running at optimum capacity levels means response times to customers and remote servers are within acceptable ranges.

• Stress: When the optimum capacity of uOne has been exceeded, stress is placed on the system. This can lead to system time outs, system lock outs, and unacceptable response times.

• Open Systems: The uOne application is a standards-based, multi-platform open system. This means that various third party software components are critical to successful operation. Third party components, as well as uOne software, must be monitored and maintained. Although some third party components are mentioned in this document, for detailed discussion of third party software operations, refer to the vendors' documentation.

• SNMP Manager: The Simple Network Management Protocol (SNMP) is the Internet standard protocol developed to manage nodes on an IP network. The value of using SNMP is customers have the ability to manage uOne software as well as other third party software and hardware vendors. Many third party vendors support SNMP management. This simplifies integration and management of multiple vendor solutions. This information is particularly useful because it can be viewed in real-time without any script development or parsing of logs. It can be viewed with standard SNMP monitoring stations, and provides information about the present state of the system.

Understanding uOne Processes

Table 1-2, Table 1-3, and Table 1-4 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.

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.
Table 1-2: Processes on the GateServer that Support the uOne Product

Processes	Description	When It Runs
SPOBJ	The Agent Manager and Monitor (AMM) server agent process. Runs on all GateServers. Also known as ACB, APP, and BASE.	Continually
TNTOBJECT	The Call Control / Media Control server agent (CMA) process. Only runs on GateServers where the CMA server agent is configured. Also known as TNT.	Continually
FaxPrint	Outbound Fax process. Only runs on GateServers where the FaxPrint is configured. There can be multiple FaxPrint processes on a host.	Continually
httpd Apache 1.3.6 HTTP daemon (web server software)	Unified Messaging System Administration (UMSA), Unified Communications Manager (UCM), and Personal Mailbox Administration (PMA) web interface processes. Only runs on GateServers where the UMSA, UCM, or PMA are installed. There can be multiple httpd processes on a host.	Continually
LogRemover	Log file move/remove process. Runs on all GateServers.	Continually
LOGSUB	The logging process for the ACB and UM application and server agents. Also the centralized logging process for remote logging features.	Continually
MWI_Notify	MWI_Notify application process. Only runs on GateServers where the MWI_Notify  application agent is configured. There is one such process per Messaging Server.	Continually
MWI_OnOff	MWI_OnOff application process. Only runs on GateServers where the MWI_OnOff  application agent is configured. There is one such process per Messaging Server.	Continually
snmpd (snmpdx)	SNMP subagent process. (Optional Solaris SNMP master agent process)	Continually
UM	UM application agent process.	Only when processing an incoming UM call
SMS_Notify	SMS_Notify application	Continually
TRAPMAN	Process that sends application traps to the SNMP manager(s).	Continually

Table 1-3: Processes on the Messaging Server that Support the uOne Product

Process	Description	When It Runs
MWI_PassOff	MWI_PassOff daemon Netscape deployments only	Continually

Table 1-4: Processes on the HylaFAX Paging Server that Support the uOne Product

Processes	Description	When It Runs
faxq	The central scheduler process.	Continually
faxgetty	Processes that handle outgoing calls to the paging service provider.	Continually
hfaxd	Paging server daemon.	Continually
faxqclean	Spooling area cleaner process.	Continually

Using uOne Tools

The uOne product provides the following tools for operations personnel:

• Unified Communications Manager (UCM)—A centralized reporting and monitoring tool for the distributed uOne system. The UCM is an optional package. (See "Centralized Management of the uOne System" in this manual for information about UCM.)

• UM Command Line Interface (CLI)—An administrative and diagnostic tool. It provides commands for starting/stopping server agents and the uOne system, changing log levels, and reloading the Schedule tables. The tool also has real-time monitors that can help operations personnel troubleshoot problems. (See "The umcli Tool" in this manual for information about using this tool.)

Posted: Mon Sep 25 19:53:57 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.