Configuration Mode Commands
  
Configuration Mode Commands
This chapter is a reference for configuration mode commands. It includes the following sections:
•  System commands
•  SteelFusion Core commands (both modes)
•  SteelFusion Core iSCSI (block mode) commands
•  SteelFusion Core NFS (file mode) commands
•  SteelFusion Core Hyper-V mode commands
•  SteelFusion Edge commands (both modes)
•  SteelFusion Edge iSCSI (block mode) commands
•  SteelFusion Edge NFS (file mode) commands
•  SteelFusion Edge Hyper-V mode commands
You can perform configuration tasks while in configuration mode. Only administrator users can enter configuration mode and enable mode commands. All commands available in user mode and enable mode are also available in configuration mode. Monitor users cannot perform configuration tasks.
To enter configuration mode
•  Connect to the CLI and enter the enable and configure terminal commands:
login as: admin
SteelFusion Core
Last login: Wed Jan 20 13:02:09 2017 from 10.0.1.1
core01 > enable
core01 # configure terminal
core01 (config) #
You are now in configuration mode.
To exit configuration mode, enter exit.
For an alphabetical list of commands, see the index at the end of this document.
System commands
This section describes commands you use to perform system administration tasks.
alarm clear
Clears the specified alarm type.
Syntax
alarm <type> clear
Parameters
<type>
Type of alarm. See the alarm enable (Core) command for a complete listing and description of alarm types.
Usage
Use this command to clear the status of the specified alarm type. If you clear an alarm and the error condition still exists, the alarm might be triggered again immediately. If you need to clear an alarm permanently, use the no alarm enable command.
Example
amnesiac (config) # alarm secure_vault_unlocked clear
Related Commands
alarm clear-threshold, alarm enable (Core)
alarm clear-threshold
Sets the threshold to clear the specified alarm type.
Syntax
[no] alarm <type> clear-threshold <threshold-level>
Parameters
<type>
Type of alarm. See the alarm enable (Core) command for a complete listing and description of alarm types.
<threshold-level>
Threshold level. The threshold level depends on the alarm type, as do the possible values.
Usage
Use this command to set the threshold at which the alarm is cleared.
Example
amnesiac (config) # alarm cpu_util_indiv clear-threshold 70
Related Commands
alarm clear, alarm enable (Core), alarm enable (Edge)
alarm enable (Core)
Enables the specified alarm.
Syntax
[no] alarm <type> enable
Parameters
<type>
Type of alarm:
•  appliance_status - This alarm indicates the overall health of the appliance.
•  appliance_unlicensed - This alarm triggers if the appliance has no BASE or MSPEC license installed for its currently configured model. This alarm also triggers for hardware earlier than xx60 with no BASE licensing installed.
•  autolicense_error - This alarm triggers on an appliance when the Riverbed Licensing Portal cannot respond to a license request with valid licenses.
•  autolicense_info - This alarm triggers if the Riverbed Licensing Portal has information regarding licenses for a Virtual Core.
•  bkup_int - This alarm triggers if the backup integration module encounters an error.
•  blkdisk - This alarm triggers and sends an email if the block-disk module encounters an error. By default, this alarm is enabled. This alarm applies only to Core-v implementations.
•  config - This alarm sends an email notification if the Core configuration has been reverted to a previous version. By default, this alarm is enabled.
 
•  coredr - This alarm is enabled by default and triggers if there are any disaster recovery errors or if there is a Degraded state in the disaster recovery configuration. There are several issues that can be reported:
•  Connection to the peer data center is down.
•  Journal LUN size - This alarm is triggered when the Journal LUN size is not large enough to allow creation of the required number of replicas. This alarm automatically clears when the new size of the Journal LUN is detected.
•  WAN RTT (replication performance) - This alarm is triggered if the ping time between data centers exceeds 100 ms.
•  WAN sync latency (replication performance) - This alarm is triggered if the backend on the secondary is having issues (slow IOPs or high latency), or if a large number of replicas (more than 10) are created at one time. This alarm also tracks the time it takes to commit writes to the secondary data center. This includes time to transmit the data, time to write the data on the secondary storage array, and time for a response.
•  Replication state - This alarm is triggered if one or more replica LUNs are in Suspended state on the primary Core and are therefore not being replicated.
•  Role issue - This alarm is triggered if any Edge connects to Core and reports a conflicting disaster recovery role.
•  Failover issue - This alarm is triggered when a disaster recovery failover has occurred, but not all Edges have failed over to the new primary data center.
•  Split-brain - This message is triggered when a split-brain state is detected between the replication data centers. A split-brain is that both sites report they are primary and suspended.
•  Data on FusionSync replica is corrupted - This alarm triggers when data mismatch is detected on any of the replica LUNs. This alarm is raised on the primary Core.
•  cpu_util_indiv - This alarm indicates whether the system has reached the CPU threshold for any of the CPUs in the system. If the system has reached the CPU threshold, check your settings. If your alarm thresholds are correct, reboot the appliance.
•  critical_temp - This alarm indicates that the CPU temperature has exceeded the critical threshold. The default value for the rising threshold temperature is 80ºC; the default reset threshold temperature is 70ºC.
•  edge - This alarm indicates that Core has lost connection with one of its configured Edges.
<type>
•  flash_error - This alarm indicates that the system has detected an error with the flash drive hardware. At times, the USB flash drive that holds the system images might become unresponsive; the appliance continues to function normally. When this error triggers you cannot perform a software upgrade, as the appliance is unable to write a new upgrade image to the flash drive without first power cycling the system. To reboot the appliance, enter the command to automatically power cycle the Core and restore the flash drive to its proper function.
•  fs_mnt - This alarm indicates that one of the mounted partitions is full or almost full. The alarm is triggered when only 7% of free space is remaining.
 
•  ha - This alarm indicates that at least one of the appliances in a high availability pair is actively serving storage data (the active node).
•  hardware - This alarm indicates the overall health of the hardware.
•  ipmi - This alarm indicates that the system has detected an Intelligent Platform Management (IPMI) event. This alarm is not supported on all appliance models.
 
•  iscsi - This alarm indicates that the iSCSI initiator is not accessible.
•  license_expired - This alarm triggers if any feature has at least one license installed, but all of them are expired.
•  license_expiring - This alarm triggers if one or more features is going to expire within two weeks.
Note: The license expiring and license expired alarms are triggered per feature. For example, if you install two license keys for a feature, LK1-FOOxxx (expired) and LK1-FOO-yyy (not expired), the alarms do not trigger, because the feature has one valid license.
•  licensing - This alarm is the parent licensing alarm and triggers if any of the license_expired, license_expiring, or appliance_unlicensed alarms are active.
 
•  link_duplex - This alarm is triggered when an interface was not configured for half-duplex negotiation but has negotiated half-duplex mode. Half-duplex significantly limits the optimization service results. This alarm is enabled by default.
•  link_io_errors - This alarm is triggered when the link error rate exceeds 0.1% while either sending or receiving packets. This threshold is based on the observation that even a small link error rate reduces TCP throughput significantly. A properly configured LAN connection should experience very few errors. The alarm clears when the rate drops below 0.05%. This alarm is enabled by default. You can change the default alarm thresholds by entering the alarm error-threshold command at the system prompt. You can enable or disable the alarm for a specific interface. For example, you can disable the alarm for a link after deciding to tolerate the errors.
•  linkstate: <x> - These alarms indicate that the system has detected a link that is down. The system notifies you through SNMP traps, email, and alarm status. By default, this alarm is not enabled. The no alarm linkstate enable command disables the link state alarm.
•  lun - This alarm indicates that the connection to the LUN failed or there is an issue with LUN resizing.
•  memory_error - This alarm indicates that the system has detected a memory error.
•  model_unlicensed - This alarm indicates that the model license has been removed or is expired.
<type>
•  other_hardware_error - This alarm indicates that the system has detected a problem with the hardware. The alarm clears when you add the necessary hardware, remove the nonqualified hardware, or resolve other hardware issues. The following issues trigger the hardware error alarm:
–  the Core does not have enough disk, memory, CPU cores, or NIC cards to support the current configuration.
–  the Core is using a dual in-line memory module (DIMM), a hard disk, or a NIC that is not qualified by Riverbed.
–  DIMMs are plugged into the Core but it cannot recognize them because the DIMM modules are in the wrong slot. You must plug DIMM modules into the black slots first and then use the blue slots when all of the black slots are in use.
–  a DIMM module is broken and you must replace it.
–  other hardware issues.
•  paging - This alarm indicates whether the system has reached the memory paging threshold. If 100 pages are swapped approximately every two hours the appliance is functioning properly. If thousands of pages are swapped every few minutes, then reboot the system. If rebooting does not solve the problem, contact Riverbed Support.
 
•  secure_vault - This alarm indicates a general secure vault error.
•  secure_vault_unlocked - This alarm indicates whether the secure vault is unlocked. When the vault is unlocked, SSL traffic is not optimized and you cannot encrypt a data store.
 
•  snapshot - This alarm indicates that a snapshot has failed to commit to the SAN, or a snapshot has failed to complete.
•  ssl - This alarm indicates whether the system has detected an SSL error.
•  sticky_staging_dir - This alarm indicates that the system has detected an error while trying to create a process dump.
•  storage_status - This alarm indicates the overall storage health status.
•  temperature - This alarm is the parent temperature alarm and triggers if any of the warning_temp or critical_temp alarms are active.
•  upgrade - This alarm indicates the status of an upgrade.
•  warning_temp - This alarm indicates whether the CPU temperature has exceeded the warning threshold. The default value for the rising threshold temperature is 80ºC; the default reset threshold temperature is 70ºC.
•  vmaware_backup - This alarm triggers and sends an email for the following conditions:
•  proxy connection failure - connection to the proxy server fails. This alarm clears when the connection is restored between the Core and proxy server.
•  backup policy failure - backup operation fails. This alarms is cleared after a successful protection operation.
•  snapshot error - proxy mounted VMs have associated snapshots and cannot be unmounted.
•  excluded VMs - VMs are excluded from a backup policy.
Usage
Enabling alarms is optional.
Critical temperature settings cannot be changed. Warning temperature settings can be changed.
The no command option disables all statistical alarms. The no alarm <type> enable command disables specific statistical alarms.
Example
Core1 # alarm ha enable
Related Commands
alarm clear, alarm clear-threshold, alarm error-threshold
alarm enable (Edge)
Enables the specified alarm.
Syntax
[no] alarm <type> enable
Parameters
<type>
•  acs - This alarm sends an email notification when an application-consistent snapshot failed to be committed to the Core, or a snapshot failed to complete. Application consistent snapshots are scheduled using the Core snapshot scheduler. A snapshot is application consistent if, in addition to being write-order consistent, it includes data from running applications that complete their operations and flush their buffers to disk. This error triggers when there are problems interacting with servers (ESXi or Windows). Errors can also occur due to misconfigurations on either side, local issues on the servers (high load, timeouts, reboots), networking problems, and so on. This alarm is enabled by default.
•  acs_hyperv_vmrs_file_size - This alarm indicates that large VMRS files will be created on Hyper-V after performing a snapshot operation on the guest VMs. The large VMRS file size on Hyper-V after a snapshot operation can be caused by one of these conditions:
•  Hyper-V Integration Services is not up to date on the VM.
•  Hyper-V Integration Services is up to date, but the VM is in the Paused or Saved state.
•  Hyper-V Integration Services is up to date, but the VSS service is not running on the VM.
This alarm is available only in Virtual Edge on Hyper-V deployments.
•  admission_conn - This alarm should not be disabled. It indicates that the system connection limit has been reached. Additional connections are passed through unoptimized. The alarm clears when the appliance moves out of this condition.
•  admission_control - This alarm should not be disabled. It indicates that the system admission control pressure limit has been reached. Additional connections are passed through unoptimized. This alarm clears when the appliance moves out of this condition.
•  admission_cpu - This alarm should not be disabled. This alarm is triggered by high CPU usage. Additional connections are passed through unoptimized. The alarm clears when the appliance moves out of this condition.
 
•  admission_mapi - This alarm should not be disabled. It indicates that the total number of MAPI optimized connections has exceeded the maximum admission control threshold.
•  admission_mem - This alarm should not be disabled. It indicates that the system connection memory limit has been reached. Additional connections are passed through unoptimized. The alarm clears when the SteelFusion Edge moves out of this condition.
•  admission_tcp - This alarm should not be disabled. This alarm is triggered by high TCP memory usage. Additional connections are passed through unoptimized. The alarm clears when the SteelFusion Edge moves out of this condition.
•  appliance_unlicensed - This alarm triggers if the appliance has no BASE or MSPEC license installed for its currently configured model.
•  arcount - This alarm should not be disabled. It indicates whether the system is experiencing asymmetric traffic. If the system experiences asymmetric traffic, the system detects this condition and reports the failure. The traffic is passed through, and the route appears in the asymmetric routing table.
•  autolicense_error - This alarm triggers on a Virtual SteelHead appliance when the Riverbed Licensing Portal cannot respond to a license request with valid licenses.
•  autolicense_info - This alarm triggers if the Riverbed Licensing Portal has information regarding licenses for a Virtual SteelHead appliance.
•  blockstore - This alarm indicates that issues with the Edge blockstore have occurred. This alarm is enabled by default.
•  bypass - This alarm should not be disabled. It indicates that the system is in bypass mode. If the SteelHead is in bypass mode, restart the SteelHead service.
•  certs_expiring - This alarm indicates that the system has expiring SSL certificates.
•  cf_ack_timeout_aggr - This alarm indicates that the connection has been lost because requests have not been acknowledged by a connection-forwarding neighbor within the set threshold.
•  cf_conn_failure_aggr - This alarm indicates that the connection cannot be established with a connection-forwarding neighbor.
•  cf_conn_lost_eos_aggr - This alarm indicates that the connection has been closed by the connection-forwarding neighbor.
•  cf_conn_lost_err_aggr - This alarm indicates that the connection has been lost with the connection-forwarding neighbor due to an error.
<type>
•  cf_keepalive_timeout_aggr - This alarm indicates that the connection forwarding neighbor has not sent a keep-alive message within the time-out period to the neighbor SteelHead(s) indicating that the connection has been lost.
•  cf_latency_exceeded_aggr - This alarm indicates that the amount of latency between connection-forwarding neighbors has exceeded the specified threshold.
•  cf_neighbor_incompatible_cluster - This alarm sends an email notification if a connection-forwarding neighbor is running a RiOS version that is incompatible with IPv6, or if the IP address configuration between neighbors does not match, or if path selection is enabled locally and the neighbor does not have path selection enabled. The appliance neighbors pass through IPv6 connections when this alarm triggers.
•  cf_read_info_timeout_aggr - This alarm indicates that the appliance has timed out while waiting for an initialization message from the connection-forwarding neighbor.
 
•  connection_forwarding - This alarm is the connection forwarding parent alarm.
•  cpu_check - This alarm indicates that the CPU capacity and cores reserved for the Virtual Edge VM hosted on Hyper-V are not sufficient to support Virtual Edge operations. This alarm is available only in Virtual Edge on Hyper-V deployments.
•  cpu_util_indiv - This alarm indicates whether the system has reached the CPU threshold for any of the CPUs in the system. If the system has reached the CPU threshold, check your settings. If your alarm thresholds are correct, reboot the appliance.
•  critical_temp - This alarm indicates that the CPU temperature has exceeded the critical threshold. The default value for the rising threshold temperature is 80ºC; the default reset threshold temperature is 70ºC.
•  crl_error: SSL_CAs - Indicates that an SSL peering certificate has failed to reenroll automatically within the Simple Certificate Enrollment Protocol (SCEP) polling interval.
•  crl_error: SSL_Peering_CAs - Indicates that an SSL peering certificate has failed to reenroll automatically within the Simple Certificate Enrollment Protocol (SCEP) polling interval.
•  datastore - This alarm indicates the overall data store health.
•  datastore_clean_needed - This alarm indicates that you need to clear the RiOS data store.
•  datastore_error - This alarm indicates that the data store is corrupt or has become incompatible with the current configuration. Clear the data store to clear the alarm. If the alarm was caused by an unintended change to the configuration, you can change the configuration to match the previous RiOS data store settings. Then restart the optimization service without clearing the RiOS data store to reset the alarm. Typical configuration changes that require a restart with a clear RiOS data store are enabling the Extended Peer Table or changing the data store encryption.
•  datastore_sync_error - This alarm indicates that the system has detected a problem with the synchronized data.
•  disconnected_sh_alert - This alarm indicates that the connection to a SteelHead appliance in a connection forwarding cluster is lost.
•  disk:<x>:status - These alarms indicate that the system has detected a problem with the specified disk or a solid-state drive.
•  domain_join_error - This alarm indicates that the system has encountered an error when attempting to join a domain.
•  duplex - This alarm indicates that the system has encountered a large number of packet errors in your network. Make sure that the speed and duplex settings on your system match the settings on your switch and router. By default, this alarm is enabled.
•  edge_ha - This alarm sends an email message if only one of the appliances in a high availability (HA) SteelFusion Edge pair is actively serving storage data (the active peer).
•  edge_service- This alarm indicates that the Edge appliance connected to the Core is not servicing the Core. Check that Edge appliance is running.
<type>
•  fan_error - This alarm indicates that the system has detected a fan error.
•  flash_error - This alarm indicates that the system has detected an error with the flash drive hardware. At times, the USB flash drive that holds the system images might become unresponsive; the SteelHead continues to function normally. When this error triggers you cannot perform a software upgrade, as the SteelHead is unable to write a new upgrade image to the flash drive without first power cycling the system. To reboot the appliance, enter the reload command to automatically power cycle the SteelHead and restore the flash drive to its proper function. On desktop SteelHead appliance x50 and x55 models, you must physically power cycle the appliance (push the power button or pull the power cord).
•  fs_mnt - This alarm indicates that one of the mounted partitions is full or almost full. The alarm is triggered when only 7% of free space is remaining.
 
•  halt_error - This alarm cannot be disabled. It indicates that the system has detected an unexpected halt to the optimization service.
•  hardware - This alarm indicates the overall health of the hardware.
•  host_hypervisor - This alarm indicates that the Virtual Edge has encountered a problem with the host hypervisor. This alarm is available only in Virtual Edge on Hyper-V deployments.
•  host_hypervisor_status - This alarm indicates that the connectivity to the host Hyper-V is lost or not established from the Virtual Edge VM. The reason for connection failure is specified in the alarm description. This alarm is available only in Virtual Edge on Hyper-V deployments.
•  hypervisor_hw_memory_error - This alarm triggers when memory error system event log entries occur on the hypervisor motherboard controller.
•  hypervisor_hw_mgmt_connection - This alarm indicates that RiOS lost IP connectivity or cannot authenticate the connection to the hypervisor motherboard controller.
•  hypervisor_hw_power_lost - This alarm triggers when the hypervisor node power is lost.
•  hypervisor_hw_temperature_error - This alarm triggers when a hypervisor CPU, board, or platform controller hub (PCH) temperature exceeds the rising threshold. When the CPU, board, or PCH returns to the reset threshold, the critical alarm clears (after polling for 30 seconds). If the appliance has more than one CPU, the alarm displays both CPUs. The default values are maintained by the motherboard.
•  hypervisor_license_error - This alarm is triggered if the hypervisor license is missing and the installer has not been run.
•  hypervisor_operation_error - This alarm is triggered if there is a hypervisor operation error.
•  hypervisor_other_hardware_error - This alarm reports status on unbranded, unknown, or unsupported cards in the system. The alarm message also reports RiOS cards not supported on the hypervisor.
•  hypervisor_version_check - This alarm indicates that the host hypervisor is running an OS version that is not supported by Virtual Edge. This alarm is available only in Virtual Edge on Hyper-V deployments.
•  inbound_qos_wan_bw_err - This alarm sends an email notification if the inbound QoS WAN bandwidth for one or more of the interfaces is set incorrectly. You must configure the WAN bandwidth to be less than or equal to the interface bandwidth link rate.
•  ipmi - This alarm indicates that the system has detected an Intelligent Platform Management (IPMI) event. This alarm is not supported on all appliance models.
 
•  iscsi - This alarm indicates that the iSCSI initiators are not accessible. Review the iSCSI configuration in the Core. The iSCSI initiators might have been removed. This alarm is enabled by default.
•  license_expired - This alarm triggers if any feature has at least one license installed, but all of them are expired.
•  license_expiring - This alarm triggers if one or more features is going to expire within two weeks.
•  licensing - This alarm is the parent licensing alarm and triggers if any of the license_expired, license_expiring, or appliance_unlicensed alarms are active.
Note: The license_expiring and license_expired alarms are triggered per feature. For example, if you install two license keys for a feature, LK1-FOOxxx (expired) and LK1-FOO-yyy (not expired), the alarms do not trigger, because the feature has one valid license.
<type>
•  link_duplex - This alarm is triggered when an interface was not configured for half-duplex negotiation but has negotiated half-duplex mode. Half-duplex significantly limits the optimization service results. This alarm is enabled by default.
•  link_io_errors - This alarm is triggered when the link error rate exceeds 0.1% while either sending or receiving packets. This threshold is based on the observation that even a small link error rate reduces TCP throughput significantly. A properly configured LAN connection should experience very few errors. The alarm clears when the rate drops below 0.05%. This alarm is enabled by default.
•  link_io_errors - This alarm is triggered when the link error rate exceeds 0.1% while either sending or receiving packets. This threshold is based on the observation that even a small link error rate reduces TCP throughput significantly. A properly configured LAN connection should experience very few errors. The alarm clears when the rate drops below 0.05%. This alarm is enabled by default. You can change the default alarm thresholds by entering the alarm error-threshold command at the system prompt. You can enable or disable the alarm for a specific interface. For example, you can disable the alarm for a link after deciding to tolerate the errors.
•  link_state: <x> - These alarms indicate that the system has detected a link that is down. The system notifies you through SNMP traps, email, and alarm status. By default, this alarm is not enabled. The no alarm linkstate enable command disables the link state alarm.
•  lun - This alarm indicates that the SteelFusion Core LUN is unavailable. This is a SteelHead EX alarm.
•  mem_check - This alarm indicates that the memory reserved for the Virtual Edge VM hosted on Hyper-V is not sufficient to support Virtual Edge operations. Also indicates that the memory allocation is dynamic. This alarm is available only in Virtual Edge on Hyper-V deployments.
•  memory_error - This alarm indicates that the system has detected a memory error.
•  mismatch_peer_aggr - This alarm indicates that the appliance has encountered another appliance that is running an incompatible version of system software. Refer to the CLI, Management Console, or the SNMP peer table to determine which appliance is causing the conflict. Connections with that peer will not be optimized, connections with other peers running compatible RiOS versions are unaffected. To resolve the problem, upgrade your system software. No other action is required as the alarm clears automatically.
•  model_unlicensed - This alarm indicates that the model license has been removed or is expired.
•  nfs_v2_v4 - This alarm indicates that the system has triggered a version 2 or version 4 NFS alarm.
 
•  non_443_ssl_servers_detected_on_upgrade - This alarm indicates that during a RiOS upgrade (for example, from 5.5 to 6.0), the system has detected a preexisting SSL server certificate configuration on a port other than the default SSL port 443. SSL traffic might not be optimized. To restore SSL optimization, you can either add a peering rule to the server-side SteelHead to intercept the connection and optimize the SSL traffic on the nondefault SSL server port or you can add an in-path rule to the client-side SteelHead to intercept the connection and optimize the SSL traffic on the nondefault SSL server port. After adding a peering or in-path rule, you must clear this alarm manually by issuing the following CLI command:
alarm non_443_ssl_servers_detected_on_upgrade clear
 
•  optimization_general - This alarm indicates that the optimization service is not operating normally. The service might not be running, it might be disabled, or it might have stopped optimizing.
•  optimization_service - This alarm indicates that the system has encountered an optimization service condition.
<type>
•  other_hardware_error - This alarm indicates that the system has detected a problem with the appliance hardware. The alarm clears when you add the necessary hardware, remove the nonqualified hardware, or resolve other hardware issues. The following issues trigger the hardware error alarm:
–  the appliance does not have enough disk, memory, CPU cores, or NIC cards to support the current configuration.
–  the appliance is using a dual in-line memory module (DIMM), a hard disk, or a NIC that is not qualified by Riverbed.
–  DIMMs are plugged into the appliance but RiOS cannot recognize them because the DIMM modules are in the wrong slot. You must plug DIMM modules into the black slots first and then use the blue slots when all of the black slots are in use.
–  a DIMM module is broken and you must replace it.
–  other hardware issues.
 
•  outbound_qos_wan_bw_err - This alarm sends an email notification if the outbound QoS WAN bandwidth for one or more of the interfaces is set incorrectly. You must configure the WAN bandwidth to be less than or equal to the interface bandwidth link rate.
•  paging - This alarm indicates whether the system has reached the memory paging threshold. If 100 pages are swapped approximately every two hours the SteelHead is functioning properly. If thousands of pages are swapped every few minutes, then reboot the system. If rebooting does not solve the problem, contact Riverbed Support.
•  path_selection_path_down - This alarm indicates that one of the predefined uplinks for a connection is unavailable because it has exceeded either the timeout value for uplink latency or the threshold for observed packet loss.
•  path_selection_path_probe_err - This alarm indicates that a path selection monitoring probe for a predefined uplink has received a probe response from an unexpected relay or interface.
•  pfs - This alarm is the parent PFS alarm and triggers if the pfs_config or pfs_operation alarms are active.
 
•  pfs_config - This alarm indicates that there has been a PFS or prepopulation operation error. If the system detects an operation error, restart the SteelHead service and PFS.
•  pfs_operation - This alarm indicates that a synchronization operation has failed. If the system detects an operation failure, attempt the operation again.
•  power_supply - This alarm indicates that an inserted power supply cord does not have power, as opposed to a power supply slot with no power supply cord inserted.
•  raid_disk_indiv - This alarm indicates that the system has encountered RAID errors (for example, missing drives, pulled drives, drive failures, and drive rebuilds). For drive rebuilds, if a drive is removed and then reinserted, the alarm continues to be triggered until the rebuild is complete. Rebuilding a disk drive can take 4 to 6 hours.
•  rhsp - This alarm indicates that the Riverbed host tools package (RHSP) is incompatible with the Windows server version. RHSP provides snapshot capabilities by exposing the Edge through iSCSI to the Windows Server as a snapshot provider. RHSP is compatible with 64-bit editions of Microsoft Windows Server 2008 R2 or later and can be downloaded from the Riverbed Support site at https://support.riverbed.com.
In Virtual Edge on Hyper-V deployments, this alarm indicates that an incompatible RHSP version is installed. The alarm also indicates that RHSP is installed on an incompatible Windows server. Windows Server 2016 is required for Virtual Edge on Hyper-V deployments.
•  secure_transport_controller_unreachable - This alarm indicates a network connectivity failure to the Controller for the secure transport feature. Issues that might trigger this alarm are Controller services down because of an upgrade or a network connectivity failure to the Controller.
•  secure_transport_registration_failed - This alarm indicates that the registration with the Controller for secure transport was unsuccessful.
•  secure_vault - This alarm indicates a general secure vault error.
•  secure_vault_rekey_needed - This alarm indicates whether the system has detected that the secure vault needs to be rekeyed.
<type>
•  secure_vault_uninitialized - This alarm indicates that the system has detected that the secure vault is uninitialized.
•  secure_vault_unlocked - This alarm indicates whether the secure vault is unlocked. When the vault is unlocked, SSL traffic is not optimized and you cannot encrypt a data store.
•  serial_cascade_misconfig - This alarm indicates that the system has encountered an error in reaching a neighbor appliance configured for connection forwarding.
•  service_error - This alarm cannot be disabled. It indicates that the system has detected a software error in the SteelHead service. The SteelHead service continues to function, but an error message that you should investigate appears in the logs.
•  single_cf - This alarm indicates that the connection to a SteelHead connection forwarding neighbor is lost.
•  smb_alert - This alarm indicates that the system has detected an SMB signing error.
•  snapshot - This alarm indicates that a snapshot has failed to commit to the SAN, or a snapshot has failed to complete.
 
•  ssd_wear - This is the parent alarm for ssd_wear_warning. This alarm triggers if one of the ssd_wear_warning:<x> alarms becomes active.
•  ssd_wear_warning:<x> - This alarm indicates that the specified disk is approaching its write cycle limit. (Appears only on SteelHead models 7050L or 7050M.)
RiOS tracks the number of writes to each block. To view the overall status, enter the following command:
show alarm ssd_wear
 
To view the status of an individual alarm, enter the following command:
show alarm ssd_wear:<x>
 
where <x> is the SSD disk port number.
•  ssl - This alarm indicates whether the system has detected an SSL error.
•  ssl_peer_scep_auto_reenroll - This alarm indicates that the system has detected an SCEP error. The appliance uses SCEP to dynamically reenroll a peering certificate to be signed by a certificate authority. The alarm clears automatically when the next automatic reenrollment succeeds. To clear the alarm, enter the protocol ssl peering auto- reenroll last-result clear-alarm command.
•  sticky_staging_dir - This alarm indicates that the system has detected an error while trying to create a process dump.
•  store_corruption - This alarm cannot be disabled. It indicates whether the data store is corrupt. To clear the data store of data, restart the SteelHead service and clear the data store on the next restart.
•  sw_version_aggr - This alarm indicates that there is a software version mismatch between peer appliances. The client-side and server-side SteelHeads are running incompatible versions of software.
•  system_detail_report - This alarm indicates that a system component has encountered a problem. This alarm is enabled by default.
•  temperature - This alarm is the parent temperature alarm and triggers if any of the warning_temp or critical_temp alarms are active.
<type>
•  uncommitted_data - This alarm indicates that the SteelFusion Edge has exceeded the percentage for writes written to the local blockstore but not yet written back to the SteelFusion Core. The alarm is triggered when the threshold reaches 5% and clears when this drops to 3%.
•  upgrade - This alarm indicates the status of an upgrade.
•  virtualization_status - This alarm indicates the status of the virtualization process.
•  vsp - This alarm is the parent VSP alarm; it is triggered if any of the VSP alarms are active. This alarm is enabled by default on the SteelFusion Edge.
•  vsp_connection_error - This alarm is triggered when any of the services critical for virtualization are not running; for example, VSP is disconnected from the hypervisor, the hypervisor password is invalid, VSP was unable to gather some hardware information, and VSP is disconnected.
•  vsp_installation_error - This alarm is triggered when VSP is not installed correctly and powered off. Possible issues are a hypervisor upgrade has failed, a configuration push from the hypervisor installer has failed, VSP could not gather enough information to set up an interface, or the hypervisor is not installed.
 
•  warning_temp - This alarm indicates whether the CPU temperature has exceeded the warning threshold. The default value for the rising threshold temperature is 80ºC; the default reset threshold temperature is 70ºC.
Example
Edge1 (config) # alarm edge_service enable
Related Commands
alarm clear, alarm clear-threshold, alarm enable (Core)
alarm error-threshold
Sets a threshold to trigger an alarm.
Syntax
[no] alarm <type> error-threshold <threshold-level>
Parameters
<type>
Type of alarm. See the alarm enable (Core) command for a complete listing and description of alarm types.
<threshold-level>
Threshold level. The threshold level and possible values depend on the alarm type.
Usage
The no command resets the threshold to the default level.
Example
amnesiac (config) # alarm cpu_util_indiv error-threshold 80
Related Commands
alarm clear, alarm clear-threshold, alarm enable (Core)
alarm rate-limit
Sets the alarm rate-limit values.
Syntax
alarm <type> rate-limit [email | snmp] term <rate-limit> {count <value> | window <duration-seconds>}
Parameters
<type>
See the alarm enable (Core) command for a complete listing and description of alarm types.
email
Sets rules for email.
snmp
Sets rules for SNMP.
term <rate-limit>
Sets the alarm event rate-limit term value. Valid choices are:
•  long
•  medium
•  short
count <value>
Sets the count value. The default values are 50 (long), 20 (medium), and 5 (short).
window <duration-seconds>
Sets the duration of time, in seconds, that the window remains open. The default values are 604800 (long), 86400 (medium), and 3600 (short).
Usage
There are three term values—long, medium, and short. Each has a window, which is a number of seconds, and a maximum count. If, for any term value, the number of alarm events exceeds the maximum count during the window, the corresponding email and SNMP notifications are not sent.
Example
amnesiac (config) # alarm crl_error rate-limit email term short window 30
Related Commands
alarm clear, alarm clear-threshold, alarm enable (Core), alarm error-threshold
alarms reset-all
Globally sets all alarms to their default settings.
Syntax
alarms reset-all
Parameters
None
Example
amnesiac (config) # alarms reset-all
Related Commands
alarm clear, alarm clear-threshold, alarm enable (Core)
rbm user (Core)
Assigns a role (that is, a feature set) to a user. A user can be associated with one or more roles.
Syntax
[no] rbm user <username> role <role> permissions <permissions>
Parameters
<username>
Name of the user.
role <role>
Specifies a role-based management type:
•  sys_admin - Configures a system administrator role. Read-only permission is not allowed for this role. This role allows permission for all other RBM roles, including changing users without being logged in as an administrator. The system administrator role allows you to add or remove a system administrator role for any other user, but not for yourself.
•  storage_reports_diag - Assigns a role related to storage-specific graphs and statistics, such as memory logs. You can set permissions to either Deny or Read/Write. This user role will also have Read/Write access to System Diagnostics and Reports to assist you with troubleshooting.
•  storage_settings - Assigns a role related to Core configuration settings, such as configuring LUNs, Edges, and Failover.
•  system_reports_diag - Assigns a role related to all nonstorage reports such as CPU and memory utilization, system logs, system dumps, or TCP dumps. You can set permissions to either Deny or Read/Write. This user role has restricted configuration capabilities.
•  system_settings - Assigns a role related to system settings. Any settings not related to configuration.
permissions <permissions>
Creates users, assigns passwords to the user, and assigns varying configuration roles to the user. A user role determines whether the user has permission to:
•  read-only - With read privileges you can view current configuration settings but you cannot change them.
•  read-write - With write privileges you can view settings and make configuration changes for a feature.
•  deny - With deny privileges you cannot view settings or make configuration changes for a feature.
Usage
The no command option allows for the deletion of a role. Only users with administrative privileges can execute the rbm user command.
Example
amnesiac (config) # rbm user helpdesk role storage_reports_diag permissions read-only
 
amnesiac (config) # no rbm user helpdesk role storage_reports_diag
Product
SteelFusion Core
Related Commands
show rbm user, show rbm users
rbm user (Edge)
Assigns a role (that is, a feature set) to a user. A user can be associated with one or more roles.
Syntax
[no] rbm user <username> role <role> permissions <permissions>
Parameters
<username>
Username.
role <role>
•  acceleration_service - Start and stop the optimization service
 
•  basic_diagnostics - Customizes system diagnostics logs, but does not include TCP dumps
 
•  cifs_acceleration - Enables CIFS optimization settings and Overlapping Open Optimization.
•  citrix_acceleration - Configures Citrix ICA optimization.
•  cloud_acceleration - Configures Cloud optimization.
•  general_settings - Configures a per-source IP connection limit and the maximum connection pooling size.
•  http_acceleration - Configures HTTP optimization settings including cache settings, keep-alive, insert cookie, file extensions to prefetch, and ability to set up HTTP optimization for a specific server subnet.
•  in-path_rules - Configures which TCP traffic to optimize and how to optimize traffic by setting in-path rules. Includes WAN visibility to preserve TCP/IP address or port information.
•  jinitiator_acceleration - Optimizes Oracle E-business application content and forms applications.
•  mapi_acceleration - Optimizes MAPI and sets Exchange and NSPI ports.
 
•  network_settings - Configures these features:
–  Topology definitions
–  Site and network definitions
–  Application definitions
–  Host interface settings
–  Network interface settings
–  DNS cache settings
–  Hardware assist rules
–  Host labels and port labels
You must include this role for users configuring path selection or enforcing QoS policies in addition to the QoS and path selection roles.
•  nfs_acceleration - Configures NFS optimization.
•  notes_acceleration - Configures Lotus Notes optimization.
•  path_selection - Configures path selection. You must also include the network settings role.
•  qos - Enforces QoS policies. You must also include the network settings role.
role <role> (cont)
 
•  replication_acceleration - Configures the SDRF/A and FCIP storage optimization modules.
•  reports - Sets system report parameters.
•  security_settings - Configures security settings, including RADIUS and TACACS authentication settings and secure vault password.
•  sql_acceleration - Configures MS-SQL optimization.
•  ssl_acceleration - Configures SSL support.
•  sys_admin - Configures a system administrator role. Read-only permission is not allowed for this role. This role allows permission for all other RBM roles, including changing users without being logged in as an administrator. The system administrator role allows you to add or remove a system administrator role for any other user, but not for yourself.
 
•  tcp_dump - Configures TCP dump utility.
•  virtual_services_platform - Adds various types of basic services (such as print, DNS, and DHCP services) in the branch to run in a virtual environment on SteelFusion Edge. ESXi versions 6.0 and 6.5 are supported.
•  windows_domain_auth - Configures Windows domain authentication.
permissions <permissions>
Creates users, assigns passwords to the users, and assigns varying configuration roles to the users. A user role determines whether the user has permission to:
•  read-only - With read privileges you can view current configuration settings but you cannot change them.
•  read-write - With write privileges you can view settings and make configuration changes for a feature.
•  deny - With deny privileges you cannot view settings or make configuration changes for a feature.
Usage
The no command option allows for the deletion of a role. Only users with administrative privileges can execute the rbm user command.
Example
amnesiac (config) # rbm user helpdesk role general_settings permissions read-only
Product
SteelFusion Edge
Related Commands
show rbm user, show rbm users
SteelFusion Core commands (both modes)
This section describes the commands that are common to the SteelFusion Core in both file and block mode.
You can use the command line to perform basic configuration tasks, display configuration information, and check status.
device-failover activate
Activates the high-availability configuration for the current Core.
Syntax
device-failover activate
Parameters
None
Usage
Use this command to activate the configuration on the Core. Activating the configuration is required when both Cores in a high availability setup were down and one of them has recently recovered. Manual activation of a configuration is required as the Core cannot detect an active high availability peer.
Note: If both Cores have restarted and require manual activation, it is important that you activate the correct Core, as the other appliance will obtain its configuration from the Core that you choose.
Example
Core_02 (config) # device-failover activate
Product
SteelFusion Core
Related Commands
show device-failover (Core)
device-failover peer set (Core)
Sets the failover peer configuration. You configure the local interface parameters in pairs.
Syntax
device-failover peer set <peer-ip> [local-if <local-interface>] additional-ip <additional-ip> [local-if2 <local-interface2>]
Parameters
<peer-ip>
IP address of the failover peer appliance.
local-if <local-interface>
Specifies the local interface for connecting with the failover peer appliance IP.
additional-ip <additional-ip>
Specifies an additional IP address for the failover peer appliance.
local-if2 <local-interface2>
Specifies an additional local interface for connecting with the failover peer appliance IP.
Usage
Use this command to enable two Cores to be configured so that either one can fail without disrupting the service of any of the LUNs being provided by SteelFusion.
Example
Core_02 (config) # device-failover peer set 10.1.1.1 local-if eth0_0 additional-ip 10.2.1.1
Product
SteelFusion Core
Related Commands
show device-failover (Core)
device-failover peer clear (Core)
Clears the failover peer configuration for the current Core.
Syntax
device-failover peer clear
Parameters
None
Usage
This command is used to properly deactivate high availability between two Cores.
To remove a high-availability configuration between two Cores (Core 01 and Core 02, for the purposes of this example), use the following commands in the listed sequence:
1. On Core 02, stop the Core service using the no service enable command.
2. On Core 01, run device-failover peer clear (Core) to clear the local failover configuration.
3. On Core 02, run device-failover activate to return the appliance to solo mode.
4. Enable Core 02 and run device-failover peer clear (Core) to clear the local failover configuration.
Example
Core 02 (config) # device-failover peer clear
 
Core 02 (config) # show device-failover
Product
SteelFusion Core
Related Command
show device-failover (Core)
device-failover peerip
Adds or removes the specified IP address to or from the failover configuration.
Syntax
device-failover peerip {add <peer-ip> [local-if <local-interface>] | remove <peer-ip>}
Parameters
add <peer-ip>
Specifies the IP address of the failover peer.
local-if <local-interface>
Specifies the local interface for connecting with the failover peer.
remove <peer-ip>
Specifies the IP address of the peer to be removed from the failover configuration.
Usage
Use this command to modify the IP address of the failover peer. First remove the existing setting and then add the new value.
Example
Core_02 (config) # device-failover peerip remove 10.1.1.1
 
Core_02 (config) # device-failover peerip add 10.1.1.2
Product
SteelFusion Core
Related Commands
device-failover peer clear (Core), device-failover peer set (Core), show device-failover (Core)
edge add id
Adds an Edge to the running Core configuration.
Syntax
[failover-peer] edge add id <id>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
Usage
Use this command to add an Edge to the current Core configuration. Each Edge is configured with a unique self-identifier (which is configured through the Edge).
All failover-peer edge commands enable you to configure an unavailable Core through its failover peer. When the intended Core becomes operational, the new configuration is added automatically. You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Example
Core_01 (config) # edge add id BranchEdge001
 
Core_02 (config) # failover-peer edge add id Edge3
Product
SteelFusion Core
Related Commands
show edge, show storage iscsi
edge id blockstore enc-type
Configures the blockstore for the specified Edge.
Syntax
[failover-peer] edge id <id> blockstore enc-type <enc-type>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and
hyphen (-).
<enc-type>
Blockstore encryption type:
•  NONE - No blockstore encryption.
•  AES_128 - Encrypt blockstore with AES 128-bit key.
•  AES_192 - Encrypt blockstore with AES 192-bit key.
•  AES_256 - Encrypt blockstore with AES 256-bit key.
Example
Core_01 (config) # edge id Branch006a blockstore enc-type AES_128
 
Core_02 (config) # failover-peer edge id Edge1 blockstore enc-type AES_128
Product
SteelFusion Core
Related Command
show edge
edge id blockstore uncommitted
Sets alarms to be triggered if uncommitted blockstore data exceeds specified thresholds.
Syntax
[failover-peer] edge id <id> blockstore uncommitted [trigger-pct <percentage>] [repeat-pct <percentage>] [repeat-interval <interval>]
Usage
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and
hyphen (-).
trigger-pct <percentage>
Triggers the alarm if the percentage of uncommitted data exceeds the specified threshold.
The default threshold is 5 percent, which for a 4 TiB (1260-4) system is 200 GiB.
repeat-pct <percentage>
Repeatedly triggers the alarm if the percentage of uncommitted data increases from a previous triggered value by more than the specified percentage.
repeat-interval <interval>
Repeatedly triggers the uncommitted data alarm at periodic time intervals until the percentage of uncommitted data falls below the clear threshold limit.
Example
Core 03 (config) # edge id Edge2 blockstore uncommitted trigger-pct 50 repeat-pct 25
 
Core 03 (config) # failover-peer edge id Edge3 blockstore uncommitted trigger-pct 50 repeat-pct 25
Product
SteelFusion Core
Related Command
show edge
edge modify id branch-recovery clear
Clears the branch recovery state for all LUNs mapped to the Edge.
Syntax
[failover-peer] edge modify id <id> branch-recovery clear
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
Example
Core_01 (config) # edge modify id Branch006a branch-recovery clear
 
Core_02 (config) # failover-peer edge modify id Branch006a branch-recovery clear
Product
SteelFusion Core
Related Commands
show storage lun, storage lun modify branch-recovery
edge modify id clear-serial
Clears the saved serial value for the Edge so that it can be replaced. This command is meant to be used while replacing an Edge in a non-HA configuration.
Syntax
[failover-peer] edge modify id <id> clear-serial
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
Usage
You should run this command on the Core first, and then add the Core on the replacement Edge.
Example
Core_01 (config) # edge modify id Branch006a clear-serial
 
Core_02 (config) # failover-peer edge modify id Branch006a clear-serial
Product
SteelFusion Core
Related Command
show edge
edge modify id netdisk-mpio active-active enable
Enables active/active NetDisk MPIO interface teaming.
Syntax
[no] [failover-peer] edge modify id <id> netdisk-mpio active-active enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
Usage
Multipath NetDisk is a high-availability component between Edges in an HA configuration. Multipath NetDisk is turned on by default and is configured to use links in active-active mode. When you configure Edge high availability, We recommend setting up Edge multipath I/O (MPIO). This configuration ensures that a failure of any single component (such as a network interface card, switch, or cable) does not result in a communication problem between the iSCSI initiators and the Edge.
By default, MPIO NetDisk is configured to use links in active-active mode. This configuration may be disruptive to installations that use the secondary link for other traffic. To disable this mode, enter the following:
Core_01 (config) # no edge modify id * netdisk-mpio active-active
Edge_01 (config) # service storage restart
Example
Core_01 (config) # edge modify id Branch006a netdisk-mpio active-active enable
 
Core_01 (config) # no edge modify id Branch006a netdisk-mpio active-active enable
 
Core_02 (config) # failover-peer edge modify id Branch006a netdisk-mpio active-active enable
 
Core_02 (config) # no failover-peer edge modify id Branch006a netdisk-mpio active-active enable
Product
SteelFusion Core
Related Command
show edge
edge modify id serialize-snap enable
Enables the serialization of application consistent snapshot operations for the Edge.
Syntax
[failover-peer] edge modify id <id> serialize-snap enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
Example
Core_01 (config) # edge modify id Branch006a serialize-snap enable
 
Core_02 (config) # failover-peer edge modify id Branch006a serialize-snap enable
Product
SteelFusion Core
Related Command
show edge
edge modify preferred-if
Sets the preferred interface on the Core for Edge connections.
Syntax
[failover-peer] edge modify preferred-if {add <interface> | remove <interface>} <interface>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
add <interface>
Adds the specified interface to the Edge configuration.
remove <interface>
Removes the specified interface from the Edge configuration.
<interface>
Preferred interface for Edge connections.
Usage
Use this command for high availability deployments. You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
In the event of a failover event, this setting ensures that the Edges will connect to the Core failover peer.
For redundancy, add multiple interfaces in the order of preference.
Example
Core_01 (config) # edge modify preferred-if add aux
 
Core_02 (config) # failover-peer edge modify preferred-if add aux
Product
SteelFusion Core
Related Command
show edge
edge remove id
Removes the specified Edge from the Core configuration.
Syntax
[failover-peer] edge remove id <id>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
Example
Core_01 (config) # edge remove id Branch006a
 
Core_02 (config) # failover-peer edge remove id Branch006a
Product
SteelFusion Core
Related Command
show edge
storage backup group add
Adds a backup protection group and configures the storage backup configuration settings.
Syntax
[failover-peer] storage backup group add <group-id> server-id <server-id> policy-id <policy-id> {membership all [exclude <members>] | membership selected members <members>} [max-history <max-history-number>] [quiesce-vm-list <quiesce-vm-list>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<group-id>
Protection group identifier.
server-id <server-id>
Specifies the Edge server identifier. Identifiers are case sensitive.
policy-id <policy-id>
Specifies the backup policy identifier.
membership all
Specifies all members in the backup protection group.
exclude <members>
Excludes the specified members.
membership selected members <members>
Specifies selected members in a backup protection group.
max-history <max-history-number>
Specifies the maximum history of protection operations maintained for the protection group. The default is 5.
quiesce-vm-list <quiesce-vm-list>
Specifies the list of VMs that will be quiesced into a state suitable for backups. This option is disabled by default.
Usage
The Core uses the protection group to map the servers, VMs, and LUNs that are being protected. Each protection group contains the information associated with the server being protected, backup proxy host, and backup protection policy.
The typical workflow for setting up backup protection follows:
1. Use the storage server add command to add an Edge server.
2. Use the storage backup proxy add command to add the backup proxy.
3. Use the storage backup policy add command to configure the backup protection policy.
4. Use the storage backup group add command to add the backup protection group.
Example
Core_01 (config) # storage backup group add group1 server-id sf-shxxx-server policy-id pol_1 membership all max-history 4
Product
SteelFusion Core
Related Commands
show storage backup group, storage backup group modify, storage backup group remove
storage backup group modify
Modifies the configuration settings for the backup protection group.
Syntax
[failover-peer] storage backup group modify <group-id> [server-id <server-id>] [membership {all | selected members <members>}] [exclude <members>] [max-history <max-history-number>] [quiesce-vm-list <quiesce-vm-list>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<group-id>
Protection group identifier.
server-id <server-id>
Specifies the Edge server identifier. Identifiers are case sensitive.
membership all
Specifies all members in the backup protection group.
membership selected members <members>
Specifies selected members in a backup protection group.
exclude <members>
Excludes the specified members from the protection group.
max-history <max-history-number>
Specifies the maximum history of protection operations maintained for the protection group. The default is 5.
quiesce-vm-list <quiesce-vm-list>
Specifies the list of VMs that will be quiesced into a state suitable for backups. This option is disabled by default.
Usage
This command allows you to modify the protection group settings. You can choose which VMs on a server you want to protect in your protection group. You can customize this protection operation by protecting either VMs on the Edge server specified by roster (inclusive selection) or all VMs on the Edge server except those excluded by roster (exclusive selection).
Example
This example shows how to limit the protection group to vm7 and vm8:
Core_01 (config) # storage backup group modify group1 membership selected members vm7,vm8
 
This example shows how to protect all VMs on the Edge server except for vm7 and vm8:
Core_01 (config) # storage backup group modify group1 membership all exclude vm7,vm8
Product
SteelFusion Core
Related Commands
show storage backup group, storage backup group add, storage backup group remove
storage backup group remove
Removes the specified backup protection group.
Syntax
[failover-peer] storage backup group remove <group-id>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<group-id>
Protection group identifier.
Usage
Each protection group maps to an Edge server, backup proxy host, and backup protection policy.
The typical workflow for removing the backup protection follows:
1. Use the storage backup group remove command to remove the backup protection group.
2. Use the storage backup policy remove command to remove the backup protection policy.
3. Use the storage backup proxy remove command to remove the backup proxy.
4. Use the storage server remove command to remove the Edge server
Example
Core_01 (config) # storage backup group remove group1
Product
SteelFusion Core
Related Commands
show storage backup group, storage backup group add, storage backup group modify
storage backup policy add
Configures the backup protection policy.
Syntax
[failover-peer] storage backup policy add <policy-name> proxy-id <proxy-id> schedule-type {daily [hour <hour>] [minute <minute>] | hourly [minute <minute>] | weekly [day <day>] [hour <hour>] [minute <minute>]}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Policy name.
proxy-id <proxy-id>
Specifies the backup proxy identifier. Identifiers are case sensitive.
schedule-type
Specifies the type of schedule.
daily
Specifies once a day.
hourly
Specifies every hour.
Note: Because each backup operation takes approximately two minutes to complete, enabling the hourly option for more than 30 LUNS can result in an increasing number of nonreplicated snapshots on Edges.
weekly
Specifies once a week.
hour <hour>
Specifies hour of the day in the 24-hour clock format. For example, for 4:00 P.M., specify 16. The range is from 0 to 23.
minute <minute>
Specifies the minutes after the hour; the valid range is from 0 to 59.
day <day>
Specifies the day of the week for a weekly schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
Usage
This command configures the backup policy that binds together the backup proxy and the schedule to run the backup operation. You can create an hourly, daily, or weekly backup schedule.
If you selected hourly, optionally specify the number of minutes after the hour to start the backup. If you selected daily, optionally specify a time (the local time at the Edge) to start the backup. If you selected weekly, optionally select the day of the week and time (the local time at the Edge).
One backup proxy can be shared among multiple backup policies. You can trigger this policy by using the storage backup trigger command on the Edge appliance.
The typical workflow for setting up backup protection follows:
1. Use the storage server add command to add an Edge server.
2. Use the storage backup proxy add command to add the backup proxy.
3. Use the storage backup policy add command to configure the backup protection policy.
4. Use the storage backup group add command to add the backup protection group.
Example
Core_01 (config) # storage backup policy add Edge-xxx-VBP proxy-id pxy_1 schedule-type weekly day mon
Product
SteelFusion Core
Related Commands
show storage backup policy, storage backup policy modify, storage backup trigger
storage backup policy modify
Modifies the backup protection policy.
Syntax
[failover-peer] storage backup policy modify <policy-name> proxy-id <proxy-id> schedule-type {daily [hour <hour>] [minute <minute>] | hourly [minute <minute>] | weekly [day <day>] [hour <hour>] [minute <minute>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Policy name.
proxy-id <proxy-id>
Specifies the backup proxy identifier.
schedule-type
Specifies the type of schedule.
daily
Specifies once a day.
hourly
Specifies every hour.
weekly
Specifies once a week.
hour <hour>
Specifies hour of the day in the 24-hour clock format; for example, for 4:00 P.M. input specify 16. The range is from 0 to 23.
minute <minute>
Specifies the minutes after the hour; the valid range is from 0 to 59.
day <day>
Specifies the day of the week for a weekly schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
Example
Core_01 (config) # storage backup policy modify Edge-xxx-VBP proxy-id pxy_1 schedule-type weekly day wed
Product
SteelFusion Core
Related Commands
show storage backup policy, storage backup policy add, storage backup policy remove
storage backup policy remove
Removes a backup protection policy.
Syntax
[failover-peer] storage backup policy remove <policy-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Backup protection policy name.
Usage
The typical workflow for removing the backup protection follows:
1. Use the storage backup group remove command to remove the backup protection group.
2. Use the storage backup policy remove command to remove the backup protection policy.
3. Use the storage backup proxy remove command to remove the backup proxy.
4. Use the storage server remove command to remove Edge server.
Example
Core_01 (config) # storage backup policy remove Edge-xxx-VBP
Product
SteelFusion Core
Related Commands
show storage backup policy, storage backup policy add, storage backup policy modify
storage backup proxy remove
Removes a backup proxy.
Syntax
[failover-peer] storage backup proxy remove <proxy-id>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<proxy-id>
Proxy identifier.
Usage
You cannot remove a backup proxy while it is in use.
The typical workflow for removing the backup protection follows:
1. Use the storage backup group remove command to remove the backup protection group.
2. Use the storage backup policy remove command to remove the backup protection policy.
3. Use the storage backup proxy remove command to remove the backup proxy.
4. Use the storage server remove command to remove Edge server.
Example
Core_01 (config) # storage backup proxy remove sh-240-vsp-proxy
Product
SteelFusion Core
Related Commands
show storage backup proxy, storage backup proxy remove, storage backup proxy modify
storage block-disk
Configures block-disk settings.
Syntax
[failover-peer] storage block-disk [io-timeout <seconds> | post-scan-sleep <seconds> | read-pending <bytes> | write-pending <bytes> | latency <threshold>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
io-timeout <seconds>
Specifies the SG I/O timeout value in seconds.
post-scan-sleep <seconds>
Specifies the sleep time in seconds before scanning for new local disks available for discovery.
read-pending <bytes>
Specifies the maximum number of bytes allowed pending a read operation.
write-pending <bytes>
Specifies the maximum number of bytes allowed pending a write operation.
latency <threshold>
Specifies the target latency alarm parameters in milliseconds.
Example
Core_02 (config) # storage block-disk post-scan-sleep 20
Product
SteelFusion Core
Related Commands
storage block-disk rescan, storage block-disk scan enable
storage block-disk rescan
Rescans for new local disks available for discovery.
Syntax
storage block-disk rescan [full]
Parameters
full
Performs a full rescan.
Example
Core_01 (config) # storage block-disk rescan
Product
SteelFusion Core
Related Commands
storage iscsi chap add
storage block-disk scan enable
Enables block-device scanning.
Syntax
[failover-peer] storage block-disk scan enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Example
Core_01 (config) # storage block-disk scan enable
Product
SteelFusion Core
Related Commands
SteelFusion Core iSCSI (block mode) commands, storage block-disk rescan
storage server add
Adds an Edge server.
Syntax
[failover-peer] storage server add <server-id > edge-id <edge-id> hostname {<hostname> | <ip-address>} type {vmware_esxi username <name> password <password> | vmware_vcenter username <username> password <password> datacenter_name <name> | windows_server}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<server-id>
Server identifier. To view existing servers, run the show storage server all command.
edge-id <edge-id>
Specifies the identifier of the Edge appliance. Edge identifiers are case sensitive.
hostname <hostname>
Specifies the hostname.
hostname <ip-address>
Specifies the IP address of the host.
type
Specifies the server type.
•  vmware_esxi - VMware ESXi.
•  vmware_vcenter - VMware vCenter.
•  windows_server - Microsoft Windows server. You don’t need a username or password for the Windows server.
This option is not available for the NFS protocol in file mode.
username <name>
Specifies the username for the server type.
password <password>
Specifies the alphanumeric password for the user.
datacenter_name <name>
Specifies the data center name for the VMware vCenter.
Usage
The typical workflow for setting up backup protection follows:
1. Use the storage server add command to add an Edge server.
2. Use the storage backup proxy add command to add the backup proxy.
3. Use the storage backup policy add command to configure the backup protection policy.
4. Use the storage backup group add command to add the backup protection group.
Any virtual machines are automatically protected when a server is added to a policy.
Example
amnesiac (config) # storage server add sf-shxxx-server edge-id edge-xxx hostname 10.3.2.1 type vmware_esxi username eastcoastadmin password centadmin396Za!
Product
SteelFusion Core
Related Commands
show storage server, storage server modify
storage server modify
Modifies the Edge server settings.
Syntax
[failover-peer] storage server modify <server-id > [edge-id <edge-id>] [hostname {<hostname> | <ip-address>}] [type {vmware_esxi | vmware_vcenter | windows_server}] [username <username>] [password <password>] [datacenter_name <name>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<server-id>
Server identifier.
edge-id <edge-id>
Specifies the identifier of the Edge appliance.
hostname <hostname>
Specifies the hostname.
hostname <ip-address>
Specifies the IP address for the host.
type
Specifies the server type.
•  vmware_esxi - VMware ESXi.
•  vmware_vcenter - VMware vCenter.
•  windows_server - Microsoft Windows server. You don’t need a username or password for the Windows server.
This option is not available for the NFS protocol in file mode.
username <username>
Specifies the username for the server type.
password <password>
Specifies the alphanumeric password for the user.
datacenter_name <name>
Specifies the datacenter name for the VMware vCenter.
Example
amnesiac (config) # storage server modify sf-shxxx-server hostname 10.3.2.1 type vmware_esxi username eastcoastadmin
Product
SteelFusion Core
Related Commands
show storage server, storage server add, storage server remove
storage server remove
Removes the Edge server.
Syntax
[failover-peer] storage server remove <server-id>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<server-id>
Server identifier.
Usage
The typical workflow for removing the backup protection follows:
1. Use the storage backup group remove command to remove the backup protection group.
2. Use the storage backup policy remove command to remove the backup protection policy.
3. Use the storage backup proxy remove command to remove the backup proxy.
4. Use the storage server remove command to remove Edge server.
Example
Core01 (config) # storage server remove esxi
Product
SteelFusion Core
Related Commands
show storage server, storage server add, storage server modify
SteelFusion Core iSCSI (block mode) commands
edge id iscsi data-digest
Includes or excludes the data digest data in the iSCSI packet for the specified Edge.
Syntax
[failover-peer] edge id <id> iscsi data-digest {enable | disable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen.
enable
Includes the data digest in the iSCSI packet in communications with the specified Edge.
disable
Excludes the data digest from the iSCSI packet in communications with the specified Edge.
Usage
All failover-peer edge commands enable you to configure an unavailable Core through its failover peer. When the intended Core becomes operational, the new configuration is added automatically.
Example
Core_01 (config) # edge id branch-009a iscsi data-digest disable
Core_01 (config) # edge id branch-009a iscsi data-digest enable
 
Core_02 (config) # failover-peer edge id Edge1 iscsi data-digest disable
Core_02 (config) # failover-peer edge id Edge1 iscsi data-digest enable
Product
SteelFusion Core
Related Commands
show edge, storage iscsi data-digest
edge id iscsi header-digest
Includes or excludes the header digest in the iSCSI packet for the specified Edge.
Syntax
[failover-peer] edge id <id> iscsi header-digest {enable | disable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, . , and hyphen (- ).
enable
Includes the header digest in the iSCSI packet in communications with the specified Edge.
disable
Excludes the header digest from the iSCSI packet in communications with the specified Edge.
Usage
The header digest can help to identify, reject, or request retransmission of a corrupt Protocol Data Unit (PDU).
All failover-peer edge commands enable you to configure an unavailable Core through its failover peer. When the intended Core becomes operational, the new configuration is added automatically.
Example
Core_01 (config) # edge id branch-009a iscsi header-digest disable
Core_01 (config) # edge id branch-009a iscsi header-digest enable
 
Core_02 (config) # failover-peer edge id Edge1 iscsi header-digest disable
Core_02 (config) # failover-peer edge id Edge1 iscsi header-digest enable
Product
SteelFusion Core
Related Commands
show edge, storage iscsi header-digest
edge id iscsi initiator add
Adds an iSCSI initiator to the specified Edge.
Syntax
[failover-peer] edge id <id> iscsi initiator add <name> auth {CHAP chap-user <name> | None} [mutual-chap <name>]}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and
hyphen.
<name>
Name of the iSCSI initiator to add.
auth
Specifies one of the following authentication options:
•  CHAP chap-user <name> - Enables CHAP and specifies the CHAP username. You must specify an existing CHAP user.
•  None - Specifies no authentication.
mutual-chap <name>
Specifies the new value for the mutual CHAP user.
Example
Core_01 (config) # edge id Branch006a iscsi initiator add iqn.1991-05.com.microsoft:jshmoe-win7.wannabe.com CHAP chap-user Chap13NYC
 
Core_02 (config) # failover-peer edge id Edge1 iscsi initiator add iqn.1991-05.com.microsoft:jshmoe-win7.wannabe.com CHAP chap-user Chap13NYC
Product
SteelFusion Core
Related Commands
edge id iscsi initiator modify, edge id iscsi initiator remove, show edge
edge id iscsi initiator modify
Modifies the authorization configuration of an existing iSCSI initiator credential in the specified Edge.
Syntax
[failover-peer] edge id <id> iscsi initiator modify <name> auth {CHAP chap-user <chap-user> | None} [mutual-chap <name>]}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
<name>
Name of the iSCSI initiator to modify.
auth
Specifies one of the following authentication options:
•  CHAP chap-user <name> - Enables CHAP and specifies the CHAP username. You must specify an existing CHAP user.
•  None - Specifies no authentication.
mutual-chap <name>
Specifies the new value for the mutual CHAP user.
Usage
Use this command to modify the CHAP authorization settings for the specified iSCSI initiator credential at the specified Edge.
All failover-peer edge commands enable you to configure an unavailable Core through its failover peer. When the intended Core becomes operational, the new configuration is added automatically.
Example
Core_01 (config) # edge id Branch006a iscsi initiator modify iqn.1991-05.com.microsoft:jshmoe-win7.wannabe.com auth CHAP chap-user Chap13NYC
 
Core_02 (config) # failover-peer edge id Edge1 iscsi initiator modify iqn.1991-05.com.microsoft:jshmoe-win7.wannabe.com auth CHAP chap-user Chap13NYC
Product
SteelFusion Core
Related Commands
edge id iscsi initiator add, edge id iscsi initiator remove, show edge
edge id iscsi initiator remove
Removes the specified iSCSI initiator credential from the specified Edge configuration.
Syntax
[failover-peer] edge id <id> iscsi initiator remove <name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
<name>
iSCSI initiator credential to be removed.
Usage
All failover-peer edge commands enable you to configure an unavailable Core through its failover peer. When the Core returns to service, the new configuration is added automatically.
Consider the following example: Core1 and Core2 are configured as failover peers. Edge1 is linked to Core1. You want to remove an iSCSI initiator credential from the Edge1 configuration. However, Core1 is down but Core2 is operational. On Core2, run the following command:
failover-peer edge id Edge1 iscsi initiator remove iqn.1991-05.com.microsoft:jshmoe-win7.wannabe.com
When Core1 resumes operation, the Edge1 configuration changes are added to its configuration.
Example
Core_01 (config) # edge id Branch006a iscsi initiator remove iqn.1991-05.com.microsoft:jshmoe-win7.wannabe.com
 
Core_02 (config) # failover-peer edge id Edge1 iscsi initiator remove iqn.1991-05.com.microsoft:jshmoe-win7.wannabe.com
Product
SteelFusion Core
Related Commands
edge id iscsi initiator modify, show edge
edge id iscsi initiator-group
Creates or deletes an iSCSI initiator group for the specified Edge.
Syntax
[failover-peer] edge id <id> iscsi initiator-group {create | delete} <name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen
(-).
create <name>
Creates the specified iSCSI initiator group.
delete <name>
Deletes the specified iSCSI initiator group.
Example
Core_01 (config) # edge id Branch006a iscsi initiator-group create defaultiGroup
 
Core_02 (config) # failover-peer edge id Branch006a iscsi initiator-group create defaultiGroup
Product
SteelFusion Core
Related Command
show edge
edge id iscsi initiator-group modify
Modifies the iSCSI initiator group in the specified Edge by adding or removing an iSCSI initiator credential.
Syntax
[failover-peer] edge id <id> iscsi initiator-group modify <group-name> initiator {add | remove} <name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen.
<group-name>
iSCSI initiator group to be modified.
initiator
iSCSI initiator to be modified.
add <name>
Adds the specified iSCSI initiator credential to the group.
remove <name>
Adds the specified iSCSI initiator credential to the group.
Example
Core_01 (config) # edge id Branch006a iscsi initiator-group modify defaultiGroup initiator add iqn.1991-05.com.microsoft:jshmoe-win7.wannabe.com
 
Core_02 (config) # failover-peer edge id Branch006a iscsi initiator-group modify defaultiGroup initiator add iqn.1991-05.com.microsoft:jshmoe-win7.wannabe.com
Product
SteelFusion Core
Related Command
show edge
edge id iscsi target modify-name
Modifies the target name setting in the specified Edge.
Syntax
[failover-peer] edge id <id> iscsi target modify-name <target-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen.
<target-name>
New value for the target name.
Example
Core_01 (config) # edge id Edge1 iscsi target modify-name iqn.2003-10.com.hoosgau:432716056
 
Core_02 (config) # failover-peer edge id Edge1 iscsi target modify-name iqn.2003-10.com.hoosgau:432716056
Product
SteelFusion Core
Related Command
show edge
edge id iscsi target security-only
Configures the iSCSI target on the specified Edge to accept either secured or unsecured initiator authentication.
Syntax
[failover-peer] edge id <id> iscsi target security-only {enable | disable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen.
enable
Enables the specified Edge to accept only secured initiator authentication.
disable
Enables the specified Edge to accept unsecured initiator authentication.
Example
Core_01 (config) # edge id 10.1.2.3 iscsi target security-only enable
 
Core_02 (config) # failover-peer edge id 10.1.2.3 iscsi target security-only enable
Product
SteelFusion Core
Related Command
show edge
edge id prepop schedule add
Adds a new prepopulation schedule for the specified Edge.
Syntax
[failover-peer] edge id <id> prepop schedule add sched-name <sched-name> start-week-day <start-week-day> start-time <start-time> stop-week-day <stop-week-day> stop-time <stop-time>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
sched-name <sched-name>
Specifies the name of the prepopulation schedule.
start-week-day <start-week-day>
Specifies the start day for the schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
start-time <start-time>
Specifies the start time for the schedule. Use the format hh:mm:ss.
stop-week-day <stop-week-day>
Specifies the stop day for the schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
stop-time <stop-time>
Specifies the stop time for the schedule. Use the format hh:mm:ss.
Example
Core_01 (config) # edge id Branch006a prepop schedule add sched-name WeeklySynch start-week-day mon start-time 00:01:00 stop-week-day mon stop-time 03:01:00
 
Core_02 (config) # failover-peer edge id Branch006a prepop schedule add sched-name WeeklySynch start-week-day mon start-time 00:01:00 stop-week-day mon stop-time 03:01:00
Product
SteelFusion Core
Related Command
show edge
edge id prepop schedule modify
Modifies the settings of the specified prepopulation schedule on the specified Edge.
Syntax
[failover-peer] edge id <id> prepop schedule modify sched-name <sched-name> start-week-day <start-week-day> start-time <start-time> stop-week-day <stop-week-day> stop-time <stop-time>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
sched-name <sched-name>
Specifies a modified name of the prepopulation schedule.
start-week-day <start-week-day>
Specifies a modified start day for the schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
start-time <start-time>
Specifies a modified start time for the schedule. Use the format hh:mm:ss.
stop-week-day <stop-week-day>
Specifies a modified stop day for the schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
stop-time <stop-time>
Specifies a modified stop time for the schedule. Use the format hh:mm:ss.
Example
Core_01 (config) # edge id Branch006a prepop schedule modify sched-name MondaySynch start-week-day mon start-time 00:02:00 stop-week-day mon stop-time 03:02:00
 
Core_02 (config) # failover-peer edge id Branch006a prepop schedule modify sched-name MondaySynch start-week-day mon start-time 00:02:00 stop-week-day mon stop-time 03:02:00
Product
SteelFusion Core
Related Command
show edge
edge id prepop schedule remove
Removes the specified new prepopulation schedule from the specified SteelFusion Edge.
Syntax
[failover-peer] edge id <id> prepop schedule remove sched-name <sched-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
sched-name <sched-name>
Specifies the name of the prepopulation schedule to be removed.
Example
Core_01 (config) # edge id Branch006a prepop schedule remove sched-name MondaySynch
Core_02 (config) # failover-peer edge id Branch006a prepop schedule remove sched-name MondaySynch
Product
SteelFusion Core
Related Command
show edge
edge id virtual-ip
Adds or removes a virtual IP address configuration for the specified Edge.
Syntax
[failover-peer] edge id <id> virtual-ip {add | remove} <ip-address>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge to which the configuration is to be pushed. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
add <ip-address>
Specifies the virtual IP address to be configured for the specified Edge.
remove <ip-address>
Specifies the virtual IP address to be removed from the configuration.
Example
Core_01 (config) # edge id Branch006a virtual-ip add 10.0.0.2
 
Core_02 (config) # failover-peer edge id Branch006a virtual-ip add 10.0.0.2
Product
SteelFusion Core
Related Command
show edge
service hypervisor-mode reset
Resets the SteelFusion Core hypervisor mode and clears all settings.
Caution: Changing the hypervisor mode in production deployments can result in loss of storage configuration and data. We strongly recommend you contact Riverbed Support to reset the hypervisor mode on your Core appliance.
Syntax
service hypervisor-mode reset {set-hypervisor-mode-hyperv | set-hypervisor-mode-esxi}
Parameters
set-hypervisor-mode-hyperv
Resets the hypervisor mode to Hyper-V and clears all storage configurations.
set-hypervisor-mode-esxi
Resets the hypervisor mode to ESXi and clears all storage configurations.
Usage
You can reset the hypervisor mode only in the physical Cores. You cannot reset the hypervisor mode in Edges and Virtual Cores. In Hyper-V deployments, you must install the required Hyper-V license on the physical Core before you change the hypervisor mode from ESXi (default mode) to Hyper-V. To view and add licenses on the Core, choose Settings > Maintenance: Licenses to display the Licenses page. For information about installing licenses on the Core, see the SteelFusion Core Installation and Configuration Guide.
Perform these prerequisite tasks before you change the hypervisor mode on an existing Core:
•  Understand hypervisor modes and the effects of changing the hypervisor mode.
•  Contact Riverbed Support and specify your requirements for which you want to change the hypervisor mode.
For example, you are an existing SteelFusion customer and want to upgrade to SteelFusion 6.0. After upgrading, you want to allocate one of your existing SteelFusion Core appliances to protect data on the Virtual Edges deployed on Hyper-V. Therefore, you want to change the hypervisor mode on the Core from ESXi to Hyper‑V.
•  Disconnect all the configured Edge appliances from the Core to avoid data loss.
•  Disconnect any configured backend storage array from the Core.
•  Disconnect any configured HA peer from the Core.
•  Disconnect any configured replication Core from the primary Core.
The Core reboots immediately after you run the service hypervisor-mode reset command and confirm the reset operation. The Core boots up in the specified hypervisor mode and the block (iSCSI) mode. Use the show service command to display the current hypervisor and storage modes of the appliance.
Example
Core1(config)# service hypervisor-mode reset set-hypervisor-mode hyperv
 
Changing the hypervisor mode in production deployments can result in loss of storage configuration and data.
Review these effects, results, and recommendations before performing the hypervisor mode change operation.
 
Effects: Loss of storage configuration
 
Results: The Core reboots immediately after the command operation. The Core boots up in the specified hypervisor mode and the block (iSCSI) mode.
 
Recommendations:
Before you change the hypervisor mode, we recommend that you remove the configured Edge appliances to avoid data loss.
Use the 'service hypervisor-mode reset set-hypervisor-mode-hyperv confirm' command to proceed with the mode change operation.
Product
SteelFusion Core
Related Commands
show service
storage backup proxy add
Adds the backup proxy and configures the backup proxy settings.
Syntax
[failover-peer] storage backup proxy add <proxy-id> hostname {<proxy-hostname> | <ip-address>} type {vmware_esxi | windows_server} username <name> password <password> storage_group <storage-group>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<proxy-id>
Proxy identifier.
hostname <proxy-hostname>
Specifies the proxy hostname of the proxy host.
hostname <ip-address>
Specifies the IP address of the proxy host.
type vmware_esxi
Specifies the VMware ESXi compute type.
type windows_server
Specifies the Microsoft Windows Server compute type.
username <name>
Specifies the username for the backup proxy.
password <password>
Specifies the password for the proxy user.
storage_group <storage-group>
Specifies the storage group or initiator group for the backup proxy.
Usage
The Core integrates with the snapshot capabilities of the storage array. Once the snapshot reaches the data center, the Core triggers the application-consistent snapshot on the supported array and automatically mounts the snapshot to a proxy host. The backup software on the storage array can then perform the backups through the proxy host in the data center.
One backup proxy can be shared among multiple backup policies.
The typical workflow for setting up backup protection follows:
1. Use the storage server add command to add an Edge server.
2. Use the storage backup proxy add command to add the backup proxy.
3. Use the storage backup policy add command to configure the backup protection policy.
4. Use the storage backup group add command to add the backup protection group.
See the storage backup proxy add (NFS) command if you are running NFS Core.
Example
Core_01 (config) # storage backup proxy add sh-240-vsp-proxy hostname sf-shxxx155 type vmware_esxi username centraladmin password mypass storage_group sh-240-vsp-iqn
Product
SteelFusion Core
Related Commands
show storage backup proxy, storage backup proxy modify, storage backup proxy remove
storage backup proxy modify
Modifies the backup proxy settings.
Syntax
[failover-peer] storage backup proxy modify <proxy-id> [hostname <proxy-hostname>] [type {vmware_esxi | windows_server}] [username <name>] [password <password>] [storage_group <storage-group>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<proxy-id>
Proxy identifier.
hostname <proxy-hostname>
Specifies the proxy hostname or IP address of the proxy host.
type vmware_esxi
Specifies the VMware ESXi compute type.
type windows_server
Specifies the Microsoft Windows Server compute type.
username <name>
Specifies the username for the backup proxy.
password <password>
Specifies the password for the proxy user.
storage_group <storage-group>
Specifies the storage group or initiator group for the backup proxy.
Usage
One backup proxy can be shared among multiple backup policies.
See the storage backup proxy modify (NFS ) command if you are running NFS Core.
Example
Core_01 (config) # storage backup proxy modify sh-240-vsp-proxy password centadmin396Za!
Product
SteelFusion Core
Related Commands
show storage backup proxy, storage backup proxy remove, storage backup proxy remove
storage coredr clear
Clears the existing data center replication setup. This command is only available from the primary data center, and only permitted if the secondary data center is connected. When high-availability is configured, this command is only permitted on the primary data center leader. For more information about leader and follower roles, see the SteelFusion Core Management Console User Guide.
Syntax
storage coredr clear
Parameters
None
Usage
This command is part of a workflow for terminating disaster recovery on the Core:
1. Use the storage coredr lun remove-replica command to unmap each replica LUN from the secondary data center before proceeding.
2. Use the storage coredr clear command.
3. Use the storage coredr edge command to stop replication on the Edges.
4. Use the show storage coredr edge command to verify that replication is stopped. If "Peer Site ID" is shown as "Not Configured,” you have stopped replication successfully.
5. Use the storage coredr clear-params command to completely remove disaster recovery settings.
Example
amnesiac (config) # storage coredr clear
Product
SteelFusion Core
Related Commands
storage coredr clear-params, storage coredr edge, storage coredr lun remove-replica, storage coredr setup peer
storage coredr clear-params
Clears the previously set parameters for replication, such as data center name, journal LUN, and replication interface.
Syntax
storage coredr clear-params
Parameters
None
Usage
After you terminate the replication configuration, use this command to clear the configured disaster recovery parameters.
Example
amnesiac (config) # storage coredr clear-params
Product
SteelFusion Core
Related Commands
storage iscsi array-settings, storage coredr set-params
storage coredr data-checker enable
Enables the data checker if it has been disabled.
Syntax
[no] [failover-peer] storage coredr data-checker enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Usage
Data checker is the component that performs background checks of the data blocks on the replica. It is automatically enabled and always runs in the background. It only reports data inconsistencies and cannot repair the replicas.
The no disables the data checker.
Example
Core_01 (config) # storage coredr data-checker enable
Core_02 (config) # failover-peer storage coredr data-checker enable
Product
SteelFusion Core
Related Command
storage iscsi chap username, storage coredr lun alias clear-alarm
storage coredr data-checker global-datarate
Configures the global data rate for the data checker.
Syntax
storage coredr data-checker global-datarate <rate>
Parameters
<rate>
Global data rate in KBps or MBps. The range of the rate is > 0 and < 1 GBps.
Usage
This command provides flexibility to increase or decrease the speed of the data checker.
You can find the current rate through syslog, for example:
Jan 22 16:40:14 sf-sh300 dc[2353]: [coredr.NOTICE] - Data checker rates updated: Max rate: 1.00 MBps, Per replica rate: 500.00 KBps
Jan 22 16:40:14 sf-sh300 dc[2353]: [coredr/checker/P3KQG5NqMIHh.NOTICE] - Data checker operating at data_rate=500.00 KBps, iops=8, io_sz=128, max_parallel_ios=5
Jan 22 16:40:14 sf-sh300 dc[2353]: [coredr/checker/P3KQG5NqMJ4I.NOTICE] - Data checker operating at data_rate=500.00 KBps, iops=8, io_sz=128, max_parallel_ios=5
Example
Core_01 (config) # storage coredr data-checker global-datarate 128
 
Core_02 (config) # failover-peer storage coredr data-checker global-datarate 128
Product
SteelFusion Core
Related Commands
storage coredr data-checker enable, storage coredr lun alias clear-alarm
storage coredr edge
Starts or stops replication for the LUNs on the specified Edge.
Syntax
[failover-peer] storage coredr edge <id> {start | stop}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<id>
Self-identifier of the Edge you want to start or stop. This value is case sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.) , and hyphen (-).
start
Starts replication on the specified Edge.
stop
Stops replication on the specified Edge.
Usage
Use this command as a first step to stopping replication and clearing the existing configuration.
Product
SteelFusion Core
Example
amnesiac (config)# > storage coredr edge Edge01NYC start
Related Commands
storage iscsi array-settings, storage coredr lun remove-replica, storage coredr lun replicate-to, show storage coredr edge
storage coredr failover
Initiates failover to a secondary data center if the primary data center goes down. After failover, writes from the Edges will be committed to the new primary data center storage array and will also be journaled. When the original primary data center recovers and the connections between data centers are reestablished, the original primary data center will automatically take the role of secondary data center and replication to the new secondary data center is automatically resumed.
Syntax
storage coredr failover
Parameters
None
Usage
You must enter this command from the secondary data center Core if the primary data center goes down.
To verify that failover was successful, use the show storage coredr settings command from the secondary Core. The Core’s Site Role should now show as Primary.
Example
amnesiac (config) # storage coredr failover
Product
SteelFusion Core
Related Commands
show storage coredr edge, storage coredr replication suspend
storage coredr interface
Adds or removes an interface for replication.
Syntax
storage coredr interface {add | remove} <interface-name>
Parameters
add
Adds the specified interface for replication.
remove
Removes the specified interface for replication.
<interface-name>
Interface to be used for replication.
Usage
Use the storage coredr interface add command to add an interface for replication between disaster recovery sites. Additional interfaces provide extra redundancy for the connection.
Use the storage coredr interface remove command to remove an interface from being used for replication. This is useful if the connection on the particular interface is down or if the interface itself becomes faulty.
Product
SteelFusion Core
Example
amnesiac (config) # storage coredr interface add eth0_0
Related Commands
storage coredr clear-params, storage coredr set-params
storage coredr lun alias clear-alarm
Clears the data corruption alarm.
Syntax
[failover-peer] storage coredr lun alias <alias> clear-alarm
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Alias for the LUN.
Usage
This command only clears the data corruption alarm but not the actual corruption itself.
If the data corruption exists, the alarm will be raised again the next time the data checker runs across a mismatch.
Product
SteelFusion Core
Example
amnesiac (config)# > storage coredr lun alias ORIG12P5D clear-alarm
Related Commands
alarm enable (Core), storage coredr data-checker enable, storage coredr data-checker global-datarate
storage coredr lun remove-replica
Removes the specified replicated LUN from the configuration.
Syntax
[failover-peer] storage coredr lun {alias <lun-alias> | site-serial <lun-serial>} remove-replica
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <lun-alias>
Specifies the alias for the LUN.
site-serial <lun-serial>
Specifies the serial number for the LUN.
Usage
Use this command when you no longer want to replicate a LUN to the secondary data center.
Before using this command, you must stop replication on the Edge where the specified LUN is mapped.
Example
Core01 # storage coredr lun site-serial ORIG12P5D remove-replica
 
Core02 # failover-peer storage coredr lun alias ORIG12P5D remove-replica
Product
SteelFusion Core
Related Command
storage coredr lun replicate-to
storage coredr lun replicate-to
Creates a copy of existing data on the primary data center and transfers it to a replica LUN on the secondary data center.
Syntax
[failover-peer] storage coredr lun {alias <lun-alias> | site-serial <lun-serial>} replicate-to <secondary-lun-serial> [first-sync {full | none}]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <lun-alias>
Specifies the alias for the replicable LUN.
site-serial <lun-serial>
Specifies the site-specific serial number for the LUN.
<secondary-lun-serial>
Serial number of the LUN at the secondary data center.
first-sync
Configures the first-sync type for the replication between the primary and replica LUNs.
•  full - Block-by-block replication that can take longer, depending on the size of the LUN.
•  none - Does not synchronize between data centers. Use this option if the LUNs are already block-for-block identical in both data centers (that is, the LUNs are empty or unformatted).
Note: It is important that only SteelFusion has access to the data center LUNs in order to ensure block-for-block consistency between the primary and secondary data centers.
Usage
After you have set up the witness using the storage coredr witness set command, use storage coredr lun replicate-to (this command) to set up the replica LUNs and start the first sync.
Replica LUNs should be equal in size or larger than the primary LUNs; however, some storage arrays do not allocate exact sizes. For this reason, Core will allow a small size leeway for the replica LUN. Possible candidates for replicas are auto-completed and displayed.
To view a list of primary and replica LUNs and their serial numbers on each data center, use the show storage coredr edge command.
Example
Core02 # failover-peer storage coredr lun alias lun1 replicate-to P3KRP50GDleg first-sync none
 
Core01 # storage coredr lun site-serial P3KRP50GDleg replicate-to P3KRP4zabEvv first-sync full
Product
SteelFusion Core
Related Commands
storage coredr edge, show storage coredr replica size-leeway, storage coredr lun remove-replica
storage coredr replication resume
Resumes replication. When replication is resumed, the journaled writes will be resynced to the secondary data center.
Syntax
[failover-peer] storage coredr replication resume
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Usage
When the WAN connection is recovered between disaster recovery sites, use this command to restart replication between the data centers.
Example
Core02 # failover-peer storage coredr replication resume
Product
SteelFusion Core
Related Command
storage coredr replication suspend
storage coredr replication suspend
Suspends replication. During a planned or extended WAN failure, suspending replication will allow Edge writes to be committed to the primary data center storage array without being replicated to the secondary data center, thus preventing the blockstore on the Edge from overfilling. Writes will be journaled when replication is suspended.
Syntax
[failover-peer] storage coredr replication suspend
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Usage
Use this command during a planned or extended WAN failure when the connection between disaster recovery sites is down. While the data center is down, this command allows Edge writes to be committed to the primary data center storage backend.
Example
Core01 # storage coredr replication suspend
Product
SteelFusion Core
Related Command
storage coredr replication resume
storage coredr set-params
Sets the parameters for disaster recovery in the primary or secondary data center.
Syntax
storage coredr set-params {primary | secondary} site <site-id> journal-lun <journal-lun> interface <interface-name>
Parameters
primary
Sets disaster recovery parameters for the primary data center.
secondary
Sets disaster recovery parameters for the secondary data center.
site <site-id>
Specifies the site ID for the primary or secondary data center.
journal-lun <journal-lun>
Specifies the serial number for the journal LUN that you created on the storage array. For more information about journal LUNs and configuring replication, see the SteelFusion Core Management Console User Guide.
interface <interface-name>
Specifies the interface for replication use. We recommend that you use different replication interfaces for each data center; however, if you have two Cores that are set up for high availability, assign the same interface to both.
Usage
This command is part of a workflow for configuring disaster recovery on the Core:
1. Use the storage coredr set-params (the current command) to specify the roles and parameters of the primary and secondary data centers. To review these parameters before continuing, use the show storage coredr settings command.
2. On the secondary data center Core, use the storage coredr setup peer command to peer the two data centers together. To confirm that you have successfully peered the Cores before continuing, use the show storage coredr settings command.
3. Use the storage coredr witness set command to set up the Witness Edge.
4. Use the storage coredr lun replicate-to command to map the replica LUNs and start first sync.
Example
amnesiac (config) # storage coredr set-params secondary site NYC journal-lun P3KRP53Wrqqy interface eth0_0
Product
SteelFusion Core
Related Command
storage coredr setup peer
storage coredr setup peer
Enables the secondary data center to communicate with the primary data center.
Syntax
storage coredr setup peer <secondary-ip> site <secondary-site-id>
Parameters
<secondary-ip>
IP address for the secondary data center.
site <secondary-site-id>
Specifies the site ID for the secondary data center.
Usage
After you have specified the roles of the primary and secondary data center using the storage coredr set-params command, you will use storage coredr setup peer (this command) from the primary data center to peer the Cores with one another.
Example
amnesiac (config) # storage coredr setup peer 10.5.123.122 site site2
Product
SteelFusion Core
Related Commands
storage coredr set-params, storage coredr witness set
storage coredr witness set
Sets up the witness Edge for disaster recovery. The witness monitors the state of both the primary and secondary Cores. If both Cores are in a state where failover is not possible (due to failed configuration synchronization, etc.), the witness will report that failover is not ready and will not succeed.
Syntax
storage coredr witness set <edge-id>
Parameters
<edge-id>
IP address for the Edge that will serve as the witness.
Usage
After you have peered the Cores together using the storage coredr setup peer command, you will use storage coredr witness set (this command) to set up the witness.
Example
amnesiac (config) # storage coredr witness set Edge01NYC
Product
SteelFusion Core
Related Commands
storage coredr lun replicate-to, storage coredr setup peer
storage iscsi array-settings
Adds or removes settings for the specified array type.
Syntax
[failover-peer] storage iscsi array-settings {add | remove} array-id <array-type>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
add
Adds a type of array.
remove
Removes a type of array.
array-id <array-type>
Specifies a type of array.
The format is <VendorID>:<ProductID>:<Revision>.
Example
Core_01 (config) # storage iscsi array-settings add array-id Nimble:Server:1.0
Service restart required for changes to take effect
Product
SteelFusion Core
Related Command
show storage iscsi
storage iscsi chap add
Adds a CHAP user to the current storage configuration.
Syntax
[failover-peer] storage iscsi chap add username <username> password <password>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
username <username>
Specifies the username for CHAP authentication.
password <password>
Specifies the password for the new CHAP user.
Example
Core_01 (config) # storage iscsi chap add username DefaultChap password CHAPpw
 
Core_02 (config) # failover-peer storage iscsi chap add username DefaultChap password CHAPpw
Product
SteelFusion Core
Related Command
show storage iscsi
storage iscsi chap delete
Deletes the specified CHAP user from the current storage configuration.
Syntax
[failover-peer] storage iscsi chap delete username <username> [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
username <username>
Specifies the CHAP user to be deleted.
force
Forces deletion if the CHAP user is currently enabled.
Example
Core_01 (config) # storage iscsi chap delete username DefaultChap
 
Core_02 (config) # failover-peer storage iscsi chap delete username DefaultChap
Product
SteelFusion Core
Related Command
show storage iscsi
storage iscsi chap modify
Modifies the password of the specified CHAP user.
Syntax
[failover-peer] storage iscsi chap modify username <username> password <password>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
username <username>
Specifies the CHAP user whose password is to be modified.
password <password>
Specifies the new password for the CHAP user.
Example
Core_01 (config) # storage iscsi chap modify username DefaultChap password newCHAPpw
 
Core_02 (config) # failover-peer storage iscsi chap modify username DefaultChap password newCHAPpw
Product
SteelFusion Core
Related Command
show storage iscsi
storage iscsi chap username
Enables or disables the specified CHAP user.
Syntax
[failover-peer] storage iscsi chap username <name> {disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<name>
CHAP user to be enabled or disabled.
disable
Disables the specified CHAP user.
enable
Enables the specified CHAP user.
Usage
Run the show storage iscsi command to display whether or not the CHAP user is enabled.
Disable or enable the CHAP user as needed.
Example
Core_01 (config) # storage iscsi chap username JoeyD disable
 
Core_02 (config) # failover-peer storage iscsi chap username JoeyD disable
Product
SteelFusion Core
Related Command
show storage iscsi
storage iscsi data-digest
Includes or excludes the data digest in the iSCSI PDU.
Syntax
[failover-peer] storage iscsi data-digest {disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
disable
Excludes the data digest from the iSCSI PDU.
enable
Includes the data digest in the iSCSI PDU.
Usage
The data digest can help to identify, reject, or request retransmission of a corrupt PDU.
Example
Core_01 (config) # storage iscsi data-digest disable
Core_01 (config) # storage iscsi data-digest enable
 
Core_02 (config) # failover-peer storage iscsi data-digest disable
Core_02 (config) # failover-peer storage iscsi data-digest enable
Product
SteelFusion Core
Related Commands
edge id blockstore uncommitted, show storage iscsi
storage iscsi header-digest
Includes or excludes the header digest in or from the iSCSI PDU.
Syntax
[failover-peer] storage iscsi header-digest {enable | disable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
enable
Includes the header digest in the iSCSI PDU.
disable
Excludes the header digest from the iSCSI PDU.
Usage
The header digest can help to identify, reject, or request retransmission of a corrupt PDU.
Example
Core_01 (config) # storage iscsi header-digest disable
Core_01 (config) # storage iscsi header-digest enable
 
Core_02 (config) # failover-peer storage iscsi header-digest disable
Core_02 (config) # failover-peer storage iscsi header-digest enable
Product
SteelFusion Core
Related Commands
edge id iscsi header-digest, show storage iscsi
storage iscsi initiator modify auth mutual-chap
Configures iSCSI initiator authentication mutual CHAP settings.
Syntax
[failover-peer] storage iscsi initiator modify auth mutual-chap {chap-user <name> | disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
chap-user <name>
Specifies the mutual CHAP user. You must specify an existing CHAP user.
disable
Disables mutual CHAP authentication.
enable
Enables mutual CHAP authentication.
Usage
Use this command to:
•  enable or disable mutual CHAP authentication for the iSCSI initiator configuration.
•  specify the mutual CHAP user.
You can specify only existing CHAP users.
Example
Core_02 (config) # storage iscsi initiator modify auth mutual-chap chap-user existingCHAPUser
 
Core_02 (config) # storage iscsi initiator modify auth mutual-chap enable
Product
SteelFusion Core
Related Commands
show storage iscsi, storage iscsi initiator modify name
storage iscsi initiator modify name
Modifies the initiator name in the iSCSI initiator configuration.
Syntax
[failover-peer] storage iscsi initiator modify name <name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<name>
New initiator name for the iSCSI initiator configuration.
Example
Core_01 (config) # storage iscsi initiator modify name iqn.2003-10.com.hoosegow:werdna-initiator
 
Core_02 (config) # failover-peer storage iscsi initiator modify name iqn.2003-10.com.hoosegow:werdna-initiator
Product
SteelFusion Core
Related Command
show storage iscsi
storage iscsi mpio interface add
Adds the specified local interface for MPIO to the iSCSI initiator configuration.
Syntax
storage iscsi mpio interface add name <name>
Parameters
name <name>
Specifies the local interface to be added.
Example
Core_01 (config) # storage iscsi mpio interface add name eth0_1
Product
SteelFusion Core
Related Commands
show storage iscsi mpio interfaces, storage iscsi mpio interface remove name, storage iscsi session mpio standard-routes
storage iscsi mpio interface remove name
Removes the specified local interface for MPIO from the iSCSI initiator configuration.
Syntax
[failover-peer] storage iscsi mpio interface remove name <name> [all]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<name>
Local interface to be removed.
To view a list of local interfaces configured for MPIO, use the show storage iscsi mpio interfaces command.
all
Removes all MPIO interfaces.
Example
Core_01 (config) # show storage iscsi mpio interfaces
Interfaces configured for MPIO
eth0_2
eth0_3
 
Core_01 (config) # storage iscsi mpio interface remove name eth0_2
 
Core_02 (config) # failover-peer storage iscsi mpio interface remove name eth0_2
Product
SteelFusion Core
Related Commands
show storage iscsi disc-portals portal, storage iscsi mpio interface add, storage iscsi session mpio standard-routes
storage iscsi portal add host
Adds an iSCSI portal configuration to the iSCSI initiator configuration.
Syntax
[failover-peer] storage iscsi portal add host <hostname> [alias <alias-name>] [port <port-number>] auth {CHAP chap-user <name> | None}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal.
alias <alias-name>
Specifies an alias name for the portal.
port <port-number>
Specifies a port number. The default is 3260.
auth
Specifies the authentication option:
•  CHAP chap-user <name> - Enables CHAP and specifies the CHAP username. You must specify an existing CHAP user.
•  None - No authentication.
Example
Core_01 (config) # storage iscsi portal add host 10.2.3.4 port 3260 auth CHAP chap-user JoeyD
 
Core_02 (config) # failover-peer storage iscsi portal add host 10.2.3.4 port 3260 auth CHAP chap-user JoeyD
Product
SteelFusion Core
Related Commands
storage iscsi portal host target add, storage iscsi portal host target modify, storage iscsi portal host target remove, storage iscsi portal modify host auth, storage iscsi portal modify host port, storage iscsi portal remove host
storage iscsi portal host disc-portal add
Manually adds a discovered portal IP address to the iSCSI portal configuration.
Syntax
[failover-peer] storage iscsi portal host <hostname> disc-portal add ip <ip-address> [port <port-number>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal configuration to which the additional IP address is to be added.
ip <ip-address>
Specifies the IP address of the added, discovered portal.
port <port-number>
Specifies the discovered portal port number.
Usage
If you have enabled multipath I/O (MPIO), this command enables you to add existing IP addresses available on the filer for connections with the Core.
MPIO enables a single iSCSI portal configuration to connect with the filer on multiple IP addresses.
Use the storage iscsi portal host rescan-portals command to discover portals on the specified iSCSI initiator.
Example
Core_01 (config) # storage iscsi portal host 123.45.6.789 add 132.45.6.780
 
Core_02 (config) # failover-peer storage iscsi portal host 123.45.6.789 add 132.45.6.780
Product
SteelFusion Core
Related Commands
show storage iscsi disc-portals portal, storage iscsi portal host disc-portal modify, storage iscsi portal host disc-portal remove, storage iscsi portal host rescan-portals
storage iscsi portal host disc-portal modify
Modifies the ID and/or port settings of the specified portal host configuration.
Syntax
[failover-peer] storage iscsi portal host <hostname> disc-portal modify id <disc-portal> port <port-number>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal configuration that is to be modified.
id <disc-portal>
Specifies the new ID value for the specified portal host.
port <port-number>
Specifies the new port number for specified portal host.
Usage
This command is intended to be used for portals discovered for multi-path I/O (MPIO) configurations. MPIO enables a single iSCSI portal configuration to connect with the filer on multiple IP addresses.
Use the storage iscsi portal host rescan-portals command to discover portals on the specified iSCSI initiator portal.
Example
Core_01 (config) # storage iscsi portal host 123.45.6.789 disc-portal modify id principal port 3260
 
Core_02 (config) # failover-peer storage iscsi portal host 123.45.6.789 disc-portal modify id principal port 3260
Product
SteelFusion Core
Related Command
show storage iscsi disc-portals portal
storage iscsi portal host disc-portal remove
Removes the specified discovered portal configuration from the iSCSI portal configuration.
Syntax
[failover-peer] storage iscsi portal host <hostname> disc-portal remove id <disc-portal>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal configuration to which the additional IP address is to be added.
id <disc-portal>
Specifies the IP address of the discovered portal to be removed from the iSCSI portal configuration.
Usage
This command is intended to be used for portals discovered for multi-path I/O (MPIO) configurations. MPIO enables a single iSCSI portal configuration to connect with the filer on multiple IP addresses.
Use the storage iscsi portal host rescan-portals command to discover portals on the specified iSCSI initiator portal.
Example
Core_01 (config) # storage iscsi portal host 123.45.6.789 disc-portal remove 132.45.6.780
 
Core_02 (config) # failover-peer storage iscsi portal host 123.45.6.789 disc-portal remove 132.45.6.780
Product
SteelFusion Core
Related Commands
show stats storage filer-iops, storage iscsi portal host disc-portal add, storage iscsi portal host disc-portal modify, storage iscsi portal host rescan-portals
storage iscsi portal host offline-luns
Takes offline all configured LUNs serviced by the specified portal.
Syntax
[failover-peer] storage iscsi portal host <hostname> offline-luns
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal.
Example
Core_01 (config) # storage iscsi portal host 10.2.3.4 offline-luns
 
Core_02 (config) # failover-peer storage iscsi portal host 10.2.3.4 offline-luns
Product
SteelFusion Core
Related Commands
storage iscsi mpio interface add, storage iscsi portal host disc-portal modify, storage iscsi portal host target modify
storage iscsi portal host rescan-luns
Rescans iSCSI targets associated with the specified portal.
Syntax
[failover-peer] storage iscsi portal host <hostname> rescan-luns {all | target name <name>}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal.
all
Rescans all iSCSI targets associated with the specified portal.
target name <name>
Rescans only the specified target.
Usage
Use this command to ensure that recently configured iSCSI targets are added.
Example
Core_01 (config) # storage iscsi portal host 10.2.3.4 rescan all
 
Core_02 (config) # failover-peer storage iscsi portal host 10.2.3.4 rescan all
Product
SteelFusion Core
Related Command
storage iscsi portal host rescan-targets
storage iscsi portal host rescan-portals
Rescans the specified iSCSI portal configuration for discoverable and available portals.
Syntax
[failover-peer] storage iscsi portal host <hostname> rescan-portals
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal configuration from which the discovered portal is to be removed.
Usage
After portals have been discovered, you can add them to the iSCSI portal configuration using the storage iscsi portal host disc-portal add command.
This command is intended to be used for portals discovered for multi-path I/O (MPIO) configurations. MPIO enables a single iSCSI portal configuration to connect with the filer on multiple IP addresses.
Example
Core_01 (config) # storage iscsi portal host 123.45.6.789 rescan-portals
 
Core_02 (config) # failover-peer storage iscsi portal host 123.45.6.789 rescan-portals
Product
SteelFusion Core
Related Commands
storage iscsi portal host disc-portal add, storage iscsi portal host disc-portal modify, storage iscsi portal host disc-portal remove
storage iscsi portal host rescan-targets
Rescans all iSCSI targets associated with the specified portal.
Syntax
[failover-peer] storage iscsi portal host <hostname> rescan-targets
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal.
Usage
Use this command to ensure that recently configured iSCSI targets are added.
Example
Core_01 (config) # storage iscsi portal host 10.2.3.4 rescan-targets
 
Core_02 (config) # failover-peer storage iscsi portal host 10.2.3.4 rescan-targets
Product
SteelFusion Core
Related Commands
storage iscsi portal host rescan-luns, storage iscsi portal host target modify
storage iscsi portal host target add
Adds an iSCSI target configuration to the specified portal.
Syntax
[failover-peer] storage iscsi portal host <hostname> target add name <name> [port <port-number>] [snapshot-host <hostname>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal to which the target is to be added.
name <name>
Specifies the name of the target.
port <port-number>
Specifies a port number the iSCSI target is listening on. The default is 3260.
snapshot-host <hostname>
Specifies the IP address for the storage snapshot.
Example
Core_01 (config) # storage iscsi portal host 10.2.3.4 target add name iqn.2003-10.com.hoosgau:432716056 port 3260
 
Core_02 (config) # failover-peer storage iscsi portal host 10.2.3.4 target add name iqn.2003-10.com.hoosgau:432716056 port 3260
Product
SteelFusion Core
Related Commands
storage iscsi portal host target modify, storage iscsi portal host target remove
storage iscsi portal host target modify
Modifies the settings of the specified iSCSI portal target.
Syntax
[failover-peer] storage iscsi portal host <hostname> target modify name <name> [latency threshold <ms>] [port <port-number>] [snapshot-host <hostname>] [snapshot-method {none | auto}]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal with the target configuration.
name <name>
Modifies the name of the target.
latency threshold <ms>
Modifies the latency threshold, in milliseconds.
port <port-number>
Modifies the port number the iSCSI target is listening on. The default is 3260.
snapshot-host <hostname>
Modifies the hostname for the storage snapshot.
snapshot-method
Modifies the snapshot method by specifying one of the following methods:
•  none - No snapshot management.
•  auto - Automatically detect snapshot management if already configured.
Example
Core_01 (config) # storage iscsi portal host 10.2.3.4 target modify name iqn.2003-10.com.hoosgau:432716056
 
Core_02 (config) # failover-peer storage iscsi portal host 10.2.3.4 target modify name iqn.2003-10.com.hoosgau:432716056
Product
SteelFusion Core
Related Commands
storage iscsi portal host target remove, storage iscsi portal host target remove
storage iscsi portal host target offline-luns
Takes offline all configured LUNs serviced by the specified iSCSI target.
Syntax
[failover-peer] storage iscsi portal host <hostname> target offline-luns name <name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal with the target configuration.
name <name>
Specifies the name of the target.
Example
Core_01 (config) # storage iscsi portal host 10.2.3.4 target offline-luns name iqn.2003-10.com.hoosgau:432716056
 
Core_02 (config) # failover-peer storage iscsi portal host 10.2.3.4 target offline-luns name iqn.2003-10.com.hoosgau:432716056
Product
SteelFusion Core
Related Commands
storage iscsi portal host target modify
storage iscsi portal host target remove
Removes an iSCSI target configuration from the specified portal.
Syntax
[failover-peer] storage iscsi portal host <hostname> target remove name <name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal with the target configuration to be removed.
name <name>
Specifies the name of the target to be removed.
Usage
You must first remove all LUNs from a target before you can remove the target itself.
Use the storage lun remove command to remove all LUNs from a target.
Example
Core_01 (config) # storage iscsi portal host 10.2.3.4 target remove name iqn.2003-10.com.hoosgau:432716056
 
Core_02 (config) # failover-peer storage iscsi portal host 10.2.3.4 target remove name iqn.2003-10.com.hoosgau:432716056
Product
SteelFusion Core
Related Commands
storage iscsi portal host target modify, storage iscsi portal host target modify
storage iscsi portal modify host alias
Modifies the alias settings of the specified iSCSI portal.
Syntax
[failover-peer] storage iscsi portal modify host <hostname> alias <alias-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal to be modified.
alias <alias-name>
Alias name.
Usage
This command allows you to modify the portal within a running session.
Example
Core_01 (config) # storage iscsi portal modify host 10.2.3.4 alias companyxyz
 
Core_02 (config) # failover-peer storage iscsi portal modify host 10.2.3.4 alias companyxyz
Product
SteelFusion Core
Related Commands
storage iscsi portal host target modify storage iscsi portal host target remove
storage iscsi portal modify host auth
Modifies the authentication settings of the specified iSCSI portal.
Syntax
[failover-peer] storage iscsi portal modify host <hostname> auth {CHAP chap-user <name> | None}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal to be modified.
CHAP chap-user <name>
Enables the CHAP authentication option and specifies the CHAP username. You must specify an existing CHAP user.
None
No authentication.
Usage
This command allows you to modify the portal within a running session.
Example
Core_01 (config) # storage iscsi portal modify host 10.2.3.4 auth None
 
Core_02 (config) # failover-peer storage iscsi portal modify host 10.2.3.4 auth None
Product
SteelFusion Core
Related Commands
storage iscsi portal host target modify storage iscsi portal host target remove
storage iscsi portal modify host port
Modifies the port settings of the specified iSCSI portal.
Syntax
[failover-peer] storage iscsi portal modify host <hostname> port <port-number>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal whose port setting is to be modified.
<port-number>
New port number for the iSCSI portal to listen on. The default is 3260.
Example
Core_01 (config) # storage iscsi portal modify host 10.2.3.4 port 3260
 
Core_02 (config) # failover-peer storage iscsi portal modify host 10.2.3.4 port 3260
Product
SteelFusion Core
Related Commands
storage iscsi portal host target modify, storage iscsi portal remove host
storage iscsi portal remove by-alias
Removes an iSCSI portal configuration from the iSCSI initiator configuration using the alias name.
Syntax
[failover-peer] storage iscsi portal remove by-alias <alias-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<alias-name>
Alias name of the iSCSI portal configuration to be removed.
Example
Core_01 (config) # storage iscsi portal remove by-alias companyxyz
 
Core_02 (config) # failover-peer storage iscsi portal remove by-alias companyxyz
Product
SteelFusion Core
Related Commands
storage iscsi portal host target modify, storage iscsi portal host target remove
storage iscsi portal remove host
Removes an iSCSI portal configuration from the iSCSI initiator configuration.
Syntax
[failover-peer] storage iscsi portal remove host <hostname>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the iSCSI portal configuration to be removed.
Example
Core_01 (config) # storage iscsi portal remove host 10.2.3.4
 
Core_02 (config) # failover-peer storage iscsi portal remove host 10.2.3.4
Product
SteelFusion Core
Related Commands
storage iscsi portal host target modify, storage iscsi portal host target remove
storage iscsi report-naa-id enable
Enables reporting of the iSCSI Network Address Authority (NAA) serial format at the configured Edges.
Syntax
[failover-peer] storage iscsi report-naa-id enable [edge id <id>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
edge id <id>
Specifies the identifier of a particular configured Edge.
Example
Core_01 (config) # storage iscsi portal report-naa-id enable edge id main-sh123
 
Core_02 (config) # failover-peer storage iscsi portal report-naa-id enable
Product
SteelFusion Core
Related Command
show storage iscsi
storage iscsi session data-digest enable
Includes the data digest in the iSCSI PDU for the current session; the running configuration does not change.
Syntax
[no] [failover-peer] storage iscsi session data-digest enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Usage
The data digest can help to identify, reject, or request retransmission of a corrupt PDU for the current. This does not affect the running configuration or other sessions. To change the configuration permanently, use the storage iscsi data-digest.
Use the no command option to disable this feature.
Example
Core_01 (config) # storage iscsi session data-digest enable
 
Core_02 (config) # no storage iscsi session data-digest enable
Product
SteelFusion Core
Related Commands
show storage iscsi storage iscsi session header-digest enable
storage iscsi session header-digest enable
Includes the header digest in the iSCSI PDU for the current session; the running configuration does not change.
Syntax
[no] [failover-peer] storage iscsi session header-digest enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Usage
The header digest can help to identify, reject, or request retransmission of a corrupt PDU. This does not affect the running configuration or other sessions. To change the configuration permanently, use the storage iscsi header-digest command.
Use the no command option to disable this feature.
Example
Core_02 (config) # storage iscsi session header-digest enable
 
Core_02 (config) # failover-peer storage iscsi session header-digest enable
Product
SteelFusion Core
Related Commands
edge id iscsi header-digest, show storage iscsi, storage iscsi session data-digest enable
storage iscsi session immediate-data enable
Enables the initiator to attach the write data command to the initial iSCSI PDU.
Syntax
[no] [failover-peer] storage iscsi session immediate-data enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Usage
Together with the storage iscsi session initial-r2t enable command, the storage iscsi session immediate-data enable command can reduce I/O time by eliminating the need for an additional round trips in small write commands between the initiator the target.
Use the no command option to disable this feature.
Example
Core_02 (config) # storage iscsi session immediate-data enable
 
Core_02 (config) # failover-peer storage iscsi session immediate-data enable
Product
SteelFusion Core
Related Commands
show storage iscsi, storage iscsi session initial-r2t enable
storage iscsi session initial-r2t enable
Enables the initiator to send unsolicited data to the target without requiring an explicit R2T (ready-to-transfer) PDU from the target.
Syntax
[no] [failover-peer] storage iscsi session initial-r2t enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Usage
Together with the storage iscsi session immediate-data enable command, the storage iscsi session initial-r2t enable command can reduce I/O time by eliminating the need for an additional round trips in small write commands between the initiator the target.
The no command option disables this feature.
Example
Core_01 (config) # storage iscsi session initial-r2t enable
 
Core_02 (config) # failover-peer storage iscsi session initial-r2t enable
Product
SteelFusion Core
Related Commands
show storage iscsi, storage iscsi session immediate-data enable
storage iscsi session mpio
Enables or disables MPIO functionality for the iSCSI initiator configuration.
Syntax
[failover-peer] storage iscsi session mpio {disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
disable
Disables MPIO functionality.
enable
Enables MPIO functionality.
Example
Core_01 (config) # storage iscsi session mpio enable
 
Core_02 (config) # failover-peer storage iscsi session mpio enable
Product
SteelFusion Core
Related Command
storage iscsi session mpio standard-routes
storage iscsi session mpio standard-routes
Enables or disables standard routing for MPIO interfaces.
Syntax
[failover-peer] storage iscsi session mpio standard-routes {disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
disable
Disables standard routing for MPIO connections.
enable
Enables standard routing for MPIO connections.
Usage
If the iSCSI portal is not in the same subnet as the interfaces configured for MPIO, this functionality allows the connection to be established using standard routing.
Example
Core_01 (config) # storage iscsi session mpio standard-routes enable
 
Core_02 (config) # failover-peer storage iscsi session mpio standard-routes enable
Product
SteelFusion Core
Related Command
storage iscsi session mpio
storage iscsi session scan-interval
Specifies the backend scan interval in seconds.
Syntax
[failover-peer] storage iscsi session scan-interval <seconds>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<seconds>
Interval in seconds.
Example
Core_01 (config) # storage iscsi session scan-interval 1200
 
Core_02 (config) # failover-peer storage iscsi session scan-interval 1200
Product
SteelFusion Core
Related Command
storage iscsi session wait-interval
storage iscsi session wait-interval
Specifies the backend wait interval in seconds.
Syntax
[failover-peer] storage iscsi session wait-interval <seconds>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<seconds>
Interval in seconds.
Example
Core_01 (config) # storage iscsi session wait-interval 1200
 
Core_02 (config) # failover-peer storage iscsi session wait-interval 1200
Product
SteelFusion Core
Related Commands
show storage iscsi, storage iscsi session scan-interval
storage iscsi session write-balance enable
Enables the write balance feature.
Syntax
[no] [failover-peer] storage iscsi session write-balance enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Usage
The no command option disables this feature.
Example
Core_01 (config) # storage iscsi session write-balance enable
 
Core_02 (config) # failover-peer storage iscsi session write-balance enable
Product
SteelFusion Core
Related Command
storage lun modify snapshot-config app-consistent
storage lun add block-disk
Adds a block disk LUN for the Core. Note that you can add only discovered LUNs.
Syntax
[failover-peer] storage lun add block-disk serial <serial> alias <alias-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
serial <serial>
Specifies the LUN with its serial number.
alias <alias-name>
Specifies an alias name for the added LUN.
Example
Core_01 (config) # storage lun add block-disk serial 60a98132486e2f374f9f6f795f61565a alias LUN4Edge2
 
Core_02 (config) # failover-peer storage lun add block-disk serial 60a98132486e2f374f9f6f795f61565a alias LUN4Edge2
Product
SteelFusion Core
Related Commands
storage lun add edge-local, storage lun add iscsi
storage lun add edge-local
Adds an edge local LUN for the Core. Note that you can add only discovered LUNs.
Syntax
[failover-peer] storage lun add edge-local edge-id <id> size <megabytes> alias <alias-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
edge-id <id>
Specifies the self-identifier of the Edge to which the LUN is to be added.
size <megabytes>
Specifies the size of the LUN, in megabytes.
The minimum value is 8 MB. The maximum depends on the available space for the blockstore.
alias <alias-name>
Specifies an alias name for the added LUN.
Example
Core_01 (config) # storage lun add edge-local edge-id Edge2 size 256 alias LUN4Edge2
 
Core_02 (config) # failover-peer storage lun add edge-local edge-id Edge2 size 256 alias LUN4Edge2
Product
SteelFusion Core
Related Commands
storage lun add block-disk, storage lun add iscsi
storage lun add iscsi
Adds an iSCSI LUN for the Core.
Syntax
[failover-peer] storage lun add iscsi serial <serial> alias <alias-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
serial <serial>
Specifies the iSCSI serial number at the storage array.
You must use a multiple of 512.
alias <alias-name>
Specifies an alias name for the LUN.
Example
Core_01 (config) # storage lun add iscsi serial hqD6WohWNjx alias LUN4Edge2
Core_02 (config) # failover-peer storage lun add iscsi serial hqD6WohWNjx alias LUN4Edge2
Product
SteelFusion Core
Related Commands
storage lun add block-disk, storage lun add edge-local
storage lun clear-pxy-state
Clears the proxy-backup related state for the specified LUN.
Syntax
[failover-peer] storage lun clear-pxy-state {alias <alias-name> | serial <serial>}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias-name>
Clears the proxy-backup related state for the LUN with the specified alias.
serial <serial>
Clears the proxy-backup related state for the LUN with the specified serial number.
Usage
Core’s proxy backup feature enables backup integration directly from the data center. Core clones the snapshot specified for data protection and mounts the cloned LUN on the proxy server. The backup software then communicates with the proxy server to perform the backup.
Example
Core_01 (config) # storage lun clear-pxy-state serial hqD6WohWNjx
 
Core_02 (config) # failover-peer storage storage lun clear-pxy-state serial hqD6WohWNjx
Product
SteelFusion Core
Related Command
show storage lun
storage lun modify accelerate-iops enable
Enables I/O operations per second acceleration on the LUN.
Syntax
[no] [failover-peer] storage lun modify {alias <alias> | serial <serial>} accelerator-iops enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
Usage
The no command option disables I/O operations per second acceleration.
Example
Core_01 (config) # storage lun modify alias DC-B01 accelerator-iops enable
 
Core_02 (config) # failover-peer storage lun modify alias DC-B01 accelerator-iops enable
Product
SteelFusion Core
Related Command
show storage lun
storage lun modify auth-igroup
Adds or removes an authorized group of iSCSI initiator credentials (igroup) to the LUN specified by its LUN alias.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} auth-igroup {add | remove} <igroup-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
add <igroup-name>
Specifies the authorized group of iSCSI initiator credentials (igroup) to be added the specified LUN.
remove <igroup-name>
Specifies the authorized group of iSCSI initiator credentials (igroup) to be removed from the specified LUN.
Example
Core_01 (config) # storage lun modify alias DC-B01 auth-igroup add igroupName
 
Core_02 (config) # failover-peer storage lun modify alias DC-B01 auth-igroup add igroupName
Product
SteelFusion Core
Related Commands
storage lun modify auth-initiator
storage lun modify auth-initiator
Adds or removes an authorized iSCSI initiator to or from the LUN specified by its alias.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} auth-initiator {add | remove} <initiator-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
add <initiator-name>
Adds the specified, authorized iSCSI initiator to the specified LUN.
remove <initiator-name>
Removes the authorized iSCSI initiator from the specified LUN.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 auth-initiator add iqn.2003-10.com.hoosegow:werdna-initiator
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 auth-initiator add iqn.2003-10.com.hoosegow:werdna-initiator
Product
SteelFusion Core
Related Command
storage lun modify auth-igroup
storage lun modify branch-recovery
Adds or removes a Windows VM to a LUN to enable a branch recovery operation.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} branch-recovery {add-vm <vm-name> [cap <percentage>] | remove-vm <vm-name>}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
add-vm <vm-name>
Adds the specified VM to the branch recovery operation.
cap <percentage>
Specifies the maximum percentage of the disk to prepopulate. For example, if you specify cap <20>, the amount of data pushed per virtual disk would be 20% of the disk size.
remove-vm <vm-name>
Removes the specified VM from the branch recovery operation.
Usage
Currently, the add-vm and remove-vm keywords apply only to VMFS LUNs. If you are using an NTFS LUN, do not provide a value for the VM parameters.
Example
Core_01 (config) # storage lun modify alias alias-vmfs_lun branch-recovery add-vm Win7 cap 10
 
Core_02 (config) # failover-peer storage lun modify alias alias-vmfs branch-recovery
Product
SteelFusion Core
Related Commands
edge modify id branch-recovery clear, show storage lun, storage lun modify branch-recovery schedule
storage lun modify branch-recovery enable
Enables the branch recovery operation on a LUN.
Syntax
[no] [failover-peer] storage lun modify {alias <alias> | serial <serial>} branch-recovery enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
Usage
The no command option disables branch recovery mode.
To configure branch recovery from the CLI:
1. Show the current configuration for a LUN: show storage lun alias alias-vmfs_lun branch-recovery
2. Add a schedule: storage lun modify alias alias-vmfs_lun branch-recovery schedule start-now
3. Add a VM - storage lun modify alias alias-vmfs_lun branch-recovery add-vm Win7
4. Enable branch recovery: storage lun modify alias alias-vmfs_lun branch-recovery enable
5. Monitor progress: show storage lun alias alias-vmfs_lun branch-recovery
Enabled : yes
Status : started
Progress : 3729920 Bytes pushed
Start date : 2014/02/20
Start time : 10:32:59
VMs:
Name : Win7
Status : In-progress
Cap : 10
Example
Core_01 (config) # storage lun modify alias alias-vmfs_lun branch-recovery enable
 
Core_02 (config) # failover-peer storage lun modify alias alias-vmfs_lun branch-recovery enable
Product
SteelFusion Core
Related Commands
edge modify id branch-recovery clear, show storage lun, storage lun modify branch-recovery schedule
storage lun modify branch-recovery restart
Restarts the branch recovery operation after it has completed.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} branch-recovery restart
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
Example
Core_01 (config) # storage lun modify alias alias-vmfs_lun branch-recovery restart
 
Core_02 (config) # failover-peer storage lun modify alias alias-vmfs_lun branch-recovery restart
Product
SteelFusion Core
Related Commands
edge modify id branch-recovery clear, storage lun modify branch-recovery, storage lun modify branch-recovery enable, storage lun modify branch-recovery schedule
storage lun modify branch-recovery schedule
Sets the schedule for when branch recovery runs on the LUN.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} branch-recovery schedule {start-date <date> start-time <time> | start-now}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
start-date <date>
Specifies the start date for the branch-recovery prepopulation schedule.
Use the format yyyy/mm/dd.
start-time <time>
Specifies the start time for the branch-recovery prepopulation schedule. Use the format hh:mm:ss.
start-now
Specifies to start branch recovery immediately.
Example
Core_01 (config) # storage lun modify alias alias-vmfs_lun branch-recovery schedule start-date
2015/03/01 start-time 00:01:00
 
Core_02 (config) # failover-peer storage lun modify alias alias-vmfs_lun branch-recovery schedule start-now
Product
SteelFusion Core
Related Commands
edge modify id branch-recovery clear, show storage lun, storage lun modify branch-recovery, storage lun modify branch-recovery enable, storage lun modify branch-recovery restart
storage lun modify client-type
Modifies the client type (VMware, Windows, or Other) of the configured LUN, specified by its alias.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} client-type <client-type>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
<client-type>
Client type for the LUN:
•  vmware - This LUN is mounted by VMware ESXi and formatted with VMFS.
•  windows - This LUN is mounted by Microsoft Windows and formatted with NTFS.
•  other - All other cases.
Usage
This command is part of a workflow for configuring application-consistent snapshot and data protection settings on the current appliance:
•  Use the storage snapshot br-proxy-host command to configure one or more proxy hosts for the snapshots.
•  Use the storage lun modify client-type command (the current command) to specify the LUN client type as Windows, VMware, or Other.
•  Enable and configure application-consistent snapshots:
–  storage lun modify snapshot-config clear-host
–  storage lun modify snapshot-config app-consistent
•  Enable and configure data protection:
–  storage lun modify snapshot host
–  storage lun modify snapshot-config proxy-backup
•  Enable and configure the snapshot schedule:
–  storage lun modify scheduled-snaps
–  storage lun modify scheduled-snaps add
Example
Core_01 (config) # storage lun modify alias LUN2GO client-type vmware
 
Core_02 (config) # failover-peer storage lun modify alias LUN2GO client-type vmware
Product
SteelFusion Core
Related Command
show storage lun
storage lun modify failover
Enables or disables the failover configuration. This command is enabled by default.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} failover {disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
disable
Disables the failover configuration.
enable
Enables the failover configuration.
Example
Core_01 (config) # storage lun modify alias LUN2GO failover enable
 
Core_02 (config) # failover-peer storage lun modify alias LUN2GO failover enable
Product
SteelFusion Core
Related Command
show storage lun
storage lun modify map edge-id
Maps the LUN to the specified Edge.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} map edge-id <edge-self-identifier>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
<edge-self-identifier>
Self-identifier of the Edge to which the LUN is to be added. Edge identifiers are case sensitive.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 map edge-id Edge2
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 map edge-id Edge2
Product
SteelFusion Core
Related Command
storage iscsi chap add
storage lun modify mpio path
Configures MPIO paths for the LUN.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} mpio path {allow | exclude | preferred} path-id <path-id>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
allow
Allows the specified path to be used in the MPIO configuration.
exclude
Excludes the specified path from being used in the MPIO configuration.
preferred
Configures the specified path as the preferred (principal) path for connections.
path-id <path-id>
Specifies the ID of the path to allow.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 mpio path allow path-id aux
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 mpio path allow path-id aux
Product
SteelFusion Core
Related Command
storage lun modify mpio policy
storage lun modify mpio policy
Configures MPIO paths for the LUN.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} mpio policy {roundrobin | fixedpath}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
roundrobin
Rotates path usage.
fixedpath
Configures a specific path.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 mpio policy roundrobin
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 mpio policy roundrobin
Product
SteelFusion Core
Related Command
storage lun modify mpio path
storage lun modify new-alias
Modifies the alias name for the specified LUN.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} new-alias <new-alias>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
new-alias <new-alias>
Specifies the new alias name.
In addition to alphanumeric characters, you may also use the hyphen (-), underscore (_), and forward slash (/).
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 new-alias LUN4EDGE6
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 new-alias LUN4EDGE6
Product
SteelFusion Core
Related Command
show storage lun
storage lun modify offline
Takes offline the LUN indicated by the alias or serial number.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} offline
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
Usage
This process might take a few minutes to complete.
Before taking the LUN offline with this command, you must stop the Windows server at the Edge using the LUN and unmount the LUN (if the Windows server is running on ESX).
To complete LUN removal, use the storage lun remove command.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 offline
Core_01 (config) # storage lun modify serial hqD6WohWNjx offline
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 offline
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx offline
Product
SteelFusion Core
Related Commands
storage lun modify online, storage lun remove
storage lun modify online
Brings online the LUN indicated by the alias or serial number.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} online
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 online
Core_01 (config) # storage lun modify serial hqD6WohWNjx online
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 online
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx online
Product
SteelFusion Core
Related Command
storage lun modify offline
storage lun modify pinned
Pins or unpins the LUN specified by its alias or serial number.
When a LUN is pinned, the data is reserved and not subject to the normal blockstore eviction policies.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} pinned {disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
disable
Sets the LUN to an unpinned state.
enable
Sets the LUN to a pinned state.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 pinned enable
Core_01 (config) # storage lun modify serial hqD6WohWNjx pinned enable
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 pinned enable
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx pinned enable
Product
SteelFusion Core
Related Commands
show storage lun, storage lun modify prepop
storage lun modify prepop
Enable prepopulation for the LUN specified by its alias or serial number.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} prepop {enable | disable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
enable
Enables prepopulation from the specified LUN.
disable
Disables prepopulation from the specified LUN.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 prepop enable
Core_01 (config) # storage lun modify serial hqD6WohWNjx prepop disable
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 prepop enable
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx prepop disable
Product
SteelFusion Core
Related Commands
show storage lun, storage lun modify prepop schedule add, storage lun modify prepop schedule modify-sched, storage lun modify prepop schedule remove
storage lun modify prepop schedule add
Adds a new prepopulation schedule for the LUN specified by its alias or serial number.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} prepop schedule add sched-name <sched-name> start-week-day <start-week-day> start-time <start-time> stop-week-day <stop-week-day> stop-time <stop-time>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
sched-name <sched-name>
Specifies the name of the prepopulation schedule.
start-week-day <start-week-day>
Specifies the start day for the schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
start-time <start-time>
Specifies the start time for the schedule. Use the format hh:mm:ss.
stop-week-day <stop-week-day>
Specifies the stop day for the schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
stop-time <stop-time>
Specifies the stop time for the schedule. Use the format hh:mm:ss.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 prepop schedule add sched-name WeeklySynch start-week-day mon start-time 00:01:00 stop-week-day mon stop-time 03:01:00
 
Core_01 (config) # storage lun modify serial hqD6WohWNjx prepop schedule add sched-name WeeklySynch start-week-day mon start-time 00:01:00 stop-week-day mon stop-time 03:01:00
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 prepop schedule add sched-name WeeklySynch start-week-day mon start-time 00:01:00 stop-week-day mon stop-time 03:01:00
 
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx prepop schedule add sched-name WeeklySynch start-week-day mon start-time 00:01:00 stop-week-day mon stop-time 03:01:00
Product
SteelFusion Core
Related Commands
show storage lun, storage lun modify prepop, storage lun modify prepop schedule modify-sched, storage lun modify prepop schedule remove
storage lun modify prepop schedule modify-sched
Modifies the prepopulation schedule for the LUN specified by its alias or serial number.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} prepop schedule modify-sched sched-name <sched-name> start-week-day <start-week-day> start-time <start-time> stop-week-day <stop-week-day> stop-time <stop-time>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
sched-name <sched-name>
Specifies the modified name of the existing prepopulation schedule to be modified.
start-week-day
<start-week-day>
Specifies the modified start day for the schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
start-time <start-time>
Specifies the modified start time for the schedule. Use the format hh:mm:ss.
stop-week-day
<stop-week-day>
Specifies the modified stop day for the schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
stop-time <stop-time>
Specifies the modified the stop time for the schedule. Use the format hh:mm:ss.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 prepop schedule modify-sched sched-name WeeklySynch start-week-day mon start-time 00:01:00 stop-week-day mon stop-time 03:01:00
 
Core_01 (config) # storage lun modify serial hqD6WohWNjx prepop schedule modify-sched sched-name WeeklySynch start-week-day mon start-time 00:01:00 stop-week-day mon stop-time 03:01:00
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 prepop schedule modify-sched sched-name WeeklySynch start-week-day mon start-time 00:01:00 stop-week-day mon stop-time 03:01:00
 
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx prepop schedule modify-sched sched-name WeeklySynch start-week-day mon start-time 00:01:00 stop-week-day mon stop-time 03:01:00
Product
SteelFusion Core
Related Commands
show storage lun, storage lun modify prepop, storage lun modify prepop schedule add, storage lun modify prepop schedule remove
storage lun modify prepop schedule remove
Removes the prepopulation schedule from the specified LUN.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} prepop schedule remove sched-name <sched-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
sched-name <sched-name>
Specifies the name of the prepopulation schedule to be removed.
Example
Core_01 (config) # storage lun modify alias LUN2 prepop schedule remove sched-name MondaySynch
 
Core_01 (config) # storage lun modify serial hqD6WohWNjx prepop schedule remove sched-name MondaySynch
 
Core_02 (config) # failover-peer storage lun modify alias LUN2 prepop schedule remove sched-name MondaySynch
 
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx prepop schedule remove sched-name MondaySynch
Product
SteelFusion Core
Related Commands
show storage lun, storage lun modify prepop, storage lun modify prepop schedule add, storage lun modify prepop schedule modify-sched
storage lun modify prepop smart
Enables smart prepopulation on the LUN specified by its alias or serial number.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} prepop smart {disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
disable
Disables prepopulation on the specified LUN.
enable
Enables prepopulation on the specified LUN.
Usage
You need to use smart prepopulation only for NTFS or VMFS LUNs. For other LUNs, you need to disable it using the disable option in this command if it has been enabled.
Prepopulation can be enabled only if the LUN is pinned. For details, see the storage lun modify pinned command.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 prepop smart enable
Core_01 (config) # storage lun modify serial hqD6WohWNjx prepop smart enable
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 prepop smart enable
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx prepop smart enable
Product
SteelFusion Core
Related Commands
show storage lun, storage lun modify prepop, storage lun modify prepop schedule add, storage lun modify prepop schedule modify-sched
storage lun modify prepop start-now
Begins the prepopulation process for the specified LUN configuration, starting from the current time.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} prepop start-now
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
Example
Core_01 (config) # storage lun modify alias LUN2 prepop start-now
Core_01 (config) # storage lun modify serial hqD6WohWNjx prepop start-now
 
Core_02 (config) # failover-peer storage lun modify alias LUN2 prepop start-now
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx prepop start-now
Product
SteelFusion Core
Related Commands
show storage lun, storage lun modify prepop, storage lun modify prepop schedule add, storage lun modify prepop schedule modify-sched, storage lun modify prepop smart
storage lun modify pri-snap
Configures private snapshot settings for the LUN specified by its alias or serial numbers.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} pri-snap {max <count> | static-name {enable <pri-snap-name> | disable}]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
max <count>
Specifies the maximum number of private snapshots to be taken of the specified LUN.
static-name
Specifies a private snapshot static name to be prepended to the filenames of snapshots taken of this LUN.
enable <pri-snap-name>
Enables the private snapshot static name from the LUN snapshot filename.
disable
Disables the private snapshot static name from the LUN snapshot filename.
Usage
You set either the maximum number of private snapshots that can be retained at any time, or enable and set a static value to be prepended to the private snapshot filenames.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 pri-snap max 14
Core_01 (config) # storage lun modify serial hqD6WohWNjx pri-snap static-name disable
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 pri-snap max 14
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx pri-snap static-name disable
Product
SteelFusion Core
Related Commands
show storage lun, storage lun modify scheduled-snaps, storage lun modify scheduled-snaps add
storage lun modify scheduled-snaps
Enables or disables the scheduled snapshots feature for the specified LUN.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} scheduled-snaps {enable | disable} [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
enable
Enables the scheduled snapshots feature for the specified LUN.
disable
Disables the scheduled snapshots feature for the specified LUN.
force
Forces the enabling or disabling of the scheduled snapshots feature if the LUN is online.
We recommend that you take the LUN offline before enabling or disabling the scheduled snapshots feature.
Usage
This command is part of a workflow for configuring application-consistent snapshot and data protection settings on the current appliance:
•  Use the storage snapshot br-proxy-host command to configure one or more proxy hosts for the snapshots.
•  Use the storage lun modify client-type command to specify the LUN client type as Windows or VMware.
•  Enable and configure application-consistent snapshots:
–  storage lun modify snapshot-config clear-host
–  storage lun modify snapshot-config app-consistent
•  Enable and configure data protection:
–  storage lun modify snapshot host
–  storage lun modify snapshot-config proxy-backup
•  Enable and configure the snapshot schedule:
–  storage lun modify scheduled-snaps (the current command)
–  storage lun modify scheduled-snaps add
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 scheduled-snaps enable
Core_01 (config) # storage lun modify serial hqD6WohWNjx scheduled-snaps disable
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 scheduled-snaps enable
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx scheduled-snaps disable
Product
SteelFusion Core
Related Command
storage lun modify scheduled-snaps add
storage lun modify scheduled-snaps add
Adds the specified snapshot policy to the configuration of the specified LUN.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} scheduled-snaps add <policy-name> [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
<policy-name>
Snapshot policy to be added to the LUN.
You define snapshot policies using the storage snapshot policy add command.
force
Forces the invocation of the policy if the LUN is online.
We recommend that you take the LUN offline before making changes to snapshot configurations.
Usage
A single snapshot policy can be assigned to more than one LUN, but each LUN can be associated with only a single snapshot policy.
This command is part of a workflow for configuring application-consistent snapshot and data protection settings on the current appliance:
•  Use the storage snapshot br-proxy-host command to configure one or more proxy hosts for the snapshots.
•  Use the storage lun modify client-type command to specify the LUN client type as Windows or VMware.
•  Enable and configure application-consistent snapshots:
–  storage lun modify snapshot-config clear-host
–  storage lun modify snapshot-config app-consistent
•  Enable and configure data protection:
–  storage lun modify snapshot host
–  storage lun modify snapshot-config proxy-backup
•  Enable and configure the snapshot schedule:
–  storage lun modify scheduled-snaps
–  storage lun modify scheduled-snaps add (the current command)
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 scheduled-snaps add company1policy
 
Core_01 (config) # storage lun modify serial hqD6WohWNjx scheduled-snaps add company1policy
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 scheduled-snaps add company1policy
 
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx scheduled-snaps add company1policy
Product
SteelFusion Core
Related Command
storage lun modify scheduled-snaps remove
storage lun modify scheduled-snaps remove
Removes any currently associated snapshot policy from the configuration of the specified LUN.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} scheduled-snaps remove [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
force
Forces the disassociation of the policy if the LUN is online.
We recommend that you take the LUN offline before making changes to snapshot configurations.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 scheduled-snaps remove
 
Core_01 (config) # storage lun modify serial hqD6WohWNjx scheduled-snaps remove
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 scheduled-snaps remove
 
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx scheduled-snaps remove
Product
SteelFusion Core
Related Commands
storage lun modify scheduled-snaps, storage lun modify scheduled-snaps add
storage lun modify scsi-res
Enables or disables the specified LUN using SCSI reservations.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} scsi-res {disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
disable
Disables the LUN using SCSI reservations.
enable
Enables the LUN using SCSI reservations.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 scsi-res disable
Core_01 (config) # storage lun modify serial hqD6WohWNjx scsi-res enable
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 scsi-res disable
 
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx scsi-res enable
Product
SteelFusion Core
Related Command
storage lun modify-all scsi-res
storage lun modify snapshot-config clear-host
Clears the snapshot host configuration from the configuration of the specified LUN.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} snapshot-config clear-host
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
Usage
This command is part of a workflow for configuring application-consistent snapshot and data protection settings on the current appliance:
•  Use the storage snapshot br-proxy-host command to configure one or more proxy hosts for the snapshots.
•  Use the storage lun modify client-type command to specify the LUN client type as Windows or VMware.
•  Enable and configure application-consistent snapshots:
–  storage lun modify snapshot-config clear-host (the current command)
–  storage lun modify snapshot-config app-consistent
•  Enable and configure data protection:
–  storage lun modify snapshot host
–  storage lun modify snapshot-config proxy-backup
•  Enable and configure the snapshot schedule:
–  storage lun modify scheduled-snaps
–  storage lun modify scheduled-snaps add
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 snapshot-config clear-host
 
Core_01 (config) # storage lun modify serial hqD6WohWNjx snapshot-config clear-host
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 snapshot-config clear-host
 
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx snapshot-config clear-host
Product
SteelFusion Core
Related Command
storage lun modify snapshot-config app-consistent
storage lun modify snapshot-config app-consistent
Configures application-consistent snapshots for the current appliance.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} snapshot-config app-consistent {clear | disable | enable | vmware} [host-info <host-info>] [fail-on-acs-err enable] [datacenter <datacenter>] [include-vms <include-vm-regex>] [exclude-vms <exclude-regex>] [script-timeout <seconds>] [quiesce-guest {enable | disable}]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
clear
Clears the application-consistent snapshot configuration for the current appliance.
disable
Disables application-consistent snapshots for the current appliance.
enable
Enables application-consistent snapshots for the current appliance.
vmware
Modifies VMware-specific parameters for the application-consistent snapshots configuration.
Specify any combination of the following parameters:
•  host-info <host-info> - Specifies the host information for VMware.
•  fail-on-acs-error enable - Causes the snapshot operation to fail if the Edge is unable to take a snapshot with the VM being quiesced.
•  datacenter <datacenter> - Specifies a data center for VMware-based application-consistent snapshots.
•  include-vms <include-regex> - Specifies by regular expression the names of the VMs to be included.
•  exclude-vms <exclude-regex> - Specifies by regular expression the names of the VMs to be excluded.
•  script-timeout <seconds> - Specifies the time-out period for the application-consistent snapshot operation.
Alternatively, specify any combination of the following parameters:
•  quiesce-guest {enable | disable} - Enables or disables quiescing VMs in the application-consistent snapshots. You cannot combine this parameter with any other VMware-specific parameters.
Usage
This command is part of a workflow for configuring application-consistent snapshot and data protection settings on the current appliance:
•  Use the storage snapshot br-proxy-host command to configure one or more proxy hosts for the snapshots.
•  Use the storage lun modify client-type command to specify the LUN client type as Windows or VMware.
•  Enable and configure application-consistent snapshots:
–  storage lun modify snapshot-config clear-host
–  storage lun modify snapshot-config app-consistent (the current command)
•  Enable and configure data protection:
–  storage lun modify snapshot host
–  storage lun modify snapshot-config proxy-backup
•  Enable and configure the snapshot schedule:
–  storage lun modify scheduled-snaps
–  storage lun modify scheduled-snaps add
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 snapshot-config app-consistent quiesce-guest enable
 
Core_01 (config) # storage lun modify serial hqD6Wo/hWNjx snapshot-config app-consistent quiesce-guest disable
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 snapshot-config app-consistent quiesce-guest enable
 
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx snapshot-config app-consistent quiesce-guest disable
Product
SteelFusion Core
Related Command
storage lun modify snapshot-config clear-host
storage lun modify snapshot-config proxy-backup
Configures data protection for snapshots for the failover peer of the current appliance.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} snapshot-config proxy-backup {clear | disable | enable | vmware {[datacenter <datacenter>] [exclude-hosts <exclude-host-regex>] [exclude-vms <exclude-regex>] [host-info <host-info>] [include-hosts <include-host-regex>] [include-vms <include-regex>] [script-timeout <seconds>] [snapshot-type <snapshot-type>]} | windows {[host-info <host-info>] [proxy-group <proxy-group>] [script-timeout <seconds>] [snapshot-type <snapshot-type>]}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
clear
Clears the proxy backup host configuration.
disable
Disables the proxy backup for snapshots.
enable
Enables the proxy backup for snapshots.
vmware
Modifies VMware-specific parameters for the proxy backup configuration.
Specify any combination of the following parameters:
•  datacenter <datacenter> - Specifies a data center for VMware-based application-consistent snapshots.
•  exclude-hosts <exclude-host-regex> - Specifies by regular expression the ESXi hosts to be excluded.
•  exclude-vms <exclude-regex> - Specifies by regular expression the names of the VMs to be excluded.
•  host-info <host-info> - Specifies the host information for the proxy backup.
•  include-hosts <include-host-regex> - Specifies by regular expression the ESXi hosts to be included.
•  include-vms <include-regex> - Specifies by regular expression the names of the VMs to be included.
•  script-timeout <seconds> - Specifies the time-out period for the backup operation on the proxy server.
•  snapshot-type <snapshot-type> - Specifies the type of backup: daily, hourly, or weekly.
windows
Modifies Windows-specific parameters for the proxy backup configuration.
Specify any combination of the following parameters:
•  host-info <host-info> - Specifies the host information for the proxy backup.
•  proxy-group <proxy-group> - Specifies the storage group/Initiator group for the proxy (backup) server.
•  script-timeout <seconds> - Specifies the time-out period for the backup operation on the proxy server.
•  snapshot-type <snapshot-type> - Specifies the type of backup: daily, hourly, or weekly.
Usage
This command is part of a workflow for configuring application-consistent snapshot and data protection settings on the current appliance:
•  Use the storage snapshot br-proxy-host command to configure one or more proxy hosts for the snapshots.
•  Use the storage lun modify client-type command to specify the LUN client type as Windows or VMware.
•  Enable and configure application-consistent snapshots:
–  storage lun modify snapshot-config clear-host
–  storage lun modify snapshot-config app-consistent
•  Enable and configure data protection:
–  storage lun modify snapshot host
–  storage lun modify snapshot-config proxy-backup (the current command)
•  Enable and configure the snapshot schedule:
–  storage lun modify scheduled-snaps
–  storage lun modify scheduled-snaps add
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 snapshot-config proxy-backup datacenter gandolfo
 
Core_01 (config) # storage lun modify serial hqD6WohWNjx snapshot-config proxy-backup datacenter gandolfo
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 snapshot-config proxy-backup datacenter gandolfo
 
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx snapshot-config proxy-backup datacenter gandolfo
Product
SteelFusion Core
Related Commands
storage lun modify scheduled-snaps, storage lun modify scheduled-snaps add
storage lun modify snapshot-config handoff enable
Enables the handoff host feature.
Syntax
[no] [failover-peer] storage lun modify {alias <alias> | serial <serial>} snapshot-config handoff enable [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
force
Forces the change in handoff configuration type.
Example
Core_01 (config) # storage lun modify serial P3KRP4qfq5iS snapshot-config handoff enable
 
Core_01 (config) # storage lun modify alias lun1 snapshot-config handoff enable
 
Core_02 (config) # failover-peer storage lun modify serial P3KRP4qfq5iS snapshot-config handoff enable
 
Core_02 (config) # failover-peer storage lun modify alias lun1 snapshot-config handoff enable
Product
SteelFusion Core
Related Command
storage snapshot handoff-host
storage lun modify snapshot host
Creates the hostname of the storage array used as the snapshot host.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} snapshot host <hostname>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
<hostname>
Name of the storage array.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 snapshot host LUN4Edge2
 
Core_01 (config) # storage lun modify serial hqD6WohWNjx snapshot host LUNEdge2
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 snapshot host LUN4Edge2
 
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx snapshot host LUNEdge2
Product
SteelFusion Core
Related Command
storage lun modify snapshot-config clear-host
storage lun modify storage-group
Specifies the storage group applicable to LUNs in an EMC storage array.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} storage-group <storage-group>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
<storage-group>
Name of the storage group.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 storage-group central
Core_01 (config) # storage lun modify serial hqD6WohWNjx storage-group central
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 storage-group central
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx storage-group central
Product
SteelFusion Core
Related Command
show storage lun
storage lun modify unmap
Unmaps the specified LUN from the Core.
Syntax
[failover-peer] storage lun modify {alias <alias> | serial <serial>} unmap [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the LUN to be modified by its alias.
serial <serial>
Specifies the LUN to be modified by its serial number.
force
Forces the unmapping if the LUN is online.
We recommend that you take the LUN offline before unmapping it. See storage lun modify offline.
Example
Core_01 (config) # storage lun modify alias LUN4Edge2 unmap
Core_01 (config) # storage lun modify serial hqD6WohWNjx unmap
 
Core_02 (config) # failover-peer storage lun modify alias LUN4Edge2 unmap
Core_02 (config) # failover-peer storage lun modify serial hqD6WohWNjx unmap
Product
SteelFusion Core
Related Command
storage lun modify offline
storage lun modify-all scsi-res
Enables or disables SCSI reservations for all configured LUNs.
Syntax
[failover-peer] storage lun modify-all scsi-res {disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
disable
Disables SCSI reservations.
enable
Enables SCSI reservations.
Example
Core_01 (config) # storage lun modify-all scsi-res enable
 
Core_02 (config) # failover-peer storage lun modify-all scsi-res enable
Product
SteelFusion Core
Related Command
storage lun modify scsi-res
storage lun remove
Removes the specified LUN from the Core configuration.
Syntax
[failover-peer] storage lun remove {alias <alias> | serial <serial>} [force]
Parameters.
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the alias of the LUN to be removed.
serial <serial>
Specifies the iSCSI serial number of the LUN to be removed.
force
Forces the removal if the LUN is online.
Usage
Before removing the LUN from the Core configuration, you must take it offline using storage lun modify offline.
Example
Core_01 (config) # storage lun remove alias LUN4Edge2 force
 
Core_02 (config) # failover-peer storage lun remove alias LUN4Edge2 force
Product
SteelFusion Core
Related Command
storage lun modify offline
storage lun resize
Resizes the specified LUN in the Core configuration.
Syntax
[failover-peer] storage lun resize {alias <alias> | serial <serial>}
Parameters.
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the alias of the LUN to be resized.
serial <serial>
Specifies the iSCSI serial number of the LUN to be resized.
Usage
Before resizing the LUN from the Core configuration, you must take it offline using storage lun modify offline.
Example
Core_01 (config) # storage lun resize alias LUN4Edge2
 
Core_02 (config) # failover-peer storage lun resize alias LUN4Edge2
Product
SteelFusion Core
Related Command
storage lun modify offline
storage lun setup-pxy-state
Creates a cloned LUN and mounts it on the proxy server.
Syntax
[failover-peer] storage lun setup-pxy-state {alias <alias> | serial <serial>} [snapshot-type <type>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
alias <alias>
Specifies the alias of the LUN to be cloned.
serial <serial>
Specifies the iSCSI serial number of the LUN to be cloned.
snapshot-type <type>
Specifies the type of snapshot to be mounted on the proxy host.
Example
Core_01 (config) # storage lun setup-pxy-state alias LUN4Edge2 force
 
Core_02 (config) # failover-peer storage lun setup-pxy-state alias LUN4Edge2
Product
SteelFusion Core
storage snapshot br-proxy-host
Adds or modifies the hosts used for configuring application-consistent snapshots or proxy backup.
Syntax
[failover-peer] storage snapshot br-proxy-host {add | modify} host <hostname> username <username> password <password> host-type <host-type>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
add
Adds the host.
modify
Modifies the host.
<hostname>
Name of the host you want to add or modify.
username <username>
Specifies the username for the host. If you are configuring a Windows host, use the format WindowsDomain\Username.
password <password>
Specifies the password for the host.
host-type <host-type>
Specifies the host type:
•  vmware-branch - Specifies the VMware host at the branch.
•  vmware-vcenter - Specifies the VMware vCenter.
•  windows-proxy - Specifies the Windows host (backup proxy) at the data center.
•  vmware-proxy - Specifies the VMware host (backup proxy) at the data center.
Examples
Core01 (config) # storage snapshot br-proxy-host modify host sf-vva14 username WindowsDomain\John.Smith password HostPwd1 host-type windows-proxy
 
Core02 (config) # failover-peer storage snapshot br-proxy-host add host sf-vva14 username John.Smith password HostPwd1 host-type vmware-vcenter
Product
SteelFusion Core
Related Command
storage snapshot br-proxy-host remove host
storage snapshot br-proxy-host remove host
Removes the host used for configuring application-consistent snapshots or proxy backup for a LUN.
Syntax
[failover-peer] storage snapshot br-proxy-host remove host <hostname>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Name of the host you want to remove.
Example
Core01 (config) # storage snapshot br-proxy-host remove host sf-vva14
Product
SteelFusion Core
Related Command
show storage snapshot, storage snapshot br-proxy-host
storage snapshot handoff-host
Adds or modifies the handoff host used for managing LUN snapshots.
Syntax
[failover-peer] storage snapshot handoff-host {add | modify} host <hostname> [username <username> password <password>] script-path <script-path> script-args <script-args>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
add
Adds the handoff host.
modify
Modifies the handoff host.
host <hostname>
Specifies the hostname of the host.
username <username>
Specifies a username for the snapshot credential.
password <password>
Specifies a password for the snapshot credential.
script-path <script-path>
Specifies the paths to both the executable and the script on the handoff host.
In both cases, you must provide the absolute path and enclose it in quotation marks. For example:
“C:\Python27\python.exe C:\handoff_scripts\sample_script.py.txt”
script-args <script-args>
Specifies the arguments that conform to your script to configure the snapshot settings. Enclose the arguments in quotation marks.
Usage
Core can interoperate with any iSCSI-compliant storage array, but support for application-consistent snapshots is limited to storage arrays from qualified vendors (Dell EqualLogic, EMC VNX, NetApp, HP 3PAR, IBM Storwize v7000, IBM XIV/Spectrum Accelerate, EMC Unity, Nimble, and Zadara). The handoff host feature enables you to configure external hosts and scripts to take the snapshots on other, nonqualified storage arrays.
Example
Core_01 (config) # storage snapshot handoff-host add chief-cs123.lab.com username testuser password testpwd script-path "c:\python\python.exe c:\handoff_scripts\sample_script.py" script-args "-option1 value1"
 
Core_02 (config) # failover-peer storage snapshot handoff-host add chief-cs123.lab.com username testuser password testpwd script-path "c:\python\python.exe c:\handoff_scripts\sample_script.py" script-args "-option1 value1"
Product
SteelFusion Core
Related Commands
show storage snapshot, storage snapshot handoff-host remove host
storage snapshot handoff-host remove host
Removes a snapshot host from the list of hosts configured for LUN snapshots.
Syntax
[failover-peer] storage snapshot handoff-host remove host <hostname>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Name of the host.
Example
Core_01 (config) # storage snapshot handoff-host remove host sf-vva14
Product
SteelFusion Core
Related Command
storage snapshot handoff-host
storage snapshot policy add
Adds a new snapshot policy to the configuration of the current appliance.
Syntax
[failover-peer] storage snapshot policy add <policy-name>
Parameters
failover-peer
Performs the command on an unavailable failover peer of the current appliance. The changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Name of the new policy.
Example
Core_01 (config) # storage snapshot policy add Weekly20150303
 
Core_02 (config) # failover-peer storage snapshot policy add Weekly20150303
Product
SteelFusion Core
Related Commands
storage snapshot policy remove, storage snapshot policy modify add-daily, storage snapshot policy modify add-hourly, storage snapshot policy modify add-weekly, storage snapshot policy rename
storage snapshot policy modify add-daily
Adds a daily snapshot schedule to the specified snapshot policy.
Syntax
[failover-peer] storage snapshot policy modify <policy-name> add-daily hour <schedule-hour> {days <schedule-days> | everyday} [max-snap-count <max-count>] [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Name of the policy to be modified.
hour <schedule-hour>
Specifies the time for the snapshot to be taken. Use the 24-hour clock format. For example, to specify 4:00 P.M., enter 16.
days <schedule-days>
Specifies the day of the week for the snapshot to be taken. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
everyday
Specifies daily snapshots.
max-snap-count <max-count>
Specifies the maximum number of weekly snapshots to be retained.
force
Forces the change (in case the policy is currently assigned).
Example
Core_01 (config) # storage snapshot policy modify DailyLUN17 add-daily hour 14 everyday
 
Core_02 (config) # failover-peer storage snapshot policy modify DailyLUN17 add-daily hour 14 everyday
Product
SteelFusion Core
Related Commands
storage snapshot policy add, storage snapshot policy modify add-hourly, storage snapshot policy modify add-weekly, storage snapshot policy rename
storage snapshot policy modify add-hourly
Adds an hourly snapshot schedule to the specified snapshot policy.
Syntax
[failover-peer] storage snapshot policy modify <policy-name> add-hourly {everyhour | hours <schedule-hours>} [max-snap-count <max-count>] [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Specifies the name of the policy to be modified.
everyhour
Specifies hourly snapshots.
hours <schedule-hours>
Specifies the time for the snapshot to be taken. To specify multiple times, add a comma after each time. Use the 24-hour clock format. For example, to specify 4:00 P.M., enter 16.
max-snap-count <max-count>
Specifies the maximum number of hourly snapshots to be retained.
force
Forces the change (in case the policy is currently assigned).
Example
Core_01 (config) # storage snapshot policy modify DailyLUN17 add-hourly everyhour
 
Core_02 (config) # failover-peer storage snapshot policy modify DailyLUN17 add-hourly everyhour
Product
SteelFusion Core
Related Commands
storage snapshot policy add, storage snapshot policy modify add-weekly, storage snapshot policy rename, storage snapshot policy remove
storage snapshot policy modify add-weekly
Adds a weekly snapshot schedule to the specified snapshot policy.
Syntax
[failover-peer] storage snapshot policy modify <policy-name> add-weekly hour <schedule-hour> day <schedule-day> [max-snap-count <max-count>] [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Name of the policy to be modified.
hour <schedule-hour>
Specifies the time for the snapshot to be taken. Use the 24-hour clock format. For example, to specify 4:00 P.M., enter 16.
day <schedule-day>
Specifies the day of the week for the snapshot to be taken. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
max-snap-count <max-count>
Specifies the maximum number of weekly snapshots to be retained.
force
Forces the change (in case the policy is currently assigned).
Example
Core_01 (config) # storage snapshot policy modify WeeklyLUN17 add-weekly 10:00:00 day mon
Core_02 (config) # failover-peer storage snapshot policy modify WeeklyLUN17 add-weekly hour 10:00:00 day mon
Product
SteelFusion Core
Related Commands
storage snapshot policy add, storage snapshot policy remove, storage snapshot policy rename storage snapshot policy modify add-hourly, storage snapshot policy rename
storage snapshot policy remove
Removes the specified snapshot policy from the configuration of the current appliance.
Syntax
[failover-peer] storage snapshot policy remove <policy-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Name of the policy to be removed.
Example
Core_01 (config) # storage snapshot policy remove Weekly20150303
 
Core_02 (config) # failover-peer storage snapshot policy remove Weekly20150303
Product
SteelFusion Core
Related Commands
storage snapshot policy add, storage snapshot policy remove, storage snapshot policy rename storage snapshot policy modify add-hourly, storage snapshot policy modify add-daily, storage snapshot policy modify add-weekly
storage snapshot policy rename
Adds a new snapshot policy to the configuration of the current appliance.
Syntax
[failover-peer] storage snapshot policy rename <policy-name> new-name <new-policy-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Name of the policy to be modified.
new-name <new-policy-name>
Specifies the new policy name.
Example
Core_01 (config) # storage snapshot policy rename Weekly20130606 new-name WeeklyLUNJacob
 
Core_02 (config) # failover-peer storage snapshot policy rename Weekly20130606 new-name WeeklyLUNJacob
Product
SteelFusion Core
Related Commands
storage snapshot policy modify add-daily, storage snapshot policy modify add-hourly, storage snapshot policy modify add-weekly storage snapshot policy remove
storage snapshot skip_vm_reg_op enable
When using backup software packages such as Veeam, Core will modify the cleanup operations it performs between successive snapshots. To ensure that incremental changes between these snapshots are captured, the data protection operation will skip unregistering VMs on the Proxy ESX server, but still perform other cleanup operations such as unmounting the ESXi datastore and detaching the cloned LUNs.
Syntax
[no] [failover-peer] storage snapshot skip_vm_reg_op enable
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
Usage
Please use caution when using this command.
The no command option disables the feature.
This command applies to all LUNs on the Core.
Example
Core_01 (config) # failover-peer storage snapshot skip_vm_reg_op enable
Product
SteelFusion Core
storage snapshot storage-array
Adds or modifies the storage arrays that can be used for snapshots.
Syntax
[failover-peer] storage snapshot storage-array {add | modify} host <hostname> type <type> username <username> password <password> [port <port-number>] [protocol <protocol>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
add
Adds a new storage array.
modify
Modifies an existing storage array.
host <hostname>
Specifies the name of the host.
type <type>
Storage array type:
•  EMC-VNX - EMC VNX
•  Dell-Equallogic - Dell EqualLogic
•  IBM-V7000 - IBM V7000
•  HP3PAR - HP3PAR
•  IBM-XIV-Spectrum-Accelerate - IBM XIV/Spectrum Accelerate
•  EMC-Unity - EMC Unity
•  NetApp - NetApp
•  Nimble
•  Zadara
username <username>
Specifies the username for the host.
password <password>
Specifies the password for the host.
port <port-number>
For NetApp storage arrays, specifies the port number.
protocol <protocol>
For NetApp storage arrays, specifies the protocol type.
Example
Core_01 (config) # storage snapshot storage-array add host sf-vva14 type NetApp username admin password 1234
 
Core_02 (config) # failover-peer storage snapshot storage-array add host 1.1.3.4 type NetApp username admin password 1234
Product
SteelFusion Core
Related Command
show storage snapshot, storage snapshot storage-array remove host
storage snapshot storage-array modify host redundant-paths add rp-host
Configures redundant paths to the specified snapshot host in case of failure.
Syntax
[failover-peer] storage snapshot storage-array modify host <hostname> redundant-paths add rp-host <rp-host> [rp-port <port>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the storage array.
<rp-host>
Redundant hostname to add for the chosen storage array.
rp-port <port-number>
Specifies the redundant port number for the chosen storage array.
Example
amnesiac (config) # storage snapshot storage-array modify host sf-vva14 redundant-paths add rp-host sf-vva20 rp-port 90
Product
SteelFusion Core
Related Commands
show edge, storage iscsi data-digest
storage snapshot storage-array modify host redundant-paths remove rp-host
Removes the specified redundant path for the snapshot host.
Syntax
[failover-peer] storage snapshot storage-array modify host <hostname> redundant-paths remove rp-host <rp-host>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the storage array.
<rp-host>
Redundant hostname to remove for the chosen storage array.
Example
amnesiac (config) # storage snapshot storage-array modify host sf-vva14 redundant-paths remove rp-host sf-vva20
Product
SteelFusion Core
Related Commands
show edge, storage iscsi data-digest
storage snapshot storage-array remove host
Removes a snapshot host.
Syntax
[failover-peer] storage snapshot storage-array remove host <hostname>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the storage array.
Example
amnesiac (config) # storage snapshot storage-array remove host sf-vva14
Product
SteelFusion Core
Related Commands
show edge, storage iscsi data-digest
storage snapshot test handoff delete serial
Test deletes a LUN snapshot without changing the current configuration.
Syntax
[failover-peer] storage snapshot test handoff delete serial <lun-serial> snap-name <snap-name> [host <hostname>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
snap-name <snap-name>
Specifies the snapshot by name.
host <hostname>
Specifies a handoff host.
Usage
Use this command for handoff host configurations only. All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test handoff delete serial ORIG12P5D snap-name snapshot1 host win_handoff_host
 
Core_02 (config) # failover-peer storage snapshot test handoff delete serial ORIG12P5D snap-name snapshot1 host win_handoff_host
Product
SteelFusion Core
Related Commands
storage snapshot handoff-host, storage snapshot test handoff take serial
storage snapshot test handoff hello serial
Tests the connection to the storage array.
Syntax
[failover-peer] storage snapshot test handoff hello serial <lun-serial> [host <hostname>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
host <hostname>
Specifies a handoff host.
Usage
Use this command for handoff host configurations only. All test commands enable you to test different snapshot configurations without affecting your configuration. This command does not change the configuration.
Example
Core_01 (config) # storage snapshot test handoff hello serial ORIG12P5D host win_handoff_host
 
Core_02 (config) # failover-peer storage snapshot test handoff hello serial ORIG12P5D host win_handoff_host
Product
SteelFusion Core
Related Commands
storage snapshot handoff-host, storage snapshot test handoff take serial
storage snapshot test handoff take serial
Test creates a LUN snapshot without changing the current configuration. For handoff host configurations only.
Syntax
[failover-peer] storage snapshot test handoff take serial <lun-serial> [snap-name <snap-name>] [host <hostname>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
snap-name <snap-name>
Specifies the name for the snapshot to be test created.
host <hostname>
Specifies the handoff host.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test handoff take serial ORIG12P5D snap-name snapshot1 host win_handoff_host
 
Core_02 (config) # failover-peer storage snapshot test handoff take serial ORIG12P5D snap-name snapshot1 host win_handoff_host
Product
SteelFusion Core
Related Commands
storage snapshot handoff-host, storage snapshot test handoff delete serial
storage snapshot test integrated delete serial
Test deletes a LUN snapshot without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated delete serial <lun-serial> snap-name <snap-name> [group <group-name>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
snap-name <snap-name>
Specifies the name of the snapshot.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated delete host kabar-vva35 serial ORIG12P5D snap-name snapshot1 private
Core_02 (config) # failover-peer storage snapshot test integrated delete host kabar-vva35 serial ORIG12P5D snap-name snapshot1 private
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete type, storage snapshot test integrated expose serial, storage snapshot test integrated expose type, storage snapshot test integrated take serial, storage snapshot test integrated take type, storage snapshot test integrated un-expose serial, storage snapshot test integrated un-expose type
storage snapshot test integrated delete type
Test deletes a LUN snapshot, specified by array type, without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated delete type <array-type> host <hostname> serial <lun-serial> snap-name <snap-name> user <username> password <password> protocol <protocol> [group <group-name>] [use-ssl]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array-type>
Storage array type:
•  emc_vnx - EMC VNX
•  dell_equallogic - Dell EqualLogic
•  netapp - NetApp
•  ibm_v7000 - IBM V7000
•  hp3par - HP3PAR
•  ibm_xiv - IBM XIV/Spectrum Accelerate
•  EMC-Unity
•  Nimble
•  Zadara
host <hostname>
Specifies the IP address or hostname of the storage array.
serial <lun-serial>
Specifies the snapshot LUN by the LUN serial number.
snap-name <snap-name>
Specifies the snapshot by name.
user <username>
Specifies a username for the snapshot credential.
password <password>
Specifies a password for the snapshot credential.
protocol <protocol>
For Zadara storage arrays, specifies the communication protocol to use with the array.
•  HTTP - Specifies Hyper Text Transport Protocol (port 80).
•  HTTPS - Specifies Hyper Text Transport Protocol Secure (port 443).
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated delete type emc_vnx host kabar-vva35 serial ORIG12P5D snap-name snapshot1 user admincentral password adminpass367
 
Core_02 (config) # failover-peer storage snapshot test integrated delete type emc_vnx host kabar-vva35 serial ORIG12P5D snap-name snapshot1 user admincentral password adminpass367
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete serial, storage snapshot test integrated expose serial, storage snapshot test integrated expose type, storage snapshot test integrated take serial, storage snapshot test integrated take type, storage snapshot test integrated un-expose serial, storage snapshot test integrated un-expose type
storage snapshot test integrated expose serial
Test creates a clone LUN out of a snapshot and exposes it to initiators without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated expose serial <lun-serial> snap-name <snap-name> [group <group-name>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
snap-name <snap-name>
Specifies the name of the snapshot.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated expose serial CLONE12P5D snap-name snapshot1
 
Core_02 (config) # failover-peer storage snapshot test integrated expose serial CLONE12P5D snap-name snapshot1
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete serial, storage snapshot test integrated delete type, storage snapshot test integrated expose type, storage snapshot test integrated take serial, storage snapshot test integrated take type, storage snapshot test integrated un-expose serial, storage snapshot test integrated un-expose type
storage snapshot test integrated expose type
Test creates a clone LUN out of a snapshot, specified by array type, without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated expose type <array-type> host <hostname> serial <lun-serial> snap-name <snap-name> user <username> password <password> protocol <protocol> [group <group-name>] [use-ssl]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array-type>
Storage array type:
•  emc_vnx - EMC VNX
•  dell_equallogic - Dell EqualLogic
•  netapp - NetApp
•  ibm_v7000 - IBM V7000
•  hp3par - HP3PAR
•  ibm_xiv - IBM XIV/Spectrum Accelerate
•  EMC-Unity
•  Nimble
•  Zadara
host <hostname>
Specifies the IP address or hostname of the storage array.
serial <lun-serial>
Specifies the snapshot LUN by the LUN serial number.
snap-name <snap-name>
Specifies the name of the snapshot.
user <username>
Specifies a username for the snapshot credential.
password <password>
Specifies a password for the snapshot credential.
protocol <protocol>
For Zadara storage arrays, specifies the communication protocol to use with the array.
•  HTTP - Specifies Hyper Text Transport Protocol (port 80).
•  HTTPS - Specifies Hyper Text Transport Protocol Secure (port 443).
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated expose type netapp host kabar-vva35 serial CLONE12P5D snap-name snapshot1 user admincentral password adminpass367 use-ssl
 
Core_02 (config) # failover-peer storage snapshot test integrated expose type netapp host kabar-vva35 serial CLONE12P5D snap-name snapshot1 user admincentral password adminpass367 use-ssl
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete serial, storage snapshot test integrated delete type, storage snapshot test integrated expose serial, storage snapshot test integrated take serial, storage snapshot test integrated take type, storage snapshot test integrated un-expose serial, storage snapshot test integrated un-expose type
storage snapshot test integrated proxy-backup serial
Test runs a proxy backup test.
Syntax
[failover-peer] storage snapshot test integrated proxy-backup serial <lun-serial>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
The proxy backup feature of Core enables backup integration directly from the data center. Core clones the snapshot specified for data protection and mounts the cloned LUN on the proxy server. The backup software then communicates with the proxy server to perform the backup.
Example
Core_01 (config) # storage snapshot test integrated proxy-backup serial ORIG12P5D
Core_02 (config) # failover-peer storage snapshot test integrated proxy-backup serial ORIG12P5D
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete serial, storage snapshot test integrated delete type, storage snapshot test integrated expose serial, storage snapshot test integrated expose type, storage snapshot test integrated take type, storage snapshot test integrated un-expose serial, storage snapshot test integrated un-expose type
storage snapshot test integrated take serial
Test creates a LUN snapshot without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated take serial <lun-serial> [group <group-name>] [ snap-name <snap-name>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
snap-name <snap-name>
Specifies the name of the snapshot.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated take serial ORIG12P5D
 
Core_02 (config) # failover-peer storage snapshot test integrated take serial ORIG12P5D
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete serial, storage snapshot test integrated delete type, storage snapshot test integrated expose serial, storage snapshot test integrated expose type, storage snapshot test integrated take type, storage snapshot test integrated un-expose serial, storage snapshot test integrated un-expose type
storage snapshot test integrated take type
Test creates a LUN snapshot, specified by array type, without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated take type <array-type> host <hostname> serial <lun-serial> user <username> password <password> protocol <protocol> [group <group-name>] [use-ssl]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array-type>
Storage array type:
•  emc_vnx - EMC VNX
•  dell_equallogic - Dell EqualLogic
•  netapp - NetApp
•  ibm_v7000 - IBM V7000
•  hp3par - HP3PAR
•  ibm_xiv - IBM XIV/Spectrum Accelerate
•  EMC-Unity
•  Nimble
•  Zadara
host <hostname>
Specifies the hostname of the storage array.
serial <lun-serial>
Specifies the snapshot LUN by the LUN serial number.
user <username>
Specifies a valid username for the snapshot credential.
password <password>
Specifies a valid password for the snapshot credential.
protocol <protocol>
For Zadara storage arrays, specifies the communication protocol to use with the array.
•  HTTP - Specifies Hyper Text Transport Protocol (port 80).
•  HTTPS - Specifies Hyper Text Transport Protocol Secure (port 443).
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated take type vnx host kabar-vva35 serial ORIG12P5D user admincentral password adminpass367
 
Core_02 (config) # failover-peer storage snapshot test integrated take type vnx host kabar-vva35 serial ORIG12P5D user admincentral password adminpass367
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete serial, storage snapshot test integrated delete type, storage snapshot test integrated expose serial, storage snapshot test integrated expose type, storage snapshot test integrated take serial, storage snapshot test integrated un-expose serial, storage snapshot test integrated un-expose type
storage snapshot test integrated un-expose serial
Test deletes the cloned LUN, which was created from the snapshot, without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated un-expose serial <lun-serial> snap-lun-serial <snap-lun-serial> [group <group-name>] [use-ssl]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
snap-lun-serial <snap-lun-serial>
Specifies the serial number of the cloned LUN to be deleted.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated un-expose serial CLONE12P5D
 
Core_02 (config) # failover-peer storage snapshot test integrated un-expose serial CLONE12P5D
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete serial, storage snapshot test integrated delete type, storage snapshot test integrated expose serial, storage snapshot test integrated expose type, storage snapshot test integrated take serial, storage snapshot test integrated take type, storage snapshot test integrated un-expose type
storage snapshot test integrated un-expose type
Test deletes the cloned LUN, specified by the array type, without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated un-expose type <array-type> host <hostname> serial <lun-serial> snap-lun-serial <snap-lun-serial> user <username> password <password> protocol <protocol> [group <group-name>] [use-ssl]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array-type>
Storage array type:
•  emc_vnx - EMC VNX
•  dell_equallogic - Dell EqualLogic
•  netapp - NetApp
•  ibm_v7000 - IBM V7000
•  hp3par - HP3PAR
•  ibm_xiv - IBM XIV/Spectrum Accelerate
•  EMC-Unity
•  Nimble
•  Zadara
host <hostname>
Specifies the hostname of the storage array.
serial <lun-serial>
Specifies the locally assigned LUN serial number.
snap-lun-serial <snap-lun-serial>
Specifies the snapshot LUN by the LUN serial number.
user <username>
Specifies a valid username for the snapshot credential.
password <password>
Specifies a valid password for the snapshot credential.
protocol <protocol>
For Zadara storage arrays, specifies the communication protocol to use with the array.
•  HTTP - Specifies Hyper Text Transport Protocol (port 80).
•  HTTPS - Specifies Hyper Text Transport Protocol Secure (port 443).
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated un-expose type emc_vnx host kabar-vva35 serial CLONE12P5D snap-lun-serial CLONE153xD user admincentral password adminpass367
 
Core_02 (config) # failover-peer storage snapshot test integrated un-expose type emc_vnx host kabar-vva35 serial CLONE12P5D snap-lun-serial CLONE153xD user admincentral password adminpass367
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete serial, storage snapshot test integrated delete type, storage snapshot test integrated expose serial, storage snapshot test integrated expose type, storage snapshot test integrated take serial, storage snapshot test integrated take type, storage snapshot test integrated un-expose serial
SteelFusion Core NFS (file mode) commands
SteelFusion 5.0 adds the ability to configure file-based exports and Edge local exports. An export is a unique identifier associated with file systems or directories located on a backend storage array that are accessible to the Core. Exports are mounted on the Core and then mapped to the Edge at the branch. If the Core uses exports instead of logical unit numbers (LUNs), it is in file mode. The terms NFS and file can be used interchangeably. You need a SteelFusion NFS (SFNFS) license to support file mode. Block mode (iSCSI) is the default mode.
The Core mounts exports provisioned for the branch offices from a NetApp or EMC Isilon storage array and manages transfers between these exports and the Edges at the branch. The exports share the space in the blockstore cache of the associated Edges, and the data is continuously replicated and kept synchronized with the associated export in the data center. The Edge blockstore caches only the working set of files for these exports; additional data is retrieved from the data center when needed. See the SteelFusion Edge Management Console User Guide for more information.
service reset
Resets the SteelFusion Core storage mode and clears all settings.
Syntax
service reset {set-mode-file | set-mode-block}
Parameters
set-mode-file
Resets the storage mode to file and clears all storage configurations. This storage mode supports the NFS protocol.
set-mode-block
Resets the storage mode to block and clears all storage configurations. This storage mode supports the iSCSI protocol. Contact technical support before using this option.
Usage
The command asks for confirmation before proceeding with changing the storage mode. The Core automatically reboots when the operation completes. This operation clears any storage configuration on the Core so be careful to ensure the command is entered on the correct Core appliance.
Use the show service command to display the current storage mode of the appliance.
Example
Core_01 (config) # service reset set-mode-file
Product
SteelFusion Core
Related Commands
show service
storage backup proxy add (NFS)
Adds the backup proxy and configures the backup proxy settings.
Syntax
[failover-peer] storage backup proxy add <proxy-id> hostname {<proxy-hostname> | <ip-address>} type vmware_esxi username <name> password <password> access_group <access-group>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<proxy-id>
Proxy identifier.
hostname <proxy-hostname>
Specifies the proxy hostname of the proxy host.
hostname <ip-address>
Specifies the IP address of the proxy host.
type vmware_esxi
Specifies the VMware ESXi compute type.
username <name>
Specifies the username for the backup proxy.
password <password>
Specifies the password for the proxy user.
acccess_group <access-group>
Specifies the access group for the backup proxy.
•  NetApp - Specify the export policy name containing the access rule for the proxy ESXi server.
•  EMC Isilon - Specify a comma-separated list of data interface IP addresses or a hostname for the proxy server.
The username and password credentials must have access to SSH because snapshot communication occurs through this channel.
Usage
The Core integrates with the snapshot capabilities of the storage array. Once the snapshot reaches the data center, the Core triggers the application-consistent snapshot on the supported array and automatically mounts the snapshot to a proxy host. The backup software on the storage array can then perform the backups through the proxy host in the data center.
One backup proxy can be shared among multiple backup policies.
The typical workflow for setting up backup protection follows:
1. Use the storage server add command to add an Edge server.
2. Use the storage backup proxy add (NFS) command to add the backup proxy.
3. Use the storage backup policy add command to configure the backup protection policy.
4. Use the storage backup group add command to add the backup protection group.
Example
Core_01 (config) # storage backup proxy add sh-240-vsp-proxy hostname sf-shxxx155 type vmware_esxi username centraladmin password rootgroup access_group sh-240-vsp-iqn
Product
SteelFusion Core
Related Commands
show storage backup proxy, storage backup proxy modify, storage backup proxy remove
storage backup proxy modify (NFS )
Modifies the backup proxy settings.
Syntax
[failover-peer] storage backup proxy modify <proxy-id> [hostname <proxy-hostname>] [type vmware_esxi] [username <name>] [password <password>] [access_group <access-group>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<proxy-id>
Proxy identifier.
hostname <proxy-hostname>
Specifies the proxy hostname or IP address of the proxy host.
type vmware_esxi
Specifies the VMware ESXi compute type.
username <name>
Specifies the username for the backup proxy.
password <password>
Specifies the password for the proxy user.
access_group <access-group>
Specifies the access group for the backup proxy.
•  NetApp - Specify the export policy name containing the access rule for the proxy ESXi server.
•  EMC Isilon - Specify a comma-separated list of data interface IP addresses or a hostname for the proxy server.
The username and password credentials must have access to SSH because snapshot communication occurs through this channel.
Usage
One backup proxy can be shared among multiple backup policies.
Example
Core_01 (config) # storage backup proxy modify sh-240-vsp-proxy password centadmin396Za!
Product
SteelFusion Core
Related Commands
show storage backup proxy, storage backup proxy remove, storage backup proxy remove
storage nfs array add
Adds a backend NFS array.
Syntax
[failover-peer] storage nfs array add <array> [scan]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array>
Backend NFS array name or IP address.
scan
Scans the backend NFS array for exports.
Usage
The storage array provides the files and hosts the storage in the backend.
Example
Core_01 (config) # storage nfs array add sf-vva20
Product
SteelFusion Core
Related Commands
show storage nfs array, show storage nfs arrays
storage nfs array modify add-snap
Adds the snapshot configurations to the NFS array.
Syntax
[failover-peer] storage nfs array modify <array> add-snap type <type> host <hostname> username <name> password <password> [protocol <protocol>] [port <port>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array>
Backend NFS array name or IP address.
type <type>
Specifies the type of storage array:
•  netapp - NetApp storage array.
•  isilon - EMC Isilon storage array. You can only use the HTTPS protocol for the Isilon snapshot communication from the Core. The default port is 8080. You can change the port but not the protocol. If you specify another protocol, it is internally changed to HTTPS.
host <hostname>
Specifies the IP address or hostname for the management of the NFS storage array.
username <name>
Specifies the username.
password <password>
Specifies the password to authenticate the NFS array.
protocol <protocol>
Specifies the communication protocol to use with the NFS array.
•  HTTP - Hyper Text Transport Protocol
•  HTTPS - Hyper Text Transport Protocol Secure
port <port>
Specifies the port number to connect to.
Usage
You only need to configure a snapshot once per storage array (per NFS server IP address). Those settings automatically apply to all exports mounted from the NFS server.
Example
Core_01 (config) # storage nfs array modify 10.4.254.17 add-snap type netapp host netapp-main username root password mypassword
Product
SteelFusion Core
Related Commands
storage nfs array modify modify-snap
storage nfs array modify map-snap
Maps existing snapshot configurations to an NFS array.
Syntax
[failover-peer] storage nfs array modify <array> map-snap host <hostname>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array>
Backend array name or server IP address or comma-separated list of array names or IP addresses.
host <hostname>
Specifies the IP address or hostname for the management of the NFS storage array.
Usage
This command allows you to reuse the snapshot host configuration across multiple data interfaces using a comma-separated list of array names or IP addresses. This option is only available through the command-line interface.
Example
Core_01 (config) # storage nfs array modify 10.5.170.201,10.5.170,202 map-snap host 10.5.27.111
Product
SteelFusion Core
Related Commands
storage nfs array modify modify-snap, storage nfs array modify add-snap
storage nfs array modify modify-snap
Modifies the snapshot configuration of the NFS array.
Syntax
[failover-peer] storage nfs array modify <array> modify-snap [host <hostname>] [username <name>] [password <password] [protocol <protocol>] [port <port>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array>
Backend NFS array name or IP address
host <hostname>
Specifies the IP address or hostname for the management of the NFS storage array.
username <name>
Specifies the username.
password <password>
Specifies the password to authenticate the NFS array
protocol <protocol>
Specifies the communication protocol to use with the NFS array.
•  HTTP - Hyper Text Transport Protocol
•  HTTPS - Hyper Text Transport Protocol Secure
port <port>
Specifies the port number to connect to.
Example
Core_01 (config) # storage nfs array modify 10.5.170.205 modify-snap username johndoe
Product
SteelFusion Core
Related Commands
storage nfs array modify add-snap
storage nfs array modify modify-snap redundant-paths
Configure redundant paths to the snapshot host.
Syntax
[failover-peer] storage nfs array modify <array> modify-snap redundant-paths {add rp-host <host> [rp-port <port>] | remove rp-host <host>}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array>
Backend array name or IP address.
add
Adds redundant paths for snapshot host.
rp-host <host>
Specifies the host for the redundant path.
rp-port <port>
Specifies the port for the redundant path.
remove
Removes redundant paths for the snapshot host.
Example
Core_01 (config) # storage nfs array modify 10.5.170.201 modify-snap redundant-paths add rp-host 10.5.27.111
Product
SteelFusion Core
Related Commands
show storage nfs array
storage nfs array modify remove-snap
Removes the snapshot configurations of the NFS array.
Syntax
[failover-peer] storage nfs array modify <array> remove-snap
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array>
Backend array name or IP address.
Example
Core_01 (config) # storage nfs array modify 10.5.170.201 remove-snap
Product
SteelFusion Core
Related Commands
show storage nfs array
storage nfs array remove
Removes the specified backend NFS array.
Syntax
[failover-peer] storage nfs array remove <array>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array>
Backend array name or IP address.
Usage
Before removing a storage array, you must unmount any exports from that storage array that are currently mapped to Edges.
Example
Core_01 (config) # storage nfs array remove sf-vva20
Product
SteelFusion Core
Related Commands
show storage nfs array
storage nfs array scan
Scans the backend NFS array for exports.
Syntax
[failover-peer] storage nfs array scan <array>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array>
Backend NFS array name or IP address.
Usage
You scan the array to find the exports, mount the exports to the Core, then map those exports from the Core to the Edge.
Example
Core_01 (config) # storage nfs array scan 10.5.20.110
Scan of 10.5.20.110 was successful
#Server: 10.5.20.110
#Last Scan: Mon Jan 15 21:23:30 2017
#Total discovered NFS Exports: 3
#NFS Export Access Free/Total
10.5.20.110:/ifs/fresh RW 39.000 TB/39.000 TB
10.5.20.110:/ifs/nfs1 RW 20.00 GB/20.00 GB
10.5.20.110:/ifs/fresh RW 199.97 GB/200.00 GB
Product
SteelFusion Core
Related Commands
show storage nfs array show storage nfs scan
storage nfs export add-edge-local
Adds the Edge local NFS export on the SteelFusion Edge.
Syntax
[failover-peer] storage nfs export add-edge-local edge-id <edge-self-identifier> edge-export-dir <edge-directory> size <size> [access -list]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
edge-id <edge-self-identifier>
Self-identifier of the Edge. Edge identifiers are case sensitive.
edge-export-dir <edge-directory>
Sets the path to the directory of the export on the SteelFusion Edge.
size <size>
Specifies the size of the Edge local export in MiB.
access <access-list>
Configures the list of clients that are allowed access to the export on the Edge. You can enter:
•  A comma-separated list of IPv4 addresses, CIDR addresses, or hostnames enclosed in quotation marks (" ").
•  An asterisk (*) meaning access to all.
•  The #VSP# keyword that is internally replaced by the actual IP addresses later. To determine VSP access, the VSP service automatically scans the VSP ESXi hypervisor for all IP addresses to be given access to the export. At the time of configuration, the IPv4 addresses are not known.
Usage
Edge local exports are used to store transient and temporary data, and also use dedicated space in the blockstore cache of the associated Edges, but this data is not replicated back to the data center.
Example
Core_01 (config) # storage nfs export add-edge-local edge-id Edge2 edge-export-dir /user_test1_core1
 
Core_02 (config) # failover-peer storage nfs export add-edge-local edge-id Edge2 edge-export-dir /user_test1_core1
Product
SteelFusion Core
Related Command
show storage nfs export (Core)
storage nfs export modify accelerate-iops
Enables or disables I/O operations per second (IOPS) acceleration for the export.
Syntax
[failover-peer] storage nfs export modify <export> accelerate-iops {enable | disable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export>
Directory path to the backend storage array where the export is located.
enable
Enables I/O operations per second acceleration for the export.
disable
Disables I/O operations per second acceleration for the export.
Usage
I/O operations per second acceleration is enabled by default for the NFS export.
Example
Core_01 (config) # storage nfs export modify main-netapp4:/vol/user1 accelerator-iops enable
Product
SteelFusion Core
Related Command
show storage nfs export (Core)
storage nfs export modify access
Modifies the NFS access settings for the export.
Syntax
[failover-peer] storage nfs export modify <export-path> access <access-list>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Directory path to the backend storage array where the export is located.
access <access-list>
Configures the list of clients that are allowed access to the export on the Edge. You can enter:
•  A comma-separated list of IPv4 addresses, CIDR addresses, or hostnames enclosed in quotation marks (" ").
•  An asterisk (*) meaning access to all.
•  The #VSP# keyword that is internally replaced by the actual IP addresses later. To determine VSP access, the VSP service scans the VSP ESXi hypervisor for all IP addresses to be given access to the export. At the time of configuration, the IPv4 addresses are not known.
Usage
The default is no access.
Example
Core_01 (config) # storage nfs export modify /user_test1_core1 access 10.2.2.2,10.2.2.1
Product
SteelFusion Core
Related Commands
show storage nfs export (Core)
storage nfs export modify edge-export-dir
Modifies the path where the export is located on the SteelFusion Edge.
Syntax
[failover-peer] storage nfs export modify <export-path> edge-export-dir <new-export-path>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Original path to the directory where the export is located on the SteelFusion Edge.
<new-export-path>
Sets the new path to the directory where the export is located on the SteelFusion Edge.
Usage
Modifying the export directory will invalidate the VMs and VMDKs in this NFS export. A manual cleanup might be necessary on the ESXi server. For more information, see the SteelFusion Design Guide.
Example
Core_01 (config) # storage nfs export modify main-netapp4:/vol/user1 edge-export-dir /tmp/testtett
Product
SteelFusion Core
Related Commands
show storage nfs export (Core)
storage nfs export modify map edge-id
Maps a mounted NFS export to a SteelFusion Edge.
Syntax
[failover-peer] storage nfs export modify <export-path> map edge-id <edge-self-identifier> [access <access-list>] [edge-export-dir <edge-directory>] [pinned enable]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Directory path to the backend storage array where the export is located.
<edge-self-identifier>
Specifies the self-identifier of the desired Edge. Edge identifiers are case sensitive.
access <access-list>
Configures the list of clients that are allowed access to the export on the Edge. You can enter:
•  A comma-separated list of IPv4 addresses, CIDR addresses, or hostnames enclosed in quotation marks (" ").
•  An asterisk (*) meaning access to all.
•  The #VSP# keyword that is internally replaced by the actual IP addresses later. To determine VSP access, the VSP service automatically scans the VSP ESXi hypervisor for all IP addresses to be given access to the export. At the time of configuration, the IPv4 addresses are not known.
edge-export-dir <edge-directory>
Sets the path to the directory where the export is located on the SteelFusion Edge.
pinned enable
Enables pinning for the export. When an export is pinned, the data is reserved and not subject to the normal blockstore eviction policies.
Usage
You scan the array to find the exports, mount the exports to the Core, then map those exports from the Core to the Edge.
Example
Core_01 (config) # storage nfs export modify 10.5.27.111:/ifs/nfs1 map edge-id sf-vvaxxx edge-export-dir /ifs/nfs1
Product
SteelFusion Core
Related Commands
show storage nfs export (Core)
storage nfs export modify offline
Takes the NFS export offline.
Syntax
[failover-peer] storage nfs export modify <export-path> offline
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Directory path to the backend storage array where the export is located.
Usage
When you take an export offline, all data is removed from the Edge blockstore and it is no longer available, unless brought back online.
After you take an export offline, you must unmap and unmount the export.
Example
Core_01 (config) # storage nfs export modify /user_test1_core1 offline
Product
SteelFusion Core
Related Commands
show storage nfs export (Core), storage nfs export modify online
storage nfs export modify online
Brings the NFS export online.
Syntax
[failover-peer] storage nfs export modify <export-path> online
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Directory path to the backend storage array where the export is located.
Usage
Pinning and prepopulation settings are not preserved across offline and online operations. You need to configure those settings after bringing an export online.
Example
Core_01 (config) # storage nfs export modify /user_test1_core1 online
Product
SteelFusion Core
Related Commands
show storage nfs export (Core), storage nfs export modify offline
storage nfs export modify pinned
Configures pinning for the NFS export.
Syntax
[failover-peer] storage nfs export modify <export-path> pinned {disable | enable}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Directory path to the backend storage array where the export is located.
disable
Pins the NFS export.
enable
Unpins the NFS export.
Usage
Pinning and prepopulation settings are not preserved across offline and online operations. You need to configure those settings after bringing an export online.
Example
Core_01 (config) # storage nfs export modify /user_test1_core1 pinned enable
Product
SteelFusion Core
Related Commands
show storage nfs export (Core)
storage nfs export modify prepop-window
Starts or removes the prepopulation operation on an NFS export.
Syntax
[failover-peer] storage nfs export modify <export-path> prepop-window {now | remove}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Directory path to the backend storage array where the export is located.
now
Starts prepopulation on an NFS export immediately.
remove
Removes the prepopulation window from the NFS export immediately.
Example
Core_01 (config) # storage nfs export modify 10.5.254.17:/user_nfs_vol_2 prepop-window remove
 
Core_01 (config) # show storage nfs exports
Total NFS Exports: 2
....
NFS Export Path: 10.5.254.17:/user_nfs_vol_2
Size : 4.75 GiB
Available Size : 2.67 GiB
Edge mapping : vge1
Edge NFS Export Directory : /user_nfs_vol_2
Edge NFS Export Access List : *
Type : nfs
ID : 6a248c29-b0d0-49c8-a734-95500f0e8f44
Edge Data Session : Connected
Backend Export Excludes : .cpkt,.riverbed_snapshot,.snapshot
Backend Export Availability : True
Metadata State : Ready
Online : yes
Prefetch : Enabled
Failover Enabled : yes
Pinned : yes
Prepop Window :
Prepop Progress : 0%
Prepop Status :
IOPs acceleration : yes
Product
SteelFusion Core
Related Commands
show storage nfs exports (Core)
storage nfs export modify unmap
Unmaps a mapped NFS export from a SteelFusion Edge.
Syntax
[failover-peer] storage nfs export modify <export-path> unmap
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Directory path to the backend storage array where the export is located.
Example
Core_01 (config) # storage nfs export modify 10.5.254.17:/user_nfs_vol_2 unmap
Product
SteelFusion Core
Related Commands
show storage nfs export (Core)
storage nfs export mount
Mounts the NFS export to the SteelFusion Core.
Syntax
[failover-peer] storage nfs export mount <export-path> [exclude <objects>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Directory path to the backend storage array where the export is located.
exclude <objects>
Excludes the specified files and directories from the export.
Usage
Mounting an export means establishing an attachment of part of a remote file system to the local file system. You must mount the export before files on the server can be accessed.
Example
Core_01 (config) # storage nfs export mount 10.5.20.110:/ifs/nfs1
Product
SteelFusion Core
Related Commands
show storage nfs export (Core), storage nfs export unmount
storage nfs export rem-edge-local
Removes the edge local NFS export on the SteelFusion Edge.
Syntax
[failover-peer] storage nfs export rem-edge-local edge-id <edge-self-identifier> edge-export <export>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
edge-id <edge-self-identifier>
Specifies the self-identifier of the Edge. Edge identifiers are case sensitive.
edge-export <export>
Sets the path to the directory of the export on the SteelFusion Edge.
Usage
Edge local exports are used to store transient and temporary data, and also use dedicated space in the blockstore cache of the associated Edges, but this data is not replicated back to the data center. The data is not backed up and there is no warning message if you remove an edge local NFS export using this command.
Example
Core_01 (config) # storage nfs export rem-edge-local edge-id sf-vvaxxx edge-export 10.5.200.200:/user_nfs_vol_1xxx
Product
SteelFusion Core
Related Commands
show storage nfs export (Core)
storage nfs export resize
Resizes the export in the Core configuration.
Syntax
[failover-peer] storage nfs export resize <export-path>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Directory path to the backend storage array where the export is located.
Usage
This command changes the export size dynamically while the export is online and serving data. You do not need to take the export offline to increase the size.
Example
Core_01 (config) # storage nfs export resize 10.5.200.200:/user_nfs_vol_1xxx
Product
SteelFusion Core
Related Commands
show storage nfs export (Core)
storage nfs export unmount
Unmounts the NFS backend export path from the Core.
Syntax
[failover-peer] storage nfs export unmount <export-path>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<export-path>
Directory path to the backend storage array where the export is located.
Usage
You must unmap the export from the Edge appliance before you can unmount it from the Core.
Example
Core_01 (config) # storage nfs export unmount 10.5.200.200:/user_nfs_vol_1xxx
Product
SteelFusion Core
Related Commands
storage nfs export mount
storage snapshot test integrated delete type (NFS)
Test deletes an NFS snapshot, specified by storage array type, without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated delete type <array-type> host <hostname> export <export-path> snap-name <snap-name> user <username> password <password> [group <group-name>] [use-ssl] [port <port>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
type <array-type>
Specifies the type of storage array:
•  netapp - NetApp storage array
•  isilon - Isilon storage array.
host <hostname>
Specifies the IP address or hostname of the storage array.
export <export-path>
Directory path to the backend storage array where the export is located.
snap-name <snap-name>
Specifies the snapshot by name.
user <username>
Specifies a username for the snapshot credential.
password <password>
Specifies an alphanumeric password for the snapshot credential.
group <group-name>
Specifies the storage or initiator group name.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
port <port>
Specifies the port to connect to.
You can only use the HTTPS protocol for the Isilon storage array. If you do not specify a port, the port defaults to 8080 for Isilon. You can change the port but not the protocol. If you specify another protocol, it is internally changed to HTTPS.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated delete type isilon host 10.5.26.101 export 10.5.26.101:/user_nfs_vol_2 snap-name snapshot1 user admincentral password adminpass367
 
Core_02 (config) # failover-peer storage snapshot test integrated delete type isilon host 10.5.26.101 export 10.5.26.101:/user_nfs_vol_2 snap-name snapshot1 user admincentral password adminpass367
Product
SteelFusion Core
Related Commands
storage snapshot test integrated expose type (NFS), storage snapshot test integrated hello type (NFS), storage snapshot test integrated take type (NFS), storage snapshot test integrated un-expose type (NFS)
storage snapshot test integrated expose type (NFS)
Test exposes a private snapshot, specified by array type, without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated expose type <array-type> host <hostname> export <export-path> snap-name <snap-name> user <username> password <password> [group <group-name>] [use-ssl] [port <port>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
type <array-type>
Specifies the type of storage array:
•  netapp - NetApp storage array.
•  isilon - EMC Isilon storage array.
host <hostname>
Specifies the IP address or hostname of the storage array.
export <export-path>
Directory path to the backend storage array where the export is located.
snap-name <snap-name>
Specifies the name of the snapshot.
user <username>
Specifies a username for the snapshot credential.
password <password>
Specifies an alphanumeric password for the snapshot credential.
group <group-name>
Specifies the storage or initiator group name.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
port <port>
Specifies the port to connect to.
You can only use the HTTPS protocol for the Isilon storage array. If you do not specify a port, the port defaults to 8080 for Isilon. You can change the port but not the protocol. If you specify another protocol, it is internally changed to HTTPS.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated expose type isilon host 10.5.26.101 export 10.5.26.101:/user_nfs_vol_2 snap-name snapshot1 user admincentral password adminpass367
 
Core_02 (config) # failover-peer storage snapshot test integrated expose type isilon host 10.5.26.101 export 10.5.26.101:/user_nfs_vol_2 snap-name snapshot1 user admincentral password adminpass367
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete type (NFS), storage snapshot test integrated hello type (NFS), storage snapshot test integrated take type (NFS), storage snapshot test integrated un-expose type (NFS)
storage snapshot test integrated hello type (NFS)
Tests the connection to the storage array.
Syntax
[failover-peer] storage snapshot test integrated hello type <array-type> host <hostname> user <username> password <password> port <port> protocol <protocol>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
type <array-type>
Specifies the type of storage array:
•  netapp - NetApp storage array.
•  isilon - Isilon storage array.
host <hostname>
Specifies the IP address or hostname of the storage array.
user <username>
Specifies a username for the snapshot credential.
password <password>
Specifies an alphanumeric password for the snapshot credential.
port <port>
Specifies the port to connect to.
You can only use the HTTPS protocol for the Isilon storage array. If you do not specify a port, the port defaults to 8080 for Isilon. You can change the port but not the protocol. If you specify another protocol, it is internally changed to HTTPS.
protocol <protocol>
Specifies the communication protocol to use with the NFS array.
•  HTTP - Hyper Text Transport Protocol
•  HTTPS - Hyper Text Transport Protocol Secure
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated hello type isilon host 10.5.26.101 user admincentral password adminpass367 port 8080 protocol https
 
Core_02 (config) # failover-peer storage snapshot test integrated hello type isilon host 10.5.26.101 user admincentral password adminpass367 port 8080 protocol https
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete type (NFS), storage snapshot test integrated expose type (NFS), storage snapshot test integrated take type (NFS), storage snapshot test integrated un-expose type (NFS)
storage snapshot test integrated take type (NFS)
Test creates an NFS snapshot for export without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated take type <array-type> host <hostname> export <export-path> user <username> password <password> [group <group-name>] [use-ssl] [snap-name <snap-name>] [port <port>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
type <array-type>
Specifies the type of storage array:
•  netapp - NetApp storage array
•  isilon - EMC Isilon storage array.
host <hostname>
Specifies the hostname of the storage array.
export <export-path>
Directory path to the backend storage array where the export is located.
user <username>
Specifies a valid username for the snapshot credential.
password <password>
Specifies a valid password for the snapshot credential.
group <group-name>
Specifies the storage or initiator group name.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
snap-name <snap-name>
Specifies the snapshot name.
port <port>
Specifies the port to connect to.
You can only use the HTTPS protocol for the Isilon storage array. If you do not specify a port, the port defaults to 8080 for Isilon. You can change the port but not the protocol. If you specify another protocol, it is internally changed to HTTPS.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated take type isilon host 10.5.26.101 export 10.5.26.101:/user_nfs_vol_2 snap-name snapshot1 user admincentral password adminpass367
 
Core_02 (config) # failover-peer storage snapshot test integrated take isilon host 10.5.26.101 export 10.5.26.101:/user_nfs_vol_2 snap-name snapshot1 user admincentral password adminpass367
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete type (NFS), storage snapshot test integrated expose type (NFS), storage snapshot test integrated hello type (NFS), storage snapshot test integrated un-expose type (NFS)
storage snapshot test integrated un-expose type (NFS)
Test the unexposing of a snapshot without changing the current configuration.
Syntax
[failover-peer] storage snapshot test integrated un-expose type <array-type> host <hostname> export <export-path> snap-export <type> user <username> password <password> [group <group-name>] [use-ssl] [port <port>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
type <array-type>
Specifies the type of storage array:
•  netapp - NetApp storage array.
•  isilon - EMC Isilon storage array.
host <hostname>
Specifies the hostname of the storage array.
export <export-path>
Directory path to the backend storage array where the export is located.
snap-export <path>
Specifies the NFS clone export path.
user <username>
Specifies a valid username for the snapshot credential.
password <password>
Specifies a valid password for the snapshot credential.
group <group-name>
Specifies the storage or initiator group name.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
port <port>
Specifies the port to connect to.
You can only use the HTTPS protocol for the Isilon storage array. If you do not specify a port, the port defaults to 8080 for Isilon. You can change the port but not the protocol. If you specify another protocol, it is internally changed to HTTPS.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage snapshot test integrated un-expose type isilon host 10.5.26.101 export 10.5.26.101:/user_nfs_vol_2 snap-export 10.5.26.102:/user_nfs_vol_1 user admincentral password adminpass367
 
Core_02 (config) # failover-peer storage snapshot test integrated un-expose type isilon host 10.5.26.101 export 10.5.26.101:/user_nfs_vol_2 snap-export 10.5.26.102:/user_nfs_vol_1 user admincentral password adminpass367
Product
SteelFusion Core
Related Commands
storage snapshot test integrated delete type (NFS), storage snapshot test integrated expose type (NFS), storage snapshot test integrated hello type (NFS), storage snapshot test integrated un-expose type (NFS)
SteelFusion Core Hyper-V mode commands
In SteelFusion 6.0, you can connect the physical Core appliance (SFCR3500) to the new Hyper-V Edge appliances (VSFH1100 and VSFH1200). The hypervisor mode on the Core must match the hypervisor mode on the Edges at your branch offices. A Core or an Edge cannot operate in both the ESXi and Hyper‑V modes at the same time. For more information about hypervisor modes, see the SteelFusion Core Installation and Configuration Guide.
This section describes commands that are specific to the SteelFusion Core Hyper-V hypervisor mode.
Note: The SteelFusion Core in the Hyper-V mode operates only in the block (iSCSI) mode. The file (NFS) mode is not applicable for the Hyper-V mode.
storage protection backup group add
Adds a backup group and configures the storage backup configuration settings.
Syntax
[failover-peer] storage protection backup group add <group-id> server-id <server-id> policy-id <policy-id> {membership all [exclude <members>] | membership selected members <members>} [max-history <max-history-number>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<group-id>
Backup group identifier.
server-id <server-id>
Specifies the Edge server identifier. Identifiers are case sensitive.
policy-id <policy-id>
Specifies the backup policy identifier.
membership all
Specifies all members in the backup group.
exclude <members>
Excludes the specified members.
membership selected members <members>
Specifies selected members in a backup group.
max-history <max-history-number>
Specifies the maximum history of backup operations maintained for the backup group. The default is 5.
Usage
The Core uses the backup group to map the servers, VMs, and LUNs that are being protected. Each backup group contains the information associated with the server being protected and backup policy.
The typical workflow for setting up backup follows:
1. Use the storage server add (Hyper-V mode) command to add an Edge server.
2. Use the storage protection backup proxy add command to add the backup proxy.
3. Use the storage protection backup policy add command to configure the backup policy.
4. Use the storage protection backup group add command to add the backup group.
Example
Core_01 (config) # storage protection backup group add group1 server-id sf-shxxx-server policy-id pol_1 membership all max-history 4
Product
SteelFusion Core
Related Commands
show storage protection backup group (Core in Hyper-V mode), storage protection backup group modify, storage protection backup group remove
storage protection backup group modify
Modifies the configuration settings for the specified backup group.
Syntax
[failover-peer] storage protection backup group modify <group-id> [server-id <server-id>] [membership {all | selected members <members>}] [members <members>] [exclude <members>] [max-history <max-history-number>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<group-id>
Backup group identifier.
server-id <server-id>
Specifies the Edge server identifier. Identifiers are case sensitive.
membership all
Specifies all members in a backup group.
membership selected members <members>
Specifies selected members in a backup group.
members <members>
Specifies members in a backup group.
exclude <members>
Excludes the specified members from the backup group.
max-history <max-history-number>
Specifies the maximum history of backup operations maintained for the backup group. The default is 5.
Usage
This command allows you to modify the backup group settings. You can choose which VMs on a server you want to back up in your backup group. You can customize this backup operation by backing up either VMs on the Edge server specified by roster (inclusive selection) or all VMs on the Edge server except those excluded by roster (exclusive selection).
Example
This example shows how to limit the backup group to vm7 and vm8:
Core_01 (config) # storage protection backup group modify group1 membership selected members vm7,vm8
 
This example shows how to back up all VMs on the Edge server except for vm7 and vm8:
Core_01 (config) # storage protection backup group modify group1 membership all exclude vm7,vm8
Product
SteelFusion Core
Related Commands
show storage protection backup group (Core in Hyper-V mode), storage protection backup group add, storage protection backup group remove
storage protection backup group remove
Removes the specified backup group.
Syntax
[failover-peer] storage protection backup group remove <group-id>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<group-id>
Backup group identifier.
Usage
Each backup group maps to an Edge server, backup proxy host, and backup policy.
The typical workflow for removing backup follows:
1. Use the storage protection backup group remove command to remove the backup group.
2. Use the storage protection backup policy remove command to remove the backup policy.
3. Use the storage protection backup proxy remove command to remove the backup proxy.
4. Use the storage server remove command to remove the Edge server.
Example
Core_01 (config) # storage protection backup group remove group1
Product
SteelFusion Core
Related Commands
show storage protection backup group (Core in Hyper-V mode), storage protection backup group add, storage protection backup group modify
storage protection backup policy add
Add and configures a backup policy.
Syntax
[failover-peer] storage protection backup policy add <policy-name> proxy-id <proxy-id> schedule-type {daily [hour <hour>] [minute <minute>] | hourly [minute <minute>] | weekly [day <day>] [hour <hour>] [minute <minute>]}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Backup policy name.
proxy-id <proxy-id>
Specifies the proxy identifier. Identifiers are case sensitive.
schedule-type
Specifies the type of schedule.
daily
Specifies once a day.
hourly
Specifies every hour.
Note: Because each backup operation takes approximately two minutes to complete, enabling the hourly option for more than 30 LUNS can result in an increasing number of nonreplicated snapshots on Edges.
weekly
Specifies once a week.
hour <hour>
Specifies hour of the day in the 24-hour clock format. For example, for 4:00 P.M., specify 16. The range is from 0 to 23.
minute <minute>
Specifies the minutes after the hour; the valid range is from 0 to 59.
day <day>
Specifies the day of the week for a weekly schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
Usage
This command configures the backup policy that binds together the backup proxy and the schedule to run the backup operation. You can create an hourly, daily, or weekly backup schedule.
If you selected hourly, optionally specify the number of minutes after the hour to start the backup. If you selected daily, optionally specify a time (the local time at the Edge) to start the backup. If you selected weekly, optionally select the day of the week and time (the local time at the Edge).
One backup proxy can be shared among multiple backup policies. You can trigger this policy by using the storage protection trigger command on the Edge appliance.
The typical workflow for setting up backup follows:
1. Use the storage server add (Hyper-V mode) command to add an Edge server.
2. Use the storage protection backup proxy add command to add the backup proxy.
3. Use the storage protection backup policy add command to configure the backup policy.
4. Use the storage protection backup group add command to add the backup group.
Example
Core_01 (config) # storage protection backup policy add Edge-xxx-VBP proxy-id pxy_1 schedule-type weekly day mon
Product
SteelFusion Core
Related Commands
show storage protection backup policy (Hyper-V mode), storage protection backup policy modify, storage protection trigger
storage protection backup policy modify
Modifies the specified backup policy.
Syntax
[failover-peer] storage protection backup policy modify <policy-name> proxy-id <proxy-id> schedule-type {daily [hour <hour>] [minute <minute>] | hourly [minute <minute>] | weekly [day <day>] [hour <hour>] [minute <minute>] } [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Backup policy name.
proxy-id <proxy-id>
Specifies the proxy identifier.
schedule-type
Specifies the type of schedule.
daily
Specifies once a day.
hourly
Specifies every hour.
weekly
Specifies once a week.
hour <hour>
Specifies hour of the day in the 24-hour clock format; for example, for 4:00 P.M. input specify 16. The range is from 0 to 23.
minute <minute>
Specifies the minutes after the hour; the valid range is from 0 to 59.
day <day>
Specifies the day of the week for a weekly schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
force
Forces the policy change if the policy is currently assigned.
Example
Core_01 (config) # storage protection backup policy modify Edge-xxx-VBP proxy-id pxy_1 schedule-type weekly day wed
Product
SteelFusion Core
Related Commands
show storage protection backup policy (Hyper-V mode), storage protection backup policy add, storage protection backup policy remove
storage protection backup policy remove
Removes the specified backup policy.
Syntax
[failover-peer] storage protection backup policy remove <policy-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Backup policy name.
Usage
The typical workflow for removing backup follows:
1. Use the storage protection backup group remove command to remove the backup group.
2. Use the storage protection backup policy remove command to remove the backup policy.
3. Use the storage protection backup proxy remove command to remove the backup proxy.
4. Use the storage server remove command to remove the Edge server
Example
Core_01 (config) # storage protection backup policy remove Edge-xxx-VBP
Product
SteelFusion Core
Related Commands
show storage protection backup policy (Hyper-V mode), storage protection backup policy add, storage protection backup policy modify
storage protection backup proxy add
Adds a backup proxy and configures the backup proxy settings.
Syntax
[failover-peer] storage protection backup proxy add <proxy-id> hostname <proxy-hostname> type {hyperv_server | windows_server} username <name> password <password> storage_group <storage-group>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<proxy-id>
Proxy identifier.
hostname <proxy-hostname>
Specifies the hostname of the proxy host.
type hyperv_server
Specifies the Microsoft Hyper-V Server compute type.
type windows_server
Specifies the Microsoft Windows Server compute type.
username <name>
Specifies the username for the backup proxy.
password <password>
Specifies the password for the proxy user.
storage_group <storage-group>
Specifies the storage group or initiator group for the backup proxy.
Usage
The Core integrates with the snapshot capabilities of the storage array. Once the snapshot reaches the data center, the Core triggers the application-consistent snapshot on the supported array and automatically mounts the snapshot to a proxy host. The backup software on the storage array can then perform the backups through the proxy host in the data center.
One backup proxy can be shared among multiple backup policies.
The typical workflow for setting up backup follows:
1. Use the storage server add (Hyper-V mode) command to add an Edge server.
2. Use the storage protection backup proxy add command to add the backup proxy.
3. Use the storage protection backup policy add command to configure the backup policy.
4. Use the storage protection backup group add command to add the backup group.
Example
Core_01 (config) # storage protection backup proxy add sh-240-vsp-proxy hostname sf-shxxx155 type windows_server username centraladmin password mypass storage_group sh-240-iqn
Product
SteelFusion Core
Related Commands
show storage protection backup proxy (Hyper-V mode), storage protection backup proxy modify, storage protection backup proxy remove
storage protection backup proxy modify
Modifies the backup proxy settings.
Syntax
[failover-peer] storage protection backup proxy modify <proxy-id> [hostname <proxy-hostname>] [type {hyperv_server | windows_server}] [username <name>] [password <password>] [storage_group <storage-group>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<proxy-id>
Proxy identifier.
hostname <proxy-hostname>
Specifies the hostname or IP address of the proxy host.
type hyperv_server
Specifies the Microsoft Hyper-V Server compute type.
type windows_server
Specifies the Microsoft Windows Server compute type.
username <name>
Specifies the username for the backup proxy.
password <password>
Specifies the password for the proxy user.
storage_group <storage-group>
Specifies the storage group or initiator group for the backup proxy.
Usage
One backup proxy can be shared among multiple backup policies.
Example
Core_01 (config) # storage protection backup proxy modify sh-240-proxy password centadmin396Za!
Product
SteelFusion Core
Related Commands
show storage protection backup proxy (Hyper-V mode), storage protection backup proxy add, storage protection backup proxy remove
storage protection backup proxy remove
Removes a backup proxy.
Syntax
[failover-peer] storage protection backup proxy remove <proxy-id>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<proxy-id>
Proxy identifier.
Usage
You cannot remove a backup proxy while it is in use.
The typical workflow for removing backup follows:
1. Use the storage protection backup group remove command to remove the backup group.
2. Use the storage protection backup policy remove command to remove the backup policy.
3. Use the storage protection backup proxy remove command to remove the backup proxy.
4. Use the storage server remove command to remove the Edge server
Example
Core_01 (config) # storage protection backup proxy remove sh-240-vsp-proxy
Product
SteelFusion Core
Related Commands
show storage protection backup proxy (Hyper-V mode), storage protection backup proxy add, storage protection backup proxy modify
storage protection snapshot group add
Adds a snapshot group and configures the storage snapshot configuration settings.
Syntax
[failover-peer] storage protection snapshot group add <group-id> server-id <server-id> policy-id <policy-id> {membership all [exclude <members>] | membership selected members <members>} [max-history <max-history-number>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<group-id>
Snapshot group identifier.
server-id <server-id>
Specifies the Edge server identifier. Identifiers are case sensitive.
policy-id <policy-id>
Specifies the snapshot policy identifier.
membership all
Specifies all members in the snapshot group.
exclude <members>
Excludes the specified members.
membership selected members <members>
Specifies selected members in a snapshot group.
max-history <max-history-number>
Specifies the maximum history of snapshot operations maintained for the snapshot group. The default is 5.
Usage
The Core uses the snapshot group to map the servers, VMs, and LUNs that are being protected. Each snapshot group contains the information associated with the server being protected and snapshot policy.
Example
Core_01 (config) # storage protection snapshot group add group1 server-id sf-shxxx-server policy-id pol_1 membership all max-history 4
Product
SteelFusion Core
Related Commands
show storage protection snapshot group (Core in Hyper-V mode), storage protection snapshot group modify, storage protection snapshot group remove
storage protection snapshot group modify
Modifies the configuration settings for the specified snapshot group.
Syntax
[failover-peer] storage protection snapshot group modify <group-id> [server-id <server-id>] [membership {all | selected members <members>}] [members <members>] [exclude <members>] [max-history <max-history-number>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<group-id>
Snapshot group identifier.
server-id <server-id>
Specifies the Edge server identifier. Identifiers are case sensitive.
membership all
Specifies all members in the snapshot group.
membership selected members <members>
Specifies selected members in a snapshot group.
members <members>
Specifies members in a snapshot group.
exclude <members>
Excludes the specified members from the snapshot group.
max-history <max-history-number>
Specifies the maximum history of protection operations maintained for the snapshot group. The default is 5.
Usage
This command allows you to modify the snapshot group settings. You can choose which VMs on a server you want to protect in your snapshot group. You can customize this snapshot operation by protecting either VMs on the Edge server specified by roster (inclusive selection) or all VMs on the Edge server except those excluded by roster (exclusive selection).
Example
This example shows how to limit the snapshot group to vm7 and vm8:
Core_01 (config) # storage protection snapshot group modify group1 membership selected members vm7,vm8
 
This example shows how to protect all VMs on the Edge server except for vm7 and vm8:
Core_01 (config) # storage protection snapshot group modify group1 membership all exclude vm7,vm8
Product
SteelFusion Core
Related Commands
show storage protection snapshot group (Core in Hyper-V mode), storage protection snapshot group add, storage protection snapshot group remove
storage protection snapshot group remove
Removes the specified snapshot group.
Syntax
[failover-peer] storage protection snapshot group remove <group-id>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<group-id>
Snapshot group identifier.
Usage
Each snapshot group maps to an Edge server and snapshot policy.
Example
Core_01 (config) # storage protection snapshot group remove group1
Product
SteelFusion Core
Related Commands
show storage protection snapshot group (Core in Hyper-V mode), storage protection snapshot group add, storage protection snapshot group modify
storage protection snapshot policy add
Adds and configures a new snapshot policy.
Syntax
[failover-peer] storage protection snapshot policy add <policy-name> policy-type {acs | ccs} schedule-type {daily [hour <hour>] [minute <minute>] | hourly [minute <minute>] | weekly [day <day>] [hour <hour>] [minute <minute>]}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Policy name.
policy-type acs
Specifies the application consistent snapshot policy type.
policy-type ccs
Specifies the crash consistent snapshot policy type.
schedule-type
Specifies the type of schedule.
daily
Specifies once a day.
hourly
Specifies every hour.
Note: Because each backup operation takes approximately two minutes to complete, enabling the hourly option for more than 30 LUNS can result in an increasing number of nonreplicated snapshots on Edges.
weekly
Specifies once a week.
hour <hour>
Specifies hour of the day in the 24-hour clock format. For example, for 4:00 P.M., specify 16. The range is from 0 to 23.
minute <minute>
Specifies the minutes after the hour; the valid range is from 0 to 59.
day <day>
Specifies the day of the week for a weekly schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
Usage
This command configures the snapshot policy that includes the schedule to run the snapshot operation. You can create an hourly, daily, or weekly backup schedule.
If you selected hourly, optionally specify the number of minutes after the hour to start the snapshot operation. If you selected daily, optionally specify a time (the local time at the Edge) to start the snapshot operation. If you selected weekly, optionally select the day of the week and time (the local time at the Edge).
Example
Core_01 (config) # storage protection snapshot policy add Edge-xxx-VBP policy-type acs schedule-type weekly day mon
Product
SteelFusion Core
Related Commands
show storage protection snapshot policy (Hyper-V mode), storage protection snapshot policy modify, storage protection snapshot policy remove
storage protection snapshot policy modify
Modifies the specified snapshot policy.
Syntax
[failover-peer] storage protection snapshot policy modify <policy-name> {policy-type {acs | ccs} | schedule-type {daily [hour <hour>] [minute <minute>] | hourly [minute <minute>] | weekly [day <day>] [hour <hour>] [minute <minute>] } [force]}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<policy-name>
Policy name.
schedule-type
Specifies the type of schedule.
daily
Specifies once a day.
hourly
Specifies every hour.
weekly
Specifies once a week.
hour <hour>
Specifies hour of the day in the 24-hour clock format; for example, for 4:00 P.M. input specify 16. The range is from 0 to 23.
minute <minute>
Specifies the minutes after the hour; the valid range is from 0 to 59.
day <day>
Specifies the day of the week for a weekly schedule. Use the first three characters (lowercase) of the English term for the day of the week: for example, sun, mon, tue, and so on.
force
Forces the policy change if the policy is currently assigned.
Example
Core_01 (config) # storage protection backup policy modify Edge-xxx-VBP proxy-id pxy_1 schedule-type weekly day wed
Product
SteelFusion Core
Related Commands
show storage protection snapshot policy (Hyper-V mode), storage protection snapshot policy add, storage protection snapshot policy remove
storage protection snapshot policy remove
Removes a snapshot policy.
Syntax
[failover-peer] storage protection snapshot policy remove <policy-name>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
<policy-name>
Snapshot policy name.
Example
Core_01 (config) # storage protection snapshot policy remove Edge-xxx-VBP
Product
SteelFusion Core
Related Commands
show storage protection snapshot policy (Hyper-V mode), storage protection snapshot policy add, storage protection snapshot policy modify
storage protection storage-array add
Adds a storage array that can be used for snapshots.
Syntax
[failover-peer] storage protection storage-array add host <hostname> type <type> username <username> password <password> [port <port-number>] [protocol <protocol>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
host <hostname>
Specifies the hostname of the storage array.
type <type>
Storage array type:
•  EMC-VNX - EMC VNX
•  Dell-Equallogic - Dell EqualLogic
•  IBM-V7000 - IBM V7000
•  HP3PAR - HP3PAR
•  IBM-XIV-Spectrum-Accelerate - IBM XIV/Spectrum Accelerate
•  EMC-Unity - EMC Unity
•  NetApp - NetApp
•  Nimble
•  Zadara
username <username>
Specifies the username for the host.
password <password>
Specifies the password for the host.
port <port-number>
For NetApp and Zadara storage arrays, specifies the port number.
protocol <protocol>
For NetApp storage arrays, specifies the protocol type.
Example
Core_01 (config) # storage protection storage-array add host sf-vva14 type NetApp username admin password 1234
 
Core_02 (config) # failover-peer storage protection storage-array add host 1.1.3.4 type NetApp username admin password 1234
Product
SteelFusion Core
Related Command
show storage protection storage-array (Hyper-V mode), storage protection storage-array modify, storage protection storage-array remove
storage protection storage-array modify
Modifies snapshot settings for the specified storage array.
Syntax
[failover-peer] storage protection storage-array modify host <hostname> {username <username> password <password> | port <port-number> | protocol <protocol> | redundant-paths}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
host <hostname>
Specifies the hostname of the storage array.
username <username>
Specifies the username for the host.
password <password>
Specifies the password for the host.
port <port-number>
For NetApp storage arrays, specifies the port number.
protocol <protocol>
For NetApp storage arrays, specifies the protocol type.
redundant-paths
Configures redundant paths to the specified snapshot host in case of failure.
Example
Core_01 (config) # storage protection storage-array modify host sf-vva14 username admin password 1234
 
Core_02 (config) # failover-peer storage protection storage-array modify host 1.1.3.4 protocol HTTPS
Product
SteelFusion Core
Related Command
show storage protection storage-array (Hyper-V mode), storage protection storage-array add, storage protection storage-array remove
storage protection storage-array modify host redundant-paths add rp-host
Configures redundant paths to the specified snapshot host in case of failure.
Syntax
[failover-peer] storage protection storage-array modify host <hostname> redundant-paths add rp-host <rp-host> [rp-port <port>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the storage array.
<rp-host>
Redundant hostname to add for the chosen storage array.
rp-port <port-number>
Specifies the redundant port number for the chosen storage array.
Example
amnesiac (config) # storage protection storage-array modify host sf-vva14 redundant-paths add rp-host sf-vva20 rp-port 90
Product
SteelFusion Core
Related Commands
show storage protection storage-array (Hyper-V mode), storage protection storage-array add, storage protection storage-array modify host redundant-paths remove rp-host
storage protection storage-array modify host redundant-paths remove rp-host
Removes the specified redundant path for the snapshot host.
Syntax
[failover-peer] storage protection storage-array modify host <hostname> redundant-paths remove rp-host <rp-host>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the storage array.
<rp-host>
Redundant hostname to remove for the chosen storage array.
Example
amnesiac (config) # storage protection storage-array modify host sf-vva14 redundant-paths remove rp-host sf-vva20
Product
SteelFusion Core
Related Commands
show storage protection storage-array (Hyper-V mode), storage protection storage-array add, storage protection storage-array modify host redundant-paths add rp-host
storage protection storage-array remove
Removes the specified storage array used as a snapshot host.
Syntax
[failover-peer] storage protection storage-array remove host <hostname>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<hostname>
Hostname of the storage array.
Example
amnesiac (config) # storage protection storage-array remove host sf-vva14
Product
SteelFusion Core
Related Commands
show storage protection storage-array (Hyper-V mode), storage protection storage-array add, storage protection storage-array modify
storage protection test integrated delete serial
Test deletes a LUN snapshot without changing the current configuration.
Syntax
[failover-peer] storage protection test integrated delete serial <lun-serial> snap-name <snap-name> [group <group-name>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
snap-name <snap-name>
Specifies the name of the snapshot.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage protection test integrated delete host kabar-vva35 serial ORIG12P5D snap-name snapshot1 private
 
Core_02 (config) # failover-peer storage protection test integrated delete host kabar-vva35 serial ORIG12P5D snap-name snapshot1 private
Product
SteelFusion Core
Related Commands
storage protection test integrated delete type
storage protection test integrated delete type
Test deletes a LUN snapshot, specified by array type, without changing the current configuration.
Syntax
[failover-peer] storage protection test integrated delete type <array-type> host <hostname> serial <lun-serial> snap-name <snap-name> user <username> password <password> [group <group-name>] [use-ssl]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array-type>
Storage array type:
•  emc_vnx - EMC VNX
•  dell_equallogic - Dell EqualLogic
•  netapp - NetApp
•  ibm_v7000 - IBM V7000
•  hp3par - HP3PAR
•  ibm_xiv - IBM XIV/Spectrum Accelerate
•  EMC-Unity
•  Nimble
•  Zadara
host <hostname>
Specifies the IP address or hostname of the storage array.
serial <lun-serial>
Specifies the snapshot LUN by the LUN serial number.
snap-name <snap-name>
Specifies the snapshot by name.
user <username>
Specifies a username for the snapshot credential.
password <password>
Specifies a password for the snapshot credential.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage protection test integrated delete type emc_vnx host kabar-vva35 serial ORIG12P5D snap-name snapshot1 user admincentral password adminpass367
 
Core_02 (config) # failover-peer storage protection test integrated delete type emc_vnx host kabar-vva35 serial ORIG12P5D snap-name snapshot1 user admincentral password adminpass367
Product
SteelFusion Core
Related Commands
storage protection test integrated delete serial
storage protection test integrated expose serial
Test creates a clone LUN out of a snapshot and exposes it to initiators without changing the current configuration.
Syntax
[failover-peer] storage protection test integrated expose serial <lun-serial> snap-name <snap-name> [group <group-name>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
snap-name <snap-name>
Specifies the name of the snapshot.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage protection test integrated expose serial CLONE12P5D snap-name snapshot1
 
Core_02 (config) # failover-peer storage protection test integrated expose serial CLONE12P5D snap-name snapshot1
Product
SteelFusion Core
Related Commands
storage protection test integrated expose type
storage protection test integrated expose type
Test creates a clone LUN out of a snapshot, specified by array type, without changing the current configuration.
Syntax
[failover-peer] storage protection test integrated expose type <array-type> host <hostname> serial <lun-serial> snap-name <snap-name> user <username> password <password> [group <group-name>] [use-ssl]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array-type>
Storage array type:
•  emc_vnx - EMC VNX
•  dell_equallogic - Dell EqualLogic
•  netapp - NetApp
•  ibm_v7000 - IBM V7000
•  hp3par - HP3PAR
•  ibm_xiv - IBM XIV/Spectrum Accelerate
•  EMC-Unity
•  Nimble
•  Zadara
host <hostname>
Specifies the IP address or hostname of the storage array.
serial <lun-serial>
Specifies the snapshot LUN by the LUN serial number.
snap-name <snap-name>
Specifies the name of the snapshot.
user <username>
Specifies a username for the snapshot credential.
password <password>
Specifies a password for the snapshot credential.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage protection test integrated expose type netapp host kabar-vva35 serial CLONE12P5D snap-name snapshot1 user admincentral password adminpass367 use-ssl
 
Core_02 (config) # failover-peer storage protection test integrated expose type netapp host kabar-vva35 serial CLONE12P5D snap-name snapshot1 user admincentral password adminpass367 use-ssl
Product
SteelFusion Core
Related Commands
storage protection test integrated expose serial
storage protection test integrated proxy-backup serial
Test runs a proxy backup test.
Syntax
[failover-peer] storage protection test integrated proxy-backup serial <lun-serial>
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
The proxy backup feature of Core enables backup integration directly from the data center. Core clones the snapshot specified for data protection and mounts the cloned LUN on the proxy server. The backup software then communicates with the proxy server to perform the backup.
Example
Core_01 (config) # storage protection test integrated proxy-backup serial ORIG12P5D
 
Core_02 (config) # failover-peer storage protection test integrated proxy-backup serial ORIG12P5D
Product
SteelFusion Core
Related Commands
storage protection test integrated delete serial storage protection test integrated expose serial, storage protection test integrated take serial, storage protection test integrated un-expose serial
storage protection test integrated take serial
Test creates a LUN snapshot without changing the current configuration.
Syntax
[failover-peer] storage protection test integrated take serial <lun-serial> [group <group-name>] [ snap-name <snap-name>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
snap-name <snap-name>
Specifies the name of the snapshot.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage protection test integrated take serial ORIG12P5D
 
Core_02 (config) # failover-peer storage protection test integrated take serial ORIG12P5D
Product
SteelFusion Core
Related Commands
storage protection test integrated take type
storage protection test integrated take type
Test creates a LUN snapshot, specified by array type, without changing the current configuration.
Syntax
[failover-peer] storage protection test integrated take type <array-type> host <hostname> serial <lun-serial> user <username> password <password> [group <group-name>] [ snap-name <snap-name>] [use-ssl]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array-type>
Storage array type:
•  emc_vnx - EMC VNX
•  dell_equallogic - Dell EqualLogic
•  netapp - NetApp
•  ibm_v7000 - IBM V7000
•  hp3par - HP3PAR
•  ibm_xiv - IBM XIV/Spectrum Accelerate
•  EMC-Unity
•  Nimble
•  Zadara
host <hostname>
Specifies the hostname of the storage array.
serial <lun-serial>
Specifies the snapshot LUN by the LUN serial number.
user <username>
Specifies a valid username for the snapshot credential.
password <password>
Specifies a valid password for the snapshot credential.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
snap-name <snap-name>
Specifies the name of the snapshot.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage protection test integrated take type vnx host kabar-vva35 serial ORIG12P5D user admincentral password adminpass367
 
Core_02 (config) # failover-peer storage protection test integrated take type vnx host kabar-vva35 serial ORIG12P5D user admincentral password adminpass367
Product
SteelFusion Core
Related Commands
storage protection test integrated take serial
storage protection test integrated un-expose serial
Test deletes the cloned LUN, which was created from the snapshot, without changing the current configuration.
Syntax
[failover-peer] storage protection test integrated un-expose serial <lun-serial> snap-lun-serial <snap-lun-serial> [group <group-name>]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<lun-serial>
LUN serial number.
snap-lun-serial <snap-lun-serial>
Specifies the serial number of the cloned LUN to be deleted.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage protection test integrated un-expose serial CLONE12P5D
 
Core_02 (config) # failover-peer storage protection test integrated un-expose serial CLONE12P5D
Product
SteelFusion Core
Related Commands
storage protection test integrated un-expose type
storage protection test integrated un-expose type
Test deletes the cloned LUN, specified by the array type, without changing the current configuration.
Syntax
[failover-peer] storage protection test integrated un-expose type <array-type> host <hostname> serial <lun-serial> snap-lun-serial <snap-lun-serial> user <username> password <password> [group <group-name>] [use-ssl]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<array-type>
Storage array type:
•  emc_vnx - EMC VNX
•  dell_equallogic - Dell EqualLogic
•  netapp - NetApp
•  ibm_v7000 - IBM V7000
•  hp3par - HP3PAR
•  ibm_xiv - IBM XIV/Spectrum Accelerate
•  EMC-Unity
•  Nimble
•  Zadara
host <hostname>
Specifies the hostname of the storage array.
serial <lun-serial>
Specifies the locally assigned LUN serial number.
snap-lun-serial <snap-lun-serial>
Specifies the snapshot LUN by the LUN serial number.
group <group-name>
Specifies the group name as follows depending on your configuration:
•  NetApp storage arrays - Initiator group name.
•  IBM - Host, which is a collection of initiators.
use-ssl
For NetApp storage arrays, uses HTTPS to dport=443.
Usage
All test commands enable you to test different snapshot configurations without affecting your configuration.
Example
Core_01 (config) # storage protection test integrated un-expose type emc_vnx host kabar-vva35 serial CLONE12P5D snap-lun-serial CLONE153xD user admincentral password adminpass367
 
Core_02 (config) # failover-peer storage protection test integrated un-expose type emc_vnx host kabar-vva35 serial CLONE12P5D snap-lun-serial CLONE153xD user admincentral password adminpass367
Product
SteelFusion Core
Related Commands
storage protection test integrated un-expose serial
storage server add (Hyper-V mode)
Adds an Edge server.
Syntax
[failover-peer] storage server add <server-id > edge-id <edge-id> hostname <hostname> type {hyperv_server | windows_server}
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<server-id>
Server identifier. To view existing servers, run the show storage server all command.
edge-id <edge-id>
Specifies the identifier of the Edge appliance. Edge identifiers are case sensitive.
hostname <hostname>
Specifies the hostname.
type
Specifies the server type.
•  hyperv_server - Microsoft Hyper-V server.
•  windows_server - Microsoft Windows server.
Usage
The typical workflow for setting up backup follows:
1. Use the storage server add (Hyper-V mode) command to add an Edge server.
2. Use the storage protection backup proxy add command to add the backup proxy.
3. Use the storage protection backup policy add command to configure the backup policy.
4. Use the storage protection backup group add command to add the backup group.
Any virtual machines are automatically protected when a server is added to a policy.
Example
amnesiac (config) # storage server add sf-shxxx-server edge-id edge-xxx hostname sf-rb335 type hyperv_server
Product
SteelFusion Core
Related Commands
show storage server, storage server modify (Hyper-V mode), storage server remove
storage server modify (Hyper-V mode)
Modifies the Edge server settings.
Syntax
[failover-peer] storage server modify <server-id > [edge-id <edge-id>] [hostname <hostname>] [force]
Parameters
failover-peer
Performs the command on the failover peer of the current appliance. If the failover peer is unavailable, the changed configuration is automatically applied when the appliance returns to service.
You can run failover-peer commands only on a Core appliance in ActiveSolo failover state.
<server-id>
Server identifier.
edge-id <edge-id>
Specifies the identifier of the Edge appliance.
hostname <hostname>
Specifies the hostname.
force
Forces the changes in the Edge server settings.
Example
amnesiac (config) # storage server modify sf-shxxx-server hostname sf-rb335
Product
SteelFusion Core
Related Commands
show storage server, storage server add (Hyper-V mode), storage server remove
SteelFusion Edge commands (both modes)
This section describes the Edge system commands. You can use the command line to perform basic configuration tasks, display configuration information, and check status. It includes the following information:
•  Hypervisor commands
•  Storage commands
Hypervisor commands
The hypervisor is included in the SteelFusion Edge system installation and does not require a separate download or license. In SteelFusion Edge 4.2 and later (and starting in SteelFusion Edge 5.0 for NFS), RiOS and ESXi versions are decoupled—you can upgrade the hypervisor independently from the RiOS software.
The hypervisor uses ESXi 6.0 Patch 6 as the virtualization platform and it is preloaded in the Edge software image. You can optionally choose other ESXi versions using the hypervisor installer or hypervisor install commands.
You set up and manage the hypervisor through the management console or command-line interface; you set up and configure virtual machines through the VMware vSphere Client or vCenter.
You must install the VMware vSphere Hypervisor Client, which enables monitoring and management of a single instance of the ESX or ESXi server. You can download the vSphere applications from the VMware website, or you can download the vSphere Client from the hypervisor host.
For file mode (NFS), before installing the hypervisor, you must configure and connect the Edge to the SteelFusion Core and set up the Edge virtual IP interface. A Core allows you to access remote storage at your data center and make that storage available to your hypervisor.
For file mode, only exports mapped to the Edge and configured with access to “everyone” or VSP access will be installed by the hypervisor installation. To determine VSP access, the VSP service scans the ESXi hypervisor for all IP addresses to be given access to the export.
See the SteelFusion Edge Management Console User Guide for more information.
Note: Hypervisor and virtualization features are not available on the Virtual SteelFusion Edge.
clear hypervisor hardware error-log
Clears the hypervisor Intelligent Platform Management Interface (IPMI) System Event Log (SEL).
Syntax
clear hypervisor hardware error-log
Parameters
None
Usage
The amber LED light stops blinking on the system when you enter this command.
Example
Edge1 # clear hypervisor hardware error-log
Product
SteelFusion Edge
Related Commands
show hypervisor hardware error-log
hypervisor check upgrades
Checks for available hypervisor upgrades for the system.
Syntax
hypervisor check upgrades
Parameters
None
Usage
In SteelFusion Edge 4.2 or later, you can upgrade ESXi and RiOS versions independently. A RiOS upgrade does not automatically upgrade the hypervisor and a hypervisor upgrade does not change the RiOS version. RiOS can support multiple ESXi versions.
For detailed information about upgrading and installing an image see the SteelFusion Edge Management Console User Guide and SteelFusion Edge Installation and Configuration Guide.
Example
Edge1 # hypervisor check upgrades
% Unable to obtain support update for 4.2.0-mainline from support site. Entitlement failure
Product
SteelFusion Edge
Related Commands
hypervisor upgrade, show hypervisor support-matrix, show hypervisor version
hypervisor console
Allows access to the hypervisor serial console.
Syntax
hypervisor console
Parameters
None
Usage
This command exposes the hypervisor serial console through an internal serial-over-LAN to hypervisor baseboard management controller (BMC). By observing the serial console activity, you can detect errors in the hypervisor installation. The escape sequence for this command is the tilde character (~).
Example
Edge1 (config) # hypervisor console
      VMware ESXi 6.0.0 (VMKernel Release Build 6921384) x
x x
x Riverbed SteelFusion Edge x
x x
x Intel(R) Xeon(R) CPU E5-2609 v2 @ 2.50GHz x
x 48 GiB Memory x
x x
x x
x Download tools to manage this host from: x
x http://machine-edgeXXX-vsp1/ x
x http://10.X.X.X/ (DHCP)   x
x http://[fe80::20e:b6ff:febe:fe05]/ (STATIC) x
x x
x x
x x
x <F2> Customize System/View Logs <F12> Shut Down/Restart
Product
SteelFusion Edge
Related Topic
Displaying hypervisor information
hypervisor image delete
Deletes a hypervisor image from the image vault.
Syntax
hypervisor image delete <filename>
Parameters
<filename>
Hypervisor image filename to delete.
Example
Edge1 (config)# hypervisor image delete esxi.6.0.0-3.79.6921384.iso
Product
SteelFusion Edge
Related Commands
show hypervisor image, show hypervisor images
hypervisor image rename
Renames a hypervisor image to a new name.
Syntax
hypervisor image rename <filename> new-name <new-filename>
Parameters
<filename>
Hypervisor image filename to rename.
new-name <new-filename>
Specifies the new hypervisor image filename.
Usage
The default hypervisor image name is hyp_image.img.iso. If you will be adding more than one image, we recommend that you specify a unique name for each image so it does not get overwritten.
Example
Edge1 # hypervisor image rename esxi.6.0.0-3.79.6921384.iso new-name mybranch2.iso
Product
SteelFusion Edge
Related Commands
show hypervisor image, show hypervisor images
hypervisor image-fetch
Configures the settings to fetch a hypervisor image.
Syntax
hypervisor image-fetch {remote <url> | version <version>} [filename <filename>]
Parameters
remote <url>
Fetches a remote hypervisor image. Specify the protocol (either http or https), authentication credentials, and the location from which to upload the image.
For example:
http://<username>:<password>@<hostname>/<path/filename>
version <version>
Downloads the specified version of the hypervisor image from the Riverbed Support site.
filename <filename>
Specifies the local path for the hypervisor image. Browse your file system and select the software image.
Usage
You can download the hypervisor image using a remote URL or download from the Riverbed Support site to store in the hypervisor image vault. These images can then be used to reinstall or upgrade the hypervisor.
For detailed information about upgrading and installing an image, see the SteelFusion Edge Management Console User Guide and SteelFusion Edge Installation and Configuration Guide.
Example
Edge1 # hypervisor image-fetch version 6.0.0-1.17.3029758
Product
SteelFusion Edge
Related Commands
hypervisor install, hypervisor upgrade, show hypervisor image, show hypervisor images
hypervisor initialize
Initializes the hypervisor to the default factory settings of the current installation of RiOS Edge software.
Syntax
hypervisor initialize [confirm]
Parameters
confirm
Confirms that you want to initialize the hypervisor to the default factory settings.
Usage
The Edge appliance ships with a hypervisor that is initialized and ready to install. ESXi is preinstalled and already deployed on the hypervisor.
Reinitializing is a destructive operation that restores the hypervisor to the default factory settings. Reinitialize with caution and only to fix critical virtualization errors.
Example
Edge1 (config) # hypervisor initialize
% Hypervisor is already installed. Reinitialization will restore hypervisor to the factory default settings. If you wish to proceed, use the command 'hypervisor initialize confirm'.
Product
SteelFusion Edge
Related Commands
hypervisor reinstall, show virtualization
hypervisor install
Installs the hypervisor configuration settings.
Syntax
hypervisor install password <password>
Parameters
password <password>
Specifies the hypervisor root password.
Usage
All the hypervisor install configuration commands are static and are not applied until this command is entered.
The hypervisor password complexity has changed in ESXi 6.0. Passwords that were valid for 5.x may not be permitted in 6.0. However, if you upgrade from ESXi 5.x to 6.x, your password will be saved. For details on this password policy change, see:
https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUID-DC96FFDB-F5F2-43EC-8C73-05ACDAE6BE43.html.
New passwords or a reinstall must satisfy the new password rules.
Example
Edge1 (config) # hypervisor install password xQaTEhb!
Successfully installed hypervisor
Product
SteelFusion Edge
Related Command
hypervisor reinstall
hypervisor install-config hostname
Configures the hypervisor hostname.
Syntax
[no] hypervisor install-config hostname <hostname>
Parameters
<hostname>
Hypervisor hostname.
Usage
The hostname maps to the IP address of the hypervisor and is used to identify the hypervisor on the network.
This command changes the hostname. If the hostname does not match this configuration, check that the host is not acquiring its name from a DNS server.
Example
Edge1 (config) # hypervisor install-config hostname vSphere-host
Product
SteelFusion Edge
Related Command
show hypervisor install-config
hypervisor install-config license key
Configures a hypervisor custom license key.
Syntax
[no] hypervisor install-config license key <license-key>
Parameters
<license-key>
Hypervisor license key.
Usage
Use this command to override the Riverbed hypervisor license and install a custom license key.
The Edge appliance ships with a Riverbed VMware vSphere license, VSPESXI, that enables basic hypervisor functions without support for more advanced vSphere features such as vCenter, vMotion, or high availability. If you need additional features beyond what the embedded VSPESXI level licensing provides, you must purchase a license upgrade through your VMware reseller.
Example
Edge1 (config) # hypervisor install-config license key 0H44L-37J51-37Y40-05A2H-CJTKH
Product
SteelFusion Edge
Related Commands
hypervisor license restore, show hypervisor license
hypervisor install-config network dns
Configures the DNS settings for the hypervisor.
Syntax
[no] hypervisor install-config network dns {domain-name <hostname> | import-rios | name-server <ip-address>}
Parameters
domain-name <hostname>
Specifies the hypervisor DNS domain setting.
import-rios
Imports DNS settings from RiOS.
name-server <ip-address>
Specifies the IPv4 address or IPv6 name server address.
Usage
You can only configure the hypervisor DNS settings through the command-line interface.
Example
Edge1 (config) # hypervisor install-config network dns import-rios
Product
SteelFusion Edge
Related Command
show hypervisor installed
hypervisor install-config network nic
Configures the hypervisor NIC settings.
Syntax
[no] hypervisor install-config network nic <nic> speed <speed> duplex <duplex>
Parameters
<nic>
Hypervisor NIC interfaces with onboard uplinks (vmnicx) to the vSwitch. Uplinks serve as bridges between physical and virtual networks. The number of uplinks depends on the appliance model.
The ports are labeled:
•  gbe0_0 (vmnicx)
•  gbe0_1 (vmnicx)
•  gbe0_2 (vmnicx)
•  gbe0_3 (vmnicx)
Use these interfaces to connect VMs to any LAN switch connected to an ESXi host.
speed <speed>
Configures the hypervisor NIC speed.
duplex <duplex>
Specifies the duplex setting: auto, full, or half. The default value is auto.
Example
Edge1 (config) # hypervisor install-config network nic gbe0_0 speed auto duplex auto
Product
SteelFusion Edge
Related Command
show hypervisor installed
hypervisor install-config network route ipv4
Configures the IPv4 network route settings for the hypervisor.
Syntax
[no] hypervisor install-config network route ipv4 {default-gw <gateway-ipv4-address> | ipv4-prefix <ipv4-prefix> gateway <ipv4-address>}
Parameters
default-gw <gateway-ipv4-address>
Specifies the hypervisor IPv4 default gateway.
The default gateways are used by the hypervisor to send packets outside the local network.
ipv4-prefix <ipv4-prefix>
Specifies the IPv4 route prefix.
gateway <ipv4-address>
Specifies the IPv4 address of the route gateway.
Usage
You must configure the default gateway for the hypervisor if you want it to route outside the network. The no command option clears the hypervisor IPv4 network route settings.
Example
Edge1 (config) # hypervisor install-config network route ipv4 default-gw 10.5.16.233
Product
SteelFusion Edge
Related Command
show hypervisor installed
hypervisor install-config network route ipv6
Configures the IPv6 network route settings for the hypervisor.
Syntax
[no] hypervisor install-config network route ipv6 {default-gw <gateway-ipv6-address> | ipv6-prefix <ipv6-prefix> gateway <ipv6-address>}
Parameters
default-gw <gateway-ipv6-address>
Specifies the hypervisor IPv6 default gateway.
The default gateways are used by the hypervisor to send packets outside the local network.
ipv6-prefix <ipv6-prefix>
Specifies the IPv6 route prefix.
gateway <ipv6-address>
Specifies the IPv6 address of the route gateway.
Usage
You must configure the default gateway for the hypervisor if you want it to route outside the network. The no command option clears the hypervisor IPv6 network route settings.
Example
Edge1 (config) # hypervisor install-config network route ipv6 default-gw 2001:38dc:52::1/64
Product
SteelFusion Edge
Related Command
show hypervisor installed
hypervisor install-config network use-auto-config
Configures the RiOS software to use the network automatic configuration settings.
Syntax
[no] hypervisor install-config network use-auto-config [confirm]
Parameters
confirm
Confirms that you want to use the automatic network configuration settings.
Usage
This command defaults to the same network settings configured by the hypervisor installer. By default, the installer:
•  creates one vSwitch called vSwitch0.
•  attaches all onboard hypervisor NIC uplinks to the vSwitch (the number of uplinks depends on the appliance model), but excludes add-on NICs for the hypervisor node. You can configure add-on hypervisor NICs for the hypervisor node through vSphere.
•  creates one VMKernel port group named Management Network.
•  creates one VM port group called VM Network.
•  enables DHCP for IPv4 addressing and tagged with management traffic.
The no command option allows you to configure the network settings manually. The show hypervisor install-config network use-auto-config command shows whether or not the hypervisor is using auto configuration.
For more information about the hypervisor installer, see the SteelFusion Edge Management Console User Guide.
Example
Edge1 (config) # hypervisor install-config network use-auto-config
% Choosing auto configuration will overwrite all existing networking configurations.
 
Edge1 (config) # hypervisor install-config network use-auto-config confirm
Product
SteelFusion Edge
Related Command
show hypervisor install-config network
hypervisor install-config network vswitch uplink
Configures the active uplinks for the vSwitch.
Syntax
[no] hypervisor install-config network vswitch <vswitch-name> [mtu <bytes>] [max-ports <number-of-ports>] uplink <active-uplinks>
Parameters
<vswitch-name>
Name of the vSwitch.
Enclose the name in quotation marks if it contains spaces: for example, "vSwitch 1".
mtu <bytes>
Specifies the vSwitch maximum transmission unit in bytes. The valid range is from 1280 to 9000.
max-ports <number-of-ports>
Specifies the vSwitch maximum number of ports. The range is from 1 to 1536.
<active-uplinks>
Active uplinks for this vSwitch. Use a comma separated list enclosed in quotation marks for multiple uplinks: for example, "uplink1, uplink2, ...<uplinkN>".
Usage
The SteelFusion Edge ships with ESXi preinstalled and a single internal vSwitch (rvbd_vswitch). Do not modify or delete this virtual switch.
By "teaming" multiple uplinks to a single vSwitch, you add redundancy and bandwidth to your network. You can verify your configuration through vSphere and vCenter.
Example
Edge1 (config) # hypervisor install-config network vswitch "vswitch 2" mtu 4000 uplink "gbe0_0, gbe0_1, gbe0_2"
Product
SteelFusion Edge
Related Command
show hypervisor installed
hypervisor install-config network vswitch vm-port
Configures the hypervisor vSwitch settings for the VM port group.
Syntax
[no] hypervisor install-config network vswitch <vswitch-name> [mtu <bytes>] [max-ports <number-of-ports>] vm-port <portgroup-name> [vm-vlan-id <vlan-id]
Parameters
<vswitch-name>
Name of the vSwitch.
Enclose the name in quotation marks if it contains spaces: for example, "vSwitch 1".
mtu <bytes>
Specifies the vSwitch maximum transmission unit in bytes. The valid range is from 1280 to 9000.
max-ports <number-of-ports>
Specifies the vSwitch maximum number of ports. The range is from 1 to 1536.
<portgroup-name>
VM port group name on the vSwitch.
Enclose the VM port group name in quotation marks if it contains spaces: for example, "portgroup 1".
vm-vlan-id <vlan-id>
Specifies the VM port group VLAN ID. The range is from 0 to 4095.
Usage
ESXi and a single vSwitch (virtual switch) are preinstalled on the SteelFusion Edge. This is an internal switch used for communication within the appliance. Do not modify or delete this virtual switch.
Example
Edge1 (config) # hypervisor install-config network vswitch "vswitch 2" mtu 4000 uplink "uplink1, uplink2, uplink3"
Product
SteelFusion Edge
Related Command
show hypervisor installed
hypervisor install-config network vswitch vmk-port ipv4-dhcp
Configures the hypervisor vSwitch settings for the VM kernel (VMK) port group and enables IPv4 address assignment through DHCP.
Syntax
[no] hypervisor install-config network vswitch <vswitch-name> [mtu <bytes>] [max-ports <number-of-ports>] vmk-port <portgroup-name> [vmk-mtu <bytes>] [vmk-tag <tag>] [vmk-vlan-id <vlan-id>] ipv4-dhcp [ipv4-dhcp-dns]
Parameters
<vswitch-name>
Name of the vSwitch.
Enclose the name in quotation marks if it contains spaces: for example, "vSwitch 1".
mtu <bytes>
Specifies the vSwitch maximum transmission unit in bytes. The valid range is from 1280 to 9000.
max-ports <number-of-ports>
Specifies the vSwitch maximum number of ports. The range is from 1 to 1536.
<portgroup-name>
Name of the VMK port group on the vSwitch.
Enclose the VMK port group name in quotation marks if it contains spaces: for example, "portgroup 1".
vmk-mtu <bytes>
Specifies the VMK port group MTU.
vmk-tag <tag>
Tags with any of the following VMK port group vSphere traffic types:
•  Management
•  VMotion
•  faultToleranceLogging
•  vSphereReplication
Use a comma-separated list enclosed in quotation marks for multiple tags: for example, "tag1, tag2, ...<tagN>".
vmk-vlan-id <vlan-id>
Specifies the VMK port group VLAN ID. The range is from 0 to 4095; 0 means none and 4095 means all.
ipv4-dhcp-dns
Dynamically obtains IPv4 network settings from a DNS server using dynamic DNS.
Usage
ESXi and a single vSwitch (virtual switch) are preinstalled on the SteelFusion Edge. The vSwitch has a kernel port and a virtual machine port. This is an internal switch used for communication within the appliance. Do not modify or delete this virtual switch.
Example
Edge1 (config) # hypervisor install-config network vswitch test vmk-port test_vmk vmk-tag Management
ipv4-dhcp
Product
SteelFusion Edge
Related Command
show hypervisor installed
hypervisor install-config network vswitch vmk-port ipv4-ip
Configures the hypervisor vSwitch settings for the VM kernel port group and configures a static IPv4 address.
Syntax
[no] hypervisor install-config network vswitch <vswitch-name> [mtu <bytes>] [max-ports <number-of-ports>] vmk-port <portgroup-name> [vmk-mtu <bytes>] [vmk-tag <tag>] [vmk-vlan-id <vlan-id>] ipv4-ip <ipv4-address> ipv4-netmask <ipv4-netmask>
Parameters
<vswitch-name>
Name of the vSwitch.
Enclose the name in quotation marks if it contains spaces: for example, "vSwitch 1".
mtu <bytes>
Specifies the vSwitch maximum transmission unit in bytes. The valid range is from 1280 to 9000.
max-ports <number-of-ports>
Specifies the vSwitch maximum number of ports. The range is from 1 to 1536.
<portgroup-name>
Name of the VMK port group on the vSwitch.
Enclose the VMK port group name in quotes if it contains spaces: for example, "portgroup 1".
vmk-mtu <bytes>
Specifies the VMK port group MTU.
vmk-tag <tag>
Tags with any of the following VMK port group vSphere traffic types:
•  Management
•  VMotion
•  faultToleranceLogging
•  vSphereReplication
Use a comma separated list enclosed in quotation marks for multiple tags: for example, "tag1, tag2, ...<tagN>".
vmk-vlan-id <vlan-id>
Specifies the VMK port group VLAN ID. The range is from 0 to 4095; 0 means none and 4095 means all.
<ipv4-address> ipv4-netmask <ipv4-netmask>
Specifies the IPv4 static address and static IPv4 netmask for the VMK port group.
Usage
ESXi and a single vSwitch (virtual switch) are preinstalled on the SteelFusion Edge. The vSwitch has a kernel port and a virtual machine port. This is an internal switch used for communication within the appliance. Do not modify or delete this virtual switch.
Example
Edge1 (config) # hypervisor install-config network vswitch test vmk-port test_vmk vmk-tag Management ipv4-ip 10.24.24.1 ipv4-netmask /24
Product
SteelFusion Edge
Related Command
show hypervisor installed
hypervisor install-config network vswitch vmk-port ipv6-dhcp
Configures the hypervisor vSwitch settings for the VM kernel port group and enables IPv6 address assignment through DHCP.
Syntax
[no] hypervisor install-config network vswitch <vswitch-name> [mtu <bytes>] [max-ports <number-of-ports>] vmk-port <portgroup-name> [vmk-mtu <bytes>] [vmk-tag <tag>] [vmk-vlan-id <vlan-id>] ipv6-dhcp [ipv6-dhcp-dns]
Parameters
<vswitch-name>
Name of the vSwitch.
Enclose the name in quotation marks if it contains spaces: for example, "vSwitch 1".
mtu <bytes>
Specifies the vSwitch maximum transmission unit in bytes. The valid range is from 1280 to 9000.
max-ports <number-of-ports>
Specifies the vSwitch maximum number of ports. The range is from 1 to 1536.
<portgroup-name>
Name of the VMK port group on the vSwitch.
Enclose the VMK port group name in quotation marks if it contains spaces: for example, "portgroup 1".
vmk-mtu <bytes>
Specifies the VMK port group MTU.
vmk-tag <tag>
Tags with any of the following VMK port group vSphere traffic types:
•  Management
•  VMotion
•  faultToleranceLogging
•  vSphereReplication
Use a comma-separated list enclosed in quotation marks for multiple tags: for example, "tag1, tag2, ...<tagN>".
vmk-vlan-id <vlan-id>
Specifies the VMK port group VLAN ID. The range is from 0 to 4095; 0 means none and 4095 means all.
ipv6-dhcp-dns
Dynamically obtains IPv6 network settings from a DNS server using dynamic DNS.
Usage
ESXi and a single vSwitch (virtual switch) are preinstalled on the SteelFusion Edge. The vSwitch has a kernel port and a virtual machine port. This is an internal switch used for communication within the appliance. Do not modify or delete this virtual switch.
Example
Edge1 (config) # hypervisor install-config network vswitch test vmk-port test_vmk vmk-tag Management
ipv6-dhcp
Product
SteelFusion Edge
Related Command
show hypervisor installed
hypervisor install-config network vswitch vmk-port ipv6-ip
Configures the hypervisor vSwitch settings for the VM kernel port group and configures a static IPv6 address.
Syntax
[no] hypervisor install-config network vswitch <vswitch-name> [mtu <bytes>] [max-ports <number-of-ports>] vmk-port <portgroup-name> [vmk-mtu <bytes>] [vmk-tag <tag>] [vmk-vlan-id <vlan-id>] ipv6-ip <ipv6-address> ipv6-masklen <ipv6-netmask>
Parameters
<vswitch-name>
Name of the vSwitch.
Enclose the name in quotation marks if it contains spaces: for example, "vSwitch 1".
mtu <bytes>
Specifies the vSwitch maximum transmission unit in bytes. The valid range is from 1280 to 9000.
max-ports <number-of-ports>
Specifies the vSwitch maximum number of ports. The range is from 1 to 1536.
<portgroup-name>
Name of the VMK port group on the vSwitch.
Enclose the VMK port group name in quotes if it contains spaces: for example, "portgroup 1".
vmk-mtu <bytes>
Specifies the VMK port group MTU.
vmk-tag <tag>
Tags with any of the following VMK port group vSphere traffic types:
•  Management
•  VMotion
•  faultToleranceLogging
•  vSphereReplication
Use a comma-separated list enclosed in quotes for multiple tags: for example, "tag1, tag2, ...<tagN>".
vmk-vlan-id <vlan-id>
Specifies the VMK port group VLAN id. The range is from 0 to 4095; 0 means none and 4095 means all.
<ipv6-address> ipv6-masklen <ipv6-netmask>
Specifies the IPv6 static address and static IPv6 netmask for the VMK port group.
Usage
ESXi and a single vSwitch (virtual switch) are preinstalled on the Edge. The vSwitch has a kernel port and a virtual machine port. This is an internal switch used for communication within the appliance. Do not modify or delete this virtual switch.
Example
Edge1 (config) # hypervisor install-config network vswitch test vmk-port test_vmk vmk-tag Management
ipv6-ip 2001:38dc:52::e9a4:c5:6282 ipv6-masklen /64
Product
SteelFusion Edge
Related Command
show hypervisor installed
hypervisor install-config network vswitch vmk-port ipv6-router-adv
Enables IPv6 router advertisement for the VMK port group.
Syntax
[no] hypervisor install-config network vswitch <vswitch-name> [mtu <bytes>] [max-ports <number-of-ports>] vmk-port <portgroup-name> [vmk-mtu <bytes>] [vmk-tag <tag>] [vmk-vlan-id <vlan-id>] ipv6-router-adv
Parameters
<vswitch-name>
Name of the vSwitch.
Enclose the name in quotation marks if it contains spaces: for example, "vSwitch 1".
mtu <bytes>
Specifies the vSwitch maximum transmission unit in bytes. The valid range is from 1280 to 9000.
max-ports <number-of-ports>
Specifies the vSwitch maximum number of ports. The range is from 1 to 1536.
<portgroup-name>
Name of the VMK port group on the vSwitch.
Enclose the VMK port group name in quotation marks if it contains spaces: for example, "portgroup 1".
vmk-mtu <bytes>
Specifies the VMK port group MTU.
vmk-tag <tag>
Tags with any of the following VMK port group vSphere traffic types:
•  Management
•  VMotion
•  faultToleranceLogging
•  vSphereReplication
Use a comma-separated list enclosed in quotation marks for multiple tags: for example, "tag1, tag2, ...<tagN>".
vmk-vlan-id <vlan-id>
Specifies the VMK port group VLAN ID. The range is from 0 to 4095; 0 means none and 4095 means all.
Usage
ESXi and a single vSwitch (virtual switch) are preinstalled on the SteelFusion Edge. The vSwitch has a kernel port and a virtual machine port. This is an internal switch used for communication within the appliance. Do not modify or delete this virtual switch.
Example
Edge1 (config) # hypervisor install-config network vswitch test vmk-port test_vmk vmk-tag Management
ipv6-router-adv
Product
SteelFusion Edge
Related Command
show hypervisor install-config
hypervisor install-config ntp enable
Configures the hypervisor to use RiOS Network Time Protocol (NTP) settings.
Syntax
[no] hypervisor install-config ntp enable
Parameters
None
Usage
We strongly recommend using the RiOS NTP server settings to ensure consistent time synchronization between the RiOS software and your virtual machines. You can only configure these settings through the command-line interface.
The no command option resets the NTP server settings to the default.
Example
Edge1 (config) # hypervisor install-config ntp enable
Product
SteelFusion Edge
Related Command
show hypervisor install-config
hypervisor install-config storage core-managed
Configures the hypervisor storage settings when managed by the Core.
Syntax
[no] hypervisor install-config storage core-managed lun <lun-alias>
Parameters
lun <lun-alias>
Configures the core-managed LUN to be used by the hypervisor during the next installation.
Usage
All hypervisor storage is provided by RiOS through iSCSI using Riverbed BlockStream technology. A hypervisor has no local disks for storage. Edge supports two storage operating modes: direct attached storage and storage managed by the Core. Use this command if you are using the Core to manage storage at your data center. This command is only available when the BlockStream is managed by Core.
If the settings at the Core change between the time you run this command and when you run your install or reinstall, your results may be different than expected.
See the SteelFusion Core Management Console User Guide for more information about how to configure SteelFusion Core.
Note: This command is not supported on SteelFusion Edge in file mode (NFS).
Example
Edge1 (config) # hypervisor install-config storage core-managed lun lun1
Product
SteelFusion Edge
Related Command
show hypervisor install-config
hypervisor install-config storage direct-attached delete-existing
Deletes the existing directly attached LUNs from the Edge.
Syntax
[no] hypervisor install-config storage direct-attached delete-existing
Parameters
None
Usage
All hypervisor storage is provided by RiOS through iSCSI using Riverbed BlockStream technology. A hypervisor has no local disks for storage. Edge supports two storage operating modes: direct attached storage and storage managed by the Core. Direct attached storage is a single, pinned LUN exposed to the hypervisor over iSCSI without connecting to a Core. Use this command to delete the existing directly attached local LUN from the Edge.
Note: This command is not supported on SteelFusion Edge in file mode (NFS).
Example
Edge1 (config) # hypervisor install-config storage direct-attached delete-existing
Product
SteelFusion Edge
Related Command
show hypervisor install-config
hypervisor install-config storage direct-attached lun
Allocates an amount of direct attached storage to the hypervisor without connecting to the SteelFusion Core.
Syntax
[no] hypervisor install-config storage direct-attached lun percent-size <lun-size> datastore-name <datastore-name> vmfs <vmfs-version>
Parameters
percent-size <lun-size>
Configures the hypervisor LUN size as a percentage of the total of the directly attached storage size. The default value is 50 percent.
datastore-name <datastore-name>
Specifies the name of the datastore. The default datastore name is rvbd_vsp_datastore.
vmfs <vmfs-version>
Specifies the version of the Virtual Machine File System (VMFS). The default VMFS version is 5. Currently, VMFS versions 3, 5, and 6 are supported.
Usage
All hypervisor storage is provided by RiOS through iSCSI using Riverbed BlockStream technology. A hypervisor has no local disks for storage. SteelFusion Edge supports two storage operating modes: direct attached storage and storage managed by the SteelFusion Core. As an alternative to using a SteelFusion Core for storage, you can create a local LUN on the Edge to be used as direct-attached storage by the hypervisor.
You can allocate 100 percent to the datastore, but to allow for future expansion, We recommend against using the entire amount. If you allocate 100 percent and then decide later to connect a Core to project remote LUNs, writes to remote LUNs could experience lower throughputs and low or no space conditions.
The SteelFusion Edge blockstore allocation changes dynamically depending on the amount of attached storage you specify. Direct attached storage is local to the SteelFusion Edge appliance and the data is not backed up.
Note: This command is not supported on SteelFusion Edge in file mode (NFS).
Example
Edge1 (config) # hypervisor install-config storage direct-attached lun percent-size 43 datastore-name jackandjill vmfs 5
Product
SteelFusion Edge
Related Command
show hypervisor install-config
hypervisor license restore
Restores the Riverbed hypervisor license.
Syntax
hypervisor license restore
Parameters
None
Usage
The Edge appliance ships with an embedded Riverbed-specific VMware ESXi vSphere Hypervisor license named VSPESXI. This license enables basic hypervisor functions such as monitoring and management of a single instance of ESXi or the ESXi server. However, this license does not support more advanced vSphere features such as vCenter, vMotion, or high availability.
Use this command to replace the existing license with the default VSPESXI license.
Example
Edge1 (config) # hypervisor license restore
Product
SteelFusion Edge
Related Command
hypervisor install-config hostname, show hypervisor license
hypervisor password
Updates the hypervisor root password.
Syntax
hypervisor password <password>
Parameters
<password>
Root password that is used to log in to the root user account of the hypervisor through vSphere or the vCenter client.
The password must meet the current vSphere password complexity requirements. Enclose the password in quotation marks if it contains spaces.
Usage
If you change a hypervisor password in vCenter or vSphere, you must change it on the SteelFusion Edge.
Hypervisor password complexity has changed in ESXi 6.0. Passwords that were valid for 5.x may not be permitted in 6.0. However, if you upgrade from 5.x to 6.x, your password will be saved. For details on this password policy change, see:
https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUID-DC96FFDB-F5F2-43EC-8C73-05ACDAE6BE43.html.
Example
Edge1 (config) # hypervisor password xQaT3#A
Product
SteelFusion Edge
Related Command
hypervisor reinstall
hypervisor reinstall
Reinstalls the hypervisor.
Syntax
hypervisor reinstall password [image-name <image-name>] <password>
Parameters
password <password>
Specifies the hypervisor root user account password.
This is the same password used to log in to the hypervisor through the vSphere and vCenter client.
Hypervisor password complexity has changed in ESXi 6.0. Passwords that were valid for 5.x may not be permitted in 6.0. However, if you upgrade from 5.x to 6.x, your password will be saved. For details on this password policy change, see:
https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUID-DC96FFDB-F5F2-43EC-8C73-05ACDAE6BE43.html.
image-name <image name>
Specifies the hypervisor image name that you want to reinstall.
confirm
Confirms that you want to reinstall the hypervisor.
Usage
Reinstallation consists of a reinitialization and installation in one step. The hypervisor reinstall command uses the most recently configured install-config settings during the reinstallation.
Example
Edge1 (config) # hypervisor reinstall password branch213
When you enter this command, the CLI returns the following alert:
WARNING: This will wipe out the current configuration, please backup any data if necessary. To proceed, use this command:
'hypervisor reinstall password <password> confirm'
Product
SteelFusion Edge
Related Commands
hypervisor initialize, hypervisor install
hypervisor restart
Restarts the hypervisor.
Syntax
hypervisor restart
Parameters
None
Usage
Before you run this command, ESXi should be in maintenance mode and all virtual machines shut down.
Example
Edge1 (config) # hypervisor restart
Product
SteelFusion Edge
Related Commands
hypervisor initialize, hypervisor install
hypervisor upgrade
Upgrades the hypervisor to the latest hypervisor image bundled with the installed RiOS Edge version.
Syntax
hypervisor upgrade [image-name <image-name>]
Parameters
image-name <image name>
Specifies the hypervisor image version name that you want to upgrade to.
confirm
Confirms that you want to upgrade the hypervisor.
Usage
In SteelFusion Edge 4.2 or later, you can upgrade the hypervisor independently from the RiOS Edge software. A RiOS upgrade does not automatically upgrade the hypervisor. You can also upgrade the hypervisor version without changing the RiOS version.
ESXi 6.0 Patch 6 is preloaded in the SteelFusion Edge software image and a fresh installation of RiOS initializes the hypervisor to this version.
After you install the hypervisor, you can upgrade to a later hypervisor image if one is available.
An upgrade does not require a restart of the appliance.
For detailed information about upgrading and installing an image see the SteelFusion Edge Management Console User Guide and SteelFusion Edge Installation and Configuration Guide.
Example
Edge1 (config) # hypervisor upgrade
Product
SteelFusion Edge
Related Commands
hypervisor initialize, hypervisor install, show hypervisor support-matrix, show hypervisor version
Storage commands
device-failover peer clear (Edge)
Clears the failover peer settings for the current SteelFusion Edge device.
Syntax
device-failover peer clear
Parameters
None
Example
Edge1 (config) # device-failover peer clear
Edge1 (config) # show device-failover
Product
SteelFusion Edge
Related Command
show device-failover (Edge)
device-failover peer set (Edge)
Specifies and sets the failover peer settings for the current Edge.
Syntax
device-failover peer set <serial-number> ip <ip-address> local-if <local-interface-name> additional-ip <additional-ip> local-if2 <local-interface-name2> edge-id <edge-id> [local-if-dc <local-interface-name>]
Parameters
<serial-number>
Serial number of the Edge active peer.
ip <ip-address>
Specifies the IP address of the Edge active peer appliance.
local-if <local-interface-name>
Specifies the local interface for the standby peer to connect to the active peer.
additional-ip <additional-ip>
Specifies the IP address of the Edge active peer, which is different from the first peer IP address specified by the ip <ip-address> parameter.
local-if2 <local-interface-name2>
Specifies the second local interface name for the standby peer to connect to the second IP address specified by the additional-ip <additional-ip> parameter.
edge-id <edge-id>
Specifies the self-identifier for the active peer. This value is case-sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
Both peer appliances must use the same self-identifier. In this case, you can use a value that represents the group of appliances.
local-if-dc <local-interface-name>
Specifies the local interface for the current appliance to use when connecting with the Core appliance.
Usage
This command configures the failover peer settings to provide high availability between SteelFusion Edge appliances. High availability enables you to configure two Edge appliances so that either one can fail without disrupting the service of the LUNs being provided by SteelFusion Core.
Example
Edge1 (config) # device-failover peer set DA3XS000085C5 ip 10.2.2.2 local-if primary additional-ip 10.3.2.2 local-if2 wan0_0 edge-id branch12
Product
SteelFusion Edge
Related Command
show device-failover (Edge)
storage backup trigger
Triggers the backup policy or backup server from the Edge appliance.
Syntax
storage backup trigger {policy <policy-id>} | server <server-name>}
Parameters
policy <policy-id>
Specifies the policy identifier.
server <server-name>
Specifies the server name.
Usage
The Edge keeps records of recent backup trigger operations that reach the Core. In addition, the Edge keeps a local record of up to three backup trigger operations that fail to reach the Core.
You can set the maximum number of backup operations that the Core maintains by using the storage backup group command. The default backup history number is 5.
Example
Edge (config) # storage backup trigger policy policy_1
Product
SteelFusion Edge
Related Commands
edge id prepop schedule modify, storage backup group modify, storage backup policy add
storage core add host
Configures the SteelFusion Core connection.
Syntax
storage core add host <hostname> edge-id <id> [local-interface <interface>]
Parameters
<hostname>
Hostname of the SteelFusion Core host device.
edge-id <id>
Specifies the self-identifier of the SteelFusion Core device. Edge identifiers are case sensitive.
local-interface <interface>
Specifies the local interface for the connection to the SteelFusion Core.
Usage
Use this command to specify and configure the connection to the intended SteelFusion Core host.
If you configure any direct attached storage to be used by the hypervisor before connecting to a Core, those LUNs will be converted to core-managed edge local LUNs once connected to a the Core.
Example
Edge1 (config) # storage core add host CoLo2 edge-id Branch1 local-interface aux
Product
SteelFusion Edge
Related Commands
show service storage, show storage core, storage core host local-interface, storage core remove
storage core host local-interface
Configures SteelFusion Core local interface connection settings.
Syntax
storage core host <hostname> local-interface {add <local-interface-name> | remove <local-interface-name>}
Parameters
<hostname>
Hostname of the SteelFusion Core host device.
add <local-interface-name>
Adds the local interface used to connect to the SteelFusion Core.
remove <local-interface-name>
Removes the local interface used to connect to the SteelFusion Core.
Example
Edge1 (config) # storage core host CoLo1 local-interface add primary
Product
SteelFusion Edge
Related Commands
show storage core, storage core add host, storage core remove
storage core host modify
Modifies the existing Core connection settings.
Syntax
storage core host <hostname> modify {port <port-number> | new-host <hostname>}
Parameters
<hostname>
Hostname of the Core host device.
port <port-number>
Specifies the port the Core device is to listen on.
new-host <hostname>
Specifies the new hostname of the Core host device.
Example
Edge1 (config) # storage core host CoLo2 modify new-host Calif2
Product
SteelFusion Edge
Related Commands
show storage core, storage core add host, storage core remove
storage core remove
Removes the connection to the specified SteelFusion Core host device.
Syntax
storage core remove host <hostname>
Parameters
host <hostname>
Hostname of the SteelFusion Core host device.
Usage
Before using this command, we strongly recommend that you take offline the LUNs associated with the Core host device.
Example
Edge1 (config) # storage core remove host CoLo2
Product
SteelFusion Edge
Related Commands
show service storage, show storage core
SteelFusion Edge iSCSI (block mode) commands
storage iscsi mpio interface (Edge)
Adds or removes the specified multipath I/O (MPIO) interface.
Syntax
storage iscsi mpio interface {add name <mpio-interface> | remove {name <mpio-interface> | all}}
Parameters
add name <mpio-interface>
Specifies an MPIO interface to add.
remove name <mpio-interface>
Removes an MPIO interface.
remove all
Removes all MPIO interfaces.
Usage
MPIO interfaces connect the Core appliance to the network and to the filer through multiple physical interfaces. These redundant connections help prevent loss of connectivity in the event of an interface, switch, cable, or other physical failure. The all keyword is only available on the Edge (not on the Core).
Example
Edge1 (config) # storage iscsi mpio interface add primary
Product
SteelFusion Edge
Related Command
show storage iscsi
storage lun activate
Activates the specified LUN.
Syntax
storage lun activate {alias <lun-alias> | serial <lun-serial>}
Parameters
alias <lun-alias>
Activates the LUN specified by the alias value number.
serial <lun-serial>
Activates the LUN specified by the serial number.
Usage
Use this command to activate a LUN that was previously deactivated because of low space in the SteelFusion Edge blockstore.
Example
Edge1 (config) # storage lun activate alias LUN2
Product
SteelFusion Edge
Related Command
show storage lun
storage lun snapshot create
Creates a storage snapshot on the specified LUN.
Syntax
storage lun {alias <alias> | serial <serial>} snapshot create [proxy-backup]
Parameters
alias <alias>
Specifies the alias of the LUN.
serial <serial>
Specifies the serial value of the LUN.
proxy-backup
Enables proxy backup for this private snapshot.
Usage
You configure the proxy backup for the specified LUN on the SteelFusion Core appliance. See the SteelFusion Design Guide and the SteelFusion Core Management Console User Guide for information about the types of snapshots supported.
Example
Edge1 (config) # storage lun alias LUN2 snapshot create
Product
SteelFusion Edge
Related Command
show storage lun
storage lun snapshot remove
Removes a storage snapshot on the specified LUN.
Syntax
storage lun {alias <alias> | serial <serial>} snapshot remove id <snapshot-id> [rm-proxy-backup]
Parameters
alias <alias>
Specifies the alias of the LUN.
serial <serial>
Specifies the serial value of the LUN.
id <snapshot-id>
Removes the private storage snapshot for the LUN as specified by the ID value.
rm-proxy-backup
Removes the proxy-backup for this private snapshot if it exists.
Usage
You configure the proxy backup for the specified LUN on the Core appliance. See the SteelFusion Design Guide and the SteelFusion Core Management Console User Guide for information about the types of snapshots supported.
Example
Edge1 (config) # storage lun alias LUN2 snapshot remove id 2
Product
SteelFusion Edge
Related Command
show storage lun
storage lun snapshot remove non-replicated
Removes all nonreplicated snapshots for the LUN.
Syntax
storage lun {alias <alias> | serial <serial>} snapshot remove non-replicated
Parameters
alias <alias>
Specifies the alias of the LUN. This is the alias of the parent LUN.
serial <serial>
Specifies the serial value of the LUN. This is the serial value of the parent LUN.
Usage
This command removes all nonreplicated snapshots on the SteelFusion Edge.
Example
Edge1 (config) # storage lun alias LUN2 snapshot remove non-replicated
Product
SteelFusion Edge
Related Command
show storage lun
SteelFusion Edge NFS (file mode) commands
device-failover peer set (Edge NFS)
Specifies and sets the failover peer settings for the current Edge.
Syntax
device-failover peer set <serial-number> ip <ip-address> local-if <local-interface-name> additional-ip <additional-ip> local-if2 <local-interface-name2> edge-id <edge-id> vip-interface <interface> [local-if-dc <local-interface-name>]
Parameters
<serial-number>
Serial number of the Edge active peer.
ip <ip-address>
Specifies the IP address of the Edge active peer appliance.
local-if <local-interface-name>
Specifies the local interface for the standby peer to connect to the active peer.
additional-ip <additional-ip>
Specifies the IP address of the Edge active peer, which is different from the first peer IP address specified by the ip <ip-address> parameter.
local-if2 <local-interface-name2>
Specifies the second local interface name for the standby peer to connect to the second IP address specified by the additional-ip <additional-ip> parameter.
edge-id <edge-id>
Specifies the self-identifier for the active peer. This value is case-sensitive and limited to the following characters: 0 to 9, a to z, A to Z, period (.), and hyphen (-).
Both peer appliances must use the same self-identifier. In this case, you can use a value that represents the group of appliances.
vip-interface <interface>
Physical interface on which the virtual IP (VIP) address is configured for reaching the Edge when it transitions to active.
The VIP is used by branch clients connected to the Edge to access NFS exports mapped to the Edge. The VIP interface can be any single data or base interface but not an in-path interface.
local-if-dc <local-interface-name>
Specifies the local interface for the current appliance to use when connecting with the Core appliance.
Usage
This command configures the failover peer settings to provide high availability between SteelFusion Edge appliances. High availability enables you to configure two Edge appliances so that either one can fail without disrupting the service of the exports being provided by SteelFusion Core.
At the branch location, because the Edge is the NFS file server, it is configured with a VIP address for the ESXi server(s) to access as NFS clients. The VIP requires an underlying network interface with a configured IP address on the same IP subnet. The underlying network interface must be reachable by the NFS clients requiring access to the file shares exported by the Edge.
Example
Edge1 (config) # device-failover peer set DA3XS000085C5 ip 10.2.2.2 local-if primary additional-ip 10.3.2.2 local-if2 wan0_0 edge-id branch12 vip-interface primary
Product
SteelFusion Edge
Related Command
show device-failover (Edge)
device-failover vip-interface
Configures a virtual IP interface for the failover configuration.
Syntax
device-failover vip-interface <interface>
Parameters
<interface>
Physical interface on which the virtual IP (VIP) is configured for reaching the Edge when it transitions to active.
The VIP is used by branch clients connected to the Edge to access NFS exports mapped to the Edge. The VIP interface can be any single data or base interface but not an in-path interface.
Usage
The Edge VIP must be configured when attaching a Core. It is the IP address that the branch ESXi clients use to access the NFS storage located on the Edge when mounting a datastore.
Example
Core_02 (config) # device-failover vip-interface eth0_1
Product
SteelFusion Edge
Related Commands
show device-failover (Core)
storage core add host (Edge NFS)
Configures the SteelFusion Core connection.
Syntax
storage core add host <hostname> edge-id <id> [local-interface <interface>] [vip-interface <interface>] [vip-address <vip-address>]
Parameters
<hostname>
Hostname of the SteelFusion Core host.
edge-id <id>
Specifies the self-identifier of the SteelFusion Core. Edge identifiers are case sensitive.
local-interface <interface>
Specifies the local interface for the connection to the SteelFusion Core.
vip-interface <interface>
Specifies the physical interface on which the virtual IP is configured for reaching the Edge when it transitions to active.
The VIP interface can be any single data or base interface but not an in-path interface.
vip-address <vip-address>
Specifies the virtual IP (VIP) address to configure on the VIP interface.
The VIP address is configured on the Edge. It is used by branch clients connected to the Edge to access the NFS exports mapped to the Edge.
Usage
Use this command to specify and configure the connection to the intended SteelFusion Core host.
If you configure any direct attached storage to be used by the hypervisor before connecting to a Core, those LUNs will be converted to core-managed edge local LUNs once connected to a the Core.
The Edge VIP must be configured when attaching to a Core in file mode. The VIP is the IP address that the branch ESXi clients use to access the NFS storage located on the Edge when mounting a datastore. The VIP is also important in high-availability configurations. See the SteelFusion Design Guide and SteelFusion Edge Management Console User Guide for more information.
Example
Edge1 (config) # storage core add host CoLo2 edge-id Branch1 local-interface aux vip-interface eth0_0 vip-address 10.2.2.2
Product
SteelFusion Edge
Related Commands
storage core host modify (Edge NFS), storage core remove (Edge NFS)
storage core host modify (Edge NFS)
Modifies the existing Core connection settings.
Syntax
storage core host <hostname> modify {port <port-number> | new-host <hostname> | vip-interface <interface> vip-address <vip-address>}
Parameters
<hostname>
Hostname of the Core host device.
port <port-number>
Specifies the port the Core device is to listen on.
new-host <hostname>
Specifies the new hostname of the Core host device.
vip-interface <interface>
Specifies the physical interface on which the virtual IP (VIP) address is configured for reaching the Edge when it transitions to active.
vip-address <vip-address>
Specifies the virtual IP (VIP) address to configure on the VIP interface.
The VIP address is configured on the Edge. It is used by branch clients connected to the Edge to access the NFS exports mapped to the Edge.
Example
Edge1 (config) # storage core host CoLo2 modify new-host Calif2 vip-interface aux vip-address 10.5.43.211
Product
SteelFusion Edge
Related Commands
show storage core, storage core add host (Edge NFS), storage core remove (Edge NFS)
storage core remove (Edge NFS)
Removes the connection to the specified SteelFusion Core host device.
Syntax
storage core remove host <hostname>
Parameters
host <hostname>
Hostname of the SteelFusion Core host device.
Usage
Before using this command, we strongly recommend that you take offline the exports associated with the Core host device.
Example
Edge1 (config) # storage core remove host CoLo2
Product
SteelFusion Edge
Related Commands
show service storage, show storage core
storage nfs export activate
Activates a deactivated NFS export on the Edge.
Syntax
storage nfs export activate <export-directory>
Parameters
<export-directory>
Directory of the export on the NFS backend storage array.
Usage
Use this command to activate an export that was previously deactivated because of low space in the SteelFusion Edge blockstore.
Example
Core_02 (config) # storage nfs export activate ifs/user_nfs2
Product
SteelFusion Edge
Related Commands
SteelFusion Core NFS (file mode) commands
storage nfs export snapshot create
Creates a snapshot of the NFS storage directory.
Syntax
storage nfs export snapshot <export-directory> create
Parameters
<export-directory>
Directory of the export on the NFS backend storage array.
Usage
See the SteelFusion Design Guide and the SteelFusion Core Management Console User Guide for information about the types of snapshots supported.
Example
Edge1 (config) # storage nfs export snapshot /USER_VOL1 create
Product
SteelFusion Edge
Related Commands
storage nfs export snapshot remove
storage nfs export snapshot remove
Removes a snapshot of the NFS storage directory.
Syntax
storage nfs export snapshot <export-directory> remove <name>
Parameters
<export-directory>
Directory of the export on the NFS backend storage array.
<name>
Name of the NFS snapshot.
Usage
See the SteelFusion Design Guide and the SteelFusion Core Management Console User Guide for information about the types of snapshots supported.
Example
Edge1 (config) # storage nfs export snapshot /USER_VOL1 remove edgesnapshot
Product
SteelFusion Edge
Related Command
storage nfs export snapshot create
SteelFusion Edge Hyper-V mode commands
In SteelFusion 6.0, you can connect the physical Core appliance (SFCR3500) to the new Hyper-V Edge appliances (VSFH1100 and VSFH1200). The hypervisor mode on the Core must match the hypervisor mode on the Edges at your branch offices. A Core or an Edge cannot operate in both the ESXi and Hyper‑V modes at the same time. For more information about hypervisor modes, see the SteelFusion Core Installation and Configuration Guide.
This section describes commands that are specific to the SteelFusion Edge Hyper-V hypervisor mode.
Note: The SteelFusion Edge in the Hyper-V mode operates only in the block (iSCSI) mode. The file (NFS) mode is not applicable for the Hyper-V mode.
storage protection trigger
Triggers protection operations based on the specified protection policy or protection server from the Edge appliance.
Syntax
storage protection trigger {policy <policy-id> | server <server-name>}
Parameters
policy <policy-id>
Specifies the policy identifier.
server <server-name>
Specifies the server name.
Usage
The Edge keeps records of recent protection trigger operations that reach the Core. In addition, the Edge keeps a local record of up to three protection trigger operations that fail to reach the Core.
You can set the maximum number of protection operations that the Core maintains by using the storage protection group command. The default protection history number is 5.
Example
Edge (config) # storage protection trigger policy policy_1
Product
SteelFusion Edge
Related Commands
storage protection backup group add, storage protection backup group modify, storage protection backup policy add
vsfed host add
Adds host hypervisor credentials to monitor hypervisor version, connectivity, and system resources (CPU and memory) allocated to the Virtual Edge.
Syntax
vsfed host add hostname <hostname> username <username> password <password>
Parameters
hostname <hostname>
Specifies the hostname of the host hypervisor.
username <username>
Specifies the username for the host hypervisor.
password <password>
Specifies the password for the host hypervisor.
Usage
To refresh the information obtained from the host hypervisor, use the vsfed host refresh-info command.
Example
Edge (config) # vsfed host add hostname sf-hyperv4 username eastcoastadmin password centadmin396Za!
Product
SteelFusion Edge
Related Commands
vsfed host refresh-info
vsfed host refresh-info
Refreshes the information obtained from the host hypervisor to the Virtual Edge. The information (such as hypervisor version, connectivity, and system resources (CPU and memory) allocated to the Virtual Edge) is obtained from the host hypervisor.
Syntax
vsfed host refresh-info
Parameters
None
Example
Edge (config) # vsfed host refresh-info
Product
SteelFusion Edge
Related Commands
vsfed host add