IJ50232: MMSDRCLI COMMAND FAILED TO EXPEL THE NODE WITH TLS HANDSHAKE ERR

APAR status

• Closed as program error.

Error description

• The client, as expected, sent the request and was
  processing the TLS authentication to complete.
  But on the server side, the  function did not get the
  payload it expected and immediately returned.
  

Local fix

Problem summary

• The automated node expel mechanism (see references to the
  mmhealthPendingRPCExpelThreshold configuration parameter) uses
  the internal
  mmsdrcli to issue an expel request to a node in the home
  cluster. If the
  sdrNotifyAuthEnabled configuration parameter is set to false
  (not recommended)
  then the command will fail with a message like the following:
  
  [W] The TLS handshake with node 192.168.132.151 failed with
  error 410 (client side).
  mmsdrcli: [err 144] Connection shut down
  
  and the expel request will fail.
  

Problem conclusion

• With the fix, the internal mmsdrcli command will no longer fail
  when invoked
  while the sdrNotifyAuthEnabled configuration parameter is set to
  false. The
  automated node expel will then work correctly.
  

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

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels