It depends on whether you want to have both nodes serving data (active-active) or you're happy relegating the 2nd node to a passive "backup" role. If active-active, you'd have one or more aggregates configured on each node. This will have a bit more "parity disk partition" tax than using all data partitions for one big aggregate, but you have more data serving performance with both nodes active.   I'd look at these docs...   Root-data partitioning concept: http://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-concepts/GUID-B745CFA8-2C4C-47F1-A984-B95D3EBCAAB4.html   Manually assigning ownership of partitioned disks http://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-psmg/GUID-07302AD3-F820-48F7-BD27-68DB0C2C49B5.html   Setting up an active-passive configuration on nodes using root-data partitioning http://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-psmg/GUID-4AC35094-4077-4F1E-8D6E-82BF111354B0.html   I can't speak to your LUN question... but I wouldn't think it matters.  See section 5.3 here: TR-4080: Best Practices for Scalable SAN https://www.netapp.com/us/media/tr-4080.pdf ... View more

If you're willing to consider 9.2 (GA), there's a nifty new boot menu option for re-partitioning systems with "one click". From the release notes: https://library.netapp.com/ecm/ecm_download_file/ECMLP2492508   Beginning with ONTAP 9.2, a new root-data partitioning option is available from the Boot Menu that provides additional management features for disks that are configured for root-data partitioning.   If you want to stick with 9.1P5, this KB article takes you through reinitialization process.    https://kb.netapp.com/support/s/article/ka31A00000013aJ/How-to-convert-or-initialize-a-system-for-Root-Data-Data-Partitioning   Note: The KB works well for FAS (non-AFF), too. You'll just end up with root-data, not root-data-data, partitions. When it's done, each node will "own" half of the 20 disks from a container perspective, and the smaller P2 root partitions will be used to build the root aggregates (and leave 1 spare). The large P1 data partitions will be "spare" for creating data aggregates from either node, as you see fit.   ... View more

+1 for robin's comments on the P2 partitions not being balanced across node 1 and node 2.   Q1: What ONTAP version are you running?   Q2: Do you plan to run in an active-passive configuration or do you want both nodes to normally serve data from their own aggregates (active-active)?   Q3: Are you in a position to destroy the data on the system and reinitialize? It might be the fastest path to configuring the system according to best practices.   ... View more

It's perfectly fine to span across shelves. ... View more

8.1.2 is very old ONTAP software. Upgrade to the latest recommended release for your FAS model. ... View more

Yes, the Remote Support Diagnostics Tool and the Remote Support Agent component of it on the Service Processors is no longer functional. See: End of Life: Remote Support Diagnostics Tool (RSDT) and Remote Support Enterprise (RSE)   You should definitely disable the RSA feature on all of your Service Processors to save bandwidth and SP CPU cycles. See: https://kb.netapp.com/support/s/article/ka31A00000012fX/data-ontap-remote-support-evolution-how-to-enable-aod-and-disable-rsdt     ... View more

In addition to changing to the correct 10GbE SFP's, you also need to ensure that the port pair is in the correct mode: CNA mode.  By default, the ports are in FC mode.   Use the command: system node hardware unified-connect modify http://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-cmpr-900/system__node__hardware__unified-connect__modify.html   Notes: The mode applies to both ports in the "pair" - for FAS2552, the port pairs are e0c/e0d and e0e/e0f (or for FC, 0c/0d and 0e/ef) After changing the mode, you must reboot the node for the change to take effect After reboot, you can verify things are set up correctly: command: system node hardware unified-connect show sysconfig or sysconfig -a: you'll see e0c and e0d in the output, now. ... View more

Hi,   You didn't mention which exact AFF model you're getting...   Based on your description of your performance bottlenecks a new AFF system should mitigate those bottlenecks, nicely.   I would request some performance modeling estimates for your new AFF system from your NetApp sales rep. ... View more

I'm glad to hear that the problem between your SMTP gateway and our SMTP servers has corrected itself...   To be clear, SMTP transport for AutoSupport to NetApp is still supported. It's just not the recommended choice.   See this technical report: Data ONTAP AutoSupport and On Demand Configuration   HTTPS   HTTPS uses TCP port 443. This protocol is the default transport protocol. This protocol supports AutoSupport On Demand and uploads of large files.   When AutoSupport messages are sent using HTTPS, the X.509 certificate of the NetApp AutoSupport server is validated, and the message content is encrypted.   NetApp strongly recommends using HTTPS transport for AutoSupport delivery for the following reasons:   HTTPS transport is significantly more secure and reliable than SMTP HTTPS is not restricted by SMTP e-mail size constraints HTTPS is easy to configure and manage HTTPS transport can be used along with SMTP delivery to internal customer personnel or systems HTTPS enables integrated AutoSupport On Demand capability to expedite case resolution ... View more

Robinpeter's suggestion was excellent - you can completely avoid SMTP issues by switching to HTTPS and all of the benefits that come with that transport protocol.   If you still need to resolve the SMTP issue, please contact NetApp via the Feedback Form on the NetApp Support Site. (select Category: AutoSupport and Sub Category: Other). Provide all of the necessary details about your SMTP relays, domain name, and ideally - detailed transaction logs. ... View more

I  noticed that this is an IBM N-series variant - you'd need to work with IBM Support.   That said, take a look at this public report for Bug 245162. It has some guidance (e.g. reseat the module) "CEMI Micro controller Fatal Error" leads to loss of access to AT-FCX module http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=245162 ... View more

Almost.   48 HDDs.   Root aggr: 1D + 2P = 3 Data aggr: 2 x (20D + 2P) = 44 Spare: 1   Root-data partitioning can improve the efficiency, but it's not available in your configuration. ... View more

What FAS platform?   The first SCSI reservation issue is indicative of downrev disk FW.   8.1.2 is very old. The things I would do before testing again are: - upgrade to 8.1.4P10 (at least). - download disk and shelf firmware packages and install/update - download latest compatible SP FW and update - download and install the latest DQP file.   ... View more

BMC can't proxy or forward AutoSupport on behalf of its host filer.  However, it can send a few kinds of AutoSupport for special situations (system down, etc.) via SMTP, if configured to do so via the AutoSupport options on the filer (if that makes sense - it gets that config info internall from its host).  It just needs a path to reach the SMTP gateway that is defined. ... View more