Novell Doc: BCC 1.2: Administration Guide for OES 2 SP1 Linux

9.2 Adding Peer Cluster Credentials

Clusters must be able to authenticate to themselves and to peer clusters. In order for one cluster to connect to a second cluster, the first cluster must be able to authenticate to the second cluster. For each node, add the authentication credentials (username and password) of the user who the selected cluster will use to authenticate to a selected peer cluster.

IMPORTANT:In order to add or change peer cluster credentials, you must access iManager on a server that is in the same eDirectory tree as the cluster for which you are adding or changing peer credentials.

9.2.1 Using Console Commands to Add Credentials

To add peer cluster credentials, do the following for each node of every cluster in the business continuity cluster:

Open a terminal console on the cluster node where you want to add peer credentials, then log in as the root user.
At the terminal console prompt, enter
```
cluster connections
```
Verify that all clusters are present in the list.

If the clusters are not present, the Identity Manager drivers are not synchronized.

If synchronization is in progress, wait for it to complete, then try cluster connections again.

If you need to synchronize, see Synchronizing Identity Manager Drivers.
For each cluster in the list, enter the following command at the server console prompt, then enter the bccadmin username and password when prompted.
```
cluster credentials cluster_name
```
Repeat the following steps for every node in each cluster:
1. As the root user, open the /etc/group file in a text editor.
2. Locate the line that reads ncsgroup, then modify it to include the bccadmin user.
  
  For example, change
```
ncsgroup:!:107:
```
  to
```
ncsgroup:!:107:bccadmin
```
  For example, change
```
ncsgroup:!:107:bccd
```
  to
```
ncsgroup:!:107:bccd,bccadmin
```
  The file should contain one of the above lines, but not both.
  
  Notice the group ID number of the ncsgroup. In this example, the number 107 is used. This number can be different for each cluster node.
3. Save the /etc/group file.
4. At the server console prompt, enter the following to verify that the bccadmin user is member of the ncsgroup.
```
id bccadmin 
```

9.2.2 Using iManager to Add Credentials

You cannot use iManager on Linux to set eDirectory credentials for BCC. You must use iManager on NetWare® or Windows (the server must be in the same eDirectory tree), or use the Linux BCC command line interface from a console prompt to set credentials.

In the Connections section of the Business Continuity Cluster Properties page, select the peer cluster, then click Edit.

In order for a cluster to appear in the list of possible peer clusters, the cluster must have the following:
- Business Continuity Clustering software installed.
- Identity Manager installed.
- The BCC-specific Identity Manager drivers configured and running.
- Be enabled for business continuity.
Add the administrator username and password that the selected cluster will use to authenticate to the selected peer cluster.

When adding the administrator username, do not include the context for the user. For example, use bccadmin instead of bccadmin.prv.novell.

Rather than using the Admin user to administer your BCC, you should consider creating another user with sufficient rights to the appropriate contexts in your eDirectory tree to manage your BCC. For information, see Section 4.3, Configuring a BCC Administrator User and Group.
Repeat Step 1 and Step 2 for the other cluster that this cluster will migrate resources to.
Continue with Adding Search-and-Replace Values to the Resource Replacement Script.