IV11339: UA SNMP LOCAL NETWORK DISCOVERY LIMITED TO SINGLE CLASS C ADDR

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)

APAR status

• Closed as program error.

Error description

• Approver:BEH
  
  Environment:
  Include components involved, platforms with versions/patches
  for each.
  Do you think the latest patch applied is involved?
  
  Problem Description:
  Expand on the APAR abstract since abstract length is limited.
  Indicate expected results and actual observed results.
  Provide as much detail as needed rather than referencing the
  PMR.
  Explain what activity was taken that caused the observed
  action
  (ie: change in a variable, entry in log or trace files,
  pop-up, etc.)
  
  Detailed Recreation Procedure:
  Provide a detailed step-by-step recreation procedure.
  Related Files and Output:
  Indicate log location, trace levels used, command output,
  configuration files, coredumps, etc.
  

Local fix

Problem summary

• SNMP local network discovery limited to single Class C address.
  
  SNMP local network discovery limited to single Class C address.
  Often the subnet mask setting for a host's interface (IP
  Address) is 255.255.255.0, a Class C subnet mask.  For this
  case, Universal Agent correctly handles the 'discovery' of each
  IP address that falls in address range defined from ANDing the
  subnet mask value against the host's IP address which results in
  deriving the Network Address.
  
  Given an example of a host IP address of 9.49.210.134 and a
  subnet mask of 255.255.255.0 the resultant Network Address is
  9.49.210 and the subnet range (number of nodes) is 255.  This
  case has always worked correctly.
  
  Given the same host IP address of 9.49.210.134 and a subnet mask
  of 255.255.254.000 the resultant Network Address is still
  9.49.210.0.  However, the computed subnet range (number of
  nodes) is 511 in this case where the range of IP addresses
  included in this subnet is 9.49.210.1 through 9.49.211.255 .
  For this case, again Universal Agent correctly finds and
  monitors IP addresses in range from 9.49.210.1 through
  9.49.210.255.   However, for the additional IP addresses of
  9.49.211.0 through 9.49.211.255 Universal Agent fails to
  correctly monitor these addresses that do not have a active SNMP
  Agent running at the IP address.
  

Problem conclusion

• The failure to correctly monitor IP addresses that are outside
  of the derived Network Address.  This was due to logic that used
  the same Network Address being compared to each Node Address,
  thus when a Node Address that is in the subnet's range does not
  match the Network Address the Node Address was being perceived
  as Unknown.  So in the above example,  Node Address 9.49.210.255
  is in subnet range and the Network Address of 9.49.210 match
  left most octets of Node Address so all is well.  Yet for Node
  Address 9.49.211.0, which is in the subnet range per the subnet
  mask of 255.255.254.000,  the Network Address of 9.49.210 was
  not matching left most octets of Node Address 9.49.211.0.
  
  Logic was changed so that when Network Address part of a Node
  Address 'changes' the Network Address value to 'match' against
  is updated to this new value per the Node Address.  So fo case
  of Node Address 9.49.211.0 being presented and currrent Network
  Address to check against is 9.49.210, Universal Agent now
  detects this 'change' and updates Network Address to 9.49.211 to
  'match' Node Addresses against.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
      | fix pack | 6.2.2-TIV-ITM-FP0008
      | fix pack | 6.2.3-TIV-ITM-FP0002
  

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:

Fix information

• Fixed component name

  UNIVERSAL AGENT

• Fixed component ID

  5724K1000

Applicable component levels

• R622 PSY

     UP