Symptom 2: Message KN3CT057 is found in the RKLVLOG

OSA workspaces contain no data and the RKLVLOG contains this message:

KN3CT057 OSA SNMP DATA COLLECTION TYPE=UNAVAILABLE, TCPIP=stack_name
This error is a data collector issue.

The z/OS® SNMP agent gets data about the OSA adapters on your system from either the OSA-Express Direct SNMP subagent (IOBSNMP), or the TCP/IP SNMP subagent that uses the OSA/SF application (IOAOSASF) and the OSA/SF sockets application (IOASNMP). If you see message KN3CT057 with a TYPE value of UNAVAILABLE, then the OSA SNMP subagent might not be started or might be configured incorrectly. See the IBM® Z OMEGAMON® AI for Networks: Planning and Configuration Guide, section “Starting the OSA adapter SNMP subagent,” for information on starting and configuring the OSA subagents.

The IOASNMP or the IOBSNMP OSA data collector must be running in every address space about which you want to collect OSA data.
  1. Issue this command from OMVS to determine what OSA agents and subagents are running: 
    osnmp -h hhhhhhh -c ccccccc walk sysordescr
    where hhhhhhh is the TCP/IP hostname or IP address and ccccccc is the community name. The sample command response that follows indicates that the IOBSNMP procedure was started and the OSA subagent is available: 
    1.3.6.1.2.1.1.9.1.3.1=z/OS SNMP Agent
1.3.6.1.2.1.1.9.1.3.2=OSA subagent
1.3.6.1.2.1.1.9.1.3.3=z/OS TCP/IP SNMP Subagent
1.3.6.1.2.1.1.9.1.3.4=z/OS OSPF SNMP Subagent
  2. Check the subagent status through the MIB by using either the Open Edition osnmp command or by using the IBM® Tivoli® NetView on z/OS MIB browser and issuing this command to see which subagents are defined in the MIB: 
    osnmp walk saDescription
    The output should look something like this: 
    1.3.6.1.4.1.2.4.12.7.1.3.1
1.3.6.1.4.1.2.4.12.7.1.3.3
    Where line 1 is the output for the z/OS TCP/IP SNMP subagent and line 2 is the output for the OSA subagent.
  3. Check the status of these subagents by issuing this command: 
    osnmp walk saStatus
    The output of this command should look something like this: 
    saStatus.1 = 1 
saStatus.3 = 1
    Valid subagent status values are the values that follow:
    • 1 = valid
    • 2 = invalid
    • 3 = connecting
    • 4 = disconnecting
    • 5 = closedByManager
    • 6 = closedByAgent
    • 7 = closedBySubagent
    • 8 = closedBySubAgentTimeout
    • 9 = closedBySubAgentError