Deploying Silver Peak Velocity with NetApp SnapMirror. October 2012

Transcription

1 Deploying Silver Peak Velocity with NetApp SnapMirror October Page

2 Formatting Conventions... 3 Prerequisites... 3 Overview... 3 VMware Configuration this must be completed at the primary and DR sites... 4 Deploying the Silver Peak Velocity Virtual Machine this must be completed at the primary and DR sites... 6 Initial Silver Peak Configuration this must be completed at the primary and DR sites Configuring Silver Peak Velocity this must be completed at the primary and DR sites NetApp Configuration this must be completed at the primary and DR sites Links Appendix A Silver Peak Velocity and NetApp SnapMirror Configuration Sheet Page

3 Formatting Conventions Italic font used for words that require special attention or as a placeholder for information that must be user supplied. Monospaced font Command names and information displayed on a system console. Also used for file, path and directory names. Bold monospaced font Words and characters that the user must type. Typed characters are always in lowercase letters, unless the program is casesensitive. Prerequisites Download Silver Peak Velocity OVA file Silver Peak Velocity licenses IP address information for appendix A Read this entire document before beginning configuration A configured and working VMware environment Overview This document describes the configuration of Silver Peak Velocity appliances for NetApp SnapMirror deployments. For this deployment the Silver Peak Velocity appliance will act as the next-hop for the SnapMirror traffic. The NetApp filers, remote and local, will have a route add statement added to the configuration. The Route Add statement will forward any traffic destined for the remote system to the Silver Peak Velocity appliance. The Velocity appliance will optimize the traffic and then forward it across the WAN to the remote site. Note that while this document only shows one side of the configuration, the remote site must have all of the reciprocal settings configured. 3 Page

4 VMware Configuration this must be completed at the primary and DR sites To begin, a new switch must be created in VMware for interfaces that won t be used by the Silver Peak Velocity appliance. The Velocity appliance has four interfaces, mgmt0, mgmt1, LAN0 and WAN0. For this deployment only the mgmt0 and WAN0 interfaces will be used. The remaining interfaces must be mapped to a vswitch that is not connected to the production LAN. 1. Open the vsphere client and select the server where the Silver Peak Velocity appliance will be deployed. 2. Select the configuration tab and click on Networking. 3. Select Add Networking. 4 Page

5 4. Add a Virtual Machine network and click next. 5. By default the vsphere client will select a physical NIC to connect the switch to the LAN. Because we are not using the virtual interfaces from the Velocity appliance that will be connected to the switch the physical NIC should be unchecked. With the physical NIC unchecked this switch will be isolated and not connected to the LAN. 5 Page

6 6. Give the new virtual switch a name and click next. 7. Click finish and the switch will be created. Deploying the Silver Peak Velocity Virtual Machine this must be completed at the primary and DR sites 8. To deploy the Velocity appliance open the vsphere client and select the server where the VM will be deployed. 6 Page

7 9. In the vsphere client click File->Deploy OVF Template. 10. Browse to the location where the Velocity appliance has been downloaded. a. Select the Velocity OVF and click Open. b. Click Next. 7 Page

8 11. Give the virtual machine a meaningful name. 12. Select an available datastore for the Velocity appliance. a. The data store that houses the Velocity appliance should not be replicated and optimized by the Velocity appliance. If the data store with the Velocity virtual machine is replicated, and optimized by the Velocity appliance, there is the potential for IO constraint as this is recursive optimization. With recursive optimization data that is being optimized is read from disk, deduplicated and written back to the same disk. The Velocity appliance will not recognize the data as being a duplicate because it stores all data encrypted on disk. b. Be sure to use a data store that has sufficient performance. 8 Page

9 13. Select Thick Provision Eager Zeroed. 14. When mapping network interfaces, only two of the available Source Networks will be used. Mgmt0 and wan0 should be mapped to the production network. If a management only network exists, map mgmt0 to a destination network that is connected to this network. Wan0 must be mapped to a destination network that is physically connected to the production network. Connect mgmt1 and lan0 to the network that was created earlier in step 6. 9 Page

10 15. Select Power on after deployment and click Finish. 16. Wait for the VM to be deployed and powered on When the Velocity VM has been deployed and powered on select it and launch a console connection. 19. Click in the console window and press Enter. 20. To login use the default username and password admin/admin. 21. Type show interfaces mgmt0 at the command line. 10 Page

11 22. Note the IP Address for mgmt0. We will use this address to connect to the GUI and continue configuration. 23. Close the console window and open a web browser. 24. Type the ip address of the mgmt0 port on the Velocity appliance into the web browser and press enter. 11 Page

12 Initial Silver Peak Configuration this must be completed at the primary and DR sites 1. Login and begin with the Silver Peak configuration wizard. The default user name and password is admin/admin. 2. Click Next> to begin the Configuration Wizard. 3. Assign the appliance hostname. If a static management IP addresss is required it can be assigned here. 12 Page

13 4. Set the date, time and optionally change the management password. The license key must also be entered during this step. The license key is included in the that includes the download link for the Velocity appliance. *Note that there is a appliance. different license key required for each Velocity 5. Select Router/Out-of-Path mode and click Next>. 13 Page

14 6. Assign the appliance IP address, next-hop IP address (typically the WAN router/default gateway) and set the max bandwidth. The max bandwidth will control how much bandwidth the Silver Peak Velocity appliance uses for replication across the WAN. The appliance IP address will also be the WAN0 IP address. *note that the Silver Peak Velocity Appliance and the NetApp filer need to be on the same subnet and on the same switch if possible. 7. Verify the configuration, click apply, and wait for the system to reboot. 14 Page

15 Configuring Silver Peak Velocity this must be completed at the primary and DR sites 8. When the appliance is finished rebooting, enter the username and password and click login. 9. Create a manual tunnel between the Silver Peak Velocity appliances. a. Select Configuration>Tunnels b. Select Add and use the following settings: Name: use a name to describe this tunnel, for example tunnel-toremote-site Admin: up MTU: 1500 Local IP: the local system IP address (this will be filled in already) Remote IP: the remote Velocity appliance system IP address. Auto Max BW: checked. Max BW can be set if replication traffic needs to be limited to a specific throughput. 15 Page

16 Min BW: 32 Mode: GRE *UDP and IPSEC are additional options for the tunnel mode. If IPSEC is chosen all traffic between the Silver Peak Velocity appliances will be encrypted. c. After entering the tunnel information the tunnel state willbe down - in progress. d. When the tunnel has been successfully configured the status will be changed to up active. *note that when the secondary site is configured an auto-tunnel will be created. Delete the auto-tunnel and manually configure a tunnel back to the primary site. 16 Page

17 10. Create a Route Policy for SnapMirror. a. Select Configuration->Route Policy b. Select Add and use the following settings: Priority: 10 Protocol: ip Src Subnet: the local subnet where the Silver Peak Velocity appliance and the NetApp filer are located Dst Subnet: the remote subnet, at the DR site, where the second Silver Peak Velocity appliance and destination NetApp filer are located Application: SnapMirror DSCP: any Tunnel: use the tunnel that was created in step 8. Tunnel Down Action: Drop The source and destination subnet can also be the IP address of the local and remote NetApp filer if a single IP address is used for SnapMirror on both sides. If more than one IP address is used then the subnet addresss should be entered. For example, a local filer with an IP address of and a subnet mask of would be entered as /24 in the source field. If the remote filer has an IP address of and a subnet mask of it would be entered as /24 in the destination field. *note that the Src and Dst subnet information will be reversed when configuring the remote Velocity appliance. 11. Click the red Save Changes button. 17 Page

18 NetApp Configurationn this must be completed at the primary and DR sites The section of the deployment guide should not be performed until the Silver Peak Velocity appliances have been configured and the tunnel is listed as up. The first step in configuringg the NetApp filers is to redirect the SnapMirror traffic to the Silver Peak Velocity appliance. To accomplish this, the Route Add command will be used to make the immediate change. The /etc/rc file will be edited to make the change persistent across reboots. This guide demonstrates the configuration on one of the NetApp filers. The second filer will need to have reciprocal changes made before optimization will begin. 12. Open an SSH or console connection to the NetApp filer. 13. Login to the filer. 14. Ping the System IP Address of the local Velocity appliance using the following command: ping x.x.x.x. Replace x.x.x.x with the IP address of the local Velocity appliance. For the filer at the DR site the local Velocity appliance will also be at the DR site. 18 Page

19 15. Add a path to the remote NetApp filer using the Velocity appliance as the next hop with the following command: route add x.x.x.x y.y..y.y 1. x.x.x.x is the IP address of the remote NetApp filer and y.y.y.y is the system IP address of the local Silver Peak Velocity appliance. *note the 1 that has been entered after the Velocity system IP address. This is the route metric and is required. 19 Page

20 16. To verify the route add command was successful use the comman nd route s. To make the route add persistent the /etc/rs file must be edited. To make this edit map a drive to the C$ share on the filer. To map a drive click the start button in Windows and open Computer. Click the Map network drive button. 17. Enter the IP addresss and share name in the Folder: field. 20 Page

21 18. When the drive is mapped a new window will open showing the contents of the C$ share. 19. Double click on the etc directory and browse to the rc file. 21 Page

22 20. Double click on the rc file. Select open file and open with WordPad. 21. Select Open when the Open File dialog is presented. The file will open in a new WordPad window. 22 Page

23 22. Find the line that reads route add default z.z.z.z, this is the default gateway for the filer. Add a new line under this one that reads route add x.x.x.x y.y.y.y 1.. This entry is identical to the command entered in step Save this file using the save command. Do not use the Save As command or this step will not work properly. Links Silver Peak Documentation: NetApp Support and Documentation: 23 Page

24 Appendix A Silver Peak Velocity and NetApp SnapMirror Configuration Sheet Local Site Silver Peak mgmt0: Replication Bandwidth: Silver Peak Appliance IP Appliance IP(also wan0): Appliance Subnet Mask: WAN0 Next-hop: Remote Site Silver Peak mgmt0: Replication Bandwidth: Silver Peak Appliance IP Appliance IP(also wan0): Appliance Subnet Mask: WAN0 Next-hop: IP Address: NetApp Primary IP Address: NetApp DR 24 Page