Run dxuldmcenteraping:

dxuldmcenteraping -a centeraIP?pathtopea where:

• centeraIP is one of the IP addresses on the EMC Centera, in IPv4 format.

• pathtopea is the full path to the PEA file.

Note:This command verifies that the PEA file may be used to access the EMC Centera. It does not check whether the correct permissions are provided by the PEA file.

For more information about dxuldmcenteraping, see

“dxuldmcenteraping” on page 182.

Centera pool entry authorization for replication

The PEA process may be used with Centera replication as a way to authenticate FSM on both the primary and replication EMC Centeras.

The PEA file used in a replication environment must provide authentication information for each of the EMC Centeras.

The composition of a PEA file used in a replication environment depends on whether you provide the path to a random-bit file when you run the profile create or profile update commands. The

random-bit file can be used as additional input during key generation.

The following methods may be used:

◆ Generate the key by providing a random-bit file.

The same file must be used on each EMC Centera. This method creates a PEA file with a single key that is accepted on each EMC Centera.

◆ Generate the key without providing a random-bit file.

A different key is created on each EMC Centera based on various machine-based values. Each key must be copied into the PEA file.

This creates a PEA file with several keys, one for each EMC Centera.

Replication PEA file created with a random-bit file

To use a replication PEA file created with a random-bit file:

1. On the primary EMC Centera, create an application profile by using a random-bit file.

The application profile must grant Read, Write, and Exist rights.

In order to have the profile create or profile update commands output a PEA file, type yes when asked if a Pool Entry

Authorization should be created.

For more information about application profile creation, refer to the EMC Centera’s documentation.

2. On each replication system, create an application profile by using the same random-bit file.

The application profile on each replication system should use the same name as the one on the primary system. The profile should, at a minimum, grant Read and Exist rights.

3. Copy the PEA file created with the primary system from the CLI host to the FSM host.

4. As root, limit access to the PEA file:

chmod 600 /path/my.pea

where /path/my.pea is the full path of the PEA file.

5. For each file system that uses the Centera module, type the full path of the PEA file in the Authentication Path option.

This is described in“Configuring a file system” on page 57.

6. For each file system that uses the Centera module, type the IP address, in IPv4 format, for each available interface on each replication server in the Replication Server Addresses option.

This is described in“Configuring a file system” on page 57.

7. Verify access using the PEA file.

This task is described in“Verify PEA access” on page 48.

Replication PEA file created without the use of a random-bit file To use a replication PEA file created without the use of a random-bit file:

1. On the primary EMC Centera, create an application profile without using a random-bit file.

The application profile must grant Read, Write, and Exist rights.

In order to have the profile create or profile update commands output a PEA file, type yes when asked if a Pool Entry

Authorization should be created.

The EMC Centera’s documentation provides more information about application profile creation.

2. On each replication system, create an application profile without using a random-bit file.

The application profile on each replication system should use the same name as the one on the primary system. The profile should, at a minimum, grant Read and Exist rights.

3. Copy the key portion of the PEA file created with each replication system into the PEA file created with the primary system, as shown inExample 1 on page 50.

Example 1 Replication environment PEA file created without a random-bit file The primary EMC Centera PEA file without the key from a replication server looks like this:

<pea version="1.0.0">

The primary EMC Centera PEA file after adding the key from a replication server looks like this (added key is in bold font):

<pea version="1.0.0">

4. Copy the resulting PEA file from the CLI host to the FSM host.

5. As root, limit access to the PEA file:

chmod 600 /path/my.pea

where /path/my.pea is the full path of the PEA file.

6. For each file system that uses the Centera module, type the full path of the PEA file in the Authentication Path option.

This is described in“Configuring a file system” on page 57.

7. For each file system that uses the Centera module, type the IP address, in IPv4 format, for each available interface on each replication server in the Replication Server Addresses option.

This is described in“Configuring a file system” on page 57.

8. Verify access using the PEA file.

This task is described in“Verify PEA access” on page 48.

Enable EMC Centera data retention

Retention of data from a UTDM file system that is migrated to a EMC Centera is enabled by using the Retention Period or the Retention Class settings. However, unless EMC Centera data retention is enabled for the file system, these retention settings do not protect data in the file system.

To provide retention both on the back-end system and in the file system, mount the file system with the bckendreten mount option. For more information, see“EMC Centera data retention”

on page 110.

FTP module preliminary tasks

Use of the FTP module requires the following preliminary tasks:

◆ Ensure that the FSM host can establish a connection to the back-end server:

• FTP server (FTP Protocol set to Native FTP)

• FTPS server (FTP Protocol set to Native FTP)

◆ Create a username/password combination on the back-end server for the file system.

◆ Obtain the full path to the target directory.

◆ Ensure that the file system host can obtain local disk-like access to the back-end server.

Check connectivity Connectivity between the FSM host and the back-end server can be confirmed by using ping. Use the ping command with the same interface address or hostname that you will use in FTP Host.

To confirm connectivity:

1. Log in as root on the FSM host system.