Creating IP partnership
After creating portset and assigning IP addresses to the portset, you have to create IP partnership for replication.
Using the management GUI
Using the CLI
For creating secured IP partnerships, the authorities and certificate installation is a prerequisite. For more information, see System Certificates.
You can export the certificate from the remote system and import it on the local system in order to allow configuration changes to be coordinated across systems without manual authentication. Use the chsystemcert command to create and manage certificates on the system.
If the certificate is signed by the system's root certificate authority, or it is a self-signed certificate, then use the following command to export the entire certificate chain on the remote system. If the certificate is signed by a trusted third-party certificate authority, then the root certificate must be retrieved from the third-party certificate authority.
chsystemcert –export
The certificate is
exported to the /dumps/certificate.pem directory on the configuration node.- To verify that the portset type is the replication for an IP partnership,
enter the following command:
In the results that display, verify and that the portset_type is replication. You can assign an IP partnership to a portset with the replication type.lsportset
- If you are creating a partnership between systems that are connected through one inter-site
link, enter the following command on the local system:
where -secured is an optional parameter and needs to be used only for secured IP partnerships.mkippartnership -clusterip ip_address_or_domain_name -linkbandwidthmbits 1000 -backgroundcopyrate 50 -link1 myportset1 -secured yes
Note: To have a fully configured partnership, repeat the preceding command on the remote system. - If you are creating a partnership between systems that are connected through dual inter-site
links, enter the following command on the local system:
where -secured is an optional parameter and needs to be used only for secured IP partnerships.mkippartnership -clusterip ip_address_or_domain_name -linkbandwidthmbits 1000 -backgroundcopyrate 50 -link1 myportset1 -link2 myportset2 -secured yes
Note: To have a fully configured partnership, repeat the preceding command on the remote system. - To specify the aggregate bandwidth of the link between two systems in megabits per second (Mbps), use the -linkbandwidthmbits parameter in the mkippartnership command.
- To specify the maximum percentage of aggregate link bandwidth that can be used for background copy operations, use the -backgroundcopyrate parameter in the mkippartnership command.
- To define a path for the certificate in the remote system, specify -sslcert /dumps/partner_certificate.pem in the mkippartnership command.
- Portsets are configured for all links between the systems.
- All systems are in the Fully Configured state.
Creating portset
You can create portset for IP partnership by using both the management GUI and the CLI.
- Using the management GUI
- To create portset using the management GUI, complete these steps:
- Select .
- Select Create Portset.
- On the Create Portset page, enter a name of the portset, and select Host Attachment, Replication, or High speed replication for the portset type.
- (Optional) Select the ownership group for the portset. An ownership group defines a subset of users and objects within the system. When you define an ownership group for portsets, you can limit, and restrict users to view and manage only specific portsets.
- Click Create.
- Using the CLI
-
To create portset using the CLI, enter the following command:
where portset_name is the name of the portset and portset_type is replication. The value owner_name indicates the name of the ownership group to which the portset belongs. It is an optional value.mkportset -name portset_name -type portset_type -ownershipgroup owner_name
Assigning IP addresses to the portset
After creation of the portset for the traffic type, you must assign the IP addresses to portset. This is required to assign the portset to the new IP partnership.
- Using the management GUI
-
To assign IP addresses to the portset using the management GUI, complete these steps:
- Select .
- Right-click the port and select Manage IP addresses.
- On the Manage IP Addresses page, select Add IP
Address. Enter the following information for the IP address that you are adding to the
selected port:
- IP address
Enter the IP address to associate with the selected port.
- Type
Select the IP protocol version of the IP address.
- Subnet Mask or Prefix
Enter the subnet mask for the IPv4 addresses or enter the prefix for IPv6 addresses.
- VLAN
Enter the corresponding VLAN tag that this IP address belongs to.
- Portset
Select the name or ID of the portset and ensure that the portset type matches the traffic type that is assigned to the port.
- IP address
- Click Back to return to the Ethernet Ports page. Verify that the port displays the Configured state. Select another port and add more IP addresses to corresponding portsets.
- Right-click the port and select either Modify Replication, Modify iSCSI hosts, or Modify Storage Ports. The traffic type for the port must match the traffic for the portset that you created.
- Using the CLI
-
To assign IP addresses to the portset using the CLI, enter the following command:
where id | name is the name or ID of the node; id is the port identifier; and id | name indicates the name or ID of the portset that was created earlier. Enter either a valid IP address for the -ip and include the values for the address. This address that is assigned to the portset and more addresses can be added to portset with the mkip command.mkip -node <id | name> -port <id> -portset <id | name> -ip <ip address> -prefix <subnet prefix> -gw <gateway address> -vlan <vlan_id>
Configuring VLAN for IP partnerships
To configure VLAN when you use IP (Internet Protocol) partnerships, consider the following requirements and procedures.
- VLAN tagging is supported for IP partnership traffic between systems.
- VLAN provides network traffic separation at the layer 2 level for Ethernet transport.
- VLAN tagging by default is disabled for any IP address of a node port. You can use the management GUI or the command-line interface (CLI) to optionally set the VLAN ID for port IPs on systems in the IP partnership.
- When a VLAN ID is configured for the port IP addresses that are mapped to the portsets, appropriate VLAN settings on the Ethernet network must also be properly configured to prevent connectivity issues.
- Setting VLAN tags for a port is disruptive. Therefore, VLAN tagging requires that you stop the partnership first before you configure VLAN tags. Then, restart again when the configuration is complete.
Follow this procedure to configure VLAN tags for existing IP partnership setups:
- Stop the partnership between the local and remote system.
- Configure VLAN on node ports in the portsets on the local system.
- Configure all intervening switches with appropriate VLAN tags.
- Configure VLAN on node ports in the portsets on the remote system.
- Check to see whether connectivity between the local and remote sites are restored.
- Restart the partnership.