V-Series FAQ Covering Product and Technical Topics

December 2010

V-Series FAQ

TABLE OF CONTENTS

GENERAL QUESTIONS ............................................................................................................. 5

1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 WHAT IS A V-SERIES CONTROLLER? ..................................................................................................... 5 HOW IS A V-SERIES CONTROLLER DIFFERENT THAN A FAS CONTROLLER? ................................... 5 WHICH PROTOCOLS ARE SUPPORTED ON A V-SERIES CONTROLLER?............................................ 5 WHICH ARRAYS AND SWITCHES ARE SUPPORTED BY THE V-SERIES CONTROLLER? ................... 5 CAN YOU DESCRIBE A V-SERIES BACK END AND FRONT END? ......................................................... 5 CAN I ATTACH BOTH ARRAY LUNS AND NETAPP DISKS TO A V-SERIES CONTROLLER? ............... 5 CAN I ATTACH ARRAY LUNS TO A FAS CONTROLLER? ....................................................................... 5 CAN I REPLACE MY FAS CONTROLLER WITH A V-SERIES CONTROLLER? ....................................... 6 CAN I CONVERT MY FAS CONTROLLER TO A V-SERIES CONTROLLER? ........................................... 6 WHAT TYPE OF RAID PROTECTION IS USED ON A V-SERIES CONTROLLER? ................................... 6 WHAT IS THE MAXIMUM STORAGE CAPACITY I CAN ATTACH TO A V-SERIES CONTROLLER? ...... 6 IS THERE A SPECIAL DATA ONTAP VERSION FOR V-SERIES? ............................................................ 6 CAN I DYNAMICALLY ADD/REMOVE THIRD-PARTY STORAGE BEHIND A V-SERIES SYSTEM? ........ 6 CAN I ADD NETAPP DISK SHELVES TO A V-SERIES SYSTEM? ............................................................ 6 WOULD YOU DESCRIBE THE SIMPLE SET OF BEST PRACTICES FOR A V-SERIES DEPLOYMENT? 6 IF I REPLACE MY V-SERIES CONTROLLER, IS A DATA MIGRATION REQUIRED?............................... 7 ARE THE LICENSES ON V-SERIES DIFFERENT THAN FAS LICENSES? ............................................... 7 WHICH LICENSES ARE REQUIRED FOR V-SERIES? .............................................................................. 7

1.19 IF A STORAGE ARRAY VENDOR STARTS SUPPORTING SOLID-STATE DISKS IN ITS ARRAY, IS THE ARRAY SUPPORTED WITH V-SERIES? ........................................................................................................ 7 1.20 HOW DO I GET V-SERIES TO SUPPORT A NEW ARRAY THAT IS NOT LISTED ON THE V-SERIES SUPPORT MATRIX? ............................................................................................................................................... 7 1.21 1.22 HOW DO I KNOW IF I NEED A FAS CONTROLLER OR A V-SERIES CONTROLLER? ........................... 8 ARE THERE PLANS TO UNIFY THE FAS AND V-SERIES PLATFORMS? ............................................... 8

1.23 CAN I MIX ARRAY LUNS FROM DIFFERENT STORAGE ARRAYS OR ARRAY VENDORS WITHIN THE SAME NETAPP AGGREGATE? ...................................................................................................................... 8 1.24 WHAT STORAGE ARRAY FEATURES CAN I USE WITH A V-SERIES CONTROLLER? ......................... 8

1.25 HOW SHOULD I RESPOND TO OTHER STORAGE ARRAY VENDORS WHO SAY THE V-SERIES CONTROLLER IS NOT SUPPORTED IN FRONT OF THEIR ARRAY OR THAT ATTACHING THE V-SERIES CONTROLLER WILL VOID THE ARRAY WARRANTY? ........................................................................................ 8 1.26 1.27 HOW ARE THIRD-PARTY ARRAYS QUALIFIED FOR V-SERIES SUPPORT? ......................................... 8 WHAT ARE MY OPTIONS IF A CONFIGURATION IS NOT LISTED ON THE SUPPORT MATRIX?.......... 9

1.28 DO THE BACK-END STORAGE ARRAYS OR SWITCHES NEED TO BE UNDER A SUPPORT CONTRACT? ........................................................................................................................................................... 9 1.29 HOW ARE V-SERIES AND THIRD-PARTY ARRAYS SUPPORTED IN A MULTIVENDOR ENVIRONMENT? ..................................................................................................................................................... 9 1.30 CAN I ADD STORAGE BEHIND AN EXISTING V-SERIES DEPLOYMENT? ............................................. 9

V-Series FAQ

TECHNICAL QUESTIONS........................................................................................................ 10
2.1 ARE THERE SPECIFIC CABLING AND ZONING MODELS FOR ATTACHING THE V-SERIES CONTROLLER TO THE STORAGE ARRAY? ....................................................................................................... 10 2.2 2.3 CAN A SINGLE V-SERIES ATTACH TO MULTIPLE ARRAY LUN GROUPS? ........................................ 11 CAN A V-SERIES CONTROLLER ATTACH TO MULTIPLE STORAGE ARRAYS? ................................. 11

2.4 CAN I USE A DIRECT-ATTACH MODEL BETWEEN THE V-SERIES CONTROLLER AND THE STORAGE ARRAY? .............................................................................................................................................. 12 2.5 HOW DO I DECIDE WHEN A SINGLE FOUR-ARRAY-PORT LUN GROUP IS OK OR WHEN I WOULD NEED TO HAVE TWO OR MORE FOUR-PORT-ARRAY LUN GROUPS ON A SINGLE STORAGE ARRAY? .... 12 2.6 HOW DO I CALCULATE USABLE V-SERIES SPACE GIVEN A FIXED AMOUNT OF STORAGE ARRAY LUN CAPACITY? HOW DO I CALCULATE REQUIRED STORAGE ARRAY CAPACITY GIVEN THE DESIRED FRONT-END USE REQUIREMENTS? .................................................................................................. 12 2.7 HOW DO I SIZE A V-SERIES SYSTEM?................................................................................................... 13

2.8 HOW DO I MIGRATE EXISTING DATA RESIDING ON THIRD-PARTY ARRAYS BEING SERVED TO HOSTS AND BRING IT UNDER V-SERIES CONTROL AND MANAGEMENT? ................................................... 13 2.9 WHAT PRECAUTIONS SHOULD I TAKE PRIOR TO DOING SYSTEM MAINTENANCE, INCLUDING FABRIC OR STORAGE ARRAY MAINTENANCE? .............................................................................................. 14 2.10 WHAT IS REQUIRED IN ORDER TO ADD OR USE A NETAPP DISK SHELF ON A V-SERIES CONTROLLER? .................................................................................................................................................... 14 2.11 WHAT HAPPENS IF I DONT SET THE FC-NON-ARRAY-ADAPTER-LIST PARAMETER CORRECTLY FOR MY HA-MP? ............................................................................................................................ 14 2.12 HOW MANY FIBER PATHS SHOULD THERE BE BETWEEN A V-SERIES CONTROLLER AND AN ARRAY OR A LUN? .............................................................................................................................................. 14 2.13 HOW MANY FABRIC HOPS CAN I HAVE BETWEEN THE V-SERIES CONTROLLER AND THE ARRAY? ................................................................................................................................................................ 15 2.14 HOW MANY ARRAY LUNS CAN I PUT ON A ONE-FS INITIATOR PORT? ............................................. 15

2.15 CAN A V-SERIES INITIATOR FC PORT ATTACH TO MULTIPLE STORAGE ARRAY TARGET PORTS USING THE FABRIC FOR FAN-IN? ...................................................................................................................... 15 2.16 CAN I SHARE STORAGE ARRAY TARGET PORTS WITH OTHER HOSTS OR WITH OTHER VSERIES CONTROLLERS? .................................................................................................................................... 15 2.17 ARE SOFT ZONING AND HARD ZONING BOTH SUPPORTED? ............................................................ 15

2.18 WHAT ARE THE MINIMUM NUMBER AND THE SIZE OF ARRAY LUNS NEEDED FOR A V-SERIES DEPLOYMENT? .................................................................................................................................................... 15 2.19 SHOULD I INSTALL THE ROOT VOLUME ON AN AGGREGATE OF NETAPP DISKS OR ON STORAGE ARRAY LUNS? ................................................................................................................................... 15 2.20 IS A MINIMUM SIZE FOR THE ROOT VOLUME OR FOR THE STORAGE ARRAY LUN NEEDED FOR THE ROOT VOLUME? .......................................................................................................................................... 15 2.21 2.22 2.23 2.24 2.25 2.26 WHY DO I NEED A SPARE LUN ON MY V-SERIES CONTROLLER ....................................................... 15 CAN I USE AN ARRAY LUN WITH AN ID OF 0 (LUN0)? ......................................................................... 16 CAN I MIX DIFFERENT-SIZE LUNS INTO THE SAME NETAPP AGGREGATE? .................................... 16 WHAT SIZE STORAGE ARRAY LUNS CAN ATTACH TO A V-SERIES CONTROLLER? ....................... 16 HOW DO YOU RECOMMEND I SIZE MY STORAGE ARRAY LUNS FOR A V-SERIES CONTROLLER?16 DOES V-SERIES SUPPORT BACK-END STORAGE ARRAY THIN PROVISIONING? ............................ 16

V-Series FAQ

2.27 SOME STORAGE ARRAYS CAN DYNAMICALLY GROW AN ARRAY LUN. IS GROWING AN ARRAY LUN SUPPORTED BEHIND A V-SERIES CONTROLLER? .................................................................................. 16 2.28 CAN I USE HITACHI DYNAMIC PROVISIONING (HDP) FOR LUNS PRESENTED TO A V-SERIES CONTROLLER? .................................................................................................................................................... 16 2.29 CAN I USE STORAGE ARRAY-BASED REPLICATION AND HAVE A V-SERIES CONTROLLER AT THE REMOTE ARRAY SITE? ............................................................................................................................... 17 2.30 ALL THE V-SERIES IMPLEMENTATION DOCUMENTS DESCRIBE A LAYOUT IN WHICH PORTS FROM ONE SIDE OF A STORAGE ARRAY CONTROLLER ARE ATTACHED TO ONE FABRIC. MY SAN DESIGN IS A CROSS IN WHICH A SINGLE STORAGE ARRAY CONTROLLER ATTACHES TO BOTH FABRICS. IS A CROSSED BACK END SUPPORTED?........................................................................................ 17 2.31 ARE THERE ANY SPECIAL REQUIREMENTS FOR USING HDS USP-V WITH A VIRTUALIZED ARRAY BEHIND THE USP-V? .............................................................................................................................. 17 2.32 IS THERE ADDED LATENCY WHEN INSTALLING A V-SERIES CONTROLLER IN FRONT OF A STORAGE ARRAY? .............................................................................................................................................. 17 2.33 CAN I USE SNAPMIRROR BETWEEN A V-SERIES CONTROLLER WITH ARRAY LUNS AND A VSERIES CONTROLLER OR FAS WITH NETAPP SHELVES?.............................................................................. 17 2.34 CAN I USE SYNCMIRROR ON A V-SERIES CONTROLLER BETWEEN DIFFERENT TYPES OF STORAGE ARRAYS OR DIFFERENT TYPES OF DISKS WITHIN THE ARRAY? ................................................ 17 2.35 CAN I USE SYNCMIRROR ON A V-SERIES CONTROLLER BETWEEN ARRAY LUNS AND NETAPP DISKS? .................................................................................................................................................................. 18 2.36 CAN I GET ANY STORAGE ARRAY INFORMATION FROM THE V-SERIES CONTROLLER? ............... 18

2.37 DOES DATA ONTAP REGISTER THE ARRAY LUNS DIFFERENTLY WHEN THEY ARE DIRECTLY ATTACHED VERSUS FABRIC ATTACHED? ....................................................................................................... 18 2.38 2.39 2.40 2.41 2.42 2.43 2.44 INTO WHICH SWITCH AND SWITCH PORT IS MY V-SERIES PHYSICALLY PLUGGED? ..................... 18 WHAT ARE CHECKSUMS, AND ARE THEY REQUIRED? ...................................................................... 19 CAN I MIX BCS AND ZCS INTO THE SAME AGGREGATE?................................................................... 19 HOW CAN I CHANGE ZCS LUN ASSIGNMENT TO BCS ASSIGNMENT? .............................................. 19 HOW DOES V-SERIES DO PATHING ASSIGNMENTS TO ARRAY LUNS? ............................................ 19 IF MY PATHS TO LUNS ARE NOT BALANCED, WHAT CAN I DO? ....................................................... 19 CAN I TRANSPARENTLY REPLACE A FABRIC BEHIND A V-SERIES CONTROLLER? ....................... 19

2.45 IF A V-SERIES CONTROLLER HAS MULTIPLE AGGREGATES THAT ARE EITHER BUILT ON THIRD-PARTY ARRAY LUNS OR BUILT ON NETAPP DISKS AND ONE AGGREGATE FAILS, WHAT HAPPENS TO DATA ONTAP, THE OTHER AGGREGATES, OR THE VOLUMES? ............................................ 20 2.46 2.47 WHAT HAPPENS IF I MOVE THE CABLE FROM ONE SWITCH FC PORT TO ANOTHER FC PORT? .. 20 CAN I REMOVE ARRAY LUNS FROM A V-SERIES CONTROLLER? ..................................................... 20

2.48 HOW DO I REPLACE THE NVRAM ON A V-SERIES CONTROLLER? ARE THESE STEPS THE SAME AS ON A FAS CONTROLLER? ............................................................................................................................. 20 2.49 ARE THE V-SERIES MOTHERBOARD REPLACEMENT STEPS THE SAME AS THOSE FOR A FAS MOTHERBOARD REPLACEMENT? ..................................................................................................................... 20 2.50 ARE THE V-SERIES V6000 FC EXPANSION SLOT MODULE STEPS THE SAME AS FOR A FAS FC EXPANSION SLOT REPLACEMENT? .................................................................................................................. 21

V-Series FAQ

GENERAL QUESTIONS

1.1

WHAT IS A V-SERIES CONTROLLER?

V-Series is an open storage controller that enables you to attach to multivendor storage systems and extend Data ONTAP features to third-party storage. The V-Series controller unifies NAS, IP, and FC SAN management in a single controller.

1.2

HOW IS A V-SERIES CONTROLLER DIFFERENT THAN A FAS CONTROLLER?

FAS and V-Series controllers are almost identical, with very few exceptions. V-Series controllers enable you to extend Data ONTAP capabilities to other vendors storage arrays and to NetApp disk shelves. FAS systems use only NetApp disk shelves and use NetApp RAID-DP for parity protection. With V-Series and storage arrays, the parity protection is performed on the array. V-Series controllers with NetApp disks use the traditional NetApp RAID-DP. V-Series does not support MetroCluster with NetApp disk shelves. VSeries does not support SnapLock compliance or disk sanitization with other vendors storage arrays.

1.3

WHICH PROTOCOLS ARE SUPPORTED ON A V-SERIES CONTROLLER?

Like FAS controllers, V-Series controllers support NFS, CIFS, HTTP, FTP, FCP, FCoE, and iSCSI protocols along with other NetApp features such as Snapshot copies, replication, and so on.

1.4

WHICH ARRAYS AND SWITCHES ARE SUPPORTED BY THE V-SERIES CONTROLLER?

V-Series supports storage arrays from vendors such as EMC, HDS, IBM, HP, Sun, 3PAR, and Fujitsu. Switch support includes Brocade and Cisco. For details on the storage array and switch models and firmware supported, refer to the support matrix at http://now.netapp.com/NOW/knowledge/docs/VSeries/supportmatrix/V-Series_SupportMatrix.pdf.

1.5

CAN YOU DESCRIBE A V-SERIES BACK END AND FRONT END?

The back end refers to how the disk subsystem attaches to the V-Series controller. The V-Series back end includes all supported storage arrays, SAN fabrics, cabling, and building of the NetApp aggregate. Front end refers to all hosts/clients attached to the controllers or NetApp feature set. There is no difference in the front-end feature set for FAS and V-Series controllers. For example, NFS protocol or SnapMirror replication is a front-end feature and is descriptive for both FAS and V-Series. Front end describes everything from the aggregate forward.

1.6

CAN I ATTACH BOTH ARRAY LUNS AND NETAPP DISKS TO A V-SERIES CONTROLLER?

Yes. Starting with Data ONTAP 7.3 you can attach both third-party storage array LUNs and NetApp disks to a V-Series controller into separate storage aggregates.

1.7

CAN I ATTACH ARRAY LUNS TO A FAS CONTROLLER?

No, FAS controllers only support NetApp disk shelves. V-Series is required to attach to storage arrays not from NetApp.

V-Series FAQ

1.8

CAN I REPLACE MY FAS CONTROLLER WITH A V-SERIES CONTROLLER?

Replacing a FAS controller with a V-Series controller requires a sales upgrade to replace the controller. The upgrade comes with the corresponding controller licenses and services required for the upgrade. There is also a trade-in program available with V-Series that is similar to the FAS program.

1.9

CAN I CONVERT MY FAS CONTROLLER TO A V-SERIES CONTROLLER?

No, you cannot convert a FAS controller to a V-Series controller.

1.10 WHAT TYPE OF RAID PROTECTION IS USED ON A V-SERIES CONTROLLER?

V-Series creates storage pools of RAID 0 (striped) using array LUNs presented from other vendors storage. The parity protection for these array LUNs is provided by the storage array. Supported array RAID types are assigned by the array vendor and include the typical RAID types of RAID 1, RAID 5, and so on. Always consult the array integration guide for the latest information specific to the storage array being deployed behind the V-Series solution. NetApp disk shelves are also supported with the V-Series platform and are protected using traditional Data ONTAP RAID-DP or RAID 4.

1.11 WHAT IS THE MAXIMUM STORAGE CAPACITY I CAN ATTACH TO A V-SERIES CONTROLLER?
Each V-Series controller can support a maximum number of back-end devices that is equivalent to the number of disks supported on a FAS system. The devices can be either array LUNs from storage arrays or NetApp disks. For example, the V3140 can support 420 devices for a standalone system or for an activeactive system. These 420 devices can be all NetApp disks, all array LUNs, or any mix of disks and array LUNs that does not exceed 420. Refer to the V-Series support matrix, which documents the device limits for each platform per release.

1.12 IS THERE A SPECIAL DATA ONTAP VERSION FOR V-SERIES?

Both V-Series systems and FAS systems use the same Data ONTAP binaries. When downloading from NOW, you will be asked if your system is a V-Series system, but this is purely to track downloads. You will download the same executables for both V-Series and FAS systems.

1.13 CAN I DYNAMICALLY ADD/REMOVE THIRD-PARTY STORAGE BEHIND A V-SERIES SYSTEM?

Yes, with some caveats. Capacity may be added transparently to an existing aggregate, but cannot be removed from that aggregate. If an array LUN does not belong to an aggregate, that is, it is labeled as a spare, it can be removed using the disk remove -w command to remove the SCSI reservation on the array LUN. The V-Series Best Practices Guide (TR-3461) discusses these issues in greater detail.

1.14 CAN I ADD NETAPP DISK SHELVES TO A V-SERIES SYSTEM?

Yes, you can add NetApp disks shelves to a V-Series system just as you can with NetApp FAS systems. See the V-Series integration guide for requirements to set fc-non-array-adapter-list for FC ports used with NetApp storage. This parameter is not needed for SAS shelves.

1.15 WOULD YOU DESCRIBE THE SIMPLE SET OF BEST PRACTICES FOR A V-SERIES DEPLOYMENT?
V-Series can be installed with one or more storage arrays and also with NetApp disk shelves. Detailed requirements and best practices can be found in the V-Series Best Practices Guide, the V-Series support matrix, and Data ONTAP documentation. A simple set of best practices includes the following items:

V-Series FAQ

Use a NetApp shelf for the root volumes. Use a four-array port LUN group described below. Use dedicated storage array ports. Sharing storage array ports can adversely affect performance. Use a single initiator to single target configuration and zoning. Use dedicated array RAID groups. Have a spare LUN assigned. If using a NetApp shelf, the spare disk meets this requirement. Avoid making changes to configurations once they are built. Changes to a stable system introduce the risk of disruption. Follow proper procedures when performing any maintenance on the V-Series controller, the backend fabric, or on the storage array. After installing a new system, make sure you properly test for path redundancy and cluster function.

1.16 IF I REPLACE MY V-SERIES CONTROLLER, IS A DATA MIGRATION REQUIRED?

A V-Series controller replacement does not require a data migration. The data remains on the array LUNs. These array LUNs are simply reassigned to the new V-Series controller.

1.17 ARE THE LICENSES ON V-SERIES DIFFERENT THAN FAS LICENSES?

V-Series and FAS both offer mostly the same sets of protocol and feature licenses. The actual system license on a V-Series controller is different than the FAS license and also includes a heterogeneous support license. A FAS license wont work on a V-Series controller. If you perform a FAS-to-V-Series upgrade, you have to replace the licenses.

1.18 WHICH LICENSES ARE REQUIRED FOR V-SERIES?

V-Series controllers come with a V-Series license, which enables the controller to attach to back-end storage array LUNs. Other protocol or feature licenses can be added. For example, FCP is a protocol license just like CIFS, NFS, and iSCSI and is used for front-end host or client attaching to the controllers.

1.19 IF A STORAGE ARRAY VENDOR STARTS SUPPORTING SOLID-STATE DISKS IN ITS ARRAY, IS THE ARRAY SUPPORTED WITH V-SERIES?
V-Series would expect to support array LUNs built on solid-state disks (SSDs) in a support storage array. However, simply including SSDs in an array is expected to require array microcode upgrades, RAID group changes, or methods of presenting the SSD-based LUNs from the array. Each array vendor might take a different approach to its SSD implementation. Including SSDs in an array will require a qualification prior to being posted on the V-Series support matrix. Use typical V-Series best practices for separate NetApp aggregates based on array LUNs built on either SSD, FC, or SATA disks.

1.20 HOW DO I GET V-SERIES TO SUPPORT A NEW ARRAY THAT IS NOT LISTED ON THE V-SERIES SUPPORT MATRIX?
V-Series has an extensive support matrix and now supports over 95% of arrays. We keep up with new storage arrays that are introduced and have an internal vetting process for arrays we plan to run through our qualification process. Addition of a storage array is an extensive process. That said, if there is a storage arrays that we have neglected, contact your NetApp account team and submit a PVR.

V-Series FAQ

1.21 HOW DO I KNOW IF I NEED A FAS CONTROLLER OR A V-SERIES CONTROLLER?

V-Series controllers are used when deployment plans include attaching to third-party storage arrays in addition to using NetApp storage. Additional heterogeneous licensing is required that is included with each V-Series system.

1.22 ARE THERE PLANS TO UNIFY THE FAS AND V-SERIES PLATFORMS?
Currently, support for heterogeneous storage is available only with V-Series controllers. V-Series controllers also support NetApp storage shelves with Data ONTAP 7.3 or later. FAS controllers use only NetApp storage.

1.23 CAN I MIX ARRAY LUNS FROM DIFFERENT STORAGE ARRAYS OR ARRAY VENDORS WITHIN THE SAME NETAPP AGGREGATE?
No, you cannot mix different array vendor LUNs in the same aggregate. Each aggregate should be made from array LUNs of the same array family: the same size and same type of underlying array disk types. Make sure you build your aggregates properly, because Data ONTAP does not prevent you from mixing array LUN sizes, types, and so on. Also, you cannot remove a single array LUN from an aggregate. So be careful when adding array LUNs to aggregates, because if you add the wrong type, you will need to migrate the data to another aggregate and then destroy the mixed aggregate.

1.24 WHAT STORAGE ARRAY FEATURES CAN I USE WITH A V-SERIES CONTROLLER?
Advanced storage array features are not supported with V-Series controllers. The V-Series open storage controller is considered the storage controller, and the array LUNs are considered the storage capacity to support the controller. Storage array features that typically are under question and not supported are (1) array thin provisioning, (2) dynamic resizing of the array LUNs, (3) array-based replication and attaching VSeries at remote sites, and (4) array-based transparent movement of LUNs.

1.25 HOW SHOULD I RESPOND TO OTHER STORAGE ARRAY VENDORS WHO SAY THE V-SERIES CONTROLLER IS NOT SUPPORTED IN FRONT OF THEIR ARRAY OR THAT ATTACHING THE V-SERIES CONTROLLER WILL VOID THE ARRAY WARRANTY?
This objection is often raised by EMC in the selling process against V-Series and is not true in practice. There are dozens of V-Series systems in production environments with both CX and DMX arrays, and EMC has not invalidated the warranty on any of these systems. If this sales tactic is encountered, simply ask the customer to ask EMC personnel if they are not honoring their warranty for current production installations running with V-Series and EMC arrays. Customer references can be provided to validate the support EMC continues to provide for these customers in conjunction with their warranty. V-Series supports any storage array listed on its support matrix in the same manner. This is outlined in our support policy and in our FAQ as well as described in our published support matrix. We have over 3,000 systems running in over 700 installations, and the support process is the same for each.

1.26 HOW ARE THIRD-PARTY ARRAYS QUALIFIED FOR V-SERIES SUPPORT?

If you require a storage array, fabric, or microcode for V-Series support that is not listed on the V-Series support matrix, file a PVR with NetApp to request the additional support.

V-Series FAQ

1.27 WHAT ARE MY OPTIONS IF A CONFIGURATION IS NOT LISTED ON THE SUPPORT MATRIX?
You can submit a PVR to V-Series product management.

1.28 DO THE BACK-END STORAGE ARRAYS OR SWITCHES NEED TO BE UNDER A SUPPORT CONTRACT?
NetApp recommends that all production equipment be on a vendor support contract.

1.29 HOW ARE V-SERIES AND THIRD-PARTY ARRAYS SUPPORTED IN A MULTIVENDOR ENVIRONMENT?
If the customer has a support contract with NetApp for our equipment, NetApp will take responsibility for troubleshooting and fault isolation of support issues that the customer believes involve NetApp. If the fault isolation determines that the other vendor's equipment is at fault, NetApp Technical Support will advise the customer to open a case with the other vendor and then continue to work with the customer and other vendor to jointly resolve the issue.

1.30 CAN I ADD STORAGE BEHIND AN EXISTING V-SERIES DEPLOYMENT?

Yes, you can add additional storage behind a deployed V-Series controller. You can add additional storage with any of these methods. Each method has its own set of risks, and you should follow proper procedures. Add array LUNs to an existing LUN group. Add a new array LUN group to an existing storage array. Add a new storage array to an existing V-Series deployment. Add NetApp shelves to existing loops. Add NetApp shelves to new loops. Making changes to a production system introduces risk. If changes must be made that risk disrupting data availability, we strongly recommend they be made during a maintenance window or even while the system is offline.

V-Series FAQ

2
2.1

TECHNICAL QUESTIONS
ARE THERE SPECIFIC CABLING AND ZONING MODELS FOR ATTACHING THE VSERIES CONTROLLER TO THE STORAGE ARRAY?

The recommended and most common way to attach a V-Series controller to a storage array is with a fourarray-port LUN group. The array LUNs in the LUN group are assigned to the four array ports with the same LUN ID. Each V-Series controller has two dedicated paths to the array LUNs through different SANs, and two HBA cards are installed in each V-Series controller.

The two-array-port model can be used if your system is small, if youre doing a demo, or if you are array port limited. The two-array-port model is shown below. Notice that both V-Series 0a ports are zoned into the same array port and must be in separate zones (use 1-1 initiator to target zoning).

10

V-Series FAQ

2.2

CAN A SINGLE V-SERIES ATTACH TO MULTIPLE ARRAY LUN GROUPS?

Yes, V-Series can also attach to multiple array LUN groups on some storage arrays. Multiple array LUN groups are not supported with all storage arrays. Refer to the V-Series support matrix to see if your storage array supports attaching multiple array LUN groups. When attaching to multiple array LUN groups, use separate initiators for each array target port and make sure of proper one-to-one zoning for each path. Shown below are two storage arrays LUN groups behind a single V-Series controller in the supported configuration.

2.3

CAN A V-SERIES CONTROLLER ATTACH TO MULTIPLE STORAGE ARRAYS?

Yes, V-Series can attach to one storage array or multiple storage arrays. When attaching to multiple storage arrays, use separate initiators for each array target port and make sure of proper one-to-one zoning for each path. Shown here are two storage arrays behind a single V-Series controller in the supported configuration.

11

V-Series FAQ

2.4

CAN I USE A DIRECT-ATTACH MODEL BETWEEN THE V-SERIES CONTROLLER AND THE STORAGE ARRAY?

V-Series does support direct attach or fabric attach for some storage arrays. The direct-attach model is shown, and it is identical to the fabric-attach model with the switches removed. The direct-attach model is not supported with all storage arrays. Consult the support matrix to see if your array storage supports the direct-attach model. If your system is direct attached, make sure the storage array ports are configured for loop mode.

2.5

HOW DO I DECIDE WHEN A SINGLE FOUR-ARRAY-PORT LUN GROUP IS OK OR WHEN I WOULD NEED TO HAVE TWO OR MORE FOUR-PORT-ARRAY LUN GROUPS ON A SINGLE STORAGE ARRAY?

V-Series can support up to 100 array LUNs in a single array LUN group. The array LUNs can be built on any type of storage array disks. System design might vary greatly depending on factors such as the type of disks in the storage array, expected system performance, and size of the array LUNs. With large archival systems, using 100 LUNs on SATA-based disks with 1TB array LUNs is okay. For performance-type systems in which you have FC drives in the array, you might want to have fewer LUNs in each LUN group and reduce the size of the array LUNs for each LUN group.

2.6

HOW DO I CALCULATE USABLE V-SERIES SPACE GIVEN A FIXED AMOUNT OF STORAGE ARRAY LUN CAPACITY? HOW DO I CALCULATE REQUIRED STORAGE ARRAY CAPACITY GIVEN THE DESIRED FRONT-END USE REQUIREMENTS?

NetApp usable space for any given array LUN includes NetApp WAFL and checksum overhead. For example, a 100GB array LUN given to a V-Series controller will include WAFL overhead of 11% and 12.5% checksum overhead, giving ~80GB usable space.

12

V-Series FAQ

2.7

HOW DO I SIZE A V-SERIES SYSTEM?

How much space do you need for your applications? How many IOPs or MB/s do you need, or how fast do you need them?

The two parts of system sizing are capacity and performance:

The capacity question is something your NetApp or NetApp Certified Partner account team can assist with. In addition to the amount of space your data requires, overheads are needed for projected growth, Snapshot copies, and file system overheads. In some cases, especially when hosting server virtualization platforms like Citrix or VMware, NetApp dedupe can substantially reduce the amount of capacity required. Your account teams have tools to factor these savings into the overall system design. The performance part of the equation can be difficult to know, but your NetApp or NetApp Certified Partner account manager and systems engineers can help you figure this out using tools NetApp developed for this purpose. This data will provide the recommended model of V-Series controller required, as well as the recommended number of disk spindles required on the third-party array.

2.8

HOW DO I MIGRATE EXISTING DATA RESIDING ON THIRD-PARTY ARRAYS BEING SERVED TO HOSTS AND BRING IT UNDER V-SERIES CONTROL AND MANAGEMENT?

When installing a V-Series controller in front of a third-party storage array, the array LUNs presented to the V-Series controller must not contain any data. Any data on these array LUNs will be overwritten by the VSeries controller. The array LUNs provisioned to V-Series create NetApp RAID groups, aggregates, flexible volumes, and NetApp LUNs. These NetApp LUNs are served up to the hosts on the front end. If there is existing data on the storage array that needs to be migrated onto a V-Series controller, the steps are as follows: Assign the unused array LUNs to the V-Series controller. The unused array LUNs can come from either the array or from NetApp disks. Configure NetApp LUNs on the V-Series controller and provision these LUNs to the hosts or clients. The hosts or clients will also be attached to their existing/legacy array LUNs in addition to their NetApp LUNs. You can now copy the existing data from the legacy array LUN to the NetApp LUN. Performing a front-end migration from the legacy storage to the new NetApp storage could vary depending on the type of hosts or applications; for example, you might use application-based migration tools or host-based volume mirroring. Use the best process for your type of data and hosts. Upon completion of the migration process, release the legacy LUNs from host usage and reassign them to the V-Series controller. Repeat the process. In some cases, the storage array capacity might be fully used by existing hosts and you will need to add some extra capacity for swing space. You might consider using NetApp disk shelves for swing space. In other cases, the storage array capacity might be partially used and you can use the unused storage array capacity for the swing space to initially build V-Series. As part of your design, you will want to wind up with a system that meets the overall best practices layouts.

13

V-Series FAQ

2.9

WHAT PRECAUTIONS SHOULD I TAKE PRIOR TO DOING SYSTEM MAINTENANCE, INCLUDING FABRIC OR STORAGE ARRAY MAINTENANCE?

A V-Series system includes the V-Series controllers, back-end fabric that connects the controller to the array, and the back-end storage array. If only a single path to the array LUNs is active, then removing the remaining path or the other array controller for maintenance will cause the system to panic. Prior to performing maintenance on the system, we recommend you: Verify that there are two paths from the V-Series controller through the fabric to the array LUNs. Use commands such as storage show disk p, sysconfig, and sysconfig a. Send out an AutoSupport (ASUP) message prior to maintenance. In addition to ASUP, collect outputs from disk show v. These items are also documented in the V-Series maintenance guide located on http://now.netapp.com.

2.10 WHAT IS REQUIRED IN ORDER TO ADD OR USE A NETAPP DISK SHELF ON A VSERIES CONTROLLER?
The way to attach NetApp disk shelves to V-Series controllers is documented in the V-Series Systems Implementation Guide for Native Disk Shelves. When using multipath I/O (MP-HA) configurations between an active-active controller and the NetApp disk shelf, you need to set the "fc-non-array-adapter-list parameter on each controller for each FC port used. From the control prompt (while in takeover mode or while the controller is halted), you run the following command to use 0a and 0c to access a NetApp shelf using mi-io: setenv fc-non-array-adapter-list Then boot Data ONTAP normally. 0a,0c

Single port access to the disk shelf does not require any special settings.

These items are also documented in the V-Series maintenance guide located on http://now.netapp.com.

2.11 WHAT HAPPENS IF I DONT SET THE FC-NON-ARRAY-ADAPTER-LIST PARAMETER CORRECTLY FOR MY HA-MP?
This parameter is used only for HA-MP configurations. Non-HA-MP configurations do not need to set fc-nonarray-adapter-list. During boot, Data ONTAP will panic with an error message of this form: sanown: received add for already known disk in process sanown_notify

2.12 HOW MANY FIBER PATHS SHOULD THERE BE BETWEEN A V-SERIES CONTROLLER AND AN ARRAY OR A LUN?
A V-Series controller must have exactly two paths to any array LUN. The two paths must be on separate fabrics and to separate array controllers. Typically for a V3000 system, VS-1 port pair 0a/0c could access a single LUN group, and the partner controller VS-2 would use port pair 0a/0c to also access LUN group 1 but through different array ports. Refer to the four-port LUN group illustration above.

14

V-Series FAQ

2.13 HOW MANY FABRIC HOPS CAN I HAVE BETWEEN THE V-SERIES CONTROLLER AND THE ARRAY?
We support one hop between the storage array and the V-Series controller. A hop is the number of interswitch links (ISLs). So a V-Seriescorecorestorage array is 1 hop. For larger fabric topologies using more hops, submit a PVR.

2.14 HOW MANY ARRAY LUNS CAN I PUT ON A ONE-FS INITIATOR PORT?
V-Series can support 100 array LUNs behind any given controller initiator port. So each array four-port LUN group can have 100 LUNs presented to the V-Series controller.

2.15 CAN A V-SERIES INITIATOR FC PORT ATTACH TO MULTIPLE STORAGE ARRAY TARGET PORTS USING THE FABRIC FOR FAN-IN?
Fan-in of storage array ports to a single NetApp FC port is not supported. Use one-to-one topology where each NetApp initiator port is attached to a single storage array target port.

2.16 CAN I SHARE STORAGE ARRAY TARGET PORTS WITH OTHER HOSTS OR WITH OTHER V-SERIES CONTROLLERS?
Storage array target ports should be dedicated to the V-Series controller. Do not share the storage array target ports with other host ports or even with other V-Series initiator ports.

2.17 ARE SOFT ZONING AND HARD ZONING BOTH SUPPORTED?

Yes, you can use either hard zoning or soft zoning.

2.18 WHAT ARE THE MINIMUM NUMBER AND THE SIZE OF ARRAY LUNS NEEDED FOR A V-SERIES DEPLOYMENT?
A standalone V-Series system requires one array LUN for its root volume. A clustered or HA pair of V-Series controllers requires at least four array LUNs. Two array LUNs are used for each controller root drive, and the other two are spare array LUNs that are used for cluster mailboxes. Refer to the V-Series support matrix for the size requirements for the root volume and the spare array LUNs for each Data ONTAP release and platform.

2.19 SHOULD I INSTALL THE ROOT VOLUME ON AN AGGREGATE OF NETAPP DISKS OR ON STORAGE ARRAY LUNS?
If the V-Series controller is installed with both NetApp storage and with third-party storage arrays, we recommend the root volume be installed on NetApp disks. If there are no NetApp disks installed, then use a single-array LUN for the root flexible volume.

2.20 IS A MINIMUM SIZE FOR THE ROOT VOLUME OR FOR THE STORAGE ARRAY LUN NEEDED FOR THE ROOT VOLUME?
Yes. For specific root volume size details, consult the Aggregate and Volume Limits section in the V-Series support matrix. The root volume size varies for each controller model, and the underlying array LUN used for the root volume should be properly sized.

2.21 WHY DO I NEED A SPARE LUN ON MY V-SERIES CONTROLLER

A spare LUN is needed for the diagnostic purpose of capturing a core file. The spare LUN requirement can be either a LUN from the array (in an array-only configuration) or a NetApp disk if NetApp shelves are used with your V-Series controller.

15

V-Series FAQ

2.22 CAN I USE AN ARRAY LUN WITH AN ID OF 0 (LUN0)?

We recommend not using a LUN0. Start your array LUN assignments with 1 or some other non-0 number. If you currently have a LUN0 assigned, you dont need to make any changes unless instructed by NetApp support.

2.23 CAN I MIX DIFFERENT-SIZE LUNS INTO THE SAME NETAPP AGGREGATE?
We strongly recommend that all array LUNs within an aggregate be the same size for the most consistent performance.

2.24 WHAT SIZE STORAGE ARRAY LUNS CAN ATTACH TO A V-SERIES CONTROLLER?
The maximum array LUN size tracks with the maximum disk size supported by FAS. V-Series currently supports array LUNs between 1GB and 1TB. But note that different storage array vendors calculate GB and TB differently, so check the implementation guide for the storage array you work with to verify the specific limit. Typically, the maximum supported array LUN size is 1952GB. The specific limits are documented in the V-Series support matrix by platform and Data ONTAP release.

2.25 HOW DO YOU RECOMMEND I SIZE MY STORAGE ARRAY LUNS FOR A V-SERIES CONTROLLER?
V-Series currently supports array LUNs up to 2TB. But array RAID group sizes and disk sizes vary, so one size does not fit all for array LUN sizing. A typical deployment takes an array RAID group and creates two, four, or six LUNs in the RAID group, which gives good overall design flexibility. Lets use the example of an array 6+1 RAID group with 400GB drives. There is approximately 2400GB of space on the RAID group, creating 4 equal-sized LUNs of 600GB each.

2.26 DOES V-SERIES SUPPORT BACK-END STORAGE ARRAY THIN PROVISIONING?

No, you cannot use storage array thin provisioning behind a V-Series controller. Data ONTAP requires access to the entire capacity of the array LUN. Using array thin provisioning results in system panics and data loss. You can use NetApp thin provisioning for front-end host or client use.

2.27 SOME STORAGE ARRAYS CAN DYNAMICALLY GROW AN ARRAY LUN. IS GROWING AN ARRAY LUN SUPPORTED BEHIND A V-SERIES CONTROLLER?
No, advanced array features such as dynamic array LUN resizing is not supported behind a V-Series controller. However, our controllers do support storage resizing for hosts or clients attached to the V-Series controller.

2.28 CAN I USE HITACHI DYNAMIC PROVISIONING (HDP) FOR LUNS PRESENTED TO A V-SERIES CONTROLLER?
HDP is supported on AMS arrays today. USP-V and HP-XP usage of HDP is not currently supported today but might be supported in the future. See V-Series support matrix for the latest news on HDP support. Overprovisioning dynamic provisioning pools (DP pools) that provide LUNs to a V-Series system is prohibited. Never assign more logical unit capacity than the total capacity of the DP pool. Consult your Hitachi documentation or the support provider for your array for additional information. If you are unsure how to prevent overprovisioning of the DP pool, then use standard RAID group type when creating logical units.

16

V-Series FAQ

2.29 CAN I USE STORAGE ARRAY-BASED REPLICATION AND HAVE A V-SERIES CONTROLLER AT THE REMOTE ARRAY SITE?
No, advanced storage array features such as storage array-based replication are not supported behind a VSeries controller. If you require replication, use NetApp replication tools.

2.30 ALL THE V-SERIES IMPLEMENTATION DOCUMENTS DESCRIBE A LAYOUT IN WHICH PORTS FROM ONE SIDE OF A STORAGE ARRAY CONTROLLER ARE ATTACHED TO ONE FABRIC. MY SAN DESIGN IS A CROSS IN WHICH A SINGLE STORAGE ARRAY CONTROLLER ATTACHES TO BOTH FABRICS. IS A CROSSED BACK END SUPPORTED?
No, a crossed back end, in which one storage array controller is attached to both fabrics, is not supported. When attaching the storage array controllers to the back-end fabric, attach all the FC ports from one array controller to the same fabric. For more details, see KB41604 on http://now.netapp.com.

2.31 ARE THERE ANY SPECIAL REQUIREMENTS FOR USING HDS USP-V WITH A VIRTUALIZED ARRAY BEHIND THE USP-V?
It is a best practice to have the V-Series system use array LUNs directly from the array rather than be virtualized behind the USP-V. Otherwise, performance problems can easily occur. If a customer must use this configuration, then strict requirements need to be followed: V-Series root volume and spare core volumes should be on USP internal disks. Do not mix array LUN types when building the aggregates. For example, do not mix array LUNs based on either FC or SATA drives, and dont mix USP internal and virtualized LUNs into the same aggregate. BCS is only supported (not ZCS) when using external drives behind the Tagmastore. Internal drives can be assigned either as BCS or as ZCS. Follow HDS recommendations for external storage array attachment and for queue depth settings on the arrays. The V-Series settings are the default settings. If the storage array behind the USP-V is on the V-Series support matrix, NetApp strongly recommends attaching directly to the back-end array and not using the USP-V.

2.32 IS THERE ADDED LATENCY WHEN INSTALLING A V-SERIES CONTROLLER IN FRONT OF A STORAGE ARRAY?
There is no additional write latency as data is written to NetApp cache and no read latency when the data is in NetApp cache. For reads coming from the back-end storage array, added read latency is in the microsecond range and can vary depending on type of back-end connectivity, disk type and speed, and controller cache size.

2.33 CAN I USE SNAPMIRROR BETWEEN A V-SERIES CONTROLLER WITH ARRAY LUNS AND A V-SERIES CONTROLLER OR FAS WITH NETAPP SHELVES?
Yes, SnapMirror can be used between FAS and V-Series systems.

2.34 CAN I USE SYNCMIRROR ON A V-SERIES CONTROLLER BETWEEN DIFFERENT TYPES OF STORAGE ARRAYS OR DIFFERENT TYPES OF DISKS WITHIN THE ARRAY?
SyncMirror can be used for transparent data mirroring between similar storage array types and vendors only. SyncMirror is only supported when used with array LUNs from the same array family and with similar configurations. See the integration guides for which storage arrays are in the same family. Additional requirements include the following: You can't mix FC and SATA in the same aggregate. You can't mix 2gb and 4gb in the same aggregate.

17

V-Series FAQ

RAID groups must be similarly configured on the array; there can be no mixed RAID levels.

2.35 CAN I USE SYNCMIRROR ON A V-SERIES CONTROLLER BETWEEN ARRAY LUNS AND NETAPP DISKS?
No. SyncMirror between aggregates built from array LUNs and aggregates built on NetApp disks is not supported and will not work. SyncMirror operates at the aggregate level.

2.36 CAN I GET ANY STORAGE ARRAY INFORMATION FROM THE V-SERIES CONTROLLER?
Data ONTAP has limited information available from the storage array and provides no detailed array LUN layout information. You can review the information that is available in SYSCONFIG-A, which includes array LUN size and encrypted array model information.

2.37 DOES DATA ONTAP REGISTER THE ARRAY LUNS DIFFERENTLY WHEN THEY ARE DIRECTLY ATTACHED VERSUS FABRIC ATTACHED?
A typical sysconfig output will show some differences in an array LUN that is fabric attached with fc-nomgmt? set and one that is directly attached. In all cases, these array LUNs are listed under each NetApp FC port. Fabric-attached systems use:

Switch00:96.127L15 :HITACHI OPEN-V 0000 178.5GB 512B/sect (50 0443F0000) Where: Switch00 is the switch that is attached to the array port 96 is the port used on switch EMBHNX00 to attach to the array 127 is the alpha ID of the switch (or array)?? L15 is the array assignment of the LUN id
If fc-no-mgmt? is set, then a fabric-attached array will show as:

FPN[20040060698061d2]:0.126L15 : HITACHI 512B/sect (50 076EB0156)

FPN of the switch L15 is the LUN ID

OPEN-V*3 0000 422.9GB

Also note the OPEN-V*3. This means the UDS array has created a LUSE on the array with three array LUNs. LUSEs are unique to the HDS USP-V array. They do work, but we recommend just using larger array LUNs. If the array is directly attached, then the LUNs show as:

0a.1L15: HITACHI 06E120162)

OPEN-V

0000 244.0GB 512B/sect (50

1 is the what??, array port alpha ID??? L15 is the LUN id. 2.38 INTO WHICH SWITCH AND SWITCH PORT IS MY V-SERIES PHYSICALLY PLUGGED?
A sysconfiga for each NetApp port will be the switch port that is cabled into the V-Series controller.

Switch Port:
18 V-Series FAQ

EMBHNX00:110

However, if you have fc-no-mgmt? set, you will not be able to see the switch per the following output:

Switch Port:

??

2.39 WHAT ARE CHECKSUMS, AND ARE THEY REQUIRED?

A checksum is a form of data redundancy check, a simple measure for protecting the integrity of data through error detection. Checksums are required. Checksum type is assigned when the raw array LUN is assigned to the V-Series controller. BCS is the default and recommended type of checksum. Data ONTAP reserves 12.5% of the space in the array LUN for the BCS. All features are supported when using BCS-assigned LUNs. Zone checksums are a V-Series option but are not recommended. When using ZCS, there is a performance degradation of ~15% for some workloads. There is no additional space reserved for ZCS. Not all features are supported when using ZCS.

2.40 CAN I MIX BCS AND ZCS INTO THE SAME AGGREGATE?
Aggregates can only contain either BCS or ZCS LUNs and cannot be intermixed.

2.41 HOW CAN I CHANGE ZCS LUN ASSIGNMENT TO BCS ASSIGNMENT?

You can change a ZCS-assigned array LUN to a BCS-assigned array LUN. The array LUN must first be a spare array LUN before you change it from ZCS to BCS, because data is not preserved on the original ZCS array LUN. The ZCS array LUN must we removed from the V-Series controller and then reassigned as a BCS array LUN.

2.42 HOW DOES V-SERIES DO PATHING ASSIGNMENTS TO ARRAY LUNS?

Each array LUN has two paths from the V-Series controller, an active path and a passive path. For tier-1 arrays, the total LUN path balancing is accomplished by splitting the primary path for half the LUNs. Tier-2 arrays will follow the primary pathing as assigned from the array.

2.43 IF MY PATHS TO LUNS ARE NOT BALANCED, WHAT CAN I DO?

Pathing assignments to back-end array LUNs should be balanced for best system performance. Tier-1 arrays paths are assigned equally to each controller path when the controller is booted or during a cluster takeover/giveback. Tier-2 array paths are assigned on the array, and the NetApp controller will follow the array pathing primary/alternate assignments.

2.44 CAN I TRANSPARENTLY REPLACE A FABRIC BEHIND A V-SERIES CONTROLLER?

Yes, you can replace a fabric between the V-Series controller and a storage array provided there is fabric redundancy in your deployment. However, great care should be taken when performing tasks such as this on live systems. Make sure you do this during a maintenance window. Removing a fabric will cause all pathing to use only the surviving fabric. Replace the other fabric and then make sure proper zoning is in place.

19

V-Series FAQ

2.45 IF A V-SERIES CONTROLLER HAS MULTIPLE AGGREGATES THAT ARE EITHER BUILT ON THIRD-PARTY ARRAY LUNS OR BUILT ON NETAPP DISKS AND ONE AGGREGATE FAILS, WHAT HAPPENS TO DATA ONTAP, THE OTHER AGGREGATES, OR THE VOLUMES?
If Data ONTAP detects a data inconsistency, the controller will panic to preserve state and reboot. Only the affected aggregates will be inconsistent. Other aggregates will only be affected because of the system reboot.

2.46 WHAT HAPPENS IF I MOVE THE CABLE FROM ONE SWITCH FC PORT TO ANOTHER FC PORT?
We dont recommend making changes to a production system outside of a maintenance window. Moving the cable between the switch and the array with soft zoning will simply change the NetApp reported disk name: for example, Switch00:96.127L15 to Switch00:83.127L15. Notice the switch port change from 96 to 83. Moving the cable between the V-Series controller and the switch with soft zoning will simply change the NetApp reported switch port for each FC port, from, say, EMBHNX00:110 to EMBHNX00:97. With hard zoning in place, you will have to rezone because of the new switch FC ports used.

2.47 CAN I REMOVE ARRAY LUNS FROM A V-SERIES CONTROLLER?

Yes, you can remove array LUNs from V-Series use. Making changes to a production system introduces risk, however. If changes must be made that risk disrupting data availability, we strongly recommend they be made during a maintenance window or possibly even while the system is offline. To permanently remove the array LUNs (that is, give back to the array) or to change the checksum assignments, array LUNs need to be spare LUNs on the V-Series controller. Use the command disk remove w. When changing the pooling assignments, the host ID, and so on, you need to remove the ownership with disk remove_ownership. These items are also documented in the V-Series maintenance guide located on http://now.netapp.com.

2.48 HOW DO I REPLACE THE NVRAM ON A V-SERIES CONTROLLER? ARE THESE STEPS THE SAME AS ON A FAS CONTROLLER?
Replacing NVRAM on a V-Series controller follows the same process as a FAS, but there are differences because of the back-end software disk ownership attach of the array LUNs. After the NVRAM is replaced and before booting the controller, the failed controller must be booted to maintenance mode, and the array LUN ownership must be reassigned from the old SYS_ID to the new SYS_ID. This change of ownership command can only be issued from the surviving V-Series node. If you run this change of ownership command from the failed node while in maintenance mode, you will panic the surviving controller.

2.49 ARE THE V-SERIES MOTHERBOARD REPLACEMENT STEPS THE SAME AS THOSE FOR A FAS MOTHERBOARD REPLACEMENT?
Replacing the motherboard on a V-Series controller is similar to replacing one on a FAS controller and follows the same process as on a FAS controller but there are some differences due to the back-end fabric and the array host groups. A new motherboard will come with new WWPNs. The array could be attached to a V-Series controller using FC ports from the motherboard or from expansion slot FC ports. If you are using expansion slot cards as FC initiator ports, no back-end changes are needed after a motherboard replacement. If your array is attached using motherboard FC ports, you will have to boot the controller to

20

V-Series FAQ

maintenance mode and then change the fabric zoning and array host group changes prior to booting the VSeries controller.

2.50 ARE THE V-SERIES V6000 FC EXPANSION SLOT MODULE STEPS THE SAME AS FOR A FAS FC EXPANSION SLOT REPLACEMENT?
Replacing the V6000 FC expansion slot module on a V-Series controller is similar to doing so on FAS and follows the same process as on a FAS, but there are some differences due to the back-end fabric and the array host groups. If the new module comes with new WWPNs, you have to boot the controller to maintenance mode and then change the fabric zoning and array host group changes prior to booting the VSeries controller.

Copyright 2010 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, AutoSupport, Data ONTAP, MetroCluster, NOW, RAID-DP, SnapLock, SnapMirror, Snapshot, SyncMirror, and WAFL are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. VMware is a registered trademark of VMware, Inc. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.

V-Series FAQ