This section provides information about configuring stations that will host CLM software.

When using the RHEL server OS, ext4 is the required file system for all application specific mount points. No other file systems are supported with CLM. OS specific mount points can be either xfs or ext4 as the file system. Windows based clients must use a local file system for client files. Network based files systems, including Samba are not supported.

While Nokia identifies areas of the storage that are not specifically required for CLM and are partitionable for customer use, station resources are expected to be dedicated for CLM. As such, these “Remainder” portions of the storage should only be used for static storage purposes. Consideration should also be made to the expected growth of the network. If the “Remainder” is not to be used, then it should not be created.

In CLM upgrade scenarios, previous disk configurations may still be valid.

When using CLM on a guest operating system of a hosted virtualized installation, specific storage requirements must be met. For optimal performance, storage should be either internal disks (10K or 15K RPM SAS, SAS or NVMe based SSDs), Fiber Channel attached storage (array) with dedicated fiber channel connections between hosts and Storage Arrays, or 10Gb iSCSI using non-shared infrastructure. In VMware environments, storage I/O shares must be set to “High” and IOPs set to “Unlimited” for best performance and low latency.

To verify disk performance for CLM, see To test CLM disk performance for the minimum required throughput and latency for a collocated CLM configuration.