SNMP Configuration and Management Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

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. The SNMP Agent and its

subagents comply with SNMP Requests for Comment (RFCs) so that SNMP-compliant

management applications, known as SNMP managers, can manage various resources

on an HP NonStop™ host.

Product Version

SNMP Agent (T9576G06), T9576H01)

Supported Release Version Updates (RVUs)

This manual supports the G06.24 RVU and all subsequent G-series RVUs and the

H06.03 RVU and all subsequent H-series RVUs until otherwise indicated by its

replacement publication.

Part Number Published

424777-006 July 2005

Summary of content (778 pages)

PAGE 1
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 2
Document History Part Number Product Version Published 424777-002 SNMP Agent (T9576G06) May 2002 424777-003 SNMP Agent (T9576G06) November 2002 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) EMS Trap S
PAGE 3
SNMP Configuration and Management Manual Glossary Index What’s New in This Manual xxiii Manual Information xxiii New and Changed Information Examples Figures xxiv About This Manual xxv Your Comments Invited xxv Audience xxv Purpose xxvi Organization xxvi Related Reading xxviii Notation Conventions xxviii Part I. Installing and Configuring SNMP 1.
PAGE 4
1. The NonStop SNMP Environment (continued) Contents 1. The NonStop SNMP Environment (continued) Traps 1-14 Architectural Overview of NonStop SNMP RFC Compliance 1-17 Related Documents 1-18 1-14 2.
PAGE 5
2. Installing and Configuring the SNMP Agent (continued) Contents 2.
PAGE 6
Contents 4. Introduction to SCF for the SNMP Agent Part II. SCF for the SNMP Agent 4.
PAGE 7
4. Introduction to SCF for the SNMP Agent (continued) Contents 4.
PAGE 8
5. SCF Commands for the SNMP Agent (continued) Contents 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 5-32 STOP ENDPOINT Command 5-33 STOP PROFILE Command 5-33 STOP TRAPDEST Command 5-34 TRACE Command 5-35 VERSION Command 5-37 Part III. Troubleshooting 6.
PAGE 9
7. Troubleshooting the SNMP Agent (continued) Contents 7. Troubleshooting the SNMP Agent (continued) Creating a Filter 7-3 Compiling the Filter 7-4 Displaying Filtered Event Messages Using Trace Records 7-4 TCP/IP 7-5 SNMP Agent 7-5 Diagnosing Request Errors 7-6 7-4 Part IV. SNMP Subagents 8.
PAGE 10
8. TCP/IP Subagent (continued) Contents 8.
PAGE 11
8. TCP/IP Subagent (continued) Contents 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.
PAGE 12
11. Host Resources Subagent Contents 11.
PAGE 13
11. Host Resources Subagent (continued) Contents 11.
PAGE 14
11. Host Resources Subagent (continued) Contents 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 12.
PAGE 15
12. Trap Multiplexer Subagent/Manager (continued) Contents 12.
PAGE 16
13. IPX/SPX Subagent (G-Series) (continued) Contents 13.
PAGE 17
14. Ethernet Subagent (continued) Contents 14.
PAGE 18
A. SCF Command Syntax Summary for the NonStop Agent (continued) Contents A. SCF Command Syntax Summary for the NonStop Agent (continued) STATUS Command A-5 STOP Command A-5 TRACE Command A-6 VERSION Command A-6 B.
PAGE 19
Glossary Contents Glossary Index Examples Example 9-1. Example 9-2. Example 9-3. Example 10-1. Example 10-2. Example 12-1. Example 12-2. Example 12-3. ASN.1 Source Code for EMS Trap MIB 9-5 Example Routing Distributor Filter 9-8 Example TACL Macro for Starting EMS Trap Subagent ASN.1 Source Code for EMS Trap MIB 10-6 Initial Contents of GENTRAP 10-10 Sample Application Filter Source Code 12-49 Sample Application Output 12-51 Sample Application Source Code 12-56 9-11 Figures Figure 1-1. Figure 1-2.
PAGE 20
Figures (continued) Contents Figures (continued) Figure 4-10. Figure 6-1. Figure 8-1. Figure 8-2. Figure 8-3. Figure 9-1. Figure 9-2. Figure 10-1. Figure 10-2. Figure 11-1. Figure 11-2. Figure 11-3. Figure 11-4. Figure 11-5. Figure 11-6. Figure 12-1. Figure 12-2. Figure 12-3. Figure 12-4. Figure 13-1. Figure 13-2. Figure 13-3. Figure 13-4. Figure 14-1. Figure 14-2.
PAGE 21
Tables (continued) Contents Tables (continued) Table 3-6. Table 3-7. Table 3-8. Table 3-9. Table 3-10. Table 3-11. Table 4-1. Table 4-2. Table 4-3. Table 4-4. Table 5-1. Table 6-1. Table 6-2. Table 7-1. Table 8-1. Table 8-2. Table 8-3. Table 8-4. Table 8-5. Table 8-6. Table 8-7. Table 8-8. Table 8-9. Table 8-10. Table 8-11. Table 8-12. Table 8-13. Table 8-14. Table 8-15. Table 8-16. Table 8-17. Table 8-18. Table 9-1. Table 10-1. Table 10-2. Table 10-3.
PAGE 22
Tables (continued) Contents Tables (continued) Table 10-4. Table 11-1. Table 11-2. Table 11-3. Table 11-4. Table 11-5. Table 11-6. Table 11-7. Table 11-8. Table 11-9. Table 11-10. Table 11-11. Table 11-12. Table 11-13. Table 11-14. Table 11-15. Table 11-16. Table 11-17. Table 11-18. Table 11-19. Table 11-20. Table 11-21. Table 11-22. Table 11-23. Table 12-1. Table 12-2. Table 12-3. Table 12-4.
PAGE 23
Tables (continued) Contents Tables (continued) Table 12-5. Table 12-6. Table 12-7. Table 12-8. Table 12-9. Table 13-1. Table 13-2. Table 13-3. Table 13-4. Table 13-5. Table 13-6. Table 13-7. Table 13-8. Table 13-9. Table 13-10. Table 13-11. Table 13-12. Table 13-13. Table 13-14. Table 13-15. Table 14-1. Table 14-2. Table 14-3. Table 14-4. Table 14-5. Table 14-6. Table 14-7. Table 14-8. Table 14-9. Table 14-10. Table C-1. Table C-2. Table C-3.
PAGE 24
Tables (continued) Contents SNMP Configuration and Management Manual—424777-006 xxii
PAGE 25
What’s New in This Manual Manual Information 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 This revision contains these changes and additions: Section Change Section 1, The NonStop SNMP Environmentt Notes concerning H-Series support have been included. Section 2, Installing and Configuring the SNMP Agent Notes concerning H-Series support have been included. Section 4, Introduction to SCF for the SNMP Agent H-series information has been added. Section 7, Troubleshooting the SNMP Agent H-series information has been added.
PAGE 27
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. Your Comments Invited After using this manual, please take a moment to send us your comments.
PAGE 28
Purpose About This Manual 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. For users of the SNMP manager, this manual describes the MIBs supported in the NonStop SNMP environment.
PAGE 29
Organization About This Manual 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 About This Manual Related Reading This manual has three companion manuals: • • • • 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
General Syntax Notation About This Manual 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. Italic computer type letters within text indicate C and Open System Services (OSS) variable items that you supply. Items not enclosed in brackets are required. For example: pathname [ ] Brackets.
PAGE 32
General Syntax Notation About This Manual 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. For example: "[" repetition-constant-list "]" Item Spacing.
PAGE 33
Notation for Messages About This Manual !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 ] ) ; !i !o:i Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text.
PAGE 34
Notation for Management Programming Interfaces About This Manual 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. } { Unknown. } | Vertical Line.
PAGE 35
Change Bar Notation About This Manual 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. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
PAGE 36
Change Bar Notation About This Manual SNMP Configuration and Management Manual—424777-006 xxxiv
PAGE 37
Part I.
PAGE 38
Part I.
PAGE 39
1 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. Because of its relative simplicity, SNMP has gained widespread acceptance as a protocol for managing devices from multiple vendors on a network.
PAGE 40
The NonStop SNMP Environment Figure 1-1.
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,” and gives the “public” community READONLY access Accepts any request received through the IPC interface and grants the requesting manager READWRITE access to all MIB objects supported
PAGE 42
Subsystem Components The NonStop SNMP Environment : Figure 1-2. Key Components in the SNMP Environment MIB Managed Resources Subagent Subagent Managed Resources MIB Managed Resources MIB Subagent System 1 Managed Resources SNMP Agent Managed Resources MIB SNMP Agent MIB System 3 System 2 Local Area Network Wide Area Network PDU MIB Definitions SNMP Manager Station PDU SNMP Manager Station MIB Definitions VST010.
PAGE 43
The NonStop SNMP Environment SNMP Manager 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. The SNMP manager sends requests to and receives responses from agent processes.
PAGE 44
SNMP Subagent The NonStop SNMP Environment SNMP agent is implemented, see Architectural Overview of NonStop SNMP on page 1-14. SNMP Subagent Entity used by HP (and other vendors), in their SNMP implementations. SNMP subagents handle a particular collection of resources. Some subagents are implemented as independent processes, and some are bound into other processes, such as the agent process. Some subagents, such as those shown in Figure 1-2, have their own MIBs.
PAGE 45
General SNMP Message Format The NonStop SNMP Environment 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; it is used for access control. Following the version and community identifiers is one of the five types of PDUs. Figure 1-3.
PAGE 46
The NonStop SNMP Environment Response PDU The three request PDUs are: • • • GetRequest PDU. This PDU performs a Get operation. The Get operation retrieves a value of a MIB object. GetNextRequest PDU. This PDU performs a GetNext operation. The GetNext operation retrieves the value of the object instance that is next in lexicographic order. SetRequest PDU. This PDU performs a Set operation. The Set operation alters the value of a MIB object.
PAGE 47
The NonStop SNMP Environment Information Protocol Also, all agents can interpret information encoded according to the basic encoding rules (BER) associated with ASN.1, which define how to encode an ASN.1 value as an octet string. BER-encoded packets can be transmitted over any transport protocol that the manager and target agent mutually support.
PAGE 48
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 As Figure 1-4 shows, an object identifier is a sequence of integers resulting from traversing a global tree.
PAGE 49
SNMP Naming Scheme The NonStop SNMP Environment Figure 1-4. Nodes in the SNMP Object Tree ccit (0) iso (1) identified-organization (3) dod (6) internet (1) directory (1) object identifier = 1.3.6.1.2.1.1 mgmt (2) mib-II (1) system (1) interfaces (2) at (3) ip (4) icmp (5) tcp (6) udp (7) egp (8) cmot (9) transmission (10) snmp (11) host (25) experimental (3) private (4) enterprises (1) tandem (169) object identifier = 1.3.6.1.4.1.169.3.155.
PAGE 50
The NonStop SNMP Environment The Management Information Base As Figure 1-4 indicates, MIB-II is described in the mgmt subtree. tandem has been assigned the value 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. The object identifier for the SNMP agent is: 1.3.6.1.4.1.169.
PAGE 51
The Management Information Base The NonStop SNMP Environment 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. Table 1-1. System Group Objects Supported by SNMP Agent's MIB Object and Attributes Definition Format of Value sysContact 1.3.6.1.2.1.1.
PAGE 52
The NonStop SNMP Environment Traps Traps Traps are unsolicited messages forwarded by an agent to SNMP managers when significant events occur. Some traps and their contents are defined by the SNMP standards. Other traps are proprietary. Traps that the SNMP agent supports are defined in Part 3, MIBs Supported by the SNMP Agent. Traps that subagents offered by HP generate are described in Part IV, SNMP Subagents. The SNMP agent can be configured to send traps to one or more specific SNMP managers.
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. The SNMP control file (SNMPCTL) contains configuration parameters for the SNMP agent.
PAGE 54
Architectural Overview of NonStop SNMP The NonStop SNMP Environment Figure 1-5. NonStop SNMP Architecture Independent SNMP Subagents EMS SNMPCTL Collector SNMP Agent MIB ZZSMPTRP SNMP Manager ZZSMPTRB TCP/IP ($ZTC0) Local Area Network Wide Area Network SNMP Manager Station SNMP Manager Station Legend IPC messages NSK operations SNMP request/response messages SNMP traps VST013.
PAGE 55
RFC Compliance The NonStop SNMP Environment 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). This document describes the SNMP architecture and message protocol.
PAGE 56
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 USA phone: 1-800-365-3642 mail: nic@nic.ddn.mil The Internet. If your site has IP-connectivity to the Internet community, you can use anonymous FTP to the host nic.ddn.mil (residing at 192.
PAGE 57
2 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 on page 2-23) EMS collector (Configuring the EMS Collector on page 2-25) Security (Configuring Security on page 2-26) TCP/IP request/response connections (Configuring TCP/IP Request/Response Connections on page 2-34) Trap destinatio
PAGE 58
Installing and Configuring the SNMP Agent Before You Configure the SNMP Agent Operations Environment which the SNMP agent communicates. This information you gather gives you an idea of the configuration you’ll need.
PAGE 59
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. When you start the SNMP agent, it performs these initialization tasks: • • • • • Ensures that the SNMP agent is running as a named process. If you did not specify a name, TACL assigns one.
PAGE 60
Installing and Configuring the SNMP Agent • • The Default SNMP Agent Sends event messages it generates to the EMS collector process $0 on the local node. Forwards requests pertaining to managed resources other than those defined in the System and SNMP MIB-II groups (which the SNMP agent itself processes) to the appropriate subagent, and returns responses to the requesting manager.
PAGE 61
The Default SNMP Agent Installing and Configuring the SNMP Agent Figure 2-1.
PAGE 62
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. Initially, the values shown in Table 2-1 are assigned to several objects in the SNMP agent's MIB.
PAGE 63
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. You also define some components of the SNMP agent configuration by using RUN line startup options, but these settings persist only as long as the agent process is running.
PAGE 64
Installing and Configuring the SNMP Agent RUN Command agent-process identifies the agent process. You can specify one through five alphanumeric characters, but the first character must be alphabetic. HP recommends using $ZSNMP to identify an SNMP agent. If you are running multiple SNMP agents on a single host (see Starting Multiple SNMP Agents on Each Node on page 2-23), HP recommends appending a digit: for example, $ZSNM0 and $ZSNM1.
PAGE 65
Installing and Configuring the SNMP Agent RUN Command backup-cpu-number specifies a backup process processor for a persistent agent process pair. 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. By default, this parameter is omitted.
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. An extensible data segment is one for which swap file extents are not allocated until needed.
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
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 Table 2-2. Summary of Startup Parameters (page 1 of 2) Startup Parameter What the Parameter Defines Default Behavior backup-cpu-number The backup process CPU for a persistent agent process pair. No parameter value is assigned, and no backup process is created. COLD | WARM Which SNMPCTL file to use while running. If SNMPCTL exists in the run subvolume, that file is used.
PAGE 70
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 [/node.]$tcpip-process The default TCP/IP process to be used when request/response connections and trap destinations are defined for the SNMP agent. For Parallel Library TCP/IP, this is the TCPSAM process.
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. To stop and restart an SNMP agent using the default configuration, you must stop the SNMP agent, purge the existing SNMPCTL file, and then restart the SNMP agent process using the WARM option.
PAGE 72
Installing and Configuring the SNMP Agent 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
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. Trap Connections The SCF TRAPDEST object identifies an Internet address and TCP/IP process to be used for the sending of trap messages.
PAGE 74
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 Figure 2-2. Running Multiple SNMP Agents on a Single Node Managed Resources Managed Resources Subagents Subagents SNMP Agent ($ZSNM0) SNMP Agent ($ZSNM1) 130.25.88.2 130.25.88.1 TCP/IP SNMP Manager VST202.
PAGE 76
Installing and Configuring the SNMP Agent Single-Node and Multiple-Node Scenarios In 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: RUN $SYSTEM.SYSTEM.SNMPAGT /NAME $ZSNM1, NOWAIT/ Caution.
PAGE 77
Single-Node and Multiple-Node Scenarios Installing and Configuring the SNMP Agent Figure 2-3. Running SNMP Agents on Multiple Nodes Managed Resources Managed Resources Managed Resources Subagents Subagents Subagents SNMP Agent SNMP Agent SNMP Agent SNMP Manager \C 130.88.25.3 130.88.25.1 \B 130.88.25.2 TCP/IP \A SNMP Manager VST203.vsd In Figure 2-3, SNMP agents on three different nodes process requests through the same TCP/IP process.
PAGE 78
Single-Node and Multiple-Node Scenarios Installing and Configuring the SNMP Agent Figure 2-4. Managing Overlapping Sets of Resources Managed Resources Managed Resources Subagents Subagents SNMP SNMP Agent 2 SNMP Agent 1 Agent 3 TCP/IP TCP/IP Subagents 130.88.25.2 130.88.26.2 130.88.26.1 Managed Resources 130.88.25.1 \C \A \B SNMP Manager X SNMP Manager Y VST204.vsd In Figure 2-4, two TCP/IP SNMP managers manage an overlapping set of resources.
PAGE 79
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*.* TCPIP Info SUBNET \EAST.$ZTC0.* Name Devicename #LOOP0 #EN1 \NOSYS.
PAGE 80
Stopping the SNMP Agent Installing and Configuring the SNMP Agent See the TCP/IPv6 Configuration and Management Manual for information about how to find the name of a TCP6SAM process. 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.
PAGE 81
Configuring the EMS Collector Installing and Configuring the SNMP Agent 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 STARTED OFF N/A status *, prog $system.system.snmpagt Process Hometerm Pri PFR %WT Userid $DMA 5,85 $T304.#TRM6 144 Program file 011 255,209 $SYSTEM.SYSTEM.
PAGE 82
Installing and Configuring the SNMP Agent Using the COLLECTOR Startup Parameter Using the COLLECTOR Startup Parameter To cause both primary and backup agent processes to send events to an EMS collector other than $0, include the COLLECTOR startup parameter when you start the SNMP agent.
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. For more information, refer to Configuring TCP/IP Request/Response Connections on page 2-34.
PAGE 84
Authenticating Requests Received Over TCP/IP Installing and Configuring the SNMP Agent Internet Addresses Each entry in the authentication table contains a single Internet address or a full wildcard address (0.0.0.0.) specification. Internet addresses are discussed in detail in the TCP/IP Configuration and Management Manual. When the SNMP agent finds a community name match, the SNMP agent looks at the address from which the request originated.
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.
PAGE 86
Authenticating Requests Received Over TCP/IP Installing and Configuring the SNMP Agent Figure 2-5. Authenticating Requests Received Through TCP/IP Request private::tsmaccess 130.253.15.230 GetNext SNMP Manager Station SNMP agent receives request. SNMP agent looks for entry containing community name. Authentication Table Response COMMUNITY ------------------- HOSTADDR ---------------------- ACCESS ------------------- Logical Identifer --------------------- Private 130.253.15.
PAGE 87
Installing and Configuring the SNMP Agent Authenticating Requests Received Using the IPC Interface In 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
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. When the SNMP agent forwards a request to a subagent, the forwarded request includes the Internet address and community string.
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) Scenario Tasks Revoke Set privileges from an SNMP manager, but allow it to retrieve information. Method (SCF Commands) Alternatively, you can simply alter the default PROFILE entry and assign READWRITE access to the “public” community. In this case, you should also alter the default host address to make it more restrictive.
PAGE 90
Configuring TCP/IP Request/Response Connections Installing and Configuring the SNMP Agent 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 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. For example: info subnet $ztc0.
PAGE 92
Multiple-Agent Connections Installing and Configuring the SNMP Agent Figure 2-6. Multiple Local SNMP Agents, Single Host Request/Response Connections SNMP Agent ($ZSNM0) SNMP Agent ($ZSNM1) 130.25.88.2 130.25.88.1 $ZTC0 SNMP Manager VST304.vsd In Figure 2-6 a successful configuration involving two SNMP agents uses the same TCP/IP process for request/response communications.
PAGE 93
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 subnet address.
PAGE 94
Configuring Trap Destinations Installing and Configuring the SNMP Agent Figure 2-7. Multiple Remote SNMP Agents, Single Host Request/Response Connections SNMP Agent ($ZSNMP) SNMP Agent SNMP Agent ($ZSNMP) ($ZSNMP) $ZTC0 \A SNMP Manager 130.25.86.3 130.25.86.2 130.25.86.1 \C \B SNMP Manager VST305.vsd Configuring Trap Destinations Each SNMP manager to which the SNMP agent process sends trap messages is represented by a trap destination definition.
PAGE 95
Configuring Trap Destinations Installing and Configuring the SNMP Agent A trap destination definition has the following attributes: SCF 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. COMMUNITY or zagInTdCommunity specifies the name included in trap messages.
PAGE 96
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
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” host).
PAGE 98
Single-Host Connections Installing and Configuring the SNMP Agent Single-Host Connections Figure 2-8. Multiple SNMP Agents, Single Host Connections SNMP Agent ($ZSNM0) SNMP Agent ($ZSNM1) 130.25.88.1 130.25.88.2 $ZTC1 $ZTC0 SNMP Manager Station 1 (at 130.25.86.15) SNMP Manager Station 2 Legend Trap PDUs Request/Response PDUs VST306.vsd In Figure 2-8, two SNMP agents receive requests through one TCP/IP process and send trap messages to the same destination through a different TCP/IP process.
PAGE 99
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 STOP ENDPOINT #DEFAULT ALTER ENDPOINT #DEFAULT, HOSTADDR 130.25.88.
PAGE 100
Multiple-Host Connections Installing and Configuring the SNMP Agent Figure 2-9. Multiple SNMP Agents, Multiple Host Connections SNMP Agent ($ZSNMP) SNMP Agent ($ZSNMP) SNMP Agent ($ZSNMP) $ZTC0 \A \C SNMP Manager 1 (at 130.25.86.5) 130.25.86.4 130.25.86.3 130.25.86.2 130.25.86.1 \B SNMP Manager 2 (at 130.25.86.4) Legend Request/Response PDUs Trap PDUs VST307.
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, & HOSTADDR 130.25.86.3 START #DEFAULT ADD TRAPDEST #STA2, NETWORK \B.$ZTC0, & HOSTADDR 130.25.86.
PAGE 102
Installing and Configuring the SNMP Agent Multiple-Host Connections SNMP Configuration and Management Manual—424777-006 2- 46
PAGE 103
3 MIBs Supported by the SNMP Agent The SNMP agent supports two MIB-II groups and one private MIB group. The two MIBII 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. Definitions for objects within the SNMP agent’s private MIB are contained in the file ZSMPMIB.
PAGE 104
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) tandem (169) nonstopsystems (3) zsmp (155) zsmpagent (1) zagInternal (7) zagInProcess (1)√ zagInEndpoint (2)√ zagInProfile (3)√ zagInTrapdest (4)√ In this section, System group objects are defined in the subsection System Group.
PAGE 105
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) √ sysDescr (1) √ sysObjectID (2) √ sysUpTime (3) √ sysContact (4) √ sysName (5) √ sysLocation (6) √ sysServices (7) √ MIB Objects Table 3-1 describes the MIB-II System group objects that are supported by the SNMP agent.
PAGE 106
MIB Objects MIBs Supported by the SNMP Agent Table 3-1. System Group Objects Supported by SNMP Agent (page 1 of 2) Object and Attributes sysDescr 1.3.6.1.2.1.1.1 read-only DisplayString (SIZE (0..255)) Definition Format and Derivation of Value A description of the node on which the SNMP agent is installed. NonStop Kernel system version: Dxx or Gxx Node: node-name Agent: agent-process-name Returned by Guardian procedure calls. sysObjectID 1.3.6.1.2.1.1.
PAGE 107
RFC Compliance MIBs Supported by the SNMP Agent Table 3-1. System Group Objects Supported by SNMP Agent (page 2 of 2) Object and Attributes Definition Format and Derivation of Value sysName 1.3.6.1.2.1.1.5 read-write DisplayString (SIZE (0..255)) A name associated with an Internet address by which the SNMP agent can be reached. A character string of 255 or fewer characters.
PAGE 108
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.
PAGE 109
MIB Objects MIBs Supported by the SNMP Agent 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) Object and Attributes Definition Format and Derivation of Value snmpInPkts 1.3.6.1.2.1.11.1 read-only Counter The total number of messages received. An integer set by the SNMP agent counter. snmpOutPkts 1.3.6.1.2.1.11.2 read-only Counter The total number of SNMP messages sent.
PAGE 110
MIB Objects MIBs Supported by the SNMP Agent Table 3-2. SNMP Group Objects Supported by SNMP Agent (page 2 of 3) Format and Derivation of Value Object and Attributes Definition snmpInReadOnlys 1.3.6.1.2.1.11.11 read-only Counter The total number of valid PDUs received for which the value of the error-status field was ‘readOnly.’ The constant value for this object is 0. snmpInGenErrs 1.3.6.1.2.1.11.
PAGE 111
MIB Objects MIBs Supported by the SNMP Agent Table 3-2. SNMP Group Objects Supported by SNMP Agent (page 3 of 3) Format and Derivation of Value Object and Attributes Definition snmpOutNoSuchNames 1.3.6.1.2.1.11.21 read-only Counter The total number of PDUs generated for which the value of the error-status field was ‘noSuchName.’ An integer set by the SNMP agent counter. snmpOutBadValues 1.3.6.1.2.1.11.
PAGE 112
MIBs Supported by the SNMP Agent RFC Compliance RFC Compliance All of the objects described in Table 3-2 comply with the definitions for SNMP group objects as set forth in 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.
PAGE 113
MIB Objects MIBs Supported by the SNMP Agent 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) √ zagInTrapdest (4) zagInDirectedTrapdestName (1
PAGE 114
MIB Objects MIBs Supported by the SNMP Agent Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 1 of 8) Format and Derivation of Value Object and Attributes Definition zagInProcess Group Objects: Describe the attributes of the SNMP agent’s process. zagInProcCurrTime 1.3.6.1.4.1.169.3.155.1.7.1.1 read-only DisplayString A string that shows the current time. month DD, YYYY HH:MM:SS:centisecond value, which is derived from SNMP agent calls to the Guardian procedure JULIANTIMESTAMP.
PAGE 115
MIB Objects MIBs Supported by the SNMP Agent Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 2 of 8) Format and Derivation of Value Object and Attributes Definition zagInProcBkupPID 1.3.6.1.4.1.169.3.155.1.7.1.6 read-only DisplayString A string that shows the backup process PID (cpu,pin) for the agent. The cpu,pin value is assigned by the RUN command PRI option or by $CMON. Derived from SNMP agent calls to the Guardian procedure PROCESS_ GETPAIRINFO_. zagInProcCreatTime 1.3.6.1.4.
PAGE 116
MIB Objects MIBs Supported by the SNMP Agent Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 3 of 8) Format and Derivation of Value Object and Attributes Definition zagInProcMaxOpeners 1.3.6.1.4.1.169.3.155.1.7.1.11 read-only INTEGER The maximum number of subagent and SCF (Subsystem Control Facility) sessions that the SNMP agent can support at one time. A numeric value assigned by the RUN command MAXOPENERS startup parameter option. The default value is 20.
PAGE 117
MIB Objects MIBs Supported by the SNMP Agent Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 4 of 8) Object and Attributes zagInEpName 1.3.6.1.4.1.169.3.155.1.7.2.1.1.2 read-only DisplayString (SIZE (2..8)) zagInEpState Definition The name assigned to this endpoint. This object is created when the SNMP agent extracts the index value from the initial row creation varbind. $agentName. #endpointName The SNMP agent prepends $agentName to #endpointName.
PAGE 118
MIB Objects MIBs Supported by the SNMP Agent Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 5 of 8) Format and Derivation of Value Object and Attributes Definition zagInProfile Group Objects: Define criteria that the SNMP agent uses to determine whether to accept or reject incoming requests from SNMP managers that communicate with the SNMP agent through TCP/IP.
PAGE 119
MIB Objects MIBs Supported by the SNMP Agent Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 6 of 8) Format and Derivation of Value Object and Attributes Definition zagInPfState The current operational state of the profile. Possible states are: DEFINED (1) STARTED (3) STARTING (4) STOPPED (5) Default value is DEFINED. Set by the SNMP agent. The address of the host sending the message.
PAGE 120
MIB Objects MIBs Supported by the SNMP Agent Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 7 of 8) Format and Derivation of Value Object and Attributes Definition zagInDirectedTrapdestName 1.3.6.1.4.1.169.3.155.1.7.4.1 read-only DisplayString (SIZE (2..8)) This object is used by the subagent to specify a trap destination name (zagInTdName) in the agent’s trap destination table to which a directed trap is sent.
PAGE 121
MIB Objects MIBs Supported by the SNMP Agent Table 3-3. zagInternal Group Objects Supported by SNMP Agent (page 8 of 8) Format and Derivation of Value Object and Attributes Definition zagInTdState The current operational state of the trap destination. One of these four numeric state values, which can only be read: DEFINED (1) STARTED (3) STARTING (4) STOPPED (5) Default value is DEFINED. Set by the SNMP agent. The address of the host which is to receive trap messages. Format of #.#.#.#.
PAGE 122
SNMP Manager Access to Private MIB Objects MIBs Supported by the SNMP Agent 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. For a detailed definition of all of the SNMP agent’s private MIB objects, see Table 3-3. Table 3-4.
PAGE 123
SNMP Manager Access to Private MIB Objects MIBs Supported by the SNMP Agent Table 3-4. Access Status of SNMP Agent’s Private MIB Objects (page 2 of 3) Object Name Object Syntax Manager Access zagInEpState Integer read-only The operational state of the endpoint. zagInEpHostAddr DisplayString read-write The local host IP address the agent is to monitor for incoming messages.
PAGE 124
Table Row Management Overview MIBs Supported by the SNMP Agent Table 3-4. Access Status of SNMP Agent’s Private MIB Objects (page 3 of 3) Object Name Object Syntax Manager Access zagInTdCommunity DisplayString read-write The name that the SNMP agent returns in traps sent to the trap destination. zagInTdNetwork DisplayString read-write The name of the TCP/IP process that the agent uses to send traps. zagInTdType Integer read-write The trap type: broadcast or directed.
PAGE 125
Table Row Management Overview MIBs Supported by the SNMP Agent Table 3-5.
PAGE 126
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. Note.
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 be written. Is supplied in a Set command by the management application that wants to create a new row and have it available for use by the SNMP agent. createAndWait (5) An action value that can only be written.
PAGE 128
Managing Table Rows From SNMP Managers MIBs Supported by the SNMP Agent zagInPfRowStatus Object1 Set one of the following row status objects (denoted in the next three columns) to this value... zagInTdRowStatus Object To do this... zagInEpRowStatus Object Table 3-7. RowStatus Values and Table Management Operations (page 1 of 2) The row state object2 will be set to... The equivalent SCF command issued against an ENDPOINT, TRAPDEST, or PROFILE object is... Create a table row.
PAGE 129
Managing Table Rows From SNMP Managers MIBs Supported by the SNMP Agent zagInPfRowStatus Object1 Set one of the following row status objects (denoted in the next three columns) to this value... zagInTdRowStatus Object To do this... zagInEpRowStatus Object Table 3-7. RowStatus Values and Table Management Operations (page 2 of 2) The row state object2 will be set to... The equivalent SCF command issued against an ENDPOINT, TRAPDEST, or PROFILE object is... Remove a table row.
PAGE 130
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.
PAGE 131
Default Values for Table Row Objects MIBs Supported by the SNMP Agent 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 Attribute zagInEndpointTable Default Value zagInTrapdestTable Default Value zagInProfileTable Default Value NAME none; a name must be supplied by an authorized SNMP management application.
PAGE 132
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). If the RowStatus value is active (1), assign it the value notInService (2) and then make your modifications. To reactivate the entry, assign its RowStatus object the value active (1).
PAGE 133
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
Authentication Table Entries MIBs Supported by the SNMP Agent 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. sysObjectID 1.3.6.1.4.1.169.3.155.
PAGE 135
Authentication Table Entries MIBs Supported by the SNMP Agent Table 3-11. SNMP Agent Private MIB Objects That Describe the SNMP Operations Environment (page 2 of 4) SNMP Agent Private MIB Object What the Object Defines and Its Default Value Equivalent SCF Construct zagInEpName A name that serves as an index into the table, uniquely identifying the table row containing the request/response connection definition.
PAGE 136
Authentication Table Entries MIBs Supported by the SNMP Agent Table 3-11. SNMP Agent Private MIB Objects That Describe the SNMP Operations Environment (page 3 of 4) SNMP Agent Private MIB Object What the Object Defines and Its Default Value Equivalent SCF Construct zagInTdHostAddr The Internet address of an SNMP manager to receive traps.
PAGE 137
Authentication Table Entries MIBs Supported by the SNMP Agent Table 3-11. SNMP Agent Private MIB Objects That Describe the SNMP Operations Environment (page 4 of 4) SNMP Agent Private MIB Object What the Object Defines and Its Default Value Equivalent SCF Construct zagInPfName A name that serves as an index into the table, uniquely identifying the table row defining the entry. #profile-name zagInPfState The operational state of the authentication table entry.
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. Each row in the zagInProfileTable corresponds to an SCF PROFILE object. Note.
PAGE 139
Part II.
PAGE 140
Part II.
PAGE 141
4 Introduction to SCF for the SNMP Agent The Subsystem Control Facility (SCF) provides a common syntax for managing HP subsystems. Managing a subsystem involves configuring, controlling, and inquiring about subsystem components known as objects. This section provides an introduction to using SCF to manage the Simple Network Management Protocol (SNMP) agent product offered by HP—the NonStop agent. • • If you have worked with SCF before, you can skip to TRACE Command on page 5-35.
PAGE 142
SCF and the DSM Family of Products Introduction to SCF for the SNMP Agent If you start the NonStop agent with its built-in defaults, you can use SCF to modify the default configuration values. If you start the NonStop agent without any predefined configuration values, you can enter the complete configuration through SCF. SCF and the DSM Family of Products SCF is part of the Distributed Systems Management (DSM) family of products.
PAGE 143
Objects Introduction to SCF for the SNMP Agent 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. There might be multiple instances of some objects, but not others. For example, in each NonStop agent environment, there can be only one PROCESS object, but many TRAPDEST objects.
PAGE 144
Object Hierarchy Introduction to SCF for the SNMP Agent 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 Introduction to SCF for the SNMP Agent 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. The NonStop agent also generates and sends traps it or the subagents with which it is communicating generate to managers configured to receive them.
PAGE 146
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
Default PROCESS Object Introduction to SCF for the SNMP Agent 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. STARTED SNMP agent process stopped outside of SCF: TACL> STOP $ZSNMP VST005.
PAGE 148
The ENDPOINT Object Introduction to SCF for the SNMP Agent The ENDPOINT Object The ENDPOINT object type represents a network interface the NonStop agent process uses to accept manager requests and return responses.
PAGE 149
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. The syntax for specifying an ENDPOINT object type: command ENDPOINT [$agent-process.]#endpoint-name Note.
PAGE 150
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. STARTED The ENDPOINT object is either ready to accept or in the process of handling requests.
PAGE 151
Default ENDPOINT Object Introduction to SCF for the SNMP Agent 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 ENDPOINT DEFINED DELETE ENDPOINT START ENDPOINT Yes Are all underlying resources available? No STARTED ABORT/STOP ENDPOINT Are any requests currently being processed? Yes Underlying resource becomes available.
PAGE 152
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.
PAGE 153
Naming Conventions: PROFILE Object Introduction to SCF for the SNMP Agent Figure 4-7. The PROFILE Object Authentication Table Entry Entry . . Subagent Managed Resources SNMP Agent EMS Collector TCP/IP #su01 #su02 ∠Ν 2 SNMP Manager VST010.
PAGE 154
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 The PROFILE object has been configured with the SCF ADD command but has not been initially activated for use in the NonStop agent authentication scheme.
PAGE 155
Default PROFILE Object Introduction to SCF for the SNMP Agent 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/ STOP PROFILE DEFINED DELETE PROFILE START PROFILE STARTED ABORT/STOP START PROFILE PROFILE STOPPED DELETE PROFILE VST011.
PAGE 156
The TRAPDEST Object Introduction to SCF for the SNMP Agent The TRAPDEST Object The TRAPDEST object type represents a manager to which the NonStop agent process can send trap messages.
PAGE 157
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
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. STARTING The TRAPDEST object is in the process of starting. If an underlying resource is unavailable, it remains in the STARTING state until the resource becomes available. At that time it enters the STARTED state.
PAGE 159
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
SCF-Configured Trap Destination Limitations: Broadcast Only Introduction to SCF for the SNMP Agent 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 ABORT/STOP TRAPDEST DELETE TRAPDEST DEFINED START TRAPDEST STARTING Underlying resource becomes unavailable. STARTED ABORT/STOP TRAPDEST STOPPED Yes SNMP agent generates coldStart trap.
PAGE 161
Introduction to SCF for the SNMP Agent Running SCF Running SCF You can run SCF interactively or noninteractively. SCF can accept input from either a terminal or a command file (OBEY file) and can direct output to either a terminal, disk file, or printer. In its simplest form, the syntax for running SCF from TACL is as follows: [ RUN ] [[$vol.]subvol.
PAGE 162
SCF Commands for Managing a Subsystem Introduction to SCF for the SNMP Agent 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. The ASSUME command defines a default object to be used when the object is omitted from an SCF command.
PAGE 163
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
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. If file-spec has the form of a disk-file name but the file does not exist, an EDIT file is created. If the name of the file is an existing disk file, the output is appended to the file.
PAGE 165
Introduction to SCF for the SNMP Agent Displaying Help for SCF Error Messages The next request returns information about the NonStop agent TRAPDEST object: -> HELP SNMP TRAPDEST This request returns information about the ADD command when it is issued against a TRAPDEST object: -> HELP SNMP ADD TRAPDEST Displaying Help for SCF Error Messages To request help for SCF error messages: -> HELP subsystem error-number For example, suppose the following messages appear on your terminal: SNMP E00001 Attribute conf
PAGE 166
Introduction to SCF for the SNMP Agent The SCF Product Module for the NonStop Agent you start the NonStop agent process. For startup parameters and configuration through SNMP, see Configuring the SNMP Agent Through SNMP Requests on page 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
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
5 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 START Command on page 5-26 STATUS Command on page 5-28 STOP Command on page 5-32 TRACE Command on page 5-35 VERSION Command on page 5-37 Table 5-1.
PAGE 170
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 GSeries 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
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 between a NonStop agent process and managers. ABORT ENDPOINT [$agent-process.]#endpoint-name [$agent-process.
PAGE 172
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
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. ABORT TRAPDEST [$agent-process.]#trapdest-name [$agent-process.]#trapdest-name identifies the trap destination being inactivated.
PAGE 174
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. $agent-process identifies the NonStop agent process to which the ENDPOINT object belongs.
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. The value 0 is recognized as a wildcard in the host addressing scheme for the HOSTADDR attribute.
PAGE 176
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. $agent-process identifies the NonStop agent process to which the PROFILE object belongs.
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. Members of the community can only retrieve information. READWRITE The NonStop agent accepts Set, Get, and GetNext requests from the associated community.
PAGE 178
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: -> ADD PROFILE $ZSNMP.#LANMGR, COMMUNITY "Private", & -> ACCESS READWRITE, HOSTADDR "130.252.86.10" -> START PROFILE $ZSNMP.
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. For more information, see the Part II, SCF for the SNMP Agent.
PAGE 181
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: -> ADD TRAPDEST $ZSNMP.#TRAP, COMMUNITY "Public", & -> HOSTADDR "130.252.86.
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 ($). The first alphanumeric character must be a letter.
PAGE 183
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. It consists of a dollar sign ($) followed by one to five alphanumeric characters, the first of which must be alphabetic. EMSCOLL [\node.
PAGE 184
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. ALTER PROFILE [$agent-process.]#profile-name [ , COMMUNITY "community-name" ] [ , HOSTADDR "ip-address"] [ , ACCESS { READONLY | READWRITE } ] [$agent-process.
PAGE 185
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. Members of the community can only retrieve information. READWRITE The NonStop agent accepts Set, 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. “community-name” is a case-sensitive of 1 to 50 character enclosed string within quotation marks. NETWORK [\node.
PAGE 187
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 definition from a NonStop agent configuration. DELETE ENDPOINT [$agent-process.]#endpoint-name $agent-process.
PAGE 188
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. It consists of a pound sign (#) followed by one to seven alphanumeric characters, the first of which must be alphabetic.
PAGE 189
INFO Command SCF Commands for the SNMP Agent 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. INFO ENDPOINT [$agent-process.]#endpoint-name [, DETAIL ] [$agent-process.
PAGE 190
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. It consists of a dollar sign ($) followed by one to five alphanumeric characters, the first of which must be alphabetic.
PAGE 191
INFO PROFILE Command SCF Commands for the SNMP Agent SNMP Info PROFILE Name *Access *Community $ZSNMP.#DEFAULT READONLY $ZSNMP.#LANMGR READWRITE *Hostaddr 0.0.0.0 130.252.86.10 public Private SNMP Info ENDPOINT Name *Network $ZSNMP.#DEFAULT \EAST.$ZTC0 $ZSNMP.#REMOTE \WEST.$ZTC0 *Hostaddr 0.0.0.0 0.0.0.0 SNMP Info TRAPDEST Name *Community $ZSNMP.#TRAP $ZSNMP.#REMOTE *Network *Hostaddr \EAST.$ZTC0 \WEST.$ZTC1 130.252.86.10 130.252.86.
PAGE 192
INFO TRAPDEST Command SCF Commands for the SNMP Agent 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 $ZSNMP.#DEFAULT READONLY $ZSNMP.#LANMGR READWRITE *Hostaddr 0.0.0.0 130.252.86.10 *Community public Private INFO TRAPDEST Command Use the INFO TRAPDEST command to display the current attribute values for a trap destination definition.
PAGE 193
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. It consists of a dollar sign ($) followed by one to five alphanumeric characters, the first of which must be alphabetic.
PAGE 194
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
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. #profile-name identifies the PROFILE object.
PAGE 196
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: -> START TRAPDEST $ZSNMP.
PAGE 197
STATUS PROCESS Command SCF Commands for the SNMP Agent 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. The ENDPOINT object enters the STOPPED state as soon as processing is finished.
PAGE 198
STATUS PROFILE Command SCF Commands for the SNMP Agent Considerations: STATUS PROCESS The NonStop agent process is always reported as being in the STARTED state.
PAGE 199
STATUS TRAPDEST Command SCF Commands for the SNMP Agent $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. It consists of a pound sign (#) followed by one to seven alphanumeric characters, the first of which must be alphabetic.
PAGE 200
STOP Command SCF Commands for the SNMP Agent #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; it does not indicate whether the manager is available to receive those trap messages.
PAGE 201
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
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. It consists of a pound sign (#) followed by one to seven alphanumeric characters, the first of which must be alphabetic.
PAGE 203
TRACE Command SCF Commands for the SNMP Agent 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.
PAGE 204
TRACE Command SCF Commands for the SNMP Agent 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. If you omit this option or set it to 0, the default value of 10,000 is assumed. RECSIZE size specifies the length of the data in the trace data records.
PAGE 205
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. The trace procedure stores this information in a trace file.
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. If it is omitted, only one line of version information is displayed.
PAGE 207
Part III.
PAGE 208
Part III.
PAGE 209
6 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
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. VST007.vsd The following steps are involved in recording and displaying trace data. 1. To start the trace interactively, issue the SCF TRACE command.
PAGE 211
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 ] ... run-option-list is one or more NonStop Kernel run options, as described in the TACL Reference Manual.
PAGE 212
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. If PTrace encounters an error in a command, it terminates immediately.
PAGE 213
PTrace Commands Supported by the NonStop Agent SNMP Agent PTrace Facility 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
SNMP Agent PTrace Facility FROM Command Table 6-1.
PAGE 215
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
SNMP Agent PTrace Facility NEXT Command date is an optional parameter in the following form: mm/dd/yyyy Note. The year field must be four digits. If date is omitted, it is replaced by the date found in the previously displayed record. If there is no previously displayed record, the date is taken from the trace file header (start of trace). time represents a 24-hour-clock time in the following form: hh:mm[:ss[.tttttt]] You must specify the hours (hh) and minutes (mm).
PAGE 217
RECORD Command SNMP Agent PTrace Facility 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 Function name: SnmpAgent_Thread Thread name: SnmpAgent ID:1 Method class: SnmpAgent Method name: Thread Object Count:0 Paramstring: 11:27:52.240 >000.
PAGE 218
SELECT Command SNMP Agent PTrace Facility 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: NIL ID:0 Method class: dictionary Method name: KeySearch Object Count:2 Object: dictionary Object ADDR:612610D Object: UNKNOWN Object ADDR:612562D 2.
PAGE 219
SELECT Command SNMP Agent PTrace Facility 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.
PAGE 220
SELECT Command SNMP Agent PTrace Facility 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: 1 ?NEXT 2 11:27:50.760 >000.000 #2 11:27:50.760 >000.000 #3 Method Method 3. The next example selects the trace records written by the Common Kernel and displays the next two records: ?SELECT COMMON Ptrace Select Key: 254 ?NEXT 2 End of Trace file. 4.
PAGE 221
7 Troubleshooting the SNMP Agent This section contains general guidelines about what to do when you encounter problems starting the SNMP agent.
PAGE 222
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.
PAGE 223
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. This distributor writes event messages to a printer or other display device or to a file. Using the operator console.
PAGE 224
Troubleshooting the SNMP Agent Compiling the Filter Compiling the Filter Before using a filter, you must compile it with the EMS filter compiler, EMF. Because filters are based on the HP Tandem Advanced Command Language (TACL), you load the TACL versions of the data definition language (DDL) files containing the definitions used in your filter. The following TACL routine defines a TACL macro named USESPI, which makes the SPI SEGF files usable to TACL.
PAGE 225
Troubleshooting the SNMP Agent 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. For information on analyzing trace information with the PTrace utility, see the TCP/IP Configuration and Management Manual (G-series).
PAGE 226
Diagnosing Request Errors Troubleshooting the SNMP Agent 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
Diagnosing Request Errors Troubleshooting the SNMP Agent Table 7-1. Handling Requests That Cannot Be Processed (page 2 of 3) SNMP Group Counter Incremented Error-Status Value Assigned The SNMP agent receives a GetRequest PDU for an object that HP does not support. snmpOutNoSuchNames noSuchName The SNMP agent receives a SetRequest PDU from a community assigned READONLY access. snmpInBadCommunityUses The SNMP agent receives a SetRequest PDU for a MIB object assigned readonly access.
PAGE 228
Diagnosing Request Errors Troubleshooting the SNMP Agent Table 7-1. Handling Requests That Cannot Be Processed (page 3 of 3) SNMP Group Counter Incremented Error-Status Value Assigned A SetRequest PDU attempts to assign an invalid value to a MIB object. snmpOutBadValues badValue SNMP agent stops processing the request. Any other condition that does not produce a normal response, such as certain errors returned in the SPI interface. snmpOutGenErrs genErr SNMP agent stops processing the request.
PAGE 229
Part IV.
PAGE 230
Part IV.
PAGE 231
8 TCP/IP Subagent The TCP/IP Subagent supports the MIB-II groups that allow TCP/IP resources (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
Architectural Overview TCP/IP Subagent • The SNMP agent sends response messages to the SNMP manager from which the request originated. 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. The only information the TCP/IP Subagent retrieves regarding an underlying X.
PAGE 233
Architectural Overview TCP/IP Subagent Figure 8-2.
PAGE 234
TCP/IP Subagent 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. Each TCP/IP Subagent can monitor subnets associated with the multiple TCP/IP subsystems.
PAGE 235
The NonStop TCP/IPv6 Subagent and its Managed Resources TCP/IP Subagent 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. If you want to implement Logical Network Partitions (LNPs), you must start an instance of the SNMP agent for every LNP though which you want to provide SNMP services.
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.
PAGE 237
Private MIB Objects Supported by the TCP/IP Subagent TCP/IP Subagent Private MIB Objects Supported by the TCP/IP Subagent The TCP/IP Subagent also supports private MIB objects that: • • Provide information about the subagent process itself, such as: ° ° ° Allow you to control certain aspects of the subagent’s behavior, such as: ° • The name of the subagent process The processor in which subagent’s primary process is running The name of the TCP/IP process controlling the managed TCP/IP subsystem °
PAGE 238
Unavailable Resources TCP/IP Subagent simply encodes and sends an SPI request to the subsystem. When the response is received, the TCP/IP Subagent extracts the desired token, field, or word offset from the reply buffer and returns the obtained value. Certain requests require more complex SPI interaction. When an intermediate value must be obtained, the value returned is obtained after two or more successive SPI interactions. A few MIB-II objects have constant values declared.
PAGE 239
Refreshing MIB Values TCP/IP Subagent Refreshing MIB Values The TCP/IP Subagent does not access TCP/IP data on demand. At startup time and at regular intervals, data is refreshed, stored in a cache, and returned to the manager through the SNMP agent when MIB values are requested.
PAGE 240
Initiating Backup Process Takeover TCP/IP Subagent 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 TCP/IP Subagent Related Documents The TCP/IP Management Programming Manual provides information to help interpret the meanings of values for MIB-II group objects supported by the TCP/IP Subagent.
PAGE 242
Before Starting the TCP/IP Subagent TCP/IP Subagent Compile the ZTSAMIB file (and the RFC1213 file if necessary) 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. Once the MIB definition files have been compiled, the TCP/IP Subagent can be started.
PAGE 243
Starting the TCP/IP Subagent TCP/IP Subagent volume identifies the volume on which the TCP/IP Subagent program file (TCPIPSA) resides. You can omit it if TCPIPSA resides on your current subvolume. By default, the Install or DSM/SCM program puts TCPIPSA into $SYSTEM. subvolume identifies the subvolume on which TCPIPSA resides. You can omit it if it is named in your TACL #PMSEARCHLIST. By default, the Install or DSM/SCM program puts TCPIPSA into SYSTEM.
PAGE 244
Starting the TCP/IP Subagent 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. -c [\node.]$collector-process is the name of the collector to which the subagent is to send EMS event messages it generates.
PAGE 245
Starting the TCP/IP Subagent 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. The maximum number of TCP/IP subsystems that can be monitored using this option is 32. Note.
PAGE 246
Stopping the TCP/IP Subagent 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.
PAGE 247
Controlling a Running TCP/IP Subagent TCP/IP Subagent Table 8-1. Querying a TCP/IP Subagent Through SNMP (page 2 of 2) You can find out this about the TCP/IP Subagent... By issuing an SNMP Get request against this ztsa object...
PAGE 248
Controlling a Running TCP/IP Subagent TCP/IP Subagent Table 8-2. Controlling a TCP/IP Subagent Through SNMP (page 1 of 2) Initially set with this startup parameter... You can control this attribute of a TCP/IP Subagent... By issuing SNMP Set requests against this ztsa object... Current process priority of subagent process ztsaProcessPriority Processor in which subagent’s backup process is running or will start ztsaBackupCPU State of the subagent’s backup process ztsaBackupState None.
PAGE 249
Controlling a Running TCP/IP Subagent TCP/IP Subagent Table 8-2. Controlling a TCP/IP Subagent Through SNMP (page 2 of 2) You can control this attribute of a TCP/IP Subagent... By issuing SNMP Set requests against this ztsa object... Initially set with this startup parameter... Rate at which SPI STATISTICS based object values are refreshed ztsaStatsCache -stats 60 seconds. Rate at which SPI STATUS based object values are refreshed ztsaStatusCache -status 90 seconds.
PAGE 250
ZTSA MIB Objects TCP/IP Subagent 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) tandem (169) nonstopsystems (3) ztsa (202) ztsaAgentName (1) ztsaAgentState (2) ztsaProcessName (3) ztsaProcessVersion (4) ztsaProgramFile (5) ztsaProcessPriority (6) ztsaProcessGroupID (7) ztsaProcessUserID (8)
PAGE 251
ZTSA MIB Objects TCP/IP Subagent Table 8-3 defines each object in the ztsa subtree. Table 8-3. Private (ZTSA) MIB Objects Supported by the TCP/IP Subagent (page 1 of 7) Object and Attributes Definition Format and Derivation of Value ztsaAgentName 1.3.6.1.4.1.169.3.202.1 read-only DisplayString (SIZE (0..31)) The name of the SNMP agent process with which the TCP/IP Subagent is communicating. \node.$agent-process specified for the -a startup parameter. If none specified, $ZSNMP on the local node.
PAGE 252
ZTSA MIB Objects TCP/IP Subagent 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 1.3.6.1.4.1.169.3.202.8 read-only INTEGER (0..255) The user ID number of the user who started the TCP/IP Subagent. user-ID-number returned by a Guardian PROCESS_GETINFO procedure call. ztsaPrimaryCPU 1.3.6.1.4.1.169.3.202.9 read-only INTEGER (0..
PAGE 253
ZTSA MIB Objects TCP/IP Subagent 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* 1.3.6.1.4.1.169.3.202.13 read-write INTEGER The state of the TCP/IP Subagent backup process.
PAGE 254
ZTSA MIB Objects TCP/IP Subagent 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* 1.3.6.1.4.1.169.3.202.16 read-write INTEGER The state of the connection between the TCP/IP Subagent and the EMS collector. Following are valid values for the state of the connection: connected (1) disconnected (2) disabled (3) enabled (4) The connected and disconnected states are set internally.
PAGE 255
ZTSA MIB Objects TCP/IP Subagent 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 1.3.6.1.4.1.169.3.202.19 read-write INTEGER (0..32000) The cache update interval (in seconds) for objects updated using the SPI STATISTICS command. A value in the range 0 to 32000 specified for the -stats startup parameter. The default is 60 seconds. After startup, the value can be set by an SNMP manager.
PAGE 256
ZTSA MIB Objects TCP/IP Subagent 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* 1.3.6.1.4.1.169.3.202.23 read-write INTEGER The state of the connection between the TCP/IP Subagent and the monitored TCP/IP process. Following are valid values for the state of the connection: connected (1) disconnected (2) disabled (3) enabled (4) The connected and disconnected states are set internally.
PAGE 257
ZTSA MIB Objects TCP/IP Subagent 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 1.3.6.1.4.1.169.3.202.27.1 not-accessible The entry that contains information related to the subnets associated with the TCP/IP subsystems. Contains the ztsaSubnetName, ztsaSubnetAddr and ztsaSubnetStatus fields. ztsaSubnetName 1.3.6.1.4.1.169.3.202.27.1.
PAGE 258
State Object/Resource Object Pairs TCP/IP Subagent 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.” Table 8-4 lists the resource objects and their associated state objects and state values. Table 8-4.
PAGE 259
State Object/Resource Object Pairs TCP/IP Subagent 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. • “Connect Success,” “Connect Failure,” and “Resource Fault” all relate to actions and events detected by the subagent.
PAGE 260
Interfaces Group TCP/IP Subagent When the state object has been placed in the “Enabled” state, the TCP/IP 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” state. The TCP/IP Subagent continues to attempt to reconnect at the rate specified for the ztsaKeepAliveTimer object.
PAGE 261
MIB Objects TCP/IP Subagent ifOutErrors (20) √ ifOutQLen (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 Format and Derivation of Value ifNumber 1.3.6.1.2.1.2.
PAGE 262
MIB Objects TCP/IP Subagent Table 8-5. Interfaces Group Objects Supported by TCP/IP Subagent (page 2 of 7) Object and Attributes ifDescr 1.3.6.1.2.1.2.2.1.2 read-only DisplayString (SIZE (1..255)) Definition Format and Derivation of Value Identification of a physical interface. $ZZLAN.lif zzz , where $line is the name of a TLAM or X.25 line associated with a TCP/IP subnet. xxx is the server banner returned from a GETVERSION command on a TLAM LINE object.
PAGE 263
MIB Objects TCP/IP Subagent Table 8-5. Interfaces Group Objects Supported by TCP/IP Subagent (page 3 of 7) Object and Attributes ifMtu 1.3.6.1.2.1.2.2.1.4 read-only INTEGER Definition Format and Derivation of Value The size of the largest datagram that can be sent or received on the interface, in octets.
PAGE 264
MIB Objects TCP/IP Subagent Table 8-5. Interfaces Group Objects Supported by TCP/IP Subagent (page 4 of 7) Object and Attributes ifPhysAddress 1.3.6.1.2.1.2.2.1.6 read-only PhysAddress Definition Format and Derivation of Value The interface’s address at the protocol layer immediately below the network layer in the protocol stack.
PAGE 265
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.2.2.1.9 read-only TimeTicks The value of sysUpTime at the time the interface entered its current operational state. If the current state existed prior to the last reinitialization of the SNMP agent, the value is 0. ifInOctets 1.3.6.1.2.1.2.2.1.
PAGE 266
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.2.2.1.15 read-only Counter The number of packets received via the interface that were discarded because of an unknown or unsupported protocol. LM_Get_Statistics_ on PIF name returns ifInUnknownProtos for SLSA. ifOutOctets 1.3.6.1.2.1.2.2.1.
PAGE 267
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.2.2.1.19 read-only Counter The number of outbound packets that were discarded even though no errors had been detected to prevent their being transmitted. LM_Get_Statistics_ on PIF name returns ifOutDiscards for SLSA. ifOutErrors 1.3.6.1.2.1.2.2.1.
PAGE 268
RFC Compliance TCP/IP Subagent RFC Compliance Table 8-6 summarizes compliance of Interfaces group support with RFC 1213. Table 8-6. Compliance With Interfaces Group Definitions in RFC 1213 Object Descriptor Complianc e Explanation ifNumber Yes See Table 8-5. ifIndex Yes See Table 8-5. ifDescr Yes See Table 8-5. ifType Partial See Table 8-5. ifMtu Partial See Table 8-5. ifSpeed Yes See Table 8-5. ifPhysAddress Partial See Table 8-5. ifAdminStatus Partial Constant value of up (1).
PAGE 269
ifTable Maintenance TCP/IP Subagent For each subnet found in response to an INFO SPI command for the SUBNET object, the TCP/IP Subagent extracts the subnet type and the associated I/O process name. Using this information, the TCP/IP Subagent sends the necessary INFO, STATUS, and STATISTICS SPI commands for the PORT object.
PAGE 270
IP Group TCP/IP Subagent IP Group The IP group contains information about the internet protocol (IP) layer of the TCP/IP subsystem being managed. The IP group consists of a collection of scalar objects and three tables: ipAddrTable, ipRouteTable, and ipNetToMediaTable.
PAGE 271
MIB Objects TCP/IP Subagent ipRouteTable (21) √ ipRouteEntry (1) √ ipRouteDest (1) √ ipRouteIfIndex (2) √ ipRouteMetric1 (3) √ ipRouteMetric2 (4) √ ipRouteMetric3 (5) √ ipRouteMetric4 (6) √ ipRouteNextHop (7) √ ipRouteType (8) √ ipRouteProto (9) √ ipRouteAge (10) ipRouteMask (11) √ ipRouteMetric5 (12) √ ipRouteInfo (13) √ ipNetToMediaTable (22) √ ipNetToMediaEntry (1) √ ipNetToMediaIfIndex (1) √ ipNetToMediaPhysAddress (2) √ ipNetToMediaNetAddress (3) √ ipNetToMediaType (4) √ ipRoutingDiscards (23) MIB O
PAGE 272
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.4.4 read-only Counter The number of input datagrams discarded because of errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, and errors discovered in processing their IP options.
PAGE 273
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.4.10 read-only Counter The total number of IP datagrams that local IP user protocols supplied to IP in requests for transmission. The value (integer) of the ZSTATS-IPOUT-PKTS field of the ZTCI-DDL-IPSTATS structure, returned from a SPI STATISTICS command on PROCESS ztsaTcpIpProcess.
PAGE 274
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.4.16 read-only Counter The number of failures detected by the IP reassembly algorithm.
PAGE 275
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.4.20.1.4 read-only INTEGER The value of the least significant bit in the IP broadcast address used for sending datagrams on the logical interface associated with the IP address of this entry. The constant value for this object is 1, as specified by RFC 1213.
PAGE 276
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.4.21.1.3 ipRouteMetric2 1.3.6.1.2.1.4.21.1.4 ipRouteMetric3 1.3.6.1.2.1.4.21.1.5 ipRouteMetric4 1.3.6.1.2.1.4.21.1.6 ipRouteMetric5 1.3.6.1.2.1.4.21.1.12 read-only INTEGER Primary and alternate routing metrics for this route. The constant value for these objects is -1 (not used). ipRouteNextHop 1.3.6.1.2.1.4.21.
PAGE 277
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.4.21.1.9 read-only INTEGER The routing mechanism by which this route was learned. The constant value for this object is 2 (configured through local network management). ipRouteMask 1.3.6.1.2.1.4.21.1.
PAGE 278
RFC Compliance TCP/IP Subagent Table 8-7. IP Group Objects Supported by TCP/IP Subagent (page 8 of 8) Object and Attributes Definition Format and Derivation of Value ipNetToMediaPhysAdd ress 1.3.6.1.2.1.4.22.1.2 read-only PhysAddress The mediadependent physical address. The value of this object is the same as the value of ifPhysAddress for the corresponding ifIndex. ipNetToMediaNetAddr ess 1.3.6.1.2.1.4.22.1.3 read-only IpAddress The IP address corresponding to the media-dependent physical address.
PAGE 279
RFC Compliance TCP/IP Subagent Table 8-8. Compliance With IP Group Definitions in RFC 1213 (page 2 of 3) Object Descriptor Complianc e ipOutDiscards Partial No corresponding HP instrumentation exists; 0 is returned. ipOutNoRoutes Yes See Table 8-7. ipReasmTimeout Partial No corresponding HP instrumentation exists; 0 is returned. ipReasmReqds Yes See Table 8-7. ipReasmOKs Yes See Table 8-7. ipReasmFails Yes See Table 8-7.
PAGE 280
ipAddrTable Maintenance TCP/IP Subagent Table 8-8. Compliance With IP Group Definitions in RFC 1213 (page 3 of 3) Object Descriptor Complianc e ipRouteMask Yes Set operation not supported; attempt returns noSuchName error. See Table 8-7 for description of retrievable information. ipRouteInfo Yes See Table 8-7. ipNetToMediaIfIndex Yes Set operation not supported; attempt returns noSuchName error. See Table 8-7 for description of retrievable information.
PAGE 281
ipNetToMediaTable Maintenance TCP/IP Subagent When the TCP/IP Subagent finds that a ROUTE object has been deleted or added, it removes or adds the corresponding ipRouteTable entry. ipNetToMediaTable Maintenance The TCP/IP Subagent builds entries by sending an INFO SPI command for the SUBNET object. For each subnet found, the TCP/IP Subagent extracts the subnet type and the associated I/O process name.
PAGE 282
MIB Objects TCP/IP Subagent icmpOutMsgs (14) √ icmpOutErrors (15) √ icmpOutDestUnreachs (16) √ icmpOutTimeExcds (17) √ icmpOutParmProbs (18) √ icmpOutSrcQuenchs (19) √ icmpOutRedirects (20) √ icmpOutEchos (21) √ icmpOutEchoReps (22) √ icmpOutTimestamps (23) √ icmpOutTimestampReps (24) √ icmpOutAddrMasks (25) icmpOutAddrMaskReps (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.
PAGE 283
MIB Objects TCP/IP Subagent Table 8-9. ICMP Group Objects Supported by TCP/IP Subagent (page 2 of 4) Object and Attributes Definition Derivation of Value icmpInTimeExcds 1.3.6.1.2.1.5.4 read-only Counter The number of ICMP time-exceeded messages received. Offset 13 in the ZSTATS-ICMP-INHIST array in the ZTCI-DDL-ICMPSTATS structure. icmpInParmProbs 1.3.6.1.2.1.5.5 read-only Counter The number of ICMP parameter-problem messages received.
PAGE 284
MIB Objects TCP/IP Subagent Table 8-9. ICMP Group Objects Supported by TCP/IP Subagent (page 3 of 4) Object and Attributes Definition Derivation of Value icmpOutErrors 1.3.6.1.2.1.5.15 read-only Counter The number of ICMP messages not sent because of problems discovered within ICMP (such as lack of buffers).
PAGE 285
RFC Compliance TCP/IP Subagent Table 8-9. ICMP Group Objects Supported by TCP/IP Subagent (page 4 of 4) Object and Attributes Definition Derivation of Value icmpOutEchoReps 1.3.6.1.2.1.5.22 read-only Counter The number of ICMP echo-reply messages sent. Offset 0 in the ZSTATS-ICMP-OUTHIST array in the ZTCI-DDL-ICMPSTATS structure. icmpOutTimestamps 1.3.6.1.2.1.5.23 read-only Counter The number of ICMP timestamp-request messages sent.
PAGE 286
TCP Group TCP/IP Subagent Table 8-10. Compliance With ICMP Group Definitions in RFC 1213 (page 2 of 2) Object Descriptor Complianc e Explanation icmpOutTimeExcds Yes See Table 8-9. icmpOutParmProbs Yes See Table 8-9. icmpOutSrcQuenchs Yes See Table 8-9. icmpOutRedirects Yes See Table 8-9. icmpOutEchos Yes See Table 8-9. icmpOutEchoReps Yes See Table 8-9. icmpOutTimestamps Yes See Table 8-9. icmpOutTimestampRep s Yes See Table 8-9.
PAGE 287
MIB Objects TCP/IP Subagent tcpRetransSegs (12) √ tcpConnTable (13) √ tcpConnEntry (1) √ tcpConnState (1) √ tcpConnLocalAddress (2) √ tcpConnLocalPort (3) √ tcpConnRemAddress (4) √ tcpConnRemPort (5) √ tcpInErrs (14) √ tcpOutRsts (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.
PAGE 288
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.6.9 read-only Gauge The number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT. The count of the connections having the following values: The total number of segments received, including those received in error.
PAGE 289
MIB Objects TCP/IP Subagent 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 1.3.6.1.2.1.6.13.1.1 read-only INTEGER The state of the TCP connection.
PAGE 290
RFC Compliance TCP/IP Subagent Table 8-11. TCP Group Objects Supported by TCP/IP Subagent (page 4 of 4) Object and Attributes Definition Format and Derivation of Value tcpConnRemAddress 1.3.6.1.2.1.6.13.1.4 read-only IpAddress The remote IP address for the TCP connection. The IP address in the ZNET-STATUSFORGN-ADDR field of the ZTCI-DDLSTATUS-PROTO structure, returned from a SPI STATUS command on PROCESS ztsaTcpIpProcess. tcpConnRemPort 1.3.6.1.2.1.6.13.1.
PAGE 291
tcpConnTable Maintenance TCP/IP Subagent Table 8-12. Compliance With TCP Group Definitions in RFC 1213 Object Descriptor Complianc e tcpConnState Partial See Table 8-11 for description of retrievable information. The MIB-II value 12 (delete TCB) is not supported in this implementation; attempts to set this object to any value return a badValue error. tcpConnLocalAddress Yes See Table 8-11. tcpConnLocalPort Yes See Table 8-11. tcpConnRemAddress Yes See Table 8-11.
PAGE 292
MIB Objects TCP/IP Subagent udpOutDatagrams (4) √ udpTable (5) √ udpEntry(1) √ udpLocalAddress (1) √ udpLocalPort (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 udpInDatagrams 1.3.6.1.2.1.7.1 read-only Counter The total number of UDP datagrams delivered to UDP users.
PAGE 293
RFC Compliance TCP/IP Subagent Table 8-13. UDP Group Objects Supported by TCP/IP Subagent (page 2 of 2) Object and Attributes Definition Format and Derivation of Value udpTable Objects: Contains entries describing UDP listener information. Refer to udpTable Maintenance on page 8-63 for information on how entries are created and updated. udpLocalAddress 1.3.6.1.2.1.7.5.1.1 read-only IpAddress The local IP address for the UDP listener.
PAGE 294
Traps Generated by the TCP/IP Subagent 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
EMS Support TCP/IP Subagent 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. 1002 SUBAGENT-UNAVAIL Object Unavailable The TCP/IP Subagent process is terminating for reasons other than an internal fault or invalid startup configuration.
PAGE 296
EMS Support TCP/IP Subagent 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. 1012 INTERNAL-FAULT Object Unavailable An internal program logic fault has been detected in the subagent.
PAGE 297
Data Definitions TCP/IP Subagent 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. 1039 LIFGETATTR-ERROR Transient Fault The LM_Get_Attributes_ function returned an error.
PAGE 298
Subsystem ID TCP/IP Subagent Subsystem ID The subsystem ID that the TCP/IP Subagent uses to identify itself as the source of event messages is: CONSTANT CONSTANT CONSTANT CONSTANT ZTSA-VAL-OWNER ZTSA-VAL-NUMBER ZTSA-VAL-VERSION ZTSA-VAL-EXTERNAL-SSID DEFINITION ZTSA-VAL-SSID 02 z-filler TYPE character 8 02 z-owner TYPE ZSPI-DDL-CHAR8 02 z-number TYPE ZSPI-DDL-INT 02 z-version TYPE ZSPI-DDL-UINT VERSION. END VALUE VALUE VALUE VALUE "TANDEM". 202. VERSION "D20". "TANDEM.202.D20". TACL SSID.
PAGE 299
Tokens in ZTSA Event Messages TCP/IP Subagent 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. Table 8-18. ZEMS Tokens in ZTSA Event Messages Token Contents ZEMS-TKN-CONTENT-STANDARD Type of standard event. ZEMS-TKN-CONTENT-USER Type of user-defined event.
PAGE 300
Event Message Descriptions TCP/IP Subagent 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. • Event message text.
PAGE 301
1001: ZTSA-EVT-SUBAGENT-AVAIL TCP/IP Subagent 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.” ztsaProcessName is the TCP/IP Subagent process name specified for the TCP/IP Subagent’s private ztsaProcessName MIB object.
PAGE 302
1002: ZTSA-EVT-SUBAGENT-UNAVAIL TCP/IP Subagent 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. Effect.
PAGE 303
1002: ZTSA-EVT-SUBAGENT-UNAVAIL TCP/IP Subagent 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
1002: ZTSA-EVT-SUBAGENT-UNAVAIL TCP/IP Subagent ZTSA-VAL-STATE-DISCONNECTED indicates the current state of the TCP/IP Subagent process. The DDL AS clause of this value (“disconnected,” defined in the preceding table) appears in the message text following “previous state.” ztsaProcessName is the name of the underlying process whose failure caused the TCP/IP Subagent process to go out of service.
PAGE 305
1003: ZTSA-EVT-AGENT-OBJ-AVAIL TCP/IP Subagent 1003: ZTSA-EVT-AGENT-OBJ-AVAIL Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZTSA-TKN-AGENT ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> <6> <7> ZTSA-TKN-AGENT ztsaAgentName ZTSA-EVT-AGENT-OBJ-AVAIL ZEMS-VAL-UNDERLYING-UP ZTSA-VAL-STATE-state ZTSA-VAL-STATE-CONNECTED ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number: <3>, reaso
PAGE 306
1003: ZTSA-EVT-AGENT-OBJ-AVAIL TCP/IP Subagent 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 ZEMS-TKN-STATE-PREVIOUS Associated Text (DDL AS Clause) and Meaning ZTSA-VAL-STATE-CONNECTED “connected” indicates a normal operational state.
PAGE 307
1004: ZTSA-EVT-AGENT-OBJ-UNAVAIL TCP/IP Subagent 1004: ZTSA-EVT-AGENT-OBJ-UNAVAIL Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZTSA-TKN-AGENT ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-UNDERLYING-OBJNAME ZEMS-TKN-SYMPTOM-STRING Value <1> <2> <3> <4> <5> <6> <7> <8> ZTSA-TKN-AGENT ztsaAgentName ZTSA-EVT-AGENT-OBJ-UNAVAIL ZEMS-VAL-UNDERLYING-FAILED ZTSA-VAL-STATE-state ZTSA-VAL-STATE-DISCONNECTED ztsaAgentName code-location/ internal-context-text <9>
PAGE 308
1004: ZTSA-EVT-AGENT-OBJ-UNAVAIL TCP/IP Subagent 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 ZEMS-TKN-STATE-PREVIOUS Associated Text (DDL AS Clause) and Meaning ZTSA-VAL-STATE-CONNECTED “connected” indicates a normal operational state.
PAGE 309
1005: ZTSA-EVT-BACKUP-OBJ-AVAIL TCP/IP Subagent 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.
PAGE 310
1005: ZTSA-EVT-BACKUP-OBJ-AVAIL TCP/IP Subagent 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 ZEMS-TKN-CHANGE-REASON Associated Text (DDL AS Clause) and Meaning ZEMS-VAL-UNDERLYING-UP “underlying-serv-up” indicates that the backup TCP/IP Subagent process is available because an underlying resource on which it depends has become available.
PAGE 311
1005: ZTSA-EVT-BACKUP-OBJ-AVAIL TCP/IP Subagent 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. Effect. TCP/IP Subagent configuration changes are now saved to the backup.
PAGE 312
1006: ZTSA-EVT-BACKUP-OBJ-UNAVAIL TCP/IP Subagent 1006: ZTSA-EVT-BACKUP-OBJ-UNAVAIL Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZTSA-TKN-BACKUP ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-SYMPTOM-STRING ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> <6> <7> ZTSA-TKN-BACKUP ztsaProcessName ZTSA-EVT-BACKUP-OBJ-UNAVAIL ZEMS-VAL-reason ZTSA-VAL-STATE-state ZTSA-VAL-STATE-DISCONNECTED code-location/ internal-context-text <8> ZEMS-VAL-NULL Conditional T
PAGE 313
1006: ZTSA-EVT-BACKUP-OBJ-UNAVAIL TCP/IP Subagent 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 ZEMS-TKN-CHANGE-REASON Associated Text (DDL AS Clause) and Meaning ZEMS-VAL-UNDERLYING-FAILED “underlying-serv-failed” indicates that an underlying service the backup TCP/IP Subagent process depends on has failed.
PAGE 314
1006: ZTSA-EVT-BACKUP-OBJ-UNAVAIL TCP/IP Subagent This information is displayed only if the value of the ZEMS-TKN-CHANGEREASON 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” always appears in the message text following “user content.” Cause.
PAGE 315
1007: ZTSA-EVT-EMSCOLL-OBJ-AVAIL TCP/IP Subagent 1007: ZTSA-EVT-EMSCOLL-OBJ-AVAIL Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZTSA-TKN-EMSCOLLECTOR ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> <6> <7> ZTSA-TKN-EMSCOLLECTOR ztsaEmsCollectorName ZTSA-EVT-EMSCOLL-OBJ-AVAIL ZEMS-VAL-reason ZTSA-VAL-STATE-state ZTSA-VAL-STATE-CONNECTED ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, even
PAGE 316
1007: ZTSA-EVT-EMSCOLL-OBJ-AVAIL TCP/IP Subagent 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” indicates a normal operational interface between the EMS collector and the subagent.
PAGE 317
1008: ZTSA-EVT-EMSCOLL-OBJ-UNAVAIL TCP/IP Subagent Sample Message 96-02-08 12:21:51 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001007 Object available emscollector-interface \NOVA.
PAGE 318
1008: ZTSA-EVT-EMSCOLL-OBJ-UNAVAIL TCP/IP Subagent 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 ZEMS-TKN-CHANGE-REASON Associated Text (DDL AS Clause) and Meaning ZEMS-VAL-UNDERLYING-FAILED “underlying-serv-failed” indicates that an underlying service the interface with the EMS collector process depends on has failed.
PAGE 319
1008: ZTSA-EVT-EMSCOLL-OBJ-UNAVAIL TCP/IP Subagent 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.” This information is displayed only if the value of the ZEMS-TKN-CHANGEREASON is ZEMS-VAL-UNDERLYING-FAILED.
PAGE 320
1009: ZTSA-EVT-TCPIP-OBJ-AVAIL TCP/IP Subagent 1009: ZTSA-EVT-TCPIP-OBJ-AVAIL Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZTSA-TKN-TCPIP ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> <6> <7> ZTSA-TKN-TCPIP ztsaTcpIpProcess ZTSA-EVT-TCPIP-OBJ-AVAIL ZEMS-VAL-reason ZTSA-VAL-STATE-state ZTSA-VAL-STATE-CONNECTED ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number: <3>, reason: <
PAGE 321
1009: ZTSA-EVT-TCPIP-OBJ-AVAIL TCP/IP Subagent 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 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.
PAGE 323
1010: ZTSA-EVT-TCPIP-OBJ-UNAVAIL TCP/IP Subagent 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-resourceunavailable”) appears in the message text following “event number.” ZEMS-VAL-reason indicates the reason the TCP/IP process has become unavailable.
PAGE 324
1010: ZTSA-EVT-TCPIP-OBJ-UNAVAIL TCP/IP Subagent 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.
PAGE 325
1011: ZTSA-EVT-OUT-OF-MEMORY TCP/IP Subagent 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. Sample Message 96-02-08 12:21:51 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001010 Object unavailable tcpip-resource \NOVA.
PAGE 326
1011: ZTSA-EVT-OUT-OF-MEMORY TCP/IP Subagent 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 Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZTSA-TKN-SUBAGENT ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-SYMPTOM-STRING ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> <6> <7> ZTSA-TKN-SUBAGENT ztsaProcessName ZTSA-EVT-INTERNAL-FAULT ZEMS-VAL-INTERNAL-FAILED ZTSA-VAL-STATE-state ZTSA-VAL-STATE-DISCONNECTED code-location/ internal-context-text <8> ZEMS-VAL-NULL Conditional
PAGE 328
1012: ZTSA-EVT-INTERNAL-FAULT TCP/IP Subagent 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 ZEMS-TKN-STATE-PREVIOUS Associated Text (DDL AS Clause) and Meaning ZTSA-VAL-STATE-CONNECTED “connected” indicates a subagent in a running state, having completed its startup initialization.
PAGE 329
1013: ZTSA-EVT-CONFIGURATION-INVALID TCP/IP Subagent Sample Message 96-02-08 11:49:38 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001012 Object unavailable TCP/IP-SNMPsubagent - \NOVA.
PAGE 330
1013: ZTSA-EVT-CONFIGURATION-INVALID TCP/IP Subagent 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 Sample Message 96-02-08 11:24:51 \NOVA.$ZTSA TANDEM.TCPIPSA.D20 001013 Object unavailable TCP/IP-SNMP-subagent \NOVA.
PAGE 332
1015: ZTSA-EVT-LANMON-OBJ-UNAVAIL TCP/IP Subagent Sample Message 96-02-08 11:31:35 \NOVA.$ZTSA TANDEM.TCPIPSA.
PAGE 333
1022: ZTSA-EVT-PIFGETSTATUS-ERROR TCP/IP Subagent 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.
PAGE 334
1022: ZTSA-EVT-PIFGETSTATUS-ERROR TCP/IP Subagent 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.” ZEMS-VAL-NULL indicates the type of subsystem-defined event.
PAGE 335
1023: ZTSA-EVT-PIFGETATTR-ERROR TCP/IP Subagent 1023: ZTSA-EVT-PIFGETATTR-ERROR Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZTSA-TKN-SUBAGENT ZEMS-TKN-EVENTNUMBER ZEMS-TKN-TXFAULT-TYPE ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> ZTSA-TKN-SUBAGENT ztsaProcessName ZTSA-EVT-PIFGETATTR-ERROR ZTSA-VAL-TF-PIFGETATTR 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
PAGE 336
1039: ZTSA-EVT-LIFGETATTR-ERROR TCP/IP Subagent 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. Generally, this condition is transient, and no corrective action is necessary.
PAGE 337
1039: ZTSA-EVT-LIFGETATTR-ERROR TCP/IP Subagent 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.” ZEMS-VAL-NULL indicates the type of subsystem-defined event.
PAGE 338
1041: ZTSA-EVT-PIFGETSTATS-ERROR TCP/IP Subagent 1041: ZTSA-EVT-PIFGETSTATS-ERROR Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZTSA-TKN-SUBAGENT ZEMS-TKN-EVENTNUMBER ZEMS-TKN-TXFAULT-TYPE ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> ZTSA-TKN-SUBAGENT ztsaProcessName ZTSA-EVT-PIFGETSTATS-ERROR ZTSA-VAL-TF-PIFGETSTATS 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
PAGE 339
Converting Events to Traps TCP/IP Subagent 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.
PAGE 340
TCP/IP Subagent Converting Events to Traps SNMP Configuration and Management Manual—424777-006 8 -110
PAGE 341
9 EMS Trap Subagent The EMS Trap Subagent translates Event Management Service (EMS) events into SNMP traps whose objects are defined in the EMS Trap MIB. This section describes the EMS Trap Subagent and its MIB. Architectural Overview EMS is a set of processes that collect event messages and then distribute them to various destinations, such as viewing consoles and printers.
PAGE 342
Architectural Overview EMS Trap Subagent Figure 9-1. EMS Components EMS Compaq Subsystems Alternate Collectors Log Files Filter Forwarding Distributor Customer Applications Primary Collector ($0) Compatibility Distributor ($Z0) Log File Filter Filter Consumer Distributor Template Printing Distributor Template Remote Collector Management Application Terminal Printer File Console VST801.
PAGE 343
RFC Compliance EMS Trap Subagent Figure 9-2. EMS Trap Subagent Components Compaq Subsystems Customer Applications Event Messages Primary or Alternate Collector Log File Filter Template Files ZSMPTMP ZSMPTMP ZSMPTMP ZSMPTMP LLL L EMS Trap Subagent SNMP Traps EM S SNMP Agent EMS Trap MIB Definition SNMP Manager Station VST802.vsd RFC Compliance The EMS Trap MIB complies with RFC 1215, A Convention for Defining Traps for Use with the SNMP.
PAGE 344
Installation EMS Trap Subagent 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. ZSMPTMPL: The TEMPL-compiled version of SSMPTMPL. EMS (D21 or later).
PAGE 345
Installation Steps EMS Trap Subagent 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 require -- editing: ----- Sun NetManager: comment out entire IMPORTS section; uncomment iso, dod, etc.
PAGE 346
Installation Steps EMS Trap Subagent Example 9-1. ASN.1 Source Code for EMS Trap MIB (page 2 of 3) --- items in each event -TrapSSIDtype TrapEventNumbertype TrapContentStandardtype TrapSubjecttype TrapProcesstype TrapGenerationtimetype TrapCriticaltype TrapTexttype ::= ::= ::= ::= ::= ::= ::= ::= DisplayString DisplayString DisplayString DisplayString DisplayString DisplayString DisplayString DisplayString (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (5..24)) (1..6)) (1..24)) (1..50)) (1..
PAGE 347
Installation Steps EMS Trap Subagent 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 ACCESS not-accessible STATUS mandatory DESCRIPTION " GMT the event was generated, rendered yyyy/mm/dd hh:mm:ss. Timestamp is GMT.
PAGE 348
Configuration EMS Trap Subagent Configuration Before using the EMS Trap Subagent, you need to create an event filter and might need to configure trap connections. This subsection describes these operations. Event Filter The EMS Trap Subagent uses an event filter known as a routing distributor filter to determine where to route trap messages. The filter contains a destination statement that identifies the SNMP agent as the routing destination.
PAGE 349
Trap Connections EMS Trap Subagent 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 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. agent-address The Internet address of the system on which the SNMP agent forwarding the trap is installed. generic-trap A 16-bit number set to 6 to signify that the trap is enterpriseSpecific.
PAGE 351
The Trap PDU EMS Trap Subagent Example 9-3.
PAGE 352
The EMS Trap MIB EMS Trap Subagent 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) ems (12) trapSSID (1) √ trapEventNumber (2) √ trapContentStandard (3) √ trapSubject (4) √ trapProcess (5) √ trapGenerationtime (6) √ trapCritical (7) √ trapText (8) √ Table 9-1 describes the objects in the EMS Trap MIB.
PAGE 353
The EMS Trap MIB EMS Trap Subagent Table 9-1. Objects in the EMS Trap MIB (page 1 of 4) Object and Attributes Definition Format of Value Derivation of Value trapSSID 1.3.6.1.4.1.169.3.12.1 not-accessible DisplayString (SIZE (5..24)) The identifier of the subsystem or application that generated the event. owner.ss.version, ZSPI-TKN-SSID token value. owner is the organization providing the software that generated the trap. For HP subsystems, the value is TANDEM. ss is the subsystem name or number.
PAGE 354
The EMS Trap MIB EMS Trap Subagent 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 whether the event is a standard event and, if so, what type of standard event. Programmers are encouraged to use standard events to improve the consistency among messages in certain categories and to promote system management automation.
PAGE 355
The EMS Trap MIB EMS Trap Subagent 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 software component most directly involved in the event. All values except floating-point values and values stored as structured tokens can be formatted. A question mark (?) appears when the value of the subject cannot be formatted. The value of the first event subject token.
PAGE 356
The EMS Trap MIB EMS Trap Subagent Table 9-1. Objects in the EMS Trap MIB (page 4 of 4) Object and Attributes Definition Format of Value Derivation of Value trapCritical 1.3.6.1.4.1.169.3.12.7 not-accessible DisplayString (SIZE (1..14)) An indication of whether the event is critical or noncritical.
PAGE 357
10 NonStop NET/MASTER Trap Subagent The NonStop NET/MASTER Trap Subagent translates Event Management Service (EMS) events routed to NonStop NET/MASTER MS into SNMP traps whose objects are defined in the EMS Trap MIB. It also gives you the ability to define your own trap objects, for use with an enterprise-specific trap MIB. This section describes the NonStop NET/MASTER Trap Subagent and its MIB.
PAGE 358
Architectural Overview NonStop NET/MASTER Trap Subagent Figure 10-1. EMS and NonStop NET/MASTER Components EMS Compaq Customer Applications Subsystems Primary Collector ($0) Alternate Collectors Log File Log Files Filter Consumer Distributor NonStopTM NET/MASTER MS LOGPROC EMSPROC or RMS Message Handler NCL Procedures MSGPROC Activity Log OCS Window VST901.
PAGE 359
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. If you are fluent in NCL and ASN.1, you can define your own trap MIB and then modify GENTRAP to correspond.
PAGE 360
Installation Steps NonStop NET/MASTER Trap Subagent Figure 10-2. NonStop NET/MASTER Trap Subagent Components EMS Compaq Subsystems Customer Applications Event Messages Primary Alternate Collectors Collector ($0) Log Files Log File Filter Consumer Distributor NonStopTM NET/MASTER MS EMSPROC or RMS Message Handler SNMP GENTRAP NMMTRAP Agent SNMP Traps NonStopTM NET/ MASTER Trap Subagent EMS Trap MIB Definition SNMP Manager Station VST902.
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. The distributed file will still be available, but NonStop NET/MASTER MS will execute your custom GENTRAP procedure. Next load the ASN.
PAGE 362
Installation Steps NonStop NET/MASTER Trap Subagent 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 require -- editing: ----- Sun NetManager: comment out entire IMPORTS section; uncomment iso, dod, etc.
PAGE 363
Installation Steps NonStop NET/MASTER Trap Subagent Example 10-1. ASN.1 Source Code for EMS Trap MIB (page 2 of 3) -- items in each event -TrapSSIDtype TrapEventNumbertype TrapContentStandardtype TrapSubjecttype TrapProcesstype TrapGenerationtimetype TrapCriticaltype TrapTexttype ::= ::= ::= ::= ::= ::= ::= ::= DisplayString DisplayString DisplayString DisplayString DisplayString DisplayString DisplayString DisplayString (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (SIZE (5..24)) (1..6)) (1..24)) (1..
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 ACCESS not-accessible STATUS mandatory DESCRIPTION " GMT the event was generated, rendered yyyy/mm/dd hh:mm:ss. Timestamp is GMT.
PAGE 365
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. Modifying GENTRAP When first installed, this file looks like Example 10-2.
PAGE 366
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 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. The agent is specified as &1 on the "NCL Proc Name" field of page 5 of RMS : System Action screen.
PAGE 367
Modifying GENTRAP NonStop NET/MASTER Trap Subagent 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 ; /* generating process */ &trap.value.5 = &$ems.tandem.spi.zems_tkn_zems_tkn_proc_desc; &trap.oid.6 = 1.3.6.1.4.1.169.3.12.
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. The sendtrap function assembles the trap and writes it to the SNMP agent.
PAGE 369
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. The closeagent function terminates communication with the SNMP agent. It closes an open instance created by openagent.
PAGE 370
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. generic-trap A 16-bit number set to 6 to signify that the trap is enterpriseSpecific. specific-trap A 16-bit number set to 0.
PAGE 371
The EMS Trap MIB NonStop NET/MASTER Trap Subagent Table 10-1. Objects in the EMS Trap MIB (page 1 of 4) Object and Attributes Definition Format of Value Derivation of Value trapSSID The identifier of the subsystem or application that generated the event. owner.ss.version, owner is the organization providing the software that generated the trap. For HP subsystems, the owner value is TANDEM. ZSPI-TKN-SSID token value. 1.3.6.1.4.1.169.3.12.1 not-accessible DisplayString (SIZE (5..
PAGE 372
The EMS Trap MIB NonStop NET/MASTER Trap Subagent 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 whether the event is a standard event and, if so, what type of standard event. Programmers are encouraged to use standard events to improve the consistency among messages in certain categories and to promote system management automation.
PAGE 373
The EMS Trap MIB NonStop NET/MASTER Trap Subagent 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 software component most directly involved in the event. All values except floatingpoint values and values stored as structured tokens can be formatted. A question mark (?) appears when the value of the subject cannot be formatted. The value of the first event subject token.
PAGE 374
Messages NonStop NET/MASTER Trap Subagent 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 whether the event is critical or noncritical. Critical events have consequences that might be severe, as when they indicate potential or actual loss of data, loss of a major subsystem function, loss of fault-tolerance capability, or loss of subsystem integrity.
PAGE 375
sendtrap Failures NonStop NET/MASTER Trap Subagent 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. &sysmsg is a text message.
PAGE 376
closeagent Failures NonStop NET/MASTER Trap Subagent &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. closeagent Failures Table 10-4 describes the actions GENTRAP takes when openagent fails. Table 10-4.
PAGE 377
11 Host Resources Subagent 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. This section describes the Host Resources Subagent and its MIB.
PAGE 378
Standard MIB Groups Host Resources Subagent As Figure 11-1 indicates, the subagent uses Guardian and Spooler procedure calls to obtain information for these MIB groups. Figure 11-1.
PAGE 379
MIB Extensions Host Resources Subagent 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) udp (7) egp (8) cmot (9) transmission (10) snmp (11) host (25) hrSystem (1) √ hrStorage (2) √ hrDevice (3) √ hrSWRun (4) √ hrSWRunPerf (5) √ hrSWInstalled (6) The subagent does not support the optional hrSWInstalled group.
PAGE 380
MIB Extensions Host Resources Subagent zhrmDevUnavail group This group describes hrDevice group devices that are in a state that may require operator attention. zhrmSaProcess group This group provides information on the subagent process.
PAGE 381
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) enterprises (1) tandem (169) nonstopsystems (3) zhrm (180) zhrmTableInfo (1) √ zhrmThreshold (2) √ zhrmDevUnavail (3) √ zhrmSaProcess (4) √ zhrmRefresh (5) √ zhrmTraps (7) √ Proactive Hardware Management You can configure the Host Resources
PAGE 382
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. These two timers also control the rate at which software data is refreshed. Whenever one of the timers runs down, values in the hrSWRun and hrSWRunPerf groups are refreshed.
PAGE 383
Host Resources Subagent Initiating Backup Process Takeover Initiating Backup Process Takeover The Host Resources Subagent can be run as a process pair to achieve a basic fault-tolerant level. The support includes a persistent subagent process and checkpointing of the startup parameters.
PAGE 384
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. The subagent generates EMS event messages when noteworthy situations arise.
PAGE 385
Host Resources Subagent • • • Installation Steps DSM Template Services (D21 or later) At least one SNMP manager that can send requests to the SNMP agent for processing by the Host Resources Subagent If the NonStop Kernel OSS environment is to be monitored, the OSS Monitor (OSSMON) must be running. Installation Steps Run the Distributed Systems Management /Software Configuration Manager (DSM/SCM) to install EMS, DSM Template Services, and the Host Resources Subagent.
PAGE 386
Configuration Host Resources Subagent 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
Configuration Host Resources Subagent Table 11-1. Host Resources Subagent Configuration Options (page 2 of 3) Subagent Attribute RUN Startup Parameter Hardware and software objects -e Software objects -w Settable MIB Object Name (Group Name) Default Behavior Values maintained for all devices and all processes except those associated with products listed under "Starting and Stopping the Subagent.” zhrmEnableSoftwareGroup (zhrmSaProcess group) hrSWRun and hrSWRunPerf group values are maintained.
PAGE 388
Starting and Stopping the Subagent Host Resources Subagent Table 11-1. Host Resources Subagent Configuration Options (page 3 of 3) Subagent Attribute RUN Startup Parameter Settable MIB Object Name (Group Name) Default Behavior NonStop Kernel personality to be monitored Guardian -t zhrmExamineGuardian (zhrmSaProcess group) Guardian file system and processes are monitored. OSS -u zhrmExamineOSS (zhrmSaProcess group) OSS file system and processes are monitored.
PAGE 389
Host Resources Subagent Starting and Stopping the Subagent Syntax of the startup options follows established UNIX conventions. [RUN] [[$volume.]subvolume.]HMSAX / NAME $subagent-process [,other-run-option]... / [ ? | startup-parameter [startup-parameter]...] volume identifies the volume on which HMSAX resides. You can omit it if HMSAX resides on your current subvolume. By default, the installation program used to put HMSAX into $SYSTEM. subvolume identifies the subvolume on which HMSAX resides.
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. If the primary process fails, the backup process automatically takes over.
PAGE 391
Starting and Stopping the Subagent Host Resources 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
Starting and Stopping the Subagent Host Resources Subagent DDL NetView SENTINEL TWORK EDIT OSIMAGE SPOOL VS EMSDIST PATHCOM SPOOLCOM YOUMAIL FILTER PERUSE SYMSERV FTP PERUSES P 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
Starting and Stopping the Subagent Host Resources Subagent device-name identifies a device: CPUnn identifies a CPU. $printer-name identifies a printer. $volume-name identifies a disk. $tape-drive-name identifies a tape drive. $network-devicename identifies a network device. 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.
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 trap generation. -n process-priority sets the initial process priority of the subagent.
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
Host Resources Subagent Troubleshooting the Subagent -w 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
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. Startup Problems If the subagent stops running shortly after startup, check the EMS event log for unusual conditions.
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. The -t and -u startup parameters can be used to exclude or include monitoring of the Guardian personality or the OSS personality of the SNMP Kernel.
PAGE 401
Host Resources Subagent hrSystem Group hrSystem Group The hrSystem group is a collection of scalar objects describing general attributes of the host.
PAGE 402
MIB Objects Host Resources Subagent Table 11-2. hrSystem Group Objects Supported by Host Resources Subagent's MIB (page 1 of 2) Format of Value Object and Attributes Definition Derivation of Value hrSystemUpTime 1.3.6.1.2.1.25.1.1 read-only TimeTicks Number of microseconds since system load. Integer without leading 0s. Guardian procedure JULIANTIMESTAMP. hrSystemDate 1.3.6.1.2.1.25.1.2 read-only DateAndTime Current Greenwich mean time.
PAGE 403
Sample Data Host Resources Subagent Table 11-2. hrSystem Group Objects Supported by Host Resources Subagent's MIB (page 2 of 2) Format of Value Object and Attributes Definition Derivation of Value hrSystemNumUsers 1.3.6.1.2.1.25.1.5 read-only Gauge Number of users running a command interpreter. Users logged in through a nonTACL process such as Pathway are not counted. Users running multiple TACLs are counted only once. Integer without leading 0s. Guardian procedure PROCESS_GETINFOLIST_.
PAGE 404
RFC Compliance Host Resources Subagent RFC Compliance Table 11-3. Compliance With hrSystem Group Definitions in RFC 1514 Object Descriptor Compliance Explanation hrSystemUpTime Yes See Table 11-2. hrSystemDate Partial Set operation not supported. hrSystemInitialLoadDevice Partial Set operation not supported. hrSystemInitialLoadParameter s Partial Set operation not supported. hrSystemNumUsers Yes See Table 11-2. hrSystemProcesses Yes See Table 11-2.
PAGE 405
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.
PAGE 406
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.2.2 read-only KBytes The total amount of physical memory in all CPUs. Integer without leading 0s. Guardian procedure PROCESSOR_ GETINFOLIST_ is called once for each CPU and the sum derived after pages are converted to kilobytes.
PAGE 407
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.2.3.1.3 read-only DisplayString Description of the type of storage represented by the entry. For RAM: the number and type of a processor: CPUnn (processortype).running Dnn.nn For disks and file system entries: the name and type of the disk: $volume(disktype).
PAGE 408
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.2.3.1.5 read-only INTEGER (1..2147483647) The capacity of the entry, in number of allocation units. Integer without leading 0s. For physical memory: if the number exceeds 2,147,483,647, the value returned is -1D. For disks: the number describes the pages formatted.
PAGE 409
Sample Data Host Resources Subagent 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, 4096, 8192, 8169, 3791 05/22/95 10:33:45, 4096, 8192, 6982, 1951 05/22/95 10:33:45, 0 05/22/95 10:33:45, 0 05/22/95 10:33:45, 311818, 0 05/22/95 10:33:45, 145449, 0 05/22/95 10:33:45, 316470, 275811, 0 05/22/95 10:33:45, 316470, 225707, 0 05/22/95 10:33:45, 9766
PAGE 410
RFC Compliance Host Resources Subagent 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 Yes See Table 11-4. hrStorageIndex Yes See Table 11-4. hrStorageType Yes See Table 11-4. hrStorageDescr Yes See Table 11-4. hrStorageAllocationUnits Yes See Table 11-4. hrStorageSize Partial Set operation is not supported.
PAGE 411
Host Resources Subagent hrDevice Group hrStorage group MIB values are initialized at startup time and then refreshed at a frequency controlled by the -s and -d startup parameters: -s hrStorageIndex hrStorageType hrStorageDescr hrStorageAllocationUnits -d hrMemorySize hrStorageSize hrStorageUsed hrStorageAllocationFailures The values of these objects can be refreshed on demand from an SNMP manager after the subagent is running.
PAGE 412
hrDevice Group Host Resources Subagent 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
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
hrDevice Group Host Resources Subagent Figure 11-4.
PAGE 415
MIB Objects Host Resources Subagent 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 hrDeviceTable Objects: Entries describing and pointing to other entries for devices associated with the system. Entries maintained are controlled by the -e startup parameter. hrDeviceIndex 1.3.6.1.2.1.25.3.2.1.1 read-only INTEGER (1..
PAGE 416
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.3.2.1.3 read-only DisplayString (SIZE (0..64)) Description of the type of device represented by the entry. CPUs: CPUnn (CPU--type). Printers: collector name of form $printer-id. Spooler collectors, used as pseudo printers, have name form [\node-name]$collectorprocess- name [.
PAGE 417
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.3.2.1.5 read-only INTEGER { unknown(1), running(2), warning(3), testing(4), down(5) } The current state of the device represented by the entry. One of the following values: unknown running warning testing down For CPUs: Guardian procedure PROCESSORSTATUS.
PAGE 418
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.3.3.1.2 read-only INTEGER (0..100) The average percent of time a processor was not idle during the last minute. Integer without leading 0s.
PAGE 419
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.3.5.1.1 read-only INTEGER { other(1), unknown(2), idle(3), printing(4), warmup(5) } The current state of the printer represented by the entry.
PAGE 420
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.3.6.1.2 read-only INTEGER { other(1), unknown(2), hardDisk(3), floppyDisk(4), opticalDiskROM(5), opticalDiskWORM(6), opticalDiskRW(7), amDisk(8) } A characterization of the type of disk represented by the entry.
PAGE 421
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.3.7.1.2 read-only The name of the disk. For Guardian: $volume Guardian procedure FILE_ GETINFOLISTBYNAME_. For OSS: $disk-fileset . InternationalDisplayString (SIZE (0..128)) hrPartitionID 1.3.6.1.2.1.25.3.7.1.3 read-only DisplayString Partition identifier.
PAGE 422
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.3.8.1.3 read-only Name of the system. \system name hrFSType 1.3.6.1.2.1.25.3.8.1.4 read-only OBJECT IDENTIFIER An object identifier from RFC 1514 identifying the type of file system represented by the entry. 1.3.6.1.2.1.25.3.9.1 (hrFSOther) RFC 1514. hrFSAccess 1.3.
PAGE 423
Sample Data Host Resources Subagent 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 1.3.6.1.2.1.25.3.8.1.7 read-only INTEGER (1..2147483647) An index that has a corresponding value in the hrStorageTable (hrStorageIndex). Integer without leading 0s. Computed by Host Resources Subagent. hrFSLastFullBackup Date 1.3.6.1.2.1.25.3.8.1.
PAGE 424
Sample Data Host Resources Subagent 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 05/22/95 05/22/95 05/22/95 10:36:03, 10:36:03, 10:36:03, 10:36:03, 1.3.6.1.4.1.169.3.180, 1.3.6.1.4.1.169.3.180, 1.3.6.1.4.1.169.3.180, 1.3.6.1.4.1.169.3.
PAGE 425
RFC Compliance Host Resources Subagent 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 Yes See Table 11-6. hrDeviceType Yes See Table 11-6. hrDeviceDescr Yes See Table 11-6. hrDeviceID Yes See Table 11-6. hrDeviceStatus Yes See Table 11-6. hrDeviceErrors Yes See Table 11-6.
PAGE 426
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 interfaces The subagent accesses the network interface file to build hrNetworkTable entries.
PAGE 427
hrDevice Group Maintenance Host Resources Subagent 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 interfaces up 2 (running) down 5 (down) up 2 (running) down 5 (down) special 4 (testing) mount 4 (testing) revive 3 (warning) exercise 4 (testing) exclusive 4 (testing) harddown 5 (down) waiting 2 (running) busy 2 (running) s
PAGE 428
Host Resources Subagent -s hrDeviceIndex hrDeviceType hrDeviceDescr hrDeviceID hrProcessorFrwID hrNetworkIfIndex hrDiskStorageAccess hrDiskStorageMedia hrDiskStorageRemoveble hrPartitionIndex hrPartitionLabel hrPartitionID hrPartitionFSIndex hrFSIndex hrFSMountPoint hrFSRemoteMountPoint hrFSType hrFSAccess hrFSBootable hrFSStorageIndex hrFSLastFullBackupDate hrFSLastPartialBackupDate -d hrDeviceStatus hrPrinterStatus hrPrinterDetectedErrorState hrDeviceErrors hrProcessorLoad hrDiskStorageCapacity hrPart
PAGE 429
hrSWRun Group Host Resources Subagent 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.
PAGE 430
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.4.1 read-only INTEGER (1..2147483647) An index value that points to the hrSWRunTable entry for the operating system associated with lowest numbered CPU on the system.
PAGE 431
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.4.2.1.2 read-only InternationalDisplayString (SIZE (0..64)) The unqualified name of the program file whose process the entry represents. For non-operating system processes: unqualified file name.
PAGE 432
MIB Objects Host Resources Subagent 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 1.3.6.1.2.1.25.4.2.1.5 read-only InternationalDisplayString (SIZE (0..128)) Information describing the process.
PAGE 433
Sample Data Host Resources Subagent 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 1.3.6.1.2.1.25.4.2.1.7 read-only INTEGER { running(1), runnable(2), notRunnable(3), invalid(4) } The state of the process.
PAGE 434
RFC Compliance Host Resources Subagent $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.
PAGE 435
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. Set zhrmEnableSoftwareGroup to 0 to disable maintenance of hrSWRunGroup objects. Set it to 1 to enable object maintenance.
PAGE 436
Sample Data Host Resources Subagent Table 11-10. hrSWRunPerf Group Objects Supported by Host Resources Subagent's MIB Object and Attributes Definition Format of Value Derivation of Value hrSWRunPerfTable Objects: Entries providing performance metrics for resources having entries in the hrSWRun group. hrSWRunPerfCPU The number of centiseconds of the total system's CPU resources consumed by the process described by this entry. For operating system entries, the CPU busy time.
PAGE 437
RFC Compliance Host Resources Subagent 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 Yes See 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 Host Resources Subagent zhrmTableInfo Group This group, defined by HP, provides information about the status of operations performed on tables in the hrStorage and hrDevice groups.
PAGE 439
zhrmTableInfo Group Host Resources Subagent 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) √ zhrmInfNetLastStableRefre
PAGE 440
MIB Objects Host Resources Subagent 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.
PAGE 441
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.1.1.5 read-only DisplayString The system time at which hrStorageTable values controlled by the -s startup parameter or the zhrmStableRefresh Now object were last refreshed. month DD, YYYY HH:MM:SS Guardian procedure JULIANTIMESTAMP.
PAGE 442
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.1.2.2 read-only INTEGER (1..65535) The lowest value of hrDeviceIndex. Integer without leading 0s. hrDeviceTable. zhrmInfDevLastIndex 1.3.6.1.4.1.169.3.180.1.2.3 read-only INTEGER (1..65535) The highest value of hrDeviceIndex. Integer without leading 0s.
PAGE 443
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.1.2.8 read-only Counter The number of Set operations performed on hrDeviceTable objects since the subagent was last started. Integer without leading 0s. Computed by Host Resources Subagent.
PAGE 444
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.1.3.6 read-only Counter The number of Get operations performed on hrProcessorTable objects since the subagent was last started. Integer without leading 0s. Computed by Host Resources Subagent. zhrmInfCpuGetNextCounter 1.3.6.1.4.1.169.3.180.1.3.
PAGE 445
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.1.4.4 read-only DisplayString The system time at which hrNetworkTable values controlled by the -d startup parameter or the zhrmDynamRefresh Now object were last refreshed. month DD, YYYY HH:MM:SS Guardian procedure JULIANTIMESTAMP.
PAGE 446
MIB Objects Host Resources Subagent 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: Objects describing the status and usage of the hrPrinterTable. zhrmInfPrnEntries 1.3.6.1.4.1.169.3.180.1.5.1 read-only Gauge The current number of entries in the hrPrinterTable. Integer without leading 0s. Computed by Host Resources Subagent.
PAGE 447
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.1.5.6 read-only Counter The number of Get operations performed on hrPrinterTable objects since the subagent was last started. Integer without leading 0s. Computed by Host Resources Subagent. zhrmInfPrnGetNextCounter 1.3.6.1.4.1.169.3.180.1.5.
PAGE 448
MIB Objects Host Resources Subagent 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 which hrDiskStorageTable values controlled by the -d startup parameter or the zhrmDynamRefresh Now object were last refreshed. month DD, YYYY HH:MM:SS Guardian procedure JULIANTIMESTAMP. zhrmInfDiskLastStableRefresh 1.3.6.1.4.1.169.3.180.1.6.
PAGE 449
MIB Objects Host Resources Subagent Table 11-12. zhrmTableInfo Group Objects Supported by Host Resources Subagent's MIB (page 10 of 12) Object and Attributes Definition zhrmInfPartTable Group Objects: Objects describing the status and usage of the hrPartitionTable. zhrmInfPartEntries 1.3.6.1.4.1.169.3.180.1.7.1 read-only Gauge The current number of entries in the hrPartitionTable. Integer without leading 0s. Computed by Host Resources Subagent. zhrmInfPartFirstIndex 1.3.6.1.4.1.169.3.180.1.7.
PAGE 450
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.1.7.6 read-only Counter The number of Get operations performed on hrPartitionTable objects since the subagent was last started. Integer without leading 0s. Computed by Host Resources Subagent. zhrmInfPartGetNextCounter 1.3.6.1.4.1.169.3.180.1.7.
PAGE 451
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.1.8.4 read-only DisplayString The system time at which hrFSTable values controlled by the -d startup parameter or the zhrmDynamRefresh Now object were last refreshed. month DD, YYYY HH:MM:SS Guardian procedure JULIANTIMESTAMP.
PAGE 452
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
PAGE 453
Host Resources Subagent zhrmTableInfo Group Maintenance zhrmTableInfo Group Maintenance Most zhrmTableInfo group values are derived from hrStorage group and hrDevice group values as Table 11-12 describes. Values in the zhrmTableInfo group are refreshed immediately after hrStorage group and hrDevice group values are refreshed. Refer to hrStorage Group Maintenance on page 11-34 and hrDevice Group Maintenance on page 11-50 for information about when hrStorage group and hrDevice group values are refreshed.
PAGE 454
MIB Objects Host Resources Subagent 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. Table 11-13.
PAGE 455
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.2.1.
PAGE 456
MIB Objects Host Resources Subagent Table 11-13. zhrmThreshold Group Objects Supported by Host Resources Subagent's MIB (page 3 of 6) Object and Attributes Definition zhrmThrRAMTable Objects Entries describing RAM in the hrStorageTable whose usage has reached or exceeded the value of zhrmThrRAMHigh Value. zhrmThrRAMIndex An index value having a corresponding value (hrFSStorageIndex) in the hrFSTable. Integer, numbered sequentially starting at 1. The value of hrStorageIndex for the device.
PAGE 457
MIB Objects Host Resources Subagent 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 requests for storage by the entry that could not be honored because of insufficient space. Integer without leading 0s, indicating the number of pagefault interrupts since the processor was loaded. The value of hrStorageAllocation Failuresfor the device. 1.
PAGE 458
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.2.2.
PAGE 459
MIB Objects Host Resources Subagent Table 11-13. zhrmThreshold Group Objects Supported by Host Resources Subagent's MIB (page 6 of 6) Object and Attributes Definition zhrmThrDiskTable Objects Entries describing writable disks in the hrStorageTable whose usage has reached or exceeded the value of zhrmThrDiskHigh Value. zhrmThrDiskIndex An index value having a corresponding value (hrFSStorageIndex) in the hrFSTable. Integer, numbered sequentially starting at 1.
PAGE 460
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, 45 Time, zhrmThrRAMIndex, zhrmThrRAMDescr, zhrmThrRAMAllocationUnits, zhrmThrRAMSize, zhrmThrRAMUsed, zhrmThrRAMAllocationFailures 05/22/95 10:20:10, 1, CPU00 (NSR-L) running D20.
PAGE 461
Host Resources Subagent zhrmDevUnavail 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. The zhrmDevUnavail group consists of several scalar objects and one table (the zhrmDevUnTable).
PAGE 462
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.3.1 read-only DisplayString The current system time. month DD, YYYY HH:MM:SS Guardian procedure JULIANTIMESTAMP. zhrmDevUnUp 1.3.6.1.4.1.169.3.180.3.2 read-only Gauge The total number of devices for which the value of hrDeviceStatus is 2 (running).
PAGE 463
MIB Objects Host Resources Subagent 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 point to entries in the hrProcessorTable, the hrPrinterTable, the hrDiskStorageTable, the hrNetworkTable, and the hrPartitionTable. Integers running sequentially from 1. The value of hrDeviceIndex for qualifying devices.
PAGE 464
MIB Objects Host Resources Subagent 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 type of device represented by the entry. For CPUs: the number and type: CPUnn (processortype). For printers: name of a printer/spooler collector. Printers have name form $printer-id.
PAGE 465
MIB Objects Host Resources Subagent 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 characterizing the entry as a particular device type and subtype. The root of the identifier is the same for all entries: 1.3.6.1.4.1.169.3.180. The value of hrDeviceID for qualifying devices. The current state of the device represented by the entry.
PAGE 466
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.
PAGE 467
Host Resources Subagent zhrmSaProcess 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. One of the objects in this group lets you enable or disable creation and maintenance of hrSWRun and hrSWRunPerf groups.
PAGE 468
MIB Objects Host Resources Subagent Table 11-15. zhrmSaProcess Group Objects Supported by Host Resources Subagent's MIB (page 1 of 3) Object and Attributes Definition Format of Value Derivation of Value zhrmSaProcCurrTime 1.3.6.1.4.1.169.3.180.4.1 read-only DisplayString The current system time. month DD, YYYY HH:MM:SS Guardian procedure JULIANTIMESTAMP. zhrmSaProcVersion 1.3.6.1.4.1.169.3.180.4.2 read-only DisplayString The version of the Host Resources Subagent.
PAGE 469
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.4.9 read-only DisplayString The name of the terminal from which the subagent was started. \node.$device-name. #subdevice-name Guardian procedure PROCESS_GETINFO_. zhrmSaIniFile The name of the subagent’s initialization file. \node.$volume. subvolume.
PAGE 470
Sample Data Host Resources Subagent 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 suppresses maintenance of hrSWRun and hrSWRunPerf group objects when set to 0. One of these values is displayed: swValuesDisabled swValuesEnabled At startup, the subagent sets this value to 1 (swValuesEnabled) unless the -w startup parameter is used.
PAGE 471
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
Host Resources Subagent zhrmRefresh 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.
PAGE 473
MIB Objects Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.5.1 read-only DisplayString The current system time. month DD, YYYY HH:MM:SS Guardian procedure JULIANTIMESTAMP. zhrmDynamRefreshInterval 1.3.6.1.4.1.169.3.180.5.
PAGE 474
Sample Data Host Resources Subagent 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 1.3.6.1.4.1.169.3.180.5.7 read-only Counter The number of times since the subagent was started that MIB values controlled by the -s startup parameter or the zhrmStableRefresh Now object were refreshed. Integer without leading 0s. Computed by Host Resources Subagent.
PAGE 475
Traps Host Resources Subagent 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. This trap identifies a CPU whose RAM storage area is experiencing critically high usage. zhrmDiskThreshold.
PAGE 476
Routing Traps Host Resources Subagent 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 on 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 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. Figure 11-6.
PAGE 478
zhrmTrapDeviceStateChange Trap Host Resources Subagent 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 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 Refer to Thresholds and Traps on page 11-100 for an explanatio
PAGE 480
EMS Support Host Resources Subagent Table 11-19. Variable Bindings in the zhrmDiskThreshold Trap Object and Attributes Definition Format of Value Derivation of Value zhrmTrapStorageThrIndex 1.3.6.1.4.1.169.3.180.7.4 not-accessible INTEGER (1..2147483647) Index value that points to the entry in the hrStorageTable for the device that the trap describes. Integer, numbered sequentially starting at 1. The value of zhrmThrDiskIndex for the device. zhrmTrapStorageDescr 1.3.6.1.4.1.169.3.180.7.
PAGE 481
Data Definitions Host Resources Subagent 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.
PAGE 482
Tokens in ZHRM Event Messages Host Resources Subagent 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. Table 11-21.
PAGE 483
Event Message Descriptions Host Resources Subagent Table 11-23.
PAGE 484
001: ZHRM-EVT-HRM-SA-TERMINATED Host Resources Subagent • 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. 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. • • • • • Descriptions of listed tokens or values.
PAGE 485
002: ZHRM-EVT-HRM-SA-STARTED Host Resources Subagent ZHRM-VAL-CR-reason is one of the following causes.
PAGE 486
002: ZHRM-EVT-HRM-SA-STARTED Host Resources Subagent 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 The Host Resources Subagent process encountered an I/O error.
PAGE 488
003: ZHRM-EVT-HRM-SA-IO-ERR Host Resources Subagent 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. ZHRM-TKN-FILE-NAME contains the name of the file with which the subagent experienced an I/O error. This token is of type ZSPI-TYP-STRING.
PAGE 489
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.
PAGE 490
005: ZHRM-EVT-HRM-SA-PROG-ERR Host Resources Subagent 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, fault type: Memory full 005: ZHRM-EVT-HRM-SA-PROG-ERR The Host Resources Subagent process experienced an internal or logic error.
PAGE 491
Related Operating System Event Messages Host Resources Subagent 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. Recovery.
PAGE 492
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
12 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
Trap-to-Event Conversion Trap Multiplexer Subagent/Manager 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 on page 12-21. Figure 12-1.
PAGE 495
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.
PAGE 496
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
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. Refer to subsequent subsections for each MIB group for information on settable MIB objects. Table 12-1.
PAGE 498
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 Section 2, Installing and Configuring the SNMP Agent.
PAGE 499
Trap Multiplexer Subagent/Manager Starting and Stopping the Trap Multiplexer trap-multiplexer-process identifies the Trap Multiplexer process. You can specify from one through five alphanumeric characters, but the first character must be alphabetic. other-run-option is any of the 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. You can change the Trap Multiplexer process priority after it is started by setting the value of ztmxProcPri in the ztmxProcess group.
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. -o causes the Trap Multiplexer to write a formatted trace of its activities to the terminal or to a Spooler destination.
PAGE 502
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 ] ...
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 PARAM ZSMP^TCPIP^NAME $ZTC1 PARAM ZSMP^TCPIP^ADDR 192.168.
PAGE 504
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.
PAGE 505
Trap Multiplexer Subagent/Manager MIB Objects Table 12-2. ztmxPDUStatistics Group Objects Supported by Trap Multiplexer’s MIB (page 1 of 3) Object and Attributes Definition Format of Value ztmxUdpStatsCurrTime 1.3.6.1.4.1.169.3.185.1.1 read-only DisplayString The system time when a Get operation is performed for this object. month DD, YYYY HH:MM:SS Guardian procedure JULIANTIMESTAMP. ztmxUdpInDatagrams 1.3.6.1.4.1.169.3.185.1.
PAGE 506
Trap Multiplexer Subagent/Manager MIB Objects Table 12-2. ztmxPDUStatistics Group Objects Supported by Trap Multiplexer’s MIB (page 2 of 3) Object and Attributes Definition Format of Value Derivation of Value ztmxTrapStatsCurrTime 1.3.6.1.4.1.169.3.185.1.9.1 read-only DisplayString The system time when a Get operation is performed for this object. month DD, YYYY HH:MM:SS Guardian procedure JULIANTIMESTAMP. ztmxInColdStartTraps 1.3.6.1.4.1.169.3.185.1.19.
PAGE 507
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 Value Derivation of Value The total number of authenticationFailure traps received by the Trap Multiplexer. These standard SNMP traps signify that the sending entity has received a request that failed authentication. Integer without leading 0s. Trap Multiplexer.
PAGE 508
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.
PAGE 509
Trap Multiplexer Subagent/Manager MIB Objects Table 12-3. ztmxProcess Group Objects Supported by Trap Multiplexer’s MIB (page 1 of 4) Object and Attributes Definition Format of Value Derivation of Value ztmxProcCurrTime 1.3.6.1.4.1.169.3.185.2.1 read-only DisplayString The current system time. month DD, YYYY HH:MM:SS Guardian procedure JULIANTIMESTAMP. ztmxProcVersion 1.3.6.1.4.1.169.3.185.2.2 read-only DisplayString The version of the Trap Multiplexer.
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 1.3.6.1.4.1.169.3.185.2.9 read-write INTEGER The priority of the Trap Multiplexer primary and backup processes. Integer without leading 0s. Initially, the value of the -n startup parameter (145 or a user-specified value). After startup, the value can be set from an SNMP manager.
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 us The status of the session between the Trap Multiplexer and the SNMP agent. A value of close indicates that the Trap Multiplexer is not communicating with the SNMP agent. One of these values is displayed: open close Trap Multiplexer.
PAGE 512
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 of attempts to write an event message converted from a trap to the EMS collector. Integer without leading 0s. Trap Multiplexer. The total number of write operations to the EMS collector that could not be completed.
PAGE 513
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. After takeover is complete, the Trap Multiplexer sets the value of ztmxSwitchToBackupNow to 0.
PAGE 514
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; for example: ZSPI-TKN-DATALIST ZTMX-TKN-TRAP-VARBIND-COUNT ZSPI-TKN-DATALIST ZTMX-TKN-TRAP-VARBIND-OID ZTMX-TKN-TRAP-VARBIND-DATATYPE value-of-variable-binding ZSPI-TKN-ENDLIST . . .
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.
PAGE 516
Trap Multiplexer Subagent/Manager Event Summary Table 12-5.
PAGE 517
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.
PAGE 518
Trap Multiplexer Subagent/Manager Subsystem ID Subsystem ID CONSTANT ZTMX-VAL-VERSION CONSTANT ZSPI-SSN-ZTMX VALUE VALUE VERSION "D20". 185. DEFINITION ZTMX-VAL-SSID 02 z-filler TYPE character 8 02 z-owner TYPE ZSPI-DDL-CHAR8 02 z-number TYPE ZSPI-DDL-INT 02 z-version TYPE ZSPI-DDL-UINT VERSION. END TACL SSID. VALUE IS ZSPI-VAL-TANDEM. REDEFINES z-filler. VALUE IS ZSPI-SSN-ZTMX.
PAGE 519
Trap Multiplexer Subagent/Manager Tokens in ZTMX Event Messages Table 12-7.
PAGE 520
Trap Multiplexer Subagent/Manager Trap Event Message Descriptions Table 12-9.
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. shows where text appears that is derived from a token in the token list.
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. In the message text, it follows the string “varbind n OID=”, where n is a number identifying the varbind.
PAGE 524
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=”. 000: ZTMX-EVT-TRAP-COLDSTART The Trap Multiplexer received a coldStart trap.
PAGE 525
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.
PAGE 526
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.
PAGE 527
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
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
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
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
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.
PAGE 532
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.
PAGE 533
Trap Multiplexer Subagent/Manager 101: ZTMX-EVT-TMX-TERMINATED ZTMX-VAL-CR-reason is one of the causes following below.
PAGE 534
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.
PAGE 535
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. The process is ready for service. Recovery. Informational message only; no corrective action is needed. Sample Message 96-07-26 11:34:51 \COMM.
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.
PAGE 537
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
Trap Multiplexer Subagent/Manager 105: ZTMX-EVT-TMX--PROG-ERR Recovery. Try using another disk as a swap device.
PAGE 539
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. If recovery is successful, an event announcing the takeover is generated.
PAGE 540
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. which uses an event filter know as a routing distributor filter to determine where to route trap messages.
PAGE 541
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.
PAGE 542
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. If you do not specify a collector name, the primary EMS collector ($0) on your current system is assumed.
PAGE 543
Trap Multiplexer Subagent/Manager Application Control Flow Example 12-2. Sample Application Output Waiting for the next Event..... VersionNumber Community Enterprise Network Address Generic trap No Specific Trap No Timeticks Varbind Count : : : : : : : : 0 public 1.3.6.1.4.1.169.3 130.252.12.3 6 5 54321 4 Varbind OID : Type : Value : #1 1.2.3 OPAQUE 1@234&5*67 Varbind OID : Type : Value : #2 1.3.2.85.6 OCTETSTRING Tandem Computers Varbind OID : Type : Value : #3 1.3.2.208.
PAGE 544
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.
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(). 7. The function named spi_cmd_load_filter() builds SPI commands to identify the EMS filter to use and then calls send_spi_cmd(). 8.
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. 14. The SPI command is processed by calling send_spi_cmd(). 15. The EMS event information is extracted from spi_buf and stored in event_buf for token parsing. 16.
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 ZTMXTKN-TRAP-VARBIND-DATATYPE has a value of ZTMX_TNM_SMI_INTEGER, the token named ZTMX_TKN_SMI_INTEGER is accessed. 34. The main block initiates communication with an EMS consumer distributor and then calls getevent_loop() to process trap events. 35.
PAGE 548
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" and "-f" respectively. By default, the program assumes $0 as the collector and tmxfo in the current subvolme as the filter.
PAGE 549
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 550
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 551
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 552
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 553
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 554
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 555
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 556
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 557
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 558
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 559
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
PAGE 560
Trap Multiplexer Subagent/Manager Application Source Code Example 12-3.
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 */ proc_len, /* length */ &distr); /* file number */ <-- 43 if (ccval) { printf ("FILE_OPEN_ returned %d\n", ccval); exit (1); } /* Add "TYPE CONSUMER" to startup msg to send to EMSDIST */ strcat (ci_startup.
PAGE 562
Trap Multiplexer Subagent/Manager SNMP Configuration and Management Manual—424777-006 12-70 Application Source Code
PAGE 563
13 IPX/SPX Subagent (G-Series) The IPX/SPX Subagent facilitates the management of NonStop IPX/SPX processes known as IPX/SPX Protocol (IPXPROTO) processes. NonStop IPX/SPX is an HP software product that provides access to NonStop Kernel systems over an Ethernet or Token Ring LAN using Novell’s NetWare protocol suite: Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX).
PAGE 564
IPX/SPX Subagent (G-Series) Architectural Overview Figure 13-1. NonStop IPX/SPX Interactions NonStopTM IPX/SPX SCP IPXMG R IPXPROT O Processes SCF TLAM (D-series) SLSA (G-series) LAN 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
IPX/SPX Subagent (G-Series) Architectural Overview Figure 13-2. IPX/SPX Subagent Interactions NonStopTM IPX/SPX SCP EM S Collector IPXMG R IPXPROT O Processes SCF IPX/SPX Subagent TLAM (D-series) or SLSA (G-series) SNMP Agents TCP/IP NonStopTM Manager LAN Legend IPX and SCF Messages SNMP Messages Telnet Workstation Manager Station VST142.
PAGE 566
IPX/SPX Subagent (G-Series) The IPX/SPX Subagent MIB The IPX/SPX Subagent MIB The subagent MIB contains objects that characterize IPXPROTO processes as well as objects that characterize the subagent process: iso (1) org (3) dod (6) internet (1) private (4) enterprises (1) novell (23) mibDoc (2) ipx (5) ipxSystem (1) <−− IPXPROTO process objects tandem (169) nonstopsystems (3) zipx (164) <−− IPXPROTO process objects tdmNwInfo (1) tdmNwIPX (2) tdmNwSPX (3) tdmNwNCP (4) tdmNwServer (5) zisa (196) <−− IPX/SPX
PAGE 567
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
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
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.
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. After startup, you use tdmNwSaConfig group objects to control the EMS collector connection.
PAGE 571
IPX/SPX Subagent (G-Series) Resource Utilization subagentkeepalive The subagent successfully connected to a previously 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. invalidprocessname An invalid process name was specified at startup.
PAGE 572
IPX/SPX Subagent (G-Series) Subagent Backup Process Subagent Backup Process The IPX/SPX Subagent can run as a process pair. At startup, you can use the -b startup parameter to start a backup process in the CPU you specify. You can also use the tdmNwSaBackupCPU object to enable or disable the existence of a backup process. If the primary subagent process fails, the backup process takes over.
PAGE 573
IPX/SPX Subagent (G-Series) Dependencies Dependencies The following products must be configured and running for the subagent to operate properly: • • • • SNMP agent (D22 or later) EMS (D21 or later) A G02 or later version of the NonStop IPX/SPX product and the underlying SLSA resources upon which it relies. An SNMP manager that can send requests to a SNMP agent process Installation Steps The subagent is automatically installed when you install NonStop IPX/SPX.
PAGE 574
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
IPX/SPX Subagent (G-Series) Starting and Stopping the Subagent Starting and Stopping the Subagent The IPXPROTO processes and SNMP agents with which you want the subagent to communicate must be running before the subagent is started. If an agent is not running, start it with the RUN command: RUN SNMPAGT /NAME $agent-process, NOWAIT/ Start the IPX/SPX Subagent by entering the RUN command at a terminal that is running the TACL program.
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. If you specify more than one agent, separate agent process names with a space.
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. ipxproto-process identifies a local or remote IPXPROTO process you want the subagent to monitor.
PAGE 578
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. After startup, you can use two MIB objects to control MIB value updates.
PAGE 579
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]. If you receive one of these messages, retry the RUN command using the correct startup syntax.
PAGE 580
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
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 Value Object and Attributes Definition ipxBasicSysInstance 1.3.6.1.4.1.23.2.5.1.1.1.
PAGE 582
IPX/SPX Subagent (G-Series) MIB Objects Table 13-2. ipxBasicSysEntry Objects Supported by the Subagent (page 2 of 3) Derivation of Value Object and Attributes Definition ipxBasicSysInHdrErrors 1.3.6.1.4.1.23.2.5.1.1.1.7 read-only Counter The number of IPX packets discarded because of errors in their headers, including any IPX packets with a size smaller than the minimum of 30 bytes. Calculated by IPXPROTO process ipxBasicSysInUnknownSockets 1.3.6.1.4.1.23.2.5.1.1.1.
PAGE 583
IPX/SPX Subagent (G-Series) ipxBasicSysTable Maintenance Table 13-2. ipxBasicSysEntry Objects Supported by the Subagent (page 3 of 3) Derivation of Value Object and Attributes Definition ipxBasicSysOutPackets 1.3.6.1.4.1.23.2.5.1.1.1.16 read-only Counter The total number of IPX packets transmitted. Calculated by IPXPROTO process ipxBasicSysConfigSockets 1.3.6.1.4.1.23.2.5.1.1.1.17 read-only INTEGER The configured maximum number of IPX sockets that can be open at one time.
PAGE 584
IPX/SPX Subagent (G-Series) HP MIB Objects Table 13-3. Compliance With Novell ipxBasicSys Group Definitions (page 2 of 2) Object Descriptor Compliance Explanation ipxBasicSysInDiscards Partial The values of ipxAdvSysInDiscards and ipxAdvSysInCompressDiscards are not taken into account. ipxBasicSysInBadChecksums Yes See Table 13-2. ipxBasicSysInDelivers Yes See Table 13-2. ipxBasicSysNoRoutes Yes See Table 13-2.
PAGE 585
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).
PAGE 586
IPX/SPX Subagent (G-Series) zipx Group tdmNwInfoTable Entries Table 13-4 describes tdmNwInfoTable entries.
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 1.3.6.1.4.1.169.3.164.1.1.1.2 read-only DisplayString (SIZE (0..50)) The name of the IPXPROTO process program name. \system.$volume. subvolume.file-name obtained using a mechanism equivalent to the SCF INFO PROCESS DETAIL command. tdmNwInfoQIOLibFileName 1.3.6.1.4.1.169.3.164.1.1.1.
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 1.3.6.1.4.1.169.3.164.1.1.1.9 read-only INTEGER The maximum percentage of QIO memory to be used by the IPXPROTO process. Integer obtained using a mechanism equivalent to the SCF INFO PROCESS DETAIL command. tdmNwInfoQIOUsage 1.3.6.1.4.1.169.3.164.1.1.1.10 read-only Gauge (0..
PAGE 589
IPX/SPX Subagent (G-Series) zipx Group tdmNwIPXTable Entries Table 13-5 describes tdmNwIPXTable entries.
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 1.3.6.1.4.1.169.3.164.2.1.1.3 read-only Counter The total number of outbound packets sent from the IPX layer. Integer value obtained using a mechanism equivalent to the SCF STATS PROCESS command. tdmNwIPXMaxSockets 1.3.6.1.4.1.169.3.164.2.1.1.
PAGE 591
IPX/SPX Subagent (G-Series) zipx Group tdmNwSPXTable Entries Table 13-6 describes tdmNwSPXTable entries.
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 1.3.6.1.4.1.169.3.164.3.1.1.2 read-only INTEGER The maximum number of concurrent explicit binds to the IPXPROTO process. Integer value obtained using a mechanism equivalent to the SCF INFO PROCESS DETAIL command. tdmNwSPXMaxConn 1.3.6.1.4.1.169.3.164.3.1.1.
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 1.3.6.1.4.1.169.3.164.3.1.1.10 read-only Counter The number of times SPX received a bad packet. Integer value obtained using a mechanism equivalent to the SCF STATS PROCESS command. tdmNwSPXSuppressedPacketCnt 1.3.6.1.4.1.169.3.164.3.1.1.
PAGE 594
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 1.3.6.1.4.1.169.3.164.4.1.1.1 read-only INTEGER The unique identifier of the instance of an 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 1.3.6.1.4.1.169.3.164.4.1.1.7 read-only Counter The number of times a user request was received by the NCP layer. Integer value obtained using a mechanism equivalent to the SCF STATS PROCESS command. tdmNwNCPTotalErrors 1.3.6.1.4.1.169.3.164.4.1.1.
PAGE 596
IPX/SPX Subagent (G-Series) zipx Group Figure 13-4.
PAGE 597
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 1.3.6.1.4.1.169.3.164.5.1.1.1 read-only INTEGER The unique identifier of the instance of an IPXPROTO process.
PAGE 598
IPX/SPX Subagent (G-Series) zipx Group Table 13-8. tdmNwServerEntry Objects Supported by the Subagent (page 2 of 2) Object and Attributes Definition Description of Value tdmNwServerType 1.3.6.1.4.1.169.3.164.5.1.1.5 read-only INTEGER The type of the server.
PAGE 599
IPX/SPX Subagent (G-Series) zisa Group zisa Group The zisa group contains objects that describe IPX/SPX Subagent process attributes.
PAGE 600
IPX/SPX Subagent (G-Series) zisa Group tdmNwSaConfig Group Objects Table 13-9 describes tdmNwSaConfig group objects.
PAGE 601
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 1.3.6.1.4.1.169.3.196.1.1.1 read-only DisplayString (SIZE (0..20)) The name of the subagent process. \system.$process, where system and process are 1 to 7 alphanumeric characters, starting with a letter. tdmNwSaProcessVersion 1.3.6.1.4.1.169.3.196.1.1.2 read-only DisplayString (SIZE (0..
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 1.3.6.1.4.1.169.3.196.1.1.9 read-only INTEGER { rowcreate (1), operatorrequest (2), subagentkeepalive (3), invalidprocessname (4), incorrectprocessname (5), resourceproblem (6)} The reason for the value of tdmNwSaBackupState. One of the values shown in the first column. tdmNwSaSwitchToBackupNow 1.3.6.1.4.1.169.
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 1.3.6.1.4.1.169.3.196.1.1.14 read-write INTEGER (0..32000) The number of minutes between subagent attempts to connect to a disconnected backup process, SNMP agent process, IPXPROTO process, or EMS collector process. The value can be set at startup by using the -k startup parameter or from a manager.
PAGE 604
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) zisa (196) tdmNwSubagent (1) tdmNwSaAgentNamesTable (2) tdmNwSaAgentNamesEntry (1) tdmNwSaAgentName (1) tdmNwSaAgentState (2) tdmNwSaAgentStateReason (3) Table 13-10.
PAGE 605
IPX/SPX Subagent (G-Series) zisa Group tdmNwSaIPXPROTONamesTable Entries Table 13-11 describes the objects in each tdmNwSaIPXPROTONamesTable entry.
PAGE 606
IPX/SPX Subagent (G-Series) zisa Group Table 13-11. tdmNwSaIPXPROTONamesEntry Objects Supported by the Subagent (page 2 of 2) Object and Attributes Definition tdmNwSaIpxProtoStateReason 1.3.6.1.4.1.169.3.196.1.3.1.4 read-only INTEGER { rowcreate (1), operatorrequest (2), subagentkeepalive (3), invalidprocessname (4), incorrectprocessname (5), resourceproblem (6)} The reason for the value of tdmNwSaIpxProtoState. Description of Value One of the values in the first column.
PAGE 607
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
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 CONSTANT ZSPI-SSN-ZISA VALUE VERSION "D30". VALUE 196. DEFINITION ZISA-VAL-SSID 02 z-filler TYPE character 8 TANDEM.
PAGE 609
IPX/SPX Subagent (G-Series) Tokens in ZISA Event Messages Table 13-13.
PAGE 610
IPX/SPX Subagent (G-Series) Tokens in ZISA Event Messages Table 13-15.
PAGE 611
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
IPX/SPX Subagent (G-Series) 1001: ZISA-EVT-SUBAGENT-AVAILABLE 1001: ZISA-EVT-SUBAGENT-AVAILABLE A subagent process has started successfully.
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
IPX/SPX Subagent (G-Series) 1002: ZISA-EVT-SUBAGENT-UNAVAILABLE 1002: ZISA-EVT-SUBAGENT-UNAVAILABLE A subagent process has stopped.
PAGE 615
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. The backup process takes over if it exists. Recovery. Informational message only; no corrective action is needed.
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). The DDL AS clause of this value (“agent-available”) appears in the message text following “event number:”. ZISA-VAL-CHRSN-reason is the change reason.
PAGE 617
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.
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.
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. resource-problem A SNMP agent process failed. Effect.
PAGE 620
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.
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
IPX/SPX Subagent (G-Series) 1006: ZISA-EVT-BACKUP-UNAVAILABLE 1006: ZISA-EVT-BACKUP-UNAVAILABLE The subagent’s backup process stopped.
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
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.
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
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.
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
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. incorrect-processname Start an EMS collector process using a unique 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.
PAGE 630
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.
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.
PAGE 632
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-allocationfailure”) 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
IPX/SPX Subagent (G-Series) 1012: ZISA-EVT-PROCESS-TRAPPED 1012: ZISA-EVT-PROCESS-TRAPPED The subagent process trapped.
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 “Termin
PAGE 636
IPX/SPX Subagent (G-Series) 1012: ZISA-EVT-PROCESS-TRAPPED SNMP Configuration and Management Manual—424777-006 13-74
PAGE 637
14 Ethernet Subagent This section describes the Ethernet Subagent and the MIBs it supports.The Ethernet Subagent allows Ethernet resources on NonStop systems to be monitored by SNMP managers. The Ethernet Subagent provides statistics about Ethernet interfaces (E4SA, 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.
PAGE 638
Ethernet Subagent The Ethernet Subagent and the SNMP Agent Figure 14-1. Architectural Overview of the Ethernet Subagent Ethernet/ Token Ring Subagent SNMP Agent forwards authenticated requests to subagent. 2 SNMP Agent Subagent returns responses and linkUp/linkDown Trap messages to SNMP Agent. 5 Subagent retrieves information about the interfaces through SCP for the configured TCP/IP process. SCP ($ZNET) 3 SNMP Agent receives and authenticates requests for information regarding Ethernet interfaces.
PAGE 639
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) internet (1) mgmt (2) mib-II (1) system (1) interfaces (2) at (3) ip (4) icmp (5) tcp (6) udp (7) egp (8) cmot (9) transmission (10) . . dot3 (7) √ . .
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) nonstopsystems (3) zesa (217) <−− Ethernet Subagent zesaAgentName (1) process objects zesaAgentState (2) zesaProcessName (3) zesaProcessVersion (4) zesaProgramFile (5) zesaProcessPriority (6) zesaProcessGroupID (7) zesaProcessUserID (8) zesaPrimaryCPU (9) zesaP
PAGE 641
Ethernet Subagent Installing the Ethernet Subagent Installing the Ethernet Subagent Run the Distributed Systems Management/Software Configuration Manager (DSM/SCM) product to install the SNMP agent and the Ethernet Subagent. Then load the ASN.1 source code for the Ethernet Subagent’s private MIB onto any SNMP manager station from which you want to monitor Ethernet resources.
PAGE 642
Ethernet Subagent Starting the Ethernet Subagent Starting the Ethernet Subagent Start the Ethernet Subagent using the TACL RUN command. Be sure to specify the name of a running SNMP agent. Following is an example of starting an Ethernet Subagent named $ZESA, with a backup process running in processor 6, that communicates with SNMP agent $ZSNMP: RUN ETHSA /NAME $ZESA, NOWAIT/ -a $ZSNMP -b 6 Syntax of the startup options follows established conventions used in the Guardian environment. [RUN] [[$volume.
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. -a -b -c -k -r -s -t [\node.]$agent-process backup-cpu-number [\node.
PAGE 644
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. -r refresh-timer specifies, in seconds, how often the subagent should refresh its cached values for the MIB. The default is 60 seconds.
PAGE 645
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
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
Ethernet Subagent ZESA MIB Objects Table 14-2. Controlling an Ethernet Subagent Through SNMP (page 2 of 2) You can control this attribute of an Ethernet Subagent... By issuing SNMP Set requests against this object... Initially set with this startup parameter.. . Rate at which subagent makes reconnection attempts zesaKeepAliveTimer -k Cause subagent to update MIB values in cache zesaRefreshNow Rate at which cached values for MIB objects are refreshed zesaRefreshTimer -r 60 seconds.
PAGE 648
Ethernet Subagent ZESA MIB Objects Table 14-3. Private (ZESA) MIB Objects Supported by the Ethernet Subagent (page 1 of 5) Object and Attributes Definition Format and Derivation of Value zesaAgentName 1.3.6.1.4.1.169.3.217.1 read-only DisplayString (SIZE (0..32)) The name of the SNMP agent process with which the Ethernet Subagent is communicating. \node.$agent-process specified for the -a startup parameter. If none specified, $ZSNMP on the local node. zesaAgentState 1.3.6.1.4.1.169.3.217.
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 1.3.6.1.4.1.169.3.217.8 read-only INTEGER (0..255) The NonStop Kernel process user ID part of the process access ID (PAID) for the Ethernet Subagent process. user-ID-number zesaPrimaryCPU 1.3.6.1.4.1.169.3.217.9 read-only INTEGER (0..
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 Subagent backup process to take over and a new backup process to be created. One of these values: 1.3.6.1.4.1.169.3.217.
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 update of the MIB tables and generating traps (if needed). One of these values: 1.3.6.1.4.1.169.3.217.
PAGE 652
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 connection between the Ethernet Subagent and the TCP/IP process whose Ethernet interfaces are being monitored. The settable values for this object are: 1.3.6.1.4.1.169.3.217.
PAGE 653
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 this resource object... Is indicated or controlled by this state object... Which may contain one of the following states...
PAGE 654
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 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” state.
PAGE 656
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) Object and Attributes Definition Format and Derivation of Value dot3StatsTable Objects: Entries describing the Ethernet interfaces of the TCP/IP resources being monitored. Refer to dot3StatsTable Maintenance on page 14-28 for information on how entries are created and updated. dot3StatsIndex 1.
PAGE 657
Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 2 of 7) Object and Attributes Definition dot3StatsFCSErrors 1.3.6.1.2.1.10.7.2.3 read-only Counter Number of frames discarded because of frame checksum errors. Format and Derivation of Value This object is supported for E4SA, GESA and the G4SA. It is a value obtained from: • • • dot3StatsSingleCollisionFrames 1.3.6.1.2.1.10.7.2.
PAGE 658
Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 3 of 7) Object and Attributes Definition dot3StatsMultipleCollision Frames 1.3.6.1.2.1.10.7.2.5 read-only Counter The number of succesfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. Format and Derivation of Value This object is supported for GESA and G4SA, but not for E4SA.
PAGE 659
Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 4 of 7) Object and Attributes Definition dot3StatsDeferredTransmissions 1.3.6.1.2.1.10.7.2.7 read-only Counter Number of frames that could not be transmitted immediately due to bus activity. Format and Derivation of Value This object is supported for E4SA, GESA, and G4SA.
PAGE 660
Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 5 of 7) Object and Attributes Definition dot3StatsExcessiveCollisions 1.3.6.1.2.1.10.7.2.9 read-only Counter Number of frames that had their transmission aborted after 15 collisions. Format and Derivation of Value This object is supported for the E4SA, GESA, and G4SA.
PAGE 661
Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 6 of 7) Object and Attributes Definition dot3StatsInternalMacTransmit Errors 1.3.6.1.2.1.10.7.2.10 read-only Counter Number of frames for which transmission on a particular interface fails due to an internal MAC sublayer tansmit error. Format and Derivation of Value This object is supported for GESA and G4SA, but not for E4SA.
PAGE 662
Ethernet Subagent MIB Objects Table 14-5. dot3StatsTable Objects Supported by Ethernet Subagent (page 7 of 7) Object and Attributes Definition dot3StatsFrameTooLong 1.3.6.1.2.1.10.7.2.13 read-only Counter Number of frames discarded because the length of the frame was greater than the maximum frame size. Format and Derivation of Value This object is supported for E4SA, GESA, and G4SA.
PAGE 663
Ethernet Subagent RFC Compliance RFC Compliance Table 14-6 summarizes compliance of Interfaces group support with RFC 1643. Table 14-6. Compliance With dot3 Group Definitions in RFC 1643 Object Descriptor Compliance Explanation dot3StatsIndex Yes See Table 14-5. dot3StatsAlignmentErrors Yes See Table 14-5. dot3StatsFCSErrors Yes See Table 14-5. dot3StatsSingleCollisionFrames Partial See Table 14-5 (dot3StatsSingleCollisionFrames is supported for GESA, E4SA, and G4SA.
PAGE 664
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
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
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 The Ethernet Subagent process (zesaProcessName) has completed process initialization after initial startup or after a takeover by the backup process.
PAGE 667
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 A Shared Resource Library (SRL) call to the SLSA has failed.
PAGE 668
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 CONSTANT CONSTANT CONSTANT ZESA-VAL-OWNER ZESA-VAL-NUMBER ZESA-VAL-VERSION ZESA-VAL-EXTERNAL-SSID DEFINITION ZESA-VAL-SSID 02 z-filler TYPE character 8 02 z-owner TYPE ZSPI-DDL-CHAR8 02 z-number TYPE ZSPI-DDL-INT 02 z-version TYPE ZSPI-DDL-UINT VERSION. END VALUE VALUE VALUE VALUE "TANDEM". 217. VERSION "G06". "TANDEM.217.G06". TACL SSID.
PAGE 669
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. ZEMS-TKN-CHANGE-REASON Reason for object state change.
PAGE 670
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. 3001: ZESA-EVT-SUBAGENT-AVAIL The Ethernet Subagent process has completed process initialization after initial startup or after a takeover by the backup process.
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 ZEMS-TKN-CHANGE-REASON Associated Text (DDL AS Clause) and Meaning ZEMS-VAL-UNDERLYING-UP “underlying-serv-up” indicates that the Ethernet Subagent process has come up because an underlying resource on which it depends has become available.
PAGE 672
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-processunavailable”) 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.” Cause.
PAGE 675
Ethernet Subagent 3003: ZESA-EVT-AGENT-OBJ-AVAIL 3003: ZESA-EVT-AGENT-OBJ-AVAIL Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZESA-TKN-AGENT ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> <6> <7> ZESA-TKN-AGENT zesaAgentName ZESA-EVT-AGENT-OBJ-AVAIL ZEMS-VAL-UNDERLYING-UP ZESA-VAL-STATE-state ZESA-VAL-STATE-CONNECTED ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number: <3>, rea
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 ZEMS-TKN-STATE-PREVIOUS Associated Text (DDL AS Clause) and Meaning ZESA-VAL-STATE-CONNECTED “connected” indicates a normal operational state.
PAGE 677
Ethernet Subagent 3004: ZESA-EVT-AGENT-OBJ-UNAVAIL 3004: ZESA-EVT-AGENT-OBJ-UNAVAIL Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZESA-TKN-AGENT ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-UNDERLYING-OBJNAME ZEMS-TKN-SYMPTOM-STRING Value <1> <2> <3> <4> <5> <6> <7> <8> ZESA-TKN-AGENT zesaAgentName ZESA-EVT-AGENT-OBJ-UNAVAIL ZEMS-VAL-UNDERLYING-FAILED ZESA-VAL-STATE-state ZESA-VAL-STATE-DISCONNECTED zesaAgentName code-location/ internal-context-text <9
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 ZEMS-TKN-STATE-PREVIOUS Associated Text (DDL AS Clause) and Meaning ZESA-VAL-STATE-CONNECTED “connected” indicates a normal operational state.
PAGE 679
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.
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 ZEMS-TKN-CHANGE-REASON Associated Text (DDL AS Clause) and Meaning ZEMS-VAL-UNDERLYING-UP “underlying-serv-up” indicates that the backup Ethernet Subagent process is available because an underlying resource on which it depends has become available.
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. Recovery. Informational message only; no corrective action is needed. Sample Messages 98-07-08 11:31:36 \NOVA.$ZESA TANDEM.ETHSA.
PAGE 682
Ethernet Subagent 3006: ZESA-EVT-BACKUP-OBJ-UNAVAIL 3006: ZESA-EVT-BACKUP-OBJ-UNAVAIL Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZESA-TKN-BACKUP ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-SYMPTOM-STRING ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> <6> <7> ZESA-TKN-BACKUP zesaProcessName ZESA-EVT-BACKUP-OBJ-UNAVAIL ZEMS-VAL-reason ZESA-VAL-STATE-state ZESA-VAL-STATE-state code-location/ internal-context-text <8> ZEMS-VAL-NULL Conditional Tokens
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 ZEMS-TKN-CHANGE-REASON Associated Text (DDL AS Clause) and Meaning ZEMS-VAL-UNDERLYING-FAILED “underlying-serv-failed” indicates that an underlying service on which the backup Ethernet Subagent process depends has 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. The Ethernet Subagent process continues to run without a backup. Configuration changes are not saved if a primary process failure occurs. Recovery.
PAGE 685
Ethernet Subagent 3007: ZESA-EVT-EMSCOLL-AVAIL 3007: ZESA-EVT-EMSCOLL-AVAIL Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZESA-TKN-EMSCOLLECTOR ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> <6> <7> ZESA-TKN-EMSCOLLECTOR zesaEmsCollectorName ZESA-EVT-EMSCOLL-AVAIL ZEMS-VAL-reason ZESA-VAL-STATE-state ZESA-VAL-STATE-CONNECTED ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number:
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” indicates a normal operational interface between the EMS collector and the subagent.
PAGE 687
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.
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 ZEMS-TKN-CHANGE-REASON Associated Text (DDL AS Clause) and Meaning ZEMS-VAL-UNDERLYING-FAILED “underlying-serv-failed” indicates that an underlying service on which the interface with the EMS collector process depends has failed.
PAGE 689
Ethernet Subagent 3008: ZESA-EVT-EMSCOLL-UNAVAIL This information is displayed only if the value of the ZEMS-TKN-CHANGEREASON 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” always appears in the message text following “user content.” Cause.
PAGE 690
Ethernet Subagent 3009: ZESA-EVT-TCPIP-OBJ-AVAIL 3009: ZESA-EVT-TCPIP-OBJ-AVAIL Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZESA-TKN-TCPIP ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> <6> <7> ZESA-TKN-TCPIP zesaTcpIpProcess ZESA-EVT-TCPIP-OBJ-AVAIL ZEMS-VAL-reason ZESA-VAL-STATE-state ZESA-VAL-STATE-CONNECTED ZEMS-VAL-NULL Conditional Tokens None Message Text Object available <1>-<2>, event number: <3>, reason:
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
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.
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-resourceunavailable”) appears in the message text following “event number.” ZEMS-VAL-reason indicates the reason the TCP/IP process has become unavailable. The DDL AS clause associated with this value is inserted in the message text following “cause.
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-CHANGEREASON is ZEMS-VAL-UNDERLYING-FAILED.
PAGE 695
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.
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
Ethernet Subagent 3012: ZESA-EVT-INTERNAL-FAULT 3012: ZESA-EVT-INTERNAL-FAULT Unconditional Tokens ZEMS-TKN-SUBJECT-MARK ZESA-TKN-SUBAGENT ZEMS-TKN-EVENTNUMBER ZEMS-TKN-CHANGE-REASON ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-STATE-CURRENT ZEMS-TKN-SYMPTOM-STRING ZEMS-TKN-USER-CONTENT Value <1> <2> <3> <4> <5> <6> <7> ZESA-TKN-SUBAGENT zesaProcessName ZESA-EVT-INTERNAL-FAULT ZEMS-VAL-INTERNAL-FAILED ZESA-VAL-STATE-state ZESA-VAL-STATE-DISCONNECTED code-location/ internal-context-text <8> ZEMS-VAL-NULL Conditiona
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 ZEMS-TKN-STATE-PREVIOUS Associated Text (DDL AS Clause) and Meaning ZESA-VAL-STATE-CONNECTED “connected” indicates a subagent in a running state, having completed its startup initialization.
PAGE 699
Ethernet Subagent 3013: ZESA-EVT-CONFIGURATION-INVALID Sample Message 98-07-08 11:49:38 \NOVA.$ZESA TANDEM.ETHSA.G06 003012 Object unavailable Ethernet-SNMPsubagent - \NOVA.
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
Ethernet Subagent 3014: ZESA-EVT-TAKEOVER-BY-BACKUP 3014: ZESA-EVT-TAKEOVER-BY-BACKUP Unconditional Tokens ZEMS-TKN-EVENTNUMBER ZEMS-TKN-TXFAULT-TYPE Value <1> ZESA-EVT-TAKEOVER-BY-BACKUP <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-bybackup”) appears in the message text. ZESA-VAL-TF-TAKEOVER identifies the type of transient fault that occurred.
PAGE 702
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.
PAGE 704
Part V.
PAGE 705
A 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
SCF Command Syntax Summary for the NonStop Agent ADD Command 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" ] [ , HOSTADDR "ip-address"] [ , ACCESS { READONLY | READWRITE } ] TRAPDEST Object ADD TRAPDEST [$agent-process.
PAGE 707
SCF Command Syntax Summary for the NonStop Agent DELETE Command 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 The DELETE command removes the definition of an object from the NonStop agent configuration.
PAGE 708
SCF Command Syntax Summary for the NonStop Agent NAMES Command 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 configuration.
PAGE 709
SCF Command Syntax Summary for the NonStop Agent STATUS Command 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 STATUS TRAPDEST [$agent-process.
PAGE 710
SCF Command Syntax Summary for the NonStop Agent TRACE Command 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
B 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. These error messages have no associated error numbers and are generally self-explanatory.
PAGE 712
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.
PAGE 713
SCF Error Messages for the NonStop Agent SCF Error Messages Help SCF Error Messages Help To request help for any SCF error message: -> HELP subsystem error-number For example, suppose the following messages appears on your terminal: SNMP E00001 Attribute conflict: HOSTADDR SNMP E-00015 Object $ZSMP.
PAGE 714
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.
PAGE 715
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. You provided an invalid wildcard specification as a HOSTADDR attribute value.
PAGE 716
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. Recovery. Check the event log to find out the corresponding file system error number.
PAGE 717
C 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. Table C-1.
PAGE 718
Unsolicited SNMP Agent Messages Events Events Event messages are sent to the EMS collector specified when starting the SNMP agent or to the EMS collector assigned through SCF by altering the PROCESS object. By default, event messages are sent to $0 on the local node. You can suppress sending event messages with the COLLECTOR startup parameter. Configuring the EMS collector is described in Section 2, Installing and Configuring the SNMP Agent..
PAGE 719
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
Unsolicited SNMP Agent Messages 003: ZSMP-EVT-STATE-CHANGE Effect. Depending on the severity of the situation, the SNMP agent responds as follows: • • • If a nonfatal error occurs (such as when an unknown value is encountered in a request), the SNMP agent stops processing the request. When the SNMP agent cannot run at all and a takeover by the backup would only cause a recurrence of the error (such as when the SNMP agent cannot complete its initialization procedures), the agent process stops.
PAGE 721
Unsolicited SNMP Agent Messages 004: ZSMP-EVT-OSS-ERROR Cause. A SNMP agent object changed state for one of the following reasons: Object A component of the SNMP agent’s configuration defined in the SNMP agent’s SNMPCTL file entered a different state. Operator An SCF command or SNMP Set request was issued against a component of the SNMP agent’s configuration, causing it to move to a different state.
PAGE 722
Unsolicited SNMP Agent Messages 004: ZSMP-EVT-OSS-ERROR Recovery.
PAGE 723
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) OSS-err-nu m Fatal Error? -10 No 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). -11 Yes An unexpected NULL pointer was passed to the encoder.
PAGE 724
Unsolicited SNMP Agent Messages 006: ZSMP-EVT-CONFIG-ERROR location-number is a numeric identifier for a specific location within the function. socket-function-name is the name of a socket function. This function, called by method-name, generated the error. socket-err-num is the socket error number. socket-file-name is the name of the protocol stack with which the socket is communicating. Cause. A socket library call returned an error when the SNMP agent was communicating with HP TCP/IP software. Effect.
PAGE 725
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
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
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, protocolname, 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. A subagent process has incorrectly opened the agent for the service requested. Effect.
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.
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. access mode. The ability of members of a community to access MIB objects.
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. See also trap destination and directed trap destination. coldStart trap. A trap signaling that the SNMP agent has been initialized and that some object values may change as a result.
PAGE 731
Glossary directed trap destination directed trap destination. In a SNMP agent configuration, a trap destination to which the SNMP agent directs traps only if explicitly told to do so by the subagent. See also trap destination and broadcast trap destination. DEFINE name. A component of the routing destination statement in the routing distributor filter source code that identifies the SNMP agent to which the EMS Trap Subagent routes trap messages.
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 on. Event Management Service.
PAGE 733
Glossary Gigabit Ethernet 4-Port ServerNet adapter (G4SA) Gigabit Ethernet 4-Port ServerNet adapter (G4SA). A multiport ServerNet adapter that provides 1000 megabits/second (Mbps) data transfer rates between HP NonStop™ S-series systems and Ethernet LANs. The G4SA is the only LAN adapter supported for the I/O Adapter Module (IOAM) enclosure, and it is installed in slots 1, 2, 3, 4, and 5 of an IOAM.
PAGE 734
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. ICMP. See Internet Control Message Protocol. ICMP group.
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. internet layer.
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. A conceptual collection of objects that can be defined and accessed via a network management protocol, such as SNMP.
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. network interface file.
PAGE 738
Glossary object tree object tree. The model used to identify SNMP objects. It comprises an unlabeled root connected to labeled nodes which in turn may have subordinate nodes. A node and its subordinate nodes make up a subtree. A node with no subordinates is a leaf object. Each object on the tree is assigned an object descriptor and an object identifier. OCS. See Operator Control Services. octet. An 8-bit value. OID. See object identifier. omf group.
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. port 162. An SNMP protocol entity receives trap messages on UDP port 162 on the host with which it is associated. PROCESS object.
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. Request for Comments. A document in a series containing surveys, measurements, ideas, techniques, and observations, as well as proposed and accepted standards for the Internet suite of protocols, such as TCP/IP and SNMP.
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. destroy Is supplied by an SNMP manager to delete all of the instances associated with an existing conceptual row. Rule Management Services.
PAGE 742
Glossary socket. socket. A pairing of an IP address and a port number. Also, a logical connection between two applications across a TCP/IP network. On SNMP systems, a socket corresponds to a file system open. The same application or system can use multiple sockets. When you identify the process or device with which you want to communicate, you identify the socket by specifying the address and port. SPI. See Subsystem Programmatic Interface. startup parameter.
PAGE 743
Glossary HP TCP/IP communicate with other systems and with workstations over local area networks based on the 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 by other vendors.
PAGE 744
Glossary trap trap. An unsolicited PDU sent asynchronously by an SNMP agent to an SNMP manager station to signal an important event. The agent is responsible for performing threshold checks and only reporting conditions that meet certain threshold criteria. In an SNMP environment, traps are usually generated as the result of few and critical events, and the interrupt message is simple and short. TRAPDEST object.
PAGE 745
Glossary well-known port well-known port. Any of a set of protocol ports preassigned for specific uses by transport level protocols (that is, TCP and UDP). Servers follow the well-known port assignments so clients can locate them. wide area network. Any of a number of technologies that data transfer among electronic entities that are geographically remote from each other. X.25. The CCITT standard protocol for transport-level network service. Originally designed to connect terminals to computers, X.
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. zhrmSaProcess group. A group defined by HP in the Host Resources Subagent’s MIB that provides information about the Host Resources Subagent process.
PAGE 747
Index Numbers 0, as Internet address wildcard 5-7, 5-9, 5-11 A ABORT command ENDPOINT object syntax 5-3 objects for which supported 5-1 PROFILE object syntax 5-4 TRAPDEST object syntax 5-5 ACCESS attribute, PROFILE object 4-12 Access modes 2-28 Activating table row entries 3-29 ADD command ENDPOINT object syntax 5-6 objects for which supported 5-1 PROFILE object syntax 5-8 TRAPDEST object syntax 5-10 ALTER command ENDPOINT object syntax 5-13 objects for which supported 5-1 PROCESS object syntax 5-15 PROFIL
PAGE 748
C Index BREAK key 6-10 Broadcast trap destination 4-19, 5-12 C Cannot send trap C-10 closeagent description 10-13 failures 10-20 coldStart trap C-1 Command modifiers DETAIL INFO command modifier 5-21 VERSION command modifier 5-38 SCF 4-23 SUB INFO command modifier 5-22 NAMES command modifier 5-25 STATUS command modifier 5-29 Commands FROM 6-6 NEXT 6-7 RECORD 6-9 SELECT 6-10 COMMUNITY attribute attribute conflict (SCF error 00002) 5-2, B-4 PROFILE object 4-12 TRAPDEST object 4-16 Community name 1-7, 2-27
PAGE 749
E Index Default object definitions (continued) TRAPDEST object 4-18, 5-12 Defense Advanced Research Projects Agency Glossary-2 DEFINED state ENDPOINT object 4-9 PROFILE object 4-14, 5-30 TRAPDEST object 4-17 DELETE command ENDPOINT object syntax 5-19 objects for which supported 5-1 PROFILE object syntax 5-19 TRAPDEST object syntax 5-20 Deleting a table row 3-30 DETAIL (SCF command modifier) INFO command 5-21 VERSION command 5-38 Device type 6-4 Directed trap destination 4-19, 5-12 Directing SCF output to
PAGE 750
E Index Endpoint object (continued) HOSTADDR attribute 4-8 INFO command 5-21 invalid wildcard specification in HOSTADDR B-5 multiple-agent connections 2-35 naming conventions 4-8 NETWORK attribute 4-8 remote connections 2-37 single-agent connections 2-35 START command 5-26 state transition illustration 4-11 states 4-9, 5-28 STATUS command 5-28 STOP command 5-33 use 2-34 wildcard support naming conventions 4-9 End-to-end services Glossary-4 Enterprise field 1-8 Enumerated value 6-10 ENV command (SCF, gener
PAGE 751
F Index Event messages destination 2-9 for troubleshooting 7-2 generated by Host Resources Subagent 11-104 generated by Trap Multiplexer 12-21 generic trap event message text 12-29, 13-50, 13-52, 13-53, 13-55, 13-58, 13-60, 13-62, 13-64, 13-66, 13-68, 13-70, 13-72 generic trap event tokens 12-29, 13-50, 13-52, 13-53, 13-55, 13-58, 13-60, 13-62, 13-64, 13-66, 13-68, 13-70, 13-72 suppressing 2-9 Exterior Gateway Protocol Glossary-4 F Filtering events for EMS Trap Subagent 9-8 for NonStop NET/MASTER Trap Su
PAGE 752
H Index Host Resources Subagent (continued) Spooler process specification 11-19 stable object refresh rate 11-19 standard MIB groups 11-1 starting 11-12 startup parameters 11-13 stopping 11-21 tracing 11-21 traps 11-99 troubleshooting 11-21 use of Guardian procedures 11-2 use of Spooler procedure 11-2 ZHRM subsystem ID 11-105 Host Resources Subagent’s MIB proprietary groups 11-3 RFC compliance 11-8 standard groups 11-1 Host Resources Subagent’s MIB groups hrDevice group 11-35 hrStorage group 11-29 hrSWRun
PAGE 753
H Index hrDeviceErrors 11-41 hrDeviceID 11-40 hrDeviceIndex 11-39 hrDeviceStatus 11-41 hrDeviceTable 11-39 hrDeviceType 11-39 hrDiskStorageAccess 11-43 hrDiskStorageCapacity 11-44 hrDiskStorageMedia 11-44 hrDiskStorageRemovable 11-44 hrDiskStorageTable 11-43 hrFSAccess 11-46 hrFSBootable 11-46 hrFSIndex 11-45 hrFSLastFullBackupDate 11-47 hrFSLastPartialBackupDate 11-47 hrFSMountPoint 11-45 hrFSRemoteMountPoint 11-46 hrFSStorageIndex 11-47 hrFSTable 11-45 hrFSType 11-46 hrMemorySize 11-30 hrNetworkIfIndex
PAGE 754
I Index hrSWRunPerfTable 11-60 hrSWRunStatus 11-57 hrSWRunTable 11-54 hrSWRunType 11-56 hrSystem group hrSystemDate 11-26 hrSystemInitialLoadDevice 11-26 hrSystemInitialLoadParameters 11-26 hrSystemMaxProcesses 11-27 hrSystemNumUsers 11-27 hrSystemProcesses 11-27 hrSystemUpTime 11-26 value maintenance 11-28 hrSystemDate 11-26 hrSystemInitialLoadDevice 11-26 hrSystemInitialLoadParameters 11-26 hrSystemMaxProcesses 11-27 hrSystemNumUsers 11-27 hrSystemProcesses 11-27 hrSystemUpTime 11-26 hrWSRunPerfCPU 11-6
PAGE 755
I Index ifMtu 8-33 ifNumber 8-31 ifOperStatus 8-34 ifOutDiscards 8-37 ifOutErrors 8-37 ifOutNUcastPkts 8-36 ifOutOctets 8-36 ifOutQLenProtos 8-37 ifOutUcastPkts 8-36 ifPhysAddress 8-34 ifSpeed 8-33 ifTable maintenance 8-38 IFTBL 11-17 ifType 8-32 INFO command ENDPOINT object syntax 5-21 objects for which supported 5-1 PROCESS object syntax 5-22 PROFILE object syntax 5-23 TRAPDEST object syntax 5-24 Information protocol 1-9 Installation EMS Trap Subagent dependencies 9-4 steps 9-4 Host Resources Subagent d
PAGE 756
I Index Internet Protocol Glossary-7 Internet suite of protocols Glossary-7 Interprocess communication See IPC transmission Invalid PDU C-11 Invalid wildcard specification (SCF error 00005) B-5 Invoking the EMS Trap Subagent 9-9 the Host Resources Subagent 11-12 the NonStop agent 2-14 the NonStop NET/MASTER Trap Subagent 10-13 the Trap Multiplexer 12-6 IP See Internet Protocol IP group ifInHdrErrors 8-42 ipAdEntAddr 8-44 ipAdEntBcastAddr 8-45 ipAdEntIfIndex 8-44 ipAdEntNetMask 8-44 ipForwarding 8-41 ipFor
PAGE 757
K Index ipRouteNextHop 8-46 ipRouteProto 8-47 ipRouteTable maintenance 8-50 ipRouteType 8-46 ipxBasicSys group compliance with Novell 13-21 ipxBasicSysExistState 13-11 ipxBasicSysName 13-11 ipxBasicSysTable 13-4, 13-19 maintenance 13-21 IPXMGR 13-1 IPXMIB 13-11 IPXMIBA 13-11 IPXPROTO process objects 13-4 IPXPROTO processes 13-1 IPX/SPX Subagent communication with other processes 13-7 configuration 13-12 dependencies 13-11 EMS Event Messages 13-16 EMS events 13-45 event message descriptions 13-49 Expand wi
PAGE 758
N Index Management Information Base (continued) for NonStop NET/MASTER Trap Subagent 10-14 for proprietary groups of Host Resources Subagent 11-3 for standard groups of Host Resources Subagent 11-1 Host Resources Subagent’s MIB 11-23 object 1-9 object group 1-12 types of 1-9 Managing table rows from SNMP managers 3-24 Message protocol 1-6 Messages Host Resources Subagent events 11-104 traps 11-99 NonStop agent events C-2 request errors 7-6 traps C-1 NonStop NET/MASTER Trap Subagent 10-18 Trap Multiplexer
PAGE 759
O Index NonStop agent (continued) example of starting two NonStop agents on same HP node 2-24 installation 2-1 internet address by which known 4-8 memory utilization 2-10 MIB groups supported by 3-1 initial values 2-6 process name 2-8 program file name (SNMPAGT) 4-5, 4-26 RFC compliance 1-17 starting 2-14 stopping 2-14 TACL PARAM statements 2-8, 2-16 TCP/IP process through which NonStop agent can be reached 4-8 through which NonStop agent sends traps 4-16 trace facility 7-5 tracing 2-11 troubleshooting 7-
PAGE 760
O Index Object identifiers (continued) for NonStop agent 1-12 for SNMP group 3-6 for System group 3-3 for TCP group 8-56 for UDP group 8-61 for zagInEndpoint group 3-14 for zagInProcess group 3-12 for zagInternal group 3-11 for zagInTrapdest group 3-17 for zhrmDevUnavail group 11-85 for zhrmRefresh group 11-96 for zhrmSaProcess group 11-91 for zhrmTableInfo group 11-62 for zhrmThreshold group 11-77 for ztmxPDUStatistics group 12-12 for ztmxProcess group 12-16 forzagInProfile group 3-16 Object name defined
PAGE 761
P Index OUT command (SCF, general) 4-22 Output, SCF, directing to a file 4-24 P Parallel Library TCP/IP 1-5, 2-11, 2-14, 2-20, 2-23, 2-24, 2-37, 8-1, 8-4, 8-15, 8-16 PARAMs for starting Trap Multiplexer 12-10 Port 161 Glossary-11 Port number Glossary-11 Port-162 Glossary-11 Problem handling 7-1 PROCESS object 2-25 ALTER command 5-15 default object definition 4-6 defined 4-5 EMSCOLL attribute 4-5, 4-6 INFO command 5-22 NAMES command 5-25 naming conventions 4-5 wildcard support 4-6 state transition illustr
PAGE 762
S Index Refreshing MIB values 11-5 Requests for Comments See also RFC compliance compliance 1-17 how to obtain 1-18 Resource Not Available ... (SCF error 00042) 5-2 Resource not available...
PAGE 763
S Index SCF (continued) continuing a command to next line 4-23 for error messages 4-24 introduction 4-21/4-24 multiple commands on a line 4-23 error messages 4-24, B-1/B-6 See also Error messages, SCF identifying subsystem 4-22 INFO command 5-21/5-24 information specific to SNMP 4-25/4-27 introduction 4-1/4-2 NAMES command 5-25 nonsensitive commands 4-23 null object 5-1 object attributes 4-3 object hierarchy 4-4 object states 4-4 objects 4-3 objects, defined 4-3 See also individual object entries online h
PAGE 764
S Index SNMP group (continued) snmpOutTooBigs 3-8 snmpOutTraps 3-9 when counters are incremented 7-6 SNMPAGT, program file name 4-26 SNMPCTL creation of 2-6 startup parameter 2-9 use of 1-14 SNMPCTL file EMSCOLL attribute 5-15 unable to update...
PAGE 765
T Index STOP command ENDPOINT object syntax 5-33 objects for which supported 5-1 PROFILE object syntax 5-33 TRAPDEST object syntax 5-34 STOPPED state ENDPOINT object 4-9, 5-28 PROFILE object 4-14, 5-30 TRAPDEST object 4-17, 5-31 Stopping TCP/IP Subagent 8-16 the EMS Trap Subagent 9-9 the Host Resources Subagent 11-21 the IPX Subagent 13-16 the NonStop agent 2-14, 2-24 the NonStop NET/MASTER Trap Subagent 10-13 the Trap Multiplexer 12-9 STOPPING state of ENDPOINT object 4-9, 5-28 SUB (SCF command modifier)
PAGE 766
T Index TCP group RFC compliance 8-60 tcpActiveOpens 8-57 tcpConnLocalAddress 8-59 tcpConnLocalPort 8-59 tcpConnRemAddress 8-60 tcpConnRemPort 8-60 tcpConnState 8-59 tcpCurrEstab 8-58 tcpInErrs 8-60 tcpInSegs 8-58 tcpMaxConn 8-57 tcpOutSegs 8-58 tcpPassiveOpens 8-57 tcpRetransSegs 8-58 tcpRtoAlgorithm 8-57 tcpRtoMax 8-57 tcpRtoMin 8-57 tcpActiveOpens 8-57 tcpConnLocalAddress 8-59 tcpConnLocalPort 8-59 tcpConnRemAddress 8-60 tcpConnRemPort 8-60 tcpConnState 8-59 tcpConnTable maintenance 8-61 tcpCurrEstab 8
PAGE 767
T Index TCP/IP (continued) TCPIPSA (program file) 8-13 TCP/IP process to be queried by 8-15 unavailable resources 8-8 uninstrumented objects 8-8 ZTSA subsystem ID 8-68 ztsa subtree 8-7 ZTSAMIB file 8-11 TCP/IP Subagent's MIB ICMP group 8-51 Interfaces group 8-30 IP group 8-40 TCP group 8-56 UDP group 8-61 TCP/IP v6 8-5 TCP/IPv6 1-5, 8-15 tdmNwInfoResetTime 13-16 tdmNwInfoTable 13-4, 13-24 tdmNwIPXTable 13-4, 13-27 TDMNWMIB 13-11 tdmNwNCPTable Entries 13-31 tdmNwSaAgentName 13-44 tdmNwSaAgentNamesTable 13-
PAGE 768
T Index Trap Multiplexer (continued) related operating system events 11-115, 12-47 SPI data definition files 12-25 starting 12-6 startup parameters 12-7 stopping 12-9 TCP/IP process(s) for trap receipt 12-8 tracing 12-9 trap event messages 12-28 ZTMX subsystem ID 12-26 Trap Multiplexer’s MIB groups ztmxPDUStatistics group 12-12 ztmxProcess group 12-16 trapContentStandard 9-14, 10-16 trapCritical 9-16, 10-18 TRAPDEST object 4-16/4-20 ABORT command 5-4, 5-5 ADD command 5-10/5-13 ALTER command 5-17 COMMUNITY
PAGE 769
U Index U W UDP See User Datagram Protocol UDP group RFC compliance 8-63 udpInDatagrams 8-62 udpInErrors 8-62 udpLocalAddress 8-63 udpLocalPort 8-63 udpOutDatagrams 8-62 UDP transmission protocol 1-9 udpInDatagrams 8-62 udpInErrors 8-62 udpLocalAddress 8-63 udpLocalPort 8-63 udpOutDatagrams 8-62 udpTable maintenance 8-63 Unable to update SNMPCTL file (SCF error 00007) B-6 Unsolicited messages from Host Resources Subagent 11-99, 11-104 from NonStop agent C-1 from NonStop NET/MASTER Trap Subagent 10-18 fr
PAGE 770
Z Index zagInEpRowStatus 3-14 zagInEpState 3-15 zagInPfAccess 3-17 zagInPfCommunity 3-17 zagInPfHostAddr 3-17 zagInPfName 3-16 zagInPfRowStatus 3-16 zagInPfState 3-17 zagInProcBkupPID 3-13 zagInProcCpuTime 3-13 zagInProcCreatTime 3-13 zagInProcCurrentOpeners 3-14 zagInProcCurrTime 3-12 zagInProcess group zagInProcBkupPID 3-13 zagInProcCpuTime 3-13 zagInProcCreatTime 3-13 zagInProcCurrentOpeners 3-14 zagInProcCurrTime 3-12 zagInProcHomeTerm 3-13 zagInProcMaxOpeners 3-14 zagInProcName 3-12 zagInProcPAID 3-1
PAGE 771
Z Index zhrmDevUnavail group (continued) zhrmDevUnDown 11-86 zhrmDevUnErrors 11-89 zhrmDevUnID 11-89 zhrmDevUnIndex 11-87 zhrmDevUnOther 11-86 zhrmDevUnStatus 11-89 zhrmDevUnTable 11-86 zhrmDevUnTrapEnable 11-86 zhrmDevUnType 11-87 zhrmDevUnUp 11-86 zhrmDevUnCurrTime 11-86 zhrmDevUnDescr 11-88 zhrmDevUnDown 11-86 zhrmDevUnErrors 11-89 zhrmDevUnID 11-89 zhrmDevUnOther 11-86 zhrmDevUnStatus 11-89 zhrmDevUnTable 11-86 zhrmDevUnTrapEnable 11-86 zhrmDevUnType 11-87 zhrmDevUnUp 11-86 zhrmDiskThreshold trap zhrm
PAGE 772
Z Index zhrmInfDiskTable group (continued) zhrmInfDiskGetNextCounter 11-72 zhrmInfDiskLastDynamRefresh 11-72 zhrmInfDiskLastIndex 11-71 zhrmInfDiskLastStableRefresh 11-72 zhrmInfDiskSetCounter 11-72 zhrmInfFSEntries 11-74 zhrmInfFSFirstIndex 11-74 zhrmInfFSGetCounter 11-75 zhrmInfFSGetNextCounter 11-75 zhrmInfFSLastDynamRefresh 11-75 zhrmInfFSLastIndex 11-74 zhrmInfFSLastStableRefresh 11-75 zhrmInfFSSetCounter 11-75 zhrmInfFSTable 11-74 zhrmInfFSTable group zhrmInfFSEntries 11-74 zhrmInfFSFirstIndex 11-74
PAGE 773
Z Index zhrmInfStorFirstIndex 11-64 zhrmInfStorGetCounter 11-65 zhrmInfStorGetNextCounter 11-65 zhrmInfStorLastDyamRefresh 11-64 zhrmInfStorLastIndex 11-64 zhrmInfStorLastStableRefresh 11-65 zhrmInfStorSetCounter 11-65 zhrmInfStorTable 11-64 zhrmInfStorTable group zhrmInfStorEntries 11-64 zhrmInfStorFirstIndex 11-64 zhrmInfStorGetCounter 11-65 zhrmInfStorGetNextCounter 11-65 zhrmInfStorLastDynamRefresh 11-64 zhrmInfStorLastIndex 11-64 zhrmInfStorLastStableRefresh 11-65 zhrmInfStorSetCounter 11-65 zhrmLast
PAGE 774
Z Index zhrmTableInfo group (continued) zhrmInfFSTable 11-74 zhrmInfNetTable 11-68 zhrmInfPartTable 11-73 zhrmInfPrnTable 11-70 zhrmInfStorTable 11-64 zhrmThrDisk 11-81 zhrmThrDisk group zhrmThrDiskHighValue 11-82 zhrmThrDiskLowValue 11-82 zhrmThrDiskPercentUse 11-81 zhrmThrDiskTotal 11-81 zhrmThrDiskTrapEnable 11-82 zhrmThrDiskUse 11-81 zhrmThrDiskAllocationFailures 11-83 zhrmThrDiskAllocationUnits 11-83 zhrmThrDiskDescr 11-83 zhrmThrDiskHighValue 11-82 zhrmThrDiskIndex 11-83 zhrmThrDiskLowValue 11-82 zh
PAGE 775
Z Index ZHRM-EVTHRM-SA-IO-ERR (003) 11-111 HRM-SA-NO-MEM-SPACE (004) 11-113 HRM-SA-PROG-ERR (005) 11-114 HRM-SA-STARTED (002) 11-109 HRM-SA-TERMINATED (001) 11-108 zipx group 13-22 maintenance 13-36 tdmNwInfoBackupCPU 13-25 tdmNwInfoEntry 13-24 tdmNwInfoIOPortAddress 13-25 tdmNwInfoIOPortName 13-25 tdmNwInfoIOPortType 13-25 tdmNwInfoNumberOfOpens 13-26 tdmNwInfoPrimaryCPU 13-25 tdmNwInfoQIOLibFileName 13-25 tdmNwInfoQIOLimit 13-26 tdmNwInfoQIOUsage 13-26 tdmNwInfoResetTime 13-26 tdmNwInfoSampleTime 13-26
PAGE 776
Z Index ztmxInDecodeErrors 12-13 ztmxInEgpNeighborLossTraps 12-15 ztmxInEnterpriseSpecificTraps 12-15 ztmxInGetNextPdus 12-13 ztmxInGetPdus 12-13 ztmxInGetResponsePdus 12-13 ztmxInLinkDownTraps 12-15 ztmxInLinkUpTraps 12-15 ztmxInSetPdus 12-13 ztmxInTrapPdus 12-13 ztmxInWarmStartTraps 12-13 ZTMXMIB 12-4 ztmxPDUStatistics group value maintenance 12-15 ztmxInAuthFailTraps 12-15 ztmxInColdStartTraps 12-13 ztmxInDecodeErrors 12-13 ztmxInEgpNeighborLossTraps 12-15 ztmxInEnterpriseSpecificTraps 12-15 ztmxInGetN
PAGE 777
Special Characters Index ztmxUdpStatsCurrTime 12-13 ZTMX-EVTTMX-IO-ERR (103) 12-43 TMX-NO-MEM-SPACE (104) 12-45 TMX-PROG-ERR (105) 12-46 TMX-STARTED (102) 12-42 TMX-TERMINATED (101) 12-40 TRAP-AUTH-FAIL (004) 12-36 TRAP-COLDSTART (000) 12-32 TRAP-EGP-LOSS (005) 12-37 TRAP-ENT-SPFC (006) 12-38 TRAP-LINKDOWN (002) 12-34 TRAP-LINKUP (003) 12-35 TRAP-WARMSTART (001) 12-33 ztsaAgentName 8-16, 8-21 ztsaAgentState 8-16, 8-21 ztsaBackupCPU 8-16, 8-18, 8-22 ztsaBackupPIN 8-16, 8-22 ztsaBackupState 8-16, 8-18, 8-23
PAGE 778
Special Characters Index SNMP Configuration and Management Manual—424777-006 Index -32