About andris

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).

andris · ‎2017-09-28

+1 on the bootarg. This bootarg is documented in the "Adding a second chassis to an existing HA pair" doc. You would just be configuring things in reverse/opposite, if going the other way. https://library.netapp.com/ecm/ecm_get_file/ECMM1280401

andris · ‎2017-09-27

Yes, 1.2.0.7 FW along with RCF 1.2. Make sure you setup and use SSH. RCF 1.2 disables Telnet access as a security best practice.

andris · ‎2017-09-26

There's a non-public bug Feature Request that allows ADP to include external shelves on FAS26xx, starting with ONTAP 9.1. If you're running ONTAP 9.2, the new Option 9 (ADP) boot menu option is the cat's meow.

andris · ‎2017-09-20

What is your goal? L2 redundancy, L3 (router) redundancy or both? To summarize from a L3 redundancy perspective... with these protocols, you have a virtual router IP address AND a virtual ethernet MAC address for this router. When one fails, the other takes over advertising the virtual IP and using gratuitous ARP requests to "teach" everyone the new location of the virtual MAC address. As you currently describe it, the NetApp nodes will not have L2 redundancy. That's OK - but if the single link to the switch fails, or the switch itself completely fails (as opposed to the router interface not working or downstream paths not working), the connectivity will fail. To configure L2 redundancy you'd dual-home the NetApp nodes to each switch, but you'd need a multi-switch link aggregation feature on the switch side. Extreme's MLAG feature, Cisco's VPC. The usual requirement on the edge/host/server/ONTAP side would be that the 2 ports are configured as a LACP (802.3ad) port-channel.

andris · ‎2017-09-20

Hi back, The idea behind all of these "router redundancy" protocols is you can have multiple physical routers cooperating to provide a reliable "virtual router" gateway IP address. The protocol itself runs between the routers, only. All the hosts (like the AFF A200) need to know is what the IP address of the virtual router/gateway is - just a configuration item when setting up the network LIFs.

andris · ‎2017-09-10

That's the right part. I can't vouch for Procurve, but optical SR usually isn't problem with the right SFP's on both ends.

andris · ‎2017-08-31

On the NetApp Support Site, if you search for configure vlan interface port ontap 9, one of the first hits is this page from the ONTAP 9.0 Network Management guide: Configuring VLANs over physical ports

andris · ‎2017-08-25

The doc link Alex pointed you to will get you going for active/passive in short order. If you're not dealing with multiple workloads and you don't have really high network I/O demands, active/passive is a reasonable choice. Even when active/active, you don't want to have either node handle much more than 50% of the total workloads, anyway (if you want acceptable performance when a node is down).

andris · ‎2017-08-25

8 HDD's is the minimum, but you'll have a better layout with root/data partitions if you do put the SSDs in the external shelf. This will allow root aggregates to spread out to 3d + 2p + 1s partitions on each node.

andris · ‎2017-08-14

I've passed on your concerns to the Product Manager.

andris · ‎2017-08-08

+1. I can think of a couple reasons why 9.0 can't be chosen, assuming all the systems are cDOT. FAS3240 or V3240: Not supported as of 9.0. DS14 storage shelves: Not supported as of 9.0.

andris · ‎2017-08-05

No, it's not supported. Check the Hardware Universe for supported 16G FC SFP's.

andris · ‎2017-08-05

Are you sure ALL of the serial numbers' models and starting ONTAP version can upgrade to 9.x?

andris · ‎2017-07-25

Can the 2 node_mgm LIF's ping each other? It looks like the wrench port on node 01 is connected to a switch, but it may not be in the correct VLAN on that switch.

andris · ‎2017-07-19

Be careful... You shouldn't have to worry about the SP version. The ONTAP version you upgrade/downgrade to will automatically do the same to the SP based on the version of SP that is bundled. Also, 3.1.2P1 is exactly what you want for ONTAP 8.3.x See: http://mysupport.netapp.com/NOW/download/tools/serviceimage/support/ServiceProcessorSupportMatrix.shtml I have to ask... why do you specifically need to run 8.3P2? Per recommended ONTAP releases at this time, 8.3.2P11 is the one you want to run for the 8.3.x ONTAP release family. https://kb.netapp.com/support/s/article/ka61A0000008aBr/Recommended-Data-ONTAP-Releases-on-the-NetApp-Support-Site

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

Re: Migrate from dual chassis HA to single chassis HA - Interconnect down

Re: Cluster interconnect switch setup (CN1610)

Re: ADP still limited to internal disks on FAS26XX with Ontap 9.2?

Re: How to configure AFF200 nodes for 10Gb VRRP, HSRP, ESRP switch configuration?

Re: How to configure AFF200 nodes for 10Gb VRRP, HSRP, ESRP switch configuration?

Re: Proper 10GbE SFP+ GBIC for the FAS2600 series?

Re: Netapp FAS2552 FCoE Nexus (non vPC)

Re: active/passive root-data adp in a FAS2620 with 4 SSD and 20 NL-SAS

Re: active/passive root-data adp in a FAS2620 with 4 SSD and 20 NL-SAS

Re: Upgrade advisor with multiple serial numbers does not show target version as 9 | UA team ?

Re: Upgrade advisor with multiple serial numbers does not show target version as 9

Re: Cisco 16G transceiver on FAS2650?

Re: Upgrade advisor with multiple serial numbers does not show target version as 9

Re: FAS node is reachable but not able to ping gateway from node1 other node2 rechable

Re: Dowgrade a new FAS8040 to 8.3P2 ¿possible?

ONTAP 9.18.1 EAP

Disaggregated ONTAP EAP

AI Data Engine (AIDE) EAP