Choose this option to configure CIS as a single node or a NCS (Novell Cluster Services) cluster resource.
Before you start with CIS configuration, ensure that the database and infrastructure services (in cluster mode) are configured.
Ensure that the cluster resource host name or IP address is reserved for the cluster configuration.
For CIS server to function in a cluster environment, ensure that all nodes are configured with OES 23.4. Novell Cluster Services must be installed and running on the servers that have CIS installed. For information, see Installing, Configuring, and Repairing Novell Cluster Services
in the OES Cluster Services for Linux Administration Guide
.
Configuration Location: Specify the following:
Configure CIS as a NCS cluster resource: Configures CIS in a cluster environment. By default, this option is enabled.
Hostname / IP address: Specify the server address for standalone and resource or virtual IP address or hostname of the NCS cluster resource where the CIS server is part of.
Configuration Path: Specify the NSS media path to store CIS configuration files and log files. For example, /media/nss/CISVOL1.
If /media/nss/CISVOL1 is a cluster volume, then you need to modify the resource to update the Load and Unload script with CIS service. For more information about the scripts, refer to the “Configure CIS Services” in the “Cloud Integrated Storage Administration guide”.
Database: Specify the following:
Select either
or database.Specify the database host name or IP address and port. By default, the database port for MariaDB is 3306 and MS SQL is 1433.
Specify the user name and password for the database.
Connection Parameters: If your MS SQL is configured with connection parameters, specify the value.This is not a mandatory field.
Use secure connection: Enables or disables the database connection to be secure. By default, this option is disabled.
If
database is selected, specify the following:NOTE:Ensure to copy MariaDB client certificates to the CIS server.
Client CA Certificate file path: Specify the path of client Certificate Authority (CA) file in .pem format.
Client Certificate file path: Specify the path of the client certificate file in .pem format.
Client Key file path: Specify the path of the key file associated with the client certificate in .pem format.
Docker Network Setting: The default CIS docker subnet is 172.16.0.0/16. If the default CIS docker subnet conflicts with your current network, modify the subnet address.
For example: 192.168.0.0/16 or 10.0.0.0/16
Infrastructure Server Host name / IP address: Specify the host name or IP address of all the configured Infrastructure server HA nodes. Separate multiple entries with a comma.
Click
. If there are errors, ensure to resolve them before you proceed.CIS Admin Name with Context: Specify the LDAP distinguished name (DN) of the user who administers the CIS server. For example, cn=admin,o=acme.
Admin Password: Specify the password for the CIS administrator.
Agent Search Context: Specify the LDAP distinguished name (DN) of the container object under which the NCP server objects of the OES server resides that connects to the CIS server. The OES server includes the agents that connects to the CIS server. The CIS admin user must have supervisory rights on this server context.
Click
. Review the configuration summary and then click . This configures CIS in the 1st node in the cluster.On configuring the CIS services, the servercert.pem and serverkey.pem are copied to /etc/opt/novell/cis_prefixes/letc_cis/certs location. The servercert.pem is configured with the hostname and IP address of the cluster node.
For CIS server to function as a cluster resource, you must replace it with the newly created servercert.pem file. For creating this certificate file, refer to the CIS Administration guide.
Modify the Load, Unload and Monitor script. For more information about the scripts, refer to the “Configure CIS Services” in the “Cloud Integrated Storage Administration guide”.
To add a new node to this cluster:
Ensure that the CIS pattern is installed and updated with the latest patches.
Ensure this node is part of the same cluster.
Migrate the CIS resource to the new node.
For trademark and copyright information, see Legal Notices.