OA41593: UNABLE TO MONITOR TCP/IP STACKS WITHOUT SNMP

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • AON Doc needs clarification.
    Examples from the v5r4 Administration Reference:
    1) Sections 4.2 ACTMON, 4.29 MONIT, and 4.35 RECOVERY all show
       the statement applies to IP Management and AON/TCP, but does
       not show that it also applies to SNA.
    2) Section 4.29 MONIT does not fully explain what the YF and NF
       mean (The 'F' means 'Forever') in the INTVL subsection.
    3) Section 4.39 TCP390
       - Defining tcpip-stack is confusing, not sure what to use
       - FORMAT only shows STACK, but PING and SNMP are also valid
         options.  Also explain which option does not use SNMP.
      - Some of the DEFAULTS are not defined: DEBUG, RPLENGTH
         and VERBOSE
       - The PARMS are not in alphabetical order, but seem to
         be in the order shown with statement options. Makes it
       difficult to find a specific parm.
    4) Need to expand explaination of how ACTMON and
       RECOVERY worked and what causes them to be involked.
       Explaination of what role MONIT and THRESHOLDS play in
       RECOVERY also needs to be expanded.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli NetView for z/OS users with the   *
    *                 AON.TCP or IPMGT tower enabled.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: The CNMPOLCY TCP390 ACTMON processing   *
    *                      requires SNMP to check stack status.    *
    *                      Also the ACTMON, MONIT, TCP390, and     *
    *                      RECOVERY statement descriptions in the  *
    *                      Administration Reference manual are     *
    *                      unclear.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    AON and IPMGT do not support stack status collection without the
    use of SNMP. Also, the descriptions of some policy statements in
    the NetView Administration Reference are unclear.
    

Problem conclusion

  • AON/IPMGT ACTMON processing is being changed to use the PING
    command to collect stack status for stacks defined on TCP390
    statements if the style sheet DISCOVERY.SNMP variable is set
    to 'NO'.
    The CNMPOLCY sample is being changed in the following ways:
    - the uncommented TCP390 DEFAULTS statement MAXCONN parameter is
      being replaced with PINGCNT=3.
    - the commented TCP390 DEFAULTS statement MAXCONN, DEBUG, and
      VERBOSE parameters are being removed.
    Also, the Tivoli NetView for z/OS Administration Reference
    manual (SC27-2869-02) in the Policy File Definitions chapter
    should be changed as follows:
    - Under the ACTMON policy statement, near the end of the first
      sentence, "AON/TCP" should be changed to "AON".
      The second paragraph should be changed to read as follows:
    "The ACTMON control file entry defines active monitoring policy
     for critical resources in the network. When a resource is being
     actively monitored, the NetView program sets a timer to check
     the status of the resource. If the resource is not active, the
     NetView program initiates failure processing (also known as
     recovery monitoring) and suspends active monitoring in favor of
     recovery monitoring. Once the resource becomes active, the
     NetView program will resume active monitoring."
    - Under the ACTMON policy statement, the SP keyword definition,
      add the following to the end of the first sentence, "or IP
      management".
    - Under the MONIT policy statement, the INTVL keyword
      explanation for the value "Y", add the following sentence:
    "Recovery monitoring will cease after the last interval
     specified."
    - Under the MONIT policy statement, the INTVL keyword
      explanation for the value "N", add the following sentence:
    "Recovery monitoring will cease after the last interval
     specified."
    - Under the MONIT policy statement, the INTVL keyword,
      explanation for the value "YF", change the explanation to read
      as follows:
    "Notify operators based on your NOMOMONS Notification Policy.
     Recovery monitoring will continue until the resource recovers
     or the control file is reloaded, using the last interval
     specified."
    - Under the MONIT policy statement, the INTVL keyword,
      explanation for the value "NF", change the explanation to read
      as follows:
    "Repeat recovery monitoring at the last interval specified until
     the resource recovers or the control file is reloaded, but do
     not call Notification Policy."
    - Under the TCP390 policy statement, the keywords should be
      alphabetized.
    - Under the TCP390 policy statement, the DEBUG keyword and
      values explanations should be added alphabetically as follows:
    "DEBUG= N | Y
         Only applies to AON/TCP option 2.5 (Issue SNMP Commands).
         This determines whether or not additional diagnostic
         information is provided when issuing SNMP commands. The
         default setting is N.
    
         N
             Indicates that no additional diagnostic information is
             provided.
    
         Y
             Indicates that additional diagnostic information is
             provided."
    - Under the TCP390 policy statement, the VERBOSE keyword and
      values explanations should be added alphabetically as follows:
    "VERBOSE= -Ovalue
         Only applies to AON/TCP option 2.5 (Issue SNMP Commands).
         Allows a user to specify output options for the SNMP
         commands.
    
         -Ovalue
             See the SNMP command help for the -O output option
             syntax and values."
    - Under the TCP390 policy statement, the MAXCONN keyword is
      obsolete and should be deleted.
    - Under the RECOVERY policy statement, the following paragraph
      should be inserted before the last paragragh preceding the
      RECOVERY syntax diagram:
    "RECOVERY monitoring is invoked by message automation and by
     active monitoring when it has been determined that a resource
     is not active.  The processing completes when the NetView
     program determines that the resource has recovered.  Before
     completion, recovery monitoring will check for ACTMON
     definitions and resume active monitoring when appropriate."
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA41593

  • Reported component name

    NETVIEW FOR Z/O

  • Reported component ID

    5697NV600

  • Reported release

    10B

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-01

  • Closed date

    2013-07-12

  • Last modified date

    2013-09-04

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

    OA41105

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

    UA69866

Modules/Macros

  •    CNMPOLCY FKXEACTT
    

Publications Referenced
SC27286902        

Fix information

  • Fixed component name

    NETVIEW FOR Z/O

  • Fixed component ID

    5697NV600

Applicable component levels

  • R10B PSY UA69866

       UP13/08/15 P F308

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

z/OS family

Software version:

10B

Reference #:

OA41593

Modified date:

2013-09-04

Translate my page

Machine Translation

Content navigation