# VMS CLI Command to check TLS Version

**URL:** <https://community.vastdata.com/t/vms-cli-command-to-check-tls-version/1982>\
**Category:** Ask a Question\
**Created:** [May 28, 2026, 9:05pm UTC](https://community.vastdata.com/t/vms-cli-command-to-check-tls-version/1982 "2026-05-28T21:05:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![billhill](https://sea2.discourse-cdn.com/flex022/user_avatar/community.vastdata.com/billhill/32/1969_2.png) [@billhill](https://community.vastdata.com/u/billhill)\
**Post date:** [May 28, 2026, 9:05pm UTC](https://community.vastdata.com/t/vms-cli-command-to-check-tls-version/1982/1 "2026-05-28T21:05:53Z")

</div>

Hi All - There is a VMS CLI command to change the default minimum TLS version from 1.2 to 1.3 (Required for RPC over TLS). Is there a way to verify that change? What command can be used to verify 1.3?

From client you can run:

# Test TLS 1.2

openssl s\_client -connect \<[example.com](http://example.com) or cluster ipaddr\>:443 -tls1\_2

# Test TLS 1.3

openssl s\_client -connect \<[example.com](http://example.com) or cluster ipaddr\>:443 -tls1\_3

The response I am getting seems like 1.2 is still running and not 1.3.

Any help is appreciated!

---

<div class="post-metadata">

**Author:** ![ram](https://sea2.discourse-cdn.com/flex022/user_avatar/community.vastdata.com/ram/32/1605_2.png) [@ram](https://community.vastdata.com/u/ram)\
**Post date:** [June 1, 2026, 10:00pm UTC](https://community.vastdata.com/t/vms-cli-command-to-check-tls-version/1982/2 "2026-06-01T22:00:32Z")

</div>

Hi @billhill just checking with the team, will follow up soon.

---

<div class="post-metadata">

**Author:** ![ram](https://sea2.discourse-cdn.com/flex022/user_avatar/community.vastdata.com/ram/32/1605_2.png) [@ram](https://community.vastdata.com/u/ram)\
**Post date:** [June 9, 2026, 4:10pm UTC](https://community.vastdata.com/t/vms-cli-command-to-check-tls-version/1982/3 "2026-06-09T16:10:34Z")

</div>

@billhill still waiting to hear back, but I do not see a command to confirm the tls version only to [modify tls version](https://kb.vastdata.com/documentation/docs/vms-modify-2).

to clarify, running both commands for `# Test TLS 1.2` and `# Test TLS 1.3` works OR only 1.2 works?

Just taking a look, have you tried running something as follows:

`openssl s_client -connect <host>:443 -tls1_3 -tlsextdebug 2>&1 | grep -i "TLS"`

---

<div class="post-metadata">

**Author:** ![billhill](https://sea2.discourse-cdn.com/flex022/user_avatar/community.vastdata.com/billhill/32/1969_2.png) [@billhill](https://community.vastdata.com/u/billhill)\
**Post date:** [June 9, 2026, 4:56pm UTC](https://community.vastdata.com/t/vms-cli-command-to-check-tls-version/1982/4 "2026-06-09T16:56:35Z")

</div>

Hello @ram - Thank you for your help and response! I was able to get this working with the help of support. vtools was required to enable TLS 1.3. From there I was able to set default TLS to 1.3. Once this was accomplished, view policy that enforces TLS on NFS was created. Remaining steps were certificate creation and installing/configuring ktls-utils package on SLES.