Infrastructure improvements
Ability to Send Logs to More than One Syslog Server
After enabling a Syslog server in the portal, you can add Syslog servers using the following CLI: portal-syslog-client add_syslog_server <ip> <port> <protocol> [name] [ca_cert] [client_cert] [client_key]
Required Parameters
ip – IP address of the syslog server
port – Port number of the syslog server
protocol – Protocol to use (UDP, TCP/TLS, or TCP/ClientCertAuth)
Optional Parameters
name – Unique identifier for the server (auto-generated if not provided).
ca_cert – CA certificate file (required for TLS).
client_cert – Cient certificate file (required for client authentication).
client_key – Client private key file (required for client authentication).
- You cannot add multiple servers with the same IP and port combination.
- If you add a server with a name that already exists, the existing server will be updated.
- All certificate files must exist and be readable. All certificates need to be placed under
/usr/local/lib/ctera/syslog/logstash/tls - The service automatically creates a new logstash pipeline configuration for each server.
Core Infrastructure Upgrades
Key infrastructure components have been upgraded including:
- The Tomcat server
- The JDK
- The Blocks table has been changed to include map files instead of having the map files stored as objects in the storage node.
Note
You cannot upgrade the portal while running a storage node migration.
FIPS 140-3 Validation
The portal now supports FIPS 140-3.
Global Administration
Global administrator features:
- New Look and Feel
- Backup to an S3 Bucket
- QumuloS3 Storage Node
- Devices Report
- New Email Templates
- Support for Bitdefender Antivirus
- Deprecated Features
Team Portal Administration
Team administrator features: