CES SMB support
In GPFS™ 4.1.1 and later, you can access a GPFS file system with an SMB client using its inherent SMB semantics.
Clustered SMB support
SMB clients can connect to any of the protocol nodes and get access to the shares defined. A clustered registry makes sure that all nodes see the same configuration data. Therefore, clients can connect to any Cluster Export Services (CES) node and see the same data. Moreover, the state of opened files (share modes, open modes, access masks, locks, and so on) is also shared among the CES nodes so that data integrity is maintained. On failures, clients can reconnect to another protocol node and IP addresses are transferred to another protocol node
The supported protocol levels are SMB2 and the base functions of SMB3 (dialect negotiation, secure negotiation, encryption of data on the wire).
Export management command
With the mmsmb command, IBM Spectrum Scale™ provides a comprehensive entry point to manage all SMB-related configuration tasks like creating, changing, and deleting SMB shares.
SMB monitoring
The monitoring framework detects issue with the SMB services and triggers failover in case of an unrecoverable error.
Integrated installation
The SMB services are installed by the integrated installer together with the CES framework and the other protocols NFS and Object.
SMB performance metrics
The SMB services provide two sets of performance metrics that are collected by the performance monitor framework. Both current and historic data (with lower granularity) can be retrieved. The two sets of metrics are global SMB metrics (such as the number of connects and disconnects) and metrics for each SMB request (number, time, throughput). The mmperfmon query tool provides access to the most important SMB metrics via predefined queries. Moreover, metrics for the clustered file metadata database CTDB are collected and exposed via the mmperfmon query command.
Authentication and mapping
The SMB services can be configured to authenticate against the authentication services Microsoft Active Directory and LDAP. Mapping Microsoft security identifiers (SIDs) to the POSIX user and group IDs on the file server can either be done automatically by using the so-called autorid mechanism or external mapping services like RFC 2307 or Microsoft Services for Unix. If none of the offered authentication and mapping schemes matches the environmental requirements, a user-defined configuration can be established.