It seems that that parameter did not exist in 1.5.x - so the "default", if you wish, would be "no."
In 10.6.x it defaults to "yes" - so if you upgrade your device from 10.5.x to 106.x it would slip from "no" to "yes" automatically, typically without a chance to notify you of that change in behaviour.
Now, of course, all depends on the peer(s) you are dealing with. Some may be sending that notification and regardless of your setting (or firmware version) all would be well.
If your peer(s), though, fail to send the notification or the session is dropped by mistake from time to time your 10. implementation wouldn't care, but your 10.6 implementation would log that error. If you reconfigure your TLS server profile, though, to set the parameter to "no" it should ignore the condition, just as the 10.5 implementation. If that doesn't happen I suggest you get back to IBM support, asking that question.
Gerd Diederichs
Original Message:
Sent: 10/27/2025 10:43:00 AM
From: John Parker
Subject: Anyone have an issue with the Require Closure Notification in 10.6.0.7?
Hi,
We just upgraded our development Datapower from 10.5.0.17 to 10.6.0.7 and we are getting a TLS error and we aren't able to reach the backend server.
IBM support said that it because we had Require Closure Notification turned on, so we turned it off and we still have the problem. It's happening intermittently, about ever1 1 in 3 or 4 times.
------------------------------
John Parker
------------------------------