HPE Nimble Implementation Specialist Lab Guide
HPE Nimble Implementation Specialist Lab Guide
Specialist
Lab guide
Rev. 4.3
Confidential – For Training Purposes Only
Use of this material to deliver training without prior written permission from HPE is prohibited.
HPE Nimble Implementation Specialist - Lab Guide
The information contained herein is subject to change without notice. The only warranties for
HPE products and services are set forth in the express warranty statements accompanying
such products and services. Nothing herein should be construed as constituting an additional
warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or
omissions contained herein.
This is an HPE copyrighted work that may not be reproduced without the written permission of
Hewlett Packard Enterprise. You may not use these materials to deliver training to any person
outside of your organization without the written permission of HPE.
Printed in the US
Table of Contents
Requirements/login instructions ............................................................................................................... 4
Lab 1: Initialize an Array ............................................................................................................................. 5
Background ............................................................................................................................................ 5
Lab Topology ......................................................................................................................................... 5
Task 1: Launch Nimble Setup Manager ............................................................................................... 6
Task 2: Subnet Configuration ............................................................................................................. 11
Task 3: Post Setup Testing ................................................................................................................. 15
Lab 2: Basic Volume Creation ................................................................................................................. 17
Task 1: Create a volume ...................................................................................................................... 17
Task 2: Create a Volume Collection ................................................................................................... 20
Task 3: Create an Initiator and an Initiator Group ............................................................................ 23
Lab 3: Windows Host SetUp (NCM)......................................................................................................... 25
Background .......................................................................................................................................... 25
Task 1: Launch NCM and connect to a volume ................................................................................ 25
Task 2: Examine the newly connected volume ................................................................................ 27
Task 3: Return to the Windows host to prepare and mount the volume ....................................... 28
Lab 4: Snapshots and Data Recovery ..................................................................................................... 30
Background .......................................................................................................................................... 30
Task 1: Create Data.............................................................................................................................. 30
Task 2: Simulate a data loss event .................................................................................................... 32
Task 3: Create a Zero-Copy Clone ..................................................................................................... 34
Task 4: Connect to the clone and recover the data ......................................................................... 37
Task 5: Disconnect and delete the clone .......................................................................................... 39
Lab 5: Replication Partner Configuration ............................................................................................... 41
Background .......................................................................................................................................... 41
Lab Topology ....................................................................................................................................... 41
Task 1: Configure the Upstream Array .............................................................................................. 42
Task 2: Configuring the Downstream Array...................................................................................... 44
Conclusion/Review ................................................................................................................................... 46
Objectives
Provide a common set of lab activities to demonstrate the following
a. Perform the Initial Setup of the HPE Nimble Storage Array
b. Perform the Initial Configuration of the HPE Nimble Storage Array
c. Create Volumes on the HPE Nimble Storage Array
d. Conduct Data Protection using the HPE Nimble Storage Arrays Snapshots
e. Conduct Data Protection using the HPE Nimble Storage Arrays Replication
Requirements/login instructions
Lab Requirements
Ensure that you have a Windows (preferred) or MAC client system with Remote Desktop
(RDP) installed.
Login Instructions
1. Follow access instructions provided to you by the lab administrator/instructor.
2. On the RDP login dialog, input the following credentials and click OK:
User name – student@edu.lab
Password – MSoft01!
Lab Topology
___________________________________________________________________________
b. Click on the radio button on the array listed and click on the Next button.
4. You will be prompted with an information box alerting you to the fact that Setup Manager will
launch the default browser with default Microsoft IP address (169.254.x.x). Click OK to continue
the array setup in the browser.
5. When the browser launches (Chrome), it will present you with a security warning. Click
Advanced and then click on the “Proceed to…” link.
6. You will be presented with a license agreement. Read the agreement, scroll down, check the
box to acknowledge and then click on the Proceed button.
7. At the subsequent array setup screen, you will keep the default option of setting up but not joining
a group and click Next.
8. Configure the array name, group name, management settings and password:
a. Enter the following data:
i. Array Name: prod-array-01
ii. Group Name: gr-prod-arrays
iii. Management IP: 192.168.100.100
iv. Netmask: 255.255.255.0
v. Default Gateway: 192.168.100.1
vi. Domain Name: edu.lab
vii. Password: Nimble01!
viii. Confirm Password: Nimble01!
b. Click on Finish when you are done.
NOTE: It may take several minutes to initialize but you should get a success message when
done. At that point, click Continue.
9. You should then be presented with a browser window with the management IP that you entered during
setup (192.168.100.100)
10. Click Advanced and then click on the “Proceed to…” link.
11. You will then presented with the login page of the GUI. The username “admin” should be
prepopulated. Enter the password Nimble01!
12. You may be presented with a login banner/usage warning, if so, click OK to bypass and continue.
2. Configure Subnets
You will configure the array to use three subnets -- one subnet for management only (on eth1 &
eth2) and two subnets for data only, data1 (eth3, eth5) and data2 (eth4, eth6).
a. Set the Management subnet as a management only network
i. Using the Traffic Type drop down, select Mgmt Only
b. Click Add to add the first Data Only Subnet, data1, and enter the following data:
i. Subnet Label - data1
ii. Network - 172.0.1.0
iii. Netmask - 255.255.255.0
iv. Ensure the Traffic Type drop down is set to Data only
v. Discovery IP - 172.0.1.100
c. Click on Add to add the second Data Only Subnet, data2, and enter the following data:
i. Subnet Label - data2
ii. Network - 172.0.2.0
iii. Netmask - 255.255.255.0
iv. Ensure the Traffic Type drop down is set to Data only
v. Discovery IP - 172.0.2.100
d. Click NEXT
NOTE: Best practice configuration dictates that if you have two network cards, you should split
the interfaces into separate switches. For simplicity sake, Nimble recommends that you
configure even numbered interfaces into one switch and odd number interfaces into the
second switch.
a. You’ll notice that eth1 should already be assigned to the management subnet – leave it
unchanged
b. Set eth2 to the management subnet by using the Subnet drop down and selecting
Management
c. Set eth3 to use the data subnet, data1, by using the Subnet drop down and selecting
data1.
i. In the Data IP Address text field, enter the IP address: 172.0.1.101
d. Set eth4 to use the data subnet, data2, by using the Subnet drop down and selecting
data2.
ii. In the Data IP Address text field, enter the IP address: 172.0.2.101
e. Set eth5 to use the data subnet, data1, by using the Subnet drop down and selecting
data1.
iii. In the Data IP Address text field, enter the IP address: 172.0.1.102
f. Set eth6 to use the data subnet, data2, by using the Subnet drop down and selecting
data2.
iv. In the Data IP Address text field, enter the IP address: 172.0.2.102
g. Set Controller A to IP address: 192.168.100.101
h. Set Controller B to IP address: 192.168.100.102
i. Click Next
4. Set Up Domain Information
a. Enter edu.lab.com for the domain name.
b. Input the DNS server IP as 192.168.100.3 and click Next
5. Set up Time Information
a. Configure the Time (NTP) Server to time.nimblestorage.com
b. Set the time zone region to America and the Country/State/City value to Los_Angeles
via the respective drop down menus.
b. Click Next
6. Configure Support Services
a. Email Alerts
i. The Send From Address should be auto populated with gr-prod-arrays@edu.lab.com, if
not enter the address in the Send From Address field
ii. Click Add and input admin@edu.lab.com for the Send To address
iv. Leave the remaining settings at default ensuring the Send event data to Nimble Storage
Support and Allow Nimble Storage Support to collect analytics data automatically
from the array are checked and Use Proxy server is unchecked.
b. Click Finish
7. Setup Complete
a. The basic installation process is complete.
b. Click on the Continue button. This will take you to the GUI Home screen. You
may be presented with a browser security warning again so just use the typical
steps used earlier in the lab to advance (click on Advanced, then Proceed…).
NOTE: There’s a chance you may need to log back into the GUI (admin/Nimble01!) if you have
left your system for a period of time
NOTE: In a production environment, you would click on the Test Diagnostics for Nimble
Analytics Settings button to verify AutoSupport is functioning properly.
This action performs several tests and each will display a green light indicating success. To
expand and review the details of each test, you can click on the arrow next to the green light.
After that, you would then click Send Diagnostics For Nimble Analytics. The Send
Diagnostics For Nimble Analytics button is used if at any point you wish to manually initiate
analysis from Nimble Support.
Since this is a lab environment, you may not be able to run the test successfully; however,
when you perform these steps on a production network, you should see a message similar to the
one shown above.
b. Scroll down and click on the Test button in the button right of the screen.
NOTE: You may skip steps 1-4 if you already have an active UI window to the production
array.
1. Launch Chrome and input the IP address of the production array (192.168.100.100) and hit Enter.
2. Input the username admin and password Nimble01! and click on Log In.
3. You may be presented with a browser security message if so, click on Advanced and the Proceed…link.
4. You may be presented with a login banner/usage warning, if so, click OK to bypass and continue.
5. Click on the Manage workspace and then select Data Storage from the drop down.
This screen provides a list of the volumes on the array and their sizes
6. Click on the plus sign (+) under Volumes to add a new volume
e. Since you’ll be addressing the volume collection and the initiator group configurations in a
subsequent task, set the Data Protection (Volume Collection) and Access (Initiator Group) values
as Not Protected and Unrestricted Access via their respective drop down options. Additionally,
you will not be configuring a CHAP account for this lab exercise so you will set the CHAP Account
field to Unrestricted Access as well.
NOTE: When creating a volume for the first time the available items in the drop down
menus for Data Protection, Access, and Chap Account will be generic. Once you have
created protection schedules, initiator groups, and chap accounts these menus will have
more options.
If you already had a volume collection, initiator group and CHAP account created, you
could associate them to this volume at this point in the configuration. Since we are
configuring Data Protection and Access in a subsequent step, you are temporarily
setting this values to Not Protected and Unrestricted Access respectively. As a result,
you will see a warning after setting these access values to unrestricted. Typically, as
best practice, you would configure these values to restrict access. For simplicity sake in
this lab, we are omitting CHAP configuration all together.
f. When you have finished configuring the parameters defined above, click on Create to create the
volume. You should see a success message.
2. You are now at the Volume Collections configuration area. Just as you did when you created a volume, click
on the plus sign (+) to add a new Volume collection.
3. Input the VC name vc-ms-fileserver within the Name field. Start From Protection Template will be left at
default of No protection template and Replication Partner the Synchronization Service at the default of
None.
4. You will configure three schedules: Hourly, Minutes and Daily. Start with Hourly.
In the first schedule name field type Hourly.
5. Leave all other values at default and click on Add Schedule. Depending on your window size, you may
need to scroll down.
6. In the next schedule name field type 2mins. Change the Every value to 2 and the time dropdown to
minutes.
NOTE: You are setting the interval to 2 minutes in order to quickly build snapshots for a
subsequent lab. Also be aware that this entry does not accept spaces.
7. Leave all other values at default and click on Add Schedule. You may need to scroll down.
8. In the next schedule name field type Daily. Keep the Every value to 1 and change the time dropdown to
days. Leave all other values at default.
10. Your schedules are created and now you can add your volume to your volume collection. Highlight the
volume under the available section by clicking on it and then and click on the Add button to move it to
Selected.
2. You are now at the Initiator Groups configuration area. Just as you did when you created a volume and a
VC, click on the plus sign (+) to add a new Initiator Group.
3. Input the name ig-fileserver and keep the default for Use all configured subnets.
6. You’ll need to get the IQN from Nimble Connection Manager (NCM), which you’ll use more extensively in
the next lab. If needed minimize your browser window to reveal the desktop.
7. In the bottom third of the NCM window you’ll see the IQN value to the right of Initiator Name.
8. Double click on the IQN value to select it (it should be highlighted blue).
9. Use the Ctrl + C key combination on your keyboard to copy the value to the clipboard.
10. Return to the array UI. Click in the IQN field and paste the IQN value from your clipboard using the Ctrl + V
key combination.
11. Leave the IP address field with the wildcard value of * to allow access from any IP address from the network.
If you were to specify an IP address, access would be determined by both a match of the IQN and the IP
address that was requesting access.
12. Click Create and you will be presented with a success message indicating that the initiator group, ig-
fileserver, was added successfully. Also notice the newly created initiator, ms-fileservers, is reflected
under the Initiators tab.
NOTE: Depending the firmware version of the array, you may need to click on the initiator
group name, ig-fileserver, to view the details/tabbed screen area shown below.
a. Click on Add button about mid-way down the screen and to the right.
b. Click on the volume ms-fileserver-01 to select it (you may need to refresh the screen to see the
volume). Notice the “red x” on the volume indicating it is currently disconnected.
c. Click Connect.
d. The Connect to Target dialog box appears. Click on the OK button to accept all defaults – the
volume should now have a green icon indicating a successful connection.
What do you see in the Recent Tasks area in the lower portion of the screen?
_______________________________________________________________________
e. Click on the Properties button
f. Examine the Volume Properties
NOTE: Some of the key information listed, beyond the volume name, is the target IQN
and the list of connections.
5. Click on the OK button to close out the volume properties
5. Click on the volume name – ms-fileserver-01, it will bring you to the Data Access tab.
Task 3: Return to the Windows host to prepare and mount the volume
In the final task of the lab you will focus on the disk management settings of the Windows host by
preparing and mounting the volume.
1. Bring the Volume Online
a. If necessary, minimize your browser window to expose the desktop and bring up Server
Management by clicking on the icon in the task bar of the server.
b. From the Upper right corner of the screen, Select Tools Computer Management
v. Click Next
vi. Click Finish
Your volume now has a file system on it. Notice that the volume is online and is formatted for NTFS
3. Launch Disk Tools from the shortcut icon on the server desktop.
4. Click Run when prompted on the security warning to open the File Generator program.
5. Adjust the default configuration settings to generate 5 files. Within the Generate box under the
Number of files section, type 5 and hit Enter. Leave the file size at the default setting (1GB) to
produce roughly 5GB total of data.
NOTE: The File Generator program may not reflect 5GB in total size on the configuration
screen until you close the program and open it back up again.
6. Set the output folder to Lab Data on the volume (E:\Lab Data).
You can also examine the progress of the files being written in the lower left of the program
9. Note the approximate time (from the right side of the task bar in your RDP host system clock) that
your data was fully written to the volume, here:
____________________
Where do you need to go on the array UI to verify how much data is written on the
volume?
____________________________________________________________________________
10. Wait several minutes and ensure that your 2Mins protection/snapshot schedule, has created at
least one snapshot from which you can recover the data in the Lab Data folder in the event of
data loss.
11. Unless you already have an active window, launch Chrome and initiate a UI connection to the
production array (192.168.100.100 admin/Nimble01!)
12. From the Manage workspace, go to Data Protection and then click on your Volume Collection,
vc-ms-fileserver.
13. After clicking on the Volume Collection, vc-ms-fileserver, click on the Snapshot Collections tab.
14. The snapshots are presented chronologically with the most recent snapshots at the top of the list by
default. In step 9 of this task, you noted the time that your data was written to the volume.
So in this example, if your data was fully written by 11:07 with no changes, either of the top two
snapshots (since they took place after 11:07) would be appropriate choices from which to
recover the data in the Lab Data folder should a data loss event occur. Ensure that you have at
least one snapshot to recover from before moving on to the next task.
1. From File Explorer, return to the E drive (ms-fileserver-01), highlight all the contents of the Lab
Data folder and delete. (If prompted by the system to permanently delete, click Yes)
2. All the data is now gone from the Lab Data folder on the ms-fileserver-01 volume.
3. Take note of the time that you deleted the files (RDP system time) so that you can choose an
appropriate snapshot to recover from in a subsequent task:
____________________
Why wouldn’t you pick the most recent snapshot in this case?
________________________________________________________________________________
________________________________________________________________________________
2. Identify the first snapshot that was taken after all the data was originally written. Click in the
checkbox to the left of it to select it.
b. By default, the system will append “clone” to the original volume name. For the sake of
simplicity, just keep the default name of ms-fileserver-01-clone and click OK.
You can now see the clone has been created and that it is online (green disk icon).
The cloned volume is now accessible via the F drive within File Explorer.
4. Select all the files in the Lab Data folder on the F drive and select Copy
5. Return to the E drive where the ms-fileserver-01 volume resides, open up the Lab Data folder
ii. In the Disconnect All Connections dialog window, click on the Remove
connect on startup checkbox
iii. Click on Yes button
d. The clone is now disconnected
_____________________________________________________________________________
_____________________________________________________________________________
Lab Topology
4. Click Next
5. You will not configure a QoS policy. Click Create to finish the partner configuration.
___________________________________________________________________________
Notice that the downstream replication partner has been configured successfully on the
production array but is unreachable. Why?
___________________________________________________________________________
8. Click the checkbox next to the Replication Partner name (gr-prod-arrays) in order to select it and click Test.
What is the replication partner status of the production array (you may need to refresh
the screen) and what does this tell you about the relationship between both arrays?
____________________________________________________________________________
____________________________________________________________________________
If the connection attempt failed, what could be the reason(s)? Troubleshoot until you get
an “Allive” status between the partners.
____________________________________________________________________________
____________________________________________________________________________
Conclusion/Review
These labs took you through some of the common/basic configurations on Nimble Storage arrays. The
tasks you were introduced to included:
• Array initialization
• Volume creation
• Volume Collection configuration
• Using snapshots to recover lost data
• Configuring and testing communication between replication partners.