IV97493: TADDM 7.3: BIGIP* SENSORS DO NOT START FOR ALL THE F5 BIG-IP LOAD BALANCER DEVICES (WHEN THEY GOT THE SAME MMS KEY)

APAR status

• Closed as program error.

Error description

• TADDM 7.3: BIGIP* sensors do not start for all the F5 Big-IP
  Load Balancer devices:
  ----------------------------------------------------------
  For supported Big-IP F5 devices only few Big-IP* sensors
  start in a scope.
  Actually it has been found out that it happens because TADDM
  uses currently MMS(= Manufacturer,Model,SerialNumber) key
  as the naming rule ,  but in case of  BigIP 12 or later
  serialNumber is not unique for the VMs.
  
  -> Because of this MMS key is same for all VMs and
  SNMPMib2Sensor is not able to launch the BipIP sensors.
  
  -> In the new implementation we will use:
       VMMS(= VMID,Manufacturer,Model,SerialNumber) key
  as naming rule, where we will use "sysNodeName" as VMID to
  uniquely identify all  the VMs;
  sysNodeName is extracted using the below OID :
             ".1.3.6.1.4.1.3375.2.1.6.2"
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * None                                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * For supported Big-IP F5 devices only few Big-IP* sensors     *
  * start in a scope.                                            *
  * On analysis, it was found that it happens because TADDM      *
  * currently uses MMS(= Manufacturer,Model,SerialNumber) key as *
  * the naming rule,  but in case of  BigIP 11.x or later        *
  * serialNumber is not unique for the VMs.                      *
  *                                                              *
  * Because of this MMS key is same for all VMs and              *
  * SNMPMib2Sensor is not able to launch the BipIP sensors.      *
  *                                                              *
  * In the new implementation the following key shall be used:   *
  *      VMMS(= VMID,Manufacturer,Model,SerialNumber) key        *
  * as naming rule, where we will use "sysNodeName" as VMID to   *
  * uniquely identify all  the VMs;                              *
  * sysNodeName is extracted using the below OID :               *
  *            ".1.3.6.1.4.1.3375.2.1.6.2"                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  packages:
  | Fix Pack | 7.3.0-TIV-ITADDM-FP0004
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• 999
  

Fix information

• Fixed component name

  APP DEPENDENCY

• Fixed component ID

  5724N5500

Applicable component levels

• R730 PSY

     UP