Versa Messaging Service (VMS) Release Notes for Release 5.1
These release notes describe features, enhancements, and fixes in Versa Messaging Service (VMS) release 5.1, for Release 5.1.1.
Product Documentation
The Versa Networks product documentation is located at https://docs.versa-networks.com.
Install the VMS Application
To install the VMS software, download the application from this location. See Install VMS.
Upgrade to Release 5.1.1
Note that you must install a software image of Release 22.1.4 dated 2024-11-10 or later for VOS, Versa Director, and Versa Analytics for VMS 5.1.1 to function.
If you are using a VMS version earlier than Release 5.1.1, you must install a new VMS cluster (node). Until you upgrade all VOS nodes to Release 22.1.4, your VMS node with an earlier VMS release (unnumbered) and VMS node with Release 5.1.1 must be active.
Note that from VMS Release 5.1.1, VMS communicates with VOS nodes over port 1376.
To upgrade a VMS node running a release prior to 5.1.1:
- Install a VMS Release 5.1.1 control plane node. For more information, see Install VMS.
- Log in to the Versa Director UI.
- Add the control plane node that you installed in Step 1 as the first node of the VMS cluster to the Versa Director Connector. For more information, see Configure VMS from Versa Director.
- Add the tenant and the required service to the VMS cluster, which enables the service on the VMS cluster.
Configure Services in Release 5.1.1
To configure third-party authentication (in earlier VMS releases, this is called passive authentication):
- Upgrade the WMI agent to Release 11.4.8.
- From the Versa Director UI, enable and configure third-party authentication on your parent tenant. For more information, see Configure VMS from Versa Director.
- Make the following changes on your WMI agent:
- Configure the parent tenant on your WMI agent. The parent tenant can be the same as the child tenant in WMI. For more information, see Install and Configure the WMI Agent.
- Change the port number from 3092 to the standard HTTPS port (443) to connect to a VMS node running VMS Release 5.1.1.
- If firewall block rules are used, update these rules to connect to the VMS node running VMS Release 5.1.1.
- Add the new VMS server details and upload the certificate to the WMI agent.
- Enable the parent tenant on your WMI agent.
- If the WMI agent server interacts with VMS Release 5.1.1 as well as previous releases, you must upload the certificates for both releases.
Similarly, you can enable and configure SSE on SIM and XIP EIP services from the Tenants and Services screen in the Versa Director UI. For more information, see Configure VMS from Versa Director.
Release 5.1.1
Released July 19, 2024
New Features
- Support for multitenancy.
- Support for third-party authentication, XIP EIP, and SASE on SIM services. You can enable multiple VMS services on a VOS node, and a single VMS cluster can simultaneously host multiple services.
- Support service automatic scaling based on micro-service architecture of VMS, which allows scaling of containers.
- Support filtering of information using tags to send data to specific branches.
- Federal Information Processing Standards (FIPS) compliance.
- Process streamed data from external sources and convert it to a format for VOS devices. Then, stream to the VOS devices that subscribe to a service.
- Forward logs and exceptions to Versa Analytics nodes. VMS can also send data or logs to external components.
- Self-monitoring and healing capabilities after deployment. In multinode deployments, VMS handles node failure by moving service and infrastructure containers to a healthy node. In single node environments, VMS detects spike-based errors and heals by relaunching containers.
Request Technical Support
To request technical support, visit http://support.versa-networks.com. If you are contacting support for the first time, register and create an account. You can also send email to support@versa-networks.com or contact your Versa Networks sales account team.
Revision History
Revision 1—Release 5.1.1, July 19, 2024