System Installation Workbook for eHarmony V3240AE

System Installation Workbook

Version 1.2

Date: June 2011

ABOUT NETAPP

NetApp creates innovative storage and data management solutions that deliver outstanding cost efficiency and accelerate performance breakthroughs. Discover our passion for helping companies around the world go further, faster at www.netapp.com.

NetApp, Inc.495 East Java DriveSunnyvale, CA 94089 USATelephone: +1 (408) 822-6000Fax: +1 (408) 822-4501Support telephone: +1 (888) 4-NETAPP

http://www.netapp.com/

Copyright and Trademark Information

© Copyright 2011 NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent of NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Go further, faster, are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries.

All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.

Table of Contents

1 SITE REQUIREMENTS.....................................................................................................51.1 System power requirements.......................................................................................61.2 Network cabling requirements...................................................................................72 CONFIGURATION DETAILS..............................................................................................82.1 Basic configuration....................................................................................................82.2 VIFs/ifgrps.................................................................................................................82.3 Network interface configuration.................................................................................92.3.1 Default gateway..................................................................................................................................................92.3.2 Administration host.............................................................................................................................................92.3.3 Timezone............................................................................................................................................................ 92.3.4 Language encoding for multiprotocol files..........................................................................................................92.3.5 Domain Name Services (DNS) resolution..........................................................................................................92.3.6 Network Information Services (NIS) resolution.................................................................................................102.3.7 Remote Management Settings (RLM or BMC).................................................................................................102.3.8 Alternate Control Path (ACP) management for SAS shelves...........................................................................102.4 CIFS configuration...................................................................................................102.5 Configure virtual LANs (VLANs)................................................................................112.6 AutoSupport settings...............................................................................................112.7 Customer/RMA details..............................................................................................112.7.1 Time synchronization........................................................................................................................................122.7.2 SNMP management settings............................................................................................................................123 INSTALLATION AND VERIFICATION CHECKLISTS............................................................13

Dear Customer,

Thank you for choosing a NetApp storage system and Trace3 Professional Services installation.

To ensure a seamless deployment and integration into your environment, please complete the information requested in this document before our engineer arrives on site. This will ensure that as many questions as possible are answered before the day of the installation, so you can start using your system.

The first part of the document includes environmental information about our products, which may help you with your computer room planning. I also strongly recommend that you visit the link shown on the next page and obtain a copy of our latest Site Requirements Guide.

The second part of the workbook covers the information that the professional services engineer will need on the day of installation. Please obtain the required information and return a completed copy of this document to the engineer before they arrive.

We look forward to working with you,

The Trace3 Team

1 Site requirements

Please download and read the latest version of the Site Requirements Guide:

http://now.netapp.com/NOW/public/knowledge/docs/hardware/NetApp/site/pdf/site.pdf

Dimensions and weight of NetApp hardware.

Hardware Dimensions U.S. Metric Rack Units*

FAS6200/V6200 series Height 10.32in 26.21cm 6U

Width 17.61in 44.73cm

Depth 24.3 in 61.72cm

Weight 125.7lbs 57kg

FAS6000/V6000 series Height 10.32 in. 26.21 cm 6U

Width 17.53 in. 44.52 cm

Depth 29 in. 73.66 cm

Weight 121 lbs. 54.885 kg

FAS3200/V3200 series Height 5.12in 13.0cm 3U

Width 17.61in 44.73cm

Depth 24in 61cm

Weight 74lbs 33.6kg

FAS3100/V3100 series Height 10.75 in 27.3 cm 6U

Width 17.73 in 45.0 cm

Depth 24 in 60.7 cm

Weight 121lbs 54.89kg

FAS2050 Height 6.9 in. 17.5 cm 4U

Width 17.6 in. 44.7 cm

Depth 22.5 in. 57.2 cm


FAS2020/FAS2040 Height 3.5 in. 8.9 cm 2U


Depth 22.5 in. 57.2 cm

Weight 60 / 66 lbs. 27.2 / 29.9 kg

DS14mk2 / DS14mk4 Height 5.25 in. 13.3 cm 3U



Weight 77 lbs. (loaded) 35 kg

DS14mk2 AT Height 5.25 in. 13.3 cm 3U



Weight 68 lbs. (loaded) 30.8 kg

DS2246 Height 3.4in 8.5cm

Width 19in 48cm

Depth 19.1in 48.4cm

Weight 49lbs(loaded)

22.2kg

DS4243 Height 7 in. 17.8 cm 4U

Width 19 in. 48.3 cm

Depth 24 in. 61 cm


http://now.netapp.com/NOW/public/knowledge/docs/hardware/NetApp/site/pdf/site.pdf

Hardware Dimensions U.S. Metric Rack Units*

(loaded)

NetApp System Cabinet Height 78.7 in. 200 cm 42U

Width 23.6 in. 60. cm

Depth 37.4 in. 95 cm

Weight 320 lbs (empty) 145.2 kg

* 1U = 1.75 inches

NOTE: Please plan for at least 36 inches (91.4 centimeters) of clearance on both front and back of the system. This amount of space allows you to reach the back panel for cabling the system. It also allows you to slide the motherboard tray out from the back of the system when removing or installing hardware.

1.1 System power requirements

Amps @ 100-120V Amps @ 200-240V

Hardware Actual (worst case) Actual (worst case) P/S Volt Range

FAS6200/V6200 series 5 2.4 100-240 VAC

FAS6000/V6000 series 9.72 4.84 100 – 240 VAC

FAS3200/V3200 series 4.22 1.97 100-240 VAC

FAS3100/V3100 series 9.74 4.69 100 – 240 VAC

FAS2050 7.51 3.73 100 – 240 VAC

FAS2040 4.85 2.39 100 – 240 VAC

FAS2020 4.94 2.45 100 – 240 VAC

DS14mk2/DS14mk4 FC w/ESH

4.52 2.23 100 – 240 VAC

DS14mk2 AT 3.15 1.55 100 – 240 VAC

DS2246 5.15 2.62 100-240VAC

DS4243 4.30 1.90 100 – 240 VAC

See http://now.netapp.com/NOW/knowledge/docs/hardware/hardware_index.shtml for additional details

NOTE: NetApp recommends using a minimum of two circuits for power supply redundancy.

42U NetApp System Cabinet Specifications.

Consult your co-location facility manager or vendor documentation if installing into third party cabinets.

Cabinet Specifications 20-Amp Single-Phase PDU

30-Amp Single-Phase 2x PDU

30-Amp Single-Phase 4x PDU

Input Voltage and Frequency 200 – 240 VAC, 50/60 HZ

# of Power Connectors 4 2 2

Power Connector Type (U.S.) NEMA L6-20 NEMA L6-30 NEMA L6-30

Power Connector Type (Intl.) IEC309-16A IEC309-30A IEC309-30A

Power Connector Type (Aus/NZ) AS/NZS3123-20

Power cord length from PDU 15 ft (4.5m) 10 ft (3m) 10 ft (3m)

NetApp Base Cabinet Part Number (U.S.)

X871A-R6 X8730A-R6 X8730B-R6

NetApp Base Cabinet Part Number (Intl.)

(Same as U.S.) X8731A-R6 X8731B-R6

http://now.netapp.com/NOW/knowledge/docs/hardware/hardware_index.shtml

1.2 Network cabling requirements

Network Device Cabling Requirements

10Base-TX/100Base-TX Cat 5/5e/6 UTP cable with RJ-45 connectors

Gigabit Ethernet (Optical) 50 or 62.5 micron multimode fiber optic cable with LC connector

Gigabit Ethernet (Copper) Cat 5e unshielded 4 pair cable with RJ45 connector

Fiber Channel 50 or 62.5 micron multimode fiber optic cable with LC connector

Fast Ethernet switch ports should be configured manually for speed and duplex settings (100 Full Duplex) when possible. The use of auto-negotiation for Fast Ethernet is discouraged for setting switch ports configuration with permanent equipment.

Cu (copper) Gigabit Ethernet switch ports, on the other hand, should be left to auto-negotiate the speed duplex settings (1000 Full). With all gigabit ports, it is highly recommended to configure the switch ports for Send On and Receive On (or Full) flow control on the switch as well as the client and enable ‘portfast’. Since this system is not a bridge or routing device, network connectivity will not complicate the boot process.

2 Configuration details

Please work with your Professional Services representative to complete this worksheet prior to the installation date. The requested information enables us to configure your equipment quickly and efficiently. Depending on the desired configuration, some fields may not be applicable.

Customer checklist of site preparation requirements (check all that apply):

Adequate rack space for the NetApp system and disk shelves has been provided.

The power requirements for the NetApp system and disk shelves have been satisfied.

The network patch cabling and switch port configuration is complete.

Company Name: NetApp Sales Order #: Storage Controller Model: Data ONTAP® Version:

2.1 Basic configuration

System Information Controller 1 Controller 2

Serial Number Hostname

2.2 VIFs/ifgrps

Virtual Interfaces (VIFs) or interface groups (Data ONTAP 8) bond multiple network ports together for increased bandwidth and/or fault tolerance.

NOTE: For systems without an e0P port, leave one network port available for ACP connections to SAS disk shelves.

Interface Details Controller 1 Controller 2

Number of virtual interfaces to configure Names of the virtual interfaces/ifgrpsFor example, vif1, iscsi_vif2

VIF/ifgrp type (multi, single, LACP)Multi – all ports are activeSingle – one port active, other ports are on standby for failoverLACP – network switch manages traffic

vif1: vif1: vif2: vif2: vif3: vif3:

Multi-mode VIF load balancing style (IP, MAC, round-robin, or port based)

vif1: vif1:

vif2: vif2:

vif3: vif3:

Number of links (network ports) in each VIF/ifgrp vif1: vif1: vif2: vif2: vif3: vif3:

Name of network ports in each VIF/ifgrpFor example,vif1= e0a, e1d vif3=vif1, vif2

vif1:

vif2:

vif3:

2.3 Network interface configuration

If you created VIF/ifgrps, then use their names, otherwise use port names (for example, e0a).

Some controllers have an e0M interface for environments with a subnet dedicated to managing servers. Include the e0M settings if you have a management subnet.

NOTE: For systems without an e0P port, leave one network port available for ACP connections to SAS disk shelves.

Controller Name

Interface Name

IP Address Network Mask Partner interface name or IP Address

Media Type

Enable Jumbo Frames?

2.3.1 Default gateway

Gateway Details Controller 1 Controller 2

Default Gateway IP address 2.3.2 Administration host

(Optional) You can limit the systems or subnets authorized to mount the root volume

Host Details Controller 1 Controller 2

Admin host/subnet IP 2.3.3 Timezone

What time zone should the systems set their clocks to (for example, US/Pacific)?

Timezone Details Controller 1 Controller 2

Time zone Physical Location (for example, Bldg 4, Dallas)

2.3.4 Language encoding for multiprotocol files

The default is POSIX and only needs to be changed for systems storing files using international alphabets.

Encoding Details Controller 1 Controller 2

Language for multiprotocol files 2.3.5 Domain Name Services (DNS) resolution

DNS Resolution Values

DNS Domain Name DNS Server IP addresses (up to 3)

2.3.6 Network Information Services (NIS) resolution

NIS Resolution Values

NIS Domain Name NIS Server IP addresses

2.3.7 Remote Management Settings (RLM or BMC)

All systems include a Remote LAN Module (RLM), a Baseboard Management Controller (BMC), or a Service Processor (SP) to provide out-of-band control of the storage system. NetApp recommends configuring these interfaces for easier, secure management and troubleshooting.

RLM/BMC Controller 1 Controller 2

IP Address Network Mask Gateway Mail server hostname

Mail server IP

2.3.8 Alternate Control Path (ACP) management for SAS shelves

For system models prior to the FAS3200 series, you must using an onboard NIC port to use ACP. New systems with dedicated e0P ports automatically assigns IP addresses.

Controller 1 Controller 2

Interface name (if not using e0P)

Private subnet(default: 198.15.1.0)

Network Mask

2.4 CIFS configuration

Systems with a CIFS license will run the CIFS setup wizard immediately after the Setup wizard completes. NT4 domains will require a server account to be created before running CIFS setup. The wizard can be aborted with Ctrl+C and run later if necessary.

NOTE: The installer will require someone with Domain Administrator privileges to help perform this section. When CIFS is configured, a domain administrator should move the controllers out of OU=Computers into a OU for servers. This will ensure Group Policy Objects can be applied to the controllers.

CIFS Configuration Controller 1 Controller 2

Authentication Mode Choose one of: Active Directory domain NT 4 domain Workgroup /etc/passwd or NIS/LDAP

Choose one of: Active Directory domain NT 4 domain Workgroup /etc/passwd or NIS/LDAP

Domain Name NetBios Name Do you want the system visible via WINS (Y/N)?

WINS IP Addresses(up to 3)

CIFS Configuration Controller 1 Controller 2

Multiprotocol or NTFS only? 2.5 Configure virtual LANs (VLANs)

(Optional) VLANs are used to segment network domains using 802.1Q protocol standards

Controller Name Interface Name VLAN IDs to activate Enable GVRP? NOTE: To trunk VLANs across an interface or VIF, you need to set "switchport mode trunk" on that interface or logical interface. This will allow 802.1q trunking, so that traffic across it is VLAN tagged. You must then create the relevant VLAN interfaces on the storage controller.

If you want a port or EtherChannel interface to be the only access port for a particular VLAN you must set "switchport mode access" on that interface. Then give the storage controller interface an IP address on that VLAN. No other information is required to VLAN tag the frames.

Reboot the controllers at this point for the settings to go into effect

2.6 AutoSupport settings

AutoSupport is a ‘phone home’ function to notify you and NetApp of any hardware problems, so that new hardware can be automatically delivered to solve the issue. (System must remain on a support contract and the level of responsiveness is dependent on the level of service contract: 2 hours – Next Business Day.)

Auto Support Settings Controller 1 Controller 2

Enable AutoSupport? If not, provide justification.

SMTP Server Name or IP AutoSupport Transport One of:

HTTPS (default) HTTP SMTP

One of: HTTPS (default) HTTP SMTP

AutoSupport From E-Mail address

<hostname@yourdomain> <hostname@yourdomain>

AutoSupport To E-Mail address(es)

2.7 Customer/RMA details

Verify this information by logging into the now.netapp.com website. This information is required to ensure that the Technical Support personnel can reach you and the replacement parts are sent to the correct address.

Customer/RMA Details Primary Contact Secondary Contact

Contact Name Contact Address Contact Phone

Customer/RMA Details Primary Contact Secondary Contact

Contact E-mail Address RMA Address RMA Attention To Name

2.7.1 Time synchronization

Time Synchronization Details Values

Time services protocol (rtc or ntp) Time Servers (up to 3 internal or external hostnames or IP addresses)

Max time skew (<5 minutes for CIFS)

2.7.2 SNMP management settings

(Optional) Fill out if you have SNMP monitoring applications (for example, Operations Manager). Set by using the ‘snmp options’ command.

SNMP Settings Controller 1 Controller 2

SNMP Trap Host SNMP Community Data Fabric Manager Server Name or IP

Data Fabric Manager Protocol

Choose one of: HTTP HTTPS

Choose one of: HTTP HTTPS

Data Fabric Manager Port

3 Installation and verification checklists

The installer will perform the following checks to ensure that your new systems are configured correctly and are ready to turn over to you.

Physical Installation Status

Check and verify all ordered components were delivered to the customer site.

Confirm the NetApp controllers are properly installed in the cabinets.

Confirm there is sufficient airflow and cooling in and around the NetApp system.

Confirm all power connections are secured adequately.

Confirm the racks are grounded (if not in NetApp cabinets).

Confirm there is sufficient power distribution to NetApp controllers & disk shelves.

Confirm power cables are properly arranged in the cabinet.

Confirm that LEDs and LCDs are displaying the correct information.

Confirm that cables from NetApp controllers to disk shelves and among disk shelves are not crimped or stretched.(fiber cable services loops should be bigger than your fist )

Confirm that fiber cables laid between cabinets are properly connected and are not prone to physical damage.

Confirm disk shelves IDs are set correctly.

Confirm that fiber channel 2Gb/4Gb loop speeds are set correctly on DS14 shelves and proper LC-LC cables are used.

Confirm that Ethernet cables are arranged and labeled properly.

Confirm all Fiber cables are arranged and labeled properly.

Confirm the Cluster Interconnect Cables are connected (for HA pairs).

Confirm there is sufficient space behind the cabinets to perform hardware maintenance.

Power On & Diagnostics Status

Power up the disk shelves to ensure that the disks spin up and are initialized properly.

Connect the console to the serial port cable and establish a console connection using a terminal emulator like Terra Term, PuTTY or Hyperterm.

NOTE: Log all console output to a text file.

Power on the controllers.

Boot the controller and press Ctrl+C at the second prompt for ‘Special Boot Menu options’.

Go to Maintenance Mode by selecting option 5.

Check the onboard fiber ports status:*> fcadmin config Change the port mode if necessary from targets to initiators (for SAN requirements).

Verify the cable connections to all shelves:*> fcadmin device_map

Verify disk ownership assignments:*> disk show –aAssign disks to each node using the disk assign command if necessary.

Verify the system has one root aggregate assigned:*> aggr status

Follow these steps for both cluster nodes, halt and then reboot each system into Data ONTAP:*> haltLOADER> boot_ontap

Verify power and cooling are at acceptable levels:

Power On & Diagnostics Status

fas1> environment status

Verify expansion cards are installed in the correct slots:fas1> sysconfig -c

Verify all local and partner shelves are visible to the system:fas1> fcadmin device_map

Verify that all disks are owned:fas1> disk show -n

Use the WireGauge tool to verify that all the shelves are cabled correctly.

Installation & Configuration Status

Confirm the correct version of Data ONTAP software and disk, shelf, motherboard and RLM/BMC firmware is installed on each controller

fas1> version –bfas1> sysconfig -a

Confirm ALL controllers are named as per the customer naming standards

Confirm the root volume is sufficiently sized ( 2x memory or 20GB minimum)fas1> vol size <root volume name>

Confirm all the licenses are installedfas1> license

Check the /etc/rc and /etc/hosts files:fas1> rdfile /etc/rc

fas1> rdfile /etc/hosts

Verify all configured Ethernet network interfaces (individual and VIF) are configured correctly as per the customer requirements: IP address, media type, flow control and speed.Confirm any interfaces not required to perform host name resolution are configured with the "-wins" optionFor clustered systems, verify they have partner interfaces for failover

Where necessary, confirm the network switches are configured to support dynamic or static multi-mode VIFs (LACP or Etherchannel) as per customer requirement.

Has the customer accessed the system console using the RLM or BMC?

Verify network connectivity and DNS resolution is configured properly:fas1> ping <hostname of mail server>

Verify configured VIFs/ifgrps function properly by disconnecting one or more cablesfas1> vif status

Pull cablesfas1> ping <hostname of mail server>

fas1> vif status

Reinsert cables

Confirm each controller is configured to synchronise time with a centralised sourcefas1> options timed

fas1> timezone

fas1> date

Confirm that AutoSupport is configured and functioning correctly.fas1> options autosupport.doit “Test”

Confirm the default ‘home’ share is stopped from each controller (and vFiler)

If necessary, confirm that telnet and RSH is disabled and SSH is enabled

If required, confirm SNMP is configured on all controllers to the appropriate traphost

Download documentation pack and upload to controller(s)

CIFS Configuration Status

If necessary, run through CIFS setup and join the controllers to the customer's Active Directory (requires an AD account with suitable permissions).

Confirm the NetApp controller’s local administrator account was created while configuring the CIFS service (and the password is set appropriately).

Confirm the permissions to the root volume (c$) and /etc folder (etc$) are configured appropriately (that is, NOT Everyone Full Control).

Confirm that appropriate Windows Domain Administrators group(s) are member of the NetApp controller’s local administrator group.

Create a share.

Have the customer map the share to a host, write data to it.

Create a Snapshot and confirm that Snapshot visibility is configured appropriately (for example, hidden to regular CIFS clients)

Confirm that qtrees storing CIFS data have the appropriate security style specified:fas1> qtree status

Confirm that qtrees storing CIFS data have the appropriate ‘oplocks’ setting.

NFS Configuration Status

Create a qtree and confirm the appropriate security style is specifiedfas1> qtree create <path>

fas1> qtree status

Export the qtree.

Check the /etc/exports file and update the same with new mount entries with appropriate permissions.

Have the customer mount the qtree from a host and write data to it.

Take a Snapshot and confirm that Snapshot visibility is configured appropriately (for example, hidden to regular clients)

iSCSI Configuration Status

Make sure the iSCSI service is started.

Verify that an iSCSI host attach or support kit has been installed on the host.

If appropriate, verify SnapDrive has been installed on the host.

Create a qtree, igroup, and LUN on the system (using SnapDrive if necessary).

Have the customer establish an iSCSI session from the host.

Create a file system on the LUN, write some data to it and confirm the data is on the LUN.

Reboot the host and confirm that the LUN is still attached.

FCP Configuration Status

Make sure the FCP service is startedfas1> fcp status

Verify an FCP host attach or support kit has been installed on the host.

If appropriate, verify that SnapDrive has been installed on the host.

Create a qtree, igroup, and LUN on the system (using SnapDrive if necessary).

Have the customer establish an FCP session from the host.

Have the customer create a file system on the LUN and, write some data to it.

Have the customer reboot the host and confirm the LUN is still attached.

Verification Checklist Status

Where necessary Make sure the CLUSTER license is enabled where necessary.

Verify the cluster options on both systems in the cluster are identical.

Temporarily disable AutoSupport:fas1> options autosupport.enable off

Test manual Cluster Failover (in both directions) and ensure success, rectify any errors and prove network connectivity continues to function correctly during failover.fas1> cf enablefas1> cf takeoverfas1> partnerfas2/fas1*> ifconfig –afas2/fas1*> vif statusfas2/fas1*> partnerfas1> cf giveback

Test Uncontrolled Cluster Failover (in both directions) by disconnecting one controller from power. Rectify any errors.

Test component failure of a PSU (Check status of LEDs and console).

Test component failure of a LAN cable (Virtual Interface Test), include vif favor.

Test component failure of a fiber cable to disk shelf (Path Test), For Multipath HA cabling, type storage show disk –p to ensure all disks have an A and B channel.

Run the WireGauge tool to ensure the shelf cabling is correct.

When installing a new system into a new NetApp cabinet, switch off one cabinet PDU, and make sure all controllers and shelves remain powered on. Check the status of LEDs and console.

Insert an entry into the system log indicating installation is complete:fas1> logger * * * System Install complete <installer name> <date> * * *

Backup the system configuration:fas1> config dump <date>.cfg

Re-enable AutoSupport:fas1> options autosupport.enable on

Post Installation Checklist Status

Give new customers a brief tour of FilerView or Systems Manager to explain the basic functions of managing their new system.

Log onto the NOW website and give the customer a brief tour of the site. Show them how to access documentation, download software and firmware, search the Knowledge Base, and verify their RMA information.

Discuss training available through NetApp University with new customers.

Since they are the basis for most Data ONTAP functionality, have the customer explain how Snapshots work. Correct any misconceptions.

Create and send a Trip Report within 24 hours to the customer, partner sales team and NetApp sales team.

When all tasks are completed, have customer sign a Certificate of Completion.

System Installation Workbook for eHarmony V3240AE

Documents

Transcript of System Installation Workbook for eHarmony V3240AE