metrocluster configuration-settings connection connect
Configure the network connections between partner nodes
Description
- metrocluster configuration-settings dr-group create,
- metrocluster configuration-settings interface create,
- metrocluster configuration-settings connection connect.
The DR groups must have been configured. Run the metrocluster configuration-settings dr-group show command to verify that every node is partnered in a DR group.
The network logical interfaces must have been configured on every node. Use the metrocluster configuration-settings interface show command to verify that every node has network logical interfaces configured to mirror NV logs and access remote storage.
Have NV log mirroring configured and mirroring disabled. NV log mirroring will be enabled by the metrocluster configure command.
Have access to remote storage. Use the storage disk show -pool Pool1 command to view the remote disks that are hosted on DR partner nodes.
The DR groups and network logical interfaces that were configured by the metrocluster configuration-settings commands cannot be deleted after the connections have been configured. The metrocluster configuration-settings connection disconnect command must be run to remove the connections before the DR groups and network logical interfaces can be deleted.
Examples
The following example shows configuration of connections in a MetroCluster over IP setup:
clusA::> metrocluster configuration-settings connection connect
[Job 269] Job succeeded: Connect is successful.
clusA::> metrocluster configuration-settings connection show
DR Source Destination
Group Cluster Node Network Address Network Address Partner Type Config State
----- ------- ------- --------------- --------------- ------------ ------------
1 clusA A1
Home Port: e0f
10.140.113.214 10.140.113.216 HA Partner completed
Home Port: e0f
10.140.113.214 10.140.113.218 DR Partner completed
Home Port: e0f
10.140.113.214 10.140.113.249 DR Auxiliary completed
Home Port: e0g
10.140.113.215 10.140.113.217 HA Partner completed
Home Port: e0g
10.140.113.215 10.140.113.248 DR Partner completed
Home Port: e0g
10.140.113.215 10.140.113.25 DR Auxiliary completed
A2
Home Port: e0f
10.140.113.216 10.140.113.214 HA Partner completed
Home Port: e0f
10.140.113.216 10.140.113.249 DR Partner completed
Home Port: e0f
10.140.113.216 10.140.113.218 DR Auxiliary completed
Home Port: e0g
10.140.113.217 10.140.113.215 HA Partner completed
Home Port: e0g
10.140.113.217 10.140.113.25 DR Partner completed
Home Port: e0g
10.140.113.217 10.140.113.248 DR Auxiliary completed
clusB B2
Home Port: e0f
10.140.113.249 10.140.113.218 HA Partner completed
Home Port: e0f
10.140.113.249 10.140.113.216 DR Partner completed
Home Port: e0f
10.140.113.249 10.140.113.214 DR Auxiliary completed
Home Port: e0g
10.140.113.25 10.140.113.248 HA Partner completed
Home Port: e0g
10.140.113.25 10.140.113.217 DR Partner completed
Home Port: e0g
10.140.113.25 10.140.113.215 DR Auxiliary completed
B1
Home Port: e0f
10.140.113.218 10.140.113.249 HA Partner completed
Home Port: e0f
10.140.113.218 10.140.113.214 DR Partner completed
Home Port: e0f
10.140.113.218 10.140.113.216 DR Auxiliary completed
Home Port: e0g
10.140.113.248 10.140.113.25 HA Partner completed
Home Port: e0g
10.140.113.248 10.140.113.215 DR Partner completed
Home Port: e0g
10.140.113.248 10.140.113.217 DR Auxiliary completed
24 entries were displayed.
clusA::> metrocluster configuration-settings show-status
Cluster Node Configuration Settings Status
-------------------------- ------------------ ---------------------------------
clusA
A1 completed
A2 completed
clusB
B1 completed
B2 completed
4 entries were displayed.