• Configure replication using the CLI

    PDF

    On this page

    Configure replication using the CLI

    Manage network interfaces

    Create interfaces to enable and control access between the system, the network, and configured 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:

    • iSCSI interfaces for controlling access to iSCSI storage. You assign the interface to an iSCSI node.
    • Replication interfaces for replication-related data or management traffic.

    The system configures each interface on a pair of symmetrical SP ports. The interface can be moved between SPs. You have the option of indicating which SP the interface will use, either a physical port or a link aggregation port. You also have the option of specifying a virtual LAN (VLAN) ID, for communicating with VLAN networks.

    Each interface is identified by an ID.

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

    Table 1. Interface attributes
    Attribute Description
    ID ID of the interface.
    Type Interface type. Value is one of the following:
    • iscsi — Interface for iSCSI storage.
    • 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.
    Health state A numerical value indicating the health of the system. Value is one of the following:
    • Unknown (0)
    • OK (5)
    • OK BUT (7)
    • Degraded/Warning (10)
    • Minor failure (15)
    • Major failure (20)
    Health details Additional health information.

    Create interfaces

    Create an interface.

    Format

    /net/if create [ -async ] [-vlanId <value>] -type { iscsi | replication} -port <value> -addr <value> [-netmask <value>] [-gateway <value>]

    Action qualifier

    Qualifier Description
    -async Run the creation operation in asynchronous mode.
    -type Specify the interface type. Value is one of the following:
    • iscsi — Interface for iSCSI storage.
    • replication — Interface for replication-related data or management traffic.
    -port Specify the ID of the SP port or link aggregation that will use the interface.
    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 Specify the virtual LAN (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.
    -addr Specify the IP address for the interface. The prefix length should be appended to the IPv6 address and, if omitted, will default to 64. For IPv4 addresses, the default length is 24. The IPv4 netmask may be specified in address attribute after slash.
    -netmask Specify the subnet mask for the interface.
    NOTE This qualifier is not required if the prefix length is specified in the -addr attribute.
    -gateway Specify the gateway for the interface.
    NOTE This qualifier configures the default gateway for the specified port’s SP.

    Example

    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.1
    Storage system port: 443
    HTTPS connection
    
    ID = IF_1
    Operation completed successfully.

    View interfaces

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

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

    Format

    /net/if [ {-id <value> | -port <value> | -type <value>} ] show

    Object qualifier

    Qualifier Description
    -id Type the ID of an interface.
    -port Type the port the interface is associated with.
    -type Specify the type of the interface. Valid values are:
    • iscsi
    • replication

    Example

    The following command displays the details of all interfaces on the system.

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/if show -detail
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    1:     ID                      = if_0
           Type                    = file
           NAS server              = nas_0
           Port                    = eth0_spa
           VLAN ID                 = 0
           IP address              = 3ffe:80c0:22c:4e:a:0:2:7f/64
           Subnet mask             = 
           Gateway                 = fe80::20a8bff:fe5a:967c
           IPv4 mode               = 
           IPv4 address            = 
           IPv4 subnet mask        = 
           IPv4 gateway            = 
           IPv6 mode               = static
           IPv6 address            = 3ffe:80c0:22c:4e:a:0:2:7f/64
           IPv6 link-local address = 
           IPv6 gateway            = fe80::20a8bff:fe5a:967c
           MAC address             = EA:3E:22:3F:0C:62
           SP                      = spa
           Preferred               = yes
    
    2:     ID                      = if_1
           Type                    = file
           NAS server              = nas_1
           Port                    = eth1_spb
           VLAN ID                 = 1
           IP address              = 192.168.1.2
           Subnet mask             = 255.255.255.0
           Gateway                 = 192.168.1.254
           IPv4 mode               = static
           IPv4 address            = 192.168.1.2
           IPv4 subnet mask        = 255.255.255.0
           IPv4 gateway            = 192.168.1.254
           IPv6 mode               = 
           IPv6 address            = 
           IPv6 link-local address = 
           IPv6 gateway            = 
           MAC address             = EA:3E:22:21:7A:78
           SP                      = spa
           Preferred               = yes
    
    3:     ID                      = if_2
           Type                    = replication
           NAS server              =
           Port                    = eth1_spb
           VLAN ID                 =
           IP address              = 10.103.75.56
           Subnet mask             = 255.255.248.0
           Gateway                 = 10.103.72.1
           IPv4 mode               = static
           IPv4 address            = 10.103.75.56
           IPv4 subnet mask        = 255.255.248.0
           IPv4 gateway            = 10.103.72.1
           IPv6 mode               =
           IPv6 address            =
           IPv6 gateway            =
           MAC address             = EA:3E:22:6D:BA:40
           SP                      = spb
           Preferred               = no

    Change interface settings

    Change the settings for an interface.

    Format

    /net/if -id <value> set [-vlanId <value>] [-addr <value>] [-netmask <value>] [-gateway <value>]

    Object qualifier

    Qualifier Description
    -id Type the ID of the interface to change.

    Action qualifier

    Qualifier Description
    -vlanId Type the virtual LAN (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 on VLANs.
    -addr Specify the IP address for the interface.
    NOTE The prefix length should be appended to the IPv6 address. The IPv4 netmask may be specified in address attribute after the slash.
    -netmask Specify the IPv4 subnet mask for the interface.
    -gateway Specify the gateway for the interface.
    NOTE The gateway is optional for both IPv4 and IPv6. This qualifier configures the default gateway for the specified port’s SP.

    Example

    The following command changes the gateway address for interface IF_1:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456!/net/if –id IF_1 set -gateway 2001:db8:0:170:a:0:2:70
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    ID = IF_1
    Operation completed successfully.

    Delete interfaces

    Delete an interface.

    NOTE Deleting an interface can break the connection between systems that use it, such as configured hosts.

    Format

    /net/if –id <value> delete

    Object qualifier

    Qualifier Description
    -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
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    Operation completed successfully.

    Manage remote storage systems

    Configure 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 remote system 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:

    Table 1. Remote system attributes
    Attribute Description
    ID ID of the remote system.
    Name Name of the remote system.
    Address Network name or management IP address of the remote system.
    Alternate management address An alternative management IP address of the remote system.
    Operational status Operational status of the session. The operational status code appears in parentheses.
    • Unknown (0x0)
    • OK (0x2)
    • Lost Communication (0xD)
    • Update Needed (0x8406)
    • Updating (0x8407)
    • Failed to Validate (0x840C)
    • Lost sync Communication (0x840D)
    Model Model number of the remote system.
    Serial number Serial number of the remote system.
    Health state Health state of the storage resource. The health state code appears in parentheses. Value is one of the following:
    • OK (5)—Resource is operating normally.
    • Degraded/Warning (10)—Working, but one or more of the following may have occurred:
      • One or more of its storage pools are degraded.
      • Its replication session is degraded.
      • Its replication session has faulted.
      • It has almost reached full capacity. Increase the primary storage size, or create additional resources to store your data, to avoid data loss.
    • Minor failure (15)—One or both of the following may have occurred:
      • One or more of its storage pools have failed.
      • The associated iSCSI node has failed.
    • Major (20)—One or both of the following may have occurred:
      • Resource is unavailable.
      • One or more of the associated storage pools have failed.
    • Critical failure (25)—One or more of the following may have occurred:
      • One or more of its storage pools are unavailable.
      • Resource is unavailable.
      • Resource has reached full capacity. Increase the primary storage size, or create additional resources to store your data, to avoid data loss.
    • Non-recoverable error (30)—One or both of the following may have occurred:
      • Resource is unavailable.
      • One or more of the associated storage pools are unavailable.
    Health details Additional health information.
    Source user name For storage systems that are the source in a replication session, the username that is used to access the system.
    Source user password For storage systems that are the source in a replication session, the user password that is used to access the system.
    Local interfaces The list of local interface identifiers used to create the interconnection between the two systems.
    Remote interfaces The list of remote interface identifiers used to create the interconnection between two systems.
    Destination user name For storage systems that are the destination in a replication session, the username that is used to access the system.
    Destination user password For storage systems that are the destination in a replication session, the user password that is used to access the system.
    Connection type The type of connection with the remote system. Valid values are:
    • sync
    • async
    • both
    Synchronous FC ports The fibre channel ports enabled for synchronous replication.
    NOTE For a local system (RS_0), this field will appear empty only when there are no FC ports. For remote systems, this will be empty when the connection type is asynchronous.
    Bandwidth schedules The bandwidth schedules for asynchronous replication sessions with source role having data transfer due to RPO or manual sync on this remote system.
    NOTE This attribute is used for async or both connection types only. If not configured, "not configured" is displayed. For sync connection type, N/A is displayed.
    Current bandwidth Current bandwidth calculated based on the configured bandwidth schedules and the schedule time zone for asynchronous replications on this remote system.
    NOTE This attribute is used for async or both connection types only. If no bandwidth schedules configured, "uses available bandwidth "is displayed.For sync connection type, N/A is displayed.

    Create remote system configurations

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

    NOTE For a source VNX system with two control stations, the home directory of the sysadmin user, which is used in configuring the import connection, must exist on the primary control station of the VNX.

    Format

    /remote/sys create -addr <value> [-type VNX] -srcUsername <value> {-srcPassword <value> | -srcPasswordSecure} -dstUsername <value> {-dstPassword <value> | -dstPasswordSecure} [-connectionType {sync | async | both}] [ -bandwidthSchedules <value> ]

    Action qualifiers

    Qualifier Description
    -addr Specify the network name or IP address of the remote system.
    -type Specify the remote system type. Valid values are:
    • VNX
    -srcUsername For systems that are the source in a replication, type the username that is used to access the system.
    -srcPassword For systems that are the source in a replication, type the user password that is used to access the system.
    -srcPasswordSecure Specify the password in secure mode. Once you run the command with this qualifier, you will be asked to type the password separately.
    -dstUsername For systems that are the destination in a replication session or VNX in an import session, specify the username that is used to access the system.
    -dstPassword For systems that are the destination in a replication session or VNX in an import session, specify the user password that is used to access the system.
    -dstPasswordSecure Specify the password in secure mode. Once you run the command with this qualifier, you will be asked to type the password separately.
    -connectionType Specify this qualifier to indicate the type of replication connection. Valid values are:
    • async
    • sync
    • both
    -bandwidthSchedules (async or both connection types only) Specify a schedule during which to cap bandwidth. Type the following to specify the schedule [{Sun|Mon|Tue|Wed|Thu|Fri|Sat}][HH-HH][/<bandwidth>], where:
    • Sun|Mon|Tue|Wed|Thu|Fri|Sat - days of the week to run the schedule
    • HH-HH - start and end time for the schedule
    • /<bandwidth> - value at which to cap bandwidth, in KBps

    Example

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

    • Network address is 10.60.10.10.
    • Includes access credentials for when the system is the source or destination.
    • Limits bandwidth to 2,000 KB/s from 7 A.M. to 6 P.M. Monday through Friday. Otherwise, bandwidth is limited to 8,000 KB/s.

    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.60.10.10 -srcUsername LocalAdmin ‑srcPassword LocalAdminPassword -dstUsername RemAdmin -dstPassword RemAdminPassword -connectionType async -bandwidthSchedules MonTueWedThuFri7-18/2000,/8000
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    ID = RS_1
    Operation completed successfully.

    View settings for remote storage systems

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

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

    Format

    /remote/sys [-id <value>] show

    Object qualifier

    Qualifier Description
    -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 -detail
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    1:    ID                   = RS_0
          Name                 = FNM00151702099
          Address              = 10.245.252.229
          Model                = Unity 300 (Local System)
          Serial number        = FNM00151702099
          Connection type      = async
          Source interfaces    = N/A
          Local interfaces     = N/A
          Remote interfaces    = N/A
          Operational status   = OK (0x2)
          Health state         = OK (5)
          Health details       = "Communication with the replication host is established. No action is required."
          Synchronous FC ports = spa_fc4, spb_fc4
          Bandwidth schedules  = MonTueWedThuFri7-18/2000,/8000
          Current bandwidth    = 8000
    
    
    2:    ID                   = RS_1
          Name                 = FNM00151702100
          Address              = 10.244.205.127
          Model                = Unity 300
          Serial number        = FNM00151702100
          Connection type      = sync
          Source interfaces    = 10.245.252.231, 10.245.252.232
          Local interfaces     = 10.245.252.231, 10.245.252.232
          Remote interfaces    = 10.244.205.131, 10.244.205.132
          Operational status   = OK (0x2)
          Health state         = OK (5)
          Health details       = "Communication with the replication host is established. No action is required."
          Synchronous FC ports = spa_iom_0_fc0, spb_iom_0_fc0
          Bandwidth schedules  = N/A
          Current bandwidth    = N/A
    
    

    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 <value> verify

    Object qualifier

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

    Example

    The following command verifies remote system configuration RS_1:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /remote/sys –id RS_1 verify
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    Operation completed successfully.

    Change settings for remote storage systems

    Changes the configuration settings for a remote system.

    NOTE If a replication connection already exists and you plan to add a different mode of file replication, do not attempt to create a new connection. Change the existing replication connection mode to Both. Also, ensure that you have the appropriate interface types configured to support both asynchronous replication (eth2, eth3) and synchronous replication (sync replication mgmt port).

    Format

    /remote/sys -id <value> set [-addr <value>] [-dstUsername <value> {-dstPassword <value> | -dstPasswordSecure}] [-connectionType {sync | async | both}] [-bandwidthSchedules <value>]

    Object qualifier

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

    Action qualifiers

    Qualifier Description
    -addr Type the network name or management IP address of the remote system.
    -dstUsername Type the username that is used to access the remote system.
    -dstPassword Type the user password that is used to access the remote system.
    -dstPasswordSecure Specify the password in secure mode. The user is prompted to specify the password.
    -connectionType Specify this qualifier to indicate the type of replication connection. Valid values are:
    • async
    • sync
    • both
    -bandwidthSchedules (async or both connection types only) Specify a schedule during which to cap bandwidth. Type the following to specify the schedule [{Sun|Mon|Tue|Wed|Thu|Fri|Sat}][HH-HH][/<bandwidth>], where:
    • Sun|Mon|Tue|Wed|Thu|Fri|Sat - days of the week to run the schedule
    • HH-HH - start and end time for the schedule
    • /<bandwidth> - value at which to cap bandwidth, in KBps
    Leave blank to delete an existing bandwidth schedule.

    Example

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

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /remote/sys –id RS_1 set –addr “10.64.74.2” -dstUsername Local/joe -dstPassword Password456!
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    ID = RS_1
    
    Operation completed successfully.

    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 <value> delete

    Object qualifier

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

    Example

    The following command deletes remote system configuration RS_1:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /remote/sys –id RS_1 delete
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    Operation completed successfully.

    Cabinet level unplanned failover of replication sessions

    Execute a failover of all NAS server synchronous replication sessions from the remote system to the local system (unplanned failover). Replication sessions of file systems created on the affected NAS servers will also fail over automatically.

    Format

    /remote/sys -id <value> failover [-force]

    Object qualifiers

    Qualifier Description
    -id Type the ID of the remote system from which to failover its NAS server synchronous replication sessions.

    Action qualifiers

    Qualifier Description
    -force Specifies whether to skip checking the network connection to the remote system. Required when the network connection is healthy. No values are allowed.

    Example

    The following command executes a cabinet level unplanned failover replication operation issued for a Unity system:

    uemcli /remote/sys -id RS_1 failover
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    ID = RS_1
    Operation completed successfully.
    NOTE After an unplanned failover, the NAS servers and file systems on the original source system must be updated to reflect the new status. If there is a large number of NAS servers and file systems, this change may take several minutes to complete. During this period, resume and failback operations of the synchronous replication sessions will not work. It is recommended to wait for all of the updates to complete before running a resume or failback operation. There is no impact to data access while this update is occurring.

    Manage replication sessions

    Storage 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 source storage data and periodically updates the copy, keeping it consistent with the source data. Storage replication provides an enhanced level of redundancy in case the main storage backup system fails. As a result:

    • Downtime associated cost of a system failure is minimized.
    • Recovery process from a natural or human-caused disaster is facilitated.

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

    It is important to note that when replicating from a Unity system running a later OE version (for example, OE 4.1.x) to a Unity system running an earlier version (for example, OE 4.0.x), you cannot have new OE version features enabled on the source.

    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 1. Replication session attributes
    Attribute Description
    ID ID of the session.
    Name Name of the replication session.
    Session type Storage type of the session. Valid values are:
    • lun
    • block
    • file
    • nas server
    Synchronization type Type of synchronization. Valid values are:
    • auto—Data is replicated automatically in order to maintain the desired Recovery Point Objective (RPO).
    • manual—Data will only be replicated when manually initiated.
    • sync—Data is synchronously replicated with RPO=0.
    NOTE For asynchronous replication, the potential for data loss increases as the RPO 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 Recovery Point Objective (RPO) interval for automatic synchronization. For synchronous replication, the RPO is set to 0 automatically.
    Resource type Type of storage resource to which the replication session is applied. Valid values are:
    • LUN
    • LUN group
    • File System
    • VMware VMFS
    • VMware NFS
    • NAS Server
    Sync State Additional state of the replication session, specific to the replication mode.
    • For asynchronous replication, valid values are:
      • idle—No active syncing. Beginning with OE 5.x, you can change replication session attributes while the session is in an Idle state.
      • manual—User initiated syncing.
      • auto syncing—System initiated syncing.
    • For synchronous replication, valid values are:
      • unknown—Unknown sync state.
      • out of sync—Destination is out of sync with the source.
      • in sync—Destination is an exact copy of the source.
      • consistent—Destination is a point in time copy of the source.
      • syncing—System initiated syncing.
      • inconsistent—Destination is not a point in time copy of the source.
    Health state Health state of the session. Valid values are:
    • Unknown—Session health cannot be determined.
    • OK—Session is operating normally.
    • Degraded/Warning—An error has caused one or more of the following:
      • Session has been paused.
      • 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 back online, you can fail back the session to return it to normal operation.
      • Session is syncing.
    • Minor failure—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.
    • Critical failure— Session has encountered an error that has halted the session.
    NOTE If the replication session is in an error state, in addition to resolving the issue (for example, destination pool out of space), try pausing, and then resuming the replication session. If the problem persists, delete and then create the replication session again.
    Health details Additional health information.
    Operational status Operational status of the session. The operational status code appears in parentheses.
    • Unknown (0x0)
    • Non Recoverable Error (0x7)
    • Lost Communication (0xd)
    • Failed Over with Sync (0x8400)
    • Failed Over (0x8401)
    • Manual Syncing (0x8402)
    • Paused (0x8403)
    • Idle (0x8404)
    • Auto Sync Configured (0x8405)
    • Destination Extend Failed Not Syncing (0x840B)
    • Destination Extend In Progress (0x840C)
    • Active (0x840D)
    • Lost Sync Communication (0x840E)
    • Syncing (0x8411)
    Source status Status of the source storage resource in the session. Valid values are:
    • Unknown—Source status is unknown.
    • OK—Source is operating normally.
    • Paused—Replication session for the source is currently paused.
    • Fatal replication issue—Source has experienced a critical error and the replication session has stopped. Delete the replication session and re-create it.
    • 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 either side could also interrupt communication.
    • Failed over—The replication session has failed over to the destination site. In a failed over state, the destination object is read/write. When communication is reestablished between the source and destination, the source is shown as Restricted Replication Access = Yes. To resume operations on the source site, the replication session needs to be failed back.
    • Switched over—The replication session has switched over to the source site. In a switched over state, the source object is read/write. When communication is reestablished between the source and destination, the destination is shown as Restricted Replication Access = Yes. To resume operations on the destination site, the replication session needs to be failed over.
    Destination status Status of the destination storage resource in the session. Valid values are:
    • Unknown—Status of the destination resource is unknown.
    • OK—Destination resource is operating normally.
    • Paused—Replication session for destination resource is currently paused.
    • Fatal replication issue—Destination has experienced a critical error and the replication session has stopped. Delete the replication session and re-create it.
    • 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 either side could also interrupt communication.
    • Failed over—The replication session has failed over to the destination site. In a failed over state, the destination object is read/write. When communication is reestablished between the source and destination, the source is shown as Restricted Replication Access = Yes. To resume operations on the source site, the replication session needs to be failed back.
    • Switched over—The replication session has switched over to the source site. In a switched over state, the source object is read/write. When communication is reestablished between the source and destination, the destination is shown as Restricted Replication Access = Yes. To resume operations on the destination site, the replication session needs to be failed over.
    Network status Status of the network connection. Valid values are:
    • Unknown—Network status is currently unknown. If you continue to see this value, check the network connections.
    • OK—Network connection is operating normally.
    • 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 (lost IP) between the systems. A change in the network configuration on either side could also interrupt communication.
    • Lost Sync Communication—Fiber Channel communication with the synchronous replication remote system has been lost. It is likely that the Fiber Channel connection has encountered issues.
    Destination type Type of destination used in the session. Valid values are:
    • 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.
    • 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 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.
    Local role The local system role. Valid values are:
    • Unknown—Status of the local system is unknown.
    • Source—Resource on the local system is replicated to the remote system.
    • Destination—Resource on the local system is the replication destination of the resource on the remote system.
    • Loopback—Resources participating in the replication session are located on the same storage system.
    • 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.
    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 system for the replication.
    Destination resource ID of the storage resource on which the data is replicated.
    Destination SP A interface ID of the interface on the SPA of the destination system for the replication.
    Destination SP B interface ID of the interface on the SPB of the destination system for the replication.
    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.
    NOTE For synchronous replication, the percentage is reported when the replication is in the Syncing state.
    Sync transfer rate Synchronization transfer rate when the session is in the syncing state. For multi-LUN applications there is a comma-separated list of values.
    NOTE This attribute is valid for asynchronous replications only.
    Sync transfer size remaining Remaining size to be transferred during synchronization. For multi-LUN applications there is a comma-separated list of values.
    NOTE This attribute is valid for asynchronous replications only.
    Previous transfer rate Previous average transfer rate for the replication session.
    NOTE This attribute is valid for asynchronous replications only.
    Average transfer rate Average transfer rate for the replication session.
    NOTE This attribute is valid for asynchronous replications only.
    Element pairs For consistency group and VMware VMFS datastore replications, the LUN element pairs within the replication.
    Hourly snapshot keep for Amount of time to keep replicated hourly snapshots on the destination. Output can be:
    • Blank when scheduled snapshots are not replicated.
    • <value><qualifier>—When a retention duration is specified, where:
      • value—An integer value. If the qualifier is h (hours), the valid range is from 1 to 42840. If the qualifier is d (days), the valid range is from 1 to 1785.
      • qualifier—A value qualifier. The valid values are:
        • h (hours)
        • d (days)
    • Forever—When -keepFor value is not specified and allow auto-delete is requested
    • Same as source—Keep the destination retention policy the same as the source retention policy
    NOTE This attribute is valid for asynchronous replications only.
    Hourly snapshot allow auto-delete Whether or not the destination pool's auto-delete policy allows replicated hourly snapshots on the destination to be deleted. Output can be:
    • Blank when scheduled snapshots are not replicated.
    • Same as source—Keep the destination retention policy the same as the source retention policy
    • yes—When -allowAutoDelete is set
    • no—When -keepFor is set
    NOTE This attribute is valid for asynchronous replications only.
    Daily snapshot keep for Amount of time to keep replicated daily snapshots on the destination. Output can be:
    • Blank when scheduled snapshots are not replicated.
    • value—An integer value. If the qualifier is h (hours), the valid range is from 1 to 42840. If the qualifier is d (days), the valid range is from 1 to 1785.
    • qualifier—A value qualifier. The valid values are:
      • h (hours)
      • d (days)
    • Same as source—Keep the destination retention policy the same as the source retention policy
    NOTE This attribute is valid for asynchronous replications only.
    Daily snapshot allow auto-delete Whether or not the destination pool's auto-delete policy allows the replicated daily snapshots on the destination to be deleted. Output can be:
    • Blank when scheduled snapshots are not replicated.
    • Same as source—Keep the destination retention policy the same as the source retention policy
    • yes—When -allowAutoDelete is set
    • no—When -keepFor is set
    NOTE This attribute is valid for asynchronous replications only.
    Allow Async Snap Replication (file system asynchronous replication sessions only) Indicates whether or not to allow snap replication in asynchronous replication sessions. Values are:
    • yes--Allow snap replication in asynchronous sessions.
    • no--Disallow snap replication in asynchronous sessions.
    Cascade Replicated Snap Whether or not to repli cate snap in the cascade replication session.
    • yes-- When snap is replicated from the inbound session, it will be automatically replicated in this replication session.
    • no-- When snap is replicated from the inbound session, it will not be automatically replicated in this replication session.
    NOTE This qualifier is used for file system asynchronous replications only.

    Create replication sessions

    Ensure you have completed the necessary configuration tasks before creating a replication session.

    For asynchronous replication, you can replicate existing snapshots and snapshots that are created from snapshot schedules.

    For synchronous file replication, you cannot replicate existing snapshots or snapshots that are created from snapshot schedules.

    NOTE Snapshots that have been created and attached as well as read/write (share) snapshots (as opposed to read-only checkpoint snapshots) are not eligible for replication. Only unattached (read-only) snapshots are eligible for replication.

    The following conditions apply to snapshot replication:

    • Asynchronous replication: You can replicate existing snapshots and snapshots that are created from snapshot schedules.
    • Synchronous file replication: You cannot replicate existing snapshots or snapshots that are created from snapshot schedules.

      You can only replicate those snapshots and snapshots that are created from snapshot schedules after you have established the synchronous replication session and it is Active.

    NOTE On a NAS server protected by replication, you must create a replication session for each file system on it. Otherwise, file system-related configurations like shares and exports may be lost after a NAS server replication session failover.

    Performing a snapshot replication from a source system running OE version 4.0, 4.1, 4.2, 4.3, or 4.4 to a destination system running OE version 5.x requires upgrading the source system to OE version 4.5 first. Upgrading to OE version 4.5 is not required but recommended if you want to perform LUN or file system replication from OE version 4.0, 4.1, 4.2, 4.3, or 4.4 to OE version 5.0 without any snapshot replication.

    Prerequisites

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

    • Create the storage resource that provides the replication source.
    • For local replication, create a replication destination on a local system.
    • For remote replication, create a replication connection to a remote system, and create a replication destination on that remote system.
    • For asynchronous replication in a co-existing asynchronous and synchronous replication with one source resource topology, create the asynchronous replication destination NAS server with both the -replDest and the -backupOnly attributes set to yes. These attributes must be set to yes on the asynchronous replication destination NAS server when the source NAS server is synchronous-replicated; otherwise, the asynchronous replication session cannot be created.

    Format

    /prot/rep/session create [-async] -srcRes <value> [-srcSPAInterface <value>] [-srcSPBInterface <value>] –dstType {local | remote –dstSys <value>} -dstRes <value> [-dstSPAInterface <value>] [-dstSPBInterface <value>] [-name <value>] [-elementPairs <value>] [-syncType {manual [–autoInitiate {yes | no}] | auto [–rpo <value>]}[-replicateHourlySnaps {yes [{-keepSameAsSource | -keepFor <value> | -allowAutoDelete}] | no}] [-replicateDailySnaps {yes [{-keepSameAsSource | -keepFor <value> | -allowAutoDelete}] | no}] [-replicateExistingSnaps] [-allowAsyncSnapReplication {yes | no}] [enableUserSnapCommonBase {-autosearch | -srcCommonBaseSnap <value> -dstCommonBaseSnap <value> [-skipSnapSignatureCheck]}]

    Action qualifiers

    Qualifier Description
    -async Run an action in asynchronous mode.
    -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 for the replication.
    NOTE This qualifier is used for asynchronous 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 for the replication.
    NOTE This qualifier is used for asynchronous replications on remote systems only. If the qualifier is not specified, the system identifies the interface automatically.
    -dstType Specify the type of destination. Valid values are:
    • 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.
    • 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 if there is catastrophic data loss, for example, due to natural disaster at the local site.
    -dstSys For remote replication, type the ID of the destination system. View settings for remote storage systems explains how to view the IDs of the remote system configuration on the local system.
    -dstRes Type the ID of the destination storage resource.
    -dstSPAInterface Type the ID of the interface on the SPA of the destination system for the replication.
    NOTE This qualifier is used for asynchronous replications on remote systems only. If the qualifier is not specified, the system identifies the interface automatically.
    -dstSPBInterface Type the ID of the interface on the SPB of the destination system for the replication.
    NOTE This qualifier is used for asynchronous replications on remote systems only. If the qualifier is not specified, the system identifies the interface automatically.
    -syncType Specify how the source and destination synchronize. Valid values are:
    • auto—Data is replicated automatically in order to maintain the wanted Recovery Point Objective (RPO).
    • manual—Data is only be replicated when manually initiated.
    NOTE

    This qualifier is used for asynchronous replications only.

    As the RPO increases, the potential for data loss also increases, and the amount of required protection space. Lowering the RPO reduces the amount of potential data loss, but also increases network traffic and may negatively impact performance. The default RPO is one hour.

    -autoInitiate Specify whether the system performs the first replication synchronization automatically. Valid values are:
    • yes
    • no
    NOTE This qualifier is used for asynchronous replications only.
    -rpo Type the time interval for when the synchronization runs. Use the following format:

    <HH>[:MM]

    Where:
    • HH—Type the number of hours. Range is 00-24 hours (1 day).
    • MM—Type the number of minutes, in 5 minute increments. Range is 05 to 55.
    For synchronous replication, specify the value 0. Once it is set, the value cannot be reset from zero to nonzero or from nonzero to zero.
    -replicateHourlySnaps Specify whether to mark hourly scheduled snapshots for replication. Valid values are:
    • yes
    • no
    NOTE This qualifier is used for asynchronous replications only.
    -replicateDailySnaps Specify whether to mark daily scheduled snapshots for replication. Valid values are:
    • yes
    • no
    NOTE This qualifier is used for asynchronous replications only.
    -keepSameAsSource Indicate whether to use the same retention policy (expiration time and auto-delete) of the source for the destination. This option propagates changes that are made to the source retention policy to the destination retention policy (from that point forward for newly created scheduled snapshots, old snapshots are left as is). No values are allowed.

    This option is enabled by default if -keepFor or -allowAutoDelete are not set.

    NOTE This qualifier is used for asynchronous replications only.
    -keepFor Specifies the retention time after which the snapshot is deleted on the destination. The interval can be defined in days or hours. Use the following format:

    <value><qualifier>

    Where:
    • value—An integer value. If the qualifier is h (hours), the valid range is from 1 to 42840. If the qualifier is d (days), the valid range is from 1 to 1785.
    • qualifier—A value qualifier. The valid values are:
      • h (hours)
      • d (days)
    NOTE This qualifier is used for asynchronous replications only.
    -allowAutoDelete Specify whether auto delete is allowed on the replicated copy of this snapshot or snapshot set.
    NOTE This qualifier is used for asynchronous replications only.
    -replicateExistingSnaps Indicates whether to replicate snapshots that exist on the source resource. This qualifier is a one-time option available during session creation that replicates snapshots existing on the source at that moment in time.
    NOTE This qualifier is used for asynchronous replications only.

    Only the user snapshots that are created after the common base snapshots were established and are in the Idle or Pending state are replicated.

    All eligible snapshots are replicated with the source retention policy applied for the destination retention policy. For a snapshot to be eligible for this option, it must meet these 3 criteria:
    • The snapshot is created by either the user or a snapshot schedule.
    • The snapshot is read-only (file resource snapshot must be a checkpoint snapshot; block resource snapshot must not be attached).
    • The snapshot is not currently undergoing deletion.
    -allowAsyncSnapReplication Indicate whether snapshot replication is allowed in an asynchronous session. Valid values are:
    • yes
    • no
    NOTE This qualifier is used for file system asynchronous replications only.
    -enableUserSnapCommonBase Designate the user snapshot as the common base for Unity systems running OE version 5.1.

    If this qualifier is absent, the system does not treat the user snapshot as the common base.

    NOTE This qualifier must be set when the replication session is configured.
    -srcCommonBaseSnap Specify the user snapshot identifier that is used as the common base on the source resource for Unity systems running OE version 5.1.
    -dstCommonBaseSnap Specify the user snapshot identifier that is used as the common base on the destination resource for Unity systems running OE version 5.1.
    -autosearch Enable the system to perform an automatic search to find a user snapshot that can be used as a common base for Unity systems running OE version 5.1.

    If this qualifier is not included, the -autosearch function is disabled.

    NOTE This qualifier must be set when the replication session is configured if you want to avoid a full copy after a failover.
    -skipSnapSignatureCheck Indicate whether you want to skip the user snap signature check when using the user snapshot as the common base for Unity systems running OE version 5.1. This qualifier is valid only when specifying the source and destination user snapshots as the common base.
    NOTE Check if the user snapshots are qualified as a common base.
    -cascadeReplicatedSnap Indicates whether you want to automatically replicate snapshots downstream when the snapshot is replicated from the inbound replication session.

    The valid values are as follows:

    • yes
    • no (default)
    -overwriteDestination Indicate whether to overwrite dirty data on the destination; it takes more time to complete full data transfer. If this qualifier is not specified, the destination might contain different data than the source if the destination has corrupted data.

    Example

    The following command creates a replication session with these settings:

    • Source storage resource is file system RS_1.
    • Destination system type is remote.
    • Remote destination system is RS_2.
    • Remote storage resource is file system LUN_2.
    • Synchronization type is automatic.
    • 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: 443
    HTTPS connection
    
    ID = 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000
    Operation 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 <value> | -name <value> | -res <value>}] show

    Object qualifiers

    Qualifier Description
    -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 sessions associated with it.

    Example 1

    The following command displays all replication sessions on the system:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session show
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    1:     ID                   = 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000
           Name		               = MyRep1
           Session type         = block
           Synchronization type = manual
           RPO                  =
           Sync State           = idle
           Health state         = OK (5)
           Operational status   = Idle (0x8404)
           Time of last sync    =
           Sync status          =
           Element pairs        = sv_4 => sv_4
     

    Example 2

    The following command displays all replication sessions on the system and their details:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session show -detail
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    1:    ID                                = 42949672965_FCNCH0972DDD67_0000_42949672967_FCNCH0972DDD67_0000
          Name                              = rep_sess_sv_1_sv_2_local
          Session type                      = lun
          Synchronization type              = manual
          RPO                               =
          Resource type                     = LUN
          Sync State                        = idle
          Health state                      = OK (5)
          Health details                    = "This replication session is operating normally. No action is required."
          Operational status                = Idle (0x8404)
          Source status                     = OK
          Destination status                = OK
          Network status                    = OK
          Destination type                  = local
          Destination system                = local
          Local role                        = Local
          Source resource                   = sv_1
          Source SP-A interface             = N/A
          Source SP-B interface             = N/A
          Destination resource              = sv_2
          Destination SP-A interface        = N/A
          Destination SP-B interface        = N/A
          Time of last sync                 = N/A
          Sync status                       =
          Sync transfer rate                = N/A
          Sync transfer size remaining      = 0
          Previous transfer rate            = N/A
          Average transfer rate             = N/A
          Element pairs                     = N/A
          Hourly snapshot keep for          = 3h 
          Hourly snapshot allow auto-delete = no
          Daily snapshot keep for           = not replicated
          Daily snapshot allow auto-delete  = not replicated
          Allow Async Snap Replication      = N/A
          Cascade Replicated Snap           = no
    

    Change replication session settings

    Change the settings for a replication session.

    Format

    /prot/rep/session {–id <value> | -name <value>} set [-async] [-newName <value>] [-srcSPAInterface <value>] [-dstSPAInterface <value>] [-srcSPBInterface <value>] [-dstSPBInterface <value>] [-syncType {manual | auto -rpo <value>}] [-replicateHourlySnaps {yes [{-keepSameAsSource | -keepFor <value> | -allowAutoDelete}] | no}] [-replicateDailySnaps {yes [{-keepSameAsSource | -keepFor <value> | -allowAutoDelete}] | no}] [-allowAsyncSnapReplication {yes [-cascadeReplicatedSnap {yes | no}] | no}]

    Object qualifiers

    Qualifier Description
    -id Type the ID of the replication session to change.
    -name Type the name of the replication session to change.

    Action qualifiers

    Qualifier Description
    -async Run an action in asynchronous mode.
    -newName Type the new name of the replication session.
    -srcSPAInterface Type the ID of the interface on the SPA of the source system for the replication.
    NOTE This qualifier is used for asynchronous 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 for the replication.
    NOTE This qualifier is used for asynchronous replications on remote systems only. If the qualifier is not specified, the system identifies the interface automatically.
    -dstSPAInterface Type the ID of the interface on the SPA of the destination system for the replication.
    NOTE This qualifier is used for asynchronous replications on remote systems only. If the qualifier is not specified, the system identifies the interface automatically.
    -dstSPBInterface Type the ID of the interface on the SPB of the destination system for the replication.
    NOTE This qualifier is used for asynchronous replications on remote systems only. If the qualifier is not specified, the system identifies the interface automatically.
    -syncType Specify how the source and destination synchronize. Valid values are:
    • auto—Data is replicated automatically in order to maintain the wanted Recovery Point Objective (RPO).
    • manual—Data only is replicated when manually initiated.
    NOTE

    This qualifier is used for asynchronous replications only.

    As the RPO increases, the potential for data loss also increases, and the amount of required protection space. Lowering the RPO reduces the amount of potential data loss, but also increases network traffic and may negatively impact performance. The default RPO is one hour.

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

    <HH>[:MM]

    Where:
    • HH—Type the number of hours. Range is 00-24 hours (1 day).
    • MM—Type the number of minutes, in 5 minute increments. Range is 05 to 55.
    NOTE For synchronous replication, specify the value 0. The value cannot be reset from zero to nonzero or from nonzero to zero.
    -replicateHourlySnaps Specify whether to mark hourly scheduled snapshots for replication. Valid values are:
    • yes
    • no
    NOTE This qualifier is used for asynchronous replications only.
    -replicateDailySnaps Specify whether to mark daily scheduled snapshots for replication. Valid values are:
    • yes
    • no
    NOTE This qualifier is used for asynchronous replications only.
    -keepSameAsSource Specify whether to use the same retention policy (expiration time and auto-delete) of the source for the destination. This option propagates changes that are made to the source retention policy to the destination retention policy (from that point forward for newly created scheduled snapshots, old snapshots are left as is). No values are allowed.
    NOTE This qualifier is used for asynchronous replications only.
    -keepFor Specify the retention time after which the snapshot is deleted on the destination. The interval can be defined in days or hours. Use the following format:

    <value><qualifier>

    Where:
    • value—An integer value. If the qualifier is h (hours), the valid range is from 1 to 42840. If the qualifier is d (days), the valid range is from 1 to 1785.
    • qualifier—A value qualifier. The valid values are:
      • h (hours)
      • d (days)
    NOTE This qualifier is used for asynchronous replications only.
    -allowAutoDelete
    NOTE Only valid when -replicateHourlySnaps yes or -replicateDailySnaps yes.
    Specify whether auto delete is allowed on the replicated copy of this snapshot or snapshot set. Valid values are:
    • yes
    • no
    NOTE This qualifier is used for asynchronous replications only.
    -allowAsyncSnapReplication Indicates whether to allow snapshot replication in asynchronous session. Valid values are:
    • yes
    • no
    -cascadeReplicatedSnap Indicates whether to replicate snapshots in the cascade replication session. This qualifier can only be modified when the session is active. Valid values are:
    • yes
    • no (default)

    Example

    The following command changes the source interface and destination interface for replication session 81604378625_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.1
    Storage system port: 443
    HTTPS connection
    
    ID = 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000
    Operation completed successfully.

    Pause replication sessions

    Pause a replication session.

    Format

    /prot/rep/session {-id <value> | -name <value>} pause [-async]

    Object qualifiers

    Qualifier Description
    -id Type the ID of the replication session to be paused.
    -name Type the name of the replication session to be paused.

    Action qualifiers

    Qualifier Description
    -async Run an action in asynchronous mode.

    Example

    The following command pauses replication session 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000:

    uemcli /prot/rep/session –id 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000 pause
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    Operation completed successfully.

    Resume replication sessions

    Resumes an existing replication session.

    Format

    /prot/rep/session {–id <value> | -name <value>} resume [-async] [-forceFullCopy] [-allowFullCopy] [-srcSPAInterface <value>] [-dstSPAInterface <value>] [-srcSPBInterface value>] [-dstSPBInterface <value>] [-forceSyncData]

    Object qualifiers

    Qualifier Description
    -id Type the ID of the replication session that you want to resume.
    -name Type the name of the replication session that you want to resume.

    Action qualifiers

    Qualifier Description
    -async Run an action in asynchronous mode.
    -allowFullCopy

    This qualifier specifies that a full synchronization can occur if there is no common base snapshot when an asynchronous replication session is resumed.

    The -allowFullCopy option is not supported when a synchronous replication session resumes after a pause operation. The full copy is performed with the same behavior with -allowFullCopy specified for synchronous file replication if the session has no common base snapshots, and neither -allowFullCopy nor -forceFullCopy is specified.

    If the source system has snapshots that were created before you upgraded your system to Unity 5.1.2 and those snapshots are used as common base snapshots, those snapshots trigger a full synchronization. Beginning with Unity 5.1.2, common base snapshots have signatures that allow delta synchronization to occur.

    NOTE This qualifier does not support synchronous block replications.
    -forceFullCopy This qualifier specifies that a full synchronization occurs when an asynchronous replication session is resumed.

    The --forceFullCopy option is not supported when a synchronous replication session resumes after a pause operation.

    NOTE This qualifier does not support synchronous block replications.
    -srcSPAInterface Type the ID of the interface on the SPA of the source system for the replication.
    NOTE This qualifier is used for asynchronous replications on remote systems only. If the qualifier is not specified, the system identifies the interface automatically.
    -dstSPAInterface Type the ID of the interface on the SPA of the destination system for the replication.
    NOTE This qualifier is used for asynchronous 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 for the replication.
    NOTE This qualifier is used for asynchronous replications on remote systems only. If the qualifier is not specified, the system identifies the interface automatically.
    -dstSPBInterface Type the ID of the interface on the SPB of the destination system for the replication.
    NOTE This qualifier is used for asynchronous replications on remote systems only. If the qualifier is not specified, the system identifies the interface automatically.
    -forceSyncData This qualifier forces a data transfer from the source system to the remote system. This transfer occurs even if the remote system has data that is not replicated from the source system.
    NOTE This qualifier is used for asynchronous replications only.

    Example

    The following command resumes the replication session 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000:

    uemcli /prot/rep/session –id 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000 resume
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    ID = 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000
    Operation completed successfully.

    Manually synchronize replication sessions

    Manually synchronize a replication session.

    Format

    /prot/rep/session{–id <value> | -name <value>} sync [-async]

    Object qualifiers

    Qualifier Description
    -id Type the ID of the replication session to synchronize.
    -name Type the name of the replication session to synchronize.

    Action qualifiers

    Qualifier Description
    -async Run an action in asynchronous mode.

    Example

    The following command initiates a manual resynchronization of replication session REPS_1:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session –id REPS_1 sync
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    Operation completed successfully.

    Delete replication sessions

    Delete a replication session. The deletion process automatically synchronizes the source storage resource with the destination storage resource, makes both read/write, and then deletes the session. You can then connect a host to either storage resource. Deleting the session from the source system automatically removes the destination and source replication sessions. This ensures that you do not have to manually delete the associated storage resources or NAS servers from the destination system.

    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. When deleting a file system synchronous replication session, though the session is deleted, if the initial synchronization does not complete, the destination file system will run into an unrecoverable error. In this case, delete the destination file system.

    Format

    /prot/rep/session {–id <value> | -name <value>} delete [-async]

    Object qualifiers

    Qualifier Description
    -id Type the ID of the replication session to delete.
    -name Type the name of the replication session to delete.

    Action qualifiers

    Qualifier Description
    -async Run an action in asynchronous mode.

    Example

    The following command deletes replication session 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session –id 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000 delete
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    Operation completed successfully.

    Fail over replication sessions

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

    After the failover, the destination system is read/write. To reestablish communication between the source and destination, fail back the session that has failed over. Fail back replication sessions explains how to fail back a replication session that has failed 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 to read-only.

    Initiate a planned downtime

    To initiate a planned downtime, run this command on the source system by specifying the -sync option with the value yes. When you fail over a replication session from the source system, the destination system is fully synchronized with the source to ensure that there is no data loss. The destination storage resource can be used for providing access to the host.

    Format

    /prot/rep/session {-id <value> | -name <value>} failover [-async] [-sync {yes | no}] [-force]

    Object qualifiers

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

    Action qualifiers

    Qualifier Description
    -async Run an action in asynchronous mode.
    -sync For an asynchronous replication session, specifies whether a synchronization needs to be performed before failing over the replication session. For a synchronous replication session, specifies whether to keep synchronization on the reversed direction after failing over the session. Valid values are:
    • yes—For a planned failover. Can only be issued from the source system. Where –sync is not specified, this is the default value for a local replication session or session where role=source.
    • no—For an unplanned failover. Can only be issued from the destination system. Where –sync is not specified, this is the default value for a remote replication session or session where role=destination.
      NOTE If the Network status=OK, the source system is probably OK. The command issued from the destination system without this option will fail. It is recommended to rerun the command using the yes option from the source system. However, in that case, the command issued from the destination system using the no option is still allowed.
    -force Specifies whether to skip a pre-check operation on file systems of a NAS server when a replication failover operation is issued from the source NAS server. No values are allowed.

    Example

    The following command performs a fail over of replication session 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session –id 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000 failover
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    Operation completed successfully.

    Fail back replication sessions

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

    • Synchronizes the destination and source storage resources
    • Makes the destination storage resource read-only
    • Makes the source storage resource read/write

    When the failback operation is complete, the replication session resumes and you may connect your hosts to the source storage resource.

    NOTE Ensure that hosts do not write to the destination storage resource, which becomes read-only.

    Format

    /prot/rep/session {–id <value> | -name <value>} failback [-async] [-forceFullCopy] [-allowFullCopy] [-force] [-syncData {force | ignore}]

    Object qualifiers

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

    Action qualifiers

    Qualifier Description
    -async Run an action in asynchronous mode.
    -allowFullCopy This qualifier specifies that a full synchronization can occur after a failback if there is no common base snapshot when an asynchronous replication session is resumed.

    The -allowFullCopy option is not supported when a synchronous replication session resumes after a pause operation. The full copy is performed with the same behavior with -allowFullCopy specified for synchronous file replication if the session has no common base snapshots, and neither -allowFullCopy nor --forceFullCopy is specified.

    If the source system has snapshots that were created before you upgraded your system to Unity 5.1.2 and those snapshots are used as common base snapshots, those snapshots trigger a full synchronization. Beginning with Unity 5.1.2, common base snapshots have signatures that allow delta synchronizations to occur.

    NOTE This qualifier does not support synchronous block replications.
    -forceFullCopy This qualifier specifies that a full synchronization occurs when an asynchronous replication session is resumed.

    The -forceFullCopy option is not supported when a synchronous replication session resumes after a pause operation.

    NOTE This qualifier does not support synchronous block replications.
    -force Before failing back a NAS server synchronous replication session, it is checked whether its associated asynchronous file system replication sessions are all preserved when coexisting. When this qualifier is specified, that check is skipped.
    -syncData Specifies the behavior of transferring data from the source system to the remote system. If the qualifier is not specified, the command fails if the remote system has data that are not replicated from the source system. Valid values are:
    • force – Force data transfer from the source system to the remote system, even if the remote system has out-of-sync data.
    • ignore – Skip data transfer from the source system to the remote system and trigger the replication session reverse from the remote system to the source system.
    NOTE This qualifier is used for asynchronous replications only.

    Example

    The following command performs a fail back of replication session 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /prot/rep/session –id 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000 failback
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    Operation completed successfully.

    Preserve asynchronous replication sessions

    Initiates a preserve asynchronous replication sessions operation on a NAS server synchronous replication session. After a NAS server synchronous replication session fails over or fails back with its file system synchronous replication sessions, the asynchronous replication sessions will be switched to the new production site by the preserve asynchronous replication sessions operation.

    Format

    /prot/rep/session {-id <value> | -name <value>} preserveAsync [ -dstSys <value> ]

    Object qualifiers

    Qualifier Description
    -id Identifies the NAS server synchronous replication session.
    -name Identifies the NAS server synchronous replication session by name.
    -dstSys Identifies the remote system which will be selected as NAS server asynchronous replication session destination system for preservation. This qualifier must be specified when there are multiple replication sessions.

    Example

    The following command preserves asynchronous replication sessions for 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000:

    uemcli /prot/rep/session –id 81604378625_FCNCH097274B3A_0000_81604378627_FCNCH097274B37_0000 preserveAsync
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    Operation completed successfully.

    Use common base snapshots

    Referencing a common base snapshot enables you to avoid a full copy when performing a failback operation to the original source after an unplanned failover.

    If an unplanned failover interrupts a file system replication session, the common base snapshot enables you to re-create that session.

    Snapshot precheck attributes

    Attribute Description
    Session ID ID of the file synchronous replication session.
    Session name Name of the file synchronous replication session.
    Source common base snapshot ID ID of the common base snapshot on the source site.
    Source common base snapshot name Name of the common base snapshot on the source site.
    Destination common base snapshot ID ID of the common base snapshot on the destination site.
    Destination common base snapshot name Name of the common base snapshot on the destination site.

    Run a precheck for existing common base snapshots

    Find common base snapshots on a NAS server or in a file replication session before you perform a failback operation. Using existing common base snapshots allows you to use the avoid full copy feature and perform a delta synchronization. This type of synchronization sends only data that has changed after the failover back to the source system.

    Common base snapshots can be snapshots that were created according to an established schedule. Common base snapshots can also be manually created snapshots of both the source and destination systems.

    NOTE The precheck can only be performed with the CLI. It cannot be performed in the Unisphere UI.

    Format

    /prot/rep/session/commonbase {-session <value> | -sessionName <value>} show -detail

    Object qualifiers

    Qualifier Description
    -session Identifies the replication session by ID number.
    -sessionName Identifies the replication session by an assigned name.
    -detail Show snapshot details.

    Example

    The following example shows a check for common base snapshots in a synchronous file replication session.

    uemcli /prot/rep/session/commonbase –session 171798691845_FCNCH097274B3A_0000_171798691846_FCNCH097274B37_0000 show -detail
    
    [Response]
    Storage system address: 10.64.75.201
    Storage system port: 443
    HTTPS connection
    
    1:    Session ID                            = 171798691845_FCNCH097274B3A_0000_171798691846_FCNCH097274B37_0000
          Session name                          = Rep1
          Source common base snapshot ID        = 171798691846
          Source common base snapshot name      = Snap1
          Destination common base snapshot ID   = 171798691848
          Destination common base snapshot name = Snap1
    
    ID = 171798691845_FCNCH097274B3A_0000_171798691846_FCNCH097274B37_0000
    Operation completed successfully.

    Re-create a replication session

    You can re-create a replication session if the source and destination systems share a common base snapshot.

    Both synchronous and asynchronous replication sessions can be re-created. The following sessions of each type can be re-created:

    • Synchronous file system sessions
    • Asynchronous file system sessions
    • Asynchronous block sessions

    The following types of synchronous and asynchronous replication sessions cannot be re-created:

    • Synchronous block sessions
    • Synchronous NAS server sessions
    • Asynchronous NAS server sessions

    Format

    /prot/rep/session create [-async] -srcRes <value> -dstType remote -dstSys <value> -dstRes <value> -syncType auto -rpo 0 -enableUserSnapCommonBase -autoSearch -srcCommonBaseSnap <value> -dstCommonBaseSnap <value>

    Object qualifiers

    Qualifier Description
    -async Run an action in asynchronous mode.
    -srcRes Type the ID of the storage resource to use as the source.
    -dstType Specify the type of destination. Valid values are:
    • local—Maintain a full copy of the storage resource on the local system. This option has advantages over snapshots in that a full copy, not just a copy of changes, is retained.
    • 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 if there is catastrophic data loss, for example, due to natural disaster at the local site.
    -dstSys For remote replication, type the ID of the destination system. View settings for remote storage systems explains how to view the IDs of the remote system configuration on the local system.
    -dstRes Type the ID of the destination storage resource.
    -syncType Specify how the source and destination synchronize. Valid values are:
    • auto—Data is replicated automatically in order to maintain the wanted Recovery Point Objective (RPO).
    • manual—Data is replicated when manually initiated.
    NOTE

    This qualifier is used for asynchronous replications only.

    As the RPO increases, the potential for data loss also increases, and the amount of required protection space. Lowering the RPO reduces the amount of potential data loss, but also increases network traffic and may negatively impact performance. The default RPO is one hour.

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

    <HH>[:MM]

    where:
    • HH—Type the number of hours. Range is 00-24 hours (1 day).
    • MM—Type the number of minutes, in 5 minute increments. Range is 05–55.
    For synchronous replication, specify the value 0. Once the value is set, it cannot be reset from zero to nonzero or from nonzero to zero.
    -enableUserSnapCommonBase Designate the user snapshot as the common base for Unity systems running OE version 5.1.

    If this qualifier is absent, the system does not treat the user snapshot as the common base.

    NOTE This qualifier must be set when the replication session is configured if you want to avoid a full copy when re-creating the session.
    -autosearch Enable the system to perform an automatic search to find the user snapshot was designated as the common base snapshot for Unity systems running OE version 5.1.

    If this qualifier is not included, the -autosearch function is disabled.

    NOTE This qualifier must be set when the replication session is configured if you want to avoid a full copy when re-creating the session.
    -srcCommonBaseSnap Specify the user snapshot identifier that is used as the common base on the source resource for Unity systems running OE version 5.1.
    NOTE This qualifier must be set when the replication session is configured if you want to avoid a full copy after a failover.
    -dstCommonBaseSnap Specify the user snapshot identifier that is used as the common base on the destination resource for Unity systems running OE version 5.1.
    NOTE This qualifier must be set when the replication session is configured if you want to avoid a full copy after a failover.

    The show action command

    The show action 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 a single object. The show action command provides qualifiers for changing the display of the output, including the format and the attributes to include. The available output formats are name-value pair (NVP), table, and comma-separated values (CSV).

    Format

    uemcli [<switches>] <object> [<object qualifier>] show [{-detail | -brief | -filter <value>] [-output {nvp | table [-wrap] | csv}]

    Action qualifier

    Qualifier Description
    -output|-o Specify the output format. Value is one of the following:
    • nvp — The name-value pair (NVP) format displays output as name=value. Name-value pair format provides an example of the NVP format.
    • table — The table format displays output as a table, with column headers and rows. By default, values that are too long to fit in a column are cut off. Add -wrap after the table qualifier, separated by a space, so that the values wrap. Table format provides an example of the table format.
    • 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 provides an example of the CSV format.
    -detail Display all attributes.
    -brief Display only the basic attributes (default).
    -filter Comma-separated list of attributes which are included into the command output.

    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 state
    la0_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. For example, 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

    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    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.

    Table 1. Network port attributes
    Attribute Description
    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.
    Protocols Types of protocols the port supports. Value is one of the following:
    • mgmt — Management interface.
    • file — Network interface for Windows (SMB) and Linux/UNIX (NFS) storage.
    • iscsi — iSCSI interface for iSCSI storage.
    Manage network interfaces explains 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 size MTU size set by the user.
    Available MTU size List of available MTU sizes.
    NOTE This can display as either a comma-separate list of exact values (if there is an iSCSI interface on the port), or an interval defined by the minimum or maximum values, such as 1280-9216.
    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:
    • Unknown (0) — Status is unknown.
    • OK (5) — Port is operating normally.
    • OK BUT (7) — Lost communication, but the port is not in use.
    • Minor failure (15) — Lost communication. Check the network connection and connected cables.
    • 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 ID If the port is in a link aggregation, the ID of the link aggregation appears. Manage link aggregations explains how to configure link aggregations on the SP ports.
    Connector type Physical connector type. Valid values are:
    • unknown
    • RJ45
    • LC
    • MiniSAS_HD
    • CopperPigtail
    • NoSeparableConnector
    MAC address Unique identifier assigned to a network device for communications on a network segment.
    SFP supported speeds List of supported speed values of the inserted Small Form-factor Pluggable.
    SFP supported protocols List of supported protocols of the inserted Small Form-factor Pluggable. Valid values are:
    • unknown
    • FibreChannel
    • Ethernet
    • SAS

    View Ethernet port settings

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

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

    Format

    /net/port/eth [-id <value>] show

    Object qualifier

    Qualifier Description
    -id Type the ID of the port.

    Example

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/port/eth show -detail
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    1:    ID                      = spa_eth2
          Name                    = SP A Ethernet Port 2
          SP                      = spa
          Protocols               = file, net, iscsi
          MTU size                = 4500
          Requested MTU size      = 4500
          Available MTU sizes     = 1280-9216
          Linux device name       = eth2
          Speed                   = 1 Gbps
          Requested speed         = auto
          Available speeds        = 1 Gbps, 10 Gbps, 100 Mbps, auto
          Health state            = OK (5)
          Health details          = "The port is operating normally."
          Aggregated port ID      = None
          FSN port ID             = None
          Connector type          = RJ45
          MAC address             = 00:60:16:7A:7F:CF
          SFP supported speeds    =
          SFP supported protocols =
    
    2:    ID                      = spa_eth3
          Name                    = SP A Ethernet Port 3
          SP                      = spa
          Protocols               = file, net, iscsi
          MTU size                = 1500
          Requested MTU size      = 1500
          Available MTU sizes     = 1500, 9000
          Linux device name       = eth3
          Speed                   = 1 Gbps
          Requested speed         = auto
          Available speeds        = 1 Gbps, 10 Gbps, 100 Mbps, auto
          Health state            = OK (5)
          Health details          = "The port is operating normally."
          Aggregated port ID      = None
          FSN port ID             = None
          Connector type          = RJ45
          MAC address             = 00:60:16:7A:7F:CE
          SFP supported speeds    =
          SFP supported protocols =

    Change Ethernet port settings

    NOTE The new settings are applied to a pair of symmetrical ports on dual SP systems.

    Change the maximum transmission unit size and port speed for an Ethernet port.

    Format

    /net/port/eth -id <value> set [-mtuSize <value>] [-speed <value>]

    Object qualifier

    Qualifier Description
    -id Type the ID of the network port.

    Action qualifier

    Qualifier Description
    -mtuSize Type the maximum transmission unit packet size (in bytes) for the port:
    • If an Ethernet port carries File interfaces only, the MTU size can be set to a custom value between 1280 and 9216.
    • If an Ethernet port carries iSCSI interfaces, the allowed MTU sizes are 1500 and 9000.
    Specific I/O modules may also restrict allowed range for MTU size value. The MTU size values of 1500 bytes (default) and 9000 bytes (jumbo frame) are supported by all interfaces and I/O modules.
    -speed Type the port speed.

    Example

    The following command sets the MTU size for Ethernet port 0 (eth0) on SP A to 9000 bytes:

    uemcli /net/port/eth –id spa_eth0 set –mtuSize 9000
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    ID = spa_eth0
    ID = spb_eth0
    Operation completed successfully.

    Manage FC ports

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

    The following table describes the port attributes.

    Table 1. FC port attributes
    Attribute Description
    ID ID of the port.
    Name Name of the port.
    SP Name of the SP on which the port resides.
    WWN World Wide Name (WWN) of the port.
    Speed Current link speed of the port.
    Requested speed Link speed set by the user.
    Available speed 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:
    • Unknown (0) — Status is unknown.
    • OK (5) — Port is operating normally.
    • OK BUT (7) — Lost communication, but the port is not in use.
    • Minor failure (15) — Lost communication. Check the network connection and connected cables.
    • 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.
    Connector type Physical connector type. Valid values are:
    • unknown
    • RJ45
    • LC
    • MiniSAS_HD
    • CopperPigtail
    • NoSeparableConnector
    SFP supported speeds List of supported speed values of the inserted Small Form-factor Pluggable.
    SFP supported protocols List of supported protocols of the inserted Small Form-factor Pluggable. Valid values are:
    • unknown
    • FibreChannel
    • Ethernet
    • SAS
    Replication capability Type of replication capability. Valid values are:
    • Sync replication
    • RecoverPoint

    View FC port settings

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

    Format

    /net/port/fc [-id <value>] show

    Object qualifier

    Qualifier Description
    -id Type the ID of the port.

    Example

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/port/fc show -detail
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    1:     ID                      = spa_fc4
           Name                    = SP A FC Port 4
           SP                      = spa
           WWN                     = 50:06:BD:01:60:05:8E:50:06:01:64:3D:E0:05:8E
           Speed                   = 1 Gbps
           Requested speed         = auto
           Available speeds        = 4 Gbps, 8 Gbps, 16 Gbps, auto
           Health state            = OK (5)
           Health details          = "The port is operating normally."
           SFP supported speeds    = 4 Gbps, 8 Gbps, 16 Gbps
           SFP supported protocols = FibreChannel
           Replication capability  = Sync replication
           SFP supported mode      = Multimode

    Change port settings

    Change the speed for an FC port.

    Format

    /net/port/fc -id <value> set -speed <value>

    Object qualifier

    Qualifier Description
    -id Type the ID of the FC port.

    Action qualifier

    Qualifier Description
    -speed Type the port speed. Available speed attribute contains the list of valid values.
    NOTE The port will be link down temporarily during change of speed.

    Example

    The following command sets the speed for FC port fc1 on SP A to 1 Gbps:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/port/fc –id spa_fc1 set –speed 1Gbps
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    ID = spa_fc1
    Operation completed successfully.

    Manage link aggregations

    Link aggregation lets you link physical ports (for example, port 0 and port 1) on a SP to a single logical port and therefore lets you use up to four Ethernet ports on the SP. If your system has two SPs, and you link two physical ports, the same ports on both SPs are linked for redundancy. For example, if you link port 0 and port 1, the system creates a link aggregation for these ports on SP A and a link aggregation on SP B.

    Each link aggregation is identified by an ID.

    NOTE The cabling on SP A must be identical to the cabling on SP B, or you cannot configure link aggregation.

    Link aggregation has the following advantages:

    • Increases overall throughput since two physical ports are linked into one logical port.
    • Provides basic load balancing across linked ports since the network traffic is distributed across multiple physical ports.
    • Provides redundant ports so that if one port in a linked pair fails, the system does not lose connectivity.
    NOTE With link aggregation, both linked ports must be connected to the same switch and the switch must be configured to use link aggregation that uses the Link Aggregation Control Protocol (LACP). The documentation that came with your switch should provide more information on using LACP.

    The following table describes the attributes for link aggregation.

    Table 1. Link aggregation attributes
    Attribute Description
    ID ID of the link aggregation. The ID is a combination of the link ID and the SP that contains the linked ports.
    Ports IDs of the linked physical ports. The port names include the name of the SP that contains the ports.
    SP Name of the SP on which the ports are linked. Valid values are:
    • SPA
    • SPB
    MTU size Maximum transmission unit (MTU) packet size (in bytes) for the linked ports. Default is 1500 bytes per packet.
    Linux device name Linux network device name.
    FSN port ID ID of the FSN port to which the link aggregation belongs, if it is part of an FSN.
    Available MTU size List of available MTU sizes.
    NOTE This displays as an interval defined by the minimum and maximum values, for example: 1280-9216.
    Health state Health state of the link aggregation. The health state code appears in parentheses. Value is one of the following:
    • Unknown (0) — Status is unknown.
    • OK (5) — Working correctly.
    • OK BUT (7) — Lost connection, but the link aggregation is not in use.
    • Degraded/Warning (10) — Working and performing all functions, but the performance may not be optimum.
    • Minor failure (15) — Working and performing all functions, but overall performance is degraded. This condition has a minor impact on the system and should be remedied at some point, but does not need to be fixed immediately.
    • Major failure (20) — Failing and some or all functions may be degraded or not working. This condition has a significant impact on the system and should be remedied immediately.
    • Critical failure (25) — Failed and recovery may not be possible. This condition has resulted in data loss and should be remedied immediately.
    • Non-recoverable error (30) — Completely failed and cannot be recovered.
    Health details Additional health information.

    View link aggregations

    View details about link aggregations. You can filter on the link aggregation ID.

    Format

    /net/la [-id <value>] show

    Object qualifier

    Qualifier Description
    -id Type the ID of the link aggregation.

    Example

    The following command shows the link aggregations on the system, in this case, for both SPA and SPB:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/la show -detail
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    1:    ID                  = spa_la_0_2
          SP                  = spa
          Ports               = spa_iom_0_eth2, spa_iom_0_eth3
          FSN port ID         = None
          MTU size            = 3456
          Available MTU sizes = 1280-9216
          Linux device name   = bond12
          Health state        = OK (5)
          Health details      = "The component is operating normally. No action is required."
          Operational status  =
    
    2:    ID                  = spb_la_0_2
          SP                  = spb
          Ports               = spb_iom_0_eth2, spb_iom_0_eth3
          FSN port ID         = None
          MTU size            = 3456
          Available MTU sizes = 1280-9216
          Linux device name   = bond12
          Health state        = OK (5)
          Health details      = "The component is operating normally. No action is required."
          Operational status  =

    Create link aggregations

    Create a link aggregation by linking two physical ports on an SP to create a logical port.

    Format

    /net/la create –ports <value> [-mtuSize <value>]

    Action qualifier

    Qualifier Description
    -ports Type the IDs of the physical ports to link on the SP. Separate the IDs with a comma. For example, to link ports 0 and 1 on SPA, type: eth0_SPA,eth1_SPA.
    -mtuSize Type the MTU size (in bytes) for the linked ports. The MTU size can be set to a custom value between 1280 and 9216.

    Specific I/O modules may restrict allowed range for MTU size value. The MTU size values of 1500 bytes (default) and 9000 bytes (jumbo frame) are supported by all interfaces and I/O modules.

    Example

    The following command links port 0 and port 1 on SPA with the default MTU size. The system has two SPs, so port 0 and port 1 on SPB are also linked, which results in two link aggregation IDs:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/la create -ports "eth0_SPA,eth1_SPA"
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    ID = la0_SPA
    ID = la0_SPB
    Operation completed successfully.

    Change link aggregations

    Change the settings of a link aggregation.

    Format

    /net/la -id <value> set [-ports <value>] [-mtuSize <value>]

    Object qualifier

    Qualifier Description
    -id Type the ID of the link aggregation to change.

    Action qualifier

    Qualifier Description
    -ports Type the IDs of the physical ports to link on the SP. Separate the IDs with a comma. For example, to link ports 0 and 1 on SPA, type: eth0_SPA,eth1_SPA
    -mtuSize Type the MTU size (in bytes) for the linked ports. The MTU size can be set to a custom value between 1280 and 9216.

    Specific I/O modules may restrict allowed range for MTU size value. The MTU size values of 1500 bytes (default) and 9000 bytes (jumbo frame) are supported by all interfaces and I/O modules.

    Example

    The following command changes the MTU size for link aggregation la0_SPA to 9000 bytes. The system has two SPs, so MTU size is updated for both link aggregation IDs:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/la –id la0_SPA set –mtuSize 9000
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    ID = la0_SPA
    ID = la0_SPB
    Operation completed successfully.

    Delete link aggregations

    Delete a link aggregation.

    Format

    /net/la [-id <value>] delete

    Object qualifier

    Qualifier Description
    -id Type the ID of the link aggregation to delete.

    Example

    The following command deletes link aggregation la0_SPA. The system has two SPs, so link aggregation la0_SPB is also deleted:

    uemcli -d 10.0.0.1 -u Local/joe -p MyPassword456! /net/la –id la0_SPA delete
    Storage system address: 10.0.0.1
    Storage system port: 443
    HTTPS connection
    
    ID = la0_SPA
    ID = la0_SPB
    Operation completed successfully.
    Questions?
    We're here to help.
    From offering expert advice to solving complex problems, we've got you covered.