IT47352: CCD/CCM IN ACCURATELY RECOGNIZING AND MANAGING NODES WHEN THEIR IP/DNS ADDRESSES CHANGE, PARTICULARLY IN CLUSTERED OR DR SETUP

APAR status

• Closed as program error.

Error description

• The Control Centre Director (CCD) and Control Centre Monitor
  (CCM) face challenges in accurately recognizing and managing
  nodes when their IP/DNS addresses change, particularly in
  clustered or disaster recovery (DR) environments and when using
  virtual IPs/load balancers. These nodes are added as new
  servers.
  
  
  Mentioned scenarios when such issues was observed.
  
  Scenario 1: Cluster or Disaster Recovery Site Movement Nodes are
  often defined in the Control Centre Director (CCD) using DNS
  alias addresses, which allows them to change IP/DNS addresses
  when moving within a cluster or to a disaster recovery (DR)
  site. While the CCD and Control Centre Monitor (CCM) can access
  and view these nodes using their DNS aliases, issues arise when
  the InstallAgent on the server connects back to CCD. CCD may
  detect a different IP/DNS address and treat the connection as a
  new, separate node, leading to duplicate entries. This can cause
  discrepancies in node status, such as showing the server as
  active while its agent status appears inactive, or vice versa.
  CCD struggles to recognize that these are the same nodes,
  complicating node management.
  
  Scenario 2: Virtual IP Address/Load Balancer In environments
  using virtual IPs or load balancers, multiple nodes may share
  the same logical name (e.g., CD.WN.STNGSSTEST). When defined in
  CCM, separate node names must be used (e.g., CD.WN.STNGSSTEST_1
  and CD.WN.STNGSSTEST_2). This results in CCD learning multiple
  instances of the same node, albeit with different DNS addresses.
  Additionally, when a server connects back to CCD using its real
  IP address instead of the virtual IP/load balancer, CCD may
  treat this as a different connection, causing it to interpret
  the node as separate. This misinterpretation further complicates
  node status and management.
  

Local fix

• STRRTC - MFT-16326
  NC / AK
  Circumvention: None
  

Problem summary

• Control Centre Director duplicate CD node
  

Problem conclusion

• Added InstanceID for duplicate CD node getting created on CC
  when discovered via OSA fix
  

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

  STR CONTROL CEN

• Fixed component ID

  5725D0200

Applicable component levels