IBM Support

PQ71075: SNMP AGENT ALWAYS SETS VALUE OF IFADMINSTATUS TO THE VALUE OF IFOPERSTATUS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • The SNMP ifAdminStatus MIB object is supposed to represent
    the desired state of an interface. The ifOperStatus MIB object
    is supposed to represent the actual state of an interface.  If
    a user requests that an interface be started then the
    ifAdminStatus MIB object should be set to up(1).  If the
    interface starts successfully, then ifOperStatus will be set
    to up(1) also.  If the interface doesn't start successfully,
    then ifOperStatus will probably be set to down(2).  Currently,
    the ifAdminStatus MIB object for an interface is always set
    to the same value as the ifOperStatus MIB object so, if
    ifOperStatus is down(2), a management application can not
    determine whether the interface was ever started or not.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the Communications Server       *
    *                 for z/OS Version 1 Release 2 & 4 IP:         *
    *                 SNMP                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: SNMP AGENT always sets the value of     *
    *                      IFADMINSTATUS to the value of           *
    *                      IFOPERSTATUS The SNMP ifAdminStatus MIB *
    *                      object is supposed to represent the     *
    *                      desired state of an interface. The      *
    *                      ifOperStatus MIB object is supposed to  *
    *                      represent the actual state of an        *
    *                      interface. If a user requests that an   *
    *                      interface be started then the           *
    *                      ifAdminStatus MIB object should be set  *
    *                      to up(1). If the interface starts       *
    *                      successfully, then ifOperStatus will be *
    *                      set to up(1) also. If the interface     *
    *                      doesn't start successfully, then        *
    *                      ifOperStatus will probably be set to    *
    *                      down(2). Currently, the ifAdminStatus   *
    *                      MIB object for an interface is always   *
    *                      set to the same value as the            *
    *                      ifOperStatus MIB object so, if          *
    *                      ifOperStatus is down(2), a management   *
    *                      application can not determine whether   *
    *                      the interface was ever started or not.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The ifAdminStatus MIB object for an interface is always set to
    the same value as the ifOperStatus MIB object. If ifOperStatus
    is down, a management application can not determine whether the
    interface was ever started or not.
    +-------------------------------------------------------------+
    + 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

Temporary fix

Comments

  • The implementation of ifAdminStatus will be changed to reflect
    more useful and accurate information.
    
    This APAR is being closed FIN (Fixed If Next) with concurrence
    from the submitting customer. This means that a fix to this
    APAR is expected to be delivered from IBM in a release (if any)
    to be available within the next 18 months.
    
    This problem will be tracked as PTR MV27787 by Communications
    Server for OS/390 Development.
    
    PTR27787   PTR 27787
    

APAR Information

  • APAR number

    PQ71075

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    120

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2003-02-17

  • Closed date

    2003-02-24

  • Last modified date

    2003-02-24

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

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

Fix information

Applicable component levels

  • R120 PSN

       UP

  • R129 PSN

       UP

  • R140 PSN

       UP

  • R149 PSN

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"120","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"120","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
24 February 2003