Beruflich Dokumente
Kultur Dokumente
SC41-5412-00
AS/400 IBM
Simple Network Management
Protocol (SNMP) Support
Version 4
SC41-5412-00
Take Note!
Before using this information and the product it supports, be sure to read the general information under “Notices” on page v.
This edition applies to the licensed program Operating System/400, (Program 5769-SS1), Version 4 Release 1 Modification 1, and to
all subsequent releases and modifications until otherwise indicated in new editions.
Make sure that you are using the proper edition for the level of the product.
Order publications through your IBM representative or the IBM branch serving your locality. If you live in the United States, Puerto
Rico, or Guam, you can order publications through the IBM Software Manufacturing Solutions at 800+879-2755. Publications are not
stocked at the address given below.
IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication. You can also mail
your comments to the following address:
IBM Corporation
Attention Department 542
IDCLERK
3605 Highway 52 N
Rochester, MN 55901-7829 USA
If you have access to Internet, you can send your comments electronically to IDCLERK@RCHVMW2.VNET.IBM.COM; IBMMAIL, to
IBMMAIL(USIB56RZ).
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes
appropriate without incurring any obligation to you.
Part 3. Appendixes
IBM may have patents or pending patent applications covering subject matter in this document. The fur-
nishing of this document does not give you any license to these patents. You can send license inquiries,
in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, NY
10594, U.S.A.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged, should contact the software interop-
erability coordinator. Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
IBM Corporation
Software Interoperability Coordinator
3605 Highway 52 N
Rochester, MN 55901-7829 USA
This publication may refer to products that are announced but not currently available in your country. This
publication may also refer to products that have not been announced in your country. IBM makes no
commitment to make available any unannounced products referred to herein. The final decision to
announce any product is based on IBM's business and technical judgment.
This publication contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
This publication contains small programs that are furnished by IBM as simple examples to provide an
illustration. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot
guarantee or imply reliability, serviceability, or function of these programs. All programs contained herein
are provided to you "AS IS". THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED.
General-Use programming interfaces allow the customer to write programs that obtain the services of the
OS/400 licensed program.
ACF/VTAM ILE
Advanced Peer-to-Peer Networking NetView
AIX Operating System/400
AnyNet OS/400
Application System/400 PS/2
APPN RISC System/6000
AS/400 RS/6000
C/400 VTAM
IBM 400
Microsoft, Windows, and the Windows 95 logo are trademarks or registered trademarks of Microsoft Cor-
poration.
PC Direct is a trademark of Ziff Communications Company and is used by IBM Corporation under license.
UNIX is a registered trademark in the United States and other countries licensed exclusively through
X/Open Company Limited.
Other company, product, and service names, which may be denoted by a double asterisk (**), may be
trademarks or service marks of others.
not start when the STRTCP command runs. 1=Add 2=Change 4=Remove 5=Display
Option 1 of the Configure TCP/IP SNMP menu Confirm Remove of Communities for
displays the Change SNMP Attributes SNMP Display: Option 4 causes the Work
(CHGSNMPA) command in prompt mode. with Communities for SNMP display to be shown:
á ñ 8.145.15ð.129
8.145.15ð.13ð
8.145.15ð.131
8.145.15ð.134
8.145.15ð.135
8.145.15ð.136
8.145.15ð.139
8.145.15ð.14ð
8.145.15ð.141
8.145.15ð.144
F3=Exit F12=Cancel
1 The user is not able to write information to the databases. They are able to write programs that access the databases.
R QZCADRLR PFILE(QSYS/QAZCADIR)
QAZCAPRT ZCBCLT
ZCBIDX
255A
12H
VARLEN
0 or 1 opens with the SNMP agent 3. Check the message, if not from SNMP agent,
return it to caller
0 or n registrations (no logical upper bound)
4. If the message is from the SNMP agent, copy
Zero opens is not a useful normal condition for a DPI packet to subagent buffer
subagent. This would occur briefly only between
a connectSNMP() call and the sending of a DPI In contrast, receiveDPIpacket() does only the last
open packet. Zero registrations might be useful step. In which case, the subagent implementation
for a subagent that only sends traps and does not must perform the first three. (Note that the DPI
implement any MIB groups. More than a single packet itself is not the message that is placed on
subtree registration may be useful for a variety of the subagent's data queue. See the
reasons: sa_dataq_msg structure in qtossapi.h for the
format of the data queue message from the SNMP
1. Perhaps separate MIBs are being imple- agent. The purpose of the data queue message,
mented by separate people, but it is decided is to signal the subagent that a DPI packet is
to have these MIB implementations all run pending.)
within a single job, which will perform the sub-
agent API functions on behalf of the MIB
implementers Waiting for Work from the SNMP
2. Perhaps a few OIDs within a MIB are known Agent
to be relatively large overhead, compared to
the rest of the subtree, for a DPI request type The main purpose for which an SNMP subagent is
(for example, set). There may be perfor- developed is to provide additional MIB groups to
mance benefits to registering these OIDs sep- SNMP manager applications. Therefore, an
arately than the rest of the subtree, with a SNMP subagent spends most of its time waiting
different time-out value. for (and processing) requests that an SNMP
manager has sent to the local SNMP agent.
The sendDPIpacket() API does just this — for any
type of DPI packet a subagent wants to send, this Figure 6-5 on page 6-8 shows the structure for
routine is used to send it. the core processing loop of a subagent implemen-
tation.
Figure 6-5. Normal processing loop for a subagent. When all the varBinds have been processed, the
list of varBinds is used to build a response DPI
The waitDPIpacket() is at the top of the loop. packet by calling mkDPIresponse().
When a request arrives from the SNMP agent, this
API will receive it, verify that it is from the SNMP Lastly, the DPI response is sent back to the
agent, and then return it to the caller. The DPI waiting SNMP agent by calling sendDPIpacket().
packet is then parsed by using the pDPIpacket() Then the subagent calls waitDPIpacket() again,
routine so that the packet contents are available. with an appropriate time-out, to again another
cycle of the normal processing loop.
A key decision point occurs after a successful
parse. The DPI packet may be a GET,
The result of changing the value of a MIB object Overview: Ethernet-like Interface MIB defines
that is an index to an instance of that MIB object objects for managing ethernet-like object interface
is undefined. For example, the result of the oper- types.
ation set ipRouteDest.9.13ð.38.28=9.13ð.38.29
is undefined. RFC: RFC1398
When adding a row to a table by setting the value RFC noted exception: The dot3CollTable
of a MIB object, default values are assigned to the is not supported.
other objects in the row.
indexes: The value of a MIB object which is MIB Subtree Description: Ethernet-like
an index to an instance of that MIB object MIB.
need not be set explicitly. For example, the
operation set MIB Subtree Object Identifier: dot3 ::= {
ipRouteNextHop.9.13ð.38.28=9.13ð.25.25ð transmission 7 }
will implicitly create the MIB object instance
MIB Subtree Object Identifier: fddi ::= { Prerequisite MIB Modules: RFC1155,
transmission 15 } RFC1212
Advanced Peer-To-Peer
Frame Relay MIB Networking (APPN) MIB
Overview: Frame Relay objects for managing Overview: The APPN Node Group provides
Frame Relay. global information about the APPN node, which is
either a network node or an end node.
RFC: RFC1315
The APPN Topology Group represents the entire
APPN network topology including network nodes,
RFC noted exception: The set operation is virtual nodes, and all transmission groups (TGs)
supported for only frTrapState.
that are associated with these nodes.
MIB Subtree Description: Frame Relay The APPN Local Topology Group describes the
MIB. local topology. This MIB group defines the
required objects for retrieval of information about
MIB Subtree Object Identifier: frame- this node and the objects that represent the local
relay ::= { transmission 32 } topology about end nodes.
Appendix A. OS/400 SNMP Agent Set Processing and Supported SNMP MIBs A-3
AS/400, APPN link stations are APPC controllers ibmappnLocalThisNode
that are attached to APPN-capable lines.)
ibmappnLocalGeneral
ibmappnLocalNnSpecific
RFC: Informational RFC 1593 ibmappnLocalTg - table of local trans-
mission groups (TGs)
RFC noted exceptions: Some groups of ibmappnLocalEnTopology
RFC 1593 are implemented with some extensions.
ibmappnLocalEnTable - table of adjacent end
Refer to the concise MIB description (MIB module)
nodes
for details.
ibmappnLocalEnTgTable - table of adjacent
MIB Subtree Description: SNA APPN MIB end node TGs
The Client Software Group provides information Prerequisite MIB Modules: RFC1155,
that is related to installed software and fixes. RFC1212
Note: A NetView for AIX application provides
RFC: None support for this data.
RFC noted exception: None NetView for AIX subagent MIB object
supported
MIB Subtree Description: Client Manage-
ment nv6saComputerSystemLoad OBJECT-TYPE
SYNTAX Gauge
MIB Subtree Object Identifier: ACCESS read-only
clientMgmtSubAgent ::= { internet(1) private(4) STATUS mandatory
enterprise(1) ibm(2) ibmprod(6) 50 } DESCRIPTION
The CPU load as a percentage. For
example, 25% is 2500.
MIB Module Name: IBMCLTM
::= { nv6saComputerSystem 1 }
The ASN.1 for this MIB is available in member
IBMCLTM in file QSYS/QANMMIB.
DPI 2.0 MIB
Prerequisite MIB Modules: RFC1155,
RFC1212 Overview: An extension to SNMP agents that
permits end-users to dynamically add or replace
management variables in the local MIB without
NetView for AIX Subagent MIB requiring recompilation of the SNMP agent.
Although SNMP subagents are supported by an
AS/400 system, this support does not use the DPI
Overview: One MIB object in this MIB is sup- 2.0 MIB. This is because the AS/400 subagent
ported. The object provides the average per-
support does not use TCP or UDP between the
centage of load (processor utilization) during the
agent and subagents. A transparent, internal
elapsed time. Each retrieval of this value is calcu-
mechanism is used by the subagents. This MIB is
lated in the same manner as the value that is dis-
supported by the AS/400 SNMP agent even
played by the DSPSYSACT command when the
though the communication between the agent and
restart function key is used.
subagent on the AS/400 does not use TCP or
UDP. This is done for compatibility.
RFC: None
This MIB is implemented by the AS/400 system
RFC noted exception: None but is not currently used. For detail on the MIB,
see RFC1592.
MIB Subtree Description: NetView for AIX
subagent ComputerSystem group RFC: RFC1592
Appendix A. OS/400 SNMP Agent Set Processing and Supported SNMP MIBs A-5
RFC noted exception: None. saNumber
number of currently registered subagents
MIB Subtree Description: SNMP Distrib- saAllPacketsIn
uted Protocol Interface Version 2.0 total number of subagent packets that are
received from all subagents
MIB Subtree Object Identifier: dpi20MIB
saAllPacketsOut
::= { ibmDPI 1 }
total number of subagent packets that are
sent to all subagents.
Prerequisite MIB Modules: SNMPv2-SMI
The saTable provides information about specific
subagents such as status, address, and
description.
SNMP Subagent MIB
The saTreeTable provides information about spe-
Note!
cific subtrees that subagents have registered with
This MIB is experimental and is subject to the SNMP agent.
change in future releases.
RFC: None
Overview: The SNMP subagent MIB provides RFC noted exception: None
information about subagents to facilitate manage-
ment activities. The MIB is designed to handle
multiple types of subagents, including DPI suba- MIB Subtree Description: SNMP suba-
gents (see RFC1592), for which the DPI 2.0 API is gent MIB
provided. All the SA MIB information is dynamic,
for the duration of the SNMP agent job. The SA MIB Subtree Object Identifier: saMIB ::=
MIB consists of six summary OIDs and two tables. { internet(1) private(4) enterprise(1) ibm(2)
The summary OIDs are: ibmResearch(2) 12 }
saDefaultTimeout
MIB Module Name: IBMSNMPSA
default value for subagents for response
timeout
The ASN.1 for this MIB is available in member
saMaxTimeout IBMSNMPSA in file QSYS/QANMMIB.
largest value a subagent may use for
response time-out Prerequisite MIB Modules: RFC1155,
RFC1212, RFC1213
saAllowDuplicateIDs
flag to allow duplicate subagent OIDs, or not
SNMP agent jobs do not start when the Another application is listening on UDP port Make sure no other applications are using UDP
STRTCPSVR command runs. 161. port 161 and then start the SNMP agent again
using the STRTCPSVR command.
SNMP managers are not receiving any The OS/400 SNMP agent is not active. Make sure TCP/IP (or AnyNet) and the OS/400
responses from the OS/400 SNMP agent for SNMP agent are active. The OS/400 SNMP
any SET, GET, or GETNEXT requests. agent is active if jobs QTMSNMP and
QTMSNMPRCV are running in subsystem
QSYSWRK. Use the WRKACTJOB command
to determine if these jobs are active.
The SNMP manager is sending the request Make sure that the SNMP manager is sending
to a system other than the intended AS/400. the request to the intended AS/400.
The SNMP manager is comparing the The SNMP agent will always send the response
response PDU source IP address with the PDU to the IP address which sent the original
destination IP address in the PDU it sent, PDU. Verify, especially for an SNMP manager
and they are not equal. system with multiple IP-addresses, that the
manager is using the expected IP address.
The SNMP manager is comparing the source The OS/400 SNMP agent does not use UDP
UDP port number in the response PDU with port 161 to send response PDUs, due to tech-
the destination UDP port number (the well- nical reasons. The SNMP management appli-
known port 161) in the PDU it sent to cation should not check the response PDU port
OS/400, and they are not equal. number. Instead, the SNMP manager applica-
tion needs to rely on checking the response
PDU IP address and, within the PDU, the
request-id to verify the PDU.
The SNMP manager is specifying a commu- Make sure that the SNMP manager is speci-
nity name that is unknown to the OS/400 fying a community name that is known to the
SNMP agent. OS/400 SNMP agent. The list of community
names may be displayed by using the
CFGTCPSNMP command. Community names
are case-sensitive, so make sure that the
SNMP manager is specifying the community
name correctly (example: PUBLIC and public
are two different community names). Also,
make sure that the value for the Translate com-
munity name (ASCIICOM) parameter for the
OS/400 community corresponds to the commu-
nity name being specified by the SNMP
manager. If the SNMP manager is an ASCII
system, the ASCIICOM parameter for the
OS/400 community should be *YES. If the
SNMP manager is an EBCDIC system or the
community name has one or more characters
that cannot be displayed, the ASCIICOM
parameter for the OS/400 community should be
*NO. If the community name or ASCIICOM
parameter need to be changed, the community
must be removed by using the RMVCOMSNMP
command and then added with the correct
values by using the ADDCOMSNMP command.
SNMP managers are receiving error responses The SNMP manager is specifying an incor- Make sure the SNMP manager is specifying an
from the OS/400 SNMP agent for GET or rect object identifier in the request. object identifier for an object that is supported
GETNEXT requests. by the OS/400 SNMP agent.
The SNMP manager is specifying an object
identifier for an object that is not supported
by the OS/400 SNMP agent.
SNMP managers are receiving error responses The SNMP manager is specifying an incor- Make sure the SNMP manager is specifying an
from the OS/400 SNMP agent for SET rect object identifier in the request. object identifier for an object that is supported
requests. by the OS/400 SNMP agent.
The SNMP manager is specifying an object Make sure the SNMP manager is specifying an
identifier for an object that is not supported object identifier for an object that can be
by the OS/400 SNMP agent. changed.
The SNMP manager is attempting to set an Make sure the SNMP manager is specifying a
object that is defined as read-only. valid value for the object.
The SNMP manager is attempting to set an
object to a value that is not valid.
The object access for the community is not Make sure that the object access for the
*WRITE. OS/400 community is *WRITE. The object
access for the community may be changed by
The object access for the community is
using the CHGCOMSNMP command. The
*SNMPATR and the object access in the
object access in the SNMP attributes may be
OS/400 SNMP attributes is not *WRITE.
changed by using the CHGSNMPA command.
SNMP managers are unable to access any The OS/400 subagent job is not active. End the SNMP agent by using the
objects found in the APPN MIB, Client Manage- ENDTCPSVR command and then start the
The OS/400 subagent job is active, but is
ment MIB, or NetView for AIX MIB. SNMP agent by using the STRTCPSVR
inactive according to the OS/400 SNMP
command. The OS/400 subagent runs in job
agent.
QSNMPSA in subsystem QSYSWRK. Use the
WRKACTJOB command to determine if this job
is active.
authenticationFailure traps are not being The IP address of the intended SNMP Make sure that the IP address of the SNMP
received by an SNMP manager. manager is not specified correctly in the manager to receive the trap is specified cor-
OS/400 SNMP attributes. rectly in the OS/400 SNMP attributes. The IP
address of the SNMP manager may be
changed by using the CHGSNMPA command.
The community name to be placed in the Make sure the trap community name is speci-
trap is not recognized by the SNMP fied correctly in the OS/400 SNMP attributes.
manager. The trap community name may be changed by
using the CHGSNMPA command.
The Send authentication traps Make sure the SNDAUTTRP SNMP attribute is
(SNDAUTTRP) SNMP attribute is specified specified as *YES. The SNDAUTTRP SNMP
as *NO. attribute may be changed by using the
CHGSNMPA command.
Verify, with the SNMP trap logging capabilities,
that the expected trap PDUs are being sent by
the SNMP agent. See Appendix B, “Journal for
SNMP Logging” on page B-1 for information
about how to use this function.
There are problems with the TCP/IP network See the TCP/IP Configuration and Reference
or AnyNet support. for more information about network problem
analysis.
Entries are not being made in journal QSNMP SET logging is specified as *NO in the Make sure that SET logging is specified as
in library QUSRSYS for SET requests received OS/400 community definition. *YES in the OS/400 SNMP community defi-
from SNMP managers. nition. The SET logging for the community may
SET logging is specified as *SNMPATR in
be changed by using the CHGCOMSNMP
the OS/400 community definition and is spec-
command. The SET logging in the SNMP attri-
ified as *NO in the OS/400 SNMP attributes.
butes may be changed by using the
CHGSNMPA command.
Entries are not being made in journal QSNMP GET logging is specified as *NO in the Make sure that GET logging is specified as
in library QUSRSYS for GET or GETNEXT OS/400 community definition. *YES in the OS/400 SNMP community defi-
requests received from SNMP managers. nition. The GET logging for the community may
GET logging is specified as *SNMPATR in
be changed by using the CHGCOMSNMP
the OS/400 community definition and is spec-
command. The GET logging in the SNMP attri-
ified as *NO in the OS/400 SNMP attributes.
butes may be changed by using the
CHGSNMPA command.
Entries are not being made in journal QSNMP Trap logging is specified as *NO in the Make sure that trap logging is specified as
in library QUSRSYS for traps sent to SNMP OS/400 SNMP attributes. *YES in the OS/400 SNMP attributes. The trap
managers. logging in the SNMP attributes may be changed
by using the CHGSNMPA command.
Table C-2 (Page 1 of 2). SNMP Management application developer problem analysis
Problem Cause Solution
The SNMP management application received The SNMP API has run out of resources to The management application can try reducing
an out of memory or out of buffers error. complete the operation. the size of the requested operation. If the
problem persists, report the error using the
ANZPRB command.
The SNMP Management application received The requested operation has exceeded the The management application can try reducing
an out of varBinds error. allowable number of varBinds for a single the number of varBinds in the varBind list.
operation.
The SNMP Management application received An Object IDentifier in the varBind list was The management application should specify the
an invalid OID error. not specified in the correct dotted decimal Object IDentifier in the correct dotted decimal
notation. notation.
The SNMP Management application receives The SNMP API's will do some rudimentary The management application should specify the
an invalid value error. checking on the value supplied during a value on a set in the correct form as specified
snmpSet operation. The API's will detect an by the ASN type.
incorrect length on integer types, and will
also check for incorrect dotted decimal nota-
tion on IP addresses and OID's when sup-
plied as values.
The SNMP Management application receives The ASN type specified for a particular OID The management application should specify a
an invalid value representation error. in the varBind list is not recognized as a known ASN type as listed in the QTOMEAPI
common ASN type. CLEINC file in QSYSINC library. (If you cannot
locate this file, contact your system support
department. The QSYSINC library can be
selectively installed at any time.)
The SNMP Management application receives The PDU specified could not be encoded or Retry the command. If the problem persists,
an encode or decode error. decoded for transmission across the wire. report the error to IBM using the ANZPRB
command.
The SNMP Management application received The value in community name length field The management application should specify a
an invalid community name length error. was not in the range of 1 to 256. community name length that is greater than 0
and less than or equal to 256.
The SNMP Management application received a The value in the time-out parameter field was The management application should specify a
time-out parameter error. not in the range of 1 to 100. time-out value that is greater than 0 and less
than or equal to 100.
The SNMP Management application received The hostname specified was not recognized The management application should specify the
an unknown host error. as a valid host on the network. correct hostname, or specify the dotted decimal
notation of the IP address.
The SNMP Management application received a The value length field on a varBind in the The management application should specify a
not OK error. varBind list was less than 0. value field greater than or equal to 0.
SNMP management application receives a The time-out value is set too low. Increase the time-out value and try again.
time-out from the SNMP APIs.
The SNMP agent receiving the SNMP opera- Make sure that the receiving agent is active.
tion is not active.
The SNMP management application is speci- Specify the correct community name.
fying a community name that is unknown to
the SNMP agent.
The SNMP management application is speci- Make sure the IP address is know to the SNMP
fying a correct community name, but the IP agent as a valid SNMP manager.
address of the manager is not part of the
community.
There are problems with the TCP/IP network See the TCP/IP Configuration and Reference
or AnyNet support. for more information about network problem
analysis.
SNMP management application receives an The SNMP management application tried to Make sure that the PDU type matches that of
invalid PDU type. issue an SNMP operation of one type while the SNMP operation being performed.
specifying a PDU built for another type.
SNMP management application receives an The SNMP management application tried to Make sure that the IP address is either in the
invalid IP address. issue an SNMP operation with an Hostname form or in the dotted decimal form.
unrecognizable IP address. (example of hostname form: host.city.state)
(example of dotted decimal form: 9.9.9.9)
SNMP management application received a The SNMP management application speci- The SNMP management application should not
Domain Error, Invalid pointer, or Invalid pointer fied a pointer which caused an object domain use system state references, retry the operation
type return code from the SNMP APIs. error, reference location in a space that does passing in a valid pointer to user state storage.
not contain a pointer, or the pointer refer- See the previously discussed message
enced storage in system state. These errors descriptions for further information.
are equivalent to escape messages
MCH6801, MCH3601, and MCH3602.
SNMP management application received an The SNMP management application speci- The SNMP management application should use
Invalid PDU, Host, Community, or Invalid fied a Null pointer. a non-NULL pointer.
pointer type return code from the SNMP APIs.
SNMP management application received a This states that the amount of space allo- The SNMP management application should
Return code 1 from the APIs. cated for the value returned in one or more specify a greater value in the val_len field of the
varBinds, for a GET or GETNEXT operation, _varBind structure.
was not sufficient.
SNMP management application receives a non- The SNMP agent could not fit the contents of If the management application specified more
zero return status in the Error Status field of the the returned data in the SNMP message. than one object identifier to retrieve, then
SNMP PDU on a Get or GetNext operation. reduce the number of object identifiers until the
returned data fits into a SNMP message.
The SNMP management application is speci- Make sure that the SNMP management appli-
fying an incorrect object identifier in the cation is specifying an object identifier for an
request. object that is supported by the receiving SNMP
agent or its subagents.
The SNMP management application is speci-
fying an object identifier that is not supported
by the receiving SNMP agent or its suba-
gents.
SNMP management application receives a non- The SNMP management application is speci- Make sure the SNMP manager is specifying an
zero return status in the Error Status field of the fying an incorrect object identifier in the object identifier for an object that is supported
SNMP PDU on a Set operation. request. by the receiving SNMP agent or its subagents.
The SNMP management application is speci- Make sure that the SNMP management appli-
fying an object identifier that is not supported cation is specifying an object identifier for an
by the receiving SNMP agent or its suba- object that can be changed.
gents.
The SNMP management application is
attempting to set and object that is defined
as read-only.
The SNMP management application is Make sure that the SNMP management appli-
attempting to set an object value that is not cation is specifying the correct ASN syntax in
valid. This value could be the incorrect ASN the ASN type field. Also, Make sure that the
syntax, or it may not be in the acceptable SNMP management application is specifying
range of values. the value with the acceptable range.
Traps are not being received by the SNMP trap The IP address of this system is not speci- Make sure that the IP address of this system is
manager. fied correctly on the SNMP agent system specified correctly on the SNMP agent system.
sending the trap.
There are problems with the TCP/IP network See the TCP/IP Configuration and Reference
or AnyNet support. for more information about network problem
analysis.
Traps are not being forwarded to other SNMP The IP address of the intended SNMP Make sure that the IP address of the SNMP
manager systems. manager is not specified correctly in the manager to receive the trap is specified cor-
OS/400 SNMP attributes. rectly in the OS/400 SNMP attributes. The IP
address of the SNMP manager may be
changed by using the CHGSNMPA command.
The community name to be placed in the Make sure the trap community name is speci-
trap is not recognized by the SNMP fied correctly in the OS/400 SNMP attributes.
manager. The trap community name may be changed by
using the CHGSNMPA command.
Trap forwarding was not specified when the Make sure that trap forwarding is specified
SNMP trap manager was started on this when the SNMP trap manager is started. The
system. SNMP trap manager is started by using the
STRTRPMGR command.
The SNMP agent on this system is not Make sure the SNMP agent is active. The
active. OS/400 SNMP agent is active if jobs
QTMSNMP and QTMSNMPRCV are running in
subsystem QSYSWRK. Use the WRKACTJOB
command to determine if these jobs are active.
There are problems with the TCP/IP network See the TCP/IP Configuration and Reference
or AnyNet support. for more information about network problem
analysis.
Jobs QTMSNMP, QTMSNMPRCV, It is possible that this may be caused by trap Do one or more of the following:
QTRAPMGR, and QTRAPMGRRCV in sub- forwarding being specified and the IP
Turn off trap forwarding by ending the trap
system QSYSWRK are consuming a large address of this system being listed as a trap
manager using the ENDTRPMGR
amount of processor resource. manager in the OS/400 SNMP attributes.
command. Then start the trap manager
It is possible that this system is part of a ring using the STRTRPMGR command with trap
of trap managers in your network that forwarding specified as *NO.
forward traps to each other.
Remove the IP address of this system from
the trap manager list in the OS/400 SNMP
attributes using the CHGSNMPA command.
Make sure there are no rings of trap man-
agers in your network.
The SNMP subagent is unable to successfully The subagent receives a NULL pointer from A NULL pointer from mkDPIopen() is usually
perform the open function the mkDPIopen() routine. caused by a simple error in one of the parame-
ters. Verify that each of the parameters in the
call are correct.
Verify that the subagent OID does not violate
SNMPv2 limits; no more than 128 subids and
each subid must be representable in a 32-bit
unsigned integer field.
The subagent cannot send the DPI open Verify that prior to calling sendDPIpacket(), a
packet. call has successfully been made to the
connectSNMP() routine.
The subagent receives an An SNMP_ERROR_DPI_otherError (101) in the
SNMP_ERROR_DPI_otherError (101) in the DPI response packet from the agent usually
DPI response packet from the agent. occurs due to some invalid value in the DPI
open packet. For example, the subagent's OID
must be null terminated and end with a subid,
not a '.'.
The subagent receives an The subagent receives a
SNMP_ERROR_DPI_duplicate- SNMP_ERROR_DPI_duplicate-
SubagentIdentifier (109) in the DPI response SubagentIdentifier (109) when the SNMP agent
packet from the agent. already has a active subagent with the same
OID, and the subagent MIB
saAllowDuplicateIDs is set to 2. Either change
the OID the subagent uses in the mkDPIopen()
call, or change the subagent MIB
saAllowDuplicateIDs to 1 to allow duplicates.
The SNMP subagent is unable to successfully The subagent receives a NULL pointer from A NULL return usually indicates some param-
perform the register function. the mkDPIregister() routine. eter error. Check the subagent's job log for
exceptions. If any are found, correct them,
rebuild the subagent code and try the call
again. If no exceptions are found, verify that the
parameters are valid (for example, group_p is
not NULL).
The subagent receives an The most common cause of an
SNMP_ERROR_DPI_otherError (101) in the SNMP_ERROR_DPI_otherError (101) in
DPI response packet from the agent. response to a DPI register packet is that the
subtree OID did not end with a '.'; verify that the
subtree OID ends with a '.'.
The subagent receives an The most common cause of an
SNMP_ERROR_DPI_alreadyRegistered SNMP_ERROR_DPI_alreadyRegistered (103)
(103) in the DPI response packet from the error is that the subagent attempted to register
agent. a subtree that would cause a protected subtree
to be affected. Verify that the subtree to be
registered (parameter group_p in the
mkDPIregister() call) is not above, at, or within
one of the SNMP agent's protected subtrees
(see the list of these in the mkDPIregister() API
documentation).
The subagent receives an For an SNMP_ERROR_DPI_higher-
SNMP_ERROR_DPI_higher- priorityRegistered (104), re-request the subtree
priorityRegistered (104) in the DPI response registration with a higher priority or 0 (which
packet from the agent. requests the highest). If the already registered
subagent has priority 0 (get the subagent MIB
saTstatus for the subtree), then there is no
higher priority to request, so the other subtree
must be unregistered or its subagent end
before you can register the subtree.
The SNMP subagent works for awhile, but then There is insufficient memory to build the Ensure that the fDPIset() routine is called so
mkDPIset() return NULL, when trying to build internal structures for the DPI packet, that memory use does not monotonically
structure for a response packet. because it has not been freed, after having increase while the subagent is running. (see
been dynamically allocated. “Simple Network Management Protocol (SNMP)
Subagent APIs” in the book System API
Reference: UNIX-Type APIs.
Some other exception condition occurred. See the messages in the job logs for both the
SNMP agent job (QTCP/QTMSNMP) and the
subagent job. Correct them and retry the suba-
gent job.
The SNMP subagent works for awhile, but then There is insufficient memory to build the Ensure that the fDPIparse() routine is called so
pDPIpacket() returns NULL, when trying to internal structures for the DPI packet, that memory use does not monotonically
parse a new incoming DPI packet. because it has not been freed, after having increase while the subagent is running. (see
been dynamically allocated. “Simple Network Management Protocol (SNMP)
Subagent APIs” in the book System API
Reference: UNIX-Type APIs.
Some other exception condition occurred. See the messages in the job logs for both the
SNMP agent job (QTCP/QTMSNMP) and the
subagent job. Correct them and retry the suba-
gent job.
The SNMP subagent occasionally gets a DPI The subagent has taken too long to respond Re-open or re-register with a longer time-out, or
unregister or close packet from the agent with to some SNMP agent request. That is, longer use a smaller max_varBinds value in the
reason_code of SNMP_UNREGISTER_time-out than the time-out value used by the subagent mkDPIopen() call, or both. Important note: the
or SNMP_CLOSE_time-out. in the mkDPIopen() or mkDPIregister() calls. entire SNMP agent waits for up to the time-out
value for a response to each DPI request. If
requests for a particular OID or subagent
subtree takes a long time (relatively) for the
subagent to process, then consideration should
be given to registering that OID or subtree sep-
arately (by the same subagent), with a appropri-
ately longer time-out.
The SNMP subagent gets a snmpsa_RC_err A run-time exception occurred, which is not See the messages in the job logs for both the
return code. covered by some other, more specific, return SNMP agent job (QTCP/QTMSNMP) and the
code. subagent job (that received the snmpsa_RC_err
return code) for exceptions. Correct them and
retry the subagent API calls. (By its nature this
return code is fairly rare, and the cause for the
exception is usually obvious, in either the agent
or the subagent job.)
(P) ─┬────────────────────────┬───────────────────────────────────5
55──ADDCOMSNMP──COM(──community-name──)────
│ ┌─\YES─┐ │
└─ASCIICOM(──┴─\NO──┴──)─┘
5──┬───────────────────────────────────────────────────┬──┬──────────────────────────┬───────────────────5
│ ┌─\ANY───────────────────────────┐ │ │ ┌─\SNMPATR─┐ │
│ │ ┌──
────────────────────────────┐ │ │ └─OBJACC(──┼─\READ────┼──)─┘
└─INTNETADR(──┴──6─manager-internet-address───
(1) ┴─┴──)─┘ ├─\WRITE───┤
└─\NONE────┘
5──┬──────────────────────────┬──┬──────────────────────────┬───────────────────────────────────────────5%
│ ┌─\SNMPATR─┐ │ │ ┌─\SNMPATR─┐ │
└─LOGSET(──┼─\YES─────┼──)─┘ └─LOGGET(──┼─\YES─────┼──)─┘
└─\NO──────┘ └─\NO──────┘
Notes:
P All parameters preceding this point can be specified in positional form.
community-name: Specify the name of the the Change SNMP Attributes (CHGSNMPA)
SNMP community being added. The name command is used for this community.
may contain characters that cannot be dis-
*READ: Allow SNMP managers that are part
played (for example, X'60619E').
of this community to read all management
information base (MIB) objects with get or get-
Optional Parameters next requests. Modification of MIB objects by
SNMP managers is not permitted.
ASCIICOM
Specifies whether the community name is *WRITE: Allow SNMP managers that are part
translated to ASCII characters when the com- of this community to change all MIB objects
munity profile is added to the SNMP agent that are able to change with set requests.
community list. Specifying *WRITE implies *READ access.
*YES: The community name is translated to *NONE: Do not allow SNMP managers that
ASCII characters when the community profile are part of this community any access to MIB
is added to the SNMP agent community list. objects.
This value should be specified if the SNMP
LOGSET
manager system defines its community names
Specifies whether set requests from SNMP
entirely of ASCII characters. An error
managers in this community are logged in
message is sent if the community name
journal QSNMP in library QUSRSYS.
cannot be translated to ASCII characters.
*SNMPATR: The value defined with the
*NO: The community name is not translated
Change SNMP Attributes (CHGSNMPA)
to ASCII characters when the community
command is used for this community.
profile is added to the SNMP agent commu-
nity list. This value should be specified if the *YES: Set requests are logged.
SNMP manager system defines its community
*NO: Set requests are not logged.
names using EBCDIC characters or charac-
ters that cannot be displayed. LOGGET
Specifies whether get requests and get-next
INTNETADR
requests from SNMP managers in this com-
Specifies the internet addresses of the SNMP
munity are logged in journal QSNMP in library
managers that are part of this community.
QUSRSYS.
*ANY: Allow any SNMP manager to be part
*SNMPATR: The value defined with the
of this community.
Change SNMP Attributes (CHGSNMPA)
manager-internet-address: Specify the command is used for this community.
internet address of the SNMP manager. The
*YES: Get requests and get-next requests
internet address is specified in the form
are logged.
nnn.nnn.nnn.nnn, where nnn is a decimal
number ranging from 0 through 255. An *NO: Get requests and get-next requests are
internet address is not valid if it has a value of not logged.
all binary ones or all binary zeros for the
network identifier (ID) portion or the host ID Example
portion of the address. If the internet address
is entered from a command line, the address ADDCOMSNMP COM(ROCHESTER)
must be enclosed in apostrophes. Up to 300 INTNETADR('8.6.5.4' '8.6.5.3')
unique internet addresses may be specified. OBJACC(\WRITE)
The same internet address may appear in
This command adds the community ROCHESTER
more than one community profile.
to the SNMP agent community list. SNMP man-
OBJACC agers with internet addresses 8.6.5.4 and 8.6.5.3
Specifies the object access for the community. are the only managers in the community and are
able to change all MIB objects.
*SNMPATR: The object access defined with
55──CFGTCPSNMP──────────────────────────────────────────────────────────────────────────────────────────5%
(P) ─┬────────────────────────┬───────────────────────────────────5
55──CHGCOMSNMP──COM(──community-name──)────
│ ┌─\YES─┐ │
└─ASCIICOM(──┴─\NO──┴──)─┘
5──┬───────────────────────────────────────────────────┬──┬──────────────────────────┬───────────────────5
│ ┌─\SAME──────────────────────────┐ │ │ ┌─\SAME────┐ │
└─INTNETADR(──┼─\ANY───────────────────────────┼──)─┘ └─OBJACC(──┼─\SNMPATR─┼──)─┘
│ ┌──
────────────────────────────┐ │ ├─\READ────┤
└──6─manager-internet-address───
(1) ┴─┘ ├─\WRITE───┤
└─\NONE────┘
5──┬──────────────────────────┬──┬──────────────────────────┬───────────────────────────────────────────5%
│ ┌─\SAME────┐ │ │ ┌─\SAME────┐ │
└─LOGSET(──┼─\SNMPATR─┼──)─┘ └─LOGGET(──┼─\SNMPATR─┼──)─┘
├─\YES─────┤ ├─\YES─────┤
└─\NO──────┘ └─\NO──────┘
Notes:
P All parameters preceding this point can be specified in positional form.
Purpose ASCIICOM
Specifies whether the community name is
The Change Community for SNMP translated to ASCII characters before it is
(CHGCOMSNMP) command changes an SNMP compared with the community name specified
community profile in the SNMP agent community in a request from an SNMP manager. This
list. An SNMP agent uses a community profile to parameter is used in combination with the
determine whether or not to honor a request sent community name to determine the community
by an SNMP manager. The community profile to be changed. If this parameter is not speci-
consists of a community name, an object access fied and two communities have the same
specification, and a list of the SNMP managers name but different ASCIICOM parameter
that are part of the community. The combination values, the community that is changed is the
of the community name (COM) and the translate community with ASCIICOM set to *YES.
to ASCII community (ASCIICOM) parameters *YES: The community name is translated to
defines a community. ASCII characters before it is compared with a
community name specified by an SNMP
Required Parameter manager.
nnn.nnn.nnn.nnn, where nnn is a decimal *SAME: The value does not change.
number ranging from 0 through 255. An
*SNMPATR: The value defined with the
internet address is not valid if it has a value of
Change SNMP Attributes (CHGSNMPA)
all binary ones or all binary zeros for the
command is used for this community.
network identifier (ID) portion or the host ID
portion of the address. If the internet address *YES: Set requests are logged.
is entered from a command line, the address *NO: Set requests are not logged.
must be enclosed in apostrophes. Up to 300
unique internet addresses may be specified. LOGGET
The same internet address may appear in Specifies whether get requests and get-next
more than one community profile. requests from SNMP managers in this com-
munity are logged in journal QSNMP in library
OBJACC QUSRSYS.
Specifies the object access for the community.
*SAME: The value does not change.
*SAME: The value does not change.
*SNMPATR: The value defined with the
*SNMPATR: The object access defined with Change SNMP Attributes (CHGSNMPA)
the Change SNMP Attributes (CHGSNMPA) command is used for this community.
command is used for this community.
*YES: Get requests and get-next requests
*READ: Allow SNMP managers that are part are logged.
of this community to read all management
information base (MIB) objects. Modification *NO: Get requests and get-next requests are
of MIB objects by SNMP managers is not per- not logged.
mitted.
*WRITE: Allow SNMP managers that are part Example
of this community to change all MIB objects CHGCOMSNMP COM(ENDICOTT) INTNETADR(\ANY)
that can be changed. Specifying *WRITE OBJACC(\READ)
implies *READ access.
This command changes community ENDICOTT to
*NONE: Do not allow SNMP managers that have an object access of read and to allow any
are part of this community to access any MIB SNMP manager to read the MIB objects on this
objects. system. All of the other community values are
LOGSET unchanged.
Specifies whether Set requests from SNMP
managers in this community are logged in
journal QSNMP in library QUSRSYS.
55──CHGSNMPA──┬────────────────────────────────────┬──┬─────────────────────────────────┬────────────────5
│ ┌─\SAME──────────┐ │ │ ┌─\SAME───────────┐ │
└─SYSCONTACT(──┼─\NONE──────────┼──)─┘ └─SYSLOC(──┼─\NONE───────────┼──)─┘
├─\CNTINF────────┤ ├─\CNTINF─────────┤
└─system-contact─┘ └─system-location─┘
5──┬──────────────────────────┬──┬──────────────────────────┬──┬────────────────────────┬────────────────5
│ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │ │ ┌─\SAME──┐ │
└─SNDAUTTRP(──┼─\YES──┼──)─┘ └─AUTOSTART(──┼─\YES──┼──)─┘ └─OBJACC(──┼─\READ──┼──)─┘
└─\NO───┘ └─\NO───┘ ├─\WRITE─┤
└─\NONE──┘
5──┬───────────────────────┬──┬───────────────────────┬──┬───────────────────────┬───────────────────────5
│ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │ │ ┌─\SAME─┐ │
└─LOGSET(──┼─\YES──┼──)─┘ └─LOGGET(──┼─\YES──┼──)─┘ └─LOGTRP(──┼─\YES──┼──)─┘
└─\NO───┘ └─\NO───┘ └─\NO───┘
5──┬────────────────────────────────────────────────────────────────────────────────────┬───────────────5%
│ ┌─\SAME──────────────────────────────────────────────────────────────┐ │
└─TRPMGR(──┼─\NONE──────────────────────────────────────────────────────────────┼──)─┘
│ ┌──
────────────────────────────────────────────────────────────────┐ │
└──6─(──manager-internet-address──community-name──┬──────────┬──)───
(1)
┴─┘
│ ┌─\YES─┐ │
└─┴─\NO──┴─┘
Note:
1 A maximum of 300 repetitions.
Purpose SYSCONTACT
Specifies the name of the contact person for
The Change SNMP Attributes (CHGSNMPA) this AS/400 system, along with information on
command changes values and options used by how to contact this person. This value is used
the OS/400 SNMP agent. The command also is only by SNMP-specific functions. This value
used to specify which SNMP managers receive also may be read or modified by an author-
traps generated by the local AS/400 system. ized SNMP manager.
*SAME: The value does not change.
The SNMP agent is shipped with the following
values for the SNMP attributes. *NONE: No system contact exists.
Keyword Value *CNTINF: The value is obtained from the
service contact information specified by using
SYSCONTACT *NONE
the Work with Contact Information
SYSLOC *NONE (WRKCNTINF) command. The value obtained
consists of the contact person and the contact
SNDAUTTRP *YES
telephone numbers.
AUTOSTART *NO
system-contact: Specify the name of the
OBJACC *READ contact person and other contact information.
LOGSET *NO All of the characters specified must be able to
be translated into the ASCII character set.
LOGGET *NO
SYSLOC
LOGTRP *NO Specifies the physical location of this AS/400
TRPMGR *NONE system. This value is used only by
SNMP-specific functions. This value also may
be read or modified by an authorized SNMP
Optional Parameters manager.
*SAME: The value does not change. *WRITE: Allow SNMP managers that are part
of a community to modify all MIB objects that
*NONE: No system location information
can be modified. Specifying *WRITE implies
exists.
*READ access.
*CNTINF: The value is obtained from the
*NONE: Do not allow SNMP managers that
service contact information specified by using
are part of a community to modify any MIB
the Work with Contact Information
objects.
(WRKCNTINF) command. The value obtained
consists of the mailing address. LOGSET
system-location: Specify the physical location Specifies the default value for whether set
of the system. All of the characters specified requests from SNMP managers in a commu-
must be able to be translated into the ASCII nity are logged in journal QSNMP in library
character set. QUSRSYS.
*SAME: The value does not change.
SNDAUTTRP
Specifies whether the SNMP agent may send *YES: Set requests are logged.
any authenticationFailure traps to any defined
*NO: Set requests are not logged.
SNMP managers. An authenticationFailure
trap is sent by the SNMP agent if a request is LOGGET
received from an SNMP manager that con- Specifies the default value for whether get
tains a community name that is not recog- requests and get-next requests from SNMP
nized by the SNMP agent. This trap is only managers in a community are logged in
sent when SNDAUTTRP is *YES and when at journal QSNMP in library QUSRSYS.
least one trap manager has been defined.
*SAME: The value does not change.
This value may also be read or modified by an
authorized SNMP manager. *YES: Get requests and get-next requests
are logged.
*SAME: The value does not change.
*NO: Get requests and get-next requests are
*YES: authenticationFailure traps may be
not logged.
sent.
*NO: authenticationFailure traps are not sent. LOGTRP
Specifies whether traps are logged in journal
AUTOSTART QSNMP in library QUSRSYS.
Specifies whether the SNMP agent is started
*SAME: The value does not change.
when the STRTCP command runs.
*YES: Traps are logged.
*SAME: The value does not change.
*NO: Traps are not logged.
*YES: The SNMP agent is started when the
STRTCP command runs. TRPMGR
*NO: The SNMP agent is not started when Specifies which SNMP managers receive
the STRTCP command runs. traps generated by this AS/400 system.
*SAME: The value does not change.
OBJACC
Specifies the default object access for SNMP *NONE: No SNMP managers receive traps.
communities.
Element 1: Manager Internet Address
*SAME: The value does not change.
manager-internet-address: Specify the
*READ: Allow SNMP managers that are part internet address of the SNMP manager. The
of a community to read all management infor- address must be of the form nnn.nnn.nnn.nnn,
mation base (MIB) objects. Modification of where nnn is a decimal number ranging from
MIB objects by SNMP managers is not per- 0 to 255. This address is independent of the
mitted. manager internet address specified on the
ADDCOMSNMP and CHGCOMSNMP com-
mands.
│ ┌─\ALL─────────────┐ │
│ │ ┌──
───────────┐ │ │
└─SERVER(──┴──6┬─\SNMP───┬┴───
(1) ─┴──)─┘
├─\TELNET─┤
├─\FTP────┤
├─\SMTP───┤
└─\LPD────┘
Notes:
1 A maximum of 5 repetitions.
55──ENDTRPMGR───────────────────────────────────────────────────────────────────────────────────────────5%
Purpose
The End Trap Manager (ENDTRPMGR) command
allows you to end the OS/400 SNMP Manager
Framework trap manager job.
│ ┌─\ALL─────────────┐ │
│ │ ┌──
───────────┐ │ │
└─SERVER(──┴──6┬─\SNMP───┬┴───
(1) ─┴──)─┘
├─\TELNET─┤
├─\FTP────┤
├─\SMTP───┤
└─\LPD────┘
Notes:
1 A maximum of 5 repetitions.
*ALL: All of the TCP/IP application servers *LPD: The line printer daemon (LPD) servers
are started. are started based on the number of servers
configured with the Change LPD Attributes
*SNMP: The Simple Network Management (CHGLPDA) command. Subsequent usage of
Protocol (SNMP) agent jobs are started. Sub- the STRTCPSVR SERVER(*LPD) command
sequent usage of the STRTCPSVR starts one additional LPD server.
SERVER(*SNMP) command results in a diag-
nostic message if the SNMP server jobs have Note: LPD works most efficiently when two
already been started. or more servers are running. Running
only one server works, but no jobs can
be received while a current job is example is also true for other TCP/IP application
running. If a large print job is running, servers.
new jobs have to wait before LPD is
ready to accept any new line printer Where appropriate, the number of servers to start
requester (LPR) requests. is based on the number of servers configured for
the server being started. The configuration option
to automatically start the servers (AUTOSTART) is
Examples ignored by the STRTCPSVR command. The
AUTOSTART parameter is used only by the
Example 1: Starting all TCP/IP Servers STRTCP command.
STRTCPSVR
Example 2: Starting the TELNET Server
This command starts all of the TCP/IP application STRTCPSVR SERVER(\TELNET)
servers that have been configured to be started.
For example: If the Change FTP Attributes This command starts the TCP/IP TELNET applica-
(CHGFTPA) command had previously been used tion server. If the TELNET server had been previ-
to configure two FTP servers, both servers would ously started, one additional TELNET server job
be started when STRTCPSVR is issued. This would be started.
55──STRTRPMGR──┬──────────────────────┬─────────────────────────────────────────────────────────────────5%
│ ┌─\NO──┐ │
└─FWDTRP(──┴─\YES─┴──)─┘
(P) ─┬────────────────────────┬──────────────────────────────────5%
55──RMVCOMSNMP──COM(──community-name──)────
│ ┌─\YES─┐ │
└─ASCIICOM(──┴─\NO──┴──)─┘
Note:
P All parameters preceding this point can be specified in positional form.
Purpose ASCIICOM
Specifies whether the community name is
The Remove Community for SNMP translated to ASCII characters before it is
(RMVCOMSNMP) command is used to remove a compared with the community name specified
Simple Network Management Protocol (SNMP) in a request from an SNMP manager. This
community profile from the SNMP agent commu- parameter is used in combination with the
nity list. The community profile consists of a com- community name to determine the community
munity name, an object access specification, and to be removed. If two communities have the
a list of the SNMP managers that are part of the same name and you don't specify the
community. The combination of the community ASCIICOM parameter, the community with
name (COM) and the translate to ASCII commu- ASCIICOM set to *YES is removed.
nity (ASCIICOM) parameters defines a community. *YES: The community name is translated to
ASCII characters before it is compared with a
Required Parameter community name specified by an SNMP
manager.
COM
Specifies the name of the SNMP community *NO: The community name is not translated
being removed. The community must already to ASCII characters before it is compared with
exist in the SNMP agent community list. a community name specified by an SNMP
manager.
community-name: Specify the name of the
SNMP community being removed. The name
may contain characters that cannot be dis- Example
played. RMVCOMSNMP COM(ROCHESTER)
P S
parameters send authentication traps parameter 2-3
automatic start 2-3 server
log traps 2-3 TCP/IP (Transmission Control Protocol/Internet Pro-
logging requests 2-3 tocol)
object access 2-3 ending D-9
send authentication traps 2-3 starting D-11
system contact 2-2 SET processing 6-2
system location 2-3 set processing, SNMP agent A-1
trap manager 2-3 Simple Network Management Protocol (SNMP)
pre-configured community attributes 2-4 See SNMP (Simple Network Management Protocol)
problem analysis C-1 SNA reference books, list H-2
agent C-1 SNMP
manager APIs C-4 reference books, list H-2
subagent APIs C-6 SNMP (Simple Network Management Protocol)
trap manager C-5 add community for D-1
processing agent attributes 2-2
GET 6-1 agent problem analysis C-1
GETNEXT 6-3 agent set processing A-1
SET 6-2 agent, communicating with subagent 6-6
programming concepts, subagent 6-1 agent, configuring 2-1
agent, definition 1-1
agent, waiting for work 6-7
Q agents 5-1
QAZCADEV database format 4-2
attribute
QAZCADIR database format 4-2
changing D-6
QAZCADRL database format 4-3
community for
QAZCADSK database format 4-2
changing D-4
QAZCAFS database format 4-2
DPI API source files 5-1
QAZCAMSC database format 4-2
manager enablement 3-1
QAZCANET database format 4-3
manager list 2-2
QAZCAPRC database format 4-3
manager problem analysis C-4
QAZCAPRT database format 4-3
manager, definition 1-1
QAZCAPTN database format 4-3
MIBs, supported A-1
QAZCASFW database format 4-4
problem analysis C-1
QAZCASFX database format 4-4
protocol elements, supported 1-2
Index X-3
SNMP (Simple Network Management Protocol) (con-
tinued) U
protocol operations 1-3 UDP (User Datagram Protocol) 1-3
remove community D-14 UNREGISTER request 6-5
subagent MIB, description A-6 User Datagram Protocol
subagent problem analysis C-6 See UDP
subagent, communicating with agent 6-6
subagents 5-1
TCP/IP (Transmission Control Protocol/Internet Pro-
V
Virtual Telecommunications Access
tocol)
Method/Network Control Program (VTAM/NCP)
configuring D-3
reference books, list H-1
trap manager problem analysis C-5
VTAM/NCP (Virtual Telecommunications Access
trap support 3-1
Method/Network Control Program)
software management database formats, client 4-1
reference books, list H-1
source files, SNMP DPI API 5-1
start parameter, automatic 2-3
Start TCP Server (STRTCPSVR) command 2-4 W
Start Trap Manager (STRTRPMGR) command 3-1 waiting for work, SNMP agent 6-7
STRTCPSVR (Start TCP Server) 2-4
STRTRPMGR (Start Trap Manager) 3-1
subagent
communicating with agent 6-6
problem analysis C-6
subagent MIB, description A-6
subagent programming concepts 6-1
subagents, relationship with agent 5-1
supported protocol elements 1-2
supported SNMP MIBs A-1
system contact parameter 2-2
system location parameter 2-3
T
TCP/IP (Transmission Control Protocol/Internet Pro-
tocol)
server
ending D-9
starting D-11
SNMP (Simple Network Management Protocol)
configuring D-3
Token Ring MIB, description A-3
Transmission Control Protocol/Internet Protocol
(TCP/IP)
See TCP/IP (Transmission Control Protocol/Internet
Protocol)
trap manager
ending D-10
problem analysis C-5
starting 3-1, D-13
stoping 3-1
trap manager parameter 2-3
TRAP request 6-6
trap router 3-1
trap support, SNMP 3-1
Very
Very Dissatis-
Satisfied Dissatis-
Satisfied fied
fied
Overall satisfaction
How satisfied are you that the information in this manual is:
Accurate
Complete
Easy to find
Easy to understand
Well organized
Applicable to your tasks
THANK YOU!
Note that IBM may use or distribute the responses to this form without obligation.
Name Address
Company or Organization
Phone No.
Cut or Fold
Reader Comments—We'd Like to Hear from You!
IBM
Along Line
SC41-5412-00
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
Cut or Fold
SC41-5412-00 Along Line
IBM
SC41-5412-ðð
Spine information: