mkippartnership

Use the mkippartnership command to define a new partnership created over Internet Protocol (IP) links.

Syntax

Parameters

-clusterip ip_address_or_domain_name: (Required) Specifies the partner system IP address, which can be IPv4, IPv6 or FQDNs. Systems that are connected over IP links are not displayed by lspartnershipcandidate before running mkippartnership. This does not apply to FC-based or FCoE-based connections.
-chapsecret CHAPsecret: (Optional) Specifies the Challenge-Handshake Authentication Protocol (CHAP) secret of the partner system. The maximum size of the CHAP secret is eighty alphanumeric characters.
-linkbandwidthmbits link_bandwidth_in_mbps: (Required) Specifies the aggregate bandwidth of the RC link between two clustered systems (systems) in megabits per second (Mbps). It is a numeric value from 1 to 100000.
Important: For partnerships over IP links with compression, this parameter specifies the aggregate bandwidth after the compression had been applied to the data. Do not set this parameter higher than the physical link bandwidth multiplied by the (carefully rounded down) compression factor.

This parameter can be specified without stopping the partnership.
Note: If the specified value is non-zero, the combination of both the -backgroundcopyrate and the -linkbandwidthmbits values must result in a background copy bandwidth of at least 8 Mbps.
-backgroundcopyrate percentage: (Optional) Specifies the maximum percentage of aggregate link bandwidth that can be used for background copy operations. It is a numeric value from 0 to 100, and the default value is 50, which means that a maximum of 50% of the aggregate link bandwidth can be used for background copy operations.
Note: If the specified value is non-zero, the combination of both the -backgroundcopyrate and the -linkbandwidthmbits values must result in a background copy bandwidth of at least 8 Mbps.
-compressed yes | no: (Optional) Specifies whether compression is enabled for this partnership. The default value is no.
-link1 portsetid1 | portsetname1: (Optional) Specifies the portset ID or name to be used for WAN link 1.
-link2 portsetid2 | portsetname2: (Optional) Specifies the portset ID or name to be used for WAN link 2.

Note: Even though link1 and link2 parameters are optional. It is absolutely required to provide at least one of links to establish IP partnership.

Note: There are two options to specify up to 2 portset IDs or names indicating the local Ethernet ports to be used by the partnership. The system supports up to 2 WAN links per partnership. These 2 portsets indicate the WAN links to which local ports are connected. All the ports that are part of the portset must be connected to or belong to the same WAN link. The values specified for the link1 and link2 parameters indicate the portset ID or name that specifies the group of IP addresses on the local system that can be used to access intersite WAN links.

Description

This command defines a new partnership that is created over Internet Protocol (IP) links. A remote system IP must be specified so its IP ports are enabled for data replication. RC sessions can then be created between the two partners.

In FC-based or FCoE-based partnerships, the partner system must first be a partnership candidate (displayed by lspartnership). Then, it can become part of a partnership, created specifying mkfcpartnership with the remote system ID or name.

The lspartnershipcandidate command displays partnership candidates.

For IP partnerships, specifying mkippartnership with the cluster IP address and CHAP secret of the partner creates the partnership.

All TCP connections are established that uses either IPv4 or IPv6, and it cannot be a mix of the two IP address types.

Both systems in a partnership must have at least one IP address from an identical replication group to establish RC partnerships. Replication groups are numeric values that specify the pools of local IP addresses that establish Remote Copy partnerships with pools of IP addresses configured on the partner system.

An invocation example

mkippartnership -clusterip xxx.xxx.xx.xx –chapsecret mychapsecret -linkbandwidthmbits 100 -backgroundcopyrate 50 -link1 5 -link2 portset6

The resulting output:

No feedback

An invocation example

mkippartnership –clusterip xxxx::xxx:xxxx:xxxx:xxxx –chapsecret mychapsecret –linkbandwidthmbits 1024 -backgroundcopyrate 25 -link1 5 -link2 portset6

The resulting output:

No feedback

An invocation example

The following example shows an IP partnership that uses compression:

mkippartnership -clusterip xxx.xxx.xx.xx –chapsecret mychapsecret -linkbandwidthmbits 100 -backgroundcopyrate 50 -link1 5 -link2 portset6

The resulting output:

No feedback

An invocation example

mkippartnership -clusterip xxx.xxx.xx.xx -linkbandwidthmbits 1000 -backgroundcopyrate 50 -link1 5 -link2 portset6

The resulting output:

No feedback