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 number
IV97493
Reported component name
APP DEPENDENCY
Reported component ID
5724N5500
Reported release
730
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-28
Closed date
2017-11-24
Last modified date
2017-11-24
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
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"730","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
24 November 2017