Scroll to navigation

ipa-csreplica-manage(1) IPA Manual Pages ipa-csreplica-manage(1)

NAME

ipa-csreplica-manage - Manage an IPA CS replica

SYNOPSIS

ipa-csreplica-manage [OPTION]... [connect|disconnect|del|list|re-initialize|force-sync]

DESCRIPTION

Manages the CA replication agreements of an IPA server for domain at domain level 0.

To manage CA replication agreements in a domain at domain level 1, use IPA CLI or Web UI, see `ipa help topology` for additional information.

- Adds a new replication agreement between SERVER_A/localhost and SERVER_B. Applicable only at domain level 0.
- Removes a replication agreement between SERVER_A/localhost and SERVER_B. Applicable only at domain level 0.
- Removes all replication agreements and data about SERVER. Applicable only at domain level 0.

- Lists all the servers or the list of agreements of SERVER
- Forces a full re-initialization of the IPA CA server retrieving data from the server specified with the --from option
- Immediately flush any data to be replicated from a server specified with the --from option
- Set CA server which handles renewal of CA subsystem certificates to SERVER

OPTIONS

The IPA server to manage. The default is the machine on which the command is run Not honoured by the re-initialize command.
The Directory Manager password to use for authentication
Provide additional information
Ignore some types of errors
The server to pull the data from, used by the re-initialize and force-sync commands.

EXAMPLES


# ipa-csreplica-manage list srv1.example.com
srv2.example.com
srv3.example.com

# ipa-csreplica-manage re-initialize --from srv2.example.com

This will re-initialize the data on the server where you execute the command, retrieving the data from the srv2.example.com replica


# ipa-csreplica-manage connect srv2.example.com srv4.example.com

# ipa-csreplica-manage disconnect srv1.example.com srv3.example.com

# ipa-csreplica-manage del srv4.example.com

# ipa-replica-manage del srv4.example.com

EXIT STATUS

0 if the command was successful

1 if an error occurred
Jul 14 2011 IPA