Page 1 Management Manual Abstract This manual describes how to install, start, configure, and stop the HP Simple Network Management Protocol (SNMP) Agent and subagents. The SCF commands used by SNMP are described. This manual also discusses the objects in the Management Information Bases (MIBs) used by the agent and subagents.
Page 2 424777-004 SNMP Agent (T9576G06) December 2003 424777-005 SNMP Agent (T9576G06) September 2004 424777-006 SNMP Agent (T9576G06, T9576H01) July 2004 Subagent Product Versions IPX/SPX Subagent (T8170D30) TCP/IP Subagent (T7862G05) Ethernet/Token Ring Subagent (T0326G06) Trap Multiplexer (T1041G06) NonStop NET/MASTER Trap Subagent (T8491D20)
Page 3: Table Of Contents
SNMP Configuration and Management Manual Glossary Index Examples Figures Tables What’s New in This Manual xxiii Manual Information xxiii New and Changed Information xxiv About This Manual Your Comments Invited Audience Purpose xxvi Organization xxvi Related Reading xxviii Notation Conventions xxviii Part I.
Page 4 Contents 1. The NonStop SNMP Environment (continued) 1. The NonStop SNMP Environment (continued) Traps 1-14 Architectural Overview of NonStop SNMP 1-14 RFC Compliance 1-17 Related Documents 1-18 2. Installing and Configuring the SNMP Agent Installation Before You Configure the SNMP Agent Operations Environment Initialization Tasks The Default SNMP Agent The SNMPCTL File...
Page 5 Contents 2. Installing and Configuring the SNMP Agent (continued) 2. Installing and Configuring the SNMP Agent (continued) After a Request Has Been Authenticated 2-31 Security Scenarios for SNMP Managers Using TCP/IP 2-32 Configuring TCP/IP Request/Response Connections 2-34 Single-Agent Connections 2-35 Multiple-Agent Connections 2-35 Remote Connections...
Page 6 Contents 4. Introduction to SCF for the SNMP Agent Part II. SCF for the SNMP Agent 4. Introduction to SCF for the SNMP Agent Tasks You Can Perform With SCF SCF and the DSM Family of Products Subsystem Programmatic Interface The Subsystem Control Point Objects Object Attributes...
Page 7 Contents 4. Introduction to SCF for the SNMP Agent (continued) 4. Introduction to SCF for the SNMP Agent (continued) Continuing a Command to the Next Line 4-23 Directing Output to a File 4-24 Error Messages 4-24 SCF Online Help 4-24 Displaying Help for NonStop Agent SCF Commands 4-24 Displaying Help for SCF Error Messages...
Page 8 Contents 5. SCF Commands for the SNMP Agent (continued) 5. SCF Commands for the SNMP Agent (continued) START PROFILE Command 5-26 START TRAPDEST Command 5-27 STATUS Command 5-28 STATUS ENDPOINT Command 5-28 STATUS PROCESS Command 5-29 STATUS PROFILE Command 5-30 STATUS TRAPDEST Command 5-31 STOP Command...
Page 9 Contents 7. Troubleshooting the SNMP Agent (continued) 7. Troubleshooting the SNMP Agent (continued) Creating a Filter Compiling the Filter Displaying Filtered Event Messages Using Trace Records TCP/IP SNMP Agent Diagnosing Request Errors Part IV. SNMP Subagents 8. TCP/IP Subagent Architectural Overview The TCP/IP Subagent and Its Managed Resources The NonStop TCP/IP Subagent and the SNMP Agent The Parallel Library TCP/IP Subagent and Its Managed Resources...
Page 10 Contents 8. TCP/IP Subagent (continued) 8. TCP/IP Subagent (continued) RFC Compliance 8-38 ifTable Maintenance 8-38 IP Group 8-40 MIB Objects 8-41 RFC Compliance 8-48 ipAddrTable Maintenance 8-50 ipRouteTable Maintenance 8-50 ipNetToMediaTable Maintenance 8-51 ICMP Group 8-51 MIB Objects 8-52 RFC Compliance 8-55 TCP Group 8-56...
Page 11 Contents 8. TCP/IP Subagent (continued) 8. TCP/IP Subagent (continued) 1014: ZTSA-EVT-TAKEOVER-BY-BACKUP 8-101 1015: ZTSA-EVT-LANMON-OBJ-UNAVAIL 8-102 1022: ZTSA-EVT-PIFGETSTATUS-ERROR 8-103 1023: ZTSA-EVT-PIFGETATTR-ERROR 8-105 1039: ZTSA-EVT-LIFGETATTR-ERROR 8-106 1041: ZTSA-EVT-PIFGETSTATS-ERROR 8-108 Converting Events to Traps 8-109 9. EMS Trap Subagent Architectural Overview RFC Compliance Installation Dependencies Installation Steps...
Page 12 Contents 11. Host Resources Subagent 11. Host Resources Subagent Architectural Overview 11-1 Standard MIB Groups 11-1 MIB Extensions 11-3 Proactive Hardware Management 11-5 Refreshing MIB Values 11-5 MIB Value Management 11-6 Obtaining Information About the Subagent 11-6 Initiating Backup Process Takeover 11-7 Monitoring the Open System Services (OSS) File System 11-7...
Page 13 Contents 11. Host Resources Subagent (continued) 11. Host Resources Subagent (continued) RFC Compliance 11-58 hrSWRun Group Maintenance 11-58 hrSWRunPerf Group 11-59 MIB Objects 11-59 Sample Data 11-60 RFC Compliance 11-61 hrSWRunPerf Group Maintenance 11-61 zhrmTableInfo Group 11-62 MIB Objects 11-64 Sample Data 11-76 zhrmTableInfo Group Maintenance...
Page 14 Contents 11. Host Resources Subagent (continued) 11. Host Resources Subagent (continued) Tokens in ZHRM Event Messages 11-105 Event Message Descriptions 11-107 001: ZHRM-EVT-HRM-SA-TERMINATED 11-108 002: ZHRM-EVT-HRM-SA-STARTED 11-109 003: ZHRM-EVT-HRM-SA-IO-ERR 11-111 004: ZHRM-EVT-HRM-SA-NO-MEM-SPACE 11-113 005: ZHRM-EVT-HRM-SA-PROG-ERR 11-114 Related Operating System Event Messages 11-115 Converting Events to Traps 11-116...
Page 15 Contents 12. Trap Multiplexer Subagent/Manager (continued) 12. Trap Multiplexer Subagent/Manager (continued) 005: ZTMX-EVT-TRAP-EGP-LOSS 12-37 006: ZTMX-EVT-TRAP-ENT-SPFC 12-38 Process Event Message Descriptions 12-39 101: ZTMX-EVT-TMX-TERMINATED 12-40 102: ZTMX-EVT-TMX-STARTED 12-42 103: ZTMX-EVT-TMX-IO-ERR 12-43 104: ZTMX-EVT-TMX-NO-MEM-SPACE 12-45 105: ZTMX-EVT-TMX--PROG-ERR 12-46 Related Operating System Event Messages 12-47 Converting Events to Traps 12-48...
Page 16 Contents 13. IPX/SPX Subagent (G-Series) (continued) 13. IPX/SPX Subagent (G-Series) (continued) Compliance With Novell MIB 13-21 HP MIB Objects 13-22 zipx Group 13-23 zisa Group 13-37 EMS Support 13-45 Subsystem ID 13-46 Tokens in ZISA Event Messages 13-46 Event Message Descriptions...
Page 17 Contents 14. Ethernet Subagent (continued) 14. Ethernet Subagent (continued) Ethernet-Like Statistics dot3Group 14-19 MIB Objects 14-20 RFC Compliance 14-27 dot3StatsTable Maintenance 14-28 Traps Generated by the Ethernet Subagent 14-29 EMS Support 14-30 Data Definitions 14-31 Subsystem ID 14-32 Ethernet Subagent (ZESA) Tokens 14-32 Standard EMS Tokens 14-32...
Page 18 SCF-Generated Numbered Error Messages Common Error Messages Subsystem-Specific Error Messages Common Versus Subsystem-Specific Errors SCF Error Messages Help If You Have to Call HP NonStop Agent Error Messages SNMP Error 00001 SNMP Error 00002 SNMP Error 00004 SNMP Error 00005...
Page 19 Contents Glossary Glossary Index Examples Example 9-1. ASN.1 Source Code for EMS Trap MIB Example 9-2. Example Routing Distributor Filter Example 9-3. Example TACL Macro for Starting EMS Trap Subagent 9-11 Example 10-1. ASN.1 Source Code for EMS Trap MIB 10-6 Example 10-2.
Page 20 Contents Figures (continued) Figures (continued) Figure 4-10. TRAPDEST Object State Transition Sequence 4-20 Figure 6-1. Recording and Displaying Trace Data Figure 8-1. Architectural Overview of the TCP/IP Subagent Figure 8-2. TCP/IP Subagent Scenarios Figure 8-3. TCP/IP Subagent Resource Object States 8-29 Figure 9-1.
Page 21 Contents Tables (continued) Tables (continued) Table 3-6. RowStatus Value Definitions 3-24 Table 3-7. RowStatus Values and Table Management Operations 3-26 Table 3-8. ENDPOINT and TRAPDEST Default Values 3-29 Table 3-9. RowStatus Values With Defined and Undefined Row Objects 3-29 Table 3-10. Initial Values of Objects in the SNMP Agent's MIB 3-32 Table 3-11.
Page 22 Contents Tables (continued) Tables (continued) Table 10-4. closeagent Return Codes and GENTRAP Actions 10-20 Table 11-1. Host Resources Subagent Configuration Options 11-10 Table 11-2. hrSystem Group Objects Supported by Host Resources Subagent's 11-26 Table 11-3. Compliance With hrSystem Group Definitions in RFC 1514 11-28 Table 11-4.
Page 23 Contents Tables (continued) Tables (continued) Table 12-5. Trap Event Token Summary 12-23 Table 12-6. Trap Multiplexer Process Event Messages 12-25 Table 12-7. ZTMX Tokens in ZTMX Event Messages 12-26 Table 12-8. ZSPI Tokens in ZTMX Event Messages 12-27 Table 12-9. ZEMS Tokens in ZTMX Event Messages 12-28 Table 13-1.
Page 24 Contents Tables (continued) SNMP Configuration and Management Manual—424777-006 xxii...
Page 25: What's New In This Manual
SNMP Configuration and Management Manual Abstract This manual describes how to install, start, configure, and stop the HP Simple Network Management Protocol (SNMP) Agent and subagents. The SCF commands used by SNMP are described. This manual also discusses the objects in the Management Information Bases (MIBs) used by the agent and subagents.
Page 26: New And Changed Information
New and Changed Information This revision contains these changes and additions: Section Change Section 1, The NonStop Notes concerning H-Series support have been included. SNMP Environmentt Section 2, Installing and Notes concerning H-Series support have been included. Configuring the SNMP Agent Section 4, Introduction to H-series information has been added.
Page 27: About This Manual
About This Manual The SNMP agent and subagents let customers manage HP NonStop systems by using SNMP managers. SNMP managers are SNMP-compliant applications that manage multiplatform networks. This manual describes how to install, configure, and interpret information generated by the SNMP agent and its subagents. It also defines SCF commands for SNMP.
Page 28: Purpose
About This Manual Purpose Purpose For NonStop system personnel, this manual describes how to install and configure the SNMP agent and its subagents. It also documents the messages generated and explains how the SNMP agent and subagents fit into the overall NonStop subsystem architecture.
Page 29 About This Manual Organization Part IV, SNMP Subagents Section 8, TCP/IP Subagent, describes the subagent that facilitates management of TCP/IP processes on SNMP systems. Section 9, EMS Trap Subagent, describes the subagent that translates EMS events into SNMP traps. Section 11, Host Resources Subagent, describes the subagent that translates Event Management Service (EMS) events routed to NonStop NET/MASTER MS into SNMP traps whose objects are defined in the EMS Trap MIB.
Page 30: Related Reading
The SNMP Manager Programmer’s Guideexplains how to use the Manager Services Toolkit product to generate SNMP managers that run as NonStop Kernel processes in Guardian or HP NonStop Kernel Open System Services (OSS) environments. The TCP/IP (Parallel Library) Configuration and Management Manual describes how to configure and manage the Parallel Library TCP/IP subsystem.
Page 31 About This Manual General Syntax Notation computer type. Computer type letters within text indicate C and Open System Services (OSS) keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.c italic computer type.
Page 32 About This Manual General Syntax Notation Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown.
Page 33: Notation For Messages
About This Manual Notation for Messages !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes. For example: error := FILE_GETINFO_ ( filenum , [ filename:maxlen ] ) ;...
Page 34: Notation For Management Programming Interfaces
About This Manual Notation for Management Programming Interfaces either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: obj-type obj-name state changed to state, caused by { Object | Operator | Service } process-name State changed from old-objstate to objstate { Operator Request.
Page 35: Change Bar Notation
About This Manual Change Bar Notation Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information.
Page 36 About This Manual Change Bar Notation SNMP Configuration and Management Manual—424777-006 xxxiv...
Page 37: Part I. Installing And Configuring Snmp
Part I. Installing and Configuring SNMP Part I consists of the following sections, which give an overview of the SNMP agent and provide installation and configuration information: Section 1 The NonStop SNMP Environment Section 2 Installing and Configuring the SNMP Agent SNMP Configuration and Management Manual—424777-006...
Page 38 Part I. Installing and Configuring SNMP SNMP Configuration and Management Manual—424777-006...
Page 39: The Nonstop Snmp Environment
The NonStop SNMP Environment This section explains how HP has implemented SNMP to facilitate management of its HP NonStop systems by using SNMP-compliant applications known as managers. SNMP originated in the Internet community in the late 1980s as a means for managing TCP/IP and Ethernet networks.
Page 40: Figure 1-1. Default Snmp Agent/Manager Interaction Over Tcp/Ip
The NonStop SNMP Environment Figure 1-1. Default SNMP Agent/Manager Interaction Over TCP/IP HP NonStop Kernel System Managed Managed Resources Resources Subagent retrieves Compaq NonStop Kernel System information from managed subsystem Subagent-1 Subagent-2 Managed Subagent sends response and Resources trap messages to...
Page 41 The NonStop SNMP Environment By default, the SNMP agent does the following: Receives and sends SNMP messages through NonStop Kernel IPC calls or through any available subnet associated with the TCP/IP process $ZTC0 on the local node Accepts any request received through TCP/IP that contains the community name “public,”...
Page 42: Subsystem Components
The NonStop SNMP Environment Subsystem Components Figure 1-2. Key Components in the SNMP Environment Managed Subagent Resources Managed Subagent Resources Managed Subagent Resources System 1 Managed Managed SNMP Agent SNMP Agent Resources Resources System 2 System 3 Local Area Network Wide Area Network SNMP...
Page 43: The Nonstop Snmp Environment (Continued)
SNMP Manager An application that automates the management of network elements (managed resources) under the control of one or more SNMP agents. HP provides an SNMP agent on its NonStop systems, and other vendors provide SNMP agents on their devices. An agent communicates with a manager using the message and information protocol defined in public SNMP documents known as RFCs.
Page 44: Snmp Subagent
SNMP managers. For more information about the Subagent Toolkit, refer to the SNMP Subagent Programmer’s Guide. HP also offers a Manager Services toolkit that allows C and C++ programmers to create SNMP managers that run as NonStop Kernel processes in either the Guardian or in the Open System Services (OSS) environment.
Page 45: General Snmp Message Format
The NonStop SNMP Environment General SNMP Message Format General SNMP Message Format Each PDU is embedded in a message, or packet, beginning with a version number and a community name. The version number identifies the version of SNMP being implemented; currently, this value is always 1 for NonStop SNMP messages. The community name identifies one or more SNMP managers;...
Page 46: Response Pdu
IPC-Encoded and BER-Encoded SNMP Packets The SNMP agent can process SNMP packets encoded using the HP IPC format. The IPC format provides the best encoding and decoding performance on NonStop Kernel systems.
Page 47: Information Protocol
SNMP packets is TCP/IP’s User Datagram Protocol (UDP). The SNMP agent supports the UDP protocol. Differences in the way the SNMP agent handles requests received through the HP NonStop Kernel IPC and requests received through the UDP protocol are discussed...
Page 48: Snmp Naming Scheme
The NonStop SNMP Environment SNMP Naming Scheme SNMP Naming Scheme SNMP uses a hierarchical model to identify objects. Every object in an SNMP environment is identified by an object descriptor and an object identifier. Object descriptors are logical names. Object identifiers are expressed in numeric dot notation. For example, the System group of MIB-II is identified as: system 1.3.6.1.2.1.1...
Page 49: Figure 1-4. Nodes In The Snmp Object Tree
The NonStop SNMP Environment SNMP Naming Scheme Figure 1-4. Nodes in the SNMP Object Tree ccit (0) iso (1) identified-organization (3) dod (6) internet (1) directory (1) object identifier = mgmt (2) 1.3.6.1.2.1.1 mib-II (1) system (1) interfaces (2) at (3) ip (4) icmp (5) tcp (6)
Page 50: The Management Information Base
169 in the enterprises subtree. In the tandem subtree, nonstopsystems has been assigned the number 3. The nonstopsystems subtree contains MIBs and subsystems defined by HP. In the zsmp subtree of the nonstopsystems node, the SNMP agent subtree, zsmpagent, has been assigned the value 1.
Page 51: Table 1-1. System Group Objects Supported By Snmp Agent's Mib
The NonStop SNMP Environment The Management Information Base In this manual, descriptions of MIB objects are normally provided in tables with four columns (in some instances, the third and fourth columns have been combined). This excerpt from the table describing the System group objects in the SNMP agent’s MIB is followed by a description of each column.
Page 52: Traps
The SNMP agent also supports a private MIB (zagInternal group) that describes attributes of the SNMP agent process and defines the resources the SNMP agent uses. These private MIB objects are defined by HP and are used to control the configuration and operation of the SNMP agent.
Page 53 The NonStop SNMP Environment Architectural Overview of NonStop SNMP The SNMP agent uses Interprocess Communication (IPC) messages to communicate with independent subagents about the resources they manage. Subagents can reside on the same node as the SNMP agent or on different nodes. Each SNMP agent can support one instance of any particular subagent.
Page 54: Figure 1-5. Nonstop Snmp Architecture
The NonStop SNMP Environment Architectural Overview of NonStop SNMP Figure 1-5. NonStop SNMP Architecture Independent SNMP Subagents SNMPCTL Collector SNMP Agent ZZSMPTRP SNMP ZZSMPTRB Manager TCP/IP ($ZTC0) Local Area Network Wide Area Network SNMP SNMP Manager Station Manager Station Legend IPC messages NSK operations SNMP request/response messages...
Page 55: Rfc Compliance
The NonStop SNMP Environment RFC Compliance RFC Compliance The NonStop SNMP implementation complies with standards and guidelines published in these RFCs: RFC 1155, Structure and Identification of Management Information for TCP/IP-Based Internets. This document describes MIB naming conventions, syntax, and other MIB object characteristics. RFC 1157, A Simple Network Management Protocol (SNMP).
Page 56: Related Documents
The NonStop SNMP Environment Related Documents Related Documents The RFCs listed earlier and in other sections of this manual are public-domain documents that you can obtain from InfoWay or from one of the following sources: DDN Network Information Center 14200 Park Meadow Drive, Suite 200 Chantilly, VA 22021 phone: 1-800-365-3642 mail: nic@nic.ddn.mil...
Page 57: Installing And Configuring The Snmp Agent
Installing and Configuring the SNMP Agent The section tells you how to install, start, and stop the SNMP agent and how to configure the following: SNMPCTL file (The SNMPCTL File on page 2-6) Multiple SNMP agents per node Starting Multiple SNMP Agents on Each Node page 2-23) EMS collector (Configuring the EMS Collector...
Page 58 SNMP agent The HP resources that the SNMP manager wants to manage Note. The SNMP implementation supported by HP uses subagents to handle various collections of resources. The HP resources the SNMP manager wants to manage determine the subagents to be installed.
Page 59: Initialization Tasks
Installing and Configuring the SNMP Agent Initialization Tasks Initialization Tasks Before you begin to configure the SNMP agent you should understand what the SNMP agent does when it is started to give you an idea of the state of the SNMP agent in which you’ll be configuring.
Page 60 SNMP agent is part of the subagent’s configuration, not the SNMP agent’s configuration. Section IV, SNMP Subagents, describes installing, starting, and configuring the subagents that HP supports. Figure 2-1 illustrates the default SNMP agent operating in an SNMP network management environment.
Page 61: Figure 2-1. Default Snmp Agent/Manager Interaction Over Tcp/Ip
Installing and Configuring the SNMP Agent The Default SNMP Agent Figure 2-1. Default SNMP Agent/Manager Interaction Over TCP/IP HP NonStop Kernel System Managed Managed Resources Resources Subagent retrieves Compaq NonStop Kernel System information from managed subsystem Subagent-1 Subagent-2 Managed Subagent sends...
Page 62: The Snmpctl File
Installing and Configuring the SNMP Agent The SNMPCTL File The SNMPCTL File When started, the SNMP agent creates an SNMP control file (SNMPCTL) in the subvolume from which it is started. You control the SNMP agent by configuring the SNMPCTL file. If started using the TRACE startup parameter, the SNMP agent also creates two trace files (ZZSMPTRP and ZZSMPTRB) in the subvolume from which it is started.
Page 63: Run Command
Installing and Configuring the SNMP Agent RUN Command The Subsystem Control Facility (SCF) (Using SCF to Configure Components of the SNMP Agent Environment on page 2-16) SNMP Set operations on SNMP agent private MIB objects (Configuring the SNMP Agent Through SNMP Requests on page 2-17) Note.
Page 64 TACL RUN command options. Refer to the TACL Reference Manual for more information about these options. HP recommends using at least the NOWAIT option so you can resume TACL operations once the SNMP agent is started.
Page 65 The backup process monitors the primary process and takes over if the primary process fails. HP strongly recommends that you use this parameter. This parameter should be an integer that identifies one of the processors on your system.
Page 66 Installing and Configuring the SNMP Agent RUN Command DATAPAGES pages [E[XTENSIBLE]] specifies the amount of storage to allocate for general dynamic memory. Specify a value for pages that ranges from 0 to 65280, representing the number of 2048-byte pages to be allocated. Including the keyword EXTENSIBLE makes the segment extensible.
Page 67 Installing and Configuring the SNMP Agent RUN Command SWAPVOL #disk-name identifies the disk to use for swapping extended memory. Specify disk-name as an unqualified device name. Any qualification is ignored. The default disk is the volume used for swapping the virtual data SNMP agent processes, as specified by the optional SWAP run option.
Page 68: Special Considerations For Users Of Logical Network Partitions (Lnps)
Installing and Configuring the SNMP Agent Special Considerations for Users of Logical Network Partitions (LNPs) tracing stops when the backup process takes over. The SCF trace file is closed and preserved when the backup process takes over. TRAPPORT trap-port-number specifies the trap port to send traps from the agent. If you do not specify this option, the default value for the trap port will remain 162.
Page 69: Startup Parameter Summary
Installing and Configuring the SNMP Agent Startup Parameter Summary Startup Parameter Summary Table 2-2. Summary of Startup Parameters (page 1 of 2) Startup Parameter What the Parameter Defines Default Behavior The backup process CPU for a No parameter value is backup-cpu-number persistent agent process pair.
Page 70: Warm | Cold Custom Configuration Parameters For The Run Command
Installing and Configuring the SNMP Agent WARM | COLD Custom Configuration Parameters for the RUN Command Table 2-2. Summary of Startup Parameters (page 2 of 2) Startup Parameter What the Parameter Defines Default Behavior TCPIP^PROCESS^NAME The default TCP/IP process to $ZTC0 on the local node.
Page 71 Installing and Configuring the SNMP Agent WARM | COLD Custom Configuration Parameters for the RUN Command If an SNMPCTL file already exists in the run subvolume (when you stop and restart an SNMP agent process), the SNMP agent uses the existing configuration values. Note.
Page 72: The Snmpctl File And Trapport
The SNMPCTL File and TRAPPORT The SNMPCTL file created using earlier versions of the SNMP agent is not compatible with the T9576G06 version. A workaround is to purge the old SNMPCTL file. PARAM Statements’ Custom Configuration for the RUN Command You can use TACL PARAM statements to set startup parameters prior to issuing the RUN command.
Page 73: Request/Response Connections
Installing and Configuring the SNMP Agent Request/Response Connections Request/Response Connections The SCF ENDPOINT object identifies an Internet address and TCP/IP process to be used for the receiving and sending of SNMP request/response messages through TCP/IP. Each SCF ENDPOINT object corresponds to a row in the SNMP agent’s private zagInEndpointTable.
Page 74: Managing Configuration Definitions Through Snmp
Installing and Configuring the SNMP Agent Managing Configuration Definitions Through SNMP Managing Configuration Definitions Through SNMP You can manage the SNMP agent configuration by manipulating rows in the SNMP agent’s private MIB tables, as follows: You create, alter the attributes of, activate, inactivate, and remove rows in the SNMP agent’s private MIB zagInEndpointTable to manage the TCP/IP connection points that the SNMP agent uses for request/response messages.
Page 75: Single-Node And Multiple-Node Scenarios
Installing and Configuring the SNMP Agent Single-Node and Multiple-Node Scenarios Single-Node and Multiple-Node Scenarios Figure 2-2. Running Multiple SNMP Agents on a Single Node Managed Managed Resources Resources Subagents Subagents SNMP SNMP Agent Agent ($ZSNM0) ($ZSNM1) TCP/IP SNMP Manager VST202.vsd SNMP Configuration and Management Manual—424777-006 2- 19...
Page 76 Installing and Configuring the SNMP Agent Single-Node and Multiple-Node Scenarios Figure 2-2, two SNMP agents are running on the same node. To run multiple agents on a single node, issue the following two commands. Issue the first command from one subvolume and the second command from a different subvolume. From one subvolume: RUN $SYSTEM.SYSTEM.SNMPAGT /NAME $ZSNM0, NOWAIT/ From a different subvolume:...
Page 77: Figure 2-3. Running Snmp Agents On Multiple Nodes
Installing and Configuring the SNMP Agent Single-Node and Multiple-Node Scenarios Figure 2-3. Running SNMP Agents on Multiple Nodes Managed Resources Managed Managed Resources Resources Subagents Subagents Subagents SNMP Agent SNMP SNMP Agent Agent TCP/IP VST203.vsd SNMP Manager SNMP Manager Figure 2-3, SNMP agents on three different nodes process requests through the same TCP/IP process.
Page 78: Figure 2-4. Managing Overlapping Sets Of Resources
Installing and Configuring the SNMP Agent Single-Node and Multiple-Node Scenarios Figure 2-4. Managing Overlapping Sets of Resources Managed Managed Resources Resources Subagents Subagents SNMP SNMP SNMP Agent 2 Agent 3 Agent 1 TCP/IP TCP/IP Subagents Managed Resources SNMP Manager Y SNMP Manager X VST204.vsd Figure...
Page 79: Starting Multiple Snmp Agents On Each Node
Installing and Configuring the SNMP Agent Starting Multiple SNMP Agents on Each Node Starting Multiple SNMP Agents on Each Node At least one TCP/IP subnet is required to handle communication between a NonStop agent process and an SNMP manager that is using TCP/IP. To find out whether at least one subnet is available, issue the SCF INFO and STATUS commands against the TCP/IP subsystem SUBNET object, for example: INFO SUBNET $ZTC*.*...
Page 80: Stopping The Snmp Agent
See also The TCP/IP Subagent and Its Managed Resources on page 8-4. The following example starts two SNMP agents on the same HP node. For Parallel Library TCP/IP and NonStop TCP/IPv6, the TCP/IP process name is the TCPSAM/TCP6SAM name. $SYSTEM TCON 5> RUN $SYSTEM.SYSTEM.SNMPAGT/NAME $ZSNM0, NOWAIT/ $SYSTEM TCON 6>...
Page 81: Configuring The Ems Collector
Installing and Configuring the SNMP Agent Configuring the EMS Collector Get the name of the SNMP agent process using either the SCF STATUS PROCESS $ZSNMP command or the TACL STATUS command. STATUS PROCESS $ZSNMP SNMP Status PROCESS $ZSNMP Name Status Trace Trace File $ZSNMP...
Page 82: Using The Collector Startup Parameter
SNMP agent. For example: RUN SNMPAGT/NAME $ZSNMP, NOWAIT/ COLLECTOR $ACOL Although HP does not recommend doing so, you can suppress output of SNMP agent events altogether by including the COLLECTOR startup parameter with no argument: RUN SNMPAGT/NAME $ZSNMP, NOWAIT/ COLLECTOR This approach is the only way to suppress event logging.
Page 83 Installing and Configuring the SNMP Agent Authenticating Requests Received Over TCP/IP To avoid extraneous authenticationFailure traps, configure security before you configure request/response connection points. Request/response connection points are represented by SCF ENDPOINT objects or by rows in the SNMP agent private zagInEndpointTable.
Page 84 Installing and Configuring the SNMP Agent Authenticating Requests Received Over TCP/IP Internet Addresses Each entry in the authentication table contains a single Internet address or a full wild- card address (0.0.0.0.) specification. Internet addresses are discussed in detail in the TCP/IP Configuration and Management Manual.
Page 85 Installing and Configuring the SNMP Agent Authenticating Requests Received Over TCP/IP ACCESS or zagInPfAccess specifies the SNMP operations authorized for each community: READONLY or READWRITE. The default authentication table entry is named $agent-process.#DEFAULT and has the following attribute values associated with it (the SNMP agent process is $ZSNMP): PROFILE $ZSNMP.#DEFAULT, COMMUNITY public HOSTADDR 0.0.0.0, ACCESS READONLY You must add an authentication table entry for each community (other than “public”)
Page 86: Figure 2-5. Authenticating Requests Received Through Tcp/Ip
Installing and Configuring the SNMP Agent Authenticating Requests Received Over TCP/IP Figure 2-5. Authenticating Requests Received Through TCP/IP Request private::tsmaccess 130.253.15.230 GetNext SNMP Manager Station SNMP agent looks for SNMP agent entry containing community receives request. name. Authentication Table COMMUNITY HOSTADDR ACCESS Logical Identifer...
Page 87: Authenticating Requests Received Using The Ipc Interface
Installing and Configuring the SNMP Agent Authenticating Requests Received Using the IPC Interface Figure 2-5, the authentication table permits the SNMP agent to accept Get and GetNext requests from any SNMP manager belonging to the “public” community, as well as Set requests sent under the “Private” community from the SNMP manager whose address is 130.252.15.230.
Page 88: Security Scenarios For Snmp Managers Using Tcp/Ip
Installing and Configuring the SNMP Agent Security Scenarios for SNMP Managers Using TCP/IP By default, authenticated manager requests forwarded to subagents are processed in accordance with the access attributes of individual MIB objects. SNMP managers can perform Get and GetNext operations on read-only MIB objects and Get, GetNext, and Set operations on read-write objects.
Page 89 Installing and Configuring the SNMP Agent Security Scenarios for SNMP Managers Using TCP/IP Table 2-3. Security Scenarios (page 2 of 2) Method Scenario Tasks (SCF Commands) Alternatively, you can simply alter the STOP PROFILE default PROFILE entry and assign ALTER PROFILE READWRITE access to the “public”...
Page 90: Configuring Tcp/Ip Request/Response Connections
Installing and Configuring the SNMP Agent Configuring TCP/IP Request/Response Connections Configuring TCP/IP Request/Response Connections The TCP/IP process handling the communication between the SNMP agent process and SNMP managers is represented by a request/response connection definition. You specify and request information about the request/response connections by issuing: SCF commands against ENDPOINT objects.
Page 91: Single-Agent Connections
Installing and Configuring the SNMP Agent Single-Agent Connections Single-Agent Connections When only one SNMP agent uses a TCP/IP process, defining the request/response connection is straightforward. Use the default host address value and ensure that at least one subnet is available to handle communication with the SNMP managers. You can issue SCF INFO and STATUS commands against the TCP/IP subsystem SUBNET object to find out about the availability of subnets.
Page 92: Figure 2-6. Multiple Local Snmp Agents, Single Host Request/Response Connections
Installing and Configuring the SNMP Agent Multiple-Agent Connections Figure 2-6. Multiple Local SNMP Agents, Single Host Request/Response Connections SNMP SNMP Agent Agent ($ZSNM0) ($ZSNM1) $ZTC0 SNMP Manager VST304.vsd Figure 2-6 a successful configuration involving two SNMP agents uses the same TCP/IP process for request/response communications.
Page 93: Remote Connections
Installing and Configuring the SNMP Agent Remote Connections Remote Connections The TCP/IP process used for communicating with SNMP managers does not have to be on the same node as the agent process. As in the scenario featuring multiple SNMP agents sharing a TCP/IP process on one host (Figure 2-6), you need to ensure that every local and remote agent process sharing the TCP/IP process uses a unique...
Page 94: Configuring Trap Destinations
Installing and Configuring the SNMP Agent Configuring Trap Destinations Figure 2-7. Multiple Remote SNMP Agents, Single Host Request/Response Connections SNMP Agent ($ZSNMP) SNMP SNMP Agent Agent ($ZSNMP) ($ZSNMP) $ZTC0 SNMP Manager VST305.vsd SNMP Manager Configuring Trap Destinations Each SNMP manager to which the SNMP agent process sends trap messages is represented by a trap destination definition.
Page 95 Installing and Configuring the SNMP Agent Configuring Trap Destinations A trap destination definition has the following attributes: SNMP Agent Private MIB Object Attribute Table Object Within Table Row TRAPDEST #trapdest-name zagInTrapdestTable zagInTdName COMMUNITY zagInTdCommunity HOSTADDR zagInTdHostAddr NETWORK zagInTdNetwork zagInTdType zagInTdPort You name the object when you define it.
Page 96: Dynamically Generated Trap Destinations
Installing and Configuring the SNMP Agent Dynamically Generated Trap Destinations Dynamically Generated Trap Destinations If no trap destinations are defined, then for every SNMP manager communicating through TCP/IP from which the SNMP manager receives a request, the SNMP agent creates a trap destination definition. The trap port value is 162, the default value. Each dynamically generated TRAPDEST object contains the default community, network, and trap type attribute values.
Page 97: Forwarding Traps To Managers Communicating Through Ipc
Installing and Configuring the SNMP Agent Forwarding Traps to Managers Communicating Through IPC Forwarding Traps to Managers Communicating Through IPC No mechanism exists for the SNMP agent to automatically forward traps through the IPC interface. To forward traps to an SNMP manager that communicates with the SNMP agent through NonStop Kernel IPC calls, configure a trap destination using a host address of 127.0.0.1 (the local loopback address, a TCP/IP convention that refers to “this”...
Page 98: Single-Host Connections
Installing and Configuring the SNMP Agent Single-Host Connections Single-Host Connections Figure 2-8. Multiple SNMP Agents, Single Host Connections SNMP SNMP Agent Agent ($ZSNM0) ($ZSNM1) $ZTC1 $ZTC0 SNMP Manager Station 1 (at 130.25.86.15) SNMP Manager Station 2 Legend Trap PDUs Request/Response PDUs VST306.vsd Figure 2-8, two SNMP agents receive requests through one TCP/IP process and...
Page 99: Multiple-Host Connections
Installing and Configuring the SNMP Agent Multiple-Host Connections The SCF commands used to configure the ENDPOINT and TRAPDEST objects in Figure 2-8 are: ASSUME PROCESS $ZSNM0 STOP ENDPOINT #DEFAULT ALTER ENDPOINT #DEFAULT, NETWORK $ZTC1, & HOSTADDR 130.25.88.1 START ENDPOINT #DEFAULT ADD TRAPDEST #STA1, HOSTADDR 130.25.86.15 START TRAPDEST #STA1 ASSUME PROCESS $ZSNM1...
Page 100: Figure 2-9. Multiple Snmp Agents, Multiple Host Connections
Installing and Configuring the SNMP Agent Multiple-Host Connections Figure 2-9. Multiple SNMP Agents, Multiple Host Connections SNMP Agent ($ZSNMP) SNMP SNMP Agent Agent ($ZSNMP) ($ZSNMP) $ZTC0 SNMP Manager 1 SNMP Manager 2 (at 130.25.86.5) (at 130.25.86.4) Legend Request/Response PDUs VST307.vsd Trap PDUs Figure 2-9, the SNMP agents on nodes \A, \B, and \C accept requests from either...
Page 101 Installing and Configuring the SNMP Agent Multiple-Host Connections SYSTEM \A ASSUME PROCESS $ZSNMP STOP ENDPOINT #DEFAULT ALTER ENDPOINT #DEFAULT, NETWORK \B.$ZTC0, & HOSTADDR 130.25.86.1 START #DEFAULT ADD TRAPDEST #STA2, NETWORK \B.$ZTC0, & HOSTADDR 130.25.86.4 START TRAPDEST #STA2 SYSTEM \C ASSUME PROCESS $ZSNMP STOP ENDPOINT #DEFAULT ALTER ENDPOINT #DEFAULT, NETWORK \B.$ZTC0, &...
Page 102 Installing and Configuring the SNMP Agent Multiple-Host Connections SNMP Configuration and Management Manual—424777-006 2- 46...
Page 103: Mibs Supported By The Snmp Agent
The SNMP agent supports two MIB-II groups and one private MIB group. The two MIB- II groups provide information about agent and node configuration and SNMP message traffic to SNMP managers. The private MIB group is defined by HP and lets you monitor—and in some cases modify—SNMP agent configuration attributes from an SNMP manager.
Page 104: Rfc Compliance
MIBs Supported by the SNMP Agent RFC Compliance Subgroups of the zagInternal group are identified by a check mark in the following list and are defined by HP: iso (1) identified-organization (3) dod (6) internet (1) private (4) enterprises (1)
Page 105: System Group
MIBs Supported by the SNMP Agent System Group System Group The System group is a collection of scalar objects that provides general information about the host on which the SNMP agent is installed: iso (1) identified-organization (3) dod (6) internet (1) mgmt (2) mib-II (1) system (1)
Page 106: Table 3-1. System Group Objects Supported By Snmp Agent
MIBs Supported by the SNMP Agent MIB Objects Table 3-1. System Group Objects Supported by SNMP Agent (page 1 of 2) Object and Attributes Definition Format and Derivation of Value sysDescr A description of the node on NonStop Kernel system 1.3.6.1.2.1.1.1 which the SNMP agent is version: Dxx or Gxx...
Page 107: Rfc Compliance
MIBs Supported by the SNMP Agent RFC Compliance Table 3-1. System Group Objects Supported by SNMP Agent (page 2 of 2) Object and Attributes Definition Format and Derivation of Value sysName A name associated with an A character string of 255 or fewer 1.3.6.1.2.1.1.5 Internet address by which characters.
Page 108: Snmp Group
MIBs Supported by the SNMP Agent SNMP Group SNMP Group The SNMP group contains statistical information about all SNMP message activity handled by the SNMP agent. The SNMP group consists of a collection of scalar objects. The SNMP agent provides values for the objects identified by a check mark in the following list: iso (1) identified-organization (3)
Page 109: Mib Objects
MIBs Supported by the SNMP Agent MIB Objects MIB Objects Table 3-2 describes the MIB-II SNMP group objects that are supported by the SNMP agent. Table 3-2. SNMP Group Objects Supported by SNMP Agent (page 1 of 3) Format and Derivation of Object and Attributes Definition Value...
Page 110 MIBs Supported by the SNMP Agent MIB Objects Table 3-2. SNMP Group Objects Supported by SNMP Agent (page 2 of 3) Format and Derivation of Object and Attributes Definition Value snmpInReadOnlys The total number of valid PDUs The constant value for this 1.3.6.1.2.1.11.11 received for which the value of object is 0.
Page 111 MIBs Supported by the SNMP Agent MIB Objects Table 3-2. SNMP Group Objects Supported by SNMP Agent (page 3 of 3) Format and Derivation of Object and Attributes Definition Value snmpOutNoSuchNames The total number of PDUs An integer set by the SNMP 1.3.6.1.2.1.11.21 generated for which the value of agent counter.
Page 112: Rfc Compliance
RFC 1213, Management Information Base for Network Management of TCP/IP-Based Internets: MIB-II. zagInternal Group The zagInternal group of the SNMP agent’s private MIB is defined by HP and provides information about the SNMP agent’s internal characteristics. The zagInternal group consists of objects in these four subgroups: zagInProcess objects, which describe the attributes of the SNMP agent’s process...
Page 113: Mib Objects
MIBs Supported by the SNMP Agent MIB Objects zagInProcMaxOpeners (11) zagInProcCurrentOpeners (12) zagInEndpoint (2) zagInEndpointTable (1) zagInEndpointEntry (1) zagInEpRowStatus (1) zagInEpName (2) zagInEpState (3) zagInEpHostAddr (4) zagInEpNetwork (5) zagInProfile (3) zagInProfileTable (1) zagInProfileEntry (1) zagInPfRowStatus (1) zagInPfName (2) zagInPfState (3) zagInPfHostAddr (4) zagInPfCommunity (5) zagInPfAccess (6)
Page 114: Table 3-3. Zaginternal Group Objects Supported By Snmp Agent
MIBs Supported by the SNMP Agent MIB Objects Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 1 of 8) Format and Derivation of Object and Attributes Definition Value zagInProcess Group Objects: Describe the attributes of the SNMP agent’s process.
Page 115 MIBs Supported by the SNMP Agent MIB Objects Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 2 of 8) Format and Derivation of Object and Attributes Definition Value zagInProcBkupPID A string that shows the The cpu,pin value is 1.3.6.1.4.1.169.3.155.1.7.1.6 backup process PID assigned by the RUN...
Page 116 MIBs Supported by the SNMP Agent MIB Objects Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 3 of 8) Format and Derivation of Object and Attributes Definition Value zagInProcMaxOpeners The maximum number of A numeric value assigned 1.3.6.1.4.1.169.3.155.1.7.1.11 subagent and SCF by the RUN command read-only...
Page 117 MIBs Supported by the SNMP Agent MIB Objects Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 4 of 8) Format and Derivation of Object and Attributes Definition Value zagInEpName The name assigned to $agentName. this endpoint. This object #endpointName 1.3.6.1.4.1.169.3.155.1.7.2.1.1.2 is created when the...
Page 118 MIBs Supported by the SNMP Agent MIB Objects Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 5 of 8) Format and Derivation of Object and Attributes Definition Value zagInProfile Group Objects: Define criteria that the SNMP agent uses to determine whether to accept or reject incoming requests from SNMP...
Page 119 MIBs Supported by the SNMP Agent MIB Objects Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 6 of 8) Format and Derivation of Object and Attributes Definition Value zagInPfState The current operational Possible states are: state of the profile. DEFINED (1) 1.3.6.1.4.1.169.3.155.1.7.3.1.1.3 STARTED (3)
Page 120 MIBs Supported by the SNMP Agent MIB Objects Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 7 of 8) Format and Derivation of Object and Attributes Definition Value zagInDirectedTrapdestName This object is used by The varbind value for this 1.3.6.1.4.1.169.3.155.1.7.4.1 the subagent to specify a object must be the name of...
Page 121 MIBs Supported by the SNMP Agent MIB Objects Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 8 of 8) Format and Derivation of Object and Attributes Definition Value zagInTdState The current operational One of these four numeric state of the trap state values, which can only 1.3.6.1.4.1.169.3.155.1.7.4.2.1.3 destination.
Page 122: Snmp Manager Access To Private Mib Objects
MIBs Supported by the SNMP Agent SNMP Manager Access to Private MIB Objects SNMP Manager Access to Private MIB Objects Table 3-4 identifies the objects in the SNMP agent’s private MIB that allow access (read-only or read-write) by SNMP management applications through the SNMP interface.
Page 123 MIBs Supported by the SNMP Agent SNMP Manager Access to Private MIB Objects Table 3-4. Access Status of SNMP Agent’s Private MIB Objects (page 2 of 3) Object Manager Object Name Syntax Access Description zagInEpState Integer read-only The operational state of the endpoint.
Page 124: Table Row Management Overview
MIBs Supported by the SNMP Agent Table Row Management Overview Table 3-4. Access Status of SNMP Agent’s Private MIB Objects (page 3 of 3) Object Manager Object Name Syntax Access Description zagInTdCommunity DisplayString read-write The name that the SNMP agent returns in traps sent to the trap destination.
Page 125: Table 3-5. Scf And Snmp Manager Access To Table Row Objects
MIBs Supported by the SNMP Agent Table Row Management Overview Table 3-5. SCF and SNMP Manager Access to Table Row Objects Accessible to SNMP Managers Through Accessible to SNMP Accessible TCP/IP’s UDP Managers Through Table Row Object From SCF Transport Protocol the IPC Interface zagInEndpointTable zagInEpRowStatus...
Page 126: Managing Table Rows From Snmp Managers
MIBs Supported by the SNMP Agent Managing Table Rows From SNMP Managers Managing Table Rows From SNMP Managers The zagInEndpointTable, zagInTrapdestTable, and zagInProfileTable in the SNMP agent’s private MIB contain entries that can be accessed by SNMP managers. The presence of a RowStatus object (zagInEpRowStatus, zagInTdRowStatus, and zagInPfRowStatus) with read-write access signifies that managers can add or delete entries in these tables.
Page 127 MIBs Supported by the SNMP Agent Managing Table Rows From SNMP Managers Table 3-6. RowStatus Value Definitions (page 2 of 2) RowStatus Value Value Type and Access Effect of RowStatus Value createAndGo (4) An action value that can only Is supplied in a Set command by the be written.
Page 128: Table 3-7. Rowstatus Values And Table Management Operations
MIBs Supported by the SNMP Agent Managing Table Rows From SNMP Managers Table 3-7. RowStatus Values and Table Management Operations (page 1 of 2) equivalent Set one of the command following row issued status objects against an (denoted in The row ENDPOINT, the next three state...
Page 129 MIBs Supported by the SNMP Agent Managing Table Rows From SNMP Managers Table 3-7. RowStatus Values and Table Management Operations (page 2 of 2) equivalent Set one of the command following row issued status objects against an (denoted in The row ENDPOINT, the next three state...
Page 130: Creating A Table Row
MIBs Supported by the SNMP Agent Creating a Table Row Creating a Table Row To create a table row, you need to supply the index value that uniquely identifies the new row. You can then build a Set operation message that contains: The object identifier (OID) for the RowStatus object of the row being created, appended by the unique index value (name) for the new row A RowStatus value that specifies either “createAndGo”...
Page 131: Default Values For Table Row Objects
MIBs Supported by the SNMP Agent Default Values for Table Row Objects Default Values for Table Row Objects Table 3-8 lists the default values for zagInEndpointTable and zagInTrapdestTable row objects. Table 3-8. ENDPOINT and TRAPDEST Default Values Table Row Object zagInEndpointTable zagInTrapdestTable zagInProfileTable...
Page 132: Deactivating Table Row Entries
MIBs Supported by the SNMP Agent Deactivating Table Row Entries Deactivating Table Row Entries To deactivate an entry, simply assign its RowStatus object a value of NotInService (2). Modifying Table Row Entries You can modify the value of an table row object only when its RowStatus is notInService (2) or notReady (3).
Page 133: Authentication Table Entries
MIBs Supported by the SNMP Agent Authentication Table Entries Authentication Table Entries The SNMP agent’s zagInProfile group objects define the authentication table entries to be used for authenticating requests received from managers that communicate with the SNMP agent through TCP/IP. (For information on how requests received through NonStop Kernel IPC calls are authenticated.
Page 134: Table 3-10. Initial Values Of Objects In The Snmp Agent's Mib
MIBs Supported by the SNMP Agent Authentication Table Entries Table 3-10. Initial Values of Objects in the SNMP Agent's MIB MIB Object Initial Value System group objects: sysDescr NonStop Kernel System Version: Dxx Node: node-name Agent: agent-process-name where Dxx is the product version of the SNMP agent; for example, D23.
Page 135 MIBs Supported by the SNMP Agent Authentication Table Entries Table 3-11. SNMP Agent Private MIB Objects That Describe the SNMP Operations Environment (page 2 of 4) SNMP Agent Private What the Object Defines and Its Equivalent SCF MIB Object Default Value Construct zagInEpName A name that serves as an index into...
Page 136 MIBs Supported by the SNMP Agent Authentication Table Entries Table 3-11. SNMP Agent Private MIB Objects That Describe the SNMP Operations Environment (page 3 of 4) SNMP Agent Private What the Object Defines and Its Equivalent SCF MIB Object Default Value Construct zagInTdHostAddr The Internet address of an SNMP...
Page 137 MIBs Supported by the SNMP Agent Authentication Table Entries Table 3-11. SNMP Agent Private MIB Objects That Describe the SNMP Operations Environment (page 4 of 4) SNMP Agent Private What the Object Defines and Its Equivalent SCF MIB Object Default Value Construct zagInPfName A name that serves as an index into...
Page 138 MIBs Supported by the SNMP Agent Authentication Table Entries You create, alter the attributes of, activate, inactivate, and remove rows in the SNMP agent’s private MIB zagInProfileTable to manage the authentication table entries that the SNMP agent uses for accepting or rejecting request messages received through TCP/IP.
Page 139 Part II. SCF for the SNMP Agent Part III consists of the following sections, which describe the Subsystem Control Facility (SCF) interface to the SNMP agent: Section 4 Introduction to SCF for the SNMP Agent Section 5 SCF Commands for the SNMP Agent SNMP Configuration and Management Manual—424777-006...
Page 140 Part II. SCF for the SNMP Agent SNMP Configuration and Management Manual—424777-006...
Page 141: Tasks You Can Perform With Scf
NonStop agent plays in such an environment SCF information specific to the NonStop agent For systems running a G-series RVU of the HP NonStop Kernel operating system, the SCF Reference Manual for G-Series Releases contains comprehensive reference material on SCF.
Page 142: Scf And The Dsm Family Of Products
SCF provides an operator interface to an intermediate process called the Subsystem Control Point (SCP). The SCP process is a network-management process that receives and distributes messages sent by SCF to HP subsystems. The SCP process provides the interface between SCF and the NonStop agent, as Figure 4-1 illustrates.
Page 143: Objects
Objects Objects In HP systems, a subsystem is represented as a collection of objects that describe a set of services or resources. An object is a distinct entity that management software can query and control. Objects might represent real resources or a relationship between resources.
Page 144: Object Hierarchy
Introduction to SCF for the SNMP Agent Object Hierarchy For the required syntax for each attribute name and value valid for NonStop agent objects, see the individual commands in Section 5, SCF Commands for the SNMP Agent. Object Hierarchy Most subsystems are structured hierarchically, with a group of objects of one type logically subordinate to an object of another type.
Page 145: The Process Object
The PROCESS Object The PROCESS Object The PROCESS object represents a NonStop agent process running on an HP system. The NonStop agent process authenticates SNMP requests from managers, processes them or forwards them to appropriate subagents, and returns responses to the manager from which the request originated.
Page 146: Process Object States
Introduction to SCF for the SNMP Agent PROCESS Object States The associated PROCESS object is named $ZSNMP. Note. For information on NonStop agent process startup parameters, see the Section 2, Installing and Configuring the SNMP Agent. The syntax for specifying a PROCESS object in SCF commands: command PROCESS $agent-process Wildcard Support: PROCESS Object The use of the asterisk (*) as a wildcard is not supported for the PROCESS object.
Page 147: Figure 4-4. Process Object State Transition Sequence
Introduction to SCF for the SNMP Agent Default PROCESS Object Figure 4-4. PROCESS Object State Transition Sequence SNMP agent process not running ALTER, INFO, NAMES, STATUS, TRACE, VERSION PROCESS "Expecting an existing SCF supported object name" TACL> RUN SNMPAGT /NAME $ZSNMP, ... / STARTING SNMP agent process completes initialization tasks.
Page 148: The Endpoint Object
Introduction to SCF for the SNMP Agent The ENDPOINT Object The ENDPOINT Object The ENDPOINT object type represents a network interface the NonStop agent process uses to accept manager requests and return responses. The attributes of the ENDPOINT object identify: The name of the TCP/IP process through which the NonStop agent can be reached by other entities on the network (NETWORK attribute) The Internet addresses (TCP/IP subnet addresses) by which the NonStop agent is...
Page 149: Endpoint Object States
Introduction to SCF for the SNMP Agent ENDPOINT Object States The logical identifier consists of an alphabetic character followed by up to six additional alphanumeric characters. For example: $ZSNMP.#END1 In the SCF command syntax descriptions, the logical identifier associated with a request/response connection is referred to as its endpoint-name.
Page 150: Endpoint Object Attributes
Introduction to SCF for the SNMP Agent ENDPOINT Object Attributes Table 4-2. ENDPOINT Object States State Description DEFINED The ENDPOINT object has been configured with the SCF ADD command but has not been initially activated for use in the NonStop agent operations environment.
Page 151: Figure 4-6. Endpoint Object State Transition Sequence
Introduction to SCF for the SNMP Agent Default ENDPOINT Object Figure 4-6. ENDPOINT Object State Transition Sequence No definition for this object exists ABORT, ALTER, DELETE, INFO, START, STATUS or STOP ENDPOINT "Object Not Found" Error ADD ENDPOINT ABORT/STOP DELETE DEFINED ENDPOINT ENDPOINT...
Page 152: The Profile Object
Introduction to SCF for the SNMP Agent The PROFILE Object The PROFILE Object The PROFILE object type represents an entry in the authentication table which the NonStop agent process consults to determine whether to accept an incoming request. The attributes of the PROFILE object type define the contents of the following table entry fields: Community name (COMMUNITY attribute) Internet address (HOSTADDR attribute)
Page 153: Figure 4-7. The Profile Object
Introduction to SCF for the SNMP Agent Naming Conventions: PROFILE Object Figure 4-7. The PROFILE Object Authentication Table Entry Entry Subagent SNMP Agent EMS Collector TCP/IP Managed Resources #su01 #su02 SNMP Manager VST010.vsd Wildcard Support: PROFILE Object The use of the asterisk (*) as a wildcard is supported in PROFILE object name specifications for the following commands: ABORT INFO...
Page 154: Profile Object States
Introduction to SCF for the SNMP Agent PROFILE Object States PROFILE Object States The PROFILE object is always in one of the DEFINED, STARTED, or STOPPED states. Table 4-3 describes the states supported for the PROFILE object: Table 4-3. PROFILE Object States State Description DEFINED...
Page 155: Figure 4-8. Profile Object State Transition Sequence
Introduction to SCF for the SNMP Agent Default PROFILE Object Figure 4-8. PROFILE Object State Transition Sequence No definition for this object exists. ABORT, ALTER, DELETE, INFO, START, STATUS or STOP PROFILE "Object Not Found" Error ADD PROFILE ABORT/ DELETE DEFINED STOP PROFILE...
Page 156: The Trapdest Object
Introduction to SCF for the SNMP Agent The TRAPDEST Object The TRAPDEST Object The TRAPDEST object type represents a manager to which the NonStop agent process can send trap messages. The attributes of the TRAPDEST object identify: The TCP/IP process that the NonStop agent process uses to send traps (NETWORK attribute) The community name that the NonStop agent includes in traps it generates (COMMUNITY attribute)
Page 157: Trapdest Object States
Introduction to SCF for the SNMP Agent TRAPDEST Object States A pound sign (#) A logical identifier representing the TRAPDEST object definition The logical identifier consists of an alphabetic character followed by up to six additional alphanumeric characters. For example: $ZSNMP.#TRAP1 In the SCF command syntax descriptions, the logical identifier associated with a trap destination configuration is referred to as its trapdest-name.
Page 158: Trapdest Object Attributes
Introduction to SCF for the SNMP Agent TRAPDEST Object Attributes Table 4-4. TRAPDEST Object States State Description DEFINED The TRAPDEST object has been configured with the SCF ADD command, but has not been initially activated for use in the NonStop agent operations environment.
Page 159: Scf-Configured Trap Destination Limitations: Broadcast Only
Introduction to SCF for the SNMP Agent SCF-Configured Trap Destination Limitations: Broadcast Only Then, if the NonStop agent receives a request from the manager at Internet address “155.186.130.123,” it creates and starts another TRAPDEST object: TRAPDEST $agent-process.#DYNA1, COMMUNITY "Tandem", NETWORK $ZTC0, HOSTADDR "155.186.130.123" Dynamic TRAPDEST generation continues until you either: ADD a TRAPDEST object (or create one through SNMP).
Page 160: Figure 4-10. Trapdest Object State Transition Sequence
Introduction to SCF for the SNMP Agent SCF-Configured Trap Destination Limitations: Broadcast Only Figure 4-10. TRAPDEST Object State Transition Sequence No definition for this objectexists. ABORT, ALTER, DELETE, INFO, START, STATUS or STOP TRAPDEST "Object Not Found" Error ADD TRAPDEST DELETE ABORT/STOP DEFINED...
Page 161: Running Scf
At the beginning of an SCF session, SCF displays its product banner. The product banner includes the HP product name, product number, version number, release date, and copyright statement. SCF indicates it is ready to process commands by displaying its prompt (->). You can change this prompt with the SETPROMPT command.
Page 162: Scf Commands For Managing A Subsystem
Introduction to SCF for the SNMP Agent SCF Commands for Managing a Subsystem Examples of other SCF commands that pertain only to the current SCF session: The SYSTEM and VOLUME commands identify the default system, volume, and subvolume names used for expanding file names. The OBEY and OUT commands identify the files used for command input and display output.
Page 163: Sensitive And Nonsensitive Commands
Introduction to SCF for the SNMP Agent Sensitive and Nonsensitive Commands The TRACE command, which traces the operation of an object according to selection criteria you specify and stores the trace information in a trace file. Sensitive and Nonsensitive Commands SCF commands fall into two categories—sensitive and nonsensitive: A sensitive command can have detrimental effects if improperly used.
Page 164: Directing Output To A File
Introduction to SCF for the SNMP Agent Directing Output to a File Directing Output to a File To direct output of all SCF commands to a disk file, application process, terminal, or printer, include after the command keyword: /OUT file-spec/ where file-spec is the file to which the output listing is to be written.
Page 165: Displaying Help For Scf Error Messages
The NonStop agent provides the means by which HP customers operating multiplatform networks can have HP subsystems managed from SNMP-compliant network managers. The SNMP agent that HP provides is referred to as the NonStop agent. The NonStop agent interacts with subagents that reside on the same or remote NonStop systems.
Page 166: The Scf Product Module For The Nonstop Agent
2-17. Note. Currently, subagents are not configured through SCF. They are configured through startup parameters as well as through SNMP requests issued by SNMP managers. For configuration of SNMP subagents that HP supports, see the Part IV, SNMP Subagents.
Page 167: Scf Configuration And The Tcpip^process^name Startup Parameter
Introduction to SCF for the SNMP Agent SCF Configuration and the TCPIP^PROCESS^NAME Startup Parameter SCF Configuration and the TCPIP^PROCESS^NAME Startup Parameter The NonStop agent has a startup parameter—TCPIP^PROCESS^NAME—that allows you to specify the TCP/IP process to be used as the default value for the NETWORK attribute when ENDPOINT and TRAPDEST objects are created.
Page 168 Introduction to SCF for the SNMP Agent SCF Configuration and the TCPIP^PROCESS^NAME Startup Parameter SNMP Configuration and Management Manual—424777-006 4- 28...
Page 169: Table 5-1. Summary Of Scf Commands Supported For Nonstop Agent Objects
SCF Commands for the SNMP Agent This section describes the SCF commands with which you manage a NonStop agent configuration. The supported commands are: ABORT Command on page 5-3 ADD Command on page 5-5 DELETE Command on page 5-19 INFO Command on page 5-21 NAMES Command on page 5-25...
Page 170: Scf Commands For The Snmp Agent
SCF Commands for the SNMP Agent Configuration Restrictions: Attribute Conflicts SCF commands for controlling your SCF session, such as the ASSUME and ENV commands, are not documented in this section. The SCF Reference Manual for G- Series Releases provides information about general SCF commands. In the following syntax diagrams, remember that if you set a default PROCESS with the ASSUME PROCESS command, you can omit the NonStop agent process name and period and just specify #object-name.
Page 171: Abort Command
SCF Commands for the SNMP Agent ABORT Command ABORT Command The ABORT command: Inactivates an object definition in the current NonStop agent configuration Behaves the same way as the STOP command for NonStop agent objects Is not valid for the PROCESS object Is a sensitive command ABORT ENDPOINT Command Use the ABORT ENDPOINT command to inactivate a request/response connection...
Page 172: Abort Profile Command
SCF Commands for the SNMP Agent ABORT PROFILE Command Considerations: ABORT ENDPOINT When you ABORT an ENDPOINT object, you only affect the availability of the TCP/IP subnets for handling communication between the NonStop agent and managers. The TCP/IP process and subnets are still available for handling communication between other entities.
Page 173: Abort Trapdest Command
SCF Commands for the SNMP Agent ABORT TRAPDEST Command Example: ABORT PROFILE The following example inactivates an entry in the authentication table used by NonStop agent process $ZSNMP: -> ABORT PROFILE $ZSNMP.#LANMGR ABORT TRAPDEST Command Use the ABORT TRAPDEST command to disable the sending of trap messages to a specific trap destination.
Page 174: Add Endpoint Command
SCF Commands for the SNMP Agent ADD ENDPOINT Command ADD ENDPOINT Command Use the ADD ENDPOINT command to define a request/response connection between a NonStop agent process and managers. ADD ENDPOINT [$agent-process.]#endpoint-name [ , NETWORK [\node.]$tcpip-process ] [ , HOSTADDR "ip-address"] [$agent-process.]#endpoint-name identifies the request/response connection being defined.
Page 175 SCF Commands for the SNMP Agent ADD ENDPOINT Command The default (“0.0.0.0”) indicates that the NonStop agent accepts requests from and returns responses through any available TCP/IP subnet defined for the specified TCP/IP process. Considerations: ADD ENDPOINT The TCP/IP process specified in the NETWORK attribute does not have to be on the same node as the NonStop agent process.
Page 176: Add Profile Command
SCF Commands for the SNMP Agent ADD PROFILE Command ADD PROFILE Command Use the ADD PROFILE command to define an authentication table entry. ADD PROFILE [$agent-process.]#profile-name [ , COMMUNITY "community-name" ] [ , HOSTADDR "ip-address"] [ , ACCESS { READONLY | READWRITE } ] [$agent-process.]#profile-name identifies the authentication table entry being defined.
Page 177 SCF Commands for the SNMP Agent ADD PROFILE Command ACCESS { READONLY | READWRITE } specifies the level of authority of an associated community to retrieve and alter network management information: READONLY The NonStop agent accepts Get and GetNext requests from the associated community.
Page 178: Add Trapdest Command
SCF Commands for the SNMP Agent ADD TRAPDEST Command Examples: ADD PROFILE The following example configures and activates an entry in the authentication table that directs the NonStop agent to process SNMP Set, Get, and GetNext requests from the manager at Internet address “130.252.86.10” sent under the “Private” community: ->...
Page 179 SCF Commands for the SNMP Agent ADD TRAPDEST Command COMMUNITY "community-name" specifies the community name included in trap messages sent to the associated manager. "community-name" is a case-sensitive 1 to 50 character enclosed string within quotation marks. The default is “Tandem.” NETWORK [\node.]$tcpip-process specifies the TCP/IP process handling the sending of trap messages by the NonStop agent process to the manager.
Page 180 SCF Commands for the SNMP Agent ADD TRAPDEST Command Trap destinations created with SCF are only of type broadcast. The SCF interface does not provide a means of creating directed trap destinations. However, a manager can change the type of a trap destination defined through SCF from type broadcast to type directed.
Page 181: Alter Command
SCF Commands for the SNMP Agent ALTER Command Examples: ADD TRAPDEST The following example tells the NonStop agent to send trap messages to the manager at Internet address “130.252.86.10.” The NonStop agent includes the community string “Public” in all trap messages it sends to this address. This example does not include the NETWORK attribute keyword and value because it is using the default $ZTC0: ->...
Page 182 SCF Commands for the SNMP Agent ALTER ENDPOINT Command NETWORK [\node.]$tcpip-process identifies the TCP/IP process handling communication between the NonStop agent process and managers for the receiving and sending of SNMP request/response messages. $tcpip-process is from one to five alphanumeric characters preceded by a dollar sign ($).
Page 183: Alter Process Command
SCF Commands for the SNMP Agent ALTER PROCESS Command ALTER PROCESS Command Use the ALTER PROCESS command to direct the NonStop agent process to send its event messages to a different EMS collector process. ALTER PROCESS $agent-process [ , EMSCOLL [\node.]$ems-collector ] $agent-process identifies the NonStop agent process whose configuration is being altered.
Page 184: Alter Profile Command
SCF Commands for the SNMP Agent ALTER PROFILE Command Example: ALTER PROCESS The following example tells the NonStop agent process $ZSNMP to send event messages it generates to EMS collector process $A0: -> ALTER PROCESS $ZSNMP, EMSCOLL $A0 ALTER PROFILE Command Use the ALTER PROFILE command to change an entry in the authentication table.
Page 185: Alter Trapdest Command
SCF Commands for the SNMP Agent ALTER TRAPDEST Command ACCESS { READONLY | READWRITE } specifies the level of authority of an associated community to retrieve and alter network management information as follows: READONLY The NonStop agent accepts Get and GetNext requests from the associated community.
Page 186 SCF Commands for the SNMP Agent ALTER TRAPDEST Command #trapdest-name identifies the TRAPDEST object. It consists of a pound sign (#) followed by one to seven alphanumeric characters, the first of which must be alphabetic. COMMUNITY "community-name" specifies the community name included in trap messages sent to the associated manager.
Page 187: Delete Command
SCF Commands for the SNMP Agent DELETE Command DELETE Command The DELETE command: Removes an object definition from a NonStop agent configuration Can be issued only against an object in the STOPPED or DEFINED state Is not valid for the PROCESS object Is a sensitive command DELETE ENDPOINT Command Use the DELETE ENDPOINT command to remove a request/response connection...
Page 188: Delete Trapdest Command
SCF Commands for the SNMP Agent DELETE TRAPDEST Command $agent-process identifies the NonStop agent process to which the PROFILE object belongs. It consists of a dollar sign ($) followed by one to five alphanumeric characters, the first of which must be alphabetic. #profile-name identifies the PROFILE object.
Page 189: Info Command
SCF Commands for the SNMP Agent INFO Command INFO Command The INFO command: Displays the current attribute values of an object Indicates with an asterisk attributes whose values can be changed with the ALTER command Is a nonsensitive command INFO ENDPOINT Command Use the INFO ENDPOINT command to display the current attribute values for a request/response connection definition.
Page 190: Info Process Command
SCF Commands for the SNMP Agent INFO PROCESS Command INFO PROCESS Command Use the INFO PROCESS command to display the current attribute values for a NonStop agent process and its defined objects. INFO PROCESS $agent-process [, SUB [ NONE | ALL | ONLY ] ] [, DETAIL ] } $agent-process identifies the NonStop agent process whose configuration you want to display.
Page 191: Info Profile Command
SCF Commands for the SNMP Agent INFO PROFILE Command SNMP Info PROFILE Name *Access *Hostaddr *Community $ZSNMP.#DEFAULT READONLY 0.0.0.0 public $ZSNMP.#LANMGR READWRITE 130.252.86.10 Private SNMP Info ENDPOINT Name *Network *Hostaddr $ZSNMP.#DEFAULT \EAST.$ZTC0 0.0.0.0 $ZSNMP.#REMOTE \WEST.$ZTC0 0.0.0.0 SNMP Info TRAPDEST Name *Network *Hostaddr *Community...
Page 192: Info Trapdest Command
SCF Commands for the SNMP Agent INFO TRAPDEST Command Example: INFO PROFILE The following example displays the attribute values of all the entries in the authentication table used by NonStop agent process $ZSNMP: -> INFO PROFILE $ZSNMP.* SNMP Info PROFILE Name *Access *Hostaddr...
Page 193: Names Command
SCF Commands for the SNMP Agent NAMES Command NAMES Command The NAMES command: Lists the names of the objects in a NonStop agent configuration Is a nonsensitive command NAMES [ PROCESS ] $agent-process [, SUB [ NONE | ALL | ONLY ] $agent-process identifies the NonStop agent process whose defined objects you want to list.
Page 194: Start Command
SCF Commands for the SNMP Agent START Command START Command The START command: Activates an object in a NonStop agent configuration Is not valid for the PROCESS object Is a sensitive command START ENDPOINT Command Use the START ENDPOINT command to activate a request/response connection. START ENDPOINT [$agent-process.]#endpoint-name [$agent-process.]#endpoint-name identifies the request/response connection to activate.
Page 195: Start Trapdest Command
SCF Commands for the SNMP Agent START TRAPDEST Command [$agent-process.]#endpoint-name identifies the authentication table entry to activate. $agent-process identifies the NonStop agent process to which the PROFILE object belongs. It consists of a dollar sign ($) followed by one to five alphanumeric characters, the first of which must be alphabetic.
Page 196: Status Command
SCF Commands for the SNMP Agent STATUS Command Every time the NonStop agent generates a trap or receives a trap for forwarding from a subagent, it attempts to reconnect. If the reconnection is successful, the TRAPDEST object enters the STARTED state. Example: START TRAPDEST The following example activates the sending of traps to all trap destinations defined for the NonStop agent process $ZSNMP:...
Page 197: Status Process Command
SCF Commands for the SNMP Agent STATUS PROCESS Command If the ENDPOINT object is in the STARTING state because an underlying resource is unavailable, the NonStop agent periodically tries to access the resource. Once the resource is available, the ENDPOINT object enters the STARTED state. A returned status of STOPPING indicates that a STOP or ABORT command was issued while the NonStop agent was processing an SNMP request.
Page 198: Status Profile Command
SCF Commands for the SNMP Agent STATUS PROFILE Command Considerations: STATUS PROCESS The NonStop agent process is always reported as being in the STARTED state. If the NonStop agent process has been stopped, the following message returns when you issue a STATUS PROCESS command: Expecting an existing SCF supported object name Example: STATUS PROCESS The following example displays the operational states for all objects defined for...
Page 199: Status Trapdest Command
SCF Commands for the SNMP Agent STATUS TRAPDEST Command $agent-process identifies the NonStop agent process to which the PROFILE object belongs. It consists of a dollar sign ($) followed by one to five alphanumeric characters, the first of which must be alphabetic. #profile-name identifies the PROFILE object.
Page 200: Stop Command
SCF Commands for the SNMP Agent STOP Command #trapdest-name identifies the TRAPDEST object. It consists of a pound sign (#) followed by one to seven alphanumeric characters, the first of which must be alphabetic. Considerations: STATUS TRAPDEST The returned state only gives you information about the ability of the NonStop agent to send trap messages to the associated manager;...
Page 201: Stop Endpoint Command
SCF Commands for the SNMP Agent STOP ENDPOINT Command STOP ENDPOINT Command Use the STOP ENDPOINT command to inactivate a request/response connection between a NonStop agent process and managers. STOP ENDPOINT [$agent-process.]#endpoint-name [$agent-process.]#endpoint-name identifies the request/response connection being inactivated. $agent-process identifies the NonStop agent process to which the ENDPOINT object belongs.
Page 202: Stop Trapdest Command
SCF Commands for the SNMP Agent STOP TRAPDEST Command $agent-process identifies the NonStop agent process to which the PROFILE object belongs. It consists of a dollar sign ($) followed by one to five alphanumeric characters, the first of which must be alphabetic. #profile-name identifies the PROFILE object.
Page 203: Trace Command
SCF Commands for the SNMP Agent TRACE Command Example: STOP TRAPDEST The following example disables the sending of trap messages by NonStop agent process $ZSNMP to all its dynamically generated trap destinations: -> STOP TRAPDEST $ZSNMP.DYNA* TRACE Command The TRACE command: Starts a trace operation on a NonStop agent process Alters trace parameters set by a previous TRACE command Stops a previously requested trace operation...
Page 204 SCF Commands for the SNMP Agent TRACE Command PAGES pages designates how much memory space, in units of 2048-byte pages, is allocated in the extended data segment used for tracing. PAGES can be specified only when a trace is being initiated, not when its parameters are being modified. pages is an integer in the range 4 through 32767 or is equal to 0.
Page 205: Version Command
SCF Commands for the SNMP Agent VERSION Command While being traced, the NonStop agent process continues normal operation. However, during its operation, the NonStop agent process also collects all trace information that meets the selection criteria specified in the TRACE command and passes it to a trace procedure.
Page 206 SCF Commands for the SNMP Agent VERSION Command $agent-process identifies the NonStop agent process whose version information you want to display. It consists of a dollar sign ($) followed by one to five alphanumeric characters, the first of which must be alphabetic. DETAIL specifies that complete version information be returned.
Page 207: Part Iii. Troubleshooting
Part III. Troubleshooting Part IV consists of the following sections, which provide diagnostic information: Section 6 SNMP Agent PTrace Facility Section 7 Troubleshooting the SNMP Agent SNMP Configuration and Management Manual—424777-006...
Page 208 Part III. Troubleshooting SNMP Configuration and Management Manual—424777-006...
Page 209: Snmp Agent Ptrace Facility
SNMP Agent PTrace Facility This section contains the following information: An introduction to the NonStop agent trace facility and the PTrace utility A description of the subsystem-specific PTrace commands and special considerations for using these commands with the NonStop agent How the PTrace utility determines the subsystem for which it is formatting records How to establish selection criteria for displaying NonStop agent records Examples of NonStop agent formatted trace record displays...
Page 210: Figure 6-1. Recording And Displaying Trace Data
SNMP Agent PTrace Facility Introduction to PTrace Figure 6-1. Recording and Displaying Trace Data Start the trace interactively by using the SCF TRACE command Collect the trace data. Stop the trace by using the SCF TRACE command. Display the trace file by using PTrace.
Page 211: Running Ptrace
SNMP Agent PTrace Facility Running PTrace Running PTrace Although the PTrace Reference Manual covers this subject in more detail, the descriptions that follow should be enough to get you started running PTrace. Starting a Noninteractive PTrace Session The syntax of the TACL or SCF RUN command for PTrace is: PTRACE [ /run-option-list ] [ ptrace-command ] ...
Page 212: Starting An Interactive Ptrace Session
SNMP Agent PTrace Facility Starting an Interactive PTrace Session ptrace-command is a PTrace command that is to be executed immediately after PTrace is initiated (such as the SELECT command, described on 6-10). If you specify one or more PTrace commands in the RUN command, PTrace executes the commands and then issues its prompt.
Page 213: Ptrace Commands Supported By The Nonstop Agent
SNMP Agent PTrace Facility PTrace Commands Supported by the NonStop Agent PTrace Commands Supported by the NonStop Agent The PTrace code consists of two modules. The first module contains the code shared by all subsystems. The second contains the additional, subsystem-specific code that actually displays the PTrace records.
Page 214: From Command
SNMP Agent PTrace Facility FROM Command Table 6-1. Summary of NonStop SNMP Agent PTrace Commands (page 2 of 2) Command Description NEXT Specifies the number of records or specifies a time after which records are to be displayed or printed RECORD Displays or prints record(s) within the specified range or prints all records SELECT...
Page 215: Next Command
SNMP Agent PTrace Facility NEXT Command Considerations: PTrace FROM Command The FROM command resets current session parameters to their default values. For more information, see the RESET Command in the PTrace Reference Manual. The FROM command resets current SELECT options to their default values if the device type and subtype of the new trace file are different from the last trace file.
Page 216 Considerations: PTrace NEXT Command Pressing the BREAK key terminates the NEXT command search or display. The function keys on an HP 6530 terminal can be used as shorthand for various NEXT count commands. For example, pressing the F6 function key displays six records.
Page 217: Record Command
SNMP Agent PTrace Facility RECORD Command 2. This example displays the next two records whose timestamp is greater than the timestamp specified in the command. ?NEXT 2 AFTER 11/19/1997 11:27:52 11:27:52.230 >001.060 #680 Method Function name: SnmpAgent_Thread Thread name: SnmpAgent ID:1 Method class: SnmpAgent...
Page 218: Select Command
SNMP Agent PTrace Facility SELECT Command Examples: PTrace RECORD Command 1. The following example displays record 18: ?RECORD 18 11:27:51.290 >000.000 #18 Method Function name: dictionary_KeySearch Thread name: ID:0 Method class: dictionary Method name: KeySearch Object Count:2 Object: dictionary Object ADDR:612610D Object: UNKNOWN Object ADDR:612562D...
Page 219: Table 6-2. Keywords For Nonstop Snmp Agent Ptrace Select Command
SNMP Agent PTrace Facility SELECT Command CURRENT selects the currently defined trace-selection options. number is an integer that specifies an enumerated value corresponding to a specific keyword. number can be specified in decimal, octal, hexadecimal, or binary notation. When you specify number, it is saved as an enumerated value. The formats and ranges follow: decimal: 0 - 32767...
Page 220 SNMP Agent PTrace Facility SELECT Command 2. The next example selects the trace records written by the NonStop agent and then displays the next two records: ?SELECT METHOD Ptrace Select Key: ?NEXT 2 11:27:50.760 >000.000 #2 Method 11:27:50.760 >000.000 #3 Method 3.
Page 221: Troubleshooting The Snmp Agent
Troubleshooting Strategy Because of the interaction between the agent process, the subagents with which it communicates, the HP TCP/IP subsystem, and the underlying LAN access and X25AM subsystems, it might be difficult to determine whether problems arose within the SNMP agent or one of the resources it uses.
Page 222: Identifying Unavailable Resources
Troubleshooting the SNMP Agent Identifying Unavailable Resources If any of the underlying resources used by the SNMP agent are not running, an SCF error and corresponding event messages are generated. Identifying Unavailable Resources You can display the current operational states of the SNMP agent resources by either: Issuing an SCF STATUS command against SNMP agent PROFILE, ENDPOINT, and TRAPDEST objects Issuing Get requests from an SNMP manager against SNMP agent private...
Page 223: Creating A Filter
Troubleshooting the SNMP Agent Creating a Filter messages or groups of messages of special interest. For example, you might want to select all the messages sent by the SNMP agent and TCP/IP. The filtered event stream can be viewed several ways: Running a printing distributor.
Page 224: Compiling The Filter
Break key and then use a TACL STOP $DIST1 command. Using Trace Records The SNMP agent and the HP TCP/IP subsystem both provide a facility for generating trace records to help you diagnose problems. While being traced, subsystems continue normal operation but pass all message traffic to a trace procedure.
Page 225: Tcp/Ip
TCP/IP TCP/IP For the HP TCP/IP subsystem, you can use the PTrace utility to format, display, and examine the trace information collected by the TRACE command. You can limit the information you format by using the options provided in the PTrace SELECT and FILTER commands.
Page 226: Diagnosing Request Errors
Troubleshooting the SNMP Agent Diagnosing Request Errors which the agent process was started. To override the default trace files, you must provide DEFINE statements specifying the locations of the primary and backup trace files. For example: ADD DEFINE =PRIMARY-TRACE-FILE, CLASS MAP, FILE $NETMAN.SNMP.SNMPTRCP ADD DEFINE =BACKUP-TRACE-FILE, CLASS MAP, FILE $NETMAN.SNMP.SNMPTRCB Using DEFINE statements is described in the TACL Reference Manual.
Page 227 Depends on how receives a the subagent is GetRequest PDU implemented. The for an object that TCP/IP Subagent, HP does not for example, returns support. a null or a 0, depending on whether the object is a string or a counter.
Page 228 Troubleshooting the SNMP Agent Diagnosing Request Errors Table 7-1. Handling Requests That Cannot Be Processed (page 3 of 3) Error-Status SNMP Group Counter Value Error Condition Incremented Assigned Message Handling A SetRequest snmpOutBadValues badValue SNMP agent stops PDU attempts to processing the assign an invalid request.
Page 229: Part Iv. Snmp Subagents
Part IV. SNMP Subagents Part II consists of the following sections, which describe the SNMP subagents: Section 8 TCP/IP Subagent Section 9 EMS Trap Subagent Section 10 NonStop NET/MASTER Trap Subagent Section11 Host Resources Subagent Section12 Trap Multiplexer Subagent/Manager Section13 IPX/SPX Subagent (G-Series) Section14 Ethernet Subagent...
Page 230 Part IV. SNMP Subagents SNMP Configuration and Management Manual—424777-006...
Page 231: Tcp/Ip Subagent
(including Parallel Library TCP/IP, and NonStop TCP/IPv6) on NonStop systems to be managed from SNMP managers. It also supports additional private MIB objects defined by HP that let you monitor and manage the subagent itself. This section describes the TCP/IP Subagent and the MIBs it supports.
Page 232: Figure 8-1. Architectural Overview Of The Tcp/Ip Subagent
Most of the information in the MIB-II groups as supported by the TCP/IP Subagent describe the HP TCP/IP subsystem and, if the interface is the ServerNet LAN Systems Access (which supports parallel LAN I/O in a G-series or H-series ServerNet based system), the underlying SLSA subsystem.
Page 233: Figure 8-2. Tcp/Ip Subagent Scenarios
TCP/IP Subagent Architectural Overview Figure 8-2. TCP/IP Subagent Scenarios NonStop Server NonStop Servers TCP/IP TCP/IP SNMP SNMP Subagent Subagent Agent Agent TCP/IP TCP/IP TCP/IP TCP/IP Subsystem Subsystem Subsystem Subsystem SNMP SNMP Manager Manager NonStop Server NonStop Servers TCP/IP TCP/IP SNMP SNMP Subagent Subagent...
Page 234: The Tcp/Ip Subagent And Its Managed Resources
The TCP/IP Subagent and Its Managed Resources The TCP/IP Subagent and Its Managed Resources Each TCP/IP Subagent manages only one HP TCP/IP subsystem. The TCP/IP resources being managed by the TCP/IP Subagent must reside on the same node as the TCP/IP Subagent. The TCP/IP Subagent can monitor the same TCP/IP resources that the SNMP agent is using to communicate with SNMP managers.
Page 235: The Nonstop Tcp/Ipv6 Subagent And Its Managed Resources
TCP/IP Subagent The NonStop TCP/IPv6 Subagent and its Managed Resources The NonStop TCP/IPv6 Subagent and its Managed Resources To run SNMP over TCP/IPv6, you must define the name of a TCP6SAM process. You can find this process by issuing a LISTDEV TCPIP command to find a process whose program name ends in TCP6SAM.
Page 236 TCP/IP Subagent Standard MIB-II Groups Supported by the TCP/IP Subagent The objects in these groups are described in the subsections dedicated to each supported MIB-II group later in this section. SNMP Configuration and Management Manual—424777-006 8 -6...
Page 237: Private Mib Objects Supported By The Tcp/Ip Subagent
Name of the subnets associated with the TCP/IP subsystem Status of the subnets IP address of the subnets These private MIB objects are defined by HP and reside in the ztsa subtree within the nonstopsystems subtree registered to HP: iso (1)
Page 238: Unavailable Resources
Reporting Values for Uninstrumented Objects When it receives a request against objects for which there is no HP instrumentation, the TCP/IP Subagent returns the following values: A zero (0) for Get and GetNext requests against unsupported MIB objects defined...
Page 239: Refreshing Mib Values
MIB Objects Supported by the TCP/IP Subagent, on page 8-21. Note. HP does not recommend disabling cache timers (by setting their values to 0). If one timer is set to 0, set all timers to 0 for consistency. The Information Cache Refresh Timer The information cache or “info cache”...
Page 240: Initiating Backup Process Takeover
TCP/IP Subagent Initiating Backup Process Takeover The Statistics Cache Refresh Timer The statistics cache or “stats cache” timer controls the rate at which the TCP/IP Subagent updates values of objects that it retrieves by issuing a SPI STATISTICS command. Statistical data is relatively volatile. The stats cache timer is initially set with the -stats startup parameter and can be managed through SNMP by setting the ztsaStatsCache object.
Page 241: Related Documents
RFC1213, Management Information Base for Network Management of TCP/IP- Based Internets: MIB-II, contains definitions for the MIB-II objects. The ZTSAMIB file contains definitions for the private TCP/IP Subagent MIB objects defined by HP. SNMP Configuration and Management Manual—424777-006 8- 11...
Page 242: Before Starting The Tcp/Ip Subagent
SNMP agent at the rate specified in its ztsakeepAliveTimer object. In addition, for the TCP/IP Subagent to communicate with a HP TCP/IP subsystem, the SCP process ($ZNET, or the SCP process specified for the -scp startup parameter) must be running.
Page 243 TACL RUN command options. Refer to the TACL Reference Manual for more information about these options. HP recommends using at least the NOWAIT option so that you can resume TACL operations once the subagent is started.
Page 244 TCP/IP Subagent Starting the TCP/IP Subagent -a [\node.]$agent-process is the name of the SNMP agent process with which you want the TCP/IP Subagent to communicate. The default value is $ZSNMP on the same node as the subagent. -b backup-cpu-number is the processor number in which a backup process is to be created. The default value is -1, indicating that no backup is to be created.
Page 245 TCP/IP Subagent Starting the TCP/IP Subagent Users of the -s option can monitor only a the following private MIB objects for information about subnets of the TCP/IP processes: TCPIP process name, TCPIPstatus, subnet name, subnet status, and subnet address. Users cannot monitor all MIB-II entries of the TCP/IP processes.
Page 246: Stopping The Tcp/Ip Subagent
TCP/IP Subagent Stopping the TCP/IP Subagent Configuration and Management Manual for more information about Parallel Library TCP/IP. For more information about NonStop TCPIPv6, see the TCP/IPv6 Configuration and Management Manual. Stopping the TCP/IP Subagent Issue a TACL STOP command to stop a TCP/IP Subagent process. For example: STOP $ZTSA Configuring a Running TCP/IP Subagent Once a TCP/IP Subagent is running, you can issue SNMP Get and Set requests from...
Page 247: Controlling A Running Tcp/Ip Subagent
TCP/IP Subagent Controlling a Running TCP/IP Subagent Table 8-1. Querying a TCP/IP Subagent Through SNMP (page 2 of 2) By issuing an SNMP Get request against You can find out this about the TCP/IP Subagent... this ztsa object... Rate at which SPI INFO based object values are refreshed ztsaInfoCache TCP/IP process being monitored ztsaTcpIpProcess...
Page 248: Table 8-2. Controlling A Tcp/Ip Subagent Through Snmp
TCP/IP Subagent Controlling a Running TCP/IP Subagent Table 8-2. Controlling a TCP/IP Subagent Through SNMP (page 1 of 2) Initially You can control By issuing SNMP Set set with this this attribute of a requests against this startup TCP/IP Subagent... ztsa object...
Page 249 TCP/IP Subagent Controlling a Running TCP/IP Subagent Table 8-2. Controlling a TCP/IP Subagent Through SNMP (page 2 of 2) Initially You can control By issuing SNMP Set set with this this attribute of a requests against this startup TCP/IP Subagent... ztsa object...
Page 250: Ztsa Mib Objects
TCP/IP Subagent ZTSA MIB Objects ZTSA MIB Objects The following collection of scalar objects in the ztsa subtree provide information about the TCP/IP Subagent and allow you to control some aspects of its behavior: iso (1) identified-organization (3) dod (6) internet (1) private (4) enterprises (1)
Page 251: Ztsa Mib Objects
NonStop Kernel. ztsaProcessVersion The version of the T7862Dnn_date -- 1.3.6.1.4.1.169.3.202.4 TCP/IP Subagent HP SNMP TCP/IP Subagent, read-only process object file. where Dnn is the product version DisplayString of the TCP/IP Subagent; for (SIZE (0..255)) example, D20.
Page 252: Table 8-3. Private (Ztsa) Mib Objects Supported By The Tcp/Ip Subagent
TCP/IP Subagent ZTSA MIB Objects Table 8-3. Private (ZTSA) MIB Objects Supported by the TCP/IP Subagent (page 2 of 7) Object and Attributes Definition Format and Derivation of Value ztsaProcessUserID The user ID number of user-ID-number returned by a 1.3.6.1.4.1.169.3.202.8 the user who started the Guardian PROCESS_GETINFO read-only...
Page 253 TCP/IP Subagent ZTSA MIB Objects Table 8-3. Private (ZTSA) MIB Objects Supported by the TCP/IP Subagent (page 3 of 7) Object and Attributes Definition Format and Derivation of Value ztsaBackupState* The state of the TCP/IP Following are valid states for the 1.3.6.1.4.1.169.3.202.13 Subagent backup backup process:...
Page 254 TCP/IP Subagent ZTSA MIB Objects Table 8-3. Private (ZTSA) MIB Objects Supported by the TCP/IP Subagent (page 4 of 7) Object and Attributes Definition Format and Derivation of Value ztsaEmsCollectorState* The state of the Following are valid values for the 1.3.6.1.4.1.169.3.202.16 connection between the state of the connection:...
Page 255 TCP/IP Subagent ZTSA MIB Objects Table 8-3. Private (ZTSA) MIB Objects Supported by the TCP/IP Subagent (page 5 of 7) Object and Attributes Definition Format and Derivation of Value ztsaStatsCache The cache update A value in the range 0 to 32000 1.3.6.1.4.1.169.3.202.19 interval (in seconds) for specified for the -stats startup...
Page 256 TCP/IP Subagent ZTSA MIB Objects Table 8-3. Private (ZTSA) MIB Objects Supported by the TCP/IP Subagent (page 6 of 7) Object and Attributes Definition Format and Derivation of Value ztsaTcpIpState* The state of the Following are valid values for the 1.3.6.1.4.1.169.3.202.23 connection between the state of the connection:...
Page 257 TCP/IP Subagent ZTSA MIB Objects Table 8-3. Private (ZTSA) MIB Objects Supported by the TCP/IP Subagent (page 7 of 7) Object and Attributes Definition Format and Derivation of Value ztsaSubnetEntry The entry that contains Contains the ztsaSubnetName, 1.3.6.1.4.1.169.3.202.27.1 information related to the ztsaSubnetAddr and not-accessible subnets associated with...
Page 258: State Object/Resource Object Pairs
TCP/IP Subagent State Object/Resource Object Pairs State Object/Resource Object Pairs The private TCP/IP Subagent MIB objects that control or indicate the internal processing state of other objects are referred to as “state objects.” The objects whose internal processing states are indicated or controlled by state objects are referred to as “resource objects.”...
Page 259: Figure 8-3. Tcp/Ip Subagent Resource Object States
TCP/IP Subagent State Object/Resource Object Pairs State Transitions for Resource Objects Figure 8-3 illustrates how resource objects move between states. Note that: Setting a “Connected” object to “Disabled” forces a transition through the “Disconnected” state. This permits the orderly shutdown of the resource and the generation of a state change event for the disconnected state.
Page 260: Interfaces Group
The Interfaces group consists of one scalar object and one table (the ifTable). The objects identified by a check mark in the following list are objects for which there is corresponding HP instrumentation: iso (1) identified-organization (3) dod (6)
Page 261: Mib Objects
(21) ifOutSpecific (22) MIB Objects Table 8-5 describes how the TCP/IP Subagent supports objects in the MIB-II Interfaces group that have HP instrumentation. Table 8-5. Interfaces Group Objects Supported by TCP/IP Subagent (page 1 of 7) Object and Attributes Definition...
Page 262 TCP/IP Subagent MIB Objects Table 8-5. Interfaces Group Objects Supported by TCP/IP Subagent (page 2 of 7) Object and Attributes Definition Format and Derivation of Value ifDescr Identification of a $ZZLAN.lif zzz , where $line is the 1.3.6.1.2.1.2.2.1.2 physical interface. name of a TLAM or X.25 line associated read-only with a TCP/IP subnet.
Page 263 TCP/IP Subagent MIB Objects Table 8-5. Interfaces Group Objects Supported by TCP/IP Subagent (page 3 of 7) Object and Attributes Definition Format and Derivation of Value ifMtu The size of the The value depends on the ifType value, as 1.3.6.1.2.1.2.2.1.4 largest datagram that follows: read-only...
Page 264 TCP/IP Subagent MIB Objects Table 8-5. Interfaces Group Objects Supported by TCP/IP Subagent (page 4 of 7) Object and Attributes Definition Format and Derivation of Value ifPhysAddress The interface’s The value depends on the ifType value, as 1.3.6.1.2.1.2.2.1.6 address at the follows: read-only protocol layer...
Page 265: Table 8-5. Interfaces Group Objects Supported By Tcp/Ip Subagent
TCP/IP Subagent MIB Objects Table 8-5. Interfaces Group Objects Supported by TCP/IP Subagent (page 5 of 7) Object and Attributes Definition Format and Derivation of Value ifLastChange The value of If the current state existed prior to the last 1.3.6.1.2.1.2.2.1.9 sysUpTime at the reinitialization of the SNMP agent, the read-only...
Page 266 TCP/IP Subagent MIB Objects Table 8-5. Interfaces Group Objects Supported by TCP/IP Subagent (page 6 of 7) Object and Attributes Definition Format and Derivation of Value ifInUnknownProtos The number of LM_Get_Statistics_ on PIF name returns 1.3.6.1.2.1.2.2.1.15 packets received via ifInUnknownProtos for SLSA. read-only the interface that Counter...
Page 267 TCP/IP Subagent MIB Objects Table 8-5. Interfaces Group Objects Supported by TCP/IP Subagent (page 7 of 7) Object and Attributes Definition Format and Derivation of Value ifOutDiscards The number of LM_Get_Statistics_ on PIF name returns 1.3.6.1.2.1.2.2.1.19 outbound packets that ifOutDiscards for SLSA. read-only were discarded even ifOutDiscards is not supported for the...
Page 268: Rfc Compliance
Partial Table 8-5. ifOutSpecific Partial No corresponding HP instrumentation exists; 0:0 is returned. ifTable Maintenance Ethernet, SNAP (Subnetwork Access Point), and X.25 interfaces are configured by the system administrator through the Subsystem Control Facility (SCF) or programmatically using SPI. The TCP/IP Subagent uses this configuration information to derive ifTable entries.
Page 269 IP group. The TCP/IP Subagent assigns a number to each SUBNET object defined in the HP TCP/IP subsystem it is managing. That number represents both the index of the ifTable and the instance of the MIB object.
Page 270: Ip Group
The IP group consists of a collection of scalar objects and three tables: ipAddrTable, ipRouteTable, and ipNetToMediaTable. Objects with a check mark in the following list are objects for which there is corresponding HP instrumentation: iso (1) identified-organization (3)
Page 271: Mib Objects
Definition Format and Derivation of Value ipForwarding An indication of The constant value is 1 (forwarding) 1.3.6.1.2.1.4.1 whether datagrams because the HP TCP/IP subsystem always read-only addressed to other attempts to forward datagrams to other INTEGER entities are being destinations.
Page 272 TCP/IP Subagent MIB Objects Table 8-7. IP Group Objects Supported by TCP/IP Subagent (page 2 of 8) Object and Attributes Definition Format and Derivation of Value ipInHdrErrors The number of input The sum (integer) of the values in the 1.3.6.1.2.1.4.4 datagrams discarded following fields of the ZTCI-DDL-IP-STATS read-only...
Page 273 TCP/IP Subagent MIB Objects Table 8-7. IP Group Objects Supported by TCP/IP Subagent (page 3 of 8) Object and Attributes Definition Format and Derivation of Value ipOutRequests The total number of The value (integer) of the ZSTATS-IP- 1.3.6.1.2.1.4.10 IP datagrams that OUT-PKTS field of the ZTCI-DDL-IP- read-only local IP user...
Page 274 TCP/IP Subagent MIB Objects Table 8-7. IP Group Objects Supported by TCP/IP Subagent (page 4 of 8) Object and Attributes Definition Format and Derivation of Value ipReasmFails The number of The sum (integer) of the values in the 1.3.6.1.2.1.4.16 failures detected by following fields of the ZTCI-DDL-IP-STATS read-only the IP reassembly...
Page 275 TCP/IP Subagent MIB Objects Table 8-7. IP Group Objects Supported by TCP/IP Subagent (page 5 of 8) Object and Attributes Definition Format and Derivation of Value ipAdEntBcastAddr The value of the least The constant value for this object is 1, as 1.3.6.1.2.1.4.20.1.4 significant bit in the specified by RFC 1213.
Page 276 TCP/IP Subagent MIB Objects Table 8-7. IP Group Objects Supported by TCP/IP Subagent (page 6 of 8) Object and Attributes Definition Format and Derivation of Value ipRouteMetric1 Primary and alternate The constant value for these objects is -1 1.3.6.1.2.1.4.21.1.3 routing metrics for (not used).
Page 277 TCP/IP Subagent MIB Objects Table 8-7. IP Group Objects Supported by TCP/IP Subagent (page 7 of 8) Object and Attributes Definition Format and Derivation of Value ipRouteProto The routing The constant value for this object is 2 1.3.6.1.2.1.4.21.1.9 mechanism by which (configured through local network read-only this route was...
Page 278: Rfc Compliance
Complianc Object Descriptor Explanation ipForwarding Set operation not supported; attempt returns noSuchName error. See Table 8-7 description of retrievable information. ipDefaultTTL Partial No corresponding HP instrumentation exists; 0 is returned. ipInReceives Table 8-7. ipInHdrErrors Table 8-7. ipInAddrErrors Partial No corresponding HP instrumentation exists; 0 is returned.
Page 279 RFC Compliance Table 8-8. Compliance With IP Group Definitions in RFC 1213 (page 2 of 3) Complianc Object Descriptor Explanation ipOutDiscards Partial No corresponding HP instrumentation exists; 0 is returned. ipOutNoRoutes Table 8-7. ipReasmTimeout Partial No corresponding HP instrumentation exists; 0 is returned.
Page 280: Ipaddrtable Maintenance
See Table 8-7 description of retrievable information. ipRoutingDiscards Partial No corresponding HP instrumentation exists; 0 is returned. ipAddrTable Maintenance Subnets are configured interactively through SCF or programmatically through SPI. The TCP/IP Subagent uses this configuration information to derive table entries.
Page 281: Ipnettomediatable Maintenance
(ICMP) layer of the TCP/IP subsystem being managed. The ICMP group consists of a collection of scalar objects. The objects identified by a check mark in the following list are objects for which there is corresponding HP TCP/IP subsystem instrumentation:...
Page 282: Table 8-9. Icmp Group Objects Supported By Tcp/Ip Subagent
(26) MIB Objects Table 8-9 describes how the TCP/IP Subagent supports objects in the MIB-II ICMP group that have HP instrumentation. Table 8-9. ICMP Group Objects Supported by TCP/IP Subagent (page 1 of 4) Object and Attributes Definition Derivation of Value...
Page 283 TCP/IP Subagent MIB Objects Table 8-9. ICMP Group Objects Supported by TCP/IP Subagent (page 2 of 4) Object and Attributes Definition Derivation of Value icmpInTimeExcds The number of ICMP Offset 13 in the ZSTATS-ICMP-IN- 1.3.6.1.2.1.5.4 time-exceeded HIST array in the ZTCI-DDL-ICMP- read-only messages received.
Page 284 TCP/IP Subagent MIB Objects Table 8-9. ICMP Group Objects Supported by TCP/IP Subagent (page 3 of 4) Object and Attributes Definition Derivation of Value icmpOutErrors The number of ICMP The difference between the value in 1.3.6.1.2.1.5.15 messages not sent the ZSTATS-ICMP-ERR field of the read-only because of problems ZTCI-DDL-ICMPSTATS structure,...
Page 285: Rfc Compliance
Table 8-9. icmpInEchoReps Table 8-9. icmpInTimestamps Table 8-9. icmpInTimestampReps Table 8-9. icmpAddrMasks Partial No corresponding HP instrumentation exists; 0 is returned. icmpInAddrMaskReps Partial No corresponding HP instrumentation exists; 0 is returned. icmpOutMsgs Table 8-9. icmpOutErrors Table 8-9. icmpOutDestUnreachs Table 8-9.
Page 286: Tcp Group
Table 8-9. icmpOutTimestampRep Table 8-9. icmpOutAddrMasks Partial No corresponding HP instrumentation exists; 0 is returned. icmpOutAddrMaskReps Partial No corresponding HP instrumentation exists; 0 is returned. TCP Group The TCP group contains information about the Transmission Control Protocol (TCP) layer of the TCP/IP subsystem being managed.
Page 287: Mib Objects
(15) MIB Objects Table 8-11 describes how the TCP/IP Subagent supports objects in the MIB-II TCP group that have HP instrumentation. Table 8-11. TCP Group Objects Supported by TCP/IP Subagent (page 1 of 4) Object and Attributes Definition Format and Derivation of Value...
Page 288 TCP/IP Subagent MIB Objects Table 8-11. TCP Group Objects Supported by TCP/IP Subagent (page 2 of 4) Object and Attributes Definition Format and Derivation of Value tcpCurrEstab The number of TCP The count of the connections having 1.3.6.1.2.1.6.9 connections for which the following values: read-only the current state is...
Page 289 TCP/IP Subagent MIB Objects Table 8-11. TCP Group Objects Supported by TCP/IP Subagent (page 3 of 4) Object and Attributes Definition Format and Derivation of Value tcpConnState The state of the TCP One of the following values, derived 1.3.6.1.2.1.6.13.1.1 connection. from the indicated SPI value in the read-only ZNET-STATUS-STATE field of the...
Page 290: Rfc Compliance
Yes. Table 8-11. tcpRtoMax Table 8-11. tcpActiveOpens Table 8-11. tcpPassiveOpens Table 8-11. tcpAttemptFails Partial No corresponding HP instrumentation exists; 0 is returned. tcpEstabResets Partial No corresponding HP instrumentation exists; 0 is returned. tcpCurrEstab Table 8-11. tcpInSegs Table 8-11. tcpOutSegs Table 8-11.
Page 291: Udp Group
Table 8-11. tcpOutRsts Partial No corresponding HP instrumentation exists; 0 is returned. tcpConnTable Maintenance The TCP/IP Subagent builds entries by sending a STATUS SPI command to the PROCESS object, using the name of the TCP/IP subsystem being managed (ztsaTcpIpProcess). It then maps the values found in the ZTCI-DDL-STATUS- PROTO structure into the appropriate MIB objects.
Page 292: Mib Objects
(2) MIB Objects Table 8-13 describes how the TCP/IP Subagent supports objects in the MIB-II UDP group that have HP instrumentation. Table 8-13. UDP Group Objects Supported by TCP/IP Subagent (page 1 of 2) Object and Attributes Definition Format and Derivation of Value...
Page 293: Rfc Compliance
UDP group support with RFC 1213. Table 8-14. Compliance With UDP Group Definitions in RFC 1213 Complianc Object Descriptor Explanation udpInDatagrams Table 8-13. udpNoPorts Partial No corresponding HP instrumentation exists; 0 is returned. udpInErrors Table 8-13. udpOutDatagrams Table 8-13. udpLocalAddress Table 8-13.
Page 294: Traps Generated By The Tcp/Ip Subagent
TCP/IP Subagent Traps Generated by the TCP/IP Subagent represent information about a particular UDP connection are transient. They persist only as long as the connection in question. Rebuilding the udpTable also causes the indexes in the tcpConnTable to be updated. Traps Generated by the TCP/IP Subagent The TCP/IP Subagent generates traps to inform SNMP managers of the status of the TCP/IP subnets.
Page 295: Table 8-16. Tcp/Ip Subagent Event Messages
TCP/IP Subagent EMS Support Table 8-16. TCP/IP Subagent Event Messages (page 1 of 3) Number ZTSA-EVT- Standard Event and Description 1001 SUBAGENT-AVAIL Object Available The TCP/IP Subagent primary process has been initialized. This event is generated at initial startup and whenever a takeover by the backup occurs.
Page 296 TCP/IP Subagent EMS Support Table 8-16. TCP/IP Subagent Event Messages (page 2 of 3) Number ZTSA-EVT- Standard Event and Description 1011 OUT-OF-MEMORY Transient Fault The subagent could not allocate memory needed for application execution. The subagent’s ability to build MIB tables and/or reply to SNMP requests might be compromised by a shortage of memory.
Page 297: Data Definitions
TCP/IP Subagent Data Definitions Table 8-16. TCP/IP Subagent Event Messages (page 3 of 3) Number ZTSA-EVT- Standard Event and Description 1023 PIFGETATTR-ERROR Transient Fault The LM_Get_Attributes_ function returned an error. The ifTable values derived through the INFO command are not current until the timer expires, the same ZLANMSRL function is retried, and a response obtained.
Page 298: Subsystem Id
TCP/IP Subagent Subsystem ID Subsystem ID The subsystem ID that the TCP/IP Subagent uses to identify itself as the source of event messages is: CONSTANT ZTSA-VAL-OWNER VALUE "TANDEM". CONSTANT ZTSA-VAL-NUMBER VALUE 202. CONSTANT ZTSA-VAL-VERSION VALUE VERSION "D20". CONSTANT ZTSA-VAL-EXTERNAL-SSID VALUE "TANDEM.202.D20".
Page 299: Table 8-18. Zems Tokens In Ztsa Event Messages
TCP/IP Subagent Tokens in ZTSA Event Messages Standard EMS Tokens Table 8-18 lists the standard EMS tokens that the TCP/IP Subagent includes in the event messages it generates. These tokens are defined in the ZEMSDDL definition file. See the EMS Manual for more information on these tokens and related data definitions.
Page 300: Event Message Descriptions
TCP/IP Subagent Event Message Descriptions Event Message Descriptions ZTSA event messages are described in order by event number. Each description includes the following: Token lists. Tokens listed as “unconditional” always appear in the event message. Tokens listed as “conditional” are included only under described conditions. Tokens not defined by ZTSA are listed only if they contain information that appears in the printed message text or if they contain ZTSA-defined values.
Page 301 TCP/IP Subagent 1001: ZTSA-EVT-SUBAGENT-AVAIL Message Text Object available <1>-<2>, event number: <3>, reason: <4>, previous state: <5>, current state: <6>, user content: <7> ZTSA-TKN-SUBAGENT identifies the subject of the event (the TCP/IP Subagent process). The DDL heading of this token (“TCP/IP-SNMP-subagent”) is inserted in the message text following “Object available.”...
Page 302: 1002: Ztsa-Evt-Subagent-Unavail
TCP/IP Subagent 1002: ZTSA-EVT-SUBAGENT-UNAVAIL ZEMS-VAL-NULL indicates the type of subsystem defined event. Because the TCP/IP Subagent process has not defined this as a private event, the DDL AS clause “undefined” always appears in the message text following “user content.” Cause. The TCP/IP Subagent process completed process initialization after initial startup or after a takeover by the backup process.
Page 303 TCP/IP Subagent 1002: ZTSA-EVT-SUBAGENT-UNAVAIL Message Text Object unavailable <1>-<2>, event number: <3>, cause: <4>, previous state: <5>, current state <6>, [ underlying object: <9>,] symptom string: <7>, user content: <8> ZTSA-TKN-SUBAGENT identifies the subject of the event (the TCP/IP Subagent process). The DDL heading of this token (“TCP/IP-SNMP-subagent”) is inserted in the message text following “Object unavailable.”...
Page 304 Cause. The TCP/IP Subagent process terminated for reasons other than an internal fault or invalid startup configuration. Effect. The TCP/IP Subagent process is unavailable. Recovery. Contact your HP service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms...
Page 305: 1003: Ztsa-Evt-Agent-Obj-Avail
TCP/IP Subagent 1003: ZTSA-EVT-AGENT-OBJ-AVAIL 1003: ZTSA-EVT-AGENT-OBJ-AVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZTSA-TKN-AGENT ZTSA-TKN-AGENT <2> ztsaAgentName ZEMS-TKN-EVENTNUMBER <3> ZTSA-EVT-AGENT-OBJ-AVAIL ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-UNDERLYING-UP ZEMS-TKN-STATE-PREVIOUS <5> ZTSA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZTSA-VAL-STATE-CONNECTED ZEMS-TKN-USER-CONTENT <7> ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number: <3>, reason: <4>, previous state: <5>, current state <6>, user content: <7>...
Page 306 TCP/IP Subagent 1003: ZTSA-EVT-AGENT-OBJ-AVAIL ZTSA-VAL-STATE-state indicates the previous state of the SNMP agent process. The DDL AS clause associated with this value is inserted in the message text following “previous state.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-STATE-PREVIOUS Meaning ZTSA-VAL-STATE-CONNECTED “connected”...
Page 307: 1004: Ztsa-Evt-Agent-Obj-Unavail
TCP/IP Subagent 1004: ZTSA-EVT-AGENT-OBJ-UNAVAIL 1004: ZTSA-EVT-AGENT-OBJ-UNAVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZTSA-TKN-AGENT ZTSA-TKN-AGENT <2> ztsaAgentName ZEMS-TKN-EVENTNUMBER <3> ZTSA-EVT-AGENT-OBJ-UNAVAIL ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-UNDERLYING-FAILED ZEMS-TKN-STATE-PREVIOUS <5> ZTSA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZTSA-VAL-STATE-DISCONNECTED ZEMS-TKN-UNDERLYING-OBJ- <7> ztsaAgentName NAME <8> code-location/ ZEMS-TKN-SYMPTOM-STRING internal-context-text <9> ZEMS-VAL-NUL ZEMS-TKN-USER-CONTENT Conditional Tokens None Message Text Object unavailable <1>-<2>, event number: <3>, cause: <4>,...
Page 308 TCP/IP Subagent 1004: ZTSA-EVT-AGENT-OBJ-UNAVAIL ZTSA-VAL-STATE-state indicates the previous state of the SNMP agent process. The DDL AS clause associated with this value is inserted in the message text following “previous state.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-STATE-PREVIOUS Meaning ZTSA-VAL-STATE-CONNECTED “connected”...
Page 309: 1005: Ztsa-Evt-Backup-Obj-Avail
TCP/IP Subagent 1005: ZTSA-EVT-BACKUP-OBJ-AVAIL Sample Message 96-02-08 12:18:39 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001004 Object unavailable agent-interface - \NOVA.$ZSNMP, event number: agent-interface-unavailable, cause: underlying-serv-failed, previous state: connected, current state: disconnected, underlying object: \NOVA.$ZSNMP, symptom string: T7862D20_01JAN96_TCPIPSA: updateAgent.2, agent interface error 201 on poll request, user content: undefined 1005: ZTSA-EVT-BACKUP-OBJ-AVAIL Unconditional Tokens...
Page 310 TCP/IP Subagent 1005: ZTSA-EVT-BACKUP-OBJ-AVAIL ZEMS-VAL-reason indicates the reason the backup TCP/IP Subagent process has become available. The DDL AS clause associated with this value is inserted in the message text following “reason.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-CHANGE-REASON Meaning ZEMS-VAL-UNDERLYING-UP...
Page 311 TCP/IP Subagent 1005: ZTSA-EVT-BACKUP-OBJ-AVAIL ZEMS-VAL-NULL indicates the type of subsystem-defined event. Because the TCP/IP Subagent process has not defined this as a private event, the DDL AS clause “undefined” always appears in the message text following “user content.” Cause. The TCP/IP Subagent successfully started a backup process identified by ztsaBackupCPU:ztsaBackupPIN.
Page 312: 1006: Ztsa-Evt-Backup-Obj-Unavail
TCP/IP Subagent 1006: ZTSA-EVT-BACKUP-OBJ-UNAVAIL 1006: ZTSA-EVT-BACKUP-OBJ-UNAVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZTSA-TKN-BACKUP ZTSA-TKN-BACKUP <2> ztsaProcessName ZEMS-TKN-EVENTNUMBER <3> ZTSA-EVT-BACKUP-OBJ-UNAVAIL ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-reason ZEMS-TKN-STATE-PREVIOUS <5> ZTSA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZTSA-VAL-STATE-DISCONNECTED ZEMS-TKN-SYMPTOM-STRING <7> code-location/ internal-context-text ZEMS-TKN-USER-CONTENT <8> ZEMS-VAL-NULL Conditional Tokens ZEMS-TKN-UNDERLYING-OBJ- <9> ztsaProcessName NAME Message Text Object unavailable <1>-<2>, event number: <3>, cause: <4>, previous state: <5>, current state <6>,...
Page 313 TCP/IP Subagent 1006: ZTSA-EVT-BACKUP-OBJ-UNAVAIL ZEMS-VAL-reason indicates the reason the backup TCP/IP Subagent process has become unavailable. The DDL AS clause associated with this value is inserted in the message text following “cause.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-CHANGE-REASON Meaning ZEMS-VAL-UNDERLYING-FAILED...
Page 314 TCP/IP Subagent 1006: ZTSA-EVT-BACKUP-OBJ-UNAVAIL This information is displayed only if the value of the ZEMS-TKN-CHANGE- REASON is ZEMS-VAL-UNDERLYING-FAILED. code-location/internal-context-text indicates where in the subsystem or application code the fault occurred. ZEMS-VAL-NULL indicates the type of subsystem defined event. Because the TCP/IP Subagent process has not defined this as a private event, the DDL AS clause “undefined”...
Page 315: 1007: Ztsa-Evt-Emscoll-Obj-Avail
TCP/IP Subagent 1007: ZTSA-EVT-EMSCOLL-OBJ-AVAIL 1007: ZTSA-EVT-EMSCOLL-OBJ-AVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZTSA-TKN-EMSCOLLECTOR ZTSA-TKN-EMSCOLLECTOR <2> ztsaEmsCollectorName ZEMS-TKN-EVENTNUMBER <3> ZTSA-EVT-EMSCOLL-OBJ-AVAIL ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-reason ZEMS-TKN-STATE-PREVIOUS <5> ZTSA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZTSA-VAL-STATE-CONNECTED ZEMS-TKN-USER-CONTENT <7> ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number: <3>, reason: <4>, previous state: <5>, current state <6>, user content: <7>...
Page 316 TCP/IP Subagent 1007: ZTSA-EVT-EMSCOLL-OBJ-AVAIL ZTSA-VAL-STATE-state indicates the previous state of the interface to the EMS collector process. The DDL AS clause associated with this value is inserted in the message text following “previous state.” Value of ZEMS-TKN-STATE-PREVIOUS Associated Text (DDL AS Clause) ZTSA-VAL-STATE-CONNECTED “connected”...
Page 317: 1008: Ztsa-Evt-Emscoll-Obj-Unavail
TCP/IP Subagent 1008: ZTSA-EVT-EMSCOLL-OBJ-UNAVAIL Sample Message 96-02-08 12:21:51 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001007 Object available emscollector-interface - \NOVA.$p0, event number: emscollector- interface-available, reason: operator-initiated, previous state: enabled, current state: connected, user content: undefined 1008: ZTSA-EVT-EMSCOLL-OBJ-UNAVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZTSA-TKN-EMSCOLLECTOR ZTSA-TKN-EMSCOLLECTOR <2>...
Page 318 TCP/IP Subagent 1008: ZTSA-EVT-EMSCOLL-OBJ-UNAVAIL ZEMS-VAL-reason indicates the reason the interface with the EMS collector process has become unavailable. The DDL AS clause associated with this value is inserted in the message text following “cause.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-CHANGE-REASON Meaning ZEMS-VAL-UNDERLYING-FAILED...
Page 319 TCP/IP Subagent 1008: ZTSA-EVT-EMSCOLL-OBJ-UNAVAIL ztsaEmsCollectorName is the name of the underlying process whose failure caused the interface between the TCP/IP Subagent and the EMS collector to go out of service. The name of the EMS collector process specified for the subagent’s private ztsaEmsCollectorName MIB object is inserted in the message text following “underlying object.”...
Page 320: 1009: Ztsa-Evt-Tcpip-Obj-Avail
TCP/IP Subagent 1009: ZTSA-EVT-TCPIP-OBJ-AVAIL 1009: ZTSA-EVT-TCPIP-OBJ-AVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZTSA-TKN-TCPIP ZTSA-TKN-TCPIP <2> ztsaTcpIpProcess ZEMS-TKN-EVENTNUMBER <3> ZTSA-EVT-TCPIP-OBJ-AVAIL ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-reason ZEMS-TKN-STATE-PREVIOUS <5> ZTSA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZTSA-VAL-STATE-CONNECTED ZEMS-TKN-USER-CONTENT <7> ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number: <3>, reason: <4>, previous state: <5>, current state <6>, user content: <7>...
Page 321 TCP/IP Subagent 1009: ZTSA-EVT-TCPIP-OBJ-AVAIL ZTSA-VAL-STATE-state indicates the previous state of the TCP/IP process. The DDL AS clause associated with this value is inserted in the message text following “previous state.” Value of ZEMS-TKN-STATE-PREVIOUS Associated Text (DDL AS Clause) ZTSA-VAL-STATE-CONNECTED “connected” indicates a normal operational interface between the TCP/IP Subagent and the TCP/IP process it is managing.
Page 322: 1010: Ztsa-Evt-Tcpip-Obj-Unavail
TCP/IP Subagent 1010: ZTSA-EVT-TCPIP-OBJ-UNAVAIL Sample Message 96-02-08 12:08:44 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001009 Object available tcpip-resource - \NOVA.$ZTC0 event number: tcpip-resource-available, reason: underlying-serv-up, previous state: disconnected, current state: connected, user content: undefined 96-02-08 12:21:51 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001009 Object available tcpip-resource - \NOVA.$foo, event number: tcpip-resource-available, reason: operator-initiated, previous state: enabled,...
Page 323 TCP/IP Subagent 1010: ZTSA-EVT-TCPIP-OBJ-UNAVAIL ztsaTcpIpProcess is the TCP/IP process name specified for the TCP/IP Subagent’s private ztsaTcpIpProcess MIB object. ZTSA-EVT-TCPIP-OBJ-UNAVAIL is the event number (1010). The DDL AS clause of this value (“tcpip-resource- unavailable”) appears in the message text following “event number.” ZEMS-VAL-reason indicates the reason the TCP/IP process has become unavailable.
Page 324 TCP/IP Subagent 1010: ZTSA-EVT-TCPIP-OBJ-UNAVAIL underlying-process is the name of the underlying process whose failure caused the interface between the TCP/IP Subagent and the TCP/IP process to go out of service. The name of one of the following processes is inserted in the message text following “underlying object”: The name of the TCP/IP process specified for the subagent’s private ztsaTcpIpProcess MIB object...
Page 325: 1011: Ztsa-Evt-Out-Of-Memory
TCP/IP Subagent 1011: ZTSA-EVT-OUT-OF-MEMORY If the underlying object is the SNMP agent process, check the operating state of the SNMP agent process. If necessary, restart the SNMP agent. The TCP/IP Subagent attempts to reconnect to the SNMP agent at the rate indicated by its ztsaKeepAliveTimer object.
Page 326 TCP/IP Subagent 1011: ZTSA-EVT-OUT-OF-MEMORY ztsaProcessName is the TCP/IP Subagent process name specified for the TCP/IP Subagent’s private ztsaProcessName MIB object. ZTSA-EVT-OUT-OF-MEMORY is the event number (1011). The DDL AS clause of this value (“out-of-memory”) appears in the message text following “event number.” ZTSA-VAL-TF-MEMORY identifies the type of transient fault that occurred.
Page 327: 1012: Ztsa-Evt-Internal-Fault
TCP/IP Subagent 1012: ZTSA-EVT-INTERNAL-FAULT 1012: ZTSA-EVT-INTERNAL-FAULT Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZTSA-TKN-SUBAGENT ZTSA-TKN-SUBAGENT <2> ztsaProcessName ZEMS-TKN-EVENTNUMBER <3> ZTSA-EVT-INTERNAL-FAULT ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-INTERNAL-FAILED ZEMS-TKN-STATE-PREVIOUS <5> ZTSA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZTSA-VAL-STATE-DISCONNECTED ZEMS-TKN-SYMPTOM-STRING <7> code-location/ ZEMS-TKN-USER-CONTENT internal-context-text <8> ZEMS-VAL-NULL Conditional Tokens None Message Text Object unavailable <1>-<2>, event number: <3>, cause: <4>, previous state: <5>, current state <6>, symptom string: <7>...
Page 328 TCP/IP Subagent 1012: ZTSA-EVT-INTERNAL-FAULT ZTSA-VAL-STATE-state indicates the previous state of the TCP/IP Subagent process. The DDL AS clause associated with this value is inserted in the message text following “previous state.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-STATE-PREVIOUS Meaning ZTSA-VAL-STATE-CONNECTED “connected”...
Page 329: 1013: Ztsa-Evt-Configuration-Invalid
TCP/IP Subagent 1013: ZTSA-EVT-CONFIGURATION-INVALID Sample Message 96-02-08 11:49:38 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001012 Object unavailable TCP/IP-SNMP- subagent - \NOVA.$ZTSA:384117973, event number: internal-fault, cause: internal-failed, previous state: connected, current state: disconnected, symptom string:T7862D20_01JAN96_TCPIPSA: AWAITIOX error -1, user content: undefined 1013: ZTSA-EVT-CONFIGURATION-INVALID Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1>...
Page 330 TCP/IP Subagent 1013: ZTSA-EVT-CONFIGURATION-INVALID ZEMS-VAL-INTERNAL-FAILED indicates that an internal error was encountered. The DDL AS clause associated with this value (“internal-failed”) is inserted in the message text following “cause.” ZTSA-VAL-STATE-ENABLED indicates the previous state of the TCP/IP Subagent process. The DDL AS clause of this value (“enabled”) appears in the message text following “previous state.”...
Page 331: 1014: Ztsa-Evt-Takeover-By-Backup
TCP/IP Subagent 1014: ZTSA-EVT-TAKEOVER-BY-BACKUP Sample Message 96-02-08 11:24:51 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001013 Object unavailable TCP/IP-SNMP-subagent - \NOVA.$ZTSA:383971797, event number: startup-configuration-invalid, cause: internal-failed, previous state: enabled, current state: disconnected, symptom string: T7862D20_01JAN96_TCPIPSA: Agent process name parameter <ZSNMP1> invalid, user content: undefined 1014: ZTSA-EVT-TAKEOVER-BY-BACKUP Unconditional Tokens Value ZEMS-TKN-EVENTNUMBER...
Page 332: 1015: Ztsa-Evt-Lanmon-Obj-Unavail
TCP/IP Subagent 1015: ZTSA-EVT-LANMON-OBJ-UNAVAIL Sample Message 96-02-08 11:31:35 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001014 Takeover by backup process, Primary-stopped 1015: ZTSA-EVT-LANMON-OBJ-UNAVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZTSA-TKN-SUBAGENT ZTSA-TKN-SUBAGENT <2> ztsaProcessName ZEMS-TKN-EVENTNUMBER <3> ZTSA-EVT-LANMON-OBJ-UNAVAIL ZEMS-TKN-TXFAULT-TYPE <4> ZTSA-VAL-TF-LANMON ZEMS-TKN-USER-CONTENT <5> ZEMS-VAL-NULL Conditional Tokens None Message Text Transient Fault <1>-<2>, event number: <3>, fault type: <4>, user content: <5>...
Page 333: 1022: Ztsa-Evt-Pifgetstatus-Error
TCP/IP Subagent 1022: ZTSA-EVT-PIFGETSTATUS-ERROR Cause. The LANMON process did not respond to the LM_Get_Version_ function. Effect. The ifDescr object values will not contain the LANMON version string. Recovery. Generally, this condition is transient, and no corrective action is necessary. If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated...
Page 334 TCP/IP Subagent 1022: ZTSA-EVT-PIFGETSTATUS-ERROR ZTSA-EVT-PIFGETSTATUS-ERROR is the event number (1022). The DDL AS clause of this value (“LM_Get_Status_error-on-PIF”) appears in the message text following “event number.” ZTSA-VAL-TF-PIFGETSTATUS identifies the type of transient fault that occurred. For this event, the DDL heading of the value (“PIF-status-cmd-not-completed”) appears in the message text following “fault type.”...
Page 335: 1023: Ztsa-Evt-Pifgetattr-Error
TCP/IP Subagent 1023: ZTSA-EVT-PIFGETATTR-ERROR 1023: ZTSA-EVT-PIFGETATTR-ERROR Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZTSA-TKN-SUBAGENT ZTSA-TKN-SUBAGENT <2> ztsaProcessName ZEMS-TKN-EVENTNUMBER <3> ZTSA-EVT-PIFGETATTR-ERROR ZEMS-TKN-TXFAULT-TYPE <4> ZTSA-VAL-TF-PIFGETATTR ZEMS-TKN-USER-CONTENT <5> ZEMS-VAL-NULL Conditional Tokens None Message Text Transient Fault <1>-<2>, event number: <3>, fault type: <4>, user content: <5> ZTSA-TKN-SUBAGENT identifies the subject of the event (the TCP/IP Subagent process).
Page 336: 1039: Ztsa-Evt-Lifgetattr-Error
TCP/IP Subagent 1039: ZTSA-EVT-LIFGETATTR-ERROR Cause. The LM_Get_Attributes_ function returned an error on the PIF. Effect. The ifTable values obtained through the INFO command are not current until the timer expires, the same ZLANMSRL call is retried, and a response obtained. Recovery.
Page 337 TCP/IP Subagent 1039: ZTSA-EVT-LIFGETATTR-ERROR ZTSA-EVT-LIFGETATTR-ERROR is the event number (1039). The DDL AS clause of this value (“LM_Get_Attributes_error-on-LIF”) appears in the message text following “event number.” ZTSA-VAL-TF-LIFGETATTR identifies the type of transient fault that occurred. For this event, the DDL heading of the value (“LIF-attr-cmd-not-completed”) appears in the message text following “fault type.”...
Page 338: 1041: Ztsa-Evt-Pifgetstats-Error
TCP/IP Subagent 1041: ZTSA-EVT-PIFGETSTATS-ERROR 1041: ZTSA-EVT-PIFGETSTATS-ERROR Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZTSA-TKN-SUBAGENT ZTSA-TKN-SUBAGENT <2> ztsaProcessName ZEMS-TKN-EVENTNUMBER <3> ZTSA-EVT-PIFGETSTATS-ERROR ZEMS-TKN-TXFAULT-TYPE <4> ZTSA-VAL-TF-PIFGETSTATS ZEMS-TKN-USER-CONTENT <5> ZEMS-VAL-NULL Conditional Tokens None Message Text Transient Fault <1>-<2>, event number: <3>, fault type: <4>, user content: <5> ZTSA-TKN-SUBAGENT identifies the subject of the event (the TCP/IP Subagent process).
Page 339: Converting Events To Traps
TCP/IP Subagent Converting Events to Traps Cause. The LM_Get_Statistics_ function returned an error. Effect. The ifTable values obtained through the STATS command are not current until the timer expires, the same ZLANMSRL call is retried, and a response obtained. Recovery. Generally, this condition is transient, and no corrective action is necessary. If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms...
Page 340 TCP/IP Subagent Converting Events to Traps SNMP Configuration and Management Manual—424777-006 8 -110...
Page 341: Ems Trap Subagent
EMS is a set of processes that collect event messages and then distribute them to various destinations, such as viewing consoles and printers. Event messages, generated by most HP subsystems and by many customer applications that run on NonStop systems, describe significant situations, such as loss of a function or need for operator action.
Page 342: Architectural Overview
EMS Trap Subagent Architectural Overview Figure 9-1. EMS Components Compaq Customer Subsystems Applications Primary Alternate Collector ($0) Collectors Compatibility Distributor Files File ($Z0) Filter Filter Filter Template Forwarding Consumer Printing Distributor Distributor Distributor Template Remote Management Collector Application Terminal Printer File Console VST801.vsd...
Page 343: Rfc Compliance
EMS Trap Subagent RFC Compliance Figure 9-2. EMS Trap Subagent Components Customer Compaq Applications Subsystems Event Messages Primary or Alternate Collector File Filter Template Files ZSMPTMP ZSMPTMP ZSMPTMP ZSMPTMP EMS Trap Subagent SNMP Traps SNMP Agent EMS Trap MIB Definition SNMP Manager Station VST802.vsd RFC Compliance...
Page 344: Installation
EMS Trap Subagent Installation Installation This subsection describes how to install the EMS Trap Subagent. Dependencies The following products must be configured and running for the EMS Trap Subagent to operate properly: SNMP agent (D23 or later). In addition to the SNMP agent, the subagent needs these files, distributed with the SNMP agent: SSMPTMPL: Template Language source code for a trap message DSM template.
Page 345: Example 9-1. Asn.1 Source Code For Ems Trap Mib
Example 9-1. ASN.1 Source Code for EMS Trap MIB (page 1 of 3) -- This MIB defines Tandem EMS event messages as traps The MIB source is set for installation on HP OpenView for Windows and Unix. Installation on other platforms may...
Page 346 EMS Trap Subagent Installation Steps Example 9-1. ASN.1 Source Code for EMS Trap MIB (page 2 of 3) -- items in each event TrapSSIDtype ::= DisplayString (SIZE (5..24)) TrapEventNumbertype ::= DisplayString (SIZE (1..6)) TrapContentStandardtype ::= DisplayString (SIZE (1..24)) TrapSubjecttype ::= DisplayString (SIZE (1..50)) TrapProcesstype ::= DisplayString (SIZE (1..50)) TrapGenerationtimetype...
Page 347 EMS Trap Subagent Installation Steps Example 9-1. ASN.1 Source Code for EMS Trap MIB (page 3 of 3) trapProcess OBJECT-TYPE SYNTAX TrapProcesstype ACCESS not-accessible STATUS mandatory DESCRIPTION " The process name that generated the event " ::= { ems 5} trapGenerationtime OBJECT-TYPE SYNTAX TrapGenerationtimetype...
Page 348: Configuration
Example 9-2 shows the source code for an event filter that selects and passes all events generated by HP subsystems. This example filter also provides, as part of the routing destination statement, a DEFINE name (=_SNMP_AGENT) to identify the SNMP agent. The DEFINE name, which circumvents hard coding of an agent process...
Page 349: Trap Connections
EMS Trap Subagent Trap Connections You compile the filter with EMF after loading the Data Definition Language (DDL) definitions used by the filter: #PUSH DUMMY #LOAD /KEEP 1, LOADED DUMMY/ $SYSTEM.ZSPIDEF.ZSPITACL #POP DUMMY EMF /IN source-filter/ object-filter The source code for the event filter is in the file identified by source-filter, and the compiled version is in the file identified by object-filter.
Page 350: The Trap Pdu
EMS Trap Subagent The Trap PDU To stop the subagent process, provide its name in the STOP command: STOP $ZSNMP The Trap PDU The trap PDU contains these fields: enterprise The object identifier for the SNMP agent, indicating the origin of the trap: 1.3.6.1.4.1.169.3.155.1.
Page 351: Example 9-3. Example Tacl Macro For Starting Ems Trap Subagent
EMS Trap Subagent The Trap PDU Example 9-3. Example TACL Macro for Starting EMS Trap Subagent ?tacl routine == routine: MYMACRO == synopsis: MYMACRO <SNMP-agent-process> == example: MYMACRO $ZSNMP == description: MYMACRO opens the SNMP agent process and forwards == from $0 as SNMP traps all EMS events that pass the filter == MYFILTER #frame #push :agent^process...
Page 352 EMS Trap Subagent The EMS Trap MIB The EMS Trap MIB The EMS Trap MIB is a collection of scalar objects, identified by a check mark in the following list: iso (1) identified-organization (3) dod (6) internet (1) private (4) enterprises (1) tandem (169) nonstopsystems (3)
Page 353: The Ems Trap Mib
DisplayString (SIZE generated the event. organization providing (5..24)) the software that generated the trap. For HP subsystems, the value is TANDEM. ss is the subsystem name or number. Refer to the Operator Messages Manual to interpret HP values.
Page 354 EMS Trap Subagent The EMS Trap MIB Table 9-1. Objects in the EMS Trap MIB (page 2 of 4) Object and Attributes Definition Format of Value Derivation of Value trapContentStandard An indication of One of these values: The value of whether the event is trapContentStandard 1.3.6.1.4.1.169.3.12.3)
Page 355 EMS Trap Subagent The EMS Trap MIB Table 9-1. Objects in the EMS Trap MIB (page 3 of 4) Object and Attributes Definition Format of Value Derivation of Value trapSubject The hardware or All values except The value of the first software component floating-point values and event subject token.
Page 356 EMS Trap Subagent The EMS Trap MIB Table 9-1. Objects in the EMS Trap MIB (page 4 of 4) Object and Attributes Definition Format of Value Derivation of Value trapCritical An indication of One of these ZEMS-TKN- 1.3.6.1.4.1.169.3.12.7 whether the event is enumerated values: EMPHASIS token not-accessible...
Page 357: Nonstop Net/Master Trap Subagent
EMS is a set of processes that collect event messages and then distribute them to various destinations, including NonStop NET/MASTER. Event messages, generated by most HP subsystems and by many customer applications that run on NonStop systems, describe significant situations, such as loss of a function or need for operator action.
Page 358: Architectural Overview
NonStop NET/MASTER Trap Subagent Architectural Overview Figure 10-1. EMS and NonStop NET/MASTER Components Compaq Customer Subsystems Applications Primary Alternate Collector ($0) Collectors File Files Filter Consumer Distributor NonStop NET/MASTER MS EMSPROC LOGPROC RMS Message Procedures Handler MSGPROC Activity OCS Window VST901.vsd SNMP Configuration and Management Manual—424777-006 10- 2...
Page 359: Rfc Compliance
NonStop NET/MASTER Trap Subagent RFC Compliance Figure 10-2 shows how the NonStop NET/MASTER Trap Subagent fits into this environment. The subagent consists of two NCL procedures, GENTRAP and NMMTRAP, which are invoked from EMSPROC or an RMS message handler: GENTRAP assembles an SNMP trap from an EMS event and calls NMMTRAP for handling communications with the SNMP agent.
Page 360: Installation Steps
NonStop NET/MASTER Trap Subagent Installation Steps Figure 10-2. NonStop NET/MASTER Trap Subagent Components Compaq Customer Subsystems Applications Event Messages Primary Alternate Collector ($0) Collectors Files File Filter Consumer Distributor NonStop NET/MASTER MS EMSPROC GENTRAP RMS Message Handler SNMP NMMTRAP Agent SNMP Traps NonStop NET/...
Page 361 NonStop NET/MASTER Trap Subagent Installation Steps The NonStop NET/MASTER Trap Subagent is installed automatically when you install NonStop NET/MASTER MS. The subagent files are installed in $dsv.ZNNMNDS. If you will be modifying GENTRAP, first copy it to your ZNNMNCS subvolume and modify the ZSNMMCS file.
Page 362: Example 10-1. Asn.1 Source Code For Ems Trap Mib
Example 10-1. ASN.1 Source Code for EMS Trap MIB (page 1 of 3) -- This MIB defines Tandem EMS event messages as traps. The MIB source is set for installation on HP OpenView for Windows and Unix. Installation on other platforms may...
Page 363 NonStop NET/MASTER Trap Subagent Installation Steps Example 10-1. ASN.1 Source Code for EMS Trap MIB (page 2 of 3) -- items in each event TrapSSIDtype ::= DisplayString (SIZE (5..24)) TrapEventNumbertype ::= DisplayString (SIZE (1..6)) TrapContentStandardtype ::= DisplayString (SIZE (1..24)) TrapSubjecttype ::= DisplayString (SIZE (1..50)) TrapProcesstype ::= DisplayString (SIZE (1..50))
Page 364 NonStop NET/MASTER Trap Subagent Installation Steps Example 10-1. ASN.1 Source Code for EMS Trap MIB (page 3 of 3) trapProcess OBJECT-TYPE SYNTAX TrapProcesstype ACCESS not-accessible STATUS mandatory DESCRIPTION " The process name that generated the event " ::= { ems 5} trapGenerationtime OBJECT-TYPE SYNTAX TrapGenerationtimetype...
Page 365: Configuration
NonStop NET/MASTER Trap Subagent Configuration Configuration You might need to perform one or both of these operations before using the subagent: Modify GENTRAP to change the SNMP trap definition or the way the subagent communicates with the SNMP agent. Configure trap connections. This subsection describes these operations.
Page 366: Example 10-2. Initial Contents Of Gentrap
NonStop NET/MASTER Trap Subagent Modifying GENTRAP Example 10-2. Initial Contents of GENTRAP (page 1 of 2) gentrap: procedure nofold procedure: gentrap synopsis: gentrap <snmp-agent-processname> description: This procedure is intended to be invoked from RMS. GENTRAP assembles an SNMP trap from the EMS event and writes it to the #TRAP interface of the specified SNMP agent.
Page 367 NonStop NET/MASTER Trap Subagent Modifying GENTRAP Example 10-2. Initial Contents of GENTRAP (page 2 of 2) &trap.oid.3 = 1.3.6.1.4.1.169.3.12.3 ; /* standard content */ &trap.value.3 = d2c(&$ems.tandem.spi.zems_tkn_content_standard) ; &trap.oid.4 = 1.3.6.1.4.1.169.3.12.4 ; /* value of subject token */ &trap.value.4 = &zzzmsubject; &trap.oid.5 = 1.3.6.1.4.1.169.3.12.5 ;...
Page 368 NonStop NET/MASTER Trap Subagent Modifying GENTRAP file-id is the file identifier you associate with the open operation. GENTRAP assigns the name myagt. return-code is an integer describing the outcome of the function call. GENTRAP uses a variable named &err to hold this value. The openagent return codes, their meanings, and the actions taken by GENTRAP when they occur are described in Messages on page 10-18.
Page 369: Trap Connections
NonStop NET/MASTER Trap Subagent Trap Connections return-code is an integer describing the outcome of the function call. GENTRAP uses a variable named &err to hold this value. The sendtrap return codes, their meanings, and the actions taken by GENTRAP when they occur are described in Messages on page 10-18.
Page 370: The Trap Pdu
NonStop NET/MASTER Trap Subagent The Trap PDU The Trap PDU The trap PDU contains these fields: enterprise The object identifier for the SNMP agent, indicating the origin of the trap: 1.3.6.1.4.1.169.3.155.1. agent-address The Internet address of the system on which the SNMP agent forwarding the trap is installed.
Page 371: The Ems Trap Mib
Refer to the Operator Messages Manua to interpret HP values. version identifies the software release version of the subsystem. For HP subsystems, this value matches the three- character release ID in the product release version (for example, D31).
Page 372 NonStop NET/MASTER Trap Subagent The EMS Trap MIB Table 10-1. Objects in the EMS Trap MIB (page 2 of 4) Object and Attributes Definition Format of Value Derivation of Value trapContentStandard An indication of One of these values: The value of whether the event is a not-specified (Event is trapContentStandard...
Page 373 NonStop NET/MASTER Trap Subagent The EMS Trap MIB Table 10-1. Objects in the EMS Trap MIB (page 3 of 4) Object and Attributes Definition Format of Value Derivation of Value trapSubject The hardware or All values except floating- The value of the first software component point values and values event subject token.
Page 374: Messages
NonStop NET/MASTER Trap Subagent Messages Table 10-1. Objects in the EMS Trap MIB (page 4 of 4) Object and Attributes Definition Format of Value Derivation of Value trapCritical An indication of One of these enumerated ZEMS-TKN- whether the event is values: EMPHASIS token 1.3.6.1.4.1.169.3.12.7...
Page 375: Sendtrap Failures
NonStop NET/MASTER Trap Subagent sendtrap Failures return-code has the value 1 or 2, as described in Table 10-2. &sys.file.rc-value contains an integer if the FILE OPEN verb in the openagent function failed: 12 (UDB is inaccessible.) 16 (UDB identifier is unavailable or not found. See &sysmsg for more information.) &sys.file.error-value is the Guardian file error number corresponding to the value of &sys.file.rc.
Page 376: Closeagent Failures
NonStop NET/MASTER Trap Subagent closeagent Failures &sys.file.rc-value contains an integer if the FILE PUTGET verb in the sendtrap function failed: 8 (Error occurred. See &sys.file.error value for more information.) 16 (Error occurred. &sysmsg might contain more information.) &sys.file.error-value is the Guardian error number corresponding to the value of &sys.file.rc. &sysmsg is a text message.
Page 377: Architectural Overview
The Host Resources Subagent supports all the mandatory and two of the optional groups of the standard Host Resources MIB. It also implements several groups defined by HP that maintain information about hardware resources that might require operator attention. These MIB extensions also let you manage the subagent and control the MIB values it maintains.
Page 378: Figure 11-1. Derivation Of Information For Rfc 1514 Support
Host Resources Subagent Standard MIB Groups Figure 11-1 indicates, the subagent uses Guardian and Spooler procedure calls to obtain information for these MIB groups. Figure 11-1. Derivation of Information for RFC 1514 Support hrSWRun Group hrSystem hrDevice hrStorage Group Group Group hrSWRunPerf Group...
Page 379: Mib Extensions
Host Resources Subagent MIB Extensions The standard MIB groups, identified by a check mark in the following list, are members of MIB-II: iso (1) identified-organization (3) dod (6) internet (1) mgmt (2) mib-2 (1) system (1) interfaces (2) at (3) icmp (5) ip (4) tcp (6)
Page 380: Figure 11-2. Derivation Of Information For Rfc 1514 Extensions
Host Resources Subagent MIB Extensions zhrmDevUnavail This group describes hrDevice group devices that are in group a state that may require operator attention. zhrmSaProcess This group provides information on the subagent group process. This group also lets you change the priority of the subagent process, cause the subagent’s backup process to take over and a new backup process to be created, control which NonStop Kernel personality...
Page 381: Proactive Hardware Management
Host Resources Subagent Proactive Hardware Management The group and trap definitions, identified by a check mark in the following list, reside in the zhrm subtree within the subtree registered to HP: iso (1) identified-organization (3) dod (6) internet (1) private (4)
Page 382: Mib Value Management
Host Resources Subagent MIB Value Management A dynamic object timer controls the rate at which hardware status and statistical information is refreshed. Status information describes object states, such as whether a device is up or down. Statistical information includes information such as the current number of system users.
Page 383: Initiating Backup Process Takeover
Monitoring the Open System Services (OSS) File System To start the Host Resources Subagent to an HP NonStop Kernel Open System Services (OSS) environment, use the -u startup parameter:...
Page 384: Related Documents
Host Resources Subagent Related Documents Related Documents The following documents provide information related to the Host Resources Subagent: The EMS Manual describes the Event Management Service (EMS). EMS is a collection of processes, tools, and interfaces that provide event-message collection and distribution in the Distributed Systems Management environment.
Page 385: Installation Steps
The RFC1514A file contains the same definitions as RFC 1514 with several exceptions. DESCRIPTION clauses have been modified to provide information specific to HP systems. Several read-write objects have been redefined as read-only objects to reflect the Host Resource Subagent’s implementation. And several comments have been added to provide a summary of conformance with RFC 1514.
Page 386: Configuration
Host Resources Subagent Configuration Configuration You can configure the behavior of the Host Resources Subagent at startup time or from an SNMP manager after startup. Table 11-1 summarizes the available options. All subagent attributes that can be controlled by setting MIB object values are reinitialized when the subagent is restarted to default values or values specified in startup parameters.
Page 387 Host Resources Subagent Configuration Table 11-1. Host Resources Subagent Configuration Options (page 2 of 3) Startup Para- Settable MIB Object Subagent Attribute meter Name (Group Name) Default Behavior Hardware and software Values maintained for objects all devices and all processes except those associated with products listed under "Starting and Stopping...
Page 388: Starting And Stopping The Subagent
Host Resources Subagent Starting and Stopping the Subagent Table 11-1. Host Resources Subagent Configuration Options (page 3 of 3) Startup Para- Settable MIB Object Subagent Attribute meter Name (Group Name) Default Behavior NonStop Kernel personality to be monitored Guardian zhrmExamineGuardian Guardian file system (zhrmSaProcess group) and processes are...
Page 389 TACL RUN command options. Refer to the TACL Reference Manual for more information about these options. HP recommends using at least the NOWAIT option so that you can resume TACL operations after subagent startup. displays help information.
Page 390 Host Resources Subagent Starting and Stopping the Subagent -a $agent-process is the name of the SNMP agent process from which you want the subagent to receive SNMP manager requests. If not specified, $ZSNMP on the same system as the subagent you specify is assumed. -b backup-cpu specifies that the subagent is to run as a process pair.
Page 391 Host Resources Subagent Starting and Stopping the Subagent Status objects Statistics objects hrProcessorLoad hrDiskStorageCapacity hrPartitionSize The default dynamic refresh rate is every 10 minutes. A value of 0 or less for the dynamic refresh rate suppresses refreshing these values. The dynamic refresh rate is the slowest rate at which values are refreshed. Because of the internal resource access mechanism, the refresh can occur before the configured time has elapsed.
Page 392 Host Resources Subagent Starting and Stopping the Subagent NetView SENTINEL TWORK EDIT OSIMAGE SPOOL EMSDIST PATHCOM SPOOLCOM YOUMAIL FILTER PERUSE SYMSERV PERUSES TACL Devices excluded are not represented in the hrDevice group. Processes associated with program file names excluded are not represented in the hrSWRun or hrSWRunPerf groups.
Page 393 Host Resources Subagent Starting and Stopping the Subagent device-name identifies a device: identifies a CPU. CPUnn identifies a printer. $printer-name identifies a disk. $volume-name identifies a tape drive. $tape-drive-name identifies a network device. $network-device- name program-file-name is an unqualified object file name. To refer to operating system entries (one per CPU), use OS.
Page 394 Host Resources Subagent Starting and Stopping the Subagent MIB-II data is maintained by the SNMP agent you specify when starting the subagent. For example, if SNMP agent process $ZSNMP is supporting MIB objects for the network under the control of TCP/IP process $ZTC0, you build the network interface file and invoke the subagent as follows: SCF /OUT $DATA.MYSUB.IFTBL/ INFO SUBNET $ZTC0.* RUN HMSAX /NAME $HMSA, NOWAIT/ -f $DATA.MYSUB.IFTBL...
Page 395 Host Resources Subagent Starting and Stopping the Subagent After the subagent is started, you can separately manage the low value thresholds for RAM and for disk devices by setting the values of zhrmThrRAMLowValue and zhrmThrDiskLowValue in the zhrmThreshold group. Refer to the discussion under Thresholds and Traps on page 11-100 for more information about the relationship between high and low threshold values and...
Page 396 Host Resources Subagent Starting and Stopping the Subagent hrPartitionID hrPartitionFSIndex hrFSIndex hrFSMountPoint hrFSRemoteMountPoint hrFSType hrFSAccess hrFSBootable hrFSStorageIndex hrFSLastFullBackupDate hrFSLastPartialBackupDate Because these values are relatively stable, the default stable refresh rate is every 1440 minutes (24 hours). A value of 0 or less suppresses refreshing these values.
Page 397: Troubleshooting The Subagent
Host Resources Subagent Troubleshooting the Subagent disables creation and maintenance of hrSWRun and hrSWRunPerf group values. This is true for both the Guardian and OSS personalities. If this parameter is not specified, the subagent creates and maintains values in the hrSWRun and hrSWRunPerf groups for processes as described for the -e startup parameter.
Page 398: Ems Event Messages
Host Resources Subagent EMS Event Messages EMS Event Messages Whenever the subagent behaves unexpectedly or an error condition arises, be sure to check for EMS events that have been generated by the subagent. Described under EMS Support on page 11-104, event messages provide information to help you diagnose and fix problems.
Page 399 Host Resources Subagent Manager Timeouts System Call Suspension If the subagent does not respond in a timely fashion to a manager request but appears to be running, the subagent might be suspended because it cannot complete a system call needed to process the request or refresh MIB values. This situation can occur when the subagent attempts to retrieve MIB values for remote printers if the connection to the remote system, the remote system itself, or a remote printer becomes unstable.
Page 400 Host Resources Subagent Manager Timeouts The -w startup parameter excludes all software processes from the MIB. You can use this startup parameter, but enable or disable software value maintenance as needed by setting the value of zhrmEnableSoftwareGroup in the zhrmSaProcess group.
Page 401: Hrsystem Group
Host Resources Subagent hrSystem Group hrSystem Group The hrSystem group is a collection of scalar objects describing general attributes of the host. The Host Resources Subagent’s MIB supports the objects identified by a check mark in the following list:dod (6) iso (1) identified-organization (3) dod (6)
Page 402: Table 11-2. Hrsystem Group Objects Supported By Host Resources Subagent's Mib
Host Resources Subagent MIB Objects Table 11-2. hrSystem Group Objects Supported by Host Resources Subagent's MIB (page 1 of 2) Format of Object and Attributes Definition Value Derivation of Value hrSystemUpTime Number of Integer Guardian procedure 1.3.6.1.2.1.25.1.1 microseconds without JULIANTIMESTAMP. read-only since system leading 0s.
Page 403: Sample Data
Host Resources Subagent Sample Data Table 11-2. hrSystem Group Objects Supported by Host Resources Subagent's MIB (page 2 of 2) Format of Object and Attributes Definition Value Derivation of Value hrSystemNumUsers Number of Integer Guardian procedure 1.3.6.1.2.1.25.1.5 users running a without PROCESS_GETINFOLIST_.
Page 404: Rfc Compliance
Host Resources Subagent RFC Compliance RFC Compliance Table 11-3. Compliance With hrSystem Group Definitions in RFC 1514 Object Descriptor Compliance Explanation hrSystemUpTime Table 11-2. hrSystemDate Partial Set operation not supported. hrSystemInitialLoadDevice Partial Set operation not supported. hrSystemInitialLoadParameter Partial Set operation not supported. hrSystemNumUsers Table 11-2.
Page 405: Hrstorage Group
Host Resources Subagent hrStorage Group hrStorage Group The hrStorage group consists of one scalar object and one table (the hrStorage table). The objects in this group describe RAM and disks on the host. The Host Resources Subagent’s MIB supports the objects identified by a check mark in the following list: iso (1) identified-organization (3) dod (6)
Page 406: Mib Objects
Host Resources Subagent MIB Objects MIB Objects Table 11-4. hrStorage Group Objects Supported by Host Resources Subagent's MIB (page 1 of 3) Object and Attributes Definition Format of Value Derivation of Value hrMemorySize The total amount Integer without Guardian procedure 1.3.6.1.2.1.25.2.2 of physical leading 0s.
Page 407 Host Resources Subagent MIB Objects Table 11-4. hrStorage Group Objects Supported by Host Resources Subagent's MIB (page 2 of 3) Object and Attributes Definition Format of Value Derivation of Value hrStorageDescr Description of the For RAM: the For physical memory: 1.3.6.1.2.1.25.2.3.1.3 type of storage number and type...
Page 408 Host Resources Subagent MIB Objects Table 11-4. hrStorage Group Objects Supported by Host Resources Subagent's MIB (page 3 of 3) Object and Attributes Definition Format of Value Derivation of Value hrStorageSize The capacity of Integer without For physical memory: 1.3.6.1.2.1.25.2.3.1.5 the entry, in leading 0s.
Page 409: Sample Data
Host Resources Subagent Sample Data Sample Data Time, hrMemorySize 05/22/95 10:33:10, 65536 Time, hrStorageIndex, hrStorageType, hrStorageDescr, hrStorageAllocationUnits, hrStorageSize, hrStorageUsed, hrStorageAllocationFailures 05/22/95 10:33:45, 1, 1.3.6.1.2.1.25.2.1.2, CPU00(NSR-L) running D20.06, 4096, 8192, 8169, 3791 05/22/95 10:33:45, 2, 1.3.6.1.2.1.25.2.1.2, CPU01(NSR-L) running D20.06, 4096, 8192, 6982, 1951 05/22/95 10:33:45, 3, 1.3.6.1.2.1.25.2.1.2, CPU02(unknown), 0, 0, 0, 05/22/95 10:33:45, 4, 1.3.6.1.2.1.25.2.1.2, CPU03(unknown), 0, 0, 0,...
Page 410: Rfc Compliance
Host Resources Subagent RFC Compliance RFC Compliance Table 11-5 summarizes compliance of hrStorage group support with RFC 1514. Table 11-5. Compliance With hrStorage Group Definitions in RFC 1514 Object Descriptor Compliance Explanation hrMemorySize Table 11-4. hrStorageIndex Table 11-4. hrStorageType Table 11-4.
Page 411: Hrdevice Group
When values of hrStorage group objects are refreshed, values for objects in the following groups are also refreshed: The hrSWRun and hrSWRunPerf groups Three of the groups defined by HP: zhrmTableInfo, zhrmThreshold, and zhrmRefresh hrDevice Group The hrDevice group is a large group consisting of a main table (the hrDeviceTable), five dependent tables (hrNetworkTable, hrProcessorTable, hrPrinterTable, hrDiskStorageTable, and hrPartitionTable), and the hrFSTable.
Page 412 Host Resources Subagent hrDevice Group hrDeviceStatus (5) hrDeviceErrors (6) hrProcessorTable (3) hrProcessorEntry (1) hrProcessorFrwID (1) hrProcessorLoad (2) hrNetworkTable (4) hrNetworkEntry (1) hrNetworkIfIndex (1) hrPrinterTable (5) hrPrinterEntry (1) hrPrinterStatus (1) hrPrinterDetectedErrorState (2) hrDiskStorageTable (6) hrDiskStorageEntry (1) hrDiskStorageAccess (1) hrDiskStorageMedia (2) hrDiskStorageRemoveble (3) hrDiskStorageCapacity (4) hrPartitionTable (7) hrPartitionEntry (1)
Page 413 Host Resources Subagent hrDevice Group Two additional tables are related to hrDevice group tables: the ifTable and the hrStorageTable. The ifTable is one of the objects in the Interfaces group, one of the MIB-II groups. The hrStorageTable is described in hrStorage Group on page 11-29.
Page 414: Figure 11-4. Relationship Among Tables In Hrdevice, Hrstorage, And Interfaces Groups
Host Resources Subagent hrDevice Group Figure 11-4. Relationship Among Tables in hrDevice, hrStorage, and Interfaces Groups hrDeviceTable hrProcessorTable hrDeviceIndex hrDeviceIndex hrPrinterTable hrDeviceIndex hrDiskStorageTable hrDeviceIndex hrNetworkTable ifTable hrDeviceIndex ifIndex hrNetworkIfIndex hrPartitionTable hrDeviceIndex hrPartiionIndex hrPartitionFSIndex hrFSTable hrFSIndex hrStorageTable hrFSStorageIndex hrStorageIndex Legend Storage Group Device Group MIB-II Interfaces Group VST1004.vsd...
Page 415: Mib Objects
Host Resources Subagent MIB Objects MIB Objects Table 11-6 describes how the Host Resources Subagent supports objects in the hrDevice group. Table 11-6. hrDevice Group Objects Supported by Host Resources Subagent’s MIB (page 1 of 9) Object and Attributes Definition Format of Value Derivation of Value hrDeviceTable Objects:...
Page 416 Host Resources Subagent MIB Objects Table 11-6. hrDevice Group Objects Supported by Host Resources Subagent’s MIB (page 2 of 9) Object and Attributes Definition Format of Value Derivation of Value hrDeviceDescr Description of the CPUs: CPUnn For CPUs: Guardian 1.3.6.1.2.1.25.3.2.1.3 type of device (CPU--type).
Page 417 Host Resources Subagent MIB Objects Table 11-6. hrDevice Group Objects Supported by Host Resources Subagent’s MIB (page 3 of 9) Object and Attributes Definition Format of Value Derivation of Value hrDeviceStatus The current state of One of the following For CPUs: Guardian 1.3.6.1.2.1.25.3.2.1.5 the device values:...
Page 418 Host Resources Subagent MIB Objects Table 11-6. hrDevice Group Objects Supported by Host Resources Subagent’s MIB (page 4 of 9) Object and Attributes Definition Format of Value Derivation of Value hrProcessorLoad The average Integer without Guardian procedure 1.3.6.1.2.1.25.3.3.1.2 percent of time a leading 0s.
Page 419 Host Resources Subagent MIB Objects Table 11-6. hrDevice Group Objects Supported by Host Resources Subagent’s MIB (page 5 of 9) Object and Attributes Definition Format of Value Derivation of Value hrPrinterStatus The current state of One of the following Spooler procedure 1.3.6.1.2.1.25.3.5.1.1 the printer values:...
Page 420 Host Resources Subagent MIB Objects Table 11-6. hrDevice Group Objects Supported by Host Resources Subagent’s MIB (page 6 of 9) Object and Attributes Definition Format of Value Derivation of Value hrDiskStorageMedia A characterization One of these values: Guardian procedure 1.3.6.1.2.1.25.3.6.1.2 of the type of disk hardDisk DEVICE_...
Page 421 Host Resources Subagent MIB Objects Table 11-6. hrDevice Group Objects Supported by Host Resources Subagent’s MIB (page 7 of 9) Object and Attributes Definition Format of Value Derivation of Value hrPartitionLabel The name of the For Guardian: Guardian procedure 1.3.6.1.2.1.25.3.7.1.2 disk.
Page 422 Host Resources Subagent MIB Objects Table 11-6. hrDevice Group Objects Supported by Host Resources Subagent’s MIB (page 8 of 9) Object and Attributes Definition Format of Value Derivation of Value hrFSRemoteMountPoint Name of the \system name 1.3.6.1.2.1.25.3.8.1.3 system. read-only InternationalDisplayString (SIZE (0..128)) hrFSType An object identifier...
Page 423: Sample Data
Host Resources Subagent Sample Data Table 11-6. hrDevice Group Objects Supported by Host Resources Subagent’s MIB (page 9 of 9) Object and Attributes Definition Format of Value Derivation of Value hrFSStorageIndex An index that has a Integer without Computed by Host 1.3.6.1.2.1.25.3.8.1.7 corresponding leading 0s.
Page 424 Host Resources Subagent Sample Data 05/22/95 10:35:30, 10002, 1.3.6.1.2.1.25.3.1.18, $TAPE4, 1.3.6.1.4.1.169.3.180.4.6, running, 0 Time, hrProcessorFrwID, hrProcessorLoad 05/22/95 10:36:03, 1.3.6.1.4.1.169.3.180, 13 05/22/95 10:36:03, 1.3.6.1.4.1.169.3.180, 1 05/22/95 10:36:03, 1.3.6.1.4.1.169.3.180, 0 05/22/95 10:36:03, 1.3.6.1.4.1.169.3.180, 0 Time, hrNetworkIfIndex 05/22/95, 10:36:15, 2 05/22/95, 10:36:15, 1 Time, hrPrinterStatus, hrPrinterDetectedErrorState 05/22/95, 10:37:00, idle, 00 05/22/95, 10:37:00, printing, 00...
Page 425: Rfc Compliance
Host Resources Subagent RFC Compliance RFC Compliance Table 11-7 summarizes compliance of hrDevice group support with RFC 1514. Table 11-7. Compliance With hrDevice Group Definitions in RFC 1514 Object Descriptor Compliance Explanation hrDeviceIndex Table 11-6. hrDeviceType Table 11-6. hrDeviceDescr Table 11-6.
Page 426: Hrdevice Group Maintenance
Host Resources Subagent hrDevice Group Maintenance hrDevice Group Maintenance Values in the hrDevice group support the following device types: Processors The subagent uses Guardian procedures PROCESSORSTATUS, PROCESSORTYPE, and PROCESSOR_GETINFOLIST_ to construct processor entries in the hrProcessorTable. Network The subagent accesses the network interface file to build interfaces hrNetworkTable entries.
Page 427 Host Resources Subagent hrDevice Group Maintenance The values of hrDeviceStatus in the hrDeviceTable map as follows to device states returned when Guardian and Spooler procedures are called: Device Device State hrDeviceStatus Processors, tapes, and network 2 (running) interfaces down 5 (down) Disks 2 (running) down...
Page 428 When values of hrDevice group objects are refreshed, values for objects in the following groups are also refreshed: The hrSWRun and hrSWRunPerf groups Four of the groups defined by HP: zhrmTableInfo, zhrmDevUnavail, zhrmThreshold, and zhrmRefresh. SNMP Configuration and Management Manual—424777-006...
Page 429: Hrswrun Group
Host Resources Subagent hrSWRun Group hrSWRun Group The hrSWRun group consists of a scalar object and one table (the hrSWRunTable). The objects in this group describe processes running on the host. The Host Resources Subagent’s MIB supports the objects identified by a check mark in the following list: iso (1) identified-organization (3) dod (6)
Page 430: Mib Objects
Host Resources Subagent MIB Objects MIB Objects Table 11-8 describes how the Host Resources Subagent supports objects in the hrSWRun group. Table 11-8. hrSWRun Group Objects Supported by Host Resources Subagent's MIB (page 1 of 4) Object and Attributes Definition Format of Value Derivation of Value hrSWOSIndex...
Page 431 Host Resources Subagent MIB Objects Table 11-8. hrSWRun Group Objects Supported by Host Resources Subagent's MIB (page 2 of 4) Object and Attributes Definition Format of Value Derivation of Value hrSWRunName The unqualified For non-operating system For non-operating 1.3.6.1.2.1.25.4.2.1.2 name of the processes: unqualified file system processes, the read-only...
Page 432 Host Resources Subagent MIB Objects Table 11-8. hrSWRun Group Objects Supported by Host Resources Subagent's MIB (page 3 of 4) Object and Attributes Definition Format of Value Derivation of Value hrSWRunParameters Information A series of values The information is 1.3.6.1.2.1.25.4.2.1.5 describing the describing such process derived by using...
Page 433: Sample Data
Host Resources Subagent Sample Data Table 11-8. hrSWRun Group Objects Supported by Host Resources Subagent's MIB (page 4 of 4) Object and Attributes Definition Format of Value Derivation of Value hrSWRunStatus The state of the One of the following The process state 1.3.6.1.2.1.25.4.2.1.7 process.
Page 434: Rfc Compliance
Host Resources Subagent RFC Compliance $ZNOT-S(0,28) started May 19, 1995 16:57:26.7 by 255,255, application, running 05/22/95 10:39:52, 1029, SYHZSHM, 1.3.6.1.4.1.169.3.180.0, \SHERIFF.$SYSTEM.SYS02.SYHZSHM, $ZSHM-S(0,29) started May 19, 1995 16:57:26.7 by 255,255, application, running 05/22/95 10:39:52, 1042, MLMAN, 1.3.6.1.4.1.169.3.180.0, \SHERIFF.$SYSTEM.SYS02.MLMAN, $ZLMG-B(0,42) started May 20, 1995 17:3:8.8 by 255,255, application, running 05/22/95 10:39:52, 1045, LISTNER, 1.3.6.1.4.1.169.3.180.0, \SHERIFF.$SYSTEM.ZTCPIP.LISTNER,...
Page 435: Hrswrunperf Group
Host Resources Subagent hrSWRunPerf Group You control whether the subagent creates or maintains hrSWRun group objects by using the -w startup parameter or, after startup, by setting the value of zhrmEnableSoftwareGroup in the zhrmSaProcess group: Use the -w startup parameter to suppress creation of hrSWRun group objects. Omit the -w startup parameter to enable object creation.
Page 436: Sample Data
Host Resources Subagent Sample Data Table 11-10. hrSWRunPerf Group Objects Supported by Host Resources Subagent's MIB Object and Format of Attributes Definition Value Derivation of Value hrSWRunPerfTable Entries providing Refer to “hrSWRunPerf Group Objects: performance metrics for Maintenance” later in this resources having section for information on how entries in the hrSWRun...
Page 437: Rfc Compliance
Host Resources Subagent RFC Compliance RFC Compliance Table 11-11 summarizes compliance of hrSWRunPerf group support with RFC 1514. Table 11-11. Compliance With hrSWRunPerf Group Definitions in RFC 1514 Object Descriptor Compliance Explanation hrSWRunPerfCPU Table 11-10. hrSWRunPerfMem Partial For non-operating system entries, the number of kilobytes associated with the memory pages that have been swapped in by the process and that are still resident is returned.
Page 438: Zhrmtableinfo Group
Group zhrmTableInfo Group This group, defined by HP, provides information about the status of operations performed on tables in the hrStorage and hrDevice groups. The zhrmTableInfo group consists of eight groups, each of which contains objects that describe one of the tables...
Page 439 Host Resources Subagent zhrmTableInfo Group zhrmInfDevGetNextCounter (7) zhrmInfDevSetCounter (8) zhrmInfCpuTable (3) zhrmInfCpuEntries (1) zhrmInfCpuFirstIndex (2) zhrmInfCpuLastIndex (3) zhrmInfCpuLastDynamRefresh (4) zhrmInfCpuLastStableRefresh (5) zhrmInfCpuGetCounter (6) zhrmInfCpuGetNextCounter (7) zhrmInfCpuSetCounter (8) zhrmInfNetTable (4) zhrmInfNetEntries (1) zhrmInfNetFirstIndex (2) zhrmInfNetLastIndex (3) zhrmInfNetLastDynamRefresh (4) zhrmInfNetLastStableRefresh (5) zhrmInfNetGetCounter (6) zhrmInfNetGetNextCounter (7) zhrmInfNetSetCounter (8) zhrmInfPrnTable (5)
Page 440: Table 11-12. Zhrmtableinfo Group Objects Supported By Host Resources Subagent's Mib
Host Resources Subagent MIB Objects zhrmInfFSTable (8) zhrmInfFSEntries (1) zhrmInfFSFirstIndex (2) zhrmInfFSLastIndex (3) zhrmInfFSLastDynamRefresh (4) zhrmInfFSLastStableRefresh (5) zhrmInfFSGetCounter (6) zhrmInfFSGetNextCounter (7) zhrmInfFSSetCounter (8) MIB Objects Table 11-12 describes how the Host Resources Subagent supports objects in the zhrmTableInfo group. Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 1 of 12) Object and Attributes Definition...
Page 441 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 2 of 12) Object and Attributes Definition Format of Value Derivation of Value zhrmInfStorLastStableRefresh The system time at month DD, YYYY Guardian procedure 1.3.6.1.4.1.169.3.180.1.1.5 which HH:MM:SS...
Page 442 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 3 of 12) Object and Attributes Definition Format of Value Derivation of Value zhrmInfDevFirstIndex The lowest value of Integer without hrDeviceTable. 1.3.6.1.4.1.169.3.180.1.2.2 hrDeviceIndex. leading 0s.
Page 443 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 4 of 12) Object and Attributes Definition Format of Value Derivation of Value zhrmInfDevSetCounter The number of Set Integer without Computed by Host 1.3.6.1.4.1.169.3.180.1.2.8 operations leading 0s.
Page 444 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 5 of 12) Object and Attributes Definition Format of Value Derivation of Value zhrmInfCpuGetCounter The number of Get Integer without Computed by Host 1.3.6.1.4.1.169.3.180.1.3.6 operations leading 0s.
Page 445 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 6 of 12) Object and Attributes Definition Format of Value Derivation of Value zhrmInfNetLastDynamRefresh The system time at month DD, YYYY Guardian procedure 1.3.6.1.4.1.169.3.180.1.4.4 which HH:MM:SS...
Page 446 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 7 of 12) Object and Attributes Definition Format of Value Derivation of Value zhrmInfPrnTable Group Objects describing Refer to “zhrmTableInfo Objects: the status and Group Maintenance”...
Page 447 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 8 of 12) Object and Attributes Definition Format of Value Derivation of Value zhrmInfPrnGetCounter The number of Get Integer without Computed by Host 1.3.6.1.4.1.169.3.180.1.5.6 operations leading 0s.
Page 448 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 9 of 12) Object and Attributes Definition Format of Value Derivation of Value The system time at month DD, YYYY Guardian procedure zhrmInfDiskLastDynamRefresh which HH:MM:SS JULIANTIMESTAMP.
Page 449 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 10 of 12) Object and Attributes Definition Format of Value Derivation of Value zhrmInfPartTable Group Objects describing Refer to “zhrmTableInfo Objects: the status and Group Maintenance”...
Page 450 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 11 of 12) Object and Attributes Definition Format of Value Derivation of Value zhrmInfPartGetCounter The number of Get Integer without Computed by Host 1.3.6.1.4.1.169.3.180.1.7.6 operations leading 0s.
Page 451 Host Resources Subagent MIB Objects Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 12 of 12) Object and Attributes Definition Format of Value Derivation of Value zhrmInfFSLastDynamRefresh The system time at month DD, YYYY Guardian procedure 1.3.6.1.4.1.169.3.180.1.8.4 which hrFSTable HH:MM:SS...
Page 452: Sample Data
Host Resources Subagent Sample Data Sample Data Time, zhrmInfStorEntries, zhrmInfStorFirstIndex, zhrmInfStorLastIndex, zhrmInfStorLastDynamRefresh, zhrmInfStorLastStableRefresh, zhrmInfStorGetCounter, zhrmInfStorGetNextCounter, zhrmInfStorSetCounter 05/22/95 10:11:25, 14, 1, 10005, May 22, 1995 09:59:48, May 21, 1995 17:20:47, 0, 106, 0 Time, zhrmInfDevEntries, zhrmInfDevFirstIndex, zhrmInfDevLastIndex, zhrmInfDevLastDynamRefresh, zhrmInfDevLastStableRefresh, zhrmInfDevGetCounter, zhrmInfDevGetNextCounter, zhrmInfDevSetCounter 05/22/95 10:13:19, 15, 1, 10002, May 22, 1995 09:59:48, May 21, 1995 17:20:47, 0, 111, 0...
Page 453: Zhrmtableinfo Group Maintenance
Group This group, defined by HP, describes RAM storage areas and disk devices in the hrStorage group, highlighting devices whose usage has reached a critically high level. Several objects in this group let you control whether the subagent sends traps when device utilization is too high.
Page 454: Table 11-13. Zhrmthreshold Group Objects Supported By Host Resources Subagent's Mib
Host Resources Subagent MIB Objects zhrmThrDiskPercentUse (3) zhrmThrDiskTrapEnable (4) zhrmThrDiskHighValue (5) zhrmThrDiskLowValue (6) zhrmThrDiskTable (7) zhrmThrDiskEntry (1) zhrmThrDiskIndex (1) zhrmThrDiskDescr (2) zhrmThrDiskAllocationUnits (3) zhrmThrDiskSize (4) zhrmThrDiskUsed (5) zhrmThrDiskAllocationFailures (6) MIB Objects Table 11-13 describes how the Host Resources Subagent supports objects in the zhrmThreshold group.
Page 455 Host Resources Subagent MIB Objects Table 11-13. zhrmThreshold Group Objects Supported by Host Resources Subagent's MIB (page 2 of 6) Object and Attributes Definition Format of Value Derivation of Value zhrmThrRAMTrapEnable When set to 1 One of these Initialized to 1 1.3.6.1.4.1.169.3.180.2.1.4 (ramTrapsEnabled) a values is...
Page 456 Host Resources Subagent MIB Objects Table 11-13. zhrmThreshold Group Objects Supported by Host Resources Subagent's MIB (page 3 of 6) Object and Attributes Definition Format of Value Derivation of Value zhrmThrRAMTable Objects Entries describing hrStorageTable. RAM in the hrStorageTable whose usage has reached or exceeded the value of zhrmThrRAMHigh...
Page 457 Host Resources Subagent MIB Objects Table 11-13. zhrmThreshold Group Objects Supported by Host Resources Subagent's MIB (page 4 of 6) Object and Attributes Definition Format of Value Derivation of Value zhrmThrRAMAllocationFailures The number of Integer without The value of requests for storage leading 0s, hrStorageAllocation 1.3.6.1.4.1.169.3.180.2.1.7.1.6...
Page 458 Host Resources Subagent MIB Objects Table 11-13. zhrmThreshold Group Objects Supported by Host Resources Subagent's MIB (page 5 of 6) Object and Attributes Definition Format of Value Derivation of Value zhrmThrDiskTrapEnable When set to 1 One of these Initialized to 1 1.3.6.1.4.1.169.3.180.2.2.4 (diskTrapsEnabled) values is...
Page 459 Host Resources Subagent MIB Objects Table 11-13. zhrmThreshold Group Objects Supported by Host Resources Subagent's MIB (page 6 of 6) Object and Attributes Definition Format of Value Derivation of Value zhrmThrDiskTable Objects Entries describing hrStorageTable. writable disks in the hrStorageTable whose usage has reached or exceeded the value of...
Page 460: Sample Data
Host Resources Subagent Sample Data Sample Data Time, zhrmThrRAMTotal, zhrmThrRAMUse, zhrmThrRAMPercentUse, zhrmThrRAMTrapEnable, zhrmThrRAMHighValue, zhrmThrRAMLowValue 05/22/95 10:19:41, 64, 59, 92, ramTrapsEnabled, 90, Time, zhrmThrRAMIndex, zhrmThrRAMDescr, zhrmThrRAMAllocationUnits, zhrmThrRAMSize, zhrmThrRAMUsed, zhrmThrRAMAllocationFailures 05/22/95 10:20:10, 1, CPU00 (NSR-L) running D20.06, 4096, 8192, 8169, 4047 Time, zhrmThrDiskTotal, zhrmThrDiskUse, zhrmThrDiskPercentUse, zhrmThrDiskTrapEnable, zhrmThrDiskHighValue, zhrmThrDiskLowValue 05/22/95 10:20:48, 4047, 2824, 69, diskTrapsEnabled, 90,...
Page 461: Zhrmdevunavail Group
Group zhrmDevUnavail Group This group, defined by HP, provides summary information about devices that are in a state that might require operator attention. MIB values reflect devices represented in the hrDevice group. One object in this group lets you control whether the subagent sends traps when the state of a device changes.
Page 462: Table 11-14. Zhrmdevunavail Group Objects Supported By Host Resources Subagent's Mib
Host Resources Subagent MIB Objects Table 11-14. zhrmDevUnavail Group Objects Supported by Host Resources Subagent's MIB (page 1 of 4) Object and Attributes Definition Format of Value Derivation of Value zhrmDevUnCurrTime The current system month DD, YYYY Guardian procedure 1.3.6.1.4.1.169.3.180.3.1 time.
Page 463 Host Resources Subagent MIB Objects Table 11-14. zhrmDevUnavail Group Objects Supported by Host Resources Subagent's MIB (page 2 of 4) Object and Attributes Definition Format of Value Derivation of Value zhrmDevUnIndex Index values that Integers running The value of point to entries in the sequentially from 1.
Page 464 Host Resources Subagent MIB Objects Table 11-14. zhrmDevUnavail Group Objects Supported by Host Resources Subagent's MIB (page 3 of 4) Object and Attributes Definition Format of Value Derivation of Value zhrmDevUnDescr Description of the For CPUs: the The value of type of device number and type: hrDeviceDescr for...
Page 465 Host Resources Subagent MIB Objects Table 11-14. zhrmDevUnavail Group Objects Supported by Host Resources Subagent's MIB (page 4 of 4) Object and Attributes Definition Format of Value Derivation of Value zhrmDevUnID An identifier The root of the The value of characterizing the identifier is the same hrDeviceID for...
Page 466: Sample Data
Host Resources Subagent Sample Data Sample Data Time, zhrmDevUnCurrTime, zhrmDevUnUp, zhrmDevUnDown, zhrmDevUnOther, zhrmDevUnTrapEnable 05/22/95 10:25:57, May 22, 1995 10:18:51, 13, 2, 0, devUnTrapsEnabled Time, zhrmDevUnIndex, zhrmDevUnType, zhrmDevUnDescr, zhrmDevUnID, zhrmDevUnStatus, zhrmDevUnErrors 05/22/95 10:26:19, 1, 1.3.6.1.2.1.25.3.1.3, CPU02(unknown), 1.3.6.1.4.1.169.3.180.0.6, down, 1 05/22/95 10:26:19, 2, 1.3.6.1.2.1.25.3.1.3, CPU03(unknown), 1.3.6.1.4.1.169.3.180.0.6, down, 1 zhrmDevUnavail Group Maintenance Most zhrmDevUnavail group values are derived from hrDevice group values as...
Page 467: Zhrmsaprocess Group
Group zhrmSaProcess Group This group, defined by HP, provides information about the subagent process and lets you change the priority at which it runs. It also lets you cause the subagent’s backup process to take over and a new backup process to be created. This procedure offers a way to refresh all MIB values in one step.
Page 468: Table 11-15. Zhrmsaprocess Group Objects Supported By Host Resources Subagent's Mib
HH:MM:SS JULIANTIMESTAMP. read-only DisplayString zhrmSaProcVersion The version of T8496Dnn_date -- Host Resources 1.3.6.1.4.1.169.3.180.4.2 the Host HP Host Resources Subagent. read-only Resources Subagent DisplayString Subagent. Where Dnn is the product version of the Host Resources Subagent; for example, D21.
Page 469 Host Resources Subagent MIB Objects Table 11-15. zhrmSaProcess Group Objects Supported by Host Resources Subagent's MIB (page 2 of 3) Object and Attributes Definition Format of Value Derivation of Value zhrmSaHomeTerm The name of the \node.$device-name. Guardian procedure 1.3.6.1.4.1.169.3.180.4.9 terminal from #subdevice-name PROCESS_GETINFO_.
Page 470: Sample Data
Host Resources Subagent Sample Data Table 11-15. zhrmSaProcess Group Objects Supported by Host Resources Subagent's MIB (page 3 of 3) Object and Attributes Definition Format of Value Derivation of Value zhrmEnableSoftwareGroup A switch that One of these values is At startup, the subagent suppresses displayed: sets this value to 1...
Page 471: Zhrmsaprocess Group Maintenance
Host Resources Subagent zhrmSaProcess Group Maintenance zhrmSaProcess Group Maintenance The zhrmSaProcess group values are updated: At subagent startup time. The values of MIB objects associated with startup parameters and startup process attributes are initialized. The counters that tally the requests handled by the subagent as well as the values of zhrmSaCpuTime and zhrmSaHeapCurrent are updated as requests are received.
Page 472: Zhrmrefresh Group
Group zhrmRefresh Group This group, defined by HP, provides information about MIB value refreshes and supports on-demand refreshes of MIB values. The zhrmRefresh group consists of a series of scalar objects. Objects in the zhrmRefresh group are identified by a check...
Page 473: Table 11-16. Zhrmrefresh Group Objects Supported By Host Resources Subagent's Mib
Host Resources Subagent MIB Objects Table 11-16. zhrmRefresh Group Objects Supported by Host Resources Subagent's MIB (page 1 of 2) Object and Attributes Definition Format of Value Derivation of Value zhrmRefreshCurrTime The current system month DD, YYYY Guardian procedure 1.3.6.1.4.1.169.3.180.5.1 time.
Page 474: Sample Data
Host Resources Subagent Sample Data Table 11-16. zhrmRefresh Group Objects Supported by Host Resources Subagent's MIB (page 2 of 2) Object and Attributes Definition Format of Value Derivation of Value zhrmStableRefreshCnt The number of times Integer without Computed by Host 1.3.6.1.4.1.169.3.180.5.7 since the subagent leading 0s.
Page 475: Traps
Host Resources Subagent Traps Traps You can configure the Host Resources Subagent to generate traps when noteworthy hardware conditions occur. Three traps are defined in the subagent’s MIB: zhrmTrapDeviceStateChange. This trap identifies a cpu, printer, disk, or tape drive that might require operation attention. zhrmRAMThreshold.
Page 476: Routing Traps
Host Resources Subagent Routing Traps Routing Traps Traps from the Host Resources Subagent are routed to SNMP managers identified in the SNMP agent’s TRAPDEST objects. Refer to Configuring Trap Destinations page 2-38 for more information on this topic. Enabling Traps By default, all subagent traps are enabled whenever the subagent is started.
Page 477: Trap Pdu
Host Resources Subagent Trap PDU You can change the high and low threshold values while the subagent is running by setting the values of zhrmThrRAMHighValue and zhrmThrRAMLowValue (for RAM storage areas) and zhrmThrDiskHighValue and zhrmDiskLowValue (for disks) in the zhrmThreshold group. If a threshold is changed such that a trap would be generated at the current activity level, a trap is not generated until the activity level changes.
Page 478: Zhrmtrapdevicestatechange Trap
Host Resources Subagent zhrmTrapDeviceStateChange Trap zhrmTrapDeviceStateChange Trap When zhrmDevUnTrapEnable is set to 1, this trap is generated whenever the status of any device represented in the hrDevice group changes. Table 11-17 describes the MIB objects constituting the variable bindings of this trap. Table 11-17.
Page 479: Zhrmramthreshold Trap
Host Resources Subagent zhrmRAMThreshold Trap zhrmRAMThreshold Trap When zhrmThrRAMTrapEnable is set to 1, this trap is generated whenever the utilization of any RAM storage area represented in the hrStorage group: Reaches or exceeds a high threshold, represented by the value of zhrmThrRAMHighValue in the zhrmThreshold group Reaches or falls below a low threshold, represented by the value of zhrmThrRAMLowValue in the zhrmThreshold group...
Page 480: Ems Support
Host Resources Subagent EMS Support Table 11-19. Variable Bindings in the zhrmDiskThreshold Trap Object and Attributes Definition Format of Value Derivation of Value zhrmTrapStorageThrIndex Index value that Integer, numbered The value of 1.3.6.1.4.1.169.3.180.7.4 points to the entry in sequentially starting zhrmThrDiskIndex for not-accessible the hrStorageTable for...
Page 481: Data Definitions
Host Resources Subagent Data Definitions Data Definitions Because they are standard events, most of the tokens, structures, and values appearing in ZHRM events are defined in the ZSPI and ZEMS data definition files ZSPIDDL and ZEMSDDL and their associated language-specific files. Data elements defined by the Host Resources Subagent are in the file ZHRMDDL and associated language-specific files: ZHRMDDL...
Page 482: Table 11-21. Zhrm Tokens In Zhrm Event Messages
Host Resources Subagent Tokens in ZHRM Event Messages Host Resources Subagent (ZHRM) Tokens Table 11-21 lists all the tokens defined by the subagent. These tokens are defined in the ZHRMDDL definition file and are described where they appear in the event message descriptions later in this section.
Page 483: Event Message Descriptions
Host Resources Subagent Event Message Descriptions Table 11-23. ZEMS Tokens in ZHRM Event Messages (page 2 of 2) Token Contents ZEMS-TKN-LOGTIME Event log time ZEMS-TKN-NAME-MANAGER Manager process name ZEMS-TKN-NODENUM System number of event sender ZEMS-TKN-PIN PIN of event sender ZEMS-TKN-SUBJECT-MARK Event subject marker ZEMS-TKN-SUPPRESS-DISPLAY Display/don’t display event flag...
Page 484: 001: Zhrm-Evt-Hrm-Sa-Terminated
Host Resources Subagent 001: ZHRM-EVT-HRM-SA-TERMINATED The Event-Message text that is generated when the contents of the event message are displayed according to the message template defined in the file ZHRMTMPL. <n> shows where text appears that is derived from a token in the token list. For a complete specification of the message, examine the message template source file SHRMTMPL.
Page 485: 002: Zhrm-Evt-Hrm-Sa-Started
Host Resources Subagent 002: ZHRM-EVT-HRM-SA-STARTED ZHRM-VAL-CR-reason is one of the following causes. The DDL AS clause associated with this value is inserted in the message text following “cause:” Associated Text (DDL AS Value of ZEMS-TKN-CHANGE-REASON clause) ZHRM-VAL-CR-PROCESS-SIGILL “Instruction failure” ZHRM-VAL-CR-PROCESS-SIGABRT “Process aborted”...
Page 486 Host Resources Subagent 002: ZHRM-EVT-HRM-SA-STARTED Conditional Tokens None Message Text Object Available - Host Resources Subagent process <1>, event number: <2>, reason: <3>, previous state: <4>, current state: <5> ZHRM-TKN-SUBJ-HRM-SA identifies the subject of the event (always the Host Resources Subagent process). The DDL heading of this token (“Host Resources Subagent process”) and the token’s value (the name of the process) are inserted in the message text.
Page 487: 003: Zhrm-Evt-Hrm-Sa-Io-Err
Host Resources Subagent 003: ZHRM-EVT-HRM-SA-IO-ERR 003: ZHRM-EVT-HRM-SA-IO-ERR The Host Resources Subagent process encountered an I/O error. Unconditional Tokens Value ZEMS-TKN-EVENTNUMBER <1> Subagent process name ZEMS-TKN-TXFAULT-TYPE <2> ZHRM-EVT-HRM-SA-IO-ERR ZHRM-TKN-SUBJ-HRM-SA <3> ZHRM-VAL-TF-IO Conditional Tokens Value ZHRM-TKN-FS-ERR <4> error code and subcode ZHRM-TKN-FILE-NAME <5>...
Page 488 Host Resources Subagent 003: ZHRM-EVT-HRM-SA-IO-ERR ZHRM-TKN-FS-ERR contains the file system error code and subcode, documented in the Guardian Procedure Errors and Messages Manual. The token is based on this structure: DEFINITION ZHRM-DDL-FS-ERR. 02 ERR-CODE TYPE ZSPI-DDL-INT HEADING 'error code' 02 ERR-SUBCODE TYPE ZSPI-DDL-INT HEADING 'error subcode' END.
Page 489: 004: Zhrm-Evt-Hrm-Sa-No-Mem-Space
Host Resources Subagent 004: ZHRM-EVT-HRM-SA-NO-MEM-SPACE 004: ZHRM-EVT-HRM-SA-NO-MEM-SPACE The Host Resources Subagent process ran out of memory. Unconditional Tokens Value ZHRM-TKN-SUBJ-HRM-SA <1> Subagent process name ZEMS-TKN-EVENTNUMBER <2> ZHRM-EVT-HRM-SA-NO-MEM- ZEMS-TKN-TXFAULT-TYPE SPACE <3> ZHRM-VAL-TF-MEM Conditional Tokens None Message Text Transient Fault - Host Resources Subagent process <1>, event number: <2>, fault type: <3>...
Page 490: 005: Zhrm-Evt-Hrm-Sa-Prog-Err
Host Resources Subagent 005: ZHRM-EVT-HRM-SA-PROG-ERR If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well. Sample Message 95-03-10 16:34:20 \COMM.$HMSA TANDEM.HRM.D21 000004 Transient Fault - Host Resources Subagent process \COMM.$HMSA, event number: Process No Memory Space,...
Page 491: Related Operating System Event Messages
Host Resources Subagent Related Operating System Event Messages Effect. The process might or might not be able to recover from the error. If the primary subagent process cannot recover, its backup process should take over. If recovery is successful, an event announcing the takeover is generated. If the error is not recoverable and the process terminates, additional events are generated.
Page 492: Converting Events To Traps
Host Resources Subagent Converting Events to Traps Process Activated Event A “Process Activated” event is reported for a process whenever the process is activated. Converting Events to Traps Any process that generates events, including the Host Resources Subagent, can have its events translated into traps by the EMS Trap Subagent, which uses an event filter known as a routing distributor filter to determine where to route trap messages.
Page 493: Trap Multiplexer Subagent/Manager
Trap Multiplexer Subagent/Manager The Trap Multiplexer is both a manager and a subagent. As a manager, the Trap Multiplexer receives traps from network devices. It converts the traps into Event Management Service (EMS) events, which can be accessed by NonStop management applications or viewed on devices of different types.
Page 494: Figure 12-1. Trap Multiplexer Functions And Components
Trap Multiplexer Subagent/Manager Trap-to-Event Conversion How the Trap Multiplexer maps traps into EMS events and what each process-oriented and trap-oriented event and its tokens look like are topics in EMS Messages page 12-21. Figure 12-1. Trap Multiplexer Functions and Components Management Primary or Applications...
Page 495: Snmp Request Processing
Trap Multiplexer Subagent/Manager SNMP Request Processing SNMP Request Processing In its subagent role, the Trap Multiplexer provides a MIB that SNMP managers can access by routing requests through a SNMP agent that resides either on the same host as the Trap Multiplexer or on a remote node. The Trap Multiplexer’s MIB, which resides in the subtree registered to Tandem, is organized into two groups, identified by a check mark in the following list: iso (1)
Page 496: Installation
Trap Multiplexer Subagent/Manager Installation Installation This subsection describes how to install the Trap Multiplexer. Dependencies The following products must be configured and running for the Trap Multiplexer to operate properly: SNMP agent (D22 or later) EMS (D21 or later) DSM Template Services (D21 or later) TCP/IP (D21 or later) To access the Trap Multiplexer’s MIB, you need at least one SNMP manager that can send requests to the SNMP agent for processing by the Trap Multiplexer.
Page 497: Table 12-1. Trap Multiplexer Configuration Options
Trap Multiplexer Subagent/Manager Configuration The Trap Multiplexer attributes that can be controlled by setting MIB object values are reinitialized when the Trap Multiplexer is restarted to default values or values specified in startup parameters. Refer to Starting and Stopping the Trap Multiplexer on page 12-6 for information on configuration using RUN startup parameters.
Page 498: Starting And Stopping The Trap Multiplexer
Trap Multiplexer Subagent/Manager Starting and Stopping the Trap Multiplexer Starting and Stopping the Trap Multiplexer To use the subagent functions of the Trap Multiplexer, the SNMP agent must be running before the Trap Multiplexer is started. If the agent is not running, start it with the RUN command: RUN SNMPAGT /NAME $agent-process, NOWAIT/ For complete information on starting the SNMP agent, refer to...
Page 499 TACL RUN command options. Refer to the TACL Reference Manual for more information about these options. HP recommends using at least the NOWAIT option so that you can resume TACL operations once the subagent is started.
Page 500 Trap Multiplexer Subagent/Manager Starting and Stopping the Trap Multiplexer -n process-priority sets the initial process priority of the Trap Multiplexer. If this parameter is not specified, the default initial priority is 145. If the Trap Multiplexer is run as a process pair, this priority applies to both primary and backup processes.
Page 501 Trap Multiplexer Subagent/Manager Starting and Stopping the Trap Multiplexer If you omit the -k startup parameter, the subagent tries to establish lost connections every 15 minutes. To change the time interval after the Trap Multiplexer is started, set the value of ztmxProcKeepAliveTimer in the ztmxProcess group.
Page 502: Using The -T And Param Startup Parameters
Trap Multiplexer Subagent/Manager Using the -t and PARAM Startup Parameters Using the -t and PARAM Startup Parameters For Parallel Library TCP/IP compatibility, you can specify IP addresses along with the TCP/IP process names. The format is: -t ([ tcpip-proc-name ] [, tcpip-proc-name ] ... ) where tcpip-proc-name is: $ tcpip-process-name ($ tcpip-process-name:ip-address1 [, ip-address2 ] )
Page 503 Trap Multiplexer Subagent/Manager Using the -t and PARAM Startup Parameters Examples Using Only -t Startup Parameter RUN SNMPTMUX /NAME $ZTMUX/ -t ($ZTC0, ($ZTC1:192.168.10.31)) RUN SNMPTMUX /NAME $ZTMUX/ -t ($ZTC0, ($ZTC1:192.168.10.42,192.168.10.43)) RUN SNMPTMUX /NAME $ZTMUX/ -t 192.168.12.4 Using Only PARAMs PARAM ZSMP^TCPIP^NAME $ztc2 PARAM ZSMP^TCPIP^ADDR 192.168.10.44 RUN SNMPTMUX /NAME $ZTMUX/ Using Both -t Startup Parameter and PARAMs...
Page 504: Ztmxpdustatistics Group
Trap Multiplexer Subagent/Manager ztmxPDUStatistics Group ztmxPDUStatistics Group The ztmxPDUStatistics group contains a collection of scalar objects describing the PDUs processed by the Trap Multiplexer. It also contains a group (ztmxTrapStatistics) of objects providing counts of the various kinds of traps received. The ztmxPDUStatistics group contains the objects identified by a check mark in the following list: iso (1)
Page 505: Table 12-2. Ztmxpdustatistics Group Objects Supported By Trap Multiplexer's Mib
Trap Multiplexer Subagent/Manager MIB Objects Table 12-2. ztmxPDUStatistics Group Objects Supported by Trap Multiplexer’s MIB (page 1 of 3) Format of Derivation of Object and Attributes Definition Value Value ztmxUdpStatsCurrTime The system time when a month DD, Guardian procedure 1.3.6.1.4.1.169.3.185.1.1 Get operation is performed YYYY JULIANTIMESTAMP.
Page 506 Trap Multiplexer Subagent/Manager MIB Objects Table 12-2. ztmxPDUStatistics Group Objects Supported by Trap Multiplexer’s MIB (page 2 of 3) Format of Derivation of Object and Attributes Definition Value Value ztmxTrapStatsCurrTime The system time when a month DD, Guardian procedure 1.3.6.1.4.1.169.3.185.1.9.1 Get operation is performed YYYY JULIANTIMESTAMP.
Page 507: Ztmxpdustatistics Group Maintenance
Trap Multiplexer Subagent/Manager ztmxPDUStatistics Group Maintenance Table 12-2. ztmxPDUStatistics Group Objects Supported by Trap Multiplexer’s MIB (page 3 of 3) Format of Derivation of Object and Attributes Definition Value Value ztmxInAuthFailTraps The total number of Integer Trap Multiplexer. authenticationFailure without 1.3.6.1.4.1.169.3.185.1.9.6 traps received by the leading 0s.
Page 508: Ztmxprocess Group
Trap Multiplexer Subagent/Manager ztmxProcess Group ztmxProcess Group This group provides information about the Trap Multiplexer process. It also lets you change the priority at which the process runs and force a backup process to take over on demand. The ztmxProcess group consists of a series of scalar objects, identified by a check mark in the following list: iso (1) identified-organization (3)
Page 509: Table 12-3. Ztmxprocess Group Objects Supported By Trap Multiplexer's Mib
HH:MM:SS JULIANTIMESTAMP. read-only DisplayString ztmxProcVersion The version of T1041Dnn_date -- Trap Multiplexer. 1.3.6.1.4.1.169.3.185.2.2 the Trap HP SNMP Trap read-only Multiplexer. Multiplexer DisplayString Where Dnn is the product version of the Trap Multiplexer; for example, D20. ztmxProcName The name of the...
Page 510 Trap Multiplexer Subagent/Manager MIB Objects Table 12-3. ztmxProcess Group Objects Supported by Trap Multiplexer’s MIB (page 2 of 4) Object and Attributes Definition Format of Value Derivation of Value ztmxProcPri The priority of the Integer without leading 0s. Initially, the value of 1.3.6.1.4.1.169.3.185.2.9 Trap Multiplexer the -n startup...
Page 511 Trap Multiplexer Subagent/Manager MIB Objects Table 12-3. ztmxProcess Group Objects Supported by Trap Multiplexer’s MIB (page 3 of 4) Object and Attributes Definition Format of Value Derivation of Value ztmxProcAgentSessionStat The status of the One of these values is Trap Multiplexer. session between displayed: the Trap...
Page 512: Ztmxprocess Group Maintenance
Trap Multiplexer Subagent/Manager ztmxProcess Group Maintenance Table 12-3. ztmxProcess Group Objects Supported by Trap Multiplexer’s MIB (page 4 of 4) Object and Attributes Definition Format of Value Derivation of Value ztmxProcEmsWriteTotal The total number Integer without leading 0s. Trap Multiplexer. of attempts to 1.3.6.1.4.1.169.3.185.2.20 write an event...
Page 513: Ems Messages
Trap Multiplexer Subagent/Manager EMS Messages When the value of ztmxSwitchToBackupNow is set to a 1. If a backup process exists, the Trap Multiplexer’s backup process takes over, refreshing all values in the Trap Multiplexer’s MIB before handling SNMP manager requests or processing incoming traps.
Page 514: Figure 12-2. Mapping Of Trap Header Variables To Ems Event Tokens
Trap Multiplexer Subagent/Manager Event Summary Variable bindings are mapped to a collection of EMS tokens grouped into a series of lists. The first token in the list describes the number of variable bindings (varbinds) in the trap PDU. If this value is greater than 0, a nested list of tokens is used to describe each varbind;...
Page 515 Trap Multiplexer Subagent/Manager Event Summary Table 12-5 summarizes the layout of tokens in an EMS event generated from a trap. Table 12-5. Trap Event Token Summary (page 1 of 2) EMS Token Contents ZEMS-TKN-EVENTNUMBER The event number: 0 ZTMX-EVT-TRAP-COLDSTART 1 ZTMX-EVT-TRAP-WARMSTART 2 ZTMX-EVT-TRAP-LINKDOWN 3 ZTMX-EVT-TRAP-LINKUP 4 ZTMX-EVT-TRAP-AUTH-FAIL...
Page 516 Trap Multiplexer Subagent/Manager Event Summary Table 12-5. Trap Event Token Summary (continued) (page 2 of 2) EMS Token Contents One of the following lists for each varbind in the trap PDU: ZSPI-TKN-DATALIST A marker indicating the start of a token list describing one varbind ZTMX-TKN-TRAP-VARBIND-OID The object identifier of the varbind, from the trap...
Page 517: Data Definitions
Trap Multiplexer Subagent/Manager Data Definitions Process Events The process events are listed in Table 12-6. All the process events are standard events, as the table indicates. See the EMS Manual for a complete description of standard events. Table 12-6. Trap Multiplexer Process Event Messages Number Event Standard Event...
Page 518: Subsystem Id
Trap Multiplexer Subagent/Manager Subsystem ID Subsystem ID CONSTANT ZTMX-VAL-VERSION VALUE VERSION "D20". CONSTANT ZSPI-SSN-ZTMX VALUE 185. DEFINITION ZTMX-VAL-SSID TACL SSID. 02 z-filler TYPE character 8 VALUE IS ZSPI-VAL-TANDEM. 02 z-owner TYPE ZSPI-DDL-CHAR8 REDEFINES z-filler. 02 z-number TYPE ZSPI-DDL-INT VALUE IS ZSPI-SSN-ZTMX. 02 z-version TYPE ZSPI-DDL-UINT VALUE IS ZTMX-VAL- VERSION.
Page 519: Table 12-8. Zspi Tokens In Ztmx Event Messages
Trap Multiplexer Subagent/Manager Tokens in ZTMX Event Messages Table 12-7. ZTMX Tokens in ZTMX Event Messages (page 2 of 2) Token Contents ZTMX-TKN-TRAP-SMI-OCTETSTRING Value of a varbind with a data type of OctetString ZTMX-TKN-TRAP-SMI-OID Value of a varbind with a data type of OBJECT IDENTIFIER ZTMX-TKN-TRAP-SMI-OPAQUE Value of a varbind with a data type of...
Page 520: Trap Event Message Descriptions
Trap Multiplexer Subagent/Manager Trap Event Message Descriptions Table 12-9. ZEMS Tokens in ZTMX Event Messages Token Contents ZEMS-TKN-BATCHJOB-ID Batch job ID of process ZEMS-TKN-CONTENT-STANDARD Type of standard event ZEMS-TKN-CONTENT-USER Type of user-defined event ZEMS-TKN-CPU CPU number of event sender ZEMS-TKN-EMPHASIS Critical/Noncritical event flag ZEMS-TKN-EVENTNUMBER Event number...
Page 521 Trap Multiplexer Subagent/Manager Trap Event Message Descriptions Tokens not defined by ZTMX are listed only if they contain information that appears in the printed message text or if they contain ZTMX-defined values. The event message text illustrates what is generated when the contents of the event message are displayed according to the message template defined in the file ZTMXTMPL.
Page 522 Trap Multiplexer Subagent/Manager Trap Event Message Descriptions Message Text With Varbinds <1> trap type - SNMP-Trap-Multiplexer - <2>, Version: <3>, Community: <4>, Enterprise: <5>, Network addr: <6>, Generic trap: <7>, Specific trap: <8>, Time ticks: <9>, (varbind 1 OID=<10>, type=<11>, value=<12>), ... (varbind n OID=<10>, type=<11>, value=<12>) ZTMX-TKN-SUBJ-TMX identifies the subject of the event (always the Trap Multiplexer process).
Page 523 Trap Multiplexer Subagent/Manager Trap Event Message Descriptions ZTMX-TKN-TRAP-TIMETICKS is the value in the time-stamp field of the trap PDU, the value of sysDescr.sysUpTime.0 at trap generation. In the message text, it follows the string “Time ticks:” ZTMX-TKN-TRAP-VARBIND-COUNT is the number of varbinds in the trap. ZTMX-TKN-TRAP-VARBIND-OID is the object identifier of a varbind in the trap.
Page 524: 000: Ztmx-Evt-Trap-Coldstart
Trap Multiplexer Subagent/Manager 000: ZTMX-EVT-TRAP-COLDSTART ZTMX-TKN-TRAP-SMI-TIMETICKS is the value of a varbind with a data type of TimeTicks. In the message text, it follows the string “value=”. ZTMX-TKN-TRAP-SMI-OPAQUE is the value of a varbind with a data type of Opaque. In the message text, it follows the string “value=”.
Page 525: 001: Ztmx-Evt-Trap-Warmstart
Trap Multiplexer Subagent/Manager 001: ZTMX-EVT-TRAP-WARMSTART Sample Message 96-07-26 10:18:36 \COMM.$ZTMX TANDEM.TRAPMUX.D31 000000 Coldstart Trap - SNMP-Trap-Multiplexer $ZTMX, Version: 0, Community: public, Enterprise: 1.3.6.1.4.1.169.2.2.66.0, Network addr: 130.252.12.3, Generic trap: 0, Specific trap: 0, Time ticks: 45366736 (no varbinds) 001: ZTMX-EVT-TRAP-WARMSTART The Trap Multiplexer received a warmStart trap. Unconditional Tokens Value ZEMS-TKN-EVENTNUMBER...
Page 526: 002: Ztmx-Evt-Trap-Linkdown
Trap Multiplexer Subagent/Manager 002: ZTMX-EVT-TRAP-LINKDOWN Sample Message 96-07-26 10:20:12 \COMM.$ZTMX TANDEM.TRAPMUX.D31 000001 Warmstart Trap - SNMP-Trap-Multiplexer $ZTMX, Version: 0, Community: public, Enterprise: 1.3.6.1.4.1.169.2.2.66.0, Network addr: 130.252.12.3, Generic trap: 1, Specific trap: 0, Time ticks: 45366736 (no varbinds) 002: ZTMX-EVT-TRAP-LINKDOWN The Trap Multiplexer received a linkDown trap. Unconditional Tokens Value ZEMS-TKN-EVENTNUMBER...
Page 527: 003: Ztmx-Evt-Trap-Linkup
Trap Multiplexer Subagent/Manager 003: ZTMX-EVT-TRAP-LINKUP Sample Message 96-07-26 10:22:45 \COMM.$ZTMX TANDEM.TRAPMUX.D31 000002 Link Down Trap - SNMP-Trap-Multiplexer $ZTMX, Version: 0, Community: public, Enterprise: 1.3.6.1.4.1.169.2.2.66.0, Network addr: 130.252.12.3, Generic trap: 2, Specific trap: 0, Time ticks: 45366736 (no varbinds) 003: ZTMX-EVT-TRAP-LINKUP The Trap Multiplexer received a linkUp trap.
Page 528: 004: Ztmx-Evt-Trap-Auth-Fail
Trap Multiplexer Subagent/Manager 004: ZTMX-EVT-TRAP-AUTH-FAIL Sample Message 96-07-26 10:26:36 \COMM.$ZTMX TANDEM.TRAPMUX.D31 000003 Link Up Trap - SNMP-Trap-Multiplexer $ZTMX, Version: 0, Community: public, Enterprise: 1.3.6.1.4.1.169.2.2.66.0, Network addr: 130.252.12.3, Generic trap: 3, Specific trap: 0, Time ticks: 45366736 (no varbinds) 004: ZTMX-EVT-TRAP-AUTH-FAIL The Trap Multiplexer received an authenticationFailure trap.
Page 529: 005: Ztmx-Evt-Trap-Egp-Loss
Trap Multiplexer Subagent/Manager 005: ZTMX-EVT-TRAP-EGP-LOSS Sample Message 96-07-26 10:30:09 \COMM.$ZTMX TANDEM.TRAPMUX.D31 000004 Authentication Failure Trap - SNMP-Trap-Multiplexer $ZTMX, Version: 0, Community: public, Enterprise: 1.3.6.1.4.1.169.2.2.66.0, Network addr: 130.252.12.3, Generic trap: 4, Specific trap: 0, Time ticks: 45366736 (no varbinds) 005: ZTMX-EVT-TRAP-EGP-LOSS The Trap Multiplexer received an egpNeighborLoss trap.
Page 530: 006: Ztmx-Evt-Trap-Ent-Spfc
Trap Multiplexer Subagent/Manager 006: ZTMX-EVT-TRAP-ENT-SPFC Sample Message 96-07-26 10:31:44 \COMM.$ZTMX TANDEM.TRAPMUX.D31 000005 Exterior Gateway Protocol Neighbor Loss Trap - SNMP-Trap-Multiplexer $ZTMX, Version: 0, Community: public, Enterprise: 1.3.6.1.4.1.169.2.2.66.0, Network addr: 130.252.12.3, Generic trap: 5, Specific trap: 0, Time ticks: 45366736 (no varbinds) 006: ZTMX-EVT-TRAP-ENT-SPFC The Trap Multiplexer received an enterpriseSpecific trap.
Page 531: Process Event Message Descriptions
Trap Multiplexer Subagent/Manager Process Event Message Descriptions Sample Message The following messages were generated from two traps received from the Host Resources Subagent, described in Section 11, Host Resources Subagent. 96-07-26 11:11:02 \COMM.$ZTMX TANDEM.TRAPMUX.D31 000006 Enterprise Specific Trap - SNMP-Trap-Multiplexer $ZTMX, Version: 0, Community: public, Enterprise: 1.3.6.1.4.1.169.3.180.7, Network addr: 130.252.109.237, Generic...
Page 532: 101: Ztmx-Evt-Tmx-Terminated
Trap Multiplexer Subagent/Manager 101: ZTMX-EVT-TMX-TERMINATED Recovery procedures you can follow to solve the problem reported by the event message. An example of the formatted message. 101: ZTMX-EVT-TMX-TERMINATED The Trap Multiplexer process terminated normally. Unconditional Tokens Value ZTMX-TKN-SUBJ-TMX <1> Trap Multiplexer process ZEMS-TKN-EVENTNUMBER name ZEMS-TKN-CHANGE-REASON...
Page 533 Trap Multiplexer Subagent/Manager 101: ZTMX-EVT-TMX-TERMINATED ZTMX-VAL-CR-reason is one of the causes following below. The DDL AS clause associated with this value is inserted in the message text following “cause:” Value of ZEMS-TKN-CHANGE-REASON Associated Text (DDL AS clause) ZTMX-VAL-CR-PROCESS-SIGILL "Instruction-failure" ZTMX-VAL-CR-PROCESS-SIGABRT "Process-aborted"...
Page 534: 102: Ztmx-Evt-Tmx-Started
Trap Multiplexer Subagent/Manager 102: ZTMX-EVT-TMX-STARTED Sample Message 96-07-26 11:43:07 \COMM.$ZTMX TANDEM.TRAPMUX.D31 000101 Object unavailable SNMP-Trap-Multiplexer - \COMM.$ZTMX, event number: Process-Terminated, cause: Process-stopped, previous state: started, current state: not-running, user content: undefined 102: ZTMX-EVT-TMX-STARTED The Trap Multiplexer process has started. Unconditional Tokens Value ZTMX-TKN-SUBJ-TMX <1>...
Page 535: 103: Ztmx-Evt-Tmx-Io-Err
Trap Multiplexer Subagent/Manager 103: ZTMX-EVT-TMX-IO-ERR ZTMX-VAL-TMX-STARTED is the current state. The DDL AS clause of this value (“started”) appears in the message text following “current state:” ZEMS-TKN-CONTENT-USER is assigned the value “undefined” in the message text following “user content:” Cause. The Trap Multiplexer process has started. Effect.
Page 536 Trap Multiplexer Subagent/Manager 103: ZTMX-EVT-TMX-IO-ERR ZTMX-EVT-TMX-IO-ERR is the event number (103). The DDL AS clause of this value (“Process-I/O-error”) is inserted in the message text following “event number:” ZTMX-VAL-TF-IO identifies the type of transient fault that occurred. For this event, the DDL heading of the value (“IO-error”) is inserted in the message text following “fault type:”...
Page 537: 104: Ztmx-Evt-Tmx-No-Mem-Space
Trap Multiplexer Subagent/Manager 104: ZTMX-EVT-TMX-NO-MEM-SPACE Sample Message 96-07-26 11:48:59 \COMM.$ZTMX TANDEM.TRAPMUX.D31 000103 Transient Fault - SNMP-Trap-Multiplexer \COMM.$ZTMX, event number: Process-I/O-error, fault type: IO-error, FS error: 4013 -- subcode: 0, File Name: $ZTC0, Additional Info: Cannot bind to port 104: ZTMX-EVT-TMX-NO-MEM-SPACE The Trap Multiplexer process ran out of memory.
Page 538: 105: Ztmx-Evt-Tmx--Prog-Err
Trap Multiplexer Subagent/Manager 105: ZTMX-EVT-TMX--PROG-ERR Recovery. Try using another disk as a swap device. If the problem persists, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management Service (EMS) logs If your local operating procedures require contacting the GCSC, supply your system number and the numbers and versions of all related products as well.
Page 539: Related Operating System Event Messages
Trap Multiplexer Subagent/Manager Related Operating System Event Messages ZTMX-TKN-ERR-TEXT contains text describing the error. This token is of type ZSPI-TYP-STRING. Cause. The Trap Multiplexer process experienced an internal or logic error. Effect. The process might or might not be able to recover from the error. If the primary process cannot recover, its backup process should take over.
Page 540: Converting Events To Traps
Trap Multiplexer Subagent/Manager Converting Events to Traps Process Activated Event A “Process Activated” event is reported for a process whenever the process is activated. Converting Events to Traps Any process that generates events, including the Trap Multiplexer, can have its events translated into traps by the EMS Trap Subagent.
Page 541: Preparing The Application
Trap Multiplexer Subagent/Manager Preparing the Application Example 12-1. Sample Application Filter Source Code filter tmxf; begin ==[#set ztmx^val^ssid [zspi^val^tandem]. [zspi^ssn^ztmx]. [ztmx^val^version] ] [#set ztmx^val^ssid TANDEM.185.D20 ] if zspi^tkn^ssid = ssid(ztmx^val^ssid) then pass else fail; end; Preparing the Application Before you can run the application, the C source code and the EMS filter source code need to be compiled and the Trap Multiplexer needs to be sending trap events to an EMS collector process.
Page 542: Running The Application
Trap Multiplexer Subagent/Manager Running the Application Running the Application You can optionally specify one or two startup parameters when you run the application: RUN application-name [-c collector-name] [-f filter-name] application-name is the name of the executable program. collector-name is the name of the EMS collector process to which the Trap Multiplexer is sending trap events.
Page 543: Application Control Flow
Trap Multiplexer Subagent/Manager Application Control Flow Example 12-2. Sample Application Output Waiting for the next Event..VersionNumber Community : public Enterprise : 1.3.6.1.4.1.169.3 Network Address : 130.252.12.3 Generic trap No Specific Trap No : 5 Timeticks : 54321 Varbind Count Varbind #1 : 1.2.3 Type...
Page 544: Application Source Code
Trap Multiplexer Subagent/Manager Application Source Code The getevent_loop() function retrieves trap events and then extracts and displays their token values, calling insert_null() or print_octetstring() functions to format strings and OCTET STRING values for display. Figure 12-4. Sample Application Control Flow main() Identify EMS collector and filter names Convert names to EMS format...
Page 545 Trap Multiplexer Subagent/Manager Application Source Code 5. The function named send_spi_cmd() sends SPI commands built by other functions to the distributor and processes the response. 6. The function named spi_cmd_set_source() builds SPI commands to identify the EMS collector from which events are to be retrieved and then calls send_spi_cmd().
Page 546 Trap Multiplexer Subagent/Manager Application Source Code 12. A buffer named event_buf is allocated for holding a trap event. ZEMS_VAL_BUFLEN provides 4200 bytes for this purpose. 13. A SPI command is built to initialize a buffer named spi_buf. This buffer, declared in the main block, is large enough to hold the longest SPI response.
Page 547 Trap Multiplexer Subagent/Manager Application Source Code 33. The value of the varbind’s data type is used to determine which statements to execute in order to extract and display the varbind’s value. For example, if ZTMX- TKN-TRAP-VARBIND-DATATYPE has a value of ZTMX_TNM_SMI_INTEGER, the token named ZTMX_TKN_SMI_INTEGER is accessed.
Page 548: Example 12-3. Sample Application Source Code
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 1 of 14) /************************************************************************ TMUXAPPC : Trap Multiplexer Application Program : Starts an EMS consumer distributor using a collector and filter provided by the user on the command-line parameters "-c"...
Page 549 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 2 of 14) /* These defines are used for zems structs to shorten names #define SPIERRDEF zspi_ddl_error_def /* spi error */ short spi_err; /* declare the SSIDs using the type defs from the DDL output */ zems_val_ssid_def emsssid;...
Page 550 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 3 of 14) /************************************************************************/ #pragma PAGE "spi_cmd_set_source()" /* builds a spi command that directs the distributor to use a collector as a source of event messages Input : Spi buffer, Collector name, and Distributor file number Return : None void spi_cmd_set_source (char* spi_buf, char* coll_name, short distr)
Page 551 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 4 of 14) /* send the comand to the distributor */ send_spi_cmd (spi_buf, distr); } /* spi_cmd_load_filter */ /*************************************************************************/ #pragma PAGE "insert_null()" /* this routine inserts a NULL at the end of an array of characters so that printf can print it as a string and returns the pointer to the beginning of the printable string...
Page 552 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 5 of 14) Input : pointer to spi_buffer and distributor file number Return : None void getevent_loop(char* spi_buf, short distr) <-- 10 char* event_buf; /* pointer to event data short byteoffset, i;...
Page 553 /* token-value /* index if (spi_err != ZSPI_ERR_OK) DEBUG(); if (strcmp(tmpssid.u_z_filler.z_filler,ZSPI_VAL_TANDEM)) printf ("A non-HP event has been reported\n"); continue; if (tmpssid.z_number != ZSPI_SSN_ZTMX) printf ("A non-Trap-Multiplexer event has been reported\n"); continue; /* check whether the event obtained is a trap event...
Page 554 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 7 of 14) spi_err = EMSGETTKN ((short*)event_buf, <-- 20 ZTMX_TKN_TRAP_VERSION, (char*) &t_version, /* trap version */ /* index if (spi_err != ZSPI_ERR_OK) DEBUG(); printf ("VersionNumber : %d \n",t_version); spi_err = EMSGETTKN ((short*)event_buf, <-- 21 ZTMX_TKN_TRAP_COMMUNITY,...
Page 555 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 8 of 14) spi_err = EMSGETTKN ((short*)event_buf, <-- 25 ZTMX_TKN_TRAP_SPECIFIC, /* specific trap no */ (char*) &t_specific, /* index if (spi_err != ZSPI_ERR_OK) DEBUG(); printf ("Specific Trap No : %d \n",t_specific); spi_err = EMSGETTKN ((short*)event_buf, <-- 26 ZTMX_TKN_TRAP_TIMETICKS,...
Page 556 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 9 of 14) /* get the varbind OID spi_err = EMSGETTKN ((short*)event_buf, <-- 31 ZTMX_TKN_TRAP_VARBIND_OID, /* varbind OID */ (char*)&t_buffer, /* index if (spi_err != ZSPI_ERR_OK) DEBUG(); pt_buffer = insert_null (t_buffer, &len);...
Page 557 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 10 of 14) case ZTMX_TNM_SMI_OID : printf ("Type : OID \n"); spi_err = EMSGETTKN ((short*) event_buf, ZTMX_TKN_SMI_OID, (char*)&t_buffer, pt_buffer = insert_null (t_buffer,&len); printf ("Value : %s\n",pt_buffer); break; case ZTMX_TNM_SMI_IPADDR : printf ("Type : IPADDR \n");...
Page 558 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 11 of 14) default : printf ("Type : UNKNOWN \n"); break; /* end of case */ /* exit from the current list spi_err = EMSGETTKN ((short*)event_buf, ZSPI_TKN_ENDLIST); if (spi_err !=ZSPI_ERR_OK) DEBUG();...
Page 559 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 12 of 14) extract the command-line parameters while (( argc != 0 ) && ( **argv == '-' )) <-- 35 opt = *( *argv + 1 ); argv++, argc--;...
Page 560 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 13 of 14) if (error) printf ("FILENAME_RESOLVE_ returned %d\n", error); exit (1); /* this will convert an external filename into an internal filename for passing it to the EMS routines error = FILENAME_TO_OLDFILENAME_ (filt_name_Dxx, /* filename */ <-- 39...
Page 561 Trap Multiplexer Subagent/Manager Application Source Code Example 12-3. Sample Application Source Code (page 14 of 14) /* Open the new process to pass this startup message */ ccval = FILE_OPEN_(proc_name, /* file name <-- 43 proc_len, /* length &distr); /* file number if (ccval) printf ("FILE_OPEN_ returned %d\n", ccval);...
Page 562 Trap Multiplexer Subagent/Manager Application Source Code SNMP Configuration and Management Manual—424777-006 12-70...
Page 563: Ipx/Spx Subagent (G-Series)
(LAN) between NonStop Kernel systems and products using the protocols. The subagent supports one of the groups in Novell’s Management Information Base (MIB) as well as several groups defined by HP containing objects that help you manage IPXPROTO processes and the subagent process itself. Architectural Overview...
Page 564: Figure 13-1. Nonstop Ipx/Spx Interactions
IPX/SPX Subagent (G-Series) Architectural Overview Figure 13-1. NonStop IPX/SPX Interactions NonStop IPX/SPX IPXMG IPXPROT Processes TLAM SLSA (D-series) (G-series) Telnet Workstation VST141.vsd The IPXPROTO processes send IPX/SPX frames to and receive them from the LAN by means of the ServerNet LAN Systems Access (SLSA) subsystem. The IPXMGR process enables management of IPXPROTO processes using the Subsystem Control Facility (SCF).
Page 565: Figure 13-2. Ipx/Spx Subagent Interactions
IPX/SPX Subagent (G-Series) Architectural Overview Figure 13-2. IPX/SPX Subagent Interactions NonStop IPX/SPX Collector IPXMG IPXPROT IPX/SPX Subagent Processes TLAM (D-series) SNMP TCP/IP Agents SLSA (G-series) NonStop Manager Legend IPX and SCF Messages SNMP Messages Telnet Workstation Manager Station VST142.vsd Although not shown in Figure 13-2, the IPX/SPX Subagent can interact over Expand with IPXPROTO processes, SNMP agent processes, and an EMS process running on...
Page 566: The Ipx/Spx Subagent Mib
IPX packet-handling statistics for IPXPROTO processes. The subagent provides read-only access to all the objects in the ipxSystem group. The zipx group, defined by HP, gives read-only access to various IPXPROTO process characteristics. This group contains five groups, each of which consists of...
Page 567: Figure 13-3. Indexes Linking Mib Table Entries
IPX/SPX Subagent (G-Series) The IPX/SPX Subagent MIB The tdmNwSPX group contains the tdmNwSPXTable, whose entries provide statistical information about the SPX layer of IPXPROTO processes. The tdmNwNCP group contains the tdmNwNCPTable, whose entries provide statistical information about the NCP layer of IPXPROTO processes. The tdmNwServer group contains the tdmNwServerTable, whose entries describe paths to Novell servers.
Page 568: Refreshing Ipxproto Object Values
IPX/SPX Subagent (G-Series) Refreshing IPXPROTO Object Values IPX/SPX Subagent Process Objects The zisa group, along with the manager application, facilitates managing the subagent process. The zisa group is a MIB group that contains the following group and two tables: The tdmNwSaConfig group supports management of subagent process attributes, such as process priority and EMS collector process name.
Page 569: Connections Between Subagent And Other Processes
IPX/SPX Subagent (G-Series) Connections Between Subagent and Other Processes setting the value of tdmNwSaRefreshNow in the tdmNwSaConfig group to forceDynamicRefresh. The subagent obtains statistical values for zipx group objects from statistics maintained by IPXPROTO processes the subagent is configured to monitor. Two objects in tdmNwInfoTable entries provide information about these statistics: The value of tdmNwInfoResetTime indicates the time at which the statistics were last initialized (set to zero).
Page 570 IPX/SPX Subagent (G-Series) Connections Between Subagent and Other Processes The -a startup parameter identifies SNMP agent processes that the subagent should accept requests from. After startup, you use tdmNwSaAgentNamesTable objects to control SNMP agent process connections. The -c startup parameter identifies the EMS collector process that the subagent should send events to.
Page 571: Resource Utilization
IPX/SPX Subagent (G-Series) Resource Utilization The subagent successfully connected to a previously subagentkeepalive connected process that failed. The rate at which the subagent attempts reconnections, called the keep-alive interval, is controlled by the -k startup parameter. By default, the subagent attempts to reconnect every 60 minutes.
Page 572: Subagent Backup Process
Novell MIB Objects on page 13-18. All other definitions in the IPX/SPX Subagent’s MIB are defined by HP and fully comply with RFC 1155, RFC 1212, and RFC 1213. Installation This subsection describes how to install the IPX/SPX Subagent.
Page 573: Dependencies
IPXMIBA contains the same definitions as IPXMIB, with several exceptions. DESCRIPTION clauses have been modified to provide information specific to HP systems. In addition, ipxBasicSysExistState is a read-only object, not a read-write object, and ipxBasicSysName has a syntax of DisplayString, not OCTET STRING.
Page 574: Configuration
IPX/SPX Subagent (G-Series) Configuration The subagent can communicate with multiple SNMP agent processes and multiple IPXPROTO processes running on the same or remote nodes. The subagent can send event messages to an EMS collector process on the same or a remote node. More information about subagent configuration appears in the following subsection.
Page 575: Starting And Stopping The Subagent
TACL RUN command options. Refer to the TACL Reference Manual for more information about these options. HP recommends using at least the following options: the NOWAIT option so that you can resume TACL operations once the...
Page 576 IPX/SPX Subagent (G-Series) Starting and Stopping the Subagent agent-process identifies a local or remote SNMP agent process from which you want the subagent to receive manager requests. You can specify from one through five alphanumeric characters, but the first character must be alphabetic. If you omit the -a startup parameter, $ZSNMP on the subagent’s node is assumed.
Page 577 IPX/SPX Subagent (G-Series) Starting and Stopping the Subagent After startup, you can use two MIB objects to control the EMS collector process. To change the EMS collector process, set the value of tdmNwSaEmsCollectorName to identify the EMS collector process. To activate or deactivate event collection, set the value of tdmNwSaEmsCollectorState to connected or disconnected, respectively.
Page 578: Troubleshooting The Subagent
IPX/SPX Subagent (G-Series) Troubleshooting the Subagent timer runs down when the refresh interval, specified in minutes, has elapsed since the previous table access. Valid values range from 0 through 32000. A value of zero or less causes the subagent to update values every time it receives a request. If you omit the -r startup parameter, the six refresh timers are set to 10 minutes.
Page 579: Timeouts
IPX/SPX Subagent (G-Series) Timeouts parameter-number identifies which startup parameter in the RUN command is incorrect. parameter-value identifies the incorrect information detected. parameter-description describes the information that would be valid for a particular startup parameter. For example, the parameter description for an invalid -r value would be: a refresh rate [0..32000].
Page 580: Novell Mib Objects
IPX/SPX Subagent (G-Series) Novell MIB Objects Manager Timeouts The greater the number of MIB values maintained, the longer it takes the subagent to refresh the values. You can minimize data refresh wait time by providing a long refresh interval in the -r startup parameter at startup, then forcing value updates when required after startup by setting the value of tdmNwSaRefreshNow to forceDyamicRefresh.
Page 581: Mib Objects
IPX/SPX Subagent (G-Series) MIB Objects ipxBasicSysOpenSocketFails (18) ipxCircuit (2) ipxForwarding (3) ipxServices (4) ipxTraps (5) MIB Objects Table 13-2 describes how the IPX/SPX Subagent supports objects in entries of the ipxBasicSysTable of the ipxSystem group. Table 13-2. ipxBasicSysEntry Objects Supported by the Subagent (page 1 of 3) Derivation of Object and Attributes Definition...
Page 582 IPX/SPX Subagent (G-Series) MIB Objects Table 13-2. ipxBasicSysEntry Objects Supported by the Subagent (page 2 of 3) Derivation of Object and Attributes Definition Value ipxBasicSysInHdrErrors The number of IPX packets Calculated by 1.3.6.1.4.1.23.2.5.1.1.1.7 discarded because of errors in IPXPROTO read-only their headers, including any IPX process Counter...
Page 583: Ipxbasicsystable Maintenance
IPX/SPX Subagent (G-Series) ipxBasicSysTable Maintenance Table 13-2. ipxBasicSysEntry Objects Supported by the Subagent (page 3 of 3) Derivation of Object and Attributes Definition Value ipxBasicSysOutPackets The total number of IPX packets Calculated by 1.3.6.1.4.1.23.2.5.1.1.1.16 transmitted. IPXPROTO read-only process Counter ipxBasicSysConfigSockets The configured maximum number Calculated by 1.3.6.1.4.1.23.2.5.1.1.1.17...
Page 584: Hp Mib Objects
13-2. ipxBasicSysOpenSocketFails Table 13-2. HP MIB Objects The IPX/SPX Subagent’s MIB contains two groups defined by HP that characterize IPX/SPX resources on NonStop Kernel systems: the zipx group and the zisa group: iso (1) org (3) dod (6) internet (1)
Page 585: Zipx Group
IPX/SPX Subagent (G-Series) zipx Group zipx Group The zipx group, which contains objects providing information about IPXPROTO processes, is named after the subsystem abbreviation for NonStop IPX/SPX (ZIPX). The zipx group objects are organized into five tables: iso (1) org (3) dod (6) internet (1) private (4)
Page 586: Table 13-4. Tdmnwinfoentry Objects Supported By The Subagent
IPX/SPX Subagent (G-Series) zipx Group tdmNwInfoTable Entries Table 13-4 describes tdmNwInfoTable entries. This table contains an entry for each IPXPROTO process the subagent is configured to monitor: iso (1) org (3) dod (6) internet (1) private (4) enterprises (1) tandem (169) nonstopsystems (3) zipx (164) tdmNwInfo (1)
Page 587 IPX/SPX Subagent (G-Series) zipx Group Table 13-4. tdmNwInfoEntry Objects Supported by the Subagent (page 2 of 3) Object and Attributes Definition Description of Value tdmNwInfoProgramFileName The name of the \system.$volume. 1.3.6.1.4.1.169.3.164.1.1.1.2 IPXPROTO process subvolume.file-name read-only program name. obtained using a DisplayString (SIZE (0..50)) mechanism equivalent to the SCF INFO PROCESS...
Page 588 IPX/SPX Subagent (G-Series) zipx Group Table 13-4. tdmNwInfoEntry Objects Supported by the Subagent (page 3 of 3) Object and Attributes Definition Description of Value tdmNwInfoQIOLimit The maximum Integer obtained using a 1.3.6.1.4.1.169.3.164.1.1.1.9 percentage of QIO mechanism equivalent to read-only memory to be used by the SCF INFO PROCESS INTEGER the IPXPROTO...
Page 589: Table 13-5. Tdmnwipxentry Objects Supported By The Subagent
IPX/SPX Subagent (G-Series) zipx Group tdmNwIPXTable Entries Table 13-5 describes tdmNwIPXTable entries. Each entry in the table contains objects that provide statistical information about the IPX layer of an IPXPROTO process the subagent is configured to monitor: iso (1) org (3) dod (6) internet (1) private (4)
Page 590 IPX/SPX Subagent (G-Series) zipx Group Table 13-5. tdmNwIPXEntry Objects Supported by the Subagent (page 2 of 2) Object and Attributes Definition Description of Value tdmNwIPXOutboundPacketCnt The total number of Integer value obtained using 1.3.6.1.4.1.169.3.164.2.1.1.3 outbound packets a mechanism equivalent to read-only sent from the IPX the SCF STATS PROCESS...
Page 591: Table 13-6. Tdmnwspxentry Objects Supported By The Subagent
IPX/SPX Subagent (G-Series) zipx Group tdmNwSPXTable Entries Table 13-6 describes tdmNwSPXTable entries. Each entry in the table contains objects that provide statistical information about the SPX layer of an IPXPROTO process the subagent is configured to monitor: iso (1) org (3) dod (6) internet (1) private (4)
Page 592 IPX/SPX Subagent (G-Series) zipx Group Table 13-6. tdmNwSPXEntry Objects Supported by the Subagent (page 2 of 3) Object and Attributes Definition Description of Value tdmNwSPXMaxBinds The maximum Integer value obtained 1.3.6.1.4.1.169.3.164.3.1.1.2 number of using a mechanism read-only concurrent explicit equivalent to the SCF INTEGER binds to the INFO PROCESS DETAIL...
Page 593 IPX/SPX Subagent (G-Series) zipx Group Table 13-6. tdmNwSPXEntry Objects Supported by the Subagent (page 3 of 3) Object and Attributes Definition Description of Value tdmNwSPXBadIncomingPacketCnt The number of times Integer value obtained 1.3.6.1.4.1.169.3.164.3.1.1.10 SPX received a bad using a mechanism read-only packet.
Page 594: Table 13-7. Tdmnwncpentry Objects Supported By The Subagent
IPX/SPX Subagent (G-Series) zipx Group tdmNwNCPMessageCnt (7) tdmNwNCPTotalErrors (8) Table 13-7. tdmNwNCPEntry Objects Supported by the Subagent (page 1 of 2) Object and Attributes Definition Description of Value tdmNwNCPEntryInstanceId The unique identifier Assigned by subagent. 1.3.6.1.4.1.169.3.164.4.1.1.1 of the instance of an read-only IPXPROTO process.
Page 595 IPX/SPX Subagent (G-Series) zipx Group Table 13-7. tdmNwNCPEntry Objects Supported by the Subagent (page 2 of 2) Object and Attributes Definition Description of Value tdmNwNCPMessageCnt The number of times Integer value obtained 1.3.6.1.4.1.169.3.164.4.1.1.7 a user request was using a mechanism read-only received by the NCP equivalent to the SCF...
Page 596: Figure 13-4. Derivation Of Tdmnwservertable Index Values
IPX/SPX Subagent (G-Series) zipx Group Figure 13-4. Derivation of tdmNwServerTable Index Values tdmNwServerTable tdmNwServer- tdmNwServer- tdmNwServer- tdmNwServer- tdmNwServer- tdmNwServer- Name EntryInstanceId InstanceId Address Type Hops RAPTOR 0x0000cafe: 000000000001:0451 0x0000cafe: RAPTOR 000000000001:8060 0xdeadbeef: D_BEEF 000000000001:0451 IPXPROT tdmNwSaIPXPROTONamesTable Process ··· tdmNwSaIpxProtoBasicSysInstance Novell RAPTO D_BEEF Novell...
Page 597: Table 13-8. Tdmnwserverentry Objects Supported By The Subagent
IPX/SPX Subagent (G-Series) zipx Group tdmNwServerType (5) tdmNwServerHops (6) Table 13-8. tdmNwServerEntry Objects Supported by the Subagent (page 1 of 2) Object and Attributes Definition Description of Value tdmNwServerEntryInstanceId The unique identifier Assigned by subagent. 1.3.6.1.4.1.169.3.164.5.1.1.1 of the instance of an read-only IPXPROTO process.
Page 598 (7), Archive Queue (8), Archive Server (9), Job Queue (10), Administration (11), Remote Bridge Server (36), Advertising Print Server (71), NetWare 386 (263), HP ODBC Server (1140), HP Telserv Server (1479), reserved by HP (1480..1488), reserved by each customer site (1489..1490). Value derived...
Page 599: Zisa Group
IPX/SPX Subagent (G-Series) zisa Group zisa Group The zisa group contains objects that describe IPX/SPX Subagent process attributes. This group consists of a subtree named tdmNwSubagent, which contains a group and two tables: iso (1) org (3) dod (6) internet (1) private (4) enterprises (1) tandem (169)
Page 600 IPX/SPX Subagent (G-Series) zisa Group tdmNwSaConfig Group Objects Table 13-9 describes tdmNwSaConfig group objects. This group contains a collection of scalar objects characterizing attributes of the subagent process: iso (1) org (3) dod (6) internet (1) private (4) enterprises (1) tandem (169) nonstopsystems (3) zisa (196)
Page 601: Table 13-9. Tdmnwsaconfig Objects Supported By The Subagent
IPX/SPX Subagent (G-Series) zisa Group Table 13-9. tdmNwSaConfig Objects Supported by the Subagent (page 1 of 3) Object and Attributes Definition Description of Value tdmNwSaProcessName The name of the \system.$process, 1.3.6.1.4.1.169.3.196.1.1.1 subagent process. where system and read-only process are 1 to 7 DisplayString (SIZE (0..20)) alphanumeric characters, starting with a letter.
Page 602 IPX/SPX Subagent (G-Series) zisa Group Table 13-9. tdmNwSaConfig Objects Supported by the Subagent (page 2 of 3) Object and Attributes Definition Description of Value tdmNwSaBackupStateReason The reason for the One of the values shown 1.3.6.1.4.1.169.3.196.1.1.9 value of tdmNwSa- in the first column. read-only BackupState.
Page 603 IPX/SPX Subagent (G-Series) zisa Group Table 13-9. tdmNwSaConfig Objects Supported by the Subagent (page 3 of 3) Object and Attributes Definition Description of Value tdmNwSaKeepAliveTimer The number of The value can be set at 1.3.6.1.4.1.169.3.196.1.1.14 minutes between startup by using the -k read-write subagent attempts startup parameter or from...
Page 604: Table 13-10. Tdmnwsaagentnamesentry Objects Supported By The Subagent
IPX/SPX Subagent (G-Series) zisa Group tdmNwSaAgentNamesTable Entries Table 13-10 describes the objects in each tdmNwSaAgentNamesTable entry. Each entry describes a SNMP agent with which the IPX/SPX Subagent is configured to communicate: iso (1) org (3) dod (6) internet (1) private (4) enterprises (1) tandem (169) nonstopsystems (3)
Page 605: Table 13-11. Tdmnwsaipxprotonamesentry Objects Supported By The Subagent
IPX/SPX Subagent (G-Series) zisa Group tdmNwSaIPXPROTONamesTable Entries Table 13-11 describes the objects in each tdmNwSaIPXPROTONamesTable entry. Each entry describes an IPXPROTO process the subagent is configured to monitor: iso (1) org (3) dod (6) internet (1) private (4) enterprises (1) tandem (169) nonstopsystems (3) zisa (196)
Page 606 IPX/SPX Subagent (G-Series) zisa Group Table 13-11. tdmNwSaIPXPROTONamesEntry Objects Supported by the Subagent (page 2 of 2) Description of Object and Attributes Definition Value tdmNwSaIpxProtoStateReason The reason for the One of the values in 1.3.6.1.4.1.169.3.196.1.3.1.4 value of tdmNwSaIpx- the first column. read-only ProtoState.
Page 607: Ems Support
IPX/SPX Subagent (G-Series) EMS Support EMS Support The events generated by the IPX/SPX Subagent are listed in Table 13-12. All the events are standard events, as the table indicates. Refer to the EMS Manual for a complete description of standard events. Table 13-12.
Page 608: Subsystem Id
IPX/SPX Subagent (G-Series) Subsystem ID SPI Programming Manual has information on the ZSPI data definitions and data definition files in general. The EMS Manual has information on ZEMS data definitions. Subsystem ID The subsystem ID that the subagent uses to identify itself as the source of event messages is: CONSTANT ZISA-VAL-VERSION VALUE VERSION "D30".
Page 609: Table 13-14. Zspi Tokens In Zisa Event Messages
IPX/SPX Subagent (G-Series) Tokens in ZISA Event Messages Table 13-13. ZISA Tokens in ZISA Event Messages (page 2 of 2) Token Contents ZISA-TKN-OBJ-STATE-REASON The state reason object, which can be one of the following: rowcreate operatorrequest subagentkeepalive invalidprocessname incorrectprocessname resourceproblem ZISA-TKN-REFRESH-RATE The refresh interval ZISA-TKN-KEEPALIVE-RATE...
Page 610 IPX/SPX Subagent (G-Series) Tokens in ZISA Event Messages Table 13-15. ZEMS Tokens in ZISA Event Messages (page 2 of 2) Token Contents ZEMS-TKN-GENTIME Event generation time ZEMS-TKN-LOGTIME Event log time ZEMS-TKN-NAME-MANAGER Manager process name ZEMS-TKN-NODENUM System number of event sender ZEMS-TKN-PIN PIN of event sender ZEMS-TKN-SUBJECT-MARK...
Page 611: Event Message Descriptions
IPX/SPX Subagent (G-Series) Event Message Descriptions Event Message Descriptions ZISA event messages are described in order by event number. Each description includes: A list of tokens that are included in the event message. Tokens listed as “unconditional” always appear in the message. Tokens listed as “conditional” are included only under described conditions.
Page 612: 1001: Zisa-Evt-Subagent-Available
IPX/SPX Subagent (G-Series) 1001: ZISA-EVT-SUBAGENT-AVAILABLE 1001: ZISA-EVT-SUBAGENT-AVAILABLE A subagent process has started successfully. Unconditional Tokens Value ZISA-TKN-SUBAGENT <1> IPX/SPX Subagent process ZEMS-TKN-EVENTNUMBER name ZEMS-TKN-CHANGE-REASON <2> ZISA-EVT-SUBAGENT-AVAILABLE ZEMS-TKN-STATE-PREVIOUS <3> ZISA-VAL-CHRSN-reason ZEMS-TKN-STATE-CURRENT <4> ZISA-VAL-STATE-DISCONNECTED ZEMS-TKN-CONTENT-USER <5> ZISA-VAL-STATE-CONNECTED ZISA-TKN-OBJ-STATE <6> undefined (null) ZISA-TKN-OBJ-STATE-REASON ZISA-VAL-CONNECTED ZISA-VAL-reason Conditional Tokens...
Page 613 IPX/SPX Subagent (G-Series) 1001: ZISA-EVT-SUBAGENT-AVAILABLE ZISA-VAL-STATE-CONNECTED is the current state. The DDL AS clause of this value (“connected”) appears in the message text following “current state:”. ZEMS-TKN-CONTENT-USER is assigned the value “undefined” in the message text following “user content:”. ZISA-VAL-CONNECTED is the value assigned to the ZISA-TKN-OBJ-STATE token.
Page 614: 1002: Zisa-Evt-Subagent-Unavailable
IPX/SPX Subagent (G-Series) 1002: ZISA-EVT-SUBAGENT-UNAVAILABLE 1002: ZISA-EVT-SUBAGENT-UNAVAILABLE A subagent process has stopped. Unconditional Tokens Value ZISA-TKN-SUBAGENT <1> IPX/SPX Subagent process ZEMS-TKN-EVENTNUMBER name ZEMS-TKN-CHANGE-REASON <2> ZISA-EVT-SUBAGENT- ZEMS-TKN-STATE-PREVIOUS UNAVAILABLE ZEMS-TKN-STATE-CURRENT <3> ZISA-VAL-CHRSN-OPERATOR-RQST ZEMS-TKN-CONTENT-USER <4> ZISA-VAL-STATE-CONNECTED ZISA-TKN-OBJ-STATE <5> ZISA-VAL-STATE-DISCONNECTED ZISA-TKN-OBJ-STATE-REASON <6> undefined (null) ZISA-VAL-DISCONNECTED ZISA-VAL-OPERATOR-REQUEST Conditional Tokens...
Page 615: 1003: Zisa-Evt-Agent-Available
IPX/SPX Subagent (G-Series) 1003: ZISA-EVT-AGENT-AVAILABLE ZEMS-TKN-CONTENT-USER is assigned the value “undefined” in the message text following “user content:”. ZISA-VAL-DISCONNECTED is the value assigned to the ZISA-TKN-OBJ-STATE token. ZISA-VAL-OPERATOR-REQUEST is the value assigned to the ZISA-TKN-OBJ-STATE-REASON token. Cause. A subagent primary process was intentionally stopped. Effect.
Page 616 IPX/SPX Subagent (G-Series) 1003: ZISA-EVT-AGENT-AVAILABLE ZISA-TKN-AGENT identifies the subject of the event, always a SNMP agent process. The DDL heading of this token (“agent-resource-object”) and the token’s value (the name of the SNMP agent process) are inserted in the message text. ZISA-EVT-AGENT-AVAILABLE is the event number (1003).
Page 617: 1004: Zisa-Evt-Agent-Unavailable
IPX/SPX Subagent (G-Series) 1004: ZISA-EVT-AGENT-UNAVAILABLE Sample Message 96-01-30 16:50:50 \COMM.$ZISA TANDEM.IPXSA.D30 001003 Object available agent-resource-object - $ZSNMP, event number: agent-available, reason: subagent-keepalive, previous state: disconnected, current state: connected, user content: undefined 1004: ZISA-EVT-AGENT-UNAVAILABLE The subagent cannot establish a connection with a SNMP agent process. Unconditional Tokens Value ZISA-TKN-AGENT...
Page 618 IPX/SPX Subagent (G-Series) 1004: ZISA-EVT-AGENT-UNAVAILABLE ZISA-VAL-CHRSN-reason is the change reason. One of the following DDL AS clauses is inserted in the message text following “cause:”: Token Value DDL AS Clause ZISA-VAL-CHRSN-OPERATOR-RQST “operatorrequest” ZISA-VAL-CHRSN-INVALID-PROC “invalid-processname” ZISA-VAL-CHRSN-INCORR-PROC “incorrect-processname” ZISA-VAL-CHRSN-RESOURCE-PROB “resource-problem” ZISA-VAL-STATE-CONNECTED is the previous state. The DDL AS clause of this value (“connected”) appears in the message text following “previous state:”.
Page 619 IPX/SPX Subagent (G-Series) 1004: ZISA-EVT-AGENT-UNAVAILABLE Change Reason Cause invalid-processname A Set operation on tdmNwSaAgentName specified a syntactically incorrect value. incorrect-processname A SNMP agent process was stopped, and a non-agent process by the same name was started. When the subagent attempted to reconnect with the stopped agent process, the name of the process running did not identify a SNMP agent process.
Page 620: 1005: Zisa-Evt-Backup-Available
IPX/SPX Subagent (G-Series) 1005: ZISA-EVT-BACKUP-AVAILABLE 1005: ZISA-EVT-BACKUP-AVAILABLE The subagent’s backup process started and the subagent checkpointed its state to the backup process. Unconditional Tokens Value ZISA-TKN-BACKUP <1> IPX/SPX subagent process ZEMS-TKN-EVENTNUMBER name ZEMS-TKN-CHANGE-REASON <2> ZISA-EVT-BACKUP-AVAILABLE ZEMS-TKN-STATE-PREVIOUS <3> ZISA-VAL-CHRSN-reason ZEMS-TKN-STATE-CURRENT <4> ZISA-VAL-STATE-DISCONNECTED ZEMS-TKN-CONTENT-USER <5>...
Page 621 IPX/SPX Subagent (G-Series) 1005: ZISA-EVT-BACKUP-AVAILABLE ZISA-VAL-STATE-CONNECTED is the current state. The DDL AS clause of this value (“connected”) appears in the message text following “current state:”. ZEMS-TKN-CONTENT-USER is assigned the value “undefined” in the message text following “user content:”. ZISA-VAL-CONNECTED is the value assigned to the ZISA-TKN-OBJ-STATE token.
Page 622: 1006: Zisa-Evt-Backup-Unavailable
IPX/SPX Subagent (G-Series) 1006: ZISA-EVT-BACKUP-UNAVAILABLE 1006: ZISA-EVT-BACKUP-UNAVAILABLE The subagent’s backup process stopped. Unconditional Tokens Value ZISA-TKN-BACKUP <1> IPX/SPX subagent process ZEMS-TKN-EVENTNUMBER name ZEMS-TKN-CHANGE-REASON <2> ZISA-EVT-BACKUP-AVAILABLE ZEMS-TKN-STATE-PREVIOUS <3> ZISA-VAL-CHRSN-reason ZEMS-TKN-STATE-CURRENT <4> ZISA-VAL-STATE-CONNECTED ZEMS-TKN-CONTENT-USER <5> ZISA-VAL-STATE-DISCONNECTED ZISA-TKN-OBJ-STATE <6> undefined (null) ZISA-TKN-OBJ-STATE-REASON ZISA-VAL-DISCONNECTED ZISA-VAL-reason Conditional Tokens None...
Page 623 IPX/SPX Subagent (G-Series) 1006: ZISA-EVT-BACKUP-UNAVAILABLE ZISA-VAL-STATE-DISCONNECTED is the current state. The DDL AS clause of this value (“disconnected”) appears in the message text following “current state:”. ZEMS-TKN-CONTENT-USER is assigned the value “undefined” in the message text following “user content:”. ZISA-VAL-DISCONNECTED is the value assigned to the ZISA-TKN-OBJ-STATE token.
Page 624: 1007: Zisa-Evt-Emscoll-Available
IPX/SPX Subagent (G-Series) 1007: ZISA-EVT-EMSCOLL-AVAILABLE 1007: ZISA-EVT-EMSCOLL-AVAILABLE The subagent has successfully connected to an EMS collector process. Unconditional Tokens Value ZISA-TKN-EMSCOLLECTOR <1> EMS collector process name ZEMS-TKN-EVENTNUMBER <2> ZISA-EVT-EMSCOLL-AVAILABLE ZEMS-TKN-CHANGE-REASON <3> ZISA-VAL-CHRSN-reason ZEMS-TKN-STATE-PREVIOUS <4> ZISA-VAL-STATE-DISCONNECTED ZEMS-TKN-STATE-CURRENT <5> ZISA-VAL-STATE-CONNECTED ZEMS-TKN-CONTENT-USER <6> undefined (null) ZISA-TKN-OBJ-STATE ZISA-VAL-CONNECTED ZISA-TKN-OBJ-STATE-REASON...
Page 625 IPX/SPX Subagent (G-Series) 1007: ZISA-EVT-EMSCOLL-AVAILABLE ZISA-VAL-STATE-CONNECTED is the current state. The DDL AS clause of this value (“connected”) appears in the message text following “current state:”. ZEMS-TKN-CONTENT-USER is assigned the value “undefined” in the message text following “user content:”. ZISA-VAL-CONNECTED is the value assigned to the ZISA-TKN-OBJ-STATE token.
Page 626: 1008: Zisa-Evt-Emscoll-Unavailable
IPX/SPX Subagent (G-Series) 1008: ZISA-EVT-EMSCOLL-UNAVAILABLE 1008: ZISA-EVT-EMSCOLL-UNAVAILABLE The subagent cannot establish a connection with an EMS collector process. Unconditional Tokens Value ZISA-TKN-EMSCOLLECTOR <1> EMS collector process name ZEMS-TKN-EVENTNUMBER <2> ZISA-EVT-EMSCOLL-UNAVAILABLE ZEMS-TKN-CHANGE-REASON <3> ZISA-VAL-CHRSN-reason ZEMS-TKN-STATE-PREVIOUS <4> ZISA-VAL-STATE-CONNECTED ZEMS-TKN-STATE-CURRENT <5> ZISA-VAL-STATE-DISCONNECTED ZEMS-TKN-CONTENT-USER <6>...
Page 627 IPX/SPX Subagent (G-Series) 1008: ZISA-EVT-EMSCOLL-UNAVAILABLE ZISA-VAL-STATE-DISCONNECTED is the current state. The DDL AS clause of this value (“disconnected”) appears in the message text following “current state:”. ZEMS-TKN-CONTENT-USER is assigned the value “undefined” in the message text following “user content:”. ZISA-VAL-DISCONNECTED is the value assigned to the ZISA-TKN-OBJ-STATE token.
Page 628: 1009: Zisa-Evt-Ipxproto-Available
IPX/SPX Subagent (G-Series) 1009: ZISA-EVT-IPXPROTO-AVAILABLE Recovery. Correcting the situation depends on the reason for the disconnection: Change Reason Recovery operatorrequest No action is required because the stoppage was deliberate. invalid-processname Resubmit the Set request using the correct syntax for a NonStop Kernel process name.
Page 629 IPX/SPX Subagent (G-Series) 1009: ZISA-EVT-IPXPROTO-AVAILABLE ZISA-EVT-EMSCOLL-AVAILABLE is the event number (1009). The DDL AS clause of this value (“ipxproto-available”) appears in the message text following “event number:”. ZISA-VAL-CHRSN-reason is the change reason. One of the following DDL AS clauses is inserted in the message text following “reason:”: Token Value DDL AS Clause...
Page 630: 1010: Zisa-Evt-Ipxproto-Unavailable
IPX/SPX Subagent (G-Series) 1010: ZISA-EVT-IPXPROTO-UNAVAILABLE Sample Message 96-01-30 16:50:50 \COMM.$ZISA TANDEM.IPXSA.D30 001009 Object available ipxproto-resource-object - $ZNV0, event number: ipxproto-available, reason: subagent-keepalive, previous state: disconnected, current state: connected, user content: undefined 1010: ZISA-EVT-IPXPROTO-UNAVAILABLE The subagent cannot establish a connection with an IPXPROTO process. Unconditional Tokens Value ZISA-TKN-IPXPROTO...
Page 631 IPX/SPX Subagent (G-Series) 1010: ZISA-EVT-IPXPROTO-UNAVAILABLE ZISA-VAL-CHRSN-reason is the change reason. One of the following DDL AS clauses is inserted in the message text following “cause:”: Token Value DDL AS Clause ZISA-VAL-CHRSN-OPERATOR-RQST “operatorrequest” ZISA-VAL-CHRSN-INVALID-PROC “invalid-processname” ZISA-VAL-CHRSN-INCORR-PROC “incorrect-processname” ZISA-VAL-CHRSN-RESOURCE-PROB “resource-problem” ZISA-VAL-STATE-CONNECTED is the previous state. The DDL AS clause of this value (“connected”) appears in the message text following “previous state:”.
Page 632: 1011: Zisa-Evt-Memory-Alloc-Failure
IPX/SPX Subagent (G-Series) 1011: ZISA-EVT-MEMORY-ALLOC-FAILURE Effect. The subagent cannot retrieve information from the IPXPROTO process. Recovery. Correcting the situation depends on the reason for the disconnection: Change Reason Recovery operatorrequest No action is required because the stoppage was deliberate. invalid-processname Resubmit the Set request using the correct syntax for a NonStop Kernel process name.
Page 633 IPX/SPX Subagent (G-Series) 1011: ZISA-EVT-MEMORY-ALLOC-FAILURE ZISA-EVT-MEMORY-ALLOC-FAILURE is the event number (1011). The DDL AS clause of this value (“memory-allocation- failure”) appears in the message text following “event number:”. ZISA-VAL-TF-MEM characterizes the type of transient fault that occurred. The DDL AS clause of this value ( “Memory-allocation”) is inserted in the message text following “fault type:”.
Page 634: 1012: Zisa-Evt-Process-Trapped
IPX/SPX Subagent (G-Series) 1012: ZISA-EVT-PROCESS-TRAPPED 1012: ZISA-EVT-PROCESS-TRAPPED The subagent process trapped. Unconditional Tokens Value ZISA-TKN-SUBAGENT <1> IPX/SPX subagent process ZEMS-TKN-EVENTNUMBER name ZEMS-TKN-TXFAULT-TYPE <2> ZISA-EVT-PROCESS-TRAPPED ZEMS-TKN-CONTENT-USER <3> ZISA-VAL-TF-PROG ZEMS-TKN-CHANGE-REASON <4> undefined (null) ZISA-VAL-CR-reason Conditional Tokens None Message Text Transient Fault IPX/SPX-SNMP-subagent-process - <1>, event number: <2>, fault type: <3>, user content:...
Page 635 IPX/SPX Subagent (G-Series) 1012: ZISA-EVT-PROCESS-TRAPPED ZISA-VAL-CR-reason is the change reason, which is one of the following values: Token Value DDL AS Clause ZISA-VAL-CR-PROCESS-SIGILL “Instruction-failure” ZISA-VAL-CR-PROCESS-SIGABRT “Process-aborted” ZISA-VAL-CR-PROCESS-SIGFPE “Arithmetic-overflow” ZISA-VAL-CR-PROCESS-SIGSEGV “Illegal-address-reference” ZISA-VAL-CR-PROCESS-SIGSTK “Stack-overflow” ZISA-VAL-CR-PROCESS-SIGTIMEOUT “Loop-timer-timeout” ZISA-VAL-CR-PROCESS-SIGTERM “Termination-request” ZISA-VAL-CR-PROCESS-SIGNOMEM “Memory-space-exhausted” Cause. The subagent process trapped. Effect.
Page 636 IPX/SPX Subagent (G-Series) 1012: ZISA-EVT-PROCESS-TRAPPED SNMP Configuration and Management Manual—424777-006 13-74...
Page 637: Ethernet Subagent
GESA, and G4SA interfaces) with the ServerNet LAN System Access (SLSA) subsystem, which supports parallel LAN I/O in a G-series ServerNet-based system. The Ethernet Subagent also supports additional private MIB objects defined by HP that let you monitor and manage the subagent itself.
Page 638: Figure 14-1. Architectural Overview Of The Ethernet Subagent
Ethernet Subagent The Ethernet Subagent and the SNMP Agent Figure 14-1. Architectural Overview of the Ethernet Subagent SNMP Agent forwards authenticated requests to subagent. Ethernet/ SNMP Agent Token Ring Subagent Subagent returns responses and linkUp/linkDown Trap messages to SNMP Agent. Subagent retrieves information about the interfaces through SCP for...
Page 639: Dot3 Statistics Group Supported By The Ethernet Subagent
Ethernet Subagent dot3 Statistics Group Supported by the Ethernet Subagent dot3 Statistics Group Supported by the Ethernet Subagent The Ethernet Subagent supports the dot3 Statistics group for Ethernet-like Interface types, defined in RFC 1643, identified by a check mark in the following list: iso (1) identified-organization (3) dod (6)
Page 640 Ethernet Subagent The Ethernet Subagent MIB These private MIB objects are defined by HP and reside in the zesa subtree within the nonstopsystems subtree registered to HP: iso (1) org (3) dod (6) internet (1) private (4) enterprises (1) tandem (169)
Page 641: Installing The Ethernet Subagent
Statistics group MIB objects. The ZESAMIB file contains definitions for the private Ethernet Subagent MIB objects defined by HP. Compile the ZESAMIB file (and, if necessary, the RFC1643 file) as described in the documentation provided with your SNMP manager. Compiling the MIB makes it possible for the SNMP manager to display the names (rather than only numeric object identifiers) of MIB objects.
Page 642: Starting The Ethernet Subagent
TACL RUN command options. Refer to the TACL Reference Manual for more information about these options. HP recommends using at least the NOWAIT option so that you can resume TACL operations once the subagent is started.
Page 643 Ethernet Subagent Starting the Ethernet Subagent startup-parameter is one of the parameters listed next with which you can control attributes of the Ethernet Subagent process. Note. Each of the Ethernet Subagent startup parameters corresponds to one of its private (zesa) MIB objects, as indicated in the following syntax diagram and described in Configuring a Running Ethernet Subagent on page 14-9.
Page 644: Stopping The Ethernet Subagent
Ethernet Subagent Stopping the Ethernet Subagent The default value is 60. Note. This timer value does not apply to objects that are placed in the disabled state by an SNMP Set request. See State Object/Resource Object Pairs on page 14-16 for information on the possible states that can be set for processes used by the Ethernet Subagent.
Page 645: Configuring A Running Ethernet Subagent
Ethernet Subagent Configuring a Running Ethernet Subagent You can force the backup process to take over and a new backup process to be created by setting the value of the zesaSwitchToBackupNow object to 1 (forceBackupTakeover) from an SNMP manager. Configuring a Running Ethernet Subagent Once an Ethernet Subagent is running, you can issue SNMP Get and Set requests from an SNMP manager to query and control the subagent.
Page 646: Controlling A Running Ethernet Subagent
Ethernet Subagent Controlling a Running Ethernet Subagent These objects are described in detail in Table 14-3 on page 14-12. Controlling a Running Ethernet Subagent In addition to getting information about a running Ethernet Subagent, you can control certain aspects of its behavior by issuing SNMP Set requests from an SNMP manager, as described in Table 14-2 on page 14-10.
Page 647: Zesa Mib Objects
Ethernet Subagent ZESA MIB Objects Table 14-2. Controlling an Ethernet Subagent Through SNMP (page 2 of 2) Initially set with You can control this By issuing SNMP Set this startup attribute of an requests against this parameter.. Ethernet Subagent... object... With this default value...
Page 648: Table 14-3. Private (Zesa) Mib Objects Supported By The Ethernet Subagent
NonStop Kernel. zesaProcessVersion The version of the T0326Gnn_date -- 1.3.6.1.4.1.169.3.217.4 Ethernet Subagent HP SNMP Ethernet Subagent, where read-only process object file. Gnn is the product version of the DisplayString Ethernet Subagent, for example, (SIZE (0..32)) G06.
Page 649 Ethernet Subagent ZESA MIB Objects Table 14-3. Private (ZESA) MIB Objects Supported by the Ethernet Subagent (page 2 of 5) Object and Attributes Definition Format and Derivation of Value zesaProcessUserID The NonStop Kernel user-ID-number 1.3.6.1.4.1.169.3.217.8 process user ID part of read-only the process access ID INTEGER (0..255)
Page 650 Ethernet Subagent ZESA MIB Objects Table 14-3. Private (ZESA) MIB Objects Supported by the Ethernet Subagent (page 3 of 5) Object and Attributes Definition Format and Derivation of Value zesaSwitchToBackupNow Causes the Ethernet One of these values: Subagent backup autoProcessPairControl (0) 1.3.6.1.4.1.169.3.217.14 process to take over forceBackupTakeover (1)
Page 651 Ethernet Subagent ZESA MIB Objects Table 14-3. Private (ZESA) MIB Objects Supported by the Ethernet Subagent (page 4 of 5) Object and Attributes Definition Format and Derivation of Value zesaRefreshNow A means of forcing an One of these values: update of the MIB tables autoDynamicRefresh (0) 1.3.6.1.4.1.169.3.217.18 and generating traps (if...
Page 652: State Object/Resource Object Pairs
Ethernet Subagent State Object/Resource Object Pairs Table 14-3. Private (ZESA) MIB Objects Supported by the Ethernet Subagent (page 5 of 5) Object and Attributes Definition Format and Derivation of Value zesaTcpIpState The state of the The settable values for this object connection between the are: 1.3.6.1.4.1.169.3.217.21...
Page 653: Table 14-4. Ethernet Subagent State Object/Resource Object Pairs
Ethernet Subagent State Object/Resource Object Pairs Table 14-4 lists the resource objects and their associated state objects and state values. Table 14-4. Ethernet Subagent State Object/Resource Object Pairs The operational state of Is indicated or controlled Which may contain one of the this resource object...
Page 654: Figure 14-2. Ethernet Subagent Resource Object States
Ethernet Subagent State Object/Resource Object Pairs State Transitions for Resource Objects Figure 14-2 illustrates how resource objects move between states. Note that: Setting a “Connected” object to “Disabled” forces a transition through the “Disconnected” state. This permits the orderly shutdown of the resource and the generation of a state change event for the disconnected state.
Page 655: Ethernet-Like Statistics Dot3Group
Ethernet Subagent Ethernet-Like Statistics dot3Group 3. Set the value of the resource object’s associated state object to “Enabled.” When the state object has been placed in the “Enabled” state, the Ethernet Subagent attempts to connect to the underlying process. If the connection attempt is successful, the object enters the “Connected” state. If the connection attempt fails, the object enters the “Disconnected”...
Page 656: Mib Objects
Ethernet Subagent MIB Objects MIB Objects Table 14-5 describes how the Ethernet Subagent supports objects in the dot3StatsTable. Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 1 of 7) Format and Derivation of Object and Attributes Definition Value dot3StatsTable Objects: Entries describing the Refer to dot3StatsTable...
Page 657 Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 2 of 7) Format and Derivation of Object and Attributes Definition Value dot3StatsFCSErrors Number of frames This object is supported for 1.3.6.1.2.1.10.7.2.3 discarded because of E4SA, GESA and the G4SA. It read-only frame checksum is a value obtained from:...
Page 658 Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 3 of 7) Format and Derivation of Object and Attributes Definition Value dot3StatsMultipleCollision The number of This object is supported for Frames succesfully GESA and G4SA, but not for 1.3.6.1.2.1.10.7.2.5 transmitted frames on E4SA.
Page 659 Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 4 of 7) Format and Derivation of Object and Attributes Definition Value dot3StatsDeferredTransmissions Number of frames This object is supported for 1.3.6.1.2.1.10.7.2.7 that could not be E4SA, GESA, and G4SA. The read-only transmitted value is obtained from:...
Page 660 Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 5 of 7) Format and Derivation of Object and Attributes Definition Value dot3StatsExcessiveCollisions Number of frames This object is supported for the 1.3.6.1.2.1.10.7.2.9 that had their E4SA, GESA, and G4SA. The read-only transmission aborted value is obtained from:...
Page 661 Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 6 of 7) Format and Derivation of Object and Attributes Definition Value dot3StatsInternalMacTransmit Number of frames for This object is supported for Errors which transmission GESA and G4SA, but not for 1.3.6.1.2.1.10.7.2.10 on a particular E4SA.
Page 662 Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 7 of 7) Format and Derivation of Object and Attributes Definition Value dot3StatsFrameTooLong Number of frames This object is supported for 1.3.6.1.2.1.10.7.2.13 discarded because E4SA, GESA, and G4SA. The read-only the length of the value is obtained from...
Page 663: Table 14-6. Compliance With Dot3 Group Definitions In Rfc 1643
14-5. dot3StatsCarrierSenseErrors Table 14-5. dot3StatsFrameTooLongs Table 14-5. dot3StatsInternalMacReceiveErrors Partial No corresponding HP instrumentation exists; 0 is returned when the object is accessed. (dot3StatsInternalMacReceiveErrors is not supported for E4SA, GESA and G4SA interfaces.) dot3StatsEtherChipSet Partial No corresponding HP instrumentation exists; NULL is returned when the object is accessed.
Page 664: Dot3Statstable Maintenance
Ethernet Subagent dot3StatsTable Maintenance dot3StatsTable Maintenance For each subnet found in response to an INFO SPI command for the SUBNET * object of the TCP/IP process, the Ethernet Subagent extracts associated logical interface (LIF) names. Using this information, the Ethernet Subagent uses the Shared Resource Library (SRL) routine LM_Get_Attributes_() to get the corresponding physical interface (PIF) name and the LIF type.
Page 665: Traps Generated By The Ethernet Subagent
Ethernet Subagent Traps Generated by the Ethernet Subagent Traps Generated by the Ethernet Subagent The Ethernet Subagent generates traps to inform SNMP managers of the status of the Ethernet interfaces to the configured TCP/IP subsystem. The SNMP managers to which the Ethernet Subagent sends traps are identified by the set of trap destination definitions configured for the SNMP agent with which the Ethernet Subagent is communicating.
Page 666: Ems Support
Ethernet Subagent EMS Support EMS Support This subsection describes the Event Management Service (EMS) events, listed in Table 14-8, generated by the Ethernet Subagent (subsystem abbreviation ZESA). Table 14-8. Ethernet Subagent Event Messages (page 1 of 2) Number ZESA-EVT- Standard Event and Description 3001 SUBAGENT-AVAIL Object Available...
Page 667: Data Definitions
Ethernet Subagent Data Definitions Table 14-8. Ethernet Subagent Event Messages (page 2 of 2) Number ZESA-EVT- Standard Event and Description 3010 TCPIP-OBJ-UNAVAIL Object Unavailable The configured TCP/IP process interface has transitioned from a “connected” state into a “disconnected” or “disabled” state. 3011 SRL-CALL-FAILED Transient Fault...
Page 668: Subsystem Id
Ethernet Subagent Subsystem ID Subsystem ID The subsystem ID that the Ethernet Subagent uses to identify itself as the source of event messages is: CONSTANT ZESA-VAL-OWNER VALUE "TANDEM". CONSTANT ZESA-VAL-NUMBER VALUE 217. CONSTANT ZESA-VAL-VERSION VALUE VERSION "G06". CONSTANT ZESA-VAL-EXTERNAL-SSID VALUE "TANDEM.217.G06".
Page 669: Event Message Descriptions
Ethernet Subagent Event Message Descriptions Table 14-10. ZEMS Tokens in ZESA Event Messages Token Contents ZEMS-TKN-CONTENT-STANDARD Type of standard event. ZEMS-TKN-CONTENT-USER Type of user-defined event (for the Ethernet Subagent, the value is always ZEMS-VAL-NULL). ZEMS-TKN-EVENTNUMBER Event number. ZEMS-TKN-SUBJECT-MARK Event subject marker. ZEMS-TKN-SUPPRESS-DISPLAY Display/do not display event flag.
Page 670: 3001: Zesa-Evt-Subagent-Avail
Ethernet Subagent 3001: ZESA-EVT-SUBAGENT-AVAIL The cause of the event, the conditions that prompted the Ethernet Subagent to generate the event message. The effects associated with or resulting from the cause. Recovery procedures for solving the problem reported by the event message. An example of the formatted message.
Page 671 Ethernet Subagent 3001: ZESA-EVT-SUBAGENT-AVAIL ZEMS-VAL-reason indicates the reason the Ethernet Subagent process has become available. The DDL AS clause associated with this value is inserted in the message text following “reason.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-CHANGE-REASON Meaning ZEMS-VAL-UNDERLYING-UP “underlying-serv-up”...
Page 672: 3002: Zesa-Evt-Subagent-Unavail
Ethernet Subagent 3002: ZESA-EVT-SUBAGENT-UNAVAIL Sample Message 98-07-08 12:21:51 \NOVA.$ZESA TANDEM.ETHSA.G06 003001 Object available Ethernet-SNMP-subagent - \NOVA.$ZESA:384566222, event number: subagent-process-available, reason: underlying-serv-up, previous state: disconnected, current state: connected, user content: undefined 3002: ZESA-EVT-SUBAGENT-UNAVAIL The Ethernet Subagent process is terminating for reasons other than an internal fault or invalid startup configuration.
Page 673 Ethernet Subagent 3002: ZESA-EVT-SUBAGENT-UNAVAIL ZESA-EVT-SUBAGENT-OBJ-UNAVAIL is the event number (3002). The DDL AS clause of this value (“subagent-process- unavailable”) appears in the message text following “event number.” ZEMS-VAL-reason indicates the reason the Ethernet Subagent process has become unavailable. The DDL AS clause associated with this value is inserted in the message text following “cause.”...
Page 674 Ethernet Subagent 3002: ZESA-EVT-SUBAGENT-UNAVAIL code-location/internal-context-text indicates where in the subsystem or application code the fault occurred. ZEMS-VAL-NULL indicates the type of subsystem defined event. Because the Ethernet Subagent process has not defined this as a private event, the DDL AS clause “undefined” always appears in the message text following “user content.”...
Page 675: 3003: Zesa-Evt-Agent-Obj-Avail
Ethernet Subagent 3003: ZESA-EVT-AGENT-OBJ-AVAIL 3003: ZESA-EVT-AGENT-OBJ-AVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZESA-TKN-AGENT ZESA-TKN-AGENT <2> zesaAgentName ZEMS-TKN-EVENTNUMBER <3> ZESA-EVT-AGENT-OBJ-AVAIL ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-UNDERLYING-UP ZEMS-TKN-STATE-PREVIOUS <5> ZESA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZESA-VAL-STATE-CONNECTED ZEMS-TKN-USER-CONTENT <7> ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number: <3>, reason: <4>, previous state: <5>, current state <6>, user content: <7>...
Page 676 Ethernet Subagent 3003: ZESA-EVT-AGENT-OBJ-AVAIL ZESA-VAL-STATE-state indicates the previous state of the SNMP agent process. The DDL AS clause associated with this value is inserted in the message text following “previous state.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-STATE-PREVIOUS Meaning ZESA-VAL-STATE-CONNECTED “connected”...
Page 677: 3004: Zesa-Evt-Agent-Obj-Unavail
Ethernet Subagent 3004: ZESA-EVT-AGENT-OBJ-UNAVAIL 3004: ZESA-EVT-AGENT-OBJ-UNAVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZESA-TKN-AGENT ZESA-TKN-AGENT <2> zesaAgentName ZEMS-TKN-EVENTNUMBER <3> ZESA-EVT-AGENT-OBJ-UNAVAIL ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-UNDERLYING-FAILED ZEMS-TKN-STATE-PREVIOUS <5> ZESA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZESA-VAL-STATE-DISCONNECTED ZEMS-TKN-UNDERLYING-OBJ- <7> zesaAgentName NAME <8> code-location/ ZEMS-TKN-SYMPTOM-STRING internal-context-text <9> ZEMS-VAL-NUL ZEMS-TKN-USER-CONTENT Conditional Tokens None Message Text Object unavailable <1>-<2>, event number: <3>, cause: <4>,...
Page 678 Ethernet Subagent 3004: ZESA-EVT-AGENT-OBJ-UNAVAIL ZESA-VAL-STATE-state indicates the previous state of the SNMP agent process. The DDL AS clause associated with this value is inserted in the message text following “previous state.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-STATE-PREVIOUS Meaning ZESA-VAL-STATE-CONNECTED “connected”...
Page 679: 3005: Zesa-Evt-Backup-Obj-Avail
Ethernet Subagent 3005: ZESA-EVT-BACKUP-OBJ-AVAIL Sample Message 98-07-08 12:18:39 \NOVA.$ZESA TANDEM.ETHSA.G06 003004 Object unavailable agent-interface - \NOVA.$ZSNMP, event number: agent-interface-unavailable, cause: underlying-serv-failed, previous state: connected, current state: disconnected, underlying object: \NOVA.$ZSNMP, symptom string: T0326G06_25JUN98_ETHSA, updateAgent.2, agent interface error 201 on poll request, user content: undefined 3005: ZESA-EVT-BACKUP-OBJ-AVAIL Unconditional Tokens...
Page 680 Ethernet Subagent 3005: ZESA-EVT-BACKUP-OBJ-AVAIL ZEMS-VAL-reason indicates the reason the backup Ethernet Subagent process has become available. The DDL AS clause associated with this value is inserted in the message text following “reason.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-CHANGE-REASON Meaning ZEMS-VAL-UNDERLYING-UP...
Page 681 Ethernet Subagent 3005: ZESA-EVT-BACKUP-OBJ-AVAIL Cause. The Ethernet Subagent successfully started a backup process identified by zesaBackupCPU:zesaBackupPIN. Effect. Ethernet Subagent configuration changes are now saved to the backup. In case of a primary failure, the backup will resume subagent processing using the last successfully checkpointed configuration.
Page 682: 3006: Zesa-Evt-Backup-Obj-Unavail
Ethernet Subagent 3006: ZESA-EVT-BACKUP-OBJ-UNAVAIL 3006: ZESA-EVT-BACKUP-OBJ-UNAVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZESA-TKN-BACKUP ZESA-TKN-BACKUP <2> zesaProcessName ZEMS-TKN-EVENTNUMBER <3> ZESA-EVT-BACKUP-OBJ-UNAVAIL ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-reason ZEMS-TKN-STATE-PREVIOUS <5> ZESA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZESA-VAL-STATE-state ZEMS-TKN-SYMPTOM-STRING <7> code-location/ internal-context-text ZEMS-TKN-USER-CONTENT <8> ZEMS-VAL-NULL Conditional Tokens ZEMS-TKN-UNDERLYING-OBJ- <9> zesaProcessName NAME Message Text Object unavailable <1>-<2>, event number: <3>, cause: <4>, previous state: <5>, current state <6>,...
Page 683 Ethernet Subagent 3006: ZESA-EVT-BACKUP-OBJ-UNAVAIL ZEMS-VAL-reason indicates the reason the backup Ethernet Subagent process has become unavailable. The DDL AS clause associated with this value is inserted in the message text following “cause.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-CHANGE-REASON Meaning ZEMS-VAL-UNDERLYING-FAILED...
Page 684 Ethernet Subagent 3006: ZESA-EVT-BACKUP-OBJ-UNAVAIL ZEMS-VAL-NULL indicates the type of subsystem defined event. Because the Ethernet Subagent process has not defined this as a private event, the DDL AS clause “undefined” always appears in the message text following “user content.” Cause. The backup Ethernet Subagent process stopped or failed to start. Effect.
Page 685: 3007: Zesa-Evt-Emscoll-Avail
Ethernet Subagent 3007: ZESA-EVT-EMSCOLL-AVAIL 3007: ZESA-EVT-EMSCOLL-AVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZESA-TKN-EMSCOLLECTOR ZESA-TKN-EMSCOLLECTOR <2> zesaEmsCollectorName ZEMS-TKN-EVENTNUMBER <3> ZESA-EVT-EMSCOLL-AVAIL ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-reason ZEMS-TKN-STATE-PREVIOUS <5> ZESA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZESA-VAL-STATE-CONNECTED ZEMS-TKN-USER-CONTENT <7> ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number: <3>, reason: <4>, previous state: <5>, current state <6>, user content: <7>...
Page 686 Ethernet Subagent 3007: ZESA-EVT-EMSCOLL-AVAIL ZESA-VAL-STATE-state indicates the previous state of the interface to the EMS collector process. The DDL AS clause associated with this value is inserted in the message text following “previous state.” Value of ZEMS-TKN-STATE-PREVIOUS Associated Text (DDL AS Clause) ZESA-VAL-STATE-CONNECTED “connected”...
Page 687: 3008: Zesa-Evt-Emscoll-Unavail
Ethernet Subagent 3008: ZESA-EVT-EMSCOLL-UNAVAIL Sample Message 98-07-08 12:21:51 \NOVA.$ZESA TANDEM.ETHSA.G06 003007 Object available emscollector-interface - \NOVA.$p0, event number: emscollector-interface- available, reason: operator-initiated, previous state: enabled, current state: connected, user content: undefined 3008: ZESA-EVT-EMSCOLL-UNAVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZESA-TKN-EMSCOLLECTOR ZESA-TKN-EMSCOLLECTOR <2>...
Page 688 Ethernet Subagent 3008: ZESA-EVT-EMSCOLL-UNAVAIL ZEMS-VAL-reason indicates the reason the interface with the EMS collector process has become unavailable. The DDL AS clause associated with this value is inserted in the message text following “cause.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-CHANGE-REASON Meaning ZEMS-VAL-UNDERLYING-FAILED...
Page 689 Ethernet Subagent 3008: ZESA-EVT-EMSCOLL-UNAVAIL This information is displayed only if the value of the ZEMS-TKN-CHANGE- REASON is ZEMS-VAL-UNDERLYING-FAILED. code-location/internal-context-text Indicates where in the subsystem or application code the fault occurred. ZEMS-VAL-NULL Indicates the type of subsystem defined event. Because the Ethernet Subagent process has not defined this as a private event, the DDL AS clause “undefined”...
Page 690: 3009: Zesa-Evt-Tcpip-Obj-Avail
Ethernet Subagent 3009: ZESA-EVT-TCPIP-OBJ-AVAIL 3009: ZESA-EVT-TCPIP-OBJ-AVAIL Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZESA-TKN-TCPIP ZESA-TKN-TCPIP <2> zesaTcpIpProcess ZEMS-TKN-EVENTNUMBER <3> ZESA-EVT-TCPIP-OBJ-AVAIL ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-reason ZEMS-TKN-STATE-PREVIOUS <5> ZESA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZESA-VAL-STATE-CONNECTED ZEMS-TKN-USER-CONTENT <7> ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number: <3>, reason: <4>, previous state: <5>, current state <6>, user content: <7>...
Page 691 Ethernet Subagent 3009: ZESA-EVT-TCPIP-OBJ-AVAIL ZESA-VAL-STATE-state indicates the previous state of the TCP/IP process. The DDL AS clause associated with this value is inserted in the message text following “previous state.” Value of ZEMS-TKN-STATE-PREVIOUS Associated Text (DDL AS Clause) ZESA-VAL-STATE-CONNECTED “connected” indicates a normal operational interface between the Ethernet Subagent and the TCP/IP process it is monitoring.
Page 692: 3010: Zesa-Evt-Tcpip-Obj-Unavail
Ethernet Subagent 3010: ZESA-EVT-TCPIP-OBJ-UNAVAIL Sample Messages 98-07-08 12:08:44 \NOVA.$ZESA TANDEM.ETHSA.G06 003009 Object available tcpip-resource - \NOVA.$ZTC0 event number: tcpip-resource-available, reason: underlying-serv-up, previous state: disconnected, current state: connected, user content: undefined 98-07-08 12:21:51 \NOVA.$ZESA TANDEM.ETHSA.G06 003009 Object available tcpip-resource - \NOVA.$ZTC1, event number: tcpip-resource-available, reason: operator-initiated, previous state: enabled,...
Page 693 Ethernet Subagent 3010: ZESA-EVT-TCPIP-OBJ-UNAVAIL zesaTcpIpProcess is the TCP/IP process name specified for the subagent’s private zesaTcpIpProcess MIB object. ZESA-EVT-TCPIP-OBJ-UNAVAIL is the event number (3010). The DDL AS clause of this value (“tcpip-resource- unavailable”) appears in the message text following “event number.” ZEMS-VAL-reason indicates the reason the TCP/IP process has become unavailable.
Page 694 Ethernet Subagent 3010: ZESA-EVT-TCPIP-OBJ-UNAVAIL The name of the TCP/IP process specified for the subagent’s private zesaTcpIpProcess MIB object The name of the SCP process specified for the subagent’s private zesaScpProcess MIB object The name of the SNMP agent process specified for the subagent’s private zesaAgentName MIB object This information is displayed only if the value of the ZEMS-TKN-CHANGE- REASON is ZEMS-VAL-UNDERLYING-FAILED.
Page 695: 3011: Zesa-Evt-Srl-Call-Failed
Ethernet Subagent 3011: ZESA-EVT-SRL-CALL-FAILED Sample Messages 98-07-08 12:21:51 \NOVA.$ZESA TANDEM.ETHSA.G06 003010 Object unavailable tcpip-resource - \NOVA.$ZTC1, event number: tcpip-resource-unavailable, cause: underlying-serv-failed, previous state: connected, current state: disconnected, underlying object: \NOVA.$zscp, symptom string: T0326G06_25JUN98_ETHSA:, updateSCP.6 retcode (-10), user content: undefined 98-07-08 12:18:39 \NOVA.$ZESA TANDEM.ETHSA.G06 003010 Object unavailable tcpip-resource -...
Page 696 Ethernet Subagent 3011: ZESA-EVT-SRL-CALL-FAILED zesaProcessName is the Ethernet Subagent process name specified for the subagent’s private zesaProcessName MIB object. ZESA-EVT-SRL-CALL-FAILED is the event number (3011). The DDL AS clause of this value (“srl-call-failed”) appears in the message text following “event number.” ZESA-VAL-TF-SRL identifies the type of transient fault that occurred.
Page 697: 3012: Zesa-Evt-Internal-Fault
Ethernet Subagent 3012: ZESA-EVT-INTERNAL-FAULT 3012: ZESA-EVT-INTERNAL-FAULT Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1> ZESA-TKN-SUBAGENT ZESA-TKN-SUBAGENT <2> zesaProcessName ZEMS-TKN-EVENTNUMBER <3> ZESA-EVT-INTERNAL-FAULT ZEMS-TKN-CHANGE-REASON <4> ZEMS-VAL-INTERNAL-FAILED ZEMS-TKN-STATE-PREVIOUS <5> ZESA-VAL-STATE-state ZEMS-TKN-STATE-CURRENT <6> ZESA-VAL-STATE-DISCONNECTED ZEMS-TKN-SYMPTOM-STRING <7> code-location/ ZEMS-TKN-USER-CONTENT internal-context-text <8> ZEMS-VAL-NULL Conditional Tokens None Message Text Object unavailable <1>-<2>, event number: <3>, cause: <4>, previous state: <5>, current state <6>, symptom string: <7>...
Page 698 Ethernet Subagent 3012: ZESA-EVT-INTERNAL-FAULT ZESA-VAL-STATE-state indicates the previous state of the Ethernet Subagent process. The DDL AS clause associated with this value is inserted in the message text following “previous state.” Value of Associated Text (DDL AS Clause) and ZEMS-TKN-STATE-PREVIOUS Meaning ZESA-VAL-STATE-CONNECTED “connected”...
Page 699: 3013: Zesa-Evt-Configuration-Invalid
Ethernet Subagent 3013: ZESA-EVT-CONFIGURATION-INVALID Sample Message 98-07-08 11:49:38 \NOVA.$ZESA TANDEM.ETHSA.G06 003012 Object unavailable Ethernet-SNMP- subagent - \NOVA.$ZESA:384566222, event number: internal-fault, cause: internal-failed, previous state: connected, current state: disconnected, symptom string:T0326G06_25JUN98_ETHSA:, AWAITIOX error -1, user content: undefined 3013: ZESA-EVT-CONFIGURATION-INVALID Unconditional Tokens Value ZEMS-TKN-SUBJECT-MARK <1>...
Page 700 Ethernet Subagent 3013: ZESA-EVT-CONFIGURATION-INVALID ZEMS-VAL-INTERNAL-FAILED indicates that an internal error was encountered. The DDL AS clause associated with this value (“internal-failed”) is inserted in the message text following “cause.” ZESA-VAL-STATE-ENABLED indicates the previous state of the Ethernet Subagent process. The DDL AS clause of this value (“enabled”) appears in the message text following “previous state.”...
Page 701: 3014: Zesa-Evt-Takeover-By-Backup
Ethernet Subagent 3014: ZESA-EVT-TAKEOVER-BY-BACKUP 3014: ZESA-EVT-TAKEOVER-BY-BACKUP Unconditional Tokens Value ZEMS-TKN-EVENTNUMBER <1> ZESA-EVT-TAKEOVER-BY-BACKUP ZEMS-TKN-TXFAULT-TYPE <2> ZESA-VAL-TF-TAKEOVER Conditional Tokens None Message Text <1>, <2> ZESA-EVT-TAKEOVER-BY-BACKUP is the event number (3014). The DDL AS clause of this value (“Takeover-by- backup”) appears in the message text. ZESA-VAL-TF-TAKEOVER identifies the type of transient fault that occurred.
Page 702: Converting Events To Traps
Ethernet Subagent Converting Events to Traps Converting Events to Traps Any process that generates events, including the Ethernet Subagent, can have its events translated into traps by the EMS Trap Subagent. The EMS Subagent uses an event filter known as a “routing distributor” to determine where to route trap messages. The filter contains a destination statement that identifies the SNMP agent as the routing destination.
Page 703: Part V. Appendices
Part V. Appendices Part V consists of the following appendices, which provide reference information: Appendix A SCF Command Syntax Summary for the NonStop Agent Appendix B SCF Error Messages for the NonStop Agent Appendix C Unsolicited SNMP Agent Messages SNMP Configuration and Management Manual—424777-006...
Page 704 Part V. Appendices SNMP Configuration and Management Manual—424777-006...
Page 705: Scf Command Syntax Summary For The Nonstop Agent
SCF Command Syntax Summary for the NonStop Agent This appendix lists, in alphabetical order, the syntax for the SCF commands supported by the NonStop agent. It is included as a quick reference for those already familiar with how the NonStop agent SCF commands function. In the following syntax diagrams, if you set a default PROCESS with the ASSUME PROCESS command, you can omit the NonStop agent process name and period, and just specify #object-name.
Page 706: Add Command
SCF Command Syntax Summary for the NonStop ADD Command Agent ADD Command The ADD command defines the configuration for an object. This is a sensitive command. ENDPOINT Object ADD ENDPOINT [$agent-process.]#endpoint-name [ , NETWORK [\node.]$tcpip-process ] [ , HOSTADDR "ip-address" ] PROFILE Object ADD PROFILE [$agent-process.]#profile-name [ , COMMUNITY "community-name"...
Page 707: Delete Command
SCF Command Syntax Summary for the NonStop DELETE Command Agent PROFILE Object ALTER PROFILE [$agent-process.]#profile-name [ , COMMUNITY "community-name" ] [ , HOSTADDR "ip-address"] [ , ACCESS { READONLY | READWRITE } ] TRAPDEST Object ALTER TRAPDEST [$agent-process.]#trapdest-name [ , COMMUNITY "community-name" ] [ , NETWORK [\node.]$tcpip-process ] [ , HOSTADDR "ip-address"] DELETE Command...
Page 708: Names Command
SCF Command Syntax Summary for the NonStop NAMES Command Agent PROCESS Object INFO PROCESS $agent-process [, SUB [ NONE | ALL | ONLY ] ] [, DETAIL ] PROFILE Object INFO PROFILE [$agent-process.]#profile-name [ , DETAIL ] TRAPDEST Object INFO TRAPDEST [$agent-process.]#trapdest-name [ , DETAIL ] NAMES Command The NAMES command lists the names of all objects defined for a NonStop agent...
Page 709: Status Command
SCF Command Syntax Summary for the NonStop STATUS Command Agent STATUS Command The STATUS command displays the operational states of objects in a NonStop agent configuration. This is a nonsensitive command. ENDPOINT Object STATUS ENDPOINT [$agent-process.]#endpoint-name PROCESS Object STATUS PROCESS $agent-process [ , SUB [ NONE | ALL | ONLY ] ] PROFILE Object STATUS PROFILE [$agent-process.]#profile-name TRAPDEST Object...
Page 710: Trace Command
SCF Command Syntax Summary for the NonStop TRACE Command Agent TRACE Command The TRACE command starts a trace operation on a NonStop agent process, alters trace parameters set by a previous TRACE PROCESS command, or stops a previously requested trace operation. This is a sensitive command. PROCESS Object TRACE PROCESS $agent-process { , STOP | { ,trace-option }...
Page 711: Scf Error Messages For The Nonstop Agent
SCF Error Messages for the NonStop Agent This appendix describes the types of error messages generated by SCF and provides cause, effect, and recovery information for the SCF error messages specific to the NonStop agent. Types of SCF Error Messages Command Parsing Error Messages Command parsing error messages are generated when a command is being broken down into its component parts.
Page 712: Common Versus Subsystem-Specific Errors
SCF Error Messages for the NonStop Agent Common Versus Subsystem-Specific Errors An example of a critical NonStop agent error message: SNMP E00009 Internet address invalid Noncritical messages are generally informational. Noncritical messages are preceded by the letter W. An example of a noncritical NonStop agent error message is: SNMP W00004 Duplicate TRAPDEST definition Common Versus Subsystem-Specific Errors When you receive an SCF error, check the subsystem identifier to see which...
Page 713: Scf Error Messages Help
-> HELP SNMP -15 -> HELP SCF 20211 If You Have to Call HP If the recovery for an error message indicates you should contact your service provider, be prepared to supply the following information. (If the error caused SCF to terminate, reenter SCF.)
Page 714: Nonstop Agent Error Messages
SCF Error Messages for the NonStop Agent NonStop Agent Error Messages NonStop Agent Error Messages The NonStop agent SCF error messages are listed in numeric order. SNMP Error 00001 SNMP E00001 Attribute conflict: HOSTADDR Cause. You tried to define an ENDPOINT object with a HOSTADDR address that is either: Identical to the HOSTADDR of an existing ENDPOINT object A member of a full wildcard address specification in an existing ENDPOINT object...
Page 715: Snmp Error 00005
SCF Error Messages for the NonStop Agent SNMP Error 00005 Effect. This is an informational message only. Configuring more than one TRAPDEST object that points to the same destination results in duplicate traps being sent to the same address. Recovery. No action is necessary. SNMP Error 00005 SNMP E00005 Invalid wildcard specification in HOSTADDR Cause.
Page 716: Snmp Error 00007
SCF Error Messages for the NonStop Agent SNMP Error 00007 SNMP Error 00007 SNMP W00007 Unable to update SNMPCTL file. Cause. The NonStop agent could not update the SNMPCTL file with the configuration change you submitted. Effect. The command is executed, but the SNMPCTL file no longer reflects the current environment.
Page 717: Unsolicited Snmp Agent Messages
Unsolicited SNMP Agent Messages The SNMP agent generates traps and EMS event messages when noteworthy conditions, such as a change in the state of an object, occur. This appendix describes these traps and events. Traps Table C-1 describes traps the SNMP agent generates. The traps are a subset of the standard SNMP traps prescribed in RFC 1157.
Page 718: Events
The SNMP agent process was unable to either decode an SNMP request or encode an SNMP response. SOCKET-ERROR An error occurred when the SNMP agent was communicating with HP TCP/IP software through the sockets library. EVT-CONFIG-ERROR The SNMP agent was started with an incorrect configuration parameter.
Page 719: 001: Zsmp-Evt-Invalid-Caid
Unsolicited SNMP Agent Messages 001: ZSMP-EVT-INVALID-CAID The SNMP agent can generate events with event numbers having a symbolic name with the prefix ZCMK. These events have negative numbers in the range -32600 to -32767 and are described in the Operator Messages Manua. 001: ZSMP-EVT-INVALID-CAID Process must run under a SUPER group creator accessor id Cause.
Page 720: 003: Zsmp-Evt-State-Change
Supporting documentation such as Event Management Service (EMS) logs and the Saveabend file of the affected process If your local operating procedures require contacting the HP Global Customer Center (GCSC), supply your system number and the numbers and versions of all related products as well.
Page 721: 004: Zsmp-Evt-Oss-Error
Unsolicited SNMP Agent Messages 004: ZSMP-EVT-OSS-ERROR Cause. A SNMP agent object changed state for one of the following reasons: A component of the SNMP agent’s configuration defined in the Object SNMP agent’s SNMPCTL file entered a different state. An SCF command or SNMP Set request was issued against a Operator component of the SNMP agent’s configuration, causing it to move to a different state.
Page 722: Table C-3. Encoding And Decoding Errors Returned By An Open Systems Solutions, Inc., Asn.1 Function
Unsolicited SNMP Agent Messages 004: ZSMP-EVT-OSS-ERROR Recovery. Contact your local Simple Network Management Protocol (SNMP) expert and provide all relevant information as follows: Descriptions of the problems and accompanying symptoms Details from the message or messages generated The OSS error number Supporting documentation such as Event Management Service (EMS) logs and the saveabend file of the affected process If your local operating procedures require contacting the GCSC, supply your system...
Page 723: 005: Zsmp-Evt-Socket-Error
Unsolicited SNMP Agent Messages 005: ZSMP-EVT-SOCKET-ERROR Table C-3. Encoding and Decoding Errors Returned by an Open Systems Solutions, Inc., ASN.1 Function (page 2 of 2) Fatal OSS-err-nu Error? Description A bad OBJECT IDENTIFIER was encountered. The first element must be 0 (ccit), 1 (iso), or 2 (joint-iso-ccit). The second element must be 0 (standard), 1 (registration authority), 2 (member body), or 3 (identified organization).
Page 724: 006: Zsmp-Evt-Config-Error
Cause. A socket library call returned an error when the SNMP agent was communicating with HP TCP/IP software. Effect. Depends on the error condition. Recovery. Network management personnel should consult the file $SYSTEM.SYSTEM.ERRNOH to translate the socket-err-num value to a socket...
Page 725: 009: Zsmp-Evt-Bad-Ipc-Pdu-Rcvd
Unsolicited SNMP Agent Messages 009: ZSMP-EVT-BAD-IPC-PDU-RCVD explanatory-text is information describing the problem. Cause. The SNMPCTL file specified at agent startup is already in use by another agent process. Effect. The agent does not start. Recovery. Network management personnel should perform one of these two recovery procedures: Stop the agent that already has the SNMPCTL file open and then restart the agent.
Page 726: 010: Zsmp-Evt-Bad-Nms-Pdu-Rcvd
Unsolicited SNMP Agent Messages 010: ZSMP-EVT-BAD-NMS-PDU-RCVD 010: ZSMP-EVT-BAD-NMS-PDU-RCVD Bad NMS PDU received from IP-address. Method function-name at location location-number. Detail: explanatory-text IP-address is the internet protocol (IP) address of the SNMP manager that sent the erroneous message. function-name is the name of a function used internally by the SNMP agent. location-number is a numeric identifier for a specific location within the function.
Page 727: 013: Zsmp-Evt-Invalid-Pdu-On-Svc-Pt
Unsolicited SNMP Agent Messages 013: ZSMP-EVT-INVALID-PDU-ON-SVC-PT 013: ZSMP-EVT-INVALID-PDU-ON-SVC-PT Invalid PDU, pdu-name, received on service point, protocol- name, from process-name pdu-name is the name of the protocol data unit (PDU). protocol-name is the name of the protocol. process-name is the name of the subagent process. Cause.
Page 728 Unsolicited SNMP Agent Messages 014: ZSMP-EVT-GUARDIAN-ERROR Recovery. Collect any relevant information, including the details from the error message. Refer to the Guardian Procedure Calls Reference Manual for information about the specific procedure and returned error number. If necessary, contact your service provider and provide all relevant information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated...
Page 729 Glossary Abstract Syntax Notation One. A formal language used to define PDUs and MIBs for SNMP. The language was developed and standardized by CCITT (International Consultative Committee on Telegraphy and Telephony) and ISO (International Organization for Standardization). access. The attribute of a MIB object that specifies how it can be accessed. Valid values are read-only, read-write, and non-accessible.
Page 730 Glossary Basic Encoding Rules Basic Encoding Rules. A language for describing transfer syntax. BER. See Basic Encoding Rules. broadcast trap destination. In a SNMP agent configuration, a trap destination to which the SNMP agent directs traps when not specifically told to send a directed trap by the subagent.
Page 731 (0x85.0x32.0x55.0x2b), and a combination of decimal (ASCII) and hexadecimal (133.0X32.85.0X2B). See also Internet address. empconfigure group. A collection of scalar objects in the ONS MIB that is used by HP problem management products. EMS. See Event Management Service.
Page 732 Glossary end-to-end services requests from SNMP manager stations) and NETWORK (the TCP/IP process that handles request/response messages). end-to-end services. Services that move octets from one system to another. entry. A row in a MIB table. event. A significant change in some condition in the system or network. Events can be operational errors, notifications of limits exceeded, requests for action needed, and so Event Management Service.
Page 733 3, 4, and 5 of an IOAM. Although the G4SA supersedes the Ethernet 4 ServerNet adapter (E4SA), Fast Ethernet ServerNet adapter (FESA), and the Gigabit Ethernet ServerNet adapter (GESA), it cannot be installed in an HP NonStop™ S-series enclosure. GENTRAP. A Network Control Language (NCL) procedure of the NonStop NET/MASTER Trap Subagent that assembles an SNMP trap from an EMS event and calls NMMTRAP to handle communications with the SNMP agent.
Page 734: Groups
Glossary hrSWRunPerf group hrSWRunPerf group. The optional MIB-II group in the Host Resources Subagent’s MIB that describes the resource consumption of the processes contained in the hrSWRun group. hrSystem group. The MIB-II group in the Host Resources Subagent’s MIB that describes general host characteristics, such as the number of current users.
Page 735 Glossary internet layer test whether a destination is reachable and responding. This protocol is used by the network layer to communicate the reachability of particular network nodes and routing control information. Strictly speaking, ICMP is part of the IP protocol because it shares the same Ethernet type field.
Page 736 Glossary managed node managed node. A network device containing an SNMP agent. managed objects. The resources supervised and controlled by SNMP managers. The agent stands between the managed resources and the SNMP manger. Managed resources are accessed via a virtual information store, the MIB. Management Information Base.
Page 737 Glossary network element network element. A resource that is monitored and controlled by network management applications. A network element consists of the managed entity (devices such as hosts, gateways, and terminal servers) and the managed entity’s agent. The managed entity’s agent is responsible for performing the network management functions requested by the network management stations.
Page 738 A collection of scalar objects in the ONS MIB that specifies the objects needed to invoke ONS (onsState) and to monitor ONS activity. onsconfirmTrap group. A table of objects in the ONS MIB used for HP problem- management products.
Page 739 Glossary port number port number. A means for identifying an application entity to a transport service in the Internet suite of protocols. On a NonStop host, each server has its own port number. port 161. An SNMP protocol entity receives request and response messages at UDP port 161 on the host with which it is associated.
Page 740 Glossary READWRITE READWRITE. An access mode that lets SNMP managers associated with a particular community both retrieve and modify the values of MIB objects. MIB objects that have read-write access can be modified. MIB objects that have read-only or read-write access can be read.
Page 741 Glossary Rule Management Services createAndGo Is supplied by an SNMP manager to create a new instance of a conceptual row and to have it available for use by the managed device. createAndWait Is supplied by an SNMP manager to create a new instance of a conceptual row but not to have it available for use by the managed device.
Page 742 SNMP agent. Examples of subagents offered on SNMP systems are the EMS Trap Subagent and the Host Resources Subagent. Subagent Toolkit. The product offered by HP that helps programmers generate subagents that make SNMP resources manageable by SNMP managers.
Page 743 IEEE 802.3 and Ethernet II standards. The pre-G-series HP TCP/IP communications product uses TLAM. HP TCP/IP. HP’s implementation of TCP/IP. HP TCP/IP provides TCP/IP connections for the NonStop system. HP TCP/IP connects the NonStop system to a variety of systems, including the Integrity S2 (HP’s fault-tolerant UNIX system) and systems manufactured...
Page 744 An SNMP message that contains a trap PDU. trap PDU. An SNMP PDU used to issue traps. The trap PDU contains these fields, with descriptions that are applicable to the SNMP agent and other HP SNMP products: enterprise The object identifier for the SNMP agent, indicating the origin of the trap: 1.3.6.1.4.1.169.3.155.1.
Page 745 X.25 provides a reliable stream transmission service that can support remote logon. X.25 Access Method. A HP product that implements, for wide area networks, the services of the network layer and layers below. X25AM. See X.25 Access Method.
Page 746 Glossary zhrmRefresh group zhrmRefresh group. A group defined by HP in the Host Resources Subagent’s MIB that provides information about the MIB value updates by the Host Resources Subagent and lets you request that the subagent refresh MIB values on demand.
Page 747 Index Numbers Attribute conflicts (continued) HOSTADDR (SCF error 00001) 5-2, 0, as Internet address wildcard 5-7, 5-9, 5-11 See also individual object entries SUBSYS (SCF error 00003) within a subsystem configuration ABORT command Attributes ENDPOINT object syntax ACCESS, PROFILE object objects for which supported COMMUNITY PROFILE object syntax...
Page 748 Index BREAK key 6-10 Configuration (continued) Broadcast trap destination 4-19, 5-12 configuring through SNMP 3-30 example of configuring multiple-host request/response connections 2-37 example of configuring multiple-host Cannot send trap C-10 trap connections 2-44 closeagent example of configuring single-host description 10-13 request/response connections 2-36 failures...
Page 749 Index Default object definitions (continued) EMS filters (continued) TRAPDEST object 4-18, 5-12 example of compilation Defense Advanced Research Projects example source code Agency Glossary-2 for troubleshooting DEFINED state ems group ENDPOINT object trapContentStandard 9-14, 10-16 PROFILE object 4-14, 5-30 trapCritical 9-16, 10-18 TRAPDEST object 4-17...
Page 750 Index Endpoint object (continued) error return-code from closeagent procedure 10-20 HOSTADDR attribute error return-code from openagent INFO command 5-21 call 10-18 invalid wildcard specification in error return-code from sendtrap HOSTADDR procedure 10-19 multiple-agent connections 2-35 Error-status naming conventions badValue NETWORK attribute genErr remote connections 2-37...
Page 751 Index Event messages destination HELP command 4-24, for troubleshooting Help facility generated by Host Resources SCF 4-24, 4-25 Subagent 11-104 SCF error message help generated by Trap Multiplexer 12-21 Heterogeneous Glossary-5 generic trap event message text 12-29, HMSAINI 11-15 13-50, 13-52, 13-53, 13-55, 13-58, Host Resources Subagent 13-60, 13-62, 13-64, 13-66, 13-68, 13-70,...
Page 752 Index Host Resources Subagent (continued) hrDevice group Spooler process specification 11-19 hrDeviceDescr 11-40 stable object refresh rate 11-19 hrDeviceErrors 11-41 standard MIB groups 11-1 hrDeviceID 11-40 starting 11-12 hrDeviceIndex 11-39 startup parameters 11-13 hrDeviceStatus 11-41 stopping 11-21 hrDeviceTable 11-39 tracing 11-21 hrDeviceType 11-39...
Page 753 Index hrDeviceErrors 11-41 hrStorage group (continued) hrDeviceID 11-40 hrStorageSize 11-32 hrDeviceIndex 11-39 hrStorageTable 11-30 hrDeviceStatus 11-41 hrStorageType 11-30 hrDeviceTable 11-39 hrStorageUsed 11-32 hrDeviceType 11-39 RFC compliance 11-34 hrDiskStorageAccess 11-43 value maintenance 11-34 hrDiskStorageCapacity 11-44 hrStorageAllocationFailures 11-32 hrDiskStorageMedia 11-44 hrStorageAllocationUnits 11-31 hrDiskStorageRemovable 11-44 hrStorageDescr...
Page 754 Index hrSWRunPerfTable 11-60 ICMP group (continued) hrSWRunStatus 11-57 icmpOutErrors 8-54 hrSWRunTable 11-54 icmpOutMsgs 8-53 hrSWRunType 11-56 icmpOutParmProbs 8-54 hrSystem group icmpOutRedirects 8-54 hrSystemDate 11-26 icmpOutSrcQuenchs 8-54 hrSystemInitialLoadDevice 11-26 icmpOutTimeExcds 8-54 hrSystemInitialLoadParameters 11-26 icmpOutTimestampReps 8-55 hrSystemMaxProcesses 11-27 icmpOutTimestamps 8-55 hrSystemNumUsers 11-27 RFC compliance 8-55 hrSystemProcesses...
Page 755 Index ifMtu 8-33 Installation (continued) ifNumber 8-31 dependencies 12-4 ifOperStatus 8-34 steps 12-4 ifOutDiscards 8-37 Instance Glossary-6 ifOutErrors 8-37 Interface layer Glossary-6 ifOutNUcastPkts 8-36 Interfaces group ifOutOctets 8-36 ifDescr 8-32 ifOutQLenProtos 8-37 ifIndex 8-31 ifOutUcastPkts 8-36 ifInDiscards 8-35 ifPhysAddress 8-34 ifInErrors 8-35 ifSpeed...
Page 756 Index Internet Protocol Glossary-7 IP group (continued) Internet suite of protocols Glossary-7 ipRouteMetric1..5 8-46 Interprocess communication ipRouteNextHop 8-46 See IPC transmission ipRouteproto 8-47 Invalid PDU C-11 ipRouteType 8-46 Invalid wildcard specification (SCF error RFC compliance 8-48 00005) ipAddrTable Invoking maintenance 8-50 the EMS Trap Subagent ipAdEntAddr...
Page 757 Index ipRouteNextHop 8-46 IPX/SPX Subagent (continued) ipRouteProto 8-47 startup parameters 13-12 ipRouteTable startup problems 13-16 maintenance 8-50 state reason object 13-8 ipRouteType 8-46 stopping 13-16 ipxBasicSys group subsystem ID 13-46 compliance with Novell 13-21 tdmNwInfo group 13-4 ipxBasicSysExistState 13-11 tdmNwIPX group 13-4 ipxBasicSysName 13-11...
Page 758: Events C
Index Management Information Base (continued) for NonStop NET/MASTER Trap NAME run option Subagent 10-14 for Host Resources Subagent 11-13 for proprietary groups of Host for NonStop agent Resources Subagent 11-3 for Trap Multiplexer 12-7 for standard groups of Host Resources Subagent 11-1 NAMES command...
Page 759 Index NonStop agent (continued) NonStop NET/MASTER Trap Subagent (continued) example of starting two NonStop agents RFC compliance 10-3 on same HP node 2-24 starting 10-13 installation stopping 10-13 internet address by which known TESTSEND 10-3 memory utilization 2-10 trap PDU...
Page 760 Index Object identifiers (continued) Object states (continued) for NonStop agent 1-12 PROFILE object 4-14, 5-30 for SNMP group TRAPDEST object 4-17, 5-31 for System group STARTING state for TCP group 8-56 ENDPOINT object 4-10, 5-26 for UDP group 8-61 PROCESS object for zagInEndpoint group 3-14 TRAPDEST object 4-17,...
Page 761 Index OUT command (SCF, general) 4-22 PROFILE object (continued) Output, SCF, directing to a file 4-24 INFO command 5-23 invalid wildcard specification in HOSTADDR naming conventions 4-12 Parallel Library TCP/IP 1-5, 2-11, 2-14, START command 5-26 2-20, 2-23, 2-24, 2-37, 8-1, 8-4, 8-15, 8-16 state transition illustration 4-15...
Page 762 Index Refreshing MIB values 11-5 RUN command Requests for Comments for starting Host Resources Subagent 11-13 See also RFC compliance for starting NonStop agent 2-14 compliance 1-17 for starting TCP/IP Subagent 8-12 how to obtain 1-18 for starting Trap Multiplexer 12-6 Resource Not Available ...
Page 763 Index SCF (continued) sendtrap continuing a command to next description 10-12 line 4-23 failures 10-19 for error messages 4-24 Sensitive SCF commands 4-23, introduction 4-21/4-24 Set operation errors multiple commands on a line 4-23 SetRequest PDU error messages 4-24, B-1/B-6 SNMP information protocol See also Error messages, SCF...
Page 764 Index SNMP group (continued) Socket Glossary-14 snmpOutTooBigs Socket error in method snmpOutTraps See Subsystem Programmatic Interface when counters are incremented START command SNMPAGT, program file name 4-26 ENDPOINT object syntax 5-26 SNMPCTL objects for which supported creation of PROFILE object syntax 5-26 startup parameter TRAPDEST object syntax...
Page 765 Index STOP command Subsystem, how SCF determines 4-22 ENDPOINT object syntax 5-33 Subtree on object tree 1-10 Swapping extended memory 2-11 objects for which supported sysContact PROFILE object syntax 5-33 sysDesc TRAPDEST object syntax 5-34 sysLocation STOPPED state sysName ENDPOINT object 4-9, 5-28 sysObjectID PROFILE object 4-14,...
Page 766 Index TCP group TCP/IP (continued) RFC compliance 8-60 trace facility tcpActiveOpens 8-57 trap connections 2-38 tcpConnLocalAddress 8-59 TCP/IP process default set with tcpConnLocalPort 8-59 TCPIP^PROCESS^NAME 5-6, 5-11 tcpConnRemAddress 8-60 through which NonStop agent can be tcpConnRemPort 8-60 reached tcpConnState 8-59 through which NonStop agent sends tcpCurrEstab 8-58...
Page 767 Index TCP/IP (continued) Template Glossary-15 TCPIPSA (program file) 8-13 TESTSEND 10-3 TLAM TCP/IP process to be queried by 8-15 See Tandem LAN Access Method unavailable resources TRACE command uninstrumented objects objects for which supported ZTSA subsystem ID 8-68 syntax 5-35 ztsa subtree Trace files ZTSAMIB file...
Page 768 Index Trap Multiplexer (continued) TRAPDEST object (continued) related operating system STOP command 5-34 events 11-115, 12-47 2-38 SPI data definition files 12-25 trapEventNumber 9-13, 10-15 starting 12-6 trapGenerationtime 9-15, 10-17 startup parameters 12-7 trapProcess 9-15, 10-17 stopping 12-9 Traps agent-address field TCP/IP process(s) for trap receipt 12-8 authenticationFailure...
Page 769 Index See User Datagram Protocol See wide area network UDP group Well-known port Glossary-17 RFC compliance 8-63 wide area network Glossary-17 Wildcard support udpInDatagrams 8-62 ENDPOINT object udpInErrors 8-62 HOSTADDR (“0”) udpLocalAddress 8-63 object name (*) udpLocalPort 8-63 PROCESS object name (*) udpOutDatagrams 8-62 PROFILE object...
Page 770 Index zagInEpRowStatus 3-14 zagInProfile group (continued) zagInEpState 3-15 zagInProfileEntry 3-16 zagInPfAccess 3-17 zagInProfileTable 3-16 zagInPfCommunity 3-17 zagInProfileEntry 3-16 zagInPfHostAddr 3-17 zagInProfileTable 3-16 zagInPfName 3-16 zagInTdCommunity 3-19 zagInPfRowStatus 3-16 zagInTdHostAddr 3-19 zagInPfState 3-17 zagInTdName 3-18 zagInProcBkupPID 3-13 zagInTdNetwork 3-19 zagInProcCpuTime 3-13 zagInTdRowStatus 3-18 zagInProcCreatTime...
Page 771 Index zhrmDevUnavail group (continued) zhrmInfCpuTable group zhrmDevUnDown 11-86 zhrmInfCpuEntries 11-67 zhrmDevUnErrors 11-89 zhrmInfCpuFirstIndex 11-67 zhrmDevUnID 11-89 zhrmInfCpuGetCounter 11-68 zhrmDevUnIndex 11-87 zhrmInfCpuGetNextCounter 11-68 zhrmDevUnOther 11-86 zhrmInfCpuLastDynamRefresh 11-67 zhrmDevUnStatus 11-89 zhrmInfCpuLastIndex 11-67 zhrmDevUnTable 11-86 zhrmInfCpuLastStableRefresh 11-67 zhrmDevUnTrapEnable 11-86 zhrmInfCpuSetCounter 11-68 zhrmDevUnType 11-87 zhrmInfDevEntries 11-65 zhrmInfDevFirstIndex...
Page 772 Index zhrmInfDiskTable group (continued) zhrmInfNetTable group (continued) zhrmInfDiskGetNextCounter 11-72 zhrmInfNetLastStableRefresh 11-69 zhrmInfDiskLastDynamRefresh 11-72 zhrmInfNetSetCounter 11-69 zhrmInfDiskLastIndex 11-71 zhrmInfParLastIndex 11-73 zhrmInfPartEntries 11-73 zhrmInfDiskLastStableRefresh 11-72 zhrmInfPartFirstIndex 11-73 zhrmInfDiskSetCounter 11-72 zhrmInfPartGetCounter 11-74 zhrmInfFSEntries 11-74 zhrmInfPartGetNextCounter 11-74 zhrmInfFSFirstIndex 11-74 zhrmInfPartLastDynamRefresh 11-73 zhrmInfFSGetCounter 11-75 zhrmInfPartLastStableRefresh 11-73 zhrmInfFSGetNextCounter 11-75...
Page 773 Index zhrmInfStorFirstIndex 11-64 zhrmSaHomeTerm 11-93 zhrmInfStorGetCounter 11-65 zhrmSaIniFile 11-93 zhrmInfStorGetNextCounter 11-65 zhrmSaPaid 11-92 zhrmInfStorLastDyamRefresh 11-64 zhrmSaPID 11-92 zhrmInfStorLastIndex 11-64 zhrmSaPri 11-92 zhrmInfStorLastStableRefresh 11-65 zhrmSaProcCurrTime 11-92 zhrmInfStorSetCounter 11-65 zhrmSaProcess group zhrmInfStorTable 11-64 value maintenance 11-95 zhrmInfStorTable group zhrmEnableSoftwareGroup 11-94 zhrmInfStorEntries 11-64 zhrmExamineGuardian 11-94 zhrmInfStorFirstIndex...
Page 774 Index zhrmTableInfo group (continued) zhrmThrRam group zhrmInfFSTable 11-74 zhrmThrRAMHighValue 11-79 zhrmInfNetTable 11-68 zhrmThrRAMLowValue 11-79 zhrmInfPartTable 11-73 zhrmThrRAMPercentUse 11-78 zhrmInfPrnTable 11-70 zhrmThrRAMTotal 11-78 zhrmInfStorTable 11-64 zhrmThrRAMTrapEnable 11-79 zhrmThrDisk 11-81 zhrmThrRAMUse 11-78 zhrmThrDisk group zhrmThrRAMAllocationFailures 11-81 zhrmThrDiskHighValue 11-82 zhrmThrRAMAllocationUnits 11-80 zhrmThrDiskLowValue 11-82 zhrmThrRAMDescr 11-80 zhrmThrRAMHighValue...
Page 775 Index ZHRM-EVT- zisa group (continued) HRM-SA-IO-ERR (003) 11-111 tdmNwSaProcessName 13-39 HRM-SA-NO-MEM-SPACE tdmNwSaProcessPAID 13-39 (004) 11-113 tdmNwSaProcessPriority 13-39 HRM-SA-PROG-ERR (005) 11-114 tdmNwSaProcessVersion 13-39 HRM-SA-STARTED (002) 11-109 tdmNwSaRefreshNow 13-41 HRM-SA-TERMINATED (001) 11-108 tdmNwSaRefreshTimer 13-41 zipx group 13-22 tdmNwSaSwitchToBackupNow 13-40 maintenance 13-36 ZISA-EVT tdmNwInfoBackupCPU 13-25 -AGENT-AVAILABLE (1003)
Page 776 Index ztmxInDecodeErrors 12-13 ztmxProcess group ztmxInEgpNeighborLossTraps 12-15 value maintenance 12-20 ztmxInEnterpriseSpecificTraps 12-15 ztmxProcAgent 12-17 ztmxInGetNextPdus 12-13 ztmxProcAgentSessionStatus 12-17 ztmxInGetPdus 12-13 ztmxProcBkupPID 12-17 ztmxInGetResponsePdus 12-13 ztmxProcCpuTime 12-17 ztmxInLinkDownTraps 12-15 ztmxProcCreatTime 12-17 ztmxInLinkUpTraps 12-15 ztmxProcCurrTime 12-17 ztmxInSetPdus 12-13 ztmxProcEmsCollector 12-17 ztmxInTrapPdus 12-13 ztmxProcEmsWriteErrors 12-20 ztmxInWarmStartTraps...
Page 777 Index Special Characters ztmxUdpStatsCurrTime 12-13 ztsaSubnetTable 8-26 ZTMX-EVT- ztsaSwitchToBackupNow 8-10, 8-18, 8-23 TMX-IO-ERR (103) 12-43 ztsaTcpIpName 8-17, 8-26 ztsaTcpIpProcess 8-17, 8-19 TMX-NO-MEM-SPACE (104) 12-45 ztsaTcpIpState 8-17, 8-19, 8-26 TMX-PROG-ERR (105) 12-46 ztsaTcpIpStatus 8-17, 8-26 TMX-STARTED (102) 12-42 ztsaTcpIpTable 8-26 TMX-TERMINATED (101) 12-40 ZTSA-EVT- TRAP-AUTH-FAIL (004)
Page 778 Index Special Characters SNMP Configuration and Management Manual—424777-006 Index -32...

This manual is also suitable for:

T9576h01

HP T9576G06 Management Manual

Part I. Installing and Configuring SNMP

The Nonstop SNMP Environment

Figures

Tables

1 The Nonstop SNMP Environment (Continued)

Installing and Configuring the SNMP Agent

2 Installing and Configuring the SNMP Agent (Continued)

Mibs Supported by the SNMP Agent

Tables (Continued)

4 Introduction to SCF for the SNMP Agent

Figures (Continued)

4 Introduction to SCF for the SNMP Agent (Continued)

SCF Commands for the SNMP Agent

5 SCF Commands for the SNMP Agent (Continued)

Part III. Troubleshooting

SNMP Agent Ptrace Facility

Troubleshooting the SNMP Agent

7 Troubleshooting the SNMP Agent (Continued)

Part IV. SNMP Subagents

TCP/IP Subagent

Quick Links

Troubleshooting

Related Manuals for HP T9576G06

Summary of Contents for HP T9576G06