NETWORK

H E A L T H Application Brief

Using the BMC PATROL SNMP Agent

Release 4.5 and Later

Concord Communications, Inc. 33 Boston Post Road West Marlboro, Massachusetts 01752

T6-9901-0001 February 1999

Important Notice
The Total View is a trademark, and Concord, the Concord logo, Network Health, and TRAKKER are registered trademarks of Concord Communications, Inc. BMC Software, PATROL, PATROL Agent, PATROL Agent for UNIX, PATROL Agent for Windows NT, PATROL Console, PATROL Knowledge Module, PATROL KM, PATROL Script Language and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. in the USA and in other select countries. INGRES is a registered trademark of Ingres Corporation. Motif is a trademark of Open Systems Foundation, Inc. PostScript is a registered trademark of Adobe Systems, Inc. SMIC. Copyright 1992 SynOptics Communications, Inc. All Rights Reserved. SynOptics makes no representations about the suitability of this software for any particular purpose. The software is supplied as is, and SynOptics makes no warranty, either express or implied, as to the use, operation, condition, or performance of the software. SynOptics retains all title and ownership in the software. Sun Microsystems, Sun Workstation, and NFS are registered trademarks of Sun Microsystems, Inc. Sun, Sun-4, SunOS, SunNet, and OpenWindows are trademarks of Sun Microsystems, Inc. SPARC is a registered trademark of SPARC International, Inc. SPARCstation and SPARCserver are trademarks of SPARC International, Inc. SQR is a trademark of SQ Software, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. General Notice: Some of the product names used herein have been used for identification purposes only and may be trademarks of their respective companies.

Proprietary Notice
The information and descriptions contained herein are the property of Concord Communications, Inc. Such information and descriptions may not be copied, disseminated, or distributed without the express written consent of Concord Communications, Inc. Concord Communications, Inc., assumes no responsibility for any inaccuracies that may appear in this document. Concord Communications, Inc., reserves the right to improve its products and change specifications at any time without notice.

U. S. Government Restricted Rights

Use, reproduction, and disclosure by the U.S. Government are subject to the restrictions set forth in FAR 52.227-19 (c) (1) and (2) and DFARS 252.227-7013 (c) (1) (ii).

1999 Concord Communications, Inc.

All Rights Reserved For assistance, contact Customer Support at: Phone: Fax: Email: Web site: (888) 832-4340 (for calls from the USA and Canada) (508) 303-4300 (for calls from other countries) (508) 303-4343 support@concord.com http://www.concord.com

Using the BMC PATROL SNMP Agent

This application brief describes: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Troubleshooting the BMC Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Discovering BMC PATROL Agents at Different Port Numbers . . . . . . . . . . . . . . . . . . . 8 Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Known Issues with BMC PATROL Agent for Windows NT . . . . . . . . . . . . . . . . . . . . . 10 Known Issues with BMC PATROL Agent for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Network Health Variables Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Introduction
This application brief describes how to use the BMC PATROL SNMP Agent as a data source for Network Health reports. To discover, poll, and generate reports on servers that have the BMC PATROL Agent installed, you must install Network Health Release 4.1.5 or later on a Windows NT or UNIX system and license the Network Health Server application. You can use the BMC PATROL Agent as a data source for the following report types: Health At-a-Glance Trend Service Level Support for the BMC PATROL Agent adds a new server type to Network Health. Network Health discovers and polls elements with BMC PATROL Agents the same way it does any other server agent. NOTE For the most up-to-date information about support for the BMC PATROL Agent in Network Health, refer to the latest version of this application brief in the Post-Sales Support area of the Concord Web site.

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Software Requirements

Software Requirements
This section describes the software requirements for the BMC server and the Network Health server to discover, poll, and generate reports. For information about known issues when Network Health discovers BMC servers, refer to the Known Issues with BMC PATROL Agent for Windows NT section on page 10 and the Known Issues with BMC PATROL Agent for UNIX section on page 11.

BMC Server Requirements

You must install the following software on each BMC server that you want Network Health to discover, poll, and report on: BMC PATROL SNMP Agent Version 3.2.5 or later for Windows NT, Solaris, or HP-UX The BMC PATROL Agent consists of a master agent and sub-agent. Make sure the BMC PATROL Agent is started. In addition, make sure the BMC PATROL master agent and sub-agent are started and can communicate with the Network Health server. The required BMC PATROL Knowledge Modules (KMs) for your operating system In addition to the BMC PATROL Agent, you must install either the Windows NT Knowledge Modules or UNIX Knowledge Modules on the BMC server. The Knowledge Modules enable the BMC PATROL Agent to collect information about server elements including the server, CPUs, disks, partitions for each local storage unit (partition, file system, volume, or drive), and network interfaces. Install all the Knowledge Modules listed in the following table for your BMC servers operating system:
Windows NT Knowledge Modules NT_CACHE Version 1.15 NT_CPU Version 1.28 NT_LOGICAL_DISKS Version 1.27 NT_MEMORY Version 1.18 NT_NETWORK Version 1.21 NT_SERVER Version 1.22 UNIX Knowledge Modules CPU Version 10.0 DISK Version 10.0 FILESYSTEM Version 10.0 MEMORY Version 10.0 NETWORK Version 10.0 SWAP Version 10.0 USERS Version 10.0

For information about troubleshooting the software installation on the BMC server, refer to the Troubleshooting the BMC Installation section on page 3.

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Troubleshooting the BMC Installation

Network Health Server Requirements

On the Windows NT or UNIX system designated as the Network Health server, you must install Network Health Release 4.1.5 or later. You also need the Network Health Server application license and the appropriate number of poller licenses to use the BMC PATROL Agent as a data source in Network Health 4.1.5. No other special Network Health licenses are required.

Troubleshooting the BMC Installation

This section describes how to troubleshoot problems with each of the required components of the BMC PATROL installation. For detailed instructions on installing and configuring the BMC PATROL software, refer to your BMC PATROL documentation.

Basic Steps
If Network Health cannot discover or poll your BMC servers, follow these steps to isolate and resolve the problem:
Perform this step 1. 2. Verify that the BMC PATROL Agent is running. Verify that the BMC PATROL master agent is running and can communicate with the Network Health server. Verify that the BMC PATROL sub-agent is running and can communicate with the Network Health server. Verify that the BMC PATROL Knowledge Modules are installed. Using instructions in this section Troubleshooting the BMC PATROL Agent Installation on page 4 Troubleshooting the BMC PATROL Master Agent Installation on page 4 Troubleshooting the BMC PATROL Sub-Agent Installation on page 5 Troubleshooting the BMC PATROL Knowledge Modules Installation on page 7

3.

4.

About the nhSnmpTool Command

Several of the troubleshooting procedures in this section instruct you to use the Network Health nhSnmpTool command to verify portions of the BMC installation. The nhSnmpTool command displays a subset of the Management Information Base (MIB) for the specified host and MIB. The nhSnmpTool command is located in the bin subdirectory of the Network Health installation directory.

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Troubleshooting the BMC Installation

These troubleshooting procedures provide examples of nhSnmpTool syntax and output. The examples are formatted for readability. For complete information about the nhSnmpTool command syntax, refer to the Command Reference section in the Network Health User Guide. NOTE Use the nhSnmpTool command only under the direction of Concord Customer Support or your Application Engineer.

Troubleshooting the BMC PATROL Agent Installation

To troubleshoot the BMC PATROL Agent installation:
1.

Verify that the BMC PATROL SNMP Agent is running on the BMC server by doing one of the following: On Windows NT, display the Task Manager and make sure that a process named PatrolAgent.exe is running. On UNIX, issue the ps command and make sure that a process named PatrolAgent is running. For example:
>

ps -ef | grep Patrol bin 15438 1 1 13:28:10 ?

0:42 PatrolAgent

2.

If the PatrolAgent process is not running on the BMC server, start it by doing one of the following: On Windows NT, display the Services dialog box in the Control Panel and start the PatrolAgent service. On UNIX, change to the BMC PATROL installation directory (as defined by the $PATROL_HOME environment variable) and issue the following command:
>

./PatrolAgent

Troubleshooting the BMC PATROL Master Agent Installation

To troubleshoot the BMC PATROL master agent installation:
1.

Verify that the BMC PATROL master agent is running on the BMC server by doing one of the following: On Windows NT, display the Task Manager and make sure that a process named Snmpmagt.exe is running. On UNIX, issue the ps command and make sure that a process named snmpmagt is running. For example:
>

ps -ef | grep snmp root 15454 1 0 13:28:17 ? 0:06 ./snmpmagt /export/mozart1/PATROL3.2/Solaris25-sun4/lib/snmpmagt.cfg NOV

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Troubleshooting the BMC Installation

2.

Use the nhSnmpTool command to verify that the Network Health server can communicate with the BMC PATROL master agent. The BMC PATROL master agent supports the MIB system group variables. The output of nhSnmpTool should be similar to the following example:
>

nhSnmpTool -n -o .1.3.6.1.2.1 -p 1161 192.124.15.118 # 192.124.15.118:.1.3.6.1.2.1 targetTxt = mib-2 sysDescr.0 = PEER Networks, a division of BMC Software, Inc., PATROL(R) SNMP Toolkit, OptiMaster Release 1.9.1 on Solaris 2.5 sysObjectID.0 = 1.3.6.1.4.1.442.1.1.1.9.2 sysUpTime.0 = 0d 0:18:40.90

3.

If Network Health cannot communicate with the BMC PATROL master agent, check the lib/snmpmagt.cfg file in the BMC PATROL installation directory to make sure the MANAGER and COMMUNITY names are valid.

Troubleshooting the BMC PATROL Sub-Agent Installation

If the BMC PATROL sub-agent does not start after you reboot the BMC server, Network Health cannot retrieve data from that server. The following error message appears in the log/PatrolAgent-host-port.errs file in the PATROL installation directory to indicate that the PATROL Agent or sub-agent did not start:
PATROL SNMP Sub-Agent init failed Make sure PATROL SNMP Master Agent is running

BMC has fixed this problem in a maintenance release of PATROL KM for Windows NT Version 3.5. If you see this error message, contact BMC Customer Support for instructions on downloading and installing the required software (pkm_nt35.exe). To troubleshoot general problems with the BMC PATROL sub-agent installation:
1.

Use the nhSnmpTool command to verify that the BMC PATROL sub-agent is running on the BMC server.

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Troubleshooting the BMC Installation

If the sub-agent is running, the output from nhSnmpTool should be similar to the following example:
>

nhSnmpTool -n -o .1.3.6.1.4.1.1031 -p 1161 192.124.15.161 # 192.124.15.161:.1.3.6.1.4.1.1031 targetTxt = enterprises.1031 enterprises.1031.1.1.1.2.0 = 2F enterprises.1031.1.1.1.3.1.1.16.84.101.114.109.105.110.97.108. 69.109.117.108.97.116.111.114 = 54:65:72:6D: enterprises.1031.1.1.1.3.1.1.16.78.84.95.76.79.71.73.67.65.76. 95.68.73.83.75.83 = 4E:54:5F:4C:4F:47:49:43: enterprises.1031.1.1.1.3.1.1.14.83.101.116.117.112.67.108.101. 97.114.84.101.120.116 = 53:65:74:75:70:43:6C enterprises.1031.1.1.1.3.1.1.11.83.78.77.80.95.115.116.97.116. 117.115 = 53:4E:4D:50:5F:73:74:61:74:75:73

If the sub-agent is not running, the output from nhSnmpTool should be similar to the following example:
>

nhSnmpTool -n -o .1.3.6 -p 1161 192.124.15.211 # 192.124.15.211:.1.3.6 targetTxt = dod sysDescr.0 = PEER Networks, a division of BMC Software, Inc., PATROL(R) SNMP Toolkit, OptiMaster Release 1 sysObjectID.0 = 1.3.6.1.4.1.442.1.1.1.9.2 sysUpTime.0 = 2d 0:23:32.97 sysContact.0 = sysName.0 = costello sysLocation.0 = sysServices.0 = 72 snmpInPkts.0 = 13620 snmpOutPkts.0 = 13620 snmpInBadVersions.0 = 0 snmpInBadCommunityNames.0 = 0 ... enterprises.4.4.2.1.4.7.1.3.6.1.2.1.11.2147483646 = 1 enterprises.4.4.2.1.4.8.1.3.6.1.4.1.4.4.2147483647 = 1

2.

If you prefer to use BMC PATROL tools to verify the sub-agent installation, issue the appropriate PATROL Script Language (PSL) commands from the BMC PATROL Developer Console. For example, to determine if the BMC PATROL sub-agent is active, enter:
>

PSL print(snmp_agent_config());

To start the sub-agent if it is inactive, enter:

>

PSL print(snmp_agent_start());

You can also verify the sub-agent installation from the PATROL Developer Console by right-clicking the icon representing your server and selecting KM Commands SNMP Reconfig.

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Troubleshooting the BMC Installation

Troubleshooting the BMC PATROL Knowledge Modules Installation

The BMC PATROL Knowledge Modules (KMs) enable Network Health to access the information collected by the BMC PATROL Agent about BMC servers in your network. You must install all of the KMs listed for your servers operating system in the BMC Server Requirements section on page 2. If Network Health cannot discover a BMC server in your network, one or more of the KMs on the BMC server might be missing or improperly installed.

Troubleshooting the KMs Installation To troubleshoot the BMC PATROL KMs installation:
1.

Use the nhSnmpTool command to verify that the BMC PATROL KMs are installed on the BMC server. The nhSnmpTool command returns a list of the installed KMs in hexadecimal values. For your reference, the following example translates the hexadecimal values into strings and includes the strings in brackets at the end of each line.

>

nhSnmpTool -n -o .1.3.6.1.4.1.1031.1.1.1.6.1.1 -p 1161 192.124.15.211 # 192.124.15.211:.1.3.6.1.4.1.1031.1.1.1.6.1.1 targetTxt = enterprises.1031.1.1.1.6.1.1 enterprises.1031.1.1.1.6.1.1.0 = 53:4F:4C:41:52:49:53 [SOLARIS] enterprises.1031.1.1.1.6.1.1.1 = 55:53:45:52:53 [USERS] enterprises.1031.1.1.1.6.1.1.2 = 53:57:41:50 [SWAP] enterprises.1031.1.1.1.6.1.1.3 = 53:4D:50 [SMP] enterprises.1031.1.1.1.6.1.1.4 = 53:45:43:55:52:49:54:59 [SECURITY] enterprises.1031.1.1.1.6.1.1.5 = 50:52:4F:43:45:53:53 [PROCESS] enterprises.1031.1.1.1.6.1.1.6 = 50:52:49:4E:54:45:52 [PRINTER] enterprises.1031.1.1.1.6.1.1.7 =50:41:54:52:4F:4C:41:47:45:4E:54 [PATROLAGENT] enterprises.1031.1.1.1.6.1.1.8 = 50:41:54:52:4F:4C [PATROL] enterprises.1031.1.1.1.6.1.1.9 = 4E:46:53 [NFS] enterprises.1031.1.1.1.6.1.1.10 = 4E:45:54:57:4F:52:4B [NETWORK] enterprises.1031.1.1.1.6.1.1.11 = 4D:45:4D:4F:52:59 [MEMORY] enterprises.1031.1.1.1.6.1.1.12 = 4C:4F:47 [LOG] enterprises.1031.1.1.1.6.1.1.13 = 4B:45:52:4E:45:4C [KERNEL] enterprises.1031.1.1.1.6.1.1.14 = 46:49:4C:45:53:59:53:54:45:4D [FILESYSTEM] enterprises.1031.1.1.1.6.1.1.15 = 44:49:53:4B [DISK] enterprises.1031.1.1.1.6.1.1.16 = 43:50:55 [CPU] enterprises.1031.1.1.1.6.1.1.17 = 43:4F:4C:4C:45:43:54:4F:52:53 [COLLECTORS] 2.

If the BMC PATROL KMs are not installed on the BMC server, install them by doing one of the following: Preload the KMs. For instructions, refer to the Setting Up the BMC PATROL Agent to Preload the KMs section, next. Install from the PATROL Developer Console. For instructions, refer to the Installing KMs from the BMC PATROL Developer Console section on page 8.

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Discovering BMC PATROL Agents at Different Port Numbers

Setting Up the BMC PATROL Agent to Preload the KMs To set up the BMC PATROL Agent to preload the KMs:
1. 2. 3. 4. 5. 6.

Start the BMC PATROL Developer Console. Right-click the icon representing the BMC server you want to discover and select Development Agent Configuration. Double-click AgentSetup. Double-click PreloadedKMs. Double-click Replace. Do one of the following: On Windows NT, enter:
"NT_CACHE,NT_CPU,NT_LOGICAL_DISKS,NT_MEMORY,NT_NETWORK,NT_SERVER"

On UNIX, enter:
"CPU,DISK,FILESYSTEM,MEMORY,NETWORK,SWAP,USERS" 7. 8. 9.

Click OK. Select Tools Apply Configuration and save the file. Close the Wpconfig dialog box and save the configuration.

Installing KMs from the BMC PATROL Developer Console To install the KMs from the BMC PATROL Developer Console:
1. 2. 3.

Start the BMC PATROL Developer Console. Double-click the icon representing the BMC server you want to discover. Double-click one of the KMs required for your operating system. For example, on Windows NT click NT_MEMORY or on UNIX click MEMORY. Double-click a variable and verify that data is being collected for that variable. Repeat steps 3 and 4 for each KM required for your operating system. For a list of the KMs you must install, refer to the BMC Server Requirements section on page 2.

4. 5.

Discovering BMC PATROL Agents at Different Port Numbers

The BMC PATROL SNMP Agent is assigned to port number 1161 by default. The Network Health installation sets an environment variable named NH_DISCOVER_SERVER_PORTS to 1161 by default to discover server elements at port 1161. If the BMC PATROL Agents in your network use ports other than 1161, you must modify the NH_DISCOVER_SERVER_PORTS environment variable to add or change the port numbers your server agents are using.

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Discovering BMC PATROL Agents at Different Port Numbers

Modifying NH_DISCOVER_SERVER_PORTS on Windows NT

To modify the NH_DISCOVER_SERVER_PORTS environment variable on a Windows NT system:
1.

On the taskbar, click Start Settings Control Panel. The Control Panel appears. Double-click System. The System Properties dialog box appears. Select the Environment tab. Under System Variables, select NH_DISCOVER_SERVER_PORTS. In the Value box, add or modify the port numbers your server agents are using. To add ports to the NH_DISCOVER_SERVER_PORTS environment variable, type the port numbers after the 1161 entry, separating each port number with a space. For example, the following entry adds ports 1162 and 1163 to the server ports that Network Health queries during a discover process:
1161 1162 1163

2.

3. 4. 5.

6. 7. 8.

Click Set. Click OK in the System Properties dialog box and close the Control Panel. Do one of the following: Stop the Network Health server, close the console, and then reopen the console to use the new port value in the Discover dialog box. Stop and restart the Network Health server to use the new port value in scheduled discover processes.

9.

Run the discover process again.

Modifying NH_DISCOVER_SERVER_PORTS on UNIX

To modify the NH_DISCOVER_SERVER_PORTS environment variable on a UNIX system:
1.

Open the nethealthrc.sh file in any text editor. The nethealthrc.sh file is located in the Network Health installation directory. Locate the following line in the nethealthrc.sh file:
export NH_DISCOVER_SERVER_PORTS; NH_DISCOVER_SERVER_PORTS="1161"

2.

3.

Edit the NH_DISCOVER_SERVER_PORTS environment variable to add or modify the port numbers your server agents are using. To add ports to the NH_DISCOVER_SERVER_PORTS environment variable, type the port numbers after the 1161 entry, separating each port number with a space. Make sure the port numbers are enclosed by double quotation marks. For example, the following entry adds ports 1162 and 1163 to the server ports that Network Health queries during a discover process:

export NH_DISCOVER_SERVER_PORTS; NH_DISCOVER_SERVER_PORTS="1161 1162 1163"

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Performance Considerations

4. 5.

Save and close the nethealthrc.sh file. Run the discover process again.

Performance Considerations
There is an additional performance cost when Network Health polls BMC servers. To find the current value of the indexes for the BMC variables, the poller must send and process many SNMP requests. The extra processing occurs on the first poll to the BMC server or when the BMC PATROL Agent is restarted. The first poll occurs after a BMC server is discovered or after the poller is restarted. For subsequent polls or when Network Health polls multiple BMC servers, there is no performance impact.

Known Issues with BMC PATROL Agent for Windows NT

This section describes known issues when Network Health discovers BMC servers that have the PATROL Agent for Windows NT software installed.

Discover Process Finds Both Loopback and Network Interfaces

Network Health discovers and collects data from the BMC servers loopback interface as well as from its network interfaces. The BMC PATROL Agent for Windows NT does not provide a network interface description or network interface type, so the discover process cannot identify the loopback interface. Collecting data from both the loopback and network interfaces might result in higher network traffic counts. If you do not want to include the BMC servers loopback interface in Network Health reports, you must disable polling for the loopback interface element in the Poller Configuration dialog box. For instructions on modifying elements, refer to the information about managing the poller configuration in the Network Health User Guide.

10

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Known Issues with BMC PATROL Agent for UNIX

Known Issues with BMC PATROL Agent for UNIX

This section describes known issues when Network Health discovers BMC servers that have the PATROL Agent for UNIX software installed.

How Network Health Calculates Network Bytes

The BMC PATROL Agent for UNIX provides information about network packets during the discovery process. It does not provide information about the number of network bytes. To calculate the number of network bytes, Network Health multiplies the number of network packets by 725.

Discover Process Finds Remote File Partitions and CDs

Network Health discovers and collects data for remotely mounted file partitions and CD-ROM drives on BMC servers that have the PATROL Agent for UNIX installed. If you do not want to include the remote file partitions and CD-ROMs in Network Health reports, you can configure the BMC PATROL Agent software to prevent the discover process from finding these elements. To configure the BMC PATROL Agent software to prevent discovery of remote file partitions and CD-ROMs:
1. 2. 3.

Open the BMC PATROL Developer Console. Select Knowledge Module Admin UNIX3 FILESYSTEM Application Edit FILESYSTEM Exclusion List. Select all of the following in the FILESYSTEM Exclusion List: Ignore NFS Filesystems Ignore CD-ROM Filesystems Ignore proc Filesystems

4.

In Network Health, run the discover process on your BMC servers. Network Health does not discover remotely mounted file partitions or CD-ROM drives on the BMC servers. For instructions on running the discover process, refer to the Network Health User Guide.

If you do not want to configure the BMC PATROL Agent to prevent discovery of remote partitions and CD-ROMs, you must disable polling for the elements you do not want to include in Network Health reports. You can disable polling for elements in the Poller Configuration dialog box. For instructions on managing the poller configuration, refer to the Network Health User Guide.

Application Brief: T6-9901-0001

11

USING THE BMC PATROL SNMP AGENT

Network Health Variables Reference

Discover Process Does Not Set Interface Speeds

When Network Health discovers BMC servers that have the PATROL Agent for UNIX installed, the discover process does not set the interface speed for the BMC server interfaces. Since the BMC PATROL Agent for UNIX does not provide speed values for interfaces, Network Health cannot determine this information during discovery. As a result, Network Health uses a default speed value of 10 MB. If 10 MB is not the correct speed for your BMC server interfaces, you can change the speed for these elements in the Poller Configuration dialog box. For instructions on modifying elements, refer to the information about managing the poller configuration in the Network Health User Guide.

How the BMC PATROL Agent Reports Virtual Memory Used

The BMC PATROL Agent for UNIX includes the reserve paging space in its count of virtual memory used. The reserve paging space is the amount of paging space other running processes might need that has not yet been allocated from one of the other paging areas. As a result of including the reserve paging space in its count, the BMC PATROL Agent might report a higher virtual memory used count than other server agents that do not include the reserve paging space in their count.

Network Health Variables Reference

This section provides tables that show how Network Health database variables map to BMC PATROL Agent variables for the following server element types: Servers Server CPUs Server partitions Server disks Each table lists the Network Health variable, the unit of measure if applicable, and the corresponding variables for the Windows NT BMC PATROL Agent and the UNIX BMC PATROL Agent. If a particular Network Health variable does not have a corresponding BMC variable, the table indicates that the variable is not supported.

12

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Network Health Variables Reference

Servers
The following table lists Network Health variables for servers and the corresponding BMC PATROL Agent variables on Windows NT and UNIX.
Network Health variable Units Pages paged in Total bytes (in + out) Pages paged out Pages swapped in Pages swapped out File cache hits File cache misses Pages Bytes Pages Windows NT BMC Agent variable UNIX BMC Agent variable MEMmemPagesInputPerSec Aggregated from net element MEMmemPagesOutputPerSec Not supported Not supported CACcachCopyReadsPerSec MEMPageIn Aggregated from net element MEMPageOut Not supported Not supported Not supported

(CACcachCopyReadsPerSec/ Not supported CACcachCopyReadHitsPercent)* (1-CACcachCopyReadHitsPercent) Not supported Not supported MEMmemPageFaultsPerSec Calculated from CPUprcrProcessorTimePercent/ numCPU Calculated from CPUprcrProcessorTimePercent^2/ numCPU SVRsvrServerSessions SVRsvrSessionsErroredOut + SVRsvrSessionsForcedOff + SVRsvrSessionsTimedOut Not supported Not supported Not supported Not supported Not supported Calculated by Network Health Calculated by Network Health Calculated by Network Health NETniPktsRcvdErrors + NETniPktsOutboundErrors + <discards> Discards not supported Not supported Not supported MEMRFault Calculated from CPUCpuUtil/numCPU Calculated from CPUCpuUtil^2/numCPU USRNoUser Not supported

Total physical memory Physical memory used Page faults Average CPU utilization

Bytes Bytes CpuSec

CPU imbalance

CpuSec

Active connections Dropped connections

Total virtual memory Virtual memory used Small comm buffers dropped Total large comm buffers Large comm buffers used Time available Time reachable Total time Total errors

Bytes Bytes Seconds Seconds Seconds

SWPTotSwapSize SWPTotSwapSize SWPTotSwapFreeSpace Not supported Not supported Not supported Calculated by Network Health Calculated by Network Health Calculated by Network Health NETInErrPerc + NETOutErrPerc + <discards> Discards not supported

Application Brief: T6-9901-0001

13

USING THE BMC PATROL SNMP AGENT

Network Health Variables Reference

Network Health variable Units Total discards Total incoming packets Total incoming bytes Total outgoing packets Total outgoing bytes Packets Bytes Packets Bytes

Windows NT BMC Agent variable UNIX BMC Agent variable Not supported NETniPktsRcvdPerSec NETniBytesRcvdPerSec NETniPktsSentPerSec NETniBytesSentPerSec Not supported NETPacketsIn NETPacketsIn * constant NETPacketsOut NETPacketsOut * constant

Server CPUs
The following table lists Network Health variables for server CPUs and the corresponding BMC PATROL Agent variables on Windows NT and UNIX.
Network Health variable Units CPU utilization CpuSec Windows NT BMC Agent variable UNIX BMC Agent variable CPUprcrProcessorTimePercent CPUCpuUtil

Server Partitions
The following table lists Network Health variables for server partitions and the corresponding BMC PATROL Agent variables on Windows NT and UNIX.
Network Health variable Units Partition storage capacity Bytes Windows NT BMC Agent variable UNIX BMC Agent variable LDldFreeMegabytes (number of MB of unallocated disk space) / LDldFreeSpacePercent (ratio of free space available on logical disk to total usable disk space) Storage capacity LDldFreeMegabytes Not supported Not supported Not supported Not supported FSUsedSpace + FSAvailableSpace

Partition storage used Partition allocation failures Partition reads Partition writes Partition reads plus writes

Bytes

FSUsedSpace Not supported Not supported Not supported Not supported

14

Application Brief: T6-9901-0001

USING THE BMC PATROL SNMP AGENT

Network Health Variables Reference

Server Disks
The following table lists Network Health variables for server disks and the corresponding BMC PATROL Agent variables on Windows NT and UNIX.
Network Health variable Units Disk storage capacity Disk storage used Disk faults Disk reads Bytes Bytes Windows NT BMC Agent variable Not supported Not supported Not supported Not supported UNIX BMC Agent variable Not supported Not supported Not supported DSKRead (number of read requests) Not supported on Solaris and HP-UX Disk writes Not supported DSKWrite (number of write requests in KB per second) Not supported on Solaris and HP-UX Disk reads & writes Bytes Not supported DSKReadWrite (number of read/write requests) DSKBps (number of read/write requests in KB per second) Not supported on Solaris and HP-UX

Application Brief: T6-9901-0001

15