Dell EMC Storage Systems Online Help for the metro node appliance Version 7.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Figures..........................................................................................................................................8 Chapter 1: Welcome...................................................................................................................... 9 Metro node overview..........................................................................................................................................................9 Welcome to metro node.....................
Removing a chart......................................................................................................................................................... 31 Moving a chart..............................................................................................................................................................31 Back-end Bandwidth Chart.......................................................................................................................................
Renaming a device....................................................................................................................................................... 71 Deleting a device..........................................................................................................................................................72 Mirroring a device....................................................................................................................................................
Storage volume properties........................................................................................................................................ 97 Create Virtual Volumes dialog box.......................................................................................................................... 98 Consistency group............................................................................................................................................................
The Create Storage View wizard........................................................................................................................... 120 Creating a storage view........................................................................................................................................... 120 Deleting a storage view.............................................................................................................................................
Figures 8 1 Simple device configuration.................................................................................................................................. 68 2 Complex device configuration.............................................................................................................................. 68 3 Extent configurations..............................................................................................................................................
1 Welcome This section gives overview on metro node, new features, and known issues. Topics: • • • Metro node overview Welcome to metro node What's New? Metro node overview The metro node family is a solution for federating Dell EMC and non Dell EMC storage arrays. Metro node resides between the servers and heterogeneous storage assets supporting a variety of arrays from various vendors.
Welcome to metro node Metro node is a Distributed Storage Federation solution that provides Local or Distributed Federation within a single data center, or between two clusters within synchronous distances. ● Mobility—Move and relocate Virtual Machines, applications, and data over distance. ● Availability—Create and maintain high-availability storage infrastructure by mirroring across locations. ● Collaboration—Enable concurrent read/write access to data across locations.
2 Using the GUI This section describes how to use the GUI. Topics: • • • • • • About the GUI Sorting data Selecting objects Properties panel Using the global search Accessing online help About the GUI Management Console screen Section hover menus The main menu on the Management Console screen provides the following menu sections: ● Dashboard — Provides a quick access to System Status (default home page) and System Health.
Sorting data When columns of data are listed in a view, an arrow displays in the column that is sorted by default. The arrow indicates the direction of the sort; ascending ( ) or descending ( ). You can also sort in the following ways: ● Create a sort order — Click in a column header to create a sort order. ● Change a sort order — Click the column header to sort the data in the column, and then click a second time to change the direction of the sort.
● To go directly to the object screen to manage that object, hover over the object name, and then click Manage in the tool tip. ● To delete the current search results and perform additional searches, type or select the new search criteria in the appropriate box and then click . The current results will update accordingly. ● To save the current search results and perform new searches, hover over the area to the right of the current tab, and then click + to create a new tab.
3 Configuring GUI default settings This section describes how to change the GUI default settings. Topics: • • Configuring the Idle Timeout Configure Settings Configuring the Idle Timeout About this task A GUI session locks after 10 minutes of inactivity, and you must reenter your password to resume the session. When you re-enter your password, any work in progress resumes at the point of the timeout. You can set the idle timer to up to 12 hours or 720 minutes.
The idle timeout is based on the URL used to access the GUI. Therefore when you access the GUI on cluster 1 and set the idle timeout, it will apply only to cluster 1. If you log into cluster 2, the idle timeout dialog will not have the same value as that of cluster 1, because the URL is different. The value of the timeout field can be an integer value between 1 and 12 if the field unit value is set to hours.
4 Using storage hierarchy maps This section describes how to use storage hierarchy maps.
Single cluster map Distributed maps Storage hierarchy maps are available for storage objects that span clusters. For these storage objects, maps show the relationships between these objects across clusters. Distributed devices and virtual volumes Distributed devices appear outside of both clusters because they are not associated with a specific cluster, but instead spans both clusters.
Map showing a distributed device and associated virtual volume Remote virtual volumes A virtual volume that has remote locality means that its supporting device is on a remote cluster. The associated map shows the supporting device on the other cluster along with the underlying storage objects.
Map showing a remote virtual volume Globally visible devices A virtual volume that is local to a cluster but is on top of a global supporting device is shown as a remote virtual volume on a different cluster.
Map showing a globally visible device. Storage view maps A storage view map shows an overview of the components in a storage view, and allows you to drill down further to see the health and properties of all underlying storage objects, down to the array level. You can print, export, search for an object and zoom in an out of a map. This topic describes features specific to storage view maps. NOTE: Storage view maps do not support multi-cluster storage objects.
the Map Overview is a section that lists the storage objects in the storage view. Expanding a list and selecting an object from this list will cause the map to zoom and pan to the selected object. After zooming in or out of specific areas of the map, you can click to refresh the map and reset it to the initial view. Initial map view Storage view components The components of the storage view (initiators, ports and virtual volumes) are shown at the bottom of the left panel.
Zooming in or out of a map and expand or collapse of all virtual volumes Zoom in or out of a map and expand or collapse of all virtual volume in the following ways: ● ● ● ● Incrementally zoom in or out of a map Zoom into a selected area of a map Zoom the map to show the entire screen Expand or collapse of all virtual volumes ● Move the entire map — In the Map view, go to MAP TOOLS, click and hold anywhere in the map (the pointer changes to a blue color box), and then drag in the direction you want to move
Unhealthy storage objects Exporting a map to an image file About this task You can export an entire map, or the currently visible portion of a map to a .PNG image file, which you can print. Steps 1. Click in the map's navigation bar. 2. In the drop-down list, select one of the following: ● Export Entire Map — Exports the entire map to an image file. ● Export In View — Exports the currently visible portion of the map to an image file. 3.
2. In the drop down list, select one of the following: ● Print Entire Map — Prints the entire map. ● Print Visible Map — Prints the currently visible portion of the map. Select a print orientation that most closely matches the dimensions of the map area you want to print. In most cases, landscape orientation works best. 3. In the Print dialog box, select the printer and print settings, and then click Print.
5 Viewing system status This section describes how to view the status of the system and other components. Topics: • • • • The System Status view Metro node cluster status Metro node director status Product version The System Status view The System Status view is the default view that displays when you connect to the GUI. It shows a graphical representation of your metro node configuration.
Metro node clusters The Connect icon next to a cluster name indicates the cluster that you are connected to. To view information about the cluster, click the Cluster Properties at the bottom display. For help on any of the cluster properties, click Help. To view version details, click the Version Details at the bottom of the status display. The cluster status displays at the bottom of the cluster image. To view status details, click Status Details at the bottom of the status display.
Metro node cluster status The following table defines the values for the metro node cluster states. Status Type Values Definition Operational Status OK The cluster is functioning normally. Degraded The cluster is not operating as configured. This may indicate one or more of the following problems: degraded redundancy level (for example, a director is dead), suspended virtual volumes or exported volumes, storage volumes not visible from all directors, or the metadata volume is not yet processed.
Status Type Values Definition volumes, suspended devices, conflicting director count configuration values, out-of-date devices, and so forth. Unknown Metro node cannot determine the cluster's health state, or the state is invalid. Critical failure The cluster is not functioning and may have failed completely. This may indicate a complete loss of back-end connectivity through all directors in the cluster. Major failure The cluster is failing and some functionality may be degraded or unavailable.
Operational state Definition Unknown Metro node cannot detect the operational state of the director, or the state is invalid. Communication state Definition OK The director is functioning normally. Busy The director's firmware is currently too busy to respond. No contact The management server is unable to connect to the director firmware. Lost communication The management server has lost the connection to the director firmware.
6 Monitoring the system This section describes how to monitor system performance. Topics: • • Performance System Health Performance The Performance Monitoring dashboard The performance monitoring dashboard provides a customized view into the performance of your metro node system and its storage objects. You decide which aspects of the system's performance to view and compare. Virtual volumes are the only storage objects for which you can view performance statistics.
The +Add Content section is displayed and shows the available charts to choose from. 4. Select the chart that you want to add. The chart is added to the dashboard. 5. When you are finished adding charts, click +ADD CONTENT to close the +Add Content section. The selected charts are added to the dashboard. 6. To view a chart in full-screen mode, click the Maximize icon in top-right corner of the chart. The chart expands to fit the entire screen.
Back-end Bandwidth Chart The Back-End Bandwidth chart on the Performance Dashboard shows the quantity of back-end reads and writes per second over time for directors. Generally, bandwidth (measured in KB/s or MB/s) is associated with large block I/O (64KB or greater I/O requests). Each array type, model, and underlying hard disk drives is different. Ensure you know your array's capabilities, for example, response time, IOPS, and bandwidth.
Viewing the Back-end Bandwidth chart 1. From the GUI main menu, click Performance. 2. In the Performance Dashboard, select the tab in which you want to display the Back-end Bandwidth chart (or create a custom tab). 3. Click +Add Content. 4. Click the Back-end Bandwidth icon. Back-end Throughput chart The Back-end Throughput chart shows the back-end I/Os per second over time for directors.
Changing the view Use the following appropriate selection criteria to filter the data: ● Director — Allows you to select all directors or a specific director in the cluster. ● Read and Write check boxes — Allows you to select one or both check boxes to filter throughput for Reads and Writes. Viewing the Back-end Throughput chart 1. From the GUI main menu, click Performance. 2. In the Performance Dashboard, select the tab in which you want to display the Back-end Throughput chart (or create a custom tab).
● Aborts — Select only this box to view only the aborts. Select this box with other boxes to view the aborts and other statistics. Clear this box to stop viewing aborts. ● Resets — Select only this box to view only the resets. Select this box with other boxes to view the resets and other statistics. Clear this box to stop viewing resets. ● Timeouts — Select only this box to view only the timeouts. Select this box with other boxes to view the timeouts and other statistics.
VNX guidelines ● ● ● ● ● <10msec — Great 10-20 msec — Decent 20-100 msec — Not so great >100 msec — Poor performance High latency could cause forced flushes due to lack of available cache to buffer writes.
often typical of back-ups or batch processing jobs. These spikes are not necessarily a sign of a problem. However, monitor their height and duration, and their impact on response time. NOTE: The chart displays data only for the directors in the cluster to which you are currently connected. To simultaneously view statistics for another cluster, open a second browser session and connect to the second cluster.
● Check if CPU utilization and front-end operations count is also high. The system might be simply at over-capacity, which may also be reflected in this category. ● Constantly rising heap usage is a potential sign of a director memory leak. Contact Dell EMC Support to identify these systems. Corrective actions ● Check if CPU utilization and front-end operations count is also high. The system might be simply at over-capacity, which may also be reflected in this category.
Changing the view To view the Front-end Queue Depth of a single director in your metro node system, select the director name from the Director drop-down. NOTE: The chart displays data only for the directors in the cluster to which you are currently connected. To simultaneously view Front-end Queue Depth for another cluster, open a second browser session and connect to the second cluster. Viewing the Front-end Queue Depth chart 1. From the GUI main menu, click Performance. 2.
● Check for bandwidth or IOPS over-provisioned metro node front-end ports. Be sure to balance hosts and LUNs across the available directors and front-end ports presented from metro node. Check the front-end fabric for saturation or overcapacity. ● Verify that front-end Fibre Channel ports, HBAs, and switch ports are configured to the proper port speeds.
NOTE: The chart displays data only for the directors in the cluster to which you are currently connected. To simultaneously view front-end port latency for another cluster, open a second browser session and connect to the second cluster. Guidelines It is difficult to give absolute recommended values for front-end latencies since they are typically highly dependent upon back-end latencies.
Guidelines ● Front-end performance should be compared to baseline numbers (native host to storage array) when metro node performance issues arise. Poor throughput might be caused by poor storage array performance. Before adding metro node to your environment, know what your application throughput was beforehand. ● Front-end performance in metro node depends heavily upon the available back-end storage array performance, and in metro node Metro configurations, the WAN performance for distributed-devices.
Changing the chart view Use the following appropriate selection criteria to filter the data: ● Director— Allows you to select all directors or a specific director in the cluster. ● Read and Write check boxes — Allows you to select one or both check boxes to filter throughput for Reads and Writes. Viewing the Front-end Throughput chart 1. From the GUI main menu, click Performance. 2.
Write Latency Delta chart This chart provides the delta between Front-end latency and Back-end Latency per director. This is a key metric for Local/ Metro — the amount of overhead time metro node spends processing a write. NOTE: The chart displays data only for the directors in the cluster to which you are currently connected. To simultaneously view Write Latency Delta for another cluster, open a second browser session and connect to the second cluster.
NOTE: The chart displays data for the cluster to which you are connected. To simultaneously view the statistics for a remote cluster, open a second browser session and connect to the remote cluster's management console. Guidelines ● The absolute value of the bytes (or bandwidth) and packet (or throughput) related categories might not indicate a problem.
NOTE: The per ip-com-port statistics will not add up perfectly to the director-level statistics category. This is because of a very small amount (less than a MB/s typically) of IP port traffic sent over the director's management port which is not tracked in this chart, but is tracked on the director level UDT category. Changing the view Use the following appropriate selection criteria to filter the data:. ● ● ● ● ● ● Director — Displays data for all directors or a specific director in the cluster.
○ Monitor the port's counters for non-zero values for tim_txcrd_z or time transmission credits are zero. This means the FC port wanted to transmit a FC packet, but did not have sufficient buffer credits to so. Any non-zero value in this category implies performance issues on the WAN link. ○ If FCIP gateway devices are used between metro node clusters, ensure that the FCIP tunnel is configured properly. ● For Brocade FCIP switches: ○ Check for bandwidth rate limiting setting on the tunnel.
Guidelines ● Local device rebuild rates are dictated by two factors: The available read performance of the source device, and the write performance of the target device. ● Distributed device rebuild rates are dictated by three factors: The available inter-cluster bandwidth, the read performance of the source device, and the write performance of the target device. ● Be aware of the potential performance impact of rebuilds on host I/O traffic. Tune the transfer-size of the rebuild accordingly.
● Press and hold Ctrl and click a column header to create a sort order. A number appears in the column header to indicate the order of the sort. ● Click a sorted column header to remove the number and clear a sort order. ● Rearrange columns by clicking the column header, and dragging the column to the desired location. Viewing the Rebuild Status dashboard 1. From the GUI main menu, click Performance. 2. Click + and select Add Rebuild Dashboard.
● For metro node Metro systems, poor virtual volume performance could be caused by poor inter-cluster WAN link performance and/or poor storage volume performance. ● Monitor other metro node performance statistics such as director CPU usage, front-end aborts, back-end aborts, storage volume latency, or WAN latency for correlations and possible causes of the poor performance. Display the default charts for a virtual volume 1. Select the virtual volume in the list. 2.
● Check for bandwidth/IOPS over-provisioned metro node front-end ports. Be sure to balance hosts and LUNs across the available directors and front-end ports presented from metro node. Check the front-end fabric for saturation or overcapacity. ● Verify that front-end FC ports, HBAs and switch ports are configured to the correct port speeds. ● Configure your host multipathing software based on metro node best practices, and ensure the installed software versions are compatible with metro node.
● Satisfactory latency or response time is depends heavily on the application's requirements. ● It is not possible to give recommended values for front-end latency since it depends heavily on back-end latency. ● In general, read or write latency values under 10msec are good, and greater than 100msec is usually cause for concern. Different volumes may have different thresholds for what is acceptable. ● Metro node Local processing overhead on read misses and on write operations is roughly 1msec.
● In a metro node Metro you will incur extra WAN round-trip time on your write latency since writes need to be successfully written to both cluster's storage before the host is acknowledged. This extra latency may impact the throughput and IOPS of serialized-type applications. Corrective actions ● Check for bandwidth/IOPS over-provisioned metro node front-end ports. Be sure to balance hosts and LUNs across the available directors and front-end ports presented from metro node.
Front End Ports dashboard The Front End Ports dashboard The Front End Ports dashboard shows performance metrics for all metro node front-end ports, sorted by the busiest total IOPS ports to the least busiest ports. You can sort each column in ascending or descending order. Note that historical data is not available for ports. The dashboard automatically refreshes every five seconds, displaying data from the last five second period.
● Unsatisfactory front-end port performance might be a symptom of poor back-end performance (metro node to storage array data path.) ● For metro node Metro systems, poor front-end port performance could result from either poor inter-cluster WAN link performance, and/or poor remote cluster storage volume performance.
Corrective actions For information about corrective actions for any errors or warnings reported, see the Troubleshooting section of metro node in the SolVe Desktop, available on Dell EMC Online Support. Opening the System Health dashboard From the GUI main menu, select Dashboard > System Health.
7 Provisioning storage This section describes how to work with various storage objects to provision storage. Topics: • • • • • • • • • • • Guide Provisioning from storage volumes Provision Job properties Distributed storage Storage arrays Storage volumes Devices Extents Distributed devices Virtual volumes Consistency group Guide For the steps to begin provisioning storage, see Guide. In the Guide, each step is a link that opens the UI screen that is required to perform the step.
Creating thin virtual volumes To create a thin virtual volume, the storage volume must be thin capable. If you do not select a thin capable storage volume, the resulting volume is thick. Launching the wizard You can launch the Provision from Storage Volumes wizard from several different locations that are listed below. Depending on where you launch the wizard, you are given the option to create a specific type of consistency group by default.
Storage arrays Supported storage arrays Metro node supports a variety of storage systems and third-party arrays. For an up-to-date list of supported arrays and other components, see the Simple Support Matrix for metro nodedocument, available on Dell EMC Online Support and on the SolVe Online. Using the Storage Arrays view Metro node automatically discovers storage arrays that are connected to the back-end ports. All arrays connected to each director in the cluster are listed in the Storage Arrays view.
Opening the Storage Arrays view From the GUI main menu, do one of the following: 1. In a metro node Local: a. Select Provision Storage. b. In the View by drop-down, select Storage Arrays. 2. In a metro node Metro: a. Select Provision Storage. b. In the Provision on drop-down, select the cluster of the storage array. c. In the View by drop-down, select Storage Arrays. Rediscovering a storage array About this task Rediscover a storage array if any changes you made to the array are not reflected in the GUI.
3. Click Close. Forgetting a storage array About this task Forget a storage array if it has been deleted from use by metro node and it is no longer used for I/O. You can forget a LUN from the Show Logical Units screen, or from the Rediscover Storage Array dialog box while rediscovering a storage array. Steps 1. From the GUI main menu, do one of the following: a. In a metro node Local: i. Select Provision Storage. ii. In the View by drop-down, select Storage Arrays. b. In a metro node Metro: i.
The Storage Volumes view The Storage Volumes view lists all storage volumes in the selected cluster. By default, storage volumes are sorted in ascending alphabetical order, then by name. The arrow in the default sort column indicates the direction of the sort; ascending ( ) or descending ( ). You can sort columns of data, select one or more storage volumes in the list, and show or hide properties links on the screen.
Tasks in this Screen You can also perform the following tasks in the Storage Volumes screen: ● Search for a storage volume — Click the field that appears. Press Enter. icon corresponding to the element and type the full or the partial name in the ● Refresh screen data — Click the Refresh icon . ● Provision from storage volumes — Click PROVISION to open the Provision from Storage Volumes wizard.
If the array does not require a Name-Mapping file, you have the option of creating and using this file to customize the names of the claimed storage volumes. For instructions to create a Name Mapping file and other configuration information, see the Configure storage arrays for metro node procedure in the SolVe Desktop, available on Dell EMC Online Support. To provision 3PAR LUNs for metro node, see the 3PAR documentation. Steps 1. From the GUI main menu, do one of the following: In metro node local a.
Setting a storage volume rebuild type About this task For XtremIO, VNX and VMAX arrays, metro node automatically detects if a storage volume is thin capable. For all other arrays, metro node does not automatically detect if a storage volume is thinly-provisioned on the array. Therefore, if a storage volume is thinly-provisioned, or thin capable, choose a thin rebuild. When you select a thin rebuild, metro node preserves the thinness of the target device by copying only non-zero data.
3. Review the results of the operation, and then click Close. Viewing ITLs for a storage volume About this task The Show ITLs dialog box shows the selected storage volume's back-end path (metro node back-end port, storage target port, and LUN). For each storage volume there should be at least two initiator-target-LUN (ITLs) for each director, indicating that each director has two paths to the storage volume.
Health state Definition Degraded The storage volume may be out-of-date and/or the underlying disk is not performing optimally. Unknown Metro node cannot determine the storage volume's Health state, or the state is invalid. Non-recoverable error The storage volume may be out-of-date compared to its mirror (applies only to a storage volume that is part of a RAID-1 Metadata Volume), and/or metro node cannot determine the Health state.
Figure 1. Simple device configuration Figure 2. Complex device configuration Using the Devices view The Devices view shows all local devices in the selected cluster. Use this view to quickly see the status of a device, search for a device, or view the underlying components of a device. Devices are sorted by name in ascending alphabetical order. You can sort columns of data, select one or more objects in the list, and show/hide properties on the screen.
Column Description Status Indicates how the device is functioning in the cluster. Device status provides more information. Virtual Volume The name of the virtual volume built on the device. Additional tasks You can also perform the following tasks from the Devices view: ● ● ● ● ● ● ● ● View the components of a device — Select the device. The underlying components display in the components panel.
Virtual volume names If a virtual volume was created on the device, the virtual volume is given the device name, followed by _vol. For example, if the device name is "Mydevice1", the virtual volume created on the device will be named Mydevice1_vol. You can rename the device or virtual volume at any time in the properties dialog box. Device names To avoid entering a different name for each device you are creating, you can enter a base name to be used for all the devices.
Viewing the status of IO to a device About this task The Service status attribute in the Device Properties dialog box indicates the status of I/O to a device. Device status provides a definition of the service status. Steps 1. From the GUI main menu, do one of the following: a. In a metro node Local: i. Select Provision Storage. ii. In the View by drop-down, select Devices. b. In a metro node Metro: i. Select Provision Storage. ii. In the Provision on drop-down, select the cluster of the devices. iii.
Deleting a device About this task You may delete one or more top-level devices that do not have virtual volumes. If the device's children are other devices, the child devices become top-level devices. If the device's children are extents, the status of those extents change from Used to Claimed. Steps 1. From the GUI main menu, do one of the following: a. In a metro node Local: i. Select Provision Storage. ii. In the View by drop-down, select Devices. b. In a metro node Metro: i. Select Provision Storage.
Health status Description Unknown Metro node cannot determine the device's Health state, or the state is invalid. Non-recoverable error The device may be out-of-date compared to its mirror (applies only to devices that are part of a RAID-1 device), and/or metro node cannot determine the Health state. Minor Failure One or more children of the device is out-of-date, but will rebuild.
Block Count The number of blocks in the underlying extent. Block Size The size of the data blocks used internally when managing I/O. The block size determines the granularity of storage volume I/O and the rebuild rate of distributed devices. Capacity The size of the device. Thin Capable Indicates if the underlying storage volume is thinly-provisioned. Storage Array Family The family of arrays that the supporting array belongs to.
Operational Status Indicates how the device is functioning. See Operational states. Service Status Indicates whether I/O can proceed on the device. See Service states. Add capacity to virtual volumes Use this dialog box to expand a virtual volume using concatenation. Add Capacity to Virtual Volume The selected virtual volume that you want to expand. Current Capacity The size of the selected virtual volume. Additional Capacity Needed Enter the amount of space to add to this virtual volume.
Operational Status Indicates how the extent is functioning in the cluster. See Operational states. Extents About extents An extent is a range of blocks of a storage volume. You can only create a full-size extent that spans the entire capacity of the storage volume. Extents are used to create devices, and then virtual volumes on top of those devices. Extent names Extents are automatically named after the underlying storage volume using the "extent_" prefix.
Column Description Storage Volume The name of the underlying storage volume. Extent Properties Panel This screen displays the properties of the extents in a separate panel at the extreme right side of the screen.
Best practices ● If the storage volume is larger than the wanted virtual volume, create an extent the size of the wanted virtual volume. Do not create smaller extents, and then use different RAID types to concatenate or stripe the extents. ● If the storage volume is smaller than the wanted virtual volume, create a single extent per storage volume, and then use devices to concatenate or stripe these extents into a larger device.
4. Click to save the new name. Deleting an extent About this task You can delete one or more unused extents. Steps 1. From the GUI main menu, do one of the following: ● In a metro node Local: a. Select Provision Storage. b. In the View by drop-down, select Extents. ● In a metro node Metro: a. Select Provision Storage. b. In the Provision on drop-down, select the cluster of the extent. c. In the View by drop-down, select Extents. 2. In the Extents view, select the extents to delete, and then click Delete.
Distributed devices About distributed devices Distributed devices are configured by using storage from both clusters, and are used only in a metro node Metro system. A distributed device's components must be other devices, and those devices must be created from storage in both clusters. You can also create a distributed device by mirroring a device remotely. Devices can be components of other devices. If a device is not a component of another device, it is referred to as a top-level device.
Column Description Device The name of the distributed device. You can change the name in the properties dialog box. Geometry Indicates the underlying RAID structure of the distributed device. Capacity The size of the distributed device. Health The overall health of the distributed device. Distributed device status provides more information. Status Indicates how the distributed device is functioning. Distributed device status provides more information.
Distributed devices in a consistency group use the rule set applied to the consistency group. If the distributed device will not be in a consistency group, you must select a rule set for the distributed device. You can change the rule set in the distributed device properties dialog box at any time. Also, you can use the CLI to create your own detach rule for the distributed device (as long as the device is not in a consistency group).
Steps 1. From the GUI, do the following: a. In a metro node Local: i. Select Provision Storage. ii. In the View by drop-down, select Devices. b. In a metro node Metro: i. Select Provision Storage. ii. In the Provision on drop-down, select the Distributed Storage. iii. In the View By drop-down, select Devices. The Distributed Devices screen is displayed. 2. To view the distributed device properties of a device at the right panel of the screen, click the distributed device name link. 3.
2. In the Distributed Devices screen, select the distributed devices to delete, and then click DELETE. A confirmation dialog box is displayed. 3. Review the distributed devices to delete and the clusters to which the underlying devices will return upon completing the operation. If satisfied, click Yes. The results dialog box is displayed. 4. Review the results of the operation and proceed accordingly. 5. Click Close to continue.
Operational status Description Starting The distributed device is not yet ready. Service status Description Running The distributed device is functioning normally. Winner–running This cluster detached the distributed device while the other cluster was unreachable, and is now sending I/O to the device. Cluster–unreachable Metro node cannot reach the cluster; the status is unknown.
Expanding volumes You can non-disruptively increase the capacity of a virtual volume by selecting a storage volume with available capacity and specifying whether to use all or a portion of the capacity. metro node automatically creates an extent based on the specified capacity. To expand a volume using existing extents or devices, use the CLI. The CLI Guide for metro node provides more information.
Name Definition Expandable by The amount of space that is available for volume expansion. A volume that has an Expandable by of 0 can still be expanded using concatenation. A volume that has an Expandable by of > 0 can be expanded using storage volume expansion. Expansion Method The expansion method available for this volume. Possible values: ● concatenation — The volume can be expanded using Concatenation or RAID-C expansion.
Opening the Virtual Volumes view From the GUI main menu, do one of the following: In metro node local 1. Click Provision Storage. 2. In the View by drop-down, click Virtual Volumes. In metro node Metro 1. Click Provision Storage. 2. In the Provision on drop-down, select the cluster of the storage volume. 3. In the View by drop-down, select Virtual Volumes. The Distributed Virtual Volumes view The Distributed Virtual Volumes view lists all distributed virtual volumes in the system.
Name Definition ● in-progress — The volume cannot be expanded because it has a volume expansion in progress. Consistency Group The name of the consistency group to which the volume belongs. Supporting Device Shows the volume's supporting device. Click a device name to see its status and properties. Distributed Virtual Volume Properties Panel This screen also displays the properties of the distributed virtual volume in a separate panel at the extreme right side of the screen.
from storage volumes provides detailed information. To provision from storage volumes, select CREATE > Provision from Storage Volumes from Provision Storage view. ● Create a virtual volume on top of a device (top-level) — Use this option if you did not create a virtual volume at the time that you created the device. This option allows you to add a virtual volume later. The volume is given the device name, followed by _vol.
NOTE: Remote virtual volumes suspend I/O during inter-cluster link outages. As a result, the availability of the data on remote virtual volumes is directly related to the reliability of the inter-cluster link. Steps 1. From the GUI main menu, do one of the following: In metro node local a. Click Provision Storage. b. In the View by drop-down, click Virtual Volumes. In metro node Metro a. Click Provision Storage. b. In the Provision on drop-down, select the cluster of the storage volume. c.
3. In the confirmation dialog box, review the volumes to delete, and if satisfied, click Yes. Renaming a volume About this task Rename a virtual volume at any time. Renaming a virtual volume does not impact host IO to the volume. Steps 1. From the GUI main menu, do one of the following: In metro node local a. Click Provision Storage. b. In the View by drop-down, click Virtual Volumes. In metro node Metro a. Click Provision Storage. b. In the Provision on drop-down, select the cluster of the storage volume.
Health status Definition OK The virtual volume is functioning normally. Unknown Metro node cannot determine the virtual volume's Health state, or the state is invalid. Non-recoverable error Metro node cannot determine the virtual volume's Health state. Minor Failure One or more of the virtual volume's underlying devices is out-of-date, but will rebuild. Major Failure One or more of the virtual volume's underlying devices is out-of-date, but will never rebuild.
Virtual volume properties Virtual Volume Name The name of the virtual volume. You can change the name in this field. Supporting Device The device on which the virtual volume was created. Consistency Group Identifies the metro node consistency group to which this virtual volume belongs. Locality Designates where the virtual volume is located. Values can be cluster 1, cluster 2 or distributed.
Show ITLs dialog box This dialog box shows a read-only list of Initiator-Target-LUN combinations that shows the storage volume's back-end path (metro node back-end port, storage port, and LUN). you can also search for a specific initiator, target or LUN by entering the number in the Find text box and pressing Enter. The following table describes the fields shown in the dialog box: Field/Column Description Storage Volume Name The name of the selected storage volume.
ALUA Support field values Value Definition Implicit The logical unit can change its ALUA access state internally within the array without any external input requesting a change. Explicit The logical unit can change its ALUA access state in response to a request from an initiator (metro node back-end software). Implicit explicit The logical unit has both implicit and explicit capabilities. None ALUA is not supported on the array.
Port Node WWN The port's node World Wide Name (WWN). The WWN is a unique network identifier for the port's node. Export Status Indicates whether or not this port is used to export storage. See metro node port status. Storage array properties Storage Array Name The name of the storage array manufacturer. Storage Array Family The family of arrays that the storage array belongs to. Possible values: ● XTREMIO — The array belongs to the XtremIO family of arrays.
Storage Array Family The family of arrays that the supporting array belongs to. Possible values: ● XTREMIO — The array belongs to the XtremIO family of arrays. ● CLARiiON — The array belongs to the VNX or Unity family of arrays. ● SYMMETRIX — The array belongs to the VMAX or Symmetrix family of arrays. ● Other — Metro node does not recognize the array, or does not support creating thin volumes on the array. ● - (dash) — The Storage Array Family property is not populated.
Applying detach rules When you create a consistency group that contains distributed or global virtual volumes, you must select a detach rule to determine if and where I/O continues during an inter-cluster link failure. Note that detach rules are applied per consistency group. Creating a consistency group provides detailed information on the detach rules available for consistency groups and their effect on I/O during a link failure.
Opening the Consistency Groups view From the GUI main menu, do one of the following: 1. In a metro node Local: a. Select Provision Storage. b. In the View by drop-down, select Consistency Groups. 2. In a metro node Metro: a. Select Provision Storage. b. In the Provision on drop-down, select the cluster of the consistency groups. c. In the View by drop-down, select Consistency Groups. Distributed Consistency Groups view The Distributed Consistency Groups screen shows all distributed consistency groups.
a. Select Provision Storage. b. In the View by drop-down, select Consistency Groups. 2. In a metro node Metro: a. Select Provision Storage. b. In the Provision on drop-down, select the Distributed Storage. c. In the View by drop-down, select Consistency Groups. Create Consistency Group wizard Use the Create Consistency Group wizard to a create a consistency group and add volumes to the group. You can create the group and add the volumes later.
Consistency Group Type Storage at Clusters Visibility Local (Local volumes only) cluster-1 or cluster-2 cluster-1 or cluster-2 Global (Local volumes that are visible at both clusters) cluster-1 or cluster-2 cluster-1 and cluster-2 Distributed (Distributed volumes only) cluster-1 and cluster-2 cluster-1 and cluster-2 Creating a consistency group About this task Use the Create Consistency Group wizard to a create a consistency group and add volumes to the group.
5. Click OK. The results dialog box opens. 6. Review the results, and then click Close. Removing a volume from a consistency group About this task Remove a volume from a consistency group at any time. If the volume is exported in a storage view, it will remain in the storage view. Be aware of the following when you remove volumes from consistency groups: ● When you remove a volume, it retains the consistency group's visibility.
Consistency Group status The Operational status column in the Consistency Groups view shows the overall status of the consistency group at both clusters. If the status is the same at both clusters, that status displays in the Operational status column. If the status is not the same at both clusters, the less than optimal status will display. The following table lists and defines the consistency group operational states.
Consistency group properties Consistency Group Name The name of the consistency group. You can change the name in the properties dialog box. Detach Rule (metro node Metro only) The detach rule that applies to the consistency group. It designates which cluster detaches if the clusters lose connectivity. Possible values: no-automatic-winner — The consistency group does not select a winning cluster.
Step 2: Select volume options Select mirroring on the cluster where the virtual volumes will be created (optional), the quantity, size and base name for the virtual volumes, and then enter a name for the provisioning job (optional). High Availability — Select this check box to enable mirroring at the cluster indicated. The option to mirror at a cluster is disabled if you have less than two arrays in the cluster. ● For a local consistency group, select the check box to enable mirroring at the local cluster.
● Type — Indicates whether the pool is capable of provisioning thick volumes, thin volumes, or both. If you select a thin pool, a thin rebuild will be automatically set for the storage volume that is created during the provisioning process. ● Free — The amount of storage available for provisioning. ● Total — The total amount of storage available from the pool. NOTE: To create a thin volume, the selected pools must be thin capable and the supporting arrays must belong to the same array family.
Selecting a storage group By default, metro node will automatically select a storage group for the newly created volumes, based on compatible policies, and the lowest amount of volumes in the group. However, if you want to select a storage group, click the Storage Group drop-down box, and then select Select from list to show the available storage groups to choose from. NOTE: For V3GR arrays only, the Storage Group drop-down box changes to a selection list because a storage group is required.
NOTE: For V3GR arrays only, the Storage Group drop-down box changes to a selection list because a storage group is required. For all other arrays, the storage group is optional. The Storage Group section shows the following information about available storage groups: ● Name — The name of a storage group on the selected array. ● Policy — The type of policy associated with the storage pool (if any).
Step 2: Select volume options Select high availability options, synchronization options, and then enter a name for the volume. If a cluster has only one array, the ability to mirror is disabled for that cluster. ● Source Cluster — Select the cluster where you want to create the virtual volume. ● High Availability — Select a check box to enable mirroring at the cluster indicated. You can select a single cluster, both clusters, or leave both check boxes unselected to disable mirroring at both clusters.
To discard all selections made on previous screens and restart the wizard from Step 1, click Start Over in the lower-right corner of the screen. To go back to a specific step, click Back until you reach that step. Step 3: Create thin volumes The storage volumes you selected support creating thin virtual volumes. To create thin virtual volumes, click the Create thin virtual volumes check box, or click Next to continue without creating thin volumes.
8 Exporting storage This section describes how to export storage. Topics: • • Initiators and metro node ports Storage views Initiators and metro node ports About Initiators and metro node ports Metro node ports The virtual volumes that are created on a device are not visible to hosts until you export them. Virtual volumes are exported to a host through front-end ports on the metro node directors and HBA ports on the host/server.
Column Description Port WWN A unique network identifier for the port. Port Properties Panel This screen displays the properties of the ports in a separate panel at the extreme right side of the screen. Using the Port Properties panel, you can: ● View the details of the port ● Enable or disable a port ● View the details of the discovered initiators of the port Tasks in this Screen You can perform the following tasks from the Ports view: ● Search for a port — Click the appears. Press Enter.
Column Description with "UNREGISTERED-". You can rename the initiator during the registration process. Host Type The type of host associated with the initiator. Node WWN A unique network identifier for the HBA's interface card. All ports on the card share this node World Wide Name (WWN). Port WWN A unique network identifier for the port. Initiator Properties Panel This screen displays the properties of the storage volumes in a separate panel at the extreme right side of the screen.
Enabling or disabling a port Steps 1. From the GUI main menu, do one of the following: ● In a metro node Local: a. Select Provision Storage. b. In the View by drop-down, select Ports. ● In a metro node Metro: a. Select Provision Storage. b. In the Provision on drop-down, select the cluster of the port. c. In the View by drop-down, select Ports. 2. In the Ports view, select the port. 3. In the Port Properties pane, click ENABLE PORT to enable the port, or DISABLE PORT to disable the port.
● HPUX ● IBM-D910 ● Default (use this type for all hosts not listed above) Rediscovering an initiator About this task When initiators are connected directly or through a Fibre Channel fabric, metro node automatically discovers them and populates the Initiators view. Steps 1. From the GUI main menu, do one of the following: a. In a metro node Local: i. Select Provision Storage. ii. In the View by drop-down, select Initiators. b. In a metro node Metro: i. Select Provision Storage. ii.
7. Click Close. The initiator is now visible in the Initiators view. Unregistering an initiator About this task You can unregister an initiator that is not included in any storage views. If an initiator is included in a storage view, Unregister is disabled. Steps 1. From the GUI main menu, do one of the following: a. In a metro node Local: i. Select Provision Storage. ii. In the View by drop-down, select Initiators. b. In a metro node Metro: i. Select Provision Storage. ii.
Add Capacity to Virtual Volume The selected virtual volume that you want to expand. Current Capacity The size of the selected virtual volume. Additional Capacity Needed Enter the amount of space to add to this virtual volume. Metro node will look for volumes with at least that available capacity. To enter the value using a different unit, select the correct unit from the drop-down list.
Storage view maps You can view a storage hierarchy map to see the components in the storage view, and drill down further to see the health and properties of all underlying storage objects. Storage view map provides more information. Using the Storage Views screen The Storage Views screen lists all storage views in a selected cluster. Use this screen to search for a storage view, assess the health of a storage view, or show associated initiators, ports, and virtual volumes.
● Add or remove virtual volumes—Select the storage view name to display its components in the panel on the right. In the panel, click Virtual Volumes, and then click Add or Remove. Opening the Storage Views screen From the GUI main menu, do one of the following: 1. In a metro node Local: a. Select Provision Storage. b. In the View by drop-down, select Storage Views. 2. In a metro node Metro: a. Select Provision Storage. b. In the Provision on drop-down, select the cluster of the storage view. c.
Steps 1. From the GUI main menu: a. In a metro node Local: i. Select Provision Storage. ii. In the View by drop-down, select Storage Views. b. In a metro node Metro: i. Select Provision Storage. ii. In the Provision on drop-down, select the cluster of the storage view. iii. In the View by drop-down, select Storage Views. 2. In the Storage Views screen, click CREATE. The Create Storage Views wizard is displayed. 3. Complete the wizard. For additional help using the wizard, click Help.
3. Type the new name in the Storage View Name field, and then click to save the changes. 4. Verify that the name has been changed in the Storage Views screen. Adding or removing initiators from a storage view About this task Add an initiator to an existing storage view to allow the associated host to access the virtual volumes in the view. Remove an initiator when the host no longer needs to access the virtual volumes in the storage view.
b. In a metro node Metro: i. Select Provision Storage. ii. In the Provision on drop-down, select the cluster of the storage view. iii. In the View by drop-down, select Storage Views. 2. In the Storage Views screen, select a storage view to display its components in the panel on the right. 3. Click the VIRTUAL VOLUMES tab in the panel to display the virtual volumes (if any) in the storage view. 4. Click ADD. The Add Virtual Volumes dialog box is displayed. 5. Complete the dialog box, and then click OK.
ii. In the Provision on drop-down, select the cluster of the storage view. iii. In the View by drop-down, select Storage Views. 2. In the Storage Views screen, select the storage view to display its components in the panel on the right. 3. Click PORTS in the components panel to display the ports (if any) in the storage view. 4. Click ADD/REMOVE PORTS. The Add/Remove Ports dialog box displays.
Director Family The hardware family to which this director belongs. Director Count The number of directors this director expects at its cluster. Auto Boot Indicates whether the application is automatically booted on power up. Auto Restart Indicates whether the application is automatically rebooted after a failure. Communication Status Indicates the connectivity status between this instance of the CLI and the firmware. Health State Indicates the overall health of the director.
9 Moving data This section describes how to move data within or across clusters.
How data mobility works When a mobility job begins, a temporary device is created. For extents and devices, a temporary RAID-1 is created for each source device or extent. The target extent or device is attached as a mirror leg of the temporary device, and synchronization between the source and the target begins. Once synchronization completes, both source and target are fully synchronized and you can commit (or cancel) the mobility job.
Refreshing screen data The time of the last data refresh displays at the upper-right of the screen. To manually refresh the data at any time, click the Refresh icon in the upper-right corner of the screen. Additional tasks You can also perform the following tasks from this screen: ● Create a device mobility job — Select CREATE > Create Device Mobility Jobs to open the Create Device Mobility Jobs wizard.
Filtering data Use the Filter icon to filter the jobs displayed on the screen. Refreshing screen data The time of the last data refresh displays at the upper-right of the screen. To manually refresh the data at any time, click the Refresh icon in the upper-right corner of the screen. Additional tasks You can also perform the following tasks from this screen: ● Create a device mobility job — Select CREATE > Create Device Mobility Jobs to open the Create Device Mobility Jobs wizard.
Moving devices across clusters Depending on the metro node environment, some devices cannot be moved across clusters. The Create Device Mobility Jobs wizard automatically filters out those devices that cannot be moved. If your device is not shown in the Available Devices list, it could be for one of these reasons: ● The device has exported virtual volumes. Unexport the virtual volume to move this device. ● The device has virtual volumes that belong to a consistency group.
Viewing job details About this task You can view additional details for a mobility job in the properties dialog box. Steps 1. In the GUI main menu, click Mobility, and then select Move Data Within Cluster or Move Data Across Clusters. The selected view is displayed. 2. To view the Mobility Job Properties, click the job name link. 3. View the details of the job, and to hide the job details, click the arrow that is on the upper left of the Device Mobility Job Properties panel.
Pausing a job About this task If the performance impact of a job is too high, consider pausing the job during the day and resuming it at night or during off-peak hours to reduce the potential performance impact. You can pause and resume a job any number of times until the job completes. Steps 1. In the GUI main menu, click Mobility , and then select Move Data Within Cluster or Move Data Across Clusters. The selected view is displayed. 2. Select one or more jobs to pause. 3. Click Pause.
Steps 1. In the GUI main menu, click Mobility , and then select Move Data Within Cluster or Move Data Across Clusters. The selected view is displayed. 2. Click the job name link. The Mobility Job Properties panel is displayed. 3. In the properties panel, select a new transfer size from the drop-down. The change takes effect immediately. 4. Click OK. Searching for a job About this task You can search for a specific job on the Move Data Within Clusters and Move Data Across Clusters screen. Steps 1.
10 Notifications This section describes about the notifications which is a consolidated area of all appliance alerts and events for the cluster. Topics: • • • • • Platform alerts view Hardware alerts view Configure alerts view Platform view properties Hardware view properties Platform alerts view The PLATFORM ALERTS view lists all platform alerts generated through notification service for a corresponding NSFW event . By default, platform alerts are sorted in descending order by the last updated time.
Column Description Resource It shows the actual resource for which the issue has occurred. Count It represents the number of times the same alert is generated over the selected period. This column is available for historical alerts only. Event Source Represents the context of the event. For example, Virtual Volume. Event Source ID Unique ID for the source of the event. Helps to narrow down to the final component. Creation Date (UTC) Date and time when the alert is generated.
Opening the Platform alerts view From the UI main menu, do the following: 1. In a metro node: a. Select Notifications. b. In the Notifications, select PLATFORM ALERTS tab. Hardware alerts view The HARDWARE ALERTS view lists all hardware alerts generated through notification service for a corresponding iDRAC or Monitor event. By default, hardware alerts are sorted in descending order by the last updated time.
Column Description User Notes It represents the notes which are added by the user. Events and alerts Events provide information about changes happening to the system. Alerts are events that require attention by the system administrator or user. Most alerts indicate that there is a problem with the system that must be rectified to attain the best performance from the system. The system displays live and historical alerts for Platform and Hardware in the dashboard.
This screen shows the following information about configure alerts: Column Description Condition ID Indicates Unique ID of all defined alert definitions. Name Name of the alert definition. Enabled Indicates if the alert definition is enabled or disabled. Event Source Defines the source of the alert definition. Callhome Enabled It indicates whether the alerts are CallHome supported or not. Description Explains about the defined alert definition.
Event and Alert feature Disabling the Event and Alert feature disables all the notifications and you do not receive any notifications that are generated for alerts. To receive the notifications for generated alerts in future, enable this feature. To enable or disable this feature, go to Settings > Notifications > Configure Alerts > Configure Notification, and enable or disable the Event and Alert feature depending upon the requirement.
Component Distributed Device Fabric Port IP Port IP Port Logical Unit 140 Notifications Condition ID Event Source 0xc0001 DIRECTOR 0xd0001 DIRECTOR 0x40001 DIRECTOR 0x40002 DIRECTOR 0x40003 DIRECTOR 0x30014 DISTRIBUTEDDEVICE 0x3001b DISTRIBUTEDDEVICE 0x90001 TARGETPORT 0x9000e TARGETPORT 0x110001 IPPORT 0x120003 COMMUNICATIONSPATH 0x150008 VIRTUALPORT 0x15000d VIRTUALPORT 0x150010 VIRTUALPORT 0x150011 INTERFACE 0x150018 VIRTUALPORT 0x150019 INTERFACE 0x15001d INT
Component Meta Volume Storage Array Storage View Storage Volume Condition ID Event Source 0x20005 LOGICALUNIT 0x20006 LOGICALUNIT 0x20009 LOGICALUNIT 0x2000d LOGICALUNIT 0x30005 METAVOLUME 0x30010 METAVOLUME 0x30011 METAVOLUME 0x30012 METAVOLUME 0x30017 METAVOLUME 0x30019 METAVOLUME 0x3001c METAVOLUME 0x3001d METAVOLUME 0x3001e METAVOLUME 0x3001f METAVOLUME 0x30020 METAVOLUME 0xf0001 METAVOLUME 0xf0002 METAVOLUME 0xf0003 METAVOLUME 0xf0004 METAVOLUME 0x8A00010E
Component System Virtual Volume Condition ID Event Source 0x3001a STORAGEVOLUME 0x180001 DISKID 0x180002 DISKID 0x190001 DISKID 0xb0001 SYSTEM 0xb0001 SYSTEM 0x30003 VIRTUALVOLUME 0x30006 VIRTUALVOLUME 0x3000a VIRTUALVOLUME 0x3000c VIRTUALVOLUME 0x3000d VIRTUALVOLUME 0x30016 VIRTUALVOLUME 0x90002 VIRTUALVOLUME 0x90003 VIRTUALVOLUME 0x90004 VIRTUALVOLUME 0x90005 VIRTUALVOLUME 0x90006 VIRTUALVOLUME 0x90007 VIRTUALVOLUME 0x90008 VIRTUALVOLUME 0x90009 VIRTUALVOLUME 0
Test Alerts The Test Alerts provides the information about the alerts are generating or not. Prerequisites The Event Alert Feature should be enabled. Steps 1. From the UI, go to the Settings > Notifications or go to the Notifications > Platform Alerts > MORE > Configure Alerts. The Configure alerts page is displayed. 2. Select More > Test Alerts . A window is displayed with the list of following alerts to test: a.
Platform view properties Platform alert tab Severity Indicates the urgency of alert: CRITICAL-A condition has occurred that can obstruct the functionality or can lead to failure of the other components. ERROR-An error has occurred that has a significant impact on the system and must be rectified immediately. WARNING-An error has occurred that you should be aware of but does not have a significant impact on the system. For example, a component is working, but its performance may not be optimum.
External RCA Represents external root cause analysis of the issue. Notes It shows the notes which are added by user. Debug Events Associated legacy debug events generated through firmware. Additional details tab To view additional information about the alert in name-value pair, click the Additional details tab. Logs tab It is for historical alerts only. It provides the list of creation and last updated time for the same alert has occurred.
Last Updated Date and time when the status of the alert is last changed. Notes It shows the notes which are added by user. Logs tab It is for historical alerts only. It provides the list of creation and last updated time for the same alert has occurred.
11 Help Topics: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Create Mobility Job wizards Supported host types Storage group properties Director properties Cluster properties Metro node Witness status Configure Settings Metro node cluster status Product version Step 1: Select or create a consistency group for the virtual volume Step 1: Create a consistency group Step 2: Select volume options Step 3: Select a storage pool Step 3: Select a pool for each mirror
• • • • • • • • Storage view properties Storage volume properties Provision Job properties The Distributed Consistency Groups view Create Virtual Volumes dialog box Platform view properties Hardware view properties Configure alerts properties Create Mobility Job wizards Mobility contains two wizards (Create Extent Mobility wizard and Create Device Mobility wizard) that allow you to create the wanted type of mobility job.
● Default (use this type for all hosts not listed above) Storage group properties Storage Group Name The name of the storage group. Storage Array The name of the array on which the storage group was created. Array Management Provider The name of the array management provider managing the array. Policy The name of the policy associated with the storage group. Number of Volumes The number of volumes currently in the storage group. Parent The name of the parent storage group (if applicable).
Transition Indications If the operational status is not OK, this field lists the reasons why. Transition Progress Displays the progress of the transition, if available. Health Indicates the health of the cluster. See metro node cluster status. Health Indications Lists the reasons for the unhealthy state. Operational Status Indicates how the cluster is functioning. See metro node cluster status. To view version details for the cluster, click Version Details at the bottom of the window.
Operational state Definition in contact This cluster is in contact with its peer over the inter-cluster network. Rebuilds may be in progress. Subject to other system-wide restrictions, I/O to all distributed virtual volumes in all synchronous consistency groups is allowed from the perspective of metro node Witness. cluster partition This cluster is not in contact with its peer and the Cluster Witness server has declared that two clusters partitioned.
The idle timeout is based on the URL used to access the GUI. Therefore when you access the GUI on cluster 1 and set the idle timeout, it will apply only to cluster 1. If you log into cluster 2, the idle timeout dialog will not have the same value as that of cluster 1, because the URL is different. The value of the timeout field can be an integer value between 1 and 12 if the field unit value is set to hours.
Status Type Values Definition Degraded The cluster is not functioning at an optimal level. This may indicate non-functioning remote virtual volumes, unhealthy devices or storage volumes, suspended devices, conflicting director count configuration values, out-of-date devices, and so forth. Unknown Metro node cannot determine the cluster's health state, or the state is invalid. Critical failure The cluster is not functioning and may have failed completely.
Mgmt server software The version of management server software running. Cluster Witness Server Software The version of Cluster Witness server software running (if Cluster Witness is installed). Directors Lists the name and version number of each director in the cluster. Step 1: Select or create a consistency group for the virtual volume Select or create a consistency group for the virtual volume. To view the topology of a consistency group, select the group in the list.
● For a distributed consistency group, select the appropriate check box to enable mirroring at one cluster or both clusters, or leave both check boxes clear to disable mirroring. Number of Volumes — The number of volumes to create. You can create a maximum of 10 volumes at a time. Each volume will have the same RAID geometry. NOTE: For Unity arrays, you can provision only one volume at a time. Capacity Per Volume — The size of each volume. Select the size in MB, GB or TB. The minimum size is 150MB.
Selecting a storage group By default, metro node will automatically select a storage group for the newly created volumes, based on compatible policies, and the lowest amount of volumes in the group. However, if you want to select the storage group, click the Storage Group drop-down box, and then select Select from list to show the available storage groups. NOTE: For V3GR arrays only, the Storage Group drop-down box changes to a selection list because a storage group is required.
Selecting a storage group By default, metro node will automatically select a storage group for the newly created volumes, based on compatible policies, and the lowest amount of volumes in the group. However, if you want to select a storage group, click the Storage Group drop-down box, and then select Select from list to show the available storage groups to choose from. NOTE: For V3GR arrays only, the Storage Group drop-down box changes to a selection list because a storage group is required.
Selecting a storage group By default, metro node will automatically select a storage group for the newly created volumes, based on compatible policies, and the lowest amount of volumes in the group. However, if you want to select a storage group, click the Storage Group drop-down box, and then select Select from list to show the available storage groups to choose from. NOTE: For V3GR arrays only, the Storage Group drop-down box changes to a selection list because a storage group is required.
Step 6: View results This screen shows the results of the provisioning request. ● To manage the provisioning job, click the View job Status link to open the Provisioning Jobs Status screen. ● To provision more storage, click Provision More in the lower-right corner of the screen to go back to Step 1 in the wizard, otherwise, click Done to close the wizard. Step 2: Select volume options Select high availability options, synchronization options, and then enter a name for the volume.
the entire capacity of the source storage volume. To ensure high availability, the array selected to provide the source storage is automatically filtered from the list of arrays available for the target storage. Select only one source and one target storage volume. The storage volume can be claimed or unclaimed. NOTE: To create a thin volume, the selected source and target storage volumes must come from the same array family, and must also be thin capable.
Show Logical Units Name (VPD ID) The VPD identifier for the logical unit. Storage Volume The storage volume to which this logical unit belongs. LUNs The LUN number on the array. Connectivity The connectivity status of the logical unit. Visibility Indicates how the logical unit is visible to the controllers. See possible values. ALUA Support Indicates if Asymmetrical Logical Unit Access (ALUA) is supported on the array.
With a unique scale-up and scale-out architecture, metro node’s advanced data caching and distributed cache coherency provides workload resiliency, automatic sharing, balancing and failover of storage domains, and enables both local and remote data access with predictable service levels. System management In addition to the web-based Graphical User Interface (UI), metro node also supports a command-line interface (CLI) for managing your system.
Expansion Method The expansion method available for this volume. Possible values: concatenation — The volume can be expanded using Concatenation or RAID-C expansion. storage-volume — The volume can be expanded to the Expandable capacity using storage volume expansion. not-supported — The volume does not support expansion. Expandable By The amount of space that is available for volume expansion. A volume that has an Expandable by of 0 can still be expanded using concatenation.
Field/Column Description System ID The array's ID number for the storage volume. Initiator The Port WWN of the metro node backend port. Target The Port WWN of the storage array target port. LUN The Logical Unit Number for the storage volume. Consistency group properties Consistency Group Name The name of the consistency group. You can change the name in the properties dialog box. Detach Rule (metro node Metro only) The detach rule that applies to the consistency group.
Thin Capable Indicates if the underlying storage volume is thinly-provisioned. Storage Array Family The family of arrays that the supporting array belongs to. Possible values: ● XTREMIO — The array belongs to the XtremIO family of arrays. ● CLARiiON — The array belongs to the VNX or Unity family of arrays. ● SYMMETRIX — The array belongs to the VMAX or Symmetrix family of arrays. ● Mixed — The supporting arrays belong to different array families.
Register Array Management Provider dialog box Provider Type The type of AMP used to manage the array. When provisioning from XtremIO arrays, select REST. For all other arrays, select SMI-S. For XtremIO v3.0, metro node requires one REST AMP per array. Therefore, if you are using multiple v3.0 arrays, register a REST AMP for each array. For XtremIO v4.0, one REST AMP can manage multiple v4.0 arrays. When you enter the array credentials, metro node automatically detects the array versions managed by the XMS.
Thin Capable Indicates if the underlying storage volume is thinly-provisioned. Storage Array Family The family of arrays that the supporting array belongs to. Possible values: ● XTREMIO — The array belongs to the XtremIO family of arrays. ● CLARiiON — The array belongs to the VNX or Unity family of arrays. ● SYMMETRIX — The array belongs to the VMAX or Symmetrix family of arrays. ● Other — metro node does not recognize the array or does not support creating thin volumes on the array.
None — ALUA is not supported on the array. Connectivity Status The connectivity status of the logical unit. Visibility Indicates how the logical unit is visible to the controllers. Possible values: Active optimized — All commands and task management functions can be sent on this path; this path has the highest performance (ALUA arrays only).
Start Time The date and time the job started. Note that N/A may display in this field if you are connected to one cluster and view the properties of a job that was started on another cluster. Transfer Speed The maximum number of bytes of data transferred at a time from the source to the target. You can change the transfer speed in the properties dialog box while the job is in the queue or in progress. Mobility job transfer speed provides more information on selecting the transfer speed.
Storage volume properties Storage Volume Name The name of the storage volume. You can change the name in this field. Use Indicates whether the storage volume is Claimed, Unclaimed, or Used. Used By The name of the extent created from the storage volume. Storage Volume Type Describes the type of data stored on the storage volume: Data protected, Metadata or Normal Integrated Services The name of the supporting storage array.
Consistency Group The name of the consistency group for the volumes (if any). Total Capacity The total capacity of the volumes being created. Thin Indicates if the volumes are thin. Resources affected at Storage Array — The storage array from which the volumes were provisioned. Storage View — The storage view selected for the volumes (if any). Storage Pool — The storage pool from which the volumes were created.
Create Virtual Volumes dialog box Use this dialog box to create a virtual volume from an existing device. The Available Devices list shows all available top-level devices. Select a device from the list and then click Add to add the device to the Selected Devices list. To create thin virtual volumes, select the Create thin virtual volumes checkbox and make sure that all selected devices are thin-capable.
Event Source ID Unique ID for the source of the event. Helps to narrow down to the final component . Resource It shows the resource for which the issue has occurred. Count It represents the number of times the same alert is generated over the selected period. This column is available for historical alerts only. Scope Incarnation Represents unique ID assigned to each director and cluster. Creation Date Date and time when the alert is generated.
Severity Code Represents the numerical code for the corresponding severity of the alert. Version Represents version of the certificate. Message ID Indicates ID of the event record. Host Display the host details. Host Name Represents IP address or network name of the remote host. AppName Represents the device or application that originated the message. Creation Date Date and time when the alert is generated. Last Updated Date and time when the status of the alert is last changed.
