About andris

andris · ‎2017-11-14

I don't believe you need licensed FCP or iSCSI... CLAM itself runs regardless of licensing. I think the easiest thing to do is just create an empty portset. cluster1::> portset create -vserver vs1 -portset ps1 -protocol mixed

andris · ‎2017-11-13

It is important to create a SAN object such as a LUN, LIF, or portset when using a single-cluster interconnect on a two-node switchless cluster of FAS22xx or FAS25xx storage systems, even if there is no intention of using the SAN object. The reason is the cluster will continue to serve data if the single-cluster interconnect path is broken. The details: If at least one SAN object is configured (LUN, portset, etc), then the Cluster Liveliness Availability Monitor (CLAM) induces a takeover by one of the nodes after the cluster interconnect timeout. The taking over node must be otherwise healthy and capable of performing the takeover. The node which took over is now in a "quorum of one" as for any other takeover, and full data services, NAS and SAN, are resumed on this node. After fixing the issue with the cluster interconnect, the administrator can perform a giveback to resume normal two-node operation. If the cluster does not have any SAN objects, then no automatic takeover occurs -- both nodes remain out of quorum and neither will serve data. Manual intervention will be required to either restore the cluster interconnect or perform a takeover.

andris · ‎2017-11-03

Yes, that's the quickest way to resolve the hostname sync issue between the ONTAP node and its SP. Related KB article: https://kb.netapp.com/support/s/article/what-is-the-sp-setup-option-and-how-can-it-be-reset

andris · ‎2017-10-31

I'd open a technical case to get additional formal assistance. All of the latest MIBs are available on the NetApp Support Site: https://mysupport.netapp.com/NOW/download/tools/mib/

andris · ‎2017-10-27

Strange.. the FCP and LUN items should be in the "blocks" group. MetroCluster-related info can be found in the "metrocluster" group. Have you tried a MIB walk/dump to see what's there, overall?

andris · ‎2017-10-27

SolidFire products do not support AutoSupport at this time. However, ActiveIQ for SolidFire can be enabled. Once enabled, you can access SolidFire ActiveIQ information at: http://activeiq.solidfire.com/

andris · ‎2017-10-26

The 1st link was meant to give guidance on how to reach the boot menu. The screenshot in that link is not based on ONTAP 9.2 (when option 9 was introduced). The 2nd link is the release note item discussing ADP boot menu (Option 9). I should have just provided you this KB article link, in retrospect: https://kb.netapp.com/support/s/article/ka21A000000DFjY/ONTAP-Boot-Menu-Option-9-Configure-Advanced-Drive-Partitioning

andris · ‎2017-10-26

Sorry for the cryptic response! Option 9 (and 9b) is in the boot menu of ONTAP. You would press "Ctrl-C" from the console when starting up ONTAP to access it: Boot menu info: http://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-sag/GUID-B86616AE-D345-4B44-AA56-BBC7ABD44068.html Additional root-data partitioning management options

andris · ‎2017-10-26

Only AFF systems support ADP v2 (root-data-data) partitioning. Since you're on ONTAP 9.2+, to get the "right" ADP setup for your system, just run Option 9b from BOTH HA partners.

andris · ‎2017-10-25

In the spirit of "teaching to fish"... this type of info is available in the Hardware Universe. Select the platform, display the results, look at the Size, Weight, Acoustic, Power table.

andris · ‎2017-10-24

The additional information section of the ONTAP® 9.0 NFS Configuration Power Guide has a bunch of great resources to check out. Specifically: NetApp Technical Report 4182: Ethernet Storage Design Considerations and Best Practices for Clustered Data ONTAP Configurations

andris · ‎2017-10-22

That is correct. Using Telnet is not a security best practice. See: https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1064173

andris · ‎2017-10-22

It doesn't matter if you have keys set up or not... you can't mix SED and non-SED drives in an HA pair. http://docs.netapp.com/ontap-9/topic/com.netapp.doc.pow-nve/GUID-5DD87E19-F311-4B2C-898C-285032E0B116.html

andris · ‎2017-10-20

I'm curious as to how the FAS62xx ended up with four cluster LIFs in the first place. Best practices only require 2 cluster ports and LIFs. Regardless, if you really only have 2 cluster ports e0a and e0b, just delete the 2 extra LIFs. Make sure you end up with a cluster LIF home-ported on each port. See: https://kb.netapp.com/support/s/article/ka31A0000004YpD/How-to-delete-a-Cluster-LIF

andris · ‎2017-10-20

You might want to open up a technical case with Support to answer the specific questions you have... More resources to check out: How quotas work with users and groups https://kb.netapp.com/support/s/article/ka21A00000058fo/FAQ-Quotas

andris · ‎2017-10-20

Nope. Go for it.

andris · ‎2017-10-17

I was able to find your support case... as noted, the only other possible reason beside it being a transient issue might be that the MSATA boot device is not fully seated. Unless this issue reoccurs, at your earliest convenience (next maintenance window) consider halting the node, opening up the controller PCM and reseating the MSATA boot device.

andris · ‎2017-10-09

Hi Richard, You sure brought up a brain-teaser… After some discussion with colleagues, listing the mailhost name multiple times in the AutoSupport configuration might speed things up, if: DNS resolution round-robins multiple SMTP server IP addresses The connection errors out immediately (e.g. 421 Service Not Available) This is because an immediate connection failure results in the AutoSupport daemon moving on to the next configured SMTP server entry, immediately. Otherwise, the AutoSupport retry logic kicks in, where (by default) retries are attempted every 4 minutes, 15 times.

andris · ‎2017-10-07

See: https://community.netapp.com/t5/Data-ONTAP-Discussions/Ontap-Select-9-2-NodeCreateFailed-InvalidRequestFault/td-p/132591/page/2 It looks like you need ESX 6.0

andris · ‎2017-10-07

Is the download taking longer than 45 minutes? See Bug 1048640 You'll need tech support assistance for the workaround.

andris · ‎2017-10-07

What ONTAP version is installed? Even/Odd disk ownership is not the best practice for AFF systems. Best practice is 0-11 Node A, 12-23 node B. If ONTAP 9.2, you can reinitialize to best practices using the new Option 9 boot menu. If ONTAP 9.0+, use this KB to reinitialize with root-data-data partitioning. Step 9 shows the disk assignment details. https://kb.netapp.com/support/s/article/How-to-convert-or-initialize-a-system-for-Root-Data-Data-Partitioning?t=1507373282342

andris · ‎2017-10-07

A few points... 1. you should have several management IP addresses: cluster_mgmt, node1_mgmt and node2_mgmt. Q: What are the IP's for node1_mgmt and node2_mgmt? 2. HW Assist requires a communication path between each other's SP's and node_mgmt IP addresses, i.e. node1 SP <-> node 2 node_mgmt LIF node 2 SP <-> node 1 node_mgmt LIF NOTE: This means the service processor's 10.x.x.x subnet and configured default gateway must be able to reach the 134.x.x.x subnet where your node_mgmt LIF's are... ping the 10.x.x.x SP addresses to help confirm this. 3. The storage failover modify commands need to specify the -node to configure each node's partner node_mgmt LIF correctly... This is a cluster shell command (i.e. nas::>) storage failover modify -node nas-01 -hwassist-partner-ip <node-02's node_mgmt IP> storage failover modify -node nas-02 -hwassist-partner-ip <node-01's node_mgmt IP> 4. system node run -node nas-01 cluster shell commands place you into the node's "node shell". That's not necessary for this configuration exercise.

andris · ‎2017-10-07

I believe group creation and maintenance is done by opening a non-technical case with the group membership details provided to the SCA team (assuming you are authorized to request them).

andris · ‎2017-10-05

Missed one last correction... IOM6 ACP FW 0209 is required for inband ACP. 0210 is recommended.

andris · ‎2017-10-05

To recap... 1. IOM3 never has and never WILL support inband-ACP. this is due to a hardware limitation. 2. IOM3 support (I.e. monitor/manage storage with IOM3/DS4243) was removed in ONTAP 9.2. It is restored in 9.2P1 and will be in 9.3. 3. With IOM3 and IOM6 mixed storage your only option for full ACP features is to use OOB-ACP (and cable up the ACP ports).

Re: Network Port Roles for FAS2240 With SFP+ Running clustermode 9.1

Re: Network Port Roles for FAS2240 With SFP+ Running clustermode 9.1

Re: SP name (prompt) does not change

Re: AFF8080 SNMP Fibre Channel monitoring

Re: AFF8080 SNMP Fibre Channel monitoring

Re: Is Autosupport is supported on Solidfire systems

Re: Advance Drive Paritioning on a new FAS 8040 running9.2.1

Re: Advance Drive Paritioning on a new FAS 8040 running9.2.1

Re: Advance Drive Paritioning on a new FAS 8040 running9.2.1

Re: FAS2240-4 fully populated with 4TB drives - what is amperage requirement

Re: FAS8040 Ontap 9 Data network settings

Re: How to Update CN1610 Cluster Switch

Re: NSE Drives on non encrypted FAS

Re: CLUS LIFs Sharing same port

Re: Users home directories and quotas

Re: Storage Disk Replace and Root Aggr Disks

Re: Failure to build endpoint environment variables. Autoboot will be disabled.

Re: Autosupport SMTP server Configuring - one hostname returns many addresses

Re: Node Create failed : ONTAP Select

Re: cluster image package get failed from CDOT 9.1 to 9.2RC1

Re: Change disk ownership AFF 8040

Re: hw_assist error

Re: ActiveIQ (MyAutosupport) and "Group"

Re: 1. IOM3 module is not supported in in-band configuration. Upgrade to IOM6 or later. 2. IOM6 Modu

Re: 1. IOM3 module is not supported in in-band configuration. Upgrade to IOM6 or later. 2. IOM6 Modu

ONTAP 9.16.1 EAP

ONTAP 9.15.1 EAP