snmp system management agent openvms version 4 · openvms vax, alpha and itanium systems to network...

COMTEK NMServer for OpenVMS

2006 COMTEK Services, Inc. User’s Guide

User’s Guide

NMServer SNMP System Management Agent

for OpenVMS Version 4.0

COMTEK Services, Inc. NMServer SNMP Products


2006 COMTEK Services, Inc. i User’s Guide

NMServer for OpenVMS

Product Data

Date: February 2006 NMServer Version: 4.0 OpenVMS Version Required: 5.5 or higher

NMServer also available for

IBM OS/400 and Stratus VOS


2006 COMTEK Services, Inc. ii User’s Guide

Copyright © 2006 COMTEK Services Inc. This manual and any examples contained herein are provided "as is" and are subject to change without notice. COMTEK makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. COMTEK shall not be liable for any errors or for incidental or consequential damages in connection with the furnishing, performance or use of this manual or the examples herein.

The following are COMTEK trademarks: NMServer, NMServer Monitor, NM∗ Server, NM∗ Master, NM∗ SysMgr, NM∗ TrpMgr, NM∗ Console, NMOpcom, NM∗ Opcom and NM∗ VmsMon

The following are third-party trademarks: HP, OpenView, NNM, Network Node Manager, Insight Manager, Compaq, DEC, Alpha, Itanium, OpenVMS and VAX are trademarks of Hewlett-Packard Company. IBM, NetView/6000, AS/400 and OS/400 are trademarks of International Business Machines Corporation. Stratus and VOS are trademarks of Stratus Computer, Inc.

All other trademarks and registered trademarks are the property of their respective holders.

COMTEK Contact Information For sales, technical or support services on NMServer, contact:

COMTEK Services, Inc. 101 South Whiting Street Suite 300 Alexandria, VA 22304

Sales: (603) 881-9556 Support: (703) 751-3997 FAX: (603) 881-5504 [email protected] [email protected] www.comtekservices.com

mailto:[email protected]

mailto:[email protected]

http://www.comtekservices.com/


2006 COMTEK Services, Inc. iii User’s Guide

Table of Contents Overview of NMServer for OpenVMS .............. 1

OpenVMS NMServer Product Suite ....................... 1 Network Manager Compatibility .................................... 3 NM∗ Master Agent Description (DPI Only)..................... 3 NM∗ SysMgr Subagent Description ............................... 4 NM∗ TrpMgr Subagent Description................................ 4 NM∗ Console Subagent Description .............................. 4 NM∗ Opcom Subagent Description................................ 4 NM∗ VmsMon Subagent Description ............................. 5

Product Installation........................................... 7

Sample Installations ............................................... 8 Sample DPI Installation ................................................ 9 Sample eSNMP Installation ........................................ 11 Changing NMServer System Logical Names.............. 13 Directory Contents ...................................................... 13

License Keys........................................................ 15 Customize Configuration Files.............................. 16

Setting up the Process Configuration Files................. 16 Setting up the Community File (DPI Only) .................. 17 Setting up the Trap Destination File (DPI Only).......... 17 Setting up the Filter Files ............................................ 18 Setting up the Critical Data Files................................. 18

Running NMServer for OpenVMS........................... 18 Process Startup Symbols............................................ 18 Process Startup .......................................................... 19 Running NMServer on a Port Other than 161............. 19 Reinitializing NMServer Processes ............................. 20 Stopping NMServer Processes................................... 20

Command Line SNMP Manager........................... 20


2006 COMTEK Services, Inc. iv User’s Guide

Sample Manager Commands ..................................... 21

NMServer Master Agent (DPI Only)................ 23

NM∗ Master Operation .......................................... 23 Privileges .................................................................... 23 Required Logical Names............................................. 24 Process Startup .......................................................... 25 Process Reinitialization............................................... 25

NM∗ Master Process Configuration Files .............. 25 COMTEK$MASTER_CONFIG Configuration File ............ 25 COMTEK$MASTER_COMM Community File .................. 29 COMTEK$MASTER_TRAP Trap Destination File...... 31

NM∗ Master MIB Objects ...................................... 31 MIB-II .......................................................................... 31 Master Agent Objects in NMSERVERVMS.MIB File .. 32

NM∗ Master Traps................................................. 33 SNMP Generic Traps.................................................. 33 Enterprise Specific Traps............................................ 34

NM∗∗∗∗ SysMgr Subagent..................................... 35

NM∗ SysMgr Operation ......................................... 35 Privileges .................................................................... 35 Required Logical Names............................................. 35 Process Startup .......................................................... 37 Process Reinitialization............................................... 38

NM∗ SysMgr Process Configuration Files ............. 38 COMTEK$SYSMGR_CONFIG Configuration File............. 38 COMTEK$SYSMGR_CRIT Critical Processes ........... 56 COMTEK$SYSMGR_CRITDSK Critical Disks............ 57 COMTEK$SYSMGR_CRITQUEUE Critical Queues .. 58 COMTEK$SYSMGR_FILTER Operator Message Filters 59

NM∗ SysMgr MIB Objects ..................................... 60

NM∗ SysMgr Traps................................................ 67 Enterprise Specific Traps............................................ 67

NM∗∗∗∗ TrpMgr Subagent ..................................... 71

NM∗ TrpMgr Subagent Operation.......................... 71


2006 COMTEK Services, Inc. v User’s Guide

Privileges .................................................................... 71 Required Logical Names............................................. 71 Process Startup .......................................................... 72 Process Reinitialization............................................... 73

NM∗ TrpMgr Process Configuration Files.............. 73 COMTEK$TRPMGR_CONFIG Configuration File ...... 73 COMTEK$TRPMGR_FILTER User Trap Filters ......... 76

NM∗ TrpMgr MIB Objects ...................................... 76

NM∗ TrpMgr Traps ................................................ 77 Enterprise Specific Traps............................................ 78

Example: NM∗ TrpMgr Mailbox Interface............... 78 DCL Command Procedure ......................................... 78 SEND_SEVERITY_TRAP.COM Command Procedure78 C Program Example.................................................... 79

NM∗∗∗∗ Console Subagent ................................... 81

NM∗ Console Subagent Operation ........................ 81 Privileges .................................................................... 81 Required Logical Names............................................. 82 Process Startup .......................................................... 82 Process Reinitialization............................................... 83

Remote Console Command Format ..................... 83

NM∗ Console Process Configuration Files ............ 84 COMTEK$CONSOLE_CONFIG Configuration File .... 84

NM∗ Console MIB Objects .................................... 87

NM∗ Console Traps............................................... 88 Enterprise Specific Traps............................................ 88

NM∗∗∗∗ Opcom Subagent ..................................... 91

NM∗ Opcom Subagent Operation.......................... 91 Privileges .................................................................... 91 Required Logical Names............................................. 91 Process Startup .......................................................... 92 Process Reinitialization............................................... 93

NM∗ Opcom Process Configuration Files.............. 93 COMTEK$NMOPCOM_CONFIG Configuration File .. 93 COMTEK$NMOPCOM_FILTER Opcom Trap Filters103


2006 COMTEK Services, Inc. vi User’s Guide

NM∗ Opcom MIB Objects .................................... 104

NM∗ Opcom Traps .............................................. 105 Enterprise Specific Traps.......................................... 105

NM∗∗∗∗ VmsMon Subagent ................................ 107

NM∗ VmsMon Subagent Operation ..................... 107 Privileges .................................................................. 107 Required Logical Names........................................... 108 Process Startup ........................................................ 108 Process Reinitialization............................................. 109

NM∗ VmsMon Process Configuration Files ......... 109 COMTEK$VMSMON_CONFIG Configuration File ... 109

NM∗ VmsMon MIB Objects ................................. 115

NM∗ VmsMon Traps............................................ 121 Enterprise Specific Traps.......................................... 121

NMServer Traps............................................. 123

Resending Traps ................................................ 123 Trap Throttling.................................................... 124

Web Interface for NMServer for OpenVMS . 125

Description ......................................................... 125 NMServer Group....................................................... 125 NMServer Monitor Group.......................................... 126

System Requirements ........................................ 127 Installation Instructions....................................... 127 Configuration Options......................................... 127

NMServer MIB................................................ 129


2006 COMTEK Services, Inc. 1 User’s Guide

1 Overview of NMServer for OpenVMS

OpenVMS NMServer Product Suite NMServer for OpenVMS is a Simple Network Management Protocol (SNMP) agent. It provides monitoring and management data for OpenVMS VAX, Alpha and Itanium systems to network managers, such as NetView or OpenView. NMServer for OpenVMS also provides a web interface for web access to NMServer system management data (See Chapter 10 of this manual for details). SNMP is an Internet Standard Protocol designed specifically for management of multi-vendor networks. Since SNMP was developed in 1988 it has become the de facto standard, and is used to manage thousands of networks worldwide.

NMServer for OpenVMS is implemented as an extensible SNMP agent. That is, NMServer for OpenVMS contains an optional single master agent application and multiple subagent applications that run on a single system. The default configuration of NMServer for OpenVMS utilizes a master agent supplied with the NMServer package that communicates with subagents using the Distributed Protocol Interface (DPI). As an alternative to using the NMServer supplied DPI master agent, NMServer for OpenVMS may be configured to run as a set of eSNMP subagents, using the eSNMP master agent supplied with HP’s TCP/IP Services (UCX). The NMServer eSNMP subagents may be run along with other HP or user supplied eSNMP subagents. Consult the current NMServer for OpenVMS product README.txt for information on eSNMP restrictions and prerequisite software.

NMServer for OpenVMS is designed to permit subagents to be added or removed as required in each operating environment. All subagents operate independently of one another and may be stopped and started without restarting the master agent.

The data that is gathered and maintained by NMServer for OpenVMS is represented in a set of Management Information Base (MIB) specifications. The MIBs supported by NMServer for OpenVMS contain information about system resource utilization, CPU utilization, disk



utilization, process statistics, critical processes, disk, and queue statistics, as well as hardware errors.

NMServer for OpenVMS uses more than 40 different types of traps to instantly alert network managers of critical situations on the managed system. Traps are sent for the following conditions:

• disk, swap file, page file, CPU and interrupt usage exceed user specified thresholds

• certain status changes in disks, shadow sets, queues, queue entries, and process MWAIT states

• excessive disk operations per second • CPU, memory, disk, and bus errors • user specified mission critical process is not running • opcom message • user text message, with optional severity coding • agent/subagent cold start, warm start, and process termination • remote console command results

Trap messages, sent by NMServer for OpenVMS, are assigned sequence numbers and are retained in internal tables. If the network manager does not receive a trap message, a retransmission of the trap may be requested.

NMServer for OpenVMS consists of the following components:

• NM∗ Master – DPI master agent (optional) • NM∗ SysMgr – system management subagent • NM∗ TrpMgr – user trap manager subagent • NM∗ Console – remote console subagent • NM∗ Opcom – operator communications (opcom) subagent • NM∗ VmsMon – VMS Monitor subagent

Each of the subagents has its own MIB and is independent of the other subagents. Some functionality is duplicated across subagents. For example, the NM∗ SysMgr subagent provides the same opcom monitoring functions as the NM∗ Opcom subagent. Only one of these subagents should be used at a time. When NMServer is purchased, the purchaser selects the subagents that are necessary to his environment. License keys issued by COMTEK Services are valid only for the subagents purchased. If the purchaser decides at a later time to add additional subagents, a new license key can be issued.



Network Manager Compatibility NMServer for OpenVMS is and SNMP agent and is therefore compatible with SNMP-based network managers. Tools to assist in the integration of NMServer for OpenVMS with HP OpenView Network Node Manager are provided with NMServer. Consult the OpenView readme provided with this product for more information.

NM∗∗∗∗ Master Agent Description (DPI Only) NM∗ Master performs all communications between the SNMP manager and the DPI NMServer subagents. The NM∗ Master agent converses with the SNMP manager in SNMP packets and uses DPI packets for communications with all subagents.

The NM∗ Master agent supports the system group of MIB-II, the DPI20 MIB, the Subagent MIB and the COMTEK NM∗ Master Agent MIB. Refer to the NM∗ Master MIBs section of Chapter 3 for more details. Community strings and trap destinations identifying SNMP manager addresses and access privileges are also maintained within NM∗ Master.

When installing NMServer for OpenVMS on an Alpha system in certain configurations, the installer has the option to install NMServer to use either an TCP/IP vendor-supplied SNMP master agent or NMServer’s own SNMP master agent. This selection merely identifies the extensible agent protocol and the master agent that is to be used between the subagents and the SNMP manager. If your environment permits you to use NMServer with the TCP vendor-supplied master agent, you will be able to you will be able to run any TCP vendor-supplied or HP supplied subagents (such as Insight Management Agents) along with NMServer. NMServer’s SNMP master agent NM∗ Master uses the DPI extensible agent protocol. The MIB data that is instrumented by the NM∗ SysMgr, NM∗ TrpMgr, NM∗ Console, NM∗ Opcom and NM∗ VmsMon subagents is the same, regardless of the choice of DPI or eSNMP as the extensible agent protocol. Consult the product Readme for information on which configuration is compatible with your environment.

By default, NM∗ Master uses UDP port 161, the standard SNMP port, to receive messages from SNMP managers. Any other agent on the system that accesses port 161 must be disabled. Alternatively, NM∗ Master may be directed to use a port other than 161, thereby allowing NMServer to coexist with another SNMP agent. See Chapter 2 for more information.



NM∗∗∗∗ SysMgr Subagent Description The NM∗ SysMgr subagent monitors system management data. This subagent tracks system performance, system resource utilization, process statistics, queue information, operator communications (opcom) and error information. Traps are generated when system conditions exceed user-defined limits.

NM∗ SysMgr supports the NM∗ SysMgr MIB and NM∗ SysMgr Trap MIB. Chapter 4 of this manual provides a detailed description of the NM∗ SysMgr subagent.

NM∗∗∗∗ TrpMgr Subagent Description NM∗ TrpMgr provides a mechanism for sending user data as trap messages to the SNMP manager. User text messages can generate either generic or severity coded traps. NM∗ TrpMgr reads user text messages from an OpenVMS mailboxes and converts the text into a trap message. The trap message is then sent, via the DPI or eSNMP master agent, to the SNMP manager(s). Chapter 5 of this manual contains a description of the NM∗ TrpMgr subagent, an example C program and an example command procedure for writing data to the NM∗ TrpMgr mailbox.

NM∗ TrpMgr supports the NM∗ TrpMgr MIB and NM∗ TrpMgr Trap MIB. Refer to Chapter 5 for more details.

NM∗∗∗∗ Console Subagent Description The NM∗ Console subagent allows OpenVMS DCL commands to be entered remotely. Commands are sent to NM∗ Console as SNMP set-requests. NM∗ Console starts a detached process to execute each command entered. The number of commands that may be active simultaneously is configurable. The results of each command are written to a file that is transmitted as a series of traps to the SNMP manager, with each line of the file being sent as a separate trap. Once the entire results file has been transmitted, it is deleted.

NM∗ Console supports the NM∗ Console MIB and NM∗ Console Trap MIB. Refer to Chapter 6 of this manual for more information on the NM∗ Console subagent.

NM∗∗∗∗ Opcom Subagent Description NM∗ Opcom provides a mechanism for sending operator communication (opcom) messages as SNMP trap messages to SNMP managers. NM∗ Opcom receives opcom messages from the OpenVMS OPCOM



process via an OpenVMS mailbox and converts the text into a trap message. The trap message is then sent, via the DPI or eSNMP master agent, to the SNMP manager(s).

NM∗ Opcom supports the NMOpcom MIB. Chapter 7 of this manual contains a detailed description of the NM∗ Opcom subagent.

NM∗∗∗∗ VmsMon Subagent Description NM∗ VmsMon provides SNMP accessibility to VMS MONITOR Utility data. NM∗ VmsMon collects system performance and utilization data on the following classes of MONITOR data: modes, file_system_cache, FCP, I/O, page, DECnet, lock, dlock, cluster, MSCP_server, states, system, rlock and timer.

NM∗ VmsMon supports the NMVmsMon MIB. Chapter 8 of this manual contains a detailed description of the NM∗ VmsMon subagent.



2 Product Installation

The following steps are required to install and configure NMServer for OpenVMS in a new operating environment. Consult the product README.txt file for the current prerequisites and installation procedures.

1. Download the NMSERVERVMS.zip file from COMTEK's web site.

2. Unzip the product on your PC. This will create a directory called vms.

3. Change directory to vms\v4.0.

4. Within this directory there will be the following directories: Agent, CIM, Concord, Doc, MIB and OpenView.

Agent: contains the NMServer for OpenVMS software installation kit.

CIM: contains tools for use with HP Insight Manager 7

Concord: contains tools for use with Concord's eHealth

Doc: contains NMServer for OpenVMS User's Guide and Getting Started Guide Set the FTP file transfer mode to BINARY before transferring .pdf files to another system.

MIB: contains MIB file that must be loaded into your SNMP manager. The NMSERVERVMS.MIB file should be transferred as ASCII. Load/compile the MIB file into your SNMP manager according to your manager's instructions. See the final section of this Readme for information on MIB dependencies.

5. Set the FTP file transfer mode to BINARY.

6. Change directory to Agent

7. FTP the zipped installation kit NMSERVER040.ZIP to your target OpenVMS system.

8. FTP the appropriate unzip utility to your target OpenVMS system (UNZIP.VAX_EXE for VAX architecture, UNZIP.ALPHA_EXE



for Alpha architecture, or UNZIP.I64_EXE for Itanium architecture).

9. On the target OpenVMS system, create a foreign command for unzipping the installation kit. (The following commands are case insensitive.)

On VAX:

$ unzip = "$ <device>:[<directory>]UNZIP.VAX_EXE"

On Alpha:

$ unzip = "$ <device>:[<directory>]UNZIP.ALPHA_EXE"

On Itanium:

$ unzip = "$ <device>:[<directory>]UNZIP.IA64_EXE"

Where <device> and <directory> identify the disk and directory location of the transferred unzip utility.

10. On the target OpenVMS system, unzip the NMSERVER040.ZIP file. This will produce a NMSERVER040.A installation kit.

$ unzip "-x" nmserver040.zip

11. On the target OpenVMS system, run VMSINSTAL to install NMServer for OpenVMS:

$ @sys$update:vmsinstal nmserver <device>:[<directory>]

Where <device> and <directory> identify the disk name and directory that contain the unzipped NMSERVER040.A installation kit.

Sample Installations NMServer for OpenVMS uses the OpenVMS VMSINSTAL utility for product installation. The VMSINSTAL installation kit performs the following actions:

1. Creates the COMTEK_ROOT system logical name, which identifies the disk/directory where the NMServer software is to be installed and run.

2. Creates the COMTEK$SNMP account. All NMServer processes are run under this account.

3. Installs the software on the target system.



4. Inquires about the TCP/IP product and version. May then inquire if DPI or eSNMP version of the product is to be installed (eSNMP is only supported on version certain version of TCP/IP products). Consult the product README.txt file for current limitations on eSNMP.

5. Builds the appropriate executable images.

6. Queries the installer for NMServer license key information and, when installing the DPI version, the SNMP community and trap destination data.

7. Notifies the installer of any additional actions that must be performed. Before the DPI version of NMServer for OpenVMS software is started, either the default SNMP agent supplied with the host system’s TCP/IP product (TCPIP Services, UCX, MultiNet, TCPware or Pathways) must be disabled or NMServer must be started on a port other than 161.

8. Lists the NMServer startup commands that may be added to the system startup procedures.

Two sample installations appear below. The first sample installation demonstrates installing the DPI version of NMServer for OpenVMS. The second demonstrates installing the eSNMP version of the NMServer product.

Sample DPI Installation @sys$update:vmsinstal nmserver sys$sysdevice:[nmserver] OpenVMS AXP Software Product Installation Procedure V7.3-2 It is 17-FEB-2006 at 17:25. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: TCPIP$FTP_1 TCPIP$SNMP_1 TCPIP$HR_MIB TCPIP$OS_MIBS * Do you want to continue anyway [NO]? yes * Are you satisfied with the backup of your system disk [YES]? yes The following products will be processed: NMSERVER V4.0 Beginning installation of NMSERVER V4.0 at 17:25 %VMSINSTAL-I-RESTORE, Restoring product save set A ...



%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. NMServer V4.0 system installation * Do you want to purge files replaced by this installation [YES]? yes * Device and directory location of COMTEK_ROOT [SYS$SYSDEVICE:[000000]]: sys$sysdevice:[nmserver.40_dpi] * Account UIC value for COMTEK$SNMP account: [100,2] %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named COMTEK$SNMP. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier COMTEK$SNMP value [000100,000002] added to rights database %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named COMTEK$SNMP. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named COMTEK$SNMP. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named COMTEK$SNMP. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named COMTEK$SNMP. %UAF-I-MDFYMSG, user record(s) updated * What TCP/IP product is used on this system (TCPIP_Services, UCX, MultiNet, TCP ware or Pathways) [TCPIP_Services]: * Which NMServer subagent protocol should be installed (ESNMP or DPI) [ESNMP]: dpi * Do you want to enter a temporary license key now [YES]? yes * Enter the Temporary NMServer License Key value supplied by COMTEK: xxxxxxxxxxxxxx The following questions relate to setting up the values that NMServer will return when the SNMP manager requests the sysLocation and sysContact MIB-II variables. * Value for SNMP MIB-II system location (sysLocation) variable: your location * Value for SNMP MIB-II system contact (sysContact) variable: system contact Linking CONSOLE DPI... Linking MASTER DPI... Linking NMOPCOM DPI... Linking SYSMGR DPI... Linking TRPMGR DPI... Linking VMSMON DPI... Linking MANAGER... The following questions relate to setting up NMServer's community file. The community file contains information that identifies all of the SNMP managers that are authorized to send messages to NMServer. * Do you want to enter a community record now [YES]? yes * Enter case sensitive community string for SNMP manager: public * What is the network mask for this community [0.0.0.0]: 255.255.255.255 * What is the IP address for this community [0.0.0.0]: 192.168.10.131 * Enter privileges for this SNMP manager (read, write, none) [Read]: read Community: public Network Mask: 255.255.255.255 IP Address: 192.168.10.131 Privileges: read * Is this record correct [YES]? yes * Do you want to enter another community record [NO]? no The following questions relate to setting up NMServer's trap destination file. The trap destination file identifies all of the SNMP managers that are to receive SNMP traps from NMServer. * Do you want to enter a trap destination record now [YES]? yes * Enter case sensitive trap community string for traps to the SNMP manager: public * Enter IP address of SNMP manager where traps should be sent: 192.168.10.131 * Enter port number where traps should be sent to the SNMP manager [162]: 162 Community: public IP Address: 192.168.10.131 Port: 162 * Is this record correct [YES]? yes * Do you want to enter another trap destination record [NO]? no Notes:



* You may choose to edit the following files and tailor them to your requirements before starting NMServer. See the NMServer User's Guide for a description of each of these files. COMTEK$CONSOLE, COMTEK$NMOPCOM_CONFIG, COMTEK$SYSMGR_CONFIG, COMTEK$TRPMGR, COMTEK$VMSMON_CONFIG Define subagent configuration values. COMTEK$SYSMGR_FILTER, COMTEK$TRPMGR_FILTER, COMTEK$NMOPCOM_FILTER Add filter rules to filter out unwanted opcom and user trap messages. COMTEK$SYSMGR_CRITDSK, COMTEK$SYSMGR_CRITPROC, COMTEK$SYSMGR_CRITQUEUE Enter the names of disks, processes, and queues that have special monitoring requirements. Press return to continue... * NMServer may be run either on the standard SNMP port (161) or on another user-defined port. If run on the standard SNMP port, any agent (such as an agent that is supplied by a TCP/IP product) currently using this port must be disabled. * Use the following commands to disable the default TCPIP Services SNMP agent: TCPIP DISABLE SERVICE SNMP @SYS$MANAGER:TCPIP$SNMP_SHUTDOWN * After your configuration has been completed, add the following commands to your system startup files after startup of your tcp/ip product: $ DEFINE/SYSTEM/NOLOG COMTEK_ROOT DKA0:[NMSERVER.40_DPI.]/TRANS=CONCEAL $ !This MUST be after your call to TCPIP$STARTUP $ TCPIP DISABLE SERVICE SNMP $ @SYS$MANAGER:TCPIP$SNMP_SHUTDOWN $ @COMTEK_ROOT:[COMTEK$SNMP.COM]RUN_NMSERVER * If you wish for NMServer to use a port other than 161 for receiving data from the SNMP manager, place the port number as a parameter on the RUN_NMSERVER command line above. For example, to use port 4567, this command would appears as: $ @COMTEK_ROOT:[COMTEK$SNMP.COM]RUN_NMSERVER 4567 NOTE: Not all SNMP managers can be configured to use a port other then 161. Consult your SNMP manager's documentation. Press return to continue... Installation of NMSERVER V4.0 completed at 17:30 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]NMSERVER040.VMI_DATA VMSINSTAL procedure done at 17:31

Sample eSNMP Installation $ @sys$update:vmsinstal nmserver sys$sysdevice:[nmserver] OpenVMS AXP Software Product Installation Procedure V7.3-2 It is 17-FEB-2006 at 12:51. Enter a question mark (?) at any time for help.



%VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: TCPIP$FTP_1 TCPIP$SNMP_1 TCPIP$HR_MIB TCPIP$OS_MIBS * Do you want to continue anyway [NO]? yes * Are you satisfied with the backup of your system disk [YES]? yes The following products will be processed: NMSERVER V4.0 Beginning installation of NMSERVER V4.0 at 12:51 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. NMServer V4.0 system installation * Do you want to purge files replaced by this installation [YES]? yes * Device and directory location of COMTEK_ROOT [SYS$SYSDEVICE:[000000]]: sys$sysdevice:[nmserver.40_esnmp] * Account UIC value for COMTEK$SNMP account: [100,2] %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named COMTEK$SNMP. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier COMTEK$SNMP value [000100,000002] added to rights database %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named COMTEK$SNMP. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named COMTEK$SNMP. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named COMTEK$SNMP. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named COMTEK$SNMP. %UAF-I-MDFYMSG, user record(s) updated * What TCP/IP product is used on this system (TCPIP_Services, UCX, MultiNet, TCPware or Pathways) [TCPIP_Services]: * Which NMServer subagent protocol should be installed (ESNMP or DPI) [ESNMP]: esnmp * Do you want to enter a temporary license key now [YES]? yes * Enter the Temporary NMServer License Key value supplied by COMTEK: xxxxxxxxxxxxxxx Linking CONSOLE ESNMP... Linking NMOPCOM ESNMP... Linking SYSMGR ESNMP... Linking TRPMGR ESNMP... Linking VMSMON ESNMP... Linking MANAGER... Notes: * You may choose to edit the following files and tailor them to your requirements before starting NMServer. See the NMServer User's Guide for a description of each of these files. COMTEK$CONSOLE, COMTEK$NMOPCOM_CONFIG, COMTEK$SYSMGR_CONFIG, COMTEK$TRPMGR, COMTEK$VMSMON_CONFIG Define subagent configuration values. COMTEK$SYSMGR_FILTER, COMTEK$TRPMGR_FILTER, COMTEK$NMOPCOM_FILTER Add filter rules to filter out unwanted opcom and user trap messages. COMTEK$SYSMGR_CRITDSK, COMTEK$SYSMGR_CRITPROC, COMTEK$SYSMGR_CRITQUEUE Enter the names of disks, processes, and queues that have special monitoring requirements. Press return to continue...



* After your configuration has been completed, add the following commands to your system startup files after startup of your tcp/ip product: $ DEFINE/SYSTEM/NOLOG COMTEK_ROOT SYS$SYSDEVICE:[NMSERVER.40_ESNMP.]/TRANS=CONCEAL $ @COMTEK_ROOT:[COMTEK$SNMP.COM]RUN_NMSERVER Press return to continue... Installation of NMSERVER V4.0 completed at 12:55 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]NMSERVER040.VMI_DATA VMSINSTAL procedure done at 12:55

Changing NMServer System Logical Names The system logical names used by NMServer are defined in the file:

comtek_root:[comtek$snmp.com]nmserver_logicals.com

This command procedure is executed by the run_nmserver.com command procedure as a first step in starting the NMServer processes. In a clustered environment, it may prove useful to modify the supplied nmserver_logicals.com file so that certain logical names identify files that are node specific while all nodes share other files. One way to accomplish this is to add the following statement to the beginning of the nmserver_logicals.com file:

$ Node = f$getsyi("NODENAME")

You may then modify the specific logical name equivalence strings to specify a different file for each node. For example,

$ define/system COMTEK$SYSMGR_CRITPROC - comtek_root:[comtek$snmp.data]sysmgr_critproc_'Node'.dat

Then create the specified node specific file so that it relates only to the specified node.

Directory Contents NMServer for OpenVMS uses the following directory structure that is created during product installation:

comtek_root:[comtek$snmp.code] comtek_root:[comtek$snmp.com] comtek_root:[comtek$snmp.data] comtek_root:[comtek$snmp.doc]

The directory [.code] contains the following NMServer executable images and associated command procedures. To simplify the following



table, executable image names have been compressed to include a <xxx> placeholder. In an actual installation, this placeholder will indicate the subagent protocol (DPI or eSNMP), the system architecture (Alpha or VAX), and for VAX, the operating system version (5.5 or 6+). For example, the NM∗ SysMgr subagent executable image will have a name like one of the following: sysmgr_dpi_alpha.exe, sysmgr_-esnmp_alpha.exe, sysmgr_dpi_vax6.exe, or sysmgr_dpi_vax5.exe. On any one system, only one copy of each executable will be present.

Image / Procedure Description console.com NM∗ Console startup command procedure console_<xxx>.exe NM∗ Console image manager_<xxx>.exe A pseudo manager for testing master.com NM∗ Master startup command procedure master_<xxx>.exe NM∗ Master image nmopcom.com NM∗ Opcom startup command procedure nmopcom_<xxx>.exe NM∗ Opcom image sysmgr.com NM∗ SysMgr startup command procedure sysmgr_<xxx>.exe NM∗ SysMgr image trpmgr.com NM∗ TrpMgr startup command procedure trpmgr_<xxx>.exe NM∗ TrpMgr image vmsmon.com NM∗ VmsMon startup command procedure vmsmon_<xxx>.exe NM∗ VmsMon image

Process output files are also written to the [.code] directory and reflect the name of the executable image.

The directory [.com] contains command procedures for defining NMServer symbols and logical names:

Procedure Description cmd.com Defines the symbol cmd to be used to run the

pseudo manager (manager_<xxx>.exe) nmserver_logicals.com Contains the system logical names required

by the NMServer processes nmserver_symbols.com Defines the symbols master, sysmgr,

trpmgr, console, nmopcom, and vmsmon reinit_nmserver.com Reinitializes NMServer processes, causing

them to re-read configuration data files run_nmserver.com Starts licensed NMServer processes

NM∗ Master (DPI only), NM∗ SysMgr, NM∗ TrpMgr, NM∗ Console, NM∗ Opcom, and NM∗ VmsMon as detached processes



send_severity_trap.com Writes a message to a User Trap mailbox which causes it to be turned into a User Trap message. Messages that contain VMS severity codes become severity coded traps.

start_nmserver.com Same as run_nmserver.com. stop_nmserver.com Stops the NMServer processes

The directory [.data] contains samples of each of the data files required by the NMServer processes. Since the NMServer processes use logical names to access these files the names and locations of these files is not important. However any changes to the file names or their locations must also be reflected in their logical name definitions.

Sample Data File Description console.dat COMTEK$CONSOLE_CONFIG file master.dat COMTEK$MASTER_CONFIG file master_communities.dat COMTEK$MASTER_COMM file master_trapdest.dat COMTEK$MASTER_TRAP file nmopcom.dat COMTEK$NMOPCOM_CONFIG file nmopcom_filter.dat COMTEK$NMOPCOM_FILTER file nmserver_license.txt NMServer license key file. sysmgr.dat COMTEK$SYSMGR_CONFIG file sysmgr_critdsk.dat COMTEK$SYSMGR_CRITDSK file sysmgr_critproc.dat COMTEK$SYSMGR_CRIT file sysmgr_critqueue.dat COMTEK$SYSMGR_CRITQUEUE file sysmgr_filter.dat COMTEK$SYSMGR_FILTER file trpmgr.dat COMTEK$TRPMGR_CONFIG file trpmgr_filter.dat COMTEK$TRPMGR_FILTER file vmsmon.dat COMTEK$VMSMON_CONFIG file

The directory [.doc] contains the MIB file that is supported by NMServer. This file is not accessed by the NMServer code, but are provided for use by network management stations. The MIB file should be treated as an ASCII text file when using FTP.

MIB File Description NMServerVMS.MIB The NMServer for OpenVMS MIB file. Contains

all MIBs supported by NMServer for OpenVMS.

License Keys Beginning with v4.0 of NMServer, all license keys are maintained in a single file:



COMTEK_ROOT:[COMTEK$SNMP.DATA]NMSERVER_LICENSE.TXT

COMTEK will provide this file when licenses are purchased. When a temporary license expires, edit this file and replace the value for the TEMPORARY_LICENSE keyword. Old style license keys that were in each subagent’s configuration file are still permitted. Contact COMTEK for information on converting from old to new style license keys.

A temporary license key will work on any VMS system and has the format:

TEMPORARY_LICENSE=

Permanent licenses are either node specific or enterprise wide. Node specific license key entries include the node name. For instance, an entry for node TEST would look like:

TEST=

Enterprise license keys have the format:

ENTERPRISE_LICENSE=

You may edit this file to update a temporary license key. When you purchase NMServer, you will be given an NMSERVER_LICENSE.TXT file that includes licenses for your environment. Make sure to use ASCII when transferring (FTP) this file to your VMS systems.

Customize Configuration Files Customizing the configuration files consists of the following steps:

1. Setting up the process configuration files

2. Setting up the community file (DPI only)

3. Setting up the trap destination file (DPI only)

4. Setting up the filter files

5. Setting up the critical data files

Refer to the Process Configuration Files sections of Chapters 3 through 8 of this manual for complete details on the format and content of each of the following files.

Setting up the Process Configuration Files Each of the NMServer processes has its own configuration file that is used to control the process’ behavior. Logical names are used to locate



these configuration files. Below are the logical names of these configuration files:

COMTEK$MASTER_CONFIG (DPI only) COMTEK$CONSOLE_CONFIG COMTEK$NMOPCOM_CONFIG COMTEK$SYSMGR_CONFIG COMTEK$TRPMGR_CONFIG COMTEK$VMSMON_CONFIG

These files are described in detail in the “Process Configuration Files” sections of Chapters 3 through 8 of this manual. Before starting NMServer, you may edit these files to enter any values that you wish to supersede the predefined defaults.

Setting up the Community File (DPI Only) During product installation, the installer is provided the opportunity to define valid community data. To make changes to the community data, edit the file identified by the logical name:

COMTEK$MASTER_COMM

See the section entitled “COMTEK$MASTER_COMM Community File” in Chapter 3 of this manual for a complete description of the community file.

The same community string may be used for multiple entries in this file, as long as the privileges for each instance are the same.

NOTE: The following entry exists by default in the community file:

public 255.255.255.255 127.0.0.1 read

This entry allows the subagents to communicate with the DPI master agent. The above entry may be removed or modified as needed, however DPI subagents will not operate unless the community string used by the subagent corresponds to a community file entry in the COMTEK$MASTER_COMM file. The community string used by each subagent is ‘public’ by default but may be modified by adding a COMMUNITY keyword entry to all of the subagents’ configuration files. The community entry for subagents only requires read access.

Setting up the Trap Destination File (DPI Only) During product installation, the installer is provided the opportunity to define SNMP managers that are to be sent NMServer traps. To make changes to these trap destinations, edit the file identified by the logical name:



COMTEK$MASTER_TRAP

See the section entitled “COMTEK$MASTER_TRAPDEST Trap Destination File” in Chapter 3 of this manual for a complete description of the trap destination file.

Setting up the Filter Files To filter unwanted opcom trap messages sent by NM∗ Opcom or NM∗ SysMgr or to filter unwanted user trap messages sent by NM∗ TrpMgr, edit the appropriate filter file. The filter files are located by the logical names:

COMTEK$NMOPCOM_FILTER COMTEK$SYSMGR_FILTER COMTEK$TRPMGR_FILTER

Records within the filter files may be up to 80 characters long and may contain the wildcard symbol “∗ ” which matches any number of characters within the record. See Chapter 4 or Chapter 7, respectively, for a complete description of NM∗ SysMgr or NM∗ Opcom opcom message filtering. See Chapter 5 of this manual for a complete description of user trap message filtering.

Setting up the Critical Data Files Edit the critical disk, critical process, and critical queue data files (COMTEK$SYSMGR_CRITDSK, COMTEK$SYSMGR_CRITPROC, and COMTEK$SYSMGR_CRITQUEUE, respectively) to insert the names of any disks, processes, or queues that have special monitoring requirements. Chapter 4 of this manual contains a complete description of each of these files.

Running NMServer for OpenVMS Process Startup Symbols Symbols that can be used to start the NMServer processes are defined in the following command procedure:

comtek_root:[comtek$snmp.com]nmserver_symbols.com

This command procedure defines the NMServer symbols master (DPI only), sysmgr, trpmgr, console, nmopcom, and vmsmon. These symbols can be used to start NMServer as a set of detached processes or to start any one of the NMServer processes individually in debug mode attached



to a terminal. This file is referenced within the NMServer startup command procedure:

comtek_root:[comtek$snmp.com]run_nmserver.com

Process Startup NMServer for OpenVMS is started as a set of detached processes by executing the following command procedure:

comtek_root:[comtek$snmp.com]run_nmserver.com Depending upon the type of license purchased, after executing this command procedure, some of the following detached processes should be present on the system: NM∗ Master (DPI only), NM∗ SysMgr, NM∗ TrpMgr, NM∗ Console, NM∗ Opcom and NM∗ VmsMon. If one of the licensed processes fail to start, examine the output files in the comtek_root:[comtek$snmp.code] directory or start the processes individually with debug enabled to help determine the cause of the problem. For information on starting any one of the NMServer processes individually or enabling the process debugging information, consult the Process Startup sections in Chapters 3-8 of this manual. Since the operation of each of the NMServer subagents is independent of the other subagents, the startup command procedure may be modified to remove the startup of any subagents that are not licensed or that are not required. The NMServer startup command may be added to the system startup file (sys$manager:systartup.com). Make sure to place this command after the UCX or other TCP/IP product startup command in that file. For example,

$ @SYS$STARTUP:TCPIP$STARTUP $ @comtek_root:[comtek$snmp.com]run_nmserver

Consult your TCP/IP product literature for information on startup commands for you TCP/IP product.

Running NMServer on a Port Other than 161 By default, the NMServer software listens for SNMP requests from SNMP managers on the default SNMP UDP port, port 161. The default SNMP port may be overridden at process startup by specifying a different port number as a parameter when invoking the run_nmserver.com command procedure. For example, to start NMServer on the port 4268, enter the following command:

$ @comtek_root:[comtek$snmp.com]run_nmserver 4268

The run_nmserver.com command procedure defines a system logical name SNMP_PORT using the value specified on the command line and



then starts all of the NMServer processes. If no port parameter is supplied to the run_nmserver.com, this command procedure deassigns the system logical SNMP_PORT, if it is defined.

Reinitializing NMServer Processes When changes are made to configuration files while NMServer is running, the NMServer processes can be reinitialized to cause them to reread configuration file data.

To reinitialize NMServer processes, use the following command:

$ @comtek_root:[comtek$snmp.com]reinit_nmserver

This command procedure has one optional parameter, the name of the process to be reinitialized. For example, to reinitialize only the NM*SysMgr subagent process, enter the command as follows:

@comtek_root:[comtek$snmp.com]reinit_nmserver nm*sysmgr

Processes that are reinitialized send Warm Start traps to the SNMP Manager to confirm the reinitialization.

Stopping NMServer Processes To stop all of the NMServer processes, use the following command:

$ @comtek_root:[comtek$snmp.com]stop_nmserver

This command determines the PID of each of the NMServer processes and stops the processes.

Command Line SNMP Manager A command line SNMP manager is provided with the NMServer product for testing and debugging purposes only. This manager is capable of issuing SNMP get, getnext, set and walk (iterative getnext commands) and listening for traps (SNMPv1 only). This tool has information on all MIBs supported by NMServer compiled-in. This allows object identifiers to be translated automatically into MIB variable names, where possible. This manager is built during the software installation. To use the manager, define the symbol cmd using the command procedure:

comtek_root:[comtek$snmp.com]cmd.com

Online help is available. To access help information, enter cmd with no parameters. A list of the available options and parameters is displayed.

If NMServer is being run on a port other than 161, this utility will send SNMP requests to the port number defined by the logical name



SNMP_PORT. Note that this utility permits the user to specify the –p <port number> parameter, see the online documentation for details.

Sample Manager Commands The following commands may be issued to verify that the NMServer components are running and that the software version of each component is as expected:

$ cmd get mCfgVersion.0 (DPI only) $ cmd get sCfgVersion.0 $ cmd get tCfgVersion.0 $ cmd get cCfgVersion.0 $ cmd get oCfgVersion.0 $ cmd get vCfgVersion.0

Note from the above example, NMServer MIB variables use a single letter prefix to identify the subagent that supports that data. The prefixes are as follows:

c for NM∗ Console m for NM∗ Master o for NM∗ Opcom s for NM∗ SysMgr t for NM∗ TrpMgr v for NM∗ VmsMon

The following commands may be issued to reinitialize the master (DPI only) and subagents:

$ cmd set mCfgReinitMaster.0 1 (DPI only) $ cmd set sCfgReinitSubagent.0 1 $ cmd set tCfgReinitSubagent.0 1 $ cmd set cCfgReinitSubagent.0 1 $ cmd set oCfgReinitSubagent.0 1 $ cmd set vCfgReinitSubagent.0 1

The following command may be used to retrieve all of the MIB items supported by NMServer:

$ cmd walk iso

The above examples are provided to illustrate the use of the pseudo manager for testing purposes. As noted above, all implemented MIB items are accessible through this mechanism. Note also, that, with the



exception of the optional community string parameter, these commands are not case sensitive.



3 NMServer Master Agent (DPI Only)

NMServer for OpenVMS is supplied with its own master agent, NM∗ Master. NM∗ Master is an extensible agent which utilizes the DPI extensible agent protocol for communications with its subagents. The NM∗ Master agent executable image is not installed in eSNMP installations of NMServer for OpenVMS. For information relevant to eSNMP installations, please skip to Chapter 4.

NM∗ Master performs the role of intermediary between the SNMP manager and the DPI subagents and handles SNMP administrative functions. On startup, each DPI subagent establishes a TCP/IP connection with the DPI master agent and notifies the master agent of which MIB subtrees it will support. NM∗ Master uses subagent status change trap messages to notify the SNMP manager of subagent connections/disconnections.

NM∗ Master receives each SNMP request from the SNMP manager, performs community based authentication on the request, converts a valid request to a DPI packet and passes the DPI packet to the appropriate subagent. NM∗ Master waits for a response from the subagent, converts the DPI response packet into an SNMP response and returns the SNMP response to the manager. NM∗ Master also receives DPI trap packets from the subagents, converts them into SNMP trap PDUs and forwards the trap to the manager.

NM∗∗∗∗ Master Operation Privileges

Privilege Description NETMBX May create a network device PRMMBX May create permanent mailboxes SYSNAM May insert in system logical name table SYSPRV May access objects via system protection



Required Logical Names The following logical names are required by NM∗ Master.

• COMTEK$MASTER_CODE - Identifies the location (device and directory) of the code for the NM∗ Master agent. This name must be in the system logical name table.

• COMTEK$MASTER_COMM - Identifies the community file for the NM∗ Master agent. The file used by NM∗ Master may be changed while the NM∗ Master process is running by setting the MIB variable mCfgCommFile.0 to the new file name and then setting the variable mCfgReinitMaster.0 to 1 (TRUE). The MIB variable mCfgCommFile.0 contains the master agent's most recent translation of this logical name. This logical name must be in the system logical name table.

• COMTEK$MASTER_CONFIG - Identifies the configuration file for the NM∗ Master agent. The actual file used by the master agent may be changed while NM∗ Master is running by setting the MIB variable mCfgFile.0 to the new file name and then setting the variable mCfgReinitMaster.0 to 1 (TRUE). The MIB variable mCfgFile.0 contains the master agent's most recent translation of this logical name. This logical name must be in the system logical name table.

• COMTEK$MASTER_TRAP - Identifies the file of trap destina-tions (i.e., IP addresses to which traps should be sent) for the NM∗ Master agent. The file used by NM∗ Master may be changed while the NM∗ Master process is running by setting the MIB variable mCfgTrapFile.0 to the new file name and then setting the variable mCfgReinitMaster.0 to 1 (TRUE). The MIB variable mCfgTrapFile.0 contains the master agent's most recent translation of this logical name. This logical name must be in the system logical name table.

These system logical names are defined by the command procedure: comtek_root:[cometk$snmp.com]nmserver_logicals.com

NM∗ Master provides MIB variables which allow the equivalence-names for the logical names COMTEK$MASTER_COMM, COMTEK$-MASTER_CONFIG, and COMTEK$MASTER_TRAP to be modified. To make changes to these logical names permanent across system reboots, the equivalence-names in the file nmserver_logicals.com must also be changed.



Process Startup The command procedure:

comtek_root:[comtek$snmp.com]nmserver_symbols.com defines the symbols that may be used to start the NMServer processes. To run the NM∗ Master process, enter the following commands:

$ @comtek_root:[comtek$snmp.com]nmserver_symbols $ master

The command master starts the process NM∗ Master as a detached process. If the NM∗ Master process fails to start, examine the output file for the process to determine the cause of the problem. This file may be found in the COMTEK$MASTER_CODE directory.

To stop the detached process, either use the MIB variable mCfgTermProc.0 described in the MIB, or use the OpenVMS stop command:

$ stop/id=<process ID>

The NM∗ Master agent may also be started attached to the user's terminal with debug information enabled. Enter the following command:

$ master –d <n>

where <n> is an optional debug level of either 1 or 2. Level 1 debugging provides a display of DPI packet creation and parsing. Level 2 debugging provides a hex dump of the incoming and outgoing DPI packets. By default, level 1 is assumed if no value is provided following the –d.

Process Reinitialization Use the following reinitialization command procedure to cause the NM*Master process to re-read data from its configuration files:

$@comtek_root:[comtek$snmp.com]reinit_nmserver NM*Master

NM∗∗∗∗ Master Process Configuration Files COMTEK$MASTER_CONFIG Configuration File The configuration file is read by the NM∗ Master agent when the process is started. This file is identified by the following logical name:

COMTEK$MASTER_CONFIG

If this logical name is not defined when the agent is started, the process will terminate with an error. If a set-request is performed on the MIB



variable mCfgFile.0, the specified file name must exist, be accessible, and contain only valid data for the set-request to be successful. NM∗ Master must be reinitialized by setting the variable mCfgReinitMaster.0 to 1 (TRUE) for the new file to take effect.

The following is an example of a NM∗ Master configuration file: AllowDupIds=disabled AuthTrap=enabled Contact=COMTEK Services (703) 751-3997 ControlTermProc=disabled DfltTimeout=5 Location=101 South Whiting St, Suite 300, Alex VA 22304 Logging=disabled MaxTimeout=60 Name=comtek TrapTableSize=100

The format of the file is a left justified variable name followed by an '=' without intervening spaces or tabs. The variable names may be expressed in upper, lower or mixed case. If one of the optional variables is missing, misspelled, or has an invalid value, a warning message is written to the process log file and a default value for the variable is used.

Most of the configuration file variables have MIB equivalents. For any corresponding MIB variable that is read-write accessible, new values supplied via set-requests are saved to the current configuration disk file. See below for MIB equivalents, optional variables and default values. Comments may be inserted in the configuration file by placing a pound sign (#) as the first character in the line.

AllowDupIds=This variable controls whether the NM∗ Master agent permits the registration of subagents with the same object identifiers. If this variable is set to ENABLED, registration of duplicate object identifiers is permitted.

Attributes Values samib MIB Variable saAllowDuplicateIDs.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value DISABLED Set-requests Take effect immediately

AuthTrap=This variable determines whether any authentication failure traps are sent to the appropriate SNMP managers. If this variable is set to



ENABLED, authentication failure traps are sent. If this variable is set to DISABLED, no authentication failure traps are sent.

Attributes Values MIB-II Variable snmpEnableAuthenTraps.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect immediately

Contact=This variable is usually the name and means of contacting the administrator for this machine.

Attributes Values MIB-II Variable sysContact.0 Required/Optional Required Set-requests Take effect immediately

ControlTermProc=This variable controls the use of the MIB object mCfgTermProc.0. If this variable is set to DISABLED, sets of the variable mCfgTermProc.0 are not allowed, thereby disabling the ability to terminate the NM∗ Master process programmatically. If this variable is set to ENABLED, process termination may be initiated via the variable mCfgTermProc.0.

Attributes Values NMMaster MIB Variable mCfgControlTermProc.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value DISABLED Set-requests Not permitted

DfltTimeout=This variable identifies the subagent default time-out value. If a subagent specifies a time-out value of zero when registering with NM∗ Master, this value is used as the maximum time NM∗ Master will wait for replies from the subagent. This value may not be greater than the current value of MaxTimeout. This value is specified in seconds.



Attributes Values samib MIB Variable saDefaultTimeout.0 Required/Optional Optional Valid Values 0-saMaxTimeout Default Value 5 Set-requests Take effect immediately

License=This variable has been replaced by the NMSERVER_LICENSE.TXT file which contains product license key(s). This variable is obsolete and is permitted here for backward compatibility with v3.5 or older of NMServer.

Attributes Values Required/Optional Optional

Location=This variable is typically a description of the system location which is meaningful to the network administrator.

Attributes Values MIB-II Variable sysLocation.0 Required/Optional Required Set-requests Take effect immediately

Logging=This variable controls logging of data within the NM∗ Master agent. If the NM∗ Master agent is run as a detached process, the log data is written to the log file identified by the MIB variable mCfgLogFile.0. When logging is enabled, data is written to the log file for each SNMP message sent or received by the master agent as well as each trap message sent or received. NOTE: Due to the amount of I/O incurred by logging, it may be necessary to increase time-out values between the NM∗ Master agent and the network management station when logging is enabled.

Attributes Values NMMaster MIB Variable mCfgLogging.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value DISABLED Set-requests Take effect immediately

MaxTimeout=This variable identifies the maximum time-out allowed to be specified by any subagent. (Time-out refers to the amount of time the NM∗ Master agent will wait for responses from a subagent.) Each



subagent is permitted to specify a time-out when opening a connection with the NM∗ Master agent and when registering a MIB subtree with the NM∗ Master agent. If the subagent specifies a time-out value that exceeds NM∗ Master's MaxTimeout value, the MaxTimeout value will be used instead of the value specified by the subagent. This value is specified in seconds.

Attributes Values Samib MIB Variable saMaxTimeout.0 Required/Optional Optional Valid Values 0-3600 Default Value 60 Set-requests Take effect immediately

Name=This variable is the name of the system on which the NM∗ Master agent is running. If this value is not supplied in the configuration file, the system node name is used.

Attributes Values MIB-II Variable sysName.0 Required/Optional Optional Default Determined by SYS$GETSYI Set-requests Take effect immediately

TrapTableSize=The number of trap messages that are to be retained in the NM∗ Master agent trap table. The trap table is a circular table containing a copy of traps generated by the NM∗ Master. This value specifies the maximum number of messages in that table. Once the maximum number of messages in the table has been reached, the oldest messages are overwritten by new trap messages.

Attributes Values NMMaster MIB variable mCfgTrapTblSize.0 Required/Optional Optional Valid Values 10..5000 Default Value 100 Set-requests Take effect immediately

COMTEK$MASTER_COMM Community File The community file is used by the NM∗ Master agent to specify community data to be used in community based message authentication. This file is located by the logical name COMTEK$MASTER_COMM. If



this logical name is not defined when NM∗ Master is started, the process will terminate with an error.

If a set-request is performed on the MIB variable mCfgCommFile.0 the specified file name must exist and be accessible to the NM∗ Master agent for the set-request to be successful. NM∗ Master must be reinitialized by setting the variable mCfgReinitMaster.0 to (1) TRUE for the new file to take effect.

The following is an example of a community file: #<community> <network mask> <host address> <privileges> control 255.255.255.0 199.199.199.0 write public 0.0.0.0 0.0.0.0 read disallow 255.0.0.0 122.0.0.0 none

The first field contains the community string. This identifies the community string that is to be part of the SNMP message. If the same community string appears on more than one record in this file, all privileges for each instance must be identical.

The second field contains the network mask and the third field contains the IP address of the host. Each SNMP message received by the NM∗ Master agent is authenticated by ANDing the IP address of the message originator with the network mask and comparing the results of the AND operation with the host address which corresponds to the network mask. This permits a single community file entry to identify to a network, a subnet, or a single host. In the above example, the entry "control 255.255.255.0 199.199.199.0 write" pertains to hosts on the IP network 199.199.199. The entry “public 0.0.0.0 0.0.0.0 read” gives read access to all hosts using the community string public.

The fourth field contains the privilege to be granted the entry. Valid privilege values are: READ (for read-only), WRITE (for read-write), and NONE (for no access).

Comments may be inserted in the community file by placing a pound sign (#) as the first character of the line.

NOTE: An entry must be present in the community file that will allow the subagents read access to the master agent. An example of such an entry is:

public 255.255.255.255 127.0.0.1 read

By default, the subagents use the community string “public” when communicating with the master agent. To specify a different value, place a COMMUNITY keyword entry in the configuration file for each



subagent and add an entry to the community file that permits the new community string read access for the local network.

COMTEK$MASTER_TRAP Trap Destination File The trap destination file is used by the NM∗ Master agent to specify the destination IP addresses of trap messages sent by the NM∗ Master agent, which includes traps initiated by NM∗ Master and those sent on behalf of NMServer subagents. This file is located by the logical name COM-TEK$MASTER_TRAP. If this logical name is not defined when NM∗ Master is started, the process will terminate with an error. If a set-request is performed on the MIB variable mCfgTrapFile.0, the specified file name must exist and be accessible to the NM∗ Master agent for the set-request to be successful. NM∗ Master must be reinitialized by setting the variable mCfgReinitMaster.0 to 1 (TRUE) for the new file to take effect.

The following is an example of a trap destination file: #<community> <IPaddress> <port> public 127.0.0.1 162 public 199.199.199.2 162

The first field contains the community string which is to accompany the trap. The second field contains the IP address of the host that is to receive the trap. The third field contains the port number to which the trap is to be sent. This field typically contains the value 162.

Comment lines have a pound sign (#) as the first character in the line.

NM∗∗∗∗ Master MIB Objects All MIB files are supplied for use by network management stations. These files are not accessed by the NMServer for OpenVMS processes. MIB files are written in ASN.1 format.

MIB-II NM∗ Master supports the following groups from MIB-II:

System Group System Description System Object Identifier System Up Time System Contact System Name System Location



System Services

SNMP Group SNMP In Packets SNMP In Bad Version SNMP In Bad Community Names SNMP In Bad Community Uses SNMP In ASN Parse Errors SNMP Enable Authentication Traps

Master Agent Objects in NMSERVERVMS.MIB File Software Error Group Status Code File Line Number Last Time Message

Trap Group Next Sequence Number Trap Time Resend Sequence Number

Configuration Group Configuration File Name Log File Name Community File Name Trap Destination File Name Reinitialization Flag Logging Flag Trap Table Size Process Termination Control Flag Terminate Process Flag NM∗ Master Agent Version Authentication Failure IP Address Authentication Failure Community String

DPI Port Group DPI Port For TCP DPI Port For UDP

saMIB Group Default Time-out Maximum Time-out Allow Duplicate Ids Flag



Number of Entries in Subagent Table All Packets In Counter All Packets Out Counter Subagent Table

Subagent Index Subagent Identifier Subagent Description Subagent Status Subagent Status Change Time Subagent Protocol Subagent Protocol Version Subagent Protocol Release Subagent Transport Subagent Transport Address Subagent Time-out Subagent Maximum VarBinds Subagent Packets In Counter Subagent Packets Out Counter

Subagent Tree Table Subagent Subtree Subagent Subtree Priority Subagent Subtree Index Subagent Subtree Status Subagent Subtree Time-out

NM∗∗∗∗ Master Traps All trap files supplied with NMServer for OpenVMS are written in ASN.1 format in compliance with RFC-1215, which is informational. Use of trap files is not supported by all SNMP manager systems. See Chapter 9 of this manual for more information about NMServer traps.

The following information provides an overview of the traps that may be generated by the NM∗ Master agent. Refer to NMSERVERVMS.MIB for a complete description of each trap, the variables that accompany it, and the circumstances under which it may be generated.

SNMP Generic Traps Trap Description coldStart(0) NM∗ Master has completed a cold start. warmStart(1) NM∗ Master has completed a

reinitialization. authenticationFailure(4) NM∗ Master received an SNMP message



that was not properly authenticated.

Enterprise Specific Traps Trap Description mSwErr(0) A software error was encountered by

NM∗ Master. mTermProc(1) NM∗ Master process termination. mSubagentStatusChange(2) The status of a subagent has changed.



4 NM∗∗∗∗ SysMgr Subagent

The NM∗ SysMgr Subagent is a system management subagent. This subagent can be used to automate many system management functions. This subagent also can be tailored and tuned according to specific system requirements so that system problems can be detected and corrected before they become critical.

NM∗ SysMgr monitors system information, CPU utilization, disk and shadow set information, active processes, hardware errors and operator communications. In addition, NM∗ SysMgr can be configured to perform special monitoring on mission critical processes, queues and disks. NM∗ SysMgr uses traps to provide instant notification when system conditions exceed user-defined thresholds. Configuration parameters include trap thresholds, trap repeat timers and statistics gathering interval timers. Nearly all configuration parameters may be modified in real time and all configuration changes are retained in a configuration file.

NM∗∗∗∗ SysMgr Operation Privileges

Privilege Description NETMBX May create a network device OPER May perform operator functions PRMMBX May create permanent mailboxes SECURITY May perform security functions SYSNAM May insert in system logical name table VOLPRO May override volume protection WORLD May affect other processes in the world

Required Logical Names The following logical names are required by NM∗ SysMgr.

• COMTEK$SYSMGR_CODE - Identifies the location (device and directory) of the code for the NM∗ SysMgr subagent. This name must be in the system logical name table.



• COMTEK$SYSMGR_CONFIG - Identifies the configuration file for the NM∗ SysMgr subagent. The actual file used may be changed while NM∗ SysMgr is running by setting the MIB variable sCfgFile.0 to the new file name and then setting the variable sCfgReinitSubagent.0 to 1 (TRUE). The MIB variable sCfgFile.0 contains the subagent's most recent translation of this logical name. This name must be in the system logical name table.

• COMTEK$SYSMGR_CRITDSK - Identifies the file that contains the current list of critical disks. The actual file may be changed while the NM∗ SysMgr is running by setting the MIB variable sCfgCritDsk.0 to the new file name and then setting the variable sCfgReinitSubagent.0 to 1 (TRUE). The MIB variable sCfgCritDsk.0 contains the subagent's most recent translation of this logical name. This name must be in the system logical name table.

• COMTEK$SYSMGR_CRITPROC - Identifies the file which contains the current list of critical processes. The actual file may be changed while the NM∗ SysMgr is running by setting the MIB variable sCfgCritFile.0 to the new file name and then setting the variable sCfgReinitSubagent.0 to 1 (TRUE). The MIB variable sCfgCritFile.0 contains the subagent's most recent translation of this logical name. This name must be in the system logical name table.

• COMTEK$SYSMGR_CRITQUEUE - Identifies the file which contains the current list of critical queues and critical jobs. The actual file may be changed while the NM∗ SysMgr is running by setting the MIB variable sCfgCritQue.0 to the new file name and then setting the variable sCfgReinitSubagent.0 to 1 (TRUE). The MIB variable sCfgCritQue.0 contains the subagent's most recent translation of this logical name. This name must be in the system logical name table

• COMTEK$SYSMGR_FILTER - Identifies the file containing opcom message filtering data. To alter the filter data while NM∗ SysMgr is running, edit this file and set the MIB variable sCfgReinitSubagent.0 to 1 (TRUE). This will cause the filter data to be reinitialized from the file.




The NM∗ SysMgr subagent provides MIB variables that allow the equivalence-names for the following logical names to be modified:

COMTEK$SYSMGR_CONFIG COMTEK$SYSMGR_CRITPROC COMTEK$SYSMGR_CRITDSK COMTEK$SYSMGR_CRITQUEUE

To make changes to these logical names permanent across system reboots, the equivalence-names in nmserver_logicals.com must also be changed.



defines the symbols that may be used to start the NMServer processes. To run the NM∗ SysMgr process, enter the following commands:

$ @comtek_root:[comtek$snmp.com]nmserver_symbols $ sysmgr

The command sysmgr starts the process NM∗ SysMgr as a detached process. If the NM∗ SysMgr process fails to start, examine the output file for the process to determine the cause of the problem. This file may be found in the COMTEK$SYSMGR_CODE directory.

To stop the detached process, either use the MIB variable sCfgTermProc.0, as described in the MIB, or use the OpenVMS stop command:


The NM∗ SysMgr subagent may also be started attached to the user's terminal with debug information enabled. Enter the following command:

$ sysmgr -d <n>

where <n> is an optional debug level of 1, 2 or 3. In a DPI environment, level 1 provides a display of DPI packet creation and parsing and levels 2 and 3 provide a hex dump of the incoming and outgoing DPI packets. In an eSNMP environment, level 1 displays eSNMP error messages, level 2 displays eSNMP error and warning messages and level 3 displays eSNMP error, warning and trace messages. By default, level 1 is assumed if no value is provided following the –d.



Process Reinitialization Use the following reinitialization command procedure to cause the NM*SysMgr process to re-read data from its configuration files:

$ @comtek_root:[comtek$snmp.com]reinit_nmserver NM*SysMgr

NM∗∗∗∗ SysMgr Process Configuration Files COMTEK$SYSMGR_CONFIG Configuration File This configuration file is read by the NM∗ SysMgr subagent when the process is started. This file is identified by the logical name COMTEK$SYSMGR_CONFIG. If this logical name is not defined when the subagent is started, the process will terminate with an error. If a set-request is performed on the MIB variable sCfgFile.0 the specified file name must exist and be accessible to NM∗ SysMgr for the set-request to be successful. NM∗ SysMgr must be reinitialized by setting the variable sCfgReinitSubagent.0 to 1 (TRUE) for the new file to take effect.

The following is an example of a configuration file: AllPsData=no Community=public ComQueue=5 ComoQueue=1 ControlTermProc=disabled CpuPersist=1 CpuUtil=90 CritDisksOnly=false CritTimer=1 DskMinFreeBlks=0 DskOps=25 DskTimer=1 DskUse=90 Filter=dropMatch Host=alpha.comtek.com HwErrTimer=1 HwErrTrap=enabled IntUtil=10 LocalDisksOnly=false MaxTrapSec=0 MemUse=90 MWAITLimit=0 OpcomCards=enabled



OpcomCentral=enabled OpcomCluster=enabled OpcomDevices=enabled OpcomDisks=enabled OpcomLicense=enabled OpcomNetwork=enabled OpcomOper1=enabled OpcomOper2=enabled OpcomOper3=enabled OpcomOper4=enabled OpcomOper5=enabled OpcomOper6=enabled OpcomOper7=enabled OpcomOper8=enabled OpcomOper9=enabled OpcomOper10=enabled OpcomOper11=enabled OpcomOper12=enabled OpcomPrinter=enabled OpcomSecurity=enabled OpcomTapes=enabled PgUse=90 PsTimer=5 QueSummary=disabled QueTimer=1 RptCritAlarm=5 RptDskAlarm=5 SwpUse=90 SysInfoTimer=1 Timeout=5 Traps=enabled TrapTableSize=100

The format of the file is a left justified variable name followed by an '=' without intervening spaces or tabs. The variable names may be expressed in upper, lower or mixed case. If one of the optional variables is missing, misspelled, or has an invalid value, a warning message is written to the process' log file and a default value for the variable is used. Most of the configuration file variables have MIB equivalents. For any corresponding MIB variable that is read-write accessible, new values supplied via set-requests are saved to the current configuration disk file. See below for MIB equivalents, optional variables and default values. Comments may



be inserted in the configuration file by placing a pound sign (#) as the first character in the line.

AllPsData=This variable controls the amount of data that is available in the process statistics table sPsTbl. If this flag is set to no, only the process statistics that are contained in the process control block (PCB) or job information block (JIB) for each process are available (data in the process header (PHD) may also be available for some processes). Setting this flag to yes makes data in the PHD available for all processes but incurs an additional performance overhead (to retrieve out swapped processes and deliver kernel mode ASTs to all processes).

Attributes Values NMSysMgr MIB Variable sCfgAllPsData.0 Required/Optional Optional Valid Values YES, NO Default Value NO Set-requests Take effect immediately

Community=This variable sets the community string to be used by the NM∗ SysMgr subagent when initiating communications with the NM∗ Master agent. This value must correspond to an entry in the NM∗ Master agent's community file identified by the logical name COMTEK$MASTER_COMM, for the subagent's IP Address. This variable is not used in an eSNMP environment.

Attributes Values NMSysMgr MIB Variable Not applicable Required/Optional Optional Default Value public Set-requests Not permitted

ComQueue=This variable specifies the threshold at which sCOMQue traps begin to be set. Once this threshold has been reached, sCOMQue traps will continue to be sent each time process statistics are gathered (as determined by the PsTimer configuration item) until the level drops below this threshold. These traps indicate that an excessive number of processes are waiting to compute (in COM state).

Attributes Values NMSysMgr MIB Variable sCfgCOMQueueLimit.0 Required/Optional Optional Default Value 5 Set-requests Take effect on next timer



expiration

ComoQueue=This variable specifies the threshold at which sCOMOQue traps begin to be set. Once this threshold has been reached, sCOMOQue traps will continue to be sent each time process statistics are gathered (as determined by the PsTimer configuration item) until the level drops below this threshold. These traps indicate that an excessive number of outswapped processes are waiting to compute (in COMO state).

Attributes Values NMSysMgr MIB Variable sCfgCOMOQueueLimit.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next timer

expiration

ControlTermProc=This variable controls the use of the variable sCfgTermProc.0. If this variable is set to DISABLED, sets of the variable sCfgTermProc.0 are not allowed, thereby disabling the ability to terminate the NM∗ SysMgr process programmatically. If this variable is set to ENABLED, process termination may be initiated via the variable sCfgTermProc.0.

Attributes Values NMSysMgr MIB Variable sCfgControlTermProc.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value DISABLED Set-requests Not permitted

CpuPersist=This variable specifies the number of consecutive minutes that the CPU utilization must exceed the CpuUtil threshold before CPU utilization trap is sent.

Attributes Values NMSysMgr MIB Variable sCfgCpuPersist.0 Required/Optional Optional Default Value 1 Set-requests Take effect immediately

CpuUtil=This variable specifies the threshold percentage of total CPU usage at which sCpuUsage traps begin to be sent. Once this threshold is



reached, sCpuUsage traps are sent once per minute until the CPU utilization drops below this threshold. This value is normalized for multiple CPU systems so that it expresses the total CPU capacity of the system during a one-minute interval. A value of zero disables these trap messages.

Attributes Values NMSysMgr MIB Variable sCfgCpuLimit.0 Required/Optional Optional Valid Values 0..100 Default Value 90 Set-requests Take effect immediately

CritDisksOnly=This variable controls if all disks available to the system are monitored or only disks that are listed in the critical disk file (COMTEK$SYSMGR_CRITDSK). This variable works with the LocalDisksOnly configuration variable.

Attributes Values NMSysMgr MIB Variable sCfgCritDisksOnly.0 Required/Optional Optional Default Value false Set-requests Take effect on next timer expiration

CritTimer=This variable specifies the number of minutes between checks for critical processes missing. A value of zero disables critical process missing processing.

Attributes Values NMSysMgr MIB Variable sCfgCritTimer.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next timer expiration

DskMinFreeBlks=This variable specifies the minimum number of free blocks required on all disks on the system that are not listed in the critical disk table. Either this variable or the variable DskUse may be specified with a nonzero value. A value of zero disables disk full traps based on the number of free blocks on a disk. The default value is only used if the value for DskUse is specified as zero and DskMinFreeBlks is omitted from the configuration file.

Variable Values NMSysMgr MIB Variable sCfgDskMinFreeBlks.0



Required/Optional Optional Default Value 1000 Set-requests Take effect on next timer expiration

DskOps=This variable specifies the disk operation per second limit at which sDskOpSec traps begin to be sent. This threshold is expressed in terms of number of operations (read and write) per second to disk. At the expiration of each sCfgDskTimer.0 interval, the number of disk operations during that interval is computed. A trap is sent if the number of operations during that interval exceeds the sCfgDskOps.0 limit. Setting this value to zero disables these traps. These traps are also disabled if the variable sCfgDskTimer.0 is set to zero.

Attributes Values NMSysMgr MIB Variable sCfgDskOps.0 Required/Optional Optional Default Value 25 Set-requests Take effect immediately

DskTimer=This variable specifies the number of minutes between updates of the disk table data. A value of zero disables gathering of disk related data.

Attributes Values NMSysMgr MIB Variable sCfgDskTimer.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next timer

expiration

DskUse=This variable specifies the default percentage of disk utilization at which sDskFull trap messages begin to be sent. A value of zero disables sDskFull trap messages due to this limit being reached.

DskUse and DskMinFreeBlks are two different ways to specify the limit at which disk full traps should be sent. These values are only in force for disks that contain no percent or blocks entry in the critical disk file COMTEK$SYSMGR_CRITDSK. Only one of these limits may be in use (that is, nonzero) at any given time. If both of these values exist in the configuration file, only one may have a nonzero value. If only one of these values is present in the configuration file and its value is nonzero, the other item will default to zero (disabled). If only one of these items exists in the configuration file and it has a value of zero (disabled), then the default value for the other limit will be in force. To disable these two



items from causing disk full traps for disks not listed in the critical disk table, both items must appear in the configuration file with a value of zero.

Attributes Values NMSysMgr MIB Variable sCfgDskLimit.0 Required/Optional Optional Valid Values 0..100 Default Value 90 Set-requests Take effect immediately

Filter=This variable controls whether NM∗ SysMgr drops opcom messages that match records in the filter file (DROPMATCH) or if it forwards only those messages that match (KEEPMATCH) a record in the filter file and drops all other messages.

Attributes Values NMSysMgr MIB Variable sCfgOpcomFilter.0 Required/Optional Optional Valid Values DROPMATCH, KEEPMATCH Default Value DROPMATCH Set-requests Take effect at process startup

Host=This variable is the name of the host on which the NM∗ Master agent is running. This variable is not currently used.

Attributes Values NMSysMgr MIB Variable sCfgHostName.0 Required/Optional Optional Default Value localhost Set-requests Not permitted

HwErrTimer=This variable specifies the number of minutes between checks for hardware errors. A value of zero disables gathering of hardware error data.

Attributes Values NMSysMgr MIB Variable sCfgHwErrTimer.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next timer expiration



HwErrTrap=This variable determines whether hardware error traps are sent. If this variable is set to ENABLED, all hardware error traps are sent. If this variable is set to DISABLED, no hardware error traps are sent.

Attributes Values NMSysMgr MIB Variable sCfgHwErrTraps.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect immediately

IntUtil=This variable specifies the threshold percentage of total Interrupt CPU usage at which sIntUsage traps begin to be sent. Once this threshold is reached, sIntUsage traps are sent once per minute until the CPU utilization in interrupt mode drops below this threshold. This value is normalized for multiple CPU systems so that it expresses the total CPU capacity of the system. A value of zero disables these trap messages.

Attributes Values NMSysMgr MIB Variable sCfgIntLimit.0 Required/Optional Optional Valid Values 0..100 Default Value 20 Set-requests Take effect immediately



LocalDisksOnly=This variable controls if all disks available to the system are monitored or only local disks. This variable works with the CritDisksOnly variable.

Attributes Values NMSysMgr MIB Variable sCfgLocalDisksOnly.0 Required/Optional Optional Default Value false Set-requests Take effect on next timer expiration



MaxTrapSec=This variable controls the maximum number of traps per second that may be transmitted by NM∗ SysMgr.

Variable Values NMSysMgr MIB Variable sCfgMaxTrapSec.0 Required/Optional Optional Valid Values 0-100 Default Value 0 Set-requests Take effect immediately

MemUse=This variable specifies the percentage of physical memory utilization at which sMemFull traps begin to be sent.

Variable Values NMSysMgr MIB Variable sCfgMemLimit.0 Required/Optional Optional Valid Values 0-100 Default Value 90 Set-requests Take effect immediately

MWAITLimit=This variable specifies the number of processes in MWAIT state that initiate sMWAITExcessive traps. A value of 0 disables these traps.

Variable Values NMSysMgr MIB Variable sCfgMWAITLimit.0 Required/Optional Optional Default Value 0 Set-requests Take effect immediately

OpcomCards=This variable controls whether NM∗ SysMgr is enabled to receive operator CARDS class messages. This variable is like performing a $ REPLY/ENABLE=CARDS for the NM∗ SysMgr process.

Attributes Values NMSysMgr MIB Variable sCfgOpcomCards.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomCentral=This variable controls whether NM∗ SysMgr is enabled to receive operator CENTRAL class messages. This variable is



like performing a $ REPLY/ENABLE=CENTRAL for the NM∗ SysMgr process.

Attributes Values NMSysMgr MIB Variable sCfgOpcomCentral.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomCluster=This variable controls whether NM∗ SysMgr is enabled to receive operator CLUSTER class messages. This variable is like performing a $ REPLY/ENABLE=CLUSTER for the NM∗ SysMgr process.

Attributes Values NMSysMgr MIB Variable sCfgOpcomCluster.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomDevices=This variable controls whether NM∗ SysMgr is enabled to receive operator DEVICES class messages. This variable is like performing a $ REPLY/ENABLE=DEVICES for the NM∗ SysMgr process.

Attributes Values NMSysMgr MIB Variable sCfgOpcomDevices.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomDisks=This variable controls whether NM∗ SysMgr is enabled to receive operator DISKS class messages. This variable is like performing a $ REPLY/ENABLE=DISKS for the NM∗ SysMgr process.



Attributes Values NMSysMgr MIB Variable sCfgOpcomDisks.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomLicense=This variable controls whether NM∗ SysMgr is enabled to receive operator LICENSE class messages. This variable is like performing a $ REPLY/ENABLE=LICENSE for the NM∗ SysMgr process.

Attributes Values NMSysMgr MIB Variable sCfgOpcomLicense.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomNetwork=This variable controls whether NM∗ SysMgr is enabled to receive operator NETWORK class messages. This variable is like performing a $ REPLY/ENABLE=NETWORK for the NM∗ SysMgr process.

Attributes Values NMSysMgr MIB Variable sCfgOpcomNetwork.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomOper1=This variable controls whether NM∗ SysMgr is enabled to receive operator OPER1 class messages. This variable is like performing a $ REPLY/ENABLE=OPER1 for the NM∗ SysMgr process.

Attributes Values NMSysMgr MIB Variable sCfgOpcomOper1.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup









OpcomPrinter=This variable controls whether NM∗ SysMgr is enabled to receive operator PRINTER class messages. This variable is like performing a $ REPLY/ENABLE=PRINTER for the NM∗ SysMgr process.



Attributes Values NMSysMgr MIB Variable sCfgOpcomPrinter.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomSecurity=This variable controls whether NM∗ SysMgr is enabled to receive operator SECURITY class messages. This variable is like performing a $ REPLY/ENABLE=SECURITY for the NM∗ SysMgr process.

Attributes Values NMSysMgr MIB Variable sCfgOpcomSecurity.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomTapes=This variable controls whether NM∗ SysMgr is enabled to receive operator TAPES class messages. This variable is like performing a $ REPLY/ENABLE=TAPES for the NM∗ SysMgr process.

Attributes Values NMSysMgr MIB Variable sCfgOpcomTapes.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

PgUse=This variable specifies the percentage of page file utilization at which sPgFull trap messages begin to be sent. A value of zero disables these trap messages.

Attributes Values NMSysMgr MIB Variable sCfgPgLimit.0 Required/Optional Optional Valid Values 0..100 Default Value 90 Set-requests Take effect immediately



PsTimer=This variable specifies the number of minutes between updates of the process statistics data. A value of zero disables gathering of process statistics data.

Attributes Values NMSysMgr MIB Variable sCfgPsTimer.0 Required/Optional Optional Default Value 5 Set-requests Take effect on next timer

expiration

QueSummary=This variable controls if queue summary statistics are collected. Queue summary statistics are those variables contained in the groups sQueBatch, sQueGeneric, sQuePrinter, sQueServer, sQueSymbiont and sQueTerminal. Enabling this variable on a system that has a large number of queues and queue entries may noticeably increase the CPU used by the NM*SysMgr agent process.

Variable Values NMSysMgr MIB Variable sCfgQueSummary.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value DISABLED Set-requests Take effect on next queue

timer expiration

QueTimer=This variable specifies the number of minutes between updates of the queue table and queue entry data. A value of zero disables gathering of queue table and queue entry data.

Variable Values NMSysMgr MIB Variable sCfgQueTimer.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next timer

expiration

RptCritAlarm=This variable specifies the number of minutes between repeat traps for a given critical process missing condition. Setting this variable to zero causes only the initial detection of a missing process to generate a trap.



Attributes Values NMSysMgr MIB Variable sCfgCritAlarm.0 Required/Optional Optional Default Value 5 Set-requests Take effect on next timer

expiration

RptDskAlarm=This variable specifies how frequently sDskFull, sPgFull, and sSwpFull trap messages are sent while utilization remains above the specified use limit. A value of zero causes only the initial trap message to be sent.

Attributes Values NMSysMgr MIB Variable sCfgDskAlarm.0 Required/Optional Optional Default Value 5 Set-requests Take effect on next timer

expiration

SwpUse=This variable specifies the percentage of swap file utilization at which sSwpFull trap messages begin to be sent. A value of zero disables these trap messages.

Attributes Values NMSysMgr MIB Variable sCfgSwpLimit.0 Required/Optional Optional Valid Values 0..100 Default Value 90 Set-requests Take effect immediately

SysInfoTimer=This variable specifies the number of minutes between updates of the system information data. A value of zero disables the gathering of system information data.

Attributes Values NMSysMgr MIB Variable sCfgSysInfoTimer.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next timer

expiration

Timeout= This variable specifies the amount of time the master agent will wait for the subagent to respond to SNMP requests. In the DPI



environment, if this value is not specified, the default value saDefaultTimeout contained in the NM∗ Master agent will be used. If the value specified exceeds the current maximum that the NM∗ Master agent will permit (saMaxTimeout), the maximum value will be used. In the eSNMP environment, valid values range from 0 to 10. If a value of zero is specified, the eSNMP master agent will wait 3 seconds for the subagent’s response. This value is specified in seconds.

Attributes Values NMSysMgr MIB Variable sCfgTimeout.0 Required/Optional Optional Valid Values 0-3600 Default Value 0 Set-requests Take effect at process startup

Traps=This variable determines whether any traps are sent. If this variable is set to ENABLED, all traps are sent. If this variable is set to DISABLED, no traps are sent. NOTE: When trap sending is disabled, trap information is logged to the NM*SysMgr process .OUT file. If traps are disabled for a prolonged period of time, this file may grow to an excessive size.

Attributes Values NMSysMgr MIB Variable sCfgTraps.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect immediately

TrapTableSize=This variable defines the number of trap messages that are to be retained in the NM∗ SysMgr internal trap table. The trap table is a circular table containing a copy of trap messages sent by the NM∗ SysMgr. This value specifies the maximum number of messages to be retained in that table. Once the maximum number of messages in the table has been reached, the oldest messages are overwritten by new trap messages.



Attributes Values NMSysMgr MIB variable sCfgTrapTblSize.0 Required/Optional Optional Valid Values 10..5000 Default Value 100 Set-requests Take effect immediately

COMTEK$SYSMGR_CRIT Critical Processes The critical process file contains the information that NM∗ SysMgr uses to monitor mission critical processes. Each line in this file contains the process name and the minimum number of instances of the process that are required to be running on the system. If the number of instances of a process drops below the specified required number, NM∗ SysMgr generates an sCriticalProcessMissing trap message. This file supports the use of wildcards. All process names are case blind.

The format of the entries in this file is <processName>,<requiredCount> where <processName> is the name of the process that is to be monitored and <requiredCount> is a number specifying the minimum number of instances of the process. Each process entry must occupy a separate line in the file and each line of the file must be left justified. No white space is permitted between the process name, the comma, and the required count.

For example, SWAPPER,1 AB%DE,7 TEST_∗ ,2

specifies that one copy of SWAPPER, seven copies of AB%DE, and two copies of TEST_∗ are to be running. Up to one hundred different process entries may be monitored simultaneously. Comments may be inserted in the critical process file by placing a pound sign (#) as the first character in the line.

The % wildcard matches any single character, while the ∗ wildcard matches any number of characters. In the above example, the AB%DE would match processes by the name of ABCDE and AB_DE but would not match a process by the name ABBBDE. The entry TEST_∗ would match TEST_1 and TEST_394829305825.

For changes to this file to take effect, the NM∗ SysMgr subagent must be reinitialized using the variable sCfgReinitSubagent.0.



NM∗ SysMgr collects performance statistics for each process listed in the critical process file. Collected statistics are: CPU ticks, buffered I/O, direct I/O and page faults. This data may be used by a network manager to track the performance of critical processes.

COMTEK$SYSMGR_CRITDSK Critical Disks The critical disk file contains the information that NM∗ SysMgr uses to monitor user specified critical disks. This file allows thresholds to be specified on individual disks; thresholds specified in this file supercede any threshold specified in the COMTEK$SYSMGR_CONFIG configuration file. The thresholds that can be set in this file are: disk space, operations per second and I/O request queue length.

The disk space utilization threshold may be expressed in terms of either percent full or minimum number of free blocks required for the specified disk. If the disk utilization reaches the percent full threshold or the number of free blocks drops below the value specified, NM∗ SysMgr generates a sDskFull trap message. When the disk full situation is later resolved, a sDskFullClear trap message is generated by NM∗ SysMgr.

If a disk exceeds the operations per second threshold in this file, a sDskOpSec trap is generated. If a disk exceeds the I/O request queue length specified in this file, then a sDskIOQLen trap is generated.

The format of this file is:

<diskName>,<utilizationType>=<value>,ops=<value>,qlen=<value>

where <diskName> is the name of the disk that is to be monitored. Disk names may be expressed as either physical disk names (including the leading underscore “_” and trailing colon “:”), as the virtual unit name for a shadow set, or as a logical volume name. <utilizationType> is either percent or blocks with a corresponding utilization value. The ops field is used to specify operations per second values; the qlen field specifies the I/O request queue threshold. For a particular disk, the user may choose to specify any combination of the following: one of the a space utilization limits (either percent or blocks), an operations per second limit, or I/O request queue length.

Examples: _ALPHA$DKA0:,percent=70

specifies that for disk _ALPHA$DKA0: sDskFull traps should be sent when disk utilization exceeds 70 percent of capacity

_DSA1:,blocks=50000,ops=0,qlen=20



specifies that for disk _DSA1: sDskFull traps should begin when less than 50000 blocks of disk space are free and sDskOpSec traps should be disabled for disk _DSA1: and sDskIOQLen traps should be sent when the I/O request queue length exceeds 20.

DISK$USER1,ops=50

specifies sDskOpSec traps should be sent for disk DISK$USER1 when operations exceed 50 per second.

To disable sDskFull traps, set blocks to 0. To disable sDskOpSec traps, set ops to 0. To disable sDskIOQLen traps, omit the qlen parameter. The following entry disables disk full, disk busy and excessive IO queue length traps for this disk.

_I64$DKA100:,blocks=0,ops=0

Each disk entry must be left justified and placed on a separate line. Comments may be inserted in the critical disk file by placing a pound sign (#) as the first character in the line.

NOTE: The <diskName> value is not validated by the NM∗ SysMgr subagent. This value must match exactly either the sDskName or sDskLogVolName in the MIB for the disk.


COMTEK$SYSMGR_CRITQUEUE Critical Queues The critical queue file contains the information that NM∗ SysMgr uses to monitor critical queues and critical jobs. Each line in this file contains the name of a queue to be monitored and an optional list of jobs required in the queue. All queue names and job names are case blind.

The format of this file is <queueName><,jobName> where <queueName> is the name of the queue that is to be monitored and <,jobName> is the name of a job in that queue. For example,

sys$batch,nightly_processing,abc my_queue

specifies that data should be gathered on the queue and its entries for the queues named SYS$BATCH and MY_QUEUE. Jobs named NIGHTLY_PROCESSING and ABC must be found in the SYS$BATCH queue.

Each queue entry must be left justified and placed on a separate line in the file. A comma must preceed each job name listed. Each queue and its required jobs must be listed on a single line in this file. Queue data that



is gathered on monitored queues is specified in the NM∗ SysMgr MIB. Queue and queue entry traps are only generated on queues listed in this file. All other system queues are ignored by NM∗ SysMgr.


COMTEK$SYSMGR_FILTER Operator Message Filters This file contains the filter requirements for Opcom messages. Operation of these filters depends on the setting of the Filter variable in the COMTEK$SYSMGR_CONFIG file. If Filter=dropMatch, opcom messages that match one of the filter enteries will be ignored or dropped - they will not be turned into traps. If Filter=keepMatch, then only those opcom messages that match one of the filters entries will be sent as traps, all other opcom messages will be ignored.

Note that before the filtering process is applied to any Opcom message NM∗ SysMgr strips off the Opcom header, if it is present. The Opcom header is determined to be present if the first line of the message begins with:

%%%%%%%%%%% OPCOM

and ends with:

%%%%%%%%%%%\x0d\x0a

The filter file permits the use of the ∗ wildcard. This wildcard character is used to match one or more characters in the message. The wildcard character must be used carefully to ensure proper filtering. Placing wildcards at the beginning and end of a filter string requires that the string be embedded within the Opcom message, i.e., not at the beginning and not at the end. The following is an example of a filter file:

∗ USERNAME1∗ ∗ TEST MESSAGE Operator * has been *abled, username *

The first entry would match any Opcom message containing the word username1 except where username1 appears at the beginning or end of the Opcom message. The second entry would match any message ending with the words test message. The third entry illustrates the use of multiple wildcards within the same message. This entry would match both messages Operator _SYS1$FTA1: has been enabled, username JONES and Operator _NODE1$FTA2: has been disabled, username SMITH.



Note that entries in the filter file are case insensitive and that each entry must be left justified. A maximum number of 50 filter file entries are permitted and each entry may contain up to 5 substrings delimited by wildcards.

NM∗∗∗∗ SysMgr MIB Objects The NMSERVERVMS.MIB MIB file is supplied for use by network management stations. This file is not accessed by the NMServer for OpenVMS processes.

Below are the objects in the NMSERVERVMS.MIB file that are supported by the NM∗ SysMgr subagent:

System Information Group Node Name Hardware Name System Boot Time System Operating System Version Memory Size Available CPU Count Active CPU Count Page File Size Page File Free Page File Used Percent Swap File Size Swap File Free Swap File Used Percent CPU Page Size System Information Update Time Physical Memory Pages Free Physical Memory Percent Used Summary Condition for System Information (ok, degraded)

CPU Group CPU Percent Used Interrupt Percent Used CPU Interval Timer Ticks Kernel Mode One Minute Ticks Executive Mode One Minute Ticks Supervisor Mode One Minute Ticks User Mode One Minute Ticks Interrupt Mode One Minute Ticks Compatibility Mode One Minute Ticks



Spin Mode One Minute Ticks Null Mode One Minute Ticks Kernel Mode Five Minute Ticks Executive Mode Five Minute Ticks Supervisor Mode Five Minute Ticks User Mode Five Minute Ticks Interrupt Mode Five Minute Ticks Compatibility Mode Five Minute Ticks Spin Mode Five Minute Ticks Null Mode Five Minute Ticks Kernel Mode Fifteen Minute Ticks Executive Mode Fifteen Minute Ticks Supervisor Mode Fifteen Minute Ticks User Mode Fifteen Minute Ticks Interrupt Mode Fifteen Minute Ticks Compatibility Mode Fifteen Minute Ticks Spin Mode Fifteen Minute Ticks Null Mode Fifteen Minute Ticks Summary Condition for CPU (ok, degraded)

Disk Group Number of Disks in Disk Table Last Time the Disk Table was Updated Summary Condition of All Disks (ok, degraded) Disk Table

Disk Table Index Disk Name Used Percent Operations per Second Mount Count Reference Count Transaction Count Media Name Operation Count Number of Free Blocks Maximum Number of Blocks Disk Status Disk Device Characteristics Disk Logical Volume Name Disk Trap Percent Full Threshold Disk Trap Blocks Free Threshold Disk Shadow Count Disk Trap Operations per Second Threshold



Total I/O Request Queue Length Disk Remote Flag Disk Entry Condition (ok, degraded) I/O Request Queue Length Delta Disk’s I/O Request Queue Threshold

Shadow Set Group Shadow Set Table

Shadow Set Table Index Shadow Set Device Name Shadow Set Failure Flag Shadow Set Copy Flag Shadow Set Merge Flag

Queue Group Number of Monitored Queues Last Time the Queue Table was Updated Summary Queue Condition (ok, degraded) Queue Table

Queue Table Index Queue Name Queue Monitoring Status Queue Status Queue Entry Count Critical Job Entry Count

Queue Entry Table Queue Entry Number Job Name Job Status

Batch Queue Pending Count Executing Count Timed Count Holding Count Retained Count

Generic Queue Pending Count Executing Count Timed Count Holding Count Generic Queue Retained Count

Printer Queue Pending Count Executing Count



Timed Count Holding Count Retained Count

Server Queue Pending Count Executing Count Timed Count Holding Count Retained Count

Symbiont Queue Pending Count Executing Count Timed Count Holding Count Retained Count

Terminal Queue Pending Count Executing Count Timed Count Holding Count Retained Count

Queue Manager Count Queue Manager Table Queue Manager Index Queue Manager Name Queue Manager Status Summary Critical Queue Condition (ok, degraded) Summary Critical Job Condition (ok, degraded) Critical Job Table

Critical Job Index Critical Job Name Critical Job Status

Process Group Number of Running Processes Last Time the Process Table was Updated Process Table

Process PID Process Name Process State Priority Direct I/O Count CPU Time Used by the Process



Page Faults Working Set Size Username Physical Terminal Name Image Name Login Time Page Table Count Process Mode Process Resource Wait State

Number of Process in COM State Number of Processes in COMO State Count of Other Processes Count of Network Processes Count of Batch Processes Count of Interactive Processes Number of Available Process Slots Summary Process Statistics Condition (ok, degraded) MWAIT Process Count

Critical Process Group Number of Processes in Critical Process Table Last Time the Critical Process Table was Updated Critical Process Summary Condition (ok, degraded) Critical Process Table

Critical Process Table Index Critical Process Name Required Process Count Current Process Count Buffer I/O CPU Time Direct I/O Page Faults

Trap Group Next Sequence Number Trap Time Resend Sequence Number Last Sequence Number Sent Lost Trap Count Trap Text Table

Trap Sequence Number Trap Timestamp Trap Type Trap Text Part 1



Trap Text Part 2 Trap Text Part 3 Trap Text Part 4 Trap Text Part 5 Trap Text Part 6 Trap Text Part 7

Hardware Error Group Number of Devices in Hardware Error Table Hardware Error Time Hardware Error Table

Hardware Error Table Index Device Name Error Count Last Time Error Detected

Software Error Group Status Code File Name Line Number Last Time Message

Opcom Group Message Part One Message Part Two Message Part Three Message Part Four Message Part Five Reply Id Reply Status Reply Text Reply Send Flag Message Part Six Message Part Seven

Configuration Group Configuration File Name Log File Name Critical Process File Name Reinitialization Flag Traps Enabled Flag Hardware Error Traps Enabled Flag CPU Limit Interrupt Limit



Disk Operations per Second Limit Disk Percent Used Limit Page File Limit Swap File Limit Process Statistics Timer Disk Timer Hardware Error Timer System Information Timer Critical Process Timer Disk Repeat Alarm Timer Critical Process Repeat Alarm Timer Trap Table Size Host Name All Process Statistics Data Flag Time-out Opcom Security Flag Process Termination Control Flag Terminate Process NM∗ SysMgr Subagent Version Subagent Up Time Maximum Traps per Second Critical Disk File Name Critical Queue File Name Critical Queue Timer Minimum Free Disk Blocks Physical Memory Utilization Limit COM Queue Limit COMO Queue Limit Opcom Cards Flag Opcom Central Flag Opcom Cluster Flag Opcom Devices Flag Opcom Disks Flag Opcom License Flag Opcom Network Flag Opcom Oper1 Flag Opcom Oper2 Flag Opcom Oper3 Flag Opcom Oper4 Flag Opcom Oper5 Flag Opcom Oper6 Flag Opcom Oper7 Flag Opcom Oper8 Flag



Opcom Oper9 Flag Opcom Oper10 Flag Opcom Oper11 Flag Opcom Oper12 Flag Opcom Printer Flag Opcom Tapes Flag Opcom Filter File Flag Local Disks Only Flag Critical Disks Only Flag CPU Threshold Persistance Count MWAIT Process Limit

NM∗∗∗∗ SysMgr Traps The following information provides an overview of the traps that may be generated by the NM∗ SysMgr subagent. Refer to the NMSERVERVMS.MIB file for a complete description of each trap, the variables that accompany it, and the circumstances under which it may be generated.

Enterprise Specific Traps Trap Description sColdStart(0) NM∗ SysMgr has completed a cold start. sSwErr(1) A software error was encountered by

NM∗ SysMgr. sHwErr(2) A hardware error was detected. sCpuUsage(3) CPU utilization exceeds the user-

specified threshold. sIntUsage(4) CPU utilization by interrupts exceeds

the user-specified threshold. sDskOpsSec(5) Disk operations per second exceed the

user-specified threshold. sDskFull(6) Disk utilization exceeds the user-

specified threshold. sDskFullClear(7) Disk utilization has dropped below the

user-specified threshold. sSwpFull(8) Swap file utilization exceeds the user-

specified threshold. sSwpFullClear(9) Swap file utilization has dropped below

the user-specified threshold. sPgFull(10) Page file utilization exceeds the user-

specified threshold.



sPgFullClear(11) Page file utilization has dropped below the user-specified threshold.

sCriticalProcessMissing(12) Too few instances of the specified process are running on the system.

sOpcomMessage(13) Operator log message. sTermProc(14) NM∗ SysMgr process termination. sDskStat(15) Disk status has transitioned into or out

of one of the following states: power fail while unit busy, time out, or mount verification in progress.

sWarmStart(16) NM∗ SysMgr has completed reinitialization.

sShdFailStatus(17) Shadow set member failure status has changed.

sShdCopyStatus(18) Shadow set member copy status has changed.

sShdMergeStatus(19) Shadow set member merge copy status has changed.

sQueStatusChange(20) Status of monitored queue has transitioned into or out of paused, stalled, starting, stopped or disabled state.

sQEntryStatusChange(21) Queue entry status has tranistioned into or out of aborting, refused, or stalled state.

sProcStatusChange(22) Process status has transitioned into or out of MWAIT state.

sMemFull(23) Physical memory utilization exceeds the user-specified threshold.

sMemClear(24) Physical memory utilization has dropped below the user-specified threshold.

sCOMQue(25) Number of processes in COM state has reached or exceeded the user-specified threshold.

sCOMOQue(26) Number of processes in COMO state has reached or exceeded the user-specified threshold.

sCritProcClear(27) Critical process missing clearing trap. Critical process is no longer missing.

sDskIOQLen(28) Disk I/O request queue has exceeded the user-specified threshold for that disk.

sCritJobMissing(29) A user-specified critical job is not present in its queue.



sMWAITExcessive(30) Too many processes are in MWAIT state.



5 NM∗∗∗∗ TrpMgr Subagent

The NM∗ TrpMgr subagent provides a mechanism by which users can send textual data as SNMP traps. NM∗ TrpMgr reads user data from an OpenVMS mailbox, converts the message into a trap message and sends the message to the master agent (DPI or eSNMP) for transmission to the SNMP manager(s).

NM∗ TrpMgr provides six OpenVMS mailboxes for users to place text messages in: five mailboxes for severity coded trap messages and one mailbox for generic trap messages. The five severity coded mailboxes correspond to the OpenVMS severity coding message scheme: success, informational, warning, error and fatal. The users may define filtering criteria for messages placed in the generic trap mailbox.

Note: Trap messages generated by other NMServer subagents do not pass through this subagent. This subagent only handles user trap data.

NM∗∗∗∗ TrpMgr Subagent Operation Privileges

Privilege Description NETMBX May create a network device PRMMBX May create permanent mailboxes SYSNAM May insert in system logical name table

Required Logical Names The following logical names are required by NM∗ TrpMgr.

• COMTEK$TRPMGR_CODE - Identifies the location (device and directory) of the code for the NM∗ TrpMgr subagent. This name must be in the system logical name table.

• COMTEK$TRPMGR_CONFIG - Identifies the configuration file for the NM∗ TrpMgr subagent. The actual file used may be changed while NM∗ TrpMgr is running by setting the MIB variable tCfgFile.0 to the new file name and then setting the variable tCfgReinitSubagent.0 to 1 (TRUE). The MIB variable



tCfgFile.0 contains the subagent's most recent translation of this logical name. This name must be in the system logical name table.

• COMTEK$TRPMGR_FILTER - Identifies the file containing user trap filtering data. To alter the filter data while NM∗ TrpMgr is running, edit this file and set the MIB variable tCfgReinitSubagent.0 to 1 (TRUE). This will cause the filter data to be reinitialized from the filter file.


NM∗ TrpMgr provides a MIB variable which allows the equivalence-name for COMTEK$TRPMGR_CONFIG to be modified. To make changes to this logical name permanent across system reboots, the equivalence-name in the system startup procedures must also be changed.



defines the symbols that may be used to start the NMServer processes. To run the NM∗ TrpMgr process, enter the following commands:

$ @comtek_root:[comtek$snmp.com]nmserver_symbols $ trpmgr

The command trpmgr starts the process NM∗ TrpMgr as a detached process. If the NM∗ TrpMgr process fails to start, examine the output file for the process to determine the cause of the problem. This file may be found in the COMTEK$TRPMGR_CODE directory.

To stop the detached process, either use the MIB variable tCfgTermProc.0, as described in the MIB, or use the OpenVMS stop command:


The NM∗ TrpMgr subagent may also be started attached to the user's terminal with debug information enabled. Enter the following command:

$ trpmgr -d <n>

where <n> is an optional debug level of 1, 2 or 3. In a DPI environment, level 1 provides a display of DPI packet creation and parsing and levels 2 and 3 provide a hex dump of the incoming and outgoing DPI packets. In an eSNMP environment, level 1 displays eSNMP error messages, level 2



displays eSNMP error and warning messages and level 3 displays eSNMP error, warning and trace messages. By default, level 1 is assumed if no value is provided following the –d.

Process Reinitialization Use the following reinitialization command procedure to cause the NM*TrpMgr process to re-read data from its configuration files:

$ @comtek_root:[comtek$snmp.com]reinit_nmserver NM*TrpMgr

NM∗∗∗∗ TrpMgr Process Configuration Files COMTEK$TRPMGR_CONFIG Configuration File This configuration file is read by NM∗ TrpMgr when the process is started. This file is identified by the logical name:

COMTEK$TRPMGR_CONFIG

If this logical name is not defined when the subagent is started, the process will terminate with an error. If a set-request is performed on the MIB variable tCfgFile.0, the specified file name must exist and be accessible to NM∗ TrpMgr for the set-request to be successful. NM∗ TrpMgr must be reinitialized by setting the variable tCfgReinitSubagent.0 to 1 (TRUE) for the new file to take effect.

The following is an example of a configuration file: Community=public ControlTermProc=disabled Host=sammy.comtek.com MaxTrapSec=0 Timeout=5 Traps=enabled TrapTableSize=100

The format of the file is a left justified variable name followed by an '=' without intervening spaces or tabs. The variable names may be expressed in upper, lower or mixed case. If one of the optional variables is missing, misspelled, or has an invalid value, a warning message is written to the process' log file and a default value for the variable is used. Most of the configuration file variables have MIB equivalents. For any corresponding MIB variable that is read-write accessible, new values supplied via set-requests are saved to the current configuration disk file. See below for MIB equivalents, optional variables and default values. Comments may be



inserted in the configuration file by placing a pound sign (#) as the first character in the line.

Community=This variable sets the community string to be used by NM∗ TrpMgr when initiating communications with NM∗ Master. NOTE: This value must correspond to an entry in the NM∗ Master agent's community file, identified by the logical name COMTEK$MAS-TER_COMM for the subagent's IP Address. This variable is not used in the eSNMP environment.

Attributes Values NMTrpMgr MIB Variable Not applicable Required/Optional Optional Default Value public Set-requests Not permitted

ControlTermProc=This variable controls the use of the variable tCfgTermProc.0. If this variable is set to DISABLED, sets of the variable tCfgTermProc.0 are not allowed, thereby disabling the ability to terminate the NM∗ TrpMgr process programmatically. If this variable is set to ENABLED, process termination may be initiated via the variable tCfgTermProc.0. This MIB item is read-only, meaning that this value may only be changed via the configuration file.

Attributes Values NMTrpMgr MIB Variable tCfgControlTermProc.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value DISABLED Set-requests Not permitted


Attributes Values NMTrpMgr MIB Variable tCfgHostName.0 Required/Optional Optional Default Value localhost Set-requests Not permitted





MaxTrapSec=This variable controls the maximum number of traps per second that may be transmitted by the NM∗ TrpMgr subagent.

Variable Values NMTrpMgr MIB Variable tCfgMaxTrapSec.0 Required/Optional Optional Valid Values 0-100 Default Value 0 Set-requests Take effect immediately

Timeout= This variable specifies the amount of time the master agent will wait for the subagent to respond to SNMP requests. In the DPI environment, if this value is not specified, the default value saDefaultTimeout contained in the NM∗ Master agent will be used. If the value specified exceeds the current maximum that the NM∗ Master agent will permit (saMaxTimeout), the maximum value will be used. In the eSNMP environment, valid values range from 0 to 10. If a value of zero is specified, the eSNMP master agent will wait 3 seconds for the subagent’s response. This value is specified in seconds.

Attributes Values NMTrpMgr MIB Variable tCfgTimeout.0 Required/Optional Optional Valid Values 0-3600 Default Value 0 Set-requests Take effect at process startup

Traps=This variable determines whether any traps are sent. If this variable is set to ENABLED, all traps are sent. If this variable is set to DISABLED, no traps are sent.

Attributes Values NMTrpMgr MIB Variable tCfgTraps.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect immediately

TrapTableSize=This variable sets the number of trap messages which are to be retained in the NM∗ TrpMgr internal trap table. The trap table is



a circular table containing a copy of traps sent by the NM∗ TrpMgr. This value specifies the maximum number of messages in that table. Once the maximum number of messages in the table has been reached, the oldest messages are overwritten by new trap messages.

Attributes Values NMTrpMgr MIB Variable tCfgTrapTblSize.0 Required/Optional Optional Valid Values 10..5000 Default Value 100 Set-requests Take effect immediately

COMTEK$TRPMGR_FILTER User Trap Filters The user trap filter file identifies user trap messages that are to be discarded by the NM∗ TrpMgr subagent rather than sent as user data traps. Filters only apply to messages read from the COMTEK$USER_TRAP generic message mailbox. Each user message that is received by NM∗ TrpMgr is compared to the entries in the file identified by the logical name COMTEK$TRPMGR_FILTER. If the message is found to match one of the entries in the filter file, the message is discarded. If the message does not match any of the entries in the filter file, the message is sent as a user trap. See COMTEK$SYSMGR_FILTER Operator Message Filter File for a description of the syntax and usage of the filter file data.

NM∗∗∗∗ TrpMgr MIB Objects The NMSERVERVMS.MIB file includes object definitions that are supported by the NM∗ TrpMgr subagent process.

Trap Group Next Sequence Number Trap Time Resend Sequence Number Flag User Message Part One User Message Part Two User Message Part Three User Message Part Four User Message Part Five Last Sequence Number Sent Trap Lost Count User Message Part Six



User Message Part Seven Success Trap Message Identifier Success Trap Message Informational Trap Message Identifier Informational Trap Message Warning Trap Message Identifier Warning Trap Message Error Trap Message Identifier Error Trap Message Fatal Trap Message Identifier Fatal Trap Message


Configuration Group Configuration File Name Log File Name Reinitialization Flag Traps Enabled Flag Trap Table Size Host Name Time-out Control Process Termination Flag Terminate Process Flag NM∗ TrpMgr Subagent Version Subagent Up Time Maximum Traps per Second

NM∗∗∗∗ TrpMgr Traps The following information provides an overview of the traps that may be generated by the NM∗ TrpMgr subagent. Refer to NMSERVERVMS.MIB for a complete description of each trap, the variables that accompany it, and the circumstances under which it may be generated. See Chapter 9 of this manual for more information about NMServer traps.



Enterprise Specific Traps Trap Description tColdStart(0) NM∗ TrpMgr has completed a cold start. tSwErr(1) A software error was encountered by

NM∗ TrpMgr. tUsrTrp(2) Message from user process. tTermProc(3) NM∗ TrpMgr subagent process termination. tWarmStart(4) NM∗ TrpMgr has completed a reinitialization. tSevSuccess(5) Severity success trap. tSevInformational(6) Severity informational trap. tSevWarning(7) Severity warning trap. tSevError(8) Severity error trap. tSevFatal(9) Severity fatal trap.

Example: NM∗∗∗∗ TrpMgr Mailbox Interface Below are two methods that illustrate writing data to the NM∗ TrpMgr subagent’s OpenVMS mailbox. The system logical name for the NM∗ TrpMgr mailbox is COMTEK$USER_TRAP.

DCL Command Procedure To access the COMTEK$USER_TRAP mailbox from a DCL command procedure, create a file which contains the following:

$ OPEN/WRITE USR_TRP_MBX COMTEK$USER_TRAP $ WRITE USR_TRP_MBX P1 $ CLOSE USR_TRP_MBX

To write a message to the mailbox, invoke the command procedure and place the message text in quotes. For example, if the above command procedure is called WRITEMBX.COM:

$ @WRITEMBX "This is the text to be sent as a trap."

SEND_SEVERITY_TRAP.COM Command Procedure The send_severity_trap.com command procedure can be found in the directory COMTEK_ROOT:[COMTEK$SNMP.COM]. This command procedure expects a single parameter: the text message that is to be sent as a trap. The text message should be enclosed in double quotes. If the text message begins with a VMS message identifier in the form %FAC-S-IDENT, the message will be placed in the appropriate in severity coded mailbox. For example, the following command:

$ @SEND_SEVERITY_TRAP –



“%SYSTEM-F-NOLOGNAM, no logical name match”

would result in this message being sent as a fatal severity coded trap message.

Messages sent to this command procedure that do not begin with a message identifier are placed in the COMTEK$USER_TRAP generic user message mailbox.

C Program Example The following example C program writes a message into the NM∗ TrpMgr subagent’s OpenVMS mailbox. Each message that is placed in this mailbox is sent to the SNMP manager as a user trap message (tUsrTrp).

#include <cmbdef.h> #include <descrip.h> #include <iodef.h> #include <ssdef.h> #include <stdio.h> #include <stdlib.h> #include <string.h> #include <stsdef.h>

extern int SYS$CREMBX(); extern int SYS$QIOW();

main() { #define PERMANENT_MBX 1 int channel, status; unsigned short iosb[4]; char trpBuffer[] = "Test Message."; $DESCRIPTOR(usrTrpMbx_dsc, "COMTEK$USER_TRAP");

status = SYS$CREMBX(PERMANENT_MBX, &channel, 0, 0, 0, 0, &usrTrpMbx_dsc, CMB$M_WRITEONLY);

if (status & STS$M_SUCCESS) {

status = SYS$QIOW(0, channel, IO$_WRITEVBLK|IO$M_NOW, &iosb, 0, 0, trpBuffer, strlen(trpBuffer), 0, 0, 0, 0);

} exit(status); }



6 NM∗∗∗∗ Console Subagent

The NM∗ Console subagent provides a method for sending commands to the OpenVMS system from an SNMP manager. To send a command to the managed system, the SNMP manager performs a SNMP set-request on the remote console command MIB variable. NM∗ Console starts a detached process to perform the requested command and sends any results generated by the command (the process output file) to the SNMP manager as a series of SNMP traps. Multiple remote console commands may be active simultaneously. This subagent does not interact with the other NMServer subagents; therefore, NMServer startup can be modified to remove starting of this subagent process without effecting the other NMServer processes.

NM∗∗∗∗ Console Subagent Operation Privileges

Privilege Description DETACH May create detached processes NETMBX May create a network device PRMMBX May create permanent mailboxes SYSNAM May insert in system logical name table

By default, the privileges enabled for the NM∗ Console process are available to the detached process that is created for each NM∗ Console command. In addition, all remote console commands are started with the comtek$snmp UIC. If additional privileges are required to execute remote console commands, the process startup file comtek_root:[com-tek$snmp.code]console.com may be modified to enable the additional privileges on NM∗ Console startup. If additional privileges are added to the NM∗ Console process, they must also be valid for the comtek$snmp UIC.



Required Logical Names The following logical names are required by NM∗ Console.

• COMTEK$CONSOLE_CODE - Identifies the location (device and directory) of the code for NM∗ Console. This name must be in the system logical name table.

• COMTEK$CONSOLE_CONFIG - Identifies the configuration file for the NM∗ Console subagent. The actual file used may be changed while NM∗ Console is running by setting the MIB variable cCfgFile.0 to the new file name and then setting the variable cCfgReinitSubagent.0 to 1 (TRUE). The MIB variable cCfgFile.0 contains the subagent's most recent translation of this logical name. This name must be in the system logical name table.

• COMTEK$CONSOLE_DATA - Identifies the device and directory where the NM∗ Console subagent will write temporary files generated during remote console command processing. These files are deleted when command processing is completed. The NM∗ Console subagent must have read, write, execute, and delete access to this directory.


NM∗ Console provides a MIB variable which allows the equivalence-name for COMTEK$CONSOLE_CONFIG to be modified. To make changes to this logical name permanent across system reboots, the equivalence-name in the system startup procedures must also be changed.



defines the symbols that may be used to start the NMServer processes. To run the NM∗ Console process, enter the following commands:

$ @comtek_root:[comtek$snmp.com]nmserver_symbols $ console

The command console starts the process NM∗ Console as a detached process. If the NM∗ Console process fails to start, examine the output file for the process to determine the cause of the problem. This file may be found in the COMTEK$CONSOLE_CODE directory.



To stop the detached process, either use the MIB variable cCfgTermProc.0, as described in the MIB, or use the OpenVMS stop command:


The NM∗ Console subagent may also be started attached to the user's terminal with debug information enabled. Enter the following command:

$ console -d <n>


Process Reinitialization Use the following reinitialization command procedure to cause the NM*Console process to re-read data from its configuration files:

$ @comtek_root:[comtek$snmp.com]reinit_nmserver NM*Console

Remote Console Command Format NM∗ Console accepts commands to be executed in the following format:

<tag> <DCL command><process qualifiers>

<tag> is used as an identifier that accompanies the traps that result from the command execution. The tag facilitates matching command results with the entered command. <DCL command> is the DCL command to be executed and any associated parameters or qualifiers of the command. The DCL command must be enclosed in angled brackets (<>). <process qualifiers> identifies any qualifiers that are to be placed on the detached process $ RUN command. All process qualifiers must start with a slash (/) and no intervening spaces may be present between qualifiers. The <process qualifiers> field is optional.

The following are examples of valid NM∗ Console commands: tag1 <dir/full COMTEK$CONSOLE_CODE> abcd <sh proc/priv> jones <run sys$sysdevice:[code]appl23>/enque=150/file=200

In the command tagged tag1, a full directory listing is requested for the directory COMTEK$CONSOLE_CODE. Each trap that is generated for



this command has the tag tag1 assigned to it. In the command tagged abcd, the process privileges for the detached process are returned as the results with each trap tagged with abcd. In the final example, the tag jones is associated with the detached process which runs appl23. In this example the enqueue_limit and file_limit qualifiers are passed to the detached process.

The NM∗ Console subagent runs as a detached process SYS$SYS-TEM:LOGINOUT passing the entered DCL command as the input to the detached process. The results of the command execution are captured in a file that is transmitted as a series of traps to each SNMP manager that has been configured as a trap destination by the master agent. Each line in the file is sent as a separate trap message and the file is deleted when all of the traps have been sent.

Since this subagent has the potential for generating large bursts of traps, important consideration should be given to the values configured for the trap throttle variable MaxTrapSec and the size of the internal trap table variable TrapTableSize in the NM∗ Console configuration file COMTEK$CONSOLE_CONFIG to prevent these traps from flooding the network or from being lost.

NM∗∗∗∗ Console Process Configuration Files COMTEK$CONSOLE_CONFIG Configuration File This configuration file is read by the NM∗ Console subagent when the process is started. This file is identified by the logical name:

COMTEK$CONSOLE_CONFIG

If this logical name is not defined when the subagent is started, the process will terminate with an error. If a set-request is performed on the MIB variable cCfgFile.0, the specified file name must exist and be accessible to NM∗ Console for the set-request to be successful. NM∗ Console must be reinitialized by setting the variable cCfgReinitSubagent.0 to 1 (TRUE) for the new file to take effect.

The following is an example of a NM∗ Console configuration file: Community=public ControlTermProc=disabled Host=sammy.comtek.com MaxCommands=5 MaxTrapSec=0 Timeout=5



Traps=enabled TrapTableSize=100

The format of the file is a left justified variable name followed by an '=' without intervening spaces or tabs. The variable names may be expressed in upper, lower or mixed case. If one of the optional variables is missing, misspelled, or has an invalid value, a warning message is written to the process' log file and a default value for the variable is used. Most of the configuration file variables have MIB equivalents. For any corresponding MIB variable which is read-write accessible, new values which are supplied via set-requests are saved to the current configuration disk file. See below for MIB equivalents, optional variables and default values. Comments may be inserted in the configuration file by placing a pound sign (#) as the first character in the line.

Community=This variable sets the community string to be used by the NM∗ Console subagent when initiating communications with the NM∗ Master agent. NOTE: This value must correspond to an entry in the NM∗ Master agent's community file COMTEK$MASTER_COMM for the subagent's IP Address. This variable is not used in the eSNMP environment.

Attributes Values NMConsole MIB Variable Not applicable Required/Optional Optional Default Value public Set-requests Not permitted

ControlTermProc=This variable controls the use of the variable cCfgTermProc.0. If this variable is set to DISABLED, sets of the variable cCfgTermProc.0 are not allowed, thereby disabling the ability to terminate the NM∗ Console process programmatically. If this variable is set to ENABLED, process termination may be initiated via the variable cCfgTermProc.0. This MIB item is read-only, meaning that this value may only be changed via the configuration file.

Attributes Values NMConsole MIB Variable cCfgControlTermProc.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value DISABLED Set-requests Not permitted




Attributes Values NMConsole MIB Variable cCfgHostName.0 Required/Optional Optional Default Value localhost Set-requests Not permitted



MaxCommands=This variable controls the maximum number of simultaneous remote console commands that may be active at any given time.

Attributes Values NMConsole MIB Variable cCfgMaxConsoleCmds.0 Required/Optional Optional Valid Values 1-100 Default Value 5 Set-requests Take effect at process startup

MaxTrapSec=This variable controls the maximum number of traps per second that may be transmitted by the NM∗ Console subagent.

Attributes Values NMConsole MIB Variable cCfgMaxTrapSec.0 Required/Optional Optional Valid Values 0-100 Default Value 0 Set-requests Take effect immediately

Timeout= This variable specifies the amount of time the master agent will wait for the subagent to respond to SNMP requests. In the DPI environment, if this value is not specified, the default value saDefaultTimeout contained in the NM∗ Master agent will be used. If the value specified exceeds the current maximum that the NM∗ Master agent will permit (saMaxTimeout), the maximum value will be used. In the



eSNMP environment, valid values range from 0 to 10. If a value of zero is specified, the eSNMP master agent will wait 3 seconds for the subagent’s response. This value is specified in seconds.

Attributes Values NMConsole MIB Variable cCfgTimeout.0 Required/Optional Optional Valid Values 0-3600 Default Value 0 Set-requests Take effect at process startup


Attributes Values NMConsole MIB Variable cCfgTraps.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect immediately

TrapTableSize=The number of trap messages that are to be retained in the NM∗ Console internal trap table. The trap table is a circular table containing a copy of traps sent by the NM∗ Console. This value specifies the maximum number of messages in that table. Once the maximum number of messages in the table has been reached, the oldest messages are overwritten by new trap messages.

Attributes Values NMConsole MIB Variable cCfgTrapTblSize.0 Required/Optional Optional Valid Values 10..5000 Default Value 100 Set-requests Take effect immediately

NM∗∗∗∗ Console MIB Objects The NMSERVERVMS.MIB file includes MIB object definitions that are supported by the NM∗ Console subagent.

Remote Console Command Group Remote Console Command Command Tag



Command Output Count of Currently Executing Commands

Trap Group Next Sequence Number Trap Time Resend Sequence Number Flag Last Sequence Number Sent Trap Lost Count


Configuration Group Configuration File Name Log File Name Reinitialization Flag Traps Enabled Flag Trap Table Size Host Name Time-out Maximum Number of Concurrent Commands Control Process Termination Flag Terminate Process Flag NM∗ Console Subagent Version Subagent Up Time Maximum Traps per Second

NM∗∗∗∗ Console Traps The following information provides an overview of the traps that may be generated by the NM∗ Console subagent. Refer to NMSERVERVMS.MIB for a complete description of each trap, the variables that accompany it, and the circumstances under which it may be generated. See Chapter 9 of this manual for more information about NMServer traps.

Enterprise Specific Traps Trap Description cColdStart(0) NM∗ Console has completed cold start.



cWarmStart(1) NM∗ Console has completed reinitialization. cSwErr(2) A software error was encountered by

NM∗ Console. cTermProc(3) NM∗ Console process termination. cConsoleResult(4) NM∗ Console command result.



7 NM∗∗∗∗ Opcom Subagent

The NM∗ Opcom subagent converts OpenVMS operator communication (opcom) messages into SNMP traps. NM∗ Opcom may be configured to enable any combination of opcom message classes (TAPES, SECURITY, etc.). NM∗ Opcom reads each opcom message received from the OpenVMS OPCOM process, compares the message to user-defined filtering criteria, converts the message into a trap message and sends the message to the master agent (DPI or eSNMP) for transmission to the SNMP manager(s).

NM∗∗∗∗ Opcom Subagent Operation Privileges

Privilege Description NETMBX May create a network device PRMMBX May create permanent mailboxes OPER May perform operator functions SECURITY May perform security functions SYSNAM May insert in system logical name table

Required Logical Names The following logical names are required by NM∗ Opcom.

• COMTEK$NMOPCOM_CODE - Identifies the location (device and directory) of the code for the NM∗ Opcom subagent. This name must be in the system logical name table.

• COMTEK$NMOPCOM_CONFIG - Identifies the configuration file for the NM∗ Opcom subagent. The actual file used may be changed while NM∗ Opcom is running by setting the MIB variable oCfgFile.0 to the new file name and then setting the variable oCfgReinitSubagent.0 to 1 (TRUE). The MIB variable oCfgFile.0 contains the subagent's most recent translation of this logical name. This name must be in the system logical name table.



• COMTEK$NMOPCOM_FILTER - Identifies the file containing opcom message filtering data. To alter the filter data while NM∗ Opcom is running, edit the file and make the changes to the file and then set the MIB variable oCfgReinitSubagent.0 to 1 (TRUE). This will cause the filter data to be reinitialized from the filter file.


NM∗ Opcom provides a MIB variable which allows the equivalence-name for COMTEK$NMOPCOM_CONFIG to be modified. To make changes to this logical name permanent across system reboots, the equivalence-name in the system startup procedures must also be changed.



defines the symbols that may be used to start the NMServer processes. To run the NM∗ Opcom process, enter the following commands:

$ @comtek_root:[comtek$snmp.com]nmserver_symbols $ nmopcom

The command nmopcom starts the process NM∗ Opcom as a detached process. If the NM∗ Opcom process fails to start, examine the output file for the process to determine the cause of the problem. This file may be found in the COMTEK$NMOPCOM_CODE directory.

To stop the detached process, either use the MIB variable oCfgTermProc.0, as described in the MIB, or use the OpenVMS stop command:


The NM∗ Opcom subagent may also be started attached to the user's terminal with debug information enabled. Enter the following command:

$ nmopcom -d <n>

where <n> is an optional debug level of 1, 2 or 3. In a DPI environment, level 1 provides a display of DPI packet creation and parsing and levels 2 and 3 provide a hex dump of the incoming and outgoing DPI packets. In an eSNMP environment, level 1 displays eSNMP error messages, level 2 displays eSNMP error and warning messages and level 3 displays



eSNMP error, warning and trace messages. By default, level 1 is assumed if no value is provided following the –d.

Process Reinitialization Use the following reinitialization command procedure to cause the NM*Opcom process to re-read data from its configuration files:

$ @comtek_root:[comtek$snmp.com]reinit_nmserver NM*Opcom

NM∗∗∗∗ Opcom Process Configuration Files COMTEK$NMOPCOM_CONFIG Configuration File This configuration file is read by NM∗ Opcom when the process is started. This file is identified by the logical name:

COMTEK$NMOPCOM_CONFIG

If this logical name is not defined when the subagent is started, the process will terminate with an error. If a set-request is performed on the MIB variable oCfgFile.0, the specified file name must exist and be accessible to NM∗ Opcom for the set-request to be successful. NM∗ Opcom must be reinitialized by setting the variable oCfgReinitSubagent.0 to 1 (TRUE) for the new file to take effect.

The following is an example of a configuration file: Community=public ControlTermProc=disabled Filter=dropMatch Host=sammy.comtek.com MaxTrapSec=0 OpcomCards=enabled OpcomCentral=enabled OpcomCluster=enabled OpcomDevices=enabled OpcomDisks=enabled OpcomLicense=enabled OpcomNetwork=enabled OpcomOper1=enabled OpcomOper2=enabled OpcomOper3=enabled OpcomOper4=enabled OpcomOper5=enabled OpcomOper6=enabled



OpcomOper7=enabled OpcomOper8=enabled OpcomOper9=enabled OpcomOper10=enabled OpcomOper11=enabled OpcomOper12=enabled OpcomPrinter=enabled OpcomSecurity=enabled OpcomTapes=enabled Timeout=5 Traps=enabled TrapTableSize=100

The format of the file is a left justified variable name followed by an '=' without intervening spaces or tabs. The variable names may be expressed in upper, lower or mixed case. If one of the optional variables is missing, misspelled, or has an invalid value, a warning message is written to the process' log file and a default value for the variable is used. Most of the configuration file variables have MIB equivalents. For any corresponding MIB variable that is read-write accessible, new values supplied via set-requests are saved to the current configuration disk file. See below for MIB equivalents, optional variables and default values. Comments may be inserted in the configuration file by placing a pound sign (#) as the first character in the line.

Community=This variable sets the community string to be used by NM∗ Opcom when initiating communications with NM∗ Master. NOTE: This value must correspond to an entry in the NM∗ Master agent's community file, identified by the logical name COMTEK$MAS-TER_COMM for the subagent's IP Address. This variable is not used in the eSNMP environment.

Attributes Values NMOpcom MIB Variable Not applicable Required/Optional Optional Default Value public Set-requests Not permitted

ControlTermProc=This variable controls the use of the variable oCfgTermProc.0. If this variable is set to DISABLED, sets of the variable oCfgTermProc.0 are not allowed, thereby disabling the ability to terminate the NM∗ Opcom process programmatically. If this variable is set to ENABLED, process termination may be initiated via the variable



oCfgTermProc.0. This MIB item is read-only, meaning that this value may only be changed via the configuration file.

Attributes Values NMOpcom MIB Variable oCfgControlTermProc.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value DISABLED Set-requests Not permitted

Filter=This variable controls whether NM∗ Opcom drops opcom messages that match records in the filter file (DROPMATCH) or if it forwards only those messages that match (KEEPMATCH) a record in the filter file and drops all other messages.

Attributes Values NMOpcom MIB Variable oCfgFilter.0 Required/Optional Optional Valid Values DROPMATCH, KEEPMATCH Default Value DROPMATCH Set-requests Take effect at process startup


Attributes Values NMOpcom MIB Variable oCfgHostName.0 Required/Optional Optional Default Value localhost Set-requests Not permitted



MaxTrapSec=This variable controls the maximum number of traps per second that may be transmitted by the NM∗ Opcom subagent.



Variable Values NMOpcom MIB Variable oCfgMaxTrapSec.0 Required/Optional Optional Valid Values 0-100 Default Value 0 Set-requests Take effect immediately

OpcomCards=This variable controls whether NM∗ Opcom is enabled to receive operator CARDS class messages. This variable is like performing a $ REPLY/ENABLE=CARDS for the NM∗ Opcom process.

Attributes Values NMOpcom MIB Variable oOpcomCfgCards.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomCentral=This variable controls whether NM∗ Opcom is enabled to receive operator CENTRAL class messages. This variable is like performing a $ REPLY/ENABLE=CENTRAL for the NM∗ Opcom process.

Attributes Values NMOpcom MIB Variable oOpcomCfgCentral.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomCluster=This variable controls whether NM∗ Opcom is enabled to receive operator CLUSTER class messages. This variable is like performing a $ REPLY/ENABLE=CLUSTER for the NM∗ Opcom process.

Attributes Values NMOpcom MIB Variable oOpcomCfgCluster.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup



OpcomDevices=This variable controls whether NM∗ Opcom is enabled to receive operator DEVICES class messages. This variable is like performing a $ REPLY/ENABLE=DEVICES for the NM∗ Opcom process.

Attributes Values NMOpcom MIB Variable oOpcomCfgDevices.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomDisks=This variable controls whether NM∗ Opcom is enabled to receive operator DISKS class messages. This variable is like performing a $ REPLY/ENABLE=DISKS for the NM∗ Opcom process.

Attributes Values NMOpcom MIB Variable oOpcomCfgDisks.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomLicense=This variable controls whether NM∗ Opcom is enabled to receive operator LICENSE class messages. This variable is like performing a $ REPLY/ENABLE=LICENSE for the NM∗ Opcom process.

Attributes Values NMOpcom MIB Variable oOpcomCfgLicense.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomNetwork=This variable controls whether NM∗ Opcom is enabled to receive operator NETWORK class messages. This variable is like performing a $ REPLY/ENABLE=NETWORK for the NM∗ Opcom process.



Attributes Values NMOpcom MIB Variable oOpcomCfgNetwork.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomOper1=This variable controls whether NM∗ Opcom is enabled to receive operator OPER1 class messages. This variable is like performing a $ REPLY/ENABLE=OPER1 for the NM∗ Opcom process.

Attributes Values NMOpcom MIB Variable oOpcomCfgOper1.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup









OpcomPrinter=This variable controls whether NM∗ Opcom is enabled to receive operator PRINTER class messages. This variable is like performing a $ REPLY/ENABLE=PRINTER for the NM∗ Opcom process.

Attributes Values NMOpcom MIB Variable oOpcomCfgPrinter.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomSecurity=This variable controls whether NM∗ Opcom is enabled to receive operator SECURITY class messages. This variable is like performing a $ REPLY/ENABLE=SECURITY for the NM∗ Opcom process.

Attributes Values NMOpcom MIB Variable oOpcomCfgSecurity.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup

OpcomTapes=This variable controls whether NM∗ Opcom is enabled to receive operator TAPES class messages. This variable is like performing a $ REPLY/ENABLE=TAPES for the NM∗ Opcom process.

Attributes Values NMOpcom MIB Variable oOpcomCfgTapes.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect at process startup




Attributes Values NMOpcom MIB Variable oCfgTimeout.0 Required/Optional Optional Valid Values 0-3600 Default Value 0 Set-requests Take effect at process startup


Attributes Values NMOpcom MIB Variable oCfgTraps.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect immediately

TrapTableSize=This variable sets the number of trap messages which are to be retained in the NM∗ Opcom internal trap table. The trap table is a circular table containing a copy of traps sent by the NM∗ Opcom. This value specifies the maximum number of messages in that table. Once the maximum number of messages in the table has been reached, the oldest messages are overwritten by new trap messages.

Attributes Values NMOpcom MIB Variable oCfgTrapTblSize.0 Required/Optional Optional Valid Values 10..5000 Default Value 100 Set-requests Take effect immediately



COMTEK$NMOPCOM_FILTER Opcom Trap Filters If the NM∗ Opcom configuration file parameter FILTER indicates dropMatch, the opcom trap filter file identifies opcom messages that are to be discarded by the NM∗ Opcom subagent rather than sent as opcom traps. Each opcom message that is received by NM∗ Opcom is compared to the entries in the file identified by the logical name COMTEK$NMOPCOM_FILTER. If the message is found to match one of the entries in the filter file, the message is discarded. If the message does not match any of the entries in the filter file, the message is sent as an opcom trap.

If the NM∗ Opcom configuration file FILTER parameter indicates keepMatch, then only the opcom messages that match a filter file record are sent as opcom message traps, all messages that don’t match a filter file record are discarded.

Note that before the filtering process is applied to any opcom message NM∗ Opcom strips off the opcom header, if it is present. The opcom header is determined to be present if the first line of the message begins with:

%%%%%%%%%%% OPCOM

and ends with:

%%%%%%%%%%%\x0d\x0a

The filter file permits the use of the ∗ wildcard. This wildcard character is used to match one or more characters in the message. The wildcard character must be used carefully to ensure proper filtering. Placing wildcards at the beginning and end of a filter string requires that the string be embedded within the opcom message, i.e., not at the beginning and not at the end. The following is an example of a filter file:

∗ USERNAME1∗ ∗ TEST MESSAGE Operator * has been *abled, username *

The first entry would cause any opcom message containing the word “username1” to match the filter record except where “username1” appears at the beginning or end of the opcom message. The second entry would cause any message ending with the words “test message” to match the filter record. The third entry illustrates the use of multiple wildcards within the same message. This entry would cause both messages “Operator _SYS1$FTA1: has been enabled, username JONES” and “Operator _NODE1$FTA2: has been disabled, username SMITH” to match the filter record. Remember that the FILTER configuration file



parameter controls if messages that match filter records are dropped or sent. Note that entries in the filter file are case insensitive and that each entry must be left justified. A maximum number of 50 filter file entries are permitted and each entry may contain up to 5 substrings delimited by wildcards.

NM∗∗∗∗ Opcom MIB Objects The NMSERVERVMS.MIB file includes MIB object definitions that are supported by the NM∗ Opcom subagent.

Opcom Message Group Opcom Message Part One Opcom Message Part Two Opcom Message Part Three Opcom Message Part Four Opcom Message Part Five Opcom Message Part Six Opcom Message Part Seven

Opcom Configuration Group Filter Drop/Keep Flag Cards Flag Central Flag Cluster Flag Devices Flag Disks Flag License Flag Network Flag Oper1 Flag Oper2 Flag Oper3 Flag Oper4 Flag Oper5 Flag Oper6 Flag Oper7 Flag Oper8 Flag Oper9 Flag Oper10 Flag Oper11 Flag Oper12 Flag Printer Flag Security Flag Tapes Flag



Subagent Configuration Group Subagent OID Next Trap Sequence Number Trap Time Resend Trap Sequence Number Last Trap Sequence Number Sent Lost Trap Count Software Error Status Code Software Error File Name Software Error Line Number Software Error Last Time Software Error Message Configuration File Name Log File Name Reinitialization Flag Traps Enabled Flag Trap Table Size Time-out Process Termination Control Flag Terminate Process NM∗ Opcom Subagent Version Subagent Up Time Maximum Traps per Second

NM∗∗∗∗ Opcom Traps The following information provides an overview of the traps that may be generated by the NM∗ Opcom subagent. Refer to NMSERVERVMS.MIB for a complete description of each trap, the variables that accompany it, and the circumstances under which it may be generated. See Chapter 9 of this manual for more information about NMServer traps.

Enterprise Specific Traps Trap Description oColdStart(0) NM∗ Opcom has completed a cold start. oSwErr(1) A software error was encountered by NM∗ Opcom. oTermProc(2) NM∗ Opcom subagent process termination. oWarmStart(3) NM∗ Opcom has completed a reinitialization. oOpcomTrp(4) Opcom message.



8 NM∗∗∗∗ VmsMon Subagent

The NM∗ VmsMon subagent provides SNMP access to data that is available through the OpenVMS MONITOR Utility. The OpenVMS MONITOR Utility is a system management tool that is used to obtain information on performance of the OpenVMS operating system. NM∗ VmsMon gathers data about operating system performance at user-controlled intervals. The following classes of data are supported:

• Cluster – clusterwide CPU, memory, disk and locking activity

• DECnet – DECnet network activity

• Dlock – distributed lock management activity

• FCP – file control primitive statistics

• File_System_Cache – file system cache data

• IO – system I/O statistics

• Lock – lock management data

• Modes – statistics on each processor mode for each CPU

• MSCP_Server – mass storage control protocol server data

• Page – page management data

• States – number of processes in each of the scheduler states

• System – several of the important statistics from the other classes

Although NM∗ VmsMon reports the same data as the OpenVMS MONITOR Utility, this subagent does not interact with the MONITOR Utility to gather the data, therefore no additional overhead is incurred to run MONITOR.

NM∗∗∗∗ VmsMon Subagent Operation Privileges

Privilege Description NETMBX May create a network device



PRMMBX May create permanent mailboxes SYSNAM May insert in system logical name table

Required Logical Names The following logical names are required by NM∗ VmsMon.

• COMTEK$VMSMON_CODE - Identifies the location (device and directory) of the code for the NM∗ VmsMon subagent. This name must be in the system logical name table.

• COMTEK$VMSMON_CONFIG - Identifies the configuration file for the NM∗ VmsMon subagent. The actual file used may be changed while NM∗ VmsMon is running by setting the MIB variable vCfgFile.0 to the new file name and then setting the variable vCfgReinitSubagent.0 to 1 (TRUE). The MIB variable vCfgFile.0 contains the subagent's most recent translation of this logical name. This name must be in the system logical name table.


NM∗ VmsMon provides a MIB variable which allows the equivalence-name for COMTEK$VMSMON_CONFIG to be modified. To make changes to this logical name permanent across system reboots, the equivalence-name in the system startup procedures must also be changed.



defines the symbols that may be used to start the NMServer processes. To run the NM∗ VmsMon process, enter the following commands:

$ @comtek_root:[comtek$snmp.com]nmserver_symbols $ vmsmon

The command vmsmon starts the process NM∗ VmsMon as a detached process. If the NM∗ VmsMon process fails to start, examine the output file for the process to determine the cause of the problem. This file may be found in the COMTEK$VMSMON_CODE directory.

To stop the detached process, either use the MIB variable vCfgTermProc.0, as described in the MIB, or use the OpenVMS stop command:




The NM∗ VmsMon subagent may also be started attached to the user's terminal with debug information enabled. Enter the following command:

$ vmsmon -d <n>


Process Reinitialization Use the following reinitialization command procedure to cause the NM*VmsMon process to re-read data from its configuration files:

$ @comtek_root:[comtek$snmp.com]reinit_nmserver NM*VmsMon

NM∗∗∗∗ VmsMon Process Configuration Files COMTEK$VMSMON_CONFIG Configuration File This configuration file is read by NM∗ VmsMon when the process is started. This file is identified by the logical name:

COMTEK$VMSMON_CONFIG

If this logical name is not defined when the subagent is started, the process will terminate with an error. If a set-request is performed on the MIB variable vCfgFile.0, the specified file name must exist and be accessible to NM∗ VmsMon for the set-request to be successful. NM∗ VmsMon must be reinitialized by setting the variable vCfgReinitSubagent.0 to 1 (TRUE) for the new file to take effect.

The following is an example of a configuration file: ClusterInterval=1 Community=public ControlTermProc=disabled DECnetInterval=1 DlockInterval=1 FCPInterval=1 FileInterval=1 Host=sammy.comtek.com IOInterval=1 LockInterval=1



MaxTrapSec=0 ModeInterval=1 MSCPInterval=1 PageInterval=1 RlockInterval=1 StatesInterval=1 SystemInterval=1 Timeout=5 TimerInterval=1 Traps=enabled TrapTableSize=100

The format of the file is a left justified variable name followed by an '=' without intervening spaces or tabs. The variable names may be expressed in upper, lower or mixed case. If one of the optional variables is missing, misspelled, or has an invalid value, a warning message is written to the process' log file and a default value for the variable is used. Most of the configuration file variables have MIB equivalents. For any corresponding MIB variable that is read-write accessible, new values supplied via set-requests are saved to the current configuration disk file. See below for MIB equivalents, optional variables and default values. Comments may be inserted in the configuration file by placing a pound sign (#) as the first character in the line.

ClusterInterval=This variable sets the frequency at which MONITOR Cluster class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsClusterUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.

Community=This variable sets the community string to be used by NM∗ VmsMon when initiating communications with NM∗ Master. NOTE: This value must correspond to an entry in the NM∗ Master agent's community file, identified by the logical name COMTEK$MAS-TER_COMM for the subagent's IP Address. This variable is not used in the eSNMP environment.



Attributes Values MIB Variable Not applicable Required/Optional Optional Default Value public Set-requests Not permitted

ControlTermProc=This variable controls the use of the variable vCfgTermProc.0. If this variable is set to DISABLED, sets of the variable vCfgTermProc.0 are not allowed, thereby disabling the ability to terminate the NM∗ VmsMon process programmatically. If this variable is set to ENABLED, process termination may be initiated via the variable vCfgTermProc.0. This MIB item is read-only, meaning that this value may only be changed via the configuration file.

Attributes Values MonSub MIB Variable vCfgControlTermProc.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value DISABLED Set-requests Not permitted

DECnetInterval=This variable sets the frequency at which MONITOR DECnet class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsDECnetUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.

DLockInterval=This variable sets the frequency at which MONITOR DLock class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsDLockUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.

FCPInterval=This variable sets the frequency at which MONITOR FCP class variables are updated.



Attributes Values NMVmsMon MIB Variable vmsFCPUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.

FileInterval=This variable sets the frequency at which MONITOR File_System_Cache class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsFileUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.


Attributes Values MonSub MIB Variable vCfgHostName.0 Required/Optional Optional Default Value localhost Set-requests Not permitted

IOInterval=This variable sets the frequency at which MONITOR IO class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsIOUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.



LockInterval=This variable sets the frequency at which MONITOR Lock class variables are updated.



Attributes Values NMVmsMon MIB Variable vmsLockUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.

MaxTrapSec=This variable controls the maximum number of traps per second that may be transmitted by the NM∗ VmsMon subagent.

Variable Values MonSub MIB Variable vCfgMaxTrapSec.0 Required/Optional Optional Valid Values 0-100 Default Value 0 Set-requests Take effect immediately

ModeInterval=This variable sets the frequency at which MONITOR Mode class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsModeUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.

MSCPInterval=This variable sets the frequency at which MONITOR MSCP class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsMSCPUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.

PageInterval=This variable sets the frequency at which MONITOR Page class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsPageUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.



RlockInterval=This variable sets the frequency at which MONITOR Rlock class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsRlockUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.

StatesInterval=This variable sets the frequency at which MONITOR States class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsStatesUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.

SystemInterval=This variable sets the frequency at which MONITOR System class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsSystemUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.


Attributes Values MonSub MIB Variable vCfgTimeout.0 Required/Optional Optional Valid Values 0-3600 Default Value 0 Set-requests Take effect at process startup



TimerInterval=This variable sets the frequency at which MONITOR Timer (TQE) class variables are updated.

Attributes Values NMVmsMon MIB Variable vmsTimerUpdateInterval.0 Required/Optional Optional Default Value 1 Set-requests Take effect on next update.


Attributes Values MonSub MIB Variable vCfgTraps.0 Required/Optional Optional Valid Values ENABLED, DISABLED Default Value ENABLED Set-requests Take effect immediately

TrapTableSize=This variable sets the number of trap messages which are to be retained in the NM∗ VmsMon internal trap table. The trap table is a circular table containing a copy of traps sent by the NM∗ VmsMon. This value specifies the maximum number of messages in that table. Once the maximum number of messages in the table has been reached, the oldest messages are overwritten by new trap messages.

Attributes Values MonSub MIB Variable vCfgTrapTblSize.0 Required/Optional Optional Valid Values 10..5000 Default Value 100 Set-requests Take effect immediately

NM∗∗∗∗ VmsMon MIB Objects The NMSERVERVMS.MIB file includes object definitions that are supported by NM∗ VmsMon.

VMS Monitor Subagent Group Subagent OID Next Trap Sequence Number Trap Time-stamp



Resend Trap Sequence Number Last Trap Sequence Number Sent Lost Trap Count Software Error Status Software Error Filename Software Error Line Software Error Last Time Software Error Message Configuration File Name Log File Name Reinitialization Flag Traps Enabled Flag Trap Table Size Time-out Process Termination Control Flag Terminate Process NM∗ VmsMon Subagent Version Subagent Up Time Maximum Traps per Second

VMS Modes Group Update Time Update Interval CPU Count Mode by CPU Table

CPU ID Kernel Ticks Executive Ticks Supervisor Ticks User Ticks Interrupt Ticks Multi-processor CPU Synchronization Ticks Compatibility Ticks Idle Ticks

Total Mode Data for all CPUs Total Kernel Ticks Total Executive Ticks Total Supervisor Ticks Total User Ticks Total Interrupt Ticks Total Multi-processor CPU Synchronization Ticks Total Compatibility Ticks Total Idle Ticks



VMS File System Cache Group Update Time Update Interval Directory FCP Cache Hit Count Directory FCP Cache Attempt Count Directory Data Hit Count Directory Data Attempt Count File Header Hit Count File Header Attempt Count File ID Hit Count File ID Attempt Count Extent Hit Count Extent Attempt Count Quota Hit Count Quota Attempt Count Storage Bitmap Cache Hit Count Storage Bitmap Cache Attempt Count

VMS FCP Group Update Time Update Interval FCP Call Count Allocation Count File Create Count Disk Read Count Disk Write Count Volume Lock Wait State Count File System CPU Tick Count File System Page Fault Count File Name Lookup Count Files Opened Count Erase I/O Operation Count

VMS I/O Group Update Time Update Interval Direct I/O Count Buffered I/O Count Mailbox Write Count Split Transfer Count Logical Name Translation Count File Open Count Page Fault Count Page Fault Read Count



Page Fault Read I/O Count Page Fault Write Count Page Fault Write I/O Count Inswap Count Free Page List Count Modified Page List Count

Page Group Update Time Update Interval Page Fault Count Page Fault Read Count Page Fault Read I/O Count Page File Write Count Page File Write I/O Count Free List Fault Count Modified List Fault Count Demand Zero Fault Count Global Valid Fault Count Write In Progress Fault Count System Page Fault Count Free Page Count Modified Page Count DECnet Group Update Time Update Interval Arriving Local Packet Count Departing Local Packet Count Arriving Transit Packet Count Transit Congestion Loss Count Receiver Buffer Failure Count

States Group Update Time Update Interval Count of Processes in COLPG State Count of Processes in MWAIT State Count of Processes in CEF State Count of Processes in PFW State Count of Processes in LEF State Count of Processes in LEFO State Count of Processes in HIB State Count of Processes in HIBO State



Count of Processes in SUSP State Count of Processes in SUSPO State Count of Processes in FPG State Count of Processes in COM State Count of Processes in COMO State Count of Processes in CUR State

Cluster Group Update Time Update Interval CPU Busy Free List Size Total Locks New Enqueues - Local New Enqueues - Incoming New Enqueues - Outgoing Enqueue Conversions - Local Enqueue Conversions - Incoming Enqueue Conversions - Outgoing Dequeues - Local Dequeues - Incoming Dequeues - Outgoing

MSCP Group Update Time Update Interval I/O Transfer Request Count Read I/O Transfer Request Count Write I/O Transfer Request Count Extra Fragment Count Split Request Count MSCP Buffer Memory Wait Count 1 Block I/O Request Count 2-3 Block I/O Request Count 4-7 Block I/O Request Count 8-15 Block I/O Request Count 16-31 Block I/O Request Count 32-63 Block I/O Request Count 64 and Over Block I/O Request Count

Lock Group Update Time Update Interval New Enqueue Request Count



Converted Enqueue Request Count Dequeue Request Count Blocking AST Count Enqueue Wait Count Enqueue Not Queued Count Deadlock Search Count Deadlocks Found Number of Current Locks Number of Current Resources

Distributed Lock Group Update Time Update Interval New Locks - Local New Locks - Incoming New Locks - Outgoing Lock Conversions - Local Lock Conversions - Incoming Lock Conversions - Outgoing Unlocks - Local Unlocks - Incoming Unlocks - Outgoing Blocking ASTs - Local Blocking ASTs - Incoming Blocking ASTs - Outgoing Directory Functions - Incoming Directory Functions - Outgoing Deadlock Message Count

System Group Update Time Update Interval CPU Busy Count of Processes in Other States Process Count Page Fault Count Read I/O Count from Page Faults Free Page List Count Modified Page List Count Direct I/O Count Buffered I/O Count

Rlock Group Update Time



Update Interval Lock Trees Acquired Lock Trees Moved for Better LOCKDIRWT Lock trees moved from this node due to higher locking activity Remaster messages received Rmaster messages sent Remaster operations that failed due to a lack of quota Remaster operations that were proposed and declined Remaster operations that have been completed Remaster rebuild messages received Remaster rebuild messages sent Trees moved because other node only one with locks remaining Count of lock trees moved from this node Timer Group Update Time Update Interval Timer requests made by the OpenVMS Count of timer requests Timer requests made by SYS$SETIMR Timer requests made by SYS$SCHDWK

NM∗∗∗∗ VmsMon Traps The following information provides an overview of the traps that may be generated by the NM∗ VmsMon subagent. Refer to NMSERVERVMS.MIB for a complete description of each trap, the variables that accompany it, and the circumstances under which it may be generated. See Chapter 9 of this manual for more information about NMServer traps.

Enterprise Specific Traps Trap Description vColdStart(0) NM∗ VmsMon has completed a cold start. vSwErr(1) A software error was encountered by NM∗ VmsMon.vTermProc(2) NM∗ VmsMon subagent process termination. vWarmStart(3) NM∗ VmsMon has completed a reinitialization.



9 NMServer Traps

NMServer for OpenVMS provides functionality that enables traps to be reliably received by the SNMP manager. Through the use of trap sequence numbering, the ability to resend traps, and a throttle for trap transmission, the SNMP manager can detect traps that are not received, resend recent traps, and limit the amount of traps that may be generated by a subagent each second to prevent network overload.

For details on trap handling, see the MIB and trap MIB files for the NM∗ Master agent (DPI only), NM∗ SysMgr subagent, NM∗ TrpMgr subagent and NM∗ Console subagent.

Resending Traps The NMServer products provide a facility for confirmed trap reception. Each NMServer process, that is, the master agent (DPI only) and each subagent, maintains its own an internal trap table in which it records the last <n> traps that the process has generated (where <n> is controlled by the configuration file parameter TrapTableSize for each process). When a trap is generated, the NMServer process assigns a sequence number to the trap and that sequence number, along with the agent or subagent up-time indicating when the trap was generated, is sent as a variable with the trap.

To prevent traps from being lost, the SNMP manager may poll the master agent (DPI only) for the next sequence number and poll each subagent for the last sequence number sent and monitor the sequence number of traps that are received. If the SNMP manager detects a gap in the sequence number indicating that a trap has been lost on the network, it may perform an SNMP set-request of the resend sequence number MIB object for the corresponding process. Setting this MIB object to the sequence number of a trap in the internal trap table causes the trap with that sequence number to be resent. The up-time variable that accompanies the trap indicates the process up time when the trap was originally generated. If the internal trap table is not sufficiently large and traps are being generated rapidly, the missing trap may not be available



in the internal trap table. In this case, increase the size of the variable TrapTableSize.

Trap Throttling Each of the NMServer subagents provides the capability to throttle traps to prevent them from flooding the network. This throttle takes the form of the configuration file variable MaxTrapSec that specifies the maximum number of traps per second that the subagent may transmit. Traps that are not immediately transmitted are retained in the subagent’s internal trap table. The value of MaxTrapSec must therefore be tuned with the variable TrapTableSize to ensure that traps that are delayed by throttling are not overwritten before they may be sent. By default, trap throttling is disabled. Trap throttling may also be disabled explicitly by setting the value of MaxTrapSec to zero.

To assist in detecting traps that are lost due to insufficient size of the internal trap table, the MIB object TrapLostCount is available in each subagent MIB. This item keeps track of the number of traps that have been lost due to throttling since the subagent process was started.

Additionally, the MIB object TrapLastSeqNumSent is available in each subagent MIB. This value may be compared to TrapNextSeqNum to determine the size of any backlog of traps due to throttling. Since the variable TrapNextSeqNum always identifies the sequence number of the next trap that will be sent and the variable TrapLastSeqNumSent identifies the sequence number of the last trap that was sent, TrapNextSeqNum will always be at least one greater than TrapLastSeqNumSent.

To ensure that sufficient space is available in the internal trap table to hold traps that are backlogged due to throttling, the difference between TrapNextSeqNum and TrapLastSeqNumSent should never be greater than TrapTableSize.

The MIB objects TrapLostCount, TrapNextSeqNum, and TrapLastSeq-NumSent all appear in each subagent’s MIB. They are prefixed by a single subagent specific character to aid in discerning the subagent to which they apply. In the NM∗ SysMgr MIB, these variables are named: sTrapLostCount, sTrapNextSeqNum, and sTrapLastSeqNumSent. In the NM∗ TrpMgr MIB, they are named: tTrapLostCount, tTrapNextSeqNum, and tTrapLastSeqNumSent. These MIB objects are called cTrapLostCount, cTrapNextSeqNum and cTrapLastSeqNumSent in the NM∗ Con-sole MIB.



10 Web Interface for NMServer for OpenVMS

The NMServer web interface provides easy access to NMServer’s proactive system management data via a web browser. NMServer’s web interface is integrated with HP’s Management Agents. For more information about web-based enterprise management (WBEM) and HP’s freely available Management Agents visit:

http://www.openvms.digital.com/openvms/products/mgmt_agents/intro.html

Description NMServer’s web interface builds on the HP OpenVMS Management Agent web interface by adding two groups of management elements to HP’s device Summary page and navigation bar. These two new groups of management elements are: NMServer and NMServer Monitor.

NMServer Group The NMServer group provides access to system performance and utilization information, including status indicators that alert the user when the node has exceeded the user-defined thresholds for an element or when a potential problem has been detected. Elements in this group include:

CPU Provides CPU utilization by mode over the following intervals: 1 minute, 5 minutes, 15 minutes, and since bootstrap

Critical Jobs Table of jobs that the user specified as mission critical in the COMTEK$SYSMGR_CRITQUEUE file

Critical Processes

Table of processes that the user specified as mission critical in the COMTEK$SYSMGR_CRIT file

Disks Table of disk information Processes Table of processes Queues Table of queues that the user specified as mission

http://www.openvms.digital.com/openvms/products/mgmt_agents/intro.html



critical in the COMTEK$SYSMGR_CRITQUEUE file

System Information

Memory, page, swap file utilization and general system information

Device Errors Table of devices that have reported errors along with error count and time of last error

Traps The most recent 100 traps that have been generated by the NM*SysMgr subagent

Data for each of these elements is provided by the NMServer NM*SysMgr subagent and corresponds to a group of MIB variables in the NMSERVERVMS.MIB.

A link to a Threshold page appears at the bottom of each page in the NMServer group. Threshold pages provide information on the current settings of limits, update intervals, etc. that control how often data for the element is gathered or when traps are generated. Values on the Threshold pages may not be altered via the Web interface. Changes to these values may be made either by editing the COMTEK$SYSMGR_CONFIG configuration file on the managed node or via a Set command issued from an authorized SNMP manager.

NMServer Monitor Group The NMServer Monitor group contains elements that correspond to the VMS MONITOR Utility program. The data in this group is provided via the NMServer NM*VmsMon subagent and is described in the NMSERVERVMS.MIB file. The following elements are available under the NMServer Monitor group:

DECnet DECnet statistics, similar to $ MONITOR DECNET

Distributed Lock

Distributed lock manager statistics, similar to $ MONITOR DLOCK

FCP File primitive statistics, similar to $ MONITOR FCP File System

Cache File system cache statistics, similar to $ MONITOR FILE_SYSTEM

IO I/O system statistics, similar to $ MONITOR IO

Lock Lock management statistics, similar to $ MONITOR LOCK

Modes CPU mode statistics, similar to $ MONITOR MODES



MSCP Server MSCP server statistics, similar to $ Monitor MSCP_SERVER

Page Page management statistics, similar to $ MONITOR PAGE

System Requirements NMServer web interface is reliant on the HP Management Agents and therefore has the same system requirements as the HP Management Agents. Consult:

http://www.openvms.digital.com/openvms/products/mgmt_agents/require.html

for specific requirements.

Installation Instructions Installation instructions for the NMServer web interface are contained in the NMServer for OpenVMS product README.htm file.

Configuration Options When using the web interface, configuration options are available that effect the way in which the data is reported. These configuration options may be set by clicking on the Options link in the top left corner of the Summary page.





A NMServer MIB -- -- file: nmservervms.mib -- -- COMTEK Services, Inc. -- Date February 2006 -- Release 4.0 -- Author NKF -- -- Copyright 1994-2006 COMTEK Services, Inc. All Rights Reserved. -- -- This COMTEK Services SNMP Management Information Base Specification -- (Specification) embodies COMTEK Services' confidential and -- proprietary intellectual property. COMTEK Services retains all -- title and ownership in the Specification, including any -- revisions. -- -- This Specification is supplied "AS IS," and COMTEK Services makes -- no warranty, either express or implied, as to the use, -- operation, condition, or performance of the Specification. -- -- PURPOSE: This MIB file identifies the objects supported by the -- COMTEK NMServer for OpenVMS SNMP agent. As of v3.6 of NMServer -- for OpenVMS, all MIB files have been combined into a single MIB -- to simplify loading of MIBs and Traps into SNMP network managers. -- As a composite of more than a dozen MIBs, this MIB is quite long. -- This MIB is organized as follows: -- comtek.mib - defines the comtek enterprise -- samib.mib - defines variables used -- nmmaster.mib -- nmmaster.trp -- nmsysmgr.mib -- nmsysmgr.trp -- nmtrpmgr.mib -- nmtrpmgr.trp -- nmconsole.mib -- nmconsole.trp -- nmvmsmon.mib -- monsub.mib -- nmopcom.mib -- Sections of the MIB are divided by a line of slashes; to jump -- from one section of the MIB to another, search for repeating -- slashes ("////"). COMTEK-VMS-MIB DEFINITIONS ::= BEGIN IMPORTS DisplayString, snmp FROM RFC1213-MIB OBJECT-TYPE FROM RFC-1212 IpAddress, TimeTicks, Counter, enterprises FROM RFC1155-SMI TRAP-TYPE FROM RFC-1215; comtek OBJECT IDENTIFIER ::= { enterprises 597 }



comtekvosMib OBJECT IDENTIFIER ::= { comtek 1 } comtekvosAgent OBJECT IDENTIFIER ::= { comtek 2 } comtekos400Mib OBJECT IDENTIFIER ::= { comtek 3 } comtekVms OBJECT IDENTIFIER ::= { comtek 4 } comtekos400 OBJECT IDENTIFIER ::= { comtek 5 } -- SUBAGENT DEFINITIONS comtekSubagent OBJECT IDENTIFIER ::= { comtek 100 } sampleMib OBJECT IDENTIFIER ::= { comtek 101 } sampleSubagent OBJECT IDENTIFIER ::= { comtek 102 } -- VOS Subagents: -- OS/400 Subagents: os400cmn OBJECT IDENTIFIER ::= { comtekos400 1 } os400genericQmonitor OBJECT IDENTIFIER ::= { comtekos400 2 } -- OpenVMS Subagents: -- Note: The following pairs of object identifiers must match the values -- in by the subagent code. These numbers uniquely identify the MIB and -- subagent. Object identifiers for new subagents and their corresponding -- MIBs should be added to the end of this list. comtekVmsNMMasterMib OBJECT IDENTIFIER ::= { comtekVms 1 } comtekVmsNMMasterAgent OBJECT IDENTIFIER ::= { comtekVms 2 } comtekVmsNMSysMgrMib OBJECT IDENTIFIER ::= { comtekVms 3 } comtekVmsNMSysMgrSubagent OBJECT IDENTIFIER ::= { comtekVms 4 } comtekVmsNMTrpMgrMib OBJECT IDENTIFIER ::= { comtekVms 5 } comtekVmsNMTrpMgrSubagent OBJECT IDENTIFIER ::= { comtekVms 6 } comtekVmsNMConsoleMib OBJECT IDENTIFIER ::= { comtekVms 7 } comtekVmsNMConsoleSubagent OBJECT IDENTIFIER ::= { comtekVms 8 } comtekVmsNMOpcomMib OBJECT IDENTIFIER ::= { comtekVms 13 } comtekVmsNMOpcomSubagent OBJECT IDENTIFIER ::= { comtekVms 14 } comtekVmsNMVmsMonMib OBJECT IDENTIFIER ::= { comtekVms 15 } comtekVmsNMVmsMonSubagent OBJECT IDENTIFIER ::= { comtekVms 16 } --////////////////////////////////////////////////////////////////////// -- created from saMIB (9505260000Z) --////////////////////////////////////////////////////////////////////// ibm OBJECT IDENTIFIER ::= { enterprises 2 } ibmResearch OBJECT IDENTIFIER ::= { ibm 4 } saMIB OBJECT IDENTIFIER ::= { ibmResearch 12 } saDefaultTimeout OBJECT-TYPE SYNTAX INTEGER -- UNITS seconds ACCESS read-write STATUS mandatory DESCRIPTION "The default timeout (in seconds) that this agent waits for a response from a SubAgent. This value is used if a timeout value is not specified for the subtree nor for the subagent that exports the subtree." DEFVAL { 5 } ::= { saMIB 1 } saMaxTimeout OBJECT-TYPE SYNTAX INTEGER -- UNITS seconds ACCESS read-write STATUS mandatory DESCRIPTION "The maximum timeout (in seconds) that this agent allows for timeout values for SubAgents. When you try to set any other timeout value it must be between 1 and this maximum value." DEFVAL { 60 }



::= { saMIB 2 } saAllowDuplicateIDs OBJECT-TYPE SYNTAX INTEGER { yes(1), no(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Controls if multiple instances of a sub-agent (as identified by the sub-agent Identifier) are allowed. Setting this object to the value no(2) will prevent (new) duplicate sub-agentIDs. However, if any duplicates exist at that point in time, the agent will not remove them. That is considered a manager responsibility." ::= { saMIB 3 } saNumber OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of entries in the saTable" ::= { saMIB 4 } saAllPacketsIn OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "A count of packets received from all subagents." ::= { saMIB 5 } saAllPacketsOut OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "A count of packets send to all subagents." ::= { saMIB 6 } saTable OBJECT-TYPE SYNTAX SEQUENCE OF SaEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The SubAgent table, listing all subagents." ::= { saMIB 7 } saEntry OBJECT-TYPE SYNTAX SaEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An entry in the SubAgnet table." INDEX { saIndex } ::= { saTable 1 } SaEntry ::= SEQUENCE { saIndex INTEGER, saIdentifier OBJECT IDENTIFIER, saDescription



DisplayString, saStatus INTEGER, saStatusChangeTime TimeTicks, saProtocol INTEGER, saProtocolVersion INTEGER, saProtocolRelease INTEGER, saTransport INTEGER, saTransportAddress OCTET STRING, saTimeout INTEGER, saMaxVarBinds INTEGER, saPacketsIn Counter, saPacketsOut Counter } saIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "An index which uniquely identifies a SubAgent. The value must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization." ::= { saEntry 1 } saIdentifier OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only STATUS mandatory DESCRIPTION "The authoritative identification for a SubAgent." ::= { saEntry 2 } saDescription OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "A descriptive name for a SubAgent." ::= { saEntry 3 } saStatus OBJECT-TYPE SYNTAX INTEGER { valid(1), invalid(2), connecting(3), disconnecting(4), closedByManager(5), closedByAgent(6),



closedBySubAgent(7), closedBySubAgentTimeout(8), closedBySubAgentError(9) } ACCESS read-write STATUS mandatory DESCRIPTION "The status of the SubAgent. The only value that can be set is invalid(2). This can only be done if the status is not already in a ClosedSomething status. Setting this object to the value invalid(2) has the effect of invalidating the entry upon which the agent will close the connection and turn it to status closedByManager(7). It is an implementation specific matter if an entry that is not valid(1) is removed from the table. However, if such an entry is kept and the subagent re-connects, then the same entry must be re-used." ::= { saEntry 4 } saStatusChangeTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The timestamp of the last status change of the SubAgent." ::= { saEntry 5 } saProtocol OBJECT-TYPE SYNTAX INTEGER { dpi(1), moh(2), smux(3) } ACCESS read-only STATUS mandatory DESCRIPTION "The SubAgent protocol being used." ::= { saEntry 6 } saProtocolVersion OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The version of the SubAgent Protocol used." ::= { saEntry 7 } saProtocolRelease OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The release of the SubAgent Protocol used." ::= { saEntry 8 } saTransport OBJECT-TYPE SYNTAX INTEGER { udp(1), tcp(2), nmq(3), sna(4)



} ACCESS read-only STATUS mandatory DESCRIPTION "The transport protocol used by the SubAgent." ::= { saEntry 9 } saTransportAddress OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS mandatory DESCRIPTION "The address of the subagent (transport specific address information)." ::= { saEntry 10 } saTimeout OBJECT-TYPE SYNTAX INTEGER -- UNITS seconds ACCESS read-write STATUS mandatory DESCRIPTION "The default timeout (seconds) for a SubAgent response. This value will be used if there is no timeout value specified for a particular subtree." DEFVAL { 0 } ::= { saEntry 11 } saMaxVarBinds OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Max varBinds this subagent accepts per request." ::= { saEntry 12 } saPacketsIn OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "A count of packets send to this subagent." ::= { saEntry 13 } saPacketsOut OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "A count of packets send to this subagent." ::= { saEntry 14 } saTreeTable OBJECT-TYPE SYNTAX SEQUENCE OF SaTreeEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The SubAgent tree table." ::= { saMIB 8 } saTreeEntry OBJECT-TYPE SYNTAX SaTreeEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An entry in the SubAgent tree table." INDEX { saTsubtree, saTpriority } ::= { saTreeTable 1 } SaTreeEntry ::= SEQUENCE {



saTsubtree OBJECT IDENTIFIER, saTpriority INTEGER, saTindex INTEGER, saTstatus INTEGER, saTtimeout INTEGER } saTsubtree OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only STATUS mandatory DESCRIPTION "The MIB subtree being exported by the SubAgent." ::= { saTreeEntry 1 } saTpriority OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The SubAgents Priority when exporting the MIB subtree. The lower the value the better the priority." ::= { saTreeEntry 2 } saTindex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The SubAgent's identity (index into the saTable)." ::= { saTreeEntry 3 } saTstatus OBJECT-TYPE SYNTAX INTEGER { valid(1), invalid(2) } ACCESS read-write STATUS mandatory DESCRIPTION "The status of subtree exported by the SubAgent. Setting this object to the value invalid(2) has the effect of invalidating the entry. It is an implementation specific matter if an entry that is not valid(1) is removed from the table." ::= { saTreeEntry 4 } saTtimeout OBJECT-TYPE SYNTAX INTEGER -- UNITS seconds ACCESS read-write STATUS mandatory DESCRIPTION "The timeout (in seconds) for objects in this subtree. A value of zero (0) means that the overall timeout value (as specified in the saTableEntry for the SubAgent) will be used." DEFVAL { 0 }



::= { saTreeEntry 5 } saMIBConformance OBJECT IDENTIFIER ::= { saMIB 9 } saMIBCompliances OBJECT IDENTIFIER ::= { saMIBConformance 1 } saMIBGroups OBJECT IDENTIFIER ::= { saMIBConformance 2 } saMIBCompliance OBJECT IDENTIFIER ::= { saMIBCompliances 1 } saTableGroup OBJECT IDENTIFIER ::= { saMIBGroups 1 } saTreeGroup OBJECT IDENTIFIER ::= { saMIBGroups 2 } --////////////////////////////////////////////////////////////////////// -- created from nmmaster.mib --////////////////////////////////////////////////////////////////////// -- When a software error is encountered, a mSwErr trap is generated containing -- the following software error description items. Invalid sets of the -- mCfgFile, mCfgTrapFile or mCfgCommFile variable will cause a mSwErr trap to -- be generated to explain the error. mSwErrStatus OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The latest software status code." ::= { comtekVmsNMMasterMib 1 } mSwErrFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The file name of the software element which generated the latest software status code." ::= { comtekVmsNMMasterMib 2 } mSwErrLineNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The line number in the file which generated the latest software status code." ::= { comtekVmsNMMasterMib 3 } mSwErrLastTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The time at which the most recent software status code was generated." ::= { comtekVmsNMMasterMib 4 } mSwErrMessage OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Description of the latest software error." ::= { comtekVmsNMMasterMib 5 } -- The NM*Master Agent process maintains an internal trap table -- containing the latest traps that have been sent. The number -- of traps that are retained is controlled by the mCfgTrapTblSize -- variable. Each trap that is sent by the NM*Master includes -- a trap sequence number and a timestamp as well as any trap



-- specific data. The trap sequence number may be used to request -- that a trap be resent to the manager. mTrapNextSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The next sequence number in trap table. When this variable is sent as part of a trap, it identifies the sequence number assigned to that trap. This is a 32-bit value and will wrap after 4294967295." ::= { comtekVmsNMMasterMib 6 } mTrapTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "sysUpTime when the latest trap was created." ::= { comtekVmsNMMasterMib 7 } mTrapResendSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "Sequence number of a trap message to be resent to the manager. Setting this variable to a trap sequence number causes the specified trap message to be resent. If the set-request contains a sequence number that is not available because more than mCfgTrapTblSize traps have been sent since the requested trap was generated, (the number of items retained is dependent on the value of mCfgTrapTblSize), an error indicator will be returned." ::= { comtekVmsNMMasterMib 8 } -- Configuration parameters which are read from disk and may be -- viewed/changed by the network manager. All changes to these -- parameters are written to the disk file. mCfgFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file currently being used for the NM*Master Agent initialization parameters. This file is identified by the logical name COMTEK$MASTER_CONFIG. Changing this variable redefines the COMTEK$MASTER_CONFIG logical name. NM*Master must be reinitialized (by setting the variable mCfgReinitMaster to true) before the new configuration file is used. If a set- request is performed on this variable and the specified file does not exist, is not accessible, or contains invalid data, the file name is not changed, an error is returned and a mSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (mCfgReinitSubagent) NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures." ::= { comtekVmsNMMasterMib 9 } mCfgLogFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Name of the log file currently being used by NM*Master.



If this process is run interactively, this variable will have the value SYS$OUTPUT: (standard output)." ::= { comtekVmsNMMasterMib 10 } mCfgCommFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file which is currently being used to provide community data. This file is accessed via the logical name COMTEK$MASTER_COMM. Changing this variable redefines the COMTEK$MASTER_COMM logical name. NM*Master must be reinitialized (by setting the variable mCfgReinitMaster to true) before the new community file is used. If a set-request is performed on this variable and the specified file does not exist, is not accessible, or contains invalid data, this variable is not changed, an error is returned and a mSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (mCfgReinitSubagent) NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures." ::= { comtekVmsNMMasterMib 11 } mCfgTrapFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file which is currently being used to provide trap destinations. This file is accessed via the logical name COMTEK$MASTER_TRAP. Changing this variable redefines the COMTEK$MASTER_TRAP logical name. NM*Master must be reinitialized (by setting the variable mCfgReinitMaster to true) before the new trap file is used. If a set-request is performed on this variable and the specified file does not exist, is not accessible, or contains invalid data, this variable is not changed, an error is returned and a mSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (mCfgReinitSubagent) NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures." ::= { comtekVmsNMMasterMib 12 } mCfgReinitMaster OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be set to force the NM*Master Agent to reinitialize. Reinitialization involves resetting the process configuration as specified in the mCfgFile, resetting community data using the mCfgCommFile, resetting the trap destinations using the mCfgTrapFile, and sending a warmStart trap." DEFVAL { false } ::= { comtekVmsNMMasterMib 13 } mCfgLogging OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION



"Flag which determines if logging is to be performed. If logging is enabled(1), all SNMP request, responses, and traps are written to the log file. Configuration Variable: Logging Set-Requests: Take effect immediately Changes to this value are written to the mCfgFile. NOTE: Enabling logging may impact performance of the NM*Master Agent. It may be necessary to raise time-out values when logging is enabled." DEFVAL { disabled } ::= { comtekVmsNMMasterMib 14 } mCfgTrapTblSize OBJECT-TYPE SYNTAX INTEGER (10..5000) ACCESS read-write STATUS mandatory DESCRIPTION "The maximum number of traps to be retained. Traps that are retained may be resent (see mTrapResendSeqNum) unless too many subsequent traps have been generated. This variable controls how many traps are retained in NM*Master's internal trap table. Configuration Variable: TrapTableSize Set-Requests: Take effect immediately Changes to this value are written to the mCfgFile." DEFVAL { 100 } ::= { comtekVmsNMMasterMib 15 } mCfgControlTermProc OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Flag which may be used to disable process termination by the mCfgTermProc variable. Setting this variable to enabled(1) allows the mCfgTermProc variable to be set to true(1) to terminate the NM*Master process. Setting this variable to disabled(2) prevents the mCfgTermProc variable from being set. Configuration Variable: ControlTermProc" DEFVAL { disabled } ::= { comtekVmsNMMasterMib 16 } mCfgTermProc OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be used to shutdown the NM*Master process. Setting this flag to true(1) causes the NM*Master process to respond to the set-request, send the mTermProc trap, close the connection to the manager, and shutdown. Set-requests: Take effect immediately if mCfgControlTermProc is enabled(2)" DEFVAL { false } ::= { comtekVmsNMMasterMib 17 } mCfgVersion OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Current version of the NM*Master Agent software." ::= { comtekVmsNMMasterMib 18 }



mAuthFailIPAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory DESCRIPTION "The IP address originating the most recent SNMP message which failed authentication." ::= { comtekVmsNMMasterMib 19 } mAuthFailCommunity OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The community string contained in the most recent SNMP message which failed authentication." ::= { comtekVmsNMMasterMib 20 } --////////////////////////////////////////////////////////////////////// -- created from nmmaster.trp --////////////////////////////////////////////////////////////////////// coldStart TRAP-TYPE ENTERPRISE snmp VARIABLES { mCfgVersion, mTrapNextSeqNum, mTrapTime } DESCRIPTION "A coldStart trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered." ::= 0 warmStart TRAP-TYPE ENTERPRISE snmp VARIABLES { mTrapNextSeqNum, mTrapTime } DESCRIPTION "A warmStart trap signifies that the sending protocol entity is reinitializing itself such that neither the agent configuration nor the protocol entity implementation is altered." ::= 1 authenticationFailure TRAP-TYPE ENTERPRISE snmp VARIABLES { mAuthFailIPAddress, mAuthFailCommunity, mTrapNextSeqNum, mTrapTime } DESCRIPTION "An authenticationFailure trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated. While implementations of the SNMP must be capable of generating this trap, they must also be capable of suppressing the emission of such traps via an implementation-specific mechanism." ::= 4 mSwErr TRAP-TYPE ENTERPRISE comtekVmsNMMasterAgent VARIABLES { mSwErrStatus, mSwErrFile, mSwErrLineNum, mSwErrMessage, mTrapNextSeqNum, mTrapTime } DESCRIPTION "Software error encountered. This trap indicates that NM*Master was unable to perform some action and explains the error. This trap is typically encountered if mCfgFile, mCfgCommFile, or mCfgTrapFile is set to a new file name which is erroneous or contains invalid data." ::= 0 mTermProc TRAP-TYPE ENTERPRISE comtekVmsNMMasterAgent VARIABLES { mTrapNextSeqNum, mTrapTime } DESCRIPTION



"NM*Master Agent process termination. This trap indicates that the NM*Master Agent is terminating." ::= 1 mSubagentStatusChange TRAP-TYPE ENTERPRISE comtekVmsNMMasterAgent VARIABLES { saIdentifier, saStatus, saStatusChangeTime, mTrapNextSeqNum, mTrapTime } DESCRIPTION "Subagent status change. The status of one of the subagents has changed. This trap is generated when a subagent connects to or disconnects from the NM*Master Agent." ::= 2 --////////////////////////////////////////////////////////////////////// -- created from nmsysmgr.mib --////////////////////////////////////////////////////////////////////// -- This lists system resources available (system, CPU, disk, queue) sResources OBJECT IDENTIFIER ::= { comtekVmsNMSysMgrMib 1 } -- This is a table of VMS process statistics sProcesses OBJECT IDENTIFIER ::= { comtekVmsNMSysMgrMib 2 } -- This is trap data sTrapInfo OBJECT IDENTIFIER ::= { comtekVmsNMSysMgrMib 3 } -- This lists error information (hardware, software, operator log) sErrInfo OBJECT IDENTIFIER ::= { comtekVmsNMSysMgrMib 4 } -- This lists NM*SysMgr Subagent configuration parameters sCfg OBJECT IDENTIFIER ::= { comtekVmsNMSysMgrMib 5 } sSyi OBJECT IDENTIFIER ::= { sResources 1 } sCpu OBJECT IDENTIFIER ::= { sResources 2 } sDsk OBJECT IDENTIFIER ::= { sResources 3 } sShd OBJECT IDENTIFIER ::= { sResources 4 } sQue OBJECT IDENTIFIER ::= { sResources 5 } sProcInfo OBJECT IDENTIFIER ::= { sProcesses 1 } sCritInfo OBJECT IDENTIFIER ::= { sProcesses 2 } sHwErrInfo OBJECT IDENTIFIER ::= { sErrInfo 1 } sSwErrInfo OBJECT IDENTIFIER ::= { sErrInfo 2 } -- System Information sSyiNodeName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..15)) ACCESS read-only STATUS mandatory DESCRIPTION "The name of the node." ::= { sSyi 1 } sSyiHwName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..31)) ACCESS read-only STATUS mandatory DESCRIPTION "The hardware model name." ::= { sSyi 2 } sSyiBootTime OBJECT-TYPE SYNTAX DisplayString (SIZE (23)) ACCESS read-only STATUS mandatory DESCRIPTION "The date and time when the system was booted. This value is in the form dd-mmm-yyyy hh:mm:ss.cc." ::= { sSyi 3 }



sSyiVersion OBJECT-TYPE SYNTAX DisplayString (SIZE (0..8)) ACCESS read-only STATUS mandatory DESCRIPTION "The software version number of the OpenVMS operating system running on the node." ::= { sSyi 4 } sSyiMemSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The total number of pages of physical memory in the system configuration. This value is static." ::= { sSyi 5 } sSyiAvailCpuCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of CPUs which were available at system bootstrap. This value is static." ::= { sSyi 6 } sSyiActiveCpuCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of active CPUs." ::= { sSyi 7 } sSyiPgSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of pages in the currently installed page files." ::= { sSyi 8 } sSyiPgFree OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of free pages in the currently installed page files." ::= { sSyi 9 } sSyiPgUsedPercent OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-only STATUS mandatory DESCRIPTION "The percent full of the currently installed page files." ::= { sSyi 10 } sSyiSwpSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of pages in the currently installed swapping files." ::= { sSyi 11 } sSyiSwpFree OBJECT-TYPE SYNTAX INTEGER



ACCESS read-only STATUS mandatory DESCRIPTION "The number of free pages in the currently installed swapping files." ::= { sSyi 12 } sSyiSwpUsedPercent OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-only STATUS mandatory DESCRIPTION "The percent full of the currently installed swapping files." ::= { sSyi 13 } sSyiCpuPgSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of CPU-specific bytes per page in the system. On VAX systems, this value is always 512. On Alpha systems, CPU page size varies from system to system." ::= { sSyi 14 } sSyiTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time (sCfgUpTime) when system information (sSyi) was last gathered. sCfgSysInfoTimer controls how often system statistics are gathered." ::= { sSyi 15 } sSyiMemFreePg OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of free pages of physical memory on the system." ::= { sSyi 16 } sSyiMemUsed OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Physical memory percentage used." ::= { sSyi 17 } sSyiCondition OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), degraded(3), failed(4) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicates current condition of System-related statistics. DEGRADED indicates that one or more of the following has exceeded the defined limit: page file usage, swap file usage, memory usage." ::= { sSyi 18 } -- CPU Statistics sCpuPercentUsed OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-only STATUS mandatory DESCRIPTION "The percent utilization of all CPUs, i.e., the percent of time the combined CPUs were not idle during the last one minute interval."



::= { sCpu 1 } sIntPercentUsed OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-only STATUS mandatory DESCRIPTION "The percent of time the combined CPUs spent in interrupt mode during the last one minute interval." ::= { sCpu 2 } sCpuTicks OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of interval timer ticks that have occurred since the last time CPU statistics were gathered (approximately one minute). This value is the sum of the one minute mode tick counters. This number has been normalized to account for all active CPUs on the system. This value may be used with the one minute CPU mode times to determine the percent of time spent in each CPU mode." ::= { sCpu 3 } -- CPU Statistics for the past one minute interval sCpuLoadOneMinute OBJECT IDENTIFIER ::= { sCpu 4 } sKernelOne OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Time in Kernel mode for all CPUs during the last one minute interval. This value indicates the number of ticks in kernel mode on the kernel stack, when no spinlock busy wait is active." ::= { sCpuLoadOneMinute 1 } sExecOne OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of interval timer ticks in Executive mode for all CPUs during the last one minute interval." ::= { sCpuLoadOneMinute 2 } sSuprOne OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of interval timer ticks in Supervisor mode for all CPUs during the last one minute interval." ::= { sCpuLoadOneMinute 3 } sUserOne OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of interval timer ticks in User mode for all CPUs during the last one minute interval." ::= { sCpuLoadOneMinute 4 } sIntrOne OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory



DESCRIPTION "Time in Interrupt mode for all CPUs during the last one minute interval. This value indicates the number of interval timer ticks in Kernel mode on the Interrupt stack." ::= { sCpuLoadOneMinute 5 } sCompOne OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of interval timer ticks in Compatibility mode for all CPUs during the last one minute interval." ::= { sCpuLoadOneMinute 6 } sSpinOne OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of interval timer ticks in mpsynch mode (i.e., Kernel mode on kernel or interrupt stack, when spinlock busy wait is active) for all CPUs during the last one minute interval." ::= { sCpuLoadOneMinute 7 } sNullOne OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "CPU idle time for all CPUs during the last one minute interval. This value is measured in interval timer ticks." ::= { sCpuLoadOneMinute 8 } -- CPU Statistics for the past five minutes sCpuLoadFiveMinute OBJECT IDENTIFIER ::= { sCpu 5 } sKernelFive OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Kernel mode during the past five minutes." ::= { sCpuLoadFiveMinute 1 } sExecFive OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Executive mode during the past five minutes." ::= { sCpuLoadFiveMinute 2 } sSuprFive OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Supervisor mode during the past five minutes." ::= { sCpuLoadFiveMinute 3 } sUserFive OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in User mode during the past five



minutes." ::= { sCpuLoadFiveMinute 4 } sIntrFive OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Interrupt mode during the past five minutes." ::= { sCpuLoadFiveMinute 5 } sCompFive OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Compatibility mode during the past five minutes." ::= { sCpuLoadFiveMinute 6 } sSpinFive OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Spin mode during the past five minutes." ::= { sCpuLoadFiveMinute 7 } sNullFive OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks the CPUs were idle during the past five minutes." ::= { sCpuLoadFiveMinute 8 } -- CPU Statistics for the past fifteen minutes sCpuLoadFifteenMinute OBJECT IDENTIFIER ::= { sCpu 6 } sKernelFifteen OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Kernel mode during the past fifteen minutes." ::= { sCpuLoadFifteenMinute 1 } sExecFifteen OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Executive mode during the past fifteen minutes." ::= { sCpuLoadFifteenMinute 2 } sSuprFifteen OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Supervisor mode during the past fifteen minutes." ::= { sCpuLoadFifteenMinute 3 } sUserFifteen OBJECT-TYPE



SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in User mode during the past fifteen minutes." ::= { sCpuLoadFifteenMinute 4 } sIntrFifteen OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Interrupt mode during the past fifteen minutes." ::= { sCpuLoadFifteenMinute 5 } sCompFifteen OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Compatibility mode during the past fifteen minutes." ::= { sCpuLoadFifteenMinute 6 } sSpinFifteen OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks spent in Spin mode during the past fifteen minutes." ::= { sCpuLoadFifteenMinute 7 } sNullFifteen OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of ticks the CPUs were idle during the past fifteen minutes." ::= { sCpuLoadFifteenMinute 8 } sCpuCondition OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), degraded(3), failed(4) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicates current condition of CPU-related statistics. DEGRADED indicates that CPU or Interrupt usage (or both) has exceeded the defined limit." ::= { sCpu 7 } -- Disk Information -- -- The disk table is a potentially sparse table of disk related information. -- Each time disk information is collected, new rows are added to the bottom -- of the disk table for new disks that are discovered. For disks that -- are no longer available, the corresponding row in the disk table becomes -- inaccessible. This allows the disk table to be walked to retrieve only -- the current disk information while ensuring that a disk index (and -- therefore the row in the disk table) relates to a specific disk. -- When the NM*SysMgr Subagent is reinitialized (see sCfgReinitSubagent), -- any inaccessible rows in the disk table are removed and the disk -- indexes and rows are re-numbered to be contiguous. -- -- Two configuration file flags are available to fine tune which disks are -- monitored: sCfgLocalDisksOnly and sCfgCritDisksOnly. These flags can -- be used alone or in combination to control which disks appear in the -- disk table (sDskTbl). Disk related traps can only be sent for disks



-- that are in the disk table. -- -- Note: When disks are shadowed, disk information is reported only -- for the shadow set virtual unit. sDskTblCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of entries in the disk table." ::= { sDsk 1 } sDskTblTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time (sCfgUpTime) when disk statistics (sDskTbl) were last gathered. sCfgDskTimer controls how often disk statistics are gathered." ::= { sDsk 2 } sDskTbl OBJECT-TYPE SYNTAX SEQUENCE OF SDskEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of disk information." ::= { sDsk 3 } sDskEntry OBJECT-TYPE SYNTAX SDskEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A row in the disk table." INDEX { sDskIndex } ::= { sDskTbl 1 } SDskEntry ::= SEQUENCE { sDskIndex INTEGER, sDskName DisplayString, sDskUsedPercent INTEGER, sDskOps INTEGER, sDskMountCnt INTEGER, sDskRefCnt INTEGER, sDskTransCnt INTEGER, sDskMediaName DisplayString, sDskOpCnt INTEGER, sDskFreeBlocks INTEGER, sDskMaxBlocks INTEGER, sDskStatus INTEGER, sDskDevChar INTEGER, sDskLogVolName DisplayString, sDskTrapPercent INTEGER, sDskTrapBlocks INTEGER, sDskShdCount Counter, sDskTrapOpSec INTEGER, sDskQueueLength Counter, sDskRemote INTEGER, sDskEntryCondition INTEGER, sDskQueueLengthDelta INTEGER, sDskQueueLengthLimit INTEGER } sDskIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION



"Location in the disk table." ::= { sDskEntry 1 } sDskName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..64)) ACCESS read-only STATUS mandatory DESCRIPTION "Device name." ::= { sDskEntry 2 } sDskUsedPercent OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The disk percent full." ::= { sDskEntry 3 } sDskOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The average number of disk operations per second during the last disk statistics update interval. (The disk statistics update frequency is determined by the variable sCfgDskTimer.)" ::= { sDskEntry 4 } sDskMountCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The mount count for the volume." ::= { sDskEntry 5 } sDskRefCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of channels assigned to the device." ::= { sDskEntry 6 } sDskTransCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The transaction count for the volume." ::= { sDskEntry 7 } sDskMediaName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..64)) ACCESS read-only STATUS mandatory DESCRIPTION "The name of the volume type." ::= { sDskEntry 8 } sDskOpCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The operation count for the volume." ::= { sDskEntry 9 } sDskFreeBlocks OBJECT-TYPE SYNTAX INTEGER



ACCESS read-only STATUS mandatory DESCRIPTION "The number of free blocks on the disk." ::= { sDskEntry 10 } sDskMaxBlocks OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The maximum number of blocks on the volume." ::= { sDskEntry 11 } sDskStatus OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The device unit status for the physical disk or virtual disk. This value is a bit vector which, when set, corresponds to the following states: Bit Description 0 TIM (time-out is enabled) 1 INT (Interrupt is expected) 2 ERLOGIP (Error log in progress on unit) 3 CANCEL (I/O on unit is canceled) 4 ONLINE (Unit is online) 5 POWER (Power failed while unit busy) 6 TIMOUT (Unit timed out) 7 INTTYPE (Receiver interrupt) 8 BSY (Unit is busy) 9 MOUNTING (Device is being mounted) 10 DEADMO (Deallocate at dismount) 11 VALID (Volume is software valid) 12 UNLOAD (Unload volume at dismount) 13 TEMPLATE (Template UCB) 14 MNTVERIP (Mount verification is in progress) 15 WRONGVOL (Wrong volume detected during mount verification) 16 DELETEUCB (Delete this UCB when reference count equals 0) 17 LCL_VALID (Volume is valid on local node) 18 SUPMVMSG (Suppress mount verification messages if they indicate success) 19 MNTVERPEND (Mount verification is pending on the device and the device is busy) 20 DISMOUNT (Dismount in progress) 21 CLUTRAN (VAXcluster state transition in progress) 22 WRTLOCKMV (Write-locked mount verification in progress) 23 SVPN_END (Last byte used from page is mapped by a system virtual page number ) 24 ALTBSY (Unit is busy via an alternate startup path) 25 SNAPSHOT (Restart verification is in progress) 26 NO_ASSIGN 27 EXFUNC_SUPP 28 FAST_PATH 29 PATHVERIP A sDskStatus trap message is sent when a device transitions into the POWER, TIMOUT, or MNTVERIP state." ::= { sDskEntry 12 } sDskDevChar OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The disk device-independent characteristics of the disk.



This value is a bit vector which, when set, corresponds to the following characteristic: Bit Description 0 REC (Device is record oriented) 1 CCL (Device is a carriage control device) 2 TRM (Device is a terminal) 3 DIR (Device is directory structured) 4 SDI (Device is single-directory structured) 5 SQD (Device is sequential and block oriented) 6 SPL (Device is being spooled) 7 OPR (Device is an operator) 8 RCT (Disk contains Revector Cache Table. This bit is set for every DAA disk) 13 NET (Device is a network device) 14 FOD (Device is files oriented) 15 DUA (Device is dual ported) 16 SHR (Device is shareable) 17 GEN (Device is a generic device) 18 AVL (Device is available for use) 19 MNT (Device is mounted) 20 MBX (Device is a mailbox) 21 DMT (Device is marked for dismount) 22 ELG (Device has error logging enabled) 23 ALL (Device is allocated) 24 FOR (Device is mounted foreign) 25 SWL (Device is software write locked) 26 IDV (Device can provide input) 27 ODV (Device can provide output) 28 RND (Device allows random access) 29 RTM (Device is a real-time device) 30 RCK (Device has read-checking enabled) 31 WCK (Device has write-checking enabled)" ::= { sDskEntry 13 } sDskLogVolName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..64)) ACCESS read-only STATUS mandatory DESCRIPTION "The logical name of the volume or volume set." ::= { sDskEntry 14 } sDskTrapPercent OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-only STATUS mandatory DESCRIPTION "The percentage of disk space utilization at which excessive disk utilization (sDskFull) traps begin to be sent for this disk. A value of 0 indicates that either a disk block free count is being used for this disk (see sDskTrapBlocks), or the system default disk use limit (identified by sCfgDskLimit), or the system default disk minimum free block limit (identified by sCfgDskMinFreeBlks) for the system is being used. Disks which have a specific usage limit set are contained in the critical disk file. See sCfgCritDsk for more information about this file." ::= { sDskEntry 15 } sDskTrapBlocks OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The minimum number of free disk blocks required for this disk. If the actual number of free blocks on the disk drops below this level, disk utilization (sDskFull) traps begin to be sent for this disk. A value of 0 indicates that either a percent full is being used for this disk (see sDskTrapPercent) or the system default disk use limit (identified by sCfgDskLimit),



or the system default disk minimum free block limit (identified by sCfgDskMinFreeBlks) for the system is being used. Disks which have a specific usage limit set are contained in the critical disk file. See sCfgCritDsk for more information about this file." ::= { sDskEntry 16 } sDskShdCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of shadow set members that make up this virtual unit. If this number is zero, then this is not a virtual disk. This number indicates the number of shadow set entries that will be found in the (sShdTbl) for this disk." ::= { sDskEntry 17 } sDskTrapOpSec OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of operations per second at which excessive disk (sDskOpSec) traps begin to be sent for this disk. A value of 0 indicates that the system default disk operations per second limit (identified by sCfgDskOps), is being used. Disks which have a specific limit set are contained in the critical disk file. If both this value and sCfgDskOps are zero, disk operations per second traps are disabled. See sCfgCritDsk for more information about the critical disk file." ::= { sDskEntry 18 } sDskQueueLength OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total I/O queue length for this disk since it was mounted." ::= { sDskEntry 19 } sDskRemote OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION "A value of true(1) indicates that the device is a remote device; a value of false(2) indicates that it is not a remote device. A remote device is a device that is not directly connected to the local node, but instead is visible through the VMScluster system." ::= { sDskEntry 20 } sDskEntryCondition OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), degraded(3), failed(4) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicates current condition of this disk entry. DEGRADED indicates that one or more of the following conditions exists: this disk's usage exceeds the defined threshold, this disk's operations/second exceeds the defined threshold, this disk's status indicates a potential problem, or a shadow set member has a status of failed, catch-up copying, or merge-copy." ::= { sDskEntry 21 } sDskQueueLengthDelta OBJECT-TYPE SYNTAX INTEGER ACCESS read-only



STATUS mandatory DESCRIPTION "I/O queue length for this disk during the last statistics gathering period." ::= { sDskEntry 22 } sDskQueueLengthLimit OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "I/O queue length threshold for this disk. When the I/O queue length (sDskQueueLengthDelta) exceeds this value, a sDskIOQLen(28) trap." ::= { sDskEntry 23 } sDskCondition OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), degraded(3), failed(4) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicates current condition of Disk-related statistics. DEGRADED indicates that one or more of the following conditions exists: a disk's usage exceeds the defined threshold, a disk's operations/second exceeds the defined threshold, a disk's status indicates a potential problem, or a shadow set member has a status of failed, catch-up copying, or merge-copy." ::= { sDsk 4 } -- Shadow set information -- -- The shadow table is a potentially sparse table of disk shadow information. -- Each time shadow information is collected, new rows are added to the -- bottom of the shadow table for new shadow sets that are discovered for the -- corresponding disk. For shadow sets that are no longer available, the -- corresponding row in the shadow table becomes inaccessible. -- When the NM*SysMgr Subagent is reinitialized (see sCfgReinitSubagent), -- any inaccessible rows in the shadow table are removed and the shadow -- indexes and rows are re-numbered to be contiguous. sShdTbl OBJECT-TYPE SYNTAX SEQUENCE OF SShdEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of shadow set information." ::= { sShd 1 } sShdEntry OBJECT-TYPE SYNTAX SShdEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A row in the shadow table. The combination of the sDskIndex and sShdIndex indices relates each shadow set table entry (sShdEntry) to its virtual unit entry in the disk table (sDskTbl)." INDEX { sDskIndex, sShdIndex } ::= { sShdTbl 1 } SShdEntry ::= SEQUENCE { sShdIndex INTEGER, sShdName DisplayString, sShdFail INTEGER, sShdCopy INTEGER, sShdMerge INTEGER } sShdIndex OBJECT-TYPE SYNTAX INTEGER



ACCESS read-only STATUS mandatory DESCRIPTION "Location in the shadow set table." ::= { sShdEntry 1 } sShdName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..64)) ACCESS read-only STATUS mandatory DESCRIPTION "Device name of the shadow set disk." ::= { sShdEntry 2 } sShdFail OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicator for shadow set member failure. A value of true(1) indicates that this member has failed out of the shadow set. " ::= { sShdEntry 3 } sShdCopy OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicator for shadow set catch-up copying. A value of true(1) indicates that this member is in a catch-up copy state." ::= { sShdEntry 4 } sShdMerge OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicator for shadow set member merge. A value of true(1) indicates that this member is in a merge state." ::= { sShdEntry 5 } -- Queue information. Names of queues to be monitored must be listed -- in the sCfgQueFile queue configuration file. The following MIB -- information relates only to those queues listed in this file. -- Refer to sCfgQueFile for information on updating the monitored -- queue information. sQueCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of queues currently being monitored. This number is the number of queue names found in the sCfgQueFile file." ::= { sQue 1 } sQueTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time (sCfgUpTime) when queue statistics (sQTbl) were last gathered. sCfgQueTimer controls how often queue statistics are gathered." ::= { sQue 2 } sQTbl OBJECT-TYPE SYNTAX SEQUENCE OF SQTblEntry



ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of queue information." ::= { sQue 3 } sQTblEntry OBJECT-TYPE SYNTAX SQTblEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A row in the queue table." INDEX { sQIndex } ::= { sQTbl 1 } SQTblEntry ::= SEQUENCE { sQIndex INTEGER, sQName DisplayString, sQMonitor INTEGER, sQStatus INTEGER, sQEntryCount INTEGER, sQCritJobCount INTEGER } sQIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Location in the queue table." ::= { sQTblEntry 1 } sQName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..31)) ACCESS read-only STATUS mandatory DESCRIPTION "Name of the queue." ::= { sQTblEntry 2 } sQMonitor OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Indicates if the queue and its entries are currently being monitored. A value of true(1) indicates that this queue and its entries are currently being monitored. A value of false(2) indicates that monitoring is currently disabled on this queue and its entries." DEFVAL { true } ::= { sQTblEntry 3 } sQStatus OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Queue status indicates the current settings of the queue status flags. This value is a bit vector which, when set, corresponds to the following characteristic: Bit Description 0 Queue is aligning 1 Queue is idle: no jobs executing and none available for execution 2 Lowercase device 3 Queue is doing /OPERATOR (intentionally not documented) 4 Queue is paused 5 Queue is pausing 6 Remote device



7 Incomplete remote request to reset (OBSOLETE) 8 Queue is resuming from paused state 9 /DEVICE=SERVER or reported to be a served queue by the symbiont 10 Device is stalled 11 Queue is starting 12 Queue is stopped 13 Queue is stopping 14 Device is unavailable 15 Queue is closed 16 Queue is executing as many jobs as it is capable of executing 17 Queue does not yet exist in db or is being removed from db 18 At least one job is executing, but the queue is capable of executing more 19 Queue is not able to accept or process jobs; its QSIs are inactive 20 AUTOSTART queue explicitly stopped 21 Queue will be stopped when work currently in progress has completed" ::= { sQTblEntry 4 } sQEntryCount OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of current queue entries. This number also identifies the number of rows in the sQEntryTbl for this queue." ::= { sQTblEntry 5 } sQCritJobCount OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of critical jobs for this queue. This number also identifies the number of rows in the sCritJobTbl for this queue." ::= { sQTblEntry 6 } sQEntryTbl OBJECT-TYPE SYNTAX SEQUENCE OF SQEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of queue entry information." ::= { sQue 4 } sQEntry OBJECT-TYPE SYNTAX SQEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A row in the queue entry table." INDEX { sQIndex, sQEntryNum } ::= { sQEntryTbl 1 } SQEntry ::= SEQUENCE { sQEntryNum INTEGER, sQEntryJobname DisplayString, sQEntryJobStatus INTEGER } sQEntryNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION



"The queue entry number of this job." ::= { sQEntry 1 } sQEntryJobname OBJECT-TYPE SYNTAX DisplayString (SIZE (0..39)) ACCESS read-only STATUS mandatory DESCRIPTION "The job name of this queue entry." ::= { sQEntry 2 } sQEntryJobStatus OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Queue status indicates the current settings of the queue status flags. This value is a bit vector which, when set, corresponds to the following characteristic: Bit Description 0 Job is aborting 1 Job is executing 2 Job is holding for /HOLD 3 Job is inaccessible 4 Job was refused by symbiont 5 Job will requeue after abort (intentionally not documented) 6 Job started execution at least once (intentionally not documented) 7 Job was retained by /RETAIN 8 Job is starting 9 Job is holding for /AFTER 10 Job is suspended by STOP/QUEUE command 11 Job is pending 12 Job does not yet exist in db or is being removed from db 13 Current job on stalled queue 14 Job was processed by the symbiont but further processing is necessary 15 Job has been completely processed" ::= { sQEntry 3 } sQueBatch OBJECT IDENTIFIER ::= { sQue 5 } sQueBatchPending OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pending jobs in the batch queue." ::= { sQueBatch 1 } sQueBatchExecuting OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of executing jobs in the batch queue." ::= { sQueBatch 2 } sQueBatchTimed OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of timed jobs in the batch queue." ::= { sQueBatch 3 } sQueBatchHolding OBJECT-TYPE SYNTAX INTEGER ACCESS read-only



STATUS mandatory DESCRIPTION "Number of holding jobs in the batch queue." ::= { sQueBatch 4 } sQueBatchRetained OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of retained jobs in the batch queue." ::= { sQueBatch 5 } sQueGeneric OBJECT IDENTIFIER ::= { sQue 6 } sQueGenericPending OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pending jobs in generic queues." ::= { sQueGeneric 1 } sQueGenericExecuting OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of executing jobs in generic queues." ::= { sQueGeneric 2 } sQueGenericTimed OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of timed jobs in generic queues." ::= { sQueGeneric 3 } sQueGenericHolding OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of holding jobs in generic queues." ::= { sQueGeneric 4 } sQueGenericRetained OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of retained jobs in generic queues." ::= { sQueGeneric 5 } sQuePrinter OBJECT IDENTIFIER ::= { sQue 7 } sQuePrinterPending OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pending jobs in printer queues." ::= { sQuePrinter 1 } sQuePrinterExecuting OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of executing jobs in printer queues."



::= { sQuePrinter 2 } sQuePrinterTimed OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of timed jobs in printer queues." ::= { sQuePrinter 3 } sQuePrinterHolding OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of holding jobs in printer queues." ::= { sQuePrinter 4 } sQuePrinterRetained OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of retained jobs in printer queues." ::= { sQuePrinter 5 } sQueServer OBJECT IDENTIFIER ::= { sQue 8 } sQueServerPending OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pending jobs in server queues." ::= { sQueServer 1 } sQueServerExecuting OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of executing jobs in server queues." ::= { sQueServer 2 } sQueServerTimed OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of timed jobs in server queues." ::= { sQueServer 3 } sQueServerHolding OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of holding jobs in server queues." ::= { sQueServer 4 } sQueServerRetained OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of retained jobs in server queues." ::= { sQueServer 5 } sQueSymbiont OBJECT IDENTIFIER ::= { sQue 9 } sQueSymbiontPending OBJECT-TYPE



SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pending jobs in symbiont queues." ::= { sQueSymbiont 1 } sQueSymbiontExecuting OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of executing jobs in symbiont queues." ::= { sQueSymbiont 2 } sQueSymbiontTimed OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of timed jobs in symbiont queues." ::= { sQueSymbiont 3 } sQueSymbiontHolding OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of holding jobs in symbiont queues." ::= { sQueSymbiont 4 } sQueSymbiontRetained OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of retained jobs in symbiont queues." ::= { sQueSymbiont 5 } sQueTerminal OBJECT IDENTIFIER ::= { sQue 10 } sQueTerminalPending OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pending jobs in terminal queues." ::= { sQueTerminal 1 } sQueTerminalExecuting OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of executing jobs in terminal queues." ::= { sQueTerminal 2 } sQueTerminalTimed OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of timed jobs in terminal queues." ::= { sQueTerminal 3 } sQueTerminalHolding OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of holding jobs in terminal queues."



::= { sQueTerminal 4 } sQueTerminalRetained OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of retained jobs in terminal queues." ::= { sQueTerminal 5 } sQMan OBJECT IDENTIFIER ::= { sQue 11 } sQManCount OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of entries in the queue manager table." ::= { sQMan 1 } sQManTbl OBJECT-TYPE SYNTAX SEQUENCE OF SQManTblEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of queue manager information." ::= { sQMan 2 } sQManTblEntry OBJECT-TYPE SYNTAX SQManTblEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A row in the queue manager table." INDEX { sQManIndex } ::= { sQManTbl 1 } SQManTblEntry ::= SEQUENCE { sQManIndex INTEGER, sQManName DisplayString, sQManStatus INTEGER } sQManIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Location in the queue manager table." ::= { sQManTblEntry 1 } sQManName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..31)) ACCESS read-only STATUS mandatory DESCRIPTION "Name of the queue manager." ::= { sQManTblEntry 2 } sQManStatus OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Queue manager status indicates the current settings of the queue manager status flags. This value is a bit vector which, when set, corresponds to the following characteristic: Bit Description 0 Start pending 1 Starting



2 Running 3 Failover 4 Stopping 5 Stopped" ::= { sQManTblEntry 3 } sQCondition OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), degraded(3), failed(4) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicates current condition of Queue-related statistics. DEGRADED indicates that either status or a queue entry status indicates a potential problem." ::= { sQue 12 } sCritJobCondition OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), degraded(3), failed(4) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicates current condition of critical jobs. DEGRADED indicates that at least one critical job is missing from its specified queue." ::= { sQue 13 } sCritJobTbl OBJECT-TYPE SYNTAX SEQUENCE OF SCritJobEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of critical job information." ::= { sQue 14 } sCritJobEntry OBJECT-TYPE SYNTAX SCritJobEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A row in the critical job table." INDEX { sQIndex, sCritJobNum } ::= { sCritJobTbl 1 } SCritJobEntry ::= SEQUENCE { sCritJobNum INTEGER, sCritJobName DisplayString, sCritJobFound INTEGER } sCritJobNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The row number for the critical job table for this queue." ::= { sCritJobEntry 1 } sCritJobName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..39)) ACCESS read-only STATUS mandatory DESCRIPTION "The job name of the critical job." ::= { sCritJobEntry 2 } sCritJobFound OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION



"Indicates if this job is present in this queue." ::= { sCritJobEntry 3 } -- Process statistics for all processes currently running on the system sPsCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes currently running of the system." ::= { sProcInfo 1 } sPsTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time (sCfgUpTime) when process statistics (sPsTbl) were last gathered. sCfgPsTimer controls how often process statistics are gathered." ::= { sProcInfo 2 } sPsTbl OBJECT-TYPE SYNTAX SEQUENCE OF SPsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of process information." ::= { sProcInfo 3 } sPsEntry OBJECT-TYPE SYNTAX SPsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A row in the process table." INDEX { sPsPID } ::= { sPsTbl 1 } SPsEntry ::= SEQUENCE { sPsPID INTEGER, sPsProcName DisplayString, sPsState INTEGER, sPsPriority INTEGER, sPsDirectIO INTEGER, sPsCpuTime TimeTicks, sPsPgFaults INTEGER, sPsWorkSetSize INTEGER, sPsUsername DisplayString, sPsPhysTerm DisplayString, sPsImageName DisplayString, sPsLoginTime DisplayString, sPsPgTblCnt INTEGER, sPsMode INTEGER, sPsRWState INTEGER } sPsPID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The VMS process identification (PID) of the process." ::= { sPsEntry 1 } sPsProcName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..15)) ACCESS read-only STATUS mandatory DESCRIPTION "The process name."



::= { sPsEntry 2 } sPsState OBJECT-TYPE SYNTAX INTEGER { colpg(1), mwait(2), cef(3), pfw(4), lef(5), lefo(6), hib(7), hibo(8), susp(9), suspo(10), fpg(11), com(12), como(13), cur(14) } ACCESS read-only STATUS mandatory DESCRIPTION "The state of the process." ::= { sPsEntry 3 } sPsPriority OBJECT-TYPE SYNTAX INTEGER (0..31) ACCESS read-only STATUS mandatory DESCRIPTION "The current priority of the process." ::= { sPsEntry 4 } sPsDirectIO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The count of the direct I/O operations performed by this process. If sCfgAllPsData is set to no(2), this value may be zero." ::= { sPsEntry 5 } sPsCpuTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The process' accumulated CPU time. If sCfgAllPsData is set to no(2), this value may be zero." ::= { sPsEntry 6 } sPsPgFaults OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The total number of page faults incurred by the process. If sCfgAllPsData is set to no(2), this value may be zero." ::= { sPsEntry 7 } sPsWorkSetSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The current working set size (in pages) of the process. If sCfgAllPsData is set to no(2), this value may be zero." ::= { sPsEntry 8 } sPsUsername OBJECT-TYPE SYNTAX DisplayString (SIZE (12))



ACCESS read-only STATUS mandatory DESCRIPTION "The owner username of the process. This string is always blank padded to a length of 12 characters." ::= { sPsEntry 9 } sPsPhysTerm OBJECT-TYPE SYNTAX DisplayString (SIZE (0..8)) ACCESS read-only STATUS mandatory DESCRIPTION "The physical device name of the terminal associated with the process." ::= { sPsEntry 10 } sPsImageName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The directory specification and image file name. If sCfgAllPsData is set to no(2), this value may be zero." ::= { sPsEntry 11 } sPsLoginTime OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "The time at which the process was created. This value is in dd-mmm-yyyy hh:mm:ss.cc format. If sCfgAllPsData is set to no(2), this value may be zero." ::= { sPsEntry 12 } sPsPgTblCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of pages the process has in its working set." ::= { sPsEntry 13 } sPsMode OBJECT-TYPE SYNTAX INTEGER { other(1), network(2), batch(3), interactive(4) } ACCESS read-only STATUS mandatory DESCRIPTION "The mode of the process." ::= { sPsEntry 14 } sPsRWState OBJECT-TYPE SYNTAX INTEGER { astwait(1), mailbox(2), npdynmem(3), pgfile(4), pgdynmem(5), mplempty(11), mpwbusy(12), scs(13), clustran(14), cpucap(15), clusrv(16), psxfrk(18), mutex(19) } ACCESS read-only



STATUS mandatory DESCRIPTION "The resource wait state of the process. This variable is only meaningful when a process is in the MWAIT state (i.e., when sPsState is set to MWAIT(2)), otherwise this variable contains no data. The above listed resource wait states have the following meanings: AST - AST wait MBX - Mailbox full NPG - Nonpaged dynamic memory PFF - Page file full PAG - Paged dynamic memory MPE - Modified page list empty MPB - Modified page writer busy SCS - Distributed lock manager wait CLU - VMScluster transition CAP - CPU capability CSV - VMScluster server process PSXFRK - POSIX fork creation MUTEX - Locked resource" ::= { sPsEntry 15 } sPsCOMQueue OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes that are waiting to compute, i.e., the number of processes with a sPsState of COM." ::= { sProcInfo 4 } sPsCOMOQueue OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of outswapped processes that are waiting to compute, i.e., the number of processes with a sPsState of COMO." ::= { sProcInfo 5 } sPsOther OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of other mode processes i.e., those processes that are not network, batch or interactive." ::= { sProcInfo 6 } sPsNetwork OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of network processes." ::= { sProcInfo 7 } sPsBatch OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of batch processes." ::= { sProcInfo 8 } sPsInteractive OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of Interactive processes."



::= { sProcInfo 9 } sPsAvailProcSlots OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of Available Process Slots." ::= { sProcInfo 10 } sPsCondition OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), degraded(3), failed(4) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicates current condition of Process-related statistics. DEGRADED indicates that one or more of the following conditions exist: too many processes in COM state, too many processes in COMO state, one or more processes in MWAIT state." ::= { sProcInfo 11 } sPsMWAITCount OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of processes currently in MWAIT state." ::= { sProcInfo 12 } -- Critical process table -- This table reflects the current status of the critical processes -- contained in the critical process file specified in sCfgCritFile sCritCnt OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-only STATUS mandatory DESCRIPTION "Number of critical process table entries." ::= { sCritInfo 1 } sCritTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time (sCfgUpTime) when critical process statistics (sCritTbl) were last gathered. sCfgCritTimer specifies how often critical process statistics are gathered." ::= { sCritInfo 2 } sCritTbl OBJECT-TYPE SYNTAX SEQUENCE OF SCritEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of critical process information." ::= { sCritInfo 3 } sCritEntry OBJECT-TYPE SYNTAX SCritEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A row in the critical process table." INDEX { sCritIndex } ::= { sCritTbl 1} SCritEntry ::= SEQUENCE { sCritIndex INTEGER, sCritName DisplayString,



sCritReqCnt INTEGER, sCritCurCnt INTEGER, sCritBufIO Counter, sCritCpuTime Counter, sCritDirIO Counter, sCritPageFlts Counter } sCritIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Location in the critical process table." ::= { sCritEntry 1 } sCritName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..15)) ACCESS read-only STATUS mandatory DESCRIPTION "Name of a critical process. Critical process names may contain * and % wildcard characters." ::= { sCritEntry 2 } sCritReqCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Minimum number of copies of this process required to be running on the system." ::= { sCritEntry 3 } sCritCurCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The current number of copies of this process running on the system." ::= { sCritEntry 4 } sCritBufIO OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total buffered I/O for all instances of this process." ::= { sCritEntry 5 } sCritCpuTime OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total CPU time for all instances of this process." ::= { sCritEntry 6 } sCritDirIO OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The total direct I/O for all instances of this process. the system." ::= { sCritEntry 7 } sCritPageFlts OBJECT-TYPE SYNTAX Counter ACCESS read-only



STATUS mandatory DESCRIPTION "The total pages faults for all instances of this process." ::= { sCritEntry 8 } sCritCondition OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), degraded(3), failed(4) } ACCESS read-only STATUS mandatory DESCRIPTION "Indicates current condition of Critical Process statistics. DEGRADED indicates that at least one critical process is missing." ::= { sCritInfo 4 } -- Trap Information -- The NM*SysMgr Subagent process maintains an internal trap table -- containing the latest traps that have been sent by the subagent. -- The number of traps that are retained in the internal trap table -- is controlled by the sCfgTrapTblSize variable. Each trap that is -- sent by NM*SysMgr includes a trap sequence number and a timestamp -- as well as any trap specific data. The trap sequence number may -- be used to request that a trap be resent to the manager. -- -- The number of traps per second that may be sent is governed by the -- sCfgMaxTrapSec variable. sTrapLastSeqNumSent identifies the -- sequence number of the last trap that was actually sent, if no -- backlog of traps exists, this number will be one less than -- sTrapNextSeqNum. If a backlog exists due to throttling, then -- the size of the backlog may be determined by comparing these -- numbers. If the size of the backlog exceeds the size of the -- trap table (as set by sCfgTrapTblSize), the backlogged traps -- will be lost as they are overwritten by new traps, the number -- of traps that have been lost is contained in sTrapLostCount. sTrapNextSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The next sequence number in the trap table. When this variable is sent as part of a trap, it identifies the sequence number assigned to that trap. This is a 32-bit value and will wrap after 4294967295." ::= { sTrapInfo 1 } sTrapTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time (sCfgUpTime) when the trap was created." ::= { sTrapInfo 2 } sTrapResendSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "Sequence number of a trap message to be resent to the manager. Setting this variable to a trap sequence number causes the specified trap message to be resent. If the set-request contains a number that is not available (the number of items retained in the trap table is dependent on the value of sCfgTrapTblSize), an error indicator will be returned." ::= { sTrapInfo 3 } sTrapLastSeqNumSent OBJECT-TYPE SYNTAX INTEGER ACCESS read-only



STATUS mandatory DESCRIPTION "Sequence number of the last trap sent. This value may be compared to sTrapNextSeqNum to determine if a backlog of traps exists. If this value is one less than sTrapNextSeqNum, then no backlog exists. A backlog of traps may exist if more traps are generated per second than may be sent (as specified by the variable sCfgMaxTrapSec)." ::= { sTrapInfo 4 } sTrapLostCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates the number of traps that have been lost. A trap is considered to be lost if it is overwritten in the internal trap table before it is sent to the NMS. This may occur if the trap table is not large enough (see sCfgTrapTblSize) to hold all of unsent traps. How quickly traps are sent to the NMS is governed by the sCfgMaxTrapSec variable. To prevent trap loss, set these two variables so that the trap backlog does not overflow the trap table and so that traps do not flood the network." ::= { sTrapInfo 5 } sTrapTextTbl OBJECT-TYPE SYNTAX SEQUENCE OF STrapTextEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of textual trap messages." ::= { sTrapInfo 6 } sTrapTextEntry OBJECT-TYPE SYNTAX STrapTextEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A row in the trap text table." INDEX { sTrapTextSeqNum } ::= { sTrapTextTbl 1 } STrapTextEntry ::= SEQUENCE { sTrapTextSeqNum INTEGER, sTrapTimeStamp DisplayString, sTrapType INTEGER, sTrapText1 DisplayString, sTrapText2 DisplayString, sTrapText3 DisplayString, sTrapText4 DisplayString, sTrapText5 DisplayString, sTrapText6 DisplayString, sTrapText7 DisplayString } sTrapTextSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Sequence number of the trap." ::= { sTrapTextEntry 1 } sTrapTimeStamp OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "System time when trap occurred." ::= { sTrapTextEntry 2 }



sTrapType OBJECT-TYPE SYNTAX INTEGER { coldStart(1), error(2), hardwareError(3), cpuUsage(4), intUsage(5), diskBusy(6), diskFull(7), diskFullClear(8), swapFull(9), swapFullClear(10), pageFull(11), pageFullClear(12), criticalProcess(13), opcom(14), terminate(15), diskStatus(16), warmStart(17), shadowFail(18), shadowCopy(19), shadowMerge(20), queueStatus(21), jobStatus(22), processStatus(23), memoryFull(24), memoryFullClear(25), comQueue(26), comoQueue(27), critProcClear(28), dskIOQLen(29), jobMissing(30), mwaitLimit(31) } ACCESS read-only STATUS mandatory DESCRIPTION "Type of trap." ::= { sTrapTextEntry 3 } sTrapText1 OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Part 1 of the trap text." ::= { sTrapTextEntry 4 } sTrapText2 OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Part 2 of the trap text." ::= { sTrapTextEntry 5 } sTrapText3 OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Part 3 of the trap text." ::= { sTrapTextEntry 6 } sTrapText4 OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Part 4 of the trap text." ::= { sTrapTextEntry 7 }



sTrapText5 OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Part 5 of the trap text." ::= { sTrapTextEntry 8 } sTrapText6 OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Part 6 of the trap text." ::= { sTrapTextEntry 9 } sTrapText7 OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Part 7 of the trap text." ::= { sTrapTextEntry 10 } -- Hardware error information for disks, tapes, buses, CPU, and memory -- -- The hardware error table is a potentially sparse table of device errors. -- Each time hardware error information is collected, new rows are added -- to the bottom of the hardware error table for devices that had not -- previously reported errors. For devices that are no longer available, -- the corresponding row in the hardware error table becomes inaccessible. -- This allows the hardware error table to be walked to retrieve only the -- current error information while ensuring that a hardware error table -- index (and therefore the row in the hardware error table) relates to a -- specific device. When the NM*SysMgr Subagent is reinitialized -- (see sCfgReinitSubagent), any inaccessible rows in the hardware error -- table are removed and the hardware error table indexes and rows are -- re-numbered to be contiguous. -- -- Note: Disk errors for shadowed disks are reported by physical shadow -- set member, they are not reported for the shadow set virtual unit. sHwErrDeviceCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of devices reporting errors." ::= { sHwErrInfo 1 } sHwErrTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time (sCfgUpTime) when hardware error statistics were last gathered." ::= { sHwErrInfo 2 } sHwErrTbl OBJECT-TYPE SYNTAX SEQUENCE OF SHwErrEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of hardware errors." ::= { sHwErrInfo 3 } sHwErrEntry OBJECT-TYPE SYNTAX SHwErrEntry



ACCESS not-accessible STATUS mandatory DESCRIPTION "A row in the hardware error table." INDEX { sHwErrIndex } ::= { sHwErrTbl 1 } SHwErrEntry ::= SEQUENCE { sHwErrIndex INTEGER, sHwErrDeviceName DisplayString, sHwErrCnt INTEGER, sHwErrLastTime TimeTicks } sHwErrIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Location in the hardware error table." ::= { sHwErrEntry 1 } sHwErrDeviceName OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Name of the device." ::= { sHwErrEntry 2 } sHwErrCnt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of errors reported by the device since last reboot of the system." ::= { sHwErrEntry 3 } sHwErrLastTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "sCfgUpTime when the latest error was detected by the NM*SysMgr Subagent." ::= { sHwErrEntry 4 } -- When a software error is encountered, a sSwErr trap is generated containing -- the following software error description items. Invalid sets of the -- sCfgFile or sCfgCritFile variable will cause a sSwErr trap to be generated -- to explain the error. sSwErrStatus OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The latest software status code." ::= { sSwErrInfo 1 } sSwErrFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The file name of the software element which generated the latest software status code." ::= { sSwErrInfo 2 } sSwErrLineNum OBJECT-TYPE SYNTAX INTEGER



ACCESS read-only STATUS mandatory DESCRIPTION "The line number in the file which generated the latest software status code." ::= { sSwErrInfo 3 } sSwErrLastTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "sCfgUpTime when the most recent software status code was generated." ::= { sSwErrInfo 4 } sSwErrMessage OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Description of the latest software error." ::= { sSwErrInfo 5 } -- Operator (OpCom) information sOpcomOne OBJECT-TYPE SYNTAX DisplayString (SIZE (1..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The first 255 characters of the text of the most recent message in the operator log. For opcom messages that exceed 255 characters, the remainder of the message will be contained in sOpcomTwo, sOpcomThree, sOpcomFour, sOpcomFive, sOpcomSix, and sOpcomSeven depending on the length of the message. All operator log messages are sent as sOpcomMessage traps and retained in the internal trap table. To retrieve a previous message, resend the trap (see sTrapResendSeqNum)." ::= { sErrInfo 3 } sOpcomTwo OBJECT-TYPE SYNTAX DisplayString (SIZE (1..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 2 of an opcom message." ::= { sErrInfo 4 } sOpcomThree OBJECT-TYPE SYNTAX DisplayString (SIZE (1..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 3 of an opcom message." ::= { sErrInfo 5 } sOpcomFour OBJECT-TYPE SYNTAX DisplayString (SIZE (1..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 4 of an opcom message." ::= { sErrInfo 6 } sOpcomFive OBJECT-TYPE SYNTAX DisplayString (SIZE (1..255)) ACCESS read-only STATUS mandatory DESCRIPTION



"Part 5 of an opcom message." ::= { sErrInfo 7 } -- The following sOpcom variables may be used to send a reply to an -- operator request. sOpcomReplyId OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "Request number to be associated with the operator reply. This number identifies a previous Opcom request. This variable is reset to zero when a reply is successfully sent. (See sOpcomReplySend.)" DEFVAL { 0 } ::= { sErrInfo 8 } sOpcomReplyStatus OBJECT-TYPE SYNTAX INTEGER { noStatus(1), blankTape(2), initializeTape(3), requestComplete(4), requestPending(5), requestAborted(6) } ACCESS read-write STATUS mandatory DESCRIPTION "Completion status to accompany opcom reply. This variable is reset to noStatus when a reply is successfully sent. (See sOpcomReplySend.)" DEFVAL { noStatus } ::= { sErrInfo 9 } sOpcomReplyText OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Text to be sent for an operator reply message. This variable is reset to null when a reply is successfully sent. (See sOpcomReplySend.)" DEFVAL { "" } ::= { sErrInfo 10 } sOpcomReplySend OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which is used to trigger sending of an operator reply message. To send an operator reply, set the sOpcomReplyId, sOpcomReplyStatus, and sOpcomReplyText variables and then set the sOpcomReplySend to true. All opcom reply variables will be reset following a successful send." DEFVAL { false } ::= { sErrInfo 11 } sOpcomSix OBJECT-TYPE SYNTAX DisplayString (SIZE (1..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 6 of an opcom message." ::= { sErrInfo 12 } sOpcomSeven OBJECT-TYPE SYNTAX DisplayString (SIZE (1..255)) ACCESS read-only STATUS mandatory



DESCRIPTION "Part 7 of an opcom message." ::= { sErrInfo 13 } -- Configuration parameters which are read from disk and may be -- viewed/changed by the network manager. All changes to these -- parameters are written to the disk file. sCfgFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file currently being used for NM*SysMgr initialization parameters. This file is identified by the logical name COMTEK$SYSMGR_CONFIG. Changing this variable redefines the COMTEK$SYSMGR_CONFIG logical name. NM*SysMgr must be reinitialized (by setting the variable sCfgReinitSubagent to true) before the new configuration file is used. If a set-request is performed on this variable and the specified file name does not exist, is not accessible by the subagent, or contains invalid data, the file name is not changed, and an error is returned, and a sSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (sCfgReinitSubagent) NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures." ::= { sCfg 1 } sCfgLogFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Name of the log file currently being used by NM*SysMgr. If this process is run interactively, this variable will have the value SYS$OUTPUT: (standard output)." ::= { sCfg 2 } sCfgCritFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file currently being used to identify critical processes. This file is associated with the logical name COMTEK$SYSMGR_CRITPROC. Changing this variable redefines the COMTEK$SYSMGR_CRITPROC logical name. NM*SysMgr must be reinitialized (by setting the variable sCfgReinitSubagent to true) before the new critical process file is used. If a set-request is performed on this variable and the specified file name does not exist, is not accessible by the subagent, or contains invalid data, the file name is not changed, an error is returned, and a sSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (sCfgReinitSubagent) NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures." ::= { sCfg 3 } sCfgReinitSubagent OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory



DESCRIPTION "Flag which may be set to force the NM*SysMgr Subagent to reinitialize. Reinitialization involves resetting the process configuration using the parameters contained in the sCfgFile and resetting the critical process, critical disk, and critical queue data as specified in the sCfgCritFile, sCfgCritDsk, and sCfgCritQue files and sending the sWarmStart trap." DEFVAL { false } ::= { sCfg 4 } sCfgTraps OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if any trap messages are sent to the NM*Master Agent. Setting this variable to disabled(2) disables all traps from being sent. Configuration Variable: Traps Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 5 } sCfgHwErrTraps OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if hardware error traps (sHwErr) should be sent. Setting this variable to enabled(1) causes a trap to be sent for every error detected. Setting this variable to disabled(2) disables hardware error traps from being sent. Configuration Variable: HwErrTrap Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 6 } sCfgCpuLimit OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "The percentage of CPU utilization at which excessive CPU utilization (sCpuUsage) traps begin to be sent. A value of 0 disables these traps. The variable sCfgCpuPersist can be used to specifiy the number of consecutive minutes the CPU utilization threshold must be exceeded before a trap is sent. Configuration Variable: CpuUtil Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 90 } ::= { sCfg 7 } sCfgIntLimit OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "The percentage of interrupt CPU utilization at which



excessive interrupt utilization (sIntUsage) traps begin to be sent. A value of 0 disables these traps. Configuration Variable: IntUtil Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 20 } ::= { sCfg 8 } sCfgDskOps OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The threshold at which excessive disk busy traps (sDskOpSec) begin to be sent. This value is expressed in terms of disk operations (reads and writes) per second. At expiration of each sCfgDskTimer interval, the number of disk operations during the intervening interval is computed. A trap is sent if the number of operations during that interval exceeds the this limit. A value of 0 disables disk busy traps. Different thresholds may be set on individual disks by specifying an OpSec limit in the critical disk file. Configuration Variable: DskOps Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 25 } ::= { sCfg 9 } sCfgDskLimit OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "The percentage of disk space utilization at which excessive disk utilization (sDskFull) traps begin to be sent. If this variable is set to a value other than zero, it is used to determine when to send sDskFull traps for disks not specified in the critical disk table (see sCfgCritDsk). This value and sCfgDskMinFreeBlks are mutually exclusive, i.e., only one of these values is in effect at any given time. If neither value is specified in the configuration file, then the default value of sCfgDskLimit is used for disk monitoring and sCfgDskMinFreeBlks is set to zero. To disable default disk full monitoring, both of these values must be zero. Set-requests to this value will fail unless sCfgDskMinFreeBlks is set to zero. Configuration Variable: DskUse Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 90 } ::= { sCfg 10 } sCfgPgLimit OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "The percentage of page file utilization at which excessive page file utilization (sPgFull) traps begin to be sent. A value of 0 disables these traps. Configuration Variable: PgUse Set-requests: Take effect immediately



Changes to this value are written to the sCfgFile." DEFVAL { 90 } ::= { sCfg 11 } sCfgSwpLimit OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "The percentage of swap file utilization at which excessive swap file utilization (sSwpFull) traps begin to be sent. A value of 0 disables these traps. Configuration Variable: SwpUse Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 90 } ::= { sCfg 12 } sCfgPsTimer OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of minutes between updates of the process statistics table (sPsTbl) data. A value of 0 disables gathering of process related data. Configuration Variable: PsTimer Set-requests: Take effect on next timer expiration Changes to this value are written to the sCfgFile." DEFVAL { 5 } ::= { sCfg 13 } sCfgDskTimer OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of minutes between updates of the disk table (sDskTbl) data. A value of 0 disables gathering of disk related data. Configuration Variable: DskTimer Set-requests: Take effect on next timer expiration Changes to this value are written to the sCfgFile." DEFVAL { 1 } ::= { sCfg 14 } sCfgHwErrTimer OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of minutes between updates of the hardware error table (sHwErrTbl) data. A value of 0 disables gathering of hardware error data. Configuration Variable: HwErrTimer Set-requests: Take effect on next timer expiration Changes to this value are written to the sCfgFile." DEFVAL { 1 } ::= { sCfg 15 }



sCfgSysInfoTimer OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of minutes between updates of the system information (sSyi) data. A value of 0 disables gathering of system information data. Configuration Variable: SysInfoTimer Set-requests: Take effect on next timer expiration Changes to this value are written to the sCfgFile." DEFVAL { 1 } ::= { sCfg 16 } sCfgCritTimer OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of minutes between critical process table (sCritTbl) updates. A value of 0 disables critical process missing processing. Configuration Variable: CritTimer Set-requests: Take effect on next timer expiration Changes to this value are written to the sCfgFile." DEFVAL { 1 } ::= { sCfg 17 } sCfgDskAlarm OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of minutes between repeat traps for disk (sDskFull), page file (sPgFull), or swap file full (sSwpFull) conditions. A value of 0 causes only the initial instance of the disk, page file, or swap file full condition to trigger a trap. Configuration Variable: RptDskAlarm Set-requests: Take effect on next timer expiration Changes to this value are written to the sCfgFile." DEFVAL { 5 } ::= { sCfg 18 } sCfgCritAlarm OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of minutes between repeat traps for a given critical process missing condition. Setting this variable to 0 causes only the first instance to generate a trap. Configuration Variable: RptCritAlarm Set-requests: Take effect on next timer expiration Changes to this value are written to the sCfgFile." DEFVAL { 5 } ::= { sCfg 19 } sCfgTrapTblSize OBJECT-TYPE



SYNTAX INTEGER (10..5000) ACCESS read-write STATUS mandatory DESCRIPTION "The maximum number of traps to be retained. Traps that are retained may be resent (see sTrapResendSeqNum) unless too many subsequent traps have been generated. This variable controls how many traps are retained in NM*SysMgr's internal trap table. Configuration Variable: TrapTableSize Set-Requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 100 } ::= { sCfg 20 } sCfgHostName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The name of the host that the subagent is communicating with. This is the host name where the NM*Master Agent resides. This variable is not currently used. Configuration Variable: Host" DEFVAL { "localhost" } ::= { sCfg 21 } sCfgAllPsData OBJECT-TYPE SYNTAX INTEGER { yes(1), no(2) } ACCESS read-write STATUS mandatory DESCRIPTION "This variable controls the amount of data that is available in the process statistics table (sPsTbl). If this flag is set to no(2), only the process statistics that are contained in the process control block (PCB) or job information block (JIB) for each process are available (data in the process header (PHD) may also be available). Setting this flag to yes makes all statistics in the sPsTbl available but incurs an additional performance overhead (to retrieve out swapped processes and deliver kernel mode ASTs to all processes). Configuration variable: AllPsData Set-requests: Take effect immediately. Changes to this value are written to the sCfgFile." DEFVAL { no } ::= { sCfg 22 } sCfgTimeout OBJECT-TYPE SYNTAX INTEGER (0..3600) ACCESS read-only STATUS mandatory DESCRIPTION "This variable identifies the time-out value that is to be used by the subagent during subtree registration. If this value is set to zero, the default value (saDefaultTimeout) contained in the NM*Master Agent will be used. If the value specified exceeds the current maximum that NM*Master will permit (saMaxTimeout), the maximum value will be used. This value is specified in seconds. Configuration Variable: Timeout" DEFVAL { 0 } ::= { sCfg 23 } sCfgOpcomSecurity OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) }



ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if the opcom security messages are to be sent as opcom traps. Setting this variable to enabled(1) causes opcom trap messages to be sent for security messages. Configuration Variable: OpcomSecurity Set-requests: Take effect at next process start-up Changes to this value are written to the tCfgFile." DEFVAL { enabled } ::= { sCfg 24 } sCfgControlTermProc OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Flag which may be used to disable process termination by the sCfgTermProc variable. Setting this variable to enabled(1) allows the sCfgTermProc variable to be set to true(1) to terminate the NM*SysMgr process. Setting this variable to disabled(2) prevents the sCfgTermProc variable from being set. Configuration Variable: ControlTermProc" DEFVAL { disabled } ::= { sCfg 25 } sCfgTermProc OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be used to shutdown the NM*SysMgr process. Setting this flag to true causes the NM*SysMgr process to respond to the set-request, send the sTermProc trap, close the connection to the NM*Master Agent, and shutdown. If the sCfgControlTermProc flag state is disabled(2), the sCfgTermProc variable can not be set. Set-requests: Take effect immediately if sCfgControlTermProc is enabled(2)" DEFVAL { false } ::= { sCfg 26 } sCfgVersion OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Current version of the NM*SysMgr Subagent software." ::= { sCfg 27 } sCfgUpTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time." ::= { sCfg 28 } sCfgMaxTrapSec OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "This value specifies the maximum number of traps per second that may be sent. A value of zero disables trap throttling, allowing all traps to be sent as they are generated. It



is recommended that this value and sCfgTrapTblSize be tuned to each operational environment. Configuration Variable: MaxTrapSec Set-requests: Take effect immediately. Changes to this value are written to the sCfgFile." DEFVAL { 0 } ::= { sCfg 29 } sCfgCritDsk OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file currently being used to identify critical disk space and operations per second trap thresholds for individual disks. This file contains: disk name (required) percent full or number of free blocks (optional) operations per second (optional) The disk name may take the form of a physical disk name (including the leading underscore (_) and trailing colon (:)), a logical volume name, or, for shadowed disks, the name of the virtual unit. If two entries specify the same disk (one by physical name and the other by logical volume name), only the entry for the physical disk name will be used for that disk. Once the disk usage exceeds the specified percent full or the number of free blocks drops below the specified free disk blocks, disk full (sDskFull) traps will begin to be sent. Disk busy (sDskOpSec) traps are sent if the number of operations per second exceeds the limit specified for this disk. The following are valid entries in the critical disk file: _ALPHA$DKA0:,blocks=652829 disk$alphasys,percent=99,ops=120 _DSA1:,ops=300 This file is associated with the system logical name COMTEK$SYSMGR_CRITDSK. Changing this variable redefines the COMTEK$SYSMGR_CRITDSK logical name. NM*SysMgr must be reinitialized (by setting the variable sCfgReinitSubagent to true) before a new critical disk file is used. If a set-request is performed on this variable and the specified file name does not exist, is not accessible by the subagent, or contains invalid data, the file name is not changed, an error is returned, and a sSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (sCfgReinitSubagent) NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures." ::= { sCfg 30 } sCfgCritQue OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file currently being used to identify queues to be monitored. This file is associated with the logical name COMTEK$SYSMGR_QUEUE. Changing this variable redefines the COMTEK$SYSMGR_QUEUE logical name. NM*SysMgr must be reinitialized (by setting the variable sCfgReinitSubagent



to true) before the new queue file is used. If a set-request is performed on this variable and the specified file name does not exist, is not accessible by the subagent, or contains invalid data, the file name is not changed, an error is returned, and a sSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (sCfgReinitSubagent) NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures." ::= { sCfg 31 } sCfgQueTimer OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of minutes between updates of the queue statistics table (sQTbl) data. A value of 0 disables gathering of queue related data. Configuration Variable: QueTimer Set-requests: Take effect on next timer expiration Changes to this value are written to the sCfgFile." DEFVAL { 1 } ::= { sCfg 32 } sCfgDskMinFreeBlks OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The minimum number of disk blocks that must be free on a disk. When the number of free blocks on a disk drops below this level, excessive disk utilization (sDskFull) traps begin to be sent. If this variable is set to a value other than zero, it is used to determine when to send sDskFull traps for disks not specified in the critical disk table (see sCfgCritDsk). This value and sCfgDskLimit are mutually exclusive, i.e., only one of these values is in effect at any given time. If neither value is specified in the configuration file, then the default value of sCfgDskLimit is used for disk monitoring and sCfgDskMinFreeBlks is set to zero. To disable default disk full monitoring, both of these values must be zero. Set-requests to this value will fail unless sCfgDskLimit is set to zero. Configuration Variable: DskMinFreeBlks Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." ::= { sCfg 33 } sCfgMemLimit OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "The percentage of physical memory utilization at which excessive memory utilization (sMemFull) traps begin to be sent. A value of 0 disables these traps. Configuration Variable: MemUse



Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 90 } ::= { sCfg 34 } sCfgCOMQueueLimit OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of processes in COM state at which excessive compute queue (sCOMQue) traps begin to be sent. A value of 0 disables these traps. Configuration Variable: COMQueue Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 5 } ::= { sCfg 35 } sCfgCOMOQueueLimit OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of processes in COMO state at which excessive outswapped compute queue (sCOMOQue) traps begin to be sent. A value of 0 disables these traps. Configuration Variable: COMOQueue Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 1 } ::= { sCfg 36 } sCfgOpcomCards OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom CARDS class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving CARDS opcom messages. Configuration Variable: Cards Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 37 } sCfgOpcomCentral OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom CENTRAL class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving CENTRAL opcom messages. Configuration Variable: Central Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 38 } sCfgOpcomCluster OBJECT-TYPE



SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom CLUSTER class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving CLUSTER opcom messages. Configuration Variable: Cluster Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 39 } sCfgOpcomDevices OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom DEVICES class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving DEVICES opcom messages. Configuration Variable: Devices Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 40 } sCfgOpcomDisks OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom DISKS class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving DISKS opcom messages. Configuration Variable: Disks Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 41 } sCfgOpcomLicense OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom LICENSE class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving LICENSE opcom messages. Configuration Variable: License Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 42 } sCfgOpcomNetwork OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom NETWORK class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving NETWORK opcom messages.



Configuration Variable: Network Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 43 } sCfgOpcomOper1 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER1 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER1 opcom messages. Configuration Variable: Oper1 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 44 } sCfgOpcomOper2 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER2 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER2 opcom messages. Configuration Variable: Oper2 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 45 } sCfgOpcomOper3 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER3 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER3 opcom messages. Configuration Variable: Oper3 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 46 } sCfgOpcomOper4 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER4 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER4 opcom messages. Configuration Variable: Oper4 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 47 }



sCfgOpcomOper5 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER5 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER5 opcom messages. Configuration Variable: Oper5 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 48 } sCfgOpcomOper6 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER6 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER6 opcom messages. Configuration Variable: Oper6 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 49 } sCfgOpcomOper7 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER7 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER7 opcom messages. Configuration Variable: Oper7 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 50 } sCfgOpcomOper8 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER8 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER8 opcom messages. Configuration Variable: Oper8 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 51 } sCfgOpcomOper9 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom



OPER9 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER9 opcom messages. Configuration Variable: Oper9 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 52 } sCfgOpcomOper10 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER10 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER10 opcom messages. Configuration Variable: Oper10 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 53 } sCfgOpcomOper11 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER11 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER11 opcom messages. Configuration Variable: Oper11 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 54 } sCfgOpcomOper12 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom OPER12 class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving OPER12 opcom messages. Configuration Variable: Oper12 Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 55 } sCfgOpcomPrinter OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom PRINTER class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving PRINTER opcom messages. Configuration Variable: Printer Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile."



DEFVAL { enabled } ::= { sCfg 56 } sCfgOpcomTapes OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will receive opcom TAPES class messages. Setting this variable to disabled(2) disables NM*SysMgr from receiving TAPES opcom messages. Configuration Variable: Tapes Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { enabled } ::= { sCfg 57 } sCfgOpcomFilter OBJECT-TYPE SYNTAX INTEGER { dropMatch(1), keepMatch(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr will drop opcom messages that match filter criteria or drop all opcom messages except those that match filter criteria. Configuration Variable: Filter Set-requests: Take effect on next process start-up Changes to this value are written to the sCfgFile." DEFVAL { dropMatch } ::= { sCfg 58 } sCfgLocalDisksOnly OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be used to instruct NM*SysMgr to gather disk statistics either on all available disks or only on local disks. A disk is considered to be local if the variable sDskRemote for the disk is FALSE(2), indicating that the disk is not remote. If this flag is set to TRUE(1), the disk table (sDskTbl) will only contain data on local disks. If this flag is set to FALSE(2), the disk table (sDskTbl) will contain data on all available disks. Configuration Variable: LocalDisksOnly Set-requests: Take effect on next timer expiration Changes to this value are written to the sCfgFile." DEFVAL { false } ::= { sCfg 59 } sCfgCritDisksOnly OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be used to instruct NM*SysMgr to gather disk statistics either on all available disks or only on disks listed in the Critical Disk file (COMTEK$SYSMGR_CRITDSK). If this flag is set to TRUE(1), the disk table (sDskTbl) will only contain data on disks listed in the Critical Disk file. If this flag is set to FALSE(2), the disk table (tblsDskTbl) will contain data on all available disks.



Configuration Variable: CritDisksOnly Set-requests: Take effect on next timer expiration Changes to this value are written to the sCfgFile." DEFVAL { false } ::= { sCfg 60 } sCfgCpuPersist OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The number of minutes the CPU must remain above the CPU utilization threshold (sCfgCpuLimit) before an excessive CPU utilization trap is sent. The value zero is not permitted for this variable. Configuration Variable: CpuPersist Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 1 } ::= { sCfg 61 } sCfgMWAITLimit OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "If the number of processes in the MWAIT state exceeds this threshold, the sMWAITExcessive trap is sent. Set this threshold to zero to disable the sMWAITExcessive traps. Configuration Variable: MWAITLimit Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { 0 } ::= { sCfg 62 } sCfgQueSummary OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*SysMgr collects summary statistics for queues. Summary statistics include the queue statistics in the following groups: sQueBatch, sQueGeneric, sQuePrinter, sQueServer, sQueSymbiont, and sQueTerminal. Setting this variable to disabled(2) prevents NM*SysMgr collecting these statistics. Enabling this variable on a system that has a large number of queues and queue entries may noticeably increase the CPU used by the NM*SysMgr process. Configuration Variable: QueSummary Set-requests: Take effect immediately Changes to this value are written to the sCfgFile." DEFVAL { disabled } ::= { sCfg 63 } --////////////////////////////////////////////////////////////////////// -- created from nmsysmgr.trp --////////////////////////////////////////////////////////////////////// sColdStart TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent



VARIABLES { sTrapNextSeqNum, sTrapTime, sCfgVersion } DESCRIPTION "A sColdStart trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered." ::= 0 sSwErr TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sSwErrStatus, sSwErrFile, sSwErrLineNum, sSwErrMessage } DESCRIPTION "Software error encountered. This trap indicates that NM*SysMgr was unable to perform some action and explains the error. This trap is typically encountered if sCfgFile, sCfgCritFile, sCfgCritDsk, or sCfgCritQue is set to a new file name which is erroneous or contains invalid data." ::= 1 sHwErr TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sHwErrDeviceName, sHwErrCnt } DESCRIPTION "Hardware error. This trap indicates that the specified device has encountered an error. sHwErr traps may be disabled by setting sCfgHwErrTraps to false(2)." ::= 2 sCpuUsage TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sCpuPercentUsed } DESCRIPTION "Excessive CPU utilization by all processes and interrupts. The threshold for this trap is contained in sCfgCpuLimit. The variable sCfgCpuPersist can be used to control how frequently these traps are sent. The sCfgCpuPersist variable specifies how many minutes the CPU usage must remain above the threshold before this trap is set." ::= 3 sIntUsage TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sIntPercentUsed } DESCRIPTION "Excessive CPU utilization by interrupts during the past one minute interval. The threshold at which this trap is sent is contained in sCfgIntLimit." ::= 4 sDskOpSec TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sDskName, sDskOps, sDskLogVolName } DESCRIPTION "Excessive average disk operations per second. The threshold at which this trap is sent is contained in either the critical disk file (sDskTrapOpSec) or in configuration file variable sCfgDskOps. sCfgDskTimer controls how often this data is computed and how often this trap may be sent." ::= 5 sDskFull TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sDskName, sDskUsedPercent, sDskFreeBlocks, sDskLogVolName } DESCRIPTION "Disk usage has reached or exceeded the critical threshold. The threshold at which this trap is sent is contained in one of the following: sDskTrapPercent (from the critical disk file)



sDskTrapBlocks (from the critical disk file) sCfgDskLimit sCfgDskMinFreeBlks If this disk has an entry in the critical disk file which specifies the threshold either in percent full (sDskTrapPercent) or in minimum disk blocks free (sDskTrapBlocks), that value is used to determine when sDskFull and sDskFullClear traps are sent. For disks which are not contained in the critical disk file, these traps are controlled by either the value contained in sCfgDskLimit (percent full) or sCfgDskMinFreeBlks (minimum number of free blocks). Only one of the two values sCfgDskLimit and sCfgDskMinFreeBlks is in force (i.e, nonzero) at any given time. If both values are zero, disk full and clear traps for disks not contained in the critical disk table are disabled. sCfgDskTimer controls how often this data is computed. sCfgDskAlarm controls how often this trap is repeated once the threshold has been reached." ::= 6 sDskFullClear TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sDskName, sDskUsedPercent, sDskFreeBlocks, sDskLogVolName } DESCRIPTION "Disk usage that had reached or exceeded the critical threshold has now gone below that threshold. This indicates that the condition that was reported by the sDskFull trap has been resolved." ::= 7 sSwpFull TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sSyiSwpUsedPercent, sSyiSwpFree } DESCRIPTION "Swap file usage has reached or exceeded the critical threshold. The threshold at which this trap is sent is contained in sCfgSwpLimit. sCfgSysInfoTimer controls how often this data is computed. sCfgDskAlarm controls how often this trap is repeated once the threshold has been reached." ::= 8 sSwpFullClear TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sSyiSwpUsedPercent, sSyiSwpFree } DESCRIPTION "Swap file usage that had reached or exceeded the critical threshold has now gone below that threshold. This indicates that the condition that was reported by the sSwpFull trap has been resolved." ::= 9 sPgFull TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sSyiPgUsedPercent, sSyiPgFree } DESCRIPTION "Page file usage has reached or exceeded the critical threshold. The threshold at which this trap is sent is contained in sCfgPgLimit. sCfgSysInfoTimer controls how often this data is computed. sCfgDskAlarm controls how often this trap is repeated once the threshold has been reached." ::= 10 sPgFullClear TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sSyiPgUsedPercent,



sSyiPgFree } DESCRIPTION "Page file usage that had reached or exceeded the critical threshold has now gone below that threshold. This indicates that the condition that was reported by the sPgFull trap has been resolved." ::= 11 sCriticalProcessMissing TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sCritName, sCritReqCnt, sCritCurCnt } DESCRIPTION "Too few instances of processes by this name. This indicates that the current number of processes running (sCritCurCnt) with the specified name is less than the required number (sCritReqCnt). sCfgCritTimer controls how often critical process checking is performed. This trap will be repeated with a frequency specified by sCfgCritAlarm until the situation is resolved." ::= 12 sOpcomMessage TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sOpcomOne, sOpcomTwo, sOpcomThree, sOpcomFour, sOpcomFive, sOpcomSix, sOpcomSeven } DESCRIPTION "New message in operator log. This message contains the text of a opcom message. The opcom header is stripped from the message before it is sent." ::= 13 sTermProc TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime } DESCRIPTION "NM*SysMgr Subagent process termination." ::= 14 sDskStat TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sDskName, sDskStatus, sDskLogVolName } DESCRIPTION "Disk device status has transitioned into one of the following states: POWER (power failed while unit was busy), TIMOUT (unit timed out), or MNTVERIP (mount verification in progress). The variable sDskStatus identifies the new status of the disk." ::= 15 sWarmStart TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime } DESCRIPTION "The NM*SysMgr Subagent process has been reinitialized." ::= 16 sShdFailStatus TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sShdName, sShdFail } DESCRIPTION "Shadow set member failure status has changed. Disk has transitioned either into or out of a shadow set failure as indicated by sShdFail." ::= 17 sShdCopyStatus TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sShdName, sShdCopy } DESCRIPTION



"Shadow set member catch-up copy status has changed. Disk has either started or completed catch-up copying as indicated by sShdCopy." ::= 18 sShdMergeStatus TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sShdName, sShdMerge } DESCRIPTION "Shadow set member merge copy status has changed. Disk has either started or completed merge copying as indicated by sShdMerge." ::= 19 sQueStatusChange TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sQName, sQStatus } DESCRIPTION "Status of monitored queue has transitioned into or out of one of the following states as indicated by the following sQStatus bit settings: paused (bit 4 set), stalled (bit 10 set), starting (bit 11 set), stopped (bit 12 set), or disabled (bit 19 set)." ::= 20 sQEntryStatusChange TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sQEntryNum, sQEntryJobname, sQEntryJobStatus } DESCRIPTION "Status of specified queue entry has transitioned into or out of one of the following states as indicated by the sQEntryJobStatus bit settings: aborting (bit 0 set), refused (bit 4 set), or stalled (bit 13 set)." ::= 21 sProcStatusChange TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sPsPID, sPsProcName, sPsState, sPsRWState } DESCRIPTION "Status of this process has transitioned into or out of MWAIT(2) state as indicated by the sPsState value. The cause of the MWAIT state is contained in the sPsRWState variable. If the process has transitioned out of the MWAIT state, the value of sPsRWState will be NULL." ::= 22 sMemFull TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sSyiMemUsed, sSyiMemFreePg } DESCRIPTION "Physical memory usage has reached or exceeded the critical threshold. The threshold at which this trap is sent is contained in sCfgMemLimit. sCfgSysInfoTimer controls how often this data is computed. sCfgDskAlarm controls how often this trap is repeated once the threshold has been reached." ::= 23 sMemClear TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sSyiMemUsed, sSyiMemFreePg } DESCRIPTION "Physical memory usage that had reached or exceeded the critical threshold has now gone below that threshold. This indicates that the condition that was reported by the sMemFull trap has been resolved." ::= 24 sCOMQue TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sPsCOMQueue }



DESCRIPTION "Number of processes in COM state has reached or exceeded the critical threshold. The threshold at which this trap is sent is contained in sCfgCOMQueueLimit. sCfgPsTimer controls how often this data is computed." ::= 25 sCOMOQue TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sPsCOMOQueue } DESCRIPTION "Number of processes in COMO state has reached or exceeded the critical threshold. The threshold at which this trap is sent is contained in sCfgCOMOQueueLimit. sCfgPsTimer controls how often this data is computed." ::= 26 sCritProcClear TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sCritName, sCritReqCnt, sCritCurCnt } DESCRIPTION "Critical Process Missing condition (indicated by the sCriticalProcessMissing Trap) has been cleared. This means that the current number of processes running (sCritCurCnt) with the specified name is equal or greater than the required number (sCritReqCnt). sCfgCritTimer controls how often critical process checking is performed." ::= 27 sDskIOQLen TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sDskName, sDskQueueLengthDelta, sDskQueueLength } DESCRIPTION "Disk I/O queue length has reached or exceeded the critical threshold specififed in the Critical Disk file." ::= 28 sCritJobMissing TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sQEntryJobname, sQName } DESCRIPTION "User-specified critical job is missing from the specified queue." ::= 29 sMWAITExcessive TRAP-TYPE ENTERPRISE comtekVmsNMSysMgrSubagent VARIABLES { sTrapNextSeqNum, sTrapTime, sPsMWAITCount } DESCRIPTION "The number of processes in MWAIT state has exceeded the threshold specified by sCfgMWAITLimit." ::= 30 --////////////////////////////////////////////////////////////////////// -- created from nmtrpmgr.mib --////////////////////////////////////////////////////////////////////// tTrap OBJECT IDENTIFIER ::= { comtekVmsNMTrpMgrMib 1 } tSwErrInfo OBJECT IDENTIFIER ::= { comtekVmsNMTrpMgrMib 2 } tCfg OBJECT IDENTIFIER ::= { comtekVmsNMTrpMgrMib 3 } -- The NM*TrpMgr Subagent process maintains an internal trap table -- containing the latest traps that have been sent by the subagent. -- The number of traps that are retained in the internal trap table -- is controlled by the tCfgTrapTblSize variable. Each trap that is -- sent by NM*TrpMgr includes a trap sequence number and a timestamp -- as well as any trap specific data. The trap sequence number may -- be used to request that a trap be resent to the manager.



-- -- The number of traps per second that may be sent is governed by the -- tCfgMaxTrapSec variable. tTrapLastSeqNumSent identifies the -- sequence number of the last trap that was actually sent, if no -- backlog of traps exists, this number will be one less than -- tTrapNextSeqNum. If a backlog exists due to throttling, then -- the size of the backlog may be determined by comparing these -- numbers. If the size of the backlog exceeds the size of the -- trap table (as set by tCfgTrapTblSize), the backlogged traps -- will be lost as they are overwritten by new traps, the number -- of traps that have been lost is contained in tTrapLostCount. tTrapNextSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The next sequence number in the trap table. When this variable is sent as part of a trap, it identifies the sequence number assigned to that trap. This is a 32-bit value and will wrap after 4294967295." ::= { tTrap 1 } tTrapTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "tCfgUpTime when the trap was created." ::= { tTrap 2 } tTrapResendSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "Sequence number of a trap message to be resent to the manager. Setting this variable to a trap sequence number causes the specified trap message to be resent. If the set-request contains a sequence number that is not available (the number of items retained in the trap table is dependent on the value of tCfgTrapTblSize), an error indicator will be returned." ::= { tTrap 3 } -- User trap messages may be used to send textual data to the SNMP manager. -- User traps can accomodate long messages - up to 1785 characters. Due -- to restrictions in SNMP, a single variable may only contain 255 characters -- so user trap messages which contain more than 255 characters are broken -- into 255 character chunks. See variables prefixed tSev below for severity -- coded user traps. tTrapUserMsgOne OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 1 of user trap data. If the user message is longer than 255 characters, the remainder will be sent in tTrapUserMsgTwo, tTrapUserMsgThree, tTrapUserMsgFour, tTrapUserMsgFive, and tTrapUserMsgSix, and tTrapUserMsgSeven as appropriate." ::= { tTrap 4 } tTrapUserMsgTwo OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 2 of user trap data."



::= { tTrap 5 } tTrapUserMsgThree OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 3 of user trap data." ::= { tTrap 6 } tTrapUserMsgFour OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 4 of user trap data." ::= { tTrap 7 } tTrapUserMsgFive OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 5 of user trap data." ::= { tTrap 8 } tTrapLastSeqNumSent OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Sequence number of the last trap sent. This value may be compared to tTrapNextSeqNum to determine if a backlog of traps exists. If this value is one less than tTrapNextSeqNum, then no backlog exists. A backlog of traps may exist if more traps are generated per second than may be sent (as specified by the variable tCfgMaxTrapSec)." ::= { tTrap 9 } tTrapLostCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates the number of traps that have been lost. A trap is considered to be lost if it is overwritten in the internal trap table before it is sent to the NMS. This may occur if the trap table is not large enough (see tCfgTrapTblSize) to hold all of unsent traps. How quickly traps are sent to the NMS is governed by the tCfgMaxTrapSec variable. To prevent trap loss, set these two variables so that the trap backlog does not overflow the trap table and so that traps do not flood the network." ::= { tTrap 10 } tTrapUserMsgSix OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 6 of user trap data." ::= { tTrap 11 } tTrapUserMsgSeven OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 7 of user trap data." ::= { tTrap 12 }



-- Below are variables relating to the severity coded user traps. -- Each severity coded trap contains two parts: facility/severity/ -- identifier string and the message text. NM*TrpMgr parses each -- message placed in the severity coded mailboxes. If the -- facility/severity/identifer string is not found at the beginning -- of the message, then the this variable will be empty in the -- severity coded trap message. tSev OBJECT IDENTIFIER ::= { tTrap 13 } tSevSuccessCode OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "User trap message identifier with a severity of Success." ::= { tSev 1 } tSevSuccessMsg OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "User trap message text with a severity of Success." ::= { tSev 2 } tSevInfoCode OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "User trap message identifier with a severity of Informational." ::= { tSev 3 } tSevInfoMsg OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "User trap message text with a severity of Informational." ::= { tSev 4 } tSevWarningCode OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "User trap message identifier with a severity of Warning." ::= { tSev 5 } tSevWarningMsg OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "User trap message text with a severity of Warning." ::= { tSev 6 } tSevErrorCode OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "User trap message identifier with a severity of Error." ::= { tSev 7 } tSevErrorMsg OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only



STATUS mandatory DESCRIPTION "User trap message text with a severity of Error." ::= { tSev 8 } tSevFatalCode OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "User trap message identifier with a severity of Fatal." ::= { tSev 9 } tSevFatalMsg OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "User trap message text with a severity of Fatal." ::= { tSev 10 } -- When a software error is encountered, a tSwErr trap is generated containing -- the following software error description items. Invalid sets of the -- tCfgFile variable will cause a tSwErr trap to be generated to explain the -- error. tSwErrStatus OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The latest software status code." ::= { tSwErrInfo 1 } tSwErrFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The file name of the software element which generated the latest software status code." ::= { tSwErrInfo 2 } tSwErrLineNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The line number in the file which generated the latest software status code." ::= { tSwErrInfo 3 } tSwErrLastTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "tCfgUpTime when the most recent software status code was generated." ::= { tSwErrInfo 4 } tSwErrMessage OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Description of the latest software error." ::= { tSwErrInfo 5 } -- Configuration parameters which are read from disk and may be



-- viewed/changed by the network manager. All changes to these -- parameters are written to the disk file. tCfgFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file currently being used for NM*TrpMgr initialization parameters. This file is identified by the logical name COMTEK$TRPMGR_CONFIG. Changing this variable redefines the COMTEK$TRPMGR_CONFIG logical name. NM*TrpMgr must be reinitialized (by setting the variable tCfgReinitSubagent to true) before the new configuration file is used. If a set-request is performed on this variable and the specified file name does not exist, is not accessible, or contains invalid data, the file name is not changed, an error is returned, and a tSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (tCfgReinitSubagent) NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures." ::= { tCfg 1 } tCfgLogFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Name of the log file currently being used by NM*TrpMgr. If this process is run interactively, this variable will have the value SYS$OUTPUT: (standard output)." ::= { tCfg 2 } tCfgReinitSubagent OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be set to force the NM*TrpMgr Subagent to reinitialize. Reinitialization involves resetting the process configuration using the parameters contained in the tCfgFile and sending the tWarmStart trap." DEFVAL { false } ::= { tCfg 3 } tCfgTraps OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if any trap messages are sent to the NM*Master Agent. Setting this variable to disabled(2) disables all traps from being sent. Configuration Variable: Traps Set-requests: Take effect immediately Changes to this value are written to the tCfgFile." DEFVAL { enabled } ::= { tCfg 4 } tCfgTrapTblSize OBJECT-TYPE SYNTAX INTEGER (10..5000) ACCESS read-write STATUS mandatory DESCRIPTION



"The maximum number of traps to be retained. Traps that are retained may be resent (see tTrapResendSeqNum) unless too many subsequent traps have been generated. This variable controls how many traps are retained in NM*TrpMgr's internal trap table. Configuration Variable: TrapTableSize Set-Requests: Take effect immediately Changes to this value are written to the tCfgFile." DEFVAL { 100 } ::= { tCfg 5 } tCfgHostName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The name of the host that the subagent is communicating with. This is the host name where the NM*Master Agent resides. This variable is not currently used. Configuration Variable: Host" DEFVAL { "localhost" } ::= { tCfg 6 } tCfgTimeout OBJECT-TYPE SYNTAX INTEGER (0..3600) ACCESS read-only STATUS mandatory DESCRIPTION "This variable identifies the time-out value that is to be used by the subagent during subtree registration. If this value is set to zero, the default value (saDefaultTimeout) contained in the NM*Master Agent will be used. If the value specified exceeds the current maximum that the NM*Master Agent will permit (saMaxTimeout), the maximum value will be used. This value is specified in seconds. Configuration Variable: Timeout" DEFVAL { 0 } ::= { tCfg 7 } tCfgControlTermProc OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Flag which may be used to disable process termination by the tCfgTermProc variable. Setting this variable to enabled(1) allows the tCfgTermProc variable to be set to true(1) to terminate the NM*TrpMgr process. Setting this variable to disabled(2) prevents the tCfgTermProc variable from being set. Configuration Variable: ControlTermProc" DEFVAL { disabled } ::= { tCfg 8 } tCfgTermProc OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be used to shutdown the NM*TrpMgr process. Setting this flag to true causes the NM*TrpMgr process to respond to the set-request, send the tTermProc trap, close the connection to the NM*Master Agent, and shutdown. If the tCfgControlTermProc flag state is disabled(2), the tCfgTermProc variable can not be set. Set-requests: Take effect immediately if



tCfgControlTermProc is enabled(2)" DEFVAL { false } ::= { tCfg 9 } tCfgVersion OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Current version of the NM*TrpMgr Subagent software." ::= { tCfg 10 } tCfgUpTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time." ::= { tCfg 11 } tCfgMaxTrapSec OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "This value specifies the maximum number of traps per second that may be sent. A value of zero disables trap throttling, allowing all traps to be sent as they are generated. It is recommended that this value and tCfgTrapTblSize be tuned to each operational environment. Configuration Variable: MaxTrapSec Set-requests: Take effect immediately. Changes to this value are written to the tCfgFile." DEFVAL { 0 } ::= { tCfg 12 } --////////////////////////////////////////////////////////////////////// -- created from nmtrpmgr.trp --////////////////////////////////////////////////////////////////////// tColdStart TRAP-TYPE ENTERPRISE comtekVmsNMTrpMgrSubagent VARIABLES { tTrapNextSeqNum, tTrapTime, tCfgVersion } DESCRIPTION "A tColdStart trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered." ::= 0 tSwErr TRAP-TYPE ENTERPRISE comtekVmsNMTrpMgrSubagent VARIABLES { tTrapNextSeqNum, tTrapTime, tSwErrStatus, tSwErrFile, tSwErrLineNum, tSwErrMessage } DESCRIPTION "Software error encountered. This trap indicates that NM*TrpMgr was unable to perform some action and explains the error. This trap is typically encountered if tCfgFile is set to a new file name which is erroneous or contains invalid data." ::= 1 tUsrTrp TRAP-TYPE ENTERPRISE comtekVmsNMTrpMgrSubagent VARIABLES { tTrapNextSeqNum, tTrapTime, tTrapUserMsgOne, tTrapUserMsgTwo, tTrapUserMsgThree, tTrapUserMsgFour, tTrapUserMsgFive, tTrapUserMsgSix, tTrapUserMsgSeven } DESCRIPTION "Message from user process. This trap contains the data that was read from the COMTEK$USER_TRAP mailbox." ::= 2



tTermProc TRAP-TYPE ENTERPRISE comtekVmsNMTrpMgrSubagent VARIABLES { tTrapNextSeqNum, tTrapTime } DESCRIPTION "NM*TrpMgr Subagent process termination." ::= 3 tWarmStart TRAP-TYPE ENTERPRISE comtekVmsNMTrpMgrSubagent VARIABLES { tTrapNextSeqNum, tTrapTime } DESCRIPTION "The NM*TrpMgr Subagent process has been reinitialized." ::= 4 tSevSuccess TRAP-TYPE ENTERPRISE comtekVmsNMTrpMgrSubagent VARIABLES { tTrapNextSeqNum, tTrapTime, tSevSuccessCode, tSevSuccessMsg } DESCRIPTION "Severity Success traps. This trap contains data that was read from the COMTEK$SUCCESS_TRAP mailbox." ::= 5 tSevInformational TRAP-TYPE ENTERPRISE comtekVmsNMTrpMgrSubagent VARIABLES { tTrapNextSeqNum, tTrapTime, tSevInfoCode, tSevInfoMsg } DESCRIPTION "Severity Informational traps. This trap contains data that was read from the COMTEK$INFORMATIONAL_TRAP mailbox." ::= 6 tSevWarning TRAP-TYPE ENTERPRISE comtekVmsNMTrpMgrSubagent VARIABLES { tTrapNextSeqNum, tTrapTime, tSevWarningCode, tSevWarningMsg } DESCRIPTION "Severity Warning traps. This trap contains data that was read from the COMTEK$WARNING_TRAP mailbox." ::= 7 tSevError TRAP-TYPE ENTERPRISE comtekVmsNMTrpMgrSubagent VARIABLES { tTrapNextSeqNum, tTrapTime, tSevErrorCode, tSevErrorMsg } DESCRIPTION "Severity Error traps. This trap contains data that was read from the COMTEK$ERROR_TRAP mailbox." ::= 8 tSevFatal TRAP-TYPE ENTERPRISE comtekVmsNMTrpMgrSubagent VARIABLES { tTrapNextSeqNum, tTrapTime, tSevFatalCode, tSevFatalMsg } DESCRIPTION "Severity Fatal traps. This trap contains data that was read from the COMTEK$FATAL_TRAP mailbox." ::= 9 --////////////////////////////////////////////////////////////////////// -- created from nmconsole.mib --////////////////////////////////////////////////////////////////////// cConsole OBJECT IDENTIFIER ::= { comtekVmsNMConsoleMib 1} cTrap OBJECT IDENTIFIER ::= { comtekVmsNMConsoleMib 2 } cSwErrInfo OBJECT IDENTIFIER ::= { comtekVmsNMConsoleMib 3 } cCfg OBJECT IDENTIFIER ::= { comtekVmsNMConsoleMib 4 } -- cConsoleCmd OBJECT-TYPE



SYNTAX DisplayString ACCESS read-write STATUS mandatory DESCRIPTION "A command to be executed by the NM*Console Subagent. The format of a command is: tag <command>qualifiers Where tag is label to be associated with the command, <command> is any command that may be entered at the DCL prompt (including any parameters or qualifiers) and qualifiers is any qualifiers which are to be placed on the detached process that is started to execute the command. The following are valid commands: abcd <dir sys$sysdevice:[comtek$snmp]*.com/col=1> test01 <stop/id=1FE>/priv=world " ::= { cConsole 1 } cConsoleTag OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Tag that accompanied a command. This tag is used in each cConsoleResult trap message to associate the command results with the command." ::= { cConsole 2 } cConsoleOutput OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Output from a cConsoleCmd command." ::= { cConsole 3 } cConsoleCurrent OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The number of remote console commands currently active." ::= { cConsole 4 } -- The NM*Console Subagent process maintains an internal trap table -- containing the latest traps that have been sent by the subagent. -- The number of traps that are retained in the internal trap table -- is controlled by the cCfgTrapTblSize variable. Each trap that is -- sent by NM*Console includes a trap sequence number and a timestamp -- as well as any trap specific data. The trap sequence number may -- be used to request that a trap be resent to the manager. -- -- The number of traps per second that may be sent is governed by the -- cCfgMaxTrapSec variable. cTrapLastSeqNumSent identifies the -- sequence number of the last trap that was actually sent, if no -- backlog of traps exists, this number will be one less than -- cTrapNextSeqNum. If a backlog exists due to throttling, then -- the size of the backlog may be determined by comparing these -- numbers. If the size of the backlog exceeds the size of the -- trap table (as set by cCfgTrapTblSize), the backlogged traps -- will be lost as they are overwritten by new traps, the number -- of traps that have been lost is contained in cTrapLostCount. cTrapNextSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory



DESCRIPTION "The next sequence number in the trap table. When this variable is sent as part of a trap, it identifies the sequence number assigned to that trap. This is a 32-bit value and will wrap after 4294967295." ::= { cTrap 1 } cTrapTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "cCfgUpTime when the trap was generated." ::= { cTrap 2 } cTrapResendSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "Sequence number of a trap message to be resent to the manager. Setting this variable to a trap sequence number causes the specified trap message to be resent. If the set-request contains a sequence number that is not available (the number of items retained in the trap table is dependent on the value of cCfgTrapTblSize), an error indicator will be returned." ::= { cTrap 3 } cTrapLastSeqNumSent OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Sequence number of the last trap sent. This value may be compared to cTrapNextSeqNum to determine if a backlog of traps exists. If this value is one less than cTrapNextSeqNum, then no backlog exists. A backlog of traps may exist if more traps are generated per second than may be sent (as specified by the variable cCfgMaxTrapSec)." ::= { cTrap 4 } cTrapLostCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates the number of traps that have been lost. A trap is considered to be lost if it is overwritten in the internal trap table before it is sent to the NMS. This may occur if the trap table is not large enough (see cCfgTrapTblSize) to hold all of unsent traps. How quickly traps are sent to the NMS is governed by the cCfgMaxTrapSec variable. To prevent trap loss, set these two variables so that the trap backlog does not overflow the trap table and so that traps do not flood the network." ::= { cTrap 5 } -- When a software error is encountered, a cSwErr trap is generated containing -- the following software error description items. Invalid sets of the -- cCfgFile variable will cause a cSwErr trap to be generated to explain the -- error. cSwErrStatus OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The latest software status code." ::= { cSwErrInfo 1 }



cSwErrFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The file name of the software element which generated the latest software status code." ::= { cSwErrInfo 2 } cSwErrLineNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The line number in the file which generated the latest software status code." ::= { cSwErrInfo 3 } cSwErrLastTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "cCfgUpTime when the most recent software status code was generated." ::= { cSwErrInfo 4 } cSwErrMessage OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Description of the latest software error." ::= { cSwErrInfo 5 } -- Configuration parameters which are read from disk and may be -- viewed/changed by the network manager. All changes to these -- parameters are written to the disk file. cCfgFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file currently being used for NM*Console initialization parameters. This file is identified by the logical name COMTEK$CONSOLE_CONFIG. Changing this variable redefines the COMTEK$CONSOLE_CONFIG logical name. NM*Console must be reinitialized (by setting the variable cCfgReinitSubagent to true) before the new configuration file is used. If a set-request is performed on this variable and the specified file name does not exist, is not accessible, or contains invalid data, the file name is not changed, an error is returned, and a cSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (cCfgReinitSubagent) NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures." ::= { cCfg 1 } cCfgLogFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Name of the log file currently being used by NM*Console. If this process is run interactively, this variable will



have the value SYS$OUTPUT: (standard output)." ::= { cCfg 2 } cCfgReinitSubagent OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be set to force the NM*Console Subagent to reinitialize. Reinitialization involves resetting the process configuration using the parameters contained in the cCfgFile and sending the cWarmStart trap." DEFVAL { false } ::= { cCfg 3 } cCfgTraps OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if any trap messages are sent to the NM*Master Agent. Setting this variable to disabled(2) disables all traps from being sent. Configuration Variable: Traps Set-requests: Take effect immediately Changes to this value are written to the cCfgFile." DEFVAL { enabled } ::= { cCfg 4 } cCfgTrapTblSize OBJECT-TYPE SYNTAX INTEGER (10..5000) ACCESS read-write STATUS mandatory DESCRIPTION "The maximum number of traps to be retained. Traps are retained for two reasons: to allow traps to be throttled to prevent flooding the network and to allow traps to be resent (see cTrapResendSeqNum). If this value is not sufficiently large, traps that are backlogged due to throttling may be lost. This value should be tuned in conjunction with cCfgMaxTrapSec. This variable controls how many traps are retained in NM*Console's internal trap table. Configuration Variable: TrapTableSize Set-Requests: Take effect immediately Changes to this value are written to the cCfgFile." DEFVAL { 100 } ::= { cCfg 5 } cCfgHostName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The name of the host that the subagent is communicating with. This is the host name where the NM*Master Agent resides. This variable is not currently used. Configuration Variable: Host" DEFVAL { "localhost" } ::= { cCfg 6 } cCfgTimeout OBJECT-TYPE SYNTAX INTEGER (0..3600) ACCESS read-only STATUS mandatory DESCRIPTION "This variable identifies the time-out value that is to be



used by the subagent during subtree registration. If this value is set to zero, the default value (saDefaultTimeout) contained in the NM*Master Agent will be used. If the value specified exceeds the current maximum that the NM*Master Agent will permit (saMaxTimeout), the maximum value will be used. This value is specified in seconds. Configuration Variable: Timeout" DEFVAL { 0 } ::= { cCfg 7 } cCfgMaxConsoleCmds OBJECT-TYPE SYNTAX INTEGER (1..100) ACCESS read-write STATUS mandatory DESCRIPTION "This variable indicates the maximum number of remote console commands that can be active at one time. Configuration Variable: MaxCommands Set-requests: Take effect at next process start-up Changes to this value are written to the cCfgFile." DEFVAL { 5 } ::= { cCfg 8 } cCfgControlTermProc OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Flag which may be used to disable process termination by the cCfgTermProc variable. Setting this variable to enabled(1) allows the cCfgTermProc variable to be set to true(1) to terminate the NM*Console process. Setting this variable to disabled(2) prevents the cCfgTermProc variable from being set. Configuration Variable: ControlTermProc" DEFVAL { disabled } ::= { cCfg 9 } cCfgTermProc OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be used to shutdown the NM*Console process. Setting this flag to true causes the NM*Console process to respond to the set-request, send the cTermProc trap, close the connection to the NM*Master Agent, and shutdown. If the cCfgControlTermProc flag state is disabled(2), the cCfgTermProc variable can not be set. Set-requests: Take effect immediately if cCfgControlTermProc is enabled(2)" DEFVAL { false } ::= { cCfg 10 } cCfgVersion OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Current version of the NM*Console Subagent software." ::= { cCfg 11 } cCfgUpTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory



DESCRIPTION "Subagent up time." ::= { cCfg 12 } cCfgMaxTrapSec OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "This value specifies the maximum number of traps per second that may be sent. A value of zero disables trap throttling, allowing all traps to be sent as they are generated. It is recommended that this value and cCfgTrapTblSize be tuned to each operational environment. Configuration Variable: MaxTrapSec Set-requests: Take effect immediately. Changes to this value are written to the cCfgFile." DEFVAL { 0 } ::= { cCfg 13 } --////////////////////////////////////////////////////////////////////// -- created from nmconsole.trp --////////////////////////////////////////////////////////////////////// cColdStart TRAP-TYPE ENTERPRISE comtekVmsNMConsoleSubagent VARIABLES { cTrapNextSeqNum, cTrapTime, cCfgVersion } DESCRIPTION "A cColdStart trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered." ::= 0 cWarmStart TRAP-TYPE ENTERPRISE comtekVmsNMConsoleSubagent VARIABLES { cTrapNextSeqNum, cTrapTime } DESCRIPTION "The NM*Console Subagent process has been reinitialized." ::= 1 cSwErr TRAP-TYPE ENTERPRISE comtekVmsNMConsoleSubagent VARIABLES { cTrapNextSeqNum, cTrapTime, cSwErrStatus, cSwErrFile, cSwErrLineNum, cSwErrMessage } DESCRIPTION "Software error encountered. This trap indicates that NM*Console was unable to perform some action and explains the error. This trap is typically encountered if cCfgFile is set to a new file name which is erroneous or contains invalid data." ::= 2 cTermProc TRAP-TYPE ENTERPRISE comtekVmsNMConsoleSubagent VARIABLES { cTrapNextSeqNum, cTrapTime } DESCRIPTION "NM*Console Subagent process termination." ::= 3 cConsoleResult TRAP-TYPE ENTERPRISE comtekVmsNMConsoleSubagent VARIABLES { cTrapNextSeqNum, cTrapTime, cConsoleTag, cConsoleOutput } DESCRIPTION "NM*Console command result. This trap contains a line from the output file generated from executing a remote console command. The cConsoleTag field identifies the tag that accompanied the command." ::= 4 --////////////////////////////////////////////////////////////////////// -- created from nmvmsmon.mib



--////////////////////////////////////////////////////////////////////// -- This MIB is designed to closely resemble the VMS MONITOR Utility. -- This MIB contains the following 12 groups which correspond to the -- VMS MONITOR Utility classes by the same name. -- 1. modes (by CPU and total for all CPUs) -- 2. file_system_cache -- 3. fcp -- 4. io -- 5. page -- 6. decnet -- 7. states -- 8. cluster -- 9. mscp_server -- 10. lock -- 11. dlock -- 12. system -- 13. rlock -- 14. timer -- -- Many of the above variables are counters which reflect the number -- of operations since the system was booted. The following additional -- variables are provided to assist in tracking how much these -- counters have changed during the most recent update interval. All -- of the variables which track these delta values are contained in -- the following groups: -- 1. delta modes (by CPU and total for all CPUs) -- 2. delta file_system_cache -- 3. delta fcp -- 4. delta io -- 5. delta page -- 6. delta decnet -- 8. delta cluster -- 9. delta mscp_server -- 10. delta lock -- 11. delta dlock -- 12. delta system -- All Delta variables are include in this folllowing group vmsDeltas OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 20 } -- MONITOR MODES vmsModes OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 1 } vmsModeUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when CPU mode statistics were last gathered." ::= { vmsModes 1 } vmsModeUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often CPU mode statistics are to be gathered. A value of 0 disables gathering of CPU mode statistics. This value is expressed in minutes." DEFVAL { 1 } ::= { vmsModes 2 } vmsModeCpuCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of entries in the CPU Mode table (i.e., the number of CPUs being monitored)."



::= { vmsModes 3 } vmsModeTable OBJECT-TYPE SYNTAX SEQUENCE OF VmsModeTableEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table description. " ::= { vmsModes 4 } vmsModeTableEntry OBJECT-TYPE SYNTAX VmsModeTableEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Row in table description. " INDEX { vmsModeCpuId } ::= { vmsModeTable 1 } VmsModeTableEntry ::= SEQUENCE { vmsModeCpuId INTEGER, vmsModeKernel Counter, vmsModeExec Counter, vmsModeSuper Counter, vmsModeUser Counter, vmsModeInter Counter, vmsModeMPSync Counter, vmsModeCompat Counter, vmsModeIdle Counter } vmsModeCpuId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "CPU ID for mode data in this row in the mode table." ::= { vmsModeTableEntry 1 } vmsModeKernel OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU has spent in kernel mode (excluding interrupt stack time) since the system was booted." ::= { vmsModeTableEntry 2 } vmsModeExec OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU has spent in Executive mode since the system was booted." ::= { vmsModeTableEntry 3 } vmsModeSuper OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU has spent in Supervisor mode since the system was booted." ::= { vmsModeTableEntry 4 } vmsModeUser OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION



"Number of clock ticks this CPU has spent in User mode (excluding compatibility-mode time) since the system was booted." ::= { vmsModeTableEntry 5 } vmsModeInter OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks (10-millisecond units) this CPU has spent on the Interrupt stack since the system was booted." ::= { vmsModeTableEntry 6 } vmsModeMPSync OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU has spent synchronizing multiple CPUs since the system was booted." ::= { vmsModeTableEntry 7 } vmsModeCompat OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU has spent in Compatibility mode since the system was booted." ::= { vmsModeTableEntry 8 } vmsModeIdle OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU has spent executing the NULL process since the system was booted." ::= { vmsModeTableEntry 9 } vmsTotalModes OBJECT IDENTIFIER ::= { vmsModes 5 } vmsTotalKernel OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total number of clock ticks all CPUs have spent in kernel mode (excluding interrupt stack time) since the system was booted." ::= { vmsTotalModes 1 } vmsTotalExec OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs have spent in Executive mode since the system was booted." ::= { vmsTotalModes 2 } vmsTotalSuper OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs have spent in Supervisor mode since the system was booted." ::= { vmsTotalModes 3 } vmsTotalUser OBJECT-TYPE SYNTAX Counter



ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs have spent in User mode (excluding compatibility-mode time) since the system was booted." ::= { vmsTotalModes 4 } vmsTotalInter OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks (10-millisecond units) all CPUs have spent on the Interrupt stack since the system was booted." ::= { vmsTotalModes 5 } vmsTotalMPSync OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs have spent synchronizing multiple CPUs since the system was booted." ::= { vmsTotalModes 6 } vmsTotalComp OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs have spent in Compatibility mode since the system was booted." ::= { vmsTotalModes 7 } vmsTotalIdle OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs have spent executing the NULL process since the system was booted." ::= { vmsTotalModes 8 } -- MONITOR FILE_SYSTEM_CACHE vmsFile OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 2 } vmsFileUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when File System statistics were last updated. " ::= { vmsFile 1 } vmsFileUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often File System statistics are to be gathered. A value of 0 disables gathering of File System statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsFile 2 } vmsFileDirFCBHit OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION



"Count of hits on directory FCB cache." ::= { vmsFile 3 } vmsFileDirFCBAttempt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of attempts on directory FCB cache." ::= { vmsFile 4 } vmsFileDirDataHit OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of hits on directory data cache." ::= { vmsFile 5 } vmsFileDirDataAttempt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of attempts on directory data cache." ::= { vmsFile 6 } vmsFileFileHdrHit OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of hits on file header cache." ::= { vmsFile 7 } vmsFileFileHdrAttempt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of attempts on file header cache." ::= { vmsFile 8 } vmsFileFileIdHit OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of hits on file ID cache." ::= { vmsFile 9 } vmsFileFileIdAttempt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of attempts on file ID cache." ::= { vmsFile 10 } vmsFileExtentHit OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of hits on extent cache." ::= { vmsFile 11 } vmsFileExtentAttempt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory



DESCRIPTION "Count of attempts on extent cache." ::= { vmsFile 12 } vmsFileQuotaHit OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of hits on quota cache." ::= { vmsFile 13 } vmsFileQuotaAttempt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of attempts on quota cache." ::= { vmsFile 14 } vmsFileBitmapHit OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of hits on storage bitmap cache." ::= { vmsFile 15 } vmsFileBitmapAttempt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of attempts on storage bitmap cache." ::= { vmsFile 16 } -- MONITOR FCP vmsFcp OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 3 } vmsFcpUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when FCP statistics were last updated. " ::= { vmsFcp 1 } vmsFcpUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often FCP statistics are to be gathered. A value of 0 disables gathering of File System statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsFcp 2 } vmsFcpFCPCall OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of QIO requests received by the file system." ::= { vmsFcp 3 } vmsFcpAllocation OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory



DESCRIPTION "Count of QIO requests that caused allocation of disk space." ::= { vmsFcp 4 } vmsFcpCreate OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of new files created." ::= { vmsFcp 5 } vmsFcpDiskRead OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of read I/O operations from the disk by the file system." ::= { vmsFcp 6 } vmsFcpDiskWrite OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of write I/O operations to the disk by the file system." ::= { vmsFcp 7 } vmsFcpVolumeLockWait OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of times a wait state was entered by the XQP due to volume lock contention." ::= { vmsFcp 8 } vmsFcpCPUTick OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of clock ticks (10-millisecond units) of CPU time used by the file system." ::= { vmsFcp 9 } vmsFcpPageFault OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of page faults for the file system." ::= { vmsFcp 10 } vmsFcpWindowTurn OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of file-map window misses." ::= { vmsFcp 11 } vmsFcpLookup OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of file name lookup operations in file directories." ::= { vmsFcp 12 }



vmsFcpOpen OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of files opened." ::= { vmsFcp 13 } vmsFcpErase OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of erase I/O operations issued." ::= { vmsFcp 14 } -- MONITOR IO vmsIo OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 4 } vmsIoUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when I/O statistics were last updated." ::= { vmsIo 1 } vmsIoUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often I/O statistics are to be gathered. A value of 0 disables gathering of I/O statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsIo 2 } vmsIoDirectIO OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of direct I/O operations." ::= { vmsIo 3 } vmsIoBufferedIO OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of buffered I/O operations." ::= { vmsIo 4 } vmsIoMailboxWrite OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of write-to-mailbox requests." ::= { vmsIo 5 } vmsIoSplitTransfer OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of split transfers." ::= { vmsIo 6 }



vmsIoLogNameTranslation OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of logical name translations." ::= { vmsIo 7 } vmsIoFileOpen OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of files opened." ::= { vmsIo 8 } vmsIoPageFault OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of page faults for all working sets." ::= { vmsIo 9 } vmsIoPageRead OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of pages read from disk as a result of page faults." ::= { vmsIo 10 } vmsIoPageReadIO OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of read I/O operations from disk as a result of page faults." ::= { vmsIo 11 } vmsIoPageWrite OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of pages written to the page file." ::= { vmsIo 12 } vmsIoPageWriteIO OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of write I/O operations to the page file." ::= { vmsIo 13 } vmsIoInswap OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of working sets read into memory from the swap file." ::= { vmsIo 14 } vmsIoFreePageCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION



"Number of pages currently on free-page list." ::= { vmsIo 15 } vmsIoModifiedPageCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages currently on modified-page list." ::= { vmsIo 16 } -- MONITOR PAGE vmsPage OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 5 } vmsPageUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when page statistics were last updated." ::= { vmsPage 1 } vmsPageUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often Page statistics are to be gathered. A value of 0 disables gathering of Page statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsPage 2 } vmsPageFault OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of page faults for all working sets." ::= { vmsPage 3 } vmsPageRead OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of pages read from disk as a result of page faults." ::= { vmsPage 4 } vmsPageReadIO OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of read I/Os as a result of operations from disk page faults." ::= { vmsPage 5 } vmsPageWrite OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of pages written to the page file." ::= { vmsPage 6 } vmsPageWriteIO OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory



DESCRIPTION "Count of write I/O operations to the page file." ::= { vmsPage 7 } vmsPageFreeListFault OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of pages read from the free list as a result of page faults." ::= { vmsPage 8 } vmsPageModListFault OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of pages read from the modified list as a result of page faults." ::= { vmsPage 9 } vmsPageDemandZeroFault OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of zero-filled pages allocated as a result of faults." ::= { vmsPage 10 } vmsPageGlobalValidFault OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of page faults for which the reference page was found to be valid in the system global page tables." ::= { vmsPage 11 } vmsPageWrtInProgressFault OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of pages read that were in the process of being written back to disk when faulted." ::= { vmsPage 12 } vmsPageSystemFault OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of page faults for which the referenced page is in system space." ::= { vmsPage 13 } vmsPageFreePageCount OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages currently on free-page list." ::= { vmsPage 14 } vmsPageModifiedPageCount OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages currently on modified-page list."



::= { vmsPage 15 } -- MONITOR DECNET vmsDecnet OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 6 } vmsDecnetUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when DECnet statistics were last gathered." ::= { vmsDecnet 1 } vmsDecnetUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often DECnet statistics are to be gathered. A value of 0 disables gathering of DECnet statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsDecnet 2 } vmsDecnetArriveLocalPkt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of arriving local packets." ::= { vmsDecnet 3 } vmsDecnetDepartLocalPkt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of departing local packets." ::= { vmsDecnet 4 } vmsDecnetArriveTransPkt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of arriving transit packets." ::= { vmsDecnet 5 } vmsDecnetTransCongestLoss OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of packets lost because of transit congestion." ::= { vmsDecnet 6 } vmsDecnetReceiveBufFail OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of receiver buffer failures." ::= { vmsDecnet 7 } -- MONITOR STATES vmsStates OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 7 } vmsStatesUpdateTime OBJECT-TYPE SYNTAX TimeTicks



ACCESS read-only STATUS mandatory DESCRIPTION "Time when Process State data was last updated." ::= { vmsStates 1 } vmsStatesUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often Process State data are to be gathered. A value of 0 disables gathering of Process State statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsStates 2 } vmsStatesCOLPG OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes in Collided Page Wait State (COLPG)." ::= { vmsStates 3 } vmsStatesMWAIT OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes in Miscellaneous Resource Wait State (MWAIT)." ::= { vmsStates 4 } vmsStatesCEF OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes in Common Event Flag Wait State (CEF)." ::= { vmsStates 5 } vmsStatesPFW OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes in Page Fault Wait State (PFW)." ::= { vmsStates 6 } vmsStatesLEF OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes in Local Event Flag Wait State (LEF)." ::= { vmsStates 7 } vmsStatesLEFO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of Outswapped processes in Local Event Flag Wait State (LEFO)." ::= { vmsStates 8 } vmsStatesHIB OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION



"Number of processes in Hibernate State (HIB)." ::= { vmsStates 9 } vmsStatesHIBO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of Outswapped processes in Hibernate State (HIBO)." ::= { vmsStates 10 } vmsStatesSUSP OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes in Suspended State (SUSP)." ::= { vmsStates 11 } vmsStatesSUSPO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of Outswapped processes in Suspended State (SUSPO)." ::= { vmsStates 12 } vmsStatesFPG OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes in Free Page Wait State (FPG)." ::= { vmsStates 13 } vmsStatesCOM OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes in Compute State (COM)." ::= { vmsStates 14 } vmsStatesCOMO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of Outswapped processes in Compute State (COMO)." ::= { vmsStates 15 } vmsStatesCUR OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of current processes (CUR)." ::= { vmsStates 16 } -- MONITOR CLUSTER vmsCluster OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 8 } vmsClusterUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when cluster statistics were last updated. " ::= { vmsCluster 1 }



vmsClusterUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often cluster statistics are to be gathered. A value of 0 disables gathering of cluster statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsCluster 2 } vmsClusterCpuBusy OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Count of clock ticks (10-millisecond units) spent in all CPU modes since system was booted." ::= { vmsCluster 3 } vmsClusterFreeListSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages currently on the free list." ::= { vmsCluster 4 } vmsClusterTotalLocks OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Total of all incoming, outgoing, and local ENQs, DEQs, and conversions." ::= { vmsCluster 5 } vmsClusterNewEnqLocal OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of new lock requests that originate and are performed on the system." ::= { vmsCluster 6 } vmsClusterNewEnqIncoming OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of new lock requests that originate on other systems and are performed on this system (incoming)." ::= { vmsCluster 7 } vmsClusterNewEnqOutgoing OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of new lock requests that originate on this system and are performed on other systems (outgoing)." ::= { vmsCluster 8 } vmsClusterEnqConversionsLocal OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of lock conversion requests (local)." ::= { vmsCluster 9 }



vmsClusterEnqConversionsIncoming OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of lock conversion requests (incoming)." ::= { vmsCluster 10 } vmsClusterEnqConversionsOutgoing OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of lock conversion requests (outgoing)." ::= { vmsCluster 11 } vmsClusterDeqLocal OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of unlock requests (local)." ::= { vmsCluster 12 } vmsClusterDeqIncoming OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of unlock requests (incoming)." ::= { vmsCluster 13 } vmsClusterDeqOutgoing OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of unlock requests (outgoing)." ::= { vmsCluster 14 } -- MONITOR MSCP SERVER vmsMscp OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 9 } vmsMscpUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when MSCP Server statistics were last updated. " ::= { vmsMscp 1 } vmsMscpUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often MSCP Server statistics are to be gathered. A value of 0 disables gathering of MSCP statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsMscp 2 } vmsMscpRequests OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of requests for I/O transfers by remote processors." ::= { vmsMscp 3 }



vmsMscpReads OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of requests for Read I/O transfers by remote processors." ::= { vmsMscp 4 } vmsMscpWrites OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of requests for Write I/O transfers by remote processors." ::= { vmsMscp 5 } vmsMscpFragments OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of extra fragments issued by the server." ::= { vmsMscp 6 } vmsMscpSplits OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of fragmented requests issued by the server." ::= { vmsMscp 7 } vmsMscpBufferWaits OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of requests that had to wait for MSCP buffer memory." ::= { vmsMscp 8 } vmsMscp1BlockIOs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of I/O requests with a length of one block." ::= { vmsMscp 9 } vmsMscp2-3BlockIOs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of I/O requests with a length of 2 to 3 blocks." ::= { vmsMscp 10 } vmsMscp4-7BlockIOs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of I/O requests with a length of 4 to 7 blocks." ::= { vmsMscp 11 } vmsMscp8-15BlockIOs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory



DESCRIPTION "Count of I/O requests with a length of 8 to 15 blocks." ::= { vmsMscp 12 } vmsMscp16-31BlockIOs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of I/O requests with a length of 16 to 31 blocks." ::= { vmsMscp 13 } vmsMscp32-63BlockIOs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of I/O requests with a length of 32 to 63 blocks." ::= { vmsMscp 14 } vmsMscp64andOverBlockIOs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of I/O requests with a length equal to or greater than 64 blocks." ::= { vmsMscp 15 } -- MONITOR LOCK vmsLock OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 10 } vmsLockUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when Lock statistics were last updated. " ::= { vmsLock 1 } vmsLockUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often Lock statistics are to be gathered. A value of 0 disables gathering of lock statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsLock 2 } vmsLockNewEnqs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of new ENQ (lock) requests." ::= { vmsLock 3 } vmsLockConvertedEnqs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of converted ENQ (lock) requests." ::= { vmsLock 4 } vmsLockDeqs OBJECT-TYPE SYNTAX Counter ACCESS read-only



STATUS mandatory DESCRIPTION "Count of DEQ (unlock) requests." ::= { vmsLock 5 } vmsLockBlockingASTs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of blocking ASTs queued." ::= { vmsLock 6 } vmsLockEnqWaits OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of times a lock could not be granted immediately and waited." ::= { vmsLock 7 } vmsLockEnqsNotQueued OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of times a lock could not be granted immediately and got an error status instead of waiting." ::= { vmsLock 8 } vmsLockDeadlockSearches OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of times that a deadlock search was performed." ::= { vmsLock 9 } vmsLockDeadlocksFound OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of times that a deadlock was found." ::= { vmsLock 10 } vmsLockCurrentLocks OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of locks currently in the system." ::= { vmsLock 11 } vmsLockCurrentResources OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of resources currently in the system." ::= { vmsLock 12 } -- MONITOR DLOCK vmsDlock OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 11 } vmsDlockUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory



DESCRIPTION "Time when Distributed Lock statistics were last updated. " ::= { vmsDlock 1 } vmsDlockUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often Lock statistics are to be gathered. A value of 0 disables gathering of dlock statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsDlock 2 } vmsDlockNewLocksLocal OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of new lock requests that originate and are performed on this system (local)." ::= { vmsDlock 3 } vmsDlockNewLocksIncoming OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of new lock requests originating on another system and performed on this system (incoming)." ::= { vmsDlock 4 } vmsDlockNewLocksOutgoing OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of new lock requests originating on this system and performed on another system (outgoing)." ::= { vmsDlock 5 } vmsDlockLockConversionsLocal OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of lock conversion requests (local)." ::= { vmsDlock 6 } vmsDlockLockConversionsIncoming OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of lock conversion requests (incoming)." ::= { vmsDlock 7 } vmsDlockLockConversionsOutgoing OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of lock conversion requests (outgoing)." ::= { vmsDlock 8 } vmsDlockUnlocksLocal OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION



"Count of unlock requests (local)." ::= { vmsDlock 9 } vmsDlockUnlocksIncoming OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of unlock requests (incoming)." ::= { vmsDlock 10 } vmsDlockUnlocksOutgoing OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of unlock requests (outgoing)." ::= { vmsDlock 11 } vmsDlockBlockingASTsLocal OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of lock manager blocking ASTs (local)." ::= { vmsDlock 12 } vmsDlockBlockingASTsIncoming OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of lock manager blocking ASTs (incoming)." ::= { vmsDlock 13 } vmsDlockBlockingASTsOutgoing OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of lock manager blocking ASTs (outgoing)." ::= { vmsDlock 14 } vmsDlockDirFuncIncoming OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of directory functions (incoming)." ::= { vmsDlock 15 } vmsDlockDirFuncOutgoing OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of directory functions (outgoing)." ::= { vmsDlock 16 } vmsDlockDeadlockMessage OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of incoming and outgoing lock manager messages required for deadlock detection." ::= { vmsDlock 17 } -- MONITOR SYSTEM vmsSystem OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 12 }



vmsSystemUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when system statistics were last updated. " ::= { vmsSystem 1 } vmsSystemUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often system statistics are to be gathered. A value of 0 disables gathering of system statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsSystem 2 } vmsSystemCpuBusy OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of clock ticks (10-millisecond units) spent in all CPU modes since system was booted." ::= { vmsSystem 3 } vmsSystemOtherStates OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes in states other than LEF, LEFO, HIB, HIBO, COM, COMO, PFW, and MWAIT." ::= { vmsSystem 4 } vmsSystemProcessCount OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of processes in the system." ::= { vmsSystem 5 } vmsSystemPageFaults OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of page faults for all working sets." ::= { vmsSystem 6 } vmsSystemReadIOs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of read I/Os resulting from disk page faults." ::= { vmsSystem 7 } vmsSystemFreePageCount OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages currently on free-page list." ::= { vmsSystem 8 } vmsSystemModifiedPageCount OBJECT-TYPE



SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages currently on modified-page list." ::= { vmsSystem 9 } vmsSystemDirectIOs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of direct I/O operations." ::= { vmsSystem 10 } vmsSystemBufferedIOs OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Count of buffered I/O operations." ::= { vmsSystem 11 } vmsRlock OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 13 } vmsRlockUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when rlock statistics were last updated. " ::= { vmsRlock 1 } vmsRlockUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often rlock statistics are to be gathered. A value of 0 disables gathering of system statistics. This value is expressed in minutes." DEFVAL { 1 } ::= { vmsRlock 2 } vmsRlockAcquire OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of lock trees moved to this node. Only available in VMS v7.3-1 and later." ::= { vmsRlock 3 } vmsRlockBetter OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of lock trees moved from this node to a cluster node with a higher value for the system parameter LOCKDIRWT. Only available in VMS v7.3-1 and later." ::= { vmsRlock 4 } vmsRlockMoreAct OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of lock trees moved



from this node due to higher locking activity on another node in the cluster. Only available in VMS v7.3-1 and later." ::= { vmsRlock 5 } vmsRlockMsgRcv OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of remaster messages received by this node. Only available in VMS v7.3-1 and later." ::= { vmsRlock 6 } vmsRlockMsgSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of remaster messages sent from this node. Only available in VMS v7.3-1 and later." ::= { vmsRlock 7 } vmsRlockNoQuota OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of remaster operations that failed due to a lack of quota. Only available in VMS v7.3-1 and later" ::= { vmsRlock 8 } vmsRlockNoTaker OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of remaster operations that were proposed and declined. Only available in VMS v7.3-1 and later." ::= { vmsRlock 9 } vmsRlockOpCnt OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of remaster operations that have been completed. Only available in VMS v7.3-1 and later." ::= { vmsRlock 10 } vmsRlockRbldMsgRcv OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of remaster rebuild messages received by this node. Only available in VMS v7.3-1 and later." ::= { vmsRlock 11 } vmsRlockRbldMsgSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of remaster rebuild messages sent from this node. Only available in VMS v7.3-1 and later."



::= { vmsRlock 12 } vmsRlockSingle OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of lock trees moved from this node to another cluster node because that node is the only one with locks remaining on the tree. Only available in VMS v7.3-1 and later." ::= { vmsRlock 13 } vmsRlockUnlock OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The accumulated systemwide count of lock trees moved from this node. Only available in VMS v7.3-1 and later." ::= { vmsRlock 14 } vmsTimer OBJECT IDENTIFIER ::= { comtekVmsNMVmsMonMib 14 } vmsTimerUpdateTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time when timer statistics were last updated. " ::= { vmsTimer 1 } vmsTimerUpdateInterval OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "How often timer statistics are to be gathered. A value of 0 disables gathering of system statistics. This value is expressed in minutes. " DEFVAL { 1 } ::= { vmsTimer 2 } vmsTimerSysubLow OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The low order longword of the accumulated systemwide count of timer requests made by the OpenVMS operating system. Only available in VMS v7.3-1 and later." ::= { vmsTimer 3 } vmsTimerSysubHigh OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The high order longword of the accumulated systemwide count of timer requests made by the OpenVMS operating system. Only available in VMS v7.3-1 and later." ::= { vmsTimer 4 } vmsTimerTotalLow OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The low order longword of the accumulated systemwide count of timer requests. Only available in VMS v7.3-1 and later."



::= { vmsTimer 5 } vmsTimerTotalHigh OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The high order longword of the accumulated systemwide count of timer requests. Only available in VMS v7.3-1 and later." ::= { vmsTimer 6 } vmsTimerUsrTimrLow OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The low order longword of the accumulated systemwide count of timer requests made by application programs through the SYS$SETIMR system service. Only available in VMS v7.3-1 and later." ::= { vmsTimer 7 } vmsTimerUsrTimrHigh OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The high order longword of the accumulated systemwide count of timer requests made by application programs through the SYS$SETIMR system service. Only available in VMS v7.3-1 and later." ::= { vmsTimer 8 } vmsTimerUsrWakeLow OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The low order longword of the accumulated systemwide count of timer requests made by application programs through the SYS$SCHDWK system service. Only available in VMS v7.3-1 and later." ::= { vmsTimer 9 } vmsTimerUsrWakeHigh OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The high order longword of the accumulated systemwide count of timer requests made by application programs through the SYS$SCHDWK system service. Only available in VMS v7.3-1 and later." ::= { vmsTimer 10 } -- The remainder of this MIB contains delta values for the -- variables above. Delta values keep track of increases -- in counter variables. -- MODE DELTAS vmsDeltaModes OBJECT IDENTIFIER ::= { vmsDeltas 1 } vmsDeltaModeTable OBJECT-TYPE SYNTAX SEQUENCE OF VmsDeltaModeTableEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table description. "



::= { vmsDeltaModes 1 } vmsDeltaModeTableEntry OBJECT-TYPE SYNTAX VmsDeltaModeTableEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Row in table description. " INDEX { vmsDeltaModeCpuId } ::= { vmsDeltaModeTable 1 } VmsDeltaModeTableEntry ::= SEQUENCE { vmsDeltaModeCpuId INTEGER, vmsDeltaModeKernel INTEGER, vmsDeltaModeExec INTEGER, vmsDeltaModeSuper INTEGER, vmsDeltaModeUser INTEGER, vmsDeltaModeInter INTEGER, vmsDeltaModeMPSync INTEGER, vmsDeltaModeCompat INTEGER, vmsDeltaModeIdle INTEGER } vmsDeltaModeCpuId OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "CPU ID for delta mode data in this row in the mode table." ::= { vmsDeltaModeTableEntry 1 } vmsDeltaModeKernel OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU spent in kernel mode (excluding interrupt stack time) during the last update interval." ::= { vmsDeltaModeTableEntry 2 } vmsDeltaModeExec OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU spent in Executive mode during the last update interval." ::= { vmsDeltaModeTableEntry 3 } vmsDeltaModeSuper OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU spent in Supervisor mode during the last update interval." ::= { vmsDeltaModeTableEntry 4 } vmsDeltaModeUser OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU spent in User mode (excluding compatibility-mode time) during the last update interval." ::= { vmsDeltaModeTableEntry 5 } vmsDeltaModeInter OBJECT-TYPE SYNTAX INTEGER



ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks (10-millisecond units) this CPU spent on the Interrupt stack during the last update interval." ::= { vmsDeltaModeTableEntry 6 } vmsDeltaModeMPSync OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU spent synchronizing multiple CPUs during the last update interval." ::= { vmsDeltaModeTableEntry 7 } vmsDeltaModeCompat OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU spent in Compatibility mode during the last update interval." ::= { vmsDeltaModeTableEntry 8 } vmsDeltaModeIdle OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks this CPU spent executing the NULL process during the last update interval." ::= { vmsDeltaModeTableEntry 9 } vmsDeltaTotalModes OBJECT IDENTIFIER ::= { vmsDeltaModes 2 } vmsDeltaTotalKernel OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Total number of clock ticks all CPUs spent in kernel mode (excluding interrupt stack time) during the last update interval." ::= { vmsDeltaTotalModes 1 } vmsDeltaTotalExec OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs spent in Executive mode during the last update interval." ::= { vmsDeltaTotalModes 2 } vmsDeltaTotalSuper OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs spent in Supervisor mode during the last update interval." ::= { vmsDeltaTotalModes 3 } vmsDeltaTotalUser OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs spent in User mode (excluding



compatibility-mode time) during the last update interval." ::= { vmsDeltaTotalModes 4 } vmsDeltaTotalInter OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks (10-millisecond units) all CPUs spent on the Interrupt stack during the last update interval." ::= { vmsDeltaTotalModes 5 } vmsDeltaTotalMPSync OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs spent synchronizing multiple CPUs during the last update interval." ::= { vmsDeltaTotalModes 6 } vmsDeltaTotalComp OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs spent in Compatibility mode during the last update interval." ::= { vmsDeltaTotalModes 7 } vmsDeltaTotalIdle OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Total clock ticks all CPUs spent executing the NULL process during the last update interval." ::= { vmsDeltaTotalModes 8 } -- FILE_SYSTEM_CACHE DELTAS vmsDeltaFile OBJECT IDENTIFIER ::= { vmsDeltas 2 } vmsDeltaFileDirFCBHit OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of hits on directory FCB cache during this update interval." ::= { vmsDeltaFile 1 } vmsDeltaFileDirFCBAttempt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of attempts on directory FCB cache during this update interval." ::= { vmsDeltaFile 2 } vmsDeltaFileDirDataHit OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of hits on directory data cache during this update interval." ::= { vmsDeltaFile 3 } vmsDeltaFileDirDataAttempt OBJECT-TYPE



SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of attempts on directory data cache during this update interval." ::= { vmsDeltaFile 4 } vmsDeltaFileFileHdrHit OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of hits on file header cache during this update interval." ::= { vmsDeltaFile 5 } vmsDeltaFileFileHdrAttempt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of attempts on file header cache during this update interval." ::= { vmsDeltaFile 6 } vmsDeltaFileFileIdHit OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of hits on file ID cache during this update interval." ::= { vmsDeltaFile 7 } vmsDeltaFileFileIdAttempt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of attempts on file ID cache during this update interval." ::= { vmsDeltaFile 8 } vmsDeltaFileExtentHit OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of hits on extent cache during this update interval." ::= { vmsDeltaFile 9 } vmsDeltaFileExtentAttempt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of attempts on extent cache during this update interval." ::= { vmsDeltaFile 10 } vmsDeltaFileQuotaHit OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of hits on quota cache during this update interval." ::= { vmsDeltaFile 11 }



vmsDeltaFileQuotaAttempt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of attempts on quota cache during this update interval." ::= { vmsDeltaFile 12 } vmsDeltaFileBitmapHit OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of hits on storage bitmap cache during this update interval." ::= { vmsDeltaFile 13 } vmsDeltaFileBitmapAttempt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of attempts on storage bitmap cache during this update interval." ::= { vmsDeltaFile 14 } -- FCP DELTA vmsDeltaFcp OBJECT IDENTIFIER ::= { vmsDeltas 3 } vmsDeltaFcpFCPCall OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of QIO requests received by the file system during the last update interval." ::= { vmsDeltaFcp 1 } vmsDeltaFcpAllocation OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of QIO requests that caused allocation of disk space during the last update interval." ::= { vmsDeltaFcp 2 } vmsDeltaFcpCreate OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of new files created during the last update interval." ::= { vmsDeltaFcp 3 } vmsDeltaFcpDiskRead OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of read I/O operations from the disk by the file system during the last update interval." ::= { vmsDeltaFcp 4 } vmsDeltaFcpDiskWrite OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory



DESCRIPTION "Number of write I/O operations to the disk by the file system during the last update interval." ::= { vmsDeltaFcp 5 } vmsDeltaFcpVolumeLockWait OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of times a wait state was entered by the XQP due to volume lock contention during the last update interval." ::= { vmsDeltaFcp 6 } vmsDeltaFcpCPUTick OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks (10-millisecond units) of CPU time used by the file system during the last update interval." ::= { vmsDeltaFcp 7 } vmsDeltaFcpPageFault OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of page faults for the file system during the last update interval." ::= { vmsDeltaFcp 8 } vmsDeltaFcpWindowTurn OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of file-map window misses during the last update interval." ::= { vmsDeltaFcp 9 } vmsDeltaFcpLookup OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of file name lookup operations in file directories during the last update interval." ::= { vmsDeltaFcp 10 } vmsDeltaFcpOpen OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of files opened during the last update interval." ::= { vmsDeltaFcp 11 } vmsDeltaFcpErase OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of erase I/O operations issued during the last update interval." ::= { vmsDeltaFcp 12 } -- MONITOR IO



vmsDeltaIo OBJECT IDENTIFIER ::= { vmsDeltas 4 } vmsDeltaIoDirectIO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of direct I/O operations during the last update interval." ::= { vmsDeltaIo 1 } vmsDeltaIoBufferedIO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of buffered I/O operations during the last update interval." ::= { vmsDeltaIo 2 } vmsDeltaIoMailboxWrite OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of write-to-mailbox requests during the last update interval." ::= { vmsDeltaIo 3 } vmsDeltaIoSplitTransfer OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of split transfers during the last update interval." ::= { vmsDeltaIo 4 } vmsDeltaIoLogNameTranslation OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of logical name translations during the last update interval." ::= { vmsDeltaIo 5 } vmsDeltaIoFileOpen OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of files opened during the last update interval." ::= { vmsDeltaIo 6 } vmsDeltaIoPageFault OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of page faults for all working sets during the last update interval." ::= { vmsDeltaIo 7 } vmsDeltaIoPageRead OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION



"Number of pages read from disk as a result of page faults during the last update interval." ::= { vmsDeltaIo 8 } vmsDeltaIoPageReadIO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of read I/O operations from disk as a result of page faults during the last update interval." ::= { vmsDeltaIo 9 } vmsDeltaIoPageWrite OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages written to the page file during the last update interval." ::= { vmsDeltaIo 10 } vmsDeltaIoPageWriteIO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of write I/O operations to the page file during the last update interval." ::= { vmsDeltaIo 11 } vmsDeltaIoInswap OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of working sets read into memory from the swap file during the last update interval." ::= { vmsDeltaIo 12 } -- PAGE DELTAS vmsDeltaPage OBJECT IDENTIFIER ::= { vmsDeltas 5 } vmsDeltaPageFault OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of page faults for all working sets during the last update interval." ::= { vmsDeltaPage 1 } vmsDeltaPageRead OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages read from disk as a result of page faults during the last update interval." ::= { vmsDeltaPage 2 } vmsDeltaPageReadIO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of read I/Os as a result of operations from disk page faults during the last update interval." ::= { vmsDeltaPage 3 }



vmsDeltaPageWrite OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages written to the page file during the last update interval." ::= { vmsDeltaPage 4 } vmsDeltaPageWriteIO OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of write I/O operations to the page file during the last update interval." ::= { vmsDeltaPage 5 } vmsDeltaPageFreeListFault OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages read from the free list as a result of page faults during the last update interval." ::= { vmsDeltaPage 6 } vmsDeltaPageModListFault OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages read from the modified list as a result of page faults during the last update interval." ::= { vmsDeltaPage 7 } vmsDeltaPageDemandZeroFault OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of zero-filled pages allocated as a result of faults during the last update interval." ::= { vmsDeltaPage 8 } vmsDeltaPageGlobalValidFault OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of page faults for which the reference page was found to be valid in the system global page tables during the last update interval." ::= { vmsDeltaPage 9 } vmsDeltaPageWrtInProgressFault OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of pages read that were in the process of being written back to disk when faulted during the last update interval." ::= { vmsDeltaPage 10 } vmsDeltaPageSystemFault OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION



"Number of page faults for which the referenced page is in system space during the last update interval." ::= { vmsDeltaPage 11 } -- DECNET DELTAS vmsDeltaDecnet OBJECT IDENTIFIER ::= { vmsDeltas 6 } vmsDeltaDecnetArriveLocalPkt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of arriving local packets during last update interval." ::= { vmsDeltaDecnet 1 } vmsDeltaDecnetDepartLocalPkt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of departing local packets during last update interval." ::= { vmsDeltaDecnet 2 } vmsDeltaDecnetArriveTransPkt OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of arriving transit packets during last update interval." ::= { vmsDeltaDecnet 3 } vmsDeltaDecnetTransCongestLoss OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of packets lost because of transit congestion during last update interval." ::= { vmsDeltaDecnet 4 } vmsDeltaDecnetReceiveBufFail OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of receiver buffer failures during last update interval." ::= { vmsDeltaDecnet 5 } -- CLUSTER DELTAS vmsDeltaCluster OBJECT IDENTIFIER ::= { vmsDeltas 8 } vmsDeltaClusterCpuBusy OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks (10-millisecond units) spent in all CPU during the last update interval." ::= { vmsDeltaCluster 1 } vmsDeltaClusterTotalLocks OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory



DESCRIPTION "Total of all incoming, outgoing, and local ENQs, DEQs, and conversions during the last update interval." ::= { vmsDeltaCluster 2 } vmsDeltaClusterNewEnqLocal OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of new lock requests that originate and are performed on the system during the last update interval." ::= { vmsDeltaCluster 3 } vmsDeltaClusterNewEnqIncoming OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of new lock requests that originate on other systems and are performed on this system (incoming) during the last update interval." ::= { vmsDeltaCluster 4 } vmsDeltaClusterNewEnqOutgoing OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of new lock requests that originate on this system and are performed on other systems (outgoing) during the last update interval." ::= { vmsDeltaCluster 5 } vmsDeltaClusterEnqConversionsLocal OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of lock conversion requests (local) during the last update interval" ::= { vmsDeltaCluster 6 } vmsDeltaClusterEnqConversionsIncoming OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of lock conversion requests (incoming) during the last update interval" ::= { vmsDeltaCluster 7 } vmsDeltaClusterEnqConversionsOutgoing OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of lock conversion requests (outgoing) during the last update interval." ::= { vmsDeltaCluster 8 } vmsDeltaClusterDeqLocal OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of unlock requests (local) during the last update interval." ::= { vmsDeltaCluster 9 } vmsDeltaClusterDeqIncoming OBJECT-TYPE



SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of unlock requests (incoming) during the last update interval." ::= { vmsDeltaCluster 10 } vmsDeltaClusterDeqOutgoing OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of unlock requests (outgoing) during the last update interval." ::= { vmsDeltaCluster 11 } -- MSCP SERVER DELTAS vmsDeltaMscp OBJECT IDENTIFIER ::= { vmsDeltas 9 } vmsDeltaMscpRequests OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of requests for I/O transfers by remote processors during the last update interval." ::= { vmsDeltaMscp 1 } vmsDeltaMscpReads OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of requests for Read I/O transfers by remote processors during the last update interval." ::= { vmsDeltaMscp 2 } vmsDeltaMscpWrites OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of requests for Write I/O transfers by remote processors during the last update interval." ::= { vmsDeltaMscp 3 } vmsDeltaMscpFragments OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of extra fragments issued by the server during the last update interval." ::= { vmsDeltaMscp 4 } vmsDeltaMscpSplits OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of fragmented requests issued by the server during the last update interval." ::= { vmsDeltaMscp 5 } vmsDeltaMscpBufferWaits OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION



"Number of requests that had to wait for MSCP buffer memory during the last update interval." ::= { vmsDeltaMscp 6 } vmsDeltaMscp1BlockIOs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of I/O requests with a length of one block during the last update interval." ::= { vmsDeltaMscp 7 } vmsDeltaMscp2-3BlockIOs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of I/O requests with a length of 2 to 3 blocks during the last update interval." ::= { vmsDeltaMscp 8 } vmsDeltaMscp4-7BlockIOs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of I/O requests with a length of 4 to 7 blocks during the last update interval." ::= { vmsDeltaMscp 9 } vmsDeltaMscp8-15BlockIOs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of I/O requests with a length of 8 to 15 blocks during the last update interval." ::= { vmsDeltaMscp 10 } vmsDeltaMscp16-31BlockIOs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of I/O requests with a length of 16 to 31 blocks during the last update interval." ::= { vmsDeltaMscp 11 } vmsDeltaMscp32-63BlockIOs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of I/O requests with a length of 32 to 63 blocks during the last update interval." ::= { vmsDeltaMscp 12 } vmsDeltaMscp64andOverBlockIOs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of I/O requests with a length equal to or greater than 64 blocks during the last update interval." ::= { vmsDeltaMscp 13 } -- LOCK DELTAS vmsDeltaLock OBJECT IDENTIFIER ::= { vmsDeltas 10 }



vmsDeltaLockNewEnqs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of new ENQ (lock) requests during this update interval." ::= { vmsDeltaLock 1 } vmsDeltaLockConvertedEnqs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of converted ENQ (lock) requests during this update interval." ::= { vmsDeltaLock 2 } vmsDeltaLockDeqs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of DEQ (unlock) requests during this update interval." ::= { vmsDeltaLock 3 } vmsDeltaLockBlockingASTs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of blocking ASTs queued during this update interval." ::= { vmsDeltaLock 4 } vmsDeltaLockEnqWaits OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of times a lock could not be granted immediately and waited during this update interval." ::= { vmsDeltaLock 5 } vmsDeltaLockEnqsNotQueued OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of times a lock could not be granted immediately and got an error status instead of waiting during this update interval." ::= { vmsDeltaLock 6 } vmsDeltaLockDeadlockSearches OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of times that a deadlock search was performed during this update interval." ::= { vmsDeltaLock 7 } vmsDeltaLockDeadlocksFound OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of times that a deadlock was found during



this update interval." ::= { vmsDeltaLock 8 } -- DLOCK DELTAS vmsDeltaDlock OBJECT IDENTIFIER ::= { vmsDeltas 11 } vmsDeltaDlockNewLocksLocal OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of new lock requests that originate and are performed on this system (local) during the last update interval." ::= { vmsDeltaDlock 1 } vmsDeltaDlockNewLocksIncoming OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of new lock requests originating on another system and performed on this system (incoming) during the last update interval." ::= { vmsDeltaDlock 2 } vmsDeltaDlockNewLocksOutgoing OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of new lock requests originating on this system and performed on another system (outgoing) during the last update interval." ::= { vmsDeltaDlock 3 } vmsDeltaDlockLockConversionsLocal OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of lock conversion requests (local) during the last update interval." ::= { vmsDeltaDlock 4 } vmsDeltaDlockLockConversionsIncoming OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of lock conversion requests (incoming) during the last update interval." ::= { vmsDeltaDlock 5 } vmsDeltaDlockLockConversionsOutgoing OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of lock conversion requests (outgoing) during the last update interval." ::= { vmsDeltaDlock 6 } vmsDeltaDlockUnlocksLocal OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of unlock requests (local) during the last update interval."



::= { vmsDeltaDlock 7 } vmsDeltaDlockUnlocksIncoming OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of unlock requests (incoming) during the last update interval." ::= { vmsDeltaDlock 8 } vmsDeltaDlockUnlocksOutgoing OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of unlock requests (outgoing) during the last update interval." ::= { vmsDeltaDlock 9 } vmsDeltaDlockBlockingASTsLocal OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of lock manager blocking ASTs (local) during the last update interval." ::= { vmsDeltaDlock 10 } vmsDeltaDlockBlockingASTsIncoming OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of lock manager blocking ASTs (incoming) during the last update interval." ::= { vmsDeltaDlock 11 } vmsDeltaDlockBlockingASTsOutgoing OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of lock manager blocking ASTs (outgoing) during the last update interval." ::= { vmsDeltaDlock 12 } vmsDeltaDlockDirFuncIncoming OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of directory functions (incoming) during the last update interval." ::= { vmsDeltaDlock 13 } vmsDeltaDlockDirFuncOutgoing OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of directory functions (outgoing) during the last update interval." ::= { vmsDeltaDlock 14 } vmsDeltaDlockDeadlockMessage OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of incoming and outgoing lock manager



messages required for deadlock detection during the last update interval." ::= { vmsDeltaDlock 15 } -- SYSTEM DELTAS vmsDeltaSystem OBJECT IDENTIFIER ::= { vmsDeltas 12 } vmsDeltaSystemCpuBusy OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of clock ticks (10-millisecond units) spent in all CPU modes during the last update interval." ::= { vmsDeltaSystem 1 } vmsDeltaSystemPageFaults OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of page faults for all working sets during the last update interval." ::= { vmsDeltaSystem 2 } vmsDeltaSystemReadIOs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of read I/Os resulting from disk page faults during the last update interval." ::= { vmsDeltaSystem 3 } vmsDeltaSystemDirectIOs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of direct I/O operations during the last update interval." ::= { vmsDeltaSystem 4 } vmsDeltaSystemBufferedIOs OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of buffered I/O operations during the last update interval." ::= { vmsDeltaSystem 5 } --////////////////////////////////////////////////////////////////////// -- created from monsub.mib --////////////////////////////////////////////////////////////////////// -- PURPOSE: -- The VMS Monitor Subagent MIB contains definitions of variables that -- are supported by the COMTEK Subagent Kernel. These variables exist -- in all COMTEK subagents. -- MIB VARIABLES: -- All COMTEK Subagents implement the following kinds of variables: -- subagent OID -- trap variables -- software error variables -- configuration variables -- See below for more information on these variables. -- -- TRAP VARIABLES:



-- Each COMTEK subagent process maintains an internal trap table -- containing the latest traps that have been sent by the subagent. -- The number of traps that are retained in the internal trap table -- is controlled by the vCfgTrapTblSize variable. Each trap that is -- sent by the subagent includes a trap sequence number and a timestamp -- as well as any trap specific data. The trap sequence number may -- be used to request that a trap be resent to the manager. -- -- The number of traps per second that may be sent is governed by the -- vCfgMaxTrapSec variable. vTrapLastSeqNumSent identifies the -- sequence number of the last trap that was actually sent, if no -- backlog of traps exists, this number will be one less than -- vTrapNextSeqNum. If a backlog exists due to throttling, then -- the size of the backlog may be determined by comparing these -- numbers. If the size of the backlog exceeds the size of the -- trap table (as set by vCfgTrapTblSize), the backlogged traps -- will be lost as they are overwritten by new traps, the number -- of traps that have been lost is contained in vTrapLostCount. -- -- SOFTWARE ERROR VARIABLES: -- The software error variables allow for diagnostic and informational -- messages to be available to the network manager. This data is -- most frequently used to provide explanations when SNMP set-requests -- are denied. These variables are available for use by the subagent -- developer. -- -- CONFIGURATION VARIABLES: -- The configuration variables reflect subagent configuration settings -- that may be made using the configuration file. All SNMP set-requests -- performed on these variables cause the disk based configuration file -- to be updated accordingly. vmsMon OBJECT IDENTIFIER ::= { comtekSubagent 7 } vSubagentOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only STATUS mandatory DESCRIPTION "Subagent OID used to identify the subagent." ::= { vmsMon 1 } vTrapNextSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The next sequence number in trap table. When this variable is sent as part of a trap, it identifies the sequence number assigned to that trap. This is a 32-bit value and will wrap after 4294967295." ::= { vmsMon 2 } vTrapTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "vCfgUpTime when the trap was created." ::= { vmsMon 3 } vTrapResendSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "Sequence number of a trap message to be resent to the manager. Setting this variable to a trap sequence number causes the specified trap message to be resent. If the set-request contains a sequence number that is not available (the number of items



retained in the trap table is dependent on the value of vCfgTrapTblSize), an error indicator will be returned." ::= { vmsMon 4 } vTrapLastSeqNumSent OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Sequence number of the last trap sent. This value may be compared to vTrapNextSeqNum to determine if a backlog of traps exists. If this value is one less than vTrapNextSeqNum, then no backlog exists. A backlog of traps may exist if more traps are generated per second than may be sent (as specified by the variable vCfgMaxTrapSec)." ::= { vmsMon 5 } vTrapLostCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates the number of traps that have been lost. A trap is considered to be lost if it is overwritten in the internal trap table before it is sent to the manager. This may occur if the trap table is not large enough (see vCfgTrapTblSize) to hold all of unsent traps. How quickly traps are sent to the manager is governed by the vCfgMaxTrapSec variable. To prevent trap loss, set these two variables so that the trap backlog does not overflow the trap table and so that traps do not flood the network." ::= { vmsMon 6 } vSwErrStatus OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The latest software status code." ::= { vmsMon 7 } vSwErrFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The file name of the software element which generated the latest software status code." ::= { vmsMon 8 } vSwErrLineNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The line number in the file which generated the latest software status code." ::= { vmsMon 9 } vSwErrLastTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "vCfgUpTime when the most recent software status code was generated." ::= { vmsMon 10 } vSwErrMessage OBJECT-TYPE SYNTAX DisplayString



ACCESS read-only STATUS mandatory DESCRIPTION "Description of the latest software error." ::= { vmsMon 11 } vCfgFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file currently being used for subagent initialization parameters. The subagent must be reinitialized (by setting the variable vCfgReinitSubagent to true) after a set-request on this variable before the new file is used. If a set-request is performed on this variable and the specified file name does not exist, is not accessible, or contains invalid data, the file name is not changed, an error is returned, and a vSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (vCfgReinitSubagent)" ::= { vmsMon 12 } vCfgLogFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Name of the log file currently being used by the subagent." ::= { vmsMon 13 } vCfgReinitSubagent OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be set to force the subagent to reinitialize. Reinitialization involves resetting the process configuration using the parameters contained in the vCfgFile and sending the vWarmStart trap." DEFVAL { false } ::= { vmsMon 14 } vCfgTraps OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if any trap messages are sent to the master agent. Setting this variable to disabled(2) disables all traps from being sent. Configuration Variable: Traps Set-requests: Take effect immediately Changes to this value are written to the vCfgFile." DEFVAL { enabled } ::= { vmsMon 15 } vCfgTrapTblSize OBJECT-TYPE SYNTAX INTEGER (10..5000) ACCESS read-write STATUS mandatory DESCRIPTION "The maximum number of traps to be retained. Traps that are retained may be resent (see vTrapResendSeqNum) unless too many subsequent traps have been generated. This variable controls how many traps are retained in the subagent's internal trap table.



Configuration Variable: TrapTableSize Set-Requests: Take effect immediately Changes to this value are written to the vCfgFile." DEFVAL { 100 } ::= { vmsMon 16 } vCfgTimeout OBJECT-TYPE SYNTAX INTEGER (0..3600) ACCESS read-only STATUS mandatory DESCRIPTION "This variable identifies the time-out value that is to be used by the subagent during subtree registration. If this value is set to zero, the default value identified by the master agent will be used. If the value specified exceeds the current maximum that the master agent allows, the master agent's maximum will be used instead. This value is specified in seconds. Configuration Variable: Timeout" DEFVAL { 0 } ::= { vmsMon 17 } vCfgControlTermProc OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Flag which may be used to disable process termination by the vCfgTermProc variable. Setting this variable to enabled(1) allows the vCfgTermProc variable to be set to true(1) to terminate the subagent process. Setting this variable to disabled(2) prevents the vCfgTermProc variable from being set. Configuration Variable: ControlTermProc" DEFVAL { disabled } ::= { vmsMon 18 } vCfgTermProc OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be used to shutdown the subagent process. Setting this flag to true causes the subagent process to respond to the set-request, send the vTermProc trap, close the connection to the master agent, and shutdown. If the vCfgControlTermProc flag state is disabled(2), the vCfgTermProc variable can not be set. Set-requests: Take effect immediately if vCfgControlTermProc is enabled(2)" DEFVAL { false } ::= { vmsMon 19 } vCfgVersion OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Current version of the NM*Toolkit Subagent Kernel software." ::= { vmsMon 20 } vCfgUpTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time."



::= { vmsMon 21 } vCfgMaxTrapSec OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "This value specifies the maximum number of traps per second that may be sent. A value of zero disables trap throttling, allowing all traps to be sent as they are generated. It is recommended that this value and vCfgTrapTblSize be tuned to each operational environment. Configuration Variable: MaxTrapSec Set-requests: Take effect immediately. Changes to this value are written to the vCfgFile." DEFVAL { 0 } ::= { vmsMon 22 } vColdStart TRAP-TYPE ENTERPRISE comtekVmsNMVmsMonSubagent VARIABLES { vTrapNextSeqNum, vTrapTime, vCfgVersion } DESCRIPTION "A vColdStart trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered." ::= 0 vSwErr TRAP-TYPE ENTERPRISE comtekVmsNMVmsMonSubagent VARIABLES { vTrapNextSeqNum, vTrapTime, vSwErrStatus, vSwErrFile, vSwErrLineNum, vSwErrMessage } DESCRIPTION "Software error encountered. This trap indicates that subagent was unable to perform some action and explains the error. This trap is typically encountered if vCfgFile is set to a new file name which is erroneous or contains invalid data." ::= 1 vTermProc TRAP-TYPE ENTERPRISE comtekVmsNMVmsMonSubagent VARIABLES { vTrapNextSeqNum, vTrapTime } DESCRIPTION "Subagent process termination." ::= 2 vWarmStart TRAP-TYPE ENTERPRISE comtekVmsNMVmsMonSubagent VARIABLES { vTrapNextSeqNum, vTrapTime } DESCRIPTION "The subagent process has been reinitialized." ::= 3 --////////////////////////////////////////////////////////////////////// -- created from nmopcom.mib --////////////////////////////////////////////////////////////////////// oOpcom OBJECT IDENTIFIER ::= { comtekVmsNMOpcomMib 1 } oOpcomCfg OBJECT IDENTIFIER ::= { comtekVmsNMOpcomMib 2 } oSubagent OBJECT IDENTIFIER ::= { comtekSubagent 6 } oOpcomMsgOne OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 1 of opcom message data. If the opcom message is longer than 255 characters, the remainder will be sent in oOpcomMsgTwo, oOpcomMsgThree, oOpcomMsgFour,



oOpcomMsgFive, and oOpcomMsgSix, and oOpcomMsgSeven as appropriate." ::= { oOpcom 1 } oOpcomMsgTwo OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 2 of opcom message data." ::= { oOpcom 2 } oOpcomMsgThree OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 3 of opcom message data." ::= { oOpcom 3 } oOpcomMsgFour OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 4 of opcom message data." ::= { oOpcom 4 } oOpcomMsgFive OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 5 of opcom message data." ::= { oOpcom 5 } oOpcomMsgSix OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 6 of opcom message data." ::= { oOpcom 6 } oOpcomMsgSeven OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Part 7 of opcom message data." ::= { oOpcom 7 } oOpcomCfgCards OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom CARDS class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving CARDS opcom messages. Configuration Variable: OpcomCards Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 1 } oOpcomCfgCentral OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write



STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom CENTRAL class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving CENTRAL opcom messages. Configuration Variable: OpcomCentral Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 2 } oOpcomCfgCluster OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom CLUSTER class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving CLUSTER opcom messages. Configuration Variable: OpcomCluster Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 3 } oOpcomCfgDevices OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom DEVICES class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving DEVICES opcom messages. Configuration Variable: OpcomDevices Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 4 } oOpcomCfgDisks OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom DISKS class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving DISKS opcom messages. Configuration Variable: OpcomDisks Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 5 } oOpcomCfgLicense OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom LICENSE class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving LICENSE opcom messages. Configuration Variable: OpcomLicense



Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 6 } oOpcomCfgNetwork OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom NETWORK class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving NETWORK opcom messages. Configuration Variable: OpcomNetwork Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 7 } oOpcomCfgOper1 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER1 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER1 opcom messages. Configuration Variable: OpcomOper1 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 8 } oOpcomCfgOper2 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER2 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER2 opcom messages. Configuration Variable: OpcomOper2 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 9 } oOpcomCfgOper3 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER3 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER3 opcom messages. Configuration Variable: OpcomOper3 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 10 } oOpcomCfgOper4 OBJECT-TYPE



SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER4 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER4 opcom messages. Configuration Variable: OpcomOper4 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 11 } oOpcomCfgOper5 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER5 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER5 opcom messages. Configuration Variable: OpcomOper5 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 12 } oOpcomCfgOper6 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER6 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER6 opcom messages. Configuration Variable: OpcomOper6 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 13 } oOpcomCfgOper7 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER7 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER7 opcom messages. Configuration Variable: OpcomOper7 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 14 } oOpcomCfgOper8 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER8 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER8 opcom messages.



Configuration Variable: OpcomOper8 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 15 } oOpcomCfgOper9 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER9 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER9 opcom messages. Configuration Variable: OpcomOper9 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 16 } oOpcomCfgOper10 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER10 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER10 opcom messages. Configuration Variable: OpcomOper10 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 17 } oOpcomCfgOper11 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER11 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER11 opcom messages. Configuration Variable: OpcomOper11 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 18 } oOpcomCfgOper12 OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom OPER12 class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving OPER12 opcom messages. Configuration Variable: OpcomOper12 Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 19 }



oOpcomCfgPrinter OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom PRINTER class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving PRINTER opcom messages. Configuration Variable: OpcomPrinter Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 20 } oOpcomCfgSecurity OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom SECURITY class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving SECURITY opcom messages. Configuration Variable: OpcomSecurity Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 21 } oOpcomCfgTapes OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will receive opcom TAPES class messages. Setting this variable to disabled(2) disables NM*Opcom from receiving TAPES opcom messages. Configuration Variable: OpcomTapes Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oOpcomCfg 22 } oOpcomCfgFilter OBJECT-TYPE SYNTAX INTEGER { dropMatch(1), keepMatch(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if NM*Opcom will drop messages that match filter criteria or drop all messages except those that match filter criteria. Configuration Variable: Filter Set-requests: Take effect on next process start-up Changes to this value are written to the oCfgFile." DEFVAL { dropMatch } ::= { oOpcomCfg 23 } oSubagentOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only STATUS mandatory DESCRIPTION "Subagent OID used to identify the subagent."



::= { oSubagent 1 } oTrapNextSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The next sequence number in trap table. When this variable is sent as part of a trap, it identifies the sequence number assigned to that trap. This is a 32-bit value and will wrap after 4294967295." ::= { oSubagent 2 } oTrapTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "oCfgUpTime when the trap was created." ::= { oSubagent 3 } oTrapResendSeqNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "Sequence number of a trap message to be resent to the manager. Setting this variable to a trap sequence number causes the specified trap message to be resent. If the set-request contains a sequence number that is not available (the number of items retained in the trap table is dependent on the value of oCfgTrapTblSize), an error indicator will be returned." ::= { oSubagent 4 } oTrapLastSeqNumSent OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Sequence number of the last trap sent. This value may be compared to oTrapNextSeqNum to determine if a backlog of traps exists. If this value is one less than oTrapNextSeqNum, then no backlog exists. A backlog of traps may exist if more traps are generated per second than may be sent (as specified by the variable oCfgMaxTrapSec)." ::= { oSubagent 5 } oTrapLostCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "This variable indicates the number of traps that have been lost. A trap is considered to be lost if it is overwritten in the internal trap table before it is sent to the manager. This may occur if the trap table is not large enough (see oCfgTrapTblSize) to hold all of unsent traps. How quickly traps are sent to the manager is governed by the oCfgMaxTrapSec variable. To prevent trap loss, set these two variables so that the trap backlog does not overflow the trap table and so that traps do not flood the network." ::= { oSubagent 6 } oSwErrStatus OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The latest software status code."



::= { oSubagent 7 } oSwErrFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "The file name of the software element which generated the latest software status code." ::= { oSubagent 8 } oSwErrLineNum OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The line number in the file which generated the latest software status code." ::= { oSubagent 9 } oSwErrLastTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "oCfgUpTime when the most recent software status code was generated." ::= { oSubagent 10 } oSwErrMessage OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Description of the latest software error." ::= { oSubagent 11 } oCfgFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "Name of the file currently being used for subagent initialization parameters. The subagent must be reinitialized (by setting the variable oCfgReinitSubagent to true) after a set-request on this variable before the new file is used. If a set-request is performed on this variable and the specified file name does not exist, is not accessible, or contains invalid data, the file name is not changed, an error is returned, and a oSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (oCfgReinitSubagent)" ::= { oSubagent 12 } oCfgLogFile OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION "Name of the log file currently being used by the subagent." ::= { oSubagent 13 } oCfgReinitSubagent OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be set to force the subagent to reinitialize. Reinitialization involves resetting the



process configuration using the parameters contained in the oCfgFile and sending the oWarmStart trap." DEFVAL { false } ::= { oSubagent 14 } oCfgTraps OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which determines if any trap messages are sent to the master agent. Setting this variable to disabled(2) disables all traps from being sent. Configuration Variable: Traps Set-requests: Take effect immediately Changes to this value are written to the oCfgFile." DEFVAL { enabled } ::= { oSubagent 15 } oCfgTrapTblSize OBJECT-TYPE SYNTAX INTEGER (10..5000) ACCESS read-write STATUS mandatory DESCRIPTION "The maximum number of traps to be retained. Traps that are retained may be resent (see oTrapResendSeqNum) unless too many subsequent traps have been generated. This variable controls how many traps are retained in the subagent's internal trap table. Configuration Variable: TrapTableSize Set-Requests: Take effect immediately Changes to this value are written to the oCfgFile." DEFVAL { 100 } ::= { oSubagent 16 } oCfgTimeout OBJECT-TYPE SYNTAX INTEGER (0..3600) ACCESS read-only STATUS mandatory DESCRIPTION "This variable identifies the time-out value that is to be used by the subagent during subtree registration. If this value is set to zero, the default value identified by the master agent will be used. If the value specified exceeds the current maximum that the master agent allows, the master agent's maximum will be used instead. This value is specified in seconds. Configuration Variable: Timeout Set-requests: Take effect at next process start-up Changes to this value are written to the oCfgFile." DEFVAL { 0 } ::= { oSubagent 17 } oCfgControlTermProc OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } ACCESS read-only STATUS mandatory DESCRIPTION "Flag which may be used to disable process termination by the oCfgTermProc variable. Setting this variable to enabled(1) allows the oCfgTermProc variable to be set to true(1) to terminate the subagent process. Setting this variable to disabled(2) prevents the oCfgTermProc variable from being set.



Configuration Variable: ControlTermProc" DEFVAL { disabled } ::= { oSubagent 18 } oCfgTermProc OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-write STATUS mandatory DESCRIPTION "Flag which may be used to shutdown the subagent process. Setting this flag to true causes the subagent process to respond to the set-request, send the oTermProc trap, close the connection to the master agent, and shutdown. If the oCfgControlTermProc flag state is disabled(2), the oCfgTermProc variable can not be set. Set-requests: Take effect immediately if oCfgControlTermProc is enabled(2)" DEFVAL { false } ::= { oSubagent 19 } oCfgVersion OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "Current version of the NM*Toolkit Subagent Kernel software." ::= { oSubagent 20 } oCfgUpTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Subagent up time." ::= { oSubagent 21 } oCfgMaxTrapSec OBJECT-TYPE SYNTAX INTEGER (0..100) ACCESS read-write STATUS mandatory DESCRIPTION "This value specifies the maximum number of traps per second that may be sent. A value of zero disables trap throttling, allowing all traps to be sent as they are generated. It is recommended that this value and oCfgTrapTblSize be tuned to each operational environment. Configuration Variable: MaxTrapSec Set-requests: Take effect immediately. Changes to this value are written to the oCfgFile." DEFVAL { 0 } ::= { oSubagent 22 } -- The NM*Opcom Subagent process maintains an internal trap table -- containing the latest traps that have been sent by the subagent. -- The number of traps that are retained in the internal trap table -- is controlled by the oCfgTrapTblSize variable. Each trap that is -- sent by NM*Opcom includes a trap sequence number and a timestamp -- as well as any trap specific data. The trap sequence number may -- be used to request that a trap be resent to the manager. -- -- The number of traps per second that may be sent is governed by the -- oCfgMaxTrapSec variable. oTrapLastSeqNumSent identifies the -- sequence number of the last trap that was actually sent, if no -- backlog of traps exists, this number will be one less than -- oTrapNextSeqNum. If a backlog exists due to throttling, then -- the size of the backlog may be determined by comparing these -- numbers. If the size of the backlog exceeds the size of the



-- trap table (as set by oCfgTrapTblSize), the backlogged traps -- will be lost as they are overwritten by new traps, the number -- of traps that have been lost is contained in oTrapLostCount. oColdStart TRAP-TYPE ENTERPRISE comtekVmsNMOpcomSubagent VARIABLES { oTrapNextSeqNum, oTrapTime, oCfgVersion } DESCRIPTION "A oColdStart trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered." ::= 0 oSwErr TRAP-TYPE ENTERPRISE comtekVmsNMOpcomSubagent VARIABLES { oTrapNextSeqNum, oTrapTime, oSwErrStatus, oSwErrFile, oSwErrLineNum, oSwErrMessage } DESCRIPTION "Software error encountered. This trap indicates that subagent was unable to perform some action and explains the error. This trap is typically encountered if oCfgFile is set to a new file name which is erroneous or contains invalid data." ::= 1 oTermProc TRAP-TYPE ENTERPRISE comtekVmsNMOpcomSubagent VARIABLES { oTrapNextSeqNum, oTrapTime } DESCRIPTION "Subagent process termination." ::= 2 oWarmStart TRAP-TYPE ENTERPRISE comtekVmsNMOpcomSubagent VARIABLES { oTrapNextSeqNum, oTrapTime } DESCRIPTION "The subagent process has been reinitialized." ::= 3 oOpcomTrp TRAP-TYPE ENTERPRISE comtekVmsNMOpcomSubagent VARIABLES { oTrapNextSeqNum, oTrapTime, oOpcomMsgOne, oOpcomMsgTwo, oOpcomMsgThree, oOpcomMsgFour, oOpcomMsgFive, oOpcomMsgSix, oOpcomMsgSeven } DESCRIPTION "Opcom message." ::= 4 END

snmp system management agent openvms version 4 · openvms vax, alpha and itanium systems to network...

Documents