docu61141 configuring asynchronous replication

7/26/2019 Docu61141 Configuring Asynchronous Replication

1/54

EMCVNXeSeriesVersion 3.1

Configuring Asynchronous Replication302-002-437 REV 02


2/54

Copyright 2015 EMC Corporation. All rights reserved. Published in the USA.

Published December, 2015

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change

without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a

particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and othercountries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

EMC CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC VNXe Series3.1 Configuring Asynchronous Replication


3/54

Overview 5

About this document.......................................................................................6VNXe overview................................................................................................ 6What is data replication?.................................................................................6Using replication for disaster recovery.............................................................7Using replication for planned downtime.......................................................... 7Fail back a replication session.........................................................................8Replication interfaces and connections........................................................... 8

Setting up replication 9

Create a replication interface.........................................................................10

Create a replicationconnection.....................................................................10Create a replicationsession.......................................................................... 11Create a replication destination....................................................... 13

Managing replication 15

Manage replication interfaces....................................................................... 16Manage replicationconnections....................................................................16Manage replicationsessions.........................................................................17

Unisphere CLI commands 21

Manage interfaces.........................................................................................22Create interfaces..............................................................................23View interfaces................................................................................ 25Delete interfaces..............................................................................26

Manage remote storage systems...................................................................26Create remote system configurations............................................... 27View settings for remote storage systems.........................................29Verify settings for remote storage systems....................................... 29Change settings for remote storage systems.................................... 30Delete remote system configurations............................................... 31

Manage replication sessions.........................................................................31Create replication sessions.............................................................. 36View replication sessions.................................................................39

Change replication session settings................................................. 40Delete replication sessions.............................................................. 42Fail over replication sessions........................................................... 43Fail back replication sessions.......................................................... 44

AssociatedCLI commands.............................................................................45The show action command...............................................................45Manage Ethernet ports.....................................................................46Manage link aggregations................................................................49

Chapter 1

Chapter 2

Chapter 3

Chapter 4

CONTENTS

EMC VNXe Series3.1 Configuring Asynchronous Replication 3


4/54

CONTENTS



5/54

CHAPTER 1

Overview

This chapter addresses the following topics:

l About this document...............................................................................................6l VNXe overview.........................................................................................................6l What is data replication?.........................................................................................6l Using replication for disaster recovery.....................................................................7l Using replication for planned downtime.................................................................. 7l Fail back a replication session.................................................................................8

l Replication interfaces and connections................................................................... 8

Overview 5


6/54

About this documentThis document provides information that you can use to configure and manage remotereplication on your EMCVNXestorage system. Along with relevant concepts and the

instructions to configure replication using Unisphere, this document also includesinformation on all CLI commands related to replication.

Note

This document includes information relevant to asynchronous replication only. For more

information on other Unisphere features or CLI commands, refer to the Unisphere online

help and CLI User Guide.

VNXe overviewEMCVNXeis a simple, yet powerful hybrid-storage system that delivers enterpriseclass reliability and data availability. It provides a solution that is easy to install, manage,service, and support. The enterprise-level features include Unified Snapshots, MulticoreCache, Multicore RAID, FAST Cache, FAST VP, and many other provisioning andmonitoring features that support a wide range of workloads such as databases, files, andvirtual machines. Along with enhanced native iSCSI protocol support, the VNXe alsosupports Fibre Channel (FC) protocol, and expanded IPv6 functionality.

What is data replication?Data replication is one of the many data protection methodologies that enable your datacenter to avoid disruptions in business operations. It is a process in which storage data is

duplicated to a remote or local system. It provides an enhanced level of redundancy incase the main storage backup system fails. It minimizes the downtime-associated costsof a system failure and simplifies the recovery process from a natural disaster or humanerror.

The replication feature leverages the Unified Snapshots technology to produce a read-only, point-in-time copy of source storage data and periodically updates the copy to keepit consistent with the source data. The system supports asynchronous replication ofblock-based storage resources (LUNs, LUN groups, and VMware VMFS datastores). Itleverages crash consistent replicas to provide remote data protection of storageresources.

Recovery Point Objective

Recovery Point Objective (RPO) is an industry accepted term that indicates the acceptableamount of data, measured in units of time, that may be lost in a failure. When you set upan asynchronous replication session, you can configure automatic synchronization basedon the RPO. You can specify an RPO from a minimum of 5 minutes up to a maximum of 24hours. The default RPO is set at a 1 hour interval.

Note

Although a smaller time interval provides more protection and lesser protection space

consumption, it also has a higher performance impact, and results in more network

traffic. A higher RPO value may result in more protection space consumption. This may

affect the snapshot schedules and space thresholds.

Overview



7/54

Replication limits

Note the following limits related to replication:

Attributes Limit

Number of replication sessions 1000 (500 per SP)

Concurrent data transfers 256 (128 per SP)

Concurrent initial synchronizations 32 (16 per SP)

Destination systems for remote replications 16

Using replication for disaster recoveryIn a disaster recovery scenario, the primary (source) system is unavailable due to anatural or human-caused disaster. Data access is still available because a replicationsession was configured between the primary and destination systems, and the

destination system contains a full copy, or replica, of the production data. The replica isup-to-date in accordance with the last time the destination synchronized with the source,as specified by the automatic synchronization recovery point objective (RPO) setting. Byissuing a session failover on the destination system, you make the destination systemthe new production system, using the replica of the primary systems data that resides onthe destination system. Using replicas for disaster recovery minimizes potential dataloss. The amount of potential data loss is affected by the RPO that is configured whensetting up the replication session.

Once the session is failed over to the destination system, the destination storageresource becomes read-write. At this point, ensure that the storage resource has thecorrect access permissions to the host and share. When originally establishing areplication session between the primary and destination systems, create the right host

access on the destination system ahead of time to reduce downtime in advance of adisaster.

To resume operations on the source, the replication session needs to be failed back. Formore information on failing back a replication session, see Fail back a replicationsession on page 8.

Using replication for planned downtimeUnlike a disaster, in which the primary (source) system is lost due to an unforeseenevent, planned downtime is a situation for which you plan and take the source systemoffline for maintenance or testing purposes. Prior to the planned downtime, both the

source and destination are running with an active replication session. When you want totake the source offline in this scenario, the destination system is used as the productionsystem for the duration of the maintenance period. Once maintenance or testingcompletes, return production to the original source system. Planned downtime involvesno window of data loss.

To initiate a planned downtime, use the Failover with Sync option on the source system.When you fail over a replication session from the source system, the destination systemis fully synchronized with the source to ensure that there is no data loss. The sessionremains paused for asynchronous replication, and the access modes are reversed. Thedestination storage resource can be used for providing access to the host.

Overview

Using replication for disaster recovery 7


8/54

To resume operations on the source, the replication session needs to be failed back. Formore information on failing back a replication session, see Fail back a replicationsession on page 8.

Fail back a replication sessionTo resume operations on a source system, the associated replication session needs to befailed back. To fail back a replication session, you use the Failback option on the originaldestination system. Failback synchronizes the original source with changes done on theoriginal destination after failover, restores the source as the production system, and thenrestarts the replication session in the original direction.

Replication interfaces and connectionsReplication can occur locally or between a local storage system and a remote storagesystem. Before you create a remote replication session, you first need to configure anactive communication channel between the two systems. This involves configuring therelevant replication licenses, setting up a replication interface on the source anddestination systems, and using the interfaces to set up a replication connection betweenthe systems.

Note

Replication interfaces and connections do not apply to local replication.

After communication is established, you can set up a remote replication session to createand update a remote replica at a remote destination site. After the initial copy, anychanges that are made to the source storage resource are transferred to the destinationstorage resource over the network at the next synchronization (automatic or manual).

Replication interfacesReplication interfaces are dedicated network interfaces configured specifically forreplication-related data or management traffic. Each Storage Processor (SP) must includeat least one replication interface configured on it. Each replication interface on the SP ofthe source system should be able to communicate to the replication interface on the SPof the destination system. To establish this, you must set up a switched network forremote replication. You can configure a replication interface with an IPv4 or IPv6 address.

Note

Replication is supported between like type IP addresses. For example, you can set up a

replication connection between a replication interface configured with IPv4 address on

the source system and a replication interface configured with IPv4 address on the remote

system.

Replication connections

Replication requires a configured connection between the source system and destinationsystem. This connection is called a replication connection. Replication connections usereplication interfaces on each SP from the local system and pairs them up with thereplication interfaces on each SP in the remote system.

Overview



9/54

CHAPTER 2

Setting up replication


l Create a replication interface.................................................................................10l Create a replication connection............................................................................. 10l Create a replication session.................................................................................. 11

Setting up replication 9


10/54

Create a replication interfaceProcedure

1. Click Settings> Replication Settings.

2. Select an available port, and click Create.

3. In the Create Replication Network Interfacewindow, specify the following settings foreach Storage Processor (SP):

Table 1

Replication interface settings

Setting Description

IP Address IP address associated with the replication interface. You can specify an

IPv4 or IPv6-based address. Ensure that you specify the same type of

address for both SPs.

Subnet Mask or

Prefix Length

IP address mask or prefix length that identifies the subnet where the

replication interface resides.

Gateway Gateway IP address associated with the replication interface.

4. Optionally, click Show Advancedto set the VLAN ID in the following manner:

a. Click the pencil icon next to theVLAN IDfield.

b. Review the confirmation message, and clickYesto confirm.

c. In theVLAN IDfield, enter the relevant value (between 1 and 4904) associatedwith the replication interface.

5. Click Create.

Create a replication connectionA replication connection establishes a communication path between two systems, and isrequired to create remote replication session.

Note

For the replication connection to work accurately, it is critical for the system times on the

local and remote systems to be within a 10 minute window. It is recommended to

configure NTP server settings on both systems.

To create a replication connection:

Procedure

1. Click Hosts> Replication Connectionsto view a list of existing replication connections.

2. ClickAdd Replication Connectionto launch theAdd Replication Connectionwizard.

3. On the Specify System Informationpanel, enter information about the remote system.The following table lists the required settings:




11/54

Table 2

Remote system information

Setting Description

Remote System

IP address Enter the management IP address of the remote system.

User Name Enter the name of a user for the remote system who has privileges to

create replication connections. Ensure that the user has a Storage

Administrator role or higher.

Password Enter the password associated with the user specified in the User

Name field for the remote system.

Enable asynchronous

connection

Select this option to enable an asynchronous connection between the

local and remote systems. This checkbox appears selected by default.

Local System

Password Enter the password associated with your user account on the local

system.

4. Click Next.

5. On the Summarypanel, verify your settings, and click Finish.

Create a replication sessionBefore you begin

Before creating a replication session, complete the following configuration tasks:

l For remote replication, set up replication interfaces.

l Create a replication connection to the remote system.

l Create the storage resource that provides the replication source.

l For local replication, configure a replication destination on the local system.

l [Optional] For remote replication, create an identical storage resource that will act asthe replication destination on the remote system.

Note

To set an existing storage resource as a destination, click Change to Read-Onlyon

the Replicationtab for that storage resource on the destination system.

You can create only one replication session for a storage resource.

Procedure

1. Click Storageand select the storage type.

Note

You can create replication sessions for LUNs, LUN groups, and VMware VMFS

datastores only.

2. Select the storage resource from the list, and click Details.


Create a replication session 11


12/54

3. Click the Replicationtab.

4. Decide if you want to create a local replication or a remote replication.

l To create a local replication, click Configure Local Replication. When you create alocal replication, the storage system creates a full copy of the storage resource onthe local system. This has advantages over snapshots in that a full copy, not just a

copy of changes, is retained.l To create a remote replication, click Configure Replication to a Remote System.

When you create a remote replication, the storage system creates a full copy ofyour storage resource on a remote system by transferring the data over thenetwork. Remote replication is often used to ensure that a copy is available at aremote site in case of catastrophic data loss at the local site.

5. Follow the steps in the Create Sessionwizard:

When the wizard finishes creating the replication session, you can review the detailson the tab. The replication session also appears in the list of Replication Sessions,which you can view by going to .

Table 3 Create Session wizard settings

Wizard page Description

Select Destination For local replication, do the following:

l Select an existing destination storage resource on this system that will

store the replicated data. You can also create a new destination resource

by clicking Create Destinationand following the steps in the

associated storage wizard.

For remote replication, do the following:

l Destination System From the list of systems discovered based on the

configured replication connections, select a destination system you wantto use for this replication session.

If the destination system you want is not listed, click Create

Connectionto configure a replication connection with that system. For

more information, see Create a replication connection on page 10.

l Storage Resource Select the storage resource on the selected

destination system that will store the replicated data.

If the storage resource you want is not listed, or to create an identical

storage resource on the destination system, click Create Destination.

For more information, see Create a replication destination on page 13.

Specify Name Enter a name for the replication session.

Replication Path

(applies to remote

replication only)

By default, the system automatically configures the communication path

from the source system to the destination. You can leave the default

selections, or click Show advancedto select specific IP interfaces for the

source and destination.

l Source SPA Interfaceand Source SPB Interface For each SP, select

an available IP address for the replication source, or choose System

Selectedto allow Unisphere to choose one for you.

l Destination SPA Interfaceand Destination SPB Interface For each

SP, select an available IP address for the replication destination, or

choose System Selectedto allow Unisphere to choose one for you.




13/54

Table 3

Create Session wizard settings (continued)

Wizard page Description

Configure

Synchronization

By default, the system will configure synchronization to occur automatically

at one hour intervals. To modify the default synchronization of the replication

session, click Show Advancedand choose from the following settings:

l Manual Synchronization Data will only be replicated when manually

initiated (by selecting the replication session in System> System

Replications> Session Detailsand clicking Sync Now). To have the

system perform the first synchronization automatically, select Perform

initial synchronization automatically.

l Automatic Synchronization Data will be replicated in order to

maintain the desired Recovery Point Objective (RPO). The default RPO is

one hour. Use the slider to increase or decrease the RPO.

Note

As the RPO increases, the potential for data loss also increases, as well as

the amount of required protection space. Lowering the RPO will reduce the

amount of potential data loss, but will also increase network traffic and may

negatively impact performance.

Summary The Summary panel displays the configured destination system, storage

resource, synchronization mode, source interface, and destination interface.

Verify that your replication session settings are correct and click Finish.

Click Backif you need to make any changes to your replication session.

Create SessionReplicationSystem> System Replications

Create a replication destination

Before you begin

Create a replication connection between the source and destination systems.

Follow these steps to create a replication destination from the Create SessionWizard.

Note

You can also set an existing storage resource to act as a replication destination. Ensure

that it is not involved in an active replication session by checking the Replicationtab on

the Details screen of the storage resource.

Procedure

1. Launch the Create Session Wizard.

2. From the Destination Systemlist, select the relevant destination system.

3. Next to the Storage Resourcelist, click Create Destination.

4. In the Unisphere Launchwindow, clickYesto launch Unisphere for the destinationsystem.

5. Log on to the Unisphere on the destination system. The relevant storage wizardappears with some values filled automatically. This ensures that you created anidentical storage resource on this system.


Create a replication destination 13


14/54

6. Review, and, if necessary, update information on the relevant screens of the wizard.

7. Click Finishto complete the wizard.

You can now go back to the browser page running Unisphere on the source system,and select the destination storage resource in the Create Session Wizard.




15/54

CHAPTER 3

Managing replication


l Manage replication interfaces............................................................................... 16l Manage replication connections............................................................................16l Manage replication sessions.................................................................................17

Managing replication 15


16/54

Manage replication interfacesModify a replication interface

Note

Replication interfaces used in a replication session cannot be modified.


2. Expand the Ethernet port associated with a replication interface.

3. Select the relevant Storage Processor (SP), and click Modify.

4. In the Modify Replication Network Interfacewindow, change the following settings:

Table 4

Replication settings

Setting Description

IP Address IP address associated with the replication interface. You can specify an

IPv4 or IPv6-based address. Ensure that you specify the same type of

address for both SPs.

Subnet Mask or

Prefix Length

IP address mask or prefix length that identifies the subnet where the

replication interface resides.

Gateway Gateway IP address associated with the replication interface.

5. Optionally, click Show Advancedto update the VLAN ID in the following manner:

a. Click the pencil icon next to theVLAN IDfield.

b. Review the confirmation message and clickYesto confirm.c. In theVLAN IDfield, type the relevant value (between 1 and 4094) associated with

the replication interface.

d. Click Modify.

Delete a replication interface

Note

Replication interfaces used in a replication session cannot be deleted. Before deleting a

replication interface, ensure that it is not used in a replication.


2. Expand the port associated with an replication interface.

3. Select the relevant interface, and click Delete.

4. ClickYesin the confirmation dialog box.

Manage replication connectionsA replication connection establishes a communication path between two systems thatyou can use to create replication sessions. After you create a replication connection, youmust define which local or remote network node acts as the source and which local orremote network node acts as the destination in the replication session.




17/54

Verify a replication connection

1. Click Hosts> Replication Connectionsto view a list of existing replicationconnections.

2. Select a replication connection from the list, and clickVerify and Update Connection.The storage system verifies the communication path to the remote host.

Modify a replication connection


2. Select a replication connection, and click Modify.

3. Specify the following settings in the Modify Replication Connectiondialog box:

Table 5

Replication connection settings

Setting Description

Name Enter a name to associate with the remote system.

Network Name or

Address

Enter the network name or IP address of the remote system.

Remote user name Enter the name of a user for the remote system who has privileges to create

replication connections. Ensure that the user has a Storage Administrator

role or higher.

Remote password Enter the password associated with the remote user name to connect to the

remote system.

Enable

asynchronous

connection

Select this option to enable an asynchronous connection between the local

and remote systems. This checkbox appears selected by default.

4. Click OKto save the settings for the replication connection.

Remove a replication connection

Note

Replication connections used in a replication session cannot be deleted. Before deleting

a replication connection, ensure that it is not used in a replication.


2. Select a replication connection from the list, and click Remove ReplicationConnection.

3. ClickYesto confirm.

Manage replication sessionsA replication session establishes an end-to-end path for a replication operation betweena source and destination. The replication source and destination may be remote or local,so the session establishes the path that the data follows as it moves from source todestination.


Manage replication sessions 17


18/54

Note

You can also perform these actions from the Replicationtab that appears on the Details

page for the storage resource participating in a replication session.

Modify a replication session

1. Click System> System Replicationsto view a list of replication sessions.

2. Select a replication session from the list, and click Details.

3. In the Generaltab, modify the following replication session settings:

Table 6

Replication session settings

Setting Information

Session Name Name of the replication session.

Interface From the relevant drop-down lists, select the IP interface that the source or

destination system must use for the replication session.

4. In the Synchronizationtab, modify the following settings:

Table 7

Synchronization settings

Setting Information

Manual

Synchronization

Select to configure manual synchronization. Data will be synchronized only

when manually initiated.

Automatic

Synchronization

Select to configure automatic synchronization. Data will be synchronized

automatically based on the configured recovery point objective (RPO). Drag

the slider icon to set an RPO value based on protection, performance

impact, network traffic, and protection space consumed.

5. ClickApply.

Manually synchronize a replication session

1. Click System > System Replicationsto view a list of replication sessions.

2. (Optional) Select a replication session from the list, and click Details.

3. Click Sync Nowto manually initiate the synchronization of the replication session.

Pause or resume a replication session


2. Select a replication session from the list and click one of the following:

l Pauseto stop an active replication session

l Resumeto continue a stopped or paused replication session

Note

The Pauseor Resumebuttons appear for storage resources in a replication session where

the source storage resource is local to the system. At any given point of time, based on

the state of the replication session, only one of these buttons appear on screen.

A replication session is automatically paused when a failover occurs. Resuming a session

from the destination storage resource ensures that any changes in the destination




19/54

storage resource are copied over back to the source storage resource at the next RPOinterval. If an RPO schedule is not set, manually synchronize the replication session.

Fail over a replication session


2. (Optional) Select a replication session from the list, and click Details.3. Click Failover.

4. In the Failoverwindow, select the type of failover you want to initiate:

Table 8 Types of failover

Type Description

Sync Before

Failover

The destination synchronizes with the source storage resource, the replication

session is stopped, and the access modes of the storage resources are

switched. After the failover operation, the destination object's status becomes

read/write and the source object's status becomes read-only.

Note

To perform this type of failover, both the source and destination objects of the

session must be available.

Failover

Without Sync

In response to an unplanned emergency scenario in which the source has

become unavailable, the access modes of the source and destination storage

resources are switched. After the failover operation, the destination object's

status becomes read/write.

Note

In this type of failover, any active data transders are terminated, causing a

potential loss of data. If the source site is still available when you perform afailover, the system attempts to change the source object from read/write to

read-only.

5. Click OK.

Fail back a replication session

Note

You can perform this action from the destination system only. Both the source and

destination storage resources must be available to perform a successful failback

operation.


2. (Optional) Select a replication session from the list, and click Details.

3. Click Failback. The option to fail back a replication session is only available if thereplication session has been previously failed over.A failback operation performs switches the access modes of the storage resourcesfollowing a failover operation. Once the destination synchronizes with the sourceagain, the source storage resource's status returns to read/write and the destinationstorage resource's status returns to read-only.




20/54

Delete a replication session


2. Select a replication session from the list

3. Click Delete.




21/54

CHAPTER 4

Unisphere CLI commands


l Manage interfaces.................................................................................................22l Manage remote storage systems........................................................................... 26l Manage replication sessions.................................................................................31l Associated CLI commands.....................................................................................45

Unisphere CLI commands 21


22/54

Manage interfacesCreate interfaces to enable and control access between the system, the network, andconfigured hosts. Specify the IP address for the interface as well as the IP addresses for

the subnet mask and gateway.You can create the following types of interfaces:

l iSCSI interfaces for controlling access to iSCSI storage. You assign the interface to aniSCSI node.

l Replication interfaces for replication-related data or management traffic.

Each interface is identified by an ID.

The following table lists the interface attributes with a description of each.

Table 9

Interface attributes

Attribute DescriptionID ID of the interface.

Type Interface type. Value is one of the following:

l file Interface for CIFS or NFS storage.

l iscsi Interface for iSCSI storage.

l replication Interface for replication-related data or management

traffic.

Port ID of the physical port or link aggregation on an SP on which the interface is

running. The ID includes the port name and SP name.

VLAN ID Virtual local area network (VLAN) ID for the interface. The interface uses the

ID to accept packets that have VLAN tags. The value range is 1-4095.

Note

If no VLAN ID is specified, which is the default, packets do not have VLAN

tags. The Unisphere online help provides more details about VLANs.

IP address IPv4 or IPv6 address.

Subnet mask IPv4 subnet mask.

Gateway IPv4 or IPv6 gateway.

MAC address MAC address of the interface.

SP SP that uses the interface.

NAS server NAS server identifier.

Preferred Sets the network interface as the preferred source for outgoing traffic. All

outgoing DNS or Active Directory requests are forwarded through this

interface, and the IP address assigned to this interface is used as the source

address of the data packets. For each NAS server, you can choose a single IP

address as preferred. Valid values are yes or no.




23/54

Table 9

Interface attributes (continued)

Attribute Description

Note

This attribute applies to file interfaces only.

Health state A numerical value indicating the health of the system. Value is one of the

following:

l Unknown (0)

l OK (5)

l OK BUT (7)

l Degraded/Warning (10)

l Minor failure (15)

l Major failure (20)

Health

detailsAdditional health information.

Create interfaces

Create an interface.

Format/net/if create [-vlanId ] -type { {file} -server | iscsi} -port | mgmt | replication} -origin {dynamic |

static -addr ] [-netmask ] [-gateway ]

Action qualifier

Qualifier Description

-type Type the interface type. Value is one of the following:

l file Interface for file-based storage, such as file systems.

l iscsi Interface for iSCSI storage.

l replication Interface for replication-related data or

management traffic.

-server Type the NAS server identifier.

Note

A NAS server cannot have more than one IPv4 interface and one IPv6

interface.

-preferred Specify this qualifier to set the network interface as the preferred sourcefor outgoing traffic. For each NAS server, you can choose an IPv4interface and IPv6 interface as the preferred interfaces.

-port Type the ID of the SP port or link aggregation that will use the interface.Manage Ethernet ports on page 46explains how to view the port IDs.


Create interfaces 23


24/54


Note

For systems with two SPs, a file interface is created on a pair of

symmetric Ethernet ports rather than on a single specified port. Its

current port is defined by NAS server SP and may differ from the

specified port. For example, if the user specifies port spa_eth2, but the

NAS server is on SP B, the interface is created on port spb_eth2.

-vlanId Type the virtual LAN (VLAN) ID for the interface. The interface uses the IDto accept packets that have VLAN tags. The value range is 14095.

Note

If no VLAN ID is specified, which is the default, packets do not have

VLAN tags. The Unisphere online help provides more details about

VLANs.

-addr Type the IP address for the interface. The prefix length should beappended to the IPv6 address and, if omitted, will default to 64. ForIPv4 addresses, the default length is 24. The IPv4 netmask may bespecified in address attribute after slash.

-netmask Type the subnet mask for the interface.

Note

This qualifier is not required if the prefix length is specified in the -addr

attribute.

-gateway Type the gateway for the interface.

Note

This qualifier configures the default gateway for the specified ports SP.

Example 1

The following command creates a replication interface. The interface receives the ID IF_1:

uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/if create -type

replication -port eth1_spb -addr 10.0.0.1 -netmask 255.255.255.0 -

gateway 10.0.0.1

Storage system address: 10.0.0.1Storage system port: 443HTTPS connection

ID = IF_1Operation completed successfully.

Example 2

The following command creates a network interface for file storage on SP A port eth0 withan IPv6 IP address. The interface receives the ID IF_2:




25/54

uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/if create -type

file -server nas_1 -port eth0_SPA -addr 2001:db8:4c:

8130:260:1600:3ed0:a3fe/64

Storage system address: 10.0.0.1Storage system port: 443

HTTPS connection

ID = IF_2Operation completed successfully.

View interfaces

View a list of interfaces on the system. You can filter on the interface ID.

Note

The show action command on page 45explains how to change the output format.

Format

/net/if [ {-id | -port | -server | -type } ] show

Object qualifier


-id Type the ID of an interface.

-port Type the port the interface is associated with.

-server Type the NAS server the interface is associated with.

-type Specify the type of the interface. Value is one of the following:

l file

l iscsi

l replication

Example

The following command displays all interfaces on the system:

uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/if show


1: ID = if_0 Type = file NAS server = nas_0 Preferred = yes Port = eth0_spa VLAN ID = 0 IP address = 3ffe:80c0:22c:4e:a:0:2:7f/64 Subnet mask =

Gateway = fe80::20a8bff:fe5a:967c SP = SPA

2: ID = if_1 Type = file NAS server = nas_1


View interfaces 25


26/54

Preferred = yes Port = eth1_spa VLAN ID = 1 IP address = 192.168.1.2 Subnet mask = 255.255.255.0 Gateway = 192.168.1.254

SP = SPA

3: ID = if_2 Type = replication NAS server = Preferred = no Port = eth1_spb VLAN ID = IP address = 10.103.75.56 Subnet mask = 255.255.248.0 Gateway = 10.103.72.1 SP = spb

Delete interfaces

Delete an interface.

CAUTION

Deleting an interface can break the connection between systems that use it, such as

configured hosts.

Format/net/if id delete

Object qualifier


-id Type the ID of the interface to delete.

Example

The following command deletes interface IF_1:

uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/if id IF_1

delete


Operation completed successfully.

Manage remote storage systemsConfigure remote storage systems that connect to the system to which you are logged in.The system uses the configuration to access and communicate with the remote system.For example, to use remote replication, create a configuration that specifies the remotesystem to use as the destination for the replication session.

Each remote system configuration is identified by an ID.

The following table lists the attributes for remote storage systems:




27/54

Table 1

Remote system attributes


ID ID of the remote system.

Name Name of the remote system.

Type Type of remote system. Value is VNXe.

Management

Address

Network name or management IP address of the remote system.

Operational status Operational status of the remote system. Value is one of the following:

l OK (0x2) - The remote system is operating normally.

l Updating (0x8407) - The connection with the remote system is

updating.

l Lost Communication (0xD) - Communication with the remote system

has been lost.

Health state Health state of the remote system. Value is one of the following:

l Unknown (0) - The health of the remote system cannot be determined.

l OK (5) - The remote system is operating normally or the connection

with the remote system is updating.

l Critical failure (25) - Communication with the remote system has been

lost.

Health details Additional health information.

Source user name For systems that are the source in a replication session, the username that

is used to access the system.

Source user

password

For systems that are the source in a replication session, the user password

that is used to access the system.

Source interfaces The list of source interface identifiers used to create the interconnect

between the two systems.

Destination user

name

For systems that are the destination in a replication session, the username

that is used to access the system.

Destination user

password

For systems that are the destination in a replication session, the user

password that is used to access the system.

Passphrase The passphrase that is used between the source and destination systems

in the replication connection.

Sync Enabled Indicates whether the synchronous connection is enabled.

Create remote system configurations

Configures a remote system configuration for the local system to access.

Format/remote/sys create -addr -type { VNXe -srcUsername{ -srcPassword | -srcPasswordSecure } -dstUsername { -dstPassword | -


Create remote system configurations 27


28/54

dstPasswordSecure } | [-sync { enable | disable }] | -name{ -passPhrase | -passPhraseSecure } } [ -srcIf] [ -connectionType ]

Action qualifiers


-addr Type the network name or IP address of the remote system.

-type Specifies the remote system type. Value is VNXe.

-srcUsername For systems that are the source in a replication session, typethe username that is used to access the system.

-srcPassword For systems that are the source in a replication session, typethe user password that is used to access the system.

-srcPasswordSecure Specify the password in secure mode. Once you run thecommand with this qualifier, you will be asked to type thepassword separately.

-dstUsername For systems that are the destination in a replication session,type the username that is used to access the system.

-dstPassword For systems that are the destination in a replication session,type the user password that is used to access the system.

-dstPasswordSecure Specify the password in secure mode. Once you run thecommand with this qualifier, you will be asked to type thepassword separately.

-name Specify the remote system name. This qualifier applies toVNX or Celerra systems only.

-passPhraseType the passphrase that is used between the source anddestination systems in the replication connection. Thisqualifier applies to VNX or Celerra systems only.

-passPhraseSecure Specify the password in secure mode. Once you run thecommand with this qualifier, you will be asked to type thepassword separately.

-sync Specify this qualifier to configure a synchronous connectionbetween the source and destination systems.

-connectionType Specify this qualifier to indicate the type of replicationconnection. Valid values are async, sync, or both.

Example

The following command creates a remote system configuration with these settings:

l Type is VNXe.

l Network address is 10.64.75.10.

l Includes access credentials for when the system is the source or destination.

The configure remote system receives the ID RS_1:

uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /remote/sys create

addr 10.64.75.10 type vnxe srcUsername admin1 -srcPassword




29/54

Password456! dstUsername admin2 dstPassword Password986! -

connectionType sync


ID = RS_1Operation completed successfully.

View settings for remote storage systems

View the configuration for a remote system on the local system. You can filter on theconfiguration ID of the remote system.

Note


Format

/remote/sys [-id ] show

Object qualifier


-id Type the ID of a remote system configuration.

Example

The following command lists all configurations for remote storage systems:

uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /remote/sys show


1: ID = RS_1 Name = MyTargetSystem Address = 10.64.74.1 Type = VNXe Model = VNXe3200 Serial number = FCNCH01234567A90

Verify settings for remote storage systems

Verify the configuration settings for a remote system to ensure that the source storage

resource can connect to the remote storage resource.

Format/remote/sys id verify

Object qualifier


-id Type the ID of a remote system configuration to verify the settings.

Example

The following command verifies remote system configuration RS_1:


View settings for remote storage systems 29


30/54

uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /remote/sys id RS_1

verify



Change settings for remote storage systems

Changes the configuration settings for a remote system.

Format/remote/sys -id set [ -name ] [ -addr ][ -dstUsername { -dstPassword | -dstPasswordSecure } ] [ { -passPhrase | -passPhraseSecure } ] [ -srcIf ]

Object qualifier


-id Type the ID of the remote system configuration to change.

Action qualifiers


-name Type the name of the system.

-addr Type the network name or management IP address of theremote system.

-dstUsername For VNXe systems that are the destination in a replicationsession, type the username that is used to access thesystem.

-dstPassword For VNXe systems that are the destination in a replicationsession, type the user password that is used to access thesystem.

-dstPasswordSecure Specify the password in secure mode - the user will beprompted to input the password.

-passPhrase Type the passphrase that is used between the source anddestination systems in the replication connection. This

qualifier applies to VNX or Celerra systems only.

-passPhraseSecure Specify the password in secure mode - the user will beprompted to input the password.

-Sync Specify this qualifier to configure a synchronous connectionbetween the source and destination systems.

Example

The following command changes the name, IP address, and access credentials for remotesystem configuration RS_1:




31/54


set name Remote2 addr 10.64.74.2 -dstUsername Local/joe -

dstPassword Password456!


HTTPS connection

ID = RS_1


Delete remote system configurations

Deletes the configuration for a remote system.

Note

Before deleting a remote system configuration, ensure that all I/O operations on the

system, such as active replication sessions, have completed to avoid data loss.

Format/remote/sys id delete

Object qualifier


-id Type the ID of the remote system configuration to delete.

Example

The following command deletes remote system configuration RS_1:


delete



Manage replication sessionsStorage replication is a process in which storage data is duplicated either locally or to a

remote network device. Replication produces a read-only, point-in-time copy of sourcestorage data and periodically updates the copy, keeping it consistent with the sourcedata. Storage replication provides an enhanced level of redundancy in case the mainstorage backup system fails. As a result:

l Downtime associated cost of a system failure is minimized.

l Recovery process from a natural or human-caused disaster is facilitated.

Each replication session is identified by an ID. The Unisphere online help provides moredetails about storage replication.


Delete remote system configurations 31


32/54

Note

At any given point in time, only one command is supported on a replication session.

Before running a new command, ensure that you wait for the existing action on the

replication session to complete.

The following table lists the attributes for replication sessions:

Table 11

Replication session attributes


ID ID of the session.

Name Name of the replication session.

Remote session ID Identified session in case of replication with the

system.

Synchronization Type of synchronization. Valid values are:

l auto Data is replicated automatically in

order to maintain the desired Recovery

Point Objective (RPO).

l manual Data will only be replicated

when manually initiated.

Note

As the RPO increases, the potential for data loss

also increases, as well as the amount of

required protection space. Lowering the RPO

will reduce the amount of potential data loss,

but will also increase network traffic and maynegatively impact performance. The default RPO

is one hour.

RPO Recovery Point Objective (RPO) interval for

automatic synchronization.

Session type Storage type of the session. Valid value is

block, which indicates a replication session of

a block-based storage resource.

Resource type Type of storage resource to which the

replication session is applied.

State State of the replication session. Valid values

are:

l In Sync

l Syncing

l Consistent

l Out of Sync

Health state Health state of the session. Valid values are:

l OK Session is operating normally.




33/54

Table 11

Replication session attributes (continued)


l Degraded/Warning Session is

currently paused.l Minor failure An error has caused

one or more of the following:

n Session has stopped. You can try to

resume a stopped replication session.

n Session has failed over, likely due to

the source storage resource becoming

unavailable. The destination storage

resource is now in a read/write state.

Review the state of the source and

check your network connections for any

problems. Once the source is backonline, you can fail back the session to

return it to normal operation.

n Communication with the replication

host has been lost. It is likely that the

system is either powered down or there

is a network connectivity issue between

the systems. A change in the network

configuration on either side could also

interrupt communication.

Note

If the replication session is in an error state, thesession will not be recoverable. You will need to

delete the session and create a new replication

session.

Health details Additional health information.

Operational status Operational status of the session. The

operational status code appears in

parentheses.

Network status Status of the network connection. Valid values

are:

l Unknown Network status is currently

unknown. If you continue to see this value,

check the network connections.

l OK Network connection is operating

normally.

l Lost Communication

Communication with the replication host

has been lost. It is likely that the system is

either powered down or there is a network

connectivity issue between the systems. A

change in the network configuration on




34/54

Table 11



either side could also interrupt

communication.

Source status Status of the source storage resource in the

session. Valid values are:

l Unknown Source status is unknown.

l OK- Source is operating normally.

l Paused Replication session for the

source is currently paused.

l Fatal replication issue Source

has experienced a critical error and the

replication session has stopped. Delete the

replication session and re-create it.

l Lost communication







communication.

l Failed over The replication session

has failed over to the destination site. In a

failover state, the destination object isread/write. When communication is

reestablished between the source and

destination, the source becomes read-only.

To resume operations on the source site,

the replication session needs to be failed

back.

Destination status Status of the destination storage resource in the

session. Valid values are:

l Unknown Status of the destination

resource is unknown.

l OK Destination resource is operatingnormally.

l Paused Replication session for

destination resource is currently paused.

l Fatal replication issue

Destination has experienced a critical error

and the replication session has stopped.

Delete the replication session and re-create

it.

l Lost communication





35/54

Table 11








communication.

l Failed over The replication session

has failed over to the destination site. In a

failover state, the destination object is

read/write. When communication is

reestablished between the source and

destination, the source becomes read-only.

To resume operations on the source site,

the replication session needs to be failedback.

Local role The local system role. Valid values are:

l Unknown Status of the local system is

unknown.

l Source Resource on the local system is

replicated to the remote system.

l Destination Resource on the local

system is the replication destination of the

resource on the remote system.

l Loopback Resources participating inthe replication session are located on the

same storage system.

l Local Resources participating in the

replication session are located on the

different storage processors of the local

system.

Source resource ID of the storage resource that is the source of

the session. The source can be local or remote.

Destination type Type of destination used in the session. Valid

values are:l local Maintain a full copy of the

storage resource on the local system. This

has advantages over snapshots in that a

full copy, not just a copy of changes, is

retained.

l remote Maintain a full copy of the

storage resource on a remote system by

transferring the data over the network.

Remote replication is often used to ensure

that a copy is available at a remote site in




36/54

Table 11



case of catastrophic data loss, for example,

due to natural disaster at the local site.

Destination system For remote sessions, the ID of the remote

system on which the data is replicated.

Destination resource ID of the storage resource on which the data is

replicated.

Time of last sync Date and time of the last replication

synchronization.

Sync status Percentage of the replication synchronization

that has completed and the amount of time

remaining.

Sync transfer size remaining Status of synchronization (percentage and timeremaining). For multi-LUN applications there is a

comma-separated list of values.

Sync transfer rate Data transfer rate during a replication

synchronization. For multi-LUN applications

there is a comma-separated list of values.

Source SP A interface ID of the interface on the SPA of the source

system for the replication.

Source SP B interface ID of the interface on the SPB of the source


Destination SP A interface ID of the interface on the SPA of the destinationsystem for the replication.

Destination SP B interface ID of the interface on the SPB of the destination


Previous transfer rate Previous transfer rate for the replication

session.

Average transfer rate Average transfer rate for the replication session.

Element pairs in the session For LUN group and VMware VMFS datastore

replications, the LUN element pairs within the

replication.

Create replication sessions

Create a replication session.

Prerequisites

Before creating a replication session, complete the following configuration tasks:

l Create the storage resource that provides the replication source.

l For local replication, create a replication destination on a local system.

l For remote replication, create a replication connection to a remote system, and create

a replication destination on that remote system.




37/54

Format/prot/rep/session create -srcRes [-srcSPAInterface

] [-srcSPBInterface ] dstType {local|remote dstSys } -dstRes [-dstSPAInterface ] [-dstSPBInterface ] [-name ] [-syncType {manual [autoInitiate {yes|no}]|[auto rpo ]]

Action qualifiers


-srcRes Type the ID of the storage resource to use as the source.

-srcSPAInterface Type the ID of the interface on the SPA of the source system forthe replication.

Note

This qualifier is used for replications on remote systems only. If

the qualifier is not specified, the system identifies the interface

automatically.

-srcSPBInterface Type the ID of the interface on the SPB of the source system forthe replication.

Note



automatically.

-dstType Specify the type of destination. Value is one of the following:

local - Maintain a full copy of the storage resource on the localsystem. This has advantages over snapshots in that a full copy,not just a copy of changes, is retained. remote - Maintain a fullcopy of the storage resource on a remote system by transferringthe data over the network. Remote replication is often used toensure that a copy is available at a remote site in case ofcatastrophic data loss, for example, due to natural disaster atthe local site.

-dstSys For remote replication, type the ID of the destination system.View settings for remote storage systems on page 29explainshow to view the IDs of the remote system configuration on thelocal system.

-dstRes Type the ID of the destination storage resource.


Create replication sessions 37


38/54


Note

To get the proper ID in the case of remote replication, you

should use a command that list resources on a local machine

with the -remSys qualifier. For example:

l uemcli /stor/prov/sf/res -remSys

show

l uemcli /stor/prov/iscsi/res -remSys

show

l uemcli /stor/prov/vmware/nfs -remSys

show

-dstSPAInterface Type the ID of the interface on the SPA of the destinationsystem for the replication.

Note



automatically.

-dstSPBInterface Type the ID of the interface on the SPB of the destinationsystem for the replication.

Note



automatically.

-syncType Specify how the source and destination will synchronize. Validvalues are:

l auto Data is replicated automatically in order to

maintain the desired Recovery Point Objective (RPO).

l manual Data will only be replicated when manually

initiated.

Note

As the RPO increases, the potential for data loss also increases,

as well as the amount of required protection space. Lowering

the RPO will reduce the amount of potential data loss, but will

also increase network traffic and may negatively impact

performance. The default RPO is one hour.

-autoInitiate Specify whether the system will perform the first replicationsynchronization automatically. Value is yes or no.




39/54


-rpo Type the time interval for when the synchronization will run.Use the following format:

[:MM]

Where:

l HH Type the number of hours. Range is 00-24 hours (1

day).

l MM Type the number of minutes, in 5 minute increments.

Range is 05 to 55.

Example

The following command creates a replication session with these settings:

l Source storage resource is file system RS_1.

l Destination system type is remote.

l Remote destination system is RS_2.

l Remote storage resource is file system LUN_2.

l Synchronization type is automatic.

l RPO is 2 hours and 30 minutes.

uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session

create -name REP1 -srcRes RS_1 dstType remote -dstSys RS_2 dstRes

LUN_2 syncType auto rpo 02h30m

Storage system address: 10.0.0.1

Storage system port: 443HTTPS connection

ID = 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000Operation completed successfully.

View replication sessions

View details about replication sessions. You can filter on the session ID.

Note

The show action command explains how to change the output format.

Format/prot/rep/session [{-id | -name | -res }]show

Object qualifier


-id Type the ID of the replication session.

-name Type the name of the replication session.

-res Type the ID of a local storage resource on the system to view the sessionsassociated with it.


View replication sessions 39


40/54

Example

The following command displays all replication sessions on the system:


show


1: ID =42949672967_FNM00134400082_0000_42949672967_FNM00131800278_0000 Name = REP1 Session type = lun Synchronization type = manual RPO = N/A Sync State = syncing Health state = OK (5) Operational status = Active (0x840d) Time of last sync = N/A

Sync status =Element pairs = N/A

Change replication session settings

Change the settings for a replication session.

Format/prot/rep/session {id | -name } set [-paused{yes|no [ -forceFullCopy ]}] [ -newName ] [ -srcSPAInterface ] [ -dstSPAInterface ] [ -srcSPBInterface ] [ -dstSPBInterface ] [ -syncType { manual | auto -rpo }]

Object qualifier


-id Type the ID of the replication session to change.

-name Type the name of the replication session to change.

Action qualifiers


-paused For automatic synchronization, specify to pause the session.Valid values are:

l yes

l no

-srcSPAInterface Type the ID of the interface on the SPA of the source system forthe replication.




41/54


Note



automatically.

-srcSPBInterface Type the ID of the interface on the SPB of the source system forthe replication.

Note



automatically.

-dstSPAInterface Type the ID of the interface on the SPA of the destination


Note



automatically.

-dstSPBInterface Type the ID of the interface on the SPB of the destinationsystem for the replication.

Note

This qualifier is used for replications on remote systems only. Ifthe qualifier is not specified, the system identifies the interface

automatically.

-syncType Specify how the source and destination will synchronize. Validvalues are:

l auto Data is replicated automatically in order to

maintain the desired Recovery Point Objective (RPO).

l manual Data will only be replicated when manually

initiated.

Note

As the RPO increases, the potential for data loss also increases,

as well as the amount of required protection space. Lowering

the RPO will reduce the amount of potential data loss, but will

also increase network traffic and may negatively impact

performance. The default RPO is one hour.

-rpo For automatic synchronization, type the time interval for whenthe synchronization will run. Use the following format:

[:MM]


Change replication session settings 41


42/54


Where:

l HH Type the number of hours. Range is 00-24 hours (1

day).

l MM Type the number of minutes, in 5 minute increments.Range is 05 to 55.

Example

The following command changes the source interface and destination interface forreplication session81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000:

uemcli /prot/rep/session id

81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000 set

srcSPAInterface if_1 srcSPBInterface if_2 dstSPAInterface if_3

dstSPBInterface if_4

Storage system address: 10.0.0.1Storage system port: 443HTTPS connectionID = 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000Operation completed successfully.

Delete replication sessions

Delete a replication session. The deletion process automatically synchronizes the sourcestorage resource with the destination storage resource, makes both read/write, and thendeletes the session. You can then connect a host to either storage resource.

Note

Once you delete a replication session, data from the source storage resource will no

longer be replicated on the destination, leaving the data unprotected.

Format/prot/rep/session {id | -name } delete

Object qualifier


-id Type the ID of the replication session to delete.

-name Type the name of the replication session to delete.

Example

The following command deletes replication session81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000:


id 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000

delete





43/54

HTTPS connection


Fail over replication sessions

Run this command on the destination system to perform a failover of a replicationsession, with possible data loss, in response to an emergency scenario in which thesource becomes unavailable.

After the failover, the destination system is read/write. To reestablish communicationbetween the source and destination, fail back the session that has failed over. Fail backreplication sessions on page 44explains how to fail back a replication session that hasfailed over.

Note

Failover operations terminate the transfer of data if there is a transfer in progress,

causing a potential loss of data. If the source site is still available when you perform a

failover, the system attempts to change the source storage resource from read/write toread-only.

Initiate a planned downtime

To initiate a planned downtime, run this command on the source system by specifyingthe -syncoption with the value yes. When you fail over a replication session from thesource system, the destination system is fully synchronized with the source to ensurethat there is no data loss. The destination storage resource can be used for providingaccess to the host.

Format/prot/rep/session { -id | -name } failover [-sync {yes | no}]

Object qualifier


-id Type the ID of the replication session to fail over.

-name Type the name of the replication session to fail over.

Action qualifier


-sync Specifies whether a synchronization needs to be performed before failingover the replication session. Valid values are:

l yes

l no

Note

You cannot use the valueyeswhen initiating a failover from the destination

system.


Fail over replication sessions 43


44/54

Example

The following command performs a fail over of replication session81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000:



failover



Fail back replication sessions

Fail back a replication session that has failed over. A failback results in the following:

l Synchronizes the destination and source storage resources.

l Makes the destination storage resource read-only.

l Makes the source storage resource read/write.

When the failback operation is complete, the replication session will resume and youmay connect your hosts to the source storage resource.

Note

Ensure that hosts do not write to the destination storage resource, which will become

read-only.

Format/prot/rep/session {id | -name } failback [-forceFullCopy]

Object qualifier


-id Type the ID of the replication session to fail back.

-name Type the name of the replication session to fail back.

Action qualifier


-forceFullCopy Specifies to force a full synchronization before the failbackoperation occurs.

Note

You may lose the common base on the source storage resource as

a result of the event that caused the original failover. If there is no

longer a common base for the source storage resource, a full

synchronization is required. For such cases, ensure that you

specify this qualifier.




45/54

Example

The following command performs a fail back of replication session81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000:



failback



Associated CLI commands

The show action command

The showaction command displays a list of objects that exist on the system and the

attributes of those objects. You can specify an object qualifier to view the attributes for asingle object. The showaction command provides qualifiers for changing the display of

the output, including the format and the attributes to include. The available outputformats are name-value pair (NVP), table, and comma-separated values (CSV).

Formatuemcli [] [] show [{-detail | -brief | -filter ] [-output {nvp | table [-wrap] | csv}]

Action qualifier


-output|-o Specify the output format. Value is one of the following:

l nvp The name-value pair (NVP) format displays output as

name=value. Name-value pair format on page 46provides an

example of the NVP format.

l table The table format displays output as a table, with column

headers and rows. By default, values that are too long to fit in acolumn are cut off. Add -wrapafter the table qualifier, separated

by a space, so that the values wrap. Table format on page 46provides an example of the table format.

l csv The comma-separated values (CSV) format is similar to the

table format, but the names and values are separated by commas.Comma-separated values format on page 46provides anexampleof the CSV format.

-detail Display all attributes.

-brief Display only the basic attributes (default).

-filter Comma-separated list of attributes which are included into thecommand output.


Associated CLI commands 45


46/54

Name-value pair format

1: ID = la0_SPA SP = SPA Ports = eth0_SPA,eth1_SPA Health state = OK (5)

2: ID = la0_SPB SP = SPB Ports = eth0_SPB,eth1_SPB Health state = OK (5)

Table format

ID | SP | Ports | Health state--------+-----+-------------------+--------------la0_SPA | SPA | eth0_SPA,eth1_SPA | OK (5)la0_SPB | SPB | eth0_SPB,eth1_SPB | OK (5)

Comma-separated values format

ID,SP,Ports,Health statela0_SPA,SPA,eth0_SPA,eth1_SPA,OK (5)la0_SPB,SPB,eth0_SPB,eth1_SPB,OK (5)

Example

The following command modifies the set of attributes in the show action output. Forexample, if you add -filter"ID,ID,ID,ID" to the command, in the output you will see

four lines with the "ID" attribute for each listed instance:

1: ID = la_0 ID = la_0 ID = la_0 ID = la_0

uemcli /net/nas/server show -filter ID, SP, Health state, ID, Name

Filter format


1: ID = nas_1 SP = SPA Health state = OK (5) ID = nas_1 Name = Mynas1

2: ID = nas_2 SP = SPA Health state = OK (5) ID = nas_2 Name = Mynas2

Manage Ethernet ports

View and change the settings for the network ports on each SP.

The following table describes the port attributes.




47/54

Table 12

Network port attributes


ID ID of the port.

Name Name of the port.

SP Name of the SP on which the port resides. Value is SPA or SPB.

Protocol Types of protocols the port supports. Value is one of the following:

l mgmt Management interface.

l file Network interface for Windows (CIFS) and Linux/UNIX (NFS)

storage.

l iscsi iSCSI interface for iSCSI storage.

Manage interfaces on page 22explains how to configure network

interfaces on the system.

MTU size Maximum transmission unit (MTU) packet size (in bytes) that the port can

transmit. Default is 1500 bytes per packet.

Requested MTU

sizeMTU size set by the user.

Available MTU

sizeList of available MTU sizes.

Speed Current link speed of the port.

Requested speed Link speed set by the user.

Available

speeds

List of available speed values.

Health state Health state of the port. The health state code appears in parentheses.

Value is one of the following:

l Unknown (0) Status is unknown.

l OK (5) Port is operating normally.

l OK BUT (7) Lost communication, but the port is not in use.

l Minor failure (15) Lost communication. Check the network

connection and connected cables.

l Major failure (20) Port has failed. Replace the SP that

contains the port.

Health details Additional health information. See Appendix A, Reference, for health

information details.

Aggregated port

IDIf the port is in a link aggregation, the ID of the link aggregation appears.

Manage link aggregations on page 49explains how to configure link

aggregations on the SP ports.

Connector type Physical connector type. Valid values are:

l unknown

l RJ45

l LC


Manage Ethernet ports 47


48/54

Table 12

Network port attributes (continued)


l MiniSAS_HD

View Ethernet port settings

View details about the network ports. You can filter on the port ID.

Note


Format/net/port/eth [-id ] show

Object qualifier


-id Type the ID of the port.

Example

uemcli /net/port/eth show


1: ID = spa_mgmt

Name = mgmt SP = spa Protocols = mgmt MTU size = 1500 Speed = 100 Mbps Health state = OK (5) Aggregated port ID =

2: ID = spa_eth0 Name = eth0 SP = spa Protocols = file, iscsi MTU size = 1500 Speed = 10 Gbps Health state = OK (5) Aggregated port ID = la0_SPA

3: ID = spa_eth1 Name = eth1 SP = spa Protocols = file, iscsi MTU size = 9000 Speed = 1 Gbps Health state = OK (5) Aggregated port ID = la0_SPA

4: ID = spa_iom_0_eth0 Name = eth2 SP = spa Protocols = file, iscsi MTU Size = 9000




49/54

docu61141 configuring asynchronous replication

Documents