Table of Contents

Using SNMP Capabilities
Monitoring uOne Resources

Viewing Server Agent Status
Viewing ACB Status
Viewing H.323 Resource Status
Viewing CMA Status
Viewing MWI/Paging Notification Information
Viewing SMS Notification Information
Viewing FaxPrint Information
Monitoring LACS

Monitoring Gateserver System Resources

Monitoring the uOne System

This chapter includes information about:

• Using SNMP capabilities

• Monitoring uOne resources

• Monitoring system resources on the Gateserver.

Using SNMP Capabilities

The uOne SNMP agent provides status information on various components in the uOne environment. You can view this information in real time using standard SNMP monitoring stations. Refer to "Supported MIBs" and "SNMP Trap IDs" for more information about SNMP support for uOne.

Monitoring uOne Resources

You perform the following tasks to ensure that uOne is functioning properly:

• View server agent status

• View ACB status

• View H.323 status

• View CMA status

• View MWI/paging notification information

• View SMS Notification information

• View FaxPrint information

Viewing Server Agent Status

For the uOne system to run smoothly and be completely functional, all those server agents must be up and running at all times. A crucial part of your job is to ensure that the following uOne server agents are up on the system:

• ACB

• CMA

• SNMP

• LOGSUB

• TRAPMAN

Note   CMA only needs to be up on systems where it is configured.

To view server agent status:

Step 2   At the command line, type:

A screen similar to the one shown in Figure 2-1 displays.

Viewing ACB Status

The ACB is a set of services used by agents for communications and other services. You should monitor the status of the ACB and agents to ensure that they are functioning properly

Step 2   At the command line, type:

Step 3   At the umcli prompt, type:

A screen similar to the one shown in Figure 2-2 displays.

You should also monitor other ACB information, such as states, threads, and comm. Refer to "The umcli Tool" in this manual for details on monitoring that information.

Viewing H.323 Resource Status

If you are using H.323, it is important to monitor the H.323 resource module to ensure communications between the VoIP network and the CMA are functioning properly.

Step 2   At the command line, type:

Step 3   At the umcli prompt, type:

A screen similar to the one shown in Figure 2-3 displays.

Note   The number of records shown is three times the maximum number of permitted simultaneous inbound calls (max ports configured in H.323.ini).

You can also monitor other H.323 resource module information, such as sentries and radvision. Refer to "The umcli Tool" in this manual for details on monitoring that information.

Viewing CMA Status

CMA provides telephony and VoIP services to application agents. You should monitor this crucial resource to ensure that CMA services are available to applications when they are needed.

Step 2   At the command line, type:

Step 3   At the umcli prompt, type one of the following commands:

• watch cma sessions

• watch cma groups

• watch cma scr

Figure 2-4, Figure 2-5, and Figure 2-6 display sample screens for these commands.

Viewing MWI/Paging Notification Information

To ensure that subscribers are notified when they receive new messages in their mailboxes, it is a good idea to monitor whether MWI and paging notification requests are succeeding or failing.

Step 2   At the command line, type:

Step 3   At the umcli prompt, type:

A screen similar to the one shown in Figure 2-7 displays.

Viewing SMS Notification Information

To ensure that subscribers receive their Short Message Service notification when they receive new messages in their mailboxes, it is a good idea to monitor whether SMS notification requests are succeeding or failing.

Step 2   At the command line, type:

Step 3   At the umcli prompt, type:

A screen similar to the one shown in Figure 2-8 displays.

Viewing FaxPrint Information

To ensure that the FaxPrint application is successfully sending subscribers' faxes to a fax machine to be printed, it is a good idea to monitor whether FaxPrint activity is working properly. Since multiple FaxPrint processes may run on a host, it is important to monitor each process.

Step 2   At the command line, type:

Step 3   At the umcli prompt, type:

A screen similar to the one shown in Figure 2-9 displays.

Monitoring LACS

LACS (SSIO) contains buffers that must have at least 10% free. Minor fluctuations in number free buffers can be expected; however, dramatic changes should not occur. To ensure that at least 10% of the buffers are free, follow this procedure:

Step 2   Type:

SSIOdump -i

Monitoring Gateserver System Resources

To ensure optimal system performance, you should monitor the following resources on the Gateserver:

• The available blocks and inodes on all file systems.

• Processor usage.

• Virtual and physical memory usage.

• VoIP port usage.

• Network bandwidth usage.

Table 2-1 provides threshold recommendations for each of these resources on the Gateserver, as well as the tools available for monitoring their performance.

Table 2-1: Monitoring the Gateserver

Resource	Monitoring Tool	Threshold
File system (blocks and inodes)	df command blocks: df -k inodes: df -e	Blocks:   No more than 80% capacity for these file systems:   /home2, /tmp, /var, and /var/tmp.   No more than 90% capacity for all remaining file systems. Inodes:   At least 1000 free inodes on all file systems.
Processor usage	sar command (sar  -u  5   2) or vmstat  5 or top or mpstat 5	No less than 25% idle time.
Memory (physical and virtual)	Physical: vmstat ps -e | grep pageout Virtual:: top vmstat	Physical:   No paging due to memory shortage is indicated by "pageout" column (ps -e)   The "SR statistic" column needs to be close to zero (vmstat) Virtual:   The top command should not show any process with a virtual address size that steadily increases day by day.   The available swap space must not decrease day by day.
VoIP calls	If you are using H.323, access the umcli tool and issue this command: watch h323 states. Count the number of idle calls.	At least 2 voice calls should be idle.
Network collisions	netstat command (netstat -i) Use this formula to calculate the collision rate:  ( coll / opkts ) * 100	No more than 2% rate.
Network bandwidth	Use the Show interface IOS command on your switching hub	10% free bandwidth.

Posted: Mon Sep 25 20:16:18 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.