PK87802: IOBSNMP REGISTERS ITS MIB WITH THE SNMP AGENT USING TOO LOW OF A TIMEOUT VALUE, CAUSING TIMEOUTS BETWEEN THE SUBAGENT AND AGENT.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• IOBSNMP registers its MIB with the SNMP agent using a three
  second timeout.  As a result, any delay in processing a request
  from the agent can result in a timeout between the subagent and
  agent.  This can cause SNMP to close the AF_UNIX socket used for
  DPI communication.
  
  This may manifest itself in multiple ways.  SNMP managers may no
  longer be able to query OSA related data.  In the IOBSNMP
  output, you may see one or both of the following messages:
  
    do_get06: Leaving do_get w/ rc --> -5
    rc not DPI_RC_OK from wait for packet->-7
  
  In the SNMP agent's output, you may see one or all of the
  following:
  
    EZZ6249I EOF received on DPI fd 6
    EZZ6229I Closing DPI UNIX socket connection, fd=6
    EZZ6253I send function failed; EDC5140I Broken pipe.
  

Local fix

• Use the following OSNMP SET commands in the Unix System Services
  shell to manually increase the timeout values for IOBSNMP's MIB:
  
    osnmp set saTtimeout.1.3.6.1.4.1.2.6.188.1.1.0 120
    osnmp set saTtimeout.1.3.6.1.4.1.2.6.188.1.3.0 120
    osnmp set saTtimeout.1.3.6.1.4.1.2.6.188.1.4.0 120
    osnmp set saTtimeout.1.3.6.1.4.1.2.6.188.1.8.0 120
  
  To issue these commands, SETs must be allowed in the SNMP
  environment.  Additionally, the community name can be added to
  the command using -c, and the host can be added using -h:
  
    osnmp -c community_name -h host_name set ...
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s) 11 IP:         *
  *                 OSA SNMP                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: IOBSNMP registers its MIB with the SNMP *
  *                      agent using too low of a timeout value, *
  *                      causing timeouts between the subagent   *
  *                      and agent.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  IOBSNMP registers its MIB with the SNMP agent using a three
  second timeout.  As a result, any delay in processing a request
  from the agent can result in a timeout between the subagent and
  agent.  This can cause SNMP to close the AF_UNIX socket used for
  DPI communication.
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

• Modules IOBSAMP and IOBGROUP have been modified to use a 20
  second timeout.
  
  * Cross Reference between External and Internal Names
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PK84262

• APAR is sysrouted TO one or more of the following:

  UK47530

Modules/Macros

• IOBGROUP IOBSAMP
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R1B0 PSY UK47530

     UP09/07/16 P F907

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.