Administrator’s Command Line Guide
Table Of Contents
- Introduction
- Accessing Acronis Storage Clusters via iSCSI
- Preparing to Work with Acronis Storage iSCSI Targets
- Creating and Running Acronis Storage iSCSI Targets
- Listing Acronis Storage iSCSI Targets
- Transferring Acronis Storage iSCSI Targets Between Acronis Storage Nodes
- Stopping Acronis Storage iSCSI Targets
- Deleting Acronis Storage iSCSI Targets
- Configuring Multipath I/O for Acronis Storage iSCSI Targets
- Managing CHAP Accounts for Acronis Storage iSCSI Targets
- Managing LUN Snapshots
- Accessing Acronis Storage Clusters via S3 Protocol
- Monitoring Acronis Storage Clusters
- Managing Cluster Security
- Maximizing Cluster Performance
Chapter 5. Managing Cluster Security
2. You add new MDS servers, chunk servers, or clients to the cluster and use the vstorage auth-node command
to authenticate them. During authentication, you use the password you set when creating the first MDS
server.
3. Acronis Storage compares the provided password with the one stored on the first MDS server, and if the
passwords match, successfully authenticates the server.
For each physical server, authentication is a one-time process. Once a server is authenticated in the cluster (for
example, when you configure it as an MDS server), the /etc/vstorage/clusters/stor1/auth_digest.key file is created on
the authenticated server. When you set up this server as another cluster component (e.g., as a chunk server),
the cluster checks that the auth_digest.key file is present and does not require you to authenticate the server
again.
62